NETWORK CONFIGURATION ESTIMATION DEVICE, NETWORK CONFIGURATION ESTIMATION METHOD, AND PROGRAM

The network configuration estimation device uses standard diagnostic communication to estimate in-vehicle network topology and ECU information, addressing the cost issue of existing methods by leveraging existing protocols, thus enhancing cyberattack detection and management.

JP7593406B2Active Publication Date: 2024-12-03NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022550459
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-09-18
Filing Date
2021-09-02
Publication Date
2024-12-03
Estimated Expiration
2041-09-02

AI Technical Summary

Technical Problem

Existing methods for estimating the configuration of in-vehicle networks require additional resources and support for new protocols, such as SNMP, leading to increased costs.

Method used

A network configuration estimation device that utilizes standard diagnostic communication methods, like UDS and DoIP, to collect and analyze information from electronic control units (ECUs) without the need for additional protocols, enabling estimation of network topology and ECU information.

Benefits of technology

Enables accurate estimation of in-vehicle network configuration without increasing resources or supporting new protocols, facilitating cyberattack detection and management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007593406000001
    Figure 0007593406000001
  • Figure 0007593406000002
    Figure 0007593406000002
  • Figure 0007593406000003
    Figure 0007593406000003
Patent Text Reader

Abstract

This network configuration estimating device for estimating configuration information relating to an internal network of a target device is provided with: a diagnostic communication transmitting and receiving unit which uses a diagnostic communication method that is supported as standard by an electronic control device on the internal network to transmit a message to the electronic control device on the internal network and to receive a response with respect to the message; and a configuration information estimating unit which estimates the configuration information relating to the internal network on the basis of the response obtained by the diagnostic communication transmitting and receiving unit.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technique for estimating configuration information of an internal network in a target device such as an automobile. [Background technology]

[0002] In recent years, the threat of cyber attacks on automobiles has increased with the advent of the connected car society. In other words, the connected functions installed in automobiles allow automobiles to connect to the outside world through networks, which in turn increases the threat of cyber attacks from the outside.

[0003] Therefore, it is important to detect cyber attacks on automobiles, identify the route and cause of the attack, and implement post-attack measures to deal with the attack.In order to accurately identify the route and cause of the attack, information on the configuration (topology) of the in-vehicle network (NW) and information processing devices (IVI, TCU, etc.) and electronic control units (ECUs) on the NW is required.

[0004] In addition to the above, vehicle configuration information is also necessary to achieve various other purposes, such as asset management and configuration anomaly detection.

[0005] A conventional technique for estimating the configuration of a network is, for example, the technique disclosed in Non-Patent Document 1. The technique disclosed in Non-Patent Document 1 uses SNMP to acquire the MAC address forwarding table of each switch in a target network, and estimates the L2 topology of the target network by analyzing the acquired information. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] Jing Jiang, Xiao Xu, Ning Cao, "Research on improved physical topology discovery based on SNMP," In 2017 IEEE International Conference on Computational Science and Engineering (CSE) and IEEE Conference on Embedded and Ubiquitous Computing (EUC), pp.219-222, (2017). Summary of the Invention [Problem to be solved by the invention]

[0007] In order to acquire information on the topology of an in-vehicle network and each ECU, it is possible to use the SNMP-based method disclosed in Non-Patent Document 1. However, in order to acquire information on the topology of an in-vehicle network and each ECU using the SNMP-based method, it is necessary to increase resources and support SNMP to enable the operation of an SNMP agent for each ECU, which causes a problem of additional costs.

[0008] The present invention has been made in consideration of the above points, and aims to provide a technology that makes it possible to estimate configuration information of an internal network in a target device without increasing resources or supporting new protocols for the components of the internal network. [Means for solving the problem]

[0009] According to the disclosed technology, there is provided a network configuration estimation device that estimates configuration information of an internal network in a target device, comprising: A diagnostic communication transmitting / receiving unit that transmits a message to an electronic control unit on the internal network by using a diagnostic communication method supported as a standard by the electronic control unit on the internal network and receives a response to the message; The response obtained by the diagnostic communication transmitting / receiving unit; How to connect a configuration information estimation unit that estimates the configuration information including a topology of the internal network based on publicly known information; There is provided a network configuration estimation device comprising: Effect of the Invention

[0010] According to the disclosed technique, it is possible to estimate configuration information of an internal network in a target device without increasing resources or supporting new protocols for the components of the internal network. [Brief description of the drawings]

[0011] [Figure 1] FIG. 4 is a diagram showing an example of vehicle-mounted configuration information. [Diagram 2] FIG. 11 is a diagram for explaining an example of diagnostic communication. [Diagram 3] FIG. 1 illustrates an example of a configuration of a configuration information estimation system according to a first embodiment. [Figure 4] 10 is a flowchart illustrating an example of a processing procedure of a diagnostic communication transmitting / receiving unit. [Diagram 5] 13 is a flowchart illustrating an example of a processing procedure of a configuration information estimation unit. [Figure 6] FIG. 1 is a system configuration diagram of a first embodiment of the present invention. [Figure 7] FIG. 11 is a system configuration diagram of Example 2 in the first embodiment. [Figure 8] FIG. 11 is a system configuration diagram of Example 3 in the first embodiment. [Figure 9] FIG. 11 is a system configuration diagram of Example 4 in the first embodiment. [Figure 10] FIG. 11 is a system configuration diagram of a fifth embodiment of the first embodiment. [Figure 11] FIG. 13 is a system configuration diagram of Example 6 in the first embodiment. [Figure 12] FIG. 4 is a diagram showing an example of vehicle configuration information. [Figure 13] FIG. 11 is a diagram showing an automobile network that is the premise of a second embodiment. [Figure 14] FIG. 1 is a diagram for explaining a goal of elemental technology 1. [Figure 15] FIG. 1 is a diagram for explaining an application target of elemental technology 1. [Figure 16] FIG. 13 is a diagram for explaining the RTT of diagnostic communication. [Figure 17] FIG. 1 is a diagram for explaining an estimation method of elemental technology 1. [Figure 18] FIG. 1 is a diagram for explaining an estimation procedure of elemental technology 1. [Figure 19] FIG. 1 is a diagram for explaining an estimation procedure of elemental technology 1. [Figure 20] FIG. 1 is a diagram for explaining an estimation procedure of elemental technology 1. [Figure 21] FIG. 1 is a diagram for explaining the goal of elemental technology 2. [Figure 22] This is a diagram for explaining the key points and procedures of elemental technology 2. [Figure 23] FIG. 13 is a diagram for explaining a conventional technique related to elemental technique 3. [Figure 24] FIG. 1 is a diagram for explaining the goal of elemental technology 3. [Diagram 25] FIG. 13 is a diagram for explaining the estimation method of elemental technology 3. [Figure 26] FIG. 13 is a diagram for explaining the estimation method of elemental technology 3. [Figure 27] FIG. 13 is a configuration diagram of Example A1 in the second embodiment. [Figure 28] 13 is a flowchart showing the overall process of Example A1 in the second embodiment. [Figure 29] 13 is a flowchart showing the process of S1030 in Example A1 in the second embodiment. [Diagram 30] 13 is a flowchart showing the process of S1031 of Example A1 in the second embodiment. [Diagram 31]FIG. 3031 of Example A1 in the second embodiment. [Diagram 32] 13 is a flowchart showing the process of S1032 of Example A1 in the second embodiment. [Diagram 33] 13 is a flowchart showing the process of S1033 of Example A1 in the second embodiment. [Diagram 34] FIG. 3032 of Example A1 in the second embodiment. [Diagram 35] 13 is a flowchart showing the process of S1034 in Example A1 of the second embodiment. [Diagram 36] FIG. 3033 of Example A1 in the second embodiment. [Figure 37] 13 is a flowchart showing the process of S1035 of Example A1 in the second embodiment. [Figure 38] FIG. 3034 of Example A1 in the second embodiment. [Figure 39] FIG. 3035 of Example A1 in the second embodiment. [Diagram 40] FIG. 3036 of Example A1 in the second embodiment. [Diagram 41] 13 is a flowchart showing the process of S1036 in Example A1 in the second embodiment. [Diagram 42] FIG. 3037 of Example A1 in the second embodiment. [Diagram 43] 13 is a flowchart showing the process of S1037 of Example A1 in the second embodiment. [Diagram 44] 13 is a flowchart showing the process of S1038 of Example A1 in the second embodiment. [Diagram 45] FIG. 3038 of Example A1 in the second embodiment. [Diagram 46] 13 is a flowchart showing the process of S1039 of Example A1 in the second embodiment. [Figure 47]FIG. 3039 of Example A1 in the second embodiment. [Figure 48] 13 is a flowchart showing the process of S1040 in Example A1 in the second embodiment. [Figure 49] 13 is a flowchart showing the process of S1061 of Example A1 in the second embodiment. [Figure 50] FIG. 3081 of Example A1 in the second embodiment. [Figure 51] 13 is a flowchart showing the process of S1091 of Example A1 in the second embodiment. [Figure 52] 13 is a flowchart showing the process of S1101 of Example A1 in the second embodiment. [Diagram 53] 13 is a flowchart showing the process of S1111 of Example A1 in the second embodiment. [Figure 54] FIG. 3111 of Example A1 in the second embodiment. [Figure 55] 13 is a table to be referred to when explaining the sum of the support degrees of Example A1 in the second embodiment. [Figure 56] FIG. 3112 of Example A1 in the second embodiment. [Figure 57] FIG. 3113 of Example A1 in the second embodiment. [Figure 58] 13 is a flowchart showing the process of S1120 in Example A1 of the second embodiment. [Figure 59] 13 is a flowchart showing the process of S1121 of Example A1 in the second embodiment. [Figure 60] FIG. 13 is a diagram showing an example of a trace route record of Example A1 in the second embodiment. [Figure 61] 13 is a flowchart showing the process of S1122 of Example A1 in the second embodiment. [Figure 62] FIG. 13 is a diagram showing one-to-one correspondence between ECU model numbers and physical ECUs in Example A1 in the second embodiment. [Figure 63] FIG. 13 is a diagram showing the settings of a network interface of Example A1 in the second embodiment. [Figure 64] FIG. 13 is a diagram showing allocation of ECU information in Example A1 in the second embodiment. [Figure 65] FIG. 13 is a diagram showing a connection relationship in Example A1 in the second embodiment. [Figure 66] 13 is a flowchart showing the process of S1130 in Example A1 of the second embodiment. [Figure 67] 13 is a flowchart showing the process of S1141 of Example A1 in the second embodiment. [Figure 68] FIG. 13 is a diagram showing records of transmission times and reception times in Example A1 in the second embodiment. [Figure 69] FIG. 3141 of Example A1 in the second embodiment. [Figure 70] 13 is a flowchart showing the process of S1151 of Example A1 in the second embodiment. [Figure 71] 13 is a flowchart showing the process of S1152 of Example A1 in the second embodiment. [Figure 72] FIG. 13 is a diagram showing records of transmission times and reception times in Example A1 in the second embodiment. [Figure 73] FIG. 3151 of Example A1 in the second embodiment. [Figure 74] 13 is a flowchart showing the process of S1161 of Example A1 in the second embodiment. [Figure 75] FIG. 3161 of Example A1 in the second embodiment. [Figure 76] FIG. 3162 of Example A1 in the second embodiment. [Figure 77] 13 is a flowchart showing the process of S1171 of Example A1 in the second embodiment. [Figure 78] FIG. 13 is a diagram showing one-to-one correspondence between ECU model numbers and physical ECUs in Example A1 in the second embodiment. [Figure 79] FIG. 13 is a diagram showing adding a requested NW_A-ID to an ECU of example A1 in the second embodiment. [Figure 80] 13 is a flowchart showing the process of S1172 of Example A1 in the second embodiment. [Figure 81] FIG. 13 is a diagram showing an estimation result of the NW_A topology of Example A1 in the second embodiment. [Figure 82] FIG. 13 is a diagram showing the addition of EUC information to the NW_A topology of example A1 in the second embodiment. [Figure 83] FIG. 13 is a diagram illustrating a connection between GWs of example A1 in the second embodiment. [Figure 84] 13 is a flowchart showing the process of S1180 in Example A1 in the second embodiment. [Figure 85] 13 is a flowchart showing the process of S1191 of Example A1 in the second embodiment. [Figure 86] 13 is a flowchart showing the process of S1192 in Example A1 of the second embodiment. [Figure 87] FIG. 13 is a diagram showing a record of ECURese transmission time of Example A1 in the second embodiment. [Figure 88] 13 is a flowchart showing the process of S1201 of Example A1 in the second embodiment. [Figure 89] FIG. 13 is a diagram showing records of alert issuance times of NW_A-IDS in Example A1 in the second embodiment. [Figure 90] 13 is a flowchart showing the process of S1211 of Example A1 in the second embodiment. [Figure 91] FIG. 3211 of Example A1 in the second embodiment. [Figure 92] FIG. 13 is a diagram showing a result after adding Example A1 in the second embodiment. [Figure 93] FIG. 3212 of Example A1 in the second embodiment. [Figure 94]FIG. 11 is a configuration diagram of Example A2 in the second embodiment. [Figure 95] FIG. 11 is a configuration diagram of Example A3 in the second embodiment. [Figure 96] FIG. 13 is a configuration diagram of Example A4 in the second embodiment. [Figure 97] FIG. 11 is a configuration diagram of Example A5 in the second embodiment. [Figure 98] FIG. 11 is a configuration diagram of Example A6 in the second embodiment. [Figure 99] FIG. 13 is a configuration diagram of Example A7 in the second embodiment. [Figure 100] FIG. 13 is a configuration diagram of Example B1 in the second embodiment. [Figure 101] FIG. 13 is a configuration diagram of Example B2 in the second embodiment. [Figure 102] FIG. 13 is a configuration diagram of Example B3 in the second embodiment. [Figure 103] FIG. 13 is a configuration diagram of Example B4 in the second embodiment. [Figure 104] FIG. 13 is a configuration diagram of Example C1 in the second embodiment. [Figure 105] FIG. 13 is a configuration diagram of Example C2 in the second embodiment. [Fig. 106] FIG. 13 is a configuration diagram of Example C3 in the second embodiment. [Figure 107] FIG. 13 is a configuration diagram of Example C4 in the second embodiment. [Figure 108] FIG. 2 illustrates an example of a hardware configuration of the apparatus. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention (the present embodiment) will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0013] In the present embodiment (first and second embodiments) described below, an automobile is taken as an example of a target device having an internal network for which configuration information is to be estimated, but the target device to which the technology according to the present invention can be applied is not limited to an automobile. The technology according to the present invention can be applied to a target device that has the characteristic of being able to obtain information from devices on a network by diagnostic communication, just like an automobile. Furthermore, the elemental technology described in the second embodiment can be applied to at least those that meet the conditions described in the applicable target.

