KR20130030852A - Service anti-collision method for host controller interface, equipment, booting method and host controller therefor - Google Patents

Abstract

PURPOSE: A method for preventing a service collision of a host controller interface layer, a terminal device therefor, a booting method thereof, and a host controller thereof are provided to prevent a collision of a service application. CONSTITUTION: An NFC terminal(200) includes a host controller(210) and a UICC(Universal Integrated Circuit Card) host(220). A management gate(211) exists in the host controller. Card RF gates(212-214) are included in the bottom of the management gate. The management gate and the card RF gates in the host controller transceive a command and an event of a HCI. The management gate and card application gates(222-224) are included in the UICC host. A service application(225) operates a specific application by using RF type technology. [Reference numerals] (220') RF reader device; (225) Service application(AID#1)

Description

Service Anti-Collision Method for Host Controller Interface, Equipment, Booting Method and Host Controller therefor}

The present specification relates to a service collision prevention method of a host controller interface (HCI) layer in a terminal device including a Universal Integrated Circuit Card (UICC) hereinafter, a terminal device and a booting method, and a host controller therefor.

Recently, NFC has been discussed as a method of short-range wireless communication. NFC communication uses a 13.56 MHz frequency band (bandwidth of 14 kHz) between terminals equipped with an NFC module (hereinafter referred to as an NFC terminal) of up to 10 centimeters. It is a technology that transmits and receives data at a maximum speed of 424Kbps at close range.

NFC communication is largely defined to operate in three modes: card emulation mode, P2P mode, and reader / writer mode.

This NFC technology is an extension of the ISO / IEC 14443 access card standard that provides communication between smart cards and readers within a single device.

Among the three operation modes of the NFC communication, the card emulation mode is a method in which a service is provided by an NFC-equipped terminal recognized by an external RF reader device (aka dongle) like an NFC tag (eg, a credit card). , Transportation cards, etc.)

Some RF reader devices adopt a method of accessing the same service to multiple RF technologies to provide the reader's own RF technology compatibility. For this reason, when the NFC-enabled terminal supports a plurality of RF technology based card emulation modes, a "duplicate card" error occurs according to service logic (eg, a traffic card).

On the other hand, used as a smart card in wireless communication systems such as GSM and Universal Mobile Telecommunication System (UMTS), such as UICC or Universal Subscriber Identity Module (USIM), which integrates and secures all kinds of personal information. It is usually in charge of a few hundred Kbytes or more.

UICC includes Subscriber Identity Module (SIM) applications on GSM networks, Universal Subscriber Identity Module (USIM) applications on UMTS networks, and other applications that can access both GSM and UMTS networks, or address books (Phonebooks) or Can be used as storage for other applications.

Meanwhile, in a terminal including a UICC, a host controller is used for control between a UICC host and a terminal host. The host controller may be defined as a host controller or a host controller interface (hereinafter, referred to as 'HCI'). Several techniques for such HCI are specified in TS 102.622, et al., Standard of the ETSI.

However, as described above, according to various technologies currently defined in relation to HCI, when an NFC terminal providing multiple RF technologies for card emulation contacts an RF reader device supporting multiple RF technologies, a collision or duplicate card There is a problem that an error may occur.

An embodiment of the present invention is to provide a method for preventing a collision of a service application when supporting various RF technologies in a terminal device including a host (UICC) and a host controller.

An embodiment of the present invention aims to define and manage a pre-selected service / RF parameter including currently running service application identification information and RF gate identification information.

An embodiment of the present invention creates a pipe between a plurality of card RF gates and a management gate in the host controller at booting of the terminal, and authenticates the corresponding service according to a pre-selected service / RF parameter when requesting a service from the outside. The purpose is to perform.

In order to achieve the above object, an embodiment of the present disclosure includes a host controller including one management gate and two or more card RF gates, one management gate and two or more card application gates, and one or more service applications. A terminal device including a host, comprising: a terminal device and a booting method for generating a pipe between a management gate of the host controller and the card RF gate in the host controller when the terminal is booted.

According to another embodiment of the present invention, a terminal apparatus including a host controller including one management gate and one or more card RF gates, and a host including one management gate, one or more card application gates and one or more service applications. As one of the card RF gates receives a service application selection (SELECT) signal from the outside, and acquires a preselected service / RF parameter (SELECTED_AID_RF) from a host controller management gate, and then the preselected service / RF parameter (SELECTED_AID_RF). A terminal device and a service collision prevention method for determining whether a service application specified by a service application selection signal is executable or not is provided.

