JP7021790B2 - Providing access to structured stored data - Google Patents

Description

The present invention relates to the field of data access. More specifically, the present invention relates to, but is not limited to, authenticating access to data.

As cybercrime such as account hacking, fraud, financial crime and industrial espionage continues to grow, securing access to sensitive data is a challenge. Thieves and hackers use a variety of methods to infer usernames and passwords to access system and secure data.

Some online providers address security concerns by requiring user authentication with increasingly complex passwords. However, in this e-commerce era, the number of passwords used continues to grow and users must remember them. Therefore, complex passwords are difficult for users to remember.

Another solution adopted by online providers is two-factor authentication or multi-factor authentication. In many cases, this authentication method requires the user to enter a one-time code sent to the user by SMS or email in addition to entering the password. While multi-factor authentication is more secure than a simple password, hackers can still intercept SMS messages and emails to receive the code.

Also, if the user forgets the password, the process for resetting the password is often a multi-step process that frustrates the user. To reset your password, you may answer a password reset question, answer a question about your account number or other personal information, contact a customer service representative, and / or go to the reset link you received by email. Access may be required.

One solution for managing and storing passwords for accessing secure information is password managers. The information in the password manager often includes a username and password, which is kept in a single data store that is accessible after authentication with the master password. Retaining information in a single datastore may be okay if the information being protected is not sensitive, but for some users it is the most sensitive each time they access less sensitive information. You may not want to access even sensitive information. For example, a user who seeks to access information related to a promotional website may not want to access information related to a bank account and an investment account at the same time.

Another problem with password managers is that some password managers have the characteristic that the master password is unrecoverable. A user who has forgotten the unrecoverable master password may permanently lose access to the stored information.

It is an object of the present invention to provide a secure data access authentication method that overcomes the shortcomings of the prior art, or at least is a useful alternative.

According to the first aspect of the present invention, there is provided a method of providing access to a plurality of structured data stores based on a plurality of personal authentication information. The method is to accept the first personal authentication information among a plurality of personal authentication information, and after the authentication of the first personal authentication information, go to the first level data store among the plurality of structured data stores. After providing access to, accepting the second personal authentication information of multiple login data, after authenticating the second personal authentication information, and after authenticating the first personal authentication information, multiple structures. Includes providing access to a second level of datastore of the authenticated datastore.

The method includes accepting a third personal authentication information out of a plurality of personal authentication information, after the authentication of the third personal authentication information, and after the authentication of the first personal authentication information and the second personal authentication information. It may further include providing access to a third level datastore of a plurality of structured datastores.

According to another aspect, at least the alpha personal authentication information among the plurality of personal authentication information can be the first biometric authentication type data.

According to another aspect, the beta personal authentication information among the plurality of personal authentication information can be the second biometric authentication type data different from the first biometric authentication type data.

According to another aspect, the gamma personal authentication information among the plurality of personal authentications can be a third data type, the third data type being the first data type and the second data type. Can be different from.

According to another aspect, at least one of the plurality of structured data stores may contain third party authentication data.

According to another aspect, the third party authentication data may include a password.

According to another aspect, the data store at least one of the plurality of structured data stores may contain at least one of a data file, a number, or a string.

According to another aspect, the plurality of personal authentication information includes at least one of fingerprint data, pin code, voice recording information, voice message data, face image information, iris image information, or retinal image information. good.

The method may further include displaying a datastore user interface containing secure information from at least one of the data stores.

According to another aspect, the step of displaying the data store user interface may display one or more icons associated with the secure information contained in the selected data store of the multiple data stores. Further may be included.

The method is to accept a data store change request for pre-stored secure information, which includes a new data store, accepts, and accepts pre-stored secure information to the new data store. And may be further included.

The methods include accepting website registration image files, recognizing text in website registration image files containing registration-related information, and secure information from multiple data stores that are authorized to access. It may further include associating with the selected data store of.

According to another aspect, the registration-related information includes at least one of a website domain, business name, username, password, password hint, password clue, reset question, icon, or reset answer. May be included.

The methods include displaying a datastore update user interface that contains secure information from a selected secure store among multiple datastores, accepting updated secure information from users, and updating secure. It may further include associating information with the selected datastore.

According to another aspect, at least one of the plurality of personal authentication information may further include accepting at least one of the plurality of personal authentication information from the client device.

According to another aspect, in order to authenticate the first personal authentication information or to authenticate the second personal authentication information, at least one of the plurality of personal authentication information is transmitted to the server. And receiving personal authentication information confirmation from the server may further be included.

According to another aspect, there is a system configured to provide a structured data protection system by any of the methods of the first aspect.

According to another aspect, there is a computer program configured to provide a structured data protection system by any of the methods of the first aspect.

According to another aspect, there is an electronically readable medium configured to store a computer program configured to provide a structured data protection system by any of the methods of the first aspect. do.

