JP7158171B2 - Power receiving device, control method, and program - Google Patents

Description

The present invention relates to information provision technology in wireless power transmission.

In recent years, technical development of wireless power transmission systems such as non-contact charging systems has been widely carried out. Patent Literature 1 describes a power transmitting device and a power receiving device that comply with standards established by the Wireless Power Consortium (WPC), which is a standardization organization for contactless charging (hereinafter referred to as “WPC standards”). Further, Patent Literature 2 discloses a device authentication method between a power transmitting device and a power receiving device for contactless charging. In the crisis authentication method of Patent Literature 2, the power transmitting device transmits challenge data to the power receiving device via the power transmitting coil, and the power receiving device generates response data by performing authentication calculation on the challenge data, and transmits the response data to the power receiving coil. to the power transmission device. Upon receiving the response data, the power transmission device performs device authentication by verification processing using the verification data.

JP 2016-007116 A JP 2010-104097 A

Power transmission is restricted between the power transmitting device and the power receiving device that have not succeeded in device authentication. Therefore, it is important for the user to bring the power receiving device close to the power transmitting device that can successfully perform device authentication. However, conventionally, the user has to place the power receiving device on the power transmitting device in order to recognize whether or not the power receiving device can succeed in device authentication, which is inconvenient.

The present invention has been made in view of the above problems, and provides a technique for improving user convenience in a wireless power transmission system that performs device authentication.

A power receiving device according to an aspect of the present invention includes power receiving means for receiving power from a power transmitting device by wireless power transmission, communication means for performing communication in a communicable range wider than a range in which the power receiving means can receive power in the wireless power transmission, Communication is started while the power receiving device has entered the communicable range and the power receiving device has not been detected by the power transmitting device in the wireless power transmission , and is authenticated with the power transmitting device by the communication means . presenting means for presenting to the user information indicating that the power transmitting device exists, at least based on the fact that the communication for authentication including the process of communicating information about the document is performed.

ADVANTAGE OF THE INVENTION According to this invention, the user's convenience in the wireless power transmission system which performs apparatus authentication can be improved.

1 is a diagram showing the configuration of a contactless charging system; FIG. It is a figure which shows the structural example of a power transmission apparatus. It is a figure which shows the structural example of a receiving device. 6 is a flowchart showing an example of the flow of device authentication processing executed by the power transmission device; 6 is a flowchart showing an example of the flow of device authentication processing executed by the power receiving device; 6 is a flowchart showing an example of the flow of power transmission control processing executed by the power transmission device; 4 is a flowchart showing an example of the flow of power reception control processing executed by the power reception device; It is a figure which shows the example of the flow of the process performed by a system. (A) is a diagram showing a communication sequence for device authentication, (B) is a diagram showing an I&C phase communication sequence, and (C) is a diagram showing a Negotiation phase communication sequence. FIG. 3 is a diagram showing an example of information stored in a power transmission device; FIG. 10 is a diagram showing an example of a screen displayed on the power receiving device; FIG. 10 is a diagram showing an example of a screen displaying information about device authentication processing on the power receiving device;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. The following embodiments are merely examples for explaining the technical idea of the present invention, and are not intended to limit the present invention to the configurations and methods described in the embodiments.

(System configuration)
FIG. 1 shows a configuration example of a non-contact charging system (wireless power transmission system) according to this embodiment. In one example, the system includes a power transmission device 101 and a power reception device 102 . Hereinafter, the power transmitting device 101 may be referred to as TX, and the power receiving device 102 may be referred to as RX. TX is an electronic device that wirelessly transmits power to RX placed on charging stand 103 . RX is an electronic device that receives power from the power transmission device 101 and charges an internal battery. Note that TX and RX may have the function of executing applications other than contactless charging. For example, TX and RX may be storage devices such as hard disk devices and memory devices, or may be information processing devices such as personal computers (PCs) and smart phones. Also, TX and RX may be, for example, an image input device such as an imaging device (camera, video camera, etc.) or a scanner, or may be an image output device such as a printer, a copier, a projector, or the like.

This system shall perform wireless power transmission using an electromagnetic induction method for contactless charging based on the WPC standard defined by WPC (Wireless Power Consortium). That is, TX and RX perform wireless power transmission for contactless charging based on the WPC standard between the power transmission coil of TX and the power reception coil of RX. The wireless power transmission method (non-contact power transmission method) is not limited to the method specified by the WPC standard, and other methods using electromagnetic induction method, magnetic resonance method, electric field resonance method, microwave method, laser, etc. may be Also, in the present embodiment, wireless power transmission is used for contactless charging, but wireless power transmission may be used for purposes other than contactless charging.

In the WPC standard, the amount of power guaranteed to be transmitted between TX and RX is defined by a value called Guaranteed Power (hereinafter referred to as "GP"). GP is guaranteed to be output to a load of RX such as a charging circuit even if the positional relationship between TX and RX fluctuates and the power transmission efficiency between the power transmitting coil and the power receiving coil decreases. Indicates power value. For example, when the GP is 5 watts, the TX transmits power so that it can output 5 watts to the load in the RX even if the positional relationship between the power transmitting and receiving coils fluctuates and the power transmission efficiency decreases.

TX and RX according to the present embodiment perform communication for device authentication and communication for power transmission control based on the WPC standard. TX and RX determine the above-described GP according to information indicating the state of device authentication obtained as a result of device authentication, and perform power transmission control so that power corresponding to the determined GP is transmitted and received. Note that GP is determined by negotiation executed by TX and RX in the Negotiation phase, which will be described later. The state of device authentication includes, for example, a state in which device authentication has been executed and failed, a state in which device authentication has been executed but failed, and a state in which device authentication cannot be executed because the TX or RX does not support device authentication. Including state. In this embodiment, TX and RX set the upper limit of GP to 15 watts when the device authentication state is a state in which device authentication has been executed and succeeded, and when the device authentication state is other than that, GP is limited to 5 watts. Note that the upper limit of GP is not limited to the combination of 15 watts and 5 watts, and any value can be used as long as the upper limit of GP when device authentication is successful is higher than the upper limit of GP in other states. may be In other words, it is assumed that power can be transmitted with a large GP only between TX and RX that have succeeded in device authentication. In this way, by determining the upper limit of the GP based on the device authentication status, the TX and RX that pass the predetermined test stipulated by the WPC standard, etc., and are recognized as capable of transmitting and receiving power with a large GP can be transmitted with a large GP only between In addition, by using device authentication that is authenticated by the user making a predetermined contract, rapid charging with a large GP is possible only in the RX owned by the user who has made the predetermined contract. You may do so. In the state where device authentication has failed, it is determined that the TX or RX may be a device that has not passed the predetermined test, and it is more likely than the state that does not support device authentication or the state that device authentication has not been executed. The upper limit of GP may be set to a smaller value. As a result, it is possible to prevent excessive power from being transmitted to a device or the like that is not compatible with receiving a large amount of power.

Communication for device authentication is communication performed between TX and RX when device authentication is performed. Device authentication may be performed in the form of TX authenticating RX, or in the form of RX authenticating TX. Furthermore, both TX and RX may mutually authenticate the other, and a state in which both authentications are successful may be defined as a state in which device authentication is successful. In this embodiment, TX authenticates RX.