According to another embodiment of the present invention, a terminal apparatus including a host controller including one management gate and two or more card RF gates, and a host including one management gate, two or more card application gates, and one or more service applications. In one of the card RF gate receives a service application selection (SELECT) signal from the outside, and after obtaining a pre-selected service / RF parameter (SELECTED_AID_RF) from the host controller management gate, 1) the pre-selected service / RF parameter Is the initial value of (SELECTED_AID_RF) or

2) Whether the service application identification information AID_n included in the preselected service / RF parameter SELECTED_AID_RF is the same as the service application identification information AID # 1 included in the service application selection signal, and the preselection; It is determined whether the RF gate identification information (GATE ID_n) included in the service / RF parameter (SELECTED_AID_RF) and the ID (GATE_ID # 1) of the card RF gate itself having received the service application selection signal are the same. Provided is a terminal device for executing a corresponding service application only when it is determined to be the initial value in 1) or the same in 2), and a service collision prevention method.

According to another embodiment of the present invention, a terminal apparatus including a host controller including one management gate and two or more card RF gates, and a host including one management gate, two or more card application gates, and one or more service applications. The terminal for storing the pre-selected service / RF parameter (SELECTED_AID_RF) including the currently selected service application identification information (AID) and card RF gate identification information (GATE_ID) in the registry for the management gate of the host controller. to provide.

According to another embodiment of the present invention, a host controller included in a near filed communication (NFC) terminal device to control a UICC (host), wherein the host controller includes one management gate and two or more card RFs connected to pipes thereof. And a pre-selected service / RF parameter (SELECTED_AID_RF) including a service application identification information (AID) and a card RF gate identification information (GATE_ID) currently selected according to a request of a card RF gate. Provide a host controller that extracts and transfers or updates data from the register.

1 shows the structure of a host controller (terminal CLF) and a host (UICC) for card emulation.
2 illustrates an internal structure of an NFC terminal and a UICC host according to an embodiment of the present invention.
3A and 3B illustrate an example of configuration of an HCP packet and an HCP message to which an embodiment of the present invention is applied, respectively.
Figure 4 shows the data flow between the card RF gate and the card application gate in the course of running the service application, which can be applied to an embodiment of the present invention.
5 is a flowchart illustrating a terminal booting process according to an embodiment of the present invention.
6 is a flowchart illustrating a service collision avoidance method in a terminal according to the present invention.

Hereinafter, some embodiments will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present disclosure rather unclear.

In addition, the present specification describes a wireless communication system as an example, and the work performed in the wireless communication is characterized in that it includes all the operations performed in the system that controls the wireless communication and the wireless communication device that transmits data with the system.

NFC technology provides a card emulation mode through a single wired protocol (SWP) and a host controller interface (HCI) between the terminal and the UICC. The SWP provides the physical layer and the MAC layer, while the HCI provides the network layer on the NFC card emulation that actually exchanges data between the NFC terminal and the outside.

NFC card emulation mode-based service is a service within the UICC of the NFC terminal through RF technology (eg, ISO14443 Type A, etc.) supported by the RF reader device at regular intervals by an RF reader device (aka dongle) attached to a bus or credit card merchant. It is provided by selecting an application (for example, an applet) and performing a subsequent operation based on the response of the NFC terminal (UICC). ETSI TS 102.622 defines the interworking between such HCI-based NFC terminal and UICC, and ETSI TS 102.705 provides an API (Application Programming Interface) for controlling the detailed RF technology of HCI in a service application in UICC.

According to ETSI TS 102.622, HCI technology consists of a Host, a Gate, a Pipe, and a Registry.

The host means CLF and UICC of the terminal, and the CLF may be expressed as a terminal host and a UICC host.

Various gates exist in such a host, and a gate and a gate are connected through a pipe to transmit and receive events and commands. Each gate has a registry that stores the necessary information and responds to requests.

The host controller (terminal CLF) and host (UICC) have one administration gate, and multiple card RF gates (terminal or host controller side), depending on the type of RF technology on the card emulation to provide. ) And a card application gate (UICC side or host side) are created and initialized during the terminal booting process.

1 shows the structure of a host controller (terminal CLF) and a host (UICC) for card emulation.

The structure of RF technology for card emulation between a host controller (terminal CLF) and a host (UICC) defined in detail in ETSI TS 102.622 is shown in FIG. 1, and as shown in FIG. Each card RF gates 111-114 are included in accordance with RF technology (types A, B, B'D).

In addition, the host side 120 has an application application related to each RF technology (for example, banking, various types of transportation card services, etc.), and an application selection unit of each RF technology type connected to each application. ), And each application selector has corresponding card application gates 121 to 124.

