Charging control device, user interface control device, vehicle and corresponding method and computer program

Abstract

The invention relates to a charging control device, a user interface control device, a vehicle comprising a charging control device and a user interface control device, and corresponding methods and computer programs. The charging control device includes at least one interface for communicating with a charging infrastructure. The charging control device comprises a cryptographically secure element. The charging control device comprises a control circuit configured to obtain a plurality of charging contracts that are cryptographically secure. The control circuit is designed to store the plurality of charging contracts in the cryptographically secure element. The control circuit is configured to store a selection of one of the plurality of charging contracts. The control circuit is designed to authenticate the charging control device with respect to the charging infrastructure on the basis of the selected charging contract.

Description

Technical Field

[0001] The present invention relates to a charging control device, a user interface control device, a vehicle comprising the charging control device and the user interface control device, and corresponding methods and computer programs. Background Art

[0002] Plug & Charge (P&C), a charging standard for electric vehicles, is based on the industry standard ISO 15118. With P&C (hereinafter referred to as P&C), the driver of an electric vehicle, such as a battery electric vehicle (BEV) or a hybrid vehicle (PHEV)—a vehicle with a hybrid power system whose battery can be charged both by the motor and by plugging in a charging plug—is authenticated at a public charging station simply by plugging in a charging cable. This authentication is performed using a standard digital contract certificate. The contract certificate also contains a contract number. The charging point operator (CPO) can use this number to settle the charging process with the contract provider (EMP or MO, Electro Mobility Provider or Mobility Operator, often the same as the EMP) via existing roaming platforms, or directly with the customer (if the CPO is also the contract provider). The operating principle is described in detail below.

[0003] According to the current version of the standard (ISO 15118-2), vehicles at a charging station can only transmit one certificate; therefore, in many systems, only one certificate is stored on the vehicle. According to the standard, this certificate is typically stored on the charging device. The certificate can be installed by the charging station either via PLC (communication via the charging cable) or via the backend (i.e., server) / telematics connection. Contract certificates are managed in a shared pool (collection) on the backend / server. Certificates are created by the MO and retrieved by the OEM (Original Equipment Manufacturer), for example, the vehicle manufacturer. The new version of the standard (ISO 15118-20) describes a method for utilizing multiple certificates. However, this standard requires adaptation to charging controllers and charging stations and will only be supported by future vehicles. Version ISO 15118-2 is typically used in charging station infrastructure and in vehicles. Vehicles and charging stations should be able to communicate using the same version of the ISO standard.

[0004] The publication "Plug & Charge Multi-Contract Handling" by Hubject (an aggregator) and Volkswagen discusses the use of multiple contracts. It proposes that customers can replace a (single) installed certificate with another desired certificate. This restriction on the number of certificates limits customers' choice of charging service providers (who issue these certificates). Consequently, P&C currently functions only with vehicle manufacturer supplies. This not only limits customers (e.g., regarding the alternating use of private and commercial contracts), but also restricts competition for P&Cs. This could discourage charging networks from offering P&Cs themselves, thereby undermining the spread and acceptance of this payment method.

[0005] There is a need for improved concepts for the technical safety of charging processes for electric vehicles. Summary of the Invention

[0006] Summarize

[0007] The present invention is based on the recognition that support for multiple charging contracts can be provided by storing multiple charging contracts / private keys in a cryptographically secure element (i.e., a "Secure Element") of the charging control device, rather than a single charging contract or the private key of the certificate associated with it, on a vehicle's charging control device. In other words, more than one contract certificate, for example, five certificates, can be installed simultaneously on the vehicle. While the private key of the corresponding certificate / charging contract is stored in the cryptographically secure element, the actual certificate and metadata related to the certificate can be stored outside the cryptographically secure element, for example, for storage space reasons. In addition, the charging control device stores information indicating which of the charging contracts should be used when a charging process is initiated (via P&C or a similar method). This selection can be made via the vehicle's user interface control unit (also known as a "Head Unit"). The vehicle driver can determine which certificates are installed and which certificate to use for the next charging process. The vehicle user interface allows the driver to select a charging certificate from a list of available certificates (e.g., contracts that the customer has signed or can sign). For example, the driver can install a specific number of charging certificates for use and, if necessary, change the active contract for each charging process. By keeping the certificates in the vehicle, re-downloading is unnecessary when changing them. The certificates can be loaded for installation via the vehicle's telematics device. This makes installation independent of the charging station.

[0008] A first aspect of the present disclosure relates to a charging control device for a vehicle. The charging control device includes at least one interface for communicating with a charging infrastructure. The charging control device includes a cryptographically secure element. The charging control device includes a control circuit configured to obtain a plurality of cryptographically secure charging contracts. The control circuit is configured to store the plurality of charging contracts in the cryptographically secure element. The control circuit is configured to store a selection of one of the plurality of charging contracts. The control circuit is configured to authenticate the charging control device with respect to the charging infrastructure based on the selected charging contract. This supports the use of multiple charging contracts while maintaining compatibility with existing charging infrastructure.

