RU2574382C2 - Communication device, communication method and programme - Google Patents

Abstract

FIELD: radio engineering, communication.

SUBSTANCE: communication device includes a first processing unit which detects an object and receives a first interface activation command after detecting a target object; a second processing unit which communicates with the target object through the first processing unit; an interface between the first processing unit and the second processing unit; the first processing unit selects a predetermined interface level from a plurality of interface levels based on the first command and communicates with the second processing unit based on the predetermined interface level.

EFFECT: providing an interface which can be compatible with a case where multiple types of target objects and protocols are detected.

20 cl, 15 dwg

Description

FIELD OF THE INVENTION

The present invention relates to a communication device, a communication method and a program, and in particular to a communication device, a communication method and a program, through each of which it is possible to provide an interface that can be used when a plurality of types of targets and protocols are detected.

State of the art

A near-field communication system for wireless close-range communication in a non-contact manner using an IC card (integrated circuit) is widespread. For example, its use as an electronic transport ticket and electronic money is well known. In addition, mobile phones have recently become widespread, functioning as an electronic ticket for transport and electronic money through contactless wireless communications.

The short-range wireless communications system has spread rapidly worldwide and is recognized as an international standard. Examples of an international standard include ISO / IEC 14443 as a non-contact type IC card system standard, ISO / IEC 18092 as NFCIP-1 standard (IPSBD - short-range communication interface and protocol), etc.

For short-range communications based on ISO / IEC 18092, active and passive communication modes are used. An active communication mode is a communication mode in which data is transmitted by outputting electromagnetic waves from each of a plurality of communication devices, exchanging data and modulating the corresponding electromagnetic wave. In passive communication mode, data transmission is carried out by removing an electromagnetic wave from one (master) from a variety of communication devices and modulating this electromagnetic wave. Other communication devices (targets) from a variety of communication devices send data by performing load modulation on an electromagnetic wave output from the master.

In passive communication mode ISO / IEC 18092 (hereinafter type F), data is encoded using the Manchester code to transfer data between the recorder and the IC card. In addition, Type F applies data rates of 212 Kbps and 424 Kbps (kilobits per second). Type F corresponds to the FeliCa (registered trademark) scheme developed by the applicant, Sony Corporation.

In addition, various communication schemes are used in the IP card system based on ISO / IEC 14443, for example, the so-called Type A and Type B.

Type A is used as MIFARE (registered trademark) by Koninklijke Philips Electronics N.V. In type A, the encoding of data for transferring data from the recorder to the IC card is carried out by the Miller code, and the encoding of data for transmitting data from the IC card to the recorder is carried out by the Manchester code. In addition, Type A applies a data rate of 106-847 Kbps (kilobits per second).

In type B, the encoding of data for transferring data from the recorder to the IC card is carried out by a code without returning to zero (NRZ) (NRZ), while the encoding of data for transmitting data from the IC card to the recorder is carried out by a code without returning to zero with invariant (BVNI) (NRZ-I). In addition, Type A applies a data transfer rate of 106 Kbps.

A short-range wireless communications device based on ISO / IEC 18092 or ISO / IEC 14443 is hereinafter referred to as an NFC device. There are protocol definitions and commands exchanged between CLF (BUPOD - non-contact data preprocessing device) and AR (PP - application processor), while the SBR device is functionally divided into BUPOD and PP (see JP-T-2009-515250). BUPOD mainly exchanges (receives and transmits) radio frequency (RF) data with the target object (BISI - proximity IC card, Proximity Integrated Circuit Card) ISO / IEC 14443 or the target ISO / IEC 18092, while the software mainly executes the application and provides overall control of the SBR device.

SUMMARY OF THE INVENTION

However, JP-T-2009-51520 only suggests a case in which one type of target and protocol is recorded from type A and type B of ISO / IEC 14443 and type F of ISO / IEC 18092. In other words, JP-T-2009-51520 discloses an interface including an MUPP and a PP assuming that only one kind of target and protocol is registered. For this reason, the interface is unsuitable for the case in which many types of targets and protocols are registered, and it is desirable to develop an interface including BUPOD and PP, which can be compatible with many types of targets and protocols.

Thus, it is desirable to provide an interface that can be compatible with a case in which many kinds of targets and protocols are logged.

In one example, the communication device includes a first processing unit configured to register a target and receive a first command to activate an interface when a target is detected. The communication device also includes a second processing unit, configured to exchange data with the target via the first processing unit. Further, the communication device includes an interface between the first processing unit and the second processing unit. The first processing unit is further configured to select a predetermined interface level from a plurality of interface levels based on the first command and exchange data with the second processing unit based on a predetermined interface level.

A predetermined interface level can be selected based on the RF protocol used in communication between the target and the first processing unit.

The first processing unit may then be configured to transmit a second command and receive a third command in response to the second command, the third command indicating the RF protocol.

The first processing unit may then be configured to receive a fourth command from the second processing unit, the fourth command associating the RF protocol with a predetermined interface level.

The first processing unit may further be configured to send a fifth command based on the first command, the fifth command indicating a predetermined interface level.

The first processing unit can then be configured to start and execute the application based on a predetermined interface level, the application exchanging data between the second processing unit and the target using the RF protocol.

In another example, the first processing unit may further be configured to receive a second command, send a third command in response to the second command, and receive the first command based on the third command.

In such an example, the first processing unit may then be configured to receive a fourth command from the second processing unit, the fourth command associating the RF protocol with a predetermined interface level.

Further in this example, the first processing unit may further be configured to send a fifth command in response to the first command, the fifth command indicating a predetermined interface level.

In the following example, a predetermined interface layer can be selected based on the RF technology used for communication between the target and the first processing unit.

According to this example, the first processing unit may further be configured to transmit a second command and receive a third command in response to the second command, the third command indicating RF technology.

Additionally, in this example, the first processing unit may further be configured to transmit a fourth command to the second processing unit, the fourth command indicating RF technology.

Further in this example, the first processing unit can be configured to launch and execute the application based on a predetermined interface level, the application exchanging data between the first processing unit and the target using RF technology.

Further in this example, the first processing unit may be configured to receive the second command, send the third command in response to the second command, and receive the first command based on the third command.

Additionally, in such an example, the first processing unit may further be configured to send a fourth command in response to the first command, the fourth command indicating a predetermined interface level.

In another example, the first processing unit may then be configured to receive a second command representing a variant of the second processing unit, and the first processing unit may further be configured to transmit a third command in response to the second command, the second command representing a variant of the first processing unit. When the variant of the second processing unit is equivalent to or higher than the variant of the first processing unit, the interface exchanges messages.

In such an example, the third command also represents a predetermined interface level, and when the second processing unit is equivalent to or higher than the first processing unit, the second processing unit transmits the command, the command indicating at least one of the polling mode and listening mode, the RF protocol and interface level.

In another example, the communication method includes the steps of detecting the target and receiving the first message in the first processing unit to activate the interface after registration. The communication method also includes a step of exchanging data between the second processing unit and the target via the first processing unit. The communication method further includes a step in which a first predetermined interface layer is selected from the plurality of interface layers based on the first message. In addition, the communication method includes the step of exchanging data between the first processing unit and the second processing unit based on a predetermined interface level.

