Power receiving apparatus, power transmitting apparatus, method executed by power receiving apparatus, method executed by power transmitting apparatus, and program

Abstract

Provided is a power receiving device (101) that wirelessly receives power from a power transmitting device (102). A power receiving device detects a near field communication (NFC) tag (S502, S516), and reads one or more pieces of tag data from the detected NFC tag. The power receiving apparatus then selects a processing method related to one or more pieces of tag data according to whether or not reading of the tag data is performed in a state in which the power receiving apparatus is capable of receiving power from the power transmitting apparatus (S503 and subsequent steps, or S517 and subsequent steps), and performs processing.

Description

Technical Field

[0001] This disclosure relates to wireless power transmission technology. Background Technology

[0002] In recent years, the technology of wireless power transmission systems has become widespread. The technology of wireless power transmission systems generally conforms to the standards established by the WPC (Wireless Power Alliance) as a standardization organization for wireless charging (Wireless Power Alliance (WPC) standards).

[0003] Meanwhile, the NFC standard is known as the standard for short-range wireless communication. NFC stands for Near Field Communication. In the NFC standard, polling refers to sending messages to detect devices acting as communication partners by transmitting and modulating a carrier wave. Polling is sent by devices equipped with NFC standard reader / writer functionality. Furthermore, devices that receive polling messages from readers / writers and respond to these polling messages by applying load modulation to the carrier wave transmitted by the readers / writers are called NFC tags.

[0004] The information exchanged in the NFC standard conforms to 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 the read NDEF messages are processed is determined by the device, and some devices only process the first NDEF message among the multiple read NDEF messages.

[0005] Patent Document 1 discloses a technique in which a power receiving device with both WPC and NFC functions disables its NFC function when a power transmitting device is detected during contactless charging. Therefore, the power transmitting device can transmit high-output power without damaging the NFC tag.

[0006] Furthermore, Patent Document 2 discloses the following technology: If the power transmitting device does not have an NFC tag detection function, the power receiving device performs NFC tag detection and notifies the power transmitting device of the detection result from the power receiving device with NFC tag detection function. When the power receiving device has detected an NFC tag, the power transmitting device stops power transmission or transmits power at low power by limiting the maximum power transmission value to a predetermined value or a smaller value, thereby minimizing damage to the NFC tag.

[0007] [List of Citations] [Patent Documents] [Patent Document 1] Japanese Patent Application Publication No. 2020-089134 [Patent Document 2] Japanese Patent Application Publication No. 2020-182355 Summary of the Invention

[0008] [Technical Issues] When a power receiving device has already read tag data from an NFC tag on a power transmitting device or from an NFC tag placed near the power transmitting device, appropriate processing is expected to protect the NFC tag. However, it is also conceivable that the power receiving device might read tag data from an NFC tag even when it is not receiving power from the power transmitting device or is unable to receive power from it. In this case, there is room to consider how the power receiving device, etc., should handle the tag data.

[0009] This disclosure provides a technique for appropriate processing when reading tag data from an NFC tag.

[0010] [Solution to the problem] According to one aspect of this disclosure, a power receiving device is provided for wirelessly receiving power from a power transmitting device. The power receiving device includes: a detection unit configured to detect near field communication (NFC) tags; a reading unit configured to read one or more tag data from the detected NFC tags; and a processing unit configured to perform processing by selecting a processing method related to one or more tag data based on whether the reading unit has read the tag data in a state where the power receiving device is capable of receiving power from the power transmitting device.

[0011] [Beneficial effects of the invention] According to this disclosure, appropriate processing can be performed when reading tag data from an NFC tag. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating a construction example of a wireless power transmission system according to the first embodiment.

[0013] Figure 2 This is a block diagram illustrating an example of the construction of a power receiving device according to an embodiment.

[0014] Figure 3 This is a block diagram illustrating an example of the construction of a power transmission device according to an embodiment.

[0015] Figure 4 This is a flowchart illustrating the processing performed by the power receiving device according to an embodiment.

[0016] Figure 5 This is part of a flowchart illustrating the process of determining the required power value, primarily performed by the power receiving device in the first embodiment.

[0017] Figure 6 From Figure 5 The flowchart continues.

[0018] Figure 7 This is a sequence diagram illustrating the processes performed by the power receiving device and the power transmitting device according to the first embodiment.

[0019] Figure 8 This is a diagram showing the NDEF information stored in the NFC tag.

[0020] Figure 9 This is a diagram illustrating a construction example of a wireless power transmission system according to a second embodiment.

[0021] Figure 10 This is a flowchart illustrating the process for detecting multiple NFC tags in the second embodiment.

[0022] Figure 11 This is part of a flowchart illustrating the process of determining the required power value, primarily performed by the power receiving device in the second embodiment.

[0023] Figure 12 From Figure 11 The flowchart continues.

[0024] Figure 13 This is a sequence diagram illustrating the processes performed by the power receiving device and the power transmitting device in the second embodiment.

[0025] Figure 14 This is a diagram showing NDEF information stored in another NFC tag. Detailed Implementation

[0026] Embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. Furthermore, not all features of the embodiments of the present disclosure are essential to the present disclosure, and the multiple features can be combined arbitrarily. In the drawings, the same reference numerals are used to denote the same or similar constituent elements, thereby avoiding redundant description.

[0027] [First Embodiment] <System Construction> Figure 1 This is a diagram illustrating a construction example of a wireless power transmission system according to an embodiment. A construction example of a wireless power transmission system according to an embodiment will be described. In this example, the wireless power transmission system is constructed to include a power receiving device 101 and a power transmitting device 102. For simplicity of the notation below, the power transmitting device 102 may be referred to as TX, and the power receiving device 101 may be referred to as RX.

[0028] For example, the RX is an electronic device that receives power from the TX and charges its built-in battery. Furthermore, the RX includes Wireless Power Consortium (WPC) functionality compliant with the WPC standard and also supports the standard's device authentication protocol. Additionally, the RX includes Near Field Communication (NFC) functionality. By using this function, the RX can, for example, operate in card emulation mode and enable electronic money payments. Furthermore, the RX includes NFC functionality such as being able to read NFC tags (another device) 103 via NFC communication when operating in reader / writer mode.

[0029] For example, TX is an electronic device that wirelessly transmits power to RX placed on its own device. TX wirelessly transmits power to RX via a power transmitting coil. Furthermore, TX includes NFC functionality: when operating in reader / writer mode, it can read NFC tag 103 via NFC communication. By using this function, TX can detect NFC devices and, for example, stop or limit power transmission, thereby protecting NFC tag 103. NFC tag 103 is an example of a device that operates without a battery and enables near-field wireless communication. More specifically, NFC tag 103 refers to an NFC / RFID tag capable of NFC communication, an NFC communication device operating in card emulation mode, etc.

[0030] Typically, a power transmitting device may exist that has an NFC tag with NFC Data Exchange Format (NDEF) information corresponding to the additional information or service provided to the power receiving device. When a battery-free NFC tag is exposed to a high-power electromagnetic field generated by power transmission processing, the tag's antenna elements may be damaged. The NFC tag is constructed to be resistant to damage when power is transmitted at a specific output level or lower, and the NDEF information can be set to indicate this resistance. Thus, the power receiving device can perform processes such as displaying a UI for utilizing the additional information and services, and the power transmitting device can perform appropriate power transmission processing. For example, when the power receiving device reads multiple NDEF messages, appropriate processing related to the NDEF information is required.

[0031] The NFC tag 103 is, for example, built into the TX. When the NFC tag 103 is an external device of the TX, the NFC tag 103 can be attached to the surface of the TX or placed in the vicinity of the TX.