A second aspect of the invention provides a method of setting access to a structured data store. In this method, the first personal authentication setting information is accepted, the first saved authentication data based on the first personal authentication setting information is saved in the user profile, and the second personal authentication setting information is stored. Includes accepting and storing a second saved authentication data based on the second personal authentication configuration information in the user profile, to the first level datastore of multiple structured datastores. Authenticating the first personal credential of the plurality of credentials to provide access to includes using the first stored credential data and of the multiple structured data stores. To authenticate the second personal credential of the plurality of credentials for providing access to the second level data store in the second level after authenticating the first personal credential. Includes the use of saved authentication data from.

The method may further include accepting a third personal authentication setting information and storing the third personal authentication setting information in a user profile as a third saved authentication data, which may further include a plurality of structures. To authenticate the third personal authentication information among the plurality of authentication information for providing access to the third level data store of the data store, the first personal authentication information and the second personal authentication information are used. It involves using a third stored authentication data after authenticating the personal authentication information of.

The method may further include accepting the first secure information and associating the first secure information with an alpha data store among a plurality of data stores.

The method may further include accepting the second secure information and associating the second secure information with a beta data store out of a plurality of data stores.

According to another aspect, the alpha personal authentication information among the plurality of personal authentication information can be the first biometric authentication type data.

According to another aspect, the second personal authentication information among the plurality of personal authentication information can be the second biometric authentication type data different from the first biometric authentication type data.

According to another aspect, the gamma personal authentication information among the plurality of personal authentication information can be a third data type, and the third data type is the first data type and the second data. It can be different from the type.

According to another aspect, at least one of the plurality of structured data stores may contain third party authentication data.

According to another aspect, the third party authentication data may include a password.

According to another aspect, the data store at least one of the plurality of structured data stores may contain at least one of a data file, a number, or a string.

According to another aspect, the plurality of personal authentication information includes at least one of fingerprint data, pin code, voice recording information, voice message data, face image information, iris image information, or retinal image information. good.

The method is to accept the website registration image file and to recognize the text in the website registration image file containing the registration related information, which includes the website domain, business name and user. Includes at least one of a name, password, password prompt, password clues, reset question, icon, or reset answer, recognizes and secure information, access is authenticated, multiple. It may further include associating with a selected datastore of the datastores.

According to another aspect, accepting at least one of the first personal authentication confirmation information, the second personal authentication confirmation information, or the third personal authentication confirmation information determines the user input timeout period. It may further include storing the user input timeout period in the user profile.

The method is to accept a data store change request for pre-stored secure information, which includes a new data store, accepts, and accepts pre-stored secure information to the new data store. And may be further included.

According to another aspect, there is a system configured to set up a structured data protection system by any of the methods of the second aspect.

According to another aspect, there is a structured data protection system according to any of the methods of the second aspect.

According to another aspect, there is an electronically readable medium that stores a computer program configured to provide a structured data protection system by any of the methods of the second aspect.

Other aspects of the invention are described in the claims.

Embodiments of the present invention will be described below as mere illustrations with reference to the following accompanying drawings.

FIG. 1 shows a system 100 according to an embodiment of the present invention. FIG. 2 shows a system 200 according to an embodiment of the present invention. FIG. 3 shows a system 300 according to an embodiment of the present invention. FIG. 4 shows method 400 according to an embodiment of the present invention. FIG. 5 shows a structured data store 500 according to an embodiment of the present invention. FIG. 6 shows method 600 according to an embodiment of the present invention. FIG. 7 shows a method 700 according to an embodiment of the present invention. FIG. 8 shows method 800 according to an embodiment of the present invention. FIG. 9 shows a user interface 900 according to an embodiment of the present invention. FIG. 10 shows a user interface 1000 according to an embodiment of the present invention. FIG. 11 shows a user interface 1100 according to an embodiment of the present invention. FIG. 12 shows a system 1200 according to an embodiment of the present invention.

The present invention provides methods, systems, and computer programs for setting up and providing access to multiple structured data stores based on multiple personal authentication information.

FIG. 1 shows a system 100 according to an embodiment. The system 100 includes a client device 102. The system 100 may further include a configuration server 104, a third party server 106, the Internet 108, a biometric device 110, a user profile database 114, and a structured data store 116.

The client device 102 may be operational to set up and provide user access to a plurality of structured data stores based on the plurality of personal authentication information, as described in connection with FIGS. 4-12. can. Further, the configuration server 104 can operate to facilitate and provide access to a plurality of structured data stores based on a plurality of personal authentication information, as described in connection with FIGS. 4 to 12. can do.

Each of the client device 102, the configuration server 104, the third party server 106, and the biometric authentication device 110 may include the processing device 200 shown in FIG. The processing device 200 includes a processor 202, a memory 204, and a communication interface 206. In an embodiment, the processing device 200 may further include a display 208.

Processor 202 may be configured for the execution of computer instructions. When executed on the system 100, the computer instructions execute some or all of the methods described in connection with FIGS. 4-12. In embodiments, processor 202 may include one or any number of processors, as will be appreciated by those of skill in the art.

The memory 204 can be an electronically readable medium or a computer readable medium configured to store computer program instructions. In an embodiment, the memory 204 may include a non-temporary medium.

