WO2005050910A1 - A method for authenticating the device’s self-validity - Google Patents

Abstract

The invention discloses a method for authenticating the device's self-validity. At least it includes the following steps: a first device stores a key which needs to authenticate self-validity; and stores a pairing key in a second device corresponding to the key then the first device obtains the authenticating information corresponding to the pairing key storing in the second device; the first device judges whether the key stored in the first device matches with the paring key stored in the second device according to authenticating information obtained from the second device; if it matches, the first device judges it self is valid; or else, it self is not valid. The invention can effectively authenticate the device's self-validity and easily be carried out.

Description

 Method for equipment to verify its legitimacy

Technical field

 The present invention relates to a security verification technology, and in particular, to a method for a device to verify its legitimacy. Background of the invention

 With the improvement of equipment security requirements, more and more attention is being paid to the verification of equipment legality. For example, some companies do not want employees to use company office equipment, especially computers, during non-working hours, so set a power-on password for each computer. When employees use the computer, they must enter the power-on password to turn it on. In this way, a password administrator can turn on each computer separately during working hours, so that employees can use the computer normally during working hours, and during passwords during non-working hours. Employees cannot use the computer without the administrator turning on the computer. This method can effectively control the occasion and time for employees to use the computer, but a password administrator is required to manage the startup password of the company's computer. Therefore, this management method brings inconvenience to the management of the employee and the company. Passwords may be leaked, and the computer system of the entire company is not highly secure.

Similarly, in order to prevent the leakage of core technologies developed by some high-tech companies, employees are restricted from directly outputting relevant data information from the computer through the computer's floppy drive or computer interface through methods such as floppy drive locks, rubberized computer interfaces, or P covers on the chassis. The computer interface here can be a USB port, a serial port, or a parallel port. In this way, the information leakage behavior caused by these information output interfaces can be effectively restricted, so as to achieve the purpose of maintaining the confidentiality of the scientific research results of the entire R & D team. However, the above-mentioned method not only limits the output of information through the above-mentioned channels, but also limits the input of information through the above-mentioned channels. Therefore, it often brings inconvenience to the normal use of users. For example, a research and development Due to work needs, personnel urgently need to view the information stored on a floppy disk. At this time, the research and development personnel must first apply, and after the application is approved, a special person will be assigned by the floppy key storage center to unlock the floppy disk lock of the computer, and In order to prevent the behavior of copying the floppy drive keys in the middle, the floppy drive information can only be viewed with the assistance of this person.

 Especially for a mobile terminal such as a mobile phone, its security is more important for the user. Most current mobile terminals use a machine-card separation method, that is, the mobile terminal itself and the user card used to verify wireless network user information are two separate parts, and they can be combined together when in use. This method has many outstanding advantages. For example, if the user wants to change a mobile terminal, he only needs to purchase a new mobile terminal and insert the original user card into the new mobile terminal. In this way, since the user's information does not need Therefore, the user does not need to go through any formalities for replacing the mobile terminal with the communication operator.

 However, the use of the machine-card separation method brings great convenience to users, and also leads to the theft and theft of mobile terminals, so that in some places people are afraid to hang the mobile terminal around their waists. Because in the machine-card separation mode, as long as a new user card is replaced on the stolen mobile terminal, it can be used without any obstacles. In this way, the thief can resell the stolen mobile terminal to make a profit. In this way, not only the user's economic benefits are greatly affected, but also need to go to the communication operator to go through a series of procedures, such as changing the contract data, which brings great inconvenience to the user.

In order to solve the problem that the mobile terminal is easy to be stolen, a more common method is to set a password protection on the mobile terminal. For example, a power-on password is set on the mobile terminal, and a correct power-on password needs to be entered each time the mobile terminal is turned on, so that the mobile terminal can perform subsequent operations such as registering with the network. If the power-on password is entered incorrectly, the mobile terminal cannot be used normally. In this way, even if the thief obtains the user's mobile terminal, he will not be able to use and sell it because he cannot enter the correct password. Therefore, this method solves the mobile terminal easily to a certain extent The problem of being stolen. However, for this method, a legal user also needs to enter a password each time the computer is turned on, which will bring great trouble to the daily use of the legal user. Therefore, at present, many users do not set such a power-on password because they feel that it is too troublesome to enter the power-on password each time, which makes this solution difficult to be accepted by users and obtains practical applications, and thus cannot fundamentally solve the problem that mobile terminals are easily stolen. Grab the problem.

 Another solution is to build a large number of Equipment Identification Register (EIR) devices and put the international mobile equipment identification (IMEI) of those stolen mobile terminals into the corresponding EIR blacklist. In this way, each time a mobile terminal is connected to the network, it needs to go to the EIR device to check whether the IMEI corresponding to the mobile terminal is added to the blacklist. If the IMEI of the mobile terminal is found in the blacklist, the network considers that the IMEI The user of the mobile terminal is an illegal user, thereby rejecting his service request. In this way, the thief will also not be able to profit from the obtained mobile terminal because it cannot be used again, which can fundamentally solve the problem that the mobile terminal is easily stolen. However, this method requires the construction of a large number of EIR equipment, the construction of network equipment needs to be increased, and the network construction cost of the communication operator is increased. At the same time, this method also requires different communication operators to unify this anti-theft service at the same time, so as to avoid that mobile terminals lost from one communication operator's network can be taken to another communication operator's network for use, which will greatly increase the number of communication operators. The tedious service coordination work among them increases the operation cost of the communication operator, and brings inconvenience to the business development of the communication operator.

 Therefore, how to more effectively verify the legitimacy of the device, and in particular, how to make the mobile terminal more effectively verify its legitimacy is a problem that needs to be urgently solved at present. Summary of the invention

In view of this, the main object of the present invention is to provide a method for the device to verify its legitimacy, which can effectively enable the device to verify its legitimacy and improve the security of the device. And the implementation is simple and reliable.

 In order to achieve the above objective, the method for verifying the legitimacy of the device according to the present invention includes at least the following steps:

 a save a key on the first device that needs to perform its own legality verification, and save a pairing key corresponding to the key on the second device;

 b. The first device obtains a verification letter corresponding to the corresponding pairing key stored by the second device c The first device determines whether the key stored by the first device and the corresponding pairing key stored by the second device match according to the verification information If yes, judge yourself legal; otherwise judge yourself illegal.

 Here, the insurance key information of the pairing key may be the pairing key itself, a calculation result obtained by calculating the pairing key, or a calculation result of jointly calculating the pairing key and the random number.

 The first device may be a mobile terminal, and the second device may be a verification device such as an HLR, AC, EIR, UC, or short message device in a mobile communication network. At this time, the verification device further stores a pairing key and mobile terminal related information. Corresponding relationship among them, the mobile terminal related information may be mobile terminal user information, mobile terminal device information, or user card information in the mobile terminal.

 When the first device is a mobile terminal, the second device may also be a second mobile terminal holding multiple pairing keys, or a user card or electronic key holding one pairing key.

 The first device may be a computer device, and the second device is a server device. The computer is determining that the key stored by the first device and the pairing key stored by the second device may be a pair of symmetric keys or an asymmetric key.

As can be seen from the technical solution of the present invention, the present invention is implemented by setting and saving on the first device. A key for verifying its legitimacy, and a corresponding pairing key is stored in the second device. Before the first device is normally used, the first device actively or passively obtains the verification information of the corresponding pairing key stored on the second device, and verifies the pairing key and itself according to the verification information obtained from the second device. Whether the saved keys match, if they match, determine that they are legal, that is, they are in a legal use state, or that the user currently using themselves is a legitimate user; otherwise, they are judged to be illegal, that is, they are in an illegal use state, or that The user currently using himself is an illegal user. If you do not want the first device to be used illegally, you only need to shut down the second device, or clear the corresponding pairing key stored by the second device, or make the second device not respond correctly to the request of the first device, so that the first device The device cannot be used normally because it cannot get the corresponding verification information. Or, if an illegal user is currently operating the first device, the authentication information obtained by the first device from the second device may be different from the authentication information obtained by the legal user from the second device, so that the first device cannot pass. The matching verification prevents illegal users from using the first device normally. In this way, the present invention can effectively achieve the purpose of the device verifying its legitimacy.

 In addition, the present invention only needs to set and save a key on a device that needs to verify its legitimacy, and save a corresponding pairing key on another device, and perform one time acquisition and save on another device before the device is normally used. The operation of the verification information of the pairing key and the operation of verifying whether the pairing key and the key saved by itself match based on the verification information may be sufficient, and the entire process is very simple and convenient.

