System and method for authorizing an electric vehicle to receive charge at a charging station

Abstract

Systems, methods, and techniques that enable a first user (e.g., a driver) of an electric vehicle (EV) to pay, pre-pay, and / or authorize a payment to use an electric vehicle supply equipment (EVSE) to charge their EV. After the first user pays, pre-pays, and / or authorizes the payment, the systems, methods, and techniques determine an available EVSE to be utilized to start charging the EV within a future time. To ensure the availability of the EVSE, the systems, methods, and techniques may reserve the available EVSE and can generate an authorization code for initiating charging the EV at an EVSE. The authorization code may enable the first user or a second user (e.g., a valet) to use the reserved EVSE to start charging the EV within the future time.

Description

SYSTEM AND METHOD FOR AUTHORIZING AN ELECTRICVEHICLE TO RECEIVE CHARGE AT A CHARGING STATIONRELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 341 ,966, filed May 13, 2022, the entirety of which is incorporated by reference herein.TECHNICAL FIELD

[0002] The present disclosure generally relates to the field of configuring an electric vehicle supply equipment (EVSE). More particularly, the present disclosure describes systems, methods, and techniques for enabling a third party to charge an electrical vehicle (EV) at an EVSE.BACKGROUND

[0003] Driving an electric vehicle (EV) may include some remarkable benefits compared to driving a vehicle with a combustion engine. To this end, industry and academia strive to increase the benefits of driving the EV, in part, by providing access to an electric vehicle supply equipment (EVSE). Currently, the industry has adopted a level one (“Level 1”), a level two (“Level 2”), and a level three (“Level 3”) EVSE.

[0004] The Level 1 and Level 2 EVSEs supply an alternating current to the EV. When charging at a Level 1 or a Level 2 EVSE, the EV converts the alternating current (AC) to a direct current (DC) using an AC-to-DC converter located inside the EV (e.g., an onboard AC-to-DC converter) to charge a battery of the EV. In certain regions, such as in the United States of America, the Level 1 EVSE may be plugged, connected, and / or coupled (herein collectively may be referred to as “coupled”) to a 120 volts AC (VAC) receptacle. The 120 VAC receptacle may carry and / or support a relatively low amount of current (e.g., approximately 12 to 16 Amperes (A)). When using the Level 1 EVSE, the battery of the EV may receive approximately enough charge to enable the EV to drive six to eight kilometers (6 to 8 km) per hour spent charging at the Level 1 EVSE.

[0005] To increase the charging speed, a driver of the EV may utilize a Level 2 EVSE. In certain regions, the Level 2 EVSE may be coupled to a 240 VAC receptacle. When using the Level 2 EVSE, the battery of the EV may receive, for example,approximately enough charge to enable the EV to drive 20 to 100 kilometers per hour spent charging at the Level 2 EVSE. Therefore, the Level 2 EVSE may support considerably higher charging speeds compared to the Level 1 EVSE.

[0006] To increase the charging speeds even further than the Level 2 EVSEs, the driver of the EV may utilize a Level 3 EVSE. The Level 3 EVSE may be referred to as a “DC EVSE,” a “DC charging station,” or a “DC Fast Charging (DCFC) station.” The DC charging station utilizes DC charging. To do so, the DC charging station may perform an AC-to-DC power conversion before power enters the EV. Therefore, the DC charging stations may have an on-site AC-to-DC converter, which enables the DC charging station to bypass the onboard AC-to-DC converter of the EV, and the DC charging station can charge the battery of the EV directly.

[0007] The EVSEs may be installed at and / or in a public or private establishment, such as a public charging station, a public parking garage, a parking garage of an office building, a parking lot of a store, a parking garage of a restaurant, a parking lot of a manufacturing facility, a parking lot of a golf course, and / or so forth. To use a public EVSE, however, a user (e.g., a driver or a passenger of the EV) may need to pay for an access to the EVSE and for an electric charge received by the EV that is being charged using the EVSE. However, the establishments may not enable the user to pay for access to, and electric charge delivered by, an EVSE at a future time. Furthermore, the establishments may not enable another user (e.g., a valet) to charge the EV.SUMMARY

[0008] The present disclosure includes systems, methods, and techniques that enable a first user of an EV to pay, pre-pay, and / or authorize a payment to use an EVSE. After the first user pays, pre-pays, and / or authorizes the payment, the systems, methods, and techniques determine an available EVSE to be utilized to start charging the EV within a future time. To ensure the availability of the EVSE, the systems, methods, and techniques may reserve the available EVSE and generate an authorization code for charging the EV within the future time. The authorization code may enable the first user (e.g., a driver of the EV) or a second user (e.g., a valet) to use the reserved EVSE to start charging the EV within the future time.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present embodiments will become more fully apparent from the following description, taken in conjunction with the accompanying drawings. Understanding that the accompanying drawings depict only typical embodiments, and are, therefore, not to be considered limiting of the scope of the disclosure, the embodiments will be described and explained with specificity and detail in reference to the accompanying drawings.

[0010] FIG. 1 illustrates an example system for charging an EV, according to one embodiment.

[0011] FIG. 2 illustrates a diagram of a kiosk that enables a person associated with an EV to pay, pre-pay, and / or authorize a payment to use an available EVSE to charge the EV, according to one embodiment.

[0012] FIG. 3 illustrates a method by which a person associated with an EV can pay, pre-pay, and / or authorize a payment to use an available EVSE to charge the EV, according to one embodiment.

[0013] FIG. 4 illustrates an environment where a valet charges an EV using an available EVSE, according to one embodiment.DETAILED DESCRIPTION

[0014] This disclosure discusses systems, methods, and techniques for charging an EV using an EVSE. According to one embodiment, a system for charging an EV system includes at least one EVSE. The system may include a processor to execute instructions that may be stored on a computer-readable medium. The instructions facilitate the system to enable a user to authorize a payment using an account management system. Then, the system may be configured to determine an available EVSE to start charging the EV within a future time. The system may also be configured to reserve for a reservation time period and may generate an authorization code that may be valid from at least a present time to the future time.

[0015] According to another embodiment, a computer-implemented method for charging an EV may include authorizing a payment for charging the EV using an EVSE. The computer-implemented method may also include determining an available EVSE of one or more EVSEs to start charging the EV within a future time. After determining the available EVSE, the computer-implemented method may includegenerating an authorization code for initiating a charging of the EV within the future time.

[0016] In some embodiments, a system, an apparatus, an application software, modules of the application software, an algorithm, a model, means, and / or a combination thereof include performing the computer-implemented method mentioned above. For example, an apparatus may include at least one communication interface to communicate with the EVSE using a communication protocol. The apparatus may also include at least one processor and at least one computer-readable medium. The computer-readable medium may include instructions that, responsive to execution by the processor, may cause the apparatus to perform the computer-implemented method mentioned above.

