System and method for electric vehicle charging and billing using a wireless vehicle communication service

Abstract

A vehicle charging station for use in transmitting charging power to an electric vehicle for use in charging the vehicle is configured to communicatively couple to the electric vehicle via a network connection to a wireless network provider and electrically couple to the electric vehicle via a connector. Vehicle charging station is further configured to receive a unique identifier from the electric vehicle via the network connection, deliver a quantity of electrical charging power to the electric vehicle via the connector, and meter the quantity of electrical charging power delivered to the electric vehicle.

Claims

1. A vehicle charging system having a vehicle charging station for use in delivering electrical charging power to an electric vehicle that includes a unique identifier of the electric vehicle embedded in the electric vehicle, the vehicle charging system comprising: a connector of the vehicle charging station configured to electrically couple the vehicle charging station to the electric vehicle; a station meter of the vehicle charging station configured to track a quantity of electrical charging power delivered to the electric vehicle via the connector; and a processor of the vehicle charging station, wherein the processor upon execution of a module, is configured to: communicatively couple, over a network and via a network connection to a wireless network provider, the vehicle charging station to the electric vehicle; communicatively couple, over the network, the vehicle charging station to a server system; receive the unique identifier embedded in the electric vehicle from the electric vehicle via the network connection to the wireless network provider; and transmit the unique identifier to the server system; wherein, upon receipt of the unique identifier, the server system: determines an account associated with the unique identifier; and generates a charging approval or a charging denial; wherein the charging denial denies access to electrical charging power at the vehicle charging station; and wherein the charging approval provides access to electrical charging power at the vehicle charging station; and wherein the processor, upon execution of a module, is further configured to: receive an input from the server system comprising one of the charging approval and the charging denial; when the input is the charging denial, prevent a charging output for charging the electric vehicle and display a message indicating a reason for the prevention of the charging output; and when the input is the charging approval, deliver a quantity of electrical charging power to the electric vehicle via the connector and meter the quantity of electrical charging power delivered to the electric vehicle via the station meter.

2. A vehicle charging system in accordance with claim 1, wherein the server system, upon receipt of the unique identifier, generates the charging approval or the charging denial based on the account associated with the unique identifier.

3. A vehicle charging system in accordance with claim 2, wherein the server system, upon receipt of the unique identifier, generates the charging approval or the charging denial based on the location of the electric vehicle and/or the vehicle charging station, and/or based on a rate per unit of the electrical charging power at a time of the receipt of the unique identifier.

4. A vehicle charging system in accordance with claim 1, wherein the server system delays the charging approval based on one or more of a system-wide electrical power demand at a time of the receipt of the unique identifier and a rate per unit of the electrical charging power at a time of the receipt of the unique identifier.

5. A vehicle charging system in accordance with claim 1, wherein the processor, upon execution of the module, is further configured to transmit, to the server system, the quantity of electrical charging power delivered to the electric vehicle to determine a transaction amount.

6. A vehicle charging system in accordance with claim 1, wherein the processor, upon execution of the module, is further configured to compare the metered quantity of electrical charging power delivered to the electric vehicle with a metered value determined by the electric vehicle.

7. A vehicle charging system in accordance with claim 1, wherein the processor, upon execution of the module, is configured to display at least one of the quantity of electrical charging power delivered to the electric vehicle, a monetary value of the quantity of electrical charging power delivered to the electric vehicle, and a quantity of electrical charging power remaining to be delivered to the electric vehicle.

8. A vehicle charging system in accordance with claim 1, wherein in generating the charging approval, the server system provides a schedule comprising a rate per unit of electrical charging power to the processor.

