Systems and Methods for Communication with Remote Management Systems

[0001] The present disclosure is related to U.S. patent application Ser. No. 13/891,399 entitled Receivers For Wireless Power Transmission, filed May 10, 2013, U.S. patent application Ser. No. 13/891,430 entitled Methodology For Pocket-Forming, filed May 10, 2013, and U.S. patent application Ser. No. 13/891,445 entitled Transmitters For Wireless Power Transmission, filed May 10, 2013, each of which are incorporated by reference in their entirety herein.

[0002] 1. Field of the Disclosure

[0003] The present disclosure relates in general to wireless power transmission systems, and more specifically to systems and methods for establishing communications with remote management systems.

[0004] 2. Background Information

[0005] Electronic devices such as laptop computers, smartphones, portable gaming devices and tablets, amongst others, 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. Additionally, users may be required to plugin to a wall or other power supply to be able to charge his or her electronic device. However, such an activity may in some cases render electronic devices inoperable during charging.

[0006] For the foregoing reasons, there is a need for simple, reliable and user friendly wireless power transmission systems where electronic devices may be powered without requiring extra chargers or plugs, and where the mobility and portability of electronic devices may not be compromised.

[0007] Various exemplary embodiments of the present disclosure describe systems and methods for communication between wireless power transmission systems and remote management systems. The disclosed systems may include power transmitters, power receivers, electronic devices and suitable remote system managers.

[0008] Power transmitters may be utilized for wireless power transmission using suitable techniques such as pocket-forming. Transmitters may be employed for sending Radio frequency (RF) signals to power receivers. Power receivers may be capable of converting RF signals into suitable electricity for powering and charging a plurality of electric devices. Wireless power transmission may allow powering and charging a plurality of electrical devices without wires.

[0009] The disclosed wireless power transmission systems may periodically perform system checkups to generate past, present and future status reports.

[0010] According to some embodiments, past status reports may include details such as the amount of power delivered to each of the electronic devices in the system during a certain time period, the amount of energy that was transferred to a group of electronic devices associated with a user, the amount of time an electronic device has been associated to a wireless power transmitter, pairing records, activities within the system, any action or event of any wireless power device in the system, errors, faults, and configuration problems, among others. Past system status data may also include power schedules, names, customer sign-in names, authorization and authentication credentials, encrypted information, areas, details for running the system, and any other suitable system or user-related information.

[0011] According to some embodiments, present status report may include any present failure, error or abnormal function of any system or subsystem components; a list of presently online end-users and devices, current system configuration and power schedules, amongst others.

[0012] According to some embodiments, future status reports may include forecasts based on the evaluation of past and present system status reports. For example, the system may be able to extrapolate possible impending sub-system component failure based on logged past behavior of sub-system components. The system may also be able to evaluate the power schedules and determine if any device will be out of energy according to historical power consumption and current power schedule.

[0013] In some embodiments, the system may further evaluate the system configuration to check if any configuration set by an operator or end-user may cause an unwanted system behavior.

[0014] According to some embodiments, the disclosed systems may be capable of evaluating if the generation of an alert is needed. If an alert is needed, the alert may be generated and sent. Depending of the type of problem detected, the alerts may be sent to the end-users, the system's owner, the service provider or any suitable combination.

[0015] According to some embodiments, using a suitable TCP/IP connection the wireless power systems may be able to send reports to a remote system manager for further evaluation. In some embodiments, the wireless power system may receive feedback from the remote system manager.

[0016] According to some embodiments, the wireless power transmitters within a system may be capable of establishing a suitable TCP/IP connection with a remote management system to validate or authenticate end-user credentials.

[0017] Numerous other aspects, features and benefits of the present disclosure may be made apparent from the following detailed description taken together with the drawings provided.

[0025] 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.

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

[0027] “Pairing” refers to the association of a single electronic device with a single power receiver.

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

[0029] “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.

[0030] “Null-space” may refer to areas or regions of space where pockets of energy do not form because of destructive interference patterns of RF waves.

[0031] “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.

