Authorization binding method based on a sticker card cloud SDK system

Abstract

The application discloses an authorization binding method based on a film card cloud SDK system, and comprises the following steps: verifying whether an authorization binding operation has been performed; in a data transparent transmission process, the film card cloud SDK randomly generates an authorization code, and attaches the authorization code to a data message; then, the film card cloud SDK backend server forwards the data message to the film card after encryption and signature; the film card calls a film card authorization binding module according to the authorization code; the film card authorization binding module compares the authorization code input by a user of a terminal device to which the film card belongs with the authorization code parsed from the message; if the authorization codes are inconsistent, the authorization fails; if the authorization codes are consistent, the film card authorization binding module uses temporary UUID data to replace formal UUID data, and the authorization binding succeeds. The method avoids the security risk that a user of a mobile terminal is interacted with the film card of the terminal by others without awareness.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to an authorization binding method of a sticker card cloud SDK (Software Development Kit) system. BACKGROUND

[0002] The sticker card, as a hardware carrier, is used in combination with a terminal application program to provide a shield-like function for the application program, and this function has been widely used in many mobile bank application systems. In order to solve the problem of accessing the sticker card by the application on the terminal with limitations, the applicant designed and applied for an invention patent "Cloud SDK system of sticker card and operation method thereof" with application number CN202010895318.6. As shown in Figure 1 The cloud SDK system of the sticker card includes a terminal device, a sticker card and an SDK background system. The SDK background system includes a user database management module 11, a key management module 12 and a sticker card cloud SDK background server 13. The terminal device includes a BIP channel management module 21, a BIP data transceiver module 22 and a sticker card cloud SDK 23. The sticker card includes an event management module 31 and a sticker card data transceiver module 32. Through the cloud SDK system of the sticker card, the mobile phone systems that do not support direct interaction between the mobile phone OS and the sticker card can communicate with the sticker card through the cloud SDK system, thereby solving the problem that the sticker card cannot be used as a hardware SE to protect the user transaction and identity authentication process of the mobile terminal.

[0003] However, the running mechanism of the cloud SDK system determines that the communication between the SDK and the sticker card is not a direct contact type transmission, but needs to be forwarded through the sticker card cloud SDK background server. Therefore, when the SDK and the sticker card are not running on the same mobile terminal at the same time, they can still communicate. For example, the sticker card is installed on mobile terminal A, and the cloud SDK is installed on mobile terminal B. As long as the SDK on mobile terminal B can get the card number of the sticker card on terminal A, the SDK on terminal B can interact with the sticker card on terminal A through the sticker card cloud SDK background server. That is, the user of mobile terminal B can initiate the sticker card of terminal A without the user of terminal A being aware, which has a certain security risk. SUMMARY

[0004] The purpose of the present application is to provide an authorization binding method based on the sticker card cloud SDK system, which avoids the security risk that the user of the mobile terminal to which the sticker card belongs is initiated by others without being aware of the sticker card of the terminal.

[0005] The technical solution to achieve the above purpose is:

[0006] An authorization binding method based on a sticker card cloud SDK system, the sticker card cloud SDK system comprising a terminal device, a sticker card and an SDK background system, the SDK background system comprising: a user database management module, a key management module, a sticker card cloud SDK background server; the terminal device comprising: a BIP channel management module, a BIP data transceiving module, a sticker card cloud SDK; the sticker card comprising: an event management module and a sticker card data transceiving module, an interaction process of the terminal device, the sticker card and the sticker card cloud SDK background server comprising: BIP channel binding, session key negotiation, data transparent transmission, the authorization binding method comprising:

[0007] Step one, verifying whether the authorization binding operation has been performed, if yes, performing normal transaction and authentication operation, if no, performing next step;

[0008] Step two, in the data transparent transmission process, the sticker card cloud SDK randomly generates an authorization code and attaches the authorization code to the data message, and then forwards the data message to the sticker card through the sticker card cloud SDK background server after encryption and signature according to the data transparent transmission process;

