Method for generating a digital vehicle record, computer program, device and vehicle

Abstract

Exemplary embodiments of the present invention provide a method 100 for use by a user terminal device to generate a digital vehicle record. The method 100 comprises generating 110 signature data indicative of a request for the digital vehicle record. Furthermore, the method 100 comprises signing 120 the signature data with a private key of the user terminal device and sending 130 the signed signature data to a communication device. The signed signature data is sent to trigger the signing of vehicle record data based on the signature data. The method 100 further comprises receiving 140 from the communication device signed vehicle record data indicative of the digital vehicle record and the signature data. The signed vehicle record data is signed with a private key of the communication device.

Description

[0001] Embodiments of the present invention relate to methods for generating a digital vehicle certificate, a computer program, a device and a vehicle, in particular but not exclusively to a concept for receiving vehicle certificate data indicative of a digital vehicle certificate based on generated signature data.

[0002] Currently, the vehicle registration document and vehicle title serve as proof of ownership of a vehicle. Both documents are analog documents and are usually issued by a motor vehicle registration office. Obtaining these documents can be cumbersome and / or involve additional costs for a vehicle buyer.

[0003] There is therefore a need to provide a method for generating a digital vehicle registration document. The method, device, computer program, and vehicle according to the independent claims address this need.

[0004] Embodiments are based on the core idea that a method for generating a digital vehicle certificate can be implemented based on signature data. This allows a user terminal to trigger the issuance of a digital vehicle certificate. Furthermore, the digital vehicle certificate can be created by a communications device based on the signature data. For this purpose, in particular, a private key of the user terminal and a private key of the communications device can be modified. By using the private keys of the user terminal and the combination device, a digital vehicle certificate that is only valid for one user terminal can be issued.

[0005] Embodiments relate to a method for performing a digital vehicle verification by a user terminal. The method comprises generating signature data indicative of a request for the digital vehicle verification. The method further comprises signing the signature data with a private key of the user terminal and sending the signed signature data to a communication device. The signed signature data is sent to trigger a signing of vehicle verification data based on the signature data. The method further comprises receiving, from the communication device, signed vehicle verification data indicative of the digital vehicle verification and the signature data. The signed vehicle verification data is signed with a private key of the communication device.By signing the signature data with the private key of the user terminal and signing the vehicle registration data with the private key of the communication device, the authenticity and / or integrity of the digital vehicle registration can be ensured. Sending the signed signature data can trigger the user terminal to receive the signed vehicle registration data. For example, by sending the signed signature data, the user terminal can trigger the communication device to generate and sign the vehicle registration data. This allows the digital vehicle registration to be created as needed.

[0006] In one embodiment, the method may further comprise receiving request data indicative of a request for a transmission of the digital vehicle certificate. The request data is received by a further user terminal. The method may further comprise generating transmission data based on the signed vehicle certificate data and the request data. The transmission data is indicative of a transmission of the digital vehicle certificate. The method may further comprise signing the transmission data and sending the transmission data to the further user terminal. By sending the transmission data, the further user terminal can receive a digital vehicle certificate for a vehicle from the user terminal. In particular, the old digital vehicle certificate of the user terminal can thereby become invalid. The transmission data can therefore be used to document a change of ownership of the vehicle.For example, a new owner of the vehicle can receive the transmission data on another user device. Using the transmission data, the user of the additional user device can then prove ownership based on the digital vehicle registration certificate.

[0007] In one embodiment, the method may further comprise sending handover data indicative of the transmission data to a backend. The handover data can be used to inform a backend about a change in the ownership of a vehicle. This allows the backend to update information about the owner of the vehicle.

[0008] In one embodiment, sending and receiving can occur via a local communication connection. This can simplify the sale of the vehicle. In particular, a sale of a vehicle can be verified by sending the transmission data via a local communication connection.

