WO2016038607A1

WO2016038607A1 - System and methods for using ultrasonic communication for control of wireless power transfer

Info

Publication number: WO2016038607A1
Application number: PCT/IL2015/050913
Authority: WO
Inventors: Moshe Raines; Ian Podkamien
Original assignee: Powermat Technologies Ltd.
Priority date: 2014-09-09
Filing date: 2015-09-08
Publication date: 2016-03-17

Abstract

The disclosure relates to systems and methods for managing a wireless power transfer to electrical mobile devices. In particular the invention relates to managing wireless power transfer to mobile devices via a wireless power outlet supporting wireless power provisioning networks using audio signal connectivity. Some electrical mobile devices operable for wireless charging do not have a receiver identifier. The current disclosure represents a technical solution and provides these electrical mobile devices conditional access in public places by coupling an electronic device with a power transfer network. More specifically, the current disclosure introduces ultrasonic bidirectional communication to enable handshake between an electrical device and a wireless power outlet supporting the power transfer protocol, enabling of identification exchange to allow power transfer.

Description

SYSTEM AND METHODS FOR USING ULTRASONIC COMMUNICATION FOR CONTROL OF WIRELESS POWER TRANSFER

FIELD OF THE INVENTION

The disclosure herein relates to systems and methods for managing wireless power transfer to electrical mobile devices. In particular the invention relates to managing wireless power transfer using audio signal connectivity, such as ultrasonic communication, to enable wireless powering of mobile devices in power transfer networks or may use Bluetooth, for any communications between the electric mobile device and the wireless power transmitter.

BACKGROUND OF THE INVENTION

The spread of mobile devices such as mobile handsets, media players, tablet computers and laptops/notebooks/netbooks and ultra-books increases user demand for access to power points at which they may transfer power to charge mobile devices while out and about or on the move.

Wireless power transfer allows energy to be transferred from a power supply to an electric load without a wired connection therebetween. The power transfer may use various transfer methods such as inductive coupling, resonant, non-coupled, RF and more.

By way of example, when electrical energy is transferred from a primary inductor to a secondary inductor, the inductors are said to be inductively coupled. An electric load wired in series with such a secondary inductor may draw energy from the power source wired to the primary inductor when the secondary inductor is inductively coupled thereto.

There is a need for systems that conveniently provide the opportunity to transfer power for charging the electrical mobile devices in public spaces, in which the user of the mobile device may remain for extended periods of time, say more than a few minutes or so. Amongst others, such public spaces may include restaurants, coffee shops, airport lounges, trains, buses, taxis, sports stadia, auditoria, theatres, cinemas or the like. Such systems may be distributed over various venues, requiring complex network architecture to provide the demand for wireless power transfer in public spaces. Each power transfer servicing venue may be equipped with wireless power outlets supporting a protocol or technology such as resonant, non-resonant, magnetic beam, inductive power transfer and the like.

The Power Matters Alliance (PMA) wireless power transfer network architecture, for example, is policy based, and allows wireless power transfer only on certain terms. A PMA wireless power receiver (Rx) may transmit their ID (RxID) to a wireless power outlet (Tx) using the inductive in-band protocol. The outlet Tx sends in turn its ID (TxID) together with the RxID to a centrally managed control server to get permission to provide power. Yet, existing legacy electrical mobile devices operable for wireless charging do not have a PMA identification ID (RxID) to enable communication with the wireless power outlet and joining the wireless power transfer network.

It is noted that there are various methods of implementing the identification code of the wireless power receiver (RxID) and for the wireless power transmitter (TxID). By way of example, the Alliance for Wireless Power (A4WP) provide such identification codes for the receiver (RxID) and transmitter (TxID) via their Bluetooth MACID.

The invention described hereinafter addresses the above-described needs providing the mechanism to control operable wireless power devices which may not be labeled.

SUMMARY OF THE INVENTION

It is according to one aspect of the disclosure, a system for controlling a wireless power transfer network, said system comprising: at least one electrical device comprising a wireless power receiver and executing a wireless power software application operable to control wireless power transfer to the at least one electrical device via the wireless power receiver; and at least one wireless power outlet operable to transfer power to the at least one electrical device;

wherein: the at least one electrical device is labeled with a device identifier and comprises an audio signal receiver; the at least one wireless power outlet comprises a transducer configured to transmit at least one audio signal of a type receivable by the audio signal receiver associated with the at least one electrical device, the at least one audio signal communicating a wireless power outlet identification code; and wherein the wireless power software application is operable to associate the at least one electrical device with the at least one wireless power outlet and control wireless power provisioning to the wireless power receiver.

As appropriate, the audio signal receiver comprises a microphone and an audio speaker associated with the at least one electrical device.

As appropriate, the transducer comprises an audio speaker and a microphone associated with the at least one wireless power outlet.

As appropriate, the at least one audio signal is at least one ultrasonic signal.

As appropriate, the at least one audio signal comprises data pertaining to the wireless power outlet identification.

Optionally, the device identifier is selected from a group consisting of: a device identification code, an international mobile equipment identity (IMEI), an application code associated with the power software application and combinations thereof.

It is according to another aspect of the disclosure, a computer implemented method is taught for a management control server to control wireless power transfer from at least one wireless power outlet to a wireless power receiver associated with an electrical device, the electrical device executing a software wireless power application and being labeled with a device identifier, the at least one wireless power outlet being labeled with a wireless power outlet identification code, the method comprising:

• receiving at least a first message from the at least one wireless power outlet communicating at least the wireless power outlet identification code and data pertaining to location of the at least one wireless power outlet;

• receiving at least a second message from the electrical device communicating, via the software wireless power application, at least the device identifier, the wireless power outlet identification code and data pertaining to device location and a carrier of the electrical device;

• comparing the wireless power outlet identification code associated with the at least a first message and the wireless power outlet identification code associated with the at least a second message; and • providing an approval response message to the at least one wireless power outlet only if the wireless power outlet identification code associated with the at least a first message matches the wireless power outlet identification code associated with the at least a second message.

It is according to yet another aspect of the disclosure, a computer implemented method is taught for an electrical device configured to receive power transfer via a wireless power receiver conductively connected thereto, the electrical device labeled with a device identifier operable to activate wireless power transfer from a wireless power outlet labeled with a wireless power outlet identification code to the wireless power receiver, the method comprising:

• executing a power transfer software application on the electrical device;

• accessing, by the power transfer software application, a configuration data of the electrical device;

• sending, by the power transfer software application, at least a detection signal such that the wireless power outlet sends at least a first message communicating the wireless power outlet identification code to a control server and a second message communicating the wireless power outlet identification code to the electrical device via power transfer software application; and

• sending, by the power transfer software application, at least a third message communicating at least the device identifier, the wireless power outlet identification code, data pertaining to device configuration and data pertaining to device carrier to the control server.

As appropriate, the method wherein the step of executing the power transfer software application comprises:

• downloading the power transfer software application to the electrical device;

• installing the power transfer software application onto the electrical device; and

• configuring the power transfer software application to communicate with the control server. As appropriate, the method, wherein the step of sending at least a third message comprises:

• opening a microphone associated with the electrical device in listen mode; and

• closing the microphone after waiting a pre-configured wait time.

Optionally, the wireless power receiver is selected from a group consisting of ring devices, dongles, cases, skins, back-covers, embedded devices, add-ons and wirelessly enabled batteries.

It is according to still another aspect of the disclosure, a computer implemented method is taught for a wireless power outlet configured and operable to bi-directionally communicate with an electrical mobile device via a power transfer software application and to provide power transfer to the electrical mobile device via a wireless power receiver, the wireless power outlet labeled with a wireless power outlet identification code and operable to receive an activation signal, the electrical mobile device labeled with a device identifier, the method comprising:

• receiving at least one detection signal from the electrical mobile device via power transfer software application;

• sending at least a first communication message communicating at least the wireless power outlet identification code to the electrical mobile device via power transfer software application;

• sending at least a second communication message communicating at least the wireless power outlet identification code to at least one control server via a network communication interface;

• receiving a power response message from the at least one control server; and

• providing wireless power transfer to the wireless power receiver if the power response authorizes powering.

Where appropriate, the wait time is associated with the setup time required by the power transfer software application.

Where appropriate, the at least second communication message further comprises data pertaining to at least one of a location and a timestamp. Optionally, the device identifier is selected from a group consisting of: a device identification code (UDID), an international mobile equipment identity (IMEI), an application code associated with the power software application.

