Method for setting up a charging device and / or fuel dispenser, computer program and device

Abstract

Exemplary embodiments of the present invention provide a method 100 for setting up a charging device and / or fuel dispenser. The method 100 comprises receiving verification data 110 indicative of a public key of a digital vehicle key associated with a user terminal device. The public key is received by a communication device. Furthermore, the method 100 comprises storing the verification data 120 for setting up the charging device and / or fuel dispenser.

Description

[0001] Embodiments of the present invention relate to methods for setting up a charging device and / or fuel pump, a computer program and a device, in particular but not exclusively to a concept for using a public key of a digital vehicle key as verification data for setting up a charging device and / or fuel pump.

[0002] The use of near-field communication (NFC) in electric vehicle charging devices or gas station pumps is now common practice for starting and stopping charging / fueling. The user holds their smartphone or an NFC-enabled card to the charging device / pump to authorize the charging / fueling process. Additional hardware is required for this. Furthermore, authorization of a charging / fueling process cannot be verified by an individual.

[0003] There is therefore a need to provide an improved method for setting up a charging device and / or fuel pump. The methods, device, and computer program according to the independent claims address this need.

[0004] Embodiments are based on the core idea that a method for setting up a charging device and / or fuel pump can be carried out based on a public key of a digital vehicle key associated with a user terminal. Verification of a user of the charging device and / or fuel pump can thus be carried out based on a digital vehicle key. This allows a user of the charging device and / or fuel pump to be identified. Furthermore, an infrastructure already required for using the vehicle, i.e., the user terminal on which the private key of the digital vehicle key is stored, can be used.

[0005] Embodiments relate to a method for implementation by a control unit of a charging device and / or fuel pump for setting up the charging device and / or fuel pump. The method comprises receiving verification data indicative of a public key of a digital vehicle key associated with a user terminal. The public key is received by a communication device. Furthermore, the method comprises storing the verification data for setting up the charging device and / or fuel pump. By using the public key, the control unit of the charging device and / or fuel pump can verify information signed with a private key of the user terminal. This allows, for example, a cryptographic control of a service requested by the user terminal to be performed. In particular, the service can be assigned to a user of the user terminal.By storing the public key, for example, a charging / fueling process, billing, or identification can be simplified.

[0006] In one embodiment, the method may further comprise receiving identification data indicative of a private key of the digital vehicle key of the user terminal. The identification data is received from a user terminal. The method may further comprise verifying the identification data based on the verification data and unlocking the charging device and / or fuel pump after verification of the identification data. The control unit of the charging device and / or fuel pump can verify the identification data from the user terminal using the public key. In particular, the security of the verification can be increased by using a private key of the digital vehicle key. For example, a user of the charging device and / or fuel pump can be determined by assigning a user ID to the digital vehicle key.This allows the charging device and / or fuel pump to be unlocked for the user after user verification. Furthermore, a storage unit for storing a private key of a digital vehicle key can have a higher security standard or offer increased security. By using the private key of the digital vehicle key, a secure infrastructure of the user terminal can be accessed. This can increase the integrity of the method according to the invention.

[0007] In one embodiment, the method may further comprise establishing a communication connection to a backend for receiving user identification data indicative of an identification of a user of the user terminal. The method may further comprise receiving the user identification data from the backend and determining a user of the user terminal based on the user identification data. By using user identification data, a user of the charging device and / or fuel pump can be determined. For example, information about a user ID associated with the private key can be stored in the backend. The control unit of the charging device and / or fuel pump can thus receive information about a user of the digital vehicle key from the backend. This can simplify the determination or verification of a user.

[0008] In one embodiment, the method may further comprise sending service data indicative of a service to be performed connected to the user terminal. The service data is sent to the backend. The method may further comprise receiving confirmation data indicative of confirmation of the service from the backend. Activation may comprise activating the service. For example, the service may require a payment, e.g., performing a charging / refueling process. For example, the payment may be processed by the backend. This may simplify activating the service.

