Patent Description:
Electrically powered vehicles, including electric vehicles and plug-in hybrid electric vehicles, include electric motors powered by energy storage devices, such as batteries. Because an energy storage device is depleted of energy as the motor is operated, the operator of the vehicle must recharge the energy storage device prior to using the vehicle again.

At least some known vehicle charging stations are provided for public use. Such charging stations are designed to charge the energy storage device when connected to the vehicle. The public use charging stations may require a user to enter information prior to charging the vehicle. In such instances, after a user drives up to the charging station, they are required to get out of their vehicle and manually enter information to the charging station. Information may include, for example, credit card information necessary to pay from energy transferred from the charging station to the vehicle. As such, known charging stations generally require physical interaction with a charging station prior to enter charging and/or payment information. Known charging stations also often require maintaining the vehicle at the charging station for extended periods of time, while the vehicle charges.

<CIT> describes a charging station for charging plug-in vehicles with a user interface to control the charging station, claim <NUM>. The user receives a request to charge the vehicle and may accept or decline, whereas the process ends also with a time run out.

<CIT> refers to systems and methods for charging electric vehicles and for quantitative and qualitative load balancing of electrical demand.

<CIT> describes a method for protecting against overcurrent conditions and ground fault conditions in a networked charging station.

<CIT> describes an electric power management apparatus for vehicles which manages the charging state of an electric power device.

<CIT> refers to a control apparatus for controlling a vehicle or premises.

In one aspect, a vehicle charging station according to claim <NUM> is provided.

In another aspect, a method according to claim <NUM> for use in charging an electrically powered vehicle for use in charging an electrically powered vehicle is provided.

In yet another aspect, one or more non-transitory computer-readable storage media having computer-executable instructions thereon according to claim <NUM> is provided.

Other features and aspects are defined in the appended dependent claims.

The examples described herein may be better understood by referring to the following description in conjunction with the accompanying drawings.

The examples described herein relate to communication of information to and/or from an electrically power vehicle and/or a vehicle charging station. More specifically, in some examples, a user profile is communicated to a vehicle charging station. In some examples, the use of an in-vehicle user interface communicate with a vehicle charging station and/or another device is provided. Some examples are related to transmitting and receiving one or more messages to and/or from a vehicle charging station from and/or to a user.

In numerous examples, the term "electrically powered vehicle" is used to refer to a vehicle that includes one or more electric motors that are used for propulsion. Energy used to propel electrically powered vehicles may come from various energy storage devices, such as, but not limited to, an on-board rechargeable battery, a capacitor, and/or an on-board fuel cell. In one example, the electrically powered vehicle is a hybrid electric vehicle, which may include both an electric motor and a combustion engine. In another example, an electrically powered vehicle is an electric vehicle, which may include only an electric motor for propulsion. Electrically powered vehicles may capture and store energy generated, for example, by braking. Moreover, some electrically powered vehicles are capable of recharging the energy storage device from a power receptacle, such as a power outlet. Accordingly, the term "electrically powered vehicle" as used herein may refer to any vehicle that includes an energy storage device to which electrical energy may be delivered, for example, via a power grid.

Example technical features of the methods, systems, and apparatus described herein may include at least one of (a) detecting a vehicle charging station, (b) retrieving a user profile from a memory device in the electrically powered vehicle, and (c) communicating the user profile to the vehicle charging station. The user profile may include, without limitation, billing information, contact information, an alert, and/or a user preference, etc. Another example technical feature of the methods, systems, and apparatus described herein includes at least one of (a) receiving, at an in-vehicle user interface, at least one user input and (b) communicating, via a vehicle controller, a charging parameter to a vehicle charging station in response to the at least one user input.

Other example technical features of the methods, systems, and apparatus described herein may include at least one of (a) controlling, at a charging device, a charging process including energy transfer between a power source and an electrically powered vehicle, (b) transmitting, via at least one network, a first electronic message to a user, and (c) receiving, via the at least one network, a second electronic message. The first electronic message includes at least one condition related to at least one of the charging process and the electrically power vehicle. The second electronic message includes a user command related to the at least one condition.

<FIG> illustrates an example computing device <NUM>. In the example, computing device <NUM> includes a memory device <NUM> and a processor <NUM> coupled to memory device <NUM>. In some examples, executable instructions are stored in memory device <NUM> and executed by processor <NUM>. Computing device <NUM> is configurable to perform one or more operations described herein by programming and/or configuring processor <NUM>. For example, processor <NUM> may be programmed by encoding an operation as one or more executable instructions and providing the executable instructions in memory device <NUM>.

