Communication apparatus, communication method, and program

Abstract

A communication device includes a first processing unit that sends a first command to start an activation processing. The communication device also includes a second processing unit that receives the first command from the first processing unit. In addition, the communication device includes an interface between the first processing unit and the second processing unit. The first processing unit activates the interface at a predetermined interface level from among a plurality of interface levels. The second processing unit starts an application in accordance with the activated interface level. The first processing unit and the second processing unit exchange data by the activated application. The first processing unit and the second processing unit perform a deactivation processing of the activated interface.

Claims

1. A communication device, comprising: a processor; and a near field communication circuitry configured to, prior to the start of an application by the processor, send a first message to the processor, the first message indicating a plurality of interfaces supported by the near field communication circuitry for communication between the near field communication circuitry and the processor, and set an interface from among the plurality of interfaces supported by the near field communication circuitry in response to a first command from the processor.

2. The communication device of claim 1, wherein the interfaces supported by the near field communication circuitry indicate interface capabilities.

3. The communication device of claim 2, wherein the interface capabilities indicate an amount of processing by which the near field communication circuitry is burdened.

4. The communication device of claim 1, wherein the processor comprises an application processor (AP).

5. The communication device of claim 1, wherein the near field communication circuitry comprises a contactless front end (CLF).

6. The communication device of claim 1, wherein the near field communication apparatus further comprises an interface between the processor and the near field communication circuitry.

7. The communication device of claim 1, wherein the processor is configured to start the application, and the application is for exchanging data with a selected external target from among external targets detected by the near field communication circuitry.

8. The communication device of claim 1, wherein the interface indicates a processing setting for the near field communication circuitry.

9. The communication device of claim 1, wherein the interfaces indicate a processing allocation.

10. The communication device of claim 1, wherein the interfaces indicate an amount of processing allocated to the near field communication circuitry.

11. A device comprising: near field communication circuitry configured to, prior to a start of an application by a processor: send a first message to the processor, the first message indicating a plurality of interfaces supported by the near field communication circuitry for communication between the near field communication circuitry and the processor, and to set an interface from the interfaces supported by the near field communication circuitry in response to a first command from the processor.

12. The device according to claim 11, wherein the interfaces supported by the near filed communication circuitry indicate interface capabilities.

13. The device according to claim 11, wherein the interface capabilities indicate an amount of processing by which the near field communication circuitry is burdened.

14. The device according to claim 11, wherein the near field communication circuitry comprises a contactless front end (CLF), and the processor comprises an application processor (AP).

15. The device according to claim 11, wherein the set interface is between the near field communication circuitry and the processor.

16. The device according to claim 11, wherein the near field communication circuitry is configured to exchange data between the application after the application is started by the processor and a selected external target of a plurality of external targets detected by the near field communication circuitry.

17. The device according to claim 16, the near field communication circuitry is configured to deactivate the interface in response to a deactivation command from the processor.

18. The device according to claim 11, wherein the interface indicates a processing setting for the near field communication circuitry.

19. The device according to claim 11, wherein the interfaces indicate a processing allocation.

20. The device according to claim 11, wherein the interfaces indicate an amount of processing allocated to the near field communication circuitry.

21. A device, comprising: a processor configured to, prior to starting an application: receive a first message from a near field communication circuitry, the first message indicating a plurality of interfaces supported by the near field communication circuitry for communication between the near field communication circuitry and the processor, and send a first command to the near field communication circuitry to cause the near field communication circuitry to set an interface from the plurality of interfaces supported by the near field communication circuitry.

22. The device according to claim 21, wherein the interfaces supported by the near field communication circuitry indicate interface capabilities.

23. The device according to claim 21, wherein the interface capabilities indicate an amount of processing by which the near field communication circuitry is burdened.

24. The device according to claim 21, wherein the processor comprises an application processor (AP).

25. The device according to claim 21, wherein the set interface is between the communication circuitry and the processor.

26. The device according to claim 21, wherein the processor is configured to start the application and the application is for exchanging data with a selected external target from among external targets detected by the communication circuitry.

27. The device according to claim 21, wherein the interface indicates a processing setting for the communication circuitry.

28. The device according to claim 21, wherein the interfaces indicate a processing allocation.

29. The device according to claim 21, wherein the interfaces indicate an amount of processing allocated to the communication circuitry.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a block diagram showing a configuration example of an embodiment of a communication system to which the present disclosure is applied;

(2) FIG. 2 is a diagram showing an interface level settable for each RF protocol;

(3) FIG. 3 is a diagram showing a difference in processing in accordance with an interface level in the case of a communication layer for P2P communication between NFC devices;

(4) FIG. 4 is a diagram illustrating a detailed format of each message;

(5) FIG. 5 is a diagram illustrating a detailed format of each message;

(6) FIG. 6 is a diagram illustrating a detailed format of each message;

(7) FIG. 7 is a diagram illustrating a detailed format of each message;

(8) FIG. 8 is a diagram illustrating a detailed format of each message;

(9) FIG. 9 is a diagram illustrating a detailed format of each message;

(10) FIG. 10 is a diagram showing a list of messages;

(11) FIG. 11 is a flowchart illustrating a sequence outline;

(12) FIG. 12 is a diagram illustrating a detailed sequence example in the case of a Poll Mode;

(13) FIG. 13 is a flowchart illustrating a detailed sequence example in the case of a Poll Mode;

(14) FIG. 14 is a flowchart illustrating a detailed sequence example in the case of a Listen Mode; and

(15) FIG. 15 is a flowchart illustrating a detailed sequence example in the case of a Listen Mode.

DETAILED DESCRIPTION

(16) [Configuration Example of Communication System to which Present Disclosure is Applied]

(17) FIG. 1 shows a configuration example of a communication system according to an embodiment to which the present disclosure is applied.

(18) The communication system in FIG. 1 includes an NFC device 1 and NFC devices 11-1 to 11-3.

(19) The NFC device 1 and the NFC devices 11-1 to 11-3 are communication apparatuses for near field wireless communication based on one or both of ISO/IEC 18092 and ISO/IEC 14443. The NFC device 1 and the NFC devices 11-1 to 11-3 can be operated as either of a polling device and a listening device.

(20) The polling device forms a so-called RF (Radio Frequency) field (magnetic field) by generating an electromagnetic wave, sends a polling command to detect a listening device as a target, and waits for the response from the listening device. In other words, the polling device performs an operation of a PCD (Proximity Coupling Device) of ISO/IEC 14443 or an operation of an initiator in the passive mode of ISO/IEC 18092.