[0009] In some examples, the at least one interface includes an interface for communicating with a user interface control of the vehicle. The control circuitry may be configured to determine metadata regarding the plurality of cryptographically secure charging contracts and to provide the metadata to the user interface control of the vehicle. This enables display of available charging contracts and selection of a charging contract by the driver via the user interface control.

[0010] For example, the control circuit may be configured to receive a control signal from the user interface control unit for selecting a charging contract and to store a selection based on the control signal. The selection made by the driver via the user interface control unit can thus be stored and the associated charging contract can be used during the next charging process.

[0011] In addition to obtaining charging contracts through charging stations, at least some examples of the present disclosure utilize the possibility of obtaining charging contracts through a server. For example, the at least one interface may include an interface for communicating with a server. The control circuitry may be configured to obtain multiple cryptographically secure charging contracts from the server. This enables obtaining charging contracts independently of the charging infrastructure.

[0012] For example, the charging contract and the communication with the charging infrastructure can be based on the standard ISO 15118 and in particular ISO 15118-2. This enables the charging infrastructure to be utilized within the framework of the standard.

[0013] Another aspect relates to a corresponding method for a charging control device for a vehicle. The method includes obtaining a cryptographically secure plurality of charging contracts. The method includes storing the plurality of charging contracts in a cryptographically secure element of the charging control device. The method includes storing a selection of one of the plurality of charging contracts. The method includes authenticating the charging control device with respect to the charging infrastructure based on the selected charging contract. Another aspect relates to a corresponding program, comprising program code that, when executed on a computer, processor, control module, or programmable hardware component, such as a charging control device, is configured to implement the method.

[0014] Another aspect of the present disclosure relates to a user interface control device for a vehicle. The user interface control device includes at least one interface for communicating with a charging control device of the vehicle and for communicating with a user interface, such as a user interface of the vehicle or a mobile device of a driver of the vehicle. The user interface control device includes a control circuit configured to obtain metadata about a plurality of charging contracts from the charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device. The control circuit is configured to display the plurality of charging contracts via a user interface. The control circuit is configured to provide selection functionality for selecting a charging contract from the plurality of charging contracts via the user interface. The control circuit is configured to provide a control signal for selecting a charging contract for the charging control device based on the selection of a charging contract. This enables display of available charging contracts and selection of a charging contract by the driver via the user interface control device.

[0015] For example, the control circuitry may be configured to activate or provide a display of the multiple charging contracts when the vehicle is located at a charging infrastructure. This allows the driver to be aware of the availability of a choice between different charging contracts. For example, the driver can indicate the use of P&C in a screen displayed when the vehicle is parked near a charging station with P&C functionality and be directly redirected to a selection screen.

[0016] In some examples, the control circuit can be configured to automatically preselect a charging contract based on the charging infrastructure and display the preselection along with the multiple charging contracts. This allows for the use of a charging contract that is particularly favorable, for example, in terms of price, for the respective charging infrastructure. Multiple certificates on board the vehicle, for example, allow for automated contract selection, for example by selecting the most favorable contract at the respective charging station.

[0017] Another aspect relates to a corresponding method for a user interface control device. The method includes obtaining metadata about a plurality of charging contracts from a charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device. The method includes displaying the plurality of charging contracts via a user interface of a vehicle. The method includes providing selection functionality for selecting a charging contract from the plurality of charging contracts via the user interface. The method includes providing a control signal for selecting a charging contract for the charging control device based on the selection of a charging contract. Another aspect relates to a program comprising program code for implementing the method when executed on a computer, processor, control module, or programmable hardware component, such as the user interface control device.

[0018] Another aspect of the present disclosure relates to a vehicle including a charging control device and a user interface control device. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Some examples of the apparatus and / or method are described in more detail below with reference to the accompanying drawings, which are merely exemplary.

[0020] Figure 1a a schematic diagram showing a charge control device;

[0021] Figure 1b A flow chart illustrating a method for a charging control device;

[0022] Figure 2a a schematic diagram showing user interface controls;

[0023] Figure 2b A flow chart illustrating a method for a user interface control device;

[0024] Figure 3 A schematic diagram showing a customer perspective on plug and charge;

[0025] Figure 4 A schematic diagram showing a technical perspective on plug and charge;

[0026] Figure 5 A schematic diagram illustrating the plug-and-charge process from a user's perspective;

[0027] Figure 6 A schematic diagram showing activation and setting of the plug-and-charge function using multiple charging contracts;

[0028] Figure 7 A simplified diagram showing the technical infrastructure for utilizing plug and charge; and

[0029] Figure 8a and 8bShows menu navigation within the vehicle. DETAILED DESCRIPTION

