JP6760452B2 - Communication device and communication method - Google Patents

Description

The present invention relates to a communication device and a communication method, and more particularly to a communication device and a communication method capable of providing an interface capable of responding even when a plurality of types of remote targets and protocols are detected.

A short-range wireless communication system that uses an IC (Integrated Circuit) card to perform wireless communication over a short distance without contact is widely used. For example, it is well known to be used as an electronic ticket or electronic money. In addition, recently, mobile phones equipped with electronic tickets and electronic money functions by non-contact wireless communication have become widespread.

Short-range wireless communication systems have rapidly become widespread worldwide and have become an international standard. For example, international standards include ISO / IEC 14443, which is a standard for proximity IC card systems, and ISO / IEC 18092, which is a standard for NFCIP (Near Field Communication Interface and Protocol) -1.

Short-range wireless communication according to ISO / IEC 18092 has an active communication mode and a passive communication mode. The active communication mode is a communication mode in which an electromagnetic wave is output and data is transmitted by modulating the electromagnetic wave in each of a plurality of communication devices that transmit and receive data. In the passive communication mode, one communication device (initiator) of a plurality of communication devices outputs an electromagnetic wave and transmits data by modulating the electromagnetic wave. The other communication device (target) among the plurality of communication devices transmits data by load-modulating the electromagnetic wave output by the initiator.

In ISO / IEC 18092 passive communication mode (hereinafter referred to as type F), data is encoded by Manchester for data transmission between the reader / writer and the IC card. In Type F, 212 kbps and 424 kbps are adopted as data communication rates. The FeliCa (registered trademark) method of Sony Corporation, the applicant of this application, corresponds to type F.

Also, in the ISO / IEC 14443 IC card system, for example, there are various communication methods called type A and type B.

Type A is adopted as the MIFARE (registered trademark) method of Philips. In Type A, data transmission from the reader / writer to the IC card is encoded by a mirror (Miller), and data transmission from the IC card to the reader / writer is encoded by Manchester. Will be. In Type A, 106 to 847 kbps (kilo bit per second) is adopted as the data communication rate.

In type B, data is encoded by NRZ for data transmission from the reader / writer to the IC card, and data is encoded by NRZ-L for data transmission from the IC card to the reader / writer. Further, in type B, 106 kbps is adopted as a data communication rate.

A communication device that performs short-range wireless communication according to ISO / IEC 18092 or ISO / IEC 14443 is hereinafter referred to as an NFC device. Some NFC devices are functionally separated into NFCC (NFC Controller) and DH (Device Host), and protocols and commands exchanged between NFCC and DH are defined (see, for example, Patent Document 1). NFCC mainly sends and receives RF data to and from remote targets (PICC (IC card) of ISO / IEC 14443 and targets of ISO / IEC 18092) via antennas, and DH mainly executes applications and NFC. Control the entire device.

Special Table 2009-515250

However, Patent Document 1 assumes only the case where any one of the remote targets and protocols of ISO / IEC 14443 type A or type B, ISO / IEC 18092 type F, etc. is detected. In other words, it is an interface between NFCC and DH on the premise that only one type of remote target or protocol is detected. Therefore, it cannot be applied when multiple types of remote targets and protocols are detected, and an interface between NFCC and DH that can support multiple types of remote targets and protocols is desired.

The present invention has been made in view of such a situation, and makes it possible to provide an interface that can handle even when a plurality of types of remote targets and protocols are detected.

The communication device of one aspect of the present invention includes a non-contact communication control unit that supports a plurality of interface levels and transmits / receives data to / from another communication device by non-contact communication. A predetermined interface is selected from the plurality of interfaces based on receiving a command transmitted from a processing unit that executes an application for exchanging data with another communication device.

The communication method of one aspect of the present invention corresponds to the communication device of one aspect of the present invention.

In one aspect of the present invention, the non-contact communication control unit supports a plurality of interface levels, and data is transmitted / received to / from another communication device by non-contact communication. Then, the non-contact communication control unit selects a predetermined interface from a plurality of interfaces based on receiving a command transmitted from a processing unit that executes an application for exchanging data with another communication device. ..

According to one aspect of the present invention, it is possible to provide an interface that can handle the detection of a plurality of types of remote targets and protocols.

It is a block diagram which shows the structural example of one Embodiment of the communication system to which this invention is applied. It is a figure which shows the configurable interface level for each RF protocol. It is the figure which showed the difference of processing by the interface level in the case of the communication layer for P2P communication between NFC devices. It is a figure explaining the detailed format of each message. It is a figure explaining the detailed format of each message. It is a figure explaining the detailed format of each message. It is a figure explaining the detailed format of each message. It is a figure explaining the detailed format of each message. It is a figure explaining the detailed format of each message. It is a figure which shows the list of messages. It is a flowchart explaining the outline of a sequence. It is a figure explaining the detailed example of the sequence in the case of Poll Mode. It is a flowchart explaining the detailed example of the sequence in the case of Poll Mode. It is a flowchart explaining the detailed example of the sequence in the case of Listen Mode. It is a flowchart explaining the detailed example of the sequence in the case of Listen Mode.

[Example of configuration of communication system to which the present invention is applied]
FIG. 1 shows a configuration example of an embodiment of a communication system to which the present invention is applied.

The communication system of FIG. 1 is composed of NFC device 1 and NFC devices 11-1 to 11-3.

NFC device 1 and NFC devices 11-1 to 11-3 are communication devices that perform short-range wireless communication by ISO / IEC 18092 and / or ISO / IEC 14443. The NFC device 1 and the NFC devices 11-1 to 11-3 can operate as either a polling device or a listening device.

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

When the listening device receives a polling command that the polling device sends by forming an RF field, it responds with a polling response. In other words, the listening device behaves as an ISO / IEC 14443 PICC or as an ISO / IEC 18092 target.

Therefore, the NFC device 1 and the NFC devices 11-1 to 11-3 can each have the same hardware configuration.

In the following, in order to facilitate the distinction between the NFC device 1 and the NFC devices 11-1 to 11-3, the NFC devices 11-1 to 11-3 are referred to as remote targets 11-1 to 11-3, respectively. Further, when it is not necessary to distinguish the remote targets 11-1 to 11-3, it is simply referred to as the remote target 11 (or NFC device 11).

The NFC device 1 includes one DH (Device Host) 21, one NFCC (NFC Controller) 22, and zero or more NFCEE (NFC Execution Environment) 23. Since the number of NFCEE23 is 0 or more, it may be 0 (may be omitted).