[0009] Embodiments relate to a method for generating a digital vehicle certificate by a communication device. The method comprises receiving signed signature data indicative of a request for the digital vehicle certificate. The signed signature data is received by a user terminal. The signed signature data is signed with a private key of the user terminal. The method further comprises generating vehicle certificate data indicative of the digital vehicle certificate based on the signature data. The method further comprises signing the vehicle certificate data with a private key of the communication device and sending the signed vehicle certificate data. The signed vehicle certificate data is sent to the user terminal. By generating the vehicle certificate data, a digital vehicle certificate can be created.The digital vehicle certificate is generated based on the signature data. This allows the digital vehicle certificate to be generated for a user device. For example, the digital vehicle certificate is linked to the user device or the user device's private key. This ensures the authenticity and / or integrity of the digital vehicle certificate. By sending the signed vehicle certificate data to the user device, a user of the user device can receive the information required to prove ownership of the vehicle. An analog document for verification can be omitted.

[0010] In one embodiment, the vehicle verification data may be indicative of at least one of the identity of an owner of the vehicle and the registration of the vehicle. Thus, relevant information regarding the vehicle may be included in the vehicle verification data.

[0011] In one embodiment, the method may further comprise sending generation data indicative of the generation of the vehicle verification data to a backend. This allows a backend to be informed about the vehicle verification data or the digital vehicle verification. For example, a backend may store the information about the vehicle verification data. The backend may, in particular, be used to replace a lost digital vehicle verification. The backend may, for example, be a certificate authority (CA), which is responsible for creating a new digital vehicle verification if the digital vehicle verification is lost.

[0012] In one embodiment, the method may further comprise receiving registration data indicative of a registration of the vehicle verification data by the backend. The registration data is received by the backend. The backend can thereby inform the communication device about a successful registration of the digital vehicle verification.

[0013] Embodiments also provide a computer program for performing any of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component.

[0014] Another embodiment is a device for generating a digital vehicle identification document. The device comprises an interface for communication with a user terminal or a communication device and a data processing circuit configured to carry out at least one of the methods described herein.

[0015] Exemplary embodiments are explained in more detail below with reference to the accompanying figures. They show: Fig. 1 shows a schematic representation of a method for generating a digital vehicle certificate; Fig. 2 shows a schematic representation of another method for generating a digital vehicle certificate; and Fig. 3 shows a block diagram of an embodiment of a device for generating a digital vehicle certificate.

[0016] Various embodiments will now be described in more detail with reference to the accompanying drawings, in which some embodiments are illustrated. In the figures, the thickness dimensions of lines, layers, and / or regions may be exaggerated for clarity.

[0017] Fig. Figure 1 shows a schematic representation of a method 100 for generating a digital vehicle certificate. The method 100 can be performed by a user terminal. The user terminal can include a data processing circuit for performing processes (e.g., for generating signature data) and a communication interface (e.g., for sending the signed signature data).

[0018] The method 100 includes generating 110 signature data indicative of a request for the digital vehicle certificate. The generation 110 of the signature data can be triggered by a user of the user terminal. For example, a user of the user terminal may wish to purchase a vehicle. To complete the purchase or to obtain proof of ownership of the vehicle, the signature data can be generated 110 by the user terminal. The signature data can thus be used, in particular, to trigger the generation of a digital vehicle certificate.

[0019] Furthermore, the method 100 comprises signing 120 the signature data with a private key of the user terminal. The private key can in particular be a private key of a digital vehicle key. High security standards can apply to a digital vehicle key. A private key in general, for example also a private key of the digital vehicle key, is stored in a secure element of the user terminal. This can increase security. Optionally, by using a private key of a digital vehicle key, an existing infrastructure for the digital vehicle key can be used. The digital vehicle key can in particular be a digital vehicle key as defined by the Car Connectivity Consortium (CCC), for example as defined in Digital Key Release 3.0 [1].

[0020] By signing 120, the integrity and / or authenticity of the identification data can be ensured. This can, for example, generate a digital vehicle certificate for the user terminal. The private key (for example, of the digital vehicle key) of the user terminal can be stored in a security element of the user terminal. A security element can be used to securely store confidential information and to protect against unauthorized access to sensitive data. The security element can be a storage device. The security element can be physically separated from other components of the communication device. The security element can have strict security measures to protect the integrity of the stored data. This can achieve an increased security standard.By using a private key of a digital vehicle key, a CCC infrastructure can be accessed.

[0021] Furthermore, the method 100 includes sending 130 the signed signature data to a communication device. The signed signature data can be sent to trigger the generation and signing of vehicle verification data based on the signature data.