[0030] illustrate

[0031] Some examples will now be described in more detail with reference to the accompanying drawings. However, other possible examples are not limited to the features of the embodiments described in detail. These may include modifications of the features as well as equivalents and alternatives to the features. In addition, the terms used herein to describe specific examples are not intended to limit other possible examples.

[0032] Throughout the description of the accompanying drawings, the same or similar reference numerals represent the same or similar elements or features, which may be implemented in the same or different forms, respectively, and provide the same or similar functions. In addition, in the accompanying drawings, the thickness of lines, layers and / or regions may be exaggerated for clarity.

[0033] Where "or" is used to combine two elements A and B, this should be understood to disclose all possible combinations, i.e., only A, only B, and A and B, unless expressly defined otherwise in individual cases. As alternative language for the same combination, "at least one of A and B" or "A and / or B" may be used. This applies equally to combinations of more than two elements.

[0034] If a singular form is used, such as "one," "the," or "the," and the use of only a single element is not explicitly or implicitly defined as required, alternative examples may also use multiple elements to achieve the same functionality. When a function is described below as being achieved using multiple elements, alternative examples may achieve the same functionality using a single element or a single processing entity. It will also be understood that when the terms "include," "comprise," "have," and / or "contain" are used, they describe the presence of the stated features, integers, steps, operations, processes, elements, components, and / or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, processes, elements, components, and / or groups thereof.

[0035] Figure 1aA schematic diagram shows a charging control device 10 for a vehicle 100 , wherein the charging control device 10 is part of the vehicle 100 . The charging control device includes at least one interface 12 for communicating with a charging infrastructure 105 (e.g., a charging station), for example, via power line communication. In some examples, the at least one interface 12 includes an interface for communicating with a user interface control device 20 of the vehicle 100 and / or at least one interface for communicating with a server (not shown), for example, via a telematics connection or a mobile radio connection. The charging control device 10 includes a cryptographically secure element 14 , such as a so-called "Secure Element" or "Trusted Execution Environment." The charging control device 10 includes a control circuit 16 coupled to the cryptographically secure element 14 and the at least one interface 12 . For example, the cryptographically secure element can be part of the control circuit 16 or a separate component. The control circuit 16 is configured to obtain a plurality of cryptographically secure charging contracts. The control circuit 16 is configured to store the plurality of charging contracts in the cryptographically secure element 14 . The control circuit 16 is configured to store a selection of one of the plurality of charging contracts. The control circuit 16 is designed to authenticate the charge control device 10 with respect to the charging infrastructure 105 based on the selected charging contract.

[0036] Figure 1b A flow chart of a corresponding method for a charging control device 16 is shown. The method includes obtaining 110 the cryptographically secure plurality of charging contracts. The method includes storing 120 the plurality of charging contracts in the cryptographically secure element 14 of the charging control device 10. The method includes storing 130 a selection of one of the plurality of charging contracts. The method includes authenticating 140 the charging control device with respect to the charging infrastructure based on the selected charging contract.

[0037] The following describes a charge control device, a corresponding method for the charge control device, and a corresponding computer program. Features that can be described in connection with the charge control device also apply to the corresponding method or computer program.

[0038] The proposed concept is based on storing not just one but multiple cryptographically secure charging contracts (i.e., cryptographically secure certificates of charging contracts, i.e., cryptographically secure certificates of contracts with mobile operators or charging infrastructure operators) in the cryptographically secure element 14 of the charging control device. For example, up to a predetermined number (e.g., up to four, five, or eight) of charging contracts (i.e., private keys of the corresponding certificates of charging contracts) can be stored on the charging control device. At least the private keys of the corresponding certificates of charging contracts are stored in the memory of the cryptographically secure element. The remaining components of the corresponding certificates of charging contracts can be stored, for example, along with metadata, in the memory of the cryptographically secure element or outside of the cryptographically secure element, such as in NVRAM (Non-Volatile Random Access Memory) of the charging control device. The charging contracts can be retrieved, for example, from a server, such as a server of the vehicle manufacturer, or from the charging infrastructure (via power line communication). In other words, the control circuit can be configured to obtain multiple cryptographically secure charging contracts from a server (e.g., via a user interface control device) and / or the charging infrastructure.

[0039] The cryptographically secure charging contract is based on a so-called provisioning certificate of the vehicle or the charging control device. The private part of the provisioning certificate is kept in the cryptographically secure element 14 and is Figure 7 As shown in , the public part of the provisioning certificate is provided to the other participants, for example, by one or more integrators. This public part can now be used to encrypt the cryptographically secure charging contract or restrict its access so that it can only be used using the private part of the provisioning certificate, with the activation occurring within the cryptographically secure element. During the authentication of the charging control unit, at least the certificate for the charging contract is now used to cryptographically protect communication with the charging infrastructure 105 and to identify the charging control unit to the charging infrastructure. The charging contract and communication with the charging infrastructure can be based on the ISO 15118 standard, and in particular, the ISO 15118-2 standard.