[0017] This disclosure includes simplified concepts for using EVSEs (or charging stations) to charge the EVs, which is further described below. For brevity and ease of description, the disclosure focuses on a first user paying, pre-paying, and / or authorizing a payment to charge an EV by using an available EVSE. After the first user pays, pre-pays, and / or authorizes the payment, a second user may charge the EV using the available EVSE. However, the techniques, method, and systems described herein are not limited to EVs and / or EVSEs. Therefore, the techniques, method, and systems described herein may be used to pay, pre-pay, and / or authorize a payment for a variety of services and / or goods.

[0018] It will be readily understood that the components of the embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of various embodiments, as represented in the figures, is not intended to limit the scope of the disclosure, as claimed, but is merely representative of various embodiments. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0019] Moreover, the phrases “connected to” and “coupled to” are used herein in their ordinary sense and are broad enough to refer to any suitable coupling or other forms of interaction between two or more entities, including electrical, mechanical, fluid, and / or thermal interaction. Two components may be coupled to each other even though they are not in direct contact with each other. The phrase “attached to” refers to interaction between two or more entities that are in direct contact with each otherand / or are separated from each other only by a fastener of any suitable variety (e.g., an adhesive).

[0020] The terms “a” and “an” can be described as one, but are not limited to one. For example, although the disclosure may recite an element having, e.g., “a line of stitches,” the disclosure also contemplates that the element can have two or more lines of stitches.

[0021] Unless otherwise stated, all ranges include both endpoints and all numbers between the endpoints.

[0022] For consistency and broad international understanding, throughout this disclosure, units of measurements may be expressed using le Systeme International d’Unites (the International System of Units, abbreviated from the French as the “SI” units), or may be colloquially referred to as the “metric system.” In addition to, or alternatively of, it is to be understood that the techniques and systems described herein may operate using other units, for example, units defined in the United States Customary System (USCS).

[0023] The terms “charge,” “energy,” and “power,” for example, “electric charge,” “electric energy,” and “electric power,” may be used interchangeably, in part, because these terms may be related. Further, the terms “power” and / or “electric power” may be expressed in units of Watts (W) and / or a derivative thereof, for example, kilowatt (kW), kilowatt-hour (kWh), and so forth. Persons having ordinary skill in art can infer and / or differentiate these terms based on context, industry usage, academic usage, linguistic choice, and / or other factors.

[0024] For decimal separators and thousand(s) separators, this disclosure generally uses an English-speaking (e.g., the United States of America) number formatting instead of, for example, a Continental-European number formatting. As such, two dollars and thirty-two cents may be written as “$2.32.” Similarly, two euros and thirty-two cents may also be written as “€2.32.” Also, when using the USCS units, one million and ninety-two pounds (e.g., weight units in USCS) may be written as “1 ,000,092 lb.” Likewise, even when using the SI units, one million and ninety-two kilograms may also be written as “1 ,000,092 kg.”

[0025] Reference throughout this specification to “an embodiment” or “the embodiment” means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Thus, the quoted phrases, or variations thereof, as recited throughout this specification are notnecessarily all referring to the same embodiment. Not every embodiment is shown in the accompanying illustrations; however, at least a preferred embodiment is shown. At least some of the features described for a shown preferred embodiment are present in other embodiments.

[0026] Alternatively of, or in addition to, the terms “an embodiment” or “the embodiment,” this disclosure may also include the terms “an aspect” or “the aspect,” depending on a linguistic choice, for example, to lower the repetitiveness of the terms “an embodiment” or “the embodiment.” Therefore, the terms “an aspect” and “an embodiment” may be synonymous with each other.

[0027] The term electric vehicle (EV), as used herein, refers to a motorized vehicle deriving locomotive power, either full-time or part-time, from an electric system onboard the motorized vehicle. By way of non-limiting examples, an EV may be an electrically powered passenger vehicle for road use; an electric scooter; an electric forklift; a cargo-carrying vehicle powered, full-time or part-time, by electricity; an offroad electrically powered vehicle; an electrically powered watercraft; and so forth. The EV may also utilize an autonomous-driving application software and / or driverassistance application software.

[0028] The term electric vehicle supply equipment (EVSE), as used herein, refers to equipment by which an EV may be charged or recharged. An EVSE may comprise or be coupled to a computing system whereby service to the EV is provisioned, optionally, according to parameters (e.g., operator-selectable parameters). Also, an EVSE may comprise a means of providing cost accounting and may further comprise a payment acceptance component. An EVSE may be installed at a home of an owner / operator of an EV, at a place of business for an owner / operator of an EV, at a fleet facility for a fleet comprising one or more EVs, at a public charging station, etc. The present disclosure uses the terms EVSE and “charging station” interchangeably. Where appropriate, however, the present disclosure differentiates an AC charging station from a DC charging station.

[0029] In one aspect, information regarding the SoC of the EV may be obtained from a computing device, such as an in-vehicle infotainment (IVI) system, a smartphone, a tablet, a server, and / or so forth. The computing device may also include a user interface (III) and may store a media access control (MAC) address of the EV. Embodiments of the present disclosure include application software that may associate this MAC address of the EV with a profile of the EV stored in a database.

[0030] The application software may be configured to detect changes of the profile of the EV, such as a change in the SoC of the battery (e.g., 10%, 25%, 50%, 75%, 90%, full charge) in real time, in near real time, and / or in time intervals (e.g., every T minute(s), where T is a positive integer). This detection may be transmitted to and / or from the EV, the EVSE (e.g., the DC charging station), and / or a network of EVSEs using various wired and / or wireless communication protocols and / or standards.

[0031] The embodiments of the disclosure can be understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments. In addition, the steps of a method do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified. Further, while the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale, unless specifically indicated.

[0032] FIG. 1 illustrates an example system 100 for charging an EV, according to one embodiment. A first user 102-1 (e.g., a driver, an owner) of an EV 104 may desire to charge the EV 104 using an available EVSE. For example, the system 100 may include a first EVSE 106, a second EVSE 108, and / or additional EVSEs (not illustrated in FIG. 1 ). In such a case, the first EVSE 106, the second EVSE 108, and / or the additional EVSEs may be part of a plurality of EVSEs. The EVSEs may be installed at and / or in an establishment, such as a public charging station, a public parking garage, a parking garage of an office building, a parking lot of a store, a parking garage of a restaurant, a parking lot of a manufacturing facility, a parking lot of a golf course, and / or another establishment, including such as may be accessible for use by a general public user. Furthermore, each EVSE may include a code scanner, a number pad, a keyboard, an RFID reader, or a combination thereof that, in part, enables a user to access the EVSE and initiate a charging of the EV.

