US20190109475A1 - Smart charging of user devices - Google Patents
Smart charging of user devices Download PDFInfo
- Publication number
- US20190109475A1 US20190109475A1 US16/103,841 US201816103841A US2019109475A1 US 20190109475 A1 US20190109475 A1 US 20190109475A1 US 201816103841 A US201816103841 A US 201816103841A US 2019109475 A1 US2019109475 A1 US 2019109475A1
- Authority
- US
- United States
- Prior art keywords
- user
- user device
- charger
- identifier
- available
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 230000004044 response Effects 0.000 claims abstract description 52
- 238000000034 method Methods 0.000 claims description 31
- 230000015654 memory Effects 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims 6
- 230000008878 coupling Effects 0.000 abstract description 84
- 238000010168 coupling process Methods 0.000 abstract description 84
- 238000005859 coupling reaction Methods 0.000 abstract description 84
- 230000000694 effects Effects 0.000 abstract description 37
- 230000001939 inductive effect Effects 0.000 abstract description 20
- 238000004891 communication Methods 0.000 description 46
- 230000008569 process Effects 0.000 description 18
- 238000010586 diagram Methods 0.000 description 17
- 238000012545 processing Methods 0.000 description 12
- 230000033001 locomotion Effects 0.000 description 9
- 230000005672 electromagnetic field Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 230000007423 decrease Effects 0.000 description 3
- 230000003247 decreasing effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 229920001621 AMOLED Polymers 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000006698 induction Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 238000004566 IR spectroscopy Methods 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/0047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with monitoring or indicating devices or circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J50/00—Circuit arrangements or systems for wireless supply or distribution of electric power
- H02J50/10—Circuit arrangements or systems for wireless supply or distribution of electric power using inductive coupling
-
- H02J7/0027—
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/0042—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by the mechanical construction
- H02J7/0045—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by the mechanical construction concerning the insertion or the connection of the batteries
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/0047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with monitoring or indicating devices or circuits
- H02J7/0048—Detection of remaining charge capacity or state of charge [SOC]
- H02J7/0049—Detection of fully charged condition
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/0047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with monitoring or indicating devices or circuits
- H02J7/005—Detection of state of health [SOH]
-
- H02J7/025—
-
- H02J2007/005—
-
- H02J2007/0062—
-
- H02J2007/0096—
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J2310/00—The network for supplying or distributing electric power characterised by its spatial reach or by the load
- H02J2310/10—The network having a local or delimited stationary reach
- H02J2310/20—The network being internal to a load
- H02J2310/22—The load being a portable electronic device
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/00032—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries characterised by data exchange
- H02J7/00034—Charger exchanging data with an electronic device, i.e. telephone, whose internal battery is under charge
-
- H—ELECTRICITY
- H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
- H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H02J7/00—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries
- H02J7/0047—Circuit arrangements for charging or depolarising batteries or for supplying loads from batteries with monitoring or indicating devices or circuits
- H02J7/0048—Detection of remaining charge capacity or state of charge [SOC]
Definitions
- the present disclosure relates to electronic charging devices and, more particularly, to electronic charging devices configured to communicate with other devices.
- 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.
- 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 in FIGS. 1A-B and FIG. 3 according to one or more embodiments of the present disclosure.
- the present disclosure provides devices, systems, and methods relating to charger devices configured to wirelessly communicate with other devices.
- 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.
- 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.
- 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.
- BLE Bluetooth® Low Energy
- IR infrared
- RF radio frequency
- 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.
- the charger device stops transmitting the “available” signal in response to determining the coupling component is coupled to the user device.
- 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.
- 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.
- an identifier e.g., a device identifier or a user identifier
- 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.
- 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.
- the charger device may stop transmitting the “available” signal.
- the charger device may access the wearable device for the device identifier via the connector.
- the charger device may transmit a “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.
- 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.
- LED light-emitting diode
- 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.
- 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.
- 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.
- 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.
- GPS global positioning system
- 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.
- 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.
- 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 diagrams 100 of a charger device 110 and one or more user devices 150 , such as user devices 150 a and 150 b , of a user 102 , according to one or more embodiments of the present disclosure.
- Charger device 110 may include a coupling component 112 , power supply components 116 , a wireless transceiver or other wireless interface 120 , a processor 122 , a memory 124 , and/or other components 126 that are interconnected by a bus 128 or other communication mechanism for communicating information between the various components.
- Coupling component 112 in various embodiments, is configured to be connected to or otherwise coupled to user device 150 via a coupling component 152 of user device 150 .
- Coupling component 112 may include a data interface 114 configured to communicate data to and from user device 150 .
- coupling component 112 includes a connector (e.g., a micro-Universal Serial Bus (USB)TM connector, a mini-USBTM connector, a LightningTM connector from Apple®, etc.), such as a plug or a receptacle, to be connected to user device 150 .
- the connector may include one or more power pins configured to charge user device 150 by delivering power received from power supply components 116 to user device 150 .
- the connector may also include one or more data pins to provide data interface 114 for transmitting and receiving data.
- the connector may include one or more other pins such as a ground pin.
- coupling component 112 includes components to wirelessly couple to user device 150 via coupling component 152 of user device 150 .
- coupling component 112 may include an inductive coil to be inductively coupled to a corresponding inductive coil in coupling component 152 and provide an alternating electromagnetic field for charging user device 150 .
- Coupling component 112 may implement other techniques and mechanisms for wirelessly delivering power to user device 150 , such as wireless conductive charging.
- Power supply components 116 deliver power to coupling component 112 .
- power supply components 116 may include power adapter components 118 that convert alternating current (AC) received from an external power source 190 , such as an AC power outlet, to direct current (DC) while charger device 110 is connected to (e.g., by plugging into) external power source 190 .
- Power adapter components 118 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 from external power source 190 .
- 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.
- power supply components 116 may include a battery (e.g., a portable battery) that provides power to coupling component 112 .
- the battery may receive AC power from external power source 190 and be charged when charger device 110 is connected to external power source 190 .
- Wireless interface 120 in various embodiments, is configured to transmit (e.g., broadcast) and/or receive one or more signals including signal 104 and signal 106 shown in FIG. 1A and FIG. 1B respectively.
- Wireless interface 120 may include a wireless communication component, such as a wireless transmitter or a wireless transceiver for local wireless communications.
- Wireless interface 120 may transmit one or more sequences of information via one or more signals 104 , 106 such that when user device 150 capable of receiving information from wireless interface 120 comes within a communication range of wireless interface 120 , the device may receive a communication from wireless interface 120 and be instructed to perform an action, such as displaying a notification (e.g., a “charger available” notification, a “done charging” notification, etc.).
- a notification e.g., a “charger available” notification, a “done charging” notification, etc.
- wireless interface 120 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.
- 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.
- AES 128-bit Advanced Encryption Standard
- CBC-MAC cipher block chaining message authentication code
- BLE communications may utilize adaptive frequency hopping, lazy acknowledgement, a 24-bit cyclic redundancy check (CRC), and 32-bit message integrity check for robustness.
- 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.
- wireless interface 120 may include a Wi-Fi® transceiver or transmitter, a RF transceiver or transmitter, an IR transceiver or transmitter, or other wireless transceiver or transmitter.
- signals 104 and 106 may be Bluetooth® signals such as BLE signals, RF signals, IR signals, or other wireless signals.
- Processor 122 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.
- processor 122 may execute instructions stored on memory 124 which causes processor 122 to perform operations described herein. In other embodiments, processor 122 may be hardwired to perform the operations described herein.
- processor 122 may be configured to determine that coupling component 112 is not coupled to user device 150 , and in response operate wireless interface 120 to transmit (e.g., broadcast) an “available” signal 104 indicating charger device 110 is available to charge user device 150 .
- “available” signal 104 may transmit a data packet that includes a message indicating charger device 110 is available and/or a timestamp.
- processor 122 may be configured to determine that coupling component 112 is coupled to user device 150 via a connection or other coupling 108 , and in response operate wireless interface 120 to not transmit an “available” signal (e.g., “available” signal 104 shown in FIG. 1A ).
- Processor 122 may operate data interface 114 of coupling component 112 or wireless interface 120 to receive an identifier such as the device identifier of user device 150 and/or a user identifier from user device 150 , and may store the identifier in memory 124 .
- Processor 122 may further be configured to determine that coupling component 112 is coupled to user device 150 via connection/coupling 108 and that user device 150 is done charging, and in response operate wireless interface 120 to transmit a “done charging” signal 106 indicating user device 150 is done charging.
- “done charging” signal 106 may transmit a data packet that includes a message indicating user device 150 is done charging, the identifier (e.g., the device identifier of user device 150 and/or the user identifier), and/or a timestamp.
- processor 122 may operate data interface 114 of coupling component 112 or wireless interface 120 to receive location data from user device 150 determined by a location component such as a GPS 170 of user device 150 and store the location data in memory 124 .
- Processor 122 may then determine that coupling component 112 is not coupled to user device 150 as shown in FIG. 1A , and in response operate wireless interface 120 to transmit (e.g., broadcast) “available” signal 104 indicating charger device 110 is available to charge user device 150 and a geolocation of charger device 110 .
- “available” signal 104 may transmit a data packet that includes a message indicating charger device 110 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 coupled user device 150 that, includes location component 170 , and the location data stored in memory 124 may be updated each time user device 150 that includes location component 170 is coupled to charger device 110 .
- the location data received from one of user devices 150 may be used repeatedly for “available” signal 104 , for example, until charger device 110 is disconnected from (e.g., by unplugging from) external power source 190 and/or the location data is updated when charger device 110 is coupled to another user device 150 that includes location component 170 .
- charger device 110 includes its own location component that determines a geolocation to be included in “available” signal 104 as location data.
- location data may be provided by user 102 .
- user 102 may enter in a geolocation on user device 150 , which may be communicated to charger device 110 via data interface 114 of coupling component 112 or wireless interface 120 .
- the merchant or the service provider may program the location data into charger devices 110 .
- Providing a geolocation of charger device 110 in “available” signal 104 may be advantageous when charger device 110 is at a location that is not easily visible or when there are multiple charger devices 110 at a location. Also, providing a geolocation of charger device 110 in “available” signal 104 may be advantageous for charger devices 110 that are provided (e.g., for free or for a fee) at various public or private locations for use by many users 102 such as the general public. For example, charger stations or kiosks that provide charger devices 110 for a fee may be located in discrete places yet still allow users 102 to find the charger stations or kiosks when their user devices 150 needs to be charged.
- charger device 110 may include other components 126 , such as a network interface configured to communicate with a service provider server 130 and/or user device 150 over a network 180 (as shown in FIG. 3 ).
- other components may include a location component such as a GPS configured to determine a geolocation.
- other components 126 include charging circuitry configured to charge a battery 156 in user device 150 .
- charging circuitry is included in user device 150 , which is typical for user devices such as mobile phones.
- Each of one or more user devices 150 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.
- 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.
- HMD head-mounted display
- smartwatch a smartwatch
- User device 150 may include coupling component 152 , battery 156 , a network interface 158 , a wireless interface 160 , a processor 162 , a memory 164 , a display 166 , one or more motion sensor components 168 , location component such as GPS 170 , and/or other components 172 that are interconnected by a bus 174 or other communication mechanism for communicating information.
- Coupling component 152 in various embodiments, is configured to be coupled to charger device 110 via coupling component 112 of charger device 110 .
- Coupling component 152 may include a data interface 154 configured to communicate data to and from charger device 110 .
- coupling component 152 includes a connector (e.g., a micro-USBTM connector, a mini-USBTM connector, a LightningTM connector from Apple®, etc.), such as a plug or a receptacle, to be connected to coupling component 112 of charger device 110 .
- the connector may include one or more power pins configured to receive power from power supply components 116 via coupling component 112 .
- the connector may also include one or more data pins to provide data interface 154 for transmitting and receiving data.
- the connector may include one or more other pins such as a ground pin.
- coupling component 152 may include components to wirelessly couple to charger device 110 via coupling component 112 of charger device 110 .
- coupling component 152 may include an inductive coil to be inductively coupled to the inductive coil of charger device 110 .
- Coupling component 152 may convert the alternating electromagnetic field generated by the inductive coil of charger device 110 to electric current for charging battery 156 .
- Coupling component 152 may implement other techniques and mechanisms for wirelessly receiving power from charger device 110 , such as wireless conductive charging.
- Network interface 158 is configured to communicate with other devices or servers over network 180 .
- user device 150 may communicate with service provider server 130 via network interface 158 .
- network interface 158 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 with network 180 .
- network interface 158 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 with network 180 .
- DSL digital subscriber line
- PSTN public switched telephone network
- Network 180 may be implemented as a single network or a combination of multiple networks.
- network 180 may include the Internet and/or one or more intranets, landline networks, wireless networks, and/or other appropriate types of communication networks.
- network 108 may comprise a wireless telecommunications network (e.g., cellular phone network) adapted to communicate with other communication networks, such as the Internet.
- Wireless interface 160 in various embodiments, is configured to transmit and receive one or more signals including signal 104 and signal 106 , shown in FIG. 1A and FIG. 1B respectively.
- Wireless interface 160 may include a wireless communication component, such as a wireless transceiver for local wireless communications.
- Wireless interface 160 may receive one or more sequences of information via one or more signals 104 , 106 from wireless interface 120 of charger device 110 when within the range of wireless interface 120 .
- wireless interface 160 may include a Bluetooth® transceiver, such as a BLE transceiver, as further described above in relation to wireless interface 120 .
- wireless interface 160 may include a Wi-Fi® transceiver, a RF transceiver, an IR transceiver, or other wireless transceiver.
- signals 104 , 106 may be Bluetooth® signals such as BLE signals, Wi-Fi® signals, RF signals, IR signals, or other wireless signals.
- Processor 162 may include one or more microprocessors, microcontrollers, hardwired logic devices such as ASICs, PLDs such as FPGAs, or other processing systems.
- processor 162 may execute instructions stored on memory 164 or a non-transitory medium 174 which causes processor 162 to perform operations described herein.
- processor 162 may be configured to determine charger device 110 is available in response to wireless interface 160 receiving “available” signal 104 from charger device 110 when charger device 110 is not coupled and charger device is within broadcast range of charger device 110 .
- Processor 162 may provide a notification to charge user device 150 based on an amount of power remaining in battery 156 , activity data tracked by motion sensor components 168 , location data determined by location component 170 , and/or other information or data related to user 102 received from service provider server 130 .
- “available” signal 104 includes a geolocation of charger device and the notification may include the geolocation of charger device 110 , which may be displayed, for example, on a map.
- Display 166 is configured to display information to user 102 .
- Display 166 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.
- OLED organic light-emitting diode
- LCD liquid crystal display
- PDP plasma display panel
- CRT cathode ray tube
- Display 166 may further include an input component.
- display 166 may be a touchscreen display configured to present a graphical user interface (GUI) to user 102 and receive a user interaction with the GUI.
- GUI graphical user interface
- One or more motion sensors 168 are configured to detect (e.g., track, monitor, quantify, capture, measure, and/or otherwise detect) movement, such as activity of user 102 , to generate activity data, which may be stored in memory 164 and/or transmitted to service provider server 130 via network 180 .
- One or more motion sensors 168 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 of user 102 .
- Location component 170 determines a geolocation of user device 150 .
- 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.
- A-GPS assisted GPS
- 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.
- user device 150 may include other components 172 , such as charging circuitry configured to charge battery 156 using power received by coupling component 152 from charger device 110 .
- the charging circuitry may be included in charger device 110 .
- FIGS. 2A-C illustrate charger devices 210 , 230 , and 250 such as charger device 110 in FIGS. 1A-B , according to one or more embodiments of the present disclosure.
- charger device 210 may include coupling component 112 (in FIGS. 1A-B ) implemented as a connector such as plug 212 and a captive power cable 214 that is connected to plug 212 and fixedly attached to a housing 216 .
- Plug 212 may be removably connected to coupling component 152 (in FIGS. 1A-B ) of user device 150 , which may be implemented as a receptacle corresponding to plug 212 .
- Housing 216 may include various other components of charger device 210 , such as power supply components 116 , wireless interface 120 , and other components of charger device 110 shown in FIGS. 1A-B .
- Power supply components 116 of charger device 210 may include a power plug 218 or other connector provided on housing 216 to be plugged into an AC power outlet, such as external power source 190 (in FIGS. 1A-B ).
- charger device 230 may include coupling component 112 (in FIGS. 1A-B ) implemented as a connector such as a receptacle 232 .
- a power cable 234 that is connected to plug 236 on one side and plug 238 on the other side may be removably connected to a housing 240 by plugging plug 238 into receptacle 232 .
- Plug 236 may be removably connected to coupling component 152 (in FIGS. 1A-B ) of user device 150 , which may be implemented as a receptacle corresponding to plug 236 .
- Housing 240 may include various other components of charger device 230 , such as power supply components 116 , wireless interface 120 , and other components of charger device 110 shown in FIGS. 1A-B .
- Power supply components 116 of charger device 210 may include a power plug or other connector 242 provided on housing 212 to be plugged into an AC power outlet, such as external power source 190 (in FIGS. 1A-B ).
- charger device 250 may include coupling component 112 (in FIGS. 1A-B ) implemented as an inductive coil in a charging plate or dock 252 .
- a power cable 254 may connect, fixedly or removably, to charging plate 252 on one side and connect, fixedly or removeably, to a housing 256 on the other side.
- Various other components of charger device 250 such as power supply components 116 , wireless interface 120 , and other components of charger device 110 shown in FIGS. 1A-B may be provided in charging plate 252 , housing 256 , or distributed between charging plate 252 and housing 256 .
- Power supply components 116 of charger device 250 may include a power plug or other connector 258 provided on housing 256 to be plugged into an AC power outlet, such as external power source 190 (in FIGS. 1A-B ).
- Charger device 250 may use the inductive coil in charging plate 252 to generate an alternating electromagnetic field.
- Coupling component 152 of user device 150 (shown in FIGS. 1A-B ) may be implemented as a corresponding inductive coil. Accordingly, when inductive coil of user device 150 is coupled to the inductive coil of charger device 250 , for example, by placing user device 150 on or near charging plate 252 , the inductive coil of user device 150 converts power from the alternating electromagnetic field into electric current to charge a battery such as battery 156 of user device 150 (shown in FIGS. 1A-B ).
- FIG. 3 illustrates a block diagram of a networked system 300 according to one or more embodiments of the present disclosure.
- User device 150 may include any appropriate combination of hardware and/or software, including the various components of user device 150 shown in FIGS. 1A-B .
- One or more processors 162 may be configured to read and execute instructions stored on memory 164 or tangible non-transitory machine-readable medium 174 .
- user device 150 includes memory 164 and/or non-transitory machine-readable medium 174 that stores instructions that, when executed by one or more processors 162 , are adapted to cause user device 150 to perform specific tasks.
- the instructions may be executed by one or more processors 162 in response to interaction with user 102 .
- such instructions may include a browser application 352 such as a mobile browser application, which may be used to provide a user interface to permit user 102 to browse information available over network 180 , including information hosted by service provider server 130 .
- Browser application 352 may be implemented as a web browser to view information available over network 180 .
- Browser application 352 may include a GUI that is configured to allow user 102 to interface and communicate with service provider server 130 or other servers managed by content providers or merchants via network 180 .
- user 102 may be able to access websites to find and purchase items, as well as access user account information or web content.
- User device 150 may also include a charge management application 354 that notifies user 102 to charge user device 150 , notifies user 102 that charger device 110 is available, and/or that another user device 150 of user 102 that is plugged into charger device 110 is done charging.
- Charge management application 354 may determine whether to provide a notification to charge user device 150 based on receiving an “available” signal such as signal 104 (in FIG. 1A ) from charger device 110 and/or an amount of power remaining in battery 156 (shown in FIGS. 1A-B )
- Charge management application 354 may further determine whether to provide a notification based on accessing data in a database 360 , which may be stored in memory 164 (in FIGS. 1A-B ).
- charge management application 354 may determine whether to provide the notification based on activity data 364 tracked by motion sensor components 168 (in FIGS. 1A-B ), location data 366 determined by location component 170 (in FIGS. 1A-B ), and/or other information or data related to user 102 that may be in database 360 and/or received from service provider server 130 .
- Charge management application 354 may access one or more identifiers 362 in database 360 and transmit at least one of identifiers 362 to charger device 110 to be included in a “done charging” signal such as signal 106 (in FIG. 1B ) indicating user device 150 is done charging, which may be recognized by another user device 150 of user 102 .
- One or more identifiers 362 may include a device identifier such as a universally unique device identifier (UUID), a media access control (MAC) address/number, or other device identifier.
- UUID universally unique device identifier
- MAC media access control
- one or more identifiers 362 may include a user identifier, which may be associated with and/or stored in a user account 340 stored in a database 338 of service provider server 130 .
- Charge management application 354 may perform various other operations relating to charge management and notifications relating to charging user device 150 described herein.
- User device 150 may also include a payment application 356 that may be utilized by user 102 using user device 150 to make a payment.
- payment application 356 may be configured to make a payment using service provider server 130 as a payment processor.
- functionalities provided by charge management application 354 and payment application 356 may actually be provided by a single application.
- User device 150 may include one or more other applications 358 as may be desired in one or more embodiments to provide additional features available to user 102 , including accessing user account 340 stored in a database 338 of service provider server 130 .
- other applications 358 may include interfaces and communication protocols that allow the user to communicate information with service provider server 130 and other online sites via network 180 .
- Other applications 358 may also include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over network 180 or various other types of generally known programs and/or applications.
- Other applications 358 may include mobile applications downloaded and resident on user device 150 that enable user 102 to access content.
- Service provider server 130 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 charging user device 150 .
- Service provider server 130 may also be capable of processing online financial and information transactions on behalf of user 102 .
- Service provider server 130 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 charge user devices 150 for a fee using charger devices 110 at a charge station or kiosk.
- Service provider server 130 may include a charge management application 332 , which may be configured to interact with user device 150 via network 180 .
- charge management application 332 may maintain information and data related to user 102 , such as activity data 342 , in user account 340 stored in database 338 .
- Charge management application 332 may determine whether to notify user 102 to charge user device 150 in response to user device 150 receiving “available” signal 104 and based on at least a part of the information and data in user account 340 , and/or transmit at least a part of the information and data in user account 340 to user device 150 such that user device 150 may determine whether to notify user 102 to charge user device 150 in response to receiving “available” signal 104 .
- Charge management application 332 may perform various other operations relating to charge management and notifications relating to charging user device 150 described herein.
- Service provider server 130 may also include a payment application 334 that may facilitate processing payments, for example, from user 102 to a merchant or service provider.
- Payment application 334 may be configured to interface with payment application 356 to receive payment details, user information, merchant information, charger device information, and additional information for processing a payment on behalf of user 102 .
- payment application 334 may also be capable of interfacing with charger device 110 at a charge station or kiosk such that when user device 150 is coupled to charger device 110 , a payment may be authorized for use of charger device 110 to which user device 150 is coupled.
- functionalities provided by charge management application 332 and payment application 334 may actually be provided by a single application.
- Service provider server 130 may also include a database 338 that includes user accounts 340 including account information for users having an account with the service provider, such as user 102 .
- payment application 334 may process payments based on account information in user account 340 of database 338 .
- Service provider server 130 may include other applications 336 and may also be in communication with one or more external databases (not shown), that may provide additional information to be used by service provider server 130 .
- the one or more external databases may be databases maintained by third parties, and may include third party account information of user 102 .
- FIG. 4A illustrates a flow diagram of a process 400 for broadcasting signals such as signal 104 (in FIG. 1A ) by a charger device such as charger device 110 (in FIGS. 1A-B ), according to one or more embodiments of the present disclosure.
- charger device 110 receives power from an external power source such as external power source 190 (in FIGS. 1A-B ).
- an external power source such as external power source 190 (in FIGS. 1A-B ).
- a user such as user 102 (in FIGS. 1A-B ) may connect charger device 110 (e.g., by plugging in plug 218 , 242 , or 258 in FIGS. 2A-C ) to an AC power outlet.
- charger device 110 determines whether charger device 110 (e.g., using coupling component 112 in FIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 (in FIGS. 1A-B ).
- coupling component 112 includes a connector (e.g., plug 212 or receptacle 242 in FIGS. 2A-B ), and charger device 110 may determine that coupling component 112 is connected to user device 150 when plug 212 is plugged into a corresponding receptacle of user device 150 or receptacle 242 is connected to user device 150 (e.g., using a power cable such as power cable 234 and a plug such as plug 236 and 238 in FIG. 2B ).
- charger device 110 may determine a connection such as connection 108 (in FIG. 1B ) by detecting a power draw by user device 150 or an increased current flow.
- charger device 110 may determine connection 108 by detecting contact with user device 150 using a physical button or switch provided on plug 212 , receptacle 232 , or plug 236 .
- coupling component 112 includes an inductive coil in a charging plate 252
- charger device may determine that coupling component 112 is wirelessly coupled to user device 120 when user device 150 including a corresponding inductive coil is placed on or near charging plate 252 .
- charger device 110 may determine a coupling such as coupling 108 (in FIG. 1B ) by detecting user device 150 is within a charging range of charger device 110 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.
- RFID radio-frequency identification
- charger device 110 may include a proximity sensor to determine coupling 108 .
- charger device 110 may determine coupling 108 by detecting a power draw by user device 150 or change in current flow through the inductive coil. In a further example, charger device 110 may determine coupling 108 by detecting contact with user device 150 using a physical button or switch provided on charging plate 252 .
- charger device 110 broadcasts or otherwise transmits (e.g., via wireless interface 120 in FIGS. 1A-B ) an “available” signal such as signal 104 (in FIG. 1A ) indicating charger device 110 is available in response to determining that charger device 110 is not connected to or otherwise coupled to user device 150 .
- “available” signal 104 may include a message indicating charger device 110 is available and/or a timestamp.
- charger device 110 may broadcast or otherwise transmit “available” signal 104 indicating charger device 110 is available and also the location of charger device 110 in response to determining that charger device 110 is not connected to or otherwise coupled to user device 150 .
- “available” signal 104 may include a message indicating charger device 110 is available, the location data, and/or a timestamp.
- Charger device 110 may have received location data such as location data 366 (in FIG. 3 ) from user device 150 while it was previously connected to or otherwise coupled to user device 150 and have stored location data 366 in a memory such as memory 124 (in FIGS. 1A-B ).
- location data may be determined by a location component such as a GPS included in charger device 110 , or may be provided by a user such as user 102 (in FIGS. 1A-B ) (e.g., via user device 150 ).
- charger device 110 (e.g., via wireless interface 120 ) does not broadcast “available” signal 104 in response to determining that charger device 110 (e.g., using coupling component 112 ) is connected to or otherwise coupled to user device 150 .
- charger device 110 when user 102 connects charger device 110 (e.g., by plugging in plug 218 , 242 , or 258 in FIGS. 2A-C ) to an AC outlet, charger device starts broadcasting “available” signal 104 and continues broadcasting “available” signal 104 while charger device 110 is not connected to or otherwise coupled to user device 150 .
- charger device 110 e.g., by plugging in plug 212 or 236 in FIGS.
- charger device 110 stops broadcasting the “available signal.”
- charger device 110 resumes broadcasting “available” signal 104 , as shown in block 406 .
- FIG. 4B illustrates another flow diagram of a process 410 for broadcasting signals by a charger device, such as charger device 110 in FIGS. 1A-B , according to one or more embodiments of the present disclosure.
- charger device 110 receives power, as described above at block 402 .
- charger device 110 determines whether charger device 110 (e.g., using coupling component 112 in FIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 (in FIGS. 1A-B ), as described above at block 404 .
- charger device 110 broadcasts or otherwise transmits (e.g., via wireless interface 120 in FIGS. 1A-B ) an “available” signal such as signal 104 (in FIG. 1A ) in response to determining that charger device 110 is not connected to or otherwise coupled to user device 150 , as described above at block 406 .
- an “available” signal such as signal 104 (in FIG. 1A )
- charger device 110 (e.g., via wireless interface 120 ) does not broadcast or otherwise transmit “available” signal 104 in response to determining that charger device 110 is connected to or otherwise coupled to user device 150 while a battery such as battery 156 (in FIGS. 1A-B ) of user device 150 is being charged.
- charger device 110 determines whether user device 150 is done charging while still connected to or otherwise coupled to user device 150 . In response to determining a battery such as battery 156 (in FIGS. 1A-B ) of user device 150 is still being charged, charger device 110 does not transmit “available” signal, as shown at block 418 . In response to determining battery 156 of user device 150 is done being charged, charger device 110 transmits “available” signal, as shown at block 416 .
- battery 156 may be done being charged when battery 156 is fully charged. Alternatively, to extend the life of battery 156 and to optimize battery health, battery 156 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 of battery 156 or a fixed amount (e.g., 80%).
- charger device 110 may determine that battery 156 of user device 150 is done being charged, for example, by detecting a decrease or stop in power draw by user device 150 , detecting a decrease or stop in current flow, or no longer detecting contact with user device 150 using a physical button or switch provided on plug 212 , receptacle 232 , plug 236 , or charging plate 252 (in FIGS. 2A-C ). In other embodiments, charger device 110 may receive a communication from user device 150 indicating user device 150 is done charging via data interface 114 (in FIGS. 1A-B ) of coupling component 112 . In a further embodiment, charger device 110 may receive a wireless communication from user device 150 indicating user device 150 is done charging via wireless interface 120 .
- charger device 110 when user 102 connects charger device 110 (e.g., by plugging in plug 218 , 242 , or 258 in FIGS. 2A-C ) to an AC outlet, charger device starts broadcasting “available” signal 104 and continues broadcasting “available” signal 104 while charger device 110 is not connected to or otherwise coupled to user device 150 .
- charger device 110 stops broadcasting the “available signal.”
- charger device 110 resumes broadcasting “available” signal 104 .
- charger device 110 continues broadcasting “available” signal 104 , as shown in block 416 .
- FIG. 5 illustrates a flow diagram of a process 500 for broadcasting two or more types of signals such as one or more signals 104 , 106 (in FIGS. 1A-B ) by a charger device such as charger device 110 (in FIGS. 1A-B ), according to one or more embodiments of the present disclosure.
- charger device 110 receives power, as described above at 402 .
- charger device 110 determines whether charger device 110 (e.g., using coupling component 112 in FIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 a (in FIGS. 1A-B ), as described above at block 404 .
- charger device 110 broadcasts or otherwise transmits (e.g., via wireless interface 120 in FIGS. 1A-B ) an “available” signal such as signal 104 (in FIG. 1A ) in response to determining that charger device 110 is not connected to or otherwise coupled to user device 150 a , as described above at block 406 .
- an “available” signal such as signal 104 (in FIG. 1A )
- charger device 110 (e.g., via wireless interface 120 ) does not broadcast or otherwise transmit “available” signal 104 in response to determining that charger device 110 is connected to or otherwise coupled to user device 150 a while user device 150 a is charging.
- charger device 110 determines whether user device 150 a is done charging while still connected to or otherwise coupled to user device 150 a . In response to determining user device 150 a is still charging, charger device 110 (e.g., via wireless interface 120 ) does not broadcast or otherwise transmit “available” signal 104 , as shown at block 508 .
- charger device 110 in response to determining user device 150 a is done charging while still connected to or otherwise coupled to user device 150 a , charger device 110 (e.g., via wireless interface 120 ) broadcasts or otherwise transmits a “done charging” signal such as signal 106 (in FIG. 1B ) that includes an identifier such as identifier 362 (e.g., a device identifier or user identifier) received from user device 150 a indicating that user device 150 a is done charging.
- “done charging” signal 106 may include a message indicating user device 150 is done charging, at least one of identifiers 362 , and/or a timestamp.
- charger device 110 in response to determining user device 150 a is done charging, broadcasts or otherwise transmits “done charging” signal 106 and also “available” signal 104 .
- a process for generating and transmitting “done charging” signal 106 is further described below in relation to FIG. 6 .
- another user device of user 102 such as user device 150 b (in FIGS. 1A-B ) may receive “done charging” signal 106 and notify user 102 that user device 150 a is done charging, such as by providing a notification to user 102 on a display such as display 166 (in FIGS. 1A-B ) of user device 150 b .
- user device 150 a may be paired to, bonded to, linked with, or otherwise associated with user device 150 b .
- user device 150 a and user device 150 b may each share its identifier 362 , such as a device identifier (e.g., a UUID or MAC address/number), to the other device, and each device may store identifier 362 of the other device in its database 360 .
- a device identifier e.g., a UUID or MAC address/number
- user device 150 a may store identifier 362 of user device 150 b in its database 360
- user device 150 b may store identifier 362 of user device 150 a in its database 360 .
- user device 150 b may recognize identifier 362 contained in “done charging” signal 106 as identifier 362 of user device 150 a previously stored in database 360 of user device 150 b during pairing of user device 150 a and 150 b .
- user 102 receives the notification, user 102 is alerted that user device 150 a is done charging and may go disconnect or otherwise uncouple user device 150 a from charger device 110 .
- charger device 110 determines whether charger device 110 (e.g., using coupling component 112 in FIGS. 1A-B ) is disconnected from or otherwise uncoupled from user device 150 a , similarly as described above at block 402 .
- coupling component 112 includes a connector (e.g., plug 212 or receptacle 242 in FIGS. 2A-B ), and charger device 110 may determine that coupling component 112 is disconnected from user device 150 when 212 or 236 (in FIGS. 2A-B ) is unplugged from a corresponding receptacle of user device 150 or receptacle 242 is disconnected from user device 150 (e.g., using a power cable such as power cable 234 and a plug such as plug 236 and 238 in FIG. 2B ).
- charger device 110 may determine a connection such as connection 108 (in FIG. 1B ) is disconnected by detecting a stopped or decreased power draw or a stopped or decreased current flow.
- charger device 110 may determine connection 108 is disconnected by detecting removal of contact with user device 150 using a physical button or switch provided on plug 212 , receptacle 232 , or plug 236 .
- coupling component 112 includes an inductive coil in a charging plate 252
- charger device may determine that coupling component 112 is decoupled from user device 120 when user device 150 including a corresponding inductive coil is removed from on or near charging plate 252 .
- charger device 110 may determine a coupling such as coupling 108 (in FIG. 1B ) is decoupled by detecting user device 150 is removed from a charging range of charger device 110 using wireless communications, such as Bluetooth® communication, RFID communication, or other communication that may be used to determine or estimate distance between two devices.
- charger device 110 may include a proximity sensor to determine coupling 108 is decoupled.
- charger device 110 may determine coupling 108 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 device 110 may determine coupling 108 is decoupled by detecting removal of contact with user device 150 using a physical button or switch provided on charging plate 252 .
- charger device 110 in response to determining charger device 110 (e.g., using coupling component 112 ) is no longer connected to or otherwise coupled to user device 150 a , charger device 110 (e.g., via wireless interface 120 ) may broadcast or otherwise transmit “available” signal 104 and no longer broadcast or otherwise transmit “done charging” signal 106 .
- charger device In response to determining charger device 110 (e.g., using coupling component 112 ) is still coupled to user device 150 that is done charging, charger device continues transmitting “done charging” signal 106 and/or “available” signal 104 , as shown at block 512 .
- FIG. 6 illustrates a flow diagram of a process for generating and transmitting a signal by a charger device such as charger device 110 (in FIGS. 1A-B ) according to one or more embodiments of the present disclosure.
- charger device 110 may receive data from a user device such as user device 150 a (in FIGS. 1A-B ) while charger device 110 is connected to or otherwise coupled to user device 150 a .
- charger device 110 may request an identifier such as identifier 362 (e.g., a device identifier or user identifier) from user device 150 a at the time charger device 110 is connected to or otherwise coupled to user device, when user device 150 a is done charging, or anytime in between.
- Charger device 110 may receive identifier 362 from user device 150 a via a data interface such as data interface 114 (in FIGS. 1A-B ) included in a coupling component such as coupling component 112 (in FIGS. 1A-B ) used to connect charger device 110 to user device 150 .
- charger device 110 may receive identifier 362 from user device 150 a through wireless communications via a wireless interface such as wireless interface 120 (in FIGS. 1A-B ).
- charger device 110 At block 604 , charger device 110 generates a “done charging” signal such as signal 106 in FIG. 1B that includes identifier 362 received from user device 150 a.
- charger device 110 broadcasts or otherwise transmits “done charging” signal 106 indicating user device 150 a is done charging, as described above at block 512 .
- FIG. 7 illustrates a flow diagram of a process 700 for notifying a user such as user 102 (in FIGS. 1A-B ) to charge a user device such as user device 150 (in FIGS. 1A-B ) using a charger device such as charger device 110 (in FIGS. 1A-B ) according to one or more embodiments of the present disclosure.
- a service provider server such as service provider server 130 (in FIGS. 1A-B and FIG. 3 ) or user device 150 determines that charger device 110 is available in response to user device 150 receiving an “available” signal such as signal 104 (in FIG. 1A ).
- user device 150 may determine charger device 110 is available in response to receiving “available” signal 104 .
- user device 150 may communicate that charger device 110 is available to service provider server 130 in response to receiving “available” signal 104 . Based on such communication, service provider server 130 may determine charger device 110 is available in response to user device 150 receiving “available” signal 104 .
- service provider server 130 or user device 150 determines an amount of power in a battery such as battery 156 (in FIGS. 1A-B ).
- user device 150 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 by battery 156 to monitor the amount of power left, by measuring the internal impedance of battery 156 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.
- a coulomb counter to measure the amount of charge (e.g., in ampere hour, Ah) delivered or stored by battery 156 to monitor the amount of power left
- measuring the internal impedance of battery 156 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.
- user device 150 may communicate the amount of power left in battery 156 to service provider server 130 as part of the communication indicating charger device 110 is available at block 706 or in a separate communication. Based on such communication, service provider server 130 may determine the amount of power left in battery 156 , which may also be in response to user device 150 receiving “available” signal 104 .
- service provider server 130 or user device 150 may access activity data, such as activity data 342 in database 338 of service provider server 130 or activity data 364 in database 360 of user device 150 in response to user device 150 receiving “available” signal 104 .
- user device 150 may detect movement of user 102 to generate activity data 364 and store activity data in database 360 of user device.
- user device 150 may transmit activity data 364 to service provider server 130 to be stored as activity data 342 in user account 340 in database 338 .
- User device 150 may transmit activity data 364 to service provider server 130 by syncing activity data 364 with activity data 342 .
- user device 150 may transmit activity data 364 to service provider server 130 by periodically transmitting activity data 364 and/or by transmitting activity data 364 in response to receiving “available” signal 104 .
- user device 150 may access activity data 342 in database 338 in response to receiving “available” signal 104 .
- service provider server 130 may access activity data 342 in database 338 of service provider server 130 and/or activity data 364 in database 360 of user device 150 in response user device 150 to receiving “available” signal 104 .
- Activity data 364 or 342 may include recent activity indicating whether user 102 has been active and/or how active user 102 has been recently (e.g., in the past 5 minutes). Activity data 364 or 342 may also include activity history indicating whether user 102 is usually active at a certain time of day in general or whether user 102 is usually active at a certain time of day on certain days of the week.
- service provider server 130 or user device 150 may access a current time in response to user device 150 receiving “available” signal 104 .
- service provider server 130 or user device 150 may determine a geolocation of user device 150 in response to user device 150 receiving “available” signal 104 .
- user device 150 may use a location component such as location component 170 to determine the geolocation, which may be stored in database 360 as location data 366 .
- user device 150 may provide service provider server 130 with access to the geolocation determined by location component 170 and/or communicate the geolocation to service provider server 130 as part of the communication indicating charger device 110 is available at block 706 or in a separate communication. Based on such access or communication, service provider server 130 may determine the geolocation of user device 150 in response to user device 150 receiving “available” signal 104 .
- service provider server 130 or user device 150 may determine battery data including battery usage data and/or other battery-related data for a battery such as battery 156 of user device 150 in response to user device 150 receiving “available” signal 104 .
- user device 150 may include a battery management system and may access battery data from battery management system.
- user device 150 may communicate the battery data to service provider server 130 as part of the communication indicating charger device 110 is available at block 706 or in a separate communication. Based on such communication, service provider server 130 may determine the battery data in response to user device 150 receiving “available” signal 104 .
- service provider server 130 or user device 150 determines whether to notify user 102 to charge user device 150 based on user device 150 receiving “available” signal, the amount of power remaining in battery 156 , activity data 364 or 342 , time (e.g., time of the day or week), and/or geolocation. Service provider server 130 or user device 150 determines whether to notify user 102 to charge user device 150 further based on other conditions and/or factors.
- service provider server 130 or user device 150 may decide to notify user 102 to charge user device 150 when charger device 110 is available and the amount of power remaining in battery 156 is low.
- service provider server 130 or user device 150 may decide to notify user 102 to charge user device 150 when charger device 110 is available, the amount of power remaining in battery 156 is low, and activity data 364 or 342 indicates user 102 has not been active recently (e.g., within the past 5 minutes).
- activity data 364 or 342 indicates user 102 has not been active recently (e.g., within the past 5 minutes).
- user 102 has not been active recently, such as when user 102 is lounging and watching television, user 102 presumably does not need user device 150 at the moment.
- service provider server 130 or user device 150 may decide to notify user 102 to charge user device 150 when charger device 110 is available, the amount of power remaining in battery 156 is low, activity data 364 or 342 indicates user 102 has not been active recently, and further activity data 364 or 342 indicates user 102 is usually not active at the time of the day or week.
- service provider server 130 or user device 150 may determine user device 150 requires charging by forecasting how much power user device 150 requires to get through the day (e.g., until night time when user 102 usually gets home) or to get through a time period in which user 102 does not have access to charger device 110 , such as during a commute (e.g., from home to work or vice versa), based on the battery usage data.
- Service provider server 130 or user device 150 may decide to notify user 102 to charge user device 150 when charger device 110 is available and user device 150 requires charging based on the battery usage data.
- Service provider server 130 or user device 150 may determine whether to notify user 102 to charge user device 150 in response to other combinations of such conditions and/or factors.
- user device 150 presents a notification on a display such as display 166 (in FIGS. 1A-B ).
- the notification may include a message prompting user 102 to charge user device 150 and/or indicate charger device 110 is available.
- the notification may include a distance to charger device 110 .
- User device 150 may determine the distance between user device 150 and charger device 110 based on “available” signal 104 (e.g., using a timestamp included in “available” signal 104 ).
- the notification may further include a geolocation of charger device 110 (e.g., presented on a map).
- FIG. 8 illustrates a charge station or kiosk 800 including multiple charger devices 110 a - e according to one or more embodiments of the present disclosure.
- charging station 800 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 users 102 (in FIGS. 1A-B ), may want to charge their user devices such as user device 150 (in FIGS. 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 station 800 does not require such a payment device, as each of charger devices 110 a - e is configured to interact with user device 150 to allow service provider server 130 to process payment for providing power for charging user device 150 .
- charger device 110 e transmits to user device 150 a charger device identifier to user device 150 via a data interface such as data interface 154 (in FIGS. 1A-B ).
- User device 150 may transmit the charger device identifier and an identifier such as identifier 362 (e.g., a device identifier or user identifier) from user device 150 to service provider server 130 .
- the charger device identifier may be associated with an account of a merchant or service provider that is charging fees for providing power through charger devices 110 a - e .
- Identifier 362 may be associated with user account 340 in database 338 of service provider server 130 .
- Service provider server 130 may process a payment from user account 340 to the account of the merchant or service provider using the charger device identifier and identifier 362 .
- charger device 110 e receives identifier 362 from user device 150 and transmits identifier 362 and a charger device identifier to service provider server 130 over network 180 .
- Service provider server 130 may process a payment from user account 340 to the account of the merchant or service provider using the charger device identifier and identifier 362 .
- FIG. 9 illustrates a flow diagram of a process for processing a payment for charging a user device such as user device 150 (in FIGS. 1A-B ) of a user such as user 102 (in FIGS. 1A-B ) by a charger device such as charger device 110 (in FIGS. 1A-B ) according to one or more embodiments of the present disclosure.
- service provider server 130 may receive from charger device 110 or user device 150 , via network 180 , a communication including an identifier such as identifier 362 (e.g., a device identifier or user identifier) and a charger device identifier, as described above in relation to FIG. 8 .
- identifier 362 e.g., a device identifier or user identifier
- charger device identifier as described above in relation to FIG. 8 .
- service provider server 130 may determine a user account such as user account 340 of user 102 based on identifier 362 .
- identifier 362 may be a user identifier associated with user account 340 .
- Service provider server 130 may also determine an account of a merchant or service provider that is to receive the payment for providing power through charger device 110 for charging user device 150 based on charger device identifier.
- charger device identifier may be associated with the account of the merchant or service provider.
- service provider server may transmit to user device a notification regarding payment for providing power for charging user device 150 .
- the notification may indicate the fee per time charger device 110 is used, or the fee per amount of charge (e.g., in Ah) delivered, or a fee for fully charging user device 150 .
- the notification may include an accept button or other GUI elements that user 102 may interact with to authorize or decline payment for charging user device 150 .
- service provider server 130 may receive an authorization from user 102 in response to user 102 providing authorization on user device 150 , such as by touching the accept button in the notification.
- service provider server 130 receives from charger device 110 or user device 150 , via network 180 , a communication indicating user device 150 is done charging or has been disconnected.
- service provider server 130 processes payment from user account 140 to the account of the merchant or service provider for providing power to user device 150 based on the fee authorized by user 102 and/or the amount of charge provided to user device 150 .
- FIG. 10 illustrates a block diagram of a computer system 1000 for implementing, for example, a charger device such as charger device 110 , service provider server such as service provider server 130 , and one or more user device such as one or more user devices 150 in FIGS. 1A-B and FIG. 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 as computer system 1000 in a manner as follows.
- computer system 1000 such as a computer and/or a network server, includes a bus 1002 or other communication mechanism for communicating information, which interconnects subsystems and components, such as a processing component 1004 (e.g., processor, micro-controller, digital signal processor (DSP), etc.), a system memory component 1006 (e.g., RAM), a static storage component 1008 (e.g., ROM), a disk drive component 1010 (e.g., magnetic or optical), a network interface component 1012 (e.g., modem or Ethernet card), a display component 1014 (e.g., LED display component, OLED display component, LCD component, PDP component, CRT display component, or other display component), an input component 1016 (e.g., keyboard, keypad, virtual keyboard, touchscreen, etc.), a cursor control component 1018 (e.g., mouse, pointer, trackball, etc.), and/or a location determination component 1020 (e.g., a processing component 1004 (e.g., processor
- computer system 1000 performs specific operations by processing component 1004 executing one or more sequences of instructions contained in memory component 1006 , such as described herein with respect to charger device 110 , service provider server 130 , and one or more user devices 150 .
- Such instructions may be read into system memory component 1006 from another computer readable medium, such as static storage component 1008 or disk drive component 1010 .
- static storage component 1008 or disk drive component 1010 may be used in place of, or in combination with, software instructions to implement the present disclosure.
- Non-volatile media includes optical or magnetic disks, such as disk drive component 1010
- volatile media includes dynamic memory, such as system memory component 1006
- transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 1002 .
- transmission media may take the form of acoustic or light waves, such as those generated during radio wave and IR data communications.
- 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.
- execution of instruction sequences to practice the present disclosure may be performed by computer system 1000 .
- a plurality of computer systems 1000 coupled by a communication link 1022 to a network 1024 such as network 180 in FIGS. 1A-B and FIG. 3 may perform instruction sequences to practice the present disclosure in coordination with one another.
- Computer system 1000 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) through communication link 1022 and network interface component 1012 .
- Network interface component 1012 may include an antenna, either separate or integrated, to enable transmission and reception via communication link 1022 .
- Received program code may be executed by processing component 1004 as received and/or stored in disk drive component 1010 or some other non-volatile storage component for execution.
- charger device 110 service provider server 130 , and one or more user devices 150 of FIGS. 1A-B and FIG. 3
- the various aspects of such devices and servers illustrated in FIGS. 1A-B and FIG. 3 may be distributed among a plurality of servers, devices, and/or other entities.
- various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software.
- 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.
- 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.
- 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.
Landscapes
- Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Charge And Discharge Circuits For Batteries Or The Like (AREA)
Abstract
Description
- 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.
- The present disclosure relates to electronic charging devices and, more particularly, to electronic charging devices configured to communicate with other devices.
- 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.
-
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.
- 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 diagrams 100 of acharger device 110 and one ormore user devices 150, such as user devices 150 a and 150 b, of auser 102, according to one or more embodiments of the present disclosure. -
Charger device 110 may include acoupling component 112,power supply components 116, a wireless transceiver orother wireless interface 120, aprocessor 122, amemory 124, and/orother components 126 that are interconnected by a bus 128 or other communication mechanism for communicating information between the various components. -
Coupling component 112, in various embodiments, is configured to be connected to or otherwise coupled touser device 150 via acoupling component 152 ofuser device 150.Coupling component 112 may include adata interface 114 configured to communicate data to and fromuser device 150. - In some embodiments,
coupling component 112 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 device 150. The connector may include one or more power pins configured to chargeuser device 150 by delivering power received frompower supply components 116 touser device 150. The connector may also include one or more data pins to provide data interface 114 for transmitting and receiving data. The connector may include one or more other pins such as a ground pin. - Alternatively,
coupling component 112 includes components to wirelessly couple touser device 150 viacoupling component 152 ofuser device 150. For example,coupling component 112 may include an inductive coil to be inductively coupled to a corresponding inductive coil incoupling component 152 and provide an alternating electromagnetic field for charginguser device 150.Coupling component 112 may implement other techniques and mechanisms for wirelessly delivering power touser device 150, such as wireless conductive charging. -
Power supply components 116, in various embodiments, deliver power tocoupling component 112. In some embodiments,power supply components 116 may includepower adapter components 118 that convert alternating current (AC) received from anexternal power source 190, such as an AC power outlet, to direct current (DC) whilecharger device 110 is connected to (e.g., by plugging into)external power source 190.Power adapter components 118 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 source 190. 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 components 116 may include a battery (e.g., a portable battery) that provides power tocoupling component 112. The battery may receive AC power fromexternal power source 190 and be charged whencharger device 110 is connected toexternal power source 190. -
Wireless interface 120, in various embodiments, is configured to transmit (e.g., broadcast) and/or receive one or moresignals including signal 104 and signal 106 shown inFIG. 1A andFIG. 1B respectively.Wireless interface 120 may include a wireless communication component, such as a wireless transmitter or a wireless transceiver for local wireless communications.Wireless interface 120 may transmit one or more sequences of information via one ormore signals user device 150 capable of receiving information fromwireless interface 120 comes within a communication range ofwireless interface 120, the device may receive a communication fromwireless interface 120 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 interface 120 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 interface 120 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 interface 120 that is implemented, signals 104 and 106 may be Bluetooth® signals such as BLE signals, RF signals, IR signals, or other wireless signals. -
Processor 122, 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,processor 122 may execute instructions stored onmemory 124 which causesprocessor 122 to perform operations described herein. In other embodiments,processor 122 may be hardwired to perform the operations described herein. - As shown in
FIG. 1A ,processor 122 may be configured to determine thatcoupling component 112 is not coupled touser device 150, and in response operatewireless interface 120 to transmit (e.g., broadcast) an “available”signal 104 indicatingcharger device 110 is available to chargeuser device 150. For example, “available”signal 104 may transmit a data packet that includes a message indicatingcharger device 110 is available and/or a timestamp. - As shown in
FIG. 1B ,processor 122 may be configured to determine thatcoupling component 112 is coupled touser device 150 via a connection orother coupling 108, and in response operatewireless interface 120 to not transmit an “available” signal (e.g., “available”signal 104 shown inFIG. 1A ).Processor 122 may operate data interface 114 ofcoupling component 112 orwireless interface 120 to receive an identifier such as the device identifier ofuser device 150 and/or a user identifier fromuser device 150, and may store the identifier inmemory 124.Processor 122 may further be configured to determine thatcoupling component 112 is coupled touser device 150 via connection/coupling 108 and thatuser device 150 is done charging, and in response operatewireless interface 120 to transmit a “done charging”signal 106 indicatinguser device 150 is done charging. For example, “done charging”signal 106 may transmit a data packet that includes a message indicatinguser device 150 is done charging, the identifier (e.g., the device identifier ofuser device 150 and/or the user identifier), and/or a timestamp. - In some embodiments, while
charger device 110 is coupled touser device 150 via connection orother coupling 108 as shown inFIG. 1B ,processor 122 may operate data interface 114 ofcoupling component 112 orwireless interface 120 to receive location data fromuser device 150 determined by a location component such as aGPS 170 ofuser device 150 and store the location data inmemory 124.Processor 122 may then determine thatcoupling component 112 is not coupled touser device 150 as shown inFIG. 1A , and in response operatewireless interface 120 to transmit (e.g., broadcast) “available”signal 104 indicatingcharger device 110 is available to chargeuser device 150 and a geolocation ofcharger device 110. For example, “available”signal 104 may transmit a data packet that includes a message indicatingcharger device 110 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 coupled
user device 150 that, includeslocation component 170, and the location data stored inmemory 124 may be updated eachtime user device 150 that includeslocation component 170 is coupled tocharger device 110. The location data received from one ofuser devices 150 may be used repeatedly for “available”signal 104, for example, untilcharger device 110 is disconnected from (e.g., by unplugging from)external power source 190 and/or the location data is updated whencharger device 110 is coupled to anotheruser device 150 that includeslocation component 170. - In further embodiments,
charger device 110 includes its own location component that determines a geolocation to be included in “available”signal 104 as location data. In yet further embodiments, location data may be provided byuser 102. For example,user 102 may enter in a geolocation onuser device 150, which may be communicated tocharger device 110 viadata interface 114 ofcoupling component 112 orwireless interface 120. In another example, forcharger devices 110 at a charging station or kiosk wherecharger devices 110 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 devices 110. - Providing a geolocation of
charger device 110 in “available”signal 104 may be advantageous whencharger device 110 is at a location that is not easily visible or when there aremultiple charger devices 110 at a location. Also, providing a geolocation ofcharger device 110 in “available”signal 104 may be advantageous forcharger devices 110 that are provided (e.g., for free or for a fee) at various public or private locations for use bymany users 102 such as the general public. For example, charger stations or kiosks that providecharger devices 110 for a fee may be located in discrete places yet still allowusers 102 to find the charger stations or kiosks when theiruser devices 150 needs to be charged. - In one or more embodiments,
charger device 110 may includeother components 126, such as a network interface configured to communicate with aservice provider server 130 and/oruser device 150 over a network 180 (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 components 126 include charging circuitry configured to charge abattery 156 inuser device 150. In other embodiments, charging circuitry is included inuser device 150, which is typical for user devices such as mobile phones. - Each of one or
more user devices 150, such as user devices 150 a and 150 b, 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 device 150 may includecoupling component 152,battery 156, anetwork interface 158, awireless interface 160, aprocessor 162, amemory 164, adisplay 166, one or moremotion sensor components 168, location component such asGPS 170, and/orother components 172 that are interconnected by abus 174 or other communication mechanism for communicating information. -
Coupling component 152, in various embodiments, is configured to be coupled tocharger device 110 viacoupling component 112 ofcharger device 110.Coupling component 152 may include adata interface 154 configured to communicate data to and fromcharger device 110. - In some embodiments,
coupling component 152 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 component 112 ofcharger device 110. The connector may include one or more power pins configured to receive power frompower supply components 116 viacoupling component 112. The connector may also include one or more data pins to provide data interface 154 for transmitting and receiving data. The connector may include one or more other pins such as a ground pin. - Alternatively,
coupling component 152 may include components to wirelessly couple tocharger device 110 viacoupling component 112 ofcharger device 110. For example,coupling component 152 may include an inductive coil to be inductively coupled to the inductive coil ofcharger device 110.Coupling component 152 may convert the alternating electromagnetic field generated by the inductive coil ofcharger device 110 to electric current for chargingbattery 156.Coupling component 152 may implement other techniques and mechanisms for wirelessly receiving power fromcharger device 110, such as wireless conductive charging. -
Network interface 158, in various embodiments, is configured to communicate with other devices or servers overnetwork 180. For example,user device 150 may communicate withservice provider server 130 vianetwork interface 158. In some embodiments,network interface 158 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 withnetwork 180. In some embodiments,network interface 158 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 withnetwork 180. -
Network 180, in various embodiments, may be implemented as a single network or a combination of multiple networks. For example,network 180 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,network 108 may comprise a wireless telecommunications network (e.g., cellular phone network) adapted to communicate with other communication networks, such as the Internet. -
Wireless interface 160, in various embodiments, is configured to transmit and receive one or moresignals including signal 104 and signal 106, shown inFIG. 1A andFIG. 1B respectively.Wireless interface 160 may include a wireless communication component, such as a wireless transceiver for local wireless communications.Wireless interface 160 may receive one or more sequences of information via one ormore signals wireless interface 120 ofcharger device 110 when within the range ofwireless interface 120. In some embodiments,wireless interface 160 may include a Bluetooth® transceiver, such as a BLE transceiver, as further described above in relation towireless interface 120. In other embodiments,wireless interface 160 may include a Wi-Fi® transceiver, a RF transceiver, an IR transceiver, or other wireless transceiver. Corresponding to the type ofwireless interface 160 that is implemented, signals 104, 106 may be Bluetooth® signals such as BLE signals, Wi-Fi® signals, RF signals, IR signals, or other wireless signals. -
Processor 162, 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,processor 162 may execute instructions stored onmemory 164 or a non-transitory medium 174 which causesprocessor 162 to perform operations described herein. - As shown in
FIG. 1A ,processor 162 may be configured to determinecharger device 110 is available in response towireless interface 160 receiving “available”signal 104 fromcharger device 110 whencharger device 110 is not coupled and charger device is within broadcast range ofcharger device 110.Processor 162 may provide a notification to chargeuser device 150 based on an amount of power remaining inbattery 156, activity data tracked bymotion sensor components 168, location data determined bylocation component 170, and/or other information or data related touser 102 received fromservice provider server 130. In some embodiments, “available”signal 104 includes a geolocation of charger device and the notification may include the geolocation ofcharger device 110, which may be displayed, for example, on a map. -
Display 166, in various embodiments, is configured to display information touser 102.Display 166 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.Display 166 may further include an input component. For example,display 166 may be a touchscreen display configured to present a graphical user interface (GUI) touser 102 and receive a user interaction with the GUI. - One or
more motion sensors 168, in various embodiments, are configured to detect (e.g., track, monitor, quantify, capture, measure, and/or otherwise detect) movement, such as activity ofuser 102, to generate activity data, which may be stored inmemory 164 and/or transmitted toservice provider server 130 vianetwork 180. One ormore motion sensors 168 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 ofuser 102. -
Location component 170, in various embodiments, determines a geolocation ofuser device 150. 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 device 150 may includeother components 172, such as charging circuitry configured to chargebattery 156 using power received bycoupling component 152 fromcharger device 110. In other embodiments, the charging circuitry may be included incharger device 110. -
FIGS. 2A-C illustratecharger devices charger device 110 inFIGS. 1A-B , according to one or more embodiments of the present disclosure. - As shown in
FIG. 2A ,charger device 210 may include coupling component 112 (inFIGS. 1A-B ) implemented as a connector such asplug 212 and acaptive power cable 214 that is connected to plug 212 and fixedly attached to ahousing 216. Plug 212 may be removably connected to coupling component 152 (inFIGS. 1A-B ) ofuser device 150, which may be implemented as a receptacle corresponding to plug 212.Housing 216 may include various other components ofcharger device 210, such aspower supply components 116,wireless interface 120, and other components ofcharger device 110 shown inFIGS. 1A-B .Power supply components 116 ofcharger device 210 may include apower plug 218 or other connector provided onhousing 216 to be plugged into an AC power outlet, such as external power source 190 (inFIGS. 1A-B ). - As shown in
FIG. 2B ,charger device 230 may include coupling component 112 (inFIGS. 1A-B ) implemented as a connector such as areceptacle 232. Apower cable 234 that is connected to plug 236 on one side and plug 238 on the other side may be removably connected to ahousing 240 by pluggingplug 238 intoreceptacle 232. Plug 236 may be removably connected to coupling component 152 (inFIGS. 1A-B ) ofuser device 150, which may be implemented as a receptacle corresponding to plug 236.Housing 240 may include various other components ofcharger device 230, such aspower supply components 116,wireless interface 120, and other components ofcharger device 110 shown inFIGS. 1A-B .Power supply components 116 ofcharger device 210 may include a power plug orother connector 242 provided onhousing 212 to be plugged into an AC power outlet, such as external power source 190 (inFIGS. 1A-B ). - As shown in
FIG. 2C ,charger device 250 may include coupling component 112 (inFIGS. 1A-B ) implemented as an inductive coil in a charging plate ordock 252. Apower cable 254 may connect, fixedly or removably, to chargingplate 252 on one side and connect, fixedly or removeably, to ahousing 256 on the other side. Various other components ofcharger device 250, such aspower supply components 116,wireless interface 120, and other components ofcharger device 110 shown inFIGS. 1A-B may be provided in chargingplate 252,housing 256, or distributed between chargingplate 252 andhousing 256.Power supply components 116 ofcharger device 250 may include a power plug orother connector 258 provided onhousing 256 to be plugged into an AC power outlet, such as external power source 190 (inFIGS. 1A-B ). -
Charger device 250 may use the inductive coil in chargingplate 252 to generate an alternating electromagnetic field.Coupling component 152 of user device 150 (shown inFIGS. 1A-B ) may be implemented as a corresponding inductive coil. Accordingly, when inductive coil ofuser device 150 is coupled to the inductive coil ofcharger device 250, for example, by placinguser device 150 on or near chargingplate 252, the inductive coil ofuser device 150 converts power from the alternating electromagnetic field into electric current to charge a battery such asbattery 156 of user device 150 (shown inFIGS. 1A-B ). -
FIG. 3 illustrates a block diagram of anetworked system 300 according to one or more embodiments of the present disclosure. -
User device 150 may include any appropriate combination of hardware and/or software, including the various components ofuser device 150 shown inFIGS. 1A-B . One ormore processors 162 may be configured to read and execute instructions stored onmemory 164 or tangible non-transitory machine-readable medium 174. In one or more embodiments,user device 150 includesmemory 164 and/or non-transitory machine-readable medium 174 that stores instructions that, when executed by one ormore processors 162, are adapted to causeuser device 150 to perform specific tasks. In some embodiments, the instructions may be executed by one ormore processors 162 in response to interaction withuser 102. For example, such instructions may include abrowser application 352 such as a mobile browser application, which may be used to provide a user interface to permituser 102 to browse information available overnetwork 180, including information hosted byservice provider server 130.Browser application 352 may be implemented as a web browser to view information available overnetwork 180.Browser application 352 may include a GUI that is configured to allowuser 102 to interface and communicate withservice provider server 130 or other servers managed by content providers or merchants vianetwork 180. For example,user 102 may be able to access websites to find and purchase items, as well as access user account information or web content. -
User device 150 may also include acharge management application 354 that notifiesuser 102 to chargeuser device 150, notifiesuser 102 thatcharger device 110 is available, and/or that anotheruser device 150 ofuser 102 that is plugged intocharger device 110 is done charging.Charge management application 354 may determine whether to provide a notification to chargeuser device 150 based on receiving an “available” signal such as signal 104 (inFIG. 1A ) fromcharger device 110 and/or an amount of power remaining in battery 156 (shown inFIGS. 1A-B )Charge management application 354 may further determine whether to provide a notification based on accessing data in adatabase 360, which may be stored in memory 164 (inFIGS. 1A-B ). For example,charge management application 354 may determine whether to provide the notification based onactivity data 364 tracked by motion sensor components 168 (inFIGS. 1A-B ),location data 366 determined by location component 170 (inFIGS. 1A-B ), and/or other information or data related touser 102 that may be indatabase 360 and/or received fromservice provider server 130. -
Charge management application 354 may access one ormore identifiers 362 indatabase 360 and transmit at least one ofidentifiers 362 tocharger device 110 to be included in a “done charging” signal such as signal 106 (inFIG. 1B ) indicatinguser device 150 is done charging, which may be recognized by anotheruser device 150 ofuser 102. One ormore identifiers 362 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 identifiers 362 may include a user identifier, which may be associated with and/or stored in a user account 340 stored in adatabase 338 ofservice provider server 130.Charge management application 354 may perform various other operations relating to charge management and notifications relating to charginguser device 150 described herein. -
User device 150 may also include apayment application 356 that may be utilized byuser 102 usinguser device 150 to make a payment. In some embodiments,payment application 356 may be configured to make a payment usingservice provider server 130 as a payment processor. In some embodiments, functionalities provided bycharge management application 354 andpayment application 356 may actually be provided by a single application. -
User device 150 may include one or moreother applications 358 as may be desired in one or more embodiments to provide additional features available touser 102, including accessing user account 340 stored in adatabase 338 ofservice provider server 130. For example,other applications 358 may include interfaces and communication protocols that allow the user to communicate information withservice provider server 130 and other online sites vianetwork 180.Other applications 358 may also include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) overnetwork 180 or various other types of generally known programs and/or applications.Other applications 358 may include mobile applications downloaded and resident onuser device 150 that enableuser 102 to access content. -
Service provider server 130, 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 device 150.Service provider server 130 may also be capable of processing online financial and information transactions on behalf ofuser 102.Service provider server 130 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 devices 150 for a fee usingcharger devices 110 at a charge station or kiosk. -
Service provider server 130 may include acharge management application 332, which may be configured to interact withuser device 150 vianetwork 180. In some embodiments,charge management application 332 may maintain information and data related touser 102, such asactivity data 342, in user account 340 stored indatabase 338.Charge management application 332 may determine whether to notifyuser 102 to chargeuser device 150 in response touser device 150 receiving “available”signal 104 and based on at least a part of the information and data in user account 340, and/or transmit at least a part of the information and data in user account 340 touser device 150 such thatuser device 150 may determine whether to notifyuser 102 to chargeuser device 150 in response to receiving “available”signal 104.Charge management application 332 may perform various other operations relating to charge management and notifications relating to charginguser device 150 described herein. -
Service provider server 130 may also include apayment application 334 that may facilitate processing payments, for example, fromuser 102 to a merchant or service provider.Payment application 334 may be configured to interface withpayment application 356 to receive payment details, user information, merchant information, charger device information, and additional information for processing a payment on behalf ofuser 102. In some embodiments,payment application 334 may also be capable of interfacing withcharger device 110 at a charge station or kiosk such that whenuser device 150 is coupled tocharger device 110, a payment may be authorized for use ofcharger device 110 to whichuser device 150 is coupled. In some embodiments, functionalities provided bycharge management application 332 andpayment application 334 may actually be provided by a single application. -
Service provider server 130 may also include adatabase 338 that includes user accounts 340 including account information for users having an account with the service provider, such asuser 102. In some embodiments,payment application 334 may process payments based on account information in user account 340 ofdatabase 338.Service provider server 130 may includeother applications 336 and may also be in communication with one or more external databases (not shown), that may provide additional information to be used byservice provider server 130. In some embodiments, the one or more external databases may be databases maintained by third parties, and may include third party account information ofuser 102. -
FIG. 4A illustrates a flow diagram of aprocess 400 for broadcasting signals such as signal 104 (inFIG. 1A ) by a charger device such as charger device 110 (inFIGS. 1A-B ), according to one or more embodiments of the present disclosure. - At
block 402,charger device 110 receives power from an external power source such as external power source 190 (inFIGS. 1A-B ). For example, a user such as user 102 (inFIGS. 1A-B ) may connect charger device 110 (e.g., by plugging inplug FIGS. 2A-C ) to an AC power outlet. - At
block 404,charger device 110 determines whether charger device 110 (e.g., usingcoupling component 112 inFIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 (inFIGS. 1A-B ). - In some embodiments,
coupling component 112 includes a connector (e.g., plug 212 orreceptacle 242 inFIGS. 2A-B ), andcharger device 110 may determine thatcoupling component 112 is connected touser device 150 whenplug 212 is plugged into a corresponding receptacle ofuser device 150 orreceptacle 242 is connected to user device 150 (e.g., using a power cable such aspower cable 234 and a plug such asplug FIG. 2B ). For example,charger device 110 may determine a connection such as connection 108 (inFIG. 1B ) by detecting a power draw byuser device 150 or an increased current flow. In another example,charger device 110 may determineconnection 108 by detecting contact withuser device 150 using a physical button or switch provided onplug 212,receptacle 232, or plug 236. - In other embodiments,
coupling component 112 includes an inductive coil in acharging plate 252, and charger device may determine thatcoupling component 112 is wirelessly coupled touser device 120 whenuser device 150 including a corresponding inductive coil is placed on or near chargingplate 252. For example,charger device 110 may determine a coupling such as coupling 108 (inFIG. 1B ) by detectinguser device 150 is within a charging range ofcharger device 110 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 device 110 may include a proximity sensor to determinecoupling 108. In a further example,charger device 110 may determine coupling 108 by detecting a power draw byuser device 150 or change in current flow through the inductive coil. In a further example,charger device 110 may determine coupling 108 by detecting contact withuser device 150 using a physical button or switch provided on chargingplate 252. - At
block 406,charger device 110 broadcasts or otherwise transmits (e.g., viawireless interface 120 inFIGS. 1A-B ) an “available” signal such as signal 104 (inFIG. 1A ) indicatingcharger device 110 is available in response to determining thatcharger device 110 is not connected to or otherwise coupled touser device 150. For example, “available”signal 104 may include a message indicatingcharger device 110 is available and/or a timestamp. - In some embodiments,
charger device 110 may broadcast or otherwise transmit “available”signal 104 indicatingcharger device 110 is available and also the location ofcharger device 110 in response to determining thatcharger device 110 is not connected to or otherwise coupled touser device 150. For example, “available”signal 104 may include a message indicatingcharger device 110 is available, the location data, and/or a timestamp.Charger device 110 may have received location data such as location data 366 (inFIG. 3 ) fromuser device 150 while it was previously connected to or otherwise coupled touser device 150 and have storedlocation data 366 in a memory such as memory 124 (inFIGS. 1A-B ). Alternatively, location data may be determined by a location component such as a GPS included incharger device 110, or may be provided by a user such as user 102 (inFIGS. 1A-B ) (e.g., via user device 150). - At
block 408, charger device 110 (e.g., via wireless interface 120) does not broadcast “available”signal 104 in response to determining that charger device 110 (e.g., using coupling component 112) is connected to or otherwise coupled touser device 150. - In an example, when
user 102 connects charger device 110 (e.g., by plugging inplug FIGS. 2A-C ) to an AC outlet, charger device starts broadcasting “available”signal 104 and continues broadcasting “available”signal 104 whilecharger device 110 is not connected to or otherwise coupled touser device 150. Whenuser 102 connects charger device 110 (e.g., by plugging inplug FIGS. 2A-B ) touser device 150,charger device 110 stops broadcasting the “available signal.” Whenuser 102 subsequently disconnects charger device 110 (e.g., by unpluggingplug 212 or 236) fromuser device 150, which may be afteruser device 150 is done charging or only partially charged,charger device 110 resumes broadcasting “available”signal 104, as shown inblock 406. -
FIG. 4B illustrates another flow diagram of aprocess 410 for broadcasting signals by a charger device, such ascharger device 110 inFIGS. 1A-B , according to one or more embodiments of the present disclosure. - At
block 412,charger device 110 receives power, as described above atblock 402. - At
block 414,charger device 110 determines whether charger device 110 (e.g., usingcoupling component 112 inFIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 (inFIGS. 1A-B ), as described above atblock 404. - At
block 416,charger device 110 broadcasts or otherwise transmits (e.g., viawireless interface 120 inFIGS. 1A-B ) an “available” signal such as signal 104 (inFIG. 1A ) in response to determining thatcharger device 110 is not connected to or otherwise coupled touser device 150, as described above atblock 406. - At
block 418, charger device 110 (e.g., via wireless interface 120) does not broadcast or otherwise transmit “available”signal 104 in response to determining thatcharger device 110 is connected to or otherwise coupled touser device 150 while a battery such as battery 156 (inFIGS. 1A-B ) ofuser device 150 is being charged. - At
block 420,charger device 110 determines whetheruser device 150 is done charging while still connected to or otherwise coupled touser device 150. In response to determining a battery such as battery 156 (inFIGS. 1A-B ) ofuser device 150 is still being charged,charger device 110 does not transmit “available” signal, as shown atblock 418. In response to determiningbattery 156 ofuser device 150 is done being charged,charger device 110 transmits “available” signal, as shown atblock 416. - In one or more embodiments,
battery 156 may be done being charged whenbattery 156 is fully charged. Alternatively, to extend the life ofbattery 156 and to optimize battery health,battery 156 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 ofbattery 156 or a fixed amount (e.g., 80%). - In some embodiments,
charger device 110 may determine thatbattery 156 ofuser device 150 is done being charged, for example, by detecting a decrease or stop in power draw byuser device 150, detecting a decrease or stop in current flow, or no longer detecting contact withuser device 150 using a physical button or switch provided onplug 212,receptacle 232, plug 236, or charging plate 252 (inFIGS. 2A-C ). In other embodiments,charger device 110 may receive a communication fromuser device 150 indicatinguser device 150 is done charging via data interface 114 (inFIGS. 1A-B ) ofcoupling component 112. In a further embodiment,charger device 110 may receive a wireless communication fromuser device 150 indicatinguser device 150 is done charging viawireless interface 120. - In an example, when
user 102 connects charger device 110 (e.g., by plugging inplug FIGS. 2A-C ) to an AC outlet, charger device starts broadcasting “available”signal 104 and continues broadcasting “available”signal 104 whilecharger device 110 is not connected to or otherwise coupled touser device 150. Whenuser 102 connects charger device 110 (e.g., by plugging inplug FIGS. 2A-B ) touser device 150,charger device 110 stops broadcasting the “available signal.” Whenuser device 150 is done charging,charger device 110 resumes broadcasting “available”signal 104. Whenuser 102 subsequently disconnects charger device 110 (e.g., by unpluggingplug 212 or 236) fromuser device 150,charger device 110 continues broadcasting “available”signal 104, as shown inblock 416. -
FIG. 5 illustrates a flow diagram of aprocess 500 for broadcasting two or more types of signals such as one ormore signals 104, 106 (inFIGS. 1A-B ) by a charger device such as charger device 110 (inFIGS. 1A-B ), according to one or more embodiments of the present disclosure. - At
block 502,charger device 110 receives power, as described above at 402. - At
block 504,charger device 110 determines whether charger device 110 (e.g., usingcoupling component 112 inFIGS. 1A-B ) is connected to or otherwise coupled to a user device such as user device 150 a (inFIGS. 1A-B ), as described above atblock 404. - At
block 506,charger device 110 broadcasts or otherwise transmits (e.g., viawireless interface 120 inFIGS. 1A-B ) an “available” signal such as signal 104 (inFIG. 1A ) in response to determining thatcharger device 110 is not connected to or otherwise coupled to user device 150 a, as described above atblock 406. - At
block 508, charger device 110 (e.g., via wireless interface 120) does not broadcast or otherwise transmit “available”signal 104 in response to determining thatcharger device 110 is connected to or otherwise coupled to user device 150 a while user device 150 a is charging. - At
block 510,charger device 110 determines whether user device 150 a is done charging while still connected to or otherwise coupled to user device 150 a. In response to determining user device 150 a is still charging, charger device 110 (e.g., via wireless interface 120) does not broadcast or otherwise transmit “available”signal 104, as shown atblock 508. - At
block 512, in response to determining user device 150 a is done charging while still connected to or otherwise coupled to user device 150 a, charger device 110 (e.g., via wireless interface 120) broadcasts or otherwise transmits a “done charging” signal such as signal 106 (inFIG. 1B ) that includes an identifier such as identifier 362 (e.g., a device identifier or user identifier) received from user device 150 a indicating that user device 150 a is done charging. For example, “done charging”signal 106 may include a message indicatinguser device 150 is done charging, at least one ofidentifiers 362, and/or a timestamp. In some embodiments, in response to determining user device 150 a is done charging, charger device 110 (e.g., via wireless interface 120) broadcasts or otherwise transmits “done charging”signal 106 and also “available”signal 104. A process for generating and transmitting “done charging”signal 106 is further described below in relation toFIG. 6 . - In one or more embodiments, another user device of
user 102 such as user device 150 b (inFIGS. 1A-B ) may receive “done charging”signal 106 and notifyuser 102 that user device 150 a is done charging, such as by providing a notification touser 102 on a display such as display 166 (inFIGS. 1A-B ) of user device 150 b. In some embodiments, user device 150 a may be paired to, bonded to, linked with, or otherwise associated with user device 150 b. During initial pairing (e.g., Bluetooth® initial pairing or bonding), user device 150 a and user device 150 b may each share itsidentifier 362, such as a device identifier (e.g., a UUID or MAC address/number), to the other device, and each device may storeidentifier 362 of the other device in itsdatabase 360. For example, user device 150 a may storeidentifier 362 of user device 150 b in itsdatabase 360 and user device 150 b may storeidentifier 362 of user device 150 a in itsdatabase 360. When user device 150 b receives “done charging”signal 106, user device 150 b may recognizeidentifier 362 contained in “done charging”signal 106 asidentifier 362 of user device 150 a previously stored indatabase 360 of user device 150 b during pairing of user device 150 a and 150 b. Whenuser 102 receives the notification,user 102 is alerted that user device 150 a is done charging and may go disconnect or otherwise uncouple user device 150 a fromcharger device 110. - At
block 514,charger device 110 determines whether charger device 110 (e.g., usingcoupling component 112 inFIGS. 1A-B ) is disconnected from or otherwise uncoupled from user device 150 a, similarly as described above atblock 402. - In some embodiments,
coupling component 112 includes a connector (e.g., plug 212 orreceptacle 242 inFIGS. 2A-B ), andcharger device 110 may determine thatcoupling component 112 is disconnected fromuser device 150 when 212 or 236 (inFIGS. 2A-B ) is unplugged from a corresponding receptacle ofuser device 150 orreceptacle 242 is disconnected from user device 150 (e.g., using a power cable such aspower cable 234 and a plug such asplug FIG. 2B ). For example,charger device 110 may determine a connection such as connection 108 (inFIG. 1B ) is disconnected by detecting a stopped or decreased power draw or a stopped or decreased current flow. In another example,charger device 110 may determineconnection 108 is disconnected by detecting removal of contact withuser device 150 using a physical button or switch provided onplug 212,receptacle 232, or plug 236. - In other embodiments,
coupling component 112 includes an inductive coil in acharging plate 252, and charger device may determine thatcoupling component 112 is decoupled fromuser device 120 whenuser device 150 including a corresponding inductive coil is removed from on or near chargingplate 252. For example,charger device 110 may determine a coupling such as coupling 108 (inFIG. 1B ) is decoupled by detectinguser device 150 is removed from a charging range ofcharger device 110 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 device 110 may include a proximity sensor to determinecoupling 108 is decoupled. In a further example,charger device 110 may determinecoupling 108 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 device 110 may determinecoupling 108 is decoupled by detecting removal of contact withuser device 150 using a physical button or switch provided on chargingplate 252. - At
block 516, in response to determining charger device 110 (e.g., using coupling component 112) is no longer connected to or otherwise coupled to user device 150 a, charger device 110 (e.g., via wireless interface 120) may broadcast or otherwise transmit “available”signal 104 and no longer broadcast or otherwise transmit “done charging”signal 106. - In response to determining charger device 110 (e.g., using coupling component 112) is still coupled to
user device 150 that is done charging, charger device continues transmitting “done charging”signal 106 and/or “available”signal 104, as shown atblock 512. -
FIG. 6 illustrates a flow diagram of a process for generating and transmitting a signal by a charger device such as charger device 110 (inFIGS. 1A-B ) according to one or more embodiments of the present disclosure. - At
block 602,charger device 110 may receive data from a user device such as user device 150 a (inFIGS. 1A-B ) whilecharger device 110 is connected to or otherwise coupled to user device 150 a. In some embodiments,charger device 110 may request an identifier such as identifier 362 (e.g., a device identifier or user identifier) from user device 150 a at thetime charger device 110 is connected to or otherwise coupled to user device, when user device 150 a is done charging, or anytime in between.Charger device 110 may receiveidentifier 362 from user device 150 a via a data interface such as data interface 114 (inFIGS. 1A-B ) included in a coupling component such as coupling component 112 (inFIGS. 1A-B ) used to connectcharger device 110 touser device 150. Alternatively,charger device 110 may receiveidentifier 362 from user device 150 a through wireless communications via a wireless interface such as wireless interface 120 (inFIGS. 1A-B ). - At
block 604,charger device 110 generates a “done charging” signal such assignal 106 inFIG. 1B that includesidentifier 362 received from user device 150 a. - At
block 604,charger device 110 broadcasts or otherwise transmits “done charging”signal 106 indicating user device 150 a is done charging, as described above atblock 512. -
FIG. 7 illustrates a flow diagram of aprocess 700 for notifying a user such as user 102 (inFIGS. 1A-B ) to charge a user device such as user device 150 (inFIGS. 1A-B ) using a charger device such as charger device 110 (inFIGS. 1A-B ) according to one or more embodiments of the present disclosure. - At
block 702, a service provider server such as service provider server 130 (inFIGS. 1A-B andFIG. 3 ) oruser device 150 determines thatcharger device 110 is available in response touser device 150 receiving an “available” signal such as signal 104 (inFIG. 1A ). In one or more embodiments,user device 150 may determinecharger device 110 is available in response to receiving “available”signal 104. In some embodiments,user device 150 may communicate thatcharger device 110 is available toservice provider server 130 in response to receiving “available”signal 104. Based on such communication,service provider server 130 may determinecharger device 110 is available in response touser device 150 receiving “available”signal 104. - At
block 704,service provider server 130 oruser device 150 determines an amount of power in a battery such as battery 156 (inFIGS. 1A-B ). In one or more embodiments,user device 150 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 bybattery 156 to monitor the amount of power left, by measuring the internal impedance ofbattery 156 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 device 150 may communicate the amount of power left inbattery 156 toservice provider server 130 as part of the communication indicatingcharger device 110 is available atblock 706 or in a separate communication. Based on such communication,service provider server 130 may determine the amount of power left inbattery 156, which may also be in response touser device 150 receiving “available”signal 104. - At
block 706,service provider server 130 oruser device 150 may access activity data, such asactivity data 342 indatabase 338 ofservice provider server 130 oractivity data 364 indatabase 360 ofuser device 150 in response touser device 150 receiving “available”signal 104. In one or more embodiments,user device 150 may detect movement ofuser 102 to generateactivity data 364 and store activity data indatabase 360 of user device. In some embodiments,user device 150 may transmitactivity data 364 toservice provider server 130 to be stored asactivity data 342 in user account 340 indatabase 338.User device 150 may transmitactivity data 364 toservice provider server 130 by syncingactivity data 364 withactivity data 342. Alternatively,user device 150 may transmitactivity data 364 toservice provider server 130 by periodically transmittingactivity data 364 and/or by transmittingactivity data 364 in response to receiving “available”signal 104. - In one or more embodiments,
user device 150 may accessactivity data 342 indatabase 338 in response to receiving “available”signal 104. In other embodiments,service provider server 130 may accessactivity data 342 indatabase 338 ofservice provider server 130 and/oractivity data 364 indatabase 360 ofuser device 150 inresponse user device 150 to receiving “available”signal 104. -
Activity data user 102 has been active and/or howactive user 102 has been recently (e.g., in the past 5 minutes).Activity data user 102 is usually active at a certain time of day in general or whetheruser 102 is usually active at a certain time of day on certain days of the week. - At
block 708,service provider server 130 oruser device 150 may access a current time in response touser device 150 receiving “available”signal 104. - At
block 710,service provider server 130 oruser device 150 may determine a geolocation ofuser device 150 in response touser device 150 receiving “available”signal 104. In one or more embodiments,user device 150 may use a location component such aslocation component 170 to determine the geolocation, which may be stored indatabase 360 aslocation data 366. In some embodiments,user device 150 may provideservice provider server 130 with access to the geolocation determined bylocation component 170 and/or communicate the geolocation toservice provider server 130 as part of the communication indicatingcharger device 110 is available atblock 706 or in a separate communication. Based on such access or communication,service provider server 130 may determine the geolocation ofuser device 150 in response touser device 150 receiving “available”signal 104. - At
block 712,service provider server 130 oruser device 150 may determine battery data including battery usage data and/or other battery-related data for a battery such asbattery 156 ofuser device 150 in response touser device 150 receiving “available”signal 104. In one or more embodiments,user device 150 may include a battery management system and may access battery data from battery management system. In some embodiments,user device 150 may communicate the battery data toservice provider server 130 as part of the communication indicatingcharger device 110 is available atblock 706 or in a separate communication. Based on such communication,service provider server 130 may determine the battery data in response touser device 150 receiving “available”signal 104. - At
block 714,service provider server 130 oruser device 150 determines whether to notifyuser 102 to chargeuser device 150 based onuser device 150 receiving “available” signal, the amount of power remaining inbattery 156,activity data Service provider server 130 oruser device 150 determines whether to notifyuser 102 to chargeuser device 150 further based on other conditions and/or factors. - For example,
service provider server 130 oruser device 150 may decide to notifyuser 102 to chargeuser device 150 whencharger device 110 is available and the amount of power remaining inbattery 156 is low. - In another example,
service provider server 130 oruser device 150 may decide to notifyuser 102 to chargeuser device 150 whencharger device 110 is available, the amount of power remaining inbattery 156 is low, andactivity data user 102 has not been active recently (e.g., within the past 5 minutes). Whenuser 102 has not been active recently, such as whenuser 102 is lounging and watching television,user 102 presumably does not needuser device 150 at the moment. - In a further example,
service provider server 130 oruser device 150 may decide to notifyuser 102 to chargeuser device 150 whencharger device 110 is available, the amount of power remaining inbattery 156 is low,activity data user 102 has not been active recently, andfurther activity data user 102 is usually not active at the time of the day or week. - In yet another example,
service provider server 130 oruser device 150 may determineuser device 150 requires charging by forecasting how muchpower user device 150 requires to get through the day (e.g., until night time whenuser 102 usually gets home) or to get through a time period in whichuser 102 does not have access tocharger device 110, such as during a commute (e.g., from home to work or vice versa), based on the battery usage data.Service provider server 130 oruser device 150 may decide to notifyuser 102 to chargeuser device 150 whencharger device 110 is available anduser device 150 requires charging based on the battery usage data. -
Service provider server 130 oruser device 150 may determine whether to notifyuser 102 to chargeuser device 150 in response to other combinations of such conditions and/or factors. - At
block 716,user device 150 presents a notification on a display such as display 166 (inFIGS. 1A-B ). The notification may include amessage prompting user 102 to chargeuser device 150 and/or indicatecharger device 110 is available. In some embodiments, the notification may include a distance tocharger device 110.User device 150 may determine the distance betweenuser device 150 andcharger device 110 based on “available” signal 104 (e.g., using a timestamp included in “available” signal 104). In further embodiments, the notification may further include a geolocation of charger device 110 (e.g., presented on a map). -
FIG. 8 illustrates a charge station orkiosk 800 includingmultiple charger devices 110 a-e according to one or more embodiments of the present disclosure. - In one or more embodiments, charging
station 800 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 users 102 (inFIGS. 1A-B ), may want to charge their user devices such as user device 150 (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 station 800 does not require such a payment device, as each ofcharger devices 110 a-e is configured to interact withuser device 150 to allowservice provider server 130 to process payment for providing power for charginguser device 150. - In some embodiments,
charger device 110 e transmits to user device 150 a charger device identifier touser device 150 via a data interface such as data interface 154 (inFIGS. 1A-B ).User device 150 may transmit the charger device identifier and an identifier such as identifier 362 (e.g., a device identifier or user identifier) fromuser device 150 toservice provider server 130. The charger device identifier may be associated with an account of a merchant or service provider that is charging fees for providing power throughcharger devices 110 a-e.Identifier 362 may be associated with user account 340 indatabase 338 ofservice provider server 130.Service provider server 130 may process a payment from user account 340 to the account of the merchant or service provider using the charger device identifier andidentifier 362. - In other embodiments,
charger device 110 e receivesidentifier 362 fromuser device 150 and transmitsidentifier 362 and a charger device identifier toservice provider server 130 overnetwork 180.Service provider server 130 may process a payment from user account 340 to the account of the merchant or service provider using the charger device identifier andidentifier 362. -
FIG. 9 illustrates a flow diagram of a process for processing a payment for charging a user device such as user device 150 (inFIGS. 1A-B ) of a user such as user 102 (inFIGS. 1A-B ) by a charger device such as charger device 110 (inFIGS. 1A-B ) according to one or more embodiments of the present disclosure. - At
block 902,service provider server 130 may receive fromcharger device 110 oruser device 150, vianetwork 180, a communication including an identifier such as identifier 362 (e.g., a device identifier or user identifier) and a charger device identifier, as described above in relation toFIG. 8 . - At
block 904,service provider server 130 may determine a user account such as user account 340 ofuser 102 based onidentifier 362. For example,identifier 362 may be a user identifier associated with user account 340.Service provider server 130 may also determine an account of a merchant or service provider that is to receive the payment for providing power throughcharger device 110 for charginguser device 150 based on charger device identifier. For example, charger device identifier may be associated with the account of the merchant or service provider. - At
block 906, service provider server may transmit to user device a notification regarding payment for providing power for charginguser device 150. For example, the notification may indicate the fee pertime charger device 110 is used, or the fee per amount of charge (e.g., in Ah) delivered, or a fee for fully charginguser device 150. When the notification is displayed on user device, it may include an accept button or other GUI elements thatuser 102 may interact with to authorize or decline payment for charginguser device 150. - At
block 908,service provider server 130 may receive an authorization fromuser 102 in response touser 102 providing authorization onuser device 150, such as by touching the accept button in the notification. - At
block 910,service provider server 130 receives fromcharger device 110 oruser device 150, vianetwork 180, a communication indicatinguser device 150 is done charging or has been disconnected. - At
block 912,service provider server 130 processes payment from user account 140 to the account of the merchant or service provider for providing power touser device 150 based on the fee authorized byuser 102 and/or the amount of charge provided touser device 150. -
FIG. 10 illustrates a block diagram of acomputer system 1000 for implementing, for example, a charger device such ascharger device 110, service provider server such asservice provider server 130, and one or more user device such as one ormore user devices 150 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 system 1000 in a manner as follows. - In accordance with various embodiments of the present disclosure,
computer system 1000, such as a computer and/or a network server, includes a bus 1002 or other communication mechanism for communicating information, which interconnects subsystems and components, such as a processing component 1004 (e.g., processor, micro-controller, digital signal processor (DSP), etc.), a system memory component 1006 (e.g., RAM), a static storage component 1008 (e.g., ROM), a disk drive component 1010 (e.g., magnetic or optical), a network interface component 1012 (e.g., modem or Ethernet card), a display component 1014 (e.g., LED display component, OLED display component, LCD component, PDP component, CRT display component, or other display component), an input component 1016 (e.g., keyboard, keypad, virtual keyboard, touchscreen, etc.), a cursor control component 1018 (e.g., mouse, pointer, trackball, etc.), and/or a location determination component 1020 (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 component 1010 may include a database having one or more disk drive components. - In accordance with various embodiments of the present disclosure,
computer system 1000 performs specific operations by processingcomponent 1004 executing one or more sequences of instructions contained inmemory component 1006, such as described herein with respect tocharger device 110,service provider server 130, and one ormore user devices 150. Such instructions may be read intosystem memory component 1006 from another computer readable medium, such asstatic storage component 1008 ordisk drive component 1010. 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 to
processing component 1004 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 component 1010, volatile media includes dynamic memory, such assystem memory component 1006, and transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 1002. 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 by
computer system 1000. In various other embodiments of the present disclosure, a plurality ofcomputer systems 1000 coupled by acommunication link 1022 to anetwork 1024 such asnetwork 180 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 system 1000 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) throughcommunication link 1022 andnetwork interface component 1012.Network interface component 1012 may include an antenna, either separate or integrated, to enable transmission and reception viacommunication link 1022. Received program code may be executed byprocessing component 1004 as received and/or stored indisk drive component 1010 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 with
charger device 110,service provider server 130, and one ormore user devices 150 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)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/103,841 US20190109475A1 (en) | 2015-08-07 | 2018-08-14 | Smart charging of user devices |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/821,615 US10050457B2 (en) | 2015-08-07 | 2015-08-07 | Smart charging of user devices |
US16/103,841 US20190109475A1 (en) | 2015-08-07 | 2018-08-14 | Smart charging of user devices |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/821,615 Continuation US10050457B2 (en) | 2015-08-07 | 2015-08-07 | Smart charging of user devices |
Publications (1)
Publication Number | Publication Date |
---|---|
US20190109475A1 true US20190109475A1 (en) | 2019-04-11 |
Family
ID=58052724
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/821,615 Active 2035-11-01 US10050457B2 (en) | 2015-08-07 | 2015-08-07 | Smart charging of user devices |
US16/103,841 Abandoned US20190109475A1 (en) | 2015-08-07 | 2018-08-14 | Smart charging of user devices |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/821,615 Active 2035-11-01 US10050457B2 (en) | 2015-08-07 | 2015-08-07 | Smart charging of user devices |
Country Status (1)
Country | Link |
---|---|
US (2) | US10050457B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10672218B1 (en) * | 2017-06-20 | 2020-06-02 | Rick Lawson | Personal electronic charging station |
US20210152036A1 (en) * | 2017-09-08 | 2021-05-20 | Apple Inc. | Wireless Power System With Battery Charge Indicators |
US20220239130A1 (en) * | 2017-06-04 | 2022-07-28 | Apple Inc. | Coordinating complementary notifications across related computing devices connected to a wireless charging apparatus |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2518128B (en) * | 2013-06-20 | 2021-02-10 | Nokia Technologies Oy | Charging rechargeable apparatus |
US10050457B2 (en) * | 2015-08-07 | 2018-08-14 | Paypal, Inc. | Smart charging of user devices |
DE102015117978A1 (en) * | 2015-10-22 | 2017-04-27 | Rwe Ag | Mobile electrical storage |
GB2559781A (en) * | 2017-02-17 | 2018-08-22 | Zapgo Ltd | Wearable electronic device including a supercapacitor |
US10381844B2 (en) | 2017-06-23 | 2019-08-13 | Dell Products L.P. | Sourcing power from a battery or AC-DC converter of a power storage adapter |
US10389154B2 (en) | 2017-06-23 | 2019-08-20 | Dell Products L.P. | Power storage adapter using a high efficiency charging method |
US10452102B2 (en) | 2017-06-23 | 2019-10-22 | Dell Products L.P. | Power delivery contract establishment in a power storage adapter |
US10978896B2 (en) | 2017-06-23 | 2021-04-13 | Dell Products L.P. | High efficiency power storage adapter |
US10181739B1 (en) | 2017-06-23 | 2019-01-15 | Dell Products L.P. | Power storage adapter using high efficiency charging for low power states |
US10476288B2 (en) | 2017-06-23 | 2019-11-12 | Dell Products L.P. | Power storage adapter for peak shift operation with a portable information handling system |
US10181731B1 (en) * | 2017-06-23 | 2019-01-15 | Dell Products L.P. | Combining power from a battery and an AC-DC converter of a power storage adapter |
US10928880B2 (en) | 2017-06-23 | 2021-02-23 | Dell Products L.P. | Power storage adapter for communicating battery data with a portable information handling system |
US10608443B2 (en) | 2017-08-15 | 2020-03-31 | Dell Products L.P. | Battery management using battery temperature distribution |
US10642333B2 (en) | 2017-08-24 | 2020-05-05 | Dell Products L.P. | Power storage adapter for efficient supply of power of multiple portable information handling systems |
US10459234B2 (en) * | 2017-08-29 | 2019-10-29 | Facebook, Inc. | Controlling a head-mounted display system in low power situations |
US10673271B2 (en) | 2017-09-01 | 2020-06-02 | Dell Products L.P. | Efficient charging of multiple portable information handling systems based on learned charging characteristics |
US10620679B2 (en) | 2017-09-01 | 2020-04-14 | Dell Products L.P. | Prioritizing supplying electrical power by a power storage adapter to connected devices |
US10404105B2 (en) | 2017-09-14 | 2019-09-03 | Dell Products L.P. | Power storage adapter for wireless power transmission |
US11513928B2 (en) | 2017-09-18 | 2022-11-29 | Dell Products L.P. | Power storage adapter with power cable validation |
US10714797B2 (en) | 2017-09-18 | 2020-07-14 | Dell Products L.P. | Multilayer thermal laminate with aerogel for battery cell enclosures |
US10488906B2 (en) | 2017-09-26 | 2019-11-26 | Dell Products L.P. | Power delivery based on temperature and other factors in a power storage adapter |
CN108054806A (en) * | 2018-01-11 | 2018-05-18 | 石李超 | A kind of onboard charger with voice control |
EP3591792A1 (en) * | 2018-07-04 | 2020-01-08 | Batterypal Sp. z o.o. | A system and a method for operating a power strip |
TWI709101B (en) * | 2019-07-29 | 2020-11-01 | 和碩聯合科技股份有限公司 | Battery charging method |
US11462925B2 (en) | 2019-08-07 | 2022-10-04 | Nathan R. Roberts | Storage and charging station system for mobile electronic devices having a unitary support tower cage structure |
GB2598612B (en) * | 2020-09-04 | 2023-04-05 | Source To Site Accessories Ltd | Identifying an electronic device connected to an electrical power source |
KR20240019623A (en) * | 2022-08-04 | 2024-02-14 | 삼성전자주식회사 | Apparatus and method for determining source capability for charging of an electronic device |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090177580A1 (en) * | 2008-01-07 | 2009-07-09 | Lowenthal Richard W | Collection of electric vehicle power consumption tax |
US20090313098A1 (en) * | 2008-06-16 | 2009-12-17 | International Business Machines Corporation | Network Based Energy Preference Service for Managing Electric Vehicle Charging Preferences |
US20130062966A1 (en) * | 2011-09-12 | 2013-03-14 | Witricity Corporation | Reconfigurable control architectures and algorithms for electric vehicle wireless energy transfer systems |
US20160141908A1 (en) * | 2014-11-14 | 2016-05-19 | Motorola Solutions, Inc | Method and apparatus for efficiency compliance in wireless charging systems |
US10050457B2 (en) * | 2015-08-07 | 2018-08-14 | Paypal, Inc. | Smart charging of user devices |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8452235B2 (en) * | 2009-03-28 | 2013-05-28 | Qualcomm, Incorporated | Tracking receiver devices with wireless power systems, apparatuses, and methods |
US9692259B2 (en) * | 2010-06-29 | 2017-06-27 | International Business Machines Corporation | Power management and priority charging assignments |
US9306634B2 (en) * | 2011-03-01 | 2016-04-05 | Qualcomm Incorporated | Waking up a wireless power transmitter from beacon mode |
US9553473B2 (en) * | 2013-02-04 | 2017-01-24 | Ossia Inc. | Systems and methods for optimally delivering pulsed wireless power |
-
2015
- 2015-08-07 US US14/821,615 patent/US10050457B2/en active Active
-
2018
- 2018-08-14 US US16/103,841 patent/US20190109475A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090177580A1 (en) * | 2008-01-07 | 2009-07-09 | Lowenthal Richard W | Collection of electric vehicle power consumption tax |
US20090313098A1 (en) * | 2008-06-16 | 2009-12-17 | International Business Machines Corporation | Network Based Energy Preference Service for Managing Electric Vehicle Charging Preferences |
US20130062966A1 (en) * | 2011-09-12 | 2013-03-14 | Witricity Corporation | Reconfigurable control architectures and algorithms for electric vehicle wireless energy transfer systems |
US20160141908A1 (en) * | 2014-11-14 | 2016-05-19 | Motorola Solutions, Inc | Method and apparatus for efficiency compliance in wireless charging systems |
US10050457B2 (en) * | 2015-08-07 | 2018-08-14 | Paypal, Inc. | Smart charging of user devices |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220239130A1 (en) * | 2017-06-04 | 2022-07-28 | Apple Inc. | Coordinating complementary notifications across related computing devices connected to a wireless charging apparatus |
US11936225B2 (en) * | 2017-06-04 | 2024-03-19 | Apple Inc. | Coordinating complementary notifications across related computing devices connected to a wireless charging apparatus |
US10672218B1 (en) * | 2017-06-20 | 2020-06-02 | Rick Lawson | Personal electronic charging station |
US20210152036A1 (en) * | 2017-09-08 | 2021-05-20 | Apple Inc. | Wireless Power System With Battery Charge Indicators |
US20230021065A1 (en) * | 2017-09-08 | 2023-01-19 | Apple Inc. | Wireless Power System With Battery Charge Indicators |
US11664686B2 (en) * | 2017-09-08 | 2023-05-30 | Apple Inc. | Wireless power system with battery charge indicators |
Also Published As
Publication number | Publication date |
---|---|
US10050457B2 (en) | 2018-08-14 |
US20170040815A1 (en) | 2017-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190109475A1 (en) | Smart charging of user devices | |
US11854050B2 (en) | Managing multiple beacons with a network-connected primary beacon | |
US11663622B2 (en) | Offline information pushing method and apparatus | |
KR102209523B1 (en) | Electronic apparatus and positiong method thereof | |
TWI633512B (en) | Near field communication (nfc) based vendor/customer interface | |
JP2018110519A (en) | System and method for wireless charging | |
US9691062B2 (en) | Systems and methods for wirelessly determining accepted forms of payment | |
TW201134050A (en) | Condition-based wireless power | |
KR20150026650A (en) | Apparatus and method for interworking among electronic devices | |
CN105531948A (en) | Systems and methods for checking a user into a location using a packet sequence including location information | |
KR102513790B1 (en) | Method and apparatus for transmitting a wireless power | |
KR20150105580A (en) | Method and apparatus for updating advertising information | |
KR102141854B1 (en) | Apparatus and method for controlling push message transmission | |
US20150288207A1 (en) | System and Method for Smart Charging a Mobile Device | |
TWI704514B (en) | Method for wireless charging services and wireless charging device | |
US20170331319A1 (en) | Charging device and method for operating a charging device | |
KR20150099236A (en) | Apparatus and method for providing push service based on location | |
KR20120132773A (en) | Wireless charging device, mobile terminal, system based on advertisement and method thereof | |
JP2015050719A (en) | Portable type information apparatus for reading out predetermined information from charger, system, program, and method | |
KR20190093639A (en) | Information processing device, control method and program of information processing device | |
WO2021214653A1 (en) | Wireless charging adapter, system and method | |
US10312720B2 (en) | Wireless charging service method and wireless charging device | |
CN112566080B (en) | Electronic device and method for controlling information exchange and discovery in electronic device | |
KR20160000355A (en) | Method of Inviting other Devices to Chat Room by Using Information on Access Point and Device therefor | |
KR20140079566A (en) | An accounting method and system for wireless charging of portable mobile terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PAYPAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TODASCO, MICHAEL CHARLES;REEL/FRAME:046649/0632 Effective date: 20150807 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |