Apparatus, device, method and computer program

Abstract

Embodiments relate to an apparatus (30). An apparatus (30) for a vehicle includes: interface circuitry (32) configured to receive a signal including information indicative of a digital key protocol from a device; and storage circuitry (36) configured to store the information.

Description

Technical Field

[0001] The present disclosure relates to the field of digital identity authorization. Embodiments relate to apparatus, devices, methods and computer programs. Background Art

[0002] The authorization process enables the user of a device to enable a certain function using his device, for example, to verify a bank transfer, to verify the generation of a digital key. For example, using a digital key enables the user of a vehicle to open the vehicle particularly easily. In particular, smart access can be used to configure a user device to act as a digital key for a vehicle. To this end, a user (owner) device (also called a sharer) can pass an invitation for a digital key (also called a data key) to a friend device (also called a sharee) to configure the friend device. This allows the friend device to be configured / authenticated in such a way that access to the vehicle (e.g., opening, starting, etc.) is enabled via wireless communication (e.g., Bluetooth or ultra-wideband technology (UWB)). However, to perform key sharing, the friend device needs to establish a connection with a network entity (e.g., a base station) via remote communication. Therefore, it may be necessary to improve the key sharing process.

[0003] Therefore, it is found that key sharing can be improved by using a device. The device can be, for example, a smart card (which is battery-free and receives power through at least one of a card connector or induction) or a key fob. Neither the smart card nor the key fob contains an internet connection. Therefore, the key sharing process can be simplified because an internet connection of the sharee (device) is not required. Summary of the invention

[0004] An example provides an apparatus for a vehicle, comprising: an interface circuit system configured to receive a signal including information indicating a digital key protocol from a device to enable a key sharing process between the device and the device; and a storage circuit system configured to store information. In this way, the apparatus can be configured to operate in accordance with a digital key protocol (e.g., a standard of the Car Connectivity Consortium (CCC), such as CCC standard version 3 ([1])). Thus, the battery-free device can be used as a digital key according to the CCC standard [1].

[0005] In an example, the interface circuit system may also be configured to receive a signal from the device via at least one of Bluetooth, Bluetooth low energy, ultra-wideband, wireless local area network, or near field communication. In this way, the device may receive information required to be configured as a digital key according to [1] through a short-range communication process. Therefore, depending on the communication technology used, the device may not necessarily need to implement a battery, for example, an NFC interface may not require a battery. For example, an interface of Bluetooth, Bluetooth low energy, ultra-wideband, wireless local area network, or near field communication is an interface that complies with [1].

[0006] In an example, the apparatus may further include a processing circuit system configured to generate a universal instance certificate authority that can be used by multiple vehicle original equipment manufacturers. For example, the universal instance certificate authority can be trusted by multiple vehicle original equipment manufacturers (OEMs) and can therefore be used by multiple vehicle original equipment manufacturers (OEMs). In this way, the storage required on the storage circuit system can be reduced because the instance certificate authority can be used for multiple OEMs.

[0007] In an example, the signal may include information indicating a digital key applet. Thus, the digital key applet may be stored on the device. Thus, the digital key applet may be stored in a storage circuit system, such as a digital key applet according to [1]. Thus, the device may be used as a sharee according to [1].

[0008] In an example, the signal may include information indicating that a digital key was generated during digital key sharing. In this way, information about the key generated for the sharee may be stored on the device.

[0009] In an example, the interface circuit system can also be configured to transmit a key signing request to the device, the request including a certificate, the certificate including a friend digital key certificate. In this way, the device can store information required for the signing process of the generated digital key.

[0010] In an example, the processing circuit system can also be configured to generate a digital key and overwrite the digital key in the storage circuit system if the storage circuit system already contains a digital key. For example, the processing circuit system can be configured to generate a digital key to manage the qualifications and / or entitlements of the digital key, for example, if the storage circuit system already contains a digital key, overwrite the digital key in the storage circuit system. In this way, digital key management can be improved.

[0011] An example provides a device for setting up a device as described above. The device includes: an interface circuit system configured to transmit a signal containing information indicating a digital key protocol to the device to enable a key sharing process between the device and the device; and a processing circuit system (14) configured to generate the signal. In this way, the device can be configured to operate in accordance with a digital key protocol as described in [1]. Therefore, the battery-free device can be used as a digital key according to the CCC standard [1].