[0032] While examples of using a smartphone as an RX and a charger as a TX have been described, this disclosure is not limited thereto. RX and TX can be integrated into other devices (cameras, smartphones, tablets, laptops, cars, robots, medical devices, and printers) and configured to power these devices.

[0033] This system assumes to use an electromagnetic induction scheme for contactless charging based on the WPC standard for wireless power transmission. That is, RX and TX perform contactless charging wireless power transmission between the power receiving coil of RX and the power transmitting coil of TX, based on the WPC standard. Furthermore, the wireless power transmission scheme (contactless power transmission scheme) is not limited to the scheme defined by the WPC standard, and can also be another electromagnetic induction scheme, magnetic field resonance scheme, electric field resonance scheme, microwave scheme, or scheme using lasers, etc. Although this embodiment assumes that wireless power transmission is used for contactless charging, it can also be used for purposes other than contactless charging.

[0034] In the WPC standard, the guaranteed power level that the RX receives from the TX 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) of the RX, even if the positional relationship between the RX and TX fluctuates and the power transmission efficiency between the power receiving coil and the power transmitting coil decreases; that is, the load power value (load power) of the RX. Furthermore, GP can be a load power level negotiated and agreed upon between the TX and RX. For example, when GP is 15 watts, the TX controls power transmission so that even if the positional relationship between the power receiving coil and the power transmitting coil fluctuates and the power transmission efficiency decreases, 15 watts can still be output to the load within the RX.

[0035] <Structure of Power Receiving Equipment> exist Figure 2 The diagram shows an example of the construction of an RX according to this embodiment. The RX includes a control unit 201, an NFC communication unit 202, a WPC communication unit 203, a power receiving coil 204, a power receiving unit 205, a detection unit 206, a charging unit 207, a battery 208, a notification unit 209, an operation unit 210, a memory 211, and a timer 212.

[0036] Control unit 201 controls the entire smartphone. Examples of control unit 201 include a central processing unit (CPU) or a microprocessor unit (MPU). Furthermore, control unit 201 can use timer 212 for time measurement. For example, control unit 201 performs control by executing a control program stored in memory 211. For example, control unit 201 is configured to include one or more processors such as a central processing unit (CPU) or a microprocessor unit (MPU).

[0037] Furthermore, control unit 201 may include hardware dedicated to a specific process, such as an application-specific integrated circuit (ASIC). Alternatively, control unit 201 may be configured to include an array of circuitry, such as a field-programmable gate array (FPGA), which is compiled to perform a predetermined process. Control unit 201 causes memory 211 to store information to be stored while performing various types of processing.

[0038] Although control unit 201 is shown as a single component in this embodiment, the invention is not limited thereto. For example, a WPC control unit (which controls the processing related to receiving power from the power transmitting device in the power receiving device) may be constructed separately from control unit 201. Alternatively, an NFC control unit (which controls the processing related to NFC communication) may be constructed separately from control unit 201. Alternatively, the WPC control unit and the NFC control unit may each be constructed separately from control unit 201. When control unit 201 is constructed as multiple separate control units, the control units are connected to each other via a communication interface to enable data communication. The communication interface can be any interface that enables data communication, such as an internal integrated circuit (I2C) or a general purpose input / output (GPIO).

[0039] The NFC communication unit 202 is a hardware module that implements NFC functionality. Specifically, it implements a card emulation mode as an alternative to a contactless IC card, a reader / writer mode for reading NFC tag 103, and a peer-to-peer (P2P) mode for directly exchanging messages between NFC devices. For example, the card emulation mode can be used to implement electronic money payments. At least the NFC communication unit 202 serves as a detection unit for detecting NFC tag 103 and a reading unit for reading one or more tag data from the detected NFC tag.

[0040] Furthermore, as described below, the control unit 201 is mainly used as a processing unit that performs processing by selecting a processing method related to one or more tag data based on whether the reading unit has read the tag data when the power receiving device is able to receive power from the power transmitting device.

[0041] WPC communication unit 203 communicates with TX communication unit 306 via wireless power transmission based on the WPC standard. WPC communication unit 203 demodulates the electromagnetic waves input from power receiving coil 204 to obtain information transmitted from TX, and performs load modulation on the electromagnetic waves to superimpose the information to be transmitted to TX onto the electromagnetic waves, thereby communicating with TX.

[0042] The power receiving unit 205 receives alternating current (AC) power (AC voltage and AC current) generated by electromagnetic induction based on electromagnetic waves emitted from the power transmitting coil of TX via the power receiving coil 204. The power receiving unit 205 converts the AC power into direct current (DC) power or AC power of a predetermined frequency and outputs the converted power to the detection unit 206.

[0043] The detection unit 206 detects whether the RX is placed on the TX based on the WPC standard. For example, when the power receiving unit 205 receives a digital Ping of the WPC standard via the power receiving coil 204, the detection unit 206 detects at least one of the voltage and current values ​​of the power receiving coil 204. For example, when the voltage value is lower than a predetermined voltage threshold or when the current value exceeds a predetermined current threshold, the detection unit 206 can determine that the RX has been placed on the TX.

[0044] In this embodiment, the placement of RX on TX means that RX is able to receive power from TX. For example, TX has a charging rack, and when RX is placed on the rack, RX can receive power. It cannot be said that the state in which RX is not placed on the rack is a state in which it can receive power.

[0045] Here, it is also conceivable that even if a power receiving device is placed on a power transmitting device, it may not necessarily be able to receive power. This could occur, for example, when a cover, casing, or other component that blocks or attenuates electromagnetic waves is attached to the power receiving device, or when an unintended component that blocks or attenuates electromagnetic waves is located between the power transmitting and receiving devices. In other words, the "state in which the power receiving device is placed on the power transmitting device" described in the flowcharts and other documents of this embodiment is merely an example of a state in which the power receiving device can receive power from the power transmitting device.

[0046] Furthermore, the state in which a power receiving device can receive power is not limited to the state in which the power receiving device is placed on a power transmitting device. For example, the state in which the power receiving device can receive power can be a state in which the power receiving device and the power transmitting device are in contact or close proximity due to mechanical engagement, or a state in which the power receiving device is in contact with the power transmitting device due to magnetic force.

[0047] In this embodiment, the state in which RX is placed on TX will be used as a typical example of the state in which RX can receive power to give the following description.

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

[0049] Battery 208 provides the entire RX with the power required for the control of various parts of the RX by the control unit 201 or for power reception and communication. In addition, battery 208 stores the power received via power receiving coil 204.

[0050] The notification unit 209 notifies the user of information through any method, such as visual, auditory, or tactile methods. For example, Figure 1 As shown, notification unit 209 notifies the user of the charging status of the RX and the status related to power transmission of the wireless power transmission system including the RX and TX. For example, notification unit 209 may be configured to include a liquid crystal display, a light-emitting diode (LED), a speaker, a vibration generating circuit, or other notification device.

[0051] The operation unit 210 has a receiving function for receiving operations from the user on the RX. The operation unit 210 is configured to include, for example, buttons, a keyboard, a voice input device (such as a microphone), a motion detection device (such as an accelerometer and a gyroscope sensor), or other input devices. Furthermore, the device integrating the notification unit 209 and the operation unit 210 can be used like a touch panel.

[0052] As described above, memory 211 stores various types of information (such as identification information and device configuration information), control programs, etc. Furthermore, memory 211 can store information obtained from functional units different from control unit 201.

[0053] Timer 212 uses, for example, an incrementing timer that measures the elapsed time since the activation time, or a decrementing timer that counts down from the set time to measure the time.