Memory device <NUM> is one or more devices operable to enable information such as executable instructions and/or other data to be stored and/or retrieved. Memory device <NUM> may include one or more computer readable media, such as, without limitation, hard disk storage, optical drive/disk storage, removable disk storage, flash memory, non-volatile memory, ROM, EEPROM, random access memory (RAM), etc. Memory device <NUM> may be configured to store, without limitation, computer-executable instructions, transmitter identifiers, account identifiers, payment account information, and/or any other type of data. Memory device <NUM> may be incorporated in and/or separate from processor <NUM>.

Processor <NUM> may include one or more processing units (e.g., in a multi-core configuration). The term processor, as used herein, refers to central processing units, microprocessors, microcontrollers, reduced instruction set circuits (RISC), application specific integrated circuits (ASIC), logic circuits, and any other circuit or processor capable of executing instructions to perform functions described herein.

Computing device <NUM> includes a communication interface <NUM> coupled to processor <NUM>. Communication interface <NUM> is configured to be coupled in communication with one or more other devices, such as another computing device <NUM>, a network, etc. Communication interface <NUM> may include, without limitation, a serial communication adapter, a wired network adapter, a wireless network adapter, a mobile telecommunications adapter, a radio frequency (RF) receiver, a radio frequency identification (RFID) reader, a keyless entry receiver, and/or any other device capable of communicating with one or more other devices. Communication interface <NUM> may transmit information to and/or receive information from one or more devices. In one example, a communication interface <NUM> of one computing device <NUM> may transmit a user profile to a communication interface <NUM> of another computing device <NUM>.

In some examples, computing device <NUM> may be used in combination with a user interface <NUM> to interact with user <NUM>, such as an operator of a vehicle. As shown in <FIG>, user interface <NUM> is separate from computing device <NUM>. User interface <NUM> may communicate with processor <NUM> directly or indirectly through one or more communication interfaces <NUM>. In at least one example, user interface <NUM> may be completely or at least partially included within computing device <NUM>.

User interface <NUM> may be configured to display information to a user <NUM>. In the example, user interface <NUM> includes a display device <NUM>, such as a cathode ray tube (CRT), a liquid crystal display (LCD), an organic LED (OLED) display, an "electronic ink" display, and/or other device suitable to display information. In some examples, user interface <NUM> includes an in-vehicle user interface, such as a display device of a navigation system and/or a media system. As used herein, "in-vehicle" user interface includes an interface coupled, mounted and/or secured to a vehicle (e.g., a vehicle dashboard) and accessible to at least one user <NUM> while present within the vehicle. Additionally, or alternatively, user interface <NUM> may include an audio output device (e.g., an audio adapter and/or a speaker, etc.).

User interface <NUM> may include an input device <NUM> to receive one or more inputs from user <NUM>. Input device <NUM> may include, without limitation, a button, a knob, a keypad, a pointing device, a mouse, a touch sensitive panel (e.g., a touch pad or a touchscreen), a gyroscope, a position detector, and/or an audio input (e.g., a microphone). In various examples, user interface <NUM> may include a single component, such as a touchscreen display, incorporating both display device <NUM> and input device <NUM>.

As described herein, computing device <NUM> may include one or more devices, servers, and/or controllers of the systems and/or methods described herein.

<FIG> illustrates an example system <NUM> that may be used to charge an electrically powered vehicle <NUM>. In the example, system <NUM> includes a vehicle charging station <NUM> coupled to vehicle <NUM>. Moreover, in the example, charging station <NUM> includes a charging device <NUM> and a power source <NUM> that is coupled to charging device <NUM>. Power source <NUM> may include a power grid of an electric utility company, a generator, a battery, an inductor, and/or any other device or system capable of providing electricity to charging device <NUM>.

Vehicle <NUM> includes at least one energy storage device <NUM>, such as a battery and/or a capacitor, coupled to a motor <NUM>. In the example, vehicle <NUM> includes vehicle controller <NUM> and in-vehicle user interface <NUM> coupled to vehicle controller <NUM>. While vehicle controller <NUM> is illustrated as being a single component and is described with reference to multiple functions herein, it should be appreciated that vehicle controller <NUM> may include multiple, separate controllers disposed throughout vehicle <NUM> in other examples. As such, each of the multiple vehicle controllers may be associated with one or more of the functions described herein.

