JP6332356B2 - Information processing apparatus and method, and program - Google Patents

Description

  The present technology relates to an information processing apparatus, method, and program, and more particularly, to an information processing apparatus, method, and program that can more easily establish communication via an interface of a different communication standard.

  As an interface for connecting to CLF (Contactless Front-end) inside an NFC (Near Field Communication) device, HCI (Host Controller Interface) specifications are defined in ETSI (European Telecommunications Standards Institute) SCP (Smart Card Platform).

  The HCI (Host Controller Interface) standard defines a logical interface between a UICC (Universal IC Card) and a CLF (see, for example, Patent Document 1).

JP 2011-130414 A

  However, the logical interface between DH and CLF is not defined. For this reason, it may be implemented with a unique specification different from HCI. In that case, since the information to be managed is different in each of these interfaces, it may be difficult to communicate between the DH and the UICC via the CLF using the two interfaces.

  The present technology has been proposed in view of such a situation, and an object thereof is to more easily establish communication via an interface of a different communication standard.

One aspect of the present technology is to establish a logical channel by connecting a plurality of processing units each mounting an arbitrary application and each of the processing units, and connecting the plurality of processing units via itself A connection control unit configured to control, and the connection control unit is established between different processing units according to a communication protocol used for the arbitrary application implemented by the processing unit. associated logical channels to each other were, a table information for storing information of the logical channel associated, the communication protocol is an information processing apparatus to create a table information associating a common logical channels together.

The connection control unit can establish the logical channel based on a request from the processing unit .

The plurality of processing units may include a control unit that controls each unit of the information processing apparatus and a device that is detachable from the information processing apparatus .

The information processing apparatus may be an NFC device .

The connection control unit can establish the logical channels with different communication standards for each processing unit .

According to one aspect of the present technology, the logical channels established between different processing units are associated with each other according to a communication protocol used for an arbitrary application implemented by each of the plurality of processing units. a table information for storing information of the logical channel, the you to create a table information in which the communication protocol is associated a common logical channel each other and establish a logical channel in connection with each of the plurality of processing units, It is an information processing method for controlling connection between the plurality of processing units via itself.

One aspect of the present technology further includes a computer that is different from each other according to a plurality of processing units each mounting an arbitrary application and a communication protocol used for each arbitrary application mounted by the processing unit. associate logical channels with each other is established between the processing unit, a table information for storing information of the logical channel associated, by you to create a table information in which the communication protocol is associated a common logical channel among A program that functions as a connection control unit configured to connect to each of the processing units to establish a logical channel and to control connection between the plurality of processing units via itself.

In one aspect of the present technology, according to a communication protocol used for an arbitrary application implemented by each of a plurality of processing units, logical channels established between different processing units are associated with each other and the associated logic a table information stored channel information, the the communication protocol you to create a table information associating a common logical channel among logical channels are established in connection with each of the plurality of processing units, the Connections between a plurality of processing units via itself are controlled.

  According to the present technology, information can be processed. In particular, communication via an interface with a different communication standard can be established more easily.

It is a figure which shows the main structural examples of an NFC device. It is a figure which shows the main structural examples of an HCI data packet. It is a figure which shows the main structural examples of an HCI command / response packet. It is a figure which shows the example of an HCI connection creation command. It is a figure which shows the example of an HCI connection creation response. It is a figure which shows the example of an HCI connection end command. It is a figure which shows the example of an HCI connection end response. It is a figure which shows the example of a NFCEE connection normal state notification. It is a block diagram which shows the main structural examples of a HCP packet. It is a figure which shows the example of an E-HCI pipe creation command. It is a figure which shows the example of an E-HCI pipe creation response. It is a figure which shows the example of an E-HCI pipe open command. It is a figure which shows the example of an E-HCI pipe open response. It is a figure which shows the example of the communication channel in an NFC device. It is a figure which shows the example of management information. It is a figure which shows the example of the conversion table of command ID and pipe ID. It is a figure which shows the example of the conversion table of a NFCEE protocol and gate ID. It is a figure which shows the example of a connection in an NFC device. It is a flowchart explaining the example of the flow of a connection process from DH to UICC. It is a figure which shows the example of a connection in an NFC device. It is a flowchart explaining the example of the flow of a connection process from DH to UICC. It is a flowchart explaining the example of the flow of a connection process from UICC to DH. It is a flowchart explaining the example of the flow of UICC extraction processing. It is a flowchart explaining the example of the flow of the connection termination request process by DH. It is a figure which shows the example of mounting of a correspondence table. And FIG. 20 is a block diagram illustrating a main configuration example of a computer.

Hereinafter, modes for carrying out the present disclosure (hereinafter referred to as embodiments) will be described. The description will be given in the following order.
1. First embodiment (NFC device)
2. Second embodiment (computer)

<1. First Embodiment>
[1-1 NFC device internal communication]
Inside an NFC (Near Field Communication) device, a DH (Device Host) and a UICC (Universal IC Card) are connected to a CLF (Contactless Front End). In ETSI (European Telecommunications Standards Institute) SCP (Smart Card Platform), a logical interface (also called a logical interface) between CLF (Contactless Front End) and UICC (Universal Integrated Circuit Card) is defined (HCI ( Host Controller Interface)), but the logical interface between DH and CLF is not defined.

  Therefore, an interface different from the logical interface between UICC and CLF can be applied between DH and CLF. In that case, communication between the DH and UICC is performed via two different logical interfaces.

  In that case, since the information managed by each of these logical interfaces is different, it may be difficult to communicate between the DH and the UICC via the CLF using the two logical interfaces.

  For example, in order to establish a connection between DH and UICC, the CLF needs to appropriately associate a logical interface between DH and CLF and a logical interface between UICC and CLF. That is, the CLF needs to establish a logical interface with one side, receive a connection request from one side, establish a logical interface with the other side, and associate the two logical interfaces.

  In order to establish a logical interface, it is necessary to make a connection request / inquiry to the other party or wait until a response is obtained. Such a procedure increases the processing time for connection. There was a fear.

  Also, for example, if the UICC is detachable from the NFC device, the CLF must make an inquiry and wait for a response that should not be obtained, even if the UICC does not exist when a connection is requested from the DH I had to. Such unnecessary processing may unnecessarily increase connection processing time.