[0054] <Structure of Electric Power Transmission Equipment> Figure 3 An example of the construction of a TX according to this embodiment is shown. The TX includes a control unit 301, a power supply unit 302, a power transmission unit 303, a detection unit 304, a power transmission coil 305, a communication unit 306, a notification unit 307, an operation unit 308, a memory 309, and a timer 310.

[0055] Control unit 301 controls the entire TX by, for example, executing a control program stored in memory 309. That is, control unit 301 controls... Figure 3 The functional units shown are as follows. Furthermore, control unit 301 performs control related to power transmission control in the TX. Additionally, control unit 301 performs control related to the NFC function of the TX. Moreover, control unit 301 can perform control for applications other than wireless power transmission. For example, control unit 301 is configured to include one or more processors such as a CPU or MPU. Control unit 301 may include a single processor, or a main control unit for overall control and sub-control units for controlling power transmission processing (as shown in the reference). Figure 2 (as described above), and NFC communication can be implemented by a separate processor.

[0056] Furthermore, the control unit 301 can be configured to include dedicated hardware (such as an application-specific integrated circuit (ASIC)) or array circuitry (such as an FPGA) for specific processes, which is compiled to execute predetermined processes. When executing various types of processes, the control unit 301 stores information to be stored in memory 309. Additionally, the control unit 301 can use timer 310 for time measurement.

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

[0058] The power transmitting unit 303 converts the DC or AC power input from the power supply unit 302 into AC frequency power in a frequency band suitable for wireless power transmission, and inputs this AC frequency power into the power transmitting coil 305, thereby generating electromagnetic waves for the RX to receive power. The frequency of the AC power generated by the power transmitting unit 303 is, for example, approximately several hundred kilohertz (kHz) (e.g., 110 kHz to 205 kHz). Based on instructions from the control unit 301, the power transmitting unit 303 inputs the AC frequency power into the power transmitting coil 305, causing the electromagnetic waves used for power transmission to be output from the power transmitting coil 305 to the RX.

[0059] Furthermore, the power transmission unit 303 controls the intensity of the electromagnetic wave to be output by adjusting the voltage (power transmission voltage) or current (power transmission current) or both input to the power transmission coil 305. If the power transmission voltage or current increases, the intensity of the electromagnetic wave increases, and if the power transmission voltage or current decreases, the intensity of the electromagnetic wave decreases. Furthermore, the power transmission unit 303 controls the output of AC frequency power based on instructions from the control unit 301, causing power transmission from the power transmission coil 305 to start or stop. Furthermore, the power transmission unit 303 is configured such that the control unit 301 can know the power transmission at any given time by notifying the control unit 301 of the current power transmission. Furthermore, the measurement of the transmitted power and the notification to the control unit 301 can be configured to be performed by a unit other than the power transmission unit 303.

[0060] The detection unit 304 detects whether an object has been placed on the TX based on the WPC standard. Specifically, the detection unit 304 detects whether the object is placed on the interface surface of the TX. For example, when the power transmitting unit 303 transmits a WPC standard analog Ping via the power transmitting coil 305, the detection unit 304 detects at least one of the voltage and current values ​​of the power transmitting coil 305.

[0061] Furthermore, the detection unit 304 can detect changes in impedance. Additionally, when the voltage drops below a predetermined voltage value or when the current value exceeds a predetermined current value, the detection unit 304 can determine that an object has been placed on the TX. The object is determined to be a power receiving device or another foreign object based on whether a predetermined response to a digital ping subsequently sent by the communication unit 306 exists. In other words, if the TX has received a predetermined response, the object is determined to be a power receiving device; otherwise, the object is determined to be something other than a power receiving device.

[0062] As described above, communication unit 306 communicates with RX for control purposes based on the WPC standard. Communication unit 306 modulates the electromagnetic waves output from power transmission coil 305 and transmits the information to RX for communication. Furthermore, communication unit 306 demodulates the electromagnetic waves output from power transmission coil 305 and modulated by RX to obtain the information transmitted by RX. In other words, the communication performed by communication unit 306 is executed by superimposing information onto the electromagnetic waves transmitted from power transmission coil 305.

[0063] Furthermore, the communication unit 306 performs NFC communication and detects the NFC tag 103 of the power-generating device. Additionally, within the communication unit 306, the module for control communication based on the WPC standard and the module for NFC communication can be implemented by a single piece of hardware, or they can be implemented by separate hardware components.

[0064] The notification unit 307 notifies the user of information through any method such as visual, auditory, or tactile means. For example, the notification unit 307 notifies the user of information indicating the charging status of TX or information related to the power transmission status of a wireless power transmission system including TX and RX, such as... Figure 1 As shown. The notification unit 307 is configured to include, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, or other notification devices.

[0065] The operation unit 308 has a receiving function for receiving operations from the user on TX. The operation unit 308 is configured to include, for example, buttons, a keyboard, a voice input device (such as a microphone), a motion detection device (such as an accelerometer and a gyroscope sensor), or other input devices. Furthermore, the device integrating the notification unit 307 and the operation unit 308 can be used like a touch panel.

[0066] The memory 309 stores various types of information, such as identification information and capability information, control programs, etc. Furthermore, the capability information includes information indicating whether the device has high-precision foreign object detection capabilities. Additionally, the memory 309 can store information obtained by functional units other than the control unit 301.

[0067] The timer 310 uses, for example, an incrementing timer that measures the elapsed time since the activation time, or a decrementing timer that counts down from the set time to measure the time.

[0068] Processing in power receiving equipment Figure 4 This is a flowchart illustrating an example of a process executed by the RX. For example, this process can be implemented by the RX's control unit 201 executing a program read from memory 211. Furthermore, at least a portion of the following processes can be implemented in hardware. In this case, for example, a predetermined compiler can be used to automatically generate dedicated circuitry using gate array circuitry (such as an FPGA) to implement the hardware based on the program used to implement the various processing steps. This is similar to what will be described below. Figures 5 to 7 and Figures 10 to 12 The processing shown.

[0069] When the user of the RX activates the RX based on the power supplied from the battery 208 or inputs a command to start the contactless charging application based on the RX's powered-on state, this process can be executed in response to that input. Furthermore, this process can be initiated by other triggers.

[0070] In S401, after the process begins, the RX performs the Ping phase process defined in the WPC standard and waits for its own device to be placed on the TX. For example, the RX detects placement on the TX by detecting a digital Ping from the TX. If the RX detects that its own device has been placed on the RX, then in S402, the RX's identification information and capability information are sent to the TX through the construction phase communication defined in the WPC standard.

[0071] Here, the RX's identification information includes the manufacturer code and basic device ID. The RX's capability information includes the following: • Information used to identify the supported WPC standard version; • Maximum power value (or reference power), which is used to identify the maximum power that RX can provide to the load; • Information indicating whether the negotiation function of the WPC standard is provided.

[0072] However, this information is merely an example, and the RX's identification and capability information can be replaced with other information, or may include additional information. For example, the identification information can be any other identification information used to identify the entity of the RX, such as a wireless power ID. Furthermore, the RX can use methods other than communication during the construction phase of the WPC standard to send the identification and capability information.

[0073] If identification and capability information are sent, the RX begins communication during the negotiation phase as defined in the WPC standard. If communication during the negotiation phase begins, in S403, the RX obtains NFC tag detection information from the TX. This NFC tag detection information may include information such as whether the TX has NFC tag detection capability, whether NFC tag detection processing has been performed, and whether an NFC tag has been detected as a result of the NFC tag detection processing.

