Power receiving apparatus, method performed by power receiving apparatus, and storage medium

Abstract

To provide a mechanism for efficiently storing identification information of a power transmission device.SOLUTION: A power reception device for wirelessly receiving power from a power transmission device includes an acquisition means for acquiring identification information of the power transmission device, an authentication means for authenticating the power transmission device, and a storage processing means for storing the identification information in a storage unit on the basis of an attribute of the identification information after authentication by the authentication means.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a power receiving device, a method performed by the power receiving device, and a program. [Background technology]

[0002] In recent years, technological development of wireless power transmission systems has been widespread. One of the technologies for wireless power transmission systems is the Qi standard, established as a wireless charging standard by the standardization organization Wireless Power Consortium (WPC), as disclosed in Patent Document 1, for example. In the Qi standard, power transmission and reception and the associated control communication are performed using magnetic induction. The Qi standard also discloses that authentication is performed between a power transmitting device and a power receiving device using the control communication. According to Patent Document 2, if authentication is successful, the power receiving device stores identification information of the power transmitting device. In this case, the power receiving device checks the identification information of the power transmitting device during subsequent charging. If the check results in the stored identification information, i.e., if authentication has been successful in the past, the process is omitted. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2015-56959 [Patent Document 2] Patent Publication No. 2020-188547 Summary of the Invention [Problem to be solved by the invention]

[0004] Patent Document 2 does not disclose an appropriate authentication control method that takes into consideration the type (category) of identification information. For example, there are various types of identification information, such as fixed type that is the same every time, and variable type that changes randomly each time. Therefore, if the stored identification information is not fixed type, problems such as an increase in processing time due to the storage of unnecessary identification information may occur.

[0005] The present disclosure has been made in consideration of at least one of the above-described problems, and an object of one aspect of the present disclosure is to provide a mechanism for efficiently storing identification information of a power transmitting device. [Means for solving the problem]

[0006] A power receiving device according to one aspect of the present disclosure is characterized by having a power receiving means for wirelessly receiving power from a power transmitting device, an acquisition means for acquiring identification information of the power transmitting device, an authentication means for authenticating the power transmitting device, and a storage processing means for storing the identification information in a storage unit based on attributes of the identification information after authentication by the authentication means. [Effects of the Invention]

[0007] According to one aspect of the present disclosure, it is possible to provide a mechanism for efficiently storing identification information of a power transmitting device. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of the configuration of a contactless charging system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram illustrating an example of the configuration of a power receiving device according to an embodiment of the present invention. [Figure 3] 1 is a block diagram illustrating an example of the configuration of a power transmission device according to an embodiment of the present invention. [Figure 4] 10 is a flowchart illustrating a process performed by a power receiving device according to the present embodiment. [Figure 5] 10 is a flowchart illustrating an authentication execution determination process performed by a power receiving device according to the present embodiment. [Figure 6] 10 is a flowchart for explaining authentication and identification information storage processing performed by the power receiving device according to the present embodiment. [Figure 7] 4 is a sequence diagram for explaining a first example of processing performed by a power transmitting device and a power receiving device according to the present embodiment. FIG. [Figure 8]10 is a sequence diagram for explaining a second example of processing performed by the power transmitting device and the power receiving device according to the embodiment. FIG. [Figure 9] FIG. 10 is a sequence diagram illustrating a third example of processing performed by the power transmitting device and the power receiving device according to the present embodiment. [Figure 10] FIG. 10 is a diagram showing a communication sequence of authentication according to the present embodiment. [Figure 11] 10 is a sequence diagram for explaining a modified example performed by the power transmitting device and the power receiving device according to the embodiment. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Note that not all of the features in the embodiments of the present disclosure are essential to the invention, and multiple features may be combined as desired. In the drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0010] [System Configuration] FIG. 1 is a diagram illustrating an example of the configuration of a wireless power transmission system according to an embodiment. In one example, the wireless power transmission system includes a power receiving device 101 and a power transmitting device 102. Hereinafter, for simplicity, the power transmitting device 102 may be referred to as a TX, and the power receiving device 101 may be referred to as an RX. The RX is, for example, an electronic device that receives power from the TX and charges a built-in battery. The RX includes a WPC function compliant with the Qi standard established by the Wireless Power Consortium (WPC) and also supports the authentication protocol of the standard. The TX is, for example, an electronic device that wirelessly transmits power to an RX placed on the device itself. The TX wirelessly transmits power to the RX via a power transmitting coil. In the following description, a smartphone is used as an example of the RX, and a charger is used as an example of the TX, but the present disclosure is not limited thereto. The RX and TX may be built into other devices (cameras, smartphones, tablet PCs, laptops, automobiles, robots, medical equipment, printers) and configured to supply power to those devices.

[0011] This system performs wireless power transmission using an electromagnetic induction method for contactless charging based on the Qi standard. That is, RX and TX perform wireless power transmission for contactless charging based on the Qi standard between the receiving coil of RX and the transmitting coil of TX. Note that the wireless power transmission method (contactless power transmission method) is not limited to the method defined by the Qi standard, and may be other methods such as electromagnetic induction, magnetic field resonance, electric field resonance, microwave, or laser. Furthermore, in this embodiment, wireless power transmission is used for contactless charging, but wireless power transmission may also be performed for purposes other than contactless charging.

[0012] In the Qi standard, the amount of power guaranteed when an RX receives power from a TX is specified by a value called Guaranteed Load Power (hereafter referred to as "GP"). GP indicates the power value guaranteed to be output to an RX load, such as a charging circuit, even if the relative positions of the RX and TX fluctuate and the power transmission efficiency between the receiving coil and the transmitting coil decreases. In addition, GP can be a load power level agreed upon through negotiation between the TX and RX. For example, if the GP is 15 watts, the TX transmits power by controlling it so that it can output 15 watts to the load in the RX, even if the relative positions of the receiving coil and the transmitting coil fluctuate and the power transmission efficiency decreases.

[0013] [Configuration of power receiving device] FIG. 2 shows an example of the configuration of the RX according to this embodiment. The RX includes a control unit 201, an NFC communication unit 202, a WPC communication unit 203, a power receiving coil 204, a power receiving unit 205, a detection unit 206, a charging unit 207, a battery 208, a notification unit 209, an operation unit 210, a memory 211, and a timer 212. The control unit 201 controls the entire smartphone. An example of the control unit 201 is a central processing unit (CPU) or a microprocessor unit (MPU). The control unit 201 can measure time using the timer 212. The control unit 201 performs control by executing a control program stored in the memory 211, for example. The control unit 201 includes one or more processors, such as a central processing unit (CPU) or a microprocessor unit (MPU). The control unit 201 may also be configured with hardware dedicated to a specific process, such as an application-specific integrated circuit (ASIC). Alternatively, the control unit 201 may be configured to include an array circuit such as an FPGA (Field Programmable Gate Array) compiled to execute predetermined processing.

