Method for receiving signed information, computer program, device and vehicle

Abstract

Exemplary embodiments of the present invention provide a method 100 for carrying out by a user terminal device to receive signed information from a vehicle. The method 100 comprises sending 110 request data indicative of a request from the vehicle for information signed with a private key of the vehicle. The request data is sent to a control unit of the vehicle. Furthermore, the method 100 comprises receiving 120 the signed information from the control unit of the vehicle.

Description

[0001] Embodiments of the present invention relate to methods for receiving signed information from a vehicle, a computer program, a device and a vehicle, in particular but not exclusively to a concept for receiving information signed with a private key of the vehicle.

[0002] When a rental vehicle is returned, a check of the rental vehicle must usually be carried out upon transfer of risk from the user to the owner, for example, a rental company. This check is performed to ensure the vehicle's condition, for example, that all windows are closed, that the rental vehicle has been parked in the correct location, and that the rental vehicle is locked. This check can be performed by a person or by the vehicle itself, if it has a communication connection to a backend. A check by a person leads to increased costs, while a check via a communication connection requires infrastructure, which in turn can lead to increased costs.

[0003] There is therefore a need to provide an improved method for receiving signed information from a vehicle. 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 receiving signed information from a vehicle can be implemented based on a request from a user terminal. The signed information can be signed using a private key of the vehicle. This ensures the integrity of the signed information.

[0005] Embodiments relate to a method for receiving signed information from a vehicle by a user terminal. The method comprises sending request data indicative of a request from the vehicle for information signed with a private key of the vehicle. The request data is sent to a control device of the vehicle. The method further comprises receiving the signed information from the control device of the vehicle. By sending the request data, the user terminal can request signed information from the vehicle, for example a mileage of the vehicle and / or information about a status of the vehicle, in particular at a point in time (for example during a transfer of risk in a rental vehicle). Based on the request data, the user terminal can then receive signed information from the control device of the vehicle.By signing the signed information with a private key of the vehicle, the reliability of the integrity of the signed information can be increased.

[0006] In one embodiment, the signed information may be information about the use of the vehicle. For example, the signed information may include information about the time the vehicle was parked. Furthermore, the signed information may include information about the duration of use. This allows, for example, a calculation of the costs for renting the vehicle based on the signed information.

[0007] In one embodiment, the signed information may be information about a status of the vehicle. For example, the signed information may include information about the vehicle's mileage. This allows a user of the user terminal to receive authenticated information about the vehicle.

[0008] In one embodiment, the method may further comprise receiving trigger data indicative of a request for the signed information. Sending may comprise sending the request data based on the trigger data. For example, a request for the signed information may be triggered by a backend, an app, and / or the vehicle's control device. Thus, receiving the signed information at the user terminal may be triggered by an event, such as the expiration of a rental period.

[0009] In one embodiment, the method may further comprise sending the signed information to a backend. By sending the signed information, the backend can obtain required information about the vehicle. For example, the backend can confirm and / or verify the end of the vehicle's rental period.

[0010] In one embodiment, obtaining may include receiving information about required signed information. The information about the required signed information is received by the backend. This allows a backend to request the required information from the user terminal, for example, to confirm and / or verify the end of the vehicle rental.

[0011] Embodiments include a method for receiving signed information from a vehicle at a user terminal by a control device of a vehicle. The method includes receiving, from a communication device, request data indicative of a request for the information signed with a private key of the vehicle. Furthermore, the method includes generating the information and signing the information with the private key of the vehicle. The method further includes sending the signed information to the user terminal. This allows the control unit to provide signed information to the user terminal.

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

[0013] Another embodiment is a device for receiving signed information. The device comprises an interface for communication with a control device of a vehicle or a user terminal and a data processing circuit configured to perform at least one of the methods described herein. Embodiments further provide a vehicle with a device as described herein.

[0014] 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 receiving signed information; Fig. Figure 2 shows a schematic representation of another method for receiving signed information at a user terminal; and Fig. 3 shows a block diagram of an embodiment of a device for receiving signed information.