[0012] In an example, the interface circuit system can also be configured to transmit a tracking signal to register the digital key to a backend, such as an OEM, and the processing circuit system can also be configured to generate the tracking signal. In this way, the digital key can be maintained by the backend.

[0013] In an example, the signal may also include information indicative of a digital key. In this way, the device may transmit the information necessary to gain access to the vehicle.

[0014] In an example, the signal also includes information indicating that the digital key stored on the device is invalid. For example, the information can indicate management of the qualifications and / or rights of the digital key stored on the device. In this way, the device can maintain the device, for example, the storage circuit system of the device.

[0015] In an example, the tracking signal may also include information indicating a certificate used to generate a digital key stored on the device. In this way, the device may transmit information about the certificate to the backend.

[0016] In an example, the device is at least one of user equipment or a smart card reader.

[0017] An example provides a method for an apparatus, comprising receiving a signal including information indicating a digital key protocol from a device to enable a key sharing procedure between the apparatus and the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Some examples of apparatus, methods and / or computer programs will be described below, by way of example only, and with reference to the accompanying drawings, in which

[0019] Figure 1 A block diagram showing an example of an apparatus;

[0020] Figure 2 A block diagram showing an example of a device;

[0021] Figure 3 A block diagram showing an example of applet deployment;

[0022] Figure 4a , 4b An example of a device structure is shown; and

[0023] Figure 5 An example of a method is shown. DETAILED DESCRIPTION

[0024] Various example embodiments will now be described more fully with reference to the accompanying drawings, in which some example embodiments are illustrated. In the various figures, the thickness of lines, layers or regions may be exaggerated for clarity. Optional components may be illustrated using broken lines, dashed lines or dotted lines.

[0025] Thus, although the example embodiments are capable of various modifications and alternative forms, embodiments thereof are shown by way of example in the drawings and will be described in detail herein. However, it should be understood that there is no intent to limit the example embodiments to the particular forms disclosed, but rather, the example embodiments are intended to cover all modifications, equivalents, and alternatives within the scope of the invention. Throughout the entire description of the drawings, like reference numerals refer to like or similar elements.

[0026] As used herein, the term "or" refers to a non-exclusive or, unless otherwise indicated (e.g., "otherwise" or "or alternatively"). In addition, as used herein, words used to describe relationships between elements should be broadly interpreted to include direct relationships or the presence of intermediate elements, unless otherwise indicated. For example, when an element is referred to as being "connected" or "coupled" to another element, the element may be directly connected or coupled to the other element, or there may be intermediate elements. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intermediate elements. Similarly, words such as "between," "adjacent," etc. should be interpreted in a similar manner.

[0027] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when used herein, the terms "include" or "comprise" specify the presence of the features, integers, steps, operations, elements, or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.

[0028] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the example embodiments belong. It will also be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning consistent with the meaning of the terms in the context of the relevant art, and should not be interpreted as an idealized or overly formal meaning unless explicitly defined herein.

[0029] Figure 1 A block diagram of an example of an apparatus 30 is shown. The apparatus 30 for a vehicle includes an interface circuit system 32 configured to receive a signal from a device, the signal including information indicating a digital key protocol to enable a key sharing process between the apparatus and the device, and a storage circuit system 36 configured to store the information.

[0030] The device can be a battery-free device and can receive power via at least one of a card connector or induction. The device is an offline device such that the device does not include an Internet connection. In [1], the sharee requires an Internet connection to perform the digital key sharing process. In contrast, the device 30 can be configured to act as a sharee according to [1] without requiring an Internet connection, for example to connect to a relay server. Alternatively, the device can act as a relay server for the device to provide the device 30 with all required information so that the device 30 can act as a sharee.

[0031] For example, the device 30 can be used as an offline token. The device 30 can include a secure element that hosts an applet and key data, such as a digital key applet. The applet and key data can be stored in a storage circuit system 36 of the device 30. The device 30 can have an interface that complies with [1], such as NFC, BLE or UWB. By using the device, management of offline tokens using the CCC infrastructure and / or user contact points defined in [1] can be provided. For example, if the device 30 is a smart card, then it can be used to replace known systems, such as a key fob. In this way, the production costs of the sharee can be reduced.

