Power-receiving apparatus, method performed by power-receiving apparatus, and program

Abstract

The power-receiving device (101) is used in combination with the corresponding product (201), and receives electric power wirelessly from the power-transmitting device (301). The power-receiving device detects that the power-receiving device and the corresponding product are combined, and determines a parameter used in a state detection process for detecting a state of the power-receiving device and the power-transmitting device, based on whether or not the combination of the power-receiving device and the corresponding product has been detected.

Description

Technical Field

[0001] This disclosure relates to a technology for an apparatus that can be used in combination with a corresponding product having a tag for near-field communication. Background Technology

[0002] As a standard for near-field communication, the Near Field Communication (NFC) standard is known. In the NFC standard, transmitting a carrier wave and modulating that carrier wave to send a message used to detect a device acting as a communication counterpart is called polling. Polling is sent by a device with a function called a reader / writer in the NFC standard. A device that functions as follows is called an NFC tag: receiving polls sent by the reader / writer and applying load modulation to the carrier wave sent by the reader / writer in response to the polling. The information exchanged in the NFC standard follows a data format called the NFC Data Exchange Format (NDEF). Multiple NDEF messages can be set in a single tag, and a reading device can read multiple NDEF messages set in an NFC tag from an NFC tag in a single NFC communication. How to process the read NDEF messages is left to the device.

[0003] In recent years, the technology used to authenticate items using NFC has become widespread. In particular, NFC-based authentication technologies have been developed to verify whether accessories and components attached to or used in conjunction with a device are compatible with that device.

[0004] Patent Document 1 discloses a technique related to the structure of a mobile phone including a radio frequency identification (RFID) tag. Specifically, the antenna of an RFID-based reader is disposed within the battery pack cover of the mobile phone body. Then, a circuit board of the reader, located inside the mobile phone body, reads an ID from an RFID tag attached to the battery pack to determine the authenticity of the battery pack (whether the battery pack is genuine).

[0005] Furthermore, Patent Document 2 describes a wireless power transmission system in which the transmitter and receiver are calibrated against each other, such that the characteristics of the transmitter and receiver are reflected in foreign object detection. It also describes the use of parameters such as scaling factors and offsets during calibration. Existing technical documents Patent documents

[0006] Patent Document 1: Japanese Patent Application Publication No. 2012-134796 Patent Document 2: Japanese Patent Application Publication No. 2017-511109 Summary of the Invention The problem the invention aims to solve

[0007] When corresponding products, such as accessories, are combined with (for example, attached to) a power receiving device that wirelessly receives power from a power transmitting device, there is a risk that efficient power transfer between the power transmitting and receiving devices cannot be achieved unless the impact of the corresponding products is taken into account.

[0008] This disclosure provides a technique that enables appropriate processing that takes into account the impact of the corresponding product during power transmission processing when power receiving equipment and corresponding products are used in combination. Solution for solving the problem

[0009] According to one aspect of this disclosure, a power receiving device includes: a detection component configured to detect that the power receiving device and a corresponding product are combined; and a determination component configured to determine parameters used in a state detection process for detecting the state of the power receiving device and the power transmitting device based on whether the combination of the power receiving device and the corresponding product has been detected. Advantages of the invention

[0010] According to this disclosure, when power receiving equipment and corresponding products are used in combination, appropriate processing can be performed that takes into account the impact of the corresponding products during power transmission processing. Attached Figure Description

[0011] Figure 1 This is a diagram illustrating a configuration example of the system according to the first embodiment. Figure 2 This is a diagram illustrating a system configuration example when the corresponding product is attached to a powered device. Figure 3 This is a diagram illustrating an example configuration of a system with the receiving device placed on the transmitting device. Figure 4 This is a diagram showing a configuration example for the corresponding product. Figure 5 This is a diagram showing an example of the configuration of the powered equipment. Figure 6 This is a diagram showing an example configuration of power transmission equipment. Figure 7 This is a flowchart illustrating an overview of the processing of the powered equipment. Figure 8 This is a flowchart illustrating the pre-configuration process for wireless power transmission. Figure 9 It is shown Figure 8 The flowchart continues. Figure 10 It is shown Figure 8 A flowchart detailing the NFC tag detection process. Figure 11 This is a diagram showing the NDEF information recorded in the NFC tag. Figure 12 This is a flowchart illustrating the details of the wireless power transmission process of the powered device. Figure 13 It is shown Figure 12 A flowchart illustrating an example of wireless power transmission pre-configuration processing for powered devices. Figure 14 This is a sequence diagram illustrating the processing of the entire system according to the first embodiment. Figure 15 It is shown Figure 14 The flowchart continues. Figure 16 This is a flowchart illustrating the wireless power transmission pre-configuration process of the powered device in the second embodiment. Figure 17 This is a flowchart illustrating the wireless power transmission pre-configuration process of the powered device in the third embodiment. Figure 18 This is a flowchart illustrating the wireless power transmission pre-configuration process of the powered device in the fourth embodiment. Figure 19 It is shown Figure 18 The flowchart continues. Figure 20 This is a flowchart illustrating the wireless power transmission pre-configuration process of the powered device in a variation of the fourth embodiment. Detailed Implementation

[0012] Embodiments of this disclosure will now be described with reference to the accompanying drawings. Not all of the multiple features in the embodiments of this disclosure are necessary, and multiple features can be combined in any way. Furthermore, the configurations shown in the following embodiments are merely examples, and this disclosure is not limited to the configurations shown. In the drawings, the same reference numerals are assigned to the same or similar configurations, and repeated descriptions are omitted.

[0013] <First Embodiment> In the first embodiment, an example of a powered device is given. The powered device is a device capable of wireless power transmission using electromagnetic induction methods for contactless charging based on WPC standards defined by the Wireless Power Consortium (WPC).

[0014] In the WPC standard, the guaranteed power output when a receiving device receives power from a transmitting device is defined by a value called Guaranteed Load Power (hereinafter referred to as "GP"). GP indicates the guaranteed power output to the load (such as a charging circuit included in the receiving device) even if, for example, the positional relationship between the receiving and transmitting devices changes and the power transfer efficiency between the receiving and transmitting coils decreases. For example, when GP is 15 watts, the transmitting device controls and sends power even if the positional relationship between the receiving and transmitting coils changes and the power transfer efficiency decreases, allowing 15 watts to be output to the load inside the receiving device.

[0015] System Configuration Figure 1 This is a diagram illustrating a configuration example of the system of this embodiment. The system includes a power receiving device 101 as an apparatus, a corresponding product 201 of 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] RX 101 is an electronic device that receives power from TX 301 and charges its built-in battery when placed on TX 301. TX 301 is an electronic device that wirelessly transmits power to RX 101 placed on it. RX 101 and TX 301 may have functions other than wireless charging. For example, RX 101 is a smartphone, and TX 301 is an accessory device for charging the smartphone's battery. However, not limited to this example, RX 101 and TX 301 may be a tablet device, a storage device such as a hard disk drive or memory device, or an information processing device such as a personal computer (PC). Furthermore, RX 101 and TX 301 may be a camera device such as a still camera or camcorder, an automobile, a robot, a medical device, or a printer.

[0017] Furthermore, the RX 101 is equipped with Near Field Communication (NFC) functionality, which enables electronic money payments, for example, when operating in card emulation mode. The RX 101 also features NFC functionality, which allows for NFC communication and reading of the NFC tag 202 when operating in reader / writer mode. The RX 101 incorporates an NFC antenna 102 for NFC communication, which is arranged adjacent to the surface of the RX 101's housing. When the NFC tag 202, located in the corresponding product 201, is near the surface of the RX 101 where the NFC antenna 102 is incorporated, the RX 101 can communicate with the NFC tag 202 by operating in reader / writer mode. Additionally, the RX 101 incorporates a sensor 103 for detecting the combination of the corresponding product 201 and the RX 101.

[0018] The combination of the corresponding product and the RX typically means that the corresponding product is attached to the RX 101 (assembled on the RX 101). However, it is not limited to this; any combination can be used even when there is no physical contact between the RX 101 and the corresponding product, as long as one or more functions or effects are produced, for example, by using the RX and the corresponding product simultaneously. "Effects" can include sensory effects on humans, such as visual and auditory effects.

[0019] As a typical example, RX 101 is a smartphone, and corresponding product 201 is a cover or housing for the smartphone. However, corresponding product 201 is not limited to a cover or housing, and can be, for example, an external battery, a gimbal, or an attached instrument.

[0020] In the following embodiments, the attachment of the corresponding product to the RX will be given as a typical example of the combination of the corresponding product and the RX.

[0021] Figure 4 This is a diagram showing a configuration example for product 201. (Reference) Figure 1 and Figure 4 The corresponding product 201 is equipped with an NFC tag 202. The NFC tag 202 is an example of a device that operates and enables near-field communication without a battery. More specific examples include NFC / RFID tags capable of NFC communication, and NFC communication devices that operate in card emulation mode. In the case where the corresponding product 201 is an NFC communication device operating in card emulation mode, the corresponding product 201 may incorporate a control unit for controlling communication and the entire corresponding product 201.

[0022] The corresponding product 201 has a detection unit 203. When the corresponding product 201 is attached to or combined with RX 101, RX 101 uses sensor 103 to detect the detection unit 203, thereby detecting that the corresponding product 201 is attached to RX 101. Sensor 103 and / or detection unit 203 are examples of detection components used to detect that RX 101 and the corresponding product 201 are combined.