In the example system <NUM>, a charging conduit <NUM> is releasably coupled between charging station <NUM> and energy storage device <NUM> and/or to vehicle controller <NUM>. Charging conduit <NUM> may permit energy transfer from power source <NUM> to vehicle <NUM>. Alternatively, a wireless conduit may permit energy transfer from power source <NUM> to vehicle <NUM>, as shown, for example, in <FIG>. Regardless of the type of conduit employed, energy is generally transferred during a charging process from power source <NUM> to energy storage device <NUM> to charge energy storage device <NUM>.

Referring again to <FIG>, charging conduit <NUM> may include at least one conductor for supplying electrical energy to energy storage device <NUM> and/or to any other component within vehicle <NUM>, and at least one conductor for transmitting information to, and/or receiving information from, vehicle controller <NUM> and/or any other component within vehicle <NUM>. Charging conduit <NUM> may couple to vehicle <NUM> at a charging receptacle <NUM>. When charging conduit <NUM> includes at least one power conductor (not shown) and at least one data conductor (not shown), charging receptacle <NUM> may include an integrated power-data receptacle to connect to both the power and data conductors.

Additionally, or alternatively, charging conduit <NUM> may include a cable with one or more conductors for supplying electricity to vehicle <NUM>, without a separate and dedicated conductor for communicating information to/from vehicle <NUM>. In such an example, information may be embedded in one or more power signals transmitted through charging conduit <NUM> between vehicle charging station <NUM> and vehicle <NUM>. In still other examples, data may be communicated between vehicle <NUM> and/or charging station <NUM> through a wireless connection. Charging receptacle <NUM> may be configured differently in various examples to provide appropriate connections between charging station <NUM> and vehicle <NUM>.

As shown, charging device <NUM> is coupled to a server <NUM> through a network <NUM>. Server <NUM> may communicate with charging device <NUM>, for example, to acknowledge/confirm an aspect of the user profile, to communicate a user response to an electronic message, and/or to perform any other function that enables system <NUM> to function as described herein. Network <NUM> may include, without limitation, the Internet, a local area network (LAN), a wide area network (WAN), a wireless LAN (WLAN), a mesh network, a virtual private network (VPN), a cellular network, and/or any other network that enables system <NUM> to function as described herein. In various examples, one or more of charging device <NUM>, vehicle controller <NUM>, and server <NUM> are connected to network <NUM>.

Further, one or more of charging device <NUM>, vehicle controller <NUM>, and/or server <NUM> may be instances of computing device <NUM>. It should be appreciated that charging device <NUM>, vehicle controller <NUM>, and/or server <NUM> may include more or less components than illustrated in the computing device <NUM> in other examples.

Methods and systems described herein may include communicating information to and/or from an electrically powered vehicle, a vehicle charging station, and/or other devices. Communicating information may generate efficiency and/or increase safety and security for a user and/or the user's information, while providing additional functionality. In various examples, information may be communicated prior to initiating a charging process, during the charging process, and/or after the charging process.

In the example, controller <NUM> of vehicle <NUM> includes memory device <NUM> and processor <NUM>. Memory device <NUM> stores at least one user profile. The user profile may include, without limitation, billing information, contact information for user <NUM>, an alert, a user preference, a vehicle identification, a vehicle manufacturer, a vehicle model, an AC profile, a limitation of energy storage device <NUM>, a type of energy storage device <NUM>, and/or other information related to vehicle <NUM>, charging station <NUM>, and/or a charging process, etc..

A user preference may include a charging time, a dollar amount, a price per unit power threshold, a voltage level, a current level, a rate threshold, a process for mitigating charging errors, a process for presenting/handling alerts, a request for a charge-time remaining indicator, a request to process/ignore charging station <NUM> diagnostics, and/or other information or preferences associated with a user, etc. In at least one example, a user preference may be based on a location. For example, a user preference may request sufficient energy transfer to permit a vehicle <NUM> to return to a user's residence, which may be less than a complete charge of energy storage device <NUM>. In such an example, controller <NUM> may communicate with a navigation system (including in-vehicle user interface <NUM>) to determine a location of vehicle <NUM>, a location of the user's residence, and estimate energy required to return to the user's residence.

Prior to communicating the user profile to charging station <NUM>, vehicle <NUM> may detect charging station <NUM>. In the example, detection may be initiated by either vehicle <NUM> or charging station <NUM>, but preferably results in each of vehicle <NUM> and charging station <NUM> detecting the other.