[0014] The control unit 201 stores information to be stored while various processes are being executed in the memory 211. Note that in this embodiment, the control unit 201 is shown as a single component, but this is not limiting. For example, a WPC control unit that controls processes related to power reception with a power transmitting device in a power receiving device may be configured separately from the control unit 201. Alternatively, an NFC control unit that controls processes related to NFC (Near Field Communication) communication may be configured separately from the control unit 201. Alternatively, the WPC control unit and the NFC control unit may each be configured separately from the control unit 201. When the control unit 201 is configured as multiple separate units, the respective control units are connected to each other via communication interfaces, and data communication is possible.

[0015] The communication interface may be any interface that realizes data communication, such as I2C (Inter-Integrated Circuit) or GPIO (General Purpose Input / Output).

[0016] The NFC communication unit 202 is a hardware module that realizes NFC functions. Specifically, it realizes a card emulation mode that acts as a contactless IC card, a reader / writer mode for reading NFC tags, and a P2P mode for directly exchanging messages between NFC devices. For example, the card emulation mode can be used to enable electronic money payments.

[0017] The WPC communication unit 203 performs wireless power transmission communication based on the Qi standard with the TX communication unit 306. The WPC communication unit 203 demodulates the electromagnetic waves input from the power receiving coil 204 to acquire information transmitted from the TX, and performs load modulation of the electromagnetic waves to superimpose information to be transmitted to the TX onto the electromagnetic waves, thereby performing communication with the TX. In other words, the WPC communication unit 203 functions as at least a receiving means for receiving information.

[0018] The power receiving unit 205 receives AC power (AC voltage and AC current) generated by electromagnetic induction based on electromagnetic waves radiated from the power transmitting coil of TX via the power receiving coil 204. The power receiving unit 205 converts the AC power into DC or AC power of a predetermined frequency and outputs it to the detection unit 206. The power receiving unit 205 functions as a power receiving means.

[0019] The detection unit 206 detects that the RX is placed on the TX based on the Qi standard. For example, the detection unit 206 detects at least one of the voltage value and the current value of the power receiving coil 204 when the power receiving unit 205 receives a Qi standard Digital Ping via the power receiving coil 204. For example, the detection unit 206 can determine that the RX is placed on the TX when the voltage value is below a predetermined voltage threshold or when the current value exceeds a predetermined current threshold.

[0020] Charging unit 207 charges battery 208 with power supplied from power receiving unit 205. Charging unit 207 also starts or stops charging battery 208 based on the control of control unit 201, and further adjusts the power used to charge battery 208 based on the charge state of battery 208. When the power used by charging unit 207 changes, the power supplied from power receiving unit 205, i.e., the received power in RX, also changes accordingly. Charging unit 207 shown here is a load in RX.

[0021] The battery 208 supplies the entire RX with power required for control of each part of the RX by the control unit 201, and for power reception and communication. The battery 208 also stores the power received via the power receiving coil 204.

[0022] The notification unit 209 notifies the user of information by any method such as visually, audibly, or tactilely. The notification unit 209 notifies the user of, for example, the charging state of RX or the state related to power transmission of the wireless power transmission system including RX and TX as shown in Fig. 1. The notification unit 209 is configured to include, for example, a liquid crystal display, an LED (Light Emitting Diode), a speaker, a vibration generating circuit, or other notification devices.

[0023] The operation unit 210 has a receiving function for receiving an operation for RX from a user. The operation unit 210 is configured to include, for example, a voice input device such as a button, a keyboard, or a microphone, a motion detection device such as an acceleration sensor or a gyro sensor, or other input devices. Note that a device in which the notification unit 209 and the operation unit 210 are integrated, such as a touch panel, may also be used.

[0024] As described above, the memory 211 stores various types of information such as identification information and device configuration information, control programs, and the like. The memory 211 may store information obtained by a functional unit other than the control unit 201. The memory 211 may be configured with one or more memories such as a read-only memory (ROM) and / or a random access memory (RAM). In addition to memories such as a ROM and a RAM, the memory 211 may also use storage media such as a flexible disk, a hard disk, a solid-state drive (SSD), an optical disk, or a magneto-optical disk. In addition, storage media such as a compact disc (CD)-ROM, a recordable CD-R, a magnetic tape, a non-volatile memory card, or a digital versatile disc (DVD) may also be used.

[0025] The timer 212 measures time using, for example, a count-up timer that measures the elapsed time from the time of activation, or a count-down timer that counts down from a set time.

[0026] The control unit 201 may control RX in cooperation with a program stored in the memory 211 and an OS (Operating System).

[0027] [Configuration of power transmission equipment] 3 shows an example of the configuration of the TX according to this embodiment. The TX includes a control unit 301, a power supply unit 302, a power transmission unit 303, a detection unit 304, a power transmission coil 305, a communication unit 306, a notification unit 307, an operation unit 308, a memory 309, and a timer 310.

[0028] The control unit 301 controls the entire TX by executing a control program stored in the memory 309, for example. That is, the control unit 301 controls each functional unit shown in FIG. 3. The control unit 301 also controls power transmission control in the TX. The control unit 301 also controls the NFC function in the TX. The control unit 301 may also control the execution of applications other than wireless power transmission. The control unit 301 includes one or more processors, such as a CPU or MPU. The control unit 301 may be configured with a single processor, or, as described with reference to FIG. 2, a main control unit that controls the entire TX and a sub-control unit that controls power transmission processing and NFC communication may each be implemented by separate processors. The control unit 301 may also include hardware dedicated to specific processing, such as an application-specific integrated circuit (ASIC), or an array circuit, such as an FPGA, compiled to execute a predetermined processing. The control unit 301 stores information to be stored during execution of various processes in the memory 309. The control unit 301 may measure time using a timer 310.

[0029] The power supply unit 302 supplies the entire TX with power required for the control of the TX by the control unit 301 and for power transmission and communication. The power supply unit 302 is, for example, a commercial power supply or a battery. The battery stores power supplied from the commercial power supply.

