The present invention is generally in the field of electric charging, and relates to the systems, hardware, and mobile application software for implementing wireless charging zones for electric vehicles.
Commercial and personal transpiration is currently dependent on fossil fuels. Use of fossil fuels, however, has become increasingly problematic. Rising costs, pollution, safety, and many countries dependence on foreign sources of fossil fuels have lead consumers to seek alternatives to traditional fuel-powered vehicles.
One alternative to traditional vehicles is electrically powered vehicles and electric/fuel hybrid vehicles. Electric vehicles utilize one or more electrical motors for propulsion, typically powered by batteries. The batteries can be charged by one or more sources of electricity, including fossil fuels, nuclear power, and renewable sources such as solar and wind power. Electric vehicles currently must be plugged in to a specially designed outlet to receive power for charging the batteries. Based on the present efficiency of both the batteries and electric motors, the range of electric vehicles is limited.
In accordance with an exemplary embodiment of the present invention, a wireless charging system includes: a charging station having a charging unit for transferring power, a control unit, and a communication unit; an application accessible through a mobile device and capable of communicating with the charging station; and a server capable of communicating with the charging station and the mobile device.
In accordance with another exemplary embodiment of the present invention, a wireless charging system includes: a charging station having a charging unit for transferring power, a communication unit, and a sensor; an application accessible through a mobile device and capable of communicating with the charging station, the application including a parking sequence for positioning a vehicle with respect to the charging unit; and a server capable of communicating with the charging station and the mobile device.
In accordance with yet another exemplary embodiment of the present invention, a wireless charging system includes: a plurality of charging stations having a charging unit for wirelessly transferring power to a vehicle; a server capable of communicating with said charging station and capable of transmitting and receiving scheduling data; and a database operably connected to the server for storing the scheduling data.
In accordance with yet another exemplary embodiment of the present invention, a method of providing a vehicle charging system includes: transmitting charging station information from a server to a user; receiving a selected charging station from said user; recognizing when said user is near said selected charging station; providing parking location information to said user; and initiating a charging sequence.
Other exemplary embodiments of the present invention, including apparatus, systems, methods, and the like which constitute part of the invention, will become more apparent from the following detailed description of the exemplary embodiments and the drawings. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and therefore not restrictive.
The accompanying drawings are incorporated in and constitute a part of the specification. The drawings, together with the general description given above and the detailed description of the exemplary embodiments and methods given below, serve to explain the principles of the invention. In such drawings:
Reference will now be made in detail to exemplary embodiments and methods of the invention as illustrated in the accompanying drawings, in which like reference characters designate like or corresponding parts throughout the drawings. It should be noted, however, that the invention in its broader aspects is not limited to the specific details, representative devices and methods, and illustrative examples shown and described in connection with the exemplary embodiments and methods.
Various exemplary embodiments are directed to a network of charging stations 10 or zones to charge electric vehicles 12 wirelessly through induction charging or magnetic resonance charging. As shown in the example of
The housing 14 may contain various electronic and mechanical components associated with the charging station 10. For example, a charging unit 20 is positioned in the housing 14. The charging unit 20 may be positioned proximate the cover 18 in order to reduce the distance between the charging unit 20 and a receiver 22 positioned on the vehicle 12. The charging unit 20 is capable of wirelessly transmitting power to the receiver 22 and may be capable of fast charging at higher voltages and currents. The charging unit 20 and the receiver 22 may include various configurations of coils having different sizes, orientations, number of loops, and loop diameters, and made from different materials for transmitting and receiving power through induction or magnetic resonance. Various exemplary embodiments may also utilize other forms of wireless power transfer, such as electromagnetic radiation. The receiver 22 is electrically connected to a battery unit 24 which may include one or more rechargeable batteries and a battery management system 25. In an exemplary embodiment, the battery management system 25 is capable of monitoring one or more properties of the batteries, for example charge level, charging rate, temperature, and usage efficiency. The receiver 22 is capable of transferring power received from the charging station 10 to charge the batteries. Various electrical components such as power converters, rectifiers and various control units may be associated with the charging unit 20 and the receiver 22. Various components may also be positioned outside of the housing 14 as desired, including the charging unit 20. A more detailed schematic of an exemplary power system is shown in
The charging unit 20 is connected to a control unit 26. The control unit 26 may include various electronic, mechanical, and/or electromechanical components to perform various control, analytical, and communication functions such as those described herein. The control unit 26 may include one or more microcontrollers, such as an Arduino board to perform dedicated tasks and functions. Though the control unit 26 is depicted and described as a single unit for clarity, it may be comprised of several individual units, working together or in isolation, to perform the various functions described herein.
The control unit 26 may be connected to a power source 28, for example an electrical utility line. The control unit 26 may contain various electronic components to convert or modify the power received from the power source 28 and supply the charging unit 20 with power in an appropriate amount, having the correct current and frequency. The control unit 26 is capable of selectively powering the charging unit 20 at appropriate times, such as by activating the charging unit 20 when a vehicle 12 is detected or a request for charging is received, or by deactivating the charging unit 20 when a vehicle 12 leaves or the battery 24 is completely charged.
The charging station 10 may include one or more sensors 30 used to determine the position of the vehicle 12. The sensors 30 may be located in the housing 14 as depicted in
The control unit 26 may contain, or be connected to, a communication unit 32 to receive and transmit information from various sources. The communication unit 32 may receive and transmit information through a wired connection and/or wirelessly. Wired connections may be achieved through one or more data or network ports. Wireless communication may be achieved through radio frequency, Bluetooth, or WiFi wireless transmission as well as optic, infrared, or other light signaling. The communication unit 32 may be in communication, either through a data connection or an electrical connection to receive and transmit information for other components in the charging station 10. The communication unit may also communicate with devices and locations outside of the charging station 10. The controller 26 and the communication unit 32 may incorporate a beagleboard or beaglebone type device to provide computing and communication functionality.
In various exemplary embodiments, the communication unit 32 transmits and receives information to and from various external devices such as the battery management system 25, the sensors 30, and one or more mobile devices 34. Mobile devices 34 may include any mobile electronic device, such as a mobile phone, tablet, laptop or other computing device. The mobile device 34 may also be a vehicle related device, such as a global positioning device (GPS), dashboard or other onboard, vehicle computer. A vehicle related mobile device 34 may be a dedicated unit or integrated with the vehicle 12 to perform different functions. The mobile device 34 may be capable of receiving information related to the vehicle 12, for example position, battery level, and charging rate. Accordingly, the battery management system 25 may also be able to communicate directly with one or more mobile devices 34.
The communication unit 32 may also be capable of transmitting and receiving information to and from a remote server 36. The remote server 36 may include a dedicated server or a storage network, such as a cloud computing network. The communication unit 32 transmits information to the remote server 36 via the Internet or a dedicated network, either through a hardwired connection or wireless connection as discussed above. In various exemplary embodiments, the sensors 30 communicate with the remote server 36 directly or through the communication unit 32. Information sent to the remote server 36 may include operating status, occupancy status, charging efficiency and statics, sensor data, and usage data. The remote server 36 may also communicate with the mobile device 34 and other devices, such as an additional user device 38 as well as an administrator system 40. The user device 38 may include any user computing device such as a mobile device 34 described above or a stationary computer or terminal. The administrator system 40 may be capable of performing various tasks and operations such as monitoring, management, customer service and support, and/or scheduling. The administrator system 40 may be capable of controlling, monitoring, testing or calibrating the sensors 30. The administrator system 40 may also be capable of sending alerts to users, authorities, and other relevant parties, for example police, fire, medical services, or towing services.
In various exemplary embodiments, the remoter server 36 may be designed to interact with one or more databases 42 for storing information relating to different charging stations 10, different vehicles 12, and/or different users. The server 36 may implement a database management system for storing, compiling, and organizing data, and to allow a user and administrators to access and search the stored data. The databases 42 may contain different units for storing data related to different topics, for example charging station 10 information, user account information, and vehicle 12 information.
The cover 18 may have an opening for receiving a control module 50 having a lid 52 which is visible and/or accessible through the cover 18. The control module 50 may be removable from the charging housing 14. In various embodiments, the control module 50 may be removed from the housing 14 without removing the cover 18. The lid 52 may contain a set of indicators 54, for example light emitting diodes (LEDs). The indicators 54 may provide status notifications for the charging unit 10, for example when the unit is currently charging and when an error has occurred. The indicators 54 may transmit different colored light depending on the notification and may also provide visual signals.
As shown in the examples of
In an exemplary implementation, interior of the charging housing 14 includes the control module 50 and a coil 60. The coil 60 may be a magnetic resonance power transfer coil. The coil 60 is supported by a mounting bracket 62. The mounting bracket 62 may be coupled to the mounting ring 44. The mounting bracket 62 may be made from a variety of materials and may be formed from a material that will not interfere with the power transfer. The coil 60 receives power from the control module 50 through a power connector 64. The control module 50 houses one or more circuit boards 66. The circuit boards 66 may be printed circuit boards containing a variety of electronic components for performing different functions as discussed herein.
In order to utilize a charging station 10, a user may access an application 100 that allows the user, for example and without limitation, to find an available charging station 10, navigate to the available charging station 10, maneuver their vehicle in a correct position for charging, pay for their charging, and monitor the status of their vehicle. Though described herein for use with the exemplary charging statin 10, the application 100 is not limited to such a use, and may be used for any type of vehicle charging. The application 100 may act as an interface between the remote server 36 and the user and may include various software, firmware, and hardware components for performing the various functions described herein. The solution stack to implement and integrate the application 100 with the overall system may utilize a LAMP (Linux (operating system), Apache HTTP Server, MySQL (database software), and PHP, Perl or Python) bundle or other similar solution stack. The application 100 may be designed with one or more languages or frameworks, including HTML, such as HTML5, WML, XML, Java JavaScript, CCS, such as CCS3, Node.js, and DOM. In various exemplary embodiments shown in the Figures and described herein, the application 100 is provided as a mobile application that can be downloaded and installed by a user to a mobile device 34. The application 100 may also be provided as a web application accessible through the Internet. The application 100 may integrate with other applications, services, such as location based services, and systems utilizing application integration software or middleware, for example WebSphere®.
According to an exemplary implementation, a user may initially access the application 100 by download the application 100 to a mobile device 34 or by connecting to the application 100 through the Internet. As shown in the example of
After the user creates an account, the application 100 may institute a push notification transmitting a verification code to a user's email account and/or phone through, for example, a Short Message Service (SMS). The user may be directed to a screen to enter the received verification code to activate their account. If the verification code is rejected the user may have a certain number of tries to reenter the code. If the verification code is continually rejected, a different verification code may be sent. If the verification code is accepted, the user may be then asked to create a password. Once a suitable password has been created, the user may select a security question, either from a predetermined list or by setting up a security questions and answer in a free-form field. The user may then be given the option of selecting an avatar or profile picture. Picture options may be provided by the application and uploaded by a user. Once the user's account is finalized, the user may be redirected to the login screen 102 to login and access the application.
The user may then go through an initial login process 1600, an example of which is depicted in
After a successful login, the user may be presented with a home screen. Showing various information, logos, greetings, and messages. A tool bar may be present along the bottom, or any other visually accessible location, of the screen having navigation icons.
The account button 108 can direct the user to the account home screen 116 as shown in
The user may also select the locations button 110 to access a location list 118 as depicted in
In various exemplary embodiments, the application 100 utilizes an integrated or embedded geographic information system or mapping service 120 as shown in
When a charging station 10 is selected, the mapping service 120 may show a picture of the charging station 10 so that the user will be familiar with the location upon arrival. If desired by the user, the mapping service 120 provides directions from the user location to the selected charging station. The mapping service 120 may continually update to provide turn-by-turn directions to the user, guiding them to the selected charging station 10. The mapping service 120 may also provide information on points of interest in the area surrounding the charging station 10, including parks, museums, galleries, restaurants, shops, and bars.
In various exemplary embodiments, the user may reserve a charging station 10 ahead of time. Reservations may be made by selecting the charging station 10, for example from the location list 118 or from the mapping service 120. Reservations may be made in advance by a user for a specific time for each charging station 10 and stored in a database 42. The application 100 may then indicate to other users that the reserved charging station 10 is in use. Reservation information may be stored in a database 42 and accessed as needed. The application 100 may transmit reminders to a user of a stored reservation, for example by email or SMS. The user may cancel within a certain timeframe prior to their reservation. The application 100 may use location data received from a user or a vehicle 12 to determine if the vehicle is in or near the appropriate charging station 10 at the reserved time. If not, the application 100 may cancel the reservation or transmit an additional reminder or a reservation confirmation message to a user. If the user fails to respond to the messages or responds that they wish to cancel the reservation, the reservation is canceled and the charging station 10 is listed as vacant. Various penalties, including a cancellation fee may be applied to a user's account for missing a reservation.
As the user approaches the charging station 10, the position of the vehicle 12 may be detected by the charging station 10 and a parking sequence 122 may be initiated by the application 100 to assist the user with aligning the vehicles receiver 22 with the charging unit 20. Improper alignment can lead to less power transfer and inefficient charging. The presence and position of the vehicle 12 may be detected by the charging station 10 sensors 30, by positioning and location data received by the application 100, or by any combination thereof. In various exemplary embodiments, the application 100 is designed to communicate with the remote server 36, the charging station 10, and/or the vehicle 12 to send and receive information regarding positioning.
As best shown in
The charging stations 10 in the network may have an identical layout as to the position of the charging unit 20 and the receivers 22 of each vehicle 12 may be placed in a uniform position relative to, for example, the front of the car. In this way, the parking sequence 122 may perform a relatively uniform determination for all parking sequences 122. In alternative embodiments, however, the charging units 20 and/or the receivers 22 may have non-uniform placement. The charging unit 10 and application 100 may communicate, either directly or through the remote server 36 to assist in properly aligning the vehicle 12. The charging station 10 may be capable of recognizing the placement of each individual vehicle receiver 22, for example by a specific vehicle 12 or receiver 22 identifier that is transmitted to the charging station. The transmission may be through, a radio transmission, WiFi, or Bluetooth or through a form of inductance communication at a specific frequency between the receiver 22 and the charging unit 20. The charging station 10 may also supply charging unit 20 position data to the application 100, either directly or through the remote server 36. The application may compare this data to stored data representing the receiver position 22 to facilitate proper alignment. The data representing the receiver position 22 may be entered or selected by a user, or it may be transmitted by the receiver 22 or another component of the vehicle 12 to the application 100.
After a vehicle 12 is properly aligned with the charging unit 20, a charging method screen 130 may be selected or automatically displayed to the user. An example of a charging method screen 130 is depicted in
As shown in the example of
Regardless of the charging method selected, the system, for example the administrator system 40, may be capable of determining an approximate time when charging will be complete. When battery percentage is selected, the system may make this calculation on information received from the battery management system 25 and information related to the charging rate and efficiency. This calculation may be performed at specific intervals and updated as needed. The user may be provided with messages or alerts informing them of when their charging will be complete. In an exemplary embodiment, when approximately 10 minutes is remaining, a message may be sent to the user. When the user returns to their vehicle 12 they may select to terminate the charging and leave the GPZ. A receipt screen is shown after the charging is terminated, a copy of which may be sent to the user, for example by email. Information of the transaction may be sent to the remote server 36. If the user does not move their vehicle 12 within the set amount of time, the user may be charged a late fee. This encourages turn-over and assists in providing proper scheduling and information to additional users.
In various exemplary embodiments, the application 100 may provide additional communications to the user based on geo-location and system usage data. For example, user location, charging station 10 usage, and reserved charging station 10 location data may trigger various communications to the user. These communications may be displayed through the application 100 or push notifications that are sent to the user, for example by email or SMS message. The communication may transmit advertisements or coupons to a user.
Various exemplary embodiments are directed to a system which implements “Green Loading Zones” (GLZs) 136. The term “Green Loading Zones” (GLZs) is used herein simply as a non-limiting reference label for consistency of description and to facilitate understanding of exemplary implementations. GLZs 136 provide wireless charging and parking in public areas for an established rate to all registered vehicles. This allows commercial fleet operators to charge their vehicles while loading and unloading payloads, thus, streamlining deliveries and work schedules. GLZs 136 can address, for example, the problem of range limitation that commercial fleets face by strategically positioning and installing charging stations 10 at GLZs 136, loading facilities, and company-owned parking lots. GLZs 136 can provide commercial fleet operators the opportunity to optimize fleet logistics and make the adoption of electric trucks cost-effective, efficient, and practical. GLZs 136 may also enable secondary vehicle systems, such as climate control systems to move from gas or diesel power to electric.
GLZs 136 may be implemented by the application 100 and the remote server 36. A dedicated database 42 may compile and log information relating to the GLZs 136, for example scheduling and usage information. A company may schedule a delivery ahead of time and reserve a particular charging station 10. A company may also have a dedicated daily/weekly/monthly time window for utilizing a GLZ 136. Scheduling and reservation of certain GLZs 136 may be optimized to increase delivery efficiency, reducing not only emissions, but congestion and gridlock caused by multiple delivery trucks or other commercial vehicles attempting to occupy and utilize a limited space.
The foregoing detailed description of the certain exemplary embodiments has been provided for the purpose of explaining the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications as are suited to the particular use contemplated. This description is not necessarily intended to be exhaustive or to limit the invention to the precise embodiments disclosed. Any of the embodiments and/or elements disclosed herein may be combined with one another to form various additional embodiments not specifically disclosed. Accordingly, additional embodiments are possible and are intended to be encompassed within this specification and the scope of the appended claims. The specification describes specific examples to accomplish a more general goal that may be accomplished in another way.
Further, exemplary implementations of above-described exemplary embodiments may be recorded in computer-readable media including program instructions to implement various operations embodied by a computer. The media may also include, alone or in combination with the program instructions, data files, data structures, and the like. The media and program instructions may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD ROM disks and DVD; magneto-optical media such as optical disks; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory (ROM), random access memory (RAM), flash memory, and the like. The media may also be a transmission medium such as optical or metallic lines, wave guides, and so on, including a carrier wave transmitting signals specifying the program instructions, data structures, and so on. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter. The described hardware devices may be configured to act as one or more software modules in order to perform the operations of the above-described embodiments of the present invention.
Only those claims which use the words “means for” are to be interpreted under 35 U.S.C. 112, sixth paragraph.
This application is based on provisional application Ser. No. 61/614,604, filed Mar. 23, 2012, and provisional application Ser. No. 61/794,237, filed on Mar. 15, 2013, the disclosures of which are incorporated herein by reference and to which priority is claimed.
Number | Name | Date | Kind |
---|---|---|---|
3801022 | Cassey | Apr 1974 | A |
5264776 | Hulsey | Nov 1993 | A |
5311973 | Tseng et al. | May 1994 | A |
5323099 | Bruni et al. | Jun 1994 | A |
5327065 | Bruni et al. | Jul 1994 | A |
5461299 | Bruni | Oct 1995 | A |
5463303 | Hall et al. | Oct 1995 | A |
5483143 | Hall et al. | Jan 1996 | A |
5498948 | Bruni et al. | Mar 1996 | A |
5506489 | Abbott et al. | Apr 1996 | A |
5600222 | Hall et al. | Feb 1997 | A |
5606237 | Biasotti et al. | Feb 1997 | A |
5646500 | Wilson | Jul 1997 | A |
5654621 | Seelig | Aug 1997 | A |
5703462 | Woody et al. | Dec 1997 | A |
5831413 | Gould | Nov 1998 | A |
5850135 | Kuki et al. | Dec 1998 | A |
6157162 | Hayashi et al. | Dec 2000 | A |
6397990 | Brien et al. | Jun 2002 | B1 |
6879889 | Ross | Apr 2005 | B2 |
7741734 | Joannopoulos et al. | Jun 2010 | B2 |
7825543 | Karalis et al. | Nov 2010 | B2 |
7880337 | Farkas | Feb 2011 | B2 |
D636333 | Kulikowski | Apr 2011 | S |
8022576 | Joannopoulos et al. | Sep 2011 | B2 |
8035255 | Kurs et al. | Oct 2011 | B2 |
8054036 | Onishi et al. | Nov 2011 | B2 |
8072182 | Vasilantone | Dec 2011 | B2 |
8076800 | Joannopoulos et al. | Dec 2011 | B2 |
8076801 | Karalis et al. | Dec 2011 | B2 |
8084889 | Joannopoulos et al. | Dec 2011 | B2 |
8097983 | Karalis et al. | Jan 2012 | B2 |
8106539 | Schatz et al. | Jan 2012 | B2 |
8115448 | John | Feb 2012 | B2 |
8169185 | Partovi et al. | May 2012 | B2 |
8183827 | Lyon | May 2012 | B2 |
8222860 | Kamijo et al. | Jul 2012 | B2 |
8304935 | Karalis et al. | Nov 2012 | B2 |
8324759 | Karalis et al. | Dec 2012 | B2 |
8362651 | Hamam et al. | Jan 2013 | B2 |
8395282 | Joannopoulos et al. | Mar 2013 | B2 |
8395283 | Joannopoulos et al. | Mar 2013 | B2 |
8400017 | Kurs et al. | Mar 2013 | B2 |
8400018 | Joannopoulos et al. | Mar 2013 | B2 |
8400019 | Joannopoulos et al. | Mar 2013 | B2 |
8400020 | Joannopoulos et al. | Mar 2013 | B2 |
8400021 | Joannopoulos et al. | Mar 2013 | B2 |
8400022 | Joannopoulos et al. | Mar 2013 | B2 |
8400023 | Joannopoulos et al. | Mar 2013 | B2 |
8400024 | Joannopoulos et al. | Mar 2013 | B2 |
8410636 | Kurs et al. | Apr 2013 | B2 |
8441154 | Karalis et al. | May 2013 | B2 |
8461719 | Kesler et al. | Jun 2013 | B2 |
8461720 | Kurs et al. | Jun 2013 | B2 |
8461721 | Karalis et al. | Jun 2013 | B2 |
8461722 | Kurs et al. | Jun 2013 | B2 |
8463536 | Yamamoto | Jun 2013 | B2 |
8466583 | Karalis et al. | Jun 2013 | B2 |
8466654 | Cook et al. | Jun 2013 | B2 |
8466660 | Iizuka et al. | Jun 2013 | B2 |
8471410 | Karalis et al. | Jun 2013 | B2 |
8476788 | Karalis et al. | Jul 2013 | B2 |
8482158 | Kurs et al. | Jul 2013 | B2 |
8487480 | Kesler et al. | Jul 2013 | B1 |
8497601 | Hall et al. | Jul 2013 | B2 |
8513915 | Patel | Aug 2013 | B2 |
8517126 | Atarashi | Aug 2013 | B2 |
8525370 | Walley et al. | Sep 2013 | B2 |
8536830 | Holmes et al. | Sep 2013 | B2 |
D692010 | Verghese | Oct 2013 | S |
8552592 | Schatz et al. | Oct 2013 | B2 |
8561770 | Stoicoviciu | Oct 2013 | B2 |
8569914 | Karalis et al. | Oct 2013 | B2 |
8569993 | Wolfien | Oct 2013 | B2 |
8751077 | Kumagai et al. | Jun 2014 | B2 |
8907811 | Windstrup | Dec 2014 | B2 |
9446674 | Dimke et al. | Sep 2016 | B2 |
20010002788 | Koike | Jun 2001 | A1 |
20080101842 | Takahashi | May 2008 | A1 |
20080300660 | John | Dec 2008 | A1 |
20090249076 | Reed et al. | Oct 2009 | A1 |
20100017249 | Fincham | Jan 2010 | A1 |
20100094496 | Hershkovitz | Apr 2010 | A1 |
20100102640 | Joannopoulos et al. | Apr 2010 | A1 |
20100127575 | Joannopoulos et al. | May 2010 | A1 |
20100133918 | Joannopoulos et al. | Jun 2010 | A1 |
20100133919 | Joannopoulos et al. | Jun 2010 | A1 |
20100133920 | Joannopoulos et al. | Jun 2010 | A1 |
20100156346 | Takada et al. | Jun 2010 | A1 |
20100161216 | Yamamoto et al. | Jun 2010 | A1 |
20100171368 | Schatz et al. | Jul 2010 | A1 |
20100181845 | Fiorello et al. | Jul 2010 | A1 |
20100185353 | Barwick | Jul 2010 | A1 |
20100187911 | Joannopoulos et al. | Jul 2010 | A1 |
20100207458 | Joannopoulos et al. | Aug 2010 | A1 |
20100219694 | Kurs et al. | Sep 2010 | A1 |
20100231340 | Fiorello et al. | Sep 2010 | A1 |
20100237709 | Hall et al. | Sep 2010 | A1 |
20100259108 | Giler et al. | Oct 2010 | A1 |
20100259110 | Kurs et al. | Oct 2010 | A1 |
20100277121 | Hall et al. | Nov 2010 | A1 |
20100308939 | Kurs | Dec 2010 | A1 |
20110043049 | Karalis et al. | Feb 2011 | A1 |
20110074218 | Karalis et al. | Mar 2011 | A1 |
20110074346 | Hall et al. | Mar 2011 | A1 |
20110074347 | Karalis et al. | Mar 2011 | A1 |
20110078092 | Kim | Mar 2011 | A1 |
20110089895 | Karalis et al. | Apr 2011 | A1 |
20110095618 | Schatz et al. | Apr 2011 | A1 |
20110121920 | Kurs et al. | May 2011 | A1 |
20110156494 | Mashinsky | Jun 2011 | A1 |
20110193416 | Campanella et al. | Aug 2011 | A1 |
20110193419 | Karalis et al. | Aug 2011 | A1 |
20110204845 | Paparo | Aug 2011 | A1 |
20110221387 | Steigerwald | Sep 2011 | A1 |
20110224900 | Hiruta et al. | Sep 2011 | A1 |
20110254503 | Widmer | Oct 2011 | A1 |
20110285349 | Widmer | Nov 2011 | A1 |
20120007441 | John | Jan 2012 | A1 |
20120032522 | Schatz et al. | Feb 2012 | A1 |
20120062345 | Kurs et al. | Mar 2012 | A1 |
20120068549 | Karalis et al. | Mar 2012 | A1 |
20120086284 | Campanella et al. | Apr 2012 | A1 |
20120086867 | Kesler et al. | Apr 2012 | A1 |
20120091794 | Campanella et al. | Apr 2012 | A1 |
20120091795 | Fiorello et al. | Apr 2012 | A1 |
20120091796 | Kesler et al. | Apr 2012 | A1 |
20120091797 | Kesler et al. | Apr 2012 | A1 |
20120091819 | Kulikowski et al. | Apr 2012 | A1 |
20120091820 | Campanella et al. | Apr 2012 | A1 |
20120091949 | Campanella et al. | Apr 2012 | A1 |
20120091950 | Campanella et al. | Apr 2012 | A1 |
20120098350 | Campanella et al. | Apr 2012 | A1 |
20120112531 | Kesler et al. | May 2012 | A1 |
20120112532 | Kesler et al. | May 2012 | A1 |
20120112534 | Kesler et al. | May 2012 | A1 |
20120112535 | Karalis et al. | May 2012 | A1 |
20120112536 | Karalis et al. | May 2012 | A1 |
20120112538 | Kesler et al. | May 2012 | A1 |
20120112691 | Kurs et al. | May 2012 | A1 |
20120119569 | Karalis et al. | May 2012 | A1 |
20120119575 | Kurs et al. | May 2012 | A1 |
20120119576 | Kesler et al. | May 2012 | A1 |
20120119698 | Karalis et al. | May 2012 | A1 |
20120139355 | Ganem et al. | Jun 2012 | A1 |
20120153733 | Schatz et al. | Jun 2012 | A1 |
20120153738 | Karalis et al. | Jun 2012 | A1 |
20120153893 | Schatz et al. | Jun 2012 | A1 |
20120184338 | Kesler et al. | Jul 2012 | A1 |
20120203410 | Wechlin et al. | Aug 2012 | A1 |
20120206096 | John | Aug 2012 | A1 |
20120228960 | Karalis et al. | Sep 2012 | A1 |
20120235500 | Ganem et al. | Sep 2012 | A1 |
20120235501 | Kesler et al. | Sep 2012 | A1 |
20120235502 | Kesler et al. | Sep 2012 | A1 |
20120235503 | Kesler et al. | Sep 2012 | A1 |
20120235505 | Schatz et al. | Sep 2012 | A1 |
20120235633 | Kesler et al. | Sep 2012 | A1 |
20120235634 | Hall et al. | Sep 2012 | A1 |
20120235636 | Partovi | Sep 2012 | A1 |
20120239117 | Kesler et al. | Sep 2012 | A1 |
20120248888 | Kesler et al. | Oct 2012 | A1 |
20120256494 | Kesler et al. | Oct 2012 | A1 |
20120313449 | Kurs et al. | Dec 2012 | A1 |
20120313742 | Kurs et al. | Dec 2012 | A1 |
20130007949 | Kurs et al. | Jan 2013 | A1 |
20130020878 | Karalis et al. | Jan 2013 | A1 |
20130024059 | Miller et al. | Jan 2013 | A1 |
20130033118 | Karalis et al. | Feb 2013 | A1 |
20130033224 | Raedy | Feb 2013 | A1 |
20130033228 | Raedy | Feb 2013 | A1 |
20130038276 | Raedy | Feb 2013 | A1 |
20130038277 | Chan et al. | Feb 2013 | A1 |
20130038402 | Karalis et al. | Feb 2013 | A1 |
20130057364 | Kesler et al. | Mar 2013 | A1 |
20130062966 | Verghese et al. | Mar 2013 | A1 |
20130069441 | Verghese et al. | Mar 2013 | A1 |
20130069753 | Kurs et al. | Mar 2013 | A1 |
20130088195 | Yoon et al. | Apr 2013 | A1 |
20130099587 | Lou et al. | Apr 2013 | A1 |
20130154389 | Kurs et al. | Jun 2013 | A1 |
20130159956 | Verghese et al. | Jun 2013 | A1 |
20130181541 | Karalis et al. | Jul 2013 | A1 |
20130193913 | Takada et al. | Aug 2013 | A1 |
20130234532 | Fells et al. | Sep 2013 | A1 |
20130249479 | Partovi | Sep 2013 | A1 |
20130265004 | Iizuka et al. | Oct 2013 | A1 |
20130278073 | Kurs et al. | Oct 2013 | A1 |
20130278074 | Kurs et al. | Oct 2013 | A1 |
20130278210 | Cook et al. | Oct 2013 | A1 |
20130285604 | Partovi | Oct 2013 | A1 |
20130300364 | Baier et al. | Nov 2013 | A1 |
20140021908 | McCool | Jan 2014 | A1 |
20140194092 | Wanstedt et al. | Jul 2014 | A1 |
20150015419 | Halker et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
2011049352 | Apr 2011 | WO |
Entry |
---|
Chargepoint America, National Grid Further Expands ChargePoint Network Driving EV Adoption Thoughout Massachusetts, Press Release, Feb. 28, 2012 (retrieved on Jun. 6, 2013). http://chargepointamerica.com/blog/. |
Ford Motor Company, New MyFord mobile app keeps focus electric owner engaged and in control of electric car experience. Press Release Jun. 5, 2011. (retrieved Jun. 6, 2013). http://ophelia.sdsu.edu:8080/ford/06-05-2011/news-center/news/press-releases/press-releases-detail/pr-new-myford-mobile-app-keeps-focus-33763.html p. 1. |
PCT/US2013/033720, “International Search Report and Written Opinion” date, Jul. 1, 2013, 3 pages. |
Ridden, Evatran unveils wireless charging solution for electric vechicles, Aug. 1, 2010 (retrieved on Jun. 6, 2013). http://www.gizmag.corn/evatran-plugless-power-induction-electric-vehicle-charging/15904/. |
Number | Date | Country | |
---|---|---|---|
20140021908 A1 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
61614604 | Mar 2012 | US | |
61794237 | Mar 2013 | US |