[0015] 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.

[0016] Fig. Figure 1 shows a schematic representation of a method 100 for receiving signed information. The method 100, for implementation by a user terminal, includes sending 110 request data indicative of a request from the vehicle for the information signed with a private key of the vehicle.

[0017] The private key can be used to decrypt encrypted data and / or generate a digital signature. For example, the vehicle can use the private key to create a digital signature that authenticates a message or piece of information and / or guarantees the integrity of the message or information (e.g., the requested information). Only a vehicle in which the private key is stored can create this digital signature, which ensures that the message or information actually originates from the vehicle, e.g., a control device of the vehicle. The digital signature of the information signed with the private key can be verified using a public key that forms a key pair with the private key. For example, the public key can be stored in a backend. This allows the backend to verify whether the signed information came from the vehicle orthe vehicle's control device was signed.

[0018] Optionally, the private key can be associated with a digital vehicle key. The digital vehicle key can, in particular, be a digital key as defined by the Car Connectivity Consortium (CCC), for example, as defined in Digital Key Release 3.0. For example, the private key can be a private key of a digital vehicle key. The vehicle's digital vehicle key can be assigned to a digital vehicle key of a user terminal. In this case, a user of the user terminal can be assigned to the digital vehicle key (for example, via a backend). By assigning the vehicle's private key to a user's digital vehicle key, the signed information can be assigned to a user or the user terminal. This can prevent misuse by third parties.In particular, the signed information can only be issued to the user of the user terminal or the user terminal.

[0019] Furthermore, security can be increased by using a digital vehicle key. A private key of a digital vehicle key is typically stored in a secure element. For example, a central control unit of the vehicle can include the security element. By storing it in a security element, the integrity of the method 100 can be increased. In particular, the use of a private key of a digital vehicle key allows access to the existing infrastructure of the CCC.

[0020] Security can be increased by using a private key for a digital vehicle key. Typically, there are increased security requirements for digital vehicle keys. These requirements are specified by the CCC. For example, the private key of the digital vehicle key is stored in a security element of the vehicle, such as the vehicle's control unit. A vehicle security element is a special storage device used to securely store confidential information and protect against unauthorized access to sensitive data. These storage devices are usually physically separated from other components of the vehicle or the control unit and have strict security measures to protect the integrity and / or confidentiality of the stored data. This can improve the security of authentication.

[0021] Optionally or alternatively, the signed information can also include an assignment to a user. For example, the signed information can include payload data that is communicated in data packets during communication between the vehicle's control unit and the user terminal. The payload can include, for example, information about the user, such as a contractual partner for the vehicle rental. This allows the signed information to be assigned to a user of the vehicle.

[0022] The request data is sent to a control device of the vehicle. The control device can generally be a device capable of wireless communication. The control device can communicate with a backend, e.g., a base station, in a mobile communication system. For example, the control device can communicate in / via a mobile communication system. The mobile communication system can include a plurality of transmission points and / or base stations capable of transmitting radio signals with the communication device.

[0023] The sending 110 of the request data can be triggered, for example, by a user input. The user can click on "End rental" in an app. The app can be executed on the user terminal and / or a control unit of the vehicle. In the method 100, the user input can advantageously be made on the user terminal. Based on the user input, the request data can be sent 110 to the control unit of the vehicle. This allows the control unit of the vehicle to receive the necessary conditions to end a rental. The control unit of the vehicle can check the conditions. Based on the verification of the conditions, the control unit of the vehicle can issue a cryptographically verifiable attestation to the phone, the signed information (see also Fig. 2) contains.

[0024] Furthermore, the method 100 includes receiving 120 the signed information from the vehicle's control unit. This allows a user of the user terminal, for example, to verify the end of a rental, which was confirmed by the vehicle. Optionally, the signed information can be sent or forwarded to a backend.

[0025] In one embodiment, the signed information can be information about the use of the vehicle. For example, the signed information can include information about the time of unlocking and / or locking the vehicle. This allows the time of use of the vehicle by the user of the user terminal to be verified. For example, the signed information can include information about a distance traveled by the vehicle. This allows, for example, a simplified billing of mileage.

