Power reception device, method and program to be performed by power reception device

Abstract

To perform appropriate processing in consideration of an influence of a compatible product in power transmission processing when a power reception device is combined with the compatible product to be used.SOLUTION: A power reception device 101 is used in combination with a compatible product 201 and wirelessly receives power from a power transmission device 301. The power reception device detects that the power reception device is combined with the compatible product and determines a parameter to be used for state detection processing for detecting states of the power reception device and the power transmission device on the basis of whether or not the combination of the power reception device and the compatible product is detected.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present disclosure relates to technology for devices that can be used in combination with counterparts that have tags that utilize near field communication. [Background technology]

[0002] The Near Field Communication (NFC) standard is known as a standard for short-range wireless communication. In the NFC standard, polling refers to transmitting a carrier wave and modulating the carrier wave to send a message to detect a communication partner. Polling is transmitted by a device with NFC-compliant reader / writer functionality. An NFC tag is a device that receives polling transmitted by a reader / writer and responds to the polling by modulating the carrier wave transmitted by the reader / writer. Information exchanged under the NFC standard complies with a data format called NDEF (NFC Data Exchange Format). Multiple pieces of NDEF information can be set on a single tag, and a reading device can read multiple pieces of NDEF information set on an NFC tag from the NFC tag in a single NFC communication. How the read NDEF information is processed is up to the device.

[0003] In recent years, technologies using NFC to authenticate items have become widespread. In particular, NFC authentication technologies have been developed to verify whether accessories or parts attached to or used in combination with devices are compatible with those devices.

[0004] Patent Document 1 discloses technology relating to the structure of a mobile phone equipped with an RFID (Radio Frequency Identification) tag. Specifically, an antenna of a reader / writer based on the RFID standard is provided on a battery pack cover of the mobile phone body. Then, a circuit board of the reader / writer arranged inside the mobile phone body reads an ID from the RFID tag attached to the battery pack to determine the authenticity of the battery pack (whether it is a genuine product or not).

[0005] Patent Document 2 also describes that in a wireless power transmission system, the power transmitter and the power receiver calibrate each other so that the characteristics of the power transmitter and the power receiver are reflected in foreign object detection. It also describes that parameters such as a scale factor and an offset are used in the calibration. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-134796 [Patent Document 2] Special Publication No. 2017-511109 Summary of the Invention [Problem to be solved by the invention]

[0007] When a power receiving device that receives power wirelessly from a power transmitting device is combined (e.g., attached) with a compatible item such as an accessory, if the influence of the compatible item is not taken into consideration, efficient power transmission between the power transmitting device and the power receiving device may not be possible.

[0008] The present disclosure provides a technique that, when a power receiving device and a compatible product are used in combination, can perform appropriate processing that takes into account the influence of the compatible product during power transmission processing. [Means for solving the problem]

[0009] A power receiving device according to one embodiment of the present disclosure includes a detection means for detecting that the power receiving device has been combined with a compatible product, and a determination means for determining parameters to be used in a status detection process for detecting the status of the power receiving device and the power transmitting device based on whether or not it has been detected that the power receiving device has been combined with the compatible product. [Effects of the Invention]

[0010] According to the present disclosure, when a power receiving device and a compatible product are used in combination, appropriate processing can be performed taking into account the influence of the compatible product during power transmission processing. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a system according to a first embodiment. [Figure 2] FIG. 10 is a diagram illustrating an example of the configuration of a system in which a compatible product is attached to a power receiving device. [Figure 3] FIG. 1 is a diagram illustrating an example of a system configuration in which a power receiving device is placed on a power transmitting device. [Figure 4] FIG. 10 is a diagram illustrating a configuration example of a corresponding product. [Figure 5] FIG. 2 illustrates an example of the configuration of a power receiving device. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a power transmitting device. [Figure 7] 10 is a flowchart illustrating an outline of processing performed by the power receiving device. [Figure 8] 10 is a flowchart illustrating a wireless power transmission pre-setting process. [Figure 9] 9 is a flowchart continuing from FIG. 8. [Figure 10] 9 is a flowchart showing details of the NFC tag detection process in FIG. 8. [Figure 11] 1A and 1B are diagrams showing NDEF information recorded on an NFC tag. [Figure 12] 10 is a flowchart illustrating details of a process of wireless power transmission by a power receiving device. [Figure 13]13 is a flowchart showing an example of a wireless power transmission presetting process of the power receiving device in FIG. 12. [Figure 14] FIG. 3 is a sequence diagram showing the processing of the entire system of the first embodiment. [Figure 15] 15 is a flowchart showing a continuation of FIG. 14. [Figure 16] 10 is a flowchart showing a wireless power transmission presetting process of a power receiving device in the second embodiment. [Figure 17] 11 is a flowchart showing a wireless power transmission presetting process of a power receiving device in a third embodiment. [Figure 18] 13 is a flowchart showing a wireless power transmission presetting process of a power receiving device in the fourth embodiment. [Figure 19] 19 is a flowchart continuing from FIG. 18. [Figure 20] 13 is a flowchart showing a wireless power transmission presetting process of a power receiving device in a modified example of the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Not all of the features in the embodiments of the present disclosure are essential, and multiple features may be combined as desired. Furthermore, the configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the illustrated configurations. In the drawings, the same reference symbols are used to designate the same or similar configurations, and redundant explanations will be omitted.

[0013] First Embodiment In the first embodiment, a power receiving device is taken as an example of a device. The power receiving device is a device that can perform wireless power transmission using an electromagnetic induction method for contactless charging based on the WPC standard defined by the Wireless Power Consortium (WPC).

[0014] In the WPC standard, the amount of power guaranteed when a power receiving device receives power from a power transmitting device is specified by a value called Guaranteed Load Power (hereinafter referred to as "GP"). GP indicates the value of power guaranteed to be output to a load, such as a charging circuit, of the power receiving device, even if, for example, the relative positional relationship between the power receiving device and the power transmitting device changes and the power transmission efficiency between the power receiving coil and the power transmitting coil decreases. For example, if the GP is 15 watts, the power transmitting device controls and transmits power so that it can output 15 watts to the load in the power receiving device, even if the relative positional relationship between the power receiving coil and the power transmitting coil changes and the power transmission efficiency decreases.

[0015] [System Configuration] 1 is a diagram showing an example of the configuration of a system according to this embodiment. This system includes a power receiving device 101 as a device, a compatible product 201 for the power receiving device 101, and a power transmitting device 301. In the following description, the power receiving device may be referred to as RX and the power transmitting device may be referred to as TX.

[0016] RX101 is an electronic device that receives power from TX301 and charges its built-in battery while placed on TX301. TX301 is an electronic device that transmits power wirelessly to the placed RX101. RX101 and TX301 may have a function for executing applications other than the wireless charging function. For example, RX101 is a smartphone, and TX301 is an accessory device for charging the smartphone's battery. However, without being limited to this example, RX101 and TX301 may be a tablet device, a storage device such as a hard disk drive or a memory device, or an information processing device such as a personal computer (PC). RX101 and TX301 may also be an imaging device such as a still camera or a video camera, an automobile, a robot, a medical device, a printer, etc.

[0017] The RX101 is also equipped with an NFC (Near Field Communication) function, which can be used to operate in, for example, card emulation mode, enabling electronic money payments, etc. The RX101 is also equipped with an NFC function that can perform NFC communication and read an NFC tag 202 by operating in reader / writer mode. The RX101 has a built-in NFC antenna 102 for NFC communication, and the NFC antenna 102 is arranged along and near the surface of the RX101 housing. When the NFC tag 202 provided in the compatible product 201 approaches the surface of the RX101 where the NFC antenna 102 is built in, the RX101 operates in reader / writer mode and can communicate with the NFC tag 202. The RX101 also has a built-in sensor 103 that detects that the compatible product 201 has been combined with the RX101.

[0018] Typically, combining a compatible item with the RX means that the compatible item is attached (mounted) to the RX101. However, this is not limited to this, and it can also mean anything that generates one or more functions or effects, even if the RX101 and the compatible item are not in physical contact with each other, for example, when the RX and the compatible item are used simultaneously. "Effects" can also include human sensory effects, such as visual and auditory effects.

[0019] As a typical example, RX101 is a smartphone, and the compatible product 201 is a cover or case for the smartphone. However, the compatible product 201 is not limited to a cover or case, and may be, for example, an external battery, a gimbal, or an attachment device.

[0020] In the following embodiments, a typical example of combining a compatible product with an RX will be exemplified by attaching the compatible product to the RX.

[0021] FIG. 4 is a diagram showing an example of the configuration of a compliant product 201. Referring to FIGS. 1 and 4, an NFC tag 202 is mounted on the compliant product 201. The NFC tag 202 is an example of a device that operates without a battery and realizes short-range wireless communication. More specific examples include an NFC / RFID tag capable of NFC communication and an NFC communication device that operates in card emulation mode. If the compliant product 201 is an NFC communication device that operates in card emulation mode, it may be equipped with a control unit that controls communication and the entire compliant product 201.

[0022] The compatible product 201 has a detectable part 203. When the compatible product 201 is attached to or combined with the RX101, the RX101 detects the detectable part 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the RX101. The sensor 103 and / or the detectable part 203 are an example of a detection means for detecting that the RX101 and the compatible product 201 have been combined.

[0023] When the RX101 is placed on the TX301, the TX301 transmits power wirelessly to the RX101 in accordance with the WPC standard. When the RX101 is placed on the TX301, the TX301 incorporates a power transmitting coil 310 that can transmit power wirelessly to the RX101 in accordance with the WPC standard, and the power transmitting coil 310 is disposed along and near the surface of the housing of the TX301.

[0024] In the following, a convex portion formed on the surface of the corresponding product will be taken as an example of the detected portion 203 of the corresponding product 201. And, a mechanical switch disposed on the surface of the housing of the RX101 that is pressed by the convex portion will be taken as an example of the sensor 103 of the RX101. However, the present invention is not limited to this, and the sensor 103 may be, for example, an optical sensor, an acoustic sensor, a thermal sensor, etc.