According to another example, a non-volatile computer-readable storage medium is encoded by computer-executable instructions. When these commands are executed by the communication device, they force the communication device to perform a method including the steps of detecting the target and receiving the first message in the first processing unit to activate the interface after registration. The method also includes the step of exchanging data between the second processing unit and the target via the first processing unit. The method further includes the step of selecting a predetermined interface layer from among the plurality of interface layers using the first processing unit based on the first message. In addition, the method includes the step of exchanging data between the first processing unit and the second processing unit based on a predetermined interface level.

Brief Description of the Drawings

1 is a block diagram showing a configuration example of an embodiment of a communication system to which the present invention is applied.

2 is a diagram showing an interface layer set for each RF protocol.

FIG. 3 is a diagram showing a difference in processing in accordance with an interface layer in the case of a communication layer for peer-to-peer communication between SBR devices.

4 is a diagram illustrating a detailed structure of each message.

5 is a diagram illustrating a detailed structure of each message.

6 is a diagram illustrating a detailed structure of each message.

7 is a diagram illustrating a detailed structure of each message.

8 is a diagram illustrating a detailed structure of each message.

9 is a diagram illustrating a detailed structure of each message.

10 is a diagram showing a list of messages. 11 is a flowchart illustrating the contents of a sequence.

12 is a diagram illustrating a detailed example of a sequence in the case of a polling mode.

13 is a block diagram illustrating a detailed example of a sequence in the case of a polling mode.

14 is a block diagram illustrating a detailed example of a sequence in the case of a listening mode.

15 is a block diagram illustrating a detailed example of a sequence in the case of a listening mode.

DETAILED DESCRIPTION OF THE INVENTION

An example configuration of a communication system to which the present disclosure applies

1 shows an example configuration of a communication system according to an embodiment to which the present invention is applied.

The communication system of FIG. 1 includes an RRF device 1 and devices 11-1 to 11-3 of the RRF.

RRF device 1 and RRs 11-1 through 11-3 are communication devices for near field communication based on ISO / IEC 18092 and ISO / IEC 14443. RRB devices 1 and RRs 11-1 through 11-3 can work both as an interrogating device and as a listening device.

The interrogating device generates a so-called RF field (radio frequency field) by generating an electromagnetic wave, sends a polling command to register the listening device as an object, and waits for a response from the listening device. In other words, the interrogating device carries out the operation of the BSU (contactless connecting device) ISO / IEC 14443 or the operation of the master in passive mode ISO / IEC 18092.

The listening device receives a polling command sent from the polling device by generating an RF field, and then responds with a polling response. In other words, the listening device performs BISIS ISO / IEC 14443 or the target of ISO / IEC 18092.

Accordingly, the RBU device 1 and the SBR devices 11-1 to 11-3 may have the same hardware configurations, respectively.

Devices 11-1 to 11-3 of the RBU are hereinafter referred to as targets 11-1 to 11-3, respectively, to simplify the distinction between the device 1 of the RBU and devices 11-1 to 11-3 of the RBU. In addition, when there is no particular need to distinguish between targets 11-1 through 11-3, targets 11-1 through 11-3 are simply called target 11 (or RRF device 11).

The RBU device 1 includes one PP (application processor) 21, one BUPOD (non-contact data preprocessing device) 22 and 0 or more EBs (security elements) 23. Since there are 0 or more EBs 23, their number may be 0 ( EB 23 may be omitted).

PP 21 provides overall control of the device 1 RRF, generates a command (KMD) to control BUPOD 22 and analyzes the result of execution in relation to this command. PP 21 is an example of a processing tool. PP 21 exchanges messages with BUPOD 22 in accordance with the GPC (main controller interface). In addition, the PP 21 runs an application for exchanging data with the target 11. Examples of the application include an application performing a data exchange operation for name cards and a peer-to-peer address book (P2P), an electronic money payment operation, and the like. between the recorder and the IC card. In addition, the PP 21 saves three applications Pril (V), Pril (C) and Pril (N) with different levels as data exchange applications in accordance with the interface level of BUPOD 22 (interface level).

Thus, BUPOD 22 includes a memory. The memory may also be external to BUPOD 22. The memory may be RAM, ROM, magnetic disk, optical disk, or any other storage device.

Further, memory is an example of a preserving means. When the PC executes a program for implementing the method according to some embodiments, the memory is an example of a non-volatile storage medium.

The BUPOD 22 is an interface that is located between the BCP 21 and the target 11 to mediate between them, and controls the path so that the BCP 21 and the EB 23 can communicate with the target 11. The BUPOD is an example of processing means. The BUPOD 22 has a plurality of interface layers as an interface layer for mediating between the BCP 21 and the target 11. In this embodiment, it is assumed that the BUPOD 22 has three interface layers including a lower layer, a middle layer, and a upper layer. BUPOD 22 receives a command from the GCI, exchanges messages with the PP 21 and performs the exchange (reception and transmission) of RF data through the antenna 24 based on the command (CMD) with the PP 21.

IHC is a logical interface between PP 21 and BUPOD 22, and the IHC defines a command (CMD) and notification (ATC) in a predetermined format, which will be described later.

EB 23 processes and stores the protected data from the processing necessary for data exchange between the RBU device 1 and target 11. In the example of FIG. 1, SBR device 1 has three EBs from 23-1 to 23-3. EB 23-1 and 23-2 are connected to BUPOD 22 to store and process the protected data that is processed by BUPOD 22, while EB 23-3 is connected to PP 21 to store and process the protected data that is processed by BP 21. It is possible to provide the required number of EB 23 in the device 1 of the RRF or lower the EB 23 if it is not necessary.

Antenna 24 is a closed coil and outputs an electromagnetic wave (RF data) when the current passing through this coil changes. An antenna is an example of a transmitting means and (or) a receiving means.

The RRF device 1, configured as described above, supports one or more of the three RF technologies below.

1) SBR-A - communication circuit type A ISO / IEC 14443.

2) SBR-B - Type B communication scheme ISO / IEC 14443.

3) SBR-F - communication schemes 212 Kbps and 424 Kbps ISO / IEC 18092.

In this list, SBR-A is an abbreviation for Type A ISO / IEC 14443, SBR-B is an abbreviation for Type B ISO / IEC 14443, and SBR-P is an abbreviation for 212 Kbps and 424 Kbps ISO / IEC 18092.

In addition, the RBU device 1 supports one or more of the six RF protocols below.

1) T1T - protocol of the tag platform of the first type (based on the type of SBR-A).

2) T2T - protocol of the tag platform of the second type (based on the type of SBR-A).

3) T3T - protocol of the tag platform of the third type (based on the type of SBR-F).

4) ISO-DEP - ISO-DEP protocol (ISO / IEC 14443-4 based on the type of SBR-A or SBR-B) / protocol of the tag platform of the fourth type (based on the type of SBR-A).

5) NFC-DEP - NFC-DEP protocol (transport protocol ISO / IEC 18092 based on SBR-A or SBR-R).

6) Usage - user definition protocol (user protocol).

In this list, T1T is an abbreviation for the protocol of the tag platform of the first type (based on SBR-A), and T2T is an abbreviation of the protocol of the tag platform of the second type (based on SBR-A). The same is true for T3T, ISO-DEP, NFC-DEP and Custom.