In this embodiment, TX and RX perform communication for device authentication by out-of-band communication using antennas and frequencies different from wireless power transmission. Here, it is assumed that the out-of-band communication is performed using, for example, a communication method conforming to the Bluetooth (registered trademark) Low Energy (hereinafter referred to as “BLE”) standard. Also, TX operates in the Central role of BLE and RX operates in the Peripheral role of BLE, but these BLE roles may be reversed. In addition, the out-of-band communication may be performed by other communication schemes such as IEEE802.11 standard series wireless LAN (for example, Wi-Fi (registered trademark)), ZigBee, and NFC (Near Field Communication).

Next, communication for power transmission control based on the WPC standard executed between TX and RX will be described. The WPC standard defines a plurality of phases including a Power Transfer phase in which power transfer is performed and a phase before actual power transfer is performed, and necessary communication for power transmission control is performed in each phase. . The phases before power transmission include a Selection phase, a Ping phase, an Identification and Configuration phase, a Negotiation phase, and a Calibration phase. Note that the Identification and Configuration phase is hereinafter referred to as the I&C phase. In the Selection phase, the TX intermittently transmits Analog Ping and detects that an object exists within the power transmission range (for example, the power receiving device 102 or conductor piece is placed on the charging stand 103). In the Ping phase, the TX transmits a Digital Ping and receives a response from the RX that received the Digital Ping, thereby acknowledging that the detected object is the RX. In the I&C phase, the RX informs the TX of its identity and capability information. In the Negotiation phase, the GP value is determined based on the GP value requested by RX, the power transmission capability of TX, and the like. In the calibration phase, RX notifies the received power value to TX, and TX makes adjustments for efficient power transmission. In the Power Transfer phase, control is performed to continue power transmission and to stop power transmission due to an error or full charge. TX and RX perform communication for power transmission control by in-band communication in which signals are superimposed using the same antenna (coil) used for wireless power transmission based on the WPC standard. Note that the range in which in-band communication based on the WPC standard is possible between TX and RX is substantially the same as the range in which power transmission is possible, and is narrower than the communicable range in out-band communication. In FIG. 1, a range 104 represents a range in which wireless power transmission and in-band communication can be performed by the transmitting and receiving coils of TX and RX, and a range 105 represents a range in which TX and RX can perform out-band communication. ing. Range 105 is wider than range 104 . In the following description, the RX being “placed” means that the RX has entered the inside of the range 104, and actually includes the state where the RX is not placed on the charging base 103. shall be taken.

(Device configuration)
Next, configurations of the power transmitting device 101 (TX) and the power receiving device 102 (RX) according to this embodiment will be described. It should be noted that the configuration described below is merely an example, and part (or in some cases, all) of the configuration described may be replaced with another configuration that performs a similar function, or may be omitted. It may be added to the configuration described. Furthermore, one block shown in the following description may be divided into multiple blocks, or multiple blocks may be integrated into one block.

FIG. 2 is a diagram showing a configuration example of TX according to this embodiment. In one example, the TX includes a control unit 201, a power supply unit 202, a power transmission unit 203, a detection unit 204, a power transmission coil 205, a first communication unit 206, a second communication unit 207, a display unit 208, an operation unit 209, a memory 210, and , and a timer 211 .

The control unit 201 controls the entire TX by executing a control program stored in the memory 210, for example. In one example, the control unit 201 performs control necessary for device authentication and power transmission in TX. The control unit 201 may perform control for executing applications other than wireless power transmission. The control unit 201 includes one or more processors such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). Note that the control unit 201 includes hardware dedicated to specific processing, such as an application-specific integrated circuit (ASIC), and an array circuit such as an FPGA (Field Programmable Gate Array) compiled to execute predetermined processing. may be configured to include The control unit 201 causes the memory 210 to store information that should be stored during execution of various processes. Also, the control unit 201 can measure time using a timer 211 .

The power supply unit 202 supplies power necessary for control, power transmission, and communication to the entire TX. The power supply unit 202 is, for example, a commercial power supply or a battery.

The power transmission unit 203 converts the DC or AC power input from the power supply unit 202 into AC frequency power in the frequency band used for wireless power transmission, and inputs the AC frequency power to the power transmission coil 205 to receive power in the RX. Generate electromagnetic waves to Note that the frequency of the AC power generated by the power transmission unit 203 is about several hundred kHz (eg, 110 kHz to 205 kHz), which is different from the BLE communication frequency (2.4 GHz) used in outband communication. Based on an instruction from the control unit 201, the power transmission unit 203 inputs AC frequency power to the power transmission coil 205 so that the power transmission coil 205 outputs an electromagnetic wave for transmitting power to RX. Further, the power transmission unit 203 controls the intensity of the electromagnetic wave to be output by adjusting the voltage (transmission voltage) or current (transmission current) input to the power transmission coil 205 . Increasing the transmission voltage or transmission current increases the intensity of the electromagnetic wave, and decreasing the transmission voltage or transmission current decreases the intensity of the electromagnetic wave. In addition, based on an instruction from the control unit 201, the power transmission unit 203 performs output control of AC frequency power so that power transmission from the power transmission coil 205 is started or stopped.

The detection unit 204 detects whether an object exists and is placed in the range 104 based on the WPC standard. The detection unit 204 detects, for example, the voltage value or the current value of the power transmission coil 205 when the power transmission unit 203 transmits WPC standard Analog Ping through the power transmission coil 205 . Then, the detection unit 204 can determine that an object exists in the range 104 when the voltage is below the predetermined voltage value or the current value is above the predetermined current value. Whether the object is RX or other foreign matter is determined when a predetermined response to Digital Ping subsequently transmitted by in-band communication by first communication unit 206 is received. is determined to be

The first communication unit 206 performs control communication based on the WPC standard as described above by in-band communication with RX. The first communication unit 206 modulates the electromagnetic wave output from the power transmission coil 205 and transmits information to RX. The first communication unit 206 also acquires information transmitted by RX by demodulating the electromagnetic wave that is output from the power transmission coil 205 and modulated in RX. That is, the communication performed by the first communication unit 206 is superimposed on the power transmission from the power transmission coil 205 .

The second communication unit 207 communicates with RX for device authentication by outband communication. In addition, the second communication unit 207 may perform communication other than communication for device authentication. The second communication unit 207 has, for example, a modulation/demodulation circuit and a communication protocol processing function necessary for performing communication complying with the BLE standard.

The display unit 208 presents information to the user by any method such as visual, auditory, and tactile. The display unit 208 notifies the user of information indicating, for example, the state of TX and the state of the wireless power transmission system including TX and RX as shown in FIG. The display unit 208 includes, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, and other notification devices. The operation unit 209 has a reception function for receiving an operation for TX from the user. The operation unit 209 includes, for example, buttons, a keyboard, an audio input device such as a microphone, a motion detection device such as an acceleration sensor or a gyro sensor, or other input devices. A device such as a touch panel in which the display unit 208 and the operation unit 209 are integrated may be used. The memory 210 stores various information as described above. Note that the memory 210 may store information obtained by a functional unit different from the control unit 201 . The timer 211 measures time by, for example, a count-up timer that measures elapsed time from the start time, a count-down timer that counts down from a set time, or the like.