For the normal use of password management for a computer, a password that can be set in the computer and can be permanently stored on the computer for the computer to verify its legitimacy, and at the same time, a corresponding pairing password is stored in a password management server; the computer is based on The corresponding pairing password verification information obtained from the password management server verifies whether the pairing password matches the password saved by itself. If they match, it means that the computer is used legally, that is, it is allowed to use; otherwise it means that the computer is illegally used, that is, it is prohibited use. In this way, by controlling the secret The code management server can conveniently and effectively control the computer's use on time and place. For computer anti-disclosure, a key set in the computer and can be permanently stored in the computer for the computer to verify the openness of its special functions, and at the same time, a corresponding pairing key is stored in an information security server; The computer verifies whether the pairing key matches the key saved by the pairing key according to the verification information of the pairing key obtained from the information security server. If the pairing key matches, the computer opens the use of its own special functions, such as allowing a floppy drive, USB port, parallel port, or The serial port is normally used, otherwise the computer is prohibited from using its own special functions. In this way, by controlling the information security server, you can conveniently and effectively control the opening and prohibition of the corresponding special functions of all other computers.

 For a mobile terminal, a key that is set in the mobile terminal and can be permanently stored in the mobile terminal for the mobile terminal to verify its legitimacy, and at the same time, a corresponding pairing key is stored in a one-lens identification device; The mobile terminal verifies whether the pairing key matches the key saved by the pairing key according to the verification information of the pairing key obtained from the verification device. If the pairing key matches, it indicates that the mobile terminal is used legally, otherwise it indicates that the mobile terminal is illegally used. In this way, for the stolen mobile terminal, by controlling the access of the corresponding pairing key stored by the verification device, the stolen mobile terminal cannot obtain the verification information of the correct pairing key from the verification device. Therefore, the stolen mobile terminal cannot be verified as being illegally used by itself when it is used, so that the stolen mobile terminal cannot be used normally. At this time, the mobile terminal is locked, the location of the mobile terminal is recorded, and the owner is notified according to the communication number stored in the mobile terminal in advance, and the public security agency is reported, so that illegal users can not only use the stolen mobile terminal to make a profit, but also Being caught quickly, thereby effectively eliminating the motive of thieves stealing the mobile terminal, helping the owner to recover the lost mobile terminal as soon as possible, and then fundamentally solving the problem that the mobile terminal is easy to be stolen.

For the user, the process of setting the key can be automatically and randomly generated by the mobile terminal, and of course, it can also be automatically and randomly generated by the verification device. Therefore, the user does not need to perform complicated input. Into. After the key is set, the mobile terminal automatically performs the above-mentioned legality verification operation when it is used, and does not require the user to perform tedious operations such as entering a power-on password. Therefore, it brings great convenience to the user and makes the present invention More practical.

 Because the access to the corresponding pairing key stored by the verification device is controlled, the stolen mobile terminal cannot obtain the correct verification information of the pairing key from the verification device, thereby making the stolen mobile terminal in use. It cannot be judged as illegal use through its own verification, so that the stolen mobile terminal cannot be used normally. Therefore, the method of the present invention does not require different communication operators to carry out this anti-theft service at the same time, reduces unnecessary service coordination between communication operators, reduces the operational complexity of the communication operators, and reduces the operation costs of the communication operators.

 For communication operators, they can make full use of existing network equipment, such as adding verification device functions to the HLR and saving corresponding pairing keys for mobile terminals to verify their legitimacy, so that mobile terminals can perform verifications from the HLR. Obtain the verification information of the corresponding pairing key. The entire operation process is simple and requires only a small amount of equipment investment by the communication operator, or even an increase in equipment investment. Moreover, since the method according to the present invention basically does not increase the operation complexity of the communication operator, the operation cost is reduced. It has almost no impact, and therefore also makes the method according to the invention easier to be accepted by a communication operator.

 In summary, the present invention can effectively verify the legitimacy of the device, improve the security of the device, and implement the method in a simple and reliable manner. Brief description of the drawings

 FIG. 1 is an overall flowchart of the present invention. '

 FIG. 2 is a method flowchart of the first embodiment of the present invention.

 FIG. 3 is a flowchart of a method according to a second embodiment of the present invention.

FIG. 4 is a flowchart of a method according to a third embodiment of the present invention. FIG. 5 is a flowchart of a method according to a fourth embodiment of the present invention.

 FIG. 6 is a flowchart of a method according to a fifth embodiment of the present invention.

 FIG. 7 is a flowchart of a method according to a sixth embodiment of the present invention.

 FIG. 8 is a flowchart of a method according to a seventh embodiment of the present invention.

 FIG. 9 is a flowchart of a method according to an eighth embodiment of the present invention.

 FIG. 10 is a method flowchart of a ninth embodiment of the present invention.

 FIG. 11 is a flowchart of a method according to a tenth embodiment of the present invention.

 FIG. 12 is a flowchart of a method according to an eleventh embodiment of the present invention.

 FIG. 13 is a flowchart of a method according to a twelfth embodiment of the present invention.

 FIG. 14 is a method flowchart of a thirteenth embodiment of the present invention.

 FIG. 15 is a method flowchart of a fourteenth embodiment of the present invention. Mode of Carrying Out the Invention

 The present invention is described in detail below with reference to the drawings and specific embodiments.

 Figure 1 shows the overall flowchart of the invention. As shown in FIG. 1, in step 101, a first device that needs to verify its legitimacy is set and saved with a key Ka for the first device to verify its legitimacy, and at the same time, a second device that is independent of the first device A corresponding pairing key Kb is stored on the device.

 In step 102, when the first device needs to perform authentication, the first device obtains the authentication information of the corresponding pairing key Kb stored on the second device.

 In step 103, the first device verifies whether the pairing key Kb and the key Ka held by itself match according to the verification information of the corresponding pairing key Kb obtained from the second device. If they match, the first device determines that it is legal in step 104 If they do not match, the first device determines that it is illegal in step 105.

The first device determines that it is legal in fact that the first device determines that it is currently using its own The user is legal, that is, the user currently uses himself legally; accordingly, the first device determines that the user is illegal. In fact, the first device judges that the user currently using itself is illegal, that is, the user currently uses himself illegally.

 In step 102, the first device may first send a request message to the second device to obtain the verification information of the corresponding pairing key Kb. After receiving the request message from the first device, the second device sends the request message to the first device. A device sends a response message containing the verification information of the corresponding pairing key Kb stored. Here, the first device sends the request message to the second device, either immediately after the first device has a special state, or after a random time or a predetermined time has passed after the first device has a special state. The special state here may be that the first device is started, or that the first device is connected to the second device, or that a period of time for verification of a cycle is reached, and so on.

 Alternatively, in step 102, the second device may actively send the saved verification information of the corresponding pairing key Kb to the first device, for example, the second device connects to itself at the first device, or waits for a period of verification When the time point is reached, the saved verification information of the corresponding pairing key Kb is sent to the first device.

 The key Ka stored in the first device and the corresponding pairing key Kb stored in the second device may be a pair of symmetric keys in a symmetric key mechanism, or may be an asymmetric key (that is, a public key). A pair of public and private keys for the mechanism. For the case of using a symmetric key mechanism, the key Ka and the pairing key Kb may be the same or different. If they are different, the pairing key Kb should be able to be derived from the key Ka. For the case of using an asymmetric key mechanism, the private key of the paired key is generally used as the key Ka, and the public key of the paired key is used as the paired key Kb. At this time, since the secret is derived from the paired key Kb The calculation amount of the key Ka is an astronomical number. Therefore, it can be considered that the key Ka cannot be derived from the pairing key Kb. Symmetric keys and asymmetric keys are common knowledge to those skilled in the art, and they are not described in this article.

The method of the present invention is further described in detail through specific embodiments. In the first embodiment of the present invention, the verification information of the corresponding pairing key Kb is the pairing key Kb itself, that is, the second device directly sends the corresponding pairing key Kb to the first device. The specific process is shown in Figure 2.

 In step 201, a key Ka that is used by the first device to verify its legitimacy is set on the first device that needs to verify its legitimacy, and a corresponding pairing key Kb is stored on another second device.

 In step 202, when authentication is required, the first device sends a request message to the second device to obtain the corresponding pairing key Kb.

 In step 203, after receiving the request message from the first device, the second device sends the corresponding pairing key Kb stored in the second device to the first device in a response message.

 In step 204, the first device verifies whether the corresponding pairing key Kb obtained from the second device and the key Ka held by itself match, and if they match, the first device determines that it is legal in step 205; if it does not match, in step 206 The first device judged itself illegal.

 In this embodiment, if the key Ka and the pairing password Kb are the same, step 204 directly determines whether the corresponding pairing key Kb obtained from the second device and the key Ka held by itself are equal to verify whether the two match. If the key Ka and the pairing password Kb are not the same, the pairing key Kb can be simply derived from the key Ka, for example, Kb is the result of an exclusive-OR operation of Ka and a fixed constant. Whether the corresponding pairing key Kb can be derived from the key Ka saved by itself to verify whether the two match; or directly in step 201, establish and save the correspondence between the key Ka and the pairing password Kb on the first device. In step 204, it is directly judged whether the corresponding pairing key Kb obtained from the second device and the key Ka held by itself satisfy the established correspondence relationship to verify whether the two match.

