Device, device control method and program

Abstract

To provide technology that makes it possible to perform appropriate processing when a device reads information from an NFC tag of a compatible product.SOLUTION: A device 101 is usable in combination with a compatible product 201. The device detects that the device is combined with the compatible product, detects a near field communication (NFC) tag in the compatible product, and reads one or more pieces of tag information from the detected NFC tag. The device then executes processing by switching a processing method related to the read one or more pieces of tag information depending on whether a predetermined condition is satisfied or not.SELECTED DRAWING: Figure 7

Description

[Technical Field]

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

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

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

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

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-134796 Summary of the Invention [Problem to be solved by the invention]

[0006] When a compatible product for a device, such as an accessory that can be used in combination with the device, has an NFC tag, it is desirable for the device not only to simply read the information contained in the NFC tag, but also to perform appropriate processing on the NFC tag depending on the situation.

[0007] The present disclosure provides a technology that can perform appropriate processing when information is read from an NFC tag of a compatible product. [Means for solving the problem]

[0008] A device according to one embodiment of the present disclosure includes: Can be combined with the device A device that can be used in combination with a counterpart, The device is a detection means for detecting that the device and the compatible product have been combined, and detecting an NFC (Near Field Communication) tag of the compatible product; Including authentication information for authenticating the corresponding product A reading means for reading one or more pieces of tag information from the NFC tag, and a .... Judgment is made, and depending on the judgment result, Processing regarding the one or more pieces of tag information Reasonand processing means for executing The processing includes an authentication process for the compatible product, and the predetermined conditions include a first condition and a second condition, the first condition being that the detection means detects that the device and the compatible product are combined, and the second condition being that the compatible product is authenticated by the authentication process. It is characterized by: [Effects of the Invention]

[0009] According to the present disclosure, when a device reads information from a compatible NFC tag, it can perform appropriate processing. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a system according to a first embodiment. [Figure 2] FIG. 10 is a diagram illustrating an example of the configuration of a system in which a compatible product is attached to a device. [Figure 3] FIG. 2 is a diagram illustrating an example of the configuration of a device. [Figure 4] FIG. 10 is a diagram illustrating a configuration example of a corresponding product. [Figure 5] 4 is a flowchart showing an outline of processing by a device in the first embodiment. [Figure 6] 6 is a flowchart showing details of the NFC tag detection / authentication flow process of FIG. 5. [Figure 7] 7 is a flowchart continuing from FIG. 6. [Figure 8] 7 is a flowchart showing details of the NFC tag detection process in FIG. 6. [Figure 9] FIG. 10 is a diagram showing NDEF information recorded on an NFC tag. [Figure 10] FIG. 3 is a sequence diagram showing the processing of the entire system of the first embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of the configuration of a system according to a second embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of the configuration of a system in which a compatible product is attached to a power receiving device. [Figure 13] FIG. 1 is a diagram illustrating an example of a system configuration in which a power receiving device is placed on a power transmitting device. [Figure 14] FIG. 2 illustrates an example of the configuration of a power receiving device. [Figure 15]FIG. 2 is a diagram illustrating an example of the configuration of a power transmission device. [Figure 16] 10 is a flowchart showing an outline of processing performed by a power receiving device in a second embodiment. [Figure 17] 10 is a flowchart illustrating details of a process of wireless power transmission by a power receiving device. [Figure 18] 10 is a flowchart illustrating a wireless power transmission pre-setting process. [Figure 19] FIG. 10 is a sequence diagram showing the processing of the entire system of the second embodiment. [Figure 20] FIG. 20 is a sequence diagram showing a continuation of FIG. 19. [Figure 21] 11 is a flowchart showing details of an NFC tag detection / authentication flow process in the third embodiment. [Figure 22] 10 is a flowchart illustrating details of a process of wireless power transmission by a power receiving device. [Figure 23] FIG. 11 is a sequence diagram showing the processing of the entire system of the third embodiment. [Figure 24] 13 is a flowchart showing details of a process of wireless power transmission by a power receiving device in a fourth embodiment. [Figure 25] 10 is a flowchart illustrating a required power selection process. [Figure 26] FIG. 2 is a sequence diagram showing the processing of the entire system. [Figure 27] 8 is a flowchart showing a modified example of the NFC tag detection / authentication flow process shown in FIGS. [Figure 28] 22 is a flowchart showing details of the NFC tag detection / authentication flow process shown in FIG. 21. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] First Embodiment [System Configuration] 1 is a diagram showing an example of the configuration of a system according to this embodiment. The system according to this embodiment includes a device 101 and a corresponding product 201 for the device 101. The device 101 is equipped with an NFC (Near Field Communication) function, and can use this function to operate in, for example, card emulation mode, enabling electronic money payment and the like. The device 101 also has an NFC function that enables it to perform NFC communication and read an NFC tag 202 by operating in a reader / writer mode. The device 101 has a built-in NFC antenna 102 for performing NFC communication, and the NFC antenna 102 is disposed along and near the surface of the housing of the device 101. When the NFC tag 202 approaches the surface of the device 101 in which the NFC antenna 102 is built, the device 101 operates in the reader / writer mode and can communicate with the NFC tag 202. The device 101 also has a built-in sensor 103 that is provided to detect that a compatible product 201 has been combined with the device 101.

[0013] Typically, combining a compatible item with a device means that the compatible item is attached (mounted) to the device. However, this is not limited to this, and it can also mean anything that generates one or more functions or effects, even if the device and the compatible item are not in physical contact with each other, for example, when the device and the compatible item are used simultaneously. "Effects" can also include human sensory effects, such as visual and auditory effects. In the following embodiments, a typical example of combining a corresponding product with a device will be an example in which the corresponding product is attached to the device.

[0014] FIG. 4 is a diagram showing an example of the configuration of a compliant product 201. Referring to FIGS. 1 and 4, an NFC tag 202 is mounted on the compliant product 201. The NFC tag 202 is an example of a device that operates without a battery and realizes short-range wireless communication. More specific examples include an NFC / RFID tag capable of NFC communication and an NFC communication device that operates in card emulation mode. If the compliant product 201 is an NFC communication device that operates in card emulation mode, it may be equipped with a control unit that controls communication and the entire compliant product 201. The compatible product 201 has a detectable portion 203. When the compatible product 201 is attached to or combined with the device 101, the device 101 detects the detectable portion 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the device 101. This is an example of a detection means for detecting that the device 101 and the compatible product 201 have been combined.

[0015] In the following description, a smartphone is used as an example of the device 101, and a cover or case for the device 101 is used as an example of the compatible product 201 for the device 101, but the present invention is not limited to this. The device 101 may be, for example, a camera, a tablet PC, a laptop, an automobile, a robot, a medical device, a printer, etc. The compatible product 201 is a compatible product for the device 101 listed above, and may be, for example, a battery, a camera, a smartphone, a tablet PC, a laptop, an automobile, a robot, a medical device, a printer, a gimbal, an attachment tool, etc. In the following description, a magnet is used as an example of the detected part 203 of the compatible product 201, and a magnetic sensor is used as an example of the sensor 103 of the device 101, but the present invention is not limited to this. For example, the sensor 103 may be an optical sensor, an acoustic sensor, a thermal sensor, or the like.

[0016] FIG. 2 is a diagram showing an example of the system configuration in a state in which a compatible product 201 is attached to a device 101. The compatible product 201 has a shape that covers the housing of the device 101, and is attached to the device 101. At this time, the NFC tag 202 of the compatible product 201 is arranged so as to overlap the area of ​​the NFC antenna 102 of the device 101. As a result, the device 101 can communicate with the NFC tag 202 by operating in reader / writer mode. Furthermore, the detectable unit 203 of the compatible product 201 is arranged near the sensor 103 of the device 101. As a result, the device 101 detects the detectable unit 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the device 101. The combination of the device 101 and the compatible product 201 being detected by the sensor 103 is an example of a first condition.