[0025] 2 is a diagram showing an example of the system configuration when a compatible product 201 is attached to the RX101. The compatible product 201 is shaped to cover the housing of the RX101 and is attached to the RX101. At this time, the NFC tag 202 of the compatible product 201 is positioned so as to overlap the area of ​​the NFC antenna 102 of the RX101. This allows the RX101 to operate in reader / writer mode and communicate with the NFC tag 202.

[0026] Furthermore, when the compatible product 201 is attached to the RX101, the detectable portion 203 of the compatible product 201 is disposed near the sensor 103 of the RX101. As a result, the RX101 detects the detectable portion 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the RX101.

[0027] 3 is a diagram showing an example of the system configuration in which the compatible product 201 is attached to the RX101 and the RX101 is placed on the TX301. FIG. 3(A) is a plan view, and FIG. 3(B) is a schematic cross-sectional view. As shown in FIGS. 3(A) and 3(B), the power transmitting coil 310 of the TX301 is arranged so as to overlap the power receiving coil 104 of the RX101 in a plan view. This allows the TX301 to wirelessly transmit power to the RX101 in accordance with the WPC standard.

[0028] [Configuration of power receiving device, compatible product, and power transmitting device] 5 is a diagram showing an example of the configuration of the RX 101. The RX 101 has an NFC antenna 102, a sensor 103, a first communication unit 504, a control unit 505, and a memory 506. The RX 101 also has a power receiving coil 104, a power receiving unit 507, a second communication unit 508, a detection unit 509, a charging unit 510, a battery 511, an operation unit 512, and a notification unit 513.

[0029] The NFC antenna 102 and the first communication unit 504 are hardware modules that realize the NFC function. Specifically, they realize a card emulation mode that acts as a contactless IC card, a reader / writer mode for reading the NFC tag 202, and a P2P mode for directly exchanging messages between NFC devices. For example, the card emulation mode enables electronic money payments.

[0030] The first communication unit 504 and the control unit 505 are mainly an example of an acquisition unit that detects an NFC tag and acquires (reads) tag information from the detected NFC tag.

[0031] The sensor 103 is, for example, a mechanical switch arranged on the surface of the housing of the RX101, and detects that the compatible product 201 has been combined with the RX101 by detecting the detected portion 203, which is a convex portion formed on the surface of the compatible product.

[0032] The control unit 505 controls the entire RX101. The control unit 505 performs control by executing a control program stored in the memory 506, for example. The control unit 505 also stores information to be stored during execution of various processes in the memory 506. The control unit 505 includes one or more processors, such as a CPU (Central Processing Unit) or an MPU (Micro-processing Unit). The control unit 505 may include a memory separate from the memory 506 that stores the control program, and may store information to be stored during execution of various processes in the separate memory.

[0033] The control unit 505 may be configured with hardware dedicated to a specific process, such as an application specific integrated circuit (ASIC), or may include an array circuit, such as a field programmable gate array (FPGA), compiled to execute a predetermined process.

[0034] Although the control unit 505 is shown as a single component, the present invention is not limited to this. For example, the WPC control unit that controls processing related to receiving power from the TX301 may be configured separately from the control unit 505. Alternatively, the NFC control unit that controls processing related to NFC communication may be configured separately from the control unit 505. Furthermore, the WPC control unit and the NFC control unit may each be configured separately from the control unit 505. When the control unit 505 is configured as multiple separate units, the respective control units are connected to each other via a communication interface, enabling data communication. In this case, the communication interface may be any interface that realizes data communication, such as I2C or GPIO.

[0035] The memory 506 stores various information such as identification information and device configuration information, control programs, etc. The memory 506 may store information obtained by a functional unit other than the control unit 505.

[0036] The second communication unit 508 performs wireless communication based on the WPC standard with the communication unit 605 (FIG. 6) of the TX 301. The second communication unit 508 controls the power receiving unit 507 to communicate with the TX 301. Specifically, the second communication unit 508 demodulates the electromagnetic waves input from the power receiving coil 104 to acquire information transmitted from the TX 301, and performs load modulation on the electromagnetic waves to superimpose information to be transmitted to the TX 301 onto the electromagnetic waves. In other words, the communication performed by the second communication unit 508 is superimposed on the electromagnetic waves transmitted from the power transmitting coil 310 of the TX 301.

[0037] The detection unit 509 detects that the RX101 is placed on the TX301 based on the WPC standard. For example, the detection unit 509 detects at least one of the voltage value and current value of the power receiving coil 104 when the power receiving unit 507 receives a Digital Ping of the WPC standard via the power receiving coil 104. For example, the detection unit 509 can determine that the RX101 is placed on the TX301 when the voltage value is below a predetermined voltage threshold or when the current value exceeds a predetermined current threshold.

[0038] Thus, in the present disclosure, placing a power receiving device on a power transmitting device means that the power receiving device is in a state where it can receive power from the power transmitting device (for example, it is placed in a position where it can receive power). Here, even if the power receiving device is placed on the power transmitting device, it may not necessarily be in a state where it can receive power. For example, this may be the case when a cover, case, or other member that blocks or attenuates electromagnetic waves is attached to the power receiving device, or when an unintended member that blocks or attenuates electromagnetic waves exists between the power transmitting device and the power receiving device. "The power receiving device is placed on the power transmitting device," which will be explained later in the flowcharts, is merely one example of the power receiving device being in a state where it can receive power from the power transmitting device. Furthermore, the state in which the power receiving device is capable of receiving power is not limited to the state in which the power receiving device is placed on the power transmitting device. For example, the state in which the power receiving device is capable of receiving power may be a state in which the power receiving device and the power transmitting device are in contact or proximity with each other through mechanical engagement, or a state in which the power receiving device is in contact with the power transmitting device by magnetic force (for example, via a compatible product). In the present disclosure, the following description will be given using a state in which the power receiving device is placed on the power transmitting device as a typical example of a state in which the RX 111 is able to receive power.

[0039] The charging unit 510 charges the battery 511 with power supplied from the power receiving unit 507. The charging unit 510 also starts or stops charging the battery 511 based on the control of the control unit 505, and further adjusts the power used to charge the battery 511 based on the charging state of the battery 511. When the power used by the charging unit 510 changes, the power supplied from the power receiving unit 507, i.e., the received power in the RX101, also changes accordingly. The charging unit 510 shown here is a load in the RX101.

[0040] The battery 511 supplies the entire RX 101 with power required for control of each part of the RX 101 by the control unit 505, power reception, and communication. The battery 511 also stores the power received via the power receiving coil 104.

[0041] The notification unit 513 notifies the user by any method such as visually, audibly, or tactilely, of, for example, the charging state of the RX101 or information indicating the state of power transmission of the wireless power transmission system including the RX101 and the TX301 as shown in Fig. 3. The notification unit 513 includes, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, and / or other notification devices.

[0042] The operation unit 512 has a function of receiving operations from the user on the RX101. The operation unit 512 includes, for example, a button, a keyboard, a voice input device, a motion detection device, and / or other input devices. An example of the voice input device is a microphone. An example of the motion detection device is an acceleration sensor or a gyro sensor. Note that a device in which the notification unit 513 and the operation unit 512 are integrated, such as a touch panel, may be used.

[0043] FIG. 6 is a diagram showing an example of the configuration of the TX 301 of this embodiment. The TX 301 includes a control unit 601 , a power supply unit 602 , a power transmission unit 603 , a detection unit 604 , a power transmission coil 310 , a communication unit 605 , a notification unit 606 , an operation unit 607 , and a memory 608 .

[0044] The control unit 601 controls the entire TX 301 by executing a control program stored in the memory 608, for example. That is, the control unit 601 controls each functional unit shown in FIG. 6. The control unit 601 also stores information to be stored while various processes are being executed in the memory 608. The control unit 601 also performs control related to power transmission and control related to the NFC function. Furthermore, the control unit 601 may also perform control for executing applications other than wireless power transmission. A specific example of the hardware of the control unit 601 is the same as the example of the hardware of the control unit 505 in FIG. 5, and therefore a description thereof will be omitted.

[0045] The control unit 601 may be configured with one processor, or a main control unit that controls the entire device and a sub-control unit that controls the power transmission process and NFC communication may each be implemented by separate processors.

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

[0047] The power transmitting unit 603 converts the DC or AC power output from the power supply unit 602 into AC frequency power in the frequency band used for wireless power transmission, and inputs the AC frequency power to the power transmitting coil 310 to generate electromagnetic waves for receiving power by the RX 101. The frequency of the AC power generated by the power transmitting unit 603 is, for example, about several hundred kHz (for example, 110 kHz to 205 kHz).

[0048] Based on instructions from the control unit 601, the power transmitting unit 603 inputs AC frequency power to the power transmitting coil 310 so that the power transmitting coil 310 outputs electromagnetic waves for transmitting power to the RX101. The power transmitting unit 603 controls the intensity of the electromagnetic waves to be output by adjusting the voltage (power transmitting voltage) and / or current (power transmitting current) input to the power transmitting coil 310. 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. Based on instructions from the control unit 601, the power transmitting unit 603 also controls the output of AC frequency power so that power transmission from the power transmitting coil 310 starts or stops.

[0049] The power transmitting unit 603 notifies the control unit 601 of the current transmitted power, thereby enabling the control unit 601 to know the transmitted power at any timing. Note that the measurement of the transmitted power and the notification to the control unit 601 may be configured to be performed by a unit other than the power transmitting unit 603.

[0050] The detection unit 604 detects whether an object is placed on the TX301 based on the WPC standard. Specifically, the detection unit 604 detects whether an object is placed on the interface surface of the TX301. For example, the detection unit 604 detects at least one of the voltage value and the current value of the power transmitting coil 310 when the power transmitting unit 603 transmits an Analog Ping of the WPC standard via the power transmitting coil 310. The detection unit 604 may detect a change in impedance. Then, the detection unit 604 may determine that an object is placed on the TX301 when the voltage is below a predetermined voltage value or the current value exceeds a predetermined current value.