[0022] Furthermore, the method 100 comprises receiving 140, from the communication device, signed vehicle verification data indicative of the digital vehicle verification and the signature data. The signed vehicle verification data is signed with a private key of the communication device. By signing the signature data with the private key of the user terminal and signing the vehicle verification data with the private key of the communication device, the authenticity and / or integrity of the digital vehicle verification can be ensured. By sending 130 the signed signature data, receipt of the signed vehicle verification data by the user terminal can be triggered. For example, by sending 130 the signed signature data, the user terminal can trigger the generation and signing of vehicle verification data by the communication device.This means that the digital vehicle certificate can be created when needed.

[0023] Optionally, method 100 may include storing the signed vehicle verification data. The signed vehicle verification data may be stored in a storage unit of the user terminal. In particular, the signed vehicle verification data may be stored in a security element of the user terminal. For example, the signed vehicle verification data may be stored in the same security element as the user terminal's private key. This may increase the security of the signed vehicle verification data or the digital vehicle verification.

[0024] In one embodiment, the method may further comprise receiving request data indicative of a request for a transmission of the digital vehicle certificate. The request data is received by a further user terminal. The method may further comprise generating transmission data based on the signed vehicle certificate data and the request data. The transmission data is indicative of a transmission of the digital vehicle certificate. The method may further comprise signing the transmission data and sending the transmission data to the further user terminal. By sending the transmission data, the further user terminal can receive a digital vehicle certificate for a vehicle from the user terminal. In particular, the old digital vehicle certificate of the user terminal can thereby become invalid. The transmission data can therefore be used to document a change of ownership of the vehicle.For example, a new owner of the vehicle can receive the transmission data on another user device. Using the transmission data, the user of the additional user device can then prove ownership based on the new digital vehicle registration document.

[0025] For example, the signed vehicle identification data can include a function for deleting or invalidating the signed vehicle identification data during transmission. The signed vehicle identification data is stored in the security element of the user terminal. Generating the transmission data can then, in particular, include executing the deletion or invalidation function. This function can issue a deletion confirmation, which is signed using the private key of the user terminal. If this signature is performed in the security element, the (old) vehicle identification data can be simultaneously either deleted or invalidated (self-revised). The proof that the (old vehicle identification data) has been invalidated or deleted depends on the integrity of the function in the security element of the user terminal.

[0026] For example, the old digital vehicle registration document can be deleted from the user terminal. The user terminal can confirm the deletion of the old digital vehicle registration document, for example, by sending information about the deletion to the other user terminal and / or a server. The information confirming the deletion can, in particular, be cryptographically confirmed information. The information confirming the deletion can, for example, be confirmed by the security element in which the user terminal's private key is stored.

[0027] In one embodiment, the method may further comprise sending transfer data indicative of the transmission data to a backend. The transfer data may comprise the transmission data. Alternatively, the transfer data may merely comprise information about a new owner of the vehicle. Using the transfer data, information about a change of ownership may be sent to the backend. The backend may then register the new owner of the vehicle. Furthermore, a registration for the old owner may be deleted. Alternatively, a registration may be changed to the new owner of the vehicle.

[0028] In one embodiment, sending and receiving can occur via a local communication connection. For example, a user can purchase a vehicle at a car dealership. To process the vehicle purchase, the user can perform method 100 using their user terminal. Method 100 can be performed in conjunction with a computer at the car dealership. The car dealership's computer can, in particular, create the digital vehicle registration document and send it to the user terminal. Communication between the computer and the user terminal can be simplified via a local communication connection. A local communication connection can be a wireless local area network and / or a Bluetooth communication connection.

[0029] For example, upon vehicle handover or upon receipt of a vehicle, a dealer can issue a digital vehicle certificate, such as a digital vehicle registration document, to the legitimate purchaser of the vehicle. For the purpose of issuing the digital vehicle certificate, the user terminal can generate 110 signature data. For example, generating 110 the signature data can include generating a key pair in a security element of the user terminal. The key pair generated by the user terminal can be intended for signature by the dealer. This allows a digital vehicle certificate to be created for a specific user terminal.

[0030] Based on the signature data, for example, the signed key pair, the dealer can issue a digital certificate, for example, using a communication device. The digital certificate can be used as digital vehicle identification. The digital certificate or a certificate chain can include, in particular, information about the vehicle (for example, a vehicle identifier) ​​and other metadata, for example, regarding the vehicle owner.