[1-2 Control processing by CLF]
Therefore, in an information processing apparatus including a plurality of processing units and a connection control unit that controls connection between the plurality of processing units, the connection control unit is a first established between the one processing unit. When there is no second logical channel established with another processing unit corresponding to the logical channel, the table information indicating the correspondence relationship between the logical channels for the first logical channel is stored in the first logical channel. When there is a table creation unit that creates without specifying a logical channel corresponding to a logical channel, a table storage unit that stores the table information created by the table creation unit, and the second logical channel, The table information for the second logical channel stored in the table storage unit is stored in the logical channel corresponding to the second logical channel in the first logical channel. So that and a table updating unit for updating to the Le.

  The information processing apparatus may be an apparatus that performs any processing as long as it has the above-described configuration and performs communication between the processing units. Each processing unit may perform any processing. The logical channel may be of any communication standard.

  The connection control unit appropriately associates the logical channel established with each processing unit using the table information. This enables communication between the processing units. However, if such processing is performed at the start of communication between the processing units, the processing time may increase as described above. Therefore, the connection control unit creates table information for a logical channel established with one processing unit before receiving a communication request between the processing units. At that time, even if there is no partner to which the correspondence relationship is established, the table information is created without specifying the partner (remaining “empty”). If a corresponding partner exists, the table information of the partner is updated.

  By doing in this way, the connection control part can abbreviate | omit processing, such as an unnecessary inquiry, and can suppress the increase in the processing time of a connection process. Therefore, the information processing apparatus can more easily establish communication via an interface with a different communication standard.

  For example, DH and UICC can communicate via CLF using two interfaces (HCI and E-HCI) for connecting to CLF. Specifically, an application in the terminal host (DH) in the mobile phone can access the application data in the UICC. For example, an electronic money application can view the balance of electronic money in the UICC and make a payment.

  The connection control unit further includes a logical channel establishment unit that establishes the logical channel with the processing unit, and the table creation unit establishes the first logical channel by the logical channel establishment unit. In this case, when the second logical channel does not exist, the table information about the first logical channel is created without designating a logical channel corresponding to the first logical channel, and the table updating unit However, when the first logical channel is established by the logical channel establishment unit, and the second logical channel exists, the table for the second logical channel stored in the table storage unit. The information may be updated so that the first logical channel is a logical channel corresponding to the second logical channel.

  By doing so, the connection control unit establishes a logical channel, creates table information about the logical channel, and reflects information on the logical channel in table information on other logical channels. Can do. As a result, communication between the processing unit and another processing unit can be more easily established immediately after the logical channel is established.

  Each of the table creation unit and the table update unit determines whether or not the second logical channel corresponding to the first logical channel exists based on a correspondence table of characteristics of each logical channel. It may be.

  How the logical channel is formed is determined by the standard. Therefore, in order to establish communication between the processing units, it is necessary to select and associate an appropriate logical channel according to the purpose and specification of the communication. Thus, by using such a correspondence table between logical channels and their characteristics, association between logical channels can be performed more easily.

  The plurality of processing units include a first processing unit in which the logical channel establishment unit establishes the logical channel for each function, and a second processing unit in which the logical channel establishment unit establishes the logical channel for each protocol; May be included. Further, the correspondence table may include information indicating the correspondence relationship between the function and the protocol as the feature. Further, when the first logical channel is established between the table creation unit and the first processing unit by the logical channel establishment unit, the table creation unit is connected to the second processing unit based on the correspondence table. When there is no second logical channel of the protocol corresponding to the function of the first logical channel established in step 1, the table information for the first logical channel is associated with the first logical channel. You may make it create without designating a logical channel. In addition, when the first logical channel is established between the table updating unit and the first processing unit by the logical channel establishment unit, the table updating unit is connected to the second processing unit based on the correspondence table. When there is a second logical channel of the protocol corresponding to the function of the first logical channel established in the table information about the second logical channel stored in the table storage unit, The first logical channel may be updated to be a logical channel corresponding to the second logical channel.

  In this way, the connection control unit can associate logical channels according to functions such as protocols and applications used for communication. Even in that case, the connection control unit can more easily establish communication between the processing units by creating the table information.

  The logical channel establishment unit may establish logical channels of different communication standards with each processing unit.

  As described above, the communication standard of the logical channel is arbitrary, and the logical channel establishment unit can also establish logical channels of different communication standards. Even in that case, the connection control unit can more easily establish communication between the processing units by creating the table information.

  The logical channel establishment unit may establish the logical channel with the requested processing unit based on a request from each processing unit.

  In this way, a logical channel can be established based on a request from the processing unit side. This eliminates the need for the connection control unit to monitor the status of other processing units, and enables flexible responses such as establishing a logical channel only for some functions of the processing unit. Become.

  The logical channel establishment unit may assign identification information to the established logical channel.

  The management of logical channels is facilitated by using predetermined identification information such as identification numbers. However, since the logical channel to be managed may change as appropriate according to the connection status of the processing units, it is desirable to assign the identification information as appropriate. In this way, it is possible to suppress an unnecessary increase in the number of identification information to be handled, and to suppress an increase in the information amount of the identification information.

  The connection control unit may further include a state storage unit that stores information indicating a current state of the logical channel established by the logical channel establishment unit.

  When a logical channel once established is terminated, the table information related to the logical channel is deleted. Therefore, when communication using the logical channel is requested, it is necessary to establish the logical channel again. At that time, if there is no information, the connection control unit must check whether such a logical channel exists (whether it can be established). Therefore, by separately holding information about the logical channel once established, the connection control unit can restore the state of the logical channel using the information when reestablishing the logical channel. . Thereby, the connection control unit can omit processing such as creation and opening of the logical channel, and can easily return the state of the logical channel.

  The table information may be information indicating a correspondence relationship between logical channels by using logical channel identification information.

  By using the identification information, an increase in the information amount of the table information can be suppressed. Thereby, the storage capacity required for storing the table information can be reduced, and the cost and load can be reduced.

  When the logical channel is disconnected, the table update unit may delete the disconnected logical channel information from the table information stored in the table storage unit.

  By reflecting not only the establishment of the logical channel but also the disconnection of the logical channel in the table information, the current establishment state of the logical channel can be grasped from the table information, and communication can be established more easily. That is, processing such as confirmation of the current state of the logical channel associated with the table information becomes unnecessary.

  The table storage unit may reserve a storage area for storing the table information in advance.

  The table information changes in accordance with the establishment status of the logical channel, but by securing the storage area in advance, it is possible to suppress the occurrence of problems such as insufficient capacity.

  The plurality of processing units may include a control unit that controls each unit of the information processing apparatus and a device that is detachable from the information processing apparatus.

  This technology can be applied to CLFs that establish logical channels with DH and UICC in NFC devices.

  The connection control unit may further include a wireless communication unit that performs wireless communication with another device.

  CLF can also communicate with other devices by non-contact communication (short-range wireless communication).

  Note that the present technology may be realized not only as an information processing apparatus but also as an information processing method or program.