9. A method for authorizing and monitoring delivery of electrical charging power to an electric vehicle from a vehicle charging station, the method comprising: providing a server system that is communicatively coupled, over a network and via a network connection to a wireless network provider, to the electric vehicle and to the vehicle charging station; receiving, by the server system, as part of a charging request from the electric vehicle over the network and via the network connection to the wireless network provider, a unique identifier embedded within the electric vehicle; determining, by the server system, an account associated with the unique identifier; generating, by the server system, a charging approval or a charging denial responsive to the charging request; when the server system generates the charging denial, providing, by the server system, the charging denial to the vehicle charging station over the network and via the network connection to the wireless network provider such that the charging denial prevents the vehicle charging station from providing a charging output for charging the electric vehicle; and when the server system generates the charging approval, providing, by the server system, the charging approval to the vehicle charging station over the network and via the network connection to the wireless network provider such that the charging approval enables the vehicle charging station to provide a quantity of electrical charging power to the electric vehicle.

10. A method in accordance with claim 9, wherein in generating the charging approval or the charging denial, the method comprises generating the charging approval or the charging denial based on the account associated with the unique identifier.

11. A method in accordance with claim 9, wherein in generating the charging approval or the charging denial, the method comprises generating the charging approval or the charging denial based on the location of the electric vehicle and/or the vehicle charging station, and/or based on a rate per unit of the electrical charging power at a time of the receipt of the unique identifier.

12. A method in accordance with claim 9, wherein when generating the charging approval, the method comprises delaying the charging approval based on one or more of a system-wide electrical power demand at a time of the receipt of the unique identifier and a rate per unit of the electrical charging power at a time of the receipt of the unique identifier.

13. A method in accordance with claim 9, wherein in generating the charging approval or the charging denial, the method comprises: determining a present monetary balance of the account; and generating the charging approval or the charging denial based on the present monetary balance, with the charging denial being generated when the present monetary balance is less than a predetermined amount and the charging approval being generated when the present monetary balance is greater than the predetermined amount.

14. A method in accordance with claim 9, further comprising receiving, by the server system, the quantity of electrical charging power delivered to the electric vehicle; and determining, by the server system, a transaction amount of the charging of the electric vehicle.

15. A method in accordance with claim 9, wherein in generating the charging approval, the method comprises providing, by the server system, a schedule comprising a rate per unit of electrical charging power to the vehicle charging station over the network and via the network connection to the wireless network provider.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a simplified block diagram of an exemplary electricity delivery system for use with an electric vehicle.

(2) FIG. 2 is an expanded block diagram of an exemplary embodiment of a system architecture of the system shown in FIG. 1.

(3) FIG. 3 is a flowchart illustrating an exemplary method for use in delivering electrical charging power to an electric vehicle using the system shown in FIGS. 1 and 2.

DETAILED DESCRIPTION OF THE INVENTION

(4) As used herein, the term “electric vehicle” includes any vehicle that includes one or more electric motors that are used for propulsion, such as an all-electric vehicle that uses only electricity, and/or a plug-in hybrid-electric vehicle that uses a gas powered engine in combination with batteries charged by an external power source or an engine and generator, to propel the vehicle. In addition, the term “electric vehicle” includes any suitable vehicle known to those skilled in the art and guided by the teachings herein provided that is capable of performing the functions described herein. Moreover, the term “wireless network provider” refers generally to an entity providing a wireless communications network that includes two or more wireless communication devices. Those having ordinary skill in the art and guided by the teachings herein provided would understand that a wireless network provider enables communications of any type or combination of information, including, without limitation, audio, video, and/or data.

(5) A controller, computing device, or computer, such as described herein, includes at least one or more processors or processing units and a system memory. The controller typically also includes at least some form of computer readable media. By way of example and not limitation, computer readable media may include computer storage media and communication media. Computer storage media may also include volatile and nonvolatile, removable and non-removable media implemented in any method or technology that enables storage of information, such as computer readable instructions, data structures, program modules, or other data. Communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media. Those skilled in the art should be familiar with the modulated data signal, which has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Combinations of any of the above are also included within the scope of computer readable media.