[0014] In this embodiment, the configuration of the in-vehicle network (NW), information about information processing devices (IVI, TCU, etc.) on the NW, and information about the electronic control unit (ECU) may be collectively referred to as "vehicle configuration information." "Vehicle configuration information" is an example of "internal network configuration information."

[0015] Additionally, TCU is an abbreviation for Telematics Control Unit, IVI is an abbreviation for In-Vehicle Infotainment, and ECU is an abbreviation for Electronic Control Unit.

[0016] In the following description (and drawings), CAN (registered trademark) is referred to as NW_A (network A), and Ethernet (registered trademark) is referred to as NW_B (network B). Note that CAN (registered trademark) is an abbreviation for Controller Area Network.

[0017] However, NW_A appearing in the following description may be a network other than CAN (registered trademark), and NW_B may be a network other than Ethernet (registered trademark). For example, NW_A may be FlexRay (registered trademark), LIN, K-Line, etc.

[0018] In this embodiment, a method for estimating configuration information of a network of a target vehicle will be described. The configuration information of the network of a target vehicle is, for example, the following information.

[0019] Topology of the target network (vehicle-mounted NW_B and vehicle-mounted NW_A) Information about devices connected to the network (e.g. model number, software version, etc.) Information on the function (=name) of each device - Information on normal communications performed by each device (especially information on normal communications sent by each device) A first embodiment and a second embodiment of the present invention will be described below. In the first embodiment, a basic configuration and operation will be described, and in the second embodiment, a more specific configuration and operation will be described. The configuration and processing described in the first embodiment and the configuration and processing described in the second embodiment can be implemented in combination. ------------------First embodiment--------------------------------

[0020] (Example of vehicle configuration information) In this embodiment, the configuration information estimation system estimates vehicle configuration information of an automobile. An example of vehicle configuration information is shown in Fig. 1. In the example of Fig. 1, the TCU and IVI connected to NW_B are connected to GW (Gateway-ECU) in a star topology. NW_A is also connected to GW, and ECUs connected to NW_A are connected to NW_A under GW in a bus topology. Information on each ECU, etc. is also shown in Fig. 1. OBD-II shown in Fig. 1 is a self-diagnosis function.

[0021] In the following description, the information processing device (IVI, TCU, etc.) and the electronic control device (ECU) are collectively referred to as "ECU." This also applies to the second embodiment.

[0022] (About diagnostic communication) In this embodiment, the configuration information estimation system estimates vehicle configuration information by collecting and analyzing information obtained through diagnostic communication that is supported as standard in devices such as ECUs mounted on automobiles. Note that diagnostic communication is implemented in almost all automobiles and ECUs. This section describes this diagnostic communication.

[0023] Diagnostic communication is used when diagnosing faults and reprogramming the ECU. In addition, diagnostic communication can also obtain information such as the ECU model number and software version. An example of the diagnostic communication procedure will be described with reference to Figure 2. Figure 2 shows an example of diagnostic communication between an external diagnostic device_A and an ECU_B.

[0024] In S1, a diagnosis request is sent from the external diagnostic device_A to the ECU_B. In S2, the ECU_B executes processing corresponding to the diagnosis request. In S3, the ECU_B sends a diagnosis response to the external diagnostic device_A. The diagnosis response includes the results of the processing, etc.

[0025] (System Configuration) Fig. 3 shows an example of the configuration of a configuration information estimation system according to this embodiment. As shown in Fig. 3, the configuration information estimation system according to this embodiment has a diagnostic communication transmitting / receiving unit 100, a diagnostic log DB 200, and a configuration information estimation unit 300. The configuration information estimation unit 300 has an ECU presence confirmation unit 310, a topology estimation unit 320, an ECU information extraction unit 330, and an output unit 340. An overview of each functional unit is as follows.

[0026] The diagnostic communication transmitting / receiving unit 100 transmits and receives diagnostic communication in accordance with a flow chart described later, and stores the received response in the diagnostic log DB 200 .

[0027] The diagnostic log DB 200 is a DB (database) that stores logs acquired by the diagnostic communication transmitting / receiving unit 100 in a predetermined format.

[0028] The configuration information estimation unit 300 estimates vehicle configuration information using information stored in the diagnostic log DB 200 by operating each internal block according to a flow diagram described later. Note that information other than diagnostic logs may be used as input to the configuration information estimation unit 300. For example, publicly known information related to the configuration or non-diagnostic logs may be used.

[0029] As described in the following embodiments 1 to 6, the diagnostic communication transmitting / receiving unit 100, the diagnostic log DB 200, and the configuration information estimating unit 300 can be implemented in one or more devices in various forms. A device including the diagnostic communication transmitting / receiving unit 100 and the configuration information estimating unit 300 may be called a network configuration estimating device. In this network configuration estimating device, the diagnostic communication transmitting / receiving unit 100 and the configuration information estimating unit 300 may be located at remote locations and communicate with each other via a network.

[0030] Moreover, a device including a configuration information estimation unit 300 that estimates configuration information by utilizing a response obtained by the diagnostic communication transmitting / receiving unit 100 may be called a network configuration estimation device.

[0031] (Operation of diagnostic communication transceiver) Next, a description will be given of an example of the operation of the diagnostic communication transmitting / receiving unit 100. First, a description will be given of UDS, DID, and DoIP which appear in the flow described later.

[0032] UDS is an abbreviation for Unified Diagnostic Services, and is the name of a standard specification (such as ISO14229-1) that defines the format of diagnostic messages in diagnostic communications.

[0033] DID is an abbreviation for Data ID. It is an ID set in a UDS diagnostic request (request message) and indicates the target of the diagnostic service. For example, when a diagnostic request in which a DID specifying a software version number is set is sent to an ECU, the ECU returns a diagnostic response (response message) in which the software version number is set.

[0034] In addition, there is ISO15765-2, known as DoCAN (Diagnostic communication over Controller Area Network), which is a standard specification that defines the network layer specifications for implementing UDS on NW-A.

[0035] DoIP is an abbreviation for Diagnostic communication over Internet Protocol, and is the name of a set of standard specifications (ISO 13400-1, ISO 13400-2) that stipulate the network layer specifications for implementing UDS on IP.

[0036] In DoIP, for example, as shown in Figure 1, only the ECU that serves as a gateway to the diagnostic function (tester) and ECUs that require particularly high-speed data transfer communicate via NW_B, while the other ECUs are connected to the gateway ECU via in-vehicle networks such as NW_A, and diagnosis is performed via this gateway ECU.

[0037] The diagnostic communication transmitting / receiving unit 100 and the ECU in this embodiment perform diagnostic communication that complies with at least the above-mentioned general standard specifications.

[0038] An example of the operation of the diagnostic communication transmitting / receiving unit 100 will be described with reference to the flowchart of Fig. 4. Note that the contents and order of messages transmitted and received in the example of the operation described with reference to Fig. 4 are merely examples, and are not limited to these.

[0039] In S101, the diagnostic communication transmitting / receiving unit 100 broadcasts a DoIP Vehicle Identification Request to the ECUs connected to the NW_B and receives responses from each ECU. The Vehicle Identification Request is a message requesting address information from the ECUs connected to the NW_B.

[0040] In S102, the diagnostic communication transmitting / receiving unit 100 transmits a UDS testerPresent to each ECU connected to the NW_A and receives a response. The testerPresent is a message for confirming the presence of the ECU connected to the NW_A and its NW_A-ID (i.e., CAN-ID).

[0041] In S103, the diagnostic communication transmitting / receiving unit 100 transmits an Entity Status Request of DoIP to each ECU connected to the in-vehicle NW_B and receives a response. The Entity Status Request is a message requesting the ECU to provide a node type (e.g., a gateway) and the like.

[0042] In S104, the diagnostic communication transmitting / receiving unit 100 transmits a UDS ReadDataByIdentifier with a value of 1 or more set as a DID to each ECU connected to the in-vehicle NW_B and NW_A, and receives a response. The ReadDataByIdentifier is a message requesting the ECU to provide data specified by the DID.

[0043] The DIDs used in S104 are, for example, 0xF181, 0xF183, 0xF184, 0xF188, 0xF189, 0xF18A, 0xF194, 0xF195, 0xF19F, 0xF18B, 0xF18C, 0xF184, 0xF191, 0xF192, 0xF193, and 0xF19F. However, these are examples and are not limited to these.

[0044] 0xF181 indicates an applicationSoftwareIdentificationDataIdentifier. 0xF183 indicates a bootSoftwareFingerprintDataIdentifier. 0xF184 indicates an applicationSoftwareFingerprintDataIdentifier. 0xF188 indicates a vehicleManufacturerECUSoftwareNumberDataIdentifier. 0xF189 indicates a vehicleManufacturerECUSoftwareVersionNumberDataIdentifier. 0xF18A indicates a systemSupplierIdentifierDataIdentifier. 0xF194 indicates a systemSupplierECUSoftwareNumberDataIdentifier. 0xF195 indicates a systemSupplierECUSoftwareVersionNumberDataIdentifier. 0xF19F indicates an EntityDataIdentifier. 0xF18B indicates an ECUManufacturingDateDataIdentifier. 0xF18C indicates an ECUSerialNumberDataIdentifier. 0xF184 indicates an applicationSoftwareFingerprintDataIdentifier. 0xF191 indicates a vehicleManufacturerECUHardwareNumberDataIdentifier. 0xF192 indicates a systemSupplierECUHardwareNumberDataIdentifier. 0xF193 indicates a systemSupplierECUHardwareVersionNumberDataIdentifier. 0xF19F indicates an EntityDataIdentifier.

[0045] (Example of operation of configuration information estimation unit) The responses received in response to the requests sent to the ECU in the above steps S101 to S104 are stored in the diagnostic log DB 200. The configuration information estimation unit 300 reads data from the diagnostic log DB 200 to estimate the configuration information of the internal network of the target device.

[0046] An example of the estimation and grasping operation by configuration information estimation unit 300 will be described below with reference to the flowchart in Fig. 5. Note that the order and contents of estimation and grasping described here are merely examples, and are not limited to those described here.

[0047] <s201> In S201, the ECU presence confirmation unit 310 confirms the presence of an ECU. Specifically, the ECU presence confirmation is as follows.

[0048] The ECU presence confirmation unit 310 confirms the presence of the ECU connected to NW_B and the address information of the ECU from the response to the DoIP Vehicle Identification Request broadcast to the ECU connected to NW_B. In other words, if address information is received as a response to the Vehicle Identification Request, it can be assumed that the ECU with that address information exists on NW_B.

[0049] Furthermore, the ECU presence confirmation unit 310 confirms the presence and NW_A-ID of the ECU connected to the NW_A from the response to the testerPresent of the UDS transmitted to each ECU connected to the NW_A. In other words, if the NW_A-ID is received as a response to the testerPresent, it can be estimated that the ECU with the NW_A-ID exists on the NW_A.

