This application pertains to electricity distribution, and more particularly, to a method, system, and apparatus for distributing electricity to electric vehicles, monitoring the distribution thereof, and providing automated billing.
Pure electric vehicles and plug-in hybrid electric vehicles are beginning to take hold in the marketplace. The price of energy for operating an electric vehicle is much lower than that of running a conventional gasoline vehicle. For example, in today's prices, to drive an electric vehicle 30 miles costs around $0.60 compared with around $2.00-$3.00 for a gasoline vehicle. However, one of the challenges with electric vehicle transportation is the ability for electric vehicle users to conveniently recharge their vehicles at remote locations, while providing adequate compensation to both real estate owners and electricity producers. Although electric vehicles are four to five times more efficient than gasoline cars, they suffer from a lack of infrastructure that effectively limits how far they can travel.
Increasing the number of locations for vehicles to recharge quickly could mean lower costs by reducing battery payloads, and would broaden the range of travel. Nevertheless, conventional efforts to accelerate the installation and adoption of charging locations have been elusive and ineffective. Difficulties persist, particularly in the areas of providing secure monitoring and control of the electricity distribution to the electric vehicles. Moreover, challenges remain for providing automated tracking and billing. These are only a few of the challenges presented by conventional approaches, which are impeding the wider adoption of electric vehicle technologies, and ultimately hurting efforts for energy independence and environmental responsibility.
Accordingly, a need remains for a method, system, and apparatus for distributing electricity to electric vehicles, monitoring the distribution thereof, and for providing automated billing.
The foregoing and other features of the invention will become more readily apparent from the following detailed description, which proceeds with reference to the accompanying drawings.
To solve the problems in the prior art, an embodiment of the invention begins by setting forth a device for use by station owners to provide access to convenient electrical recharging for electric vehicle users, and a simple way for the electric vehicle users to pay for the electrical recharging. While often referred to herein as “electric vehicles,” such vehicles can include plug-in hybrid vehicles, pure electric vehicles, or any one of a variety of vehicles that operate or move using at least some electricity.
Some embodiments of the invention provide an apparatus, system, and method of billing to automatically and securely bill for electricity or energy usage by users of devices such as electric vehicles. In one embodiment, a plug outlet device may be situated in a recharging location accessible by electric vehicles. For example, a provider such as a real estate owner, electricity or energy producer, or station owner may provide the plug outlet device and/or the electricity for recharging the electric vehicles. For the sake of simplicity, these will hereinafter be referred to merely as a “provider,” although such reference can mean one entity, or more than one entity, involved in providing the plug outlet device and/or the electricity. The provider may locate the plug outlet device in the recharging location and ensure that an energy source is electrically coupled to the plug outlet device. The plug outlet device may include, for example, a microcontroller, a radio frequency identification (RFID) sensor, an infrared sensor, a contactor, a current sensor, or a communication device, among other components, any or all of which may be surrounded by an enclosure.
An electric vehicle user may plug the vehicle into the plug outlet device and begin verification of his or her account status by exposing, or otherwise operatively coupling, an RFID tag to the RFID sensor. The RFID tag may have associated therewith a user's identification (ID). The RFID tag may be embedded in a plug adapter apparatus, which may be operatively coupled to the plug outlet device. The RFID tag may be structured to communicate with the RFID sensor only when the terminal end of the plug adapter apparatus is inserted into the plug outlet device.
The user's ID and location information of the plug outlet device, among other information, may be transmitted to a remote computer server, which may then verify any of the information including the user's ID and the location information. Once verified, the remote server may transmit a signal back to the plug outlet device at the recharging location, which may trigger a contactor within the plug outlet device to release the flow of electricity to the vehicle. When the user unplugs the plug adapter apparatus from the plug outlet device, a message may be transmitted to the remote server detailing the amount of electricity or energy consumed for the charging of the electric vehicle. The remote server may access its database to determine the price of electricity or energy associated with the particular location of the plug outlet device, and may access the database to determine the provider's surcharge. The surcharge may be associated with a particular station or plug outlet device, among other possibilities. The remote server may automatically bill or deduct from the user's account for the electricity or energy used and the surcharge. The remote server may credit the account or accounts of the provider for the cost of the electricity and/or the surcharge. As previously mentioned, the provider may be any one or more of the station owner, real estate owner, or electricity producer, among other possibilities.
In one example embodiment, the described system can lower transaction costs by avoiding credit card transaction fees. Furthermore, the electric vehicle user can access a map of stations that participate in a common vehicle-charging network, which improves knowledge about the network and encourages increased usage of the network by electric vehicles users and station owners; electric vehicle charging at each participating station is accessible using the electric vehicle user's ID. In addition, the provider can earn a return on the investment of installing the plug outlet device, and other components, thereby supplying an incentive to the provider to participate. In another example embodiment, the plug outlet device can recognize any vehicle user ID on the network, which also increases the likelihood that electric vehicle users will connect to the system, and can reassure and incentivize the provider to continue offering electric vehicle charging services. These and other embodiments will now be described in detail with reference to the following figures.
The plug outlet device 130 may include an RFID sensor 40, which may be located beneath a shielded portion of the plug adapter apparatus 120 when the plug adapter apparatus 120 is plugged in to the plug outlet 10, so that the RFID sensor 40 can identify the RFID tag 50. The RFID sensor 40 may be structured to read information from the RFID tag 50. The plug outlet device 130 may also include a microcontroller 30, a communication device 60, a contactor 70, a voltage or current sensor 20, and a connection to a high voltage source 80. Any or all of the components of the plug outlet device 130 may be contained within the enclosure 115.
As previously mentioned, the provider may locate the plug outlet device 130 at the recharging location and ensure that an energy source, such as the high voltage source 80, is electrically coupled to the plug outlet device 130. An electric vehicle user may plug the plug adapter apparatus 120 into the plug outlet device 130 and begin verification of his or her account status by exposing, or otherwise operatively coupling, the RFID tag 50 to the RFID sensor 40. The RFID tag 50 may have associated therewith a user's identification (ID). The RFID tag 50 may be embedded in the plug adapter apparatus 120, which may be operatively coupled to the plug outlet device 130. The RFID tag 50 may be structured to communicate with the RFID sensor 40 only when the terminal end of the plug adapter apparatus 120 is inserted into the plug outlet device 130.
The communication device 60 may provide a wireless or wired connection from the microcontroller 30 to an intermediary wireless device 32, such as a cell phone. One example of the wireless connection includes a Bluetooth® or other short-distance wireless connection technology operatively coupling the microcontroller 30 to the intermediary wireless device 32. The intermediary wireless device 32 may communicate with a wireless network such as a cellular network so that a communication link can be established between the remote server 90 and the microcontroller 30. The microcontroller 30 can automatically adjust to different varieties of communication devices, whether Bluetooth®, wired, cellular, satellite, WI-FI®, etc. In addition, the intermediary wireless device 32 can maintain a log of each transaction or communication to be stored on the intermediary wireless device 32 for future reference.
The remote server 90 may be located either on the general premises where the plug outlet device 130 is located—however, the remote server 90 is preferably located at a remote location different from where the plug outlet device 130 is located. In addition, location information of the plug outlet device 130, such as a location ID number, may also be transmitted, among other information, from the microcontroller 30 to the communication device 60, and then to the remote server 90. The remote server 90 may verify the status of the user ID number and the location information, and may transmit a verification signal to the microcontroller 30.
When the microcontroller 30 receives the verification signal, it may switch the contactor 70 to electrically couple the high voltage source 80 to the plug outlet 10. As soon as the high voltage is electrically coupled to the plug outlet 10, the microcontroller 30 begins monitoring energy usage by taking measurements using a voltage or current sensor 20. The microcontroller 30 transmits the measurements from the voltage or current sensor 20 to the remote server 90. When the user or vehicle finishes receiving electricity, the user unplugs the plug adapter apparatus 120 from the plug outlet 10 of the plug outlet device 130. This interruption may be detected by the voltage or current sensor 20 and/or the RFID sensor 40, each of which are operatively coupled to the microcontroller 30.
The microcontroller 30 may transmit a message to the remote server 90 indicating that the user or vehicle is finished receiving electricity or energy, and detailing the amount of electricity or energy consumed for the charging of the electric vehicle. The remote server 90 may access the database 92 to determine the price of electricity or energy associated with the particular location of the plug outlet device 130, or based on a source of energy, and may access the database 92 to determine the provider's surcharge. The surcharge may be associated with a particular station or plug outlet device, among other possibilities. The remote server 90 may also store a record of the electricity or energy usage and may automatically bill or deduct from the user's account or accounts 94 according to the price and surcharge stored in the database 92 of the remote server 90. Prices of electricity stored in the database 92 can vary based on the location of the plug outlet device 130, and therefore, the database 92 can store a variety of different prices for different locations. In other words, the price of electricity can be determined based on the location of the plug outlet devices. The remote server 90 may credit the account or accounts 94 of the provider by an amount corresponding to the cost of the electricity or energy and/or the surcharge. At about this time, the microcontroller 30 returns to monitoring the RFID sensor 40. While the database 92 and the user/provider account(s) 94 are shown as separate, it should be understood that the database 92 may include the user/provider account(s) 94.
The remote server 90 may also host one or more web pages 140, which can be accessed by one or more computers 140. The one or more web pages 140 can be used to modify the software on the microcontroller 30 and on the remote server 90 to automate the distribution of the electricity, change billing criteria, change ownership of an account, or check the status of the microcontroller 30 or other components of the system, among other possibilities. For example, the server 90 may transmit signals to the microcontroller 30 at regular intervals to check that it is operational. If not, the remote server 90 may alert an administrator via email, text messages, or by some other alert means.
The monitoring and communication device 270 may include an enclosure 190 containing a microcontroller 200, a voltage or current sensor 160, an RFID sensor 210, a communication device 220, and/or an authentication key 230. The voltage or current sensor 160 may measure the charge across the conductive loop 150. The voltage or current sensor 160 may transmit the measured charge to the microcontroller 200. The microcontroller 200 may be operatively coupled to the communication device 220, the authentication key 230, and the RFID sensor 210. The monitoring and communication device 270 may be operatively associated with the cord 170 via the conductive loop 150.
The plug outlet device 280 may include an authentication device 240, an RFID tag 260, a contactor 250, and a plug outlet 290. The plug outlet device 280 may be electrically coupled to a high voltage source 300, but is normally off until the plug end 180 is inserted, detected, and validated. The authentication device 240 may be operatively coupled to the contactor 250. The contactor 250 may switch on the flow of electricity from the high voltage source over line 300 to the plug outlet 290. The RFID tag 260 may be read from outside of the enclosure of the plug outlet device 280.
For example, the communication device 220 may provide a Bluetooth® or other wireless or wired connection from the microcontroller 200 to an intermediary wireless device 202, such as a cell phone. The intermediary wireless device 202 may communicate with a wireless network such as a cellular network so that a communication link can be established between the remote server 310 and the microcontroller 200. The microcontroller 200 can automatically adjust to different varieties of communication devices, whether Bluetooth®, wired, cellular, satellite, WI-FI®, etc. In addition, the intermediary wireless device 202 can maintain a log of each transaction or communication to be stored on the intermediary wireless device for future reference.
The remote server 310 may verify that the station ID number is a valid plug-in location and that the microcontroller ID is associated with a valid user account. The remote server 310 may wirelessly transmit a verification message to the microcontroller 200 of the monitoring and communication device 270. When the server verification is received by the microcontroller 200, the microcontroller 200 may transmit the authentication key 230 of the monitoring and control device 270 to the authentication device 240 of the plug outlet device 280 over either a wireless or wired connection. After authentication, the contactor 250 may be switched to supply electricity from the high voltage source 300 to the plug outlet 290. The microcontroller 200 may monitor the voltage or current sensor 160, which monitors the charge on the conductive loop 150 and may transmit this information to the remote server 310. The amount of electricity or energy used can be determined based on the charge information gathered from the conductive loop 150. When the user unplugs the plug end 180 from the plug outlet device 280, this action is detected by the voltage or current sensor 160.
The microcontroller 200 may wirelessly transmit a message to the remote server 310 indicating that the user or vehicle is finished receiving electricity or energy, and detailing the amount of electricity or energy consumed for the charging of the electric vehicle, or the charge information measured by the voltage or current sensor 160. The remote server 310 may access the database 312 to determine the price of electricity or energy associated with the particular location of the plug outlet device 280, or based on a source of energy, and may access the database 312 to determine the provider's surcharge. Prices of electricity stored in the database 312 can vary based on the location of the plug outlet device 280, and therefore, the database 312 can store a variety of different prices for different locations. In other words, the price of electricity can be determined based on the location of the plug outlet devices. The remote server 310 may also store a record of the electricity or energy usage and may automatically bill or deduct from the user's account or accounts 314 according to the price and surcharge stored in the database 312 of the remote server 310. The remote server 310 may credit the account or accounts 314 of the provider by an amount corresponding to the cost of the electricity or energy and/or the surcharge. At about this time, the microcontroller 200 returns to monitoring the RFID sensor 210. It should be understood that while the database 312 and the user/provider account(s) 314 are shown as separate, the database 312 can include the user/provider account(s) 314.
The microcontroller 200 may include a security feature to prevent tampering with the monitoring and communication device 270. Specifically, whenever the microcontroller 200 detects a break in the conductive loop 150 after initial placement of the conductive loop 150 around the cord 170, the microcontroller 200 would prevent authentication until reset by an authorized administrator. For example, the microcontroller 200 may prevent the authentication key 230 from being provided to the authentication device 240 when a break is detected in the conductive loop 150, unless otherwise overridden by the administrator.
The third example embodiment associated with
Having described and illustrated the principles of the invention with reference to illustrated embodiments, it will be recognized that the illustrated embodiments can be modified in arrangement and detail without departing from such principles, and can be combined in any desired manner.
For example, the embodiments of the invention may provide both monitoring and control of electricity or energy distribution, and with networks that require either long distance or local verification of location and user ID numbers. The contactors discussed above (e.g., 70 and 250) can be modular so that the same type of microcontroller (e.g., 30, 200, and 600) can be used in applications that control current flow (switch on and off) and applications that only monitor energy usage.
By allowing providers such as real estate owners and energy producers to easily bill a large number of electric vehicle users, the system allows not only the users, but also the developers of stations for electric vehicles, the benefit from the gain in efficiency offered by electric vehicles.
Today's costs for electricity is about $0.10/kwh. The cost for energy from renewable sources is higher at about a cost of $0.15 to $0.20/kwh. The embodiments of this invention allow for energy producers to generate energy from renewable sources at the higher cost, and still offer electric vehicle users a significant savings over gasoline. In other words, by facilitating billing transactions between electric vehicle users and electricity producers, the embodiments of the invention can be used to give all parties a convenient, cost effective way to combine the efficiency of electric vehicles and the environmental benefits of renewable generation with an end price that is lower to the driver than more polluting gasoline transportation. The system may automatically check recharging station maintenance from a remote server, which provides the station owner with assurance that the station will remain operational. The billing may also be fully automated thereby eliminating unessential labor costs that would otherwise be a limiting factor to implementing a large scale electricity distribution system for electric vehicles.
Other embodiments may provide for alternate configurations, which carryout similar objectives to the preferred embodiments. These involve attaching the communication components to the vehicle rather than to the plug outlet, a means of conserving components in arrays of multiple plug outlets, and a configuration that combines components into enclosures, which can easily attach to a vehicle or a stationary power source using a wire conductor (e.g., loop) or a plug adaptor. Furthermore, embodiments of the invention may include a method by which modularized components provide flexibility across a variety of communication systems and allow users and real estate owners to choose between either monitoring and/or control capabilities. Other applications of the disclosed embodiments include: security systems, backup power, automated energy management systems, and power generation monitoring and control systems, among other possibilities.
Although the foregoing discussion has focused on particular embodiments, other configurations are contemplated. In particular, even though expressions such as “according to an embodiment of the invention” or the like are used herein, these phrases are meant to generally reference embodiment possibilities, and are not intended to limit the invention to particular embodiment configurations. As used herein, these terms can reference the same or different embodiments that are combinable into other embodiments.
Consequently, in view of the wide variety of permutations to the embodiments described herein, this detailed description and accompanying material is intended to be illustrative only, and should not be taken as limiting the scope of the invention. What is claimed as the invention, therefore, is all such modifications as may come within the scope and spirit of the following claims and equivalents thereto.
This application claims the benefit of U.S. provisional patent application Ser. No. 61/161,358, filed Mar. 18, 2009, herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4532418 | Meese et al. | Jul 1985 | A |
5184058 | Hesse et al. | Feb 1993 | A |
5272431 | Nee | Dec 1993 | A |
5323099 | Bruni et al. | Jun 1994 | A |
5327066 | Smith | Jul 1994 | A |
5349535 | Gupta | Sep 1994 | A |
5369352 | Toepfer et al. | Nov 1994 | A |
5422624 | Smith | Jun 1995 | A |
5461298 | Lara et al. | Oct 1995 | A |
5461299 | Bruni | Oct 1995 | A |
5467006 | Sims | Nov 1995 | A |
5499181 | Smith | Mar 1996 | A |
5548200 | Nor et al. | Aug 1996 | A |
5563491 | Tseng | Oct 1996 | A |
5594318 | Nor et al. | Jan 1997 | A |
5684379 | Svedoff | Nov 1997 | A |
5717374 | Smith | Feb 1998 | A |
5742229 | Smith | Apr 1998 | A |
5790976 | Boll et al. | Aug 1998 | A |
5806018 | Smith et al. | Sep 1998 | A |
5847537 | Parmley, Sr. | Dec 1998 | A |
5914654 | Smith | Jun 1999 | A |
5926004 | Henze | Jul 1999 | A |
5927938 | Hammerslag | Jul 1999 | A |
6018293 | Smith | Jan 2000 | A |
6067008 | Smith | May 2000 | A |
6185501 | Smith et al. | Feb 2001 | B1 |
6307347 | Ronning | Oct 2001 | B1 |
6463967 | Boyle | Oct 2002 | B1 |
6614204 | Pellegrino et al. | Sep 2003 | B2 |
6727809 | Smith | Apr 2004 | B1 |
6771188 | Flick | Aug 2004 | B2 |
6850898 | Murakami et al. | Feb 2005 | B1 |
6859009 | Jablin | Feb 2005 | B2 |
6864807 | Todoriki et al. | Mar 2005 | B2 |
7058524 | Hayes et al. | Jun 2006 | B2 |
7068991 | Parise | Jun 2006 | B2 |
7298289 | Hoffberg | Nov 2007 | B1 |
7358851 | Patenaude et al. | Apr 2008 | B2 |
7373247 | Park | May 2008 | B2 |
7602274 | Lee et al. | Oct 2009 | B2 |
7616105 | Macielinski et al. | Nov 2009 | B2 |
7737829 | Nishiyama | Jun 2010 | B2 |
7994908 | Tonegawa et al. | Aug 2011 | B2 |
7999665 | Chander et al. | Aug 2011 | B2 |
8000074 | Jones et al. | Aug 2011 | B2 |
8054048 | Woody et al. | Nov 2011 | B2 |
8093861 | Christensen | Jan 2012 | B2 |
20020070881 | Marcarelli et al. | Jun 2002 | A1 |
20020158749 | Ikeda et al. | Oct 2002 | A1 |
20030120442 | Pellegrino et al. | Jun 2003 | A1 |
20030209375 | Suzuki et al. | Nov 2003 | A1 |
20040104814 | Christensen et al. | Jun 2004 | A1 |
20050052286 | Perraud et al. | Mar 2005 | A1 |
20050143955 | Quint et al. | Jun 2005 | A1 |
20070126395 | Suchar | Jun 2007 | A1 |
20070278998 | Koyama | Dec 2007 | A1 |
20080039989 | Pollack et al. | Feb 2008 | A1 |
20080208401 | Kumar et al. | Aug 2008 | A1 |
20090021213 | Johnson | Jan 2009 | A1 |
20090030712 | Bogolea et al. | Jan 2009 | A1 |
20090062967 | Kressner et al. | Mar 2009 | A1 |
20090066287 | Pollack et al. | Mar 2009 | A1 |
20090079388 | Reddy | Mar 2009 | A1 |
20090082957 | Agassi et al. | Mar 2009 | A1 |
20090091291 | Woody et al. | Apr 2009 | A1 |
20090184833 | Tonegawa et al. | Jul 2009 | A1 |
20090192927 | Berg et al. | Jul 2009 | A1 |
20090195349 | Frader-Thompson et al. | Aug 2009 | A1 |
20090210357 | Pudar et al. | Aug 2009 | A1 |
20090237239 | McSheffrey | Sep 2009 | A1 |
20090251300 | Yasuda et al. | Oct 2009 | A1 |
20090261779 | Zyren | Oct 2009 | A1 |
20090313103 | Ambrosio et al. | Dec 2009 | A1 |
20100049737 | Ambrosio et al. | Feb 2010 | A1 |
20100060452 | Schuster et al. | Mar 2010 | A1 |
20100065627 | Outwater | Mar 2010 | A1 |
20100153193 | Ashby et al. | Jun 2010 | A1 |
20100161480 | Littrell | Jun 2010 | A1 |
20100161481 | Littrell | Jun 2010 | A1 |
20100174667 | Vitale et al. | Jul 2010 | A1 |
20100211340 | Lowenthal et al. | Aug 2010 | A1 |
20100211643 | Lowenthal et al. | Aug 2010 | A1 |
20100225475 | Karch et al. | Sep 2010 | A1 |
20100241542 | Pinkusevich et al. | Sep 2010 | A1 |
20100274570 | Proefke et al. | Oct 2010 | A1 |
20100315197 | Solomon et al. | Dec 2010 | A1 |
20110282535 | Woody et al. | Nov 2011 | A1 |
Number | Date | Country |
---|---|---|
2438979 | Dec 2007 | GB |
2006074868 | Mar 2006 | JP |
2006074868 | Mar 2006 | JP |
2008083022 | Apr 2008 | JP |
2008083022 | Apr 2008 | JP |
2008295136 | Dec 2008 | JP |
2008295136 | Dec 2008 | JP |
Entry |
---|
The Cost of Generating Electricity , Mar. 2004, The Royal Academy of Engineering, pp. 7-13. |
International Search Report/Written Opinion, PCT/US2010/027651, Oct. 21, 2010, ISA/KR, Korean Intellectual Property Office, Daejeon, Republic of Korea. |
Wang, Yunyan, “Management Information System of Charging Station for Electric Vehicle (EV),” Proceedings of the Eighth International Conference on Electrical Machines and Systems, 2005 ICEMS, vol. 1, Sep. 27-29, 2005, pp. 857-860. |
Pratt, Robert G., et al., “Development of a Microprocessor-based, Credit Card Operated, Electric Vehicle Parking/Charging Meter System,” Electric Vehicle Council, EVC Expo '83, Oct. 4-6, 1983, pp. 1-9, Detroit, Michigan. |
Abella, M. Alonso, et al., “Photovoltaic Charging Station for Electric Vehicles,” 2003, Proceedings of 3rd World Conference on Photovoltaic Energy Conversion, May 12-16, 2003, vol. 3, pp. 2280-2283, Osaka,Japan. |
C'Connell, Lawrence G., “Infrastructure Considerations for Electric Vehicles,” Electric Power Research Institute, No. 921539, Aug. 1992, pp. 1-5. |
Coulomb Technologies, “Changing the Way We Get Places,” http://www.coulombtech.com/library/chargepoint—appnote.php, Dec. 16, 2009. |
Pudar, U.S. Appl. No. 61/44,009, Provisional Application Specification, p. 5—Par. 18. |
U.S. Appl. No. 61/144,009, filed Jan. 12, 2009, Nikola Pudar. |
U.S. Appl. No. 61/210,306, filed Mar. 17, 2009, Igor Pinkusevich. |
The Cost of Generating Electricity, Mar. 2004, The Royal Academy of Engineering, pp. 7-13. |
U.S. Appl. No. 61/144,009, filed Jan. 12, 2009. |
U.S. Appl. No. 61/210,306, filed Mar. 17, 2009. |
IBM, Green Car Versatile Plug, Dec. 18, 2008, IPCOM000177564D. |
Number | Date | Country | |
---|---|---|---|
20100241560 A1 | Sep 2010 | US |
Number | Date | Country | |
---|---|---|---|
61161358 | Mar 2009 | US |