[0051] Whether this object is the RX101 or another foreign object is determined based on the presence or absence of a predetermined response to the Digital Ping subsequently transmitted by the communication unit 605. That is, if the TX301 receives a predetermined response, the object is determined to be the RX101, and if not, the object is determined to be an object other than the power receiving device.

[0052] The communication unit 605 performs control communication with the RX101 based on the WPC standard as described above. The communication unit 605 modulates the electromagnetic waves output from the power transmitting coil 310 and transmits information to the RX101 to perform communication. The communication unit 605 also demodulates the electromagnetic waves output from the power transmitting coil 310 and modulated by the RX101 to acquire information transmitted by the RX101. That is, the communication performed by the communication unit 605 is superimposed on the electromagnetic waves transmitted from the power transmitting coil 310.

[0053] The communication unit 605 also performs NFC communication and detects the NFC tag of the device to which power is transmitted. Note that the communication unit 605 may be realized by a single piece of hardware, with a module for performing control communication based on the WPC standard and a module for performing NFC communication, or each may be realized by separate hardware.

[0054] The notification unit 606 notifies the user of information by any method such as visually, audibly, or tactilely. The notification unit 606 notifies the user of, for example, the charging state of the TX301 or information indicating the state of power transmission in the wireless power transmission system including the TX301 and the RX101 as shown in Fig. 3. A specific hardware example of the notification unit 606 is similar to that of the notification unit 513 in Fig. 5, and therefore a description thereof will be omitted.

[0055] The operation unit 607 has a function of accepting operations from the user for the TX 301. A specific example of the hardware of the operation unit 607 is similar to that of the operation unit 512 in Fig. 5, and therefore a description thereof will be omitted.

[0056] The memory 608 stores various information such as identification information and capability information, control programs, etc. The capability information includes, for example, information indicating whether the device has a high-precision foreign object detection processing capability. Note that the memory 608 may store information obtained by a functional unit other than the control unit 601.

[0057] [Processing of power receiving devices] 7 is a flowchart showing an outline of the processing of the RX101. This processing can be implemented, for example, by the control unit 505 of the RX101 executing a program read from the memory 506. Note that at least part of the following procedure may be implemented by hardware. In this case, the hardware can be implemented, for example, by 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.

[0058] In S701, the RX101 starts the periodic NFC tag detection and authentication (detection and authentication) flow processing. The periodic NFC tag detection and authentication flow is started, for example, at one of the following three times: (a) The timing when the user performs a predetermined operation via the operation unit 512 of the RX101 (b) Timing when the RX101 is turned on (c) The timing when the sensor 103 detects that the compatible product 201 is attached to the RX101 The "predetermined operation" in (a) is an operation for executing an NFC tag detection and authentication flow, or any other operation.

[0059] In S702, the RX101 executes an NFC tag detection and authentication flow. When the RX101 detects the NFC tag 202 of the compatible product 201, and if the NDEF information (tag information) of the NFC tag 202 contains authentication information, the RX101 executes authentication processing according to the conditions described below.

[0060] In S703, the RX101 executes wireless power transmission processing based on the WPC standard and receives power from the TX301. Here, the RX101 executes wireless power transmission pre-setting processing and sets wireless power transmission according to the authentication status of the compatible product 201. The wireless power transmission pre-setting processing will be abbreviated as pre-setting processing below.

[0061] In this embodiment, as an example of the pre-setting process, a process of determining parameters to be used for detecting the state of wireless power transmission based on the WPC standard is shown, based on the authentication state of the compatible product 201 and information included in the NFC tag of the compatible product 201. Details will be described later.

[0062] Figures 8 and 9 are flowcharts showing details of the NFC tag detection and authentication flow (S702) in Figure 7. Figure 10 is a flowchart showing details of the NFC tag detection process (mainly S801 to S803) in Figure 8.

[0063] In FIG. 8, first, in S801, the RX101 executes NFC tag detection processing. As shown in FIG. 10, after starting processing, in S901 the RX101 sets the type of NFC tag to be detected. There are multiple types of NFC tags, including Type-A, Type-B, and Type-F, and the RX101 sets the type of NFC tag that has not yet been detected. In S902, the RX101 executes NFC tag detection. This can be executed by a reader / writer function that complies with the NFC standard. Specifically, the RX101 transmits a carrier wave and modulates the carrier wave to send a message for detecting an NFC tag of the set type. When an NFC tag receives a message from RX101, it responds to this message by applying load modulation to the transmitted carrier wave. This allows the RX101 to detect the NFC tag 202.

[0064] In S903, the RX101 determines whether or not the detection of the NFC tag 202 was successful. If the RX101 determines that the detection of the NFC tag 202 was successful (YES in S903), then in S904 it stores the NDEF information read from the NFC tag 202. On the other hand, if the RX101 determines that the NFC tag detection failed (NO in S903), it ends the processing. When storing the NDEF information in S904, the RX101 manages information for each NFC tag that was detected.

[0065] In S905, the RX101 determines whether detection processing has been performed for all types of NFC tags (Type-A / Type-B / Type-F). If the RX101 determines that detection has been performed for all types (YES in S905), the RX101 ends the processing. On the other hand, if the RX101 determines that detection has not been performed for all types (NO in S905), the RX101 returns to S901 and performs NFC tag detection processing for the next type.

[0066] The above is the NFC tag detection process (mainly S801 to S803) executed in Fig. 8. By performing detection processes for all NFC tag types, the situation can be properly understood even when multiple NFC tags are present near the RX101. For example, if there are two NFC tags and they are different types, the NDEF information can be read from all of the tags.

[0067] Returning to the explanation of the flowchart in Fig. 8, in S802, the RX101 determines whether or not an NFC tag has been detected in the NFC tag detection process of S801. If an NFC tag has not been detected (No in S802), the process ends. If the RX101 has detected an NFC tag (Yes in S802), the RX101 determines whether or not reading the NFC tag was successful in S803. If reading the NFC tag was not successful (No in S803), the process ends. If reading the NFC tag was successful (Yes in S803), the RX101 stores the NDEF information of all NFC tags that were successfully read in memory.

[0068] In S804, the RX101 checks all NDEF information detected from one NFC tag that has not yet been processed. Checking the NDEF information means analyzing the NDEF information 1001 to 1003 shown in Fig. 11(A). The NFC tag 202 of the compatible product 201 is assumed to be an NFC tag implemented by the provider of the compatible product 201, and as an example, has three pieces of NDEF information.

[0069] The NDEF information 1001 is information relating to the product information of the compatible product 201. Possible information includes information on the device type (e.g., information indicating that the type of the compatible product 201 is a cover), manufacturer information, product model, serial number, etc. The product information of the compatible product 201 is an example of second information.

[0070] The NDEF information 1002 is information relating to the authentication of the compatible product 201, and is assumed to be, for example, an authentication key. The information relating to the authentication of the compatible product 201 is an example of first information.

[0071] The NDEF information 1003 is information that allows power transmission for the NFC tag 202 of the compatible product 201 (information regarding the permission of power transmission), and is assumed to include the version of wireless power transmission, information regarding whether power transmission is permitted, and the permitted power value (e.g., 8 W). In this embodiment, the "power transmission" mainly refers to power transmission for wireless charging of the RX101. "Power transmission is permitted" means that power transmission is permitted as long as it is of a level that does not damage the NFC tag 202, for example.

[0072] The NDEF information is not limited to that shown in Fig. 11(A), and various information can be set depending on the intended use of the provider of the compatible product 201. Also, in Fig. 11(A), three pieces of NDEF information are stored in the NFC tag 202, but a greater or lesser number of pieces of NDEF information may be stored. The same applies to Figs. 11(B), (C), and (D), which will be described later.

[0073] 9, in S805, the RX101 determines whether or not the NDEF information confirmed in S804 contains authentication information for the compatible product 201 (NDEF information 1002 in FIG. 11A). If there is no authentication information for the compatible product 201 (No in S805), the RX101 does not perform authentication processing and proceeds to S812. If there is authentication information for the compatible product 201 (Yes in S805), the RX101 determines in S806 whether or not the sensor 103 has detected that the compatible product 201 is attached to the RX101.

[0074] If attachment is not detected (No in S806), in S807 the RX101 transitions to a compatible product unauthenticated state and stores in memory the fact that the compatible product 201 is in an unauthenticated state. Then, the process proceeds to S812. The compatible product unauthenticated state means that authentication of the compatible product 201 has not been successful.

[0075] Furthermore, if attachment is not detected (No in S806), even if the compatible product 201 is already in an authenticated state, the RX101 cancels the authentication. That is, the state of the compatible product 201 transitions to an unauthenticated compatible product state (S807). Whether the compatible product 201 is in an authenticated state can be determined by performing the processes of S809 to S811, as will be described later. That is, if the compatible product 201 was attached to the RX101 last time, and authentication processing for the compatible product 201 was executed and authentication was successful, the fact that the compatible product is in an authenticated compatible product state is stored in memory, and therefore the device can determine that the compatible product 201 is in an authenticated state.

[0076] If it is detected that the compatible product 201 is attached to the RX101 (Yes in S806), the RX101 determines in S808 whether or not the compatible product is already in an authenticated state. The authenticated state means that the authentication of the compatible product 201 has been successful. If the compatible product is in an authenticated state (Yes in S808), the RX101 does not perform authentication processing and proceeds to S812.

[0077] If the compatible product is not in an authenticated state (No in S808), in S809 the RX101 executes authentication processing for the compatible product 201. The RX101 performs authentication by processing at least the authentication information (NDEF information 1002 (authentication key)) of the NDEF information in the NFC tag of the compatible product 201, and stores the result of the authentication processing. In S810, the RX101 determines whether or not the authentication processing for the compatible product was successful. If the authentication processing for the compatible product was successful (Yes in S810), the RX101 transitions to a compatible product authenticated state in S811, stores the fact that the compatible product is in an authenticated state in memory, and proceeds to S812. If the authentication processing for the compatible product was not successful (No in S810), the RX101 proceeds to S812 without transitioning to an authenticated state.