[0023] With RX 101 placed on top of it, TX 301 wirelessly transmits power to RX 101 based on the WPC standard. TX 301 incorporates a power transmission coil 310 capable of wirelessly transmitting power to RX 101 based on the WPC standard with RX 101 placed on top of it, and the power transmission coil 310 is arranged adjacent to the surface of the housing of TX 301.

[0024] Below, as an example of the detected part 203 corresponding to product 201, a protrusion formed on the surface of the corresponding product will be described. Furthermore, as an example of the sensor 103 of RX 101, a mechanical switch arranged on the housing surface of RX 101 and pressed by the protrusion will be described. However, this is not a limitation; for example, the sensor 103 may be an optical sensor, an acoustic sensor, or a thermal sensor, etc.

[0025] Figure 2 This diagram illustrates a system configuration example with the corresponding product 201 attached to the RX 101. The corresponding product 201 has a housing shape that covers the RX 101 and is attached to the RX 101. At this time, the NFC tag 202 of the corresponding product 201 is arranged to overlap with the area of ​​the NFC antenna 102 of the RX 101. This enables the RX 101 to communicate with the NFC tag 202 by operating in reader / writer mode.

[0026] Furthermore, when the corresponding product 201 is attached to the RX 101, the detection unit 203 of the corresponding product 201 is positioned close to the sensor 103 of the RX 101. This allows the RX 101 to detect that the corresponding product 201 has been attached to the RX 101 by detecting the detection unit 203 using the sensor 103.

[0027] Figure 3 This is a diagram showing an example of system configuration where the RX 101 is placed on the TX 301 when the corresponding product 201 is attached to the RX 101. Figure 3 (A) is its plan view, and Figure 3 (B) is its schematic cross-sectional view. For example... Figure 3As shown in (A) and (B), the power supply coil 310 of TX 301 is arranged to overlap with the power receiving coil 104 of RX 101 in the plan view. This enables TX 301 to wirelessly transmit power to RX 101 based on the WPC standard.

[0028] Configuration of power receiving equipment, corresponding products and power transmitting equipment Figure 5 This diagram illustrates a configuration example of the RX 101. The RX 101 includes an NFC antenna 102, a sensor 103, a first communication unit 504, a control unit 505, and a memory 506. Furthermore, the RX 101 includes a receiving coil 104, a 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 implement NFC functionality. Specifically, they implement a card emulation mode as an alternative to 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, electronic money payments become possible by using the card emulation mode.

[0030] The first communication unit 504 and control unit 505 are examples of acquisition components used to detect NFC tags and obtain (read) tag information from the detected NFC tags.

[0031] The sensor 103 is, for example, a mechanical switch arranged on the housing surface of the RX 101, and detects the combination of the corresponding product 201 and the RX 101 by detecting the detected part 203, which is a protrusion formed on the surface of the corresponding product.

[0032] Control unit 505 controls the RX 101 as a whole. Control unit 505 performs control, for example, by executing a control program stored in memory 506. Furthermore, control unit 505 causes memory 506 to store information that should be stored during the execution of various processes. Control unit 505 includes one or more processors, such as a central processing unit (CPU) or a microprocessor unit (MPU). Control unit 505 may include a separate memory from memory 506 storing the control program, and this separate memory may store information that should be stored during the execution of various processes.

[0033] Note that the control unit 505 may be configured with hardware dedicated to a specific process, such as an application-specific integrated circuit (ASIC). Furthermore, the control unit 505 may include array circuitry, such as a field-programmable gate array (FPGA) compiled to perform a predetermined process.

[0034] Although control unit 505 is shown as a single component, this disclosure is not limited thereto. For example, a WPC control unit that controls processes related to receiving power from TX301 may be configured separately from control unit 505. Alternatively, an NFC control unit that controls processes related to NFC communication may be configured separately from control unit 505. Furthermore, the WPC control unit and the NFC control unit may each be configured separately from control unit 505. When control unit 505 is configured as multiple separate units, the individual control units are connected to each other via a communication interface, thereby enabling data communication. In this case, the communication interface may be any interface that enables data communication (specifically, such as I2C or GPIO).

[0035] Memory 506 stores various types of information, such as identification information and device configuration information, as well as control programs. Note that memory 506 may store information obtained from functional units different from control unit 505.

[0036] The second communication unit 508 communicates with the communication unit 605 of TX 301. Figure 6 This enables wireless communication based on the WPC standard. The second communication unit 508 controls the powered unit 507 to communicate with the TX 301. Specifically, the second communication unit 508 demodulates the electromagnetic waves input from the powered coil 104 to obtain information transmitted from the TX 301, and superimposes the information to be transmitted to the TX 301 onto the electromagnetic waves by load modulation. In other words, the communication performed by the second communication unit 508 is superimposed on the electromagnetic waves transmitted from the powered coil 310 of the TX 301.

[0037] The detection unit 509 detects that RX 101 is placed on TX 301 based on the WPC standard. For example, the detection unit 509 detects at least one of the voltage and current values ​​of the power receiving coil 104 when the power receiving unit 507 receives a WPC standard digital ping via the power receiving coil 104. For example, when the voltage value drops below a predetermined voltage threshold or when the current value exceeds a predetermined current threshold, the detection unit 509 can determine that RX 101 is placed on TX 301.

[0038] As described above, in this disclosure, the placement of the power receiving device on the power transmitting device means that the power receiving device is in a state where it can receive power from the power transmitting device (e.g., the power receiving device is placed at a location where it can receive power). Here, it is also conceivable that even if the receiving device is placed on the transmitting device, the receiving device does not necessarily need to be in a state capable of receiving power. For example, this could occur when a cover, casing, or other component that blocks or attenuates electromagnetic waves is attached to the receiving device, or when an unintended component that blocks or attenuates electromagnetic waves is present between the transmitting and receiving devices. The phrase "the receiving device is placed on the transmitting device," described later in the flowchart, is merely an example of the receiving device being in a state capable of receiving power from the transmitting device. Furthermore, the state in which the receiving device is able to receive power is not limited to the state in which the receiving device is placed on the transmitting device. For example, the state in which the receiving device is able to receive power can be a state in which the receiving device and the transmitting device are in contact or close to each other through mechanical engagement, or a state in which the receiving device is in contact with the transmitting device through magnetic force (e.g., via a corresponding product). In this disclosure, the state in which the power receiving device is placed on the power transmitting device will be regarded as a typical example of the state in which the RX 101 is able to receive power, and will be described below.

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

[0040] Battery 511 supplies the RX 101 with the power required for control of the various units of RX 101 by control unit 505, receiving power, and communication. In addition, battery 511 stores the power received via receiving coil 104.

[0041] Notification unit 513 uses any method such as visual, auditory, or tactile means to notify the user of, for example, the charging status of the RX 101 or related information. Figure 3 The information shown includes the status of the power transmission of the wireless power transmission system, including RX 101 and TX 301. The notification unit 513 includes, for example, a liquid crystal display, LEDs, a speaker, vibration generation circuitry, and / or other notification devices.

[0042] The operation unit 512 has a receiving function for receiving operations from the user on the RX 101. The operation unit 512 includes, for example, buttons, a keyboard, a voice input device, a motion detection device, and / or other input devices. Examples of voice input devices include a microphone. Examples of motion detection devices include an accelerometer sensor and a gyroscope sensor. Note that a device integrating the notification unit 513 and the operation unit 512, such as a touch panel, can be used.

[0043] Figure 6 This is a diagram illustrating a configuration example of TX 301 in this embodiment. 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 TX 301 as a whole by, for example, executing a control program stored in the memory 608. That is, the control unit 601 controls... Figure 6 The functional units shown are as follows. Furthermore, the control unit 601 causes the memory 608 to store information that should be stored during the execution of various processes. In addition, the control unit 601 performs control related to power transmission and control related to NFC functionality. Furthermore, the control unit 601 can perform control for applications other than wireless power transmission. Specific hardware examples of the control unit 601 are provided below. Figure 5 The hardware example of control unit 505 is the same, so its description will be omitted.

[0045] The control unit 601 may be configured with a single processor, or the main control unit controlling the whole and the sub-control units for controlling power supply processing and NFC communication may each be implemented by a separate processor.

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

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

[0048] The power transmission unit 603 inputs AC frequency power to the power transmission coil 310 based on instructions from the control unit 601, causing the power transmission coil 310 to output electromagnetic waves for transmitting power to RX 101. The power transmission unit 603 controls the intensity of the output electromagnetic waves by adjusting the voltage (power transmission voltage), current (power transmission current), or both input to the power transmission coil 310. Increasing the power transmission voltage or current increases the intensity of the electromagnetic waves, while decreasing the power transmission voltage or current decreases the intensity of the electromagnetic waves. Furthermore, the power transmission unit 603 controls the output of AC frequency power based on instructions from the control unit 601, thereby starting or stopping the power transmission from the power transmission coil 310.

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

[0050] The detection unit 604 detects whether an object is placed on TX 301 based on the WPC standard. Specifically, the detection unit 604 detects whether an object is placed on the interface surface of TX 301. For example, the detection unit 604 detects at least one of the voltage and current values ​​of the power supply coil 310 when the power supply unit 603 sends a WPC standard analog ping via the power supply coil 310. The detection unit 604 can detect changes in impedance. Then, when the voltage drops below a predetermined voltage value or when the current value exceeds a predetermined current value, the detection unit 604 can determine that an object is placed on TX 301.

[0051] The presence or absence of a predetermined response to a digital Ping subsequently sent by the communication unit 605 determines whether the object is RX 101 or another foreign object. That is, when TX 301 receives the predetermined response, the object is identified as RX 101; otherwise, the object is identified as an object different from the receiving device.

