Authentication system, authentication method and computer-readable medium
The authentication system uses tokenized biometric data and zero-knowledge proofs to secure user identity in financial SaaS systems, addressing security challenges by ensuring only anonymized data is stored and compared, thus protecting user privacy and simplifying authentication processes.
Patent Information
- Application Number
- JP2024003046U
- Authority / Receiving Office
- JP · JP
- Patent Type
- Utility models
- Current Assignee / Owner
- Filing Date
- 2024-09-10
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2034-09-10
AI Technical Summary
Existing financial SaaS systems face security challenges in user authentication, particularly when migrating to the cloud, as they risk exposing sensitive user data to third parties and compromising user privacy.
An authentication system and method that utilizes tokenized biometric data and zero-knowledge proofs to secure user identity, ensuring that only anonymized data is stored and compared, eliminating the need for complex algorithms and reducing the risk of data leakage.
The system effectively protects user privacy by ensuring only anonymized data is stored and compared, simplifying authentication processes and reducing the risk of data exposure, while maintaining high security standards.
Smart Images

Figure 0003249056000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to authentication technology, and more particularly to an authentication system, an authentication method, and a computer-readable medium. [Background technology]
[0002] SaaS (Software as a Service) application technology has become one of the focus tasks of the development of digital transformation in various industries. Taking the financial industry as an example, the development of financial SaaS can bring the following benefits: Eliminate hardware and location limitations, achieve high availability for customers and users who need to provide and / or access financial services, provide high scalability to expand the scope of financial SaaS under permitted resources, and enable financial SaaS to operate independently from software and hardware maintenance schedules for customers and users who need to continuously provide and / or access financial services.
[0003] However, financial services often involve the exchange of various confidential or personal data, and it is necessary to ensure the identity of a user before granting access to the financial services. Moving financial services to the cloud may also result in further security and legal issues arising from the fact that user authentication data provided during user authentication may be leaked or identified by a third party.
[0004] Therefore, there is an unmet need in the art to establish an authentication system, an authentication method, and a computer readable medium to address the above problems. Summary of the Invention
[0005] The authentication system may include a provider authentication device, a storage device connected to the provider authentication device, a user device connected to the provider authentication device, and a client device connected to the provider authentication device and the user device, wherein during an enrolment phase of the authentication system, the user device is configured to validate an enrolment request of a user and send the enrolment request to the client device, the client device receiving the enrolment request and generating, in response to the enrolment request, an enrolment data set comprising a user enrolment identifier and first biometric data of the user; The enrollment data set is configured to transmit to a provider authentication device, the provider authentication device configured to receive the enrollment data set, process the first biometric data in the enrollment data set to generate first tokenized biometric data, concatenate a user enrollment identifier with the first tokenized biometric data to generate authentication baseline data, store the authentication baseline data in a storage device, and erase the first biometric data from the enrollment data set, the storage device configured to save the authentication baseline data. During an authentication phase of the authentication system, the user device is configured to receive a service access request and the second biometric data of the user, send the service access request to the client device, and send the second biometric data to the provider authentication device, the client device is configured to receive the service access request and send the user's identity identifier to the provider authentication device in response to the service access request, the provider authentication device is configured to receive the identity identifier, retrieve authentication baseline data from the storage device according to the identity identifier corresponding to the user registration identifier in the authentication baseline data, receive the second biometric data, process the second biometric data to generate second tokenized biometric data, concatenate the second tokenized biometric data with the identity identifier to generate authentication data, and if the authentication result of authenticating the authentication data using the authentication baseline data is successful, approve the service access request from the user device and erase the second biometric data.
[0006] The computer readable medium stores computer executable code that, when executed, performs an authentication method.
[0007] These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings. [Brief description of the drawings]
[0008] [Figure 1] FIG. 2 is a schematic diagram showing the arrangement of elements of the authentication system of the present invention. [Diagram 2] FIG. 2 is a flow diagram illustrating the enrollment stage of the authentication method of the present invention. [Diagram 3] FIG. 2 is a flow diagram illustrating the authentication stage of the authentication method of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] The following description of the embodiments is for explaining the implementation of the present invention, and a person skilled in the art of the present invention can easily understand the advantages and effects of the present invention based on the contents of this specification, and / or can apply the present invention to other embodiments. Therefore, any element described in the present invention can be combined with any other element disclosed in the embodiments of the present invention.
[0010] The order of the drawings shown in the accompanying drawings of this disclosure is merely for illustrating the embodiments described herein so that those skilled in the art can read and understand the present invention therefrom, and is not intended to limit the scope of the present disclosure. Any changes, modifications or adjustments to the above features should be included within the scope of the technical content of the present disclosure, as long as they do not affect the designed purpose and effect of the present invention.
[0011] As used in this specification, when a description is described as "comprising," "including," or "having" a limitation, unless otherwise specified, the description may further include other elements, structures, areas, parts, facilities, devices, systems, steps, connections, modules, units, etc., and does not exclude other elements.
[0012] As used herein, terms such as "first", "second", etc. are merely used to describe or distinguish elements, such as components, structures, areas, parts, facilities, devices, systems, steps, connections, modules, units, etc., and are not used to limit the scope of implementation of the present disclosure or to limit the spatial order of elements. Additionally, unless otherwise specified, singular terms such as "a" and "an" also refer to plural terms, and terms such as "or" and "and / or" can be used interchangeably.
[0013] As used herein, the term "authentication" may be used interchangeably with terms such as "verification," "authorization," "determination," "decision," "verification," "assessment," "ratification," "verification," "check," etc. In the event that a message, data, or command is authenticated, phrases such as "data authentication," "command authentication," "data verification," or "command verification" may be used.
[0014] FIG. 1 is a schematic diagram showing the arrangement of elements of an authentication system 1. The authentication system 1 may include a user device 100, a client device 200, a provider authentication device 300, and a storage device 400. Each element of the authentication system may be connected to each other in any suitable wired or wireless manner. In the embodiment described herein, the provider may refer to a cloud service provider that provides a financial SaaS application, the client may refer to a financial institution that subscribes to the provider for the financial SaaS application, and the user may refer to any individual, organization, or group that requests access to a financial service from the client. The authentication system 1 may be used to perform a user authentication operation through an integrated financial SaaS application, and upon successful authentication, allow the user to access the financial service from the client. However, the authentication system 1 may also be applied to a user authentication operation of a SaaS application in other industry fields, and the service provided by the client may refer to other services in other industry fields.
[0015] User device 100 may be embodied as any device for accessing financial services, such as a personal computer, a tablet, a mobile device, an application, a virtual machine, or any combination thereof. In the embodiments described herein, user device 100 may include an automated teller machine and / or a mobile device having a financial services application and may be used to access financial services by a user operating on user device 100.
[0016] Client device 200 may be implemented as a device that provides financial services to a user through an integrated SaaS application, such as a mainframe computer, a personal computer, a tablet, a mobile device, a cloud computing device, an application, a server, a virtual machine, or any combination thereof. In embodiments described herein, a client may subscribe to a financial SaaS application and then integrate the financial SaaS application into client device 200 to provide financial services to the user.
[0017] The provider authentication device 300 may be implemented as any device that performs user authentication operations, such as a mainframe computer, a personal computer, a tablet, a mobile device, a cloud computing device, an application, a server, a virtual machine, or any combination thereof. In the embodiments described herein, the user authentication operations performed by the provider authentication device 300 may be integrated as part of a financial SaaS application or may function as an add-on item in a financial SaaS application provided by the provider. The user authentication operations may only be integrated into a financial service if a client establishes an additional subscription with the provider.
[0018] Storage device 400 may be implemented as any suitable cloud storage device, server, memory, database, and / or hard drive. In embodiments described herein, storage device 400 may be used to store data generated from performing user authentication operations and may be used to provide data necessary for performing user authentication operations. In some other embodiments, storage device 400 may be managed by a provider or a client.
[0019] In some embodiments, an authentication method may be further provided. The authentication method may be used to realize a user authentication operation using the user device 100, the client device 200, the provider authentication device 300 and the storage device 400. The authentication method may include a registration stage and an authentication stage. Details of the authentication method may be understood through Figures 2, 3 and the following description.
[0020] Additionally, a computer readable medium may be provided that stores computer executable code that, when executed, may be used to perform the authentication method.
[0021] FIG. 2 is a flow diagram showing steps S201 to S210 (S2010) of the registration stage, and the entity performing the steps and the direction of data transmission may be understood by the direction of the arrows and the positional relationship between the steps, the user device 100, the client device 200, the provider authentication device 300 and the storage device 400.
[0022] In step S201, the user device 100 may send a registration request to the client device 200. Here, a user who needs financial services may operate the user device 100 to input registration data and first biometric authentication information. The registration request may be a bank account registration request. The first biometric authentication data may be at least one of a user's face recognition information, a user's fingerprint recognition information, a user's vein recognition information, a user's voice pattern recognition information, a user's iris recognition information, and a user's signature recognition information, and the first biometric authentication data may be obtained by a user operating a camera lens, a sensing panel, a microphone, and / or a scanning device of the user device 100.
[0023] In step S202, the client device 200 can receive an enrollment request, enrollment data, and first biometric authentication data from the user device 100, generate an enrollment data set according to the enrollment request, and send the enrollment data set to the provider authentication device 300. Here, the client device 200 can generate a user enrollment identifier corresponding to the user according to the content of the enrollment data, compress the user enrollment identifier and the first biometric authentication data into an enrollment data set, and send the enrollment data set to the provider authentication device 300. The user enrollment identifier may be a code formed of any form of letters, numbers, letters, and / or symbols, and may be used to represent the identity of the user during a user authentication operation and distinguish the user from other users who use financial services.
[0024] In step S203, the provider authentication device may receive the enrollment data set, process the first biometric data in the enrollment data set to generate first tokenized biometric data, and generate authentication baseline data by concatenating a user enrollment identifier with the first tokenized biometric data. Here, the first biometric data may be converted (tokenized) into anonymized homogeneous data by any data tokenization technique to obtain the first tokenized biometric data. The use of data tokenization technique to convert the first biometric data is helpful to replace confidential data that may leak user privacy with a unique identification symbol, retain necessary information contained in the first biometric data, and protect user privacy when performing user authentication operation using the first tokenized biometric data. Also, other anonymization and / or encryption operations may be performed on the first biometric data to obtain the first tokenized biometric data, so as to further ensure the security of the first biometric data during identity authentication tasks. Additionally, the authentication baseline data generated in step S203 may be formed by combining the user enrollment identifier and the first tokenized biometric data in any order or combination and may be used as a comparison baseline for authenticating authentication data uploaded during the authentication phase. For example, if the user enrollment identifier is expressed as "USRID1235XX" and the first tokenized biometric data is expressed as "USRIMG2468XX", the generated authentication baseline data may be expressed as "USRID1235XX-USRIMG2468XX".
[0025] In step S204, the provider authentication device 300 can determine whether the generation of the authentication baseline data is successful. "No" indicates that the generation of the authentication baseline data is unsuccessful, and then execute step S205 to erase the first biometric authentication data from the enrollment data set, and execute step S210 to communicate a rejection notice of the user's enrollment request to the user device 100 (e.g., via the client device 200). "Yes" indicates that the generation of the authentication baseline data is successful, and then execute step S206 to store the authentication baseline data in the storage device 400. Regardless of whether the generation of the authentication baseline data is successful or not, the first biometric authentication data is erased after use. Therefore, the system 1 can realize zero-knowledge proof of the user authentication operation without recording the first biometric authentication data, and prevent the leakage of the user's privacy, by only storing the anonymized first tokenized biometric authentication data.
[0026] In step S207, the provider authentication device 300 may determine whether the authentication baseline data is successfully stored in the storage device 400. "No" indicates that the authentication baseline data storage has failed, and then step S210 may be performed to communicate a rejection notice of the user's registration request to the user device 100 (e.g., via the client device 200). "Yes" indicates that the authentication baseline data storage has been successful, and then step S208 may be performed to return a registration record to the client device 200, and step S209 may be performed to communicate an approval notice of the user's registration request to the user device 100 (e.g., via the client device 200). The registration record returned in step S208 may include a user registration identifier of the registration data set. The client device 200 may store the user registration identifier (e.g., in an internal memory of the client device 200) and accordingly identify the user during access to financial services and store related data.
[0027] FIG. 3 is a flow diagram showing steps S301 to S310 of the authentication stage, and the entity performing the steps and the data transmission direction may be understood from the direction of the arrows and the positional relationship between the steps, the user device 100, the client device 200, the provider authentication device 300, and the storage device 400.
[0028] In step S301, the user device 100 can send a service access request to the client device 200. Here, a user who needs financial services can operate the user device 100 to input service access data. The service access data may include at least one of the following: a user's username, a user's user passcode, a user's identity information, a user's signature information, a user's debit card identifier, a user's debit card verification number, a user's payment request information, a user's withdrawal request information, a user's deposit / foreign exchange request information, a user's loan request information, a user's account management request, a user's transaction information, and a user's financial management request, and the service access data may be input by the user operating an input window displayed by the user device 100, a built-in card slot of the user device 100, or an external / attached scanner device of the user device 100.
[0029] In step S302, the client device 200 receives the service access request and the service access data from the user device 100, generates an identity identifier of the user according to the service access data, and sends the identity identifier to the provider authentication device 300. If the client device 200 has stored the user registration identifier of the user from the successful registration, it may generate the identity identifier by searching the corresponding user registration identifier according to the service access data, and output the user registration identifier as the identity identifier. If the client device 200 does not store the user registration identifier in advance, the identity identifier may be generated from the content of the service access data, and may be a code formed of any form of letters, numbers, sentences, and / or symbols, and the form of the identity identifier may be the same as the user registration identifier.
[0030] In step S303, the provider authentication device 300 can retrieve authentication baseline data from the storage device 400 according to the identity identifier. Here, the storage device 400 can retrieve authentication baseline data having a user registration identifier corresponding to the identity identifier, and return the authentication baseline data to the provider authentication device 300. For example, if the identity identifier received by the provider authentication device 300 is expressed as "USRID1235XX" and one authentication baseline data stored in the storage device 400 is expressed as "USRID1235XX-USRIMG2468XX", the storage device 400 can return one authentication baseline data to the provider authentication device 300 for authentication in a later step.
[0031] In step S304, the provider authentication device 300 may receive the authentication baseline data and request the user (e.g., via the client device 200) to upload second biometric data and a device identifier of the user device 100. The second biometric data may include at least one of the following: face recognition information of the user, fingerprint recognition information of the user, vein recognition information of the user, voice pattern recognition information of the user, iris recognition information of the user, and signature recognition information of the user, and the second biometric data may be obtained by the user operating a camera lens, a sensing panel, a microphone, and / or a scanning device of the user device 100. The device identifier may be at least one of a field code of the user device 100, a device serial number of the user device 100, a mobile device identifier of the user device 100, an Internet Protocol address of the user device 100, a media access control address of the user device 100, and a unique device identifier of the user device 100, and the device identifier may be automatically extracted by the user device 100 upon request of the provider authentication device 300.
[0032] In step S305, the provider authentication device 300 may receive the device identifier and determine the validity of the device identifier. "No" indicates that the device identifier is invalid and the user device 100 may be a problematic device, and then step S308 may be performed to erase the second biometric data and step S310 may be performed to communicate a denial of the user's service access request to the user device 100 (e.g., via the client device 200). "Yes" indicates that the device identifier is valid and authentication may proceed to a later step.
[0033] In step S306, the provider authentication device 300 may receive the second biometric data, process the second biometric data to generate second tokenized biometric data, and generate authentication data by concatenating the identity identifier with the second tokenized biometric data. Here, the same data tokenization technique for generating the first tokenized biometric data may be utilized to generate the second tokenized biometric data from the second biometric data. Thus, it is possible to prevent privacy data included in the user's second biometric data uploaded during the authentication phase from being leaked. Similarly, other anonymization and / or encryption operations may be performed on the second biometric data to obtain the second tokenized biometric data, which further ensures the security of the second biometric data during the identity authentication task. Also, the authentication data generated in step S306 may be formed by combining the identity identifier and the second tokenized biometric data in the same order or combination as the user registration identifier and the first tokenized biometric data included in the authentication baseline data. For example, if the identity identifier is expressed as "USRID1235XX" and the second tokenized biometric data is expressed as "USRIMG2468XX", the generated authentication data may be expressed as "USRID1235XX-USRIMG2468XX".
[0034] In step S307, the provider authentication device 300 may compare the difference between the authentication data and the authentication baseline data to generate an authentication result, and determine whether the authentication result of authenticating the authentication data using the authentication baseline data is successful. "No" indicates that the authentication is unsuccessful, and then step S308 may be performed to erase the second biometric authentication data, and step S310 may be performed to communicate a rejection notice of the user's service access request to the user device 100 (e.g., via the client device 200). "Yes" indicates that the authentication is successful, and then step S308 may be performed to erase the second biometric authentication data, and step S309 may be performed to communicate an approval notice of the user's service access request to the user device 100 (e.g., via the client device 200), so that the user may proceed to operate the user device 100 to access financial services on the client device 200.
[0035] For example, if the authentication data is expressed as "USRID1235XX-USRIMG2400XX" and the authentication baseline data is expressed as "USRID1235XX-USRIMG2468XX", the provider authentication device 300 can determine that the authentication result of authenticating the authentication data using the authentication baseline data is unsuccessful, and then execute steps S308 and S310 to prohibit the user from accessing financial services. If the authentication data and the authentication baseline data are both expressed as "USRID1235XX-USRIMG2468XX", the provider authentication device 300 can determine that the authentication result of authenticating the authentication data using the authentication baseline data is successful, and then execute steps S309 and S310 to allow the user to access financial services. In other words, identity authentication of a user who needs access to financial services only requires authenticating the difference between the authentication data and the authentication baseline data. Therefore, complex algorithms and encoding / decoding operations can be omitted, and the configuration cost for migrating financial services to the cloud can be greatly reduced. Furthermore, regardless of whether the authentication is successful, the second biometric authentication data is erased after use, and the system 1 does not store a record of the second biometric authentication data, thereby achieving zero-knowledge proof of the user authentication operation and preventing the leakage of user privacy.
[0036] Based on the above, the authentication system, authentication method, and computer-readable medium of the present invention are useful for realizing user identification tasks based on zero-knowledge proofs, anonymizing confidential or personal data when migrating services to the cloud, simplifying the steps required for user authentication operations, and reducing the risk that authentication information required for user authentication operations will be leaked to or identified by a third party.
[0037] Those skilled in the art will readily recognize that numerous modifications and variations of the apparatus and method may be made while retaining the teachings of this invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.
Claims
1. 1. An authentication system, comprising: A provider authentication device; a storage device connected to the provider authentication device; a user device connected to the provider authentication device; a client device connected to the provider authentication device and the user device, During the registration phase of said authentication system, The user device includes: Verify the user's registration request, configured to send the registration request to the client device; The client device includes: receiving the registration request; generating an enrollment data set in response to the enrollment request, the enrollment data set including a user enrollment identifier and first biometric data for the user; configured to transmit the enrollment data set to the provider authentication device; The provider authentication device includes: receiving the enrollment data set; processing the first biometric data in the enrollment data set to generate first tokenized biometric data; Concatenating the user enrollment identifier with the first tokenized biometric data to generate authentication baseline data; configured to store the authentication baseline data in the storage device and to erase the first biometric data from the enrollment data set; the storage device is configured to store the authentication baseline data; During an authentication phase of the authentication system, The user device includes: receiving a service access request and second biometric data of the user; Sending the service access request to the client device; configured to transmit the second biometric authentication data to the provider authentication device; The client device includes: receiving the service access request; configured to transmit an identity identifier of the user to the provider authentication device in response to the service access request; The provider authentication device includes: receiving the identity identifier, and retrieving the authentication baseline data from the storage device according to the identity identifier that corresponds to the user registration identifier of the authentication baseline data; receiving the second biometric data; processing the second biometric data to generate second tokenized biometric data; Concatenating the second tokenized biometric data with the identity identifier to generate authentication data; and upon successful authentication of the authentication data using the authentication baseline data, the authentication system is configured to approve the service access request from the user device and erase the second biometric data.
2. the user device includes an automated teller machine and / or a mobile device having a financial services application; the registration request is a bank account registration request; The authentication system of claim 1 , wherein the service access request is a financial service access request.
3. During said registration phase: The user device includes: confirming the enrollment data and the first biometric authentication data set by the user using the user device; further configured to transmit the enrollment data and the first biometric data to the client device; The client device includes: receiving the enrollment data and the first biometric data; generating the user enrollment identifier using the first biometric data; further configured to generate the enrollment data set using the user enrollment identifier and the first biometric data; The provider authentication device includes: The authentication system of claim 1 , further configured to transmit the user enrollment identifier of the enrollment data set to the client device after storing the authentication baseline data in the storage device.
4. the registration data includes the user's username, the user's user passcode, the user's identity information, and / or the user's signature information; 4. The authentication system of claim 3, wherein the first biometric authentication data includes face recognition information of the user, fingerprint recognition information of the user, vein recognition information of the user, voice pattern recognition information of the user, iris recognition information of the user, and / or signature recognition information of the user.
5. During said authentication phase, The user device includes: Verifying service access data imported by the user using the user device; further configured to transmit the service access data to the client device; The client device includes: further configured to generate the identity identifier of the user in response to the service access data; The provider authentication device includes: The authentication system of claim 1 , further configured to, upon successful authentication of the authentication data using the authentication baseline data, enable the client device to provide a service to the user via the user device in accordance with the service access data.
6. the service access data includes the user's username, the user's user passcode, the user's identity information, the user's signature information, the user's debit card identifier, the user's debit card verification number, the user's payment request information, the user's withdrawal request information, the user's deposit / foreign exchange request information, the user's loan request information, the user's account management request, the user's transaction information, and / or the user's financial management request; 6. The authentication system of claim 5, wherein the second biometric authentication data includes face recognition information of the user, fingerprint recognition information of the user, vein recognition information of the user, voice pattern recognition information of the user, iris recognition information of the user, and / or signature recognition information of the user.
7. During said authentication phase, The user device includes: Extracting a device identifier of the user device; further configured to transmit the device identifier to the provider authentication device; The provider authentication device includes: receiving the device identifier; The authentication system of claim 1 , further configured to reject the service access request from the user device and erase the second biometric data if the device identifier is authenticated as invalid.