FIG. 3 is a diagram showing a configuration example of RX according to the present embodiment. For example, the RX includes a control unit 301, a battery 302, a power receiving unit 303, a detection unit 304, a power receiving coil 305, a first communication unit 306, a second communication unit 307, a display unit 308, an operation unit 309, a memory 310, and a timer 311. , and a charging unit 312 .

The control unit 301 controls the entire RX by executing a control program stored in the memory 310, for example. In one example, the control unit 301 performs control necessary for device authentication and power reception in RX. The control unit 301 may perform control for executing applications other than wireless power transmission. The control unit 301 includes one or more processors such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). Note that the control unit 301 includes hardware dedicated to specific processing, such as an application-specific integrated circuit (ASIC), and an array circuit such as an FPGA (Field Programmable Gate Array) compiled to execute predetermined processing. may be configured to include The control unit 301 causes the memory 310 to store information that should be stored during execution of various processes. Also, the control unit 301 can measure time using a timer 311 .

A battery 302 supplies the power required for control, power reception, and communication for the entire RX. Also, the battery 302 stores power received via the power receiving coil 305 . In the power receiving coil 305 , induced electromotive force is generated by the electromagnetic wave radiated from the power transmitting coil 205 of TX, and the power receiving unit 303 acquires the power generated in the power receiving coil 305 . The power receiving unit 303 acquires AC power generated by electromagnetic induction in the power receiving coil 305 . Then, the power receiving unit 303 converts the AC power into DC power or AC power of a predetermined frequency, and outputs the power to the charging unit 312 that performs processing for charging the battery 302 . That is, the power receiving unit 303 supplies power to the load in RX. The GP described above is the amount of power guaranteed to be output from the power receiving unit 303 .

The detection unit 304 detects whether or not the RX is placed within the range 104 where the power can be received from the TX, based on the WPC standard. The detection unit 304 detects, for example, the voltage value or current value of the power receiving coil 305 when the power receiving unit 303 receives a WPC standard Digital Ping through the power receiving coil 305 . The sensing unit 304 may determine that RX is resting on the range 104 if, for example, the voltage is below a predetermined voltage threshold or the current value is above a predetermined current threshold.

The first communication unit 306 performs control communication based on the WPC standard as described above by in-band communication with TX. The first communication unit 306 demodulates the electromagnetic wave input from the power receiving coil 305 to obtain information transmitted from the TX, and load-modulates the electromagnetic wave to superimpose the information to be transmitted to the TX on the electromagnetic wave. , TX. That is, the communication performed by the first communication unit 306 is superimposed on the power transmission from the power transmission coil 205 of TX.

The second communication unit 307 performs communication for device authentication with the TX by outband communication. In addition, the second communication unit 307 may perform communication other than communication for device authentication. The second communication unit 307 has, for example, a modulation/demodulation circuit and a communication protocol processing function necessary for performing communication complying with the BLE standard.

The display unit 308 presents information to the user by any method such as visual, auditory, and tactile. The display unit 308 notifies the user of, for example, the state of RX and the state of the wireless power transmission system including TX and RX as shown in FIG. The display unit 308 includes, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, and other notification devices. The operation unit 309 has a reception function for receiving an operation for RX from the user. The operation unit 309 includes, for example, buttons, a keyboard, a voice input device such as a microphone, a motion detection device such as an acceleration sensor or a gyro sensor, or other input devices. A device such as a touch panel in which the display unit 308 and the operation unit 309 are integrated may be used. The memory 310 stores various information as described above. Note that the memory 310 may store information obtained by a functional unit different from the control unit 301 . The timer 311 measures time by, for example, a count-up timer that measures elapsed time from the start time, a count-down timer that counts down from a set time, or the like.

(Processing flow)
Next, an example of the flow of processing executed by TX and RX will be described. In this embodiment, the TX and RX perform device authentication in advance with a partner device existing within a range where outband communication can be performed using outband communication. Here, the range in which out-band communication can be performed is wider than the range in which in-band communication can be performed as described above. For this reason, the TX and RX execute device authentication even when the RX is not placed on the TX (on the charging base 103), execution) can be stored. As a result, when the device authentication is completed in advance, the TX does not need to perform the device authentication after the RX is placed within the power transmission range, so power transmission can be started quickly. Also, the RX can recognize that there is a successfully authenticated TX within the range where out-band communication can be performed, and can notify the user of this recognition result. This eliminates the need for the user to unnecessarily place the RX on the TX when searching for a TX capable of fast charging. In the following, first, the flow of device authentication processing executed by TX and RX will be described, and then the flow of processing when non-contact charging is performed will be described. Note that the device authentication process and power transmission control process in TX can be performed in parallel. Similarly, device authentication processing and power reception control processing in RX can also be performed in parallel. That is, a TX can perform an authentication process with other surrounding RXs while transmitting power to any RX, and a RX can receive power from any TX with surrounding TXs. can perform authentication processing between

[Device Authentication Processing in Power Transmission Device]
FIG. 4 is a flow chart showing an example of the flow of device authentication processing executed by the TX. This processing can be realized by executing a program read from the memory 210 by the control unit 201 of the TX, for example. Note that at least part of the following procedures may be implemented by hardware. The hardware in this case can be realized by, for example, using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as FPGA from a program for realizing each processing step. In addition, this processing is performed in response to the TX being powered on, in response to the user of the TX inputting an instruction to start the contactless charging application, or in response to the TX being connected to a commercial power source and supplying power. Depending on what is being received, it can be executed. Moreover, this process may be started by other triggers.

TX first waits for Advertise including identification information of RX by BLE (using the second communication unit 207) (S401). For example, the TX performs a BLE scanning operation and waits for an advertising packet containing information indicating that the identification information of the RX is included in the packet and the identification information of the RX. For example, by setting the AD Type of the BLE advertising packet to a predetermined value, it is indicated that this packet contains the identification information of RX, and when the AD Type is the predetermined value, the identification information of RX is included in AD Data. Predefine what is included. By sharing this definition between TX and RX, it is possible to wait for an advertising packet containing the above information. Here, the RX identification information is information for identifying each individual RX. This RX identification information is, for example, the Manufacturer Code and Basic Device ID defined by the WPC standard. Also, the identification information of RX may be a Wireless Power ID or a Bluetooth Address unique to the second communication unit 307 of RX (hereinafter referred to as "BD_ADDR"). Note that when BD_ADDR is used as RX identification information, the identification information is included in the header of the advertising packet instead of AD Data.

Subsequently, TX establishes a BLE connection with RX, which is the source of the advertising packet, and performs device authentication using BLE communication (S402). TX establishes a BLE connection with RX by transmitting CONNECT_REQ, which is a BLE connection request, to BD_ADDR included in the header of the advertising packet from RX.

Here, the content of communication for device authentication performed between TX and RX will be described with reference to FIG. 9(A). Note that the device authentication in this embodiment is a challenge-response type device authentication using an electronic certificate. The TX acts as an initiator sending a challenge text to the RX, and the RX acts as a responder encrypting the challenge text received from the TX and sending it to the TX. First, TX sends a GET_DIGESTS message to RX (F901). GET_DIGESTS is a message requesting information on digital certificates possessed by the recipient (RX). RX sends DIGESTS to TX in response to GET_DIGESTS (F902). DIGESTS is information about an electronic certificate owned by the sender (RX).