[0074] After acquiring NFC tag detection information, RX determines in S404 whether to perform NFC tag detection processing. Here, the determination of whether to perform NFC tag detection processing is based on the NFC tag detection information acquired from TX. For example, when TX does not have NFC tag detection functionality, or when TX has NFC tag detection functionality but has not yet performed NFC tag detection, RX can perform NFC tag detection processing, etc. Furthermore, the present invention is not limited to this. When an NFC tag is detected as a result of performing NFC tag detection in TX, RX can also perform NFC tag detection processing to reconfirm the presence of an NFC tag. Therefore, NFC tags can be detected more reliably.

[0075] When it is determined that NFC tag detection processing will be performed ("Yes" in S404), RX moves the process to S405. Conversely, when it is determined that NFC tag detection processing will not be performed ("No" in S404), RX moves the process to S412. In S405, RX sends a pause request to TX and moves the process to S406. In S406, RX performs NFC tag detection processing and moves the process to S407. Here, NFC tag detection processing can be performed sequentially for various tag types (Type A, Type B, and Type F) using NFC-compliant reader / writer functions, but is not limited to this.

[0076] If NFC tag detection processing is performed, the RX determines in S407 whether an NFC tag has been detected during the NFC tag detection process. This determination can be based on whether a pre-defined communication with the NFC tag was performed using a reader / writer function, or whether the data stored in the NFC tag (tag data) was successfully read. The data stored in the NFC tag can be data recorded in the NDEF format defined in the NFC standard. The data stored in the NFC tag only needs to be in a format that the RX can recognize as pre-defined data (such as raw data), and the data is not limited to this.

[0077] When it is determined that an NFC tag has been detected ("Yes" in S407), the RX proceeds to S408. Conversely, when it is determined that no NFC tag has been detected ("No" in S407), the RX proceeds to S410. In S408, the RX determines whether the detected NFC tag is a power-transmitting NFC tag. This can be determined by checking whether the tag data read from the NFC tag includes power-transmitting permission tag data indicating that power transmission is permitted. If power-transmitting permission tag data is included, then the NFC tag is a power-transmitting NFC tag. The format of the data indicating that the detected NFC tag is a power-transmitting NFC tag can be a value, a string, etc., and is not limited to these.

[0078] When it is determined that the detected NFC tag is an NFC tag that allows power transmission ("Yes" in S408), the RX moves the process to S409. On the other hand, when it is determined that the detected NFC tag is not an NFC tag that allows power transmission ("No" in S408), the RX sends a WPC standard End Power Transmission (EPT) data packet to the TX and ends the process.

[0079] Although in this embodiment the process terminates immediately when the detected NFC tag is not a power-transmitting NFC tag, the process may not terminate. In this case, by setting the desired power value (described below) to a limited power value, power transmission and reception can continue while preventing damage and overheating of the NFC tag, thereby achieving a safer and more efficient wireless power transmission system.

[0080] In S409, the RX stores predetermined information included in the data stored in the NFC tag that allows power transmission, and the processing moves to S410. Here, the predetermined information may primarily be the power value that the NFC tag allows power transmission. The power value that allows power transmission (hereinafter referred to as the permitted power value) may be a power value indicating the tolerance of the NFC tag's power transmission relative to the TX or the power reception of the RX. Specifically, the power value indicating the NFC tolerance may be a power value corresponding to the required power value of the negotiable load power or the guaranteed load power described below. The permitted power value is a piece of information included in the power transmission permitted tag data.

[0081] In addition to the permitted power value, the pre-defined information may also include the Qi standard version in the WPC standard, information about the NFC versions supported by the NFC tag, and the version of the protection function. Information about the NFC versions supported by the NFC tag may include, for example, the NFC-related standard versions established by the NFC Forum, the NFC standardization organization, and type A / B / F information.

[0082] Subsequently, in S410, RX re-executes the Ping phase process defined in the WPC standard and waits for its own device to be placed on TX. When it detects that RX has been placed on TX, RX sends identification and capability information to TX in S411 via the construction phase communication defined in the WPC standard, and moves the process to S412. In S412, RX performs a process to determine the required power value. The process for determining the required power value will be described below.

[0083] In S413, RX sends the required power value (the required value for transmitting power) determined in S412 to TX, and uses TX to determine the GP value. If RX determines the GP, RX sends information about the predetermined received power value to TX, thus determining the relationship between received power and transmitted power in the absence of foreign objects in S414. Here, the information about the predetermined received power value includes the received power value under light load / light load conditions and the received power value under maximum load / connected load conditions. If the information about the received power value has been sent, RX begins power reception in S415 according to the communication in the power transmission phase defined in the WPC standard. Subsequently, when an error occurs or the battery reaches a fully charged state, RX sends an EPT data packet according to the WPC standard. Thus, power transmission from TX stops, and the series of processes for contactless charging ends.

[0084] Figure 5 and Figure 6 This is a flowchart primarily illustrating the process performed by RX in S412 to determine the required power value. Furthermore, Figure 5 and Figure 6 This illustrates an example of how the RX selects a processing method related to tag data (in this case, NDEF information) read from an NFC tag to perform processing, depending on whether the RX is placed on the TX. The required power value is the power information sent to the TX during the negotiation phase.

[0085] When the process is triggered, RX determines whether it has been placed on TX (S501). Whether RX has been placed on TX can be determined by whether S401 has been completed. When it is determined that RX has been placed on TX ("Yes" in S501), RX moves to S502 for processing related to NDEF information, which includes processing for determining the required power value in wireless power transmission. On the other hand, when it is determined that RX has not been placed on TX ("No" in S501), RX moves to S516 for processing NDEF information unrelated to wireless power transmission. That is, RX selects a processing method related to one or more tag data to perform processing based on whether the tag data is read while RX is placed on TX.

[0086] The processing related to tag data refers to the following processing performed by the RX. These processing include processing to confirm the existence of specific tag data (e.g., power transmission license tag data) [1], processing related to power transmission using tag data [2], and processing of information content based on tag data [3].

[0087] The processing method indicates the processing (one or more processes) to be performed (or not performed) in processing [1], [2] and [3], and the tag data (one or more tag data) to be processed in response to processing [3] among multiple tag data. In addition, the processing method may refer to the order in which the three processes [1], [2] and [3] are performed.

[0088] In S502, RX determines whether it has already performed NFC tag detection processing. S502 represents the processing of S404. If NFC tag detection processing has been performed ("Yes" in S502), RX moves the processing to S503. On the other hand, if NFC tag detection processing has not been performed ("No" in S502), RX moves the processing to S510.

[0089] In S503, RX determines whether an NFC tag has been detected in the NFC tag detection process of S406. If it is determined that an NFC tag has been detected ("Yes" in S503), RX moves the process to S504. On the other hand, if it is determined that no NFC tag has been detected ("No" in S503), RX moves the process to S510.

[0090] In S504, RX determines whether the reading from NFC tag 103 was successful. If the reading is successful ("Yes" in S504), RX moves the process to S505. On the other hand, if RX determines that the reading was unsuccessful ("No" in S504), because RX confirms the existence of the NFC tag but cannot determine whether the tag is a tag that allows power transmission, the protection of the NFC tag is given priority, and the process proceeds to S509.

[0091] In S505, RX confirms the NDEF information read from NFC tag 103 (e.g., all NDEF information here). Figure 8 This is a diagram illustrating an example of NDEF information (multiple NDEF messages). In this embodiment, step S505 is to analyze... Figure 8 The steps 701 to 703 of the NDEF information are shown. In this embodiment, it is assumed that the NFC tag 103 is an NFC tag implemented by a TX provider and has three NDEF information entries as an example.