The DH 21 controls the entire NFC device 1, generates a command (CMD) for controlling the NFC 22, and interprets the execution result for the command. The DH21 exchanges messages with the NFCC 22 according to the NCI (NFC Controller Interface). The DH 21 also executes an application that exchanges data with the remote target 11. Applications include, for example, applications that perform data exchange processing of business cards and address books in P2P (Peer-to-Peer) communication, electronic money payment processing between a reader / writer / IC card, and the like. The DH21 internally stores three applications App (H), App (M) and App (L) having different levels according to the interface level (interface level) of the NFCC 22 as an application for exchanging data. are doing.

The NFCC 22 is arranged between the DH 21 and the remote target 11, is an interface that mediates between the DH 21 and the remote target 11, and controls the route so that the DH 21 and the NFC EE 23 can exchange data with the remote target 11. The NFCC 22 has a plurality of interface levels as the level of the interface that mediates between the DH 21 and the remote target 11. In this embodiment, the NFCC 22 has three levels of interface levels: low level, medium level, and high level. The NFCC 22 exchanges messages with the DH 21 according to the NCI, and transmits / receives RF data via the antenna 24 based on a command (CMD) from the DH 21.

NCI is a logical interface between DH21 and NFCC22, and NCI defines commands (CMD) and notifications (NTF) in a predetermined format, which will be described later.

The NFCEE 23 processes and retains secure data among the processes required for the NFC device 1 to exchange data with the remote target 11. In the example of FIG. 1, three NFCEEs 23-1 to 23-3 are provided in the NFC device 1. NFCEE23-1 and 23-2 are connected to NFCC22 to hold and process secure data handled by NFCC22, and NFCEE23-3 is connected to DH21 to hold and process secure data handled by DH21. A required number of NFCEE 23s can be provided in the NFC device 1, and can be omitted if unnecessary.

The antenna 24 constitutes a closed-loop coil, and an electromagnetic wave (RF data) is output by changing the current flowing through the coil.

The NFC device 1 configured as described above supports one or more of the following three RF technologies.
<RF technology>
(1) NFC-A ・ ・ ・ ISO / IEC 14443 Type A communication method (2) NFC-B ・ ・ ・ ISO / IEC 14443 Type B communication method (3) NFC-F ・ ・ ・ ISO / IEC 18092 212 kbps and 424 kbps communication methods
NFC-A is an abbreviation for Type A in ISO / IEC 14443, NFC-B is an abbreviation for Type B in ISO / IEC 14443, and NFC-F is an abbreviation for 212 kbps in ISO / IEC 18092. Abbreviation for 424kbps communication method.

In addition, NFC device 1 supports one or more of the following six RF protocols.
<RF protocol>
(1) T1T ・ ・ ・ TYPE 1 TAG PLATFORM Protocol (based on Type NFC-A)
(2) T2T ・ ・ ・ TYPE 2 TAG PLATFORM Protocol (based on Type NFC-A)
(3) T3T ・ ・ ・ TYPE 3 TAG PLATFORM Protocol (based on Type NFC-F)
(4) ISO-DEP ・ ・ ・ ISO-DEP Protocol (ISO / IEC 14443-4 based on Type NFC-A or NFC-B)
/ TYPE 4 TAG PLATFORM Protocol (based on Type NFC-A or NFC-B)
(5) NFC-DEP ・ ・ ・ NFC-DEP Protocol (ISO / IEC 18092 transport protocol based on
NFC-A or NFC-F)
(6) Prop: Proprietary Protocol
T1T is an abbreviation for TYPE 1 TAG PLATFORM Protocol (based on NFC-A) in the present specification, and T2T is an abbreviation for TYPE 2 TAG PLATFORM Protocol (based on NFC-A). The same applies to T3T, ISO-DEP, NFC-DEP, and Prop.

[About interface level]
In the NFC device 1, when exchanging data with the remote target 11, the processing for that purpose can be shared between the DH 21 and the NFCC 22. In other words, the processing required for the DH 21 to exchange data with the remote target 11 can be taken over by the intermediate NFCC 22. At this time, to what level the NFCC 22 takes over the processing required for data exchange is determined by the interface level designated (notified) from the DH 21 to the NFCC 22.

Of the three levels of interface level that NFCC22 has, low level, medium level, and high level, the high level has the most processing handled by the NFCC 22 as an interface, and the low level has the least processing handled by the NFCC 22 as an interface. .. The interface level needs to be set for each RF protocol, and in NFCC22, the interface level that can be set is determined by the RF protocol.

FIG. 2 shows the interface levels that the NFCC 22 can configure for the RF protocol.

Only low interface levels can be set for the T1T, T2T, and T3T RF protocols. The RF technology when the RF protocol is T1T and T2T is NFC-A, and the RF technology when the RF protocol is T3T is NFC-F.

For each of the ISO-DEP and NFC-DEP RF protocols, low-level, medium-level, and high-level interface levels can be set. If the RF protocol is ISO-DEP, the RF technology is NFC-A or NFC-B, and if the RF protocol is NFC-DEP, the RF technology is NFC-A or NFC-F.

Only low levels of interference can be configured for Prop's RF protocol.

FIG. 3 is a diagram showing a difference in processing depending on the interface level in the case of a communication layer for P2P communication between NFC devices.

At the low interface level, the NFCC 22 has ISO / IEC 18092 Frame format, Anticollision, Bit coding, Modulation / Load modulation functions. At the medium level interface level, the NFCC 22 also has features up to the ISO / IEC 18092 transport protocol. That is, the NFCC 22 has the functions of Protocol activation / deactivation, Segmentation and reassembly, and Retransmission in addition to the low-level functions. At the high level of interface, NFCC22 has functions up to LLCP (NFC Forum Logical Link Control Protocol), which is a higher layer protocol of ISO / IEC 18092 transport protocol.

The interface level of the NFCC 22 can be appropriately determined and implemented for each RF protocol from among these three stages according to the application requirements assumed by the NFCC 22 and the cost of the IC chip.

In the initial process, the NFCC 22 notifies the DH 21 of information about how much interface level it supports. The DH 21 grasps the interface level supported by the NFCC 22, selects the optimum interface level from the interface levels supported by the NFCC 22 according to the requirements of the application assumed by the DH 21, and designates the interface level as the NFCC 22. If the NFCC 22 supports all interface levels, the DH21 can select the optimal interface level depending on the processing supported by the application. For example, if the DH 21 wants to execute the application with less processing, the DH 21 may select a high level interface level and specify it in the NFCC 22.

