US20190109475A1 - Smart charging of user devices - Google Patents

Abstract

A charger device may include a coupling component configured to deliver power for charging user devices and a wireless interface configured to broadcast wireless signals. The coupling component may include a connector that may be plugged into a user device or an inductive coil to be inductively coupled to a user device. The charger device may determine whether the coupling component is coupled to a user device and transmit via the wireless interface an “available” signal indicating the charger device is available in response to determining the coupling component is not coupled. The user device may provide a notification to the user based, at least in part, on receiving the “available” signal. The user device may provide the notification further based on other information, such as activity of a user detected by the user device, a geolocation determined by the user device, or information received from a service provider.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
• This application is a continuation of U.S. patent application Ser. No. 14/821,615, filed Aug. 7, 2015, which is incorporated by reference in its entirety.
TECHNICAL FIELD
• The present disclosure relates to electronic charging devices and, more particularly, to electronic charging devices configured to communicate with other devices.
BACKGROUND
• A conventional plug-in charger device for user devices, such as a cell phone charger, includes power adapter components that convert alternating current (AC) to direct current (DC). Charging circuitry that charges a battery of the user device may be included in the user device, which is typical for cell phones, and may receive power from the charger device to charge the battery. Alternatively, the charging circuitry may be included in the charger device.
• A conventional wireless charger device, such as an inductive charger, may include an induction coil to create an alternating electromagnetic field. A corresponding induction coil in a user device may receive power from the alternating electromagnetic field to drive an electric current to charge a battery of the user device.
• A conventional charger device, is unable to notify a user who wants to charge his or her user device when it is not occupied by another user device. Furthermore, although a user device may provide a notification for low battery, it is not able to take into account whether a charger device is available or whether the user is busy.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIGS. 1A-B illustrate block diagrams of a charger device and a user device according to one or more embodiments of the present disclosure.
• FIGS. 2A-C illustrate charger devices according to one or more embodiments of the present disclosure.
• FIG. 3 illustrates a block diagram of a networked system according to one or more embodiments of the present disclosure.
• FIGS. 4A-B illustrate flow diagrams of processes for broadcasting signals by a charger device according to one or more embodiments of the present disclosure.
• FIG. 5 illustrates a flow diagram of a process for broadcasting two or more types of signals by a charger device according to one or more embodiments of the present disclosure.
• FIG. 6 illustrates a flow diagram of a process for generating and transmitting signals according to one or more embodiments of the present disclosure.
• FIG. 7 illustrates a flow diagram of a process for notifying a user to charge a user device according to one or more embodiments of the present disclosure.
• FIG. 8 illustrates a charge station or kiosk including multiple charger devices according to one or more embodiments of the present disclosure.
• FIG. 9 illustrates a flow diagram of a process for processing a payment for charging a user device by a charger device according to one or more embodiments of the present disclosure.
• FIG. 10 illustrates a block diagram of a system for implementing one or more components inFIGS. 1A-B andFIG. 3 according to one or more embodiments of the present disclosure.
• Embodiments of the present disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures, wherein showings therein are for purposes of illustrating embodiments of the present disclosure and not for purposes of limiting the same.
DETAILED DESCRIPTION
• The present disclosure provides devices, systems, and methods relating to charger devices configured to wirelessly communicate with other devices. In the following description, specific details are set forth describing certain embodiments. It will be apparent, however, to one skilled in the art that the disclosed embodiments may be practiced without some or all of these specific details. The specific embodiments presented are meant to be illustrative, but not limiting. One skilled in the art may realize other material that, although not specifically described herein, is within the scope of this disclosure.
• In one or more embodiments, a charger device may be a charger, power adapter, or an external power source that delivers power for charging user devices such as mobile phones (e.g., cell phones, smartphones, etc.), wearable devices, computers, tablets, or other user devices. The charger device includes a coupling component configured to deliver power to charge user devices and a wireless interface configured to transmit signals. The coupling component may include a connector that may be plugged into a user device. Alternatively, the coupling component may include an inductive coil that may be inductively coupled to a user device. The wireless interface may transmit at least one of Bluetooth® signals such as Bluetooth® Low Energy (BLE) (also called Bluetooth® Smart) signals, Wi-Fi® signals, infrared (IR) signals, visible light signals, or radio frequency (RF) signals.
• In one or more embodiments, a charger device may determine whether the coupling component is connected to or otherwise coupled to a user device and transmit via the wireless interface an “available” signal indicating the charger device is available in response to determining the coupling component is not coupled. The user device may provide a notification to the user based, at least in part, on receiving the “available” signal. In some embodiments, the charger device stops transmitting the “available” signal in response to determining the coupling component is coupled to the user device. In other embodiments, the charger device stops transmitting the “available” signal in response to determining the coupling component is coupled to the user device that is charging, and resumes transmitting the “available” signal in response to determining the coupling component is coupled to the user device that is done charging.
• In some embodiments, the coupling component may include a data interface to communicate data between the charger device and the coupled user device. The charger device may receive via the data interface an identifier (e.g., a device identifier or a user identifier) from the user device while the coupling component is coupled to or electronically connected to the user device, and transmit a “done charging” signal that includes the identifier indicating that the user device is done charging in response to determining the coupling component is coupled to the user device that is done charging. Another user device that is bonded to, paired to, linked with, or otherwise associated with the user device may, in response to receiving the “done charging” signal, recognize the identifier included in the “done charging” signal and provide the user a notification indicating the user device is done charging.
• For example, a user may have a wearable device that is paired with his or her smartphone (e.g., via Bluetooth® pairing). The smartphone may store a device identifier for the wearable device. A charger device may transmit an “available” signal to the smartphone and/or wearable device, and the smartphone and/or the wearable device may notify the user to charge the wearable device. When the user plugs in the connector of the charger device to the wearable device, the charger device may stop transmitting the “available” signal. The charger device may access the wearable device for the device identifier via the connector. When the wearable device is done charging, the charger device may transmit a “done charging” signal. When the smartphone receives the “done charging” signal, the smartphone may recognize the device identifier included in the “done charging” signal and notify the user that the wearable device is done charging, for example, by presenting a notification on a display of the smartphone. In another example, the smartphone may be the device that is charged, and the wearable device may be the device that receives the “done charging” signal and notify the user that the smartphone is done charging, for example, by providing a vibration or by presenting a notification on a display or an indicator, such as a light-emitting diode (LED), of the wearable device.
• In one or more embodiments, a user device, or a service provider server in communication with a user device, may determine a charger device is available in response to the user device receiving an “available” signal from the charger device, determine an amount of power remaining in a battery of the user device, and provide a notification to charge the user device based, at least in part, on receiving the “available” signal and the amount of power remaining in the battery.
• In some embodiments, the notification to charge the user device may further be provided based on activity data. The activity data may be tracked by a motion sensor of the user device. The activity data may include, for example, recent activity data indicating whether the user has been recently active and/or activity history data indicating whether the user is usually active at that time of the day in general or at that day of the week. For example, the user device may notify the user to charge the user device if the charger device is available, the battery is low, and the user has been idle for 5 minutes or is typically idle during that time of the day, presuming that the user does not need the user device at the moment.
• In some embodiments, the notification to charge the user device may further be provided based on a geolocation of the user device. The geolocation may be determined via a global positioning system (GPS) of the user device. For example, the user device may notify the user to charge the user device if the charger device is available, the battery is low, and the user is determined to be at home based on the geolocation.
• In some embodiments, the notification to charge the user device may further be provided based on battery usage data of the user device. The battery usage data may be used to forecast how much power is required by the battery, for example, to get through the day. The battery usage data may also be used to determine when to charge and how much to charge to maximize battery life.
• In yet further embodiments, the notification to charge the user device may be based on the amount of power remaining with the charger device. For example, with charger devices using a battery or other finite source of power, a notification may be sent even when a currently coupled and charging user device is not at 100% power. In one embodiment, the notification is sent based on the remaining power level of the charger device, how many user devices need charging (e.g., less than 100% power), the power level of the currently charging user device, and the power level of the user devices needing to be charged. Various thresholds can be used based on preferences and usage. In this way, more user devices may be charged and the charger device more efficiently utilized.
• FIGS. 1A-B illustrate block diagrams100 of acharger device110 and one ormore user devices150, such as user devices150aand150b, of auser102, according to one or more embodiments of the present disclosure.
• Charger device110 may include acoupling component112,power supply components116, a wireless transceiver orother wireless interface120, aprocessor122, amemory124, and/orother components126 that are interconnected by a bus128 or other communication mechanism for communicating information between the various components.
• Coupling component112, in various embodiments, is configured to be connected to or otherwise coupled touser device150 via acoupling component152 ofuser device150.Coupling component112 may include adata interface114 configured to communicate data to and fromuser device150.
• In some embodiments,coupling component112 includes a connector (e.g., a micro-Universal Serial Bus (USB)™ connector, a mini-USB™ connector, a Lightning™ connector from Apple®, etc.), such as a plug or a receptacle, to be connected touser device150. The connector may include one or more power pins configured to chargeuser device150 by delivering power received frompower supply components116 touser device150. The connector may also include one or more data pins to provide data interface114 for transmitting and receiving data. The connector may include one or more other pins such as a ground pin.
• Alternatively,coupling component112 includes components to wirelessly couple touser device150 viacoupling component152 ofuser device150. For example,coupling component112 may include an inductive coil to be inductively coupled to a corresponding inductive coil incoupling component152 and provide an alternating electromagnetic field for charginguser device150.Coupling component112 may implement other techniques and mechanisms for wirelessly delivering power touser device150, such as wireless conductive charging.
• Power supply components116, in various embodiments, deliver power tocoupling component112. In some embodiments,power supply components116 may includepower adapter components118 that convert alternating current (AC) received from anexternal power source190, such as an AC power outlet, to direct current (DC) whilecharger device110 is connected to (e.g., by plugging into)external power source190.Power adapter components118 may include, for example, a transformer, a rectifier, a filter, and/or a regulator. The transformer may step down the voltage of the AC power received fromexternal power source190. The rectifier may convert the AC signal to a DC signal. The filter may smooth out the DC signal, and a regulator may help keep the output DC signal steady. In some embodiments,power supply components116 may include a battery (e.g., a portable battery) that provides power tocoupling component112. The battery may receive AC power fromexternal power source190 and be charged whencharger device110 is connected toexternal power source190.
• Wireless interface120, in various embodiments, is configured to transmit (e.g., broadcast) and/or receive one or moresignals including signal104 and signal106 shown inFIG. 1A andFIG. 1B respectively.Wireless interface120 may include a wireless communication component, such as a wireless transmitter or a wireless transceiver for local wireless communications.Wireless interface120 may transmit one or more sequences of information via one ormore signals104,106 such that whenuser device150 capable of receiving information fromwireless interface120 comes within a communication range ofwireless interface120, the device may receive a communication fromwireless interface120 and be instructed to perform an action, such as displaying a notification (e.g., a “charger available” notification, a “done charging” notification, etc.).
• In some embodiments,wireless interface120 may include a Bluetooth® transceiver or transmitter, such as a BLE transceiver or transmitter. BLE is a technology that transmits information at a frequency of about 2.4 GHz (about 2042-2480 MHz) over forty 2 MHz-wide channels, and has a range of about 100 meters or about 320 feet. Information transmitted according to the BLE protocol may be transmitted at a rate of about 1 Mbit/s with an application throughput of about 0.27 Mbit/s. In some embodiments, BLE communications may be secured using 128-bit Advanced Encryption Standard (AES) encryption with counter mode with a cipher block chaining message authentication code (CBC-MAC) and user defined security. Further, in some embodiments, BLE communications may utilize adaptive frequency hopping, lazy acknowledgement, a 24-bit cyclic redundancy check (CRC), and 32-bit message integrity check for robustness. Moreover, in some embodiments, BLE-capable devices may consume a fraction of the power of standard Bluetooth® devices due to the BLE protocol allowing low duty cycles, and being designed for applications that may not require continuous data transfer. In other embodiments,wireless interface120 may include a Wi-Fi® transceiver or transmitter, a RF transceiver or transmitter, an IR transceiver or transmitter, or other wireless transceiver or transmitter. Corresponding to the type ofwireless interface120 that is implemented, signals104 and106 may be Bluetooth® signals such as BLE signals, RF signals, IR signals, or other wireless signals.
• Processor122, in various embodiments, may include one or more microprocessors, microcontrollers, hardwired logic devices such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs) such as field-programmable gate arrays (FPGAs), or other processing systems. In some embodiments,processor122 may execute instructions stored onmemory124 which causesprocessor122 to perform operations described herein. In other embodiments,processor122 may be hardwired to perform the operations described herein.
• As shown inFIG. 1A,processor122 may be configured to determine thatcoupling component112 is not coupled touser device150, and in response operatewireless interface120 to transmit (e.g., broadcast) an “available”signal104 indicatingcharger device110 is available to chargeuser device150. For example, “available”signal104 may transmit a data packet that includes a message indicatingcharger device110 is available and/or a timestamp.
• As shown inFIG. 1B,processor122 may be configured to determine thatcoupling component112 is coupled touser device150 via a connection orother coupling108, and in response operatewireless interface120 to not transmit an “available” signal (e.g., “available”signal104 shown inFIG. 1A).Processor122 may operate data interface114 ofcoupling component112 orwireless interface120 to receive an identifier such as the device identifier ofuser device150 and/or a user identifier fromuser device150, and may store the identifier inmemory124.Processor122 may further be configured to determine thatcoupling component112 is coupled touser device150 via connection/coupling108 and thatuser device150 is done charging, and in response operatewireless interface120 to transmit a “done charging”signal106 indicatinguser device150 is done charging. For example, “done charging”signal106 may transmit a data packet that includes a message indicatinguser device150 is done charging, the identifier (e.g., the device identifier ofuser device150 and/or the user identifier), and/or a timestamp.
• In some embodiments, whilecharger device110 is coupled touser device150 via connection orother coupling108 as shown inFIG. 1B,processor122 may operate data interface114 ofcoupling component112 orwireless interface120 to receive location data fromuser device150 determined by a location component such as aGPS170 ofuser device150 and store the location data inmemory124.Processor122 may then determine thatcoupling component112 is not coupled touser device150 as shown inFIG. 1A, and in response operatewireless interface120 to transmit (e.g., broadcast) “available”signal104 indicatingcharger device110 is available to chargeuser device150 and a geolocation ofcharger device110. For example, “available”signal104 may transmit a data packet that includes a message indicatingcharger device110 is available, the location data, and/or a timestamp.
• The location data included in “available” signal may be the location data received from the most recently coupleduser device150 that, includeslocation component170, and the location data stored inmemory124 may be updated eachtime user device150 that includeslocation component170 is coupled tocharger device110. The location data received from one ofuser devices150 may be used repeatedly for “available”signal104, for example, untilcharger device110 is disconnected from (e.g., by unplugging from)external power source190 and/or the location data is updated whencharger device110 is coupled to anotheruser device150 that includeslocation component170.
• In further embodiments,charger device110 includes its own location component that determines a geolocation to be included in “available”signal104 as location data. In yet further embodiments, location data may be provided byuser102. For example,user102 may enter in a geolocation onuser device150, which may be communicated tocharger device110 viadata interface114 ofcoupling component112 orwireless interface120. In another example, forcharger devices110 at a charging station or kiosk wherecharger devices110 are placed at a particular location by a merchant or a service provider, the merchant or the service provider may program the location data intocharger devices110.
• Providing a geolocation ofcharger device110 in “available”signal104 may be advantageous whencharger device110 is at a location that is not easily visible or when there aremultiple charger devices110 at a location. Also, providing a geolocation ofcharger device110 in “available”signal104 may be advantageous forcharger devices110 that are provided (e.g., for free or for a fee) at various public or private locations for use bymany users102 such as the general public. For example, charger stations or kiosks that providecharger devices110 for a fee may be located in discrete places yet still allowusers102 to find the charger stations or kiosks when theiruser devices150 needs to be charged.
• In one or more embodiments,charger device110 may includeother components126, such as a network interface configured to communicate with aservice provider server130 and/oruser device150 over a network180 (as shown inFIG. 3). In some embodiments, other components may include a location component such as a GPS configured to determine a geolocation. In some embodiments,other components126 include charging circuitry configured to charge abattery156 inuser device150. In other embodiments, charging circuitry is included inuser device150, which is typical for user devices such as mobile phones.
• Each of one ormore user devices150, such as user devices150aand150b, may be a mobile phone (e.g., a cell phone, a smartphone, etc.), a wearable device (e.g., an activity tracker, a fitness tracker, a head-mounted display (HMD) device, a smartwatch, etc.), a tablet, a personal computer, a laptop, a notebook, a set-top box, a video game console, or other user device.User device150 may includecoupling component152,battery156, anetwork interface158, awireless interface160, aprocessor162, amemory164, adisplay166, one or moremotion sensor components168, location component such asGPS170, and/orother components172 that are interconnected by abus174 or other communication mechanism for communicating information.
• Coupling component152, in various embodiments, is configured to be coupled tocharger device110 viacoupling component112 ofcharger device110.Coupling component152 may include adata interface154 configured to communicate data to and fromcharger device110.
• In some embodiments,coupling component152 includes a connector (e.g., a micro-USB™ connector, a mini-USB™ connector, a Lightning™ connector from Apple®, etc.), such as a plug or a receptacle, to be connected tocoupling component112 ofcharger device110. The connector may include one or more power pins configured to receive power frompower supply components116 viacoupling component112. The connector may also include one or more data pins to provide data interface154 for transmitting and receiving data. The connector may include one or more other pins such as a ground pin.
• Alternatively,coupling component152 may include components to wirelessly couple tocharger device110 viacoupling component112 ofcharger device110. For example,coupling component152 may include an inductive coil to be inductively coupled to the inductive coil ofcharger device110.Coupling component152 may convert the alternating electromagnetic field generated by the inductive coil ofcharger device110 to electric current for chargingbattery156.Coupling component152 may implement other techniques and mechanisms for wirelessly receiving power fromcharger device110, such as wireless conductive charging.
• Network interface158, in various embodiments, is configured to communicate with other devices or servers overnetwork180. For example,user device150 may communicate withservice provider server130 vianetwork interface158. In some embodiments,network interface158 includes a wireless communication component, such as a wireless broadband component, a wireless satellite component, or various other types of wireless communication components including RF, microwave frequency (MWF), and/or IR components configured to communicate withnetwork180. In some embodiments,network interface158 is configured to interface with a coaxial cable, a fiber optic cable, a digital subscriber line (DSL) modem, a public switched telephone network (PSTN) modem, an Ethernet device, and/or various other types of wired and/or wireless network communication devices configured to communicate withnetwork180.
• Network180, in various embodiments, may be implemented as a single network or a combination of multiple networks. For example,network180 may include the Internet and/or one or more intranets, landline networks, wireless networks, and/or other appropriate types of communication networks. In another example,network108 may comprise a wireless telecommunications network (e.g., cellular phone network) adapted to communicate with other communication networks, such as the Internet.
• Wireless interface160, in various embodiments, is configured to transmit and receive one or moresignals including signal104 and signal106, shown inFIG. 1A andFIG. 1B respectively.Wireless interface160 may include a wireless communication component, such as a wireless transceiver for local wireless communications.Wireless interface160 may receive one or more sequences of information via one ormore signals104,106 fromwireless interface120 ofcharger device110 when within the range ofwireless interface120. In some embodiments,wireless interface160 may include a Bluetooth® transceiver, such as a BLE transceiver, as further described above in relation towireless interface120. In other embodiments,wireless interface160 may include a Wi-Fi® transceiver, a RF transceiver, an IR transceiver, or other wireless transceiver. Corresponding to the type ofwireless interface160 that is implemented, signals104,106 may be Bluetooth® signals such as BLE signals, Wi-Fi® signals, RF signals, IR signals, or other wireless signals.
• Processor162, in various embodiments, may include one or more microprocessors, microcontrollers, hardwired logic devices such as ASICs, PLDs such as FPGAs, or other processing systems. In some embodiments,processor162 may execute instructions stored onmemory164 or a non-transitory medium174 which causesprocessor162 to perform operations described herein.
• As shown inFIG. 1A,processor162 may be configured to determinecharger device110 is available in response towireless interface160 receiving “available”signal104 fromcharger device110 whencharger device110 is not coupled and charger device is within broadcast range ofcharger device110.Processor162 may provide a notification to chargeuser device150 based on an amount of power remaining inbattery156, activity data tracked bymotion sensor components168, location data determined bylocation component170, and/or other information or data related touser102 received fromservice provider server130. In some embodiments, “available”signal104 includes a geolocation of charger device and the notification may include the geolocation ofcharger device110, which may be displayed, for example, on a map.
• Display166, in various embodiments, is configured to display information touser102.Display166 may include an LED screen, an organic light-emitting diode (OLED) screen such as an active matrix OLED (AMOLED) screen, a liquid crystal display (LCD) screen, a plasma display panel (PDP) screen, or a cathode ray tube (CRT) screen.Display166 may further include an input component. For example,display166 may be a touchscreen display configured to present a graphical user interface (GUI) touser102 and receive a user interaction with the GUI.
• One ormore motion sensors168, in various embodiments, are configured to detect (e.g., track, monitor, quantify, capture, measure, and/or otherwise detect) movement, such as activity ofuser102, to generate activity data, which may be stored inmemory164 and/or transmitted toservice provider server130 vianetwork180. One ormore motion sensors168 may include one or more accelerometers that measures acceleration and a gyroscope that measures orientation that may be used together to detect the movement/activity ofuser102.
• Location component170, in various embodiments, determines a geolocation ofuser device150. Location component may be implemented as a GPS that uses satellite-based positioning and/or assisted GPS (A-GPS) that uses cell tower information to improve reliability and accuracy of GPS-based positioning. In one implementation, the geolocation may include GPS coordinates, zip-code information, area-code information, street address information, and/or various other generally known types of location data or information.
• In one or more embodiments,user device150 may includeother components172, such as charging circuitry configured to chargebattery156 using power received bycoupling component152 fromcharger device110. In other embodiments, the charging circuitry may be included incharger device110.
• FIGS. 2A-C illustratecharger devices210,230, and250 such ascharger device110 inFIGS. 1A-B, according to one or more embodiments of the present disclosure.
• As shown inFIG. 2A,charger device210 may include coupling component112 (inFIGS. 1A-B) implemented as a connector such asplug212 and acaptive power cable214 that is connected to plug212 and fixedly attached to ahousing216. Plug212 may be removably connected to coupling component152 (inFIGS. 1A-B) ofuser device150, which may be implemented as a receptacle corresponding to plug212.Housing216 may include various other components ofcharger device210, such aspower supply components116,wireless interface120, and other components ofcharger device110 shown inFIGS. 1A-B.Power supply components116 ofcharger device210 may include apower plug218 or other connector provided onhousing216 to be plugged into an AC power outlet, such as external power source190 (inFIGS. 1A-B).
• As shown inFIG. 2B,charger device230 may include coupling component112 (inFIGS. 1A-B) implemented as a connector such as areceptacle232. Apower cable234 that is connected to plug236 on one side and plug238 on the other side may be removably connected to ahousing240 by pluggingplug238 intoreceptacle232. Plug236 may be removably connected to coupling component152 (inFIGS. 1A-B) ofuser device150, which may be implemented as a receptacle corresponding to plug236.Housing240 may include various other components ofcharger device230, such aspower supply components116,wireless interface120, and other components ofcharger device110 shown inFIGS. 1A-B.Power supply components116 ofcharger device210 may include a power plug orother connector242 provided onhousing212 to be plugged into an AC power outlet, such as external power source190 (inFIGS. 1A-B).
• As shown inFIG. 2C,charger device250 may include coupling component112 (inFIGS. 1A-B) implemented as an inductive coil in a charging plate ordock252. Apower cable254 may connect, fixedly or removably, to chargingplate252 on one side and connect, fixedly or removeably, to ahousing256 on the other side. Various other components ofcharger device250, such aspower supply components116,wireless interface120, and other components ofcharger device110 shown inFIGS. 1A-B may be provided in chargingplate252,housing256, or distributed between chargingplate252 andhousing256.Power supply components116 ofcharger device250 may include a power plug orother connector258 provided onhousing256 to be plugged into an AC power outlet, such as external power source190 (inFIGS. 1A-B).
• Charger device250 may use the inductive coil in chargingplate252 to generate an alternating electromagnetic field.Coupling component152 of user device150 (shown inFIGS. 1A-B) may be implemented as a corresponding inductive coil. Accordingly, when inductive coil ofuser device150 is coupled to the inductive coil ofcharger device250, for example, by placinguser device150 on or near chargingplate252, the inductive coil ofuser device150 converts power from the alternating electromagnetic field into electric current to charge a battery such asbattery156 of user device150 (shown inFIGS. 1A-B).
• FIG. 3 illustrates a block diagram of anetworked system300 according to one or more embodiments of the present disclosure.
• User device150 may include any appropriate combination of hardware and/or software, including the various components ofuser device150 shown inFIGS. 1A-B. One ormore processors162 may be configured to read and execute instructions stored onmemory164 or tangible non-transitory machine-readable medium174. In one or more embodiments,user device150 includesmemory164 and/or non-transitory machine-readable medium174 that stores instructions that, when executed by one ormore processors162, are adapted to causeuser device150 to perform specific tasks. In some embodiments, the instructions may be executed by one ormore processors162 in response to interaction withuser102. For example, such instructions may include abrowser application352 such as a mobile browser application, which may be used to provide a user interface to permituser102 to browse information available overnetwork180, including information hosted byservice provider server130.Browser application352 may be implemented as a web browser to view information available overnetwork180.Browser application352 may include a GUI that is configured to allowuser102 to interface and communicate withservice provider server130 or other servers managed by content providers or merchants vianetwork180. For example,user102 may be able to access websites to find and purchase items, as well as access user account information or web content.
• User device150 may also include acharge management application354 that notifiesuser102 to chargeuser device150, notifiesuser102 thatcharger device110 is available, and/or that anotheruser device150 ofuser102 that is plugged intocharger device110 is done charging.Charge management application354 may determine whether to provide a notification to chargeuser device150 based on receiving an “available” signal such as signal104 (inFIG. 1A) fromcharger device110 and/or an amount of power remaining in battery156 (shown inFIGS. 1A-B)Charge management application354 may further determine whether to provide a notification based on accessing data in adatabase360, which may be stored in memory164 (inFIGS. 1A-B). For example,charge management application354 may determine whether to provide the notification based onactivity data364 tracked by motion sensor components168 (inFIGS. 1A-B),location data366 determined by location component170 (inFIGS. 1A-B), and/or other information or data related touser102 that may be indatabase360 and/or received fromservice provider server130.
• Charge management application354 may access one ormore identifiers362 indatabase360 and transmit at least one ofidentifiers362 tocharger device110 to be included in a “done charging” signal such as signal106 (inFIG. 1B) indicatinguser device150 is done charging, which may be recognized by anotheruser device150 ofuser102. One ormore identifiers362 may include a device identifier such as a universally unique device identifier (UUID), a media access control (MAC) address/number, or other device identifier. In addition, or alternatively, one ormore identifiers362 may include a user identifier, which may be associated with and/or stored in a user account340 stored in adatabase338 ofservice provider server130.Charge management application354 may perform various other operations relating to charge management and notifications relating to charginguser device150 described herein.
• User device150 may also include apayment application356 that may be utilized byuser102 usinguser device150 to make a payment. In some embodiments,payment application356 may be configured to make a payment usingservice provider server130 as a payment processor. In some embodiments, functionalities provided bycharge management application354 andpayment application356 may actually be provided by a single application.
• User device150 may include one or moreother applications358 as may be desired in one or more embodiments to provide additional features available touser102, including accessing user account340 stored in adatabase338 ofservice provider server130. For example,other applications358 may include interfaces and communication protocols that allow the user to communicate information withservice provider server130 and other online sites vianetwork180.Other applications358 may also include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) overnetwork180 or various other types of generally known programs and/or applications.Other applications358 may include mobile applications downloaded and resident onuser device150 that enableuser102 to access content.
• Service provider server130, according to some embodiments, may be maintained by an online service provider, such as PayPal, Inc. of San Jose, Calif., which may provide services related to charge management and notifications relating to charginguser device150.Service provider server130 may also be capable of processing online financial and information transactions on behalf ofuser102.Service provider server130 may also be capable of providing access to goods and services (collectively referred to as “items”) of a merchant or service provider that are for purchase and may provide a payment service processing for the purchased items. Items may include delivering power to chargeuser devices150 for a fee usingcharger devices110 at a charge station or kiosk.
• Service provider server130 may include acharge management application332, which may be configured to interact withuser device150 vianetwork180. In some embodiments,charge management application332 may maintain information and data related touser102, such asactivity data342, in user account340 stored indatabase338.Charge management application332 may determine whether to notifyuser102 to chargeuser device150 in response touser device150 receiving “available”signal104 and based on at least a part of the information and data in user account340, and/or transmit at least a part of the information and data in user account340 touser device150 such thatuser device150 may determine whether to notifyuser102 to chargeuser device150 in response to receiving “available”signal104.Charge management application332 may perform various other operations relating to charge management and notifications relating to charginguser device150 described herein.
• Service provider server130 may also include apayment application334 that may facilitate processing payments, for example, fromuser102 to a merchant or service provider.Payment application334 may be configured to interface withpayment application356 to receive payment details, user information, merchant information, charger device information, and additional information for processing a payment on behalf ofuser102. In some embodiments,payment application334 may also be capable of interfacing withcharger device110 at a charge station or kiosk such that whenuser device150 is coupled tocharger device110, a payment may be authorized for use ofcharger device110 to whichuser device150 is coupled. In some embodiments, functionalities provided bycharge management application332 andpayment application334 may actually be provided by a single application.
• Service provider server130 may also include adatabase338 that includes user accounts340 including account information for users having an account with the service provider, such asuser102. In some embodiments,payment application334 may process payments based on account information in user account340 ofdatabase338.Service provider server130 may includeother applications336 and may also be in communication with one or more external databases (not shown), that may provide additional information to be used byservice provider server130. In some embodiments, the one or more external databases may be databases maintained by third parties, and may include third party account information ofuser102.
• FIG. 4A illustrates a flow diagram of aprocess400 for broadcasting signals such as signal104 (inFIG. 1A) by a charger device such as charger device110 (inFIGS. 1A-B), according to one or more embodiments of the present disclosure.
• Atblock402,charger device110 receives power from an external power source such as external power source190 (inFIGS. 1A-B). For example, a user such as user102 (inFIGS. 1A-B) may connect charger device110 (e.g., by plugging inplug218,242, or258 inFIGS. 2A-C) to an AC power outlet.
• Atblock404,charger device110 determines whether charger device110 (e.g., usingcoupling component112 inFIGS. 1A-B) is connected to or otherwise coupled to a user device such as user device150 (inFIGS. 1A-B).
• In some embodiments,coupling component112 includes a connector (e.g., plug212 orreceptacle242 inFIGS. 2A-B), andcharger device110 may determine thatcoupling component112 is connected touser device150 whenplug212 is plugged into a corresponding receptacle ofuser device150 orreceptacle242 is connected to user device150 (e.g., using a power cable such aspower cable234 and a plug such asplug236 and238 inFIG. 2B). For example,charger device110 may determine a connection such as connection108 (inFIG. 1B) by detecting a power draw byuser device150 or an increased current flow. In another example,charger device110 may determineconnection108 by detecting contact withuser device150 using a physical button or switch provided onplug212,receptacle232, or plug236.
• In other embodiments,coupling component112 includes an inductive coil in acharging plate252, and charger device may determine thatcoupling component112 is wirelessly coupled touser device120 whenuser device150 including a corresponding inductive coil is placed on or near chargingplate252. For example,charger device110 may determine a coupling such as coupling108 (inFIG. 1B) by detectinguser device150 is within a charging range ofcharger device110 using wireless communications, such as Bluetooth® communication, radio-frequency identification (RFID) communication, or other communication that may be used to determine or estimate distance between two devices. In another example,charger device110 may include a proximity sensor to determinecoupling108. In a further example,charger device110 may determine coupling108 by detecting a power draw byuser device150 or change in current flow through the inductive coil. In a further example,charger device110 may determine coupling108 by detecting contact withuser device150 using a physical button or switch provided on chargingplate252.
• Atblock406,charger device110 broadcasts or otherwise transmits (e.g., viawireless interface120 inFIGS. 1A-B) an “available” signal such as signal104 (inFIG. 1A) indicatingcharger device110 is available in response to determining thatcharger device110 is not connected to or otherwise coupled touser device150. For example, “available”signal104 may include a message indicatingcharger device110 is available and/or a timestamp.
• In some embodiments,charger device110 may broadcast or otherwise transmit “available”signal104 indicatingcharger device110 is available and also the location ofcharger device110 in response to determining thatcharger device110 is not connected to or otherwise coupled touser device150. For example, “available”signal104 may include a message indicatingcharger device110 is available, the location data, and/or a timestamp.Charger device110 may have received location data such as location data366 (inFIG. 3) fromuser device150 while it was previously connected to or otherwise coupled touser device150 and have storedlocation data366 in a memory such as memory124 (inFIGS. 1A-B). Alternatively, location data may be determined by a location component such as a GPS included incharger device110, or may be provided by a user such as user102 (inFIGS. 1A-B) (e.g., via user device150).
• Atblock408, charger device110 (e.g., via wireless interface120) does not broadcast “available”signal104 in response to determining that charger device110 (e.g., using coupling component112) is connected to or otherwise coupled touser device150.
• In an example, whenuser102 connects charger device110 (e.g., by plugging inplug218,242, or258 inFIGS. 2A-C) to an AC outlet, charger device starts broadcasting “available”signal104 and continues broadcasting “available”signal104 whilecharger device110 is not connected to or otherwise coupled touser device150. Whenuser102 connects charger device110 (e.g., by plugging inplug212 or236 inFIGS. 2A-B) touser device150,charger device110 stops broadcasting the “available signal.” Whenuser102 subsequently disconnects charger device110 (e.g., by unpluggingplug212 or236) fromuser device150, which may be afteruser device150 is done charging or only partially charged,charger device110 resumes broadcasting “available”signal104, as shown inblock406.
• FIG. 4B illustrates another flow diagram of aprocess410 for broadcasting signals by a charger device, such ascharger device110 inFIGS. 1A-B, according to one or more embodiments of the present disclosure.
• Atblock412,charger device110 receives power, as described above atblock402.
• Atblock414,charger device110 determines whether charger device110 (e.g., usingcoupling component112 inFIGS. 1A-B) is connected to or otherwise coupled to a user device such as user device150 (inFIGS. 1A-B), as described above atblock404.
• Atblock416,charger device110 broadcasts or otherwise transmits (e.g., viawireless interface120 inFIGS. 1A-B) an “available” signal such as signal104 (inFIG. 1A) in response to determining thatcharger device110 is not connected to or otherwise coupled touser device150, as described above atblock406.
• Atblock418, charger device110 (e.g., via wireless interface120) does not broadcast or otherwise transmit “available”signal104 in response to determining thatcharger device110 is connected to or otherwise coupled touser device150 while a battery such as battery156 (inFIGS. 1A-B) ofuser device150 is being charged.
• Atblock420,charger device110 determines whetheruser device150 is done charging while still connected to or otherwise coupled touser device150. In response to determining a battery such as battery156 (inFIGS. 1A-B) ofuser device150 is still being charged,charger device110 does not transmit “available” signal, as shown atblock418. In response to determiningbattery156 ofuser device150 is done being charged,charger device110 transmits “available” signal, as shown atblock416.
• In one or more embodiments,battery156 may be done being charged whenbattery156 is fully charged. Alternatively, to extend the life ofbattery156 and to optimize battery health,battery156 may be done being charged when it is charged to a certain amount, which may be a variable amount based on the state or age ofbattery156 or a fixed amount (e.g., 80%).
• In some embodiments,charger device110 may determine thatbattery156 ofuser device150 is done being charged, for example, by detecting a decrease or stop in power draw byuser device150, detecting a decrease or stop in current flow, or no longer detecting contact withuser device150 using a physical button or switch provided onplug212,receptacle232, plug236, or charging plate252 (inFIGS. 2A-C). In other embodiments,charger device110 may receive a communication fromuser device150 indicatinguser device150 is done charging via data interface114 (inFIGS. 1A-B) ofcoupling component112. In a further embodiment,charger device110 may receive a wireless communication fromuser device150 indicatinguser device150 is done charging viawireless interface120.
• In an example, whenuser102 connects charger device110 (e.g., by plugging inplug218,242, or258 inFIGS. 2A-C) to an AC outlet, charger device starts broadcasting “available”signal104 and continues broadcasting “available”signal104 whilecharger device110 is not connected to or otherwise coupled touser device150. Whenuser102 connects charger device110 (e.g., by plugging inplug212 or236 inFIGS. 2A-B) touser device150,charger device110 stops broadcasting the “available signal.” Whenuser device150 is done charging,charger device110 resumes broadcasting “available”signal104. Whenuser102 subsequently disconnects charger device110 (e.g., by unpluggingplug212 or236) fromuser device150,charger device110 continues broadcasting “available”signal104, as shown inblock416.
• FIG. 5 illustrates a flow diagram of aprocess500 for broadcasting two or more types of signals such as one ormore signals104,106 (inFIGS. 1A-B) by a charger device such as charger device110 (inFIGS. 1A-B), according to one or more embodiments of the present disclosure.
• Atblock502,charger device110 receives power, as described above at402.
• Atblock504,charger device110 determines whether charger device110 (e.g., usingcoupling component112 inFIGS. 1A-B) is connected to or otherwise coupled to a user device such as user device150a(inFIGS. 1A-B), as described above atblock404.
• Atblock506,charger device110 broadcasts or otherwise transmits (e.g., viawireless interface120 inFIGS. 1A-B) an “available” signal such as signal104 (inFIG. 1A) in response to determining thatcharger device110 is not connected to or otherwise coupled to user device150a, as described above atblock406.
• Atblock508, charger device110 (e.g., via wireless interface120) does not broadcast or otherwise transmit “available”signal104 in response to determining thatcharger device110 is connected to or otherwise coupled to user device150awhile user device150ais charging.
• Atblock510,charger device110 determines whether user device150ais done charging while still connected to or otherwise coupled to user device150a. In response to determining user device150ais still charging, charger device110 (e.g., via wireless interface120) does not broadcast or otherwise transmit “available”signal104, as shown atblock508.
• Atblock512, in response to determining user device150ais done charging while still connected to or otherwise coupled to user device150a, charger device110 (e.g., via wireless interface120) broadcasts or otherwise transmits a “done charging” signal such as signal106 (inFIG. 1B) that includes an identifier such as identifier362 (e.g., a device identifier or user identifier) received from user device150aindicating that user device150ais done charging. For example, “done charging”signal106 may include a message indicatinguser device150 is done charging, at least one ofidentifiers362, and/or a timestamp. In some embodiments, in response to determining user device150ais done charging, charger device110 (e.g., via wireless interface120) broadcasts or otherwise transmits “done charging”signal106 and also “available”signal104. A process for generating and transmitting “done charging”signal106 is further described below in relation toFIG. 6.
• In one or more embodiments, another user device ofuser102 such as user device150b(inFIGS. 1A-B) may receive “done charging”signal106 and notifyuser102 that user device150ais done charging, such as by providing a notification touser102 on a display such as display166 (inFIGS. 1A-B) of user device150b. In some embodiments, user device150amay be paired to, bonded to, linked with, or otherwise associated with user device150b. During initial pairing (e.g., Bluetooth® initial pairing or bonding), user device150aand user device150bmay each share itsidentifier362, such as a device identifier (e.g., a UUID or MAC address/number), to the other device, and each device may storeidentifier362 of the other device in itsdatabase360. For example, user device150amay storeidentifier362 of user device150bin itsdatabase360 and user device150bmay storeidentifier362 of user device150ain itsdatabase360. When user device150breceives “done charging”signal106, user device150bmay recognizeidentifier362 contained in “done charging”signal106 asidentifier362 of user device150apreviously stored indatabase360 of user device150bduring pairing of user device150aand150b. Whenuser102 receives the notification,user102 is alerted that user device150ais done charging and may go disconnect or otherwise uncouple user device150afromcharger device110.
• Atblock514,charger device110 determines whether charger device110 (e.g., usingcoupling component112 inFIGS. 1A-B) is disconnected from or otherwise uncoupled from user device150a, similarly as described above atblock402.
• In some embodiments,coupling component112 includes a connector (e.g., plug212 orreceptacle242 inFIGS. 2A-B), andcharger device110 may determine thatcoupling component112 is disconnected fromuser device150 when212 or236 (inFIGS. 2A-B) is unplugged from a corresponding receptacle ofuser device150 orreceptacle242 is disconnected from user device150 (e.g., using a power cable such aspower cable234 and a plug such asplug236 and238 inFIG. 2B). For example,charger device110 may determine a connection such as connection108 (inFIG. 1B) is disconnected by detecting a stopped or decreased power draw or a stopped or decreased current flow. In another example,charger device110 may determineconnection108 is disconnected by detecting removal of contact withuser device150 using a physical button or switch provided onplug212,receptacle232, or plug236.
• In other embodiments,coupling component112 includes an inductive coil in acharging plate252, and charger device may determine thatcoupling component112 is decoupled fromuser device120 whenuser device150 including a corresponding inductive coil is removed from on or near chargingplate252. For example,charger device110 may determine a coupling such as coupling108 (inFIG. 1B) is decoupled by detectinguser device150 is removed from a charging range ofcharger device110 using wireless communications, such as Bluetooth® communication, RFID communication, or other communication that may be used to determine or estimate distance between two devices. In another example,charger device110 may include a proximity sensor to determinecoupling108 is decoupled. In a further example,charger device110 may determinecoupling108 is decoupled by detecting a stopped or decreased in power draw or change in current flow through the inductive coil. In a further example,charger device110 may determinecoupling108 is decoupled by detecting removal of contact withuser device150 using a physical button or switch provided on chargingplate252.
• Atblock516, in response to determining charger device110 (e.g., using coupling component112) is no longer connected to or otherwise coupled to user device150a, charger device110 (e.g., via wireless interface120) may broadcast or otherwise transmit “available”signal104 and no longer broadcast or otherwise transmit “done charging”signal106.
• In response to determining charger device110 (e.g., using coupling component112) is still coupled touser device150 that is done charging, charger device continues transmitting “done charging”signal106 and/or “available”signal104, as shown atblock512.
• FIG. 6 illustrates a flow diagram of a process for generating and transmitting a signal by a charger device such as charger device110 (inFIGS. 1A-B) according to one or more embodiments of the present disclosure.
• Atblock602,charger device110 may receive data from a user device such as user device150a(inFIGS. 1A-B) whilecharger device110 is connected to or otherwise coupled to user device150a. In some embodiments,charger device110 may request an identifier such as identifier362 (e.g., a device identifier or user identifier) from user device150aat thetime charger device110 is connected to or otherwise coupled to user device, when user device150ais done charging, or anytime in between.Charger device110 may receiveidentifier362 from user device150avia a data interface such as data interface114 (inFIGS. 1A-B) included in a coupling component such as coupling component112 (inFIGS. 1A-B) used to connectcharger device110 touser device150. Alternatively,charger device110 may receiveidentifier362 from user device150athrough wireless communications via a wireless interface such as wireless interface120 (inFIGS. 1A-B).
• Atblock604,charger device110 generates a “done charging” signal such assignal106 inFIG. 1B that includesidentifier362 received from user device150a.
• Atblock604,charger device110 broadcasts or otherwise transmits “done charging”signal106 indicating user device150ais done charging, as described above atblock512.
• FIG. 7 illustrates a flow diagram of aprocess700 for notifying a user such as user102 (inFIGS. 1A-B) to charge a user device such as user device150 (inFIGS. 1A-B) using a charger device such as charger device110 (inFIGS. 1A-B) according to one or more embodiments of the present disclosure.
• Atblock702, a service provider server such as service provider server130 (inFIGS. 1A-B andFIG. 3) oruser device150 determines thatcharger device110 is available in response touser device150 receiving an “available” signal such as signal104 (inFIG. 1A). In one or more embodiments,user device150 may determinecharger device110 is available in response to receiving “available”signal104. In some embodiments,user device150 may communicate thatcharger device110 is available toservice provider server130 in response to receiving “available”signal104. Based on such communication,service provider server130 may determinecharger device110 is available in response touser device150 receiving “available”signal104.
• Atblock704,service provider server130 oruser device150 determines an amount of power in a battery such as battery156 (inFIGS. 1A-B). In one or more embodiments,user device150 may determine an amount of power left in a battery, for example, by using a coulomb counter to measure the amount of charge (e.g., in ampere hour, Ah) delivered or stored bybattery156 to monitor the amount of power left, by measuring the internal impedance ofbattery156 to determine open circuit voltage used to calculate the amount of power left, and/or by other processes for determining the amount of power left. In some embodiments,user device150 may communicate the amount of power left inbattery156 toservice provider server130 as part of the communication indicatingcharger device110 is available atblock706 or in a separate communication. Based on such communication,service provider server130 may determine the amount of power left inbattery156, which may also be in response touser device150 receiving “available”signal104.
• Atblock706,service provider server130 oruser device150 may access activity data, such asactivity data342 indatabase338 ofservice provider server130 oractivity data364 indatabase360 ofuser device150 in response touser device150 receiving “available”signal104. In one or more embodiments,user device150 may detect movement ofuser102 to generateactivity data364 and store activity data indatabase360 of user device. In some embodiments,user device150 may transmitactivity data364 toservice provider server130 to be stored asactivity data342 in user account340 indatabase338.User device150 may transmitactivity data364 toservice provider server130 by syncingactivity data364 withactivity data342. Alternatively,user device150 may transmitactivity data364 toservice provider server130 by periodically transmittingactivity data364 and/or by transmittingactivity data364 in response to receiving “available”signal104.
• In one or more embodiments,user device150 may accessactivity data342 indatabase338 in response to receiving “available”signal104. In other embodiments,service provider server130 may accessactivity data342 indatabase338 ofservice provider server130 and/oractivity data364 indatabase360 ofuser device150 inresponse user device150 to receiving “available”signal104.
• Activity data364 or342 may include recent activity indicating whetheruser102 has been active and/or howactive user102 has been recently (e.g., in the past 5 minutes).Activity data364 or342 may also include activity history indicating whetheruser102 is usually active at a certain time of day in general or whetheruser102 is usually active at a certain time of day on certain days of the week.
• Atblock708,service provider server130 oruser device150 may access a current time in response touser device150 receiving “available”signal104.
• Atblock710,service provider server130 oruser device150 may determine a geolocation ofuser device150 in response touser device150 receiving “available”signal104. In one or more embodiments,user device150 may use a location component such aslocation component170 to determine the geolocation, which may be stored indatabase360 aslocation data366. In some embodiments,user device150 may provideservice provider server130 with access to the geolocation determined bylocation component170 and/or communicate the geolocation toservice provider server130 as part of the communication indicatingcharger device110 is available atblock706 or in a separate communication. Based on such access or communication,service provider server130 may determine the geolocation ofuser device150 in response touser device150 receiving “available”signal104.
• Atblock712,service provider server130 oruser device150 may determine battery data including battery usage data and/or other battery-related data for a battery such asbattery156 ofuser device150 in response touser device150 receiving “available”signal104. In one or more embodiments,user device150 may include a battery management system and may access battery data from battery management system. In some embodiments,user device150 may communicate the battery data toservice provider server130 as part of the communication indicatingcharger device110 is available atblock706 or in a separate communication. Based on such communication,service provider server130 may determine the battery data in response touser device150 receiving “available”signal104.
• Atblock714,service provider server130 oruser device150 determines whether to notifyuser102 to chargeuser device150 based onuser device150 receiving “available” signal, the amount of power remaining inbattery156,activity data364 or342, time (e.g., time of the day or week), and/or geolocation.Service provider server130 oruser device150 determines whether to notifyuser102 to chargeuser device150 further based on other conditions and/or factors.
• For example,service provider server130 oruser device150 may decide to notifyuser102 to chargeuser device150 whencharger device110 is available and the amount of power remaining inbattery156 is low.
• In another example,service provider server130 oruser device150 may decide to notifyuser102 to chargeuser device150 whencharger device110 is available, the amount of power remaining inbattery156 is low, andactivity data364 or342 indicatesuser102 has not been active recently (e.g., within the past 5 minutes). Whenuser102 has not been active recently, such as whenuser102 is lounging and watching television,user102 presumably does not needuser device150 at the moment.
• In a further example,service provider server130 oruser device150 may decide to notifyuser102 to chargeuser device150 whencharger device110 is available, the amount of power remaining inbattery156 is low,activity data364 or342 indicatesuser102 has not been active recently, andfurther activity data364 or342 indicatesuser102 is usually not active at the time of the day or week.
• In yet another example,service provider server130 oruser device150 may determineuser device150 requires charging by forecasting how muchpower user device150 requires to get through the day (e.g., until night time whenuser102 usually gets home) or to get through a time period in whichuser102 does not have access tocharger device110, such as during a commute (e.g., from home to work or vice versa), based on the battery usage data.Service provider server130 oruser device150 may decide to notifyuser102 to chargeuser device150 whencharger device110 is available anduser device150 requires charging based on the battery usage data.
• Service provider server130 oruser device150 may determine whether to notifyuser102 to chargeuser device150 in response to other combinations of such conditions and/or factors.
• Atblock716,user device150 presents a notification on a display such as display166 (inFIGS. 1A-B). The notification may include amessage prompting user102 to chargeuser device150 and/or indicatecharger device110 is available. In some embodiments, the notification may include a distance tocharger device110.User device150 may determine the distance betweenuser device150 andcharger device110 based on “available” signal104 (e.g., using a timestamp included in “available” signal104). In further embodiments, the notification may further include a geolocation of charger device110 (e.g., presented on a map).
• FIG. 8 illustrates a charge station orkiosk800 includingmultiple charger devices110a-eaccording to one or more embodiments of the present disclosure.
• In one or more embodiments, chargingstation800 may be provided at various public or private locations including an airport, a hotel, a restaurant, a store, a department store, a park, a camp, an airplane, a bus, a school, an office, a fitness center, or other location where one or more users, such as users102 (inFIGS. 1A-B), may want to charge their user devices such as user device150 (inFIGS. 1A-B). Conventional charge stations that charge for use of charger devices include a payment device, such as a credit card or bill acceptor for accepting payment.Charging station800 does not require such a payment device, as each ofcharger devices110a-eis configured to interact withuser device150 to allowservice provider server130 to process payment for providing power for charginguser device150.
• In some embodiments,charger device110etransmits to user device150 a charger device identifier touser device150 via a data interface such as data interface154 (inFIGS. 1A-B).User device150 may transmit the charger device identifier and an identifier such as identifier362 (e.g., a device identifier or user identifier) fromuser device150 toservice provider server130. The charger device identifier may be associated with an account of a merchant or service provider that is charging fees for providing power throughcharger devices110a-e.Identifier362 may be associated with user account340 indatabase338 ofservice provider server130.Service provider server130 may process a payment from user account340 to the account of the merchant or service provider using the charger device identifier andidentifier362.
• In other embodiments,charger device110ereceivesidentifier362 fromuser device150 and transmitsidentifier362 and a charger device identifier toservice provider server130 overnetwork180.Service provider server130 may process a payment from user account340 to the account of the merchant or service provider using the charger device identifier andidentifier362.
• FIG. 9 illustrates a flow diagram of a process for processing a payment for charging a user device such as user device150 (inFIGS. 1A-B) of a user such as user102 (inFIGS. 1A-B) by a charger device such as charger device110 (inFIGS. 1A-B) according to one or more embodiments of the present disclosure.
• Atblock902,service provider server130 may receive fromcharger device110 oruser device150, vianetwork180, a communication including an identifier such as identifier362 (e.g., a device identifier or user identifier) and a charger device identifier, as described above in relation toFIG. 8.
• Atblock904,service provider server130 may determine a user account such as user account340 ofuser102 based onidentifier362. For example,identifier362 may be a user identifier associated with user account340.Service provider server130 may also determine an account of a merchant or service provider that is to receive the payment for providing power throughcharger device110 for charginguser device150 based on charger device identifier. For example, charger device identifier may be associated with the account of the merchant or service provider.
• Atblock906, service provider server may transmit to user device a notification regarding payment for providing power for charginguser device150. For example, the notification may indicate the fee pertime charger device110 is used, or the fee per amount of charge (e.g., in Ah) delivered, or a fee for fully charginguser device150. When the notification is displayed on user device, it may include an accept button or other GUI elements thatuser102 may interact with to authorize or decline payment for charginguser device150.
• Atblock908,service provider server130 may receive an authorization fromuser102 in response touser102 providing authorization onuser device150, such as by touching the accept button in the notification.
• Atblock910,service provider server130 receives fromcharger device110 oruser device150, vianetwork180, a communication indicatinguser device150 is done charging or has been disconnected.
• Atblock912,service provider server130 processes payment from user account140 to the account of the merchant or service provider for providing power touser device150 based on the fee authorized byuser102 and/or the amount of charge provided touser device150.
• FIG. 10 illustrates a block diagram of acomputer system1000 for implementing, for example, a charger device such ascharger device110, service provider server such asservice provider server130, and one or more user device such as one ormore user devices150 inFIGS. 1A-B andFIG. 3, according to one or more embodiments of the present disclosure. It should be appreciated that other devices utilized by users, service providers, and/or merchants in the system discussed above may be implemented ascomputer system1000 in a manner as follows.
• In accordance with various embodiments of the present disclosure,computer system1000, such as a computer and/or a network server, includes a bus1002 or other communication mechanism for communicating information, which interconnects subsystems and components, such as a processing component1004 (e.g., processor, micro-controller, digital signal processor (DSP), etc.), a system memory component1006 (e.g., RAM), a static storage component1008 (e.g., ROM), a disk drive component1010 (e.g., magnetic or optical), a network interface component1012 (e.g., modem or Ethernet card), a display component1014 (e.g., LED display component, OLED display component, LCD component, PDP component, CRT display component, or other display component), an input component1016 (e.g., keyboard, keypad, virtual keyboard, touchscreen, etc.), a cursor control component1018 (e.g., mouse, pointer, trackball, etc.), and/or a location determination component1020 (e.g., a GPS device as illustrated, a cell tower triangulation device, and/or a variety of other location determination devices known in the art). In one implementation,disk drive component1010 may include a database having one or more disk drive components.
• In accordance with various embodiments of the present disclosure,computer system1000 performs specific operations by processingcomponent1004 executing one or more sequences of instructions contained inmemory component1006, such as described herein with respect tocharger device110,service provider server130, and one ormore user devices150. Such instructions may be read intosystem memory component1006 from another computer readable medium, such asstatic storage component1008 ordisk drive component1010. In other embodiments, hard-wired circuitry may be used in place of, or in combination with, software instructions to implement the present disclosure.
• Logic may be encoded in a computer readable medium, which may refer to any medium that participates in providing instructions toprocessing component1004 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. In one embodiment, the computer readable medium is non-transitory. In various implementations, non-volatile media includes optical or magnetic disks, such asdisk drive component1010, volatile media includes dynamic memory, such assystem memory component1006, and transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus1002. In one example, transmission media may take the form of acoustic or light waves, such as those generated during radio wave and IR data communications.
• Some common forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, carrier wave, or any other medium from which a computer is adapted to read.
• In various embodiments of the present disclosure, execution of instruction sequences to practice the present disclosure may be performed bycomputer system1000. In various other embodiments of the present disclosure, a plurality ofcomputer systems1000 coupled by acommunication link1022 to anetwork1024 such asnetwork180 inFIGS. 1A-B andFIG. 3 (e.g., a LAN, WLAN, PTSN, and/or various other wired or wireless networks, including telecommunications, mobile, and cellular phone networks) may perform instruction sequences to practice the present disclosure in coordination with one another.
• Computer system1000 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) throughcommunication link1022 andnetwork interface component1012.Network interface component1012 may include an antenna, either separate or integrated, to enable transmission and reception viacommunication link1022. Received program code may be executed byprocessing component1004 as received and/or stored indisk drive component1010 or some other non-volatile storage component for execution.
• In view of the present disclosure, it will be appreciated that various devices, systems, and methods have been described according to one or more embodiments relating to electronic charging devices configured to communicate with other devices by broadcasting signals.
• Although various components and steps have been described herein as being associated withcharger device110,service provider server130, and one ormore user devices150 ofFIGS. 1A-B andFIG. 3, it is contemplated that the various aspects of such devices and servers illustrated inFIGS. 1A-B andFIG. 3 may be distributed among a plurality of servers, devices, and/or other entities.
• Where applicable, various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and/or software components set forth herein may be combined into composite components comprising software, hardware, and/or both without departing from the scope of the present disclosure. Where applicable, the various hardware components and/or software components set forth herein may be separated into sub-components comprising software, hardware, or both without departing from the scope of the present disclosure. In addition, where applicable, it is contemplated that software components may be implemented as hardware components and vice-versa.
• Software, in accordance with the present disclosure, such as program code and/or data, may be stored on one or more computer readable mediums. It is also contemplated that software identified herein may be implemented using one or more specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein may be changed, combined into composite steps, and/or separated into sub-steps to provide features described herein.
• The various features and steps described herein may be implemented as systems comprising one or more memories storing various information described herein and one or more processors coupled to the one or more memories and a network, wherein the one or more processors are operable to perform steps as described herein, as non-transitory machine-readable medium comprising a plurality of machine-readable instructions which, when executed by one or more processors, are adapted to cause the one or more processors to perform a method comprising steps described herein, and methods performed by one or more devices, such as a hardware processor, mobile device, server, and other devices described herein.
• The foregoing disclosure is not intended to limit the present disclosure to the precise forms or particular fields of use disclosed. As such, it is contemplated that various alternate embodiments and/or modifications to the present disclosure, whether explicitly described or implied herein, are possible in light of the disclosure. Having thus described embodiments of the present disclosure, persons of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of the present disclosure. Thus, the present disclosure is limited only by the claims.