Optionally, the network communication interface is selected from a group consisting of: a proprietary application programming interface (API), a Zigbee interface, a WiFi interface and combinations thereof.

It is according to a further aspect of the disclosure, a system for controlling a wireless power transfer network, the system comprising: at least one electrical device comprising a wireless power receiver and executing a wireless power software application; at least one wireless power outlet operable to transfer power to the at least one electrical device; and at least one control server in communication with the at least one electrical device and the wireless power outlet operable to control wireless power transfer to the at least one electrical device via the wireless power receiver,

wherein: the at least one electrical device is labeled with a device identifier and comprises an audio signal receiver; the at least one wireless power outlet comprises a transducer configured to transmit at least one audio signal of a type receivable by the audio signal receiver associated with the at least one electrical device, the at least one audio signal communicating a wireless power outlet identification code; and wherein the at least one control server is operable to: receive a first communication message from the at least one electrical device via the wireless power software application and a second communication message from the at least one wireless power outlet, the first communication and the second communication including the wireless power outlet identification code such that the at least one control server is operable to associate the at least one electrical device with the at least one wireless power outlet and control wireless power provisioning to the wireless power receiver.

Optionally, the first communication message further comprises data selected from a group consisting of: a device identifier, data pertaining to a carrier, data pertaining to said at least one electrical device and combinations thereof.

Optionally, the second communication message further comprises data selected from a group consisting of: data pertaining to a location, a timestamp and combinations thereof.

BRIEF DESCRIPTION OF THE DRAWINGS For a better understanding of the embodiments and to show how it may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings.

With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of selected embodiments only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects. In this regard, no attempt is made to show structural details in more detail than is necessary for a fundamental understanding; the description taken with the drawings making apparent to those skilled in the art how the several selected embodiments may be put into practice. In the accompanying drawings:

Fig. 1A is a block diagram illustrating the main elements of managing power transfer by a wireless power outlet (Tx) to a wireless power receiver (Rx) with a feedback signal path according to embodiments of the present invention;

Fig. IB is a block diagram illustrating the main elements of managing power transfer by a wireless power outlet (Tx) to a wireless power receiver (Rx) an inductive feedback channel according to still another embodiment of the present power transfer system invention;

Fig. 2 is a system diagram schematically illustrating selected components of a network architecture with the various application interfaces;

Fig. 3 is a block diagram schematically illustrating system architecture for providing wireless power transfer services to electrical mobile devices in a possible servicing venue deployment;

Fig. 4 is a block diagram schematically illustrating an expanded view of the system architecture for providing wireless power transfer services to electrical mobile devices ;Fig. 4A is a screen display illustrating a management functionality for non- compliant electrical mobile devices; Fig. 4B is a flowchart representing selected actions of a possible method to enable wireless power transfer in the system architecture for non-compliant electrical mobile devices;

Fig. 5A is a flowchart representing selected actions of a possible method for a policy based activation sequence using a power transfer protocol in a power network;

Fig. 5B is a flowchart representing selected actions of a possible method for an activation sequence using a power transfer protocol in a power network for a non- compliant electrical mobile device;

Fig. 5C is a flowchart representing selected actions of a possible method for an exemplified activation sequence for a non-compliant electrical mobile device;

Fig. 6A is a flowchart representing selected actions of a method for installing and initializing a power transfer software application for managing wireless power transfer;

Fig. 6B is a flowchart representing further possible actions of a method for enabling a communication device to activate a wireless power outlet; and

Fig. 7 is a flowchart illustrating selected actions of a possible method representing the user experience for managing and controlling wireless power transfer to a non- compliant electrical mobile device according to the currently disclosed subject matter.

DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely examples of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.

Wireless power transfer systems technologies may use various configurations of coils and magnetic/non-magnetic transfer techniques, such as inductive power transfer technology (non-resonant), magnetic resonance power technology, magnetic beam technology and the like. Thus, not every wireless power transmitter associated with a wireless power outlet is technically operable of transferring wireless power to a wireless power receiver associated with an electrical mobile device.

Aspects of the present invention herein relates to providing systems and methods for managing wireless power transfer to electrical mobile devices, cars and more. In particular the invention relates to managing wireless power transfer to mobile devices via wireless power transfer networks, such as the Power Matters Alliance (PMA), the Alliance for Wireless Power (A4WP), Qi of Wireless Power Consortium (WPC) and the like for example, using audio signals such as ultrasonic connectivity.

Wireless power transfer network architecture such as the PMA architecture is often policy based, and allows wireless power transfer only on certain terms. Compliant wireless power receivers (Rx) transmit their ID (RxID) to the wireless power outlet (Tx) using the inductive in-band protocol. The Tx in turn sends its ID (TxID) together with the RxID to the centrally managed control server to get permission to provide power. Existing legacy (non-compliant) phones, which are wireless power charging enabled, do not have an identification ID (RxID), thus are not allowed to communicate with a network based wireless power outlet nor joining the wireless power transfer network.

The currently disclosed subject matter provides a user dedicated software application using out-of-band communication between the application and the wireless power outlet in form of an ultrasonic bi-directional communication between the Transmitter and the device or other any bi-directional communications, to further allow the software application to communicated with the centrally managed control server, allowing the wireless power outlet for non-compliant electrical mobile devices.

As used herein, a wireless power outlet point may be referred to herein as, variously, a wireless power transmitter, a "PAP" (Power Access Point), a "CS" (Charging Spot), a "hotspot" or a 'charger".

As used herein, a "management server" refers to a server configured to manage multiple wireless power outlets configured to provide power transfer to electrical mobile devices, and controlling the power charging between an electrical mobile device and an associated wireless power outlet. The term "management server" may be referred to herein as, variously, as a "control server", "central server" or a "server".

As used herein, an electrical mobile device may be referred to herein as, variously, a 'user device", an "electrical device", an "electronic device", a 'mobile device", a 'communication device" or a 'device". The device may be an electrical device with a battery, e.g., a mobile handset, a media player, a tablet computer, a laptop/notebook/netbook/ultra-book, a PDA or the like. Alternatively, the device may be an accessory with a battery, such as earphones and the like, or a stand-alone battery. As a further alternatively, the device may be any powered device, including electrical mobile devices without a battery.

As used herein, the term wireless power transfer technology is associated with power transferred possibly over short distances by magnetic fields using inductive coupling between a primary coil and a secondary coil. Inductive power transfer may use resonant or non-resonant driving frequencies. Other equivalent power transfer technologies include other wireless power transfer technologies such as magnetic beam transfer, electric field technologies using capacitive coupling between electrodes, Laser, RF, ultrasonic power transfer, etc.

As used herein, magnetic resonance power technology (also known as a resonant transformer, resonant-inductive coupling, or resonance charging) is associated with power transfer between two inductors that are tuned to resonate at the same natural resonant frequency. Resonance power technology may allow power to be transferred wirelessly over a distance with flexibility in relative orientation and positioning. Based on the principles of electromagnetic coupling, resonance -based chargers generate an oscillating current into a highly resonant coil to create an oscillating electromagnetic field. A second coil with the same resonant frequency receives power from the electromagnetic field and converts it back into electrical current that can be used to power and charge a portable device. Resonance charging may provide spatial freedom, enabling the transmitter (resonance charger) to be separated from the receiver (portable device) by several inches or more. As used herein, the term "in-band transmission" is associated with systems transmitting data and control signals within the same channel or frequency, then the signaling is said to be "in-band." For example, an analog modem transmits control signals and data in the same human voice frequency band.

As used herein, the term "out-of-band transmission" refers to systems transmitting control signals residing in a channel separate from the data, then the signaling are said to be "out-of-band" signals. For example, in ISDN service, the D channel is a dedicated channel for control signals, and the B channels carry the data. The traditional SS7 telephone system uses an entirely separate network for control signals.

It is noted that some power transfer protocol, such as the PMA's, may use magnetic induction, which requires devices to be placed on a charging surface for power transfer to happen. On the other hand, other power transfer protocols may use resonance charging, which may transmit power at greater distances, meaning devices can be a foot or two away from a power transmitter or more and still receive power.

Tx-Rx Communication:

Generally, each electrical mobile device may have a unique identifier, which may be referred to as a receiver identification (RxID), in the system that allows the recognition thereof. The RxID may be a MAC address. The management server may store user or electrical mobile device related information in addition to the RxID, such as power transfer related data, billing information, user credits and the like.

