Control of a motor vehicle

Abstract

A method (200) for controlling a motor vehicle (105) comprises steps of capturing, by a key management system (110), a request to establish a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); depositing, by the key management system (110), a request to establish a lock in a digital vehicle key stored on a mobile device; transmitting the request from the mobile device to the motor vehicle (105); and establishing a lock on the part of the motor vehicle (105).

Description

[0001] The present invention relates to the control of a motor vehicle by means of a digital vehicle key. In particular, the invention relates to the addition of a newly created digital vehicle key.

[0002] A motor vehicle includes a control unit configured to operate a predetermined security function of the vehicle based on a digital vehicle key. A digital vehicle key, which is assigned authorization to control a security function, is stored in the control unit. This security function may include, in particular, central locking or an immobilizer. Another part of the digital vehicle key may be stored on a user's device. The user can wirelessly present their digital vehicle key to the vehicle to control the security function.

[0003] A new vehicle key can be added to the system by creating the key and submitting it to a key management system, which signs it and stores it on the vehicle. The process of creating or adding a newly generated digital vehicle key represents a potential attack vector against the security concept. To protect against this, a block can be implemented on the vehicle, preventing it from accepting any newly generated digital vehicle key for storage. The block can be implemented directly on the vehicle. Alternatively, a request to implement a block can be transmitted wirelessly to the vehicle. If a wireless connection cannot be established, for example, because the vehicle is located in an underground parking garage with radio wave shielding, the request cannot be received and the block cannot be implemented.

[0004] One of the problems underlying the present invention is to provide an improved technique for securing a motor vehicle by means of a digital vehicle key. The invention solves this problem by means of the subject matter of the independent claims. Dependent claims describe preferred embodiments.

[0005] It was recognized that communication between a motor vehicle that can be controlled by means of a wireless key and a key management system can be established by transmitting a message in a digital key stored on a mobile device.

[0006] The mobile device can be moved independently of the vehicle, so any radio interference in the vicinity of the vehicle is only temporary for the mobile device. This allows the key to transmit a request to activate or deactivate a lock, preventing a newly generated vehicle key from being used to control the vehicle. Information can be transmitted or stored in encrypted form, ensuring system security.

[0007] The inventive concept can be expressed in various methods, different control devices for a motor vehicle, and different key management systems. Furthermore, the invention can be realized by a motor vehicle or a system comprising at least one motor vehicle.

[0008] A procedure, a control device for a motor vehicle, and a key management system are proposed for setting up a barrier.

[0009] A procedure for controlling a motor vehicle comprises steps of capturing, by a key management system, a request to establish a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle; depositing, by the key management system, a request to establish a lock in a digital vehicle key stored on a mobile device; transmitting the request from the mobile device to the motor vehicle; and establishing a lock by the motor vehicle.

[0010] The digital vehicle key can be configured according to the proposals of the Car Connectivity Consortium. A technical specification of the underlying technology has been published. A block imposed by the vehicle may, in particular, prevent the vehicle from accepting a certification package for a newly created digital vehicle key.

[0011] The request is preferably stored in the vehicle key only if direct communication between the key management system and the vehicle is unsuccessful. For example, if communication fails for a predetermined period of a few seconds or minutes, transmission via the key can be used as an alternative. Optionally, an attempt can also be made to transmit the request directly from the key management system to the vehicle.

[0012] The request can be stored in a mailbox on the vehicle key. The vehicle key can support a private mailbox and / or a confidential mailbox, with the private mailbox being the preferred option and not being assigned to any specific purpose. Information is stored encrypted in both cases. Preferably, the request is encrypted in such a way that only the recipient, and optionally the sender, can decrypt the message. A stored message can also be cryptographically signed, thus preventing any undetected modification.

[0013] In response to a received request, the key management system can implement a block. This block can prevent a newly created digital key from being assigned an attestation package to the vehicle. Blocks implemented by the key management system and the vehicle itself can operate independently and each can prevent the addition of a new vehicle key on its own.