Regarding interface level

When the SBR device 1 exchanges data with the target 11, the SBR device 1 can distribute the processing between the PP 21 and the BUPOD 22. In other words, the intermediate BUPOD 22 can be forced to perform the processing necessary for exchanging data with the target 11 instead of the PP 21. In this the moment on the basis of the interface level defined (notified by the notification) of the PP 21 in relation to the BUPOD 22, it is determined at what level the BUPOD 22 carries out the processing necessary for data exchange, instead of the BOP 21.

Of the three stages of the interface levels, including the lower, middle, and upper levels of BUPOD 22, the upper level is the level at which the processing volume assigned to BUPOD 22 as the interface is the largest, and the lower level is the level at which the processing volume, assigned to BUPOD 22 as an interface is the smallest. It is necessary to set the interface level for each RF protocol, and the set interface level is set in advance depending on the RF protocol in BUPOD 22.

2 shows an interface layer that can be set for the RF protocol BUPOD 22.

For T1T, T2T, and T3T protocols, only the lower interface layer can be set. In addition, for the T1T and T2T RF protocols, the SBR-A RF technology is installed, and for the T3T RF protocol, the SBR-F RF technology is installed.

You can set any of the three (lower, middle, or upper) interface layers for the ISO-DEP and NFC-DEP RF protocols. For the RF protocol ISO-DEP, the RF technology SBR-A or SBR-B is installed, and for the RF protocol NFC-DEP, the RF technology SBR-A or SBR-F is installed.

For the User protocol, only the lower interface layer can be set.

Figure 3 shows the difference in processing depending on the interface level in the case of the communication level for peer-to-peer communication between SBR devices.

At the lower interface level, BUPOD 22 performs the functions of frame format, collision avoidance, bit coding and modulation / load modulation based on ISO / IEC 18092. At the middle interface level, BUPOD 22 additionally performs functions up to the transport protocol based on ISO / IEC 18092. Namely , BUPOD 22, along with the functions at the lower level, additionally performs the functions of activation-deactivation of the protocol, segmentation and reverse recovery and relay. At the upper interface level, BUPOD 22 performs functions up to the PULS (logical communication protocol of the RRF forum), which is the highest level transport protocol based on ISO / IEC 18092.

It is possible to set and set the interface level of BUPOD 22 for each RF protocol of three stages in accordance with the application conditions, the cost of IC crystals, etc., which are assumed to be BUPOD 22.

During the initial processing, BUPOD 22 notifies the PP 21 of data regarding to which interface level BUPOD 22 itself is supporting. BCP 21 takes an interface layer supported by BUPOD 22, selects an optimal interface layer from interface layers supported by BUPOD 22, in accordance with the application conditions envisioned by BCP 21, and assigns an interface layer to BUPOD 22. If BUPOD 22 supports all interface layers, BCP 21 can choose the optimal interface level according to the processing supported by the application. For example, if it is desired that the SC 21 execute the application with less processing, the SC 21 may select and assign an upper interface layer for the BUPOD 22.

Message format

Next, a detailed description will be given of a message defined as a HCC with reference to FIGS. 4-9.

There are three types of messages, including KMD (command) from PP 21 to BUPOD 22, OTV (response) to a command from BUPOD 22 to PP 21 and ATC (notification) from BUPOD 22 to PP 21.

Figure 4 shows the formats of the INIT_COM initialization command and the INIT_RES initialization response.

The “INIT_COM” initialization command is a message for initializing the IHC and exchanging capabilities between BUPOD 22 and PP 21. The “INIT_COM” initialization command includes, as parameters, the “option” elements indicating the IHC variant (option number) of the PP 21, and “IHC properties ", Indicating the capabilities of PP 21. In the" properties of the GCI "element, data are entered about the communication control functions supported by PP 21, such as data on the availability of the data flow control function, the card emulation function, the function of creating an additional message, etc.

The initialization response “INIT_RES” is a message for responding to the initialization command. The initialization response “INIT_RES” includes the “status” elements, representing the result of the response to the initialization command “INIT_COM”, the “option” representing the BKPOD 22 GCI variant, the GCI property representing the BUPOD 22 means and the GCI interfaces , representing the means of the BUPOD 22 interface. In the “IGC properties” element, data are entered on the communication control functions supported by the BUPOD 22, such as data on the availability of the data flow control function, the functions of the battery shutdown mode, and routing functions using identifying an application identifier for a card emulation application, etc. An interface layer for each RF protocol supported by BUPOD 22 is entered in the “IGC interfaces” element.

The PP 21 and the BUPOD 22 mutually check these options by means of the “INIT_COM” initialization command and the initialization response “INIT_RES”, and if the PP 21 option is equal to or higher than the BUPOD 22 option, it is possible to exchange messages while receiving commands from the HMC. On the other hand, if the PP 21 option is lower than the BUPOD 22 option, the PP 21 performs error processing, such as outputting an error message.

Figure 5 shows the formats of the command "SET_INTERFACE_LEVEL_COM" setting the interface level and the response "SET_INTERFACE_LEVEL_RES" setting the interface level.

The command "SET_INTERFACE_LEVEL_COM" setting the interface level is a message connecting the RF protocol and the interface level. The command "SET_INTERFACE_LEVEL_COM" setting the interface level includes the number (n) of data elements of the installation of the interface level and n data elements of the installation of the interface level.

The interface level setting data for one RF protocol includes the “mode” elements representing the mode (polling-listening mode) of the target 11, the “protocol” representing the used RF protocol, and the “interface level” representing the used interface level. Namely, it is possible to set the interface level (“interface level”) for the polling mode and listening mode for one RF protocol (“protocol”). For example, you can perform the installation so that for the case of the polling mode, if the RF protocol is ISO-DEP, the middle interface level is set, and for the case of the listening mode, if the RF protocol is ISO-DEP, the upper interface level is set. Accordingly, the number n of interface-level setup data elements is at most twice the number of RF protocols.

The response “SET_INTERFACE_LEVEL_RES” of the interface level setting is a message for responding to the interface level setting command. The response "SET_INTERFACE_LEVEL_RES" setting the interface level includes as parameter YES = 1 or NO = 0, representing the result of the response.

6 shows the formats of the DISCO VER_START_COM command to start detection, the DISCOVER_START_RES response to start detection, the DISCOVER_STOP_COM command to complete detection, and the DISCO VER_STOP_RES response to complete detection.

The discovery trigger DISCOVER_START_COM command is a discovery target discovery request message 11. The discovery trigger DISCOVER_START_COM command parameter includes a detection types element representing RF technologies as detection targets, the number of which corresponds to the number of RF technologies that desirable to detect.

The response “DISCOVER_START_RES” to start the discovery is a message to respond to the discovery start command. The response "DISCOVER_START_RES" to start the detection includes as a parameter YES = 1 or NO = 0, representing the result of the response.

The DISCOVER_STOP_COM command to complete the detection is a request message to complete the discovery of the target 11. The DISCOVER_STOP_COM discovery completion command does not include any parameters.

The response "DISCOVER_STOP_RES" to complete the discovery is a response message to the discovery completion command. The response “DISCOVER_STOP_RES” of the completion of the detection includes, as a parameter, YES = 1 or NO = 0, representing the result of the response.