[0030] The power transmitting unit 303 converts the DC or AC power input from the power supply unit 302 into AC frequency power in a frequency band used for wireless power transmission, and inputs the AC frequency power to the power transmitting coil 305 to generate electromagnetic waves for transmitting power to the RX. The frequency of the AC power generated by the power transmitting unit 303 is, for example, several hundred kHz (e.g., 110 kHz to 205 kHz). Based on instructions from the control unit 301, the power transmitting unit 303 inputs the AC frequency power to the power transmitting coil 305 so that the power transmitting coil 305 outputs electromagnetic waves for transmitting power to the RX. The power transmitting unit 303 also controls the intensity of the electromagnetic waves to be output by adjusting the voltage (power transmitting voltage) or current (power transmitting current), or both, input to the power transmitting coil 305. Increasing the power transmitting voltage or power transmitting current increases the intensity of the electromagnetic waves, and decreasing the power transmitting voltage or power transmitting current decreases the intensity of the electromagnetic waves. Furthermore, the power transmitting unit 303 controls the output of AC frequency power so as to start or stop power transmission from the power transmitting coil 305 based on instructions from the control unit 301. Furthermore, the power transmitting unit 303 notifies the control unit 301 of the current transmitted power, thereby enabling the control unit 301 to know the transmitted power at any timing. Note that the measurement of the transmitted power and the notification to the control unit 301 may be configured to be performed by a unit other than the power transmitting unit 303.

[0031] The detection unit 304 detects whether an object is placed on the TX based on the Qi standard. Specifically, the detection unit 304 detects whether an object is placed on the interface surface of the TX. For example, the detection unit 304 detects at least one of the voltage value and the current value of the power transmitting coil 305 when the power transmitting unit 303 transmits an Analog Ping of the Qi standard via the power transmitting coil 305. The detection unit 304 may also detect a change in impedance. Then, the detection unit 304 may determine that an object is placed on the TX when the voltage is below a predetermined voltage value or the current value exceeds a predetermined current value. Whether the object is an RX or another foreign object is determined based on the presence or absence of a predetermined response to a Digital Ping subsequently transmitted by the communication unit 306. That is, if the TX receives a predetermined response, the object is determined to be an RX; otherwise, the object is determined to be an object different from the RX.

[0032] The communication unit 306 performs control communication with the RX based on the Qi standard as described above. The communication unit 306 modulates the electromagnetic waves output from the power transmitting coil 305 and transmits information to the RX to perform communication. The communication unit 306 also demodulates the electromagnetic waves output from the power transmitting coil 305 and modulated by the RX to acquire information transmitted by the RX. That is, the communication performed by the communication unit 306 is superimposed on the electromagnetic waves transmitted from the power transmitting coil 305. The communication unit 306 functions as a transmitting unit that transmits at least power information (described later). The communication unit 306 also performs NFC communication and detects an NFC tag of a device to transmit power. In this case, the communication unit 306 functions as a detecting unit. Note that the communication unit 306 may be realized by a single piece of hardware, with a module that performs control communication based on the Qi standard and a module that performs NFC communication, or each may be realized by separate pieces of hardware.

[0033] The notification unit 307 notifies the user of information by any method such as visually, audibly, or tactilely. The notification unit 307 notifies the user of, for example, the charging state of the TX or information indicating the state of power transmission in the wireless power transmission system including the TX and RX as shown in Fig. 1. The notification unit 307 is configured to include, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, or other notification devices.

[0034] The operation unit 308 has a function of receiving operations for TX from the user. The operation unit 308 includes, for example, a voice input device such as a button, keyboard, or microphone, a motion detection device such as an acceleration sensor or gyro sensor, or other input device. Note that a device in which the notification unit 307 and the operation unit 308 are integrated, such as a touch panel, may also be used.

[0035] Memory 309 stores various information such as identification information and capability information, as well as control programs. The capability information includes information indicating whether or not the device has high-precision foreign object detection processing capability. Memory 309 may also store information obtained by a functional unit other than control unit 301. Timer 310 measures time using, for example, a count-up timer that measures the elapsed time from the time of activation, or a count-down timer that counts down from a set time.

[0036] [Processing in the power receiving device] 4 is a flowchart showing an example of the flow of processing executed by the RX. This processing can be realized by, for example, the control unit 201 of the RX reading out a program from the memory 211 and executing it.

[0037] Note that at least a part of the following procedures may be implemented by hardware. In this case, the hardware may be implemented by, for example, using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as an FPGA from a program for implementing each processing step. The same applies to the processes shown in FIGS. 5 to 10, which will be described later. This process may be executed in response to a command to start a contactless charging application input by the user of RX in response to RX being powered on and RX being started by power supply from the battery 208 or TX. This process may also be started in response to another trigger.

[0038] In S401, after starting processing, the RX executes processing defined as the Ping phase of the Qi standard and waits for its own device to be placed on the TX. The RX detects that it has been placed on the TX, for example, by detecting a Digital Ping from the TX. When the RX detects that its own device has been placed on the TX, in S402 it transmits the RX's identification information and capability information to the TX through communication in the Configuration phase defined in the Qi standard. Here, the RX's identification information includes the Manufacturer Code and Basic Device ID. The RX's capability information includes the following information:

[0039] - Information that can identify the supported Qi standard version Maximum Power Value (or Reference Power) is the value that specifies the maximum power that the RX can supply to the load. -Information indicating whether or not the Qi standard negotiation function is available.

[0040] However, this information is merely an example, and the identification information and capability information of the RX may be replaced by other information or may include other information. For example, the identification information may be any other identification information that can identify an individual RX, such as a Wireless Power ID. The RX may also transmit the identification information and capability information by a method other than communication in the configuration phase of the Qi standard. After transmitting the identification information and capability information, the RX starts communication in the negotiation phase defined in the Qi standard. After starting communication in the negotiation phase, the RX acquires identification information from the TX in S403.

[0041] Here, the identification information of the TX can be acquired by transmitting an acquisition request to the TX using a Qi-standard General Request (GRQ) data packet and receiving the information as a response to the acquisition request, but is not limited to this. For example, the acquisition request can be transmitted using a Qi-standard Specific Request (SRQ) data packet and received as a response, or the information can be acquired using any packet that the TX can transmit. The identification information of the TX is an ID that can identify the TX, and can be, for example, a unique (device-specific) ID associated with the individual TX, or a temporary ID generated by the TX at a predetermined timing. The predetermined timing can be, but is not limited to, when the power transmission process starts, when the identification information is transmitted, when a predetermined number of power transmission attempts is reached, after a predetermined time has elapsed, when a user issues a command to generate (or update), etc. Furthermore, the identification information of the TX can include information indicating the type of the identification information. For example, this can be a flag indicating whether the ID is device-specific (or a flag indicating whether the ID is temporary). In the case of a flag, the value of the flag can be stored in a field separate from the identification information and transmitted together with the identification information. Alternatively, the identification information may be assigned according to a predetermined rule, and whether it is a device-specific ID or not may be determined from the identification information itself. Furthermore, the identification information may include the expiration date of the ID, identification information indicating the manufacturer of the TX, etc.

[0042] Note that the temporary ID generated by the TX at a predetermined timing is the same as the unique (device-specific) ID linked to the individual TX in that it is an ID that can identify the TX. However, the temporary ID generated by the TX at a predetermined timing is different from the unique (device-specific) ID linked to the individual TX in that it is a variable type that changes at each predetermined timing (for example, a response to an acquisition request). The unique (device-specific) ID linked to the individual TX is, in principle, fixed and does not change. Note that an ID with a relatively long expiration date may be treated as a fixed type for the period until the expiration date.