[0052] Communication unit 605 performs control communication with RX 101 based on the WPC standard as described above. Communication unit 605 modulates the electromagnetic waves output from power transmission coil 310 to transmit information to RX 101, thereby performing communication. Furthermore, communication unit 605 demodulates the electromagnetic waves output from power transmission coil 310 and modulated in RX 101 to obtain the information transmitted by RX 101. In other words, the communication performed by communication unit 605 is superimposed on the electromagnetic waves transmitted from power transmission coil 310.

[0053] In addition, the communication unit 605 performs NFC communication and detects the NFC tag of the power-transmitting device. Note that the communication unit 605 can be implemented by a single hardware module for both WPC-based control communication and NFC communication, or it can be implemented by separate hardware.

[0054] The notification unit 606 uses any method, such as visual, auditory, or tactile means, to notify the user of information. The notification unit 606 notifies the user of, for example, the charging status of the TX 301, or related information. Figure 3 The information shown pertains to the power transmission status of the wireless power transmission system, including TX 301 and RX101. A specific hardware example of notification unit 606 is provided. Figure 5 The hardware example of notification unit 513 is the same, so its description will be omitted.

[0055] Operation unit 607 has a receiving function to receive operations from the user on TX 301. Specific hardware examples of operation unit 607 are as follows: Figure 5 The hardware example of the operation unit 512 is the same, so its description will be omitted.

[0056] Memory 608 stores various types of information, such as identification information and capability information, as well as control programs. Capability information includes, for example, information indicating whether TX 301 has high-precision foreign object detection and processing capabilities. Note that memory 608 may store information obtained from functional units different from control unit 601.

[0057] Handling of power receiving equipment Figure 7 This is a flowchart illustrating an overview of the processing of the RX 101. This processing can be implemented, for example, by executing a program read from memory 506 via the control unit 505 of the RX 101. Note that at least some of the following steps can be implemented in hardware. In this case, the hardware can be implemented, for example, by automatically generating dedicated circuitry using gate array circuitry (such as an FPGA) from the program used to implement the various processing steps using a predetermined compiler.

[0058] In S701, RX 101 initiates the periodic NFC tag detection / authentication (detection and authentication) process. The periodic NFC tag detection / authentication process begins at any of the following three time points. (a) Timing of a user performing a pre-defined operation via the operation unit 512 of RX 101 (b) Timing of power-on of RX 101 (c) Sensor 103 detects the timing of the corresponding product 201 being attached to RX 101. The “pre-defined operation” in (a) is an operation or other operation used to perform the NFC tag detection / authentication process.

[0059] In S702, RX 101 performs the NFC tag detection / authentication process. When RX 101 detects the NFC tag 202 corresponding to product 201 and the NDEF information (tag information) of the NFC tag 202 includes authentication information, RX 101 performs authentication processing according to the conditions described later.

[0060] In S703, RX 101 performs wireless power transfer processing based on the WPC standard and receives power from TX 301. Here, RX 101 performs wireless power transfer pre-configuration processing and configures the wireless power transfer settings according to the certification status of the corresponding product 201. Wireless power transfer pre-configuration processing is abbreviated as pre-configuration processing in the following text.

[0061] In this embodiment, as an example of pre-configured processing, a process is shown for determining parameters for status detection related to wireless power transmission based on the authentication status of the corresponding product 201 and information included in the NFC tag of the corresponding product 201. Details will be described later.

[0062] Figure 8 and Figure 9 It is shown Figure 7 A flowchart detailing the processing of the NFC tag detection / authentication procedure (S702) in the process. Figure 10 It is shown Figure 8 The flowchart details the NFC tag detection process (mainly S801 to S803).

[0063] exist Figure 8 First, in S801, RX 101 performs NFC tag detection processing. For example... Figure 10 As shown, in S901, after processing begins, RX 101 sets the type of the NFC tag to be detected. NFC tags exist in multiple types, such as Type A / Type B / Type F, and the type of NFC tags that have not yet been detected is set. In S902, RX 101 performs NFC tag detection. This can be performed by a reader / writer function compliant with the NFC standard. Specifically, RX 101 transmits a carrier wave and modulates that carrier wave to send a message for detecting NFC tags of the set type. When the NFC tag receives the message from RX 101, the NFC tag applies load modulation to the transmitted carrier wave in response to the message. As a result, RX 101 detects NFC tag 202.

[0064] In S903, RX 101 determines whether the detection of NFC tag 202 has been successful. When RX 101 determines that the detection of NFC tag 202 has been successful (yes in S903), in S904, RX 101 retains the NDEF information read from NFC tag 202. On the other hand, when RX 101 determines that the NFC tag detection has failed (no in S903), the process ends. When retaining the NDEF information in S904, RX 101 manages the information for each NFC tag that has undergone detection.

[0065] In S905, RX 101 determines whether detection processing has been performed for all types (Type A / Type B / Type F) of NFC tags. When RX 101 determines that detection of all types has been performed (Yes in S905), the processing ends. On the other hand, when RX 101 determines that detection of all types has not been performed (No in S905), RX 101 returns to S901 and performs detection processing for the next type of NFC tag.

[0066] The above constitutes Figure 8 The NFC tag detection processing performed in the process (mainly S801 to S803) allows for proper understanding even when multiple NFC tags are present near the RX 101, thanks to the detection processing for all NFC tag types. For example, when two NFC tags are present and they are of different types, NDEF information can be read from all tags.

[0067] Return to Figure 8 The flowchart describes the process. In S802, RX 101 determines whether an NFC tag has been detected in the NFC tag detection process in S801. If no NFC tag has been detected (No in S802), the process ends. If RX 101 has detected an NFC tag (Yes in S802), then in S803, RX 101 determines whether the NFC tag reading has been successful. If the NFC tag reading has not been successful (No in S803), the process ends. If the NFC tag reading has been successful (Yes in S803), then RX 101 retains the NDEF information of all successfully read NFC tags in memory.

[0068] In S804, RX 101 examines all NDEF information detected from an NFC tag that has not yet undergone processing. Examining NDEF information implies analysis. Figure 11The NDEF information 1001 to 1003 shown in (A) is as follows. Assume that the NFC tag 202 corresponding to product 201 is an NFC tag implemented by the provider of product 201, and as an example, the NFC tag 202 has three NDEF information.

[0069] NDEF information 1001 is information related to the product information of the corresponding product 201. Contemplated examples include information related to the device type (e.g., information indicating that the type of the corresponding product 201 is a cover), manufacturer information, product model, and serial number. The product information of the corresponding product 201 is an example of second information.

[0070] NDEF information 1002 is information related to the authentication of the corresponding product 201, and for example, an authentication key is envisioned. The information related to the authentication of the corresponding product 201 is an example of the first information.

[0071] NDEF information 1003 is information authorizing power delivery to the NFC tag 202 of the corresponding product 201 (information related to the authorization of power delivery), and envisions the version of wireless power transmission, information on whether power delivery is authorized, and the permissible power value (e.g., 8W). In this embodiment, "power delivery" as mentioned here primarily refers to power delivery for wireless charging of the RX 101. "Authorized power delivery" means, for example, that power delivery is authorized as long as the power does not damage the NFC tag 202.

[0072] NDEF information is not limited to Figure 11 (A) and various types of information can be set according to the intended use of the supplier of the corresponding product 201. Furthermore, in Figure 11 In (A), three NDEF information entries are stored in NFC tag 202, but more or fewer NDEF information entries can be stored. This also applies to the descriptions that follow. Figure 11 (B), (C) and (D).

[0073] refer to Figure 9 In S805, RX 101 determines the certification information of the corresponding product 201. Figure 11 The NDEF information 1002 in (A) is included in the NDEF information confirmed in S804. If the certification information for the corresponding product 201 does not exist (No in S805), then RX 101 proceeds to S812 without certification processing. If the certification information for the corresponding product 201 exists (Yes in S805), then in S806, RX 101 determines whether sensor 103 has detected that the corresponding product 201 is attached to RX 101.

[0074] If attachment has not yet been detected (No in S806), then in S807, RX 101 transitions to the uncertified state for the corresponding product, and retains the fact that the corresponding product 201 is in the uncertified state in memory. Afterwards, processing proceeds to S812. The uncertified state for the corresponding product means that the certification of the corresponding product 201 has not yet been successful.

[0075] Furthermore, if attachment has not been detected (No in S806), RX 101 cancels authentication even if the corresponding product 201 is already in an authenticated state. That is, the state of the corresponding product 201 changes to the corresponding product unauthenticated state (S807). As will be described later, the fact that the corresponding product 201 is in an authenticated state can be determined by performing the processes from S809 to S811. That is, if the corresponding product 201 was attached to RX 101 in the previous case, the authentication process for the corresponding product 201 was performed, and the authentication was successful, the fact that the corresponding product 201 is in an authenticated state is retained in the memory, so the device can determine that the corresponding product 201 is in an authenticated state.

[0076] If the corresponding product 201 has been detected to be attached to RX 101 (Yes in S806), then in S808, RX 101 determines whether the corresponding product 201 is already in the certified state. The certified state means that the certification of the corresponding product 201 has been successful. If the corresponding product 201 is in the certified state (Yes in S808), then RX 101 proceeds to S812 without performing certification processing.

