Inspection apparatus, inspection system, and inspection method

There are provided an inspection apparatus, an inspection system, and an inspection method capable of inspecting operation of a control device, accurately, during use.An inspection apparatus configured to inspect operation of an ECU coupled to automotive networks, includes an inspection performance control unit configured to transmit two pieces of data including operation-inspection data and security-check data used for inspecting the operation of the ECU, to the ECU, and configured to receive data output from the ECU. The operation-inspection data is data previously generated based on design information of the ECU. The security-check data is data including part or entirety of the operation-inspection data replaced with random data.

TECHNICAL FIELD

The present invention relates to an inspection apparatus, an inspection system, and an inspection method that inspect operation of a control device with which a motor vehicle has been equipped. In particular, the invention is suitable for applying to an inspection apparatus, an inspection system, and an inspection method that inspect operation of a control device coupled to automotive networks.

BACKGROUND ART

Recently, a technique of coupling a plurality of control devices (electronic control units: ECUs) with which a motor vehicle has been equipped, to automotive networks (controller area network: CAN) and operating the plurality of control devices in cooperation with each other through the automotive networks, has been developed.

Examples of the plurality of ECUs include an engine ECU that performs control of an engine, a transmission ECU that performs control of shift changing, and a brake ECU that adjusts brake oil pressure. PTL 1 discloses a technique of determining a defect of cooperating operation and specifying a failure area in a case where the plurality of ECUs operates in cooperation with each other.

In particular, PTL 1 discloses a failure diagnosis system including a defect determining means configured to determine occurrence of the defect due to the cooperating operation, based on data transmitted and received between the ECUs through automotive networks, a program acquisition means configured to acquire an inspection diagnosis program previously prepared in correspondence to the defect when the occurrence of the defect is determined, and a failure area specifying means configured to perform the inspection diagnosis program so as to perform corresponding processing to the ECUs, and configured to specify the failure area based on information transmitted from the ECUs by the performance of the corresponding processing.

CITATION LIST

Patent Literature

SUMMARY OF INVENTION

Technical Problem

However, the failure diagnosis system described in PTL 1 specifies the failure area, using the previously prepared inspection diagnosis program. The inspection diagnosis program is a program previously generated before use, based on design information on the ECUs. Thus, it cannot be determined whether the ECUs properly operate in a case where data not assumed at a design stage, is transmitted to the ECUs during the use.

That is, a failure can be specified about the failure (a malfunction). However, it cannot be accurately determined whether the operation being performed is normal or abnormal.

The present invention has been made in consideration of the above point. An object of the present invention is to propose an inspection apparatus, an inspection system, and an inspection method capable of inspecting operation of an ECU accurately during use.

Solution to Problem

In order to solve the above problem, the inspection apparatus according to the present invention includes: an inspection performance control unit configured to transmit two pieces of data including operation-inspection data and security-check data used for inspecting operation of an ECU, to the ECU, and configured to receive data output from the ECU. The operation-inspection data is data previously generated based on design information of the ECU. The security-check data is data including part or entirety of the operation-inspection data replaced with random data.

In order to solve the above problem, an inspection system according to the present invention, includes: a service providing server including: an inspection plan unit configured to plan a schedule for inspecting operation of an ECU; an inspection data generation unit configured to generate two pieces of data including operation-inspection data and security-check data used for inspecting the operation of the ECU; and an inspection control unit configured to transmit the generated two pieces of data to an exterior in accordance with the planned schedule; and a gateway configured to transmit, in a case where the two pieces of data including the operation-inspection data and the security-check data transmitted from the service providing server, are received, the received two pieces of data to the ECU, the gateway configured to transmit, in a case where data output from the ECU is received, inspection performance result information including the received data to the service providing server. The operation-inspection data is data previously generated based on design information of the ECU. The security-check data is data including part or entirety of the operation-inspection data replaced with random data.

In order to solve the problem, an inspection method according to the present invention, includes: a first step of planning a schedule for inspecting operation of an ECU, by an inspection plan unit; a second step of generating two pieces of data including operation-inspection data and security-check data used for inspecting the operation of the ECU, by an inspection data generation unit; a third step of transmitting the generated two pieces of data to an exterior, by an inspection control unit, in accordance with the planned schedule; and a fourth step of transmitting by a gateway, in a case where the two pieces of data including the operation-inspection data and the security-check data transmitted from a service providing server, are received, the received two pieces of data to the ECU, and in a case where data output from the ECU is received, inspection performance result information including the received data to the service providing server. The operation-inspection data is data previously generated based on design information of the ECU. The security-check data is data including part or entirety of the operation-inspection data replaced with random data.

Advantageous Effects of Invention

According to the present invention, the operation of the ECU during the use can be accurately inspected.

DESCRIPTION OF EMBODIMENTS

One embodiment of the present invention will be described below for the drawings.

(1) Entire Configuration