[0043] After acquiring the identification information of TX, RX executes authentication execution decision processing in S404, which will be described later.

[0044] In S405, RX transmits the requested power value (requested value of transmission power) determined in S404 to TX, and determines the value of GP between RX and TX.

[0045] Once the RX has determined the GP, in S406 it transmits to the TX, through communication in the calibration phase defined in the Qi standard, information on a predetermined received power value so that the TX can derive the relationship between the transmitted power and the received power in a state where there is no foreign object.

[0046] Here, the information on the predetermined received power value includes the received power value in a light load state / Light Load and the received power value in a maximum load / Connected Load state. After transmitting the information on the received power value, RX starts receiving power through communication in the Power Transfer phase defined by the Qi standard in S407. After starting power reception, RX executes authentication and identification information storage processing in S408. The authentication and identification information storage processing will be described later.

[0047] In S409, RX determines whether or not redetermining the GP is necessary. Here, the determination of whether or not redetermining the GP is necessary can be made based on whether or not the required power value has been changed in S408.

[0048] If RX needs to redetermine GP (YES in S409), it proceeds to S410. On the other hand, if RX does not need to redetermine GP (NO in S409), it proceeds to S411. In S410, RX transmits the required power value to TX, and redetermines the GP value between RX and TX.

[0049] In S411, RX determines whether or not to stop receiving power. If RX determines to stop receiving power (YES in S411), it stops receiving power and ends this processing. On the other hand, if RX determines not to stop receiving power = to continue receiving power (NO in S411), it returns processing to S411.

[0050] Here, the decision as to whether to stop power reception can be made based on whether an error has occurred, whether the battery has reached full charge, etc., but is not limited to these. When RX stops power reception, it sends an End Power Transfer Data Packet of the Qi standard. This stops power transmission from TX, and the series of processes for contactless charging ends.

[0051] Next, an example of the flow of the authentication execution decision process executed by the RX in S404 will be described with reference to Fig. 5. In this process, the control unit 201 functions as a decision unit that decides whether or not to execute authentication.

[0052] In S501, RX determines whether the identification information of TX acquired in S403 is device-specific information. Here, the determination of whether the identification information of TX is device-specific information can be made based on information indicating the type included in the identification information. If the identification information of TX is device-specific information (YES in S501), RX proceeds to S502. On the other hand, if the identification information of TX is not device-specific information, that is, is temporary information (NO in S501), RX proceeds to S506.

[0053] In S502, the RX determines whether the identification information of the TX has been stored. Here, the determination of whether the identification information of the TX has been stored can be made by sequentially reading out the identification information stored in the memory 211 and comparing it to see if there is any identification information that matches the identification information of the TX acquired in S403. If the identification information of the TX has been stored (YES in S502), the RX proceeds to S503. On the other hand, if the identification information of the TX has not been stored (NO in S502), the RX proceeds to S506.

[0054] In S503, the RX determines whether authentication of the TX has been performed in the past. Here, the determination of whether authentication of the TX has been performed in the past can be made by referring to information related to authentication that is associated with the identification information of the TX and stored in the memory 211. The information related to authentication (an example of authentication-related information) can be, but is not limited to, the execution result (including at least one piece of information such as success / failure / not performed), information related to the execution result (number of successes, most recent authentication date and time), a combination of the execution time and the TX's certificate, etc.

[0055] The format of each piece of information may be stored as a numerical value, a character string, binary data, or the like, or may be stored using a bit flag, and is not limited to these.

[0056] For example, if a success is stored as the execution result, the RX can determine that authentication has been performed in the past. If the RX has already performed authentication of the TX (YES in S503), the RX proceeds to S504. On the other hand, if the RX has not already performed authentication of the TX (=failed or not yet performed) (NO in S503), the RX proceeds to S506.

[0057] In S504, RX determines whether or not authentication previously performed is still valid. Here, the determination of whether or not authentication previously performed is valid can be made by referring to information related to authentication stored in memory 211 in association with the identification information of the TX. For example, if the current time is within the validity period of the TX's certificate or if the execution time is within a predetermined period, the previously performed authentication can be determined to be valid. In addition, for example, if the RX's certificate (e.g., root certificate or intermediate certificate) has been updated since the time the authentication was performed, the previously performed authentication may be determined to be invalid (not valid). Alternatively, if the TX's certificate is included in the revocation list held by RX, the previously performed authentication may be determined to be invalid (not valid).

[0058] If the determination result in S504 is "YES", the process proceeds to step S502, otherwise the process proceeds to S506.

[0059] In S505, RX determines that authentication is not required, sets the requested power value to a value greater than a predetermined value, and terminates this process. The predetermined value is a sufficiently small value that is unlikely to cause damage to contaminants or heat generation even if power transmission and reception processing continues. It may be, for example, 5 watts or less, but is not limited to this. The value greater than the predetermined value may be the smaller of its own receivable power value and the negotiable power value acquired from TX. Meanwhile, in S506, RX determines that authentication is required, sets the requested power value to a predetermined value, and terminates this process.

[0060] According to the operation described above, if authentication of the TX has been performed and is valid before starting power reception, the RX in this embodiment considers the TX to be a trusted device whose authenticity has been verified, skips authentication, and sets the requested power value to a value greater than a predetermined value. This makes it possible to immediately start power reception at a high power value even when authentication processing is not performed, thereby realizing a safe and highly efficient wireless power transmission system.

[0061] Next, an example of the flow of the authentication and identification information storage process executed by the RX in S408 will be described with reference to Fig. 6. In this process, the control unit 201 functions as a storage processing unit that stores the identification information.

[0062] In S601, RX determines whether or not authentication is required. Here, the determination of whether or not authentication is required is made based on whether or not it was determined in S404 that authentication is required. If authentication is required (YES in S601), the process proceeds to S602. On the other hand, if authentication is not required (NO in S601), the authentication and identification information storage process is terminated. In this case, after the process shown in FIG. 6 (authentication and identification information storage process) is terminated, an affirmative determination is made in S409 in FIG. 4, and the process proceeds to S410.

[0063] In S602, the RX performs authentication. Note that the term "authentication" used in this specification corresponds to Authentication defined in the Qi standard, but may also correspond to authentication processing of other methods.

[0064] The details of the authentication process performed between the RX and TX are shown in Figure 10. In the Qi standard, authentication operates so that the RX authenticates the TX.

[0065] First, RX sends a GET_DIGESTS request to TX (F1001). The GET_DIGESTS request is used to obtain the certificate chain digest. When TX receives the GET_DIGESTS request, it sends a DIGESTS response to RX (F1002). The DIGESTS response is used to transmit the certificate chain digest and to report the slots that contain valid certificate chain digests.