[0077] If the corresponding product 201 is not in the certified state (No in S808), then in S809, RX 101 performs the authentication process for the corresponding product 201. RX 101 performs authentication by processing at least the authentication information (NDEF information 1002 (authentication key)) in the NDEF information of the NFC tag of the corresponding product 201, and retains the result of the authentication process. In S810, RX 101 determines whether the authentication process for the corresponding product has been successful. If the authentication process for the corresponding product has been successful (Yes in S810), then in S811, RX 101 transitions to the certified state for the corresponding product, retains the fact that the corresponding product 201 is in the certified state in the memory, and proceeds to S812. If the authentication process for the corresponding product has not yet been successful (No in S810), then RX 101 proceeds to S812 without transitioning to the certified state.

[0078] As described above, once the corresponding product 201 has successfully undergone certification, for example, if the corresponding product 201 is subsequently removed from RX 101, the status of the corresponding product 201 can be returned to the uncertified state. Therefore, when the corresponding product 201 is subsequently reattached to RX 101, the appropriate certification process can be performed again.

[0079] In S812, RX 101 determines whether the NFC tag being processed has NDEF information other than authentication information. If no NDEF information other than authentication information exists (No in S812), processing proceeds to S814. If NDEF information other than authentication information exists (Yes in S812), then in S813, RX 101 performs processing for the first NDEF information other than authentication information. Figure 11 Taking the NDEF information in (A) as an example, this corresponds to processing NDEF information 1001, and it is assumed that RX 101 reads the device type information, manufacturer information, and serial number of the corresponding product 201. After that, the processing of RX 101 proceeds to S814.

[0080] The control unit 505 and the program for performing the authentication process are examples of authentication components used for authenticating corresponding products.

[0081] Note that in the NFC tag, from Figure 11 The NDEF information is read sequentially from the left side of (A). That is, NDEF information 1001 is read first. Alternatively, it is conceivable that when the NDEF information is stored in an NFC tag, it can be stored in association with an ID or number that identifies the NDEF information. In this case, RX 101 can read the NDEF information in the order of ID or number.

[0082] In S814, RX 101 determines whether any NFC tag other than the processed NFC tag has been detected in S804. If any other NFC tag other than the processed NFC tag has been detected (Yes in S814), RX 101 returns to S804 and performs subsequent processing again for the NFC tag other than the processed NFC tag. If RX 101 has not detected any other NFC tag other than the processed NFC tag (No in S814), the processing ends.

[0083] Figure 12 It is shown Figure 7 A flowchart detailing the wireless power transmission processing of the RX 101 based on the WPC standard in the S703. In S1101, RX 101 performs the processing defined in the WPC standard as the selection and ping phases, and waits for the device itself to be placed on TX 301. RX 101 detects that it is placed on TX 301 by, for example, detecting a digital ping from TX 301. When RX 101 receives a digital ping from TX 301, RX 101 sends a signal strength (SIG) data packet to TX 301.

[0084] In S1102, when RX 101 detects that the device itself has been placed on TX 301, RX 101 performs pre-configuration processing.

[0085] Figure 13 This is a flowchart illustrating an example of a pre-configuration process (S1102) performed by RX 101. In this process, parameters for state detection related to wireless power transmission based on the authentication status of the corresponding product 201 and information included in the NFC tag of the corresponding product 201 are determined. State detection means detecting the state of RX 101 and TX 301 when RX 101 is in a state where it can receive power from TX 301. State detection includes, for example, foreign object detection or coupling state detection. Hereinafter, the process related to this state detection is referred to as "state detection processing" and includes foreign object detection processing or coupling state detection processing. Furthermore, hereafter, the parameters used for state detection (indicated in the figure as "parameters related to state detection") are abbreviated as "state detection parameters".

[0086] In the state detection process, high-precision detection cannot be performed when the parameters used in the calculations during the state detection process are the same regardless of whether the corresponding product 201 is attached to RX 101. At least when the corresponding product 201 is attached to RX 101, high-precision state detection suitable for the state in which the corresponding product 201 is attached becomes possible by setting the state detection parameters.

[0087] Foreign object detection processing, for example, involves TX 301 detecting the presence of a foreign object between RX 101 and TX 301 while RX 101 is placed on TX 301. In this case, the state detection parameter is a constant related to RX 101 used in the foreign object detection processing. The constant related to RX 101 is, for example, a value set based on the structure (e.g., the thickness and shape of the housing), material, or state of RX 101, or a threshold used in calculations for performing a predetermined foreign object detection method. When a foreign object exists between RX 101 and TX 301 and TX 301 wirelessly transmits power to RX 101, an overcurrent may be generated in the foreign object, leading to heat generation and posing a safety hazard. Therefore, TX 301 performs foreign object detection processing and takes countermeasures such as stopping power supply or reducing power supply when a foreign object is detected.

[0088] For example, foreign object detection processing can be performed using the following method. For example, in the absence of foreign objects, the efficiency of the power transmission when TX 301 sends power to RX 101 is pre-calculated. The efficiency of the power transmission when TX 301 sends power to RX 101 is the ratio of the power received by RX 101 to the power sent by TX 301. Then, when the efficiency of the power transmission during the power transmission period decreases below the efficiency of the power transmission in the absence of foreign objects, it is determined that "foreign objects are present". The pre-configuration processing in this embodiment is, for example, a process for determining (setting) a constant associated with RX 101, which is used by TX 301 to calculate the aforementioned power transmission efficiency. Alternatively, when a corresponding product is attached to RX 101 and the product information (NDEF information 1001) of the corresponding product is read, the pre-configuration processing is a process for determining a constant associated with the corresponding product 201, which is used to calculate the power transmission efficiency. Alternatively, the constant can be either a constant associated with RX101 or a constant associated with the corresponding product 201.

[0089] Alternatively, foreign object detection processing can be performed using other methods. For example, in the absence of foreign objects, the power loss when TX 301 sends power to RX 101 is pre-calculated. The power loss when TX 301 sends power to RX 101 is the difference between the power sent by TX 301 and the power received by RX 101. Then, if the power loss of TX 301 during power transmission exceeds the power loss in the absence of foreign objects described above, it is determined that "a foreign object is present". The pre-configuration processing in this embodiment is, for example, a process for determining a constant associated with RX 101, which is used by TX 301 to calculate the power loss in the absence of foreign objects described above.

[0090] The coupling state detection process is, for example, a process by which TX 301 detects the electromagnetic coupling state between the receiving coil 104 of RX 101 and the supply coil 310 of TX 301. 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 RX 101 used in a process in which TX 301 calculates the coupling coefficient or coupling factor between the receiving coil 104 of RX 101 and the supply coil 310 of TX 301. By calculating the coupling coefficient or coupling factor, TX 301 can estimate, for example, whether there is a positional offset between the receiving coil 104 of RX 101 and the supply coil 310 of TX 301 while power is being supplied to RX 101.

[0091] In this embodiment, the "state detection parameter" corresponds to, for example, a "constant related to RX 101" and / or a "constant related to the corresponding product 201". Alternatively, the "state detection parameter" may not be limited to a "constant" but may be a predetermined calculation formula, etc.

[0092] The control unit 505 and the program for performing the processing of setting (determining) status detection parameters are primarily examples of a determining component that determines the status detection parameters based on one or more predetermined conditions, including whether a combination of the powered device and the corresponding product has been detected. In this embodiment, multiple conditions exist as predetermined conditions. These will be explained below. Figure 13 As described in the flowchart, multiple conditions are used for judgments in some decision-making processes (e.g., S1203 to S1205) after S1202. This also applies to the second embodiment ( Figure 16 ), Third embodiment ( Figure 17 ) and the fourth embodiment ( Figures 18 to 20 The flowchart in )

[0093] refer to Figure 13When processing begins, in S1201, RX 101 sets a power profile (power profile information, power profile compatibility information) for wireless power transmission based on the WPC standard supported by the device itself. The power profile is one of the standards in the WPC standard and includes, for example, a baseline power profile (BPP) and an extended power profile (EPP). The maximum power supply is 5W for BPP and 15W for EPP. Additionally, MPP can also be used as a power profile. In this embodiment, the power profile is set based on information pre-recorded in the memory 506 of RX 101. In this embodiment, as an example, RX 101 also supports MPP, the power profile is set to MPP, and RX 101 retains this setting in memory 506. Note that MPP is an abbreviation for Magnetically Powered Profile.

[0094] In S1202, RX 101 determines whether the corresponding product has been detected attached to RX 101. Note that this determination process is already in S806 of S702. Figure 9 The process is performed in S1202, so the result of the judgment can be used in S1202. If the attachment of the corresponding product has not yet been detected (No in S1202), then in S1207, RX 101 sets the power-received device-based parameters pre-recorded in memory 506 as status detection parameters. Then, RX 101 retains the setting in memory 506 and ends the process.

[0095] Here, the condition detection parameters of the powered device are based on the condition detection parameters of the powered device obtained in advance, and one of the following is envisioned, for example. - Parameters primarily measured by the RX 101 manufacturer during the product manufacturing phase (before the product leaves the factory; the same applies below) in the condition that the corresponding product 201 is not attached to the RX 101. - This parameter was primarily calculated by the RX 101 manufacturer during the product manufacturing phase, assuming that the corresponding product 201 was not attached to the RX 101. - Parameters primarily set by the purchaser or user of the RX 101, for example, during the initial setup of the product, assuming that the corresponding product 201 is not attached to the RX 101.

[0096] Below, "Status detection parameters based on powered equipment" has the same meaning as above.

[0097] If RX 101 has detected the attachment of the corresponding product (as in S1202), then RX 101 proceeds to S1203 and determines whether the corresponding product 201 is in the corresponding product authentication state. This determination is based on the authentication status-related information stored in memory 506 in S811 when the NFC tag detection / authentication process is executed in S702.