[0092] NDEF information 701 is Uniform Resource Locator (URL) information and is considered, for example, a URL related to services provided in conjunction with a TX (Transmission Device). NDEF information 702 is considered information about the TX, device type information (e.g., indicating "TX," i.e., information about the power transmission device), manufacturer information, serial number, etc. NDEF information 703 is information permitting power transmission, i.e., power transmission license tag data, and is considered, for example, the version of wireless power transmission and the licensed power value (e.g., 10W). NDEF information is not limited to... Figure 8 The information shown can be configured to set various parameters according to the intended use specified by the TX provider.

[0093] In this embodiment, the left side represents the first NDEF information, the middle side represents the second NDEF information, and the right side represents the third NDEF information. The RX reads the NDEF information sequentially from the left. When NDEF information is stored in an NFC tag, it can be stored in association with an ID or number used to identify the NDEF information. In this case, the RX only needs to read the NDEF information in the order of the ID or number.

[0094] In S506, RX determines whether the detected NFC tag is an NFC tag that allows power transmission. That is, in S506, RX checks whether NDEF information 703 exists. This process is the process described above for checking whether specific tag data (e.g., tag data that allows power transmission) exists [1]. Furthermore, the processes in S506 to S513 are the processes described above related to power transmission using tag data [2].

[0095] When it is determined that the detected NFC tag is an NFC tag that allows power transmission (NDEF information 703 exists) ("Yes" in S506), the RX moves the process to S507. On the other hand, when it is determined that the detected NFC tag is not an NFC tag that allows power transmission (NDEF information 703 does not exist) ("No" in S506), the RX determines the limited power value as the required power value (S509) and ends the required power value determination process. The limited power value is a value less than or equal to a predetermined value that is small enough to reduce the possibility of damage, overheating, etc., of the NFC tag even when power transmission processing continues. For example, it can be 5 watts or lower, but is not limited to this.

[0096] In S507, RX determines whether the permitted power value is less than the transmittable power value. The transmittable power value is the maximum power value that TX can transmit at that time, and can be the negotiated load power of the WPC standard. When the permitted power value is less than the transmittable power value ("Yes" in S507), RX moves the process to S508. On the other hand, when the permitted power value is greater than or equal to the transmittable power value ("No" in S507), RX moves the process to S510.

[0097] In S508, the RX determines whether the permissible power value is less than the acceptable power value. The acceptable power value is the maximum power value that the RX can receive at that time, and it can be calculated based on the RX's operating state. Furthermore, the maximum acceptable power value can be the maximum power value (or a reference power value). In this case, the control unit 201 acts as a calculation unit. The operating state of the RX can be determined by, for example, load, temperature, the coupling coefficient between the transmitting coil and the receiving coil, etc., but is not limited to these. When the permissible power value is less than the acceptable power value ("yes" in S508), the RX determines the permissible power value as the desired power value (S511) and ends the desired power value determination process. On the other hand, when the permissible power value is greater than or equal to the acceptable power value, the RX moves the process to S510.

[0098] In S510, RX determines whether the receivable power value is less than or equal to the transmittable power value. When the receivable power value is less than or equal to the transmittable power value ("Yes" in S510), RX determines the receivable power value as the desired power value (S512) and ends the desired power value determination process. On the other hand, when the receivable power value is greater than the transmittable power value ("No" in S510), RX determines the transmittable power value as the desired power value (S513) and ends the desired power value determination process.

[0099] In S514, RX determines whether there is any NDEF information other than the NDEF message indicating permission to transmit power (e.g., NDEF information 703) among the NDEF information confirmed in S505; that is, whether there is any unprocessed (unsupported) NDEF information. If it is determined that there is an NDEF message other than the NDEF message indicating permission to transmit power ("Yes" in S514), RX moves the processing to S515. Conversely, if it is determined that there is no NDEF message other than the NDEF message indicating permission to transmit power ("No" in S514), RX ends the processing.

[0100] In S515, RX processes the first NDEF information, in addition to the NDEF information indicating permission for power transmission. Figure 8Taking the NDEF information in the example, this process corresponds to processing NDEF information 701. In this example, RX displays a UI for accessing the service provided with TX on a display unit (not shown) provided in RX. The processing of S515 is the above-described processing based on the information content of the tag data [3].

[0101] Furthermore, not only are S511 and 509 connected to S514, but S512 and 513 are also connected to S514, although the paths of S512 and 513 are the paths determined by "No" in S503. Therefore, when processing follows the path determined by "No" at S503, S514 will inevitably result in "No" determination, and processing will end as is.

[0102] When the determination at S501 is "No", the process of RX not being placed on TX is performed. In this case, since this means that RX is not involved in S406, NFC tag detection processing is first performed at S516. This processing is the same as the processing in S406.

[0103] In S517, RX determines whether an NFC tag has been detected during the NFC tag detection process. This process is the same as in S407. When it is determined that an NFC tag has been detected ("Yes" in S517), RX moves the process to S518. On the other hand, when it is determined that no NFC tag has been detected ("No" in S517), RX ends the process. Furthermore, a determination similar to that in S504 is performed after S517 and before S518, but this is omitted here. When the determination is "No", RX ends the process.

[0104] In S518, RX, for example, performs processing related to the first NDEF information. Using Figure 8 Taking the NDEF information in the example, the processing target is NDEF information 701. In this case, the RX displays a UI on the display unit (not shown) provided in the RX for accessing the URL of the service provided with the TX. Furthermore, since the processing starting from S516 is unrelated to the power transmission processing, even if the RX initially reads NDEF information 703 in S518, it can be simply ignored.

[0105] <Processing of the entire system> Next, we will refer to Figure 7The sequence of operations for performing the above-described processes in this embodiment is described. The initial state is changed to a state where RX is not placed on TX. Furthermore, it is assumed that: an NFC tag that allows power transmission is built into or attached to TX, or an NFC tag is located around TX, and RX placed thereon can read data from the NFC tag. Furthermore, in this embodiment, an example with a permitted power value of 10 watts, a transmit power value of 12 watts, and a receive power value of 15 watts will be described.

[0106] When the RX detects that it has been placed on the TX, communication in the negotiation phase begins after exchanging identification and capability information, and the RX obtains NFC tag detection information from the TX. The RX performs NFC tag detection processing based on the obtained NFC tag detection information. At this point, the RX detects an NFC tag, but since the detected NFC tag is an NFC tag that allows power transmission, control is performed to continue power transmission processing. Subsequently, as described above, since the comparison of power values ​​shows that the permitted power value < the transmittable power value < the receiveable power value, the RX requests the permitted power value as the GP value.

[0107] When RX is placed on TX in F600, TX and RX perform communication in the Ping phase of the WPC standard, and RX detects that it has been placed on TX (F601 and S401). Subsequently, in F602, RX sends identification and capability information to TX according to the communication in the construction phase of the WPC standard (S402). Then, TX and RX begin communication in the negotiation phase of the WPC standard, and RX sends a Foreign Object Detection (FOD) status data packet of the WPC standard to TX in F603. Upon receiving the FOD status data packet, TX determines that no foreign object exists in this embodiment and sends an acknowledgment (ACK) in F604.

[0108] Subsequently, in F605, RX sends a Capability Information (CAP) notification request to TX using the WPC standard General Request (GRQ) packet. If the Capability Information Notification Request is received, TX sends a WPC standard CAP packet to RX in F606. Furthermore, the CAP packet may include a transmittable power value, i.e., negotiated load power.