[1-3 Overview]
Describes the CLF processing method in the following cases.
1) Correspondence management and correspondence processing between the management information of the original interface HCI and the management information of E-HCI
A) A connection request from both the DH and UICC connected to the CLF establishes a connection between the DH and the UICC via the CLF.
B) By creating an “empty” correspondence table when one of the HCI or E-HCI connections is established, there is no need to make an inquiry from the CLF to the connection destination when the other connection request is accepted. , Processing is speeded up.
C) When a detachable UICC is removed, a notification is sent from the CLF to the DH, and useless processing such as sending data to the unconnected UICC can be prevented.
2) DH to UICC connection processing procedure
A) When communicating with a detachable NFCEE such as UICC via CLF, a communication channel is established depending on whether a pipe is connected to a gate with a function that supports the specified data exchange format (protocol). To do.
3) UICC to DH connection processing procedure
A) When communicating via DH and CLF, a communication channel is established depending on whether a connection having a data exchange format (protocol) corresponding to the specified function (gate) is established.

Differences between connection from DH and connection from UICC
In the case of UICC, a list of gate IDs indicating which functions are obtained is acquired, and a pipe is created and opened for the gates listed in the list, so a communication channel is created for all that is possible. On the other hand, in the case of DH, select one to create a communication channel.

[1-4 NFC device]
FIG. 1 is a diagram illustrating a main configuration example of an NFC device. The NFC (Near Field Communication) device 100 is an arbitrary communication device such as a mobile phone terminal. As illustrated in FIG. 1, the NFC device 100 includes a DH 111, a CLF 112, and a UICC 113.

  A DH (Device Host) 111 is an entity (information processing apparatus) that controls an NFC device. Embedded SE that operates as an information processing apparatus may be used.

  A CLF (Contactless Front-end) 112 is an entity (communication processing device) having a function capable of communicating with an external device via RF (for example, non-contact communication, near field communication, etc.). The CLF 112 has an antenna 131 for the RF communication.

  The UICC (Universal IC Card) 113 is a device that can be attached to and detached from the NFC device 100 (for example, a card-type device that is inserted into a mobile phone).

  The DH 111 and the CLF 112 are connected by an HCI (Host Controller Interface) 121 that is a unique logical interface specification. UICC 113 and CLF 112 are connected by E-HCI 122 defined in ETSI SCP.

[1-5 HCI]
The HCI 121 is a logical interface specification between the CLF 112 and the DH 111. In the HCI 121, the NFC processing entity that can be seen from the DH 111 is referred to as NFCEE (NFC Execution Environment). NFCEE has an entity that can handle multiple protocols. When the DH 111 is connected to the NFCEE connected via the CLF 112, the DH 111 and the NFCEE protocol processing entity are connected using the connection. Each connection is assigned an identifier called Connection ID, and is managed by the CLF 112.

  The DH 111 can acquire an NFCEE identifier (NFCEE ID) managed by the CLF 112 and a protocol (NFCEE Protocol) supported by the NFCEE by transmitting a command for detecting the NFCEE to the CLF 112.

  UICC 113 is one form of NFCEE. When the UICC 113 is connected to the CLF 112, the CLF 112 notifies the DH 111 of the NFCEE ID and the NFCEE Protocol. When the DH 111 connects to the UICC 113, the above NFCEE ID and NFCEE Protocol are specified. NFCEE Protocol includes, for example, APDU (Application Protocol Data Unit) and T3T (Type 3 Tag) Command. APDU is a message structure defined in ISO (International Organization for Standardization) / IEC (International Electrotechnical Commission) 7816-4. Used in NFC Forum Type 4 Tag Operation. T3T is a message structure defined by NFC Forum Type 3 Tag Operation.

[1-6 E-HCI]
E-HCI 122 is a logical interface standard between CLF 112 and UICC 113 defined by ETSI SCP. Here, it is referred to as E-HCI. In the E-HCI 122, an NFC processing entity including the DH 111 and the UICC 113 is referred to as a host. The host has one or more gates representing independent functions and is connected to the gates in the CLF 112 to form a pipe.

  The CLF 112 and the host are required to implement an administration gate that manages the pipe. The host has a unique host ID within the device. Fixed values are assigned to the DH 111 and the UICC 113. Therefore, when the UICC 113 wishes to connect to the DH 111, a host ID (Host ID) is designated.

[1-7 Message configuration]
Next, the specification of the HCI message will be described.

  FIG. 2 is a diagram illustrating a main configuration example of an HCI data packet. This packet is used to transfer messages exchanged on the logical channel specified by the Connection ID.

  In FIG. 2, PBF (Packet Boundary Flag) is information indicating whether or not the next packet is continuous. Connection ID is identification information for identifying a logical channel. RFU (Reserved for future use) is an area for expansion. Payload Length is information indicating the length of Payload. Payload stores higher layer messages. The message format varies depending on the NFCEE Protocol used.

  FIG. 3 is a diagram illustrating a main configuration example of the HCI command / response packet. This packet is used to transfer an HCI command or response.

  In FIG. 3, TYPE is information indicating the contents of the packet. TYPE is set to one of a value “001b” representing “request”, a value “010b” representing “response”, and “011b” representing “notification”. PBF (Packet Boundary Flag) is information indicating whether or not the next packet is continuous. GID (Group ID) is information indicating which functional classification this packet has. OID (Opcode ID) is information indicating the function of this packet. RFU (Reserved for future use) is an area for expansion, and Payload Length indicates the length of Payload. Payload stores command or response parameters.

  The following is an example of information transmitted in this packet.

  FIG. 4 is a diagram illustrating an example of an HCI connection creation command. In FIG. 4, the NFCEE ID is notified from the CLF 112 to the DH 111 in advance. In the NFCEE Protocol, APDU (‘00’) and T3T Command (‘02’) are set according to the message format exchanged by the application.

  FIG. 5 is a diagram illustrating an example of an HCI connection creation response. FIG. 6 is a diagram illustrating an example of an HCI connection end command. FIG. 7 is a diagram illustrating an example of an HCI connection end response. FIG. 8 is a diagram illustrating an example of the NFCEE connection normal state notification.

  Next, the specification of the E-HCI message will be described.

  FIG. 9 is a block diagram illustrating a main configuration example of an E-HCI HCP packet. This packet is used to transfer messages exchanged on the logical channel specified by the pipe ID. The exchanged message includes a command and a response.

  In FIG. 9, CB (Chaining Bit) is information indicating whether or not the next packet is continuous. pID (Pipe ID) is identification information for identifying a pipe to which this packet is transferred. TYPE is information (command, response, or event) indicating the type of this packet. INSTRUCTION is information indicating the function of this packet. Data stores the upper layer message. The message format depends on the CLF gate ID.

  The following is an example of information transmitted in this packet.

  FIG. 10 is a diagram illustrating an example of an E-HCI pipe creation command. In order to specify the gate ID of the connection destination, the UICC 113 acquires a list of gate IDs from the Identity management gate on the CLF 112 in advance. Since the gate ID for connecting to the DH 111 in ETSI is undefined, a unique gate ID definition is required. For example, the definition is as follows.

