JP2018516041A - Calculation of power consumption in wireless power supply system - Google Patents

Abstract

Various techniques for calculating power consumption in a wireless supply system are described herein. In one example, the power consumption receives information related to at least one portable device, identifies a discharge / charge curve associated with at least one battery in the at least one portable device, and receives information and the identified discharge / charge. Calculated by calculating power consumption of at least one portable device based at least in part on the curve.

Description

CROSS REFERENCE TO RELATED APPLICATIONS This application is entitled “INTEGRATED CHIPS INCORPORTING TRANSPORTIVE COMPONENTS FOR REMOTE WIRELESS POWER DELIVERY AND FOR RECEIVING WIRELES 62 US Patent Application No. 4/69”, filed on November 17, 2015. , US Provisional Patent Application No. 62 / 163,964 entitled “SYSTEMS AND METHODS FOR WIRELESS CHARGING” filed on May 19, 2015, and “SYSTEMS AND METHODS FOR” filed on April 10, 2015. US Provisional Patent Application No. 62 entitled “WIRELESS CHORGING” / 146,233, all of which are hereby incorporated by reference.

  This application was filed on April 8, 2016, US Patent Application _________________________ R. R. on the date of April, 2016 on April 8, 2016, from US Patent Application _______________ US patent application _________ entitled "STATUS OF AN ELECTRONIC DEVICE IN A WIRELESS POWER DELIVERY", filed on April 8, 2016 US Patent Application No. _______________________________________N U.S. Patent Application No. 15 / 092,026 TE filed on April 6, 2016, filed on April 6, 2016, entitled "ESTABLISHING CONNECTIONS WITH CHARGERS IN MULTI-CHARGER WIRELESS POWER DELIVERY ENVIRONMENTS" FOR DELIVER US Patent Application No. 15 / 091,986, entitled “ING RETRODIVERIVE WIRELESS POWER”, US Patent Application No. 15 / 048,982, 2016 entitled “WIRELESS CHARGEABLE BATTERY APPARATUS” filed on February 19, 2016 US Patent Application No. 15 / 048,984, filed on February 2, 2015, on the date of “REMOVABLE ATTACHABLE PORTABLE DEVICE APPARATUS WITH INTEGRATED WIRELESS POWER RECEIVING FACILITES” filed on February 2, 2015 BEACON SIGN US Patent Application No. 14 / 956,673 entitled “ALS IN WIRELESS POWER DELIVERY ENVIRONMENTS”, “TECHNIQUES FOR IMAGE WIRE RELATIONS ENVIRONMENTS US patent application filed on November 19, 2015” No. 14 / 945,741, U.S. Patent Application No. 14 / 945,783, filed Oct. 29, 2015, filed Nov. 19, 2015, entitled “WIRELESS POWERED ELECTRONIC DISPLAY APPARATIES”. TECHNIQUES FOR FILTERI Related to U.S. Patent Application Serial No. 14 / 926,014 entitled G MULTI-COMPONENT SIGNALS ", all of which are incorporated by reference in their entirety herein.

  The techniques described herein generally relate to the field of wireless communication and power transmission, such as wireless power supply systems and clients for receiving wireless power.

  Many portable electronic devices are powered by batteries. Rechargeable batteries are often used to avoid the cost of replacing traditional dry batteries and saving valuable resources. However, charging a battery with a conventional rechargeable battery charger requires connection to an alternating current (AC) power outlet, which may not be available or may be inconvenient. It is therefore desirable to obtain battery charger power from electromagnetic radiation.

(No corresponding description)

(No corresponding description)

  Accordingly, there is a need for techniques that overcome the above-mentioned problems and that provide additional benefits. The examples provided herein and some of the limitations associated therewith of some previous or related systems are intended to be illustrative and not exclusive. Other limitations of existing or conventional systems will become apparent to those skilled in the art upon reading the following detailed description.

  Overall, the examples herein and some of the limitations associated therewith of some preceding or related systems are intended to be illustrative and not exclusive. Other limitations of existing or conventional systems will become apparent to those skilled in the art upon reading the following.

One or more embodiments of the invention are shown by way of example and are not limited to the figures of the accompanying drawings in which like reference numerals indicate like elements.

