NETWORK-CONTROLLED CHARGING SYSTEM FOR ELECTRIC VEHICLES

Abstract

A server of a network-controlled charging system for electric vehicles receives a request for charge transfer for an electric vehicle at a network-controlled charge transfer device, determines whether to enable charge transfer, and responsive to determining to enable charge transfer, transmits a communication to the network-controlled charge transfer device that indicates to the network-controlled charge transfer device to enable charge transfer.

Claims

1. A method in a server of a network-controlled charging system for electric vehicles, the method comprising: storing availability information of a plurality of network-controlled charge transfer devices; providing availability information of the plurality of network-controlled charge transfer devices to an electric vehicle operator, the availability information indicating for each of the plurality of network-controlled charge transfer devices whether that network-controlled charge transfer device is unavailable due to that network-controlled charge transfer device currently being used for charging; receiving a request for charge transfer for an electric vehicle at first one of the plurality of network-controlled charge transfer devices that is indicated as being available through the stored availability information, wherein the request for charge transfer originates from an electric vehicle operator; determining whether to enable charge transfer for the electric vehicle at the first one of the plurality of network-controlled charge transfer devices; responsive to determining to enable charge transfer, transmitting a communication to the first one of the plurality of network-controlled charge transfer devices that indicates to the first one of the plurality of network-controlled charge transfer devices to enable charge transfer; and generating a report detailing power consumed by charging electric vehicles at the plurality of network-controlled charge transfer devices.

2. The method of claim 1, wherein determining whether to enable charge transfer includes validating a payment source for the charge transfer.

3. The method of claim 1, further comprising: receiving an indication of a load reduction requirement; and transmitting a communication to the plurality of network-controlled charge transfer devices that indicates to the plurality of network-controlled charge transfer devices to limit charge transfer.

4. The method of claim 1, further comprising: receiving a message that indicates a period of high electricity demand; determining that the electric vehicle operator does not want to charge the electric vehicle during periods of high electricity demand; and transmitting a communication to the first one of the plurality of network-controlled charge transfer devices that indicates to the first one of the plurality of network-controlled charge transfer devices to stop charge transfer.

5. The method of claim 1, further comprising: receiving a message that indicates a period of high electricity demand; determining that the electric vehicle operator is willing to sell energy stored in the electric vehicle to a local power grid coupled with the first one of the plurality of network-controlled charge transfer devices; and communicating to the first one of the plurality of network-controlled charge transfer devices to enable charge transfer from the electric vehicle to the local power grid.

6. The method of claim 1, wherein determining whether to enable charge transfer includes performing the following: accessing a profile associated with the electric vehicle operator, wherein the profile indicates whether that electric vehicle operator wants to charge their electric vehicle only during periods of lower power rates; and responsive to determining a period of lower power rates exist, determining to enable charge transfer.

7. The method of claim 1, further comprising: transmitting information to the first one of the plurality of network-controlled charge transfer devices that indicates whether the electric vehicle operator wants to charge their electric vehicle only during periods of lower power rates to enable the first one of the plurality of network-controlled charge transfer devices to manage charge transfer based on that information.

8. The method of claim 1, wherein determining whether to enable charge transfer includes performing the following: accessing a profile associated with the electric vehicle operator; and validating a payment source for the electric vehicle operator based on the profile.

9. The method of claim 8, further comprising: responsive to completion of charge transfer, requesting payment from the payment source.

10. A server in a network-controlled charging system for electric vehicles, comprising: a computer configured to perform the following: store availability information of a plurality of network-controlled charge transfer devices; provide availability information of the plurality of network-controlled charge transfer devices to an electric vehicle operator, the availability information indicating for each of the plurality of network-controlled charge transfer devices whether that network-controlled charge transfer device is unavailable due to that network-controlled charge transfer device currently being used for charging; receive a request for charge transfer for an electric vehicle at first one of the plurality of network-controlled charge transfer devices that is indicated as being available through the stored availability information, wherein the request for charge transfer originates from an electric vehicle operator, determine whether to enable charge transfer for the electric vehicle at the first one of the plurality of network-controlled charge transfer devices, responsive to a determination to enable charge transfer, transmit a communication to the network-controlled charge transfer device that indicates to the first one of the plurality of network-controlled charge transfer devices that indicates to the first one of the plurality of network-controlled charge transfer devices to enable charge transfer, and generate a report detailing power consumed by charging electric vehicles at the plurality of network-controlled charge transfer devices.