[0033] In one aspect, the EVSE 106 may have a first location, and the EVSE 108 may have a second location. At the first location, the first EVSE 106 may be coupled to a first distribution line of a power grid, a first transformer of the power grid, a firstswitchgear of a first establishment (e.g., a first public charging station), a first circuit breaker inside the first switchgear, and / or so forth. Similarly, at the second location, the second EVSE 108 may be coupled to a second distribution line of the power grid, a second transformer of the power grid, a second switchgear of a second establishment, a second circuit breaker inside the second switchgear, and / or so forth. In another aspect, the EVSEs 106, 108 may be co-located and may receive AC power from a same distribution line of the power grid, a same transformer of the power grid, a same switchgear of a same establishment, a same circuit breaker inside the same switchgear, and / or so forth.

[0034] In some embodiments, the first user 102-1 may want to authorize a second user 102-2 to charge the EV 104 using the available EVSE (e.g., the EVSE 106 or the EVSE 108). For example, the first user 102-1 may be a driver and / or an owner of the EV 104, and the second user 102-2 may be a valet who may be working at an establishment. As another example, the first user 102-1 may be a parent of the second user 102-2, and the second user 102-2 may be a teenager who may drive the EV 104 but may not have the necessary monetary funds to pay for access to the EVSE 106, the EVSE 108, and / or the system 100. As yet another example, the first user 102-1 may be an owner and / or a driver of the EV 104, and the second user 102-2 may be a passenger of the EV 104 who may volunteer to charge the EV 104 while the first user 102-1 performs another activity (e.g., attends a business meeting, runs an errand, goes to an appointment, and / or so forth). The system 100 can enable the first user 102-1 to provide a payment or a payment mechanism for paying for the charging and the system can generate an authorization code, which can be transferrable to the second user 102-2, to enable the second user 102-2 to initiate charging the EV at an available (and / or potentially reserved) EVSE 106, 108. The authorization code may be transferred to the second user 102-2 such as by a physical transfer (e.g., a coupon or ticket with the code written or typed, a visual presentation on a display, an audible presentation, etc.) and / or an electronic transfer (e.g., via wireless protocol, over a communication network, etc.). The transfer medium for transfer of the authorization code may be temporary and disposable such that the authorization code can be easily and simply discarded upon use and / or expiration. The authorization code may be active, functional, or otherwise operable for a limited future time, such as an expiration period. In a valet parking scenario, the authorization code may expire within a relatively short expiration period (e.g., 10-15 minutes) that may be long enough toallow the second user 102-2 to park the vehicle, and also not so long as to allow an unintended person to use the authorization code were it to be inadvertently or unintentionally lost, stollen, or otherwise not actually activated by the intended second user. The authorization code may be generally operable with a set or class of EVSE, such as an available EVSE of a plurality of EVSE at an establishment. The authorization code may be specifically operable with only a single reserved or otherwise specified EVSE selected from a plurality of EVSE at an establishment. The authorization code may be limited use so as to be single use. The authorization code may be limited use so as to be limited to a particular type, class, network, and / or other grouping of EVSE.

[0035] In one aspect, the system 100 may utilize a first computing device 110 (computing device 110) that may be accessed by, used by, or associated with the first user 102-1 and / or the EV 104. In addition, the system 100 may also utilize a second computing device 112 (computing device 112) that may be accessed by, used by, or associated with the second user 102-2 and / or the EV 104. The computing devices 110 and 112 may be implemented as any suitable computing or other electronic device. For example, the computing devices 110 and 112 may be or may include a smartphone, a near field communication (NFC) technology such as a radio-frequency identification (RFID) technology, an in-vehicle infotainment (IVI) system, a navigation device, a media device, a laptop computer, a network-attached storage (NAS) device, a desktop computer, a tablet computer, a computer server, a smart appliance, a cellular base station, a broadband router, an access point, a gaming device, an internet-of-things (loT) device, a sensor, a security device, an asset tracker, a fitness management device, a wearable device, a wireless power device, and so forth. In some embodiments, the IVI system and its associated user interface (III) may enhance a driving or riding experience by incorporating features, such as a state of charge (SoC) of a battery of the EV 104, navigation, directions to an available EVSE (e.g., EVSE 106 and / or EVSE 108), parking information, parking assistance, traffic information, a rear dashcam, handsfree phone, radio stations, and / or other features. For these features, the computing devices 110 and 112 may also utilize navigation, autonomous-driving, driver-assistance, and / or other application software.

[0036] In some embodiments, each of the computing devices 110 and 112 may include a display screen (e.g., a touchscreen), at least one camera, and / or other components (e.g., a microphone, a speaker). Furthermore, each of the computingdevices 110 and 112 may also include at least one application processor (processor) and at least one computer-readable medium.

[0037] In some embodiments, the system 100 may include at least one database 114 and at least one system computing device 116. The database 114 may store data from or used by the first user 102-1 , the EV 104, the second user 102-2, the EVSE 106, the EVSE 108, other EVSEs not illustrated in FIG.1 , the computing device 110, the computing device 112, and / or the system computing device 116. The data stored in the database 114 may be data associated with the first user 102-1 , the second user 102-2, the EV 104, the EVSEs 106,108, and / or the system computing device 116. For example, the data stored in the database 114 may include financial (or purchasing) data of an account management system that may be associated with the first user 102-1 , the EVSEs, the computing device 110, the computing device 112, the system computing device 116, the system 100, an application software that may associated with the EVSEs (EVSE application software), and / or a combination thereof. As another example, the data stored in the database 114 may include information regarding a make, a model, a vehicle identification number (VIN), a license plate, a MAC address, a state of charge (SoC), and / or so forth of the EV 104. As yet another example, the data stored in the database 114 may include data associated with the EVSEs 106, 108 and / or additional EVSEs, such as an availability of each EVSE (e.g., the EVSE(s) that is / are currently not being utilized), a reservation of an EVSE to be utilized at a future time, utilization data of each EVSE (e.g., which EVSE tends to be used more often), an amount of power (e.g., kW, kWh) being delivered by each EVSE, an amount of currency (e.g., $, €, and / or so forth) being charged to the first user 102- 1 , and / or so forth.

[0038] In some embodiments, the system computing device 116 may be a remote computing device, such as a server, a controller, a cloud computer, and / or so forth. In such a case, the first user (e.g., the first user 102-1 of FIG. 1 ) may utilize their smartphone (e.g., the computing device 110 of FIG. 1 ) to establish a communication connectivity and communicate with the system computing device 116. The system computing device 116 may be associated with, part of, and / or embedded in the system 100. The system computing device 116 may also communicate with the EV 104, the EVSE 106, the EVSE 108, the computing device 110, the computing device 112, and / or the database 114 directly and / or via a network 118.