(6) Although described in connection with an exemplary energy delivery system environment, embodiments of the invention are operational with numerous other general purpose or special purpose computing system environments or configurations. The energy delivery system environment is not intended to suggest any limitation as to the scope of use or functionality of any aspect of the invention. Moreover, the energy delivery system environment should not be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment. Examples of well known systems, environments, and/or configurations that may be suitable for use with aspects of the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.

(7) Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more controllers, computers, or other devices. Aspects of the invention may be implemented with any number and organization of components or modules. For example, aspects of the invention are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Alternative embodiments of the invention may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.

(8) The order of execution or performance of the operations in the embodiments of the invention illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the invention may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the invention.

(9) In some embodiments, a processor includes any programmable system including systems and microcontrollers, reduced instruction set circuits (RISC), application specific integrated circuits (ASIC), programmable logic circuits (PLC), and any other circuit or processor capable of executing the functions described herein. The above examples are exemplary only, and thus are not intended to limit in any way the definition and/or meaning of the term processor.

(10) In some embodiments, a database includes any collection of data including hierarchical databases, relational databases, flat file databases, object-relational databases, object oriented databases, and any other structured collection of records or data that is stored in a computer system. The above examples are exemplary only, and thus are not intended to limit in any way the definition and/or meaning of the term database. Examples of databases include, but are not limited to only including, Oracle® Database, MySQL, IBM® DB2, Microsoft® SQL Server, Sybase®, and PostgreSQL. However, any database may be used that enables the systems and methods described herein. (Oracle is a registered trademark of Oracle Corporation, Redwood Shores, Calif.; IBM is a registered trademark of International Business Machines Corporation, Armonk, N.Y.; Microsoft is a registered trademark of Microsoft Corporation, Redmond, Wash.; and Sybase is a registered trademark of Sybase, Dublin, Calif.)

(11) Technical effects of the methods, systems, and vehicle charging station herein include at least one of communicatively coupling a vehicle charging station to the electric vehicle via a network connection to a wireless network provider, electrically coupling the vehicle charging station to the electric vehicle via a connector, receiving a unique identifier of the electric vehicle via the network connection, determining an account associated with the identifier, determining whether to approve or deny service to the electric vehicle, delivering a quantity of electrical charging power to the electric vehicle via the connector, metering the quantity of electrical charging power delivered, determining a transaction amount based on the quantity of delivered electrical charging power, and deducting the transaction amount from the account.

(12) FIG. 1 is a simplified block diagram of an exemplary electricity delivery system 100 for use with a wireless network provider 101 and an electric vehicle 102. In the exemplary embodiment, system 100 includes a server system 104 and a vehicle charging station 106 that is coupled to server system 104. As shown in FIG. 1, server system 104 may be coupled to a plurality of vehicle charging stations 106. In one embodiment, vehicle charging station 106 is coupled to a network 108 that enables vehicle charging station 106 to access server system 104 over network 108. In one embodiment, network 108 includes a private network such as a wide area network. In another embodiment, network 108 includes a public network, such as the Internet. In the exemplary embodiment, vehicle charging stations 106 are connected to network 108 through many interfaces such as a local area network (LAN), a wide area network (WAN), dial-in-connections, cable modems, wireless modems, and/or special high-speed Integrated Services Digital Network (ISDN) lines. A database server 110 includes a database 112 that contains information on a variety of matters, such as account information related to electric vehicle power distribution. In the exemplary embodiment, centralized database 112 is stored in server system 104 and is accessed via at least one vehicle charging station 106. In an alternative embodiment, database 112 is stored remotely from server system 104 and may be non-centralized. Moreover, in the exemplary embodiment, each vehicle charging station 106 is capable of electrically coupling to one or more electric vehicles 102 via a connector 114 and providing electrical charging power to one or more electric vehicles 102 via connector 114. Each electric vehicle 102 stores the electrical charging power and uses the stored power for propulsion, rather than, or in addition to, more conventional energy sources such as gasoline.