[0009] Step three, the sticker card decrypts and verifies the signature of the transparent transmission message, takes out the data message, and calls the sticker card authorization binding module;

[0010] Step four, the sticker card authorization binding module compares whether the authorization code input by the user of the terminal device to which the sticker card belongs is consistent with the authorization code parsed from the message; if the authorization codes are inconsistent, the authorization fails, and an error code is returned to the sticker card cloud SDK background server and then transmitted to the terminal application of the terminal device; if the authorization codes are consistent, the sticker card authorization binding module uses the temporary UUID data to cover the formal UUID data, and the authorization binding succeeds.

[0011] Preferably, the step one comprises:

[0012] An authorization code generation module is set in the sticker card cloud SDK, an STK application module is set in the terminal device to which the sticker card belongs, and a sticker card authorization binding module is set in the sticker card; the sticker card authorization binding module maintains a formal UUID data, a MESN data and a temporary UUID data; the sticker card cloud SDK locally maintains a UUID data and a MESN data;

[0013] When the terminal application initiates a BIP channel binding operation to the sticker card cloud SDK background server, the UUID data generated by the sticker card cloud SDK is transmitted simultaneously; when the sticker card cloud SDK background server negotiates a session key with the sticker card, the UUID data transmitted by the sticker card cloud SDK is transmitted simultaneously; after the sticker card receives the UUID data transmitted by the sticker card cloud SDK background server, the UUID data is used to cover the temporary UUID data in the sticker card.

[0014] The sticker card returns the generated session key, and returns "MESN + formal UUID data" to the sticker card cloud SDK background server at the same time; the sticker card cloud SDK background server returns the received session key + MESN + UUID data to the sticker card cloud SDK of the terminal device;

[0015] The sticker card cloud SDK compares the received MESN data with the locally maintained MESN data, and also compares the received UUID data with the locally maintained UUID data. If they are consistent, the authorization binding operation has been authorized. If they are inconsistent, the next step is performed.

[0016] Preferably, in the data transparent transmission process in step two, the sticker card cloud SDK generates an authorization code randomly, and displays it to the user through the interface of the terminal application, and prompts the user to perform the authorization binding operation for the first use of the device; the user confirms, and the sticker card cloud SDK attaches the authorization code to the data message.

[0017] Preferably, in step four, the sticker card authorization binding module invokes the STK application module in the terminal device to which the sticker card belongs through the STK instruction, the STK application module displays an input box according to the STK instruction, and prompts the user to input the authorization code; the user inputs the authorization code, and the STK application module returns the authorization code input by the user to the sticker card authorization binding module.

[0018] Preferably, the sticker card is inserted into the mobile phone, and the IMEI is obtained after starting, and then the MESN is calculated, and the MESN data is used to overwrite the locally stored MESN data.

[0019] Preferably, the UUID in the sticker card cloud SDK is generated by calling the terminal device interface when the sticker card cloud SDK is used for the first time, and the UUID generated for the first time is always used in subsequent use, and the MESN is initially empty by default.

[0020] An authorization binding method based on a sticker card cloud SDK system, the sticker card cloud SDK system comprising a terminal device, a sticker card and an SDK background system, the SDK background system comprising: a user database management module, a key management module, a sticker card cloud SDK background server; the terminal device comprising: a BIP channel management module, a BIP data transceiver module, a sticker card cloud SDK; the sticker card cloud SDK comprising a sticker card authorization binding module, the sticker card comprising: an event management module and a sticker card data transceiver module, and the interaction process of the terminal device, the sticker card and the sticker card cloud SDK background server comprising: BIP channel binding, session key negotiation, data transparent transmission, and the authorization binding method comprising:

[0021] Step one, verify whether the binding operation has been authorized, if yes, proceed with normal transaction and authentication operation, if not, proceed to the next step;

[0022] Step two, in the data transparent transmission process, the sticker card randomly generates an authorization code and attaches the authorization code to the data message, and then encrypts and signs the data according to the data transparent transmission process and forwards it to the sticker card cloud SDK background server through the sticker card cloud SDK;