In the example, vehicle <NUM> and/or charging station <NUM> may be detected by one or more sensors. In one example, charging receptacle <NUM> may include a sensor to detect the presence of charging conduit <NUM> inserted therein. The sensor may include, for example, a switch. The sensor permits vehicle <NUM> and/or vehicle controller <NUM> to detect charging conduit <NUM>, thereby detecting charging station <NUM>. Conversely, a sensor may be associated with charging conduit <NUM>, such that charging station <NUM> detects vehicle <NUM> when charging conduit <NUM> is inserted into charging receptacle <NUM>. In another example, charging station <NUM> may includes a weight sensor to detect the presence of vehicle <NUM> over charging station <NUM>.

Additionally, or alternatively, charging station <NUM> may utilize communication in order to detect vehicle <NUM>, or vice-versa. Specifically, for example, charging device <NUM> may initiate communication by transmitting an identification signal to its generally vicinity via communication interface <NUM>. When a vehicle <NUM> pulls up to charging station <NUM>, vehicle <NUM> may receive the identification signal and generate a response signal through communication interface <NUM> to establish communication with charging station <NUM>. Consequently, vehicle <NUM> detects charging station <NUM>, and charging station <NUM> detects vehicle <NUM>. It should be appreciated that an identification signal may be transmitted by a vehicle and received by a charging station in other examples.

In the example, the identification signal may be transmitted consistently from vehicle <NUM> or charging station <NUM>. Additionally, or alternatively, the identification signal may be transmitted in response to a user input. For example, user <NUM> may pull up to charging station <NUM> and provide an input to in-vehicle user interface <NUM>, causing processor <NUM>, in combination with communication interface <NUM>, to transmit an identification signal. Charging station <NUM>, in turn, receives the identification signal and responds. As such, each of vehicle <NUM> and charging station <NUM> has detected the other. It should be appreciated that various signals in various orders may be communication between, vehicle controller <NUM>, vehicle <NUM>, charging station <NUM> and/or charging device <NUM> to permit detection of one or both of vehicle <NUM> and charging station <NUM>.

Once charging station <NUM> is detected, processor <NUM> of controller <NUM> retrieves the user profile from memory device <NUM> and communicates the user profile to charging station <NUM>. In the example, processor <NUM> automatically retrieves the user profile from memory device <NUM> and automatically communicates the user profile to charging station <NUM>. In other examples, a user input to input device <NUM> may be required to retrieve and/or communicate the user profile. In at least one example, a user input may be required to selected one of a plurality of user profiles stored in memory device <NUM>.

Once charging station <NUM> receives the user profile, charging station <NUM> may enable energy transfer from the power source <NUM> to vehicle <NUM> at least partially based on the user profile. Accordingly, at least a portion of information required by charging station <NUM> to initiate a charging process is communicated to charging station <NUM>, without user <NUM> manually entering the content of the user profile. In this manner, communicating the user profile to charging station <NUM> may provide increased safety, security and efficiency over known methods of entering information to a charging station. Specifically, for example, billing information is not entered to charging station <NUM> in plain view of others. Additionally, or alternatively, communicating the user profile from vehicle controller <NUM> may provide increased safety, security and efficiency over known methods, because a payment device (e.g., a credit card, debit card, key-chain radio frequency identification (RFID) device, a mobile telephone, or other device linked to a payment account) is not publically handled by user <NUM>, such that it may become lost. Moreover, the user profile, including billing/contact information, is passed electronically so that user profile is embedded in a communication between vehicle controller <NUM> and charging station <NUM> and outside the plain view of others.

Apart from billing and contact information, the user profile may include other information, such as one or more user preferences. In the example, for example, the user profile may include a charging time. When user <NUM> pulls up to charging station <NUM>, charging station <NUM> may charge vehicle <NUM> according to the charging time defined in the user profile without one or more inputs from user <NUM>.

Similarly, the user profile may include a preferred notification when an alert is generated, so that user <NUM> is notified in a particular manner if, for example, a charging error occurs. In another example, the user profile may include information related to a charging rate threshold (dollar per watt), such that charging station automatically initiates a charging processes with the current rate of energy is below the rate threshold. Further, as the number and variety of electrically powered vehicles grows, a number of variables necessary to properly/safely charge vehicle <NUM> may also increase. For example, one type of vehicle <NUM> may require 240VAC to charge, while another type of vehicle <NUM> may require 480VAC to charge. The user profile may be used in various examples to provide any and/or all information to charging station <NUM> to facilitate charging, thereby potentially obviating a user's need to directly interact with the charging station <NUM>.

