Method for safety supply of energy to a vehicle

By establishing a communication session between the vehicle and the energy supply terminal, generating and decrypting encrypted data packets, and processing transactions, the problems of security voucher theft, payment method programming and transaction amount authorization are solved, and a safe and economical electric vehicle charging payment is achieved. Solution.

CN118984780APending Publication Date: 2024-11-19VISA INTERNATIONAL SERVICE ASSOCIATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031233.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-28
Filing Date
2023-03-27
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In the prior art, the security credentials of vehicle energy supply terminals are easily stolen and hacked, and different terminals need to specially program different payment methods to handle different payment methods, making it difficult to maintain security compliance, the charging infrastructure is high, and the user cannot charge. Accurately authorize transaction amount.

Method used

By establishing a communication session between the vehicle and the energy supply terminal, generating encrypted data packets, transmitting them to the service provider's computer to decrypt, using vouchers or tokens to process transactions, determining the remaining capacity of the vehicle's energy storage unit and the required transaction amount, and generating an authorization request Messages are transmitted to authorized entity computers for authorization.

Benefits of technology

It improves the security of energy supply terminals, simplifies the payment process, reduces the cost of terminal modification, allows users to more accurately pre-authorize the amount, and avoids unnecessary fund holdings.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118984780A_ABST
    Figure CN118984780A_ABST
Patent Text Reader

Abstract

A method is disclosed. The method includes establishing a communication session between a vehicle including a first processor and an energy supply terminal including a second processor. The method includes obtaining, by the first processor in the vehicle, credentials or tokens, and then generating an encrypted data packet including the credentials or tokens. The method also includes providing the encrypted data packet to the energy supply terminal. The energy supply terminal transmits the encrypted data packet to a service provider computer, which decrypts the encrypted data packet to obtain the credential or token, and then processes a transaction for supplying energy to the vehicle using the credential or the token.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a PCT application claiming priority to and the benefit of U.S. Provisional Application No. 63 / 324,382 filed on March 28, 2022 and U.S. Provisional Application No. 63 / 324,565 filed on March 28, 2022, which are incorporated herein by reference in their entirety. Background Art

[0003] Various methods have been developed to provide energy to vehicles. Such methods generally require a user to provide credentials to an energy supply terminal. For example, in order to purchase gasoline from a gasoline supply terminal (e.g., a gas pump) or to purchase electricity from an electricity terminal, a user needs to provide a secure credential such as a credit card or debit card number to the terminal.

[0004] Providing security credentials to the energy supply terminal increases the risk that the security credentials may be stolen by unauthorized users. For example, some unauthorized users may place a skimmer on a card reader at the energy supply terminal and / or may intercept wireless data transmission between an authorized user device and the energy supply terminal. In addition, hackers may hack into the energy supply terminal to obtain the security credentials. Furthermore, unethical employees who may have access to the security credentials may also steal the security credentials obtained by the energy supply terminal.

[0005] Another problem is that there can be many different energy supply terminals. As more payment methods become available, each energy supply terminal needs to be specially programmed or adapted to handle different payment methods. This situation may be difficult to implement and maintain. Further, if the card credentials are received at the energy supply terminal, the energy supply terminal needs to be PCI-DSS (Payment Card Industry-Data Security Standard) compliant. Maintaining this security compliance on many different types of energy supply terminals is also difficult to implement and maintain.

[0006] Another issue is that the current charging infrastructure needs to keep up with the continued demand for electric vehicles. The number of charging stations needs to increase. Conventional charging stations typically require expensive components (e.g., card readers) and specialized software (e.g., cryptographic keys to secure payment data) to process payment transactions.

[0007] Finally, yet another issue to be addressed is how much to charge a user when they charge their electric vehicle. If there is a card reader on the charging station, the charging station will not know how much to authorize for the transaction because it is unknown how much power the user will purchase when the charging station receives the user's credentials. While it is possible to "pre-authorize" a standard amount per electric vehicle (e.g., one hundred dollars) and hold that amount on the user's account (as is currently done at gas stations), this practice may unnecessarily and temporarily prevent some users from using funds they should have access to.

[0008] Embodiments of the invention address these and other problems individually and collectively. Summary of the invention

[0009] One embodiment of the present invention includes a method, comprising: establishing a communication session between a vehicle including a first processor and an energy supply terminal including a second processor; obtaining a credential or token by the first processor in the vehicle, generating an encrypted data packet including the credential or token by the first processor in the vehicle; and providing the encrypted data packet to the energy supply terminal by the first processor in the vehicle, wherein the energy supply terminal transmits the encrypted data packet to a service provider computer, the service provider computer decrypts the encrypted data packet to obtain the credential or token, and then uses the credential or the token to process a transaction for supplying energy to the vehicle.

[0010] Another embodiment of the present invention includes a vehicle, comprising: a first processor; and a computer-readable medium, the computer-readable medium comprising code executable by the first processor to cause the first processor to perform operations, the operations comprising: establishing a communication session between the vehicle and an energy supply terminal including a second processor; obtaining credentials or tokens, generating an encrypted data packet including the credentials or tokens; and providing the encrypted data packet to the energy supply terminal.

[0011] Another embodiment includes a method, comprising: receiving, by a service provider computer, an encrypted data packet from a vehicle via an energy supply terminal, the energy supply terminal supplying energy from the energy supply terminal to the vehicle; decrypting, by the service provider computer, the encrypted data packet to obtain a credential or a token; and processing a transaction for supplying the energy to the vehicle using the credential or the token.

[0012] Another embodiment includes a service provider computer, comprising: a processor; and a computer-readable medium, the computer-readable medium including code executable by the processor for performing operations, the operations including: receiving an encrypted data packet from a vehicle via an energy supply terminal; decrypting the encrypted data packet to obtain a credential or a token; and processing a transaction for supplying energy to the vehicle using the credential or the token.

[0013] Another embodiment of the present invention includes a method comprising: determining, by a processor, a remaining capacity of an energy storage unit in a vehicle; determining, by the processor, a transaction amount required to fill the remaining capacity of the energy storage unit; generating, by the processor, an authorization request message including a token or credential and including the transaction amount; and transmitting, by the processor, the authorization request message to an authorization entity computer for authorization.

[0014] Another embodiment of the present invention includes a computer, comprising: a processor; a computer-readable medium coupled to the processor, the computer-readable medium including code executable by the processor for performing operations, the operations including: determining a remaining capacity of an energy storage unit in a vehicle; determining a transaction amount required to fill the remaining capacity of the energy storage unit; generating an authorization request message including a token or credential and including the transaction amount; and transmitting the authorization request message to an authorization entity computer for authorization.

[0015] Another embodiment of the present invention includes a method, comprising: issuing a first sub-root key pair by a certificate authority computer to a first sub-entity computer, wherein the first sub-entity computer subsequently issues a mobile operator electric vehicle digital certificate including an electric vehicle public key to an electric vehicle; and issuing a second sub-root key pair by the certificate authority computer to a second sub-entity computer, wherein the second sub-entity computer subsequently issues a mobile operator service provider digital certificate including a service provider public key to a service provider associated with an energy supply terminal.

[0016] Another embodiment of the present invention includes a certificate authority computer, comprising: a processor; and a computer-readable medium, the computer-readable medium including code executable by the processor for performing operations, the operations including: issuing a first sub-root key pair to a first sub-entity computer, wherein the first sub-entity computer thereafter issues a mobile operator electric vehicle digital certificate including an electric vehicle public key to an electric vehicle; and issuing a second sub-root key pair to a second sub-entity computer, wherein the second sub-entity computer thereafter issues a mobile operator service provider digital certificate including a service provider public key to a service provider associated with an energy supply terminal.

[0017] A better understanding of the nature and advantages of embodiments of the present invention may be obtained by reference to the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A block diagram of a system according to an embodiment is shown.

[0019] Figure 2 A block diagram of a vehicle according to an embodiment is shown.

[0020] Figure 3 A block diagram of a provisioning terminal according to an embodiment is shown.

[0021] Figure 4 A block diagram of a service provider computer is shown according to an embodiment.

[0022] Figure 5 A block diagram of a user device according to an embodiment is shown.

[0023] Figure 6 A block diagram of a certificate distribution system according to an embodiment is shown.

[0024] Figure 7 A system diagram is shown showing an electric vehicle, a supply terminal, and a service provider computer according to an embodiment.

[0025] Figure 8 Interaction between a user device and a virtual access device in a vehicle in some embodiments is shown. DETAILED DESCRIPTION

[0026] Before discussing the embodiments of the present disclosure, some terms may be described in further detail.

[0027] "User" may include an individual. In some embodiments, a user may be associated with one or more personal accounts and / or mobile devices. In some embodiments, a user may also be referred to as a cardholder, account holder, or consumer.