In the first embodiment, the second device directly sends the pairing key Kb to the first device. And we know that the key information is easily leaked during the process of sending the pairing key ¾) by the second device to the first device, so the security is not high enough. To this end, the present invention proposes a second embodiment as shown in FIG. 3.

 In step 301, a key Ka that is used by the first device to verify its legitimacy is set and saved on the first device that needs to verify its legitimacy, and a corresponding pairing key Kb is stored on another second device.

 In step 302, when authentication is required, the first device sends a request message to the second device to obtain authentication information of the corresponding pairing key Kb.

 In step 303, after receiving the request message from the first device, the second device performs calculation according to a corresponding pairing key Kb saved by itself according to a predetermined algorithm, and obtains a calculation result, that is, the corresponding pairing key Kb verify message.

 In step 304, the second device sends the obtained calculation result to the first device through a response message.

 In step 305, the first device also performs calculation according to a predetermined algorithm according to the key Ka saved by the first device, and obtains a calculation result.

 In step 306, the first device compares the calculation result received from the second device with the calculation result obtained by itself to verify whether the corresponding pairing key Kb stored by the second device and the key Ka held by itself match, and if they match, in step 307 The first device determines that it is legal; if it does not match, the first device determines that it is illegal in step 308.

Here, the predetermined algorithm used by the second device may be any algorithm, and preferably performs digest calculation. Accordingly, the predetermined algorithm used by the first device may be an algorithm corresponding to the predetermined algorithm used by the second device. For example, if the corresponding pairing key Kb stored by the second device is the same as the key Ka held by itself, then the first device and the second device may use the same digest algorithm to perform the matching based on the pairing key Kb and the key Ka, respectively. Digest operation, the obtained operation result information will be the same, that is, the digest calculated according to the pairing key Kb and the key Ka The calculated digests are the same, that is, it can be verified whether the pairing key Kb and the key Ka match by comparing whether the digest results are the same. For another example, if the corresponding pairing key Kb stored by the second device is different from the key Ka held by itself, and the pairing key Kb can be simply derived from the key Ka, then if the second device uses a digest algorithm Then, the algorithm corresponding to the first device should first include simply deriving the pairing key Kb from the key Ka, and then perform the same digest algorithm as the second device's calculation based on the derived pairing key Kb.

 In the second embodiment, a fixed algorithm is used for the calculation of a fixed key, so that the result obtained by each calculation is the same. This also causes the calculation result information to be easily forged due to leakage, thereby reducing the cost. Invention safety. For this reason, the present invention proposes a third embodiment as shown in FIG.

 In step 401, a key Ka that is used by the first device to verify its legitimacy is set and saved on the first device that needs to verify its legitimacy, and a corresponding pairing key Kb is stored on another second device.

 In step 402, when the first device needs to perform authentication, it sends a random number to the second device, and requests to obtain authentication information of the corresponding pairing key Kb.

 In step 403, the second device calculates according to a corresponding pairing key Kb saved by itself and a random number received from the first device according to a predetermined algorithm, and obtains a calculation result, that is, verification information of the corresponding pairing key Kb.

 In step 404, the second device sends the obtained calculation result to the first device.

 In step 405, the first device performs calculation according to a predetermined algorithm according to a key Ka saved by itself and a random number generated by itself, to obtain a calculation result.

In step 406, the first device compares the calculation result received from the second device with the calculation result obtained by itself to verify whether the corresponding pairing key Kb saved by the second device and the key Ka held by itself match, and if they match, in step 407 The first device determines that it is legal; if not, the first device determines that it is illegal. Similar to the second embodiment, the predetermined algorithm used by the second device here may be any algorithm, and preferably performs encryption, decryption, or digest operations, for example, using a key to perform a cryptographic operation on a random number, or according to a key Calculates a summary of the random numbers. Accordingly, the predetermined algorithm used by the first device may be an algorithm corresponding to the predetermined algorithm used by the second device. For example, if the corresponding pairing key Kb held by the second device is the same as the key Ka held by itself, then the second device and the first device may use the same digest algorithm to respectively compare the pairing key Kb and the key Ka with each other. The random number is digested, and the obtained calculation result information will be the same, that is, the digest of the random number calculated according to the pairing key Kb and the digest of the random number calculated according to the key Ka are the same, that is, by comparing whether the digest result is The same can verify whether the pairing key Kb and the key Ka match.

 In addition, the second device may also generate a controllable random number to perform verification. For this reason, a fourth embodiment shown in Fig. 5 is proposed.

 In step 501, a key Ka that is used by the first device to verify its legitimacy is set on the first device that needs to verify its legitimacy, and a corresponding pairing key Kb is stored on another second device.

 In step 502, when authentication is needed, the first device sends a request message to the second device to obtain authentication information of the corresponding pairing key Kb.

 In step 503, the second device generates a controllable random number, and performs calculation according to a corresponding pairing key Kb and the controllable random number saved by itself according to a predetermined algorithm, to obtain a calculation result, that is, a corresponding pairing key Kb Verification information.

 In step 504, the second device sends the obtained calculation result and the generated controllable random number to the first device.

 In step 505, the first device performs calculation according to a predetermined algorithm according to the key Ka saved by itself and the controllable random number received from the second device to obtain a calculation result.

In step 506, the first device compares the calculation result received from the second device with its own obtained Whether the calculated results match, if they match, execute step 507, and if they do not match, determine in step 510 that they are illegal.

 In step 507, the first device determines whether the controllable random number is acceptable, and if so, determines that it is legal in step 508; otherwise, determines in step 509 that the verification operation has failed.

 After determining that the verification operation fails, the next verification operation may be performed again, for example, requesting the second device to generate a controllable random number again, or renegotiating a controllable random number generation rule with the second device. For example, it is required that the controllable random number generated by the second device starts from a certain number and is generated in increments, and the increment is within a range, such as within 0 to 255, and so on.

 The controllable random number generated by the second device can be generated by setting a controllable random number occurrence. The controllable random number generator includes a controllable number generator and a random number generator. The controllable number generator can generate a controllable number sequence. Two adjacent numbers in the controllable number sequence satisfy a preset relationship, such as the previous number is greater than or less than the next number, or the latter number is the same as the previous number. The difference satisfies a certain rule, for example, the difference is a constant value, or the difference is a number in a region such as 1 to 256, or the difference itself is an equal difference sequence, and so on. A typical example of a controllable number sequence is a sequence of natural numbers, where the difference between each number and its previous number is a constant one.

 When the second device generates a random number using a controllable random number generator, first a controllable number is generated by the controllable number generator, and a random number is generated by the random number generator; and then a controllable number and a random number are jointly calculated to obtain a random number. The new random number. The joint calculation here can insert each bit of the controllable number into the random number according to a certain rule.

The first device determines whether the controllable random number is acceptable by directly determining whether the random number is a controllable random number. For example, after receiving the random number and the calculation result, the first device picks up the controllable number from the random number according to the above-mentioned insertion rule, and compares the controllable number saved by the first device when the previous verification succeeds, that is, the reference number, Determine whether the value and the reference number saved by itself meet the preset rule or relationship of the controllable number sequence, such as whether it is increasing, and the difference is No is between 0 and 255 and so on. If the rule is satisfied, the value is determined to be a controllable number, and accordingly, the random number is a controllable random number; otherwise, it is determined that the random number is not a controllable random number. The first device saves the controllable number picked up as a reference number each time the verification is successful, so as to be used as a comparison parameter in the next verification. During the initial verification of the first device, the stored reference number may be a null value, for example, 0.

 In addition, for the fourth embodiment, a controllable random number may not be generated, but a verification sequence number may be further considered when the random numbers are jointly calculated. The first device is a mobile terminal and the second device is an HLR. In this case, the verification serial number may be an authentication serial number used for mobile terminal authentication. For this reason, a fifth embodiment shown in Fig. 6 is proposed.

 In step 601, a key Ka that is used by the first device to verify its legitimacy is set and saved on the first device that needs to verify its legitimacy, and a corresponding pairing key Kb is stored on another second device. A verification sequence number is stored on both the first device and the second device.

 In step 602, when the first device verifies its legitimacy, a random number is generated by the second device. For example, the random number is generated after receiving a request message from the first device, or the random number is generated in a specific state, such as reaching a predetermined time.

 In step 603, the second device generates a random number and calculates according to a predetermined algorithm according to the corresponding pairing key Kb saved by itself, the random number and the saved verification sequence number, to obtain a calculation result, that is, the corresponding pairing key Kb Verification information.

 In step 604, the second device sends the obtained calculation result, the generated random number, and the saved verification sequence number to the first device.

 In step 605, the first device performs calculation according to a predetermined algorithm according to the key Ka saved by itself and the random number and verification sequence number received from the second device to obtain a calculation result.

In step 606, the first device compares whether the calculation result received from the second device and the calculation result obtained by itself match, and if they match, execute step 607; if they do not match, in step 610 The first device determines that it is illegal.

 In step 607, the first device determines whether the verification serial number is acceptable. If it is, in step 608, the first device determines that it is legal, and uses the verification serial number to update the verification serial number saved by itself. Otherwise, it determines in step 609 The operation fails. At this time, the next verification operation can be performed again, such as requesting to update the verification serial number saved by itself, or initiating an operation to synchronize the verification serial number, so that the verification serial number of the second device is synchronized with the verification serial number of the first device. For example, the verification serial number of the first device is sent to the second device, and the second device updates its own verification serial number according to the verification serial number of the first device, so that the verification serial numbers stored by the two are consistent, thereby ensuring the next time. The first device judges that the verification serial number is acceptable.

 Step 604 further includes an operation of updating the verification serial number by the second device.

 The judgment of whether the verification serial number is acceptable here is to determine whether a preset condition is satisfied between the current verification serial number and the verification serial number stored by the first device. The preset condition here is that the difference between the current authentication serial number and the authentication serial number stored by the first device is within a predetermined range. Of course, other conditions are also possible.

 Of course, it can be understood that it is also possible to first determine whether the verification serial number is acceptable, and if it is acceptable, determine whether the calculation result matches, if not, determine that the first device is illegal, and if it matches, determine that the first device is legal; The serial numbers do not match, and you can initiate a synchronous serial number verification operation.

 As described above, the first verification device determines that the verification operation fails, or the first device determines that it is illegal.