[0017] [Device and compatible product configuration] FIG. 3 is a diagram illustrating an example of the configuration of the device 101. As shown in FIG. The device 101 includes an NFC antenna 102 , a sensor 103 , a communication unit 304 , a control unit 305 , a memory 306 , a notification unit 307 , and an operation unit 308 .

[0018] The communication unit 304 and the NFC antenna 102 connected to it are a hardware module that realizes the NFC function. Specifically, it realizes a card emulation mode that acts as a contactless IC card, a reader / writer mode for reading the NFC tag 202, and a P2P mode for directly exchanging messages between NFC devices. For example, the card emulation mode can be used to enable electronic money payments, etc. The communication unit 304 and the control unit 305 are mainly an example of a reading unit that detects an NFC tag and reads one or more pieces of tag information from the detected NFC tag.

[0019] The sensor 103 is, for example, a magnetic sensor, and detects that the compatible product 201 has been combined with the device 101 by detecting the detected part 203, which is a magnet.

[0020] The control unit 305 controls the entire device 101. The control unit 305 performs control by, for example, executing a control program stored in the memory 306. The control unit 305 also stores information to be stored while various processes are being executed in the memory 306. The control unit 305 includes one or more processors, such as a CPU (Central Processing Unit) or an MPU (Micro-processing Unit). The control unit 305 may include a memory separate from the memory 306 that stores the control program, and may store information to be stored while various processes are being executed in the separate memory. The control unit 305 may be configured with hardware dedicated to a specific process, such as an application specific integrated circuit (ASIC), or may include an array circuit, such as a field programmable gate array (FPGA), compiled to execute a predetermined process.

[0021] In this embodiment, the control unit 305 is shown as a single component, but is not limited to this. For example, an NFC control unit that controls processing related to NFC communication may be configured separately from the control unit 305. When the control unit 305 is configured as multiple separate units, the respective control units are connected to each other via a communication interface, enabling data communication. In this case, the communication interface may be any interface that realizes data communication, such as I2C or GPIO.

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

[0023] The notification unit 307 notifies the user of information by any method, such as visually, audibly, or tactilely. For example, the notification unit 307 notifies the user of the status of the device 101. The notification unit 307 includes, for example, a liquid crystal display, an LED, a speaker, a vibration generating circuit, and / or other notification devices.

[0024] The operation unit 308 has a function of accepting operations from the user on the device 101. The operation unit 308 includes, for example, a button, a keyboard, a voice input device, a motion detection device, and / or other input devices. An example of the voice input device is a microphone. An example of the motion detection device is an acceleration sensor, a gyro sensor, or the like.

[0025] It should be noted that a device in which the notification unit 307 and the operation unit 308 are integrated, such as a touch panel, may be used.

[0026] [Device Processing] 5 is a flowchart showing an outline of processing by the device 101. This processing can be realized, for example, by the control unit 305 of the device 101 executing a program read from the memory 306. Note that at least a part of the following procedure may be realized by hardware. In this case, the hardware can be realized, for example, by using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as an FPGA from a program for realizing each processing step.

[0027] The control unit 305 and the program for processing are mainly an example of a processing means that switches the processing method for one or more pieces of tag information read from the NFC tag 202 and executes the processing depending on whether or not a predetermined condition is met.

[0028] The processing related to tag information means, for example, the following processing [1] to [3] performed by the device 101. [1] Checking for the presence of tag information [2] Processing based on the content of tag information [3] Processing related to power transmission using tag information (explained in the second embodiment and subsequent embodiments) The processing method means which process (one or more) among [1], [2], and [3] to execute (or not execute), and which tag data (one or more) among the multiple tag data for [2] to process. The processing method may also include the order in which the three processes [1], [2], and [3] are executed. As will be described in the second and subsequent embodiments, the processing related to power transmission in [3] also includes various setting processes for power transmission that are performed before power is actually transmitted from the power transmitting device.

[0029] In step S501, the device 101 starts a periodic NFC tag detection / authentication flow process. The periodic NFC tag detection / authentication flow starts, for example, at one of the following three times: (a) The timing when the user performs a predetermined operation via the operation unit 308 of the device 101 (b) Timing when device 101 is turned on (c) The timing when the sensor 103 detects that the compatible product 201 is attached to the device 101 The "predetermined operation" in (a) is an operation for executing an NFC tag detection / authentication flow or other operation.

[0030] In S502, the device 101 executes an NFC tag detection / authentication flow. When the device 101 detects the NFC tag 202 of the compatible product 201 and the NDEF information (tag information) of the NFC tag 202 contains authentication information, the device 101 executes authentication processing according to conditions described below.

[0031] In S503, the device 101 executes an action according to the authentication status of the compatible product. For example, if the compatible product 201 has been successfully authenticated, the action may be to perform a specific process in an application of the device (e.g., a smartphone) 101.

[0032] Another example of the above action will be described. For example, assume that device 101 is a camera and compatible product 201 is its battery. The battery's NFC tag 202 contains information about its power specifications, which the camera detects by executing the NFC tag detection / authentication flow. If the battery's power specifications match those of the camera, the camera authenticates the battery. If the battery authentication is not successful, the camera displays a message on its GUI (Graphical User Interface) that the battery does not meet the specifications and stops operation. This prevents the battery from overheating and the camera from malfunctioning.

[0033] Figures 6 and 7 are flowcharts showing details of the NFC tag detection / authentication flow (S502) in Figure 5. Figure 8 is a flowchart showing details of the NFC tag detection process (mainly S601 to S603) in Figure 6.

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

[0035] In S703, the device 101 determines whether or not the detection of the NFC tag 202 was successful. If the device 101 determines that the detection of the NFC tag 202 was successful (YES in S703), the device 101 stores the NDEF information read from the NFC tag 202 in S704. On the other hand, if the device 101 determines that the NFC tag detection failed (NO in S703), the device 101 ends the processing. When storing the NDEF information in S704, the device 101 manages information for each NFC tag that was detected.

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

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

[0038] Returning to the description of the flowchart in Figure 6, in S602, the device 101 determines whether or not an NFC tag has been detected in the NFC tag detection process of S601. If an NFC tag has not been detected (No in S602), the process ends. If the device 101 has detected an NFC tag (Yes in S602), the device 101 determines whether or not reading the NFC tag was successful in S603. If reading the NFC tag was not successful (No in S603), the process ends. If reading the NFC tag was successful (Yes in S603), the device 101 stores the NDEF information of all NFC tags that were successfully read in memory.

[0039] In S604, the device 101 checks all NDEF information detected from one NFC tag that has not yet been processed. Checking the NDEF information means analyzing the NDEF information 801 to 803 shown in Fig. 9. The NFC tag 202 of the compatible product 201 is assumed to be an NFC tag implemented by the provider of the compatible product 201, and has, as an example, three pieces of NDEF information.

[0040] The NDEF information 801 is information relating to the compatible product 201. It is assumed that the information includes information on the device type (for example, information indicating that the type of the compatible product 201 is a cover), manufacturer information, serial number, and the like. The NDEF information 802 is information relating to the authentication of the compatible product 201 (authentication information for authenticating the compatible product 201), and is assumed to be, for example, an authentication key. The NDEF information 803 is information that allows power transmission for the NFC tag 202 of the compatible product 201 (information indicating that power transmission is allowed), and is assumed to include the version of wireless power transmission, information regarding whether power transmission is allowed, and the allowed power value (e.g., 8 W). In this embodiment, "power transmission" refers mainly to power transmission for wireless charging of a smartphone (device 101). "Power transmission is allowed" means that power transmission is allowed as long as it is not damaging to the NFC tag 202, for example. The NDEF information is not limited to that shown in FIG. 9, and various information can be set depending on the intended use of the provider of the compatible product 201.