(21) The listening device receives a polling command which is sent from the polling device by forming the RF field and then responds with a polling response. In other words, the listening device performs the operation of PICC of ISO/IEC 14443 or the operation of the target of ISO/IEC 18092.

(22) Accordingly, the NFC device 1 and the NFC devices 11-1 to 11-3 may have the same hardware configurations, respectively.

(23) The NFC devices 11-1 to 11-3 are respectively referred to as targets 11-1 to 11-3 hereinbelow to simplify the difference between the NFC device 1 and the NFC devices 11-1 to 11-3. In addition, when it is not particularly necessary to distinguish the targets 11-1 to 11-3, the targets 11-1 to 11-3 are simply referred to as a target 11 (or an NFC device 11).

(24) The NFC device 1 includes one AP (Application Processor) 21, one CLF (Contactless Front end) 22, and 0 or more SEs (Secure Element) 23. Since 0 or more SEs 23 are provided, the number thereof may be 0 (the SE 23 may be omitted).

(25) The AP 21 performs overall control of the NFC device 1, generates a command (CMD) for controlling the CLF 22, and analyzes an execution result with respect to the command. The AP is an example of a processing means. The AP 21 exchanges a message with the CLF 22 in accordance with the HCI (Host Controller Interface). In addition, the AP 21 executes an application for data exchange with the target 11. Examples of the application include an application which performs data exchange processing for name cards and an address book in the P2P (Peer-to-Peer) communication, electronic money payment processing, and the like between a reader writer and an IC card. In addition, the AP 21 stores therein three applications App (H), App (M), and App (L) with different levels as the applications for data exchange in accordance with the level of the interface of the CLF 22 (interface level).

(26) Thus, the CLF 22 includes a memory. The memory can also be external to the CLF 22. The memory can be a ROM, a RAM, a magnetic disk, an optical disk, or any other memory.

(27) Further, the memory is an example of a storing means. When the AP executes a program to perform a method according to some embodiments, the memory is an example of a non-transitory storage medium.

(28) The CLF 22 is an interface which is disposed between the AP 21 and the target 11 to mediate therebetween and controls the path such that the AP 21 and the SE 23 can exchange data with the target 11. The CLF is an example of a processing means. The CLF 22 has a plurality of interface levels as the interface level for mediating the AP 21 and the target 11. In this embodiment, the CLF 22 is assumed to have three stages of interface levels including a low level, a middle level, and a high level. The CLF 22 is instructed by the HCI and exchanges messages with the AP 21 and performs transceiving of RF data through an antenna 24 based on a command (CMD) from the AP 21.

(29) The HCI is a logical interface between the AP 21 and the CLF 22, and a command (CMD) and a notification (NTF) in a predetermined format which will be described later are defined in the HCI.

(30) The SE 23 performs processing and retaining of secure data from among the processing which are necessary for the data exchange between the NFC device 1 and the target 11. In the example of FIG. 1, three SEs 23-1 to 23-3 are provided in the NFC device 1. The SEs 23-1 and 23-2 are connected to the CLF 22 to perform retaining and processing of secure data which is treated by the CLF 22 while the SE 23-3 is connected to the AP 21 to perform retaining and processing of secure data which is treated by the AP 21. It is possible to provide a necessary number of SEs 23 in the NFC device 1 or omit the SEs 23 if it is not necessary.

(31) The antenna 24 constitutes a closed-loop coil and outputs an electromagnetic wave (RF data) if the current flowing through the coil changes. The antenna is an example of a transmitting means and/or a receiving means.

(32) The NFC device 1 configured as described above supports one or more of the following three RF technologies.

(33) (1) NFC-A . . . Type A communication scheme of ISO/IEC 14443

(34) (2) NFC-B . . . Type B communication scheme of ISO/IEC 14443

(35) (3) NFC-F . . . 212 kbps and 424 kbps communication schemes of ISO/IEC 18092

(36) The NFC-A is an abbreviated expression of Type A of ISO/IEC 14443, the NFC-B is an abbreviated expression of Type B of ISO/IEC 14443, and the NFC-F is an abbreviated expression of 212 kbps and 424 kbps communication schemes of ISO/IEC 18092, in this specification.

(37) In addition, the NFC device 1 supports one or more of the following six RF protocols.

(38) (1) T1T . . . TYPE 1 TAG PLATFORM Protocol (based on Type NFC-A)

(39) (2) T2T . . . TYPE 2 TAG PLATFORM Protocol (based on Type NFC-A)

(40) (3) T3T . . . TYPE 3 TAG PLATFORM Protocol (based on Type NFC-F)

(41) (4) ISO-DEP . . . ISO-DEP Protocol (ISO/IEC 14443-4 based on Type NFC-A or NFC-B)

(42) /TYPE 4 TAG PLATFORM Protocol (based on Type NFC-A or NFC-B)

(43) (5) NFC-DEP . . . NFC-DEP Protocol (ISO/IEC 18092 transport protocol based on NFC-A or NFC-F)

(44) (6) Prop . . . Proprietary Definition Protocol (Proprietary Protocol)

(45) The T1T is an abbreviated expression of TYPE 1 TAG PLATFORM Protocol (based on NFC-A), and the T2T is an abbreviated expression of TYPE 2 TAG PLATFORM Protocol (based on NFC-A), in this specification. The same is true for the T3T, the ISO-DEP, the NFC-DEP, and the Prop.

(46) [Concerning Interface Level]

(47) When the NFC device 1 exchanges data with the target 11, the NFC device 1 can allot processing to the AP 21 and the CLF 22. In other words, it is possible to cause the intermediate CLF 22 to perform processing which is necessary for the data exchange with the target 11 instead of the AP 21. At this time, to which level the CLF 22 performs the processing necessary for the data exchange instead is determined based on the interface level designated (notified) from the AP 21 to the CLF 22.

(48) From among the three stages of interface levels including a low level, a middle level, and a high level of the CLF 22, the high level is a level at which the amount of processing allotted to the CLF 22 as an interface is the largest, and the low level is a level at which the amount of processing allotted to the CLF 22 as an interface is the smallest. It is necessary to set the interface level for each RF protocol, and a settable interface level is set in advance depending on the RF protocol in the CLF 22.

(49) FIG. 2 shows the interface level which can be set for the RF protocol by the CLF 22.

(50) Only a low interface level can be set for each of the RF protocols T1T, T2T, and T3T. In addition, the RF technology when the RF protocol is Ill and T2T is NFC-A, and the RF technology when the RF protocol is T3T is NFC-F.