[0026] In one embodiment, the signed information may be information about a status of the vehicle. A user of the user terminal may require verified information about the vehicle. For example, the user may want to sell the vehicle or have the vehicle's value appraised, which may depend, in particular, on the vehicle's mileage. The signed information may include information about the vehicle's mileage. This allows a user to obtain verifiable data about the vehicle's mileage.

[0027] In one embodiment, method 100 may further comprise receiving trigger data indicative of a request for the signed information. Sending may comprise sending the request data based on the trigger data. The trigger data may be generated, for example, by user input as described above. Optionally or alternatively, the trigger data may be received by a backend. For example, a user may wish to terminate a vehicle rental. The backend may send trigger data indicative of information required to terminate the vehicle rental to the user terminal.

[0028] In one embodiment, obtaining may include receiving information about required signed information. The information about the required signed information may be obtained from the backend. By receiving the information about the required signed information, the user terminal may send request data 110, which may trigger creation of the required signed information by the vehicle's control device.

[0029] Optionally, method 100 may include creating request data based on the trigger data. By creating request data based on the trigger data, the request for signed information can be adapted to a current situation. For example, the user terminal may request signed information to terminate a vehicle rental.

[0030] The user terminal's request can then include information about the information required by the backend, for example. The vehicle or the vehicle's control device can create the information required by the backend and sign it using the vehicle's private key. The user terminal can receive 120 the signed information and forward it to the backend. This allows the backend to obtain the required information from the vehicle, even if the vehicle cannot establish a communication connection with the backend.

[0031] In one embodiment, method 100 may further include sending the signed information to a backend. By sending the signed information, the backend may obtain required information about the vehicle. For example, the backend may confirm and / or verify the end of the vehicle's rental.

[0032] 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, for example, be a user terminal (UT) or user equipment (UE) within the meaning of the respective communication standards used for mobile communication. The user terminal can, for example, be 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.

[0033] 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.

[0034] Fig. 2 shows a schematic representation of a further method 200 for receiving signed information at a user terminal. The method 200 for implementation by a control device (of a vehicle) comprises receiving 210, from a communication device, request data indicative of a request for the information signed with a private key of the vehicle. The method 200 further comprises generating 220 the information and signing 230 the information with the private key of the vehicle. Furthermore, the method comprises sending 240, to the user terminal, the signed information. The method 200 can be implemented by a counterpart (in the sense of transmitter and receiver) to the user terminal, which is related to Fig. 1. The control device can, for example, be a central control device of the vehicle.

[0035] As with reference to Fig. 1, the private key can be assigned to a digital vehicle key. In particular, the private key can be associated with a private key of a digital vehicle key of the user terminal. This allows a direct connection between the signed information and the user terminal or a user of the user terminal to be established by using the private key. Thus, the control device can create signed information that is uniquely assigned to a user or a user terminal. This can prevent misuse by third parties.

[0036] For example, a customer can use a digital vehicle key from their user device to rent a vehicle. After use, the customer clicks "End Rental" in the rental company's app. Clicking this button in the rental company's app can create trigger data. The rental company's app can be run on the user device and / or a control unit of the vehicle.

[0037] The user terminal can receive or create the trigger data. In response to receiving / creating the trigger data, the user terminal can create request data based on the trigger data. The created request data can then be sent to the vehicle's control unit. The request data can be sent via a local communication connection, for example, via a Bluetooth Low Energy and / or wireless local area network communication connection.

[0038] The vehicle's control unit can receive the request data 210. Based on the request data, the vehicle's control unit can perform a check. For example, the request data includes information about required information from the vehicle (e.g., whether all windows are closed, whether the rental vehicle has been parked in the correct location, or whether the rental vehicle is locked). The vehicle's control unit can perform a prescribed check to generate 220 the (required) information. The vehicle's control unit can generate 220 the required information.

