GB2641025A

GB2641025A - Power transmission method and apparatus

Info

Publication number: GB2641025A
Application number: GB2406683.9A
Authority: GB
Inventors: Sahyoun Walaa; Le Houerou Brice
Original assignee: Canon Inc
Current assignee: Canon Inc
Priority date: 2024-05-13
Filing date: 2024-05-13
Publication date: 2025-11-19
Also published as: GB202406683D0; WO2025237948A1

Abstract

Methods and apparatus for managing power transfer performed between a first wireless power apparatus and a second wireless power apparatus, the method includes establishing settings data relating to a first power transfer session including the first wireless power apparatus and the second wireless power apparatus. A second power transfer session is enabled, including the first power apparatus and the second power apparatus, based on the settings data established in the first power transfer session. The first power transfer session may require authentication. The settings data may be stored at either or both of the first and second wireless power apparatus.

Description

Power transmission method and apparatus

Field of the Invention

The present disclosure relates to a Wireless power Transmission system. In particular, but not exclusively, aspects of the disclosure aim to provide an improved method of wireless power transmission between a power transmitter and a power receiver. According to an embodiment, a reliable and low-latency activation solution of the full power delivery mode for Qi-compliant devices with user experience is provided by maintaining settings between the power transmitter and the power receiver.

Background

Wireless power charging is used nowadays in consumer applications such as smartphones, tablets and smart watches. Further applications are interested in wireless power transfer technologies such as medical applications, home appliances and electric vehicles or other fields with technologies that may require electrical power.

The fast-growing wireless charging market has motivated the manufacturers to find a global wireless charging standard for interoperability between devices. Most products rely on magnetic induction or magnetic resonance wireless charging technologies. The Wireless Power Consortium (WPC) is one of the open standard development groups working on these technologies to set global standards for safety, efficiency and interoperability. WPC has developed wireless power transfer standards related to Wireless mobile device charging (Qi), cordless kitchen appliances (IQ) and Light Electric vehicles (LEV). It combines magnetic induction and resonance technologies.

This disclosure relates particularly but not exclusively to the Qi standard using magnetic induction for wireless power transfer. The magnetic induction is based on transmitter and receiver coils being tightly coupled together. To guarantee the best power transmission between coils, the coils should be coupled in an optimum manner in order to maximize the coupling factor k between coils. The coupling factor k depends upon the shape of the inductors, the angle between the inductors and the distance between inductors. In order to transmit wireless power efficiency in a magnetic induction system, the transmitter and the receiver coils should be of same diameter and aligned with minimal distance between them. This tight coupling allows for less heat to be produced and for higher efficiency wireless power transfer.

Multiple Qi generations have been published in the recent years. The Qi standard has launched its first generation of Baseline Power Profile (BPP) in 2010 with 5W wireless power transfer. The subsequent versions have included new profiles with higher power transmission up to 15 W (e.g., Extended Power Profile (EPP)) and new features to address issues related to Foreign Object Detection (EOM. The latest version of the Qi specification (Qi 2.0) has introduced the Magnetic Power Profile (MPP) to enhance the coupling between coils by adding a magnet ring.

In Qi based wireless power transmission systems, the control of how the coils are powered is done via a control unit at the power transmitter (PTx) side and a control unit at the power receiver (PRx) side. The PTx and PRx communicate with each other using in-band communication with data modulation (Either amplitude or frequency based) on the power carrier frequency. A Qi-compliant device use a carrier frequency of 128 kHz and in the newest version of the Qi standard the Qi-complaint device uses an additional power carrier frequency of 360 kHz.

The communication protocol as specified in the Qi standard should be backward compatible i.e. it should be possible to use either a PRx or PTx, which is compliant with a newer version of the Qi standard, and capable of greater than SW wireless charging (using MPP or EPP), with either PRx or PTx, compliant with the first version of the Qi standard only capable of SW or less wireless charging (i.e. using only BPP).. A first communication between PRx and PTx is performed using BPP at 128 kHz to be compatible with the first Qi version. Once power transfer has been established for up to SW wireless charging, a second communication between the PRx and PTx is performed to check compatibility and other settings before going to the full power delivery above SW. The second communication is performed at either 128kHz or 360 kHz power carrier frequency for either EPP or MPP. Prior going to full power delivery, i.e. a higher-power mode, the PRx may need to configure the PTx, negotiate one or more power contract elements and validate an authentication of the PTx. There is time available for the configuration and the negotiation phases to occur, as time is needed to establish the power contract elements including the operating frequency, the power loss accounting, the power level, for example.

The authentication phase is mandatory in the communication protocol in order to protect the Qi brand and safeguard end users (PRx) from counterfeit power transmitters that may damage the PRx. WPC has added the mandatory support of the Qi authentication protocol at the PTx side for all power transmitters offering power charging above SW, starting from Qi 1.3 version.

The authentication phase plays a major role in minimizing product damage and end user safety risk for better user experience. In order to ascertain the authenticity of a transmitter product (PTx), a Qi individual unique certificate is assigned to the transmitter during manufacturing process. This unique certificate is a combination of WPC and manufacturer certificates attesting that the transmitter satisfies all Qi certification requirements.

The authentication phase consists of a first step requiring the PTx certificate to be sent and then validated by the PRx followed by a second step where the PRx challenges the PTx to send a response signed with the transmitter's unique private key for further validation. Upon successful two-steps validation, the PRx and the PTx may negotiate to bring the power level above 5W. The authentication exchanged messages are done using in-band communication with ASK modulation at receiver side and FSK modulation at transmitter side. As the in-band communication uses magnetic induction, the data rate is very low of the order of few kbits/sec.

Although the authentication protocol ensures the authenticity of the power transmitter and protects the power receivers, the PTx certificate needs an exchange of huge number of data packets with the PRx which may take few seconds to be received correctly. Any error in the sending of the certificate may require a retransmission of the certificate again leading to a delay while the data packets are exchanged again.

Thus, the communication protocol as in the recent specification requires an estimated time of between 15-30 seconds before activating the full power delivery mode.

The time required with the current Qi specifications can be considered as a drawback for some user experiences.

Furthermore, future specifications may add fast charging requirements not aligned with the current communication protocol limitations.

Accordingly, it is desirable to provide a better user experience with a communication protocol that is reliable but has lower latency than existing methods.

Summary

According to an aspect of the disclosure, there is provided a method for managing power transfer between a first wireless (contactless) power apparatus and a second wireless (contactless) power apparatus, the method comprising establishing settings data relating to a first (previous/earlier) power transfer session including the first wireless power apparatus and the second wireless power apparatus and enabling (establishing/activating) a second (subsequent or future) power transfer session, including the first power apparatus and the second power apparatus, based on the settings data. The enabling may comprise enabling the activation or power transfer phase of a power transfer session or experience.

Accordingly, by using settings data established in relation to a first power transfer session, a second power transfer session between the same devices can be enabled (established) more quickly thereby providing a responsive and low latency method of wireless power transfer.

The settings data may be related to specific or predetermined settings. Those settings being associated, used or indicative of the first power transfer session. The settings may be associated with a successful first power transfer (session or phase). The settings may be associated with a first power transfer session where a successful authentication of one of the first and second wireless power apparatus was performed. For example, successful authentication of one of the first and second wireless power apparatus which acted as a wireless power transmitter. The settings data may be session data (e.g. data relating to a communication session), or merely any data associated with the first power transfer between the first and second wireless power apparatuses.

Equivalently, the first and second power transfer session could be a first and second user experience. Alternatively, the first and second power transfer session may be afirst and second power transfer phase (or event) which takes place using the settings data of a power transfer session between the first and second wireless power devices. Alternatively, the first and second power transfer session may be a first power transfer and a second power transfer between the first and second wireless power apparatus. Alternatively, the first and second power transfer session may be a first power delivery and a second power delivery between the first and second wireless power apparatus. The power may be transferred (delivered) from the first wireless power apparatus to the second wireless power apparatus or alternatively from the second wireless power apparatus to the first wireless power apparatus.

Optionally, the first power transfer session and the second power transfer session use a full or high power delivery mode.

Optionally, the first power transfer session and the second power transfer session use a non-baseline power profile, non-BPP.

Optionally, the non-BPP profile (e.g. high power deliver mode) is an extended power profile, EPP, or a magnetic power profile, MPP.

Optionally, the first power transfer session requires authentication of at least one of the first wireless power apparatus and the second wireless power apparatus.

Optionally, the settings data indicates that at least one of the first wireless power apparatus and the second wireless power apparatus participated in the first power transfer session.

Optionally, the settings data comprises information elements related to one or both of the first wireless power apparatus and second wireless power apparatus Optionally, the information elements are associated with successful settings in the first power transfer session. In other words, settings which resulted in a successful power transfer between the first and second wireless power devices.

Optionally, the settings data may comprise an identifier associated with the settings data relating to the first power transfer session.

Optionally, the identifier comprises one or more of a session ID, a power device ID, a certificate or slot mask (Digest), For example, the digest may be used to retrieve a certificate or a slot mask that is included as at least part of the settings data.

Optionally, the settings data includes one or more power contract elements of the first power transfer session.

Optionally the settings data, once established, is valid for a predetermined duration oft me.

For example, the settings data may comprise timer data indicating a time period duration/length of time) for which the settings data is valid for use in enabling (activating or establishing) a second or subsequent power transfer session. The duration (length) of the time period may be static or variable.

The duration may depend on one or more of a predetermined algorithm, a battery level of the first or second power apparatus, and one or more of the power contract elements of the second power transfer session.

Optionally, the establishment of the settings data takes place after an authentication process has been performed between the first wireless power apparatus and the second wireless power apparatus in the first power transfer session.

Optionally, the establishment of the settings data comprises sending a request to generate the settings data from the second wireless power apparatus to the first wireless power apparatus or from the first wireless power apparatus to the second wireless power apparatus.

Optionally, the request is made using a predetermined message.

Optionally, said establishment comprises generating the settings data at the second wireless power apparatus or the first wireless power apparatus in response to the request.

