An identity verification method and terminal suitable for dual offline transactions

Abstract

The present invention relates to an identity verification method and terminal suitable for dual offline transactions, and belongs to the field of offline transaction security technology. The method of the present invention comprises the following steps: within the update cycle, the mobile terminal and the terminal synchronize the root keys within at least two previous and subsequent update cycles; the mobile terminal adds corresponding identification information to all root keys to generate corresponding groups of user keys; the mobile terminal generates identity authentication information with all user keys and the unique identification of the mobile terminal; after the terminal obtains the identity authentication information, based on its own root key information, the terminal uses the same algorithm as the mobile terminal to calculate the user key, and compares the several groups of user keys calculated by itself with the several groups of user keys in the identity authentication information. When at least one group is the same, the identity authentication is passed. The present invention prevents the problem of verification failure due to deviation in key update under the premise of ensuring the safety and reliability of identity authentication.

Description

Technical Field

[0001] The invention relates to an identity verification method and a terminal suitable for dual offline transactions, belonging to the technical field of offline transaction security. Background Art

[0002] In recent years, electronic payment has developed rapidly and has been popularized in all walks of life. Traditional online electronic payment is that after the two parties exchange identity information by scanning codes, they establish contact with the payment platform (financial institution). After the payment platform verifies and confirms the identity information of the payer, the corresponding amount is deducted from the payer's electronic account and deposited into the electronic account of the payee to complete the transaction. In the process of online payment, the two parties do not need to verify each other's information, but only need to obtain the upload platform. For the seller, submit a deduction application to the payment platform, the platform verifies the buyer's information, and pays the amount to the seller's account based on credit transactions or real-time deduction transactions. The seller receives the full amount of payment and delivers the goods or provides services. At this time, the seller does not care about the payer's true identity and repayment ability in credit transactions. In an online environment, based on the platform's database and hardware resources, the identity verification method is mature and easy. It is also easy for the payment platform to grasp the user's payment ability and provide the corresponding credit transaction limit, as well as to ensure that the debt can be recovered.

[0003] However, in terms of transaction efficiency and payment experience, online transactions require both parties to communicate with the payment platform to transmit data. Whether the buyer actively requests payment from the platform before payment, or the seller applies for deduction from the platform and the platform communicates with the buyer to verify, until the payment is finally successful, this process will take hundreds of milliseconds even when the network is in good condition, which can be clearly felt as a momentary lag for the user experience. Under normal circumstances in daily life, this sense of lag will not have an impact, but in the process of, for example, a large number of people queuing to pay, this lag will accumulate and bring greater impact and waste. At the same time, in the case of dense traffic, the connection speed of the mobile network wireless network will also be greatly affected. The reduction in network speed will cause a longer wait before the payment is successful, and even payment failures will require re-payment, which greatly reduces the mobile payment experience.

[0004] In order to deal with this problem, offline payment came into being. Offline payment does not communicate with the financial platform during payment. The seller verifies the buyer's identity, records the account and delivers the goods, and then submits a deduction application to the financial platform. In this process, identity verification is particularly important. The practice of the prior art is that the financial platform regularly updates the same root key to the seller's device and the seller's device. The buyer's device combines the user's identity information with the root key through a certain algorithm to generate a user key. When trading in an offline state, the user key and transaction information and user information generate transaction verification information, such as a QR code. After scanning the code, the seller's device obtains the user information and combines it with the root key using the same algorithm. After combining, it is compared with the user key parsed from the QR code. If the comparison is consistent, it is considered that the identity verification has passed. If the user has sufficient credit at the seller or the seller has other ways to guarantee the buyer's repayment, the account is directly recorded and the goods are delivered. This process does not require interaction with a third-party financial platform. The data exchange between the buyer and seller's devices is completely offline based on QR code decoding. The entire process is millisecond-level, completely eliminating the feeling of lag. In terms of experience, you can immediately see a prompt of successful payment (scanning code to complete identity authentication successfully) after scanning the code, and the seller can deliver the goods. The payment process does not require an Internet connection, there is no lag, and there will be no payment failure due to poor network status, which reduces the waiting time for queuing payment and improves the payment experience.