[Message format]
Next, the details of the message defined as NCI will be described with reference to FIGS. 4 to 9.

There are three types of messages: CMD (command) from DH21 to NFCC22, RSP (response) from NFCC22 to DH21, and NTF (notification) from NFCC22 to DH21.

FIG. 4 shows the formats of the initialization command “INIT_CMD” and the initialization response “INIT_RSP”.

The initialization command "INIT_CMD" is a message for initializing NCI and exchanging the capabilities of NFCC22 and DH21. The initialization command "INIT_CMD" includes "Version" indicating the NCI version (version number) of the DH21 and "NCI Features" indicating the capabilities of the DH21 as parameters. In "NCI Features", information about the communication control function supported by the DH21, for example, information about the presence / absence of a flow control function, a card emulation function, another message creation function, and the like is input.

The initialization response "INIT_RSP" is a message that responds to the initialization command. The initialization response "INIT_RSP" includes, as parameters, "Status" indicating the response result of the initialization command "INIT_CMD", "Version" indicating the NCI version of NFCC22, "NCI Features" indicating the capability of NFCC22, and NFCC22. Includes "NCI Interfaces" representing interface capabilities. In "NCI Features", information about the communication control function supported by NFCC22, for example, information about the presence / absence of a flow control function, a battery OFF mode function, a routing function using a card embroidery application identifier, etc. is input. .. In "NCI Interfaces", the interface level for each RF protocol supported by NFCC22 is input.

DH21 and NFCC22 confirm each other's version by the initialization command "INIT_CMD" and the initialization response "INIT_RSP", and if the version of DH21 is equal to or higher than the version of NFCC22, the message according to NCI It is possible to communicate. On the other hand, when the version of DH21 is lower than the version of NFCC22, DH21 performs error processing such as outputting an error message, for example.

FIG. 5 shows the formats of the interface level setting command “DISCOVER_MAP_CMD” and the interface level setting response “DISCOVER_MAP_RSP”.

The interface level setting command "DISCOVER_MAP_CMD" is a message that associates the RF protocol with the interface level. The interface level setting command "DISCOVER_MAP_CMD" includes the number of interface level setting data [n] and n interface level setting data as parameters.

The interface level setting data for one RF protocol includes "Mode" indicating the mode (Poll Mode / Listen Mode) of the remote target 11, "Protocol" indicating the RF protocol to be used, and "Interface level" indicating the interface level to be used. ”Is included. That is, for one RF protocol (“Protocol”), the interface level (“Interface level”) can be set for each mode of Poll Mode and Listen Mode. For example, if the RF protocol is ISO-DEP and Poll Mode, it can be set to a medium level interface level, and if the RF protocol is ISO-DEP and Listen Mode, it can be set to a high level interface level. Therefore, the number n of interface level setting data is at most twice the number of RF protocols.

The interface level setting response "DISCOVER_MAP_RSP" is a message that responds to the interface level setting command. The interface level setting response "DISCOVER_MAP_RSP" includes OK = 1 or NG = 0 indicating the response result as a parameter.

FIG. 6 shows the formats of the discovery start command “DISCOVER_START_CMD”, the discovery start response “DISCOVER_START_RSP”, the discovery stop command “DISCOVER_STOP_CMD”, and the discovery stop response “DISCOVER_STOP_RSP”.

The discovery start command "DISCOVER_START_CMD" is a message requesting the start of detection of the remote target 11. The parameters of the discovery start command "DISCOVER_START_CMD" include "Discovery Type" representing the RF technology to be detected as many as the number of RF technologies desired to be detected.

The discovery start response "DISCOVER_START_RSP" is a message in response to the discovery start command. The discovery start response "DISCOVER_START_RSP" includes OK = 1 or NG = 0 indicating the response result as a parameter.

The discovery stop command "DISCOVER_STOP_CMD" is a message requesting the detection stop of the remote target 11. The discovery stop command "DISCOVER_STOP_CMD" has no parameters.

The discovery stop response "DISCOVER_STOP_RSP" is a message in response to the discovery stop command. The discovery stop response "DISCOVER_STOP_RSP" includes OK = 1 or NG = 0 indicating the response result as a parameter.

FIG. 7 shows the formats of the discovery selection command “DISCOVER_SELECT_CMD”, the discovery selection response “DHISCOVER_SELECT_RSP”, the deactivation command “DEACTIVATE_CMD”, and the deactivation response “DEACTIVATE_RSP”.

The discovery selection command "DISCOVER_SELECT_CMD" is a message for selecting the RF technology (remote target 11) and the RF protocol. The selected RF technology (remote target 11) is input to the parameter "Target Handle" of the discovery selection command "DISCOVER_SELECT_CMD", and the selected RF protocol is input to the parameter "Target Port".

The discovery selection response "DHISCOVER_SELECT_RSP" is a message that responds to the discovery selection command. The discovery selection response "DHISCOVER_SELECT_RSP" includes OK = 1 or NG = 0, which represents the response result, as parameters.

The deactivation command "DEACTIVATE_CMD" is a message requesting the end of data exchange with the remote target 11. The deactivation command "DEACTIVATE_CMD" includes parameters such as "Target Handle" corresponding to RF technology, "Target Port" corresponding to RF protocol, and "Deactivation Type" which is a command to send to a remote target. ..

The deactivation response "DEACTIVATE_RSP" is a message that responds to the deactivation command "DEACTIVATE_CMD". The deactivation response "DEACTIVATE_RSP" includes OK = 1 or NG = 0, which represents the response result, as parameters.

FIG. 8 shows the formats of the discovery notification “DISCOVER_NTF”, the activation notification “ACTIVATE_NTF”, and the deactivation notification “DEACTIVATE_NTF”.

The discovery notification "DISCOVER_NTF" is a message notifying the remote target and its RF technology and RF protocol. There may be multiple combinations of remote targets, RF technologies, and RF protocols, as with the discovery selection command "DISCOVER_SELECT_CMD" described above.

In the discovery notification "DISCOVER_NTF", as parameters, "Target Handle" which is the number assigned to the RF technology by NFCC22, "Target Port" which is the number assigned to the RF protocol by NFCC22, and "Discovery" indicating the detected RF technology. Includes "Type", "RF Protocol" representing the RF protocol of the remote target 11, "Technology Specific Parameters" representing RF technology-specific parameters, and "More" indicating the presence or absence of the next discovery notification DISCOVER_NTF.