[0031] The digital certificate can be created using a root certificate from a root CA, such as a vehicle manufacturer. The root CA's root certificate is typically pre-installed or manually inserted into the trust stores of operating systems, web browsers, or other applications. This means that all certificates signed by the root CA are accepted as trustworthy, as they form a chain of trust. This chain of trust begins with the root certificate and extends through intermediate CAs to the end-user certificates. The dealer can therefore create vehicle verification data, which may include an end-user certificate.

[0032] Optionally, the issuance of a digital vehicle registration certificate can be registered on a central server. This allows a customer to be issued with or regenerated proof of vehicle ownership if the user device is lost. In particular, the central server or a backend can be used to generate a digital vehicle registration certificate for a replacement user device.

[0033] Furthermore, the digital vehicle registration document can also be a digital vehicle registration document. An analog vehicle registration document is usually issued by a motor insurance company or a government agency. The digital vehicle registration document in the form of a digital vehicle registration document could therefore be issued, for example, by a motor insurance company or a motor vehicle registration office.

[0034] If the vehicle is sold to another user, the digital vehicle registration document can be transferred as proof of ownership. For example, the previous owner can create a signed confirmation that serves as proof for a buyer of the vehicle. The signed confirmation can be part of the transfer data. Optionally, this signed confirmation can be verified by the central server. The verification can be based, for example, on the handover data.

[0035] The new owner of the vehicle or information about the new owner of the vehicle can then be stored in a database by the central server or a backend.

[0036] The digital vehicle registration document can be a counterpart to the analog vehicle registration document and / or vehicle title. The digital vehicle registration document can replace an analog vehicle registration document and / or vehicle title. Security can be ensured by storing the digital vehicle registration document in a security element of the user's terminal. Furthermore, the integrity and authenticity of the digital vehicle registration document can be guaranteed by a cryptographic signature of the private key of the communication device, for example, a communication device of a vehicle dealer, a public authority, and / or an insurance company.

[0037] Furthermore, the digital vehicle registration document can also be used for inspections by authorities, insurance companies, and / or the police. In particular, the digital vehicle registration document can be linked to the user's device's private key. Verification can then also be provided via a signature using the user's device's private key.

[0038] The user terminal can generally be a device capable of wireless communication. In particular, the user terminal can be a mobile user terminal, e.g., a user terminal suitable for being carried by a user. The user terminal can be, e.g., a user terminal (UT) or user equipment (UE) within the meaning of the respective communication standards used for mobile communication. The user terminal can be, for example, a mobile phone, such as a smartphone, or another type of mobile communication device, such as a smartwatch, a laptop, a tablet computer, autonomous augmented reality glasses, etc.

[0039] Further details and aspects are mentioned in connection with the embodiments described below. Fig. 1 may comprise one or more optional additional features corresponding to one or more aspects related to the proposed concept or one or more embodiments described below (e.g. Fig. 2 - 3) were mentioned.

[0040] Fig. Figure 2 shows a schematic representation of another method 200 for generating a digital vehicle verification. The method 200 can be carried out by a communication device. The communication device can include a data processing circuit for performing processes (e.g., for generating vehicle verification data) and a communication interface (e.g., for receiving the signed signature data).

[0041] The method 200 comprises receiving 200 signed signature data indicative of a request for the digital vehicle verification. The signed signature data is received by a user terminal. The signed signature data is signed with a private key of the user terminal. Furthermore, the method 200 comprises generating 210 vehicle verification data indicative of the digital vehicle verification based on the signature data. Furthermore, the method 200 comprises signing 220 the vehicle verification data with a private key of the communication device and sending 230 the signed vehicle verification data. The signed vehicle verification data is sent to a user terminal. The method 200 can be used together with the method described with reference to Fig. 1. The method 200 can be carried out in the context of the transmitter and receiver with the Fig. 1 described procedures.

[0042] The communication device can generate 210 a digital vehicle certificate for a user terminal. In particular, the generation 210 of the digital vehicle certificate can be triggered by receiving the signed signature data. For example, the process of issuing a digital vehicle certificate can be started by the user terminal.