7 shows the formats of the DISCOVER_SELECT_COM detection selection command, the DISCOVER_SELECT_RES response to the detection selection, the DEACT_COM deactivation command, and the DEACT_RES response to deactivation.

The “DISCOVER_SELECT_COM” detection selection command is a message for selecting the RF technology (target 11) and the RF protocol. The selected RF technology (target 11) is entered in the parameter “Target ID”, and the selected RF protocol is entered in the parameter “SAP target” (SAP - Service Advertising Protocol, protocol of the offered services) of the DISCOVER_SELECT_COM command of the detection selection.

The response “DISCOVER_SELECT_RES” to the discovery selection is a response message to the discovery selection command. The response "DISCOVER_SELECT_RES" to the selection of detection as a parameter includes YES = 1 or NO = 0, representing the result of the response.

The deactivation DEACT_COM command is a request message to complete the exchange of data with the target 11. The DEACT_COM deactivation command as parameters includes the elements “Target ID” corresponding to RF technology, “SAP target” corresponding to RF protocol, and "deactivation type", which is the command to be sent to the object.

The DEACT_RES deactivation response is a response message to the deactivation DEACT_COM command. The response “DEACTJRES” of deactivation as a parameter includes YES = 1 or NO = 0, representing the result of the response.

Fig. 8 shows the formats of the "DISCOVERJSTTF" notification notification, the "ACTJSTTF" activation notification, and the DEACT_NTF deactivation notification.

The “DISCOVER_NTF” detection notification is a notification message about the target, its RF technology and RF protocol. There are many combinations of target, RF technology, and RF protocol in some cases, in the same way as in the DISCOVER_SELECT COM command mentioned above, detection selection.

The notification “DISCOVER_NTF” of detection as parameters includes the element “Target ID”, which is the number assigned to BUPOD 22 RF technology, “SAP of the target”, which is the number assigned to BUPOD 22 RF protocol, “detection type” representing detected RF technology, an “RF protocol” representing the RF protocol of the target 11, “specific technology parameters” representing a specific RF technology parameter, and “more” representing the presence of the following detection “DISCOVER_NTF” notification.

The ACT_NTP activation notification is a notification message about the activation (activation, start) of a specific level (activation, start) of the interface. The ACT_NTF notification of activation as parameters includes an activation parameters element representing activation parameters and an interface type representing an activated interface level, along with the elements of Target ID, SAP of Target, and type of detection ”and“ RF protocol ”.

The DEACT_NTF deactivation notification is a notification message about the deactivation (deactivation) of a particular interface layer. The “DEACT_NTF” deactivation notification as parameters includes the “deactivation parameters” element representing the deactivation parameters, along with the “Target ID” and “Target SAP object” elements mentioned above.

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

Sequence contents

Next, with reference to FIG. 10, the contents of the sequence of operations performed between the BCP 21 and the BUPOD 22 will be described when the BCP 21 exchanges data with the target 11.

The sequence of operations performed between the PP 21 and BUPOD 22, when the PP 21 communicates with the target 11, includes in general the following five steps.

1) Initialization processing to set the interface level for the RF protocol

2) Discovery processing for target 11

3) Activation processing for the interface

4) Data exchange processing

5) Deactivation processing for the interface

When the PP 21 communicates with a plurality of targets 11, steps 3) -5) are sequentially performed for each of the plurality of targets 11.

1) Initialization processing to set the interface level for the RF protocol

In the initialization processing, the SC 21 assigns an interface to the BUPOD 22 (notifies about it) by sending the “SET_INTERFACE_LEVEL_COM” command to set the interface level after checking the means of the BUPOD 22 interface. The initialization processing corresponds to the processing in step S11 of the BCP 21 and the processing in step S21 of the BUPOD 22 of FIG. 10.

2) Discovery processing for target 11

The detection processing is an operation for detecting the target 11. If the PP 21 sends a discovery trigger command “DISCO VER_START_COM” to request the detection start of the target 11 to the BUPOD 22 in step S12, in step S22, the BUPOD 22 starts the detection processing of the target 11.

Upon detection of the target 11 BUPOD 22 alternately repeats the polling mode and listening mode. Namely, further BUPOD 22 repeats the processing of setting the polling command and waiting for the response of the other side (polling mode) and the processing of waiting for the polling command of the other side (listening mode).

In the polling mode, if the BUPOD 22 receives a response to the sent polling command, the communication line with the target 11 is considered established, and at this moment the mode (polling mode) is supported. In the polling mode, the BUPOD 22 may function as a CID (processing control device) or setter and send a command.

On the other hand, in the listening mode, if the BUPOD 22 sends a response to the polling command of the other side, the communication line with the target 11 is considered established, and at this moment the mode (listening mode) is supported. In listening mode, the BUPOD 22 may function as a BISL or target and respond to a received command (send a response).

The ALMC 22 notifies the PP 21 of the detected target 11 by the notification “DISCOVER_NTF” of the detection in step S23. When a plurality of targets 11 are detected, the LUPOD 22 sends a discovery notification “DISCOVERJNTF” for each of the detected targets 11.

3) Activation processing for the interface

The PP 21 receives the detection notification "DISCOVER_NTF", then selects one predetermined target 11 from the received targets and sends the detection selection command "DISCOVER_SELECT_COM" to the LUPOD 22 in step S13.

BUPOD 22 receives the detection selection command “DISCOVER_SELECT_COM” and activates the interface of one selected target 11 based on the detection selection command “DISCOVER_SELECT_COM” in step S24. Then, the BUPOD 22, by the activation notification “ACT_NTF”, notifies the PP 21 that the interface of the target 11 selected by the discovery selection command “DISCOVER_SELECT_COM” is activated.

In addition, this processing is performed in the Polling mode, and in the listening mode, other processing is performed, since the PP 21 does not select the target 11. Namely, the BUPOD 22 responds with a plurality of RF technologies in the listening mode when the BUPOD 22 stores a state machine for a plurality of RF -technologies. The BUPOD 22 responds with the RF technology detected first when the BUPOD 22 stores the state machine for one RF technology. BUPOD 22 activates the interface of the responding target 11 and notifies the PP 21 of this via an “ACT_NTF” activation notification. Since the target 11 sends a command in listening mode, NUODO 22 performs the operation in accordance with the received command.

4) Data exchange processing

The PP 21 receives the “ACTJNTF” activation notification from the BUPOD 22 and then activates the application in step S14. At this moment, PP 21 selects one of the applications: Pril (V), Pril (C) and Pril (N) in accordance with the interface level BUPOD 22.

The PP 21 communicates with the target 11 through the BUPOD 22 through the activated application in step S15. The NUPP 22 exchanges data between the PP 21 and the target 11 in step S25.

5) Deactivation processing for the interface

In the polling mode, the application activated in the PP 21 sends a deactivation command “DEACT_COM” to the BUPOD 22 at the time the application is completed. BUPOD 22 receives the deactivation DEACT_COM command, deactivates the interface of the communicating target 11 and disconnects the communication with the target 11 in step S26.

On the other hand, BUPOD 22 sends a DEACT_NTF deactivation notification to the PP 21 after disconnecting from the communicating target 11 in the listening mode. The SC 21 terminates the application when the deactivation notification “DEACT_NTF” is received in step S26.