T4AT wired gate ID = 'F0'
T4BT wired gate ID = 'F1'
T3T wired gate ID = 'F2'

  FIG. 11 is a diagram illustrating an example of an E-HCI pipe creation response. FIG. 12 is a diagram illustrating an example of the E-HCI pipe open command. FIG. 13 is a diagram illustrating an example of an E-HCI pipe open response.

[1-8 Logical channel establishment processing]
A logical communication path for communication between the DH 111 and the UICC 113 is referred to as a logical channel (or logical channel). It is assumed that a unique command is used between the DH 111 and the CLF 112, and a command defined by E-HCI is used between the UICC 113 and the CLF 112.

  FIG. 14 is a diagram illustrating a system configuration example inside the NFC device.

  The DH 111 can implement an arbitrary application. In FIG. 14, for example, a T4T application (T4T application) 211 that is a T4T (APDU) command-based application and a T3T application that is a T3T command-based application are shown as an example. (T3T application) 212 is implemented.

  In addition, an arbitrary connection can be implemented between the DH 111 and the CLF 112, but in FIG. 14, as an example, a T4T connection (T4T conn) 221 and a T3T connection that are connections for communication between the DH and UICC Assume that (T3T conn) 222 and an RF connection (RF conn) 223 that is a connection for RF communication are mounted. The connection ID of this T4T connection (T4T conn) 221 is T4T (Conn ID = T4T). The connection ID of the T3T connection (T3T conn) 222 is T3T (Conn ID = T3T). The connection ID of the RF connection (RF conn) 223 is RF (Conn ID = RF).

  Further, the CLF 112 can be mounted with an arbitrary gate. In FIG. 14, as an example, a Type A RF card gate 241 and a Type B RF card gate are used. 243 is implemented. The CLF 112 is assumed to further mount a type F RF card gate (Type F RF card gate) 245 defined in the E-HCI. The CLF 112 is used for communication between the DH 111 and the UICC 113. The T4T wired gate (Type 4 Tag (T4T) wired gate (original)) 242 and the T3T wired gate (Type 3 Tag (T3T) wired gate (original) 244) is implemented.

  The UICC 113 can be mounted with an arbitrary gate. In FIG. 14, for example, a Type A card application gate (Type A card) that controls a Type A RF card gate 241 is used as an example. application gate) 251 is implemented. In addition, the UICC 113 is mounted with a type B card application gate 252 that controls, for example, a type B RF card gate 243. Furthermore, UICC113 shall mount the Type F card application gate (Type F card application gate) 253 which controls the Type F RF card gate (Type F RF card gate) 245, for example.

  In FIG. 14, between the CLF 112 and the UICC 113, there are a Type A RF pipe, a Type B RF pipe, a Type F RF pipe, and a T4TA. It is assumed that a pipe (T4TA pipe), a T4TB pipe (T4TB pipe), and a T3T pipe (T3T pipe) have been created.

  Type A RF pipe is a pipe between Type A RF card gate 241 and Type A card application gate 251. Type B RF pipe is a pipe between Type B RF card gate 243 and Type B card application gate 252. Type F RF pipe is a pipe between Type F RF card gate 245 and Type F card application gate 253.

  The T4TA pipe is a pipe between the T4T wired gate 242 and the Type A card application gate 251. The T4TB pipe is a pipe between the T4T wired gate 242 and the Type B card application gate 252. The T3T pipe is a pipe between the T3T wired gate 244 and the Type F card application gate 253.

  Although any application can be implemented in the UICC 113, in FIG. 14, as an example, an APDU application (APDU application) 261 that is an APDU command-based application and a type F that is a T3T command-based application Assume that an application (Type F application) 262 is implemented.

  Since the T4T application 211 on the DH 111 and the APDU application 261 on the UICC 113 are both applications that can process APDU, they can be connected by a logical channel.

  Further, since both the T3T application 212 on the DH 111 and the Type F application 262 on the UICC 113 are applications that can process the T3T command, they can be connected by a logical channel.

[1-9 Management of correspondence between HCI management information and E-HCI management information]
In HCI and E-HCI, different information is managed as shown in the table of FIG. The CLF 112 that implements the two interfaces associates these pieces of information as follows. Examples of connection IDs and pipe IDs are shown in FIG. Examples of the NFCEE protocol and gate ID are shown in FIG.

[1-10 Connection process from DH to UICC]
The DH 111 performs connection processing to the UICC 113 when communication with the UICC 113 is necessary. When establishing a logical channel from the DH 111 to the UICC 113, the DH 111 transmits a connection creation command (parameters: NFCEE ID, NFCEE Protocol) to the CLF 112.

  When an E-HCI pipe corresponding to the designated NFCEE Protocol is created, the CLF 112 creates a corresponding connection and responds with a connection creation command response (Status = OK). If there is no pipe, respond with an error. In E-HCI, since there is no function for creating a pipe from the CLF 112 to the UICC 113, the UICC 113 (host) needs to create a pipe in advance during initialization such as when the UICC 113 is inserted.

