JP6517735B2 - In-vehicle device log collection system - Google Patents

Description

  The present invention relates to an in-vehicle device log collection system.

  The log information is a hardware or software time-series operation record of a certain device. Taking the case where the device is a personal computer as an example, hardware log information is, for example, the power-on time, the temperature of a CPU (Central Processing Unit), the rotational speed of a cooling fan, and the like. The log information of software is, for example, debug information embedded in source code, error information, CPU usage, and the like. An equipment failure (abnormality) appears as a change in log information, and a specific symptom can be identified by analyzing the change.

  The device may monitor its own failure. However, if many devices are in operation after the manufacturer ships many devices, the individual devices are often connected to the manufacturer's server via the network and are collectively monitored by the server. . In this case, when the server analyzes all log information of all devices, the amount of resources used for acquisition, accumulation, transmission, analysis, etc. of log information becomes enormous. Therefore, techniques for narrowing the amount of log information to be processed, such as accumulation, to a sufficient amount for identifying a defect have been generalized.

  The log collection system of patent document 1 has a terminal device and a server. The server acquires log information from the terminal device via the network and analyzes it. Then, the server changes the method of detecting the abnormal state according to the content of the analyzed abnormal state, and instructs the terminal device to change the granularity, the content, and the accumulation frequency of the log information to be accumulated. The server further changes the content of the log information collected from the terminal device and the collection frequency according to the content of the analyzed abnormal state.

JP 2012-198796 A

  In Patent Document 1, it is assumed that hardware and software are operating in a matured state after entering the mass production system after development of the device has already been completed. However, at the time of device development, it is often the case that one server has to analyze the failure of many devices dispersed at remote locations.

  For example, when an on-vehicle device such as a car navigation system or a car audio is tested in a test course of each country in the world, a server disposed at one point in a certain country may analyze log information of the on-vehicle device. During such development, in-vehicle device developers cooperate with testers (test drivers) dispersed in each country to acquire necessary log information from the in-vehicle devices and analyze them. At this time, generally, the tester sends a defect report describing the defect of the in-vehicle device to the developer, and cuts out log information at the time of occurrence of the defect from the entire log information and stores it in the server. The developer further narrows down the log information stored in the server while referring to the defect report.

In such a cooperative system, there is an essential contradiction that it is the developer who analyzes the log information but the tester who cuts out the necessary log information first. For example, the following problems may occur due to this.
-The log information of the part which the developer judges to be necessary is not extracted, and the developer will request the tester to cut out the log information again.
-It is common for testers to embed markers in log information at the time of failure occurrence. However, it is difficult to embed the marker in the log information of all related hardware or software, for example, when the failure continues across multiple hardware or software.

  During development of in-vehicle devices, it is also conceivable to completely automate extraction of log information and storage on a server. However, it is practically rare that equipment and environment for this purpose are provided at all sites. If forced to automate, false detection of a defect may occur and the development efficiency may decrease. After all, it is necessary for developers and testers to work seamlessly together.

On the other hand, from the developer's point of view, the log information under test contains a lot of very useful information. For example, even if the tester sees the car-mounted device seemingly operating normally, the software may detect a failure. As a developer, there is also a need to analyze all log information in a pre-specified range even if no failure occurs.
Therefore, an object of the present invention is to efficiently acquire, without excess or deficiency, log information that a developer really needs from in-vehicle devices under development that are being tested in a distributed manner.

The in-vehicle device log collection system of the present invention includes a log management device and an in-vehicle log collection device, and the log management device is a summary to be preferentially analyzed among the log information collected by the in-vehicle log collection device from the in-vehicle device. A function of generating an analysis script in which conditions for extracting information in the vehicle log collection device and an instruction to transmit the extracted summary information are described, and transmitting the analysis script to the vehicle log collection device via the communication device The function of receiving the summary information extracted and transmitted by the on-board log collection device based on the analysis script via the communication device, and the function of extracting the log information at the time of occurrence of a failure in the on-vehicle device from the received summary information And the on-vehicle log collection device has a function of collecting log information from the on-vehicle device, and an analysis screen transmitted by the log management device. Function of receiving summary information via the communication device, and a function of extracting summary information from the collected log information based on the description of the received analysis script, the summary information extracted, and time information at the time when the failure occurs. And a function of transmitting to the log management apparatus via the communication apparatus.
Other means will be described in the form for carrying out the invention.

  According to the present invention, it is possible to efficiently acquire the log information that the developer really needs from the in-vehicle devices under development that are being tested in a distributed manner without excess or deficiency.