[0040] Which of the charging contracts (i.e., which of the certificates) is used for this purpose depends on the selection of the charging contract. This can be a preselection, such as the selection of the first charging contract installed, as per the standard. This preselection can then be changed via the user interface control unit. Thus, the control circuit can be configured to determine metadata about the cryptographically secure multiple charging contracts and to provide this metadata to the user interface control unit of the vehicle. This metadata can include, for example, the charging contract identifier, the validity period of the charging contract, and / or the operator that issued the charging contract. Based on this metadata, the vehicle driver can now select a charging contract via the user interface control unit. In response to the provided metadata, the control circuit can receive a control signal from the user interface control unit for selecting a charging contract. This control signal can, for example, contain an indication of which charging contract should be selected. The control circuit can be configured to store the selection based on the control signal. This can occur, for example, via a so-called pointer (reference) stored in a data structure, for example within the cryptographically secure element, using the cryptographically secure element, or externally.

[0041] The at least one interface 12 may correspond, for example, to one or more inputs and / or one or more outputs for receiving and / or transmitting information, eg as digital bit values, based on codes, within a module, between modules, or between modules of different entities.

[0042] In various embodiments, the control circuit 16 may correspond to any controller, processor, or programmable hardware component. For example, the control circuit 16 may be implemented as software that programs the corresponding hardware component. Here, the control circuit 16 may be implemented as programmable hardware with correspondingly adapted software. Any processor, such as a digital signal processor (DSP), may be used. The embodiments are not limited to a specific type of processor. Any processor or multiple processors are contemplated for implementation. In some examples, the control circuit 16 may include a cryptographically secure element 14.

[0043] Further details and aspects of the charging control device, the corresponding method, and the computer program are provided in conjunction with the concepts or examples described later (e.g., Figures 2 to 8b). The charging control device and the computer program of the corresponding method may include one or more additional optional features corresponding to one or more aspects of the proposed concepts or examples described earlier or later.

[0044] Figure 2aA schematic diagram of a user interface control device 20 (also referred to as a "Head Unit") for a vehicle is shown. The user interface control device 20 includes at least one interface 22 for communicating with a charging control device 10 (in a vehicle) Figure 1a The user interface control device includes a control circuit 24 coupled to the at least one interface 22. The control circuit 24 is configured to obtain metadata regarding a plurality of charging contracts from the charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device. The control circuit 24 is configured to display the plurality of charging contracts via the user interface. The control circuit 24 is configured to provide, via the user interface, selection functionality for selecting a charging contract from the plurality of charging contracts. The control circuit 24 is configured to provide, based on the selection of the charging contract, a control signal for selecting the charging contract for the charging control device.

[0045] Figure 2b A flow chart illustrating a corresponding method for a user interface control device 24 is shown. The method includes obtaining 210 metadata about a plurality of charging contracts from a charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device. The method includes displaying 220 the plurality of charging contracts via the user interface. The method includes providing 230 selection functionality for selecting a charging contract from the plurality of charging contracts via the user interface. The method includes providing 240 a control signal for selecting a charging contract for the charging control device based on the selection of the charging contract.

[0046] The following describes a user interface control device, a corresponding method for the user interface control device, and a corresponding computer program. Features that can be described in connection with the user interface control device also apply to the corresponding method or computer program.

[0047] In the proposed concept, the user interface control device is used to display and select existing contracts. This is exemplified, for example, in Figure 6In the example shown in FIG. 3 , three charging contracts (DE 123456789, DE 987654321, and DE 555555555) are displayed, two of which are already installed and one (DE 555555555) is ready for download. The control circuit can therefore be designed to display one or more charging contracts available for download (e.g., from a server of a vehicle manufacturer) in addition to the multiple charging contracts stored in the cryptographically secure element of the charging control device, and to retrieve the corresponding information from the server (e.g., by querying the identifier of a new contract certificate, as in Figure 7 , wherein a user interface control device 710 and a server 740 are shown). The charging contracts available to the charging control device can be displayed with the aid of metadata, which the user interface control device receives from the charging control device. Figure 7 As shown in the figure, the control circuit can also be from the server (in Figure 7 740) in the charging contract, for example, retrieves additional information about the charging contract using the charging contract identifier. This additional information may include, for example, information about the price of the charging process, such as by time level, by the provider of the charging station, information about the contracting parties of the charging contract, etc.

[0048] The user interface displays the (installed and possibly available) charging contracts. An input method of the user interface (eg, a touch-sensitive screen or a tactile input device) can be used to provide a selection functionality in the interaction with the control circuit.