[0005] Of course, offline payment devices refer to devices that are offline for a certain period of time before and after payment, while still being able to realize payment functions. This does not mean that payment devices can be offline indefinitely. While being convenient, payment security must also be considered. In order to prevent the payment QR code from being stolen and misused, it is necessary to update the key regularly (updating the key means updating the QR code). Being offline for too long will cause the payment device to be unable to update the root key, which will lead to subsequent payment failures. Therefore, when improving the security of offline payment identity authentication, the method of increasing the frequency of key updates is often adopted. However, as the frequency of key updates increases, it will be more likely that the device will fail to obtain a new key in time due to offline or other reasons, resulting in key deviations and ultimately failure to pay. This will also lead to a decline in user experience. Summary of the invention

[0006] The purpose of the present invention is to provide an identity verification method and terminal suitable for dual offline transactions, so as to solve the problem of payment failure caused by deviation in key synchronization in existing offline transactions.

[0007] To achieve the above object, the solution of the present invention includes:

[0008] An identity verification method applicable to dual offline transactions of the present invention comprises the following steps:

[0009] 1) Synchronizing the root key information of the mobile terminal that needs to be authenticated within the update cycle, and synchronizing the root key information of the terminal used for identity verification within the update cycle; the root key information includes the root key of the current update cycle, and at least the root key of the previous update cycle or the root key of the next update cycle; the root key carries the corresponding root key timestamp;

[0010] 2) The mobile terminal adds corresponding identification information to each root key in the root key information to generate a number of corresponding groups of user keys; the identification information includes a unique identifier of the mobile terminal and a root key timestamp;

[0011] 3) The mobile terminal generates identity authentication information using all user keys and a unique identifier of the mobile terminal; after obtaining the identity authentication information, the terminal calculates the user key based on its own root key information using the same algorithm as the mobile terminal, and compares the several groups of user keys calculated by itself with the several groups of user keys in the identity authentication information. If at least one group is the same, the identity authentication is passed.

[0012] The present invention aims at the situation that the key cannot be updated successfully due to network disconnection during the key synchronization process. The root keys of the two key periods before and after are synchronized for both interacting parties at once. On the basis of ensuring the security and reliability of identity authentication, the situation that the key error identity verification fails due to the failure to successfully update the root key is prevented.

[0013] Furthermore, the root key information includes three groups of root keys, namely: the root key of the current update cycle, the root key of the previous update cycle and the root key of the next update cycle.

[0014] In addition to the root key of the current cycle, each synchronization also synchronizes the root key of the previous cycle and the root key of the next cycle, further increasing the fault tolerance of synchronization failures. Even when both parties are offline (there are deviations in key updates), reliable identity recognition can still be guaranteed within a certain offline range.

[0015] Furthermore, the user key is also updated according to the validity period within the update period.

[0016] The user key is further updated regularly during the root key cycle to further improve security and prevent someone from stealing the QR code with authentication information and cheating on authentication.

[0017] Furthermore, in step 3), when the terminal calculates the user key based on its own root key information and using the same algorithm as the mobile terminal, it preferentially calculates according to the main root key group and compares it with several groups of user keys in the identity authentication information; the main root key is the root key of this update cycle.

[0018] The terminal preferentially calculates the user key based on the root key of the current period, and compares it with the user key obtained from the mobile terminal in sequence. If the comparison is successful, the identity authentication is successful, and no other root key calculation is performed, which increases verification efficiency and reduces calculation amount.

[0019] Furthermore, in step 1), the method for synchronizing the root key information between the mobile terminal and the terminal includes: pushing by a third party or actively applying to a third party for pulling.

[0020] Furthermore, the identity verification information also includes transaction information.

[0021] The identity verification method of the present invention can be used for identity verification in offline transactions, solves the problem of payment failure caused by deviation in key synchronization, improves payment experience, and increases user satisfaction.

