Handling device and method of security data
Abstract
A handling device of security data (for example, a portable unit ID) of a vehicle comprises: an in-vehicle unit having a portable unit authenticating unit, an EEPROM, a ROM, and a controller; a vehicle having the in-vehicle unit, a door locking mechanism, and a communication unit; and a portable unit for locking or unlocking the door locking mechanism of the vehicle. In the above device, an encryption unit for encrypting the security data with a cipher key is interposed between the controller and the EEPROM, the security data (portable unit ID) is encrypted with the cipher key and stored into the EEPROM, according to the instruction from the controller based on the authentication result of the portable unit authenticating unit, and the cipher key is stored into the ROM.

Term
Term ended
Projected expiry passed 15 October 2023, 2.9 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
5 claims: 2 independent, 3 dependent
- 1A handling device of security data comprising:an in-vehicle unit having a portable unit authenticating unit, a nonvolatile memory, and a controller;a vehicle having the in-vehicle unit, an in-vehicle system, and a communication unit;and a portable unit for giving a control instruction to the in-vehicle system of the vehicle through communication with the communication unit, in which an encryption unit for encrypting the security data of the vehicle with a cipher key is interposed between the controller and the nonvolatile memory of the in-vehicle unit, and the security data is encrypted with the cipher key and stored into the nonvolatile memory according to the instruction from the controller.
- 5A handling method of security data of a vehicle provided with an in-vehicle unit having a portable unit authenticating unit, a nonvolatile memory, and a controller, a vehicle having the in-vehicle unit, a door locking mechanism, and a communication unit, and a portable unit for locking or unlocking the door locking mechanism of the vehicle through communication with the communication unit, the method comprising a step of encrypting the security data with a cipher key in an encryption unit provided between the controller and the nonvolatile memory of the in-vehicle unit, and a step of storing the encrypted signal into the nonvolatile memory and storing the cipher key into another nonvolatile memory than the above nonvolatile memory.
Independent claims2
31 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
Field of the invention
The present invention relates to a technique for handing security data such as an ID code and a cipher key in remote keyless entry (RKE), when automatically locking or unlocking the door of a vehicle according to communication with a portable unit.
Description of the Related Art
Fig. 3 shows a block structure of remote keyless entry (RKE) and a method of handling the security data such as an ID code and a cipher key. In Fig. 3, a vehicle 1 has a door locking mechanism 5 and a detector 4 for detecting open/close of a door. Further, an in-vehicle unit 2 is set within the vehicle 1. In the in-vehicle unit 2, a portable unit authenticating unit 6 authenticates the ID of the portable unit after receiving a door locked signal or a door unlocked signal from the portable unit 20 through a portable unit receiving/transmitting antenna 3, and as a result of the authentication, when the ID is authenticated, a general controller 7 controls the door locking mechanism so as to lock or unlock the door. Here, an EEPROM 9 stores the ID (vehicle ID and portable unit ID) and the cipher key (the portable unit communicates with the vehicle through a signal encrypted by the cipher key) and a ROM 8 stores a program for general control.
Hitherto, as the remote keyless entry (RKE) for locking or unlocking the door locking mechanism of a vehicle, there are known a manual RKE that is one-way communication from a portable unit to an in-vehicle unit as well as a passive PKE that is two-way communication between a portable unit and an in-vehicle unit. This passive PKE is to lock or unlock the door of a vehicle automatically and do the two-way communication between a portable unit a user carries and an in-vehicle unit set in the vehicle, and as a result of the recognition of the portable unit ID and the in-vehicle ID, when the in-vehicle unit authenticates the portable unit, it performs the locking or unlocking operation on the door locking mechanism 5. Each of the portable unit and the in-vehicle unit has the unique ID (Identification Code) and cipher key (Key) in order to authenticate with each other, and at a communication time, they communicate with each other through a signal obtained by encrypting the data including the ID with the cipher key.
In description of the concrete function of the passive PKE, the in-vehicle unit 2 transmits a request signal at regular intervals. The request signal, including the in-vehicle ID, can arrive at only a short distance. When the portable unit 20 is out of the reach of a request signal, it cannot receive the request signal. While, when a person carrying the portable unit approaches the vehicle, coming into the reach of a request signal, the portable unit receives the request signal, checks the in-vehicle ID included in the request signal, and sends a response signal to the vehicle after confirming that it has been issued from the correct in-vehicle unit.
The in-vehicle unit receives the response signal, takes out the portable unit ID included therein, and compares it with the portable unit ID registered in a memory. In the case of agreement, it issues an unlocking signal to the door locking mechanism 5, to unlock (release) the door, while in the case of disagreement, it does not issue any control signal to the locking mechanism. When a user carrying the portable unit gets off the vehicle and goes far away, the in-vehicle unit issues a locking signal to the door locking mechanism at the point when the portable unit is not in a position to receive a request signal, namely, at the point when the in-vehicle unit is not in a position to receive a response signal.
A request signal and a response signal are encrypted with the cipher key stored by the portable unit and the in-vehicle unit in common and issued, and a receiving party decodes the signal with the cipher key stored by its own self.
Since the security data such as the ID and the cipher key should be kept in a memory even if a battery is removed, it is stored in a nonvolatile memory such as an EEPROM or a ROM. The data stored into the EERPOM or the ROM indicates the information value in the form of the original data. Especially, in the in-vehicle unit, it is stored in the EEPROM not in the ROM, because of the peculiar situation of the portable unit ID as follows. The peculiar situation means that the portable unit ID is not initially stored in the in-vehicle, but that the in-vehicle unit, receiving a response signal from some portable unit (one vehicle includes a plurality of portable units having various IDs), analyzes the signal, takes out the portable unit ID previously stored in the same portable unit, and stores it into the self nonvolatile memory.
Since a car dealer and a user can do this work at any time, it is not necessary to make a match (pairing) of a portable unit and an in-vehicle unit in a manufacturing facility advantageously. However, since the ID will be registered afterward as mentioned above, ROM cannot be used as the storing medium. Further, through a signal transmitted from one to the other in the in-vehicle unit and the portable unit, the cipher key will be also registered in the other afterward (although Fig. 3 doesn't show a memory in the portable unit, the portable unit has a memory), and therefore, it will be stored in the EEPROM not in the ROM.
SUMMARY OF THE INVENTION
In the above-mentioned conventional technique, since the ROM as a nonvolatile memory adopts the structure of preventing others from decoding the stored contents of the ROM, it takes a lot of time and trouble to decode the above even if others try to do. On the contrary, generally, the EEPROM is comparatively easy to analyze its stored contents, if according to the specification of the IC because of its structure. Accordingly, when the data of the portable ID and the cipher key stored in the EEPROM is decoded by others and its rule is analyzed by others, there is a fear of causing the collapse of the securities of many cars. In the conventional technique, there has been a problem from the viewpoint of the security of a car because the security data such as the ID and the cipher key is stored in the EEPROM as it is with no change of value.
An object of the invention is to prevent others from decoding the security data, even if reading the data, by encrypting the security data to be stored in the EEPROM and/or the ROM that is a nonvolatile memory before storing the above.
In order to solve the above problem, the invention adopts the following structure.
A handling device of security data comprises: an in-vehicle unit having a portable unit authenticating unit, a nonvolatile memory, and a controller; a vehicle having the in-vehicle unit, an in-vehicle system, and a communication unit; and a portable unit for giving a control instruction to the in-vehicle system of the vehicle through communication with the communication unit, in which device an encryption unit for encrypting the security data of the vehicle with a cipher key is interposed between the controller and the nonvolatile memory of the in-vehicle unit, and the security data is encrypted with the cipher key and stored into the nonvolatile memory according to the instruction from the controller. Further, a handling method of security data of a vehicle provided with the in-vehicle unit having the portable unit authenticating unit, the nonvolatile memory, and the controller, the vehicle having the in-vehicle unit, a door locking mechanism, and the communication unit, and the portable unit for locking or unlocking the door locking mechanism of the vehicle through communication with the communication unit, comprises a step of encrypting the security data with a cipher key in an encryption unit provided between the controller and the nonvolatile memory of the in-vehicle unit, and a step of storing the encrypted signal into the nonvolatile memory and storing the cipher key into another nonvolatile memory than the above nonvolatile memory. According to the handling device or method of the security data, since the security data is stored in the nonvolatile memory in the form of the signal encrypted with the cipher key, there is no fear that the security data of the vehicle may be decoded by others.
In the handling device of security data, the cipher key is stored in another nonvolatile memory than the nonvolatile memory storing the encrypted signal of the security data. In the handling device of security data, the security data includes a portable unit ID, the nonvolatile memory is an EEPROM, and the other nonvolatile memory is a ROM. According to the above structure, since the cipher key is kept in the nonvolatile memory such as the ROM whose data is difficult to decode, in handing the security data such as the portable unit ID, there is no fear that the cipher key may be read out by others.
BRIEF DESCRIPTION OF THE DRAWINGS
<ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 is a block diagram showing a system of handling the security data such as an ID code and a cipher key in remote keyless entry, according to an embodiment of the invention.</li><li>Fig. 2 is a flow chart showing the flow of storing the security data into the EEPROM, according to the embodiment.</li><li>Fig. 3 shows a block structure of remote keyless entry and a method of handling the security data such as an ID code and a cipher key, according to the conventional technique.</li></ul>
DESCRIPTION OF THE PREFERRED EMBODIMENT
A device and a method of handling the security data according to an embodiment of the invention will be described with reference to Fig. 1 and Fig. 2. Fig. 1 is a block diagram showing a handling system of the security data such as an ID code and a cipher key in remote keyless entry, according to the embodiment of the invention, and Fig. 2 is a view showing a flow of storing the security data into the EEPROM, according to the embodiment.
In the drawings, the reference numeral 1 designates a vehicle, 2 designates an in-vehicle unit, 3 designates a portable unit receiving/transmitting antenna, 4 designates a door open/close detector, 5 designates a door locking mechanism (in-vehicle system), 6 designates a portable unit authenticating unit, 7 designates a general controller, 8 designates a ROM, 9 designates an EEPROM (Electrically Erasable Programmable Read-Only Memory), 10 designates a data encryption controller, 20 designates a portable unit, 21 designates an antenna of portable unit, and 22 designates an EEPROM within the portable unit.
In Fig. 1, the vehicle 1 and the portable unit 20 form passive keyless entry which automatically locks or unlocks a door through two-way communication between the in-vehicle unit 2 and the portable unit 20 with assured management and security of the vehicle. Namely, when the portable unit 20 is in the reach of a request signal from the in-vehicle unit 2, the portable unit 20 issues a response signal upon receipt of the request signal, while the in-vehicle unit 2 releases (unlocks) the door lock as a result of the ID check upon receipt of the response signal. Further, when the portable unit 20 is moved far away from the vehicle 1, the in-vehicle unit 2 gives the door locking mechanism 5 an operation to lock the door when it is not in a position to receive a response signal from the portable unit 20.
More specifically, the in-vehicle unit 2 transmits a request signal including the in-vehicle unit ID to the portable unit 20 through the antenna 3 at regular intervals, while the portable unit 20 transmits a response signal including the portable unit ID to the in-vehicle unit 2 through the antenna 21, in a manner of the two-way communication. The portable unit authenticating unit 6 of the in-vehicle unit 2 compares the portable unit ID included in the response signal from the portable unit 20 with the portable unit ID previously stored in the EEPROM 9. In the case of agreement, the general controller 7 releases the door lock by issuing an unlocking signal to the door locking mechanism 5, while in the case of disagreement, the general controller 7 never issues the unlocking signal to the door locking mechanism 5 and never releases the door lock.
The request signal from the in-vehicle unit 2 and the response signal from the portable unit 20 are encrypted with a first cipher key stored in both the portable unit and the in-vehicle unit and issued, and in a receiving party, the request signal or the response signal is decoded with the first cipher key stored in the receiving party.
In use of the remote keyless entry (RKE), the portable unit ID included in a response signal is newly registered in the in-vehicle unit, by setting the in-vehicle unit at the ID register mode, to analyze a response signal issued by the portable unit 20, take out the corresponding portable unit ID, and store it in the EEPROM 9. In short, a prescribed portable unit ID is not previously stored in the in-vehicle unit 2, but the portable ID of a portable unit is learned and stored. Thus, it is necessary to store a portable unit ID before use of the RKE, not simultaneously with completion of the manufacture of an in-vehicle unit. Therefore, the portable unit ID is stored in a nonvolatile memory, not in the ROM but in the EEPROM.
The EEPROM 9 of the vehicle 1 in Fig. 1 stores the in-vehicle unit ID of the corresponding vehicle other than the portable unit IDs attached to a plurality of portable units for the corresponding vehicle, as mentioned above. Each different ID may be attached to each portable unit, the same ID may be attached to the portable units, or ID different in every group may be attached.
The ID (portable unit ID and in-vehicle unit ID) stored in the EEPROM 9 is a signal encrypted with a second cipher key by the data encryption controller 10, and this is one of the characteristic points of the invention. If ID is stored in the EEPROM directly in the form of its original signal like the conventional technique, there is such a fear that the ID may be decoded by others because of the structure of the EEPROM, which is a serious problem from the viewpoint of security of the vehicle. According to the invention, since ID is encrypted with the second cipher key and stored in the EEPROM 9, the ID cannot be decoded even if the data is read out by others. Together with the first cipher key for a request signal and a response signal, the second cipher key is also stored in the ROM 8 whose data is difficult to decode.
Fig. 2 shows a flow of taking out the portable unit ID included in a response signal from a portable unit and storing it into the EEPROM. When an instruction to store the data (for example, the portable unit ID) into the EEPROM is issued by the general controller 7 (Step 1), the data encryption controller 10 encrypts the security data (Step 2) by using some function f2 (E-Key, data)=E-data. The f2 (x, y) is the encryption function by using the second encryption key, <i>E-Key</i> is the cipher key for encrypting the data to be stored into the EEPROM, data is the security data to be stored into the EEPROM, and <i>E-data</i> is to be obtained by encrypting the <i>data</i> so as to be stored into the EEPROM. Then, the encrypted data is decoded by using the function f2<sup>-1</sup> (E-Key, E-data)=data. The encrypted data is stored in the EEPROM in Step 3.
As mentioned above, according to the invention, data (for example, a request signal and a response signal) used for the communication between an in-vehicle unit and a portable unit is encrypted with the first cipher key and the security data (for example, ID) to be stored in the EEPROM, not in the ROM is encrypted with the second cipher key, hence to prevent others from decoding the data. Here, the first cipher key and the second cipher key are both stored into the ROM whose data is difficult to decode.
Although the above description has been made, by way of example, in the case of storing the portable unit ID into the EEPROM 9 of the in-vehicle unit, the in-vehicle unit ID is also stored in the EEPROM 9, in addition to the portable unit ID, and this in-vehicle unit ID is also encrypted with the second cipher key. Further, the portable unit 20 may be provided with the EEPROM 22 and some controller not illustrated and the in-vehicle unit ID and the corresponding portable unit ID may be encrypted and stored in this nonvolatile memory.
Although the above description has been made, by way of example, by using the passive RKE for issuing a request signal at regular intervals, a trigger switch may be provided in a door handle, and the operation of the trigger switch may cause the transmission of a request signal. Further, although the description has been made, by way of example, in the case where the in-vehicle system is the door locking mechanism, the in-vehicle system is not restricted to this, but it may be the other device such as an engine starter. In the case of the engine starter, the trigger switch may be built in the ignition cylinder for inserting a mechanical key or it may be built as a single switch.
According to the invention, since the security data is stored in the form of a signal encrypted with a cipher key, when storing it into a nonvolatile memory, there is no fear that the security data of a vehicle may be decoded by others.
Since the cipher key is stored in a nonvolatile memory such as a ROM whose data is difficult to decode, there is no fear that the cipher key may be read by others.
Further, also in the communication through a request signal and a response signal in the remote keyless entry, the security is assured by encrypting the two-way communication with the other cipher key, and since the other cipher key is stored in a nonvolatile memory such as a ROM whose data is difficult to decode, there is no fear that the other cipher key may be decoded by others.
Contents4
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Category | Cited during | Relevant claims |
|---|---|---|---|---|---|
| US8179230B2 | Cited by | United States of America | – | Applicant | – |
| WO2007074354A1 | Cited by | World Intellectual Property Organization (WIPO) | – | International search | – |
| DE102006034418A1 | Cited by | Germany | – | Search report | – |
| EP0663650A2 | Cites | European Patent Office (EPO) | A | Search report | 1-5 |
| EP0903271A2 | Cites | European Patent Office (EPO) | X | Search report | 1-5 |
| EP1098472A2 | Cites | European Patent Office (EPO) | A | Search report | 1-5 |
| US5392356A | Cites | United States of America | A | Search report | 3,4 |
| US5610574A | Cites | United States of America | A | Search report | 1,5 |
| US5787367A | Cites | United States of America | A | Search report | 1-5 |
| US6043752A | Cites | United States of America | X | Search report | 1 |
| US6384711B1 | Cites | United States of America | A | Search report | 3,4 |
| WO9517739A1 | Cites | World Intellectual Property Organization (WIPO) | A | Search report | 1-5 |
8 members in 4 offices
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 2002301948 | Japan | A | |
| 2002301948 | Japan | – | |
| 2002301948 | – | – | – |
| JP20020301948 | – | – | – |
Members8
| Document | Office | Kind | |
|---|---|---|---|
| EP1411477A1This record | European Patent Office (EPO) | A1 | |
| KR20040034454A | Republic of Korea | A | |
| US2004083374A1 | United States of America | A1 | |
| JP2004137718A | Japan | A | |
| KR100586476B1 | Republic of Korea | B1 | |
| US7426275B2 | United States of America | B2 | |
| JP4153283B2 | Japan | B2 | |
| EP1411477B1 | European Patent Office (EPO) | B1 |
26 legal events, as 3 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Designation fees paidAKX | AKX | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1411477
- Publication, DOCDB
- 1411477
- Publication, EPODOC
- EP1411477
- Application
- 3023557
- Application, DOCDB
- 03023557
- Application, EPODOC
- EP20030023557
Titles3
- German
- Handhabungsvorrichtung und Verfahren für Sicherheitsdaten
- English
- Handling device and method of security data
- French
- Dispositif de manutention et procédé pour données de sécurité
Classification
- CPC, 5
- B60R25/24
- E05B49/00
- G07C9/00309
- G07C2009/0023
- G07C2009/00412
- IPC, 3
- G06F21 62
- G07C9 00
- E05B49 00
Designated states2
- Contracting states, 1
- Türkiye
- Extension states, 1
- North Macedonia