Optionally, storing the settings data at either or both of the first wireless power apparatus and the second wireless power apparatus.

Optionally, the method further comprises generating a notification to a user of indicating that one of the first wireless power device and second wireless power device is a trusted device based on the validation.

Optionally, the method further comprises requesting, by the second power apparatus, the settings data from the first wireless power apparatus Optionally, the enabling of the second power transfer session is based on validation of the retrieved settings data by the second wireless power apparatus.

Optionally, the method further comprises negotiating a power contract for the second power transfer session after the settings data is validated by the second wireless power apparatus.

Optionally, the method further comprises negotiating a power contract for the second power transfer session before the settings data is validated by the second wireless power apparatus.

Optionally, one or more (negotiation) steps relating to establishing a power contract between the first wireless power apparatus and the second wireless power apparatus are omitted based on the information in the settings data.

Optionally, the second power transfer session is enabled prior to performing authentication between the first wireless power apparatus and the second wireless power apparatus Optionally, in (or by) enabling the second power transfer session one or more authentication steps -between the first wireless power apparatus and the second wireless apparatus are omitted.

Optionally, the (enabled) second power transfer session is halted upon a failed authentication.

Optionally, the authentication is performed upon the settings data no longer being valid.

Optionally, no authentication process is performed for the second power transfer session when the second power transfer session is enabled.

Opt onally, the method further comprises updating the settings data upon one or more of i) the second power transfer session being enabled, ii) one or more authentication steps between the first w eless power device and the second wireless power device being performed, and iii) a predetermined duration of time having passed.

Optionally, the first wireless power apparatus is a (wireless or contactless) power transmitter apparatus and the second power apparatus is a power receiver apparatus.

Alternatively, the first wireless apparatus may be a (wireless or contactless) power receiver and the second power apparatus a (wireless or contactless) power transmitter.

Further, the first wireless power apparatus and the second wireless power apparatus may alternatively be considered as a first power apparatus and a second power apparatus or a first contactless power apparatus and a second contactless power apparatus or a first wireless charging apparatus and a second wireless charging apparatus.

Optionally, the first wireless power transfer session and the second wireless power transfer session are performed in accordance with one or more features of a Qi specification. Alternatively, or additionally, the method may be in accordance with one or more features of the Ki and/or Light Electric Vehicle wireless power transfer specifications.

According to a further aspect of the disclosure, there is provided a power transmitter apparatus comprising means for transmitting power in a wireless power transfer session and control means for controlling the apparatus to perform a method in accordance with of any of the aspects or embodiments set out in the preceding statements.

According to a yet further aspect of the disclosure, there is provided a power receiver apparatus comprising means for receiving power in a wireless power transfer session, and control means for controlling the apparatus to perform a method in accordance with any of the aspects or embodiments set out in the preceding statements.

According to a yet further aspect there is provided a system comprising a first wireless (contactless) power apparatus and a second wireless (contactless) power apparatus, 30 the system being configured to perform the method of any of the aspects or embodiments set out in the preceding statements. Optionally, in said system the first wireless power apparatus is a wireless power transmitter apparatus and the second power apparatus is a power receiver apparatus.

Furthermore, features implemented in hardware may be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly. For example, in accordance with other aspects of the invention, there is provided a computer program comprising instructions to cause (when executed) a power apparatus to perform a method in accordance with any of aspects or examples/embodiments set out above in the preceding statements.

The program may be provided on its own or may be carried on, by or in a carrier medium. The carrier medium may be non-transitory, for example a storage medium, in particular a computer-readable storage medium. The carrier medium may also be transitory, for example a signal or other transmission medium. The signal may be transmitted via any suitable network, including the Internet.

Further features of the invention are characterised by the independent and dependent claims.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, method aspects may be applied to apparatus/device/ unit aspects, and vice versa.

Furthermore, features implemented in hardware may be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly Any apparatus feature as described herein may also be provided as a method feature, and vice versa. As used herein, means plus function features may be expressed alternatively in terms of their corresponding structure, such as a suitably programmed processor and associated memory.

It should also be appreciated that particular combinations of the various features described and defined in any aspects of the invention can be implemented and/or supplied and/or used independently.

Brief Description of the Drawings

Figure 1 is a block schematic diagram of a wireless power charging system with a power transmitter apparatus and a power receiver apparatus in which one or more embodiments may be implemented; Figure 2 is a block schematic diagram of Qi communications protocol phases; Figure 3 is a block schematic diagram showing communications protocol operating mode for Qi-compliant devices; Figure 4a is a block schematic diagram illustrating an example of non-Baseline Power Profile (BPP) communications protocol for Qi-compliant devices; Figure 4b is a flow diagram showing an example of non-Baseline Power Profile (BPP) communications protocol for Qi-compliant devices; Figure 5 is a block schematic diagram illustrating communications protocol operating mode including specific settings for Qi-compliant devices according to one or more embodiments Figure 6a is a block schematic diagram illustrating communications protocol for non-Baseline Qi profiles with a first user experience of specific settings according to one or more embodiments; Figure 6b is a block schematic diagram illustrating communications protocol for non-Baseline Qi profiles with future user experience of specific settings according to one or more 20 embodiments; Figure 7 is a flow diagram related to communications protocol for non-Baseline Qi profiles with a first user experience of specific settings according to one or more embodiments; Figure 8a is a flow diagram related to communications protocol for non-Baseline Qi profiles with future user experience of specific settings in negotiation phase according to one or more embodiments; Figure 8b is a flow diagram related to communications protocol for non-Baseline Qi profiles with future user experience of specific settings in power transfer phase according to one or more embodiments; Figure 9a is a block schematic diagram of an example method performed at power receiver apparatus for processing the setup of specific settings for first user experience according to one or more embodiments; Figure 9b is a block schematic diagram of an example method performed at power receiver apparatus for processing the application of specific settings for future user experience according to one or more embodiments; Figure 10a is a block schematic diagram of an example method performed at power transmitter apparatus for processing the setup of specific settings for first user experience according to one or more embodiments; Figure 10b is a block schematic diagram of an example method performed at power transmitter apparatus for processing the application of specific settings for future user experience according to one or more embodiments; Figures 11 is a schematic diagram illustrating example formats of specific settings messages in accordance with one or more embodiments; and Figure 12 is a block schematic diagram of an example of wireless charging device in 10 accordance with one or more embodiments; Figure 13 is a flow chart showing a method for managing power transfer according to one or more embodiments.

Detailed Description

Figure 1 is a block schematic diagram of a wireless power charging system with a power transmitter apparatus and a power receiver apparatus in which one or more embodiments of the according to the present disclosure may be implemented.

As mentioned above, the time required within the current Qi specifications to perform high power charging and in particular the MPP profile is disadvantageous. For example, an end user PRx may have experienced a full power delivery with the PTx previously. Any new communication session a PTx will lead to the same process being performed including the authentication phase. Thus, the communication protocol suffers from high latency and low responsiveness.

According to embodiments of the invention, (specific) settings relating to a previous (first) user experience are stored and are used in a subsequent (future or second) user experience to reduce, postpone, or remove entirely authentication protocol between the transmitter and receiver. Specific embodiments will now be described for WPC-compliant devices using the WPC specifications. However, it will be appreciated that it is not intended that the present invention is limited to WPC specifications or the system architecture of Figure 1 and aspects of the disclosure have applicability used in any contactless/ wireless charging specifications with a power transmitter and a power receiver.

Figure 1 shows the system architecture 100 for WPC-compliant devices. The system architecture 100 is composed of a contactless/wireless power transmitter PTx 101, a contactless/wireless power receiver PRx 102 and Qi accessory 103. The PTx 101 wirelessly transmits power to the PRx 102. In embodiments, the elements of the power transmitter PTx 101 may form part of a Base Station and the power receiver PRx 102 may form part of a mobile device.

WPC introduced Qi Wireless charging in 2010 with the Baseline Power Profile (BPP) power profile that allowed the PTx to deliver power up to SW. The BPP power profile was the only available mode for the first Qi specifications versions 1.0 and 1.1.

The Qi standard has introduced in version 1.2 the Extended Power Profile (EPP) power profile with a power delivery up to 15W. Version 1.3 added an authentication process for a safer, consistent and reliable wireless power charging. The operating frequency for both BPP and EPP power profiles is 128 kHz.

A recent version of the Qi 2.0 specification has introduced a new magnetic power profile (MPP) together with a few updates to legacy BPP and EPP power profiles. The MPP power profile adds magnetic ring features to guarantee the tight alignment of the primary coil 101e and the secondary coil 102a in order to ensure safer power transfer up to 15W and an increase of the efficiency. The MPP power profile operates at 360 kHz to mitigate interference with nearby vehicle key fobs.

The PTx 101 includes a power control unit 101b that provides overall control of the units comprising power transmitting apparatus. The different units 101a-h may be a part of the power transmitter system architecture.

The PRx 102 includes a power control unit 102b that provides overall control of the units comprising the power receiving apparatus. The different units 102a-h may be a part of the power receiver system architecture.

An external power source PIN is applied to the variable voltage supply 101a in PTx 101 to control the DC voltage of the input power signal. The DC power supplied by the variable voltage supply 101a is converted by the inverter 101c, acting as a power conversion unit, to AC power. The inverter 101c is a full bridge DC/AC converter that generates the AC power signal from DC power. To control the magnitude of the power transfer between PTx 101 and PRx 102, the DC voltage of the inverter in 101c is regulated and controlled.

At the PRx side 102, the power conversion unit 102d consists of a rectifier which converts the AC power received to DC power in order to supply the load 102e.

The resonant circuit 101d and 102c are switched capacitors in series with the coil to boost power transfer capability and to support both BPP and non-BPP modes (e.g., EPP and MPP). The MPP mode in the Qi 2.0 specification has an operating frequency range outside of the existing BPP frequency range and therefore requires different tuning capacitors on both the PTx 101 and PRx 102 for high and efficient power transfer. Because of this, both the PTx 101 and the PRx 102 employs switchable tuning capacitors to support both MPP and BPP operating frequencies.