[0032] “Receiver” may refer 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.

[0033] “wireless power transmission” may refer to transmitting energy wirelessly.

[0034] The various exemplary embodiments presented here describe systems and methods for communication between wireless power transmission systems and remote management systems. The disclosed systems may include power transmitters, power receivers, electronic devices and suitable remote system managers.

[0035] FIG. 1 shows a wireless power system architecture 100, according to an exemplary embodiment. System architecture 100 may include one or more wireless power transmitters 102, and one or more wireless power receivers 104. In some embodiments, wireless power system architecture 100 may include one or more electronic devices 106, where electronic devices 106 may not have a built-in wireless power receiver 104. In other embodiments, wireless power system architecture 100 may include electronic devices 108 with a built-in power receiver 104.

[0036] Power transmitters 102 may 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.

[0037] According to exemplary embodiments, power transmitters 102 may include a power transmitter manager application 110, a third party Bluetooth Low Energy (BTLE) API 112, a BTLE chip 114, an antenna manager software 116 and an antenna array 118 among other components. Power transmitter manager application 110 may be an executable program loaded into a non-volatile memory within a power transmitter 102. Power transmitter manager application 110 may control the behavior of power transmitter 102, monitor the state of charge of electronic devices 106, electronic devices 108 and power receivers 104, may keep track of the location of power receivers 104 and may execute power schedules, amongst others. In some embodiments, power transmitters 102 may include a distributed wireless power transmission system database (not shown in figure) for storing information related to power receivers 104, electronic devices 106, power status, power schedules, IDs, pairing and any suitable information necessary for running the system.

[0038] Third party BTLE API 112 may enable the effective interaction between power transmitter manager application 110 and BTLE chip 114. Antenna manager software 116 may process orders from power transmitter manager application 110 and may control power and direction angle of antenna array 118.

[0039] Antenna arrays 118 that may be included in power transmitters 102 may include a number of antenna elements capable of transmitting power. In some embodiments, antenna array 118 may include from up to 512 antenna elements which may be distributed in an equally spaced grid. In one embodiment, antenna array 118 may have an 8×8 grid to have a total of 64 antenna elements. In another embodiment, antenna array 118 may have a 16×16 grid to have a total of 256 antenna elements. In another embodiment, antenna array 118 may have a total of 512 antenna elements. However, the number of antenna elements may vary in relation with the desired range and power transmission capacity of power transmitter 102. Generally, with more antenna elements, a wider range and higher power transmission capacity may be achieved. Alternate configurations may also be possible including circular patterns or polygon arrangements, amongst others.

[0040] The antenna elements of antenna array 118 may include suitable antenna types for operating in frequency bands such as 900 MHz, 2.5 GHz, 5.250 GHz, or 5.8 GHz, antenna elements may operate in independent frequencies, allowing a multichannel operation of pocket-forming.

[0041] Power transmitter 102 may additionally include other suitable communications methods such as Wi-Fi, Zig bee and LAN amongst others.

[0042] Power receivers 104 may include a power receiver application 120, a third party BTLE API 112, a BTLE chip 114, and a power reception antenna array 122. Power receivers 104 may be capable of utilizing pockets of energy produced by power transmitter 102 for charging or powering electronic devices 106 and electronic devices 108. Power receiver application 120 may be an executable program loaded into a non-volatile memory within a power receiver 104.

[0043] Third party BTLE API 112 may enable the effective interaction between power receiver application 120 and BTLE chip 114. Antenna array 122 may be capable of harvesting power from pockets of energy.

[0044] Electronic devices 106 and electronic devices 108 may include a GUI for managing the wireless power system architecture 100. The GUI may be associated with an executable program loaded into a non-volatile memory. In some embodiments, electronic devices 106 and electronic devices 108 may include a distributed wireless power transmission system database (not shown in figure) for storing information related to power receivers 104, power status, power schedules, IDs, pairing and any suitable information necessary for running the system.