FIG. 2 illustrates an example wireless power supply environment illustrating wireless power supply from one or more wireless transmitters to various wireless devices within the wireless power supply environment. FIG. 6 is a sequence diagram illustrating an exemplary operation between a wireless transmitter and a power receiving client for initiating wireless power supply. FIG. 2 is a block diagram illustrating an exemplary wireless power receiver (client) according to one embodiment. 1 is an overview of a system illustrating various components of various embodiments described herein. FIG. FIG. 3 illustrates an exemplary environment including a cloud processing system configured to calculate power consumption of wireless devices in a power distribution domain, according to various embodiments. FIG. 3 illustrates an example administrator interface for a cloud processing system, according to various embodiments. FIG. 7 is a flow diagram illustrating an example process that facilitates calculating power consumption of a wireless device in accordance with various embodiments. FIG. 7 is a flow diagram illustrating an example process that facilitates calculating power consumption of a wireless device in accordance with various embodiments. FIG. 6 is a diagrammatic representation of a machine in an exemplary form of a computer system in which a set of instructions is executed to cause the machine to perform any one or more methods described herein. FIG. 6 is a diagrammatic representation of a machine in an exemplary form of a computer system in which a set of instructions is executed to cause the machine to perform any one or more methods described herein.

  The following description and drawings are illustrative and should not be construed as limiting. Numerous specific details are set forth in order to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to “one embodiment” or “an embodiment” of this disclosure may, but need not, be a reference to the same embodiment, and such a reference may refer to at least one of the embodiments. means.

  As used herein, “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. The phrase “in one embodiment” appears in various places throughout the specification, but not necessarily all referring to the same embodiment, and this phrase is a separate and mutually exclusive phrase from the other embodiments. It is not an embodiment or an alternative embodiment. In addition, various features are described that may be exhibited by some embodiments but not others. Similarly, various requirements are described which are requirements of some embodiments but not other embodiments.

  The terms used in this specification generally have their ordinary meanings in the art, within the context of this disclosure and in the specific context where each term is used. Certain terms used to describe the present disclosure are discussed below or elsewhere in the specification to provide additional guidance to the engineer for describing the present disclosure. For convenience, certain terms may be highlighted using italics and / or quotation marks and the like. The use of highlighting does not affect the scope and meaning of the terms, and the scope and meaning of the terms are the same in the same context, whether or not they are highlighted. It will be appreciated that the same can be said for multiple methods.

  Accordingly, alternative languages and synonyms may be used for any one or more of the terms described herein, and the time when the terms are detailed or described herein is not particularly important. Synonyms for specific terms are provided. A detailed description of one or more synonyms does not exclude the use of other synonyms. The use of any examples in any part of this specification, including examples of any terms described herein, is merely exemplary and is within the scope and meaning of this disclosure or the scope and meaning of any term It is not intended to further limit. Similarly, the present disclosure is not limited to the various embodiments described herein.

  Without further limiting the scope of the present disclosure, examples of instruments, devices, methods and their associated results according to embodiments of the present disclosure are described below. Note that titles or subtitles may be used in the examples for the convenience of the reader and are not intended to limit the scope of the disclosure in any way. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure relates. In case of conflict, the present document, including definitions, will control.

  Embodiments of the present disclosure have self-contained, attached and / or integrated power receiving clients (also referred to herein as “wireless power receivers” or “clients”) from one or more chargers (this book). The description describes various techniques for wireless charging and / or wireless power supply to one or more wireless devices (also referred to as “devices” or “target devices”).

  The techniques described herein provide power, data, or both using wireless technologies. In some embodiments, power, data or both power and data may be supplied simultaneously as a continuous composite waveform, as a pulse waveform, as multiple overlapping waveforms, or as a combination or variation thereof. Power and data may be supplied using the same or different radio technologies.

  The wireless technology described herein may be applied not only to electromagnetic (EM) waves, but also to other forms of sound waves and / or periodic excitation (eg, phonons). The EM wave may include radio waves, microwaves, infrared rays, visible rays, ultraviolet rays, X-rays and / or gamma rays. The sound waves may include very low frequency sound waves, acoustic waves and / or ultrasound waves. The techniques described herein may utilize multiple radio technologies and / or multiple frequency spectra simultaneously within radio technology to provide power, data, or both power and data.