[0098] If the corresponding product 201 is not in the corresponding product certified state (No in S1203), then RX 101 performs the above process in S1207 and ends the process. If the corresponding product 201 is in the corresponding product certified state (Yes in S1203), then in S1204, RX 101 determines whether the product information of the corresponding product 201 has been read from the NDEF information of the NFC tag of the corresponding product 201. Here, product information refers to information included in... Figure 11 The information in NDEF information 1001 of (A) includes device type, manufacturer, product model, serial number, etc. In S1204, based on the NDEF information of the NFC tag of the corresponding product 201 stored in memory 506 in S801 when the NFC tag detection / authentication process is performed in S702, it is determined whether the product information has been read.

[0099] If the product information for the corresponding product 201 has not yet been read (No in S1204), then RX 101 performs the above process in S1207 and ends the process. If the product information for the corresponding product 201 has already been read (Yes in S1204), then in S1205, RX 101 determines whether the status detection parameter based on the product information of the corresponding product exists in the memory 506. This status detection parameter based on the product information of the corresponding product is a parameter pre-acquired based on the product information of the corresponding product.

[0100] The status detection parameters based on the product information of the corresponding product are status detection parameters that are obtained in advance based on the product information of the corresponding product, and one of the following is envisioned, for example. -Parameters primarily measured by the manufacturer of the corresponding product 201 during the product manufacturing stage (before the product leaves the factory; the same applies below) with the corresponding product 201 attached to the RX 101. -Parameters primarily calculated by the manufacturer of product 201 during the product manufacturing phase, assuming product 201 is attached to RX 101. - Parameters primarily set by the purchasers or users of the corresponding products 201 and RX 101, for example, during the initial setup of the products, assuming that the corresponding product 201 is attached to the RX 101.

[0101] Below, "Status 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), then RX 101 performs the above-described process in S1207 and ends the process. If the status detection parameters based on the product information of the corresponding product 201 exist in the memory 506 (Yes in S1205), then in S1206, RX 101 performs the following process. That is, RX 101 sets the status detection parameters based on the product information of the corresponding product 201 recorded in the memory 506, retains the setting in the memory 506, and ends the process.

[0103] Return to Figure 12 The description is as follows. In S1103, RX 101 performs processing defined as the Identification and Configuration (I&C) phase of the WPC standard. In the I&C phase, RX 101 sends an identification data packet (ID packet) to TX 301. In addition to the manufacturer code and basic device ID, which serve as identification information for each individual RX 101, the ID packet also stores information elements that identify the version of the supported WPC standard.

[0104] RX 101 can send its identification information to TX 301 via an extended identification data packet (XID packet). Additionally, RX 101 sends a configuration data packet to TX 301. The configuration data packet includes capability information (device configuration information) of RX 101 as indicated below. - Ability to identify the version of the WPC standard supported by the RX 101 - Maximum power value or reference power, which is the maximum power value that the RX 101 can supply to the load. -Information indicating whether the RX 101 has the negotiation function of the WPC standard. - Parameters used in frequency shift keying, which is a modulation scheme used for communication when TX301 sends information to RX101.

[0105] However, this information is merely an example, and the identification and capability information of the RX 101 can be replaced by other information, or further include other information. For example, the identification information can be any other identification information capable of identifying an individual RX 101, such as a wireless power ID. Furthermore, the RX 101 can transmit identification and capability information through methods other than the communication in the I&C phase of the WPC standard.

[0106] Here, RX 101 includes information about the power profile of the WPC standard supported by the device itself, set in S1102, in any one of the ID packet, XID packet, and configuration data packet, and notifies TX 301 of this. Upon receiving this notification, TX 301 compares the information about the power profile of the WPC standard supported by RX 101 with the power profile of the WPC standard supported by TX 301, and determines the power profile to be used.

[0107] For example, TX 301 pre-sets the priority order of the power profiles to be used, and selects and determines the power profile with the highest priority from the power profiles supported by both TX 301 and RX 101. For example, suppose the priority order of the power profiles to be used is set to 1: MPP, 2: EPP, 3: BPP. Then, if the power profiles supported by both TX 301 and RX 101 are MPP and BPP, then MPP is selected and determined as the power profile to be used.

[0108] As another example, there is a method in which RX 101 includes information about the power profiles it supports, along with the priority order of those power profiles, in any one of the ID packet, XID packet, and configuration packet, and notifies TX 301 of this. In this case, TX 301 selects and determines the power profile with the highest priority order from the power profiles of RX 101 notified by RX 101, from the power profiles supported by both TX 301 and RX 101.

[0109] Furthermore, RX 101 includes the status detection parameters set in S1102 in any of the ID packet, XID packet, and configuration packet, and notifies TX 301 of this. Alternatively, RX 101 can notify TX 301 of the status detection parameters by including the status detection parameters set in S1102 in a predetermined packet during the negotiation phase of the WPC standard, as described later. Upon receiving this notification, TX 301 performs status detection processing based on the status detection parameters notified from RX 101 in the WPC standard-based wireless power transmission processing following the negotiation phase. That is, TX 301 can perform one or more status detection processes in any one or more of the negotiation phase, calibration phase, and power transmission phase.

[0110] In S1104, when RX 101 sends identification and capability information, RX 101 initiates communication in the negotiation phase defined by the WPC standard. During the negotiation phase, RX 101 sends a requested power value to TX 301 and determines the value of GP with TX 301. GP is an example of power information used to indicate the power requested by the energized device from the energizing device.

[0111] When RX 101 determines the GP, in S1105, RX 101 initiates communication during the calibration phase defined by the WPC standard. During the calibration phase, RX 101 sends information to TX 301 related to a predetermined power supply value, allowing TX to derive the relationship between the supplied and received power under conditions free of foreign objects. This information includes the power supply value under light load conditions and the power supply value under maximum load conditions. Note that during the calibration phase, RX 101 may notify TX 301 of status detection parameters.

[0112] When RX 101 sends information related to the received power value, in S1106, RX 101 begins receiving power through communication in the power transfer phase defined by the WPC standard. Subsequently, when a fully charged state is reached, RX 101 sends the WPC standard End Power Transfer (EPT). This stops power delivery from TX 301, and the series of processes for contactless charging concludes.

[0113] Processing of the entire system Figure 14 and Figure 15 This is a sequence diagram illustrating the processing of the entire system. In this example flowchart, as the initial state, RX 101 is in a state where it is not placed on TX 301 (it cannot receive power), and in F1311, RX 101 is placed on TX 301.

[0114] In F1301, RX 101 initiates a periodic NFC tag detection / authentication process. Although not shown, RX 101 performs the NFC tag detection / authentication process periodically at predetermined time intervals. In this example, after initiating the periodic NFC tag detection / authentication process, it is assumed that the corresponding product 201 is attached to RX 101 (F1302).

[0115] In F1303, RX 101 performs the NFC tag detection / authentication process and reads and authenticates the NFC tag of the corresponding product 201.

[0116] In F1304, RX 101 obtains NDEF information (authentication information (e.g., authentication key)) related to authentication from the NFC tag of the corresponding product 201.

[0117] From F1305 to F1309, the RX 101 performs reservation processing based on the authentication information obtained in F1304. That is, as... Figure 8 As shown in the flowchart, RX 101 performs authentication processing according to conditions, changes the state of the corresponding product 201, and retains the state (authenticated or unauthenticated) in memory.

[0118] In F1310, RX 101 performs processing for NDEF information other than NDEF information related to the authentication of the corresponding product 201, and also performs processing for any other NFC tags detected.

[0119] When RX 101 is placed on TX 301 in F1311, in F1312, TX 301 and RX 101 perform communication during the Ping phase of the WPC standard, and in F1313, TX 301 detects that RX 101 is placed on it. Furthermore, in F1314, RX 101 detects that the device itself is placed on TX 301. Subsequently, in F1315, RX 101 performs... Figure 13 The flowchart illustrates the pre-configuration process. Specifically, the RX 101 sets the power profile and status detection parameters according to the WPC standard supported by the RX 101.

[0120] RX 101 sends identification and capability information (not shown) to TX 301 via communication during the I&C phase of the WPC standard. During the I&C phase, in F1316, RX 101 informs TX 301 of the power profile information of the WPC standard supported by RX 101. In F1317, TX 301 determines the power profile to be used based on the power profile information of the WPC standard supported by RX 101 and the power profile information of the WPC standard supported by TX 301. In F1318, RX 101 requests information from TX 301 regarding the power profile to be used. This request can be achieved by sending a general request packet to TX 301. In F1319, TX 301 responds to the request from RX 101 for information regarding the power profile to be used and informs RX 101 of the power profile to be used. Notification from TX 301 to RX 101 of the power profile to be used can be achieved by sending a transmitter identification packet (TX ID packet) to RX 101.

[0121] In F1320, RX 101 notifies TX 301 of the status detection parameters. Upon receiving this notification, TX 301 performs status detection processing based on the status detection parameters notified from RX 101 in subsequent wireless power transmission processing based on the WPC standard.

[0122] In F1321 to F1323, TX 301 and RX 101 communicate during the WPC standard negotiation phase and proceed to the power transfer phase to begin power supply and receiving processes. When the battery reaches a fully charged state, in F1324, RX 101 sends a End Power Transfer (EPT) packet to TX 301 to request the cessation of power transfer. Upon receiving the EPT packet, TX 301 stops power supply.

[0123] According to the above embodiments, once RX 101 has successfully authenticated the corresponding product 201, re-authentication processing can be avoided in the next periodic NFC tag detection process. Therefore, increased power consumption of RX 101 and reduced processing performance of other applications can be avoided. Furthermore, once the corresponding product 201 has successfully undergone authentication, if the corresponding product 201 is subsequently removed from RX 101, the state of the corresponding product 201 can return to the unauthenticated state. Therefore, when the corresponding product 201 is subsequently reattached to RX 101, appropriate authentication processing can be performed again.