[0041] 7, in S605, the device 101 determines whether or not the NDEF information confirmed in S604 contains authentication information for the compatible product 201 (NDEF information 802 in FIG. 9). If there is no authentication information for the compatible product 201 (No in S605), the device 101 does not perform authentication processing and proceeds to S612. If there is authentication information for the compatible product 201 (Yes in S605), the device 101 determines in S606 whether or not the sensor 103 has detected that the compatible product 201 is attached to the device 101.

[0042] If attachment is not detected (No in S606), the device 101 transitions to a compatible product unauthenticated state in S607 and stores in memory the fact that the compatible product 201 is in an unauthenticated state. Then, the process proceeds to S612. The compatible product unauthenticated state means that authentication of the compatible product 201 has not been successful.

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

[0044] If it is detected that the compatible product 201 is attached to the device 101 (Yes in S606), the device 101 determines in S608 whether or not the device 101 is already in a compatible product authenticated state. The compatible product authenticated state means that the compatible product 201 has been successfully authenticated. The compatible product authenticated state is an example of the second condition. If the device 101 is in a compatible product authenticated state (Yes in S608), the device 101 does not perform authentication processing and proceeds to S612.

[0045] If the device 101 is not in the authenticated compatible product state (No in S608), in S609 the device 101 executes authentication processing for the compatible product 201. The device 101 performs authentication by processing at least the authentication information (NDEF information 802 (authentication key)) of the NDEF information in the NFC tag of the compatible product 201, and stores the result of the authentication processing. In S610, the device 101 determines whether the authentication processing for the compatible product was successful. If the authentication processing for the compatible product was successful (Yes in S610), the device 101 transitions to the authenticated compatible product state in S611, stores the fact that the compatible product is in the authenticated compatible product state in memory, and proceeds to S612. If the authentication processing for the compatible product was not successful (No in S610), the device 101 proceeds to S612 without transitioning to the authenticated product state.

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

[0047] In S612, the device 101 determines whether or not there is NDEF information other than authentication information in the NFC tag being processed. If there is no NDEF information other than authentication information (No in S612), the process proceeds to S614. If there is NDEF information other than authentication information (Yes in S612), the device 101 executes processing on the first NDEF information other than authentication information in S613. Using the NDEF information in FIG. 8 as an example, it is expected that the device 101 will read information on the device type, manufacturer information, and serial number of the compatible product 201 in response to processing the NDEF information 801. Thereafter, the process of the device 101 proceeds to S614. Note that the NDEF information is read from the NFC tag in order from the left side of FIG. 9. In other words, the NDEF information 801 is read first. Alternatively, when the NDEF information is stored in the NFC tag, it may be stored in association with an ID or number that identifies the NDEF information. In this case, the device 101 may read the NDEF information in the order of the IDs or numbers.

[0048] In S614, the device 101 determines whether or not an NFC tag other than the NFC tag processed in S604 has been detected. If an NFC tag other than the processed NFC tag has been detected (Yes in S614), the device 101 returns to S604 and executes the subsequent processing again on the one NFC tag other than the processed NFC tag. If the device 101 has not detected an NFC tag other than the processed NFC tag (No in S614), the device 101 ends the processing.

[0049] [System-wide processing] FIG. 10 is a sequence diagram showing the processing of the entire system when the above-mentioned processing is executed.

[0050] In F901, the device 101 starts a periodic NFC tag detection / authentication flow. Although not shown, the device 101 periodically executes the NFC tag detection / authentication flow at predetermined time intervals. In this example, it is assumed that after the periodic NFC tag detection / authentication flow starts, the compatible product 201 is attached to the device 101 (F902).

[0051] In F903, the device 101 executes an NFC tag detection / authentication flow, and reads the NFC tag of the compatible product 201 and performs authentication processing.

[0052] In F904, the device 101 acquires NDEF information related to authentication (authentication information (for example, an authentication key)) from the NFC tag of the compatible product 201.

[0053] In steps F905 to F909, the device 101 performs predetermined processing based on the authentication information acquired in step F904. That is, the device 101 executes authentication processing according to conditions, transitions the state of the compatible product 201, and stores the state (authenticated or unauthenticated) in memory, as shown in the flowcharts of FIGS.

[0054] In F910, the device 101 processes NDEF information other than the NDEF information related to the authentication of the compatible product 201, and if another NFC tag is detected, processes the other NFC tag.

[0055] In F911, the device 101 executes an action according to the authentication status of the compatible product 201.

[0056] For example, when using NFC technology to authenticate a compatible product attached to a device, it is desirable that the authentication be performed after the compatible product is attached to the device, and once successful, subsequent authentication is unnecessary unless the compatible product is removed from the device. However, if the conditions for performing the authentication process are not set appropriately, there is a risk that the authentication process will be performed multiple times even when authentication is not required. This could result in increased power consumption of the device and slower processing performance of other applications. In contrast, according to the present embodiment described above, once the device 101 has successfully authenticated the compatible product 201, it is possible to avoid performing the authentication process again in the next periodic NFC tag detection process. This makes it possible to avoid an increase in the power consumption of the device 101 and a decrease in the processing performance of other applications. Furthermore, if the compatible product 201 is removed from the device 101 after it has been successfully authenticated once, the state of the compatible product 201 can be returned to an unauthenticated compatible product state. Therefore, if the compatible product 201 is subsequently attached to the device 101 again, it is possible to perform the appropriate authentication process again. As described above, when the device 101 reads information from the NFC tag 202, it can perform appropriate processing depending on the situation.

[0057] Second Embodiment The second embodiment will be described in detail below with reference to the accompanying drawings. Further, duplicated descriptions of the same or similar configurations as those of the first embodiment will be omitted. In this embodiment, a power receiving device is applied as the device 101 in the first embodiment. The power receiving device is a device that can perform wireless power transmission using an electromagnetic induction method for contactless charging based on the WPC standard defined by the Wireless Power Consortium (WPC).

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

[0059] [System Configuration] 11 is a diagram showing an example of the configuration of a system according to this embodiment. This system is made up of a power receiving apparatus 111 as a device 101, a compatible product 201 for the power receiving apparatus 111, and a power transmitting apparatus 1001. In the following description, the power receiving apparatus may be referred to as RX and the power transmitting apparatus as TX.

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

[0061] 1, the RX111 has an NFC antenna 102 and a sensor 103. The RX111 also has a built-in receiving coil 104, which is disposed along and near the surface of the housing of the RX111. The RX111 can perform wireless power transmission based on the WPC standard with the TX1001 using the receiving coil 104.

[0062] When the RX111 is placed on the TX1001, the TX1001 transmits power wirelessly to the RX111 in accordance with the WPC standard. The TX1001 has a built-in power transmitting coil 1010 that can transmit power wirelessly to the RX111 in accordance with the WPC standard when the RX111 is placed on the TX1001, and the power transmitting coil 1010 is arranged along and near the surface of the housing of the TX1001.

[0063] In the following description, a magnet is used as an example of the detected part 203 of the compatible product 201, and a magnetic sensor is used as an example of the sensor 103 of the device 101, but the present invention is not limited to this.

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