Wireless technology may include dedicated hardware components for supplying power and / or data. Dedicated hardware components may be modified based on the radio technology or combination of radio technologies being utilized. For example, when applied to sound waves, the system uses a microphone and speaker rather than an antenna.
System overview / structure

  FIG. 1 is a diagram illustrating an example wireless communication / power supply environment 100 that illustrates wireless power supply from one or more wireless transmitters 101 to various wireless devices 102 within the wireless communication / power supply environment. More specifically, FIG. 1 shows wireless power and / or data as one or more power receiving clients 103.1-103 (also referred to herein as "wireless power receivers" or "wireless power clients"). . n available wireless devices 102.1 to 102.n. 1 illustrates an exemplary wireless power supply environment 100 that can be supplied to n. The wireless power receiver is configured to receive wireless power from one or more wireless transmitters 101.

  As shown in the example of FIG. 1, the wireless devices 102.1 to 102. n are mobile phone devices 102.2 and 102. n, and the wireless game controller 102.1, the wireless devices 102.1 to 102. n requires power and one or more integrated power receiving clients 103.1 to 103.n. It can be any (smart or dumb) wireless device or system that can receive wireless power via n. A smart device is an electronic device that can communicate (eg, using WiFi) and transmit a beacon signal. The dam type device is an electronic device such as a passive device that does not communicate (for example, does not have a Bluetooth (registered trademark) function or a WiFi function) and does not transmit a beacon signal. As described herein, one or more integrated power receiving clients or “wireless power receivers” are connected to one or more transmitter / transmitters 101. a to 101. n receive and process power from the wireless device 102.1 to 102.102 for operation. n.

  Each transmitter 101 (also referred to herein as a “charger”, “array of antennas” or “antenna array system”) includes a plurality of antennas 104, such as an antenna array including hundreds or thousands of spaced antennas, for example. Each antenna can supply wireless power to the wireless device 102. Each transmitter 101 may also supply a wireless communication signal to the wireless device 102. In some embodiments, wireless power and wireless communication signals may be provided as a combined power / communication signal. Indeed, although the detailed description provided herein focuses on transmitting power wirelessly, aspects of the invention are equally applicable to transmitting data wirelessly.

  In some embodiments, the antenna is an adaptively phased radio frequency antenna and transmitter 101 is described in US Pat. No. 8,558,661, US Pat. No. 8,159,364, US Pat. No. 8,409,953. , U.S. Patent No. 8446248, U.S. Patent No. 8854176, U.S. Patent Application No. 14 / 461,332 and U.S. Patent Application No. 14 / 815,893. Utilizes the novel phase shifting algorithm described. The transmitter 101 can determine the appropriate phase to supply a coherent power transmission signal to the power receiving client 103. The array is configured to emit signals (eg, continuous wave signals or pulsed power transmission signals) from multiple antennas at specific phases relative to each other.

  In addition, the transmitter 101 provides a time-delayed retro-directional radio frequency (RF) that provides wireless RF power that matches the client antenna pattern (polarization, shape of each lobe and power level) in a three-dimensional (3D) space. A holographic array may be included. It is understood that use of the term “array” does not necessarily limit the antenna array to a particular array structure. That is, the antenna array need not be configured in a particular “array” shape or geometric shape. Further, as used herein, the term “array” or “array system” is intended to include associated peripheral circuitry for generating, receiving, and transmitting signals such as radios, digital logic, and modems. May be used.

  The wireless device 102 may include one or more power receiving clients 103 (also known as “wireless power receivers”). As shown in the example of FIG. 1, a power supply antenna 104a and a data communication antenna 104b are shown. The power supply antenna 104a is configured to supply radio frequency power in a wireless power supply environment. The data communication antenna includes the power receiving clients 103.1 to 103 and / or the wireless devices 102.1 to 102. n is configured to send and receive data communications with n. In some embodiments, the data communication antenna can communicate via Bluetooth®, WiFi, ZigBee®, or other wireless communication protocols.

  Each power receiving client 103.1 to 103. n includes one or more antennas (not shown) for receiving signals from the transmitter 101. Similarly, each transmitter 101. a to 101. n includes an antenna array having one or more antennas and / or sets of antennas that can emit continuous wave signals with a particular phase relative to each other. As described above, each array receives a coherent signal as a power receiving client 102.1-102. An appropriate phase can be determined for transmission to n. The coherent signal can be determined, for example, by calculating the complex conjugate of the received beacon signal at each antenna of the array, so that the coherent signal is appropriately phased for the particular power receiving client that transmitted the beacon signal. The The beacon signal, referred to herein primarily as a continuous waveform, can alternatively or additionally take the form of a modulated signal.

  Although not shown, each component of the environment, such as a wireless power receiver, transmitter, etc., can include a mechanism for control and synchronization, such as a data communication synchronization module. Transmitter 101. a to 101. n is connected to a power source such as a power outlet or power source that connects the transmitter to a standard or primary alternating current (AC) power source in the building, for example. Alternatively or additionally, one or more transmitters 101. a to 101. n can be powered through a battery or other power supply mechanism.

  In some embodiments, the power receiving clients 102.1-102. n and / or transmitter 101. a to 101. n uses a reflective object 106, such as a wall or other RF reflective obstacle in range to transmit beacon signals within a wireless power supply environment and supply and / or receive wireless power and / or data, or This reflective object 106 is faced. The reflective object 106 can be utilized for multidirectional signal communication regardless of whether the obstructing object is in line of sight between the transmitter and the power receiving client.

  As described herein, each wireless device 102.1-102. n can be any system and / or device and / or any combination of devices / systems that can establish connections with other devices, servers and / or other systems in exemplary environment 100. May be. In some embodiments, the wireless devices 102.1-102. n includes a display or other output function for presenting data to the user, and / or an input function for receiving data from the user. As an example, the wireless device 102 may be a video game controller, a server desktop, a desktop computer, a computer cluster, such as a notebook, laptop computer, portable computer, mobile phone, smartphone, battery or battery-connected component, PDA, etc. The mobile computing device may be, but is not limited to. The wireless device 102 may be any wearable terminal such as a watch, a necklace, a ring, or a terminal built into a customer. Other examples of wireless device 102 include, but are not limited to, safety sensors (eg, fire or carbon monoxide), electric toothbrushes, electronic door locks / handles, light switch controllers, electric shavers, and the like.

  Although not shown in the example of FIG. 1, the transmitter 101 and the power receiving clients 103.1 to 103. Each n can include a data communication module for communicating via a data channel. Alternatively or additionally, the power receiving clients 103.1 to 103. n is a wireless device 102.1-102.n to communicate with a transmitter via an existing data communication module. n can be instructed.

  FIG. 2 is a sequence diagram 200 illustrating exemplary operations between the wireless transmitter 101 and the power receiving client 103 for initiating wireless power supply, according to one embodiment. Initially, communication is established between the transmitter 101 and the power receiving client 103, such as via Bluetooth (registered trademark), WiFi, ZigBee (registered trademark), or other wireless communication protocol. The transmitter 101 then sends a beaconing schedule to the power receiving client 103 to coordinate the beacon transmission schedule and RF power / data supply schedule with this power receiving client and any other power receiving clients. Based on the schedule, the power receiving client 103 transmits a beacon. As illustrated, the transmitter 101 receives a beacon from the power reception client 103 and detects the phase (or direction) at which the beacon signal is received. Next, the transmitter 101 supplies wireless power and / or data to the power receiving client 103 based on the phase (or direction) of the received beacon. That is, the transmitter 101 determines the complex conjugate of the phase and supplies power to the power receiving client 103 in the same direction in which the beacon signal is received from the power receiving client 103 using the complex conjugate.

  In some embodiments, the transmitter 101 includes multiple antennas, one or more of which are used to power the power receiving client 103. The transmitter 101 can detect the phase of the beacon signal received by each antenna. Due to multiple antennas, different beacon signals may be received at each antenna of the transmitter 101. Accordingly, the transmitter is disclosed in U.S. Pat. No. 8,558,661, U.S. Patent Application No. 8159364, U.S. Patent Application No. 8410953, U.S. Patent Application No. 8446248, U.S. Patent Application No. 8854176, And any of the algorithms or processes described in one or more of US Provisional Patent Application No. 62 / 146,233 and US Provisional Patent Application No. 62 / 163,964 may be utilized. An algorithm or process determines the manner in which signals are emitted from one or more antennas, taking into account the effects of multiple antennas in transmitter 101. In other words, the algorithm determines the manner in which signals are emitted from one or more antennas such that the beacon waveform is approximately reproduced but the aggregate signal is generated from the transmitter 101 in the opposite direction.

  FIG. 3 is a block diagram illustrating an exemplary receiver 300 according to one embodiment. Receiver 300 includes control logic 310, battery 320, communication block 330c and associated antenna 370, power meter 340, rectifier 350, beacon signal generator 360 and associated antenna 380, rectifier 350 or beacon signal generator. Various components including a switch 365 that connects 360 to an associated antenna 390. In some embodiments, some or all of the components can be omitted. Additional or fewer components are also possible.

  The rectifier 350 receives a power transmission signal (via one or more client antennas) supplied to the battery 320 via a power meter 340 for charging from a power transmitter. The power meter 340 measures the total received power signal strength and provides this measurement to the control logic 310. The control logic 310 may also receive the battery power level from the battery 320 itself, or may receive battery power data, such as from an operating system API running on the receiver 300. Control logic 310 may also transmit / receive data signals on a data carrier frequency, such as a base signal clock for clock synchronization, via communication block 330. Beacon signal generator 360 transmits a beacon signal or a calibration signal using either antenna 380 or antenna 390. Note that although the battery 320 is shown to be charged by the receiver 300 and to supply power to the receiver 300, the receiver can also receive power directly from the rectifier 350. This may provide a charging current in addition to providing rectifier 350 instead of providing charging to battery 320. Also, the use of multiple antennas is an example of an implementation, and the structure may be reduced to one shared antenna, where the receiver multiplexes signal reception / transmission.

  Optional motion sensor 395 detects motion and sends a signal to control logic 310. For example, if the terminal is receiving power at a high frequency above 500 MHz, the position of the terminal can be a hot spot for (incident) radiation. Thus, if the terminal is worn by a person, the radiation level may exceed the regulations or exceed an acceptable radiation level set by a medical / industry authority. To avoid any excess radiation problems, the terminal may integrate motion detection mechanisms such as accelerometers, auxiliary GPS or other mechanisms. Upon detecting that the terminal is in operation, the disclosed system is assumed to be handled by the user and either stops transmitting power to the power transfer array or is a portion of the power that can tolerate the received power. Signal to the power transfer array to reduce When the terminal is used in a mobile environment such as a car, train or airplane, power is transmitted only intermittently or at a reduced level unless the terminal is about to lose all available power.