In the previous embodiment, the pairing key Kb and the key Ka generally belong to a pair of symmetric keys. If the pairing key Kb and the key Ka are a pair of asymmetric keys, then Ka can also be stored on the first device as a private key and the pairing key Kb as a public key on the second device. To this end, the present invention proposes a sixth embodiment as shown in FIG. 7. In step 701, a first device that needs to verify its legitimacy is set up and saves a private key Ka for the first device to verify its legitimacy, and at the same time, a corresponding paired public key Kb is stored on another second device.

 In step 702, when authentication is required, the first device sends a random number to the second device, requesting to obtain authentication information of the corresponding paired public key Kb.

 In step 703, the second device performs a cryptographic calculation on the random number received from the first device according to a corresponding paired public key Kb stored by itself, to obtain a ciphertext of the random number, that is, verification of the corresponding paired public key Kb. information.

 In step 704, the second device sends the obtained ciphertext to the first device.

 In step 705, the first device decrypts the ciphertext obtained from the second device according to the private key Ka saved by itself, and obtains the corresponding plaintext.

 In step 706, the first device compares whether the plaintext obtained by decryption is the same as the random number that it sent to the second device in step 702 to verify whether the corresponding pairing key Kb saved by the second device matches the key Ka saved by itself. If it matches, the first device determines that it is legal in step 707; if it does not match, the first device determines that it is invalid in step 708.

 In the present invention, a verification switch indicating whether to perform legality verification may be set on the first device. When the first device needs to perform verification, first read the value of the verification switch, if the value indicates that the validity is not performed Verification, then the first device directly determines that it is legal without performing the verification step. If the value of the verification switch indicates that verification is required, the first device executes the steps of obtaining verification information from the second device and judging the correctness of the verification information, and determines whether it is legal according to the judgment result.

Of course, the user can perform maintenance and management operations on the key or the authentication switch stored on the first device, such as setting a key, viewing a key, setting an authentication switch, viewing an authentication switch, and the like. For the security of using the first device, for these maintenance management operations, a maintenance management operation password may be further set. Specifically, a Maintenance management operation password. When the user needs to perform maintenance management operations on the key or verification switch of the first device, the first device first prompts the user to enter the maintenance management operation password. If the maintenance management operation password entered by the user is correct, the first device Allow users to perform maintenance management operations; otherwise, the first device does not allow users to perform maintenance management operations.

 In a seventh embodiment of the present invention as shown in FIG. 8, the first device is a mobile terminal, and the second device is a verification device that stores user information of the mobile terminal. For example, it may be an HLR or an AC.

 In step 801, a key Ka is set and saved on the mobile terminal. The key Ka can be any combination of characters with an unlimited number of digits, preferably a digital key of 128 bits or more is used. The key Ka should be able to be permanently stored in the mobile terminal without power, that is, when the mobile terminal is not powered, the key Ka will still be stored in the mobile terminal without being lost.

 In step 802, the correspondence between the pairing key Kb of the key Ka and the user information of the mobile terminal user is stored in an authentication device. The user information here may be the number of the mobile terminal, the International Mobile Subscriber Identity (IMSI) information of the user card, the subscription data of the user, or any other information that can identify the user identity of the mobile terminal, such as a user card Electronic serial number ESN, user card or user ID number stored in the mobile terminal, and so on.

 In step 803, after connecting to the network, the mobile terminal sends a request message requesting the pairing key Kb of the mobile terminal key Ka to an authentication device such as the HLR.

 In step 804, after receiving the request message from the mobile terminal, the verification device sends the corresponding pairing key Kb corresponding to the current user information of the mobile terminal to the corresponding mobile terminal through the response message.

In step 805, after receiving the key Kb from the verification device, the mobile terminal verifies whether the pairing key Kb obtained from the verification device and the key Ka held by itself match. If the two match, the mobile terminal determines in step 806 Legal, that is, the current user of the mobile terminal is Legal users, at this time the mobile terminal is allowed to perform any operation. If the two do not match, in step

807 determines that the mobile terminal is illegal, that is, the user of the mobile terminal is an illegal user.

 After determining that the user of the mobile terminal is illegal in step 807, the mobile terminal may perform a lock operation at this time to reject the user's business operation, or notify the network to stop serving the mobile terminal, and so on. For example, the mobile terminal can perform processing such as locking the keyboard and stopping responding to the user's operation, so that the user can no longer use the mobile terminal. In addition, an alarm message can also be sent to the communication operator through the communication network, and the communication operator reports the public security agency for processing, or directly reports the alarm to the public security agency. Of course, the mobile terminal user can also set a communication alarm number on the mobile terminal in advance, such as setting For the communication numbers of relatives and friends, the mobile terminal notifies the owner according to the communication alarm number stored in the mobile terminal in advance by the owner after discovering that the terminal has been used illegally. In addition, when performing processes such as locking the keyboard and stopping responding to user operations, the mobile terminal can play voice messages such as "You are an illegal user" to attract the attention of the illegal users.

Of course, it can be understood that, in the seventh embodiment, like the second embodiment, a predetermined calculation such as a digest operation may be performed on the key to perform corresponding matching verification. A random number can be further generated like the third embodiment, and the random number and the key are used for joint calculation to perform corresponding matching verification. Like the fourth embodiment, a controllable random number can be generated and further judged whether the controllable random number is acceptable. As in the fifth embodiment, the verification serial number can be saved and further judged whether the verification serial number is acceptable. As in the sixth embodiment, a private key may be stored in the mobile terminal, and the corresponding relationship between the paired public key of the private key stored in the corresponding authentication device and the user information of the user of the mobile terminal. In this case, the mobile terminal sends a random number to the verification device. The verification device obtains the corresponding paired public key according to the mobile terminal user information, uses the public key to encrypt the random number, and sends the obtained ciphertext to the mobile The terminal, the mobile terminal decrypts the ciphertext according to the private key saved by itself to obtain a plaintext of a random number, and then determines whether the plaintext is the same as the random number sent to the verification device by itself. Whether the saved private key and the public key corresponding to the current user information of the mobile terminal stored by the verification device match to determine the legality status of the mobile terminal. That is, in the seventh embodiment, any one of the calculation modes in the first to sixth embodiments can be combined.

 In an eighth embodiment of the present invention as shown in FIG. 9, the first device is a mobile terminal and the second device is a short message forwarding device. The short message forwarding device here may be a short message center.

 In step 901, a special short message communication number is set in advance.

 In step 902, a key Ka is set and saved in the mobile terminal.

 In step 903, the correspondence between the user information and the pairing key Kb of the key Ka set in the mobile terminal is added in the short message forwarding device.

 In step 904, the mobile terminal sends a short message of the pairing key Kb requesting the mobile terminal key Ka by using the special short message communication number as the called number after connecting to the network. In step 905, the short message forwarding device is receiving After receiving the short message from the mobile terminal, it is determined that the short message is a short message for which the mobile terminal requests a key according to the destination number of the short message as a special short message communication number.

 In step 906, the short message forwarding device obtains a corresponding pairing key Kb corresponding to the user of the mobile terminal according to the mobile terminal number or IMSI information carried in the short message.

 In step 907, the short message forwarding device sends a short message to the mobile terminal, and the calling number of the short message is the aforementioned special short message communication number, and the short message carries the information obtained by the short message forwarding device. The corresponding pairing key Kb.

 In step 908, after receiving the short message whose calling number is the special short message communication number, the mobile terminal extracts the corresponding pairing key Kb obtained by the short message forwarding device from the short message.

In step 909, the mobile terminal compares whether the corresponding pairing key Kb obtained from the short message forwarding device matches the key Ka stored by itself, and if the two match, in step 910 The mobile terminal determines that it is legal, that is, indicates that the current user of the mobile terminal is a legitimate user. At this time, the mobile terminal allows any operation. If the two do not match, the mobile terminal determines that it is illegal in step 911, that is, it indicates that the mobile terminal is current. The user is an illegal user.

 Compared with the seventh embodiment, the request message sent by the mobile terminal to the verification device and the response message returned by the verification device to the mobile terminal are both sent through a short message.

 In a ninth embodiment of the present invention as shown in FIG. 10, the first device is a mobile terminal, and the second device is a short message sending and receiving device. The short message sending and receiving device here may be a second mobile terminal or a short message sending and receiving device. Short message server.

 In step 1001, a short message communication signal code is set for the short message transmitting and receiving device required for verification.

 In step 1002, a key Ka is set and saved in the mobile terminal.

 In step 1003, the correspondence between the user information and the pairing key Kb of the key Ka set in the mobile terminal is added in the short message transceiver.

 In step 1004, after the mobile terminal is connected to the network, the mobile terminal sends a short message to the short message sending and receiving device requesting the pairing key Kb of the mobile terminal key Ka through the short message communication number.

 In step 1005, after receiving the short message from the mobile terminal, the short message transmitting and receiving device obtains a corresponding pairing key Kb corresponding to the mobile terminal user according to the mobile terminal number or IMSI information carried in the short message.

 In step 1006, the short message sending and receiving device sends a short message to the mobile terminal, and the short message carries the corresponding pairing key Kb obtained by the short message sending and receiving device.

 In step 1007, after the mobile terminal receives the short message whose calling number is the short message communication number of the short messaging device, the mobile terminal extracts the corresponding matching key Kb obtained by the short messaging device.