It is a figure explaining the composition of a vehicle-mounted apparatus log collection system. It is a figure which shows an example of a log information database. It is a figure which shows an example of marker allocation information. It is a figure which shows an example of an analysis script registration screen. It is a figure which shows an example of a warning screen. (A) is a figure which shows an example of a marker confirmation * correction screen, (b) is a figure which shows an example of a malfunction report. (A) is a figure which shows another example of a marker confirmation * correction screen, (b) is a figure which shows another example of a defect report. (A) is a figure which shows an example of a whole log management screen, (b) is a figure which shows an example of a summary confirmation screen. It is a figure which shows an example of a log download screen. (A) is a figure which shows an example of a relationship analysis screen (vehicle), (b) is a figure which shows an example of a relationship analysis screen (version). It is a sequence diagram of a processing procedure. It is a figure showing an example of an analysis script.

  Hereinafter, modes for carrying out the present invention (referred to as “the present embodiment”) will be described in detail with reference to the drawings and the like.

(Configuration of in-vehicle device log collection system)
The configuration of the in-vehicle device log collection system 1 will be described with reference to FIG. The in-vehicle device log collection system 1 includes an in-vehicle log collection device 2, a log management device 3, and a base server 4. These are mutually connected by a wired or wireless network 5. The user of the in-vehicle device log collection system 1 is typically a manufacturer of in-vehicle devices such as car navigation and car audio. Manufacturers have headquarters and many bases as their own organizations. Each base has a test course, and vehicles travel on the test course. The vehicle is equipped with the on-vehicle device 6 and the on-vehicle log collection device 2.

  The in-vehicle log collection device 2 is a general computer connected to the in-vehicle device 6. The on-vehicle log collection device 2 may constitute a part of the on-vehicle device 6. The on-vehicle log collection device 2 includes a central control device 11 (collection device side control device), an input device 12, an output device 13, a main storage device 14, an auxiliary storage device 15 and a communication device 16. Connected to each other. The auxiliary storage device 15 stores an analysis script 32, marker assignment information 33, a failure report 34, and a summary information database 35 (details will be described later).

  The log collection unit 21 in the main storage device 14 is a program. Hereinafter, when the log collecting unit 21 describes the operation subject as “the log collecting unit 21”, the central control unit 11 reads the log collecting unit 21 from the auxiliary storage device 15 and loads the log collecting unit 21 into the main storage device 14. Function (detailed later) shall be realized. Usually, a plurality of in-vehicle log collection devices 2 and a vehicle equipped with the in-vehicle log collection device 2 are disposed at each site. The user who operates the in-vehicle log collection device 2 is a tester of the in-vehicle device 6. The site server 4 stores a log information database 31. One base server 4 is usually arranged at each base.

  The log management device 3 is also a general computer. The log management device 3 includes a central control device 41 (management device side control device), an input device 42, an output device 43, a main storage device 44, an auxiliary storage device 45, and a communication device 46. It is connected to the. The auxiliary storage device 45 stores an analysis script 32, marker assignment information 33, a failure report 34, and a summary information database 35. These are the same as the respective information stored in the auxiliary storage device 15 of the on-vehicle log collection device 2.

  The log management unit 22 in the main storage device 44 is a program. Hereinafter, when the log management unit 22 describes the operation subject, the central control device 41 reads the log collection unit 22 from the auxiliary storage device 45 and loads the log collection unit 22 into the main storage device 44. Function (detailed later) shall be realized. Normally, one log management device 3 is disposed at the head office. The user who operates the log management device 3 is a developer of the in-vehicle device 6.

(Log information database)
The log information database 31 of the base server 4 will be described with reference to FIG. In the log information database 31, the base ID is associated with the country ID stored in the country column 101, the base ID in the base column 102, the vehicle ID in the vehicle column 103, and the in-vehicle log collection device in the in-vehicle log collection device column 104. ID, tester name in tester column 105, log type in log type column 106, item in item column 107, version in version column 108, status value in status value column 109, The acquisition time point 110 stores the acquisition time point.

The country ID of the country column 101 is an identifier that uniquely identifies the country to which the base belongs.
The base ID in the base column 102 is an identifier for uniquely specifying a base.
The vehicle ID of the vehicle column 103 is an identifier that uniquely identifies the vehicle on which the in-vehicle device 6 is mounted.
The on-vehicle log collection device ID in the on-vehicle log collection device column 104 is an identifier for uniquely identifying the on-vehicle log collection device 2.
The examiner name in the examiner column 105 is the name of the examiner.
The log type in the log type column 106 is a type of log information of the in-vehicle device 6 controlled by the control software (not shown). The log type may be the name of hardware controlled by the control software.