The power is transferred wirelessly from the primary coil 101e to the secondary coil 102a via the Qi accessory unit 103. The 103 unit may include the non-magnetic keep-out area between coils, the magnetic ring specific to MIPP mode and other communication protocols such as RFID.

To ensure safe and efficient battery (102e) charging, battery management systems in the power receiver 102 (e.g., mobile devices) require information from the power transmitter (e.g., power source or the charger) to establish power contracts, regulate operating voltages, and detect the presence of foreign objects before battery charging starts. To this end, communications units 101f and 102f are used respectively at 101 and 102 power devices. The power signal provides the carrier for all communications.

The communications protocol differs between power profiles. The original protocol introduced in version 1.0 for BPP power profile consists of unidirectional communication from PRx to PTx. Starting from version 1.2, the Qi standard supports bidirectional communication. To facilitate bidirectional communication, both Frequency Shift Keying (FSK) and Amplitude Shift Keying (ASK) are used. On the PTx side, communications to the PRx uses FSK modulation of the power transfer frequency. The PRx side modulates its load 102e to affect ASK communication to the PTx. Prior to Qi 2.0 version (BPP and EPP modes), the FSK modulation speed at PTx is limited to 512 cycles per bit of data transferred while the ASK modulation speed at PRx is limited to 128 cycles per bit of data transferred which is faster than FSK. In Qi 2.0 version, the PTx uses FSK modulation speed of 128 cycles per bit of data transferred in order to speed up the data streams at the PTx side.

The communications protocol has evolved within the Qi specifications to take into account development of the power profiles. Version 1.3 has added an authentication process for a safer, consistent and reliable wireless power charging experience. The Qi version 2.0 has reduced the number of cycles per bit in order to speed up the data streams at PTx, in particular for the authentication process.

The authentication units 101g and 102g support non-BPP power profiles (EPP and MPP) starting from version 1.3 for safer and reliable wireless power charging and to avoid PTx counterfeits. Referring to the Authentication protocol in version 1.3 and 2.0, two-step validation is required by validating the PTx certificate and a follow-up challenge to the PTx.

The memory in 101h and the memory in 102h may store the power devices respective data including certification data.

Either or both of the power transmitter 101 and the power receiver 102 may be implemented in a power charging device 1200 as shown in and described with reference to Figure 12 below with the method as shown in Figure 5 being performed by the processing unit 1211.

We will now proceed to describe the Qi communications protocol for Qi-compliant devices with respect to Figures 2 and 3 According to Qi 2.0 communications protocol technical specification, clause 2.1, the communications protocol 200 comprises several phases including ping 201, configuration 202, negotiation 203 and power transfer 204. The EPP and MPP power profiles include all the phases 201-203 shown in figure 2. In the BPP power profile, however, the negotiation phase 203 is skipped.

Before initiating a Digital Ping to solicit a response from a Power Receiver 102, the Power Transmitter 101 should go through the following stages.

Detect objects: For this purpose, the Power Transmitter can use Analog Pings 301 or a variety of alternative methods. The Qi, Power Delivery, Technical Specification provides a number of examples. The Analog ping 301 is a very low power signal for detecting an object without waking up the power receiver 101.

Collect information of the presence of any foreign object found in addition to the power receiver.

The PTx 101 detecting the placement of a PRx 102 on the charging surface, starts the Digital ping phase in 302 to wake up the PRx 102.

The digital ping phase 302 consists of sending a digital ping 302a by the PTx 101. The PRx 102 sends a signal strength SIG and then proceeds to the identification 302b and configuration in 303.

According to clause 5 in the Qi 2.0 communications protocol, the PRx may identify itself in 302b using an identification (ID) data packet and optionally an extended identification XID data packet. The identification allows the PTx to determine the supported Qi protocol version by reading the PRx's ID data packet. The XID data packet may advertise the support of either EPP or MPP power profiles. Based on the PRx identification data packets, the PTx shall proceed to the next phase according to the Qi specifications.

In the configuration phase 202 or 303, the Power Transmitter and Power Receiver continue to operate using the Digital Ping parameters. According to clause 5 in Qi 2.0 communications protocol, this part of the protocol in 303 consists of three sub-steps as follows: The Power Receiver PRx identifies itself to the Power Transmitter PTx.

The Power Receiver PRx and Power Transmitter PTx establish a baseline Power Transfer Contract.

The Power Receiver and Power Transmitter determine the protocol variant to use in the power transfer.

The Negotiation phase 203 may come after the configuration phase 202 to negotiate the power contract elements. This phase is not present in the Baseline Protocol. In the case of EPP and MPP power profiles, the PTx 101 and the PRx 102 establish an extended or MPP power contract with additional settings.

The negotiation phase 203 may occur at two different stages in the communications protocol scheme. The negotiation phase 203 may be represented as question-answer technique where the PRx 102 sends simple query data packets and the PTx 101 answers with response pattern data packets. A first negotiation phase 304 may come directly after the configuration phase 202 or 303 serves to initiate the extended or MPP power contract by completing information about power loss accounting that is related to foreign object detection. The length of the negotiation phase is not restricted. In addition to simple queries, the PTx can use data-request data packets to retrieve more information from the PTx, e.g., the PTx identification or the PTx capabilities or extended capabilities.

The negotiation may also come later as a renegotiation phase 306 that may interrupt occasionally the power transfer phase 204. It serves mainly to adjust the power contract elements that have been issued in a previous negotiation phase 304. It may also be used to 25 create new power contract elements between the PTx and the PRx.

After negotiation phase 203/304 or 306 in EPP/MPP or configuration phase 202/303 in BPP, the Power transfer phase 204/305 begins. This is the phase in which the power transfer to the Power Receiver's Load occurs. A calibration process is needed in this phase for EPP/MPP protocols. Occasional interruptions of this phase may occur to renegotiate an element in 304 of the Power Transfer Contract. However, the power transfer continues during such renegotiations.

In the power transfer phase, the PRx reports the received power level to the PTx. The PRx and the PTx aim to drive the control error data to zero, at which point the system is operating at its target power level.

The PTx and the PRx can exchange application-level data throughout the power transfer phase 204/305 by enabling data transport streams. An important common application is authentication 305a, where both sides can authenticate in order to validate their counterpart's credentials.

It is recommended that the PTx and PRx first negotiate a Power Transfer Contract in 304 for the low power level in an intermediary four phases' loop, and after successful authentication in 305a, subsequently renegotiate a Power Transfer Contract for the higher power level in 306. Following the Qi specifications for EPP/M PP or non-BPP power profiles, the power transmitter 101 and the power receiver 102 may transit between different protocol phases depicted in figure 2 multiple times. In an example, the power devices (101 and 102) may do a first ping 302, configuration 303, negotiation 304 and power transfer 305 phases. In 305, the devices may authenticate in 305a. After authentication validation the PRx may need to renegotiate the power contract elements for higher power level. In this case, the power devices (101 and 102) may need to transit through the ping 302, configuration 303 phases to reach the renegotiation phase 306. After a successful renegotiation, the power devices (101 and 102) transit to the power transfer phase 305 to activate the full power delivery mode 305b as assigned in the renegotiated power contract.

Figure 2 represents a single loop of - Three phases for BPP power profile including 201, 202 and 204 -Four complete phases including 201-204 for non-BPP power profiles This loop can be repeated as much as needed to reach the full power delivery state. In an example, the MPP power profile may need at least three loops to reach the full power delivery state.

The non-Baseline Power Profile (BPP) communications protocol will now be described in more detail with reference to Figures 4a and 4b.

Figures 4a and 4b are examples of establishment of non-BPP power charging mode between a power transmitter 101 and a power receiver 102. Figure 4a represents the block diagram wherein different flows may be exchanged between the power transmitter and the power receiver as further illustrated in figure 4b.

According to Qi specifications and to ensure backward compatibility, the system starts up by operating initially in Qi BPP frequency band at 128 kHz to negotiate and determine which power profile is supported by both PTx and PRx devices. Therefore, the steps in 401, 402 and 403 reflect the ping 201, the configuration 202 and the power transfer 203 phases in BPP mode.

Referring to figure 2, the different consecutive phases constitute a loop. A BPP loop includes 201, 202 and 204 phases. A non-BPP loop includes all phases 201-204.

After the power receiver PRx 102 wakes up, it sends in a digital ping 401 the signal strength SIG 401a and the identification 401b. As already stated, the identification may include the ID and the XID data packets of the PRx. The XID data packet helps the PTx to determine the power profiles supported at the PRx side.

The PRx 102 may proceed by sending the configuration data packet (CFG) 402 in which the BPP power contract elements are settled. As the PTx 101 is aware of the supported power profiles at the PRx 102 side, it may send an FSK response pattern corresponding to an ACK response pattern (EPP mode) or MPP response pattern (MPP mode). Thus, the PRx identifies the supported power profiles at PTx side.

No negotiation phase is required in the BPP mode and thus, the power devices switch directly to the power transfer phase 403 and apply the BPP power contract established previously. Thus, a BPP mode may need one loop to begin power transfer at SW.

In case both PRx and PTx support a non-BPP power profile (e.g., EPP or MPP or any future power profile), the PRx may request a restart of the system in the power transfer phase 403. In order to establish a guaranteed load power level, the system may need several loops of four phases as stated in figure 2.

In an example, the PRx and the PTx may advertise MPP support. In power transfer (PT) phase 403, the PRx may send then an End Power Transfer (EPT)/rep data packet in order to switch to the new operating frequency at 360 kHz proper for MPP devices. As will be understood, the EPT/rep data packet t is broadly defined as a control message sent by a Qi power receiver in order to restart the system.

A second loop starts with digital ping 404 executed at the new operating frequency including the flows 404a and 404b followed by a configuration 405 for MPP mode. According to the XID data packet in 404b, the PRx may select the MPP-restricted mode or the MPP full mode as the activated power profile.

According to the Qi 2.0 communications MPP protocol technical specifications, the MPP restricted mode is a one-way directional communication from PRx to PTx with the power level limited to SW as for the BPP mode. The MPP full mode is a bidirectional communication that enables all Qi communication protocol phases including the negotiation phase and allows power level transfer up to 15 W. In case of MPP restricted mode, the power devices (101 and 102) perform a second configuration phase 405 followed by a power transfer phase 407. Hence, the transferred power level is 5 W at 360 kHz.