[0124] Furthermore, RX 101 can set appropriate status detection parameters based on the certification status of the corresponding product 201. For example, when the corresponding product 201 is attached to RX 101 and certification has been successful, RX 101 can set status detection parameters that take into account the influence of the corresponding product 201 and notify TX 301. This enables high-precision status detection processing suitable for the attached state of the corresponding product 201, for example, when the corresponding product 201 is attached to RX 101. As a result, efficient power transmission processing becomes possible.

[0125] As described above, RX 101 can perform appropriate processing that takes into account the impact of the corresponding product during power transmission processing.

[0126] <Second Embodiment> The second embodiment will now be described in detail with reference to the accompanying drawings. Furthermore, descriptions of configurations identical or similar to those in the first embodiment will be omitted. The second embodiment illustrates an example where the NDEF information of the NFC tag corresponding to product 201 includes the status detection parameters themselves.

[0127] The system configuration example in this embodiment, as well as the configuration of the powered device (RX 101), corresponding product 201, and powered device (TX 301), are the same as in the first embodiment. Therefore, their description will be omitted.

[0128] Handling of power receiving equipment As in the first embodiment, Figure 7 An overview of the processing of RX 101 is shown. Furthermore, as in the first embodiment, it is also... Figure 8 and Figure 9 The details of the NFC tag detection / authentication process (S702) are shown. Furthermore, as in the first embodiment, [the following is also included]. Figure 10 The middle shows Figure 8 Details of NFC tag detection processing (mainly S801 to S803) in the process.

[0129] In this embodiment, Figure 8 In S804, RX 101 examines all NDEF information detected from an NFC tag that has not yet undergone processing. Examining NDEF information implies analysis. Figure 11 The NDEF information 1011 to 1014 is shown in (B). Assume that the NFC tag 202 corresponding to product 201 is an NFC tag implemented by the provider of product 201, and as an example, the NFC tag 202 has four NDEF information.

[0130] NDEF information 1011, NDEF information 1012, and NDEF information 1013 are respectively related to Figure 11The NDEF information 1001, NDEF information 1002, and NDEF information 1003 in (A) are identical. NDEF information 1014 is a state detection parameter suitable for the state in which the corresponding product 201 is attached to RX 101. For example, the state detection parameter is a parameter related to foreign object detection processing or a parameter related to coupling state detection processing in TX 301. The state detection parameter suitable for the state in which the corresponding product is attached to RX 101 is a parameter that is pre-measured in the state in which the corresponding product is attached to RX 101. Alternatively, the state detection parameter suitable for the state in which the corresponding product is attached to RX 101 is a parameter that is pre-calculated under the assumption that the corresponding product 201 is attached to RX 101. That is, the state detection parameter is obtained by the manufacturer of the corresponding product 201 and / or RX 101 during the manufacturing stage of the product. NDEF information is not limited to... Figure 11 The NDEF information shown in (B) can be configured in various ways according to the intended use of the supplier of the corresponding product 201.

[0131] The status detection parameter in NDEF information 1014 is an example of the second information and an example of information specifying the status detection parameter. The information specifying the status detection parameter can be the status detection parameter itself, such as NDEF information 1014, or it can be a URL or other address information indicating the existence of information representing the status detection parameter.

[0132] As in the first embodiment, Figure 12 It shows Figure 7 Details of the wireless power transmission processing of the RX 101 based on the WPC standard in the S703. Figure 12 In this embodiment, the content of each processing step in processing steps S1101 and S1103 to S1106 is the same as that in the first embodiment.

[0133] Figure 16 This illustrates that in this embodiment... Figure 12 The flowchart illustrates an example of the pre-configuration process performed in S1102. In this process, status detection parameters related to wireless power transmission based on the WPC standard are determined based on the authentication status of the corresponding product 201 and the information included in the NFC tag of the corresponding product 201.

[0134] The processing from S1401 to S1403 is the same as in the first embodiment. Figure 13 The processing from S1201 to S1203 is the same, so its description will be omitted.

[0135] In S1404, RX 101 determines whether the status detection parameters have been read from the NDEF information (NDEF information 1014) of the NFC tag of the corresponding product 201. These status detection parameters are appropriate for the state in which the corresponding product 201 is attached to RX 101. The appropriate status detection parameters for the state in which the corresponding product 201 is attached to RX 101 are as described above. In S1404, when the NFC tag detection / authentication process is executed in S702, the determination is based on the NDEF information of the NFC tag of the corresponding product 201 stored in memory 506 in S801.

[0136] If the status detection parameters have not yet been read (No in S1404), then in S1406, RX 101 sets the power-received device-based status detection parameters pre-recorded in memory 506 as the status detection parameters. Then, RX 101 retains the setting in memory 506 and ends the process.

[0137] If the status detection parameters have been read (Yes in S1404), then in S1405, RX 101 sets the status detection parameters recorded in memory 506 to the state of the corresponding product 201 attached to RX 101. Then, RX 101 retains the settings in memory 506 and ends the process.

[0138] As in the first embodiment, in Figure 14 and Figure 15 The diagram illustrates the processing of the entire system in this embodiment.

[0139] As described above, according to this embodiment, the same effect as that described in the first embodiment can be obtained. Furthermore, in this embodiment, since the state detection parameters are pre-stored as NEDF information in the NFC tag 202, the RX101 can read these state detection parameters, and in the pre-configuration process, the read state detection parameters themselves can be set.

[0140] As described above, RX 101 can perform appropriate processing that takes into account the impact of the corresponding product during power transmission processing.

[0141] <Third Embodiment> The third embodiment will now be described in detail with reference to the accompanying drawings. Furthermore, descriptions of configurations identical or similar to those of the first and second embodiments will be omitted.

[0142] The third embodiment illustrates an example where the NDEF information of the NFC tag corresponding to product 201 includes a corrected value for the status detection parameters. RX 101 performs calculations based on the corrected value of the status detection parameters and status detection parameters pre-recorded in the memory 506 of RX 101 suitable for a state where the corresponding product is not attached to RX 101. As a result, RX 101 calculates and sets status detection parameters suitable for a state where the corresponding product 201 is attached to RX 101.

[0143] The system configuration example in this embodiment, as well as the configuration of the powered device (RX 101), corresponding product 201, and powered device (TX 301), are the same as in the first embodiment. Therefore, their description will be omitted.

[0144] Handling of power receiving equipment As in the first embodiment, Figure 7 An overview of the processing of RX 101 is shown. Furthermore, as in the first embodiment, it is also... Figure 8 The details of the NFC tag detection / authentication process (S702) are shown. Furthermore, as in the first embodiment, [the following is also included]. Figure 10 The middle shows Figure 8 Details of NFC tag detection processing (mainly S801 to S803) in the process.

[0145] In this embodiment, Figure 8 In S804, RX 101 examines all NDEF information detected from an NFC tag that has not yet undergone processing. Examining NDEF information implies analysis. Figure 11 The NDEF information 1021 to 1024 is shown in (C). Assume that the NFC tag 202 corresponding to product 201 is an NFC tag implemented by the provider of product 201, and as an example, the NFC tag 202 has four NDEF information.

[0146] NDEF information 1021, NDEF information 1022, and NDEF information 1023 are respectively related to Figure 11The NDEF information 1001, NDEF information 1002, and NDEF information 1003 in (A) are the same. NDEF information 1024 is a correction value for the state detection parameter when the corresponding product 201 is attached to RX 101. The correction value for the state detection parameter is a correction value used to correct the influence of the corresponding product 201 in state detection. For example, the correction value for the state detection parameter is a correction value for a parameter related to foreign object detection processing in TX 301 or a correction value for a coupling state detection parameter. RX 101 calculates based on the correction value of the state detection parameter and state detection parameters suitable for the state when the corresponding product is not attached to RX 101, which are pre-recorded in the memory 506 of RX 101. In other words, the state detection parameters suitable for the state when the corresponding product is not attached to RX 101 are the aforementioned "state detection parameters based on the powered device". As a result, RX 101 calculates state detection parameters suitable for the state when the corresponding product 201 is attached to RX 101. NDEF information is not limited to... Figure 11 (C), and various types of information can be set according to the intended use of the supplier of the corresponding product 201.

[0147] In this embodiment, the correction information is not limited to the correction value of the state detection parameter, and any correction information used in the state detection process to correct the influence of the corresponding product 201 can be used. The correction information may include, for example, a predetermined calculation formula for correction. This correction information is an example of second information.

[0148] As in the first embodiment, Figure 12 It shows Figure 7 Details of the wireless power transmission processing of the RX 101 based on the WPC standard in the S703. Figure 12 In this embodiment, the content of each processing step in processing steps S1101 and S1103 to S1106 is the same as that in the first embodiment.

[0149] Figure 17 In this embodiment Figure 12 An example of the pre-configuration process performed in S1102. In this process, parameters for status detection related to wireless power transmission based on the authentication status of the corresponding product 201 and the information included in the NFC tag of the corresponding product 201 are determined.

[0150] The processing from S1501 to S1503 is the same as in the first embodiment. Figure 13 The processing from S1201 to S1203 is the same, so its description will be omitted.

[0151] In S1504, RX 101 determines whether the correction value of the status detection parameter has been read from the NDEF information of the NFC tag of the corresponding product 201. Based on the NDEF information of the NFC tag of the corresponding product 201 stored in memory 506 in S801 when the NFC tag detection / authentication process is executed in S702, the determination of whether the correction value has been read is made.

