English:
[0001] Wireless power transfer (“WPT”), sometimes also known as inductive power transfer (“IPT”) has recently become more prevalent in a number of applications. One application in which WPT/IPT has seen increases in use is the consumer electronics space around devices such as mobile phones (i.e., smart phones) and their accessories (e.g., wireless earphones, smart watches, etc.) as well as tablets and other types of portable computers and their accessories (e.g., styluses, etc.).
[0002] In some embodiments, a wireless power receiver is capable of negotiating with a power transmitter in a standards-compliant way to operate in a manner that is beyond the scope of the standard.
[0003] A wireless power receiver can include a receiver coil configured to receive power from a wireless power transmitter, a rectifier coupled to the receiver coil configured to convert an AC voltage appearing across the receiver coil to a DC voltage delivered to a load, and a control and communications module coupled to the receiver coil and the rectifier. The controller and communications module may be further configured to receive in-band communication signals from the wireless power transmitter via the receiver coil and operate the rectifier to generate in- band communication signals delivered to the power transmitter via the receiver coil. The in-band communication signals can include communications in compliance with a standard communication protocol negotiating a transition to an enhanced or extended operating mode. The enhanced or extended operating mode can include operating at one or more of a frequency and a power level different than a frequency or power level prescribed by the standard communication protocol.
[0006] The wireless power transmitter can further include an NFC communication module coupled to the control and communication module. In that case, the enhanced or extended operating mode can include delaying wireless power transfer to permit NFC communication with a corresponding NFC communication module in the wireless power receiver. The communication in compliance with a standard communication protocol can include negotiating a transition to an enhanced or extended operating mode include communications indicating one or more enhanced capabilities of the transmitter. The communication in compliance with a standard communication protocol negotiating a transition to an enhanced or extended operating mode can further include communications requesting one or more enhanced capabilities of the receiver. The communication in compliance with a standard communication protocol negotiating a transition to an enhanced or extended operating mode can still further include communications acknowledging one or more enhanced capabilities of the receiver. The communication in compliance with a standard communication protocol negotiating a transition to an enhanced or extended operating mode can also include communications relating to a user interface capability of at least one of the transmitter and receiver.
[0007] A method of negotiating wireless power transfer between a wireless power transmitter or a wireless power receiver and a counterpart device can include initiating communication with the counterpart device using a standard communication protocol, communicating one or more enhanced capabilities of the device to the counterpart device using the standard communication protocol, and determining whether the counterpart device is also capable of operating in accordance with each of the one or more enhanced capabilities. If the counterpart device is not capable of operating in accordance with one or more of the enhanced capabilities, the method can further include operating in a standard mode. Alternatively, if the counterpart device is capable of operating in accordance with one or more of the enhanced capabilities, the method can further include negotiating a transition to an agreed enhanced mode including one or more of the enhanced capabilities. The communications between the device and its counterpart may be in-band or out- of-band communications. The enhanced capabilities may include an ability to operate at a frequency or power level different than a frequency or power level prescribed by the standard communication protocol. The enhanced capabilities may include NFC communications capabilities and the enhanced mode includes delaying wireless power transfer to permit NFC communication. The enhanced capabilities may also include user interface capabilities of the transmitter or receiver device, in which case the agreed enhanced mode can include an agreement between the device and its counterpart as to which device will provide information about a state of wireless power transfer to a user.
[0008] Figure 1 illustrates a wireless power transfer system.
[0009] Figures 2A-2E illustrate a wireless power transfer negotiation to operate in an enhanced/extended wireless power transfer mode.
[0010] Figure 3 illustrates a flow chart of a receiver-side negotiation for an enhanced/extended wireless power transfer mode.
[0011] Figure 4 illustrates a flow chart of a transmitter-side negotiation for an enhanced/extended wireless power transfer mode.
[0012] Figure 5 illustrates a flow chart of an NFC scan process associated with an enhanced/extended wireless power transfer mode.
[0013] Figure 6 illustrates a high level flow chart of a power transfer negotiation to operate in an enhanced/extended wireless power transfer mode.
[0014] In the following description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of the disclosed concepts. As part of this description, some of this disclosure’s drawings represent structures and devices in block diagram form for sake of simplicity. In the interest of clarity, not all features of an actual implementation are described in this disclosure. Moreover, the language used in this disclosure has been selected for readability and instructional purposes, has not been selected to delineate or circumscribe the disclosed subject matter. Rather the appended claims are intended for such purpose.
[0015] Various embodiments of the disclosed concepts are illustrated by way of example and not by way of limitation in the accompanying drawings in which like references indicate similar elements. For simplicity and clarity of illustration, where appropriate, reference numerals have been repeated among the different figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the implementations described herein. In other instances, methods, procedures and components have not been described in detail so as not to obscure the related relevant function being described. References to “an,” “one,” or “another” embodiment in this disclosure are not necessarily to the same or different embodiment, and they mean at least one. A given figure may be used to illustrate the features of more than one embodiment, or more than one species of the disclosure, and not all elements in the figure may be required for a given embodiment or species. A reference number, when provided in a given drawing, refers to the same element throughout the several drawings, though it may not be repeated in every drawing. The drawings are not to scale unless otherwise indicated, and the proportions of certain parts may be exaggerated to better illustrate details and features of the present disclosure.
[0016] Figure 1 illustrates a simplified block diagram of a wireless power transfer system 100. Wireless power transfer system includes a power transmitter (PTx) 110 that wirelessly transfers power to a power receiver (PRx) 120 via inductive coupling 130. Power transmitter 110 may receive input power that is converted to an AC voltage having particular voltage and frequency characteristics by an inverter 114. Inverter 114 may be controlled by a controller/communications module 116 that operates as further described below. In various embodiments, the inverter controller and communications module may be implemented in a common system, such as a system based on a microprocessor, microcontroller, or the like. In other embodiments, the inverter controller may be implemented by a separate controller module and communications module that have a means of communication between them. Inverter 114 may be constructed using any suitable circuit topology (e.g., full bridge, half bridge, etc.) and may be implemented using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc. made using silicon, silicon carbide, or gallium nitride devices).
[0017] Inverter 114 may deliver the generated AC voltage to a transmitter coil 112. In addition to a wireless coil allowing magnetic coupling to the receiver, the transmitter coil block 112 illustrated in Fig. 1 may include tuning circuitry, such as additional inductors and capacitors, that facilitate operation of the transmitter in different conditions, such as different degrees of magnetic coupling to the receiver, different operating frequencies, etc. The wireless coil itself may be constructed in a variety of different ways. In some embodiments, the wireless coil may be formed as a winding of wire around a suitable bobbin. In other embodiments, the wireless coil may be formed as traces on a printed circuit board. Other arrangements are also possible and may be used in conjunction with the various embodiments described herein. The wireless transmitter coil may also include a core of magnetically permeable material (e.g., ferrite) configured to affect the flux pattern of the coil in a way suitable to the particular application. The teachings herein may be applied in conjunction with any of a wide variety of transmitter coil arrangements appropriate to a given application.
[0018] PTx controller/communications module 116 may monitor the transmitter coil and use information derived therefrom to control the inverter 114 as appropriate for a given situation. For example, controller/communications module may be configured to cause inverter 114 to operate at a given frequency or output voltage depending on the particular application. In some embodiments, the controller/communications module may be configured to receive information from the PRx device and control inverter 114 accordingly. This information may be received via the power transmission coils (i.e., in-band communication) or may be received via a separate communications channel (not shown, /.< ., out-of-band communication). For in-band communication, controller/communications module 116 may detect and decode signals imposed on the magnetic link (such as voltage, frequency, or load variations) by the PRx to receive information, and may instruct the inverter to modulate the delivered power by manipulating various parameters (such as voltage, frequency, phase, etc.) to send information to the PRx. In some embodiments, controller/communications module may be configured to employ frequency shift keying (FSK) communications, in which the frequency of the inverter signal is modulated, to communicate data to the PRx. Controller/communications module 116 may be configured to detect amplitude shift keying (ASK) communications or load modulation based communications from the PRx. In either case, the controller/communications module 126 may be configured to vary the current drawn on the receiver side to manipulate the waveform seen on the Tx coil to deliver information to from the PRx to the PTx. For out-of-band communication, additional modules that allow for communication between the PTx and PRx may be provided, for example, WiFi, Bluetooth, or other radio links or any other suitable communications channel.
[0019] As mentioned above, controller/communications module 116 may be a single module, for example, provided on a single integrated circuit, or may be constructed from multiple modules/devices provided on different integrated circuits or a combination of integrated and discrete circuits having both analog and digital components. The teachings herein are not limited to any particular arrangement of the controller/communications circuitry.
[0020] PTx device 110 may optionally include other systems and components, such as a near field communications (“NFC”) module 118. In some embodiments, NFC module 118 may communicate with a corresponding module or radio frequency identification (RFID) tag in the PRx via the power transfer coils. In other embodiments, NFC module 118 may communicate with a corresponding module or tag using a separate physical channel 138. In some embodiments, as described in greater detail below, it may be necessary to suspend inductive power transfer to prevent interference with NFC communications.
[0021] As noted above, wireless power transfer system also includes a wireless power receiver (PRx) 120. Wireless power receiver can include a receiver coil 122 that may be magnetically coupled 130 to the transmitter coil 112. As with transmitter coil 112 discussed above, receiver coil block 122 illustrated in Fig. 1 may include tuning circuitry, such as additional inductors and capacitors, that facilitate operation of the transmitter in different conditions, such as different degrees of magnetic coupling to the receiver, different operating frequencies, etc. The wireless coil itself may be constructed in a variety of different ways. In some embodiments, the wireless coil may be formed as an winding of wire around a suitable bobbin. In other embodiments, the wireless coil may be formed as traces on a printed circuit board. Other arrangements are also possible and may be used in conjunction with the various embodiments described herein. The wireless receiver coil may also include a core of magnetically permeable material (e.g., ferrite) configured to affect the flux pattern of the coil in a way suitable to the particular application. The teachings herein may be applied in conjunction with any of a wide variety of receiver coil arrangements appropriate to a given application.
[0022] Receiver coil 122 outputs an AC voltage induced therein by magnetic induction via transmitter coil 112. This output AC voltage may be provided to a rectifier 124 that provides a DC output power to one or more loads associated with the PRx device. Rectifier 124 may be controlled by a controller/communications module 126 that operates as further described below. In various embodiments, the rectifier controller and communications module may be implemented in a common system, such as a system based on a microprocessor, microcontroller, or the like. In other embodiments, the rectifier controller may be implemented by a separate controller module and communications module that have a means of communication between them. Rectifier 124 may be constructed using any suitable circuit topology (e.g., full bridge, half bridge, etc.) and may be implemented using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc. made using silicon, silicon carbide, or gallium nitride devices).
[0023] PRx controller/communications module 126 may monitor the receiver coil and use information derived therefrom to control the rectifier 124 as appropriate for a given situation. For example, controller/communications module may be configured to cause rectifier 124 to operate provide a given output voltage depending on the particular application. In some embodiments, the controller/communications module may be configured to send information to the PTx device to effectively control the power delivered to the receiver. This information may be received sent via the power transmission coils (i.e., in-band communication) or may be sent via a separate communications channel (not shown, i.e., out-of-band communication). For in-band communication, controller/communications module 126 may, for example, modulate load current or other electrical parameters of the received power to send information to the PTx. In some embodiments, controller/communications module 126 may be configured to detect and decode signals imposed on the magnetic link (such as voltage, frequency, or load variations) by the PTx to receive information from the PTx. In some embodiments, controller/communications module 126 may be configured to receive frequency shift keying (FSK) communications, in which the frequency of the inverter signal has been modulated to communicate data to the PRx. Controller/communications module 126 may be configured to generate amplitude shift keying (ASK) communications or load modulation based communications from the PRx. In either case, the controller/communications module 126 may be configured to vary the current drawn on the receiver side to manipulate the waveform seen on the Tx coil to deliver information to from the PRx to the PTx. For out-of-band communication, additional modules that allow for communication between the PTx and PRx may be provided, for example, WiFi, Bluetooth, or other radio links or any other suitable communications channel.
[0024] As mentioned above, controller/communications module 126 may be a single module, for example, provided on a single integrated circuit, or may be constructed from multiple modules/devices provided on different integrated circuits or a combination of integrated and discrete circuits having both analog and digital components. The teachings herein are not limited to any particular arrangement of the controller/communications circuitry.
[0025] PRx device 120 may optionally include other systems and components, such as a near field communications (“NFC”) module 128. In some embodiments, NFC module 128 may communicate with a corresponding module or radio frequency identification (RFID) tag in the PTx via the power transfer coils. In other embodiments, NFC module 128 may communicate with a corresponding module or tag using a separate physical channel 138. In some embodiments, as described in greater detail below, it may be necessary to suspend inductive power transfer to prevent interference with NFC communications.
[0026] Numerous variations and enhancements of the above described wireless power transmission system 100 are possible, and the following teachings are applicable to any of such variations and enhancements.
[0027] As noted above, PRx controller/communications module 126 and PTx controller/communications module 126 may communicate with each other to respectively identify themselves to one another and to negotiate power delivery between them. This identification and negotiation process may be done in conjunction with a standard-defined protocol, such as protocols defined by the Wireless Power Consortium Qi standard, so that devices from different manufacturers can interoperate. Compliance with such a standard provides the benefit of interoperability at the potential expense of specialization. In other embodiments, the identification and negotiation process may be done in conjunction with a proprietary protocol determined by the manufacturer of the devices, which provides the benefit of improved flexibility and potentially extended performance, with the drawback of the loss of interoperability with devices that do not implement the proprietary protocol.
[0028] To address this dilemma, the controller/communications modules may be configured to initiate the negotiation process according to a standard-defined protocol. In the process of that negotiation, one, the other, or both devices may identify themselves — in a way that complies with the standard — as supporting an enhanced capability set that goes beyond the scope of the standard. If both devices are capable of operating in accordance with this enhanced capability set, the devices may choose to operate in accordance with the enhanced capability set. Otherwise, the devices may choose to operate in conjunction with the standards-based capability set. In one embodiment, the enhanced capability set may include the ability to operate at a different frequency, at different power levels, or in other ways that go beyond what is defined in an existing standard.
[0029] Figures 2A-2H illustrate an exemplary communication exchange between a wireless power receiver (PRx) 120 and a wireless power transmitter (PTx) 110 to migrate from a first communication protocol regime to a second regime including one or more enhancements specific to that second regime. In some examples the first protocol regime is a standards-based regime, such as Qi. Enhancements in the second regime may be either an extended or enhanced version of the standard (such as a latter version or an alternate version) or may be a completely separate and proprietary system. The various communication packets described may take any of a variety of forms, employing different packet structures, different modulation schemes for communicating the packets and the like. The following description addresses at a high level the components of the communication packets, but it will be appreciated that any particular protocol implementations may specify different or additional data that may be included in these packets as appropriate.
[0030] With reference to Fig. 2A, an exemplary negotiation process begins with PRx 120 sending a sequence of messages 202-208 to power transmitter 110. This exchange may be triggered by the PRx detecting that it is in proximity to a PTx, as is commonly implemented in wireless power transfer systems. The exchanges may take place using in-band communication at a frequency specified by the standard. In some embodiments, this frequency may be between about 100kHz and about 250kHz. In some embodiments, this frequency may be 128kHz. In the illustrated example, the four messages 202-208 correspond to messages sent in accordance with the Qi standard; however, in some embodiments, there may be more or fewer messages, and they may comply with an alternative standard or protocol.
[0031] The first message 202 may be a SIG packet, z.e., a Signal Strength packet in accordance with the Qi standard. The second message 204 may be an ID packet, z.e., an Identification packet in accordance with the Qi standard. The third message 206 may be an XID, z.e., Extended Identification packet in accordance with the Qi standard. The fourth message 208 may be a CFG packet, z.e., a Configuration packet in accordance with the Qi standard. In some embodiments, these four packets may correspond to a “Ping” and “Configuration Phase” according to the Qi standard. Details of these packets, including the information contained therein and the effects of such packets in the system are described in detail in the Qi standard versions to which they pertain, and thus are not repeated here. It will be appreciated that various versions of the Qi standard may incorporate different versions of such packets, and that later versions may combine, eliminate, or otherwise changes such packets. Thus the illustrated packets are provided here merely as examples of a standards-compliant initialization, and other similar arrangements could also be used.
[0032] Of interest in the above-described communications is the XID packet. In the Qi standard, this optional packet may be used to provide additional information exchange between the PRx and PTx. This additional information exchange may include identification of enhanced capabilities, such as the ability to perform in accordance with an extension or enhancement to the standard or other extra- standard (z. e. , beyond the scope of the standard) mode of operation. These performance io modes not specified in the standard are described herein are referred to as extra-standard (“XS”). Thus, upon receiving a communication from the PRx that it is capable of performance in accordance with an extension or enhancement to the standard, the PTx may send a response packet 210 that is an XS ACK, z.e., an acknowledgement of the extra-standard capability of the PRx.
[0033] Turning now to Fig. 2B, further communication between the PRx and PTx is illustrated. Upon receiving from the PTx acknowledgement of the PRx enhanced (XS) capabilities, the PRx may send a further packet 212 requesting that the PTx provide its enhanced capabilities, if any. This may take the form of a “GET” request in which the PRx requests that the PTx send its enhanced capabilities, if any, in the form of an XS XID packet, z.e., a packet that is beyond the scope of the base standard and provides what extra capabilities beyond the standard the PTx is capable of providing. This packet may provide an indication of the various features beyond the scope of the base standard that the PTx can provide, such as different power transfer parameters (voltage, power level, operation frequency, etc.) as well as one or more parameters relating to the PTx that are necessary to operate in the enhanced (XS) mode.
[0034] As an example, the PTx may indicate that it is capable of operating at a different frequency beyond that defined in the base standard. In some cases the PRx may be configured to prefer operating at this different frequency if available, for example, to avoid potential interference with other devices or systems. As a result, the PRx may initiate a series of communications to transition from the present standards-compliant operating frequency to the different, extra-standard frequency. As part of this communication process, the PRx may also attempt to exchange other information about the power transfer, including user interface (UI related information) and information relating to other devices systems, such as the NFC system described above. To that end, the communications illustrated in Fig. 2B may continue with the PRx requesting UI related parameters (message 216) and the PTx reporting the requested UI related parameters (message 218).
[0035] As an example, it may be desirable to provide a user with feedback indicating the state or status of the wireless power transfer system. For example, it might be useful to provide a visual indication (such as an LED or colored LED) or an audio notification (such as a beep or chime) of a successful or unsuccessful power transfer arrangement. Depending on the particular devices used, either the PTx or the PRx may or may not have certain UI types available. For example, a charging pad may have status LEDs, but may not have a speaker that allows it to reproduce a chime. Other devices, such as a smart phone, may be able to provide audio and visual indicators. Likewise, other devices, such as a charging case may have limited UI capabilities. Thus, to provide the desired level of feedback to the user, the devices may need to negotiate amongst themselves to determine which device has the capabilities to provide the desired feedback to the user.
[0036] In the illustrated embodiment, it is the PRx that makes the decision as to which device will provide the required user feedback. Turning now to Fig. 2C, the PRx may communicate its determination, informed by its own capabilities and the capabilities received from the PTx in its XID packet, as to how various user interface issues will be handled. This may be communicated to the PRx by an SRQ UI (special request-user interface) packet 220. The PTx may acknowledge this request/instruction (ACK packet 222) and both devices may proceed accordingly. Similarly, the PRx may indicate a desired operating frequency via SRQ Freq packet 224 (special requestfrequency). The PTx may acknowledge this request/instruction (ACK packet 224) and both devices may proceed accordingly to operate at a different frequency as described in greater detail below. Additionally, the PRx may use an SRQ NFC (special request-NFC) packet 228 request certain NFC parameters. These may include, for example, as a delay between deactivating the present power and communication exchange at the default/standard frequency and reactivating power and communication exchange at the optional frequency requested in packet 224, to allow for an NFC scan to take place, as described in greater detail below. The PTx may acknowledge this request/instruction (ACK packet 230) and both devices may proceed accordingly. Finally, the PRX may provide for additional special requests concomitant with the enhanced/extended protocols or may indicate an end to the special requests with SRQ End (special request-end) packet 232. The PTx may acknowledge this request/instruction (ACK packet 234) and both devices may proceed accordingly, e.g., to transition to the new frequency, provide the desired UI interactions, and allow for NFC operation as agreed in the foregoing exchange.
[0037] Turning now to Fig. 2D, the PRx may send an EPT (end power transfer) packet 236 in accordance with the original standard, e.g., the Qi standard. It will be appreciated that depending on the particular standard and version used, this packet may be different; however, the point of this instruction (and ending of the current power/data exchange regime) is to transition from operation in accordance with the original power transfer standard (e.g., at a standard-defined frequency) to power transfer in accordance with the enhanced/extended standard as negotiated in the preceding exchange (e.g. , at a different frequency not in accordance with the original standard but in accordance with the enhanced standard). Thus, power transfer is disabled (238), which can also allow for time to perform a NFC scan, if negotiated (240). It is noted that, more generally speaking, other types of out of band communication can be utilized, such as Bluetooth and RFID communications. Further details of such an out of band communication, in this example a NFC scan, are discussed below.
[0038] Following the disabling of power transfer 238 and the optional NFC scan 240 (or other activities taking place during the negotiated delay), power transfer may be reinitiated in the enhanced mode, e.g., at a different frequency, beginning with the message exchange 242-248. In some embodiments, this re-initiation in the enhanced mode is responsive to successful communications between the PTx and PRx during the optional out of band communication period (e.g., NFC scan 240). In the illustrated embodiment, this begins with the PRX sending a series of messages compliant with the extended or enhanced standard (“XS”) that otherwise match a basic pattern corresponding to the standards-compliant initiation or “Ping” conducted initially. As before, the exchanges may take place using in-band communication at a frequency specified by the extended or enhanced standard. In some embodiments, this frequency may be between about 360kHz, although other frequencies may be used.
[0039] In the illustrated example exchange, the first message 242 may be an XS: SIG packet, i.e., a Signal Strength packet in accordance with an extended standard. The second message 244 may be an XS:ID packet, i.e., an Identification packet in accordance with the extended standard. The third message 246 may be an XS:XID, i.e., Extended Identification packet in accordance with the extended standard. The fourth message 248 may be a XS:CFG packet, i.e., a Configuration packet in accordance with the extended standard. In some embodiments, these four packets may correspond to a “Ping” and “Configuration Phase” generally paralleling the Qi standard. In other embodiments, the exchange may include more or fewer messages and may be entirely unique or may generally parallel other standards-based communication protocols. Thus, the illustrated packets are provided here merely as examples of a ping or initialization procedure, and other similar arrangements could also be used. In some embodiments this ping or initialization procedure may be used to confirm the parameters negotiated in the prior special request exchange described above.
[0040] Turning now to Fig. 2E, establishing power transfer in accordance with the enhanced standard (e.g., at a different frequency) may require exchange of further information between the receiver and transmitter. Thus, the PRx may request extended identification information of the PTx using message/packet 252, XS: GET PTx XID (/.< ., extended standard, get power transmitter extended identification information). In response, the PTx may provide the requested information via message/packet 254 PTx XID. The PRx may also provide to the PTX an indication of its own capabilities using message 256 XS: SEND PRx Cap (extended standard, send power receiver capabilities). This transmission may be acknowledged by the PTx with acknowledgement 258. Finally, there may be a further exchange in which the PRx sends one or more configuration packets, illustrated here by packet 260, XS: SEND CFGn (extended standard, send configuration n), with n being any of an essentially arbitrary number of packets required to exchange the required information. Each of these messages may be acknowledged by an acknowledgement message/packet 262. Upon culmination of the configuration exchange, power transfer in accordance with the enhanced standard may commence 264.
[0041] The foregoing message/packet exchange is exemplary. The extended standard (XS) communications may include more, fewer, or different message exchanges are required to establish power transfer in accordance with the various extensions of the underlying standard. Additionally, each message or packet may include various combinations of information necessary for the power contract negotiation between the receiver and transmitter. Additionally, although the illustrated process is shown as being driven by the receiver, in some embodiments, the transmitter (PTx) may determine various configuration parameters rather than relying on the receiver (PRx) to do so. Thus, the foregoing description should be considered as but one example of how to facilitate a transition from a standards-compliant wireless transfer mode to a wireless transfer mode that is based on an extension or enhancement to that standard.
[0042] Figure 3 illustrates a simplified decision tree/flow chart 300 describing the receiver-side (PRx) transition from a standards-compliant wireless power transfer mode to a wireless power transfer mode in accordance with an extension or enhancement of such a standard (e.g., at a frequency no specified in the base standard). The process begins with “Ping Phase 302” in which the PRx and PRx initiate communication. This ping phase may, for example, correspond to the message exchange depicted above in Fig. 2A, which generally corresponds to the ping phase defined by the Qi standard, or may be any other suitable standards-based exchange. From this point, the process proceeds to block 304 in which the receiver reports its identification and extended identification information, again in a way that complies with the base standard. As outlined above, the extended identification information packet prescribed by the standard may allow for communication of capabilities beyond the scope of the standard. In block 308, the PRx may report/acknowledge receipt of configuration packets received from the PTx. In block 310, the PRx may determine if the PTx is capable of operating in conjunction with one or more enhancements or extensions that are desired by the PRx. If not, the process may proceed to block 312, in which base mode power transfer in conjunction with the standard is provided. Otherwise, if the PTx provided an acknowledgement of the extended/enhanced capabilities requested by the PRx, the system may transition to negotiating the extended mode power transfer 314 as described above, followed by a transition to the enhanced/extended mode in block 316.
[0043] Figure 4 illustrates a simplified decision tree/flow chart 400 describing the transmitter-side (PTx) transition from a standards-compliant wireless power transfer mode to a wireless power transfer mode in accordance with an extension or enhancement of such a standard (e.g., at a frequency no specified in the base standard). The process begins with device detection 402, which may be provided by any number of sensors designed to detect that a PRx devices has been brought within range of the PTx. This leads to the digital ping stage 404 (corresponding to the Rx-side digital ping phase 302), discussed in greater detail above. Then, in block 406, the PTx receives an ID packet (406) and an XID packet (408) if expected based on the contents of the ID packet. All of these communications may be in compliance with an industry standard, as described above. In block 410, the PTx can determine whether an XID packet was received. If not, power transfer in the base mode (or a shutdown, as appropriate) may be entered (block 412). Alternatively, if an XID packet was received, the PTx may analyze the contents of the packet to determine whether the PRx is capable of operating in an enhanced/extended mode. If not, the PTx may transition to the base mode or disable power transfer (block 412). If so, the PTx may determine if the PRx has requested the base (standards-compliant mode) (block 416). If so, such mode may be entered. Alternatively, the PTx may receive the configuration phase packets (blocks 418/420), sent by the PRx in block 306 above. These packets may be acknowledged by the PTx (block 422) which may then determine (block 422) whether to restart and go to the ping phase or proceed to the extended/enhanced negotiation phase (block 426), corresponding to the receiver side negotiation phase in block 314.
[0044] Returning briefly to Fig. 2D, and as discussed above, after the negotiation phase during which the PRx and PTx agree to transition to a power transfer mode compliant with an extended/enhanced version of the standard that is different from the base standard (e.g, operating at a different frequency than those defined by the standard), the initially established standards power transfer may be disabled (block 238) before being reactivated in the extended/enhanced mode. In some embodiments, the exchange between PRx and PTx may include a delay before reactivation to allow time for NFC communication between PRx and PTx (e.g., as specified in the SRQ NFC block 228, discussed above). This delay may be provided because the power transfer can interfere with the NFC process, as they may use similar frequencies. Additionally the high power levels associated with wireless power transfer can, in some cases, cause damage to NFC equipment. Thus in the above-described negotiation process, the PRx and PTx can negotiate a time to allow for NFC scans.
[0045] The NFC communication may be used for any of a variety of purposes. For example, in some embodiments, the NFC communication may be used to provide PRx capabilities, properties, or parameters to the PTx, and vice-versa. These may be used to confirm the information provided in the various communications and negotiations described above. In other cases, the NFC communication may be used to provide information exchange that is not otherwise possible or feasible using the above-described techniques. In some embodiments, NFC communication may be used to read one or more NFC devices that are provided in either the PRx or PTx. These NFC tags may be used to perform additional functions, including but not limited to authentication, providing software/firmware updates delivered from PRx to PTx or vice-versa, confirmation of power parameters negotiated in the preceding stages, and the like.
[0046] Figure 5 illustrates a high level flowchart 500 of the NFC scan process. Beginning at block 502, the devices may perform their initial negotiation as described above, followed by a delay in power transfer (block 504) and NFS scan (506) as described above. The time period of the delay may be negotiated to account for the NFC functions to be performed. For example, relatively short tasks like authentication or confirmation of negotiated power transfer parameters may take a relatively short period of time. Alternatively, processes like firmware updates may take longer periods of time. The negotiated power transfer delay time may take these differences into account. Furthermore, if the devices originally specify a certain power transfer delay time period for the NFC scan, but during the subsequent NFC scan discover more devices that need to be read, they can negotiate for a subsequent, longer power transfer delay time period to allow sufficient time to scan all of the tags. For example, in block 508, it can be determined whether all NFC devices have been read. If so, power transfer may be enabled or reenabled (in accordance with the enhanced/extended power transfer mode) in block 510. Otherwise, the devices may negotiate a longer power transfer delay (block 512) to allow for further NFC scanning.
[0047] In addition to the foregoing, there may be some cases in which it is desirable to simplify the above-described negotiation process. As one example, a PRx device may have a dead battery, rendering it difficult or impossible to engage in a more protracted power contract negotiation process. In that case, the PRx device may indicate its preferred frequency in the XID packet described above with respect to Fig. 2A, element 206. Recall that, as described above, the XID packet was used to inform the PTx that the device was capable of various enhanced extra- standard power transfer modes. Instead, in this particular example, the PRx simply provides a pref erred/ desired power parameter (such as frequency of operation) and the PTx device will honor that, if possible.
[0048] Figure 6 illustrates a high level flow chart of a power negotiation process 600 for extended or enhanced charging mode that remains compliant. The process may take place on either both devices as described more specifically above. The process can begin with initiating a standards- based negotiation in block 602. This negotiation may take place using standards-compliant mechanisms to ensure interoperability with devices that do not support the desired enhanced or extended capabilities. In some embodiments, these standards-compliant mechanisms may be provided by the Wireless Power Consortium Qi standard, or any other suitable wireless power transfer standard. However, in block 604, a standards-compliant mechanism may be used to signal enhanced capabilities. In some embodiments, this may include the “XID” (extended identification) packets provided for in the Qi standard and may optionally include additional mechanisms for exchanging the required information. In other embodiments, other standards- compliant mechanisms may be used as appropriate for a different version of the standard, or a different standard entirely. In block 606, the devices may determine whether both devices are capable of operation in compliance with the desired enhanced or extended modes or capabilities. If not, then the devices may proceed to operate in the standards-compliant mode, in which case wireless power transfer may take place according to the relevant standard (block 608).
[0049] Otherwise, if in block 606 it is determined that the devices are capable of operating in extended/enhanced modes beyond what is specified in the standard, the devices may negotiate a transition to a desired extended enhanced mode (block 610). These extended or enhanced modes may provide for power transfer in a way that is not compliant with the base standard, including, for example, operation at different frequencies, different voltages, different power levels, etc. Once an agreed enhanced or extended mode is agreed, then the devices may transition to and operate in accordance with this agreed enhanced or extended mode (block 612).
[0050] The foregoing describes exemplary embodiments of wireless power transfer systems that are able to negotiate enhanced/extended operating modes while remaining compliant with wireless power transfer standards that do not support such enhanced/extended operating modes. Such systems may be used in a variety of applications but may be particularly advantageous when used in conjunction with personal electronic devices such as mobile computing devices (e.g., laptop computers, tablet computers, smart phones, and the like) and their accessories (e.g., wireless earphones, styluses and other input devices, etc.) as well as wireless charging accessories (e.g., charging mats, pads, stands, etc.) Although numerous specific features and various embodiments have been described, it is to be understood that, unless otherwise noted as being mutually exclusive, the various features and embodiments may be combined various permutations in a particular implementation. Thus, the various embodiments described above are provided by way of illustration only and should not be constructed to limit the scope of the disclosure. Various modifications and changes can be made to the principles and embodiments herein without departing from the scope of the disclosure and without departing from the scope of the claims.
[0051] The foregoing describes exemplary embodiments of wireless power transfer systems that are able to transmit certain information amongst the PTx and PRx in the system. The present disclosure contemplates this passage of information improves the devices’ ability to provide wireless power signals to each other in an efficient and non-damaging manner to facilitate battery charging. It is contemplated some implementers of the present technology may consider the passage of identifiers, such as serial numbers, UIDs, manufacturer IDs, MAC addresses, or the like, to aide in the identification of PTx’ s and PRx’s, particularly their wireless capabilities, to one another.