In case of MPP full mode, the configuration phase is followed by a first negotiation phase 406 where the PRx may send simple and data-request queries as stated earlier. As recommended by the Qi standard, a power transfer contract for power level (5W) may be negotiated first in 406. In this case, the second loop is considered as an intermediate loop for negotiating low power level in a non-BPP mode. Next, the power devices may start the power transfer phase in 407.

In 407, the power devices (101 and 102) may start an authentication process 408 in case the exchanged data streams are enabled. The authentication in 408 is a two-step validation process. According to the Qi 2.0 authentication technical specifications, as a first step of the validation process, the PRx 102 may request the Qi certification from the PTx 101 by sending a "Get Certificate" request 408a. The PTx 102 will send the certificate in "certificate chain" 408b if it exists. The certificate is a unique certificate pre-installed during the manufacturing process. The certificate chain has at least three certificates as stated in clause 3 of the Qi 2.0 authentication technical specification: * Root certificate identifying the WPC Root Certificate Authority * Manufacturer CA certificate identifying the product's manufacturer Product certificate identifying the individual power transmitted product The root and manufacturer certificates are signed by the WPC Root certificate Authority. The certificate chain length is of the order of hundreds of bytes. For MPP, for example, the certificate chain may exceed the 512 bytes as mentioned in clause 8.6.2.4.

The PRx once receiving the certificate chain may proceed to the validation. In addition to the validation of the certificate, the PRx will send a follow-up "Challenge" 408c to the PTx as a second step validation process. The PTx may reply with "Challenge response" 408d signed with the PTx' s unique private key.

The PRx may initiate the operations in any order by challenging the PTx first and then requesting the certificate chain.

Upon successful two-step authentication, the power devices need to renegotiate the power transfer contract to bring power level at new guaranteed load power level above 5 W. Thus, the system may restart a third loop and may transit again through the different phases in 409 to reach the renegotiation phase 306 or 410. Once power transfer contract is issued, the power devices (101 and 102) transit to the power transfer phase 411 and activate the full power delivery mode 411a above 5W. In case of a failed authentication process, the PRx can choose not to draw power levels above 5W.

The certificate chain length is of the order of hundreds of bytes and can exceed 512 bytes for MPP mode. The in-band communications between power devices have low data rate estimated to 2 kbits/sec. Hence, 512 bytes of certificate may take a few seconds to be transferred successfully.

In order to reduce the time required for authentication process, the PRx may use the "Get Digest" request for faster validation process. The PTx may reply with the Digest response. The Digest method can be used just if the digest is cached at PRx.

If the Digest is not in cache, the PRx will be obliged to go through the full authentication process to activate the full power delivery mode. Some user experiences may suffer from this latency as the authentication process as stated is time consuming and redundant. In a first example of user experience, a power receiver is on wireless power charger (transmitter) and is unplugged for a spontaneous usage and then plugged again. Thus, the power devices need to go through all the authentication process if digest is not in the cache. In a second example of user experience, the power transmitter may be for personal use and thus, it is a trusted/reliable device for the PRx. After a first successful authentication, the power transmitter can be considered as trusted/reliable device and thus, the authentication process is a waste of time.

Furthermore, future Qi generations focus on fast charging requirements. A heavy authentication process as in the present specifications may not respond to Qi standard requirements.

The aforementioned examples show that the communications protocol suffers from high latency and low responsiveness. In order to respond to user experiences and future Qi generations requirements, there is a need to optimize the communications protocol including the authentication process.

Improvements of communications protocol are illustrated in the following figures to answer user experience requirements in accordance with one or more embodiments of the invention.

For the sake of simplicity, the term "first user experience" designates a user experience where the full power delivery mode is activated after successful authentication. Equivalently, this can be referred to as a first power transfer session between a power transmitter and power received in a full power deliver mode. It is considered for the power devices as the reference user experience to be used to establish specific settings (i.e. settings that relate specifically to the first user experience or first power transfer session in the full power delivery mode). The term "first user experience-is used in the rest of the description.

First user experience The first user experience (e.g. a first power transfer session) will be described with reference to Figure 5 which is a block schematic diagram illustrating communications protocol operating mode including specific settings for Qi-compliant devices according to one or more embodiments of the invention.

In a first user experience, the power transmitter PTx 101 and the power receiver PRx 102 devices may use the communications protocol shown in Figure 3. After successful authentication 505a in the power transfer phase 505, the full power delivery state 505b can be activated.

A renegotiation of the power transfer contract may be needed if the power transfer contract for higher power level is not yet established or need to be updated. Thus, the power devices may need to start a new loop including the different phases in figure 2 to renegotiate the new terms of the power transfer contract for higher power level. The power devices go through digital ping 302, configuration 303 and renegotiation 506. In 506, a new power transfer contract for full power delivery is established or updated between power devices (101 and 102) and then the power devices transit to power transfer phase 505.

Thus, the activation of the full power delivery state 505b can occur after the authentication process 505a or after establishment/update of the power transfer contract in 506 and entering the power transfer phase 505.

According to one or more embodiments of the present invention, the power devices may create specific settings (e.g. settings data relating to a power transfer session including a power transmitter and a power receiver, or settings that are at least in part specific to a particular power transfer session between the power transmitter and power receiver) 505c at full power delivery state 505b. The specific settings may include information elements related to the power devices (101 and 102) and associated with the successful settings in the first user experience. Or more generally it may be any data that is related to or associated with the first user experience (e.g. a first power transfer session between the power devices 101 and 102).

Thus, the power devices (101 and 102) may recognize each other for future user experiences and may activate the full power delivery state 505b prior to the validation of the authentication 505a.

In an embodiment, the specific settings 505c can be created upon power receiver 102 request. After a successful first user experience, the PRx 102 may consider the power transmitter as a trusted/reliable device and thus, it may decide to create specific settings with the power transmitter already identified and authenticated. In another embodiment, the specific settings can be created at the power receiver and then communicated to the power transmitter.

In a yet further embodiment, the power transmitter can request the creation of the specific settings to the power receiver.

The specific settings, by way of example, may comprise a "session" that can be time-delimited with stored session settings to be applied or recalled by both power transmitter and power receiver in future user experience (i.e. power transfer) sessions.

The creation of the specific settings is done at the power transmitter and/or the power receiver by storing one or more information elements associated with the ongoing settings applied during the first user experience. According to one example, the specific settings may include all or part of the following information: -Specific settings identifier: The identifier is associated with the specific settings, for example a session ID. It can be a random ID or a part of an information element. The specific settings ID may link all or part of the following information together. In a future user experience, the specific settings ID is recalled by the power receiver and thus, referring to this ID, the power transmitter will fetch from its memory the information elements stored with this ID.

- Power devices ID: the first user experience' s settings may be linked to the PRx ID/XID and a PTx ID/XID. The identification of the power transmitter and the power receiver may change The ID may change from time to time and thus, associating the random identifier with the specific settings may help the power devices to perform identification.

- The certificate or a slot mask (Digest) stored at the power receiver side and referred at the power transmitter side. This information element is recalled using the Digest messages in Qi standard and helps to reduce the authentication process if the certificate exists in the cache. In the present disclosure, this slot mask (Digest) can be a part of the information elements used for specific settings - Timer: The specific settings are established at a certain point in time defined as the first user experience (or first power transfer session) and then brought to an end after timer expiry. The timer may be reset at each specific settings or authentication success in future user experiences (power transfer sessions). Otherwise, the timer may be settled once and at expiration, the power devices should undergo a full communications protocol as in figure 3 and then create another specific settings environment.

Power contract elements: The power contract elements negotiated in the negotiation phase may be stored in order to be recalled for future user experiences. In this case, the power devices may skip a part of the negotiation phase. In some use case, this information element can be efficient if the time elapsed between a first user experience in which the specific settings are created and a second user experience applying the specific settings is short. The unplugged power receiver for short time usage and then plugged again to the power transmitter can be an example of use case.

The establishment of the specific settings can be done during full power transfer.

The user at the establishment of the specific settings between power devices may receive an alert or a proprietary message notifying that the power transmitter is a trusted/reliable device (e.g., established session) or identified device.

Future user experience (e.g. a second power transfer session) In future (or subsequent) user experience (which includes establishment of a second power transfer session between the power transmitter and power receiver included in the first power transfer session described above), the power receiver starts the communications protocol with the power transmitter in order to establish full power delivery above 5W. Thus, the power devices need to negotiate and to authenticate in order to bring the full power delivery above 5W.

After a first BPP loop with three phases including a first ping phase 302, a first configuration phase 303 and a first power transfer phase 505, the system restarts again a second four phases' loop (i.e., figure 2) based on the exchanged information of the first loop. In an example, the power receiver and the power transmitter may indicate their support of the MPP power profile in the first loop and thus, the power receiver may request to switch to a new operating frequency in order to establish the MPP power profile.

In the second loop, the power receiver may switch to a new power profile with power transfer above 5W. A second ping 302 followed by a second configuration 303 is performed. Afterwards, a first negotiation phase 504 starts. At this stage, and according to Qi standard, it is recommended to negotiate power transfer contract for low power level in an intermediary four phases' loop (according to figure 2) before authentication. According to one or more embodiments, the PRx and the PTx may exchange and retrieve the specific settings 504a in negotiation phase 504 or later at the power transfer phase 505 before authentication process.

In an embodiment where the specific settings exchange 504a is occurring in the negotiation phase, the PRx 102 may send a first part of the information elements in the specific settings. The information elements may include the identifier to the power transmitter at a previous user experience of the specific settings ID. The PTx may recognize the specific settings ID and/or any other part of the specific settings information elements sent by the PRx.

The part of the specific settings other than the specific settings ID can be any information element of the specific settings that is capable of helping the PTx to retrieve the settings data at the PTx which have been stored from the previous power transfer session. The PTx may thereafter send an acknowledgement and retrieve the second part of the specific settings and send it to the PRx. The PRx receiving the second part of specific settings information elements may validate and send an acknowledgement to the power transmitter.