[0039] In some embodiments, the network 118 may facilitate communication between an EV (e.g., EV 104), an EVSE (e.g., EVSE 106, EVSE 108), the database 114, the computing device 110, the computing device 112, the system computing device 116, a satellite(s) 120, and / or a base station(s) 122. Communication(s) in the system 100 may be performed using various protocols and / or standards. Examples of such protocols and standards include an Open Charge Point Protocol (OCPP), such as OCPP 1.6, OCPP 2.0, OCPP 2.0.1 ; a 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) standard, such as a 4th Generation (4G) or a 5th Generation (5G) cellular standard; an Institute of Electrical and Electronics (IEEE) 802.11 standard, such as IEEE 802.11 g, ac, ax, ad, aj, or ay (e.g., Wi-Fi 6® or WiGig®); an IEEE 802.16 standard (e.g., WiMAX®); a Bluetooth Classic® standard; a Bluetooth Low Energy® or BLE® standard; an IEEE 802.15.4 standard (e.g., Thread® or ZigBee®); other protocols and standards established or maintained by various governmental, industry, and / or academia consortiums, organizations, and / or agencies; and so forth. Therefore, the network 118 may be a cellular network, the Internet, a wide area network (WAN), a local area network (LAN), a wireless LAN (WLAN), a wireless personal-area-network (WPAN), a mesh network, a wireless wide area network (WWAN), a peer-to-peer (P2P) network, and / or a Global Navigation Satellite System (GNSS) (e.g., Global Positioning System (GPS), Galileo, Quasi-Zenith Satellite System (QZSS), BeiDou, GLObal NAvigation Satellite System (GLONASS), Indian Regional Navigation Satellite System (IRNSS), and so forth). Communication can also be provided via email, file transfer protocol (FTP), hyper text transport protocol (HTTP) such as via a link, or the like.

[0040] In addition to, or alternatively of, the communications illustrated in FIG. 1 , the system 100 may facilitate other unidirectional, bidirectional, wired, wireless, direct, and / or indirect communications utilizing one or more communication protocols and / or standards. Therefore, FIG. 1 does not necessarily illustrate all communication signals. In some embodiments, the computing device 110 communicates with the EV 104, the EVSE 106, the EVSE 108, the computing device 110, and / or the system computing device 116 directly (e.g., via Bluetooth Classic® or a different short-range communication protocol) and / or indirectly (e.g., via the network 118).

[0041] It is to be understood that the EV 104, the EVSE 106, the EVSE 108, the computing device 110, the computing device 112, the database 114, the system computing device 116, the network 118, the satellite 120, the base station 122, andother elements in the system 100 that may not be explicitly illustrated in FIG. 1 include appropriate wired and / or wireless communication interfaces to accommodate the abovementioned communication protocols and / or standards. Next, the description partly focuses on the first user 102-1 using a retail kiosk to pay for access to an available EVSE (e.g., the EVSE 106, the EVSE 108, or any other EVSE).

[0042] FIG. 2 illustrates a diagram 200 of a retail kiosk 202 (kiosk 202) that enables a first user (e.g., the first user 102-1 of FIG. 1 ) to pay, pre-pay, and / or authorize a payment to use an available EVSE to charge their EV (e.g., the EV 104 of FIG. 1 ), according to one embodiment. The kiosk 202 may include a human-machine interface 204 (HMI 204), a display screen 206, a payment terminal 208, a communication interface 210, at least one application processor 212 (processor 212), at least one computer-readable medium 214, and / or more components that may not be explicitly illustrated in FIG. 2.

[0043] FIG. 2 is partly described in the context of FIG. 1 . For example, the system computing device 116 of FIG. 1 may be part of, embedded in and / or on, associated with, and / or communicating with the kiosk 202. As another example, the kiosk 202 may utilize the EVSE application software. Therefore, in some embodiments, this disclosure may describe and / or refer to the kiosk 202 of FIG. 2, the system computing device 116 of FIG. 1 , and the EVSE application software, interchangeably.

[0044] In some embodiments, the EVSE application software may include a first mode of operation and a second mode of operation. For example, the first mode of operation may enable immediate (instead of at a future time) initiation of charging the EV. The first mode may place more emphasis on the driver (instead of, for example, a valet) charging the EV. As another example, the second mode of operation may enable charging the EV at a future time by, in part, utilizing an authorization code, as is further described herein. The second mode of operation may place more emphasis on the valet (or a second user) charging the EV. Generally, this disclosure may place more emphasis on the second mode of operation of the EVSE application software.

[0045] The kiosk 202 may be located at an accessible location of an establishment (e.g., at a central location), such as at an entrance of a public charging location, a public parking garage, a parking garage of an office building, a parking lot of a store, a parking garage of a restaurant, a parking lot of a manufacturing facility, a parking lot of a golf course, and / or so forth. In addition, the kiosk 202 may be attended (e.g., bythe second user 102-2 of FIG. 1 ) may be unattended (e.g., self-serving, used by the first user 102-1 of FIG. 1 ), may be attended for a first example service (e.g., using a valet to park the EV), may be unattended for a second example service (e.g., paying for parking, paying for access to an available EVSE, and so forth), may be attended during a first example time period of the day (e.g., 8:00 AM to 6:00 PM), may be unattended during a second example time period of the day (e.g., 6:00 PM to 8:00 AM), a combination thereof, and / or so forth.

[0046] In some embodiments, for example, as a user (e.g., the first user 102-1 ) drives, rides, and / or walks to, adjacent to, and / or near (collectively may be referred to as “approaches”) the kiosk 202, the user may utilize the HMI 204 to interact with the kiosk 202 of FIG. 2 (and / or the system computing device 106 of FIG. 1 ). The HMI 204 may enable the user to choose from a list of possible requests, such as a request to access to an available EVSE and for the EV to receive electric charge delivered by the EVSE, a request to use an available parking spot, a request for a valet service, a request for a parking spot with access to an available EVSE (e.g., a parking spot that includes an EVSE), and / or so forth.

[0047] In one aspect, the display screen 206 may be a touchscreen that may utilize any type of touchscreen technology, such as a resistive touchscreen, a surface capacitive touchscreen, a projected capacitive touchscreen, a surface acoustic wave (SAW) touchscreen, an infrared (IR) touchscreen, and so forth. In such a case, the display screen 206 may be integrated with the HMI 204 into a single unit, enabling the first user to choose from the list of possible requests by touching the display screen 206. The HMI 204 may comprise a printer for printing information, including an authorization code generated by the authorization code generation module 224.

[0048] In some embodiments, the payment terminal 208 may be integrated with or separate from the HMI 204 and / or the display screen 206. The payment terminal 208 may enable the first user (e.g., the first user 102-1 of FIG. 1 ) to pay for a service that the first user may have requested, for example, using the HMI 204 (and / or the display screen 206). The requested service may include paying, pre-paying, and / or authorizing a payment to access an available EVSE and an electric charge delivered by the available EVSE. For clarity, the payment terminal 208 may accept one or more forms of payment, such as a credit card, a debit card, a digital wallet, a cryptocurrency, a bank account, a paper currency, a coin currency, and / or so forth. Furthermore, the payment terminal 208 may be configured to accept one or more types of currencies(e.g., $, €, ¥, £, and / or so forth). It is to be understood, that the payment terminal 206 (and any method, technique, system, and / or apparatus described herein) may be configured to conform with local (e.g., city), state, country, and / or international regulations. For example, the payment terminal 208 may be configured to accept an anonymous payment(s) from a user (e.g., the first user 102-1 of FIG. 1 ).