[0078] As described above, if the compatible product 201 is once successfully authenticated and then, for example, the compatible product 201 is removed from the RX 101, the state of the compatible product 201 can be returned to an unauthenticated compatible product state. Therefore, if the compatible product 201 is subsequently attached to the RX 101 again, appropriate authentication processing can be executed again.

[0079] In S812, the RX101 determines whether or not there is NDEF information other than authentication information in the NFC tag being processed. If there is no NDEF information other than authentication information (No in S812), the process proceeds to S814. If there is NDEF information other than authentication information (Yes in S812), the RX101 executes processing on the first NDEF information other than authentication information in S813. Taking the NDEF information in FIG. 11(A) as an example, this corresponds to processing the NDEF information 1001, and it is expected that the RX101 will read information on the device type, manufacturer information, serial number, etc. of the compatible product 201. Thereafter, the process of the RX101 proceeds to S814.

[0080] The control unit 505 and the program for the authentication process are an example of an authentication means that performs authentication of a compatible product.

[0081] In the NFC tag, the NDEF information is read in order from the left side of FIG. 11(A). In other words, the NDEF information 1001 is read first. Alternatively, when the NDEF information is stored in the NFC tag, it may be stored linked to an ID or number that identifies the NDEF information. In this case, the RX101 may read the NDEF information in ID or number order.

[0082] In S814, the RX101 determines whether or not an NFC tag other than the NFC tag processed in S804 has been detected. If an NFC tag other than the processed NFC tag has been detected (Yes in S814), the RX101 returns to S804 and executes subsequent processing again for the one NFC tag other than the processed NFC tag. If the RX101 has not detected an NFC tag other than the processed NFC tag (No in S814), the processing ends.

[0083] FIG. 12 is a flowchart showing the details of the processing of wireless power transmission by the RX101 based on the WPC standard in S703 of FIG. In S1101, RX101 executes the processes defined as the Selection phase and Ping phase of the WPC standard, and waits for its own device to be placed on TX301. RX101 detects that it has been placed on TX301, for example, by detecting a Digital Ping from TX301. When RX101 receives a Digital Ping from TX301, it transmits a Signal Strength (SIG) data packet to TX301.

[0084] In S1102, when the RX101 detects that its own device has been placed on the TX301, it executes the pre-setting process.

[0085] FIG. 13 is a flowchart showing an example of the above-mentioned presetting process (S1102) by the RX101. In this process, parameters used for status detection related to wireless power transmission based on the WPC standard are determined based on the authentication status of the compatible product 201 and information included in the NFC tag of the compatible product 201. Status detection refers to detecting the status of the RX101 and TX301 when the RX101 is in a state where it can receive power from the TX301. Status detection includes, for example, foreign object detection and coupling status detection. Hereinafter, the process related to this status detection will be referred to as the "status detection process," and this includes the foreign object detection process, the coupling status detection process, and so on. In addition, below, the parameters used for status detection (shown as "parameters related to status detection" in the figure) will be abbreviated as the "status detection parameters."

[0086] In the state detection process, if the parameters used for calculation during the state detection process are the same whether or not the compatible product 201 is attached to the RX101, highly accurate detection cannot be performed. At least when the compatible product 201 is attached to the RX101, highly accurate state detection adapted to the state in which the compatible product 201 is attached can be achieved by setting the state detection parameters.

[0087] The foreign object detection process is, for example, a process in which the TX301 detects whether or not a foreign object exists between the RX101 and the TX301 when the RX101 is placed on the TX301. In this case, the state detection parameters are constants related to the RX101 that are used in this foreign object detection process. The constants related to the RX101 are, for example, values ​​that are set based on the structure (e.g., the thickness and shape of the housing), material, or state of the RX101, or thresholds used in calculations to execute a predetermined foreign object detection method. If the TX301 transmits wireless power to the RX101 when a foreign object exists between the RX101 and the TX301, an overcurrent may occur in the foreign object, causing heat generation and potentially posing a risk. Therefore, the TX301 executes the foreign object detection process, and if a foreign object is detected, it takes appropriate measures, such as stopping power transmission or reducing the transmitted power.

[0088] For example, the foreign object detection process may be performed by the following method. For example, the efficiency of the power transmission when the TX301 transmits power to the RX101 in a state where no foreign object is present is calculated in advance. The efficiency of the power transmission when the TX301 transmits power to the RX101 is the ratio of the power received by the RX101 to the power transmitted by the TX301. Then, if the efficiency of the power transmission when the TX301 is transmitting power falls below the efficiency of the power transmission when no foreign object is present, it is determined that a foreign object is present. The pre-setting process in this embodiment is, for example, a process of determining (setting) constants related to the RX101 that the TX301 uses to calculate the above-mentioned efficiency of the power transmission. Alternatively, when a compatible product is attached to the RX101 and the product information (NDEF information 1001) of the compatible product is read, the pre-setting process is a process of determining constants related to the compatible product 201 that are used to calculate the efficiency of the power transmission. Alternatively, it may be both the constants related to the RX101 and the constants related to the corresponding product 201.

[0089] Alternatively, the foreign object detection process can be performed using another method such as the following. For example, the power loss when the TX301 transmits power to the RX101 in a state where no foreign object is present is calculated in advance. The power loss when the TX301 transmits power to the RX101 is the difference between the power transmitted by the TX301 and the power received by the RX101. Then, if the power loss while the TX301 is transmitting power exceeds the power loss in a state where no foreign object is present, it is determined that a foreign object is present. The presetting process in this embodiment is, for example, a process of determining a constant related to the RX101 that the TX301 uses to calculate the amount of power loss in a state where no foreign object is present.

[0090] The coupling state detection process is, for example, a process in which the TX301 detects the electromagnetic coupling state between the power receiving coil 104 of the RX101 and the power transmitting coil 310 of the TX301. In this case, the state detection parameter is a constant used in the coupling state detection process. More specifically, the state detection parameter is a constant related to the RX101 that is used in the process in which the TX301 calculates the coupling coefficient or coupling factor between the power receiving coil 104 of the RX101 and the power transmitting coil 310 of the TX301. By calculating the coupling coefficient or coupling factor, the TX301 can estimate whether or not there is a positional deviation between the power receiving coil 104 of the RX101 and the power transmitting coil 310 of the TX301 while power is being transmitted to the RX101.

[0091] In this embodiment, the "state detection parameter" corresponds to, for example, a "constant related to RX101" and / or a "constant related to corresponding product 201." Alternatively, it is not limited to these "constants," and may be a predetermined calculation formula or the like.

[0092] The control unit 505 and the program that executes the process of setting (determining) the status detection parameters are an example of a determination means that determines the status detection parameters based on one or more predetermined conditions, including whether or not a combination of the power receiving device and a compatible product has been detected. In this embodiment, there are multiple predetermined conditions. As will be described in the flowchart of FIG. 13 below, the multiple conditions are conditions for determination in several determination processes (e.g., S1203 to S1205) after S1202. This also applies to the flowcharts in the second embodiment (FIG. 16), the third embodiment (FIG. 17), and the fourth embodiment (FIGS. 18 to 20).

[0093] Referring to FIG. 13, when the process starts, in S1201, the RX101 sets a power profile (power profile information, power profile compatibility information) for wireless power transmission based on the WPC standard that the device itself supports. The power profile is one of the standards in the WPC standard, and examples thereof include BPP (Baseline Power Profile) and EPP (Extended Power Profile). The maximum power supply amount is 5 W for BPP and 15 W for EPP. Another example of a power profile is MPP. In this embodiment, the power profile is set based on information pre-recorded in the memory 506 of the RX101. In this embodiment, for example, the RX101 also supports MPP, and the MPP is set as the power profile, and the RX101 stores this setting in the memory 506. Note that MPP is an abbreviation for Magnetic Power Profile.

[0094] In S1202, the RX101 determines whether or not it has detected that a compatible product is attached to the RX101. Note that this determination process has already been performed in S806 (FIG. 9) in S702, and therefore the result of that determination can be used in S1202. If it has not detected that a compatible product is attached (No in S1202), in S1207 the RX101 sets parameters based on the power receiving device, which are pre-recorded in the memory 506, as status detection parameters. The RX101 then stores these settings in the memory 506 and ends the process.

[0095] Here, the state detection parameter based on the power receiving device is a state detection parameter acquired in advance based on the power receiving device, and is assumed to be, for example, any one of the following. Parameters measured by the manufacturer of RX101 when the compatible product 201 is not attached to the RX101, such as during the manufacturing stage (before shipping the product, the same applies below). - Parameter calculated mainly by the manufacturer of RX101, assuming that the compatible product 201 is not attached to the RX101 during the manufacturing stage of the product. Parameters set mainly by purchasers and users of RX101, for example, when initializing the product, assuming that the compatible product 201 is not attached to the RX101.

[0096] Hereinafter, the term "state detection parameters based on the power receiving device" has the same meaning as above.

[0097] If the RX101 detects that a compatible product is attached (Yes in S1202), the process proceeds to S1203, where it determines whether the compatible product has been authenticated. This determination is made based on the information about the authentication status stored in the memory 506 in S811 when the NFC tag detection and authentication flow was executed in S702.

[0098] If the compatible product has not been authenticated (No in S1203), the RX101 executes the above-described process in S1207 and ends the process. If the compatible product has been authenticated (Yes in S1203), the RX101 determines in S1204 whether or not the product information of the compatible product 201 has been read from the NDEF information of the NFC tag of the compatible product 201. Here, the product information refers to the information included in the NDEF information 1001 in FIG. 11(A) (device type, manufacturer, product model, serial number, etc.). In S1204, when the NFC tag detection and authentication flow was executed in S702, it is determined whether or not the product information has been read based on the NDEF information of the NFC tag of the compatible product 201 that was stored in the memory 506 in S801.

[0099] If the product information of the compatible product 201 has not been read (No in S1204), the RX101 executes the above-described process in S1207 and ends the process. If the product information of the compatible product 201 has been read (Yes in S1204), the RX101 determines in S1205 whether or not a status detection parameter based on the product information of the compatible product exists in the memory 506. This status detection parameter based on the product information of the compatible product is a parameter acquired in advance based on the product information of the compatible product.