At this stage and after successful exchange of specific settings information elements in 504a, the power devices may proceed to negotiate the power transfer contract 504b for guaranteed load power level. The power devices may also retrieve the power transfer contract if it exists in the specific settings and may renegotiate on the basis of the retrieved contract.

The user may be notified after specific settings validation in 504a by an alert or proprietary message that the power transmitter is identified and/or a trusted/reliable device. Thus, the user may get a first notification that power charging is ongoing even though the power transfer may take a while before being activated.

Compared to the legacy technique, the use of specific settings from previous user experience may allow directly the negotiation of power transfer contract for high power level in the same loop. and thus avoids a third loop of four phases before (enabling) activating the full power mode delivery. Therefore, the specific settings may allow skipping of the intermediary loop with full four stages (i.e., figure 2) where the power transfer contract for low power level is negotiated.

After negotiation of power transfer contract in 504b, the power devices can go directly to full power delivery state 505b. The full power delivery mode is activated (enabled) and the power transmitter can transmit the power level negotiated with the power receiver in 504b.

The power receiver may determine afterwards how to proceed to the authentication 505d after activating full power delivery as stated hereafter: - The power receiver may request a full authentication process to the power transmitter by exchanging certificates and challenge - The power receiver may reduce the authentication process by skipping the certificate request. In this case, the power receiver may just challenge the power transmitter.

-The power receiver may decide to skip all the authentication process as the spec fic settings are still valid and the timer has not expired.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings after full power delivery or authentication validation or timer expiry. The updated specific settings may be stored at both power devices for next user experience.

By applying the specific settings, it is possible to speed up the communications protocol to reach the full power delivery mode by skipping one four phases' loop and the authentication process. Consequently, the time to full power delivery is reduced and helps to relieve the user from high latency and a low responsiveness experience. In other words, according to one or more embodiments, the specific settings allow a low latency user experience.

Embodiments will now be explained with reference to figures 6a, 6b, 7 and 11.

An example of first user experience block diagram 600a is illustrated in figure 6a with specific settings set up. At least three loops are needed in order to reach full power delivery state 609a. When the system starts up, it initially operates in BPP mode for backward compatibility. A first BPP three phases' loop is swept as follows: First Digital ping phase 601a, first configuration phase 602a and first power transfer phase 603a. The power devices (101 and 102) may then switch to non-BPP power profile and start a second four phases' loop with a second digital ping phase 604a, second configuration phase 605a and a first negotiation phase 606 followed by a second power transfer phase 607.

In the power transfer phase 607, the authentication process 607a is mandatory for non-BPP power profiles since version 1.3 before full power delivery. When authentication succeeded, the power transmitter can begin the full power delivery. A third four phases' loop 608 may start to renegotiate the power transfer contract for higher power level if it is not yet negotiated in 606.

At the power transfer phase 609 of the third loop, the power devices may transit to full power delivery state 609a and the power transmitter may start the above 5W power delivery as stated in the power transfer contract established in 606 or 608.

The power devices (101 and 102) may create specific settings in 609b by exchanging simple and data-request queries. The request of specific settings set up may be initiated at a first power device (PRx or PTx). The second power device (PTx or PRx) may respond with an acknowledgment or a rejection of the request. In case of request rejection, the power transmitter is considered as non-trusted/reliable device. In case of acknowledgment 609d, the specific settings are set up and stored at power receiver and/or power transmitter.

The creation of the specific settings is done at the power transmitter and/or the power receiver (first and second power devices) by storing some information elements associated to the ongoing settings applied during the first user experience. According to one or more embodiments, the specific settings may include all or part of the following information: -Specific settings identifier: The identifier is associated with the specific settings, for example a session ID. It can be a random ID or a part of an information element. The specific settings ID may link all or part of the following information together. In a future user experience, the specific settings ID is recalled by the power receiver and thus, referring to this ID, the power transmitter will fetch from its memory the information elements stored with this ID.

- Power devices ID: associated to the first user experience's settings such as PRx ID/XID and a PTx ID/XID. The identification of the power transmitter and the power receiver may change The ID may change from time to time and thus, referring the random identifier to the specific settings may help the power devices to identify.

-The certificate or a slot mask (Digest) stored at the power receiver side and referred at the power transmitter side. This information element is recalled using the Digest messages in Qi standard and helps to reduce the authentication process if the certificate exists in the cache. In the present invention, this slot mask (Digest) can be a part of the information elements used for specific settings -Timer: The specific settings are established at a certain point in time defined as first user experience and then brought to an end (i.e. are no longer valid or able to provide validation) after timer expiry. The timer may be reset at each specific settings or authentication validation in future user experiences. Otherwise, the timer may be settled once and at expiration, the power devices should undergo a full communications protocol as in figure 3 and then create another specific settings environment.

- Power contract elements: The power contract elements negotiated in the negotiation phase may be stored in order to be recalled for future user experiences. In this case, the power devices may skip a part of the negotiation phase. In some use cases, this information element can be efficient is the time elapsed between a first user experience in which the specific settings are created and a second user experience applying the specific settings is short. The unplugged power receiver for short time usage and then plugged in again to the power transmitter can be an example of use case.

In an example of specific settings, the power devices may create a session 609c at a first user experience and may assign some information elements to the session as stated previously.

The power receiver stored from its side all the information elements needed to identify and authenticate the specific settings (e.g., session). The power transmitter may store some information elements related to the specific settings identifier and other necessary information elements needed for future user experience identification and authentication. For instance, the power transmitter may store the specific settings ID, the power receiver ID and a slot mask (Digest) of the certificate exchanged with the power receiver.

The specific settings established between power devices 101 and 102 are then recalled in future user experiences (subsequent power transfer sessions or a second power transfer session). The block diagram 600b represents an example of future power transfer (session) using the specific settings set up previously.

The system starts up with BPP three phases' loop in accordance with legacy (figure 3). A first digital ping phase 601b followed by a configuration phase 602b and a power transfer phase 603b for BPP power profile. During the first BPP loop, the system will determine whether the PTx and the PRx both supports the same non-BPP mode (e.g., EPP or MPP).

Assuming that the same non-BPP mode is supported at both power devices, the power receiver may then request to switch to non-BPP power profile (e.g., EPP or MPP). A second four phases' loop is started with digital ping phase 604b, configuration phase 605b and a first negotiation phase 610.

At the negotiation phase 610, the power receiver 102 may interrogate in 610a the power transmitter about stored specific settings. The power receiver may send the specific settings ID with or without some information elements related to the specific settings. The power transmitter may reply with an acknowledgment and other information elements in the specific settings that prove its authenticity.

As an example of specific settings, the power devices may create a session in 609c. This session has an ID and associated information elements as stated previously. The power receiver in 610a may recall the established session between power devices by sending at least the session ID. The power receiver may send additional information elements associated to the session ID to the power transmitter. The power transmitter identifying the session ID may reply with an acknowledgment and some required information elements to identify the session at the power receiver. The required information elements may be requested by the power receiver or sent by the power transmitter by default.

The power receiver receiving acknowledgment and additional information elements from the power transmitter may verify the received information elements. In case the power receiver validates the information transmitted by the power transmitter, the power receiver may send an acknowledgment and thus, power devices may retrieve in 610b the specific settings information stored at both sides. After specific settings validation, the power devices may skip the intermediate negotiation of power transfer contract for low power level as intermediate loop and negotiate directly power transfer contract for higher power level (above SW) in 610c. Thus, an intermediate loop can be excluded from the communications protocol in accordance with one or more embodiments of this invention.

The power devices may then proceed to the full power delivery state 611a in the power transfer phase 611 without the need for preliminary authentication process validation 61 lb. In case of failed validation at the power receiver, the legacy protocol is used with an intermediate negotiation of the power transfer contract at low power level (if not yet done) and then go to the authentication process 61 lb. According to the aforementioned new stages added to the negotiation phase 610, and compared to legacy, the system can avoid at least one loop before and postpone the authentication process until after (enabling) activating the full power delivery state.

The authentication process 611b may be postponed to after the full power delivery state or merely reduced to the challenge step validation. Furthermore, the system can choose to not proceed for authentication whilst the specific settings have not yet expired.

The system may proceed to the renegotiation of the power transfer contract established already in 610 with a third loop 612, 613 and 614. The renegotiation is performed to negotiate some power contract elements for new guaranteed load power level. Nevertheless, the power transfer continues during the renegotiation phase 614 with no interruption.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings 609c after full power delivery (611a) or authentication validation (611b) or timer expiry. The updated specific settings may be stored at both power devices for next user 25 experiences.

Figure 7 is a flow diagram illustrating the different phases in the protocol including different exchanged messages. The flow diagram 700 illustrates an example of the creation of specific settings associated to the PTx and the PRx for a first user experience in accordance with one or more embodiments.

The system starts legacy three phases' BPP loop (401-403) followed by a legacy second four phases' loop (404-407) with an authentication process 408 at the power transfer phase 407. The description of the different phases is shown in figure 4b. Next, the system may negotiate a power transfer contract for low power level in the legacy negotiation phase 406 at the second loop. Thus, there is a need for a third four phases' loop (409, 410, 711) in order to renegotiate in 410, the power transfer contract for a new guaranteed load power level above 5W after authentication validation in 408. The digital ping, configuration and renegotiation phases (409 and 410) are legacy phases shown in figure 44 and already described above.

The power transfer phase 711 is an amendment of the 411 phase of figure 4. Upon activating the full power delivery mode in the power transfer phase 609 or 711, the system may decide to create specific settings pairing the power devices. The decision can be taken at the power receiver or power transmitter. The establishment of the specific settings can occur at the beginning of the power transfer phase 711 whilst full power delivery mode 711a (illustrated in figure 7) or at earlier stage during the renegotiation phase (not illustrated in figure 7) after enabling data streams.

