WO2022170333A9

WO2022170333A9 - Secure electric vehicle charging

Info

Publication number: WO2022170333A9
Application number: PCT/US2022/070502
Authority: WO
Inventors: Nikhil Srinath BHARADWAJ
Original assignee: Eve Energy Ventures Inc.
Priority date: 2021-02-04
Filing date: 2022-02-03
Publication date: 2023-06-08
Also published as: CL2023002302A1; WO2022170333A1; CA3206498A1; DE112022000922T5; EP4289156A1

Abstract

Systems and methods for secure electric vehicle (EV) charging are provided. One embodiment includes an EV charger, where the EV charger includes a power management unit, a processor, a low power short range point-to-point communication system, a memory containing machine readable instructions, where the processor is configured by the machine readable instructions to receive an authentication request from a mobile device via the low power short range point-to-point communication system, send encrypted EV charger access credentials to the mobile device, receive a digital token from the mobile device, verify the digital token, and initiate a charging session based upon a command contained within the digital token.

Description

SECURE ELECTRIC VEHICLE CHARGING

CROSS-REFRENCE TO RELATED APPLICATIONS

[0001] The current application claims priority to U.S. Provisional Patent Application No. 63/145,850, entitled “Secure Electric Vehicle Charging” and filed February 4, 2021. The disclosure of U.S. Provisional Patent Application No. 63/145,850 is incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

[0002] The invention generally relates to electric vehicle charging and more specifically relates to systems and methods for secure electric vehicle charging.

BACKGROUND

[0003] An incredible amount of infrastructure is relied upon to transport electricity from power stations, where the majority of electricity is currently generated, to where it is consumed by individuals. Power stations can generate electricity in a number of ways including using fossil fuels or using renewable energy sources such as solar, wind, and hydroelectric sources. Substations typically do not generate electricity, but can change the voltage level of the electricity as well as provide protection to other grid infrastructure during faults and outages. From here, the electricity travels over distribution lines to bring electricity to locations where it is consumed such as homes, businesses, and schools. The term "smart grid" describes a new approach to power distribution which leverages advanced technology to track and manage the distribution of electricity. A smart grid can be created by applying upgrades to existing power grid infrastructure including the addition of more renewable energy sources, advanced smart meters that digitally record power usage in real time, and bidirectional energy flow that enables the generation and storage of energy in additional places throughout the electric grid.

[0004] Electric vehicles (EVs), which include plug-in hybrid electric vehicles (PHEVs), can use an electric motor for propulsion. EV adoption has been spurred by federal, state, and local government policies providing various incentives (e.g. rebates, fast lanes, parking, etc.). Continued EV adoption is likely to have a significant impact on the future smart grid due to the additional stress load that EVs add to the grid (an EV’s power demand can be many times that of an average residential house). Cost inefficiencies in deployment of electrical vehicle supply equipment (EVSE) infrastructure and service panel capacity restrictions can lead to situations where there are too few chargers and too many drivers, which can cut into EV drivers’ satisfaction and impede ownership growth rates of EVs.

SUMMARY OF THE INVENTION

[0005] Systems and methods for secure electric vehicle (EV) charging are illustrated. One embodiment includes a system for electric vehicle (EV) charging, the system including: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to-point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, and store, in the memory, first charging session data for the first charging session, wherein the digital token is encrypted using a public key and is self-authenticating without use of an internet connection.

[0006] A further embodiment includes a system for electric vehicle (EV) charging, the system including: an EV charger including a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to-point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, store, in the memory, first charging session data for the first charging session, authenticate a second mobile device via the low power short range point-to-point communication system, cause the storing of at least the first charging session data on the second mobile device for forwarding, initiate a second charging session, end the second charging session, and store, in the memory, second charging session data for the second charging session.

[0007] A further embodiment includes a system for electric vehicle (EV) charging, the system including: an EV charger including a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: receive an authentication request from a first mobile device via the low power short range point- to-point communication system, authenticate the first mobile device via the low power short range point-to-point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token by decrypting the digital token using cryptographic information contained within a digital certificate, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, store, in the memory, first charging session data for the first charging session, wherein the digital token is bound to a specific time period, is encrypted using a public key, and is self-authenticating without use of an internet connection, authenticate a second mobile device via the low power short range point-to- point communication system, cause the first charging session data to be sent to the second mobile device via the low power short range point-to-point communication system, initiate a second charging session, end the second charging session, store, in the memory, second charging session data for the second charging session, cause the second charging session data to be sent to the second mobile device via the low power short range point-to-point communication system, and use mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

[0008] A further embodiment includes an EV charger, where the EV charger includes a power management unit, a processor, a low power short range point-to-point communication system, a memory containing an authentication software application, where the processor is configured by the authentication software application to receive an authentication request from a mobile device via the low power short range point-to- point communication system, send encrypted EV charger access credentials to the mobile device, receive a digital token from the mobile device, verify the digital token, and initiate a charging session based upon a command contained within the digital token.

[0009] In another embodiment, the EV charger’s memory includes a digital certificate including cryptographic information.

[0010] In a further embodiment, the authentication request from the mobile device includes an encrypted challenge.

[0011] In still another embodiment, the EV charger access credentials include charger ID, time of day, and session time.

[0012] In a still further embodiment, the verification of the digital token is performed by decrypting the digital token using cryptographic information contained within the digital certificate.

[0013] In yet another embodiment, the processor is further configured by the authentication software application to collect charging session data.

[0014] In a yet further embodiment, the processor is further configured by the authentication software application to send the charging session data to the mobile device via the low power short range point-to-point communication system.

[0015] In another additional embodiment, the charging session data includes duration of the charging session, energy used during the charging session, and a plug-in status.

[0016] In a further additional embodiment, the charging session data further includes a status of the EV charger, diagnostics data, temperature data and humidity data. [0017] In another embodiment again, the digital token is bound to a specific time period.

[0018] In a further embodiment again, the low power short range point-to-point communication system is a near field communication (NFC) system.

[0019] In still yet another embodiment, the processor is configured by the authentication software application to receive a second communication from the user’s mobile device via the NFC system.

[0020] In a still yet further embodiment, the second communication includes an encrypted message to end the charging session.

[0021] In still another additional embodiment, the processor is configured by the authentication software application to decrypt the second communication message and to end the charging session.

[0022] In a still further additional embodiment, the EV charger further includes a locking mechanism, and the processor is further configured by the authentication software application to release the locking mechanism upon ending the charging session.

[0023] In still another embodiment again, a system for EV charging includes an EV charger where the EV charger includes a power management unit; a processor; a low power short range point-to-point communication system; and a memory including an authentication software application; where the processor is configured by the authentication software application to: receive an authentication request from a mobile device via the low power short range point-to-point communication system; send encrypted EV charger access credentials to the mobile device; receive a digital token from the mobile device; verify the digital token; and initiate a charging session based upon a command contained within the digital token; a mobile device comprising a mobile device processor and a mobile device memory containing a mobile device authentication software application; where the mobile device processor is configured by the mobile device authentication software application to: send an authentication request to the EV charger via the low power short range point-to-point communication system; receive encrypted EV charger access credentials from the EV charger; and send a digital token to the EV charger. [0024] In a still further embodiment again, in the EV charging system, the EV charger processor is further configured by the authentication software application to collect charging session data and to send the charging session data to the mobile device via the low power short range point-to-point communication system.

[0025] In yet another additional embodiment, in the EV charging system, the charging session data includes duration of the charging session, energy used during the charging session; plug-in status, status of the EV charger, diagnostics data, temperature and humidity.

[0026] In a yet further additional embodiment, the EV charging system further includes a server, where the mobile device processor is configured by the mobile device authentication software application to communicate with the server when a network connection with the server is present.

[0027] In yet another embodiment again, in the EV charging system the mobile device processor is configured by the mobile device authentication software application to send the charging session data to the server.

BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The description and claims will be more fully understood with reference to the following figures and data graphs, which are presented as exemplary embodiments of the invention and should not be construed as a complete recitation of the scope of the invention.

[0029] Fig. 1 is a diagram conceptually illustrating a power distribution network in accordance with an embodiment of the invention.

[0030] Fig. 2 is a diagram conceptually illustrating systems and methods for secure electric vehicle charging in accordance with an embodiment of the invention.

[0031] Fig. 3 is a diagram of a server with a charging protocol application used in systems and methods for secure electric vehicle charging in accordance with an embodiment of the invention. [0032] Fig. 4 is a diagram of a mobile device with an authentication application used in systems and methods for electric vehicle charging in accordance with an embodiment of the invention.

[0033] Fig. 5 is a diagram of an EV charger device with an authentication application and an optional near field communication (NFC) used in systems and methods for secure electric vehicle charging in accordance with an embodiment of the invention.

[0034] Fig. 6 is a diagram of an EV charger NFC system-on-chip (SoC) in accordance with an embodiment of the invention.

[0035] Fig. 7 illustrates an authentication process in accordance with an embodiment of the invention.

[0036] Fig. 8 is a flow chart illustrating an authentication process performed on a mobile device in accordance with an embodiment of the invention.

[0037] Fig. 9 is a flow chart illustrating an authentication process performed on an EV charger in accordance with an embodiment of the invention.

[0038] Fig. 10 is a flow chart illustrating an authentication process performed on a server system in accordance with an embodiment of the invention.

[0039] Fig. 11 shows a revolving authentication diagram of scheduled sessions in accordance with an embodiment of the invention.

[0040] Figs. 12A-12D show screen shots of a user interface of an application used in systems and methods for secure electric vehicle charging in accordance with an embodiment of the invention.

[0041] Figs. 13A-13B show screen shots of a user interface of an application used in systems and methods for secure electric vehicle charging showing a map with public charger location and availability in accordance with an embodiment of the invention.

[0042] Figs. 14A-14B show screen shots of a user interface of an application used in systems and methods for secure electric vehicle charging showing a map with private charger location and availability in accordance with an embodiment of the invention.

[0043] Fig. 15 illustrates a firmware update process in accordance with an embodiment of the invention. [0044] Fig. 16 is a flow chart illustrating a firmware update process performed by an EV charger in accordance with an embodiment of the invention.

[0045] Fig. 17 is a flow chart illustrating an EV charger firmware update process performed by a mobile device in accordance with an embodiment of the invention.

[0046] Fig. 18 is a flow chart illustrating an EV charger firmware update process performed by a server system in accordance with an embodiment of the invention.

[0047] Fig. 19 illustrates a load management process in accordance with an embodiment of the invention.

[0048] Fig. 20 is a flow chart illustrating a load management process performed by a server system in accordance with an embodiment of the invention.

[0049] Fig. 21 is a flow chart illustrating a load management process performed by a mobile device in accordance with an embodiment of the invention.

[0050] Fig. 22 illustrates an overview of a system for secure electric vehicle charging, where an EV charger possesses a network connection in accordance with an embodiment of the invention.

[0051] Fig. 23 illustrates a networked set of EV chargers in accordance with an embodiment of the invention.

[0052] Fig. 24A illustrates a process for sending charging session data to a server in accordance with an embodiment of the invention.

[0053] Fig. 24B illustrates a process for sending charging session data to a server in accordance with an embodiment of the invention.