[0023] Step three, the sticker card cloud SDK decrypts and signs the transparent transmission message, extracts the data message, and calls the sticker card authorization binding module;

[0024] Step four, the sticker card authorization binding module compares the authorization code input by the user of the terminal device to which the sticker card cloud SDK belongs with the authorization code parsed from the message; if the authorization codes are inconsistent, the authorization fails, and an error code is returned to the sticker card cloud SDK background server and then transmitted to the terminal device to which the sticker card belongs; if the authorization codes are consistent, the sticker card authorization binding module uses the temporary UUID data to overwrite the formal UUID data, and the authorization binding is successful.

[0025] Preferably, in step two, in the data transparent transmission process, the sticker card randomly generates an authorization code and pops up an interface to display it to the user, and prompts the user that the first use of the device requires authorization binding operation; the user confirms, and the sticker card attaches the authorization code to the data message.

[0026] Preferably, in step four, the sticker card cloud SDK displays an input box and prompts the user to input the authorization code; the user inputs the authorization code, and the sticker card cloud SDK returns the authorization code input by the user to the sticker card authorization binding module.

[0027] The beneficial effects of the present application are: the present application binds the terminal application, the terminal device to which the sticker card belongs, and the sticker card itself, avoiding the security risks of the user of the mobile terminal being interacted with the sticker card of the terminal by others without any awareness. BRIEF DESCRIPTION OF DRAWINGS

[0028] Figure 1 is a structure diagram of the sticker card cloud SDK system;

[0029] Figure 2 is a structure diagram of the sticker card cloud SDK system in the present application;

[0030] Figure 3 is a flowchart of the authorization binding method based on the sticker card cloud SDK system of the present application; DETAILED DESCRIPTION

[0031] The present application will be further described below with reference to the accompanying drawings.

[0032] Referring to Figure 1 , the existing sticker card cloud SDK system includes a terminal device, a sticker card, and an SDK background system. The SDK background system includes: a user database management module 11, a key management module 12, and a sticker card cloud SDK background server 13. The terminal device includes: a BIP (BIP, independent (data transmission) protocol) channel management module 21, a BIP data transceiver module 22, and a sticker card cloud SDK 23. The sticker card includes: an event management module 31 and a sticker card data transceiver module 32.

[0033] The user database management module 11 is used to manage the mobile phone number of the user and the card number of the sticker card. The key management module 12 is used to manage the session key. The sticker card cloud SDK background server 13 connects the user database management module 11 and the key management module 12.

[0034] The BIP channel management module 21 uses the BIP protocol to transmit channel management instructions between the sticker card cloud SDK background server 13. The BIP data transceiver module 22 uses the BIP protocol to transmit transaction instructions between the sticker card cloud SDK background server 13. The sticker card cloud SDK 23 is called by the terminal application, and interacts with the sticker card cloud SDK background server 13.

[0035] The event management module 31 is connected with the BIP channel management module 21, and is used to process channel management instructions. The sticker card data transceiver module 32 transmits transaction instructions with the BIP data transceiver module 22, and interacts with the sticker card application.

[0036] When the terminal application background has accessed the sticker card cloud SDK background server, the terminal application calls the sticker card cloud SDK to realize the related functions of the shield. When the sticker card cloud SDK judges that it needs to interact with the sticker card, the terminal application calls the sticker card cloud SDK, and interacts with the sticker card cloud SDK background server through the network of the terminal application background;

[0037] When the terminal application background has not accessed the sticker card cloud SDK background server, the terminal application calls the sticker card cloud SDK to realize the related functions of the shield. When the sticker card cloud SDK judges that it needs to interact with the sticker card, the terminal application calls the sticker card cloud SDK, and interacts with the sticker card cloud SDK background server through the network of the terminal application background;