An item of the item column 107 is information for explaining what a state value acquired by the control software indicates.
The version of the version field 108 is a version of control software.
The state values in the state value column 109 are specific values acquired by the control software. The state value is a numerical value, a symbol indicating start / stop, a flag indicating the presence or absence of a malfunction (abnormality), etc., and a character string indicating the state of operation or malfunction (abbreviated as “···” in the figure) ).
The acquisition time point of the acquisition time field 110 is the date, time, hour, minute and second when the state value is acquired.

(Marker assignment information)
The marker assignment information 33 will be described with reference to FIG. In the marker assignment information 33, the in-vehicle log collection device field 112 stores the in-vehicle log collection device ID in association with the marker ID stored in the marker field 111, and the insufficiency button depression time point 113 stores the insufficiency button depression time point. ing.

The marker ID in the marker field 111 is an identifier that uniquely identifies the marker. The marker is information indicating a combination of the on-vehicle log collection device 2 and the point at which the malfunction button is pressed (immediately described later).
The in-vehicle log collection device ID of the in-vehicle log collection device column 112 is the same as the in-vehicle log collection device ID in FIG. 2.
When the defect button is pressed in the defect button pressing time column 113, the tester recognizes that a defect has occurred in the in-vehicle device 6, and presses the defect button (not shown). .

  In the following, in order to facilitate understanding of the contents of the present embodiment, the display screen will be described first, and then the processing procedure will be described.

(Analysis script registration screen)
The analysis script registration screen 51 will be described with reference to FIG. The analysis script 32 (FIG. 1) is an instruction sheet that the log management device 3 transmits to the on-vehicle log collection device 2. The log management unit 22 of the log management device 3 displays the analysis script registration screen 51 on the output device 43. The developer who sees the screen inputs, for example, “qqq-analyze” in the analysis script upload field 52. This is a so-called file path, and is position information on the network where the analysis script 32 is stored.

Next, it is assumed that the developer has input, for example, the following data into the analysis script field 53 via the input device 42. Note that these input data are conditions for extracting summary information to be preferentially analyzed from the log information.
・ Enter "CAN (Controller Area Network)" in the log type column 53a.
Enter "Processing delay time" in the keyword field 53b.
・ Enter "120 ms or more" in the numerical value judgment field 53c. Note that "more than" is selected by a radio button.
In the action column 53d, enter “notice of defect to tester”, “sound 1” and “notification of summary information” (input a check mark in the check column).
Further, it is assumed that the developer similarly inputs in the analysis script field 54 as shown in FIG. Then, it is assumed that the information registered on the analysis script registration screen 51 is transmitted to the on-vehicle log collection device 2.

  Then, the log collection unit 21 of the in-vehicle log collection device 2 having received the analysis script 32 cuts out the log information of the period when the processing delay time of CAN has become 120 ms or more among the log information output by the in-vehicle device 6 , This is sent to the log management device 3 as summary information. Furthermore, the log collection unit 21 issues a warning to the tester with a specific sound (sound 1) via the output device 13 (speaker). The sound of the warning continues as long as "the processing delay time of CAN is 120 ms or more". The sound may be an electronic sound such as "pi, pi, pi, ..." or a language such as "please be careful ...". Furthermore, the warning here may be anything that will alert the examiner aurally, visually or tactilely.

  Similarly, the log collection unit 21 cuts out log information of a period when the internal bus traffic of module A becomes 54 KB / s or more among the log information output by the in-vehicle device 6, and manages the log as summary information. Send to device 3 Furthermore, the log collection unit 21 issues a warning to the tester with a specific sound (sound 2) different from the sound 1 via the output device 13 (speaker). The sound of the warning continues as long as "the internal bus traffic of module A is 54 KB / s or more". The contents input to the analysis script fields 53, 54,... Of FIG. 4 are uploaded to “qqq-analyze”.

  The warning screen 55 will be described with reference to FIG. The log collection unit 21 of the on-vehicle log collection device 2 displays a warning screen 55 on the output device 13. In the above, the example which the log collection part 21 emits a sound was shown. However, the log collection unit 21 may issue a warning in color. The warning screen 55 displays designs 56a, 56b,... Corresponding to the analysis script fields 53, 54,. Among them, the log collecting unit 21 may highlight the processing delay time 56a and the internal bus traffic 56b in a specific color (a color such as yellow that is easy to draw attention).