[0054] Fig. 25 illustrates an EV charger hardware schematic diagram in accordance with an embodiment of the invention.

[0055] Figs. 26A and 26B illustrate schematic representations for an embedded security system in accordance with an embodiment of the invention.

DETAILED DESCRIPTION

[0056] Turning now to the drawings, systems and methods for secure electric vehicle charging in accordance with various embodiments of the invention are illustrated. In numerous embodiments, systems and methods for secure electric vehicle charging can include methods for installing and enabling EV chargers at sites where a network connection is not available. In various embodiments, systems and methods for secure electric vehicle charging can include an electric vehicle supply equipment (EVSE), which can interact with EVs and/or EV drivers’ mobile devices via a low power short range point- to-point communication system such as (but not limited to) a near field communication (NFC) system. It will be understood by those skilled in the art the mobile devices can include any of a variety of mobile devices capable of communicating via a wide area network (e.g. a cellular data network) and a low power point-to-point communication system including (but not limited to) wearable mobile devices such as wearable smart watches. In many embodiments, the electric vehicle itself can communicate with an electric vehicle charger directly via a low power short range point-to-point communication system such as (but not limited to) a near field communication (NFC) system. In certain embodiments, systems and methods for secure electric vehicle charging can include an EV charger communicating with an EV via the power charger instead of and/or in addition to using wireless communication.

[0057] Deployment of EV chargers in some environments can be challenging since a network connection may not be available in those environments, for example it could be difficult to establish network connections in underground parking garages. Therefore, neither the EV charger nor a mobile device communicating with the EV charger may be able to establish an internet connection at the time the EV charger is attempting to authenticate the mobile device. In some environments, it can be cost prohibitive to bring in a reliable network. For example, it can be expensive to bring in a reliable network in rural areas or a dense urban setting. Even if a reliable network can be brought in, the reliability of the network can still be a problem. EV charging companies can lose revenue because of lost charging session data due to unreliable networks causing lost data packets.

[0058] In many embodiments, systems and methods for secure electric vehicle charging can include a user authentication process without the need for the presence of a network connection. In certain embodiments, the authentication process can enable an EV operator’s mobile device to authenticate itself to an EV charger and enable the EV charger to deliver encrypted access credentials to an EV operator’s mobile device via a low power short range point-to-point communication system such as (but not limited to) an NFC system, enabling a charging session for the EV without the presence of a network connection. Systems and methods for secure EV charging can, for example, enable a charging session for an electric vehicle where an EV charger may be installed in an underground parking lot, where internet connection may not be available to either the EV charger or the EV operator’s mobile device. In many embodiments, systems and methods for secure EV charging can reduce (or eliminate) latency due to network communications. For example, latency in commencing a charging session can be reduced by a factor of 50 by eliminating delays associated with communications between an EV charger and a remote server over a wide area network. In numerous embodiments, systems and methods for secure EV charging can reduce the cost of installation of an EV charger by enabling installation of the EV charger close to a power panel where a network connection may not be available.

[0059] In several embodiments, the charging session data can be stored locally on the mobile device when no network connection is available. In many embodiments, systems and methods for secure EV charging can enable buffering of the data transmitted from the EV charger to the mobile device, where the data is stored on the mobile device and is then transmitted to a server once a network connection is restored. In certain embodiments, the data can also include data from previous sessions. In this way, data from multiple charging sessions can be uploaded to the server when a single mobile device establishes a network connection with the server. In the case of a private network with a dedicated charging station where only one driver is mapped to be able to use it, the charger ledger session data can be shared as a unified macro ledger across many EV chargers utilizing a mesh network such as a Bluetooth Low Energy (BLE) mesh networks. In some embodiments, charging session data from previous charging sessions may be sent through a mobile device executing a subsequent charging session. Examples where previous charging session data may be sent through other mobile devices are described in connection with Fig. 24A below. [0060] In various embodiments, systems and methods for secure EV charging can include a feature where the EV operator’s mobile device can communicate with a server in order to obtain an encrypted payload from the server for a charging session. In numerous embodiments, the payload can include data such as the name of an EV charger, updated time, an authentication challenge, as well as firmware updates. The payload may also include data to start and stop a charging session, and collect charging session data. In many embodiments, the payload may be bound to a specific time period and/or time slot on a specific EV charger or array of EV chargers. In several embodiments, when a charging session is initiated and a mobile device has communicated with an EV charger, the mobile device can then gain access to an access management system (AMS) residing on a server. In certain embodiments, the EV charger and the EV operator’s user identification (user ID) can be verified against a database which is maintained on the server. In many embodiments, when the verification has been successfully completed, an encrypted payload can be sent from the server to the mobile device. In several embodiments, the mobile device can send the encrypted payload to the EV charger via a low power short range point-to-point communication system such as (but not limited to) an NFC system in order to initiate a charge. In numerous embodiments, upon completion of the charging session, systems and methods for secure electric vehicle charging can enable an EV operator to end the session by tapping on a user interface of the software application. The charging session data can be retrieved from the EV charger by the mobile device to log the details of the charging session. As is discussed further below, a charging session can be ended without requiring the EV operator to interact with a software application.

[0061] In many embodiments, data such as an EV charger location access levels as well as a ledger with available credits and an encrypted payload to start/stop a charging session and the EV operator’s user ID can be communicated via the short-range point- to-point communication system and stored locally on the user’s mobile device. This data can be updated after every charging session. In several embodiments, pre-downloaded ledger data can enable systems and methods for secure EV charging to perform properly without a network connection or where the network connection is unreliable. In certain embodiments, status or authentication levels such as the ledger balance and/or the EV charger location access can be shared with a server, while utilizing a “listener” mode for reconnecting to a user’s mobile device over a network (e.g. a Wi-Fi network). In several embodiments, the data verification can be performed using an access management system residing on a server in real time if the user’s mobile device is online. Upon acceptance of data across all layers, a new payload can be sent in order to enable a charging session. In some embodiments, a reload of balance or credit can be performed over the internet when the user mobile device is connected to the internet. Systems and methods for secure EV charging can set up a negative debit ledger locally in order to account for the updated balance.

[0062] In several embodiments, authentication can be performed against locally stored data if a user’s mobile device is offline. The EV charger can be pre-loaded with a digital certificate. In a number of embodiments, the digital certificate can include cryptographic information such as (but not limited to) a public and private key pair. Upon acceptance of the data, a pre-authorized token can be utilized to enable a charging session. In some embodiments, pre-authorized data may include validity and expiration date information such that charging sessions can be limited until the expiration date or until the calculated energy use/cost has been reached. In cases where a location was added offline or a credit balance is below a threshold, the user may establish a network connection to the server.

[0063] In many embodiments, in a shared public setting, access can be authenticated by a server, or authenticated locally in order to enable a charging session for a user. In several embodiments, in a private setting, the authentication can be performed using an EV operator’s user ID and the EV charger’s cache. In these settings, the balance/credit authentication can be performed in their entirety. In some embodiments, in a public setting both location and the EV operator’s user ID authentication can be bypassed and the balance/credit authentication can be the only verification performed.

[0064] In several embodiments, systems and methods for secure EV charging can maintain local intelligence settings that can be updated over several payloads of charging sessions. These local intelligence settings can include location hour settings, pricing per hour or kWh setting, and user ID. In certain embodiments, when an EV charger is in use or reserved by a revolving time-based authorization, the charger may not respond to new charging requests. In some embodiments, a time-based authorization can be performed in order to accept or deny a charging session request if the request is received outside the EV charger’s location hours.

[0065] In many embodiments, systems and methods for secure electric vehicle charging can deliver firmware updates to an EV charger via multiple communications with one or more mobile devices, each communication carrying a piece of the firmware. In several embodiments, a server can break up the firmware into multiple pieces and send those pieces to an EV operator’s mobile device. In certain embodiments, the mobile device can send the firmware pieces to the EV charger via a low power short range point- to-point communication system such as (but not limited to) NFC system by breaking up the firmware into multiple pieces, the pieces are more suitable for transmission via a low power short range point-to-point communication system such as (but not limited to) NFC system, as compared to a complete firmware package which may require higher bandwidth and/or longer communication times than are typically available when communicating via NFC systems. In numerous embodiments, systems and methods for secure electric vehicle charging can deliver power management control information to an EV charger. This can be performed by the EV operator’s mobile device sending the power management control information to the EV charger.

[0066] In several embodiments, systems and methods for secure electric vehicle charging can include a software application. In certain embodiments, the user interface of the software application includes an “add to wallet” feature. This feature can allow a user to add a token to a digital wallet on the user mobile device, thus enabling a charging session in the event of loss of a network connection or when a network connection is not present. However, some add to wallet features may not be unlocked for developer access for peer to peer communication so the application in the background may not be able to retrieve confirmation from the EV charger. These add to wallet features may be used with networked end-devices and processors that rely on a direct connection to the cloud. Thus, applications that utilize the wallet benefit from the ability to retrieve data and updates after a "tap" is completed via the wallet. In some embodiments, the EV charger may include a BLE iBeacon to establish the pairing as the vehicle operator arrives at the station. Once the tap is completed, the EV charger may process the request and revert it back to the app over BLE iBeacon protocols. Thus, the mobile device may be configured to send and receive transaction processes with data sent over NFC but received over BLE.

[0067] In many embodiments, the user interface can include a button on a map for quick access to bring up a reader. In numerous embodiments, the user interface can include a “tap to start” and/or “tap to stop” features. In various embodiments, the software application can include a “charge now” feature where the vehicle can select a charger, an end time, and a payment card on one screen. In many embodiments, the software application can include a “charge later” feature where the software application can display buttons for today/tomorrow booking on a calendar, and auto-select start and end times. In several embodiments, systems and methods for secure electric vehicle charging can utilize a mobile device’s local storage to download an encrypted payload ahead of time for accessing chargers in remote areas. In many embodiments, systems and methods for secure electric vehicle charging can utilize a mobile device’s local storage to store session log data on the mobile device’s memory at the end of session. In several embodiments, the session data can then be sent to the cloud for payment processing. This session log data can include data from sessions involving other mobile devices or previous sessions involving the same mobile device. Examples where previous charging session data are sent during a tap to start from a mobile device are described in connection with Fig. 24A below and are applicable to this description.

[0068] While specific systems and methods for secure electric vehicle charging are described above, any of a variety of different configurations of systems and methods for secure electric vehicle charging can be utilized for EV charging as appropriate to the requirements of specific applications of embodiments of the invention. Electric vehicle power distribution networks and methods of providing power to electric vehicles in accordance with various embodiments of the invention are discussed further below. Electric Vehicle Power Distribution Networks

[0069] Fig. 1 illustrates a power distribution network in accordance with an embodiment of the invention. The power distribution network 100 includes a power generator 102. Electricity may be generated at power generator 102. Power transmission lines 104 can transmit electricity between the power generator 102 and power substation 106. Power substation 106 additionally can connect to one or more large storage batteries 108, which temporarily store electricity, as well as power distribution lines 110. The power distribution lines 110 can transmit electricity from the power substation 106 to one or more charging stations 112. Each charging station 112 can include a battery 114 and/or solar panels 116. Electric vehicles 118 can connect to the charging station 112 and request delivery of power.