[0039] After generating 220 the information, the vehicle's control device can sign 230 the information with the private key. The signed information can then be sent 240 to the user terminal.

[0040] The user device can then send an end-of-rental request to a backend of the rental company. The end-of-rental request can include the signed information. The backend can verify the signed information using the public key. Alternatively, the backend can establish a communication connection to a backend of an original equipment manufacturer (OEM) to have the OEM backend verify the signed information. Based on the verification of the signed information, a rental of the vehicle can then be terminated by the backend. In particular, no communication connection between the vehicle and the backend is required for this. This can simplify the termination of a rental of a rental vehicle.

[0041] Optionally or alternatively, the signed information can include an assignment to a user or a user terminal. For example, the generated 220 information can include payload data that is indicative of a user or a user terminal. Signing 230 can prevent changes to the payload data. By decrypting the signed information, the payload data can then be accessed, and a user or a user terminal for whom the signed information was created can be determined.

[0042] 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.

[0043] Fig. 3 shows a block diagram of an embodiment of a device 30 for controlling a diagnostic session of a vehicle 40. The device may comprise a user terminal as described with reference to Fig. 1 or a control unit as described with reference to Fig. 2. The device 30 comprises an interface 32 for communication with a user terminal (as described with reference to Fig. 2) or with a control device (as 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 control device. Further embodiments include a vehicle 40 with a device 30.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] In at least some embodiments, the vehicle 40 may, for example, correspond to a land vehicle, a watercraft, an aircraft, a rail vehicle, a road vehicle, a car, a bus, a motorcycle, an off-road vehicle, a motor vehicle, or a truck. The device 30 may, for example, be a part of or a control unit of the vehicle 40.

[0050] 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 - 2) described embodiments were mentioned.

[0051] 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.

[0052] 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).

[0053] 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.

[0054] 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.

[0055] The above-described embodiments are merely illustrative of the principles of the present invention. It is understood that modifications and variations of the arrangements and details described herein will be apparent to others skilled in the art. Therefore, it is intended that the invention be limited only by the scope of the following claims and not by the specific details presented in the description and explanation of the embodiments herein. List of reference symbols 30 Device 32 interface 34 Data processing circuit 40 vehicles 100 Method for performing by a user terminal for receiving signed information from a vehicle 110 Sending request data 120 Receiving the signed information 200 for implementation by a control device of a vehicle for receiving signed information from a vehicle at a user terminal 210 Receiving request data 220 Generating information 230 Signing the information 240 Sending the signed information

Claims

[1] A method (100) for receiving signed information from a vehicle by a user terminal, comprising: Sending (110), to a control device of the vehicle, request data indicative of a request from the vehicle for the information signed with a private key of the vehicle; and Receiving (120), from the control device of the vehicle, the signed information. [2] The method (100) of claim 1, wherein the signed information is information about a use of the vehicle. [3] The method (100) according to any one of the preceding claims, wherein the signed information is information about a status of the vehicle. [4] The method (100) of any preceding claim, further comprising obtaining trigger data indicative of a request for the signed information, and wherein sending comprises sending the request data based on the trigger data. [5] The method (100) of any preceding claim, further comprising sending, to a backend, the signed information. [6] The method (100) of claim 4 and 5, wherein obtaining comprises receiving, from the backend, information about required signed information. [7] A method (200) for performing by a control device of a vehicle for receiving signed information from a vehicle at a user terminal, comprising: Receiving (210), from a communication device, request data indicative of a request for the information signed with a private key of the vehicle; generating (220) the information; Signing (230) the information with the vehicle’s private key; and Sending (240) the signed information to the user terminal. [8] A computer program for carrying out one of the methods (100) according to one of the preceding claims, when the computer program runs on a computer, a processor, or a programmable hardware component. [9] A device (30) for receiving signed information from a vehicle, comprising: an interface (32) for communication with a user terminal or a control device; and a data processing circuit (34) configured to carry out at least one of the methods (100; 200) according to any one of claims 1-7. [10] A vehicle (40) having a device (30) according to claim 9.

Images