[0050] Furthermore, the ECU presence confirmation unit 310 confirms the presence of the Gateway-ECU and its address information from the response to the DoIP Entity Status Request. That is, when a response indicating that the node type is Gateway is received as the response to the Entity Status Request, it can be estimated that the Gateway-ECU exists.

[0051] <s202> In S202, the topology estimation unit 320 estimates the topology of the internal network of the target device (here, the automobile). Specifically, the estimation is performed as follows.

[0052] The topology estimation unit 320 estimates that the ECUs connected to the NW_B are connected to one Switch in a star configuration.

[0053] For example, based on the confirmation result in S201 that one Gateway-ECU (also functions as a Switch) exists and that an ECU exists on NW_B, the topology estimation unit 320 estimates that the internal network has a configuration in which the ECUs connected to NW_B are connected to one Switch in a star shape. Such an estimation can be made based on, for example, a predetermined rule.

[0054] Furthermore, the topology estimation unit 320 estimates that the NW_A is connected to the Gateway-ECU. For example, the topology estimation unit 320 estimates that the NW_A is connected to the Gateway-ECU based on the fact that the existence of the Gateway-ECU and the existence of an ECU connected to the NW_A are confirmed as a result of the confirmation in S201. Such an estimation can be performed based on, for example, a predetermined rule.

[0055] Furthermore, the topology estimation unit 320 estimates that the ECU connected to the NW_A is connected to the NW_A under the Gateway-ECU in a bus topology. For example, the topology estimation unit 320 estimates that the ECU connected to the NW_A is connected to the NW_A under the Gateway-ECU in a bus topology based on the estimation result that the NW_A is connected to the Gateway-ECU and publicly known information on the connection method of the ECU to the NW_A (e.g., that it is connected in a bus topology). Such an estimation can be performed based on, for example, a predetermined rule.

[0056] <s203> In S203, the ECU information extraction unit 330 extracts the ECU information, specifically as follows.

[0057] The ECU information extraction unit 330 grasps the ECU information (VIN, model number, software version, etc.) of each ECU from the response to ReadDataByIdentifier of the UDS with the DID set to 0xF181, 0xF183, 0xF184, 0xF188, 0xF189, 0xF18A, 0xF194, 0xF195, 0xF19F, 0xF18B, 0xF18C, 0xF184, 0xF191, 0xF192, 0xF193, or 0xF19F (these DIDs are examples).

[0058] <s204> In S204, the output unit 340 outputs the information obtained in S201 to S203. For example, the output unit 340 creates a graphical image as shown in Fig. 1 from the information obtained in S201 to S203, and outputs (displays) the image. The output unit 340 may also output the information obtained in S201 to S203 in the form of a list or natural language. Also, it may output audio in a natural language.

[0059] The configuration information estimating system according to the present embodiment shown in Fig. 3 can be implemented in various forms. Below, examples 1 to 6 will be described as examples of implementation methods according to the present embodiment.

[0060] Example 1 Fig. 6 is a configuration diagram of the configuration information estimation system in the embodiment 1. As shown in Fig. 6, in the embodiment 1, an external device having all the functions of the configuration information estimation system, that is, a diagnostic communication transmitting / receiving unit 100, a diagnostic log DB 200, and a configuration information estimation unit 300, is connected to an automobile 400.

[0061] The method of connecting an external device to automobile 400 may be a method of physically connecting the external device to automobile 400, or a method of realizing the external device on a network such as a cloud and remotely connecting the external device on the network to automobile 400.

[0062] Example 2 7 is a configuration diagram of a configuration information estimation system in Example 2. In Example 2, two devices, a diagnostic communication transmitting / receiving device including a diagnostic communication transmitting / receiving unit 100, and a configuration information estimation device including a diagnostic log DB 200 and a configuration information estimation unit 300, are connected to an automobile 400.

[0063] 7 shows a configuration example in which the diagnostic communication transmitting / receiving device is physically connected to the automobile 400, and the configuration information estimation device is placed on the cloud and connected to the diagnostic communication transmitting / receiving device via a network. Note that this type of connection is just one example, and the locations where the diagnostic communication transmitting / receiving device and the configuration information estimation device are placed are not limited to a specific one.

[0064] Example 3 8 is a configuration diagram of a configuration information estimating system according to a third embodiment. The third embodiment is an example in which a diagnostic log DB 200 is provided in a diagnostic communication transmitting / receiving device in the configuration of the second embodiment.

[0065] In the second and third embodiments, the diagnostic log DB 200 may be arranged outside the diagnostic communication transmitting / receiving device or the configuration information estimating device, rather than inside these devices.

[0066] Example 4 Fig. 9 is a configuration diagram of a configuration information estimation system in the fourth embodiment. In the fourth embodiment, a processing device that realizes all functions from the diagnostic communication transmitting / receiving unit 100 to the configuration information estimation unit 300 is disposed on an in-vehicle NW. That is, as shown in Fig. 9, a processing device having the diagnostic communication transmitting / receiving unit 100, the diagnostic log DB 200, and the configuration information estimation unit 300 is provided inside an automobile 400.

[0067] The above-mentioned processing device provided in the automobile 400 may be arranged in a form of being physically connected to the in-vehicle NW, or may be realized on any ECU. In other words, one or more ECUs may have the diagnostic communication transmitting / receiving unit 100, the diagnostic log DB 200, and the configuration information estimating unit 300.

[0068] Example 5 10 is a configuration diagram of a configuration information estimation system in the fifth embodiment. In the fifth embodiment, a processing device that performs processing on an in-vehicle network is provided inside an automobile 400, and an external device is connected to the automobile 400. As shown in FIG. 10, the processing device includes a diagnostic communication transmitting / receiving unit 100, and the external device includes a diagnostic log DB 200 and a configuration information estimation unit 300.

[0069] The processing device may be arranged in a form in which the device is physically connected in the in-vehicle NW, or may be realized on any ECU. Also, the method of connecting the external device may be a method of physically connecting the device to the automobile 400, or a method of providing an external device as a device on a network such as a cloud and remotely connecting it to the automobile 400.

[0070] Example 6 11 is a configuration diagram of a configuration information estimating system according to a sixth embodiment. The sixth embodiment is an example in which a diagnostic log DB 200 is provided in the processing device in the configuration of the fifth embodiment.

[0071] In the fifth and sixth embodiments, the diagnostic log DB 200 may be arranged outside the processing device or the external device, rather than inside these devices. ---------------------------------- Second embodiment-------------------------------- Next, a second embodiment will be described.

[0072] (Example of vehicle configuration information) In the second embodiment as well, the configuration information estimation system estimates vehicle configuration information of an automobile. An example of vehicle configuration information is shown in Fig. 12. The vehicle configuration information is made up of three items in Fig. 12: the topology of the in-vehicle network, ECU information (two tables), and normal communication (a thick-lined box in the table on the right). Note that this information is within the scope of elemental technologies 1 to 3, which will be described later.

[0073] In the second embodiment, diagnostic communication is used in the same manner as in the first embodiment, as described with reference to FIG.

[0074] (About car networks) The automobile network assumed in the second embodiment is shown in Fig. 13. As shown in Fig. 13, in this network, one OBD-II port is connected to both the NW_A bus and the in-vehicle NW-B. The following diagnostic communications (1) and (2) are possible from one OBD-II port.

[0075] (1) Diagnostic communication with the ECU connected to NW_A is possible using only NW_A (without going through SW). It is also possible to use the in-vehicle NW_B from OBD-II to GW, and then use NW_A after GW to perform diagnostic communication with the ECU connected to NW_A.

[0076] (2) For ECUs connected to the in-vehicle NW_B, diagnostic communication is performed using only the in-vehicle NW_B (via SW).

[0077] (About elemental technologies) Here, the elemental technologies in the second embodiment will be described. The elemental technologies in the second embodiment are (1) to (3) below. Note that in (4) and (5), the technologies described in the first embodiment are shown as elemental technologies 4 and 5.

[0078] (1) Technology to estimate the topology of NW_A (Elemental Technology 1) (2) Technology to identify the normal (non-diagnostic) NW_A-ID (000 to 6FF) sent by the ECU connected to NW_A (Elemental Technology 2) (3) Technology to estimate the function (=name) of each ECU (Elemental Technology 3) (4) Technology to acquire ECU information for each ECU (Elemental Technology 4) (5) Technology to estimate the topology of NW_B (Elemental Technology 5) Hereinafter, elemental technologies 1 to 3 in the second embodiment will be described. (Elemental Technology 1) <Conventional technologies and issues related to element technology 1> The conventional technology related to element technology 1 is the technology disclosed in the already described Non-Patent Document 1. As described above, the technology disclosed in Non-Patent Document 1 uses SNMP to acquire the MAC address forwarding table of each switch in the target network, and estimates the L2 topology of the target network by analyzing the acquired information.

[0079] However, in order to obtain the topology of the NW_A bus using an SNMP-based method such as that described in Non-Patent Document 1, additional resources are required to enable the operation of the SNMP agent and support for SNMP is required in each ECU, resulting in additional costs.

[0080] <Key points and effects of elemental technology 1> Elemental technology 1 also utilizes the sending and receiving of diagnostic communications that are available as standard in most automobiles. Specifically, the topology of the NW_A bus is estimated by using the RTT of diagnostic communications when the occupancy rate of a specific bus is forcibly increased (congested). The details of this technology will be described later.

[0081] Since diagnostic communication protocols are supported as standard in each ECU, this technology makes it possible to estimate the topology of the NW_A bus without incurring additional costs such as increasing resources or supporting new protocols.

[0082] <Objectives and application of elemental technology 1> In elemental technology 1, the goal is to identify ECUs connected to the same NW_A bus. For example, in the case of the configuration shown in Figure 14, the following information is estimated.

[0083] - ECU-A and ECU-B are connected to the same bus -ECU-A and ECU-C are connected to different buses -ECU-B and ECU-C are connected to different buses The target of application of elemental technology 1 is a system that has a bus with a domain architecture, for example, a system that has multiple buses under the GW as shown in Figure 15. The GW routes diagnostic communication to the appropriate bus. For example, diagnostic communication with NW_A-ID corresponding to ECU-A is sent from the GW only to the bus to which ECU-A is connected. <Key points regarding the estimation method for elemental technology 1> As described above, in elemental technology 1, the topology of NW_A is estimated by utilizing the RTT (Round Trip Time) of diagnostic communication when the occupancy rate of a specific bus is forcibly increased (congested).

[0084] The definition of the RTT of diagnostic communication will be described with reference to Fig. 16. Fig. 16 shows an example of diagnostic communication from a PC to ECU-A. The RTT of diagnostic communication is the time from when the PC starts sending a diagnostic request (S1) to one ECU to when the PC finishes receiving the diagnostic response (S2) from that ECU.

[0085] Here, assume that only bus 1 is congested, as shown in Fig. 17. When only bus 1 is congested, the RTT of diagnostic communication with the ECU connected to bus 1 becomes longer compared to when there is no congestion. On the other hand, the RTT of diagnostic communication with the ECU connected to bus 2 does not change compared to when there is no congestion. In elemental technology 1, such phenomena are utilized to estimate the topology.

[0086] <Outline of estimation procedure for elemental technology 1> An outline of the estimation procedure of elemental technology 1 will be described with reference to Fig. 18 to Fig. 20. First, as shown in Fig. 18, a diagnosis request is sent several times to ECU-B and ECU-C, and the average RTT values ​​of ECU-B and ECU-C are examined. An image of the average RTT values ​​of ECU-B and ECU-C is shown in the lower left of Fig. 18 (and Figs. 19 and 20).

[0087] Next, as shown in Fig. 19, the occupancy rate of the bus connecting ECU-A and ECU-B is increased by sending diagnosis requests to ECU-A at a high frequency. In the example of Fig. 19, the occupancy rate of the bus is shown to be 99%.

[0088] Next, as shown in Fig. 20, when the bus to which ECU-A is connected is congested, diagnostic requests are sent several times to ECU-B and ECU-C, and the average RTT values ​​of ECU-B and ECU-C are examined.

[0089] As shown in the lower left of Figure 20, if the average value of the RTT statistics has increased compared to when there is no congestion (lower left diagram), the ECU is determined to be connected to the same bus as ECU-A. In the example of Figure 20, it is determined that "ECU-A and B are connected to the same bus."

[0090] (Elemental Technology 2) Next, elemental technology 2 will be described.

[0091] <Conventional technologies and issues related to element technology 2> An example of conventional technology related to elemental technology 2 is "Sekar Kulandaivel, Tushar Goyal, Arnav Kumar Agrawal, and Vyas Sekar, "CANvas: Fast and Inexpensive Automotive Network Mapping," In the Proceedings of the 28th USENIX Security Symposium, pp.389-405, (2019)."

[0092] This conventional technology utilizes a characteristic of NW_A that if an abnormal collision of messages sent by an ECU occurs a certain number of times, the message transmission of that ECU stops (bus off), and identifies all NW_A-IDs of NW_A messages sent by a single ECU.