FIG. 1illustrates an entire configuration of an inspection system5according to the present embodiment. The inspection system5is configured with a motor vehicle1, a service providing server2, and a terminal having a communication function3. The motor vehicle1, the service providing server2, and the terminal having a communication function3are coupled so as to be communicable to each other through a communication network4. The communication network4is, for example, a mobile phone network or a wireless local area network (LAN).

The motor vehicle1is configured with a gateway11and a plurality of electronic control units (ECUs)12. The gateway11and each of the ECUs12are coupled through automotive networks referred to as a controller area network (CAN).

The gateway11here is a terminal that functions as an inspection apparatus. The gateway11is configured with an inspection performance control unit111, an inspection information acquisition unit112, an inspection performance unit113, an inspection monitor unit114, a communication unit115, and an inspection information management unit116.

The inspection performance control unit111stores an inspection performance data information1161received through the communication unit115, in the inspection information management unit116, and also acquires and transmits the inspection performance data information1161stored in the inspection information management unit116, to the ECUs12. The inspection performance data information1161includes operation-inspection data and security-check data.

The operation-inspection data is test data of the ECUs12to be previously generated at a design stage based on design information. The details will be given later (refer toFIG. 6). The security-check data is test data for inspecting and diagnosing whether operation of the ECUs12is normal or abnormal during actual use. The details will be given later (refer toFIG. 5). Note that, these pieces of data are collectively referred to as inspection data in some cases.

The inspection information acquisition unit112acquires inspection performance result information1162stored in the inspection information management unit116, and transmits the inspection performance result information1162to the service providing server2through the communication unit115. The inspection performance unit113transmits the operation-inspection data and the security-check data to the ECUs12based on an inspection performance request from the inspection performance control unit111.

The inspection monitor unit114monitors and acquires data output from the ECUs12based on the operation-inspection data and the security-check data, and stores the acquired data as the inspection performance result information1162in the inspection information management unit116.

The ECUs12are control devices that control various types of instruments included in the motor vehicle1. Examples of the ECUs12include an engine ECU that performs control of an engine, a transmission ECU that performs control of shift changing, and a brake ECU that adjusts brake oil pressure.

The service providing server2is configured with an inspection plan unit21, an inspection control unit22, an inspection data generation unit23, a dependence analysis unit231, a field structure analysis unit232, an inspection data allocation unit233, an inspection data entry unit24, an inspection result collection unit25, an inspection result analysis unit26, and an inspection service information management unit27.

The inspection plan unit21plans a schedule of an inspection to be performed to the ECUs12, transmits the planned schedule to the terminal having a communication function3owned by a user of the motor vehicle1, receives the schedule approved in the terminal having a communication function3, and stores the schedule in the inspection service information management unit27.

The inspection control unit22collectively controls operation of the inspection data generation unit23, the inspection data entry unit24, the inspection result collection unit25, and the inspection result analysis unit26.

The inspection data generation unit23generates the security-check data, using the dependence analysis unit231, the field structure analysis unit232, and the inspection data allocation unit233, and stores the generated security-check data in the inspection service information management unit27.

The inspection data entry unit24transmits a notification for performing an inspection, to the terminal having a communication function3owned by the user of the motor vehicle1, acquires the security-check data and the operation-inspection data from the inspection service information management unit27, and transmits the pieces of data to the motor vehicle1being an object to be inspected.

When receiving an inspection completion notification from the gateway11, the inspection result collection unit25transmits a collection request for the inspection performance result information1162to the gateway11, and stores the inspection performance result information1162collected from the gateway11, in the inspection service information management unit27.

The inspection result analysis unit26acquires inspection result information280and inspection collation result information281from the inspection service information management unit27, and compares both of the pieces of information so as to analyze whether a signal output from the ECUs12is normal or abnormal.

The inspection service information management unit27includes various types of information (271to281) necessary for operation of the service providing server2. The details of the various types of information will be described later (refer toFIGS. 2 to 14).

The terminal having a communication function3is configured with a screen display unit31, a service performance confirmation unit32, and a communication unit33. The screen display unit31displays the schedule of the inspection planned by the service providing server2, on a display screen, and also displays an inspection result analyzed by the service providing server2, on the display screen. The service performance confirmation unit32performs editing and approval processing for the schedule of the inspection displayed on the display screen.

(2) Table Configuration

The various types of information stored in the inspection service information management unit27of the service providing server2will be described with reference toFIGS. 2 to 12.

FIG. 2illustrates a logical configuration of user information271. The user information271is configured with a user ID column2711, a user PASS column2712, and a user name column2713. The user ID column2711stores identification information of a user who uses the inspection system5. The user PASS column2712stores a password of the user. The user name column2713stores a user name.

FIG. 3illustrates a logical configuration of object-to-be-inspected vehicle information272. The object-to-be-inspected vehicle information272is configured with a user ID column2721, a vehicle identification number (VIN) column2722, a maker column2723, a model column2724, a color column2725, and a vehicle number column2726.

The user ID column2721stores the identification information of the user. The VIN column2722stores identification information for identifying the motor vehicle1being the object to be inspected. The maker column2723stores a maker name of the motor vehicle1. The model column2724stores a model of the motor vehicle1. The color column2725stores a color of the motor vehicle1. The vehicle number column2726stores a vehicle number of the motor vehicle1.