[1-11 Establishment of logical channel between T4T / APDU applications]
As shown in FIG. 18, when the T4T application 211 on the DH 111 establishes a logical channel with the APDU application 261 on the UICC 113, NFCEE ID = UICC and NFCEE Protocol = T4T are specified in the connection creation command transmitted by the DH 111. .

  In this case, since T4T is specified in the NFCEE Protocol, the CLF 112 creates a T4T connection 221 (Conn ID = T4T) with the DH 111, and there is a pipe connected to the T4T wired gate 242 based on the NFCEE Protocol = T4T. Link with T4TA pipe ID and T4TB pipe ID. When a link is established, a connection creation command response with a normal termination status is transmitted to the DH 111. If there is no pipe and a link cannot be established, a connection creation command response including an error status is transmitted to DH111.

  Note that the protocol / gate ID correspondence table is held in a fixed manner. When a connection creation request is made, a gate ID corresponding to the protocol is searched. Associate the pipe ID and connection ID corresponding to the gate ID. If multiple gate IDs corresponding to the protocol are found, associate them with one connection ID.

  An example of the flow of connection processing from the DH to the UICC will be described with reference to the flowchart of FIG.

  When the UICC 113 is mounted at a predetermined position of the NFC device 100, in step S101, the CLF 112 makes a pipe open request to the Identity gate to the UICC 113. In step S102, the CLF 112 makes a gate ID list acquisition request to the Identity gate to the UICC 113. The CLF 112 acquires and holds the gate ID list supplied from the UICC 113 in response to this request.

  In step S103, the UICC 113 issues a pipe creation request to the DH connection gate to the CLF 112. At that time, the UICC 113 supplies Dest host ID, Dest gate ID, source host ID, and source gate ID.

  In step S104, the CLF 112 creates a pipe to the DH connection gate in response to the request. Also, the CLF 112 assigns the supplied Dest gate ID to the pipe ID corresponding to the gate ID of the DH connection gate, and creates the table 401.

  In step S105, the CLF 112 refers to the protocol / gate ID correspondence table 404 stored in advance, and determines whether or not there is a protocol corresponding to the requested Dest gate ID. If it is determined that a protocol exists, the process proceeds to step S106.

  In step S <b> 106, the CLF 112 updates the connection ID / pipe ID correspondence table (table information) 402 relating to the connection ID of the protocol that has already been created (stored). More specifically, the CLF 112 stores the requested Dest gate ID (the pipe ID set in step S104) in the pipe ID column corresponding to the protocol corresponding to the requested Dest gate ID in the correspondence table 402. to add. When the update of the correspondence table 402 ends, the process proceeds to step S108.

  If it is determined in step S105 that there is no protocol corresponding to the requested Dest gate ID, the process proceeds to step S107.

  In step S107, the CLF 112 creates and stores a connection ID / pipe ID correspondence table (table information) 402 relating to the requested Dest gate ID. At this time, since the connection ID associated with the requested Dest gate ID is undecided, the CLF 112 associates the “empty” connection ID with the pipe ID (Dest gate ID). The value indicating “empty” is arbitrary. When the process of step S107 ends, the process proceeds to step S108.

  As described above, even when the correspondence between the connection ID and the pipe ID is not yet determined, the CLF 112 creates the correspondence table 402 as soon as the pipe is established. As a result, when there is a connection request from the DH 111, the CLF 112 can easily establish communication using the correspondence table 402.

  In step S108, the CLF determines whether to create another pipe. If it is determined to create another pipe, the process returns to step S103. That is, the processes in steps S103 to S108 are repeated for the number of pipes to be created.

  If it is determined in step S108 that another pipe is not to be created, the process proceeds to step S109.

  Upon obtaining a UICC connection creation request from the DH 111 in step S109, the CLF 112 creates a UICC connection connection for the protocol specified in the request in step S110. Also, the CLF 112 assigns a connection ID to the created connection, creates and stores a correspondence table 403 that associates the protocol with the connection ID.

  In step S111, the CLF 112 refers to the protocol / gate ID correspondence table 404 stored in advance, and determines whether there is a gate corresponding to the requested protocol. If it is determined that a gate exists, the process proceeds to step S112.

  In step S112, the CLF 112 updates a connection ID / pipe ID correspondence table (table information) 402 that has already been created (stored) for the gate. More specifically, the CLF 112 adds the connection ID assigned in step S110 to the connection ID column corresponding to the gate corresponding to the requested protocol in the correspondence table 402. In the example of FIG. 19, the correspondence table 402 is updated to become a correspondence table 405. The CLF 112 stores this correspondence table 405. When the update of the correspondence table 402 ends, the connection process ends.

  If it is determined in step S111 that there is no gate corresponding to the requested protocol, the process proceeds to step S113.

  In step S113, the CLF 112 creates and stores a connection ID / pipe ID correspondence table (table information) 402 regarding the requested protocol. At this time, since the pipe ID associated with the requested protocol is not yet determined, the CLF 112 associates an “empty” pipe ID with the connection ID. The value indicating “empty” is arbitrary. When the process of step S113 ends, this connection process ends.

  Thus, even if the correspondence between the connection ID and the pipe ID is not yet determined, the CLF 112 creates the correspondence table 402 as soon as the connection is established. Thereby, when there is a connection request from the UICC 113, the CLF 112 can easily establish communication using the correspondence table 402.

  Note that the storage area for storing information such as the various correspondence tables described above can be provided in any location as long as it is accessible from the CLF 112. For example, the storage area may be provided inside the CLF 112 or may be provided outside the CLF 112.

[1-12 Establishment of logical channel between T3T / Type F applications]
As shown in FIG. 20, when the T3T application 212 on the DH 111 establishes a logical channel with the Type F application 262 on the UICC 113, NFCEE ID = UICC and NFCEE Protocol = T3T are specified in the connection creation command transmitted by the DH 111.

  In this case, since T3T is specified in the NFCEE Protocol, the CLF 112 creates a T3T connection 222 (Conn ID = T3T) with the DH 111, and there is a pipe connected to the T3T wired gate 244 based on the NFCEE Protocol = T3T. Link with T3T pipe ID. When a link is established, a connection creation command response with a normal termination status is transmitted to the DH 111. If there is no pipe and a link cannot be established, the CLF 112 transmits a connection creation command response including an error status to the DH 111.

  The flow of connection processing from the DH to the UICC in this case is the same as that described with reference to FIG. 19 as shown in FIG.

  In step S104, the CLF 112 assigns the pipe ID “12” to the T3T wired gate 244 and creates the table 421.

  In step S105, the CLF 112 refers to the protocol / gate ID correspondence table 424 stored in advance, and determines whether or not a protocol corresponding to the T3T wired gate 244 exists.

  In step S106, the CLF 112 updates the connection ID / pipe ID correspondence table (table information) 422 that has already been created (stored) and is related to the connection ID of the protocol T3T.

  In step S107, the CLF 112 creates and stores a connection ID / pipe ID correspondence table (table information) 422 for the T3T wired gate 244. More specifically, for example, for the pipe ID “12” assigned in the correspondence table 421, the CLF 112 creates a correspondence table 422 that associates an empty connection ID with a pipe ID (Dest gate ID). create.

  As described above, even if the correspondence between the connection ID and the pipe ID is not yet determined, the CLF 112 creates the correspondence table 422 as soon as the pipe is established. Thereby, when there is a connection request from the DH 111, the CLF 112 can easily establish communication using the correspondence table 422.

  In step S110, the CLF 112 creates a T3T UICC connection, assigns a connection ID “05” to the created connection, and creates and stores a correspondence table 423 that associates the T3T with the connection ID.

  In step S111, the CLF 112 refers to the protocol / gate ID correspondence table 424 stored in advance, and determines whether there is a gate corresponding to the protocol T3T.

  In step S112, the CLF 112 is assigned in step S110 to the connection ID column corresponding to the pipe ID “12” corresponding to the requested protocol T3T in the correspondence table 422 already created (stored). A connection ID “05” is added.

  In step S113, the CLF 112 creates and stores a correspondence table (table information) 422 of the connection ID “05” and “empty” (empty) pipe ID regarding the requested protocol T3T.

  As described above, even if the correspondence between the connection ID and the pipe ID is not yet determined, the CLF 112 creates the correspondence table 422 as soon as the connection is established. Thereby, when there is a connection request from the UICC 113, the CLF 112 can easily establish communication using the correspondence table 422.

