JP2001301572A - Method for imparting identification code of on-vehicle ecu and on-vehicle ecu - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for imparting an identification code of an on- vehicle ECU enabling the simplification of working processes and cost reduction. SOLUTION: An engine ECU 10 and a security ECU 20 are interconnected in such a manner as to enable serial communications therebetween. A vehicle ID (vehicle identification code) and an ECU-ID (ECU identification code) are stored in the flash ROM 12 of the engine ECU 10, and the flash ROM 22 of the security ECU 20 also stores the ECU-ID as does the flash ROM of the engine ECU 10. If there is an ID write request from an external tool 40 during assembly of the ECU in the engine or replacement of the ECU, the vehicle ID transmitted from the external tool 40 is written in the flash ROM 12 in the engine ECU 10. Subsequently, the vehicle ID is processed to originate an ECU-ID, which is then written in the flash ROM 12.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of assigning an ECU identification code for individually identifying ECUs mounted on a vehicle, and to executing security processing for preventing vehicle theft using the ECU identification code. The present invention relates to a vehicle-mounted ECU device.

[0002]

2. Description of the Related Art Conventionally, a vehicle identification code (vehicle ID) unique to a vehicle is assigned to each vehicle, and a predetermined repair work or the like is performed by a dealer or the like using the vehicle ID. There is also known a technique in which a vehicle ID is written in a memory (flash ROM or the like) of an in-vehicle ECU, and the vehicle ID in the memory is appropriately read out and used by an external tool.

In recent years, various in-vehicle ECU devices having a vehicle anti-theft function (security function) have been proposed. For example, in an in-vehicle ECU device including an engine control ECU that controls an in-vehicle engine and a security ECU that determines whether or not the engine was operated in a regular procedure when starting the engine, a security ECU is provided.
Determines that the door lock has been unlocked normally and that the ignition key has been turned on, and sends a start permission signal to the engine control ECU indicating that the start is permitted. The engine control ECU receives the start permission signal and starts control of fuel injection and ignition.

A start permission signal transmitted from the security ECU to the engine control ECU is transmitted to an external (third party).
It is conceivable to encrypt the signal so that the signal is not leaked. In this case, the start permission signal may be encrypted using the above-described vehicle ID. However, since the vehicle ID may be described (engraved) on the vehicle body, there is a risk that the encryption may be analyzed. Therefore, it has been considered to generate an identification code different from the vehicle ID inside the ECU and encrypt the start permission signal with the identification code inside the ECU. That is, this identification code is given as a unique identification code (ECU-ID) to each engine control ECU, and the code is less likely to be leaked to the outside.
The reliability of the security function is improved. This ECU
-The ID is used for the vehicle anti-theft function,
It is also used to prevent unauthorized alteration of

[0005]

However, in the above-mentioned prior art, the ECU-ID is usually generated in the manufacturing process of the ECU maker, and the ECU built-in memory (flash RO) is used.
M), the vehicle ID is generated when the vehicle manufacturer incorporates the vehicle-mounted ECU device into the vehicle,
Similarly, it is written into the ECU built-in memory. Therefore, there is a problem that the number of steps for writing each piece of code information increases, and the cost increases accordingly.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and an object of the present invention is to provide a method for assigning an identification code for an in-vehicle ECU which can simplify a working process and reduce costs. To provide.

[0007]

According to the first aspect of the present invention, when the vehicle identification code (vehicle ID) is assigned, the ECU identification code (ECU-ID) is generated and assigned at the same time. There is no need for a separate step for assigning the identification code, and the working steps can be simplified and the cost can be reduced.

[0008] In this case, the vehicle identification code is unique to the vehicle and does not overlap in a plurality of vehicles. Therefore, as described in the second and third aspects, the ECU identifies the vehicle based on the vehicle identification code. By generating an identification code,
Duplicate ECU identification codes can be avoided. Therefore, an appropriate ECU identification code can be assigned.
In particular, by performing the writing process of the ECU identification code obtained by processing the vehicle identification code following the writing process of the vehicle identification code (claim 1 + 2), the operation is simplified and the practical effect is improved.