FIG. 4illustrates a logical configuration of object-to-be-inspected ECU information273. The object-to-be-inspected ECU information273is configured with a model column2731, an ECU-ID column2732, an ECU name column2733, an-object-to-be-inspected flag column2734, an inspection period column2735, and a CAN-ID column2736.

The model column2731stores the model of the motor vehicle1being the object to be inspected. The ECU-ID column2732stores identification information for identifying the ECUs12being objects to be inspected. The ECU name column2733stores an ECU name. The object-to-be-inspected flag column2734stores information of whether the ECUs12are objects to be inspected, and, for example, stores “target” or “non-target”.

The inspection period column2735stores an inspection period. The CAN-ID column2736stores identification information of the CAN to which ECUs12being the objects to be inspected, have been coupled.

FIG. 5illustrates a logical configuration of security-check data information274. The security-check data information274is configured with an inspection ID column2741, an ECU-ID column2742, a CAN-ID column2743, and an inspection data column2744.

The inspection ID column2741stores identification information for identifying an inspection with security-check data allocated to each of the ECUs12being the objects to be inspected. The ECU-ID column2742stores identification information for identifying the ECUs12to be objects to be inspected with the security-check data.

The CAN-ID column2743stores identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled. The inspection data column2744stores inspection data and stores, for example, data corresponding to a data field of a CAN protocol.

FIG. 6illustrates a logical configuration of operation-inspection data information275. The operation-inspection data information275is configured with an inspection ID column2751, an ECU-ID column2752, a CAN-ID column2753, and an inspection data column2754, similarly to the security-check data information274.

The inspection ID column2751stores identification information for identifying an inspection with the operation-inspection data allocated to each of the ECUs12being the objects to be inspected. The ECU-ID column2752stores identification information for identifying the ECUs12to be objects to be inspected with the operation-inspection data.

The CAN-ID column2753stores the identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled. The inspection data column2754stores inspection data and stores, for example, data corresponding to a data field of a CAN protocol.

FIG. 7illustrates a logical configuration of schedule information276. The schedule information276is configured with a VIN column2761, a date-and-time column2762, and an inspection ID column2763. The VIN column2761stores the identification information for identifying the motor vehicle1being the object to be inspected.

The date-and-time column2762stores an inspection date and time approved by the user of the motor vehicle1being the object to be inspected. The inspection ID column2763stores identification information for identifying the inspection to be performed to the motor vehicle1.

FIG. 8illustrates a logical configuration of field structure information277. The field structure information277is configured with a model column2771, a CAN-ID column2772, a detailed field ID column2773, a segment ID column2774, and a bit number column2775.

The model column2771stores the model of the motor vehicle1being the object to be inspected. The CAN-ID column2772stores the identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled.

The detailed field ID column2773stores identification information for identifying a segment having a meaning in which the data field of the CAN protocol has been classified in more detail, based on design information of applications of the ECUs12. The segment ID column2774stores identification information for identifying a meaning included in data, based on the design information of the applications of the ECUs12.

For example, the segment ID column2774stores an eigenvalue for identifying a segment of “significant digits, variable data, reservation data, dummy data, or checksums”. The bit number column2775stores the number of bits allocated to detailed field ID.

FIG. 9illustrates a logical configuration of field segment information278. The field segment information278is configured with a segment ID column2781and a segment name column2782. The segment ID column2781stores identification information for identifying a type of data to be used in the data field of the CAN protocol.

The segment name column2782stores a name of the type of data to be used in the data field of the CAN protocol, the name of the type of data corresponding to segment ID. The name of the type of data may be segmented into, for example, “significant digits, variable data, reservation data, dummy data, or checksums”.

FIG. 10illustrates a logical configuration of field dependence information279. The field dependence information279is configured with a model column2791, a CAN-ID column2792, and a detailed field dependence column2793. The model column2791stores the identification information of the motor vehicle1being the object to be inspected. The CAN-ID column2792stores the identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled.

The detailed field dependence column2793stores information indicating processing dependence of the detailed field ID (refer toFIG. 8) in the applications of the ECUs12, based on, for example, away to be used as a condition of branch processing or an argument of a function call in the design information of the applications of the ECUs12. For example, in a case where there is dependence between A1 and A2 in the detailed field ID (refer toFIG. 8), “A1 & A2” is stored with “&”.

FIG. 11illustrates a logical configuration of the inspection result information280. The inspection result information280is configured with a VIN column2801, an inspection result column2802, and performance inspection ID column2803. The VIN column2801stores the identification information for identifying the motor vehicle1being the object to be inspected. The inspection result column2802stores a result of the inspection that has been performed, as a log file. The performance inspection ID column2803stores identification information for identifying the inspection performed to the motor vehicle1.

FIG. 12illustrates a logical configuration of the inspection collation result information281. The inspection collation result information281is configured with a model column2811, a CAN-ID column2812, a performance inspection data column2813, an estimate output data column2814, and a determination result column2815.