Activation notification "ACTIVATE_NTF" is a message notifying the activation (activation, activation) of a specific interface level. The activation notification "ACTIVATE_NTF" includes the above-mentioned "Target Handle", "Target Port", "Discovery Type", and "RF Protocol" as parameters, "Activation Parameters" indicating activation parameters, and activation. Includes "Interface Type", which represents the interface level.

Deactivation notification "DEACTIVATE_NTF" is a message notifying the deactivation (deactivation) of a specific interface level. The deactivation notification "DEACTIVATE_NTF" includes the above-mentioned "Target Handle" and "Target Port" as parameters and "Deactivation Parameters" representing deactivation parameters.

FIG. 9 shows a list of messages described with reference to FIGS. 4-8.

[Sequence overview]
Next, with reference to FIG. 10, the outline of the sequence performed between the DH 21 and the NFCC 22 when the DH 21 exchanges data with the remote target 11 will be described.

When the DH 21 exchanges data with the remote target 11, the sequence performed by the DH 21 and the NFCC 22 is roughly composed of the following five steps.
(1) Initialization process for setting interface level for RF protocol (2) Discovery process for remote target 11 (3) Interface activation process (4) Data exchange process (5) Interface deactivation process
When the DH 21 exchanges data with a plurality of remote targets 11, steps (3) to (5) are sequentially executed for each of the plurality of remote targets 11.

