WO2012122752A1

WO2012122752A1 - Method and device for locking or unlocking terminal and smart card

Info

Publication number: WO2012122752A1
Application number: PCT/CN2011/075991
Authority: WO
Inventors: 王潇滨; 刘杰杰
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-03-16
Filing date: 2011-06-20
Publication date: 2012-09-20
Also published as: CN102149074A; CN102149074B

Abstract

A method and device for locking or unlocking a terminal and a smart card are disclosed in the present invention. Wherein the locking method includes the following steps: Personal Computer (PC) side software for locking management obtains an equipment identifier of the terminal and a user identifier of the smart card, searches binding relationship data set by an operator based on said equipment identifier, determines an allowable binding range corresponding to said equipment identifier, judges whether said user identifier is within said allowable binding range or not, if yes binds said equipment identifier and said subscriber identifier, and otherwise, does not perform binding operation. According to the solution provided by the present invention, the terminal and the smart card are locked or unlocked through the PC side software for locking management so that the binding relationship can be flexibly configured or released according to the requirement on the operator, the locking or unlocking are performed conveniently and fast, thus the requirement for locking or unlocking batch terminals and smart cards is satisfied.

Description

Method and device for locking or unlocking terminal and smart card

The present invention relates to terminal technologies, and more particularly to a method and apparatus for locking or unlocking a terminal and a smart card. Background technique

In recent years, with the rapid development of mobile terminal technology, the global popularity of 3G networks, and the intensification of competition among operators, mobile terminal devices are more customized by operators, and operators have also proposed higher customized services. It is required that when the operator customizes the mobile terminal device, for the needs of the operator and the user security, the requirement for a mobile terminal to lock one or a batch of (U)SIM cards is often proposed. The SIM (Subscriber Identity Module) card and the USIM (Universal Subscriber Identity Module) card are collectively referred to as a (U)SIM card.

Locking is a special requirement for a mobile terminal. When the mobile terminal completes the binding operation of locking to a specific card, the mobile terminal is required to use only the specific card, and other cards cannot be used normally on the mobile terminal. In this way, the operator can effectively solve the problems of users transferring the network privately, carrying out the goods privately, and losing the customer group, so as to ensure that the users who purchase the mobile terminal during the promotion can satisfy the terms of the agreement and ensure that the mobile terminal and the service are purchased at a low price. The user is able to use a particular reservation for a relatively long period of time.

Operators place high demands on the security of the lock, usually storing some lock/unlock control information on the mobile terminal or (U)SIM card side. For example, a locking scheme needs to write the acquired locking/unlocking control information in the form of configuration information in the mobile terminal, such as saving in a certain flag of the mobile phone firmware Flash or a fixed memory, so that once the binding relationship is established, It is difficult to change, unless you change the phone firmware or rewrite the memory, you can not flexibly adapt to the operator's flexible operational needs. If the operator's locking requirements for the terminal and the (U)SIM card change, it must pass Trivial operations can be achieved.

In addition, there is currently no effective security mechanism that effectively protects lock-related sensitive data and prevents hackers from breaking the lock. Since the above control information is stored in a memory that the mobile terminal can access at random, such that once the mobile terminal is re-programmed, or the control information is broken or rewritten, the card lock is automatically disabled.

In summary, there is currently no convenient and flexible mobile terminal and (U)SIM card locking scheme. In addition, illegal unlocking cannot be effectively avoided. Summary of the invention

In view of the above, it is an object of the present invention to provide a method and apparatus for locking a terminal and a smart card to facilitate locking. Another object of the present invention is to provide a method and apparatus for unlocking a terminal and a smart card, which is convenient and flexible to unlock.

In order to solve the above technical problem, the technical solution of the present invention is implemented as follows:

A method for locking a terminal and a smart card, comprising: acquiring, by the PC side software for performing the lock management, a device identifier of the terminal and a user identifier of the smart card, searching for the binding relationship data set by the operator based on the device identifier, determining the location Determining the allowed binding range of the device identifier, determining whether the user identifier is within the allowed binding range, and if yes, binding the device identifier and the user identifier; otherwise, not binding operating.

The binding operation between the device identifier and the user identifier includes: the PC side software writes the binding relationship between the device identifier of the terminal and the user identifier of the smart card to the configuration information stored by the terminal and the configuration information stored by the smart card. in.