(51) It is possible to set any of the interface levels from among the low level, the middle level, and the high level for each of the RF protocols ISO-DEP and NFC-DEP. The RF technology when the RF protocol is ISO-DEP is NFC-A or NFC-B, and the RF technology when the RF protocol is NFC-DEP is NFC-A or NFC-F.

(52) Only the low interface level can be set for the RF protocol Prop.

(53) FIG. 3 shows a difference in processing depending on the interface level in the case of a communication layer for the P2P communication between NFC devices.

(54) At the low interface level, the CLF 22 has functions of Frame format, Anticollision, Bit coding, and Modulation/Load modulation based on ISO/IEC 18092. At the middle interface level, the CLF 22 further has functions up to a transport protocol based on ISO/IEC 18092. That is, the CLF 22 further has functions of Protocol activation/deactivation, Segmentation and reassembly, and Retransmission as well as the functions at the low level. At the high interface level, the CLF 22 has functions up to LLCP (NFC Forum Logical Link Control Protocol) which is a higher layer protocol of transport protocol based on ISO/IEC 18092.

(55) It is possible to set and mount the interface level of the CLF 22 for each RF protocol from among the three stages in accordance with the application conditions, the costs of the IC chips, and the like which are assumed by the CLF 22.

(56) In initial processing, the CLF 22 notifies the AP 21 of the information regarding up to which interface level the CLF 22 itself supports. The AP 21 grasps the interface level supported by the CLF 22, selects an optimal interface level from among the interface levels supported by the CLF 22 in accordance with the application conditions assumed by the AP 21, and designates the interface level for the CLF 22. When the CLF 22 supports all interface levels, the AP 21 can select an optimal interface level in accordance with the processing supported by the application. For example, when it is desired that the AP 21 executes an application with less processing, the AP 21 may select and designate the high interface level for the CLF 22.

(57) [Message Format]

(58) Next, detailed description will be made of a message defined as an HCI with reference to FIGS. 4 to 9.

(59) There are three kinds of messages including a CMD (command) from the AP 21 to the CLF 22, an RSP (response) from the CLF 22 to the AP 21 for the command, and an NTF (notification) from the CLF 22 to the AP 21.

(60) FIG. 4 shows formats for an initialization command INIT_COM and an initialization response INIT_RES.

(61) The initialization command INIT_COM is a message for initialization of the HCI and the ability exchange between the CLF 22 and the AP 21. The initialization command INIT_COM includes Version representing the HCI version (version number) of the AP 21 and HCI Features representing the ability of the AP 21 as parameters. The information regarding the communication control functions supported by the AP 21 such as information regarding the presence of a flow control function, a card emulation function, an additional message creation function, and the like is input in HCI Features.

(62) The initialization response INIT_RES is a message for responding to the initialization command. The initialization response INIT_RES includes Status representing the response result for the initialization command INIT_COM, Version representing the HCI version of the CLF 22, HCI Features representing the ability of the CLF 22, and HCI Interfaces representing the interface ability of the CLF 22 as parameters. The information regarding the communication control functions supported by the CLF 22 such as information regarding the presence of a flow control function, a battery OFF mode function, a routing function with the use of an application identifier of card emulation, and the like is input in HCI Features. The interface level for each RF protocol supported by the CLF 22 is input in HCI Interfaces.

(63) The AP 21 and the CLF 22 mutually check the versions thereof by the initialization command INIT_COM and the initialization response INIT_RES, and it is possible to exchange messages while being instructed by the HCI if the version of the AP 21 is equivalent or higher than the version of the CLF 22. On the other hand, if the version of the AP 21 is lower than the version of the CLF 22, the AP 21 performs error processing such as an output of an error message.

(64) FIG. 5 shows formats for the interface level setting command SET_INTERFACE_LEVEL_COM and the interface level setting response SET_INTERFACE_LEVEL_RES.

(65) The interface level setting command SET_INTERFACE_LEVEL_COM is a message for associating the RF protocol and the interface level. The interface level setting command SET_INTERFACE_LEVEL_COM includes the number [n] of interface level setting data items and n interface level setting data items.

(66) The interface level setting data for one RF protocol includes Mode representing the mode (Poll mode/Listen Mode) of the target 11, Protocol representing the used RF protocol, and Interface level representing the used interface level. That is, it is possible to set the interface level (Interface level) for each of the Poll Mode and the Listen Mode for one RF protocol (Protocol). For example, setting can be made such that the middle interface level is set for the case of the Poll Mode when the RF protocol is ISO-DEP and the high interface level is set for the case of the Listen Mode when the RF protocol is ISO-DEP. Accordingly, the number n of the interface level setting data items becomes twice as large as the number of the RF protocols at a maximum.

(67) The interface level setting response SET_INTERFACE_LEVEL_RES is a message for responding to the interface level setting command. The interface level setting response SET_INTERFACE_LEVEL_RES includes OK=1, or NG=0, which represents the response result, as a parameter.

(68) FIG. 6 shows formats for the discovery start command DISCOVER_START_COM, the discovery start response DISCOVER_START_RES, the discovery stop command DISCOVER_STOP_COM and the discovery stop response DISCOVER_STOP_RES.

(69) The discovery start command DISCOVER_START_COM is a message for requesting the start of the detection of the target 11. The parameter of the discovery start command DISCOVER_START_COM includes Discovery Types representing the RF technologies as detection targets, the number of which corresponds to the number of the RF technologies which are desired to be detected.

(70) The discovery start response DISCOVER_START_RES is a message for responding to the discovery start command. The discovery start response DISCOVER_START_RES includes OK=1 or NG=0, which represents the response result, as a parameter.

(71) The discovery stop command DISCOVER_STOP_COM is a message for requesting the detection of the target 11 to be stopped. The discovery stop command DISCOVER_STOP_COM does not include any parameters.

(72) The discovery stop response DISCOVER_STOP_RES is a message for responding to the discovery stop command. The discovery stop response DISCOVER_STOP_RES includes OK=1 or NG=0, which represents the response result, as a parameter.

(73) FIG. 7 shows formats for the discovery selection command DISCOVER_SELECT_COM, the discovery selection response DISCOVER_SELECT_RES, the deactivation command DEACT_COM, and the deactivation response DEACT_RES.

(74) The discovery selection command DISCOVER_SELECT_COM is a message for selecting the RF technology (target 11) and the RF protocol. A selected RF technology (target 11) is input in the parameter Target ID, and a selected RF protocol is input to the parameter Target SAP of the discovery selection command DISCOVER_SELECT_COM.