[0032] The key sharing process between the device 30 and the sharer can be accomplished using the CCC key sharing based mechanism described in [1]. Instead of receiving key creation and certification data from the sharer (e.g., owner / administrator / server) via the device's Internet link, the data required for key creation can be transmitted to the device 30 via the device using the interface circuit system 32. In this way, the device 30 does not need to be configured to access the Internet. Optionally, the device can act as a proxy. The device (e.g., the proxy) can be the NFC interface of the sharer itself (e.g., shared with the device 30 itself via the NFC interface or BLE interface of the owner's user equipment), an NFC reader connected to a personal computer, linked to a key creation server directly or through a device OEM server. Optionally, encryption on the device interface circuit system can increase protection against man-in-the-middle attacks.

[0033] In an example, the interface circuit system may also be configured to receive a signal from the device via at least one interface of Bluetooth, low-power Bluetooth, ultra-wideband, wireless local area network, or near-field communication. The device 30 does not have a direct Internet connection interface. The digital key framework on the device may only be required for non-NFC dedicated keys. The digital key framework function of the device may provide basic BLE / UWB functions (see also FIG. 4). In this way, the production cost of the device 30 can be reduced. The digital key framework can be hosted on an NFC, BLE, or UWB chip included by the device 30 (e.g., by the interface circuit system 32). For example, the interface circuit system can be an NFC, BLE, or UWB chip. Therefore, a separate chip may not be required. The interface circuit system 32 can be used to communicate with a device (e.g., an NFC reader) for applet deployment (e.g., installing / storing a digital key applet on the device 30), key deployment (e.g., transmitting information about the key sharing process) and / or key management (e.g., deleting expired digital keys on the device 30).

[0034] In an example, the device 30 may also include a processing circuit system that is configured to generate a universal instance certificate authority that can be used by multiple vehicle original equipment manufacturers. For example, the universal instance certificate authority can be trusted by multiple vehicle original equipment manufacturers (OEMs) and can therefore be used by multiple vehicle OEMs. For example, the device 30 can use the same instance CA for multiple vehicle OEMs to simplify implementation and / or data handling. In this way, scalability can be provided even after the device 30 is produced. For example, the universal instance certificate authority can be generated by using a digital key applet, for example, which can be stored on the device 30, for example, during a setup process.

[0035] For example, [1] can be changed to include a generic instance CA. In Section 4.1, the applet instance layout, the feature "A different instance CA should be used for each vehicle OEM." in lines 8 and 9 can be removed. This feature can be replaced by "A (generic) instance CA should be used for different vehicle OEMs." In this way, [1] can be adapted to a generic instance CA.

[0036] In an example, the signal may include information indicating a digital key applet. For example, the digital key applet may be stored in a secure element of the device 30, e.g., contained by the storage circuit system 36. The digital key applet may be an applet compliant with [1]. The information indicating the digital key applet may be received during the manufacturing process of the device 30, may be received from a chip manufacturer of an NFC / SE chip that may be integrated into the device 30. Thus, the digital key applet may be stored on the device 30 before the user may become the owner of the device 30.

[0037] In an example, the signal may include information indicating the generation of a digital key during digital key sharing (e.g., a key sharing process). For example, KeyCreation data and / or Attestation data according to [1] may be transmitted from a device (e.g., owner, administrator, server) from a backend via an Internet link to the apparatus 30. In this way, the apparatus 30 may receive information required for the key sharing process without an Internet connection.

[0038] In an example, the interface circuit system 32 may also be configured to transmit a key signing request to the device, the request including a certificate including a friend digital key certificate. Therefore, the device certificate chain defined in Section 16.4 of [1] may be adapted to the apparatus 30 to consume less storage capacity. In this way, the verification of the certificate chain required for the key sharing process may be partially performed by the backend.

[0039] In principle, the basic certificate chain model described in 16.4 of [1] can be reused as follows:

[0040] —> Certification / Verification

[0041] => Trust

[0042] Vehicle OEM CA => Equipment OEM CA

[0043] Device OEM CA => Instance CA Certificate

[0044] Vehicle OEM CA Certificate -> Device OEM CA Certificate -> Instance CA Certificate -> Digital Key Certificate