In addition, each of the card RF gates 111 to 114 on the host controller side is connected to the corresponding card application gate on the host side through a pipe.

On the other hand, RF technologies over NFC are not new technologies, but were previously used in credit cards and transportation cards. Such RF technologies exist in various ways, and specific RF reader devices are commercialized to select specific service applications based on a plurality of RF technologies in one RF reader device to secure compatibility between RF technologies.

Accordingly, in the structure as shown in FIG. 1, when an NFC terminal providing a plurality of RF technologies for card emulation contacts an RF reader device supporting a plurality of RF technologies, an error such as a collision or a duplicate card may be generated.

For example, if you select a primary card with a primary card set via PPSE used in the credit card industry, or if a service application is developed or modified using the HCI API of ETSI TS 102.705, you may not get a “duplicate card” error. It can be an obstacle in terms of compatibility and scalability of NFC technology. In addition, the modification of all RF reader devices to suit the NFC environment can be problematic in terms of cost and service scalability.

In addition, there is a limit in modifying all service applications to utilize the HCI API, and there is a limit in making all NFC UICCs support the HCI API. Therefore, there is a need for a method of utilizing a general-purpose and existing RF infrastructure.

 The present invention addresses this issue by adding an HCI connection (pipe generation) between the management gate and the card RF gate in the host controller (terminal CLF), and through a specific RF technology, If an applet is selected, a technique for preventing service collision is proposed by not transmitting a selection command for the same service application through another RF technology to the UICC host.

More specifically, in an embodiment of the present invention, a host controller including one management gate and two or more card RF gates, a host including one management gate and two or more card application gates and one or more service applications Provided with a terminal device comprising a, during booting of the terminal, it is possible to create a pipe between the management gate of the host controller and the card RF gate in the host controller. Further, after one of the card RF gates receives a service application selection (SELECT) signal from the outside and obtains a preselected service / RF parameter (SELECTED_AID_RF) from a host controller management gate, the preselected service / RF parameter (SELECTED_AID_RF). It is possible to determine whether or not the service application specified by the service application selection (SELECT) signal is executable.

To this end, the registry for the management gate of the host controller may store a pre-selected service / RF parameter (SELECTED_AID_RF) including the currently selected service application identification information (AID) and card RF gate identification information (GATE_ID). The management gate of the controller extracts and transmits a pre-selected service / RF parameter (SELECTED_AID_RF) including the currently selected service application identification information (AID) and card RF gate identification information (GATE_ID) from the register according to a request of the card RF gate. Can be updated or updated.

2 illustrates an internal structure of an NFC terminal and a UICC host according to an embodiment of the present invention.

NFC terminal 200 according to an embodiment of the present invention is configured to include a host controller 210 or the CLF and UICC host 220 of the terminal.

One management gate 211 is present in the host controller, and one or more RF type-specific card RF gates 212 to 214 are included under the management gate. Such a host controller may be expressed in other terms such as an NFC controller as the CLF of the terminal.

In addition, a communication function is provided between the management gate 211 in the host controller 210 and the card RF gates 212 to 214 for each RF type to transmit and receive events and commands of the HCI, and specifically, the HCI. Can be connected to each other by pipes according to the standard.

In addition, the UICC host 220 also includes one management gate 221 and one or more RF type-specific card application gates 222 to 224, and can drive a specific application using one or more RF type technologies. There is a service application 225 (AID; Applet ID) that may be present.

In FIG. 2, there are three types of RF types 1 to 3, and it is assumed that the service application 225 (AID) can operate by all three types of RF technologies.

In addition, the outside of the NFC terminal 200 includes an RF reader device 220 'that selects and drives a specific service application through a plurality of RF technologies.

The NFC terminal creates a pipe at boot time between the management gate of the host controller and the card RF gate in the host controller, and as described below, one of the card RF gates is a service application select (SELECT) signal from the outside. Received, and after obtaining the pre-selected service / RF parameter (SELECTED_AID_RF) from the host controller management gate, execution of the service application specified by the service application selection (SELECT) signal using the pre-selected service / RF parameter (SELECTED_AID_RF) It can be determined whether or not, and the specific scheme will be described in more detail with reference to FIGS. 5 and 6 below.

Hereinafter, the HCI technology and the configuration of the host, gate, pipe, and the like will be described in detail.

HCI stands for a logical interface that allows the use of a contactless application hosted on a UICC. In particular, to perform control on a host (ie, UICC host) mounted inside a UICC connected to a host controller embedded in a contactless front end (hereinafter referred to as “CLF”) of the terminal. will be.