(75) The discovery selection response DISCOVER_SELECT_RES is a message for responding to the discovery selection command. The discovery selection response DISCOVER_SELECT_RES includes OK=1 or NG=0, which represents the response result, as a parameter.

(76) The deactivation command DEACT_COM is a message for requesting the completion of the data exchange with the target 11. The deactivation command DEACT_COM includes Target ID corresponding to the RF technology, Target SAP corresponding to the RF protocol, and Deactivation Type which is the command to be sent to the target, as parameters.

(77) The deactivation response DEACT_RES is a message for responding to the deactivation command DEACT_COM. The deactivation response DEACT_RES includes OK=1 or NG=0, which represents the response result, as a parameter.

(78) FIG. 8 shows formats for the discovery notification DISCOVER_NTF, the activation notification ACT_NTF, and the deactivation notification DEACT_NTF.

(79) The discovery notification DISCOVER_NTF is a message for the notification of the target, and the RF technology and the RF protocol thereof. There are a plurality of combinations of the target, the RF technology, and the RF protocol in some cases in the same manner as in the aforementioned discovery selection command DISCOVER_SELECT_COM.

(80) The discovery notification DISCOVER_NTF includes Target ID which is the number allotted by the CLF 22 to the RF technology, Target SAP which is the number allotted by the CLF 22 to the RF protocol, Discovery Type representing the detected RF technology, RF Protocol representing the RF protocol of the target 11, the Technology Specific Parameters representing the RF technology specific parameter, and More representing the presence of the next discovery notification DISCOVER_NTF, as parameters.

(81) The activation notification ACT_NTF is a message for the notification of the activation (activating, starting) of a specific interface level (activation, start). The activation notification ACT_NTF includes Activation Parameters representing the activation parameters and Interface Type representing the activated interface level as well as the aforementioned Target ID, Target SAP, Discovery Type, and RF protocol, as parameters.

(82) The deactivation notification DEACT_NTF is a message for the notification of the deactivation (deactivating) of a specific interface level. The deactivation notification DEACT_NTF includes Deactivation Parameters representing the deactivation parameters as well as the aforementioned Target ID and Target SAP, as parameters.

(83) FIG. 9 shows a list of messages described with reference to FIGS. 4 to 8.

(84) [Sequence Outline]

(85) Next, description will be made of the outline of the sequence performed between the AP 21 and the CLF 22 when the AP 21 exchanges data with the target 11 with reference to FIG. 10.

(86) The sequence performed between the AP 21 and the CLF 22 when the AP 21 exchanges data with the target 11 roughly includes the following five steps.

(87) (1) Initialization processing for setting interface level for RF protocol

(88) (2) Discovery processing for target 11

(89) (3) Activation processing for interface

(90) (4) Data exchange processing

(91) (5) Deactivation processing for interface

(92) When the AP 21 exchanges data with a plurality of targets 11, the steps from (3) to (5) are sequentially executed for each of the plurality of target 11.

(93) (1) Initialization Processing for Setting Interface Level for RF Protocol

(94) In the initialization processing, the AP 21 designates (notifies of) the interface level associated with an RF protocol by sending the interface level setting command SET_INTERFACE_LEVEL_COM after checking the interface ability of the CLF 22. The initialization processing corresponds to the processing in Step S11 of the AP 21 and the processing in Step S21 of the CLF 22 in FIG. 10.

(95) (2) Discovery Processing for Target 11

(96) The discovery processing is processing for detecting the target 11. If the AP 21 sends the discovery start command DISCOVER_START_COM for requesting the start of the detection of the target 11 to the CLF 22 in Step S12, the CLF 22 starts the processing of detecting the target 11 in Step S22.

(97) In the detection of the target 11, the CLF 22 alternately repeats the Poll Mode and the Listen Mode. That is, the CLF 22 repeats processing of setting the polling command and waiting for the response from the counterpart (Poll Mode) and processing of waiting for the polling command from the counterpart (Listen Mode) thereafter.

(98) In the Poll Mode, if the CLF 22 receives a response for the sent polling command, the communication link with the target 11 is regarded to have been established, and the mode at that time (Poll Mode) is maintained. In the Poll Mode, the CLF 22 can act as a PCD or an Initiator and send a command.

(99) On the other hand, in the Listen Mode, if the CLF 22 sends a response to the polling command from the counterpart, the communication link with the target 11 is regarded to have been established, and the mode at that time (Listen Mode) is maintained. In the Listen Mode, the CLF 22 can act as a PICC or a Target and respond to the received command (send the response).

(100) The CLF 22 notifies the AP 21 of the detected target 11 by the discovery notification DISCOVER_NTF in Step S23. When a plurality of targets 11 are detected, the CLF 22 sends the discovery notification DISCOVER_NTF for each of all detected targets 11.

(101) (3) Activation Processing for Interface

(102) The AP 21 receives the discovery notification DISCOVER_NTF, then selects one predetermined target 11 from among the received targets, and sends the discovery selection command DISCOVER_SELECT_COM to the CLF 22 in Step S13.

(103) The CLF 22 receives the discovery selection command DISCOVER_SELECT_COM and activates the interface of the one selected target 11 based on the discovery selection command DISCOVER_SELECT_COM in Step S24. Then, the CLF 22 notifies the AP 21 of the fact that the interface of the target 11 selected by the discovery selection command DISCOVER_SELECT_COM has been activated, by the activation notification ACT_NTF.

(104) In addition, this processing is processing in the case of the Poll Mode, and different processing is performed in the case of the Listen Mode since the AP 21 does not select the target 11. That is, the CLF 22 responds with a plurality of RF technologies in the Listen Mode when the CLF 22 retains a state machine for the plurality of RF technologies. The CLF 22 responds with the RF technology detected first when the CLF 22 retains a state machine for one RF technology. The CLF 22 activates the interface of the responding target 11 and notifies the AP 21 of the fact by the activation notification ACT_NTF. Since the target 11 sends a command in the Listen Mode, the CLF 22 performs processing in accordance with the received command.

(105) (4) Data Exchange Processing

(106) The AP 21 receives the activation notification ACT_NTF from the CLF 22 and then activates the application in Step S14. At this time, the AP 21 selects one of the applications App (H), App (M), and App (L) in accordance with the interface level of the CLF 22.

(107) The AP 21 exchanges data with the target 11 through the CLF 22 by the activated application in Step S15. The CLF 22 exchanges data between the AP 21 and the target 11 in Step S25.

(108) (5) Deactivation Processing for Interface

(109) In the Poll Mode, the application activated in the AP 21 sends the deactivation command DEACT_COM to the CLF 22 at the time of the completion of the application. The CLF 22 receives the deactivation command DEACT_COM, deactivates the interface of the communicating target 11, and disconnects the communication link with the target 11 in Step S26.