[0049] In addition, the payment terminal 208 may be configured to print or email a receipt, a link to a virtual receipt, a coupon, instructions for the first user (e.g., the first user 102-1 , the driver of the EV 104), instructions for a second user (e.g., the second 102-2, a valet, and / or so forth), a map (e.g., the map may display a location of an available EVSE), an authorization code for starting to charge the EV 104 within a future time and at the available EVSE, and / or so forth. The authorization code may be a number, an alphanumeric code, a word, a phrase, a quick response (QR) code, a combination thereof, and / or so forth. Furthermore, the authorization code may be used for only a limited time period, as is further described herein.

[0050] For example, the instructions for the first user may be printed on a coupon and / or receipt and may include phrases, such as or to the effect of: “Thank you for choosing Location “P” to charge your EV. Please give the authorization code to the valet. The valet will use this authorization code to charge your EV. The authorization code is valid for the next fifteen (15) minutes.” Note that “P” may stand for or may denote an integer, an address, the name of the establishment, and / or so forth. Also, in this and other examples, the code may be valid for any configurable period of time as appropriate to allow time for the EV to be parked and charging to initiate, while also not unnecessarily tying up a resource if the EV is not in fact parked to be charged.

[0051] As another example, the instructions for the second user may be printed on the same or a different coupon and may include phrases, such as or to the effect of: “Charge the EV at the EVSE “M” of the Location “P.” The EVSE “M” is located on the Nth Floor of the Location “P.” The authorization code is valid for the next fifteen (15) minutes.” Note that “N” may stand for an integer and the floor may be above ground or underground. Also, “M” may stand for an integer greater than zero (0). It is to be understood that the second user (e.g., the valet) does not need to pay for charging the EV (e.g., the EV 104 of FIG. 1 ) because the first user has already pre-paid and / or has already authorized a payment to charge the EV by utilizing the kiosk 202 of FIG. 2 and / or by utilizing the system computing device 116 of FIG. 1.

[0052] In some embodiments, the communication interface 210 of the kiosk 202 may be a wired, a wireless, or a combination thereof communication interface. Furthermore, the communication interface 210 may enable the kiosk 202 to communicate with an EV (e.g., the IVI system of the EV 104 of FIG. 1 ), an EVSE (e.g., the EVSE 106, the EVSE 108), a computing device (e.g., a smartphone, the computing device 110, the computing device 112), the system computing device 116, the database 114 and / or a network (e.g., the network 118) using any of the forementioned communication protocols and / or standards.

[0053] In some embodiments, the computer-readable medium 214 includes instructions 216 (e.g., code, pseudocode, algorithms, application software, configurations, and / or so forth) that may be executed by the processor 212. In addition, the computer-readable medium 214 may include or may access purchasing data 218 that may be associated with the account management system. For example, the account management system may enable the kiosk 202 of FIG. 2, the system computing device 116 of FIG. 1 , the system 100 of FIG. 1 , and / or so forth to calculate a cost (e.g., in $, €, ¥, £, etc.) of an amount of power (e.g., in kW, in kWh) delivered by the available EVSE charging the EV. As another example, the account management system may enable the payment terminal 208 of the kiosk 202 in FIG. 1 , the system computing device 116 of FIG. 1 , the system 100 of FIG. 1 , and / or so forth to enable the first user to authorize a payment. As yet another example, the account managements system may enable the first user or a second user (e.g., a valet of a public establishment) to charge the EV using the available EVSE by, for example, the first user or the second user presenting the coupon and / or the receipt to the available EVSE.

[0054] In some embodiments, the kiosk 202 of FIG. 2, the system computing device 116 of FIG. 1 , and / or the system 100 may utilize an availability module 220, a reservation module 222, and an authorization code module 224. For clarity, aspects of certain embodiments described herein may be implemented as software modules, such as the availability module 220, the reservation module 222, the authorization code module 224, and / or other software modules. The availability module 220, the reservation module 222, the authorization code module 224, and / or any other software module may include any type of instruction, computer instruction, and / or computerexecutable code, pseudocode, algorithms, application software, configurations, and / orso forth that may be located within or on a computer-readable storage medium, such as the computer-readable medium 214, and / or any other computer-readable medium.

[0055] Furthermore, a particular software module may comprise disparate instructions stored in different locations of a computer-readable storage medium, which together implement the described functionality of the module. Indeed, a software module may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several computer-readable storage media. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules may be located in local and / or remote computer-readable storage media. In addition, data being tied or rendered together in a database record may be resident in the same computer-readable storage medium, or across several computer-readable storage media, and may be linked together in fields of a record in a database (e.g., the database 114) across a network (e.g., the network 118).

[0056] In some embodiments, the kiosk 202 and / or the system computing device 116 of FIG. 1 may include the availability module 220 to find and / or determine an available EVSE (e.g., EVSE 106, EVSE 108, or another EVSE not explicitly illustrated in any of the figures) to initiate charging the EV (e.g., the EV 104) within a future time (e.g., within five, ten, fifteen, twenty, and so forth minutes). Note that the future time may be set by an administrator and / or an operator of the kiosk 202, the system computing device 116, the system 100, and / or the EVSE application software. The EVSE application software may be stored on, utilized by, and / or accessed by kiosk 202 of FIG. 2, the system computing device 116 of FIG. 1 , the computing devices 110 and 112 of FIG. 1 , the EVSEs of FIG.1 , the database 114, the account management system, and / or a combination thereof.

[0057] In some embodiments, the kiosk 202, the system computing device 116 of FIG. 1 , and / or the EVSE application software may include the reservation module 222 to reserve the available EVSE for the future time and for a charging time period (e.g., one hour) after the future time. Therefore, a reservation time period (reservation) may be longer than the future time. For example, if the future time is set at fifteen (15) minutes, and the charging time period is set at one (1 ) hour (or 60 minutes), then, the reservation is for 75 minutes from a present time. As another example, if the futuretime is set at fifteen (15) minutes, but the EV initiates charging sooner, for example, in five (5) minutes, and the charging time period is set at one (1 ) hour, then, the reservation time is for 65 minutes from the present time. Furthermore, to notify other users (e.g., other drivers of other EVs), a reserved EVSE may display on a display screen (not illustrated) of the reserved EVSE a phrase, such as or to the effect of: “Reserved” or “Reserved until 3:32 PM,” for example. As another example, after a user reserves the available EVSE, the reserved EVSE may require an authorization code to charge the EV during the reservation, as is further described herein.