The approximate course of the sequence is described above for an example in which communication is carried out by one target 11.

Detailed sequence example (in case of polling mode)

Next, the sequence performed between the PP 21 and BUPOD 22 when the PP 21 communicates with a plurality of targets 11 will be described in detail with reference to FIGS. 11-13.

11 shows the RF technology and the RF protocol supported by each of the targets 11-1 through 11-3.

Target 11-1 supports SBR-A as RF technology and two RF protocols, including ISO-DEP and NFC-DEP. Target 11-2 supports SBR-B as an RF technology and ISO-DEP as an RF protocol. Target 11-3 supports SBR-F as RF technology and TKT as RF protocol.

11, the “Target ID” and “SAP Target” shown on the right side of the segment for the RF protocol represent the identifiers assigned to the detected target 11 of the BUPOD 22 in the sequence shown in FIGS. 12-13.

Example sequence for polling mode

12-13 are flowcharts showing the sequence in which the RRF device 1 (BUPOD 22) is operated in a polling mode for communicating with three targets 11-1 to 11-3 with various RF technologies.

First, the UI 21 sends the initialization command INIT_COM in step S41, and the NUODC 22 sends an INIT_RES initialization response to the UI 21 in step S42. The INITJRES initialization response includes an interface layer for each RF protocol supported by the BUPOD 22, as described above.

In step S43, the PP 21 sends the interface level setting command SET_INTERFACE_LEVEL_COM for connecting the RF protocol and the interface level to the BUPOD 22 based on the interface level for each RF protocol supported by the BUPOD 22. In step S43, SET_INTERFACE_LEVEL_COM is sent (5, polling, ISO-DEP protocol , middle interface level, polling, NFC-DEP protocol, upper interface level, polling, T1T protocol, lower interface level, polling, T2T protocol, lower interface level, polling, T3T protocol, lower interface level). According to this command, in BUPOD 22 in the interrogation mode with the ISO-DEP RF protocol, the middle interface level is set, for NFC-DEP - the upper interface level, and for T1T, T2T and T3T - the lower interface level.

Although the setup for the T1T, T2T, and T3T RF protocols is done in this example, the levels of the T1T, T2T, and T3T RF protocols can be fixed at the lower level, and command sending and installation can be omitted, since for the T1T, T2T and RF protocols T3T can only be set lower interface level.

Since the sequence of FIG. 12 describes an example in which the RRF device 1 (BUPOD 22) is operated in polling mode, the assignment of each interface level in listening mode in the interface level setting command SETJNTERFACE_LEVEL_COM is omitted in step S43.

BUPOD 22 sends a response SET_INTERFACE_LEVEL_RES to the installation of the interface level, which represents that at step S44 the command SET_INTERFACE_LEVEL_COM of the installation of the interface level from the PP 21 is received.

Then, the PP 21 designates the SBR-A, SBR-B, and SBR-F as the RF technology of the detection targets and sends the discovery trigger command DISCOVER_START_COM to the LUOD 22 in step S45. The BUPOD 22 sends a DISCOVER_START_RES response to the start of detection, representing that the DISCOVER_START_COM detection start command is received at step S46.

Then, BUPOD 22 sends a command to detect targets 11 for SBR-A, SBR-B, and SBR-F, designated as RF technologies for detection targets. In particular, the AU 21 sends the SENS_REQ command to the SBR-A in step S47 and receives the SENSJRES response to the SENS_REQ command, which is sent from the target 11-1 to the RF field in step S48. At the time of receiving the SENS_RES response, the RF protocol of the target 11-1 is not yet known.

In addition, the AU 21 sends the SENSB_REQ command to the RR-B in step S49 and receives the SENSB_RES response to the SENSB_REQ command, which is sent from the target 11-2 to the RF field in step S50. By the time the SENSB_RES response is received, it is already known that the RF protocol of target 11-2 is ISO-DEP.

In addition, the SC 21 sends the SENSF_REQ command for the RRF-R in step S51 and receives the SENSF_RES response to the SENSF_REQ command, which is sent from the target 11-3 to the RF field in step S52. By the time the SENSF_RES response is received, it is already known that the RF protocol of target 11-3 is T3T.

Although BUPOD alternates between polling and listening, if no target 11 is detected, operation in the listening mode is not performed, since targets 11-1 through 11-3 are detected in polling mode.

The BUPOD 22 sends three detection notifications DISCOVER_NTF to notify the PP 21 of the detected objects 11-1 to 11-3 in steps S53-S55. In particular, the BUPOD 22 assigns the detected target RNB-A 11-1 to “TID1” as the target ID and “TSAP1” as the SAP target and sends a DISCO VER_NTF detection notification to the PP 21 at step S53.

The BUPOD 22 assigns the detected RBN-B target 11-2 to “TID2” as the target ID and “TSAP2” as the SAP of the target and sends detection notification DISCOVERJNTF to the PP 21 in step S54. BUPOD 22 assigns the detected target 11-3 of the RBU-F “TID3” as the target ID and “TSAP3” as the SAP of the target and sends detection notification DISCOVER_NTF to the PP 21 in step S55.

Here, the last “greater” parameters in the DISCOVER NTF detection notifications sent in steps S53-S54 are “1” since the DISCOVER_NTF detection notifications will be sent again. On the other hand, the last parameter “greater” than the detection notification DISCOVER_NTF sent in step S55 is “0”, since the detection notification DISCOVER_NTF will no longer be sent.

In the sequence below, the target 11 is determined by the ID of the target and the SAP of the target assigned by BUPOD 22, and a message is exchanged between the BCP 21 and the BUPOD 22.

The PP 21 selects a connection with the target 11-2 from the detected targets 11-1 to 11-3 and sends a discovery selection command DISCO VER_SELECT_COM with parameters TID2 for “target ID” and TSAP2 for “SAP target” in step S56.

The BUPOD 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES representing that the command is received on the PP 21 in step S57.

The middle interface layer is assigned by the aforementioned interface level SET_INTERFACE_LEVEL_COM command for the ISO-DEP RF protocol, represented by “Target SAP” = TSAP2 included in the discovery selection command DISCOVER_SELECT_COM. The protocol activation operation is performed by the BUPOD 22 at the middle interface layer, as described above with reference to FIG. 3.

Thus, the BUPOD 22 activates the protocol in step S58. Namely, BUPOD 22 reports its own characteristics (specifications) and sends an ATTRIB command to request characteristics of the target 11-2 to the target 11-2. The BUPOD 22 receives the ATTA response from the target 11-2 as a response to the ATTRIB command in step S59.

If the ATTA response is received, BUPOD 22 sends an activation notification ACT_NTF, representing that the activation of the interface at the middle interface level is completed, at the PP 21 in step S60. Activation notification parameters ACT_NTF include the received response “ATTA” as the “activation parameter” and the “middle interface level activated” indicating the activated interface level as the “type of interface”.

After the activation of the interface is completed, the APP application (Cp) corresponding to the middle interface level in the PP 21 starts the data exchange between the PP 21 and the target 11-2 (TID2) using the ISO-DEP RF protocol (TSAP2) in step S61.

When the predetermined data exchange has been completed and the adj (CP) application has been completed, the PP 21 sends the deactivation command DEACT_COM to the LUPOD 22 in step S62. The parameter “deactivation type” of the DEACT_COM deactivation command includes the “DESELECT” command to be sent to the target 11-2.

