WO2015181817A1

WO2015181817A1 - System and methods for locating nearby venues for wireless power transfer

Info

Publication number: WO2015181817A1
Application number: PCT/IL2015/050542
Authority: WO
Inventors: Eduardo Alperin; Ilya GLUZMAN; Oola Greenwald; Ian Podkamien; Elieser Mach
Original assignee: Powermat Technologies Ltd.
Priority date: 2014-05-26
Filing date: 2015-05-21
Publication date: 2015-12-03

Abstract

The disclosure relates to system and methods for managing a wireless power transfer network for power transfer to electrical devices. In particular, the disclosure relates to determining a nearby venue servicing location providing wireless power transfer according to electrical devices according the charging technology of device. The wireless power transfer network comprises a distribution of venues providing wireless power transfer services and manageable via a central management server connectable to a central management console and in communication with the various power transfer outlets in the various venues, via a communication network. The management server is operable to communicate with the various system components using standardized system API. The system is accessible by electrical devices executing a provisioning system based upon the system's API to allow user desired functionality. In particular, a needed functionality is locating a nearby venue supporting the power transfer technology of the electrical device.

Description

SYSTEM AND METHODS FOR LOCATING NEARBY VENUES FOR WIRELESS POWER TRANSFER

FIELD OF THE INVENTION

The disclosure herein relates to systems and methods for managing a network of devices configured to transmit power wirelessly for charging electrical devices. In particular the invention relates to determining a nearby venue servicing location providing wireless power transfer according to the desired technology.

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.

There is a need for systems that conveniently provide the opportunity to transfer power for charging the electrical 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. Further, there is a need for such systems to enable easy tracking of power transfer locations in public spaces as soon as the need arises, that is, when the battery level runs low, while power transfer locations around current location may answer user expectations.

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 - resonant, non-resonant, magnetic beam, inductive power transfer and the like, not necessary compatible to a specific electrical device. The diversification of technologies may prevent providing the required service of power transfer to electrical devices which do not support or are not compatible with the technology of the wireless power outlet. An electrical device may be configured with a specific technology, not necessarily compatible to the technology of a specific wireless power outlet at a venue. Existing application layers may enable finding nearby venue locations, but do not generally provide the associated data with respect to technology.

The invention described hereinafter addresses the above-described needs.

The use of a wireless non-contact system for the purposes of automatic identification or tracking of items is an increasingly important and popular functionality.

Inductive power coupling allows energy to be transferred from a power supply to an electric load without a wired connection therebetween. An oscillating electric potential is applied across a primary inductor. This sets up an oscillating magnetic field in the vicinity of the primary inductor. The oscillating magnetic field may induce a secondary oscillating electrical potential in a secondary inductor placed close to the primary inductor. In this way, electrical energy may be transmitted from the primary inductor to the secondary inductor by electromagnetic induction without a conductive connection between the inductors.

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.

Under some condition, the efficiency of power transfer can be increased by matching the resonant frequencies of the primary and secondary inductors.

SUMMARY OF THE INVENTION

It is according to one aspect of the disclosure to teach a method for managing a wireless power transfer network comprising at least one management server in communication with at least one electrical device, the method comprising at least one management processor executing instructions to perform operations comprising: receiving at least one servicing location request message from the at least one electrical device; processing the at least one location request message; and sending the at least one servicing location response message to at least one electrical device; wherein the at least one servicing location request message communicates data indicating a current location and protocol compatibility of said electrical device and said at least one servicing location response message communicates data indicating at least one nearby venue providing wireless power using a protocol compatible with said electrical device.

As appropriate, the at least one electrical device may communicate with the management server via a communication module.

Variously, the technology is associated with the type of wireless power charging technology required by the at least one electrical device determined by a value selected from a group consisting of: non-resonance power transfer, resonance power transfer, MIMO power transfer, inductive power transfer and the like as well as combinations thereof.

The method wherein referencing at least one servicing location request message comprises data pertaining to a license key provided by the management server, the license key authorizing the at least one location request message.

The method wherein referencing at least one servicing location request message comprises data pertaining to a version format of the at least one location request message.

The method wherein referencing the at least one servicing location request message comprises data pertaining to the current location of the at least one electrical device.

As appropriate, the current location may comprise a latitude value and a longitude value.

As appropriate, the servicing location request message may comprise data pertaining to a radius determining the maximum distance of searching from the current location.

As appropriate, the servicing location request message may comprise data pertaining to a maximum number determining the size of a nearest venues list to be sent in the at least one response message.

As appropriate, the at least one servicing location request message may comprise data pertaining to a current time timestamp, the current time timestamp is presented in a standard world time format (UTC). As appropriate, the at least one servicing location request message may comprise data pertaining to a list of customers to allow filtering of the result list.

As appropriate, the at least one servicing location response message may comprise data pertaining to a version format of the at least one servicing location response message.

As appropriate, the at least one servicing location response message may comprise data pertaining to a list of venue locations filtered according to the at least one location request message.

Variously, the list of venue locations may comprise an array of data elements selected from a group consisting of: a store name, a store location, a distance from said current location, a customer store chain name and combinations thereof.

Another aspect of the disclosure is to teach a method for managing a wireless power transfer network comprising at least one management server in communication with at least one electrical device, the method comprising at least one electrical device processor executing instructions to perform operations comprising sending at least one servicing location request message to the at least one management server; receiving at least one servicing location response message from the at least one management server; and processing the at least one location response message; wherein the at least one servicing location request message communicates data indicating a current location and protocol compatibility of said electrical device and said at least one servicing location response message communicates data indicating at least one nearby venue providing wireless power using a protocol compatible with said electrical device.

Optionally, the at least one electrical device communicates with the management server via a communication module.

Variously, the technology is associated with the type of charging technology required by the at least one electrical device determined by a value selected from a group consisting of: non-resonance power transfer, resonance power transfer, MIMO power transfer, inductive power transfer and the like as well as combinations thereof. As appropriate, the at least one servicing location request message may comprise data pertaining to a license key provided by said management server, the license key authorizing the at least one location request message.