The stored computer program instructions, when executed on the processor 202, can perform some or all of the methods described in connection with FIGS. 4-12.

In an embodiment, the processor 202 and memory 204 may be incorporated into a custom chipset such as system-on-chip. For example, the processor 202 and memory 204 may be integrated into a custom Snapdragon, Tegra, Mali-400, Cortex, Samsung Exynos, Intel Atom, Apple or Motorola chips, or other types of chips known to those of skill in the art. ..

In embodiments, some of the methods described in relation to FIGS. 4-12 may be stored or performed outside of system 100. For example, some of the methods described in relation to FIGS. 4-12 may be stored or executed in a combination of a server and a cloud storage facility via the Internet 108.

The communication interface 206 can be configured to communicate with a device outside the client device 102 or the configuration server 104. For example, the communication interface 206 can communicate with either the biometric device 110, the user profile database 114, or the structured data store 116.

In an embodiment, the communication interface 206 may include a wired or wireless interface. Communication interface 206 may include short-range or low-power radio standards such as Bluetooth, Bluetooth LE, Zigbee, or Near Field Communication (NFC). Communication interface 206 may further include WIFI, 3G, 4G, Ethernet, or other communications known to those of skill in the art. In an embodiment, the processing device 200 can request, transmit, or receive information, store information, or transmit or receive a message with a remote device via the Internet 108.

In an embodiment, the client device 102 can be a portable or mobile computing device, such as a smartphone, tablet, smartwatch, or wearable device. In another embodiment, the client device 102 can be a computing device, such as a smart TV, video game console, laptop or desktop computer, or app-enabled home hardware.

In an embodiment, the client device 102 can accept input from one or more integrated input devices. However, in another embodiment, the client device 102 may be connected to a cooperating external input device, including one or more biometric devices 110.

The client device 102 or biometric device 110 may include a combination of input devices capable of operating to receive information from humans, animals, or the environment. In an embodiment, the client device 102 or biometric device 110 may include a fingerprint scanner such as a capacitive touch device, an ultrasonic device, or an optical device.

In embodiments, the client device 102 or biometric device 110 may include a face scanning device, such as an optical imaging device, a thermal imaging device, or a 3D scanning device.

In the embodiment, the client device 102 or the biometric device 110 may include an eye scanner. In an embodiment, the eye scanner may include an iris scanner or a retinal scanner that uses a visible, infrared, and / or near-infrared imaging device.

In an embodiment, the client device 102 or biometric device 110 may include a voice detector that may include a microphone device, such as a voice recognition device or a phrase recognition device.

In another embodiment, as will be appreciated by those skilled in the art, the client device 102 or biometric device 110 may include other biometric or biometric devices capable of authenticating the user's identity.

FIG. 1 includes a configuration server 104. The configuration server 104 can be operational to execute instructions or to retrieve and store data in the database. In an embodiment, the configuration server 104 may include a single server or multiple servers in a distributed architecture. In an embodiment, the configuration server 104 can support a relational database, a NoSQL database, a distributed database, or any other database known to those of skill in the art.

FIG. 3 shows a system 300 according to one embodiment. The system 300 can facilitate the setting and provision of access to a plurality of structured data stores based on the plurality of personal authentication information. The system 300 includes a client application 302. The system 300 may further include a configuration server application 304, a third party server application 306, and a biometric application 310.

The configuration server 304 can be configured to accept input from the client application 302 in order to facilitate the setting and provision of access to the plurality of structured data stores based on the plurality of personal authentication information.

The client application 302 can communicate with the third party server application 306.

The client application 302 can communicate with the biometric application 310.

In an embodiment, the client application 302, the configuration server application 304, the third party server application 306, and the biometric application 310 can each run on a separate device. For example, the client application 302 can run on the client device 102, the configuration server application 304 can run on the configuration server 102, the third party server application 306 can run on the third party server 106, and biometric authentication. The application 310 can operate on the biometric authentication device 110.

However, in another embodiment, the functionality of any one of the client application 302, the configuration server application 304, the third party server application 306, and the biometric application 310 may be distributed to additional computing devices. For example, the configuration server application 304 can operate in a group of distributed servers.

FIG. 4 shows method 400, which is an exemplary embodiment that can be performed in combination with client application 302 or configuration server application 304. Method 400 can provide access to a plurality of structured data stores based on the plurality of personal authentication information.

FIG. 5 shows an example of a plurality of structured data stores 500. A data store is a physical or virtual repository for the persistent storage and management of one or more collections of data. In an embodiment, the data store can be a simple file, database, or other repository known to those of skill in the art.

As can be seen from FIG. 5, examples of the plurality of structured data stores 500 include a first level data store 502, a second level data store 504, and a third level data store 506. The third level data store 506 is configured to be accessed after accessing the second level data store 504, and both the third level data store 506 and the second level data store 504 are both. It is configured to be accessed after accessing the first level data store 502.

Users accessing the data stores in the structured data store 500 need to be authenticated prior to access. Authentication is the process of verifying a user's identity using personal authentication information provided by the user. For example, a user accessing the first data store 402 may be authenticated at the first level.