11. The server of claim 10, wherein the computer is configured to determine whether to enable charge transfer through a validation of a payment source for the charge transfer.

12. The server of claim 10, wherein the computer is further configured to perform the following: receive an indication of a load reduction requirement; and transmit a communication to the plurality of network-controlled charge transfer devices that indicates to the plurality of network-controlled charge transfer devices to limit charge transfer.

13. The server of claim 10, wherein the computer is further configured to perform the following: receive a message that indicates a period of high electricity demand; determine that the electric vehicle operator does not want to charge the electric vehicle during periods of high electricity demand; and transmit a communication to the first one of the plurality of network-controlled charge transfer devices that indicates to the first one of the plurality of network-controlled charge transfer devices to stop charge transfer.

14. The server of claim 10, wherein the computer is further configured to perform the following: receive a message that indicates a period of high electricity demand; determine that the electric vehicle operator is willing to sell energy stored in the electric vehicle to a local power grid coupled with first one of the plurality of network-controlled charge transfer devices; and communicate to the first one of the plurality of network-controlled charge transfer devices to enable charge transfer from the electric vehicle to the local power grid.

15. The server of claim 10, wherein the computer is configured to determine whether to enable charge transfer includes the computer to perform the following: access a profile associated with the electric vehicle operator, wherein the profile indicates whether that electric vehicle operator wants to charge their electric vehicle only during periods of lower power rates; and responsive to a determination that a period of lower power rates exists, determine to enable charge transfer.

16. The server of claim 10, wherein the computer is further configured to transmit information to the first one of the plurality of network-controlled charge transfer devices that indicates whether the electric vehicle operator wants to charge their electric vehicle only during periods of lower power rates to enable the first one of the plurality of network-controlled charge transfer devices to manage charge transfer based on that information.

17. The server of claim 10, wherein the computer is configured to determine whether to enable charge transfer includes the computer to perform the following: access a profile associated with the electric vehicle operator; and validate a payment source for the electric vehicle operator based on the profile.

18. The server of clam 17, wherein the computer is further configured to perform the following: responsive to completion of charge transfer, request payment from the payment source.

Description

BRIEF DESCRIPTION OF THE FIGURES

[0026] FIG. 1 is a schematic diagram of a network-connected charging outlet system according to a first embodiment of the invention.

[0027] FIG. 2 is a schematic diagram of a network-connected charging outlet system according to a second embodiment of the invention.

[0028] FIG. 3 is a schematic circuit diagram of a network-connected charging outlet of the invention.

[0029] FIG. 4 is a schematic circuit diagram of a parking meter display unit of the invention.

[0030] FIG. 5 is a schematic diagram of a server of the invention.

[0031] FIG. 6 is a schematic diagram of a remote payment system of the invention.

DETAILED DESCRIPTION

[0032] The present invention will now be described in detail with reference to the drawings, which are provided as illustrative examples of the invention so as to enable those skilled in the art to practice the invention. Notably, the figures and examples below are not meant to limit the scope of the present invention to a single embodiment, but other embodiments are possible by way of interchange of some or all of the described or illustrated elements.