[0152] If the correction value of the status detection parameter has not yet been read (No in S1504), then in S1506, RX 101 sets the power-received device-based status detection parameter pre-recorded in memory 506 as the status detection parameter. Then, RX 101 retains the setting in memory 506 and ends the process.

[0153] If the correction value of the status detection parameter has already been read (as in S1504), then in S1505, RX 101 processes as follows: RX 101 uses the correction value of the status detection parameter stored in memory 506, and the status detection parameters suitable for the state where the corresponding product is not attached to RX 101, which are pre-recorded in memory 506 of RX 101, to perform a predetermined calculation. As a result, RX 101 calculates and determines the status detection parameters suitable for the state where the corresponding product 201 is attached to RX 101. The determined status detection parameters suitable for the state where the corresponding product 201 is attached to RX 101 are set, and the setting is stored in memory 506, and the process ends.

[0154] As in the first embodiment, in Figure 14 and Figure 15 The diagram illustrates the processing of the entire system in this embodiment.

[0155] As described above, according to this embodiment, the same effect as that described in the first embodiment can be obtained. Furthermore, in this embodiment, since the correction value of the state detection parameter is pre-stored as NEDF information in the NFC tag 202, the RX 101 can read the correction value of the state detection parameter, and in the pre-configuration process, the state detection parameter can be calculated based on the correction value.

[0156] As described above, RX 101 can perform appropriate processing that takes into account the impact of the corresponding product during power transmission processing.

[0157] <Fourth Embodiment> The fourth embodiment will now be described in detail with reference to the accompanying drawings. Furthermore, descriptions of configurations identical or similar to those of the first to third embodiments will be omitted.

[0158] The fourth embodiment illustrates an example of processing when, for example, the NDEF information of the NFC tag corresponding to product 201 does not include authentication-related information but includes a correction value for the status detection parameters. RX 101 performs calculations using the correction value for the status detection parameters and status detection parameters pre-recorded in RX 101's memory 506, suitable for a state where the corresponding product is not attached to RX 101. As a result, even when the NDEF information of the NFC tag corresponding to product 201 does not include authentication-related information, RX 101 calculates and sets status detection parameters suitable for a state where the corresponding product 201 is attached to RX 101.

[0159] Note that in this embodiment, when the NDEF information of the NFC tag of the corresponding product 201 includes authentication-related information, the processing is as follows. That is, as in the first and second embodiments, RX 101 is set with state detection parameters suitable for the state of the corresponding product 201 attached to RX 101 (state detection parameters based on the product state of the corresponding product). As will be described later, this is via... Figure 18 The processing in S1603 is performed.

[0160] The system configuration example in this embodiment, as well as the configuration of the powered device (RX 101), corresponding product 201, and powered device (TX 301), are the same as in the first embodiment. Therefore, their description will be omitted.

[0161] Handling of power receiving equipment As in the first embodiment, Figure 7 An overview of the processing of RX 101 is shown. Furthermore, as in the first embodiment, it is also... Figure 8 The details of the NFC tag detection / authentication process (S702) are shown. Furthermore, as in the first embodiment, [the following is also included]. Figure 10 The middle shows Figure 8 Details of NFC tag detection processing (mainly S801 to S803) in the process.

[0162] In this embodiment, Figure 8 In S804, RX 101 examines all NDEF information detected from an NFC tag that has not yet undergone processing. Examining NDEF information implies analysis. Figure 11 The NDEF information shown in any one of (A) to (D). Assume that the NFC tag 202 corresponding to product 201 is an NFC tag implemented by the provider of product 201, and as an example, the NFC tag 202 has three or four NDEF information. Figure 11 The NDEF information 1031, NDEF information 1032, and NDEF information 1033 in (D) are respectively related to Figure 11 The NDEF information 1021, NDEF information 1023, and NDEF information 1024 in (C) are the same. Here, Figure 11 The NFC tag shown in (D) does not include NDEF information containing authentication-related information.

[0163] As in the first embodiment, Figure 12 It shows Figure 7 Details of the wireless power transmission processing of the RX 101 based on the WPC standard in the S703. Figure 12 In this embodiment, the content of each processing step in processing steps S1101 and S1103 to S1106 is the same as that in the first embodiment.

[0164] Figure 18 and Figure 19 In this embodiment Figure 12 An example of the pre-configuration process performed in S1102. In this process, parameters for status detection related to wireless power transmission based on the authentication status of the corresponding product 201 and the information included in the NFC tag of the corresponding product 201 are determined.

[0165] The processing of S1601 is the same as in the first embodiment. Figure 13 The processing of S1201 is the same, so its description will be omitted.

[0166] In S1602, RX 101 determines whether the corresponding product has been detected attached to RX 101. Note that this determination process is already in S806 of S702. Figure 8 The determination is performed in S1602, so the result can be used in S1602. If the attachment of the corresponding product has not yet been detected (No in S1602), then in S1609, RX 101 sets the power-received device-based status detection parameters pre-recorded in memory 506 as status detection parameters. Then, RX 101 retains the setting in memory 506 and ends the process.

[0167] If RX 101 has detected the attachment of the corresponding product (as in S1602), then RX 101 proceeds to S1603 and determines whether the corresponding product 201 is in the corresponding product certified state. In S1603, the determination is made based on the authentication status-related information stored in memory 506 in S811 when the NFC tag detection / authentication process was executed in S702.

[0168] If the corresponding product 201 is not in the certified state (No in S1603), then in S1607, RX101 determines whether the correction value of the status detection parameter has been read from the NDEF information of the NFC tag of the corresponding product 201. If the correction value has not been read (No in S1607), then RX101 performs the process described in S1609 and ends the process. If the correction value of the status detection parameter has been read (Yes in S1607), then in S1608, RX101 processes as follows. RX101 uses the correction value of the status detection parameter stored in memory 506 and the status detection parameters suitable for the state where the corresponding product is not attached to RX101, which are pre-recorded in memory 506 of RX101, to perform calculations. As a result, RX101 calculates and determines the status detection parameters suitable for the state where the corresponding product 201 is attached to RX101. The RX 101 sets the state detection parameters suitable for the state of the corresponding product 201 attached to the RX 101, retains the settings in the memory 506, and ends the process.

[0169] If the corresponding product 201 is in the certified state (Yes in S1603), then in S1604, RX 101 determines whether the product information of the corresponding product 201 has been read from the NDEF information of the NFC tag of the corresponding product 201. In S1604, when the NFC tag detection / authentication process is executed in S702, the determination is based on the NDEF information of the NFC tag of the corresponding product 201 stored in the memory 506 in S801.

[0170] If the product information for the corresponding product 201 has not yet been read (No in S1604), then RX 101 performs the above process in S1607. If the product information for the corresponding product 201 has already been read (Yes in S1604), then in S1605, RX 101 determines whether the status detection parameters based on the product information of the corresponding 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), then RX 101 performs the above process 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), then in S1606, RX 101 sets the status detection parameters based on the product information of the corresponding product 201 recorded in the memory 506. Then, RX 101 retains the setting in the memory 506 and ends the process.

[0172] As in the first embodiment, in Figure 14 and Figure 15The diagram illustrates the processing of the entire system in this embodiment.

[0173] As a variation of this embodiment, in Figure 12 An example of the pre-configuration processing performed in S1102 could be... Figure 20 The process is shown. In this case, the processes S1601 to S1603 and S1707 to S1709 are respectively related to... Figure 18 S1601 to S1603 and Figure 19 The same processing is used for S1607 to S1609, so their description will be omitted.

[0174] In S1704, RX 101 determines whether the status detection parameters have been read from the NDEF information (NDEF information 1014) of the NFC tag of the corresponding product 201. These status detection parameters are appropriate for the state in which the corresponding product 201 is attached to RX 101. The appropriate status detection parameters for the state in which the corresponding product 201 is attached to RX 101 are as described above. In S1704, when the NFC tag detection / authentication process is executed in S702, the determination is based on the NDEF information of the NFC tag of the corresponding product 201 stored in memory 506 in S801.

[0175] If the status detection parameters have not yet been read (No in S1704), RX 101 proceeds to process S1707. If the status detection parameters have been read (Yes in S1704), then in S1705, RX 101 sets the status detection parameters recorded in memory 506 to the appropriate state for the corresponding product 201 to be attached to RX 101. Then, RX 101 retains the settings in memory 506 and ends the process.

[0176] As described above, according to this embodiment, the same effect as that described in the first embodiment above can be obtained. Specifically, in this embodiment, even when the corresponding product 201 is attached to RX 101 and authentication has not yet been successful (No in S1603), RX 101 can still perform the following processing. That is, when RX 101 has read the correction value of the status detection parameter from the NDEF information (Yes in S1607 and Yes in S1707), RX 101 can calculate and set the status detection parameter based on the correction value. In this way, RX 101 can set the status detection parameter that takes into account the influence of the corresponding product 201 and notify the power supply equipment 301.

[0177] As described above, RX 101 can perform appropriate processing that takes into account the impact of the corresponding product during power transmission processing.

[0178] <Other Embodiments> In various embodiments Figure 13 In the processing of the entire system shown, the processes from F1303 to F1310 can be performed between F1314 and F1315. Even in this case, the same effect as shown in the various embodiments can be obtained.

