Patent Publication Number: US-9899873-B2

Title: System and method for generating a power receiver identifier in a wireless power network

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     The present disclosure is related to U.S. non-provisional patent application DWV-3DPF-010 entitled “Methodology for Pocket-forming”; and DWV-3DPF-028 entitled “Methodology for Multiple Pocket-Forming”; DWV-3DPF-015 entitled “Method for 3 Dimensional Pocket-forming”; DWV-3DPF-027 entitled “Receivers for Wireless Power Transmission”; DWV-3DPF-029 entitled “Transmitters for Wireless Power Transmission” invented by Michael Leabman, each of which are incorporated by reference in their entirety herein. 
     BACKGROUND 
     Field of the Disclosure 
     The present disclosure relates generally to wireless power networks, and more specifically to a system and method for generating a wireless power receiver identifier in a wireless power network. 
     Background Information 
     Electronic devices such as laptop computers, smartphones, portable gaming devices, tablets and so forth may require 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 have to find available power sources to connect to. Lastly, users must plugin to a wall power socket or other power supply to be able to charge his or her electronic device. 
     An approach to mitigate this issue may include using RF waves through suitable power transmission techniques such as pocket-forming. This approach may provide wireless power transmission while eliminating the use of wires or pads for charging devices. In addition, electronic equipment may require less components as typical wall chargers may not be required. In some cases, even batteries may be eliminated as a device may fully be powered wirelessly. 
     The approach may enable the creation of wireless power networks similar in structure to regular wireless local area networks (WLAN) where a wireless access point is used to provide internet or intranet access to different wireless devices. A wireless power transmitter may provide wireless power charging to a plurality of wireless power receiver devices. As in a WLAN, a wireless power network may require a way to identify and associate wireless power receivers to have better control of such devices to when and which device to charge. 
     For the foregoing reasons, there is a need for a way to identify and control wireless power receiver devices within a wireless power network. 
     SUMMARY 
     Embodiments in the present disclosure may be directed to a system and method for generating a unique identifier for one or more wireless power devices (that is, one or more wireless power receivers, wireless power transmitters, or GUI management devices, or system management servers, and others) within a wireless power network. The system and method may include suitable automated software embedded on a chip that may run when a wireless power device boots up for the first time. The unique ID may allow easy associations of wireless power devices with different user defined names. 
     In one aspect of the present disclosure, a system architecture that may enable the registration and communication controls between wireless power transmitter and one or more wireless power receivers is disclosed. Wireless power receivers may include covers or customer pocket-forming enabled devices. 
     In one embodiment, wireless power transmitter may include a microprocessor that integrates a power transmitter manager app (PWR TX MGR APP), and a third party application programming interface (third party API) for a Bluetooth Low Energy chip (BTLE CHIP HW). Wireless power transmitter may also include an antenna manager software (Antenna MGR Software) to control an RF antenna array that may be used to form controlled RF waves which may converge in 3-D space and create pockets of energy on wireless power receivers (covers or customer pocket-forming enabled devices). 
     In another embodiment, covers may include a power receiver app (PWR RX APP), a third party application programming interface (third party API) for a Bluetooth Low Energy chip (BTLE CHIP HW), and a radio frequency (RF) antenna array which may be used to receive and utilize the pockets of energy sent from wireless power transmitter. 
     In yet another embodiment, customer pocket-forming enabled devices may refer to a wireless device such as smartphones, tablets, or any of the like that may include an integrated wireless power receiver chip (not shown in  FIG. 1 ) for wireless power charging. Customer pocket-forming enabled devices may include a power receiver app (PWR RX APP), and a third party application programming interface (third party API) for a Bluetooth Low Energy chip (BTLE CHIP HW). Customer pocket-forming enabled devices may also include an RF antenna array which may used to receive and utilize pockets of energy sent from wireless power transmitter. GUI may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others. 
     In another aspect of the present disclosure, an exemplary method may be used to generate a unique identifier for wireless power devices within a wireless power network is disclosed. The method may employ suitable software embedded on a chip that may be triggered the first time a wireless power receiver is turned on. The method may first check if a NV RAM ID flag is set in the wireless power receiver, if the ID flag is set then the software reads the ID from the NV RAM (at a different address) and continues normal operation. If ID flag is not set, the software runs a suitable random number generator method to generate a random ID which may be 32-bits or greater. Once the ID is generated, the software writes the ID to NV RAM unique address. Finally, the software may write the unique 32-bits (or greater) ID flag to NV RAM unique address, read ID from NV RAM and continue normal operation. 
     In another embodiment, the method may also be used to not only generate unique IDs for wireless power receivers, but also to generate unique IDs for wireless power transmitters and GUIs. By generating unique IDs for each of the components in a wireless power network, the components may be more easily associated to users and have friendly names. For example, a user may have in his or her home more than one wireless power transmitter located at different places such as the living room, the bedrooms, and the kitchen among others. Then the power transmitter&#39;s unique ID may be associated with a custom label, stored in said transmitter&#39;s system database, for each of the wireless power transmitters at different locations. 
     In a further aspect of the present disclosure, a flowchart of a method for registering and associating a wireless power receiver to a wireless power network is provided. The method may include automated software embedded on a wireless power receiver chip that may be triggered when a wireless power receiver boots up. Therefore, the method may start when a wireless power receiver boots up when turned on by the user. Then, the wireless power receiver broadcasts ads, which may include an unique ID number, to any power transmitter manager and GUI that is within its range. Then, power transmitter manager and GUI, that are within range of the wireless power receiver broadcast, receive and decode the advertisement. Subsequently, power transmitter manager may store the unique ID number of said wireless power receiver in a database. This database may serve to store relevant information from wireless power receivers such as, identifiers, voltage ranges, location, signal strength and/or any relevant information from the wireless power receiver. Following the method, GUI may update and sync all relevant information in its copy of the system database, for better control of the wireless power devices. GUI may then ask the user to assign a name for the wireless power receiver that may have joined the wireless power network. Finally, the user assigns a name of its preference and the GUI syncs that name with the database. 
     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. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The present disclosure can be better understood by referring to the following figures. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the disclosure. In the figures, reference numerals designate corresponding parts throughout the different views. 
         FIG. 1  shows a system architecture in which one or more embodiments of the present disclosure may operate; 
         FIG. 2  shows a flowchart of a method that may be used to generate a unique identifier for a wireless power receiver device within a wireless power network; and 
         FIG. 3  shows a flowchart of a method for registering and associating a wireless power receiver to a wireless power network. 
     
    
    
     DETAILED DESCRIPTION 
     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. 
     Definitions 
     As used here, the following terms may have the following definitions: 
     “Real time communication” refers to communicating the status of data at the receiver at the continuing present time, where a proprietary algorithm may read the present state of important information at the receiver continually and rapidly with only 1/100th of a second of delay. 
     “Transmitter” may refer 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, substantially all of which pass through one or more RF antenna such that focused RF signals are directed to a target. 
     “Receiver” may refer to a device including at least one antenna element, at least one rectifying circuit and at least one power converter, which may utilize pockets of energy for powering, or charging an electronic device. 
     “Pocket-forming” may refer to generating two or more RF waves which converge in 3-D space, forming controlled constructive and destructive interference patterns. 
     “Pockets of energy” may refer to areas or regions of space where energy or power may accumulate in the form of constructive interference patterns of RF waves. 
     Description of the Drawings 
     Reference will now be made to the exemplary embodiments illustrated in the drawings, and specific language will be used here to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. Alterations and further modifications of the inventive features illustrated here, and additional applications of the principles of the inventions as illustrated here, which would occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the invention. 
       FIG. 1  shows a system architecture  100  for a wireless power network, according to an embodiment. System architecture  100  may enable the registration and communication controls between wireless power transmitter  102  and one or more wireless power receivers within a wireless power network. Wireless power receivers may include covers  104  and customer pocket-forming enabled devices  106 . 
     In one embodiment, wireless power transmitter  102  may include a microprocessor that integrates a power transmitter manager app  108  (PWR TX MGR APP), and a third party application programming interface  110  (Third Party API) for a Bluetooth Low Energy chip  112  (BTLE CHIP HW). Wireless power transmitter  102  may also include an antenna manager software  114  (Antenna MGR Software) to control an RF antenna array  116  that may be used to transmit controlled Radio Frequency (RF) waves which may converge in 3-D space. 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 that may be 3-Dimensional in shape whereas null-spaces may be generated at destructive interference patterns. Pockets of energy may be formed on wireless power receivers (covers  104  and customer pocket-forming enabled devices  106 ). In some embodiment, Bluetooth Low Energy chip  112  may be another type of wireless protocol such as WiFi or the like. 
     Power transmitter manager app  108  may include a database (not shown), which may store relevant information from wireless power receivers such as, identifiers, voltage ranges, location, signal strength and/or any relevant information from the wireless power receiver. 
     Power transmitter manager app  108  may call third party application programming interface  110  for running a plurality of functions such as start a connection, end a connection, and send data among others. Third party application programming interface  110  may command Bluetooth Low Energy chip  112  according to the functions called by power transmitter manager app  108 . 
     Third party application programming interface  110  at the same time may call power transmitter manager app  108  through a callback function which may be registered in the power transmitter manager app  108  at boot time. Third party application programming interface  110  may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or a message is received. 
     Covers  104  may include a power receiver app  118  (PWR RX APP), a third party application programming interface  120  (Third party API) for a Bluetooth Low Energy chip  122  (BTLE CHIP HW), and a RF antenna array  124  which may be used to receive and utilize the pockets of energy sent from wireless power transmitter  102 . 
     Power receiver app  118  may call third party application programming interface  120  for running a plurality of functions such as start a connection, end the connection, and send data among others. Third party application programming interface  120  may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received. 
     Covers  104  may be paired to a wireless device such as a smartphone, or tablet among others via a BTLE connection  126  by using a graphical user interface (GUI  128 ) that may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others. Covers  104  may also communicate with wireless power transmitter  102  via a BTLE connection  126  to send important data such as an identifier for the device as well as battery level information, antenna voltage, geographic location data, real-time received power feedback, or other information that may be of use for the wireless power transmitter  102 . 
     In other embodiments, GUI  128  may also be installed on a wireless device (smartphones or tablets) that may not have the cover  104 . GUI  128  may perform operations to communicate with power transmitter manager app  108  via BTLE connection  126  or any other wireless communication protocols such as WiFi, and LAN among others. 
     Customer pocket-forming enabled devices  106  may refer to a wireless device such as smartphones, tablets, or any of the like that may include an integrated wireless power receiver chip (not shown in  FIG. 1 ) for wireless power charging. Customer pocket-forming enabled devices  106  may include a power receiver app  130  (PWR RX APP), and a third party application programming interface  132  (Third Party API) for a Bluetooth Low Energy chip  134  (BTLE CHIP HW). Customer pocket-forming enabled devices  106  may also include an RF antenna array  136  which may used to receive and utilize pockets of energy sent from wireless power transmitter  102 . GUI  138  may be downloaded from any suitable application store and may run on any suitable operating system such as iOS and Android, among others. 
     Power receiver app  130  may call third party application programming interface  132  for running a plurality of functions such as start a connection, end the connection, and send data among others. Third party application programming interface  132  may have a timer callback that may go for ten times a second, and may send callbacks every time a connection begins, a connection ends, a connection is attempted, or message is received. 
     Customer pocket-forming enabled devices  106  may also communicate with wireless power transmitter  102  via a BTLE connection  126  to send important data such as an identifier for the device as well as battery level information, antenna voltage, geographic location data, real-time received power feedback, or other information that may be of use for the wireless power transmitter  102 . 
       FIG. 2  shows a flowchart of a method  200  that may be used to generate a unique identifier for one or more wireless power receiver within a wireless power network. 
     Method  200  may include automated software embedded on a wireless power receiver chip that may be triggered the first time a wireless power receiver is turned on. 
     In one embodiment, method  200  may start at step  202  when a wireless power receiver, either a cover or a customer pocket-forming enable device, boots up the first time within a wireless power network. Then, at step  204 , method  200  may check if the ID flag at a unique address is in non-volatile (NV) RAM is set in the wireless power receiver. If ID flag is set, at step  206 , the method  200  reads from its unique address in NVRAM in the wireless power receiver and it continues normal operation. If ID flag is not set, then at step  208 , the method  200  triggers a suitable random number generator method to generate a random ID which may be 32-bits or greater. Once the ID is generated, at step  210 , the method  200  writes the ID to its unique address in NV RAM. Finally, at step  212 , method  200  may write the unique 32-bits (or greater) ID flag to unique address in NV RAM, read ID from NV RAM and continue normal operation. 
     In another embodiment, method  200  may also be used to not only generate unique IDs for wireless power receivers, but also to generate unique IDs for wireless power transmitters and GUIs. By generating unique IDs for each of the components in a wireless power network, the components may be more easily associated to users and have friendly names. For example, a user may have in his or her home more than one wireless power transmitter located at different places such as the living room, bedrooms, and kitchen among others. Then the power transmitter&#39;s unique ID may be associated with a custom label for each of the wireless power transmitters at different locations. 
       FIG. 3  shows a flowchart of a method  300  for registering and associating one or more wireless power receivers to a wireless power network. 
     In one aspect of the present disclosure, method  300  may include automated software embedded on a wireless power receiver chip that may be triggered when a wireless power receiver boots up. Therefore, method  300  may start at step  302 , when a wireless power receiver boots up when turned on by the user. Then, at step  304 , the wireless power receiver broadcasts advertisement, which may include a unique ID number, to any power transmitter manager and GUI that is within its range. Next, at step  306 , power transmitter manager and GUI, that are within the radio of the wireless power receiver broadcast, receive and decode the advertisement. Then, power transmitter manager, at step  308 , may store the unique ID number of said wireless power receiver in a database. This database may serve to store relevant information from wireless power receivers such as, identifiers, voltage ranges, location, signal strength and/or any relevant information. Following method  300 , at step  310 , GUI may update and sync all relevant information from said transmitter&#39;s database for better control of the wireless power devices. At step  312 , GUI may ask the user to assign a name for the wireless power receiver that may have joined the wireless power network. Next, at step  314 , the user assigns a name of its preference. Then, at step  316 , GUI syncs that name and stores it in its database. Finally, at step  318 , power transmitter manager reads name from GUI database and updates its own database copy. The system database in power transmitter devices and GUI devices may be identical between every device, when up to date. All system devices may operate and communicate so as to keep each one&#39;s database up to date. 
     The foregoing method descriptions and the process flow diagrams 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. 
     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. 
     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. 
     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. 
     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. 
     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.