[0014] A control device for a motor vehicle comprises a means of communication with a mobile device on which a digital vehicle key for the motor vehicle is stored; and a processing unit. The processing unit is configured to read a request stored in the vehicle key, addressed from a key management system to the motor vehicle; the request being to establish a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle; and to establish the requested lock.

[0015] A key management system for digital vehicle keys for a motor vehicle comprises a communication device with a mobile device on which a digital vehicle key for the motor vehicle is stored; and a processing device. The processing device is configured to read a request stored in the vehicle key, directed from the motor vehicle to the key management system, wherein the request concerns the establishment of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle; and to establish the requested lock.

[0016] Erected barriers can be dismantled in a coordinated manner by also using a digital vehicle key for information transmission if necessary. A procedure, a control device for a motor vehicle, and a key management system are proposed for dismantling a barrier.

[0017] A method for controlling a motor vehicle comprises the steps of detecting, by the motor vehicle, a request to remove a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle; locating a mobile device on which a digital vehicle key for the motor vehicle is stored, within the vicinity of the motor vehicle; depositing, by the motor vehicle, a request directed from the motor vehicle to a key management system in the digital vehicle key, the request being for the removal of a lock; transmitting the request from the mobile device to the key management system; and removing a corresponding lock by the key management system.

[0018] The request is preferably stored in the vehicle key only if direct communication between the vehicle and the key management system is unsuccessful. The request can be stored in a mailbox on the vehicle key, particularly a private mailbox. Further options regarding the transmission of a request to establish a lock are described above.

[0019] Furthermore, in response to the received request, a block existing on the vehicle is preferably removed; this block prevents the processing of an attestation package for a newly created digital vehicle key. If no such block exists, the key management system creates the attestation package and provides it to the vehicle. A newly created digital vehicle key can only be used to control the vehicle after the attestation package has been evaluated by the vehicle. The vehicle's own block can prevent the acceptance or processing of an attestation package.

[0020] A control device for a motor vehicle comprises a means of communication with a mobile device on which a digital vehicle key for the motor vehicle is stored; and a processing device. The processing device is configured to store in the digital vehicle key a request directed from the motor vehicle to a key management system; the request being for the removal of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle.

[0021] A key management system for digital vehicle keys for a motor vehicle comprises a device for communicating with a mobile device on which a digital vehicle key for the motor vehicle is stored; and a processing device configured to read a request stored in the vehicle key, directed from the motor vehicle to the key management system; wherein the request concerns the removal of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle; and the removal of the requested lock.

[0022] Furthermore, a motor vehicle is proposed that includes one of the control devices described herein. The motor vehicle may, in particular, be a passenger car. In addition, a system is proposed that includes at least one motor vehicle described herein and a key management system described herein.

[0023] A control device and a key management system described herein may each be configured to partially or completely execute a method described herein. For this purpose, a processing unit may be used, preferably of electronic design, comprising, for example, an integrated circuit, a programmable logic device, or a programmable microcomputer. The method may be implemented as a configuration or as a computer program product with program code means for the processing unit. The configuration or the computer program product may be stored on a computer-readable data carrier. Features or advantages of the method may be transferred to the device or vice versa.

[0024] The invention will now be described in more detail with reference to the attached drawings, in which: Fig. 1 a system; Fig. 2. A flowchart of a process; Fig. 3 a flowchart of another procedure; and Fig. 4. A flowchart of yet another procedure is illustrated.

[0025] Fig. Figure 1 shows a system 100 with a motor vehicle 105 and a key management system 110. The motor vehicle 105 includes a control device 115 configured to control a predetermined function of the motor vehicle 105, in particular a security function, based on a digital vehicle key. The security function may, for example, include unlocking a vehicle door or hatch of the motor vehicle 105, deactivating an immobilizer, or activating a drive motor.