[0065] Furthermore, when the compatible product 201 is attached to the RX111, the detectable part 203 of the compatible product 201 is disposed near the sensor 103 of the RX111. As a result, the RX111 detects the detectable part 203 using the sensor 103, thereby detecting that the compatible product 201 has been attached to the RX111. Furthermore, the power receiving coil 104 of the RX111 is disposed inside the detectable part 203, which is a circular magnet of the compatible product 201, when viewed from above. The relative arrangement of the detectable part 203 and the power receiving coil 104 is such that power can be received using MPP, which is expected to become the power profile of the WPC standard in the future, as will be described later. MPP is an abbreviation for Magnetic Power Profile.

[0066] Fig. 13 is a diagram showing an example of the system configuration in which the compatible product 201 is attached to the RX111 and the RX111 is placed on the TX1001. Fig. 13(A) is a plan view, and Fig. 13(B) is a schematic cross-sectional view. As shown in Figs. 13(A) and 13(B), the power transmitting coil 1010 of the TX1001 is arranged so as to overlap the power receiving coil 104 of the RX111 in a plan view. This allows the TX1001 to wirelessly transmit power to the RX111 in accordance with the WPC standard.

[0067] [Configuration of power receiving device, compatible product, and power transmitting device] 14 is a diagram showing an example of the configuration of the RX 111. The RX 111 has an NFC antenna 102, a sensor 103, a first communication unit 1304, a control unit 1305, and a memory 1306. The RX 111 also has a power receiving coil 104, a power receiving unit 1307, a second communication unit 1308, a detection unit 1309, a charging unit 1310, a battery 1311, an operation unit 1312, and a notification unit 1313.

[0068] The NFC antenna 102 and the first communication unit 1304 are hardware modules that realize the NFC function. Similar to the NFC antenna 102 and the communication unit 304 of the first embodiment, these realize the card emulation mode, the reader / writer mode, P2P, and the like.

[0069] The sensor 103, the control unit 1305, and the memory 1306 basically have the same functions as the NFC antenna 102, the sensor 103, the control unit 305, and the memory 306 described with reference to FIG.

[0070] Although the control unit 1305 is shown as a single component, it is not limited to this. For example, the WPC control unit that controls processing related to power reception from the TX 1001 may be configured separately from the control unit 1305. Alternatively, the NFC control unit that controls processing related to NFC communication may be configured separately from the control unit 1305. Furthermore, the WPC control unit and the NFC control unit may each be configured separately from the control unit 1305. A specific example of the hardware of the control unit 1305 is the same as the example of the hardware of the control unit 305 in FIG. 3, and therefore a description thereof will be omitted.

[0071] The second communication unit 1308 performs wireless power transmission communication based on the WPC standard with the communication unit 1405 (FIG. 15) of the TX1001. The second communication unit 1308 controls the power receiving unit 1307 to communicate with the TX1001. Specifically, the second communication unit 1308 demodulates the electromagnetic waves input from the power receiving coil 104 to acquire information transmitted from the TX1001, and performs load modulation on the electromagnetic waves to superimpose information to be transmitted to the TX1001 onto the electromagnetic waves. In other words, the communication performed by the second communication unit 1308 is superimposed on the electromagnetic waves transmitted from the power transmitting coil 1010 of the TX1001.

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

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

[0074] The charging unit 1310 charges the battery 1311 with power supplied from the power receiving unit 1307. The charging unit 1310 also starts or stops charging the battery 1311 based on the control of the control unit 1305, and further adjusts the power used to charge the battery 1311 based on the charging state of the battery 1311. When the power used by the charging unit 1310 changes, the power supplied from the power receiving unit 1307, i.e., the received power in the RX111, also changes accordingly. The charging unit 1310 shown here is a load in the RX111.

[0075] Mainly, the power receiving unit 1307 or the charging unit 1310 is an example of a power receiving unit that wirelessly receives power from a power transmitting device.

[0076] The battery 1311 supplies the entire RX 111 with power required for control of each part of the RX 111 by the control unit 1305, power reception, and communication. The battery 1311 also stores the power received via the power receiving coil 104.

[0077] The notification unit 1313 notifies the user of, for example, the charging state of the RX111 and information indicating the state of power transmission in the wireless power transmission system including the RX111 and the TX1001 as shown in Fig. 13. A specific hardware example of the notification unit 1313 is similar to that of the notification unit 307 in Fig. 3, and therefore a description thereof will be omitted.

[0078] The operation unit 1312 has a function of accepting operations from the user for the RX 111. A specific example of the hardware of the operation unit 1312 is similar to that of the operation unit 308 in Fig. 3, and therefore a description thereof will be omitted.

[0079] The configuration of the counterpart 201 of the RX111 of this embodiment is the same as that of the first embodiment, and therefore a description thereof will be omitted.

[0080] FIG. 15 is a diagram showing an example of the configuration of the TX 1001 of this embodiment. The TX 1001 includes a control unit 1401 , a power supply unit 1402 , a power transmission unit 1403 , a detection unit 1404 , a power transmission coil 1010 , a communication unit 1405 , a notification unit 1406 , an operation unit 1407 , and a memory 1408 .

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

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

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

[0084] The power transmitting unit 1403 converts the DC or AC power output from the power supply unit 1402 into AC frequency power in a frequency band used for wireless power transmission, and inputs the AC frequency power to the power transmitting coil 1010 to generate electromagnetic waves for receiving power by the RX 111. The frequency of the AC power generated by the power transmitting unit 1403 is, for example, about several hundred kHz (for example, 110 kHz to 205 kHz). Based on instructions from the control unit 1401, the power transmitting unit 1403 inputs AC frequency power to the power transmitting coil 1010 so that the power transmitting coil 1010 outputs electromagnetic waves for transmitting power to the RX 111. The power transmitting unit 1403 controls the intensity of the electromagnetic waves to be output by adjusting the voltage (power transmitting voltage) and / or current (power transmitting current) input to the power transmitting coil 1010. Increasing the power transmitting voltage or power transmitting current increases the intensity of the electromagnetic waves, and decreasing the power transmitting voltage or power transmitting current decreases the intensity of the electromagnetic waves. Based on instructions from the control unit 1401, the power transmitting unit 1403 also controls the output of AC frequency power so that power transmission from the power transmitting coil 1010 starts or stops.

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

[0086] The detection unit 1404 detects whether an object is placed on the TX1001 based on the WPC standard. Specifically, the detection unit 1404 detects whether an object is placed on the interface surface of the TX1001. For example, the detection unit 1404 detects at least one of the voltage value and the current value of the power transmitting coil 1010 when the power transmitting unit 1403 transmits an Analog Ping of the WPC standard via the power transmitting coil 1010. The detection unit 1404 may detect a change in impedance. Then, the detection unit 1404 may determine that an object is placed on the TX1001 when the voltage is below a predetermined voltage value or the current value exceeds a predetermined current value. Whether this object is the RX111 or another foreign object is determined based on the presence or absence of a predetermined response to the Digital Ping subsequently transmitted by the communication unit 1405. That is, if the TX1001 receives a predetermined response, the object is determined to be the RX111; otherwise, the object is determined to be an object other than the power receiving device.

[0087] The detection unit 1404 is an example of a state detection unit that detects a state in which the power receiving device can receive power from the power transmitting device. The condition that the RX 111 is in a state in which the TX 1001 can receive power is an example of a third condition.

[0088] The communication unit 1405 performs control communication with the RX111 based on the WPC standard as described above. The communication unit 1405 modulates the electromagnetic waves output from the power transmitting coil 1010 and transmits information to the RX111 to perform communication. The communication unit 1405 also demodulates the electromagnetic waves output from the power transmitting coil 1010 and modulated by the RX111 to acquire information transmitted by the RX111. That is, the communication performed by the communication unit 1405 is superimposed on the electromagnetic waves transmitted from the power transmitting coil 1010. The communication unit 1405 also performs NFC communication and detects the NFC tag of the device to which power is transmitted. Note that the communication unit 1405 may be realized by a single piece of hardware, with a module for performing control communication based on the WPC standard and a module for performing NFC communication, or each may be realized by separate pieces of hardware.