[0038] Currently, the interaction process only includes BIP channel binding, session key negotiation, and data transparent transmission. In order to avoid the security risks in the background art, for the user to whom the terminal device belongs to which the film card belongs to, when a terminal device of a certain third party (including the current device to which the film card belongs) first calls the film card through the film card cloud SDK, the above user needs to know which specific terminal device and which terminal application are calling the film card on his / her device through the film card cloud SDK. At the same time, the user can make a decision on whether to authorize the above calling operation. Only when the user authorizes the above calling operation, the calling process will continue until the operation is completed, otherwise the calling process will be terminated immediately. Once the first transaction is authorized, the terminal device to which the terminal application belongs, the terminal device to which the film card belongs, and the film card itself will form a stable binding relationship. As long as the binding relationship does not change, the subsequent calling process will no longer appear the authorization binding step. Once the binding relationship changes, that is, the terminal device to which the terminal application belongs is replaced, or the terminal device to which the film card belongs is replaced (including the replacement of different card slots in the same device), or the film card is replaced. The first call after the replacement will trigger the authorization binding operation. That is, the authorization binding is added to the above interaction process.

[0039] To achieve the above purpose, the authorization binding method based on the film card cloud SDK system of the present application comprises the following steps: Figures 2-3

[0040] Step S1, setting an authorization code generation module in the film card cloud SDK, setting an STK (STK is a Sim Tool Kit, also known as a SIM card tool kit) application module in the terminal device to which the film card belongs, and setting a film card authorization binding module in the film card; the authorization code generation module is used to generate an authorization code and display it on the terminal application interface. The STK application module is used to pop up an input prompt box to let the user input the authorization code. The film card authorization binding module is used to process the authorization code binding process.

[0041] The film card authorization binding module in the film card maintains a formal UUID (Universally Unique Identifier, Universal Unique Identifier) data and a MESN (unique serial number of the terminal device, which is obtained by performing a unique mapping calculation on the IMEI (International Mobile Equipment Identity, International Mobile Equipment Identity)) data. The above two data are empty by default at the factory, and a temporary UUID is also maintained, which is empty by default at the factory;

[0042] ​The sticker card is inserted into a mobile phone, and after starting, the IMEI is acquired through the PROVIDE LOCAL INFORMATION instruction (defined in the international standard GSM11.14) to calculate the MESN, and the MESN data is used to cover the locally stored MESN data;

[0043] The sticker card cloud SDK also maintains a UUID data and a MESN data. The UUID is generated by calling the terminal device interface when the SDK is used for the first time, and the UUID data generated for the first time is always used in subsequent use. The MESN is initially empty by default;

[0044] In step S2, the terminal application initiates a BIP channel binding operation to the sticker card cloud SDK background server while transmitting the UUID data generated by the sticker card cloud SDK;

[0045] When the sticker card cloud SDK background server negotiates the session key with the sticker card, the UUID data transmitted by the sticker card cloud SDK is also transmitted;

[0046] In step S3, after receiving the UUID data transmitted by the cloud SDK background server, the sticker card uses the UUID data to cover the local temporary UUID data of the sticker card;

[0047] In step S4, when the sticker card returns the generated session key, it also returns the "MESN + formal UUID data" to the sticker card cloud SDK background server;

[0048] The sticker card cloud SDK background server returns the received session key + MESN + UUID data to the sticker card cloud SDK of the terminal device;

[0049] In step S5, the sticker card cloud SDK compares the received MESN data with the locally maintained MESN data, and also compares the received UUID data with the locally maintained UUID data. If they are consistent, it means that the authorization binding operation has been performed before, and subsequent binding is not required. The authorization binding is completed. If they are inconsistent, the next step is performed;

[0050] In step S6, in the data transparent transmission packaging process, the sticker card cloud SDK randomly generates an authorization code and displays it to the user through the interface of the terminal application, and prompts the user to perform the authorization binding operation for the first time;

[0051] The display interface has cancel and confirm buttons. If the user presses the cancel key, the calling process is terminated and the process is ended. If the user presses the confirm key, the sticker card cloud SDK attaches the authorization code to the data message, and then performs encryption and signature according to the data transparent transmission process and forwards it to the sticker card through the sticker card cloud SDK background server;