(1) Initialization process for setting the interface level for the RF protocol In the initialization process, the DH21 specifies the interface level of the NFCC22 by sending the interface level setting command "DISCOVER_MAP_CMD" after confirming the interface capability of the NFCC22. (Notice. In FIG. 10, the initialization process corresponds to the process of step S11 of DH21 and the process of step S21 of NFCC22.

(2) Discovery Process of Remote Target 11 The discovery process is a process of detecting the remote target 11. When the DH 21 transmits the discovery start command "DISCOVER_START_CMD" requesting the start of detection of the remote target 11 to the NFCC 22 in step S12, the NFCC 22 starts the process of detecting the remote target 11 in step S22.

In the detection of the remote target 11, the NFCC 22 alternately repeats the Poll Mode and the Listen Mode. That is, the NFCC 22 repeatedly sends a polling command from itself, waits for a response from the other party (Poll Mode), and then waits for a polling command from the other party (Listen Mode).

In Poll Mode, when the NFCC 22 receives a response to the transmitted polling command, it considers that a communication link with the remote target 11 has been established, and maintains the mode (Poll Mode) at that time. In Poll Mode, the NFCC 22 can act as a PCD or Initiator and send commands.

On the other hand, in Listen Mode, when the NFCC 22 sends a response to the polling command from the other party, it is considered that the communication link with the remote target 11 has been established, and the mode (Listen Mode) at that time is maintained. In Listen Mode, the NFCC 22 can act as a PICC or Target and respond (send a response) to the received command.

In step S23, the NFCC 22 notifies the DH 21 of the detected remote target 11 by the discovery notification “DISCOVER_NTF”. When the NFCC 22 detects a plurality of remote targets 11, a discovery notification "DISCOVER_NTF" is transmitted for each remote target 11 for all the detected remote targets 11.

(3) Interface activation process The DH21 that received the discovery notification "DISCOVER_NTF" selects a predetermined remote target 11 from the received ones in step S13, and sends the discovery selection command "DISCOVER_SELECT_CMD" to the NFCC22. To do.

In step S24, the NFCC 22 receives the discovery selection command "DISCOVER_SELECT_CMD" and activates the interface of one selected remote target 11 based on the discovery selection command "DISCOVER_SELECT_CMD". Then, the NFCC 22 notifies the DH 21 by the activation notification "ACTIVATE_NTF" that the interface of the remote target 11 selected by the discovery selection command "DISCOVER_SELECT_CMD" has been activated.

Note that this process is a process in which the mode is Poll Mode, and in the case of Listen Mode, the process is different because the DH 21 cannot select the remote target 11. That is, in Listen Mode, when the NFCC 22 holds a state machine for a plurality of RF technologies, the NFCC 22 responds with the plurality of RF technologies. If the NFCC 22 holds a state machine for one RF technology, the NFCC 22 responds with the first RF technology it detects. The NFCC 22 activates the interface of the remote target 11 that responded, and notifies the DH 21 to that effect by the activation notification "ACTIVATE_NTF". In Listen Mode, the remote target 11 sends a command, so the NFCC 22 performs processing according to the received command.

(4) Data exchange processing
Upon receiving the activation notification "ACTIVATE_NTF" from the NFCC 22, the DH 21 starts the application in step S14. At this time, the DH 21 selects one of the applications App (H), App (M), and App (L) according to the interface level of the NFCC 22.

In step S15, the DH 21 exchanges data with the remote target 11 via the NFCC 22 by the launched application. The NFCC 22 exchanges data between the DH 21 and the remote target 11 in step S25.

(5) Interface deactivation processing
In Poll Mode, the application started by DH21 sends the deactivation command "DEACTIVATE_CMD" to NFCC22 when the application ends. In step S26, the NFCC 22 receives the deactivation command "DEACTIVATE_CMD", deactivates the interface of the remote target 11 during communication, and disconnects the communication link with the remote target 11.

On the other hand, in Listen Mode, the NFCC 22 sends a deactivation notification "DEACTIVATE_NTF" to the DH 21 after disconnecting the communication link with the remote target 11 during communication. In step S16, the DH 21 terminates the application when it receives the deactivation notification "DEACTIVATE_NTF".

In the above, a rough sequence flow has been described for an example of communicating with one remote target 11.

[Detailed example of sequence (for Poll Mode)]
Next, with reference to FIGS. 11 to 13, details of the sequence performed by the DH 21 and the NFCC 22 when the DH 21 exchanges data with a plurality of remote targets 11 will be described.

FIG. 11 shows the RF technologies and protocols supported by each of the remote targets 11-1 to 11-3.

The remote target 11-1 supports NFC-A as an RF technology and two RF protocols, ISO-DEP and NFC-DEP. Remote target 11-2 supports NFC-B as an RF technology and ISO-DEP as an RF protocol. Remote target 11-3 supports NFC-F as an RF technology and T3T as an RF protocol.

In FIG. 11, the “Target Handle” and “Target Port” described on the right side of the RF protocol column refer to the identifier assigned by the NFCC 22 to the detected remote target 11 in the series of sequences shown in FIGS. 12 and 13. Shown.

[Poll Mode sequence example]
12 and 13 are flowcharts showing a sequence in which the NFC device 1 (NFCC22) operates in Poll Mode and communicates with three remote targets 11-1 to 11-3 having different RF technologies.

First, in step S41, the DH 21 transmits an initialization command INIT_CMD, and in response, the NFCC 22 transmits an initialization response INIT_RSP to the DH 21 in step S42. The initialization response INIT_RSP contains the interface level for each RF protocol supported by NFCC22, as described above.

In step S43, the DH 21 transmits to the NFCC 22 an interface level setting command DISCOVER_MAP_CMD that associates the RF protocol with the interface level based on the interface level for each RF protocol supported by the NFCC 22. In step S43, DISCOVER_MAP_CMD (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 being transmitted. This sets the interface level in Poll Mode to medium level when the RF protocol is ISO-DEP, high level when NFC-DEP, and low level when T1T, T2T, and T3T.

In this example, the RF protocols of T1T, T2T, and T3T are also set, but the RF protocols of T1T, T2T, and T3T can only be set at a low interface level, so they are low. The level can be fixed and command transmission and setting can be omitted.

Further, since the sequence of FIG. 12 is an explanation of an example in which the NFC device 1 (NFCC22) operates in Poll Mode, the interface level setting command DISCOVER_MAP_CMD in step S43 omits the specification of each interface level in Listen Mode. ing.

In step S44, the NFCC 22 transmits an interface level setting response DISCOVER_MAP_RSP to the effect that the interface level setting command DISCOVER_MAP_CMD from the DH 21 is accepted.

Then, in step S45, the DH 21 specifies NFC-A, NFC-B, and NFC-F as the RF technologies to be detected, and transmits the discovery start command DISCOVER_START_CMD to the NFC C22. In step S46, the NFCC 22 transmits a discovery start response DISCOVER_START_RSP to the effect that the discovery start command DISCOVER_START_CMD has been accepted to the DH 21.

Then, NFCC 22 transmits a command for detecting the remote target 11 for NFC-A, NFC-B, and NFC-F designated as RF technologies to be detected. Specifically, in step S47, the NFCC 22 transmits the command SENS_REQ of NFC-A, and in step S48, receives the response SENS_RES to the command SENS_REQ transmitted from the remote target 11-1 existing in the RF field. To do. At the time of receiving response SENS_RES, the RF protocol of remote target 11-1 is still unknown.

Further, the NFCC 22 transmits the NFC-B command SENSB_REQ in step S49, and receives the response SENSB_RES to the command SENSB_REQ transmitted from the remote target 11-2 existing in the RF field in step S50. By receiving the response SENSB_RES, it is also known that the RF protocol of the remote target 11-2 is ISO-DEP.

Further, the NFCC 22 transmits the NFC-F command SENSF_REQ in step S51, and receives the response SENSF_RES to the command SENSF_REQ transmitted from the remote target 11-3 existing in the RF field in step S52. By receiving the response SENSF_RES, it is also known that the RF protocol of the remote target 11-3 is T3T.

If the remote target 11 is not detected, the NFCC 22 alternately repeats the Poll Mode and the Listen Mode, but since the remote targets 11-1 to 11-3 are detected in the Poll Mode, the Listen Mode operation is not performed.

In steps S53 to S55, the NFCC 22 transmits three discovery notifications DISCOVER_NTF notifying the detected remote targets 11-1 to 11-3 to the DH21. Specifically, in step S53, the NFCC 22 assigns "TH1" as the Target Handle and "TP1" as the Target Port for the detected remote target 11-1 of NFC-A, and transmits the discovery notification DISCOVER_NTF to the DH21.

In step S54, the NFCC 22 assigns “TH2” as the Target Handle and “TP2” as the Target Port for the detected remote target 11-1 of the NFC-B, and transmits the discovery notification DISCOVER_NTF to the DH 21. In step S55, the NFC C22 assigns “TH3” as the Target Handle and “TP3” as the Target Port for the detected NFC-F target 11-1, and transmits the discovery notification DISCOVER_NTF to the DH21.

Here, in the discovery notification DISCOVER_NTF transmitted in steps S53 and S54, the discovery notification DISCOVER_NTF is also transmitted next, so that the final parameter "More" of the discovery notification DISCOVER_NTF is "1". On the other hand, in the discovery notification DISCOVER_NTF in step S55, since there is no discovery notification DISCOVER_NTF to be transmitted next, the final parameter "More" is "0".

In the subsequent sequences, the remote target 11 is specified by the Target Handle and Target Port assigned by the NFCC 22 between the DH 21 and the NFCC 22, and a message is exchanged.

In step S56, the DH 21 selects communication with the remote target 11-2 from the detected remote targets 11-1 to 11-3, and sets "Target Handle" = TH2 and "Target Port" = TP2 as parameters. Send the discovery selection command DISCOVER_SELECT_CMD.

In step S57, the NFCC 22 receives the discovery selection command DISCOVER_SELECT_CMD and transmits the discovery selection response DHISCOVER_SELECT_RSP to the effect that the command is accepted to the DH21.

For the ISO-DEP RF protocol represented by "Target Port" = TP2 included in the discovery selection command DISCOVER_SELECT_CMD, the above-mentioned interface level setting command DISCOVER_MAP_CMD specifies a medium level interface level. At the medium level interface level, protocol activation is a process performed by the NFCC 22, as described with reference to FIG.

Therefore, the NFCC 22 performs protocol activation in step S58. That is, the NFCC 22 notifies the remote target 11-2 of its own attribute (specification) and sends an ATTRIB command requesting the attribute of the remote target 11-2 to the remote target 11-2. In step S59, the NFCC 22 receives an ATTA response from the remote target 11-2 as a response to the ATTRIB command.

Upon receiving the ATTA response, the NFCC 22 sends an activation notification ACTIVATE_NTF to the DH21 in step S60 to the effect that the activation of the interface at the medium level interface level is complete. The parameters of the activation notification ACTIVATE_NTF include the received response "ATTA" as "Activation Parameters" and "Mid I / F Level activated" indicating the activated interface level as "Interface Type".

After the interface activation is completed, in step S61, the application App (M) corresponding to the middle level interface level in DH21 is started, and ISO-DEP is started between DH21 and the remote target 11-2 (TH2). Data exchange is performed using the RF protocol of (TP2).

When the predetermined data exchange is performed and the application App (M) is terminated, the DH 21 transmits the deactivation command DEACTIVATE_CMD to the NFCC 22 in step S62. The parameter "Deactivation Type" of the deactivation command DEACTIVATE_CMD includes "DESELECT" which is a command to be sent to the remote target 11-2.

In step S63, the NFCC 22 transmits a deactivation response DEACTIVATE_RSP to the effect that the deactivation command DEACTIVATE_CMD is accepted to the DH21.

Then, in step S64, the NFCC 22 transmits a DESELECT command to the remote target 11-2 based on the parameter “Deactivation Type” included in the deactivation command DEACTIVATE_CMD. In step S65, the NFCC 22 receives the DESELECT response from the remote target 11-2 and deactivates the interface. Deactivation of the interface releases the parameters associated with remote target 11-2 (TH2) and ISO-DEP (TP2).

In step S66 and subsequent steps of FIG. 13, the remote target 11-1 (TH1) is selected as the communication partner, and communication is performed between the DH 21 and the remote target 11-1 (TH1).

That is, in step S66, the DH 21 transmits the discovery selection command DISCOVER_SELECT_CMD with "Target Handle" = TH1 and "Target Port" = TP1 as parameters to the NFCC 22.

In step S67, the NFCC 22 receives the discovery selection command DISCOVER_SELECT_CMD and transmits the discovery selection response DHISCOVER_SELECT_RSP to the effect that the command is accepted to the DH21.

Then, in step S68, the NFCC 22 recognizes a predetermined PICC and communicates with the remote target 11-1 corresponding to the parameters TH1 and TP1 even when a plurality of PICCs (IC cards) exist. Collision (Anticollision) processing is performed.

In step S69, the NFCC 22 receives a SEL_RES (ISO-DEP | ISO-DEP) response from the remote target 11-1 indicating that it supports ISO-DEP and ISO-DEP as RF protocols.

The NFCC22 assigns "TP4" as the Target Port to the ISO-DEP RF protocol, assigns "TP5" as the Target Port to the NFC-DEP RF protocol, and sets the discovery notification DISCOVER_NTF to DH21 as steps S70 and S71. Send to. That is, in step S70, NFCC22 transmits the discovery notification DISCOVER_NTF (TH1, TP4, NFC-A, PROTOCOL_ISO_DEP, SEL_RES, More = 1) to DH21, and in step S71, the discovery notification DISCOVER_NTF (TH1, TP5, NFC-A). , PROTOCOL_NFC_DEP, SEL_RES, More = 0) is transmitted to DH21.

In step S72, the DH 21 selects NFC-DEP from the two RF protocols and transmits a discovery selection command DISCOVER_SELECT_CMD with "Target Handle" = TH1 and "Target Port" = TP5 as parameters.

In step S73, the NFCC 22 receives the discovery selection command DISCOVER_SELECT_CMD and transmits the discovery selection response DHISCOVER_SELECT_RSP to the effect that the command is accepted to the DH21.

For the NFC-DEP RF protocol, a high level interface level is specified in the interface level setting in step S43 described above. Therefore, in step S74, the NFCC 22 activates the protocol activation (ATR_REQ command requesting the attribute) and the LLCP.

In step S75, the NFCC 22 receives the ATR_RES response and the LLCP activation result from the remote target 11-1 as a response to the ATR_REQ command. Then, in step S76, the NFCC 22 sends an activation notification ACTIVATE_NTF to the DH21 to the effect that the activation of the interface at the high level is completed. The parameters of the activation notification ACTIVATE_NTF include the received response "ATR_RES" as "Activation Parameters" and "High I / F Level activated" indicating the activated interface level as "Interface Type".

After the interface activation is completed, in step S77, the application App (H) corresponding to the high level interface level in DH21 is started, and NFC-DEP is started between DH21 and the remote target 11-1 (TH1). Data exchange is performed using the RF protocol of (TP5).

When the predetermined data exchange is performed and the application App (H) is terminated, the DH 21 transmits the deactivation command DEACTIVATE_CMD to the NFCC 22 in step S78. The parameter "Deactivation Type" of the deactivation command DEACTIVATE_CMD includes "DSL_REQ" which is a command to be sent to the remote target 11-1.

In step S79, the NFCC 22 sends a deactivation response DEACTIVATE_RSP to the effect that the deactivation command DEACTIVATE_CMD is accepted to the DH21.

Then, in step S80, the NFCC 22 transmits a DSL_REQ command to the remote target 11-1 based on the parameter "Deactivation Type" included in the deactivation command DEACTIVATE_CMD. In step S81, the NFCC 22 receives the DSL_RES response from the remote target 11-1 and deactivates the interface. Deactivation of the interface releases the parameters associated with remote target 11-1 (TH2) and NFC-DEP (TP5).

In step S82 and subsequent steps, the remote target 11-3 (TH3) is selected as the communication partner, and communication is performed between the DH 21 and the remote target 11-3 (TH3).

Specifically, in step S82, the DH 21 transmits a discovery selection command DISCOVER_SELECT_CMD having "Target Handle" = TH3 (NFC-F) and "Target Port" = TP3 (T3T) as parameters to the NFCC 22.

In step S83, the NFCC 22 receives the discovery selection command DISCOVER_SELECT_CMD and transmits the discovery selection response DHISCOVER_SELECT_RSP to the effect that the command is accepted to the DH21.

For the T3T RF protocol, a low level interface level is specified in the interface level setting in step S43 described above. There is no protocol activation at the lower interface level. Therefore, in step S84, the NFCC 22 immediately sets the parameter of "Activation Parameters" to "NULL" and sends an activation notification ACTIVATE_NTF to the DH21 to the effect that the activation of the interface at the low level is completed.

After the interface activation is completed, in step S85, the application App (L) corresponding to the low level interface level in DH21 is started, and T3T (TP3) is started between DH21 and the remote target 11-3 (TH3). ) RF protocol is used for data exchange.