(13) As described in more detail below, in the exemplary embodiment, each electric vehicle 102 includes a unique identifier that is used by vehicle charging station 106 and/or server 104 to identify the electric vehicle 102 and/or an account associated with electric vehicle 102. For example, database 112 may include transactional and/or accounting data related to prepayment information associated with a quantity of electrical charging power that has been paid for in advance for later distribution to electric vehicle 102. Moreover, database 112 may include historical electrical charging power distribution data, such as transaction dates, and/or a quantity of electrical charging power delivered to electric vehicle 102 for each transaction. Further, database 112 may include historical payment information, such as prepayment dates and/or prepayment amounts.

(14) Moreover, those having ordinary skill in the art and guided by the teachings herein provided should understand that wireless network provider 101 can use any publicly accessible or any proprietary system, and can use any appropriate access and/or link protocol to communicate with electric vehicle 102, server system 104, and vehicle charging station 106, including, without limitation, analog, digital, packet-based, time division multiple access (TDMA), direct sequence code division multiple access (CDMA), frequency hopping CDMA, wideband code division multiple access (WCDMA), frequency division multiple access (FDMA), spread spectrum or any other known or future developed access or link protocol or methodology. The wireless network provider 101 can further use any of a variety of networking protocols, such as, User Datagram Protocol (UDP), Transmission Control Protocol/Internet Protocol (TCP/IP), AppleTalk™, Inter-Packet Exchange/Sequential Packet Exchange (IPX/SPX), Network Basic Input Output System (Net BIOS), or any proprietary or non-proprietary protocol, to communicate digital voice, data and/or video with electric vehicle 102. Further, using network 108, wireless network provider 101 can communicate with vehicle charging station 106 and server 104 using any appropriate access protocol, link protocol, and/or network protocol as described above and as is known by those having ordinary skill in the art and guided by the teachings herein.

(15) The embodiments illustrated and described herein as well as embodiments not specifically described herein, but within the scope of aspects of the invention, constitute exemplary means for identifying an electric vehicle via a network connection to a wireless network provider and providing electrical charging power delivery and metering for the electric vehicle. For example, server system 104 or vehicle charging station 106, or any other similar computer device that is programmed with computer-executable instructions, as illustrated in FIG. 1, provides exemplary means for identifying an electric vehicle using a wirelessly communicated identifier.

(16) FIG. 2 is an expanded block diagram of an exemplary system architecture 200 of system 100 (shown in FIG. 1). Components in system architecture 200 that are identical to components of system 100 are identified in FIG. 2 using the same reference numerals used in FIG. 1. In the exemplary embodiment, system 200 includes server system 104 and vehicle charging stations 106. Server system 104 also includes database server 110, an application server 202, a web server 204, a directory server 206, and a mail server 208. A disk storage unit 210 is coupled to database server 110 and to directory server 206. Disk storage unit 210 may include, but is not limited to only including, a Network Attached Storage (NAS) device and/or a Storage Area Network (SAN) device. In one embodiment, database 112 is stored in database server 110. In the exemplary embodiment, database 112 is coupled to database server 110. Servers 110, 202, 204, 206, and 208 are coupled in a local area network (LAN) 212. Moreover, a system administrator workstation 214, a user workstation 216, and a supervisor workstation 218 may be coupled to LAN 212 to enable communication with server system 104. Alternatively, workstations 214, 216, and 218 may be coupled to LAN 212 using a link to an Internet 219, or may be coupled through a private network. In one embodiment, an owner or user of electric vehicle 102 may access server system 104 via web server 204 to access, for example, the user's account and/or a payment service that enables the user to pay for electrical charging power that has been delivered to electric vehicle 102 via connector 114 or will be delivered to electric vehicle 102. Moreover, in one embodiment, mail server 208 may be configured to send a message, such as an email message, to the user when the user's account balance falls below a predetermined balance. Alternatively, a user may setup a periodic reminder, wherein mail server 208 transmits a message to the user at a configurable periodic rate or when the account balance reaches a predetermined balance as a reminder to prepay for electrical charging power to be delivered later to electric vehicle 102. As used herein, the term “balance” includes any amount of money available in an account for use in paying for electrical charging power, such as an amount of cash on deposit and an amount of credit available on an account, including a credit card and line of credit.