[0026] The concept of the digital vehicle key presented here preferably follows the proposals of the Car Connectivity Consortium (CCC). In simplified terms, a specific digital vehicle key is assigned to a first person 120 and is typically stored on a first mobile device 125, which is also assigned to that first person 120. The digital vehicle key is additionally stored on the control unit 115 in the motor vehicle 105. Controlling a security function of the motor vehicle 105 requires cryptographic communication between the control unit 115 and the mobile device 125. Preferably, an asymmetric cryptographic method is used to authenticate one of the communication partners. The digital vehicle key can comprise a private part, which is stored on the mobile device 125, and a public part, which is stored on the control unit 115.

[0027] Conversely, the first mobile device 125 may possess a public key of the control device 115, whose corresponding private key is known only to the control device 115. Mutual authentication between the first mobile device 125 and the control device 115 can be performed in a so-called standard transaction. To make their digital key accessible on the first mobile device 125, the person 120 can first authenticate themselves to the first mobile device 125, for example, by presenting a biometric feature or by entering a predetermined secret.

[0028] A new digital vehicle key can be created and assigned to a second person 130, who is assigned a second mobile device 135 for this purpose. For example, it is assumed that the first person 120 is the owner of the vehicle 105 and that the digital vehicle key assigned to them authorizes them to issue or sign a newly created vehicle key. The second person 120 is usually referred to as a friend.

[0029] The generation process can include the key management system 110 digitally signing a newly created digital vehicle key and creating an attestation package that includes the signed key, and storing this attestation package with the motor vehicle 105 or the control device 115.

[0030] It is proposed to selectively prevent or re-enable the addition of a newly created digital vehicle key to a pool of valid digital vehicle keys that can be used to control the motor vehicle 105. It is particularly preferred that a lock be implemented or removed to prevent the addition of a newly created vehicle key by the motor vehicle 105 or the control device 115 and / or also by the key management system 110.

[0031] Optionally, a device 140 can be provided through which a request to the key management system 110 for the creation of a lock can be submitted directly. Device 140 can be equipped with its own digital vehicle key, which can be used to generate the request. Access to device 140 can be restricted in any way. For example, a person 120 or 130 who wishes to set or remove a lock can explain their legal position that authorizes them to do so. Their request can then be reviewed by another person or automatically by device 140.

[0032] Fig. Figure 2 shows a flowchart of a procedure 200 for exiting or participating in a process for key creation for a motor vehicle 105. Exiting corresponds to erecting at least one lock; and participating to removing all locks.

[0033] In step 205, it is assumed that the motor vehicle 105 is in an initial state with regard to its control by means of a digital vehicle key. This state can be reached when the motor vehicle 105 is handed over by the manufacturer to its first owner.

[0034] In step 210, an owner key can be generated. This is a digital vehicle key, which is typically assigned the authorization to create or sign a newly created vehicle key. In other words, the first person 120, as the owner, can use their assigned vehicle key to create or cryptographically sign further digital vehicle keys.

[0035] In step 215, additional keys can be generated if necessary, for example, for the second person 130. If the number of digital vehicle keys that can be used to control the motor vehicle 105 meets the requirements of the first person 120, they can request to stop adding new vehicle keys. To do this, the first person 120 can send a corresponding message to the control device 115 using their first mobile device 125 and the digital vehicle key stored on it.

[0036] In step 225, the control device 115 can check whether a received request grants authorization to exit the vehicle. Specifically, it can verify whether this authorization is assigned to the digital vehicle key on which the request was based. Authorizations for a digital vehicle key are generally defined before the vehicle key is generated or cryptographically signed.

[0037] In step 230, it can be checked whether at least one digital vehicle key is present in the inventory of valid digital vehicle keys for vehicle 105, which can be used as a basis for controlling later participation in adding a newly created digital vehicle key. In other words, before a block is placed against adding a newly created digital vehicle key for vehicle 105, it can be checked whether predetermined conditions are met in order to later remove the block.