The model column2811stores the model of the motor vehicle1being the object to be inspected. The CAN-ID column2812stores the identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled.

The performance inspection data column2813stores inspection data transmitted to the ECUs12. The estimate output data column2814stores data estimated to be output by the ECUs12based on a result of the transmission of the performed inspection data to the ECUs12.

The determination result column2815stores a result determined by comparing the estimate output data and output data being stored in the log file of the inspection result (refer toFIG. 11). For example, in a case where the output data is within a range of the estimate output data, “no abnormality” is stored. In a case where the output data is out of the range of the estimate output data, “abnormality” is stored.

Next, the various types of information stored in the inspection information management unit116of the motor vehicle1, will be described with reference toFIGS. 13 and 14.

FIG. 13illustrates a logical configuration of the inspection performance data information1161. The inspection performance data information1161is configured with a performance order column11611, an inspection ID column11612, a CAN-ID column11613, an inspection data column11614, and a progress column11615.

The performance order column11611stores order in which inspection data stored in the inspection data column11614is transmitted to the ECUs12. The inspection ID column11612stores identification information for identifying the operation-inspection data or the security-check data in association with each of the ECUs12.

The CAN-ID column11613stores the identification information of the CAN to which the ECUs12being the objects to be inspected have been coupled. The inspection data column11614stores the inspection data (the operation-inspection data or the security-check data) to be transmitted to the ECUs12.

The progress column11615stores information of whether the inspection using the inspection data stored in the inspection data column11614has been completed. For example, “completion” is stored with timing with which the inspection data is transmitted to the ECUs12and data output from the ECUs12is acquired.

FIG. 14illustrates a logical configuration of the inspection performance result information1162. The inspection performance result information1162is configured with an inspection ID column11621and an inspection result column11622. The inspection ID column11621stores identification information for identifying the operation-inspection data or the security-check data in association with each of the ECUs12.

The inspection result column11622stores the data output from the ECUs12after the inspection performance unit113transmits the inspection data stored in the inspection data column11614to the ECUs12. For example, a log file including “a date, the inspection data transmitted to the ECUs12, and the data output from the ECUs12”, recorded therein, is stored.

(3) Data Structure

FIG. 15illustrates a data frame structure. The data frame structure is stipulated with ISO15031 of the international organization for standardization.

A start of frame (SOF) field is a field that indicates a start of a data frame. An arbitration field is configured with ID (an identifier) indicating a destination, and a remote transmission request (RTR). The arbitration field is a field that indicates priority of the frame. A controller field is a field that indicates a reservation bit and the number of bytes of data.

Note that, the ID included in the arbitration field is CAN-ID according to the present embodiment. The CAN-ID determines a structure (segments) of the data field to be described later.

The data field is a field that stores a data body. According to the present embodiment, random data is stored in a part of the data field or the entirety thereof so that the security-check data is generated. Note that, the security-check data is generated by the inspection data generation unit23of the service providing server2.

Details of generation processing of the security-check data will be described later (refer toFIG. 24). Here, with the simple descriptions, the inspection data generation unit23first analyzes the structure (the segments) of the data field, and acquires, for example, an analysis result indicating four segments. Next, dependence of each of the segments is analyzed. Finally, based on the dependence, the random data is stored in any of segments having proper inspection efficiency, and then the security-check data is generated.

A CRC field is a field that checks an error of the data frame. An ACK field is a field that indicates a sign of confirmation of reception that has been correctly made. An end of frame (EOF) field is a field that indicates an end of the data frame.

(4) Screen Configuration

FIG. 16illustrates a screen configuration displayed by the screen display unit31of the terminal having a communication function3. The screen is a screen upon editing or approval in the terminal having a communication function3in a case where the service providing server2has transmitted the schedule of the inspection to the terminal having a communication function3.

A user name region311displays a user name registered as the user of the motor vehicle1being the object to be inspected. The user name is acquired from the user name stored in the user name column2713. A maker region312displays the maker name of the motor vehicle1being the object to be inspected. The maker name is acquired from the maker name stored in the maker column2723.

A model region313displays the model of the motor vehicle1being the object to be inspected. The model is acquired from the model stored in the model column2724. A color region314displays the color of the motor vehicle1being the object to be inspected. The color is acquired from the color stored in the color column2725. A vehicle number region315displays the vehicle number of the motor vehicle1being the object to be inspected. The vehicle number is acquired from the vehicle number stored in the vehicle number column2726.

An inspection date and time region316displays the schedule prepared by the inspection plan unit21, to be editable. A performance period region317displays an inspection period. The inspection period is acquired from the inspection period stored in the inspection period column2735. A registration approval button318is a button to be pressed upon approving the inspection to be performed at the inspection date and time displayed on the inspection day and time region316.

(5) Flow Charts

FIG. 17illustrates processing steps of schedule registration processing. The schedule registration processing is performed by the service providing server2and the terminal having a communication function3.