[0109] Subsequently, in F607, RX sends a notification request for NFC tag detection information to TX using the WPC standard GRQ data packet. If the notification request for NFC tag detection information is received, TX sends the NFC tag detection information to RX in F608. Alternatively, NFC tag detection information can be sent using data packets defined in the WPC standard. Furthermore, the NFC tag detection information may include information such as whether TX has NFC tag detection capability, whether NFC tag detection has been performed, and whether an NFC tag has been detected as a result of NFC tag detection. The case where TX does not have NFC tag detection capability in this embodiment will be described below.

[0110] If RX receives NFC tag detection information (S403), since TX does not have NFC tag detection functionality, it determines (decides) to perform NFC tag detection processing ("Yes" in S404). Furthermore, in F609, RX sends a pause request to TX using a WPC standard GRQ data packet (S405). Here, the pause request can include the time during which TX will stop the processing. The pause request can be a WPC standard EPT data packet, but it can also use different data packets. Upon receiving the pause request, TX pauses power transmission processing in F610.

[0111] If the NFC tag detection process begins, RX reads the NFC tag in F611 (S406) and obtains the power transmission license tag data from the NFC tag in F612 ("Yes" in both S407 and S408). Subsequently, in F613, RX primarily stores the licensed power value as information included in the power transmission license tag data (S409). Besides the licensed power value, the information stored by RX can also be the Qi standard version in the WPC standard, information about the NFC version supported by the NFC tag, and the version of the protection function. In F614, TX resumes the power transmission process. Since the processes from F615 to F620 are similar to those from F601 to F606, their descriptions will be omitted.

[0112] In F621, RX performs processing to determine the required power value (S412). RX detects an NFC tag that allows power transmission ("Yes" in S502, S503, and S504). Because the permitted power value is currently less than the transmittable power value ("Yes" in S507) and less than the receiveable power value ("Yes" in S508), RX determines the required power value of GP as the permitted power value (S511). Furthermore, in F622, RX performs processing on the first tag data other than the power transmission permitted tag data (S515).

[0113] Subsequently, in F623, RX stores the required power value of GP in a WPC standard Request-Specific-Q (SRQ) packet and sends the required power to TX. When the SRQ packet as a request for GP is received, TX receives the required power because it is less than or equal to its own sendable power value and stores it as the GP value in F624. Subsequently, in F625, TX sends an ACK to RX as an acceptance response. If the ACK is received, RX stores the required power value as the GP value in F626, as if the required power value sent in F623 had been accepted (S413).

[0114] Subsequently, in F627, RX sends a negotiation phase end notification to TX in the SRQ packet of the WPC standard. If the negotiation phase end notification is received, TX sends an ACK to RX in F628, i.e., accepts the response. Then, RX and TX calculate the power loss baseline value for foreign object detection based on the determined GP value (F629 and S414) and begin power transmission and reception processing (F630 and S415).

[0115] As described above, when reading multiple NDEF messages, the RX detects NFC tags that allow power transmission and confirms the existence of such NDEF messages based on the read NDEF information. In this case, if NDEF messages allow power transmission, the RX requests the minimum of the following: the power value that the power transmitting device can transmit, the power value that the power receiving device can receive, and the power value permitted by the NFC tag, as the GP value. Therefore, even when an NFC tag capable of transmitting power is located on the TX, power transmission and reception can continue while suppressing damage and heat generation to the NFC tag, achieving a safer and more efficient wireless power transmission system. Furthermore, by processing NDEF messages other than those allowing power transmission, the RX can access services and functions intended to be provided to the RX by the TX. As described above, the RX can perform appropriate processing when reading NDEF information from NFC tags, especially multiple NDEF messages.

[0116] Although in this embodiment, Figure 5 The description of NDEF information processing in S515 and S518 describes the RX processing a first NDEF information in addition to the NDEF information that allows power transmission, but the invention is not limited thereto. For example, the RX can also process a second or subsequent predetermined NDEF information (a specific number of predetermined NDEF information). Alternatively, the RX can process all target NDEF information or multiple selected NDEF information sequentially. In this case, even if the RX reads NDEF information 703 in S518, it can simply be ignored.

[0117] [Second Embodiment] The second embodiment of this disclosure will now be described in detail with reference to the accompanying drawings. In the second embodiment, descriptions of structures and operations similar to those of the first embodiment will be omitted or simplified.

[0118] Figure 9 This is a diagram illustrating an example of the construction of a wireless power transmission system according to this embodiment. Because the power receiving device 101, the power transmitting device 102, and the NFC tag 103 are... Figure 1 Those that are the same as those in the text will be omitted from the description. In this embodiment, the power receiving device 101 is referred to as RX, and the power transmitting device 102 is referred to as TX.

[0119] NFC tag 804 is a different NFC tag from NFC tag 103. Figure 9 This illustrates a scenario where multiple NFC tags are present during RX tag detection. NFC tag 804 is, for example, an NFC tag accidentally placed between RX and TX, and can be, for example, an NFC card supporting touch payment, a keychain-type NFC tag, etc. In this embodiment, as... Figure 9 As shown, the control of the RX will be described from the perspective of the RX in a wireless power transmission environment between the RX and TX, for cases where multiple NFC tags are present.

[0120] Figure 2 The structure of RX in Figure 3 The construction of TX in and Figure 4 The processes performed by the RX during wireless power transmission are the same as those in the first embodiment, and therefore will not be described again here.

[0121] Figure 10 This is in this embodiment Figure 4 The flowchart shown is a detailed flowchart of the NFC tag detection process performed in S406 in the wireless power transmission flowchart.

[0122] In S901, after processing begins, the RX sets the type of the NFC tag to be detected. Multiple NFC tags exist, including types A, B, and F, and the types of tags not yet detected are also set. In S902, the RX performs NFC tag detection. For example, this detection can be performed using a reader / writer function based on the NFC standard. In S903, the RX determines whether the NFC tag detection was successful. When it is determined that the NFC tag detection was successful ("Yes" in S903), the RX moves the processing to S904. Conversely, when it is determined that the RX determined the NFC tag detection failed ("No" in S903), the processing ends.

[0123] In S904, RX maintains the NDEF information read from the NFC tag. RX manages the read information of each NFC tag that has been detected. In S905, RX determines whether detection processing has been performed on all types of NFC tags. This process is used to determine whether detection has been performed on all types (e.g., type A, type B, and type F). When it is determined that all types have been detected ("Yes" in S905), RX ends the process. On the other hand, when it is determined that not all types have been detected ("No" in S905), RX returns to S901 and performs NFC tag detection processing on the next type.

[0124] The above is in this embodiment. Figure 4 NFC tag detection processing is performed during wireless power transmission. RX can appropriately determine the processing procedure even when multiple NFC tags are present by performing detection processing on all NFC tag types. Figure 9 As shown. For example, when NFC tag 103 and NFC tag 804 are NFC tags of different types, NDEF information can be read from all tags. Furthermore, when NFC tag 103 and NFC tag 804 are NFC tags of the same type, RX can determine the presence of at least one NFC tag by determining NFC tag detection failure in S903.

[0125] When two or more of the same NFC tag types exist, the RX can include an NFC communication unit capable of detecting them individually. In this case, the RX only needs to... Figure 10 The flowchart shown detects all NFC tags and reads the NDEF information stored in each NFC tag.

[0126] Figure 11 and Figure 12 It is mainly shown in Figure 4 The flowchart of the required power value determination process performed by RX in S412. Based on Figure 5 and Figure 6 The flowchart, such as Figure 9 As shown, from the perspective of RX, Figure 11 and Figure 12 The flowchart is expanded to correspond to the case where there are multiple NFC tags. Therefore, the ellipsis and Figure 5 and Figure 6 Description of overlapping processing steps.