In step 1008, the mobile terminal compares the corresponding pairing secrets obtained from the short messaging device. Whether the key Kb matches the key Ka stored by the user. If the two match, the mobile terminal determines that it is legal in step 1009, that is, it indicates that the current user of the mobile terminal is a legitimate user. At this time, the mobile terminal is allowed to perform any operation. If they do not match, the mobile terminal determines that it is illegal in step 1010, that is, it indicates that the current user of the mobile terminal is an illegal user.

 In the above eighth and ninth embodiments, for a short message center serving as a short message forwarding device, it may directly receive a short message from a mobile terminal and send a short message to the mobile terminal. For a short message server or another second mobile terminal, the short message interaction between the mobile terminal and the short message server, or the short message interaction between the mobile terminal and the second mobile terminal needs to be forwarded by the short message center.

 When the second device is a short message sending and receiving device, the short message sending and receiving device is often not specifically used to respond to the authentication request of the mobile terminal. These short message sending and receiving devices may also process some short messages for other purposes. The short message sending / receiving device needs to distinguish the short message used for verifying the request. At this time, a verification operation code may be added to the short message sent by the mobile terminal to the short message sending and receiving device to verify the request to distinguish that the short message is a short message used to verify the request, so that the short message sending and receiving device can distinguish and process. Correspondingly, the short message sending and receiving device should also add a verification operation code to the short message of the verification request returned to the mobile terminal to distinguish that the short message is the short message of the verification request, so that the mobile terminal can Distinguish. The verification operation code here may be identified by adding a specific content to the beginning of the short message.

 The short message forwarding device and the short message transmitting and receiving device herein may be collectively referred to as a short message device. In a tenth embodiment of the present invention as shown in FIG. 11, the first device is a mobile terminal and the verification device is an unstructured supplementary service data (USSD) center (UC).

 In step 1101, a key Ka is set and saved in the mobile terminal.

In step 1102, the correspondence between the user information and the pairing key Kb of the key Ka set in the mobile terminal is added in the UC. In step 1103, after connecting to the network, the mobile terminal sends a request message for the pairing key Kb of the mobile terminal key Ka to the UC through a USSD command.

 In step 1104, after receiving the request message from the mobile terminal, the UC obtains the corresponding pairing key Kb corresponding to the user of the mobile terminal according to the user information carried in the request message.

 In step 1105, the UC sends the obtained corresponding pairing key b to the mobile terminal through a USSD command.

 In step 1106, the mobile terminal compares whether the corresponding pairing key Kb obtained from the UC matches the key Ka held by itself. If the two match, the mobile terminal determines that it is legal, that is, it indicates the current user of the mobile terminal. It is a legal user. At this time, the mobile terminal is allowed to perform any operation. If the two do not match, the mobile terminal determines that it is illegal in step 908, that is, it indicates that the current user of the mobile terminal is an illegal user.

 For the ninth embodiment, if the second device is a second mobile terminal, as in the tenth embodiment, when the mobile terminal sends an authentication request to the second mobile terminal, it is not through a short message, but through a user. To the user signaling (UUS) to pass the certificate request; correspondingly, when the second mobile terminal sends the response message of the request message to the mobile terminal, the response message may also be transmitted not through the short message but through the UUS.

In practice, for a case where the first device is a mobile terminal and the second device is a second mobile terminal, the second mobile terminal may not perform the operation of saving the correspondence between the user information and the corresponding pairing key Kb, and It is sufficient to directly save the pairing key Kb of the key Ka of the mobile terminal as the first device, because the second mobile terminal may store a limited number of pairs of the key Ka of the mobile terminal as the first device Key Kb. In this case, after the second mobile terminal receives the verification request, it can send all the saved pairing keys Kb to the mobile terminal that needs to be verified, and the mobile terminal that needs to be verified determines whether there is a The pairing key Kb of the two mobile terminals matches the key Ka held by themselves. Now, the inspection passes, otherwise the insurance card fails.

 In the seventh to tenth embodiments, the correspondence between the user information of the mobile terminal user and the corresponding pairing key Kb is stored in the authentication device. In practice, the identification information of the mobile terminal may be used to replace the user information of the mobile terminal user stored in the correspondence relationship described in the verification device as the second device. The user information of the mobile terminal and the identification information of the mobile terminal herein may be collectively referred to as mobile terminal related information. In the following embodiments, the correspondence between the identification information of the mobile terminal and the corresponding pairing key Kb is saved in the blepharoplasty device.

 In the eleventh embodiment of the present invention as shown in FIG. 12, the first device is a mobile terminal, and the second device is a verification device that stores identification information of the mobile terminal. For example, it may be an HLR or an AC. Can be EIR.

 In step 1201, a key Ka is set and saved on the mobile terminal. The key Ka can be any combination of characters with an unlimited number of digits, preferably a digital key of 128 bits or more is used. The key Ka should be able to be permanently stored in the mobile terminal without power, that is, if the mobile terminal is not powered, the key Ka will still be stored in the mobile terminal without being lost.

 In step 1202, a correspondence between the pairing key Kb of the key Ka and the identification information of the mobile terminal is stored in an authentication device. The identification information here may be the identification of the mobile terminal. For example, for GSM, it may be IMEI, for CDMA, it may be ESN, and of course, it may also be a personalized information customized by the user for the mobile terminal.

 In step 1203, after connecting to the network, the mobile terminal sends to the verification device such as the HLR a request message requesting the pairing key Kb of the mobile terminal key Ka, and the request information carries identification information of the mobile terminal.

 In step 1204, after receiving the request information from the mobile terminal, the verification device obtains the corresponding pairing key Kb according to the identification information of the mobile terminal, and sends the pairing key Kb to the corresponding mobile terminal.

In step 1205, after receiving the key Kb from the verification device, the mobile terminal verifies Whether the pairing key Kb obtained from the verification device and the key Ka held by it match, and if they match, it is determined in step 1206 that the mobile terminal is legal, that is, the current user of the mobile terminal is a legitimate user, and the mobile terminal is allowed to perform In any operation, if the two do not match, it is determined in step 1207 that the mobile terminal is illegal, that is, the current user of the mobile terminal is an illegal user.

 Here, an identifier may be further set for a correspondence relationship between the pairing key stored in the verification device and related information of the mobile terminal, and for a lost mobile terminal, the identifier is set as that the mobile terminal is lost. At this time, before the verification device determines the pairing key, it further includes: determining whether the identifier indicates that the mobile terminal has been lost, and if so, acquiring contract information of the mobile terminal user, thereby determining information of the current user who illegally uses the mobile terminal, to help find The whereabouts of the stolen mobile terminal; otherwise, it is processed according to the normal process, that is, the step of determining the pairing key and the subsequent steps are performed. Of course, it can be understood that the identification effect can also be determined after the pairing key is determined, and the same effect can be achieved.

 Similarly, in the seventh to tenth embodiments, the user information of the mobile terminal user stored in the correspondence relationship in the verification device as the second device is replaced with the identification information of the mobile terminal, and When the verification device sends the verification request message, it carries the identification information of the mobile terminal. Accordingly, the verification device obtains the corresponding pairing key Kb according to the mobile terminal identification information carried in the request message.

 In a twelfth embodiment of the present invention as shown in FIG. 13, the first device is a mobile terminal, and the second device is a user card inserted in the mobile terminal.

 In step 1301, a key Ka is set and saved on the mobile terminal, and a pairing key Kb of the key Ka is set and saved on the user card.

 In step 1302, the mobile terminal sends a request message to the user card requesting authentication information of the pairing key Kb.