[0093] A specific example of a prior art approach is as follows.

[0094] At the same time as ECU-A on the NW_A bus transmits an NW_A message with NW_A-ID=0x300, an estimated device connected to the NW_A bus transmits an NW_A message with NW_A-ID=0x300.

[0095] This causes a collision of NW_A messages with NW_A-ID=0x300. If this collision occurs repeatedly, ECU-A goes bus-off.

[0096] When ECU-A goes bus-off, all NW_A messages sent by ECU-A for NW_A-ID=0x300 (e.g., 0x301, 0x302) will also stop.

[0097] At this time, the NW_A-ID of the NW_A message that is no longer being sent is checked by the estimation device to identify the NW_A-ID of the NW_A message being sent by ECU-A. In this example, it is identified that "ECU-A is sending NW_A messages with NW_A-ID=0x300, 0x301, and 0x302."

[0098] However, the above-mentioned conventional techniques have the following problems.

[0099] In most recent automobiles, the OBD-II port installed to access the in-vehicle NW_A bus is set to send and receive only diagnostic communications. On the other hand, in order to generate a collision of NW_A messages in the above-mentioned conventional technology, it is necessary to be able to send non-diagnostic communications to the in-vehicle NW_A bus. Therefore, it is difficult to implement the conventional technology in a general form that uses the OBD-II port.

[0100] <Key points and effects of elemental technology 2> In elemental technology 2, diagnostic communication is used to disrupt the transmission period of the NW_A message of the target ECU, and the disruption of the transmission period of the NW_A message is detected by the NW_A-IDS. Then, by associating the detection result with the information of the target ECU, the NW_A-ID of the NW_A message transmitted by the ECU is identified.

[0101] With this technology, it is possible to identify the "NW_A-ID of the NW_A message sent by the ECU" using the OBD-II port in most modern automobiles. <Objectives and application of elemental technology 2> In elemental technology 2, for example, as shown in FIG. 21, the goal is to associate a normal NW_A-ID (000 to 6FF) transmitted by an ECU connected to NW_A with a diagnostic NW_A-ID (700 to 7FF), and ultimately with ECU information.

[0102] Elemental technology 2 is based on the premise that an IDS exists on the target network and monitors normal messages. The IDS issues an alert if the interval between normal message transmission times is shorter / longer than the design value or if there is an abnormal change in the payload. The IDS alert contains information about the message detected as abnormal (NW_A-ID in the example of an automobile). The vehicle configuration estimation device can obtain the IDS alert in some way.

[0103] <Key points and procedures for the estimation method of elemental technology 2> The processing procedure that is the key point of elemental technology 3 will be described with reference to FIG.

[0104] (1) Using ECUReset (e.g., NW_A-ID=7E0), the periodicity and payload changes of the message transmissions of the normal NW_A-ID (e.g., NW_A-ID=300) sent by the target ECU are disrupted.

[0105] (2) An alert is issued to the NW_A-IDS. For example, the alert includes NW_A-ID=300.

[0106] (3) Then it is determined that "the NW_A-ID contained in the alert is the normal NW_A-ID sent by the target ECU."

[0107] (Elemental Technology 3) Next, elemental technology 3 will be described.

[0108] <Conventional technologies and issues related to element technology 3> An example of a conventional technique related to elemental technology 3 is "X. Feng, et al: Acquisitional Rule-based Engine for Discovering Internet-of-Things Dvices. USENIX (2018)." This conventional technique uses response information collected from IoT devices and web crawling and scraping techniques to identify IoT device information (device type, vendor, model number).

[0109] More specifically, in this conventional technology, multiple web crawling / scraping results B are obtained for keyword A extracted from the response of an IoT device. In the automobile example, assume that the ECU model number "12345-67890" can be obtained from an ECU. In this case, A=12345-67890. Also assume that the crawling / scraping results using A are as shown in Figure 23.

[0110] In this conventional technology, the confidence level conf(A⇒B) is calculated for each of the multiple results B.

[0111] conf(A⇒B) = (number of results containing both A and B) / (number of results containing A) Then, the result with the highest confidence is extracted as a single result. In the example of Figure 23, A=12345-67890 and B=Engine Module are extracted with conf(A⇒B)=0.67.

[0112] The above conventional techniques have the following problems.

[0113] If you crawl or scrape using the entire ECU model number as a keyword, there are often no search results and you cannot infer the ECU's functions.

[0114] In addition, when extracting the most reliable result, as in the above-mentioned conventional technology, the result with the least amount of information may be selected. For example, in the case of Figure 23, "Hybrid Engine Module" has more information, so this result is what we want to be extracted. However, in the case of the conventional technology, when the scraping result (table) shown in Figure 23 is obtained, "Engine Module" which appears more frequently is selected.

[0115] <Key points and effects of elemental technology 3> The key points of elemental technology 3 are points 1 and 2 below.

[0116] Point 1 is to use the scraping results that use only the digits indicating the function based on the naming convention of ECU part numbers. Point 2 is to extract the results that maximize the sum of the support of the words contained in each web crawling and scraping result.

[0117] This technology can avoid the inability to estimate ECU functions (names) due to lack of search results. It also outputs highly reliable results with a large amount of information.

[0118] <Objectives and application of elemental technology 3> The objective of elemental technology 3 is to estimate the function (name) of each ECU (including NW_B connection). For example, in the example shown in Fig. 24, it estimates that "ECU-X is an IVI," "ECU-Y is a TCU," "ECU-A is an engine ECU," etc. Furthermore, elemental technology 3 can obtain information that uniquely identifies a device, and in the case of an automobile, it can obtain the "ECU model number."

[0119] <Key points and procedures for the estimation method of elemental technology 3> First, we will explain the overall picture of the estimation method of elemental technology 3. In elemental technology 3, the function (name) is identified by utilizing each ECU model number acquired through diagnostic communication and web crawling and scraping technology. An image of this is shown in Figure 25. Below, we will explain the above-mentioned points 1 and 2 in more detail.

[0120] <Point 1> In point 1, we also use the results of web crawling and scraping using only the functional digits of the ECU part number based on the naming convention of the ECU part number.

[0121] Many ECU model numbers are made up of a combination of digits indicating function information and digits indicating the vehicle model and year. When the digits indicating function information are marked with a circle and the digits indicating the model year are marked with a triangle, the ECU model number may have the following structure: ·○○○○○-△△△△△ ·△△△-○○○○○○-△ The reasons why using only functional digits as in point 1 reduces the number of non-existent search results are as follows:

[0122] Searching under the condition "all digits of the ECU model number match" is searching for ECUs that are "installed in vehicles of a specified model year" and have a "specified function." On the other hand, searching under the condition "only the digits indicating the function of the ECU model number match" is searching for ECUs with a "specified function." In other words, the number of search results can be reduced by reducing the number of search restrictions.

[0123] The method of extracting functional digits is not limited to a specific extraction method, but for example, any of the following extraction methods 1 to 3 can be used.

[0124] Extraction method 1) In extraction method 1, the digits related to the function are determined based on the publicly available "ECU model number naming rule information." For example, if the naming rule is published on the website of an automobile manufacturer, the digits related to the function are determined based on that public information.

[0125] Extraction method 2) In extraction method 2, only ECU model numbers related to a certain function are extracted and analyzed, and the digit related to the function is determined based on the analysis results. For example, when only ECU model numbers related to the engine ECU are extracted and analyzed, there is a digit whose value does not change in any ECU model number. This digit is determined as the digit related to the function.

[0126] Extraction method 3) In extraction method 3, the ECU model numbers of the ECUs installed in a certain automobile are extracted and analyzed, and the digits related to the function are determined based on the analysis results. For example, when the ECU model numbers of the ECUs installed in a certain automobile are extracted and analyzed, there is a digit whose value does not change in any ECU model number. Since this digit is considered to indicate the vehicle model rather than the function, the remaining digits are determined to be digits related to the function.

[0127] <Point 2> Point 2 of elemental technology 3 extracts the result that maximizes the sum of the support of words contained in each web crawling / scraping result. Specifically, it is as follows.

[0128] When inferring the function (name) of an ECU whose ECU model number is "12345-67890", assume that the web crawling / scraping results shown in Figure 26 are obtained. Calculate the following support sup(X) for the word X included in Figure 26.

[0129] sup(X) = (number of results containing X) / (number of all web crawling / scraping results) Then, the sum of the support of the words contained in each line is calculated for each line, and the result with the maximum sum is extracted as a single result. In the example of Figure 26, Hybrid Engine Module is extracted. Here, sup(Engine) = 1, sup(Module) = 1, sup(Hybrid) = 0.3, and the sum = 2.3.

[0130] (Example) The specific device configuration and operation in the second embodiment will be described below as examples. The outline of each example is as follows.

[0131] A. List of examples in terms of combinations of elemental technologies Example A1: Example of the most basic combination of elemental technologies (details of the processing flow) Examples A2 to A4: Examples in which each elemental technology is used alone Examples A5 to A7: Examples of partially combining elemental technologies B. List of examples in terms of physical functional arrangement Example B1: An example in which the functions according to the present invention are deployed on an in-vehicle network Example B2: An example in which the function according to the present invention is directly connected to the OBD-II port Example B3: Example of implementing the function according to the present invention from a charging port Note that B1 to B3 may be arranged on the cloud by extracting components other than the in-vehicle network 1 and the message transmission / reception unit 23, which will be described later.

[0132] Example B4: Example of performing estimation using the function according to the present invention deployed on an external network C. Listing of Examples in Terms of Purpose Example C1: Example of use for security analysis in SOC (Security Operation Center) etc. Example C2: Example of use for asset management Example C3: Example of performing anomaly detection Example C4: Example of use for security diagnosis In addition, when actually implementing the present invention, the above-mentioned embodiments A and B are combined. For example, embodiment A1 is implemented with the functional arrangement of embodiment B1. This is then used for the purpose described in C. Each embodiment will be described below.

[0133] (Example A1) The embodiment A1 is an embodiment with the most basic combination of core technologies. Here, as an example, the physical deployment of the embodiment B2 will be described.

[0134] <Device configuration (block diagram)> Fig. 27 shows a configuration diagram of a configuration information estimation system in embodiment A1. As shown in Fig. 27, the configuration information estimation system includes a component estimation unit 2 and a configuration information estimation result DB 22. The component estimation unit 2 may be called a vehicle configuration estimation device or a network configuration estimation device. The configuration information estimation system may be called a configuration information estimation device. The component estimation unit 2 is connected to an in-vehicle NW 1 and a website 7 (Web server) and is capable of communicating with them.

[0135] The component estimation unit 2 includes an ECU basic information acquisition unit 3, an ECU function estimation unit 4, a NW_B topology estimation unit 12, a NW_A bus topology estimation unit 13, a normal NW_A communication estimation unit 18, a message transmission / reception unit 23, and a configuration information acquisition / registration unit 24.

[0136] The ECU function estimation unit 4 includes a Web search unit 6, a search result DB 8, an exact match extraction unit 9, a specific partial match extraction unit 10, and an estimation unit 11. Note that the exact match extraction unit 9, the specific partial match extraction unit 10, and the estimation unit 11 may be collectively referred to as an estimation unit.

[0137] The NW_A bus topology estimation unit 13 includes a base RTT calculation unit 14, a congestion RTT calculation unit 15, an RTT comparison unit 16, and an estimation unit 17. Note that the "RTT comparison unit 16 and the estimation unit 17" may be collectively referred to as an estimation unit.

[0138] The normal NW_A communication estimation unit 18 includes a restart command sending unit 19, a vehicle alert receiving unit 20, and an estimation unit 21.

[0139] The operation of the device will be described below with reference to a flowchart. In the following description, messages are transmitted to and received from the in-vehicle network 1 and the in-vehicle ECU via the message transmitting / receiving unit 23.

[0140] <Overall process flow> The overall process flow of the configuration information estimation system will be described with reference to Fig. 28. Note that the process order shown in Fig. 28 is just an example.

[0141] At S1030, the ECU basic information acquisition unit 3 acquires ECU basic information. At S1040, the ECU function estimation unit 4 estimates the ECU function. At S1120, the NW_B topology estimation unit 12 estimates the topology of NW_B. At S1130, the NW_A bus topology estimation unit 13 estimates the NW_A bus topology. At S1180, the normal NW_A communication estimation unit 18 estimates normal NW_A communication.

[0142] The processing contents of each step will be explained in detail below.

[0143] <s1030> S1030 will be described with reference to FIG.

[0144] In S1030-1, the vehicle configuration estimation device is connected to the OBD-II port (NW_B) of the in-vehicle NW1. In S1030-2, the ECU basic information acquisition unit 3 executes S1031. In S1030-3, the ECU basic information acquisition unit 3 executes S1032. In S1032, S1033 and S1034 are also executed.