[0127] S1001 to S1004 are the same as S501 to S504. In S1005, RX confirms all NDEF information for each NFC tag. Because RX is in Figure 10The flowchart process performs NFC tag detection for all NFC types and maintains NDEF information for each detected NFC tag, thus confirming the NDEF information of each NFC tag. In this embodiment, RX confirms the NDEF information read from NFC tag 103 and NFC tag 804.

[0128] Here, the NDEF information held by NFC tag 103 is... Figure 8 The same as shown. Meanwhile, the NDEF information held by the NFC tag 804 is as follows: Figure 14 As shown. For example, an NFC tag supporting touch payment is assumed to be NFC tag 804. The NFC tag supporting touch payment has, for example, payment information in NDEF information 1201 and information allowing power transmission (power transmission license tag data) in NDEF information 1202. The NDEF information of NFC tag 804 is not limited to... Figure 14 The information shown can be configured and various settings can be configured based on the application of the NFC tag 804.

[0129] In S1006, RX determines whether all NFC tags are power-transmitting tags. When it is determined that all detected NFC tags are power-transmitting NFC tags ("Yes" in S1006), RX moves the process to S1007. On the other hand, when it is determined that at least one of the detected NFC tags is not a power-transmitting NFC tag ("No" in S1006), RX determines the restricted power value as the desired power value (S1010) and ends the desired power value determination process.

[0130] In S1007, RX sets the minimum permitted power value from the permitted power values ​​in the information allowing power transmission of all NFC tags as the permitted power value to be used in subsequent processing. In this embodiment, this means using the permitted power value (e.g., 8W) in NDEF information 1202.

[0131] The subsequent processing from S1008 to S1015 is the same as that from S507 to S514. Here, the “permitted power value” in S1008, S1009 and S1012 refers to the permitted power value selected in S1007.

[0132] In S1016, RX processes the first NDEF information in the NDEF information, excluding the NDEF information that allows power transmission. When multiple NFC tags are detected, if... Figure 10In the flowchart, if NFC tag 103 is detected before NFC tag 804, then the processing of the first NDEF information other than the NDEF information that allows power transmission is the processing of NDEF information 701. In other words, this is the processing of the UI used to display the URL for accessing the services provided with TX. On the other hand, when NFC tag 804 is detected before NFC tag 103, RX activates the application for processing payment information 1201, as the processing of the first NDEF information other than the NDEF information that allows power transmission.

[0133] <System Flow> Next, we will refer to Figure 13 This describes the sequence of operations used to perform the processes described above in this embodiment. Based on Figure 7 The operation sequence, such as Figure 9 As shown, from the perspective of RX, Figure 13 The flowchart is expanded to correspond to the case where multiple NFC tags exist. Therefore, the description of overlap handling will be omitted.

[0134] F1100 to F1110 are the same as F600 to F610. F1111 to F1113 are basically the same as F611 to F613, and are cyclical processes performed on all NFC tags (S901 to S905).

[0135] F1114 is a process (S1007) for selecting the minimum permitted power value from the permitted power values ​​of NDEF information obtained from multiple NFC tags during the cyclic processing of F1111 to F1113. In this embodiment, NDEF information 703 and NDEF information 1202 are the processing targets, and NDEF information 1201 with 8W is selected. Subsequent processing from F1115 to F1131 is the same as F614 to F630.

[0136] In this embodiment, Figure 11 and Figure 12 The descriptions of S1016 and S1019 describe the processing beyond detection. Figure 10 The flowchart shows an example of the first NDEF information obtained beyond the NDEF information that allows power transmission, based on all tag types. However, the invention is not limited to this; the RX can also process, for example, a second predetermined NDEF information or subsequent predetermined NDEF information. Alternatively, control can be implemented to process all or more target NDEF information sequentially.

[0137] It can be performed only on tag data of a specific NFC tag. Figure 11 and Figure 12S1016 and S1019. For example, a specific NFC tag is an NFC tag associated with a power transmitting device. In this case, RX needs to obtain information about TX from the NFC tag. Figure 8 In the example shown, this corresponds to the NDEF information 702 of NFC tag 103. The RX is able to identify the presence of an NFC tag associated with a power transmitting device by verifying the device type (TX) information in the NDEF information 702. Furthermore, the RX can be controlled to sequentially process a first NDEF message or multiple second NDEF messages and subsequent NDEF messages (e.g., all second and subsequent NDEF messages) in addition to the NDEF message that allows power transmission within the NDEF information obtained from NFC tag 103.

[0138] [Other Embodiments] For example, in the first embodiment described above, the RX may not perform the processing in S515. The processing after "yes" in S501 is the processing under the condition that the RX is placed on the TX. Therefore, the RX can be controlled to only perform the processing of the NDEF information that allows power transmission in S505 and S506, without performing the processing of other NDEF information.

[0139] Similarly, in the second embodiment described above, the RX may not perform the processing in S1016. The processing after "yes" in S1001 is the processing under the condition that the RX is placed on the TX. Therefore, the RX can be controlled to perform only the processing of the NDEF information that allows power transmission in S1005 to S1007, without processing other NDEF information.

[0140] In the above embodiments, an NFC tag, which uses wireless communication as defined by the NFC standard, is used as an example of a wireless communication tag. However, other common radio frequency identifier (RFID) tags can also be used. In this case, the NFC tag can be replaced by an IC tag / card or an RF tag / card, etc.

[0141] although Figures 4 to 6 and Figures 10 to 12 The flowchart in the diagram shows processes performed by the RX, but these processes can also be performed by the power transmission equipment. In this case, besides Figure 3 In addition to the components of the TX shown, the power transmission device only needs to include an NFC communication unit similar to the NFC communication unit of the RX. The NFC communication unit serves as: a detection unit for detecting NFC tags and a reading unit for reading tag data from the detected NFC tags.

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

[0143] Furthermore, for example, power transmitting and receiving devices can be image input devices such as imaging devices (still cameras, video cameras, etc.) or scanners, or image output devices such as printers, copiers, or projectors. Additionally, they may be storage devices such as hard disk drives or memory devices, or information processing devices such as personal computers (PCs), smartphones, or tablets.

[0144] Furthermore, the power receiving device disclosed herein can also be an information terminal device. For example, an information terminal device has a display unit (shower) that displays information to a user and receives power supplied from a power receiving antenna. Additionally, the power received from the power receiving antenna is stored in a power storage unit (battery), and power is supplied from the battery to the display unit. In this case, the power receiving device may also have a communication unit for communicating with devices other than the power transmitting device. The communication unit may support communication standards such as NFC communication or fifth-generation mobile communication systems (5G).

[0145] Furthermore, the power receiving device disclosed herein can also be a vehicle, such as a car. For example, a car used as a power receiving device can receive power from a charger (power transmitting device) via a power transmitting antenna installed in a parking lot. Alternatively, a car used as a power receiving device can receive power from a charger (power transmitting device) via a power transmitting antenna embedded in the road. Such a car supplies the received power to a battery. The battery power can be supplied to a drive unit (motor or electrical unit) that drives the wheels, or it can be used to drive sensors for driving assistance or a communication unit for communicating with external devices. In other words, in this case, in addition to the wheels, the power receiving device can also include a battery, a motor or sensors driven using the received power, and a communication unit for communicating with devices other than the power transmitting device. Furthermore, the power receiving device can have a housing unit for accommodating a person. For example, the sensor is a sensor used to measure distances between vehicles or distances to other obstacles. The communication unit can be compatible with, for example, a Global Positioning System (GPS). Furthermore, the communication unit can be compatible with communication standards such as fifth-generation mobile communication systems (5G). Additionally, the vehicle can be a bicycle or a motorcycle.