(Marker confirmation / correction screen)
The marker confirmation / correction screen 61 will be described with reference to FIG. The log collection unit 21 of the on-vehicle log collection device 2 displays the marker confirmation / correction screen 61 on the output device 13. As a premise of the following description, it is assumed that the tester (Hitachi Taro) tests the on-vehicle apparatus 6 using the on-vehicle log collection device M001 while driving the vehicle V001 on the test course (see FIG. 2). It is assumed that the tester recognizes a defect (flickering of the screen) of the in-vehicle device 6 at 10:01:30 on February 12, 2016, and presses the defect button on the input device 12 of the in-vehicle log collection device 2. Thereafter, it is assumed that the tester finishes the test and creates the defect report 34 (FIG. 6B) while looking at the marker confirmation / correction screen 61 on the output device 13 of the on-vehicle log collection device 2.

  The marker confirmation / correction screen 61 (FIG. 6A) shows log information in chronological order. These pieces of log information are extracted from the summary information database 35 by the log collection unit 21 of the on-vehicle log collection device 2 based on the time point of the marker 62 whose marker ID is the MR 102. The log information is divided into items such as playback music 63a, key operation 63b and navigation guidance 63c. The log collecting unit 21 can extract data from the summary information database 35 when the malfunction button is pressed to the specific on-vehicle log collecting apparatus 2 by using the marker ID.

  That is, in the example of FIG. 6A, the log collection unit 21 operates the reproduction music 63a as the log information of the period including the time “10:01:30 on February 12, 2016” for the vehicle V001, and the key operation 63b and navigation guidance 63c are acquired. In addition, even if the log information is not included in the summary information database 35, the log collecting unit 21 (even if not specified in the analysis script fields 53, 54,... In FIG. 4) These log information can be extracted from the database 31.

  The tester determines that switching the playback music from the radio to the USB (Universal Serial Bus) is the cause of the failure, and adds a marker 64 indicating the switching time. The tester can also change the positions of the markers 62 and 64 left and right. Adding a new marker is equivalent to the log collection unit 21 of the on-vehicle log collection device 3 adding a record (row) of the marker allocation information 33 (FIG. 3), and moving the marker is an on-vehicle log This corresponds to the log collection unit 21 of the collection device 3 changing the pressing time point of the failure button of the existing record of the marker allocation information 33.

  As another example, the tester recognizes a defect in the on-vehicle device 6 (the reproduction of the music becomes small) at 10:00:00 on Feb. 12, 2016, and the tester uses the input device 12 of the on-vehicle log collection device 2. It is assumed that the problem button of is pressed. After that, it is assumed that the tester creates the defect report 34 (FIG. 7B) while looking at the marker confirmation / correction screen 61 (FIG. 7A).

In the example of FIG. 7A, the log collecting unit 21 determines five summary information from the summary information database 35 based on the marker 66 indicating the time point "10:00:00 on February 12, 2016" for the vehicle V001. I am getting information. That is, these five are a music speaker 65a, a guidance speaker 65b, a voice synthesis unit 65c, a map unit 65d and a position determination unit 65e. The tester who saw these log information knows the following things.
-The voice for guiding the poor intersection was synthesized, and the playback sound of the music should be reduced so that the voice is not erased.
・ However, the voice of the guidance was not generated from the speaker.
-As a result, it was interpreted that the playback sound of music became small alone.
The tester newly adds a marker 67 indicating when the music reproduction sound has returned to the original size.

(Whole log management screen and summary confirmation screen)
The entire log management screen 71 will be described with reference to FIG. 8 (a). The log management unit 22 of the log management device 3 displays the entire log management screen 71 on the output device 43. Now, on the horizontal axis of the overall log management screen 71, a certain period is displayed. The period is from a point slightly before 12:00 on February 12, 2016 to a point slightly after 11:00. The log management unit 22 refers to the summary information database 35, checks the presence or absence of summary information for all vehicles in the relevant period, and displays the result.

  The summary information is not acquired for the vehicle V003 in the relevant period. The markers 72 and 73 are displayed for the vehicle V001 and the vehicle V002, respectively, but no marker is displayed for the vehicle V004. This indicates that the tester pressed the malfunction button at the time of testing the vehicle V001 and the vehicle V002, but did not press the malfunction button at the time of the test of "V004".

  The developer selects the marker 72 of the vehicle V001. Then, the log management unit 22 changes the screen to the summary confirmation screen 75 (FIG. 8B). The log management unit 22 extracts the summary information about the vehicle (which is the vehicle V001) specified by the marker 72 and the time point from the summary information database 35, and displays it as an item A76a, an item B76b, and an item C76c. From the item A 76 a, it can be read how some physical quantity (state value) changes in time series. From item B 76 b, it can be read that an “abnormal log” has occurred at a certain point in time.