[0100] The state detection parameter based on the product information of the compatible product is a state detection parameter acquired in advance based on the product information of the compatible product, and is assumed to be, for example, any one of the following. Parameters measured by the manufacturer of the compatible product 201 when the compatible product 201 is attached to the RX101, mainly during the manufacturing stage of the product (before shipping the product, the same applies below). -Parameters calculated mainly by the manufacturer of the compatible product 201, assuming that the compatible product 201 is attached to the RX101 during the manufacturing stage of the product. Parameters set by purchasers or users of the compatible product 201 and RX101, assuming that the compatible product 201 is attached to the RX101, for example, during initial product setup.

[0101] Hereinafter, "state detection parameters based on product information of the corresponding product" has the same meaning as above.

[0102] If the status detection parameters based on the product information of the corresponding product 201 do not exist in the memory 506 (No in S1205), the RX101 executes the above-mentioned processing in S1207 and ends the processing. If the status detection parameters based on the product information of the corresponding product 201 exist in the memory 506 (Yes in S1205), the RX101 executes the following processing in S1206. That is, the RX101 sets the status detection parameters based on the product information of the corresponding product 201 recorded in the memory 506, stores this setting in the memory 506, and ends the processing.

[0103] Returning to the explanation of Figure 12, in S1103, the RX101 executes processing defined as the Identification and Configuration phase (I&C phase) of the WPC standard. In the I&C phase, the RX101 transmits an Identification Data Packet (ID Packet) to the TX301. The ID Packet stores the Manufacturer Code and Basic Device ID, which are identification information for each individual RX101, as well as information elements that can identify the version of the WPC standard that is supported.

[0104] The RX101 may transmit its identification information to the TX 301 by using an Extended Identification Data Packet (XID Packet). The RX101 also transmits a Configuration Data Packet to the TX 301. The Configuration Data Packet contains the following capability information (device configuration information) of the RX101. Information that can identify the version of the WPC standard that the RX101 supports Maximum Power Value or Reference Power, which is a value that specifies the maximum power that the RX101 can supply to a load. Information indicating whether the RX101 has the WPC standard negotiation function Parameters used in frequency shift keying, a communication modulation method used when TX301 transmits information to RX101

[0105] However, this information is merely an example, and the identification information and capability information of the RX 101 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 the individual RX 101, such as a Wireless Power ID. Furthermore, the RX 101 may transmit the identification information and capability information by a method other than communication in the I&C phase of the WPC standard.

[0106] Here, RX101 includes the information on the power profile of the WPC standard that its own device supports, which was set in S1102, in either an ID packet, XID packet, or configuration data packet and notifies TX301. Upon receiving this notification, TX301 compares the information on the power profile of the WPC standard that RX101 supports with the power profiles of the WPC standard that TX301 supports, and determines the power profile to use.

[0107] For example, the TX301 sets the priority of the power profiles to be used in advance, and selects and determines the power profile with the highest priority from among the power profiles supported by both the TX301 and the RX101. For example, the priorities of the power profiles to be used are set as follows: 1st: MPP, 2nd: EPP, 3rd: BPP. If the power profiles supported by both the TX301 and the RX101 are MPP and BPP, then MPP is selected and determined as the power profile to be used.

[0108] As another example, the RX101 may include information about the power profiles it supports, along with their priority, in an ID, XID, or configuration data packet and notify the TX301. In this case, the TX301 selects and determines the power profile with the highest priority among the power profiles supported by both the TX301 and RX101 that it has received notification of from the RX101.

[0109] Furthermore, RX101 notifies TX301 of the state detection parameters set in S1102 by including them in an ID packet, XID packet, or configuration data packet. Alternatively, RX101 may notify TX301 of the state detection parameters set in S1102 by including them in a predetermined packet in the negotiation phase of the WPC standard, which will be described later. Upon receiving this notification, TX301 performs state detection processing based on the state detection parameters notified by RX101 in wireless power transmission processing based on the WPC standard after this negotiation phase. In other words, TX301 can perform one or more state detection processing in one or more of the negotiation phase, calibration phase, and power transfer phase.

[0110] In S1104, after transmitting the identification information and capability information, the RX101 starts communication in the negotiation phase defined in the WPC standard. In the negotiation phase, the RX101 transmits a requested power value to the TX301, and determines a GP value between the RX101 and the TX301. The GP is an example of power information indicating the power that the power receiving device requests from the power transmitting device.

[0111] After determining the GP, in S1105, the RX101 starts communication in the calibration phase defined in the WPC standard. In the calibration phase, the RX101 transmits information about a predetermined received power value to the TX301 so that the TX can derive the relationship between the transmitted power and the received power in a state without a foreign object. Here, the information about the predetermined received power value includes the received power value in a light load state and the received power value in a maximum load state. Note that the RX101 may notify the TX301 of state detection parameters in this calibration phase.

[0112] After transmitting the information on the received power value, the RX101 starts receiving power through communication in the Power Transfer phase specified in the WPC standard in S1106. After that, when the battery reaches full charge, the RX101 transmits End Power Transfer (EPT) in accordance with the WPC standard. This stops power transmission from the TX301, and the series of processes for contactless charging ends.

[0113] [System-wide processing] 14 and 15 are sequence diagrams showing the processing of the entire system. In this example flowchart, the initial state is a state in which the RX101 is not mounted on the TX301 (a state in which power reception is not possible), and the RX101 is mounted on the TX301 at F1311.

[0114] In F1301, the RX101 starts a periodic NFC tag detection and authentication flow. Although not shown, the RX101 periodically executes the NFC tag detection and authentication flow at predetermined time intervals. In this example, it is assumed that after the periodic NFC tag detection and authentication flow starts, the compatible product 201 is attached to the RX101 (F1302).

[0115] In F1303, the RX101 executes the NFC tag detection and authentication flow, and performs the reading and authentication process of the NFC tag of the compatible product 201.

[0116] In F1304, the RX101 acquires NDEF information related to authentication (authentication information (e.g., authentication key)) from the NFC tag of the compatible product 201.

[0117] In steps F1305 to F1309, the RX101 performs predetermined processing based on the authentication information acquired in step F1304. That is, the RX101 executes authentication processing according to conditions, transitions the state of the compatible product 201, and stores that state (authenticated or unauthenticated) in memory, as shown in the flowchart in Fig. 8.

[0118] In F1310, the RX101 processes NDEF information other than the NDEF information related to the authentication of the compatible product 201, and if another NFC tag is detected, processes the other NFC tag.

[0119] When the RX101 is mounted on the TX301 at F1311, the TX301 and RX101 execute communication in the Ping phase of the WPC standard at F1312, causing the TX301 to detect at F1313 that the RX101 has been mounted on its own device. Also, at F1314, the RX101 detects that its own device has been mounted on the TX301. After that, at F1315, the RX101 executes pre-setting processing as shown in the flowchart in Figure 13. Specifically, the RX101 sets the power profile and state detection parameters of the WPC standard that the RX101 supports.

[0120] RX101 transmits identification information and capability information to TX301 through communication in the I&C phase of the WPC standard (not shown). In the I&C phase, at F1316, RX101 notifies TX301 of information about the power profile of the WPC standard that RX101 supports. At F1317, TX301 determines the power profile to use based on information about the power profile of the WPC standard that RX101 supports and information about the power profile of the WPC standard that TX301 supports. At F1318, RX101 requests information about the power profile to use from TX301. This request can be realized by transmitting a General Request Data Packet to TX301. At F1319, TX301 responds to the request from RX101 for information about the power profile to use, and notifies RX101 of the power profile to use. The TX301 can notify the RX101 of the power profile to be used by transmitting a Power Transmitter Identification Data Packet (TX ID Packet) to the RX101.

[0121] In F1320, RX101 notifies the TX301 of the state detection parameters. Upon receiving this notification, TX301 executes state detection processing based on the state detection parameters notified by RX101 in the subsequent processing of wireless power transmission based on the WPC standard.

[0122] At F1321 to F1323, the TX301 and RX101 communicate in the negotiation phase of the WPC standard, then proceed to the power transfer phase and start power transmission and reception processing. When the battery is fully charged, at F1324 the RX101 sends an end power transfer data packet (EPT packet) to the TX301 requesting that power transmission be stopped. Upon receiving the EPT packet, the TX301 stops power transmission.

[0123] According to the present embodiment described above, once the RX101 has successfully authenticated the compatible product 201, it is possible to avoid performing the authentication process again in the next periodic NFC tag detection process. This makes it possible to avoid an increase in the power consumption of the RX101 and a decrease in the processing performance of other applications. Furthermore, if the compatible product 201 is removed from the RX101 after it has been successfully authenticated once, the state of the compatible product 201 can be returned to an unauthenticated compatible product state. Therefore, if the compatible product 201 is subsequently attached to the RX101 again, it is possible to perform the appropriate authentication process again.

[0124] Furthermore, the RX101 can set appropriate state detection parameters according to the authentication status of the compatible product 201. For example, when the compatible product 201 is attached to the RX101 and authentication is successful, the RX101 can set state detection parameters that take into account the influence of the compatible product 201 and notify the TX301. This enables highly accurate state detection processing adapted to the state in which the compatible product 201 is attached, for example, when the compatible product 201 is attached to the RX101. As a result, efficient power transmission processing is possible.

[0125] As described above, the RX101 can perform appropriate processing that takes into account the influence of compatible products during power transmission processing.

[0126] Second Embodiment The second embodiment will be described in detail below with reference to the accompanying drawings. Further, duplicated descriptions of configurations that are the same as or similar to those of the first embodiment will be omitted. In the second embodiment, an example will be shown in which the state detection parameters themselves are included in the NDEF information of the NFC tag of the compatible product 201.

[0127] The configuration example of the system in this embodiment, and the configurations of the power receiving device (RX101), compatible product 201, and power transmitting device (TX301) are the same as those in the first embodiment, and therefore a description thereof will be omitted.

[0128] [Processing of power receiving devices] An overview of the processing of RX101 is shown in Fig. 7, as in the first embodiment. Details of the processing of the NFC tag detection and authentication flow (S702) are also shown in Figs. 8 and 9, as in the first embodiment. Details of the NFC tag detection processing (mainly S801 to S803) in Fig. 8 are also shown in Fig. 10, as in the first embodiment.