[0145] In S1030-4, the ECU basic information acquisition unit 3 executes S1035. In S1030-5, the ECU basic information acquisition unit 3 disconnects the vehicle configuration estimation device from the OBD-II port (NW_B) and connects it to the OBD-II port (NW_A).

[0146] In S1030-6, the ECU basic information acquisition unit 3 executes S1036. In S1030-7, the ECU basic information acquisition unit 3 executes S1037. In S1037, the ECU basic information acquisition unit 3 also executes S1038. In S1030-8, the ECU basic information acquisition unit 3 executes S1039.

[0147] <s1031> Next, the process of S1031 will be described with reference to FIG.

[0148] In S1031-1, the ECU basic information acquisition unit 3 acquires a local IP address on the in-vehicle NW 1 by AutoIP or DHCP in accordance with the DoIP regulations.

[0149] In S1031-2, if the ECU basic information acquisition unit 3 receives a Vehicle Announcement broadcast by each ECU on the in-vehicle NW 1 in accordance with the DoIP regulations, the process proceeds to S1031-5, and if not, the process proceeds to S1031-3.

[0150] In S1031-3, the ECU basic information acquisition unit 3 broadcasts a Vehicle Identification Request (defined in DoIP) on the in-vehicle NW1.

[0151] In S1031-4, each ECU on the in-vehicle network 1 responds with a Vehicle Identification Response to the Vehicle Identification Request in accordance with the DoIP standard. The ECU basic information acquisition unit 3 receives the Vehicle Identification Response.

[0152] In S1031-5, the ECU basic information acquisition unit 3 records information such as the source IP address included in the received Vehicle Announcement or Vehicle Identification Response in a storage means such as a memory. The recorded information is shown in FIG. 31 (Table 3031). Note that the information to be recorded is not limited to that in Table 3031.

[0153] <s1032> Next, the process of S1032 will be described with reference to FIG. 32. In S1032-1, the ECU basic information acquisition unit 3 declares the following variables.

[0154] · The list of IP addresses in Table 3031 stored in the previous step (S1031), "IP = [192.168.10.1, 192.168.10.2, 192.168.10.3]" · The length of the IP list, "Length(IP)" (in this example, Length(IP) = 3) · "DID = [0xF18C, 0xF190, 0xF191, 0xF194, 0xF195, 0xF19F]" · The length of the DID, "Length(DID)" (in this example, Length(DID) = 6) · i = 0 Note that the variable names may be other than the above. Also, the content of IP may be unified with values other than IP addresses. Other values may be added to DID. In S1032-2, the ECU basic information acquisition unit 3 determines whether i < Length(IP). If Yes, it proceeds to S1032-3; if No, the process ends.

[0155] In S1032-3, the ECU basic information acquisition unit 3 executes the process of S1033. In S1032-4, the ECU basic information acquisition unit 3 executes the process of S1034. In S1032-5, i is incremented by 1, and the process returns to S1032-2.

[0156] <s1033> Next, the process of S1033 will be described with reference to Fig. 33. In S1033-1, the ECU basic information acquisition unit 3 transmits a DoIP Entity Status Request to the IP[i] on the in-vehicle NW1.

[0157] In S1033-2, the ECU having IP[i] on the in-vehicle network 1 responds with a DoIP Entity Status Response to the DoIP Entity Status Request in accordance with the DoIP standard. The ECU basic information acquisition unit 3 receives the DoIP Entity Status Response.

[0158] In S1033-3, the ECU basic information acquisition unit 3 records the "Node type" and IP[i] included in the received DoIP Entity Status Response in the storage means. An example of the recorded information is shown in FIG. 34 (Table 3032).

[0159] <s1034> Next, the process of S1034 will be described with reference to FIG. 35. In S1034-1, the ECU basic information acquisition unit 3 declares a variable j = 0. Note that the variable name may be other than j. In S1034-2, the ECU basic information acquisition unit 3 determines whether j < Length(DID) is satisfied. If Yes, it proceeds to S1034-3. If No, the process ends.

[0160] In S1034-3, the ECU basic information acquisition unit 3 transmits readDataByIdentifier (specified by UDS) with DID[j] set in DID to IP[i] and receives a response. In S1034-4, the ECU basic information acquisition unit 3 records the dataRecord of the received response together with IP[i] and DID[j] in the storage means. An example of the recorded information is shown in FIG. 36 (Table 3033). In S1034-5, the ECU basic information acquisition unit 3 sets j = j + 1 and returns to S1034-2.

[0161] <s1035> Next, S1035 will be described with reference to Fig. 37. In S1035-1, ECU basic information acquisition unit 3 changes the DID in Fig. 36 (Table 3033) to "Description" based on the UDS regulations, and converts dataRecord from ASCII (hexadecimal) to a character string. The result after changing and converting Fig. 36 (Table 3033) is as shown in Fig. 38 (Table 3034). Note that the content of the description and the method of converting dataRecord are not limited to this.

[0162] In S1035-2, the ECU basic information acquisition unit 3 organizes the data in Fig. 38 (Table 3034) using "IP address" and "ECU model number" as a composite primary key. The organized result is as shown in Fig. 39 (Table 3035). Note that the organization method is not limited to this.

[0163] In S1035-3, the ECU basic information acquisition unit 3 combines Fig. 39 (Table 3035), Fig. 31 (Table 3031), and Fig. 34 (Table 3032) using "IP address" as a key. The result is as shown in Fig. 40 (Table 3036).

[0164] In S1035-4, the ECU basic information acquisition unit 3 stores the combination result of FIG. 40 (table 3036) in the configuration information estimation result DB 22 via the configuration information acquisition / registration unit 24.

[0165] <s1036> Next, S1036 will be described with reference to Fig. 41. In S1036-1, the ECU basic information acquisition unit 3 transmits a TesterPresent request to all the diagnostic NW_A-IDs = 0x700 to 0x7FF and the extended diagnostic NW_A-IDs (hereinafter, these are collectively referred to simply as "NW_A-IDs") in sequence in accordance with the DoCAN and UDS regulations.

[0166] In S1036-2, if a response occurs on the in-vehicle network in response to the TesterPresent request transmitted in the previous step, the ECU basic information acquisition unit 3 records the NW_A-ID (request NW_A-ID) transmitted by itself in the storage means. For example, if a response occurs when a TesterPresent request with NW_A-ID=700 is transmitted, the ECU basic information acquisition unit 3 records NW_A-ID=700 and the NW_A-ID (response NW_A-ID) set in the response. The result is as shown in FIG. 42 (Table 3037).

[0167] <s1037> Next, S1037 will be described with reference to FIG. 43. In S1037-1, the ECU basic information acquisition unit 3 declares the following variables.

[0168] · The required NW_A-ID list "NW_A-ID = [0x700, 0x724, 0x750, 0x7E0, 0x7E1]" in FIG. 42 (Table 3037) recorded in the previous step · The length of the list "Length(NW_A-ID)" (in this example, Length(NW_A-ID) = 5) · "DID = [0xF18C, 0xF190, 0xF191, 0xF194, 0xF195, 0xF19F]" · The length of DID "Length(DID)" (in this example, Length(DID) = 6) · i = 0 Note that the variable names may be other than those above. Also, the content of NW_A-ID may be unified with values other than NW_A-ID. Other values may be added to DID. In S1037-2, it is checked whether i < Length(NW_A-ID) is satisfied. If Yes, proceed to S1037-3. If No, end the process. In S1037-3, the ECU basic information acquisition unit 3 executes S1038. In S1037-4, set i = i + 1 and return to S1037-2.

[0169] <s1038> Next, S1038 will be described with reference to FIG. 44. In S1038-1, the ECU basic information acquisition unit 3 declares a variable j = 0. Note that the variable name can be other than j.

[0170] In S1038-2, the ECU basic information acquisition unit 3 determines whether j < Length(DID) is satisfied. If Yes, it proceeds to S1038-3; if No, the process ends.

[0171] In S1038-3, the ECU basic information acquisition unit 3 transmits readDataByIdentifier (defined by UDS) with DID[j] set in DID to NW_A-ID[i] and receives a response.

[0172] In S1038-4, the ECU basic information acquisition unit 3 records the dataRecord of the received response together with NW_A-ID[i] (request NW_A-ID), response NW_A-ID, and DID[j] in the storage means. An example of the recorded information is shown in FIG. 45 (Table 3038). In S1038-5, j = j + 1 and it returns to S1038-2.

[0173] <s1039> Next, S1039 will be described with reference to Fig. 46. In S1039-1, the ECU basic information acquisition unit 3 changes the DID in Fig. 45 (Table 3038) to "Description" based on the UDS regulations, and converts the dataRecord from ASCII (hexadecimal) to a character string. Note that the content of the description and the method of converting the dataRecord are not limited to this.

[0174] In S1039-2, the ECU basic information acquisition unit 3 organizes the data from the previous step using "NW_A-ID" and "ECU model number" as a composite primary key. The result of the organization is as shown in Figure 47 (Table 3039). Note that the organization method is not limited to this.

[0175] In S1039-3, the ECU basic information acquisition unit 3 passes the arrangement result of FIG. 47 (table 3039) to the configuration information estimation result DB 22 via the configuration information acquisition / registration unit 24.

[0176] <s1040> Next, S1040 will be described with reference to FIG. 48. In S1040-1, the ECU function estimation unit 4 declares the following variables.

[0177] · A list of non-duplicate ECU model numbers in FIGS. 40 (Table 3036) and 47 (Table 3039), obtained from the configuration information estimation result DB22 via the configuration information acquisition / registration unit 24 · "PN = [11111-56789, 22222-56789, 33333-56789, 44444-56789, 55555-56789, 66666-56789, 77777-56789, 88888-56789]" · The length of the PN list "Length(PN)" (in this example, Length(PN) = 8) · i = 0 Note that the variable names may be other than those above. Also, the content of the IP may be unified with values other than the IP address.

[0178] In S1040-2, the ECU function estimation unit 4 determines whether i < Length(PN) is satisfied. If Yes, it proceeds to S1040-3; if No, the process ends. In S1040-3, S1061 is performed for PN[i]. In S1040-4, S1091 is performed for PN[i]. In S1040-5, S1101 is performed for PN[i]. In S1040-6, S1111 is performed for PN[i]. In S1040-7, i = i + 1 and it returns to S1040-2.

[0179] <s1061> Next, S1061 will be described with reference to Fig. 49. In S1061-1, the Web search unit 6 crawls Web pages using the ECU model number acquired from the configuration information estimation result DB 22 as a search word. The Web page to be crawled at this time is preferably a website suitable for searching for the function (=name) of an ECU from the ECU model number. In addition, two types of search words are used: the entire ECU model number and digits related to the function of the ECU model number.

[0180] The digits related to the function of the ECU model number are identified by the method described in the explanation of point 1 of elemental technology 3. However, the identification method is not limited to this.

[0181] In S1061-2, the Web search unit 6 scrapes pair information of the ECU model number and the function corresponding to that ECU model number from the Web page crawled in the previous step.

[0182] In S1061-3, the Web search unit 6 stores the pair information in the past search result DB 8. The past search result DB 8 has a DB structure as shown in FIG. 50 (table 3081), for example. <s1091> Next, step S1091 will be described with reference to Fig. 51. In step S1091, the exact match extraction unit 9 acquires, from the search result DB 8, pair information whose ECU model numbers are an exact match.

[0183] <s1101> Next, S1101 will be described with reference to Fig. 52. In S1101, the specific partial match extraction unit 10 acquires, from the search result DB8, pair information in which digits related to the function of the ECU model number match.

[0184] <s1111> Next, S1111 will be described with reference to Fig. 53. In S1111-1, the estimation unit 11 divides the function information of the paired information acquired in the above steps into words. For example, when paired information having the function information "Genuine Engine Control Module" is acquired, this is divided into four parts: "Genuine", "Engine", "Control", and "Module".

[0185] In S1111-2, the estimation unit 11 deletes frequent words that are not related to the function from among the words divided in the previous step. For example, in the example of the previous step, "Genuine" is deleted. However, it is not necessary to delete them.

[0186] In S1111-3, the estimation unit 11 calculates the support of each divided word. Specifically, the support of word x is calculated by the following formula. An example of the calculation result of the support is shown in FIG. 54 (Table 3111).

[0187] Support(x) = (number of pairs containing x) / (number of all pairs) In S1111-4, the estimation unit 11 calculates the sum of the support of words included in the function information of each paired information. Then, the paired information with the largest sum is output. Note that instead of the sum, the one with the largest average or product may be selected.

[0188] As an example, the process and results of calculating the sum based on the example of the support levels shown in FIG. 55 are shown below.

[0189] 1.Gas Motor Module Sum=0.25+0.5+1.0=1.75 2.Engine Motor Control Module Sum=0.75+0.5+0.75+1.0=3.0 3.Engine Control Module Sum=0.75+0.75+1.0=2.5 4.Engine Control Module Sum=0.75+0.75+1.0=2.5 Since the information of 2 has the maximum value, output the pair information of 2. The functional information of the pair information on which Figure 55 is based is as follows:

[0190] 1.Gas Motor Module 2.Engine Motor Control Module 3.Engine Control Module 4.Engine Control Module In S1111-5, the estimation unit 11 adds the labeled result, which will be described below, to a row having an appropriate ECU model number in FIG. 40 (Table 3036) or FIG. 47 (Table 3039) of the configuration information estimation result DB 22 via the configuration information acquisition and registration unit 24. Examples of the result are shown in FIG. 56 (Table 3112) and FIG. 57 (Table 3113). The labeling is as follows.

[0191] When "pair information with a perfect match in ECU model numbers" obtained from the search result DB8 is used in this process, only pair information with a perfect match in ECU model numbers is used for processing. The output result is then labeled "perfect match." On the other hand, when "pair information with a perfect match in ECU model numbers" obtained from the search result DB8 is used in this process, only pair information with a perfect match in ECU model numbers is used for processing. The output result is then labeled "partial match."

[0192] <s1120> Next, S1120 will be described with reference to Fig. 58. In S1120-1, the NW_B topology estimation unit 12 executes S1121. In S1120-2, the NW_B topology estimation unit 12 executes S1122.

[0193] <s1121> Next, S1121 will be described with reference to FIG. 59. In S1121-1, the NW_B topology estimation unit 12 declares the following variables.

[0194] · The list of IP addresses in FIG. 54 (Table 3111), "IP = [192.168.10.1, 192.168.10.2, 192.168.10.3]", obtained from the configuration information estimation result DB22 via the configuration information acquisition / registration unit 24 · The length of the IP list "Length(IP)" (in this example, Length(IP) = 3) · i = 0 Note that the variable names may be other than those above. Also, the content of IP may be unified with values other than IP addresses.

[0195] In S1121-2, the NW_B topology estimation unit 12 determines whether i < Length(IP) is satisfied. If Yes, it proceeds to S1121-3; if No, the process ends.

[0196] In S1121-3, the NW_B topology estimation unit 12 executes ICMP traceroute for IP[i] on the in-vehicle NW1 and records the result in the storage means. An example of the recorded information is shown in FIG. 60. In S1121-4, i = i + 1 and it returns to S1121-2.

[0197] <s1122> S1122 will be described with reference to FIG.

[0198] In S1122-1, the NW_B topology estimation unit 12 extracts all ECU model numbers from FIG. 56 (Table 3112) of the configuration information estimation result DB 22 via the configuration information acquisition and registration unit 24. Next, the NW_B topology estimation unit 12 deletes duplications of the extracted ECU model numbers. Then, the ECU model numbers from which duplications have been deleted are made to correspond one-to-one with physical ECUs. An example of the result is shown in FIG. 62.

[0199] In S1122-2, the NW_B topology estimation unit 12 adds the network interface to the information in Fig. 62 based on the "ECU model number", "MAC address", and "IP address" in Fig. 56 (Table 3112) acquired from the configuration information estimation result DB 22 via the configuration information acquisition and registration unit 24. The result is as shown in Fig. 63.

[0200] In S1122-3, the NW_B topology estimation unit 12 appropriately assigns all the information in Fig. 56 (Table 3112) acquired from the configuration information estimation result DB 22 via the configuration information acquisition and registration unit 24 to the ECUs and the ECU interfaces. The result is as shown in Fig. 64.

[0201] In S1122-4, the NW_B topology estimation unit 12 organizes the connection relationship between the OBD-II port, the ECU's network interface (and thus the physical ECU), and the IP router's NW_B cable based on the traceroute record (FIG. 62). If multiple ECUs exist under the same IP router, it is estimated that those ECUs and the IP router are connected by one NW_B switch. Also, if multiple ECUs exist in the in-vehicle network but no IP router exists, it is estimated that those ECUs are connected by one NW_B switch. The result is as shown in FIG. 65. It is noted that the method of organizing the connection relationship between ECUs is not limited to this.

[0202] In S1122-5, the NW_B topology inference unit 12 stores the inference result of FIG. 65 in the configuration information inference result DB 22 via the configuration information acquisition / registration unit 24.

[0203] <s1130> Next, S1130 by the NW_A bus topology estimation unit 13 will be described with reference to FIG.

[0204] In S1130-1, the base RTT calculation unit 14 executes S1141. In S1130-2, the congestion RTT calculation unit 15 executes S1151. In S1130-3, the congestion RTT calculation unit 15 executes S1152. In S1130-4, the RTT comparison unit 16 executes S1161. In S1130-5, the estimation unit 17 executes S1171. In S1130-6, the estimation unit 17 executes S1172.

[0205] <s1141> Next, S1141 will be described with reference to FIG.

[0206] In S1141-1, the base RTT calculation unit 14 transmits a TesterPresent request defined by UDS to NW_A-ID[i] 100 times at 200 ms intervals. Then, it receives a response to that. Furthermore, it records the transmission time and reception time in the storage means. An example of the recorded information is shown in FIG. 68. Note that the transmission interval and the number of transmissions are not limited to these.

[0207] In S1141-2, the base RTT calculation unit 14 calculates the statistical value of the response time (hereinafter referred to as pace response time) using the record of the previous step (Figure 68). Then, the result is recorded together with NW_A-ID[i] (e.g., Figure 69 (Table 3141)). The base response time is the difference between the time when TesterPresent is sent with the request NW_A-ID (0x700 in Figure 68) and the time when TesterPresent is received with the response NW_A-ID (0x708 in Figure 68) immediately thereafter. In addition, the average value, maximum value, minimum value, and standard deviation are calculated as statistical values. However, other statistical values ​​may be calculated.

[0208] <s1151> Next, S1151 will be described with reference to FIG. 70.

[0209] In S1151-1, the convergence RTT calculation unit 15 declares the following variables.

[0210] · A list "NW_A-ID = [0x700, 0x724, 0x750, 0x7E0, 0x7E1]" obtained from the configuration information estimation result DB22 via the configuration information acquisition / registration unit 24, with the request NW_A-ID in FIG. 57 (Table 3113) sorted in ascending order · The length of the list "Length(NW_A-ID)" (in this example, Length(NW_A-ID) = 5) · i = 0 Note that the variable names can be other than the above. Also, the content of NW_A-ID can be unified with values other than NW_A-ID.

[0211] In S1151-2, the convergence RTT calculation unit 15 determines whether i < Length(NW_A-ID) is satisfied. If Yes, it proceeds to S1151-2; if No, the process ends. In S1151-3, j = i + 1.

[0212] In S1151-4, the convergence RTT calculation unit 15 determines whether j < Length(NW_A-ID) is satisfied. If Yes, it proceeds to S1151-5; if No, the process ends. In S1151-5, the convergence RTT calculation unit 15 executes S1152 and returns to S1151-2.

[0213] <s1152> Next, S1152 will be described with reference to FIG.

[0214] In S1152-1, the congestion RTT calculation unit 15 continues to transmit a TesterPresent request defined by UDS to NW_A-ID[i] at 0.5 ms intervals until S1152 ends, congesting the NW_A bus to which the NW_A message of NW_A-ID[i] is transmitted. Note that the transmission interval is not limited to this.

[0215] In S1152-2, the congestion RTT calculation unit 15 transmits a TesterPresent request defined by UDS to NW_A-ID[j] 100 times at 200 ms intervals. Then, it receives a response to that. Furthermore, it records the transmission time and reception time in the storage means. An example of the recorded information is shown in FIG. 72. Note that the transmission interval and the number of transmissions are not limited to these.

[0216] In S1152-3, the congestion RTT calculation unit 15 calculates the statistical value of the response time (hereinafter, referred to as the congestion response time) using the record of the previous step. Then, the result is recorded in the storage means together with NW_A-ID[i] (referred to as the congestion NW_A-ID in FIG. 73 (Table 3151)) and NW_A-ID[j] (referred to as the statistical value calculation target NW_A-ID in FIG. 73 (Table 3151)). An example of the recorded information is shown in FIG. 73 (Table 3151).

[0217] The response time during congestion is the difference between the time when TesterPresent is sent with the request NW_A-ID and the time when TesterPresent is received with the response NW_A-ID immediately after that. In addition, the average, maximum, minimum, and standard deviation are calculated as statistical values. However, other statistical values ​​may be calculated. <s1162> Next, S1161 will be described with reference to FIG.

[0218] In S1161-1, the RTT comparator 16 compares the statistical value of NW_A-ID=x in FIG. 69 (Table 3141) with the statistical value of NW_A-ID=x for calculating the statistical value in FIG. 73 (Table 3151). Then, rows in which any value of the statistical value on the FIG. 73 (Table 3151) side has increased by 50% or more compared to FIG. 69 (Table 3141) are extracted from FIG. 73 (Table 3151). The extraction result is as shown in FIG. 75 (Table 3161). Note that the extraction method of FIG. 75 (Table 3161) is not limited to this.

[0219] In S1161-2, the RTT comparator 16 groups the congested NW_A-ID and the statistical value calculation target NW_A-ID in each row of Table 3161 in Fig. 75. For example, 0x700 and 0x724 are one group, 0x700 and 0x7E0 are one group, 0x724 and 0x7E0 are one group, and 0x750 and 0x7E1 are one group.

[0220] In S1161-3, the RTT comparison unit 16 combines the groups created in the previous step as much as possible. For example, 0x700 and 0x724 are one group, 0x700 and 0x7E0 are one group, and 0x724 and 0x7E0 are one group, so these three are considered to be one group. The result is as shown in Figure 76 (Table 3162).

[0221] <s1171> Next, S1171 will be described with reference to FIG.

[0222] In S1171-1, the estimation unit 17 extracts all ECU model numbers from the information equivalent to FIG. 56 (Table 3112) stored in the configuration information estimation result DB 22. Next, duplicates of the extracted ECU model numbers are deleted. Then, the ECU model numbers from which duplicates have been deleted are made to correspond one-to-one to physical ECUs. The result is as shown in FIG. 78.

[0223] In S1171-2, the estimation unit 17 adds the information of the requested NW_A-ID to Fig. 78 based on the information equivalent to Fig. 56 (Table 3112) stored in the configuration information estimation result DB 22. The result is as shown in Fig. 79.

[0224] In S1171-3, the estimation unit 17 compares the statistical value of NW_A-ID=x in FIG. 69 (Table 3141) with the statistical value of NW_A-ID=x for calculating the statistical value in FIG. 73 (Table 3151). Then, rows in which any value of the statistical value on the FIG. 73 (Table 3151) side has increased by 50% or more compared to FIG. 69 (Table 3141) are extracted from FIG. 73 (Table 3151). The extraction result is as shown in FIG. 75 (Table 3161). Note that the extraction method of FIG. 75 (Table 3161) is not limited to this.

[0225] In S1171-4, the estimation unit 17 groups the congested NW_A-ID and the statistical value calculation target NW_A-ID in each row of Table 3161 in Fig. 75. For example, 0x700 and 0x724 are one group, 0x700 and 0x7E0 are one group, 0x724 and 0x7E0 are one group, and 0x750 and 0x7E1 are one group.

[0226] In S1171-5, the estimation unit 17 combines the groups created in the previous step as much as possible. For example, 0x700 and 0x724 are one group, 0x700 and 0x7E0 are one group, and 0x724 and 0x7E0 are one group, so these three are considered to be one group. The result is as shown in Figure 76 (Table 3162).

[0227] <s1172> Next, S1172 will be described with reference to FIG.

[0228] In S1172-1, the estimation unit 17 determines that the ECUs responding to the NW_A message of the NW_A-ID grouped together in Fig. 76 (Table 3162) are connected to the same NW_A bus. Then, based on the determination result, the estimation unit 17 converts the information in Fig. 79 into a topology diagram of the NW_A bus (Fig. 81).

[0229] In S1172-2, the estimation unit 17 appropriately assigns all the information in Fig. 56 (Table 3112) passed to the configuration information estimation result DB 22 (configuration information organizing unit) to the ECUs. The result is as shown in Fig. 82.

[0230] In S1172-3, the estimation unit 17 searches for an ECU whose function includes GW (gateway) in a "complete match" or "partial match" with the ECU with NodeType = 0x1 in Figure 65 passed to the configuration information estimation result DB 22 (configuration information sorting unit) and the ECU in Figure 82.

[0231] In S1172-4, the estimation unit 17 connects the ECUs found in the previous step to the NW_A bus. The result is as shown in FIG.

[0232] In S1172-5, the estimation unit 17 stores the information shown in FIG. 83 in the configuration information estimation result DB 22 via the configuration information acquisition / registration unit 24. <s1180> Next, S1180 performed by the normal NW_A communication estimation unit 18 will be described with reference to FIG.