(Log download screen)
The log download screen 81 will be described with reference to FIG. It is assumed that the developer selects the marker 72 on the entire log management screen 71 (FIG. 8A) and then presses the “download log” button (not shown). Then, the log management unit 22 changes the screen to the log download screen 81 (FIG. 9). The log management unit 22 refers to the log information database 31, checks the presence or absence of all log information regarding the vehicle V001 for each log type, and displays the log type in which the log information exists.

  In the example of FIG. 9, it is displayed that the log type A 83 a, the log type B 83 b, the log type C 83 c, and the log type D 83 d exist as log information including the time point indicated by the marker 82. Now, the developer is investigating a defect that has occurred in the vehicle V 001 when the marker 82 indicates. The developer thinks that the log information of the log type A 83 a, the log type C 83 c and the log type D 83 d is necessary for the period “10:00 to 10:06 on February 12, 2016”. Then, the developer first enters a check mark in the check boxes 84a, 84c and 84d among the check boxes 84a, 84b, 84c and 84d, and the period "10:00 to 10:02 on February 12, 2016 Draw an arrow-shaped figure 85 for "minutes". Then, the log management unit 22 acquires log information required by the developer from the log information database 31.

(Relational analysis screen (vehicle))
The relationship analysis screen (vehicle) 91a will be described with reference to FIG. 10 (a). The log management unit 22 of the log management device 3 displays the relationship analysis screen (vehicle) 91 a on the output device 43. Now, a developer wants to browse log information in which a specific event has occurred for each vehicle in a specific period. At this time, the developer inputs, for example, an event “warning abc” in the keyword column 92. Then, the log management unit 22 searches the log information database 31 using “warning abc” as a search key, and displays, for each vehicle, log information corresponding to even one keyword.

  In the example of FIG. 10A, “Warning abc” is issued twice to the log information of the vehicle V001 in a period (9:45 to 11:15 on February 12, 2016) in which the developer wishes to view the document. In addition, it can be understood that “warning abc” has occurred once in the log information of the vehicle V 003. “Warning abc” has not occurred during the relevant period for the vehicle V 002 For example, when scrolling the period of the horizontal axis and looking at other time zones, "warning abc" should have occurred.

  The bar 93 of the log information about the vehicle V 003 is uniquely highlighted. This indicates that the log information of the period related to the bar 93 is also stored as summary information (designated in the analysis script fields 53, 54,... In FIG. 4).

(Relational analysis screen (version))
The relationship analysis screen (version) 91b will be described with reference to FIG. 10 (b). The log management unit 22 of the log management device 3 displays the relationship analysis screen (version) 91 b on the output device 43. Now, a developer wants to view log information, in which a specific event has occurred, for each control software version in a specific period. At this time, the developer inputs, for example, an event “error def” in the keyword column 94. Then, the log management unit 22 searches the log information database 31 using “error def” as a search key, and displays the log information corresponding to even one location for each version. The contents displayed on the relation analysis screen (version) 91b conform to the contents displayed on the relation analysis screen (vehicle) 91a, and thus the detailed description will be omitted. However, the number of times of occurrence of the keyword in the log information in the relevant period is displayed for each version in the cumulative total columns 95a, 95b and 95c.
Note that “(Vehicle)” and “(Version)” added to the names of the relationship analysis screen (vehicle) 91a and the relationship analysis screen (version) 91b display log information for each vehicle, and log information for each version Includes the meaning of displaying.