[0022] A terminal for identity verification of the present invention comprises a processor and a memory, wherein the processor executes instructions stored in the memory to implement the following method:

[0023] 1) Synchronizing root key information within an update cycle, the root key information including the root key of the current update cycle and at least the root key of the previous update cycle or the root key of the next update cycle; the root key carries a corresponding root key timestamp;

[0024] 2) obtaining identity authentication information of a mobile terminal that needs to be authenticated; the identity authentication information includes all user keys of the mobile terminal and a unique identifier of the mobile terminal;

[0025] 3) Based on its own root key information and the identity authentication information, the user key is calculated, and several groups of user keys calculated by itself are compared with several groups of user keys in the identity authentication information. If at least one group is the same, the identity authentication is passed.

[0026] Furthermore, the root key information includes three groups of root keys, namely: the root key of the current update cycle, the root key of the previous update cycle and the root key of the next update cycle.

[0027] Furthermore, when the terminal calculates the user key based on its own root key information and the identity authentication information, it preferentially calculates according to the main root key group and compares it with several groups of user keys in the identity authentication information; the main root key is the root key of this update cycle.

[0028] Furthermore, the identity verification information also includes transaction information. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1is a flow chart of an identity verification method applicable to offline transactions according to Embodiment 1 of the present invention;

[0030] Figure 2 is a flow chart of an identity verification method applicable to offline transactions according to Embodiment 2 of the present invention;

[0031] Figure 3 is a flow chart of an identity verification method applicable to offline transactions according to Embodiment 3 of the present invention;

[0032] Figure 4 It is a schematic diagram of the terminal structure for identity verification of the present invention. DETAILED DESCRIPTION

[0033] The present invention will be further described in detail below in conjunction with the accompanying drawings.

[0034] Method Example 1:

[0035] In this embodiment, the interactive parties of the offline transaction business include the payment platform party that provides financial services, and can also be an Internet trusted site service platform, a cloud key platform, an all-in-one card platform, etc. The specific platform identity is not limited in the present invention, and is referred to as a platform or a payment platform in this embodiment; the terminal equipment with identity authentication requirements such as the payment terminal or POS terminal used by the provider of goods or services is referred to as a terminal in this embodiment; and the smart devices with networking and display functions such as mobile phones used by users who purchase goods or services, that is, devices with identity attributes and identity authentication requirements, are referred to as mobile terminals in this embodiment. The terminal is connected to the platform through a wireless or wired network, and the mobile terminal is connected to the platform through a cellular data network or wifi.

[0036] When the network connection is good, the transaction payment process can be carried out in the online payment mode as described in the background technology section, or the mobile terminal can synchronize the key with the platform and the terminal during the transaction. After the terminal verifies that the key is correct during the transaction, it will feedback that the transaction is successful and the transaction payment is completed. The present invention does not limit the online transaction process with a good network, and the focus of the present invention is on the key synchronization security algorithm based on offline transactions.

[0037] like Figure 1 As shown, the specific working process of the key synchronization security algorithm applied to offline transactions of the present invention is described below by taking the offline transaction mode of the mobile terminal and the terminal as the mode in which the terminal scans the payment QR code of the mobile terminal. It should be clear to those skilled in the art that the key synchronization security algorithm of the present invention can also be applied to other forms of transactions or interactive processes with identity authentication requirements.

[0038] In this embodiment, the root key is updated every day.

[0039] The platform generates three groups of root keys for the day, namely the first root key A1, the second root key A2 and the third root key A3. Among the three groups of root keys, the first root key A1 of the day is the second root key of the previous day (yesterday), or the first root key A1 of each day is the second root key of the previous day; the second root key A2 of each day is the third root key of the previous day (yesterday), or the second root key of each day is the third root key of the previous day (yesterday), and the second root key A2 of each day will be retained until the next day (tomorrow) as the first root key of the next day; and the third root key A3 of each day is newly generated according to the relevant algorithm on the same day, and the third root key A3 of the day will also be retained until the next day as the second root key of the next day, and will continue to be retained until the day after the next day (the day after tomorrow) as the first root key of the day after tomorrow. It can be understood that there is a root key for the day, and at the same time, a root key of yesterday and a root key of tomorrow. Or we can say that each root key is kept for 3 days, and each day of the 3 days is used as a set of root keys for that day.