中文:
[0001]无线电力传输(“WPT”),有时也被称为感应电力传输(“IPT”),近来在许多应用中变得更加普遍。其中WPT/IPT的使用增加的一个应用是围绕诸如移动电话(即,智能电话)和其附件(例如,无线耳机、智能手表等)以及平板电脑和其他类型的便携式计算机和其附件(例如,手写笔等)的设备的消费电子产品空间。
[0002]在一些实施方案中,无线电力接收器能够以符合标准的方式与电力发射器协商,从而以超出标准范围的方式进行操作。
[0003]一种无线电力接收器可包括:接收器线圈,该接收器线圈被配置为从无线电力发射器接收电力;整流器,该整流器耦接到该接收器线圈并被配置为将跨该接收器线圈出现的AC电压转换为递送到负载的DC电压;和控制和通信模块,该控制和通信模块耦接到该接收器线圈和该整流器。该控制器和通信模块可被进一步配置为经由该接收器线圈从该无线电力发射器接收带内通信信号;以及操作该整流器以生成经由该接收器线圈递送到该电力发射器的带内通信信号。该带内通信信号可包括协商到增强或扩展操作模式的转变的符合标准通信协议的通信。该增强或扩展操作模式可包括以与该标准通信协议所规定的频率或功率电平不同的频率和功率电平中的一者或多者进行操作。
[0006]该无线电力发射器还可包括NFC通信模块,该NFC通信模块耦接到该控制和通信模块。在此情况下,该增强或扩展操作模式包括延迟无线电力传输以允许与该无线电力接收器中的对应NFC通信模块的NFC通信。协商到增强或扩展操作模式的转变的符合标准通信协议的该通信可包括指示该发射器的一个或多个增强能力的通信。协商到增强或扩展操作模式的转变的符合标准通信协议的该通信还可包括请求该接收器的一个或多个增强能力的通信。协商到增强或扩展操作模式的转变的符合标准通信协议的该通信还可进一步包括确认该接收器的一个或多个增强能力的通信。协商到增强或扩展操作模式的转变的符合标准通信协议的该通信还可包括与该发射器和该接收器中的至少一者的用户界面能力相关的通信。
[0007]一种协商无线电力发射器或无线电力接收器与配对设备之间的无线电力传输的方法可包括:使用标准通信协议来发起与该配对设备的通信;使用该标准通信协议向该配对设备传送该设备的一个或多个增强能力;以及确定该配对设备是否也能够根据该一个或多个增强能力中的每一者进行操作。如果该配对设备不能够根据该增强能力中的一者或多者进行操作,则该方法还可包括以标准模式进行操作。另选地,如果该配对设备能够根据该增强能力中的一者或多者进行操作,则该方法还可包括协商到包括该增强能力中的一者或多者的约定增强模式的转变。该设备与其配对设备之间的该通信可以是带内通信或带外通信。该增强能力可包括以与该标准通信协议所规定的频率或功率电平不同的频率或功率电平进行操作的能力。该增强能力可包括NFC通信能力并且该增强模式包括延迟无线电力传输以允许NFC通信。该增强能力还可包括该发射器或接收器设备的用户界面能力,在该情况下,该约定增强模式可包括关于哪个设备将向用户提供关于无线电力传输的状态的信息的该设备与其配对设备之间的约定。
[0008]图1示出了无线电力传输系统。
[0009]图2A至图2E示出了在增强/扩展无线电力传输模式中操作的无线电力传输协商。
[0010]图3示出了用于增强/扩展无线电力传输模式的接收器侧协商的流程图。
[0011]图4示出了用于增强/扩展无线电力传输模式的发射器侧协商的流程图。
[0012]图5示出了与增强/扩展无线电力传输模式相关联的NFC扫描过程的流程图。
[0013]图6示出了在增强/扩展无线电力传输模式中操作的电力传输协商的高级流程图。
[0014]在以下描述中,为了解释的目的,阐述了很多具体细节以便提供对所公开构思的彻底理解。作为该描述的一部分,为了简单起见,本公开的附图中的一些附图以框图形式表示结构和设备。为了清晰起见,在本公开中未描述实际具体实施的所有特征。此外,本公开中使用的语言是出于可读性和指导目的而选择的,尚未选择它来描绘或限制所公开的主题。相反,所附权利要求旨在用于此目的。
[0015]所公开的概念的各种实施方案以举例的方式进行说明,而不仅限于各个附图,在附图中类似的附图标号指示类似的元件。为简单和清楚说明起见,在合适的情况下,在不同附图中重复参考标号以指示对应或类似的元件。此外,示出许多具体细节以便提供对本文所述的具体实施的充分理解。在其他情况下,未详细描述方法、规程和部件以免模糊所描述的相关功能。在本公开中提到“一个”、“一种”或“另一种”实施方案未必是相同或不同的实施方案,并且这意味着至少一个。给定附图可用于示出本公开的多于一个实施方案或多于一个种类的特征,并且对于给定的实施方案或种类可能不需要附图中的所有元件。当在给定附图中提供时,参考标号在整个若干附图中是指相同的元件,但其可以不在每个附图中重复。除非另外指明,否则附图未按比例绘制,并且某些部件的比例可被放大以更好地示出本公开的细节和特征。
[0016]图1示出了无线电力传输系统100的简化框图。无线电力传输系统包括经由感应耦接130将电力无线传输到电力接收器(PRx)120的电力发射器(PTx)110。电力发射器110可接收由逆变器114转换成具有特定电压和频率特性的AC电压的输入电力。逆变器114可由控制器/通信模块116控制,该控制器/通信模块如下进一步描述的那样操作。在各种实施方案中,逆变器控制器和通信模块可在公共系统(诸如基于微处理器、微控制器等的系统)中实现。在其他实施方案中,逆变器控制器可由其间具有通信装置的单独控制器模块和通信模块实现。逆变器114可使用任何合适的电路拓扑(例如,全桥、半桥等)来构造并且可使用任何合适的半导体开关器件技术(例如使用硅、碳化硅或氮化镓器件制造的MOSFET、IGBT等)来实现。
[0017]逆变器114可将所生成的AC电压递送到发射器线圈112。除了允许磁耦接到接收器的无线线圈之外,图1所示的发射器线圈块112可包括调谐电路(诸如附加电感器和电容器),该调谐电路促进发射器在不同状况(诸如到接收器的不同程度的磁耦接、不同操作频率等)下的操作。无线线圈本身可以各种不同方式构造。在一些实施方案中,无线线圈可被形成为围绕合适线轴的导线绕组。在其他实施方案中,无线线圈可被形成为印刷电路板上的迹线。其他布置也是可能的且可结合本文中描述的各种实施方案使用。无线发射器线圈还可包括磁性可渗透材料(例如,铁氧体)芯,其被配置为以适合于特定应用的方式影响线圈的通量图案。本文中的教导内容可结合适于给定应用的各种发射器线圈布置中的任一者应用。
[0018]PTx控制器/通信模块116可监测发射器线圈并且使用从其导出的信息来控制逆变器114以适于给定情况。例如,控制器/通信模块可被配置为取决于特定应用致使逆变器114在给定频率或输出电压下操作。在一些实施方案中,控制器/通信模块可被配置为从PRx设备接收信息并且相应地控制逆变器114。此信息可经由电力输送线圈(即带内通信)接收或可经由单独通信信道(未示出,即带外通信)接收。对于带内通信,控制器/通信模块116可检测和解码由PRx施加在磁链路上的信号(诸如电压、频率或负载变化)以接收信息,并且可指示逆变器通过操纵各种参数(诸如电压、频率、相位等)来调制所递送的电力以向PRx发送信息。在一些实施方案中,控制器/通信模块可被配置为采用频移键控(FSK)通信以向PRx传送数据,在该FSK通信中逆变器信号的频率被调制。控制器/通信模块116可被配置为检测来自PRx的幅移键控(ASK)通信或基于负载调制的通信。在任一情况下,控制器/通信模块126可被配置为改变在接收器侧上汲取的电流以操纵在Tx线圈上看到的波形,从而将信息从PRx递送到PTx。对于带外通信,可提供允许PTx与PRx之间的通信的附加模块,例如WiFi、蓝牙、或其他无线电链路、或任何其他合适的通信信道。
[0019]如上所述,控制器/通信模块116可以是例如设置在单个集成电路上的单个模块,或者可由设置在不同集成电路上的多个模块/设备或者具有模拟部件和数字部件的集成电路和分立电路的组合来构造。本文中的教导内容不限于控制器/通信电路的任何特定布置。
[0020]PTx设备110可任选地包括其他系统和部件,诸如近场通信(“NFC”)模块118。在一些实施方案中,NFC模块118可经由电力传输线圈与PRx中的对应模块或射频标识(RFID)标签通信。在其他实施方案中,NFC模块118可使用单独物理信道138与对应模块或标签通信。在一些实施方案中,如下文更详细描述,可能有必要暂停感应电力传输以防止干扰NFC通信。
[0021]如上文所提及,无线电力传输系统还包括无线电力接收器(PRx)120。无线电力接收器可包括可磁性耦接130到发射器线圈112的接收器线圈122。如同上文所讨论的发射器线圈112,图1所示的接收器线圈块122可包括调谐电路(诸如附加电感器和电容器),该调谐电路促进发射器在不同状况(诸如到接收器的不同程度的磁耦接、不同操作频率等)下的操作。无线线圈本身可以各种不同方式构造。在一些实施方案中,无线线圈可被形成为围绕合适线轴的导线绕组。在其他实施方案中,无线线圈可被形成为印刷电路板上的迹线。其他布置也是可能的且可结合本文中描述的各种实施方案使用。无线接收器线圈还可包括磁性可渗透材料(例如,铁氧体)芯,其被配置为以适合于特定应用的方式影响线圈的通量图案。本文中的教导内容可结合适于给定应用的各种接收器线圈布置中的任一者应用。
[0022]接收器线圈122输出经由发射器线圈112通过磁感应在其中感应出的AC电压。该输出AC电压可被提供给整流器124,该整流器向与PRx设备相关联的一个或多个负载提供DC输出电力。整流器124可由控制器/通信模块126控制,该控制器/通信模块如下进一步描述的那样操作。在各种实施方案中,整流器控制器和通信模块可在公共系统(诸如基于微处理器、微控制器等的系统)中实现。在其他实施方案中,整流器控制器可由其间具有通信装置的单独控制器模块和通信模块实现。整流器124可使用任何合适的电路拓扑(例如,全桥、半桥等)来构造并且可使用任何合适的半导体开关器件技术(例如使用硅、碳化硅或氮化镓器件制造的MOSFET、IGBT等)来实现。
[0023]PRx控制器/通信模块126可监测接收器线圈并且使用从其导出的信息来控制整流器124以适于给定情况。例如,控制器/通信模块可被配置为取决于特定应用致使整流器124提供给定输出电压。在一些实施方案中,控制器/通信模块可被配置为向PTx设备发送信息以有效地控制递送给接收器的电力。此信息可经由电力输送线圈(即带内通信)发送或可经由单独通信信道(未示出,即带外通信)发送。对于带内通信,控制器/通信模块126可例如调制所接收的电力的负载电流或其他电参数以将信息发送到PTx。在一些实施方案中,控制器/通信模块126可被配置为检测和解码由PTx施加在磁链路上的信号(诸如电压、频率或负载变化)以从PTx接收信息。在一些实施方案中,控制器/通信模块126可被配置为接收频移键控(FSK)通信以向PRx传送数据,在该FSK通信中逆变器信号的频率已经被调制。控制器/通信模块126可被配置为生成来自PRx的幅移键控(ASK)通信或基于负载调制的通信。在任一情况下,控制器/通信模块126可被配置为改变在接收器侧上汲取的电流以操纵在Tx线圈上看到的波形,从而将信息从PRx递送到PTx。对于带外通信,可提供允许PTx与PRx之间的通信的附加模块,例如WiFi、蓝牙、或其他无线电链路、或任何其他合适的通信信道。
[0024]如上所述,控制器/通信模块126可以是例如设置在单个集成电路上的单个模块,或者可由设置在不同集成电路上的多个模块/设备或者具有模拟部件和数字部件的集成电路和分立电路的组合来构造。本文中的教导内容不限于控制器/通信电路的任何特定布置。
[0025]PRx设备120可任选地包括其他系统和部件,诸如近场通信(“NFC”)模块128。在一些实施方案中,NFC模块128可经由电力传输线圈与PTx中的对应模块或射频标识(RFID)标签通信。在其他实施方案中,NFC模块128可使用单独物理信道138与对应模块或标签通信。在一些实施方案中,如下文更详细描述,可能有必要暂停感应电力传输以防止干扰NFC通信。
[0026]以上描述的无线电力输送系统100的许多变化和增强是可能的,并且以下教导内容适用于此类变化和增强中的任一者。
[0027]如上所述,PRx控制器/通信模块126和PTx控制器/通信模块126可彼此通信以分别向彼此标识其自身并且协商它们之间的电力递送。此标识和协商过程可结合标准定义的协议(诸如由无线电力联盟Qi标准定义的协议)进行,使得来自不同制造商的设备可互操作。符合此类标准以专业化的潜在代价提供了互操作性的益处。在其他实施方案中,标识和协商过程可结合由设备的制造商确定的专有协议来进行,这提供了改进灵活性和潜在扩展性能的益处,缺点在于失去与不实现专有协议的设备的互操作性。
[0028]为了解决这个难题,控制器/通信模块可被配置为根据标准定义协议来发起协商过程。在该协商的过程中,一个设备、另一设备或两个设备可以符合标准的方式将其自身标识为支持超出标准范围的增强能力集。如果两个设备都能够根据该增强能力集进行操作,则设备可选择根据该增强能力集进行操作。否则,设备可选择结合基于标准的能力集来操作。在一个实施方案中,增强能力集可包括以不同频率、以不同功率电平或以超出现有标准中定义的方式的其他方式操作的能力。
[0029]图2A至图2H示出了用于从第一通信协议体系迁移到第二体系的无线电力接收器(PRx)120与无线电力发射器(PTx)110之间的示例性通信交换,该第二体系包括特定于该第二体系的一或多个增强。在一些示例中,第一协议体系是基于标准的体系,诸如Qi。第二体系中的增强可以是标准的扩展版本或增强版本(诸如后面版本或另选版本)或者可以是完全分离且专有的系统。所描述的各种通信分组可采用各种形式中的任一者,从而采用不同的分组结构、用于传送分组的不同调制方案等。以下描述以高级别说明了通信分组的部件,但将了解的是,任何特定协议具体实施可指定视情况可包括于这些分组中的不同或附加数据。
[0030]参考图2A,示例性协商过程开始于PRx 120向电力发射器110发送消息202-208的序列。此交换可由PRx检测到其接近PTx而触发,如通常在无线电力传输系统中实现的那样。交换可使用带内通信以标准所指定的频率进行。在一些实施方案中,此频率可介于约100kHz与约250kHz之间。在一些实施方案中,该频率可以是128kHz。在所示示例中,四个消息202-208对应于根据Qi标准发送的消息;然而,在一些实施方案中,可存在更多或更少的消息,并且它们可符合另选标准或协议。
[0031]第一消息202可以是SIG分组,即根据Qi标准的信号强度分组。第二消息204可以是ID分组,即根据Qi标准的标识分组。第三消息206可以是XID,即根据Qi标准的扩展标识分组。第四消息208可以是CFG分组,即根据Qi标准的配置分组。在一些实施方案中,这四个分组可对应于根据Qi标准的“查验”和“配置阶段”。这些分组的细节(包括其中包含的信息以及此类分组在系统中的效果)在它们所属的Qi标准版本中详细描述,并且因此这里不再重复。应当理解,Qi标准的各种版本可并入此类分组的不同版本,并且稍后版本可组合、消除或以其他方式改变此类分组。因此,这里提供所示分组仅作为符合标准的初始化的示例,并且也可使用其他类似的布置。
[0032]在上述通信中感兴趣的是XID分组。在Qi标准中,该任选分组可用于提供PRx和PTx之间的附加信息交换。此附加信息交换可包括增强能力的标识,诸如根据对标准或其他超标准(即,超出标准的范围)操作模式的扩展或增强来执行的能力。本文描述的标准中未指定的这些性能模式被称为超标准(“XS”)。因此,在从PRx接收到其能够根据对标准的扩展或增强来执行的通信时,PTx可发送响应分组210,该响应分组是XS ACK,即PRx的超标准能力的确认。
[0033]现在转到图2B,示出了PRx和PTx之间的进一步通信。在从PTx接收到对PRx增强(XS)能力的确认时,PRx可发送请求PTx提供其增强能力(如果有的话)的另一分组212。这可采取“GET”请求的形式,其中PRx请求PTx以XS XID分组(即超出基本标准范围并且提供PTx能够提供的超出标准的哪些额外能力的分组)的形式发送其增强能力(如果有的话)。该分组可提供超出PTx可提供的基本标准的范围的各种特征的指示,诸如不同电力传输参数(电压、功率电平、操作频率等)以及在增强(XS)模式中操作所必需的与PTx相关的一个或多个参数。
[0034]作为示例,PTx可指示其能够以超出基本标准中定义的频率的不同频率进行操作。在一些情况下,PRx可被配置为优选以该不同频率(如果可用的话)操作,例如以避免对其他设备或系统的潜在干扰。因此,PRx可发起一系列通信以从符合当前标准的操作频率转变到不同的、超标准频率。作为该通信过程的一部分,PRx还可尝试交换关于电力传输的其他信息,包括用户界面(UI相关信息)和与其他设备系统(诸如上述NFC系统)相关的信息。为此,图2B所示的通信可继续PRx请求UI相关参数(消息216)并且PTx报告所请求的UI相关参数(消息218)。
[0035]作为示例,可能期望向用户提供指示无线电力传输系统的状态或状况的反馈。例如,可能有用的是提供成功或不成功的电力传输布置的视觉指示(诸如LED或彩色LED)或音频通知(诸如哔哔声或钟声)。取决于所使用的特定设备,PTx或PRx可具有或可不具有某些可用UI类型。例如,充电垫可具有状态LED,但可不具有允许其再现钟声的扬声器。诸如智能电话的其他设备可以能够提供音频和视觉指示符。类似地,其他设备(诸如充电盒)可具有有限的UI能力。因此,为了向用户提供期望水平的反馈,设备可能需要在它们之间协商以确定哪个设备具有向用户提供期望反馈的能力。
[0036]在所示的实施方案中,PRx决定哪个设备将提供所需的用户反馈。现在转到图2C,PRx可传送其关于将如何处理各种用户界面问题的确定,该确定由其自身能力以及在其XID分组中从PTx接收的能力通知。这可通过SRQ UI(特殊请求-用户界面)分组220传送到PRx。PTx可确认该请求/指令(ACK分组222)并且这两个设备可相应地继续。类似地,PRx可经由SRQ频率分组224(特殊请求-频率)指示期望的操作频率。PTx可确认该请求/指令(ACK分组224)并且这两个设备可相应地继续以不同频率操作,如以下更详细地描述的。另外,PRx可使用SRQ NFC(特殊请求-NFC)分组228以请求某些NFC参数。这些可包括例如作为以默认/标准频率去激活当前电力和通信交换与以分组224中请求的任选频率重新激活功率和通信交换之间的延迟,允许NFC扫描发生,如以下更详细描述的。PTx可确认该请求/指令(ACK分组230)并且这两个设备可相应地继续。最后,PRX可提供伴随增强/扩展协议的附加特殊请求或者可通过SRQ End(特殊请求-结束)分组232指示特殊请求的结束。PTx可确认该请求/指令(ACK分组234)并且这两个设备可相应地继续例如转变到新频率、提供期望的UI交互、以及允许如前述交换中约定的NFC操作。
[0037]现在转到图2D,PRx可根据原始标准(例如,Qi标准)发送EPT(结束电力传输)分组236。应当理解,取决于所使用的特定标准和版本,该分组可以是不同的;然而,该指令的点(以及当前电力/数据交换体系的结束)是从根据原始电力传输标准的操作(例如,以标准定义频率)转变到根据如在先前交换中协商的增强/扩展标准的电力传输(例如,以不根据原始标准而是根据增强标准的不同频率)。因此,电力传输被禁用(238),这也可允许执行NFC扫描的时间,如果协商的话(240)。应当注意,更一般而言,可利用其他类型的带外通信,诸如蓝牙和RFID通信。下文讨论了此带外通信(在此示例中为NFC扫描)的进一步细节。
[0038]在禁用电力传输238和任选NFC扫描240(或在协商的延迟期间发生的其他活动)之后,电力传输可以增强模式(例如,以不同频率)重新发起,开始于消息交换242-248。在一些实施方案中,增强模式中的该重新发起响应于在任选带外通信时段(例如,NFC扫描240)期间的PTx和PRx之间的成功通信。在所示的实施方案中,这开始于PRX发送一系列符合扩展或增强标准(“XS”)的消息,这些消息本来与对应于最初进行的符合标准的发起或“查验”的基本模式相匹配。如前所述,交换可使用带内通信以扩展或增强标准所指定的频率进行。在一些实施方案中,此频率可介于约360kHz,但可使用其他频率。
[0039]在所示的示例交换中,第一消息242可以是XS:SIG分组,即根据扩展标准的信号强度分组。第二消息244可以是XS:ID分组,即根据扩展标准的标识分组。第三消息246可以是XS:XID,即根据扩展标准的扩展标识分组。第四消息248可以是XS:CFG分组,即根据扩展标准的配置分组。在一些实施方案中,这四个分组可对应于通常与Qi标准并行的“查验”和“配置阶段”。在其他实施方案中,交换可包括更多或更少的消息,并且可以是完全唯一的或者可一般地与其他基于标准的通信协议并行。因此,这里提供所示的分组仅作为查验或初始化规程的示例,并且也可使用其他类似的布置。在一些实施方案中,该查验或初始化规程可用于确认在以上描述的先前特殊请求交换中协商的参数。
[0040]现在转到图2E,根据增强标准(例如,以不同频率)建立电力传输可需要接收器与发射器之间的进一步信息交换。因此,PRx可使用消息/分组252XS:GET PTx XID(即,扩展标准,获取电力发射器扩展标识信息)来请求PTx的扩展标识信息。作为响应,PTx可经由消息/分组254PTx XID提供所请求的信息。PRx还可使用消息256XS:SEND PRx Cap(扩展标准,发送电力接收器能力)向PTX提供其自身能力的指示。该输送可由PTx通过确认258来确认。最后,可存在进一步交换,其中PRx发送一个或多个配置分组,这里由分组260XS:SEND CFGn(扩展标准,发送配置n)示出,其中n是交换所需信息所需要的基本上任意数量的分组中的任一者。这些消息中的每一者可由确认消息/分组262确认。在配置交换的顶点之后,可开始264根据增强标准的电力传输。
[0041]前述消息/分组交换是示例性的。扩展标准(XS)通信可包括需要更多、更少或不同的消息交换以根据基础标准的各种扩展来建立电力传输。另外,每个消息或分组可包括接收器与发射器之间的电力合同协商所必需的信息的各种组合。另外,虽然所示出的过程被示为由接收器驱动,但在一些实施方案中,发射器(PTx)可确定各种配置参数而不是依赖于接收器(PRx)来这样做。因此,前述描述应被视为仅是如何促进从符合标准的无线传输模式到基于对该标准的扩展或增强的无线传输模式的转变的一个示例。
[0042]图3示出了简化决策树/流程图300,其描述接收器侧(PRx)从符合标准的无线电力传输模式到根据此标准的扩展或增强的无线电力传输模式(例如,以基本标准中未指定的频率)的转变。过程开始于“查验阶段302”,其中PRx和PRx发起通信。该查验阶段可例如对应于以上在图2A中描绘的消息交换,该消息交换一般对应于由Qi标准定义的查验阶段,或者可以是任何其他合适的基于标准的交换。从这一点开始,过程行进到框304,其中接收器再次以符合基本标准的方式报告其标识和扩展标识信息。如上所概述,由标准规定的扩展标识信息分组可允许传送超出标准范围的能力。在框308中,PRx可报告/确认接收到从PTx接收的配置分组。在框310中,PRx可确定PTx是否能够结合PRx所期望的一个或多个增强或扩展来操作。如果不是,则过程可行进到框312,其中提供结合标准的基本模式电力传输。否则,如果PTx提供了PRx所请求的扩展/增强能力的确认,则系统可转变到协商如上所述的扩展模式电力传输314,随后在框316中转变到增强/扩展模式。
[0043]图4示出了简化决策树/流程图400,其描述发射器侧(PTx)从符合标准的无线电力传输模式到根据此标准的扩展或增强的无线电力传输模式(例如,以基本标准中未指定的频率)的转变。过程开始于设备检测402,其可由被设计成检测PRx设备已被带入PTx的范围内的任何数量的传感器提供。这导致数字查验阶段404(对应于Rx侧数字查验阶段302),如以上更详细讨论的。然后,在框406中,PTx接收ID分组(406)和XID分组(408)(如果基于ID分组的内容预期的话)。如上所述,所有这些通信可符合工业标准。在框410中,PTx可确定是否接收到XID分组。如果不是,则可进入以基本模式的电力传输(或关机,视情况而定)(框412)。另选地,如果接收到XID分组,则PTx可分析分组的内容以确定PRx是否能够以增强/扩展模式操作。如果否,则PTx可转变到基本模式或禁用电力传输(框412)。如果是,则PTx可确定PRx是否已经请求了基本模式(符合标准的模式)(框416)。如果是,则可进入此模式。另选地,PTx可接收以上由PRx在框306中发送的配置阶段分组(框418/420)。这些分组可由PTx确认(框422),PTx然后可确定(框422)是重新启动并进入查验阶段还是行进到扩展/增强协商阶段(框426),其对应于框314中的接收器侧协商阶段。
[0044]暂时返回到图2D,并且如上所讨论,在PRx和PTx约定转变到符合与基本标准不同的标准的扩展/增强版本的电力传输模式(例如,以与基本标准所定义的频率不同的频率操作)的协商阶段之后,可在以扩展/增强模式重新激活之前禁用初始建立的标准电力传输(框238)。在一些实施方案中,PRx与PTx之间的交换可包括在重新激活之前的延迟以允许在PRx与PTx之间进行NFC通信的时间(例如,如以上讨论的SRQ NFC框228中指定的)。可提供此延迟,因为电力传输可干扰NFC过程(这是因为它们可使用类似频率)。另外,在一些情况下,与无线电力传输相关联的高功率电平可导致对NFC装备的损坏。因此,在上述协商过程中,PRx和PTx可协商用于允许NFC扫描的时间。
[0045]NFC通信可用于各种目的中的任一者。例如,在一些实施方案中,NFC通信可用于向PTx提供PRx能力、属性或参数,并且反之亦然。这些可用于确认在以上描述的各种通信和协商中提供的信息。在其他情况下,NFC通信可用于提供使用上述技术本来不可能或不可行的信息交换。在一些实施方案中,NFC通信可用于读取在PRx或PTx中提供的一个或多个NFC设备。这些NFC标签可用于执行附加功能,包括但不限于认证、提供从PRx递送到PTx或从PTx递送到PRx的软件/固件更新、确认在先前阶段中协商的功率参数等。
[0046]图5示出了NFC扫描过程的高级流程图500。在框502处开始,设备可执行如上文所描述的其初始协商,随后是如上文所描述的电力传输延迟(504)和NFS扫描(506)。可协商延迟的时间段以考虑要执行的NFC功能。例如,相对短的任务(类似协商的电力传输参数的认证或确认)可花费相对短的时间段。另选地,类似固件更新的过程可能花费较长的时间段。协商的电力传输延迟时间可考虑这些差异。此外,如果设备最初指定用于NFC扫描的特定电力传输延迟时间段,但在后续NFC扫描期间发现需要读取的更多设备,则其可协商用于允许足够时间来扫描所有标签的后续较长电力传输延迟时间段。例如,在框508中,可确定是否已读取所有NFC设备。如果是,则可在框510中启用或重新启用电力传输(根据增强/扩展电力传输模式)。否则,设备可协商较长电力传输延迟(框512)以允许进一步NFC扫描。
[0047]除了前述情况之外,可存在其中期望简化上述协商处理的一些情况。作为一个示例,PRx设备可具有耗尽电池,从而使得难以或不可能参与较长时间的电力合同协商过程。在该情况下,PRx设备可在以上相对于图2A描述的XID分组(元素206)中指示其优选频率。回想一下,如上所述,XID分组用于向PTx通知该设备能够进行各种增强的超标准电力传输模式。相反,在该特定示例中,PRx简单地提供优选/期望的功率参数(诸如操作频率),并且如果可能的话,PTx设备将履行该参数。
[0048]图6示出了保持符合的扩展或增强充电模式的电力协商过程600的高级流程图。过程可在以上更具体描述的两个设备中的任一个上进行。过程可开始于在框602中发起基于标准的协商。该协商可使用符合标准的机制来进行以确保与不支持期望的增强或扩展能力的设备的互操作性。在一些实施方案中,这些符合标准的机制可由无线电力联盟Qi标准或任何其他合适的无线电力传输标准提供。然而,在框604中,可使用符合标准的机制来发信号通知增强的能力。在一些实施方案中,这可包括在Qi标准中提供的“XID”(扩展标识)分组并且可任选地包括用于交换所需信息的附加机制。在其他实施方案中,其他符合标准的机制可适当地用于不同版本的标准,或者完全不同的标准。在框606中,设备可确定两个设备是否均能够进行符合期望的增强或扩展模式或能力的操作。如果否,则设备可继续以符合标准的模式操作,在此情况下,可根据相关标准进行无线电力传输(框608)。
[0049]否则,如果在框606中确定设备能够以超出标准中指定的模式的扩展/增强模式操作,则设备可协商到期望的扩展增强模式的转变(框610)。这些扩展或增强模式可以不符合基本标准的方式提供电力传输,包括例如以不同频率、不同电压、不同功率电平等的操作。一旦约定增强或扩展模式被约定,则设备可转变到该约定增强或扩展模式并且根据其进行操作(框612)。
[0050]前面描述了无线电力传输系统的示例性实施方案,该无线电力传输系统能够协商增强/扩展操作模式,同时保持符合不支持此类增强/扩展操作模式的无线电力传输标准。此类系统可用于多种应用,但当结合个人电子设备诸如移动计算设备(例如,膝上型计算机、平板计算机、智能电话等)和其附件(例如,无线耳机、手写笔和其他输入设备等)以及无线充电附件(例如,充电垫、垫板、支架等)使用时,可尤其有利。尽管已经描述了许多特定特征和各种实施方案,但应当理解,除非另外指出是相互排斥的,否则各种特征和实施方案可在特定具体实施中组合成各种排列。因此,上文描述的各种实施例仅仅以举例方式提供,而不应解释为限制本公开的范围。在不脱离本公开的范围和不脱离权利要求的范围的情况下,可以对本文的原理和实施方案进行各种修改和改变。
[0051]前面描述了能够在系统中的PTx和PRx之间输送某些信息的无线电力传输系统的示例性实施方案。本公开预期此信息传递改进了设备以有效且非破坏性方式向彼此提供无线电力信号以促进电池充电的能力。可预期的是,本技术的一些实施者可考虑标识符(诸如序列号、UID、制造商ID、MAC地址等)的传递以帮助PTx和PRx(特别是它们的无线能力)相对于彼此的标识。