In the example, charging device <NUM> may evaluate the user profile prior to initiating an energy transfer to verify information and/or confirm if additional information is needed. For example, charging device <NUM> may communicate through network <NUM> to verify and/or authorize billing information prior to permitting energy transfer to vehicle <NUM>. In another example, charging device <NUM> may access one or more networks to verify information and/or provide further functionality during a charging process. For example, the content of a user profile may provide a basis to offer one or more advertisements to user <NUM> before, during or after a charging process.

Additionally, or alternatively, a user profile may include only a portion of the information necessary to initiate a charging process. For example, a user profile may include billing information, contact information, and an AC profile, but not include a charge time. In this manner, a user profile may supply information routinely entered by a user, but does not include other information that a user may want to adjust for each charging process. Information not included in the user profile may be provided by a user to charging station <NUM>, for example, through in-vehicle user interface <NUM>, consistent with the methods described herein.

The user profile may be defined by user <NUM> in several different ways. In one example, the user profile may be defined by use of display device <NUM> and input device <NUM> of in-vehicle user interface <NUM>. Vehicle controller <NUM> may display multiple messages to user <NUM> through display device <NUM> to elicit one or more inputs from user <NUM> to input device <NUM> to define the user profile. For example, user <NUM> may be prompted at display device <NUM> to enter a preferred charging time. In response to the prompt, user <NUM> may enter an input to inputs device <NUM> to enter or select about <NUM> minutes, about <NUM> hours, about <NUM> hours, or another suitable time, etc. Once defined, the user profile is stored in memory device <NUM> of vehicle controller <NUM> for communication to charging station <NUM>. In several examples, the user profile may be defined through another interface to vehicle controller <NUM>. For example, a user communication device, such as a smartphone or personal computer, may communicate, via network <NUM>, with communication interface <NUM> of vehicle controller <NUM> to define the user profile. It should be appreciated that a user profile may be defined by entering a new user profile and/or editing an existing user profile. Further, multiple user profiles may be created and/or edited. Specifically, for example, multiple user profiles may include, without limitation, a short charge profile, medium charge profile, long charge profile, top off profile, etc..

In the example, vehicle <NUM> includes in-vehicle user interface <NUM> and vehicle controller <NUM> coupled in communication with in-vehicle user interface <NUM>. In-vehicle user interface <NUM> includes at least one input device <NUM> configured to receive an input from user <NUM>. Vehicle controller <NUM> is configured to receive a user input from in-vehicle user interface <NUM> and communicate a charging parameter to vehicle charging station <NUM> in response to the user input.

Charging parameters may include any parameters to initiate, alter and/or terminate a charging process. In the example a charging parameter may include, without limitation, an instruction related to a charging process, a selection of a charging process option, billing information, contact information, an alert, a user preference, a vehicle model, an AC profile, a limitation of energy storage device <NUM>, a type of energy storage device <NUM>, and/or any other information associated with the charging process, vehicle <NUM>, charging station <NUM> and/or user <NUM>.

In the example, user <NUM> may be able to communicate with charging station <NUM> from within vehicle <NUM>. As such, user <NUM> is able to communicate with charging station <NUM> without exiting vehicle <NUM>, thereby providing for the safety, security and/or convenience of user <NUM>. Moreover, communicating billing information, for example, to charging station <NUM> from within vehicle <NUM> may provide additional privacy and security, as compared to entering such information outside vehicle <NUM> in plain view of others.

Further, in several examples, use of in-vehicle user interface <NUM> may permit additional functionality of vehicle <NUM>, without the addition of display and/or input devices. More specifically, in the example, in-vehicle user interface <NUM> may be included in a system of vehicle <NUM> intended to perform at least one other function, such as navigation, entertainment, etc. For example, in-vehicle user interface <NUM> may be incorporated with an audio system, a visual system, a navigation system, a media system and/or any other system within vehicle <NUM>. In one example, in-vehicle user interface <NUM> includes a touchscreen display (e.g., display device <NUM> and input device <NUM>) of a navigation system. A navigation system may include any system suitable for providing location and/or or direction information. A media system may include any system suitable to provide radio, CD, MP3, video, DVD, gaming, telecommunications and/or other media functionality.

