WO2016164846A1 - Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil - Google Patents

Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil Download PDF

Info

Publication number
WO2016164846A1
WO2016164846A1 PCT/US2016/026819 US2016026819W WO2016164846A1 WO 2016164846 A1 WO2016164846 A1 WO 2016164846A1 US 2016026819 W US2016026819 W US 2016026819W WO 2016164846 A1 WO2016164846 A1 WO 2016164846A1
Authority
WO
WIPO (PCT)
Prior art keywords
battery
portable device
power
information
wireless
Prior art date
Application number
PCT/US2016/026819
Other languages
English (en)
Other versions
WO2016164846A8 (fr
Inventor
Hatern ZEINE
Anas ALFARRA
Dale MAYES
Fady EL-RUKBY
Samy MAHMOUD
John B. SPRINGER
Benjamin Todd RENNEBERG
Prithvi SHYLENDRA
Anthony L. JOHNSON
Douglas Wayne WILLIAMS
Original Assignee
Ossia Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ossia Inc. filed Critical Ossia Inc.
Priority to KR1020177032538A priority Critical patent/KR20180050601A/ko
Priority to EP16836076.6A priority patent/EP3281273A4/fr
Priority to CN201680033396.7A priority patent/CN108141045B/zh
Priority to JP2017552049A priority patent/JP2018516041A/ja
Publication of WO2016164846A1 publication Critical patent/WO2016164846A1/fr
Publication of WO2016164846A8 publication Critical patent/WO2016164846A8/fr

Links

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/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
    • H02J50/00—Circuit arrangements or systems for wireless supply or distribution of electric power
    • H02J50/20—Circuit arrangements or systems for wireless supply or distribution of electric power using microwaves or radio frequency waves
    • 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/50—Circuit arrangements or systems for wireless supply or distribution of electric power using additional energy repeaters between transmitting devices and receiving 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/80—Circuit arrangements or systems for wireless supply or distribution of electric power involving the exchange of data, concerning supply or distribution of electric power, between transmitting devices and receiving 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
    • 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

Definitions

  • WIRELESS POWER DELIVERY U.S. Application No. , filed April 8, 2016, titled WIRELESS POWER TRANSCEIVERS FOR SUPPLEMENTING WIRELESS POWER DELIVERY AND EXTENDING RANGE; U.S. Application No. 15/093,023, filed April 7, 2016, titled TECHNIQUES FOR STATICALLY TUNING RETRO- DIRECTIVE WIRELESS POWER TRANSMISSION SYSTEMS; U.S. Application No. 15/092,026, filed April 6, 2016, titled ESTABLISHING CONNECTIONS WITH CHARGERS IN MULTI-CHARGER WIRELESS POWER DELIVERY ENVIRONMENTS; U.S. Application No.
  • the technology described herein relates generally to the field of wireless communication and power transmission, such as wireless power delivery systems and clients for receiving wireless power.
  • Figure 1 is a diagram illustrating an example wireless power delivery environment depicting wireless power delivery from one or more wireless transmitters to various wireless devices within the wireless power delivery environment.
  • Figure 2 is a sequence diagram illustrating example operations between a wireless transmitter and a power receiver client for commencing wireless power delivery.
  • FIG. 3 is a block diagram illustrating an example wireless power receiver (client) in accordance with an embodiment.
  • Figure 4 is a system overview diagram illustrating various components of the various embodiments described herein.
  • Figure 5 is a diagram illustrating an example environment including a cloud processing system configured to calculate power consumption of wireless devices in power distribution areas, according to various embodiments.
  • Figure 6 is a diagram illustrating an example of an admin interface of a cloud processing system, according to various embodiments.
  • Figures 7A and 7B are flow diagrams illustrating example processes facilitating calculation of power consumption of wireless devices, according to various embodiments.
  • Figure 8 is a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • Figure 9 is a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • Embodiments of the present disclosure describe various techniques for wirelessly charging and/or wireless power delivery from one or more chargers to one or more wireless devices (also referred to herein as “devices” or “target devices”) having embedded, attached, and/or integrated power receiver clients (also referred to herein as “wireless power receivers” or “clients”).
  • wireless devices also referred to herein as “devices” or “target devices”
  • embedded, attached, and/or integrated power receiver clients also referred to herein as “wireless power receivers” or “clients”
  • power, data, or both may be delivered simultaneously as a continuous complex waveform, as a pulsed waveform, as multiple overlapping waveforms, or combinations or variations thereof.
  • the power and data may be delivered using the same or different wireless technologies.
  • the wireless technologies described herein may apply to not only electromagnetic (EM) waves, but also to sound waves, and/or other forms of periodic excitations (e.g., phonons).
  • EM waves may include radio waves, microwaves, infrared radiation, visible light, ultraviolet radiation, X-rays, and/or gamma rays.
  • Sound waves may include infrasound waves, acoustic waves, and/or ultrasound waves.
  • the techniques described herein may simultaneously utilize multiple wireless technologies and/or multiple frequency spectrums within a wireless technology to deliver the power, data or both.
  • the wireless technologies may include dedicated hardware components to deliver power and/or data.
  • the dedicated hardware components may be modified based on the wireless technology, or combination of wireless technologies, being utilized. For example, when applied to sound waves, the system employs microphones and speakers rather than antennas.
  • Figure 1 is a diagram illustrating an example wireless communication/power delivery environment 100 depicting wireless power delivery from one or more wireless transmitters 101 to various wireless devices 102 within the wireless communication/power delivery environment. More specifically, Figure 1 illustrates an example wireless power delivery environment 100 in which wireless power and/or data can be delivered to available wireless devices 102.1 -102. n having one or more power receiver clients 103.1 -103. n (also referred to herein as "wireless power receivers" or “wireless power clients”). The wireless power receivers are configured to receive wireless power from one or more wireless transmitters 101 .
  • the wireless devices 102.1 -102. n are mobile phone devices 102.2 and 102.n, respectively, and a wireless game controller 102.1 , although the wireless devices 102.1 -102. n can be any (smart or dumb) wireless device or system that needs power and is capable of receiving wireless power via one or more integrated power receiver clients 103.1 -103. n.
  • Smart devices are electronic devices that can communicate (e.g., using WiFi) and transmit beacon signals.
  • Dumb devices are electronic device are passive devices that may not communication (e.g., no Bluetooth or Wifi capability) and may not transmit a beacon signal.
  • the one or more integrated power receiver clients or “wireless power receivers” receive and process power from one or more transmitters/transmitters 101 .a-101 .n and provide the power to the wireless devices 102.1 -102. n for operation thereof.
  • Each transmitter 101 (also referred to herein as a “charger”, “array of antennas” or “antenna array system”) can include multiple antennas 104, e.g., an antenna array including hundreds or thousands of spaced-apart antennas, that are each capable of delivering wireless power to wireless devices 102.
  • Each transmitter 101 may also deliver wireless communication signals to wireless devices 102.
  • the wireless power and wireless communication signals may be delivered as a combined power/communication signal. Indeed, while the detailed description provided herein focuses on wirelessly transmitting power, aspects of the invention are equally applicable to wirelessly transmitting data.
  • the antennas are adaptively-phased radio frequency antennas and the transmitter 101 utilizes a novel phase shifting algorithm as described in one or more of U.S. Patent Nos. 8558661 , 8159364, 8410953, 8446248, 8854176, U.S. Patent Application Nos. 14/461 ,332 and 14/815,893.
  • the transmitter 101 is capable of determining the appropriate phases to deliver a coherent power transmission signal to the power receiver clients 103.
  • the array is configured to emit a signal (e.g., continuous wave or pulsed power transmission signal) from multiple antennas at a specific phase relative to each other.
  • the transmitter 101 may include a time delayed retro directive radio frequency (RF) holographic array that delivers wireless RF power that matches the client antenna patterns in three dimensional (3D) space (polarization, shape & power levels of each lobe).
  • RF radio frequency
  • array does not necessarily limit the antenna array to any specific array structure. That is, the antenna array does not need to be structured in a specific "array” form or geometry.
  • array or array system may be used include related and peripheral circuitry for signal generation, reception and transmission, such as radios, digital logic and modems.
  • the wireless devices 102 can include one or more power receiver clients 103 (also known as a "wireless power receiver"). As illustrated in the example of Figure 1 , power delivery antennas 104a and data communication antennas 104b are shown.
  • the power delivery antennas 104a are configured to provide delivery of wireless radio frequency power in the wireless power delivery environment.
  • the data communication antennas are configured to send data communications to, and receive data communications from, the power receiver clients 103.1 -103 and/or the wireless devices 102.1 -102. n.
  • the data communication antennas can communicate via BluetoothTM, WiFi, ZigBeeTM, or other wireless communication protocols.
  • Each power receiver client 103.1 -103. n includes one or more antennas (not shown) for receiving signals from the transmitters 101 .
  • each transmitter 101.a-101 .n includes an antenna array having one or more antennas and/or sets of antennas capable of emitting continuous wave signals at specific phases relative to each other.
  • each array is capable of determining the appropriate phases for delivering coherent signals to the power receiver clients 102.1 -102. n.
  • coherent signals can be determined by computing the complex conjugate of a received beacon signal at each antenna of the array such that the coherent signal is properly phased for the particular power receiver client that transmitted the beacon signal.
  • the beacon signal which is primarily referred to herein as a continuous waveform, can alternatively or additionally take the form of a modulated signal.
  • each component of the environment can include control and synchronization mechanisms, such as a data communication synchronization module.
  • the transmitters 101.a-101 .n are connected to a power source such as, for example, a power outlet or source connecting the transmitters to a standard or primary alternating current (AC) power supply in a building.
  • a power source such as, for example, a power outlet or source connecting the transmitters to a standard or primary alternating current (AC) power supply in a building.
  • AC alternating current
  • one or more of the transmitters 101 .a-101 .n can be powered by a battery or via other power providing mechanism.
  • the power receiver clients 102.1 -102. n and/or the transmitters 101 .a-101 .n utilize or encounter reflective objects 106 such as, for example, walls or other RF reflective obstructions within range to beacon and deliver and/or receive wireless power and/or data within the wireless power delivery environment.
  • the reflective objects 106 can be utilized for multi-directional signal communication regardless of whether a blocking object is in the line of sight between the transmitter and the power receiver client.
  • each wireless device 102.1 -102. n can be any system and/or device, and/or any combination of devices/systems that can establish a connection with another device, a server and/or other systems within the example environment 100.
  • the wireless devices 102.1 -102. n include displays or other output functionalities to present data to a user and/or input functionalities to receive data from the user.
  • a wireless device 102 can be, but is not limited to, a video game controller, a server desktop, a desktop computer, a computer cluster, a mobile computing device such as a notebook, a laptop computer, a handheld computer, a mobile phone, a smart phone, a battery or component coupled to a battery, a PDA etc.
  • the wireless device 102 can also be any wearable device such as watches, necklaces, rings or even devices embedded on or within the customer.
  • Other examples of a wireless device 102 include, but are not limited to, safety sensors (e.g., fire or carbon monoxide), electric toothbrushes, electronic door locks/handles, electric light switch controllers, electric shavers, etc.
  • the transmitter 101 and the power receiver clients 103.1 -103. n can each include a data communication module for communication via a data channel.
  • the power receiver clients 103.1 -103. n can direct the wireless devices 102.1 -102. n to communicate with the transmitter via existing data communications modules.
  • FIG. 2 is a sequence diagram 200 illustrating example operations between a wireless transmitter 101 and a power receiver client 103 for commencing wireless power delivery, according to an embodiment.
  • communication is established between the transmitter 101 and the power receiver client 103, such as communicate via BluetoothTM, WiFi, ZigBeeTM, or other wireless communication protocols.
  • the transmitter 101 subsequently sends a beaconing schedule to the power receiver client 103 to arrange beacon broadcasting and RF power/data delivery schedules with this and any other power receiver clients.
  • the power receiver client 103 broadcasts the beacon.
  • the transmitter 101 receives the beacon from the power receiver client 103 and detects the phase (or direction) at which the beacon signal was received.
  • the transmitter 101 then delivers wireless power and/or data to the power receiver client 103 based the phase (or direction) of the received beacon. That is, the transmitter 101 determines the complex conjugate of the phase and uses the complex conjugate to deliver power to the power receiver client 103 in the same direction in which the beacon signal was received from the power receiver client 103.
  • the transmitter 101 includes many antennas; one or more of which are used to deliver power to the power receiver client 103.
  • the transmitter 101 can detect phases of the beacon signals that are received at each antenna. The large number of antennas may result in different beacon signals being received at each antenna of the transmitter 101 .
  • the transmitter may then utilize the algorithm or process described in one or more of U.S. Patent Nos. 8558661 , 8159364, 8410953, 8446248, 8854176, and U.S. Provisional Patent Application Nos. 62/146,233 and 62/163,964.
  • the algorithm or process determines how to emit signals from one or more antennas that takes into account the effects of the large number of antennas in the transmitter 101 . In other words, the algorithm determines how to emit signals from one or more antennas in such a way as to create an aggregate signal from the transmitter 101 that approximately recreates the waveform of the beacon, but in the opposite direction.
  • FIG. 3 is a block diagram illustrating an example receiver 300 in accordance with an embodiment.
  • the receiver 300 includes various components including control logic 310, battery 320, communication block 330 and associated antenna 370, power meter 340, rectifier 350, beacon signal generator 360 and an associated antenna 380, and switch 365 connecting the rectifier 350 or the beacon signal generator 360 to an associated antenna 390.
  • Some or all of the components can be omitted in some embodiments. Additional or fewer components are also possible.
  • the rectifier 350 receives (via one or more client antennas) the power transmission signal from the power transmitter, which is fed through the power meter 340 to the battery 320 for charging.
  • the power meter 340 measures the total received power signal strength and provides the control logic 310 with this measurement.
  • the control logic 310 also may receive the battery power level from the battery 320 itself or receive battery power data from, e.g. an API of an operating system running on the receiver 300.
  • the control logic 310 may also transmit/receive via the communication block 330 a data signal on a data carrier frequency, such as the base signal clock for clock synchronization.
  • the beacon signal generator 360 transmits the beacon signal, or calibration signal, using either the antenna 380 or 390.
  • An optional motion sensor 395 detects motion and signals the control logic 310. For example, when a device is receiving power at high frequencies above 500 MHz, its location may become a hotspot of (incoming) radiation. So when the device is on a person, the level of radiation may exceed a regulation or exceed acceptable radiation levels set by medical/industrial authorities.
  • the device may integrate motion detection mechanisms such as accelerometers, assisted GPS, or other mechanisms. Once the device detects that it is in motion, the disclosed system assumes that it is being handled by a user, and signals the power transmitting array either to stop transmitting power to it, or to lower the received power to an acceptable fraction of the power. In cases where the device is used in a moving environment like a car, train or plane, the power might only be transmitted intermittently or at a reduced level unless the device is close to losing all available power.
  • motion detection mechanisms such as accelerometers, assisted GPS, or other mechanisms.
  • FIG 4 is a system overview diagram illustrating various embodiments and components possible, though other combinations and variations are possible.
  • the wireless power receiver can be in a form of an application specific integrated circuit (ASIC) chip, a mobile phone case, in a display device (e.g. computer monitor or television, which in turn may relay power to a nearby receiver 103), packaged within a standard battery form factor (e.g. AA battery), etc.
  • ASIC application specific integrated circuit
  • Techniques for calculating power consumption in wireless power delivery systems are disclosed herein. More specifically, techniques for calculating power consumption of devices, operating systems and applications are disclosed. For example, if multiple mobile phones having different operating systems are being charged via a wireless power delivery system, then the system can record power consumption of each individual mobile phone, the power consumption of each operating system running on each mobile phone, and the power consumption of each specific application running on each mobile phone. For example, a map application may consume more power if it is using GPS and a constant data connection to a website (versus an application that does not). Also, sometimes users may notice that their mobile phone runs out of charge more quickly than before but they would not know why. The techniques described herein may make it easier to pinpoint the cause, as well as provide other benefits.
  • FIG. 5 is a diagram illustrating an example environment 500 including a cloud processing system 550 configured to calculate power consumption of wireless devices in power distribution areas 520, according to various embodiments.
  • the example environment 500 includes the cloud processing system 550, a network 560, multiple power distribution areas 520, and multiple third party data consumers 510.
  • Each power distribution area 520 includes one or more wireless power transmitters or "chargers" 501 in communication with the network 560 and an administrator device (either locally or via network 560).
  • the chargers 501 provide wireless power to various wireless devices as described herein.
  • the cloud processing system 550 includes multiple servers 540 and data repositories 530. Any number of servers 540 and/or data repositories 530 may be included with cloud processing system 550.
  • the cloud processing system 550 is configured to calculate power usage of wireless devices in each power distribution area 520.
  • the wireless devices can provide information to the chargers 501 through the use of software on the wireless devices that access APIs on the devices to gather the information.
  • a charger 501 may transmit a periodic "Client Query" message to a client. This message requests the client to return a variety of information to the charger 501 .
  • the Client Query message may be a ZigBee message.
  • the wireless device may automatically transmit the information to the charger 501 periodically, or based on a trigger (e.g., when the battery level is below a threshold value, or when a rate of power consumption exceeds a threshold value).
  • the information sent to the charger 501 may include a device manufacturer name or ID, device model, battery type/model, hardware, operating system, etc.
  • the information may also include periodic updates on or status of applications currently running on the device, present battery status, device location, RF power received since last request, coulombs in or out of the battery since last request, device temperature, or other information related to power usage.
  • the charger 501 receives this information and passes it along via network 560 to the cloud processing system 550.
  • the charger 501 includes local processing capabilities.
  • the cloud processing system 550 or charger 501 then calculates power usage of the wireless devices based on the received information, including power usage based on particular hardware, operating system, application usage, etc.
  • the cloud processing system 550 or charger 501 may utilize the wireless device's battery status (e.g., voltage and/or coulombs in/out) to calculate the power usage of the particular hardware.
  • the cloud processing system 550 or charger 501 includes a database of types of batteries used in wireless devices, and their associated discharge/charge curves.
  • the cloud processing system 550 or charger 501 may identify a particular discharge/charge curve from the information received from the wireless device (e.g., device ID, manufacturer/model number, etc.).
  • the cloud processing system 550 or charger 501 may then identify where on the discharge/charge curve the device's present battery status falls, and from that calculate the time to charge or the time to die for that particular battery.
  • the cloud processing system 550 or charger 501 may also track the percentage of time spent sending power to each wireless device, and from that calculate the amount of power that should be delivered to each wireless device.
  • the cloud processing system 550 provides various information and alerts to a user and/or to a charger 501 . For example, if the power consumption of particular devices exceed a threshold, this might trigger an alert.
  • the cloud processing system 550 can also provide recommendations regarding power consumption to a user and/or charger 501 , and/or the wireless device. For example, if the charger 501 scheduled a particular wireless device ("client 1 ") to receive 75% of the available charge cycles over the last minute, but client 1 reports that more power was discharged from its battery than delivered into the battery, the cloud processing system 550 could report to the user to "move client 1 closer to the charger.” At the same time, charger 501 may dedicate more charging cycles to other wireless devices that may have a more effective power delivery.
  • the third party data consumers 510 may be any entity that can utilize the collected wireless device information.
  • the third party data consumers 510 can include telecommunications service providers, security service providers, home automation systems, energy companies, application developers (e.g., to optimize development across platforms, device manufacturers, etc.).
  • the third party data consumers 510 can purchase and/or otherwise obtain rights to aggregated data from the cloud processing system 550.
  • a security service provider may utilize phase data included in the wireless device information to determine if there is motion in the power distribution area 520 (e.g., in lieu of access to motion sensor data).
  • a home automation system may utilize temperature data included in the wireless device information to control a home thermostat.
  • the network 560 may be any type of cellular, IP-based or converged telecommunications network, including but not limited to Global System for Mobile Communications (GSM), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDM), General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Advanced Mobile Phone System (AMPS), Worldwide Interoperability for Microwave Access (WiMAX), Universal Mobile Telecommunications System (UMTS), Evolution- Data Optimized (EVDO), Long Term Evolution (LTE), Ultra Mobile Broadband (UMB), Voice over Internet Protocol (VoIP), Unlicensed Mobile Access (UMA), etc.
  • GSM Global System for Mobile Communications
  • TDMA Time Division Multiple Access
  • CDMA Code Division Multiple Access
  • OFDM Orthogonal Frequency Division Multiple Access
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data GSM Environment
  • AMPS Advanced Mobile Phone System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the network 560 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the cloud processing system 550, chargers 501 and third party data consumers 510.
  • communications to and from the cloud processing system 550, chargers 501 and third party data consumers 510 can be achieved by an open network, such as the Internet, or a private network, such as an intranet and/or the extranet.
  • the cloud processing system 550, chargers 501 and third party data consumers 510 can be coupled to the network 560 (e.g., Internet) via a dial-up connection, a digital subscriber loop (DSL, ADSL), cable modem, wireless connections, direct fiber connections and/or any other types of connection.
  • the network 560 e.g., Internet
  • the databases 530 can be implemented via object-oriented technology and/or via text files, and can be managed by any database management system. As shown, the databases 530 are coupled to (or otherwise included within cloud processing system 550). However, it is appreciated that in some embodiments, the databases 530 may be alternatively or additionally directly coupled to network 560 and/or distributed across multiple systems.
  • the wireless device has installed a simple client application on its operating system (iOS, Android, etc.).
  • the wireless device initially reports the device hardware information, the operating system device information, and/or the battery status to the charger 501 .
  • the wireless device may receive a ZigBee message requesting the information, and may then return the information to the charger 501 .
  • the wireless device may automatically provide the information to the charger 501 periodically or based on a trigger (e.g., when the battery level is below a threshold value, or when a rate of power consumption exceeds a threshold value).
  • the wireless device may periodically update relevant information such as running applications, battery status, and location to the charger 501 .
  • the charger 501 reports this information collected from the client to an admin interface of the cloud processing system 550.
  • An example of the admin interface of the cloud processing system 550 is shown in Figure 6.
  • the admin interface 600 includes general charging details 615 for a selected wireless device.
  • the general charging details include the selected wireless devices charging status (e.g., not charging, charging, fully charged) and the battery level of the selected wireless device.
  • the admin interface 600 further includes voltage information 620 for a selected wireless device.
  • the voltage information 620 includes RF voltage, the present battery voltage, and the net voltage. The voltage information 620 may plotted over time to show changes in the wireless device's voltage.
  • the cloud processing system 550 sends information and alerts if power level consumption exceeds a threshold or usual/average value.
  • the cloud processing system 550 may send the alerts to the wireless device, to the charger 501 , and/or as a notification in the admin interface.
  • the alerts may be a visual notification on a display (e.g., a pop-up window), an audio notification (e.g., an alarm), or other type of notification.
  • the cloud processing system 550 also can send recommendations regarding power usage based on previously collected information to the wireless device through the charger 501.
  • the wireless device user or the administrator may monitor the calculated power usage based on hardware, operating system, running apps, or other characteristics of the wireless device. This information may also be beneficial to 3rd party data consumers, such as telecommunication companies, energy companies, and application developers. For example, an application developer may utilize the power usage information to optimize application development across hardware platforms and operating systems.
  • the techniques described herein solve the problem of enabling a charger system to calculate the power consumption requirements for hardware, operating systems and applications consistently across devices that are based on different platforms.
  • operating systems such as iOS
  • the techniques described herein are based on the operating system and client device itself, and not a centralized service, Thus, the techniques described herein provide the power usage information across different hardware, operating systems and applications.
  • the cloud processing system 550 or charger 501 may calculate the power usage information for devices, operating systems, and/or applications.
  • this power usage information is useful for owners of the charger 501 and for owners of the wireless devices so they are aware of the cost incurred and the battery life length for the wireless devices.
  • This power usage information could also be useful for other providers and software developers as a way to optimize hardware and software energy consumption.
  • measuring power consumption and application usage at such a granular level and at such a global scale may be leveraged to uncover trends. For example, if power consumption increases across many wireless devices at one time, this could be an indication of a specific event many user are experiencing. For example, if the power consumption for a specific application (e.g., a weather application) increases for many wireless devices, this could mean that users are experiencing an issue with that application (e.g., a major weather issue).
  • a specific application e.g., a weather application
  • the same power usage information is useful for understanding usage habits of users which allows for customizing services and providing more targeted advertising. For example, if a user's battery performance starts degrading, it is possible to notify them that it is time to change the battery and to recommend a battery that meets his or her needs.
  • Figs. 7 A and 7B are flow diagrams illustrating example processes 700A and 700B, respectively, facilitating calculation of power consumption of wireless devices, according to various embodiments.
  • An application and/or software module having instructions included therein can be executed by one or more processors of the wireless device to cause the wireless device, in conjunction with a power receiver client such as, for example, client 103 of Figure 1 , to perform the example process 700A.
  • the wireless device can be any wireless device such as, for example, wireless device 102 of Figure 1.
  • An application and/or software module having instructions included therein can be executed by one or more processors of a cloud processing system such as, for example, cloud processing system 550 of Figure 5, directing the cloud processing system to perform the example process 700B.
  • process 700A illustrates a flow diagram showing an example process 700A facilitating calculation of power consumption of a wireless device in a wireless power delivery environment, according to an embodiment.
  • the wireless device accesses one or more Application Program Interfaces (APIs) on the wireless device to gather information related to the wireless device.
  • APIs Application Program Interfaces
  • the information can include a device manufacturer name or ID, device model, battery type/model, hardware, operating system, attached devices (e.g., wirelessly connected keyboard/mouse), etc.
  • the information can also include periodic updates on applications currently running or executing on the wireless device, current battery level of the primary battery of the wireless device, the wireless device's current/past locations, etc.
  • the wireless device monitors the applications executing on the wireless device (e.g., those applications that are running or have a footprint in RAM).
  • the wireless device determines if a trigger is detected.
  • the trigger can be configured to occur periodically. Alternatively or additionally, the trigger can occur if, for example, a threshold level of power is crossed (either the power dips below low power threshold or power increases to or above upper power threshold).
  • the wireless device gathers power information about the wireless device and, at process 718A, provides the power information to a charger.
  • process 700B illustrates a flow diagram showing an example process 700B facilitating calculation of power consumption of a wireless device in a wireless power delivery environment, according to an embodiment.
  • a wireless charger receives power information from a wireless device and transfers the information to a cloud processing system.
  • a cloud processing system receives power information from a wireless device and transfers the information to a cloud processing system.
  • some or all of the processes or steps discussed can alternatively or additionally be performed by a charger in other embodiments.
  • the cloud processing system receives the information associated with the wireless device.
  • the cloud processing system calculates power usage of the client based on the information. The power usage may be calculated based on a discharge/charge curve for the particular battery in the wireless device, as described above.
  • the cloud processing system determines if a trigger has been detected.
  • the trigger can be configured to occur periodically. Alternatively or additionally, the trigger can occur if, for example, a threshold level of power is crossed (either the power dips below low power threshold or power increases to or above upper power threshold).
  • the cloud processing system responsively provides power usage information corresponding to the wireless device to an administer and, at process 718B, to the charger.
  • the administrator may use the power usage information to detect problems with the charging of wireless devices. For example, if power delivery from a charger to all its associated wireless devices drops over time, the administrator may be able to determine whether something is wrong with that particular charger, or whether something in the charger's environment has changed.
  • the process may also branch at process 712B to process 720B where the cloud processing system aggregates data received from multiple devices and, at process 722B, processes the data to identify various trends across geographies, chargers, environments, devices, etc.
  • the cloud processing system provides the aggregated data and or the trend data to a data consumer such as, for example, a 3rd party data consumer 510.
  • the data consumer may provide use the aggregated data to provide additional services for the administrator or the users of the wireless devices. For example, if the aggregated data indicates that 100% allocation of power delivery cycles can't keep up with the charge needs of the wireless devices, the data consumer may offer a larger or second charger to the administrator of the charger.
  • FIG. 8 depicts a block diagram illustrating example components of a representative client (e.g., mobile device, tablet computer, category controller, maintenance controller, etc.) 800 in the form of a mobile (or smart) phone or tablet computer device.
  • a representative client e.g., mobile device, tablet computer, category controller, maintenance controller, etc.
  • Various interfaces and modules are shown with reference to Figure 8, however, the mobile device or tablet computer does not require all of modules or functions for performing the functionality described herein.
  • various components are not included and/or necessary for operation of the category controller.
  • components such as GPS radios, cellular radios, and accelerometers may not be included in the controllers to reduce costs and/or complexity.
  • components such as ZigBeeTM radios and RFID transceivers, along with antennas, can populate the Printed Circuit Board.
  • Figure 9 depicts a diagrammatic representation of a machine, in the example form, of a computer system 900 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • the computer system 900 can be representative of any computer system, server, etc., described herein.
  • the computer system 900 includes a processor (CPU), memory, non-volatile memory, and an interface device. Various common components (e.g., cache memory) are omitted for illustrative simplicity.
  • the computer system 900 is intended to illustrate a hardware device on which any of the components depicted in the example of Figure 1 (and any other components described in this specification) can be implemented.
  • the computer system 900 can be of any applicable known or convenient type.
  • the components of the computer system 900 can be coupled together via a bus or through some other known or convenient device.
  • the processor may be, for example, a conventional microprocessor such as an Intel x86-based microprocessor.
  • Intel x86-based microprocessor One of skill in the relevant art will recognize that the terms "machine-readable (storage) medium” or “computer-readable (storage) medium” includes any type of device that is accessible by the processor.
  • the memory is coupled to the processor by, for example, a bus.
  • the memory can include, by way of example but not limitation, random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), flash RAM, etc.
  • RAM random access memory
  • DRAM dynamic RAM
  • SRAM static RAM
  • flash RAM etc.
  • the memory can be local, remote, or distributed.
  • the bus also couples the processor to the non-volatile memory and drive unit.
  • the non-volatile memory is often a magnetic floppy or hard disk, a magnetic- optical disk, an optical disk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory during execution of software in the computer 13.
  • the nonvolatile storage can be local, remote, or distributed.
  • the non-volatile memory is optional because systems can be created with all applicable data available in memory.
  • a typical computer system will usually include at least a processor, memory, and a device (e.g., a bus) coupling the memory to the processor.
  • Software is typically stored in the non-volatile memory and/or the drive unit. Indeed, for large programs, it may not even be possible to store the entire program in the memory. Nevertheless, it should be understood that for software to run, if necessary, it is moved to a computer readable location appropriate for processing, and for illustrative purposes, that location is referred to as the memory herein. Even when software is moved to the memory for execution, the processor will typically make use of hardware registers to store values associated with the software, and local cache that, ideally, serves to speed up execution.
  • the bus also couples the processor to the network interface device.
  • the interface can include one or more of a modem or network interface. It will be appreciated that a modem or network interface can be considered to be part of the computer system.
  • the interface can include an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (e.g.
  • the interface can include one or more input and/or output devices.
  • the I/O devices can include, by way of example but not limitation, a keyboard, a mouse or other pointing device, disk drives, printers, a scanner, and other input and/or output devices, including a display device.
  • the display device can include, by way of example but not limitation, a liquid crystal display (LCD), OLED, or some other applicable known or convenient display device. For simplicity, it is assumed that controllers of any devices not depicted reside in the interface.
  • the computer system 1300 can be controlled by operating system software that includes a file management system, such as a disk operating system.
  • a file management system such as a disk operating system.
  • operating system software with associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Washington, and their associated file management systems.
  • Windows® is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Washington, and their associated file management systems.
  • Windows® from Microsoft Corporation of Redmond, Washington
  • Windows® Windows® from Microsoft Corporation of Redmond, Washington
  • Linux operating system is the Linux operating system and its associated file management system.
  • the file management system is typically stored in the non-volatile memory and/or drive unit and causes the processor to execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non-volatile memory and/or drive unit.
  • the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine may operate in the capacity of a server or a client machine in a client-server network environment or as a peer machine in a peer-to-peer (or distributed) network environment).
  • the machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a smart phone a processor, a telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA personal digital assistant
  • machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
  • the term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
  • machine-readable storage media machine-readable media, or computer-readable (storage) media
  • recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
  • CD ROMS Compact Disk Read-Only Memory
  • DVDs Digital Versatile Disks
  • transmission type media such as digital and analog communication links.

