EP2728556B1 - Electronic key registration method, electronic key registration system, and controller - Google Patents
Electronic key registration method, electronic key registration system, and controller Download PDFInfo
- Publication number
- EP2728556B1 EP2728556B1 EP13190424.5A EP13190424A EP2728556B1 EP 2728556 B1 EP2728556 B1 EP 2728556B1 EP 13190424 A EP13190424 A EP 13190424A EP 2728556 B1 EP2728556 B1 EP 2728556B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- key
- electronic
- controller
- code
- encryption
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00571—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by interacting with a central unit
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00817—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the lock can be programmed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00309—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks
- G07C2009/00388—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks code verification carried out according to the challenge/response method
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00309—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks
- G07C2009/00412—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated with bidirectional data transmission between data carrier and locks the transmitted data signal being encrypted
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00817—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the lock can be programmed
- G07C2009/00825—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the lock can be programmed remotely by lines or wireless communication
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00817—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the lock can be programmed
- G07C2009/00841—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the lock can be programmed by a portable device
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C9/00—Individual registration on entry or exit
- G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
- G07C9/00857—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys where the code of the data carrier can be programmed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
Definitions
- the present invention relates to a method and system for registering an electronic key to a controller of a communication subject, and a controller.
- An electronic key system verifies an electronic key by performing wireless communication with an electronic key. When the electronic key is verified, the locking and unlocking of vehicle doors and the starting of the engine is performed. In such an electronic key system, encrypted communication is performed between the electronic key and the vehicle to maintain a certain level of security. This allows for the electronic key to be verified with a high level of confidentiality.
- the common key cryptosystem is one type of an encryption standard.
- an electronic key system that uses the common key cryptosystem, when registering an electronic key to a controller of a vehicle, the electronic key and the vehicle both store the same encryption key.
- the controller uses the encryption key to communicate with and verify the electronic key by comparing identification information that is transmitted from the electronic key with identification information that is stored in the controller.
- Japanese Laid-Open Patent Publication No. 2011-20475 describes an electronic key registration system that registers an electronic key to a controller by storing an encryption key in the controller and the electronic key.
- a data center communicates with the electronic key and the controller to store an encryption key in the electronic key and the controller and associate the electronic key with the controller. This prevents an unauthorized electronic key from being registered to the controller.
- the electronic keys are required to be registered one by one.
- communication is performed between the data center and the electronic key and between the data center and the controller. That is, communication with the data center is repeated for a number of times that is the same as the number of electronic keys that are to be registered. Accordingly, the registration of electronic keys is burdensome. This problem occurs not only when the electronic key system is applied to a vehicle but also when applied to a building such as a house.
- the present invention relates to an electronic key registration method, an electronic key registration system, and controller that facilitate the registration of a plurality of electronic keys while maintaining a certain level of security.
- a first embodiment of the present invention is an electronic key registration method for registering a plurality of electronic keys to a controller of a communication subject through communication with a data center.
- the electronic keys are capable of communicating with the controller.
- the electronic key registration method includes storing communication subject identification information and a communication subject encryption key in the controller.
- the communication subject identification information and the communication subject encryption key are unique to the communication subject.
- the method includes storing the communication subject identification information and the communication subject encryption key in the data center, and storing first key identification information and a first key encryption key in the first electronic key.
- the first key identification information and the first key encryption key are unique to a first electronic key.
- the method also includes storing second key identification information and a second key encryption key in the second electronic key.
- the second key identification information and a second key encryption key are unique to the second electronic key. Further, the method includes storing the first and second key identification information and the first and second key encryption keys in the data center, acquiring the first key identification information from the first electronic key with the controller, acquiring the second key identification information from the second electronic key with the controller, transmitting the communication subject identification information together with the first and second key identification information from the controller to the data center, and generating a first encryption key generation code with the data center. The first encryption key generation code is based on the communication subject encryption key and the first key encryption key. Additionally, the method includes generating a second encryption key generation code with the data center. The second encryption key generation code is based on the communication subject encryption key and the second key encryption key.
- the method includes obtaining the first and second encryption key generation codes together from the data center with the controller, generating the first key encryption key based on the first encryption key generation code with the controller, generating the second key encryption key based on the second encryption key generation code with the controller, and storing the first and second key encryption keys in the controller.
- a second embodiment of the present invention is an electronic key registration system provided with a plurality of electronic keys including first and second electronic keys, a controller arranged in a communication subject and capable of communicating with the electronic keys, and a data center.
- the controller includes a memory that stores commands executed by the controller.
- the commands include commands configured to have the controller acquire first key identification information from the first electronic key, acquire second key identification information from the second electronic key, transmit communication subject identification information together with the first and second key identification information to the data center, acquire a first encryption key generation code corresponding to the first electronic key together with a second encryption key generation code corresponding to the second electronic key from the data center, generate a first key encryption key based on the first encryption key generation code, generate a second key encryption key based on the second encryption key generation code, and store the first and second key encryption keys in the controller.
- a third embodiment of the present invention is a controller arranged in a communication subject.
- the controller is capable of communicating with a data center and a plurality of electronic keys including first and second electronic keys.
- the controller includes a memory that stores commands executed by the controller.
- the commands include commands configured to have the controller acquire first key identification information from the first electronic key, acquire second key identification information from the second electronic key, transmit communication subject identification information together with the first and second key identification information to the data center, acquire a first encryption key generation code corresponding to the first electronic key together with a second encryption key generation code corresponding to the second electronic key from the data center, generate a first key encryption key based on the first encryption key generation code, generate a second key encryption key based on the second encryption key generation code, and store the first and second key encryption keys in the controller.
- the registration of a plurality of electronic keys is facilitated as well as a certain level of security is maintained.
- the vehicle 1 includes an immobilizer system 3 that performs ID verification on an electronic key 2 through, for example, near-field communication.
- the communication distance for near-distance communication is several centimeters.
- the electronic key 2 includes a transponder 4 that serves as an ID tag.
- the transponder 4 is activated by drive radio waves transmitted from a coil antenna 5 of the vehicle 1.
- the ID verification of the electronic key 2 is performed based on a key ID signal transmitted from the transponder 4.
- the vehicle 1 corresponds to a communication subject
- the immobilizer system 3 is one example of an electronic key system.
- the vehicle 1 includes an immobilizer ECU 6 that serves as a controller.
- An in-vehicle LAN 13 connects the immobilizer ECU 6 to an engine ECU 12 that controls the operation of an engine 11.
- the immobilizer ECU 6 includes a memory 69 that stores an ID code of the electronic key 2. Further, the immobilizer ECU 6 is connected to the coil antenna 5, which is arranged in a key cylinder.
- the coil antenna 5 receives and transmits radio waves on a low frequency (LF) band or a high frequency (HF) band.
- LF low frequency
- HF high frequency
- a magnetic field antenna is used as the coil antenna 5.
- the immobilizer ECU 6 is one example of a controller.
- the transponder 4 includes a control unit 41 that controls communication of the transponder 4.
- the control unit 41 includes a memory 42 that stores a key ID code (key identification information) unique to the electronic key 2.
- the key ID code is a transponder code.
- the transponder 4 is connected to an antenna 21 that transmits and receives radio waves on an LF band or an HF band in the same manner as the coil antenna 5.
- the immobilizer ECU 6 intermittently transmits radio waves from the coil antenna when, for example, the electronic key 2 is inserted into the key cylinder.
- the transponder 4 receives radio waves transmitted from the coil antenna 5 with the antenna 21.
- ID verification immobilizer verification
- the immobilizer ECU 6 stores information indicating that ID verification has been accomplished in the memory 69.
- the key cylinder includes an ignition switch (IGSW) that detects the rotational position of the electronic key 2. For example, when the ignition switch 14 is rotated to an engine start position together with the electronic key 2, the engine ECU 12 communicates with the immobilizer ECU 6 to check whether or not ID verification of the electronic key 2 has been accomplished. When the engine ECU 12 receives information indicating ID verification accomplishment from the immobilizer ECU 6, the engine ECU 12 starts the execution of an ignition control and a fuel injection control on the engine 11.
- IGSW ignition switch
- challenge-response verification is performed in addition to the ID verification of the electronic key 2.
- the immobilizer ECU 6 transmits a challenge code (e.g., random number code) to the electronic key 2.
- the electronic key 2 computes a response code from the challenge code and returns the response code to the vehicle 1.
- the immobilizer ECU 6 computes a response code and determines whether or not the response code conforms to the response code acquired from the electronic key 2.
- the wireless communication performed between the immobilizer ECU 6 and the transponder 4 is based on the common key cryptosystem, which stores the same encryption key in the electronic key 2 and the immobilizer ECU 6.
- the electronic key 2 and the immobilizer ECU 6 each use the encryption key to compute the response code from the challenge code.
- the memory 42 of the transponder 4 stores a key ID code KID (key identification information) and a key encryption key K.
- the key encryption key K is unique to the electronic key 2 and associated with the key ID code KID.
- the key encryption key K is used to verify the electronic key 2.
- the memory 69 of the immobilizer ECU 6 includes a registration flag set to indicate whether or not to permit registration of the electronic key 2 to the immobilizer ECU 6. Further, the memory 69 of the immobilizer ECU 6 stores a vehicle ID code VID (communication subject identification information), which is unique to the vehicle 1, a vehicle encryption key VK (communication subject encryption key), the key encryption key K, and an encryption standard AES (encryption program).
- VID vehicle ID code
- VK communication subject encryption key
- the vehicle encryption key VK is unique to the vehicle 1 and associated with the vehicle ID code VID.
- the key encryption key K conforms to that stored in the memory 42 of the transponder 4 and is used to verify the electronic key 2.
- the key encryption key K stored in the memory 69 of the immobilizer ECU 6 is generated by the immobilizer ECU 6 when the electronic key 2 is registered.
- the vehicle encryption key VK and the encryption standard AES are used for registration of the electronic key 2 (generation of the key encryption key K).
- An electronic key registration system 7 registers the electronic key 2 that is used in the immobilizer system 3.
- the electronic key registration system 7 is used to, for example, register a new electronic key 2 to the immobilizer ECU 6 or reregister the electronic key to an exchanged immobilizer ECU 6.
- the electronic key registration system 7 includes a registration tool 8 and a data center 10.
- the data center 10 includes a database 9.
- the database 9 includes an ECU database 9a, which stores data of the immobilizer ECU 6, and an electronic key database 9b, which stores data of the electronic key 2.
- the electronic key database 9b stores the key ID code KID and the encryption key K of each electronic key 2.
- the ECU database 9a stores the vehicle ID code VID and the vehicle encryption key VK of each vehicle 1 and the key ID code KID and the key encryption key K of each electronic key 2.
- the key ID code KID and the key encryption code K are stored to the ECU database 9a when the electronic key 2 is registered.
- the database 9 also stores the encryption standard AES (encryption program).
- the data center 10 uses the encryption standard AES to generate a SEED code SC (encryption key generation code).
- the immobilizer ECU 6 uses the SEED code SC to generate the key encryption key K.
- the electronic key registration system 7 when the key ID code KID and the key encryption key K are both stored in the memory 69 of the immobilizer ECU 6, the electronic key 2 is registered to the immobilizer ECU 6.
- the immobilizer ECU 6 does not directly acquire the key encryption key K from the data center 10 or the electronic key 2. Rather, the immobilizer ECU 6 acquires the SEED code SC from the data center 10 and uses the SEED code SC to generate the key encryption key K.
- the SEED code differs for each electronic key 2 and for each vehicle 1.
- the data center 10 uses the encryption standard AES, the key encryption key K, and the vehicle encryption key VK to generate the SEED code SC.
- the registration tool 8 is communicatively connected to the immobilizer ECU 6 of the vehicle 1 when registering the electronic key 2.
- the registration of the electronic key 2 is performed by switching the operation mode of the immobilizer ECU 6 to a registration mode.
- the registration tool 8 includes a control unit 81, an operation unit 82 operated by a user, and a display unit 83 that shows the status of a registration process.
- the registration tool 8 prompts the user to input the quantity of the electronic keys 2 that are to be registered.
- the registration tool 8 transmits a registration signal, together with the input quantity, to the immobilizer ECU 6 of the vehicle 1.
- the immobilizer ECU 6 starts the registration mode.
- the immobilizer ECU 6 includes a mode switching unit 61 that switches the operation mode.
- the mode switching unit 61 switches the operation mode to the registration mode.
- the mode switching unit 61 switches the operation mode to a normal mode in which verification (ID verification) of the electronic key 2 is performed, and the normal mode is maintained until a registration signal is received next from the registration tool 8.
- the immobilizer ECU 6 includes a key ID write unit 62 that writes a key ID code KID of the electronic key 2 to the memory 69.
- the key ID write unit 62 writes the key ID code KID, which is transmitted from the electronic key 2, to the memory 69.
- the immobilizer ECU 6 includes a key ID check unit 63 that checks whether or not the key ID code KID stored in the memory 69 conforms to the key ID code KID stored in the electronic key 2.
- the key ID check unit 63 transmits a key ID request signal from the coil antenna 5 to the electronic key 2.
- the key ID check unit 63 acquires the key ID code KID (key ID signal) from the electronic key 2, and checks whether or not the key ID code KID is stored in the memory 69.
- the key ID check unit 63 transmits a challenge code used for challenge-response verification to the electronic key 2.
- the key ID check unit 63 stores a response code transmitted from the electronic key 2, and checks whether or not the response code conforms to the response code obtained by the key ID check unit 63 (response code verification).
- the immobilizer ECU 6 also includes a SEED read unit 64 that reads a SEED code used to generate the key encryption key K. During the registration mode, the SEED read unit 64 transmits a SEED request signal from the coil antenna 5 to the data center 10 to acquire the SEED code SC (SEED signal) from the data center 10.
- SEED code SC SEED signal
- the immobilizer ECU 6 includes a SEED generation request unit 65.
- the SEED generation request unit 65 transmits a SEED generation request signal to the data center 10 to request for the generation of a SEED code SC from the key encryption key K.
- the data center 10 generates the SEED code SC and stores the SEED code SC in the database 9.
- the immobilizer ECU 6 includes an encryption key generation unit 66 that generates the key encryption key K.
- the encryption key generation unit 66 receives the SEED code SC acquired by the SEED read unit 64 and uses the SEED code SC, the encryption standard AES, and the vehicle encryption key VK to generate the key encryption key K.
- the immobilizer ECU 6 includes an encryption key registration unit 67 that registers the key encryption key K and updates the registration flag.
- the encryption key registration unit 67 stores the key encryption key K generated by the encryption key generation unit 66 in the memory 69 to register the key encryption key K (i.e., electronic key 2) to the immobilizer ECU 6. Further, when an electronic key 2 is allowed to be additionally registered to the immobilizer ECU 6 (vehicle 1), the encryption key registration unit 67 sets the registration flag to indicate an acceptable state. When an electronic key 2 is not allowed to be additionally registered, the encryption key registration unit 67 sets the registration flag to indicate a non-acceptable state.
- the immobilizer ECU 6 includes a database update unit 68 to update the data of the database 9 in the data center 10 based on the key ID code KID and the key encryption key K stored in the memory 69.
- the database update unit 68 transmits a data update signal to the data center 10 and reflects the data of the memory 69 to the data of the database 9.
- the immobilizer ECU 6 acquires the vehicle ID code VID from the vehicle 1 in advance. For example, when a certain operation that requests for the vehicle ID is performed on the vehicle 1, the vehicle ID code VID may be illustrated on the display 15 of the vehicle 1 and stored in the memory 69. Alternatively, when immobilizer verification is accomplished after inserting the electronic key 2 into the key cylinder, the vehicle ID code VID may be illustrated on the display 15 and stored in the memory 69.
- a registration step of the electronic key 2 under an online environment will now be described.
- two electronic keys namely, a first electronic key 2a and a second electronic key 2b
- the registration tool 8 is connected to the vehicle 1 and to a network 20.
- an electronic key manufacturing step is performed in an electronic key manufacturing plant.
- a key ID code KID-1 and a key encryption key K-1 are stored in the memory 42 of the first electronic key 2a
- a key ID code KID-2 and a key encryption key K-2 are stored in the memory 42 of the second electronic key 2b.
- the key ID codes KID-1 and KID-2 and the key encryption keys K-1 and K-2 of the electronic keys 2a and 2b are stored in the electronic key database 9b of the data center 10.
- the key ID codes KID-1 and KID-2 and the key encryption keys K-1 and K-2 of the electronic keys 2a and 2b are not stored in the ECU database 9a of the data center 10.
- a controller manufacturing step for manufacturing the immobilizer ECU 6 is performed in parallel to or before or after the electronic key manufacturing step.
- the vehicle ID code VID-A and the vehicle encryption key VK-A of the vehicle 1 are stored in the memory 69 of the immobilizer ECU 6.
- a registration step of the electronic keys 2a and 2b is performed under an online environment.
- the immobilizer ECU 6 reads the key ID codes KID-1 and KID-2 from the electronic keys 2a and 2b. Further, the immobilizer ECU 6 transmits a SEED generation request signal to the data center 10 together with the vehicle ID code VID-A and the key ID codes KID-1 and KID-2.
- the data center 10 In response to the SEED generation request signal, the data center 10 generates SEED codes SC-A1 and SC-A2.
- the step of generating the SEED codes may be skipped.
- the immobilizer ECU 6 acquires the SEED codes SC-A1 and SC-A2 from the data center 10.
- the immobilizer ECU 6 generates the key encryption keys K-1 and K-2 based on the SEED codes SC-A1 and SC-A2 and stores the key encryption keys K-1 and K-2 in the memory 69.
- the key ID codes KID-1 and KID-2 acquired from the immobilizer ECU 6 are stored in the ECU database 9a of the data center 10.
- the key encryption keys K-1 and K-2 of the electronic key database 9b are reflected to the ECU database 9a.
- the registration step will now be described in detail.
- the registration tool 8 transmits a registration signal to the immobilizer ECU 6 (step S21).
- the registration signal includes the quantity of the electronic keys 2 that are to be registered (in this case, two).
- the mode switching unit 61 of the immobilizer ECU 6 switches the operation mode to the registration mode (step S22).
- the immobilizer ECU 6 sequentially communicates with the electronic keys 2a and 2b to acquire the key ID codes KID-1 and KID-2.
- the key ID write unit 62 of the immobilizer ECU 6 first transmits a key ID request signal from the coil antenna 5 to the first electronic key 2a (step S23-1).
- the transponder 4 of the first electronic key 2a transmits a key ID signal from the antenna 21 to the immobilizer ECU 6 (step S24-1).
- the key ID signal includes the key ID code KID-1 stored in the memory 42 of the first electronic key 2a.
- the key ID write unit 62 of the immobilizer ECU 6 acquires the key ID code KID-1 from the key ID signal and writes the key ID code KID-1 to the memory 69 (step S25-1).
- the key ID check unit 63 of the immobilizer ECU 6 transmits a challenge code from the coil antenna 5 to the first electronic key 2a (step S26-1).
- the challenge code is, for example, a random number code.
- the transponder 4 of the first electronic key 2a encrypts the challenge code with the key encryption key K-1 to generate a response code (step S27-1). Then, the transponder 4 of the first electronic key 2a transmits the response code from the antenna 21 to the immobilizer ECU 6 (step S28-1).
- the ID check unit 63 of the immobilizer ECU 6 stores the response code transmitted from the first electronic key 2a in the memory 69 (step S29-1). At this point of time, the key ID check unit 63 does not have the key encryption key K-1 of the first electronic key 2a but stores the response code in the memory 69 to perform response code verification later.
- the key ID write unit 62 of the immobilizer ECU 6 transmits a key ID request signal from the coil antenna 5 to the second electronic key 2b (step S23-2).
- the transponder 4 of the second electronic key 2b transmits a key ID signal from the antenna 21 to the immobilizer ECU 6 (step S24-2).
- the key ID signal includes the key ID code KID-2 stored in the memory 42 of the second electronic key 2b.
- the key ID write unit 62 of the immobilizer ECU 6 acquires the key ID code KID-2 from the key ID signal and writes the key ID code KID-2 to the memory 69 (step S25-2).
- the key ID check unit 63 of the immobilizer ECU 6 transmits a challenge code from the coil antenna 5 to the second electronic key 2b (step S26-2).
- the challenge code is, for example, a random number code.
- the transponder 4 of the second electronic key 2b encrypts the challenge code with the key encryption key K-2 to generate a response code (step S27-2). Then, the transponder 4 of the second electronic key 2b transmits the response code from the antenna 21 to the immobilizer ECU 6 (step S28-2).
- the ID check unit 63 of the immobilizer ECU 6 stores the response code transmitted from the second electronic key 2b in the memory 69 (step S29-2). At this point of time, the key ID check unit 63 does not have the key encryption key K-2 of the second electronic key 2b but stores the response code in the memory 69 to perform response code verification later.
- the immobilizer ECU 6 sequentially communicates with the first and second electronic keys 2a and 2b to acquire the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b and the respective response codes.
- the SEED generation request unit 65 of the immobilizer ECU 6 transmits the SEED generation request signal to the data center 10 (step S31).
- the SEED generation request signal includes the vehicle ID code VID-A, which is used to identify the vehicle 1, and the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b.
- the immobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 together for the electronic keys 2a and 2b that are the subjects of registration.
- the data center 10 When the data center 10 receives the SEED generation request signal, the data center 10 stores the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b in the ECU database 9a (step S32). Then, the data center 10 generates the SEED code SC-A1 corresponding to the electronic key 2a and the SEED code SC-A2 corresponding to the electronic key 2b (step S33). In this case, the data center 10 uses the encryption standard AES, the key encryption keys K-1 and K-2, and the vehicle encryption key VK-A to generate the SEED codes SC-A1 and SC-A2. When the SEED codes SC-A1 and SC-A2 have already been stored in the data center 10, steps S31 to S33 may be skipped.
- the SEED read unit 64 of the immobilizer ECU 6 then transmits the SEED request signal to the data center 10 (step S34).
- the data center 10 transmits a SEED signal, which includes the SEED codes SC-A1 and SC-A2, to the immobilizer ECU 6 (step S35). Accordingly, the immobilizer ECU 6 receives the SEED codes SC-A1 and SC-A2 of the electronic keys 2a and 2b, which are the registration subjects, together from the data center 10.
- the immobilizer ECU 6 When receiving the SEED signal, the immobilizer ECU 6 calculates the key encryption keys K-1 and K-2 and sequentially verifies the response codes of the electronic keys 2a and 2b.
- the encryption key generation unit 66 of the immobilizer ECU 6 first calculates the key encryption key K-1 of the first electronic key 2a based on the encryption standard AES, the SEED code SC-A1 acquired by the SEED read unit 64, and the vehicle encryption key VK-A (step S36-1). That is, the immobilizer ECU 6 does not directly acquire the key encryption key K-1 from the data center 10. Rather, the immobilizer ECU 6 acquires the SEED code SC-A1 to generate the key encryption key K-1.
- the key ID check unit 63 of the immobilizer ECU 6 uses the key encryption key K-1 to encrypt the challenge code, which was transmitted to the first electronic key 2a in advance, to generate a response code (step S37-1). Further, the key ID check unit 63 of the immobilizer ECU 6 verifies the response code with the response core, which was transmitted in advance from the first electronic key 2a and stored in the memory 69 (step S38-1).
- the encryption key registration unit 67 of the immobilizer ECU 6 stores the key encryption key K-1 generated by the encryption key generation unit 66 in the memory 69 (step S39-1).
- the key encryption key K-1 that is, the first electronic key 2a
- the immobilizer ECU 6 This allows for ID verification (immobilizer verification) of the first electronic key 2a to be performed with the key encryption key K-1 through encrypted communication between the immobilizer ECU 6 and the first electronic key 2a.
- the encryption key generation unit 66 of the immobilizer ECU 6 calculates the key encryption key K-2 of the second electronic key 2b based on the encryption standard AES, the SEED code SC-A2 acquired by the SEED read unit 64, and the vehicle encryption key VK-A (step S36-2). That is, the immobilizer ECU 6 does not directly acquire the key encryption key K-2 from the data center 10. Rather, the immobilizer ECU 6 acquires the SEED code SC-A2 to generate the key encryption key K-2.
- the key ID check unit 63 of the immobilizer ECU 6 uses the key encryption key K-2 to encrypt the challenge code, which was transmitted to the second electronic key 2b in advance, to generate a response code (step S37-2). Further, the key ID check unit 63 of the immobilizer ECU 6 verifies the response code with the response core, which was transmitted in advance from the second electronic key 2b and stored in the memory 69 (step S38-2).
- the encryption key registration unit 67 of the immobilizer ECU 6 stores the key encryption key K-2 generated by the encryption key generation unit 66 in the memory 69 (step S39-2).
- the key encryption key K-2 that is, the second electronic key 2b
- the immobilizer ECU 6 This allows for ID verification (immobilizer verification) of the second electronic key 2a to be performed with the key encryption key K-2 through encrypted communication between the immobilizer ECU 6 and the second electronic key 2b.
- the database update unit 68 of the immobilizer ECU 6 transmits the database update signal to the data center 10 (step S40).
- the data center 10 updates the data of the ECU database 9a based on the data of the electronic key database 9b (step S41).
- the key encryption keys K-1 and K-2 are stored in the ECU database 9a.
- the immobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b together to the data center 10 and receives the SEED codes SC-A1 and SC-A2 corresponding to the electronic keys 2a and 2b together from the data center 10.
- the immobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b together to the data center 10 and receives the SEED codes SC-A1 and SC-A2 corresponding to the electronic keys 2a and 2b together from the data center 10.
- the immobilizer ECU 6 when the immobilizer ECU 6 acquires the key ID codes KID-1 and KID-2 of the electronic keys 2a and 2b, the immobilizer ECU 6 also acquires the response codes of the electronic keys 2a and 2b used for the challenge-response verification. Thus, after generating the key ID codes KID-1 and KID-2, the immobilizer ECU 6 performs response code verification without performing communication again with the electronic keys 2a and 2b. As a result, the time for registering the electronic keys 2a and 2b may be reduced.
- the immobilizer ECU 6 includes a memory (RAM or the like) that stores commands executed by the immobilizer ECU 6.
- the commands are configured to have the immobilizer ECU 6 acquire the key ID code KID-1 from the first electronic key 2a, acquire the key ID code KID-2 from the second electronic key 2b, transmit the vehicle ID code VID together with both of the key ID codes KID-1 and KID2 to the data center 10, acquire the SEED code SC-A1 corresponding to the first electronic key 2a together with the SEED code SC-A2 corresponding to the second electronic key 2b from the data center 10, generate the key encryption key K-1 based on the SEED code SC-A1, and generate the key encryption key K-2 based on the SEED code SC-A2.
- the commands stored in the memory are configured to have the immobilizer ECU 6 transmit a challenge code to the first electronic key 2a after acquiring the key ID code KID-1 from the first electronic key 2a, receive from the first electronic key 2a a first response code generated by the first electronic key 2a based on the key encryption key K-1 and the challenge code, transmit the challenge code to the second electronic key 2b after acquiring the key ID code KID-2 from the second electronic key 2b, receive from the second electronic key 2b a second response code generated by the second electronic key 2b based on the key encryption key K-2 and the challenge code, generate a third response code based on the key encryption key K-1 and the challenge code after generating the key encryption key K-1 based on the SEED code SC-A1, generate a fourth response code based on the key encryption key K-2 and the challenge code after generating the key encryption key K-1 based on the SEED code SC-A2, verify the first electronic key 2a by comparing the first response code with the third response code, and verify the second electronic key 2b by
- step S30 when the registration tool 8 switches the operation mode to the registration mode, the quantity of the electronic keys 2 that are to be registered is set. However, the quantity of the electronic keys 2 does not have to be designated in advance.
- step S30 when the immobilizer ECU 6 obtains the key ID codes KID of all of the electronic keys 2 that are to be registered, the registration tool 8 transmits an acquisition termination command (key ID acquisition termination signal) to the immobilizer ECU 6. In response to the termination signal, the immobilizer ECU 6 terminates the acquisition of the key ID codes KID and may then proceed to step S31.
- the response code of the electronic key 2 is generated after the immobilizer ECU 6 acquires the key ID code KID.
- the response code of the electronic key 2 may be generated after the immobilizer ECU 6 calculates the key encryption key K from the SEED code SC.
- the encryption standard AES is used to generate the SEED code SC and the key encryption key K.
- a different encryption standard or encryption specification may be used.
- the data center 10 may verify the user (person performing registration) before executing a registration command in the registration step that is performed under an online environment.
- a registration command in the registration step that is performed under an online environment.
- an ID code and password of the person performing the registration may be used to perform user verification.
- the registration tool 8 may be a versatile computer, such as a personal computer or a smartphone, incorporating software used exclusively for registration.
- the encryption key is registered after the challenge-response verification is performed.
- the challenge-response verification may be omitted.
- the vehicle ID code VID when acquiring the vehicle ID code VID, the vehicle ID code VID is illustrated on the display 15 of the vehicle 1. Instead, a certain operation requesting for the vehicle ID code VID may be performed so that the vehicle 1 sends a mail to an address designated by the user. In this case, only the user that receives the mail can check the vehicle ID code VID. Thus, a high level of confidentiality may be obtained.
- the above embodiment is applied to the immobilizer system 3 in which the electronic key 2 is inserted into the key cylinder.
- the electronic key system may be configured so that communication is performed between the electronic key 2 and the vehicle 1 (controller) when the electronic key 2 enters a communication area formed by the vehicle 1.
- the electronic key system is applied to the vehicle 1 but may be applied to a building such as a house.
- a method for registering first and second electronic keys (2a, 2b) to a controller (6) of a communication subject (1) through communication with a data center (10) includes acquiring first and second key identification information (KID-1, KID-2) from the first and second electronic keys (2a, 2b) with the controller (6), transmitting communication subject identification information (VID) together with both of the first and second key identification information (KID-1, KID-2) from the controller (6) to the data center (10), acquiring a first encryption key generation code (SC-A1) corresponding to the first electronic key (2a) together with a second encryption key generation code (SC-A2) corresponding to the second electronic key (2b) from the data center (10) with the controller, generating a first key encryption key (K-1) based on the first encryption key generation code (SC-A1) with the controller, generating a second key encryption key (K-2) based on the second encryption key generation code (SC-A2) with the controller, and storing the first and second key encryption keys (K-1, K-2) in the controller
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Lock And Its Accessories (AREA)
Description
- The present invention relates to a method and system for registering an electronic key to a controller of a communication subject, and a controller.
- An electronic key system verifies an electronic key by performing wireless communication with an electronic key. When the electronic key is verified, the locking and unlocking of vehicle doors and the starting of the engine is performed. In such an electronic key system, encrypted communication is performed between the electronic key and the vehicle to maintain a certain level of security. This allows for the electronic key to be verified with a high level of confidentiality.
- The common key cryptosystem is one type of an encryption standard. In an electronic key system that uses the common key cryptosystem, when registering an electronic key to a controller of a vehicle, the electronic key and the vehicle both store the same encryption key. The controller uses the encryption key to communicate with and verify the electronic key by comparing identification information that is transmitted from the electronic key with identification information that is stored in the controller.
- Japanese Laid-Open Patent Publication No.
2011-20475 - When registering a plurality of electronic keys in the electronic key registration system of the prior art, the electronic keys are required to be registered one by one. Thus, whenever an electronic key is registered, communication is performed between the data center and the electronic key and between the data center and the controller. That is, communication with the data center is repeated for a number of times that is the same as the number of electronic keys that are to be registered. Accordingly, the registration of electronic keys is burdensome. This problem occurs not only when the electronic key system is applied to a vehicle but also when applied to a building such as a house.
- The present invention relates to an electronic key registration method, an electronic key registration system, and controller that facilitate the registration of a plurality of electronic keys while maintaining a certain level of security.
- A first embodiment of the present invention is an electronic key registration method for registering a plurality of electronic keys to a controller of a communication subject through communication with a data center. The electronic keys are capable of communicating with the controller. The electronic key registration method includes storing communication subject identification information and a communication subject encryption key in the controller. The communication subject identification information and the communication subject encryption key are unique to the communication subject. Further, the method includes storing the communication subject identification information and the communication subject encryption key in the data center, and storing first key identification information and a first key encryption key in the first electronic key. The first key identification information and the first key encryption key are unique to a first electronic key. The method also includes storing second key identification information and a second key encryption key in the second electronic key. The second key identification information and a second key encryption key are unique to the second electronic key. Further, the method includes storing the first and second key identification information and the first and second key encryption keys in the data center, acquiring the first key identification information from the first electronic key with the controller, acquiring the second key identification information from the second electronic key with the controller, transmitting the communication subject identification information together with the first and second key identification information from the controller to the data center, and generating a first encryption key generation code with the data center. The first encryption key generation code is based on the communication subject encryption key and the first key encryption key. Additionally, the method includes generating a second encryption key generation code with the data center. The second encryption key generation code is based on the communication subject encryption key and the second key encryption key. Further, the method includes obtaining the first and second encryption key generation codes together from the data center with the controller, generating the first key encryption key based on the first encryption key generation code with the controller, generating the second key encryption key based on the second encryption key generation code with the controller, and storing the first and second key encryption keys in the controller.
- A second embodiment of the present invention is an electronic key registration system provided with a plurality of electronic keys including first and second electronic keys, a controller arranged in a communication subject and capable of communicating with the electronic keys, and a data center. The controller includes a memory that stores commands executed by the controller. The commands include commands configured to have the controller acquire first key identification information from the first electronic key, acquire second key identification information from the second electronic key, transmit communication subject identification information together with the first and second key identification information to the data center, acquire a first encryption key generation code corresponding to the first electronic key together with a second encryption key generation code corresponding to the second electronic key from the data center, generate a first key encryption key based on the first encryption key generation code, generate a second key encryption key based on the second encryption key generation code, and store the first and second key encryption keys in the controller.
- A third embodiment of the present invention is a controller arranged in a communication subject. The controller is capable of communicating with a data center and a plurality of electronic keys including first and second electronic keys. The controller includes a memory that stores commands executed by the controller. The commands include commands configured to have the controller acquire first key identification information from the first electronic key, acquire second key identification information from the second electronic key, transmit communication subject identification information together with the first and second key identification information to the data center, acquire a first encryption key generation code corresponding to the first electronic key together with a second encryption key generation code corresponding to the second electronic key from the data center, generate a first key encryption key based on the first encryption key generation code, generate a second key encryption key based on the second encryption key generation code, and store the first and second key encryption keys in the controller.
- Other embodiment s and advantages of the present invention will become apparent from the following description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
- According to the present invention, the registration of a plurality of electronic keys is facilitated as well as a certain level of security is maintained.
- The invention, together with objects and advantages thereof, may best be understood by reference to the following description of the presently preferred embodiments together with the accompanying drawings in which:
-
Fig. 1 is a schematic block diagram of an electronic key registration system; -
Fig. 2 is a schematic block diagram illustrating an electronic key registration process in the electronic key registration system ofFig. 1 ; and -
Figs. 3 and4 are schematic flow charts illustrating an electronic key registration process in the electronic key registration system ofFig. 1 . - One embodiment of an electronic key registration system applied to, for example, a vehicle will now be described with reference to
Figs. 1 to 4 . - Referring to
Fig. 1 , thevehicle 1 includes animmobilizer system 3 that performs ID verification on anelectronic key 2 through, for example, near-field communication. The communication distance for near-distance communication is several centimeters. Theelectronic key 2 includes atransponder 4 that serves as an ID tag. Thetransponder 4 is activated by drive radio waves transmitted from acoil antenna 5 of thevehicle 1. The ID verification of theelectronic key 2 is performed based on a key ID signal transmitted from thetransponder 4. In the present embodiment, thevehicle 1 corresponds to a communication subject, and theimmobilizer system 3 is one example of an electronic key system. - The
vehicle 1 includes an immobilizer ECU 6 that serves as a controller. An in-vehicle LAN 13 connects the immobilizer ECU 6 to anengine ECU 12 that controls the operation of anengine 11. The immobilizer ECU 6 includes amemory 69 that stores an ID code of theelectronic key 2. Further, the immobilizer ECU 6 is connected to thecoil antenna 5, which is arranged in a key cylinder. Thecoil antenna 5 receives and transmits radio waves on a low frequency (LF) band or a high frequency (HF) band. A magnetic field antenna is used as thecoil antenna 5. The immobilizer ECU 6 is one example of a controller. - The
transponder 4 includes acontrol unit 41 that controls communication of thetransponder 4. Thecontrol unit 41 includes amemory 42 that stores a key ID code (key identification information) unique to theelectronic key 2. In the present embodiment, the key ID code is a transponder code. Thetransponder 4 is connected to anantenna 21 that transmits and receives radio waves on an LF band or an HF band in the same manner as thecoil antenna 5. - The immobilizer ECU 6 intermittently transmits radio waves from the coil antenna when, for example, the
electronic key 2 is inserted into the key cylinder. For example, when the key cylinder is inserted into the key cylinder and theengine 11 is started, thetransponder 4 receives radio waves transmitted from thecoil antenna 5 with theantenna 21. Thetransponder 4, which is activated by the radio waves, transmits a key ID signal, which includes the key ID code stored in thememory 42, from theantenna 21. The immobilizer ECU 6, which receives the key ID signal with thecoil antenna 5, performs ID verification (immobilizer verification) on theelectronic key 2. When the ID verification of theelectronic key 2 is accomplished, theimmobilizer ECU 6 stores information indicating that ID verification has been accomplished in thememory 69. - The key cylinder includes an ignition switch (IGSW) that detects the rotational position of the
electronic key 2. For example, when theignition switch 14 is rotated to an engine start position together with theelectronic key 2, theengine ECU 12 communicates with theimmobilizer ECU 6 to check whether or not ID verification of theelectronic key 2 has been accomplished. When theengine ECU 12 receives information indicating ID verification accomplishment from theimmobilizer ECU 6, theengine ECU 12 starts the execution of an ignition control and a fuel injection control on theengine 11. - In the immobilizer verification, challenge-response verification is performed in addition to the ID verification of the
electronic key 2. In the challenge-response verification, theimmobilizer ECU 6 transmits a challenge code (e.g., random number code) to theelectronic key 2. Theelectronic key 2 computes a response code from the challenge code and returns the response code to thevehicle 1. In the same manner, theimmobilizer ECU 6 computes a response code and determines whether or not the response code conforms to the response code acquired from theelectronic key 2. The wireless communication performed between theimmobilizer ECU 6 and thetransponder 4 is based on the common key cryptosystem, which stores the same encryption key in theelectronic key 2 and theimmobilizer ECU 6. Theelectronic key 2 and theimmobilizer ECU 6 each use the encryption key to compute the response code from the challenge code. - The
memory 42 of thetransponder 4 stores a key ID code KID (key identification information) and a key encryption key K. The key encryption key K is unique to theelectronic key 2 and associated with the key ID code KID. The key encryption key K is used to verify theelectronic key 2. - The
memory 69 of theimmobilizer ECU 6 includes a registration flag set to indicate whether or not to permit registration of theelectronic key 2 to theimmobilizer ECU 6. Further, thememory 69 of theimmobilizer ECU 6 stores a vehicle ID code VID (communication subject identification information), which is unique to thevehicle 1, a vehicle encryption key VK (communication subject encryption key), the key encryption key K, and an encryption standard AES (encryption program). The vehicle encryption key VK is unique to thevehicle 1 and associated with the vehicle ID code VID. The key encryption key K conforms to that stored in thememory 42 of thetransponder 4 and is used to verify theelectronic key 2. The key encryption key K stored in thememory 69 of theimmobilizer ECU 6 is generated by theimmobilizer ECU 6 when theelectronic key 2 is registered. The vehicle encryption key VK and the encryption standard AES are used for registration of the electronic key 2 (generation of the key encryption key K). - An electronic
key registration system 7 registers theelectronic key 2 that is used in theimmobilizer system 3. The electronickey registration system 7 is used to, for example, register a newelectronic key 2 to theimmobilizer ECU 6 or reregister the electronic key to an exchangedimmobilizer ECU 6. - As illustrated in
Fig. 1 , the electronickey registration system 7 includes aregistration tool 8 and adata center 10. As illustrated inFig. 2 , thedata center 10 includes adatabase 9. Thedatabase 9 includes anECU database 9a, which stores data of theimmobilizer ECU 6, and an electronickey database 9b, which stores data of theelectronic key 2. The electronickey database 9b stores the key ID code KID and the encryption key K of eachelectronic key 2. TheECU database 9a stores the vehicle ID code VID and the vehicle encryption key VK of eachvehicle 1 and the key ID code KID and the key encryption key K of eachelectronic key 2. The key ID code KID and the key encryption code K are stored to theECU database 9a when theelectronic key 2 is registered. Thedatabase 9 also stores the encryption standard AES (encryption program). Thedata center 10 uses the encryption standard AES to generate a SEED code SC (encryption key generation code). Theimmobilizer ECU 6 uses the SEED code SC to generate the key encryption key K. - In the electronic
key registration system 7, when the key ID code KID and the key encryption key K are both stored in thememory 69 of theimmobilizer ECU 6, theelectronic key 2 is registered to theimmobilizer ECU 6. Theimmobilizer ECU 6 does not directly acquire the key encryption key K from thedata center 10 or theelectronic key 2. Rather, theimmobilizer ECU 6 acquires the SEED code SC from thedata center 10 and uses the SEED code SC to generate the key encryption key K. The SEED code differs for eachelectronic key 2 and for eachvehicle 1. In the present embodiment, thedata center 10 uses the encryption standard AES, the key encryption key K, and the vehicle encryption key VK to generate the SEED code SC. - The
registration tool 8 is communicatively connected to theimmobilizer ECU 6 of thevehicle 1 when registering theelectronic key 2. The registration of theelectronic key 2 is performed by switching the operation mode of theimmobilizer ECU 6 to a registration mode. Theregistration tool 8 includes acontrol unit 81, anoperation unit 82 operated by a user, and adisplay unit 83 that shows the status of a registration process. When an operation for starting the registration mode is performed, theregistration tool 8 prompts the user to input the quantity of theelectronic keys 2 that are to be registered. Theregistration tool 8 then transmits a registration signal, together with the input quantity, to theimmobilizer ECU 6 of thevehicle 1. In response to the registration signal, theimmobilizer ECU 6 starts the registration mode. - The
immobilizer ECU 6 includes amode switching unit 61 that switches the operation mode. In response to the registration signal from theregistration tool 8, themode switching unit 61 switches the operation mode to the registration mode. Upon completion of the registration mode (registration of the electronic key 2), themode switching unit 61 switches the operation mode to a normal mode in which verification (ID verification) of theelectronic key 2 is performed, and the normal mode is maintained until a registration signal is received next from theregistration tool 8. - The
immobilizer ECU 6 includes a keyID write unit 62 that writes a key ID code KID of theelectronic key 2 to thememory 69. In the registration mode, the keyID write unit 62 writes the key ID code KID, which is transmitted from theelectronic key 2, to thememory 69. - Further, the
immobilizer ECU 6 includes a keyID check unit 63 that checks whether or not the key ID code KID stored in thememory 69 conforms to the key ID code KID stored in theelectronic key 2. In the registration mode, the keyID check unit 63 transmits a key ID request signal from thecoil antenna 5 to theelectronic key 2. Further, the keyID check unit 63 acquires the key ID code KID (key ID signal) from theelectronic key 2, and checks whether or not the key ID code KID is stored in thememory 69. Further, the keyID check unit 63 transmits a challenge code used for challenge-response verification to theelectronic key 2. The keyID check unit 63 stores a response code transmitted from theelectronic key 2, and checks whether or not the response code conforms to the response code obtained by the key ID check unit 63 (response code verification). - The
immobilizer ECU 6 also includes aSEED read unit 64 that reads a SEED code used to generate the key encryption key K. During the registration mode, the SEED readunit 64 transmits a SEED request signal from thecoil antenna 5 to thedata center 10 to acquire the SEED code SC (SEED signal) from thedata center 10. - The
immobilizer ECU 6 includes a SEEDgeneration request unit 65. During the registration mode, when the SEED code SC is not stored in the data center 10 (e.g., when theelectronic key 2 is newly registered), the SEEDgeneration request unit 65 transmits a SEED generation request signal to thedata center 10 to request for the generation of a SEED code SC from the key encryption key K. In response to the SEED generation request signal, thedata center 10 generates the SEED code SC and stores the SEED code SC in thedatabase 9. - The
immobilizer ECU 6 includes an encryptionkey generation unit 66 that generates the key encryption key K. During the registration mode, the encryptionkey generation unit 66 receives the SEED code SC acquired by the SEED readunit 64 and uses the SEED code SC, the encryption standard AES, and the vehicle encryption key VK to generate the key encryption key K. - The
immobilizer ECU 6 includes an encryptionkey registration unit 67 that registers the key encryption key K and updates the registration flag. During the registration mode, the encryptionkey registration unit 67 stores the key encryption key K generated by the encryptionkey generation unit 66 in thememory 69 to register the key encryption key K (i.e., electronic key 2) to theimmobilizer ECU 6. Further, when anelectronic key 2 is allowed to be additionally registered to the immobilizer ECU 6 (vehicle 1), the encryptionkey registration unit 67 sets the registration flag to indicate an acceptable state. When anelectronic key 2 is not allowed to be additionally registered, the encryptionkey registration unit 67 sets the registration flag to indicate a non-acceptable state. - The
immobilizer ECU 6 includes adatabase update unit 68 to update the data of thedatabase 9 in thedata center 10 based on the key ID code KID and the key encryption key K stored in thememory 69. When a key ID code KID and a key encryption key K are newly acquired, thedatabase update unit 68 transmits a data update signal to thedata center 10 and reflects the data of thememory 69 to the data of thedatabase 9. - The
immobilizer ECU 6 acquires the vehicle ID code VID from thevehicle 1 in advance. For example, when a certain operation that requests for the vehicle ID is performed on thevehicle 1, the vehicle ID code VID may be illustrated on thedisplay 15 of thevehicle 1 and stored in thememory 69. Alternatively, when immobilizer verification is accomplished after inserting theelectronic key 2 into the key cylinder, the vehicle ID code VID may be illustrated on thedisplay 15 and stored in thememory 69. - With reference to
Figs. 2 to 4 , a registration step of theelectronic key 2 under an online environment will now be described. Here, twoelectronic keys 2, namely, a first electronic key 2a and a second electronic key 2b, are simultaneously registered. In the registration step, theregistration tool 8 is connected to thevehicle 1 and to anetwork 20. This sets theimmobilizer ECU 6 under an online environment that allows for communication with thedata center 10. - Further, an electronic key manufacturing step is performed in an electronic key manufacturing plant. Referring to
Fig. 2 , in the electronic key manufacturing step, a key ID code KID-1 and a key encryption key K-1 are stored in thememory 42 of the first electronic key 2a, and a key ID code KID-2 and a key encryption key K-2 are stored in thememory 42 of the second electronic key 2b. - In the electronic key manufacturing step, the key ID codes KID-1 and KID-2 and the key encryption keys K-1 and K-2 of the
electronic keys key database 9b of thedata center 10. In the electronic key manufacturing step, the key ID codes KID-1 and KID-2 and the key encryption keys K-1 and K-2 of theelectronic keys ECU database 9a of thedata center 10. - A controller manufacturing step for manufacturing the
immobilizer ECU 6 is performed in parallel to or before or after the electronic key manufacturing step. In the controller manufacturing step, the vehicle ID code VID-A and the vehicle encryption key VK-A of thevehicle 1 are stored in thememory 69 of theimmobilizer ECU 6. - Referring to
Fig. 2 , a registration step of theelectronic keys immobilizer ECU 6 reads the key ID codes KID-1 and KID-2 from theelectronic keys immobilizer ECU 6 transmits a SEED generation request signal to thedata center 10 together with the vehicle ID code VID-A and the key ID codes KID-1 and KID-2. In response to the SEED generation request signal, thedata center 10 generates SEED codes SC-A1 and SC-A2. When the SEED codes have already been generated in thedata center 10, the step of generating the SEED codes may be skipped. Then, theimmobilizer ECU 6 acquires the SEED codes SC-A1 and SC-A2 from thedata center 10. Theimmobilizer ECU 6 generates the key encryption keys K-1 and K-2 based on the SEED codes SC-A1 and SC-A2 and stores the key encryption keys K-1 and K-2 in thememory 69. The key ID codes KID-1 and KID-2 acquired from theimmobilizer ECU 6 are stored in theECU database 9a of thedata center 10. After the key encryption keys K-1 and K-2 are stored in theimmobilizer ECU 6, the key encryption keys K-1 and K-2 of the electronickey database 9b are reflected to theECU database 9a. The registration step will now be described in detail. - Referring to
Fig. 3 , when the user operates theoperation unit 82 of theregistration tool 8 and selects the registration mode, theregistration tool 8 transmits a registration signal to the immobilizer ECU 6 (step S21). The registration signal includes the quantity of theelectronic keys 2 that are to be registered (in this case, two). In response to the registration signal, themode switching unit 61 of theimmobilizer ECU 6 switches the operation mode to the registration mode (step S22). - Then, the
immobilizer ECU 6 sequentially communicates with theelectronic keys ID write unit 62 of theimmobilizer ECU 6 first transmits a key ID request signal from thecoil antenna 5 to the firstelectronic key 2a (step S23-1). - In response to the key ID request signal, the
transponder 4 of the first electronic key 2a transmits a key ID signal from theantenna 21 to the immobilizer ECU 6 (step S24-1). The key ID signal includes the key ID code KID-1 stored in thememory 42 of the first electronic key 2a. - The key
ID write unit 62 of theimmobilizer ECU 6 acquires the key ID code KID-1 from the key ID signal and writes the key ID code KID-1 to the memory 69 (step S25-1). - Then, the key
ID check unit 63 of theimmobilizer ECU 6 transmits a challenge code from thecoil antenna 5 to the firstelectronic key 2a (step S26-1). The challenge code is, for example, a random number code. - The
transponder 4 of the first electronic key 2a encrypts the challenge code with the key encryption key K-1 to generate a response code (step S27-1). Then, thetransponder 4 of the first electronic key 2a transmits the response code from theantenna 21 to the immobilizer ECU 6 (step S28-1). - The
ID check unit 63 of theimmobilizer ECU 6 stores the response code transmitted from the first electronic key 2a in the memory 69 (step S29-1). At this point of time, the keyID check unit 63 does not have the key encryption key K-1 of the first electronic key 2a but stores the response code in thememory 69 to perform response code verification later. - Subsequently, the key
ID write unit 62 of theimmobilizer ECU 6 transmits a key ID request signal from thecoil antenna 5 to the secondelectronic key 2b (step S23-2). - In response to the key ID request signal, the
transponder 4 of the second electronic key 2b transmits a key ID signal from theantenna 21 to the immobilizer ECU 6 (step S24-2). The key ID signal includes the key ID code KID-2 stored in thememory 42 of the second electronic key 2b. - The key
ID write unit 62 of theimmobilizer ECU 6 acquires the key ID code KID-2 from the key ID signal and writes the key ID code KID-2 to the memory 69 (step S25-2). - Then, the key
ID check unit 63 of theimmobilizer ECU 6 transmits a challenge code from thecoil antenna 5 to the secondelectronic key 2b (step S26-2). The challenge code is, for example, a random number code. - The
transponder 4 of the second electronic key 2b encrypts the challenge code with the key encryption key K-2 to generate a response code (step S27-2). Then, thetransponder 4 of the second electronic key 2b transmits the response code from theantenna 21 to the immobilizer ECU 6 (step S28-2). - The
ID check unit 63 of theimmobilizer ECU 6 stores the response code transmitted from the second electronic key 2b in the memory 69 (step S29-2). At this point of time, the keyID check unit 63 does not have the key encryption key K-2 of the second electronic key 2b but stores the response code in thememory 69 to perform response code verification later. - In this manner, the
immobilizer ECU 6 sequentially communicates with the first and secondelectronic keys electronic keys - Then, as illustrated in
Fig. 4 , the SEEDgeneration request unit 65 of theimmobilizer ECU 6 transmits the SEED generation request signal to the data center 10 (step S31). The SEED generation request signal includes the vehicle ID code VID-A, which is used to identify thevehicle 1, and the key ID codes KID-1 and KID-2 of theelectronic keys immobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 together for theelectronic keys - When the
data center 10 receives the SEED generation request signal, thedata center 10 stores the key ID codes KID-1 and KID-2 of theelectronic keys ECU database 9a (step S32). Then, thedata center 10 generates the SEED code SC-A1 corresponding to the electronic key 2a and the SEED code SC-A2 corresponding to the electronic key 2b (step S33). In this case, thedata center 10 uses the encryption standard AES, the key encryption keys K-1 and K-2, and the vehicle encryption key VK-A to generate the SEED codes SC-A1 and SC-A2. When the SEED codes SC-A1 and SC-A2 have already been stored in thedata center 10, steps S31 to S33 may be skipped. - The SEED read
unit 64 of theimmobilizer ECU 6 then transmits the SEED request signal to the data center 10 (step S34). - In response to the SEED request signal, the
data center 10 transmits a SEED signal, which includes the SEED codes SC-A1 and SC-A2, to the immobilizer ECU 6 (step S35). Accordingly, theimmobilizer ECU 6 receives the SEED codes SC-A1 and SC-A2 of theelectronic keys data center 10. - When receiving the SEED signal, the
immobilizer ECU 6 calculates the key encryption keys K-1 and K-2 and sequentially verifies the response codes of theelectronic keys key generation unit 66 of theimmobilizer ECU 6 first calculates the key encryption key K-1 of the first electronic key 2a based on the encryption standard AES, the SEED code SC-A1 acquired by the SEED readunit 64, and the vehicle encryption key VK-A (step S36-1). That is, theimmobilizer ECU 6 does not directly acquire the key encryption key K-1 from thedata center 10. Rather, theimmobilizer ECU 6 acquires the SEED code SC-A1 to generate the key encryption key K-1. - Then, the key
ID check unit 63 of theimmobilizer ECU 6 uses the key encryption key K-1 to encrypt the challenge code, which was transmitted to the first electronic key 2a in advance, to generate a response code (step S37-1). Further, the keyID check unit 63 of theimmobilizer ECU 6 verifies the response code with the response core, which was transmitted in advance from the first electronic key 2a and stored in the memory 69 (step S38-1). - When the response code verification is accomplished, the encryption
key registration unit 67 of theimmobilizer ECU 6 stores the key encryption key K-1 generated by the encryptionkey generation unit 66 in the memory 69 (step S39-1). As a result, the key encryption key K-1, that is, the first electronic key 2a, is registered to theimmobilizer ECU 6. This allows for ID verification (immobilizer verification) of the first electronic key 2a to be performed with the key encryption key K-1 through encrypted communication between theimmobilizer ECU 6 and the first electronic key 2a. - Then, the encryption
key generation unit 66 of theimmobilizer ECU 6 calculates the key encryption key K-2 of the second electronic key 2b based on the encryption standard AES, the SEED code SC-A2 acquired by the SEED readunit 64, and the vehicle encryption key VK-A (step S36-2). That is, theimmobilizer ECU 6 does not directly acquire the key encryption key K-2 from thedata center 10. Rather, theimmobilizer ECU 6 acquires the SEED code SC-A2 to generate the key encryption key K-2. - Then, the key
ID check unit 63 of theimmobilizer ECU 6 uses the key encryption key K-2 to encrypt the challenge code, which was transmitted to the second electronic key 2b in advance, to generate a response code (step S37-2). Further, the keyID check unit 63 of theimmobilizer ECU 6 verifies the response code with the response core, which was transmitted in advance from the second electronic key 2b and stored in the memory 69 (step S38-2). - When the response code verification is accomplished, the encryption
key registration unit 67 of theimmobilizer ECU 6 stores the key encryption key K-2 generated by the encryptionkey generation unit 66 in the memory 69 (step S39-2). As a result, the key encryption key K-2, that is, the second electronic key 2b, is registered to theimmobilizer ECU 6. This allows for ID verification (immobilizer verification) of the second electronic key 2a to be performed with the key encryption key K-2 through encrypted communication between theimmobilizer ECU 6 and the second electronic key 2b. - Subsequently, the
database update unit 68 of theimmobilizer ECU 6 transmits the database update signal to the data center 10 (step S40). In response to the update signal, thedata center 10 updates the data of theECU database 9a based on the data of the electronickey database 9b (step S41). As a result, the key encryption keys K-1 and K-2 are stored in theECU database 9a. - As described above, when registering the
electronic keys immobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 of theelectronic keys data center 10 and receives the SEED codes SC-A1 and SC-A2 corresponding to theelectronic keys data center 10. Thus, there is no need for the number of times communication is performed to be the same as the quantity of theelectronic keys 2 that are subject to registration. Accordingly, the registration process of a plurality ofelectronic keys 2 is facilitated. Further, when theimmobilizer ECU 6 acquires the key ID codes KID-1 and KID-2 of theelectronic keys immobilizer ECU 6 also acquires the response codes of theelectronic keys immobilizer ECU 6 performs response code verification without performing communication again with theelectronic keys electronic keys - In the present embodiment, the
immobilizer ECU 6 includes a memory (RAM or the like) that stores commands executed by theimmobilizer ECU 6. The commands are configured to have theimmobilizer ECU 6 acquire the key ID code KID-1 from the first electronic key 2a, acquire the key ID code KID-2 from the second electronic key 2b, transmit the vehicle ID code VID together with both of the key ID codes KID-1 and KID2 to thedata center 10, acquire the SEED code SC-A1 corresponding to the first electronic key 2a together with the SEED code SC-A2 corresponding to the second electronic key 2b from thedata center 10, generate the key encryption key K-1 based on the SEED code SC-A1, and generate the key encryption key K-2 based on the SEED code SC-A2. - Further, the commands stored in the memory are configured to have the
immobilizer ECU 6 transmit a challenge code to the first electronic key 2a after acquiring the key ID code KID-1 from the first electronic key 2a, receive from the first electronic key 2a a first response code generated by the first electronic key 2a based on the key encryption key K-1 and the challenge code, transmit the challenge code to the second electronic key 2b after acquiring the key ID code KID-2 from the second electronic key 2b, receive from the second electronic key 2b a second response code generated by the second electronic key 2b based on the key encryption key K-2 and the challenge code, generate a third response code based on the key encryption key K-1 and the challenge code after generating the key encryption key K-1 based on the SEED code SC-A1, generate a fourth response code based on the key encryption key K-2 and the challenge code after generating the key encryption key K-1 based on the SEED code SC-A2, verify the first electronic key 2a by comparing the first response code with the third response code, and verify the second electronic key 2b by comparing the second response code with the fourth response code. - The above embodiment has the advantages described below.
- (1) The key ID code KID and the key encryption key K of the
electronic key 2 are registered in advance to thedata center 10. Thedata center 10 generates the SEED code SC from the key encryption key K, and theimmobilizer ECU 6 generates the key encryption key K from the SEED code SC. Thus, only theelectronic key 2 that has the key ID code KID and the key encryption key K, which are registered in advance to thedata center 10, and that is capable of communicating with thedata center 10 through theimmobilizer ECU 6 is registered to theimmobilizer ECU 6. This maintains a certain level of security. Further, theimmobilizer ECU 6 transmits the key ID codes KID-1 and KID-2 of theelectronic keys data center 10. Theimmobilizer ECU 6 also acquires the SEED codes SC-A1 and SC-A2, which are generated from the key encryption key K-1 and K-2, together from thedata center 10. In this manner, when transmitting and receiving the key ID codes KID and the SEED codes, communication between theimmobilizer ECU 6 and thedata center 10 does not have to be performed for a number of times that is the same as the quantity of theelectronic keys 2 to be registered. This facilitates the process for registering a plurality ofelectronic keys 2, while maintaining a certain level of security. - (2) When acquiring the key ID codes KID-1 and KID-2 of the
electronic keys immobilizer ECU 6 also acquires the response codes of theelectronic keys immobilizer ECU 6 performs response code verification without communicating again with theelectronic keys electronic keys - (3) When the
registration tool 8 switches the operation mode of theimmobilizer ECU 6 to the registration mode, the quantity of theelectronic keys 2 that are to be registered is set. Thus, theimmobilizer ECU 6 recognizes the quantity of theelectronic keys 2 that are registered. This allows for theimmobilizer ECU 6 to terminate the registration process once theelectronic keys 2 are all registered and proceed to the next process. Thus, the registration process may be smoothly performed. - It should be understood that the present invention may be embodied in the following forms.
- In the above embodiment, when the
registration tool 8 switches the operation mode to the registration mode, the quantity of theelectronic keys 2 that are to be registered is set. However, the quantity of theelectronic keys 2 does not have to be designated in advance. For example, referring toFig. 3 , step S30, which is illustrated by broken lines inFig. 3 , may be added. In step S30, when theimmobilizer ECU 6 obtains the key ID codes KID of all of theelectronic keys 2 that are to be registered, theregistration tool 8 transmits an acquisition termination command (key ID acquisition termination signal) to theimmobilizer ECU 6. In response to the termination signal, theimmobilizer ECU 6 terminates the acquisition of the key ID codes KID and may then proceed to step S31. - In the above embodiment, after the
immobilizer ECU 6 acquires the key ID code KID, the response code of theelectronic key 2 is generated. However, the response code of theelectronic key 2 may be generated after theimmobilizer ECU 6 calculates the key encryption key K from the SEED code SC. - In the above embodiment, the encryption standard AES is used to generate the SEED code SC and the key encryption key K. However, a different encryption standard or encryption specification may be used.
- In the above embodiment, the
data center 10 may verify the user (person performing registration) before executing a registration command in the registration step that is performed under an online environment. For example, an ID code and password of the person performing the registration may be used to perform user verification. - In the above embodiment, the
registration tool 8 may be a versatile computer, such as a personal computer or a smartphone, incorporating software used exclusively for registration. - In the above embodiment, the encryption key is registered after the challenge-response verification is performed. However, as long as a certain level of security may be obtained, the challenge-response verification may be omitted.
- In the above embodiment, when acquiring the vehicle ID code VID, the vehicle ID code VID is illustrated on the
display 15 of thevehicle 1. Instead, a certain operation requesting for the vehicle ID code VID may be performed so that thevehicle 1 sends a mail to an address designated by the user. In this case, only the user that receives the mail can check the vehicle ID code VID. Thus, a high level of confidentiality may be obtained. - The above embodiment is applied to the
immobilizer system 3 in which theelectronic key 2 is inserted into the key cylinder. However, the electronic key system may be configured so that communication is performed between theelectronic key 2 and the vehicle 1 (controller) when theelectronic key 2 enters a communication area formed by thevehicle 1. - In the above embodiment, the electronic key system is applied to the
vehicle 1 but may be applied to a building such as a house. - The present examples and embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the equivalence of the appended claims.
- A method for registering first and second electronic keys (2a, 2b) to a controller (6) of a communication subject (1) through communication with a data center (10) includes acquiring first and second key identification information (KID-1, KID-2) from the first and second electronic keys (2a, 2b) with the controller (6), transmitting communication subject identification information (VID) together with both of the first and second key identification information (KID-1, KID-2) from the controller (6) to the data center (10), acquiring a first encryption key generation code (SC-A1) corresponding to the first electronic key (2a) together with a second encryption key generation code (SC-A2) corresponding to the second electronic key (2b) from the data center (10) with the controller, generating a first key encryption key (K-1) based on the first encryption key generation code (SC-A1) with the controller, generating a second key encryption key (K-2) based on the second encryption key generation code (SC-A2) with the controller, and storing the first and second key encryption keys (K-1, K-2) in the controller (6).
Claims (5)
- An electronic key registration method for registering a plurality of electronic keys (2a, 2b) to a controller (6) of a communication subject (1) through communication with a data center (10), wherein the electronic keys (2a, 2b) are capable of communicating with the controller (6), the electronic key registration method comprising:storing communication subject identification information (VID) and a communication subject encryption key (VK), which are unique to the communication subject (1), in the controller (6);storing the communication subject identification information (VID) and the communication subject encryption key (VK) in the data center (10);storing first key identification information (KID-1) and a first key encryption key (K-1), which are unique to a first electronic key (2a), in the first electronic key (2a);storing second key identification information (KID-2) and a second key encryption key (K-2), which are unique to a second electronic key (2b), in the second electronic key (2b);storing the first and second key identification information (KID-1, KID-2) and the first and second key encryption keys (K-1, K-2) in the data center (10);acquiring the first key identification information (KID-1) from the first electronic key (2a) with the controller (6);acquiring the second key identification information (KID-2) from the second electronic key (2b) with the controller (6);transmitting both of the first and second key identification information (KID-1, KID-2) together with the communication subject identification information (VID) from the controller (6) to the data center (10);generating a first encryption key generation code (SC-A1) with the data center (10), wherein the first encryption key generation code (SC-A1) is based on the communication subject encryption key (VK) and the first key encryption key (K-1);generating a second encryption key generation code (SC-A2) with the data center (10), wherein the second encryption key generation code (SC-A2) is based on the communication subject encryption key (VK) and the second key encryption key (K-2);obtaining both of the first and second encryption key generation codes (SC-A2, SC-A2) from the data center (10) with the controller (6);generating the first key encryption key (K-1) based on the first encryption key generation code (SC-A1) with the controller (6);generating the second key encryption key (K-2) based on the second encryption key generation code (SC-A2) with the controller (6); andstoring the first and second key encryption keys (K-1, K-2) in the controller (6).
- The electronic key registration method according to claim 1, further comprising:transmitting a challenge code used for challenge-response verification to the first electronic key (2a) from the controller (6) after the acquiring the first key identification information (KID-1) from the first electronic key (2a);transmitting a first response code to the controller (6) from the first electronic key (2a), wherein the first response code is generated based on the first key encryption key (K-1) and the challenge code by the first electronic key (2a);transmitting the challenge code to the second electronic key (2b) from the controller (6) after the acquiring the second key identification information (KID-2) from the second electronic key (2b);transmitting a second response code to the controller (6) from the second electronic key (2b), wherein the second response code is generated based on the second key encryption key (K-2) and the challenge code by the second electronic key (2b);generating a third response code based on the first key encryption key (K-1) and the challenge code with the controller (6) after the generating the first key encryption key (K-1) with the controller (6);generating a fourth response code based on the second key encryption key (K-2) and the challenge code with the controller (6) after the generating the second key encryption key (K-2) with the controller (6);verifying the first electronic key (2a) by comparing the first response code with the third response code; andverifying the second electronic key (2b) by comparing the second response code with the fourth response code.
- The electronic key registration method according to claim 1, further comprising:switching an operation mode of the controller (6) to a registration mode with a registration tool (8); andsetting the quantity of registered electronic keys (2a, 2b) with the registration tool (8) when switching to the registration mode.
- An electronic key registration system comprising:a plurality of electronic keys (2a, 2b) including first and second electronic keys (2a, 2b);a controller (6) arranged in a communication subject (1), wherein the controller (6) is capable of communicating with the electronic keys (2a, 2b); anda data center (10), whereinthe controller (6) includes a memory that stores commands executed by the controller (6) and configured to have the controller (6)acquire first key identification information (KID-1) from the first electronic key (2a),acquire second key identification information (KID-2) from the second electronic key (2b),transmit both of the first and second key identification information (KID-1, KID-2) together with communication subject identification information (VID) to the data center (10),acquire a first encryption key generation code (SC-A1) corresponding to the first electronic key (2a) together with a second encryption key generation code (SC-A2) corresponding to the second electronic key (2b) from the data center (10),generate a first key encryption key (K-1) based on the first encryption key generation code (SC-A1),generate a second key encryption key (K-2) based on the second encryption key generation code (SC-A2), andstore the first and second key encryption keys (K-1, K-2) in the controller (6).
- A controller (6) arranged in a communication subject (1), wherein the controller (6) is capable of communicating with a data center (10) and a plurality of electronic keys (2a, 2b) including first and second electronic keys (2a, 2b), the controller (6) comprising
a memory that stores commands executed by the controller (6) and configured to have the controller (6)acquire first key identification information (KID-1) from the first electronic key (2a),acquire second key identification information (KID-2) from the second electronic key (2b),transmit both of the first and second key identification information (KID-1, KID-2) together with communication subject identification information (VID) to the data center (10),acquire a first encryption key generation code (SC-A1) corresponding to the first electronic key (2a) together with a second encryption key generation code (SC-A2) corresponding to the second electronic key (2b) from the data center (10),generate a first key encryption key (K-1) based on the first encryption key generation code (SC-A1),generate a second key encryption key (K-2) based on the second encryption key generation code (SC-A2), andstore the first and second key encryption keys (K-1, K-2) in the controller (6).
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012242709A JP5964726B2 (en) | 2012-11-02 | 2012-11-02 | Electronic key registration system |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2728556A2 EP2728556A2 (en) | 2014-05-07 |
EP2728556A3 EP2728556A3 (en) | 2018-01-10 |
EP2728556B1 true EP2728556B1 (en) | 2019-12-04 |
Family
ID=49515213
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13190424.5A Active EP2728556B1 (en) | 2012-11-02 | 2013-10-28 | Electronic key registration method, electronic key registration system, and controller |
Country Status (4)
Country | Link |
---|---|
US (1) | US9020147B2 (en) |
EP (1) | EP2728556B1 (en) |
JP (1) | JP5964726B2 (en) |
CN (1) | CN103806758B (en) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6093503B2 (en) | 2012-01-31 | 2017-03-08 | 株式会社東海理化電機製作所 | Electronic key registration method |
US9704316B2 (en) | 2013-09-10 | 2017-07-11 | Gregory Paul Kirkjan | Contactless electronic access control system |
KR101535034B1 (en) * | 2014-08-20 | 2015-07-07 | 현대자동차주식회사 | System for registering a plurality of smart key and method thereof |
US9714004B2 (en) | 2015-02-02 | 2017-07-25 | Kabushiki Kaisha Tokai Rika Denki Seisakusho | Electronic key registration system |
US10277597B2 (en) | 2015-11-09 | 2019-04-30 | Silvercar, Inc. | Vehicle access systems and methods |
US10355854B2 (en) | 2015-12-17 | 2019-07-16 | Intel Corporation | Privacy preserving group formation with distributed content key generation |
US9992175B2 (en) * | 2016-01-08 | 2018-06-05 | Moneygram International, Inc. | Systems and method for providing a data security service |
US10339739B2 (en) * | 2017-01-26 | 2019-07-02 | SmartBox Technology, LLC | Vehicle key programming system and method |
US10491392B2 (en) * | 2017-03-01 | 2019-11-26 | Ford Global Technologies, Llc | End-to-end vehicle secure ECU unlock in a semi-offline environment |
US11227455B2 (en) * | 2018-03-18 | 2022-01-18 | Hy-Ko Products Company Llc | Distributed cloning tool assembly, system, and method for replication of vehicle access devices |
US11539782B2 (en) * | 2018-10-02 | 2022-12-27 | Hyundai Motor Company | Controlling can communication in a vehicle using shifting can message reference |
US11574513B2 (en) * | 2020-03-31 | 2023-02-07 | Lockfob, Llc | Electronic access control |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5940002A (en) * | 1997-10-10 | 1999-08-17 | Ut Automotive Dearborn, Inc. | Security system with random number remote communication |
JP2004088338A (en) * | 2002-08-26 | 2004-03-18 | Tokai Rika Co Ltd | Identification code registration update system, identification code registration update method, and identification code registration update program |
DE60307013T2 (en) * | 2002-10-28 | 2006-11-23 | Nissan Motor Co., Ltd., Yokohama | Engine control for a vehicle with electronic key |
JP4465998B2 (en) * | 2003-07-22 | 2010-05-26 | トヨタ自動車株式会社 | Mobile terminal and vehicle remote control system |
JP4195842B2 (en) * | 2003-07-28 | 2008-12-17 | 株式会社東海理化電機製作所 | Engine start / stop control system |
JP4092503B2 (en) * | 2004-03-26 | 2008-05-28 | 日産自動車株式会社 | Engine starting device and engine starting method |
US7961076B2 (en) * | 2006-02-28 | 2011-06-14 | International Business Machines Corporation | Methods and apparatuses for remote control of vehicle devices and vehicle lock-out notification |
JP2008059450A (en) * | 2006-09-01 | 2008-03-13 | Denso Corp | Vehicle information rewriting system |
JP4362136B2 (en) * | 2007-02-26 | 2009-11-11 | 三菱電機株式会社 | Electronic key device for vehicle |
JP5173891B2 (en) * | 2009-03-02 | 2013-04-03 | 株式会社東海理化電機製作所 | Secret key registration system and secret key registration method |
JP5257814B2 (en) * | 2009-07-13 | 2013-08-07 | 株式会社東海理化電機製作所 | Secret key registration system and secret key registration method |
JP5162566B2 (en) * | 2009-12-09 | 2013-03-13 | 本田技研工業株式会社 | Anti-theft device for outboard motor |
JP5765539B2 (en) * | 2010-09-27 | 2015-08-19 | 日本電気株式会社 | Information processing system, vehicle check method, and vehicle check program |
CN202003425U (en) * | 2011-03-31 | 2011-10-05 | 上海圣兆信息技术有限公司 | Central management system for monitoring intelligent lock |
JP5918004B2 (en) | 2012-04-27 | 2016-05-18 | 株式会社東海理化電機製作所 | Electronic key registration system |
JP5969263B2 (en) | 2012-05-10 | 2016-08-17 | 株式会社東海理化電機製作所 | Electronic key registration system |
JP5973224B2 (en) | 2012-05-10 | 2016-08-23 | 株式会社東海理化電機製作所 | Electronic key registration method |
JP5990406B2 (en) | 2012-06-06 | 2016-09-14 | 株式会社東海理化電機製作所 | Electronic key registration method |
JP5985894B2 (en) * | 2012-06-06 | 2016-09-06 | 株式会社東海理化電機製作所 | Electronic key registration method |
-
2012
- 2012-11-02 JP JP2012242709A patent/JP5964726B2/en not_active Expired - Fee Related
-
2013
- 2013-10-21 US US14/058,710 patent/US9020147B2/en active Active
- 2013-10-28 EP EP13190424.5A patent/EP2728556B1/en active Active
- 2013-10-29 CN CN201310526106.0A patent/CN103806758B/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
EP2728556A2 (en) | 2014-05-07 |
JP2014091400A (en) | 2014-05-19 |
CN103806758A (en) | 2014-05-21 |
CN103806758B (en) | 2018-01-26 |
EP2728556A3 (en) | 2018-01-10 |
US9020147B2 (en) | 2015-04-28 |
US20140126719A1 (en) | 2014-05-08 |
JP5964726B2 (en) | 2016-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2728556B1 (en) | Electronic key registration method, electronic key registration system, and controller | |
JP5990406B2 (en) | Electronic key registration method | |
US9137658B2 (en) | Electronic key registration system | |
JP6093503B2 (en) | Electronic key registration method | |
JP5866216B2 (en) | Electronic key registration system | |
JP5922419B2 (en) | Wireless communication system | |
EP2811686B1 (en) | Portable device registration system and portable device registration method | |
JP6093502B2 (en) | Electronic key registration method | |
JP5855957B2 (en) | Mobile device registration system | |
JP5767129B2 (en) | Electronic key registration system | |
JP5855958B2 (en) | Mobile device registration system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20131028 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 9/06 20060101ALN20171206BHEP Ipc: G07C 9/00 20060101AFI20171206BHEP Ipc: H04L 9/08 20060101ALI20171206BHEP |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180622 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 9/06 20060101ALN20190515BHEP Ipc: G07C 9/00 20060101AFI20190515BHEP Ipc: H04L 9/08 20060101ALI20190515BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G07C 9/00 20060101AFI20190517BHEP Ipc: H04L 9/08 20060101ALI20190517BHEP Ipc: H04L 9/06 20060101ALN20190517BHEP |
|
INTG | Intention to grant announced |
Effective date: 20190605 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1210342 Country of ref document: AT Kind code of ref document: T Effective date: 20191215 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602013063556 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20191204 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200304 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200304 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200305 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200429 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200404 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602013063556 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1210342 Country of ref document: AT Kind code of ref document: T Effective date: 20191204 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
26N | No opposition filed |
Effective date: 20200907 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602013063556 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20201028 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201028 Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20201031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210501 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201031 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201031 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201028 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201028 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191204 |