Source: https://patents.google.com/patent/JP6517689B2/en
Timestamp: 2019-09-22 02:09:36
Document Index: 791045216

Matched Legal Cases: ['art 1300', 'art 1300', 'art 1300', 'art 1500', 'art 1500', 'art 1500']

JP6517689B2 - System and method for wireless power control communication using Bluetooth (R) Low Energy - Google Patents
System and method for wireless power control communication using Bluetooth (R) Low Energy Download PDF
JP6517689B2
JP6517689B2 JP2015504621A JP2015504621A JP6517689B2 JP 6517689 B2 JP6517689 B2 JP 6517689B2 JP 2015504621 A JP2015504621 A JP 2015504621A JP 2015504621 A JP2015504621 A JP 2015504621A JP 6517689 B2 JP6517689 B2 JP 6517689B2
JP2015504621A
JP2015515851A5 (en
JP2015515851A (en
2013-03-26 Application filed by クアルコム，インコーポレイテッド filed Critical クアルコム，インコーポレイテッド
2015-05-28 Publication of JP2015515851A publication Critical patent/JP2015515851A/en
2016-12-28 Publication of JP2015515851A5 publication Critical patent/JP2015515851A5/ja
2019-05-22 Publication of JP6517689B2 publication Critical patent/JP6517689B2/en
The present invention relates generally to wireless power. More specifically, the present disclosure is directed to establishing a connection between wireless charging and a charging device using Bluetooth® Low Energy.
An increasing number of different electronic devices are powered via rechargeable batteries. Such devices include mobile phones, portable music players, laptop computers, tablet computers, computer peripheral devices, communication devices (eg, Bluetooth devices), digital cameras, hearing aids and the like. Although battery technology has improved, battery powered electronic devices increasingly require more power and consume it, thereby often requiring recharging. Rechargeable devices are often charged via a wired connection through a cable or other similar connection physically connected to a power source. Cables and similar connections may in some cases be inconvenient or cumbersome and have other disadvantages. A wireless charging system capable of transferring power in free space to be used to charge a rechargeable electronic device or to power an electronic device is some of the drawbacks of wired charging solutions There is a possibility to overcome. Accordingly, wireless power transfer systems and methods that efficiently and safely transfer power to electronic devices are desirable.
Each of the various implementations of the systems, methods, and devices within the scope of the appended claims has several aspects, any of which is solely responsible for the desirable attributes described herein. There is no. Several salient features are described herein without limiting the scope of the appended claims.
The details of one or more implementations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. It should be noted that the relative dimensions of the following figures may not be drawn to scale.
One aspect of the present disclosure provides a wireless charger for connecting to a charging device via a wireless communication network. The wireless charger includes a transmitter configured to transmit a power signal. The wireless charger further includes a device scanner configured to scan for one or more connection solicitations sent by the device. The wireless charger further includes a receiver configured to receive the connection request from the charging device via the wireless communication network in response to the transmitted power signal. The transmitter may be configured to transmit a connection request to establish a connection with the charging device in response to the received connection request.
Another aspect of the present disclosure provides a method for wirelessly connecting to a charging device via a wireless communication network. The method includes the step of transmitting a power signal. The method further includes the step of scanning for one or more connection requests sent by the device. The method further includes receiving a connection request from the charging device via the wireless communication network in response to the transmitted power signal. The method further includes transmitting a connection request to establish a connection with the charging device in response to the received connection request.
Another aspect of the present disclosure provides an apparatus for connecting with a charging device via a wireless communication network. The apparatus includes means for transmitting a power signal. The apparatus further includes means for scanning for one or more connection requests sent by the device. The apparatus further includes means for receiving a connection request from the charging device via the wireless communication network in response to the transmitted power signal. The apparatus further includes means for transmitting a connection request to establish a connection with the charging device in response to the received connection request.
Another aspect of the present disclosure provides a non-transitory computer readable medium comprising code that, when executed, causes the device to transmit a power signal. The medium further includes code that, when executed, causes the device to scan for one or more connection requests sent by the device. The medium further includes code that, when executed, causes the device to receive a connection request from the charging device via the wireless communication network in response to the transmitted power signal. The medium further includes code that, when executed, causes the device to transmit a connection request to establish a connection with the charging device in response to the received connection request.
Another aspect of the present disclosure provides a charging device for connecting to a wireless charger via a wireless communication network. The charging device includes a receiver configured to receive the power signal transmitted by the wireless charger. The charging device further includes a processor configured to generate a connection request in response to the power signal being received. The charging device further includes a transmitter configured to transmit the connection request via the wireless communication network. The receiver may be configured to receive a connection request to establish a connection with the wireless charger in response to the transmitted connection request.
Another aspect of the present disclosure provides a method for connecting with a wireless charger via a wireless communication network. The method includes the step of receiving a power signal transmitted by the wireless charger. The method further includes the step of generating a connection request in response to the power signal being received. The method further comprises the step of transmitting the connection request via the wireless communication network. The method further includes receiving a connection request to establish a connection with the wireless charger in response to the transmitted connection request.
Another aspect of the present disclosure provides an apparatus for connecting with a wireless charger via a wireless communication network. The apparatus includes means for receiving a power signal transmitted by the wireless charger. The apparatus further includes means for generating a connection request in response to the power signal being received. The apparatus further includes means for transmitting the connection request via the wireless communication network. The apparatus further includes means for receiving a connection request to establish a connection with the wireless charger in response to the transmitted connection request.
Another aspect of the present disclosure provides a non-transitory computer readable medium comprising code that, when executed, causes the device to receive a power signal transmitted by the wireless charger. The medium further includes code that, when executed, causes the device to generate a connection request in response to the power signal being received. The medium further includes code that, when executed, causes the device to transmit a connection request via the wireless communication network. The medium further includes code that, when executed, causes the device to receive a connection request to establish a connection with the wireless charger in response to the transmitted connection request.
FIG. 1 is a functional block diagram of an exemplary wireless power transfer system, according to an exemplary embodiment. FIG. 2 is a functional block diagram of exemplary components that may be used in the wireless power transfer system of FIG. 1 according to various exemplary embodiments. FIG. 3 is a schematic diagram of a portion of the transmit or receive circuit of FIG. 2 including a transmit or receive coil, according to an exemplary embodiment. FIG. 2 is a functional block diagram of a transmitter that may be used in the wireless power transfer system of FIG. 1 according to an exemplary embodiment. FIG. 2 is a functional block diagram of a receiver that may be used in the wireless power transfer system of FIG. 1 according to an exemplary embodiment. FIG. 5 is a schematic view of a portion of a transmitter circuit that may be used in the transmitter circuit of FIG. FIG. 6 is a block diagram of a wireless charging system that may incorporate the transmit circuit of FIG. 4 and the receive circuit of FIG. 5; FIG. 8 is a block diagram of a charging service and profile for a wireless charging system, such as the wireless charging system of FIG. 7. FIG. 8 is another block diagram of charging services and profiles for a wireless charging system, such as the wireless charging system of FIG. 7. FIG. 8 is a timing diagram of communication between a wireless charger and a charging device, such as the wireless charger and charging device of FIG. 7, to establish a connection between the wireless charger and the charging device. FIG. 9 is a timing diagram of communication between a wireless charger and a charging device, such as the wireless charger and charging device of FIG. 7, during a first connection. FIG. 8 is a timing diagram of communication between a wireless charger and a charging device, such as the wireless charger and charging device of FIG. 7. FIG. 8 is another timing diagram of communication between a wireless charger and a charging device, such as the wireless charger and charging device of FIG. 7. FIG. 6 is a flowchart of an exemplary method for wirelessly connecting to a charging device via a wireless communication network. FIG. 2 is a functional block diagram of a wireless charger according to an exemplary embodiment. FIG. 7 is a flowchart of an exemplary method for connecting to a wireless charger via a wireless communication network. FIG. 2 is a functional block diagram of a charging device according to an exemplary embodiment.
The various features illustrated in the drawings may not be drawn to scale. Thus, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method or device. Finally, like reference numerals may be used to indicate like features throughout the specification and figures.
The following detailed description, with reference to the accompanying drawings, is intended to describe exemplary embodiments and is not intended to represent the only embodiments in which the present invention can be practiced. . The term "exemplary" as used throughout the description means "serving as an example, instance, or illustration" and is necessarily preferred over other exemplary embodiments, or It should not be construed as advantageous. The detailed description includes specific details in order to provide a thorough understanding of the exemplary embodiments. In some cases, several devices are shown in block diagram form.
Transmitting power wirelessly may refer to transmitting any form of energy associated with an electric field, magnetic field, electromagnetic field, etc. from a transmitter to a receiver without using physical electrical conductors (eg, Power can be transmitted through free space). The power output in the wireless field (e.g., a magnetic field) may be received, captured or combined by the "receive coil" to achieve power transfer.
FIG. 1 is a functional block diagram of an exemplary wireless power transfer system 100 in accordance with an exemplary embodiment. An input power 102 can be provided to the transmitter 104 from a power source (not shown) to generate the field 105 to enable energy transfer. Receiver 108 may be coupled to field 105 and may generate output power 110 for storage or consumption by a device (not shown) coupled to output power 110. Both transmitter 104 and receiver 108 are separated by distance 112. In an exemplary embodiment, transmitter 104 and receiver 108 are configured according to each other's resonant relationship. When the resonant frequency of receiver 108 and the resonant frequency of transmitter 104 are approximately the same or very close, transmission loss between transmitter 104 and receiver 108 is minimized. Thus, enabling wireless power transfer over longer distances as opposed to purely inductive solutions that may require large coils where the coils need to be very close (e.g. several mm) be able to. Thus, resonant inductive coupling techniques may improve efficiency and enable power transfer over different distances and with different induction coil configurations.
The receiver 108 can receive power when located in the energy field 105 generated by the transmitter 104. The field 105 corresponds to the area where the energy output by the transmitter 104 may be captured by the receiver 108. In some cases, the field 105 may correspond to the "near field" of the transmitter 104, as described further below. The transmitter 104 may include a transmit coil 114 for outputting energy transfer. Further, receiver 108 includes a receive coil 118 for receiving or capturing energy from the energy transfer. The near field may correspond to a region where there is a strong reaction field due to the current and charge in the transmit coil 114 that radiates power from the transmit coil 114 to a minimum. In some cases, the near field may correspond to a region within about one wavelength (or a fraction of the wavelength) of the transmit coil 114. The transmit coil 114 and receive coil 118 are sized according to the application and device associated with them. As mentioned above, efficient energy transfer occurs by coupling most of the energy of the field 105 of the transmit coil 114 to the receive coil 118, rather than propagating most of the energy of the electromagnetic wave to the non-near field. It can be done. When located within field 105, a “coupled mode” can be generated between transmit coil 114 and receive coil 118. The area around transmit coil 114 and receive coil 118 where this coupling can occur is referred to herein as the coupled mode area.
FIG. 2 is a functional block diagram of exemplary components that may be used in the wireless power transfer system 100 of FIG. 1 in accordance with various exemplary embodiments. The transmitter 204 may include a transmitter circuit 206, which may include an oscillator 222, a driver circuit 224, and a filter / matching circuit 226. Oscillator 222 may be configured to generate a signal of a desired frequency, such as 468.75 KHz, 6.78 MHz, or 13.56 MHz, which may be adjusted in response to frequency control signal 223. The oscillator signal may be provided to a driver circuit 224 configured to drive the transmit coil 214 at, for example, the resonant frequency of the transmit coil 214. Driver circuit 224 may be a switching amplifier configured to receive a square wave from oscillator 222 and output a sine wave. For example, driver circuit 224 may be a class E amplifier. Also, filter / matching circuit 226 may be included to filter harmonics or other unwanted frequencies and to match the impedance of transmitter 204 to transmit coil 214.
Receiver 208 generates a DC power output from the AC power input to power matching circuit 232 and a device (not shown) charging battery 236 shown in FIG. 2 or coupled to receiver 208. And a receiver circuit 210 which may include a rectifier / switching circuit 234 for Matching circuit 232 may be included to match the impedance of receive circuit 210 to receive coil 218. Additionally, receiver 208 and transmitter 204 may communicate on separate communication channels 219 (eg, Bluetooth, zigbee, cellular, etc.). Alternatively, receiver 208 and transmitter 204 can communicate via in-band signaling using the characteristics of wireless field 205.
Receiver 208, which may initially have an associated load (eg, battery 236) that can be selectively disabled, as described more fully below, is the power transmitted by transmitter 204 and received by receiver 208 Can be configured to determine whether the amount of is appropriate to charge the battery 236. Further, receiver 208 may be configured to validate the load (eg, battery 236) upon determining that the amount of power is appropriate. In some embodiments, receiver 208 may be configured to directly utilize the power received from the wireless power transfer field without charging battery 236. For example, communication devices such as near field communication (NFC) or radio frequency identification devices (RFID) receive power from wireless power transfer fields by interacting with wireless power transfer fields and / or utilize received power And may be configured to communicate with transmitter 204 or other devices.
FIG. 3 is a schematic diagram of a portion of the transmit circuit 206 or receive circuit 210 of FIG. 2 including a transmit or receive coil 352, according to an exemplary embodiment. As shown in FIG. 3, the transmit or receive circuit 350 used in the exemplary embodiment can include a coil 352. Also, the coil can be referred to as a "loop" antenna 352 or can be configured as a "loop" antenna 352. Also, coil 352 may be referred to herein as a "magnetic" antenna or induction coil, or may be configured as a "magnetic" antenna or induction coil. The term "coil" is intended to refer to a component that can wirelessly output or receive energy for coupling to another "coil". The coil may also be referred to as a type of "antenna" configured to output or receive power wirelessly. Coil 352 may be configured to include an air core or a physical core (not shown) such as a ferrite core. Air core loop coils may be more durable to unrelated physical devices placed near the core. In addition, the air core loop coil 352 allows other components to be placed in the core region. In addition, the air core loop may more easily allow receiving coil 218 (FIG. 2) to be placed in the plane of transmitting coil 214 (FIG. 2), and the coupled mode region of transmitting coil 214 (FIG. 2) is May be more powerful.
As mentioned above, efficient transfer of energy between transmitter 104 and receiver 108 is achieved during the generation of matched or near-matched resonances between transmitter 104 and receiver 108. Can be However, even when the resonances between the transmitter 104 and the receiver 108 are not matched, energy can be transferred, which can affect efficiency. The transfer of energy is accomplished by coupling the energy from the field 105 of the transmit coil to the nearby receive coil, which is established instead of propagating the energy from the transmit coil to free space.
The resonant frequency of the loop coil or magnetic coil is based on the inductance and capacitance. While the inductance may simply be the inductance generated by the coil 352, a capacitance may be added to the inductance of the coil to generate a resonant structure of the desired resonant frequency. As a non-limiting example, capacitor 352 and capacitor 354 may be added to transmit or receive circuit 350 to generate a resonant circuit that selects signal 356 at the resonant frequency. Thus, for larger diameter coils, the size of the capacitance needed to sustain resonance may decrease as the diameter or inductance of the loop increases. Further, as the diameter of the coil increases, the efficient energy transfer area of the near field may increase. Other resonant circuits formed using other components are also contemplated. As another non-limiting example, a capacitor may be placed in parallel between the two terminals of coil 350. With respect to the transmit coil, a signal 358 having a frequency substantially corresponding to the resonant frequency of the coil 352 may be an input to the coil 352.
In one embodiment, transmitter 104 may be configured to output a time-varying magnetic field having a frequency corresponding to the resonant frequency of transmit coil 114. When the receiver is in field 105, a time-varying magnetic field can induce a current in receiving coil 118. As mentioned above, when the receive coil 118 is configured to resonate at the frequency of the transmit coil 114, energy can be transferred efficiently. The AC signal induced in the receiver coil 118 may be rectified as described above to generate a DC signal that may be supplied to charge or power the load.
FIG. 4 is a functional block diagram of a transmitter 404 that may be used in the wireless power transfer system of FIG. 1 according to an exemplary embodiment. The transmitter 404 can include a transmit circuit 406 and a transmit coil 414. The transmit coil 414 may be the coil 352 shown in FIG. The transmit circuit 406 may supply RF power to the transmit coil 414 by generating an oscillating signal that generates energy (eg, magnetic flux) around the transmit coil 414. The transmitter 404 can operate at any suitable frequency. As an example, transmitter 404 may operate in the 13.56 MHz ISM band.
The transmitter circuit 406 is a fixed impedance matching circuit 409 for matching the impedance (eg, 50 ohms) of the transmitter circuit 406 to the transmitter coil 414 and the self of the device coupled to the receiver 108 (FIG. 1) with harmonic radiation. And a low pass filter (LPF) 408 configured to reduce jamming to a level that prevents jamming. Other exemplary embodiments may include different filter topologies, including, but not limited to, notch filters, which attenuate certain frequencies while passing other frequencies to coil 414. And adaptive impedance matching, which may vary based on a measurable transmission metric, such as the output power of or the DC current drawn by the driver circuit 424. The transmitter circuit 406 further includes a driver circuit 424 configured to drive the RF signal determined by the oscillator 423. The transmit circuitry 406 may be comprised of discrete devices or circuits, or alternatively, may be comprised of an integrated assembly. An exemplary RF power output from the transmit coil 414 may be on the order of 2.5 watts.
The transmitter circuit 406 adjusts the output power level to adjust the frequency or phase of the oscillator 423 and to implement a communication protocol to interact with neighboring devices via the attached receiver. It may further include a controller 415 for selectively enabling the oscillator 423 during the transmit phase (or duty cycle) of the receiver. Note that controller 415 may also be referred to herein as processor 415. Adjustment of the oscillator phase and associated circuitry in the transmit path may allow, among other things, the reduction of out-of-band emissions when moving from one frequency to another.
The transmitter circuit 406 may further include load sensing circuit 416 for detecting the presence or absence of an active receiver in the vicinity of the near field generated by the transmitter coil 414. By way of example, load sensing circuit 416 monitors the current through driver circuit 424 that may be affected by the presence or absence of a working receiver in the vicinity of the field generated by transmit coil 414, as described further below. . Detection of changes to the load on driver circuit 424 is by controller 415 for use in determining whether to enable oscillator 423 to transmit energy and to communicate with an active receiver. Be monitored. As described more fully below, the current measured at driver circuit 424 may be used to determine whether an ineffective device is located within the wireless power transfer area of transmitter 404.
The transmit coil 414 may be implemented with a litz wire or as an antenna strip having a thickness, width, and type of metal selected to keep the resistance loss low. In one implementation, transmit coil 414 may generally be configured in association with larger structures, such as tables, mats, lamps, or other less portable configurations. Thus, the transmit coil 414 may not generally need to be “rolled” to practical dimensions. An exemplary implementation of the transmit coil 414 is "electrically small" (ie, a fraction of the wavelength), and lower usable frequencies by using a capacitor to define the resonant frequency Can be tuned to resonate.
Transmitter 404 may collect and track information regarding the location and status of receiver devices that may be associated with transmitter 404. Thus, the transmit circuit 406 may include a presence detector 480, an enclosed detector 460, or a combination thereof, connected to the controller 415 (also referred to herein as a processor). The controller 415 may adjust the amount of power delivered by the driver circuit 424 in response to the presence signals from the presence detector 480 and the enclosed detector 460. The transmitter 404 is, for example, an AC-DC converter (not shown) for converting conventional AC power in a building, DC-DC for converting a conventional DC power source into a voltage suitable for the transmitter 404 Power may be received directly through some power supplies, such as a converter (not shown), or from a conventional DC power supply (not shown).
As a non-limiting example, the presence detector 480 may be a motion detector utilized to sense the initial presence of the device to be charged inserted into the coverage area of the transmitter 404. After detection, the transmitter 404 may be turned on and the RF power received by the device may be used to switch the switch on the Rx device in a predetermined manner, which in turn causes the transmitter 404 to drive. It brings about a change to the impedance.
As another non-limiting example, the presence detector 480 may be, for example, a detector capable of detecting a person by infrared detection means, motion detection means, or other suitable means. In some exemplary embodiments, a provision may exist to limit the amount of power that transmit coil 414 can transmit at a particular frequency. In some cases, these provisions are intended to protect persons from electromagnetic radiation. However, there may be an environment where the transmitting coil 414 is located in an area that is not occupied by a person or infrequently occupied by a person, such as, for example, a garage, an industrial site, or a store. If there are no people in these environments, it may be possible to increase the power output of the transmit coil 414 beyond the normal power limit requirements. In other words, the controller 415 adjusts the power output of the transmitting coil 414 to or below the regulation level in response to the presence of a person, and transmits if the person is outside the regulatory distance from the electromagnetic field of the transmitting coil 414. The power output of coil 414 may be adjusted to a level above regulatory levels.
As a non-limiting example, enclosed detector 460 (sometimes referred to herein as an enclosed compartment detector or enclosed space detector) determines that the enclosure is closed or open. And a device such as a sensing switch. When the transmitter is in a closed enclosure, the power level of the transmitter may be increased.
In an exemplary embodiment, a method may be used in which the transmitter 404 does not remain on indefinitely. In this case, the transmitter 404 can be programmed to disconnect after a time determined by the user. This feature prevents the transmitter 404, and in particular the driver circuit 424, from working long after the wireless devices around the transmitter 404 are fully charged. This event may be due to a failure of the circuit sent by the repeater or receiver coil to detect that the device is fully charged. In order to prevent the transmitter 404 from shutting off automatically when another device is placed around it, the automatic shut-off function of the transmitter 404 does not detect any activity around it It may be activated only after a defined period of time has elapsed. The user may be able to determine the inactivity time interval and change it as desired. As a non-limiting example, this time interval may be longer than the time interval required to fully charge the device, under the assumption that the particular type of wireless device was initially completely discharged.
FIG. 5 is a functional block diagram of a receiver 508 that may be used in the wireless power transfer system of FIG. 1 according to an exemplary embodiment. Receiver 508 includes receiver circuitry 510 that may include a receiver coil 518. Receiver 508 is further coupled to a device 550 for providing it with received power. Note that receiver 508 is shown as being external to device 550 but may be integrated into device 550. Energy may be wirelessly propagated to receive coil 518 and then coupled to device 550 through the remainder of receive circuit 510. By way of example, charging devices include mobile phones, portable music players, laptop computers, tablet computers, computer peripheral devices, communication devices (eg Bluetooth devices), digital cameras, hearing aids (and other medical devices) etc. Devices may be included.
The receive coil 518 may be tuned to resonate at the same frequency as the transmit coil 414 (FIG. 4) or within a particular frequency range. The receive coil 518 may have similar dimensions as the transmit coil 414 or may have different sizes based on the dimensions of the associated device 550. As an example, device 550 may be a portable electronic device having a diameter or length dimension smaller than the diameter or length of transmit coil 414. In such instances, the receive coil 518 may be implemented as a multi-turn coil to reduce the capacitance value of the tuning capacitor (not shown) and to increase the impedance of the receive coil. As an example, receive coil 518 may be disposed about the substantial circumference of device 550 to maximize coil diameter and reduce loop turns (ie, turns) and inter-winding capacitance of receive coil 518. May be done.
The receiver circuit 510 may allow for impedance matching to the receiver coil 518. The receiving circuit 510 includes a power conversion circuit 506 for converting the received RF energy source into charging power for use by the device 550. The power conversion circuit 506 includes an RF-DC converter 520 and may include a DC-DC converter 522. The RF-DC converter 520 rectifies the RF energy signal received by the receiving coil 518 into non-AC power having an output voltage represented by V rect . The DC-to-DC converter 522 (or other power regulator) is capable of matching the rectified RF energy signal to the device 550 having an output voltage and output current represented by V out and I out (eg, , Voltage). Various RF-DC converters are contemplated, including partial and complete rectifiers, regulators, bridges, doublers, and linear and switching converters.
The receiver circuit 510 may further include a switching circuit 512 for connecting the receiver coil 518 to the power converter circuit 506 or for disconnecting the power converter circuit 506. Disconnecting the receive coil 518 from the power conversion circuit 506 not only interrupts the charging of the device 550, but also changes the "seen" "load" from the transmitter 404 (FIG. 2).
As disclosed above, transmitter 404 includes load sensing circuit 416 that can detect variations in bias current supplied to transmitter driver circuit 424. Thus, the transmitter 404 has a mechanism to determine that the receiver is in the near field of the transmitter.
When multiple receivers 508 are present in the transmitter's near field, time multiplexing the loading and unloading of one or more receivers to more efficiently couple other receivers to the transmitter May be desirable. Receiver 508 may also be cloaked to eliminate coupling to other nearby receivers or reduce loading on nearby transmitters. This "unloading" of the receiver is also known herein as "cloaking." Further, this switching between unloading and loading, controlled by receiver 508 and detected by transmitter 404, provides a communication mechanism from receiver 508 to transmitter 404, as will be more fully described below. It can be realized. In addition, a protocol that enables sending a message from receiver 508 to transmitter 404 may be associated with this switching. As an example, the switching speed may be on the order of 100 microseconds.
In the exemplary embodiment, communication between transmitter 404 and receiver 508 refers to a device sensing / charging control mechanism, rather than conventional two-way communication (ie, in-band signaling using coupled fields). . In other words, transmitter 404 may use on / off keying of the transmitted signal to adjust whether energy is available in the near field. The receiver may interpret these energy changes as a message from transmitter 404. From the receiver side, receiver 508 may use tuning and detuning of receive coil 518 to adjust how much power is being received from the field. In some cases, tuning and detuning may be realized via switching circuit 512. The transmitter 404 may detect this difference in power used from the field and interpret these changes as a message from the receiver 508. It should be noted that modulation of transmit power and other forms of load behavior may be utilized.
The receiving circuit 510 may further include a signaling detector / beacon circuit 514, which may be used to identify fluctuations in received energy that may correspond to information signaling from the transmitter to the receiver. Additionally, the signaling / beacon circuit 514 detects transmission of reduced RF signal energy (ie, beacon signal) and rectifies the reduced RF signal energy to nominal power to provide power in the receiver circuit 510. It may be used to wake up either the unpowered circuit or the power depleted circuit to configure the receive circuit 510 for wireless charging.
The receiver circuit 510 further includes a processor 516 for coordinating the processes of the receiver 508 described herein, including the control of the switching circuit 512 described herein. Also, cloaking of receiver 508 may also occur when other events occur, including detection of an external wired charging source (eg, wall outlet / USB power) providing charging power to device 550 . Processor 516 may monitor beacon circuit 514 to determine beacon status and extract messages sent from transmitter 404, in addition to controlling receiver cloaking. Processor 516 may adjust DC-DC converter 522 to improve performance.
FIG. 6 is a schematic diagram of a portion of transmit circuit 600 that may be used for transmit circuit 406 of FIG. The transmitter circuit 600 may include a driver circuit 624 as described above in FIG. As mentioned above, the driver circuit 624 may be a switching amplifier that may be configured to receive a square wave and output a sine wave to supply to the transmitter circuit 650. In some cases, driver circuit 624 may be referred to as an amplifier circuit. Although driver circuit 624 is illustrated as a class E amplifier, any suitable driver circuit 624 may be used depending on the embodiment. The driver circuit 624 can be driven by the input signal 602 from the oscillator 423, as shown in FIG. Also, driver circuit 624 may be provided with a drive voltage V D configured to control the maximum power that may be delivered via transmitter circuit 650. The transmitter circuit 600 may include a filter circuit 626 to eliminate or reduce harmonics. The filter circuit 626 may be a three pole (capacitor 634, inductor 632 and capacitor 636) low pass filter circuit 626.
The signal output by the filter circuit 626 may be provided to a transmit circuit 650 that includes a coil 614. The transmitter circuit 650 may resonate at the frequency of the filtered signal provided by the driver circuit 624 (e.g., due to coil inductance or capacitance, or additional capacitor components) A series resonant circuit having a capacitance 620 and an inductance may be included. The load of transmitter circuit 650 can be represented by variable resistor 622. This load may be a function of wireless power receiver 508 positioned to receive power from transmitter circuit 650.
FIG. 7 is a block diagram of a wireless charging system 700 that may incorporate the transmit circuit 406 of FIG. 4 and the receive circuit 510 of FIG. The wireless charging system 700 may include a wireless charger 702 and a charging device 704. Wireless charger 702 may include a wireless power transmitter 710 and a Bluetooth® transceiver 720. In one embodiment, the wireless power transmitter 710 may be similar to and / or include the same functionality as the transmit circuit 406 of FIG. The charging device 704 may be similar to the charging device 550 of FIG. 5 and may further include a wireless power receiver 715 and a Bluetooth® transceiver 725. In one embodiment, the wireless power receiver 715 may be similar to and / or include the same functionality as the receiver circuit 510 of FIG.
Wireless power transmitter 710 may be coupled to transmit coil 714. The transmit coil 714 may be similar to the transmit coil 414 of FIG. Similarly, wireless power receiver 715 may be coupled to receive coil 718. The receive coil 718 may be similar to the receive coil 518 of FIG. In one embodiment, the wireless power transmitter 710 may be configured to wirelessly transmit power to the wireless power receiver 715 to charge the charging device 704.
Further, Bluetooth® transceiver 720 may be coupled to Bluetooth® antenna 724, and Bluetooth® transceiver 725 may be coupled to Bluetooth® antenna 728. In one embodiment, wireless charger 702 via antenna 724 and 728 so that charging device 704 can wirelessly receive power from wireless charger 702 to charge its battery or similar device. Bluetooth® transceivers 720 and 725 may be used to establish a connection between the and charging device 704. It is noted that although the use of the Bluetooth® protocol to establish a connection between the wireless charger 702 and the charging device 704 is described herein, this is not intended to be limiting. I want to. The aspects of the disclosure described herein may be implemented through the use of any wired or wireless communication protocol (eg, proprietary communication protocol, communication protocol established by standards organizations such as IEEE). For example, IrDA, Wireless USB, Z-Wave, ZigBee, USB, FireWire, etc. may be used.
FIG. 8A is a block diagram of a charging service and profile 800 for a wireless charging system, such as the wireless charging system 700 of FIG. In one embodiment, charging service and profile 800 includes wireless charger 802 and charging device 804. The wireless charger 802 may be similar to the wireless charger 702 of FIG. 7 and the charging device 804 may be similar to the charging device 704 of FIG. The wireless charger 802 may include a processor 810 configured to operate the charging profile 815. In some aspects, the charging profile 815 is a generic attribute profile (GATT) client using the Bluetooth® Low Energy (BLE) transport, and the GATT is transported by the general operation and attribute protocol Set up a framework for the data to be stored. In general, GATT is used for discovery services.
The charging device 804 can operate in two modes: self-powered mode and charger powered mode. In the self-powered mode, the charging device 804 includes sufficient power to operate in the normal mode during charging (e.g., sufficient charge remains in the battery or other internal power source). In the charger power supply mode, the charging device 804 does not have sufficient power to operate in the normal mode and needs to power up the power from the wireless charger 802 to support the charging operation. is there.
The charging device 804 may include a processor 820 configured to operate the charging service 825. In some aspects, the charging service 825 is a GATT server using BLE transport, and the GATT server is data transported via attribute protocol and access attribute protocol requests, commands, and confirmations from GATT clients. Remember. In one embodiment, charging service 825 may interact with charging profile 815 when charging device 804 is operating in a self-powered mode. For example, the charging device 804 in the self-powered mode has enough charge in its battery so that it can start up devices such as the processor 820 which may use more power than other components like the chipset It may be left. In other embodiments, the charging service 825 can interact with the charging profile 815 when the charging device 804 is operating in the charger power supply mode.
The charging device 804 may also include a chipset, such as a Bluetooth® chipset 830, configured to operate the charging service 835. In some aspects, charging service 835 is a GATT server. In one embodiment, the charging service 835 can interact with the charging profile 815 when the charging device 804 is operating in the charger power supply mode. For example, the charging device 804 in the charger power supply mode may not have sufficient charge to activate all of its components, such as the processor 820. As a way to conserve power using power received from the wireless charger 802, only the Bluetooth® chipset 830 may be activated. In other embodiments, the charging service 835 can interact with the charging profile 815 when the charging device 804 is operating in a self-powered mode. In other words, the charging device 804 can include at least two GATT servers, each implementing a different charging service 825 or 835, each server being an instance of WiPower charging service (WPCS), and a device information service ( May contain one instance of DIS).
Although FIG. 8A shows chipset 830 as being a Bluetooth® chipset, this is not intended to be limiting, and chipset 830 is designed to handle any wireless communication protocol. Note that you get. In further embodiments, charging services 825 and / or 835 may be implemented on an accessory of charging device 804, such as an external device or shell.
FIG. 8B is another block diagram of a charging service and profile 850 for a wireless charging system, such as the wireless charging system 700 of FIG. In one embodiment, charging device 804 may include a chipset, such as Bluetooth® chipset 830 configured to operate charging services 825 and 835. The charge service 825 may be used to interact with the charge profile 815 when the charge device 804 is in the self-powered mode, and to interact with the charge profile 815 when the charge device 804 is in the charger power mode. , Charging service 835 may be used. Alternatively, charging service 825 may be used to interact with charging profile 815 when charging device 804 is in charger power supply mode, and interacts with charging profile 815 when charging device 804 is in self-powering mode In order to do so, a charging service 835 may be used. In other implementations, a processor such as, for example, processor 820 of FIG. 8A may be configured to operate charging services 825 and 835. In other words, the charging device 804 can include one GATT server, which implements at least two different charging services 825 or 835, and the GATT server can include one instance of the WPCS, and one instance of the DIS. .
FIG. 9 is a timing diagram of communication between a wireless charger and a charging device, such as wireless charger 702 and charging device 704, to establish a connection between the wireless charger and the charging device. The wireless charger 702 can transmit a power pulse 902, which can be used to provide power to a charging device, such as the charging device 704, to charge the charging device. The wireless charger 702 can transmit a power pulse 902 to detect a charging device. As shown in FIG. 9, the power pulse 902 was transmitted but the charging device was not within the range of the power pulse 902. The wireless charger 702 can wait for a period of time before transmitting another power pulse 904. For example, the wireless charger 702 can wait 11.25 ms or 22.5 ms. Upon transmitting the power pulse 902 and / or 904, the wireless charger 702 can initiate a general connection establishment procedure. As shown in FIG. 9, power pulse 904 was transmitted and was within the range of charging device 704.
In some embodiments, the wireless charger 702 initiates a scan for advertisements (eg, notification of connection request or device characteristics) from a device such as the charging device 704. In a further embodiment, once the wireless charger 702 detects a load on the power pulse 904, the wireless charger 702 may be notified of an advertisement (eg, notification of connection request or device characteristics) from a device such as the charging device 704. Start a scan In this way, the wireless charger 702 can save power only by scanning for advertisements once it detects a load on the power pulse. In one embodiment, the power pulse 904 causes the charging device 704 to generate an advertisement (eg, the processor of the charging device 704 can generate an advertisement). The advertisement can include target device address and charging service type. For example, the advertisement may be BLE advertisement 906. The charging device 704 can send the BLE advertisement 906 (eg, as a broadcast message) to the wireless charger 702 as a scheduled recipient. If the BLE ad 906 does not reach the wireless charger 702 (as shown in FIG. 9), the charging device 704 can generate and send another BLE ad 908. For example, the charging device 704 can wait 20 ms before sending another BLE ad 908. If the connection is not established within a frame for a period of time, such as 10 seconds, the charging device 704 can leave the connectable mode and stop any charging that could have been initiated. In this manner, the charging device 704 saves power by only generating and transmitting BLE advertisements 906 and / or 908 once it receives power pulses 902 and / or 904 from the wireless charger 702. be able to.
Once the wireless charger 702 receives the BLE ad 908, the wireless charger may send a connection request 912 to the charging device 704. When the charging device 704 receives the connection request 912, a connection 914 between the wireless charger 702 and the charging device 704 is established. In some embodiments, once wireless charger 702 receives BLE advertisement 908, wireless charger 702 may transmit power pulse 902 and power pulse 902 until connection 914 between wireless charger 702 and charging device 704 is established. And / or 904 may continue to transmit.
Note that during the connection process shown in FIG. 9, the wireless charger 702 can continue to transmit power 910, eg, via power pulses 902 and / or 904, to charge the charging device 704. . In some aspects, the charging device 704 can be in charger power supply mode, and the power 910 causes the charging device 704 to remain active to establish a connection with the wireless charger 702. Can. Once the connection can not be established, the charging device 704 is currently in a self-powered mode and / or otherwise wireless charging does not require the power transmitted from the wireless charger 702 Once the device 702 determines, the wireless charger 702 can stop transmitting power 910.
If the connection is lost at any point, the charging device 704 can attempt to reconnect with the wireless charger 702. Alternatively, charging device 704 can wait until it receives another power pulse 902 and / or 904 from wireless charger 702.
FIG. 10 is a timing diagram of communication between a wireless charger and a charging device, such as the wireless charger 702 and the charging device 704 of FIG. 7, during a first connection. In one embodiment, subsequent communication may occur during the first connection regardless of whether the charging device is operating in a self-powered mode or a charger powered mode. After connection 914 is established between wireless charger 702 and charging device 704, wireless to ensure that charging device 704 is compatible with the charger via BLE authentication / encryption / combination procedure 1002 The charger 702 can authenticate the charging device 704. The BLE authentication / encryption / combination procedure 1002 will be described in more detail with respect to FIGS. 11 and 12.
After authentication, the wireless charger 702 can discover the primary service by sending a universally unique identifier (UUID) request 1004. For example, UUID request 1004 may be used to discover a primary WPCS. The charging device 704 may respond with a UUID response 1006. The wireless charger 702 can then discover some or all characteristics of the service by sending a service request 1008. For example, service request 1008 may be used to discover some or all of the characteristics of the WPCS. The charging device 704 may respond with a service response 1012.
The wireless charger 702 can then discover the primary service by sending a UUID request 1014. For example, UUID request 1014 may be used to discover a primary DIS. The charging device 704 may respond with a UUID response 1016. The wireless charger 702 can then discover some or all characteristics of the service by sending a service request 1018. For example, service request 1018 may be used to discover some or all of the characteristics of DIS. The charging device 704 may respond with a service response 1020.
It should be noted that during the first connection process shown in FIG. 10, the wireless charger 702 can continue to transmit power 1010 to charge the charging device 704. In some aspects, the charging device 704 can be in charger power supply mode, and the power 1010 causes the charging device 704 to remain active to establish a connection with the wireless charger 702. Can. Once the wireless charger 702 determines that the connection has been terminated and / or that the wireless charger 702 does not require the power transmitted from the wireless charger 702 otherwise, the wireless charger 702 will You can stop sending.
FIG. 11 is a timing diagram of communication between a wireless charger and a charging device, such as the wireless charger 702 and the charging device 704 of FIG. In one embodiment, subsequent communication may occur when the charging device 704 is operating in a self-powered mode. After connection 914 is established between the wireless charger 702 and the charging device 704, the charging device 704 uses a challenge response protocol via the BLE transport (eg, via BLE authentication / encryption procedure 1102) The wireless charger 702 can authenticate the charging device 704 to ensure that it matches the charger.
The wireless charger 702 can send a write without response (WPT authenticate) value 1104 to the charging device 704. In one embodiment, based on the received value, the charging device 704 generates a key value and wirelessly charges the key value via notification (WPT authenticate) value response 1106. It can be sent to 702. In another embodiment, based on the received value, the charging device 704 wirelessly stores 702 the stored or embedded key value in the charging device 704 via the notification (WPT authentication) value response 1106. Can be sent to The key value may be a public key, a private key, a public key certificate, a digital signature, a security token, a unique manufacturer identifier, etc. If the key value matches the value expected by the wireless charger 702, the authentication has ended and the wireless charger 702 has determined that the charging device 704 is compatible with it.
In other aspects, the wireless charger 702 can engage in one or more communications with the charging device 704 to ensure that the charging device 704 is compatible with the charger 702. The wireless charger 702 can send one or more authentication messages to the charging device 704. If one or more responses received from the charging device 704 match the responses expected by the wireless charger 702, the authentication is over and the wireless charger 702 determines that the charging device 704 is compatible with it . For example, the wireless charger 702 can use a combined key to authenticate the charging device 704. The wireless charger 702 can transmit a request for a charger technology key value stored in the charging device 704. If the charging device 704 is compatible with the wireless charger 702, the charger technology key value stored in the charging device 704 and transmitted by the charging device 704 to the wireless charger 702 is equal to the value expected by the wireless charger 702. I can do it. If the charging device 704 is compatible, the wireless charger 702 can transmit a request for the manufacturer key value stored on the charging device 704. If the charging device 704 is manufactured by the manufacturer of the charging device 704, the manufacturer key value stored in the charging device 704 and transmitted to the wireless charger 702 by the charging device 704 is the value expected by the wireless charger 702 Can match. In other embodiments, the wireless charger 702 can request both the charger technology key value and the manufacturer key value at the same or nearly the same time. In this manner, the manufacturer charges only the charging device 704 manufactured by the manufacturer, and / or charges the charging device 704 manufactured by the manufacturer differently from other compatible charging devices 704. It may be possible to limit the wireless charger 702 to do so.
In yet another aspect, the wireless charger 702 can authenticate the charging device via one-way communication. The wireless charger 702 can send one or more messages and determine whether the charging device 704 is compatible based on the behavior or action of the charging device 704. For example, if charging device 704 may be adapted to temporarily stop receiving power from wireless charger 702 based on one or more messages sent by wireless charger 702, charging device 704 may: Authentication may end. Similarly, charging device 704 can send one or more messages without being prompted, and wireless charger 702 can match charging device 704 based on the received one or more messages. You can decide whether to For example, the conforming device 704 may be configured to transmit a particular message or set of messages within a first time period of receiving a power pulse. If the wireless charger 702 receives a particular message or set of messages within a time period, the wireless charger 702 may determine that the charging device 704 is compatible and the authentication may end.
In one embodiment, if the authentication fails, the wireless charger 702 can reduce the amount of power transmitted or stop transmitting power to the charging device 704. In other embodiments, the wireless charger 702 can transmit power to the charging device 704 at a low level before authentication occurs. If the authentication is successful, the wireless charger 702 can transmit power to the charging device 704 at a normal level. If the authentication fails, the wireless charger 702 can continue to transmit power to the charging device 704 at a low level, or can stop transmitting power to the charging device 704.
The wireless charger 702 can then transmit the read characteristic value 1108 to the charging device 704. In one embodiment, the read characteristic value 1108 can include a charging parameter. The charging device 704 may respond by sending a read response 1112. In one embodiment, the read response 1112 can include charging parameters.
The wireless charger 702 can then send the write characteristic value 1114 to the charging device 704. In one embodiment, the write characteristic value 1114 can include charge control to command the charging device 704 to transition to the charging state to initiate charging. The charging device 704 may respond with a write characteristic value response 1116. In one embodiment, the write characteristic value response 1116 can include a confirmation that the charging device 704 transitions to a charging state and begins charging.
During charging, charging device 704 may periodically transmit notification values 1118, 1120 and / or 1122 to wireless charger 702. In one embodiment, the notification values 1118, 1120 and / or 1122 can include a charge report indicating the current charge level and / or voltage level of the charging device 704. Once the wireless charger 702 determines that the charging device 704 has a sufficient amount of power, the wireless charger 702 can transmit a write characteristic value 1124. In one embodiment, the write characteristic value 1124 can include charge control to command the charging device 704 to stop charging. The charging device 704 may respond with a write characteristic value response 1126. In one embodiment, the write characteristic value response 1126 can include a confirmation that the charging device 704 stops charging. Once the wireless charger 702 receives the write characteristic value response 1126, the connection is terminated 1128.
Note that during the communication shown in FIG. 11, the wireless charger 702 can continue to transmit power 1110 to charge the charging device 704. Once the wireless charger 702 determines that the connection is terminated at 1128 and / or otherwise the charging device 704 does not need the power transmitted from the wireless charger 702, the wireless charger 702 It is possible to stop sending 1110.
FIG. 12 is another timing diagram of communication between a wireless charger and a charging device, such as the wireless charger 702 and the charging device 704 of FIG. In one embodiment, subsequent communication may occur when the charging device 704 is operating in the charger power supply mode. After connection 914 is established between wireless charger 702 and charging device 704, wireless to ensure that charging device 704 is compatible with the charger via BLE authentication / encryption / combination procedure 1202 The charger 702 can authenticate the charging device 704.
The wireless charger 702 can send a no answer (WPT certified) write value 1204 to the charging device 704. Based on the received value, the charging device 704 can generate a key value and send the key value to the wireless charger 702 via a notification (WPT authentication) value response 1206. If the key value matches the value expected by the wireless charger 702, the authentication has ended and the wireless charger 702 has determined that the charging device 704 is compatible with it. If the authentication fails, the wireless charger 702 can stop transmitting power 1210 to the charging device 704.
The wireless charger 702 can then transmit the read characteristic value 1208 to the charging device 704. In one embodiment, the read characteristic value 1208 can include a charging parameter. The charging device 704 may respond by sending a read response 1212. In one embodiment, the read response 1212 can include charging parameters.
Unlike communication, as shown in FIG. 11, the wireless charger 702 may not need to transmit the write characteristic value 1114 to the charging device 704 to instruct the charging device 704 to initiate charging. Please note that. In one embodiment, since charging device 704 is operating in a charger power feed mode, it may be assumed that charging device 704 is already in a charging state.
During charging, charging device 704 may periodically send notification values 1214, 1216 and / or 1218 to wireless charger 702. In one embodiment, notification values 1214, 1216 and / or 1218 may include a charge report indicating the current charge level and / or voltage level of charging device 704. Once the wireless charger 702 determines that the charging device 704 has a sufficient amount of power, the wireless charger 702 can transmit the write characteristic value 1220. In one embodiment, the write characteristic value 1220 can include charge control to command the charging device 704 to stop charging. The charging device 704 may respond with a write characteristic value response 1222. In one embodiment, the write characteristic value response 1222 can include a confirmation that the charging device 704 stops charging. Once the wireless charger 702 receives the write characteristic value response 1222, the connection is terminated at 1224.
Note that during the communication shown in FIG. 12, the wireless charger 702 can continue to transmit power 1210 to charge the charging device 704. In some aspects, the charging device 704 can be in charger power supply mode, and the power 1210 causes the charging device 704 to remain active to establish a connection with the wireless charger 702. can do. Once the wireless charger 702 determines that the connection has been terminated and / or that the charging device 704 does not require the power transmitted from the wireless charger 702, then the wireless charger 702 determines the power 1210. You can stop sending.
FIG. 13 is a flow chart of an example method 1300 for connecting a charging device via a wireless communication network (eg, a personal area network using a Bluetooth® interface). In one embodiment, the steps in flowchart 1300 may be performed by wireless charger 702. Although the method of flowchart 1300 is described herein with reference to a particular order, in various embodiments, the blocks herein may be performed in a different order or may be omitted. Additional blocks may be added. Those skilled in the art will appreciate that the method of flowchart 1300 can be implemented in a device that can be configured to charge another device via wireless transfer of power.
At block 1302, method 1300 transmits a power signal. In one embodiment, the power signal is a power pulse. At block 1304, method 1300 scans for one or more connection requests sent by the device. In one embodiment, method 1300 can detect a load based on the transmitted power signal. Method 1300 may then scan for one or more connection requests sent by the device based on the detected load. At block 1306, method 1300 receives a connection request from the charging device via the wireless communication network in response to the transmitted power signal. At block 1308, method 1300 sends a connection request to establish a connection with the charging device in response to the received connection request. In some embodiments, when the method 1300 receives a connection request from a charging device, the method 1300 continues to transmit power signals until a connection is established.
FIG. 14 is a functional block diagram of a wireless charger 1400 in accordance with an illustrative embodiment. The wireless charger 1400 comprises means 1402, means 1404, means 1406 and means 1408 for the various actions described with respect to FIGS. 1 to 12. The wireless charger 1400 includes means 1402 for transmitting a power signal. In one embodiment, the means 1402 for transmitting a power signal may be configured to perform one or more of the functions described with respect to block 1302 above. The wireless charger 1400 further includes means 1404 for scanning for one or more connection requests sent by the device. In one embodiment, the means 1404 for scanning for one or more connection requests sent by the device may be configured to perform one or more of the functions described above with respect to block 1304. The wireless charger 1400 further includes means 1406 for receiving a connection request from the charging device via the wireless communication network in response to the transmitted power signal. In one embodiment, means 1406 for receiving a connection request from the charging device via the wireless communication network in response to the transmitted power signal includes one or more of the functions described above with respect to block 1306. It may be configured to perform. Wireless charger 1400 further includes means 1408 for transmitting a connection request to establish a connection with the charging device in response to the received connection request. In one embodiment, the means 1408 for sending a connection request to establish a connection with the charging device in response to the received connection request includes one or more of the functions described above with respect to block 1308. Can be configured to perform.
FIG. 15 is a flowchart of an exemplary method 1500 for wirelessly connecting to a wireless charger via a wireless communication network (eg, a personal area network using a Bluetooth® interface). In one embodiment, the steps in flowchart 1500 may be performed by charging device 704. Although the method of flowchart 1500 is described herein with reference to a particular order, in various embodiments, the blocks herein may be performed in a different order or may be omitted. Additional blocks may be added. Those skilled in the art will appreciate that the method of flowchart 1500 may be implemented in a device that may be configured to be charged by another device via wireless transfer of power.
At block 1502, method 1500 receives a power signal transmitted by a wireless charger. At block 1504, method 1500 generates a connection request in response to the power signal being received. At block 1506, method 1500 sends a connection request over a wireless communication network. At block 1508, the method 1500 receives a connection request to establish a connection with the wireless charger in response to the transmitted connection request.
FIG. 16 is a functional block diagram of a charging device 1600 in accordance with an illustrative embodiment. The charging device 1600 comprises means 1602, means 1604, means 1606 and means 1608 for the various actions described with respect to FIGS. 1 to 12. The charging device 1600 includes means 1602 for receiving the power signal transmitted by the wireless charger. In one embodiment, the means 1602 for receiving the power signal transmitted by the wireless charger may be configured to perform one or more of the functions described above with respect to block 1502. The charging device 1600 further includes means 1604 for generating a connection request in response to the power signal being received. In one embodiment, the means 1604 for generating the connection request in response to the power signal being received may be configured to perform one or more of the functions described above with respect to block 1504. . The charging device 1600 further includes means 1606 for transmitting the connection request via the wireless communication network. In one embodiment, means 1606 for transmitting the connection request via the wireless communication network may be configured to perform one or more of the functions described above with respect to block 1506. The charging device 1600 further includes means 1608 for receiving a connection request to establish a connection with the wireless charger in response to the transmitted connection request. In one embodiment, the means 1608 for receiving a connection request to establish a connection with a wireless charger in response to the transmitted connection request comprises one or more of the functions described above with respect to block 1508 or It may be configured to implement more than one.
The various operations of the above method may be performed by any suitable means capable of performing the operations, such as various hardware and / or software components, circuits and / or modules. In general, any operations shown in the figures may be performed by corresponding functional means capable of performing the operations. The means for transmitting the power signal and the means for transmitting the connection request include a transmitter. The means for detecting the load comprises a load detector. Means for scanning for one or more connection requests sent by the device include a device scanner. Means for receiving a connection request include a receiver. The means for receiving the power signal and the means for receiving the connection request include a receiver. The means for generating a connection request comprises a processor. Means for transmitting a connection request include a transmitter.
Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any of them. It may be represented by a combination.
The various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality may be implemented in various ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments.
Various exemplary blocks, modules, and circuits described with respect to the embodiments disclosed herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) Or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. obtain.
The steps of methods or algorithms and functions described in connection with the embodiments disclosed herein may be embodied directly in hardware or embodied in software modules executed by a processor. Or may be embodied in a combination of the two. When implemented in software, the functions may be stored on a tangible non-transitory computer readable medium as one or more instructions or code, or transmitted via the non-transitory computer readable medium. The software module may be random access memory (RAM), flash memory, read only memory (ROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, removable disk, CD ROM, or It may reside in any other form of storage medium known in the art. A storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. As used herein, discs and discs are compact discs (CDs), laser discs (registered trademark) (discs), optical discs, digital versatile discs (disc) , Floppy (registered trademark) disks, and Blu-ray discs (discs), and the discs normally reproduce data magnetically, and the discs reproduce data optically with a laser. Do. Combinations of the above should also be included within the scope of computer readable media. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
To aspects of the present disclosure, several aspects, advantages, and novel features of the present invention have been described herein. It should be understood that in accordance with any particular embodiment of the present invention, not all of such advantages may be realized. Thus, the present invention embodies or optimizes one advantage or group of advantages taught herein without necessarily realizing other advantages that may be taught or suggested herein. It can be implemented.
Various modifications to the above-described embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
105 fields
114 transmitter coil
118 receive coil
214 transmitter coil
218 receive coil
350 transmitter or receiver
352 coil
352 "loop" antenna
354 capacitor
408 Low Pass Filter (LPF)
506 Power converter circuit
514 Signal transmission detector / beacon circuit
518 Receive coil
614 coil
634 capacitor
700 wireless charging system
702 Wireless Charger
704 charging device
710 Wireless Power Transmitter
714 transmitter coil
715 Wireless Power Receiver
718 Receive coil
720 Bluetooth (R) transceiver
724 Bluetooth (registered trademark) antenna
725 Bluetooth (R) transceiver
728 Bluetooth (R) antenna
800 charging service and profile
802 wireless charger
804 charging device
815 charging profile
825 charging service
830 Bluetooth (registered trademark) chipset
835 charging service
902 power pulse
904 power pulse
906 BLE Advertising
908 another BLE ad
912 Connection request
914 connection
1002 BLE authentication / encryption / combination procedure
1004 Universal Unique Identifier (UUID) Request
1006 UUID response
1008 Service request
1012 Service response
1016 UUID response
1018 Service request
1104 No response write value
1106 Notification (WPT certification) value response
1108 Characteristic value
1112 Read response
1114 Write characteristic value
1116 Write characteristic value response
1118 Notification value
1120 notification value
1122 Notification value
1124 Write characteristic value
1126 Write characteristic value response
1204 No response write value
1206 Notification (WPT certification) value response
1208 Characteristic value
1212 read response
1220 write characteristic value
1222 Write characteristic value response
1300 ways
1306 blocks
1308 blocks
1400 wireless charger
1402 means
1404 means
1406 means
1408 means
1500 ways
1502 blocks
1506 blocks
1508 blocks
1600 charging device
1602 means
1604 means
1606 means
1608 means
A wireless charger for connecting to a charging device via a wireless communication network, comprising:
A load detector configured to detect a load based on a change detected in a circuit driving the power signal, the detected change being generated by the transmission of the power signal and the transmitter A load detector due to the presence of the load in the
A device scanner configured to scan for one or more connection requests sent by the charging device in response to the detection of the load;
The response was generated connected in the charging device requested the transmitted power signal, a receiver configured to receive via the wireless communication network,
Wireless charging and a second transmitter that a connection request to establish a connection with the charging device in response to consists to transmit via the wireless communication network to the received connection request vessel.
The wireless charger of claim 1, wherein the connection request includes charging information associated with a charging service.
The wireless charger according to claim 2, wherein the charging information includes a target device address and a charging service type.
The wireless charger according to claim 1, wherein the connection request is transmitted in a separate communication from the transmitted power signal.
The wireless charger of claim 1, wherein the power signal charges the charging device.
A charger power supply mode wherein the charging device does not include sufficient power to operate in the normal mode during charging, and a self including the power sufficient for the charging device to operate in the normal mode during charging. 6. The wireless charger of claim 5, wherein the charging device includes a power delivery mode.
The charger power supply mode is supported by a first physical implementation, the self power supply mode is supported by a second physical implementation, and the charging device is in the charger power supply mode. The wireless device of claim 6, wherein the charging device terminates connection with the wireless charger when the charging device receives an amount of power sufficient to operate in the normal mode during charging. Charger.
When the charging device receives an amount of power sufficient to operate in the normal mode during charging, the charging device transitions to the self-powered mode, the charging device with the wireless charger The wireless charger according to claim 7, wherein the connection of is reestablished.
7. The wireless charger of claim 6, wherein the charger power delivery mode is supported by a first physical implementation and the self-power delivery mode is supported by the first physical implementation.
When the charging device receives an amount of power sufficient to operate in the normal mode without charging the connection with the wireless charger, the charging device supplies the charger power. 10. The wireless charger of claim 9, transitioning from the mode to the self powered mode.
7. The wireless of claim 6, wherein the second transmitter is further configured to transmit an instruction to initiate a charging operation at the charging device when the charging device is in the self-powered mode. Charger.
The wireless charger according to claim 1, wherein the receiver is further configured to receive a charging report from the charging device, the charging report including a current charge level of the charging device.
13. The wireless charger of claim 12, wherein the second transmitter is further configured to transmit a charge stop command to the charging device based on the received charge report.
A method for connecting a charging device via a wireless communication network, comprising:
Detecting a load based on a change detected by the circuit driving the power signal, the detected change being transmission of the power signal and the field within the field generated by transmission of the power signal Steps due to the presence of the load,
Scanning for one or more connection requests sent by the charging device in response to the detection of the load;
A step in which the said connection request generated in the charging device in response to the transmitted power signal, to receive through the wireless communication network,
Transmitting via the wireless communication network a connection request to establish a connection with the charging device in response to the received connection request.
15. The method of claim 14, wherein receiving a connection request comprises receiving charging information associated with a charging service.
The method according to claim 15, wherein the charging information comprises a target device address and a charging service type.
15. The method of claim 14, wherein transmitting a connection request comprises transmitting the connection request in a separate communication from the transmitted power signal.
The step of transmitting a power signal may further comprise transmitting the power signal to charge the charging device, the charging device not having sufficient power to operate in normal mode during charging. 15. The method of claim 14, wherein the charging device includes a self-powered mode and a self-powered mode wherein the charging device includes power sufficient to operate in the normal mode during charging.
Terminating the connection with the charging device when the charging device receives an amount of power sufficient to operate in the normal mode during charging, the charger power supply mode being: 19. The method according to claim 18, further comprising the steps of: supported by a physical implementation of: the self-powered mode supported by a second physical implementation; and the charging device is the charger powered mode. Method described.
Re-establishing a connection with the charging device after the charging device transitions to the self-powered mode, the charging device having an amount of power sufficient to operate in the normal mode during charging; 21. The method of claim 19, further comprising the step of the charging device transitioning to the self-powered mode when receiving.
Maintaining the connection with the charging device when the charging device transitions from the charger power supply mode to the self-power supply mode, the charger power supply mode being a first physical 19. The method of claim 18, further comprising the steps supported by an implementation, wherein the self-powered mode is supported by the first physical implementation.
The method according to claim 18, further comprising: transmitting an instruction to start a charging operation in the charging device when the charging device is in the self-powered mode.
15. The method of claim 14, further comprising receiving a charge report from the charging device, wherein the charge report comprises a current charge level of the charging device.
24. The method of claim 23, further comprising transmitting a charge stop instruction to the charging device based on the received charge report.
An apparatus for connecting to a charging device via a wireless communication network, the apparatus comprising:
Means for transmitting a power signal,
Means for detecting a load based on a change detected in the circuit driving the power signal, the detected change generated by transmission of the power signal and the transmission means Means due to the presence of said load in the field;
Means for scanning for one or more connection requests sent by the charging device in response to the detection of the load;
An access request generated in the responsive charging device to the transmitted power signal, means for receiving via said wireless communication network,
Means for transmitting , via the wireless communication network, a connection request to establish a connection with the charging device in response to the received connection request.
26. The apparatus of claim 25, wherein the means for receiving a connection request comprises means for receiving a target device address and a charging service type.
26. The apparatus of claim 25, wherein the means for transmitting a connection request comprises means for transmitting the connection request in a separate communication from the transmitted power signal.
The means for transmitting a power signal further comprises means for transmitting the power signal to charge the charging device, the power of the charging device sufficient to operate in normal mode during charging. 26. The apparatus according to claim 25, wherein the charging device includes a charger power supply mode not including: and a self-powering mode in which the charging device includes power sufficient to operate in the normal mode during charging. .
Means for terminating a connection with the charging device when the charging device receives an amount of power sufficient to operate in the normal mode during charging, the charger power supply mode being 30. The method of claim 28, further comprising: means supported by one physical implementation, wherein the self-powered mode is supported by a second physical implementation, and the charging device is the charger powered mode. The device described in.
Means for maintaining the connection with the charging device when the charging device transitions from the charger power supply mode to the self-power supply mode, the charger power supply mode being a first physical 29. The apparatus of claim 28, further comprising: means supported by a static implementation, wherein the self-powered mode is supported by the first physical implementation.
29. The apparatus of claim 28, further comprising: means for transmitting an instruction to initiate a charging operation on the charging device when the charging device is in the self-powered mode.
Said means for transmitting a power signal, and said means for transmitting a connection request comprises a transmitter, said means for detecting a load comprises a load detector, and said means for scanning for a device 26. The apparatus of claim 25, comprising a device scanner, wherein the means for receiving comprises a receiver.
A non-transitory computer readable recording medium comprising code, wherein the code when executed on the device
Send a power signal,
Causing a load to be detected based on a change detected by the circuit driving the power signal,
Wherein the access request generated in the charging device in response to the transmitted power signal, is received via a wireless communication network,
Causing a connection request to establish a connection with the charging device in response to the received connection request through the wireless communication network ;
A non-transitory computer readable recording medium, wherein the detected change is due to the transmission of the power signal and the presence of the load in the field generated by the transmission of the power signal.
34. The medium of claim 33, further comprising code that, when executed, causes the device to receive a target device address and a charging service type.
34. The medium of claim 33, further comprising code that, when executed, causes the device to transmit the connection request in a separate communication from the transmitted power signal.
A code that, when executed, causes the device to transmit the power signal to charge the charging device, wherein the charging device does not contain sufficient power to operate in normal mode during charging. 34. The medium of claim 33, further comprising a cord, wherein the charging device includes a power supply mode, and a self-powering mode wherein the charging device includes power sufficient to operate in the normal mode during charging. .
A code that, when executed, causes the device to terminate the connection with the charging device when the charging device receives an amount of power sufficient to operate in the normal mode during charging. A power supply mode supported by a first physical implementation, a self power supply mode supported by a second physical implementation, and the charging device being the charger power supply mode 37. The medium of claim 36, further comprising:
A code that, when executed, causes the device to re-establish connection with the charging device after the charging device transitions to the self-powered mode, the charging device operating in the normal mode while charging 38. The medium of claim 37, further comprising a code, wherein the charging device transitions to the self-powered mode when receiving an amount of power sufficient to do so.
JP2015504621A 2012-04-03 2013-03-26 System and method for wireless power control communication using Bluetooth (R) Low Energy Active JP6517689B2 (en)
JP2015515851A JP2015515851A (en) 2015-05-28
JP2015515851A5 JP2015515851A5 (en) 2016-12-28
JP6517689B2 true JP6517689B2 (en) 2019-05-22
JP2015504621A Active JP6517689B2 (en) 2012-04-03 2013-03-26 System and method for wireless power control communication using Bluetooth (R) Low Energy
JP2015504622A Active JP6530311B2 (en) 2012-04-03 2013-03-26 System and method for wireless power control communication using Bluetooth (R) Low Energy
JP2017143375A Pending JP2017209008A (en) 2012-04-03 2017-07-25 System and method for wireless power control communication using bluetooth(r) low energy
JP2017230260A Pending JP2018057266A (en) 2012-04-03 2017-11-30 SYSTEM AND METHOD FOR WIRELESS POWER CONTROL COMMUNICATION USING Bluetooth(R) LOW ENERGY
JP5615972B2 (en) 2014-10-29 Control of the electromagnetic field distribution of the wireless power transmitter
2016-11-07 A871 Explanation of circumstances concerning accelerated examination
Ref document number: 6517689