[0028] A "user device" may be a device operated by a user. Examples of user devices may include mobile phones, smart phones, cards, personal digital assistants (PDAs), laptop computers, desktop computers, server computers, thin client devices, tablet PCs, and the like. In addition, the user device may be any type of wearable technology device, such as a watch, earphones, rings, bracelets, glasses, and the like. The user device may include one or more processors capable of processing user input. The user device may also include one or more input sensors for receiving user input. As is known in the art, there are a variety of input sensors capable of detecting user input, such as accelerometers, cameras, microphones, and the like. The user input obtained by the input sensor may come from a variety of data input types, including but not limited to audio data, visual data, or biometric data. The user device may include any electronic device that can be operated by a user, and the electronic device may also provide remote communication capabilities with a network. Examples of remote communication capabilities include using a mobile phone (wireless) network, a wireless data network (e.g., 3G, 4G, or similar networks), Wi-Fi, Wi-Max, or any other communication medium that can provide access to a network (such as the Internet or a private network). The user device may also be a payment device such as a credit card, debit card, or prepaid card.

[0029] A "payment device" may include any suitable device that can be used to conduct a financial transaction (e.g., provide payment credentials to a merchant). A payment device may be a software object, a hardware object, or a physical object. As an example of a physical object, a payment device may include a substrate (e.g., a paper or plastic card), and information printed, embossed, encoded, or otherwise included at or near the surface of the object. A hardware object may involve a circuit system (e.g., a permanent voltage value), and a software object may involve non-permanent data stored on the device. A payment device may be associated with a value such as a monetary value, a discount, or store credit, and a payment device may be associated with an entity such as a bank, a merchant, a payment processing network, or an individual. A payment device may be used to conduct a payment transaction. Suitable payment devices may be handheld and compact so that they can fit into a user's wallet and / or pocket (e.g., may be pocket-sized). Exemplary payment devices may include smart cards, magnetic stripe cards, key chain devices (e.g., Speedpass available from Exxon-Mobil Corporation), and other electronic devices. TM ) and the like. Other examples of mobile communication devices include pagers, payment cards, security cards, access cards, smart media, transponders, and the like. If the payment device is in the form of a debit card, credit card, or smart card, the payment device may also optionally have features such as a magnetic stripe. Such devices may operate in contact or contactless mode. In some embodiments, the mobile communication device may act as a payment device (e.g., the mobile communication device may store and be able to send payment credentials for a transaction).

[0030] An "application" may be computer code or other data stored on a computer-readable medium (eg, a memory element or a secure element) that may be executed by a processor to perform a task.

[0031] A "key" may include a piece of information used in a cryptographic algorithm to transform input data into another representation. A cryptographic algorithm may be an encryption algorithm that transforms original data into an alternative representation, or a decryption algorithm that transforms encrypted information back into the original data. Examples of cryptographic algorithms may include Triple Data Encryption Standard (TDES), Data Encryption Standard (DES), Advanced Encryption Standard (AES), etc.

[0032] A "public key" may include an encryption key that may be openly and publicly shared. A public key may be designed to be shared and may be configured so that any information encrypted with the public key can only be decrypted using the private key associated with the public key (i.e., a public / private key pair).

[0033] A "private key" may include any cryptographic key that may be protected and secure. A private key may be securely stored at an entity and may be used to decrypt any information that has been encrypted using the associated public key of a public / private key pair associated with the private key.

[0034] A "public / private key pair" may refer to a pair of associated cryptographic keys generated by an entity. The public key may be used for public functions, such as encrypting a message to be sent to an entity, or for verifying a digital signature that should be made by an entity. On the other hand, the private key may be used for private functions, such as decrypting a received message or applying a digital signature. In some embodiments, the public key may be authorized by a subject known as a certificate authority (CA), which stores the public key in a database and distributes it to any other entity that requests it. The private key may typically be kept in a secure storage medium, and will typically be known only to the entity. The public and private keys may be in any suitable format, including formats based on Rivest-Shamir-Adleman (RSA) or elliptic curve cryptography (ECC).

[0035] A "digital signature" may include an electronic signature for a message. A digital signature may be a numeric data value, an alphanumeric data value, or any other type of data. In some embodiments, a digital signature may be a unique data value generated from a message (or data packet) and a private key using a cryptographic algorithm. In some embodiments, a verification algorithm using a public key may be used to verify the signature. A digital signature may be used to prove the authenticity of the sender.

[0036] "Interaction" may include a mutual action or influence. "Interaction" may include a communication, contact, or exchange between parties, devices, and / or entities. Exemplary interactions include a transaction between two parties and an exchange of data between two devices. In some embodiments, an interaction may include a user requesting access to a power transfer.

[0037] "Access device" can be any suitable device that provides access to resources. The access device can take any suitable form. Some examples of access devices include vending machines, kiosks, POS or point of sale devices (e.g., POS terminals), cellular phones, PDAs, personal computers (PCs), tablet PCs, handheld dedicated readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), etc. The access device can use any suitable contact or contactless operation mode to send or receive data from or associated with a user's mobile communication device. In some embodiments, the access device may include a reader, a processor, and a computer-readable medium. The reader may include any suitable contact or contactless operation mode. For example, an exemplary reader may include a radio frequency (RF) antenna, an optical scanner, a barcode reader, or a magnetic stripe reader for interacting with a payment device and / or a mobile communication device.

[0038] "Access data" may include any suitable data that can be used to access a resource or create data that can access a resource. In some embodiments, the access data may be account information for a payment account. Account information may include PAN, payment token, expiration date, card verification value (e.g., CVV, CVV2), dynamic card verification value (dCVV, dCVV2), an identifier of the issuer holding the account, etc. In other embodiments, the access data may include data that can be used to access a location or access secure data. Such information may be ticket information for an event, data for accessing a building, transit ticket information, passwords, biometrics, or other credentials for accessing secure data, etc.

[0039] A "credential" may include any evidence of an authority, right, or privilege. For example, an access credential may include permission to access certain tangible or intangible assets, such as buildings or files. Examples of credentials may include a password, passcode, or confidential message.

[0040] "Payment credentials" may include any suitable information associated with an account (e.g., a payment account and / or payment device associated with the account). Such information may be directly related to the account, or may be derived from information related to the account. Examples of account information may include PAN (primary account number or "account number"), username, expiration date, CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification value, and the like. CVV2 is generally understood to be a static verification value associated with a payment device. The CVV2 value is typically visible to the user (e.g., consumer), while the CVV and dCVV values ​​are typically embedded in a memory or authorization request message, which is not easily known to the user (although they are known to the issuer and payment processor). Payment credentials may be any information that identifies a payment account or is associated with a payment account. Payment credentials may be provided to make payments from a payment account. Payment credentials may also include username, expiration date, gift card number or code, and any other suitable information.

[0041] A "digital signature" may include a type of electronic signature. A digital signature may encrypt a document with a digital code that may be difficult to copy. In some embodiments, a "digital signature" may refer to the result of applying an algorithm based on a public / private key pair that allows a signing party to demonstrate and a verifier to verify the authenticity and integrity of a document. The signing party works with the help of a private key and the verifier works with the help of a public key. This process proves the authenticity of the sender, the integrity of the signed document, and the so-called principle of non-repudiation, which does not allow denial of what has been signed. A certificate or other data that includes a signing party's digital signature is said to be "signed" by the signing party.

[0042] A "certificate" or "digital certificate" may include an electronic file and / or a data file. In some cases, a certificate or digital certificate may be a device certificate. In some embodiments, a digital certificate may use a digital signature to bind a public key to data associated with the same identity. A digital certificate may be used to prove ownership of a public key. A certificate may include one or more data fields, such as the legal name of the identity, the serial number of the certificate, the start and end dates of validity of the certificate, licenses associated with the certificate, etc. The certificate may include a "start valid" date indicating the first date the certificate is valid, and an "end valid" date indicating the last date the certificate is valid. The certificate may also include a hash of the data included in the data field in the certificate. The certificate may be signed by a certificate authority.

[0043] A "certificate authority" (CA) may include an entity that issues digital certificates. A certificate authority may prove its identity using a certificate authority certificate, which includes the certificate authority's public key. A certificate authority certificate may be signed with the private key of another certificate authority, or may be signed with the private key of the same certificate authority. The latter is referred to as a self-signed certificate. A certificate authority may maintain a database of all certificates issued by the certificate authority. A certificate authority may maintain a list of revoked certificates. A certificate authority may be operated by an entity, such as a processing network entity, an issuer, an acquirer, a central bank, etc.

[0044] Figure 1 A system according to an embodiment is shown. The system may include a user 100 operating a user device 102 and an electric vehicle 103 including an electric vehicle processor 104 (which may be an example of a first processor). In some embodiments, the electric vehicle processor 104 may be an electric vehicle communication controller (EVCC).

[0045] The system may also include an energy supply terminal 105 (eg, an electric vehicle charging station) including an energy supply terminal processor 106 (which may be an example of a second processor). In some embodiments, the energy supply terminal processor 106 may be a supply equipment communication controller (SECC).

[0046] The terms "Electric Vehicle Communication Controller (EVCC)" and "Supply Equipment Communication Controller (SECC)" come from ISO 15118. ISO 15118 is one of the International Electrotechnical Commission (IEC) standard groups for electric road vehicles and electric industrial trucks. ISO 15118 is a proposed international standard that defines a vehicle-to-grid (V2G) communication interface for bidirectional charging / discharging of electric vehicles.