[0045] In some embodiments, wireless power system architecture 100 may include multiple power transmitters 102 and/or multiple power receivers 104 for charging a plurality of electronic devices 106. In systems including multiple power transmitters 102, the two or more power transmitters may be in constant communication using any suitable communication channel available, including Bluetooth, BTLE, Wi-Fi, Zig bee, LAN, LTE and LTE direct amongst others.

[0046] FIG. 2 illustrates a wireless power transmission system network 200, according to an exemplary embodiment.

[0047] According to some embodiments, wireless power transmission system network 200 may include multiple wireless power transmission system 202 capable of communicating with a remote management system 204 through internet cloud 206.

[0048] In some embodiments, wireless power transmission system 202 may include one or more wireless power transmitters 208, one or more power receivers 210, one or more back-up servers 212 and a local network 214.

[0049] According to some embodiments, each power transmitter 208 may include a wireless power transmitter manager 216 and a distributed wireless power transmission system database 218. Each power transmitter 208 may be capable of managing and transmitting power to one or more power receivers 210, where each power receiver 210 may be capable of charging or providing power to one or more electronic devices 220.

[0050] Power transmitter managers 216 may control the behavior of power transmitters 208, monitor the state of charge of electronic devices 220, and power receivers 210, may keep track of the location of power receivers 210 and may execute power schedules, run system check-ups and keep track of the energy provided to each of the different electronic devices 220, amongst others.

[0051] According to some embodiments, database 218 may store relevant information from electronic devices 220 such as, identifiers for electronic devices 220, voltage ranges for electronic devices 220, location, signal strength and/or any relevant information from electronic devices 220. Database 218 may also store information relevant to the wireless power transmission system 202 such as, receiver ID's, transmitter ID's, end-user handheld device names ID's, system management server ID's, charging schedules, charging priorities and/or any data relevant to a power transmission system network 200.

[0052] Additionally, in some embodiments, database 218 may store data of past and present system status.

[0053] The past system status data may include details such as the amount of power delivered to an electronic device 220, the amount of energy that was transferred to a group of electronic devices 220 associated with a user, the amount of time an electronic device 220 has been associated to a wireless power transmitter 208, pairing records, activities within the system, any action or event of any wireless power device in the system, errors, faults, and configuration problems, among others. Past system status data may also include power schedules, names, customer sign-in names, authorization and authentication credentials, encrypted information, physical areas of system operation, details for running the system, and any other suitable system or user-related information.

[0054] Present system status data stored in database 218 may include the locations and/or movements in the system, configuration, pairing, errors, faults, alarms, problems, messages sent between the wireless power devices, and tracking information, among others.

[0055] According to some exemplary embodiments, databases 218 within power transmitters 208 may further store future system status information, where the future status of the system may be forecasted or evaluated according to historical data from past system status data and present system status data.

[0056] In some embodiments, records from all device databases 218 in a wireless power transmission system 202 may also be stored and periodically updated in server 212. In some embodiments, wireless power transmission system network 200 may include two or more servers 212.

[0057] In another exemplary embodiment, wireless power transmitters 208 may further be capable of detecting failures in the wireless power transmission system 202. Examples of failures in power transmission system 202 may include overheating of any component, malfunction, and overload, among others. If a failure is detected by any of wireless power transmitters 208 within the system, then the failure may be analyzed by any wireless power transmitter manager 216 in the system. After the analysis is completed, a recommendation or an alert may be generated and reported to owner of the power transmission system or to a remote cloud-based information service, for distribution to system owner or manufacturer or supplier.

[0058] In some embodiments, power transmitters 208 may use network 214 to send and receive information. Network 214 may be a local area network, or any suitable communication system between the components of the wireless power transmission system 202. Network 214 may enable communication between power transmitters, the communication of power transmitters with server 212, and may facilitate the communication between power transmission system 202 and remote management system 204, amongst others.

[0059] According to some embodiments, network 214 may facilitate data communication between power transmission system 202 and remote management system 204 through internet cloud 206.