[0043] In one embodiment, the vehicle verification data can be indicative of at least one of the identity of the vehicle owner and the vehicle registration. In particular, this information can be included in the metadata of a certificate or a certificate chain. The vehicle verification data can thus include a certificate or a certificate chain. Relevant information can thus be stored within the certificate or certificate chain. This increases the security of the stored information.

[0044] In one embodiment, method 200 may further comprise sending generation data indicative of the generation of the vehicle verification data to a backend. The generation data can be used to inform a backend about the generated 210 digital vehicle verification. The backend can then, for example, register the digital vehicle verification. In particular, the backend can be used to issue a (new) digital vehicle verification in the event of loss of the user terminal.

[0045] In one embodiment, method 200 may further include receiving registration data indicative of a registration of the vehicle verification data by the backend. The registration data can be used to notify the communication device of a completed registration. For example, as part of fleet management, the communication device can send a plurality of digital vehicle verifications to the backend for a vehicle fleet. The digital vehicle verification can eliminate the need to digitize the wanted vehicle verification in order to perform a registration. In particular, the digital vehicle verification can simplify the registration of a vehicle.

[0046] The communication device can generally be a device capable of wireless communication. The communication device can communicate with a backend, e.g., a base station, a user terminal in a mobile communication system. For example, the communication device can communicate within / via a mobile communication system. The mobile communication system can comprise a plurality of transmission points and / or base stations capable of transmitting radio signals to the control unit. The communication device can communicate with the user terminal in a local communication system. The communication device can be part of a computer, a laptop, or a tablet.

[0047] Further details and aspects are mentioned in connection with the embodiments described below and / or above. Fig. 2 may comprise one or more optional additional features corresponding to one or more aspects related to the proposed concept or one or more of the above (e.g. Fig. 1) and / or embodiments described below (e.g. Fig. 3) were mentioned.

[0048] Fig. Figure 3 shows a block diagram of an embodiment of a device for generating a digital vehicle certificate. The device 30 comprises an interface 32 for communication with a user terminal (for example, for carrying out the method relating to Fig. 2) or with a communication device (for example for carrying out the method described with reference to Fig. 1). The device 30 further comprises a data processing circuit 34 which is designed to carry out at least one of the methods described herein, for example the method which is described with reference to Fig. 1 for the user terminal or with reference to Fig. 2 for the communication device.

[0049] The Fig. The interface 32 shown in Figure 3 can, for example, correspond to one or more inputs and / or one or more outputs for receiving and / or transmitting information, for example in digital bit values, based on a code, within a module, between modules, or between modules of different entities. The interface 32 can, for example, be configured to communicate with other network components via a (radio) network or a local area network.

[0050] In exemplary embodiments, the data processing circuit 34 can correspond to any controller or processor or a programmable hardware component. For example, the data processing circuit 34 can also be implemented as software programmed for a corresponding hardware component. In this respect, the data processing circuit 34 can be implemented as programmable hardware with appropriately adapted software. Any processors, such as digital signal processors (DSPs), can be used. Exemplary embodiments are not limited to a specific type of processor. Any processor or even multiple processors are conceivable for implementing the data processing circuit 34.

[0051] As in Fig. 3, the interface 32 may be coupled to the respective data processing circuitry 34 of the device 30. In examples, the device 30 may be implemented by one or more processing units, one or more processing devices, any means of processing, such as a processor, a computer, or a programmable hardware component operable with appropriately adapted software. Likewise, the described functions of the data processing circuitry 34 may also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may be a general-purpose processor, a digital signal processor (DSP), a microcontroller, etc.The data processing circuit 34 may be capable of controlling the interface 32 such that any data transfer that occurs over the interface 32 and / or any interaction that the interface 32 may be involved in can be controlled by the data processing circuit 34.

[0052] In one embodiment, the device 30 may include a memory and at least one data processing circuit 34 operatively coupled to the memory and configured to perform one of the methods described above.

[0053] In examples, interface 32 may correspond to any means for obtaining, receiving, transmitting, or providing analog or digital signals or information, e.g., any terminal, contact, pin, register, input terminal, output terminal, conductor, trace, etc., that enables the provision or receipt of a signal or information. Interface 32 may be wireless or wired and may be configured to communicate with other internal or external components, e.g., to send or receive signals or information.