Before the searching for the binding relationship data set by the operator based on the device identifier, the method further includes: the PC side software reading the configuration information stored by the terminal, determining whether the binding relationship exists, and if yes, ending the current process; if not, Searching for binding relationship data set by the operator based on the device identifier; or

The PC side software reads the configuration information stored by the terminal and the configuration information stored by the smart card, and determines the binding. Whether the relationship exists, if any exists, the current process is ended; if none exists, the binding relationship data set by the operator is searched based on the device identifier.

After the binding operation of the device identifier and the user identifier, the method further includes: the PC side software acquiring the device identifier of the terminal and the user identifier of the smart card, and determining whether the device identifier and the user identifier meet the binding relationship, and if yes, The binding relationship between the device identifier and the user identifier is released; otherwise, the unlocking operation is not performed.

A method for unlocking a terminal and a smart card, comprising: a PC side software for performing lock management, obtaining a device identifier of the terminal, and a user identifier of the smart card, determining whether the device identifier and the user identifier meet the binding relationship, and if The binding relationship between the device identifier and the user identifier is released; otherwise, the unlocking operation is not performed.

The binding relationship between the device identifier and the user identifier is specifically: the binding relationship between the device identifier of the terminal and the user identifier of the smart card is deleted in the configuration information stored in the terminal and the configuration information stored in the smart card; or

Deleting the binding relationship between the device identifier of the terminal and the user identifier of the smart card in the configuration information stored in the terminal; or

The binding relationship between the device identifier of the terminal and the user identifier of the smart card is deleted in the configuration information of the smart card.

Determining whether the device identifier and the user identifier meet the binding relationship, specifically: reading the configuration information stored by the terminal, determining the user identifier that needs to be bound to the terminal, and determining whether the user identifier of the smart card can be tied to the requirement If the matching user IDs match, the configuration information of the smart card is read, and the device IDs to be bound to the smart card are determined, and the device identifiers of the terminal are consistent with the device identifiers to be bound. Compliance with the binding relationship; or,

Read the configuration information of the smart card, determine the device ID to be bound to the smart card, and determine whether the device ID of the terminal is the same as the device ID to be bound. The configuration information stored in the terminal determines the user identifier to be bound to the terminal, and determines whether the user identifier of the smart card can match the user identifier to be bound. If the matching can match, the binding relationship is met; or

The configuration information stored in the terminal is read, and the user identifier to be bound to the terminal is determined, and the user identifier of the smart card is matched with the user identifier to be bound, and if it can match, the binding relationship is met; or

Read the configuration information of the smart card, determine the device ID to be bound to the smart card, and determine whether the device ID of the terminal is the same as the device ID to be bound. If they are consistent, the binding relationship is met.

After obtaining the device identifier of the terminal and the user identifier of the smart card, the method further includes:

The PC side software checks the validity of the acquired device ID and user ID.

A device for locking a terminal and a smart card, comprising:

a device identifier determining unit, configured to acquire a device identifier of the terminal;

a user identifier determining unit, configured to acquire a user identifier of the smart card;

a verification unit, configured to determine, according to the binding relationship data set by the device identifier search operator, the allowed binding range corresponding to the device identifier, and determine whether the user identifier is within the allowed binding range, if Sending the device identifier and the user identifier to the locking unit;

a locking unit, configured to perform a binding operation on the device identifier and the user identifier.

The device further includes an unlocking unit,

The verification unit is further configured to: determine whether the device identifier and the user identifier meet the binding relationship, and if yes, send the device identifier and the user identifier to the unlocking unit; the unlocking unit is configured to: The binding relationship between the device identifier and the user identifier is released. A device for unlocking a terminal and a smart card, comprising:

a device identifier determining unit, configured to acquire a device identifier of the terminal; a user identifier determining unit, configured to acquire a user identifier of the smart card;

a verification unit, configured to determine whether the device identifier and the user identifier meet the binding relationship, and if yes, send the device identifier and the user identifier to the unlocking unit;

The unlocking unit is configured to release the binding relationship between the device identifier and the user identifier.

The verification unit is further configured to: perform an effective check on the acquired device identifier and the user identifier.

The device further includes a detecting unit, configured to determine whether the terminal is correctly connected to the PC, and if yes, triggering the device identification determining unit; and further determining whether the card reader is correctly connected to the PC, and if yes, triggering the user Identification determination unit.