These HCIs can be broadly divided into two parts: HCI cores and contactless platforms, where HCI cores specify logical interfaces that are independent of specific applications, and contactless platforms can be used to implement HCI cores for specific contactless applications using UICC and CLF. It is related.

In addition, a low-level protocol for supporting HCI may be separately defined, for example, Single Wire Protocol (SWP).

In the present specification, the length of all data is in bytes unless otherwise specified, and each byte is represented by b8 to b1 (b8 is the leftmost bit). Hexadecimal values are indicated by a single expression, such as '1F'.

In one embodiment of the present invention, a host, i.e., a UICC, is physically connected to a host controller, and HCI defines an interface between hosts.

The HCI architecture is defined by three major levels: a set of gates, a Host Controller Protocol (HCP) messaging mechanism, and an HCP routing mechanism, with each gate exchanging commands, responses, and events, and the HCP routing mechanism provides a message when needed. Can be divided into

Each host may have a stack structure of any physical and data link layer, an HCP routing layer, an HCP messaging layer, and a gate layer from a lower level.

In the case of a UICC host, the arbitrary physical and data link layers may be SWP layers, and in the case of a terminal host and an additional host, the physical and data link layers may be the same physical and data layer structures as the host controller.

The host controller performs a function of mediating packet transmission between the UICC host and the terminal host in the physical and data link layer and the HCP routing layer. The host controller provides a predetermined physical and data link layer (SWP layer) for connection with the UICC host. And an HCP routing layer thereon.

For proper operation, the HCP has a data link layer beneath it, and the data link layer (e.g. SWP) is error free and orderly receive / transmit is preferred, and provides unique data flow control. A packet of a layer is delivered with a maximum size unique to a data link layer, and the size of each received packet is reported to an upper layer.

Meanwhile, the gate provides an entry point of a service operated inside each host. HCP allows gates to exchange messages from other hosts, and there are two types of gates: a management gate or an administration gate and a generic gate.

The management gate is used for the management of the host network, the generic gate is independent of the management of the host network and the characteristics are defined only within the HCI core.

The gate type is classified by a gate identifier, and the gate identifier may be defined as shown in Table 2 below.

[Table 1] An example of the gate identifier

The gate identifier may be uniquely defined within the range of the host (from '10' to 'FF') or may have the same value as the same gate type of all hosts ('00' to '0F').

The host and the gate may have the following characteristics.

Every host and host controller must have one administration gate, every host can have one link management gate and the host controller must have one link management gate.

In addition, every host and host controller should have one identity management gate and one loop back gate, and may have one or more generic gates.

The card RF gate and the card application gate in one embodiment of the present invention may be one type of such a comprehensive gate.

Meanwhile, 'pipe' is defined as a logical communication channel between two gates.

There are two types of pipes: static pipes and dynamic pipes. Static pipes are always available and do not need to be created or deleted, and dynamic pipes can be created and deleted. Can be.

The state of the pipe can be open (open) or closed (closed) and must be maintained continuously until the host power is down and back up. The state of the pipe must remain persistent as long as the host is temporarily removed from the host network and not replaced by another device. The state of dynamic pipes immediately after their creation and the initial state of static pipes should always be closed.

Pipe Identifier The PID has a length of 7 bits and the value of the PID is used in the head of the HCP packet as routing information. The pipe identifiers of the static pipes are predefined as shown in Table 3 below, and the pipe identifiers of the dynamic pipes are dynamically allocated by the host controller.

Table 2. Static Pipe Identifiers (PIDs)

Static pipes always connect the gates of the host and the gates of the host controller, while dynamic pipes connect the two gates of the other hosts. Static pipes and dynamic pipes can connect different types of gates, as shown in Table 3, and dynamic pipe identifiers are uniquely defined within the host network.

Meanwhile, a registry template is associated with all gates, and the registry template defines gate-related parameters. A parameter is identified by a parameter identifier consisting of 1 byte, and the parameter identifier is uniquely defined within the range of the gate.

The parameter identifiers of all gates are defined within the range of '00' to 'EF', and the parameter identifiers in the range of 'F0' to 'FF' may be used for a proprietary purpose.

For each pipe connected to the gate, a new instance of the registry is created. When creating a pipe, the Access Rights Read-Write or Write-Only parameters of all registry parameters are the default values. Is set. The Read-Only (RO) parameter may be set to an appropriate value different from the default value.

The host is responsible for managing the registry concerned, and the registry's persistence and default values are dictated by each registry description.

When a pipe is deleted, its registry instance is also deleted.

The HCP packet transmitted and received between each host and the host controller may have a format as shown in FIG. 3A.

That is, each host may transmit and receive an HCP packet having a format as shown in FIG. 3 using a data link layer.