(110) On the other hand, the CLF 22 sends the deactivation notification DEACT_NTF to the AP 21 after the disconnection of the communication link with the communicating target 11 in the Listen Mode. The AP 21 completes the application when the deactivation notification DEACT_NTF is received in Step S16.

(111) The rough sequence flow has been described above for the example in which communication is performed by one target 11.

(112) [Detailed Example of Sequence (in the Case of Poll Mode)]

(113) Hereinafter, detailed description will be made of the sequence performed between the AP 21 and the CLF 22 when the AP 21 exchanges data with a plurality of targets 11 with reference to FIGS. 11 to 13.

(114) FIG. 11 shows the RF technology and the RF protocol supported by each of the targets 11-1 to 11-3.

(115) The target 11-1 supports NFC-A as the RF technology and two RF protocols including ISO-DEP and NFC-DEP. The target 11-2 supports NFC-B as the RF technology and ISO-DEP as the RF protocol. The target 11-3 supports the NFC-F as the RF technology and T3T as the RF protocol.

(116) In FIG. 11, Target ID and Target SAP shown in the right side of the section for the RF protocol represent identifiers allotted to the detected target 11 by the CLF 22 in a series of sequence shown in FIGS. 12 and 13.

(117) [Sequence Example for Poll Mode]

(118) FIGS. 12 and 13 are flowcharts showing a sequence in which the NFC device 1 (CLF 22) is operated in the Poll Mode to communicate with three targets 11-1 to 11-3 with different RF technologies.

(119) First, the AP 21 sends an initialization command INIT_COM in Step S41, and the CLF 22 sends an initialization response INIT_RES as a response to the AP 21 in Step S42. The initialization response INIT_RES includes an interface level for each RF protocol supported by the CLF 22 as described above.

(120) In Step S43, the AP 21 sends an interface level setting command SET_INTERFACE_LEVEL_COM for associating the RF protocol and the interface level to the CLF 22 based on the interface level for each RF protocol supported by the CLF 22. In Step S43, SET_INTERFACE_LEVEL_COM (5, Poll, ISO-DEP Protocol, Mid I/F Level, Poll, NFC-DEP Protocol, High I/F Level, Poll, T1T Protocol, Low I/F Level, Poll, T2T Protocol, Low I/F Level, Poll, T3T Protocol, Low I/F Level) is sent. With such a command, the middle interface level is set when the RF protocol is ISO-DEP, the high interface level is set for NFC-DEP, and the low interface level is set for T1T, T2T, and T3T in the CLF 22 in the Poll Mode.

(121) Although setting is made for the RF protocols T1T, T2T, and T3T in this example, the levels of the RF protocols T1T, T2T, and T3T may be fixed to the low level, and the sending of the command and the setting may be omitted since only the low interface level can be set for the RF protocols T1T, T2T, and T3T.

(122) Since the sequence of FIG. 12 describes an example in which the NFC device 1 (CLF 22) is operated in the Poll Mode, the designation of each interface level in the Listen Mode is omitted in the interface level setting command SET_INTERFACE_LEVEL_COM in Step S43.

(123) The CLF 22 sends an interface level setting response SET_INTERFACE_LEVEL_RES which represents that the interface level setting command SET_INTERFACE_LEVEL_COM from the AP 21 has been understood in Step S44.

(124) Then, the AP 21 designates NFC-A, NFC-B, and NFC-F as the RF technologies of the detection targets and sends a discovery start command DISCOVER_START_COM to the CLF 22 in Step S45. The CLF 22 sends a discovery start response DISCOVER_START_RES representing that the discovery start command DISCOVER_START_COM has been understood to the AP 21 in Step S46.

(125) Then, the CLF 22 sends a command for detecting the targets 11 for NFC-A, NFC-B, and NFC-F designated as the RF technologies of the detection targets. Specifically, the AP 21 sends a command SENS_REQ for NFC-A in Step S47 and receives a response SENS_RES for the command SENS_REQ which is sent from the target 11-1 in the RF field in Step S48. The RF protocol of the target 11-1 is not yet known at the time of receiving the response SENS_RES.

(126) In addition, the AP 21 sends a command SENSB_REQ for NFC-B in Step S49 and receives a response SENSB_RES for the command SENSB_REQ which is sent from the target 11-2 in the RF field in Step S50. The fact that the RF protocol of the target 11-2 is ISO-DEP is known by receiving the response SENSB_RES.

(127) Moreover, the AP 21 sends a command SENSF_REQ for NFC-F in Step S51 and receives a response SENSF_RES for the command SENSF_REQ which is sent from the target 11-3 in the RF field in Step S52. The fact that the RF protocol of the target 11-3 is T3T is known by receiving the response SENSF_RES.

(128) Although the CLF 22 alternately repeats the Poll Mode and the Listen Mode if no target 11 is detected, the operation in the Listen Mode is not performed since the targets 11-1 to 11-3 are detected in the Poll Mode.

(129) The CLF 22 sends three discovery notifications DISCOVER_NTF for the notification of the detected targets 11-1 to 11-3 to the AP 21 in Steps S53 to S55. Specifically, the CLF 22 allots TID1 as the Target ID and TSAP1 as the Target SAP for the detected target 11-1 of NFC-A and sends a discovery notification DISCOVER_NTF to the AP 21 in Step S53.

(130) The CLF 22 allots TID2 as the Target ID and TSAP2 as the Target SAP for the detected target 11-2 of NFC-B and sends a discovery notification DISCOVER_NTF to the AP 21 in Step S54. The CLF 22 allots TID3 as the Target ID and TSAP3 as the Target SAP for the detected target 11-3 of NFC-F and sends a discovery notification DISCOVER_NTF to the AP 21 in Step S55.

(131) Here, the last parameters More of the discovery notifications DISCOVER_NTF sent in Steps S53 and S54 are 1 since the discovery notification DISCOVER_NTF will be sent again. On the other hand, the last parameter More of the discovery notification DISCOVERY_NTF sent in Step S55 is 0 since no discovery notification DISCOVER_NTF will be sent again.

(132) In the following sequence, the target 11 is specified by the Target ID and the Target SAP allotted by the CLF 22, and messages are exchanged between the AP 21 and the CLF 22.

(133) The AP 21 selects communication with the target 11-2 from among the detected targets 11-1 to 11-3 and sends a discovery selection command DISCOVER_SELECT_COM with parameters of TID2 for Target ID and TSAP2 for Target SAP in Step S56.