[0049] For example, the selection functionality can be provided so that the driver can make the selection by clicking or selecting a menu item via a tactile input device. If the user selects a charging contract that is not available on the charge control device, the control circuit can be designed to retrieve the charging contract from the server as a cryptographically secure charging contract and send it to the charge control device.

[0050] Various measures can be implemented to support the selection of a charging contract. For example, the control circuit can be configured to activate or display multiple charging contracts when the vehicle is located at a charging infrastructure (e.g., via a request or prompt on a screen that is displayed when the driver parks the vehicle). To this end, the control circuit can be configured to detect the vehicle's location at the charging infrastructure using a map that includes the locations of the charging infrastructure and the vehicle's location. Alternatively or additionally, the control circuit can be configured to detect the vehicle's location at the charging infrastructure using a near-field radio signal transmitted by the charging infrastructure.

[0051] However, actual selection can also be supported. Thus, the control circuit can be designed to automatically preselect a charging contract based on the charging infrastructure and display this preselection together with the multiple charging contracts. Various criteria can be considered in the preselection, such as the operator of the charging infrastructure, the respective expected price of the respective charging contract at the charging infrastructure, whether the trip is private or business travel, etc.

[0052] If a selection is made (or a selection deviating from a previously made selection is made), a control signal for selecting the charging contract is provided to the charging control device. If a previously uninstalled charging contract is selected, the control signal may also include the charging contract and / or instructions for installing and selecting the charging contract.

[0053] The at least one interface 22 may correspond, for example, to one or more inputs and / or one or more outputs for receiving and / or transmitting information, eg as digital bit values, based on codes, within a module, between modules, or between modules of different entities.

[0054] In an embodiment, the control circuit 24 may correspond to any controller, processor, or programmable hardware component. For example, the control circuit 24 may also be implemented as software that is programmed to the corresponding hardware component. Here, the control circuit 24 may be implemented as programmable hardware including correspondingly adapted software. Any processor, such as a digital signal processor (DSP), may be used. The embodiments are not limited to a specific type of processor. Any processor or multiple processors are contemplated for implementation.

[0055] After combining (e.g. Figures 1a to 1b , 3 to 8b) describe further details and aspects of the user interface control device, corresponding method, and computer program. The user interface control device, corresponding method, and computer program may include one or more additional optional features corresponding to one or more aspects described before or after the proposed concept or example.

[0056] The present disclosure relates to the use of multiple contracts (ie, contracts) when utilizing a charging infrastructure, for example, according to the “Plug and Charge” (plug and charge) charging standard for electric vehicles.

[0057] Plug & Charge enables electric vehicle (BEV) and PHEV) drivers to automatically authenticate at public charging stations by simply plugging in a charging cable. This functionality is based on ISO standard 15118: Charging stations, vehicles, and charging contracts that support this standard can offer Plug & Charge. The list of vehicles, charging station operators, and contract providers that support Plug & Charge is growing.

[0058] In a simplified illustration, Plug & Charge consists of three components. First, Plug & Charge includes a private contract (contract), in which the contract provider queries the customer for a unique vehicle identification number (e.g., a vehicle-specific so-called PCID, a Provisioning Certificate ID, or a Provisioning Certificate Identifier, which can be the same as the VIN, or Vehicle Identification Number) in order to create a digital contract certificate in the backend system. This is followed by the downloading and activation of the contract. The customer can then download the charging contract certificate to the vehicle, along with the corresponding identification number in the vehicle user interface. The vehicle can then be charged using Plug & Charge. The next time the vehicle is plugged in at a compatible charging station, it transmits the contract certificate to the station via power line communication (i.e., communication via the charging cable). The charging station can then check the contract identifier for charging.

[0059] According to the present disclosure, the vehicle can provide the possibility of managing more than one contract: the customer can load multiple contracts onto the vehicle and select a contract in the user interface as the contract valid for the next charging process.

[0060] Plug & Charge enables a fully automatic and reliable charging experience through certified technology (according to ISO 15118) from EV to charging station. Figure 3 A schematic diagram shows the customer perspective on Plug & Charge. Without Plug & Charge, the charging process consists of "plugging in," "manual authentication" (e.g., via a smart card or mobile app), "waiting for charging instructions," and "locking and leaving the vehicle." With Plug & Charge, the second step, "manual authentication," is eliminated.