[0047] The cable 120 may be attached to the energy supply terminal 105 and may physically and communicatively connect the electric vehicle and the energy supply terminal 105. In some embodiments, the cable 120 is a charging cable suitable for charging an electric car or other electric vehicle 103. In some embodiments, the energy supply terminal 105 and the electric vehicle 103 may communicate via a protocol such as ISO 15118.

[0048] In other embodiments, cable 120 is not necessary where other energy supply mechanisms may be used. For example, electric vehicle 103 may receive energy (e.g., electrical energy) from energy supply terminal 105 via induction, which does not require the use of a physical charging cable. Communications between energy supply terminal 105 and electric vehicle 103 may be transmitted via another wireless protocol (e.g., Bluetooth). TM or Wi-Fi TM )occur.

[0049] The system may also include a service provider computer 108 operated by a service provider and a certificate authority computer 110 operated by a certificate authority. The system may also include a transaction processing subsystem, which may include a processing network computer 112 in a processing network (such as a payment processing network) and an authorization entity computer 114 that may communicate with the service provider computer 108. In some embodiments, the entity operating the payment processing network may be referred to as a "mobile operator."

[0050] Figure 1 The electrical components (e.g., computers) in the system of any of the following figures can be in operative communication with each other via any suitable communication medium 150. Suitable examples of the communication medium 150 can be any one and / or combination of the following: direct interconnection; the Internet; a local area network (LAN); a metropolitan area network (MAN); an operating mission as an Internet node (OMNI); a secure custom connection; a wide area network (WAN); a wireless network (e.g., using protocols such as, but not limited to, the Wireless Application Protocol (WAP); I-mode, etc.), etc. Figure 1 Messages between computers, networks, and devices may be transmitted using secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); Hypertext Transfer Protocol (HTTP); and Hypertext Transfer Protocol Secure (HTTPS).

[0051] In some embodiments, the service provider operating the service provider computer 108 may be a service provider that can provide charging services to users. Alternatively, it may be an entity (e.g., a payment processor) that performs services on behalf of the service provider that provides the charging service. Examples of service providers may include charging point operators, electric vehicle manufacturers, payment processors such as payment service providers, etc.

[0052] In some embodiments, if the user 110 has a pre-existing relationship with the service provider, the user 100 can communicate with the service provider computer 108 to establish a service provider account. In some cases, the service provider account can be used to obtain electrical energy from the energy supply terminal 105. In some embodiments, the service provider account can be identified by a service provider account number such as an eMobility account ID (eMAID). In other embodiments, the service provider operating the service provider computer 108 may not have a pre-existing relationship with the user 100.

[0053] The certificate authority computer 110 can provide the digital certificate to Figure 1One or more other devices in. For example, the certificate authority computer 110 can provide a sub-root key to a sub-certificate authority (e.g., a mobile operator or other entity). The sub-certificate authority can provide certificates to various entities. In some embodiments, the sub-certificate authority can issue a mobile operator electric vehicle digital certificate to an electric vehicle. Another sub-certificate authority can issue a mobile operator service provider digital certificate to a service provider operating a service provider computer. The mobile operator electric vehicle digital certificate and the mobile operator service provider digital certificate can originate from the mobile operator. In Figure 6 An example of such a digital certificate system including a certificate authority computer is shown in .

[0054] Figure 2 A block diagram of a vehicle 200 according to some embodiments is shown. The vehicle 200 may be, for example, an electric vehicle. Although the vehicle 200 may be described as an automobile, it should be understood that in some embodiments, the techniques described herein may also be applicable to other types of vehicles, such as motorcycles, boats, airplanes, or other types of powered machinery for transporting a user from one location to another.

[0055] The vehicle 200 may include various electronic control units (ECUs) to operate and control the electrical system or other subsystems of the vehicle 200, and may include sensors 235 that the ECUs may monitor. Each ECU may include a microcontroller and one or more memories (e.g., any combination of SRAM, EEPROM, flash memory, etc.) that store one or more executable programs of the ECU. Examples of ECUs may include an engine / motor control unit 210, a transmission control unit 220, and the like. In some embodiments, the vehicle 200 may include additional ECUs not explicitly shown, omit one or more ECUs, and / or integrate any functionality of different ECUs into a single ECU.

[0056] Vehicle 200 may also include a battery system 230 including one or more batteries and a charging interface 233 for charging the one or more batteries. Battery system 230 and charging interface 233 may communicate with and be coupled to an onboard computing system 250 and its processor 252.

[0057] The engine / motor control unit 210 may control actuators, valves, motors, and / or other components of the engine of the vehicle 200 or the motor of the vehicle 200. The transmission control unit 220 may control the gear shifting and transmission modes (e.g., parking, driving, neutral, reverse) of the vehicle 200. The battery system 230 may include electronic devices that may control the voltage and current supplied by one or more batteries of the battery system to various components of the vehicle 200. The sensor 235 may include: a vehicle speed sensor (e.g., a wheel sensor) to detect the speed of the vehicle 200, a temperature sensor to detect the operating temperature of various components of the vehicle, an air sensor to detect the oxygen level in the engine, a sensor to detect the amount of energy (e.g., electrical energy, gasoline, etc.) currently in the vehicle or the available capacity of an energy storage device (such as a battery), a camera to observe the surroundings of the vehicle 200, and the like. The various ECUs, devices, and sensors may communicate with each other via the vehicle communication bus 240. Examples of the vehicle communication bus 240 may include a controller area network (CAN) bus, a local interconnect network (LIN) bus, a vehicle area network (VAN) bus, or other suitable signaling bus for vehicle communications.

[0058] The vehicle 200 may also include various radio frequency (RF) transceivers to allow the vehicle 200 to receive and transmit RF signals to and from other devices. For example, the vehicle 200 may include a positioning satellite receiver 170 (e.g., a GPS receiver) to receive satellite signals that may be demodulated and decoded to determine the location of the vehicle 200. The positioning satellite receiver 270 may be used by a positioning or navigation subsystem of the vehicle 200 to perform route determination and mapping functions.

[0059] The vehicle 200 may also include a wireless communication subsystem 290 to enable network connectivity for the vehicle 200. The wireless communication subsystem 290 may include one or more wireless transceivers that use WiFi, WiMax, or other types of wireless network communication protocols to connect the vehicle 200 to an external network (e.g., the Internet) so that the vehicle 200 can communicate with a remote server. The wireless communication subsystem 290 may also include one or more short-range or short-range wireless transceivers (e.g., RFID, Bluetooth or Bluetooth Low Energy, NFC, beacons, infrared transmitters and / or receivers) that can be used to communicate with access devices that are close to the vehicle 200.

[0060] The vehicle 200 may also include an onboard computing system 250 with which a user of the vehicle 200 may interact. The onboard computing system 250 may be an information system, an infotainment system, or other instrument system. The onboard computing system 250 may be installed in a center console, a dashboard, a rear console, or other locations in the vehicle 200 that facilitate user access to the onboard computing system 250. In some embodiments, the onboard computing system 250 may be coupled to the vehicle communication bus 240 to receive vehicle status information from the ECU and sensors 235.

[0061] The vehicle-mounted computing system 250 may include a processor 252, a memory 260, and a user interface 254. The user interface 254 may include an input interface, such as any number of buttons, knobs, microphones, and / or touch screens that may receive user input, and an output interface, such as a display (which may be part of a touch screen) and / or a speaker. The display of the user interface 254 may be integrated with the housing of the vehicle-mounted computing system 250, or may be a separate component that is coupled to the vehicle-mounted computing system 250 but is installed at a different location from the vehicle-mounted computing system 250. For example, the display of the user interface 254 can be mounted on the surface of the center console, on the dashboard, on the surface of the rear console, behind the headrest, on the interior roof, on the sun visor, or other suitable location in the vehicle, and can display various types of information, including information such as vehicle status information (e.g., speed, fuel economy, engine temperature, etc.), environmental information (e.g., inside / outside temperature, weather, etc.), navigation information (e.g., maps, routes, places of interest, etc.), entertainment (e.g., video or audio selections or the name of a radio station), energy level information (e.g., the current amount of charge and the amount of gasoline that needs to be filled to a certain capacity), transaction information, energy terminal information, etc.

[0062] The memory 260 may include any combination of SRAM, DRAM, EEPROM, flash memory, and / or other types of memory, among others. The memory 260 may store a plurality of applications, such as an in-vehicle access application 262, a navigation application 264, a virtual access device application 266, and / or other applications not explicitly shown (e.g., an air conditioning control application). The virtual access device application 266 may include code executable by the processor 252 to emulate an access device, such as a point-of-sale terminal. Some of the functions programmed into the virtual access device application 266 are described below in connection with the present invention. Figure 8 Described in the description.

[0063] The navigation application 264 can be part of the positioning or navigation subsystem of the vehicle 200 and can provide navigation functions such as maps and route determination functions. The user of the vehicle 200 can input the desired location into the onboard computing system 250, and the navigation application 264 can determine the current location of the vehicle 200 using the positioning satellite receiver 270 and provide directions to the desired location. The navigation application 264 can display a map on the user interface 254 and highlight the route to the desired destination. The navigation application 264 can also display nearby places of interest and / or nearby businesses on the user interface 254.