In several examples, in-vehicle user interface <NUM> may include display device <NUM> and input device <NUM>. Input device <NUM> is provided to receive one or more inputs from user <NUM>. Display device <NUM> may be utilized to solicit inputs from user <NUM> and/or display one or more messages from charging station <NUM>. In one example, charging station <NUM> may transmit a message to vehicle <NUM> requesting a charging time. In turn, display device <NUM> displays a request for a charging time to user <NUM>. User <NUM> may provide an input to input device <NUM> entering or selecting a charging time. Vehicle controller <NUM>, in turn, transmits a charging parameter (e.g., the charging time) to charging station <NUM>. In another example, a user profile may contain only a portion of information needed to initiate a charging process for vehicle <NUM>. After charging station <NUM> receives the user profile, charging station <NUM> may transmit a message requesting information not included in the user profile. In turn, a request may be displayed to user <NUM> at display device <NUM>, and user <NUM> may then select or enter, via input device <NUM>, information requested by charging station <NUM>. Vehicle controller <NUM> receives the one or more user inputs and communicates at least one charging parameter, based on the user inputs, to provide the information requested by charging station <NUM>.

It should be appreciated that in one or more examples, a user input to in-vehicle user interface <NUM> may be in response to a message originating from a device other than charging station <NUM>.

In the example, communication between charging station <NUM> and in-vehicle user interface <NUM> may be controlled by vehicle controller <NUM>. In such examples, vehicle controller <NUM> may be configured to transmit and/or receive messages to and/or from in-vehicle user interface <NUM> or other components or vehicle <NUM> according to one or more formats and/or protocols. In the example, vehicle <NUM> includes a packet-based, wired connection between vehicle controller <NUM> and in-vehicle user interface <NUM>. In-vehicle user interface <NUM> may include, for example, a vehicle audio system. As such, vehicle controller <NUM> may be configured to receive and/or transmit message according to a radio data system (RDS) format to permit vehicle controller <NUM> to transmit/receive formatted messages to/from the vehicle audio system. Additionally, or alternatively, vehicle controller <NUM> may be configured to transmit and/or receive messages to and/or from charging station <NUM> according to one or more formats and/or protocols. For example, vehicle controller <NUM> may be configured to transmit packet-based messages to charging station <NUM> through charging conduit <NUM>.

In the example, the functionality of charging station <NUM> may be affected when vehicle <NUM> is coupled to charging station <NUM>. For example, a display device and/or an input device of charging station <NUM> may be disabled when charging station <NUM> is connected in communication with vehicle <NUM>. Disabling the display device and/or input device of charging station <NUM> may prevent input of information from multiple sources and/or display of user information at charging station <NUM>. In alternative examples, one or both of a display device and an input device of charging station <NUM> may be enabled, when charging station <NUM> is coupled in communication with vehicle <NUM>.

<FIG> illustrates system <NUM> according to another example of the present disclosure. System <NUM> includes an electrically powered vehicle <NUM> and a vehicle charging station <NUM>. Charging station <NUM> includes a charging device <NUM> and a power source <NUM> coupled to charging device <NUM>. Charging device <NUM> controls energy transfer from power source <NUM> to vehicle <NUM>. In this example, a magnetic/electric field <NUM> is radiated from charging station <NUM> to transfer energy to vehicle <NUM>, and more specifically an energy storage device <NUM> included in vehicle <NUM>. Contrary to the example of <FIG>, including charging conduit <NUM>, magnetic/electric field <NUM> permits wireless transfer of energy between charging station <NUM> and vehicle <NUM>. It should be appreciated that wired energy transfer or wireless energy transfer may be used alone, or in combination, in one or more other examples.

In addition to energy storage device <NUM>, vehicle <NUM> includes a motor <NUM>, a vehicle controller <NUM>, and an in-vehicle user interface <NUM> coupled to vehicle controller <NUM>. In the example, vehicle controller <NUM> is coupled to network <NUM> through communication interface <NUM>. As shown, communication interface <NUM> permits wireless communication between vehicle <NUM> and charging station <NUM>, via network <NUM>. As indicated above, network <NUM> may include, without limitation, the Internet, a local area network (LAN), a wide area network (WAN), a wireless LAN (WLAN), a mesh network, a virtual private network (VPN), a cellular network, and/or any other network that enables system <NUM> to function as described herein.