[0066] Next, the RX sends a GET_CERTIFICATE request to the TX (F1003). The GET_CERTIFICATE request is used to read a segment of the target certificate chain.

[0067] When TX receives GET_CERTIFICATE, it sends a CERTIFICATE response to RX (F1004). The CERTIFICATE response is used to send the requested segment of the certificate chain.

[0068] Then, the RX sends a CHALLENGE request to the TX to start authentication (F1005).

[0069] When the TX receives the CHALLENGE request from the RX, it transmits a CHALLENGE_AUTH response to the RX (F1006).

[0070] If the validity of the response received from TX is confirmed, RX determines that the authentication is successful, otherwise it determines that the authentication is unsuccessful and ends the process.

[0071] When the authentication is completed, in S603, RX determines whether the authentication was successful. If the authentication is successful (YES in S603), RX proceeds to S604. On the other hand, if the authentication is not successful (NO in S603), RX ends the authentication and identification information storage process. In this case, after the process shown in FIG. 6 is completed, S409 and S410 in FIG. 4 may be skipped and a negative determination may be made in S411. That is, RX may stop receiving power.

[0072] In S604, RX determines whether or not to change the requested power value. Here, the determination of whether or not to change the requested power value can be made based on whether or not the requested power value determined in S404 is a predetermined value, that is, whether or not it was determined that authentication was necessary in a state where the authenticity of TX had not been proven, and the requested power value was limited to a predetermined value. If RX changes the requested power value (YES in S604), the process proceeds to S605. On the other hand, if RX does not change the requested power value (NO in S604), the process proceeds to S606.

[0073] In S605, RX determines that TX is a legitimate (trusted) device based on the success of authentication and that charging at a higher power value is possible, and changes the requested power value to a value greater than the predetermined value. In this case, after the processing shown in Fig. 6 is completed, a positive determination is made in S409 in Fig. 4, and the process proceeds to S410.

[0074] In S606, RX determines whether the identification information of TX is device-specific information. Note that this determination may be omitted in a mode in which the determination result in S501 above is used.

[0075] If the identification information of TX is device-specific information (YES in S606), RX proceeds to S607. On the other hand, if the identification information of TX is not device-specific information, that is, is temporary information (NO in S606), RX ends the authentication and identification information storage process.

[0076] In S607, RX stores the identification information of TX in the memory 211 and ends the authentication and identification information storage process. Note that in addition to the identification information of TX, information related to authentication linked to the identification information may also be stored. Note that in this case, the identification information of TX is stored in a non-volatile storage unit. That is, if the memory 211 includes a volatile memory and a non-volatile memory, the identification information of TX is stored in the non-volatile memory.

[0077] According to the operation described above, the RX in this embodiment controls whether to store the identification information of the TX depending on the type of the identification information (whether the identification information is device-specific or not). This makes it possible to determine whether authentication using the identification information is necessary, i.e., whether authentication can be omitted, when retrying charging with the TX. Furthermore, it is possible to avoid matching with unnecessary identification information that does not match the device-specific identification information, thereby realizing a safe and highly efficient wireless power transmission system.

[0078] [System-wide processing] Next, an example of the processing executed in this embodiment will be described. Some examples of the operation sequence when the above processing is executed will be shown.

[0079] In the initial state, RX is not placed on TX. TX has sufficient power transmission capability to transmit power at GP as requested by RX. In this embodiment, the predetermined value is 5 watts, and the value greater than the predetermined value is 15 watts.

[0080] [[First processing example]] In this processing example, the identification information of the TX is device-specific information, and the RX does not already have the identification information of the TX stored. First, when the RX detects that it has been placed on the TX, it exchanges identification information and capability information, then starts communication in the negotiation phase and acquires the TX's identification information. The RX checks whether the acquired identification information is stored or not, and since matching identification information is not stored, it determines that authentication is required and sets the requested power value to a predetermined value (5 watts). After that, the RX determines GP with the TX and starts receiving power, and performs authentication. At this time, authentication is successful, so the RX stores the identification information of the TX, changes the requested power value to a value greater than the predetermined value (15 watts), and again determines GP with the TX.

[0081] 7 shows the operation sequence in the first processing example. When the RX is placed on the TX in F701, the TX and RX perform communication in the Ping phase of the Qi standard, and the RX detects that it has been placed on the TX (F702, S401).

[0082] Next, in F703, RX transmits identification information and capability information to TX through communication in the configuration phase of the Qi standard (S402).

[0083] Next, the TX and RX start communication in the negotiation phase of the Qi standard, and in F704, the RX transmits an FOD Status data packet of the Qi standard to the TX.

[0084] When the TX receives the FOD Status data packet, it determines that no foreign object is present in this embodiment and transmits an ACK in F705.

[0085] Next, in F706, RX uses a Qi standard General Request (GRQ) data packet to send a capability information (CAP) notification request to TX.

[0086] When the TX receives the capability information notification request, it transmits a Qi-standard CAP data packet to the RX in step F707. The CAP data packet may include a negotiable power value, i.e., Negotiable Load Power. When the RX receives the CAP data packet, the WPC communication unit 203 and the control unit 201 function as an acquisition unit for acquiring the negotiable power value.

[0087] Next, in F708, RX transmits a notification request of the identification information to TX. Note that the notification request of the identification information can be transmitted using a data packet defined in the Qi standard.

[0088] When the TX receives the request for notification of the identification information, it transmits the identification information to the RX in F709. Note that the response (identification information) to the request for notification of the identification information can be transmitted using a data packet defined in the Qi standard. The identification information can include the ID of the TX, information on whether the ID is a device-specific ID, and the like. Hereinafter, in this processing example, the description will be given assuming that the identification information of the TX is a device-specific ID.

[0089] When RX acquires the identification information of TX, it starts the authentication execution decision process (S404), and because the identification information is unique to the device (YES in S501), it checks the identification information in F710. As a result of the check, RX determines that no matching identification information is stored (NO in S502), so it determines in F711 that authentication must be executed and determines the required power value to be 5 watts (S506).

[0090] Next, in F712, RX stores the GP's requested power value in a Qi-standard Specific Request (SRQ) data packet and transmits it to TX.

[0091] When the TX receives the SRQ data packet that is a request from the GP, the requested power value is equal to or less than its own negotiable power value, so it accepts the requested power value and stores it as the GP's value in F713.

[0092] Next, in F714, TX sends ACK to RX as a response of acceptance.

[0093] When RX receives the ACK, it assumes that the requested power value transmitted in F712 has been accepted, and stores the requested power value as the value of GP in F715 (S405).

[0094] Next, in F716, RX sends a notification of the end of the negotiation phase to TX using a Qi standard SRQ data packet.