[0060] Remote management system 204 may be operated by be owner of the system, the manufacturer or supplier of the system or a service provider. Remote management system may include business cloud 222, remote manager 224 and backend server 226, where the remote manager 224 may further include a general database 228. Functionality of backend server 226 and remote manager 224 can be combined into a single physical or virtual server.

[0061] General database 228 may store additional backups of the information stored in the device databases 218. Additionally, general database 228 may store marketing information, customer billing, customer configuration, customer authentication, and customer support information, among others. In some embodiments, general database 228 may also store information, such as less popular features, errors in the system, problems report, statistics, and quality control, among others.

[0062] Each wireless power transmitter 208 may periodically establish a TCP communication connection with remote manager 224 for authentication, problem report purposes or reporting of status or usage details, among others.

[0063] FIG. 3 shows a flowchart of a general system status 300 report generation process, according to an exemplary embodiment. Wireless power transmission systems may periodically send status reports to a remote management system, similar to the management systems previously described. General system status 300 report generation process may start with past status report generation 302, in this step any server within a wireless power transmission system may gather information that may include details such as the amount of power delivered to each of the electronic devices in the system during a certain time period, the amount of energy that was transferred to a group of electronic devices associated with a user, the amount of time an electronic device has been associated to a wireless power transmitter, pairing records, activities within the system, any action or event of any wireless power device in the system, errors, faults, and configuration problems, among others. Past system status data may also include power schedules, names, customer sign-in names, authorization and authentication credentials, encrypted information, areas, details for running the system, and any other suitable system or user-related information.

[0064] Then, the server within the wireless power transmission system may run a system check-up 304. In this step, the server within the wireless power transmission system may check for any present failure, error or abnormal function of any system or subsystem components. Additionally, the server within the wireless power transmission system may check and perform an evaluation of the current system configuration.

[0065] Afterwards, the system may generate present status report 306 and future status report 308. Present status report may include any present failure, error or abnormal function of any system or subsystem components; a list of presently online end-users and devices, current system configuration and power schedules, amongst others.

[0066] Future status report 308 may include forecasts based on the extrapolation or evaluation of past and present system status reports. For example, the system may be able to extrapolate possible impending sub-system component failure based on logged past behavior of sub-system components. The system may also be able to evaluate the power schedules and determine is any device will be out of energy according to historical power consumption and current power schedule.

[0067] In some embodiments, the system may further evaluate the system configuration to check if any configuration set by an operator or end-user may cause an unwanted system behavior. Such will be reported using the same techniques described above.

[0068] Then, the wireless power transmitters may evaluate 310 if an alert is needed. If an alert is needed, the alert may be immediately generated and sent 312. Depending of the type of problem detected, the alerts may be sent to the end-users, the system's owner, the service provider or any suitable combination, or to a remote system manager which can distribute a description of this urgent situation to customer service or other personnel via email, text message, or synthesized voice telephone call, according to alert configuration records stored within general database.

[0069] After the alert has been sent or if there is no alert needed, the server within the wireless power transmission system executing the report generation algorithm described in FIG. 3 may update 314 its database with the reports and optionally back them up in a suitable server. If there are multiple servers, then only one at a time will be active for the generation of reports, while the others remain in stand-by mode, to take over if the active server goes offline. A hierarchy of priority will determine which online server is the present active (master) server.

[0070] Then, using a suitable TCP/IP connection the reports may be sent 316 to a remote system manager for further evaluation. In some embodiments, the system may receive 318 feedback from the remote system manager to indicate verification and storage of any received information.

[0071] FIG. 4 is a flowchart of a past status report 400 generation process, according to an exemplary embodiment. The process for generation of a past status report 400 may start with the generation 402 of a non-end-user report, where no-end-user report may include logged activity, commands and configuration inputs of any non-end-user system operator.

[0072] Then, the system may generate 404 a logged usage report which may include logged usage details and wireless energy consumption details. The wireless energy consumption details may include the amount of power delivered to each device and total amount of power delivered to the devices associated with each end user.

[0073] In some embodiments, the logged usage report may be used to compute power bills to charge end-users for the amount of wireless power received during a given time period.