Subsequently, TX sends a GET_CETTIFICATE message to RX requesting detailed information about the electronic certificate (F903). RX sends CERTIFICATE to TX in response to GET_CERTIFICATE from TX (F904). TX then transmits a CHALLENGE message including the challenge text to RX (F905), and RX transmits to TX a RESPONSE obtained by encrypting the challenge text received from TX (F906). When the validity of the RESPONSE received from RX is confirmed, TX transmits RESULT (Success) to RX (F907), and terminates device authentication. RESULT (Success) means that the validity of RESPONSE can be confirmed and device authentication has succeeded. If the device authentication fails, RESULT (Fail) is sent instead of RESULT (Success), and the device authentication process ends. When the initiator (TX) receives a message indicating that the counterpart device (RX) does not support device authentication communication, the initiator (TX) determines that the counterpart device does not support device authentication. Also, if the initiator (TX) does not receive a response during communication, it may retry by retransmitting a message to obtain the response, or if the partner device does not support device authentication. It may be determined that there is

Note that each of the above messages is transmitted and received by any of the predefined GATT service characteristics Read, Write, Notify, and Indicate in GATT communication in the BLE connection. When the device authentication communication is completed, the TX cuts off the BLE connection by sending LL_TERMINATE_IND of BLE. Note that the BLE connection may be disconnected from RX. Note that when the BLE connection is used by another application, the BLE connection may not be disconnected even after the device authentication communication ends. Also, prior to communication for device authentication, the TX can obtain information as to whether or not the RX supports device authentication in the BLE advertising packet or GATT communication. Then, if the RX does not support device authentication, the TX may determine that the device authentication is not supported and may not execute the communication of FIG. 9A. In this case, the TX may not send a BLE connection request. The information as to whether or not the device is compatible with device authentication may be used in combination with other information such as information indicating the name of the manufacturer. For example, when information such as a predetermined manufacturer name is acquired in a BLE advertising packet or GATT communication, it may be determined that device authentication is supported.

In the above description, the case where TX performs device authentication of RX was described, but RX may perform device authentication of TX. Mutual authentication that performs authentication may be performed. If TX and RX authenticate each other, the reliability of device authentication can be further enhanced. By reversing the roles of TX and RX in FIG. 9A (by operating RX as an initiator and operating TX as a responder), RX can perform device authentication of TX.

Returning to FIG. 4, the TX associates the device authentication status obtained as a result of the device authentication processing of S402 with the identification information of the RX, which is the partner device of the device authentication processing, and stores it in the memory 210 (S403). The TX determines whether or not there has been a user operation instructing to end the device authentication process (S404), and if there has been such a user operation (YES in S404), the process of FIG. 4 ends. On the other hand, if there is no user operation for ending such device authentication processing (NO in S404), the TX repeats the processing of S401 to S403. In S401, the TX may refer to the memory stored in the previous S403 and ignore the advertising packet from the RX that has already performed communication for device authentication. As a result, the TX can not repeat device authentication with the same RX, suppresses the occurrence of unnecessary communication, and performs device authentication with other RXs existing in the range 105 that have not been executed. Communication for device authentication can be performed.

FIG. 10 shows an example of information (correspondence information 1000) stored in S403. The correspondence information 1000 is information in which the identification information of the RX with which the TX has performed the communication of the device authentication process by the process of FIG. 4 and the information indicating the authentication status thereof are associated with each other. In S403, the TX registers, as information elements of the correspondence information 1000, identification information of the RX and information indicating the state of device authentication. Note that the correspondence information 1000 in FIG. 10 indicates that device authentication has succeeded between TX and RX whose identification information is AAAA and whose identification information is CCCC. Further, the correspondence information 1000 indicates that the device authentication failed with the RX with the identification information of BBBB, and the RX with the identification information of DDDD supported the device authentication. RXs not registered in the correspondence information 1000 are RXs for which device authentication has not been executed with the TX, RXs for which a predetermined period of time has elapsed after execution of device authentication, or registered RXs, as will be described later. is the RX whose information has been erased in response to the number of . The TX can determine that an RX that is not registered in the correspondence information 1000 is a device that has not yet been authenticated.

Note that the correspondence information 1000 may be partially or wholly erased at timings such as when the TX power is turned off, at the time of a termination operation, after charging is completed, and at predetermined intervals. In addition to the identification information and authentication status of each RX, the TX associates and stores information on the time when communication for device authentication was performed or information on the expiration date, and based on the current time and those information, Information that has passed a certain period of time after being registered may be deleted. Also, if the advertising packet or GATT communication from RX contains information indicating a request for re-authentication, TX may erase the information on that RX. As a result, the TX can update the device authentication status of the RX with which the device authentication communication was performed in the past to the latest status. Also, when the size of the corresponding information 1000 becomes equal to or larger than a predetermined size, the TX may erase part or all of the registered information of the RX. At this time, the TX can erase the old one based on the time information mentioned above. As a result, it is possible to prevent the memory 210 from overflowing due to an increase in the size of the correspondence information 1000 . Also, as the information indicating the authentication status, instead of or in addition to success, failure, and non-compliant, upper limit values of GPs corresponding to these statuses may be registered. In addition, the TX may also register the BD_ADDR of each RX so that it can be used as a destination for BLE connection requests when establishing a BLE connection with that RX later. This allows the TX to establish a connection in a short time when it becomes necessary to establish a BLE connection with the RX.

[Device Authentication Processing in Power Receiving Device]
Next, an example of the flow of device authentication processing executed by RX will be described with reference to FIG. This processing can be implemented by executing a program read from the memory 310 by the control unit 301 of the RX, for example. Note that at least part of the following procedures may be implemented by hardware. The hardware in this case can be realized by, for example, using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as FPGA from a program for realizing each processing step. This process may be executed in response to the power of the RX being turned on, or in response to the user of the RX inputting an instruction to start the contactless charging application. Moreover, this process may be started by other triggers.

First, RX performs advertisement including identification information of its own device in BLE, and waits for establishment of BLE connection (S501). The RX, for example, repeatedly and intermittently transmits an advertising packet containing information indicating that identification information of its own device is included in the packet and identification information of its own device. Then, the RX receives a BLE connection establishment request CONNECT_REQ from the other device (TX) that received the advertising packet, thereby establishing a BLE connection with the TX.

After the BLE connection is established, the RX performs the device authentication communication described with reference to FIG. 9A in the BLE connection (S502). If the RX succeeds in device authentication in S502 (YES in S503) and the detection unit 304 does not determine that its own device is placed on the TX (NO in S504), the display unit 308 displays the device nearby for authentication. Notify the user that there is a successful TX (S506). As a result, the user has succeeded in device authentication with the RX owned by the user, and can recognize that there is a power transmitting device in the vicinity that can rapidly charge the RX using a large amount of power. can. After that, RX advances the process to S505. Also, if the device authentication in S502 fails (NO in S503), or if the device authentication succeeds (YES in S503) and its own device is placed on the TX (YES in S504) does nothing and advances the process to S505. In S505, RX determines whether or not there has been a user operation instructing to end this process, and if there has been such a user operation (YES in S505), the process of FIG. 5 ends. On the other hand, if there is no user operation indicating to end the process (NO in S505), RX returns the process to S501. This allows the RX to communicate with other TXs for device authentication. Note that the RX may perform device authentication communication again with the same TX. However, even when performing device authentication with the same TX, RX may not perform device authentication again for a predetermined period after performing communication for device authentication last time.