[0095] When TX receives the notification of the end of the negotiation phase, it sends an ACK, which is an acceptance response, to RX in F717.

[0096] Thereafter, RX and TX calculate the reference value of power loss for the purpose of foreign object detection based on the determined GP value (F718, S406), and start power transmission and reception processing (F719, S407).

[0097] When RX starts receiving power, it executes authentication and identification information storage processing (S408), and because authentication needs to be executed (YES in S601), it starts authentication processing in F720 (S602).

[0098] In the following processing example, the explanation will be given assuming that authentication was successful. Since authentication was successful (YES in S603) and the current requested power value is 5 watts, RX changes the negotiable power value of TX to a larger power value of 15 watts (YES in S604, S605).

[0099] Next, since the identification information of TX is information unique to the device (YES in S606), RX stores the identification information in F721 (S607).

[0100] Next, TX and RX start communication in the negotiation phase of the Qi standard and re-determine the GP.

[0101] Hereafter, F722 to F733 are similar to F704 to F707 and F712 to F719, respectively, and therefore their explanation will be omitted.

[0102] As described above, in the first processing example, since authentication of TX is successful and the identification information is unique to the device, RX stores the identification information, assuming that TX is a legitimate (trusted) device. This makes it possible to determine whether authentication using the identification information is necessary, that is, whether authentication can be omitted, when retrying charging with TX, thereby realizing a safe and highly efficient wireless power transmission system.

[0103] [[Second processing example]] In this processing example, the identification information of the TX is device-specific information, and the RX has already stored the identification information of the TX. In other words, this is a processing example in which the RX is placed on the same TX again after the first processing example is performed.

[0104] First, when RX detects that it has been placed on TX, it transmits its identification information and capability information to TX, then starts communication in the negotiation phase and acquires TX's identification information. RX checks whether the acquired identification information is already stored, and since matching identification information is stored and previous successful authentication is still valid, it determines that authentication is not necessary and sets the requested power value to a value greater than the predetermined value, setting the TX's negotiable power value at 15 watts. After that, RX determines GP with TX and starts power reception, and continues power reception without performing authentication or re-determining GP.

[0105] Fig. 8 shows the operation sequence in the second processing example. Since F801 to F809 are the same as F701 to F709 in Fig. 7, their explanation will be omitted and only the differences will be explained.

[0106] When RX acquires the identification information of TX, it starts the authentication execution decision process (S404), and because the identification information is unique to the device (YES in S501), it checks the identification information in F810. As a result of the check, RX finds that the identification information is stored (YES in S502), and authentication has been executed and is valid (YES in S503, YES in S504), so it determines in F811 that authentication is not necessary and that the required power value is 15 watts (S505).

[0107] Since F812 to F819 are the same as F712 to F719 in FIG. 7, respectively, the description thereof will be omitted.

[0108] As described above, in the second processing example, RX stores the identification information of TX, and authentication has been executed and is in a valid state, so RX sets the requested power value to a value greater than the predetermined value and continues processing. This makes it possible to immediately start receiving power at a power value greater than the predetermined value even if authentication processing is not executed, thereby realizing a safe and highly efficient wireless power transmission system.

[0109] [[Third processing example]] In this processing example, the identification information of the TX is assumed to be temporary information. First, when the RX detects that it has been placed on the TX, it transmits its identification information and capability information to the TX, then starts communication in the negotiation phase and acquires the TX's identification information. Because the acquired identification information is not device-specific, the RX does not check whether the identification information is stored, but determines that authentication is required and sets the requested power value to a predetermined value (5 watts). After that, the RX determines GP with the TX and starts receiving power, and performs authentication. At this time, although the authentication is successful, because the identification information of the TX is not device-specific, it is not stored, and the requested power value is changed to a value larger than the predetermined value (15 watts), and GP is again determined with the TX.

[0110] 9 shows the operation sequence in the third processing example. F901 to F908, F911 to F919, and F920 to F931 are the same as F701 to F708, F712 to F720, and F722 to F733 in FIG. 7, respectively, so their explanation will be omitted and only the differences will be explained. When the TX receives a request for notification of identification information, it transmits the identification information to the RX in F909. In this processing example, the explanation will be given assuming that the TX's identification information is a temporary ID. When the RX acquires the TX's identification information, it starts authentication execution decision processing (S404). Since the identification information is not unique to the device (NO in S501), it does not check the identification information, but determines that authentication execution is necessary in F910 and determines the required power value to be 5 watts (S506). Thereafter, the RX starts authentication processing in F919 (S602). In the following processing example, the explanation will be given assuming that authentication is successful. Since the authentication is successful (YES in S603) and the current requested power value is 5 watts, RX changes the negotiable power value of TX to 15 watts as a larger power value (YES in S604, S605). However, since the identification information of TX is not device-specific information (NO in S606), the identification information is not stored.

[0111] As described above, in the third processing example, even if authentication is successful, RX does not store the identification information of TX because the identification information is not device-specific information. This makes it possible to avoid matching with identification information that does not match device-specific identification information, i.e., to avoid matching with unnecessary identification information, thereby realizing a safe and highly efficient wireless power transmission system.

[0112] [[Other processing examples]] In the above embodiment, the RX stores information related to authentication together with the identification information of the TX, but it may also store only the identification information. In this case, it is possible to control the RX to store the identification information only if the identification information of the TX is unique to the device, and not to store the identification information if the identification information is not unique to the device. Also, it is possible to omit the determination of whether authentication has been performed (S503) and the determination of whether the performed authentication is valid (S504). This makes it possible to determine whether authentication is necessary based on whether power has been received from the TX in the past, while suppressing the amount of data to be stored and the processing load, thereby realizing a safe and highly efficient wireless power transmission system.

[0113] In the above embodiment, if authentication is not successful in the RX, the identification information is not stored, but it may be stored. In this case, the execution result of the information related to the authentication may be stored as not successful (=failed or not executed) together with the identification information. Furthermore, if the identification information has already been stored, it may be deleted, or the execution result of the information related to the authentication stored in association with the identification information may be changed to not successful, i.e., invalidated. This makes it possible to reliably execute authentication for the TX that was not successful in authentication, thereby realizing a safer and more efficient wireless power transmission system.

[0114] In the above embodiment, if the identification information of the TX is not unique to the device, the RX does not store the identification information. However, the RX may store the identification information. In this case, the RX may store the fact that the identification information is temporary information together with the identification information. Furthermore, the execution result of the authentication information may be stored as not successful (= failed or not executed), but this is not limiting. This makes it possible to reliably perform authentication even when the RX stores identification information that is not unique to the device, i.e., that makes it difficult to determine whether the device is legitimate (trustworthy), and thus makes it possible to realize a safer and more efficient wireless power transmission system.