In step 1303, after receiving the request message from the mobile terminal, the user card sends the verification information of the pairing key Kb to the mobile terminal. In step 1304, the mobile terminal verifies whether the verification information of the pairing key Kb obtained from the user card and the verification information of the key Ka held by itself match. If the two match, it is determined in step 1305 that the mobile terminal is legal, that is, the mobile terminal The current user is a legal user. At this time, the mobile terminal is allowed to perform any operation. If the two do not match, it is determined in step 1306 that the mobile terminal is illegal, that is, the current user of the mobile terminal is an illegal user.

 In the twelfth embodiment, an electronic key used with a mobile terminal can be used instead of a user card, and the same effect can be achieved.

 Of course, it can be understood that in the twelfth embodiment, the verification information of the pairing key can be the pairing key itself as in the first embodiment. The key can be subjected to a predetermined calculation such as a digest operation as in the second embodiment to perform corresponding matching verification. A random number can be further generated like the third embodiment, and the random number and the key are used for joint calculation to perform corresponding matching verification. Like in the fourth embodiment, a controllable random number is generated and it is further judged whether the controllable random number is acceptable. Like the fifth embodiment, it is possible to save the verification serial number and further determine whether the verification serial number is acceptable. As in the sixth embodiment, a private key is stored in the mobile terminal, and a paired public key of the private key is stored in the user card. In this case, a random number is sent to the user card through the mobile terminal, the user card uses the paired public key to encrypt the random number, and sends the obtained ciphertext to the mobile terminal, and the mobile terminal decrypts it according to the private key saved by it The ciphertext obtains the plaintext of the random number, and then compares the plaintext and the random number sent to the user card to determine whether the private key saved by the user and the public key saved by the user card match to determine the validity of the mobile terminal. status. That is, in the twelfth embodiment, any one of the calculation modes in the first to sixth embodiments can be combined.

In the seventh to twelfth embodiments, there is no strict sequence between storing the key Ka in the mobile terminal and the corresponding pairing key Kb in the verification device, that is, the correspondence may be saved in the verification device first. The corresponding pairing key Kb for the user information of the mobile terminal user or the identification information of the mobile terminal, and then save the key Ka in the mobile terminal. More Further, the pairing key Kb corresponding to the key Ka and Ka of the mobile terminal may be generated by the mobile terminal, and the key Ka is stored in the mobile terminal, and the pairing key Kb is sent to the verification device and saved by the verification device; or corresponding to the mobile The key Ka of the terminal and the pairing key Kb of Ka are generated by the verification device, and the pairing key Kb is stored in the verification device, and the key Ka is sent to the corresponding mobile terminal for storage by the mobile terminal.

 There are two ways to send the pairing key Kb from a mobile terminal to an authentication device such as HLR and AC. One way is to call a special number first, and then append the above information to be sent to the verification device. For example, suppose the pairing key Kb is 5134356, call a special number first 17999, and then add the pairing key Kb5134356 after 17999, that is, call 179995134356. In this way, the verification device will extract the pairing key Kb5134356 according to the previous agreement. The second method is implemented by adding a supplementary service command operation code to the verification device. For example, the SetK operation code for setting the key is used to set the pairing key Kb of the mobile terminal password Ka in the verification device, and the GetK command is used to obtain the pairing key Kb of the mobile terminal key Ka from the verification device. For the case where the mobile terminal is HLR, SetK can be completed by setting a call forwarding command, for example, setting the prefix of the destination number of the call forwarding to a special prefix, and appending the pairing password Kb to be set after the prefix. GetK can be completed by querying the call transfer status command. For example, the number prefix of the call transfer destination number returned by the HLR to the mobile terminal is a special number prefix, and the pairing password Kb obtained by the query is appended to the number prefix. Of course, the pairing key Kb can also be transmitted by other methods.

In these embodiments, the key Ka and the pairing key Kb generated by the mobile terminal can be generated automatically or manually. In the case of automatic generation, if the user selects the legality verification operation through the menu of the mobile terminal to execute the legality verification function setting, the mobile terminal judges whether the key Ka saved by it is empty, and if it is empty, the mobile terminal automatically randomly Generate and save the key Ka and the pairing key Kb. For the same case, the mobile terminal The terminal only needs to generate one, and then save the key Ka, and automatically send the pairing key Kb to the verification device, for example, by using a SetK operation code. After the verification device obtains the pairing key Kb sent by the mobile terminal, it establishes a correspondence between the pairing key Kb and the current user information or mobile terminal identification information of the mobile terminal. If it is generated manually, the mobile terminal will require the user to input the key Ka and the pairing key Kb by himself, save the information entered by the user (or save only the key Ka) after the user inputs, and send the pairing key Kb to the verification device in. In the automatic mode, the mobile terminal can display the randomly generated key to the user. When the mobile terminal executes the setting of the validity verification function, if it finds that the key Ka held by it is not empty, the mobile terminal directly obtains the pairing key Kb according to the key Ka, and sends the pairing key Kb to the verification device. Save it. Obtaining the pairing key Kb according to the key Ka may be deriving the pairing key Kb according to the key Ka, or querying the pairing key Kb according to the key Ka, and so on.

 There are multiple ways for setting the first device key Ka and the second device setting key Kb, which are not listed here.

 The mobile terminal user can set, view, change and clear the key Ka and the pairing key Kb, and at the same time, synchronize the setting or change result of the pairing key Kb to the verification device, and the verification device will modify the corresponding saved original The correspondence between the user information of the mobile terminal user and the pairing key Kb is modified by the verification device, and the correspondence between the corresponding identification information of the corresponding mobile terminal and the pairing key Kb is stored.

 Of course, it is also possible to set a verification switch for whether to perform a verification operation in the mobile terminal. In this way, the mobile terminal performs the above verification operation only when the verification switch is turned on; otherwise, the mobile terminal directly judges that it is being used legally. The user of the mobile terminal can perform the operations of closing and opening the authentication switch.

The maintenance operation password can be set on the mobile terminal to restrict the setting, viewing, changing, and clearing of the key information, as well as setting the verification switch and checking the status of the verification switch. Here The setting operations include opening and closing. When a user needs to view key information and other maintenance operations, he must enter the password. The mobile terminal determines whether the password is correct. If the password is allowed to be viewed correctly, the user is not allowed to view it. In this way, it is possible to further prevent thieves from obtaining key information set by the user in the mobile terminal, thereby being convenient for the user without losing the anti-theft effect.

 In order to facilitate the operation and maintenance of legal users, the mobile terminal should be able to enable the user to perform maintenance operations on the mobile terminal without being connected to the mobile network. For example, if the user fails to pass the authentication of the mobile terminal 3 due to card replacement, the mobile terminal may prompt the user to actively close the verification switch or reset the key Ka.

 In the case where the first device to be verified is a mobile terminal, the key Ka in the mobile terminal may be stored on a chip separately set in the mobile terminal, and the chip may be referred to as a legality verification chip. In the present invention, the operation of the mobile terminal to determine whether the key Ka stored in the mobile terminal and the corresponding pairing key Kb stored in the verification device match can be performed by the validity verification chip.

 In the case where the first device is a mobile terminal and the second device is a verification device, if the correspondence between the pairing key Kb of the mobile terminal key Ka and the user information of the user of the mobile terminal is stored in the verification device, what needs to be explained is After the mobile terminal sets the validity verification function, whether the user replaces the user card or the number, and the corresponding pairing key Kb corresponding to the user information of the user of the corresponding verification device has not changed, that is, it is still stored with the mobile terminal. If the key Ka matches, the mobile terminal can still pass the verification operation of the present invention even after the user card is replaced. On the contrary, if the pairing key Kb in the user information is changed, that is, it no longer matches the key Ka stored in the mobile terminal, the mobile terminal cannot pass the verification operation of the present invention. Therefore, for a stolen mobile terminal, since the pairing key Kb corresponding to the user information of the thief cannot match the key Ka of the stolen mobile terminal, the thief will not be able to use the mobile terminal normally.

If a legal user forgets the key information saved by the mobile terminal, the legal user can View the key information through the password; similarly, the user can also obtain the corresponding pairing key Kb set in the verification device from the operator according to the identity certificate. Therefore, the mobile terminal adds a legality verification function, while improving the security of the user's mobile terminal, it will not bring troubles in use and maintenance to the legal user.

 In the case that the first device is a mobile terminal and the second device is a verification device, if the correspondence between the pairing key Kb of the mobile terminal key Ka and the mobile terminal identification information is stored in the verification device, the mobile terminal replaces the user card Later, if the mobile terminal can still access the corresponding authentication device, for example, the authentication device is jointly constructed by different operators, or users of different operators are allowed to access the authentication device to each other, then the mobile terminal can still be used normally. If the authentication device is owned by a device operator and only users of the operator's network are allowed to access the authentication device, after the mobile terminal has replaced the user card, if the user card is the user card of the operator's network, the mobile device The use of the terminal is not affected; if the user card is not the user card of the operator's network, the mobile terminal cannot pass the verification because it cannot access the corresponding insurance equipment, so that the mobile terminal cannot be used normally. In this way, it can effectively prevent The occurrence of illegal network hopping. In this case, if the user's mobile terminal is stolen, the user can request the operator to delete the correspondence between the identification information of the mobile terminal and the corresponding pairing key Kb stored in the verification device by virtue of his own identity certificate. Since the stolen mobile terminal cannot obtain the corresponding pairing key Kb required for the mobile terminal for verification when the thief uses it again, the thief will not be able to use the mobile terminal normally, thus achieving the anti-theft effect.

 The mobile terminal mentioned in the present invention may be a mobile phone, a personal digital assistant (PDA), a portable computer or a personal computer (PC), etc., as long as they can directly or indirectly connect to a verification device on a corresponding communication network, the present invention can be applied. Invented to verify the legality of equipment use.