Here, examples of screens displayed by the display unit 308 in S506 will be described with reference to FIGS. 11A to 11G. Note that although FIGS. 11A to 11G illustrate an example in which the RX has a display such as a smartphone and the display unit 308 displays information on the display, the present invention is not limited to this. In other words, the information may be presented by outputting text information by voice as shown in at least one of FIGS. 11(A) to 11(G). For example, when S506 is executed, RX can display a display such as that shown in FIG. 11A on the full screen or in a pop-up window. In addition, as in the case of notification of reception of e-mail, etc., as shown in FIG. You can display a string similar to . Note that the operating system is a program that serves as a base when the control unit 301 executes the processing of FIG. 5, FIG. 7 described later, and other processing.

Further, RX may display detailed information about TXs present in the vicinity (for example, within the BLE communication range), as shown in FIG. 11(C). Here, of the information shown in FIG. 11C, information 1121 indicates the name of TX. The name of TX can be obtained from TX by any of Read, Write, Notify, and Indicate of predefined GATT service characteristics in GATT communication in the BLE connection established in S502. This GATT communication is performed before and after device authentication communication. Information 1122 indicates the distance from RX (own device) to TX. For example, the distance is displayed by increasing the number of bars as the distance is shorter. The RX control unit 301 causes the second communication unit 307 to transmit the HCI_Read_RSSI command defined by the BLE standard. Then, the control unit 301 acquires the reception intensity (RSSI) of radio waves for BLE communication from the TX via the second communication unit 307 . Since the value of RSSI is generally inversely proportional to the square of the distance to TX in an environment close to free-space propagation, control section 301 identifies the distance based on the value of RSSI, and displays the information on display section 308. can be displayed. Note that, for example, the RX may acquire information indicating the location of the TX from the TX. The RX can then estimate the distance between it and the TX based on its own position and the TX's position. Also, the information 1122 may display information on the reception strength of the radio wave sent from the TX instead of the distance to the TX. Information 1123 represents the upper limit of GP. As described above, in this embodiment, when the device authentication is successful, the GP is set to 15 watts, so the information "15 W" is displayed here. Since this numerical value is defined by the WPC standard, the RX can store the numerical value for each state of device authentication in the memory 310 in advance. It should be noted that it is not necessary to display the watts as shown in FIG. 11(C). For example, if the upper limit of the GP is 15 watts, a character string representing the speed of charging, such as "rapid charge possible", if the upper limit of GP is 5 watts, "rapid charge not possible", etc., instead of or in addition to the watt display may be displayed. Information 1124 is the expected charging time. RX can calculate and display the expected charging time from, for example, the value of GP, the remaining amount of battery 302, and the efficiency of charging unit 312. FIG. In addition, the RX retains in the memory 310 information on the required charging time obtained by measuring combinations of a plurality of GP values and the remaining amount of the battery 302 in advance. You may estimate the time and display the result. By performing the display as shown in FIG. 11C, the amount of TX information that the user can obtain increases, so convenience can be improved. Note that if the distance between the RX and the TX is estimated to exceed a predetermined value, the information about the TX may not be displayed. Furthermore, when the position of the TX can be specified, the RX displays information on the position where the TX exists (for example, a map that allows the position of the TX to be specified or information indicating the direction in which the TX exists) on the display unit 308. You may let In addition, in the same manner as the TX name is obtained by BLE as described above, RX obtains, for example, advertisement character string information from TX, and based on this obtained information, the information in FIG. 11 (D) Information such as 1131 may be displayed. As a result, it is possible to realize a business model that provides a contactless charging environment to attract more customers. In addition, for example, RX acquires information on "AA store" from TX and information for specifying fixed phrases to be used (for example, "You can charge, please come to the store"), and based on these information , may generate the information to be presented.

Further, when the RX repeats the processing of S501 to S505 and has performed device authentication with a plurality of TXs, the RX may display a list of information on the plurality of TXs as shown in FIG. 11(E). In FIG. 11(E), each row indicates information of one TX. Information about each TX is obtained in a similar manner as described with respect to FIG. 11(C). In FIG. 11E, information 1141 indicates that the name of the first TX is "charging stand XX" and that this TX is located at a distance of five bars. In addition, FIG. 11E shows whether or not quick charging is possible according to the upper limit of GP determined according to the authentication status. For example, charging base XX has a GP upper limit of 15 watts corresponding to successful authentication, indicating that fast charging is possible. The RX further acquires (for example, additionally) information indicating whether power is being transmitted from the TX to another RX, information indicating the power transmission capability of the TX, or information on the power transmission reserve, and based on that information, , information 1142 may indicate "in use". For example, an RX may indicate "busy" when the TX is transmitting to another RX. In addition, when the TX is transmitting power to another RX and the TX does not have the power transmission capacity to transmit power to multiple RXs in parallel, or when the TX has insufficient power transmission capacity Medium” can be displayed. On the other hand, the RX can display the distance between the TX and the RX, similar to the information 1141, when the TX is in a state where it can transmit power with sufficient power to the RX. Note that when displaying a list of information on a plurality of TXs as in FIG. 11E, even if authentication fails in S503 and the result is NO in S503, the information on the TX may be displayed. The information 1143 indicates that the TX with the name “charging stand zz” fails authentication, the upper limit of GP is 5 W, and low-speed charging is performed when placed on this TX. As described above, by notifying information of a plurality of TXs, it is possible to give more choices to the user who is looking for a charging stand, and improve convenience. In addition, if there is a TX that does not support device authentication, the same information as the TX that failed authentication may be presented, or information about such a TX that does not support device authentication should not be presented. can be Further, information may be presented in a list as shown in FIG. 11(E) for TXs that do not support device authentication, and information may not be presented for TXs for which device authentication has failed.

Also, a TX that fails authentication may be a device that has not passed a predetermined test. Therefore, when the authentication fails in S503, RX can display a predetermined character string as shown in FIG. 11(F) to alert the user not to use such TX. Further, if the authentication is not successful even after repeating the processing of S501 to S505 for a predetermined number of times or for a predetermined period of time, the user may be notified to that effect by a display as shown in FIG. 11(G). As a result, it is possible to prevent the user from continuously searching for a charging stand in a situation where there is no charging stand capable of rapid charging nearby. Although FIGS. 11A to 11G are described as separate screen display examples, they may be used in combination. For example, information about TX as shown in FIG. 11(C) and information of character strings obtained from TX as shown in FIG. 11(D) may be presented at the same time. Alternatively, the icon shown in the notification area as shown in FIG. 11B and the information shown in FIG. 11C may be presented at the same time. Also, in this case, for example, the information in FIG. 11C may be cleared after a certain period of time has passed since it was presented, and the display may transition to a state in which only the icon in FIG. 11B is displayed. In this manner, the screen examples of FIGS. 11A to 11G can be used in combination as appropriate.