[0054] Further details and aspects are mentioned in connection with the embodiments described above. Fig. 3 may comprise one or more optional additional features corresponding to one or more aspects related to the proposed concept or one or more of the above (e.g. Fig. 1 - 3) described embodiments were mentioned.

[0055] Further embodiments are computer programs for carrying out one of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component. Depending on specific implementation requirements, embodiments of the invention can be implemented in hardware or in software. The implementation can be carried out using a digital storage medium, for example a floppy disk, a DVD, a Blu-ray disc, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, a hard disk, or another magnetic or optical storage device on which electronically readable control signals are stored that can interact or interact with a programmable hardware component in such a way that the respective method is carried out.

[0056] A programmable hardware component can be formed by a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated circuit (IC = Integrated Circuit), a single-chip system (SOC = System on Chip), a programmable logic element or a field-programmable gate array with a microprocessor (FPGA = Field Programmable Gate Array).

[0057] The digital storage medium can therefore be machine- or computer-readable. Some embodiments thus comprise a data carrier having electronically readable control signals capable of interacting with a programmable computer system or a programmable hardware component such that one of the methods described herein is performed. One embodiment is thus a data carrier (or a digital storage medium or a computer-readable medium) on which the program for performing one of the methods described herein is recorded.

[0058] In general, embodiments of the present invention can be implemented as a program, firmware, computer program, or computer program product with program code or data, wherein the program code or data is effective to perform one of the methods when the program runs on a processor or a programmable hardware component. The program code or data can also be stored, for example, on a machine-readable medium or data carrier. The program code or data can be present, among other things, as source code, machine code, or bytecode, as well as other intermediate code. List of reference symbols 30 Device 32 interface 34 Data processing circuit 100 procedures for generating a digital vehicle certificate 110 Generating signature data 120 Signing the signature data 130 Sending the signed signature data 140 Receiving signed vehicle verification data 200 procedures for generating a digital vehicle certificate 210 Receiving signed signature data 220 Generating vehicle verification data 230 Signing the vehicle verification data 240 Sending the signed vehicle verification data

Claims

[1] A method (100) for performing by a user terminal for generating a digital vehicle record, comprising: Generating (110) signature data indicative of a request for the digital vehicle certificate; Signing (120) the signature data with a private key of the user terminal; Sending (130) the signed signature data to a communication device for triggering a signing of vehicle verification data based on the signature data; and Receiving (140), from the communication device, signed vehicle verification data indicative of the digital vehicle verification and the signing data, wherein the signed vehicle verification data is signed with a private key of the communication device. [2] The method (100) of claim 1 further comprising: Receiving, from another user terminal, request data indicative of a request for transmission of the digital vehicle record; Generating transmission data based on the signed vehicle verification data and the request data, the transmission data being indicative of a transmission of the digital vehicle verification; Signing the transmission data; and Sending the transmission data to the other user terminal. [3] The method (100) of any preceding claim, further comprising sending, to a backend, handover data indicative of the transmission data. [4] The method (100) according to any one of the preceding claims, wherein the sending and receiving are performed via a local communication connection. [5] A method (200) for performing by a communication device for generating a digital vehicle certificate, comprising: Receiving (210), from a user terminal, signed signature data indicative of a request for the digital vehicle certificate, the signed signature data being signed with a private key of the user terminal; Generating (220) vehicle verification data indicative of the digital vehicle verification based on the signature data; Signing (230) the vehicle verification data with a private key of the communication device; and Sending (240) the signed vehicle verification data to the user terminal. [6] The method (200) of claim 5, wherein the vehicle verification data is indicative of at least one of an identity of an owner of the vehicle and a registration of the vehicle. [7] The method (200) of any one of claims 5 or 6, further comprising sending, to a backend, generation data indicative of the generation of the vehicle verification data. [8] The method (200) of claim 7, further comprising receiving, from the backend, registration data indicative of registration of the vehicle verification data by the backend. [9] A computer program for carrying out one of the methods (100; 200) according to one of the preceding claims, when the computer program runs on a computer, a processor, or a programmable hardware component. [10] A device (30) for generating a digital vehicle certificate, comprising: an interface (32) for communication with a user terminal or a communication device; and a data processing circuit (34) configured to carry out at least one of the methods (100) according to any one of claims 1-8.

Images