Where appropriate, wireless power outlets may have a unique identifier, which may be referred to as a transmitter identification (TxID), in the system that allows the recognition thereof.

For illustrative purposes only, possible methods for providing access to power for electrical mobile devices in public spaces are presented hereinafter. The method may allow a user to transfer power or charge an electrical mobile device such as a mobile phone, a tablet or the like from a wireless power outlet and may further allow a power provider to manage the power provision, while gathering power transfer related information. A user may place or connect an electrical mobile device to a wireless power outlet. For example an inductively enabled device may be placed upon a wireless power outlet. Alternatively, or additionally, a power supply may be conductively connected to an electrical mobile device.

The power access point may detect the electrical mobile device connection. For example, wired connection may be detected by detecting the load and wireless connection may be detected using various remote sensors such as hall sensors, analog ping schemes or the like.

Initial Authentication / Handshake:

The wireless power outlet may enable power transfer for a predefined time T_free during which time period user credentials may be authenticated.

Optionally, the wireless power outlet may transmit a random pattern to the device via the close communication. The wireless power outlet may further transmit that same pattern to a control server via a WAN/LAN connection.

For example, a software application running on the electrical mobile device may be operable to receive the pattern and to relay the same pattern to the management server along with user identification token.

Variously, the management server and the electrical mobile device may exchange multiple messages to complete authentication of the user.

Optionally, the wireless power outlet may initiate a registration process upon first- time interaction with the management server to determine initial setup, providing credentials to allow accessing the management server. It is also noted that the first-time authentication may be used for the agreement of the management server to manage the outlet Tx and agreement with regard to the identification of each side, the identity of the outlet Tx and the identity of the management server, for any further communications.

The management server may thereby be able to associate the specific wireless power outlet with the specific wireless power receiver associated with an electrical mobile device. Where the wireless power receiver is associated with a particular electrical mobile device the wireless power outlet may also be associated with that electrical mobile device. Accordingly, if the user is deemed permitted to use the service the management server may send a confirmation signal allowing the wireless power outlet to continue servicing the electrical mobile device. Where required, the confirmation signal may define a specific time period for which the service is granted or send a disconnect event on termination of that time.

Additionally or alternatively, the management server may define multiple levels of service, for example, as may be expressed in terms of services provided to different users. For example, paying users may be allowed access to full powering capability, perhaps up to 20 watts or so, while non-paying users may be provided limited access to, say 0.5 watts, which may be sufficient to charge only low power devices or perform trickle charge for completely depleted batteries.

During operation, the wireless power outlet may be operable to receive operating signals from the management server. According to the operating signals received, the wireless power outlet may be operable to perform various actions such as providing power continuously, aborting power transfer, modifying the service policy or the like.

As noted herein, various methods may be implemented for enabling close communication between the electrical mobile device and the wireless power outlet.

Audio Communication:

The close communication channel between the electrical mobile device and wireless power outlet, of the currently disclosed subject matter may be based upon audio signals sensed via a microphone of the electrical mobile device, using audible bands, 300Hz-20kHz, say. It is particularly noted that the current disclosure may use ultrasonic audible communication at a frequency of 18 kHz and higher, beyond 20 kHz.

The audio signal may be emitted from an audio emitter such as a speaker or the like associated with the wireless power outlet. Many electrical mobile devices, such as mobile phones and the like have microphone and software applications may have access to the microphone.

It is noted that powering the microphone unit may itself demand power. Consequently, the software application running on the electrical mobile device may activate the microphone only where 'a-charge-connect' event is detected in the system. Accordingly, upon device detection the wireless power outlet may provide an initial power transfer to power the microphone. After a short interval, an identification signal may be sent via the audio signal to enable authorizing continuous power transfer.

The audio signal may include additional tones that are not related to the communication pattern which may mask the random patterns communicated. For example, an audio identification signal may be masked by a connection tone serving to provide users with an indication that a connection has been made.

Ultrasonic Communications:

Ultrasonic connectivity technology may enable a mobile electrical device to be paired with a wireless power outlet. Ultrasonic technology requires a speaker to emit sound and a microphone to pick it up. The audio waves of ultrasonic communication may oscillate at a high frequency beyond the range of human hearing (18-20 kHz or higher). The nearby mobile device and the associated outlet are operable to detect this type of audio communication.

It is noted that the wireless power outlet may play a unique or encoded ultrasonic sound through the outlet speaker to communicate its TXID by encoding the numbers representing the TXID into the played ultrasonic sound. The mobile device, placed on upper surface of the wireless power outlet may be operable to receive the associated message communication and pair with the power outlet.

It is specifically noted that using ultrasonic communication technology to broadcast and receive data is operable between nearby devices, but may also be operable in long range perhaps in the cross venue range or higher as suits requirements.

Bluetooth and NFC:

Still other embodiments may use Bluetooth, Bluetooth Low Energy, WiFi, Zigbee or Near Field Communication (NFC) to achieve the close communication channel. These could be combined with the basic power signal to trigger their activation thereby conserving power.

In various embodiments of this system the LAN/WAN interface of the device may be WLAN or Cellular 2G/3G/4G connections. The connection to the WLAN or Cellular access point may also include manual or automatic insertion of user credentials. In this case the information may be conveyed to the management server to enable user identification. The information provided in order to allow access may also be stored by the device application and later provided directly to the management server.

Additionally or alternately, the LAN/WAN connection of the wireless power outlet may be achieved via the charged device. The wireless power outlet may encrypt messages to the management server and deliver this to the application on the communication device via the close communication channel therebetween. The application may then send the message to the server via its LAN/WAN connection.

Power Management:

The power management of PMA wireless power network system of the current disclosure is a centrally managed system operable to execute on at least one control server in communication with at least one wireless power modem associated with a venue providing power charging services.

The centrally managed control server may further communicate with a management console locally or via a communication network such as the Internet.

The centrally managed control server is operable to execute various power management software processes and applications, using various API's (of PMA power transfer protocol, as an example), as described in Fig. 2. The power management software may provide a platform, centrally covering power management aspects of a network of wireless power outlets distributed in public spaces and organizations. The power management software may provide a manager of a venue, for example, the ability to manage the wireless power outlets (hotspots, charging spots) that are installed therein, supporting various power transfer protocols such as PMA, A4WP, WPC, MIMO or other third party power transfer protocols. Optionally, the same management software system, with higher system administration rights, may allow power management of several venues or manage the whole organizational wireless power outlet network. The power management software is operable to provide remote control and monitoring, maintenance of wireless power outlets coupled with system remote health checking. The system is further operable to enable provisioning functionality, maintaining security and business goals using policy enforcement technique. Various functionalities may be available through the power management software, and may also be available to third-party applications through network application programming interfaces (APIs) for the server or another client application. Without limiting the scope of the application, selected functionalities may include, amongst others:

• Using satellite positioning, antenna triangulation, wireless network locations or in-door positioning location information to display a map with nearby public hotspots.

• Booking a Hotspot in advance, and accordingly, the booked Hotspot will not charge for other users, only for the registered user when he arrives, and identified by the unique RxID.

• Registering devices.

• Checking power transfer statistics.

• Buying accessories, charging policies.

• Checking real-time power transfer balances for registered devices.

• Setting notification methods, receiving notifications.

• Setting an automatic check-in to the Hotspot location.

• Setting automatic interactions with social networks, e.g. automatic check-ins, tweets, status updates, and the like.

• Providing store-specific promotion updates via push notifications, for example, based on past and current usage of power transfer services and user's micro- location.

• Using accumulated information of the usage of the wire transfer service, including locations and the like, to better target users with promotions/ads.

• Creating loyalty plans for venues based on usage of the wire transfer services in their premises.

• Providing services to users based on information that their social-network connections are/were at a close proximity.

• Launching a third party application on a user's device based on past or current usage of power transfer services and user's micro-location.

• Collecting statistical information associated with usage of the application It is noted that if communication with the server cannot be established, the application may allow providing power transfer based on a predefined "offline policy". Furthermore, this may imply that the ultrasonic communication may allow the telephone's software application to control locally the charging spot, bypassing the communication network.

Optionally, the management software may provide monitoring of outlet network components, mapping of network elements, maintenance and event management, performance and usage data collector, management data browser and intelligent notifications allowing configurable alerts that will respond to specific outlet network scenarios.