The RX may always execute the device authentication processing in FIG. 5 (for example, while its own device is powered on), or may be triggered by a predetermined user operation received via the operation unit 309. You may At this time, as shown in FIG. 12A, the RX displays information based on predetermined conditions such as the remaining amount of the battery 302 of its own device on the display unit 308, and selects an option 1211 to prompt the user to perform the processing in FIG. You may choose whether to execute Further, as shown in FIG. 12(B), the RX may automatically start the processing of FIG. An option 1221 may be displayed for allowing the user to select whether to enable the function to activate or not. Note that the conditions in FIG. 12B may be set by a user operation. In addition, the condition here is the condition regarding the remaining amount of the RX battery 302, but it may be, for example, a time condition such as "every XX minutes", or it may be geographically moved more than a predetermined distance. It may be a position-related condition such as , or other conditions may be used. Also, as shown in FIG. 12(C), the RX displays an icon 1231 in a notification area similar to that for notifying the reception of an e-mail, thereby indicating whether or not the device authentication process in FIG. 5 is being executed. You may make it represent whether. The RX may display this icon 1231 together with the icon 1111 in FIG. 11(B), as shown in FIG. 12(C). For example, when the device authentication process is started with a user operation as a trigger, the RX may display as shown in FIG. 12(D) until a TX that succeeds in device authentication is found. Although the examples in which the information in FIGS. 12A to 12D are visually displayed have been described, as long as the information to be presented is conveyed to the user, the screen display can be replaced with or in addition to this. Alternatively, information may be presented by voice output or vibration output.

With the device authentication processing as described above, the TX can store information on the state of device authentication with the nearby RX in the memory 210 as shown in FIG. In addition, the RX can notify the user via the display unit 308 that the TX that has succeeded in device authentication exists in the vicinity of its own device. Note that when the power transmission capacity is less than a predetermined value (for example, less than 15 watts) such as when power is being transmitted to a certain RX, the TX does not establish a BLE connection even if it receives an advertisement packet from another RX, or , device authentication may not be performed. That is, the TX can establish a BLE connection and perform device authentication in response to receiving an advertisement packet from another RX only when the remaining power transmission capacity is equal to or greater than a predetermined value. As a result, it is possible to suppress the display of the information of the TX that does not have the spare capacity for quick charging on the display unit 308 of the RX.

[Power transmission control processing in power transmission device]
Next, the flow of power transmission/reception control processing will be described. FIG. 6 shows an example of the flow of power transmission control processing executed by the TX. This processing can be realized by executing a program read from the memory 210 by the control unit 201 of the TX, for example. Note that at least part of the following procedures may be implemented by hardware. The hardware in this case can be realized by, for example, using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as FPGA from a program for realizing each processing step.

In this process, the TX first executes the processes specified as the Selection phase and the Ping phase of the WPC standard, and waits for the RX to be placed (S601). TX repeats and intermittently transmits WPC-standard Analog Ping to detect an object existing within a power transmission range. Then, when TX detects that an object exists within the transmittable range, it transmits a Digital Ping, and when there is a predetermined response to the Digital Ping, the detected object is RX, and RX is It determines with having been mounted in the charging stand 103. FIG.

When the TX detects that the RX is placed, the TX acquires identification information from the RX through in-band communication in the I&C phase defined by the WPC standard (S602). FIG. 9B shows the communication flow in the I&C phase. In the I&C phase, RX sends an Identification Packet (ID Packet) to TX (F911). The ID packet stores information elements capable of specifying the supported WPC standard version in addition to the manufacturer code and basic device ID, which are identification information for each individual RX. RX further transmits a Configuration Packet to TX (F912). The configuration packet includes Maximum Power Value, which is a value specifying the maximum power that the RX can supply to the load, and information indicating whether or not the RX has the Negotiation function of the WPC standard. When TX receives these packets, it sends an ACK (F913) and the I&C phase ends. Note that the TX may acquire the identification information of the RX by a method other than communication in the I & C phase of the WPC standard, and the identification information of each RX individual is a wireless power ID, BD_ADDR, etc. It may be any other identifiable information.

In S602, the TX may further acquire information on whether the RX supports communication for device authentication and other information from the RX. The TX may also determine which communications the RX supports from the version number of the WPC standard identified by the ID Packet described above.

The TX checks whether the RX identification information acquired in S602 is stored in the memory 210 as an information element of the correspondence information 1000 (S603). In S603, it may be determined whether or not the identification information corresponding to the identification information acquired in S602 is stored in the memory 210 instead of the identification information itself acquired in S602. For example, it may be determined whether the hash value of the identification information acquired in S603 is stored in the memory 210 . Then, if the identification information of RX is stored in the memory 210 (YES in S603), the TX reads from the memory 210 information on the state of device authentication associated with the identification information (S604), and the process proceeds to S605. proceed. If the identification information of RX is not stored in memory 210 (NO in S603), TX determines that device authentication has not been performed, and advances the process to S605. If the identification information of RX is not stored in memory 210, TX performs device authentication communication in FIG. may proceed. Also, the TX may update the correspondence information 1000 using the result of this device authentication. As a result, the TX can perform device authentication with the RX that does not have an out-of-band communication function such as BLE. Further, when the identification information of RX is not stored in the memory 210, TX waits for a predetermined time for device authentication to be executed in the device authentication processing of FIG. If performed, the process may proceed to S605 while holding the result. In this case, if a predetermined time has passed without device authentication being performed, TX may perform device authentication communication in in-band communication as described above, or RX does not support device authentication communication. It may be determined that Note that, when the TX acquires the BD_ADDR in S602, the TX may transmit a BLE connection request to the BD_ADDR to establish a BLE connection without waiting for advertisement and perform device authentication. As a result, a BLE connection can be established with an RX that supports device authentication by BLE, but device authentication has not been executed at the time of S603, and device authentication can be performed. In addition, TX acquires information as to whether it supports communication for device authentication in S602, and for RXs that do not support communication for device authentication, in-band communication or out-of-band communication as described above is performed. A trial of communication for device authentication by band communication may be omitted.

After that, the TX decides the GP through negotiation with its RX based on the authentication status, the RX's request, and its power transmission capability (S605). In S605, communication of the Negotiation phase of the WPC standard as shown in FIG. 9C is performed. First, RX notifies the requested GP value by transmitting a Specific Request to TX (F921). The TX determines whether or not to accept the request based on the power transmission capability of its own device and the authentication status of the RX that sent the Specific Request, and transmits an ACK if accepted or a NACK if not accepted to the RX. (F922). Here, TX accepts the request of RX when the size of GP requested by RX is a size that can be transmitted by the power transmission capability of its own device and is equal to or less than the upper limit of GP based on the authentication status. . That is, TX takes the value of GP as requested by RX. On the other hand, TX will not accept RX's request if the size of GP requested by RX is not achievable by its power transmission capability or if it exceeds the upper limit of GP based on authentication status. . In this case, the TX may, for example, determine a small value predefined in the WPC standard as the value of GP. Note that TX may determine another small value as the value of GP at this time. These small values are previously stored in the TX's memory 210 in one example. In addition, TX is capable of transmitting power simultaneously to multiple RXs and is already transmitting power to another RX. may determine the value of GP. Note that in S605, not only communication in the Negotiation phase of the WPC standard, but also other procedures for determining the GP based on the state of device authentication between TX and RX may be executed. In addition, when the TX acquires information indicating that the RX does not support the Negotiation phase (for example, in S602), the TX does not perform communication in the Negotiation phase, and sets the value of the GP (for example, ) may be a small value.