[0064] The onboard access application 262 enables the onboard computing system 250 to access resources of the vehicle 200. In some scenarios, the onboard access application 262 can allow a user of the vehicle 200 to perform transactions with a resource provider computer without requiring the user to leave the vehicle 200 and without requiring the user to use another device such as the user's payment card or mobile device. The onboard access application 262 can store account credentials 267 or tokens or reference identifiers thereof for various accounts, allow the user to select a particular account, and upon user approval, transmit the account credentials or tokens (or reference identifiers thereof) associated with the selected account to the user device and / or server. The memory 260 can also include a cryptographic key 268, which can be used to encrypt data, sign data, verify data, etc.

[0065] The memory 260 may include a computer-readable medium. The computer-readable medium may include code executable by the processor 252 to perform operations including: establishing a communication session between the vehicle and an energy supply terminal including a second processor; obtaining a credential or token; generating an encrypted data packet including the credential or token; and providing the encrypted data packet to the energy supply terminal.

[0066] The computer-readable medium in the memory 260 may also include code that can be executed by the processor 252 to perform the following operations, the operations including: determining the remaining capacity of the energy storage unit in the vehicle; determining the transaction amount required to fill the remaining capacity of the energy storage unit; generating an authorization request message including a token or credential and including the transaction amount; and transmitting the authorization request message to the authorization entity computer for authorization.

[0067] Figure 3A block diagram of an energy supply terminal 80 according to an embodiment is shown. The energy supply terminal 80 may include a processor 302. The energy supply terminal may also include a computer-readable medium 304 coupled to the processor 302, a short-range communication interface 306, an actuator 308, a vehicle interface 310, and a long-range communication interface 314. An energy source 312 may be coupled to the actuator 308 and the vehicle interface 310. The actuator 308 may be a pump or a switch (e.g., an electrical or mechanical switch) that allows the energy source 312 to provide energy to the vehicle interface 310 and then to the connected vehicle. The energy source 312 may be an electrical wire or a conduit, or the energy source may be a fuel tank.

[0068] The computer readable medium 304 may also include a communication module 304A, an energy regulation module 304B, and an authentication module 304C. The communication module 304A may include code that can be executed by the processor 302 to allow the energy supply terminal 80 to communicate with an external device such as a vehicle or a remote computer such as the terminal support computer 70 described previously. The energy regulation module 304B and the processor 302 can determine how much energy is needed or should be provided to the vehicle, and can control the actuator 308 to control the energy flow to the vehicle interface 310 and the connected vehicle. The authentication module 304C can be used to authenticate users and / or vehicles that can be connected to the energy supply terminal 80.

[0069] The computer-readable medium 304 may also include code that, when executed by the processor 302, causes the processor to perform the following operations, the operations including: establishing a communication session between a vehicle including a first processor and an energy supply terminal including a second processor; receiving an encrypted data packet including a credential or a token from the vehicle by the energy supply terminal; and transmitting the encrypted data packet by the energy supply terminal to a service provider computer, the service provider computer decrypting the encrypted data packet to obtain the credential or the token, and then using the credential or the token to process a transaction for supplying energy to the vehicle.

[0070] Figure 4 A block diagram of a service provider computer 400 is shown according to an embodiment. The service provider computer 400 may include a processor 402, which may be coupled to a data storage device 406 and a network interface 408. A computer readable medium 404 may also be operably coupled to the processor 402. The data storage device 406 may store any suitable data, including but not limited to credentials and / or tokens, references to credentials and / or tokens, user data (e.g., a username) or vehicle data (e.g., a VIN) associated with a credential or token, and the like.

[0071] The computer-readable medium 404 may include a plurality of software modules, including a credential / token management module 404A, an authentication module 404B, and an authorization processing module 404D.

[0072] The credential / token management module 404A may include code that causes the processor 402 to retrieve a credential or token from the data storage device 406 in response to receiving a credential or token identifier. The credential / token management module 404A may also include code that causes the processor 402 to receive credentials and / or tokens and store them in the data storage device 406.

[0073] Authentication module 404B may include code that causes processor 402 to authenticate a user, user device, or vehicle used by a user before processing a transaction.

[0074] The cryptographic module 404C may include code that causes the processor 402 to perform cryptographic operations including encryption, decryption, hashing, signing, signature verification, key generation, and the like.

[0075] The authorization processing module 404D may include code that causes the processor 402 to perform authorization processing. The authorization processing may include generating an authorization request message and transmitting the authorization request message or providing instructions to generate an authorization request message and transmitting the authorization request message, receiving an authorization response message, and generating notifications related to transaction authorization or rejection. The authorization processing may also include collecting authorization data and transmitting it to another computer.

[0076] The computer-readable medium 404 may also include code that can be executed by the processor 402 to perform the following operations, the operations including: receiving an encrypted data packet from the vehicle via the energy supply terminal by the service provider computer; decrypting the encrypted data packet by the service provider computer to obtain a credential or token; and processing a transaction for supplying energy to the vehicle using the credential or token.

[0077] Figure 5 A block diagram of a user device 500 is shown in accordance with an embodiment. The user device 500 may include device hardware 504 coupled to a system memory 502.

[0078] Device hardware 504 may include a processor 506, a short-range antenna 514, a long-range antenna 516, input elements 510, a user interface 508, and output elements 512 (which may be part of the user interface 508). Examples of input elements may include a microphone, a keypad, a touch screen, a sensor, etc. Examples of output elements may include a speaker, a display screen, and a haptic device.

[0079] The long-range antenna 516 may include one or more RF transceivers and / or connectors that can be used by the user device 500 to communicate with other devices and / or connect to an external network. The user interface 508 may include any combination of input and output elements to allow the user to interact with the user device 500 and call the functions of the user device. The short-range antenna 509 may be configured to communicate with external entities through a short-range communication medium (e.g., using Bluetooth, Wi-Fi, infrared, NFC, etc.). The long-range antenna 819 may be configured to communicate over the air with a remote base station and a remote cellular or data network.

[0080] The system memory 502 may be implemented using any combination of any number of non-volatile memories (eg, flash memory) and volatile memories (eg, DRAM, SRAM), or any other non-transitory storage media or combinations thereof.

[0081] The system memory 502 may also store a transaction initiation module 502A, a voice assistant module 502B, an authentication module 502C, a credential and / or token 502D, and an operating system 502E. The transaction initiation module 502A may include instructions or codes for initiating and conducting transactions with an external device (e.g., an access device or a processing computer). The transaction initiation module may include code that can be executed by the processor 506 to generate an authorization request message and transmit the authorization request message and receive an authorization response message and forward the authorization response message. The transaction initiation module may also include code that can be executed by the processor 506 to form a local connection or otherwise interact with an external device (e.g., an operator computer). The voice assistant module 502B may include code that can be executed by the processor 506 to receive a voice segment and generate data corresponding to the voice segment and analyze the data. The authentication module 502C may include code that can be executed by the processor 506 to authenticate a user. This may be performed using a user secret (e.g., a password) or a user biometric. The system memory 502 may also store a credential and / or token or a reference 502D to a credential and / or token.

[0082] Figure 6 The digital certificate structure according to the embodiment is shown. The certificate authority computer 110 operated by the certificate authority can store the root certificate. The root certificate can be a digital certificate associated with a root public key and a root private key. The certificate authority computer 110 can issue a sub-root key to one or more sub-entities, and the one or more sub-entities can include an organization operating the certificate authority root and / or a third party authorized by the certificate authority to operate as a sub-certificate authority.

[0083] Figure 6An example of a sub-entity computer is shown, which includes a first sub-entity computer 113 operated by a first sub-entity (e.g., a service provider, a manufacturer, etc.) and a second sub-entity computer 108 operated by a second sub-entity. For example, the certificate authority computer 110 can issue a first sub-root key pair to the first sub-entity computer 113, and can allow the first sub-entity operating the first sub-entity computer 113 to issue an electric vehicle digital certificate (or a "contract certificate" according to ISO 15118) to the electric vehicle. For example, the first sub-entity computer 113 can be operated by a mobile operator or a representative of a mobile operator, and can issue a mobile operator electric vehicle digital certificate to the electric vehicle 103. The mobile operator electric vehicle digital certificate can include an electric vehicle public key, and the certificate or its components can be signed with a private key of the first sub-root key pair. An external entity can verify the mobile operator electric vehicle digital certificate by accessing the public key of the first sub-root key pair to verify the signed mobile operator electric vehicle digital certificate. The electric vehicle 103 can also be provided with a root certificate from the certificate authority computer 110. The root certificate may be used by an external entity to authenticate the first sub-entity computer 108 that issued the mobile operator electric vehicle digital certificate, and to verify that the mobile operator electric vehicle digital certificate is otherwise reputable.