[0040] The first root key A1, the second root key A2, and the third root key A3 are also equipped with corresponding first root key timestamps T1, second root key timestamps T2, and third root key timestamps T3, respectively. The root key timestamps correspond to the date and synchronization time when the root key is used as the second root key, and can also be the generation time of the root key. Because the root key interval is set to synchronize every day, the synchronization time of each day will not be exactly the same, and because the synchronization date is different from the generation date and time, the timestamp is unique for the root key and corresponds to the root key one by one.

[0041] After the first root key A1, the second root key A2, and the third root key A3 of the day are generated, the platform will synchronize the three sets of root keys (and the corresponding timestamps T1, T2, and T3) to the mobile terminal and the terminal after the set time interval. The synchronization methods include the platform actively pushing the root keys to the mobile terminal and the terminal, and the mobile terminal and the terminal actively applying to the platform to pull the root keys. After receiving the three sets of root keys, the terminal saves the three sets of root keys.

[0042] After receiving the root key, the mobile terminal uses the set algorithm to generate three sets of user keys by combining the three sets of root keys with the corresponding timestamps and user unique identifiers. The specific user keys and the elements used to generate the user keys are shown in the following table:

[0043]

[0044] If the mobile network is in good condition at this time, the three sets of user keys B1, B2, and B3 will be synchronized to the platform and then to the terminal. In this state, transactions will be conducted. The mobile terminal will generate a QR code with the three sets of user keys, transaction information, and user unique identification. After scanning and decoding, the terminal can easily identify and match the three sets of user keys, complete user identity verification (verification of the mobile device), and then complete the transaction. In this case, the transaction will not fail due to key synchronization deviation, so it is not discussed. The above-mentioned user unique identification can be the user's mobile phone number or the student ID number in the campus scenario, which is the information that uniquely determines the user's identity. The above-mentioned transaction information can be a specific consumption amount entered in advance.

[0045] If the mobile terminal network status is not good at this time, when conducting transactions, the terminal device only has the current three sets of root keys A1, A2, and A3. After the terminal scans the code to obtain the three sets of user keys B1, B2, and B3 and the user's unique identifier, it uses the same set algorithm to calculate the user's unique identifier and its own three sets of root keys and the corresponding timestamps to obtain three sets of terminal calculation keys b1, b2, and b3. When the platform does not synchronize new keys, the three sets of user keys B1, B2, and B3 obtained by parsing the mobile terminal QR code should correspond to the three sets of terminal calculation keys b1, b2, and b3 calculated by the terminal itself. In principle, during the identification comparison, as long as one set of decoded user keys is the same as any terminal calculation key calculated by itself, it is considered that the identity authentication has passed and the transaction can continue.

[0046] If the mobile terminal network status is not good at this time, and the terminal device has updated the root key when the transaction is being conducted. At this time, the three groups of root keys on the mobile terminal are still A1, A2, and A3; the three groups of user keys on the mobile terminal are still B1, B2, and B3. The three groups of root keys on the terminal device are: A2 (the second root key of the previous cycle is used as the first root key of this cycle), A3 (the third root key of the previous cycle is used as the second root key of this cycle), and A4 (a new root key is generated, which will be used as the second root key of the next cycle in the future; in this embodiment, the cycle is days). After the terminal scans and parses the QR code to obtain the three sets of user keys B1, B2, B3 and the user's unique identifier, the user's unique identifier and its own three sets of root keys A2, A3, A4 and the corresponding timestamp are calculated using the same set algorithm to obtain three sets of terminal calculation keys b2, b3, b4. The terminal compares the three sets of user keys B1, B2, B3 obtained by parsing the mobile QR code with the three sets of terminal calculation keys b2, b3, b4 obtained by the terminal itself. In the end, two sets of corresponding keys are the same, namely B2 and b2 and B3 and b3. According to the principle that a set of user keys and terminal calculations are the same, it is considered that the identity authentication has passed. In this case, the identity authentication has passed and the transaction can continue.