Optionally, the power management software may enforce policies for command and control, these may include operational aspects such as power management aspects, defining who, when and where can charge and for how long, defining type of service (current) and the like.

Optionally, the power management software may include operational aspects of providing power transfer or control billing aspect associated with an electrical mobile device. Thus, the power management software may be operable to provide features such as aborting power provision of a power transfer outlet, continue providing power, modifying the service or controlling one or more aspects of the power transfer procedure by enforcing a new policy, for example, or the like, possibly according to operating signals received. The power management software may further be operable to handle user accounts, registration of devices, user specific information, billing information, user credits and the like.

It is noted the management software may further be operable to detect undesirable conditions while coupling health checking functionality and remote maintenance. For example, events such as adding or removing a wireless power outlet in a venue, may be detected.

Optionally, the system may be configured that when a new wireless power outlet is detected, the system automatically responds in installing an appropriate policy. Additionally or alternatively, the system may configured to transmit an alert the system administrator with an appropriate message.

Communicating with a Control Server:

A wireless power outlet may be operable to transfer wireless power to an electrical mobile device associated with a power receiver and may further be configured to respond to remote commands to enable system functionalities such as identification and authorization, power provisioning, maintenance, health checks and the like. Accordingly, the wireless power outlet needs to be in communication via a communication channel. Such communication channel may be mediated by wireless access points, cellular networks, wired networks or the like that may provide an internet protocol (IP) connection to at least one of the wireless power outlet.

A centrally managed control server may be in communication with the wireless power outlet, directly, if the outlet includes a communication module. More commonly, the wireless power outlet may be managed and controlled via a venue gateway, where the gateway acts as an entrance node (or a stopping point) for the venue internal network. The gateway may further provide the logic of the software application, as communicated and defined by the controlling management server.

It is specifically noted that for the alternatives mentioned above, each requires a different software application according to the associated technology and power-transfer protocol of the wireless power outlet.

The wireless power out of the current disclosure and the wireless power software application are operable to communicate with the control server to provide management functionality to non-compliant electrical mobile devices.

Description of the Embodiments:

It is noted that the systems and methods of the invention described herein may not be limited in their application to the details of construction and the arrangement of the components or methods set forth in the description or illustrated in the drawings and examples. The systems, methods of the invention may be capable of other embodiments or of being practiced or carried out in various ways. Alternative methods and materials similar or equivalent to those described herein may be used in practice or testing of embodiments of the invention. Nevertheless, particular methods and materials are described herein for illustrative purposes only. The materials, methods, and examples are not intended to be necessarily limiting.

Accordingly, various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, it should be appreciated that the methods may be performed in an order different than described, and that various steps may be added, omitted or combined. Also, aspects and components described with respect to certain embodiments may be combined in various other embodiments. It should also be appreciated that the systems, methods, devices, and software may individually or collectively be components of a larger system, wherein other procedures may take precedence over or otherwise modify their application.

Wireless power transfer systems:

Inductive power coupling allows energy to be transferred from a power supply to an electric load without a wired connection therebetween. When electrical energy is transferred wirelessly from a primary inductor to a secondary inductor, the inductors are said to be inductively coupled. An electric load wired in series with such a secondary inductor may draw energy from the power source wired to the primary inductor when the secondary inductor is inductively coupled thereto. Fig. 1A and Fig. IB represent various possible embodiments of a wireless power transfer system.

Reference is now made to Fig. 1A, illustrating schematically a block diagram of the main elements of an inductive power transfer system 100 A adapted to transmit power at a non-resonant frequency according to another embodiment of the invention. The inductive power transfer system 100A consists of an inductive power outlet 200 configured to provide power to a remote secondary unit 300. The inductive power outlet 200 includes a primary inductive coil 220 wired to a power source 240 via a driver 230. The driver 230 is configured to provide an oscillating driving voltage to the primary inductive coil 220.

The secondary unit 300 includes a secondary inductive coil 320, wired to an electric load 340, which is inductively coupled to the primary inductive coil 220. The electric load 340 draws power from the power source 240. A communication channel 120 may be provided between a transmitter 122 associated with the secondary unit 300 and a receiver 124 associated with the inductive power outlet 200. The communication channel 120 may provide feedback signals S and the like to the driver 230.

Reference to the block diagram of Fig. IB, showing another embodiment block diagram of the main elements of an inductive power transfer system 100B. It is a particular feature of certain embodiments of the invention that an inductive communications channel 1120 is incorporated into the inductive power transfer system 100B for transferring signals between an inductive power outlet 1200 and a remote secondary unit 1300. The communication channel 1120 is configured to produce an output signal S_out in the power outlet 1200 when an input signal S_in is provided by the secondary unit 1300 without in tempting the inductive power transfer from the outlet 1200 to the secondary unit 1300.

The inductive power outlet 1200 includes a primary inductive coil 1220 wired to a power source 1240 via a driver 1230. The driver 1230 is configured to provide an oscillating driving voltage to the primary inductive coil 1220, variously at a voltage transmission frequency f_t which is higher or lower than the resonant frequency f_R of the system.

The secondary unit 1300 includes a secondary inductive coil 1320, wired to an electric load 1340, which is inductively coupled to the primary inductive coil 1220. The electric load 1340 draws power from the power source 1240. Where the electric load 1340 requires a direct current supply, for example a charging device for an electrochemical cell or the like, a rectifier 1330 may be provided to rectify the alternating current signal induced in the secondary coil 1320.

An inductive communication channel 1120 is provided for transferring signals from the secondary inductive coil 1320 to the primary inductive coil 1220 concurrently with uninterrupted inductive power transfer from the primary inductive coil 1220 to the secondary inductive coil 1320. The communication channel 1120 may provide feedback signals to the driver 1230. The inductive communication channel 1120 includes a transmission circuit 122 A and a receiving circuit 1 124. The transmission circuit 1 122 is wired to the secondary coil 1320, optionally via a rectifier 1330, and the receiving circuit 1124 is wired to the primary coil 1220.

The signal transmission circuit 1122 includes at least one electrical element 2126, selected such that when it is connected to the secondary coil 1320, the resonant frequency f_R of the system or its quality factor changes. The transmission circuit 1 122 is configured to selectively connect the electrical element 1 126 to the secondary coil 1320. As noted above, any change in either the inductance L or the capacitance C changes the resonant frequency of the system similarly, any change in the resistance of the system may effectively shift the resonance frequency by changing the quality factor. Optionally, the electrical element 1126 may be have a low resistance for example, with a resistance say under 50 ohms and Optionally about 1 ohm.

It is particualarly noted that the electrical element 1126, such as a resistor for example, may act to change the effective resonant frequency of the system by damping or undamping the system and thereby adjusting the quality factor of thereof.

Typically, the signal receiving circuit 1 124 includes a voltage peak detector 1 128 configured to detect large increases in the transmission voltage. In systems where the voltage transmission frequency f_t is higher than the resonant frequency f_R of the system, such large increases in transmission voltage may be caused by an increase in the resonant frequency f_R thereby indicating that the electrical element 1126 has been connected to the secondary coil 1320. Thus the transmission circuit 1122 may be used to send a signal pulse to the receiving circuit 1124 and a coded signal may be constructed from such pulses.

According to some embodiments, the transmission circuit 1122 may also include a modulator (not shown) for modulating a bit-rate signal with the input signal S_in. The electrical element 1126 may then be connected to the secondary inductive coil 1320 according to the modulated signal. The receiving circuit 1124 may include a demodulator (not shown) for demodulating the modulated signal. For example the voltage peak detector 1128 may be connected to a correlator for cross-correlating the amplitude of the primary voltage with the bit-rate signal thereby producing the output signal S_out.

In other embodiments, a plurality of electrical elements 1126 may be provided which may be selectively connected to induce a plurality of voltage peaks of varying sizes in the amplitude of the primary voltage. The size of the voltage peak detected by the peak detector 1128 may be used to transfer multiple signals.

Network API Communication:

The deployment of wireless power transfer infrastructure may enable the provision of convenient access to wireless power transfer in public venues. Accordingly, a smart, manageable, global wireless power transfer network may allow a wider deployment of wireless power provision for mainstream technology and possible standardization of a network architecture and associated APIs. The API of the Power Matters Alliance (PMA), is described hereinafter, as an example.