[0089] The notification unit 1406 notifies the user of information by any method such as visually, audibly, tactilely, etc. The notification unit 1406 notifies the user of, for example, the charging state of the TX 1001 or information indicating the state of power transmission in a wireless power transmission system including the TX 1001 and the RX 111 as shown in Fig. 13. A specific example of the hardware of the notification unit 1406 is similar to that of the notification unit 307 in Fig. 3, and therefore a description thereof will be omitted.

[0090] The operation unit 1407 has a function of accepting operations from the user for the TX 1001. A specific example of the hardware of the operation unit 1407 is the same as that of the operation unit 308 in Fig. 3, and therefore a description thereof will be omitted.

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

[0092] [Processing of power receiving devices] 16 is a flowchart showing an outline of the processing of the RX111. This processing can be implemented, for example, by the control unit 1305 of the RX111 executing a program read from the memory 1306. Note that at least part of the following procedure may be implemented by hardware. In this case, the hardware can be implemented, for example, by using a predetermined compiler to automatically generate a dedicated circuit using a gate array circuit such as an FPGA from a program for implementing each processing step.

[0093] The processing of RX 111 in S1501 and S1502 is similar to the processing of device 101 in S501 and S502 (FIG. 5) in the first embodiment. The start timing of S1501 is similar to the above (a) to (c) described in S501 in the first embodiment. The details of the process in S1502 are also similar to those in FIGS. 6 and 7 in the first embodiment.

[0094] In S1503, the RX111 executes wireless power transmission processing based on the WPC standard and receives power from the TX1001. Here, the RX111 executes wireless power transmission pre-setting processing and sets wireless power transmission according to the authentication status of the compatible product 201. The wireless power transmission pre-setting processing is an example of settings related to wireless power transmission processing. The wireless power transmission pre-setting processing will be abbreviated as pre-setting processing below. In this embodiment, as an example of the pre-setting process, a process of determining a power profile for wireless power transmission based on the WPC standard according to the authentication state of the compatible product 201 will be described in detail later.

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

[0096] In S1602, the RX 111 executes pre-setting processing when it detects that its own device has been placed on the TX 1001. The pre-setting processing is processing for setting wireless power transmission according to the authentication status of the compatible product.

[0097] 18 is a flowchart showing an example of presetting processing, illustrating processing for setting a power profile for wireless power transmission based on the WPC standard. The power profile is one of the standards in the WPC standard, and examples include BPP (Baseline Power Profile) and EPP (Extended Power Profile). The maximum power supply amount is 5 W for BPP and 15 W for EPP. In addition, the above-mentioned MPP is scheduled to be added in the future.

[0098] When the process starts, in S1701 the RX111 determines whether or not it has detected that a compatible product is attached to the RX111. Note that this determination process has already been performed in S606 (FIG. 7) in S1502, so that determination result can be used in S1701. If it has not detected that a compatible product is attached (No in S1701), in S1704 the RX111 sets BPP and EPP as the power profile of the WPC standard that the RX111 supports, saves this setting in memory 1306, and ends the process.

[0099] If the RX111 detects that a compatible product is attached (Yes in S1701), the process proceeds to S1702, where it determines whether the compatible product has been authenticated. This determination is made based on the information about the authentication state stored in the memory 1306 in S611 when the NFC tag detection / authentication flow was executed in S1502.

[0100] If the device is not in a compatible product certified state (No in S1702), the RX111 executes the above-mentioned process in S1704 and ends the process. If the device is in a compatible product certified state (Yes in S1702), the RX111 sets MPP as the power profile of the WPC standard that the device supports in S1703, saves this setting in the memory 1306, and ends the process.

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

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

[0103] However, this information is merely an example, and the identification information and capability information of the RX 111 may be replaced by other information or may include other information. For example, the identification information may be any other identification information that can identify the individual RX 111, such as a Wireless Power ID. Furthermore, the RX 111 may transmit the identification information and capability information by a method other than communication in the I&C phase of the WPC standard.

[0104] Here, RX111 includes information about the power profile of the WPC standard that it supports in either an ID packet, XID packet, or configuration data packet and notifies TX1001. Upon receiving this notification, TX1001 compares the information about the power profile of the WPC standard that RX111 supports with the power profiles of the WPC standard that TX1001 supports, and determines the power profile to use. For example, the TX1001 sets the priority of the power profiles to be used in advance, and selects and determines the power profile with the highest priority from among the power profiles supported by both the TX1001 and the RX111. For example, assume that the priorities of the power profiles to be used are set as follows: 1st: MPP, 2nd: EPP, 3rd: BPP. If the power profiles supported by both the TX1001 and the RX111 are MPP and BPP, then MPP is selected and determined as the power profile to be used. As another example, the RX111 may include information about the power profiles it supports, along with their priority, in an ID, XID, or configuration data packet and notify the TX1001. In this case, the TX1001 selects and determines the power profile with the highest priority among the power profiles supported by both the TX1001 and RX111 that it has received notification of from the RX111.

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

[0106] After determining the GP, the RX111 starts communication in the calibration phase defined in the WPC standard in S1605. In the calibration phase, the RX111 transmits information about a predetermined received power value to the TX1001 so that the TX can derive the relationship between the transmitted power and the received power in a state without a foreign object. Here, the information about the predetermined received power value includes the received power value in a light load state and the received power value in a maximum load state.

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

[0108] [System-wide processing] 19 and 20 are sequence diagrams showing the processing of the entire system. As an initial state, the RX111 is not placed on the TX1001 (it is not capable of receiving power). The processing of F1801 to F1810 by the RX111 is the same as F901 to F910 by the device 101 in the first embodiment (FIG. 10), and therefore a description thereof will be omitted.

[0109] In this example flowchart, it is assumed that RX111 is mounted on TX1001 in F1811. When the RX111 is placed on the TX1001 at F1811, the TX1001 and RX111 execute communication in the Ping phase of the WPC standard at F1812, causing the TX1001 to detect at F1813 that the RX101 has been placed on its own device. Also, at F1814, the RX101 detects that its own device has been placed on the TX1001. After that, at F1815, the RX111 executes the pre-setting process as shown in the flowchart in Figure 18, and sets the power profile of the WPC standard that the RX111 supports.

[0110] The RX111 transmits identification information and capability information to the TX1001 through communication in the I&C phase of the WPC standard (not shown). In the I&C phase, at F1816, the RX111 notifies the TX1001 of information about the power profile of the WPC standard that the RX111 supports. At F1817, the TX1001 determines the power profile to use based on information about the power profile of the WPC standard that the RX111 supports and information about the power profile of the WPC standard that the TX1001 supports. At F1818, the RX111 requests information about the power profile to use from the TX1001. This request can be realized by sending a General Request Packet to the TX1001. At F1819, the TX1001 responds to the request from the RX111 for information about the power profile to use and notifies the RX111 of the power profile to use. The TX1001 can notify the RX111 of the power profile to be used by transmitting a Power Transmitter Identification Packet (TX ID Packet) to the RX111.

[0111] At F1820 to F1822, the TX1001 and RX111 communicate in the negotiation phase of the WPC standard, then proceed to the power transfer phase and start power transmission and reception processing. When the battery is fully charged, at F1823 the RX111 sends an end power transfer packet (EPT packet) to the TX1001 requesting that power transmission be stopped. Upon receiving the EPT packet, the TX1001 stops power transmission.