[0047] It can be seen from the above situation that even if a legitimate mobile terminal (not a key error, but only because the key has expired, so it can still be considered a legitimate terminal) fails to successfully update the root key for two cycles due to network disconnection or other reasons, the transaction can still be completed through verification. Similarly, if the terminal fails to successfully update the root key for two cycles, the legitimate mobile terminal can also complete the transaction through verification. The method of the present invention can still ensure reliable identity recognition in the scenario of dual offline (both the terminal and the mobile terminal are offline), while avoiding recognition failures caused by untimely key synchronization due to offline.

[0048] As another embodiment, in order to further improve the success rate of identity recognition and avoid the failure of password verification caused by key and timestamp deviation in offline scenarios. After the mobile terminal receives the root key, the three groups of root keys are respectively combined with the timestamps of the three groups of root keys and the user's unique identifier using a set algorithm to generate nine groups of user keys. The specific user key and the elements that generate the user key are shown in the following table:

[0049]

[0050] During the transaction, after the terminal scans and identifies the mobile terminal QR code, it obtains the user's unique identifier and the 9 sets of user keys shown in the table above. The terminal uses the same set algorithm to calculate the corresponding 9 sets of terminal calculation keys b11, b12, b13, b21, ... b32, b33 based on the 3 sets of root keys A1, A2, A3 and timestamps T1, T2, T3 stored in itself. The terminal compares the 9 sets of user keys obtained by parsing the mobile terminal QR code with the 9 sets of terminal calculation keys obtained by the terminal itself. If at least one set of user keys and terminal calculation keys are the same, it is considered that the identity verification has passed and the transaction can continue.

[0051] Method Example 2:

[0052] In order to increase the security of transactions on the basis of method embodiment 1, an additional level of transaction key that is updated over time or periodically is added. The validity period or update period of the transaction key should be at least shorter than the update period of the root key. That is, within the same root key period, the transaction key is updated several times. For example, if the root key is updated with a period of 1 day, the validity period of the transaction key is 6 hours, that is, the transaction key is updated 4 times within the key period of the root key.

[0053] The specific process is as follows Figure 2As shown, after the root key and the root key update time and update cycle are determined, the update time and update cycle of the transaction key corresponding to each root key are also determined. The update time corresponding to the generation of the transaction key is the timestamp of the corresponding transaction key. For 3 groups of root keys, there are 3 transaction key timestamps t1, t2, and t3. After obtaining the above 9 groups of user keys, the transaction keys are generated regularly. The specific method for generating the transaction key is that each of the 9 groups of user keys B11, B12, ..., B33 is respectively generated with the corresponding 3 transaction key timestamps t1, t2, t3 and the transaction key valid time. The transaction key is regenerated according to the above method after the valid time. The transaction key of the new cycle has a corresponding update time, and also has a corresponding new timestamp. In this way, within a transaction key cycle, 9 groups of user keys multiplied by 3 transaction key timestamps of the cycle will generate a total of 27 groups of transaction keys.

[0054] During this transaction key cycle, when the user consumes offline, a QR code containing 27 sets of transaction keys, user unique identification and transaction information is generated. The terminal scans the code to parse out these 27 sets of transaction keys, user unique identification and transaction information. The terminal calculates the corresponding 27 sets of terminal calculation keys based on the 3 sets of root keys stored in itself using the same method and process as the mobile terminal. The terminal compares the 27 sets of transaction keys obtained by parsing the mobile terminal QR code with the 27 sets of terminal calculation keys obtained by the terminal itself. If at least one set of transaction keys is the same as the terminal calculation key, it is considered that the identity verification has passed and the transaction can continue.