FIG. 4 is an overview of the system showing the various possible embodiments and components, but other combinations and variations are possible. As shown, in some embodiments, the wireless power receiver is implemented in a standard battery form factor (eg, AA batteries) (eg, a computer monitor or a television in the vicinity). It may be in the form of an application specific integrated circuit (ASIC) chip in a display device or a mobile phone case.
Method for calculating power consumption in a wireless power supply system

  Techniques for calculating power consumption in a wireless power supply system are disclosed herein. More specifically, a technique for calculating power consumption of devices, operating systems, and applications is disclosed. For example, if multiple mobile phones with different operating systems are being charged via a wireless power supply system, the system will use the power consumption of each mobile phone, the power consumption of each operating system running on each mobile phone , And the power consumption of each particular application running on each mobile phone. For example, if a map application uses GPS and uses a constant data connection to the website (compared to an application that uses GPS and does not use a constant data connection to the website) ) May consume more power. In addition, the user may notice that the mobile phone is running out of charge more rapidly than before, but the reason is unknown. The techniques described herein can facilitate identifying the cause and provide other benefits.

  FIG. 5 is a diagram illustrating an example environment 500 that includes a cloud processing system 550 configured to calculate power consumption of wireless devices in a power distribution area 520, according to various embodiments. As shown in the example of FIG. 5, the exemplary environment 500 includes a cloud processing system 550, a network 560, a plurality of power distribution areas 520, and a plurality of third party data users 510. Each power distribution area 520 includes one or more wireless power transmitters or “chargers” 501 that communicate with the network 560 and an administrator terminal (locally or via the network 560). The charger 501 supplies wireless power to various wireless devices as described herein.

  As shown in FIG. 5, the cloud processing system 550 includes a plurality of servers 540 and a data repository 530. Any number of servers 540 and / or data repositories 530 may be included in the cloud processing system 550. The cloud processing system 550 is configured to calculate the power usage of the wireless device in each power distribution area 520.

  More specifically, the wireless device can provide information to the charger 501 through the use of wireless device software that accesses the device's API to collect the information. For example, the charger 501 may send a periodic “client query” message to the client. This message requests the client to return various information to the charger 501. In some examples, the client query message may be a ZigBee message. Alternatively, the wireless device may automatically send information to the charger 501 periodically or based on a trigger (eg, when the battery level is below the threshold or the power consumption rate exceeds the threshold). . The information transmitted to the charger 501 may include a device manufacturer name or ID, a device type, a battery type / type, hardware, an operating system, and the like. This information also includes periodic updates or status of applications currently running on the device, current battery status, device location, RF power received from previous requests, battery internal or external from previous requests. Other information regarding coulombs, equipment temperature, or power usage may be included.

  The charger 501 receives this information and transmits it to the cloud processing system 550 via the network 560. Alternatively, in some embodiments, charger 501 includes a local processing function. Therefore, the cloud processing system 550 or the charger 501 calculates the power usage of the wireless device based on the received information including the power usage based on specific hardware, operating system, application usage, and the like. For example, the cloud processing system 550 or the charger 501 can calculate the power usage of specific hardware using the battery status of the wireless device (eg, internal / external voltage and / or coulomb). In some embodiments, cloud processing system 550 or charger 501 includes a database of battery types used in wireless devices and their associated discharge / charge curves. The cloud processing system 550 or the charger 501 may identify a specific discharge / charge curve from information received from the wireless device (eg, device ID, manufacturer / model number, etc.). The cloud processing system 550 or charger 501 then identifies on the discharge / charge curve where the device's current battery condition is decreasing, thereby charging or depleting that particular battery. Calculate The cloud processing system 550 or charger 501 also tracks the percentage of time spent transmitting power to each wireless device, thereby calculating the amount of power to be supplied to each wireless device.

  In some embodiments, the cloud processing system 550 provides various information and alerts to the user and / or the charger 501. For example, if the power consumption of a specific device exceeds a threshold, a warning may be triggered. The cloud processing system 550 can also recommend power consumption to the user and / or the charger 501 and / or the wireless device. For example, the charger 501 schedules a particular wireless device (“Client 1”) to receive 75% of the charge cycle that is available to the end, but the client 1 has more power than is supplied to the battery. Can report that the battery has been discharged from the battery, the cloud processing system 550 can report to the user “to bring the client 1 closer to the charger”. At the same time, the charger 501 can allocate more charging cycles to other wireless devices that are more efficient in power supply.

  The third party data user 510 may be any entity that can use the collected wireless device information. For example, third party data users 510 may include telecommunications service providers, security service providers, home automation systems, energy companies, application developers (eg, optimizing development via platforms, equipment manufacturers, etc.). it can. In some embodiments, the third party data consumer 510 can purchase aggregate data from the cloud processing system 550 and / or otherwise obtain rights to the aggregate data. For example, the security service provider can use the phase data included in the wireless device information to determine whether there is motion in the power distribution area 520 (eg, instead of accessing motion sensor data). As another example, a home automation system can control a home thermostat using temperature data included in wireless device information.

  The network 560 may be any type of cellular telecommunication network, IP-based telecommunication network, or centralized telecommunication network, such as a global system for mobile communications (GSM), time division multiplexing. Access (TDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDM), General Packet Radio Service (GPRS), Extended Data GSM® Environment (EDGE), Advanced Mobile Phone System (AMPS), Global Interoperability for Microwave Access (WiMAX), Universal Mobile Telecommunications System (UMTS), Advanced Data Optimization (EVDO), Long Term Evolution (LTE), Ultra Mobile Broadband (UMB), Voice・ Over - Internet Protocol (VoIP), including such unlicensed mobile access (UMA), but are not limited to.

  Network 560 is any collection of separate networks that operate in whole or in part to provide connectivity to cloud processing system 550, charger 501 and third party data consumer 510. It may be. In some embodiments, communication between the cloud processing system 550, the charger 501 and the third party data consumer 510 is accomplished by an open network such as the Internet or a private network such as an intranet and / or an extranet. can do.

  Cloud processing system 550, charger 501 and third party data user 510 can be dial-up connections, digital subscriber lines (DSL, ADSL), cable modems, wireless connections, direct fiber connections and / or any other scheme. A connection can be made to a network 560 (eg, the Internet).

  Database 530 can be implemented via object-oriented technology and / or text files and can be managed by any database management system. As shown, the database 530 is connected to the cloud processing system 550 (or is otherwise included in the cloud processing system 550). However, it will be appreciated that in some embodiments, the database 530 may alternatively or additionally be connected directly to the network 560 and / or distributed across multiple systems.

  In some embodiments, as described above, the wireless device has a simple client application installed on its operating system (iOS, Android, etc.). The wireless device first reports device hardware information, operating system device information and / or battery status to the charger 501. For example, the wireless device may receive a ZigBee message requesting information and then send the information back to the charger 501. Alternatively, the wireless device may automatically provide information to the charger 501 periodically or based on a trigger (eg, when the battery level is below the threshold or the power consumption rate exceeds the threshold). . The wireless device may periodically update the charger 501 with related information such as an operating application, a battery state, and a location. The charger 501 reports this information collected from the client to the administrator interface of the cloud processing system 550. An example of the administrator interface of the cloud processing system 550 is shown in FIG.

  As shown in FIG. 6, the administrator interface 600 includes the overall charging details 615 of the selected wireless device. The overall charging details include the state of charge of the selected wireless device (eg, uncharged, charging, fully charged) and the battery level of the selected wireless device. Administrator interface 600 further includes voltage information 620 for the selected wireless device. The voltage information 620 includes the RF voltage, the current battery voltage, and the net voltage. Voltage information 620 may be displayed over time to indicate changes in the voltage of the wireless device.

  Returning to FIG. 5, the cloud processing system 550 transmits information and alerts when the power consumption level exceeds a threshold or normal / average value. The cloud processing system 550 may send a warning to the wireless device, may be sent to the charger 501, and / or may be sent as an administrator interface notification. The alert may be a visual notification (eg, a pop-up window) on the display device, an audio notification (eg, an alarm), or other type of notification. The cloud processing system 550 can also send recommendations regarding power usage based on previously collected information to the wireless device via the charger 501. A user or administrator of the wireless device may monitor the power usage calculated based on the hardware, operating system, running application, or other characteristics of the wireless device. This information is also useful for third party data users such as telecommunications companies, energy companies and application developers. For example, an application developer may utilize power usage information to optimize application development via a hardware platform and operating system.

  Thus, in some embodiments, the techniques described herein allow the charger system to consistently calculate hardware, operating system and application power consumption requirements across devices based on different platforms. Solve the problem.

  In some embodiments, an operating system (such as iOS) may provide a breakdown of battery consumption per application. However, the technology described herein is based on the operating system and the client device itself, not a centralized service. Thus, the techniques described herein provide power usage information through different hardware, operating systems, and applications.

  As described above, the cloud processing system 550 or the charger 501 may calculate power usage information for devices, operating systems, and / or applications. In some embodiments, this power usage information is useful to the owner of the charger 501 and the owner of the wireless device, so the owner knows the cost of generating the wireless device and the battery life. This power usage information can also be useful to other providers and software developers as a way to optimize hardware and software energy consumption. Furthermore, at larger scales, trends can be exploited using measurements of power consumption and application utilization at such a fine and global scale. For example, if power consumption increases across many wireless devices at once, it may be a sign of a particular event that many users are experiencing. For example, if the power consumption of a particular application (eg, weather application) increases for many wireless devices, it may mean that the user is experiencing problems with that application (eg, severe weather problems). .

  In some embodiments, the same power usage information is useful for customizing services and understanding user usage habits that allow for more targeted advertising. For example, when the battery performance of the user starts to deteriorate, it is possible to notify that it is time to replace the battery and to recommend a battery that satisfies the user's needs.

  7A and 7B are flow diagrams that illustrate exemplary processes 700A and 700B, respectively, that facilitate calculating power consumption of a wireless device in accordance with various embodiments. The application and / or software module that includes the instructions may be executed by one or more processors of the wireless device to execute the exemplary process 700A in cooperation with a power receiving client, such as the client 103 of FIG. . The wireless device may be any wireless device such as the wireless device 102 of FIG. Applications and / or software modules that include instructions are executed by one or more processors of a cloud processing system, such as, for example, cloud processing system 550 of FIG. 5, to instruct the cloud processing system to execute exemplary process 700B. can do.

  With reference to FIG. 7A, a process 700A illustrates a flow diagram illustrating an example process 700A that facilitates calculating power consumption of a wireless device in a wireless power supply environment according to one embodiment. First, in process 710A, the wireless device accesses one or more application program interfaces (APIs) on the wireless device to collect information about the wireless device. For example, this information can include the manufacturer name or ID of the device, the device type, battery type / type, hardware, operating system, and attached devices (such as a wirelessly connected keyboard / mouse). This information may also include periodic updates of applications currently running or running on the wireless device, the current battery level of the wireless device's primary battery, the current / past location of the wireless device, and the like.

  In process 712A, the wireless device monitors an application running on the wireless device (eg, an application running in RAM or having a footprint). In decision process 714A, the wireless device determines whether a trigger has been detected. In some embodiments, the trigger can be configured to occur periodically. Alternatively or additionally, a trigger occurs, for example, when the power threshold level crosses (power falls below a low power threshold or power increases to a high power threshold or exceeds a high power threshold). there is a possibility. In process 716A, in response to the trigger, the wireless device collects power information about the wireless device and provides power information to the charger in process 718A.

  With reference to FIG. 7B, a process 700B illustrates a flow diagram illustrating an example process 700B that facilitates calculating power consumption of a wireless device in a wireless power supply environment according to one embodiment. First, the wireless charger receives power information from the wireless device and transfers the information to the cloud processing system. As mentioned above, some or all of the described processes or steps may alternatively or additionally be performed by a charger in other embodiments.

  In process 710B, the cloud processing system receives information related to the wireless device. In process 712B, the cloud processing system calculates the client's power usage based on the information. As described above, the power consumption can be calculated based on the discharge / charge curve of a specific battery in the wireless device. Next, in decision process 714B, the cloud processing system determines whether a trigger has been detected. In some embodiments, the trigger can be configured to occur periodically. Alternatively or additionally, a trigger occurs, for example, when the power threshold level crosses (power falls below a low power threshold or power increases to a high power threshold or exceeds a high power threshold). there is a possibility. When the trigger occurs, the cloud processing system provides the power usage information corresponding to the wireless device to the administrator in process 716B with good responsiveness and provides the charger in process 718B with good responsiveness. In some examples, an administrator may use power usage information to detect problems with charging a wireless device. For example, if the power supply from a charger to all associated wireless devices decreases over time, the administrator can determine if there is a problem with that particular charger or if there is a change in the charger environment. Can be determined.