[1-13 Packet transmission processing from DH to UICC]
The application on the DH 111 transmits a packet to the corresponding application on the UICC 113 using the connection created as described above. When the T4T application 211 transmits a packet to the UICC 113, the T4T Connection ID is specified and the packet is transmitted.

  The CLF 112 transmits the packet received through the connection of T4T Connection ID to the E-HCI pipes (existing pipes) of T4TA pipe ID and T4TB pipe ID, which are the corresponding E-HCI pipes. At this time, the CLF 112 performs processing to replace the HCI header with the E-HCI header.

[1-14 UICC to DH connection processing]
Next, connection processing from the UICC 113 to the DH 111 will be described. This process is performed when the UICC 113 is inserted before the DH 111 creates a connection to the UICC 113.

  When establishing a logical channel from the UICC 113 to the DH 111, the UICC 113 transmits ADM_CREATE_PIPE to the CLF 112. The CLF 112 responds with ANY_OK and the pipe ID of the created pipe when the specified gate is implemented.

  After the pipe is created, the UICC 113 sends ANY_OPEN_PIPE and CLF responds with ANY_OK to open the pipe. It is assumed that a logical channel can be established with the DH 111 by mounting the designated gate. Since Conn ID is limited to 15, it can be used efficiently by creating it dynamically.

  As in E-HCI, HCI does not have a function to create a connection from CLF 112 to DH 111. For example, during initialization at the time of DH 111 activation, DH 111 needs to create a connection in advance. is there.

  When connecting from the UICC 113, the UICC 113 acquires a list of gates in the CLF 112, and therefore, logical channels are established for all the gates in the CLF 112.

[1-15 Establishment of logical channel between APDU / T4T applications]
In FIG. 18, when the APDU application 261 on the UICC 113 establishes a logical channel with the T4T application 211 on the DH 111, the destination HID = DH, destination GID = T4T wired gate, Specify source GID = Type A and / or Type B card application gate. The GID specified here specifies that there is a T4T wired gate 242 virtually on the DH.

  In this case, the CLF 112 creates a connection of T4T Connection ID and links it with a T4T wired pipe ID (T4TA wired pipe or T4TB wired pipe) based on the destination GID.

  An example of the flow of connection processing from the UICC to the DH will be described with reference to the flowchart of FIG.

  In this case, the connection process is performed in the same order as the process of each step of the DH to UICC connection process described with reference to the flowchart of FIG.

  More specifically, in steps S201 to S205, the same processes as those in steps S109 to S113 in FIG. 19 are performed. Thereafter, in steps S206 to S212, the processes in steps S101 to S106 in FIG. The same processing as each processing is performed.

  In the case of the example in FIG. 22, if it is determined in step S210 that there is no protocol corresponding to the requested Dest gate ID, the process proceeds to step S212 without performing the same process as in step S107.

  A more specific example of the above processing flow will be described. Upon obtaining a UICC connection connection creation request from the DH 111 in step S201, the CLF 112 creates a UICC connection connection for the protocol “APDU” specified in the request in step S202. Also, the CLF 112 assigns a connection ID “04” to the created connection, and creates and stores a correspondence table 441 that associates the protocol with the connection ID.

  If there is a gate corresponding to the requested protocol, the CLF 112 obtains the connection ID “04” corresponding to the requested protocol and the pipe ID ID correspondence table (table information) 442 in step S204. Create and remember.

  Further, if there is no gate corresponding to the requested protocol, the CLF 112, in step S205, the correspondence table (table information) of the connection ID “04” and “empty” (empty) pipe ID corresponding to the requested protocol. ) 442 is created and stored.

  As described above, even when the correspondence between the connection ID and the pipe ID is not yet determined, the CLF 112 creates the correspondence table 442 as soon as the connection is established. Thereby, when there is a connection request from the UICC 113, the CLF 112 can easily establish communication using the correspondence table 442.

  In step S207, the CLF 112 makes a gate ID list acquisition request to the Identity gate to the UICC 113. The CLF 112 acquires and holds the gate ID list supplied from the UICC 113 in response to this request.

  In step S209, the CLF 112 creates a pipe to the DH connection gate in response to the request. Also, the CLF 112 associates the supplied Dest gate ID with the pipe ID “10, 11” and creates the table 443.

  In step S210, the CLF 112 refers to the protocol / gate ID correspondence table 444 stored in advance, and determines whether or not there is a protocol corresponding to the requested Dest gate ID. If it is determined that the protocol exists, the process proceeds to step S211.

  In step S211, the CLF 112 updates the connection ID / pipe ID correspondence table (table information) 442 that has already been created (stored) and is related to the connection ID of the protocol. More specifically, the CLF 112 adds the requested Dest gate ID “10, 11” to the pipe ID column corresponding to the connection ID “04” in the correspondence table 442. When the update of the correspondence table 442 ends, the process proceeds to step S212.

[1-16 Establishment of logical channel between Type F / T3T applications]
In FIG. 20, in contrast to the above-described example, when Type F application 262 on UICC 113 establishes a logical channel with T3T application 212 on DH 111, in ADM_CREATE_PIPE transmitted by UICC 113, destination HID = DH, destination GID = T3T wired gate, source GID = Type F card application Specify gate. The GID specified here specifies that there is a T3T wired gate 244 on the DH 111 virtually.

  In this case, the CLF 112 creates a connection with the T3T Connection ID and links it with the T3T wired pipe ID based on the destination GID.

  Since the connection process in this case is performed in the same manner as described with reference to the flowchart of FIG. 22, the description thereof is omitted.

[1-17 Packet transmission processing from UICC to DH]
The application on the UICC 113 transmits a packet to the corresponding application on the DH 111 using the achieved E-HCI pipe. When the APDU application 261 transmits a packet to the DH 111, the created T4TA wired pipe or T4TB wired pipe is specified and the packet is transmitted.

  Either of the two routes may be used. For example, when another application is using a T4TB wired pipe, it can send packets to the DH via the T4TA wired pipe path in parallel. At this time, the CLF 112 performs processing to replace the E-HCI header with the HCI header.