In the embodiment, the personal authentication information may include fingerprint data. The fingerprint data may include data received from the fingerprint scanner. The fingerprint data may include raw data such as a two-dimensional image file, or processed data such as feature extraction information, image checksum, or hash information.

In the embodiment, the personal authentication information may include voice recording information from the voice recognition device. The voice recording information may be text-independent. The voice recording information may include raw data such as an audio file, or processed data that may include voiceprints or feature extraction information. The voice recording information may be used to authenticate the user's voice.

In the embodiment, the personal authentication information may include voice message data from the phrase recognition device. The voice message data is text dependent and may include raw data such as audio files or processed data. Voice message data may be used to authenticate the speaker.

In an embodiment, the personal authentication information may include face image information from a face scanning device. The face image information may include raw data such as an image file or processed data such as feature extraction information, image checksum, or hash information. Face image information may be used to authenticate a user based on one or more features of the face.

In the embodiment, the personal authentication information may include image data of the eyes using an eye scanner. For example, personal authentication information may include iris image information or retinal image information. The image data of the eye may include raw data such as image data or processed data such as feature extraction information, image checksum, or hash information.

In the embodiment, the personal authentication information may include password data or a password.

In the embodiment, the personal authentication information may include pin code data. For example, personal credentials may include a passcode or lock screen pattern.

The examples of personal authentication information presented herein are not intended to be limiting. Those skilled in the art will easily understand that any kind of information that can authenticate a user may be used as personal credentials to provide access to a data store. For example, any kind of biometric information that can be reasonably used to identify the user may be used.

If one data store is configured to be accessed after accessing another, the user must authenticate both data stores before accessing the innermost data store. For example, as shown in FIG. 5, if the second level data store 504 is configured to be accessed after accessing the first level data store 502, the user is configured to access the second level data. Before accessing store 504, it needs to be authenticated in the first level data store 502 and the second level data store 504.

The example of the structured data store 500 includes three structured data stores, but this is not intended to be limiting. In an embodiment, the structured data store 500 may include two, three, or any number of data stores.

In another embodiment, the third level data store 506 does not have to be configured to be accessed after accessing the second level data store 504. For example, the third level data store 506 may be configured to access only the first level data store 502 and then access it.

Method 400 starts from step 402. In step 402, the first personal authentication information 402 out of the plurality of personal authentication information is accepted.

In the embodiment, the accepted personal authentication information may be received from the biometric authentication device integrated in the client device 102 or from the outside of the client device 102 such as the biometric authentication device 110.

Method 400 follows step 404. In step 404, after authentication of the first personal authentication information 402, access to the first level data store among the plurality of structured data stores is provided. For example, access to the first level data store 502 may be provided.

Method 400 follows step 406. In step 406, the second personal authentication information of the plurality of login data is accepted.

Method 400 follows step 408. In step 408, after the authentication of the second personal authentication information and after the authentication of the first personal authentication information, access to the second level data store among the plurality of structured data stores is provided. For example, access to a second level data store 504 may be provided.

Allow access to the first level data store 502 after authentication of the first personal credentials 402 and second level after authentication of both the first personal credentials 402 and the second personal credentials 404. Allowing access to the data store 504 allows the user to set different security levels for the information.

For example, a user may place less sensitive information in a first level data store and higher confidential information in a second level data store. Therefore, if only the less sensitive information in the first level data store is accessed, the user does not even access the more sensitive information in the second level data store.

In an embodiment, the method 400 may include additional steps. For example, method 400 follows steps 410 and 412. In step 410, the third personal authentication information among the plurality of login data may be accepted.

In an embodiment, method 400 may follow step 412. In step 412, after the authentication of the third personal authentication information 410 and after the authentication of the first personal authentication information 402 and the second personal authentication information 406, the data of the third level among the plurality of structured data stores. Access to the store may be provided. For example, access to a third level data store 506 may be provided.

If the third level data store 506 is configured to be accessed after accessing the first and second level data stores 502, 504, the user accesses the third level data store 506. Must be authenticated at all three data store levels. This ensures that the user has a more secure data store for information that the user determines is too sensitive to access using the information contained in the first and second level data stores 502, 504. Can be provided to. Users will also be able to access less sensitive data without having to access the most sensitive data.

By providing access to multiple structured data stores based on multiple personal credentials, the user can protect the information according to the confidentiality of the data as determined by the user. As a result, the user can manage his / her own information with peace of mind.

In embodiments, there may be different levels of data stores with their own personal credentials that must be authenticated for the user to access, as will be appreciated by those of skill in the art.

In the embodiment, the alpha personal authentication information among the plurality of personal authentication information can be the first biometric authentication type data. The biometric authentication type data is data that requires the user to input biometric authentication. For example, biometric type data may include, but is not limited to, fingerprint data, voice data, eye image data, or face image data.