(17) Each vehicle charging station 106 includes a network module 220 that communicates with server system 104. For example, server system 104 is communicatively coupled to vehicle charging stations 106 to enable server system 104 to be accessed via the Internet 219. The systems and processes, though, are not limited to being practiced using a WAN type communication method or Internet 219.

(18) To facilitate communication between electric vehicle 102 and server system 104 via wireless network provider 101, electric vehicle 102 includes a unique vehicle identifier 222 that is embedded within electric vehicle 102. In the exemplary embodiment, identifier 222 is a number generated by server system 104 upon creation of the user's account. In other embodiments, unique vehicle identifier 222 includes a manufacturer provided vehicle identification number (VIN) of electric vehicle 102. In other embodiments, identifier 222 can be one or more of an electrical charging power supplier account number, a pre-paid stored value account number, a credit account number, or any suitable identifying number of a type known to those skilled in the art and guided by the teachings herein provided that is capable of being used as described herein. In one embodiment, unique vehicle identifier 222 is accessible only upon authorization by the user of electric vehicle 102, as to restrict unauthorized access to unique vehicle identifier 222. In another embodiment, a new unique vehicle identifier 222 is generated after completion of one or more of transactions for the delivery of electrical charging power, and identifier 222 is stored in electric vehicle and server system 104 for a subsequent transaction. Electric vehicle 102 also includes a vehicle communications module 224 for use in communicatively coupling electric vehicle to server system 104 and to vehicle charging station 106 via a network connection to wireless network provider 101.

(19) In the exemplary embodiment, identifier 222 is linked in database 112 to an account associated with electric vehicle 102. An account balance is maintained within database including prepayments made to the account by the account owner. Alternatively, identifier 222 may be linked to an account associated with a person, such that an account balance may be allocated among one or more electric vehicles 102. Further, in the exemplary embodiment, each vehicle charging station 106 includes a station meter 226 that tracks a quantity of electrical charging power delivered to electric vehicle 102 via connector 114. Moreover, in the exemplary embodiment, electric vehicle 102 includes a vehicle meter 228 that tracks a quantity of electrical charging power received by electric vehicle 102 via connector 114.

(20) During use, when a customer desires to charge electric vehicle 102 via vehicle charging station 106, electric vehicle 102 is communicatively coupled to vehicle charging station 106 via wireless network provider 101 and to server system 104, and electric vehicle 102 is electrically coupled to vehicle charging station 106 via connector 114. More specifically, identifier 222 is transmitted to server system 104 via wireless network provider 101, and server system 104 determines an account associated with identifier 222. In the exemplary embodiment, either wireless network provider 101 and/or server system 104 are operated by an entity other than an electrical charging power supplier, such as a manufacturer of electric vehicle 102, for example, General Motor's OnStar system, Toyota Motor Corporation's G-Book system, Hughes Telematics, as well as other telemetry and telematic-type system providers. In another embodiment, network provider 101 and/or server system 104 are owned and/or operated by the electrical charging power supplier. In the exemplary embodiment, after server system 104 has determined the account associated with identifier 222, server system 104 determines an account balance. In such an embodiment, if the account balance meets a predetermined balance, server system 104 instructs vehicle charging station 106 to enable service to electric vehicle 102. Alternatively, if the account balance does not meet the predetermined balance, server system 104 may instruct vehicle charging station 106 to deny service to electric vehicle 102 and display a message to the user/customer stating the reason for the denial. Further, in such an embodiment, server system 104 may issue a temporary credit to the account balance.