The invention according to claim 4 relates to an in-vehicle ECU device including an in-vehicle engine control ECU and a security ECU, wherein the engine control ECU includes any one of claims 1 to 3. The ECU identification code is assigned using the method described in (1) or (2). And this E
The CU identification code is transmitted to and stored in the security ECU. The security ECU uses the ECU identification code to generate a code indicating whether the starting operation was a normal procedure and transmits the code to the engine control ECU, and the engine control ECU receives the code from the security ECU. It is determined whether the start of the engine is permitted or prohibited according to the code. In such cases,
Desired security processing using the ECU identification code becomes possible.

[0010]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is an overall circuit configuration diagram schematically showing a vehicle anti-theft device to which the present invention is applied.

This device has an engine EC as a main configuration.
U10 and a security ECU 20.
The CUs 10 and 20 are connected to each other so that serial communication is possible. The engine ECU 10 includes a well-known logical operation circuit including a CPU 11, a flash ROM 12, a RAM 13, and the like. Similarly, security ECU
20 is a CPU 21, a flash ROM 22, a RAM 2
Consists of 3 mag.

The engine ECU 10 fetches detection results from a sensor group (not shown) to detect an engine operating state, and controls fuel injection and ignition timing based on the detected operation state. That is, the ECU 10 outputs a control signal to the injector 31 and the igniter (ignition device) 32 after the engine is started, thereby controlling the operating state of the engine.

The flash ROM 1 of the engine ECU 10
2 includes a vehicle ID (vehicle identification code) and an ECU-ID
(ECU identification code) is stored, and each vehicle can be identified by the vehicle ID. Further, each engine ECU can be identified by the ECU-ID. In particular, the ECU-ID stored only as memory data has a low possibility of being leaked to the outside, and is used for preventing theft of a vehicle and preventing unauthorized modification of memory data.

On the other hand, in the security ECU 20,
A security program is stored in the flash ROM 22 in advance, and the CPU 21 unlocks the vehicle door in a regular procedure according to the security program.
Further, it is determined whether an ignition key (hereinafter, referred to as an IG key) 33 operated by the vehicle driver is a regular key. That is, the door key switch 35 is connected to the security ECU 20, and the door key switch 35 is turned on when the lock of the vehicle door is released by a proper door key.

The IG key 33 has a built-in memory 33a for storing a predetermined security code set for each vehicle, and the key cylinder 34 reads the security code built in the IG key and secures the security code. ECU2
Transfer to 0. On the other hand, the security code stored in the flash ROM 22 of the security ECU 20 is the same as the security code stored in the flash ROM 22, and the security ECU 20 stores the security code stored in the IG key read by the key cylinder 34 and the security code stored in the flash ROM 22. To determine the regular key.

The flash ROM 22 of the security ECU 20 has the same EC number as the engine ECU 10.
The U-ID is stored, and the CPU 21 generates a code for giving permission to start the engine using the ECU-ID, and transmits the code to the engine ECU 10.

The starter 36 is connected to the security ECU 20
The engine is driven by a starter permission signal from the controller and receives a + B voltage from a battery (not shown) to rotate and crank the engine. When the IG key 33 is turned on,
When an IG key switch (not shown) is turned on, the power supply voltage (+ B voltage) from the vehicle battery is supplied to each of the ECUs 10 and 20 and the starter 36.

The external tool 40 is an external device used by vehicle manufacturers, dealers, and the like.
Used by connecting to 10 connection ports. As one function, the external tool 40 includes a vehicle ID assigned to each vehicle.
Is transmitted to the engine ECU 10.

The operation of the system having the above configuration will be described below. FIG. 2 is a flowchart showing a procedure for generating the ECU-ID, and this process is executed by the engine ECU 10 at the time of startup. That is, FIG. 2 shows a process of generating the ECU-ID from the vehicle ID when the ECU is assembled into the engine or when the ECU is replaced. By the way, before writing the ECU-ID, the ECU-ID
Is set to the initial value "H'0000 0000 0000 0000".

More specifically, referring to FIG.
In step 1, it is determined whether there is a request to write a vehicle ID from the external tool 40.
Proceeding to step 102, the vehicle ID transmitted from the external tool 40 is stored in the flash RO in the engine ECU 10.
Write to M12.