(Processing procedure)
The processing procedure will be described with reference to FIG. Note that solid arrows indicate the flow of information processing, and broken arrows indicate the flow of information.
In step S201, the log management unit 22 of the log management device 3 displays the analysis script registration screen 51 (FIG. 4). Specifically, first, the log management unit 22 displays the analysis script registration screen 51 on the output device 43.
Second, the log management unit 22 accepts that the developer inputs the data described above in the analysis script upload field 52 and the analysis script fields 53, 54,.

  In step S202, the log management unit 22 transmits an analysis script. Specifically, the log management unit 22 creates the analysis script 32 based on the data input to the analysis script fields 53, 54,. The content of the analysis script 32 is the data itself input to the analysis script fields 53, 54,. Then, the log management unit 22 stores the created analysis script 32 in the auxiliary storage device 45 and transmits the analysis script 32 to the on-vehicle log collection device 2. Thereafter, the tester starts to test the on-vehicle apparatus 6 using the on-vehicle log device 2.

  In step S203, the log collection unit 21 of the on-vehicle log collection device 2 starts collection of log information. Thereafter, the log collection unit 21 acquires the total amount of log information and accumulates the total amount in the log information database 31 of the base server 4 via the network 5 until the end of the test. The log collection unit 21 may store the entire amount in its own auxiliary storage device 15. At the same time, the log collection unit 21 extracts (cuts out) summary information specified by the developer by the analysis script 32 from the log information and accumulates it in the summary information database 35.

  In step S204, the log collection unit 21 receives pressing of the failure button. Specifically, the log collection unit 21 recognizes that the tester recognizes a defect in the in-vehicle apparatus 6 and presses the defect button via the input device 12. The malfunction button is displayed on the screen of the input device 12.

  In step S205, the log collection unit 21 requests a marker ID. Specifically, the log collection unit 21 transmits a request to the effect that the marker ID is issued, to the log management device 3 together with the on-vehicle log collection device ID and the pressing time of the malfunction button (time information).

In step S206, the log management unit 22 of the log management device 3 numbers and transmits the marker ID. Specifically, first, the log management unit 22 generates a new record of the marker assignment information 33 (FIG. 3).
Second, the log management unit 22 assigns a new marker ID, and stores it in the marker field 111 of the new record.

Thirdly, the log management unit 22 adds the in-vehicle log collection device ID and the malfunction button pressed time point (time information) transmitted in step S 205 to the in-vehicle log collection device field 112 and the malfunction button pressed time field 113 of the new record. I will remember each.
Fourth, the log management unit 22 transmits the newly generated record (the marker ID, the on-vehicle log collection device ID, and the pressing time of the malfunction button are stored) to the on-vehicle log collection device 2.

In step S207, the log collection unit 21 of the on-vehicle log collection device 2 notifies the tester of the failure. Specifically, first, the log collection unit 21 constantly monitors the state values specified by the log type 53 a and the like specified in the analysis script 32 and the keyword 53 b and the like.
Second, the log collection unit 21 tests the state value by a method designated by the action 53d or the like in a period which is equal to or less than (or equal to) the value designated by the numerical value judgment 53c or the like. Issue a warning to As a matter of course, when the check mark is not input to any “notice of defect to tester” such as the action 53 d, step S 207 is omitted.

  In step S204, the tester recognizes the apparent abnormality as a defect and presses the defect button. On the other hand, in step S207, the log collection unit 21 suggests (notifies) the tester that "the log information is in a proper state even when the malfunction button is pressed". That is, the log collection unit 21 warns that a failure may occur.

In step S208, the log collection unit 21 transmits summary information. Specifically, first, the log collection unit 21 constantly monitors the state values specified by the log type 53 a and the like specified in the analysis script 32 and the keyword 53 b and the like.
Second, when the status value is equal to or greater than the value specified by the numerical value determination 53c or the like (is the same or less than or equal to), the log collection unit 21 summarizes the log information of the period during which the state continues. The information is stored in the summary information database 35 as information and transmitted to the log management device 3. As a matter of course, when the check mark is not input to any "summary information notification" such as the action 53d, step S208 is omitted.
Thereafter, the tester ends the test of the in-vehicle device 6.

  In step S209, the log collection unit 21 displays the marker confirmation / correction screen 61 (FIG. 6 (a) or FIG. 7 (a)). Specifically, the log collection unit 21 displays the marker confirmation / correction screen 61 on the output device 13 of the on-vehicle log collection device 2. At this time, the log collection unit 21 receives that the user adds, deletes or moves a marker, and updates the record of the marker assignment information 33 (FIG. 3) according to the received content.