(21) In another embodiment, electric vehicle 102 also transmits a location of electric vehicle 102 and/or vehicle charging station 106. In such an embodiment, electric vehicle 102 may obtain the location from a Global Positioning Satellite receiver (not shown) in electric vehicle 102, from wireless network provider 101, from vehicle charging station 106, or from any means known to those skilled in the art that is capable of performing the functions described herein. Moreover, in such an embodiment, server system 104 may use the location information to determine a different rate per unit of electrical charging power for service to electric vehicle 102. Further, in such an embodiment, server system 104 may also use the location information to determine an availability of electrical charging power to vehicle charging station 106, and based on such a determination, vehicle charging station 106 may deny service to electric car or delay service to electric car for a period of time, as to avoid, for example, peak charging times, a per unit cost higher than desired by the user or the owner of electric car 102, or an electricity shortage. In another embodiment, server system 104 also communicates with electric vehicle 102 to request the delay of service to avoid, for example, peak charging times, a per unit cost higher than desired by the user or the owner of electric car 102, or an electricity shortage.

(22) In one embodiment, vehicle charging station 106 meters electrical charging power delivery to electric vehicle 102 via connector 114 at different rate per unit of electrical charging power, such as a higher rate, when a temporary credit is issued. In another embodiment, server system 104 may instruct vehicle charging station 106 to deny service to electric vehicle 102 when the account associated with identifier 222 has been put into a hold state. In such an embodiment, a hold state may be placed on the account based on, for example, a delinquent payment by the customer and/or a report of electric vehicle 102 being stolen.

(23) In the exemplary embodiment, when service to electric vehicle 102 is enabled, vehicle charging station 106 delivers a quantity of electrical charging power to electric vehicle 102 via connector 114. During delivery, vehicle charging station 106, via station meter 226, and electric vehicle 102, via vehicle meter 228, each meter the quantity of electrical charging power delivered and/or a transaction amount based on the quantity of electrical charging power delivered. A final transaction amount is determined at the conclusion of the delivery of the electrical charging power, the final transaction amount is transmitted to server system 104, and server system 104 deducts the final transaction amount from the account balance. If the final transaction amount is greater than the account balance, server system 104 may issue a temporary credit using a different rate, such as a higher rate, as described above. In addition, in one embodiment, upon the conclusion of the delivery of the electrical charging power, station meter 226 and vehicle meter 228 compare the quantity of electrical charging power delivered and/or the final transaction amount. If the comparison results in a match, then vehicle meter 228 generates a receipt. In one embodiment, the receipt is stored in vehicle meter 228. In another embodiment, the receipt is also transmitted to vehicle charging station 106 for storage in server system 104. This comparison facilitates enabling accuracy of the metered quantity of electrical charging power delivered and/or ensuring that the correct transaction amount is billed to the account and/or deducted from the account balance. Moreover, the comparison facilitates ensuring that, if there are multiple electric vehicles 102 receiving electrical charging power from vehicle charging station 106, the correct account is billed.

(24) FIG. 3 is a flowchart 300 illustrating an exemplary method for use in delivering electrical charging power to electric vehicle 102 (shown in FIGS. 1 and 2) using the system shown in FIGS. 1 and 2. In the exemplary embodiment, vehicle charging station 106 (shown in FIGS. 1 and 2) is communicatively coupled 301 to electric vehicle 102 (shown in FIGS. 1 and 2) via the network connection to wireless network provider 101 (shown in FIGS. 1 and 2), and vehicle charging station 106 is also electrically coupled 302 to electric vehicle 102 via connector 114 (shown in FIGS. 1 and 2). Further, in the exemplary embodiment, server system 104 (shown in FIGS. 1 and 2) receives 303 unique vehicle identifier 222 (shown in FIG. 2) from electric vehicle 102 via the network connection. In the exemplary embodiment, electric vehicle 102 and, more specifically, identifier 222, is associated with a customer account. Server system 104 determines 304 an account associated with identifier 222. More specifically, server system 104 determines 304 the user account associated with identifier 222 within database 108 (shown in FIGS. 1 and 2). In the exemplary embodiment, server system 104 then determines 305 a current balance of the customer account.