[0052] Step S7, the sticker card receives the decrypted and signed message, takes out the data message, and judges whether it has an authorization code. If it does not have an authorization code, it is processed according to the data transmission process; if it has an authorization code, the sticker card authorization binding module is called for the next operation;

[0053] Step S8, the sticker card authorization binding module calls the STK application module in the terminal device to which the sticker card belongs through the STK instruction. The STK application module displays an input box according to the instruction requirement and prompts the user to input the authorization code;

[0054] Step S9, the input interface has cancel and confirm buttons. If the user presses the cancel key, the calling process is terminated and the process is ended. If the user inputs the authorization code and presses the confirm key, the STK application module returns the authorization code input by the user to the sticker card authorization binding module;

[0055] Step S10, the authorization code binding module compares whether the authorization code input by the user is consistent with the authorization code parsed in the message. If the authorization codes are not consistent, the authorization fails, the sticker card application terminates the processing of other data messages, returns an error code to the sticker card cloud SDK background server, and then transmits it to the terminal application, and the process is ended. If the authorization codes are consistent, the sticker card authorization binding module uses the temporary UUID data to cover the formal UUID data, the authorization binding is successful, and the sticker card application module then processes the received other data messages.

[0056] In addition, the steps of the sticker card cloud SDK generating a random authorization code and displaying the authorization code through the terminal application interface, and the step of the sticker card popping up an STK input box to prompt the user to input the authorization code can be exchanged, that is, the sticker card generates a random authorization code and displays the authorization code to the user, and the terminal application sticker card cloud SDK pops up an input box to prompt the user to input. Specifically,

[0057] An authorization binding method based on a sticker card cloud SDK system, the sticker card cloud SDK system comprising a terminal device, a sticker card, and an SDK background system, the SDK background system comprising: a user database management module, a key management module, and a sticker card cloud SDK background server; the terminal device comprising: a BIP channel management module, a BIP data transceiver module, and a sticker card cloud SDK; the sticker card cloud SDK comprising a sticker card authorization binding module; the sticker card comprising: an event management module and a sticker card data transceiver module; and an interaction process of the terminal device, the sticker card, and the sticker card cloud SDK background server comprising: BIP channel binding, session key negotiation, and data transmission, the authorization binding method comprising:

[0058] Step 1, verify whether the authorization binding operation has been performed. If yes, perform normal transaction and authentication operation, if not, proceed to the next step;

[0059] Step two, in the data transparent process, the sticker card randomly generates an authorization code, and attaches the authorization code to the data message, and then encrypts and signs the data transparent process and forwards it to the sticker card cloud SDK background server through the sticker card cloud SDK;

[0060] In the data transparent process, the sticker card randomly generates an authorization code, and pops up an interface to display to the user, and prompts the user to perform authorization binding operation for the first use of the device; the user confirms that the sticker card attaches the authorization code to the data message.

[0061] Step three, the sticker card cloud SDK receives the transparent message, decrypts and verifies the signature, takes out the data message, and calls the sticker card authorization binding module;

[0062] Step four, the sticker card authorization binding module compares the authorization code input by the user of the terminal device to which the sticker card cloud SDK belongs with the authorization code parsed from the message; if the authorization codes are inconsistent, the authorization fails, and an error code is returned to the sticker card cloud SDK background server and then transmitted to the terminal device to which the sticker card belongs; if the authorization codes are consistent, the sticker card authorization binding module uses the temporary UUID data to cover the formal UUID data, and the authorization binding is successful.

[0063] The sticker card cloud SDK displays an input box, and prompts the user to input the authorization code; the user inputs the authorization code, and the sticker card cloud SDK returns the authorization code input by the user to the sticker card authorization binding module.

[0064] The above embodiments are only for illustrating the present application, and are not a limitation of the present application. Those skilled in the art can make various transformations or modifications without departing from the spirit and scope of the present application, therefore all equivalent technical solutions should belong to the scope of the present application, which should be limited by the claims.

Claims