First, the inspection plan unit21of the service providing server2transmits a notification of an inspection approval request (SP1). The notification of the inspection approval request is a notification for requesting transmission of ID and a password. When receiving the notification of the inspection approval request, the service performance confirmation unit32of the terminal having a communication function3transmits the ID and the password input by the user, to the service providing server2(SP2).

Next, when receiving the ID and the password, the inspection plan unit21refers to the user information271and then performs identification processing of the ID and the password (SP3). When the identification processing identifies the ID and the password, the inspection plan unit21refers to the object-to-be-inspected vehicle information272and the object-to-be-inspected ECU information273, prepares one inspection schedule or a plurality of inspection schedules, and transmits a notification of an approval request for the prepared one schedule or the prepared plurality of schedules, to the terminal having a communication function3(SP4).

The notification of the approval request for the one schedule or the plurality of schedules, is a notification for instructing displaying of the one schedule or the plurality of schedules together with the various types of information included in the user information271, the object-to-be-inspected vehicle information272, and the object-to-be-inspected ECU information273. When receiving the notification of the approval request for the one schedule or the plurality of schedules, the screen display unit31displays the one schedule or the plurality of schedules together with the various types of information included in the notification, on the display screen (SP5). Note that, the display screen to be displayed is the display screen described inFIG. 16.

After editing the one schedule or the plurality of schedules as necessary (SP6), the service performance confirmation unit32approves the one schedule or the plurality of schedules by the press of the registration approval button318(SP7). The service performance confirmation unit32transmits the approved one schedule or the approved plurality of schedules, to the service providing server2(SP8). When receiving the one schedule or the plurality of schedules from the terminal having a communication function3, the inspection plan unit21stores the one schedule or the plurality of schedules in the schedule information276(SP9).

The inspection plan unit21transmits a registration completion notification for notifying that the one schedule or the plurality of schedules has been stored and the registration has been completed (SP10). When receiving the registration completion notification, the screen display unit31displays a registration completion screen indicating that the registration has been completed (SP11), and completes the schedule registration processing.

FIG. 18illustrates detailed processing steps of the schedule registration processing on the side of the terminal having a communication function3. Here, the detailed processing steps of the processing performed by the terminal having a communication function3during the schedule registration processing inFIG. 17, will be described.

In wait for the inspection approval request (SP101), the service performance confirmation unit32of the terminal having a communication function3determines whether the notification of the inspection approval request transmitted from the service providing server2has been received (SP102). When the service performance confirmation unit32acquires a negative result with the determination at step SP102, the processing proceeds to step SP101so as to be on standby.

In contrast to this, when acquiring a positive result with the determination at step SP102, the service performance confirmation unit32transmits the ID and the password to the service providing server2. After that, when receiving the notification of the schedule approval request from the service providing server2, the service performance confirmation unit32displays the one schedule or the plurality of schedules together with the various types of information, on the display screen (SP103).

The service performance confirmation unit32determines whether editing operation of the user has instructed the editing of the one schedule or the plurality of schedules (SP104). When the service performance confirmation unit32acquires a negative result with the determination at step SP104, the processing proceeds to step SP106. When acquiring a positive result, the service performance confirmation unit32edits the one schedule or the plurality of schedules (SP105).

Next, the service performance confirmation unit32edits the one schedule or the plurality of schedules in a range of the performance period displayed on the performance period region317, and approves the one schedule or the plurality of schedules by the press of the registration approval button318. The service performance confirmation unit32transmits the approved one schedule or the approved plurality of schedules to the service providing server2(SP106).

In wait for the schedule registration completion (SP107), the service performance confirmation unit32determines whether the registration completion notification has been received (SP108). When the service performance confirmation unit32acquires a negative result with the determination at step SP108, the processing proceeds to step SP107. In contrast to this, when acquiring a positive result with the determination at step SP108, the service performance confirmation unit32displays the registration completion screen on the display screen (SP109), and then completes the schedule registration processing.

FIG. 19illustrates detailed processing steps of the schedule registration processing on the side of the service providing server2. Here, the detailed processing steps of the processing performed by the service providing server2during the schedule registration processing inFIG. 17, will be described.

When completing the identification processing of the ID and the password transmitted from the terminal having a communication function3, the inspection plan unit21of the service providing server2refers to the object-to-be-inspected ECU information273and prepares the one schedule or the plurality of schedules during the “inspection period” (SP111).

Next, the inspection plan unit21acquires the user information271and the object-to-be-inspected vehicle information272(SP112), and then transmits, for example, the user information271together with the prepared one schedule or the prepared plurality of schedules, to the terminal having a communication function3(SP113). Next, in wait for reception of the one schedule or the plurality of schedules approved in the terminal having a communication function3(SP114), the inspection plan unit21determines whether the approved one schedule or the approved plurality of schedules has been received (SP115).

When the inspection plan unit21acquires a negative result with the determination at step SP115, the processing proceeds to step SP114. In contrast to this, when acquiring a positive result with the determination at step SP115, the inspection plan unit21stores the received one schedule or the received plurality of schedules in the schedule information276(SP116). The inspection plan unit21transmits the registration completion notification to the terminal having a communication function3(SP117), and then completes the schedule registration processing.