In an embodiment illustrated in figure 7, the power receiver 102 may send a request 711b to the power transmitter 101 in order to create specific settings with the power transmitter. The request may be sent as GET [request] or GRQ [request] data packet or any other data request packet. The figure 11 represents a GET [request] data packet 1100 that allows PRx (or PTx) to request specific information from PTx (or PRx) The requested specific information is indicated in the parameter field 1100a. Different values of the parameter could be assigned as function of GET Request Types. In case of GET [specific settings], a new parameter value is assigned for PRx and PTx.

The power transmitter 101 may reply with either the data requested or a NULL in 711c to the power receiver. The data requested response 711 c is sent in case the specific settings are supported at the power transmitter side and the power transmitter agrees to exchange specific settings with the power receiver. The data requested may include one or part of the following information elements: Specific settings ID, power devices ID, certificate or a slot mask (Digest) of the certificate, timer or power contract elements.

For instance, the specific settings can be a session or data identifying a session. Thus, the power receiver may send a GET [session] in 71 lb and the power transmitter may respond with session ID in 711c The power transmitter may withdraw the specific settings request with NULL response in 711c because the requested information is not supported by the power device 101 or any other problems related to its functional blocks in figure 1 (e.g., out of memory).

The specific settings may be sent by the power transmitter in 711c. The system may complete the specific settings information elements by exchanging additional data packets in 711d. The additional information elements added in 711d can be requested or issued by the PRx. The specific settings or a part of the specific settings are then stored at both power transmitter and power receiver in their respective memories 101h and 102h.

The data packets 711c and 711d can be a new exchanged message or an amendment of an existing message in Qi standard. The figure 11 shows a specific settings new data packet 1101 where the specific settings' information elements are included in data fields 1 1 0 la. The data packet 1101 can be a data stream packet or a proprietary packet. The power devices may amend existing auxiliary data packet or proprietary data packet. The data packet 1102 represents an amended auxiliary data packet where the stream number indicates the type of payload information 1102b. New stream number in 1102a can be added to ADT data packet to indicate specific settings data streams and the information elements corresponding to the specific settings are added to the payload 1102b.

In another embodiment not illustrated in figure 7, the PRx may create the specific settings in case it considers the power transmitter as a trusted/reliable device. The PRx may then send in a first data packet, a simple request to the power transmitter to receive its acknowledgment.

The PRx may use either a new message as 1101 data packet or an amendment of an existing data packet such as specific request SRQ. The 1101 data packet may insert in the specific settings data field 1101a, the simple request of specific settings creation. The amended data packet SRQ may add a request value corresponding to the specific settings. The message can be proprietary data packet.

The power transmitter 101 may reply with either an acknowledgment ACK or a non-acknowledgment NAK response 711b. The ACK response is sent whether the specific settings are supported at the power transmitter side and the latter one agrees to exchange specific settings with the power receiver. The power transmitter may withdraw the specific settings request with NAK response because this technique is not supported by the power device 101 or any other problems related to its functional blocks in figure 1 (e.g., out of memory).

In case of a received ACK from the power transmitter, the system may complete the specific settings information elements by exchanging additional data packets in 711d. The additional information elements added in 711d can be requested or issued by the PRx. The PRx may share some information elements related to the specific settings with the PTx in a first stage (e.g., specific settings ID) and/or request some additional information elements from the PTx.

The specific settings or a part of the specific settings are then stored at both power transmitter and power receiver in their respective memories 101h and 102h.

The specific settings data packet 711d can be a new exchanged message or an amendment of an existing message in Qi standard. Figure 11 shows a specific settings new data packet 1101 where the specific settings' information elements are included in data fields 1101a. The data packet 1101 can be a data stream packet or a proprietary packet. The power devices may amend an existing auxiliary data packet or proprietary data packet. The data packet 1102 represents an amended auxiliary data packet where the stream number indicates the type of payload information 1102b. New stream number in 1102a can be added to ADT data packet to indicate specific settings data streams and the information elements corresponding to the specific settings are added to the payload 1102b.

The power transmitter can initiate the creation of specific settings. Thus, the embodiments evoked hereinabove for a first user experience can be applied with the power transmitter in place of the power receiver. All or part of the specific settings are then stored at power receiver and power transmitter side for future user experiences.

Figure 8a represents an example of future (subsequent or further) user experiences recalling specific settings set previously by the power devices. The flow diagram 800a illustrates an example of recalling the specific settings in the negotiation phase 807.

The system starts with a BPP first loop (401-403) and then restarts with a second nonBPP loop with four phases. The legacy phases 401 to 405 have been detailed previously with reference to figures 3 and 4.

At the negotiation phase of the second loop, the power devices may exchange part of the information elements relative to the specific settings established in the previous user experience. In an embodiment illustrated in flow diagram 800a, the power receiver may recall the specific settings by sending a part of the information elements in message 807a. This message 807a can use new message data packet as in 1101 or an amended existing message, for instance an auxiliary data stream 1102. These data packets can be data streams or proprietary data packets. The data fields 1101a and 1102a may bring a part of the information elements necessary to the PTx to identify the specific settings (e.g., specific settings ID).

The power transmitter may fetch in its memory by referring to the information elements sent in message 807a (e.g., specific settings ID). If the specific settings is present at PTx side, 30 it sends an acknowledgment ACK message 807b to the PRx.

The power receiver may send a GET [request] 807c whereas the request is to complete the specific settings or to retrieve the certificate chain DIGEST at PTx. The power transmitter may respond with the requested information elements. The message 807d may include either the requested part of the specific settings not sent in message 807a or the certificate chain DIGEST. The information in message 807d allows the PRx to validate the specific settings authenticity of the PTx. The power transmitter may send the message 807d after message 807a or 807b in order to complete with some missing information elements in the specific settings message sent in 807a.

The information elements sent in message 807d are verified at the power receiver side.

The PRx may then send an ACK message 807e to the PTx to inform the validation of the specific settings at the power receiver. Thus, the power devices may activate the full power delivery mode.

As shown previously in figure 6b, after specific settings validation, the power devices may skip the intermediate negotiation of power transfer contract for low power level as intermediate loop and negotiate directly power transfer contract for higher power level (above 5W) in 610c or 808. Thus, an intermediate loop can be excluded from the communications protocol in accordance with one or more embodiments.

The power devices may then proceed to the full power delivery state 611a or 810a in the power transfer phase 611 or 810 without the need for a preliminary authentication process validation.

According to the aforementioned new stages added to the negotiation phase 610 or 807, and compared to legacy, the system can avoid at least one loop before and postpone the authentication process to after (enabling) activating the full power delivery state.

The authentication process 611b or 810b may be postponed to after the full power delivery state 810a or reduced to the challenge step validation. Furthermore, the system can choose to not proceed for authentication whilst the specific settings has not yet arrived to expiration.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings 609c or 810c after full power delivery (611a or 810a) or authentication validation (61 lb or 810b) or timer expiry. The updated specific settings may be stored at both power devices for next user experiences.

In another embodiment the specific settings recall may come later and at the beginning of the power transfer phase as illustrated in the flow diagram 800b of the figure 8b.

In this flow diagram, the legacy phases 401 to 406 are described hereinabove with reference to figure 4. The power transfer contract negotiate in 406a may deal with low power level as recommended in the legacy method.

The exchange of specific settings messages may occur in the power transfer phase before authentication process 809g. The exchanged messages 809a to 809e are similar to 808a to 808b in the flow diagram 800a with a shift from the negotiation phase to the power transfer phase Once the PRx validates and sends an ACK to the PTx, the power devices may proceed to full power delivery mode in 8091 In case the power contract negotiated in 406a is for low power level, a renegotiation phase (not illustrated in figure 8b) may be required to negotiate some power contract elements for new guaranteed load power level. Nevertheless, the power transfer may continue during the renegotiation phase 614 with no interruption. Once the renegotiation has succeeded, the power transmitter may start to transmit in full power delivery mode as negotiated in the new power transfer contract.