(134) The CLF 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES representing that the command has been understood to the AP 21 in Step S57.

(135) The middle interface level is designated by the aforementioned interface level setting command SET_INTERFACE_LEVEL_COM for the RF protocol of ISO-DEP represented by Target SAP=TSAP2 included in the discovery selection command DISCOVER_SELECT_COM. The protocol activation is the processing performed by the CLF 22 in the middle interface level as described above with reference to FIG. 3.

(136) Thus, the CLF 22 performs the protocol activation in Step S58. That is, the CLF 22 informs of its own attributes (specifications) and sends an ATTRIB command for requesting the attributes of the target 11-2 to the target 11-2. The CLF 22 receives a response ATTA from the target 11-2 as a response for the ATTRIB command in Step S59.

(137) If the response ATTA is received, the CLF 22 sends an activation notification ACT_NTF representing the fact that the activation of the interface in the middle interface level has been completed to the AP 21 in Step S60. The parameters of the activation notification ACT_NTF include a received response ATTA as Activation Parameter and Mid I/F Level activated representing the activated interface level as Interface Type.

(138) After the completion of the interface activation, the application App (M) corresponding to the middle interface level in the AP 21 is started to exchange data between the AP 21 and the target 11-2 (TID2) with the use of the RF protocol ISO-DEP (TSAP2) in Step S61.

(139) When predetermined data exchange is performed, and the application App (M) is completed, the AP 21 sends a deactivation command DEACT_COM to the CLF 22 in Step S62. The parameter Deactivation Type of the deactivation command DEACT_COM includes a command DESELECT to be sent to the target 11-2.

(140) The CLF 22 sends a deactivation response DEACT_RES representing the fact that the deactivation command DEACT_COM has been understood to the AP 21 in Step S63.

(141) Then, the CLF 22 sends a DESELECT command to the target 11-2 based on the parameter Deactivation Type included in the deactivation command DEACT_COM in Step S64. The CLF 22 receives the response DESELECT from the target 11-2 and deactivates the interface in Step S65. The parameters relating to the target 11-2 (TID2) and ISO-DEP (TSAP2) are released by the deactivation of the interface.

(142) From Step S66 in FIG. 13, the target 11-1 (TID1) is selected as a communication counterpart, and communication is performed between the AP 21 and the target 11-1 (TID1).

(143) That is, the AP 21 sends a discovery selection command DISCOVER_SELECT_COM with parameters of TID1 as Target ID and TSAP1 as Target SAP to the CLF 22 in Step S66.

(144) The CLF 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES representing that the command has been understood to the AP 21 in Step S67.

(145) Then, the CLF 22 recognizes a predetermined PICC and performs anticollision processing for communication even if a plurality of PICCs (IC cards) exist between the CLF 22 and the target 11-1 corresponding to the parameter TID1 and the TSAP1, in Step S68.

(146) In Step S69, the CLF 22 receives a response SEL_RES (ISO-DEP|NFC-DEP) representing that ISO-DEP and NFC-DEP are supported as the RF protocols from the target 11-1.

(147) The CLF 22 allots TSAP4 as the Target SAP for the RF protocol ISO-DEP and TSAP5 as the Target SAP for the RF protocol NFC-DEP, and sends discovery notifications DISCOVER_NTF to the AP 21 in Steps S70 and S71. That is, the CLF 22 sends a discovery notification DISCOVER_NTF (TID1, TSAP4, NFC-A, PROTOCOL_ISO_DEP, SEL_RES, More=1) to the AP 21 in Step S70 and sends a discovery notification DISCOVER_NTF (TID1, TSAP5, NFC-A, PROTOCOL_NFC_DEP, SEL_RES, More=0) to the AP 21 in Step S71.

(148) The AP 21 selects NFC-DEP from among the two RF protocols and sends a discovery selection command DISCOVER_SELECT_COM with parameters TID1 as Target ID and TSAP5 as Target SAP in Step S72.

(149) In Step S73, the CLF 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES representing that the command has been understood to the AP 21.

(150) The high interface level is designated for the RF protocol NFC-DEP in the aforementioned interface level setting in Step S43. Thus, the CLF 22 performs protocol activation (ATR_REQ command for requesting attributes) and LLCP activation in Step S74.

(151) In Step S75, the CLF 22 receives the results of the response ATR_RES and the LLCP activation as a response to the ATR_REQ command from the target 11-1. Then, the CLF 22 sends an activation notification ACT_NTF representing the fact that the interface activation in the high level has been completed to the AP 21 in Step S76. The parameters of the activation notification ACT_NTF include received response ATR_RES as Activation Parameter and High I/F Level activate representing the activated interface level as Interface Type.

(152) After the completion of the interface activation, the application App (H) corresponding to the high interface level in the AP 21 is started to exchange data between the AP 21 and the target 11-1 (TID1) with the use of the RF protocol NFC-DEP (TSAP5) in Step S77.

(153) When predetermined data exchange is performed, and the application App (H) is completed, the AP 21 sends a deactivation command DEACT_COM to the CLF 22 in Step S78. The parameter Deactivation Type of the deactivation command DEACT_COM includes a command DSL_REQ to be sent to the target 11-1.

(154) The CLF 22 sends a deactivation response DEACT_RES representing the fact that the deactivation command DEACT_COM has been understood to the AP 21 in Step S79.

(155) Then, the CLF 22 sends a DSL_REQ command to the target 11-1 based on the parameter Deactivation Type included in the deactivation command DEACT_COM in Step S80. The CLF 22 receives the response DSL_RES from the target 11-1 and deactivates the interface in Step S81. The parameters relating to the target 11-1 (TID1) and NFC-DEP (TSAP5) are released by the deactivation of the interface.

(156) From Step S82, the target 11-3 (TID3) is selected as a communication counterpart, and communication is performed between the AP 21 and the target 11-3 (TID3).

(157) Specifically, the AP 21 sends a discovery selection command DISCOVER_SELECT_COM with parameters of TID3 (NFC-F) as Target ID and TSAP3 (T3T) as Target SAP to the CLF 22 in Step S82.

(158) The CLF 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES representing that the command has been understood to the AP 21 in Step S83.

(159) The low interface level is designated for the RF protocol T3T in the aforementioned interface level setting in Step S43. No protocol activation is performed in the low interface level. Therefore, the CLF 22 immediately sets NULL for the parameter of Activation Parameters and sends an activation notification ACT_NTF representing that the interface activation in the low level has been completed to the AP 21 in Step S84.