[0129] In this embodiment, in S804 of Fig. 8, the RX 101 checks all NDEF information detected from one NFC tag that has not yet been processed. Checking the NDEF information means analyzing the NDEF information 1011 to 1014 shown in Fig. 11(B). The NFC tag 202 of the compatible product 201 is assumed to be an NFC tag implemented by the provider of the compatible product 201, and as an example, has four pieces of NDEF information.

[0130] NDEF information 1011, NDEF information 1012, and NDEF information 1013 are similar to the NDEF information 1001, NDEF information 1002, and NDEF information 1003 in FIG. 11A, respectively. NDEF information 1014 is a state detection parameter adapted to a state in which the corresponding product 201 is attached to the RX101. For example, the state detection parameter is a parameter related to a foreign object detection process or a parameter related to a connection state detection process in the TX301. The state detection parameter adapted to a state in which the corresponding product is attached to the RX101 is a parameter measured in advance when the corresponding product is attached to the RX101. Alternatively, the state detection parameter adapted to a state in which the corresponding product is attached to the RX101 is a parameter calculated in advance assuming a state in which the corresponding product 201 is attached to the RX101. In other words, this state detection parameter is acquired by the manufacturer of the corresponding product 201 and / or RX101 during the product manufacturing stage. The NDEF information is not limited to that shown in FIG. 11(B), and various information can be set depending on the intended use of the provider of the compatible product 201.

[0131] The status detection parameter in the NDEF information 1014 is an example of second information, and is an example of information that identifies the status detection parameter. The information that identifies the status detection parameter may be the status detection parameter itself, such as the NDEF information 1014, or may be a URL or other address information that indicates the presence of information that indicates the status detection parameter.

[0132] Details of the processing of wireless power transmission by RX101 based on the WPC standard in S703 in Fig. 7 are shown in Fig. 12, similar to the first embodiment. In Fig. 12, the contents of each processing in S1101 and S1103 to S1106 are similar to those in the first embodiment.

[0133] Fig. 16 is a flowchart showing an example of the pre-setting process executed in S1102 of Fig. 12 in this embodiment. In this process, state detection parameters related to wireless power transmission based on the WPC standard are determined based on the authentication state of the compatible product 201 and information included in the NFC tag of the compatible product 201.

[0134] The processing from S1401 to S1403 is the same as the processing from S1201 to S1203 in FIG. 13 in the first embodiment, and therefore a description thereof will be omitted.

[0135] In S1404, the RX101 determines whether or not a status detection parameter has been read from the NDEF information (NDEF information 1014) of the NFC tag of the compatible product 201. This status detection parameter is a status detection parameter adapted to the state in which the compatible product 201 is attached to the RX101. The status detection parameter adapted to the state in which the compatible product 201 is attached to the RX101 is as described above. In S1404, the determination is made based on the NDEF information of the NFC tag of the compatible product 201 that was stored in the memory 506 in S801 when the NFC tag detection and authentication flow was executed in S702.

[0136] If the state detection parameters have not been read (No in S1404), in S1406, the RX101 sets, as the state detection parameters, state detection parameters based on the power receiving device that are pre-recorded in the memory 506. Then, the RX101 stores this setting in the memory 506 and ends the process.

[0137] If the state detection parameters have been read (Yes in S1404), in S1405 the RX 101 sets the state detection parameters, which are recorded in the memory 506 and are adapted to the state in which the compatible product 201 is attached to the RX 101. Then the RX 101 stores this setting in the memory 506 and ends the process.

[0138] The overall processing of the system in this embodiment is shown in FIGS. 14 and 15, similarly to the first embodiment.

[0139] As described above, according to this embodiment, it is possible to obtain the same effects as those described in the first embodiment. Furthermore, in this embodiment, the state detection parameters are stored in advance as NEDF information in the NFC tag 202, so that by reading this, the RX101 can set the read state detection parameters themselves in the pre-setting process.

[0140] As described above, the RX101 can perform appropriate processing that takes into account the influence of compatible products during power transmission processing.

[0141] Third Embodiment The third embodiment will be described in detail below with reference to the accompanying drawings. Further, duplicated descriptions of the same or similar configurations as those of the first and second embodiments will be omitted.

[0142] In the third embodiment, an example will be shown in which the NDEF information of the NFC tag of the compatible product 201 includes a correction value for the state detection parameter. The RX101 performs calculations based on this correction value for the state detection parameter and a state detection parameter adapted to a state in which the compatible product is not attached to the RX101, which is pre-recorded in the memory 506 of the RX101. As a result, the RX101 calculates and sets a state detection parameter adapted to a state in which the compatible product 201 is attached to the RX101.

[0143] The configuration example of the system in this embodiment, and the configurations of the power receiving device (RX101), compatible product 201, and power transmitting device (TX301) are the same as those in the first embodiment, and therefore a description thereof will be omitted.

[0144] [Processing of power receiving devices] An overview of the processing of RX101 is shown in Fig. 7, as in the first embodiment. Also, details of the processing of the NFC tag detection and authentication flow (S702) are shown in Fig. 8, as in the first embodiment. Also, details of the NFC tag detection processing in Fig. 8 (mainly S801 to S803) are shown in Fig. 10, as in the first embodiment.

[0145] In this embodiment, in S804 of Fig. 8, the RX 101 checks all NDEF information detected from one NFC tag that has not yet been processed. Checking the NDEF information means analyzing the NDEF information 1021 to 1024 shown in Fig. 11(C). The NFC tag 202 of the compatible product 201 is assumed to be an NFC tag implemented by the provider of the compatible product 201, and as an example, has four pieces of NDEF information.

[0146] NDEF information 1021, NDEF information 1022, and NDEF information 1023 are the same as the NDEF information 1001, NDEF information 1002, and NDEF information 1003 in FIG. 11A, respectively. NDEF information 1024 is a correction value for a state detection parameter when the compatible device 201 is attached to the RX101. The correction value for the state detection parameter is a correction value for correcting the influence of the compatible device 201 on state detection. For example, it is a correction value for a parameter related to foreign object detection processing in the TX301 or a correction value for a coupling state detection parameter. The RX101 performs calculations based on the correction value for the state detection parameter and a state detection parameter that is pre-recorded in the memory 506 of the RX101 and that is adapted to a state when the compatible device is not attached to the RX101. The state detection parameter that is adapted to a state when the compatible device is not attached to the RX101 is, in other words, the "state detection parameter based on the power receiving device" described above. As a result, the RX 101 calculates a state detection parameter adapted to the state in which the compatible product 201 is attached to the RX 101. The NDEF information is not limited to that shown in Fig. 11(C), and various information can be set depending on the intended use of the provider of the compatible product 201.

[0147] In this embodiment, the correction information is not limited to the correction value of the state detection parameter, but may be any correction information for correcting the influence of the counterpart 201 in the state detection process. The correction information may include, for example, a predetermined arithmetic expression for correction. This correction information is an example of the second information.

[0148] Details of the processing of wireless power transmission by RX101 based on the WPC standard in S703 in Fig. 7 are shown in Fig. 12, similar to the first embodiment. In Fig. 12, the contents of each processing in S1101 and S1103 to S1106 are similar to those in the first embodiment.

[0149] Fig. 17 shows an example of the pre-setting process executed in S1102 of Fig. 12 in this embodiment. In this process, parameters to be used for detecting the state of wireless power transmission based on the WPC standard are determined based on the authentication state of the compatible product 201 and information included in the NFC tag of the compatible product 201.

[0150] The processing from S1501 to S1503 is the same as the processing from S1201 to S1203 in FIG. 13 in the first embodiment, and therefore a description thereof will be omitted.

[0151] In S1504, the RX101 determines whether or not the correction value of the state detection parameter has been read from the NDEF information of the NFC tag of the compatible product 201. When the NFC tag detection and authentication flow was executed in S702, it is determined whether or not the correction value has been read based on the NDEF information of the NFC tag of the compatible product 201 stored in the memory 506 in S801.

[0152] If the correction values ​​for the state detection parameters have not been read (No in S1504), in S1506 the RX101 sets, as the state detection parameters, state detection parameters based on the power receiving device that are pre-recorded in the memory 506. Then, the RX101 stores these settings in the memory 506 and ends the process.

[0153] If the correction values ​​of the state detection parameters have been read (Yes in S1504), the RX101 performs the following processing in S1505. The RX101 performs a predetermined calculation using the state detection parameter correction values ​​stored in the memory 506 and state detection parameters that are pre-recorded in the memory 506 of the RX101 and are adapted to a state in which the corresponding product 201 is not attached to the RX101. As a result, the RX101 calculates and determines state detection parameters that are adapted to a state in which the corresponding product 201 is attached to the RX101. The determined state detection parameters that are adapted to a state in which the corresponding product 201 is attached to the RX101 are set, and this setting is stored in the memory 506, ending the processing.

[0154] The overall processing of the system in this embodiment is shown in FIGS. 14 and 15, similarly to the first embodiment.

[0155] As described above, according to this embodiment, it is possible to obtain the same effects as those described in the first embodiment. Furthermore, in this embodiment, the correction values ​​of the state detection parameters are stored in advance as NEDF information in the NFC tag 202, so that by reading this, the RX 101 can calculate the state detection parameters based on the correction values ​​in the pre-setting process.

[0156] As described above, the RX101 can perform appropriate processing that takes into account the influence of compatible products during power transmission processing.

[0157] <Fourth embodiment> The fourth embodiment will be described in detail below with reference to the accompanying drawings. Further, duplicated descriptions of configurations that are the same as or similar to those of the first to third embodiments will be omitted.

[0158] The fourth embodiment will show an example of processing in the case where, for example, the NDEF information of the NFC tag of the compatible product 201 does not include information related to authentication but does include a correction value for the state detection parameter. The RX101 performs calculations using the correction value for the state detection parameter and a state detection parameter that is adapted to a state in which the compatible product is not attached to the RX101 and that is pre-recorded in the memory 506 of the RX101. As a result, even if the NDEF information of the NFC tag of the compatible product 201 does not include information related to authentication, the RX101 calculates and sets a state detection parameter that is adapted to a state in which the compatible product 201 is attached to the RX101.