When the predetermined data exchange is performed and the application App (L) is terminated, the DH 21 transmits a deactivation command DEACTIVATE_CMD to the NFCC 22 in step S86. At the low level interface level, protocol deactivation is not performed as with protocol activation, so the parameter "Deactivation Type" of the deactivation command DEACTIVATE_CMD is "NULL".

In step S87, the NFCC 22 transmits a deactivation response DEACTIVATE_RSP to the effect that the deactivation command DEACTIVATE_CMD is accepted to the DH21. The NFCC 22 then deactivates the interface and releases the parameters associated with the remote targets 11-3 (TH3) and T3T (TP3).

As described above, the NFC device 1 (DH21 and NFCC22) operates as a polling device and can detect a plurality of remote targets 11 having different RF protocols. Then, the NFC device 1 can sequentially exchange data with the plurality of detected remote targets 11.

[Detailed example of sequence (for Listen Mode)]
Next, with reference to FIGS. 14 and 15, a sequence when the NFC device 1 operates in Listen Mode will be described.

In the examples of FIGS. 14 and 15, the RF protocol supported by the remote target 11-3 is NFC-DEP, unlike FIG. 11.

First, in step S101, the DH 21 transmits an initialization command INIT_CMD, and in response, the NFCC 22 transmits an initialization response INIT_RSP to the DH 21 in step S102. The initialization response INIT_RSP contains the interface level for each RF protocol supported by NFCC22, as described above.

