A user authentication method, apparatus, device, storage medium, and program product.
By generating an authentication-bound user identifier and combining UAID and biometric authentication information for verification and risk assessment, the security risks of user authentication when terminal devices are used by others are resolved, and the uniqueness of user identity and business compatibility authentication are achieved.
Patent Information
- Application Number
- CN202611412582.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-11
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, user authentication methods based on UAID are difficult to distinguish whether the user is operating the device when the terminal device is used or shared by others, which poses a security risk.
By integrating the user's authentication binding UAID and biometric authentication information to generate an authentication-bound user identifier, user authentication is performed by combining UAID consistency verification, user identifier validity verification, biometric verification, and risk assessment.
It effectively ensures the uniqueness of user identity, improves the security of user authentication, and adapts to the authentication requirements of different target access services, ensuring business adaptability.
Smart Images

Figure CN123122959A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of communication technology, and in particular to a user authentication method, apparatus, electronic device, computer-readable storage medium, and computer program product. Background Technology
[0002] With the deepening development of the mobile internet, digital identity authentication has become a core element in ensuring online business security and user experience. UAID (Uniform Anonymous Identifier), as an identity identifier with high anonymity, uniqueness, strong stability, and non-retrogression, is widely used in scenarios such as finance, insurance, e-commerce, travel, and government affairs. However, in existing technologies, user authentication methods based on UAID may still maintain the same UAID when the terminal device is used or shared by others, making it difficult to distinguish whether it is the user's own operation, thus posing certain security risks. Summary of the Invention
[0003] This invention provides a user authentication method, apparatus, device, storage medium, and program product to solve the technical problem that existing user authentication methods are unable to distinguish whether the operation is performed by the user themselves, thus posing a security risk.
[0004] To address the aforementioned technical problems, a first aspect of this invention provides a user authentication method applied to an authentication platform, comprising: When the authentication requirements of the target access service requested by the user meet the triggering conditions of the first authentication process, the user's current unified anonymous identifier (UAID) is obtained. Based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, the user is authenticated to obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
[0005] As a preferred embodiment, the step of authenticating the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtaining the user's authentication result, specifically includes: Extract the authentication-bound UAID, the biometric authentication information, and the identifier generation time from the authentication-bound user identifier; When the current UAID is consistent with the authentication-bound UAID, the user identifier validity verification result is obtained based on the user identifier validity time threshold and the identifier generation time; When the user identifier validity verification result is successful, the user is subjected to biometric verification based on the biometric authentication information to obtain the biometric verification result; When the biometric verification result is successful, a risk assessment is performed on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result.
[0006] As a preferred embodiment, the step of performing biometric verification on the user based on the biometric authentication information to obtain the biometric verification result specifically includes: Based on the biometric authentication information, the target biometric authentication type of the user is determined; wherein, the target biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication. Send a biometric verification instruction to the user's terminal; wherein the biometric verification instruction is used to instruct the user terminal to perform local biometric verification based on the target biometric authentication type and to return the local biometric verification result; When the biometric local verification result returned by the user terminal is "verification passed", the biometric verification result is determined to be "verification passed".
[0007] As a preferred embodiment, the step of conducting a risk assessment on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result specifically includes: Based on the identifier generation time, the current time, and the user identifier validity time threshold, determine the remaining validity time of the authentication-bound user identifier; According to the preset risk quantification strategy, the remaining effective time is assessed to obtain the target risk quantification value corresponding to the remaining effective time; The certification result is obtained based on the comparison between the preset risk quantification threshold corresponding to the certification requirement and the target risk quantification value.
[0008] As a preferred embodiment, the risk quantification strategy is used to indicate the preset basic risk quantification value and the preset risk growth value corresponding to each remaining effective time in each preset remaining effective time range; wherein, the shorter the remaining effective time, the faster the risk value corresponding to the preset risk growth value increases.
[0009] As a preferred embodiment, the method specifically generates the current UAID through the following steps: When a UAID generation instruction is received from the business platform, the user's identity information is obtained; wherein, the identity information includes a mobile phone number and a user terminal hardware identifier; wherein, the UAID generation instruction is generated by the business platform when it determines that the user is a first-time user based on the identity information; Based on the identity information, the preset business platform registration identifier, the first random identifier, the second random identifier, the first business platform configuration key, and the second business platform configuration key, the user's current UAID is generated through an encryption algorithm.
[0010] As a preferred embodiment, the method specifically generates the authentication-bound user identifier through the following steps: When the current UAID is generated or an authentication-bound user identifier update indication is received from the service platform, a biometric verification request is sent to the user's terminal; wherein, the authentication-bound user identifier update indication is generated by the service platform when it receives the authentication-bound user identifier update request from the user; the biometric verification request is used to request the user terminal to perform local biometric verification according to a preset biometric authentication type and to return the local biometric verification result; the biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication; When the local biometric verification result is received from the user terminal and the local biometric verification result is successful, the current UAID is determined to be the current authentication-bound UAID, and the target biometric authentication type is determined based on the local biometric verification result. Based on the authentication-bound UAID, current time, target biometric authentication type, and the business platform configuration device key corresponding to the user, the user's current authentication-bound user identifier is generated.
[0011] As a preferred embodiment, the method further includes: When the authentication requirement meets the triggering condition of the second authentication process, the user's current UAID is obtained; The user is authenticated based on the authentication-bound UAID corresponding to the authentication-bound user identifier and the current UAID, and the authentication result of the user is obtained.
[0012] As a preferred embodiment, the authentication requirement is determined based on the risk value corresponding to the target access service; the risk value is determined based on the occurrence frequency of each preset risk event corresponding to the target access service and the preset risk summation value; The specific triggering condition for the first authentication process is: the risk value corresponding to the authentication requirement is greater than a preset risk value threshold; The specific triggering condition for the second authentication process is: the risk value corresponding to the authentication requirement is less than or equal to the preset risk value threshold.
[0013] A second aspect of the present invention provides a user authentication device, comprising: The authentication triggering module is used to obtain the user's current unified anonymous identifier (UAID) when the authentication requirements of the target access service requested by the user meet the first authentication process triggering conditions. The user authentication module is used to authenticate the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
[0014] A third aspect of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the user authentication method described in any of the first aspects.
[0015] A fourth aspect of the present invention provides a computer-readable storage medium comprising a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the user authentication method described in any of the first aspects.
[0016] A fifth aspect of the present invention provides a computer program product, including a computer program / instructions, wherein when the computer program / instructions are executed by a processor, the steps of the user authentication method described in any of the first aspects are implemented.
[0017] Compared to existing technologies, the beneficial effects of this invention are that by integrating the user's authentication binding UAID and biometric authentication information to generate an authentication binding user identifier, and using this authentication binding user identifier for user authentication, when the user's terminal device is used or shared by others, it can effectively distinguish whether it is the user operating based on the biometric authentication information in the authentication binding user identifier, effectively ensuring the uniqueness of the user's identity and significantly improving the security of user authentication. At the same time, it can perform user authentication for different target access services requested by the user, ensuring the service adaptability of user authentication. Attached Figure Description
[0018] Figure 1 This is a flowchart illustrating the user authentication method in an embodiment of the present invention; Figure 2 This is a schematic diagram of user authentication interaction in an embodiment of the present invention; Figure 3 This is a flowchart of the user authentication process in an embodiment of the present invention; Figure 4 This is an interactive diagram illustrating the generation of UAID and authentication-bound user identifier in an embodiment of the present invention; Figure 5 This is a schematic diagram illustrating the interaction of updating the authentication-bound user identifier in an embodiment of the present invention; Figure 6 This is a schematic diagram of the user authentication device in an embodiment of the present invention; Figure 7 This is a schematic diagram of the structure of the electronic device in an embodiment of the present invention. Detailed Implementation
[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0020] Please see Figure 1 The first aspect of this invention provides a user authentication method applied to an authentication platform, comprising the following steps S1 and S2: Step S1: When the authentication requirements of the target access service requested by the user meet the first authentication process triggering condition, obtain the user's current unified anonymous identifier (UAID). Step S2: Based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and the preset user identifier validity time threshold, authenticate the user to obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
[0021] It is worth noting that the authentication platform in this embodiment can be a base station, i.e., the operator authentication service provided by the base station, or it can be a security foundation service for the entire base station, such as... Figure 2As shown, when a user's terminal initiates a service access request to the service platform, the service platform generates a user authentication request based on the target service and user identification information in the request. In this embodiment, after receiving the user authentication request, the current authentication process needs to be determined based on the authentication requirements of the target service requested by the user. This is because different services have different requirements for risk control rigor. For example, services such as content recommendation, page personalization, and advertising have lower requirements for risk control rigor, while services such as coupon redemption, sign-in reward redemption, points mall redemption, real-name authentication, wallet payment, contract signing, and sensitive information modification have relatively higher requirements for risk control rigor. Therefore, when the authentication requirements of the target service requested by the user meet the triggering conditions of the first authentication process, it indicates that the current target service has a high risk level and requires more stringent risk control. First, the user's current UAID is obtained as the identity identification information that needs to be verified. Then, the user's current authentication-bound user identifier is used, and the authentication requirements of the current target service and the preset user identifier validity time threshold are considered to authenticate the user. It is understood that the authentication-bound user identifier in this embodiment is generated in advance based on the user's authentication-bound UAID and biometric authentication information. The authentication-bound UAID is the UAID bound to the user for authentication, which is stored locally. Since it can identify the user's terminal and mobile phone number, it can identify risk events such as device forgery and SIM (Subscriber Identity Module) card transfer. However, if the user's terminal device is used by others or the user's terminal is shared by multiple people, the UAID will not change, so it is impossible to distinguish whether it is the user's own operation. Therefore, this embodiment also integrates biometric authentication information into the authentication-bound user identifier, so as to strengthen the user's identity authentication through biometric authentication. Even if the user's terminal device is used by others or the user's terminal is shared by multiple people, non-users will fail the user authentication because they cannot pass the biometric authentication, thus effectively identifying identity fraud.
[0022] Furthermore, in the user authentication process, this embodiment also considers the authentication requirements of the target access service and the user identifier validity time threshold pre-configured by the service platform. The authentication requirements of the target access service can reflect the risk level of the business operations involved in the target access service, thereby enabling differentiated authentication for users based on different authentication requirements, making user authentication business-adaptable.
[0023] In addition, by setting a time limit for the validity of user identifiers, the authentication-bound user identifiers are made time-sensitive, so that users must reapply for and generate authentication-bound user identifiers after a period of time, to ensure that the operator is always the user himself.
[0024] After obtaining the user's authentication result, it is fed back to the business platform so that the business platform can allow the user to access the target access service when the authentication result is successful, and deny the user access to the target access service when the authentication result is unsuccessful.
[0025] The user authentication method provided in this invention generates an authentication-bound user identifier by integrating the user's authentication-bound UAID and biometric authentication information, and uses this authentication-bound user identifier for user authentication. Thus, when a user's terminal device is used or shared by others, it can effectively distinguish whether the operation is performed by the user himself based on the biometric authentication information in the authentication-bound user identifier, effectively ensuring the uniqueness of the user's identity and significantly improving the security of user authentication. At the same time, it can perform user authentication for authentication requirements of different target access services requested by the user, ensuring the service adaptability of user authentication.
[0026] As a preferred embodiment, the step of authenticating the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtaining the user's authentication result, specifically includes: Extract the authentication-bound UAID, the biometric authentication information, and the identifier generation time from the authentication-bound user identifier; When the current UAID is consistent with the authentication-bound UAID, the user identifier validity verification result is obtained based on the user identifier validity time threshold and the identifier generation time; When the user identifier validity verification result is successful, the user is subjected to biometric verification based on the biometric authentication information to obtain the biometric verification result; When the biometric verification result is successful, a risk assessment is performed on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result.
[0027] Specifically, such as Figure 3As shown, this embodiment extracts the user's authentication-bound UAID, biometric authentication information, and identifier generation time from the authentication-bound user identifier. The authentication-bound UAID is used to perform a consistency check on the user's current UAID. If the current UAID is inconsistent with the authentication-bound UAID, it indicates that the terminal device has been changed, posing a transaction risk. Therefore, the user's authentication result is determined to be authentication failure. If the current UAID is consistent with the authentication-bound UAID, it indicates that the user's mobile phone number and user terminal remain unchanged, that is, the consistency check of the current UAID passes, and the next authentication step is executed.
[0028] Furthermore, this embodiment needs to use the user identifier validity time threshold to verify the validity of the authentication-bound user identifier. Specifically, it is shown in the following expression: T r =compare(Time, T) now -timestamp), where Time is the valid time threshold for the user identifier, and timestamp is the identifier generation time of the user identifier bound to the authentication. now The time difference between the current time and the time the identifier was generated can be used to determine the usage time of the user identifier bound to this authentication, while T... r The difference between the valid time threshold for user identification and this time difference can be understood as follows: if T r If T is less than or equal to 0, it indicates that the authentication-bound user ID has expired or is invalid and cannot be used for user authentication; therefore, the user's authentication result is deemed unsuccessful. r If the value is greater than 0, it indicates that the authentication-bound user ID has not expired and can still be used for user authentication. The validity verification of the authentication-bound user ID is deemed successful, and the next authentication step is executed.
[0029] Furthermore, in order to effectively identify identity theft, this embodiment uses biometric authentication information to verify the user's biometric features to check whether the user is the one requesting access to the service. If the biometric verification result is unsuccessful or no result is received within a preset time period, it indicates that someone other than the user is operating the service, or that the person impersonating the user is afraid to perform biometric verification, resulting in a long period without a result. This suggests that the user's access request is not being performed by the user, and therefore the user's authentication result is unsuccessful. If the biometric verification result is successful, it indicates that the user is the one operating the service, and therefore the user's biometric verification is successful, proceeding to the next authentication step.
[0030] It is worth noting that even if the aforementioned verification steps have all passed, the authentication-bound user identifier itself still carries risks. This embodiment measures the risk level of the authentication-bound user identifier based on its remaining usage time. It can be understood that if the remaining usage time is long, it indicates that the authentication-bound user identifier was recently generated and has a longer validity period, thus the risk level is low. Conversely, if the remaining usage time is short, it indicates that the authentication-bound user identifier is about to expire and the user's biometric verification has not been performed again for a long time, thus the risk level is high. By assessing the risk of the authentication-bound user identifier, we can adapt to the authentication requirements of different target access services requested by users and carry out differentiated risk control for requesting users, ensuring the security of service access.
[0031] This invention, by sequentially performing UAID consistency verification, user identifier validity verification, biometric verification, and risk assessment of the authentication-bound user identifier, can not only effectively verify risks such as device forgery, SIM card transfer, and identity impersonation, but also adapt to the authentication requirements of different target access services requested by users to perform differentiated risk control for requesting users, significantly improving the security of user authentication.
[0032] As a preferred embodiment, the step of performing biometric verification on the user based on the biometric authentication information to obtain the biometric verification result specifically includes: Based on the biometric authentication information, the target biometric authentication type of the user is determined; wherein, the target biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication. Send a biometric verification instruction to the user's terminal; wherein the biometric verification instruction is used to instruct the user terminal to perform local biometric verification based on the target biometric authentication type and to return the local biometric verification result; When the biometric local verification result returned by the user terminal is "verification passed", the biometric verification result is determined to be "verification passed".
[0033] Specifically, the biometric authentication information in the authentication-bound user identifier is used to characterize the target biometric authentication type corresponding to the user's biometric verification during the generation process of the authentication-bound user identifier. After determining the target biometric authentication type, in order to verify whether the user is the one requesting access to the service during the user authentication process, this embodiment sends a biometric verification instruction to the user's terminal to instruct the user terminal to perform local biometric verification based on the target biometric authentication type and to return the local biometric verification result. It is understood that currently, terminal devices such as mobile phones and tablets support at least one of fingerprint verification, voiceprint verification, and face authentication. If the target biometric authentication type is fingerprint authentication, the biometric verification instruction instructs the user terminal to extract and verify the user's fingerprint features; if the target biometric authentication type is voiceprint authentication, the biometric verification instruction instructs the user terminal to extract and verify the user's voiceprint features; if the target biometric authentication type is face authentication, the biometric verification instruction instructs the user terminal to extract and verify the user's face features.
[0034] This invention provides a more comprehensive guarantee for user privacy by performing biometric verification locally on the user terminal, and the user terminal only needs to return the local biometric verification result without returning the specific user biometric information.
[0035] As a preferred embodiment, the step of conducting a risk assessment on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result specifically includes: Based on the identifier generation time, the current time, and the user identifier validity time threshold, determine the remaining validity time of the authentication-bound user identifier; According to the preset risk quantification strategy, the remaining effective time is assessed to obtain the target risk quantification value corresponding to the remaining effective time; The certification result is obtained based on the comparison between the preset risk quantification threshold corresponding to the certification requirement and the target risk quantification value.
[0036] Specifically, in this embodiment, the current usage time of the authentication-bound user identifier can be determined by the time difference between the current time and the identifier generation time, and then the remaining valid time of the authentication-bound user identifier can be determined based on the difference between the user identifier valid time threshold and the current usage time.
[0037] Furthermore, this embodiment pre-sets a risk quantification strategy to assess the risk of the remaining valid time, thereby characterizing the current risk level of the authenticated and bound user identifier through a specific target risk quantification value. It is worth noting that the risk quantification strategy in this embodiment defines a risk quantification rule where a shorter remaining valid time corresponds to a larger risk quantification value. After obtaining the target risk quantification value, based on a preset risk quantification threshold corresponding to the current authentication requirement, if the target risk quantification value is greater than the preset risk quantification threshold, it indicates that the current risk level of the authenticated and bound user identifier does not meet the authentication requirements of the target access service, and the user's authentication result is determined to be authentication failure; otherwise, the user's authentication result is determined to be authentication success.
[0038] This invention achieves risk assessment of the authentication-bound user identifier by quantifying the remaining validity period of the identifier. This enables refined risk management of the authentication-bound user identifier, and the quantified risk value can more intuitively reflect the risk level of the identifier, providing a basis for judging subsequent user authentication results.
[0039] As a preferred embodiment, the risk quantification strategy is used to indicate the preset basic risk quantification value and the preset risk growth value corresponding to each remaining effective time in each preset remaining effective time range; wherein, the shorter the remaining effective time, the faster the risk value corresponding to the preset risk growth value increases.
[0040] Specifically, in the risk quantification strategy of this embodiment, a corresponding basic risk quantification value and risk growth value are first set for each remaining effective time in each remaining effective time range. The risk quantification value of a certain remaining effective time in a certain remaining effective time range is the sum of the corresponding preset basic risk quantification value and preset risk growth value. The risk growth value is determined based on the product of the preset maximum risk growth value corresponding to the current remaining effective time range and the risk change coefficient. Based on the risk change coefficient, the shorter the remaining effective time, the faster the risk value corresponding to the risk growth value increases. Moreover, for two adjacent remaining effective time ranges, the maximum risk quantification value corresponding to the remaining effective time in the remaining effective time range with the larger remaining effective time is less than the minimum risk quantification value corresponding to the remaining effective time in the remaining effective time range with the smaller remaining effective time, so as to ensure that the shorter the remaining effective time, the larger the corresponding risk quantification value.
[0041] In one embodiment, the risk quantification strategy is specifically shown in the following expression: ; in, , and These are the preset baseline quantitative values for risk; , and These are the preset maximum risk growth values corresponding to each remaining valid time period, where... Can be set to The difference between the preset maximum risk quantification value corresponding to a remaining effective time that is less than or equal to 0. For example, the preset maximum risk quantification value corresponding to a remaining effective time that is less than or equal to 0 can be 100. Can be set to and The difference between them Can be set to and The difference between them; , and These are the risk change coefficients corresponding to each remaining effective time period; and Define boundaries for the preset remaining valid time range; , and It is a preset constant to ensure that the risk quantification value is greater than or equal to 0 and less than the preset maximum risk quantification value when the remaining effective time is less than or equal to 0; The risk control factor configured for the business platform, for example, set to 0.5~2.0, is used to adjust the risk quantification results; That is, the remaining valid time. The risk quantification value. Preferably, to avoid the risk quantification being too extreme and causing the quantification mechanism to be subjective, the above expression can be configured as: ; The aforementioned risk quantification strategy ensures that the shorter the remaining effective time, the faster the risk value corresponding to the preset risk growth value increases, while the longer the remaining effective time, the slower the risk value corresponding to the preset risk growth value increases. In addition, by setting risk control factors, flexible adjustments to the risk quantification strategy can be made for different businesses and scenarios. For example, setting the risk control factor to be greater than 1 results in a more stringent risk assessment, while setting it to less than 1 results in a more relaxed risk assessment, further improving the business adaptability and flexibility of risk assessment for authentication-bound user identifiers.
[0042] As a preferred embodiment, the method specifically generates the current UAID through the following steps: When a UAID generation instruction is received from the business platform, the user's identity information is obtained; wherein, the identity information includes a mobile phone number and a user terminal hardware identifier; wherein, the UAID generation instruction is generated by the business platform when it determines that the user is a first-time user based on the identity information; Based on the identity information, the preset business platform registration identifier, the first random identifier, the second random identifier, the first business platform configuration key, and the second business platform configuration key, the user's current UAID is generated through an encryption algorithm.
[0043] It is worth noting that when a user's terminal accesses the service platform for the first time, the service platform will determine whether it is a first-time user based on its identity information. Specifically, in this embodiment, the service platform can determine whether the current user is a first-time user based on the current historical access records. These historical access records are used to store the identity information of the accessing user. If the current user's identity information does not exist in the historical access records, it is a first-time user, and the identity information of the current accessing user is stored in the historical access records while sending the UAID generation instruction. Alternatively, in this embodiment, after generating the user's current UAID, it will send it to the service platform, so that the service platform binds the user's identity information with the UAID. Therefore, if the service platform cannot find the corresponding UAID locally based on the identity information of the currently accessing user, it determines that the currently accessing user is a first-time user and sends the UAID generation instruction. This embodiment does not make specific limitations here. Figure 4 As shown, in this embodiment, when the UAID generation instruction sent by the service platform is received, the user's mobile phone number is obtained by the terminal application calling the gateway to retrieve the number without being noticed and returning it. The user's user terminal hardware identifier can be extracted from the user terminal. The user terminal hardware identifier can be IMEI (International Mobile Equipment Identity), Android ID, OAID (Open Anonymous Device Identifier), IDFV (Identifier for Vendor), or device model, etc. This embodiment does not make specific limitations here.
[0044] As one implementation, this embodiment utilizes a terminal application installed on the user terminal to retrieve the gateway number and user terminal hardware identifier via a pre-loaded authentication SDK. The terminal application can be an app installed on the user terminal or a website requiring login authentication, such as a food delivery app or a shopping app, with the corresponding business services provided by the business platform. The authentication SDK is a component installed on the user terminal; after obtaining the phone number, the authentication SDK is responsible for returning the phone number and user terminal hardware identifier to the authentication platform. Furthermore, this embodiment also utilizes the terminal application installed on the user terminal to perform local biometric verification on the user terminal via the authentication SDK. This means that the authentication SDK extracts biometric features using a biometric extraction device on the user terminal and then verifies their consistency with the locally stored authentication biometric features on the user terminal. These authentication biometric features are the user's own biometric features. The authentication SDK then returns the local biometric verification result to the authentication platform.
[0045] Furthermore, in this embodiment, based on the user's identity information, a preset business platform registration identifier, a first random identifier, and a first business platform configuration key, a first hash value is generated using a hash function. Based on the user's identity information, the business platform registration identifier, a second random identifier, and a second business platform configuration key, a second hash value is generated using a hash function. Then, the first and second hash values are concatenated to generate the current UAID, as shown in the following expression: First hash value = Hash(identity information + first random identifier + business platform registration identifier + first business platform configuration key); Second hash value = Hash(identity information + second random identifier + business platform registration identifier + second business platform configuration key); UAID = First hash value + Second hash value; Among them, the first random identifier and the second random identifier are two UUIDs (Universally Unique Identifier) randomly generated in this embodiment, and the business platform registration identifier is the code used when registering the business platform.
[0046] It is worth noting that after generating the UAID, it can be bound to a user identifier, such as the user's mobile phone number or the user's registered account name on the business platform. When user authentication is required, the user's current UAID can be directly obtained based on the user identifier. Since the user's authentication-bound user identifier needs to be bound to its authentication-bound UAID, binding the UAID to the user identifier can ensure that even after the user changes to a new device, such as inserting the original SIM card into a new user terminal, the corresponding authentication-bound user identifier can still be found to authenticate the user's business access behavior.
[0047] This invention generates UAID using a hash algorithm, thereby ensuring that the user's mobile phone number and user terminal hardware identifier cannot be deduced from the UAID. Furthermore, the UAID does not contain plaintext information that can identify the user, thus guaranteeing anonymity. In addition, by introducing the business platform registration identifier as a perturbation factor, the UAID is different in different business scenarios, preventing different business platforms from authenticating users based on the same UAID.
[0048] As a preferred embodiment, the method specifically generates the authentication-bound user identifier through the following steps: When the current UAID is generated or an authentication-bound user identifier update indication is received from the service platform, a biometric verification request is sent to the user's terminal; wherein, the authentication-bound user identifier update indication is generated by the service platform when it receives the authentication-bound user identifier update request from the user; the biometric verification request is used to request the user terminal to perform local biometric verification according to a preset biometric authentication type and to return the local biometric verification result; the biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication; When the local biometric verification result is received from the user terminal and the local biometric verification result is successful, the current UAID is determined to be the current authentication-bound UAID, and the target biometric authentication type is determined based on the local biometric verification result. Based on the authentication-bound UAID, current time, target biometric authentication type, and the business platform configuration device key corresponding to the user, the user's current authentication-bound user identifier is generated.
[0049] Specifically, such as Figure 4As shown, after generating the user's current UAID, this embodiment also sends a biometric verification request to the user's terminal. For example, a biometric verification request can be initiated to the user according to the OAuth2.0 protocol to request the user terminal to perform local biometric verification according to a preset biometric authentication type. It can be understood that this embodiment can generate a specific biometric verification request by obtaining the biometric authentication methods supported by the user terminal and the biometric authentication information configured by the business platform. For example, some user terminals may not have fingerprint collection hardware and only support voiceprint verification and face verification. In this embodiment, the biometric verification request is used to request the user terminal to perform local biometric verification according to voiceprint authentication or face authentication. Considering that frequent face recognition will affect the user experience, the business platform can configure relevant biometric authentication information to determine which type of biometric authentication is not required. For example, if the biometric authentication information configured by the business platform is that face authentication is not required, then the biometric verification request in this embodiment is used to request the user terminal to perform local biometric verification according to fingerprint authentication or voiceprint authentication. This embodiment will not be elaborated further here.
[0050] Furthermore, if a local biometric verification result is received from the user terminal and the verification is successful, it indicates that the user is currently operating the system. The current UAID is used as the authentication binding UAID, and the target biometric authentication type corresponding to the local biometric verification result is determined. This target biometric authentication type is the type of biometric authentication that the user needs to perform locally for subsequent user authentication. Different characters can be used to represent different biometric authentication types, such as 1 for fingerprint authentication, 2 for voiceprint authentication, and 3 for facial authentication. This embodiment does not specify a particular type. The authentication binding UAID, current time, and target biometric authentication type can be concatenated as plaintext information. An HMAC (Hash-based Message Authentication Code) hash operation is then performed using the device key configured by the user's business platform to obtain the user's current authentication binding identifier. When subsequent user authentication is required, this embodiment uses the device key configured by the business platform to decrypt the authentication binding identifier, thereby extracting the authentication binding UAID, identifier generation time, and target biometric authentication type.
[0051] It is worth noting that if the local biometric verification result cannot be received from the user terminal, or if the local biometric verification result is a verification failure, it indicates that there is a risk that the operation is not performed by the user, and the process of generating the authentication and binding user identifier will be stopped.
[0052] In addition, such as Figure 5 As shown, when user authentication fails due to the user changing to a new user terminal or the current authentication-bound user ID expiring, the user can initiate an authentication-bound user ID update request to the business platform. This causes the business platform to send an authentication-bound user ID update instruction to the authentication platform. In this embodiment, after receiving the authentication-bound user ID update instruction sent by the business platform, the user's current authentication-bound user ID is regenerated in the same way as described above, thereby updating and replacing the original authentication-bound UAID and authentication-bound user ID.
[0053] This invention generates an authentication-bound user identifier by combining the user's authentication-bound UAID, the current identifier generation time, and the target biometric authentication type. This not only effectively verifies risky behaviors such as device forgery and identity impersonation during user authentication, but also makes the authentication-bound user identifier time-sensitive, effectively ensuring the security of business access.
[0054] As a preferred embodiment, the method further includes: When the authentication requirement meets the triggering condition of the second authentication process, the user's current UAID is obtained; The user is authenticated based on the authentication-bound UAID corresponding to the authentication-bound user identifier and the current UAID, and the authentication result of the user is obtained.
[0055] Specifically, such as Figure 3 As shown, considering that some services have lower requirements for strict risk control, such as content recommendation, page personalization, and advertising, this embodiment indicates that the risk level of the current target access service is low when the authentication requirements of the target access service requested by the user meet the triggering conditions of the second authentication process. At this time, it is only necessary to perform consistency verification on the user's current UAID, and then feed back the user's authentication result to the business platform. On the one hand, this can avoid the business access risk caused by device replacement, and on the other hand, it can improve the user authentication efficiency for such low-risk business access, thereby improving the user's business access experience.
[0056] As a preferred embodiment, the authentication requirement is determined based on the risk value corresponding to the target access service; the risk value is determined based on the occurrence frequency of each preset risk event corresponding to the target access service and the preset risk summation value; The specific triggering condition for the first authentication process is: the risk value corresponding to the authentication requirement is greater than a preset risk value threshold; The specific triggering condition for the second authentication process is: the risk value corresponding to the authentication requirement is less than or equal to the preset risk value threshold.
[0057] Specifically, this embodiment measures the authentication requirements of the target access service based on the occurrence frequency of each preset risk event and the preset risk superposition value. It can be understood that the preset risk events can be user input of payment password, user input of platform password, rights issuance, high-frequency payment behavior, abnormal login due to device switching, etc. Among them, the occurrence frequency of business operations such as user input of payment password, user input of platform password, and rights issuance can be determined in advance by the business platform, because the business operations involved in different services and their occurrence frequency are pre-configured by the business platform. As for abnormal user behaviors such as high-frequency payment behavior and abnormal login due to device switching, the business platform can count them when the user actually accesses the service and then feed back the corresponding risk event information. Thus, this embodiment can determine the occurrence frequency of such risk events based on the risk event information.
[0058] Furthermore, for each preset risk event, this embodiment sets a corresponding risk accumulation value. For example, for business operations involving passwords, such as user input of payment password and user input of platform password, the risk accumulation value for each occurrence is set to 1. For business operations not involving passwords, such as the issuance of benefits, the risk accumulation value for each occurrence is set to 0.5. For abnormal user behavior, the risk accumulation value for each occurrence is set to 0.5 or 1. This embodiment does not make specific limitations here, thereby determining the risk value of the target access business and using it as its authentication requirement. It is worth noting that the occurrence count of each preset risk event is the occurrence count in a single event within the same product lifecycle. For example, assuming that a certain business has two password verifications in a single event within the same product lifecycle, and the risk accumulation value for each occurrence of the password verification is 1, then the risk value corresponding to the authentication requirement of that business is 2. Based on the risk value of each business, the businesses can be classified according to their needs. For example, businesses with a risk value greater than 2 can be classified as high-risk businesses, businesses with a risk value greater than 0 and less than or equal to 2 can be classified as medium-risk businesses, and businesses with a risk value equal to 0 can be classified as low-risk businesses. This embodiment does not make specific limitations here. Thus, the business platform can set the authentication process required for various businesses according to actual needs to form the first authentication process triggering condition and the second authentication process triggering condition in this embodiment. Therefore, this embodiment does not make specific limitations on the preset risk value threshold used to trigger the authentication process.
[0059] This invention measures authentication requirements based on the number of occurrences of each preset risk event and the preset risk superposition value corresponding to the target access service. This enables user authentication strategies for different services to be adjusted in real time according to changes in user behavior patterns and security environment, significantly improving the accuracy and flexibility of service access risk control.
[0060] Please see Figure 6 A second aspect of the present invention provides a user authentication device 100, comprising: The authentication triggering module 11 is used to obtain the user's current UAID when the authentication requirements of the target access service requested by the user meet the first authentication process triggering condition; User authentication module 12 is used to authenticate the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
[0061] As a preferred embodiment, the user authentication module 12 is used to authenticate the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtain the user's authentication result, specifically including: Extract the authentication-bound UAID, the biometric authentication information, and the identifier generation time from the authentication-bound user identifier; When the current UAID is consistent with the authentication-bound UAID, the user identifier validity verification result is obtained based on the user identifier validity time threshold and the identifier generation time; When the user identifier validity verification result is successful, the user is subjected to biometric verification based on the biometric authentication information to obtain the biometric verification result; When the biometric verification result is successful, a risk assessment is performed on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result.
[0062] As a preferred embodiment, the user authentication module 12 is used to perform biometric verification on the user based on the biometric authentication information and obtain the biometric verification result, specifically including: Based on the biometric authentication information, the target biometric authentication type of the user is determined; wherein, the target biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication. Send a biometric verification instruction to the user's terminal; wherein the biometric verification instruction is used to instruct the user terminal to perform local biometric verification based on the target biometric authentication type and to return the local biometric verification result; When the biometric local verification result returned by the user terminal is "verification passed", the biometric verification result is determined to be "verification passed".
[0063] As a preferred embodiment, the user authentication module 12 is used to perform a risk assessment on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements, and obtain the authentication result, specifically including: Based on the identifier generation time, the current time, and the user identifier validity time threshold, determine the remaining validity time of the authentication-bound user identifier; According to the preset risk quantification strategy, the remaining effective time is assessed to obtain the target risk quantification value corresponding to the remaining effective time; The certification result is obtained based on the comparison between the preset risk quantification threshold corresponding to the certification requirement and the target risk quantification value.
[0064] As a preferred embodiment, the risk quantification strategy is used to indicate the preset basic risk quantification value and the preset risk growth value corresponding to each remaining effective time in each preset remaining effective time range; wherein, the shorter the remaining effective time, the faster the risk value corresponding to the preset risk growth value increases.
[0065] As a preferred embodiment, the device generates the current UAID through the following steps: When a UAID generation instruction is received from the business platform, the user's identity information is obtained; wherein, the identity information includes a mobile phone number and a user terminal hardware identifier; wherein, the UAID generation instruction is generated by the business platform when it determines that the user is a first-time user based on the identity information; Based on the identity information, the preset business platform registration identifier, the first random identifier, the second random identifier, the first business platform configuration key, and the second business platform configuration key, the user's current UAID is generated through an encryption algorithm.
[0066] As a preferred embodiment, the device generates the authentication-bound user identifier through the following steps: When the current UAID is generated or an authentication-bound user identifier update indication is received from the service platform, a biometric verification request is sent to the user's terminal; wherein, the authentication-bound user identifier update indication is generated by the service platform when it receives the authentication-bound user identifier update request from the user; the biometric verification request is used to request the user terminal to perform local biometric verification according to a preset biometric authentication type and to return the local biometric verification result; the biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication; When the local biometric verification result is received from the user terminal and the local biometric verification result is successful, the current UAID is determined to be the current authentication-bound UAID, and the target biometric authentication type is determined based on the local biometric verification result. Based on the authentication-bound UAID, current time, target biometric authentication type, and the business platform configuration device key corresponding to the user, the user's current authentication-bound user identifier is generated.
[0067] As a preferred embodiment, the authentication triggering module 11 is further configured to: When the authentication requirement meets the triggering condition of the second authentication process, the user's current UAID is obtained; The user authentication module 12 is also used for: The user is authenticated based on the authentication-bound UAID corresponding to the authentication-bound user identifier and the current UAID, and the authentication result of the user is obtained.
[0068] As a preferred embodiment, the authentication requirement is determined based on the risk value corresponding to the target access service; the risk value is determined based on the occurrence frequency of each preset risk event corresponding to the target access service and the preset risk summation value; The specific triggering condition for the first authentication process is: the risk value corresponding to the authentication requirement is greater than a preset risk value threshold; The specific triggering condition for the second authentication process is: the risk value corresponding to the authentication requirement is less than or equal to the preset risk value threshold.
[0069] The user authentication device 100 provided in this embodiment of the invention generates an authentication-bound user identifier by fusing the user's authentication-bound UAID and biometric authentication information, and uses the authentication-bound user identifier for user authentication. Thus, when a user's terminal device is used or shared by others, it can effectively distinguish whether it is the user operating the device based on the biometric authentication information in the authentication-bound user identifier, effectively ensuring the uniqueness of the user's identity and significantly improving the security of user authentication. At the same time, it can perform user authentication for different target access services requested by the user, ensuring the service adaptability of user authentication.
[0070] Please see Figure 7 The third aspect of the present invention provides an electronic device 200, including a memory 22, a processor 21, and a computer program stored in the memory 22 and executable on the processor 21. When the processor 21 executes the computer program, it implements the user authentication method described in any embodiment of the first aspect.
[0071] For example, the computer program may be divided into one or more modules / units, which are stored in the memory 22 and executed by the processor 21 to complete the present invention. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the electronic device 200.
[0072] The electronic device 200 may include, but is not limited to, a processor 21 and a memory 22. Those skilled in the art will understand that the schematic diagram is merely an example of the electronic device 200 and does not constitute a limitation on the electronic device 200. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the electronic device 200 may also include input / output devices, network access devices, buses, etc.
[0073] The processor 21 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, or the processor 21 can be any conventional processor 21. The processor 21 is the control center of the electronic device 200, connecting various parts of the electronic device 200 via various interfaces and lines.
[0074] The memory 22 can be used to store the computer programs and / or modules. The processor 21 implements various functions of the electronic device 200 by running or executing the computer programs and / or modules stored in the memory 22 and calling the data stored in the memory 22. The memory 22 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0075] A fourth aspect of the present invention provides a computer-readable storage medium comprising a stored computer program, wherein, when the computer program is executed, it controls the device where the computer-readable storage medium is located to perform the user authentication method described in any embodiment of the first aspect.
[0076] A fifth aspect of the present invention provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the user authentication method described in any embodiment of the first aspect.
[0077] Wherein, if the modules / units integrated in the electronic device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.
[0078] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also considered to be within the scope of protection of the present invention.
Claims
1. A user authentication method, characterized in that, Applied to authentication platforms, including: When the authentication requirements of the target access service requested by the user meet the triggering conditions of the first authentication process, the user's current unified anonymous identifier (UAID) is obtained. Based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, the user is authenticated to obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
2. The user authentication method as described in claim 1, characterized in that, The process of authenticating the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtaining the user's authentication result, specifically includes: Extract the authentication-bound UAID, the biometric authentication information, and the identifier generation time from the authentication-bound user identifier; When the current UAID is consistent with the authentication-bound UAID, the user identifier validity verification result is obtained based on the user identifier validity time threshold and the identifier generation time; When the user identifier validity verification result is successful, the user is subjected to biometric verification based on the biometric authentication information to obtain the biometric verification result; When the biometric verification result is successful, a risk assessment is performed on the authentication-bound user identifier based on the identifier generation time, the user identifier validity time threshold, and the authentication requirements to obtain the authentication result.
3. The user authentication method as described in claim 2, characterized in that, The step of performing biometric verification on the user based on the biometric authentication information and obtaining the biometric verification result specifically includes: Based on the biometric authentication information, the target biometric authentication type of the user is determined; wherein, the target biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication. Send a biometric verification instruction to the user's terminal; wherein the biometric verification instruction is used to instruct the user terminal to perform local biometric verification based on the target biometric authentication type and to return the local biometric verification result. When the biometric local verification result returned by the user terminal is "verification passed", the biometric verification result is determined to be "verification passed".
4. The user authentication method as described in claim 2, characterized in that, The step of conducting a risk assessment on the authentication-bound user identifier based on the identifier generation time, the user identifier validity period threshold, and the authentication requirements to obtain the authentication result specifically includes: Based on the identifier generation time, the current time, and the user identifier validity time threshold, determine the remaining validity time of the authentication-bound user identifier; According to the preset risk quantification strategy, the remaining effective time is assessed to obtain the target risk quantification value corresponding to the remaining effective time; The certification result is obtained based on the comparison between the preset risk quantification threshold corresponding to the certification requirement and the target risk quantification value.
5. The user authentication method as described in claim 4, characterized in that, The risk quantification strategy is used to indicate the preset basic risk quantification value and the preset risk growth value corresponding to each remaining effective time in each preset remaining effective time range; wherein, the shorter the remaining effective time, the faster the risk value corresponding to the preset risk growth value increases.
6. The user authentication method as described in claim 1, characterized in that, The method specifically generates the current UAID through the following steps: When a UAID generation instruction is received from the business platform, the user's identity information is obtained; wherein, the identity information includes a mobile phone number and a user terminal hardware identifier; wherein, the UAID generation instruction is generated by the business platform when it determines that the user is a first-time user based on the identity information; Based on the identity information, the preset business platform registration identifier, the first random identifier, the second random identifier, the first business platform configuration key, and the second business platform configuration key, the user's current UAID is generated through an encryption algorithm.
7. The user authentication method as described in claim 1, characterized in that, The method specifically generates the authentication-bound user identifier through the following steps: When the current UAID is generated or an authentication-bound user identifier update indication is received from the service platform, a biometric verification request is sent to the user's terminal; wherein, the authentication-bound user identifier update indication is generated by the service platform when it receives the authentication-bound user identifier update request from the user; the biometric verification request is used to request the user terminal to perform local biometric verification according to a preset biometric authentication type and to return the local biometric verification result; the biometric authentication type is fingerprint authentication, voiceprint authentication, or facial authentication; When the local biometric verification result is received from the user terminal and the local biometric verification result is successful, the current UAID is determined to be the current authentication-bound UAID, and the target biometric authentication type is determined based on the local biometric verification result. Based on the authentication-bound UAID, current time, target biometric authentication type, and the business platform configuration device key corresponding to the user, the current authentication-bound user identifier of the user is generated.
8. The user authentication method as described in claim 1, characterized in that, The method further includes: When the authentication requirement meets the triggering condition of the second authentication process, the user's current UAID is obtained; The user is authenticated based on the authentication-bound UAID corresponding to the authentication-bound user identifier and the current UAID, and the authentication result of the user is obtained.
9. The user authentication method as described in claim 8, characterized in that, The authentication requirements are determined based on the risk value corresponding to the target access service; the risk value is determined based on the occurrence frequency of each preset risk event corresponding to the target access service and the preset risk summation value. The specific triggering condition for the first authentication process is: the risk value corresponding to the authentication requirement is greater than a preset risk value threshold; The specific triggering condition for the second authentication process is: the risk value corresponding to the authentication requirement is less than or equal to the preset risk value threshold.
10. A user authentication device, characterized in that, include: The authentication triggering module is used to obtain the user's current unified anonymous identifier (UAID) when the authentication requirements of the target access service requested by the user meet the first authentication process triggering conditions. The user authentication module is used to authenticate the user based on the current UAID, the authentication requirement, the user's current authentication-bound user identifier, and a preset user identifier validity period threshold, and obtain the user's authentication result; wherein, the authentication-bound user identifier is generated in advance based on the user's authentication-bound UAID and biometric authentication information.
11. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the user authentication method according to any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein, when the computer program is executed, it controls the device on which the computer-readable storage medium is located to perform the user authentication method according to any one of claims 1 to 9.
13. A computer program product, characterized in that, It includes a computer program / instruction that, when executed by a processor, implements the steps of the user authentication method according to any one of claims 1 to 9.