[0033] A first embodiment of the network-controlled charge transfer system 100 for charging electric vehicles is shown in FIG. 1. The system 100 comprises a network-controlled charge transfer device 110, a local power grid 120, a data control unit 130, and a server 140. The system 100 interfaces with an electric vehicle 150, with an electrical connector 152, and an electric vehicle operator 160, via a mobile communication device 162. The network-controlled charge transfer device 110, referred to herein as a Smartlet™, is connected to the local power grid 120 by an electric power line 170, and to the electric vehicle 150 by the electrical connector 152. The flow of electrical power may be in either direction for both of these electrical connections. In other words, the electric vehicle 150 can be recharged from the local power grid 120, or the local power grid 120 can receive power from the electric vehicle 150. The Smartlet™ 110 has a communication link to the data control unit 130 over a local area network (LAN) 180. The LAN 180 may be either a wireless local area network (WLAN) or a power line communication (PLC) network. The data control unit 130 has a communication link to the server 140 over a wide area network (WAN) 185. The electric vehicle operator 160 uses the mobile communication device 162 to establish a communication link to the Smartlet™ 110 over a wireless network 190. This wireless network may be a WLAN or a wireless personal area network (WPAN). The communication link between the electric vehicle operator 160 and the Smartlet™ 110 allows information to be shared which enables recharging of the electric vehicle 150.

[0034] The Smartlet™ 110 comprises an electrical receptacle 112 and indicator lights 114. The electrical receptor 112 and the electrical connector 152 are configured to make an electrical connection allowing safe flow of electrical power between the Smartlet™ 110 and the electrical vehicle 150. Examples of suitable receptacles are those conforming to the NEMA (National Electrical Manufacturers Association) standards 5-15, 5-20 and 14-50. Although, other receptacles will be used for systems outside the United States which operate at voltages other than 110V (for example 220V) and which are required to meet different standards. In preferred embodiments the electrical receptacle 112 has a cover. The cover is lockable and is released by the Smartlet™ 110 upon receipt of a request for charging of an electrical vehicle 150 by the electric vehicle operator 160. This request may be made by the mobile communication device 162, as described above.

[0035] The indicator lights 114 are used to show the operational status of the Smartlet™ 110—for example, the status may be: charging in progress, charging complete, vehicle-to-grid (V2G) in progress and error warning. The indicator lights 114 may be LEDs (light emitting diodes), may be capable of showing a number of different colors and may be capable of continuous or flashing modes of operation. Alternatively, the indicator lights 114 may be replaced by an alphanumeric display.

[0036] The local power grid 120 is the electrical supply grid owned and operated by local utility companies. Although, the local power grid 120 does extend to parts of the electrical supply network that are not owned by the utility company, such as electrical cables on private premises.

[0037] The data control unit 130 acts as a bridge between the LAN and the WAN, and enables communication between the Smartlet™ 110 and the server 140. The server 140 is generally remote from the Smartlet™ 110.

[0038] The system 100 is shown in FIG. 1 with only one Smartlet™ 110; however, the system will be comprised of many Smartlet™ 110, all linked to the server 140 through one or more data control units 130. There will be one data control unit 130 for each group of geographically proximate (within the range of the same local area network) Smartlets™ 110.

[0039] The electric vehicle 150 is any battery operated electric vehicle, including EVs and plug in hybrids. Electric vehicles 150 that have the necessary V2G electronics are able to provide power to the local power grid 120.

[0040] The mobile communication device 162, used by the electric vehicle operator 160, can be any type of WLAN or WPAN compatible device. Examples of compatible devices are: one way and two-way RFID devices, an example of the latter being a FasTrac™ card; Wi-Fi® devices, such as a personal computer; BlueTooth® devices, such as a mobile phone; and ZigBee® devices. In some embodiments of the invention the vehicle user 160 can monitor charging using the mobile communication device 162. This can be implemented by allowing access to the vehicle user 160 of the power consumed by the electric vehicle 150, which is monitored by the Smartlet™ 110 and stored on the server 140. Access can either be directly to the Smartlet™ 110 over a LAN or to the server 140 over the Internet.

