CN103065107B - A kind of noncontact swipe the card application implementation method and device - Google Patents

Abstract

The invention discloses a method and device for realizing a non-contact card swiping application. The main technical solution includes: a CLF module in an NFC terminal receives a non-contact card swiping command, which carries an application identification of a card swiping application; The corresponding relationship with the application identification is to determine the security module identification corresponding to the application identification carried in the non-contact card swiping command; the non-contact card swiping command is sent to the security module corresponding to the determined security module identification for processing. According to this technical solution, the CLF module is connected to each security module built in the NFC terminal, and can route the non-contact card swiping command to the corresponding security module for processing according to the stored corresponding relationship, avoiding the security module that is effectively connected to the CLF module. The failure of card swiping caused by the mismatch with the security module supported by the contactless card swiping application improves the success rate of the contactless card swiping application.

Description

A method and device for implementing a non-contact card swiping application

technical field

The invention relates to the field of communication technology, in particular to a method and device for realizing a non-contact card swiping application.

Background technique

With the development of contactless card swiping technology, the contactless card swiping method has more and more performances superior to the contact card swiping method. For example, in the contactless card swiping method, there is no mechanical contact between the contactless card and the card reader terminal, avoiding Eliminate various failures caused by mechanical contact with the card reader terminal, such as avoiding the failure of card reading caused by rough card insertion, non-card foreign object insertion, dust or oil entering the card insertion area and other poor contact factors in the contact card swiping method . In addition, compared with contact cards, non-contact cards have no exposed modules on the surface, which avoids problems such as module falling off, electrostatic breakdown, bending damage, etc., and the reliability of the cards is higher. Therefore, contactless cards have been widely used due to their good performance and high cost performance, and have been widely used in various fields such as public transportation, medical care, campus card, and access control.

In order to make better use of the non-contact card swiping technology, the non-contact card swiping technology has been integrated with the popular mobile terminal. The mobile terminal with the non-contact card swiping function is the NFC (Near Field Communication, short-range wireless communication) terminal. The NFC terminal passes The built-in antenna and security module combine non-contact card swiping technology with mobile terminals to provide users with a good experience. Among them, the security module can be SIM (Subscriber Identity Module) card, SD (Secure Digital Memory Card, secure digital card), independent SE (Secure, security) module, etc.

NFC terminals can have three working modes, namely: card simulation mode, card reader mode and point-to-point mode. At present, the typical implementation schemes of NFC terminals are divided into two categories: one is CLF (Contactless Fronted, non-contact front) module and single The other type is that the CLF module is connected with all security modules built in the terminal at the same time. Figure 1 shows a schematic diagram of the structure of a CLF module connected to a single security module. As shown in Figure 1, the CLF module in the NFC terminal is only connected to one security module, which can be a SIM card, SD or an independent SE module, etc. . Figure 2 shows a schematic structural diagram of the CLF module being connected to various security modules built in the terminal at the same time. As shown in Figure 2, the CLF module in the NFC terminal is connected to the security modules such as the SIM card, SD and SE modules built in the NFC terminal at the same time.

In the connection mode between the CLF module and the security module shown in Figure 1, the CLF module is only fixedly connected to a single security module, so that there is a new security module introduced by the NFC terminal or a security module connected to the CLF module and a security module supported by the card swiping application In the case of a mismatch, the non-contact card swiping of the NFC terminal fails. For example, the CLF module in the NFC terminal is only connected to the SE module, if a SIM card is inserted into the NFC terminal, the contactless application on the SIM card will not be available. In the connection mode between the CLF module and the security module shown in Figure 2, although the CLF module in the NFC terminal can be connected to multiple security modules supported by the NFC terminal such as the SE module and the SIM card at the same time, in practical applications, the NFC terminal only It can support the CLF module to communicate with one of the connected security modules, that is, set the connection channel between the CLF module and one of the connected security modules as active, and set the other connection channels as dormant state, only the connection channel in the activated state can be used normally, so there is also a situation where the NFC terminal introduces a new security module or the security module connected to the CLF module that is set to the active state does not match the security module supported by the card swiping application. The contactless card swiping of the NFC terminal fails. For example, the CLF module in the NFC terminal is connected to the SE module and the SIM card, the connection channel between the CLF module and the SE module is set to the active state, and the connection channel between the CLF module and the SIM card is set to the dormant state, then the contactless application supports If the security module is a SIM card, the application will not work.

To sum up, existing NFC terminals cannot support non-contact card swiping applications due to the above reasons, and the success rate of non-contact card swiping applications is low.

Contents of the invention

In view of this, an embodiment of the present invention provides a method and device for implementing a non-contact card swiping application. By adopting the technical solution, the success rate of using the non-contact card swiping application can be improved.

Embodiments of the present invention are realized through the following technical solutions:

According to an aspect of an embodiment of the present invention, a method for implementing a contactless card swiping application is provided, including:

The non-contact front-end CLF module in the short-range wireless communication NFC terminal receives a non-contact card swiping command, and the non-contact card swiping command carries the application identification of the card swiping application;

According to the stored corresponding relationship between the security module identification and the application identification of the security module connected to the CLF module built in the NFC terminal, determine the security module identification corresponding to the application identification carried in the non-contact card swiping command;

Sending the non-contact card swiping command to the security module corresponding to the determined security module identifier for processing.

According to another aspect of the embodiments of the present invention, a device for realizing a contactless card swiping application is also provided, including:

A receiving unit, configured to receive a non-contact card swiping command, wherein the non-contact card swiping command carries an application identification of a card swiping application;

The first storage unit is used to store the corresponding relationship between the security module identification and the application identification of the security module connected to the non-contact front-end CLF module built in the short-range wireless communication NFC terminal;

A security module identification determination unit, configured to determine the security module identification corresponding to the application identification carried in the contactless card swiping command according to the correspondence stored by the first storage unit;

The command distribution unit is configured to send the contactless card swiping command received by the receiving unit to the security module corresponding to the security module identification determined by the security module identification determination unit for processing.

Through at least one of the above-mentioned technical solutions provided by the embodiments of the present invention, the CLF module in the NFC terminal receives a contactless card swiping command, which carries the application identification of the card swiping application in the non-contact card swiping command. The corresponding relationship between the security module identification and the application identification of the security module, determine the security module identification corresponding to the application identification carried in the non-contact card swiping command, and send the non-contact card swiping command to the security module corresponding to the determined security module identification to process. According to this technical solution, the CLF module is connected to each security module built in the NFC terminal, and can route the non-contact card swiping command to the corresponding security module for processing according to the corresponding relationship between the stored security module and the application identification, avoiding the The module has the problem of card swiping failure caused by the mismatch between the effectively connected security module and the security module supported by the contactless card swiping application, thereby improving the success rate of the contactless card swiping application.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the present invention, and constitute a part of the description, and are used together with the embodiments of the present invention to explain the present invention, and do not constitute a limitation to the present invention. In the attached picture:

FIG. 1 is a schematic flowchart of a method for implementing a contactless card swiping application provided by Embodiment 1 of the present invention;

FIG. 2 is a schematic structural diagram of an NFC terminal provided in Embodiment 1 of the present invention;

FIG. 3 is a schematic flow diagram of saving the corresponding relationship between security module identifiers and application identifiers provided by Embodiment 1 of the present invention;

FIG. 4 is a schematic flow diagram of determining a security module for processing the non-contact card swiping command through broadcasting provided by Embodiment 1 of the present invention;

5 is a schematic diagram of a connection state between a CLF module and a security module in an NFC terminal provided by Embodiment 1 of the present invention;

6 is a schematic flow diagram of the CLF module saving the information used to identify the state of the connection channel between the CLF module and the security module as open or closed provided by Embodiment 1 of the present invention;

FIG. 7 is a schematic flow diagram of verifying the sender of the indication information based on the symmetric key mechanism provided by Embodiment 1 of the present invention;

FIG. 8 is a schematic flow diagram of verifying the sender of the indication information based on the asymmetric key mechanism provided by Embodiment 1 of the present invention;

FIG. 9 is a schematic diagram of an application scenario of a contactless card swiping application provided by Embodiment 2 of the present invention;

FIG. 10 is a schematic flow diagram of implementing a non-contact card swiping application based on the scenario shown in FIG. 9 provided by Embodiment 2 of the present invention;

Fig. 11 is a schematic structural diagram of a device for implementing a non-contact card swiping application provided by Embodiment 3 of the present invention;

FIG. 12 is a schematic structural diagram of another implementation device for a contactless card swiping application provided by Embodiment 3 of the present invention.

Detailed ways

In order to provide an implementation plan for improving the success rate of non-contact card swiping applications, the embodiment of the present invention provides a method and device for implementing non-contact card swiping applications. The preferred embodiments of the present invention will be described below in conjunction with the accompanying drawings. It should be understood that , the preferred embodiments described here are only used to illustrate and explain the present invention, not to limit the present invention. And in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Embodiment one

Embodiment 1 of the present invention provides a method for implementing a non-contact card swiping application. This method can be applied to an NFC terminal, specifically, it can be implemented in a CLF module in an NFC terminal. By implementing this method in a CLF module, it is possible to realize Automatic routing of contactless card swiping applications, thereby improving the success rate of contactless card swiping applications.

Fig. 1 shows a schematic flowchart of a method for implementing a non-contact card swiping application provided by Embodiment 1 of the present invention. As shown in Fig. 1, the method mainly includes the following steps:

Step 101, the CLF module in the NFC terminal receives a non-contact card swiping command, and the non-contact card swiping command carries the application identification of the card swiping application.