[0159] In this embodiment, if the NDEF information of the NFC tag of the compatible product 201 includes information related to authentication, the following processing is performed. That is, similar to the first and second embodiments, the RX101 sets state detection parameters (state detection parameters based on the product state of the compatible product) adapted to the state in which the compatible product 201 is attached to the RX101. This is processing that goes through Yes in S1603 in Fig. 18, as will be described later.

[0160] The configuration example of the system in this embodiment, and the configurations of the power receiving device (RX101), compatible product 201, and power transmitting device (TX301) are the same as those in the first embodiment, and therefore a description thereof will be omitted.

[0161] [Processing of power receiving devices] An overview of the processing of RX101 is shown in Fig. 7, as in the first embodiment. Also, details of the processing of the NFC tag detection and authentication flow (S702) are shown in Fig. 8, as in the first embodiment. Also, details of the NFC tag detection processing in Fig. 8 (mainly S801 to S803) are shown in Fig. 10, as in the first embodiment.

[0162] In this embodiment, in S804 of FIG. 8, the RX 101 checks all NDEF information detected from one NFC tag that has not yet been processed. Checking the NDEF information means analyzing the NDEF information shown in any one of FIGS. 11(A) to 11(D). The NFC tag 202 of the compatible product 201 is assumed to be an NFC tag implemented by the provider of the compatible product 201, and has three or four pieces of NDEF information, for example. NDEF information 1031, 1032, and 1033 in FIG. 11(D) are similar to the NDEF information 1021, 1023, and 1024 in FIG. 11(C), respectively. Note that the NFC tag shown in FIG. 11(D) does not include NDEF information that includes information related to authentication.

[0163] Details of the processing of wireless power transmission by RX101 based on the WPC standard in S703 in Fig. 7 are shown in Fig. 12, similar to the first embodiment. In Fig. 12, the contents of each processing in S1101 and S1103 to S1106 are similar to those in the first embodiment.

[0164] 18 and 19 show an example of the pre-setting process executed in S1102 of Fig. 12 in this embodiment. In this process, parameters to be used for detecting the state of wireless power transmission based on the WPC standard are determined based on the authentication state of the compatible product 201 and information included in the NFC tag of the compatible product 201.

[0165] The process of S1601 is the same as the process of S1201 in FIG. 13 in the first embodiment, and therefore a description thereof will be omitted.

[0166] In S1602, the RX101 determines whether or not it has detected that a compatible product is attached to the RX101. Note that this determination process has already been performed in S806 (FIG. 8) in S702, and therefore the result of that determination can be used in S1602. If it has not detected that a compatible product is attached (No in S1602), in S1609 the RX101 sets, as the status detection parameters, status detection parameters based on the power receiving device that are pre-recorded in the memory 506. The RX101 then stores this setting in the memory 506 and ends the process.

[0167] If the RX101 detects that a compatible product is attached (Yes in S1602), the process proceeds to S1603, where it determines whether the compatible product has been authenticated. In S1603, this determination is made based on the information about the authentication status stored in the memory 506 in S811 when the NFC tag detection and authentication flow was executed in S702.

[0168] If the compatible product is not in an authenticated state (No in S1603), the RX101 determines in S1607 whether or not the correction values ​​of the state detection parameters have been read from the NDEF information of the NFC tag of the compatible product 201. If the correction values ​​of the state detection parameters have not been read (No in S1607), the RX101 executes the process of S1609 described above and ends the process. If the correction values ​​of the state detection parameters have been read (Yes in S1607), the RX101 performs the following process in S1608. The RX101 performs calculations using the correction values ​​of the state detection parameters stored in the memory 506 and state detection parameters that are adapted to a state in which the compatible product is not attached to the RX101 and that are pre-recorded in the memory 506 of the RX101. As a result, the RX101 calculates and determines state detection parameters that are adapted to a state in which the compatible product 201 is attached to the RX101. The RX101 sets the state detection parameters that are adapted to the state in which the compatible product 201 is attached to the RX101, stores the settings in the memory 506, and ends the process.

[0169] If the compatible product is in an authenticated state (Yes in S1603), in S1604 the RX101 determines whether or not the product information of the compatible product 201 has been read from the NDEF information of the NFC tag of the compatible product 201. In S1604, the determination is made based on the NDEF information of the NFC tag of the compatible product 201 that was stored in the memory 506 in S801 when the NFC tag detection and authentication flow was executed in S702.

[0170] If the product information of the compatible product 201 has not been read (No in S1604), the RX101 executes the above-described processing in S1607. If the product information of the compatible product 201 has been read (Yes in S1604), the RX101 determines in S1605 whether or not state detection parameters based on the product information of the compatible product exist in the memory 506.

[0171] If the status detection parameters based on the product information of the corresponding product 201 do not exist in the memory 506 (No in S1605), the RX101 executes the above-mentioned processing in S1607. If the status detection parameters based on the product information of the corresponding product 201 exist in the memory 506 (Yes in S1605), the RX101 sets the status detection parameters based on the product information of the corresponding product 201 recorded in the memory 506 in S1606. The RX101 then stores this setting in the memory 506 and ends the processing.

[0172] The overall processing of the system in this embodiment is shown in FIGS. 14 and 15, similarly to the first embodiment.

[0173] As a modification of this embodiment, the example of the presetting process executed in S1102 of Fig. 12 may be the process shown in Fig. 20. In this case, the processes of S1601 to S1603 and S1707 to S1709 are the same as the processes of S1601 to S1603 of Fig. 18 and S1607 to S1609 of Fig. 19, respectively, and therefore description thereof will be omitted.

[0174] In S1704, the RX101 determines whether or not the status detection parameter has been read from the NDEF information (NDEF information 1014) of the NFC tag of the compatible product 201. This status detection parameter is a status detection parameter adapted to the state in which the compatible product 201 is attached to the RX101. The status detection parameter adapted to the state in which the compatible product 201 is attached to the RX101 is as described above. In S1704, the determination is made based on the NDEF information of the NFC tag of the compatible product 201 that was stored in the memory 506 in S801 when the NFC tag detection and authentication flow was executed in S702.

[0175] If the status detection parameters have not been read (No in S1704), the RX101 proceeds to the processing of S1707. If the status detection parameters have been read (Yes in S1704), in S1705 the RX101 sets the status detection parameters that are adapted to the status when the compatible product 201 is attached to the RX101, which are recorded in the memory 506. The RX101 then stores this setting in the memory 506 and ends the processing.

[0176] As described above, according to this embodiment, it is possible to obtain the same effects as those described in the first embodiment. In particular, in this embodiment, the RX101 can perform the following processing even when the compatible product 201 is attached to the RX101 and authentication has not been successful (NO in S1603). That is, when the RX101 reads a correction value for the state detection parameter from the NDEF information (YES in S1607, YES in S1707), it can calculate and set the state detection parameter based on the correction value. In this way, the RX101 can set the state detection parameter taking into account the influence of the compatible product 201 and notify the power transmitting device 301.

[0177] As described above, the RX101 can perform appropriate processing that takes into account the influence of compatible products during power transmission processing.

[0178] <Other embodiments> In the overall system processing shown in Fig. 13 of each embodiment, the processing from F1303 to F1310 may be executed between F1314 and F1315. Even in this case, the same effects as those shown in each embodiment can be obtained.

[0179] In each of the above embodiments, the compatible product 201 has an NFC tag, and authentication processing is performed to authenticate the compatible product. However, the use of a compatible product without an NFC tag is also included in the scope of the present disclosure. In this case, when it is detected that a compatible product without an NFC tag is attached to the RX101, a predetermined state detection parameter different from the "state detection parameter based on the power receiving device" may be set. The predetermined state detection parameter may be, for example, a constant state detection parameter that estimates the influence of the compatible product, regardless of the structure, etc., of the compatible product.

[0180] In the above embodiments, examples have been shown in which the TX 301 performs the state detection process, but this may also be performed by the RX 101. In this case, the RX 101 does not need to notify the TX 301 of the state detection parameters set in S1102, but may notify it in the same way as in the above embodiments.

[0181] 9, the order of S806 and S808 (S1203 of S1202 in FIG. 13) may be reversed. In this case, in S808, which is executed before S806, it is determined whether or not attachment of the compatible product 201 to the RX101 has been detected, both when the compatible product 201 is in an authenticated state (YES) and when the compatible product 201 is not in an authenticated state (NO). In this case, as with the example described in the explanation of FIG. 9, even if the compatible product 201 has already been authenticated, if attachment of the compatible product 201 has not been detected, processing is executed to cancel the authentication. Such processing can also be applied to FIGS. 16, 17, and 18.

[0182] In the first embodiment, the following is an example of a detection means for detecting that the RX101 and the compatible product 201 have been combined. For example, when the compatible product 201 is attached to or combined with the RX101, the RX101 detects the detectable part 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the RX101. However, this is not limiting, and for example, attachment may be detected by periodically detecting an NFC tag. Specifically, the following embodiments are envisioned. 10, the RX101 executes detection of the NFC tag 202 of the compatible product 201 (S902), and if NFC tag detection is successful (YES in S903), it stores the read NDEF information (S904). If, for example, information on the compatible product 201 in the NDEF information 1001 shown in Fig. 11 (device type, manufacturer, serial number, etc.) among the stored NDEF information satisfies a predetermined condition, the RX101 determines that the compatible product 201 has been attached to the RX101. The predetermined condition is, for example, that all of the following conditions are satisfied: ·Device type: Cover Manufacturer: This information must be set in advance on the RX101. Serial number: This must be the information that has been set in advance on the RX101.

[0183] Some (or in some cases all) of the components in the above embodiments may be replaced with other components that perform similar functions, or may be omitted, or other components may be added. Furthermore, the present invention is not limited to the WPC standard, and can be applied to various standards.