(160) After the completion of the interface activation, the application App (L) corresponding to the low interface level in the AP 21 is started to exchange data between the AP 21 and the target 11-3 (TID3) with the use of the RF protocol T3T (TSAP3) in Step S85.

(161) When predetermined data exchange is preformed, and the application App (L) is completed, the AP 21 sends a deactivation command DEACT_COM to the CLF 22 in Step S86. Since no protocol deactivation is performed in the same manner as the protocol activation, the parameter Deactivation Type of the deactivation command DEACT_COM is NULL.

(162) The CLF 22 sends a deactivation response DEACT_RES representing the fact that the deactivation command DEACT_COM has been understood to the AP 21 in Step S87. Thereafter, the CLF 22 deactivates the interface and releases the parameters relating to the target 11-3 (TID3) and T3T (TSAP3).

(163) As described above, the NFC device 1 (the AP 21 and the CLF 22) can be operated as a polling device and detect a plurality of targets 11 with different RF protocols. In addition, the NFC device 1 can sequentially exchange data with a plurality of detected targets 11.

(164) [Detailed Example of Sequence (in the Case of Listen Mode)]

(165) Next, description will be made of a sequence in which the NFC device 1 is operated in the Listen Mode with reference to FIGS. 14 and 15.

(166) In the examples of FIGS. 14 and 15, the RF protocol supported by the target 11-3 is NFC-DEP, unlike the example in FIG. 11.

(167) First, the AP 21 sends an initialization command INIT_COM in Step S101, and the CLF 22 sends an initialization response INIT_RES as a response to the AP 21 in Step S102. The initialization response INIT_RES includes an interface level for each RF protocol supported by the CLF 22 as described above.

(168) The AP 21 sends an interface level setting command SET_INTERFACE_LEVEL_COM for associating between the RF protocol and the interface level to the CLF 22 based on the interface level for each RF protocol supported by the CLF 22 in Step S103. In the example of FIG. 14, SET_INTERFACE_LEVEL_COM (2, Listen, ISO-DEP Protocol, Mid I/F Level, Listen, NFC-DEP Protocol, High I/F Level) is sent, and the middle level is designated for the RF protocol ISO-DEP and the high level is designated for NFC-DEP in the Listen Mode. Since the level of the RF protocols T1T, T2T, and T3T are fixed to the low level, the designation thereof is omitted. In addition, each interface level in the Poll Mode is also omitted.

(169) The CLF 22 sends an interface level setting response SET_INTERFACE_LEVEL_RES representing that the interface level setting command SET_INTERFACE_LEVEL_COM from the AP 21 has been understood to the AP 21 in Step S104.

(170) In Step S105, the AP 21 designates NFC-A, NFC-B, and NFC-F as the RF technologies of the detection targets and sends a discovery start command DISCOVER_START_COM to the CLF 22. The CLF 22 sends a discovery start response DISCOVER_START_RES representing that the discovery start command DISCOVER_START_COM has been understood to the AP 21 in Step S106.

(171) Then, the CLF 22 firstly sends a polling command for operating the NFC device 1 in the Poll Mode for NFC-A, NFC-B, and NFC-F designated as the RF technologies of the detection targets. Specifically, the CLF 22 sequentially sends commands SENS_REQ, SENSB_REQ, and SENSF_REQ for operating the NFC device 1 in the Poll mode in Steps S107 to S109.

(172) Since the responses for the commands SENS_REQ, SENSB_REQ, and SENSF_REQ have not been received, the CLF 22 then detects the polling command for operating the NFC device 1 in the Listen Mode and responds.

(173) Specifically, the CLF 22 receives the command SENS_REQ sent from the target 11-1 in Step S110 and sends the response SENS_RES to the target 11-1 in Step S111.

(174) In addition, the CLF 22 receives the command SENSB_REQ sent from the target 11-2 in Step S112 and sends the response SENSB_RES to the target 11-2 in Step S113.

(175) Furthermore, the CLF 22 receives the command SENSF_REQ sent from the target 11-3 in Step S114 and sends the response SENSF_RES to the target 11-3 in Step S115.

(176) In Step S116, the CLF 22 sends a response SRL_RES (ISO-DEP & NFC-DEP) representing that ISO-DEP and NFC-DEP are supported as the RF protocols to the target 11-1 detected first.

(177) Since the middle or higher interface level is designated for RF protocols ISO-DEP and NFC-DEP of the target 11-1, the CLF 22 waits for the protocol activation by the target 11-1. Then, the CLF 22 receives a RATS (Request for Answer To Select) for requesting for ATS from the target 11-1 in Step S117 and sends an ATS response for the command to the target 11-1 in Step S118. With such operations, the protocol activation by the RF protocol ISO-DEP is completed.

(178) After receiving the RATS command, the CLF 22 sends an activation notification ACT_NTF (TID1, TSAP1, NFC-A, PROTOCOL_ISO_DEP, ATS, Mid I/F Level activated) representing that the interface activation has been completed to the AP 21 in Step S119.

(179) In Step S120, the application App (M) corresponding to the middle interface level in the AP 21 is started to exchange data between the AP 21 and the target 11-1 (TID1) with the use of the RF protocol ISO-DEP (TSAP1).

(180) After the predetermined data exchange has been performed, the CLF 22 receives a command DESELECT from the target 11-1 as a PCD (reader writer) in Step S121 and sends a DESELECT response to the target 11-1 in Step S122. With such operations, the interface with the use of the RF protocol ISO-DEP is deactivated in the CLF 22.

(181) Then, the CLF 22 sends a deactivation notification DEACT_NTF to the AP 21 with the parameters of TID1 as Target ID, TSAP1 as Target SAP, and DESELECT as Deactivation Parameter in Step S123. The AP 21 receives the deactivation notification DEACT_NTF and then completes the application App (M).

(182) Although data exchange is then performed with the target 11-2, which has been secondly detected, for which allocation has been made such that Target ID=TID2 and Target SAP=TSAP2, the description of the processing will be omitted.

(183) Then, exchange is performed with the target 11-3, which has been thirdly detected, for which allocation has been made such that Target ID=TID3 and Target SAP=TSAP3.

(184) In Step S124 in FIG. 15, the CLF 22 receives a command ATR_REQ for requesting the attributes from the target 11-3. The high interface level is designated for the RF protocol NFC-DEP in the aforementioned Step S103. Therefore, the CLF 22 sends the response ATR_RES as a response to the command ATR_REQ and performs LLCP activation in Step S125.

(185) After the protocol activation and the LLCP activation, the CLF 22 sends an activation notification ACT_NTF to the AP 21 in Step S126. The parameters of the activation notification ACT_NTF include the received response ATR_RES as Activation Parameter and High I/F Level activated representing the activated interface level as Interface Type.