FIG. 20illustrates a series of processing steps of ECU inspection processing. The ECU inspection processing is performed by the gateway11of the motor vehicle1, the service providing server2, and the terminal having a communication function3.

First, the inspection control unit22of the service providing server2regularly or irregularly refers to the schedule information276, and acquires “date and time” of an inspection schedule so as to check the one schedule or the plurality of schedules (SP21). Next, the inspection control unit22determines whether an inspection to be performed is present (SP22). When the inspection control unit22acquires a negative result, the processing goes back to step SP21. When the inspection control unit22acquires a positive result, the processing proceeds to step SP23.

Next, the inspection control unit22transmits an inspection performance notification to the terminal having a communication function3by the inspection data entry unit24(SP23). When receiving the inspection performance notification, the screen display unit31displays a reminder screen (SP24). Meanwhile, the inspection data entry unit24acquires inspection data from the security-check data information274and the operation-inspection data information275, and transmits the acquired inspection data to the gateway11of the motor vehicle1being the object to be inspected (SP25).

When receiving the inspection data, the inspection performance control unit111of the gateway11stores the received inspection data in the inspection performance data information1161(SP26). Next, the inspection performance control unit111confirms a vehicle state of the motor vehicle1(SP27). In a case where the motor vehicle1is not on standby (SP28: N), the inspection performance control unit111determines that the state is not inspectable, and then the processing proceeds to step SP27.

Note that, on standby means that the motor vehicle1is in a stopped state and a certain period of time also has passed. In a state where the motor vehicle1is on standby (SP28: Y), the inspection performance control unit111acquires the inspection data stored in the inspection performance data information1161, and the inspection performance unit113transmits the acquired inspection data to the ECUs12(SP29).

Next, the inspection performance control unit111acquires data output from the ECUs12by the inspection monitor unit114, in particular, captures a packet (SP30), and stores the captured packet in the inspection performance result information1162.

Next, the inspection performance control unit111confirms whether inspection data to be transmitted to the ECUs12remains in the inspection performance data information1161(SP31). In a case where the inspection data remains, the processing proceeds to step SP28. In a case where no inspection data remains, the processing proceeds to step SP32. Note that, in a case where the inspection has not been completed even when a certain period of time has passed, the service providing server2may be notified of a warning.

In a case where no inspection data to be transmitted to the ECUs12remains, the inspection performance control unit111transmits an inspection result completion notification indicating that the inspection has been completed, to the service providing server2(SP32). When receiving the inspection result completion notification, the inspection control unit22of the service providing server2transmits a notification of an inspection result collection request, to the gateway11by the inspection result collection unit25(SP33).

When receiving the notification of the inspection result collection request, the inspection information acquisition unit112of the gateway11acquires the inspection performance result information1162(SP34), and then transmits the acquired inspection performance result information1162to the service providing server2(SP35). When receiving the inspection performance result information1162, the inspection result collection unit25of the service providing server2stores the inspection performance result information1162in the inspection result information280(SP36).

Next, the inspection result analysis unit26refers to the inspection result information280and the inspection collation result information281, and compares an output result actually output from the ECUs12and an output result being estimated so as to analyze the inspection result information280(SP37), determines the analysis result (SP38), and stores the determined result in the inspection collation result information281.

The inspection control unit22transmits the determined result to the terminal having a communication function3(SP39). Note that, the determined result may be transmitted to, for example, a dealer and a motor vehicle maker other than the terminal having a communication function3. When receiving the determined result, the screen display unit31of the terminal having a communication function3displays the determined result, as an inspection result, on the display screen (SP40). As described above, the series of processing of the ECU inspection processing is completed.

FIG. 21illustrates detailed processing steps of the ECU inspection processing on the side of the terminal having a communication function3. Here, the detailed processing steps of the processing performed by the terminal having a communication function3during the ECU inspection processing inFIG. 20, will be described.

In wait for the inspection performance notification (SP201), the service performance confirmation unit32of the terminal having a communication function3determines whether the inspection performance notification transmitted from the service providing server2has been received (SP202). When the service performance confirmation unit32acquires a negative result with the determination at step SP202, the processing proceeds to step SP201.

In contrast to this, when acquiring a positive result with the determination at step SP202, the service performance confirmation unit32displays the remainder screen on the display screen (SP203). Next, the service performance confirmation unit32determines whether the determined result transmitted from the service providing server2has been received (SP204). When acquiring a negative result with the determination at step SP204, the service performance confirmation unit32remains on standby until the determined result is received.

In contrast to this, when acquiring a positive result with the determination at step SP204, the service performance confirmation unit32displays the inspection result on the display screen by the screen display unit31(SP205), and then completes the ECU inspection processing.

FIG. 22illustrates detailed processing steps of the ECU inspection processing on the side of the service providing server2. Here, the detailed processing steps of the processing performed by the service providing server2during the ECU inspection processing inFIG. 20, will be described.