[1-18 UICC removal processing]
When the UICC 113 is removed, the CLF 112 notifies the DH 111. As a result, the correspondence between the connection ID and the pipe ID can be updated in a timely manner, and inconsistent processing such as data transmission to an entity that is not actually connected can be prevented. The UICC 113 extraction notification from the CLF 112 to the DH 111 is notified in the format shown in FIG.

  An example of the flow of UICC extraction processing will be described with reference to the flowchart of FIG. In step S301, the CLF 112 notifies the DH 111 that the UICC 113 has been removed.

  In step S302, the CLF 112 deletes the pipe ID information corresponding to the removed UICC 113 from the connection ID / pipe ID correspondence table (table information). For example, it is assumed that the correspondence table 461 is held. If the pipe IDs “10” and “11” are deleted by removing the UICC 113, the CLF 112 indicates “empty” (Empty) instead of the pipe IDs as shown in the correspondence table 462. Set the value. When the process of step S302 ends, the UICC extraction process ends.

  In this way, a connection ID correspondence table in which the corresponding pipe no longer exists is maintained. Thereby, the CLF 112 can easily establish communication using the correspondence table 462 when the UICC 113 is set again.

[1-19 Connection termination request from DH]
By transmitting a connection end command from the DH 111, the communication channel connected to the UICC 113 can be disconnected. In that case, the CLF 112 updates the correspondence between the connection ID and the pipe ID.

  An example of the flow of connection termination request processing by DH will be described with reference to the flowchart of FIG. In step S321, the CLF 112 acquires a connection end command supplied from the DH 111. In the connection end command, the connection to be ended is specified using the connection ID.

  In step S322, based on the request, the CLF 112 updates the connection ID / pipe ID correspondence table (table information). That is, the information of the designated connection ID is deleted from the correspondence table. For example, assume that a correspondence table 481 is held. When the termination of the connection with the connection ID “04” is requested, the CLF 112 sets a value indicating “empty” (Empty) instead of the connection ID “04” as shown in the correspondence table 482. When the process of step S322 ends, the connection end request process by DH ends.

  In this way, a correspondence table of pipe IDs for which there is no corresponding pipe is maintained. Thereby, when the communication with the UICC 113 is requested again from the DH 111, the CLF 112 can easily establish communication using the correspondence table 482.

[1-20 Pipe status storage]
In accordance with ETSI, the CLF 112 is required to store the pipe state in a nonvolatile manner. When the UICC 113 is inserted, the CLF 112 activates the SWP interface with the UICC 113 and holds the 2-byte SYNC ID transmitted from the UICC 113 during that time. Further, when a pipe is created / opened, the CLF 112 retains the ID and state of the created / opened pipe in association with the SYNC ID.

  If at least one held SYNC ID matches the SYNC ID transmitted from the UICC, the CLF 112 determines that the UICC has been inserted before, and restores the held pipe state. This eliminates the pipe creation / open procedure.

[1-21 Implementation example of correspondence table]
The CLF 112 reserves a fixed memory for the correspondence table between pipe IDs and connection IDs. For example, as shown in FIG. 25, the CLF 112 reserves entries for 16 pipe IDs, and sets all values to “FF”.

  When pipe creation is requested from the UICC 113, when a connection having a protocol corresponding to the designated gate ID is found, the CLF 112 writes the pipe ID and the connection ID associated therewith in the corresponding entry.

  When not found, the CLF 112 writes the pipe ID and the connection ID associated therewith to the entry in which both the pipe ID and the connection ID are “FF”.

  When connection creation is requested from the DH 111, when a pipe having a gate ID corresponding to the designated protocol is found, the CLF 112 writes a connection ID and a pipe ID associated therewith in the corresponding entry.

  When not found, the CLF 112 writes the connection ID and the pipe ID associated therewith to the entry in which both the pipe ID and the connection ID are 'FF'.

  When pipe deletion is requested, the CLF 112 finds the same value as the requested pipe ID, and sets it to 'FF'. If connection deletion is requested, the CLF 112 finds the same value as the requested connection ID, and sets it to 'FF'.

<2. Second Embodiment>
[Computer]
The series of processes described above can be executed by hardware or can be executed by software. When a series of processing is executed by software, a program constituting the software is installed in the computer. Here, the computer includes, for example, a general-purpose personal computer that can execute various functions by installing a computer incorporated in dedicated hardware and various programs.

  FIG. 26 is a block diagram illustrating an example of a hardware configuration of a computer that executes the series of processes described above according to a program.

  In a computer 900 shown in FIG. 26, a CPU (Central Processing Unit) 901, a ROM (Read Only Memory) 902, and a RAM (Random Access Memory) 903 are connected to each other via a bus 904.

  An input / output interface 910 is also connected to the bus 904. An input unit 911, an output unit 912, a storage unit 913, a communication unit 914, and a drive 915 are connected to the input / output interface 910.

  The input unit 911 includes, for example, a keyboard, a mouse, a microphone, a touch panel, an input terminal, and the like. The output unit 912 includes, for example, a display, a speaker, an output terminal, and the like. The storage unit 913 includes, for example, a hard disk, a RAM disk, a nonvolatile memory, and the like. The communication unit 914 includes a network interface, for example. The drive 915 drives a removable medium 921 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

  In the computer configured as described above, the CPU 901 loads the program stored in the storage unit 913 into the RAM 903 via the input / output interface 910 and the bus 904 and executes the program, for example. Is performed. The RAM 903 also appropriately stores data necessary for the CPU 901 to execute various processes.

  The program executed by the computer (CPU 901) can be recorded and applied to, for example, a removable medium 921 as a package medium or the like. The program can be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

  In the computer, the program can be installed in the storage unit 913 via the input / output interface 910 by attaching the removable medium 921 to the drive 915. Further, the program can be received by the communication unit 914 via a wired or wireless transmission medium and installed in the storage unit 913. In addition, the program can be installed in the ROM 902 or the storage unit 913 in advance.

  The program executed by the computer may be a program that is processed in time series in the order described in this specification, or in parallel or at a necessary timing such as when a call is made. It may be a program for processing.

  Further, in the present specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in chronological order according to the described order, but is not necessarily performed in chronological order. It also includes processes that are executed individually.

  In this specification, the system means a set of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Accordingly, a plurality of devices housed in separate housings and connected via a network and a single device housing a plurality of modules in one housing are all systems. .

  In addition, in the above description, the configuration described as one device (or processing unit) may be divided and configured as a plurality of devices (or processing units). Conversely, the configurations described above as a plurality of devices (or processing units) may be combined into a single device (or processing unit). Of course, a configuration other than that described above may be added to the configuration of each device (or each processing unit). Furthermore, if the configuration and operation of the entire system are substantially the same, a part of the configuration of a certain device (or processing unit) may be included in the configuration of another device (or other processing unit). .

  The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, but the technical scope of the present disclosure is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field of the present disclosure can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that it belongs to the technical scope of the present disclosure.

  For example, the present technology can take a configuration of cloud computing in which one function is shared by a plurality of devices via a network and jointly processed.

  In addition, each step described in the above flowchart can be executed by being shared by a plurality of apparatuses in addition to being executed by one apparatus.

  Further, when a plurality of processes are included in one step, the plurality of processes included in the one step can be executed by being shared by a plurality of apparatuses in addition to being executed by one apparatus.