The HCP packet may be divided into a packet head and a message area. The packet head may be further divided into a CB (Chaining Bit) field of 1 bit (b8) and a pID field of 7 bits (b7 to b1). It can consist of a total of n byte field values.

The CB field has a value of 1 unless a message fragmentation is used as a coupling bit, and pID is a pipe identifier.

The host controller forwards the packet to the destination host using the pID field value. The destination host forwards the packet to the destination gate, which allows any two gates connected by a pipe to exchange messages using this mechanism.

3B shows an example of an HCP message structure.

The HCP message includes one instruction information and optionally data.

The HCP message may be composed of an 8-bit head and n bytes of data, and the head may be composed of a type field of 2 bits (b8 and b7) and an indication field of 6 bits (b6 to b1).

The type field is for indicating a type of indication, and the indication field is for indicating specific indication information.

Types of instructions include a command (Type value 0), an event (Type value 1), a response to the command (Type value 2), and the like. Type value 3 is reserved for future use. .

The indication field value authorizes commands, events, and responses, and all three types can transfer data.

The data field structure for indication information included in the HCP message of FIG. 3B may be defined in various tables.

Table 3 is a list of all kinds of commands (words) that can be included in an HCP message, and the meaning of each command applies equally at all gates.

Table 3 Commands Included in HCP Messages

As shown in Table 3, the command may be classified into a generic command applied to all gates and an administrative command required for managing the host network.

Attributes such as the description and length of the generic commands ANY_SET_PARAMETER, ANY_GET_PARAMETER, ANY_OPEN_PIPE, and ANY_CLOSE_PIPE defined in Table 3 are omitted.For example, as defined in the ETSI SCP standard TS 102 622. It may be configured.

On the other hand, when the management commands are roughly shown, ADM_CREATE_PIPE is used by the host to request the host controller to create a new dynamic pipe between two gates, and ADM_NOTIFY_PIPE_CREATED is used to generate the dynamic pipe to the destination host of the pipe where the host controller is created. ADM_DELETE_PIPE is a command used by the host to notify the host controller about deleting a dynamic pipe. ADM_NOTIFY_PIPE_DELETED command is a command sent by the host controller to the host to notify the deletion of a dynamic pipe. .

Each management command may have a command parameter, and a component that receives each command may give a predetermined response according to a processing result. The response may include an ANY_OK response indicating that the processing is completed normally and a plurality of error responses indicating that the processing is not completed. The types and meanings of the error responses will be described below. In addition, the response may also include a predetermined parameter (response parameter).

Figure 4 shows the data flow between the card RF gate and the card application gate in the course of running the service application, which can be applied to an embodiment of the present invention.

4, as described in FIG. 6 below, after a request for selecting a specific service application is received from an external RF reader device, a flow of a process in which the specific RF type and a specific service application are authenticated as being legitimately available and the service is performed. Means.

First, the card RF gate transmits the EVT_FIELD_ON message to the card application gate (S410), and generates an initialization and collision prevention message according to an embodiment of the present invention (S420).

Next, the card RF gate transmits an EVT_CARD_ACTIVATED message to the card application gate to activate the corresponding card application (gate) (S430), and then transmits and receives data using the EVT_SEND_DATA command between the gates (S440 and S450).

When the service is completed, the card RF gate sends the EVT_CARD_DEACTIVATED message to the card application gate to deactivate the corresponding card application (gate) and finally terminates the service by sending the EVT_FIELD_OFF message.

Meanwhile, the management gate in the host controller supports various parameters in the registry. In an embodiment of the present invention, in order to prevent service collision, the parameters of 01 to 04 of Table 4 (SESSION_IDENTITY, MAX_PIPE, WHITELIST, and HOST_LIST) of Table 4 are currently defined. In addition to the above, the SELECTED_AID_RF parameter is additionally defined and supported.

[Table 4]

 SELECTED_AID_RF is information that can indicate a service application and RF technology (type) currently being performed, and is not limited to the above terms. In this specification, the term SELECTED_AID_RF is used as equivalent to the term preselected service / RF parameter.

The SELECTED_AID_RF or the pre-selected service / RF parameter may include a specific service application identification (AID) and RF gate ID (RF Gate ID) currently selected, and the service application identification information (AID) is 5 to 16 bytes. The RF gate ID may have a length of 1 byte, but is not limited thereto.

Also, the initial value of the SELECTED_AID_RF or the pre-selected service / RF parameter is 'FFF…'. FFF (total length is 6 to maximum 17 bytes) ', but is not limited thereto. When the SELECTED_AID_RF or the pre-selected service / RF parameter is an initial value, it indicates that there is no service application or RF gate currently being executed.