Step 102, the CLF module determines the security module ID corresponding to the application ID carried in the contactless card swiping command according to the stored correspondence between the security module ID and the application ID.

In this step 102, the saved security module identifier is the identifier of the security module connected to the CLF module built in the NFC terminal.

Step 103, the CLF module sends the received contactless card swiping command to the security module corresponding to the determined security module identifier for processing.

So far, the implementation process of the contactless card swiping application is over.

According to the above process, the CLF module is connected to each security module built in the NFC terminal, and can route the non-contact card swiping command to the corresponding security module for processing according to the corresponding relationship between the stored security module and the application identification, avoiding the There is a problem of card swiping failure caused by a mismatch between the effectively connected security module and the security module supported by the contactless card swiping application, thereby improving the success rate of the contactless card swiping application.

The NFC terminal involved in Embodiment 1 of the present invention includes a CLF module and at least one security module, and the CLF module is connected to the antenna adapter, CPU (central processing unit) and each security module respectively. In practical applications, the structure diagram of the NFC terminal As shown in Figure 2, the CLF module is connected to various security modules included in the NFC (note: the figure schematically shows that the CLF module is connected to SD, SE and SIM cards, and the NFC terminal can choose to connect with the CLF module according to actual needs. type and number of connected security modules). Each security module can communicate with the CPU through the CLF module, and the CPU can write the acquired application into the security module corresponding to the application through the CLF module, and the CLF module can convert the format of the application data as required. Preferably, various security modules can also be directly connected to the CPU of the NFC terminal, and the CPU can obtain the application and write the obtained application into the security module connected to it and corresponding to the application, so that it does not need to be converted by the CLF module.

In the above technical solution provided by Embodiment 1 of the present invention, the corresponding relationship between the security module identifier and the application identifier is stored in the CLF module. Specifically, the corresponding relationship can be saved after the CPU writes the application into the security module. The stored security module identifier The process of the corresponding relationship with the application identifier is shown in Figure 3, and mainly includes the following steps:

Step 301, after the CPU acquires the application data of the application, it determines the security module corresponding to the application.

In step 301, the security module corresponding to the application can be specified by the provider of the application, or can be specified by the user, and the same application can be written into multiple security modules.

Step 302, the CPU writes the application into the determined security module corresponding to the application according to the connection mode with each security module.

In this step 302, the connection mode between the CPU and each security module can be directly connected to the security module or connected to the security module through the CLF module. If it is directly connected to the security module, the application data is written directly to the application If the corresponding security module is connected to the security module through the CLF module, the application data is written into the security module corresponding to the application through the CLF module. Moreover, if there are multiple determined security modules corresponding to the application, the application needs to be respectively written into the multiple security modules.

Step 303: Save the correspondence between the application ID of the application and the security module ID of the security module in which the application is written.

This step 302 may also be performed after the security module corresponding to the application is determined in step 301, that is, the corresponding relationship between the application ID of the application and the determined security module ID of the security module corresponding to the application is saved.

So far, the process of saving the corresponding relationship between the security module ID and the application ID ends.

Through the process corresponding to Figure 3, the corresponding relationship between the security module identifier and the application identifier can be saved in the CLF module (the corresponding relationship can be called a routing table). Specifically, when the CLF module saves the corresponding relationship between the security module identifier and the application identifier, it can be as The form of the list is shown in Table 1 below:

Table 1

Application ID Security Module Identification 0xD1560001018003800000000100000001 SE 0xD1560001018003800000000100000002 SIM 0xD1560001018003800000000200000003 SD

According to the corresponding relationship of the application logo and security module identification above, the application identifier is "0xd1560001018003800000000000001" corresponding to the security module SE. The application logo is "0xd156000101800380000000000000002", and the application logo is "0xd15600010180000000000003" "" Corresponds to the security module SD.

Embodiment 1 of the present invention further provides a specific implementation process of step 103 included in the corresponding flow in FIG. 1, that is, the specific process in which the CLF module sends the received contactless card swiping command to the security module corresponding to the determined security module identifier for processing, The process includes:

When the security module identification corresponding to the application identification carried in the non-contact card swiping command determined in step 102 is one, the non-contact card swiping command is directly sent to the security module corresponding to the determined security module identification for processing;

When it is determined in step 102 that there are more than two security module identifications corresponding to the application identification carried in the contactless card swiping command, the contactless card swiping command is sent to the security module with the highest priority among the determined security module identifications Identify the corresponding security module for processing. Wherein, the priority of the security module ID can be specified by the application provider in advance, or can be specified by the user, and the priority information of the security module ID can be saved together with the corresponding relationship between the security module ID and the application ID, for example, the corresponding The security module ID with the highest priority is set as the default. When the same application ID corresponds to multiple security module IDs, the security module corresponding to the security module ID that is set as the default is selected as the security module ID that processes the application corresponding to the application ID. , generally, only one of the multiple security module IDs corresponding to the same application ID is set as the default, and the application IDs on the same security module are not allowed to be repeated. For example, the electronic wallet application (the application AID is 0xD1560001018003800000000100000000) is preset on the SE and the SIM card, and the electronic wallet application on the SE is the default application, as shown in Table 2 below:

Table 2

Application ID Security Module Identification Whether to apply by default 0xD1560001018003800000000100000000 SE yes 0xD1560001018003800000000100000000 SIM card no

According to the corresponding relationship saved in Table 1 above, the e-wallet application whose application ID is "0xD1560001018003800000000100000000" can be in the security module SE and the security module SIM card at the same time, but it is only set as the default on the security module SE. Therefore, subsequent applications have When the electronic wallet applies a card swiping command, the command will be routed to the SE for processing, unless the connection channel between the CLF module and the SE is closed.

In the above process corresponding to Figure 1 provided by Embodiment 1 of the present invention, if the determination result of the above step 102 is: the CLF module has not determined the security module identification corresponding to the application identification carried in the contactless card swiping command according to the stored correspondence , in order to improve the success rate of contactless card swiping, the CLF module can further determine the security module for processing the contactless card swiping command through broadcasting. This process is specifically shown in Figure 4 and mainly includes the following steps:

Step 401, the CLF module broadcasts the non-contact card swiping command to each security module built in the NFC terminal connected to it.

In step 401, the CLF module may send the non-contact card swiping command to all security modules connected to it, in order to determine the security module capable of processing the card swiping application.

In step 402, the CLF module receives the information fed back by the security module for identifying the application that supports the application identifier carried in the contactless card swiping command.

In this step 402, after receiving the non-contact card swiping command sent by the CLF module, the security module obtains the application identification in the non-contact card swiping command, and if the security module determines that it supports the application corresponding to the application identification, it will feed back the application to the CLF module. It is used to identify the information that supports the application. If it is not supported, no feedback is required. The format of the information sent by the security module to identify the application that supports the application identification can be predetermined. For example, in order to reduce the amount of information transmission, "1" can be set to indicate support, and "0" can be set to indicate no support. In actual applications, you can The format of the information can be determined flexibly, and will not be listed one by one here.

Step 403 , the CLF module instructs one of the security modules that have fed back the application identification carried in the contactless card swiping command to process the contactless card swiping command.

In this step 403, if it is fed back that there are multiple security modules that support the application identification carried in the contactless card swiping command, the CLF module can select a security module to respond to the contactless card swiping command according to preset rules. to process.

So far, the process of determining the security module processing the non-contact card swiping command by means of broadcasting ends.

Through the process corresponding to Figure 4, even if the security module identification corresponding to the application identification carried in the contactless card swiping command is not determined according to the corresponding relationship saved by the CLF module, the CLF module can also determine that the contactless card swiping command can A security module for processing commands, thus ensuring the success rate of non-contact card swiping applications.

Further, if the corresponding security module identification corresponding to the application identification carried in the contactless card swiping command is not determined according to the corresponding relationship saved by the CLF module, it means that the CLF module does not save the corresponding relationship between the application identification and the security module identification. In this case, the CLF module can further update the corresponding relationship between the stored application ID and the security module ID according to the determination result of the security module that can process the contactless card swiping command determined in this broadcast. Specifically, in the above After step 402, that is, after the CLF module receives the information fed back by the security module for identifying the application corresponding to the application identification carried in the command that supports the contactless card swiping, the CLF module can separately save and feed back the information used to identify the application that supports the contactless card swiping command. The corresponding relationship between the security module identification of the security module of the application identification carried in the command and the application identification carried in the non-contact card swiping command, so that when there is a subsequent non-contact card swiping command including the application identification, it can be directly based on the saved The corresponding relationship determines the security module that processes the non-contact card swiping command, thereby improving the card swiping efficiency.

In the implementation method of the non-contact card swiping application provided by Embodiment 1 of the present invention, in order to improve the control of the NFC terminal, the connection status between the CLF module and each security module in the NFC terminal can also be controlled. Figure 5 shows a schematic diagram of the connection state between the CLF module and the security module in the NFC terminal, as shown in Figure 5, the CLF module includes a controller, the controller is used to receive the control CLF module and the security module sent by the security module included in the security device Set the command to open or close the connection channel of the security module. In practical applications, a switch can be set on the connection channel between the CLF module and each security module. If the controller receives a command to control the opening of the connection channel between the CLF module and the set security module, it can turn off the switch. At this time, the connection channel is valid. Communication is possible; if the connection channel between the control CLF module and the setting security module is closed, the switch can be turned on. At this time, the connection channel is invalid and communication cannot be performed. It should be understood that the method of controlling the connection channel between the CLF module and the security module described here is only one implementation of the present invention. In practical applications, there may be various control methods, such as setting the effective bit of the connection channel Wait, I won't list them one by one here. Moreover, in practical applications, the security device shown in Figure 5 can be provided by the application provider or the NFC terminal operator, that is, the security device is independent of the NFC terminal, and is used by the application provider or the NFC terminal operator to manage the application , the security device can also be built into the NFC terminal and controlled by the user, so that the user can manage and control the NFC terminal itself.