According to the solution provided by the present invention, the locking or unlocking operation of the terminal and the smart card is performed by performing the PC-side software of the lock management, and the binding relationship or the unbinding relationship can be flexibly configured according to the requirements of the operator, and the locking is conveniently and quickly performed. Or unlock the lock to meet the needs of the batch terminal and smart card lock or unlock.

In addition, since the PC-side software for performing lock management is installed on the PC managed by the operator, the binding relationship between the terminal and the smart card storage in the prior art is easily avoided from being easily rewritten and erased, so that the lock is easily released. Effectively avoid illegal unlocking and unlock it through a secure route. DRAWINGS

1 is a schematic flow chart of locking a terminal and a (U)SIM card in the present invention;

2 is a schematic flowchart of unlocking a terminal and a (U)SIM card in the present invention;

3 is a schematic structural diagram of an apparatus for locking a terminal and a smart card in the present invention;

FIG. 4 is a schematic structural diagram of an apparatus for unlocking a terminal and a smart card in the present invention. detailed description

In the present invention, when the lock operation is required, the PC side software for performing lock management is acquired. The device identifier of the terminal and the user identifier of the smart card, based on the binding relationship data set by the device identifier search operator, determining an allowable binding range corresponding to the device identifier, and determining whether the user identifier is in the allowed binding If yes, the binding between the device identifier and the user identifier is performed; otherwise, the binding operation is not performed.

In the present invention, when the unlocking operation is required, the PC-side software for performing the lock management acquires the device identifier of the terminal and the user identifier of the smart card, and determines whether the device identifier and the user identifier meet the binding relationship. If yes, The binding relationship between the device identifier and the user identifier is released; otherwise, the unlocking operation is not performed.

The terminal described above may include a fixed station, a mobile phone, a netbook, and the like. A smart card is a card that can be inserted into a terminal and used to identify a user. It can be a SIM card, a USIM card, or a UIM (User Identity Model) card. The device identifier of the terminal may be an IMEI (International Mobile Equipment Identity), and the user identifier of the smart card may be an IMSI (International Mobile Subscriber Identification Number).

After obtaining the device identifier of the terminal and the user identifier of the smart card, the device identifier and the user identifier of the device may be checked for validity, so that the device identifier and the user identifier of the subsequent locking or unlocking operation are in compliance with international standards and operators. standard.

The binding operation of the device identifier and the user identifier includes: binding the binding relationship between the device identifier of the terminal and the user identifier of the smart card to the configuration information stored by the terminal and the configuration information stored by the smart card.

The binding relationship between the device identifier and the user identifier is specifically: the binding relationship between the device identifier of the terminal and the user identifier of the smart card is deleted in the configuration information stored in the terminal and the configuration information stored in the smart card; or Deleting the binding relationship between the device identifier of the terminal and the user identifier of the smart card in the configuration information stored in the terminal; or deleting the device identifier of the terminal and the user identifier of the smart card in the configuration information stored by the smart card Binding off Department.

The specific implementation of the solution of the present invention is described in detail below by taking the device identification of the terminal as IMEI, the smart card as the (U)SIM card, and the user identification of the smart card as IMSI.

FIG. 1 is a schematic flowchart of locking a terminal and a (U)SIM card according to the present invention. As shown in FIG. 1, the specific processing process includes:

Step 101: When the locking operation is required, the PC side software determines whether the terminal is correctly connected to the PC, and if yes, proceeds to step 102; otherwise, the locking operation fails, and the current process ends.

The PC-side software for lock management is installed on the PC managed by the operator, so that the operator can perform lock management, such as a lock operation or an unlock operation, on the terminal and the (U)SIM card through the PC side software.

The PC connects to the terminal through the data line, and determines whether the terminal is correctly connected to the PC by detecting the port. Specifically, after the terminal is connected to the PC through the data line, the voltage of the port of the PC is changed, and the PC side software detects After the voltage of the port of the PC is changed, the message is sent to the terminal. If the response is returned after receiving the message, the terminal is correctly connected to the PC, and the signal path with the terminal is established; if the terminal does not receive the return In response, the terminal is not properly connected to the PC.

Step 102: The PC side software determines whether the card reader is correctly connected to the PC, and if yes, proceeds to step 103; otherwise, the locking operation fails, and the current process ends.