In some embodiments, the process may branch to process 720B at process 712B, where the cloud processing system aggregates data received from multiple devices and processes this data at process 722B to provide geography. Identify various trends, such as charger, environment, equipment. Once identified, in process 724B, the cloud processing system provides aggregate data and / or trend data to a data user, such as third party data user 510, for example. In some examples, the data consumer may use the aggregated data to provide additional services for a wireless device administrator or user. For example, if the aggregate data indicates that even if the 100% power supply cycle is allocated, the wireless device cannot meet the need for charging, the data user can choose a larger charger or a second charger. It may be provided to the administrator of the charger.
Exemplary computer system

  FIG. 8 is a block diagram illustrating exemplary components of a representative client (eg, mobile device, tablet computer, category controller, maintenance controller, etc.) 800 in the form of a mobile phone (or smartphone) or tablet computer device. FIG. Although various interfaces and modules are illustrated with reference to FIG. 8, a mobile device or tablet computer does not require all the modules or functions to perform the functions described herein. It will be appreciated that in many embodiments, the operation of a category controller does not include various components and / or these components are not required. Components such as GPS radios, cellular radios, accelerometers, etc. may not be included in the controller to reduce cost and / or complexity. Furthermore, components such as a ZigBee (registered trademark) radio and an RFID transceiver can be mounted on a printed circuit board together with an antenna.

  FIG. 9 illustrates a schematic representation of a machine in an exemplary form of a computer system 900 upon which a set of instructions are executed to cause the machine to perform any one or more methods described herein. FIG. Computer system 900 may represent any computer system, server, etc. described herein.

  In the example of FIG. 9, the computer system 900 includes a processor (CPU), memory, non-volatile memory, and interface equipment. For the sake of simplicity, various common components (eg, cache memory) are omitted. Computer system 900 is intended to represent a hardware device that can implement any of the components shown in the example of FIG. 1 (and any other components described herein). Computer system 900 may be of any applicable known or convenient type. The components of the computer system 900 can be connected together via a bus or other known or convenient device.

  The processor may be a conventional microprocessor such as, for example, an Intel 86-based microprocessor. Those skilled in the art will recognize that the term “machine-readable (storage) medium” or “computer-readable (storage) medium” includes any type of device accessible by a processor.

  The memory is connected to the processor by a bus, for example. By way of example and not limitation, the memory can include random access memory (RAM) such as dynamic RAM (DRAM), static RAM (SRAM), flash RAM, and the like. The memory may be local memory, remote memory or distributed memory.

  The bus also connects the processor to the non-volatile memory and drive unit. Non-volatile memory is often a magnetic floppy or hard disk, magneto-optical disk, optical disk, CD-ROM, EPROM or EEPROM, such as an EEPROM, magnetic card or optical card, or another for large amounts of data Format storage device. Some of this data is often written to memory by a direct memory access process during execution of software in the computer 13. The non-volatile storage device may be local, remote, or distributed. Nonvolatile memory is optional because the system can be built using all applicable data available in memory. A typical computer system typically includes at least a processor, memory, and equipment (eg, a bus) that connects the memory to the processor.

  Software is typically stored in non-volatile memory and / or drive units. In fact, for large programs, it may not even be possible to store the entire program in memory. Nevertheless, to run the software, if necessary, move the software to a computer-readable location suitable for processing and, for purposes of illustration, that location is referred to herein as memory. It should be understood that it is called. Even when software is moved to memory for execution, processors typically use hardware registers to store values associated with the software and a local cache that ideally speeds execution. To do. As used herein, when a software program is referred to as “implemented on a computer-readable medium”, the software program may be any known location (from a non-volatile storage device to a hardware register) or convenient. It is assumed that it will be stored in a different place. A processor is considered “configured to execute a program” if at least one value associated with the program is stored in a register readable by the processor.

  The bus also connects the processor to network interface equipment. The interface can include one or more modems or network interfaces. It will be appreciated that a modem or network interface can be considered part of a computer system. The interface may include an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (eg, “direct PC”), or other interface for connecting the computer system to other computer systems. The interface can include one or more input devices and / or output devices. An input / output device can include, by way of example and not limitation, other input and / or output devices including a keyboard, mouse or other pointing device, disk drive, printer, scanner, and display device. The display device may include, by way of example and not limitation, a liquid crystal display (LCD), an OLED, or other applicable known or convenient display device. For simplicity, it is assumed that a controller for any device not shown is present in the interface.

  In operation, the computer system 1300 can be controlled by operating system software including a file management system such as a disk operating system. An example of operating system software, including associated file management system software, is the family of operating systems known as Microsoft® Windows® and their associated file management system in Redmond, Washington. Another example of operating system software, including associated file management system software, is the Linux® operating system and associated file management system. File management systems are typically stored in non-volatile memory and / or drive units and allow the processor to perform various operations necessary for the operating system to input and output data to and from the non-volatile memory and / or drive. Store data in memory, such as storing files in the unit.

  Some portions of the detailed description can be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is generally considered herein a self-consistent sequence of actions that lead to a desired result or output. An operation is an operation that requires physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to regard these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

  However, it should be noted that these terms and similar terms are all related to the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise stated, as will be apparent from the following description, discussions that use terms such as `` process, '' `` calculate, '' `` calculate, '' `` determine '' or `` display '' throughout the specification Manipulating data represented as physical (electronic) quantities in computer system registers and memories, and similarly represented as physical quantities in computer system memories or registers or such information storage devices, transmission devices or display devices Refers to the operation and processing of a computer system or similar electronic computing device that converts to other data.

  The algorithms and display devices presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with the program according to the teachings herein, or it may prove advantageous to construct a more specialized device to perform the methods of some embodiments. There is also a possibility to do. The required structure for a variety of these systems will appear from the description herein. In addition, these techniques are not described with reference to any particular programming language, and thus various embodiments can be implemented using various programming languages.

  In alternative embodiments, the machine may operate as a stand-alone device or may be connected (eg, networked) to other machines. In a network deployment, the machine may operate with the capacity of a server or client machine in a client-server network environment, and may operate as a peer machine in a peer-to-peer (or distributed) network environment.

  The machine is a server computer, client computer, personal computer (PC), tablet PC, laptop computer, set top box (STB), personal digital assistant (PDA), mobile phone, smartphone, processor, telephone, web appliance, network router , A switch or bridge, or any machine capable of executing a sequence of instructions (sequentially or otherwise) that specify the action that the machine should take.

  Although a machine-readable medium or machine-readable storage medium is illustrated in an exemplary embodiment as being a single medium, the terms “machine-readable medium” and “machine-readable storage medium” may include one or more It should be construed to include a single medium or multiple media (eg, centralized or distributed databases, and / or associated caches and servers) that store a sequence of instructions. The terms “machine-readable medium” and “machine-readable storage medium” are capable of storing, encoding or carrying a sequence of instructions for execution by a machine, and currently disclosed techniques and techniques. It should be construed to include any medium that causes a machine to perform any one or more methods of innovation.

  Further, although the embodiments have been described in the context of a fully functional computer and computer system, those skilled in the art can distribute various embodiments as various forms of program products, and the present disclosure It will be understood that the invention applies equally regardless of the particular type of machine or computer readable medium used to make the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, among other things, volatile and non-volatile memory devices, floppy disks and other removable disks, hard disk drives, optical disks (eg read-only) Including, but not limited to, recordable media such as compact discs (CD-ROM), digital versatile discs (DVD), and transmission media such as digital and analog communication links.