[0084] A similar process can be performed between the certificate authority computer 110 and the second sub-entity computer 115. In some embodiments, the second sub-entity computer 115 can be operated by a mobile operator or a representative of the mobile operator. For example, the certificate authority computer 110 can issue a second sub-root key to the second sub-entity computer 115. The sub-entity computer can issue a mobile operator service provider digital certificate (e.g., a mobile operator payment service provider digital certificate) to the service provider operating the energy supply terminal 105. The mobile operator service provider digital certificate may include a service provider public key. The mobile operator service provider digital certificate or its components can be signed with the private key of the second sub-root key pair. The mobile operator service provider digital certificate can be loaded into the energy supply terminal in the system. The energy supply terminal can be part of a charging network that works in conjunction with a service provider (e.g., a charging network, a payment service provider, etc.). In some embodiments, the mobile operator service provider digital certificate can be transmitted from the energy supply terminal 105 to the electric vehicle 103 during a charging session. The electric vehicle 103 uses the mobile operator service provider digital certificate (after authentication with the certificate authority root, which will have been pre-installed) to generate a session-unique key, which is used to create an encrypted data packet that can only be decrypted by the service provider (the second sub-entity computer 115 has issued the mobile operator service provider certificate to the service provider).

[0085] Figure 6 The certificate hierarchy shown in can allow any electric vehicle to trust the energy supply terminal, and allow any energy supply terminal to trust any electric vehicle, because the certificates of these entities can correspond to the root public key and root certificate of the certificate authority computer 110. For example, before the electric vehicle 103 transmits sensitive data (such as credentials or tokens) to the energy supply terminal 105, the electric vehicle processor 104 can receive the mobile operator service provider digital certificate of the energy supply terminal 105, and can verify the digital signatures of both the second sub-entity computer 115 and the certificate authority computer 110.

[0086] in other words, Figure 6 The certificate hierarchy shown in can allow any electric vehicle to trust the energy supply terminal, and any energy supply terminal to trust any electric vehicle, because the certificates of these entities can correspond to the root public key and root certificate of the certificate authority computer 110. According to ISO15118, the electric vehicle certificate (left branch) can be used to sign messages originating from the electric vehicle 103 (which can be authenticated by the energy supply terminal 105 (which has the root certificate authority key of the certificate authority computer 110)). In addition to the functions described in ISO15118, the service provider certificate can be authenticated by the electric vehicle 103 (which has the root certificate authority key of the certificate authority computer 110) before creating an encrypted JWE containing sensitive card data.

[0087] Figure 7 A diagram and overlay process flow for power transfer according to an embodiment is shown. Figure 7 The process shown in can be performed by the electric vehicle 103, the energy supply terminal 105 (eg, a charging station), and the service provider computer 108. The process may include explicit interaction with the user 100, or may be completed automatically without direct user involvement.

[0088] The user 100 can manipulate the charging cable attached to the energy supply terminal 105 and insert it into the electric vehicle 103. A communication session can then be established between the electric vehicle 103 and the energy supply terminal 105 via the charging cable, the electric vehicle may include a first processor, and the energy supply terminal may include a second processor. The charging cable is suitable for supplying energy from the energy supply terminal 105 to the electric vehicle 103. The first processor in the electric vehicle 103 and the second processor in the energy supply terminal 105 can communicate using a protocol such as ISO 15118 (e.g., ISO 15118-2 or ISO 15118-20). The actions described below with respect to the electric vehicle 103 and the energy supply terminal 105 can be performed by the first processor and the second processor, respectively.

[0089] At step S2, the electric vehicle 103 may transmit a service discovery request to the energy supply terminal 105. The service discovery request may request a list of services available at the energy supply terminal 105.

[0090] In step S4, after receiving the service discovery request from the electric vehicle 103, the energy supply terminal 105 may transmit a service discovery response including an available service list to the electric vehicle 103. For example, the energy supply terminal 105 may indicate that a plurality of applications including an electric vehicle payment application are available.

[0091] At step S6, after receiving the service discovery response from the energy supply terminal 105, the electric vehicle 103 may determine a set of services from the list of available services it supports. After the electric vehicle 103 determines a set of supported services, the electric vehicle 103 may then transmit a service detail request to the energy supply terminal 105. The service detail request may request details associated with one or more services compatible with the electric vehicle 103. In some embodiments, the service detail request may include indicators of one or more compatible services.

[0092] In step S8, after receiving the service details request from the electric vehicle 103, the energy supply terminal 105 may transmit a service details response to the electric vehicle 103. The service details response may include energy supply terminal data (e.g., terminal identifier) ​​and a mobile operator service provider digital certificate associated with the service provider computer 108 and issued by a mobile operator (e.g., such as the above-mentioned certificate authority or sub-institution). The mobile operator service provider digital certificate may include a public key associated with a private key stored at the service provider computer 108, and the service provider computer provides services for a charging network including the energy supply terminal 105. The mobile operator service provider digital certificate may also include other data, such as the data described above according to the term "digital certificate", including the name of the service provider, the date of issue, the validity date, and the digital signature. The electric vehicle 103 may also verify the mobile operator service provider digital certificate by verifying the certificate chain to the root of the certificate authority and by determining whether the mobile operator service provider digital certificate is expired.

[0093] In other words, the electric vehicle 103 will have an integrity-checked copy of the certificate authority root certificate that was previously installed (this may occur during manufacturing or at some point after manufacturing). As described above, the electric vehicle 103 will receive the mobile operator service provider digital certificate in the service details response. If a sub-certificate authority has been used, the mobile operator service provider digital certificate will include a service provider leaf certificate and a sub-certificate authority certificate. If a sub-certificate authority has not yet been used, the mobile operator service provider digital certificate will only contain a service provider leaf certificate. The electric vehicle 103 can verify the certificate chain of the service provider certificate. For example, if there is a sub-certificate authority ID, the electric vehicle 103 can authenticate the service provider leaf certificate to the sub-certificate authority, and then the electric vehicle 103 can authenticate the sub-certificate authority certificate with the certificate authority root. If there is no sub-certificate authority certificate, the electric vehicle 103 can directly authenticate the service provider leaf certificate to the sub-certificate authority.

[0094] In step S10, the electric vehicle 103 may prompt the user (e.g., via a display on the electric vehicle 103, via the user device 102, etc.) to select one or more services from a group of services that are compatible with both the electric vehicle 103 and the energy supply terminal 105. Alternatively, this selection may be automatically performed by the electric vehicle 100 based on pre-established consumer preferences.

[0095] In step S12, after receiving the service detail response from the energy supply terminal 105, the electric vehicle 103 may transmit an interactive service selection request including the selected service(s) to the energy supply terminal 105. In some embodiments, the selected service may be a specific payment service application.

[0096] In step S14, after receiving the interactive service selection request from the electric vehicle 103, the energy supply terminal 105 may transmit an interactive service selection response to the electric vehicle 103. The interactive service selection response may verify the service selection.

[0097] At step S16, after receiving the interactive service selection response from the energy supply terminal 105, the electric vehicle 103 may transmit an interactive detail request including the mobile operator electric vehicle digital certificate to the energy supply terminal 105. In some cases, a contract identifier such as an eMAID may also be present in the interactive detail request. The eMAID may identify the contract associated with the electric vehicle 103 to the energy supply terminal 105. In some cases, the contract identifier may enable the energy supply terminal 105 to provide a specific service to the user of the electric vehicle 103 as a result of the transaction (e.g., reward, data collection, etc.).

[0098] At step S18, after receiving the interaction detail request from the electric vehicle 103, the energy supply terminal 105 can verify the mobile operator electric vehicle digital certificate to determine that it is valid. For example, the energy supply terminal 105 can use the appropriate public key to verify the signature of the certificate authority computer and any sub-certificate authority computer, and can also verify that the certificate is not expired. If the energy supply terminal 105 determines that the mobile operator electric vehicle digital certificate is valid, it can transmit the interaction detail response including the challenge to the electric vehicle 103. In some embodiments, the challenge can be a random number string. Thereafter, the electric vehicle 103 can form a signed challenge by signing the challenge using a private key associated with the public key in the mobile operator electric vehicle digital certificate.