In addition, this technique can also take the following structures.
(1) a plurality of processing units;
A connection control unit for controlling connection between the plurality of processing units,
The connection control unit
If there is no second logical channel established with another processing unit corresponding to the first logical channel established with one of the processing units, the logical channel with respect to the first logical channel A table creating unit that creates table information indicating a correspondence relationship between the first logical channel without designating a logical channel corresponding to the first logical channel;
A table storage unit for storing the table information created by the table creation unit;
When the second logical channel is present, the table information about the second logical channel stored in the table storage unit is used as the logical information corresponding to the second logical channel as the first logical channel. An information processing apparatus comprising: a table updating unit that updates the channel so as to be a channel.
(2) The connection control unit
A logical channel establishment unit for establishing the logical channel with the processing unit;
When the first logical channel is established by the logical channel establishment unit and the second logical channel does not exist, the table creation unit obtains the table information about the first logical channel as the first logical channel. Create without specifying the logical channel corresponding to one logical channel,
When the first logical channel is established by the logical channel establishment unit, and the second logical channel exists, the table update unit is configured to store the second logical channel stored in the table storage unit. The information processing apparatus according to (1), wherein the table information regarding the first logical channel is updated to be a logical channel corresponding to the second logical channel.
(3) Each of the table creation unit and the table update unit determines whether or not the second logical channel corresponding to the first logical channel exists based on a correspondence table of characteristics of each logical channel. The information processing apparatus according to (2).
(4) The plurality of processing units include a first processing unit in which the logical channel establishment unit establishes the logical channel for each function, and a second processing unit in which the logical channel establishment unit establishes the logical channel for each protocol. Including a processing unit,
The correspondence table includes information indicating correspondence between the function and the protocol as the feature,
The table creation unit is established with the second processing unit based on the correspondence table when the first logical channel is established with the first processing unit by the logical channel establishment unit. When the second logical channel of the protocol corresponding to the function of the first logical channel does not exist, the table information indicating the correspondence relationship between the logical channels is stored for the first logical channel. Create without specifying the logical channel corresponding to the logical channel,
When the first logical channel is established between the table update unit and the first processing unit by the logical channel establishment unit, the table update unit is established with the second processing unit based on the correspondence table. When there is a second logical channel of a protocol corresponding to the function of the first logical channel, the table information about the second logical channel stored in the table storage unit is The information processing apparatus according to (3), wherein one logical channel is updated to be a logical channel corresponding to the first logical channel.
(5) The information processing apparatus according to any one of (2) to (4), wherein the logical channel establishment unit establishes logical channels having different communication standards with each processing unit.
(6) The information according to any one of (2) to (5), wherein the logical channel establishment unit establishes the logical channel with the requested processing unit based on a request from each processing unit. Processing equipment.
(7) The information processing apparatus according to any one of (2) to (6), wherein the logical channel establishment unit assigns identification information to the established logical channel.
(8) The connection control unit further includes a state storage unit that stores information indicating a current state of the logical channel established by the logical channel establishment unit. Information processing device.
(9) The information processing apparatus according to any one of (1) to (8), wherein the table information is information indicating a correspondence relationship between logical channels using logical channel identification information.
(10) When the logical channel is disconnected, the table update unit deletes the information of the disconnected logical channel from the table information stored in the table storage unit. (1) to (9) The information processing apparatus according to any one of the above.
(11) The information processing apparatus according to any one of (1) to (10), wherein the table storage unit reserves a storage area for storing the table information in advance.
(12) The plurality of processing units include a control unit that controls each unit of the information processing device, and a device that can be attached to and detached from the information processing device. Information processing device.
(13) The information processing apparatus according to any one of (1) to (12), wherein the connection control unit further includes a wireless communication unit that performs wireless communication with another device.
(14) In the information processing method of the information processing apparatus,
The information processing apparatus is
When there is no second logical channel established with another processing unit corresponding to the first logical channel established with one processing unit, the logical channel between the logical channels The table information indicating the correspondence relationship is created without designating the logical channel corresponding to the first logical channel,
Storing the created table information;
When the second logical channel exists, the stored table information about the second logical channel is set so that the first logical channel is a logical channel corresponding to the second logical channel. Information processing method to be updated.
(15) Connect the computer
When there is no second logical channel established with another processing unit corresponding to the first logical channel established with one processing unit, the logical channel between the logical channels A table creation unit that creates table information indicating the correspondence relationship of the first logical channel without specifying a logical channel corresponding to the first logical channel;
A table storage unit for storing the table information created by the table creation unit;
When the second logical channel is present, the table information about the second logical channel stored in the table storage unit is used as the logical information corresponding to the second logical channel as the first logical channel. A program that functions as a table updater that updates channels.

  100 NFC device, 111 DH, 112 CLF, 113 UICC, 121 HCI, 122 E-HCI, 131 antenna

Claims (7)

A plurality of processing units each implementing an arbitrary application;
A connection control unit configured to connect to each of the processing units to establish a logical channel, and to control connection between the plurality of processing units through itself;
The connection control unit associates logical channels established between different processing units according to a communication protocol used for the arbitrary application implemented by the processing unit, and sets the associated logical channels. a table information for storing information, the information processing apparatus the communication protocol to create a table information associating a common logical channels together. The information processing apparatus according to claim 1, wherein the connection control unit establishes the logical channel based on a request from the processing unit. The information processing apparatus according to claim 1, wherein the plurality of processing units include a control unit that controls each unit of the information processing apparatus and a device that is detachable from the information processing apparatus. The information processing apparatus according to claim 1, wherein the information processing apparatus is an NFC device. The information processing apparatus according to claim 1, wherein the connection control unit establishes the logical channel having a different communication standard for each processing unit. Table information for storing information on the associated logical channels by associating logical channels established between different processing units according to a communication protocol used for an arbitrary application implemented by each of the plurality of processing units. And creating table information for associating logical channels having a common communication protocol to establish a logical channel by connecting to each of the plurality of processing units, and between the plurality of processing units via itself Control connections
Information processing method. Computer
A plurality of processing units each implementing an arbitrary application;
Table information that stores logical channels established between different processing units and stores the associated logical channel information in accordance with the communication protocol used for each arbitrary application implemented by the processing unit. And creating table information for associating logical channels with a common communication protocol to establish a logical channel by connecting to each of the processing units, and connecting between the plurality of processing units via itself Connection controller configured to control
Program to function as.

Images