The authentication process 611b or 809g may be postponed to after the full power delivery state 809f or reduced to the challenge step validation. Furthermore, the system can choose to not proceed for authentication whilst the specific settings has not yet expired.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings 609c or 809h after full power delivery (611a or 8090 or authentication validation (611b or 809g) or timer expiry. The updated specific settings may be stored at both power devices for next user experiences.

The flow diagrams 800a and 800b shows that specific settings can speed up the communications protocol by (enabling) activating the full power delivery mode whilst postponing the authentication process to after full power delivery. Thus, a significant reduction of the time required for full power delivery mode can be expected as the certificate exchange is no more necessary. Furthermore, the flow diagram 800a allows as well to reduce the number of needed loops before the full delivery mode activation by skipping an intermediate loop for low power level.

Figure 9a is a block schematic diagram of an example method performed at power receiver apparatus for processing the setup of specific settings for first user experience according to embodiments.

In a first user experience (first power transfer session) for non-BPP power profiles, the power receiver may authenticate the power transmitter and then migrate to full power delivery state 901 where the PTx transmits the power level negotiated in the power transfer contract. The block diagram 900a represents the creation of specific settings at a first user experience.

For better user experience, the PRx may decide to consider the PTx as a trusted/reliable device or a device with some priorities to simplify the establishment of the power profile. Thus, the power devices (101 and 102) may create specific settings in 609b by exchanging simple and data-request queries. The request of specific settings set up 902 may be initiated at a first power device (PRx or PTx). The second power device (PTx or PRx) may respond with an acknowledgment or a rejection of the request. In case of request rejection, the power transmitter is considered as non-trusted/reliable device. In case of acknowledgment 609d, the specific settings are set up in 903 and stored at power receiver and/or power transmitter in 904.

In a first example, the specific settings 505c can be created upon power receiver 102 request. After a successful first user experience, the PRx 102 may consider the power transmitter as a trusted/reliable device and thus, it may decide to create specific settings with the power transmitter already identified and authenticated.

In a second example, the specific settings can be created at the power receiver and then communicated to the power transmitter.

In a third example, the power transmitter can request the creation of the specific settings to the power receiver.

The PRx may create or contribute to the creation of the specific settings is done at the power transmitter and/or the power receiver by exchanging and then storing some information elements associated to the ongoing settings applied during the first user experience. For example, the specific settings may include all or part of the information described for the specific settings in the preceding embodiment(s) and, thus, will no be repeated here.

Different messages flow may be exchanged between power devices to create the specific settings as already detailed hereinabove with reference to figure 7.

The user may be notified about the specific settings establishment by an alert or a proprietary message giving the status of the charging device. In an example, the notification may include a trusted/reliable or a recognized or a paired device.

In future (subsequent or later) user experience, the power devices may attempt to retrieve the specific settings if existing for simplified power profile establishment process. The block diagram 900b represents the retrieval process of specific settings at PRx. After exchanging the PTx ID at 906, the power devices may proceed to validate the specific settings established in a previous user experience.

According to one or more embodiments, the PRx 102 may exchange and retrieve the specific settings 504a with the PTx 101 in negotiation phase 504 or lately at the power transfer phase 505 before authentication process.

In a first example, the PRx 102 may send a first part of the information elements in the specific settings in 907. The information elements may include the specific settings ID at previous user experience. The PTx may then recognize the specific settings ID and the first part of the specific settings information elements sent by the PRx 102. The PRx may thereafter receive an acknowledgement in 908. The PRx may request information elements from the PTx in order to validate the specific settings from its side in 910. For instance, the PRx may send a request for specific settings not sent in 907 or a Get certificate or digest. This information element may be stored at the PRx and included in the specific settings information elements. The PRx may receive the second part of specific settings information elements in 910. For instance, the PRx may receive the certificate or the digest chain from the PTx in 911. Next, the PRx may check the received information elements in 911. The PRx may validate and send an acknowledgement to the power transmitter in 911a. In case the received information in 910 cannot be validate by the PRx, it sends a NAK 911b to the PTx and then go to legacy procedure 916 as existing in the standard.

At 911a and after successful exchange of specific settings information elements in 504a, the power receiver may proceed to negotiate the power transfer contract 504b with the power transmitter for guaranteed load power level. The power receiver may also retrieve the power transfer contract in previous user experience if it exists in the specific settings and may renegotiate on the basis of the retrieved contract.

Figures 8a and 8b already described above represent different messages exchanged between the power receiver and the power transmitter to retrieve the specific settings.

Compared to the legacy, the use of specific settings from a previous user experience (previous power transfer session) may allow directly the negotiation of power transfer contract for high power level in the same loop to enable the full power mode delivery. and avoids a third loop before activating the full power mode delivery. Therefore, the specific settings may allow to skip an intermediary loop (i.e., figure 2) where the power transfer contract for low power level is negotiated.

After negotiation of power transfer contract in 504b, the power receiver can go to power transfer phase and can activate directly the full power delivery state 505b or 913. The authentication phase is postponed to after the activation of full power delivery mode.

The power receiver may determine afterwards how to proceed to the authentication 505d or 915after activating full power delivery as stated hereafter: - The power receiver may request a full authentication process to the power transmitter by exchanging certificates and challenge -The power receiver may reduce the authentication process by skipping the certificate request. In this case, the power receiver may just challenge the power transmitter.

- The power receiver may decide to skip all the authentication process as the specific settings are still valid and the timer has not expired.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings after full power delivery or authentication validation or timer expiry. The updated specific settings 915 may be stored at both power devices for next user experience.

By applying the specific settings, it is possible to speed up the communications protocol to reach the full power delivery mode by skipping at least one loop and the authentication process. Consequently, the time to full power delivery is reduced and helps to relief the user from high latency and low responsiveness experience. According to one or more embodiments, the specific settings allow a low latency user experience with responsive system.

Figure 10a is a block schematic diagram of an example method performed at power transmitter apparatus for processing the setup of specific settings for a first user experience. In a first user experience for non-BPP power profiles, the power transmitter may succeed the authentication process and migrate with the power receiver to full power delivery state 1001 where the PTx transmits the power level negotiated in the power transfer contract. The block diagram 1000a represents the creation of specific settings at a first user experience.

For better user experience, the PTx may decide to request specific settings from the PRx in order to be labelled as a trusted/reliable device or a device with some priorities for this power receiver to be used for future user experience. In step 1002, the power transmitter may initiate the specific settings creation by sending a request to the power receiver. It may also receive a request for specific settings creation from the PRx.

The creation of the specific settings at the power transmitter may need a device assessment to check its capabilities. If the power transmitter is the initiator of the specific settings request, thus, it supports the specific settings experience. In case the power transmitter receives a request from the power receiver, then a device assessment is needed from its side. The power transmitter 101 may reply with an ACK 1003b or NAK 1003a response to the power receiver.

In an example, the power transmitter may then send all or part of the specific settings to the power receiver in 1003b. The specific settings may include the specific settings ID or the information needed for future experience identification. The power transmitter may send specific settings data in 1003a that may include one or part of the following information elements: Specific settings ID, power devices ID, certificate or a slot mask (Digest) of the certificate, timer or power contract elements.

The power transmitter may withdraw the specific settings request 1002 with NAK (NULL in figure 7) response because the requested specific settings are not supported by the power device 101 or any other problems related to its functional blocks in figure 1 (e.g., out of 10 memory).

The power transmitter may then receive an acknowledgment 1004 from the power receiver for specific settings information sent previously. The power transmitter may then store the specific settings data from its side in its memory 101h for future usage (1005).

In another example, the power transmitter may receive specific settings from the power receiver. In this case, the power transmitter may acknowledge the received data and store it in its memory 1005.

Different messages flow may be exchanged between power devices to create the specific settings as detailed hereinabove in figure 7.

Figure 10b is a block schematic diagram of an example method performed at power transmitter apparatus for processing the application of specific settings for future user experience. In a future user experience, the power devices may attempt to retrieve the specific settings if existing for simplified power profile establishment process. The block diagram 1000b represents the retrieve process of specific settings at PTx. After exchanging the PTx ID at 1006, the power devices may proceed to validate the specific settings already established in previous user experience.

According to one or more embodiments, the PTx 102 may exchange and retrieve the specific settings 504a with the PRx 101 in negotiation phase 504 or lately at the power transfer phase 505 before authentication process.

In a first example, the PTx 102 may receive a first part of the information elements in the specific settings in 1007. The information elements may include the identifier of the specific settings at previous user experience. The power transmitter may check in 1008 the presence of corresponding specific settings and may fetch them from its memory by referring to the information elements sent in message 1007 (e.g., specific settings ID). If the specific settings data is present at PTx side, it sends an acknowledgment ACK message 1008b to the PRx. In case the specific settings are not found, the power transmitter may send a NAK 1008a to the power receiver.

In order to be identified at PRx side, the PTx may send information elements 1009 to the PTx including the other part of the specific settings that may identify the PTx as previously used device. For instance, the PRx may send a request query including Get certificate or digest.

The PTx may then respond with the certificate or the digest stored by PRx in previous session. Next, the PTx may receive response 1010 from the power receiver. In case of acknowledgment response 1011, the PTx may proceed to full power delivery mode 1011a by activating the power transfer at the new guaranteed load power level. In case of non-acknowledgment response, the power transmitter may return to legacy protocol. The power transmitter may conduct a renegotiation phase in 1011a if the power transfer contract for new guaranteed power level is not yet done. During the renegotiation phase, the power transfer may continue.

Figures 8a and 8b already described above represent different messages between the power receiver and the power transmitter to retrieve the specific settings.

Compared to the legacy technique, the use of specific settings from a previous user experience may allow directly the negotiation of power transfer contract for high power level in the same loop thereby enabling the full power transfer and avoiding a third loop before activating the full power mode delivery. Therefore, the specific settings may allow to skip an intermediary loop (i.e., figure 2) where the power transfer contract for low power level is negotiated.

After negotiation of power transfer contract in 504b, the power transmitter can transit to power transfer phase and can transmit directly the full power in 1011a. The authentication phase is postponed to after the activation of full power delivery mode.

The power receiver may determine afterwards how to proceed to the authentication 505d or 1012 after activating full power delivery as stated hereafter: -The power receiver may request a full authentication process to the power transmitter by exchanging certificates and challenge - The power receiver may reduce the authentication process by skipping the certificate request. In this case, the power receiver may just challenge the power transmitter.

For privacy reason, the power devices (101 and 102) may choose to update the specific settings after full power delivery or authentication validation or timer expiry. The updated specific settings 1013 may be stored at both power devices for next user experience.

By applying the specific settings, it is possible to speed up the communications protocol to reach the full power delivery mode by skipping at least one loop and the authentication process. Consequently, the time to full power delivery is reduced and helps relieve the user from a high latency experience with low responsiveness. In other words, according to one or more embodiments, the use of specific settings (e.g. the use of settings relating to a first user experience to validate a future user experience) allow a low latency user experience with high responsiveness.

In an embodiment shown in Figure 13, there is provided a method 1300 of managing power transfer between first and second wireless power devices (apparatus). In a first step 1301, settings data is established. The settings data may relate to a previously performed power transfer session (i.e. a previous user experience) between the first wireless power apparatus and the second wireless power apparatus. That previous power transfer session may be as in previous embodiments a high power or full power transfer session such as EPP or MPP in the Qi standard. Alternatively or additionally,the previous power transfer session may require (e.g. having a power profile that requires) an element of authentication e.g. of one of the wireless power devices and, particularly, of the wireless power device responsible for power transmission. For example, in an embodiment, a plurality or all power profiles available will require at least some authentication. The settings data may be specific settings that are predetermined or selected but related to the first power transfer session. Establishing the settings data may include steps of storing at least part of the settings data at either or both of the devices and as mentioned in embodiments above this may be done at the request of either device.

In step 1302, a second power transfer session (i.e. future or subsequent user experience) is enabled between the devices based on the (established) settings data. The second power transfer session may also be a high power or full power transfer session such as EPP or MPP in the Qi standard and in embodiments the settings data may be used to omit, reduce, or postpone authentication steps that would normally be required to authenticate one of the devices as the power transmitter. Alternatively, or additionally the settings data may allow for some steps in establishing a power contact to be omitted, for example, by reusing elements of the power contract from the earlier first session. The settings data may include any of the elements already discussed above in the preceding description with reference to specific settings or other settings data for the first user experience using the MPP or EPP mode. The use of the settings data to enable the second power transfer session may be time limited and the settings data itself may include timer data indicating the duration of validity. In enabling (the activation of) the second power transfer session, a challenge and response protocol may take place between the devices, whereby one device requests part or all of the settings data by means of an identifier which identifies the previous power transfer session.

In an optional step 1303, the settings data may be updated. This could happen upon the second power transfer session being enabled, ii) one or more authentication steps between the first wireless power device and the second wireless power device being performed, and iii) a predetermined duration of time having passed.