[0233] In S1180-1, the restart command transmission unit 19 executes S1191. In S1180-2, the restart command transmission unit 19 executes S1192. In S1180-3, the vehicle alert reception unit 20 executes S1201. In S1180-4, the vehicle alert reception unit 20 executes S1211.

[0234] <s1191> Next, S1191 will be described with reference to FIG. 85.

[0235] In S1191-1, the restart instruction transmission unit 19 declares the following variables.

[0236] · The required NW_A-ID list "NW_A-ID = [0x700, 0x724, 0x750, 0x7E0, 0x7E1]" in FIG. 56 (Table 3112) stored in the configuration information estimation result DB 22 · The length of the list "Length(NW_A-ID)" (in this case, Length(NW_A-ID) = 5) · i = 0 Note that the variable names may be other than those above. Also, the content of NW_A-ID may be unified with values other than NW_A-ID.

[0237] In S1191-2, the restart instruction transmission unit 19 determines whether i < Length(NW_A-ID) holds. If Yes, it proceeds to S1191-3; if No, the process ends. In S1191-3, the restart instruction transmission unit 19 executes S1192. In S1191-3, the restart instruction transmission unit 19 sets i = i + 1 and returns to S1191-2.

[0238] <s1192> Next, S1192 will be described with reference to FIG.

[0239] In S1192-1, the restart command transmission unit 19 transmits an ECUReset (ResetType=HardReset) request defined by UDS to NW_A-ID[i] ten times at random intervals of 5 to 10 seconds. Note that the transmission interval, the number of transmissions, and the ResetType are not limited to these.

[0240] In S1192-2, the restart command transmission unit 19 records the time when the ECUReset request was transmitted in the previous step together with NW_A-ID[i] in the storage means. An example of the recorded information is shown in FIG.

[0241] <s1201> Next, S1201 will be described with reference to FIG.

[0242] First, let us explain the premise. An ECU on the in-vehicle network 1 transmits an NW_A message of a certain NW_A-ID at a constant (designed value) time interval (transmission interval). In addition, the NW_A-IDS on the in-vehicle network 1 issues an alert if the transmission interval of an NW_A message of a certain NW_A-ID significantly deviates from the designed value. The alert stores the time of the alert and the NW_A-ID of the detected NW_A message.

[0243] An ECU that receives an ECUReset will temporarily stop sending NW_A messages in order to restart the ECU. After the restart, the ECU will resume sending NW_A messages after a set amount of time. Therefore, the intervals at which an ECU that receives an ECUReset sends NW_A messages will temporarily increase or decrease. The NW_A-IDS will determine this as an abnormality and issue an alert. In S1201-1, the vehicle alert receiving unit 20 records the alert of the NW_A-IDS together with the time in the storage means. An example of the stored information is shown in FIG.

[0244] <s1211> Next, S1211 will be described with reference to FIG.

[0245] In S1211-1, the estimation unit 21 associates the NW_A-ID recorded as the information shown in Fig. 87 with the NW_A-ID recorded as the information shown in Fig. 89. The association is performed based on the similarity of the recorded time. An example of the result of the association is shown in Fig. 91 (Table 3211).

[0246] In S1211-2, the estimation unit 21 adds the result of Fig. 91 (Table 3211) to the result of vehicle configuration estimation (for example, Fig. 83 or Fig. 56 (Table 3112)). At that time, a row satisfying the condition "NW_A-ID column of ECU Reset in Table 3211" = "requested NW_A-ID in Fig. 83 or Table 3112" is added to Fig. 83 or Fig. 56 (Table 3112).

[0247] When adding, for example, add it with a column name of “Regular Transmission NW_A-ID.” The result example is as shown in FIG. 92 and FIG. 93 (Table 3212).

[0248] (Example A2) Next, an embodiment A2 will be described. Fig. 94 is a configuration diagram of a system in the embodiment A2. As shown in Fig. 94, the configuration in the embodiment A2 is a configuration including only an ECU function estimation unit 4 corresponding to elemental technology 3 as an estimation unit. The processing of each unit is the same as the processing described in the embodiment A1.

[0249] (Example A3) Next, an embodiment A3 will be described. Fig. 95 is a configuration diagram of a system in the embodiment A3. As shown in Fig. 95, the configuration in the embodiment A3 is a configuration including only a NW_A bus topology estimation unit 13 corresponding to elemental technology 1 as an estimation unit. The processing of each unit is the same as the processing described in the embodiment A1.

[0250] (Example A4) Next, an embodiment A4 will be described. Fig. 96 is a configuration diagram of a system in the embodiment A4. As shown in Fig. 96, the configuration in the embodiment A4 is a configuration including only a normal NW_A communication estimation unit 18 corresponding to elemental technology 2 as an estimation unit. The processing of each unit is the same as the processing described in the embodiment A1.

[0251] (Example A5) Next, an embodiment A5 will be described. Fig. 97 is a configuration diagram of a system in the embodiment A5. As shown in Fig. 97, the configuration in the embodiment A5 is a configuration in which the normal NW_A communication estimation unit 18 is removed from the configuration of the embodiment A1 (Fig. 27). The processing of each unit is the same as the processing described in the embodiment A1.

[0252] (Example A6) Next, an embodiment A6 will be described. Fig. 98 is a configuration diagram of a system in the embodiment A6. As shown in Fig. 98, the configuration in the embodiment A6 is a configuration in which the NW_A bus topology estimation unit 13 is removed from the configuration of the embodiment A1 (Fig. 27). The processing of each unit is the same as the processing described in the embodiment A1.

[0253] (Example A7) Next, an embodiment A7 will be described. Fig. 99 is a configuration diagram of a system in the embodiment A7. As shown in Fig. 99, the configuration in the embodiment A7 is a configuration in which the ECU function estimation unit 4 is removed from the configuration of the embodiment A1 (Fig. 27). The processing of each unit is the same as the processing described in the embodiment A1.

[0254] (Example B1) Next, embodiment B1 will be described. Embodiment B1 is an embodiment in which a configuration information estimation system according to the present invention is installed on an in-vehicle NW. Fig. 100 is a configuration diagram of an automobile (in-vehicle NW) in embodiment B1. As shown in Fig. 100, a vehicle configuration estimation device 2 and a configuration information estimation result DB 22 are provided as functions of an ECU on the in-vehicle NW.

[0255] 100, instead of providing the configuration information estimation result DB22 in the ECU, the configuration information estimation result DB22 may be provided on the cloud. Also, in the vehicle configuration estimation device 2, one or more functional units other than the message transmission / reception unit 23 may be provided on the cloud. For example, only the ECU function estimation unit 4 in the vehicle configuration estimation device 2 may be provided on the cloud.

[0256] (Example B2) Next, embodiment B2 will be described. In embodiment B2, the configuration information estimation system (device) according to the present invention is directly connected to the OBD-II port. Fig. 101 is a configuration diagram of the system in embodiment B2. As shown in Fig. 101, the configuration information estimation system is directly connected to the OBD-II port.

[0257] 101, instead of providing the configuration information estimation result DB22 on the configuration information estimation system (device), the configuration information estimation result DB22 may be provided on the cloud. Also, in the vehicle configuration estimation device 2, one or more functional units other than the message transmission / reception unit 23 may be provided on the cloud. For example, only the ECU function estimation unit 4 in the vehicle configuration estimation device 2 may be provided on the cloud.

[0258] (Example B3) Next, an embodiment B3 will be described. Fig. 102 shows the configuration of a system in embodiment B3. As shown in Fig. 102, in embodiment B3, a configuration information estimation system according to the present invention is provided in a charger and connected to a charging port. Processing of the configuration information estimation system is executed via the charging port.

[0259] 102, instead of providing the configuration information estimation result DB22 on the charger, the configuration information estimation result DB22 may be provided on the cloud. Also, in the vehicle configuration estimation device 2, one or more functional units other than the message transmission / reception unit 23 may be provided on the cloud. For example, only the ECU function estimation unit 4 in the vehicle configuration estimation device 2 may be provided on the cloud.

[0260] (Example B4) Next, an embodiment B4 will be described. Fig. 103 shows the configuration of a system in embodiment B4. As shown in Fig. 103, in embodiment B4, a configuration information estimation system according to the present invention is provided on an external network, and processing of the configuration information estimation system is executed via the external network.

[0261] (Example C1) Next, an embodiment C1 will be described. The embodiment C1 is an embodiment in which the configuration information estimation system is used for security analysis in a SOC, etc. Fig. 104 is a system configuration diagram in the embodiment C1.

[0262] 104, the system includes a vehicle configuration estimation device 2 connected to an automobile, a configuration information estimation result DB 22, a configuration information acquisition unit 30, a security analysis unit 31, and an analysis result presentation unit 32. Each unit is connected as shown in the figure.

[0263] Configuration information acquisition unit 30 extracts necessary configuration information from configuration information estimation result DB 22 and passes it to security analysis unit 31. Security analysis unit 31 performs more advanced security analysis using the vehicle configuration information estimated by vehicle configuration estimation device 2. Then, it passes the analysis result to analysis result presentation unit 32.

[0264] The analysis result presentation unit 32 receives the analysis results, processes them appropriately, and presents the results to the analyst. Note that the analyst is not limited to a person, and may be a program that uses the analysis results to perform further analysis.

[0265] The security analysis performed by the security analysis unit 31 is not limited to a specific one, but examples thereof include those listed below.

[0266] - Prediction of attack routes using topology information - Estimation of entry points using topology information and software versions of each ECU -Cause estimation using topology information and software versions of each ECU - Prediction of abnormal communication or processes using topology information, software versions of each ECU, and normal communication information - Estimation of impact using topology information, software version of each ECU, information on normal communication, and information on the function of each ECU - Estimation of countermeasures using topology information and software versions of each ECU (Example C2) Next, an embodiment C2 will be described. The embodiment C2 is an embodiment in which the configuration information estimation system is used for asset management. Fig. 105 is a system configuration diagram in the embodiment C2.

[0267] 105, the system includes a vehicle configuration estimation device 2 connected to an automobile, a configuration information estimation result DB 22, a configuration information acquisition unit 30, an asset management unit 33, and a management information presentation unit 34. Each unit is connected as shown in the figure.

[0268] The configuration information acquisition unit 30 extracts necessary configuration information from the configuration information estimation result DB 22 and passes it to the asset management unit 33. The asset management unit 33 holds management information, and performs management based on the received configuration information, such as checking for ECUs not included in the management information or ECUs whose support has expired. At this time, public information such as the support status of ECU software is also used.

[0269] The management information presentation unit 34 acquires the management information from the asset management unit 33, processes it appropriately (for example, extracts and organizes only the device names and address information of ECUs that are not included in the management information), and presents the results to the administrator. Note that the administrator is not limited to a person, and may be a program that performs further analysis using the management information.

[0270] (Example C3) Next, an embodiment C3 will be described. The embodiment C3 is an embodiment in which the configuration information estimation system is utilized for anomaly detection. Fig. 106 is a system configuration diagram in the embodiment C3.

[0271] 106, the system includes a vehicle configuration estimation device 2 connected to an automobile, a configuration information estimation result DB 22, a configuration information acquisition unit 30, and an abnormality detection unit 35. Each unit is connected as shown in the figure.

[0272] The configuration information acquisition unit 30 extracts necessary configuration information from the configuration information estimation result DB 22 and passes it to the anomaly detection unit 35. The anomaly detection unit 35 detects an abnormal state of the vehicle configuration information by using information from a DB in which normal vehicle configuration information is stored, anomaly detection rules, and public information (e.g., information from a vulnerability DB). Furthermore, the anomaly detection result is notified to an analyst such as the vehicle manager or SOC.

[0273] The anomaly detection method is not limited to a specific method, but examples thereof include those listed below.

[0274] The vehicle configuration information stored in the normal vehicle configuration information DB is compared with the vehicle configuration information stored in the configuration information estimation result DB, and any difference is detected as an abnormality.

[0275] An abnormality is detected when the vehicle configuration information stored in the configuration information estimation result DB22 satisfies the anomaly detection rules or has configuration information defined as an abnormal state in public information (vulnerability DB) or the like.

[0276] - Machine learning is used to learn the vehicle configuration information of normal automobiles, and machine learning-based anomaly detection is performed based on the learned model.

[0277] (Example C4) Next, an embodiment C4 will be described. The embodiment C4 is an embodiment in which the configuration information estimation system is utilized for security diagnosis. Fig. 107 is a system configuration diagram in the embodiment C4.

[0278] 107, the system includes a vehicle configuration estimation device 2 connected to an automobile, a configuration information estimation result DB 22, a configuration information acquisition unit 30, a security diagnosis unit 36, and a diagnosis result presentation unit 37. Each unit is connected as shown in the figure.

[0279] The configuration information acquisition unit 30 extracts necessary configuration information from the configuration information estimation result DB 22 and passes it to the security diagnosis unit 36. Based on the received configuration information, the security diagnosis unit 36 ​​performs a diagnosis as to whether or not there is an ECU with a security problem in the automobile. At this time, the presence or absence of a problem is confirmed by using public information such as the support status of the ECU software.