[0112] According to the present embodiment described above, once the RX111 has successfully authenticated the compatible product 201, it is possible to avoid performing the authentication process again in the next periodic NFC tag detection process. This makes it possible to avoid an increase in power consumption of the RX111 and a decrease in the processing performance of other applications. Furthermore, if the compatible product 201 is removed from the RX111 after it has been successfully authenticated once, the state of the compatible product 201 can be returned to an unauthenticated compatible product state. Therefore, if the compatible product 201 is subsequently attached to the RX111 again, it is possible to perform the appropriate authentication process again. Furthermore, the RX111 can switch the power profile of the WPC standard to be used depending on the certification status of the compatible product 201. For example, it is possible to make it possible to use MPP as the power profile only when the compatible product 201 is attached to the RX111 and has been certified.

[0113] <Third embodiment> The second embodiment will be described in detail below with reference to the accompanying drawings. Further, redundant explanations of configurations that are the same as or similar to those of the first and second embodiments will be omitted. In this embodiment, as in the second embodiment, a power receiving device is applied as the device 101 in the first embodiment. The system configuration example of this embodiment, and the configurations of the power receiving device (RX111), compatible product 201, and power transmitting device (TX1001) are the same as those of the second embodiment. Therefore, explanations will be omitted.

[0114] [Processing of power receiving devices] The outline of the processing flow of the RX 111 is shown in FIG. 16, similar to the second embodiment. In this embodiment, a regular NFC tag detection / authentication flow is executed at an initial stage (F2101 in FIG. 23 described later), and thereafter, when the compatible product 201 is attached to the RX111, the attachment is detected (F2102 in FIG. 23). These points are the same as in the second embodiment. However, in this embodiment, after the attachment of the compatible product 201 is detected, the NFC tag detection / authentication flow is not executed until the RX111 is placed on the TX1001. The NFC tag detection / authentication flow is executed after the RX111 is placed on the TX1001 (S1502, S2002 in FIG. 22 described later, F2107 in FIG. 23). In other words, in this embodiment, the NFC tag detection / authentication flow is executed based on the fact that the RX111 is placed on the TX1001. Thereafter, the RX111 starts processing for wireless power transmission based on the WPC standard, that is, processing for receiving power from the TX1001 (S1503, S2003 and subsequent steps in FIG. 22).

[0115] Fig. 21 is a flowchart showing details of the processing of the NFC tag detection / authentication flow (S1502) in Fig. 16. As in the first and second embodiments, the processing from S1901 to S1904 is the same as the processing from S601 to S604 shown in Fig. 6, and therefore a description thereof will be omitted.

[0116] In S1905, the RX 111 determines whether or not the NDEF information confirmed in S604 contains information relating to the authentication of the compatible product 201 (NDEF information 802 in FIG. 9, that is, authentication information).

[0117] If there is no authentication information for the compatible product 201 (No in S1905), the RX111 proceeds to S612 and does not perform authentication processing. If there is authentication information for the compatible product 201 (Yes in S1905), the RX111 determines in S1906 whether or not it has detected that the RX111 has been placed on the TX1001.

[0118] If not detected (No in S1906), the RX111 proceeds to S612 and does not perform authentication processing. If the RX111 detects that it has been placed on the TX1001 (Yes in S1906), the RX111 determines in S1907 whether the sensor 103 has detected that a compatible product is attached to the RX111.

[0119] If it has not been detected (No in S1907), in S1908 the RX111 transitions to a compatible product unauthenticated state and stores the fact that it is in the compatible product unauthenticated state in the memory 1306. Then, the process proceeds to S612. The compatible product unauthenticated state means that authentication of the compatible product 201 has not been successful. This makes it possible to return the state of the compatible product 201 to the compatible product unauthenticated state, for example, if the compatible product is removed from the RX111 after it has been successfully authenticated. Therefore, if the compatible product 201 is subsequently attached to the RX111 again, appropriate authentication processing can be executed again.

[0120] If it is detected that the compatible product 201 is attached to the RX 111 (Yes in S1907), the RX 111 proceeds to S1909. The subsequent processing is the same as in the first and second embodiments, and therefore a description thereof will be omitted.

[0121] Fig. 22 is a flowchart showing details of the wireless power transmission process of the RX111 based on the WPC standard in S1503 of Fig. 16 in this embodiment. S1503 in Fig. 16 means that the power transmission process from the TX1001 (firstly the pre-setting process) is started. This embodiment differs from the second embodiment in that after the RX111 is placed on the TX1001 (S2001), an NFC tag detection / authentication flow is executed (S1502, S2002) before the pre-setting process (S2003). The process from S2003 onwards is the same as S1602 of Fig. 17, and therefore a description thereof will be omitted.

[0122] [System-wide processing] Fig. 23 is a sequence diagram showing the processing of the entire system. As an initial state, it is assumed that the RX111 is not placed on the TX1001 (it is not capable of receiving power). F2101 and F2102 are the same as F1801 and F1802 in Fig. 19, and therefore their description will be omitted.

[0123] In this embodiment, it is assumed that the RX111 is mounted on the TX1001 at F2103. When the RX111 is mounted on the TX1001 at F2103, the TX1001 and RX111 execute communication in the Ping phase of the WPC standard at F2104, and the TX1001 detects at F2105 that the RX101 has been mounted on its own device. Furthermore, the RX101 detects at F2106 that its own device has been mounted on the TX1001.

[0124] F2107 to F2115 are similar to F1803 to F1810 and F1815 (FIG. 19) in the second embodiment, and therefore their description will be omitted. Furthermore, the processing after F2115 is similar to F1816 to F1823 (FIG. 20) in the second embodiment, and therefore their description will be omitted.

[0125] According to the present embodiment described above, even if the NFC tag detection / authentication flow is not executed before the RX 111 is placed on the TX 1001, it is executed after the RX 111 is placed on the TX 1001, and then the pre-setting process is executed, thereby achieving the same effects as the second embodiment.

[0126] <Fourth embodiment> The fourth embodiment will be described in detail below with reference to the accompanying drawings. Further, redundant explanations will be omitted for configurations that are the same as or similar to those of the first to third embodiments. In this embodiment, as in the second and third embodiments, a power receiving device is applied as the device 101 in the first embodiment. The configuration example of the system in this embodiment, and the configurations of the power receiving device (RX111), the compatible product 201, and the power transmitting device (TX1001) are the same as those in the second and third embodiments. Therefore, explanations will be omitted.

[0127] [Processing of power receiving devices] The outline of the processing flow of the RX111 is similar to that of the third embodiment (described with reference to Fig. 16), and therefore the description thereof will be omitted. This embodiment differs from the third embodiment in that, in the processing of wireless power transmission based on the WPC standard in S1503 of Fig. 16, a required power selection process is executed after a presetting process.

[0128] Fig. 24 is a flowchart showing details of the processing of wireless power transmission by RX111 based on the WPC standard in S1503 of Fig. 16. As described above, the processing other than the required power selection processing in S2204 (S2201 to S2203 and S2205 to S2208) is the same as in the third embodiment (Fig. 22), and therefore description thereof will be omitted.

[0129] In S2204, the RX111 executes the required power selection process, which selects the required power value for the GP based on the information of the compatible product 201 detected by the RX111, information from other NFC tags, and the specifications of the device itself.

[0130] FIG. 25 is a flowchart showing the required power selection process. In S2301, the RX 111 determines whether an NFC tag has been detected. This determination result is obtained by the NFC tag detection process (S602 in FIG. 6) executed in the NFC tag detection / authentication flow in S2202.