By using biometric type data as personal authentication information, users can come up with strong passwords that secure first-level information stores and avoid the hassle of remembering them. Since it is simply not possible for the user to forget his / her biometric information, the biometric personal authentication information can reduce the need to reset the password. Also, biometric type data can be more secure than passwords. This allows the user to consistently and securely access the information in the first data store.

In the embodiment, the beta personal authentication information among the plurality of personal authentication information can be the second biometric authentication type data different from the first biometric authentication type data.

By using the first type of biometric data for the first personal authentication information and the second type of biometric data for the second personal authentication information, the user does not have to come up with and remember the password. , Easy access to second level data stores.

In the embodiment, the gamma personal authentication information among the plurality of personal authentication information can be a third data type, and the third data type is the first data type and the second data type. It's different. For example, the third personal authentication information can be a third type of biometric data.

For example, the first personal authentication information may include fingerprint data or pin code, the second personal authentication information may include voice recording information or voice message data, and a third accepted personal authentication information. May include face recognition data or eye recognition data.

By assigning different data types to each level of the data store, it provides additional security for the information held in the innermost structured data store, which in the example presented is the third level data store. Will be possible.

In the embodiment, at least one of the plurality of structured data stores contains third party authentication data. Third-party authentication data can be a secure third-party repository or website, a username or username hint, a password or password hint, a password recovery question, answer, or hint, or secure from a third-party server 106. Other information regarding the acquisition of information can be identified.

In the embodiment, the third party authentication data may include a password.

In an embodiment, at least one of a plurality of structured data stores may include at least one of a data file, a number, or a string.

For example, at least one of a plurality of structured data stores may contain a document containing any combination of text, images, video, or audio. At least one of a plurality of structured data stores may further contain other types of data, such as numbers or strings.

Third parties, including secure data in structured data stores, by allowing users to store any combination of data files, numbers, or strings in any one of multiple data stores. Allows data security or password security for the server.

In the embodiment, at least one of the plurality of personal authentication information may be accepted within the user input timeout period.

For example, the user input timeout period may be set during the configuration step. After a user attempts to access a data store, the amount of time spent providing credentials may be measured and compared to the user input timeout period. If the time spent entering personal credentials is too long, the user does not have to be authenticated.

For example, if your personal credentials include a smartphone lock screen pattern and the user attempting to authenticate spends 5 seconds entering the pattern, but the user input timeout period is only 2 seconds, this will bring you to the data store. It can be shown that the subsequent user who tried to access is not the original user.

By providing a user input timeout period, it is possible to incorporate skill levels into the user authentication process. This allows for a more robust authentication process.

In an embodiment, method 400 may follow step 412. In step 412, a data store user interface containing secure information from at least one of the plurality of data stores may be displayed.

In an embodiment, the display of the data store user interface may further include the display of one or more icons associated with the secure information contained in the selected data store of the plurality of data stores.

For example, FIGS. 9, 10, and 11 show examples of data store user interfaces 900, 1000, and 1100, respectively.

As seen in the data store user interface 900, an icon 902 may be displayed that represents secure information available in the second level data store.

After selecting the website icon 902, the data store user interface illustrates a display example of secure information associated with the selected website icon 902.

For example, the data store user interface 1000 is a website called "uefa.com", alex321 @ yahoo. Describe the username com and the password "footbal16".

The data store user interface 900 and the data store user interface 1000 allow the user to display only the secure information that he or she wants to check. This can prevent other secure information from being seen by others, for example in public places.

The data store user interface 1100 shows a third example. The data store user interface 1100 includes an icon 1102, which is displayed next to the website, user name, and password. This allows the user to see all the information in the data store at a glance.

Each datastore provides easy and secure access to secure information, but allows the user to decide which secure information to store in it, and the datastore user interface allows the user to see all of the secure information at a glance. By enabling it, users can feel that they are managing their own secure information.

In the embodiment, the method 400 may further include the steps of the method 600. Method 600 may include step 602. A data store change request 602 regarding pre-stored secure information may be accepted, and the data store change request includes a new data store. The data store change request 602 is a request for changing the data store in which the secure information stored in advance is stored.

In an embodiment, the datastore user interface can provide a simple way for the user to generate a datastore change request 602. For example, the data store user interface 1000 describes the data store level selector 1002. The user may decide to store the pre-stored information about the Union of European Football Associations (UEFA) website login in a new data store, the first level data store 502. After making changes using the data store level selector 1002, the user can press the save button 1004 to save and generate the data store change request 602.

Method 600 may further include step 604. In step 604, the pre-stored secure information may be associated with the new data store.

The data store change request 602 allows the user to manage his or her own data. The user can modify the data store to access the pre-stored secure information and the required authentication associated with it.

Method 600 may further include step 606. In step 606, the website registration image file may be accepted.

The website registration image file 606 is an image of a website that the user registers for secure access or that the user resets secure access. For example, the website registration image file 606 can be a screenshot for a link of a registered user.

In the embodiment, the website registration file 606 can be a screenshot.

Method 600 may further include step 608. In step 608, the text in the website registration image file containing the registration related information may be recognized. For example, text may be recognized using optical character recognition, or other protocols known to those of skill in the art.