[0041] A second embodiment of the network controlled charge transfer system 200 for charging electric vehicles 150 is shown in FIG. 2. The system 200 comprises a network-controlled charge transfer device (Smartlet™ 110, a local power grid 120, a payment station 135, and a server 140. The system 200 interfaces with an electric vehicle 150, with an electrical connector 152, and an electric vehicle operator 160, via a mobile communication device 162. The Smartlet™. 110 is connected to the local power grid 120 by an electric power line 170, and to the electric vehicle 150 by the electrical connector 152. The flow of electrical power may be in either direction for both of these electrical connections. The Smartlet™ 110 has a communication link to the payment station 135 over a LAN 180. The LAN 180 may be either a WLAN or a PLC network. The payment station 135 has a communication link to the server 140 over a WAN 185. (In this embodiment, the payment station 135 is taking the place of the data control unit 130 for acting as a bridge between the LAN and the WAN.) The electric vehicle operator 160 may use the mobile communication device 162 to establish a communication link to the Smartlet™ 110 over a wireless network 190. This wireless network may be a WLAN or a WPAN. Instead of using a mobile communication device 162, the electric vehicle operator 160 may manually interact with the payment station 135, which then sends appropriate instructions to the Smartlet™ 110 regarding charging of the electric vehicle 150. In preferred embodiments these instructions will include an instruction to unlock a cover over the electrical receptacle 112, thus allowing the vehicle operator 160 to connect the electric vehicle 150 to the electrical receptacle 112 with the electrical connector 152.

[0042] The payment station 135 can be several tens of meters remote from the Smartlet™ 110. The payment station 135 is shown comprising a currency reader, a credit card reader, a receipt printer, a display and input buttons. However, the payment station does not have to include all of these components. For example, some payment stations may not include a currency reader and will only allow payment by credit card using the credit card reader. The electric vehicle operator 160 can use the payment station 135 to pay for and schedule recharging of the electric vehicle 150, and also for V2G transactions. The payment station 135 may also be used to pay for parking. Further details of the payment station 135 are provided in FIG. 6 and the related description.

[0043] A schematic of the Smartlet™ 110 is provided in FIG. 3. The Smartlet™ 110 comprises an electrical receptacle 112, a lockable cover 1125 over the electrical receptacle 112, a control device 171, a current measuring device 172, an electric power line 170, a controller 111, a display unit 113, a vehicle detector 115, a WLAN transceiver 181, an alternating current line transceiver 182, a WPAN transceiver 191 and an RFID transceiver 192.

[0044] Electric power is delivered to receptacle 112 along power line 170. Controller 111 is used to lock and unlock the cover 1125; the lock mechanism is electromechanical. When unlocked, the cover 1125 may be lifted by the vehicle operator 160 in order to connect the electric vehicle 150 to the electrical receptacle 112 using the electrical connector 152. Control device 171 is used to turn the electric supply at the receptacle 112 on and off. The control device 171 is preferably a solid state device and is controlled by controller 111. The current flowing along the power line 170 is measured by current measuring device 172. An example of a suitable measuring device 172 is an induction coil. The controller 111 is programmed to monitor the signal from the current measuring device 172 and to calculate the total power either: consumed (in recharging the electric vehicle); or transferred to the local power grid 120 from the electric vehicle 150 (V2G). It is also envisaged that power may be both consumed and transferred to the grid during the time an electric vehicle is connected to the Smartlet™ 110, in which case the controller 111 will calculate both the power consumed and the power transferred to the local power grid 120.

[0045] The indicators 114 and display 113 are controlled by the controller 111 and are used to provide information to the Smartlet™ 110 user. The indicators 114 are discussed in more detail above, with reference to FIG. 1, and the display 113 is discussed in more detail below with reference to FIG. 4.

[0046] Vehicle detector 115 is used to detect the presence of a vehicle in the parking space corresponding to the Smartlet™ 110. The vehicle detector 115 is controlled by the controller 111. The vehicle detector 115 is a detector such as a sonar sensor array, a camera, or an induction coil. The sonar array is an array as used on the rear bumper of automobiles to detect close proximity to an object; this array can be attached to the Smartlet™ 110 or will be mounted to a support structure in close proximity to the Smartlet™ 110. The camera is a digital camera providing a video signal to the Smartlet™ 110; the video signal is processed by an object recognition program to detect the presence of a vehicle or other obstruction. The induction coil is either embedded in the pavement of the parking space or is protected by a roadworthy casing attached to the surface of the pavement. The induction coil is connected to the Smartlet™ 110 and detects the presence of large metal objects in close proximity to the coil (such as an engine block, electric motor or rear differential of a vehicle).

[0047] The controller 111 is shown with four transceivers—a WLAN transceiver 181, an alternating current line transceiver 182, a WPAN transceiver 191 and an RFID transceiver 192. A transceiver is a device that both sends and receives signals, allowing for two-way communication. The WLAN transceiver 181 allows for the controller to communicate with mobile communication devices which are carried by a vehicle operator 160 (see communication link 190 in FIGS. 1 & 2) and with a data control unit 130 or payment station 135 (see communication link 180 in FIGS. 1 & 2). WLAN transceiver 181 could be a Wi-Fi® transceiver. The alternating current line transceiver allows the controller to communicate on a PLC network with a control data unit 130 or payment station 135 (see communication link 180 in FIGS. 1 & 2). The WPAN transceiver 191 allows the controller 111 to communicate with mobile communication devices 162 which are carried by the vehicle operator 160. WPAN transceiver 191 could be a BlueTooth® or ZigBee® transceiver. The RFID transceiver 192 allows the controller to communicate with a compatible RFID device carried by the vehicle operator 160. An example of an RFID device that could be carried by the vehicle operator 160 is a FasTrak® card. A FasTrak® device is an example of a two-way RFID communication device. Although, a one-way RFID communication device from vehicle operator 160 to controller 111 can be utilized. Not all embodiments of the Smartlet™ 110 have all four types of transceiver; however, all Smartlet™ 110 will have at least one wireless transceiver for communication with compatible mobile wireless communication devices 162 available to vehicle operators 160, and one transceiver for communication with the data control unit 130. See FIGS. 1 & 2.

[0048] A more detailed view of the display unit 113 is shown in FIG. 4. An example of parking information is shown on the display unit 113—an indicator 1131 shows the paid parking time remaining in minutes 1132 or a parking violation 1133. This parking information may be displayed in many other ways than that shown in FIG. 4. The display unit 113 may be an LCD (liquid crystal display); although other passive flat panel displays such as OLEDs (organic light emitting displays) and other emissive flat panel displays such as FEDs (field emission displays) may be used. When a passive display unit 113 is used it is preferred that it be backlit, so as to be readily viewed in low ambient light conditions. The display unit 113 is attached to the Smartlet™ 110 so that it is readily observable by the vehicle operator 160. For example, the display 113 may be mounted on a pole at a height of approximately 125 cm above the pavement, and the Smartlet™ 110 would also be mounted on the pole at a convenient height for the vehicle operator. The indicator lights 114 may be positioned next to the display 113, or may be positioned on the Smartlet™ 110 itself, as shown in FIGS. 1 & 2. The display 113 is controlled by the controller 111. The display 113 may also be used to display information regarding the vehicle charging process, such as: time charging, power consumed, estimated time to completion of charging, vehicle-to-grid (V2G) power transferred, general status indications and error warnings.

[0049] A schematic diagram of the server 140 is shown in FIG. 5. The server 140 comprises a computer 141, report generator 142, and database 143. The server 140 is configured to communicate with the following: Smartlet™ network 195; World Wide Web 197; utility companies 144, for receiving power load management data; credit card companies 145, for credit authorization and charging; FasTrak® database 146, for debiting FasTrak® accounts; and banks 146, for debiting bank accounts. The database 143 is used to store consumer profiles and other data required for report generation, as described below.

[0050] The report generator 142 creates reports such as: utility company reports 1421, detailing power consumed and V2G power sold to local power grid 120; subscriber reports 1422, detailing power consumed and V2G power sold to the local power grid 120, account balance, payments and invoices, and subscriber profile data; and tax authority reports 1423, providing details of taxable transactions.

[0051] The Smartlet™ network 195 comprises a multiplicity of data control units 130 and/or payment stations 135, each data control unit 130 and/or payment station 135 being connected by a communication link 180 to a multiplicity of Smartlets™ 110. The communication link 185 between the computer 141 and the Smartlets™ network 195 is a WAN.

[0052] The server 140 is interfaced with the Web 197 to allow subscribers (owners and operators 160 of electric vehicles 150) to do the following: (1) set-up user/consumer profiles; and (2) determine availability of Smartlets™ 110 for recharging their electric vehicles 150. A user profile contains financial account information—details required for payment—and may also include information such as whether the vehicle operator wants to: charge the electric vehicle only during periods of lower power rates; not charge the vehicle during periods of high power grid load; and sell power to the local grid. The availability of Smartlets™ 110 is stored on the server and the information is collected from the Smartlet™ network 195. There are two ways that the availability of a Smartlet™ 110 can be determined: (1) using a vehicle detector 115 (see FIG. 3 and related description) to determine whether the parking space corresponding to the Smartlet™ 110 is available; and (2) flagging a Smartlet™ 110 as being unavailable whenever charging is ongoing, V2G is ongoing or parking has been paid for.

[0053] A schematic diagram of the payment station 135 is shown in FIG. 6. The payment station 135 comprises a controller 1351, a display 1352, a set of buttons 1352, a credit card reader 1354, a receipt printer 1355, a currency reader 1356, a wireless transceiver 1357 and an alternating current line transceiver 1358.

[0054] The display 1352 provides a vehicle operator 160 with information regarding recharging and/or parking their electric vehicle 150. The display shares the same characteristics as the display 113 discussed above with reference to FIG. 4. However, the display 1352 may also be touch sensitive, allowing a vehicle user to input information directly on the display screen 1352. The buttons 1353 allow for input of information requested from the display 1352.

[0055] The credit card reader 1354 is used for reading credit cards, debit cards, smart cards, and other cards that are used for identification purposes or for making payment. The printer 1355 is used for printing receipts, when requested by the consumer. The printer 1355 may also be used to print receipts for displaying in the electric vehicle 150 to show that recharging and/or parking is properly permitted. The currency reader 1356 is used for accepting currency—notes and/or coins—for payment. The currency reader 1356 is able to authenticate and identify the value of currency accepted.

[0056] The payment station 135 is networked to Smartlets™ 110 via either a WLAN or a PLC. The payment station controller 1351 takes the place of data control unit 130 in acting as a bridge between the LAN 180 and the WAN 185. See FIGS. 1 & 2.

[0057] A vehicle user 160 can use the network-controlled charge transfer systems 100 and 200 for charging their electric vehicle 150. A vehicle user 160 who has a user profile on the server 140 is referred to as a subscriber. Some examples of how the systems 100 and 200 can be used are provided below.

[0058] Vehicle Charging Utilizing a Mobile Wireless Communication Device [0059] 1. a subscriber uses the Internet to establish a profile, which includes setting-up payment by credit card, debiting a bank account, a FasTrak® account, a Paypal® account, or other financial service; [0060] 2. the subscriber uses a wireless mobile communication device 162, such as a mobile phone or a FasTrak® card, to request to the Smartlet™ 110 to charge the electric vehicle 150; [0061] 3. the subscriber connects the electric vehicle 150 to the Smartlet™ 110 using the connector 152 (see FIGS. 1 & 2); [0062] 4. the Smartlet™ 110 relays this request over the communication network to the server 140; [0063] 5. the server 140 accesses the subscriber profile from the database 143, validates the payment source by contacting the credit card company, FasTrak® database or bank, and via the communication network enables the Smartlet™ 110 to charge the vehicle 150; [0064] 6. based on the subscriber profile and load management data from the utility company the server determines the charging periods and communicates this information to the Smartlet™ 110; [0065] 7. the Smartlet™ 110 monitors the charging current, as described above with reference to FIG. 3; [0066] 8. when the vehicle 150 is disconnected from the Smartlet™ 110, charging is disabled and a bill is sent to the payment source. Note that determining when the electric vehicle 150 is disconnected from the Smartlet™ 110 can be done by: detecting when the current flow goes to zero; or using a sensor on the receptacle 112 which detects the mechanical removal of the connector 152. If a sensor is used, the sensor is monitored by controller 111. See FIG. 3.

[0067] Note that the load management data from the utility company may limit the ability to recharge the vehicle 150 or the recharge rate for vehicle 150, according to a Demand Response system. For example, the utility company could send a message to the Smartlet™ server 140 requiring a reduction in load. The Smartlet™ server 140 then turns off charging of some vehicles 150. Which vehicles have charging stopped will depend on the subscriber profiles and the requirements of the Demand Response system. The Demand Response system and subscriber profiles may also allow for V2G.

[0068] The general procedure described above is also followed for V2G or a combination of charging and V2G, except that V2G will result in credits to the subscriber's account for sale of power to the local power grid 120.

[0069] Vehicle Charging Utilizing a Payment Station [0070] 1. vehicle user 160 uses the payment station 135 to request and pay for charging the vehicle 150; [0071] 2. vehicle user 160 connects the electric vehicle 150 to the Smartlet™ 110 using connector 152; [0072] 3. the payment station 135 communicates via WAN 185 with server 140 for payment authorization; [0073] 4. the payment station 135 enables the Smartlet™ 110 for charging; [0074] 5. when the vehicle is disconnected from the Smartlet™ 110, charging is disabled, the payment station 135 is notified, the payment station 135 notifies the server 140 and a bill is sent to the payment source. Note that the load management data from the utility company may limit the ability to recharge the vehicle 150 or the recharge rate for vehicle 150, according to a Demand Response system.

[0075] The general procedure described above is also followed for V2G or a combination of charging and V2G, except that V2G will result in credits to the vehicle user's account for sale of power to the local power grid 120.

[0076] Vehicle Parking Utilizing a Mobile Wireless Communication Device [0077] 1. a subscriber uses the Internet to establish a profile, which includes setting-up payment by credit card, debiting a bank account, a FasTrak® account, a Paypal® account, or other financial service; [0078] 2. the subscriber uses a wireless mobile communication device 162, such as a mobile phone, to request to the Smartlet™ 110 parking for the vehicle 150; [0079] 3. the Smartlet™ 110 relays this request over the communication network to the server 140; [0080] 4. the server 140 accesses the subscriber profile from the database 143, validates the payment source by contacting the credit card company, FasTrak® database or bank, and via the communication network sends a message to the Smartlet™ 110 to allow parking of the vehicle 150; [0081] 5. the Smartlet™ 110 sets the parking meter shown on display 113 (see FIGS. 3 & 4) and sets the indicators 114, if used; [0082] 6. the server 140 sends a bill to the payment source.
Optionally, if a vehicle detector 115 is used to detect the presence of a vehicle, then the amount of time a vehicle is parked without proper payment may be monitored and communicated to the payment station 135 and server 140.

[0083] Vehicle Parking Utilizing a Payment Station [0084] 1. vehicle user 160 uses the payment station 135 to request and pay for parking the vehicle 150; [0085] 2. the payment station 135 communicates via WAN 185 with server 140 for payment authorization; [0086] 3. the payment station 135 communicates to the Smartlet™ 110 to allow parking; [0087] 4. the server 140 sends a bill to the payment source.

[0088] The above methods for use of the Smartlet™ network for electric vehicle charging, V2G and parking can be combined. For example, a parking fee may be imposed in addition to a fee for power consumed in recharging a vehicle. Also, a parking fee may be imposed when a vehicle is parked for V2G.

[0089] The above embodiments of the present invention have been given as examples, illustrative of the principles of the present invention. Variations of the apparatus and method will be apparent to those skilled in the art upon reading the present disclosure. These variations are to be included in the spirit of the present invention. For example, the Smartlet™ network may be used for public and private garage and parking lot charging of electric vehicles. Furthermore, the Smartlet™ network may be used for home charging of electric vehicles, in which case a Smartlet™ receptacle in the home is connected via a LAN and a WAN to the Smartlet™ server 140. Those skilled in the art will appreciate that the Smartlet™ network may also be used for non-vehicle applications, including selling electricity to people in places such as airports and coffee shops.