The PC is connected to the card reader through the data line, and the port is detected to determine whether the card reader is properly connected to the PC. Specifically, after the card reader is connected to the PC through the data line, the voltage of the PC port is changed. After the PC side software detects that the voltage of the port of the PC has changed, it sends a message to the card reader. If the response returned by the card reader after receiving the message, the card reader is correctly connected to the PC, and the software is established. The signal path of the reader; if the response returned by the reader is not received, the reader is not properly connected to the PC. Steps 103 to 104: The PC side software reads the configuration information stored by the terminal, and determines whether the binding relationship exists. If yes, it indicates that the lock is not required, the lock operation fails, and the current process ends. If not, the process continues. 105.

After the terminal is bound to the (U)SIM card, the binding relationship is stored in the configuration information stored in the terminal and the configuration information stored in the (U)SIM card. The configuration information can be used to determine the terminal and the (U)SIM card binding.

Before performing step 105, the PC side software can further read (U) the configuration information stored in the SIM card to determine whether the binding relationship exists. If it exists, it indicates that the lock is not needed at present, the locking operation fails, and the current process ends; If yes, proceed to step 105.

In addition, in the specific implementation, the configuration information stored in the (U)SIM card may be read first, whether the binding relationship exists, and when the binding relationship does not exist, the configuration information stored in the terminal is read.

Steps 105 to 106: The PC side software reads the IMEI of the terminal to determine whether the IMEI is correct. If it is correct, proceed to step 107; if not, the locking operation fails, and the current process ends.

The PC side software sends an AT command for reading the IMEI to the terminal, and after receiving the AT command, the terminal returns the IMEI of the terminal to the PC side software.

After reading the IMEI, the PC side software determines whether the IMEI is correct, that is, checks the validity of the IMEI, that is, determines whether the IMEI complies with international standards and carrier standards, such as determining whether the number of digits of the IMEI and the number of the set digits are in compliance with international standards. Standard and carrier standards.

Steps 107 to 108: The card reader reads (IMS) the IMSI of the SIM card, and the PC side software obtains the IMSI read by the card reader to determine whether the IMSI is correct. If yes, proceed to step 109; if not, then The lock operation failed and the current process is ended.

The PC side software sends an AT command for reading the IMSI to the card reader. After receiving the AT command, the card reader reads the IMEI of the (U) SIM card and returns it to the PC side software.

After obtaining the IMSI, the PC side software determines whether the IMSI is correct, that is, validates the IMSI. Sexual inspection, that is, to determine whether the IMSI complies with international standards and operator standards, such as determining whether the number of digits of the IMSI and the number of the set digits meet international standards and operator standards.

Step 109: The PC side software is based on the binding relationship database set by the IMEI search operator, and obtains an IMSI section that meets the conditions, that is, an IMSI section corresponding to the IMEI, according to the content returned by the binding relation database.

The operator sets and stores the IMSI interval for each IMEI corresponding to the binding in the binding relationship database according to the operation requirements. For example, in the binding relation database, IMEI-1 allows the IMSI interval to be bound to IMSI-1 to IMSI. -5, IMEI-2 allows the IMSI interval of the binding to be IMSI-6 to IMSI-8, and IMEI-3 allows the IMSI interval of the binding to be IMSI-9.

Step 110: The PC side software determines whether the IMSI of the (U)SIM card is within the IMSI interval, and if yes, proceeds to step 111; otherwise, the prompt cannot lock the terminal with the (U)SIM card, the locking operation fails, and the current end Process.

Step 111: The PC side software writes the binding relationship between the IMEI and the IMSI to the configuration information stored in the terminal, and writes the configuration information stored in the (U)SIM card to complete the locking of the IMEI and the IMSI.

After the locking operation is completed, when the terminal is powered on, the terminal reads the configuration information stored by itself, determines the IMSI to be bound to itself, and reads the IMSI of the inserted (U)SIM card, and determines whether the IMSI of the (U)SIM card can Matches the IMSI that needs to be bound. If it can match, it starts normally and allows the user to use normally. If it cannot match, it does not start normally, and the user is prompted to insert the (U)SIM card incorrectly. Further, when the terminal is powered on, the (U)SIM card reads the configuration information stored by itself, determines the IMEI to be bound to itself, and reads the IMEI of the terminal inserted by the (U)SIM card, and determines the IMEI of the terminal. Whether the IMEIs to be bound are consistent. If they are consistent, the information is exchanged with the terminal to enable the terminal to start normally and allow the user to use the device normally. If the information is inconsistent, the terminal does not interact with the terminal, so that the terminal cannot be started normally. U) The SIM card is incorrect. In the solution of the present invention, the operator can hide the configuration information stored in the terminal and the configuration information stored in the (U)SIM card in the set storage space through the PC side software, so that the hidden storage space can be found only in the set storage space through the PC side software. The configuration information, and the configuration information is modified to effectively prevent malicious tampering.