The BUPOD 22 sends a deactivation response DEACTJRES representing that the deactivation command DEACT_COM has been received at the Ack 21 in step S63.

Then, BUPOD 22 sends a DESELECT command to the target 11-2 based on the “deactivation type” parameter included in the deactivation DEACT_COM command in step S64. BUPOD 22 receives a DESELECT response from target 11-2 and deactivates the interface in step S65. Parameters related to target 11-2 (TID2) and ISO-DEP (TSAP2) are revoked by deactivating the interface.

Starting from step S66 of FIG. 13, a target 11-1 (TID1) is selected as the second communication participant, and communication is performed between the PP 21 and the target 11-2 (TID1).

Namely, the PP 21 sends the discovery selection command DISCO VER_SELECT_COM with the parameters TID1 as “Target ID” and TSAP1 as “SAP Target” to BUPOD 22 in step S66.

The BUPOD 22 receives the discovery selection command DISCOVER_SELECT_COM and sends a discovery selection response DISCOVER_SELECT_RES, representing that the command is received, to the PP 21 in step S67.

Then, the BUPOD 22 recognizes the predetermined BFID and performs collision avoidance processing for communication even if there are a plurality of BFID (IP cards) between the BUPOD 22 and the target 11-1 corresponding to the TID1 TSAP1 parameter in step S68.

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

BUPOD 22 assigns “TSAP4” as the SAP Target to the RF Protocol ISO-DEP, and “TSAP5” as the SAP Target to the RF Protocol NFC-DEP, and sends DISCOVERJNTF notification messages to the PP 21 in steps S70 and S71. Namely, BUPOD 22 sends detection notification DISCO VER_NTF (TID1, TSAP4, SBR-A, PROTOCOL_ISO_DEP, SEL_RES, greater than 1) to the PP 21 in step S70, and sends detection DISCOVER_NTF notification (TID1, TSAP5, SBR-A, PROTOCOL_NTRD_ , larger) on the PP 21 in step S71.

The PP 21 selects NFC-DEP from the two RF protocols and sends the discovery selection command DISCOVER_SELECT_COM with parameters TID1 as “Target ID” and TSAP1 as “SAP Target” in step S72.

In step S73, the LUPEL 22 receives the detection selection command DISCOVER_SELECT_COM and sends a detection selection response DISCOVER_SELECT_RES representing that the command is received to the control unit 21.

In the setting of the interface layer described above, in step S43, the upper interface layer is assigned to the NFC-DEP RF protocol. Thus, BUPOD 22 performs protocol activation (ATR_REQ property request command) and PULS activation in step S74.

In step S75, the BUPOD 22 receives the results of the ATR_RES response and the activation of the PULS as a response to the ATR_REQ command from the target 11-1. Then, the BUPOD 22 sends an activation notification ACT_NTF, meaning that the activation of the interface at the upper level is completed, at the PP 21 in step S76. Activation notification parameters ACT_NTF include the received response "ATR_RES" as the "activation parameter" and "activate the upper interface layer" representing the activated interface layer as the "type of interface",

After the activation of the interface is completed, the APP application (B) corresponding to the upper interface level in the PP 21 starts the data exchange between the PP 21 and the target 11-1 (TID1) using the NFC-DEP RF protocol (TSAP5) in step S77.

When the predetermined data exchange is completed and the App (B) application is completed, the PP 21 sends a deactivation command DEACT_COM to the BUPOD 22 in step S78. The “deactivation type” parameter of the deactivation DEACT_COM command includes the “DSL_REQ” command to be sent to the target 11-1.

The BUPOD 22 sends a deactivation response DEACT_RES representing that the deactivation command DEACT_COM has been received at the Ack 21 in step S79.

Then, the BUPOD 22 sends the DSLJREQ command to the target 11-1 based on the “deactivation type” parameter included in the deactivation command DEACT_COM in step S80. The MUPP 22 receives the DSLJRES response from the target 11-1 and deactivates the interface in step S81. Parameters related to target 11-1 (TID1) and NFC_DEP (TSAP5) are revoked by deactivating the interface.

Starting from step S82, target 11-3 (TID3) is selected as the second communication participant, and communication is performed between the PP 21 and target 11-3 (TID3).

Namely, the PP 21 sends the discovery selection command DISCOVER_SELECT_COM with the parameters TID3 (SBR-F) as the “Target ID” and TSAP1 (T3T) as the “SAP Target” on the BUPOD 22 in step S82.

The BUPOD 22 receives the detection selection command DISCOVER_SELECT_COM and sends a detection selection response DISCOVER_SELECT_RES, indicating that the command is received, to the UE 21 at step S83.

In the setting of the interface layer mentioned above, in step S43, the lower interface layer is determined for the T3T RF protocol. At the lower interface level, the protocol is not activated; therefore, BUPOD 22 immediately sets “zero” as the “activation parameter” parameter and sends an activation notification ACT_NTF, representing that the activation of the interface at the lower level is completed, to the PP 21 in step S84.

After the activation of the interface is completed, the App Pri (H) corresponding to the lower interface level in the PP 21 starts the data exchange between the PP 21 and the target 11-3 (TID3) using the T3T RF protocol (TSAP3) in step S85.

When the predetermined data exchange is completed and the App (H) application is completed, the PP 21 sends the deactivation command DEACT_COM to the BUPOD 22 in step S86. Since protocol deactivation is not performed, as well as protocol activation, the parameter “deactivation type” of the deactivation DEACT_COM command is “zero”.

The BUPOD 22 sends a deactivation response DEACT_RES, meaning that the deactivation command DEACT_COM is received, at the Ack 21 in step S87. Next, BUPOD 22 deactivates the interface and recalls parameters related to the target 11-3 (TID3) and T3T (TSAP3).

As described above, the RBU device 1 (PP 21 and BUPOD 22) can be operated as an interrogating device and detect many objects 11 with different RF protocols. In addition, the RBU device 1 can sequentially exchange data with a plurality of detected targets 11.

Detailed sequence example (in case of listening mode)

Next will be described the sequence in which the device 1 RRF is operated in listening mode, with reference to Fig.14-15.

In the examples of FIGS. 14-15, the RF protocol supported by the target 11-3 is NFC-DEP, in contrast to the example of FIG. 11.

Initially, the UI 21 sends an initialization command INIT_COM in step S101, and the NUPP 22 sends an INIT_RES response to initialization in the UI 21 in step S102. The initialization response of INIT_RES includes an interface layer for each RF protocol supported by BUPOD 22, as described above.

The PP 21 sends the interface level setting command SET_INTERFACE_LEVEL_COM for communication between the RF protocol and the interface level on the BUPOD 22 based on the interface level for each RF protocol supported by the BUPOD 22 in step S103. In the example of FIG. 14, SET_INTERFACE_LEVEL_COM is sent (2, listening, ISO-DEP protocol, middle interface level, listening, NFC-DEP protocol, upper interface level), and in listening mode, the average level is determined for the ISO-DEP RF protocol, and the upper level is defined for NFC-DEP. Since the level of the T1T, T2T, and T3T protocols is fixed at the lower level, their definition is omitted. In addition, each interface layer in polling mode is also omitted.