[0074] Then, the system may generate 406 an automatic actions report which may include automatic actions performed by or over any of the system components, including all power transmitters, power receivers, and any system management GUI.

[0075] Subsequently, the system may generate 408 a location and movement report, which may include the location and movement tracking details of power receivers relative to power transmitters in the system.

[0076] After the reports have been generated the system may assemble past status report 400 and update 410 the database.

[0077] Then, using a suitable TCP/IP connection the reports may be sent 412 to a remote system manager for further evaluation. In some embodiments, the system may receive 414 feedback from the remote system manager to indicate verification and storage of any received information.

[0078] FIG. 5 is a flowchart of a present status report 500 generation process, according to an exemplary embodiment. The process of generation of present status reports 500 may start with the generation 502 of a system functioning report, in which the system may evaluate the performance of each of the systems components to detect any failure, error or abnormal function of any system or subsystem component. Then the system may generate 504 a list of all online users and devices. Afterwards, the system may generate 506 a report of the current system configuration.

[0079] Additionally, the system may check 508 the state of charge all the electronic devices within the system. If any electronic device within the system is in urgent need 510 of charge the system may generate and send 512 an alert. The alert may be sent to the users in form of text messages, emails, voice synthesis telephone communication or any other suitable means.

[0080] In some embodiments, whenever an electronic device has a minimum amount of energy left the system may be capable of contacting the end-user to make the end user aware of the current state of charge of the electronic device.

[0081] After the reports have been generated the system may assemble present status report 500 and update 514 the database.

[0082] Then, using a suitable TCP/IP connection the reports may be sent 516 to a remote system manager for further evaluation. In some embodiments, the system may receive 518 feedback from the remote system manager to indicate verification and storage of any received information.

[0083] FIG. 6 is a flowchart of a future status report 600 generation process, according to an exemplary embodiment. The process of generation of future status report 600 may start with the generation 602 of a component failure forecast in which impending sub-system component failure may be extrapolated from logged past behavior of sub-system components. Then the system may generate 604 a device state of charge forecast, based on present rate of energy consumption of the devices, configured charging schedule, logged usage and any other suitable parameter. In this step the system may determine if any device will reach an unexpected critically low level of charge at some point in the future.

[0084] Afterwards, the system may perform 606 a system configuration analysis, in which the system may evaluate any configuration set by the system operator or end-user to determine if it may cause any unwanted system behavior.

[0085] Then, if a problem was found 608 in any of the first 3 steps, the system may generate a suitable alert 610. If an alert is sent to an end-user or system operator it may be in the form of text messages, emails, voice synthesis telephone communication or any other suitable means. In some embodiments, the system provider may be contacted by similar means.

[0086] Afterwards, the system may assemble future status report 600 and update 612 the database.

[0087] Subsequently, using a suitable TCP/IP connection the reports may be sent 614 to a remote system manager for further evaluation. In some embodiments, the system may receive 618 feedback from the remote system manager to indicate verification and storage of any received information.

[0088] In example #1 a wireless power transmission system generates a general status report as described in FIG. 3. When checking the state of charge of the electronic devices within the system, an electronic device with critically low level of charge and no scheduled charge time is identified. In this example, the wireless power system is able to contact the owner of the electronic device via SMS message. The user schedules a charging period for the device and the device is charged before it runs out of energy.

[0089] In example #2 a wireless power transmission system generates a general status report as described in FIG. 3. When checking the system configuration a possible unwanted behavior is identified. A device is scheduled to charge for too long without usage, which may cause overheating of some components. In this example, the power transmitter send a report to the remote management system and the remote management system sends an alert via email to the user.

[0090] In example #3 a wireless power service provider utilizes the past status reports generated by wireless power delivery system over the past 30 days to compute bills and charge end-users for their wireless power consumption.

[0091] In example #4 an end-user's electronic device requests wireless power. The wireless power transmitter utilizes a suitable TCP/IP connection to communicate with a remote system manager and authenticate the end-users credentials. The credentials of the end-user are authenticated and the electronic device is charged.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.