After determining the GP, the TX performs calibration (S606) and power transmission (S607) until full charge based on the GP. Calibration is a process of adjusting the correlation between the power transmitted by the TX to the RX and the value measured inside the TX by the TX and the value of the received power measured inside the RX. The TX performs this processing by processing the Calibration phase of the WPC standard. Moreover, power transmission is performed by processing of the Power Transfer phase of the WPC standard. The calibration and power transmission in S606 and S607 are the same as in the prior art, so detailed descriptions are omitted here. Note that the calibration and power transmission in S606 and S607 may be performed by a method other than the WPC standard.

After that, the TX terminates the processing of FIG. 6 if there is an end operation by the user (YES in S608), and while there is no such operation (NO in S608), Then, the process returns to S601.

[Power Receiving Control Processing in Power Receiving Device]
Next, an example of the flow of power reception control processing executed by RX will be described with reference to FIG. This processing can be implemented by executing a program read from the memory 310 by the control unit 301 of the RX, for example. Note that at least part of the following procedures may be implemented by hardware. The hardware in this case can be realized by, for example, using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as FPGA from a program for realizing each processing step.

After starting the power reception control process, the RX executes processes defined as the Selection phase and the Ping phase of the WPC standard, and waits for its own device to be placed on the TX (S701). The RX detects that it has been placed on the TX, for example by detecting a Digital Ping from the TX. When RX detects that its own device is placed on TX, it transmits information including identification information of its own device to TX by in-band communication by ID Packet and Configuration Packet described using FIG. 9B (S702). Note that the RX identification information may be transmitted by a method other than communication in the I & C phase of the WPC standard, and other identification information such as BD_ADDR may be used as long as it is information that can identify each individual RX. may Also, RX may transmit information other than identification information to TX in S702.

RX then transmits the requested GP value to TX, waits for a response from TX, and determines the GP (S703). In S703, communication of the Negotiation phase of the WPC standard as described with reference to FIG. 9C is performed. If the response from TX is ACK, RX sets the GP value to the same value as the requested GP, and if the response from TX is NACK, the GP value is defined in advance by the WPC standard. small value. Note that if the response from TX is a NACK, another small value may be used as the value of GP. Note that in S703, the GP may be determined by another method based on the state of device authentication between TX and RX, which is different from communication in the Negotiation phase of the WPC standard. Also, if the RX transmits information indicating that it does not support the Negotiation phase in S702, it may not perform communication in the Negotiation phase and set the value of GP to a small value predefined by the WPC standard. Any of the above small values may be stored in memory 310 in advance, for example.

After determining the GP, the RX performs calibration (S704) and power reception (S705) until full charge based on the GP. Calibration and power reception are performed by the WPC standard Calibration phase process and the Power Transfer phase process, but processes similar to these may be performed by procedures other than the WPC standard. The RX determines whether or not the user has performed an operation to terminate this process (S706), and if such an operation has been performed (YES in S706), the process of FIG. If not (NO in S706), the process returns to S701.

[System operation]
The operation sequence of the device authentication process and power transmission/reception control process between TX and RX described with reference to FIGS. 4 to 7 will be described with reference to FIG. In FIG. 8, it is assumed that time flows from top to bottom. Also, in the initial state, it is assumed that the user carrying the RX is outside the TX and BLE communication range 105 . It is also assumed that RX has identification information of "CCCC" and is an RX that requires 15 watts as a GP. In addition, the TX has the ability to transmit GP as 15 Watts, with a GP cap of 15 Watts for RXs with successful GP authentication and a GP cap of 5 Watts for other RXs, It is assumed that power transmission is performed.

First, TX waits for an object to be placed by Analog Ping while waiting for advertisement from RX (S401, S601, F801). On the other hand, RX waits for BLE connection while advertising, and concurrently waits for placement on TX (S501, S701, F802). In addition, in FIG. 8, "ADV_IND" means Advertising Indication, which is an advertising packet. After that, it is assumed that the user carrying the RX moves into the range 105 (F803). It is assumed that RX is not placed on range 104 at this point. Since BLE communication can be performed in range 105, TX receives an advertising packet of RX (F804), transmits a connection request (F805), and establishes a BLE connection. Thereafter, device authentication is performed between TX and RX (S402, S502, F806). RX identification information “CCCC” is notified from RX to TX by an advertising packet (F804). After communication for device authentication, the BLE connection is disconnected (F807).

Here, in this example, it is assumed that authentication has succeeded in F806. Therefore, the TX stores the result of "successful authentication" together with "CCCC", which is the identification information of RX, in the memory 210 (S403, F808). In the memory 210, the identification information CCCC and the information "authentication success" are stored in association with each other like the correspondence information 1000 in FIG. On the other hand, since the RX has been successfully authenticated (YES in S503) and is not placed on the charging base 103 (NO in F504), it notifies the user that there is a power transmitting device that has been successfully authenticated nearby. (S506, F809).

Here, since the TX is performing the power transmission control processing in FIG. F810). After that, when the user places the RX whose identification information is CCCC in the range 104 where the TX can transmit power (F811), the TX detects the placement of the object by Analog Ping (S601, F812, F813), and digital Ping is sent (F814). RX detects from this Digital Ping that it is placed in range 104 where it can receive power from TX (S701, F815). Subsequently, through in-band communication between TX and RX, RX notifies TX of identification information “CCCC” of RX (S602, S702, F816). Here, in F808, the memory 210 of the TX stores the result of "successful authentication" as the authentication status information with the RX whose identification information is "CCCC", like the correspondence information 1000 in FIG. Therefore, TX refers to the memory 210 and recognizes that the authentication has succeeded with the RX whose identification information is "CCCC" (S604, F817). Therefore, the TX caps the GP for this RX at 15 Watts. Then, TX determines the GP to be 15 watts based on the determined upper limit value, the request for 15 watts GP from RX, and the transmission capability of the own device capable of achieving 15 watts GP ( S605, S703, F818). Then, TX and RX perform calibration (S606, S704, F819) for power transmission at the determined GP and power transmission (S607, S705, F820) for contactless charging.

In this processing example, in the BLE communication of F806, the identification information “CCCC” is notified from RX to TX, and in the in-band communication of F816, the same identification information “CCCC” is notified from RX to TX. is confirmed by That is, it is confirmed between TX and RX that the pair of TX and RX for which device authentication is performed by BLE communication and the pair of TX and RX for performing in-band communication and power transmission are the same pair. Therefore, TX can transmit power suitable for RX based on the result of device authentication in BLE.

In addition, since the device authentication process and the power transmission/reception control process are executed in parallel, during a period in which the user has not placed the RX with the identification information "CCCC" on the TX, for the device authentication of the TX and RX communication is performed (F806). That is, before the user places the RX with the identification information “CCCC” on the TX in F811, communication for device authentication is performed. It is notified that the device exists (F809). Also, after the user places the RX on the TX in F811, the permitted 15 watt transmission is performed between the TX and RX that have successfully performed device authentication without further device authentication in F816-F820. . Therefore, by the above-described procedure, it is possible to notify the user of the RX that there is a TX in the vicinity of the RX that has been successfully authenticated and that is capable of rapid charging, thereby improving convenience. In addition, since power transmission and reception can be started without performing device authentication after the RX is placed on the TX, the time from the placement of the RX to the start of charging can be shortened.

