# US 2020/0401721 A1 · System and method for associating multiple logins to a single record in a database

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0401721 A1
- Document ID: US20200401721A1
- Status: Published application
- Kind: A1
- Application number: 16/910,401
- Filed: 2020-06-24
- Published: 2020-12-24
- Earliest claimed: 2019-06-24
- Assignees: Main Sequence Technology, Inc.
- Applicants: Main Sequence Technology, Inc.
- Inventors: Michael H. Snyder
- Web page: https://patentgrep.com/patent/US20200401721A1

## CPC

- G06F 21/6227: {where protection concerns the structure of data, e.g. records, types, queries}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 21/45: Structures or tools for the administration of authentication
- G06F 2221/2131: Lost password, e.g. recovery of lost or forgotten passwords
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for resolving ambiguity in computer data includes processing a record creation request transmitted from a computing device. The record creation request includes entity creation data and a login key. The login key includes a primary identifier and a password. The method also includes executing a matching algorithm with a selectable combination of the entity creation data at an entity database to identify a single entity record matching a selectable combination of the record creation request. The single entity record is linked to multiple different login keys. The method also includes updating one or more attributes of the single entity record with the entity creation data. Further, the method includes storing session data created during a session associated with the login key by using the login key to segregate the session data in the entity database, and linking the session data to the single entity record.

## Claims

### Claim 1

A computer-implemented method for resolving ambiguity in computer data, comprising:
processing a record creation request transmitted from a computing device, the record creation request including entity creation data and a login key, wherein the login key includes a primary identifier and a password;
executing a matching algorithm with a selectable combination of the entity creation data at an entity database to identify a single entity record matching a selectable combination of the record creation request, wherein the single entity record is linked to multiple different login keys;
updating one or more attributes of the single entity record with the entity creation data; and
storing session data created during a session associated with the login key by using the login key to segregate the session data in the entity database, and linking the session data to the single entity record.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the entity creation data is extracted from an entity creation interface and transmitted from the computing device via the record creation request, the entity creation interface having one or more data entry methods configured to receive the entity creation data and the login key.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the entity creation data includes an email address, an entity name, and a device identifier, and the selectable combination of the entity creation data includes one or more of the email address, the entity name, and the device identifier.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the entity database includes an entity record table or index, an authentication table or index, and a data cache object.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4, including transmitting to the computing device the session data created during a session associated with the login key in the data cache object.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, including determining if pre-existing data linked with the session and the login key is stored in the data cache object, and transmitting the pre-existing data to the computing device.

### Claim 7 (depends on 4)

The computer-implemented method of claim 4, processing a further entity creation request associated with the single entity record, the further entity creation request including further entity creation data and a further login key comprising a further primary identifier and a further password, wherein the further login key is different than the login key.

### Claim 8 (depends on 7)

The computer-implemented method of claim 7, including updating the single entity record according to the further entity creation data thereby maintaining a single entity records for a plurality of entity creation requests with different login keys.

### Claim 9 (depends on 7)

The computer-implemented method of claim 7, including granting read-only access to session data associated with the further login key in the data cache object.

### Claim 10 (depends on 4)

The computer-implemented method of claim 4, including receiving a password reset request, the password reset request including a reset login key comprising a reset primary identifier and a reset password.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10, including inserting the reset login key in the authentication table.

### Claim 12 (depends on 11)

The computer-implemented method of claim 11, including retrieving from the data cache object a most recent data cache record associated with the single entity record, and updating the most recent data cache record with the reset login key, and deleting remaining records in the data cache object associated with the single entity record, and linking remaining records in the authentication table associated with the single entity record with the most recent data cache record.

### Claim 13

A computer-implemented method for resolving ambiguities in computer data, comprising:
receiving a new entity creation request, the new entity creation request including entity creation data and a login key, wherein the login key includes a primary identifier and a password;
determining based on the entity data that the new entity creation request is associated with a pre-existing single entity record in an entity database, wherein the login key of the new entity creation request is different than a pre-existing login key linked with the pre-existing single entity record; and
upon determining the new entity creation request is associated with the pre-existing single entity record, updating the pre-existing single entity record with the entity creation data, and creating a new data object in the entity database including data created with the login key.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein the new entity creation data is extracted from an entity creation interface and transmitted from a computing device via the new entity creation request, the entity creation interface having one or more data entry methods configured to receive the entity creation data and the login key.

### Claim 15 (depends on 13)

The computer-implemented method of claim 13, wherein the new data object is stored according to the login key and the pre-existing single entity record.

### Claim 16 (depends on 13)

The computer-implemented method of claim 13, wherein the entity database includes an entity table or index, an authentication table or index and a data cache object.

### Claim 17 (depends on 16)

The computer-implemented method of claim 16, wherein the pre-existing single entity record is stored in the entity table or index.

### Claim 18 (depends on 16)

The computer-implemented method of claim 16, wherein the login key and the pre-existing login key are stored in the authentication table or index and linked to the pre-existing single entity record.

### Claim 19 (depends on 16)

The computer-implemented method of claim 16, wherein the data cache object stores session data associated with the pre-existing single entity record by segregating the session data according to the login key and the pre-existing login key.

### Claim 20 (depends on 19)

The computer-implemented method of claim 19, including transmitting to the computing device the session data created associated with the login key.