[0058] To this end, in some embodiments, the kiosk 202 and / or the system computing device 116 of FIG. 1 may utilize the authorization code generation module 224 to generate an authorization code for charging the EV within (or at) the later time and at the available EVSE. The authorization code may be valid from at least a present time to the future time. The future time may be a reservation time. The future time may comprise time for the second user 102-2 to take the EV to the reserved and / or available EVSE. The future time may allow time for the EV to completely charge. The future time may be a limited expiration period of a duration to allow only the second user 102-2 to initiate charging of the EV at the EVSE. Such expiration period may be a duration significantly shorter than a time period for charging the EV at the EVSE.

[0059] The first user may then share the authorization code with a second user (e.g., the second user 102-2, a valet at the establishment, a passenger of the EV 104, and so forth). By so doing, the second user may use the authorization code to charge the EV at the available EVSE, as is further described below. The authorization code may be transferred to the second user 102-2 such as by a physical transfer (e.g., a coupon or ticket with the code written or typed, a visual presentation on a display, an audible presentation, etc.) and / or an electronic transfer (e.g., via wireless protocol, over a communication network, etc.). The transfer medium for transfer of the authorization code may be temporary and disposable such that the authorization code can be easily and simply discarded upon use and / or expiration. The authorization code may be active, functional, or otherwise operable for a limited future time, such as an expiration period. In a valet parking scenario, the authorization code may expire within a relatively short expiration period (e.g., 10-15 minutes) that may be long enough to allow the second user 102-2 to park the EV, and also short enough to limit any unintended person from using the authorization code, such as were it to beinadvertently or unintentionally lost, stollen, or otherwise not actually activated by the intended second user 102-2. The expiration of the authorization code after an expiration period can provide a tighter control for ensuring that the authorization to begin charging is in fact used by the second user 102-2 (e.g., valet) to charge the EV being parked, thus providing the first user 102-1 greater confidence and piece of mind that a payment for authorizing charging is being used as desired to charge an intended EV.

[0060] The authorization code may be generally operable with a set or class of EVSE, such as an available EVSE of a plurality of EVSE at an establishment. The authorization code may be specifically operable with only a single reserved or otherwise specified EVSE selected from a plurality of EVSE at an establishment. The authorization code may be limited use so as to be single use. The authorization code may be limited use so as to be limited to a particular type, class, network, and / or other grouping of EVSE. Next, the description partly focuses on a method that enables the first user to authorize the second user to charge the EV at an available EVSE.

[0061] FIG. 3 illustrates a method 300 that enables a person associated with the EV to pay, pre-pay, and / or authorize a payment to use an available EVSE to charge their EV. In one aspect, the person associated with the EV may be considered a first user of the EV, such as the first user 102-1 of FIG. 1 , the driver of the EV 104 of FIG. 1 , the owner of the EV 104 of FIG. 1 , and / or so forth.

[0062] FIG. 3 is partly described in the context of FIGS. 1 and 2. In addition, the steps, the stages, and / or the blocks of the method 300 do not necessarily need to be executed in any specific order, or even sequentially, nor need the steps be executed only once, unless otherwise specified. Furthermore, the method 300 can be utilized by using one, more than one, and / or all the steps, stages, and / or blocks that are illustrated in FIG. 3. Therefore, the method 300 does not necessarily include a minimum, an optimal, or a maximum number of steps, stages, and / or blocks that are needed to implement the systems, methods, and techniques described herein. For clarity, the method 300 illustrates one embodiment.

[0063] At stage 302, the first user may scan a first QR code using a camera of a computing device, such as a camera of a first user’s smartphone. For clarity, the computing device of the first user may also include at least one display screen and may be the same and / or equivalent to the computing device 110 of FIG. 1 . The first QR code may be located at an establishment with at least one EVSE. For example,the first QR code may be printed on a laminated label at an entrance of the establishment. As another example, the first QR code may be displayed on a display screen, for example, the display screen 206 of the kiosk 202 of FIG. 2.

[0064] After the first user scans the first QR code, at stage 304, the computing device of the first user (e.g., the computing device 110 of the first user 102-1 ) may open the EVSE application software. In some embodiments, the EVSE application software may be a web-based application software. Also, as forementioned, the EVSE application software may be stored on, utilized by, and / or accessed by kiosk 202 of FIG. 2, the system computing device 116 of FIG. 1 , the computing devices 110 and 112 of FIG. 1 , the EVSEs of FIG.1 , the database 114, the account management system, and / or a combination thereof.

[0065] After opening the EVSE application software, at stage 306, the EVSE application software may prompt the first user to pay, pre-pay, and / or authorize a payment using the account management system. In some embodiments, as forementioned, the account management system may also include and / or use financial (or purchasing) data associated with the first user (e.g., a credit card, a bank account, a debit card).

[0066] In some embodiments, after the EVSE application software and / or the account management system approves the payment, for example, approves a credit card, a debit card, a digital wallet, a cryptocurrency, a bank account, and / or so forth, at stage 308, the application software may find and / or determine an available EVSE to start charging the EV within a future time (e.g., within five, ten, fifteen, twenty, and so forth minutes).

[0067] In some embodiments, at stage 310, the application software may reserve the available EVSE for a reservation time period. Therefore, after the stage 310, the EVSE may no longer be considered available but may be considered a reserved EVSE. The reserved EVSE may be utilized after a user inputs, displays, shows, and so forth an authorization code to the reserved EVSE.

[0068] To this end, in some embodiments, at stage 312, the EVSE application software generates the authorization code for charging the EV at the reserved EVSE. The authorization code may be a second QR code, a number, an alphanumeric code, a word, a phrase, or a combination thereof. Further, the EVSE application software may display the authorization code on a display screen of the computing device of the first user (e.g., the computing device 110 of the first user 102-1 of FIG. 1 ). Theauthorization code may be valid from at least a present time to the future time. Therefore, unlike the first QR code described at stage 302, the authorization code that is generated at stage 312 may be a temporary authorization code.

[0069] After stage 312, the first user may share the authorization code with a second user (e.g., a valet), as is further described partly in regard to FIG. 4.

[0070] FIG. 4 illustrates an environment 400 where a valet charges the EV, according to one embodiment. In the illustrated environment 400, the valet 402-2 may assume control of an EV from a driver 402-1 for a limited time primarily for purposes of parking the EV, and the driver 402-1 or other owner of the EV may desire that the EV charge while parked. In order for the EV to charge while parked, the valet 402-2 will initiate charging.