Reference is now made to the system diagram of Fig. 2 showing a network architecture representation of a wireless power transfer system 200A with various application interfaces.

It is particularly noted that the network architecture representation 200A, the entities and the associated application interfaces may be used to facilitate standardization of the Application Programming Interfaces (APIs) between the various entities while keeping flexibility to accommodate for innovative approaches.

The network architecture representation 200A includes a first venue architecture 202A, a second venue architecture 202B connectable to a certified device manufacturer (PCDM) 206-1 and a wireless charging spot provider (WCSP) 208-1 through a cloud network service (PCS) 204-1. The first venue architecture 202A and the second venue architecture 202B may further include various network entities.

By way of illustration, in this particular embodiment, the first venue architecture 202A may include a wireless power receiver (Rx) 214A entity connectable to at least one wireless power transmitter (Tx) 216A entity in communication with at least one transmitter gateway (T-GW) 218A entity. The wireless power receiver 214A entity may further be connectable to a User Control Function (UCF) 212A entity. The second venue architecture 202A may include a wireless power receiver 214B, wireless power transmitters 216B, and a transmitter gateway (T-GW) 218B entity in a similar network architecture, possibly differing in the number of network entities, depending on venue servicing capability.

Where appropriate, the wireless power receiver is the entity receiving the power possibly for charging or powering an electrical client device.

Where appropriate, the wireless power transmitter is the entity transmitting the power. Optionally, the wireless power transmitter may be operable to support simultaneously a single power receiver and multiple power receivers.

The term T-GW refers to a Transmitter Gateway function, connecting one or more wireless power transmitter entities to the Internet and serving as an aggregator for multiple wireless power transmitter devices located in a venue.

The term UCF refers to a User Control Function, a logical function providing the user with an interface to the charging service. Accordingly, where appropriate, the UCF is operable to provide a user with services such as searching for wireless charging spot locations, device activation, service subscription, statues monitoring and the like. Optionally, a UCF may be collocated with a power receiver or implemented on a separate device.

The term PCS refers to a cloud service, a centralized system providing cloud service management for the wireless power transfer network.

The term PCDM refers to a certified device manufacture.

The term WCSP refers to a wireless charging spot service providers, ranging from a large-scale provider controlling multiple cross-nation wireless charging spot deployments down to a single wireless charging spot coffee shop.

It is particularly noted that the various network entities are connectable via an associated Application Programming Interface API, applicable to interfacing any two connectable network entities, as described hereinafter The network architecture representation 200A includes an RX-TX API interface PI between a wireless power receiver and a transmitter, an RX-UCF API interface P2 between a UCF and a wireless power receiver, a TX-TGW API interface NP5 between a transmitter and a transmitter gateway, a TGW-PCS API interface Nl between a transmitter gateway and a cloud server or network management server, a UCF-PCS API interface N2 between a cloud service or a network management server and a user control function entity, a PCS-WCSP API interface N3 between a cloud service and wireless charging spot service provider, a PCS-PCDM API interface N4 between a cloud service and a certified manufacturer and a UCF API interface SI for a UCF collocated with an wireless power receiver.

It is noted that where appropriate the RX-UCF API interface P2 may not be required depending on the wireless power receiver type, allowing for support of embedded UCF function as well as aftermarket add on. Accordingly, the P2 API may be technology agnostic.

It is further noted that the TX-TGW API interface NP5 may be an open interface left for vendor specific implementation.

The TGW-PCS API interface Nl may be an IP based interface supporting initial provisioning and initialization of a wireless power transmitter and a T-GW, continuous usage reporting between the two entities and continuous provisioning and policy settings for a wireless power transmitter connected to a T-GW. Support of admission and change control for wireless power receiver devices coupled with the controlling of a wireless power transmitter is further included.

The UCF-PCS API interface N2 may be an IP based interface carried over OOB bearer services of the UCF (cellular WLAN etc.). Optionally, the interface N2 may be carried via the wireless charging receiver and transmitter. The UCF-PCS API interface N2 may support charging and service subscription provisioning including billing information where required, charging status reporting and charging spot location data. Additionally, target value messaging from a service provider via PCS may further be supported. Examples of messages for the UCF-PCS API interface N2 are presented below. The PCS-WCSP API interface N3 may be an IP based interface supporting WCSP initial and continuous provisioning and monitoring of its network entities (Transmitter and T-GW), admission policy settings for power receiver on the different power transmitter devices and usage information combined with statistics on different power transmitter and power receiver devices. The PCS-WCSP API interface N3 further supports handling of power receiver subscription (support for centralized or path-through models for subscription and billing info handling) and policy and usage based targeted messaging configuration.

The PCS-PCDM API interface N4 may support registration of power receiver identifiers (RXIDs) and registration of certified power transmitter identifiers (TXIDs). This interface may allow certified OEMs/ODMs to pre-register their devices with the PCS. Registration may be via a registration form providing company and device details as required.

The UCF API S 1 internal interface may provide a set of S/W API for specific OS that allows application layer for accessing power receiver information exposed via the RX-UCF API interface P2. For example, for Android, these may be, inter alia, the APIs for Dalvik application accessing RXID information and power receiver registers or the like. The internal interface may provide for an API to Java like applications to accessing power receiver resources on the platform.

By the way of a non-limiting example, provided for illustrative purposes only, an interface may be described for the Android OS platform, other examples will occur to those skilled in the art. Regarding the Android interface, most of its application written in Java, the Java Virtual Machine is not used, rather another API, the Dalvik API, is used. Similar APIs may be defined for other leading OS in the consumer electronics space.

The API may allow UCF applications development that is abstracted from the specific hardware implementation.

With regard to TGW-PCS API, interface Nl may enable communication between the network management server and satellite elements such as wireless power outlets, communication modules, gateway modules and the like. The TGW-PCS API interface Nl may use an application programming interface (API) for example based on JavaScript Object Notation (JSON), Extensible Markup Language (XML) or the like. Accordingly the network management server may remotely manage the satellite elements.

The TGW-PCS API interface Nl or network messaging protocol may include various messages used for network management such as messages providing tools for maintaining the health, configuration, and control of a Power Module (PM) or wireless power outlet; messages for health and configuration of a Communication Module (CM); or access authorization messages for a new network element such as a power transmitter to join the wireless power transfer network.

Network messages may include a version number uniquely identifying the message format. This may enable a network management to be backward compatible and able to communicate with satellite elements such as power outlets using multiple versions of the communication protocol.

Messages may be further labeled by time stamps and a sequential message identification code (message ID) such that received messages may be validated. For example, a message timestamp may be reported as UTC time zone such that messages sent to the network server may be filtered by time. Accordingly, recent messages may be processed whereas old messages and messages with future time stamps may be ignored.

According to another validation method, the timestamp and message ID may be compared as a check that the messages are sent in sequential order. For example, if a message with a timestamp older than a previous message is sent for a transmitter, the message is ignored. Thus if message n with timestamp of 4:30:50 is received after message n+1 with the earlier timestamp of 4:30: 10, message n is ignored, similarly if message n+1 with timestamp of 4:29: 10 is received after message n with timestamp of 4:29:40, message n+1 is ignored.

Examples of various communication message types which may be used as appropriate include the following:

Status Report Messages which may be sent to a management server by a wireless power outlet periodically, upon request or ad hoc to report the wireless power outlet's charging status, the ID of a coupled power receiver, and operational errors. Extended Status Report Messages may be sent to a management server by a wireless power outlet in response to a request from the management server network to provide hardware-dependent diagnostic information.

Status Response Messages which may be sent from a management server to the wireless power outlet in response to a Status Report Message or Extended Status Report Message to provide control commands to instruct the power outlet to execute certain actions.

Configuration Report Messages which may be sent to a management server by a wireless power outlet periodically or when instructed to do so in a Response Message. The Configuration Report Message may provide information to the network manager regarding hardware and software of the power outlet.

Configuration Response Messages which may be sent from a management server to the wireless power outlet in response to a Configuration Report Message to provide configuration commands to instruct the power outlet to execute certain actions pertaining to configuration such as software updates and the like.

Health Status Report Messages which may be sent to a management server by a communication module periodically, when instructed to do so, or ad hoc to provide health status to the network management server.

Health Status Response Messages which may be sent from a management server to a communication module in response to a Health Status Report Message and provide control commands to instruct the communication module to execute certain actions.