Based on an instruction from the inspection control unit22, the inspection data entry unit24of the service providing server2regularly or irregularly refers to the schedule information276, and acquires the “date and time” of the inspection schedule so as to check the one schedule or the plurality of schedules (SP211). The inspection data entry unit24determines whether the inspection to be performed is present (SP212).

When the inspection data entry unit24acquires a negative result with the determination at step SP212, the processing proceeds to step SP211. In contrast to this, when acquiring a positive result with the determination at step SP212, the inspection data entry unit24transmits the inspection performance notification to the terminal having a communication function3(SP213).

Next, the inspection data entry unit24acquires the inspection data from the security-check data information274and the operation-inspection data information275, and transmits the inspection data to the gateway11of the motor vehicle1being the object to be inspected (SP214).

Next, in wait for the inspection result completion notification (SP215), the inspection control unit22determines whether the inspection result completion notification transmitted from the gateway11has been received (SP216). When the inspection control unit22acquires a negative result with the determination at step SP216, the processing proceeds to step SP215.

In contrast to this, when acquiring a positive result with the determination at step SP216, the inspection control unit22transmits the notification of the inspection result collection request, to the gateway11by the inspection result collection unit25(SP217). Next, in wait for the inspection result collection (SP218), the inspection result collection unit25determines whether the inspection performance result information1162transmitted from the gateway11has been received (SP219).

When the inspection result collection unit25acquires a negative result with the determination at step SP219, the processing proceeds to step SP218. In contrast to this, when acquiring a positive result with the determination at step SP219, the inspection result collection unit25stores the received inspection performance result information1162in the inspection result information280.

The inspection result analysis unit26refers to the inspection result information280and the inspection collation result information281, and compares the output result actually output from the ECUs12and the output result being estimated so as to analyze the inspection result (SP220). The inspection result analysis unit26determines no abnormality in a case where the output result is as estimated, and determines abnormality in a case where the output result is not as estimated (SP221).

The inspection control unit22transmits the determined result to the terminal having a communication function3(SP222) and then completes the ECU inspection processing.

FIG. 23illustrates detailed processing steps of the ECU inspection processing on the side of the gateway11of the motor vehicle1. Here, the detailed processing steps of the processing performed by the gateway11during the ECU inspection processing inFIG. 20, will be described.

In wait for a processing request from the service providing server2(SP231), the inspection performance control unit111of the gateway11determines whether the processing request is present (SP232). When the inspection performance control unit111acquires a negative result with the determination at step SP232, the processing proceeds to step SP231. When acquiring a positive result, the inspection performance control unit111determines a processing description (SP233).

In a case where the processing description includes an inspection performance request, namely, in a case where the inspection data has been received from the service providing server2, the inspection performance control unit111stores the received inspection data in the inspection performance data information1161(SP234). Next, the inspection performance control unit111confirms the vehicle state of the motor vehicle1(SP235), and determines whether the motor vehicle1is on standby (SP236).

In a case where the motor vehicle1is on standby (SP236: Y), the inspection performance control unit111generates a message corresponding to the CAN protocol, based on the “CAN-ID” and the “inspection data” of the inspection performance data information1161, and transmits the generated message to the ECUs12by the inspection performance unit113(SP237).

Next, the inspection performance control unit111acquires the data output from the ECUs12by the inspection monitor unit114, in particular, captures the packet, and stores the captured packet in the inspection performance result information1162(SP238). Next, the inspection performance control unit111updates the “progress” of the inspection performance data information1161to “completion” (SP239).

Next, the inspection performance control unit111refers to the “progress” of the inspection performance data information1161and confirms whether an item in which “completion” has not been made is present, so as to confirm whether inspection data to be transmitted to the ECUs12remains in the inspection performance data information1161(SP240).

When the inspection performance control unit111acquires a negative result with the determination at step SP240, the processing proceeds to step SP236. When acquiring a positive result, the inspection performance control unit111transmits the inspection result completion notification to the service providing server2(SP243), and then completes the ECU inspection processing.

Referring back to step SP236, in a case where the motor vehicle1is not on standby (SP236: N), the processing may wait until a standby state is made. However, the inspection temporarily suspends here (SP241), and a suspension notification indicating the suspension is transmitted to the service providing server2(SP243). Then, the ECU inspection processing is completed.

Referring back to step SP233, in a case where the processing description includes the inspection result collection request, namely, in a case where the notification of the inspection result collection request has been received from the service providing server2, the inspection performance control unit111acquires the inspection performance result information1162by the inspection information acquisition unit112(SP242), transmits the inspection performance result information1162to the service providing server2(SP243), and then completes the ECU inspection processing.

FIG. 24illustrates processing steps of security-check data generation processing. The security-check data generation processing is performed by the service providing server2during the ECU inspection processing (refer toFIG. 20) or with arbitrary timing before the ECU inspection processing.