[0071] The environment 400 depicted includes a dense city that may have a considerably costly real estate, such as New York, London, Tokyo, Hong Kong, Paris, and so forth. While the disclosed embodiments are useful in a dense city environment, the disclosure is not limited to such and the disclosed embodiments can be useful and / or implemented in other environments. In the environment 400, a driver 402-1 (or a first user 402-1 ) of an EV 404 may rely on a valet 402-2 (or a second user 402-2) working at a building 406 to park the EV 404 at and / or in a parking lot (not illustrated) associated with building 406. The parking lot may be an underground parking of the building 406; the building 406 may be a multistory parking structure; the parking lot may be near the building 406; and / or so forth. Additionally, or alternatively, the driver 402-1 may desire to ask the valet 402-2 to charge EV 404 using an available EVSE that may be located at the parking lot or may be located near the parking lot.

[0072] In some embodiment, as the driver 402-1 approaches an entrance of the building 406, the driver 402-1 may use a camera of the computing device 110 of FIG. 1 to scan a first QR code that may be displayed at the entrance of the building 406. After the driver 402-1 scans the first QR code, the computing device 110 may open the EVSE application software. Alternatively, the driver 402-1 may have already installed the EVSE application software on the computing device 110 of FIG. 1 , and the driver 402-1 may not need or may elect not to use the first QR code to utilize the EVSE application software.

[0073] In some embodiments, the kiosk 202 of FIG. 2 may be located at the entrance of the building 406. In such a case, the driver 402-1 may utilize the kiosk 202 to pay, pre-pay, and / or authorize a payment to use an available EVSE. Therefore, thedriver 402-1 may first utilize any technique, method, system, and / or apparatus described herein to pay, pre-pay, and / or authorize a payment for the available EVSE and the electric charge delivered by the EVSE to the EV 404.

[0074] In some embodiments, after the driver 402-1 pays, pre-pays, and / or authorizes the payment using the account management system, the authorization code is generated. As described herein, the authorization code may include a second QR code (e.g., a temporary QR code), a number, an alphanumeric code, a word, a phrase, or a combination thereof. In one aspect, unless the authorization code is used before the future time, the authorization of the payment may be canceled after future time.

[0075] In some embodiments, the authorization code may be displayed on the display screen of the driver’s smartphone (e.g., the computing device 110 of FIG. 1 ). The driver 402-1 may show, send, and / or communicate the authorization code to the valet 402-2. In some embodiments, the valet 402-2 may user their smartphone (e.g., the computing device 112 of FIG. 1 ) to take a screen shot (e.g., take a photo) of the authorization code. As forementioned, each EVSE may include a code scanner, a number pad, a keyboard, an RFID reader, or a combination thereof that, in part, enables a user to access the EVSE and initiate a charging of the EV. For example, when using the second QR code, the valet 402-2 may display the second QR code to the code scanner of the EVSE to initiate the charging of the EV. As another example, when using a number as the authorization code, the valet 402-2 may enter the authorization code using the number pad of the EVSE. As yet another example, when using an alphanumeric code as the authorization code, the valet 402-2 may enter the authorization code using the keyboard of the EVSE.

[0076] In some embodiments, the authorization code may be automatically sent to an RFID of the valet 402-2 of FIG. 4 (or the computing device 112 of the second user 102-2 of FIG. 1 ). In such a case, the valet 402-2 of FIG. 4 may tap their RFID to the RFID reader of the EVSE to initiate the charging of the EV 404.

[0077] In some embodiments, after the valet 402-2 initiates the charging of the EV 404, the driver 402-1 may utilize their smartphone and the EVSE application software to view in real time, in near real time, and / or in time intervals the amount of power (e.g., in kW) being delivered to their EV (e.g., the EV 404), the cost of the amount of power (e.g., in $, €, ¥, £, etc.), a change in the SoC (e.g., 10%, 25%, 50%, 75%, 90%, full charge), the reservation time period, the charging time period, amessage from the EVSE application software, a message from the valet 402-2, and / or so forth.

[0078] Next, the description includes additional example embodiments of the systems, methods, and techniques that enable a first user (e.g., a driver) of an EV to pay, pre-pay, and / or authorize a payment to use an EVSE.Example Embodiments

[0079] Example 1. A system for authorizing charging an electric vehicle (EV), the system comprising: potentially at least one electric vehicle supply equipment (EVSE); one or more processors; and at least one memory having instructions stored thereon that, when executed by the one or more processors, cause the system to: enable, at least based on user input, user authorization of payment (e.g., using an account management system); determine an available EVSE of the at least one EVSE to initiate charging the EV within a future time; reserve the available EVSE of the at least one EVSE for a reservation time period; and generate an authorization code to be provided or otherwise presented at the reserved EVSE for initiating charging of the EV within the future time.

[0080] Example 2. The system of Example 1 , wherein the user is a first user, and the authorization code is transferrable to enable a second user to initiate charging the EV within the future time and at the reserved EVSE of the at least one EVSE.

[0081] Example 3. The system of Example 2, wherein the second user is a valet working at an establishment (e.g., a public establishment) having the reserved EVSE of the at least one EVSE.

[0082] Example 4. The system of Example 1 , wherein the authorization code is valid from at least a present time to the future time.

[0083] Example 4.1 The system of Example 1 , wherein the future time is an expiration period that is shorter in duration than a period to complete charging the EV.

[0084] Example 5. The system of Example 1 , wherein the authorization code is temporary (e.g., and expires at the end of the future time).

[0085] Example 6. The system of Example 1 , wherein the authorization code comprises a quick response (QR) code, a number, an alphanumeric code, a word, a phrase, or a combination thereof.

[0086] Example 7. The system of Example 1 further comprises a retail kiosk with a payment terminal, wherein the payment terminal of the retail kiosk enables the userto authorize the payment using a credit card, a debit card, a bank account, a digital wallet, a cryptocurrency, a paper currency, a coin currency, or a combination thereof.

[0087] Example 8. The system of Example 7, wherein the retail kiosk is located at an establishment (e.g., a public establishment).

[0088] Example 9. The system of Example 8, wherein the retail kiosk is configured to print the authorization code on a coupon, a receipt, or a combination thereof.

[0089] Example 10. A computer-implemented method for charging an electric vehicle (EV), the computer-implemented method comprising: obtaining authorization of payment for charging the EV using an electric vehicle supply equipment (EVSE); determining an available EVSE of one or more EVSEs to start charging the EV within a future time; generating an authorization code to be provided to the available EVSE for initiating a charging of the EV within the future time.

[0090] Example 11. The computer-implemented method of Example 10 further comprising: reserving the available EVSE of the one or more EVSEs for a reservation time period, and the reservation time period starting after the initiating of charging of the EV within the future time.

[0091] Example 12. The computer-implemented method of Example 10 enabling a user to scan a quick response (QR) code by utilizing a camera of a computing device associated with the user, and responsive to the scanning, performing the computer- implemented method of Example 10.

[0092] Example 12.1. The computer-implemented method of Example 10, further comprising receiving, from a computing device associated with a user, a result of a scan of a quick response (QR) code.