Landscapes

  • Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

La présente invention concerne diverses techniques permettant de calculer une consommation d'énergie dans des systèmes de distribution sans fil. Dans un exemple, une consommation d'énergie est calculée par réception d'informations associées à au moins un dispositif portable, identification d'une courbe de charge/décharge associée à au moins une batterie dans ledit dispositif portable, et calcul de consommation d'énergie dudit dispositif portable au moins en partie sur la base des informations reçues et de la courbe de charge/décharge identifiée.
PCT/US2016/026819 2015-04-10 2016-04-08 Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil WO2016164846A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020177032538A KR20180050601A (ko) 2015-04-10 2016-04-08 무선 전력 전달 시스템에서 전력 소비를 계산하는 기법
EP16836076.6A EP3281273A4 (fr) 2015-04-10 2016-04-08 Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil
CN201680033396.7A CN108141045B (zh) 2015-04-10 2016-04-08 计算无线电力递送系统中的功耗
JP2017552049A JP2018516041A (ja) 2015-04-10 2016-04-08 無線電力供給システムにおける消費電力の計算

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201562146233P 2015-04-10 2015-04-10
US62/146,233 2015-04-10
US201562163964P 2015-05-19 2015-05-19
US62/163,964 2015-05-19
US201562256694P 2015-11-17 2015-11-17
US62/256,694 2015-11-17

