Method, Device, and System for Dynamically Binding a Smart Card

• US 20170188226A1
• Filed: 07/14/2014
• Published: 06/29/2017
• Est. Priority Date: 05/27/2014
• Status: Active Grant

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: WU, Chuanxi
• Granted Patent: US 10,356,602 B2
• Time in Patent Office: Days
• CPC Class Codes: H04W 12/084 using delegated authorisation, e.g. open authorisation [OAuth] protocol
• CPC Class Codes: H04W 12/48 using secure binding, e.g. securely binding identity modules to devices, services or applications
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 8/183 Processing at user equipment or user record carrier
• CPC Class Codes: H04W 8/186 Processing of subscriber group data

Abstract

Disclosed is a smart card dynamic binding method, herein, a UICC is provided with a first basic file and a second basic file, and before selecting an application, a USIM sets a PIN to a blocked state, instructs a terminal that a USIM service table supports an additional terminal profile, and receives a profile download instruction; after determining that the terminal supports a provide local information command, the USIM sends a proactive provide local information command to the terminal; the UICC receives a terminal response including an IMEI of the terminal, matches the IMEI number with the IMEI number in the first basic file; if the matching is successful, sets a status flag of binding check success into the second basic file; starts a USIM initialization process, sets the PIN to an unblocked status and a disabled status; also disclosed is a smart card dynamic binding device and system.

Claims

1. A smart card dynamic binding method, comprising:

a universal integrated circuit card, UICC, being provided with a first basic file and a second basic file, wherein, the first basic file is used for pre-storing an International Mobile Equipment Identifier, IMEI, of a terminal or a group of terminals, and the second basic file is used for storing a status flag of binding check result;

a universal subscriber identity module, USIM, in the UICC setting a personal identification number, PIN, to a blocked state before selecting an application, instructing the terminal that a USIM Service Table supports an Additional TERMINAL PROFILE, and receiving a Profile download instruction from the terminal;

the USIM sending a proactive PROVIDE LOCAL INFORMATION command to the terminal after determining that the terminal supports the PROVIDE LOCAL INFORMATION command;

the UICC receiving a TERMINAL RESPONSE including the IMEI of the terminal, matching the IMEI number with the IMEI number in the first basic file, and when the matching succeeds, determining that the binding check succeeds, setting a status flag of binding check success into the second basic file, and starting an initialization process of the USIM, and setting the PIN to an unblocked state and a Disable state.

2. The smart card dynamic binding method of claim 1, wherein, said sending the PROVIDE LOCAL INFORMATION command to the terminal comprises:

executing the sending of the PROVIDE LOCAL INFORMATION command through an application program which is pre-embedded in the UICC as a code of an operating system in the UICC.

3. The smart card dynamic binding method of claim 1, wherein, the UICC matching the IMEI number with the IMEI number in the first basic file comprises:

executing the matching of the IMEI number of the terminal with the IMEI number in the first basic file through a script file.

4. The smart card dynamic binding method of claim 3, wherein, the script file is pre-embedded in the UICC as a code of an operating system in the UICC.

5. The smart card dynamic binding method of claim 1, wherein, the method further comprises:

the UICC accepting a dynamic management of a management platform for the first basic file through an OTA mechanism.

6. The smart card dynamic binding method of claim 1, wherein, the method further comprises:

the UICC providing background personnel with reading of the status flag of binding check result in the second basic file through an OTA mechanism.

7. The smart card dynamic binding method of claim 1, wherein, the method further comprises:

when the UICC performs an OTA interaction with the terminal, the terminal determining that a data change has occurred in the first basic file, and executing operations of restarting and resetting the terminal, the UICC being initialized after the terminal is restarted, and re-executing a binding check of the UICC and the terminal.

8. The smart card dynamic binding method of claim 1, wherein, the method further comprises:

when a data change has occurred in the first basic file, the UICC sending a proactive refresh command to the terminal to trigger a 3G session or a reset of the UICC;