Fig. 6 shows the schematic flow chart of the information that the CLF module saves the information used to identify the state of the connection channel between the CLF module and the security module as open or closed. As shown in Fig. 6, the process mainly includes the following steps:

Step 601, the CLF module receives instruction information indicating to open or close the connection channel with the set security module, and the instruction information carries the security module identifier of the set security module.

In this step 601, the indication information may be sent by a security module of the security device shown in FIG. 5 .

Step 602, the CLF module verifies the sender of the indication information, and after the verification is passed, controls the connection channel of the security module corresponding to the security module identifier carried in the indication information to be opened or closed according to the indication information.

Step 603, the CLF module saves the information used to identify whether the state of the connection channel between the CLF module and the security module is open or closed.

So far, the process for the CLF module to save the information used to identify the state of the connection channel between the CLF module and the security module as being open or closed ends.

In the above step 602 included in the process corresponding to Figure 6, the CLF module can verify the sender of the indication information based on a verification mechanism such as a symmetric key mechanism or an asymmetric key mechanism. The verification process is described in detail.

1. Verify the sender of the indication information based on the symmetric key mechanism

Figure 7 shows a schematic flow diagram of verifying the sender of the indication information based on the symmetric key mechanism. Specifically, the CLF module is preset in the CLF module and the subkey KEYSUB, and the root key is stored in the security module of the security device. KEYROOT. As shown in Figure 7, the verification process mainly includes:

Step 1, the security module sends an order (GetID command) to obtain the identification of the CLF module to the CLF module;

Step 2. The CLF module generates a random number RAND1;

Step 3, the CLF module returns a response message (Response) to the security module, which carries the generated RAND1 and the identifier of the CLF module in the response message;

Step 4. The security module generates RAND2, uses KEYROOT to encrypt the identity of the CLF module to generate KEYSUB, uses KEYSUB to encrypt RAND1||RAND2 to generate a session key KEYSession, and uses KEYSession to open or close the connection channel (Open/CloseChannel) command The body is processed to generate MAC1;

Step 5, the security module sends the Open/CloseChannel command to the CLF module, and the command summary includes: security module identification (ChannelID), RAND2, MAC1 and other information to indicate opening or closing of a certain CLF module and the corresponding security module of the ChannelID connection channel;

Step 6. After receiving the Open/CloseChannel command, the CLF module uses KEYSUB to encrypt RAND1||RAND2 to generate a session key KEYSession, uses KEYSession to process the body of the Open/CloseChannel command to generate MAC2, and then compares MAC1 and MAC2. If MAC2 is equal, the specified connection channel between the CLF module and the security module is opened or closed according to the instruction, otherwise an error message is returned;

Step 7: The CLF module returns an execution response message (Response) to the security module.

So far, the process of verifying the sender of the indication information based on the symmetric key mechanism ends.

2. Verify the sender of the indication information based on the asymmetric key mechanism