[0093] Example 13. The computer-implemented method of Example 12 further comprising: displaying the authorization code on a display screen of the computing device associated with the user.

[0094] Example 14. The computer-implemented method of Example 13, wherein the QR code comprising a first QR code, and the authorization code comprising a second QR code.

[0095] Example 15. The computer-implemented method of Example 10 further comprising: generating a location of the available EVSE.

[0096] Example 16. The computer-implemented method of Example 10, wherein the authorization code enables a radio-frequency identification (RFID) to initiate the charging of the EV at the available EVSE within the future time.

[0097] Example 17. The computer-implemented method of Example 10, wherein the EVSE comprises a code scanner, and the initiating of charging of the EV comprises a user displaying the authorization code to the code scanner the EVSE.

[0098] Example 18. The computer-implemented method of Example 10 further comprising: canceling the authorization of the payment after the future time.

[0099] Example 19. The computer-implemented method of Example 10, wherein the EVSE comprises a code scanner, a number pad, a keyboard, an RFID reader, or a combination thereof.

[0100] Example 19.1. The computer-implemented method of Example 10, wherein the future time is an expiration period that is shorter in duration than a time to complete charging the EV.

[0101] Example 20. A system computing device comprising: an interface to communicate with one or more EVSEs over a network; at least one processor; and at least one computer-readable medium having instructions that, responsive to execution by the at least one processor, cause the system computing device to perform the computer-implemented method of Example 10.

[0102] Example 21. The system computing device of Example 20, wherein the communication utilizes a communication protocol, and the communication protocol comprises: an Open Charge Point Protocol (OCPP); a Third Generation Partnership Project (3GPP) Long-Term Evolution (LTE) standard; an Institute of Electrical and Electronics (IEEE) 802.11 standard; an IEEE 802.16 standard; an IEEE 802.15.4 standard; a Bluetooth Classic® standard; a Bluetooth Low Energy® (BLE®) standard; or a combination thereof.

[0103] Furthermore, the described features, operations, or characteristics may be arranged and designed in a wide variety of different configurations and / or combined in any suitable manner in one or more embodiments. Thus, the detailed description of the embodiments of the systems and methods is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments of the disclosure. In addition, it will also be readily understood that the order of the steps or actions of the methods described in connection with the embodiments disclosed may be changed as would be apparent to those skilled in the art. Thus, any order in the drawings or Detailed Descriptions is for illustrative purposes only and is not meant to imply a required order, unless specified to require an order.

[0104] Embodiments may include various steps, which may be embodied in machine-executable instructions to be executed by a general-purpose or specialpurpose computer (or other electronic device). Alternatively, the steps may be performed by hardware components that include specific logic for performing the steps, or by a combination of hardware, software, and / or firmware.

[0105] Any of the application processor(s) or processor(s) described herein may include any type of processor, such as a central processing unit (CPU) or a multi-core processor. The processor(s) may be configured to execute instructions (e.g., code, pseudocode, algorithm(s), application software, software module(s), configurations, computer instruction(s), and / or so forth) that may be stored in a computer-readable medium(a).

[0106] Any of the computer-readable medium(a) (or memory) described herein may include any suitable data storage media, such as non-volatile memory (e.g., flash memory), volatile memory (e.g., random-access memory (RAM)), optical media, magnetic media (e.g., disc or tape), and so forth. Moreover, the computer-readable medium(a) does / do not include transitory propagating signals or carrier waves.

[0107] A software module, a memory component, a computer-readable medium, and / or so forth may include any type of computer instruction or computer-executable code that may be located within the software module, the memory component, the computer-readable medium, as is well known in the art.

[0108] It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention.

Claims

CLAIMS1. A system for authorizing charging an electric vehicle (EV), the system comprising: one or more processors; and at least one memory having instructions stored thereon that, when executed by the one or more processors, cause the system to: enable, at least based on user input, user authorization of payment for charging the EV; determine an available electric vehicle supply equipment (EVSE) from among a plurality of EVSE to initiate charging the EV within a future time; reserve the available EVSE of the at least one EVSE for at least the future time; and generate an authorization code to be provided at the reserved EVSE for initiating charging of the EV within the future time.

2. The system of claim 1 , wherein the user is a first user, and the authorization code is transferrable to enable a second user to initiate charging the EV within the future time and at the reserved EVSE of the at least one EVSE.

3. The system of claim 2, wherein the second user is a valet working at an establishment having the reserved EVSE of the at least one EVSE.

4. The system of claim 1 , wherein the authorization code is valid from at least a present time to the future time.

5. The system of claim 1 , wherein the future time is an expiration period that is shorter in duration than a period to complete charging the EV.

6. The system of claim 1 , wherein the authorization code is temporary and expires at the end of the future time.

7. The system of claim 1 , wherein the authorization code comprises a quick response (QR) code, a number, an alphanumeric code, a word, a phrase, or a combination thereof.

8. The system of claim 1 , further comprising a payment terminal that enables the user to authorize the payment.

9. The system of claim 1 , further comprising a printer to print the authorization code on a coupon, a receipt, or a combination thereof.

10. A computer-implemented method for charging an electric vehicle (EV), the computer-implemented method comprising: obtaining authorization of payment for charging the EV using an electric vehicle supply equipment (EVSE); determining an available EVSE of one or more EVSEs to start charging the EV within a future time; generating an authorization code to be provided to the available EVSE for initiating a charging of the EV within the future time.

11. The computer-implemented method of claim 10 further comprising: reserving the available EVSE of the one or more EVSEs for a reservation time period.

12. The computer-implemented method of claim 10, further comprising: receiving, from a computing device associated with a user, a result of a scan of a quick response (QR) code.

13. The computer-implemented method of claim 12, further comprising: displaying the authorization code on a display screen of the computing device associated with the user.

14. The computer-implemented method of claim 13, wherein the QR code comprises a first QR code, and the authorization code comprises a second QR code.

15. The computer-implemented method of claim 10, further comprising: generating a location of the available EVSE.

16. The computer-implemented method of claim 10, wherein the authorization code enables a radio-frequency identification (RFID) card to initiate the charging of the EV at the available EVSE within the future time.

17. The computer-implemented method of claim 10, wherein the EVSE comprises a code scanner, and the initiating of charging of the EV comprises a user displaying the authorization code to the code scanner of the EVSE.

18. The computer-implemented method of claim 10 further comprising: canceling the authorization of the payment after the future time.

19. The computer-implemented method of claim 10, wherein the future time is an expiration period that is shorter in duration than a time to complete charging the EV.

20. A system computing device comprising: an interface to communicate with one or more EVSEs over a network; at least one processor; and at least one computer-readable medium having instructions that, responsive to execution by the at least one processor, cause the system computing device to perform the computer-implemented method of claim 10.

Images