(186) In Step S127, the application App (H) corresponding to the high interface level in the AP 21 is started to exchange data between the AP 21 and the target 11-3 (TID3) with the use of the RF protocol NFC-DEP (TSAP3).

(187) After the predetermined data exchange, the CLF 22 receives a command DSL_REQ from the target 11-3 as the initiator (reader writer) in Step S128 and sends a response DSL_RES to the target 11-3 in Step S129. With such operations, the interface with the use of the RF protocol NFC-DEP is deactivated in the CLF 22.

(188) Then, the CLF 22 sends a deactivation notification DEACT_NTF to the AP 21 in Step S130. Specifically, the CLF 22 sends a deactivation notification DEACT_NTF with parameters of TID3 as Target ID, TSAP3 as Target SAP, and DSL_REQ as Deactivation Parameter. The AP 21 receives the deactivation notification DEACT_NTF and then completes the application App (H).

(189) The NFC device 1 (the AP 21 and the CLF 22) can be operated as a listening device and detects a plurality of targets 11 with different RF protocols. In addition, the NFC device 1 can sequentially exchange data with the detected plurality of targets 11.

(190) The NFC device 1 for the near field wireless communication based on ISO/IEC 18092 or ISO/IEC 14443 is operated while being functionally divided into the AP 21 and the CLF 22. The AP 21 mainly executes the application and performs overall control of the NFC device 1. The CLF 22 is disposed between the AP 21 and the target 11 and mainly sends and receives RF data with the target 11 (a PICC (IC card) of ISO/IEC 14443 or a target of ISO/IEC 18092) through the antenna 24.

(191) The AP 21 selects (designates) one interface level from among a plurality of interface levels supported by the CLF 22 for each RF protocol and notifies the CLF 22. The plurality of interface levels are classified depending on up to which level of processing the CLF 22 positioned in between is burdened when the NFC device 1 exchanges data with the target 11. Specifically, when the interface level is classified into three stages including a low level, a middle level, and a high level, the amount of the processing allotted to the CLF 22 is the largest at the high level, and the amount of the processing allotted to the CLF 22 is the smallest at the low level. The AP 21 obtains information regarding the interface level supported by the CLF 22 and designates a predetermined interface level for each RF protocol with respect to the CLF 22. Then, the AP 21 activates and executes an application App at a level corresponding to the designated interface level. With such a configuration, the AP 21 can concentrate on the execution of the application processing by allotting processing, which can be executed by the CLF 22, to the CLF 22. In addition, when the CLF 22 supports a higher interface level, the CLF 22 and the AP 21 can exchange data at a higher interface level (data exchange in units in which the application of the AP 21 can more easily perform processing) by setting the interface level to be as high as possible. With such a configuration, the target 11 and the NFC DEVICE 1 can effectively exchange data.

(192) When the CLF 22 is operated as a polling device, the CLF 22 sends a polling command, detects (discovers) a plurality of targets 11, and then notifies the AP 21 of all detected targets 11 (discovery notification DISCOVER_NTF). Then, a target 11 for communication is sequentially selected one by one by the AP 21 from among the plurality of detected targets 11, and communication (data execution by the application) is executed. With respect to each of the selected targets 11, operations including interface activation, application execution in accordance with the interface level (including start and completion), and interface deactivation are performed. With such operations, it is possible to effectively exchange data with a plurality of targets 11 with different RF technologies or RF protocols.

(193) On the other hand, when the CLF 22 is operated as a listening device, a target 11 is selected as a communication counterpart from among a plurality of targets 11, with which a communication link has been established, in the detection order. The CLF 22 activates the interface corresponding to the RF protocol of the selected target 11 and notifies the AP (activation notification ACT_NTF). The AP 21 executes (including start and completion) the application in accordance with the interface level of the target 11 for which the activation notification has been made. Accordingly, communication (data exchange by the application) with the plurality of targets 11 with which a communication link has been established is sequentially executed. With such a configuration, it is possible to effectively exchange data with a plurality of targets 11 with different RF technologies or RF protocols.

(194) The above description was made of an example in which the processing necessary for the data communication between the target 11 and the AP 21 is performed by CLF 22 instead in accordance with the interface level designated for a predetermined RF protocol.

(195) However, the CLF 22 performs processing to be performed by the AP 21 instead of the AP 21 in accordance with the interface level designated for a predetermined RF protocol in the data exchange processing between the target 11 and the AP 21, in some cases.

(196) For example, if the NFC device 1 is in a reader/writer mode, and the interface level activated by the CLF 22 is the high level, the CLF 22 performs the processing for accessing the NDEF data instead of the AP 21. Here, the NDEF data is data in a common data format NDEF (NFC Data Exchange Format) used by applications.

(197) Specific description will be made of an example of an NFC FORUM: Type 3 Tag Operation which is a specification of Type 3 from among the Tag Operations defining a command for accessing the NDEF data. When the NDEF data is read in the NFC FORUM Type 3 Tag Operation, Polling Command/Response and Check Command/Response are exchanged between the target 11 and the NFC device 1. The exchange of Check Command/Response is performed a plurality of times in some cases in accordance with the NDEF data size. When Check Command/Response has been exchanged a plurality of times, the data obtained by coupling the data obtained by Check Command/Response exchanged the plurality of times becomes the NDEF data.

(198) When the interface level of the CLF 22 is the high level, the CLF 22 voluntarily executes Polling Command/Response and Check Command/Response once or more. When Check Command/Response is exchanged a plurality of times, the CLF couples the data obtained by exchanging Check Command/Response the plurality of times to generate NDEF data. On the other hand, the interface level of the CLF 22 is the middle or low level, the CLF 22 only relays Polling Command/Response supplied from the AP 21 and Check Command/Response exchanged once or more. The AP 21 also performs the processing of generating the NDEF data from the data obtained by exchanging Check Command/Response the plurality of times.

(199) The steps described in the flowchart may of course be executed in a time-series manner in the order described in this specification, or without executing the steps in the time-series manner, the steps may be executed in parallel or at a necessary timing such as by the timing of calling or the like.

(200) In addition, the system in this specification represents the entire apparatus including a plurality of apparatuses.

(201) The embodiments of the present disclosure are not limited to the aforementioned embodiments, and various modifications can be made within the range of the scope of the present disclosure.

(202) For example, a program executed to perform a method according to some embodiments need not be stored in a non-transitory storage medium. The program can also be stored in a transitory storage medium, such as a propagating wave.