Publications (2)

Publication Number Publication Date
WO2016164846A1 true WO2016164846A1 (fr) 2016-10-13
WO2016164846A8 WO2016164846A8 (fr) 2018-01-25

Family

ID=57072733

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2016/026819 WO2016164846A1 (fr) 2015-04-10 2016-04-08 Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil
PCT/US2016/026824 WO2016164851A1 (fr) 2015-04-10 2016-04-08 Charge sans fil ayant de multiples moyens de réception d'énergie sur un dispositif sans fil

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US2016/026824 WO2016164851A1 (fr) 2015-04-10 2016-04-08 Charge sans fil ayant de multiples moyens de réception d'énergie sur un dispositif sans fil

Country Status (5)

Country Link
EP (1) EP3281273A4 (fr)
JP (1) JP2018516041A (fr)
KR (1) KR20180050601A (fr)
CN (1) CN108141045B (fr)
WO (2) WO2016164846A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021531714A (ja) * 2018-04-25 2021-11-18 オッシア インコーポレイテッド 指向性無線電力および無線データ通信
EP3836350A4 (fr) * 2019-03-15 2022-03-23 OMRON Corporation Système de transmission d'énergie sans fil

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10164473B2 (en) * 2016-02-15 2018-12-25 Semiconductor Components Industries, Llc System and method for device charging
RU2658332C1 (ru) 2017-08-04 2018-06-20 Самсунг Электроникс Ко., Лтд. Система беспроводной передачи мощности для среды с многолучевым распространением
US11979038B2 (en) * 2019-03-07 2024-05-07 Google Llc Wireless charging alignment
JP7087210B2 (ja) * 2019-04-10 2022-06-20 オシア インク． 簡略化されたワイヤレス動力レシーバアーキテクチャ
EP4026226A1 (fr) * 2019-09-06 2022-07-13 Carrier Corporation Charge sans fil de batteries de dispositifs d'accès
EP3934057B1 (fr) * 2020-04-29 2024-03-20 Huawei Digital Power Technologies Co., Ltd. Extrémité de transmission de charge sans fil sur une longue distance, extrémité de réception et système
CN113438635A (zh) * 2021-06-29 2021-09-24 展讯通信（上海）有限公司 蓝牙通信方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080122297A1 (en) * 2006-11-24 2008-05-29 Semiconductor Energy Laboratory Co., Ltd. Wireless Power Supply System and Wireless Power Supply Method
KR20110088100A (ko) * 2010-01-28 2011-08-03 주식회사 팬택 무선전력 송수신을 위한 시스템, 단말장치, 관리서버 및 전송장치
US20110225073A1 (en) * 2010-03-12 2011-09-15 Samsung Electronics Co., Ltd. Apparatus and method for performing wireless charging
US20120220350A1 (en) * 2009-02-26 2012-08-30 Research In Motion Limited Method and Apparatus for Dynamic Battery Management Control in a Mobile Communication Device
JP2015050719A (ja) * 2013-09-03 2015-03-16 Kddi株式会社 充電器から所定情報を読み取る携帯型情報機器、システム、プログラム及び方法

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN2666013Y (zh) * 2003-10-31 2004-12-22 宏碁股份有限公司 非接触感应式的手持装置充电装置
TW200904015A (en) * 2007-03-15 2009-01-16 Powercast Corp Multiple frequency transmitter, receiver, and systems thereof
US8111042B2 (en) * 2008-08-05 2012-02-07 Broadcom Corporation Integrated wireless resonant power charging and communication channel
US8401595B2 (en) * 2008-12-08 2013-03-19 Samsung Electronics Co., Ltd. Method and system for integrated wireless power and data communication
US8682261B2 (en) * 2009-02-13 2014-03-25 Qualcomm Incorporated Antenna sharing for wirelessly powered devices
CN102823109B (zh) * 2010-04-13 2015-01-28 富士通株式会社 电力供给系统、送电器及受电器
CN102347640B (zh) * 2011-06-09 2013-09-18 东南大学 一种无线能量传输装置
JP2013026813A (ja) * 2011-07-21 2013-02-04 Sharp Corp 機器情報取得システム
KR101253670B1 (ko) * 2011-09-05 2013-04-11 엘에스전선 주식회사 다중 안테나를 이용한 무선 전력 전송 장치 및 그 제어 방법
US10103582B2 (en) * 2012-07-06 2018-10-16 Energous Corporation Transmitters for wireless power transmission
JP6126373B2 (ja) * 2012-12-13 2017-05-10 パナソニック株式会社 無線モジュール及び無線通信装置
KR20160013842A (ko) * 2013-02-28 2016-02-05 파워매트 테크놀로지스 엘티디. 전기장치용 분산 무선전력 전송 네트워크의 관리 시스템들 및 관리방법들
US9362778B2 (en) * 2013-03-14 2016-06-07 Robert Bosch Gmbh Short distance wireless device charging system having a shared antenna
KR101767804B1 (ko) * 2013-03-26 2017-08-11 후지쯔 가부시끼가이샤 무선 전력 전송 시스템 및 무선 전력 전송 방법
WO2015022690A1 (fr) * 2013-08-15 2015-02-19 Humavox Ltd. Dispositif de charge sans fil
CN104360270A (zh) * 2014-10-22 2015-02-18 成都西可科技有限公司 一种便携式电子设备的电池充电曲线采集装置与方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080122297A1 (en) * 2006-11-24 2008-05-29 Semiconductor Energy Laboratory Co., Ltd. Wireless Power Supply System and Wireless Power Supply Method
US20120220350A1 (en) * 2009-02-26 2012-08-30 Research In Motion Limited Method and Apparatus for Dynamic Battery Management Control in a Mobile Communication Device
KR20110088100A (ko) * 2010-01-28 2011-08-03 주식회사 팬택 무선전력 송수신을 위한 시스템, 단말장치, 관리서버 및 전송장치
US20110225073A1 (en) * 2010-03-12 2011-09-15 Samsung Electronics Co., Ltd. Apparatus and method for performing wireless charging
JP2015050719A (ja) * 2013-09-03 2015-03-16 Kddi株式会社 充電器から所定情報を読み取る携帯型情報機器、システム、プログラム及び方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2021531714A (ja) * 2018-04-25 2021-11-18 オッシア インコーポレイテッド 指向性無線電力および無線データ通信
JP7089060B2 (ja) 2018-04-25 2022-06-21 オッシア インコーポレイテッド 指向性無線電力および無線データ通信
EP3836350A4 (fr) * 2019-03-15 2022-03-23 OMRON Corporation Système de transmission d'énergie sans fil