[0099] At step S20, before or after signing the challenge to form a signed challenge, the electric vehicle 103 may provide an interactive data request to the user operating the user device 102. The interactive data request may prompt the user (e.g., via a user interface in the electric vehicle 103 or through the user's mobile phone) to interact the user device 102 with a reader on the electric vehicle 103 so that the electric vehicle 103 can obtain a credential or token from the user device 102. For example, the user device 102 may be a credit card, and the reader in the electric vehicle 103 may be a contact or contactless card reader (e.g., an NFC reader). The reader in the electric vehicle 103 may read the credential or token from a memory in the user device 102.

[0100] In other embodiments, the user need not interact with the user device 102 and the electric vehicle 103. The credential or token may be stored in a memory (eg, a secure element) in the electric vehicle 103 and may be obtained from the memory.

[0101] In other embodiments, the user may select a payment credential or token on his mobile phone, which may be attached to the electric vehicle 103 using Bluetooth, Wi-Fi, or a physical cable. In this case, the credential or token may be obtained from the mobile phone's memory, or may be retrieved by the phone from some Internet-based service, which may be identified using the configuration data received from the energy supply terminal 105 in S8.

[0102] In some embodiments, in response to receiving the interaction detail request, the electric vehicle 103 may determine the amount of charge required to electrically fill a battery in the electric vehicle 103. For example, the electric vehicle 103 may determine the amount of battery capacity available in the battery of the electric vehicle 103 and may determine the amount of charge required to fill it.

[0103] At step S22, the electric vehicle 103 can generate an encrypted data packet by encrypting the interactive data including at least the credential or token and (optionally) the amount of electricity required to fully charge the battery of the electric vehicle 103 with a session key, wherein the session key is derived using an algorithm such as elliptic curve-Diffie Hellman, using a service provider public key obtained from a mobile operator service provider digital certificate. Before doing so, the electric vehicle 103 can verify that the mobile operator service provider digital certificate is valid and authentic. In some embodiments, JWE (JSON Web Encryption) can be used. Then, in step S24, an authorization request message including an encrypted data packet, a challenge, and a signed challenge can be generated by the electric vehicle 103 and then transmitted to the energy supply terminal 105. The message for transmitting the encrypted data packet, the challenge received in S18, and the signed challenge can be a data format compatible with ISO 15118.

[0104] At step S26, after receiving the authorization request message from the electric vehicle 103, the energy supply terminal 105 can verify the signed challenge using the public key in the mobile operator electric vehicle digital certificate. Once the signed challenge is verified, the energy supply terminal 105 can transmit the authorization request message to the service provider computer 108. In other embodiments, the signed challenge can be verified by the service provider computer 108 instead of the energy supply terminal 105.

[0105] At step S28, the service provider computer 108 may decrypt the encrypted interaction data using a session key derived using an algorithm such as Elliptic Curve-Diffie Hellman, using a private key of the service provider computer 108, and using data provided by a JWE created by the electric vehicle 103, to obtain the credential or token and the amount of power required to fully charge the battery of the electric vehicle 103. The service provider computer 108 may then process a transaction for supplying electrical energy to the electric vehicle using at least the credential or token.

[0106] In step S30, the service provider computer 108 may use the amount of power in the authorization request message to estimate the amount of the transaction. In some embodiments, the service provider computer 108 may store a conversion table that correlates the amount of power to various costs, or it may store a conversion factor that allows the service provider computer 108 to calculate costs based on the amount of power. In other embodiments, the amount of the transaction may be simply a fixed cost that will cover fully charging any vehicle battery from empty.

[0107] More specifically, in some embodiments, if the amount of charge obtained by the user is not known when the user provides an account to the energy supply terminal 105, the service provider computer 108 can then determine the pre-authorization amount (e.g., the amount of funds to be reserved for paying for charging the electric vehicle 103). The service provider computer 108 can determine the pre-authorization amount after receiving information about the percentage of battery charge requested or required to fully charge the battery in the electric vehicle 103 and determining the information. For example, the current cost per kilowatt-hour can be multiplied by the estimated amount of charge required to determine the pre-authorization amount. For example, the service provider computer 108 can determine that the pre-authorization amount is $20.00 because the battery in the electric vehicle is 50% full and has 50% of the capacity to be charged. The pre-authorization amount can be included in the authorization request message together with the token or voucher. Then, the service provider computer 108 can process the authorization request message, which can include communicating with the payment processing network to authorize payment. After processing the authorization request, the service provider computer 108 can transmit an authorization response to the energy supply terminal 105 (e.g., it indicates whether the interaction is authorized or not authorized). A hold is then placed in the user's account for the amount of the authorization request. After charging of the electric vehicle 103 is completed, the cost of charging is later determined by the service provider computer 108, and a subsequent message (e.g., another authorization or liquidation message) may be sent to the authorization entity computer with the actual cost of charging, and the previous hold may be released. For example, if the hold is $20 and the actual cost of charging is $10, the hold on the remaining $10 is released.

[0108] In other embodiments, if the charge amount is known, the transaction amount for the charge is included in the authorization request message along with the credential or token.

[0109] The authorization request message generated by the service provider computer 108 may also be converted to a different data format (e.g., from an ISO 15118 or XML type data format to ISO 8583). The service provider computer 108 may then process the authorization request message, which may include communicating with the processing network computer 112 and the authorization entity computer 114 to authorize the payment. After processing the authorization request, the service provider computer 108 may receive an authorization response from the processing network computer 112 and the authorization entity computer 114 indicating whether the transaction is authorized.

[0110] In step S32, the service provider computer 108 may transmit the authorization request message to an authorization entity computer 114 operated by the issuer of the account associated with the credential or token (e.g., via a transmission computer operated by an acquirer and a processing network computer 112 operated by a payment processing network). The authorization request message may be converted to a different data format, such as an ISO 8583 type data format. The authorization entity computer 114 may authorize or deny the transaction and may transmit an authorization response message back to the service provider computer 108 along with the authorization decision.

[0111] If the authorization request message includes a token instead of a credential such as a PAN, the processing network computer 112 may de-tokenize the token to a real PAN and may replace the token with the real PAN before transmitting the authorization request message to the authorization entity computer 114 .

[0112] In step S34, after receiving the authorization response message, the service provider computer 108 may provide the authorization response message, or may provide the authorization response message in a different data format back to the energy supply terminal 105. Then, in step S36, the authorization response message may be transmitted to the electric vehicle 103.

[0113] At step S38, after receiving the authorization response from the energy supply terminal 105, the electric vehicle 103 may transmit a power transfer request to the energy supply terminal 105. The power transfer request may be a request to charge the electric vehicle 103.

[0114] In step S40, after receiving the power transfer request from the electric vehicle 103, the energy supply terminal 105 may transmit a power transfer response to the electric vehicle 103. After receiving the power transfer response from the energy supply terminal 105, the electric vehicle 103 may receive power from the energy supply terminal 105.

[0115] In some embodiments, after the electric vehicle has been charged, a clearing and settlement process may be performed between the payment processing network, the acquirer of the service provider computer, and the issuer of the voucher.

[0116] If the authorization request message to the authorization entity computer is a pre-authorization request message, the actual cost of electricity obtained by the electric vehicle 103 can be included in a subsequent authorization request, where the actual amount can be submitted by the service provider computer 108 and any hold on the user's account due to the pre-authorization request message processing can be released.

[0117] Although the use of the above-described pre-authorization process is described in the context of an electric car having an energy storage unit in the form of a battery, it should be understood that embodiments of the present invention may be used in other contexts. For example, the energy storage unit may be a gas tank in a car. In such embodiments, the car may send a signal to a gas pump (e.g., via short-range wireless communication or via a gas pump) indicating how full the car's gas tank is and indicating the storage capacity of the gas tank. The gas pump may determine how much gas will be needed to fill the gas tank. The gas pump may then send a pre-authorization to an authorization entity computer operated by the issuer of the user's payment device in order to authorize the amount. The hold and release process will be similar to the above process.

[0118] Figure 8 An exemplary communication flow between a user device 804 and a virtual access device 802 on a vehicle 800 is shown in accordance with some embodiments. Figure 8 The steps in Figure 7 This occurs in step S20 of the described flow. The user device 804 may be a payment card, a mobile phone, a secure element in the electric vehicle 103 or the like.

[0119] The virtual access device 802 can be simulated based on, for example, an access device profile obtained from an actual access device such as an actual point of sale (POS) terminal. The communication can be in the form of an application command sent from the virtual access device 802 and an application data response sent from the user device 804 in response to the application command. In some embodiments, the application command and data response can be in the form of APDU commands and responses. However, it should be understood that other messages, messaging protocols or formats can be used to exchange application data for conducting transactions.

[0120] In order to initiate the application data exchange, the virtual access device 802 can initiate the transaction by sending an available application request S802 to the user device 804 to request information about which one or more payment application identifiers (AIDs) are available. Each AID can correspond to an account of the user and / or a processing option associated with the account. In some embodiments, the available application request S802 can be in the form of a select PPSE command. The available application request S802 can include a payment environment identifier (e.g., a PPSE name) to identify the payment environment supported by the virtual access device 802.

[0121] After receiving the available application request S802, the user device 804 can identify and process the request by identifying the payment environment identifier (e.g., PPSE name) included in the request, and respond by sending the available application response S804 back to the virtual access device 802. Available application response S804 may include a list of available AIDs, and may include the payment environment identifier (e.g., PPSE name) as a dedicated file name. In some embodiments, the available application response S804 may be in the form of selecting a PPSE response, and may include PPSE file control information (FCI). For example, the available application response S804 may include a directory entry for each available AID. If the user device 804 only supports one AID, the user device 804 may respond with a single directory entry for the supported AID. If the user device 804 supports an account with multiple AIDs, the transaction application may respond with the directory entry for each supported AID. Each directory entry may include, for example, the following information: an AID, an application tag associated with the AID (e.g., a mnemonic associated with the AID), an application priority indicator indicating the priority of the AID, a kernel identifier indicating the kernel preference of the application, and / or additional information related to the specific AID. Available Application Response S804 may also include other data such as FCI issuer discretionary data.

[0122] When the virtual access device 802 receives the available application response S804, the virtual access device 802 may select a suitable application from the application list received in the available application response S804 (e.g., by selecting an AID from the available AIDs received in the available application response S804). In some embodiments, the selected AID may be the highest priority AID on the prioritized list of application identifiers supported by the access device simulated by the virtual access device 802. The prioritized list of application identifiers may be obtained as part of the access device profile. The virtual access device 802 may send an application selection S806 with the selected AID to the user device 804 to continue the transaction. In some embodiments, the application selection S806 may be in the form of a select AID command.

[0123] When receiving application selection S808, user device 804 can send terminal transaction data request 808, to request transaction data from virtual access device 802, to perform transaction using selected application / AID.In some embodiments, terminal transaction data request S808 can be in the form of selecting AID response, and can include AID file control information (FCI) with selected AID as special file name.Terminal transaction data request S808 can include a list of transaction data identifiers for requesting appropriate data from virtual access device 802, and the list of transaction data identifiers can be in the form of processing option data object list (PDOL).The transaction data requested by user device 804 for exchange can include terminal transaction qualifier (TTQ), authorization amount, other amounts, terminal country code, terminal verification result, transaction currency code, transaction data, transaction type and / or unpredictable numbers.Terminal transaction data request 808 can also include other data, such as FCI issuer discretionary data, application identifier and language preference.

[0124] After receiving the terminal transaction data request 808, the virtual access device 802 may send the terminal transaction data S810 requested by the user device 804 to the user device 804. The terminal transaction data S810 provided by the virtual access device 802 may be obtained from the access device configuration file. In some embodiments, the terminal transaction data 810 may be sent in the form of a Get Processing Options (GPO) command, and may include the terminal transaction data requested in the Processing Options Data Object List (PDOL). In some embodiments, the terminal transaction data S810 (e.g., a terminal transaction qualifier (TTQ)) may include a transaction type indicator indicating a transaction type supported by the access device. In some embodiments, the terminal transaction data S810 (e.g., a terminal transaction qualifier TTQ)) may also include a CVM requirement indicator to indicate whether the access device requires a consumer verification method (CVM) for the transaction, and also include one or more CVM type indicators indicating the CVM type supported by the access device. Examples of CVMs that may be supported by the access device may include online PINs, signatures, and / or consumer device CVMs (CDCVMs) such as passwords to unlock a screen or user device 804.

