# US 2015/0106632 A1 · Method for storing data in a relational database and relational database server

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

- Number: US 2015/0106632 A1
- Document ID: US20150106632A1
- Status: Published application
- Kind: A1
- Application number: 14/402,176
- Filed: 2012-12-06
- Published: 2015-04-16
- Earliest claimed: 2012-05-24
- Assignees: NEC Europe Ltd.
- Applicants: NEC Europe Ltd.
- Inventors: Ghassan Karame; Jens-Matthias Bohli; Sebstian Gajek
- Web page: https://patentgrep.com/patent/US20150106632A1

## CPC

- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- G06F 16/284: {Relational databases}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The invention relates to a method for storing data in a relational database, comprising a plurality of tables, wherein the data is stored in these tables, wherein each row of each table is provided with an original primary key for identification, and wherein foreign keys are provided for cross-referencing different tables of the relational database, wherein the primary keys are encrypted, wherein the foreign keys are encrypted based on the encrypted primary keys and wherein for each table where a primary key is referenced as a foreign key an encrypted pointer is stored to link the corresponding encrypted foreign key to the encrypted primary key. The present invention further relates to a relational database server.

## Claims

### Claim 1

A method for storing data in a relational database, comprising
a plurality of tables (T1, T2), wherein the data is stored in these tables, wherein each row of each table (T1, T2) is provided with an original primary key (PK) for identification, and wherein foreign keys (FK) are provided for cross-referencing different tables (T1, T2) of the relational database,
characterized in that
the primary keys (PK) are encrypted, that
the foreign keys (FK) are encrypted based on the encrypted primary keys (PK) and that
for each table where a primary key (PK) is referenced as a foreign key (FK) an encrypted pointer (P) is stored to link the corresponding encrypted foreign key (FK) to the encrypted primary key (PK).

### Claim 2 (depends on 1)

The method according to claim 1, characterized in that the primary keys (PK) and/or the foreign keys (FK) are encrypted by symmetric encryption, preferably AES.

### Claim 3 (depends on 1)

The method according to claim 1, characterized in that multiple occurrences of foreign keys (FK) in the same table (T1, T2) are linked consecutively based on at least a prior occurrence.

### Claim 4 (depends on 3)

The method according to claim 3, characterized in that for the first occurrence of a foreign key (FK) in a table (T1, T2) this foreign key (FK) is generated by encrypting the corresponding encrypted primary key (PK) and a value for table identification.

### Claim 5 (depends on 1)

The method according to claim 1, characterized in that pointers (P) are encrypted with a encryption key (K2) different from the encryption key (K1) for encrypting the primary keys (PK) and/or foreign keys (FK).

### Claim 6 (depends on 1)

The method according to claim 1, characterized in that a control table is generated, preferably encrypted.

### Claim 7 (depends on 1)

The method according to claim 1, characterized in that at least one of the encryption keys (K1, K2) for encrypting the primary keys (PK) and/or the pointers (P) is stored outside the relational database.

### Claim 8 (depends on 1)

The method according to claim 1, characterized in that the encrypted foreign keys (FK) are stored in form of a linked list starting from the from the foreign key (FK) that links to the primary key (PK).

### Claim 9 (depends on 1)

The method according to claim 1, characterized in that the primary keys (PK) are provided in form of extra identifiers, preferably generated by the relational database itself.

### Claim 10 (depends on 1)

A relational database server for storing data, preferably for performing with a method according to claim 1, is configured to provide a plurality of tables (T1, T2), to store the data in these tables (T1, T2), to provide each row of each table (T1, T2) with an original primary key (PK) for identification, and to provide foreign keys (FK) for cross-referencing different tables (T1, T2),
characterized in that
the relational database server is configured to encrypt the primary keys (PK), to encrypt the foreign keys (FK) based on the encrypted primary keys (PK) and to store an encrypted pointer (P) to link the corresponding encrypted foreign key (FK) to the encrypted primary key (PK) for each table (T1, T2) where a primary key (PK) is referenced as a foreign key (FK).

### Claim 11 (depends on 10)

The relational database server according to claim 10, characterized in that the relational database server is connected to a encryption server, wherein the encryption server is configured to provide encryption keys (K1, K2) for encrypting the primary keys (PK) and/or the pointers (P).