[0131] If an NFC tag is not detected (No in S2301), in S2308 the RX111 determines the receivable power value of the RX111 as the power value requested by the GP, stores it in the memory 1306, and ends the process. The receivable power value is the maximum power value that the RX111 can currently receive, and can be determined by the operating state of the RX111, such as the load, temperature, and / or the coupling coefficient of the transmitting and receiving coils, but is not limited to this. The control unit 1305 is an example of a calculation unit that calculates the receivable power value based on the operating state of the power receiving device.

[0132] If an NFC tag is detected (Yes in S2301), the RX 111 determines in S2302 whether or not the NFC tag has been successfully read. The result of this determination is obtained by the process of S603 executed in the NFC tag detection / authentication flow in S2202.

[0133] If the NFC tag was not successfully read (No in S2302), the RX111 executes S2308 described above and ends the process. If the NFC tag is successfully read (Yes in S2302), in S2303 the RX111 checks all of the NDEF information of the NFC tag. If multiple NFC tags are detected, the RX111 checks all of the NDEF information for each NFC tag. Note that if the NFC tag is successfully read (Yes in S603), the RX111 stores the NDEF information of all of the NFC tags that were successfully read in the memory 1306. In S2303, the RX111 simply checks this NDEF information. Checking the NDEF information means analyzing the NDEF information (for example, the NDEF information 801 to 803 shown in FIG. 9).

[0134] 9, the NDEF information 803 includes information that allows NFC tags to transmit power. In S2304, the RX 111 determines whether all NFC tags are allowed to transmit power. If the RX 111 determines that all NFC tags are allowed to transmit power (YES in S2304), in S2305, the RX 111 selects the smallest value from among the allowable power values ​​of all NFC tags and sets this as the allowable power value to be used in subsequent processing. This means that the allowable power value (e.g., 8 watts) in the NDEF information 803 is used.

[0135] On the other hand, if the RX111 determines that at least one of the detected NFC tags is not an NFC tag that is permitted to transmit power (NO in S2304), it determines the limit power value as the GP's required power value in S2309 and ends the required power selection process. The limit power value is a sufficiently small value that there is little possibility that the NFC tag will be damaged or generate heat even if the power transmission process is continued. The limit power value can be a predetermined value or less, for example, 5 watts or less, but is not limited to this.

[0136] In S2306, the RX111 determines whether the minimum allowable power value selected in S2305 is smaller than the receivable power value. If the allowable power value is smaller than the receivable power value (YES in S2306), the RX111 determines the allowable power value as the GP's requested power value in S2307 and ends the requested power selection process. On the other hand, if the allowable power value is equal to or greater than the receivable power value (NO in S2306), the RX111 executes S2308 described above and ends the requested power selection process.

[0137] [System-wide processing] 26 is a sequence diagram showing the processing of the entire system. In the initial state, the RX 111 is not mounted on the TX 1001. The processing up to F2416 is the same as the processing from F2101 to F2115 (FIG. 23) in the third embodiment, and therefore a description thereof will be omitted.

[0138] In F2416, the RX111 executes the required power selection process. As an example, let's assume that all NFC tags detected in the NFC tag detection / authentication flow (F2107) contain information that allows power transmission, and that the smallest allowable power value among those NFC tags is 8W. Also, let's assume that the allowable power value of the RX111 is 12W. In this case, in S2306 of Fig. 25, the result is Yes because the allowable power value is smaller than the allowable power value, and the allowable power value of 8W is selected as the GP's required power value in S2307.

[0139] The processing of the I&C phase from F2417 to F2420 is the same as in the second and third embodiments, and therefore a description thereof will be omitted.

[0140] Next, the RX111 and the TX1001 proceed to the Negotiation phase processing. In F2421, the RX111 transmits a Foreign Object Detection (FOD) Status data packet of the WPC standard to the TX1001. Upon receiving the FOD Status data packet, the TX1001 determines that no foreign object is present in this embodiment and transmits an ACK in F2422.

[0141] In F2423, the RX111 requests information about the transmittable power value from the TX1001. This request can be realized by sending a capability information notification request to the TX1001 using a General Request (GRQ) data packet of the WPC standard. When the TX1001 is requested to provide information about the transmittable power value, it notifies the RX111 of the information about the transmittable power value in F2424. This notification can be realized using a Power Transmitter Capabilities (CAP) data packet of the WPC standard. Note that the CAP data packet can include the transmittable power value of the TX1001, i.e., the Negotiable Load Power.

[0142] In F2425, the RX111 determines the GP's requested power value. The RX111 compares the requested power value selected in the requested power selection process in F2416 with the transmittable power value notified by the TX1001 in F2424, and determines the smaller of the two values ​​as the GP's requested power value. Since the TX1001's transmittable power value is 12W and the requested power value selected in the requested power selection process in F2416 is 8W, the GP's requested power value is determined to be 8W.

[0143] In F2426, the RX111 stores the determined GP requested power value in a WPC-standard Specific Request (SRQ) data packet and sends it to the TX1001. When the TX1001 receives the SRQ data packet, which is a GP request, the requested power value is smaller than its own transmittable power value, so it accepts the requested power value and stores it as the GP value in F2427.

[0144] At F2428, the TX1001 sends an ACK to the RX111 as a response to the acceptance. Upon receiving the ACK, the RX111 assumes that the requested power value sent at F2426 has been accepted, and stores that requested power value as the GP value at F2429. At F2430, the RX111 sends a notification of the end of the negotiation phase to the TX1001 using an SRQ data packet conforming to the WPC standard. Upon receiving the notification of the end of the negotiation phase, the TX1001 sends an ACK to the RX111 as a response to the acceptance at F2431.

[0145] The processing from F2432 to F2434 is the same as the processing from F1821 to F1823 in FIG. 20, and therefore a description thereof will be omitted.

[0146] According to the present embodiment described above, it is possible to obtain the same effects as the second and third embodiments. Furthermore, the RX111 can select an appropriate required power value based on the information of the NFC tag detected in the NFC tag detection process. This makes it possible to prevent products and components equipped with NFC functionality from being damaged by electromagnetic waves transmitted from the TX1001.

[0147] <Other embodiments> In the first embodiment, the order of S606 and S608 in Fig. 7 may be reversed. Fig. 27 is a flowchart showing such an example. After S605, in both cases where the compatible product 201 is in an authenticated state (YES) in S608 and where the compatible product 201 is not in an authenticated state (NO), it is determined whether or not attachment of the compatible product 201 to the device 101 has been detected (S606a and S606b). Then, in S606b, if attachment of the compatible product 201 to the device 101 has been detected (YES), the processing of the device 101 may proceed to S609. In the example of Figure 27, as in the example described in the explanation of Figure 7, even if the compatible product 201 has already been authenticated (YES in S608), if the attachment of the compatible product 201 is not detected (No in S606a), processing is executed in S607 to cancel the authentication.

[0148] In the third and fourth embodiments, the order of S1906 to S1909 in Fig. 21 can be changed as appropriate for the same purpose as above. Fig. 28 is a flowchart showing such an example. In this flowchart example, YES at S1909 → YES at S1906 → YES at S1907a → S612. However, this is not limiting, and the order may be YES at S1909 → YES at S1907a → S1906 → S612.

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

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

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

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

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

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

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

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

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

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