[0115] In the above embodiment, the RX determines whether to store the identification information of the TX depending on the type of the identification information. However, the RX may request the user via the notification unit 209 to instruct whether to allow storage. At this time, the notification unit 209 may display information or a message that allows the user to identify whether the TX is a legitimate (trusted) device depending on whether the identification information is device-specific or whether authentication was successful or not. Alternatively, the user may be requested to instruct only when the identification information of the TX is not device-specific or when authentication failed. Furthermore, even if the user instructs not to allow storage, the identification information may be stored together with information indicating that the user did not allow it. This makes it possible to notify the user whether the TX is a legitimate (trusted) device depending on the type of identification information and the authentication result. Furthermore, it is possible to omit authentication for TXs that the user has allowed to be stored (registered) and to reliably perform authentication for TXs that the user has not allowed, thereby realizing a safe and highly efficient wireless power transmission system.

[0116] In the above embodiment, when the RX determines that authentication is not required, the authentication process executed during the power transfer phase is not performed. However, it may be performed. That is, the authentication process is performed after starting power reception from the TX, whose identification information has been stored, at a power value greater than a predetermined value. This allows the desired power to be received early, and in the unlikely event that the TX is masquerading as an unauthorized device, the received power can be limited or stopped. Also, part of the authentication process may be omitted. For example, steps F1003 to F1004 can be omitted by using authentication-related information (e.g., a certificate of the TX) stored in association with the TX's identification information. This significantly reduces the processing time related to authentication and makes it possible to reliably confirm whether the TX is a legitimate device, thereby realizing a safer and more efficient wireless power transmission system. Also, for example, if the TX's identification information has been stored but authentication has not been performed or the authentication is invalid, the authentication process may be simplified in a similar manner. However, this is not limited to this. In the above embodiment, when it is determined that authentication is to be performed in the RX, the requested power value is set to a predetermined value. However, this does not have to be a predetermined value. For example, if identification information has been stored but authentication has not been performed or authentication is not valid, the requested power value may be set to a value greater than a predetermined value to determine the GP, and the received power value may be controlled to fall within the predetermined value until the authentication process is completed. This makes it possible to confirm whether the TX is a legitimate device by performing authentication, and also reduces the processing time required to re-determine the GP, thereby realizing a safer and more efficient wireless power transmission system.

[0117] In the above embodiment, the RX stores information related to authentication in association with the identification information of the TX. However, the RX may store information related to power transmission and reception (an example of power transmission-related information), such as a GP or a power profile. In this case, for example, when the RX determines that authentication is not required, the RX may set the required power value to the stored GP value. This reduces the need to repeat the processing sequence for determining the GP, thereby achieving a safer and more efficient wireless power transmission system. FIG. 11 shows an example of such a modification. FIG. 11 differs from the processing flow shown in FIG. 8 in that F806 and F807 are omitted and F810A and F811A are added. In this case, the capability information may also be stored as part of the information related to power transmission and reception (an example of power-related information). In the example shown in FIG. 11, the omission of F806 and F807 reduces the processing load. Furthermore, even if F806 is omitted, the required power value can be set to a relatively high value, such as 15 W, in F812 by using the information related to power transmission and reception read out in F810A.

[0118] In the above embodiment, the WPC communication unit 203, i.e., wireless power transmission communication based on the Qi standard, is used as a method for notifying the RX of the identification information of the TX, but other general wireless communication may also be used. For example, Wi-Fi (registered trademark), Bluetooth (registered trademark), NFC, etc. may be used instead.

[0119] In the above embodiment, the RX determines whether or not authentication is required based on the identification information of the TX, but the determination may also be made based on the state of wireless communication established with the TX. For example, a state in which Bluetooth pairing with the TX is complete can be considered to be a state in which the identification information of the TX is stored, and a state in which a Bluetooth link with the TX is established can be considered to be a state in which authentication has been performed and is valid.

[0120] In the above embodiment, an example in which the RX authenticates the TX has been described, but the TX may operate to authenticate the RX, or both may perform authentication. In this case, the TX may determine whether or not authentication is required based on the type of identification information of the RX, the status of authentication execution, etc., and may determine the negotiable load power depending on whether or not authentication is required. For example, if it is determined that authentication is required, the negotiable load power may be set to a predetermined value, and if it is determined that authentication is not required, the negotiable load power may be set to a value greater than the predetermined value. Furthermore, other determinations and processes performed by the RX described in the above embodiment may also be applied to the TX in the same way.

[0121] Furthermore, in the above embodiment, a specific processing order is illustrated in the processing flow diagrams (flowcharts) shown in Figures 4 to 6, but this is not limiting. That is, the processing order of each step may be changed as long as the relationship between input and output of each step is not impaired. This also applies to the diagrams shown in Figures 7 to 9. For example, in the example shown in Figure 6, the processing of S604 and S605 may be changed to the processing of S606 and S607.

[0122] [Other embodiments] The present disclosure can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions.

[0123] Although each embodiment has been described in detail above, it is not limited to a specific embodiment, and various modifications and changes are possible within the scope of the claims. It is also possible to combine all or a plurality of components of the above-described embodiments. For example, in the above-described embodiment, two values ​​are exemplified as the required power value: a predetermined value (5 watts) and a value greater than the predetermined value (15 watts), but any of three or more values ​​may be selectively used, such as 20 watts or more.

[0124] In addition, the following supplementary notes are disclosed regarding the above-described embodiment.

[0125] [Appendix 1] power receiving means for wirelessly receiving power from a power transmitting device; an acquisition means for acquiring identification information of the power transmitting device; authentication means for authenticating the power transmitting device; a storage processing means for storing the identification information in a storage unit based on an attribute of the identification information after authentication by the authentication means.

[0126] [Appendix 2] The attribute of the identification information includes a fixed type in which the identification information is fixed; 2. The power receiving device according to claim 1, wherein the storage processing means stores the identification information in the storage unit when an attribute of the identification information is fixed.

[0127] [Appendix 3] The power receiving device described in Appendix 1 or 2, characterized in that the storage processing means stores the identification information in the memory unit when the attribute of the identification information is fixed and authentication by the authentication means is successful.

[0128] [Appendix 4] the attribute of the identification information includes a variable type in which the identification information varies; The power receiving device according to any one of appendices 1 to 3, characterized in that the storage processing means does not store the identification information in the storage unit if the attribute of the identification information is variable.

[0129] [Appendix 5] The power receiving device according to any one of appendices 1 to 4, characterized in that the identification information includes attribute information indicating the attribute, or is acquired by the acquisition means together with the attribute information.

[0130] [Appendix 6] a determination means for determining whether the identification information is stored in the storage unit; The power receiving device according to any one of appendices 1 to 5, further comprising an authentication control means for performing authentication by the authentication means when the determination means determines that the identification information is not stored, and not performing or simplifying authentication by the authentication means when the determination means determines that the identification information is stored.