Claims (21)

1. (canceled)

2. A system, comprising:

one or more processors, one or more computer-readable memories, with program instructions stored on the one or more computer-readable memories, the one or more processors configured to execute the program instructions to cause the system to perform the operations comprising:

in response to determining that a first device is coupled to a charging device, determining an identifier from one or more identifiers to transmit to the charging device;

detecting reception of the identifier by a second device; and

in response to the detecting reception of the identifier by the second device, providing a notification to a user of the second device, the notification indicating that the first device has been charged.

3. The system ofclaim 2, wherein the identifier is associated with the first device being charged to a predetermined level.

4. The system ofclaim 2, the operations further comprising determining, based on detecting a power level on the first device, to provide a notification to a user of the first device to charge the first device.

5. The system ofclaim 4, wherein the notification further includes location information corresponding to the charging device.

6. The system ofclaim 4, wherein the determining to provide the notification to charge the first device is further based on receiving a signal from the charger device indicating that the charger device is available for use.

7. The system ofclaim 2, wherein the identifier is associated with the first device.

8. The system ofclaim 2, wherein the identifier is associated with the user of the first device.

9. A method comprising:

in response to determining that a first device is coupled to a charging device, determining an identifier from one or more identifiers to transmit to the charging device;

detecting reception of the identifier by a second device; and