In an example, secure information includes at least one of a website domain, business name, username, password, password hint, password clue, password reset question, icon, or password reset answer. You can do it.

Method 600 may further include step 610. In step 610, the secure information may be associated with a selected data store among a plurality of data stores for which access is authenticated. The selected data store may be determined by the user.

This allows the user to enter information in the data store without having to re-enter. This allows more accurate information to be retained in the data store.

Method 600 may further include step 612. In step 612, a data store update user interface containing secure information from a selected secure store among the plurality of data stores may be displayed.

Method 600 may further include step 614. In step 614, the secure information updated by the user may be accepted by the data store update user interface. For example, the data store update user interface allows users to edit secure information.

Method 600 may further include step 616. In step 616, the updated secure information may be associated with the selected data store.

Step 612, 614, and 616 allow the user to update the information held in the data store.

In an embodiment, the steps of method 400 and method 600 may be performed in client application 302. However, in another embodiment, the steps 400 and 600 may be performed on the client application 302 and the configuration server 304.

For example, FIG. 12 shows the system 1200. The system 1200 includes a client application 302 and a configuration server 304.

In the embodiment, at least one of the plurality of personal authentication information may be accepted by the client device. For example, the message 1202 including the personal authentication information received from the user may be transmitted from the client application 302 to the setting server application 304.

In the embodiment, at least one of the plurality of personal authentication information may be transmitted to the server, and the personal authentication information confirmation may be received from the server. The personal authentication information confirmation is a message confirming that the personal authentication information has authenticated the user. For example, message 1204 may be sent from the server application 304 to the client application 302.

FIG. 7 shows an application embodiment according to another embodiment 700. Method 700 may be used to set up access to a structured data store. Method 700 starts from step 702. In step 702, the first personal authentication setting information is accepted.

The first personal authentication setting information is information received when the user sets access to the data store. For example, if the first level data store requires fingerprint personal authentication information, the first personal authentication setting information 702 includes the first fingerprint data.

Method 700 follows step 704. In step 704, the first saved authentication data based on the first personal authentication setting information 702 is saved in the user profile. The saved authentication data is used to authenticate the personal authentication information to be received later.

In the embodiment, for example, when the authentication information is a password, the first stored authentication data can be the same as the first personal authentication setting information.

However, in another embodiment, the first saved authentication data can be different from the first personal authentication setting information. For example, when the first personal authentication setting information 702 includes an image such as a fingerprint image, the first stored authentication data may include one or more features derived from the fingerprint image. Alternatively, the first personal authentication setting information 702 may include an image hash.

The user profile contains saved authentication data that can be used to authenticate the user.

Method 700 follows step 706. In step 706, the second personal authentication setting information is accepted.

Method 700 follows step 708. In step 708, the second saved authentication data based on the second personal authentication setting information is saved in the user profile. To authenticate the first personal credentials of the plurality of credentials to provide access to the first level data store of the plurality of structured data stores, the first stored authentication data The authentication of the second personal credential of the plurality of credentials that includes use and provides access to the second level data store of the plurality of structured data stores is the first. Includes the use of a second stored authentication data after authentication of personal credentials.

By allowing the user to store personal authentication data in the user profile, the structured data store 500 can be configured to have the same advantages as those discussed with respect to FIGS. 4, 5, and 6.

In an embodiment, the method 700 may include additional steps. For example, method 700 may include step 710. In step 710, the third personal authentication setting information may be accepted.

Method 700 may further include step 712. In step 712, the third personal authentication setting information may be stored in the user profile as the third saved authentication data. For the authentication of the third personal authentication information among the plurality of authentication information for providing access to the third level data store among the plurality of structured data stores, the first personal authentication information and the first personal authentication information are used. The use of the third stored authentication data after the authentication of the personal authentication information of 2 may be included.

In an embodiment, the method 700 may include additional steps. For example, method 700 may include any of the steps of method 800.

In an embodiment, the method 800 may include steps 802 and 804. In step 802, the first secure information may be accepted.

In step 804, the first secure information may be associated with an alpha data store out of a plurality of data stores. For example, the alpha data store can be a first level data store 502, a second level data store 504, or a third level data store 506.

In an embodiment, the method 800 may include steps 806 and 808. In step 806, the second secure information may be accepted.

In step 808, the second secure information may be associated with a beta data store out of a plurality of data stores. For example, the beta data store can be a first level data store 502, a second level data store 504, or a third level data store 506.

In the embodiment, the alpha personal authentication information among the plurality of personal authentication information can be the first biometric authentication type data.

In the embodiment, the beta personal authentication information among the plurality of personal authentication information can be the second biometric authentication type data different from the first biometric authentication type data.

In the embodiment, the gamma of the plurality of personal authentication information can be a third data type, and this third data type is different from the first data type and the second data type. can do.

In an embodiment, at least one of the plurality of structured data stores may contain third party authentication data.

In the embodiment, the third party authentication data may include a password.

In an embodiment, at least one of a plurality of structured data stores may include at least one of a data file, a number, or a string.