[0045] However, for example, the size of the certificates stored on the device 30 can be reduced to speed up transmission and / or storage requirements (e.g., using a minimal dedicated TLV format). For example, the device does not necessarily need to check the vehicle OEM certification chain. If the check is performed using a backend (e.g., a "device OEM backend" connected to the device 30 via the device's NFC reader), then this check can be performed during key deployment. In this way, a reduction in the resources required on the smart token 30 (e.g., storage capacity) can be achieved by outsourcing the verification of the vehicle certificate chain, for example, at the backend of the vehicle OEM. Therefore, the certificate chain known from [1] does not have to be stored entirely on the device 30. The device 30 OEM CA certificate can be verified at the backend. Only the friend digital key certificate (e.g., if there is an association between the device 30 and the owner of the device 30) or the friend digital key certificate and the instance certificate authority certificate (if there is now an association between the user and the device 30) must be transmitted by the device 30 to the device. Therefore, the certificate chain can be

[0046] (Vehicle OEM CA certificate -> Device OEM CA certificate) -> (Optional) Instance CA certificate -> Digital key certificate.

[0047] It is mandatory that only the digital key certificate has to be transmitted by and stored on the device 30 .

[0048] For example, the key-sharing certificate chain described in section 16.8 of [1] could be modified as follows:

[0049] Before issuing a digital key to a friend, the owner device verifies the authenticity of the public key created in the friend's device. The friend's device can be a different device brand than the owner's device.

[0050] Assume the vehicle has provided the owner SE with the vehicle OEM CA PK, which is securely stored in the authorized PK structure within the digital key creation data [L]. For verification, the friend device provides the instance CA certificate [E] signed by the device OEM and the friend device OEM CA certificate [F] signed by the vehicle OEM.

[0051] —>Proof / Verification

[0052] =>Trust

[0053] Owner Server / Vehicle OEM Server / Key Tracking Server / Verify:

[0054] (Vehicle OEM CA PK—>Friend Device OEM CA Certificate)—>(Optional)Friend Instance CA Certificate—>Friend Digital Key Certificate

[0055] The owner device signs the friend digital key certificate using the owner's private key. When the friend's public key is presented online by the friend device or by the vehicle OEM server, the vehicle verifies the owner signature (and the key tracking signature, if used) before accepting the friend's public key:

[0056] Owner PK—>Friend Digital Key Certificate

[0057] Vehicle OEM CA PK—>Friend Device OEM CA Certificate—>Friend Instance CA Certificate—>Friend Digital Key Certificate

[0058] Thus, if immobilizer token deployment is done via key tracking, or key creation is done using a key management server / server-based owner device, the vehicle OEM can verify trust of the instance CA certificate in a backend system that has access to the device OEM CA certificate. This can avoid the necessity of carrying each vehicle OEM certificate on the device 30, which can allow for better scalability and / or less required storage capacity after market launch. Alternatively, a central certification authority can certify the device 30.

[0059] In an example, the processing circuit system may also be configured to generate a digital key and, if the storage circuit system already contains a digital key, overwrite the digital key in the storage circuit system. For example, the processing circuit system may be configured to generate a digital key, manage qualifications and / or rights of the digital key, and, if the storage circuit system already contains a digital key, overwrite the digital key in the storage circuit system.

[0060] like Figure 1 As shown in , the corresponding interface circuit system 32 is coupled to the corresponding storage circuit system 36 at the device 30. Optionally, the interface circuit system can be coupled to the processing circuit system. In an example, the processing circuit system can be implemented using one or more processing units, one or more processing devices, any components for processing (such as processors, computers, or programmable hardware components that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include general-purpose processors, digital signal processors (DSPs), microcontrollers, etc. The processing circuit system is capable of controlling the interface circuit system 32 so that any data transmission occurring through the interface circuit system 32 and / or any interaction that the interface circuit system 32 may involve can be controlled by the processing circuit system.

[0061] In an example, the interface circuit system 32 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 32 may be wireless or wired, and it may be configured to communicate with other internal or external components, such as transmitting or receiving signals, information.

[0062] The device 30 can be integrated into a bracelet or a ring.

[0063] Further details and aspects will be mentioned in conjunction with the embodiments described below. Figure 1 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or below (e.g., Figure 2-5 ) described in one or more examples.

[0064] Figure 2 A block diagram of an example of a device 10 is shown. The device 10 is used to set a reference Figure 1 The device 10 comprises: an interface circuit system configured to transmit a signal containing information indicating a digital key protocol to the device to enable a key sharing process between the device and the device; and a processing circuit system (14) configured to generate the signal. In this way, the device can be configured to operate in accordance with a digital key protocol (e.g., CCC as described in [1]). Therefore, the battery-free device can be used as a digital key according to the CCC standard [1].

[0065] In an example, the interface circuit system can also be configured to transmit a tracking signal, which means registering the digital key to a backend (eg, OEM), and the processing circuit system can also be configured to generate the tracking signal. In this way, the backend can maintain the digital key.

[0066] For example, a communication link with a backend (e.g., a vehicle OEM server) can be used for digital key tracking and / or key tracking proof retrieval (if needed). This can be done by connecting to a vehicle OEM server through the device 10, for example, through the owner device, the device OEM server. For example, a digital key stored on a device can be registered with the backend. In this way, the backend can be informed of the digital key on the device. Therefore, the backend can receive information about multiple registered digital keys (e.g., multiple digital keys on multiple devices that can be assigned to the same vehicle). Therefore, maintenance of the digital keys of the vehicle can be improved.

[0067] Optionally, the CCC Digital Key applet interface for key creation and certification can be reused (certificate formats may vary). Optionally, key configurations ("rights") can be fully reused and / or extended if needed, for example to support specific access rights.

[0068] In an example, the signal may also include information indicative of a digital key. In this way, the device may transmit the information needed to gain access to the vehicle.

[0069] In an example, the signal may also include information indicating that the digital key stored on the device is invalid. For example, deleting the digital key may be primarily accomplished by the vehicle using an existing key deletion process. For example, key cleanup on the device may be accomplished using an agent (e.g., device 10) via the CCC VIEW / TERMINATE ENDPOINT interface. To support this, it may be beneficial to store a list of digital keys that should be on the device in the device OEM backend and synchronize the digital keys (e.g., perform deletion when necessary) via an agent (e.g., via device 10).

[0070] In an example, the tracking signal may also include information indicating a certificate used to generate a digital key stored on the device. For example, the digital key may be made known to the vehicle. If key tracking is used, then the vehicle OEM server may be used. Otherwise, an offline key sharing process may be used through a certificate in a private mailbox.

[0071] In an example, the device is at least one of a user equipment or a smart card reader (e.g., connected to a computer). For example, the user equipment may be a communication device within the meaning of a corresponding communication standard for mobile communication, such as a mobile phone (such as a smart phone) or another type of mobile communication device (such as a smart watch, a laptop, a tablet computer, or autonomous augmented reality glasses).

[0072] like Figure 2 As shown in , the corresponding interface circuit system 12 is coupled to the corresponding processing circuit system 14 at the device 10. In the example, the processing circuit system 14 can be implemented using one or more processing units, one or more processing devices, any component for processing (such as a processor, a computer, or a programmable hardware component that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 14 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include a general-purpose processor, a digital signal processor (DSP), a microcontroller, etc. The processing circuit system 14 is capable of controlling the interface circuit system 12 so that any data transmission occurring through the interface circuit system 12 and / or any interaction that the interface circuit system 12 may involve can be controlled by the processing circuit system 14.

[0073] In an embodiment, the device 10 may include a memory and at least one processing circuitry 14 operably coupled to the memory and configured to perform the method mentioned below.

[0074] In an example, the interface circuit system 12 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 12 may be wireless or wired, and may be configured to communicate with another internal or external component, such as transmitting or receiving signals, information.

[0075] The device 10 may be a computer, a server, a processor, a control unit, a (field) programmable logic array ((F)PLA), a (field) programmable gate array ((F)PGA), a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or a system on a chip (SoC) system.

[0076] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 2 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1 ) and / or below (for example, Figure 3-5 ) described in one or more examples.

[0077] Figure 3 An example of a block diagram of applet deployment is shown. The applet deployment may be performed by a personal computer 310, an NFC reader 320 (including an NFC interface circuit system 322), and a device 330. The device 330 may include a security element 336 (or a hardware security model) and an NFC interface circuit system 332. The device may be a key card that may be integrated into a user's personal item (e.g., a bracelet, a ring).

[0078] A CCC compliant applet (following the CCC applet specification in [1]) may be deployed to the SE 336 (or hardware security model) using application protocol data unit commands during the initial device 330 production or setup process. Alternatively, a chip vendor may develop a CCC compliant NFC / Secure Element chipset with a pre-installed CCC applet compliant with [1].

[0079] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 3 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-2 ) and / or one or more of the examples described below (e.g., Figures 4-5).

[0080] Figure 4a ,4b An example of a device structure is shown. Figure 4a and Figure 4b The device structure shown in can be used to replace the device structure in [1] from Figure 2 .2 Known functional components of the equipment. Figure 4a A device structure is shown which only gives an NFC connection, for example a smart card. Figure 4b Another device architecture is shown that can be used for a key fob, for example, a key fob with BLE / UWB connectivity. For this architecture, a digital key framework needs to be implemented on the device to provide limited BLE / UWB connectivity. In addition, the device architecture shows that a direct Internet connection may not be required on the device side.

[0081] More details and aspects will be mentioned in conjunction with the embodiments described above and / or below. The example shown in FIG. 4 may include one or more optional additional features, which correspond to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-3 ) and / or below (for example, Figure 5 ) described in one or more examples.