[0131] [Appendix 7] 7. The power receiving device according to claim 6, wherein the determining means makes the determination based on an attribute of the identification information.

[0132] [Appendix 8] The attribute of the identification information includes a fixed type in which the identification information is fixed; 8. The power receiving device according to claim 6, wherein the determining means performs the determination when an attribute of the identification information is fixed.

[0133] [Appendix 9] the attribute of the identification information includes a variable type in which the identification information varies; 9. The power receiving device according to claim 6, wherein the determining means does not perform the determination when an attribute of the identification information is a variable type.

[0134] [Appendix 10] The power receiving device according to any one of Supplementary Notes 1 to 9, characterized in that when the storage processing means stores the identification information in the storage unit, it stores authentication-related information relating to authentication by the authentication means in the storage unit in association with the identification information.

[0135] [Appendix 11] The power receiving device described in Appendix 10, characterized in that the authentication-related information includes the result of authentication performed by the authentication means, or the time of execution and a certificate of the power transmitting device obtained during authentication by the authentication means.

[0136] [Appendix 12] 12. The power receiving device according to claim 11, wherein the execution result of the authentication includes at least one of success, failure, and not executed.

[0137] [Appendix 13] A power receiving device described in any one of Appendices 10 to 12, further comprising an authentication control means for omitting or simplifying authentication by the authentication means based on the authentication-related information stored in the memory unit.

[0138] [Appendix 14] The power receiving device further includes a power receiving control means that starts wirelessly receiving power from the power transmitting device at a first power value before authentication by the authentication means; The power receiving device described in any one of Appendices 1 to 13, characterized in that the power receiving control means, when authentication by the authentication means is successful, wirelessly receives power from the power transmitting device at a second power value higher than the first power value.

[0139] [Appendix 15] The power receiving device described in Appendix 14, characterized in that when the storage processing means stores the identification information in the memory unit, it links power transmission-related information regarding the power transmission function of the power transmitting device to the identification information and stores it in the memory unit.

[0140] [Appendix 16] The power receiving device according to claim 15, wherein the power receiving control means controls wireless power reception from the power transmitting device based on the power transmission related information stored in the memory unit.

[0141] [Appendix 17] The power receiving device described in Appendix 16, characterized in that when the determination means determines that the identification information is stored and the power transmission related information indicates that wireless power reception from the power transmitting device can be performed at the second power value, the power receiving control means starts wireless power reception from the power transmitting device at the second power value before authentication by the authentication means.

[0142] [Appendix 18] A method performed by a power receiving device that wirelessly receives power from a power transmitting device, comprising: acquiring identification information of the power transmitting device; an authentication step of authenticating the power transmitting device; a step of storing the identification information in a storage unit based on an attribute of the identification information after the authentication step; A method comprising:

[0143] [Appendix 19] A program for causing a computer to function as the control method for a power receiving device described in Supplementary Note 18. [Explanation of symbols]

[0144] 201: control unit, 202: NFC communication unit, 203: WPC communication unit, 204: power receiving coil, 205: power receiving unit, 206: detection unit, 207: charging unit, 208: battery, 209: notification unit, 210: operation unit, 211: memory, 212: timer

Claims

1. power receiving means for wirelessly receiving power from a power transmitting device; an acquisition means for acquiring identification information of the power transmitting device; authentication means for authenticating the power transmitting device; a storage processing means for storing the identification information in a storage unit based on an attribute of the identification information after authentication by the authentication means.

2. The attribute of the identification information includes a fixed type in which the identification information is fixed; The power receiving device according to claim 1 , wherein the storage processing means stores the identification information in the storage unit when an attribute of the identification information is fixed.

3. 3. The power receiving device according to claim 2, wherein the storage processing means stores the identification information in the storage unit when an attribute of the identification information is fixed and authentication by the authentication means is successful.

4. the attribute of the identification information includes a variable type in which the identification information varies; The power receiving device according to claim 1 , wherein the storage processing means does not store the identification information in the storage unit when an attribute of the identification information is variable.

5. The power receiving device according to claim 1 , wherein the identification information includes attribute information indicating the attribute, or is acquired by the acquiring means together with the attribute information.

6. a determination means for determining whether the identification information is stored in the storage unit; The power receiving device according to claim 1, further comprising an authentication control means for performing authentication by the authentication means when the determination means determines that the identification information is not stored, and not performing or simplifying authentication by the authentication means when the determination means determines that the identification information is stored.

7. The power receiving device according to claim 6, wherein the determining means makes the determination based on an attribute of the identification information.

8. The attribute of the identification information includes a fixed type in which the identification information is fixed; The power receiving device according to claim 6, wherein the determining means performs the determination when an attribute of the identification information is a fixed type.

9. the attribute of the identification information includes a variable type in which the identification information varies; The power receiving device according to claim 6 , wherein the determining means does not perform the determination when an attribute of the identification information is a variable type.

10. The power receiving device according to claim 1 , wherein when the storage processing means stores the identification information in the storage unit, the storage processing means stores authentication-related information related to authentication by the authentication means in association with the identification information in the storage unit.

11. The power receiving device according to claim 10 , wherein the authentication-related information includes a result of authentication performed by the authentication unit, or a time of execution and a certificate of the power transmitting device obtained during authentication performed by the authentication unit.

12. The power receiving device according to claim 11 , wherein the execution result of the authentication includes at least one of success, failure, and not executed.

13. 11. The power receiving device according to claim 10, further comprising authentication control means for omitting or simplifying authentication by said authentication means based on said authentication-related information stored in said storage unit.

14. the power receiving device further includes a power receiving control means that starts wirelessly receiving power from the power transmitting device at a first power value before authentication by the authentication means; The power receiving device according to claim 1, characterized in that, when authentication by the authentication means is successful, the power receiving control means wirelessly receives power from the power transmitting device at a second power value higher than the first power value.

15. The power receiving device according to claim 14, characterized in that when the storage processing means stores the identification information in the storage unit, it associates power transmission-related information regarding the power transmission function of the power transmitting device with the identification information and stores it in the storage unit.

16. The power receiving device according to claim 15, wherein the power reception control means controls wireless reception of power from the power transmitting device based on the power transmission related information stored in the storage unit.

17. The power receiving device described in claim 16, characterized in that when the determination means determines that the identification information is stored and the power transmission related information indicates that wireless power reception from the power transmitting device can be performed at the second power value, the power receiving control means starts wireless power reception from the power transmitting device at the second power value before authentication by the authentication means.

18. A method performed by a power receiving device that wirelessly receives power from a power transmitting device, comprising: acquiring identification information of the power transmitting device; an authentication step of authenticating the power transmitting device; a step of storing the identification information in a storage unit based on an attribute of the identification information after the authentication step; A method comprising:

19. A program for causing a computer to function as the method according to claim 18.

Images