[0055] As another implementation mode, when the terminal compares the transaction key obtained by decoding with the terminal calculation key obtained by calculation, it gives priority to comparing the transaction key obtained by the master key line and the terminal calculation key. The master key line is the fifth group of user key B22 obtained by the current second root key A2 (or the root key of the current period) and the second root key timestamp T2, as well as the transaction key obtained by the fifth group of user key B22 and the transaction key timestamp t2 corresponding to the second root key of the corresponding transaction key period. The transaction key obtained by the master key line and the corresponding terminal calculation key are given priority.

[0056] When the specific terminal compares the transaction key obtained by decoding with the terminal calculation key obtained by calculation, after each set of terminal calculation keys is calculated, it is compared with each set of transaction keys in turn. If there is no similarity, it will continue to calculate the next set of terminal calculation keys and compare them. If there is a similarity, the calculation can be stopped and the identity verification is considered successful.

[0057] Method embodiment 3:

[0058] The difference between this embodiment and method embodiment 1 is that the update frequency of the root key can be slower, that is, the update cycle is longer; or faster, that is, the update cycle is shorter; for example, it is updated every 4 hours. Correspondingly, more groups of root keys can be configured, such as the root key of the previous 4-hour cycle, the root key of the previous 4-hour cycle, the root key of the current 4-hour cycle, the root key of the next 4-hour cycle, and the root key of the next 4-hour cycle.

[0059] For offline application scenarios, the mobile terminal, such as the user's mobile phone, is more likely to be disconnected from the network due to external or internal performance. For example, it may be powered off and shut down when updating the root key due to exhaustion of power; the key may not be updated due to network congestion caused by a large number of people gathering to use the payment function for a period of time, such as lunch time in a campus scene; or the phone's own power saving logic or traffic protection function may shut down the background operation of the corresponding platform App or cut off the network connection of the background software and fail to update the key. For the terminal, it is often fixed at the consumption point, and even a relatively reliable wired connection can be achieved. Of course, it is still impossible to avoid network congestion caused by too many people surfing the Internet in a short period of time, but in comparison, the mobile terminal is more likely to fail to successfully update the key due to network disconnection. Especially before and after each platform updates the key, it is most likely that the terminal has completed the key update, but the mobile terminal fails to update the network. At this time, the payment method using the existing technology of single-group key authentication will cause payment failure and affect the transaction.

[0060] For the most common situation that the terminal completes the update of a new cycle of the root key, but the mobile terminal fails to update and still uses the root key of the previous cycle, as other embodiments, Figure 3As shown, each time the root key is synchronized, only the second root key A2 and the third root key A3 are synchronized, that is, the root key of the current cycle and the root key of the next cycle are synchronized. When the above-mentioned most frequently occurring situation occurs, the mobile terminal fails to update and still retains the second root key A2 and the third root key A3, as well as the corresponding user key and transaction key; and the terminal completes a new round of root key update, and the root key is A3 (the root key of the current cycle, that is, the root key of the next cycle in the previous cycle) and A4 (the root key of the next cycle). At this time, since the mobile terminal and the terminal both have the same root key A3, user identity authentication can be completed to complete the transaction, and the terminal preferentially compares the final key obtained by the master key line, that is, the final key corresponding to the same root key A3, which can also improve the efficiency of user identity verification and reduce useless calculations and comparisons. Of course, for the most common situation mentioned above, the root key synchronized in each cycle can also be the root key A1 of the previous cycle and the root key A2 of the current cycle. At this time, the root key of the mobile terminal is A1 and A2 synchronized in the previous cycle, and the root key of the terminal is A2 (the root key of the previous cycle) and A3 (the root key of the current cycle) synchronized in the new cycle. Since both the terminal and the mobile terminal have the root key A2, they can pass the identity authentication. However, since the terminal prioritizes the comparison of the master key line, that is, the key finally obtained by A3, it cannot pass the identity authentication directly after the master key line is calculated. It is also necessary to complete the calculation of the non-master key line, that is, A2, before passing the comparison.