First, the inspection data generation unit23of the service providing server2refers to the object-to-be-inspected ECU information273, and acquires “ECU-ID” including “target” in the “object-to-be-inspected flag” as ECU-ID being an object t to be inspected (SP31). Next, the inspection data generation unit23acquires “CAN-ID” corresponding to the ECU-ID specified as the object to be inspected (SP32).

Next, the inspection data generation unit23refers to the field structure information277, and acquires “detailed field ID” and “the number of bits” corresponding to the CAN-ID acquired at step SP32so as to analyze the field structure of the data field (refer toFIG. 15), by the field structure analysis unit232(SP33).

For example, the field structure analysis unit232refers to the field structure information277, and acquires pieces of detailed field ID of “A1”, “A2”, “A3”, and “A4” corresponding to the CAN-ID including “0x7E0” in a case where the CAN-ID acquired at step SP32is “0x7E0”.

The field structure analysis unit232acquires each of the number of bits of “8 bits”, “8 bits”, “16 bits”, and “32 bits” corresponding to the pieces of detailed field ID of “A1” to “A4”, respectively. As a result, the field structure analysis unit232can acquire an analysis result including the data field structure segmented into four, such as “A1” to “A4”, and the respective segments being “8 bits”, “8 bits”, “16 bits”, and “32 bits”.

Note that, the field structure analysis unit232refers to the field structure information277so as to acquire pieces of segment ID of “D1”, “D2”, “D2”, and “D4” corresponding to the pieces of detailed field ID of “A1” to “A4”, respectively. The field structure analysis unit232refers to the field segment information278so as to acquire segment names of “significant digits”, “variable data”, and “dummy” corresponding to “D1”, “D2”, and “D4”. As a result, a meaning indicated by the data stored in “A1” to “A4”, can be analyzed.

Next, the inspection data generation unit23refers to the field dependence information279and acquires “detailed field dependence” corresponding to the CAN-ID acquired at step SP32, by the dependence analysis unit231(SP34).

For example, the dependence analysis unit231refers to the field dependence information279, and acquires dependence of {A1, (A2 & A3), A4} corresponding to the CAN-ID of “0x7E0” in a case where the CAN-ID acquired at step SP32is “0x7E0”. In this case, there is dependence between the data stored in the segment of “A2” and the data stored in the segment of “A3”.

Next, the inspection data generation unit23determines an allocation number of random data by the inspection data allocation unit233, based on “the number of bits” acquired at step SP33and the “detailed field dependence” acquired at step SP34(SP35).

For example, the inspection data generation unit23allocates the random data to a position at which a more effective inspection can be achieved in the data field, in terms of inspection efficiency, instead of allocating the random data to all the data field totally including 64 bits. Here, since there is the dependence between “A2” and “A3”, and “A2” and “A3” are “8 bits” and “16 bits”, respectively, the inspection data generation unit23determines the allocation number of the random data to be 24 bits.

Note that, the inspection data generation unit23may determine the allocation number of the random data per dependence unit as described above, or may determine the allocation number of the random data in accordance with priority corresponding to characteristics of the “segment ID” of the field segment information278. For example, the random data may be allocated to “A1” and fixed data may be allocated to “A2” to “A4”.

Next, based on the allocation number of the data determined at step SP35, the inspection data generation unit23determines a range in which the random data is used, and generates inspection data by the inspection data allocation unit233(SP36). The inspection data generation unit23stores the generated data in the security-check data information274(SP37).

Next, the inspection data generation unit23determines whether dependence including no inspection data generated remains in the dependence acquired at step SP34(SP38). When the inspection data generation unit23acquires a negative result with the determination at step SP38, the processing proceeds to step SP36. When receiving a positive result, the inspection data generation unit23completes the security-check data generation processing.

(6) Effect According to the Present Embodiment

As described above, the inspection system5according to the present embodiment, transmits the security-check data considered not to be received by the ECUs12at the design stage of the ECUs12, to the ECUs12, together with the operation-inspection data previously prepared at the design stage of the ECUs12, and determines whether the data output from the ECUs12is in a proper range. Therefore, the operation of the ECUs12during the use can be accurately inspected.

(7) Another Embodiment

According to the present embodiment described above, the inspection result analysis unit26of the service providing server2refers to the inspection result information280and the inspection collation result information281, analyzes the inspection result information280, and determines the analysis result (refer to SP37and SP38inFIG. 20). However, the present embodiment is not limited to this. A gateway11of a motor vehicle1may include an inspection result analysis unit26and inspection collation result information281. The gateway11may refer to inspection performance data information1161and the inspection collation result information281, may analyze the inspection performance data information1161, and may determine the analysis result, by the inspection result analysis unit26.

FIG. 25illustrates processing steps of ECU inspection processing according to another embodiment. The ECU inspection processing according to the other embodiment is different from the ECU inspection processing according to the present embodiment described above (FIG. 20) in that the gateway11analyzes an inspection result (SP31A) and determines the analysis result (SP32A) and in that the gateway11acquires the determined result (SP36A) and transmits the determined result to a service providing server2(or directly to a terminal having a communication function3) (SP37A).

REFERENCE SIGNS LIST