Any other compatible features described above in connection with earlier embodiments and aspects may be combined with the embodiment herein described with respect to Figure 13.

The steps of the process 1300 may be implemented in hardware or software. Each step of the process may be performed a functionally equivalent hardware unit or software module, for example, or executed at a control unit of a power transfer device or in software executed by one or more processors of a device.

Figure 12 is a block schematic diagram of an example of wireless charging device (a 20 power device) in accordance with one or more embodiments.

The wireless charging device 1200 may preferably be an electronic device capable of wireless charging such as a micro-computer or a workstation or a mobile device or a light portable device or a fixed device. The wireless charging device 1200 comprises a communication bus 1213 to which there are preferably connected: -a processing unit 1211, such as a microprocessor, and denoted CPU in Figure 12. The processing unit 1211 may be a single processing unit or processor or may comprise two or more processing units or processors carrying out the processing required for the operation of the wireless charging device 1200. The number of processors and the allocation of processing functions to the central processing unit 1211 is a matter of design choice for a skilled person; -memory for storing data and computer programs containing instructions for the operation of the communication device 1200. The computer programs may contain a number of different program elements (modules) or sub-routines containing instructions for a variety of operations and for implementing the methods in accordance with one or more embodiments; and - at least one communication interface 1202 for communicating with other devices or nodes in a wireless communication system, such as a wireless charging system of Figure 1.

The at least one communication interface 1202 may be connected to a second communication interface 1203, such as a secondary coil or RFID of the wireless charging system, over which digital data packets or frames or control frames are transmitted.

Each of the power transmitter and the power receiver may comprise such a wireless charging device 1200.

The memory may include: - a read only memory 1207, denoted ROM, for storing computer programs for implementing the methods in accordance with one or more embodiments; - a random-access memory 1212, denoted RANI, for storing the executable code of methods according to one or more embodiments as well as the registers adapted to record variables and parameters necessary for implementing methods according to one or more embodiments.

Optionally, the communication device 1200 may also include one or more of the following components: - a data storage means 1204 such as a hard disk, for storing computer programs for 20 implementing methods according to one or more embodiments; - a disk drive 1205 for a disk 1206, the disk drive being adapted to read data from the disk 1206 or to write data onto said disk; - a screen 1209 for displaying decoded data and/or serving as a graphical interface with the user, by means of a keyboard 1210 or any other user input means.

Preferably the communication bus provides communication and interoperability between the various elements included in the communication device 1200 or connected to it. The representation of the bus is not limiting and in particular, the processing unit is operable to communicate instructions to any element of the wireless charging device 1200 directly or by means of another element of the wireless charging device 1200.

The disk 1206 may optionally be replaced by any information medium such as for example a compact disk (CD-ROM), rewritable or not, a ZIP disk, a USB key or a memory card and, in general terms, by an information storage means that can be read by a microcomputer or by a microprocessor, integrated or not into the communication device, possibly removable and adapted to store one or more programs whose execution enables methods according to one or more embodiments to be implemented.

The executable code may optionally be stored either in read only memory 1207, on the hard disk 1204 or on a removable digital medium such as for example a disk 1206 as described previously. According to an optional variant, the executable code of the programs can be received by means of the communication interface 1203, via the interface 1202, in order to be stored in one of the storage means of the communication device 1200, such as the hard disk 1204, before being executed.

The processing unit 1211 is preferably adapted to control and direct the execution of the instructions or portions of software code of the program or programs according to the disclosure, which instructions are stored in one of the aforementioned storage means. Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term "processor," as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. Also, the techniques could be fully implemented in one or more circuits or logic elements.

While the present disclosure has been described with reference to embodiments, it is to be understood that the disclosure is not limited to the disclosed embodiments. It will be appreciated by those skilled in the art that various changes and modification might be made without departing from the scope of the disclosure, as defined in the appended claims. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. The mere fact that different features are recited in mutually different dependent claims does not indicate that a combination of these features cannot be advantageously used.

In the preceding embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof If implemented in software, the functions may be stored on or transmitted over, as one or more instructions or code, a computer-readable medium and executed by a hardware-based processing unit.

Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are instead directed to non-transient, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Mu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Claims

CLAIMS1. A method for managing power transfer between a first-wireless power apparatus and a second wireless power apparatus, the method comprising: establishing settings data relating to a first power transfer session including the first wireless power apparatus and the second wireless power apparatus; enabling a second power transfer session, including the first power apparatus and the second power apparatus, based on the settings data.
2. A method according to claim 1, wherein the first power transfer session and the second power transfer session use a high power delivery mode
3. A method according to claim 2, wherein the first power transfer session and the second power transfer session use a non-baseline power profile, non-BPP.
4. A method according to claim 3, wherein the non-BPP profile is an extended power profile, EPP, or a magnetic power profile, MPP.
5. A method according to any preceding claim wherein the first power transfer session requires authentication of at least one of the first wireless power apparatus and the second wireless power apparatus.
6. A method according to any preceding claim, wherein the settings data indicates that at least one of the first wireless power apparatus and the second wireless power apparatus participated in the first power transfer session.
7. A method according to any preceding claim, wherein the settings data comprises information elements related to one or both of the first wireless power apparatus and second wireless power apparatus
8. A method according to claim 7, wherein the information elements are associated with successful settings in the first power transfer session
9. A method according to any preceding claim, wherein the settings data comprises an identifier associated with the settings data relating to the first power transfer session.
10. A method according to claim 9, wherein the identifier comprises one or more of a session ID, a power device ID, a certificate or slot mask (Digest),
11. A method according to any preceding claim, wherein the settings data includes one or more power contract elements of the first power transfer session.
12. A method according to any preceding claim, wherein the settings data, once established, is valid for a predetermined duration of time.
13. A method according to claim 11, wherein the settings data may comprise timer data indicating a time period for which the settings data is valid.
14. A method according to claims 11 or 12, wherein the duration may be static or variable.
15. A method according to claim 13, wherein the duration depends on one or more of a predetermined algorithm, a battery level of the first or second power apparatus, and one or more of the power contract elements of the second power transfer session.
16. A method according to any preceding claim, wherein the establishment of the settings data is after an authentication process has been performed between the first wireless power apparatus and the second wireless power apparatus in the first power transfer session.
17. A method according to any preceding claim, wherein the establishment of the settings data comprises sending a request to generate the settings data from the second wireless power apparatus to the first wireless power apparatus or from the first wireless power apparatus to the second wireless power apparatus.
18. A method according to claim 17, wherein the request is made using a predetermined 20 message.
19. A method according to claim 17 or 18, wherein said establishment comprises generating the settings data at the second wireless power apparatus or the first wireless power apparatus in response to the request.
20. A method according to any preceding claim comprising storing the settings data at either or both of the first wireless power apparatus and the second wireless power apparatus.
21. A method according to any preceding claim further comprising generating a notification to a user of indicating that one of the first wireless power device and second wireless power device is a trusted device based on the validation.
22. A method according to any preceding claim, further comprising requesting, by the second power apparatus, the settings data from the first wireless power apparatus.
23. A method according to claim 22, wherein the enabling of the second power transfer session is based on validation of the retrieved settings data by the second wireless power apparatus.
24. A method according to claim 23, further comprising negotiating a power contract for the second power transfer session after the settings data is validated by the second wireless power apparatus.
25. A method according to claim 23, further comprising negotiating a power contract for the second power transfer session before the settings data is validated by the second wireless power apparatus.
26. A method according to claims 24 or 25, wherein one or more negotiation steps relating to establishing a power contract between the first wireless power apparatus and the second wireless power apparatus are omitted based on the information in the settings data.
27. A method according to any preceding claim, wherein the second power transfer session is enabled prior to performing authentication between the first wireless power apparatus and the second wireless power apparatus
28. A method according to claim 27, wherein in enabling the second power transfer session one or more authentication steps between the first wireless power apparatus and the second wireless apparatus are omitted.
29. A method according to claim 27 or claim 28, wherein the enabled second power transfer session is halted upon a failed authentication.
30. A method according to any of claims 27 to 29, wherein the authentication is performed upon the settings data no longer being valid.
31 A method according to any of claims 1 to 26 wherein the authentication process is not performed for the second power transfer session when the second power transfer session is enabled.
32. A method according to any preceding claim, further comprising updating the settings data upon one or more of i) the second power transfer session being enabled, ii) one or more authentication steps between the first wireless power device and the second wireless power device being performed, and iii) a predetermined duration of time having passed.
33. A method according to any preceding claim, wherein the first wireless power apparatus is a wireless power transmitter apparatus and the second power apparatus is a power receiver apparatus.
34. A method according to any preceding claim, wherein the first wireless power transfer session and the second wireless power transfer session are performed in accordance with one or more features of a Qi specification.
35. A power transmitter apparatus comprising: means for transmitting power in a wireless power transfer session; and control means for controlling the apparatus to perform the method of any of claims 1 to 34.
36. A power receiver apparatus comprising: means for receiving power in a wireless power transfer session; and control means for controlling the apparatus to perform the method of any of claims 1 to 34.
37. A system comprising a first wireless power apparatus and a second wireless power apparatus, the system being configured to perform the method of any of claims 1 to 34.
38. A system according to claim 37, wherein the first wireless power apparatus is a wireless power transmitter apparatus and the second power apparatus is a power receiver apparatus.
39. A computer program comprising instructions to cause a power apparatus to perform the method of any of claims 1 to 34.