Figure 8 shows a schematic flow diagram of verifying the sender of the indication information based on the asymmetric key mechanism. Specifically, the issuer certificate (including the issuer's public key) or the issuer's public key KEYPUB, CLF module is preset in the CLF module The identity of the issuer's private key KEYPRIVATE is stored in the security module. As shown in Figure 8, the verification process mainly includes the following steps:

Step 1, the security module sends an order (GetID command) to obtain the identification of the CLF module to the CLF module;

Step 2. The CLF module generates a random number RAND1;

Step 3, the CLF module returns a response message (Response) to the security module, which carries the generated RAND1 and the identification ID of the CLF module in the response message;

Step 4, the security module generates RAND2, uses KEYPRIVATE to encrypt the hash value of the connection channel opening or closing (Open/CloseChannel) command body to generate signature MAC1;

Step 5. The security device sends an Open/CloseChannel command to the CLF module, which includes security module identification (ChannelID), RAND1, RAND2, MAC1 and other information to open/close the connection channel between a certain CLF module and the security module corresponding to the ChannelID ;

Step 6. After receiving the Open/CloseChannel command, the CLF module uses KEYPUB to decrypt MAC1, calculates the hash value of the command body, and compares it with the decrypted result. If the two are equal, open/close the communication between the CLF module and the security module according to the command. Specify the connection channel, otherwise return an error message;

Step 7: The CLF module returns an execution response message (Response) to the security device.

So far, the process of verifying the sender of the indication information based on the asymmetric key mechanism ends.

According to the above process, the opening or closing of the connection channel between the CLF module and the security module can be flexibly controlled, thereby improving the management efficiency of the security module and the card swiping application.

Based on the above processing process, the CLF module saves the information used to identify the state of the connection channel between the CLF module and the security module as open or closed. The closed information can be stored together with the corresponding relationship between the security module identifier and the application identifier, for example, as shown in Table 3 below:

table 3

Application ID Security Module Identification connection channel status 0xD1560001018003800000000100000001 SE turn on 0xD1560001018003800000000100000002 SIM turn on 0xD1560001018003800000000200000003 SD closure

According to the content saved in Table 3, it can be seen that the connection channel between the CLF module and the security module SE and the security module SIM card is open, that is, available, and the connection channel between the CLF module and the security module SD is closed, that is, unavailable.

According to the above process, if the link between the CLF module and a certain security module is closed, the "connection channel state" flag of the entry related to the security module is set to "Off", if a certain (or some) applications on the security module are the default applications, the user needs to select the default application from the remaining entries in the command routing table, if there is no entry that meets the conditions, it will not be executed the step. If the link between the CLF module and a security module is opened, the "connection channel status" flag of the entry related to the security module in the command routing table is set to "open", if one of these entries (or If there is no default application in the command routing table for certain) application identifiers, the user needs to select a default application, and if there is no table entry that meets the conditions, this step will not be performed.

In order to ensure that the security module can successfully process the non-contact card swiping command, before executing step 103 included in the corresponding process in Figure 1, that is, the CLF module sends the non-contact card swiping command to the security module corresponding to the determined security module identification for processing Before, the following process was further performed:

According to the saved information for identifying the connection channel state between the CLF module and the security module as open or closed, select the security module whose connection channel state is open from the security modules corresponding to the determined security module identification;

Then, correspondingly, when the above-mentioned step 103 is executed, that is, the CLF module sends the non-contact card swiping command to the security module corresponding to the determined security module identification for processing, specifically, the non-contact card swiping command is sent to the selected The connection channel is processed by the security module whose status is open.

The above-mentioned technical solution provided by the embodiment of the present invention can also support the dynamic installation and deletion of card swiping applications, namely:

If the application is dynamically installed in the security module, after the application is successfully installed, the information of the application needs to be added to the command routing table. Decide whether to set newly installed apps as default apps;

If the application is dynamically deleted in the security module, after the application is successfully deleted, the information of the application needs to be deleted from the command routing table. If the application is the default application, the user needs to select the Do not apply. If there is no entry that meets the conditions, this step will not be performed.

Embodiment two

Embodiment 2 of the present invention provides a specific implementation process of the non-contact card swiping application provided in Embodiment 1 above.

Figure 9 shows a schematic diagram of the application scenario of the contactless card swiping application. Can communicate with APDU (ApplicationProtocolDataUnit, application protocol data unit) command.

Figure 10 shows a schematic flow diagram of implementing a non-contact card swiping application based on the scenario shown in Figure 9, as shown in Figure 10, mainly including the following steps:

Step 1001, the non-contact POS machine/reader sends an application selection command to the NFC terminal, and the command includes the application identification (AID) of the application;

Step 1002, after the CLF module receives the application selection command, it searches in the command routing table (that is, the stored correspondence between the application identification and the security module identification) according to the AID contained therein;

Step 1003, the CLF module judges whether to find an entry matching the AID (i.e. the security module identification corresponding to the AID), if finding a matching entry, proceed to step 1004; if not finding a matching entry, Skip to step 1006;

Step 1004, if the entry matching the AID is found, the CLF module judges whether the entry is a default application, if so, skip to step 1009; if the entry found is not a default application, then execute step 1005;

Step 1005, the CLF module continues to search in the command routing table, and returns to step 1003;

Step 1006, the CLF module forwards the application selection command to all security modules whose connection channels are open;

Step 1007, the CLF module judges whether to receive a correct response (that is, whether to receive the message fed back by the security module to identify the application that supports the AID); ), the CLF module returns an application not found response to the non-contact POS machine/reading head, and the process ends; otherwise, continue to execute step 1008;

Step 1008, if a certain (or some) security modules in the open state return a correct response, the CLF module lists all applications that meet the conditions, and the user selects a default application, and the CLF module adds all application information to the command routing table, And set the default application;

Step 1009, the CLF module selects a default application from the command routing table;

Step 1010, the CLF module routes subsequent commands to the application until the transaction ends or a new application selection command is received.

At this point, the process ends.

Embodiment Three

Corresponding to the procedures given in the first and second embodiments above, the third embodiment of the present invention provides a device for implementing a non-contact card swiping application, as shown in FIG. 11 , the device includes:

A receiving unit 1101, a first saving unit 1102, a security module identifier determining unit 1103, and a command distributing unit 1104;

in:

The receiving unit 1101 is configured to receive a non-contact card swiping command, and the non-contact card swiping command carries the application identification of the card swiping application;