In step S103, the DH 21 transmits to the NFCC 22 an interface level setting command DISCOVER_MAP_CMD that associates the RF protocol with the interface level based on the interface level for each RF protocol supported by the NFCC 22. In the example of FIG. 12, DISCOVER_MAP_CMD (2, Listen, ISO-DEP Protocol, Mid I / F Level, Listen, NFC-DEP Protocol, High I / F Level) is transmitted, in Listen Mode, the RF protocol is ISO-DEP. Is specified as medium level, and NFC-DEP is specified as high level. The RF protocols for T1T, T2T, and T3T are omitted because they are low-level fixed. Also, each interface level in Poll Mode is omitted.

In step S104, the NFCC 22 transmits an interface level setting response DISCOVER_MAP_RSP to the effect that the interface level setting command DISCOVER_MAP_CMD from the DH 21 is accepted.

In step S105, DH21 specifies NFC-A, NFC-B, and NFC-F as RF technologies to be detected, and transmits the discovery start command DISCOVER_START_CMD to NFCC22. In step S106, the NFCC 22 transmits a discovery start response DISCOVER_START_RSP to the effect that the discovery start command DISCOVER_START_CMD is accepted to the DH 21.

Then, the NFCC 22 first transmits a polling command for the NFC device 1 to operate as the Poll Mode for the NFC-A, NFC-B, and NFC-F designated as the RF technologies to be detected. Specifically, in steps S107 to S109, the NFCC 22 sequentially transmits commands SENS_REQ, SENSB_REQ, and SENSF_REQ for the NFC device 1 to operate as the Poll Mode.

Since the response to the commands SENS_REQ, SENSB_REQ, and SENSF_REQ could not be received, the NFC C22 next detects and responds to the polling command for the NFC device 1 to operate as Listen Mode.

Specifically, the NFCC 22 receives the SENS_REQ command transmitted from the remote target 11-1 in step S110, and transmits the SENS_RES response to the remote target 11-1 in step S111.

Further, the NFCC 22 receives the SENSB_REQ command transmitted from the remote target 11-2 in step S112, and transmits the SENSB_RES response to the remote target 11-2 in step S113.

Further, the NFCC 22 receives the SENSF_REQ command transmitted from the remote target 11-3 in step S114, and transmits the SENSF_RES response to the remote target 11-3 in step S115.

In step S116, the NFCC 22 transmits a response SRL_RES (ISO-DEP & NFC-DEP) indicating that ISO-DEP and NFC-DEP are supported as RF protocols to the first detected remote target 11-1.

For ISO-DEP and NFC-DEP, which are the RF protocols of remote target 11-1, the interface level of medium level or higher is specified, so NFCC22 waits for protocol activation from remote target 11-1. .. Then, in step S117, the NFCC 22 receives a RATS (Request for Answer To Select) command requesting ATS from the remote target 11-1, and in response to this, sends an ATS response to the remote target 11-1 in step S118. To do. This completes protocol activation using the ISO-DEP RF protocol.

After receiving the RATS command, the NFCC 22 sends an activation notification ACTIVATE_NTF (TH1, TP1, NFC-A, PROTOCOL_ISO_DEP, ATS, Mid I / F Level activated) to the DH21 in step S119 to the effect that the interface activation is completed. ..

In step S120, the application App (M) corresponding to the medium level interface level in DH21 is launched and uses the ISO-DEP (TP1) RF protocol between DH21 and the remote target 11-1 (TH1). The data exchange that was in place takes place.

After the predetermined data exchange is performed, in step S121, the NFCC 22 receives the DESELECT command from the remote target 11-1 as the PCD (reader / writer), and in step S122, sends the DESELECT response to the remote target 11-1. To do. This deactivates the interface using the ISO-DEP RF protocol in NFCC22.

Then, in step S123, the NFCC 22 transmits a deactivation notification DEACTIVATE_NTF to the DH21 with "Target Handle" = TH1, "Target Port" = TP1, and "Deactivation Parameters" = DESELECT as parameters. DH21 that received the deactivation notification DEACTIVATE_NTF terminates the application App (M).

Next, data is exchanged between the second detected and NFCC22 "Target Handle" = TH2, "Target Port" = TP2 and the assigned remote target 11-2, but the processing is omitted. To do.

Next, data is exchanged between "Target Handle" = TH3, "Target Port" = TP3 and the assigned remote target 11-3 in the NFCC 22 detected third.

In step S124 of FIG. 15, the NFCC 22 receives an ATR_REQ command requesting an attribute from the remote target 11-3. For the NFC-DEP RF protocol, a high level interface level is specified in step S103 described above. Therefore, in step S125, the NFCC 22 transmits an ATR_RES response as a response to the ATR_REQ command and also activates the LLCP.

After completing the protocol activation and LLCP activation, in step S126, the NFCC 22 sends an activation notification ACTIVATE_NTF to the DH21. The parameters of the activation notification ACTIVATE_NTF include the received response "ATR_RES" as "Activation Parameters" and "High I / F Level activated" indicating the activated interface level as "Interface Type".

In step S127, the application App (H) corresponding to the high level interface level in DH21 is launched and uses the NFC-DEP (TP3) RF protocol between DH21 and remote target 11-3 (TH3). The data exchange that was in place takes place.

After the predetermined data exchange is performed, in step S128, the NFCC 22 receives the DSL_REQ command from the remote target 11-3 as the initiator (reader / writer), and in step S129, sends the DSL_RES response to the remote target 11-3. To do. This deactivates the interface using the NFC-DEP RF protocol in NFCC22.

Then, in step S130, the NFCC 22 transmits a deactivation notification DEACTIVATE_NTF to the DH 21. Specifically, the NFCC 22 sends a deactivation notification DEACTIVATE_NTF with "Target Handle" = TH3, "Target Port" = TP3, and "Deactivation Parameters" = DSL_REQ as parameters. DH21 that received the deactivation notification DEACTIVATE_NTF terminates the application App (H).