[0038] In step 235, a corresponding lock can be installed on the motor vehicle 105 or on the control device 115. This lock can, in particular, prevent the acceptance of an attestation package for a newly created digital vehicle key for the motor vehicle 105 or the storage of the digital vehicle key contained therein.

[0039] In step 240, a message can be transmitted from vehicle 105 to the key management system to instruct it to also implement a block against adding a digital vehicle key for vehicle 105. This block can prevent a key signing request or a key tracking request for vehicle 105 from being fulfilled. Furthermore, it can prevent an information packet regarding a newly created digital vehicle key from being transmitted to vehicle 105 or control unit 115.

[0040] Adding a newly created digital vehicle key to the inventory of valid vehicle keys for vehicle 105 is already prevented if only one of the locks is active. Existing digital vehicle keys in the inventory can still be used. Optionally, a digital vehicle key in the inventory can also be invalidated while one of the locks is active. In this case, priority is given to ensuring that at least one digital vehicle key remains in the inventory that can be used to remove the lock.

[0041] An existing lock on the vehicle (105) and / or the key management system (110) can remain in place indefinitely. An optional method is provided to remove the lock. This can be done, in particular, using a digital vehicle key to which appropriate authorization can be assigned.

[0042] Fig. Figure 3 shows a flowchart of a procedure 300 for establishing a block against the addition of a newly created vehicle key for the motor vehicle 105. At the beginning of the procedure 300, all participants 105, 110, 120, 125, 135 can be informed that a new digital vehicle key can be created and made functional for controlling the motor vehicle 105.

[0043] In step 205, a person 120 can request the installation of a lock via device 140. To do this, the person 120 can identify and / or authenticate themselves to device 140. If the request is successfully processed, a request to install a lock can be transmitted to the key management system 110 in step 310.

[0044] In step 315, person 120 can enter information on a mobile device 125 to initiate a lock. In step 320, person 120 can authenticate themselves. Optionally, they can reconfirm their entry to prevent unintentional locking. In step 325, a request to establish a lock can be created based on a digital vehicle key stored on person 110's mobile device 125. The request can be transmitted to the key management system 110 in step 330. In step 335, the key management system 110 can establish the lock.

[0045] Following step 310 or step 335, the key management system 110 can verify the request based on the digital vehicle key used for its creation. If the verification is successful, a request to establish a lock can be transmitted to the vehicle 105 in step 340, which can then establish the lock in step 345. Should step 345 fail, particularly because a communication link between the key management system 110 and the vehicle 105 is temporarily unavailable, the process can still proceed with procedure 300.

[0046] In step 350, a notification of a set lock can be sent from the key management system 110 to the mobile device 125 of person 110. Furthermore, a request directed to the vehicle 105 can be transmitted to the mobile device 125, whereby the request concerns the creation of a lock by the vehicle 105. The request can be stored in a mailbox of the digital vehicle key of the owner 120.

[0047] In step 355, mobile device 110 can adjust the user interface for person 110 so that the set block is recognizable or the option to set a block is no longer offered. Furthermore, in step 330, sharing an existing key with another person 130 can be prevented.

[0048] Similarly, optionally in step 365, a notification of the imposed lock can be transmitted from the key management system 110 to a mobile device 135. The mobile device 135 is assigned to a person 130 who is not the owner of the vehicle 105 or whose digital vehicle key does not have the authorization to sign a newly created vehicle key. In step 370, sharing an existing vehicle key by person 130 can be prevented. Furthermore, a request addressed to the vehicle 105 can be transmitted to the mobile device 135, whereby the request concerns the creation of a lock on the vehicle 105. The request can be stored in a mailbox of the digital vehicle key of person 130.

[0049] In step 375, the request to establish a lock can be transmitted from mobile device 125 to vehicle 105 as soon as communication is possible between the owner's mobile device 125 (120) and the vehicle 105. Similarly, in step 375, the request to establish a lock can be transmitted from mobile device 135 to vehicle 105 as soon as communication is possible between the friend's mobile device 135 (130) and the vehicle 105. Steps 375 and 380 are in Fig. Three alternatives are presented, but the current technique also works if a request is transmitted multiple times.