As appropriate, the at least one servicing location request message may comprise data pertaining to a version format of the at least one location request message.

As appropriate, the at least one servicing location request message may comprise data pertaining to the current location of the at least one electrical device.

As appropriate, the at least one servicing location request message may comprise data pertaining to a current time timestamp, the current time timestamp is presented in a standard world time format (UTC).

As appropriate, the at least one servicing location request message comprises data pertaining to a list of customers to allow filtering of the result list.

Variously, the list of venue locations comprises an array of data elements selected from a group consisting of: a store name, a store location, a distance from said current location, a customer store chain name and combinations thereof. According to another aspect of the presently disclosed subject matter, there is provided a system for inductive transfer of electric power to an inductive receiver, the system comprising an array of inductive power outlets and a controller, the controller configured to selectively operate one or more of the inductive power outlets to operate in one of two or more modes of providing power.

One of the modes may be a multiple input, multiple output mode, wherein two or more of the inductive power outlets cooperate to form a beam toward the receiver.

One of the modes may be an inductive mode.

One of the modes may be a resonance mode.

The controller may be configured to make the selection based on a coupling factor between at least one of the inductive power outlets and the receiver.

The controller may be configured to reevaluate the coupling factor after a predetermined time interval has elapsed, and select a mode for continued power transfer accordingly.

The controller may be configured to make the selection based on the type of receiver.

According to another aspect of the presently disclosed subject matter, there is provided a method for providing power wirelessly to a receiver, the method comprising:

(a) providing a system comprising an array of inductive power outlets and a controller configured to operate the outlets;

(b) detecting a receiver by the system;

(c) calculating a coupling factor between at least one of the inductive power outlets and the receiver;

(d) selecting, based on the coupling factor, a mode of power transfer from the inductive power outlet to the receiver, from two or more modes of providing power; and

(e) transferring power from the inductive power outlet to the receiver according to the mode selected. The method may further comprise reevaluating, after the transferring, the coupling factor after a predetermined interval, and repeating steps (d) and (e).

The method may further comprise determining whether power is required by the receiver, and, if not, terminating the method.

One of the modes may be an inductive mode.

One of the modes may be a resonance mode.

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. 1 is a schematic illustration of a system according to the presently disclosed subject matter;

Fig. 2 illustrates an inductive power outlets of the system illustrated in Fig. 1 ;

Fig. 3 illustrates a method for providing power wirelessly to a receiver;

Fig. 4 is a block diagram showing the main elements of an inductive power transfer system with a feedback signal path according to embodiments of the present invention; Fig. 5 is a block diagram showing the main elements of an inductive power transfer system with an inductive feedback channel according to still another embodiment of the present power transfer system invention;

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

Fig. 7 is a system diagram schematically representing selected components of a possible servicing venue deployment;

Fig. 8 is a system diagram schematically representing selected components of a servicing venue deployment associated with various power transfer technologies; and

Fig. 9 is a flowchart representing selected actions of a possible method for locating nearby servicing venues, via communications with the management server, to provide wireless power transfer to an electrical device according to a desired technology.

DETAILED DESCRIPTION

Aspects of the present invention relate to providing system and methods for managing a network of devices configured to transmit power wirelessly for charging electrical devices. In particular, the present disclosure relates to locating a servicing venue for wireless power transfer according to a desired technology.

Wireless power transfer systems technologies may use various configurations of coils and 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 device.

As used herein, inductive power transfer technology is associated with power is transferred 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.

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 allows 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 inject 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, magnetic beam technology is associated with wireless power transfer using multi coil array to form the "Magnetic Beam" ("Phase Array" or MIMO, magnetic multiple-input multiple-output) and stir it towards the power receiver which may change position during power transmission. The Magnetic beam technology aims at increase of wireless power range.

Accordingly, a user equipped with a non-resonant based device, for example, may walk into a venue providing PMA wireless power transfer services. Yet, though the transmitter and the receiver are PMA certified, the user may not be able to receive the power transfer service if the transmitters of the venue support resonant technology. Furthermore, the same servicing conflict may result when searching an appropriate servicing venue via an application using an appropriate Application Programming Interface (API), as described in Fig. 3. The existing API, is not supporting technology differences.

Possible deployment of wireless power transfer venues is described hereinafter in Fig. 4 and Fig. 5, elaborating on the user experience and the associated technical issues that need a solution. The technical solution details are described hereinafter in the flowchart of Fig. 6, illustrating the flow of interactions of a user via a centrally managed software application, using enhancement of the PMA API.

Power Management:

The power management system is a centrally managed system operable to execute on at least one management server and further communicate with a management console locally or via a communication network. The management server is operable to execute various power management software processes and applications, using various API's, as described in Fig. 3. The power management software provides 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 with the ability to manage the wireless power outlets (hotspots) that are installed therein. 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.

The wireless power network management, from the user perspective, may provide a set of provisioning functionalities such as the ability to search and discover location of a venue providing wireless power transfer service. In particular, the management software may enable to identify the power outlet technology and further its availability and uptime.

Furthermore, 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.

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.

The power management software may include operational aspects of providing power transfer or control billing aspect associated with an electrical 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.

Management Server Functionality:

The management server may be capable of integration with external servers or services. Some integration may be for data enhancements and external validation of rights for users or devices, and others may be for managing a certain functional aspect of the system, such as: network management and monitoring, maintenance of remote units, policy enforcement, user management, device management, billing, advertising, socializing and the like.

Various functionalities may be available through the power management software, and may also be available to third-party applications through 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 the providing of power transfer based on a predefined "offline policy". System Architecture:

As used herein, the term "management server" refers to a server configured to manage multiple inductive power outlets configured to provide power transfer to electrical mobile electrical 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, the mobile electrical 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 devices without a battery.