Gateway Configuration Report Messages which may be sent to a management server by a communication module periodically, when instructed to do so, or ad hoc. The Configuration Report Message may provide information to a network manager regarding hardware and software of the communication module.

Gateway Configuration Response Messages which may be sent from a management server to the communication module in response to a Gateway Configuration Report Message to provide configuration commands to instruct the wireless power outlet to execute certain actions pertaining to configuration such as firmware updates, software updates, clearing cache, rebooting, archiving logs, setting defaults such as log sizes and the like.

Join Request Messages which may be sent to a management server by a communication module to provide details of a candidate wireless power outlet to be added to the network.

Join Request Response Messages which may be sent from a management server to a communication module in response to Join Request Messages to authorize the addition of the candidate wireless power outlet to the network or to reject the candidate power outlet.

System Architecture - Venue System Deployment:

System architecture and venue deployment may vary according to technology, location and various other parameters, providing different internal wireless power outlets layout. A venue wireless power outlet may use different power transfer protocols such as Power Matters Alliance (PMA), Alliance for Wireless Power (A4WP), Qi of Wireless Power Consortium (WPC), a Beam Forming protocol (multiple input, multiple output, MIMO), a third party associated power-transfer protocol and the like.

In such network distribution, the communication channel may be mediated by wireless access points, cellular networks, wired networks or the like that may provide an internet protocol (IP) connection to at least one of the electrical mobile devices or the wireless power outlet. It is further noted that optionally, the communication channel to the wireless power outlet may be mediated indirectly via the electrical mobile device and the close communication module. Similarly, the communication channel to the electrical mobile device may be mediated indirectly via the wireless power outlet.

Reference is now made to Fig. 3, representing schematic system architecture, which is generally indicated at 300A, for providing wireless power transfer services to electrical mobile devices in a possible servicing venue deployment.

It is noted that an electrical mobile device may be operable for powering according to its power transfer protocol that needs to be compatible with the specific technology of the targeted wireless power transmitter. A wireless power outlet is operable to transfer power to an electrical mobile device, if both are configured to communicate supporting resonant technology, for example.

Further, various power transfer protocols are in common use, such as Power Matters Alliance (PMA), Alliance for Wireless Power (A4WP), Qi of Wireless Power Consortium (WPC), Beam Forming protocol (multiple input, multiple output, MIMO), a proprietary third party power transfer technology and the like.

The wireless power outlet system architecture 300A comprises a set of wireless power transfer venues 311A-G, each venue may be associated with at least one wireless gateway 301A-G, depending on venue layout arrangement. Each wireless power modem may be in communication with a centrally managed control server 330 via a communication network 320. Furthermore, the centrally managed control server 330 may be configured to communicate with electrical mobile devices (enabling user functions) according to the UCF-PCS API interface N2 as described in Fig. 2 and further in the section of "Mobile Device - Power Software Application".

As appropriate, each wireless power outlet may be associated with and identification code, a TxID (Transmitter ID). Accordingly, the electric mobile device, may be identified by a device identification code (UDID), International Mobile Equipment Identity (IMEI), an Application code associated with the power software application and the like.

Reference is now made to Fig. 4, representing another schematic system architecture presentation, which is generally indicated at 400, for providing power wirelessly to electrical mobile devices. The system distribution comprises a set of venues 413A, 413B, each associated with at least one venue gateway 403A, 403B for controlling wireless power transfer from wireless power outlets of the venue. The system may be controlled and managed by a centrally managed control server 430 over a communication network 420.

The venue 413 A is shown in an expanded manner and includes a venue gateway 403A, a set of wireless power outlets 422, 424, 426 operable under PMA associated power transfer protocol, for example, powering electrical mobile devices 432, 434 and 436. The various wireless power outlets 422, 424, 426 may be accessible and controlled via the venue gateway 403A using an interface (see Fig. 2) providing transparent access to each outlet. Additionally, the centrally managed control server may expose an application programming interface (API) according to the interface system as described in Fig. 2, enabling to develop a management application presented in a screen display 442, as shown hereinafter in Fig. 4A.

It is particularly noted that the set of wireless power outlets of a venue may be fully configured under a specific power transfer protocol, such as PMA. Additionally or alternatively the set of wireless power outlets of a venue may use a mixture of associated power transfer protocols.

Reference is now made to Fig. 4A, presenting a screen display, which is generally indicated at 400A, for providing power management functionality, according to the currently disclosed subject matter.

It is noted that the management system of non-compliant (non-PMA) electrical mobile devices provides functionality of recording network based charging sessions and further provides wireless charging spot (CS) management capabilities.

The management screen display 400A provides management functionality for a non-compliant device including basic policy management (using button 452) allowing to change current policy accordingly, statistics information / usage (using button 454), interaction with user users (using send message button 456) and turning on/off the session ( using button 458). Additionally, the button 451 allows retrieving location based information and the button 453 allows retrieving user based information.

Reference is now made to the flowchart of Fig. 4B, representing selected actions of a possible method, which is generally indicated at 400B, to enable wireless power transfer in the system architecture for non-compliant electrical mobile devices.

The method 400B may include enabling a communication device - step 462, by getting a wireless charging enabled device or associating a powering ring with the device; activating the enabled communication device - step 464, by downloading of a power transfer software application onto the communication device to activate the device on a power transfer network; dropping the communication device (enabled and activated) on a charging spot at a servicing venue to start charging - step 466, where the charging spot is operable for magnetic induction to transfer power to the communication device via an associated wireless power receiver. It is noted that the wireless power transfer session may be reported by the charging spot to a centrally managed control server to allow the management system via the venue gateway to control the power provisioning phase - step 468 and to allow various management and control functions such as updating session policy, changing policy, charging duration management, billing, user management and the like.

It is further noted that such power transfer software may optionally be obtained from an online source such as the Google App Store for Android operating system application or Apple App Store for an Apple iOS operating system application or the like.

PMA Network and non-PMA devices:

The Power Matters Alliance (PMA) architecture of the network is policy based, allowing wireless power transfer only on certain terms requiring identification of the wireless power receiver associated with the electrical mobile device. PMA wireless power receivers (Rx) transmit their ID (RxID) to the wireless power transmitter (Tx) using the inductive in-band protocol. As appropriate, the transmitter Tx may further send its ID (TxID) together with the RxID to the centrally managed control server via the communication network to authorize wireless power transfer (as described in Fig. 5A hereinafter). Existing legacy phones activated for wireless charging do not have PMA RXID, thus the PMA network may not be accessible for these devices.

Alongside other networks, the current disclosure may provide provides a technical solution, enabling such legacy devices by using a wireless power software application to allow wireless power transfer to such devices via the PMA power network or other power network. Non-PMA, or other non-compliant, electrical mobile devices may not support the RxID in-band transmission, thus a different method is required authorize, control and manage wireless power transfer to such devices. The current invention uses out-of-band communication between the power transmitter Tx and the wireless power software application in form of a ultrasonic bidirectional communication coupled with the software application, and further communicating with the centrally managed control server to allow power provisioning to the non-compliant devices via a wireless power outlet, as described in Fig. 5B hereinafter.

Reference is now made to the flowchart of Fig. 5A, representing selected actions of a possible method, which is generally indicated at 500A, for a policy based activation sequence using PMA power transfer protocol in a PMA power network, for example.

It is noted that the activation sequence as described hereinafter is associated with the existing PMA power transfer protocol and is brought here to illustrate the novelty of the presented subject matter of the current disclosure associated the system architecture for non-compliant electrical mobile devices.

The method 500A, may include placing the electric mobile device on the charging spot surface - step 520A; executing the power provisioning software application - step 522A; sending, by the wireless power outlet, data pertaining to the carrier, the device and location to the centrally managed control server - step 524A; receiving the data, by the centrally managed control server - step 526A.

Accordingly, transmitting, by the electrical mobile device, the RxID as an in-band communication - step 528A; and receiving the RxID by the charging spot - step 530A;

The activation sequence further continues by transmitting the TxID, RxID, location and timestamp to the centrally managed control server - step 532A; and receiving said values by the server - step 534A; thereafter approving wireless power transfer according to currently imposed policy - step 536A and transmitting the message to the outlet; receiving the message - 538A, and if approved starting power transfer - 540A.

Reference is now made to the flowchart of Fig. 5B, representing selected actions of a possible method, which is generally indicated at 500B, an activation sequence using the power transfer protocol in a suitable power network for a for a non-compatible wireless power device.