(25) In one embodiment, server system 104 determines 306 whether to approve or to deny service to electric vehicle 102 and transmits the determination to vehicle charging station 106. In such an embodiment, if the current balance is less than a predetermined amount, the customer is denied service at vehicle charging station 106. Further, in such an embodiment, the customer may be prompted to insert a credit card or cash into a payment accepter device (not shown) coupled to vehicle charging station 106. In one embodiment, service may be denied by server system 104 if a stolen car report associated with electric vehicle 102 exists. In the exemplary embodiment, the current account balance may be increased by the account holder remotely using, for example, user workstation 216 (shown in FIG. 2). For example, in one embodiment, the customer may login to server system 104 via user workstation 216 in order to access a payment program that enables the customer to designate a payment amount to be applied to the account balance. In such an embodiment, the customer also designates a payment source including, but not limited to, a credit card, a debit card, and/or a banking account. The payment amount, in such an embodiment, is then credited to the account balance.

(26) In the exemplary embodiment, a quantity of electrical charging power is delivered 308 to electric vehicle 102 via vehicle charging station 106 through connector 314, and the quantity of electrical charging current delivered is metered 310. A transaction amount is determined 312 based on an actual quantity of electrical charging power delivered to electric vehicle 102 at vehicle charging station 106. More specifically, station meter 226 (shown in FIG. 2) meters the quantity of electrical charging power delivered. In one embodiment, vehicle charging station 106 determines 312 the transaction amount based on the quantity of electrical charging power delivered and transmits the transaction amount to server system 104. In another embodiment, vehicle charging station 106 transmits, to server system 104, the quantity of electrical charging power delivered to electric vehicle 102, and server system 104 determines 312 the transaction amount based on the quantity of electrical charging power delivered 308. In the exemplary embodiment, the transaction amount is then compared 313 to the current balance in the customer account. If the transaction amount is less than the current balance, the transaction amount is deducted 314 from the current balance. The new balance is then stored in database 112. In one embodiment, the new balance is transmitted by server system 104 to vehicle charging station 106 and is displayed to the user/customer.

(27) In an alternative embodiment, the new balance is also transmitted to electric vehicle 102 via the network connection to wireless network provider 101 and is displayed to the customer via vehicle meter 228 (shown in FIG. 2). If the current balance is less than the transaction amount, the customer account may be credited with the difference between the transaction amount and the current balance, and the customer may be billed for the difference at a later time. In such an embodiment, the billing rate may be changed for any electrical charging power distributed on credit. Alternatively, the customer may be prompted to submit payment to vehicle charging station by, for example, the customer being prompted to insert a credit card into the payment acceptance device (not shown) coupled to vehicle charging station 106. In the exemplary embodiment, a confirmation of the receipt of the delivered electrical charging power is generated 308 by vehicle meter 228. The receipt may be used by the customer to verify a quantity of electrical charging power delivered and/or a cost per unit of electrical charging power. The receipt may be generated by electric vehicle 102 and stored in electric vehicle 102 and database 112. Alternatively, the receipt may be generated by server system 104, stored in database 112, and transmitted to electric vehicle 102 via a network connection to wireless network provider 101. In addition, in one embodiment, an adjusted current balance may be displayed to the customer via vehicle charging station 106 to reflect a deduction of the transaction amount from the account.

(28) Described in detail herein are exemplary embodiments of methods, systems, and computers that facilitate delivering electrical charging power to vehicles, such as electric vehicles. More specifically, the embodiments described herein facilitate identifying an electric vehicle at a vehicle charging station using a unique identifier embedded within the electric vehicle. Identifying an electric vehicle via a network connection to a wireless network provider facilitates automatic deduction of a transaction amount from an account. Such an automatic deduction facilitates time savings for a customer and greater ease in collecting revenue for an electric distribution utility.

(29) The methods and systems described herein are not limited to the specific embodiments described herein. For example, components of each system and/or steps of each method may be used and/or practiced independently and separately from other components and/or steps described herein. In addition, each component and/or step may also be used and/or practiced with other assembly packages and methods.

(30) While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.