[0280] The diagnostic result presentation unit 37 acquires the diagnostic result from the security diagnostic unit 36, processes it appropriately (for example, converts the diagnostic result into a score, etc.), and presents the result to the administrator. Note that the administrator is not limited to a person, and may be a program that performs further analysis using the management information.

[0281] For example, the ECU model numbers of ECUs with confirmed vulnerabilities and software version information (blacklist) are recorded in the diagnostic rules used by the security diagnostic unit 36. The security diagnostic unit 36 ​​compares the vehicle configuration information (blacklist) stored in the diagnostic rules with the vehicle configuration information in the configuration information estimation result DB 22, and if there is information that corresponds to the blacklist, points out a vulnerability.

[0282] (Hardware configuration example) The device consisting of diagnostic communication transmitting / receiving unit 100, diagnostic log DB 200, and configuration information estimation unit 300 described in the first embodiment, the device consisting of diagnostic communication transmitting / receiving unit 100 and diagnostic log DB 200, the device consisting of diagnostic log DB 200 and configuration information estimation unit 300, the device consisting of diagnostic communication transmitting / receiving unit 100 and configuration information estimation unit 300, the device consisting of diagnostic communication transmitting / receiving unit 100, the device consisting of diagnostic log DB 200, and the device consisting of configuration information estimation unit 300 can all be realized, for example, by causing a computer to execute a program. This computer may be a physical computer or a virtual machine on the cloud.

[0283] The system, device, and functional unit described in the second embodiment can also be realized by, for example, causing a computer to execute a program. This computer may be a physical computer or a virtual machine on a cloud.

[0284] The entity on which the above program runs is called the "device." The device can be realized by executing a program corresponding to the processing performed by the device, using hardware resources such as a CPU and memory built into a computer. The above program can be recorded on a computer-readable recording medium (such as a portable memory) and stored or distributed. The above program can also be provided via a network such as the Internet or email.

[0285] Fig. 108 is a diagram showing an example of the hardware configuration of the computer. The computer in Fig. 108 has a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, and the like, all of which are connected to one another via a bus BS. Note that some of these devices may not be included. For example, a device that does not perform display may not include the display device 1006.

[0286] The program for realizing the processing on the computer is provided by a recording medium 1001 such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via a network. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.

[0287] The memory device 1003 reads out and stores the program from the auxiliary storage device 1002 when an instruction to start the program is received. The CPU 1004 realizes the functions related to the device in accordance with the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network, and functions as a transmitting unit and a receiving unit. The display device 1006 displays a GUI (Graphical User Interface) or the like according to a program. The input device 1007 is composed of a keyboard and mouse, buttons, a touch panel, or the like, and is used to input various operation instructions. The output device 1008 outputs the results of calculations.

[0288] (Effects of the embodiment) As described above, in the embodiment of the present invention, information useful for estimating vehicle configuration information is collected by transmitting and receiving diagnostic communications using a diagnostic communication protocol (DoCAN, DoIP, UDS, etc.) that is supported as standard by each ECU, and the vehicle configuration information is estimated by analyzing the collected information. This makes it unnecessary to increase resources or support a new protocol when estimating vehicle configuration information, and can reduce additional costs.

[0289] (Summary of the embodiment) This specification discloses at least the following network configuration estimation device, network configuration estimation method, and program. (Section 1) A network configuration estimation device that estimates configuration information of an internal network in a target device, A diagnostic communication transmitting / receiving unit that transmits a message to an electronic control unit on the internal network by using a diagnostic communication method supported as a standard by the electronic control unit on the internal network and receives a response to the message; a configuration information estimation unit that estimates configuration information of the internal network based on the response obtained by the diagnostic communication transmission / reception unit; A network configuration estimation device comprising: (Section 2) The configuration information estimation unit a presence confirmation unit that confirms the presence of the electronic control unit on the internal network based on the response; a topology estimation unit that estimates a topology of the internal network based on a result of the presence confirmation of the electronic control unit by the presence confirmation unit; an information extraction unit that extracts information about the electronic control unit on the internal network based on the response; 2. A network configuration estimation device according to claim 1, comprising: (Section 3) the diagnostic communication transceiver transmits a message to each of a first network and a second network in the internal network and receives a response thereto; The configuration information estimation unit confirms the presence of an electronic control unit connected to the first network based on a response to a message transmitted to the first network, and confirms the presence of an electronic control unit connected to the second network based on a response to a message transmitted to the second network. 3. A network configuration estimation device according to claim 1 or 2. (Section 4) The diagnostic communication transmitting / receiving unit transmits a message in which a data ID is set, and receives a response thereto; The configuration information estimation unit extracts information corresponding to the data ID from a response to a message in which the data ID is set. 5. A network configuration estimation device according to claim 1, wherein the network configuration estimation device is a network configuration estimation device for estimating a network topology of a network. (Section 5) A network configuration estimation device that estimates configuration information of an internal network in a target device, a configuration information estimation unit that transmits a message to an electronic control unit on the internal network by using a diagnostic communication method supported as a standard in the electronic control unit on the internal network, and estimates configuration information of the internal network based on a response obtained from a device that receives a response to the message. A network configuration estimation device comprising: (Section 6) A network configuration estimation device that estimates configuration information of an internal network in a target device, A base RTT calculation unit that calculates a round trip time of a first electronic control unit on the internal network by using a diagnostic communication method that is supported as a standard in the electronic control unit on the internal network in a non-congested state; a congestion RTT calculation unit that calculates a round trip time of the first electronic control unit in a congestion state in which a diagnosis request is frequently transmitted to the second electronic control unit; an estimation unit that estimates whether the first electronic control unit and the second electronic control unit are connected to the same bus by comparing a round trip time in the non-congested state with a round trip time in the congested state; A network configuration estimation device comprising: (Section 7) A network configuration estimation device that estimates configuration information of an internal network in a target device, A restart command transmission unit that transmits a restart command to a target electronic control unit on the internal network by using a diagnostic communication method that is supported as a standard in the electronic control unit on the internal network; an alert receiving unit that receives an alert generated due to the restart command from the internal network; an estimation unit that estimates that the ID included in the alert is an ID for normal communication transmitted by the target electronic control device; A network configuration estimation device comprising: (Section 8) A network configuration estimation device that estimates configuration information of an internal network in a target device, A web search unit that searches for functions of the electronic control device using the entire model number of the target electronic control device acquired using a diagnostic communication method supported as standard by the electronic control device on the internal network and digits related to functions in the model number; an estimation unit that estimates a function that maximizes the sum of the support rates of words included in the search results obtained by the web search unit as a function of the target electronic control device; A network configuration estimation device comprising: (Section 9) A network configuration estimation method executed by a network configuration estimation device that estimates configuration information of an internal network in a target device, comprising: sending a message to an electronic control unit on the internal network using a diagnostic communication method supported as a standard by the electronic control unit on the internal network, and receiving a response to the message; estimating configuration information of the internal network based on the response; A network configuration estimation method comprising: (Section 10) A program for causing a computer to function as each unit in the network configuration estimation device according to any one of claims 1 to 8.

[0290] Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims.

[0291] This application claims priority to International Patent Application PCT / JP2020 / 035621, filed on September 18, 2020, the entire contents of which are incorporated herein by reference. [Explanation of symbols]

[0292] 1 In-vehicle NW 2. Component Estimation Section 3 ECU basic information acquisition section 4 ECU function estimation section 6 Web Search Section 7. Websites 8 Search result database 9 Exact match extraction part 10 Specific partial match extraction part 11 Estimation part 12 NW_B Topology Estimation Unit 13 NW_A bus topology estimation section 14 Base RTT calculation section 15 Congestion RTT Calculation Unit 16 RTT comparison section 17 Estimation part 18 Normal NW_A communication estimator 19 Restart command transmitter 20 Vehicle alert receiver 21 Estimation part 22 Configuration information estimation result DB 23 Message sending and receiving section 24 Configuration information acquisition and registration section 30 Configuration information acquisition unit 31 Security Analysis Department 32 Analysis result presentation section 33 Asset Management Department 34 Management information presentation section 35 Anomaly detection unit 36 Security Diagnostics Department 37 Diagnosis result display section 500 ECU 100 Diagnostic communication transmission / reception unit 200 Diagnostic log database 300 Configuration Information Estimation Unit 310 ECU existence confirmation part 320 Topology Estimation Unit 330 ECU information extraction section 340 Output section 400 Automobiles 1000 Drive Device 1001 Recording media 1002 Auxiliary storage device 1003 Memory device 1004 CPU 1005 Interface device 1006 Display device 1007 Input Device 1008 Output device

Claims

1. A network configuration estimation device that estimates configuration information of an internal network in a target device, A diagnostic communication transmitting / receiving unit that transmits a message to an electronic control unit on the internal network by using a diagnostic communication method supported as a standard by the electronic control unit on the internal network and receives a response to the message; a configuration information estimation unit that estimates the configuration information including a topology of the internal network based on the response obtained by the diagnostic communication transmission / reception unit and publicly known information on a connection method; A network configuration estimation device comprising:

2. The configuration information estimation unit a presence confirmation unit that confirms the presence of the electronic control unit on the internal network based on the response; a topology estimation unit that estimates a topology of the internal network based on a result of the presence confirmation of the electronic control unit by the presence confirmation unit; an information extraction unit that extracts information about the electronic control unit on the internal network based on the response; The network configuration estimation device according to claim 1 , comprising:

3. the diagnostic communication transmitting / receiving unit transmits a message to each of a first network and a second network in the internal network and receives a response thereto; The configuration information estimation unit confirms the presence of an electronic control unit connected to the first network based on a response to a message transmitted to the first network, and confirms the presence of an electronic control unit connected to the second network based on a response to a message transmitted to the second network. The network configuration estimation device according to claim 1 .

4. The diagnostic communication transmitting / receiving unit transmits a message in which a data ID is set, and receives a response thereto; The configuration information estimation unit extracts information corresponding to the data ID from a response to a message in which the data ID is set. The network configuration estimation device according to claim 1 .

5. A network configuration estimation device that estimates configuration information of an internal network in a target device, A configuration information estimation unit that transmits a message to an electronic control unit on the internal network using a diagnostic communication method supported as standard by the electronic control unit on the internal network, and estimates the configuration information including the topology of the internal network based on the response to the message obtained by a device that receives the response and publicly known information on a connection method. A network configuration estimation device comprising:

6. A network configuration estimation device that estimates configuration information of an internal network in a target device, A base RTT calculation unit that calculates a round trip time of a first electronic control unit on the internal network by using a diagnostic communication method that is supported as a standard in the electronic control unit on the internal network in a non-congested state; a congestion RTT calculation unit that calculates a round trip time of the first electronic control unit in a congestion state in which a diagnosis request is frequently transmitted to the second electronic control unit; an estimation unit that estimates whether the first electronic control unit and the second electronic control unit are connected to the same bus by comparing a round trip time in the non-congested state with a round trip time in the congested state; A network configuration estimation device comprising:

7. A network configuration estimation device that estimates configuration information of an internal network in a target device, A restart command transmission unit that transmits a restart command to a target electronic control unit on the internal network by using a diagnostic communication method that is supported as a standard in the electronic control unit on the internal network; an alert receiving unit that receives an alert generated due to the restart command from the internal network; an estimation unit that estimates that the ID included in the alert is an ID of a normal communication transmitted by the target electronic control device; A network configuration estimation device comprising:

8. A network configuration estimation device that estimates configuration information of an internal network in a target device, A Web search unit that searches for functions of the electronic control device using the entire model number of the target electronic control device acquired using a diagnostic communication method supported as standard by the electronic control device on the internal network and digits related to functions in the model number; an estimation unit that estimates a function having a maximum sum of support degrees of words included in the search results obtained by the web search unit as a function of the target electronic control device; A network configuration estimation device comprising:

9. A network configuration estimation method executed by a network configuration estimation device that estimates configuration information of an internal network in a target device, comprising: sending a message to an electronic control unit on the internal network using a diagnostic communication method supported as a standard by the electronic control unit on the internal network, and receiving a response to the message; estimating the configuration information including the topology of the internal network based on the response and publicly known information of a connection method; A network configuration estimation method comprising:

10. A program for causing a computer to function as each unit in the network configuration estimation device according to any one of claims 1 to 8.

Citation Information

Patent Citations

  • Security vulnerability detection method and device, storage medium and intelligent equipment

    CN110908357A

  • Diagnosis system for on-vehicle network, and on-vehicle control device

    JP2007099145A

  • Apparatus for diagnosing communication of a vehicle, system having the same and method thereof

    KR1020200143961A

  • Method and system for enhanced scanner user interface

    US20140188330A1

  • Information update device and information update method

    WO2019073932A1