In addition, although this embodiment demonstrated that communication for power transmission control based on a WPC standard was performed by in-band communication, it is not restricted to this. For example, part or all of communication other than notification of identification information of RX from RX to TX in the ID packet of the I&C phase (S602, S702) may be performed by out-of-band communication (BLE). Even in this way, the TX can correctly recognize the device authentication state corresponding to the identification information of the RX placed in the range 104 in S604, and transmit power to the RX with appropriate power. Note that the ID packet in the I&C phase may also be transmitted through outband communication as long as it is possible to determine that the RX for which device authentication has been performed through outband communication and the placed RX are the same. That is, for example, as long as the same identification information as the RX identification information obtained in out-band communication at the time of device authentication can be obtained in in-band communication, what is the transmission/reception method of the identification information and other communication for power transmission/reception control? may be done as follows. Note that when part of the communication for power transmission control is performed by BLE, the BLE connection may be disconnected if the BLE connection is in progress when the placement of the RX in the range 104 is detected in S601 and S701. Then, in S602 and S702, TX and RX may notify BD_ADDR of RX by in-band communication, and TX may transmit a BLE connection request with that BD_ADDR. As a result, it is possible to suppress the problem of cross-connection in which communication for power transmission control is performed using the BLE connection in a state where the RX is BLE-connected to a TX different from the TX on which it is placed.

(Other embodiments)
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in the computer of the system or apparatus reads and executes the program. It can also be realized by processing to It can also be implemented by a circuit (for example, ASIC) that implements one or more functions.

101: power transmission device, 102: power reception device, 301: control unit, 304: detection unit, 306: first communication unit, 307: second communication unit, 308: display unit

Claims (27)

A power receiving device,
a power receiving means for receiving power from a power transmitting device by wireless power transmission;
a communication means for performing communication in a communicable range wider than a range in which the power receiving means can receive power in the wireless power transmission;
Communication is started while the power receiving device has entered the communicable range and the power receiving device has not been detected by the power transmitting device in the wireless power transmission , and is authenticated with the power transmitting device by the communication means . presenting means for presenting to a user information indicating that the power transmitting device exists, at least based on the fact that the communication for authentication including the process of communicating information about the document is performed;
A power receiving device comprising: The presentation means presents information indicating that the power transmission device exists when the authentication with the power transmission device is successful.
The power receiving device according to claim 1, characterized in that: the presentation means presents information by displaying visual information on a screen;
3. The power receiving device according to claim 1, wherein: The presenting means presents information indicating the presence of the power transmitting device in a notification area defined by an operating system on the screen.
4. The power receiving device according to claim 3, characterized in that: The information indicating the presence of the power transmission device includes the name of the power transmission device, the reception intensity of radio waves transmitted from the power transmission device or the distance between the power transmission device and the power reception device based on the reception intensity, and including at least one of information about the amount of power that the power receiving device can receive from the power transmitting device and information indicating the time required to charge the battery of the power receiving device;
The power receiving device according to any one of claims 1 to 4, characterized in that: The presentation means presents information indicating that the power transmission device exists and information based on a character string obtained from the power transmission device via the communication means.
The power receiving device according to any one of claims 1 to 5, characterized in that: The presenting means provides information indicating whether or not the power transmitting device is transmitting power to another power receiving device, or information obtained from the power transmitting device via the communication means, together with information indicating that the power transmitting device exists. presenting information based on information on the power transmission capacity or power transmission reserve of the power transmission device;
The power receiving device according to any one of claims 1 to 6, characterized in that: The presenting means presents information indicating that the power transmitting device that has failed the authentication exists.
The power receiving device according to any one of claims 1 to 7, characterized by: The presentation means presents information calling attention not to use the power transmission device that has failed the authentication as information indicating that the power transmission device that has failed the authentication exists.
The power receiving device according to claim 8, characterized by: The presenting means does not present information regarding the existence of the power transmission device when the authentication with the power transmission device fails.
The power receiving device according to any one of claims 1 to 7, characterized by: When the communication for the authentication cannot be performed with the power transmission device or the authentication with the power transmission device is not successful, the presentation means provides information indicating that the power transmission device does not exist. to present
The power receiving device according to any one of claims 1 to 7, characterized by: The communication means performs communication for the authentication with the power transmitting device existing within the communicable range in response to receiving a predetermined user operation.
The power receiving device according to any one of claims 1 to 11, characterized in that: further comprising means for displaying a screen for accepting the predetermined user operation;
13. The power receiving device according to claim 12, characterized by: The communication means performs communication for the authentication with the power transmitting device existing within the communicable range based on the satisfaction of a predetermined condition.
The power receiving device according to any one of claims 1 to 13, characterized in that: the predetermined condition is a condition regarding the remaining amount of the battery of the power receiving device;
15. The power receiving device according to claim 14, characterized by: further comprising means for displaying a screen for accepting a user operation as to whether or not to perform the communication for the authentication with the power transmitting device existing within the communicable range when the predetermined condition is satisfied. ,
16. The power receiving device according to claim 14 or 15, characterized in that: further comprising means for presenting information indicating whether communication for the authentication is being performed;
The power receiving device according to any one of claims 1 to 16, characterized in that: the communication means performs communication according to the Bluetooth Low Energy standard;
The power receiving device according to any one of claims 1 to 17, characterized by: The wireless power transmission complies with the standards of the Wireless Power Consortium,
The power receiving device according to any one of claims 1 to 18, characterized in that: The power receiving device according to any one of claims 1 to 19, wherein the communication for authentication is performed using an antenna different from an antenna used for the wireless power transmission. 21. The apparatus according to any one of claims 1 to 20, wherein the power receiving device operates as an initiator in the communication for authentication, and the power transmitting device operates as a responder in the communication for authentication. A powered device as described. The power receiving device according to any one of claims 1 to 21, wherein a GET_DIGESTS message and a GET_CERTIFICATE message are used in said communication for authentication. 2. The communication other than the communication for authentication is performed using an antenna used in the wireless power transmission, or is superimposed on the transmitted power transmitted from the power transmitting device. 23. The power receiving device according to any one of 22. 24. The power receiving device according to any one of claims 1 to 23, wherein the magnitude of received power in said wireless power transmission is determined based on a result of said authentication. The received power when charging the battery of the power receiving device with power from the power transmitting device that fails the authentication is higher than the received power when charging the battery with power from the power transmitting device that does not support authentication. 25. The power receiving device according to any one of claims 1 to 24, wherein the power receiving device is small. A control method executed by a power receiving device having power receiving means for receiving power from a power transmitting device by wireless power transmission, and communication means for performing communication in a communicable range wider than the power receiving range of the power receiving means in the wireless power transmission. and
Communication started while the power receiving device has entered the communicable range and the power receiving device has not been detected by the power transmitting device in the wireless power transmission, wherein the communication means communicates with the power transmitting device a presenting step of presenting to the user information indicating that the power transmitting device exists, at least based on the fact that the communication for authentication including the processing of communicating information about the certificate is performed. control method. A computer provided in a power receiving device having power receiving means for receiving power from a power transmitting device by wireless power transmission, and communication means for performing communication in a communicable range wider than the power receiving range of the power receiving means in the wireless power transmission , a program for executing the control method according to claim 26 .

Images