[0070] The power generator 102 can include a power source generating power through fossil fuels, nuclear, solar, wind, and/or hydroelectric power. The substation 106 may convert the voltage of the electricity for more efficient power distribution. In some embodiments, solar panels 116 may be used as distributed power generation sources, and can generate power to supply electric charging stations as well as generate additional power for the power grid. While illustrated in separate buildings, the charging stations 112 may all be located in one building such as an office building or an apartment building. [0071] While specific systems incorporating a power distribution network are described above with reference to Fig. 1 , any of a variety of systems including secure EV charging can be utilized to provide secure EV charging as appropriate to the requirements of specific applications in accordance with various embodiments of the invention. Systems for secure EV charging in accordance with a number of embodiments of the invention are discussed below.

Systems for Secure EV Charging

[0072] Fig. 2 illustrates a system diagram of a secure EV charging system in accordance with an embodiment of the invention. The secure EV charging system 200 includes an EV charger 202. The EV charger 202 can communicate with a user mobile device 204 via a low power short range point-to-point communication system 202a such as NFC. The user mobile device 204 may be a smart device such as a smartphone. Also, the user mobile device 204 can include wearable mobile devices such as wearable smart watches. In some embodiments, the EV charger 202 can communicate with an EV 216 without communicating with the user mobile device 204. The EV 202 can come with a pre-installed low power short range point-to-point communication system or may be retrofitted with a low power short range point-to-point communication system which may be used to interact electronically with the short range point-to-point communication system 202a embedded in the EV charger 202. The mobile device 204 can communicate with an NFC access management 206.

[0073] The NFC access management 206 may be linked to a server 208. The server 208 can include a charging protocol, for example open charge point protocol (OCPP). This protocol may enable communication between the server 208 and the user mobile device 204. The NFC access management 206 can further communicate with a database (DB) 212. A central management system (CMS) 210 can communicate with the server 208, the access management 206, and the database 212. The CMS 210 can also communicate with other mobile devices 214.

[0074] A mobile user can use the user mobile device 204 to tap on a user interface to identify an EV charger 202 to start a charging session. The EV charger 202 can deliver encrypted access credentials to the user mobile device 204 via a low power short range point-to-point communication system 202a such as (but not limited to) NFC and/or Bluetooth Low Energy (BLE). In some embodiments, the mobile user can proceed with a charging session with no network connection available. Upon completion of the charging session, the charging session data can be sent from the EV charger 202 to the user mobile device 202. The charging session data may be stored locally on the user mobile device 204, which can be sent back to the server 208 when a network connection is available or becomes available. In some embodiments, the user mobile device 204 may send data that can include information concerning other charging sessions and/or information regarding charging sessions involving other EV chargers that share a local area network connection with the EV charger 202 communicating with the user mobile device 204. Examples of embodiments involving networked EV chargers are discussed in connection with Fig. 23. Fig. 23 discusses a mesh networking scheme that can be used to network multiple EV chargers together.

[0075] In instances when a network connection is available during charging, the user mobile device 204 can use encrypted access credentials to communicate with the server 208 having the NFC access management 206. The server 208 can verify the mobile user’s identification (user ID) and the EV charger 202 against a repository of users and chargers located in the database 212. Upon successful verification of the user ID and the EV charger 202, an encrypted payload may be sent from the server 208 to the user mobile device 204. The user mobile device 204 can then send the encrypted payload to the EV charger 202 via a low power short range point-to-point communication system 202a such as (but not limited to) an NFC system to start a charging session. Upon completion of the charging session, the session data can be stored on the mobile device 204 and sent back to the server 208. This session log data can include data from sessions involving other mobile devices 214.

[0076] In many embodiments, the EV charger 202 can be configured to communicate with other EV chargers as illustrated in Fig. 23. When an EV charger is configured in this way, data received by one EV charger can be distributed to other EV chargers. In addition, messages and/or session data provided by one EV charger may have originated at another EV charger.

[0077] While specific systems for secure EV charging are described above with reference to Fig. 2, any of a variety of systems can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including low power short range point-to-point communication, delivering encrypted access credentials, and storing session data in accordance with various embodiments of the invention. Server systems for secure EV charging in accordance with a number of embodiments of the invention is discussed below. EV Charging Server Systems

[0078] Fig. 3 illustrates a block diagram of a server system 300 in accordance with an embodiment of the invention. The server system 300 may include a processor 302. The processor 302 can exchange data with memory 306. The processor 302 can communicate through an input/output (I/O) interface 304. The memory 306 can include an EV charging protocol software application 308. The EV charging protocol software application 308 can enable communication between the server and an access management system. The term “application” herein is utilized to describe machine readable instructions including (but not limited to) software applications, operating system software, firmware, embedded firmware, and/or instructions utilized to configure an FPGA, etc. The EV charging protocol software application 308 can also enable communication between the server and mobile devices. Note that a server system can be implemented using one or multiple physical servers and that different server hardware may provide different servers and/or different servers may respond to sequences of requests from an individual mobile device.

[0079] While specific server systems for secure EV charging are described above with reference to Fig. 3, any of a variety of server systems can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including communication between the server and the mobile device in accordance with various embodiments of the invention. Mobile devices configured by an authentication application to communicate securely with EV chargers in accordance with a number of embodiments of the invention is discussed below.

Authentication Applications

[0080] Fig. 4 illustrates a block diagram of a mobile device 400 configured using an authentication application in accordance with an embodiment of the invention. The mobile device 400 can include a processor 402. The processor 402 can exchange data with memory 406. The processor 402 can communicate through an input/output (I/O) interface 404. The memory 406 can include an authentication software application 408 executable by the processor 402. The authentication software application 408 can communicate with an EV charger and pass an encrypted payload to the EV charger in order to initiate a charging session. The term “application” herein is utilized to describe machine readable instructions including (but not limited to) software applications, operating system software, firmware, embedded firmware, and/or instructions utilized to configure an FPGA, etc. An example of the encrypted payload passed from the mobile device 400 to the EV charger is shown below:

{

//Encryption Challenge here with Secure Element or Cloud based methodology like HCE

“driverld”: “ae34-fbd-4ybdi-46ss-9kmn0”

“locationld”: “Accepted”,

“changeNFCtagName”: “ “,

“diagnosticQuery”: “Temperature, GFCI”.

“firmwarellpdate”: “ “,

“pricePerhour”: “ “,

“pricePerkWh: “0.32”,

“locationHours: “MMDDYY T - MMDDYY T”,

“multipleSessionsperDay”: “False”,

“maxSessionduration”: “12”

“authSetting”: Private

},