Conclusion

  Throughout the specification and claims, words such as “comprise”, “comprising” and the like have exclusive or exhaustive meanings, unless the context clearly indicates otherwise. Should be construed in a comprehensive sense, i.e. in the sense of "including but not limited to". As used herein, the terms “connected”, “coupled” or any variation thereof mean any direct or indirect connection or coupling between two or more elements. However, the coupling of connections between elements may be physical, logical, or a combination thereof. Furthermore, terms used herein, “above”, “below” and like meanings, as used herein, refer to the entire application and refer to any particular part of the application. It doesn't mean that. As long as the context allows, words of the form for practicing the invention described above using single or multiple numbers may each include multiple or single numbers. For a list of two or more items, the word “or” means all interpretations of that word, such as any of the items in the list, all of the items in the list, and any combination of the items in the list. To cover.

  The above detailed description of embodiments of the present disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While particular embodiments and examples of the present disclosure have been described above for purposes of illustration, various equivalent modifications may be made within the scope of the disclosure, as will be appreciated by those skilled in the art. For example, while processes or blocks are presented in a predetermined order, alternative embodiments may execute routines with steps, systems with blocks may be used in a different order, and alternatives or subcombinations Some processes or blocks may be deleted, moved, added, classified, combined, and / or modified to provide Each of these processes or blocks may be implemented in a variety of different ways. Also, occasionally, processes or blocks are shown as being executed in series, but these processes or blocks may instead be executed in parallel or at different times. Moreover, any specific numbers described herein are merely examples, and alternative embodiments may use different values or ranges.

  The teachings of the disclosure provided herein are not necessarily the systems described above, and can be applied to other systems. The elements and acts of the various embodiments described above can be combined to provide further embodiments.

  Any of the patents and applications mentioned above, as well as other references, including those set forth in the attached filings, are hereby incorporated by reference. Aspects of the present disclosure can be modified as needed to provide further embodiments of the present disclosure using the systems, functions and concepts of the various references described above.

  These and other changes can be made to the disclosure in light of the above-described aspects of the invention. Although the foregoing description describes specific embodiments of the present disclosure and describes the best mode contemplated, the present teachings may be implemented in many ways, no matter how detailed the foregoing is set forth. be able to. The details of the system may vary considerably in its implementation details, but are still encompassed by the subject matter disclosed herein. As stated above, certain terms used in describing a particular feature or aspect of this disclosure are intended to be limited to any particular characteristic, feature or aspect of the disclosure with which the term is associated. It is not implied that it will be redefined herein. In general, the terms used in the following claims are intended to disclose the disclosure herein, unless the foregoing Detailed Description section explicitly defines such terms. It should not be construed as limited to any particular embodiment. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments but also all equivalent ways of implementing or implementing the disclosure under the claims.

  Although specific aspects of the disclosure are presented below in specific claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the present disclosure is described as a means plus function claim under 35 USC 112, sixth paragraph, other aspects are equally well defined as means plus function claims. Or in other forms as embodied on a computer readable medium. (All claims intended to be handled under 35 USC 112, sixth paragraph begin with the word “means”). Accordingly, Applicant reserves the right to make additional claims after filing to pursue such additional claim forms for other aspects of the disclosure.