[0184] The power transmitting device and the power receiving device may be, for example, an image input device such as an imaging device (still camera, video camera, etc.) or a scanner, or an image output device such as a printer, a copier, a projector, etc. Furthermore, they may be storage devices such as a hard disk drive or a memory device, or information processing devices such as a personal computer (PC), a smartphone, or a tablet device.

[0185] The power receiving device of the present disclosure may also be an information terminal device. For example, the information terminal device has a display unit (display) that receives power from a power receiving antenna and displays information to a user. The power received from the power receiving antenna is stored in a power storage unit (battery), and power is supplied from the battery to the display unit. In this case, the power receiving device may have a communication unit that communicates with other devices different from the power transmitting device. The communication unit may be compatible with communication standards such as NFC communication and the fifth generation mobile communication system (5G).

[0186] The power receiving device of the present disclosure may also be a vehicle such as an automobile. For example, the automobile serving as the power receiving device may receive power from a charger (power transmitting device) via a power transmitting antenna installed in a parking lot. The automobile serving as the power receiving device may also receive power from the charger (power transmitting device) via a power transmitting antenna embedded in the road. Such an automobile supplies the received power to a battery. The battery's power may be supplied to a driving unit (motor, electric unit) that drives the wheels, or may be used to drive a sensor used for driving assistance or a communication unit that communicates with an external device. In other words, in this case, the power receiving device may include, in addition to the wheels, a battery, a motor or sensor that is driven using the received power, and a communication unit that communicates with devices other than the power transmitting device. Furthermore, the power receiving device may have a storage unit for accommodating a person. For example, the sensor may be a sensor used to measure the distance between vehicles or the distance to other obstacles. The communication unit may be compatible with, for example, a global positioning system (GPS). The communication unit may be compatible with communication standards such as the fifth generation mobile communication system (5G), etc. The vehicle may be a bicycle or a motorcycle.

[0187] The power receiving device of the present disclosure may also be an electric tool, a home appliance, or the like. These devices, which are power receiving devices, may have a battery and / or a motor that is driven by the received power stored in the battery. These devices may also have a notification means for notifying the user of the remaining battery charge, etc. These devices may also have a communication unit that communicates with other devices different from the power transmitting device. The communication unit may be compatible with communication standards such as NFC and the fifth generation mobile communication system (5G).

[0188] The power transmitting device of the present disclosure may also be an on-board charger that transmits power to a mobile information terminal device, such as a smartphone or tablet, that supports wireless power transmission within the vehicle. Such an on-board charger may be installed anywhere within the vehicle. For example, the on-board charger may be installed in the console of the vehicle, on the instrument panel (instrument panel, dashboard), between passenger seats, on the ceiling, or in the door. However, it is preferable that the on-board charger is not installed in a location that interferes with driving. Furthermore, although the power transmitting device has been described using the example of an on-board charger, such a charger is not limited to being installed in a vehicle, but may also be installed in transportation such as a train, airplane, or ship. In this case, the charger may also be installed between passenger seats, on the ceiling, or in the door.

[0189] The power transmitting device may also be a vehicle such as an automobile equipped with an on-board charger. In this case, the power transmitting device has wheels and a battery, and supplies power to the power receiving device via a power transmitting circuit unit and a power transmitting antenna using power from the battery.

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

[0191] In addition, some of the processes described with reference to the flowcharts in this disclosure may be implemented by hardware. For example, a specific compiler may be used to automatically generate a dedicated circuit on an FPGA from a program for implementing each step. Alternatively, a gate array circuit may be formed in the same manner as an FPGA and implemented as hardware.

[0192] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) A power receiving device, a detection means for detecting that the power receiving device and a compatible product are combined; and a determination means for determining parameters to be used in a state detection process for detecting the states of the power receiving device and the power transmitting device based on whether or not it is detected that the power receiving device and the compatible product are combined. A power receiving device characterized by: (Configuration 2) The device further includes an acquisition unit for acquiring tag information from an NFC (Near Field Communication) tag included in the compatible product, The determining means determines the parameter based on the tag information when it is detected that the power receiving device and the compatible product are combined. 2. The power receiving device according to configuration 1, (Configuration 3) The tag information includes product information of the corresponding product, The determining means determines the parameters based on product information of the corresponding product. 3. The power receiving device according to configuration 2. (Configuration 4) When the power receiving device has parameters based on product information of the compatible product, the determining means determines the parameters as parameters to be used in the state detection process, and when the power receiving device does not have parameters based on the product information of the compatible product, determines parameters acquired when the compatible product is not combined with the power receiving device as parameters to be used in the state detection process. 4. The power receiving device according to configuration 3. (Configuration 5) the tag information includes information for identifying the parameter, The determining means determines the parameter based on information for identifying the parameter. 3. The power receiving device according to configuration 2. (Configuration 6) the tag information includes correction information for correcting the influence of the corresponding product on the state detection process; The determining means determines the parameters based on the correction information. 3. The power receiving device according to configuration 2. (Configuration 7) The device further includes an authentication means for performing authentication processing of the compatible product. 7. The power receiving device according to any one of configurations 2 to 6, wherein: (Configuration 8) the authentication means performs the authentication process based on first information of the tag information; When the authentication process for the compatible product is successful, the determining means determines the parameter based on second information of the tag information that is different from the first information. 8. The power receiving device according to configuration 7. (Configuration 9) When the authentication of the compatible product by the authentication process is not successful, the determining means determines the parameters acquired when the compatible product is not combined with the power receiving device as the parameters to be used in the state detection process. 8. The power receiving device according to configuration 7. (Configuration 10) When the authentication process does not succeed in authenticating the compatible product and correction information for correcting the influence of the compatible product on the state detection process is acquired from the tag information, the determination means determines the parameters based on the correction information. 8. The power receiving device according to configuration 7. (Configuration 11) When the detection means does not detect that the power receiving device and the compatible product are combined, the determination means determines the parameters acquired when the compatible product is not combined with the power receiving device as the parameters to be used in the state detection process. 2. The power receiving device according to configuration 1, (Configuration 12) The state detection process is a process of detecting a foreign object between the power transmitting device and the power receiving device, or a process of detecting an electromagnetic coupling state between a power transmitting coil of the power transmitting device and a power receiving coil of the power receiving device. 12. The power receiving device according to any one of configurations 1 to 11. (Configuration 13) The power supply control device further includes a notification unit that notifies the power transmission device of the determined parameters. 13. The power receiving device according to any one of configurations 1 to 12. (method) A method performed by a power receiving device, a detecting step of detecting that the power receiving device and a compatible product are combined; and a determination step of determining parameters to be used in a state detection process for detecting the states of the power receiving device and the power transmitting device based on whether or not it is detected that the power receiving device and the compatible product are combined. A method characterized by: (program) A program for causing a computer to execute the above method.

[0193] The present disclosure has been described in detail above based on preferred embodiments thereof, but the present disclosure is not limited to the above embodiments, and various modifications are possible based on the gist of the present disclosure, and these modifications are not excluded from the scope of the present disclosure. [Explanation of symbols]

[0194] 101: Power receiving device 103: Sensor 104: Receiving coil 201: Compatible products 202: NFC tag 301: Power transmission equipment 310: Transmission coil 505: Control unit

Claims

1. A power receiving device, a detection means for detecting that the power receiving device and a compatible product are combined; and a determination means for determining parameters to be used in a state detection process for detecting the states of the power receiving device and the power transmitting device based on whether or not it is detected that the power receiving device and the compatible product are combined. A power receiving device characterized by:

2. The device further includes an acquisition unit for acquiring tag information from an NFC (Near Field Communication) tag included in the compatible product, The determining means determines the parameter based on the tag information when it is detected that the power receiving device and the compatible product are combined. The power receiving device according to claim 1 .

3. The tag information includes product information of the corresponding product, The determining means determines the parameters based on product information of the corresponding product. The power receiving device according to claim 2 .

4. When the power receiving device has parameters based on product information of the compatible product, the determining means determines the parameters as parameters to be used in the state detection process, and when the power receiving device does not have parameters based on the product information of the compatible product, determines parameters acquired when the compatible product is not combined with the power receiving device as parameters to be used in the state detection process. The power receiving device according to claim 3 .

5. the tag information includes information for identifying the parameter, The determining means determines the parameter based on information for identifying the parameter. The power receiving device according to claim 2 .

6. the tag information includes correction information for correcting the influence of the corresponding product on the state detection process; The determining means determines the parameters based on the correction information. The power receiving device according to claim 2 .

7. The device further includes an authentication means for performing authentication processing of the compatible product. The power receiving device according to claim 2 .

8. the authentication means performs the authentication process based on first information of the tag information; When the authentication process for the compatible product is successful, the determining means determines the parameter based on second information of the tag information that is different from the first information. The power receiving device according to claim 7 .

9. When the authentication of the compatible product by the authentication process is not successful, the determining means determines the parameters acquired when the compatible product is not combined with the power receiving device as the parameters to be used in the state detection process. The power receiving device according to claim 7 .

10. When the authentication process does not succeed in authenticating the compatible product and correction information for correcting the influence of the compatible product on the state detection process is acquired from the tag information, the determination means determines the parameters based on the correction information. The power receiving device according to claim 7 .

11. When the detection means does not detect that the power receiving device and the compatible product are combined, the determination means determines the parameters acquired when the compatible product is not combined with the power receiving device as the parameters to be used in the state detection process. The power receiving device according to claim 1 .

12. The state detection process is a process of detecting a foreign object between the power transmitting device and the power receiving device, or a process of detecting an electromagnetic coupling state between a power transmitting coil of the power transmitting device and a power receiving coil of the power receiving device. The power receiving device according to claim 1 .

13. The power supply control device further includes a notification unit that notifies the power transmission device of the determined parameters. The power receiving device according to claim 1 .

14. A method performed by a power receiving device, a detecting step of detecting that the power receiving device and a compatible product are combined; and a determination step of determining parameters to be used in a state detection process for detecting the states of the power receiving device and the power transmitting device based on whether or not it is detected that the power receiving device and the compatible product are combined. A method characterized by:

15. A program for causing a computer to execute the method according to claim 14.

Images