The wireless power outlet point may be referred to herein as, variously, a 'PAP", a 'hotspot" or a 'charger".

Some embodiments representing the current system architecture may use Client/Server technology, but are not limited and may use other network architectures such as a peer-to-peer architecture, where each node has equivalent responsibilities.

In software engineering, Client/Server architecture refers to a network architecture where each computer, device or process on the network is either a client or a server. Such network architecture are applicable to enterprise applications, and generally the presentation, application processing, and data management functions are logically separated and operable on various nodes (tiers) of the system.

The client software (may be referred to as the user agent) allows the interaction between the client machine (a dashboard terminal, a workstation, a dedicated wireless power outlet or an electrical mobile device) and the application layer. When web-based applications are used, the client node (usually a browser) renders the user interface, which may be generated by a presentation layer on the client side or the server side by interpreting the HTML, Java applets, or ActiveX controls, for example. The presentation layer is software allowing the visualization functions for the application (on a dashboard terminal, electrical mobile device) and may comprise of static objects such as images, form fields receiving retrieved data from the database layer, or may use dynamically generated objects to allow populating the data appropriately, and displaying the result of the analysis or computation produced by the application layer. The output of the presentation layer may be submitted to a dashboard, and further formatted to be presented on a terminal dashboard, for example. On web-based applications, the presentation layer may be implemented by web servers.

The application layer provides the business logic of the distributed system of wireless power transfer network and the management software may be installed on a management server. The application layer may receive procedure invocations from the presentation layer, to which it returns the results of the application logic (computation or the analysis) performed on the management server. The application layer may further communicate with the database layer to store, update and retrieve data. The management database layer may store the application data, such as business logic and policies, third party business related information, user information, geographical locations, device IDs, power transfer duration and additional related information. The management database software may be installed on the management server or on a separate server (node). For any case, a database interface may be required in order to implement the business logic, allowing connecting to the database server(s) to retrieve, update and store data.

Communicating with the Management Server:

The management or control server may be in communication with the wireless power outlet, the electrical mobile device, or both. 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 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 device and the close communication module. Similarly, the communication channel to the electrical device may be mediated indirectly via the wireless power outlet. Description of the Embodiments:

It is noted that the systems and methods of the invention described herein may not be limited in its 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.

MIMO type power transfer systems:

As illustrated in Fig. 1, there is provided a system, which is generally indicated at 10A, for inductively providing electric power. The system comprises an array 12 of inductive power outlets 14, a power supply 16, and a controller 18.

As illustrated in Fig. 2, each of the inductive power outlets 14 comprises a primary coil 20 wired to the power supply 16 via a driver 22 which provides the electronics necessary to drive the primary coil. For this purpose, the driver 22 may comprise a switching unit providing a high frequency oscillating voltage supply. Each of the primary coils 20 comprises a conducting wire 24, optionally wound around a ferromagnetic core 26. In addition, each transmitter 14 comprises a capacitor 28 serially connected thereto. The controller 18 is configured to operate each of the inductive power outlets. Thus, the inductive power outlets 14 are configured to transmit power inductively to a compatible receiver (not illustrated), as is well-known in the art.

Examples of receivers, additional details and examples of suitable inductive power outlets, as well as methods of control thereof, are described in United States Patent Number 8,749,097, United States Patent Number 8,872,386, United States Patent Application Number 14/152,358 and United States Patent Application Number 14/273,280 the full contents of which are incorporated herein by reference.

The controller 18 is further configured to operate several of the inductive power outlets 14 in coordination such that their magnetic fields combine constructively at the receiver, i.e., they cooperate to create a "beam" theretoward. This type of power transfer is referred to herein as MIMO (multiple input, multiple output). The controller 18 is configured to spatially direct the beam according to the location of the receiver.

The power received by the receiver, i.e., the current induced in a coil thereof (i.e., a secondary coil), when several of the inductive power outlets 18 are transmitting power thereto, can be maximized by scaling the current flowing in each of the inductive power outlets 14 as given by the following:

∑Γ= ι ΐ™. Ι ²