[0061] The present invention provides a new high-security key synchronization and verification method for identity authentication. It can ensure the verification success rate when both parties of identity authentication (the authenticator and the authenticated party) are offline to a certain extent, and in particular, it can still meet the verification success rate requirement when both parties of identity authentication are offline to a certain extent (referred to as double offline). According to the setting of the key synchronization cycle and the number of root keys synchronized in each cycle, the fault tolerance of the method of the present invention for the offline degree (the length of offline time) can be adjusted. For example, the longer the root key synchronization cycle and the more root key groups synchronized in each cycle, the greater the allowable offline degree (the longer the offline time), and vice versa. The allowable degree is smaller. Of course, the greater the allowable offline degree, the lower the security will be.

[0062] The identity authentication method of the present invention can be applied to the field of mobile payment. Based on the characteristics of the method of the present invention that it is applicable to offline, especially dual offline, it can be applied to a variety of application scenarios. For example, in mobile payment in a campus scenario, the campus is a closed environment where all students are registered (a public environment with uncertain non-personnel and high mobility), so the requirements of offline payment can be met while ensuring that the identity authentication is correct (the accounting method is used when consuming, and then the actual deduction is made by communicating with the payment platform). Since the time and place of campus dining are very concentrated and there are a large number of people, it is necessary to meet the mobile payment of lunch for a large number of students in a short period of time. When a large number of people gather, the network signal will decrease to a certain extent or even disconnect from the network. At this time, as described in the background technology, online payment will have great problems in this scenario, seriously affecting students' dining and restaurant order. At this time, the payment method using the method of the present invention can be fault-tolerant to a certain degree of offline or even dual offline, and can still verify the smooth payment while ensuring payment security, providing reliable technical guarantee for offline payment in the above-mentioned campus environment.

[0063] Device Example:

[0064] A kind of Figure 4 The terminal for identity verification shown in the figure can be used for offline transactions. After the identity verification is passed, according to the corresponding credit limit, the goods can be delivered or the services can be provided before the actual payment is received.

[0065] The terminal of the present invention specifically includes a processor 110 and a memory 120, a communication unit 130 and a camera 140 connected to the processor 110. The payment terminal of the present invention can be connected to the platform 100 through the communication unit and obtain the root key regularly; the payment QR code of the mobile terminal can also be scanned and identified through the camera 140. The memory 120 of the terminal of the present invention stores a computer program that can be run on the processor 110, and the processor 110 implements the method of the above method embodiment when executing the computer program. Specifically, it includes identifying relevant information from the payment QR code and performing identity authentication of the mobile terminal based on the key transaction synchronization security algorithm applied to offline transactions of the present invention. The key synchronization security algorithm specifically applied to offline transactions has been introduced clearly enough in the method embodiment and will not be repeated here.

[0066] The processor 110 described in this embodiment refers to a processing device such as a microprocessor MCU or a programmable logic device FPGA;

[0067] The memory 120 described in this embodiment includes a physical device for storing information, which is usually to digitize the information and then store it in a medium using electrical, magnetic or optical methods. For example: various memories that use electrical energy to store information, such as RAM, ROM, etc.; various memories that use magnetic energy to store information, such as hard disks, floppy disks, tapes, magnetic core memories, bubble memories, and USB flash drives; various memories that use optical methods to store information, such as CDs or DVDs. Of course, there are other types of memories, such as quantum memories, graphene memories, etc.

[0068] The communication unit 130 described in this embodiment may be a 3G communication module, a WIFI module and corresponding necessary antenna and other components, or a device capable of realizing data interaction such as a wired network card;

[0069] The camera 140 described in this embodiment can be an optical camera in the prior art, which is used to capture the QR code image information with payment information in the method embodiment, and then recognized and decoded by the processor. Of course, if there are other forms of transaction information interaction methods, such as Bluetooth or radio frequency, the corresponding Bluetooth module or radio frequency module can be used instead of the camera. The specific transaction or identity information interaction method is not limited by the present invention.