In the example, because energy transfer and communication between charging station <NUM> and vehicle <NUM> are wireless, a user <NUM> may initiate and complete a charging process, without exiting vehicle <NUM> to attached a charging conduit or enter information to charging station <NUM>. By permitting user <NUM> to remain in the vehicle during a charging process, system <NUM> provides increased security, safety and/or convenience to user <NUM> over know methods and systems for charging an electrically powered vehicle. It should be appreciated that in other examples, such as illustrated in <FIG>, charging conduit <NUM> may be automatically connected to vehicle <NUM> prior to a charging process, such that even when a physical connection for energy transfer is present, user <NUM> may complete a charging processes without exiting vehicle <NUM>.

In the example, charging station <NUM> includes power source <NUM> and charging device <NUM> for controlling energy transfer from power source <NUM> to vehicle <NUM>. Charging device <NUM> is configured to transmit, via network <NUM>, a first electronic message to user <NUM> and receive, via network <NUM>, a second electronic message from user <NUM>. The first electronic message including a condition related to at least one of the charging process and vehicle <NUM>. The second electronic message including a user command related to the condition.

By transmitting the electronic message to user <NUM>, charging device <NUM> is able to promptly notify user <NUM> of one or more conditions. In the example, vehicle controller <NUM> may be coupled to an on-board computer of vehicle <NUM> to access information related to various sensors, such as tire pressure, window state, etc., and/or an alarm system of vehicle <NUM> to receive alarm indication. Accordingly, conditions may include, without limitation, a status of a charging process, an amount of energy transferred, a status, a charging error, or other information related to the charging process. Additionally, or alternatively, the condition may include, without limitation the state of a window (i.e., open or closed), a tire pressure, oil change indicator, an unauthorized access (e.g., a break-in), a temperature, etc. The prompt notification of any of the conditions may permit user <NUM> to more quickly respond to the condition, which may increase efficiency and/or security while vehicle <NUM> is charging.

In one example, a condition may include a charging error, and the first electronic message may indicate the charging error to user <NUM>. The first message may also indicate that the charging process has been suspended. If the error occurs after only <NUM> minutes into a two-hour charging process, for example, user <NUM> may not have realized the charging error until returning to vehicle <NUM> after a couple hours. By notifying user <NUM> of the error promptly, user <NUM> may address the error and re-initiate the charging process, without the loss of substantial charging time. In the example, the user command of the second message may be sufficient to mitigate the charging error and re-imitate charging of vehicle <NUM>. For example, a user command may accept a longer charge time, a different voltage or a partial charge in order to resume a charging process.

In another example, user <NUM> may be notified via the first electronic message that one or more windows of vehicle <NUM> are open during inclement weather. User <NUM> may be able to promptly return to vehicle <NUM> to adjust one or more windows as dictated by weather. Alternatively, the user command of the second message may direct vehicle controller <NUM> to adjust (directly or through a different computing device) the state of the windows according to the weather.

In yet another example, a charging process may cease based on an energy rate (dollar per watt) that exceeds a user preference. When the charging process ceases, charging device <NUM> and/or vehicle controller <NUM> may transmit the first electronic message to user <NUM> indicating the current energy rate. In response, user <NUM> may transmit the second message including a command to re-initiate charging of vehicle <NUM>, notwithstanding the energy rater exceeding the user preference. It should be appreciated that various other alterations and/or changes may be implemented by a user via a user command in the second electronic message. In at least one example, user <NUM> may initiate a message to charging device <NUM> and/or controller <NUM>, without a prior electronic message from charging device <NUM>.

The first and second electronic messages may include a SMS message, a voicemail message, an email message or other electronic message suitable for transmission over network <NUM>, etc. The electronic messages may be received/transmitted by user <NUM> at a communication device <NUM>, such as, without limitation, a cellular phone, a pager, a smartphone, a personal computer, a laptop, a tablet, a workstation, a security system, or any other device suitable to receive and/or send an electronic message.

As explained above, charging station <NUM> may communicate with vehicle <NUM> in response to the second message. Alternatively, charging station <NUM> may communicate to a third party in response to the second message. For example, when a condition indicates an unauthorized access of vehicle <NUM> or charging station <NUM>, a message to a third-party may include a message to security personnel, a local authorities or police. In another example, when a condition indicated all four tire are flat, a message to a third party may include a message to security personnel, a local authorities or police, indicating vandalism and/or tires of vehicle <NUM> have been slashed. Messages to one or more other third-parties related to the condition of the first message and/or a user command of the second message should be considered within the scope of the present disclosure.