[0179] In the various embodiments described above, the corresponding product 201 has an NFC tag, and authentication processing for authenticating the NFC tag is performed. However, the use of a corresponding product without an NFC tag is also included within the scope of this disclosure. In this case, when a corresponding product without an NFC tag is detected attached to RX 101, a predetermined state detection parameter different from the "state detection parameter based on the powered device" can be set. This predetermined state detection parameter can, for example, be a state detection parameter that is estimated as a fixed value representing the influence of the corresponding product, independent of the structure of the corresponding product, etc.

[0180] In the above embodiments, examples of TX 301 performing state detection processing have been shown, but RX 101 can also perform this state detection processing. In this case, RX 101 does not need to notify TX 301 of the state detection parameters set in S1102, but can do so in the same manner as in the above embodiments.

[0181] exist Figure 9 In China, S806 and S808 ( Figure 13 The order of S1202 and S1203 in the code can be reversed. In this case, in S808 executed before S806, it is determined whether the attachment of the corresponding product 201 to RX 101 has been detected, whether the corresponding product 201 is in a certified state (yes) or not in a certified state (no). Similarly, in this case, with... Figure 9 The same approach described in the example indicates that, even if the corresponding product 201 is already certified, the process for decertifying is performed when the attachment of the corresponding product 201 has not yet been detected. Such processing can also be applied to... Figure 16 , Figure 17 and Figure 18 .

[0182] In the first embodiment, an example of a detection component for detecting the combination of RX 101 and corresponding product 201 is described below. For example, it is described that when corresponding product 201 is attached to or combined with RX 101, RX 101 detects that corresponding product 201 is attached to RX 101 by using sensor 103 to detect the detected part 203. However, it is not limited to this; for example, attachment can be detected by periodic NFC tag detection. Specifically, the following embodiments are envisioned. exist Figure 10 In the periodic NFC tag detection shown, RX 101 performs detection of the NFC tag 202 corresponding to product 201 (S902), and if the NFC tag detection is successful (Yes in S903), the read NDEF information is retained (S904). The NDEF information retained here includes, for example... Figure 11 When the information (device type, manufacturer, serial number, etc.) of the corresponding product 201 in the NDEF information 1001 shown meets predetermined conditions, RX 101 determines that the corresponding product 201 is attached to RX 101. The predetermined conditions are, for example, conditions that meet all of the following conditions. - Device type: Must be a lid - Manufacturer: This information must be pre-set in the RX 101. - Serial number: This must be information pre-set in the RX 101.

[0183] Some (or in some cases all) of the configurations in the embodiments can be replaced by other configurations with similar functionality, or can be omitted, and other configurations can be added. Furthermore, it is not limited to the WPC standard and can be applied to a variety of other standards.

[0184] Furthermore, the power transmitting and receiving equipment can be, for example, image input devices such as camera devices (still cameras or video cameras) or scanners, or image output devices such as printers, copiers, or projectors. Additionally, it can be a storage device such as a hard disk drive or memory device, or an information processing device such as a personal computer (PC), smartphone, or tablet.

[0185] Furthermore, the powered device according to this disclosure can be an information terminal device. For example, the information terminal device includes a display unit (display) supplied with power received from the powered antenna, which displays information to the user. Note that the power received through the powered antenna is accumulated in a power accumulation unit (battery), and power is supplied from the battery to the display unit. In this case, the powered device may include a communication unit that communicates with other devices different from the powered device. The communication unit may support communication standards such as NFC communication and fifth-generation mobile communication systems (5G).

[0186] Additionally, the power receiving device disclosed herein can be a vehicle, such as a car. For example, a car serving as a power receiving device can be adapted to receive power from a charger (power receiving device) via a power transmitting antenna installed in a parking lot. Furthermore, a car serving as a power receiving device can be adapted to receive power from a charger (power receiving device) via a power transmitting antenna buried in the road. In such a car, the received power is supplied to a battery. The battery power can be supplied to an activation unit (motor or electric motor unit) driving the wheels, or it can be used to drive sensors for drive assistance or to drive a communication unit for communication with external devices. In other words, in this case, in addition to wheels, the power receiving device can also have a battery, a motor driven using the received power, sensors, and can also have a communication unit for communicating with devices other than the power receiving device. Furthermore, the power receiving device can include a housing unit for accommodating people. Examples of sensors include sensors for measuring distances between vehicles or distances to other obstacles. The communication unit can be compatible with a Global Positioning System (e.g., Global Positioning Satellite (GPS)). Additionally, the communication unit can be compatible with communication standards such as 5G. Furthermore, the vehicle can be a bicycle or a motorcycle.

[0187] Furthermore, the power receiving device disclosed herein can be a power tool or a household appliance, etc. In addition to a battery, such a device as a power receiving device may also include a motor driven by the power received from the battery. Additionally, these devices may have a notification unit that indicates the remaining battery level, etc. Moreover, such a device may include 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 5G.

[0188] Additionally, the power transmission device disclosed herein can be an on-board charger in a vehicle, such as an automobile, that transmits power to portable information terminal devices supporting wireless power transmission, such as smartphones and tablets. This on-board charger can be located anywhere within the vehicle's interior. For example, it can be mounted on the vehicle's console, or on the instrument panel (dashboard or dashboard), between passenger seats, or on the ceiling or doors. However, it is preferred that the power transmission device not be mounted in a location where driving is disturbed. Furthermore, although the power transmission device has been described as an example of an on-board charger, it is not limited to such a charger located in a vehicle and can also be mounted in transportation machinery such as trains, airplanes, and ships. In this case, the charger can also be mounted between passenger seats or on the ceiling or doors.

[0189] Vehicles, such as automobiles, including onboard chargers, can be power transmission devices. In this case, the power transmission device includes wheels and a battery, and uses battery power to supply power to the receiving device through a power transmission circuit unit and a power transmission antenna.

[0190] This disclosure can also be implemented by supplying a program for implementing one or more functions of the above embodiments to a system or device via a network or storage medium, and having the program read and executed by one or more processors in the computer of the system or device. Alternatively, this disclosure can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0191] Furthermore, a portion of the process described with reference to the flowcharts in this disclosure can be implemented in hardware. For example, by using a predetermined compiler, dedicated circuits can be automatically generated on an FPGA based on the program used to implement the various steps. Additionally, the gate array circuitry can be formed in the same manner as an FPGA implemented as hardware.

[0192] As described above, the present disclosure has been described in detail based on preferred embodiments, but the present disclosure is not limited to the above embodiments, and various modifications can be made based on the spirit of the present disclosure, and such modifications are not excluded from the scope of the present disclosure.

[0193] (Cross-reference to related applications) This application claims the benefit of Japanese Patent Application No. 2024-040888, filed on March 15, 2024. The entire contents of the aforementioned Japanese patent application are incorporated herein by reference.

Claims

1. A power receiving device, comprising: A detection component configured to detect that the powered device and the corresponding product are combined; as well as A determining component is configured to determine the parameters used in the state detection process for detecting the state of the power receiving device and the power transmitting device based on whether the combination of the power receiving device and the corresponding product has been detected.

2. The power receiving device according to claim 1 further includes an acquisition component, the acquisition component being configured to acquire tag information from a near-field communication tag, i.e., an NFC tag, included in the corresponding product. in, When a combination of the powered device and the corresponding product is detected, the determining component determines the parameters based on the tag information.

3. The power receiving equipment according to claim 2, wherein, The label information includes product information for the corresponding product, and The determining component determines the parameters based on the product information of the corresponding product.

4. The power receiving equipment according to claim 3, wherein, When the powered device has parameters based on product information of the corresponding product, the determining component determines the parameters based on the product information of the corresponding product as the parameters used in the state detection process. When the powered device does not have parameters based on product information of the corresponding product, the determining component determines the parameters obtained when the corresponding product is not combined with the powered device as the parameters used in the state detection process.

5. The power receiving equipment according to claim 2, wherein, The label information includes information for specifying the parameters, and The determining component determines the parameter based on the information used to specify the parameter.

6. The power receiving equipment according to claim 2, wherein, The label information includes correction information for correcting the impact of the corresponding product on the state detection process, and The determining component determines the parameters based on the correction information.

7. The power receiving device according to claim 2 further includes an authentication component configured to perform authentication processing for the corresponding product.

8. The power receiving equipment according to claim 7, wherein, The authentication component performs the authentication process based on the first information in the tag information, and If the authentication process has successfully authenticated the corresponding product, the determining component determines the parameter based on second information in the label information that is different from the first information.

9. The power receiving equipment according to claim 7, wherein, If the authentication process has not yet successfully authenticated the corresponding product, the determining component will determine the parameters obtained when the corresponding product is not combined with the powered device as the parameters used in the state detection process.

10. The power receiving equipment according to claim 7, wherein, If the certification process has not yet successfully certified the corresponding product, and if correction information for correcting the impact of the corresponding product in the status detection process is obtained from the label information, the determining component determines the parameter based on the correction information.

11. The power receiving equipment according to claim 1, wherein, If the detection component does not detect a combination of the powered device and the corresponding product, the determining component determines the parameters obtained in the state where the corresponding product is not combined with the powered device as the parameters used in the state detection process.

12. The power receiving equipment according to claim 1, wherein, The state detection process is used to detect foreign objects between the power supply equipment and the power receiving equipment, or to detect the electromagnetic coupling state between the power supply coil included in the power supply equipment and the power receiving coil included in the power receiving equipment.

13. The power receiving device according to claim 1, further comprising a notification component configured to notify the power supply device of the determined parameters.

14. A method performed by an electrical receiving device, the method comprising: The power receiving device and the corresponding product were detected to be combined; as well as The parameters used in the state detection process for detecting the state of the power receiving equipment and the corresponding product are determined based on whether the combination of the power receiving equipment and the corresponding product has been detected.

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

Images