in response to the detecting reception of the identifier by the second device, providing a notification to a user of the second device, the notification indicating that the first device has been charged.

10. The method ofclaim 9, wherein the identifier is associated with the first device being charged to a predetermined level.

11. The method ofclaim 9, further comprising determining, based on detecting a power level on the first device, to provide a notification to a user of the first device to charge the first device.

12. The method ofclaim 11, wherein the notification further includes location information corresponding to the charging device.

13. The method ofclaim 12, wherein the determining to provide the notification to charge the first device is further based on receiving a signal from the charger device indicating that the charger device is available for use.

14. The method ofclaim 9, wherein the identifier is associated with the first device.

15. The method ofclaim 9, wherein the identifier is associated with the user of the second device, and wherein the first device is also associated with the user of the second device.

16. A computer program product comprising:

one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices, the program instructions when executed cause a machine to perform operations comprising:

in response to determining that a first device is coupled to a charging device, determining an identifier from one or more identifiers to transmit to the charging device;

detecting reception of the identifier by a second device; and

in response to the detecting reception of the identifier by the second device, providing a notification to a user of the second device, the notification indicating that the first device has been charged.

17. The computer program product ofclaim 16, wherein the identifier is associated with the first device being charged to a predetermined level.

18. The computer program product ofclaim 16, the operations further comprising determining, based on detecting a power level on the first device, to provide a notification to a user of the first device to charge the first device.

19. The computer program product ofclaim 18, wherein the notification further includes location information corresponding to the charging device.

20. The computer program product ofclaim 19, wherein the determining to provide the notification to charge the first device is further based on receiving a signal from the charger device indicating that the charger device is available for use.

21. The computer program product ofclaim 16, wherein the identifier is associated with the user of the first device.

Images