The first saving unit 1102 is used to save the corresponding relationship between the security module identification and the application identification of the security module connected to the non-contact front-end CLF module built in the short-range wireless communication NFC terminal;

A security module identification determination unit 1103, configured to determine the security module identification corresponding to the application identification carried in the non-contact card swiping command according to the correspondence stored by the first storage unit 1102;

The command distribution unit 1104 is configured to send the contactless card swiping command received by the receiving unit 1101 to the security module corresponding to the security module identification determined by the security module identification determination unit 1103 for processing.

In a preferred implementation provided by Embodiment 3 of the present invention, the command distribution unit 1104 included in the device shown in FIG. 11 is specifically used to directly send the non-contact card swiping command to the determined The security module corresponding to the security module identification performs processing; when the determined security module identification is more than two, the non-contact card swiping command is sent to the security module corresponding to the security module identification with the highest priority among the determined security module identifications for processing .

In a preferred implementation mode provided by Embodiment 3 of the present invention, the command allocation unit 1101 included in the device shown in FIG. When the security module identification corresponding to the application identification is applied, the non-contact card swiping command is broadcast to each security module connected to the CLF module built in the NFC terminal, and the instruction feedback is used to identify and support the application identification carried in the contactless card swiping command. In the security module A security module handles the contactless swipe commands.

In a preferred implementation provided by Embodiment 3 of the present invention, the first storage unit 1102 included in the device shown in FIG. 11 is also used to broadcast the non-contact swiping card to each security module connected to the CLF module built in the NFC terminal at the command distribution unit After the command, the corresponding relationship between the security module identification used to identify the security module supporting the application identification carried in the contactless card swiping command and the application identification carried in the contactless card swiping command is saved and fed back.

As shown in Figure 12, in a preferred implementation mode provided by Embodiment 3 of the present invention, the device shown in Figure 11 may further include:

The second storage unit 1105 is used to store the information used to identify the state of the connection channel between the CLF module and the security module as open or closed;

Correspondingly, the security module selection unit 1103 is configured to, before the command distribution unit 1104 sends the non-contact card swiping command to the security module corresponding to the determined security module identifier for processing, according to the second storage unit 1105 stored for identifying the CLF The information that the state of the connection channel between the module and the security module is open or closed, and the security module whose connection channel state is open is selected from the security modules corresponding to the determined security module identification;

The command distributing unit 1104 is specifically configured to send the non-contact card swiping command to the security module whose connection channel status is selected to be opened for processing.

In a preferred implementation manner provided by Embodiment 3 of the present invention, the second storage unit 1105 included in the device shown in FIG. 12 is specifically used to receive instruction information indicating to open or close the connection channel with the set security module, and the instruction information carries Set the security module identification of the security module; and after passing the verification of the sender of the instruction information, control the connection channel of the security module corresponding to the security module identification carried in the instruction information to open or close according to the instruction information, and save the information used to identify the CLF The status of the connection channel between the module and the security module is open or closed.

It should be understood that the units included in the device for implementing the contactless card swiping application are only logically divided according to the functions realized by the terminal. In practical applications, the above units can be superimposed or split. And the functions realized by the device for realizing the non-contact card swiping application provided by this embodiment correspond to the flow of the method for realizing the non-contact card swiping application provided by the above embodiment one by one. The method has been described in detail in the embodiments, and will not be described in detail here.

Moreover, the implementation device for the contactless card swiping application in the third embodiment also has functional modules capable of implementing the solutions of the first and second embodiments, which will not be repeated here.

Through at least one of the above-mentioned technical solutions provided by the embodiments of the present invention, the CLF module in the NFC terminal receives a contactless card swiping command, which carries the application identification of the card swiping application in the non-contact card swiping command. The corresponding relationship between the security module identification and the application identification of the security module, determine the security module identification corresponding to the application identification carried in the non-contact card swiping command, and send the non-contact card swiping command to the security module corresponding to the determined security module identification to process. According to this technical solution, the CLF module is connected to each security module built in the NFC terminal, and can route the non-contact card swiping command to the corresponding security module for processing according to the corresponding relationship between the stored security module and the application identification, avoiding the The module has the problem of card swiping failure caused by the mismatch between the effectively connected security module and the security module supported by the contactless card swiping application, thereby improving the success rate of the contactless card swiping application.

While preferred embodiments of the present application have been described, additional changes and modifications to these embodiments can be made by those skilled in the art once the basic inventive concept is appreciated. Therefore, the appended claims are intended to be construed to cover the preferred embodiment and all changes and modifications which fall within the scope of the application.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (10)