[0070] The device is composed of the above-mentioned memory 120, processor 110, communication unit 130, camera 140 and computer program, and is implemented by the processor 110 executing corresponding program instructions in the terminal computer. The processor 110 can be equipped with various operating systems, such as Windows operating system, Linux system, Android, iOS system, etc.

[0071] As another embodiment, the device may further include a display, and the display is used to display transaction information and identity identification or transaction results for reference by staff and users.

Claims

1. An identity verification method suitable for dual offline transactions, characterized in that: The steps include: 1) During the update cycle, the platform synchronously updates the root key information of the mobile terminal that needs to be authenticated and the root key information of the terminal used for identity verification; the root key information includes the root key of the current update cycle, and at least the root key of the previous update cycle or the root key of the next update cycle; the root key carries a corresponding root key timestamp; the root key timestamp is the root key generation time; 2) The mobile terminal generates a user key by combining each root key in the root key information with the timestamp corresponding to the root key and the unique identifier of the mobile terminal, and converts each root key in the root key information with the timestamp corresponding to other root keys and the unique identifier of the mobile terminal into a user key; 3) The mobile terminal generates identity authentication information using all user keys and the unique identifier of the mobile terminal; After the terminal obtains the identity authentication information, it calculates the user key based on its own root key information using the same algorithm as the mobile terminal, and compares several groups of user keys calculated by itself with several groups of user keys in the identity authentication information. When at least one group is the same, the identity authentication is passed.

2. The identity verification method applicable to dual offline transactions according to claim 1, characterized in that: The root key information includes three groups of root keys, namely: the root key of the current update cycle, the root key of the previous update cycle and the root key of the next update cycle.

3. The identity verification method applicable to dual offline transactions according to claim 1 or 2, characterized in that: The user key is also updated according to the validity period within the update period.

4. The identity verification method applicable to dual offline transactions according to claim 2, characterized in that: In step 3), the terminal calculates the user key based on its own root key information and adopts the same algorithm as the mobile terminal, and preferentially calculates it according to the main root key group and compares it with several groups of user keys in the identity authentication information; the main root key is the root key of this update cycle.

5. The identity verification method applicable to dual offline transactions according to claim 1, 2 or 4, characterized in that: In step 1), the method for synchronizing the root key information between the mobile terminal and the terminal includes: pushing by a third party or actively applying to a third party for pulling.

6. The identity verification method applicable to dual offline transactions according to claim 1, 2 or 4, characterized in that: The identity verification information also includes transaction information.

7. A terminal for identity verification, characterized in that: The invention comprises a processor and a memory, wherein the processor executes instructions stored in the memory to implement the following method: 1) Synchronize root key information within an update cycle, the root key information including the root key of the current update cycle and at least the root key of the previous update cycle or the root key of the next update cycle; the root key carries a corresponding root key timestamp; the root key timestamp is the root key generation time; 2) obtaining identity authentication information of the mobile terminal to be authenticated; the identity authentication information includes all user keys of the mobile terminal and a unique identifier of the mobile terminal; all user keys of the mobile terminal are generated by: generating user keys by combining each root key in the root key information with a timestamp corresponding to the root key and a unique identifier of the mobile terminal, and Generate a user key by using the timestamp and the unique identifier of the mobile terminal corresponding to each root key in the root key information and other root keys; 3) Based on its own root key information and the identity authentication information, the user key is calculated, and several groups of user keys calculated by itself are compared with several groups of user keys in the identity authentication information. If at least one group is the same, the identity authentication is passed.

8. The terminal for identity verification according to claim 7, characterized in that: The root key information includes three groups of root keys, namely: the root key of the current update cycle, the root key of the previous update cycle and the root key of the next update cycle.

9. The terminal for identity verification according to claim 8, characterized in that: When the terminal calculates the user key based on its own root key information and the identity verification information, the terminal preferentially calculates according to the main root key group and compares with the plurality of groups of user keys in the identity verification information; The master root key is the root key for this update cycle.

10. The terminal for identity verification according to claim 7, 8 or 9, characterized in that: The identity verification information also includes transaction information.

Images