after the terminal refreshes, the UICC being initializing and re-executing a binding check of the UICC and the terminal.

9. The smart card dynamic binding method of claim 1, wherein, the method comprises:

a terminal receiving an instruction that a USIM service table supports an Additional TERMINAL PROFILE sent by a USIM in a UICC and returning a Profile download instruction;

the terminal receiving a PROVIDE LOCAL INFORMATION command sent by the USIM in the UICC and sending a TERMINAL RESPONSE including an IMEI number of the terminal to the UICC.

10. The smart card dynamic binding method of claim 9, wherein, the method further comprises:

when the UICC performs an OTA interaction with the terminal, the terminal determining that a data change has occurred in a first basic file, and executing operations of restarting and resetting the terminal.

11. The smart card dynamic binding method of claim 9, wherein, the method further comprises:

when receiving a proactive refresh command sent by the UICC, the terminal performs a refresh operation to trigger a 3G session or a reset of the UICC.

12. (canceled)

13. A UICC which is provided with a first basic file and a second basic file, wherein, the first basic file is used for pre-storing an IMEI of a terminal or a group of terminals, and the second basic file is used for storing a status flag of binding check result;

the UICC further comprises;

a USIM application module, and a matching module;

wherein,

the USIM application module is configured to set a PIN to a blocked state before selecting an application, instruct the terminal that a USIM service table supports an Additional TERMINAL PROFILE, and receive a Profile download instruction from the terminal, after determining that the terminal supports a PROVIDE LOCAL INFORMATION command, send a proactive PROVIDE LOCAL INFORMATION command to the terminal and sets the PIN to an unblocked state and a Disable state after starting an initializing process of the USIM;

a matching module is configured to receive a TERMINAL RESPONSE including an IMEI of the terminal, match the IMEI number with the IMEI number in the first basic file, and determine that the binding check succeeds when the matching succeeds, set a status flag of binding check success into the second basic file, and start an initialization process of the USIM.

14. The UICC of claim 13, wherein, the USIM application module is specifically configured to execute the sending of the proactive PROVIDE LOCAL INFORMATION command through an application program which is pre-embedded in the UICC as a code of an operating system in the UICC.

15. The UICC of claim 13, wherein, the matching module is specifically configured to execute the matching of the IMEI number of the terminal with the IMEI number in the first basic file through a script file.

16. The UICC of claim 13, wherein, the UICC further comprises:

a dynamic management module, configured to accept a dynamic management of a management platform for the first basic file through an OTA mechanism.

17. The UICC of claim 16, wherein, the dynamic management module is further configured to provide background personnel with reading of the status flag of binding check result in the second basic file through the OTA mechanism.

18. The UICC of claim 13, wherein, the UICC further comprises:

a re-binding module, configured to notify the USIM application module after the terminal is restarted;

or send a proactive refresh command to the terminal when a data change has occurred in the first basic file to trigger a 3G session or a reset of the UICC, and notify the USIM application module after the terminal refreshes.

19. A terminal comprising:

a profile download instruction providing module, and an IMEI number providing module;

a profile download instruction providing module, configured to receive an instruction that a USIM service table supports an Additional TERMINAL PROFILE sent by a USIM in a UICC and return a Profile download instruction;

an IMEI number providing module, configured to receive a proactive PROVIDE LOCAL INFORMATION command sent by the USIM in the UICC and send a TERMINAL RESPONSE including an IMEI number of the terminal to the UICC.

20. The terminal of claim 19, wherein, the terminal further comprises, a restarting module, configured to determine that a data change has occurred in the first basic file in the UICC, and execute operations of restarting and resetting the terminal.

21. The terminal of claim 19, wherein, the terminal further comprises:

a refreshing module, configured to perform a refreshing operation upon receiving a proactive refresh command sent by the UICC, to trigger a 3G session or a reset of the UICC.

22. (canceled)