1. A method for implementing a contactless card swiping application, comprising: The non-contact front-end CLF module in the short-range wireless communication NFC terminal receives a non-contact card swiping command, and the non-contact card swiping command carries the application identification of the card swiping application; According to the stored corresponding relationship between the security module identification and the application identification of the security module connected to the CLF module built in the NFC terminal, determine the security module identification corresponding to the application identification carried in the non-contact card swiping command; Sending the non-contact card swiping command to the security module corresponding to the determined security module identifier for processing; If the security module identifier corresponding to the application identifier carried in the contactless card swiping command is not determined according to the stored correspondence, the method further includes: Broadcast the non-contact card swiping command to each security module connected to the CLF module built in the NFC terminal; And instructing one of the security modules that have fed back the security modules used to identify and support the application identifier carried in the contactless card swiping command to process the contactless card swiping command. 2. The method according to claim 1, characterized in that, sending the non-contact card swiping command to the security module corresponding to the identified security module identifier for processing comprises: When the determined security module identification is one, directly send the non-contact card swiping command to the security module corresponding to the determined security module identification for processing; When more than two security module identifiers are determined, the contactless card swiping command is sent to the security module corresponding to the security module identifier with the highest priority among the determined security module identifiers for processing. 3. The method according to claim 1, wherein, after broadcasting the non-contact card swiping command to each security module connected to the CLF module built into the NFC terminal, further comprising: The corresponding relationship between the security module identifier used to identify the security module supporting the application identifier carried in the contactless card swiping command and the application identifier carried in the contactless card swiping command is saved and fed back respectively. 4. The method according to claim 1, wherein before sending the non-contact card swiping command to the security module corresponding to the identified security module identifier for processing, further comprising: According to the saved information for identifying the connection channel state between the CLF module and the security module as open or closed, select the security module whose connection channel state is open from the security modules corresponding to the determined security module identification; Sending the non-contact card swiping command to the security module corresponding to the determined security module identification for processing, including: The non-contact card swiping command is sent to the selected security module whose connection channel is open for processing. 5. The method according to claim 4, wherein the mode of storing information for identifying the state of the connection channel between the CLF module and the security module as opening or closing includes: receiving instruction information indicating to open or close the connection channel with the set security module, the instruction information carrying the security module identification of the set security module; After passing the verification of the sender of the indication information, control the opening or closing of the connection channel of the security module corresponding to the security module identifier carried in the indication information according to the indication information, and save the information used to identify the CLF Information about whether the status of the connection channel between the module and the security module is on or off. 6. A device for realizing a contactless card swiping application, characterized in that it comprises: A receiving unit, configured to receive a non-contact card swiping command, wherein the non-contact card swiping command carries an application identification of a card swiping application; The first storage unit is used to store the corresponding relationship between the security module identification and the application identification of the security module connected to the non-contact front-end CLF module built in the short-range wireless communication NFC terminal; A security module identification determination unit, configured to determine the security module identification corresponding to the application identification carried in the contactless card swiping command according to the correspondence stored by the first storage unit; A command distribution unit, configured to send the contactless card swiping command received by the receiving unit to the security module corresponding to the security module identification determined by the security module identification determination unit for processing; The command assigning unit is further configured to send to the Each security module connected to the CLF module built in the NFC terminal broadcasts the contactless card swiping command, and indicates that one of the security modules used to identify and support the application identification carried in the contactless card swiping command is fed back. The module processes the non-contact card swiping command. 7. The device according to claim 6, wherein the command distribution unit is specifically configured to directly send the non-contact card swiping command to the determined security module when the identified security module is identified as one. The security module corresponding to the security module identification is processed; when the determined security module identification is more than two, the non-contact card swiping command is sent to the security module with the highest priority among the determined security module identifications. The module identifies the corresponding security module for processing. 8. The device according to claim 6, wherein the first storage unit is also used to broadcast the command distribution unit to each security module connected to the CLF module built in the NFC terminal. After the non-contact card swiping command, save and feed back the security module identification of the security module that supports the application identification carried in the non-contact card swiping command and the information of the application identification carried in the non-contact card swiping command respectively. Correspondence. 9. The apparatus of claim 6, further comprising: The second storage unit is used to store the information used to identify the state of the connection channel between the CLF module and the security module as open or closed; The security module selection unit is configured to, before the command allocation unit sends the non-contact card swiping command to the security module corresponding to the determined security module identifier for processing, according to the information stored by the second storage unit for Identify the information that the state of the connection channel between the CLF module and the security module is open or closed, and select the security module whose connection channel state is open from the security modules corresponding to the determined security module identification; The command distributing unit is specifically configured to send the non-contact card swiping command to the security module whose connection channel status is selected to be opened for processing. 10. The device according to claim 9, wherein the second storage unit is specifically configured to receive instruction information indicating to open or close the connection channel with the set security module, and the instruction information carries the Set the security module identification of the security module; and after the sender of the instruction information is verified, according to the instruction information, control the connection channel of the security module corresponding to the security module identification carried in the instruction information to open or close, and save the information used to identify the state of the connection channel between the CLF module and the security module as open or closed.