[0082] Figure 5 An example of a method is shown. The method comprises receiving 510 a signal from a device, the signal comprising information indicative of a digital key protocol to enable a key sharing procedure between the apparatus and the device.

[0083] Further details and aspects will be mentioned in conjunction with the above embodiments. Figure 5 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1 -4) One or more examples of the description. Reference numerals

[0084] 10 Equipment

[0085] 12Interface circuit system

[0086] 14 Processing circuit system

[0087] 30 devices

[0088] 32 interface circuit system

[0089] 36 Storage Circuit System

[0090] 310 pcs

[0091] 320 NFC Reader

[0092] 322 interface circuit system

[0093] 330 devices

[0094] 332 NFC interface circuit system

[0095] 336 Safety Element

[0096] 400 Method for use in device

[0097] 410 Receive signal from device

Claims

1. A device (30) for a vehicle, comprising: an interface circuit system (32) configured to receive a signal including information indicating a digital key protocol from a device to enable a key sharing process between the apparatus and the device; as well as The storage circuit system (36) is configured to store the information.

2. The device (30) according to claim 1, wherein The interface circuit system (32) is also configured to receive the signal from the device via at least one of Bluetooth, Bluetooth Low Energy, Ultra Wideband, Wireless Local Area Network, or Near Field Communication.