{

"chargePointld": "Xeall",

"connectorld": 1 ,

"csChargingProfiles": {

"chargingProfileld": "4875db47-392a-40ae-9213-71 c59f268b4e",

"chargingProfileKind": 'Absolute",

"chargingProfilePurpose": "TxProfile",

"chargingSchedule": {

"chargingRatellnit": "W¹,

"chargingSchedulePeriod": [

{

"limit": 22000.0,

"startPeriod": 0

},

{

"limit": 15000.0,

"startPeriod": 180

},

{

"limit": 8000.0,

"startPeriod": 1080 }

"duration": 1980

}

[0081] While this is one example of an encrypted payload, alternative formats and/or syntaxes can be utilized to communicate the same data or similar data. This example may be data intensive due to the fact that it follows the OCPP standard utilized by many conventional EV chargers. This may lead to latency issues which may be problematic as NFC may have slower data transfer speeds compared to other transfer mediums and NFC transfer sessions may last a short time such as up to 300ms. While a user may hold their mobile device in contact with the EV charger for a longer time to transfer a larger amount of data, holding the mobile device in contact with the EV charger for a long period of time may be inconvenient and annoying to many users. In some embodiments, a translation in the cloud may be performed from the OCPP standard to another standard communication protocol. The other standard communication protocol may employ an adaption layer or include the majority of the payload to be programmed within the firmware. The data being shared from the cloud to the mobile device 400 and the EV charger may include the attributes to execute the session and may be compiled locally. Thus, the data transferred from the EV charger to the mobile device 400 may be minimal which may make these embodiments more suitable for NFC.

[0082] In many embodiments, the mobile device 400 may be configured by the authentication application 408 to perform authentication with the EV charger. In several embodiments, the mobile device 400 may be configured by the authentication application 408 to present a user interface to the user that enables control of charging using the EV charger. In numerous embodiments, the mobile device 400 may be configured by the authentication application 408 to gather log session data from the EV charger. In certain embodiments, the mobile device 400 may be configured by the authentication application 408 to provide portions of firmware updates to EV chargers. In many embodiments, the mobile device 400 may be configured by the authentication application 408 to communicate with remote server systems including a server system 300 having EV charging protocol software application 308 as described in connection with Fig. 3.

[0083] While specific mobile devices that are configured by authentication applications are described above with reference to Fig. 4, any of a variety of mobile devices and/or authentication applications can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including authentication of the mobile device by the EV charger in accordance with various embodiments of the invention. EV chargers that are capable of communicating via low power short range point-to-point communication system such as (but not limited to) NFC and/or Bluetooth Low Energy (BLE) in accordance with a number of embodiments of the invention are discussed below.

EV Chargers with Low Power Short Range Point-to-point Communication System

[0084] Fig. 5 illustrates a block diagram of an EV charger 500 in accordance with an embodiment of the invention. The EV charger 500 can receive electric power from the grid and includes a power management unit 512 that can convert AC to DC, monitor power connections, and control input and output power flows. The EV charger 500 can include a processor 502. The processor 502 can exchange data with memory 506. The processor 502 can communicate through an input/output (I/O) interface 504. The memory 506 can include an authentication software application 508 executable by the processor 502. The term “application” herein is utilized to describe machine readable instructions including (but not limited to) software applications, operating system software, firmware, embedded firmware, and/or instructions utilized to configure an FPGA, etc. The EV charger 500 can include a low power short range point-to-point communication system 510 such as (but not limited to) NFC and/or Bluetooth Low Energy (BLE). An NFC system-on-chip (SoC) 510 can be installed in the EV charger 500. The authentication software application 508 can enable the EV charger 500 to communicate with a mobile device via the low power short range point-to-point communication system 510. In a number of embodiments, the EV charger 500 includes a locking mechanism configured to lock the charging cable to an EV. In several embodiments, the EV charger 500 includes one or more wires between the I/O interface 504 and the locking mechanism (not shown) that enables the processor 502 to control the activation and/or release of the locking mechanism. As discussed further below, the ability of the EV charger 500 to control the locking mechanism can encourage users to initiate an interaction between their mobile devices and the EV charger upon completion of a charging session in order to release the locking mechanism. In several embodiments, this interaction enables exchange of charging session data between the EV charger 500 and the mobile device that can then be provided to system servers when a network connection is available to the mobile device.

[0085] In some embodiments, the EV charger 500 may not be configured to depend on a tap to end a charging session to retrieve data associated with the session for a previous charging session and can send previous charging session data from another operator’s interaction with the EV charger with a separate mobile device. The one operator’s interaction with the EV charger 500 may include sending multiple transactions of data or a previous charging session data to the mobile device to relay to the server. In this case, the other mobile device may be used to provide the previous charging session data to the server when a network connection is available to the other mobile device. Examples of a process where previous charging session data may be sent through other mobile devices are described in connection with Fig. 24A below. In these examples, a tap to end may not be performed and thus the previous charging session data may remain on the EV charger 500 until it is sent to the other mobile device.

[0086] Fig. 6 illustrates a block diagram of an EV charger NFC SoC 600 in accordance with an embodiment of the invention. The NFC SoC 600 includes a micro-controller unit (MCU) 602. The NFT SoC 600 may include a DC-DC converter 610 which can regulate power and provide conditioned power to the MCU 602 and the rest of the circuits. The MCU 602 may communicate with a memory 612. The MCU 602 can also control an NFC unit 614. In several embodiments, the MCU 602 also controls a WiFi and/or blue tooth low energy (BLE) unit 606. The MCU 602 can interface with outside circuits through a UART/USB unit 604. [0087] In many embodiments, the EV charger 500 can log session data and provide the charging session data to one or more user mobile devices. In several embodiments, the EV charger 500 can receive portions of firmware updates in order to build and deploy complete firmware updates. In numerous embodiments, the EV charger 500 can receive power management information and can adjust charging algorithms based upon the received power management information.

[0088] While a specific EV charger 500 and an EV Charger NFC SoC 600 is described above with reference to Figs. 5 and 6, these are merely exemplary and any of a variety of EV chargers and NFC SoCs can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including communication between the EV charger and the mobile device via low power short range point-to-point communication systems in accordance with various embodiments of the invention. Further, various authentication processes in accordance with a number of embodiments of the invention are discussed below.

Authentication Processes

[0089] In many embodiments, systems and methods for secure electric vehicle charging can include a user authentication process which may function without the presence of a network connection. In certain embodiments, the authentication process can enable an EV operator’s mobile device to authenticate itself to an EV charger and enable the EV charger to deliver encrypted access credentials to an EV operator’s mobile device via a low power short range point-to-point communication system such as (but not limited to) an NFC system, enabling a charging session for the EV without the presence of a network connection. In several embodiments, the charging session data can be stored locally on the mobile device when no network connection is available. In many embodiments, systems and methods for secure EV charging can enable buffering of the data transmitted from the EV charger to the mobile device, where the data is stored on the mobile device and is then transmitted to a server when a network connection is restored. In certain embodiments, the data can also include data from previous charging sessions. In this way, data from multiple charging sessions can be uploaded to the server when a single mobile device establishes a network connection with the server. Examples where previous charging session data may be sent through other mobile devices are described in connection with Fig. 24A below. In this example, the previous charging session data may be sent to the other mobile device during a tap to start.

[0090] In several embodiments, when there is no network connection present, authentication can be performed against locally stored data. Upon successful authentication, a pre-authorized payload (e.g. a digital token) can be utilized to enable a session. The pre-authorized data can also pass validity and expiration data, so the charging sessions are limited until expiration date or until the calculated energy use/cost is reached. In case a location was added offline or balance is lower than the limit set, the user may reconnect to update an access management software and database with the most recent data.

[0091] Fig. 7 illustrates an authentication process in accordance with an embodiment of the invention. An EV operator mobile device 712 may tap to start (702) the session to initiate a charge. The EV operator 712 may tap a start button on a user interface of a software application in order to initiate the charge. In many embodiments, the charging session may be directly initiated on an EV charger 714 when even no network connection is present. The mobile device 712 can communicate with the EV charger 714 via a low power short range point-to-point communication system such as (but not limited to) NFC system. The EV charger 714 can proceed to collect one or more unique identifiers for the charging session and authenticate the user.

[0092] The EV charger 714 can deliver (704) encrypted access credentials to the mobile device 712. In a number of embodiments, the access credentials are utilized by the mobile device 712 to confirm that one or more pre-authorized digital tokens present on the mobile device are capable of activating the EV charger 714. In several embodiments, the access credentials include the identity of the EV charger 714 and the mobile device 712 which may confirm that a pre-authorized digital token is authorized for use on the identified EV charger 714. In certain embodiments, the access credentials include time of use restrictions and the mobile device 712 confirms that the current sessions meet the time of use restrictions and/or that a pre-authorized digital token is authorized for use at the current time and/or for the requested charging duration. As can readily be appreciated, the specific information contained within the access credentials and utilized to confirm that one or more of the pre-authorized digital tokens can be utilized to initialize a charging session may be limited by the requirements of a specific application.

[0093] The mobile device 712 can send (706) a pre-authorized digital token to the EV charger. The EV charger 714 may initiate a charging session upon successful receipt and decryption of the digital token. The digital token can be encrypted using public keys. In certain embodiments, the digital token is self-authenticating. The EV charger 714 may authenticate (708) the digital token without the presence of a network connection. After authenticating 708 the digital token, the EV charger 714 may initiate (710) a charging session. In several embodiments, the digital token includes an encrypted payload that contains a command. In a number of embodiments, the command is formatted in accordance with a protocol such as (but not limited to) the Open Charge Point Protocol (OCPP). When the encrypted payload is a command, the EV charger 714 can be configured to respond to the decryption of the payload received from the mobile device 712 by executing a command (e.g. a “commence charging session” command). As can readily be appreciated, the specific data provided to the EV charger 714 by the mobile device 712 to initiate and/or control a charging session is largely dependent upon the requirements of specific applications. In some embodiments, the digital token may include other information such as amperage, state of charge or battery level, and/or user departure time.

[0094] At the end of the charging session, the user may end the session by sending an “end charging session” command to the EV charger. The mobile device 712 may tap to end (718) the charging session. In embodiments in which the EV charger 714 is equipped with a locking mechanism, at receipt of the “end charging session” command, the EV charger 714 may release (720) the locking mechanism of the charging connection. In embodiments in which the EV charger 714 includes a locking mechanism controlled by the EV and both the mobile device 712 and the EV are connected to the Internet, then the mobile device 712 can send a message to a server that can initiate a message to the EV to unlock the locking mechanism when the “end charging session” command is sent to the EV charger 714. In some embodiments, the EV charger 714 can send an “end charging session” command via a short-range point-to-point communication system to the user’s mobile device 712 to be displayed on the user’s mobile device 712 or to cause a sense of touch and motion (haptics) on the user’s mobile device 712. As discussed below, in many embodiments, the mobile device 712 may not tap to end to end the charging session. Further, the EV charger 714 may not be equipped with a locking mechanism and thus the charger may simply be disconnected from the EV to end the charging session or the charging session may simply time out to end.

[0095] In certain embodiments, the mobile device 712 can tap “end” to complete the charging session and to unplug the EV. In this way, the software on the mobile device 712 may terminate billing to avoid being charged for a full charging session. In addition, the mobile device 712 can also collect session data and diagnostics information from the EV charger 714. This data can include information such as (but not limited to) transaction ID, energy dispensed, meter reading (cumulative) to maintain redundancy if data is lost at end of session. The mobile device 712 may store (722) session data locally on the mobile device 712 when no network connection is available. In many embodiments, the session data can include duration, session ID/transaction ID, kWh used, details regarding the EV, details regarding maximum amperage for the EV diagnostics, EV operator details, temperature, humidity, charger faults, relay didn’t shut off, ventilator, and diagnostics regarding any errors that may have occurred during the charging session. In some embodiments, the session data can include the status of the EV charger 714 at the time the charging ended, such as whether the EV was still plugged into the EV charger.

[0096] In some embodiments, the session data can include data collected by the EV charger 714 during a previous session and provided by the EV charger 714 for forwarding to the server system 716. In many embodiments, systems and methods for secure EV charging can enable storing of the session data locally on the mobile device 712. The mobile device 712 may transmit (724) the stored data to a server system when a network connection is available. For example, the mobile device 712 may not have an internet connection during the EV charging session, however the mobile device 712 may travel to where it has an internet connection and at that time the session data may be transferred to the server 716. The mobile device 712 may also have the internet connection disabled at the time of charging and then enable the internet connection at a time after charging.

[0097] In several embodiments, when a network connection is available during the charging session, the EV operator’s mobile device 712 can communicate with the server 716 and obtain an encrypted payload from the server 716. Upon initiation of a charging session, the mobile device 712 communicates with the EV charger 714. The mobile device 712 can then gain access to an access management system (AMS) residing on a server 716, where the EV charger 714 and the EV operator’s user identification (user ID) can be verified against a database which is maintained on the server 716. In many embodiments, when the verification has been successfully completed, an encrypted payload for initiating a charge can be passed from the server 716 to the mobile device 712, where the mobile device 712 can send the encrypted payload to the EV charger 714 via a low power short range point-to-point communication system such as (but not limited to) NFC system in order to initiate a charge. In numerous embodiments, upon completion of the charging session, systems and methods for secure electric vehicle charging can enable the mobile device 712 to end the session by tapping on a user interface of the software application. The session data can be retrieved from the EV charger 714 by the mobile device 712 in order to log the details of the charging session.

[0098] FIG. 8 illustrates an authentication process for a mobile device in accordance with an embodiment of the invention. Process 800 includes tapping to start (802) a charging session. The mobile device may receive (804) encrypted credentials from the EV charger. The mobile device may send (806) a digital token to the EV charger. The digital token may be used to verify the mobile device. After the mobile device is verified, the EV charger may begin the charging session. To end the charging session, the mobile device may interact (808) with the EV charger via the user interface to end the session. The mobile device may tap to end the charging session. The mobile device may receive and store (810) the charging session data during the tap to end. The mobile device may receive the charging session data from the EV charger through a low power short range point-to-point communication system. When a network connection is available, the mobile device may send (812) the session data to the server. As discussed above, in some embodiments, the mobile device may not tap to end their charging session but instead the charging session may end when a user disconnects their EV from the EV charger or when the charging session times out. In these instances, a subsequent mobile device may receive the charging session data. Examples where previous charging session data may be sent through subsequent mobile devices are described in connection with Fig. 24A below. As described, the EV charger may send the previous charging session data to the subsequent mobile device at the start of another charging session.

[0099] Fig. 9 illustrates an authentication process performed by an EV charger in accordance with an embodiment of the invention. The process 900 includes receiving (902) a request for authentication. The EV charger may send (904) encrypted credentials to the mobile device. The EV charger may receive (906) a digital token from the mobile device (906). The EV charger may verify the digital token and initiate (908) a charging session. In embodiments where the EV charger includes a locking mechanism, upon completion of the charging session, the EV charger may release (910) the charging lock. The EV charger may then provide (912) the session data to the mobile device. In many embodiments, the charging session data provided to the mobile device can also include session data from previous charging sessions including charging sessions involving different mobile devices. In some embodiments, the EV charger may not include a charging lock. In some instances, the EV charger may not provide the charging session data to the mobile device but instead the charging session data may be provided to a subsequent mobile device. Examples where previous charging session data may be sent through other mobile devices are described in connection with Fig. 24A below.

[0100] Fig. 10 illustrates an authentication process performed by an EV charging server in accordance with an embodiment of the invention. The process 1000 can include receiving (1002) session data from the mobile device when the mobile device has a network connection. The server may update (1004) a database based on the session data. In some embodiments, the server may pass an encrypted payload to the mobile device for initiating a charging session. In many embodiments, the mobile device may maintain a data connection and provide the session data. In several embodiments, when the mobile device is disconnected from the internet connection during a charging session, the mobile device can establish a network connection at a later time and provide the session data at that time. In addition, the EV charger may provide the charging session data to an alternative mobile device, which in turn can provide the charging session data to the server system when the alternative mobile device has an internet connection. Examples where previous charging session data may be sent through alternative mobile devices are described in connection with Fig. 24A below.

[0101] While specific authentication processes are described above with reference to Figs. 7-10, any of a variety of authentication processes can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including collecting one or more unique identifiers for the charging session and authenticating the user in accordance with various embodiments of the invention. For example, revolving time-based authentication processes may be utilized and are discussed below.

Revolving Time-Based User Authentication

[0102] In many embodiments, systems and methods for secure EV charging can include a time-based user authentication. In many embodiments, time-based user authentication can be performed by collecting a unique identifier of a mobile device request for a charging session. In several embodiments, the requested start and end times can be matched with an interval-based service that only displays the “Auth request” button on the user interface within a timed interval for a particular user’s start and end interval maintained in a local time zone.

[0103] In some embodiments, the EV charger may include a Real Time clock with an auxiliary battery to maintain time during power outages. The auxiliary battery may include a coin shaped battery. This may be useful to keep track of various aspects of the EV charger such as expired tokens and reservations. However, drifts in time may be a problem in offline devices. In some embodiments, time may be updated when connecting with a mobile device in which time of day may be passed as part of the payload from the mobile device to the EV charger. In some implementations, the NFC module of the EV charger may receive the time from the backend and correct for drift in time. In some embodiments, there may be an additional verification check to the mobile application's token timestamp that the current time is later than the timestamp. If the mobile application's time is much later/earlier than the NFC module's time (e.g. over 1 minute), the mobile application's time may be be ignored. If the mobile application's time is later/earlier than the NFC module's time for a small amount of time (e.g. for less than 1 minute), the NFC module's time may be corrected.

[0104] The authentication and session start command between the EV operator and the EV charger can be inserted into a dynamic revolving timescale between 0 to 24 hours in 15-minute interval gaps. A set of charging sessions may be received from different EV operators requesting charging sessions. The authorization command on a user interface may be made visible for each reserved session unique to the user between start and end of the interval. The same logic may be applicable when aborting charging.

[0105] Fig. 11 conceptually illustrates a revolving time-based user authentication process in accordance with an embodiment of the invention. Three users (A, B, C) may have three intervals (e.g. S1 -E1 , S2-E2, S3-E3), during which time the “Authorization” button becomes visible on the user interface of each user’s software application.

[0106] While specific time-based authentication processes are described above with reference to Fig. 11 , any of a variety of time-based authentication processes can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including authentication between the EV operator and the EV charger based on a revolving timescale in accordance with various embodiments of the invention.

Authentication Application User Interfaces

[0107] In many embodiments, systems and methods for secure EV charging can include a software application. The software application on an EV operator’s mobile device can include a user interface. Figs. 12A-12D show various screen shots of an example of a user interface for an authentication application that can be installed on a user’s mobile device. The user interface may enable an EV operator to interact with the software application in order to find a charger, and start and end a charging session. A token can be added to a digital wallet on a mobile device as shown in Figs.12A-12D. Once a token has been added to the digital wallet on the mobile device, a charging session can be started without the presence of a network connection as discussed above.

[0108] Figs. 13A and 13B illustrate various screen shots of an example of a user interface for an authentication application in accordance with an embodiment of the invention, where locations of public charges are displayed on a map, and the user can select a charger from the displayed map. Figs. 14A and 14B show various screen shots of an example of a user interface for an authentication application, where locations of private chargers are displayed on a map, and a user can select a charger from the displayed map.

[0109] While specific examples of user interfaces for authentication applications are described above with reference to Figs. 12-14, any of a variety of user interfaces can be utilized within authentication applications as appropriate to the requirements of specific applications including adding a token to a digital wallet and starting a charging session without the presence of a network connection in accordance with various embodiments of the invention.

Firmware Update Processes

[0110] Fig. 15 illustrates a firmware update process in accordance with an embodiment of the invention. The EV charging server 716 may divide (1502) the firmware into multiple pieces. The server 716 may send (1504) one or more of those firmware pieces to an EV operator’s mobile device 712. The mobile device 712 can deliver (1506) one of more of the received firmware pieces to an EV charger 714 via a low power short range point-to-point communication system such as (but not limited to) NFC system. For example, one mobile device may deliver one or more pieces of the firmware and another mobile device may deliver another one or more pieces of the firmware. The pieces of the firmware may be small enough to be suitable for transmission via a low power short range point-to-point communication system such as (but not limited to) NFC system with a short connection time. A complete firmware would require a long connection time for transfer via a low power short range point-to-point communication system. Thus, the mobile device would be connected to the EV charger 714 for a long period of time. Different pieces can come from different mobile devices and/or during different sessions. The EV charger 714 can keep track (1508) of the pieces of the firmware to assure the firmware’s integrity. The EV charger 714 may communicate with the mobile device 712 to request missing firmware pieces. Further, as illustrated in Fig. 23, multiple EV chargers may be networked together. Thus, the multiple EV chargers may share firmware data such that different pieces are delivered to different EV chargers which may be combined into a complete firmware update.

[0111] Fig. 16 illustrates a firmware update process for an EV charger in accordance with an embodiment of the invention. Process 1600 includes receiving (1602) one or more pieces of the firmware via multiple NFC communications with a mobile device. The EV charger can keep track (1604) of the received firmware pieces to assure integrity of the firmware. The EV charger reassembles (1606) the pieces of firmware once the complete firmware update is received. The pieces of firmware can come from different mobile devices and/or different sessions. When the EV charger receives the entire firmware, the EV charger performs (1608) the firmware update.

[0112] In several embodiments, the firmware update can be performed over multiple charging sessions. In many embodiments, the firmware update can include encrypted start and end bits. In numerous embodiments, the firmware update can perform checksum verification. In certain embodiments, the firmware update can be initiated outside charging hours or when the EV charger is available and/or during low utilization periods. In some embodiments, the firmware update can include clear, reset, and trigger confirmation messages.

[0113] Fig. 17 illustrates a process for delivering portions of a firmware update using a mobile device to an EV charger in accordance with an embodiment of the invention. Process 1700 includes receiving (1702) one or more pieces of the firmware from a server. The mobile device may send (1704) one or more of the firmware pieces to the EV charger via NFC. In many embodiments, the EV charger can receive one or more pieces of the firmware from the mobile device and then send a confirmation. In some embodiments, the mobile device may receive more firmware pieces than will be sent to the EV charger and only send the EV charger the firmware pieces which the EV charger is missing. In some embodiments, the mobile device may note the firmware pieces that have been sent to the EV charger and report back to the server that these pieces have been sent to the EV charger. The server may then only send the firmware pieces that have not been sent to the EV charger to the mobile devices. In some embodiments, the EV charger can either perform the firmware update or can get a command for firmware update. In many embodiments, a checksum can be performed.

[0114] Fig. 18 illustrates a firmware update process for a server system in accordance with an embodiment of the invention. Process 1800 includes dividing (1802) the firmware into multiple pieces. The server may send (1804) at least one of the multiple pieces of the firmware to the mobile device. In several embodiments, a checksum can be performed. In some embodiments, the server can send firmware updates when the EV charger is available.

[0115] While specific firmware update processes are described above with reference to Figs. 15-18, any of a variety of firmware update processes can be utilized to deliver firmware updates to EV chargers as appropriate to the requirements of specific applications including firmware update via short range point-to-point communication system in accordance with various embodiments of the invention.

Load Management Processes

[0116] Fig. 19 illustrates a load management process in accordance with an embodiment of the invention. A server 716 can collect (1902) data about electricity usage. Based on the collected data, the server 716 can determine (1904) whether a certain percentage of EV chargers should be made unavailable from the mobile device schedules. The server 716 sends (1906) instructions to synchronize the EV operator’s mobile device 712 with an electricity load profile including the current and future charging schedules. The EV operator’s mobile device 712 sends (1908) a list of unavailable chargers to the EV charger 714 via NFC. In many embodiments, systems and methods for secure EV charging can restrict the amount of power that can be drawn from the EV charger 714 to some point up to maximum power available on that EV charger in order to control total power consumption. [0117] In some embodiments, the server 716 can keep track of the total amperage of a certain EV charger. In certain embodiments, the amperage can be set as multiples, for example 15A or 30A. In several embodiments, data can be collected frequently, for example in 15-minute intervals. In numerous embodiments, data for a building including many EV chargers can be based on 24-hour usage across the building. The peak charging times (which can be the most expensive) for the next 48 hours can be calculated using the previous 24-hour data and displayed on the EV operators’ mobile devices in a single calendar view across all EV chargers. The scheduled time on EV operators’ mobile devices can allow the EV operators to have complete transparency into peak charging times and may lead to slower charging times or surge pricing. In some embodiments, when case energy management is activated, sessions during these identified times can have a separate load profile sent by the server system to supersede default charging amperage, and increased charging times can be displayed to the EV operators.

[0118] As discussed previously, the EV chargers may operate in completely offline environments where both the mobile device and EV chargers are not connected to the internet or cloud and thus it is beneficial for decisions and processing to be performed without consideration of internet access. Ordinarily, EV chargers accommodate a static max output amperage that is pre-defined or operate on a first in first out method with locally available data or max thresholds. However, this method, although advantageous for offline applications, may not incorporate user requirements (e.g. state of charge levels or battery percentage, departure times, and market pricing criteria such as the ability to pay a higher rate due to a priority charge request) and ability to run machine learning (ML) algorithms locally and utilize inference-based processing to better allocate power. Therefore, in some embodiments the EV chargers perform match-making via NFC or other short-range methods to utilize user interactive load management. However, in offline environments due to the lack of a mobile device to cloud connection, data associated with real time max amperage levels across the location or all chargers at a site may not be readily available.

[0119] Thus, in some embodiments, the EV chargers retain the ability to run machine learning (ML) algorithms, and keep user-need based load management capabilities locally. The EV chargers may include an Al chip with fast clock rates (e.g. a GPU), include a mesh networking technology like BLE mesh to allow the EV chargers to communicate to each other, and run low memory tuned compressed algorithms on the edge. The ledger data for the last 30 days of sessions may be collected in each individual EV charger but also may be shared to a global file record across all networked EV chargers. The ledger data may not be specified depending on available memory. Moreover, the historical building level energy profiles may also be pre-programmed in each EV charger during provisioning in 15-minute intervals as an example. In some embodiments, the EV chargers may have a local controller or direct integration with a Building Management System to provide real time meter or panel power information. With these two data sources, the EV chargers may include peak-finding algorithms to predict coincident peaks between the building and total EV charger/vehicle power demand to throttle amperage or pricing information of sessions for vehicle operators. Moreover, the real time amperage levels of EV chargers may be shared between all the EV chargers in a network to maintain the macro/total amperage across stations at a particular location (e.g. within a building). Based on vehicles plugging in, the user ID, and user requirements passed via short range communication at the start of a session, a particular EV charger may allocate remaining power dynamically to the next available charger by communicating over the mesh network to other networked chargers while maintaining the total amperage below the maxima for the group of chargers. For example, if there are multiple EV chargers with a limited capacity to share between the multiple EV chargers, the EV chargers may dynamically calculate which EV charger receives power based on vehicles plugging in, the user ID, and the user requirements to determine the optimal amount of power to provide to each EV charger.

[0120] Fig. 20 illustrates a load management process performed by an EV charger server in accordance with an embodiment of the invention. Process 2000 includes collecting (2002) or receiving data about electricity usage. The EV server may make (2004) certain percentages of EV chargers unavailable from mobile device schedules based on electricity usage data. The EV server may synchronize (2006) the load profile schedule including the current and future charging schedules. This load profile schedule may be sent to the mobile device. In several embodiments, a receipt of actual power consumption information from the EV charger is provided to the EV charger server so that the server can compare future usage data that it receives and determine whether the adjustment to the power of the EV charger improved the electricity usage, and determine what adjustment to make in the future.

[0121] Fig. 21 illustrates a load management process for a mobile device in accordance with an embodiment of the invention. Process 2100 includes receiving (2102) the load profile schedule including the current and future charging schedules from the server system. The mobile device updates (2104) the EV charger via NFC with a list of unavailable chargers. In some embodiments, the EV charger is updated via NFC with a list of limited availability chargers which may have limited availability due to load profile schedules reducing available amperages. In some embodiments, the EV chargers are networked. In several embodiments, a single EV charger might communicate with a mobile device and then distribute data to other networked EV chargers.

[0122] While specific load management processes are described above with reference to Figs. 19-21 , any of a variety of load management processes can be utilized to provide load management information to EV chargers that lack direct network connections with power management server systems and enable the EV chargers to modify the manner that they deliver power to EVs in response to changes in network demand as appropriate to the requirements of specific applications in accordance with various embodiments of the invention.

Systems for Secure EV Charging with Networks

[0123] Fig. 22 illustrates a system diagram of an EV charging system in accordance with an embodiment of the invention. The system 2200 includes EV chargers 2202 which can communicate with a server 2204 via network connection. Server 2204 can include a charging protocol, for example open charge point protocol (OCPP). This protocol enables communication between the server 2204 and the EV chargers 2202 devices. The server 2204 can enable authentication of users by verifying the users against a list of users maintained on the server 2204. As discussed above, EV chargers 2202 may also not be connected to the network and may be provided data solely from user mobile devices which the EV chargers 2202 interact with.

[0124] Fig. 23 illustrates a networked set of EV chargers in accordance with an embodiment of the invention. The networked EV chargers may include multiple EV chargers 2202a, 2202b, 2202c, 2202d. The multiple EV chargers 2202a, 2202b, 2202c, 2202d may be networked together such that the EV chargers are capable of communicating with one another. For example, the EV chargers 2202a, 2202b, 2202c, 2202d may form a mesh such that the EV chargers 2202a, 2202b, 2202c, 2202d are able to share data with each other. In some embodiments, a first EV charger may be indirectly connected with another EV charger in such a fashion that the other EV charger communicates through an intermediate EV charger to communicate with the first EV charger.

[0125] While specific system for secure EV charging are described above with reference to Figs. 22 and 23, any of a variety of systems can be utilized to provide secure EV charging as appropriate to the requirements of specific applications including authentication of users against a list of users in accordance with various embodiments of the invention.

Additional Applications

[0126] While the systems and processes described above have been discussed in the context of EV chargers, systems and methods in accordance with embodiments of the invention can be utilized to provide authentication, secure data transfer, firmware updates, and gathering of session data in any of a variety of contexts involving communication between two devices, where an internet connection is unavailable, intermittently available, and/or only available to one of the devices. For example, systems and methods described herein can be used to authenticate electric scooters, where there may be no internet connection available for authentication. As another example, systems and methods described herein can be used to authenticate real estate access controls using short range point-to-point communication systems such as NFC, where there may be no internet connection available for authentication. [0127] Systems and methods in accordance with embodiments of the invention can be utilized to provide access control system for any kind of asset. These assets may benefit from authorization, authentication, payment, and log of session data to coordinate payments. Specific examples can include micro-mobility, ride sharing, common areas in a community setting, fitness areas, private real estate units, and assets used in a sharing economy, for example real estate assets used in Airbnb. Other examples can include connected vending machines, washers and dryers in a shared apartment environment, where systems and methods described herein can be used to enable payment with a non-internet connected device. Systems and methods described herein can also be used in some settings to provide a mobile payment without having a network connection, where the cost of maintaining the network connection can be high.

[0128] In several embodiments, processes similar to those described herein can be utilized in applications including (but not limited to) security and access control applications. For example, in some settings multiple people are able to use a “key” at the same time. Another example is where everyone having access to an area may be able to provide a token to the access control system. In other examples, this can also apply where EV chargers including a single control that has multiple ports. For example, an EV charger may permit many people to authenticate and start charging on the EV charger that controls multiple ports for charging.

[0129] While the above descriptions and associated figures have depicted systems and methods for secure EV charging, it should be clear that any of a variety of configurations for systems and methods for secure EV charging can be implemented in accordance with embodiments of the invention. More generally, although the present invention has been described in certain specific aspects, many additional modifications and variations would be apparent to those skilled in the art. It is therefore to be understood that the present invention may be practiced otherwise than specifically described. Thus, embodiments of the present invention should be considered in all respects as illustrative and not restrictive. Example Methods of Sending Charging Session Data to a Server

[0130] As discussed previously, previous charging sessions may be sent to an EV operator mobile device which subsequently taps to start a charging session. In some cases, a mobile device may tap to start a charging session however may not tap to end the charging session. In these cases, the charging session may be ended when the charging session times out or when the EV charger is unplugged from the EV. However, in these cases, the charging session data may remain on the EV charger without a mechanism to send this back to the server. In some embodiments, the EV charger may send the previous charging session data to a subsequent mobile device which taps to start a subsequent charging session. This subsequent mobile device may send the charging session to the server when an internet connection is present.

[0131] Fig. 24A illustrates a process for sending charging session data to a server in accordance with an embodiment of the invention. A mobile device 712 starts (2402) a charging session with an EV charger 714. The mobile device 712 may tap to start the charging session with the EV charger 714 in which the mobile device 712 communicates with the EV charger 714 via a short range point-to-point communication system (e.g. NFC). The mobile device 712 may not have an internet connection during the tap to start and may pass an encrypted token to the EV charger 714 to authenticate the user mobile device 712 for the charging session. During this communication, the EV charger 714 may send (2404) charging session data to the mobile device 712. The charging session data may be previous charging session data. This previous charging session data may be charging session data from a previous charging session started by the mobile device 712 or may be charging session data from previously started from another mobile device. For example, a first EV may charge with the EV charger 714 and create a first charging session data. The mobile device 712 may be associated with a second EV which may charge with the EV charger 714 creating a second charging session data. The first charging session data may be sent (2404) to the mobile device 712 after the tap to start 2402. The mobile device 712 may be the same mobile device in both the first charging session and the second charging session. The first EV and the second EV may be the same EV. The mobile device 712 may not tap to end the first charging session and/or the second charging session. In this case, the first charging session data may be stored on the EV charger 714 until the tap to start of the second charging session where the first charging session data may be sent to the user mobile device 712. Advantageously, the tap to start may be a short time period because the data is already preloaded on the mobile device 712 before the tap to start and thus the mobile device 712 may not communicate through the internet with the server 716 during the tap to start. During the tap to start, the mobile device 712 may not be connected to the internet. In some embodiments, the other charging session data may be from another EV charger networked to the EV charger 714. The other EV charger may transfer the other charging session data to the EV charger 714 through a mesh network.

[0132] After the mobile device 712 receives the previous charging session data, the EV charger 714 may begin charging (2406) the EV. When the mobile device 712 is connected to the internet, the mobile device 712 may send (2408) the previous charging session data to the server 716 which stores the charging session data in a database. For example, when the mobile device 712 taps to start 2402, the mobile device 712 may not be connected to the internet and thus may store the previous charging session data. At a later time when the mobile device 712 establishes a connection with the internet, the previous charging session data may be sent (2408) to the server 716. Advantageously, in instances when a previous mobile device does not tap to end a charging session, the previous charging session data is able to be sent from the EV charger 714 to the server 716 without the EV charger 714 having an internet connection. Otherwise, the previous charging session data may not be transferred from the EV charger 714 to the server 716 in the absence of an internet connection.

[0133] In some embodiments, the previous charging session data may be charging session data from another EV charger which is networked to the EV charger 714. In some embodiments, the other EV charger may be an EV charger which is assigned to a particular user. In these instances, the assigned EV charger may have a user which frequently does not return charging session data and thus, it may be more reliable for the charging session data to be returned through another mobile device. In some embodiments, the mobile device 712 may further send information to the EV charger 714 which indicates that a previous charging session data has been successfully transferred to the server 716 at a previous time. Thus, this may appropriately signal the EV charger 714 to remove or archive previous charging session data that has been properly transferred to the server 716. The EV charger 714 may store previous charging session data until notification that the previous charging session data has been properly sent to the server 716.

[0134] Fig. 24B illustrates a process for sending charging session data to a server in accordance with an embodiment of the invention. Many of the features of the process described in connection with Fig. 24A are relevant to Fig. 24B and will not be repeated. In Fig. 24B, a missing ledger request 2452 may be sent from the server 716 to the user mobile device 712. The user mobile device 712 may tap to start on the EV charger 714 through an NFC module. The user mobile device 712 may utilize the missing ledger request 2452 to send the missing ledger request 2454 to the EV charger 714. In response, the EV charger 714 through the NFC module may send the missing ledger 2456 to the user mobile device 712. When connected to the internet, the user mobile device 712 may send the missing ledger 2458 to the server 716 which may update the missing ledger request and send the updated missing ledger request 2460 back to the user mobile device 712.

Example EV Charger Hardware

[0135] The EV charger described above may include many pieces of hardware which enable to functionality described above. Fig. 25 illustrates an EV charger hardware schematic diagram in accordance with an embodiment of the invention. The EV charger hardware 2500 may include a wireless MCU module 2502 which may include BLE and/or WiFi radio interface. The EV charger hardware 2500 may include an NFC chip 2504 which may include an analog/digital interface between the MCU module 2502 and an NFC enabled smartphone. The NFC chip 2504 may support "active mode" (Reader/Writer), "passive mode" (e.g. a tag emulation), and "peer-to-peer mode". The EV charger hardware 2500 may include an NFC antenna which may be mounted on the external surface of a housing of the EV charger and may not have an underlined metal surface closer than 10-30 mm. The NFC antenna may be connected to the NFC chip 2504 through a 2-wire cable. It may be beneficial for the cable to be relatively short. The EV charger hardware 2500 may include a "crypto or secure element" chip for the storage of a private key and data ("ticket" and "report" payloads) decryption/encryption. The EV charger hardware 2500 may include a flash memory chip which is used for the MCU module’s 2502 external storage for "big" data blocks like firmware update, some logs, and/or others. The EV charger hardware 2500 may include a CT metering chip for energy real time data processing. The EV charger hardware 2500 may include an EEPROM memory chip which may be nonvolatile memory for relatively often logged data (accumulated energy), that later can be copied to the flash (may prevent near term flash tearing). The EV charger hardware 2500 may include a UART-level shifters (3.3V to 5V) and buffers. The EV charger hardware 2500 may include a LIART pins ESD protection. The EV charger hardware 2500 may include a second LIART for firmware loading and testing. The second LIART may be removed after firmware loading and testing. The EV charger hardware 2500 may include a DC-DC voltage converter 2506 to 3.3V and 5V. An external power source may be 5-12V and the DC-DC voltage converter 2506may be used to convert the voltage to 3.3V and 5V. The EV charger 2500 may include a power input resettable fuse. The EV charger hardware 2500 may include a power input reverse-polarity protection. The EV charger hardware 2500 may include one or more LIART connectors. The EV charger hardware 2500 may include other components including but not limited to resistors, capacitors, ferrite beads, and/or transistors. The EV charger hardware 2500 may include a local RTC chip for date/time keeping. The EV charger hardware 2500 may include a local RTC back-up battery.

[0136] The EV charger hardware 2500 may include a retrofit/add-on component for smart and offline EV chargers to bring short-range communication and additional computing resources. The add-on component may be added outside the housing of an existing EV charger utilizing BLE or WiFi-direct to avoid internal direct universal asynchronous receiver-transmitter (LIART) or other wired communication links. The connection of these components is illustrated in Fig. 25. Example Authentication Processes

[0137] Various embodiments include an authentication process. In the authentication process, the user presents an NFC Tag to initiate a charging session. The authentication process checks whether an application is downloaded. If the application is not downloaded and background NFC used, the application store page may be loaded. If the application is downloaded, a certificate check may performed to identify an authorized user. The authentication process may authenticate the user in different ways based on different EV charger configurations. Three different authentication cases based on different EV charger configurations are presented below: when an EV charger is public and available to all, when an EV charger is public and shared by a subset of users, and when the EV charger is private. Each of these cases will be discussed separately.

[0138] When an EV charger is public and available to all, EVSE availability (e.g. in- use or location hours) and health may be checked. A challenge/synchronous or asynchronous encryption/decryption method may be utilized to verify security over a secure element with a crypto-accelerator or over cloud with a method like host cloud emulation. In some embodiments, the encryption standard may not be a transport layer security (TLS) as it benefits from a connection between the client and the server and thus may not be suitable for offline mode where the EV Charger is not connected to the internet. In some embodiments, the encryption standard may include a triple data encryption standard (3DES)/advanced encryption standard (AES) to encrypt the data, elliptic curve digital signature algorithm (ECDSA) for digital signatures, and/or elliptic curve Diffie-Hellman (ECDH) for the key exchange. Utilizing a secure element, although the best paired and most secure with NFC offline methods, may include slow processing speeds compared to a simple firmware hardcoded micro-controller unit (MCU) encryption standards. Therefore, for NFC based access and data logging/processing/metering it may be beneficial to have split encryption/decryption responsibilities if payloads are expansive. In some embodiments, the encryption process may include a secure element public and private key pair encryption for authentication and a second step including payload processing using a second set of keys in the MCU environment. In some embodiments, partial encryption methods may be used. [0139] In some embodiments, no location or driver ID check may be performed unless multiple sessions and charging max hour verification is required or if reservations are enabled. In some embodiments, a balance check may be completed locally on user mobile device ledger if offline or against AMS server and database on the mobile device, EV, or other personal connected device if they are connected to the internet. If no payment is required all steps may be bypassed and only location hours may be verified. If reservations are enabled, a timestamp may also be passed for verification and the payload may be pre-downloaded in an online environment.

[0140] When an EV charger is public and shared by a subset of users, EVSE availability (e.g. in-use or location hours) and health may be checked. A challenge/synchronous or asynchronous encryption/decryption method may be utilized to verify security over a secure element with a crypto-accelerator or over cloud with a method like host cloud emulation. Location ID access may be verified locally or in realtime with an AMS server or a database on the mobile device, EV, or other personal connected device. No driver ID check may be performed unless multiple sessions and charging max hour verification is required or if reservations are enabled.

[0141] A balance check may be completed locally on user mobile device ledger if offline or against an AMS server and database on the mobile device, EV, or other personal connected device. If no payment is required a balance check may be bypassed. If reservations are enabled, the timestamp may be also passed for verification and the payload may be pre-downloaded in an online environment.

[0142] When the EV charger is private, EVSE availability (e.g. in-use or location hours) and health may be checked. A challenge/synchronous or asynchronous encryption/decryption method may be utilized to verify security over a secure element with a crypto-accelerator or over cloud with a method such as host cloud emulation. Location ID access may be verified locally or in real-time with an AMS server or a database on the mobile device, EV, or other personal connected device. No driver ID check may be performed unless multiple sessions and charging max hour verification is required or if reservations are enabled. Alternatively, the driver ID can be stored locally in the cache of the EV charger’s NFC SoC. In some embodiments, the location ID access verification may be accelerated or bypassed. Balance check may be performed completed locally on the user mobile device ledger if offline or against the AMS server or a database on the mobile device, EV, or other personal connected device. If no payment is required the balance check may be bypassed. For a private EV charger, reservations may not be needed.

[0143] In some embodiments, the NFC level checks may be performed in the NDEF payload and the OCPP payload and parsed separately and stored in the SoC. In some embodiments, the NDEF may only be used for application redirection and ISO 14443 and/or ISO 7816 by Apple Inc. may be used for the rest of the read/write communication. Once the above checks are completed the payload may be passed to the EV charger over communication like USB or RS232 as an example. This payload can also hold charging profile data like amperage levels at different intervals for energy management, load management or demand response programs.

[0144] After the authentication process discussed above, the charger may be turned on. During the charging session, energy data and other diagnostic information may be recorded and stored locally on the SoC. If a reservation was made, the session termination request over OCPP may also be stored locally on the SoC and is initiated at the end time of the session.

[0145] In some embodiments, the driver may tap the charger again to end the session and unplug the EV or unplugs the EV to end session. The driver may tap the NFC reader again to terminate billing to avoid further charges and to collect charging session data and diagnostics information. As discussed above, in some embodiments, the EV charging session data may be stored in the EV charger as previous EV charging session data. The previous EV charging session data may be sent to the server from another user mobile device. The EV charging session data can include information like transaction ID, energy dispensed, meter reading (cumulative) to maintain redundancy if data is lost at end of the charging session.

[0146] In certain embodiments, based on duration or energy reading and associated price, the total cost may be calculated locally on the EV charger and deducted from the available credits in the local encrypted ledger on the mobile device. This data may be passed instantaneously when the user mobile device is connected to the internet or at a time when the user mobile device connected to the internet to update back-end data logs. [0147] The SoC may store a number of charging session data locally and can be retrieved by another user mobile device in the event that the user mobile device does not tap to end the charging session.

[0148] The updated charging session data may be checked against local ledger amount and on a reconnect event the AMS may update logs or permission settings for the user or driver if any changes are detected and the locally stored data is updated as well.

[0149] Figs. 26A and 26B illustrate schematic representations for an embedded security system in accordance with an embodiment of the invention. In various embodiments, to securely transmit messages between the server, user mobile device, and the EV charger/module public key infrastructure (PKI). All messages in transit may therefore be encrypted and help prevent man in the middle attacks. To develop such a system message initiated by the user mobile device locally over short range communication with the EV charger, a fast and reliable method such as Elliptic Curve Diffie-Helman may be utilized that allows the creation of a shared key to encrypt and decrypt messages between the two parties. Fig. 26A illustrates an example of a key exchange utilizing PKI in accordance with an embodiment of the invention. Party A may be the EV charger/module and Party B may be the user mobile device. Both devices use their respective private keys and the other party's public key to generate the shared keys. [0150] In some embodiments, this only supports encryption between the mobile device and the EV charger. Therefore, to employ verification and encryption of messages sent over long distances between the EV charger and the server for exchanged information such as charging history and tokens, the EV chargers may be equipped with the public key of the server and the server may be equipped with the public key of the individual EV chargers. Fig. 26B illustrates a diagram illustrating positioning of different public and private keys for utilizing PKI on an example EV charging system. The EV charging system may include an EV charger 2606 which includes a near field communication module. The near field communication module may communicate with a user mobile device 2602. When connected to the internet, the user mobile device 2602 may communicate with a server 2604. The public keys may be used to verify the signatures against a specific message sender to make sure the sender in question actually was the party that sent it. Also, the EV charger 2606 may have its own individual private keys used to decrypt messages encrypted by the server using its public keys and the server may use its own private key to decrypt messages encrypted by the EV charger 2606 using the server's public key. This asymmetric encryption scheme allows all messages to be encrypted between each party for every exchange.

[0151] Although only a few embodiments of the invention have been described in detail, it should be appreciated that the invention may be implemented in many other forms without departing from the spirit or scope of the invention. For example, embodiments such as enumerated below are contemplated:

[0152] Item 1 : A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, and store, in the memory, first charging session data for the first charging session, wherein the digital token is encrypted using a public key and is selfauthenticating without use of an internet connection. [0153] Item 2: The system of item 1 , wherein the processor is further configured by the machine readable instructions to: authenticate a second mobile device via the low power short range point-to-point communication system, cause the storing of the first charging session data on the second mobile device for forwarding, initiate a second charging session, end the second charging session, and store, in the memory, second charging session data for the second charging session.

[0154] Item 3: The system of item 2, wherein the processor is further configured by the machine readable instructions to: use mobile device machine readable instructions on the second mobile device to send the first charging session data to a server system via an internet connection of the second mobile device.

[0155] Item 4: The system of item 2, wherein the processor is further configured by the machine readable instructions to: cause the storing of the second charging session data on the second mobile device for forwarding.

[0156] Item 5: The system of item 4, wherein the storing of the second charging session data on the second mobile device is responsive to the end of the second charging session.

[0157] Item 6: The system of item 4, wherein the processor is further configured by the machine readable instructions to: use mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

[0158] Item 7: The system of item 2, wherein causing the first charging session data to be sent to the second mobile device is performed via the low power short range point- to-point communication system. [0159] Item 8: The system of item 1 , wherein the low power short range point-to-point communication system is a near field communication (NFC) system.

[0160] Item 9: The system of item 1 , wherein the EV charger access credentials comprise charger ID, time of day, and session time.

[0161] Item 10: The system of item 1 , wherein the processor is further configured by the machine readable instructions to: receive the authentication request from the first mobile device via the low power short range point-to-point communication system.

[0162] Item 11 : The system of item 1 , wherein verifying the digital token includes decrypting the digital token using cryptographic information contained within a digital certificate stored on the EV charger.

[0163] Item 12: The system of item 1 , wherein the digital token is bound to a specific time period.

[0164] Item 13: The system of item 1 , wherein the processor is further configured by the machine readable instructions to: receive a communication from the first mobile device to end the first charging session.

[0165] Item 14: The system of item 13, wherein the processor is further configured by the machine readable instructions to: decrypt the communication and to end the charging session.

[0166] Item 15: The system of item 14, wherein: the EV charger further comprises a locking mechanism, and the processor is further configured by the machine readable instructions to release the locking mechanism upon ending the charging session.

[0167] Item 16: The system of item 1 , wherein the processor is further configured by the machine readable instructions to: cause the storing of the first charging session data on the first mobile device for forwarding when a communication is received to end the first charging session. [0168] Item 17: The system of item 16, wherein the processor is further configured by the machine readable instructions to: send the first charging session data to a server system via an internet connection of the first mobile device.

[0169] Item 18. The system of item 16, wherein the processor is further configured by the machine readable instructions to: decrypt the communication to end the first charging session, and end the first charging session.

[0170] Item 19. The system of item 1 , wherein the processor is further configured by the machine readable instructions to: send the first charging session data to another EV charger for forwarding.

[0171] Item 20. The system of item 1 , wherein the processor is further configured by the machine readable instructions to: receive a time of day from the first mobile device to update a time of day on the EV charger.

[0172] Item 21 . A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, store, in the memory, first charging session data for the first charging session, authenticate a second mobile device via the low power short range point- to-point communication system, cause the storing of at least the first charging session data on the second mobile device for forwarding, initiate a second charging session, end the second charging session, and store, in the memory, second charging session data for the second charging session.

[0173] Item 22: The system of item 21 , wherein the processor is further configured by the machine readable instructions to: use a mobile device machine readable instructions on the second mobile device to send the first charging session data to a server system via an internet connection of the second mobile device.

[0174] Item 23: The system of item 21 , wherein the processor is further configured by the machine readable instructions to: cause the storing of the second charging session data on the second mobile device for forwarding.

[0175] Item 24: The system of item 23, wherein the processor is further configured by the machine readable instructions to: use a mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

[0176] Item 25: The system of item 23, wherein the storing of the second charging session data on the second mobile device is responsive to the end of the second charging session.

[0177] Item 26. The system of item 21 , wherein causing the first charging session data to be sent to the second mobile device is performed via the low power short range point- to-point communication system. [0178] Item 27. The system of item 21 , wherein the low power short range point-to- point communication system is a near field communication (NFC) system.

[0179] Item 28. The system of item 21 , wherein the EV charger access credentials comprise charger ID, time of day, and session time.

[0180] Item 29. The system of item 21 , wherein the processor is further configured by the authentication software application to: receive an authentication request from the first mobile device via the low power short range point-to-point communication system.

[0181] Item 30. The system of item 21 , wherein verifying the digital token includes decrypting the digital token using cryptographic information contained within a digital certificate stored on the EV charger.

[0182] Item 31 . The system of item 21 , wherein the digital token is bound to a specific time period.

[0183] Item 32. The system of item 21 , wherein the first charging session data and/or the second charging session data comprise duration of the charging session, energy used during the charging session, a plug-in status, a status of the EV charger, diagnostics data, temperature data, and humidity data.

[0184] Item 33. The system of item 21 , wherein the first mobile device and the second mobile device are the same mobile device.

[0185] Item 34. The system of item 21 , wherein the first charging session data and/or the second charging session data comprise duration of the charging session, energy used during the charging session, and a plug-in status.

[0186] Item 35. The system of item 34, wherein the first charging session data and/or the second charging session data further comprise a status of the EV charger, diagnostics data, temperature data, and humidity data.

[0187] Item 36. The system of item 21 , wherein the digital token is encrypted using a public key.

[0188] Item 37. The system of item 21 , wherein the digital token is self-authenticating without use of an internet connection. [0189] Item 38. The system of item 21 , wherein the processor is further configured by the machine readable instructions to receive a time of day from the first mobile device and/or the second mobile device to update a time of day on the EV charger.

[0190] Item 39. A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: receive an authentication request from a first mobile device via the low power short range point-to-point communication system, authenticate the first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device, receive a digital token from the first mobile device, verify the digital token by decrypting the digital token using cryptographic information contained within a digital certificate, initiate a first charging session based upon a command contained within the digital token, with the internet connection not being available, end the first charging session, store, in the memory, first charging session data for the first charging session, wherein the digital token is bound to a specific time period, is encrypted using a public key, and is self-authenticating without use of an internet connection, authenticate a second mobile device via the low power short range point- to-point communication system, cause the first charging session data to be sent to the second mobile device via the low power short range point-to-point communication system, initiate a second charging session, end the second charging session, store, in the memory, second charging session data for the second charging session, cause the second charging session data to be sent to the second mobile device via the low power short range point-to-point communication system, and use mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

DOCTRINE OF EQUIVALENTS

[0191] While the above description contains many specific embodiments of the invention, these should not be construed as limitations on the scope of the invention, but rather as an example of one embodiment thereof. It is therefore to be understood that the present invention may be practiced in ways other than specifically described, without departing from the scope and spirit of the present invention. Thus, embodiments of the present invention should be considered in all respects as illustrative and not restrictive. Accordingly, the scope of the invention should be determined not by the embodiments illustrated, but by the appended claims and their equivalents.

Claims

WHAT IS CLAIMED IS:

1 . A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device; receive a digital token from the first mobile device; verify the digital token; initiate a first charging session based upon a command contained within the digital token; with the internet connection not being available, end the first charging session; and store, in the memory, first charging session data for the first charging session, wherein the digital token is encrypted using a public key and is selfauthenticating without use of an internet connection.

2. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: authenticate a second mobile device via the low power short range point-to-point communication system; cause the storing of the first charging session data on the second mobile device for forwarding; initiate a second charging session; end the second charging session; and store, in the memory, second charging session data for the second charging session.

-55-

3. The system of claim 2, wherein the processor is further configured by the machine readable instructions to: use mobile device machine readable instructions on the second mobile device to send the first charging session data to a server system via an internet connection of the second mobile device.

4. The system of claim 2, wherein the processor is further configured by the machine readable instructions to: cause the storing of the second charging session data on the second mobile device for forwarding.

5. The system of claim 4, wherein the storing of the second charging session data on the second mobile device is responsive to the end of the second charging session.

6. The system of claim 4, wherein the processor is further configured by the machine readable instructions to: use mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

7. The system of claim 2, wherein causing the first charging session data to be sent to the second mobile device is performed via the low power short range point-to-point communication system.

8. The system of claim 1 , wherein the low power short range point-to-point communication system is a near field communication (NFC) system.

9. The system of claim 1 , wherein the EV charger access credentials comprise charger ID, time of day, and session time.

-56-

10. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: receive the authentication request from the first mobile device via the low power short range point-to-point communication system.

11 . The system of claim 1 , wherein verifying the digital token includes decrypting the digital token using cryptographic information contained within a digital certificate stored on the EV charger.

12. The system of claim 1 , wherein the digital token is bound to a specific time period.

13. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: receive a communication from the first mobile device to end the first charging session.

14. The system of claim 13, wherein the processor is further configured by the machine readable instructions to: decrypt the communication and to end the charging session.

15. The system of claim 14, wherein: the EV charger further comprises a locking mechanism; and the processor is further configured by the machine readable instructions to release the locking mechanism upon ending the charging session.

16. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: cause the storing of the first charging session data on the first mobile device for forwarding when a communication is received to end the first charging session.

-57-

17. The system of claim 16, wherein the processor is further configured by the machine readable instructions to: send the first charging session data to a server system via an internet connection of the first mobile device.

18. The system of claim 16, wherein the processor is further configured by the machine readable instructions to: decrypt the communication to end the first charging session; and end the first charging session.

19. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: send the first charging session data to another EV charger for forwarding.

20. The system of claim 1 , wherein the processor is further configured by the machine readable instructions to: receive a time of day from the first mobile device to update a time of day on the EV charger.

21 . A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: authenticate a first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device; receive a digital token from the first mobile device; verify the digital token;

-58- initiate a first charging session based upon a command contained within the digital token; with the internet connection not being available, end the first charging session; store, in the memory, first charging session data for the first charging session; authenticate a second mobile device via the low power short range point- to-point communication system; cause the storing of at least the first charging session data on the second mobile device for forwarding; initiate a second charging session; end the second charging session; and store, in the memory, second charging session data for the second charging session.

22. The system of claim 21 , wherein the processor is further configured by the machine readable instructions to: use a mobile device machine readable instructions on the second mobile device to send the first charging session data to a server system via an internet connection of the second mobile device.

23. The system of claim 21 , wherein the processor is further configured by the machine readable instructions to: cause the storing of the second charging session data on the second mobile device for forwarding.

24. The system of claim 23, wherein the processor is further configured by the machine readable instructions to: use a mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

25. The system of claim 23, wherein the storing of the second charging session data on the second mobile device is responsive to the end of the second charging session.

26. The system of claim 21 , wherein causing the first charging session data to be sent to the second mobile device is performed via the low power short range point-to-point communication system.

27. The system of claim 21 , wherein the low power short range point-to-point communication system is a near field communication (NFC) system.

28. The system of claim 21 , wherein the EV charger access credentials comprise charger ID, time of day, and session time.

29. The system of claim 21 , wherein the processor is further configured by the authentication software application to: receive an authentication request from the first mobile device via the low power short range point-to-point communication system.

30. The system of claim 21 , wherein verifying the digital token includes decrypting the digital token using cryptographic information contained within a digital certificate stored on the EV charger.

31 . The system of claim 21 , wherein the digital token is bound to a specific time period.

32. The system of claim 21 , wherein the first charging session data and/or the second charging session data comprise duration of the charging session, energy used during the charging session, a plug-in status, a status of the EV charger, diagnostics data, temperature data, and humidity data.

33. The system of claim 21 , wherein the first mobile device and the second mobile device are the same mobile device.

34. The system of claim 21 , wherein the first charging session data and/or the second charging session data comprise duration of the charging session, energy used during the charging session, and a plug-in status.

35. The system of claim 34, wherein the first charging session data and/or the second charging session data further comprise a status of the EV charger, diagnostics data, temperature data, and humidity data.

36. The system of claim 21 , wherein the digital token is encrypted using a public key.

37. The system of claim 21 , wherein the digital token is self-authenticating without use of an internet connection.

38. The system of claim 21 , wherein the processor is further configured by the machine readable instructions to receive a time of day from the first mobile device and/or the second mobile device to update a time of day on the EV charger.

39. A system for electric vehicle (EV) charging, the system comprising: an EV charger comprising a power management unit, a processor, a low power short range point-to-point communication system, and a memory containing machine readable instructions, the EV charger not having an internet connection available, the processor being configured by the machine readable instructions to: receive an authentication request from a first mobile device via the low power short range point-to-point communication system; authenticate the first mobile device via the low power short range point-to- point communication system in part by sending encrypted EV charger access credentials to the first mobile device; receive a digital token from the first mobile device, verify the digital token by decrypting the digital token using cryptographic information contained within a digital certificate; initiate a first charging session based upon a command contained within the digital token; with the internet connection not being available, end the first charging session; store, in the memory, first charging session data for the first charging session, wherein the digital token is bound to a specific time period, is encrypted using a public key, and is self-authenticating without use of an internet connection; authenticate a second mobile device via the low power short range point- to-point communication system; cause the first charging session data to be sent to the second mobile device via the low power short range point-to-point communication system; initiate a second charging session; end the second charging session; store, in the memory, second charging session data for the second charging session; cause the second charging session data to be sent to the second mobile device via the low power short range point-to-point communication system; and use mobile device machine readable instructions on the second mobile device to send the first charging session data and the second charging session data to a server system via an internet connection of the second mobile device.

-62-