[0125] Once the user device 804 receives the terminal transaction data S810, the user device 804 may increment its application transaction counter (ATC), use at least some of the received terminal transaction data 810 to generate dynamic transaction processing information, and send a set of transaction processing information S812 including the generated dynamic transaction processing information to the virtual access device 802. In some embodiments, the transaction processing information S812 may be sent in the form of a GPO response. In some embodiments, the transaction processing information S812 may include one or more application file locators (AFLs) that may be used by the virtual access device 802 as file addresses to read account data stored on the user device 804, and application interaction features (AIPs) that may be used to indicate the capabilities of the user device 804.

[0126] In some embodiments, the AFL included in the transaction processing information S812 may include a file address for reading account data, such as a transaction cryptogram dynamically generated from an access device using a limited use key (LUK) and / or an unpredictable number, including Track-2 equivalent data of a token or PAN, and additional data such as issuer application data (IAD), form factor indicator (FFI), card transaction qualifier (CTQ), cryptographic information data (CID), updated ATC, and / or application PAN sequence number (PSN). In some embodiments, the issuer application data (IAD) may include a length indicator indicating the length of the IAD, a cryptographic version number (CVN) indicating the version of the transaction cryptogram, a derived key indicator (DKI) that can be used to identify a master key (e.g., a master key associated with an issuer used when generating a LUK), a card verification result (CVR), a wallet provider ID, and / or derived data, such as a key index used when generating a LUK. In some embodiments, the transaction processing information S812 may include the above-mentioned account data itself, rather than its corresponding AFL or a combination thereof. It should be understood that in some embodiments, the transaction processing information S812 sent from the user device 804 to the virtual access device 802 may include some or all of the information described above, and in some embodiments, may include additional information not specifically described.

[0127] After the virtual access device 802 receives the transaction processing information S812, the virtual access device 802 may send an account data request S814 to the user device 804 to read additional account data that may be stored on the user device 804. In some embodiments, the account data request S814 may be in the form of a read record command and may include an application file locator (AFL) indicating the location of the account data that the virtual access device 802 is attempting to read. The AFL included in the account data request S814 may correspond to the AFL in the transaction processing information S812 provided from the user device 804 to the virtual access device 802.

[0128] In response to receiving the account data request S814 from the virtual access device 802, the user device 804 may send the account data 816 stored at the location indicated by the AFL to the virtual access device 802. In some embodiments, the account data 816 may be sent in the form of a read record response. The account data 816 may include, for example, the account data elements discussed above (e.g., PAN, token, CVV, etc.) and / or application usage controls indicating the issuer's restrictions on the use and services allowed by the application, the cardholder's name, customer-specific data, the issuer country code, the token requester ID (e.g., in the case of using a token), and / or other account-related data accessible at the AFL location. It should be understood that in some embodiments, the account data 816 sent from the user device 804 to the virtual access device 802 may include some or all of the information described above, and in some embodiments, may include additional information not specifically described.

[0129] In some embodiments, there may be more than one pair of account data request S814 and account data 816 communication exchanges between the virtual access device 802 and the user device 804. Once the virtual access device 802 has received the required data from the transaction processing information S812 and / or one or more account data 816 transmissions, some or all of the data elements in the transaction processing information S812 and / or one or more account data 816 transmissions may be concatenated by the virtual access device 802 to form a data packet. The data packet may include a checksum, and a data packet length indicator to indicate the length of the data packet. The data packet may be used by the virtual access device to generate a transaction authorization request message to request authorization of a transaction from an issuer. For example, in some embodiments, the transaction authorization request message may include at least Track-2 equivalent data (including a token or PAN) and a transaction cryptogram generated using a LUK, and may authorize the transaction based at least on verifying that the transaction cryptogram was correctly generated and that the LUK used to generate the transaction cryptogram has not exhausted the LUK set of one or more limited usage thresholds.

[0130] Other embodiments of the invention may include other devices, computers, and methods.

[0131] Another embodiment of the present invention includes a method, comprising: establishing a communication session between a vehicle including a first processor and an energy supply terminal including a second processor via a cable, the cable being suitable for supplying energy from the energy supply terminal to the vehicle; for the energy supply cable, receiving an encrypted data packet including the credential or token from the vehicle by the energy supply terminal; and transmitting the encrypted data packet to a service provider computer by the energy supply terminal, the service provider computer decrypting the encrypted data packet to obtain the credential or token, and then using the credential or the token to process a transaction for supplying energy to the vehicle.

[0132] Another embodiment of the present invention includes an energy supply terminal, comprising: a processor; and a computer-readable medium coupled to the processor, the computer-readable medium including code for causing the processor to perform operations, the operations including: establishing a communication session between a vehicle including a first processor and the energy supply terminal via a cable, the cable being suitable for supplying energy from the energy supply terminal to the vehicle; for an energy supply cable, receiving an encrypted data packet including the credential or token from the vehicle by the energy supply terminal; and transmitting the encrypted data packet to a service provider computer by the energy supply terminal, the service provider computer decrypting the encrypted data packet to obtain the credential or token, and then using the credential or token to process a transaction for supplying energy to the vehicle.

[0133] Embodiments of the present invention provide several technical advantages. Using embodiments of the present invention, the energy supply terminal does not need to be modified with dedicated hardware or software so that the user can conveniently obtain energy for the user's vehicle from the energy supply terminal. In addition, in the context of electric vehicle charging, when charging the electric vehicle, the user can simply "plug and play". In some embodiments, the user does not need to take active steps to pay for the charging of the user's vehicle. In addition, sensitive data such as payment credentials and payment tokens are protected when they are passed from the electric vehicle to the service provider computer. Therefore, there is no need to provide special software and hardware for the energy supply terminal (e.g., charging station) to provide data security for sensitive data.

[0134] Other embodiments have advantages including allowing the user of the vehicle to pre-authorize an amount more accurately based on the amount of energy they may actually obtain. The benefit of doing so is that when obtaining energy for the user's vehicle, there is no need to unnecessarily hold an excess amount in the user's account.

[0135] Any software component or function described in this application can be implemented as a software code executed by a processor using any suitable computer language such as Java, C, C++, C#, Objective-C, Swift or a scripting language such as Perl or Python using, for example, conventional or object-oriented techniques. The software code can be stored as a series of instructions or commands on a computer-readable medium for storage and / or transmission, and suitable media include random access memory (RAM), read-only memory (ROM), magnetic media such as a hard drive or floppy disk, or optical media such as a compact disk (CD) or a digital versatile disk (DVD), flash memory, etc. The computer-readable medium can be any combination of such storage devices or transmission devices.

[0136] Such programs can also be encoded and transmitted using carrier signals suitable for transmission via wired networks, optical networks and / or wireless networks that meet multiple protocols, including the Internet. Therefore, the computer-readable medium according to an embodiment of the present invention can be created using data signals encoded with such programs. The computer-readable medium encoded with program code can be encapsulated with compatible devices or (for example, downloaded via the Internet) provided separately from other devices. Any such computer-readable medium can reside on or within a single computer product (for example, a hard drive, a CD or an entire computer system), and can be present on or within different computer products in a system or network. The computer system can include a monitor, a printer, or other suitable displays for providing any result mentioned herein to the user.