[0009] In one embodiment, receiving 110 can occur via a local communication connection. Furthermore, the method can comprise determining a position of the user terminal via the local communication connection and activating a function of the charging device and / or fuel pump based on the determined position. A local communication connection can be, for example, an ultra-broadband or a Bluetooth Low Energy communication connection. By determining the user terminal, a function of the charging device and / or fuel pump, for example a display of the charging device and / or fuel pump, can be activated when needed. This can reduce energy consumption of the charging device and / or fuel pump and / or improve the user experience.

[0010] In one embodiment, the method may further comprise creating challenge data indicative of an authentication request and sending the challenge data to the user terminal. By creating the challenge data, the control unit of the charging device and / or fuel pump can trigger authentication of the user terminal. This can improve the use of the charging device and / or fuel pump.

[0011] Embodiments relate to a method for setting up a charging device and / or fuel pump by a communication device. The method comprises sending verification data indicative of a public key of a digital vehicle key associated with a user terminal to a control unit of the charging device and / or fuel pump. By sending the public key, the communication device can provide the control unit of the charging device and / or fuel pump with the information required to set up the charging device and / or fuel pump. This can simplify the setup of the charging device and / or fuel pump.

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

[0013] Another embodiment is a device for setting up a charging device and / or fuel pump. The device comprises an interface for communicating with a charging device and / or fuel pump or a communication device, and a data processing circuit configured to carry out at least one of the methods described herein. Embodiments further provide a charging device and / or fuel pump 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 setting up a charging device and / or fuel pump; Fig. 2 shows a schematic representation of another method for setting up a charging device and / or fuel pump; and Fig. 3 shows a block diagram of an embodiment of a device.