In addition, for companies that want to restrict employees' use of computers during non-working hours, this The invention proposes a thirteenth embodiment as shown in FIG. 14. The first device is a computer device, and the second device is a password management server.

 At step 1401, a normal use password is stored in the computer device.

 In step 1402, a correspondence between a managed computer device and a corresponding normal use password is stored in the password server.

 In step 1403, when the normal use password needs to be input after the computer device is turned on, a request message for the normal use password is sent to the password management server.

 In step 1404, if the password management server confirms that the computer device can be powered on, it sends a corresponding normal use password to the computer device; otherwise, it sends a computer device failure message or a wrong normal use password to the computer device.

 In step 1405, the computer device compares whether the normal use password obtained from the password management server is consistent with the normal use password saved by itself. If they are the same, it is determined in step 1406 that they are legal and allowed to enter the normal use state; otherwise, it is determined in step 1407 that they are illegal and prohibited to enter the normal use state, or directly shut down, so that the employee cannot use the computer equipment.

 Of course, it can be understood that if the password management server is shut down during non-working hours or does not respond to the request message sent by the computer device, the computer device will not receive the power-on password information from the password management server, and the comparison in step 1405 will inevitably Failed to start normally. In this way, the company can restrict employees to use the company's computer equipment during non-working hours by turning on and off the password management server separately during working hours and non-working hours.

 For computer anti-disclosure, the present invention proposes a fourteenth embodiment as shown in FIG.

In step 1501, a key Ka is set and saved in the computer for the computer to verify the legitimacy of its special function opening. In step 1502, at the same time, a corresponding pairing key Kb of the computer is stored in an information security server.

 In step 1503, when the computer performs special functions as required, for example, a floppy drive is needed, or data needs to be written to the computer through a USB port, etc., the insurance key information of the matching key Kb is obtained from the information security server.

 In step 1504, the information security server obtains the corresponding pairing key Kb according to the information of the requesting computer, and sends the obtained verification information of the pairing key Kb to the computer.

 In step 1505, after receiving the verification information of the pairing key Kb returned by the information security server, the computer determines whether the pairing key Kb and the key Ka held by it match based on the verification information. If they match, in step 1506, The computer opens the use of its own special functions, such as allowing the floppy drive, USB port, parallel port or serial port to be used normally; otherwise, in step 1507, the computer prohibits the use of its own special functions.

 Here, the key Kb may be the same as the key Ka, and the verification information of the key Kb may be the key Kb itself. In step 1505, it is determined whether the pairing key Kb and the key Ka saved by the key Kb match to determine whether Kb is Same as Ka. ·

Of course, it can be understood that in the fourteenth embodiment, a predetermined calculation such as a digest operation may be performed on the key to perform corresponding matching verification as in the second embodiment, or a random number may be further generated as in the third embodiment. And use the random number and key for joint calculation to perform corresponding matching verification. Similarly, as in the fourth embodiment, a controllable random number may be further generated and it is determined whether the controllable random number is acceptable. As in the sixth embodiment, a private key is stored in a computer, the corresponding relationship between the paired public key of the private key stored in the corresponding information security server and the computer information, and a computer is sent to the information security server through the computer. A random number, the information security server obtains a corresponding paired public key according to the computer information, encrypts the random number with the public key, and sends the obtained ciphertext to the computer, and the computer decrypts the ciphertext according to the private key saved by the computer Plain text of random numbers, then By comparing whether the plaintext and the random number sent to the information security server are the same, it can be judged whether the private key saved by itself and the public key corresponding to the computer saved by the information security server match, and then whether the computer allows the corresponding special function use.

 In this way, by controlling the information security server, you can conveniently and effectively control the opening and prohibition of the corresponding special functions of all other computers.

 It can be understood that, in a case where the first device cannot obtain the verification information of the corresponding pairing key Kb from the second device, that is, the pairing key Kb of the key Ka does not exist on the second device, the first device will directly determine that it is illegal .

 In all the above embodiments, the correspondence between the user information of the mobile terminal user and the corresponding pairing key Kb, the correspondence between the identification information of the mobile terminal and the corresponding pairing key Kb, and the personality of the mobile terminal are stored in the verification device. The correspondence between the information and the corresponding pairing key Kb, the correspondence between the computer and the corresponding pairing password Kb, and the correspondence between the computer and the corresponding pairing key Kb are actually the user information of the mobile terminal user, the mobile terminal's The identification information, the personalized information of the mobile terminal, and the computer information such as the computer equipment identification are used as the name of an account, and the pairing key Kb is used as the key of the account. In this way, when the first device performs verification, it obtains the verification information of the corresponding pairing key Kb from the corresponding verification device according to the corresponding account name, and verifies the corresponding pairing key Kb stored in the second device according to the verification information. Whether it matches the key Ka saved by you. Therefore, the implementation methods such as the account name and key Ka set for authentication that are extended from this clearly fall within the protection scope of the present invention.

In the present invention, the mobile terminal related information may be user information of the mobile terminal, and the user information is one or any combination of mobile terminal number information, international mobile subscriber identity IMSI information, or user subscription data. The above mobile terminal related information may be mobile terminal user card related information, and the user card related information is one of personal identification information set in the user card, international mobile subscriber identity IMSI information, and electronic serial number ESN of the user card, or random combination. The above mobile terminal related information may be mobile terminal identification information, and the mobile terminal identification information is international mobile equipment identification IMEI information or personal identification information set in the mobile terminal.

 The present invention can preset a prescribed verification operation response time. If the first device does not complete a verification operation within the prescribed verification operation response time, the first device may directly determine that it is illegal, or may determine that the verification operation failed and Repeat the next verification operation. If the next verification operation is successful, it may be determined that the first device is legitimate.

 However, in order to prevent the verification from being repeated forever, a verification operation end time may be specified. If the first device fails to pass the verification within the prescribed verification operation end time, it will directly determine that it is illegal. Or you can specify a permitted number of verification operations. If the first device fails to pass the verification within the specified number of allowed verification operations, it will directly determine that it is illegal.

 In the present invention, the second device exists independently of the first device, that is, the second device does not depend on the first device, and if there is no first device, the second device can operate normally. In other words, the operations of the first device and the second device are independent of each other.

 The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall be included in the present invention. Within the scope of protection.

Claims