In the following step 103, the ECU-ID in the flash ROM 12 is set to the initial value (H'0000 000).
0 0000 0000). This determination is
This is performed to prevent the ECU-ID from being overwritten. If step 103 is YES, the process proceeds to step 104, where ECU-ID is created and flash RO
Write to M12. Here, the ECU-ID is created by processing the vehicle ID, and is created according to the following equation as an example. ECU-ID = (Vehicle ID *
H'1000 0000) + year + month + day + hour + minute + second, that is, ECU-
An ID is created, so that each engine ECU 10 can assign a different ECU-ID. However, ECU-I
D need only be an identification code unique to each engine ECU 10 and can be created by a method other than the above equation.

On the other hand, the function of preventing vehicle theft includes the ECU-ID created by the engine ECU 10 as described above.
Is also stored on the security ECU 20 side, and the security ECU 20 generates and outputs a code for permitting or prohibiting the engine start using the ECU-ID. In the following, the security ECU 20 uses the ECU-ID
For storing and storing the information (the flowchart of FIG. 3), the ECU
The procedure for determining whether to permit the start of the engine using the ID (the flowcharts in FIGS. 4 and 5) will be sequentially described.

First, the security ECU 20 has an EC
A procedure for storing the U-ID will be described. Here, FIG.
FIG. 3A shows processing on the security ECU 20 side, and FIG.
(B) shows the processing on the engine ECU 10 side.

3A is started when the power to the security ECU 20 is turned on. First, at step 201, the flash ROM 22 in the security ECU 20 is started.
It is determined whether or not the ECU-ID has already been stored. For example, when the ECU-ID is created by the engine ECU 10 when the ECU is assembled, the security EC
If the ECU-ID is not stored in U20, step 2
01 is NO and the routine proceeds to step 202. Step 20
In 2, the ECU requests the engine ECU 10 to transmit the ECU-ID.

At this time, on the engine ECU 10 side, as shown in FIG.
It is determined whether a CU-ID transmission request has been made (step 301).
The ECU-ID in the control unit 12 is transmitted to the security ECU 20 (step 302).

After the transmission request in step 202, the security ECU 20 determines in step 203 whether the ECU-ID has been received from the engine ECU 10. If YES, the process proceeds to step 204, where the received ECU-ID is stored in the flash ROM 22. After the ECU-ID is stored, step 201 becomes YES, and the processing of steps 202 to 204 is passed.

Next, a procedure for determining whether to permit the start of the engine using the ECU-ID will be described. FIG. 4 is a flowchart showing a security program executed on the security ECU 20 side, and FIG.
5 is a flowchart illustrating a start permission determination program executed on the CU 10 side.

The process of FIG. 4 is started when the security ECU 20 is reset. First, in steps 401 to 403, preconditions for determining whether or not the vehicle door has been unlocked in a regular procedure are confirmed. In step 401, the EC in the flash ROM 22
It is determined whether the U-ID is not the initial value. In step 402, it is determined whether or not a door key switch (not shown) is turned on. The door key switch is a switch that is turned on when the door lock of the vehicle is released by a regular door key of the owner of the vehicle. In step 403, the personal identification code in the IG key is compared with the personal identification code in the flash ROM 22 to determine whether or not both match.

According to steps 401 to 403, E
Only when the CU-ID is not kept at the initial value and the vehicle door is unlocked in a regular procedure, all the determination results are YE.
It becomes S.

If all of the steps 401 to 403 are YES, the process proceeds to a step 404, where a code β is generated using the ECU-ID as a code indicating that the vehicle door has been unlocked in a regular procedure. If any of Steps 401 to 403 is NO, the process proceeds to Step 406, and a code γ is generated using the ECU-ID as a code indicating that the vehicle door has not been unlocked in a regular procedure. . As an example, the encryptions β and γ are generated by the following equations. Encryption β = (ECU-ID) −constant B Encryption γ = (ECU-ID) + constant C (where B ≠
C) Further, following the generation of the encryption β in step 404, in step 405, a signal to permit the starter to start is transmitted to the starter 36. Then, in step 407, the encryption (β or γ) is transmitted to the engine ECU 10.

On the other hand, the process of FIG. 5 is started by the engine ECU 10 after the ON operation of the IG key. First, at step 501, it is determined whether fuel injection and ignition have already been permitted (whether or not the start has been permitted). Determine. If it is immediately after the IG key is turned on, step 501 becomes NO and the process proceeds to step 502.

In step 502, the security ECU
It is determined whether or not the cipher transmitted from 20 is β. If the cipher is β, after analyzing the cipher β in step 503, it is determined in step 504 whether or not the analysis result is correct. That is, the security ECU 20 decrypts the ECU-ID stored and held by analyzing the encryption β, and determines whether or not the ECU-ID is correct.

If step 504 is YES, the process proceeds to step 505, where fuel injection and ignition are permitted. That is, the starting permission is given. Step 502 or 504
If any of the above is NO, the routine proceeds to step 506, where fuel injection and ignition are prohibited. After the start is permitted, step 501 becomes YES, and the start permitted state is continued.

According to the embodiment described above, the following effects can be obtained. When the vehicle ID (vehicle identification code) is written into the flash ROM 12 of the engine ECU 10, an ECU-ID (ECU identification code) is generated and written into the flash ROM 12 in the subsequent processing. There is no need for a step, and the working steps can be simplified and the cost can be reduced.

In this case, since the vehicle ID is unique to the vehicle, the generation of the ECU-ID based on the vehicle ID prevents the ECU-ID from being duplicated. Also, in particular,
ECU-ID based on vehicle ID and date / time / minute / second when ID was created
Therefore, different ECU-IDs can be assigned to all engine ECUs 10.

Further, since the engine ECU 10 and the security ECU 20 perform the above-described security processing (the processing of FIGS. 4 and 5) using the ECU-ID, highly reliable security processing can be performed.

The present invention can be embodied in the following forms other than the above. In the above embodiment, as “Summary 1”,
The vehicle ID is stored in the flash ROM 1 in the engine ECU 10.
After the process of writing to the ECU 2, the ECU-ID is created and written to the flash ROM 12, and the "Summary 2" is further referred to as ECU-ID based on the vehicle ID.
However, only one of the abstracts 1 and 2 may be embodied as a requirement. That is, (1) the vehicle ID is stored in the flash R in the engine ECU 10;
In-vehicle ECU that creates an ECU-ID and writes it to the flash ROM 12 following the process of writing to the OM 12
apparatus. (2) In-vehicle E that generates ECU-ID based on vehicle ID
CU device. Alternatively, each of these may be embodied and implemented independently.

The ECU-I created as in the above embodiment
D can be applied not only to the prevention of vehicle theft, but also to the prevention of unauthorized alteration. Also in this case, by using the ECU-ID that is less likely to be leaked to the outside, it is possible to appropriately prevent unauthorized modification of ECU data.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an outline of a vehicle antitheft device according to an embodiment of the invention.

FIG. 2 is a flowchart showing a procedure for creating an ECU-ID by an engine ECU.

FIG. 3 is a flowchart showing a procedure for storing an ECU-ID in a security ECU.

FIG. 4 is a flowchart showing a security program by a security ECU.

FIG. 5 is a flowchart showing a start permission determination program by an engine ECU.

[Explanation of symbols]

10: Engine ECU, 12: Flash ROM, 20
... Security ECU, 22 ... Flash ROM, 40
... external tools.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Kia Archer United Kingdom Hearts Hat Fields Bishop Square 1 Denso Sales United Kingdom Limited F-term (reference) 2E250 AA21 BB08 BB66 DD06 FF27 FF35 HH01 JJ05 LL00 PP15 SS01 SS04 TT04

Claims (4)

[Claims] 1. A procedure for writing a vehicle identification code assigned to each vehicle to a nonvolatile memory, followed by an ECU for individually identifying the ECUs.
A method of generating an identification code and writing the identification code in a nonvolatile memory. 2. The method according to claim 1, wherein the ECU identification code is generated based on the vehicle identification code. 3. An on-vehicle ECU identification code assigning method, wherein an ECU identification code for individually identifying an ECU is generated based on a vehicle identification code. 4. An ECU identification code for identifying an ECU for controlling an in-vehicle engine using the method according to any one of claims 1 to 3, wherein the ECU identification code is used when starting the engine. An in-vehicle ECU that is transmitted to and stored in a security ECU that determines whether or not the start procedure is a normal procedure. The security ECU generates a code that indicates whether or not the start operation is a normal procedure using the ECU identification code. With the engine control EC
U, and the engine control ECU sends the security E
An in-vehicle ECU device that determines whether to allow or prohibit starting of an engine according to a code received from a CU.