BUPOD 22 sends a response SET_INTERFACE_LEVEL_RES to the installation of the interface level, representing that the command SET_INTERFACE_LEVEL_COM setting the interface level from the PP 21 is received at the PP 21 at step S104.

In step S105, the PP 21 identifies the SBR-A, SBR-B, and SBR-F as the RF technology of the detection targets and sends the DISCO VER_START_COM command to start the detection on the LUOD 22. the start of the detection is sensed at the PP 21 in step S106.

Then, the BUPOD 22 first sends a polling command for operating the RBU device 1 in polling mode for the RBU-A, RBU-B, and SBR-F designated as RF technologies for the detection targets. In particular, the NUODE 22 sequentially sends the SENS_REQ, SENSB_REQ, and SENSF_REQ commands for operating the SBR device 1 in a polling mode in steps S107-S109.

Since responses to the SENS_REQ, SENSB_REQ, and SENSF_REQ commands have not been received, the BUPOD 22 then detects a polling command for operating the RRB device 1 in listening mode and responds.

In particular, the NUODC 22 receives the SENS_REQ command sent from the target 11-2 in step S110 and sends a SENS_RES response to the target 11-1 in step S111.

In addition, the BUPOD 22 receives the SENSB_REQ command sent from the target 11-2 in step S112 and sends a SENSB_RES response to the target 11-2 in step S113.

Next, the BUPOD 22 receives the SENSFJREQ command sent from the target 11-3 in step S114 and sends a SENSF_RES response to the target 11-3 in step S115.

In step S116, the MUCH 22 sends an SRL-RES (ISO-DEP and NFC-DEP) response representing that ISO-DEP and NFC-DEP are supported as RF protocols to the target 11-1 detected first.

Since the middle or upper interface layer is defined for the RF protocols ISO-DEP and NFC-DEP of the target 11-1, the BUPOD 22 waits for the protocol to be activated by the target 11-1. Then, the BUPOD 22 receives the RCDE (request for response to select) for the EFA request from the target 11-1 in step S117 and sends the EFA response to the command to the target 11-1 in step S118. These steps complete the activation of the protocol by the RF protocol ISO-DEP.

Upon receipt of the command, the GCAP BUPPOD 22 sends an activation notification ACT_NTF (TID1, TSAP1, SBR-A, PROTOCOL_ISO_DEP, EFA, the middle interface level is activated), meaning that the activation of the interface is completed, to the PP 21 in step S119.

In step S120, the APP application (Cp) corresponding to the middle interface level in the PP 21 starts the data exchange between the PP 21 and the target 11-1 (TID1) using the ISO-DEP RF protocol (TSAP1).

After the predetermined data exchange has been performed, the BUPOD 22 receives the DESELECT command from the target 11-1 as the STM (personal communication device. Personal Communication Device) (recording-reproducing device) in step S121 and sends a DESELECT response to the target 11 -1 in step S122. With these actions, the interface using the RF protocol ISO-DEP is deactivated in BUPOD 22.

Then, BUPOD 22 sends a deactivation notification DEACT_NTF to the PP 21 with parameters TID1 as “target ID”, TSAP1 as “SAP target” and DESELECT as “deactivation parameter” in step S123. The PP 21 receives the DEACT_NTF deactivation notification and then terminates the adj (Wed) application.

Although then data is exchanged with the target 11-2, which was detected second and for which "Target ID" = TID2 and "Target SAP" = TSAP2 are assigned, the processing description will be omitted.

Then an exchange is made with the targets 11-3, which was detected second and for which “Target ID” = TSHZ and “Target SAP” = TSAP3 are assigned.

In step S124 of FIG. 15, the BUPOD 22 receives the ATR_REQ property request command from the target 11-3. In the above step S103, an upper interface layer was determined for the NFC-DEP protocol. Therefore, the NUPP 22 sends the ATR_RES response as a response to the ATR_REQ command and performs the activation of the PULS in step S 125.

After activating the protocol and activating the PULS, the BUPOD 22 sends an activation notification ACT_NTF to the PP 21 in step S126. Activation notification parameters ACT_NTF include the received response "ATR_RES" as the "activation parameter" and "upper interface layer activated" representing the activated interface layer as the "type of interface".

In step S127, the App Attachment (B) corresponding to the upper interface layer in the PP 21 starts the data exchange between the PP 21 and the objects 11-3 (TID3) using the NFC-DEP RF protocol (TSAP3).

After a predetermined data exchange, BUPOD 22 receives the DSL_REQ command from target 11-3 as a master (recorder / player) in step S128 and sends a DSL_RES response to target 11-3 in step S129. By such actions, the interface using the RF protocol NFC-DEP is deactivated in BUPOD 22.

Then, the NUPP 22 sends a deactivation notification DEACT_NTF to the UE 21 in step S130. In particular, BUPOD 22 sends a deactivation notification DEACT_NTF with parameters TID3 as “target ID”, TSAP3 as “SAP target” and DSL_REQ as “deactivation parameter”. The PP 21 receives the DEACT_NTF deactivation notification and then terminates the PRI (B) application.

The device 1 RBU (PP 21 and BUPOD 22) can be operated as a listening device and detects many objects 11 with different RF protocols. In addition, the device 1 RBU can sequentially exchange data with the detected many targets 11.

The RRF device 1 for short-range wireless communication based on ISO / IEC 18092 or ISO / IEC 14443 is operated by being functionally divided into BCP 21 and BUPOD 22. The BCP 21 mainly executes the application and carries out general control of the BFR device 1. BUPOD 22 is located between the PP 21 and the target 11 and basically sends and receives RF data to the target 11 and from the target 11 (VLSI (IP card) ISO / IEC 14443 or target ISO / IEC 18092) through the antenna 24.

The PP 21 selects (assigns) one interface layer from a plurality of interface layers supported by the BUPOD 22 for each RF protocol and notifies the BUPOD 22. The plurality of interface layers are classified depending on the processing level at which the BUPOD 22 is loaded in the middle when the device 1 The SBR communicates with target 11. In particular, when the interface layer is classified into three stages, including the lower, middle, and upper levels, the amount of processing assigned to BUPOD 22 at the upper level is It is Busy greatest, and at the bottom - the lowest. The BCP 21 receives data related to the interface layer supported by the BUPOD 22 and determines a predetermined interface layer for each RF protocol with respect to the BUPOD 22. Then, the BCP 21 activates and runs the App at a level corresponding to the determined interface layer. With this configuration, the BCP 21 can focus on the execution of the application processing by assigning the BUPOD 22 processing that can be performed BUPOD 22. In addition, when the BUPOD 22 supports the upper interface layer, the BUPOD 22 and the PP 21 can exchange data at the upper interface level (data exchange in blocks with which PP 21 application can process more easily) by setting the interface level as high as possible. With this configuration, the target 11 and the RBU device 1 can efficiently exchange data.

When the BUPOD 22 is operated as a polling device, the BUPOD 22 sends a polling command, detects (recognizes) a plurality of targets 11, and then notifies the PP 21 of all detected targets 11 (detection notification DISCOVER_NTF). Then, the PP 21 sequentially selects the target 11 one after another from the set of detected target 11, and the communication (data execution by the application) is executed. In relation to each of the selected targets 11, actions are taken that include activating the interface, executing the application in accordance with the interface level (including starting and ending), and deactivating the interface. With such actions, efficient data exchange with a variety of targets 11 with various RF technologies or RF protocols is possible.

