System and method for smart registration of wireless power receivers in a wireless power network

[0001] The present disclosure is related to U.S. non-provisional patent application Ser. No. 13/891,430, filed May 10, 2013, entitled “Methodology for Pocket-forming”; and application Ser. No. 13/925,469, filed Jun. 24, 2013, entitled “Methodology for Multiple Pocket-Forming”; application Ser. No. 13/946,082, filed Jul. 19, 2013, entitled “Method for 3 Dimensional Pocket-forming”; application Ser. No. 13/891,399, filed May 10, 2013, entitled “Receivers for Wireless Power Transmission”; application Ser. No. 13/891,445, filed May 10, 2013, entitled “Transmitters for Wireless Power Transmission” invented by Michael Leabman, each of which are incorporated by reference in their entirety herein.

[0002] Field of the Disclosure

[0003] The present disclosure relates in general to wireless power transmission, and more specifically to systems and methods for smart registration of wireless power receivers within a wireless power network.

[0004] Background Information

[0005] Electronic devices such as laptop computers, smartphones, portable gaming devices, tablets, and so forth may need power for performing their intended functions. This may require having to charge electronic equipment at least once a day, or in high-demand electronic devices more than once a day. Such an activity may be tedious and may represent a burden to users. For example, a user may be required to carry chargers in case his electronic equipment is lacking power. In addition, users may have to find available power sources to connect to. Lastly, users must plugin to an electric outlet or other power supply to be able to charge his or her electronic device. However, such an activity may render electronic devices inoperable during charging. Current solutions to this problem may include inductive pads which may employ magnetic induction or resonating coils. Nevertheless, such a solution may still require that electronic devices may have to be placed in a specific place for powering. Thus, electronic devices during charging may not be portable.

[0006] Other solutions to this problem may include using controlled Radio RF waves which may converge in 3-D space for charging or powering electronic devices. This option may provide wireless power using one or more wireless power transmitters and one or more wireless power receivers, while eliminating the use of wires or pads for charging devices.

[0007] The ability to charge electronic devices wirelessly has great benefits. However, it may be necessary to manage the access of users to the network to prevent the abuse of the system resources. For example if many devices are connected to a wireless power network, different failures can affect the network, therefore interrupting the power transfer. Failures may include a loss of power, a failure in the hardware or software of a wireless power transmitter manager, overload of the wireless power transmitter manager, and malfunctioning in a wireless power transmitter manager, among others.

[0008] For the foregoing reasons, there is a need for a system and method that may allow the smart registration of wireless power receivers within a wireless power network so as to prevent the abuse of the system resources which may eventually result in a breakdown of the system.

[0009] The present disclosure provides a system and method for smart registration of wireless power receivers within a wireless power network.

[0010] In one embodiment, a wireless power network may include one or more wireless power transmitter managers and/or one or more wireless power receivers for powering various customer devices. Each wireless power device may include a universally unique identifier (UUID).

[0011] In a different aspect of this embodiment, a wireless power receiver may be paired with a customer device. In another embodiment, the wireless power receiver may be built-in to the customer device.

[0012] In another aspect of this embodiment, each wireless power transmitter manager in the wireless power network may receive customer device's signal strength from advertisement emitted by the wireless power receiver and customer device's graphical user interface (GUI). Graphical user interface (GUI) may be part of wireless power system software downloaded and installed from public application store. Also wireless power transmitter manager may send power in a range up to 30 feet.

