WO2006024224A1 - A method for the safe protecting of the user card - Google Patents

A method for the safe protecting of the user card Download PDF

Info

Publication number
WO2006024224A1
WO2006024224A1 PCT/CN2005/001344 CN2005001344W WO2006024224A1 WO 2006024224 A1 WO2006024224 A1 WO 2006024224A1 CN 2005001344 W CN2005001344 W CN 2005001344W WO 2006024224 A1 WO2006024224 A1 WO 2006024224A1
Authority
WO
WIPO (PCT)
Prior art keywords
user card
authentication
terminal
authentication number
verification device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2005/001344
Other languages
English (en)
French (fr)
Inventor
Zhengwei Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=35999701&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2006024224(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP05781777A priority Critical patent/EP1737201A4/en
Publication of WO2006024224A1 publication Critical patent/WO2006024224A1/zh
Priority to US11/553,825 priority patent/US7650139B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
    • G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/409—Device specific authentication in transaction processing
    • G06Q20/4097—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners
    • G06Q20/40975—Device specific authentication in transaction processing using mutual authentication between devices and transaction partners using encryption therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2129—Authenticate client device independently of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the invention relates to an information security technology, and in particular relates to a security guarantee method for a user card. Background of the invention
  • a user card such as a SIM card in a mobile terminal
  • HN code information access to a user card
  • the access to the user card will be protected by the PIN code, that is, after the PI code is usually encountered, the mobile phone prompts the user to input the PIN code, and then the normal boot is the same.
  • the user is required to enter the PIN code each time the phone is turned on, which is difficult for the user to accept. Therefore, most users currently do not set a PIN code.
  • the main object of the present invention is to provide a security method for a user card, which ensures the security of the user card and makes it more usable, so that the mobile terminal user can conveniently and safely use the user. card.
  • a security method for a user card includes at least the following steps:
  • the user card authenticates the verification device according to the set security key before responding to the relevant access request; if the authentication passes, the relevant access request is allowed, otherwise the relevant access request is rejected.
  • Step b: authenticating the verification device according to the set security key includes:
  • the first calculation result and the second calculation result are obtained by the user card and the verification device respectively according to the security key;
  • the user card compares whether the first calculation result and the second calculation result are consistent. If the agreement is the same, the authentication passes; otherwise, the authentication fails.
  • the step bl l further includes: generating a first authentication number
  • Step bl l is performed by the user card and the verification device respectively according to the security key to obtain the first calculation result and the second calculation result: the user card and the verification device respectively calculate according to the security key and the first authentication number. The first calculation result and the second calculation result.
  • the first authentication number is generated by the user card and sent to the verification device.
  • the step bl l further includes: the verification device generates a second authentication number, and sends the user card to the user card;
  • Step bl l is performed by the user card and the verification device respectively according to the security key, and the first calculation result and the second calculation result are: the user card and the verification device respectively according to the security key, the first authentication number, and the second The number of authentications is calculated to obtain the first calculation result and the second calculation result.
  • the first authentication number is generated by the verification device and sent to the user card
  • the step M l further includes: the user card determines whether the first authentication number is illegal, and if it is illegal, the authentication fails, otherwise, step bl l and subsequent steps are performed.
  • the user card determines whether the first authentication number is legal: determining whether the first authentication number is greater than the first authentication number when the previous authentication succeeds; if it is greater than, it is legal, otherwise, it is illegal.
  • the first authentication number is a random number.
  • the step b11 further includes: the user card sends the first authentication number saved or generated by the user card to the verification device, and the verification device generates a second authentication number according to the received first authentication number, and the second authentication is performed. The number is sent to the user card;
  • step b11 the user card and the verification device respectively calculate the first calculation result and the second calculation result according to the security key: the user card and the face card device respectively calculate according to the security key and the second authentication number. The first calculation result and the second calculation result.
  • the method further includes: determining, by the user card, whether the second authentication number is legal, if not, the authentication fails, otherwise, performing step b l l and subsequent steps.
  • the method further includes: the user card saves the second authentication number sent by the verification device when the authentication device passes the authentication;
  • Determining, by the user card, whether the second authentication number is legal determining that the second authentication number currently received is greater than the second authentication number saved when the authentication device passes the last authentication, and if yes, confirming that the data is valid, otherwise, confirming illegal.
  • the first authentication number is a second authentication number sent by the verification device that is saved when the authentication device is successfully authenticated by the user card, and the verification device sends the newly generated second authentication number to the user card. Further includes:
  • the verification device After the verification device generates a new second authentication number, it is determined whether the newly generated second authentication number is greater than the first authentication number sent by the user card. If it is greater than, the confirmation is legal, and then the second generation is newly generated. The step of transmitting the authentication number to the user card; otherwise, confirming the illegality, and ending the processing flow or regenerating the new second authentication number and re-verifying the validity of the newly generated second authentication number.
  • the verification device is a terminal, an electronic key, a home location register, an authentication center, or a device identification register.
  • the verification device is an electronic key;
  • the method further includes: respectively setting a wireless transceiver module in the mobile terminal and the electronic key, the mobile terminal and the electronic key establish a wireless communication connection through the set wireless transceiver module, and the mobile terminal transmits the user card and the electronic key through the wireless communication connection The interaction between the two.
  • the method or method further includes: respectively setting a data communication line interface in the mobile terminal and the electronic key, the mobile terminal and the electronic key establish a wired communication connection by connecting a data communication line between the two interfaces, and the mobile terminal passes the cable
  • the communication connection transmits the interaction information between the user card and the electronic key.
  • the verification device is a terminal
  • step b before the terminal responds to the authentication request of the user card, the terminal further includes: determining its legality, and if it is legal, responding to the authentication request, otherwise, rejecting the authentication request.
  • the method further includes: storing a terminal security key in the terminal and the network side related device or in a terminal electronic key, and the terminal determines that the legality of the terminal is: the terminal according to the terminal security key to the network side related device or The terminal electronic key is authenticated. If the authentication is passed, it is judged that it is legal. Otherwise, it is judged that it is illegal.
  • the terminal performs authentication according to the terminal security key, including:
  • the terminal generates a random number and then sends it to the network side related device or the terminal electronic key; the network side related device or the terminal electronic key calculates according to the random number and the terminal security key saved by itself, and obtains a calculation result, and then the calculation result is obtained.
  • the terminal performs corresponding calculation according to the random number and the service key saved by itself, and obtains a calculation result, and compares the calculated result with the calculation result from the network side related device or the terminal electronic key, if consistent , the certification is passed; otherwise the certification does not pass.
  • step a the verification device saves the security key of the user card according to the identification information of the user card; before step bl 1 further includes: the verification device obtains the identifier of the user card requesting the authentication Information, and according to the identification information of the user card, determine the corresponding security key that is saved and participates in the current calculation.
  • the identification information of the user card is a card number of the user card, or a personalized information identifier generated by the user for the user card.
  • Step b The related access request includes: an access request for the information material saved by the user card, or an operation access to the network service setting data in the user card, or a request for performing a corresponding summary calculation or encryption and decryption calculation.
  • the present invention first sets a security key in the user card, sets the verification device, and saves the security key to a verification device; before the user card responds to the relevant access request, according to the setting
  • the security key authenticates the authentication device; if the authentication passes, the relevant access request is allowed, otherwise the relevant access request is rejected.
  • the verification device here may be a mobile terminal, so that after the user card is set to the security protection function, when the user card is inserted into another illegal terminal, the user card cannot be relatedly accessed because the authentication fails, thus ensuring the access.
  • User card security When the user card is inserted into the legal terminal, since the authentication can be passed, the user card can be directly accessed, so that the user can access the user card without inputting the PIN code, thereby facilitating the user's use.
  • the authentication of the verification device by the user card in the invention ensures the security of the user card, facilitates the use of the user, improves the available line of the user card, and thus solves the problem because the user is unwilling to input the PIN code. And the user card security issue.
  • Figure 1 is a general flow chart of the present invention
  • Figure 2 is a flow chart of the first embodiment of the present invention.
  • Figure 3 is a flow chart of a second embodiment of the present invention.
  • FIG. 4 is a flow chart of a third embodiment of the present invention
  • FIG. 5 is a flow chart of an embodiment of the terminal device of the present invention verifying its legitimacy. Mode for carrying out the invention
  • the invention sets a security key on the user card, sets the verification device, and saves the security key to an authentication device; the user card authenticates the verification device according to the set security key before responding to the relevant access request; Pass, allow related access requests, otherwise reject related access requests.
  • FIG. 1 is a general flow chart of the present invention. As shown in FIG. 1, the present invention includes at least the following steps:
  • Step Sl Set a security key in the user card.
  • the security key can be generated by the user card according to the root key and a random number, for example, by performing a digest operation, wherein the random number can be generated by the mobile terminal.
  • the security key can be directly a random number generated by the mobile terminal or a random value entered by the user.
  • the terminal prompts the user to input the PIN code of the user card, and then sets the randomly generated security key to the user card according to the user card PIN code input by the user.
  • Step S2 Set the verification device, and save the security key to the verification device.
  • the authentication device here may be the terminal itself, an electronic key, or a device on the network side, such as a home location register (HLR), an authentication center (AC), and an equipment identification register (EIR).
  • HLR home location register
  • AC authentication center
  • EIR equipment identification register
  • the terminal can directly save the security key.
  • the verification device is an electronic key
  • a wireless transceiver module is respectively disposed in the mobile terminal and the electronic key, and the mobile terminal and the electronic key establish a wireless communication connection through the wireless transceiver module, and the mobile terminal transmits the user card and the electronic device through the wireless communication connection Interaction letter between keys
  • the mobile terminal can set the security key to the electronic key through the wireless communication connection.
  • the wireless communication connection can be established by communication techniques such as infrared or basketball.
  • a data communication line interface may also be respectively disposed in the mobile terminal and the electronic key, and the mobile terminal and the electronic key establish a wired communication connection by connecting a data communication line between the two interfaces, and the mobile terminal is connected through the wired communication. Transmitting interaction information between the user card and the electronic key.
  • the terminal and the authentication device can exchange information through a short message or an OTA (Over The Air) interface, or a service operation command (such as setting a call forwarding command or viewing a call forwarding status command).
  • OTA Over The Air
  • service operation command such as setting a call forwarding command or viewing a call forwarding status command.
  • information can also be exchanged through other signaling methods.
  • Step S3 Before the user card responds to the related access request, the authentication device is authenticated according to the set security key. If the authentication is passed, step S4 is performed to permit the related access request. Otherwise, step S5 is performed to reject the related access request.
  • the relevant access request here may be an access request for the information material saved by the user card, for example, viewing the directory record saved by the user card, viewing the short message saved by the user card, and the like. Or operational access to data on network service settings in the user card, such as some custom service setup data for the operator. Or perform a corresponding digest calculation or a request for cryptographic calculation, for example, the terminal sends a random number to the user card, and the user card performs a digest operation on the random number according to the root key saved by itself, and returns the calculated digest value to the terminal. Operation.
  • the user card can authenticate the authentication device according to the set security key. For example, the security key saved by the verification device can be directly returned to the user card, and the user card compares the security key from the verification device and saves it by itself. Whether the security keys are consistent. If they are consistent, the authentication is passed. Otherwise, the authentication fails.
  • the verification device may perform a correlation calculation according to the security key to obtain a second calculation result, and return the second calculation result to the user card, and the user card also performs corresponding calculation according to the security key. Calculate, get the first calculation result. Then, the user card determines whether the authentication of the verification device passes by comparing whether the first calculation result and the second calculation result are consistent. That is, if they match, the authentication passes, otherwise, the authentication fails.
  • the calculation here can be a summary calculation.
  • the related digest algorithm can be found in the book "Application Cryptography". It can also refer to the relevant security standards for mobile communication. It is not described in detail here. Of course, it can also be an encryption calculation.
  • an authentication number may also be generated, where the digest calculation is performed according to the security key and the authentication number, that is, the first A calculation result and a second calculation result are obtained by the user card and the verification device respectively performing a corresponding digest calculation according to the security key and the authentication number saved by the user card.
  • the number of authentications here can actually be a random number.
  • the authentication number is generated by the user card and transmitted to the verification device.
  • the verification device is a terminal.
  • Step Sl l Set a security key in the user card; and save the security key to the terminal.
  • Step S12 The terminal sends the related access request to the user card.
  • Step S13 After receiving the relevant access request, the user card generates a first authentication number, and returns the first authentication number to the terminal.
  • Step S14 The terminal performs digest calculation according to the first authentication number returned by the user card and the security key saved by the user, obtains a second calculation result, and returns the second calculation result to the user card.
  • Step S15 After receiving the second calculation result returned by the terminal, the user card performs digest calculation according to the first authentication number and the saved security key to obtain the first calculation result.
  • Step S16 The user card determines whether the first calculation result and the second calculation result are consistent. If they are consistent, the terminal is allowed to perform related access to the user card in step S17; otherwise, if not, the terminal is not allowed to perform related access to the user card in step S18.
  • the above authentication number may also be generated by the verification device and transmitted to the user card.
  • the user card may further determine the validity of the authentication number generated by the verification device, so as to prevent the attacker from attacking the user card by using the illegal authentication number. If the number of authentications generated by the verification device is invalid, the authentication for the verification device fails. If the authentication is valid, the digest calculation is performed.
  • the object of the present invention can also be achieved, but it is obvious that the security is not very high.
  • FIG. 3 it is a flowchart of a second embodiment of the present invention, in which the authentication device generates an authentication number, and the user card verifies the authentication number. And in this embodiment, the verification device is a terminal.
  • Step S21 setting a security key in the user card; and saving the security key to the terminal;
  • Step S22 The terminal generates a second authentication number, performs digest calculation according to the second authentication number and the security key saved by itself, to obtain a second calculation result, and the terminal sends the related access request to the user card, where the related access request is carried.
  • Step S23 After receiving the relevant access request, the user card determines that the request information carries the legality of the second authentication number. If it is illegal, step S27 is performed to end the processing; otherwise, the following step S24 is continued; the user card passes the request The information carries the validity of the second authentication number to judge, which can avoid message replay attacks.
  • Step S24 The user card performs a digest calculation according to the second authentication number and the security key saved by itself, to obtain a first calculation result;
  • Step S25 The user card determines whether the first calculation result and the second calculation result are consistent. If they are consistent, in step S26, the terminal is allowed to perform related access to the user card; otherwise, If the values are inconsistent, the terminal is not allowed to perform related access to the user card in step S27.
  • the validity of the user card for the second authentication number in step S23 can be determined by repeatability. That is, the repeatability of the authentication number generated by the verification device is judged, so that the attacker can effectively prevent the attacker from using the same authentication number or the used authentication number to perform a message replay attack on the user card. For example, when a repetitive judgment is made, the user card can save the number of authentications generated by the verification device and sent to itself when the previous authentication succeeds.
  • this authentication it is determined whether the authentication number generated by the verification device is greater than or The number of authentications generated by the verification device when the previous authentication succeeds is saved by itself, where the judgment is greater than whether the number of authentications is required to be incremented, and whether the number of authentications is required to be decremented is determined to be less than .
  • the number of authentications generated by the verification device may be required to be incremented or decremented.
  • the user card can save the authentication number generated by the verification device when the authentication succeeds, so that the second authentication number newly generated by the verification device is determined by the authentication number when the next authentication is performed. is it legal.
  • the verification device may first authenticate the second authentication number generated by itself, specifically The user card saves the second authentication number corresponding to the current authentication when the verification of the verification device is successful. On the next authentication, the user card sends the saved second authentication number to the verification device, and the verification device is generating a new one.
  • the validity of the newly generated second authentication number is determined according to the second authentication number transmitted by the user card, so as to ensure that the newly generated second authentication number can be verified by the user card, for example If the number of authentications generated by the user card requesting the verification device is incrementally generated, after the verification device generates an authentication number, the second authentication number is determined. If yes, the authentication number is used to perform the current authentication. Otherwise, the verification device regenerates a new second authentication number and re-verifies whether the newly generated second authentication number is greater than A second authentication number that satisfies the requirements is generated.
  • the increment or decrement random number generation function can be utilized to generate an increment or decrement sequence of authentication numbers.
  • the first authentication number saved or generated by the user card may be sent to the verification device by the user card, and the verification device is based on the received first authentication.
  • the weight produces a second authentication number.
  • the first authentication number sent by the user card to the verification device may be sent to the user card by another device such as the verification device, or may be actively generated by the user card itself.
  • the user card may be other according to the user card.
  • the information sent by the device is generated.
  • the first authentication number may be generated by the user card
  • the second authentication number is generated by the verification device
  • the digest calculation may be based on the first authentication number, the second authentication number, and the security key.
  • the first calculation result and the second calculation result are functions of the first authentication number, the second authentication number, and the security key.
  • the verification device is a terminal.
  • Step S3 Set a security key in the user card; and save the security key to the terminal;
  • Step S32 The terminal generates a second authentication number, and sends a related access request to the user card, where the request carries the generated second authentication number;
  • Step S33 After receiving the relevant access request, the user card generates a first authentication number, and returns the first authentication number to the terminal.
  • Step S34 The terminal performs digest calculation according to the first authentication number returned by the user card, the second authentication number generated by itself, and the security key saved by itself, to obtain a second calculation result, and return the second calculation result to the user card. ;
  • Step S35 After receiving the second calculation result returned by the terminal, the user card is based on the first The first calculation result is obtained by performing a digest calculation on the weight, the second authentication number, and the security key saved by itself;
  • Step S36 The user card determines whether the first calculation result and the second calculation result are consistent. If they are consistent, the terminal is allowed to perform related access to the user card in step S37; otherwise, if not, in step S38, the terminal is not allowed to The user card enters 4 related accesses.
  • the user card and the verification device perform digest calculation using the first authentication number, the second authentication number, and the security key, the first authentication number, the second authentication number, the security key, and the like are performed. If any one of the three is different, the first calculation result and the second calculation result may be different, and the authentication of the verification device by the user card may not be passed. In this way, the user card can easily generate the first authentication number, for example, a sequence of natural numbers or a sequence of random increments, thereby avoiding message replay attacks such as repetitive attacks without increasing the number of user cards.
  • the computational complexity of the authentication number; and then, according to the verification device, a random number of authentication numbers can be generated to prevent the attacker from attacking the security key by using the regularity of a single authentication number.
  • the security key of the user card may also be saved according to the identification information of the user card, so that when the user card authenticates the security card device, the verification device acquires the identification information of the user card requesting the authentication, and the The identification information of the user card determines the corresponding security key saved by itself, and then performs corresponding digest calculation according to the security key to obtain the second calculation result described above.
  • the identification information of the user card here is the card number of the user card, or the personalized information identifier generated by the user for the user card.
  • the verification device is a terminal or an electronic key
  • the user card can be named as a communication card or a mobile card. This is convenient for dual-card phones, or where a user often uses more than two cards to replace one or more cards.
  • the terminals in the above first to third embodiments may also be other verification devices.
  • the verification device can also determine its legality before responding to the authentication request of the user card. If it is legal, it responds to the authentication request of the user card, otherwise it rejects the authentication request.
  • a terminal security key may be stored in the terminal and the network side related device or in the terminal electronic key, and the terminal may pair the related network side device or the terminal electronic according to the terminal security key saved by the terminal.
  • the key is authenticated to judge its legality. If the authentication passes, it judges that it is legal. Otherwise, it judges that it is illegal.
  • the network side device here can be HLR, AC or EIR.
  • FIG. 5 it is a flow chart of an embodiment of the terminal of the present invention for judging its own legitimacy. As can be seen from the figure, the following steps are included:
  • Step S110 Separate the terminal security key in the terminal and the network side related device respectively;
  • Step S120 The terminal generates a random number, and then sends the data to the network side related device;
  • Step S130 The network side related device saves according to the random number and the self.
  • the terminal security key is calculated, and a calculation result is obtained, and then the calculation result is returned to the terminal;
  • Step S140 The terminal performs corresponding calculation according to the random number and the terminal security key saved by itself, to obtain a calculation result;
  • Step S150 The terminal compares the calculated result with the calculation result from the related device on the network side. If they are consistent, the authentication passes, otherwise the authentication fails.
  • the network side related device may also be replaced by a terminal electronic key, that is, a terminal security key may be stored in the terminal electronic key.
  • a terminal security key may be stored in the terminal electronic key.
  • the corresponding steps S120 and S130 are performed.
  • the network side related device in S150 is a terminal electronic key.
  • the user card may be a SIM card in a GSM network or a UIM card in a CDMA network. Of course, it can also be other user identification modules, or modules having such functions.
  • the terminal in the present invention may be a mobile terminal such as a mobile phone, a PDA, or other portable device, and the like. Therefore, it is to be understood that the foregoing is only the preferred embodiment of the present invention, and is not intended to limit the invention, and any modifications, equivalents, improvements, etc., which are included within the spirit and principles of the present invention, should be included It is within the scope of the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Storage Device Security (AREA)
  • Telephone Function (AREA)

Description

一种用户卡的安全保障方法
技术领域
本发明涉及信息安全技术 , 具体涉及一种用户卡的安全保障方法。 发明背景
目前, 移动终端中诸如 SIM卡之类的用户卡的信息存取是通过 HN 码来进行保护的。 具体来说, 当用户设置了用户卡的 PIN码后, 对用户 卡的访问将通过 PIN码保护, 也即通常所遇到的设置 PI 码后, 手机提 示用户输入 PIN码, 而后才能正常开机一样。 每次访问用户卡, 即每次开机都要让用户输入 PIN码, 则难以被广大用 户接受。 因此, 目前的绝大多数用户都不设置 PIN码。 基于这种原因, 事实上, 目前的用户卡 PIN码对用户卡的安全保护起不到应有的作用, 因为没有人或很少人愿意用, 就等于没有用, 正如再严谨的制度和法律 条文必须具有其可操作性一样。 发明内容
有鉴于此, 本发明的主要目的是提供一种用户卡的安全保障方法, 在保证用户卡的安全性同时, 使得其具有更好易用性, 从而使得移动终 端用户可以方便安全地使用其用户卡。
本发明的上述目的是通过如下的技术方案予以实现的:
一种用户卡的安全保障方法, 至少包括如下步骤:
a. 在用户卡中设置一个安全密钥; 设置一个验证设备, 并将安全密 钥保存在验证设备中;
b. 用户卡在响应相关访问请求前, 根据设置的安全密钥对验证设备 进行认证; 如果认证通过, 允许相关访问请求, 否则拒绝相关访问请求。
步骤 b所述根据设置的安全密钥对验证设备进行认证包括:
bl l . 由用户卡和验证设备分别根据安全密钥进行计算得到第一计 算结果和第二计算结果;
bl2. 用户卡比较第一计算结果和第二计算结果是否一致, 如果一 致, 则认证通过; 否则, 认证不通过。
步骤 bl l之前进一步包括: 产生第一鉴权数;
步骤 bl l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和验证设备分别根据安全密 钥和第一鉴权数进行计算得到第一计算结果和第二计算结果。
所述第一鉴权数由用户卡产生, 并发送给验证设备。
步骤 bl l之前进一步包括: 验证设备产生第二鉴权数, 并^送给用 户卡;
步骤 bl l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和验证设备分别根据安全密 钥、 第一鉴权数和第二鉴权数进行计算得到第 计算结果和第二计算结 果。
所述第一鉴权数由验证设备产生, 并发送给用户卡;
步骤 M l之前进一步包括: 用户卡判断第一鉴权数是否非法, 如果 非法, 则鉴权不通过, 否则, 执行步骤 bl l及其以后步骤。
用户卡判断第一鉴权数是否合法为: 通过判断该第一鉴权数是否大 于上次认证成功时的第一鉴权数来判断其合法性; 如果大于则合法, 否 则, 非法。 所述第一鉴权数是一个随机数。
步骤 b l l之前进一步包括: 用户卡将自身保存或生成的第一鉴权数 发送给验证设备, 验证设备根据收到的第一鉴权数产生第二鉴权数, 并 将所述第二鉴权数发送给用户卡;
步骤 b l l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和脸证设备分别根据安全密 钥和第二鉴权数进行计算得到第一计算结果和第二计算结果。
步骤 b l l之前, 进一步包括: 用户卡判断第二鉴权数是否合法, 如 果不合法, 则鉴权不通过, 否则, 执行步骤 b l l及其以后步骤。
该方法进一步包括: 用户卡在对验证设备认证通过时保存验证设备 发送来的第二鉴权数;
所述用户卡判断第二鉴权数是否合法为: 判断当前收到的第二鉴权 数大于上次对验证设备认证通过时保存的第二鉴权数, 如果大于则确认 合法, 否则, 确认非法。
所述第一鉴权数是用户卡上一次对验证设备认证成功时保存的验证 设备发送的第二鉴权数, 所述验证设备在将新产生的第二鉴权数发送给 用户卡之前, 进一步包括:
验证设备在产生新的第二鉴权数后, 判断新产生的第二鉴权数是否 大于用户卡发送来的第一鉴权数, 如果大于, 则确认合法, 之后执行将 新产生的第二鉴权数发送给用户卡的步骤; 否则确认非法, 并结束本处 理流程或重新产生新的第二鉴权数并重新验证新产生的第二鉴权数的 合法性。
所述验证设备是终端、 电子钥匙、 归属位置寄存器、 鉴权中心或设 备标识寄存器。
所述验证设备是电子钥匙; 该方法进一步包括: 在移动终端和电子钥匙中分别设置一个无线收 发模块, 移动终端和电子钥匙通过所设置的无线收发模块建立无线通信 连接, 移动终端通过该无线通信连接传送用户卡和电子钥匙之间的交互 §息。
该方法或者进一步包括: 在移动终端和电子钥匙中分别设置一个数 据通信线接口, 移动终端和电子钥匙通过连接在所述两个接口之间的数 据通信线建立有线通信连接, 移动终端通过该有线通信连接传送用户卡 和电子钥匙之间的交互信息。
所述验证设备是终端;
步骤 b中, 所述终端在响应用户卡的认证请求之前, 进一步包括: 判断自己的合法性, 如果合法, 则响应该认证请求, 否则, 拒绝该认证 请求。
所述方法进一步包括: 在终端和网络侧相关设备中或者是一个终端 电子钥匙中保存一个终端安全密钥, 所述终端判断自己的合法性为: 终端根据终端安全密钥对网络侧相关设备或终端电子钥匙进行认 证, 如果认证通过, 则判断自己合法, 否则, 判断自己非法。
所述终端根据终端安全密钥进行认证包括:
终端产生一个随机数,然后发送给网络侧相关设备或终端电子钥匙; 网络侧相关设备或终端电子钥匙根据随机数和自己保存的终端安全 密钥进行计算, 得到一个计算结果, 然后将该计算结果返回给终端; 终端根据随机数和自己保存的业务密钥进行相应的计算, 得到一个 计算结果, 并比较自己计算得到的结果和来自网络侧相关设备或终端电 子钥匙的计算结果是否一致, 如果一致, 则认证通过; 否则认证不通过。
步骤 a中,验证设备根据用户卡的标识信息保存用户卡的安全密钥; 步骤 bl 1之前进一步包括: 验证设备获取请求认证的用户卡的标识 信息, 并根据该用户卡的标识信息确定自己保存的、 且参与本次计算的 相应安全密钥。
所述用户卡的标识信息是用户卡的卡号, 或者是用户为用户卡生成 的个性化信息标识。
步骤 b所述相关访问请求包括: 对用户卡保存的信息资料的访问请 求, 或对用户卡中网络业务设置数据的操作访问, 或执行相应的摘要计 算或加解密计算的请求。
从本发明的技术方案可以看出, 本发明首先在用户卡中设置一个安 全密钥, 设置验证设备, 并将该安全密钥保存到一个验证设备; 用户卡 在响应相关访问请求前, 根据设置的安全密钥对验证设备进行认证; 如 果认证通过, 允许相关访问请求, 否则拒绝相关访问请求。 这里的验证 设备可以是移动终端, 这样, 在用户卡设置了安全防护功能后, 将该用 户卡插入其它非法终端时, 会因为认证不通过而无法对用户卡进行相关 的访问,这样就保证了用户卡的安全。而将用户卡插入合法的终端中时, 由于认证能够通过, 因此, 就可以直接对用户卡进行访问, 这样, 用户 不需要输入 PIN码即可以访问用户卡, 因此方便了用户使用。
可以看出, 本发明中通过用户卡对验证设备的认证, 在保证用户卡 安全性的同时, 方便了用户的使用, 提高了用户卡的可用行, 从而, 解 决了因为用户不愿意输入 PIN码而带来的用户卡安全性问题。 附图简要说明
图 1是本发明的总体流程图;
图 2是本发明第一实施例的流程图;
图 3是本发明第二实施例的流程图;
:图 4是本发明第三实施例的流程图; 图 5是本发明终端设备验证其合法性的实施例流程图。 实施本发明的方式
下面结合附图和具体实施例对本发明进行详细说明。
本发明在用户卡设置一个安全密钥, 设置验证设备, 并将该安全密 钥保存到一个验证设备; 用户卡在响应相关访问请求前, 根据设置的安 全密钥对验证设备进行认证; 如果认证通过, 允许相关访问请求, 否则 拒绝相关访问请求。
图 1是本发明的总体流程图。 如图 1所示, 本发明至少包括如下步 骤:
步骤 Sl、 在用户卡中设置一个安全密钥。
这里的安全密钥可以由用户卡根据其中的根密钥, 和一个随机数进 行一定的运算, 比如进行摘要运算产生, 其中, 随机数可以由移动终端 产生。 当然, 安全密钥可以直接是由移动终端产生的一个随机数, 或者 是用户输入的一个随机值。 比如, 终端提示用户输入用户卡的 PIN码, 而后, 根据用户所输入的用户卡 PIN码, 将随机产生的安全密钥设置到 用户卡中。
步骤 S2、 设置验证设备, 并将该安全密钥保存到验证设备中。 这里的验证设备可以是终端本身, 也可以是一个电子钥匙, 也可以 是网络侧的一个设备, 如归属位置寄存器(HLR )、 鉴权中心(AC )、 和 设备标识寄存器 (EIR ) 等。
如果验证设备是终端本身, 则终端可以直接保存该安全密钥。 如果 验证设备是一个电子钥匙, 则在移动终端和电子钥匙中分别设置一个无 线收发模块, 移动终端和电子钥匙通过该无线收发模块建立无线通信连 接, 移动终端通过该无线通信连接传送用户卡和电子钥匙之间的交互信 息, 这时, 移动终端可以通过该无线通信连接, 将安全密钥设置到电子 钥匙。 所述无线通信连接可以通过红外线或篮牙等等通信技术建立。 当 然, 也可以在移动终端和电子钥匙中分别设置一个数据通信线接口, 移 动终端和电子钥匙通过连接在所述两个接口之间的数据通信线建立有 线通信连接, 移动终端通过该有线通信连接传送用户卡和电子钥匙之间 的交互信息。
如果验证设备是 HLR等网络设备,终端和该验证设备可以通过短消 息或者 OTA ( Over The Air )接口, 或业务操作命令(如设置呼叫转移 命令或查看呼叫转移状态命令)等进行信息交互。 当然, 也可以通过其 它信令方式进行信息交互。
步骤 S3、 用户卡在响应相关访问请求前, 根据设置的安全密钥对验 证设备进行认证; 如果认证通过, 则执行步骤 S4, 允许相关访问请求, 否则, 执行步骤 S5, 拒绝相关访问请求。
这里的相关访问请求可以是对用户卡保存的信息资料的访问请求, 比如, 查看用户卡保存的号码簿记录, 查看用户卡保存的短消息, 等等。 或对用户卡中关于网络业务设置的数据的操作访问, 比如, 运营商的一 些定制业务设置数据。 或执行相应的摘要计算或加解密计算的请求, 比 如, 终端发送给用户卡一个随机数, 用户卡根据自己保存的根密钥对该 随机数进行摘要运算, 并将计算的摘要值返回给终端的操作。
用户卡根据设置的安全密钥对验证设备进行认证的方式有很多, 比 如, 可以直接由验证设备将自己保存的安全密钥返回给用户卡, 用户卡 比较来自验证设备的安全密钥和自己保存的安全密钥是否一致, 如果一 致, 则认证通过, 否则, 认证不通过。
也可以是验证设备根据安全密钥进行相关计算得到第二计算结果, 并将第二计算结果返回给用户卡, 用户卡也根据安全密钥进行相应的计 算, 得到第一计算结果。 之后用户卡通过比较第一计算结果和第二计算 结果是否一致来判断对验证设备的认证是否通过。 即, 如果一致, 则认 证通过, 否则, 认证不通过。 这里的计算可以是摘要计算, 相关的摘要 算法参见 《应用密码学》 一书, 也可以参见移动通信的相关安全标准, 这里不详细叙述, 当然, 也可以是一个加密计算。
当然, 上述通过第一计算结果和第二计算结果进行判断的处理方案 中, 也可以产生一个鉴权数, 上述摘要计算则根据安全密钥和该鉴权数 共同进行摘要计算, 也即, 第一计算结果和第二计算结果是用户卡和验 证设备分别根据自己保存的安全密钥和鉴权数进行相应的摘要计算得 到。 这里的鉴权数实际上可以是一个随机数。
一般地, 在用户卡对验证设备进行认证时, 鉴权数是由用户卡产生 并传送给验证设备。
下面再结合附图及具体实施例对本发明方案做进一步详细的描述。 如图 2所示, 是本发明的第一实施例流程图, 本实施例中验证设备 是终端。
步骤 Sl l、 在用户卡中设置一个安全密钥; 并将该安全密钥保存到 终端。
步骤 S12、 终端将相关访问请求发送给用户卡;
步骤 S13、 用户卡接收到相关访问请求后, 产生第一鉴权数, 并将 第一鉴权数返回给终端。
步骤 S14、 终端根据用户卡返回的第一鉴权数和自己保存的安全密 钥进行摘要计算,得到第二计算结果,并将第二计算结果返回给用户卡。
步骤 S 15、 用户卡接收到终端返回的第二计算结果后, 也根据第一 鉴权数和自己保存的安全密钥进行摘要计算得到第一计算结果。
步骤 S16、用户卡判断上述第一计算结果和第二计算结果是否一致, 如果一致, 则在步骤 S 17 , 允许终端对用户卡进行相关访问; 否则, 如 果不一致, 则在步骤 S 18 , 不允许终端对用户卡进行相关访问。
上述鉴权数也可以是由验证设备产生并传送给用户卡。 这时, 用户 卡在进行所述的摘要计算并得到第一计算结果之前, 可以进一步对验证 设备产生的鉴权数进行合法性判断, 避免攻击者利用非法鉴权数对用户 卡进行攻击, 如果判断验证设备产生的鉴权数不合法, 则, 本次对于验 证设备的认证不通过, 如果合法, 才进行所述的摘要计算。 当然, 如果 用户卡不进行验证,也可以实现本发明的目的,但显然安全性不是很高。
如图 3所示, 是本发明的第二实施例流程图, 该实施例即通过验证 设备生成鉴权数, 并由用户卡对鉴权数进行验证。 且本实施例中验证设 备是终端。
步骤 S21、 在用户卡中设置一个安全密钥; 并将该安全密钥保存到 终端;
步骤 S22、 终端产生第二鉴权数, 根据第二鉴权数和自己保存的安 全密钥进行摘要计算, 得到第二计算结果; 终端将相关访问请求发送给 用户卡, 该相关访问请求中携带产生的第二鉴权数和计算得到的第二计 算结果;
步骤 S23、 用户卡接收到相关访问请求后, 判断请求信息中携带第 二鉴权数的合法性, 如果非法, 则执行步骤 S27 , 结束处理; 否则, 继 续执行如下步骤 S24; 用户卡通过对请求信息中携带第二鉴权数的合法 性进行判断, 可以避免消息重放攻击。
步骤 S24、 用户卡根据第二鉴权数和自己保存的安全密钥进行摘要 计算得到第一计算结果;
步骤 S25、用户卡判断上述第一计算结果和第二计算结果是否一致, 如果一致, 则在步骤 S26 , 允许终端对用户卡进行相关访问; 否则, 如 果不一致, 则在步骤 S27 , 不允许终端对用户卡进行相关访问; 上述步骤 S23中用户卡对于第二鉴权数的合法性判断, 可以采用重 复性判断来进行。 也即判断验证设备产生的鉴权数的重复性, 从而可以 有效地避免攻击者利用同一个鉴权数或者已经用过的鉴权数对用户卡 进行消息重放攻击。 比如, 要进行重复性判断时, 用户卡可以保存上一 次认证成功时由验证设备产生并发送给自己的鉴权数, 在本次认证时, 判断本次验证设备产生的鉴权数是否大于或小于自己保存的上一次认 证成功时由验证设备产生的所述鉴权数, 其中, 对于要求递增产生鉴权 数来说为判断是否大于, 对于要求递减产生鉴权数来说则是判断是否小 于。 这里, 可以要求验证设备产生的鉴权数是递增的或递减的。 这时, 用户卡在认证成功时, 可以保存本次认证成功时由验证设备产生的鉴权 数, 以便于下一次认证时, 以此鉴权数来判断验证设备新产生的第二鉴 权数是否合法。
当然, 用户卡在对验证设备进行认证之前, 也即验证设备在将新产 生的第二鉴权数发送给用户卡之前, 验证设备可以先对自身产生的第二 鉴权数进行认证, 具体来说, 用户卡在对验证设备验证成功时, 保存对 应于本次认证的第二鉴权数, 在下一次认证时, 用户卡将保存的第二鉴 权数发送给验证设备, 验证设备在产生新的第二鉴权数时, 根据用户卡 传送来的第二鉴权数判断新产生的第二鉴权数的合法性, 以保证新产生 的第二鉴权数能够通过用户卡的验证, 例如, 如果用户卡要求验证设备 产生的鉴权数是递增产生的, 那么, 验证设备产生一个鉴权数后, 判断 二鉴权数, 如果是, 则使用该鉴权数进行本次的鉴权, 否则, 验证设备 重新产生新的第二鉴权数并重新验证新产生的第二鉴权数是否大于用 备产生一个满足要求的第二鉴权数为止。 当然, 可以利用递增或递减随 机数产生函数来产生递增或递减鉴权数序列。
一般地, 在上述验证设备生成新的第二鉴权数的处理过程中, 是可 以由用户卡将自身保存或生成的第一鉴权数发送给验证设备, 验证设备 根据收到的第一鉴权数产生第二鉴权数。 其中, 用户卡发送给验证设备 的第一鉴权数, 可以是诸如验证设备之类的其它设备发送给用户卡的, 也可以是用户卡自身主动生成的, 当然, 还可以是用户卡根据其它设备 发送来的信息生成的。
实际当中, 也可以是由用户卡产生第一鉴权数, 由验证设备产生第 二鉴权数, 所述的摘要计算也可以是根据第一鉴权数, 第二鉴权数和安 全密钥联合进行的摘要计算。 这时, 第一计算结果和第二计算结果是第 一鉴权数, 第二鉴权数和安全密钥的函数。 其相应的实现过程如图 4所 示。
如图 4所示, 是本发明的第三实施例流程图, 本实施例中验证设备 是终端。
步骤 S3 1、 在用户卡中设置一个安全密钥; 并将该安全密钥保存到 终端;
步骤 S32、 终端产生第二鉴权数, 并将相关访问请求发送给用户卡, 请求中携带产生的第二鉴权数;
步骤 S33、 用户卡接收到相关访问请求后, 产生第一鉴权数, 并将 第一鉴权数返回给终端;
步骤 S34、 终端根据用户卡返回的第一鉴权数、 自己产生的第二鉴 权数和自己保存的安全密钥进行摘要计算, 得到第二计算结果, 并将第 二计算结果返回给用户卡;
步骤 S35、 用户卡接收到终端返回的第二计算结果后, 根据第一鉴 权数、 第二鉴权数和自己保存的安全密钥进行摘要计算得到第一计算结 果;
步骤 S36、用户卡判断上述第一计算结果和第二计算结果是否一致, 如果一致, 则在步骤 S37, 允许终端对用户卡进行相关访问; 否则, 如 果不一致, 则在步骤 S38, 不允许终端对用户卡进 4亍相关访问。
上述步骤 S34和 S35中, 用户卡和验证设备在利用第一鉴权数、 第 二鉴权数和安全密钥进行摘要计算时, 第一鉴权数、 第二鉴权数和安全 密钥等三者中, 有任意一个不同的话, 第一计算结果和第二计算结果就 有可能不同, 也就会导致用户卡对验证设备的认证不通过。 这样, 用户 卡可以很简单地产生第一鉴权数, 比如, 就是一个自然数序列, 或者一 个随机递增序列, 从而既可以避免重复性攻击等消息重放攻击, 又不会 增加用户卡产生第一鉴权数时的计算复杂度; 而后, 根据验证设备可以 产生一个随机性较高的鉴权数, 以防止攻击者可能利用单一鉴权数的规 律性对安全密钥进行攻击。
在验证设备中, 还可以根据用户卡的标识信息保存用户卡的安全密 钥, 这样, 在用户卡对 -险证设备进行认证时, 验证设备获取请求认证的 用户卡的标识信息, 并 居该用户卡的标识信息确定自己保存的相应安 全密钥, 而后根据该安全密钥进行相应的摘要计算以得到上述所述的第 二计算结果。
这里的用户卡的标识信息是用户卡的卡号, 或者是用户为用户卡生 成的个性化信息标识。 比如, 当验证设备是终端或电子钥匙时, 可以给 用户卡取名为联通卡, 移动卡。 这对于双卡手机, 或一个用户经常使用 一个手机更换使用两张以上卡的情况将非常方便。
当然, 上述第一至第三实施例中的终端也可以是其它验证设备。 验证设备还可以在响应用户卡的认证请求之前,判断自己的合法性, 如果合法, 则响应该用户卡的认证请求, 否则, 拒绝该认证请求。
实际当中, 对于验证设备是终端的情况, 可以在终端和网络侧相关 设备中或终端电子钥匙中保存一个终端安全密钥, 终端可以根据自己保 存的终端安全密钥对相关网络侧设备或终端电子钥匙进行认证来判断 自己的合法性, 如果认证通过, 则判断自己合法, 否则, 判断自己非法。 这里的网络侧设备可以是 HLR、 AC或 EIR。
如图 5所示, 是本发明的终端判断自己的合法性的一个实施例流程 图, 从图中可见, 包括如下步骤:
步骤 S110、 在终端和网络侧相关设备中分别保存终端安全密钥; 步骤 S120、 由终端产生一个随机数, 然后发送给网络侧相关设备; 步骤 S130、 网络侧相关设备根据随机数和自己保存的终端安全密钥 进行计算, 得到一个计算结果, 然后将该计算结果返回给终端;
步骤 S140、终端根据随机数和自己保存的终端安全密钥进行相应的 计算, 得到一个计算结果;
步骤 S150、终端比较自己计算得到的结果和来自网络侧相关设备的 计算结果是否一致, 如果一致, 则认证通过, 否则认证不通过。
上述步骤 S110中,所述网络侧相关设备也可以用一个终端电子钥匙 来代替, 即, 也可以是在终端电子钥匙中保存一个终端安全密钥, 后续 的实现步骤中, 相应的步骤 S120、 S130、 S150所述网络侧相关设备为 终端电子钥匙。
所述用户卡, 可以是 GSM网络中的 SIM卡或者 CDMA 网络中的 UIM卡。 当然, 也可以是其它用户标识模块, 或具有类似这种功能的模 块。
本发明中的终端可以是移动终端, 如手机, 也可以是 PDA, 也可以 是其它便携式设备, 等等。 因此可以理解, 以上所述仅为本发明的较佳实施例而已, 并不用以 限制本发明, 凡在本发明的精神和原则之内, 所作的任何修改、 等同替 换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、一种用户卡的安全保障方法,其特征在于,该方法包括如下步骤: a. 在用户卡中设置一个安全密钥; 设置一个验证设备, 并将安全密 钥保存在验证设备中;
b. 用户卡在响应相关访问请求前,根据设置的安全密钥对脸证设备 进行认证; 如果认证通过, 允许相关访问请求, 否则拒绝相关访问请求。
2、根据权利要求 1所述的用户卡的安全保障方法, 其特征是, 步骤 b所述根据设置的安全密钥对验证设备进行认证包括:
bl l. 由用户卡和验证设备分别根据安全密钥进行计算得到第一计 算结果和第二计算结果;
bl2. 用户卡比较第一计算结果和第二计算结果是否一致, 如果一 致, 则认证通过; 否则, 认证不通过。
3、根据权利要求 2所述的用户卡的安全保障方法, 其特征是, 步骤 bl l之前进一步包括: 产生第一鉴权数;
步骤 bl l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和验证设备分别根据安全密 钥和第一鉴权数进行计算得到第一计算结果和第二计算结果。
4、根据权利要求 3所述的用户卡安全保障方法, 其特征是, 所述第 一鉴权数由用户卡产生, 并发送给验证设备。
5、根据权利要求 4所述的用户卡的安全保障方法, 其特征是, 步骤 bl l之前进一步包括: 验证设备产生第二鉴权数, 并发送给用户卡; 步骤 bl l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和验证设备分别根据安全密 钥、 第一鉴权数和第二鉴权数进行计算得到第一计算结果和第二计算结 果。
6、根据权利要求 3所述的用户卡的安全保障方法, 其特征是, 所述 第一鉴权数由验证设备产生, 并发送给用户卡;
步骤 bl l之前进一步包括: 用户卡判断第一鉴权数是否非法, 如果 非法, 则鉴权不通过, 否则, 执行步骤 bl l及其以后步骤。
7、根据权利要求 6所述的用户卡的安全保障方法, 其特征是, 用户 卡判断第一鉴权数是否合法为: 通过判断该第一鉴权数是否大于上次认 证成功时的第一鉴权数来判断其合法性; 如果大于则合法, 否则, 非法。
8、 根据权利要求 3至 7中任意一项所述的用户卡的安全保障方法, 其特征是, 所述第一鉴权数是一个随机数。
9、根据权利要求 2所述的用户卡的安全保障方法, 其特征是, 步骤 bl l 之前进一步包括: 用户卡将自身保存或生成的第一鉴权数发送给验 证设备, 验证设备根据收到的第一鉴权数产生第二鉴权数, 并将所述第 二鉴权数发送给用户卡;
步骤 M l所述由用户卡和验证设备分别根据安全密钥进行计算得到 第一计算结果和第二计算结果为: 由用户卡和验证设备分别根据安全密 钥和第二鉴权数进行计算得到第一计算结果和第二计算结果。
10、 根据权利要求 9所述的用户卡的安全保障方法, 其特征是, 步 骤 bl l之前, 进一步包括: 用户卡判断第二鉴权数是否合法, 如果不合 法, 则鉴权不通过, 否则, 执行步骤 M l及其以后步骤。
11、根据权利要求 10所述的用户卡安全保障方法, 其特征是, 该方 法进一步包括: 用户卡在对验证设备认证通过时保存验证设备发送来的 第二鉴权数;
所述用户卡判断第二鉴权数是否合法为: 判断当前收到的第二鉴权 数大于上次对验证设备认证通过时保存的第二鉴权数, 如果大于则确认 合法, 否则, 确认非法。
12、 根据权利要求 9至 11中任意一项所述的用户卡安全保障方法, 其特征是, 所述第一鉴权数是用户卡上一次对验证设备认证成功时保存 的验证设备发送的第二鉴权数, 所述验证设备在将新产生的第二鉴权数 发送给用户卡之前, 进一步包括:
验证设备在产生新的第二鉴权数后, 判断新产生的第二鉴权数是否 大于用户卡发送来的第一鉴权数, 如果大于, 则确认合法, 之后执行将 新产生的第二鉴权数发送给用户卡的步骤; 否则确认非法, 并结束本处 理流程或重新产生新的第二鉴权数并重新验证新产生的第二鉴权数的 合法性。
13、 根据权利要求 1所述的用户卡的安全保障方法, 其特征是, 所 述验证设备是终端、 电子钥匙、 归属位置寄存器、 鉴权中心或设备标识 寄存器。
14、 根据权利要求 1所述的用户卡安全保障方法, 其特征是, 所述 验证设备是电子钥匙;
该方法进一步包括: 在移动终端和电子钥匙中分别设置一个无线收 发模块, 移动终端和电子钥匙通过所设置的无线收发模块建立无线通信 信息。
该方法或者进一步包括: 在移动终端和电子钥匙中分别设置一个数 据通信线接口, 移动终端和电子钥匙通过连接在所述两个接口之间的数 据通信线建立有线通信连接, 移动终端通过该有线通信连接传送用户卡 和电子钥匙之间的交互信息。
15、 根据权利要求 1所述的用户卡的安全保障方法, 其特征是, 所 述验证设备是终端; 步骤 b中, 所述终端在响应用户卡的认证请求之前, 进一步包括: 判断自己的合法性, 如果合法, 则响应该认证请求, 否则, 拒绝该认证 请求。
16、根据权利要求 15所述的用户卡的安全保障方法, 其特征是, 所 述方法进一步包括: 在终端和网络侧相关设备中或者是一个终端电子钥 匙中保存一个终端安全密钥, 所述终端判断自己的合法性为:
终端根据终端安全密钥对网络侧相关设备或终端电子钥匙进行认 证, 如果认证通过, 则判断自己合法, 否则, 判断自己非法。
17、根据权利要求 16所述的用户卡的安全保障方法, 其特征是, 所 述终端才艮据终端安全密钥进行认证包括:
终端产生一个随机数,然后发送给网络侧相关设备或终端电子钥匙; 网络侧相关设备或终端电子钥匙根据随机数和自己保存的终端安全 密钥进行计算, 得到一个计算结果, 然后将该计算结果返回给终端; 终端根据随机数和自己保存的业务密钥进行相应的计算, 得到一个 计算结果, 并比较自己计算得到的结果和来自网络侧相关设备或终端电 子钥匙的计算结果是否一致, 如果一致, 则认证通过; 否则认证不通过。
18、 根据权利要求 2所述的用户卡的安全保障方法, 其特征是, 步 骤 a中, 验证设备根据用户卡的标识信息保存用户卡的安全密钥;
步骤 b l l之前进一步包括: 猃证设备获取请求认证的用户卡的标识 信息, 并根据该用户卡的标识信息确定自己保存的、 且参与本次计算的 相应安全密钥。
19、根据权利要求 18所述的用户卡的安全保障方法, 其特征是, 所 述用户卡的标识信息是用户卡的卡号, 或者是用户为用户卡生成的个性 化信息标识。
20、 根据权利要求 1所述的用户卡的安全保障方法, 其特征是, 步 骤 b所述相关访问请求包括: 对用户卡保存的信息资料的访问请求, 或 对用户卡中网络业务设置数据的操作访问, 或执行相应的摘要计算或加 解密计算的请求。
PCT/CN2005/001344 2004-08-29 2005-08-29 A method for the safe protecting of the user card Ceased WO2006024224A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP05781777A EP1737201A4 (en) 2004-08-29 2005-08-29 METHOD FOR SECURELY PROTECTING THE USER CARD
US11/553,825 US7650139B2 (en) 2004-08-29 2006-10-27 Method for ensuring security of subscriber card

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410076727.4 2004-08-29
CNB2004100767274A CN100459787C (zh) 2004-08-29 2004-08-29 一种用户卡的安全保障方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/553,825 Continuation US7650139B2 (en) 2004-08-29 2006-10-27 Method for ensuring security of subscriber card

Publications (1)

Publication Number Publication Date
WO2006024224A1 true WO2006024224A1 (en) 2006-03-09

Family

ID=35999701

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001344 Ceased WO2006024224A1 (en) 2004-08-29 2005-08-29 A method for the safe protecting of the user card

Country Status (4)

Country Link
US (1) US7650139B2 (zh)
EP (1) EP1737201A4 (zh)
CN (1) CN100459787C (zh)
WO (1) WO2006024224A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7570764B2 (en) * 2001-10-10 2009-08-04 Nortel Networks Limited Sequence number calculation and authentication in a communications system
CN101640883B (zh) * 2008-07-29 2012-07-04 中国移动通信集团公司 一种用户卡存储器空间管理方法、系统及装置
US8204475B2 (en) * 2009-06-10 2012-06-19 Qualcomm Incorporated Method and apparatus for preventing unauthorized use of computing devices
CN106550359B (zh) * 2015-09-18 2019-12-06 中国电信股份有限公司 一种终端和sim卡的认证方法和系统
CN111885600B (zh) * 2020-09-02 2023-04-07 中国联合网络通信集团有限公司 双卡终端的接入方法、终端及服务器
CN113643042B (zh) * 2021-08-20 2024-04-05 武汉极意网络科技有限公司 一种基于线上业务安全的安全验证系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1050991A1 (en) * 1999-04-27 2000-11-08 Sientescom Developments Limited A dynamic validation system
CN1291390A (zh) * 1998-01-27 2001-04-11 Dsc电信有限合伙公司 动态更新蜂窝话机唯一加密密钥的方法
CN1307789A (zh) * 1998-06-26 2001-08-08 艾利森电话股份有限公司 蜂窝通信系统中的用户确认方法

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE470519B (sv) * 1992-11-09 1994-06-27 Ericsson Telefon Ab L M Anordning för tillhandahållande av tjänster såsom telefonkommunikation datakommunikation, etc omfattande en terminalenhet och en accessenhet
SE9803569L (sv) * 1998-10-19 2000-04-20 Ericsson Telefon Ab L M Förfarande och system för autentisering
GB2366938B (en) * 2000-08-03 2004-09-01 Orange Personal Comm Serv Ltd Authentication in a mobile communications network
FR2822318B1 (fr) * 2001-03-14 2003-05-30 Gemplus Card Int Dispositif portable pour securiser le trafic de paquets dans une plate-forme hote
FR2836611A1 (fr) * 2002-02-28 2003-08-29 Bull Sa Procede de communication reseau avec une carte a puce par messages asynchrones
AU2003265034A1 (en) * 2002-10-07 2004-04-23 Telefonaktiebolaget Lm Ericsson (Publ) Security and privacy enhancements for security devices
CN1708942B (zh) * 2002-10-31 2010-11-03 艾利森电话股份有限公司 设备特定安全性数据的安全实现及利用
GB2400478B (en) * 2003-04-07 2006-03-29 Research In Motion Ltd Method and system of supporting smart cards on electronic devices
AT502613B1 (de) * 2003-04-15 2007-08-15 Blum Gmbh Julius Dämpfer mit gehäuse
US7532723B2 (en) * 2003-11-24 2009-05-12 Interdigital Technology Corporation Tokens/keys for wireless communications
US7940932B2 (en) * 2004-04-08 2011-05-10 Texas Instruments Incorporated Methods, apparatus, and systems for securing SIM (subscriber identity module) personalization and other data on a first processor and secure communication of the SIM data to a second processor
US7314164B2 (en) * 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. System for biometric security using a smartcard

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1291390A (zh) * 1998-01-27 2001-04-11 Dsc电信有限合伙公司 动态更新蜂窝话机唯一加密密钥的方法
CN1307789A (zh) * 1998-06-26 2001-08-08 艾利森电话股份有限公司 蜂窝通信系统中的用户确认方法
EP1050991A1 (en) * 1999-04-27 2000-11-08 Sientescom Developments Limited A dynamic validation system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1737201A4 *

Also Published As

Publication number Publication date
CN100459787C (zh) 2009-02-04
US7650139B2 (en) 2010-01-19
EP1737201A4 (en) 2007-04-11
EP1737201A1 (en) 2006-12-27
US20070105530A1 (en) 2007-05-10
CN1741676A (zh) 2006-03-01

Similar Documents

Publication Publication Date Title
CN105188055B (zh) 无线网络接入方法、无线接入点以及服务器
CN109729523B (zh) 一种终端联网认证的方法和装置
CN108471610B (zh) 蓝牙连接控制系统
KR101485230B1 (ko) 안전한 멀티 uim 인증 및 키 교환
US9094823B2 (en) Data processing for securing local resources in a mobile device
CN103428696B (zh) 实现虚拟sim卡的方法、系统及相关设备
CN100477834C (zh) 安全装置的安全和保密性增强
CN103905401B (zh) 一种身份认证方法和设备
EP3709598B1 (en) Anti'sim swapping fraud
CN101366299B (zh) 使用特殊随机询问的引导认证
KR101028882B1 (ko) 휴대단말기를 이용한 otp 방식의 사용자인증 시스템 및 방법
WO2011017924A1 (zh) 无线局域网的认证方法、系统、服务器和终端
KR20160021763A (ko) 사용자 신원 인증 방법, 단말, 및 서버
WO2006060943A1 (fr) Procede d'authentification
CN107454035B (zh) 一种身份认证的方法及装置
WO2017185450A1 (zh) 终端的认证方法及系统
CN105898743A (zh) 一种网络连接方法、装置及系统
CN109587683B (zh) 短信防监听的方法及系统、应用程序和终端信息数据库
CN1705263B (zh) 移动终端用户的合法性验证方法及其移动终端
CN100459787C (zh) 一种用户卡的安全保障方法
CN107786978B (zh) 基于量子加密的nfc认证系统
CN100499900C (zh) 一种无线通信终端接入鉴权方法
CN101175324B (zh) 一种用户卡的安全保障方法
KR100545512B1 (ko) 무선통신에서의 재사용 침입 방지 시스템 및 방법
WO2006026925A1 (en) A method for setting the authentication key

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2005781777

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 11553825

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 2005781777

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 11553825

Country of ref document: US