In an embodiment, the plurality of personal authentication information may include at least one of fingerprint data, pin code, voice recording information, voice message data, face image information, iris image information, or retinal image information.

In an embodiment, the method 700 may further include step 606, step 608, and step 610 of the method 600.

In the embodiment, the acceptance of at least one of the first personal authentication confirmation information, the second personal authentication confirmation information, or the third personal authentication confirmation information further includes steps 810 and 812 of the method 800. You can do it.

In step 810, the user input timeout period may be determined.

In step 812, the user input timeout period may be stored in the user profile.

By providing structured access to secure information in structured data stores, users can provide secure access to information of different levels of confidentiality so that users are safe with their information. , And you can feel that you are properly managing where the information is held.

Although the present invention has been exemplified by using the description of the embodiment and the description of the embodiment has been given in considerable detail, the applicant expresses that the scope of the appended claims is limited in such detail or in any sense. Not intended. Additional benefits and modifications can be easily conceived by those skilled in the art. Thus, the invention, which has a wide range of aspects, is not limited to specific details, exemplary devices and methods, and exemplary examples presented and described. Accordingly, deviations from such details may be made that do not deviate from the intent or scope of the applicant's general concept of the invention.

Claims (33)

In a way to provide access to multiple structured data stores in a database based on multiple personal credentials.
A step in which the client device receives the first personal authentication information among the plurality of personal authentication information from the user, and
After the authentication of the first personal authentication information, the client device is a step of providing the user's access to the first level data store among the plurality of structured data stores, the first step . Steps where the level data store stores multiple username / password pairs to access one of multiple servers, and
After the user is provided with access to the first level data store, the user obtains one of the usernames / passwords in the first level data store and the user in the client device. Steps to access the server using first name / password,
A step in which the client device receives a second personal authentication information out of the plurality of personal authentication information from the user .
After the authentication of the second personal authentication information and after the authentication of the first personal authentication information, the client device accesses the user's access to the second level data store among the plurality of structured data stores. A step in which the second level data store stores a plurality of username / password pairs for accessing one of the plurality of servers.
After the user is provided with access to the second level data store, the user obtains one of the usernames / passwords in the second level data store and the user in the client device. Steps to access the server using first name / password,
A step in which the client device receives a third personal authentication information among the plurality of personal authentication information from the user, and
After the authentication of the third personal authentication information, and after the authentication of the first personal authentication information and the second personal authentication information, the client device is the third level of the plurality of structured data stores. A step of providing user access to a data store of the third level, wherein the third level data store stores multiple username / password pairs for accessing one of multiple servers. With a certain step
After the user is provided with access to the third level data store, the user obtains one of the usernames / passwords in the third level data store and the user in the client device. Including the step of accessing the server using the first name / password.
A method characterized in that the first personal authentication information, the second personal authentication information, and the third personal authentication information are of different types from each other. The method according to claim 1 , wherein the alpha personal authentication information among the plurality of personal authentication information is a type of the first biometric authentication data . In the method according to claim 2 , the beta personal authentication information among the plurality of personal authentication information is characterized by being a second biometric data type different from the first biometric data type. How to. In the method according to claim 3 , the gamma personal authentication information among the plurality of personal authentication information is the type of the third biometric authentication data, and the type of the third biometric authentication data is the first biometric authentication. A method characterized by being different from the type of data and the type of the second biometric data . The method according to any one of claims 1 to 4 , wherein at least one of the plurality of structured data stores includes third-party authentication data. The method according to claim 5 , wherein the third-party authentication data includes a password. In the method according to any one of claims 1 to 6 , at least one of the plurality of structured data stores includes at least one of a data file, a number, or a character string. A method characterized by. In the method according to any one of claims 1 to 7 , the plurality of personal authentication information includes fingerprint data, pin code, voice recording information, voice message data, face image information, iris image information, or retinal image information. A method comprising at least one of. In the method according to any one of claims 1 to 8 .
A method comprising: the client device further comprising displaying a data store user interface containing secure information from at least one of the plurality of data stores. In the method of claim 9 , the step of displaying the data store user interface is one in which the client device is associated with the secure information contained in the at least one of the plurality of data stores. A method characterized by further including a step of displaying one or more icons. In the method according to any one of claims 1 to 10 .
The step in which the client device accepts a data store change request relating to pre-stored secure information, wherein the data store change request includes a new data store, and a step of accepting the data store change request.
A step in which the client device associates the pre-stored secure information with the new data store.
A method characterized by further inclusion. In the method according to any one of claims 9 to 11 .
The step in which the client device accepts the website registration image file,
A step in which the client device recognizes the text in the website registration image file containing registration-related information.
A step in which the client device associates the secure information with a selected data store among the plurality of data stores for which access is authenticated.
A method characterized by further inclusion. In the method of claim 12 , the registration-related information may be a website domain, business name, username, password, password hint, password clue, reset question, icon, or reset answer. A method comprising at least one. In the method according to any one of claims 1 to 13 .
A step in which the client device displays a data store update user interface containing secure information from a selected secure store among the plurality of data stores.
A step in which the client device receives updated secure information from the user,
A step in which the client device associates the updated secure information with the selected data store.
A method characterized by further inclusion. In the method according to any one of claims 1 to 14 , the step of accepting at least one of the plurality of personal authentication information is the step.
A method comprising: the client device further includes a step of accepting at least one of the plurality of personal authentication information from the client device. In the method according to any one of claims 1 to 15 , the step of authenticating the first personal authentication information or the step of authenticating the second personal authentication information is the step.
A step in which the client device transmits the personal authentication information of at least one of the plurality of personal authentication information to the server.
When the client device receives a personal authentication information confirmation from the server,
A method characterized by further inclusion. A structured data protection system configured to perform the method according to any one of claims 1-16 . An electronically readable medium comprising a command for performing the method according to any one of claims 1 to 16 . How to set up access to a structured data store,
In the client device, the step of accepting the first personal authentication setting information,
In the client device, a step of saving the first saved authentication data based on the first personal authentication setting information in the user profile, and
The step of accepting the second personal authentication setting information in the client device ,
In the client device, a step of saving the second saved authentication data based on the second personal authentication setting information in the user profile, and
The step of accepting the third personal authentication setting information in the client device,
In the client device, the step of saving the third personal authentication setting information as the third saved authentication data in the user profile, and
Including
The step of authenticating the first personal authentication information of the plurality of credentials for providing access to the first level data store of the plurality of said structured data stores in the client device is described above. Including the step of using the first saved authentication data
In the client device, the step of authenticating the second personal credentials of the plurality of credentials to provide access to the second level data store of the plurality of structured data stores . A step of using the second stored authentication data is included after the step of authenticating the first personal authentication information.
In the client device, the step of authenticating the third personal authentication information of the plurality of credentials for providing access to the third level data store of the plurality of the structured data stores is described above. A step of using the first stored authentication data is included after the step of authenticating the first and second personal authentication information.
The first, second, and third level data stores store multiple username / password pairs to access one of the plurality of servers.
After the user accesses each of the first, second, and third level data stores, the user obtains one of the usernames / passwords in the corresponding data store and the username / password. Use to access the relevant server and
The first, second and third personal authentication information are of different types from each other, and at least one personal authentication information must be authenticated and acquired within a user timeout period. Method. In the method of claim 19 .
In the client device, the step of accepting the first secure information and
A step of associating the first secure information with an alpha data store among the plurality of data stores in the client device .
A method characterized by further inclusion. In the method of claim 20 ,
The step of accepting the second secure information in the client device ,
A step of associating the second secure information with a beta data store among the plurality of data stores in the client device .
A method characterized by further inclusion. The method according to any one of claims 19 to 21 , wherein the alpha personal authentication information among the plurality of personal authentication information is the type of the first biometric authentication data . In the method according to claim 22 , the beta personal authentication information among the plurality of personal authentication information is a second biometric data type different from the first biometric data type . How to. In the method according to claim 23 , the gamma personal authentication information among the plurality of personal authentication information is a third biometric authentication data type , and the third biometric authentication data type is the first biometric authentication data. A method characterized by being different from the type of authentication data and the type of the second biometric authentication data . The method according to any one of claims 19 to 24 , wherein at least one of the plurality of structured data stores includes third-party authentication data. 25. The method of claim 25 , wherein the third party authentication data includes a password. In the method according to any one of claims 19 to 26 , at least one of the plurality of structured data stores includes at least one of a data file, a number, or a character string. A method characterized by. In the method according to any one of claims 19 to 27 , the plurality of personal authentication information includes fingerprint data, pin code, voice recording information, voice message data, face image information, iris image information, or retinal image information. A method comprising at least one of. In the method according to any one of claims 22 to 28, which cites claim 21 or claim 21 .
In the client device, the step of accepting the website registration image file and
The step of recognizing the text in the website registration image file containing the registration-related information on the client device, wherein the registration-related information includes a website domain, a business name, a user name, a password, a password prompt, and a password. A step to recognize, including at least one of a clue, a reset question, an icon, or a reset answer.
In the client device, the step of associating the first or second secure information with a selected data store among the plurality of data stores for which access is authenticated.
A method characterized by further inclusion. In the method according to any one of claims 19 to 29 , at least one of the first personal authentication setting information, the second personal authentication setting information, or the third personal authentication setting information is used. The steps to accept are
In the client device, the step of determining the user input timeout period and
In the client device, the step of saving the user input timeout period in the user profile, and
A method characterized by further inclusion. In the method according to any one of claims 19 to 30 ,
In the client device, a step of accepting a data store change request relating to pre-stored secure information, wherein the data store change request includes a new data store, and a step of accepting the data store change request.
In the client device, the step of associating the pre-stored secure information with the new data store,
A method characterized by further inclusion. A system configured to set up a structured data protection system by the method of any one of claims 19-31 . An electronically readable medium comprising a command for performing the method according to any one of claims 19 to 31 .

Images