Claims (20)

A system for determining power consumption of a mobile device,
Including a cloud processing system that communicates with the wireless charger,
In the cloud processing system,
The wireless charger is configured to supply power to at least one portable device;
The at least one portable device is powered by at least one battery;
The wireless charger receives information from the at least one portable device;
The wireless charger transmits the information to the cloud processing system;
The cloud processing system determines power consumption of the at least one battery based on the information.   The cloud processing system determines the power consumption based on a discharge / charge curve associated with the at least one battery, and the discharge / charge curve is identified based at least in part on the received information. Item 4. The system according to Item 1.   The system of claim 2, wherein the cloud processing system determines the power consumption based on a discharge / charge curve associated with the at least one battery.   The said at least one wireless device automatically transmits the information to the wireless charger periodically while the wireless charger supplies power to the at least one portable device. system.   The system of claim 1, wherein the at least one portable device transmits the information to the wireless charger in response to a trigger event.   The system of claim 5, wherein the trigger event is based at least in part on a request for information from the wireless charger.   The system of claim 5, wherein the trigger event is based at least in part on a battery level of the at least one portable device that is below a threshold.   The system of claim 5, wherein the trigger event is based at least in part on a power consumption rate of the at least one portable device that exceeds a threshold.   The information includes: device identification, device manufacturer, device type, device operating system, application currently running on the at least one portable device, battery status of the at least one battery, battery type, battery The system of claim 1, comprising: one or more of: type, device location, power received from previous request, internal or external coulomb of at least one battery from previous request, and temperature. A method for determining power consumption of a mobile device, comprising:
Receiving information related to at least one portable device that is wirelessly rechargeable;
Identifying a discharge / charge curve associated with at least one battery in the at least one portable device;
Calculating power consumption of the at least one portable device based at least in part on the received information and the identified discharge / charge curve.   The method of claim 10, wherein the discharge / charge curve is identified based at least in part on the received information.   The method of claim 10, further comprising requesting the information from an operating system running on the at least one mobile device.   The method of claim 12, wherein requesting the information includes sending a ZigBee message to the at least one mobile device.   The method of claim 10, wherein information is automatically received periodically from the at least one mobile device.   The information includes: device identification, device manufacturer, device type, device operating system, application currently running on the at least one portable device, battery status of the at least one battery, battery type, battery The method of claim 10, comprising: one or more of: type, device location, power received from previous request, internal or external coulomb of at least one battery from previous request, and temperature. A computer-readable storage medium having instructions stored thereon, wherein when executed by one or more processors of the portable device, the instructions cause the portable device to
Accessing one or more application program interfaces (APIs) of the mobile device;
Collecting information related to the use of the mobile device via the one or more APIs;
A computer-readable storage medium that provides the information related to use of the portable device to a wireless power supply system in response to a trigger event.   The computer-readable storage medium of claim 16, wherein the trigger event is based at least in part on a request for information from the wireless charger.   The computer-readable storage medium of claim 16, wherein the trigger event is based at least in part on a battery level of the portable device that is below a threshold.   The computer-readable storage medium of claim 16, wherein the trigger event is based at least in part on a power consumption rate of the portable device that exceeds a threshold.   The information includes device identification, device manufacturer, device type, device operating system, application currently running on the portable device, battery status of the at least one battery, battery type, battery type, The computer readable storage medium of claim 16, comprising one or more of: device location, power received from a previous request, internal or external coulomb of at least one battery from a previous request, and temperature.

Images