Methods illustrated in <FIG> are described below with reference to system <NUM>. It should be appreciated that the methods described herein are not limited to system <NUM>. Likewise, system <NUM> should not be understood to be limited to one or more of the methods described herein. <FIG> illustrates method <NUM> according to an example of the present disclosure. Method <NUM> includes detecting <NUM> a vehicle charging station, retrieving <NUM> a user profile from a memory device in the electrically powered vehicle, and communicating <NUM> the user profile to the vehicle charging station, the user profile including billing information.

Method <NUM> may include receiving at least one message from vehicle charging station <NUM> and displaying, at a display device <NUM>, the at least one message to user <NUM>. Method <NUM> may also include receiving a user profile from user <NUM> and storing the user profile in memory device <NUM>. Furthermore, method <NUM> may include receiving an input to in-vehicle user interface <NUM> to define the user profile.

<FIG> illustrates method <NUM> according to an example of the present disclosure. Method <NUM> includes receiving <NUM>, at in-vehicle user interface <NUM>, at least one user input and communicating <NUM>, via vehicle controller <NUM>, a charging parameter to vehicle charging station <NUM> in response to the at least one user input. Method <NUM> may include displaying, at in-vehicle user interface <NUM>, at least one charging option to user <NUM>, and wherein the at least one user input selects the at least one charging option. Method <NUM> may also include displaying, at in-vehicle user interface <NUM>, at least one message from vehicle charging station <NUM>. Method <NUM> may include establishing a wireless connection between electrically powered vehicle <NUM> and vehicle charging station <NUM>.

<FIG> illustrates method <NUM> according to an example of the present disclosure. Method <NUM> includes controlling <NUM>, at the charging device, a charging process including energy transfer between the power source and the electrically powered vehicle, transmitting <NUM>, via network <NUM>, a first electronic message to user <NUM> and receiving <NUM>, via network <NUM>, a second electronic message. The first electronic message includes at least one condition related to at least one of the charging process and electrically power vehicle <NUM>. The second electronic message includes a user command related to the at least one condition.

Method <NUM> may include transmitting the user command to electrically powered vehicle <NUM>. Method <NUM> may also include transmitting a third message to a third-party in response to the user command. Moreover, method <NUM> may include altering the charging process in response to the user command to mitigate the charging error.

While the above functions and systems have been described with reference to system <NUM> or system <NUM>, it should be appreciated that various system examples may be employed to enable one or more of the functions described herein. More specifically, systems described herein should not be understood to be limited to one or more methods described herein, while methods described herein should not be understood to be limited to the particular examples illustrated herein. Accordingly, several different system examples and/or several different method examples are described herein without limitation.

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

While certain functions and/or operations are described above with respect to particular devices, it is contemplated that any device may perform one or more of the described operations. Systems and methods described herein may limit the manual interaction between a charging station and a user of the charging station. Further, the systems and methods described herein may efficiency and conveniently utilize one or more in-vehicle interfaces to communicate with charging station, rather than known interfaces, which are specific to and/or included in charging stations. Further still, the systems and methods described herein may provide communications between a user and a charging station, while the user is away from the charging station.

Some examples involve the use of one or more electronic or computing devices. Such devices typically include a processor or controller, such as a general purpose central processing unit (CPU), a graphics processing unit (GPU), a microcontroller, a reduced instruction set computer (RISC) processor, an application specific integrated circuit (ASIC), a programmable logic circuit (PLC), and/or any other circuit or processor capable of executing the functions described herein. The methods described herein may be encoded as executable instructions embodied in a computer readable medium, including, without limitation, a storage device and/or a memory device. Such instructions, when executed by a processor, cause the processor to perform at least a portion of the methods described herein.

Claim 1:
A vehicle charging station (<NUM>) for charging an electrically powered vehicle (<NUM>), said vehicle charging station comprising:
a power source (<NUM>); and
a charging device (<NUM>) coupled to said power source, said charging device configured to:
control a charging process between said power source and an electrically powered vehicle;
transmit, via at least one network (<NUM>), a first electronic message to a user, the first electronic message including a charging error and an indication that the charging process has been suspended; and
receive, via the at least one network, a second electronic message from the user, the second electronic message including a user command that indicates acceptance of longer charging time, a different voltage, or a partial charge in order to allow the charging process to be resumed;
resume the charging process in response to receiving the user command of the second electronic message,
wherein said charging device (<NUM>) is configured to receive a user profile from the electrically powered vehicle (<NUM>), wherein the user profile includes contact information, and wherein the charging device is configured to transmit the first message based on the contact information.