Moreover, in the solution of the present invention, the terminal that needs to be locked may be further configured to read the configuration information stored by itself in the startup process, and if the configuration information is not read, the normal startup cannot be performed; and/or, the configuration needs to be locked. The (U)SIM card must first read the configuration information stored in the terminal during the startup process of the terminal. If the configuration information is not read, the information is not exchanged with the terminal, and the terminal cannot be started normally.

2 is a schematic flowchart of unlocking a terminal and a (U)SIM card according to the present invention. As shown in FIG. 2, the specific processing process includes:

Step 201: When the unlocking operation is required, the PC side software determines whether the terminal is correctly connected to the PC, and if yes, proceeds to step 202; otherwise, the unlocking operation fails, and the current process ends.

The specific implementation is the same as step 101 described above, and details are not described herein again.

Step 202: The PC side software determines whether the card reader is correctly connected to the PC, and if yes, proceeds to step 203; otherwise, the unlocking operation fails, and the current process ends.

The specific implementation is the same as step 102 described above, and details are not described herein again.

Steps 203 to 204: The PC side software reads the configuration information stored by the terminal, and determines whether the binding relationship exists. If yes, the process proceeds to step 205. If not, the current unlocking operation is not required, and the unlocking operation fails. Process.

Step 205 to step 206: The PC side software reads the IMEI of the terminal to determine whether the IMEI is correct. If it is correct, the process proceeds to step 207; if not, the unlock operation fails, and the current process ends.

The specific implementation is the same as the steps 105 to 106 described above, and details are not described herein again. Step 207 to step 208: The card reader reads (IMS) the IMSI of the SIM card, and the PC side software obtains the IMSI read by the card reader to determine whether the IMSI is correct. If yes, proceed to step 209; if not, then The unlock operation failed and the current process is ended.

The specific implementation is the same as the steps 107 to 108 described above, and details are not described herein again.

Step 209: The PC side software reads the configuration information stored by the terminal, and determines the binding with the terminal.

IMSI, judging whether the IMSI of the (U)SIM card can match the bound IMSI, if it can match, proceed to step 210; if it cannot match, it prompts that the terminal cannot be unlocked with the (U)SIM card, and the unlock operation fails. , ends the current process.

Step 210: The PC side software reads (U) the configuration information stored in the SIM card, determines the IMEI bound to the (U)SIM card, and determines whether the IMEI of the terminal is consistent with the bound IMEI. If they are consistent, continue to perform the steps. 211 ; If they are inconsistent, the terminal cannot be unlocked with the (U)SIM card, the unlock operation fails, and the current process ends.

In addition, in the specific implementation, step 210 may be performed first, and then step 209 is performed.

Step 211: The PC side software deletes the binding relationship between the IMEI and the IMSI from the configuration information stored in the terminal and the configuration information stored in the (U)SIM card, and unlocks the IMEI and the IMSI.

In addition, the above unlocking operation is performed on both the terminal and the (U)SIM card. If the user only needs to unlock the terminal, the step 209 may be: the PC side software reads the configuration information stored by the terminal. Determining the IMSI bound to the terminal, determining whether the IMSI of the (U)SIM card can match the bound IMSI, and if yes, deleting the binding relationship between the IMEI and the IMSI from the configuration information stored in the terminal, and ending The current process; if it cannot match, the prompt cannot unlock the terminal and the (U)SIM card, the unlocking operation fails, and the current process ends.

Alternatively, only need to unlock on the (U)SIM card, step 210 may be: the PC side software reads (U) the configuration information stored by the SIM card, determines the IMEI bound to the (U)SIM card, and determines the terminal. Whether the IMEI is consistent with the bound IMEI. If they are consistent, the binding relationship between the IMEI and the IMSI is deleted from the configuration information stored in the (U)SIM card, and the current process is ended; if not, then The prompt cannot unlock the terminal and the (U)SIM card, the unlock operation fails, and the current process ends.