Also Published As

Publication number Publication date
WO2016164846A8 (fr) 2018-01-25
WO2016164851A1 (fr) 2016-10-13
EP3281273A4 (fr) 2019-11-27
CN108141045B (zh) 2019-10-25
KR20180050601A (ko) 2018-05-15
JP2018516041A (ja) 2018-06-14
CN108141045A (zh) 2018-06-08
EP3281273A2 (fr) 2018-02-14

Similar Documents

Publication Publication Date Title
US10574081B2 (en) Calculating power consumption in wireless power delivery systems
EP3281273A2 (fr) Calcul de consommation d'énergie dans des systèmes de distribution d'énergie sans fil
US10587154B2 (en) Techniques for scheduling delivery of wireless power in wireless power delivery environments
US10559275B2 (en) Inferring battery status of an electronic device in a wireless power delivery environment
US20210249910A1 (en) Techniques for facilitating beacon sampling efficiencies in wireless power delivery environments
US9620996B2 (en) Wireless charging with multiple power receiving facilities on a wireless device
US10566852B2 (en) Establishing connections with chargers in multi-charger wireless power delivery environments
US20190020199A1 (en) Removably Attachable Portable Device Apparatus With Integrated Wireless Power Receiving Facilities
US10256670B2 (en) Wireless power transceivers for supplementing wireless power delivery and extending range
US20200127704A1 (en) Wireless Power Enabled Electronic Shelf Label
US20230369897A1 (en) Wireless Power Transmission System Operations In Multi-Signal Environments

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017552049

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20177032538

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2016836076

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16836076

Country of ref document: EP

Kind code of ref document: A2