As described above, the NFC device 1 (DH21 and NFCC22) operates as a listening device and can detect a plurality of remote targets 11 having different RF protocols. Then, the NFC device 1 can sequentially exchange data with the plurality of detected remote targets 11.

The NFC device 1 that performs short-range wireless communication according to ISO / IEC 18092 or ISO / IEC 14443 operates by being functionally separated into DH21 and NFCC22. The DH21 mainly executes applications and controls the entire NFC device 1. The NFCC 22 is arranged between the DH 21 and the remote target 11, and mainly transmits and receives RF data to and from the remote target 11 (PICC (IC card) of ISO / IEC 14443 and the target of ISO / IEC 18092) via the antenna 24. Do.

For each RF protocol, the DH 21 selects one interface level from the plurality of interface levels supported by the NFCC 22, and notifies (designates) the NFCC 22. The plurality of interface levels are classified according to the level to which the NFCC 22 located in the middle bears the processing when the NFC device 1 exchanges data with the remote target 11. Specifically, when the interface level is classified into three levels of low level, medium level, and high level, the high level has the most processing in charge of NFCC22, and the low level has the least processing in charge of NFCC22. The DH 21 acquires information about the interface levels supported by the NFCC 22, and specifies a predetermined interface level for the NFCC 22 for each RF protocol. Then, the DH 21 launches and executes the application App of the level corresponding to the specified interface level. As a result, the DH 21 can concentrate on the execution of the application processing by sharing the processing that can be executed by the NFCC 22. Also, if the NFCC22 supports a higher interface level, by setting it to the highest possible interface level, the NFCC22 and DH21 can exchange data at the higher interface level (for the DH21 application). Data exchange in easy units) will be possible. As a result, the remote target 11 and the NFC device 1 can efficiently exchange data.

When the NFCC 22 operates as a polling device, when it transmits a polling command to detect (discover) a plurality of remote targets 11, it notifies the DH 21 of all the detected remote targets 11 (discovery notification DISCOVER_NTF). Then, the remote targets 11 to communicate with are selected one by one by the DH 21 from the plurality of detected remote targets 11, and the communication (data exchange by the application) is executed. For each selected remote target 11, the operation of activating the interface, executing the application according to the interface level (including starting and terminating), and deactivating the interface is performed. As a result, data can be efficiently exchanged with a plurality of remote targets 11 having different RF technologies or RF protocols.

On the other hand, when the NFCC 22 operates as a listening device, the NFCC 22 selects the remote target 11 as the communication partner in the order of detection for the plurality of remote targets 11 for which the communication link has been established. The NFCC 22 activates the interface corresponding to the RF protocol of the selected remote target 11 and notifies the DH 21 (activation notification ACTIVATE_NTF). The DH 21 executes an application (including start and stop) according to the interface level of the remote target 11 notified of activation. Therefore, communication (data exchange by the application) is sequentially executed with the plurality of remote targets 11 that have established the communication link. As a result, data can be efficiently exchanged with a plurality of remote targets 11 having different RF technologies or RF protocols.

In the above-mentioned example, an example has been described in which the NFCC 22 substitutes the processing required for the remote target 11 and the DH 21 to exchange data according to the interface level specified for the predetermined RF protocol.

However, even in the data exchange process between the remote target 11 and the DH 21, the NFCC 22 may substitute the process to be performed by the DH 21 according to the interface level specified for the predetermined RF protocol.

For example, when the NFC device 1 is in Reader / Writer mode and the level of the interface activated by the NFCC 22 is high, the NFCC 22 executes a process for accessing the NDEF data on behalf of the DH 21. Here, the NDEF data is NDEF (NFC Data Exchange Format) data, which is a common data format used by applications.

This will be explained in detail with the example of NFC FORUM Type 3 Tag Operation, which is a specification for Type 3 in the Tag Operation that specifies commands for accessing NDEF data. In the NFC FORUM Type 3 Tag Operation, when reading NDEF data, Polling Command / Response and Check Command / Response are exchanged between the remote target 11 and the NFC device 1. This Check Command / Response exchange may occur multiple times depending on the size of the NDEF data. When the Check Command / Response is exchanged multiple times, the data obtained by combining the data acquired by the Check Command / Response multiple times becomes the NDEF data.

When the interface level of the NFCC 22 is high, the NFCC 22 proactively executes the Polling Command / Response and one or more Check Command / Response. Then, when the Check Command / Response is exchanged a plurality of times, the NFCC 22 combines the data acquired by the Check Command / Response a plurality of times to generate NDEF data. On the other hand, when the interface level of the NFCC 22 is medium level or low level, the NFCC 22 only relays the Polling Command / Response supplied from the DH 21 and one or more Check Command / Response. The DH21 also performs a process of generating NDEF data from the data acquired by a plurality of Check Command / Response.

In the present specification, the steps described in the flowchart are performed in chronological order in the order described, and of course, when they are called in parallel or when they are called, even if they are not necessarily processed in chronological order. It may be executed at the required timing such as.

In addition, in this specification, a system represents the whole apparatus composed of a plurality of apparatus.

The embodiment of the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the gist of the present invention.

1 NFC device, 11-1 to 11-3 NFC device (remote target), 21 DH (Device Host), 22 NFCC (NFC Controller), 23 NFCEE (NFC Execution Environment), App (H), App (M), App (L) application

Claims (6)

It has a non-contact communication control unit that supports multiple interface levels and sends and receives data to and from other communication devices by non-contact communication.
The non-contact communication control unit selects a predetermined interface from the plurality of interfaces based on receiving a command transmitted from a processing unit that executes an application for exchanging data with the other communication device. Communication device. The communication device according to claim 1, wherein the non-contact communication control unit activates the selected predetermined interface. The communication device according to claim 2, wherein the non-contact communication control unit deactivates the activated interface after exchanging data with the other communication device by the application. In a communication method of a communication device including a non-contact communication control unit that supports multiple interface levels and transmits / receives data to / from another communication device by non-contact communication.
The non-contact communication control unit selects a predetermined interface from the plurality of interfaces based on receiving a command transmitted from a processing unit that executes an application for exchanging data with the other communication device. Communication methods including that. The communication method according to claim 4, further comprising the non-contact communication control unit activating the selected predetermined interface. The communication method according to claim 5, further comprising deactivating the activated interface after the non-contact communication control unit exchanges data with the other communication device by the application.

Images