On the other hand, when the BUPOD 22 is operated as a listening device, the target 11 is selected as the second communication participant from the plurality of target 11 with which the communication connection has been established in the registration order. BUPOD 22 activates the interface corresponding to the RF protocol of the selected target 11, and notifies the PP 21 (activation notification ACT_NTF). The PP 21 executes (including starting and terminating) the application in accordance with the interface level of the target 11 for which an activation notification has been made. Accordingly, the communication (data exchange by the application) is executed sequentially with a plurality of targets 11 with which the communication connection has been established. With this configuration, efficient data exchange with a variety of targets 11 with different RF technologies or RF protocols is possible.

The above is a description of an example in which the processing necessary to transfer data between the target 11 and the PP 21 is instead performed by the BUPOD 22 in accordance with an interface layer defined for a predetermined RF protocol.

However, BUPOD 22 carries out the processing to be performed by the PP 21, instead of the PP 21 in accordance with the interface level defined for the predetermined RF protocol in the data exchange operation between the target 11 and the PP 21, in some cases.

For example, if the SBR device 1 is in the recording-playback device mode, and the interface level activated by the BUPOD 22 is the upper level, the BUPOD 22 performs processing for accessing the data in the FODS instead of the PP 21. Here, the FODC data refers to the data in the common FODS format (RRF data exchange format) used by applications.

An example of a shortcut operation of a third type of RRF forum will be described in detail, which is a detail of a third type of shortcut operations that define an access command to the FODS data. When the FODS data is read in the shortcut operation of the third type of RRF forum, the target 11 and the RRF device 1 exchange the polling response command and the verification response command. In some cases, the response response command is exchanged many times in accordance with the size of the FODS data. When the exchange of the response response command took place many times, the data obtained by combining into pairs of data obtained as a result of the exchange of the response response command carried out many times becomes FODS data.

When the BUPOD interface layer 22 is upper, the BUPOD 22 arbitrarily executes a polling response command and a verification response command one or more times. When the verification response command exchange has been performed multiple times, the BUPOD 22 pairs data obtained as a result of the verification response response command exchange performed many times to generate FODC data. On the other hand, when the BUPOD 22 interface layer is middle or lower, the BUPOD 22 relies only on the polling response command issued from the PP 21 and the verification response command exchanged one or more times. PP 21 also performs the operation of generating FODS data from the data obtained as a result of exchanging the verification response command multiple times.

The steps described in the flowchart of the algorithm can, of course, be performed in sequential mode in the order described in this description, or without performing steps in sequential mode, the steps can be performed in parallel or at the right time, for example, at the time of the call or the like. P.

In addition, the system in this description is a whole device that includes many devices.

Embodiments of the present invention are not limited to the above embodiments, and various modifications are possible without departing from the scope of the present invention.

For example, a program executed to implement the method according to some of the embodiments does not have to be stored on a non-volatile storage medium. The program may also be stored on a volatile storage medium such as a propagating wave.

Claims (20)

1. A communication device comprising:
a first processing circuit configured to receive a first command upon detection of a target;
a second processing circuit configured to exchange data with the target via the first processing circuit, in which the first processing circuit is further configured to select a predetermined interface level from a plurality of interface layers based on the protocol of the first command used in communication with the target, and data with a second processing circuit based on a predetermined interface level. 2. The communication device according to claim 1, wherein the predetermined interface level is selected based on the RF protocol used in communication between the target and the first processing circuit. 3. The communication device according to claim 1, wherein the first processing circuit is further configured to transmit a second command and receive a third command in response to the second command, wherein the third command indicates an RF protocol. 4. The communication device according to claim 3, wherein the first processing circuit is further configured to receive a fourth command from the second processing circuit, the fourth command associating the RF protocol with a predetermined interface level. 5. The communication device according to claim 3, in which the first processing circuit is further configured to send a fifth command based on the first command, the fifth command indicating a predetermined interface level. 6. The communication device according to claim 5, wherein the first processing circuit is further configured to run and execute the application based on a predetermined interface level, the application exchanging data between the second processing circuit and the target using the RF protocol. 7. The communication device according to claim 2, wherein the first processing circuit is further configured to receive a second command, send a third command in response to the second command, and receive the first command based on the third command. 8. The communication device according to claim 7, in which the first processing circuit is additionally configured to receive a fourth command from the second processing circuit, the fourth command associating the RF protocol with a predetermined interface level. 9. The communication device of claim 8, wherein the first processing circuit is further configured to send a fifth command in response to the first command, the fifth command indicating a predetermined interface level. 10. The communication device according to claim 9, in which the first processing circuit is further configured to run and execute the application based on a predetermined interface level, the application exchanging data between the second processing circuit and the target using RF technology. 11. The communication device according to claim 1, wherein the predetermined interface level is selected based on the RF technology used for communication between the target and the first processing circuit. 12. The communication device according to claim 11, wherein the first processing circuit is further configured to transmit a second command and receive a third command in response to the second command, the third command indicating RF technology. 13. The communication device of claim 12, wherein the first processing circuit is further configured to transmit a fourth command to a second processing circuit, the fourth command indicating RF technology. 14. The communication device according to claim 13, wherein the first processing circuit is further configured to start and execute an application based on a predetermined interface level, the application exchanging data between the first processing circuit and the target using RF technology. 15. The communication device according to claim 11, wherein the first processing circuit is further configured to receive a second command, send a third command in response to the second command, and receive the first command based on the third command. 16. The communications apparatus of claim 15, wherein the first processing circuit is further configured to send a fourth command in response to the first command, the fourth command indicating a predetermined interface level. 17. The communication device according to claim 1, wherein the first processing circuit is further configured to receive a second command representing a variant of the second processing circuit, wherein the first processing circuit is further configured to transmit a third command in response to the second command, wherein the second command represents a variant of the first processing scheme, and when the variant of the second processing scheme is equivalent to or higher than the variant of the first processing scheme, the interface exchanges messages. 18. The communication device according to claim 17, in which the third command also represents a predetermined interface level, and when a variant of the second processing circuit is equivalent to or higher than a variant of the first processing circuit, the second processing circuit transmits a command, the command indicating at least one polling mode and listening mode, RF protocol and interface level. 19. A communication method comprising the steps of: receiving a first message in a first processing scheme;
exchanging data between the second processing scheme and the target by the first processing scheme;
using the first processing scheme, a predetermined interface level is selected from the plurality of interface layers based on the protocol of the first message used in communication with the target; and
exchange data between the first processing circuit and the second processing circuit based on a predetermined interface level. 20. A non-volatile computer-readable storage medium encoded by computer-executable instructions, in which instructions, when executed by a communication device, cause the communication device to implement a method comprising the steps of:
receiving the first message in the first processing scheme;
exchanging data between the second processing scheme and the target by the first processing scheme;
using the first processing scheme, a predetermined interface level is selected from the plurality of interface layers based on the protocol of the first message used in communication with the target; and
exchange data between the first processing circuit and the second processing circuit based on a predetermined interface level.

Images