The activation sequence as described hereinafter is associated with the non- compatible electrical mobile devices and the current disclosed subject matter enabling such device to join a power transfer network and become compatible with the network system architecture with no hardware changes.

The method 500B, may include placing the electric mobile device on the charging spot surface - step 520B; executing the power provisioning software application operable to use ultrasonic communication - step 522B; sending, by the power software application, an initiation signal - step 524B; receiving, by the wireless power outlet, the initiation signal transmitted - step 526B; transmitting, by the wireless power outlet, the associated TxID to the power software application - step 528B; receiving, by the power software application, the TxID - step 530B; and transmitting, by the wireless power outlet, the associated TxID of the outlet and data pertaining to location and the timestamp - step 532B; receiving the data, by the centrally managed control server - step 534B.

Accordingly, transmitting, by the power software application, the received TxID, device UDID, and data pertaining to the carrier and the device - step 538B; and receiving the data by the centrally managed control server - step 540B; then, pending processor analysis, approving the transmitter Tx to provide wireless power to the device identified by its UDID - step 542B ; receiving, by the wireless power outlet, the approval message - step 544B; thereafter, providing power to the electric mobile device - step 546B.

Reference is now made to flowchart of Fig. 5C, representing selected actions of a possible method, which is generally indicated at 500C, for an exemplified activation sequence for a non-compliant electrical mobile device, according to one aspect of the invention.

Existing legacy electrical mobile devices operable for wireless charging may not have associated receiver identifier (RXID). It is noted that the method 500C represent one possible technical solution and provides the legacy electrical mobile devices a conditional access in public places by coupling a non-compliant electronic device with a power transfer network. It is further noted that the flow of actions, as described hereinafter, are presented by the way of a non-limiting example, provided for illustrative purposes only.

The venue wireless power outlet, may be configured to be controlled by a networked control server. The outlet may use the sound speaker of the outlet to communicate the device identifier TXID (the MAC ID of the outlet, for example) to the electrical mobile device by ultrasonic message (18 KHz). The power software application associated with the mobile device may receive the TXID using mobile device's internal microphone. The software application may be configured to further communicate the mobile device/application ID (may be IMEI, UDID, other) and the TXID to the networked control server to enable control and management of the wireless power transfer.

It is specifically noted that the suggested technical solution does not require any special hardware.

Accordingly, the method 500C, may include placing the electric mobile device on the wireless power outlet surface - step 520C; engaging with the wireless power outlet by executing the power provisioning software application operable to use ultrasonic communication - step 522C; starting the wireless power transfer immediately - step 524C; and receiving wireless power by the electrical mobile device - step 526C; as appropriate, changing the electrical device microphone to listen mode, for a short period of time Tl (527), say, 30 seconds - step 528C, by the wireless power software application; and on the wireless power outlet side, waiting, after power transfer started, for a setup time completion T2 (529) as may be associated with the wireless power software application, say 5 seconds, or so - step 530C; transmitting the outlet TXID in a sound file (".wav" format or the like, for example), using ultrasonic communication at frequency of 18 KHz - step 532C; and upon receiving of the TXID on the electric mobile device side (by the software application), sending the received TXID coupled with the application ID (AppID, UDID, IMEI or other), device location and timestamp of the transmission - step 534C; and receiving the transmitted message - step 536C, at the centrally managed control server.

The Mobile Device - the Power Software Application:

The electrical mobile device software application may provide several sub-module components covering various possible functionalities, such as provisioning, billing, advertising, communication and the like. Optionally, the software application may allow modular functionality, to provide interfaces to additional features. The wireless power outlet may include an identification module to allow authorized usage, a near communication or the like. Optionally, the wireless power outlet includes a wireless LAN/WAN transmission unit module (as described hereinabove, in the communication module section).

The electrical mobile device may be operable to execute a provisioning software for paid charging, enabling the monitoring and controlling of power transfer. Such provisioning software may be an application that is preinstalled or accessed via a computer network such as by downloading from 'apps store' or operating as a web-based application. Further, the operation of the electrical mobile device, in relation to the wireless power transfer system described herein, may be controlled by software embedded within the OS of the device, the application programming interface (API) of the device OS, or firmware. The provisioning software may be distributed among a combination of: software embedded within the OS; the application programming interface (API) of the device OS, firmware, a pre-installed or downloaded application; and/or a web-based application. For example, the interaction of the device user with the charging system may be mediated with a preinstalled or downloaded application, while the interaction of the device with the other components of the wireless power transfer system such as the wireless power outlet and the server may be mediated through OS-embedded software.

The provisioning software may run on an electrical mobile device having a user interface. Alternatively, the device may not have a user interface.

The provisioning software may be automatically launched when power transfer is initiated on the electrical mobile device. Alternatively the user may launch the provisioning software, and then allow the power transfer of the device to commence.

The provisioning software application or the web-based application may further comprise additional functionalities to allow for more traffic, improve user satisfaction, provide brand exposure, and add direct revenues or the like. The Application may use features such as low battery notifications, locating a power transfer spot, directions to the power transfer spot, associated power transfer related or mobile device accessories for purchase. Additionally or alternatively, the application may provide power transfer history in general, optionally per location, receiving adverts based upon location, user identification, battery status, rate of power transfer and the like. Optionally, the pushed advertising may be coupled with promotional codes to facilities within venue area.

Optionally, the electrical mobile device software application may allow to promotion through social networks to get discounts on 'Like', share location with friends and inviting them to join.

Optionally, the electrical mobile device software application may allow ranking the power transfer experience.

Optionally, the electrical mobile device software application may allow providing skins or themes for a desired configuration of look and feel.

Reference is now made to the flowchart of Fig. 6A, representing selected actions of a possible method, which is generally indicated at 600A, for installing and initializing a power transfer software application on an electrical mobile device.

The method 600A may include downloading of a power transfer software application onto the electrical mobile device - step 602A. The power transfer software may be operable to enable the electrical mobile device to communicate with a remote wireless power transfer centrally managed control server. Such power transfer software may optionally be obtained from an online source such as the Google App Store for Android operating system application or Apple App Store for an Apple iOS operating system application or the like.

The power transfer software may be installed on the electrical mobile device - step 604A. Optionally, the initial settings of the software application are configured - step 606A. It is particularly noted that the device may be configured to allow activation via the power transfer software application - step 608A. Where appropriate a notification may be received from the centrally managed control server prompting a user to bring the electrical mobile device within range of a wireless power outlet - step 610A. For example, a wireless power receiver may be connected to the device and the device may be positioned adjacent to the wireless power outlet or the c device may be brought into the vicinity of a loosely coupled resonant wireless power outlet transmitter. Reference is now made to flowchart of Fig. 6B, representing further possible actions of a method, which is generally indicated at 600B, for enabling an electrical mobile device to initiate activation of a wireless power outlet to start charging.

The method may include receiving power transfer software application configuration settings - step 602B, optionally from a centrally managed control server. The received settings may be stored in memory of the electrical mobile device or in an associated repository - step 604B. It is noted that the software application may be enabled to access various device services, such as location based services and the like, of the electrical mobile device - step 606B. Accordingly, the software application may prompt the user to provide such access in response to receiving an enabling request via the software application popup or upon starting of power transfer. The electrical mobile device may then be brought within range of the charging spot - step 608B to enable power transfer; and initiating an activation request by the software application to allow power transfer - step 61 OB.

Reference is now made to flowchart of Fig. 7, representing a user experience method, which is generally indicated at 700, for providing wireless power transfer to an electrical mobile device, initiated by the power transfer software application.

The method may include requesting power transfer by a user - step 710; checking if the user is a new user - step 712; then getting the wireless power software application according to the type of the electrical mobile device - step 714; followed by registering to the powering services via the downloaded software application - step 716. Otherwise, if the user is an existing user, then starting the software application - step 718; placing the electrical mobile device onto the charging spot - step 720, to initiate handshaking between the device itself (via the power software application). Optionally, showing the authorization process for power transfer by the software application. Thereafter, upon approving, powering the electrical mobile device.

Technical and scientific terms used herein should have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosure pertains. Nevertheless, it is expected that during the life of a patent maturing from this application many relevant systems and methods will be developed. Accordingly, the scope of the terms such as computing unit, network, display, memory, server and the like are intended to include all such new technologies a priori.

As used herein the term "about" refers to at least ± 10 %.