3. The device (30) according to claim 1 or 2, wherein The signal includes information indicating a digital key applet to enable a key sharing process between the apparatus and the device.

4. The device (30) according to any one of the preceding claims, further comprising Processing circuitry is configured to generate a generic instance certificate authority that can be used by multiple vehicle original equipment manufacturers.

5. The device (30) according to any one of the preceding claims, wherein The signal includes information indicating that a digital key is generated during digital key sharing.

6. The device (30) according to any one of the preceding claims, wherein The interface circuit system (32) is also configured to transmit a key signing request to the device, the key signing request including a certificate including a friend digital key certificate.

7. The device (30) according to claims 3 to 6, wherein The processing circuitry is further configured to generate a digital key and, if the storage circuitry already includes a digital key, overwrite the digital key in the storage circuitry.

8. A device (10) for setting up a device according to any one of the preceding claims, comprising: an interface circuit system (12) configured to transmit a signal including information indicative of a digital key protocol to the apparatus to enable a key sharing process between the apparatus and a device; as well as A processing circuit system (14) is configured to generate the signal.

9. The device (10) according to claim 8, wherein The interface circuit system (12) is also configured to transmit a tracking signal to register the digital key to the backend; and The processing circuitry (14) is further configured to generate the tracking signal.

10. The device (10) according to any one of claims 8 or 9, wherein The signal also includes information indicative of a digital key.

11. The device (10) according to any one of claims 8 to 10, wherein The signal also includes information indicating that the digital key stored on the device is invalid.

12. The device (10) according to any one of claims 9 to 11, wherein The tracking signal also includes information indicative of a certificate used to generate a digital key stored on the device.

13. The device (10) according to any one of claims 8 to 12, wherein The device is at least one of user equipment or a smart card reader.

14. A method (400) for an apparatus, comprising: A signal including information indicative of a digital key protocol is received ( 410 ) from a device to enable a key sharing procedure between the apparatus and the device.

15. A computer program having a program code for carrying out the method (100) according to claim 14 when the computer program is executed on a computer, a processor or a programmable hardware component.

Images