[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. 1 shows a schematic representation of a method 100 for setting up a charging device and / or fuel pump. The method 100, for implementation by a control unit of the charging device and / or fuel pump, includes receiving 110 verification data indicative of a public key of a digital vehicle key associated with a user terminal.

[0017] 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. The digital vehicle key can have a key pair. The key pair can include a private key and a public key. A signature created using the private key can be verified using the public key. By receiving 110 the verification data indicative of the public key, the control unit of the charging device and / or fuel pump can thus receive information that can be used to verify the user terminal. This can simplify the setup of the control unit of the charging device and / or fuel pump. In particular, the need for a near-field communication interface can be eliminated.

[0018] The public key is received by a communication device. The communication device can be a user terminal or can be comprised of a user terminal. For example, the private key of the associated digital vehicle key can be stored in the user terminal. Alternatively, the communication device can be part of a vehicle, for example a central control device or part of a central control device. Alternatively, the communication device can be a backend or can be comprised of a backend. For example, a backend can be assigned to an original equipment manufacturer. A plurality of public keys of digital vehicle keys can be stored in the backend. For example, a plurality of public keys of digital vehicle keys for a vehicle can be stored in the backend.This allows the control unit of the charging device and / or fuel pump to receive a plurality of public keys from the backend of the digital vehicle key for a vehicle. This allows the control unit of the charging device and / or fuel pump to be configured in a simplified manner, particularly for use with a vehicle.

[0019] Furthermore, the method 100 includes storing 120 the verification data for setting up the charging device and / or fuel pump. The verification data can be stored in a storage unit of the charging device and / or fuel pump, e.g., the control unit. Since the verification data is a public key, the verification data can be stored in any storage unit of the charging device and / or fuel pump. Storage with increased security, for example, storage in a secure element of the charging device and / or fuel pump, is not required. This can reduce the effort required to store the verification data.

[0020] By using the public key, the control unit of the charging device and / or fuel pump can verify information signed with a private key of the user device. This allows, for example, cryptographic verification of a service requested by the user device. In particular, the service can be assigned to a user of the user device. Storing the public key can simplify, for example, charging / refueling processes, billing, and identification.

[0021] Furthermore, security can be increased through the use of the public key. Typically, there are increased security requirements for the digital vehicle key. 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 communication device. A security element of the communication device 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 communication device and have strict security measures to protect the integrity of the stored data.By storing the public key in the charging device and / or fuel pump, for example, in a storage unit (which is part of the control unit, for example), the CCC infrastructure can be used. This can improve the security of authentication.

[0022] In one embodiment, method 100 may further comprise receiving identification data indicative of a private key of the digital vehicle key of the user terminal. The identification data is received by a user terminal. Furthermore, method 100 may comprise verifying the identification data based on the verification data and unlocking the charging device and / or fuel pump after verifying the identification data. Verification of the identification data may be performed by checking the identification data using the public key. Since the identification data is indicative of a private key, it can be identified and / or decrypted using the public key. This allows for a simplified check to determine whether the sender of the identification data, i.e., the user terminal, has stored the private key.Since, as described above, the private key is stored in a security element, the probability that a third party knows the private key is extremely low. This allows for identification of the user's device with increased security.

[0023] In one embodiment, method 100 may further comprise establishing a communication connection to a backend for receiving user identification data indicative of an identification of a user of the user terminal. Method 100 may further comprise receiving the user identification data from the backend and determining a user of the user terminal based on the user identification data. An assignment of a user ID to a digital vehicle key may be stored in the backend, for example, a backend of an original equipment manufacturer.

[0024] The control unit of the charging device and / or fuel pump can receive a mapping of the user ID to a private key or public key in advance. Optionally or alternatively, the control unit of the charging device and / or fuel pump can send a request for user identification data to the backend. The request can contain information about the private key received from the user terminal. This allows the backend to provide the control unit of the charging device and / or fuel pump with information about a user ID for the respective private key. For example, the user ID can be used to determine whether a user is authorized to use the vehicle and / or the charging device and / or fuel pump.

[0025] In one embodiment, the method 100 may further comprise sending service data indicative of a service to be performed connected to the user terminal. The service data is sent to the backend. Furthermore, the method 100 may comprise receiving confirmation data indicative of confirmation of the service from the backend. Activation may comprise activating the service. The service may, for example, be a charging / refueling process, monitoring, error analysis, and / or use of a local data communication connection. For example, a user may have booked a data flat rate. By assigning the user ID, a determination may be made in the backend as to whether the user has booked a data flat rate. The backend can then send confirmation data indicative of the booking of the data flat rate to the control unit of the charging device and / or fuel pump.This allows a local communication connection to be enabled for the user device, which can improve the user experience. For example, the confirmation data can include confirmation of a payment, e.g., for a charging / fueling process, and / or confirmation of authorization, e.g., for using the local communication connection. This can simplify the use of a service provided by the charging device and / or fuel pump.

[0026] In one embodiment, receiving 110 can occur via a local communication connection. Furthermore, the method 100 can include determining a position of the user terminal via the local communication connection and activating a function of the charging device and / or fuel pump based on the determined position. A local communication connection can be, for example, an ultra-broadband or a Bluetooth Low Energy communication connection. Position determination can be performed, in particular, using an ultra-broadband communication connection, since this is more accurate than using a Bluetooth Low Energy communication connection.

[0027] Based on the position of the user terminal, a function of the charging device and / or fuel pump can be activated. For example, a display for operating the charging device and / or fuel pump and / or a wireless local area network (WLAN) module for establishing a local WLAN communication connection with the user terminal can be activated. For example, the WLAN module can be deactivated again when the user terminal exceeds a certain distance from the charging device and / or fuel pump. This allows a WLAN module of the charging device and / or fuel pump to be selectively activated and / or deactivated.

[0028] In one embodiment, method 100 may further comprise creating challenge data indicative of an authentication request and sending the challenge data to the user terminal. By creating the challenge data, the control unit of the charging device and / or fuel pump can trigger authentication of the user terminal. This can improve the use of the charging device and / or fuel pump.

[0029] The charging device may be a charging device for charging the vehicle via a wired connection or a charging device for charging the vehicle without a wired connection, e.g., via induction.

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

[0031] Fig. 2 shows a schematic representation of a further method 200 for setting up a charging device and / or fuel pump. The method 200 for implementation by a communication device for setting up a charging device and / or fuel pump comprises sending 210 verification data indicative of a public key of a digital vehicle key associated with a user terminal to the charging device and / or fuel pump (in particular the charging device and / or fuel pump that is related to Fig. 1). The method 200 can be implemented by a counterpart of the control unit of the charging device and / or fuel pump from Fig. 1. In particular, the method 200 can be carried out in conjunction with the method of the control unit of the charging device and / or fuel pump from Fig. 1 within the framework of sender and receiver.

[0032] As with reference to Fig. 1, the communication device can be (part of) a user terminal, (part of) a control device of the vehicle, or (part of) a backend. The communication device can generally be a device capable of wireless communication. In particular, the communication device can be a mobile communication device, 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.The communication device can also be part of the vehicle, for example part of a central control unit of the vehicle.

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

[0034] Fig. Figure 3 shows a block diagram of an embodiment of a device 30 for setting up a charging device and / or fuel pump. The device can either be a part of a charging device, e.g., the control unit as shown in Fig. 1 or a communication device (see Fig. 2). The device 30 comprises an interface 32 for communication with a communication device (for example the one shown in Fig. 2) or a control unit of the charging device and / or fuel pump (for example the one described in Fig. 1 described control unit of the charging device and / or fuel pump). 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 control unit of the charging device and / or fuel pump or with reference to Fig. 2 for the communication device. Further embodiments are a charging device and / or fuel pump with a device 30. The illustration in Fig. 3 of the device 30 as part of the charging device 40 is an example of a device 30 according to the invention. In other examples, the device 30 may be a user terminal external to the vehicle 30.

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

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

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

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

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

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

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

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

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

[0044] 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 40 Charging device 100 Method for implementation by a charging device for setting up the charging device 110 Receiving verification data 120 Saving the verification data 200 Method for implementation by a communication device for setting up a charging device 210 Sending verification data

Claims

[1] A method (100) for implementation by a control unit of a charging device and / or fuel pump for setting up the charging device and / or fuel pump, comprising: Receiving (110), from a communication device, verification data indicative of a public key of a digital vehicle key associated with a user terminal; and Storing (120) the verification data for setting up the charging device and / or fuel pump. [2] The method (100) of claim 1, further comprising Receiving, from a user terminal, identification data indicative of a private key of the digital vehicle key of the user terminal; Verifying the identification data based on the verification data; and unlocking the charging device and / or fuel pump after verifying the identification data. [3] The method (100) according to any one of the preceding claims, further comprising Establishing a communication connection to a backend for receiving user identification data indicative of an identification of a user of the user terminal; Receiving the user identification data from the backend; and Determining a user of the user terminal based on the user identification data. [4] The method (100) of claim 3, further comprising Sending, to the backend, service data indicative of a service to be performed connected to the user terminal; and Receiving, from the backend, confirmation data indicative of a confirmation of the service, where Activation includes activation of the service. [5] The method (100) according to any one of the preceding claims, wherein receiving occurs via a local communication link, and the method further comprises: Determining a position of the user terminal via the local communication link; and Activating a function of the charging device and / or fuel pump based on the determined position. [6] The method (100) according to any one of the preceding claims, further comprising: Creating challenge data indicative of an authentication request; and Sending the challenge data to the user device. [7] A method (100) for implementation by a communication device for setting up a charging device and / or fuel pump, comprising sending (210) to a control unit of the charging device and / or fuel pump, verification data indicative of a public key of a digital vehicle key associated with a user terminal. [8] 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. [9] A device (30) for setting up a charging device and / or fuel pump, comprising: an interface (32) for communication with a control unit of a charging device 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-7. [10] A charging device (40) and / or fuel pump comprising a device (30) according to claim 9.

Images