Claim  1. A method for validating the legitimacy of equipment insurance, including at least the following steps:  a. Save a key on the first device that needs to perform its own legality verification, and save a pairing key corresponding to the key on the second device;  b. The first device obtains the verification information corresponding to the corresponding pairing key stored by the second device.  c The first device judges whether the key stored by the first device matches the corresponding pairing key stored by the second device according to the verification information, and if yes, determines that it is legal; otherwise, determines that it is illegal.  2. The method according to claim 1, wherein the verification information corresponding to the pairing key is the pairing key itself, and whether the judgment of the key and the pairing key match in step c directly determines the key and Whether the pairing keys match.  3. The method according to claim 1, wherein the verification information corresponding to the pairing key is a calculation result obtained by performing a predetermined calculation on the pairing key, and step b comprises: the second device pair corresponding to the first The corresponding pairing key of the device performs a predetermined calculation, and sends the calculation result to the first device;  Step c further includes: after acquiring the authentication information from the second device, the first device performs a corresponding predetermined calculation on the key saved by itself, and obtains a calculation result; determining whether the key and the pairing key are described in step C Matching is to determine whether the two calculation results match. 4. The method according to claim 3, wherein the second device performs a predetermined calculation on the pairing key by performing a predetermined joint calculation on the pairing key and a random number, and the first device performs a secret calculation on itself. The corresponding predetermined calculation of the key is a corresponding predetermined joint calculation of the key stored in the first device and the same random number. 5. The method according to claim 4, further comprising the step of generating a random number by the first device and sending the random number to the second device before step b, or further including the second step before step b. The device generates a random number, and step b further includes a step in which the second device sends the random number to the first device.  6. The method according to claim 4, further comprising: before step b, the second device generates a controllable random number, and in step b, further comprising the second device sending the controllable random number to the first device. The step of counting, before judging that they are legal in step c, further includes judging whether the controllable random number is acceptable, and if yes, judging that they are legal, otherwise determining that the verification operation has failed.  7. The method according to claim 3, further comprising: generating, by the second device, a random number and storing a verification sequence number; and performing a predetermined calculation on the pairing key by the second device is a pairing secret. The key, the random number, and a verification sequence number are used to perform predetermined joint calculation. The method further includes the second device sending the random number and the verification sequence number to the first device. A corresponding predetermined joint calculation is performed on the key stored by the first device and the random number and the verification serial number received from the second device.  8. The method according to claim 7, characterized in that the step ankle c before judging that it is legal further comprises judging whether the verification serial number is acceptable, and if so, judging itself as legal, otherwise determining that the verification operation has failed.  9. The method according to claim 8, characterized in that the method further comprises the first device storing a verification serial number when the last verification succeeds, and the determination of whether the verification serial number is receivable is to determine the current verification serial number and the first A device saves whether the pre-set conditions are met between the serial numbers. 10. The method according to claim 9, wherein the preset condition is whether a difference between a current verification sequence number and a verification sequence number stored by the first device is within one Within the predetermined range.  11. The method according to any one of claims 3, 4, and 7, wherein the predetermined calculation is one of an encryption operation, a decryption operation, or a digest operation.  12. The method according to claim 1, wherein the one device is a mobile terminal, and the second device is an authentication device.  13. The method according to claim 12, wherein the verification device further stores a correspondence relationship between a pairing key and related information of the mobile terminal, and the acquiring in step b corresponds to the storage of the second device. The verification information for the corresponding pairing key includes:  The mobile terminal sends a request message to the verification device to obtain verification information corresponding to the corresponding pairing key stored by the verification device;  After receiving the request message, the verification device determines a corresponding pairing key according to the relevant information of the mobile terminal;  The verification device sends a response message containing verification information corresponding to the determined pairing key to the mobile terminal.  14. The method according to claim 13, wherein the verification device is one of a home location register (HLR), an authentication center (AC), and an equipment identity register (EIR) provided in a mobile communication network.  15. The method according to claim 13, wherein the verification device is an unstructured supplementary service data USSD center, and the request message and response message are sent by a USSD command.  16. The method according to claim 13, wherein the verification device is a short message device, and the request message and the response message are sent through a short message, and the method further comprises: receiving, from the short message, the mobile terminal from The verification information is extracted from the short message of the device. 17. The method according to claim 16, wherein the short message device is a short message center, and the short message as the request message is a special number whose called number is a pre-assigned one. The short message with a fixed number, and the short message as a response message is a short message with the calling number being the specific number.  18. The method according to claim 16, wherein the short message device is a second mobile terminal or a short message server.  19. The method according to claim 18, wherein the request message and response message are short messages with a verification operation code.  20. The method according to claim 13, further comprising setting an identifier for the correspondence between the pairing key stored in the authentication device and the mobile terminal related information, and setting the identifier for the lost mobile terminal. Because the mobile terminal has been lost, the insurance card device further determines whether the identifier indicates that the mobile terminal has been lost when determining the pairing key, and if so, does not return verification information to the mobile terminal; otherwise, performs the step of returning verification information to the mobile terminal.  21. The method according to claim 13, wherein the mobile terminal related information is user information of the mobile terminal, and the user information is mobile terminal number information, international mobile subscriber identity IMSI information, or user subscription data. One or any combination.  22. The method according to claim 13, wherein the mobile terminal related information is mobile terminal user card related information, and the user card related information is personal identity information set in the user card and an international mobile user identity IMSI One or any combination of information, electronic serial number ESN of the user card.  23. The method according to claim 13, wherein the mobile terminal related information is mobile terminal identification information, and the mobile terminal identification information is International Mobile Equipment Identity IMEI information or a personal identity set in the mobile terminal. information.  24. The method according to claim 23, wherein before step b, the method further comprises the step of the mobile terminal sending mobile terminal identification information to the second device. 25. The method according to claim 12, wherein the verification device is a second A mobile terminal, where the second mobile terminal stores one or more pairing keys, and step b includes:  The first mobile terminal sends a request message to the second mobile terminal to obtain a pairing key corresponding to the first mobile terminal;  After receiving the request message, the second mobile terminal saves a value greater than or equal to 1 key is sent to the first mobile terminal;  The first mobile terminal verifies its legitimacy by comparing whether a pairing key of one or more received from the second mobile terminal contains a pairing key that matches the key held by itself.  26. The method according to claim 25, wherein the first mobile terminal sends a request message to the second mobile terminal to obtain a corresponding pairing key corresponding to the first mobile terminal and the second mobile terminal sends the request message to the second mobile terminal. Sending a key greater than or equal to 1 to the first mobile terminal is performed through a short message with a verification operation code.  27. The method according to claim 12, wherein a pairing key is stored in the verification device, and the obtaining the verification information corresponding to the corresponding pairing key stored in the second device in step b comprises:  The mobile terminal sends a request message to the verification device to obtain verification information corresponding to the corresponding pairing key stored by the verification device;  After receiving the request message, the verification device sends a response message containing verification information corresponding to the pairing key saved by the verification device to the mobile terminal.  28. The method according to claim 27, wherein the verification device is an electronic key or a user card inserted in a mobile terminal. 29. The method according to claim 12, further comprising after step b: if the mobile terminal determines that it is illegal, performing a lock service operation that stops responding to a user operation. 30. The method according to claim 29, after performing the lock service operation, further comprising: the mobile terminal playing voice information indicating that the identity of the user is illegal, or sending a notification message indicating that the identity of the user is illegal to the communication network.  31. The method according to claim 12, wherein step a further comprises the step of the mobile terminal sending the pairing key of the key to the verification device, and the verification device saves the pairing key, or further comprises the mobile terminal transmitting the key Sending to the verification device, the verification device generates a pairing key based on the key and saves the pairing key.  32. The method according to claim 12, wherein the mobile terminal is one of a mobile phone or a personal digital assistant (PDA), a portable computer, and a desktop computer that can be directly or indirectly connected to a mobile communication network.  33. The method according to claim 1, wherein the first device is a computer device, the second device is a server device, and step b includes:  The computer device sends a request message to the server device to obtain authentication information corresponding to the corresponding pairing key of the computer device;  After receiving the request message, the server device sends verification information corresponding to the corresponding pairing key of the computer device to the computer device;  The computer device verifies its legitimacy by comparing whether the verification information matches the verification information corresponding to the key stored in itself.  34. The method according to claim 33, wherein the server device is a password management server, and after verifying the legitimacy, further comprising: if it is judged that it is legal, the computer device enters a normal use state or performs an open special function operation.  35. The method according to claim 1, wherein the key stored by the first device and the pairing key stored by the second device are a pair of symmetric keys. 36. The method according to claim 35, wherein the key is the same as the pairing key, and in step c, the judging the key stored by the first device and the phase stored by the second device is determined. Whether the pairing key should match is to determine whether the verification information corresponding to the key held by the first device and the verification information corresponding to the corresponding pairing key held by the second device are the same.  37. The method according to claim 35, wherein the pairing key is obtained by performing a predetermined calculation on the key, and step c further comprises the first device performing the predetermined calculation on the key. To obtain a calculated value, and determining whether the key stored in the first device and the corresponding pairing key stored in the second device match is to determine the calculation information corresponding to the calculated value of the first device and the corresponding pairing stored in the second device Whether the key calculation information is the same.  38. The method according to claim 35, further comprising storing a correspondence between a key and a pairing key in the first device, and step c further comprising the first device corresponding to a key stored in itself. Performing a calculation corresponding to the calculation of the pairing key of the second device to obtain a calculated value, and determining whether the key stored by the first device and the corresponding pairing key stored by the second device match is determining the verification information of the first device Whether the eyelid identification information corresponding to the corresponding pairing key stored by the second device is the same.  39. The method according to any one of claims 36 to 38, wherein the verification information is verification information obtained by performing an encryption calculation or a decryption operation or a digest calculation on a key or a paired key.  40. The method according to claim 1, wherein the key stored by the first device and the pairing key stored by the second device are a pair of asymmetric keys.  41. The method according to claim 40, wherein the key stored by the first device is a private key, and the pairing key stored by the second device is a corresponding public key, and step b includes: The second device sends a random number, and the second device performs encryption calculation on the random number using a corresponding pairing key corresponding to the first device to obtain a ciphertext of the random number, and sends the ciphertext of the random number to the first device; Step c further includes: when the first device obtains the random number from the second device, After the ciphertext, the ciphertext is decrypted by using a key saved by the ciphertext to obtain a plaintext. The judgment of whether the key and the pairing key match in step C is to judge whether the plaintext and the random number are the same.  42. The method according to claim 1, further comprising the step of setting a verification switch indicating whether to perform legality verification in advance in the first device, and before step b, further comprising: determining by the first device: Whether the value of the verification switch indicates that legality verification is performed, and if yes, perform step 1? Otherwise, directly determine that it is legal.  43. The method according to claim 1, further comprising the steps of performing a maintenance operation on the verification information stored in the first device, and further setting a maintenance operation password before the maintenance operation; The verification information of a device before the maintenance operation further includes:  The user is prompted to enter the maintenance operation password, and judge whether the maintenance operation password entered by the user is correct. If the maintenance operation password is correct, perform maintenance operations on the verification information of the first device, otherwise no maintenance operations are performed. .  44. The method according to claim 43, wherein the verification information is a key or verification switch information indicating whether to perform legality verification; and the maintenance operations are initializing a key, deleting a key, and modifying a key. , View the key, turn on the verification switch, turn off the verification switch, and view the status of the risk switch, or any combination.  45. The method according to claim 1, wherein the first device executes step b immediately after reaching a special state, or executes step b after a random time or a predetermined time has passed after reaching a special state.  46. The method according to claim 45, wherein the special state is that the first device is started, or the first device is connected to the second device, or a preset period of time for certificate verification is reached. 47. The method of claim 1, further comprising: First set a prescribed verification operation response time. In step C, if the verification operation is not completed within the prescribed verification operation response time, the first device directly determines that it is illegal or judges that the verification operation has failed and restarts the verification operation.  48. The method according to claim 1, further comprising setting a predetermined verification operation end time or verification operation allowable number of times in advance, and in step c, if the first device is within the prescribed verification operation end time If the number of times allowed by the verification operation does not pass the verification, it is directly determined that it is illegal.  49. The method of claim 1, wherein the second device is independent of the first device.