where ¾ is a beamforming vector satisfying the relationship wherein β(Ι₅ is the current in primary coil 20 of the i^th transmitter 14 (where I_S is the total current of the array 12), m, (referred to as the magnetic channel between the i^h transmitter and the receiver) is given by:

where ω is the frequency of the AC current of the inductive power outlets, ZL is the impedance of the receiver, R_L is the resistance of the receiver, and , is the mutual inductance between the receiver and the i^th transmitter; m^* is the complex conjugate of The controller 18 accomplishes beamforming by calculating the above for each of the inductive power outlets 14, and controlling the operational parameters (e.g., the power and capacitance) of each one accordingly. The controller 18 is configured to have the beam track the receiver (i.e., change the parameters thereof such that power induced in the receiver is maximized as the receiver moves in space) by re-evaluating the mutual inductance ( ,) between the receiver and each of the inductive power outlets 14.

The controller 18 may be configured to follow a beamforming protocol comprising the steps of (a) magnetic channel estimation, (b) beamforming, and (c) automatic beam steering, as will be described below.

In the step of magnetic channel estimation, the controller 18 "learns" the magnetic channel between each of the inductive power outlets 14 and the receiver, thereby computing a beamforming vector. This is accomplished by measuring the load that the receiver puts on each of the inductive power outlets 14. To this end, a known voltage V is applied to the i^th transmitter 14, while the circuits connected to each of the other inductive power outlets are open. The current 7_Ϊ( flowing through the i^th transmitter 14 is measured, and the voltage V is divided thereby to obtain the total impedance of the i^h coil, i.e.,

This value can be used to compute the magnetic channel between the i^th transmitter 14 and the receiver as follows:

where ¾ is the intrinsic impedance of the i transmitter 14, and y, is equal to +1 if the value of M] is positive, and -1 otherwise.

In the step of beamforming, the magnetic channels determined in the magnetic channel estimation step are applied to each of the inductive power outlets 14, and the currents of each are set to satisfy 7_Ϊ( = thereby ensuring that the beam is directed at the receiver. In the step of automatic beam steering, the steps of magnetic channel estimation and beamforming are repeated at regular intervals, to ensure that the beam is properly directed. The more this takes place, the more accurate the beam direction will be. However, since the magnetic channel estimation includes cutting power to inductive power outlets 14, performing the step of automatic beam steering at overly small intervals may reduce the amount of power transferred to the receivers.

It will be appreciated in the in MIMO mode of operation, the controller 18 may determine (and direct the system 10A accordingly) that some of the inductive power outlets 14 should not transmit any power at all, i.e., they should be deactivated. In addition, during the course of power transfer, the controller 18 may determine (and direct the system 10A accordingly) that some of the inductive power outlets 14 which had not been transmitting power should be activated.

For example, a few of the inductive power outlets 14 which are located close to one another may be activated to form the beam. In a case wherein the system 10A serves a larger area, only those inductive power outlets 14 which are necessary to transmit power to the receiver are activated, with non-active inductive power outlets being activated as the receiver moves within the area. (It will be appreciated that herein the specification and claims, the term "area" may be construed as referring to a three-dimensional space, depending on the context.)

The theory behind the derivation of the above can be found in "Magnetic MIMO: How to Charge Your Phone in Your Pocket" by Jouya Jadidian & Dina Katabi, published in "Proceedings of the 20th annual International Conference on Mobile Computing and Networking", by the Association for Computing Machinery, Pages 495-506, the entire contents of which are incorporated herein by reference.

The controller 18 is configured to select the mode of wireless power provision of the system 10A. The selection may be, for example, based on a coupling factor k determined thereby. The coupling factor indicates how tightly coupled the inductive power outlets 14 and receiver are, and varies between 0 and 1, with the higher value indicating a tighter coupling (i.e., a value of 1 indicates that all power flux in the transmitter reaches the receiver). The value may be computed, and is affected by many factors, including, but not limited to, the distance between the transmitter 14 and the receiver, the relative angle therebetween, the geometry of the primary and secondary coils, etc. According to a non-limiting example, the coupling factor may be given by:

⁼ I where L_m is the mutual inductance of the transmitter and receiver, and L] and L₂ are the inductances of, respectively, the transmitter and the receiver.

For values of k in a high range, the controller 18 is configured to operate in an inductive mode, wherein the transfer of power from one or more of the inductive power outlets 14 to the receiver is performed using inductance. For values of k in a moderate range, the controller 18 is configured to operate in a resonance mode, wherein the transfer of power from one or more of the inductive power outlets 14 to the receiver is performed using resonance, values of k in a low range, the controller 18 is configured to operate in a MIMO mode, wherein the transfer of power from one or more of the inductive power outlets 14 to the receiver is performed using MIMO such as described above.

When determining which mode to operate in, the controller 18 may determine the coupling factor between each of the inductive power outlets 14 (or a subset thereof) and the receiver.

According to some examples, the high range may be between about 0.6 and 1, the moderate range may be between about 0.3 and about 0.6, and the low range may be between below about 0.3.

According to some modifications, for borderline cases (e.g., a small range of values of k near the extreme ends of each range; in the example given above, this may be between 0.295 and 0.305 and between 0.595 and 0.605), the controller may attempt two different types of power transfer to see which is more efficient or otherwise suitable. According to this modification of the example given above, the for values of k between 0.295 and 0.305, the controller 18 may briefly operate the system 10A to transfer power using MIMO and then briefly operate the system to transfer power using resonance, and compare the amount of power transferred according to each method. It may then select the method through which more power was transferred to continue power transfer when k remains within the "borderline" range.

The controller 18 may be further configured to re-evaluate the value of k, and reevaluate (i.e., change or continue) the method of power transfer accordingly, when a predefined interval of time has elapsed. The interval may be on the order of several seconds. The controller 18 may be further configured to alter the interval, for example extending it if the value of k has remained constant for a predefined amount of time.

Accordingly, the controller 18 may attempt to transfer power via MIMO. Simultaneously, it evaluates the coupling factor, and determines whether to continue transferring power using the MIMO mode, or to use one of the other modes to transfer power.

In addition, if the controller 18 determines that power should be transferred by a single transmitter 14, e.g., via induction or resonance, it may direct the system 10A to supply power for transfer only to the transmitter 14 with the highest coupling factor with the receiver.

The system 10A may be configured to detect the type of device of which the receiver constitutes a part. Thus, the controller 18 may be further or alternately configured to select the mode of wireless power provision of the system 10A based on the type of receiver, i.e., which type or type of power transfer is most suitable therefore.

It will be appreciated that although the controller 18 is described and illustrated herein the specification and claims as constituting an independent element of the system 10A, it may be integrated into one or more elements. For example, the functions thereof may be carried out by one or more of the inductive power outlets 14. For example, one of the inductive power outlets 14 may assume the functions of the controller 18, and serve as a "master" directing operation of the other inductive power outlets, which serve as "slaves".

As illustrated in Fig. 3, there is provided a method, which is generally designated at 100, for providing power wirelessly to a receiver, for example using the system 10A described above with reference to Figs. 1 and 2. It will be appreciated that references in the method 100 as described below which are described as being performed by the "system" may be carried out by any suitable element thereof.

In step 102, a system for providing power by induction, such as described above, is provided. The system defines an area in which a receiver can be subject to inductive power provision thereby.

In step 104, the system detects a receiver within the area.

In step 106, the system determines whether or not the receiver requires power be provided thereto. If not, the method may be terminated.

In step 108, the system calculates the coupling factor between inductive power outlets thereof and the receiver. The system may calculate the coupling factor between the receiver and all of the inductive power outlets, or for a subset thereof. For example, it may determine, based on past calculations of other inductive power outlets, that the inductive power outlet having the ideal coupling factor with the receiver has been identified. The calculation of the coupling factor may include providing power under the MIMO mode, as described above. In addition, the system may determine whether or not power is required to be provided, and, if not, terminate execution of the method.

In step 110, the system selects, based on the value of the coupling factor calculated in step 108, a mode of power transfer for continuing transfer of electric power, and which of the inductive power outlets are involved therewith. The modes may include inductive, resonance, and MIMO. The system may take the type of receiver into account, if such information is available.

In step 112, the system transfers power inductively to the receiver using the mode selected in step 110.

In step 114, the system, after a predetermined interval, reevaluates the need for providing power and the coupling factor, returning to step 106.

The method continues until terminated, e.g., as in step 106, or when the receiver is no longer detected by the system. Those skilled in the art to which this invention pertains will readily appreciate that numerous changes, variations and modifications can be made without departing from the scope of the invention mutatis mutandis.

Inductive power transfer systems:

Fig. 4 and Fig. 5 represent different possible embodiments of an inductive power transfer system.

Reference is now made to Fig. 4, illustrating schematically a block diagram of the main elements of an inductive power transfer system 100A 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.

In some embodiments, a voltage peak detector 140 is provided to detect large increases in the transmission voltage. As will be descried below the peak detector 140 may be used to detect irregularities such as the removal of the secondary unit 200, the introduction of power drains, short circuits or the like.

Reference to the block diagram of Fig. 5, showing another embodiment block diagram of the main elements of an inductive power transfer system 200A. 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 200 A 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 Si_n 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, typically at a voltage transmission frequency f_t which is higher than the resonant frequency fR 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 1124. The transmission circuit 1122 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 fjt of the system increases. The transmission circuit 1122 is configured to selectively connect the electrical element 1126 to the secondary coil 1320. As noted above, any decrease in either the inductance L or the capacitance C increases the resonant frequency of the system. 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 1124 includes a voltage peak detector 1128 configured to detect large increases in the transmission voltage. In systems where the voltage transmission frequency f_t is higher than the resonant frequency fR of the system, such large increases in transmission voltage may be caused by an increase in the resonant frequency fR 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_ln. 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:

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 is disclosed which may allow a wider deployment of wireless power provision for mainstream technology and possible standardization of a network architecture and associated APIs. Reference is now made to the system diagram of Fig. 6 showing a network architecture representation of a wireless power transfer system 300A with various application interfaces.

It is particularly noted that the network architecture representation 300A, 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 300A includes a first venue architecture 302A, a second venue architecture 302B connectable to a certified device manufacturer (PCDM) 306-1 and a wireless charging spot provider (WCSP) 308-1 through a cloud network service (PCS) 304-1. The first venue architecture 302A and the second venue architecture 302B may further include various network entities.

By way of illustration, in this particular embodiment, the first venue architecture 302A may include a wireless power receiver (Rx) 314A entity connectable to at least one wireless power transmitter (Tx) 316A entity in communication with at least one transmitter gateway (T-GW) 318A entity. The wireless power receiver 314A entity may further be connectable to a User Control Function (UCF) 312A entity. The second venue architecture 302A may include a wireless power receiver 314B, wireless power transmitters 316B, and a transmitter gateway (T-GW) 318B 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 300A 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.

Communication security may be provided by using secure communication channels such as an HTTPS connection. Furthermore, communication may include MAC address filtering using transmitter identification codes (TXID), receiver identification codes (RXID), gateway identification codes (GWID) and the like to control network access. Accordingly, TXIDs may be preregistered with the network management server and before the associated power outlet is authorized to join the network and communication is enabled. 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 the management server by a power outlet periodically, upon request or ad hoc to report a power outlet's charging status, the ID of a coupled power receiver, and operational errors.

Extended Status Report Messages may be sent to the management server by a 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 the management server to the 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 the management server by a 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 the management server to the 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 the 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 the management server to the communication module in response to a Health Status Report Message to provide control commands to instruct the communication module to execute certain actions.

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

Gateway Configuration Response Messages which may be sent from the management server to the communication module in response to a Gateway Configuration Report Message to provide configuration commands to instruct the 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 the management server by a communication module to provide details of a candidate power outlet to be added to the network.

Join Request Response Messages which may be sent from the management server to a communication module in response to Join Request Messages to authorize the addition of the candidate power outlet to the network or to reject the candidate power outlet. So as to better illustrate the communication protocol of the particular embodiment described herein, reference is now made to the flowcharts which show selected actions involved in the communication protocol.

API Examples:

Specifically, the UCF-PCS API interface N2 may be implemented using JavaScript Object Notation (JSON) over HTTPS link from UCF to PCS. The HTTPS session establishment may include mutual authentication to allow for validation of client identity.

The UCF-PCS API interface N2 may include the GET_NEARBY_LOCATIONS messages which may be sent to the management server in order to retrieve the closest venue locations to the provided position. In particular, the GET_NEARBY_LOCATIONS message may use a technology parameter to determine charging technology match of the electric device and the servicing venue inductive power outlets.

Additionally, various communication message types may be communicated between the UCF and the PCS as appropriate, may include the following:

GET_PACKAGES messages which may be sent to the cloud server in order to retrieve the list of packages (comprising daily passes) available for purchase. Such purchases may be enabled via online market places such as the Apple App store, Google Play and the like.

ADD_ALLOWANCES messages which may be sent to the cloud server once a package is purchased, whereby the client sends the purchase information including validation receipt and the service adds the purchased day passes.

PvEDEEM_GIFT_CARD messages which may be sent to the cloud server in order to send a gift-card ID so the server redeems the daily passes to the associated account.

GET_ALLOWANCES messages which may be sent to the cloud server in order to retrieve the number of daily passes for an associated account and the number of free daily minutes this account is entitled to receive. ADD_ACCOUNT messages which may be sent to the cloud server in order to create an unnamed account for a client, for example identified by a hardware related unique identifier.

REGISTER_ACCOUNT messages which may be sent to the cloud server in order to add personal information to the account.

PUSH_ID messages which may be sent to the cloud server in order to send the server an ID to be added to the account used to send push notifications to the client.

ASSOCIATE_RX messages which may be sent to the cloud server in order to add a receiver to a user account.

DISASSOCIATE_RXmessages which may be sent to the cloud server in order to remove an Rx from an associated account.

RETRIEVE_RX messages which may be sent to the cloud server in order to retrieve the list of receivers associated with a particular account.

GET_COURTESY_CUSTOMER messages which may be sent to the cloud server in order to retrieve the customer sponsoring wireless charging free minutes.

Reference is now made to Fig. 7, schematically representing selected components of a possible servicing venue deployment 400A for providing wireless power transfer services to electrical mobile devices. The power management system may provide locating functionality to electrical devices installed with an appropriate software application.

The wireless power outlet deployment 400A comprises a set of wireless power transfer venues 401A-F in communication with a central management server 410 via a communication network 120.

Two users, for example, 440a and 440b within the public space each using a personal electric device 442a and 442b connectable to the communication network 120. The electrical devices 440a and 440b are operable to execute a software application making use of the UCS-PCS API (see Fig. 6). As such, the message of GET_NEARBY_LOCATIONS with a technology value as a function parameter may be used to display a list of applicable venue locations, based upon the desired technology. It is noted that possible technologies, as described in this specification, may be selected from a group consisting of non-resonance, resonance, MIMO, and any.

It is further noted that the information regarding the location of the Hotspot may be associated with the TxID of the wireless power outlet. Such location information may be programmed into the Hotspot at, e.g., the time of installation, and may provide very accurate location information, which may be more accurate than what may be provided through other methods, such as GPS or antenna triangulation. Where the power provisioning software is an application configured for a mobile device, the Hotspot may transmit information regarding itself (e.g., TxID, location, and the like) to the device, which then transfers the information to the application. The application may further identify the location using GPS, antenna triangulation, in-door positioning methods and the like. Such data, may be transmitted by the wireless power outlet to the provisioning layer of the management server.

Reference is now made to Fig. 8, schematically representing a distributed system 500A for providing wireless power transfer services to electrical mobile devices in various venue locations searchable via a power management software application, for example. The distributed system may provide an application layer based upon a proprietary communication API to provide manageability and accessibility functions, over a computer network such as the Internet, mobile network, P2P architecture and the like. The application layer may be used by users and administrator having different access and permission rights, to allow various system functions such as authentication, identification, configuration, reporting, monitoring, policy management and the like.

The distributed system 500A comprises a management server 530, a management database 550, a communication network 560, venue setup 501A, venue setup 501B and venue setup 501C.

Optionally, the distributed wireless power management system 500A comprises a dashboard terminal 540.

The venue setup 501 A comprises a set of wireless power outlets 512a-e (collectively 512) accessible by PMA standards and connectable with the computer network 560 via the local venue gateway(s) 518A. The venue setup 50 IB comprises a set of wireless power outlets 514a-e (collectively 514) accessible by A4WP standards and connectable with the computer network 560 via the local venue gateway(s) 518B. The venue setup 501C comprises a set of wireless power outlets 516a-b (collectively 516) accessible by PMA standard / A4WP standard and connectable via an associated connection module of each wireless power outlet with the computer network 560.

With particular reference to the flowchart Fig. 9, selected actions are presented of a possible method 600A for performing a search of nearby venue servicing locations providing service of power transfer, according to an applicable technology. The communication may be performed between the electrical device associated with a user and the management server via a communication module.

The servicing location request message may include data pertaining to the operations required for locating of an appropriate servicing location with matching technology of the wireless power outlets of a venue and the electrical device. Accordingly, an inductive power outlet may support inductive type of technology, resonance type of technology or any type of technology.

The method 600A includes the communication module associated with an electrical device receiving a user charging request - step 610; thus, obtaining the technology of the electrical device - step 612; and generating a servicing location request communication message for searching nearby locations - step 614, based upon the N-2 interfacing API (as described hereinabove, Fig. 6); thereafter, sending the servicing location request to the management server - step 616; The management server, receiving the servicing location request message - step 618; processing the servicing location request message - step 620, to form a list of venue locations answering the search criteria; and further filtering the result list according to the desired technology - step 622; generating the servicing location response message - step 624; sending the servicing locations response message to the communication module - step 626; and the communication module, receiving the locations response message - step 628; processing the result set - step 630; and optionally, based upon configuration, presenting the result set to the user on the associated electrical device display - step 632. The interaction between the electrical device and the management server may use the User Control Function (UCF) / PMA Cloud Service (PCS) API (N2, Fig. 3) of GET_NEARBY_LOCATIONS message which may be communicated to the management server in order to retrieve the closest locations relative to current location. In particular, filtering the result set by the technology available may be selected from a group consisting of "non-resonance", "resonance", "mimo", "inductive", "capacitive", "magnetic beam" and "any" or "NON-RESONANCE ", "RESONANCE", "MIMO" , "INDUCTIVE" , "CAPACITIVE", "MAGNETIC BEAM" and "ANY".

The GET_NEARBY_LOCATIONS message helps locating nearby venues providing wireless power charging service. Accordingly, the UCF may provide to the cloud server data pertaining to the device location alongside other relevant parameters.

The GET_NEARBY_LOCATIONS message may include various parameters of the "GET NEARBY LOCATIONS" message may include various parameters such as:

• a 'LICENSE KEY' parameter to provide a license key of a user of the current device, allocated by the management server, optionally upon joining,

• a 'MESSAGE_TYPE' parameter to provide a Message name such as "GET_NEARBY_LOCATIONS",

• a 'VERSION' parameter to provide the version of message format thereby enabling the management server to be compatible with multiple communication protocols,

• a 'LATITUDE' parameter to provide the current latitude of the current device,

• a 'LONGITUDE' parameter to provide the current longitude of the current device,

• a 'RADIUS' parameter to provide the maximum distance on map from current location (latitude/longitude) to be searched for,

• a 'NUMBER OF RESULTS' parameter to provide The maximum number with nearest venues to be sent in the response,

• a 'ΡΜΑ_ΤΥΡΕ' parameter to determine the type of wireless charging technology required by the user, having a format: 'INDUCTIVE',

RESONANCE', MIMO', 'ANY', • a 'TIMESTAMP' parameter to provide a UTC -based report time having a format: YYYY-MM-DDTHH:MM:SSZ where ':', 'T' and 'Z' are constant values,

• a 'CUSTOMERS' parameter to provide a list of chains to filter the result list having a format: ["SBX", "CBTL", "MCD", "*"], values are acronyms of chains and "*" is a wildcard.

The GET_NEARBY_LOCATIONS response may include a plurality of result sets, associated with servicing locations according to the requested technology. The response may include various data response parameters of the "GET NEARBY LOCATIONS" message such as:

• a 'LOCATIONS' parameter to provide a list of venues filtered according to request, in particular as determined by the technology parameter, and may contain array of venues, as defined hereinafter,

• an 'ARRAY OF VENUES' to provide array of nearest locations, with the following parameter, for each entry in the list,

• a 'STORE' parameter to provide a name of a store, such as "134 5th AVENUE",

• a 'LATITUDE' latitude value of the store, such as 40.738952,

• a 'LONGITUDE', longitude value of the store, such as -73.991988,

• a 'DISTANCE', the distance from the requesting location, such as X (meters),

• a 'CUSTOMERS', the value of the acronym of the chain this venue is affiliated to, such as "SBX" - acronyms of the chain (may stand for Starbucks). Optionally, a 'ΡΜΑ_ΤΥΡΕ' parameter determining the type of wireless charging technology available, may be added to the 'ARRAY OF VENUES' for a specific venue, having a format: 'INDUCTIVE', RESONANCE', NON-RESONANCE', 'ΜΙΜΟ', 'ANY', where 'ANY' may indicate that all three technologies are available at a venue.

The GET_NEARBY_LOCATIONS, Example: messages may all share a common standardized headers. For example, the request messages for getting nearby charging spot locations may have headings of the form:

> POST /requests HTTP/1.1

Host: app-fe.powermatrix.com

Accept: application/] son