[0061] Figure 4 A schematic diagram showing the technical perspectives on plug and charge. First (1.) the vehicle manufacturer (as OEM in Figure 4(shown in the figure) provides the provision certificate to the integrator. The vehicle user then signs a charging contract with the mobile operator (MO). As part of the signing of the charging contract, the vehicle user provides the vehicle identification number (e.g. PCID), which can be done, for example, by the vehicle manufacturer. The mobile operator creates a contract certificate (3.) for the given vehicle identification number, which is also provided to the integrator. The integrator notifies the OEM (4.) that it has received the contract certificate and optionally forwards it to the OEM (or the contract certificate is retrieved by the OEM as needed). The customer instructs the vehicle manufacturer and, in particular, the vehicle to download and install (5.) the contract certificate. As part of the charging process, the vehicle manufacturer or the vehicle communicates (6.) with the charging station operator (CPO) via ISO 15118, which can now again establish contact with the mobile operator via the integrator and / or roaming platform regarding payment for the charging process.

[0062] Charging using Plug & Charge and similar protocols offers the advantage that the charging process does not require the use of RFID (Radio Frequency Identification) cards or mobile devices. Nor does it require the use of EVSE IDs (identification for electric vehicle supply equipment) or QR (Quick Response) codes. Similarly, the use of smartphone apps, which is currently common, is not required to start the charging process. The management of multiple contracts enables the use of these contracts, thereby enabling the use of different contracts (e.g., with the vehicle manufacturer or other mobile operators).

[0063] Figure 5 A schematic diagram shows the Plug & Charge process from the user's perspective. A distinction is made between the "Setup" (or Settings), "Search & Find," "Charging Session," "Payment," and "Reset" phases. The "Setup" phase includes registering with the charging contract and activating Plug & Charge using a mobile device, as well as activating and setting up the function in the vehicle. The "Search & Find" phase includes searching for a charging station, parking and getting out of the vehicle, plugging in the charging connector, manually authenticating, waiting for the charging instruction, locking and leaving the vehicle, and unplugging the charging connector. The "Payment" phase includes providing information on the payment and charging history on the mobile device. The "Reset" phase involves resetting the vehicle. Once the function has been configured once, the customer no longer needs to perform any authentication activities. The configuration is integrated into the existing elements: contract management, charging menu, and resetting to factory settings.

[0064] The settings include, for example, a plug and charge registration process. The plug and charge registration process may include, for example, a registration on the user interface of the vehicle manufacturer (for example, via an Internet browser) in order to register and activate the P&C option. There, the plug and charge settings can be called up via the vehicle management, for example, and plug and charge can be activated. In addition, a contract can be selected to activate plug and charge. For example, all electric vehicles that support plug and charge (BEV and PHEV) can obtain a charging contract based on the vehicle manufacturer that includes plug and charge functionality. A simple check of the vehicle identification number allows the user to check whether the vehicle supports plug and charge. When the vehicle is unlocked, the charging contract based on the vehicle manufacturer can be activated for the plug and charge functionality.

[0065] Figure 6 A schematic diagram shows the activation and setting of a plug and charge function including multiple charging contracts, and in particular shows the activation of charging contracts in a vehicle. Figure 6 Figure 3 shows three screens that appear separated from each other. The top screen shows the main screen for selecting a Plug & Charge contract. This screen includes a switch for activating Plug & Charge and displays the available charging contracts, along with an indication of which contract is currently selected. For example, the user interface displays a list of all available contracts (e.g., from the vehicle manufacturer or other sources). In this case, two installed charging contracts are displayed (the top contract is selected) and one charging contract is ready for installation. A context menu is also displayed in the center, which is invoked when one of the charging contracts is clicked. This context menu displays the charging contract's identification number and buttons for accessing other screens. These buttons include options for contract details, contract activation, contract download (grayed out because the selected contract is already selected), and contract deletion. The bottom screen displays the contract details. This display includes a button for deleting the contract, as well as information including the charging contract's identification number, information about the contract's expiration date, and information about whether a cost estimate is available for the contract. This user guidance enables user-specific installation, activation, selection, and configuration of charging contracts. For example, a distinction can be made between primary and secondary users. Installation, selection and configuration of multiple plug-and-play contracts by the vehicle manufacturer or others is possible.

[0066] Plug & Charge is offered using so-called aggregators, who ensure that a single contract can be used in multiple countries, or that multiple contracts can be used in each country. A similar approach is followed with Easy Charge in China. The present invention can also be used in conjunction with Easy Charge.

[0067] exist Figure 7 A simplified diagram of the technical infrastructure for utilizing plug and charge is shown in FIG. Figure 7Show that it can correspond to Figure 1a The charging control device 710 of the charging control device 10 may correspond to Figure 1a and 1b The user interface control device 20 includes a user interface control device 720, an intermediary 730 (which can be used in the vehicle or during vehicle manufacturing), a plug-and-charge coordinator 740 (from the vehicle manufacturer), an integrator 750, a mobility service provider 760, an operator of a charging station 770, and a charging station 780. Charging control device 710 is configured for communication in accordance with ISO 15118 and is responsible for certificate storage and handling (including diagnostic tasks). The intermediary is the vehicle manufacturer's root certificate authority and provides provisioning certificates.

[0068] To install a new contract in a vehicle, and specifically in the charging control unit, the following steps can be performed. To enable the installation of a charging contract (or corresponding certificate), a provisioning certificate is required. In this example, this is performed by an intermediary 740. The intermediary receives a Certificate Signing Request (CSR) from the charging control unit and provides the private key of the certificate to the charging control unit 730 and the public key to the Plug and Charge coordinator 740. The Plug and Charge coordinator issues the provisioning certificate (i.e., its public key) to the integrator 750. The provisioning certificate securely contains the vehicle's identification (e.g., the vehicle frame number).

[0069] If a customer signs a charging contract, they provide the vehicle's identification to the mobility service provider 750 as part of the contract. The mobility service provider creates a new contract certificate. This contract certificate can now be encrypted using a provisioning certificate (i.e., a public key) so that it can only be decrypted by the vehicle's charge control unit. The matching provisioning certificate is determined using the identification. The integrator 750 receives the encrypted contract certificate and notifies the plug-and-charge coordinator 740 of this information. The plug-and-charge coordinator can now obtain the contract certificate and provide it to the charge control unit, for example, via a telematics connection. Alternatively, the contract certificate can be exchanged between the charging station 780 and the charge control unit 710 via power line communication. If the charge control unit has the corresponding contract certificate, it can be identified by the contract certificate within the context of mutual TLS (Transport Layer Security) communication. The charging station is identified by a leaf certificate derived from the V2G (Vehicle-to-Grid) root certificate. The charging session is authorized between charging station 780, the operator of charging station 770, and aggregator 750, wherein charging station operator 770 can determine mobility service provider 760 via aggregator 750. Payment to mobility service provider 760 is then made according to the contract via the electronic mobility identifier.

[0070] The user interface controller includes a graphical interface system, which can be based on a graphical operating system for mobile devices, for example, and allows for user guidance on board the vehicle, as well as configuration of the vehicle and plug-and-charge functionality, as well as the actual controller functionality. The latter communicates with charge controller 710 and receives information from it about the certificates stored there. This graphical interface system now allows users to select one of the stored certificates, with the selection being communicated to the charge controller. User interface controller 720 also requests the identifier of the new contract certificate (and V2G root certificate) from plug-and-charge coordinator 740 so that it can install the contract certificate. If installation is initiated, user interface controller 720 requests the corresponding certificates for installation from the plug-and-charge coordinator. These certificates are then transmitted to the charge controller. For communication between user interface controller 720 and charge controller 710, diagnostic communication and / or status / configuration communication, for example, can be used.

[0071] In many cases, the driver selects a charging contract via the vehicle's user interface. Alternatively or additionally, this selection can also be made via the vehicle manufacturer's mobile app. This mobile app can be used as an alternative to the vehicle's user interface to configure and provide notifications.

[0072] Figure 8a and 8b Shows the menu navigation in the vehicle. Figure 8a The example in Figure 1 shows a case where Plug & Charge is not supported. In this case, the charging costs are displayed under the "Charging" point in the menu structure. Here, a contract can be selected to estimate the charging costs. This corresponds to the current situation, for example.

[0073] exist Figure 8b The case where Plug & Charge is activated is shown in FIG. In this case, the "Plug & Charge" point is displayed under the "Charging" point in the menu structure, including the option to select a contract for Plug & Charge. This contract is then used for charging the vehicle.

[0074] In the present invention, the charging device (i.e., the charging control unit) and the user interface control unit (head unit) generally exchange the following information. The charging control unit provides the user interface control unit with metadata about installed contracts and information about which contract is currently active. The user interface control unit then provides the charging control unit with information about which contract should be activated. Upon plugging into a charging station, only the activated contract is transmitted for authentication. Selection of the active contract via the user interface / user interface control unit can be performed using various mechanisms. This can occur manually, for example, through user input, which is stored. When parking a vehicle at a plug-and-charge charging station, the user can be informed via the user interface of the contract selection options. This selection can be partially automated, for example, based on user-defined rules, such as location / GPS (Global Positioning System), or the charging station operator, or fully automated, for example, where the user interface control unit determines from a database which installed contracts are compatible with the respective charging station (roaming) or which contract is the most favorable when the vehicle is parked.

[0075] The aspects and features described in association with one of the foregoing examples may also be combined with one or more of the other examples to replace the same or similar features of the other example, or to additionally introduce the features into the other example.

[0076] Examples may also include or relate to a (computer) program including program code for implementing one or more of the above-described methods, when executed on a computer, processor, or other programmable hardware component. In other words, the steps, operations, or processes of various methods described above may also be performed by a programmed computer, processor, or other programmable hardware component. Examples may also encompass program storage devices, such as digital data storage media, that are machine-readable, processor-readable, or computer-readable and encode or contain machine-executable, processor-executable, or computer-executable programs and instructions. Such program storage devices may include, for example, or be digital memories, magnetic storage media such as magnetic disks and tapes, hard drives, or optically readable digital data storage media. Other examples may also include computers, processors, control units, field programmable logic arrays ((F)PLA=(Field)Programmable Logic Array), field programmable gate arrays ((F)PGA=(Field)Programmable Gate Array), graphics processors (GPU=Graphics Processor Unit), application specific integrated circuits (ASIC=application specific integrated circuit), integrated circuits (IC=Integrated Circuit) or single-chip systems (SoC=System-on-a-Chip), which are programmed to perform the steps of the above-described methods.

[0077] It should also be understood that the disclosure of multiple steps, processes, operations, or functions disclosed in the specification or claims should not be interpreted as mandatory to follow the described order, unless it is explicitly given or required for technical reasons in individual cases. Therefore, the above description does not limit the implementation of multiple steps or functions to a specific order. In addition, in other examples, a single step, a single function, a single process, or a single operation may include and / or be decomposed into multiple sub-steps, sub-functions, sub-processes, or sub-operations.

[0078] When aspects are described in the preceding paragraphs in connection with an apparatus or system, these aspects should also be understood as descriptions of the corresponding methods. For example, a block, device, or functional aspect of the apparatus or system may correspond to a feature of the corresponding method, such as a method step. Accordingly, an aspect described in connection with a method may also be understood as a description of a corresponding block, element, property, or functional feature of the corresponding apparatus or system.

[0079] The following claims are hereby incorporated into the detailed description, wherein each claim may serve as a separate example in its own right. Furthermore, it should be noted that although a dependent claim may refer to a specific combination with one or more other claims in the claims, other examples may also include combinations of the dependent claim with the technical solutions of each other dependent or independent claim. Unless otherwise specified in individual cases that a combination is not contemplated, these combinations are explicitly mentioned here. Furthermore, the features of a claim should also be included for each other independent claim, even if that claim is not directly defined as dependent on the other independent claim.

Claims

1. A charging control device for a vehicle, the charging control device comprising: at least one interface for communicating with a charging infrastructure; Cryptographically secure components; as well as A control circuit, wherein the control circuit is configured to: Get cryptographically secure multiple charging contracts, storing the plurality of charging contracts in the cryptographically secure element, storing a selection of one of the plurality of charging contracts, and The charging control device is authenticated with respect to the charging infrastructure based on the selected charging contract.

2. The charging control device according to claim 1, wherein: The at least one interface includes an interface for communicating with a user interface control device of the vehicle, wherein the control circuit is configured to determine metadata about the plurality of charging contracts with cryptographic security and to provide the metadata to the user interface control device of the vehicle.

3. The charging control device according to claim 2, wherein: The control circuit is configured to obtain a control signal for selecting a charging contract from the user interface control device, and is configured to store the selection based on the control signal.

4. The charging control device according to any one of claims 1 to 3, wherein: The at least one interface includes an interface for communicating with a server, wherein the control circuit is configured to obtain the cryptographically secure plurality of charging contracts from the server.

5. The charging control device according to any one of claims 1 to 4, wherein: The charging contract and the communication with the charging infrastructure are based on the ISO 15118 standard.

6. A user interface control device for a vehicle, the user interface control device comprising: at least one interface for communicating with a charging control device of the vehicle and for communicating with a user interface; A control circuit, wherein the control circuit is configured to: obtaining metadata about a plurality of charging contracts from the charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device; displaying the plurality of charging contracts through the user interface; providing selection functionality for selecting a charging contract from the plurality of charging contracts via the user interface; and A control signal for selecting a charging contract for the charging control device is provided based on the selection of the charging contract.

7. The user interface control device according to claim 6, wherein: The control circuit is designed to activate or provide a display of the plurality of charging contracts when the vehicle is located at a charging infrastructure.

8. The user interface control device according to claim 7, wherein: The control circuit is designed to automatically carry out a preselection of charging contracts as a function of the charging infrastructure and to display the preselection together with the plurality of charging contracts. 9 . A vehicle comprising the charge control device according to claim 1 and the user interface control device according to claim 6 .

10. A method for a charging control device for a vehicle, the method comprising: Get cryptographically secure multiple charging contracts; storing the plurality of charging contracts in a cryptographically secure element of the charging control device; storing a selection of one of the plurality of charging contracts; and The charging control device is authenticated with respect to the charging infrastructure based on the selected charging contract.

11. A method for a user interface control device for a vehicle, the method comprising: obtaining metadata about a plurality of charging contracts from a charging control device, the charging contracts being stored in a cryptographically secure element of the charging control device; displaying the plurality of charging contracts via a user interface; providing selection functionality for selecting a charging contract from the plurality of charging contracts via the user interface; and A control signal for selecting a charging contract for the charging control device is provided based on the selection of the charging contract. 12 . A program comprising a program code for carrying out the method according to claim 10 or the method according to claim 11 when the program code is executed on a computer, a processor, a control module or a programmable hardware component.

Images