[0146] Furthermore, the power receiving device disclosed herein can also be a power tool, a household appliance, etc. In addition to a battery, these power receiving devices may also include a motor driven by the received power stored in the battery. Furthermore, these devices may have a notification unit for informing the user of the remaining battery power, etc. Additionally, these devices may have a communication unit for communicating with devices other than the power transmitting device. The communication unit may be compatible with communication standards such as NFC or fifth-generation mobile communication systems (5G).

[0147] Furthermore, the power transmitting device disclosed herein can be an on-board charger that transmits power to mobile information terminal devices (such as smartphones and tablets) that support wireless power transmission within a vehicle (automobile). This on-board charger can be located anywhere within the vehicle. For example, it can be installed on the vehicle's console, or on the dashboard (instrument panel or instrument cluster), between passenger seats, on the ceiling, or on a door. However, it is best to avoid installation in locations that interfere with driving. Moreover, while examples of on-board chargers have been described using power transmitting devices, such chargers are not limited to those installed in vehicles; they can also be installed on transportation vehicles such as trains, airplanes, and ships. In such cases, the charger can also be installed between passenger seats, on the ceiling, or on a door.

[0148] In addition, vehicles equipped with onboard chargers (such as automobiles) can be used as power transmitting devices. In this case, the power transmitting device has wheels and a battery, and uses the battery to supply power to the power receiving device via a power transmitting circuit unit and a power transmitting antenna.

[0149] This disclosure can also be implemented in a process in which a program implementing one or more functions of the above embodiments is provided to a system or device via a network or storage medium, and one or more processors in the computer of the system or device read and execute the program. Furthermore, this disclosure can be implemented by circuitry (e.g., an ASIC) implementing one or more functions.

[0150] Furthermore, some of the processes described with reference to the flowcharts in this disclosure can be implemented in hardware. For example, it is only necessary to use a pre-defined compiler to automatically generate dedicated circuitry on the FPGA based on the program used to implement each step. Additionally, gate array circuitry can be formed and implemented in hardware, just like an FPGA.

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

[0152] (Cross-reference to related applications) This application claims the benefit of Japanese Patent Application No. 2023-139196, filed on August 29, 2023. The entire contents of the aforementioned Japanese patent application are incorporated herein by reference.

Claims

1. A power receiving device for wirelessly receiving power from a power transmitting device, the power receiving device comprising: The detection unit is configured to detect near field communication (NFC) tags; The reading unit is configured to read one or more tag data from the detected NFC tag; as well as The processing unit is configured to perform processing by selecting a processing method associated with one or more tag data based on whether the reading unit has read the tag data in a state where the power receiving device is able to receive power from the power transmitting device.

2. The power receiving device according to claim 1, wherein, When the reading unit has read the tag data while the power receiving device is able to receive power, the processing unit confirms whether there is power transmission permission tag data indicating that power transmission is permitted in one or more tag data entries.

3. The power receiving device according to claim 2, wherein, If the power transmission license tag data exists, the processing unit determines, based on the power transmission license tag data, the power information indicating the required power to be transmitted by the power transmission device during negotiation with the power transmission device.

4. The power receiving device according to claim 3, further comprising: The computing unit is configured to calculate the receivable power value based on the operating state of the power receiving device. The processing unit determines the power information based on the power transmission license tag data and the receivable power value.

5. The power receiving device according to claim 2, wherein, In the absence of the power transmission license tag data, the processing unit determines the power information regarding the power that is limited to a predetermined value or less in negotiations with the power transmission equipment.

6. The power receiving device according to claim 3, wherein, The processing unit also performs processing related to one or more tag data in addition to the power transmission license tag data.

7. The power receiving device according to claim 6, wherein, The processing unit performs processing related to a specific number of tag data in one or more tag data sets, in addition to the power transmission license tag data.

8. The power receiving device according to claim 7, wherein, The specific number of tag data is the first tag data.

9. The power receiving device according to claim 6, wherein, The processing unit performs sequential processing related to multiple tag data other than the power transmission license tag data, or processing related to one or more tag data selected from the multiple tag data.

10. The power receiving device according to claim 2, wherein, The power transmission license tag data includes the power value that the NFC tag allows for power transmission.

11. The power receiving device according to claim 1, wherein, When the detection unit detects multiple NFC tags, the reading unit reads one or more tag data entries from each of the NFC tags.

12. The power receiving device according to claim 11, wherein, The processing unit performs processing related to each tag data in the one or more tag data.

13. The power receiving device according to claim 11, wherein, The processing unit verifies whether there is power transmission license tag data indicating permission to transmit power among one or more tag data read from all NFC tags.

14. The power receiving device according to claim 13, further comprising: The computing unit is configured to calculate the receivable power value based on the operating state of the power receiving device. Where all NFC tags have the power transmission license tag data, the processing unit determines the power information of the required power to be transmitted by the power transmitting device in negotiation with the power transmitting device based on the minimum power value allowed to be transmitted and the receivable power value of each NFC tag, wherein the minimum value and the receivable power value are included in the power transmission license tag data.

15. The power receiving device according to claim 13, wherein, If at least one of the NFC tags does not have the power transmission license tag data, the processing unit determines the power information regarding the power that is limited to a predetermined value or less in negotiation with the power transmission device.

16. The power receiving device according to claim 13, wherein, The processing unit also performs processing related to one or more tag data in addition to the power transmission license tag data.

17. The power receiving device according to claim 16, wherein, The processing unit performs processing related to one or more tag data other than the power transmission license tag data read from a specific NFC tag among all NFC tags.

18. The power receiving device according to claim 17, wherein, The specific NFC tag is an NFC tag associated with the power transmitting device.

19. The power receiving device according to claim 2 or 13, wherein, The processing unit prevents processing related to tag data other than the power transmission license tag data.

20. The power receiving device according to claim 1, wherein, When the power receiving device cannot receive power from the power transmitting device, the processing unit reads the tag data, and performs processing related to at least one piece of read tag data.

21. The power receiving device according to claim 20, wherein, The processing unit performs processing related to the tag data with a specific number.

22. A power transmitting device for wirelessly transmitting power to a power receiving device, the power transmitting device comprising: The detection unit is configured to detect near field communication (NFC) tags; The reading unit is configured to read one or more tag data from the detected NFC tag; as well as The processing unit is configured to perform processing by selecting a processing method related to one or more tag data based on whether the reading unit has read the tag data in a state where the power receiving device is able to receive power from the power transmitting device.

23. A method performed by a power receiving device, the power receiving device being configured to wirelessly receive power from a power transmitting device, the method comprising: The detection process involves detecting Near Field Communication (NFC) tags. The reading step involves reading one or more tag data entries from the detected NFC tag; as well as The processing steps involve selecting a processing method related to one or more tag data based on whether the tag data has been read in the reading step, depending on whether the power receiving device is able to receive power from the power transmitting device.

24. A method performed by a power transmitting device, the power transmitting device being configured to wirelessly transmit power to a power receiving device, the method comprising: The detection process involves detecting Near Field Communication (NFC) tags. The reading step involves reading one or more tag data entries from the detected NFC tag; as well as The processing steps involve selecting a processing method related to one or more tag data based on whether the tag data has been read in the reading step, depending on whether the power receiving device is able to receive power from the power transmitting device.

25. A program that causes a computer to perform the method according to claim 23.

26. A program that causes a computer to perform the method according to claim 24.

Images