[0050] In step 385, the motor vehicle can verify a received request and, if the verification is successful, establish the requested lock locally.

[0051] Fig.Figure 4 shows a flowchart of another method 400 for removing a block against the addition of a newly created digital vehicle key for a motor vehicle 105. In one embodiment, a counter is provided for both the motor vehicle 105 and the key management system 110, the counter value of which can be incremented when a block is established. At the beginning of the method, it is assumed that the counter values ​​of the motor vehicle 105 and the key management system 110 are identical.

[0052] In step 405, person 120 makes an entry at vehicle 105 to remove a lock. In step 410, vehicle 105 checks for the presence of a mobile device 125 within its range and determines that a digital vehicle key stored on it is authorized to set a lock. If the check is successful, in step 420, vehicle 105 can set a lock and increase the local meter reading.

[0053] The increased meter reading can be transmitted in step 420, along with a request to establish a lock, to the key management office 110. If this step is successful, the process can continue in the conventional manner.

[0054] However, if direct communication with the key management 110 is not possible, a request to remove the lock can be created by the key management in step 425.

[0055] In step 430, the request, along with the current meter reading, can be transmitted to the mobile device 125 of the owner 120. This transmission preferably occurs as soon as the mobile device 125 is within communication range of the vehicle 105. Both pieces of information can be stored in a mailbox of the owner 120's digital vehicle key, which is stored on the mobile device 125.

[0056] In step 435, the request can be transmitted from the mobile device 125 to the key management system 110. It is possible to wait until a communication connection between the mobile device 125 and the key management system 110 can be established.

[0057] Similarly, in step 440, the request, along with the current meter reading, can be transmitted to the mobile device 135 of friend 120. This transmission preferably occurs as soon as the mobile device 135 is within communication range of the vehicle 105. Both pieces of information can be stored in a mailbox of the owner 120's digital vehicle key, which is stored on the mobile device 125.

[0058] In step 445, the request can be transmitted from the mobile device 125 to the key management system 110. This can be done by waiting until a communication connection can be established between the mobile device 135 and the key management system 110.

[0059] Steps 430 and 435 are presented as alternatives to steps 440 and 445; however, a technique described herein also works when several paths are pursued in parallel.

[0060] In step 455, the vehicle 105 can verify a received request. If the verification is successful, a lock can be set locally on the vehicle 105. Additionally, the local counter can be incremented to match the received counter reading from the key management system 110. This resynchronizes the counters of the key management system and the vehicle 105. Reference sign 100 System 105 motor vehicles 110 Key Management 115 Control device 120 first person 125 first mobile device 130 second person 135 second mobile device 100 System 105 motor vehicles 110 Key Management 115 Control device 120 first person (owner) 125 first mobile device 130 second person (friend) 135 second mobile device 140 Device 200 procedures 205 new motor vehicles 210 Generate owner keys 215. Possibly generate another key. 220 Record exit request 225 Request justified? 230 vehicle keys exist for participation? 235 vehicles blocked Lock 240 key management 245 Record participation request, check eligibility Release 250 vehicles Release 255 key management 260 Synchronize 300 procedures 305 Create a request for a lock 310 Request to set up a lock (proprietary message) 315 Input: Set lock 320 Confirmation and authentication of the person 325 Generate a request to establish a barrier 330 Submit request 335 Check request 340 Submit request to set a block Set 345 block 350 Send notification of set block 355 Deactivate the control for setting a lock 360 key sharing not possible 365 Send notification of set block Sharing 370 keys is not possible. 375 Request to erect a barrier upon next contact with motor vehicle 370 Submit request to erect a barrier upon next contact with motor vehicle 385 Check request, establish lock 400 procedures 405 Input: Remove lock 410 Check the presence and authorization of a digital key 415 Remove lock, increase meter reading, meter unsynchronized 420 Request and meter reading 425 Generate a request to remove a block, attach meter reading 430 Submit a request to remove a block to an owner's mobile device 435 Manage key with Submit request to key management for removal 440 Send a request to remove a block to a friend's mobile device 445 Submit dismantling request to key management Increase meter reading to 450, submit confirmation with meter reading 455 Vehicle locked, counter synchronized