[0159] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) A device that can be used in combination with a counterpart, a detection means for detecting that the device and the corresponding product have been combined; a reading means for detecting an NFC (Near Field Communication) tag of the compatible product and reading one or more pieces of tag information from the detected NFC tag; and a processing means for switching a processing method for the one or more pieces of tag information that have been read and executing the processing depending on whether a predetermined condition is satisfied. A device characterized by: (Configuration 2) the one or more pieces of tag information include authentication information for the device to authenticate the corresponding product; The processing means executes authentication processing for the compatible product based on the authentication information. 10. The device of claim 1. (Configuration 3) The predetermined condition is: a first condition that the combination of the device and the compatible product is detected by the detection means; a second condition that the compatible product is in a state where it has been authenticated by the authentication process. 3. The device of claim 2. (Configuration 4) The processing means If the first condition and the second condition are satisfied, or if the first condition is not satisfied, the authentication process is not performed; If the first condition is met and the second condition is not met, execute the authentication process. 4. The device of configuration 3. (Configuration 5) When the second condition is satisfied, if the first condition is not satisfied, the processing means cancels the certification of the compatible product. 4. The device of configuration 3. (Configuration 6) power receiving means for wirelessly receiving power from a power transmitting device; and a state detection unit for detecting a state in which the device is capable of receiving power from the power transmitting device, The predetermined condition further includes a third condition that the device is in a state where it can receive power from the power transmitting device. 6. The device of any one of configurations 3 to 5. (Configuration 7) The processing means not performing the authentication process if the first condition, the second condition, and the third condition are satisfied, or if the third condition is not satisfied; If the first condition and the third condition are satisfied but the second condition is not satisfied, the authentication process is executed. 7. The device of configuration 6. (Configuration 8) When the second condition and the third condition are satisfied, if the first condition is not satisfied, the processing means revokes the certification of the compatible product. 8. The device of configuration 7. (Configuration 9) The processing means performs settings related to wireless power transmission processing with the power transmitting device. 7. The device of configuration 6. (Configuration 10) The processing means sets a power profile in the Wireless Power Consortium (WPC) standard in accordance with the first condition and the second condition. 10. The device of any one of configurations 6 to 9. (Configuration 11) The processing means If the first condition and the second condition are satisfied, a first power profile is set; If at least one of the first condition and the second condition is not satisfied, a second power profile different from the first power profile and a third power profile different from the first and second power profiles are set. 11. The device of claim 10. (Configuration 12) When the third condition is satisfied, the processing means checks whether or not there is information indicating that power transmission is permitted among the one or more pieces of tag information. 12. The device of any one of configurations 6 to 11. (Configuration 13) When there is information indicating that the power transmission is permitted, the processing means determines power information indicating power to be requested from the power transmission device in negotiation with the power transmission device based on the information indicating that the power transmission is permitted. 13. The device of claim 12. (Configuration 14) a calculation unit for calculating a receivable power value based on an operating state of the device; The processing means determines the power information based on the information indicating that power transmission is permitted and the receivable power value. 14. The device of claim 13. (Configuration 15) When there is no information indicating that the power transmission is permitted, or when the reading means cannot detect the NFC tag, the processing means determines power information of power limited to a predetermined value or less in negotiation with the power transmitting device. 13. The device of claim 12. (Configuration 16) The detecting means is a magnetic sensor. 16. The device of any one of configurations 1 to 15. (method) A method of controlling a device that can be used in combination with a counterpart, comprising: a detecting step of detecting that the device and the corresponding product have been combined; a reading step of detecting an NFC (Near Field Communication) tag of the compatible product and reading one or more pieces of tag information from the detected NFC tag; and a processing step of switching a processing method for the one or more pieces of tag information that have been read and executing the processing depending on whether a predetermined condition is satisfied. A control method comprising: (program) 17. A program for causing a computer to operate as the device according to any one of configurations 1 to 16.

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

[0161] 101:Device 102: NFC antenna 103: Sensor 111: Power receiving device 201: Compatible products 202: NFC tag 304: Communications Department 305, 1305: Control unit 801~803: NDEF information 1001: Power transmission equipment 1304: First Communications Department 1307: Power receiving unit 1308: Second Communications Department 1309:Detection unit

Claims

1. A device, The device is a device that can be used in combination with a corresponding product that can be combined with the device, and the device is a detection means for detecting that the device and the corresponding product have been combined; a reading means for detecting an NFC (Near Field Communication) tag of the compatible product and reading one or more pieces of tag information from the NFC tag, the tag information including authentication information for authenticating the compatible product; a processing means for determining whether a predetermined condition is satisfied and for executing a process relating to the one or more pieces of tag information in accordance with the determination result; The processing includes an authentication process for the corresponding product, the predetermined conditions include a first condition and a second condition, the first condition is that the detection means detects that the device and the corresponding product are combined; The second condition is that the corresponding product is authenticated by the authentication process. A device characterized by:

2. The processing means If the first condition and the second condition are satisfied, or if the first condition is not satisfied, the authentication process is not performed; If the first condition is met but the second condition is not met, execute the authentication process.

2. The device of claim 1 .

3. When the second condition is satisfied, if the first condition is not satisfied, the processing means cancels the certification of the compatible product.

2. The device of claim 1 .

4. power receiving means for wirelessly receiving power from a power transmitting device; and a state detection unit for detecting a state in which the device is capable of receiving power from the power transmitting device, The predetermined condition further includes a third condition that the device is in a state capable of receiving power from the power transmitting device.

2. The device of claim 1 .

5. The processing means not performing the authentication process if the first condition, the second condition, and the third condition are satisfied, or if the third condition is not satisfied; If the first condition and the third condition are satisfied but the second condition is not satisfied, the authentication process is executed.

5. The device of claim 4.

6. When the second condition and the third condition are satisfied, if the first condition is not satisfied, the processing means cancels the certification of the compatible product.

6. The device of claim 5.

7. The processing means performs settings related to wireless power transmission processing with the power transmitting device.

5. The device of claim 4.

8. The processing means sets a power profile in the Wireless Power Consortium (WPC) standard in accordance with the first condition and the second condition.

5. The device of claim 4.

9. The processing means If the first condition and the second condition are satisfied, a first power profile is set; If at least one of the first condition and the second condition is not satisfied, a second power profile different from the first power profile and a third power profile different from the first and second power profiles are set.

9. The device of claim 8.

10. When the third condition is satisfied, the processing means checks whether or not there is information indicating that power transmission is permitted among the one or more pieces of tag information.

5. The device of claim 4.

11. When there is information indicating that the power transmission is permitted, the processing means determines power information indicating power to be requested from the power transmission device in negotiation with the power transmission device based on the information indicating that the power transmission is permitted.

11. The device of claim 10.

12. a calculation unit for calculating a receivable power value based on an operating state of the device; The processing means determines the power information based on the information indicating that power transmission is permitted and the receivable power value.

12. The device of claim 11 .

13. When there is no information indicating that the power transmission is permitted or when the reading means cannot detect the NFC tag, the processing means determines power information of power limited to a predetermined value or less in negotiation with the power transmitting device.

11. The device of claim 10.

14. The detecting means is a magnetic sensor.

2. The device of claim 1 .

15. A method for controlling a device, comprising: The device is a device that can be used in combination with a corresponding product that can be combined with the device, and the control method includes: a detecting step of detecting that the device and the corresponding product have been combined; a reading step of detecting an NFC (Near Field Communication) tag of the compatible product and reading one or more pieces of tag information from the NFC tag, the tag information including authentication information for authenticating the compatible product; a processing step of determining whether a predetermined condition is satisfied and executing a process related to the one or more pieces of tag information in accordance with the determination result, The processing includes an authentication process for the corresponding product, the predetermined conditions include a first condition and a second condition, the first condition is that the combination of the device and the corresponding product is detected in the detection step; The second condition is that the corresponding product is authenticated by the authentication process. A control method comprising:

16. A program for causing a computer to operate as the device according to any one of claims 1 to 14.

Images