1. An authorization binding method based on a screen protector card cloud SDK system, wherein the screen protector card cloud SDK system includes a terminal device, a screen protector card, and an SDK backend system, the SDK backend system including: User database management module, key management module, and screen protector card cloud SDK backend server; The terminal device includes: a BIP channel management module, a BIP data transceiver module, and a screen protector card cloud SDK; the screen protector card includes: an event management module and a screen protector card data transceiver module. The interaction process between the terminal device, the screen protector card, and the screen protector card cloud SDK backend server includes: BIP channel binding, session key negotiation, and data pass-through. The authorization binding method includes: Step 1: Verify whether the binding operation has been authorized. If yes, proceed with the normal transaction and authentication process. If not, proceed to the next step. Step 2: During the data pass-through process, the screen protector card cloud SDK randomly generates an authorization code and attaches the authorization code to the data packet. Then, after encryption and signing according to the data pass-through process, it is forwarded to the screen protector card through the screen protector card cloud SDK backend server. Step 3: After receiving the transparently transmitted message, the film-applying card decrypts and verifies the signature, extracts the data message, and calls the film-applying card authorization and binding module; Step 4: The screen protector card authorization binding module compares the authorization code entered by the user on the terminal device to which the screen protector card belongs with the authorization code parsed in the message. If the authorization codes do not match, the authorization fails, and an error code is returned to the screen protector card cloud SDK backend server and then forwarded to the terminal application on the terminal device. If the authorization codes match, the screen protector card authorization binding module uses temporary UUID data to overwrite the official UUID data, and the authorization binding is successful. Step one includes: Set up an authorization code generation module in the screen protector card cloud SDK, set up an STK application module in the terminal device to which the screen protector card belongs, and set up a screen protector card authorization binding module in the screen protector card; the screen protector card authorization binding module maintains a formal UUID data, a MESN data and a temporary UUID data; the screen protector card cloud SDK locally maintains a UUID data and a MESN data; When the terminal application initiates a BIP channel binding operation to the screen protector card cloud SDK backend server, it simultaneously transmits the UUID data generated by the screen protector card cloud SDK; when the screen protector card cloud SDK backend server negotiates the session key with the screen protector card, it simultaneously transmits the UUID data transmitted by the screen protector card cloud SDK; after receiving the UUID data transmitted by the cloud SDK backend server, the screen protector card uses the UUID data to overwrite the temporary UUID data on the screen protector card's local storage. When the screen protector card returns the generated session key, it also returns "MESN + official UUID data" to the screen protector card cloud SDK backend server; the screen protector card cloud SDK backend server returns the received session key + MESN + UUID data to the screen protector card cloud SDK of the terminal device; The cloud SDK for applying the screen protector compares the received MESN data with the MESN data maintained locally by the SDK, and also compares the received UUID data with the UUID data maintained locally by the SDK. If they match, the binding operation has been authorized; if they do not match, proceed to the next step. Insert the screen protector card into the phone, power it on, use the PROVIDE LOCAL INFORMATION command to obtain the IMEI, then calculate the MESN, and use this MESN data to overwrite the locally stored MESN data.

2. The authorization binding method based on the cloud SDK system for film-covered cards according to claim 1, characterized in that, In step two, during the data pass-through process, the screen protector card cloud SDK randomly generates an authorization code and displays it to the user through the terminal application interface. At the same time, the user is prompted that authorization binding is required when using the device for the first time. After the user confirms, the screen protector card cloud SDK attaches the authorization code to the data packet.

3. The authorization binding method based on the cloud SDK system for film-covered cards according to claim 1, characterized in that, In step four, the screen protector card authorization and binding module invokes the STK application module in the terminal device to which the screen protector card belongs via STK commands. The STK application module displays an input box according to the STK commands and prompts the user to enter an authorization code. After the user enters the authorization code, the STK application module returns the authorization code entered by the user to the screen protector card authorization and binding module.

4. The authorization binding method based on the cloud SDK system for film-covered cards according to claim 1, characterized in that, The UUID in the screen protector card cloud SDK is generated by calling the terminal device interface when the screen protector card cloud SDK is used for the first time. Subsequent uses will always use the UUID generated the first time. The MESN is initially empty by default.

Images