Content-type: application/] son

Content-Length: 192

Likewise, the response message of getting nearby charging spot locations may have headings of the form:

< HTTP/1.1 200 OK

Content- Type: application/] son

Date: Sun, 05 Jan 2014 15:41:07 GMT

transfer-encoding: chunked

Connection: keep-alive

The message body structure itself may follow similar standards for example, where applicable: The body of an HTTPS message delivered to the network server may contain several concatenated messages in a JSON array, the array may contain different types of API messages, including messages for both the Power Module (or wireless power outlet) and the Communication Module.

For example, a message body of GET_NEARBY_LOCATIONS may include multiple messages such as:

GET_NEARBY_L0CATIONS {

"LICENSE_KEY" : "00000000",

"MESSAGE_TYPE " : "GET_NEARBY_LOCATIONS " ,

"VERSION": "0.0",

"TIMESTAMP" : "2012-11-22T14: 12 :38Z",

"LATITUDE": "00000000",

"LONGITUDE": "00000000",

"RADIOUS": "5000000", "NUMBER_OF_RESULTS" : "30",

" PMA_TYPE" : " RESONANCE " ,

"TIMESTAMP" : "2012-11-22T14: 12 :38Z",

"CUSTOMERS": ["SBX", "WFB", "*"]

} and GET_NEARBY_LOCATIONS response may take the message format (header removed) note that multiple sets of parameters are provided under a common heading indicating a plurality of nearby hotspot locations:

{

"MESSAGE_TYPE " : " GET_NEARBY_LOCATIONS " ,

"VERSION": "0.0",

LOCATIONS: [

{

"STORE": "134 5th AVENUE",

"LATITUDE": "40.738952",

"LONGITUDE": "-73.991988",

"DISTANCE": "133",

"CUSTOMER": "SBX"

},

{"STORE": "Leaky Cauldron"

"LATITUDE": "51.511906",

"LONGITUDE": "-0.12847",

"DISTANCE": "2600000",

"CUSTOMER": "WFB"

}

Optionally, for a request of "PMA_TYPE" = 'ANY', the response may include the type of technology available at a venue, such as:

{

"MESSAGE_TYPE " : " GET_NEARBY_LOCATIONS " ,

"VERSION": "0.0",

LOCATIONS: [

{

"STORE": "134 5th AVENUE",

"LATITUDE": "40.738952",

"LONGITUDE": "-73.991988",

"DISTANCE": "133",

"PMA_TYPE " : "NON-RESONANCE "

"CUSTOMER": "SBX"

},

{"STORE": "Leaky Cauldron" " LATITUDE 51.511906

"LONGITUDE -0.12847

"DISTANCE 2600000

PMA TYPE RESONANCE

"CUSTOMER "WFB

It will be appreciated that although, only a selection of message types and formats are described herein for illustrative purposes, other message types may be sent as required. In certain embodiments, empty messages may be sent by the communication module to the network management server periodically. Such empty messages may be used to elicit response messages from the network management server as required. In other embodiments, the network management server may not respond to a communication where there is no functional change required for the power module or the communication module. Still other message types and formats may be used in adapted protocol versions as will occur to those skilled in the art as required.

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 method for managing a wireless power transfer network comprising at least one management server in communication with at least one electrical device, said method comprising at least one management processor executing instructions to perform operations comprising:

receiving at least one servicing location request message from said at least one electrical device;

processing said at least one servicing location request message; and

sending at least one servicing location response message to said at least one electrical device;

wherein said at least one servicing location request message communicates data indicating a current location and protocol compatibility of said electrical device and said at least one servicing location response message communicates data indicating at least one nearby venue providing wireless power using a protocol compatible with said electrical device.

2. The method of claim 1 , wherein said at least one electrical device communicates with said management server via a communication module.

3. The method of claim 1, wherein said protocol is associated with the type of wireless power technology required by said at least one electrical device.

4. The method of claim 3, wherein said protocol is selected from a group consisting of: non-resonance power transfer, resonance power transfer, MIMO power transfer, inductive power transfer and combinations thereof.

5. The method of claim 1, wherein said at least one servicing location request message comprises data pertaining to a license key provided by said management server, said license key authorizing said at least one location request message.

6. The method of claim 1, wherein said at least one servicing location request message comprises data pertaining to a version format of said at least one location request message.

7. The method of claim 1, wherein said at least one servicing location request message comprises data pertaining to said current location of said at least one electrical device.

8. The method of claim 7, wherein said current location comprises a latitude value and a longitude value.

9. The method of claim 1, wherein said servicing location request message includes data pertaining to a radius determining the maximum distance of searching from said current location.

10. The method of claim 1, wherein said servicing location request message comprises data pertaining to a maximum number determining the size of a nearest venues list to be sent in the at least one response message.

11. The method of claim 1 , wherein said at least one servicing location request message comprises data pertaining to a current time timestamp, said current time timestamp is presented in a standard world time format (UTC).

12. The method of claim 1, wherein said at least one servicing location request message comprises data pertaining to a list of customers to allow filtering of the result list.

13. The method of claim 1, wherein said at least one servicing location response message comprises data pertaining to a version format of said at least one servicing location response message.

14. The method of claim 1, wherein said at least one servicing location response message comprises data pertaining to a list of venue locations filtered according to said at least one location request message.

15. The method of claim 14, wherein said list of venue locations comprises an array of data elements selected from a group consisting of: a store name, a store location, a distance from said current location, a customer store chain name and combinations thereof.

16. A method for managing a wireless power transfer network comprising at least one management server in communication with at least one electrical device, said method comprising at least one electrical device processor executing instructions to perform operations comprising: sending at least one servicing location request message to said at least one management server;

receiving at least one servicing location response message from said at least one management server; and

processing said at least one location response message;

17. The method of claim 16, wherein said at least one electrical device communicates with said management server via a communication module.

18. The method of claim 16, wherein said protocol is selected from a group consisting of: non-resonance power transfer, resonance power transfer, MIMO power transfer, inductive power transfer and combinations thereof.

19. The method of claim 16, wherein said at least one servicing location request message comprises data pertaining to a license key provided by said management server, said license key authorizing said at least one location request message.

20. The method of claim 16, wherein said at least one servicing location request message comprises data pertaining to a version format of said at least one location request message.

21. The method of claim 16, wherein said at least one servicing location request message comprises data pertaining to said current location of said at least one electrical device.

22. The method of claim 21, wherein said current location comprises a latitude value and a longitude value.

23. The method of claim 16, wherein said servicing location request message comprises data pertaining to a radius determining the maximum distance of searching from said current location.

24. The method of claim 16, wherein said servicing location request message comprises data pertaining to a maximum number determining the size of a nearest venues list to be sent in the at least one response message.

25. The method of claim 16, wherein said at least one servicing location request message comprises data pertaining to a current time timestamp, said current time timestamp is presented in a standard world time format (UTC).

26. The method of claim 16, wherein said at least one servicing location request message comprises data pertaining to a list of customers to allow filtering of the result list.

27. The method of claim 16, wherein said at least one servicing location response message comprises data pertaining to a version format of said at least one servicing location response message.

28. The method of claim 16, wherein said at least one servicing location response message comprises data pertaining to a list of venue locations filtered according to said at least one location request message.

29. The method of claim 28, wherein said list of venue locations comprises an array of data elements selected from a group consisting of: a store name, a store location, a distance from said current location, a customer store chain name and combinations thereof.

30. A system for inductive transfer of electric power to an inductive receiver, the system comprising an array of inductive power outlets and a controller, the controller configured to selectively operate one or more of said inductive power outlets to operate in one of two or more modes of providing power.

31. The system according to claim 30, wherein one of said modes is a multiple input, multiple output mode, wherein two or more of said inductive power outlets cooperate to form a beam toward said receiver.

32. The system according to any one of claims 30 and 31, wherein one of said modes is an inductive mode.

33. The system according to any one of claims 30 to 32, wherein one of said modes is a resonance mode.

34. The system according to any one of claims 30 to 33, wherein said controller is configured to make the selection based on a coupling factor between at least one of said inductive power outlets and the receiver.

35. The system according to claim 34, wherein said controller is configured to reevaluate the coupling factor after a predetermined time interval has elapsed, and select a mode for continued power transfer accordingly.

36. The system according to any one of claims 30 to 35, wherein said controller is configured to make the selection based on the type of receiver.

37. A method for providing power wirelessly to a receiver, the method comprising:

(a) providing a system comprising an array of inductive power outlets and a controller configured to operate said outlets;

(b) detecting a receiver by said system;

(c) calculating a coupling factor between at least one of said inductive power outlets and the receiver;

(d) selecting, based on said coupling factor, a mode of power transfer from said inductive power outlet to the receiver, from two or more modes of providing power; and

(e) transferring power from said inductive power outlet to said receiver according to the mode selected.

38. The method according to claim 37, further comprising, after the transferring, reevaluating the coupling factor after a predetermined interval, and repeating steps (d) and (e).

39. The method according to any one of claims 37 and 38, further comprising determining whether power is required by said receiver, and, if not, terminating the method.

40. The method according to any one of claims 37 through 39, wherein one of said modes is a multiple input, multiple output mode, wherein two or more of said inductive power outlets cooperate to form a beam toward said receiver.

41. The method according to any one of claims 37 through 40, wherein one of said modes is an inductive mode.

42. The method according to any one of claims 37 through 41, wherein one of said modes is a resonance mode.