[go: up one dir, main page]

CN108650098B - Method and device for user-defined verification mode - Google Patents

Method and device for user-defined verification mode Download PDF

Info

Publication number
CN108650098B
CN108650098B CN201810433357.7A CN201810433357A CN108650098B CN 108650098 B CN108650098 B CN 108650098B CN 201810433357 A CN201810433357 A CN 201810433357A CN 108650098 B CN108650098 B CN 108650098B
Authority
CN
China
Prior art keywords
verification
service
user
event
authentication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810433357.7A
Other languages
Chinese (zh)
Other versions
CN108650098A (en
Inventor
吕晨晨
管维刚
陈文鸿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Advanced New Technologies Co Ltd
Advantageous New Technologies Co Ltd
Original Assignee
Advanced New Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Priority to CN201810433357.7A priority Critical patent/CN108650098B/en
Publication of CN108650098A publication Critical patent/CN108650098A/en
Application granted granted Critical
Publication of CN108650098B publication Critical patent/CN108650098B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/32—User authentication using biometric data, e.g. fingerprints, iris scans or voiceprints
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/42—User authentication using separate channels for security data
    • G06F21/43—User authentication using separate channels for security data wireless channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3215—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a plurality of channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H04L9/3231—Biological data, e.g. fingerprint, voice or retina

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Biodiversity & Conservation Biology (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本说明书实施例提供一种用户自定义验证方式的方法和装置。在设置阶段，接收用户针对某项业务而设置的验证方式，从而允许用户根据自己对于某项业务的重要性判断，自己定义该项业务所需的核身方式。在用户使用业务的阶段，客户端针对本次业务请求事件，向服务端查询用户针对该业务设置的验证方式，并依据这样的验证方式对用户进行核身验证。

Figure 201810433357

The embodiments of this specification provide a method and apparatus for user-defined authentication mode. In the setting stage, the verification mode set by the user for a certain service is received, thereby allowing the user to define the verification mode required by the service according to his own judgment of the importance of the service. In the stage when the user is using the service, the client queries the server for the authentication method set by the user for the service for this service request event, and authenticates the user according to this authentication method.

Figure 201810433357

Description

Method and device for user-defined verification mode
Technical Field
One or more embodiments of the present description relate to the field of computer technology, and more particularly, to secure authentication and identity verification.
Background
With the development of computer and internet technologies, the variety and number of various client applications and apps are increasing day by day, the related daily scenes are more and more abundant, and various aspects of affairs in life can be realized through various client applications and apps. With the use scenes and the use frequency of the applications and apps becoming higher and higher, more and more insecurity factors are brought, such as lawbreakers stealing accounts of others for payment, transfer, sending information and the like. Thus, security authentication and identity verification are becoming increasingly important.
In the conventional technology, a general application or App adopts a single secure authentication manner to authenticate the user identity, for example, the authentication is performed by a transaction password, or short message authentication, or fingerprint, etc. But such a way of authentication is still relatively thin. If the mobile phone or the password is stolen, the information is easily leaked.
Accordingly, improved solutions are desired that more efficiently secure authentication and authentication of a user.
Disclosure of Invention
One or more embodiments of the present specification describe a method and apparatus that allow a user to set different authentication methods for different services, thereby satisfying the security requirements of the user for authentication.
According to a first aspect, there is provided a method for setting a verification manner, the method being performed at a client, the method comprising:
responding to a first operation of a user, and providing a service option for the user, wherein the first operation is used for starting verification mode setting;
providing an authentication mode option for a user in response to a second operation of the user, wherein the second operation is an operation of selecting a first service from the service options;
receiving a third operation of the user, wherein the third operation is to select at least one verification mode from the verification mode options;
and sending setting information to a server, wherein the setting information at least comprises the information of the user, the information of the first service and the information of the at least one verification mode set by the user aiming at the first service.
According to one possible design, before sending the setting information to the server, the user identity is verified according to a verification mode set by the system.
In one embodiment, the verification method options may include: a plurality of verification modes recommended for the first service; or a plurality of authentication means by which the user has been authenticated.
In one embodiment, the user may select from the following authentication methods: transaction password verification, short message verification, face verification, fingerprint verification and voiceprint verification.
According to a second aspect, there is provided a method for setting a verification manner, the method being performed at a server, the method comprising:
receiving setting information, wherein the setting information at least comprises information of a user, information of a first service and information of at least one verification mode, and the at least one verification mode is set by the user aiming at the first service;
and storing the association relation between the first service and the at least one verification mode aiming at the user.
In a possible design, a multi-level mapping table is used to store the association relationship, where the multi-level mapping table includes a first-level table entry, a second-level table entry, and a third-level table entry, the first-level table entry is used to store user information of multiple users, the second-level table entry is used to store information of available services of each user, and the third-level table entry is used to store information of verification modes set by each user for each available service.
According to a third aspect, there is provided a method of security authentication, the method performed at a client, comprising:
responding to a service request event of a user, and sending a query request to a server, wherein the query request is used for requesting to query a verification mode corresponding to the service request event;
acquiring at least one verification mode from a server, wherein the at least one verification mode is set by the user aiming at the service corresponding to the service request event;
and verifying the user identity by adopting the at least one verification mode.
In one embodiment, the client includes a service platform and a verification platform, and accordingly, sending the query request to the server specifically includes:
responding to the service request event, the service platform requests an event verification ID from a server by using event information of the service request event;
the service platform obtains the event verification ID from the server side and sends the event verification ID to the verification platform;
and the verification platform sends the query request to the server based on the event verification ID.
According to a fourth aspect, there is provided a method for security authentication, performed at a server, for assisting a client in security authentication, the method comprising:
receiving an inquiry request sent by the client in response to a service request event of a user, wherein the inquiry request is used for requesting to inquire a verification mode corresponding to the service request event;
inquiring at least one verification mode set by the user for the service corresponding to the service request event according to the inquiry request;
and sending the at least one verification mode to the client.
In one embodiment, the client includes a service platform and a verification platform, and accordingly, receiving the query request specifically includes:
receiving event information sent by the service platform in response to a service request event of a user, and generating an event verification ID for the service request event based on the event information;
sending the event verification ID to the service platform;
receiving the query request from the verification platform, the query request generated based on the event verification ID.
In one embodiment, at least one verification mode set by the user for the service corresponding to the service request event is queried in the following mode:
according to the event verification ID based on the query request, acquiring event information of a service request event corresponding to the event verification ID;
determining a user and a service corresponding to the service request event;
and inquiring at least one verification mode set by the user for the service in the pre-stored setting information.
According to a fifth aspect, there is provided an apparatus for setting a verification mode, the apparatus being located at a client and comprising:
the first providing unit is configured to respond to a first operation of a user, and provide a service option for the user, wherein the first operation is used for starting verification mode setting;
a second providing unit configured to provide the user with an authentication mode option in response to a second operation of the user, wherein the second operation is an operation of selecting the first service from the service options;
the receiving unit is configured to receive a third operation of the user, wherein the third operation is to select at least one verification mode from the verification mode options;
a sending unit, configured to send setting information to a server, where the setting information at least includes information of the user, information of the first service, and information of the at least one authentication manner set by the user for the first service.
According to a sixth aspect, there is provided an apparatus for setting a verification mode, the apparatus being located at a server and comprising:
a receiving unit configured to receive setting information, the setting information including at least information of a user, information of a first service, and information of at least one authentication manner, wherein the at least one authentication manner is set by the user for the first service;
a storage unit configured to store, for the user, an association relationship between the first service and the at least one authentication manner.
According to a seventh aspect, there is provided an apparatus for security authentication, the apparatus being located at a client, comprising:
the system comprises a request unit, a service request unit and a verification unit, wherein the request unit is configured to respond to a service request event of a user and send a query request to a server, and the query request is used for requesting to query a verification mode corresponding to the service request event;
an obtaining unit, configured to obtain at least one verification manner from a server, where the at least one verification manner is set by the user for a service corresponding to the service request event;
and the verification unit is configured to verify the user identity by adopting the at least one verification mode.
According to an eighth aspect, there is provided an apparatus for security authentication, the apparatus being located at a server and used for assisting a client in security authentication, the apparatus comprising:
a receiving unit, configured to receive an inquiry request sent by the client in response to a service request event of a user, where the inquiry request is used to request to inquire a verification mode corresponding to the service request event;
the query unit is configured to query at least one verification mode set by the user for the service corresponding to the service request event according to the query request;
a sending unit configured to send the at least one authentication manner to the client.
According to a ninth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method of the first to fourth aspects.
According to a tenth aspect, there is provided a computing device comprising a memory and a processor, wherein the memory has stored therein executable code, and wherein the processor, when executing the executable code, implements the methods of the first to fourth aspects.
Through the method and the device in the embodiment of the specification, the user is allowed to define the core mode required by a certain service according to the judgment of the importance of the user to the service. In the stage that the user uses the service, the client inquires the verification mode set by the user aiming at the service from the server aiming at the service request event, and verifies the user according to the verification mode. Therefore, the process that the user self-defines the verification mode aiming at various services is realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram illustrating an implementation scenario of an embodiment disclosed herein;
FIG. 2 illustrates a flow diagram of a method of setting a verification mode, according to one embodiment;
FIG. 3A shows an exemplary interface of service options provided to a user;
FIG. 3B shows an exemplary interface for authentication mode options provided to a user;
FIG. 4 illustrates a diagram of a mapping table according to one embodiment;
FIG. 5 illustrates a method of security verification according to one embodiment;
FIG. 6 illustrates a method performed at a server to assist a client in security authentication, according to one embodiment;
FIG. 7 illustrates a process for security verification according to one embodiment;
FIG. 8 shows a schematic block diagram of an apparatus for setting an authentication mode at a client according to one embodiment;
FIG. 9 shows a schematic block diagram of an apparatus for setting an authentication mode at a server according to one embodiment;
FIG. 10 shows a schematic block diagram of a security authentication apparatus at a client according to one embodiment;
FIG. 11 shows a schematic block diagram of a security verification device at a server according to one embodiment.
Detailed Description
The scheme provided by the specification is described below with reference to the accompanying drawings.
Fig. 1 is a schematic view of an implementation scenario of an embodiment disclosed in this specification. As shown in fig. 1, the embodiment is performed between a client and a server. The client comprises a terminal device and various client applications and apps installed in the terminal device, such as a Payment App; the server corresponds to the service provided by the client. For many application services, a plurality of servers are used to perform corresponding functions, for example, a business server is used to perform business functions, a storage server is used to store large-scale data, and a security server is used to perform security functions. The server in fig. 1 may be, for example, a cloud security server adopted by a payment apparatus.
The interaction between the client and the server is divided into two phases. In the first stage, the client provides the user with authentication mode options for different services. Therefore, the user can judge according to the importance of the user to a certain service and define the core mode required by the service. For example, as shown in fig. 1, the user may set three verification modes, i.e., a transaction password, a short message and a face, for the loan service. The user-defined authentication mode can be stored in a server, such as a security server.
In the second phase, the user uses the service, generating a service request. For example, the user is ready to apply for a loan, thereby generating a loan request. At this time, the client queries the required verification mode from the server for the current service request event. The server side inquires the verification mode set by the user aiming at the service and returns the verification mode to the client side. For example, the service end inquires that the user sets three verification modes of a transaction password, a short message and a human face for the loan service before, and then returns the three verification modes to the client. The client side then verifies the transaction password, the short message and the face of the user in sequence. Therefore, the process that the user self-defines the verification mode aiming at various services is realized. Specific implementations of the above process are described below.
FIG. 2 illustrates a flow diagram of a method of setting a verification mode, according to one embodiment. The method is performed at the client. The client may include various computing terminals (e.g., PCs), smart portable devices (e.g., cell phones, tablets), and applications and apps installed thereon. As shown in fig. 2, the method for setting the verification mode includes, step 21, providing a service option to a user in response to a first operation of the user, where the first operation is used to start verification mode setting; step 22, responding to a second operation of the user, providing an authentication mode option for the user, wherein the second operation is an operation of selecting a first service from the service options; step 23, receiving a third operation of the user, wherein the third operation is to select at least one verification mode from the verification mode options; step 24, sending setting information to a server, where the setting information at least includes information of the user, information of the first service, and information of the at least one authentication mode set by the user for the first service. The execution of the respective steps is described below.
First, in step 21, in response to an operation of a user to start authentication mode setting, a service option is provided to the user. For simplicity and distinction, the above-described operation for starting the authentication mode setting is also referred to as a first operation.
In one embodiment, a customized authentication mode entry is provided for the user in the client application, for example, a "set security authentication" is added to a "my" column of the payment treasure, a "set security authentication" is added to a column of other apps similar to a "personal center", and the like. Thus, the operation of clicking to enter the entrance by the user is the first operation, and is used for starting the setting of the verification mode. And providing service options for the user once receiving the operation of starting the verification mode setting by the user. Generally, the service options include a plurality of services available to the user and supporting a user-customized authentication approach.
Fig. 3A shows an exemplary interface of service options provided to a user. After the user enters the "set security verification" function, the service options shown in fig. 3A may be presented to the user. In fig. 3A, the service options illustratively include loan transactions, transfer transactions, and bind/unbind transactions for user selection.
Thus, the user can select a service to set the authentication method from the service options. The operation of selecting the service is referred to as a second operation for short, and the service selected by the user is referred to as a first service. In fig. 3A, it is assumed that the user selects a loan transaction.
Next, in step 22, in response to the above-mentioned second operation of the user, an authentication mode option is provided to the user, where the option includes a plurality of alternative authentication modes. Alternative verification methods may include, for example, transaction password verification, short message verification, face verification, fingerprint verification, voiceprint verification, and the like.
In one embodiment, regardless of the service selected by the user, all possible authentication modes are provided to the user in the authentication mode option for the user to freely select. In another embodiment, the verification mode option comprises a verification mode recommended by the system for the first service selected by the user. In other words, the user selects different services, and the alternative authentication modes presented in the authentication mode options may be different. For example, the system may evaluate the security requirement level of each service in advance, and recommend a verification method with a higher security level, such as a fingerprint or a human face, for a service with a higher security requirement level, such as a loan service; for services with lower security requirement level, such as deposit, a general authentication mode of security level, such as a transaction password, is recommended. For services with special requirements, a corresponding verification mode can be also recommended in a targeted manner. For example, if the service selected by the user is a high security level service for a company account, the user may be provided with an authentication means, e.g., LBS-based (location based service), in an authentication means option, which may authenticate the operating location to ensure that the company account operates only within the location range of the company.
Based on the above authentication mode options, the user can select from the alternative authentication modes. Accordingly, in step 23, the client receives an operation of selecting at least one authentication mode from the authentication mode options by the user, which is also referred to as a third operation.
In one embodiment, only the authentication mode in which the user has been authenticated is provided to the user in the authentication mode option. In another embodiment, all possible authentication modes are provided in the authentication mode option. At this time, if the authentication method selected by the user in step 23 includes a specific authentication method that the user has not authenticated, the user identity is then authenticated using the specific authentication method. For example, if fingerprint authentication is selected, but the fingerprint has not been previously authenticated, the user is required to enter a fingerprint for authentication.
FIG. 3B shows one exemplary interface for authentication mode options provided to a user. In fig. 3B, the verification method options include a transaction password, a short message, a face, and a fingerprint for the user to select. Then, the user can select an authentication method that the user thinks necessary from the authentication method options. Assume that after the user selects the loan transaction in fig. 3A, three verification methods, i.e., a transaction password, a short message, and a face, are selected in fig. 3B for the loan transaction.
After receiving the operation of selecting the verification mode by the user, in step 24, the client sends setting information to the server, where the setting information at least includes information of the user, information of the first service selected by the user, and information of at least one verification mode set by the user for the first service, and the setting information is used for the server to store and record the verification mode set by the user for the service. In this way, the setting of the authentication mode performed at the client is completed.
In one embodiment, in order to increase security and prevent others from assuming the user to perform authentication setting, after the user performs the first operation, at any stage before step 24, the user is authenticated once. The mode of the core-body verification can be preset by the system. Thus, the security of the setting of the verification mode is increased.
And correspondingly to the client, the server receives the setting information sent by the client, and stores and records the setting information. As described above, the received setting information at least includes information of the user, information of the first service selected by the user, and information of at least one authentication manner set by the user for the first service. For this reason, the server needs to store the association relationship between the service and the set verification method for each user.
In one embodiment, the server side stores the association relationship by using a multi-level mapping table. The multi-level mapping table comprises a first-level table entry, a second-level table entry and a third-level table entry, wherein the first-level table entry is used for storing user information of a plurality of users, the second-level table entry is used for storing information of available services of all the users, and the third-level table entry is used for storing verification mode information set by all the users aiming at all the available services.
FIG. 4 illustrates a diagram of a mapping table according to one embodiment. It is understood that the mapping table is a mapping table used by the server to store setting information of each user. As shown in fig. 4, in the first-level entry of the mapping table, information of each User, such as User ID, is stored, including User1, User2, …; in the second level entry of the mapping table, information of available services of each User, for example, the available service of User 1: loans, transfer accounts, deposits, tie cards, and the like; in the third-level table entry of the mapping table, information of verification modes set by each User for each available service is stored, for example, three verification modes of a transaction password, a short message and a face are set by the User1 for a loan service, two verification modes of the transaction password and the short message are set for a transfer service, and the verification modes of the transaction password are set for both deposit and binding.
It is to be understood that the server may also store the setting information of the user in other forms, which is not limited herein.
Thus, in the first stage of the embodiment of the present specification, that is, the stage in which the user sets the verification manner, the client receives the setting operation of the user, and arranges the setting operation as the setting information and sends the setting information to the server, and the server stores and records the setting information of each user, so that the user can set different verification manners for each service according to the needs of the user based on the importance judgment of the user on each service.
Next, it is described how to guide the user to complete the authentication according to the personalized settings of the user in the second phase of the embodiment, i.e. the phase in which the user performs security authentication for using the service.
FIG. 5 illustrates a method of security authentication, performed at a client, according to one embodiment. As shown in fig. 5, the method includes: step 51, responding to a service request event of a user, sending a query request to a server, wherein the query request is used for requesting to query a verification mode corresponding to the service request event; step 52, obtaining at least one verification mode set by the user for the service corresponding to the service request event from the server; and 53, verifying the user identity by adopting at least one verification mode.
In one embodiment, the client comprises a service platform and a verification platform, wherein the service platform is used for processing service-related requests, and the verification platform is used for authenticating the user aiming at various services. In such a case, step 51 further comprises the following process: the user sends a service request event to the service platform, and the service platform requests the service end for an event verification ID by using the event information of the service request event. After obtaining the requested event validation ID from the server, the service platform sends the event validation ID to the validation platform. Then, the verification platform sends the query request to the server based on the event verification ID, so as to request to query the verification mode corresponding to the service request event.
Next, in step 52, the client obtains the verification mode corresponding to the service request event from the server. In the case where the client includes a service platform and a verification platform, in this step, the verification platform receives a returned verification means from the server.
Then, in step 53, the client verifies the user identity in the verification manner obtained from the server. More specifically, user authentication may be performed by an authentication platform in the client.
In one embodiment, in step 53, the client, particularly the authentication platform therein, sequentially obtains each piece of authentication information provided by the user for each set authentication manner, and sends each piece of authentication information to the core authentication center, so that the core authentication center authenticates the identity of the user.
Corresponding to the method performed at the client shown in fig. 5, fig. 6 shows a method performed at the server for assisting the client in security authentication according to an embodiment, and includes: step 61, receiving an inquiry request sent by a client in response to a service request event of a user, wherein the inquiry request is used for requesting to inquire a verification mode corresponding to the service request event; step 62, according to the query request, querying at least one verification mode set by the user for the service corresponding to the service request event; and 63, sending the at least one verification mode to the client.
In one embodiment, the client includes a service platform and a verification platform. Accordingly, the above step 61 includes the following processes: the server receives event information sent by the client service platform in response to a service request event of a user, and generates an event verification ID for the service request event based on the event information. In one embodiment, the server encodes the item in the event information according to a predetermined rule, thereby generating the event verification ID. In another embodiment, the server generates the current event verification ID from the serial number. And then, sending the generated event verification ID to the service platform. As previously described, the service platform will forward the event validation ID to the validation platform. Then, the server receives an inquiry request generated based on the event authentication ID from the authentication platform, so as to inquire the authentication manner corresponding to the service request event.
Next, in step 62, the authentication mode set by the user for the service corresponding to the service request event is queried. As described above, the server stores and records the setting information of each user, including the verification manner set by each user for each available service, for example, as shown in fig. 4. Accordingly, when receiving an inquiry request from the client, the server can inquire from the stored setting information what authentication mode the current user has set for the service of the current service request event.
In one embodiment, the query request includes current user information and requested service information. In such a case, the server may directly query the setting information, and the current user sets a verification manner for the requested service.
In another embodiment, the query request is generated based on the event verification ID described above. In this case, the querying process may include, first, obtaining event information of the service request event corresponding to the event verification ID according to the event verification ID based on the query request. Then, according to the event information, determining a user and a service corresponding to the service request event; then, the verification mode set by the user for the service is inquired in a pre-stored setting information mapping table.
Then, in step 63, the queried authentication manner is sent to the client for the client to perform security authentication.
The second stage of the verification process is described below in conjunction with fig. 7. FIG. 7 illustrates a process for security verification according to one embodiment. In the example of FIG. 7, the client includes a business platform and a verification platform.
First, in step S01, the user sends a service request to the service platform, forming a service request event. For example, in one example, the user (user01) uses a loan service. After the user fills in the personal information, the loan amount and the collection card number, the user clicks 'confirm loan', and then sends a loan service request to the service platform to form a service request event.
After receiving such a service request, the service platform obtains event information of the service request event in step S02. In one embodiment, the service platform extracts elements of the service request event to form event information. The event information may include: user information (e.g., userID), device information, service type, service serial number, etc. For example, in the case where the user01 uses the loan service as described above, the event information may include, for example, the user name user01, the type number of the loan service S01, the loan amount 10k, the service line number xxxxxx, and the like.
Then, in step S03, the service platform sends the above event information to the server, i.e., requests an event verification ID from the server using the event information.
After the server receives the event information, at step S04, a preliminary verification is performed on the service request event. This includes, for example, verifying that the userID therein is legitimate, verifying that the formats of the various pieces of information are correct, and so forth.
After the preliminary authentication is passed, in step S05, the server generates an event authentication ID, also called vid (verify ID), for the service request event. In one example, the server encodes an item in the event information according to a predetermined rule, thereby generating the above-mentioned event verification ID. For example, the VID may be generated by composing each item in the event information into a character string and applying a predetermined encoding format to the character string. In another example, the server generates an event verification ID for the current event based on the serial number. Or, in yet another example, the server randomly generates a string as the event verification ID for the current event.
In one example, for the above-described service request event for which the user01 uses the loan service, it is assumed that the event verification ID generated therefor is EV 001.
It can be understood that, while generating the event verification ID, the server stores the corresponding relationship between the generated event verification ID and the event information for subsequent query.
Next, in step S06, the server returns the generated event verification ID to the service platform.
Then, the service platform forwards the event verification ID to the verification platform at step S07. Since the event authentication ID is only one ID (e.g., EV001) and does not include information related to the service in the service request event, the authentication platform is prevented from acquiring unnecessary service information, and thus security is improved.
After the verification platform receives the event verification ID from the service platform, in step S08, an inquiry request may be sent to the server based on the event verification ID to request a verification manner required for inquiring about the current service request event.
In step S09, the server queries the verification method corresponding to the current service request event. As described above, the server generates an event verification ID and stores a correspondence between the generated event verification ID and the event information. Therefore, when receiving the query request, the server first obtains the event information of the service request event corresponding to the event verification ID included in the query request according to the correspondence. Then, according to the event information, determining a user and a service corresponding to the service request event; then, the authentication mode set by the user for the service is inquired in the pre-stored user setting information. For example, the query request received by the server includes an event authentication ID: the EV001, then the service end can locate event information based on the ID, including the user name user01, the type number of the loan transaction S01, the loan amount 10k, the transaction sequence number xxxxxx, and so on. According to the above event information, it can be determined that the user corresponding to the service request event is user01 and the service is S01. Then, in the pre-stored user setting information, the authentication manner set by the user01 for the service S01, for example, including a transaction password, a short message, and a face, may be queried.
Next, in step S10, the server returns the queried authentication method to the authentication platform.
In step S11, the verification platform sends out verification requests to the user in sequence for each verification mode obtained, and in step S12, obtains the verification information of the user in sequence. For example, if the obtained authentication methods are a transaction password, a short message and a human face, the user is sequentially requested to input the password, the short message and the human face information in step S11, and the password, the short message content and the human face information input by the user are respectively obtained in step S12.
Next, the authentication platform transmits the authentication information input by the user to the authentication center at step S13. In most business application scenarios, an authentication center which is independent of a client and a security server of a server is adopted and is specially used for identity authentication. Of course, in some scenarios, the verification center may also be integrated in some servers of the server side.
After receiving the verification information from the client verification platform, the verification center verifies the verification information in step S14. Then, in step S15, a verification result, such as verification pass or verification fail, is sent to the client verification platform, and the verification platform may notify the service platform of the verification result.
The service platform may then determine whether to allow the user to proceed with the current service request based on the verification result.
When a user sets a plurality of verification methods for a current service, the plurality of verification methods are all verified to be verified. For example, in one example, the verification platform sends the transaction password, the short message verification content and the face information to the verification center, the verification center verifies the three verification modes respectively, and only when each verification information is matched with the reserved standard information respectively, the verification result is returned to the client.
Through the above method, when the user uses the service, the user identity is verified according to the verification method set by the user for the service.
In one embodiment, in case the service platform is notified that the verification is passed, the service platform also performs a secondary verification to increase security. The secondary verification can be used for judging whether the verification platform really initiates the query to the server side or not and verifying the user according to the query result. The process of the secondary verification may include that the service platform sends the event verification ID to the server again, and the request server determines whether the event verification ID is requested to be queried. If the prior verification platform initiates a query request to the server based on the event verification ID, a corresponding API interface is called. The server side can judge whether the corresponding event verification ID is inquired or not through the called record of the corresponding API interface, and returns the judgment result to the service platform. In an embodiment, the service end may further query the verification mode corresponding to the event verification ID, and return the verification mode to the service platform. Therefore, the service platform can compare the verification mode obtained from the server and the verification mode in the verification result notification to further confirm.
It will be appreciated that there are also more ways of secondary verification. Both of these approaches may be employed to further consolidate the security of the core-body authentication.
Through the implementation mode, the user is allowed to define the core mode required by a certain service according to the judgment of the importance of the user to the service. In the stage that the user uses the service, the client inquires the verification mode set by the user aiming at the service from the server aiming at the service request event, and verifies the user according to the verification mode. Therefore, the process that the user self-defines the verification mode aiming at various services is realized.
According to another embodiment, a device for setting a verification mode is provided at a client. FIG. 8 shows a schematic block diagram of an apparatus to set a verification mode according to one embodiment. It is to be understood that the setup device 80 of fig. 8 is located on the client side. As shown in fig. 8, the setting device 80 includes: a first providing unit 81 configured to provide a service option to a user in response to a first operation of the user, wherein the first operation is used to start an authentication mode setting; a second providing unit 82 configured to provide the authentication mode option to the user in response to a second operation of the user, wherein the second operation is an operation of selecting the first service from the service options; a receiving unit 83 configured to receive a third operation of the user, where the third operation is to select at least one authentication mode from the authentication mode options; a sending unit 84 configured to send setting information to a server, where the setting information at least includes information of the user, information of the first service, and information of the at least one authentication manner set by the user for the first service.
In one embodiment, the apparatus 80 further includes a first verification unit (not shown) configured to verify the user identity according to a verification manner set by the system before sending the setting information to the server.
In one embodiment, the authentication mode options provided by the second providing unit 82 include: a plurality of verification modes recommended for the first service; or a plurality of authentication means by which the user has been authenticated.
In one embodiment, the at least one authentication mode selected by the user includes a particular authentication mode that the user has not authenticated; correspondingly, the apparatus 80 further comprises a second authentication unit (not shown) configured to authenticate the user identity using the specific authentication approach.
According to one embodiment, the at least one authentication means comprises one or more of: transaction password verification, short message verification, face verification, fingerprint verification and voiceprint verification.
According to another embodiment, a device for setting the verification mode is provided at the server side. FIG. 9 shows a schematic block diagram of an apparatus to set a verification mode according to one embodiment. It is to be understood that the setting device 90 of fig. 9 is located at the server side. As shown in fig. 9, the setting device 90 includes: a receiving unit 91 configured to receive setting information including at least information of a user, information of a first service, and information of at least one authentication manner set by the user for the first service; and a storage unit 92 configured to store, for the user, an association relationship between the first service and the at least one authentication manner.
In an embodiment, the storage unit 92 is configured to store the association relationship by using a multi-level mapping table, where the multi-level mapping table includes a first-level table entry, a second-level table entry, and a third-level table entry, the first-level table entry is used to store user information of multiple users, the second-level table entry is used to store information of available services of each user, and the third-level table entry is used to store verification mode information set by each user for each available service.
According to an embodiment of yet another aspect, an apparatus for secure authentication is provided at a client. FIG. 10 shows a schematic block diagram of a security authentication device according to one embodiment. It is to be understood that the authentication apparatus 100 of fig. 10 is located on the client side. As shown in fig. 10, the authentication apparatus 100 includes: a request unit 101, configured to respond to a service request event of a user, and send an inquiry request to a server, where the inquiry request is used to request to inquire a verification manner corresponding to the service request event; an obtaining unit 102, configured to obtain at least one verification manner from a server, where the at least one verification manner is set by the user for a service corresponding to the service request event; the verification unit 103 is configured to verify the user identity by using the at least one verification method.
In one embodiment, the requesting unit 101 includes a service module 1011 and a verification module 1012, wherein the service module 1011 is configured to, in response to the service request event, request an event verification ID from a server using event information of the service request event, obtain the event verification ID from the server, and send the event verification ID to the verification module 1012; the verification module 1012 is configured to issue the query request to the server based on the event verification ID.
According to one embodiment, the event information includes at least one of: user information, device information, service type, service serial number.
In an embodiment, the verification unit 103 is configured to sequentially obtain each piece of verification information provided by the user for each verification manner of the at least one verification manner, and send each piece of verification information to the core verification center, so that the core verification center verifies the identity of the user.
According to an embodiment of yet another aspect, an apparatus for security authentication is provided at a server. FIG. 11 shows a schematic block diagram of a security authentication device according to one embodiment. It should be understood that the authentication device 110 of fig. 11 is located at the server side for assisting the client in performing security authentication. As shown in fig. 11, the apparatus 110 includes: a receiving unit 111, configured to receive an inquiry request sent by the client in response to a service request event of a user, where the inquiry request is used to request to inquire a verification manner corresponding to the service request event; the query unit 112 is configured to query, according to the query request, at least one verification manner set by the user for a service corresponding to the service request event; and a sending unit 113 configured to send the at least one authentication means to the client.
In one embodiment, the client includes a service platform and a verification platform. Accordingly, the receiving unit 111 of the server device 110 is configured to: receiving event information sent by a service platform in response to a service request event of a user, and generating an event verification ID for the service request event based on the event information; sending the event verification ID to the service platform; receiving the query request from the verification platform, the query request generated based on the event verification ID.
According to one embodiment, the event information includes at least one of: user information, device information, service type, service serial number.
In one embodiment, the receiving unit 111 encodes an item in the event information according to a predetermined rule, thereby generating the event verification ID.
According to one embodiment, the querying element 112 is configured to: according to the event verification ID based on the query request, acquiring event information of a service request event corresponding to the event verification ID; determining a user and a service corresponding to the service request event; and inquiring at least one verification mode set by the user for the service in the pre-stored setting information.
According to an embodiment of another aspect, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method described in connection with fig. 2, 5 and 6.
According to an embodiment of yet another aspect, there is also provided a computing device comprising a memory and a processor, the memory having stored therein executable code, the processor, when executing the executable code, implementing the method described in connection with fig. 2, 5 and 6.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

Claims (34)

1. A method for setting a verification mode, which is executed at a client, comprises the following steps:
responding to a first operation of a user, and providing a service option for the user, wherein the first operation is used for starting verification mode setting;
providing an authentication mode option to a user in response to a second operation of the user, wherein the second operation is an operation of selecting a first service from the service options, and the authentication mode option comprises an alternative authentication mode determined based on the evaluation of the security requirement level of the first service;
receiving a third operation of the user, wherein the third operation is to select at least one verification mode from the verification mode options;
and sending setting information to a server, wherein the setting information at least comprises the information of the user, the information of the first service and the information of the at least one verification mode set by the user aiming at the first service.
2. The method of claim 1, wherein before sending the setting information to the server, further comprising verifying the user identity according to a verification mode set by the system.
3. The method of claim 1, wherein the authentication mode option comprises:
a plurality of verification modes recommended for the first service; or
The user has passed multiple authentication modes of authentication.
4. The method of claim 1, wherein the at least one authentication mode comprises a specific authentication mode that the user has not authenticated, the method further comprising authenticating the user identity using the specific authentication mode.
5. The method of claim 1, wherein the at least one authentication means comprises one or more of: transaction password verification, short message verification, face verification, fingerprint verification and voiceprint verification.
6. A method for setting a verification mode is executed at a server side and comprises the following steps:
receiving setting information, wherein the setting information at least comprises information of a user, information of a first service and information of at least one verification mode, the at least one verification mode is set by the user aiming at a verification mode option provided by the first service, and the verification mode option comprises an alternative verification mode determined based on the safety requirement level evaluation of the first service;
and storing the association relation between the first service and the at least one verification mode aiming at the user.
7. The method according to claim 6, wherein storing the association between the first service and the at least one verification mode for the user comprises storing the association using a multi-level mapping table, where the multi-level mapping table includes a first-level entry, a second-level entry, and a third-level entry, the first-level entry is used to store user information of multiple users, the second-level entry is used to store information of available services for the respective users, and the third-level entry is used to store information of verification modes set by the respective users for the respective available services.
8. A method of security authentication, the method performed at a client, comprising:
responding to a service request event of a user, and sending a query request to a server, wherein the query request is used for requesting to query a verification mode corresponding to the service request event;
acquiring at least one verification mode from a server, wherein the at least one verification mode is set by a verification mode option provided by the user for the service corresponding to the service request event, and the verification mode option comprises an alternative verification mode determined based on the evaluation of the security requirement level of the first service;
and verifying the user identity by adopting the at least one verification mode.
9. The method of claim 8, wherein the client comprises a service platform and a verification platform, and the issuing of the query request to the server in response to the service request event of the user comprises:
responding to the service request event, the service platform requests an event verification ID from a server by using event information of the service request event;
the service platform obtains the event verification ID from the server side and sends the event verification ID to the verification platform;
and the verification platform sends the query request to the server based on the event verification ID.
10. The method of claim 9, wherein the event information comprises at least one of: user information, device information, service type, service serial number.
11. The method according to claim 8, wherein the verifying the user identity by using the at least one verification method includes sequentially obtaining each piece of verification information provided by the user for each verification method of the at least one verification method, and sending each piece of verification information to the core verification center, so that the core verification center verifies the user identity.
12. A method for security authentication, the method being performed at a server for assisting a client in security authentication, the method comprising:
receiving an inquiry request sent by the client in response to a service request event of a user, wherein the inquiry request is used for requesting to inquire a verification mode corresponding to the service request event;
inquiring at least one verification mode set by the user aiming at a verification mode option provided by the service corresponding to the service request event according to the inquiry request, wherein the verification mode option comprises an alternative verification mode determined based on the safety requirement level evaluation of the first service;
and sending the at least one verification mode to the client.
13. The method of claim 12, wherein the client comprises a service platform and a verification platform, and the receiving the query request sent by the client in response to a service request event of a user comprises:
receiving event information sent by the service platform in response to a service request event of a user, and generating an event verification ID for the service request event based on the event information;
sending the event verification ID to the service platform;
receiving the query request from the verification platform, the query request generated based on the event verification ID.
14. The method of claim 13, wherein the event information comprises at least one of: user information, device information, service type, service serial number.
15. The method of claim 13 or 14, wherein generating an event validation ID for the service request event based on the event information comprises: and encoding the item in the event information according to a predetermined rule, thereby generating the event verification ID.
16. The method according to claim 13, wherein querying at least one authentication manner set by the user for the service corresponding to the service request event comprises:
according to the event verification ID based on the query request, acquiring event information of a service request event corresponding to the event verification ID;
determining a user and a service corresponding to the service request event;
and inquiring at least one verification mode set by the user for the service in the pre-stored setting information.
17. An apparatus for setting a verification mode, the apparatus being located at a client and comprising:
the first providing unit is configured to respond to a first operation of a user, and provide a service option for the user, wherein the first operation is used for starting verification mode setting;
a second providing unit configured to provide the user with an authentication mode option in response to a second operation of the user, wherein the second operation is an operation of selecting the first service from the service options;
a receiving unit configured to receive a third operation of a user, wherein the third operation is to select at least one authentication mode from the authentication mode options, and the authentication mode options include alternative authentication modes determined based on the evaluation of the security requirement level of the first service;
a sending unit, configured to send setting information to a server, where the setting information at least includes information of the user, information of the first service, and information of the at least one authentication manner set by the user for the first service.
18. The apparatus according to claim 17, further comprising a first authentication unit configured to authenticate the user identity according to an authentication manner set by the system before sending the setting information to the server.
19. The apparatus of claim 17, wherein the authentication mode options comprise:
a plurality of verification modes recommended for the first service; or
The user has passed multiple authentication modes of authentication.
20. The apparatus according to claim 17, wherein the at least one authentication manner comprises a specific authentication manner that the user has not authenticated, the apparatus further comprising a second authentication unit configured to authenticate the user identity using the specific authentication manner.
21. The apparatus of claim 17, wherein the at least one authentication means comprises one or more of: transaction password verification, short message verification, face verification, fingerprint verification and voiceprint verification.
22. An apparatus for setting a verification mode, the apparatus being located at a server and comprising:
a receiving unit configured to receive setting information, the setting information at least including information of a user, information of a first service, and information of at least one authentication manner, wherein the at least one authentication manner is set by an authentication manner option provided by the user for the first service, and the authentication manner option includes an alternative authentication manner determined based on a security requirement level evaluation for the first service;
a storage unit configured to store, for the user, an association relationship between the first service and the at least one authentication manner.
23. The apparatus according to claim 22, wherein the storage unit is configured to store the association relationship by using a multi-level mapping table, where the multi-level mapping table includes a first-level table entry, a second-level table entry, and a third-level table entry, the first-level table entry is used to store user information of multiple users, the second-level table entry is used to store information of available services of each user, and the third-level table entry is used to store verification mode information set by each user for each available service.
24. An apparatus for security verification, the apparatus being located at a client, comprising:
the system comprises a request unit, a service request unit and a verification unit, wherein the request unit is configured to respond to a service request event of a user and send a query request to a server, and the query request is used for requesting to query a verification mode corresponding to the service request event;
an obtaining unit, configured to obtain at least one authentication manner from a server, where the at least one authentication manner is set by an authentication manner option provided by the user for a service corresponding to the service request event, and the authentication manner option includes an alternative authentication manner determined based on an evaluation of a security requirement level of the first service;
and the verification unit is configured to verify the user identity by adopting the at least one verification mode.
25. The apparatus of claim 24, wherein the request unit comprises a service module and a validation module,
the service module is configured to respond to the service request event, request an event verification ID from a server by using event information of the service request event, obtain the event verification ID from the server, and send the event verification ID to the verification module;
the verification module is configured to issue the query request to the server based on the event verification ID.
26. The apparatus of claim 25, wherein the event information comprises at least one of: user information, device information, service type, service serial number.
27. The apparatus according to claim 24, wherein the authentication unit is configured to sequentially obtain each piece of authentication information provided by the user for each authentication manner of the at least one authentication manner, and send each piece of authentication information to the core authentication center, so that the core authentication center authenticates the identity of the user.
28. An apparatus for security authentication, the apparatus being located at a server and used for assisting a client in security authentication, the apparatus comprising:
a receiving unit, configured to receive an inquiry request sent by the client in response to a service request event of a user, where the inquiry request is used to request to inquire a verification mode corresponding to the service request event;
the query unit is configured to query, according to the query request, at least one authentication mode set by the user for an authentication mode option provided by a service corresponding to the service request event, where the authentication mode option includes an alternative authentication mode determined based on the evaluation of the security requirement level of the first service;
a sending unit configured to send the at least one authentication manner to the client.
29. The apparatus of claim 28, wherein the client comprises a service platform and a verification platform, the receiving unit is configured to:
receiving event information sent by the service platform in response to a service request event of a user, and generating an event verification ID for the service request event based on the event information;
sending the event verification ID to the service platform;
receiving the query request from the verification platform, the query request generated based on the event verification ID.
30. The apparatus of claim 29, wherein the event information comprises at least one of: user information, device information, service type, service serial number.
31. The apparatus of claim 29 or 30, wherein the receiving unit generates an event verification ID for the service request event based on the event information comprises: and encoding the item in the event information according to a predetermined rule, thereby generating the event verification ID.
32. The apparatus of claim 29, wherein the querying element is configured to:
according to the event verification ID based on the query request, acquiring event information of a service request event corresponding to the event verification ID;
determining a user and a service corresponding to the service request event;
and inquiring at least one verification mode set by the user for the service in the pre-stored setting information.
33. A computer-readable storage medium, on which a computer program is stored which, when executed in a computer, causes the computer to carry out the method of any one of claims 1-16.
34. A computing device comprising a memory and a processor, wherein the memory has stored therein executable code that, when executed by the processor, performs the method of any of claims 1-16.
CN201810433357.7A 2018-05-08 2018-05-08 Method and device for user-defined verification mode Active CN108650098B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810433357.7A CN108650098B (en) 2018-05-08 2018-05-08 Method and device for user-defined verification mode

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810433357.7A CN108650098B (en) 2018-05-08 2018-05-08 Method and device for user-defined verification mode

Publications (2)

Publication Number Publication Date
CN108650098A CN108650098A (en) 2018-10-12
CN108650098B true CN108650098B (en) 2021-04-20

Family

ID=63749771

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810433357.7A Active CN108650098B (en) 2018-05-08 2018-05-08 Method and device for user-defined verification mode

Country Status (1)

Country Link
CN (1) CN108650098B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110059457B (en) * 2018-11-05 2020-06-30 阿里巴巴集团控股有限公司 Body-building method and device
CN109842611B (en) * 2018-12-14 2023-04-18 平安科技（深圳）有限公司 Identity authentication method, identity authentication device, computer equipment and storage medium
CN110071915B (en) * 2019-04-10 2021-08-06 创新先进技术有限公司 An identity verification product push method, device, device and system architecture
CN111415246B (en) * 2020-04-08 2023-04-18 中国银行股份有限公司 Online business processing method and device for bank outlets
CN113781051A (en) * 2021-09-06 2021-12-10 中国银行股份有限公司 Abnormal operation monitoring method and system
CN113869905A (en) * 2021-09-06 2021-12-31 中国银行股份有限公司 Abnormal transaction monitoring method and system
CN114036494A (en) * 2021-12-02 2022-02-11 神州数码融信软件有限公司 Factorized dynamic authentication process management method
CN113904934B (en) * 2021-12-09 2022-04-08 之江实验室 A kind of high security device configuration method and device based on heterogeneous verification

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1992596A (en) * 2005-12-27 2007-07-04 国际商业机器公司 User authentication device and method
CN101156352A (en) * 2006-01-24 2008-04-02 华为技术有限公司 Authentication method, system and authentication center based on mobile network end-to-end communication
CN105578384A (en) * 2015-05-28 2016-05-11 宇龙计算机通信科技(深圳)有限公司 Method and device for storing business information
CN107018119A (en) * 2016-08-30 2017-08-04 阿里巴巴集团控股有限公司 Authentication system, method and platform

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100213555B1 (en) * 1997-01-22 1999-08-02 윤종용 Method for checking the personalisation of mobile equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1992596A (en) * 2005-12-27 2007-07-04 国际商业机器公司 User authentication device and method
CN101156352A (en) * 2006-01-24 2008-04-02 华为技术有限公司 Authentication method, system and authentication center based on mobile network end-to-end communication
CN105578384A (en) * 2015-05-28 2016-05-11 宇龙计算机通信科技(深圳)有限公司 Method and device for storing business information
CN107018119A (en) * 2016-08-30 2017-08-04 阿里巴巴集团控股有限公司 Authentication system, method and platform

Also Published As

Publication number Publication date
CN108650098A (en) 2018-10-12

Similar Documents

Publication Publication Date Title
CN108650098B (en) Method and device for user-defined verification mode
TWI668589B (en) Identity registration method and device
US11765177B1 (en) System and method for providing a web service using a mobile device capturing dual images
US8151326B2 (en) Using audio in N-factor authentication
US20250392587A1 (en) System and method for authenticating a user to provide a web service
US20150186875A1 (en) Information Configuration Method, Device, System, Client And Server
CN105323253B (en) Identity verification method and device
CN110838010B (en) Service processing method, device, terminal, server and storage medium
CN111030812A (en) Token verification method, device, storage medium and server
CN105868970B (en) authentication method and electronic equipment
US20150242602A1 (en) Network authentication method for secure user identity verification using user positioning information
CN109308416B (en) Business service data processing method, device, system, storage medium and equipment
CN103973711A (en) A verification method and device
CN109831441B (en) Identity authentication method, system and related components
KR20170015038A (en) System and method for user authentication using mobile number and personal information
WO2017049735A1 (en) Fingerprint authentication method, cloud server, fingerprint recognition method, and terminal
CN109496443B (en) Mobile authentication method and system therefor
CN109829273B (en) Identity authentication method, device, system, equipment and readable storage medium
KR20150003297A (en) Method and system using a cyber id to provide secure transactions
CN114707976B (en) Payment methods, user terminals, devices, equipment, systems and media
JP2017102842A (en) Personal identification system, personal identification information output system, authentication server, personal identification method, personal identification information output method, and program
CN112200555B (en) Electronic resource transfer method, device and storage medium
WO2016138743A1 (en) Secure payment method, mobile terminal, and payment authentication server
HK1261856A1 (en) Method and device for user-defined verification modes
HK1261856B (en) Method and device for user-defined verification modes

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1261856

Country of ref document: HK

TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20201022

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Innovative advanced technology Co.,Ltd.

Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant before: Advanced innovation technology Co.,Ltd.

Effective date of registration: 20201022

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Advanced innovation technology Co.,Ltd.

Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands

Applicant before: Alibaba Group Holding Ltd.

GR01 Patent grant
GR01 Patent grant