Claims

[1] Method (200) for steering a motor vehicle (105), wherein the method (200) comprises the following steps: - Capture, through a key management system (110), a request to establish a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); - Deposit, through the key management (110), a request to establish a lock in a digital vehicle key stored on a mobile device; - Transmitting the request from the mobile device to the motor vehicle (105); and - Erection of a barrier by the motor vehicle (105). [2] Method (200) according to claim 1, wherein the request is stored in the vehicle key only if direct communication between the key management (110) and the motor vehicle (105) is unsuccessful. [3] Method (200) according to claim 1 or 2, wherein the request is stored in a mailbox of the vehicle key. [4] Method (200) according to one of the preceding claims, wherein the key management (110) establishes a lock in response to the received request, so that no attestation package is provided to the motor vehicle (105) for a newly created digital key. [5] Control device (115) for a motor vehicle (105), wherein the control device (115) comprises the following elements: - a device for communication with a mobile device on which a digital vehicle key for the motor vehicle (105) is stored; and - a processing device designed to read a request stored in the vehicle key, which is directed from a key management unit (110) to the motor vehicle (105); - where the requirement concerns the establishment of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); and - to erect the requested lock. [6] Key management (110) for digital vehicle keys for a motor vehicle (105), wherein the key management (110) comprises the following elements: - a device for communication with a mobile device on which a digital vehicle key for the motor vehicle (105) is stored; and - a processing device designed to read a request stored in the vehicle key, directed from the motor vehicle (105) to the key management system (110); - where the requirement concerns the establishment of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); and - to erect the requested lock. [7] Method (200) for steering a motor vehicle (105), wherein the method (200) comprises the following steps: - Detection, by a motor vehicle (105), of a request to remove a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); - Determining a mobile device on which a digital vehicle key for the motor vehicle (105) is stored, in the area of ​​the motor vehicle (105); - Depositing, by the motor vehicle (105), a request directed from the motor vehicle (105) to a key management system (110) in the digital vehicle key; - where the requirement concerns the removal of a barrier; - Transmitting the request from the mobile device to the key management (110); and - Removal of a corresponding lock by the key management (110). [8] Method (200) according to claim 7, wherein the request is stored in the vehicle key only if direct communication between the motor vehicle (105) and the key management system (110) is unsuccessful. [9] Method (200) according to claim 7 or 8, wherein the request is stored in a mailbox of the vehicle key. [10] Method (200) according to any one of claims 7 to 9, wherein in response to the received request a lock existing on the part of the motor vehicle (105) is removed; wherein the lock prevents the processing of an attestation package for a newly created digital vehicle key. [11] Control device (115) for a motor vehicle (105), wherein the control device (115) comprises the following elements: - a device for communication with a mobile device on which a digital vehicle key for the motor vehicle (105) is stored; and - a processing device designed to store in the digital vehicle key a request directed from the motor vehicle (105) to a key management system (110); - where the requirement concerns the removal of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105). [12] Key management (110) for digital vehicle keys for a motor vehicle (105), wherein the key management (110) comprises the following elements: - a device for communication with a mobile device on which a digital vehicle key for the motor vehicle (105) is stored; and - a processing device designed to read a request stored in the vehicle key, directed from the motor vehicle (105) to the key management system (110); - where the requirement concerns the removal of a lock against the addition of a newly created digital vehicle key that can be used to control the motor vehicle (105); and - to remove the requested block. [13] Motor vehicle (105) comprising a control device (115) according to claim 5 and / or 11. [14] System comprising a motor vehicle (105) according to claim 13 and a key management system (110) according to claim 6 and / or 12.

Images