3 is a schematic structural diagram of an apparatus for locking a terminal and a smart card in the present invention. As shown in FIG. 3, the apparatus includes: a device identification determining unit, a user identification determining unit, a verification unit, and a locking unit. The device identifier determining unit is configured to obtain the device identifier of the terminal; the user identifier determining unit is configured to obtain the user identifier of the smart card; the verification unit is configured to determine the binding relationship data set by the operator based on the device identifier, and determine the device. Identifying the allowed binding range, determining whether the user identifier is within the allowed binding range, and if yes, sending the device identifier and the user identifier to the locking unit; the locking unit is configured to use the device The identity and the user identity are bound.

The verification unit is further configured to perform validity check on the acquired device identifier and the user identifier. The device further includes a detecting unit, configured to determine whether the terminal is correctly connected to the PC, and if so, triggering the device identification determining unit; and further configured to determine whether the card reader is correctly connected to the PC, and if yes, triggering the user identification to be determined unit.

The locking unit is specifically configured to: write the binding relationship between the device identifier and the user identifier into the configuration information stored in the terminal, and write the configuration information into the configuration information stored by the smart card.

The device further includes an unlocking unit, and the verification unit is further configured to determine whether the device identifier and the user identifier meet the binding relationship, and if yes, send the device identifier and the user identifier to the unlocking unit; The binding relationship between the device identifier and the user identifier is released.

The verification unit is further configured to: read configuration information stored by the terminal, determine a user identifier that needs to be bound to the terminal, determine whether the user identifier of the smart card can match the user identifier that needs to be bound, and if yes, read The configuration information of the smart card is stored, and the device identifier that is bound to the smart card is determined, and the device identifier of the terminal is determined to be consistent with the device identifier to be bound. If the device identifier is consistent, the device identifier and the user identifier are sent to the unlocking unit. The unlocking unit is specifically configured to: configure the binding relationship between the device identifier and the user identifier from the configuration information stored in the terminal, And delete the configuration information of the smart card storage.

Alternatively, the verification unit is further configured to: read the configuration information stored by the smart card, determine the device identifier that needs to be bound to the smart card, determine whether the device identifier of the terminal is consistent with the device identifier to be bound, and if they are consistent, read the terminal. The stored configuration information is determined, and the user identifier that is bound to the terminal is determined, and the user identifier of the smart card is matched with the user identifier that needs to be bound. If the user identifier is matched, the device identifier and the user identifier are sent to the user identifier. The unlocking unit is specifically configured to: delete the binding relationship between the device identifier and the user identifier from the configuration information stored by the terminal and the configuration information stored by the smart card.

Alternatively, the verification unit is further configured to: read configuration information stored by the terminal, determine a user identifier that needs to be bound to the terminal, and determine whether the user identifier of the smart card can match the user identifier that needs to be bound, and if yes, The device identifier and the user identifier are sent to the unlocking unit. The unlocking unit is specifically configured to: delete the binding relationship between the device identifier and the user identifier from the configuration information stored by the terminal.

Or the verification unit is further configured to: read configuration information stored by the smart card, determine a device identifier that needs to be bound to the smart card, determine whether the device identifier of the terminal is consistent with the device identifier to be bound, and if yes, the The device identifier and the user identifier are sent to the unlocking unit. The unlocking unit is specifically configured to: delete the binding relationship between the device identifier and the user identifier from the configuration information stored by the smart card.

4 is a schematic structural diagram of an apparatus for unlocking a terminal and a smart card according to the present invention. As shown in FIG. 4, the apparatus includes: a device identifier determining unit, a user identifier determining unit, a verifying unit, and an unlocking unit. The device identifier determining unit is configured to obtain the device identifier of the terminal; the user identifier determining unit is configured to obtain the user identifier of the smart card; the verification unit is configured to determine whether the device identifier and the user identifier meet the binding relationship, and if yes, Sending the device identifier and the user identifier to the unlocking unit; the unlocking unit is configured to release the binding relationship between the device identifier and the user identifier. The detailed functions of the verification unit and the unlocking unit are described in detail in Figure 3, This will not be repeated here.

In addition, the specific implementations of the device identifier determining unit, the user identifier determining unit, the verifying unit, the locking unit, the unlocking unit, and the detecting unit in FIG. 3 and FIG. 4 are all involved in the process descriptions of FIG. 1 and FIG. Let me repeat.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for locking a terminal and a smart card, comprising:

The PC-side software for performing the lock management acquires the device identifier of the terminal and the user identifier of the smart card, and based on the binding relationship data set by the device identifier search operator, determines the allowable binding range corresponding to the device identifier, and determines the location Whether the user identifier is within the allowed binding range, and if yes, binding the device identifier and the user identifier; otherwise, the binding operation is not performed.

The method according to claim 1, wherein the obtaining the device identifier of the terminal and the user identifier of the smart card further comprises: performing, by the PC side software, a validity check on the acquired device identifier and the user identifier.

The method according to claim 1, wherein the binding operation between the device identifier and the user identifier comprises: binding, by the PC side software, the device identifier of the terminal and the user identifier of the smart card. The relationship is written in the configuration information stored in the terminal and the configuration information stored in the smart card.

The method according to claim 1, wherein before the searching for the binding relationship data set by the operator based on the device identifier, the method further includes:

The PC side software reads the configuration information stored in the terminal, and determines whether the binding relationship exists. If yes, the current process ends; if not, the binding relationship data set by the operator is searched based on the device identifier; or

The PC side software reads the configuration information stored by the terminal and the configuration information stored by the smart card, and determines whether the binding relationship exists. If any exists, the current process ends. If none exists, the operator settings are searched based on the device identifier. Binding relational data.

The method according to any one of claims 1 to 4, wherein after the binding operation of the device identifier and the user identifier, the method further comprises: acquiring, by the PC side software, a device identifier of the terminal and a user identifier of the smart card, Determining whether the device identifier and the user identifier meet the binding If the relationship is yes, the binding relationship between the device identifier and the user identifier is released; otherwise, the unlocking operation is not performed.

6. A method for unlocking a terminal and a smart card, comprising:

The PC-side software for performing the lock management acquires the device identifier of the terminal and the user identifier of the smart card, and determines whether the device identifier and the user identifier meet the binding relationship. If yes, the device identifier and the user identifier are released. Binding relationship; otherwise, no unlocking operation is performed.

The method according to claim 6, wherein the acquiring the device identifier of the terminal and the user identifier of the smart card further comprises: performing, by the PC side software, a validity check on the acquired device identifier and the user identifier.

The method according to claim 6, wherein the debinding relationship between the device identifier and the user identifier includes:

Deleting the binding relationship between the device identifier of the terminal and the user identifier of the smart card in the configuration information stored in the terminal and the configuration information stored in the smart card; or

The method according to claim 6, 7 or 8, wherein the determining whether the device identifier and the user identifier meet the binding relationship comprises:

The configuration information stored in the terminal is read, and the user identifier that needs to be bound to the terminal is determined, and whether the user identifier of the smart card matches the user identifier that needs to be bound, and if the matching can be performed, the configuration information stored by the smart card is read, and the configuration information is determined. The device ID to be bound to the smart card is used to determine whether the device ID of the terminal is the same as the device ID to be bound. If they are consistent, the binding relationship is met.

Read the configuration information stored in the smart card, and determine the device identifier that needs to be bound to the smart card. Determine whether the device ID of the terminal is the same as the device ID to be bound. If the device ID is consistent, read the configuration information stored in the terminal, determine the user ID to be bound to the terminal, and determine whether the user ID of the smart card can be bound. The user IDs match, and if they match, they match the binding relationship; or,

10. A device for locking a terminal and a smart card, comprising:

The device according to claim 10, wherein the verification unit is further configured to: perform validity check on the acquired device identifier and the user identifier.

The device according to claim 10, wherein the device further comprises: a detecting unit, configured to determine whether the terminal is correctly connected to the PC, and if yes, triggering the device identification determining unit; Whether the card is correctly connected to the PC, and if so, the user identification determining unit is triggered.

13. Apparatus according to claim 10, 11 or 12, wherein said apparatus Further including an unlocking unit,

The verification unit is further configured to: determine whether the device identifier and the user identifier meet the binding relationship, and if yes, send the device identifier and the user identifier to the unlocking unit; the unlocking unit is configured to: The binding relationship between the device identifier and the user identifier is released.

14. A device for unlocking a terminal and a smart card, comprising:

The device according to claim 14, wherein the verification unit is further configured to: perform validity check on the acquired device identifier and the user identifier.

The device according to claim 14 or 15, wherein the device further comprises a detecting unit, configured to determine whether the terminal is correctly connected to the PC, and if yes, triggering the device identification determining unit; Whether the card reader is properly connected to the PC, and if so, the user identification determining unit is triggered.