[0013] According to some aspects of this embodiment, wireless power transmitter manager may include a device database, where device database may store information about all network devices such as unique device identification (ID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.

[0014] In a different aspect of this embodiment, each wireless power device bought by a customer may be registered at the time of purchase, or registered later by the customer using public accessible web page or smart device application that communicates to an energy domain service.

[0015] Energy domain service may be one or more cloud-based servers and each cloud-based servers may include a database that may store a registry for each wireless power device purchased by a customer. In a different aspect of this embodiment, energy domain service may be hosted in an internet accessible cloud.

[0016] In another embodiment, a method for smart registration of wireless power receivers within a wireless power network may include the steps of a wireless power transmitter manager detecting a customer device; establishing a connection with a wireless power receiver to read its UUID; sending wireless power transmitter manager's UUID and wireless power receiver's UUID to an energy domain service for authentication and authorization to transmit power to customer device; inspecting wireless power transmitter manager registry; verifying wireless power receiver registry; authorizing the wireless power transmitter manager to send power to wireless power receiver; and reporting energy consumption statistics to energy domain service for subsequent billing of customer depending on billing policy of wireless power transmitter manager specified within registry.

[0017] According to some aspect of this embodiment, a customer may be able to select through a GUI device, which wireless power receivers may receive charge from customer's wireless power transmitter manager.

[0018] In another embodiment, the customer may be provided with a pre-authorized wireless power receiver at commercial point of sale by proprietor or clerk. The wireless power receiver may be attached to customer's device, subsequently proprietor may register customer's billing information, such as credit card, Pay Pal account, or a different payment method, immediately the local wireless power system may start sending power to the customer device that is attached to pre-authorized wireless power receiver. The local wireless power system may report energy consumption statistics to energy domain service for subsequent billing of customer.

[0019] The system and method for smart registration of wireless power receivers within a wireless power network described here may allow a network manager to manage the access of users to the network, preventing the abuse of system resources which may eventually result in a breakdown of the system. Numerous other aspects, features and benefits of the present disclosure may be made apparent from the following detailed description taken together with the drawing figures.

[0024] The present disclosure is here described in detail with reference to embodiments illustrated in the drawings, which form a part here. Other embodiments may be used and/or other changes may be made without departing from the spirit or scope of the present disclosure. The illustrative embodiments described in the detailed description are not meant to be limiting of the subject matter presented here.

[0025] As used here, the following terms may have the following definitions:

[0026] “Transmitter” refers to a device including a chip which may generate two or more RF signals, at least one RF signal being phase shifted and gain adjusted with respect to other RF signals, all of which pass through one or more RF antenna such that focused RF signals are directed to a target.

[0027] “Receiver” refers to a device which may include at least one antenna, at least one rectifying circuit, and at least one power converter for powering or charging an electronic device using RF waves.

[0028] “Pocket-forming” refers to generating two or more RF waves which converge in 3-D space, forming controlled constructive and destructive interference patterns.

[0029] “Pockets of energy” refers to areas or regions of space where energy or power may accumulate in the form of constructive interference patterns of RF waves.

[0030] “wireless power system” refers to one or more wireless power transmitter managers and one or more wireless power receivers that provide wireless power to electronic devices, and also one or more cloud-based back-end servers that perform system management functions.

[0031] “wireless power network” refers to one or more wireless power transmitter managers, wireless power receivers, servers, and clouds within a local network or the internet to provide wireless power transfer to electronic devices.

[0032] “Wireless power device” refers to a device used in a wireless power network to send, receive, and store information, among others; examples of wireless power devices may include wireless power transmitter manager, wireless power receiver, end user hand-held devices and servers, among others.

[0033] “GUI device” refers to a software installed in a client computing device such as a laptop computer, smartphone, or tablet, among others to manage the wireless power network.

[0034] “Pairing” refers to the relationship between a wireless power receiver and the graphical user interface (GUI) to which it is physically adjacent.

[0035] “Assigned” refers to the relationship between a wireless power receiver and its nearest wireless power transmitter manager.

[0036] In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, which may not be to scale or to proportion, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings and claims, are not meant to be limiting. Other embodiments may be used and/or and other changes may be made without departing from the spirit or scope of the present disclosure.

[0037] FIG. 1 shows a wireless power system 100 using a wireless power transmitter manager 102, according to an embodiment. Wireless power transmitter manager 102 may include a processor with computer-readable medium, such as a random access memory (RAM) (not shown) coupled to the processor. Examples of processor may include a microprocessor, an application specific integrated circuit (ASIC), and field programmable object array (FPOA), among others.

[0038] Wireless power transmitter manager 102 may transmit controlled Radio RF waves which may converge in 3-D space to a wireless power receiver 104 for charging or powering a customer device 106. These RF waves may be controlled through phase and/or relative amplitude adjustments to form constructive and destructive interference patterns (pocket-forming). Pockets of energy may form at constructive interference patterns and can be 3-dimensional in shape whereas null-spaces may be generated at destructive interference patterns.

[0039] Wireless power receiver 104 may be paired with customer device 106 or may be built into customer device 106. Examples of customer devices 106 may include laptop computer, mobile device, smartphones, tablets, music players, and toys, among other. Customer device 106 may include a graphical user interface 112 (GUI) as part of wireless power system 100 software downloaded and installed from public application store.

[0040] Wireless power transmitter manager 102 may receive customer device's signal strength from advertisement emitted by wireless power receiver 104 for the purpose of detecting if wireless power receiver 104 is nearer to wireless power transmitter manager 102 than to any other wireless power transmitter manager 102 in system 100. Graphical user interface 112 (GUI) may receive customer device's signal strength from advertisement emitted by wireless power receiver 104 for the purpose of detecting if wireless power receiver 104 is paired with graphical user interface 112 (GUI).

[0041] According to some aspects of this embodiment, wireless power transmitter manager 102 may include a device database 116, where device database 116 may store information about all network devices, such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer devices past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.

[0042] Wireless power transmitter manager 102 may send power in a range up to 30 feet.

[0043] Wireless power transmitter manager 102 may use, but is not limited to, Bluetooth low energy (BTLE) to establish a communication link 108 with wireless power receiver 104 and a control link 110 with customer device's graphical user interface (GUI). Wireless power transmitter manager 102 may use control link 110 to receive commands from and receive pairing information from customer device's graphical user interface (GUI).

[0044] Wireless power transmitter manager 102 may include antenna manager software 114 to track customer device 106. Antenna manager software 114 may use real time telemetry to read the state of the power received in customer device 106.

[0045] Wireless power transmitter manager 102 may create a wireless energy area model which includes information about all the movements in the system. This information may be stored in device database 116.

[0046] In other situations, there can be multiple wireless power transmitter managers 102 and/or multiple wireless power receivers 104 for powering multiple and various customer devices 106.

[0047] FIG. 2 illustrates a system architecture for smart registration 200 of wireless power receivers within a wireless power network, according to another embodiment.

[0048] In a wireless power network, one or more wireless power transmitter managers and/or one or more wireless power receivers may be used for powering various customer devices.

[0049] Each wireless power device in the wireless power network may include a universally unique identifier (UUID). Examples of wireless power devices may include wireless power transmitter manager, wireless power receiver, end user hand-held or mobile devices, and servers, among others.

[0050] A wireless power transmitter manager 202 may include a processor with computer-readable medium, such as a random access memory (RAM) (not shown) coupled to the processor. Examples of processor may include a microprocessor, an application specific integrated circuit (ASIC), and a field programmable object array (FPOA), among others.

[0051] According to some aspects of this embodiment, each wireless power device bought by a customer may be registered at the time of purchase, or registered later by the customer using public accessible web page or smart device application that communicates to energy domain service 214. The registry may be stored in an energy domain service 214.

[0052] Energy domain service 214 may be one or more cloud-based servers and each cloud-based servers may include a database that may store a registry for each wireless power device purchased by a customer. Cloud-based servers may be implemented through known in the art database management systems (DBMS) such as, for example, MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice Base, FileMaker Pro and/or any other type of database that may organize collections of data. The registry may include customer's name, customer's credit card, Pay Pal account, or any other method of payment, address, and wireless power device UUID, among others. The registry may indicate whether wireless power transmitter manager 202 is for business, commercial, municipal, government, military, or home use. The registry may also include different access policies for each wireless power transmitter manager 202, depending on it use, for example if wireless power transmitter manager 202 will be for businesses use, the customer may need to define whether the power transfer will be charged or not.

[0053] In a different aspect of this embodiment, a wireless power receiver 204 may include a nonvolatile memory for storing wireless power transmitter manager 202 universally unique identifier (UUID). Examples of nonvolatile memory may include read-only memory, flash memory, ferroelectric RAM (F-RAM) hard disks, floppy disks, and optical discs, among others. Wireless power receiver 204 may be paired with customer device 206 or may be built into customer device 206. Examples of customer devices 206 may include laptop computer, mobile device, smartphone, tablet, music player, and toys, among other. Customer device 206 may include a graphical user interface 208 (GUI) as part of wireless power system software downloaded and installed from public application store.

[0054] According to some aspects of this embodiment, wireless power transmitter manager 202 may include a device database 210, where device database 210 may store information about all network devices such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.

[0055] Wireless power transmitter manager 202 may send power in a range up to 30 feet.

[0056] According to some aspects of this embodiment, wireless power transmitter manager 202 may detect customer device's signal strength from advertisement emitted graphical user interface 208 (GUI) for the purpose of detecting if wireless power receiver 204 is paired with graphical user interface 208 (GUI). Wireless power transmitter manager 202 may also detect if wireless power receiver 204 is nearer to wireless power transmitter manager 202 than to any other wireless power transmitter manager 202 in the wireless power network through an analysis of each device database records in the wireless power system 100. Each record may include a list of each wireless power receiver 204 and its signal strength relative to and detected by wireless power transmitter manager 202. Then wireless power receiver 204 may be assigned to wireless power transmitter manager 202, which may have exclusive control and authority to change the wireless power receiver's record in distributed system device database 210 until wireless power receiver 204 moves to a new location closer to another wireless power transmitter manager 202. If wireless power receiver 204 change to new location closer to another wireless power transmitter manager 202, then wireless power transmitter manager 202 (with control over wireless power receiver 204) may update wireless power receiver's record with its UUID.

[0057] If wireless power receiver 204 tries to charge using wireless power transmitter manager 202, then wireless power transmitter manager 202 may verify with energy domain service 214 if it is authorized to send power to wireless power receiver 204. Therefore wireless power transmitter manager 202 may establish a communication connection with wireless power receiver 204 to request its universally unique identifier (UUID). Wireless power receiver 204 may send UUID to wireless power transmitter manager 202. Wireless power transmitter manager 202 may establish communication connection with energy domain service 214 and then send its UUID and wireless power receiver 204 UUID to energy domain service 214 through an internet cloud 212, where internet cloud 212 may be any suitable connections between computers such as, for example, intranets, local area networks (LAN), virtual private networks (VPN), wide area networks (WAN) and the internet among others. Once energy domain service 214 receives wireless power transmitter UUID and wireless power receiver 204 UUID, it may inspect the registry for wireless power transmitter manager 202 using UUID. Registry may include access policy for wireless power transmitter manager 202. Energy domain service 214 may determine through the access policy whether wireless power transmitter manager 202 needs to pay to receive power. If wireless power transmitter manager 202 access policy states that wireless power receiver 204 with UUID needs to pay to receive power, energy domain service 214 may verify whether a credit card, Pay Pal, or other payment method, may be denoted within wireless power receiver 204 registry. If a payment method is associated with wireless power receiver 204, energy domain service 214 may send a message to wireless power transmitter manager 202 authorizing the power transfer to wireless power receiver 204. Wireless power transmitter manager 202 may report energy consumption statistics to energy domain service 214 for subsequent billing of wireless power receiver's owner. Energy consumption statistics may be stored in device database 210 and also may be sent to energy domain service 214 and saved in wireless power receiver's registry.

[0058] If no payment method is associated with wireless power receiver 204, energy domain service 214 may send a message to wireless power transmitter manager 202 denying the power transfer to wireless power receiver 204.

[0059] In the case wireless power transmitter manager 202 access policy states that no charge will be applied to certain wireless power receivers 204, then energy domain service 214 may confirm if wireless power receiver 204 is allowed to receive power from wireless power transmitter manager 202. If wireless power receiver 204 is allowed to receive power from wireless power transmitter manager 202, then, energy domain service 214 may send a message to wireless power transmitter manager 202 authorizing the power transfer to wireless power receiver 204. Otherwise energy domain service 214 may send a message to wireless power transmitter manager 202 denying the power transfer to wireless power receiver 204.

[0060] According to some aspect of this embodiment, a customer, may be able to select through a GUI device, which wireless power receivers 204 may receive charge from wireless power transmitter manager 202. In the GUI device, customer may be able to visualize each wireless power receiver 204 near wireless power transmitter manager 202, then, customer may select which wireless power receivers 204 are allowed to receive charge from wireless power transmitter manager 202. This information may be stored in device database 210 and also may be sent to energy domain service 214.

[0061] In a different aspect of this embodiment, a proprietor or clerk of a commercial or retail business establishment that owns a wireless power system may be able to select through the GUI device a wireless power receiver 204 to receive power from one or more wireless power transmitter managers 202 within power range of wireless power receiver 204. The customer may be provided with a pre-authorized wireless power receiver 204 at business establishment by proprietor or clerk. The wireless power receiver 204 may be attached to customer's device. The proprietor or clerks may specify to GUI device the customer's method of payment (credit card, Pay Pal, cash, among others.). Immediately the wireless power transmitter manager 202 that belong to business establishment may start sending power to the customer device that is attached to pre-authorized wireless power receiver 204. Customer may be billed on behalf of business establishment for power provided. Also in the GUI device, proprietor or clerk may be able to visualize power received by wireless power receiver 204 and the amount to bill for power received. This information may be stored in distributed system device database 210 and also may be sent to energy domain service 214.

[0062] FIG. 3 is a flowchart of a method for smart registration 300 of wireless power receivers within a wireless power network, according to a further embodiment.

[0063] In a wireless power network, one or more wireless power transmitter managers and/or one or more wireless power receivers may be used for powering various customer devices. Each wireless power device in the wireless power network may include a universally unique identifier (UUID). Examples of wireless power devices may include wireless power transmitter manager, wireless power receiver, end user hand-held or mobile devices and servers, among others.

[0064] The method may start at step 302 when a wireless power transmitter manager detects a customer device. Customer device may be paired with wireless power receiver or wireless power receiver may be built in a customer device. Example of customer devices may include smartphones, mobile device, tablets, music players, toys and others at the same time. Customer device may include a graphical user interface (GUI) as part of wireless power system software downloaded and installed from public application store.

[0065] Wireless power transmitter manager may detect customer device's signal strength from advertisement emitted graphical user interface (GUI) for the purpose of detecting if wireless power receiver is paired with graphical user interface (GUI). Wireless power transmitter manager may also detect if wireless power receiver is nearer to wireless power transmitter manager than to any other wireless power transmitter manager in the wireless power network through an analysis of each device database records in the wireless power system. Each record may include a list of each wireless power receiver and its signal strength relative to and detected by wireless power transmitter manager. Then wireless power receiver may be assigned to wireless power transmitter manager, which may have exclusive control and authority to change the wireless power receiver's record in distributed system device database until wireless power receiver moves to a new location closer to another wireless power transmitter manager.

[0066] According to some aspects of this embodiment, Device database may store information about all network devices such as universally unique identifier (UUID), serial number, signal strength, identification of paired partner device, customer device's power schedules and manual overrides; customer device's past and present operational status, battery level and charge status, hardware value measurements, faults, errors, and significant events; names, customer's authentication or authorization names, and configuration details running the system, among others.

[0067] Wireless power transmitter manager may establish a communication connection with wireless power receiver indicating is within range to receive charge. Wireless power transmitter manager may send power in a range up to 30 feet.

[0068] If wireless power receiver tries to obtain charge from wireless power transmitter manager, wireless power transmitter manager may verify with energy domain service if it is authorized to send power to wireless power receiver. Therefore wireless power transmitter may establish a communication connection with wireless power receiver to request universally unique identifier (UUID). Wireless power receiver may send UUID to wireless power transmitter manager. Wireless power transmitter manager may read wireless power receiver UUID, at step 304.

[0069] Energy domain service may be one or more cloud-based servers and each cloud-based servers may include a database that may store a registry for each wireless power device purchased by a customer. Cloud-based servers may be implemented through known in the art database management systems (DBMS) such as, for example, MySQL, PostgreSQL, SQLite, Microsoft SQL Server, Microsoft Access, Oracle, SAP, dBASE, FoxPro, IBM DB2, LibreOffice Base, FileMaker Pro and/or any other type of database that may organize collections of data. The registry may include customer's name, customer's credit card, address, and wireless power device UUID, among others. The registry may indicate whether wireless power transmitter manager is for business, commercial, municipal, government, military, or home use. The registry may also include different access policies for each wireless power transmitter manager, depending on it use, for example if wireless power transmitter manager will be for businesses use, the customer may need to define whether the power transfer will be charged or not.

[0070] According to some aspects of this embodiment, each wireless power device bought by a customer may be registered at the time of purchase, or registered later by the customer using public accessible web page or smart device application that communicates to energy domain service.

[0071] Wireless power transmitter manager may send its UUID and also wireless power receiver UUID to an energy domain service through the internet cloud, at step 306. Internet cloud may be any suitable connections between computers such as, for example, intranets, local area networks (LAN), virtual private networks (VPN), wide area networks (WAN) and the internet among others.

[0072] Energy domain service may inspect the registry for wireless power transmitter manager using UUID, at step 308. Registry may include access policy for wireless power transmitter manager.

[0073] Energy domain service may determine through the access policy whether wireless power transmitter manager needs to pay to receive power, at step 310.

[0074] If wireless power transmitter manager access policy states that wireless power receiver with UUID needs to pay to receive power, energy domain service may verify whether a credit card, Pay Pal, or other payment method, may be denoted within wireless power receiver registry, at step 312.

[0075] If a payment method is associated with wireless power receiver registry, energy domain service may send a message to wireless power transmitter manager authorizing the power transfer to wireless power receiver, at step 314.

[0076] Wireless power transmitter manager may report energy consumption statistics to energy domain service for subsequent billing of wireless power receiver's owner, at step 316. Energy consumption statistics may be stored in device database and also may be sent to energy domain service and saved in wireless power receiver's registry.

[0077] In the case no payment method is associated with wireless power receiver, energy domain service may send a message to wireless power transmitter manager denying the power transfer to wireless power receiver, at step 318.

[0078] Else, if wireless power transmitter manager access policy states that no charge will be applied to a certain wireless power receiver which may be trying to obtain power from wireless power transmitter manager, energy domain service may confirm whether wireless power receiver is allowed to receive power from wireless power transmitter manager, at step 320.

[0079] If wireless power receiver is allowed to receive power from wireless power transmitter manager. Energy domain service may send a message to wireless power transmitter manager authorizing the power transfer to wireless power receiver, at step 314.

[0080] Wireless power transmitter manager may report energy consumption statistics to energy domain service, at step 316. Energy consumption statistics may be stored in device database and also may be sent to energy domain service and saved in wireless power receiver's registry.

[0081] Otherwise if wireless power receiver is not allowed to receive power from wireless power transmitter manager, energy domain service may send a message to wireless power transmitter manager denying the power transfer to wireless power receiver, at step 322

[0082] According to some aspect of this embodiment, a customer may be able to select through a GUI device which wireless power receivers may receive charge from wireless power transmitter manager. In the GUI device, customer may be able to visualize each wireless power receiver near to wireless power transmitter manager, then customer may select which wireless power receivers are allowed to receive charge from wireless power transmitter manager. This information may be stored in device database and also may be sent to energy domain service.

[0083] Example #1 is a wireless power network with components similar to those described in FIG. 2. A customer may have a wireless power transmitter manager in his/her house. The customer invites three friends to watch a football game. Two of the three friends have a wireless power receiver cover paired with their cellphones. When both wireless power receivers are within the range of the wireless power transmitter manager, they may receive a message from wireless power transmitter manager indicating they are within range to receive power. One of the wireless power receivers may try to obtain power from wireless power transmitter manager, but first the wireless power transmitter manager may verify whether wireless power receiver is authorized to receive power. Therefore wireless power transmitter manager may send its own UUID and wireless power receiver UUID to an energy domain service. Energy domain service may verify access policy for wireless power transmitter manager to determine if a billing charge has to be applied for using wireless power transmitter manager. The access policy for wireless power transmitter manager may indicate that no charge will be applied for using wireless power transmitter manager and that any wireless power receiver is able to receive charge from it. Energy domain service may verify wireless power receiver registry and then energy domain service may authorize wireless power transmitter manager to send power to wireless power receiver.

[0084] Example #2 is a wireless power network with components similar to those described in FIG. 2. A restaurant may have a wireless power transmitter manager. A customer within the restaurant has a cellphone with a wireless power receiver cover. The customer may want to charge his/her cellphone while having dinner. The customer tries to charge his/her cellphone using wireless power transmitter manager, the wireless power transmitter manager may need to verify if wireless power receiver is authorized to receive power. Therefore wireless power transmitter manager may send its own UUID and wireless power receiver UUID to an energy domain service. Energy domain service may verify access policy for wireless power transmitter manager to determine if a billing charge has to be applied for using wireless power transmitter manager. The access policy for wireless power transmitter manager may indicate that a charge will be applied for using wireless power transmitter manager. Then, energy domain service may verify wireless power register to determine whether a method of payment such as credit card or other method is associated with wireless power receiver. If a payment method is on the registry file, energy domain service may authorize wireless power transmitter manager to send power to wireless power receiver. Wireless power transmitter manager may track the amount of power sent to wireless power receiver. This information may be stored in device database and also may be sent to energy domain service to generate a bill, on behalf of the restaurant.

[0085] While various aspects and embodiments have been disclosed, other aspects and embodiments are contemplated. The various aspects and embodiments disclosed are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

[0086] The foregoing method descriptions and the interface configuration are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by one of skill in the art the steps in the foregoing embodiments may be performed in any order. Words such as “then,” “next,” etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

[0087] The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed here may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

[0088] Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0089] The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description here.

[0090] When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed here may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used here, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

[0091] The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined here may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown here but is to be accorded the widest scope consistent with the following claims and the principles and novel features disclosed here.