[0137] The above description is illustrative rather than restrictive. After reading this disclosure, many variations of the present invention will become apparent to those skilled in the art. Therefore, the scope of the present invention should not be determined with reference to the above description, but should be determined with reference to the pending claims together with their full scope or equivalents.

[0138] One or more features of any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the present invention.

[0139] As used herein, the use of "a," "an," or "the" is intended to mean "at least one" unless clearly indicated to the contrary.

Claims

1. A method, include: establishing a communication session between a vehicle including a first processor and an energy supply terminal including a second processor; obtaining, by said first processor in said vehicle, a credential or token, generating, by the first processor in the vehicle, an encrypted data packet including the credential or token; as well as The encrypted data packet is provided by the first processor in the vehicle to the energy supply terminal, wherein the energy supply terminal transmits the encrypted data packet to a service provider computer, the service provider computer decrypts the encrypted data packet to obtain the credential or token, and then uses the credential or the token to process a transaction for supplying energy to the vehicle.

2. The method of claim 1 , wherein the energy is electrical energy, the vehicle is an electric vehicle including a battery system, the battery system includes a battery, the energy supply terminal is an electrical energy supply terminal, and wherein the communication session between the vehicle and the energy supply terminal is via a cable in the form of a charging cable, and the encrypted data packet is provided by the first processor in the vehicle to the energy supply terminal via the charging cable.

3. The method of claim 2, wherein the service provider computer processes the transaction by generating an authorization request message including the credential or token and a value associated with supplying the electrical energy to the electric vehicle. The method according to claim 3 , wherein the electric vehicle is an electric car.

5. The method according to claim 2, wherein obtaining the credential or the token include: The credential or the token is received from a user device held by a user of the electric vehicle.

6. The method according to claim 2, wherein obtaining the credential or the token include: The credential or the token is retrieved from a memory in a user device separate from the electric vehicle.

7. The method of claim 2, further comprising, before obtaining the credential or token: The electric vehicle transmits a service discovery request to the electric energy supply terminal; receiving, by the electric vehicle, a service discovery response including a list of available services from the electric energy supply terminal; determining, by the electric vehicle, a set of services in the list of available services, wherein the set of services includes services supported by the electric vehicle; transmitting, by the electric vehicle to the electric energy supply terminal, a service details request including an indicator of the set of services; receiving, by the electric vehicle, a service details response from the power supply terminal, the service details response including power supply terminal data and a service provider computer digital certificate associated with a service provider computer in communication with the power supply terminal; transmitting, by the electric vehicle to the electric energy supply terminal, a service selection request including a service in the group of services; receiving, by the electric vehicle, a service selection response from the electric energy supply terminal; The electric vehicle transmits an interaction detail request including the electric vehicle digital certificate to the electric energy supply terminal; receiving, by the electric vehicle, an interaction detail response including a challenge from the electric energy supply terminal; and The challenge is signed by the electric vehicle using a private key associated with a public key in the electric vehicle digital certificate to form a signed challenge.

8. A method according to claim 7, wherein providing the encrypted data packet to the power supply terminal via the cable includes providing an authorization request message including the encrypted data packet to the power supply terminal, wherein the power supply terminal transmits the authorization request message including the encrypted data packet and the signed challenge to the service provider computer, the service provider computer decrypts the encrypted data packet to obtain the credential or token, and then processes the transaction for supplying energy to the electric vehicle by modifying the authorization request message to include the credential or the token and transmitting the modified authorization request message to the authorization entity computer for authorization.

9. The method of claim 8, wherein the authorization request message further includes an estimated amount of charge to be filled in the battery as determined by the electric vehicle.

10. The method according to claim 8, further comprising: include: The electric vehicle and the electric energy supply terminal receive a transaction response to the authorization request message; as well as The electric vehicle receives electric energy from the electric energy supply terminal.

11. The method of claim 2, wherein providing the encrypted data packet to the power supply terminal via the cable comprises providing an authorization request message including the encrypted data packet to the power supply terminal, wherein the power supply terminal transmits the authorization request message including the encrypted data packet and a signed challenge to the service provider computer, the service provider computer decrypts the encrypted data packet to obtain the credential or token, and then processes the transaction for supplying energy to the electric vehicle by modifying the authorization request message to include the credential or token and transmitting the modified authorization request message to an authorization entity computer for authorization.

12. The method of claim 2, wherein providing the encrypted data packet to the power supply terminal via the cable comprises providing an authorization request message including the encrypted data packet to the power supply terminal, wherein the power supply terminal transmits the authorization request message including the encrypted data packet and the signed challenge to the service provider computer, the service provider computer decrypts the encrypted data packet to obtain the credential or token, and then processes the transaction for supplying energy to the electric vehicle by modifying the authorization request message to include the credential or token and transmitting the modified authorization request message to an authorization entity computer for authorization, and wherein the method further include: The authorization request message is generated by a virtual access application in the electric vehicle.

13. The method of claim 12, wherein the virtual access application interacts with a user device external to the electric vehicle to obtain the credential or the token. The method of claim 2 , wherein the token is obtained.

15. A vehicle, include: a first processor; as well as A computer readable medium comprising code executable by the first processor to cause the first processor to perform operations comprising: establishing a communication session between the vehicle and an energy supply terminal including a second processor; Get a credential or token, generating an encrypted data packet including the credential or token; and The encrypted data packet is provided to the energy supply terminal.

16. The vehicle of claim 15, wherein the energy is electrical energy, the vehicle is an electric vehicle including a battery system, the battery system includes a battery, the energy supply terminal is an electrical energy supply terminal, and wherein the communication session is conducted via a cable, the cable is a charging cable, and the encrypted data packet is provided by the first processor in the vehicle to the energy supply terminal via the charging cable.

17. The vehicle of claim 16, wherein providing the encrypted data packet to the power supply terminal via the cable comprises providing an authorization request message including the encrypted data packet to the power supply terminal, and wherein the operation further comprises: include: The authorization request message is generated by a virtual access application on the computer-readable medium in the vehicle.

18. The vehicle of claim 16, wherein the operation further include: receiving a transaction from the power supply terminal; as well as The electric vehicle receives electric energy from the electric energy supply terminal.

19. A method, include: receiving, by a service provider computer, an encrypted data packet from a vehicle via an energy supply terminal; decrypting, by the service provider computer, the encrypted data packet to obtain a credential or token; as well as A transaction for supplying energy to the vehicle is processed using the credential or the token.

20. The method of claim 19, wherein the energy is electrical energy, the vehicle is an electric vehicle comprising a battery system, the battery system comprises a battery, the energy supply terminal is an electrical energy supply terminal, and wherein the encrypted data packet is received from the vehicle via a cable, the cable being a charging cable.

21. A method, include: determining, by a processor, a remaining capacity of an energy storage unit in the vehicle; determining, by the processor, a transaction amount required to fill a remaining capacity of the energy storage unit; generating, by the processor, an authorization request message including a token or a credential and including the transaction amount; as well as The processor transmits the authorization request message to an authorization entity computer for authorization.

22. The method of claim 21, wherein the processor is in an energy supply terminal or a service provider computer.

23. The method of claim 21, wherein the energy storage unit is a battery and the vehicle is an electric vehicle.

24. The method according to claim 23, wherein the remaining capacity of the energy storage unit is determined by analyzing a message from the vehicle comprising data regarding the remaining capacity of the energy storage unit.

25. The method according to claim 24, wherein the data on the remaining capacity of the energy storage unit is the amount of electricity to be supplied to the battery in the electric vehicle so that the battery is fully charged.

26. A computer, include: processor; as well as A computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor for performing operations comprising: determining a remaining capacity of an energy storage unit in the vehicle; determining a transaction amount required to fill the remaining capacity of the energy storage unit; generating an authorization request message including the token or credential and including the transaction amount; and The authorization request message is transmitted to an authorization entity computer for authorization.

27. The computer of claim 26, wherein the energy storage unit is a battery in the vehicle.

28. The computer according to claim 26, further comprising: include: A message is received from the vehicle via an energy supply terminal, the message comprising the token or the credential and the remaining capacity of the energy storage unit.

29. A method, include: issuing, by the certificate authority computer, a first sub-root key pair to a first sub-entity computer, wherein the first sub-entity computer thereafter issues a mobile operator electric vehicle digital certificate including an electric vehicle public key to the electric vehicle; and The certificate authority computer issues a second sub-root key pair to a second sub-entity computer, wherein the second sub-entity computer then issues a mobile operator service provider digital certificate including a service provider public key to a service provider associated with the energy supply terminal.

30. A certificate authority computer, include: processor; as well as A computer readable medium comprising code executable by the processor for performing operations comprising: issuing a first sub-root key pair to a first sub-entity computer, wherein the first sub-entity computer thereafter issues a mobile operator electric vehicle digital certificate including an electric vehicle public key to the electric vehicle; as well as A second sub-root key pair is issued to a second sub-entity computer, wherein the second sub-entity computer thereafter issues a mobile operator service provider digital certificate including a service provider public key to a service provider associated with the energy supply terminal.