Such SELECTED_AID_RF or pre-selected service / RF parameter executes a specific command (for example, ANY_GET_PARAMETER and ANY_SET_PARAMETER) through a dynamic pipe with a management gate in a card RF gate generated at the terminal booting (described in connection with FIG. 5 below). Parameter that can be read and written.

5 is a flowchart illustrating a terminal booting process according to an embodiment of the present invention.

NFC terminal according to an embodiment of the present invention during the booting process, the host controller (CLF of the terminal) and the host (UICC) performs the SWP and HCI initialization process, between the management gate of the host controller and the management gate of the host The command generates and initializes RF gates for the supported RF technology initially set in the UICC (host), that is, the card RF gate on the host controller side and the card application gate on the host side.

When initialization of each card RF gate (terminal side or host controller side) and card application gate (host side or UICC side) is completed, a predetermined interval is established between each RF type card RF gate in the host controller and the management gate of the host controller. Dynamic pipes are created with commands (such as ADM_CREATE_PIPE).

Referring to Figure 5 the flow of the NFC terminal booting method for preventing a service collision according to an embodiment of the present invention in detail as follows.

First, when booting starts, the management gate of the host (UICC) transmits a pipe creation message (ADM_CREATE_PIPE) to the management gate of the host controller. (S510) According to the command, the pipe is connected between the management gate of the host and the management gate of the host controller. Is generated, the management gate of the host controller sends a pipe creation notification message (ADM_NOTIFY_PIPE_CREATED) to the card RF gate of the host controller, and the card RF gate returns a response message (ANY_OK) thereto (S520 and S530).

Next, the card RF gate that returns a response message (ANY_OK) to the pipe creation notification message (ADM_NOTIFY_PIPE_CREATED) sends the pipe creation message (ADM_CREATE_PIPE) to the host controller management gate, and the host controller management gate responds to it with the response message (ANY_OK). ) Is returned to the card RF gate (S540 and S550). A dynamic pipe is generated between the management gate inside the host controller and the card RF gate for each RF type, so that a service collision prevention process as shown in FIG. 6 may be performed. It becomes a state.

Finally, the host controller management gate transmits a final response message (ANY_OK) to the management gate of the host controller (S560).

The process of creating a pipe between the management gate of the host and the management gate of the host controller by the steps S510 to S530 and S560 is a previously defined technique. In an embodiment of the present invention, the host controller may implement a service collision prevention. The S540 and S550 steps are further configured to generate a dynamic pipe between the management gate and the card RF gate for each RF type.

6 is a flowchart illustrating a service collision avoidance method in a terminal according to the present invention.

First, the card RF gate inside the host controller receives a service application selection (SELECT) signal including service application identification information (AID) through a specific type of RF from an external RF reader device (S610).

The card RF gate that receives the service application select (SELECT) signal is the card RF gate that supports the corresponding RF type among the multiple card RF gates.