The terms "comprises", "comprising", "includes", "including", "having" and their conjugates mean "including but not limited to" and indicate that the components listed are included, but not generally to the exclusion of other components. Such terms encompass the terms "consisting of" and "consisting essentially of".

The phrase "consisting essentially of" means that the composition or method may include additional ingredients and/or steps, but only if the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the claimed composition or method.

As used herein, the singular form "a", "an" and "the" may include plural references unless the context clearly dictates otherwise. For example, the term "a compound" or "at least one compound" may include a plurality of compounds, including mixtures thereof.

The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or to exclude the incorporation of features from other embodiments.

The word "optionally" is used herein to mean "is provided in some embodiments and not provided in other embodiments". Any particular embodiment of the disclosure may include a plurality of "optional" features unless such features conflict.

Whenever a numerical range is indicated herein, it is meant to include any cited numeral (fractional or integral) within the indicated range. The phrases "ranging/ranges between" a first indicate number and a second indicate number and "ranging/ranges from" a first indicate number "to" a second indicate number are used herein interchangeably and are meant to include the first and second indicated numbers and all the fractional and integral numerals therebetween. It should be understood, therefore, that the description in range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the disclosure. Accordingly, the description of a range should be considered to have specifically disclosed all the possible sub-ranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed sub-ranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 3, 4, 5, and 6 as well as non- integral intermediate values. This applies regardless of the breadth of the range.

It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the disclosure, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination or as suitable in any other described embodiment of the disclosure. Certain features described in the context of various embodiments are not to be considered essential features of those embodiments, unless the embodiment is inoperative without those elements.

Although the invention has been described in conjunction with specific embodiments thereof, it is evident that other alternatives, modifications, variations and equivalents will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications, variations and equivalents that fall within the spirit of the invention and the broad scope of the appended claims.

Additionally, the various embodiments set forth hereinabove are described in terms of exemplary block diagrams, flow charts and other illustrations. As will be apparent to those of ordinary skill in the art, the illustrated embodiments and their various alternatives may be implemented without confinement to the illustrated examples. For example, a block diagram and the accompanying description should not be construed as mandating a particular architecture, layout or configuration.

The presence of broadening words and phrases such as "one or more," "at least," "but not limited to" or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term "module" does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations. Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a computer-readable medium such as a storage medium. Processors may perform the necessary tasks.

All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present disclosure. To the extent that section headings are used, they should not be construed as necessarily limiting.

The scope of the disclosed subject matter is defined by the appended claims and includes both combinations and sub combinations of the various features described hereinabove as well as variations and modifications thereof, which would occur to persons skilled in the art upon reading the foregoing description.

Claims

1. A system for controlling a wireless power transfer network, said system comprising: at least one electrical device comprising a wireless power receiver and executing a wireless power software application operable to control wireless power transfer to said at least one electrical device via said wireless power receiver; and

at least one wireless power outlet operable to transfer power to said at least one electrical device;

wherein:

said at least one electrical device is labeled with a device identifier and comprises an audio signal receiver;

said at least one wireless power outlet comprises a transducer configured to transmit at least one audio signal of a type receivable by said audio signal receiver associated with said at least one electrical device, said at least one audio signal communicating a wireless power outlet identification code; and

wherein said wireless power software application is operable to associate said at least one electrical device with said at least one wireless power outlet and control wireless power provisioning to said wireless power receiver.

2. The system of claim 1, wherein said audio signal receiver comprises a microphone and an audio speaker associated with said at least one electrical device.

3. The system of claim 1, wherein said transducer comprises an audio speaker and a microphone associated with said at least one wireless power outlet.

4. The system of claim 1 , wherein said at least one audio signal is at least one ultrasonic signal.

5. The system of claim 1, wherein said at least one audio signal comprises data pertaining to said wireless power outlet identification and data pertaining to said at least one electrical device.

6. The system of claim 1, wherein said device identifier is selected from a group consisting of: a device identification code, an international mobile equipment identity (IMEI), an application code associated with the power software application and combinations thereof.

7. A method for a management control server to control wireless power transfer from at least one wireless power outlet to a wireless power receiver associated with an electrical device, said electrical device executing a software wireless power application and being labeled with a device identifier, said at least one wireless power outlet being labeled with a wireless power outlet identification code, the method comprising:

receiving at least a first message from said at least one wireless power outlet communicating at least said wireless power outlet identification code and data pertaining to location of said at least one wireless power outlet;

receiving at least a second message from said electrical device communicating, via said software wireless power application, at least said device identifier, said wireless power outlet identification code and data pertaining to device location and a carrier of said electrical device;

comparing said wireless power outlet identification code associated with said at least a first message and said wireless power outlet identification code associated with said at least a second message; and

providing an approval response message to said at least one wireless power outlet only if said wireless power outlet identification code associated with said at least a first message matches said wireless power outlet identification code associated with said at least a second message.

8. A method for an electrical device configured to receive power transfer via a wireless power receiver conductively connected thereto, said electrical device labeled with a device identifier operable to activate wireless power transfer from a wireless power outlet labeled with a wireless power outlet identification code to said wireless power receiver, said method comprising:

executing a power transfer software application on said electrical device; accessing, by said power transfer software application, a configuration data of said electrical device;

sending, by said power transfer software application, at least a detection signal such that said wireless power outlet sends at least a first message communicating said wireless power outlet identification code to a control server and a second message communicating said wireless power outlet identification code to said electrical device via power transfer software application; and

sending, by said power transfer software application, at least a third message communicating at least said device identifier, said wireless power outlet identification code, data pertaining to device configuration and data pertaining to device carrier to said control server.

9. The method of claim 8, wherein said step of executing said power transfer software application comprises:

downloading said power transfer software application to said electrical device; installing said power transfer software application onto said electrical device; and

configuring said power transfer software application to communicate with said control server.

10. The method of claim 8, wherein said step of sending at least a third message comprises:

opening a microphone associated with said electrical device in listen mode; and

closing said microphone after waiting a pre-configured wait time.

11. The method of claim 8, wherein said wireless power receiver is selected from a group consisting of ring devices, dongles, cases, skins, back-covers, embedded devices, addons and wirelessly enabled batteries.

12. A method for a wireless power outlet configured and operable to communicate bi- directionally with an electrical mobile device via a power transfer software application and to provide power transfer to said electrical mobile device via a wireless power receiver, said wireless power outlet labeled with a wireless power outlet identification code and operable to receive an activation signal, said electrical mobile device labeled with a device identifier, said method comprising:

receiving at least one detection signal from said electrical mobile device via power transfer software application;

sending at least a first communication message communicating at least said wireless power outlet identification code to said electrical mobile device via power transfer software application;

sending at least a second communication message communicating at least said wireless power outlet identification code to at least one control server via a network communication interface;

receiving a power response message from said at least one control server; and providing wireless power transfer to said wireless power receiver if said power response authorizes powering.

13. The method of claim 12, wherein said wait time is associated with the setup time required by said power transfer software application.

14. The method of claim 12, wherein said at least second communication message further comprises data pertaining to at least one of a location and a timestamp.

15. The method of claim 12, wherein said device identifier is selected from a group consisting of: a device identification code (UDID), an international mobile equipment identity (IMEI), an application code associated with the power software application.

16. The method of claim 12, wherein said network communication interface is selected from a group consisting of: a proprietary application programming interface (API), a Zigbee interface, a WiFi interface and combinations thereof.

17. A system for controlling a wireless power transfer network, said system comprising: at least one electrical device comprising a wireless power receiver and executing a wireless power software application; at least one wireless power outlet operable to transfer power to said at least one electrical device; and

at least one control server in communication with said at least one electrical device and said wireless power outlet and operable to control wireless power transfer to said at least one electrical device via said wireless power receiver,

wherein:

wherein said at least one control server is operable to:

receive a first communication message from said at least one electrical device via said wireless power software application and a second communication message from said at least one wireless power outlet, said first communication and said second communication including said wireless power outlet identification code such that said at least one control server is operable to associate said at least one electrical device with said at least one wireless power outlet and control wireless power provisioning to said wireless power receiver.

18. The system of claim 17, wherein said first communication message further comprises data selected from a group consisting of: a device identifier, data pertaining to a carrier, data pertaining to said at least one electrical device and combinations thereof.

19. The system of claim 17, wherein said second communication message further comprises data selected from a group consisting of: data pertaining to a location, a timestamp and combinations thereof.