In step S210, the log collection unit 21 transmits the problem report 34. Specifically, first, the log collection unit 21 uses the software for creating a document for the tester to use the document creation software for the input device 12 of the on-vehicle log collection device 2 (FIG. 6 (b) or 7 (b) is received.
Second, the log collection unit 21 stores the defect report 34 in the auxiliary storage device 15 and transmits the defect report 34 to the log management device 3.

  In step S211, the log management unit 22 of the log management device 3 displays the entire log management screen 71 (FIG. 8A) and the summary confirmation screen 75 (FIG. 8B). Specifically, the log management unit 22 displays the entire log management screen 71 and the summary confirmation screen 75 on the output device 43 of the log management device 3. The developer can know the outline of what summary information about which vehicle is acquired by viewing or operating these screens. Furthermore, the developer can know the outline of the relation between a plurality of items with respect to a certain defect.

  The entire log management screen 71 (FIG. 8A) and the summary confirmation screen 75 (FIG. 8B) illustrate information included in the summary information transmitted in step S208. In other words, the summary information is information that the developer wants to analyze first with priority, of the total amount of log information (see also the description of FIG. 12 described later).

  In step S212, the log management unit 22 displays the log download screen 81 (FIG. 9). Specifically, the log management unit 22 displays the log download screen 81 on the output device 43 of the log management device 3. At this time, the log management unit 22 receives an input of log information required by the developer.

  In step S213, the log management unit 22 receives log information. Specifically, the log management unit 22 acquires, from the log information database 31, the log information in the range input as the developer needs in the log download screen 81 displayed in step S212.

  In step S214, the log management unit 22 displays a relationship analysis screen. Specifically, the log management unit 22 causes the output device 43 of the log management device 3 to display a relationship analysis screen (vehicle) 91a (FIG. 10 (a)) and a relationship analysis screen (version) 91b (FIG. 10 (b)). Display After the developer makes a rough policy using the summary information in step S211, the developer can search the log information (total amount information) using the screen to search for the cause of the defect in more detail. it can.

  In step S215, the log management unit 22 analyzes the trend. Specifically, the log management unit 22 uses the summary information to perform a mild trend analysis not involving the tester. As an example of trend analysis, statistical values such as average value and variance value of state values based on summary information are acquired, they are compared with statistical values such as average value and variance value of the whole log information, Output the relationship, etc.

In step S216, the log management unit 22 updates and transmits the analysis script 32. Specifically, the log management unit 22 repeats the processes of steps S201 and S202. At this time, the developer changes the value input to the analysis script registration screen 51 (FIG. 4) based on his / her knowledge obtained by looking at the screens displayed in step S211 and step S214 .
After this, the processing of steps S203 to S215 is repeated. When the developer inputs an end instruction to the log management device 3 without responding to the process of step S216, the processing procedure ends.

(Another example of analysis script)
Another example of the analysis script 32 will be described with reference to FIG. The log management device 3 determines the processing content to be performed by the on-vehicle log collection device 2 by the analysis script 32. As an example of such an analysis script 32, the example of FIG. 12 exists other than the example of FIG. The log management unit 22 of the log management device 3 accepts that the developer inputs the following five types of instructions via the input device 42. The log management unit 22 stores the received instruction as the analysis script 32 in the auxiliary storage device 45 and transmits it to the on-vehicle log collection device 2.

  Instruction 1: The on-vehicle log collection device 2 stores, for the specific log information specified by the developer, the state value at the time when the tester is pressing the failure button. At this time, it is desirable that the malfunction button is held in the pressed state until it is pressed again (cancelled) after being pressed once. The log information column 321 reflects the following idea of the developer.

-The log information whose log type is "CAN", whose item is "processing time delay" and whose version is "1.01" is particularly important, and the period during which the tester recognizes a defect I want to remember by all means.
-The same applies to log information whose log type is "module A", whose item is "memory usage" and whose version is "3.02".
• Other log information does not need to be stored even if the tester recognizes a defect. (It does not mean that other log information is not necessary, but it means that the total amount of log information is analyzed in several times.)

Instruction 2: The on-vehicle log collection device 2 stores the state value at the time when the state value exceeds a certain threshold value for the specific log information specified by the developer. The log information column 322 reflects the following idea of the developer.
The log information whose log type is “CAN” and whose item is “processing time delay” is controlled by control software whose version is “1.01”. At this time, if the state value exceeds the threshold TH1, the control efficiency is reduced, and it is necessary to upgrade the control software.
The same applies to log information whose log type is “module A”, whose item is “memory usage”, and whose version is “3.02”.

Instruction 3: For the specific log information specified by the developer, the on-vehicle log collection device 2 stores the state value at the time when the state value exceeds a certain threshold, and continues while the state value exceeds the threshold Alert the examiner. The log information column 323 reflects the following idea of the developer.
The log information whose log type is “CAN” and whose item is “processing time delay” is controlled by control software whose version is “1.01”. At this time, when the state value exceeds the threshold TH11, the control becomes unstable. Therefore, it is necessary to alert the tester by voice or the like to lower the state value to the threshold TH11 or less.
The same applies to log information whose log type is “module A”, whose item is “memory usage”, and whose version is “3.02”.

Instruction 4: The on-vehicle log collection device 2 stores state values at all points in a specific period for specific log information specified by the developer. The log information column 324 reflects the following idea of the developer.
The log information whose log type is “CAN” and whose item is “internal bus traffic” is controlled by control software whose version is “2.01”. I want to acquire log information from multiple in-vehicle devices in a certain period and then aggregate and analyze them at the headquarters.
The same applies to log information whose log type is “module B”, whose item is “number of warnings”, and whose version is “4.01”.

Instruction 5: The on-vehicle log collection device 2 performs specific statistical processing on specific log information specified by the developer, and records statistical information as a result. The log information column 325 reflects the following idea of the developer.
-By knowing the hourly average value and variance of the status value of the log information whose log type is "CAN", the item is "internal bus traffic", and the version is "2.01", I want to analyze how much outliers can be regarded as outliers.
-The same applies to log information whose log type is "module A", whose item is "memory usage" and whose version is "3.02".

(Effect of this embodiment)
(1) The in-vehicle device log collection system enables a developer to efficiently search for truly necessary information from log information, using the time of occurrence of a failure as a key.
(2) The in-vehicle device log collection system warns the tester of the occurrence of a potential failure, thereby preventing the tester from missing the failure.
(3) The in-vehicle device log collection system enables the developer to review the conditions for extracting summary information from the log information at appropriate timing.
(4) The in-vehicle device log collection system can acquire log information at the time of occurrence of a failure without directly embedding a marker in the log information.

(5) The in-vehicle device log collection system enables the tester to review the time of failure.
(6) The on-vehicle equipment log collection system can reduce the burden on the tester when driving a vehicle equipped with the on-vehicle equipment, and can safely and reliably convey a warning.
(7) The in-vehicle device log collection system can prepare statistical information for detecting a failure.
(8) The in-vehicle device log collection system enables a developer to easily search for log information at the time of occurrence of a failure while reading the failure report.

DESCRIPTION OF SYMBOLS 1 in-vehicle apparatus log collection system 2 in-vehicle log collection apparatus 3 log management apparatus 4 base server 5 network 6 in-vehicle apparatus 11, 41 central control apparatus 12, 42 input apparatus 13, 43 output apparatus 14, 44 main storage 15, 45 auxiliary storage Device 16, 46 Communication device 21 Log collection unit 22 Log management unit 31 Log information database 32 Analysis script 33 Marker allocation information 34 Problem report 35 Summary information database

Claims (8)

Equipped with a log management device and an on-board log collection device,
The log management device
A condition for extracting, in the on-vehicle log collection device, summary information to be preferentially analyzed among the log information collected by the on-vehicle log collection device from the on-vehicle apparatus, and an instruction to transmit the extracted summary information Generating an analysis script in which the information is described, and transmitting the analysis script to the on-vehicle log collection device via the communication device;
A function of receiving, via a communication device, summary information extracted and transmitted by the on-vehicle log collection device based on the analysis script;
A management apparatus side control apparatus having a function of extracting the log information at the time of occurrence of a failure in the in-vehicle device from the received summary information;
The on-vehicle log collection device
A function of collecting log information from the in-vehicle device;
A function of receiving the analysis script transmitted by the log management device via a communication device;
A function of extracting the summary information from the collected log information based on the description of the received analysis script;
A collection apparatus side control apparatus having a function of transmitting the extracted summary information and time information at the time of occurrence of the failure to the log management apparatus via a communication apparatus; Equipment log collection system. The analysis script is
Write an instruction to issue a warning when there is a possibility that the failure will occur,
The on-vehicle log collection device
Emitting a warning based on the analysis script to prompt the user to input a time when the failure occurs;
The vehicle-mounted apparatus log collection system according to claim 1, characterized in that The log management device
Updating the content described in the analysis script;
The on-vehicle equipment log collection system according to claim 2, characterized in that The log management device
When there are a plurality of in-vehicle log collection devices, a marker identifier is assigned to a combination of each in-vehicle log collection device and the time when the failure occurs, and the failure occurs using the assigned marker identifier. Extracting the log information at the time of
The on-vehicle equipment log collection system according to claim 3, characterized in that The on-vehicle log collection device
Receiving the input after the user corrects the time when the failure occurs;
The on-vehicle equipment log collection system according to claim 4, characterized in that The warning is
Alerting the user aurally, visually or tactilely,
The on-vehicle equipment log collection system according to claim 5, characterized in that The summary information is
Including statistical information about the in-vehicle device;
The on-vehicle equipment log collection system according to claim 6, characterized in that The log management device
Sending the marker identifier to the onboard log collection device;
The on-vehicle log collection device
Sending a defect report describing the content of the defect using the marker identifier to the log management device;
The on-vehicle equipment log collection system according to claim 7, characterized in that

Images