In FIG. 6, the card RF gate receiving the service application select signal is gate 1 (GATE_ID # 1), and the service application identification information (AID) included in the service application select signal is 1 service application ( AID # 1).

The card RF gate receiving the service application select signal transmits ANY_GET_PARAMETER, which is a preselected service / RF parameter request message for acquiring the preselected service / RF parameter (SELECTED_AID_RF) to the management gate of the host controller (S620).

The host controller management gate receiving the preselected service / RF parameter request message (ANY_GET_PARAMETER) reads the preselected service / RF parameter (SELECTED_AID_RF) corresponding to '05' of Table 4 from the registry and responds to the corresponding card RF gate. (ANY_OK; S630)

Then, the corresponding card RF gate GATE_ID # 1 is 1) whether the received preselected service / RF parameter SELECTED_AID_RF is a predetermined initial value, or 2) within the preselected service / RF parameter SELECTED_AID_RF received from the management gate. 3) whether the service application identification information AID_n included is the same as the service application identification information AID # 1 included in the service application selection signal received from the external RF reader, and 3) the pre-selected service / RF parameter. It is determined whether the RF gate identification information (GATE ID_n) included in the (SELECTED_AID_RF) is the same as the ID (GATE_ID # 1) of the card RF gate itself (S640).

If the received pre-selected service / RF parameter (SELECTED_AID_RF) is a preset initial value (for example, 'FFF ... FFF'), or is included in the pre-selected service / RF parameter (SELECTED_AID_RF) received from the management gate. The RF gate included in the identification information AID_n is the same as the service application identification information AID # 1 included in the service application selection signal received from the external RF reader device and included in the pre-selected service / RF parameter SELECTED_AID_RF. If the identification information GATE_ID_n is equal to the ID GATE_ID # 1 of the card RF gate itself (YES), it is determined that the corresponding application can be executed.

If the status is YES, the service application can be executed. Therefore, the selected service / RF parameter (SELECTED_AID_RF) including the service application identification information (AID # 1) and the RF gate identification information (GATE_ID # 1) is executed. Transmits a parameter setting message (ANY_SET_PARAMETER) requesting an update to the management gate of the host controller (S650).

The management gate of the host controller updates the pre-selected service / RF parameter (SELECTED_AID_RF) including service application identification information (AID # 1) and RF gate identification information (GATE_ID # 1) in the registry, and updates the response signal (ANY_OK). Return to the RF gate (S660).

In operation S660 of updating the preselected service / RF parameter SELECTED_AID_RF, if the length of the service application identification information AID # 1 is less than 16 bytes, the remaining bytes may be padded with 'FF'.

Then, the card RF gate GATE_ID # 1 performs the service as shown in FIG. 4 through the card application gate # 1 in the corresponding host (S670).

That is, after transmitting EVT_FIELD_ON, the data flow by ETSI TS 102 622 is followed.

In step S640, the received pre-selected service / RF parameter (SELECTED_AID_RF) is not a preset initial value (for example, 'FFF ... FFF'), but within the pre-selected service / RF parameter (SELECTED_AID_RF) received from the management gate. The included service application identification information AID_n is not the same as the service application identification information AID # 1 included in the service application selection signal received from the external RF reader device or in the preselected service / RF parameter SELECTED_AID_RF. If the included RF gate identification information (GATE_ID_n) is not the same as the ID (GATE_ID # 1) of the card RF gate (NO), no additional operation is performed (EVT_FIELD_ON event not transmitted).

By using the above embodiments, it is possible to prevent a collision for a specific service application in a terminal including a UICC supporting various RF technologies.

In addition, when the NFC terminal is contacted with an RF reader device that selects the same service application (AID) through multiple RF technologies installed at home and abroad, and provides a card emulation mode based service, a “duplicate card” error or service conflict Can be prevented from occurring, and in particular, a service collision can be prevented without changing the configuration of an existing RF reader device or changing a service application (applet).

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. In other words, within the scope of the present invention, all of the components may be selectively operated in combination with one or more. In addition, although all of the components may be implemented as one independent hardware, some or all of the components may be selectively combined to perform a part or all of the functions in one or a plurality of hardware. As shown in FIG.

It is also to be understood that the terms such as " comprises, "" comprising," or "having ", as used herein, mean that a component can be implanted unless specifically stated to the contrary. But should be construed as including other elements. All terms, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used terms, such as predefined terms, should be interpreted to be consistent with the contextual meanings of the related art, and are not to be construed as ideal or overly formal, unless expressly defined to the contrary.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims (17)

A terminal device comprising a host controller including one management gate and two or more card RF gates, and a host including one management gate and two or more card application gates and one or more service applications.
At boot of the terminal,
And a pipe is created between the management gate of the host controller and the card RF gate in the host controller. The method of claim 1,
The card RF gate transmits a pipe creation message (ADM_CREATE_PIPE) to a host controller management gate to generate the pipe, and the host controller management gate returns a response message (ANY_OK) thereto to the card RF gate. . A booting method of a terminal device including a host controller including one management gate and two or more card RF gates, and a host including one management gate and two or more card application gates and one or more service applications.
Generating a pipe between the management gate of the host and the management gate of the host controller by transmitting a pipe creation message (ADM_CREATE_PIPE) to the management gate of the host controller;
Generating a pipe between the card RF gate and the host controller management gate by transmitting a pipe creation message (ADM_CREATE_PIPE) to the host controller management gate by the card RF gate;
Booting method of a terminal device comprising a. A terminal device including a host controller including one management gate and one or more card RF gates, and a host including one management gate, one or more card application gates, and one or more service applications.
One of the card RF gates receives a service application selection (SELECT) signal from the outside, obtains a preselected service / RF parameter (SELECTED_AID_RF) from a host controller management gate, and then selects the preselected service / RF parameter (SELECTED_AID_RF). And determining whether the service application specified by the service application selection signal is executable. A terminal device including a host controller including one management gate and two or more card RF gates, and a host including one management gate, two or more card application gates, and one or more service applications.
After one of the card RF gates receives a service application selection (SELECT) signal from the outside and obtains a preselected service / RF parameter (SELECTED_AID_RF) from a host controller management gate,
1) Whether the pre-selected service / RF parameter (SELECTED_AID_RF) is an initial value or
2) Whether the service application identification information AID_n included in the preselected service / RF parameter SELECTED_AID_RF is the same as the service application identification information AID # 1 included in the service application selection signal, and the preselection; Whether the RF gate identification information (GATE ID_n) included in the service / RF parameter (SELECTED_AID_RF) and the ID (GATE_ID # 1) of the card RF gate itself that received the service application selection (SELECT) signal are the same.
Judging
The terminal device characterized in that the service application is executed only when it is determined to be the initial value in 1) or the same in 2). The method of claim 5,
And the service application identification information (AID_n) included in the pre-selected service / RF parameter (SELECTED_AID_RF) is 5 to 16 bytes, and the RF gate identification information (GATE ID_n) is 1 byte of information. The method of claim 5,
The initial value of the preselected service / RF parameter SELECTED_AID_RF is' FFF... FFF ”terminal device. The method of claim 5,
If it is determined as the initial value in 1) or the same in 2), the pre-selected service / RF parameter including service application identification information (AID # 1) and RF gate identification information (GATE_ID # 1) is executed. And a SELECTED_AID_RF) in the registry. A method of preventing a service collision of a terminal device including a host controller including one management gate and one or more card RF gates, and a host including one management gate, one or more card application gates, and one or more service applications,
A first card RF gate of the card RF gates receives a service application select signal from an external source;
Obtaining, by the first card RF gate, a pre-selected service / RF parameter (SELECTED_AID_RF) from the host controller management gate;
Determining, by the first card RF gate, whether the service application specified by the service application selection (SELECT) signal is executable using the pre-selected service / RF parameter (SELECTED_AID_RF);
Service conflict prevention method comprising a. A method of preventing a service collision of a terminal device including a host controller including one management gate and two or more card RF gates, and a host including one management gate, two or more card application gates, and one or more service applications,
A first card RF gate (GATE_ID # 1) of the card RF gates receiving a service application selection (SELECT) signal from the outside;
Obtaining, by the first card RF gate (GATE_ID # 1), a pre-selected service / RF parameter (SELECTED_AID_RF) from a host controller management gate;
1) whether the first card RF gate GATE_ID # 1 is 1) the initial value of the preselected service / RF parameter SELECTED_AID_RF, or 2) service application identification information AID_n included in the preselected service / RF parameter SELECTED_AID_RF. ) Is identical to the service application identification information (AID # 1) included in the service application selection (SELECT) signal, and the RF gate identification information (GATE ID_n) included in the pre-selected service / RF parameter (SELECTED_AID_RF) and the service. Determining whether or not the ID (GATE_ID # 1) of the card RF gate itself having received the application selection signal is the same; And
Executing a corresponding service application only when it is determined to be the initial value in 1) or the same in 2);
Service conflict prevention method comprising a. The method of claim 10,
The service application identification information (AID_n) included in the preselected service / RF parameter (SELECTED_AID_RF) is 5 to 16 bytes, and the RF gate identification information (GATE ID_n) is 1 byte of information. The method of claim 10,
The initial value of the preselected service / RF parameter SELECTED_AID_RF is' FFF... FFF ”service collision prevention method characterized in that. The method of claim 10,
If it is determined as the initial value in 1) or the same in 2), the pre-selected service / RF parameter including service application identification information (AID # 1) and RF gate identification information (GATE_ID # 1) is executed. Service conflict prevention method, comprising: updating SELECTED_AID_RF to the registry. A terminal device including a host controller including one management gate and two or more card RF gates, and a host including one management gate, two or more card application gates, and one or more service applications.
The terminal for storing a pre-selected service / RF parameter (SELECTED_AID_RF) including the currently selected service application identification information (AID) and card RF gate identification information (GATE_ID) in the registry for the management gate of the host controller. Device. 15. The method of claim 14,
And the service application identification information (AID_n) included in the pre-selected service / RF parameter (SELECTED_AID_RF) is 5 to 16 bytes, and the RF gate identification information (GATE ID_n) is 1 byte of information. A host controller included in an NFC (Near Filed Communication) terminal device to control a UICC (host),
The host controller includes a management gate and at least two card RF gates piped thereto.
The management gate of the host controller extracts a preselected service / RF parameter (SELECTED_AID_RF) including a currently selected service application identification information (AID) and card RF gate identification information (GATE_ID) according to a request of a card RF gate from a register. Host controller, characterized in that for transmitting or updating. 17. The method of claim 16,
And 5 to 16 bytes of service application identification information (AID_n) included in the preselected service / RF parameter (SELECTED_AID_RF) and 1 byte of RF gate identification information (GATE ID_n).

Images