# US 2016/0253367 A1 · Client computer for querying a database stored on a server via a network

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

- Number: US 2016/0253367 A1
- Document ID: US20160253367A1
- Status: Published application
- Kind: A1
- Application number: 14/955,212
- Filed: 2015-12-01
- Published: 2016-09-01
- Earliest claimed: 2013-09-27
- Assignees: Compugroup Medical AG
- Applicants: Compugroup Medical AG
- Inventors: Adrian Spalka; Jan Lehnhardt
- Web page: https://patentgrep.com/patent/US20160253367A1

## CPC

- G06F 16/235: {Update request formulation}
- G06F 16/23: Updating
- G06F 16/242: Query formulation
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/278: {Data partitioning, e.g. horizontal or vertical partitioning}
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/9538: Presentation of query results
- G06F 21/34: involving the use of external additional devices, e.g. dongles or smart cards
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- 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}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/3247: {involving digital signatures}
- H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/0471: {applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- F04C 2270/0421: Controlled or regulated
- G06F 2221/2107: File encryption
- G06F 2221/2115: Third party
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- F04C: ROTARY-PISTON, OR OSCILLATING-PISTON, POSITIVE-DISPLACEMENT MACHINES FOR LIQUIDS (engines F03C); ROTARY-PISTON, OR OSCILLATING-PISTON, POSITIVE-DISPLACEMENT PUMPS

## Abstract

The invention relates to a client computer for querying a database stored on a server via a network, the server being coupled to the client computer via the network, wherein the database comprises first data items and suffix items, wherein each suffix item describes a suffix of at least one first data item of the first data items, wherein for each suffix item a first referential connection exists in the database assigning said suffix item to the at least one first data item comprising the suffix of said suffix item, wherein each suffix item is encrypted with a suffix cryptographic key in the database, wherein each first data item is encrypted with a first cryptographic key in the database, wherein the client computer has installed thereon an application program, the application program being operational to: receiving a search request, the search request specifying an infix search expression, said expression comprising a first wildcard term on the left side of a search criterion and a second wildcard term on the right side of the search criterion, transforming the infix search expression into a prefix search expression by disregarding in the search request the first wildcard term and maintaining the search criterion and the second wildcard term, determine a search interval by transforming the prefix search into a corresponding search interval, performing a prefix search by determining all the encrypted suffix items lying within the search interval, providing to the database a request for providing the one or more encrypted first data items being assigned via the first referential connection to the determined encrypted suffix items, receiving from the database the requested encrypted first data items and decrypting said received first data items.

## Claims

### Claim 1

(canceled)

### Claim 2

(canceled)

### Claim 3

(canceled)

### Claim 4

(canceled)

### Claim 5

(canceled)

### Claim 6

(canceled)

### Claim 7

(canceled)

### Claim 8

(canceled)

### Claim 9

(canceled)

### Claim 10

(canceled)

### Claim 11

(canceled)

### Claim 12

(canceled)

### Claim 13

(canceled)

### Claim 14

(canceled)

### Claim 15

(canceled)

### Claim 16

A client computer for updating a database stored on a server, the server being coupled to the client computer via the network, wherein the database comprises first data items and suffix items, wherein each suffix item describes a suffix of at least one first data item of the first data items, wherein for each suffix item a first referential connection exists in the database assigning said suffix item to the at least one first data item comprising the suffix of said suffix item, wherein each suffix item is encrypted with a suffix cryptographic key in the database, wherein each first data item is encrypted with a first cryptographic key in the database, wherein the client computer has installed thereon an application program, the application program being operational to perform the steps of
a) receiving an update first data item, the update first data item comprising a set of successional symbols,
b) creating an update suffix item by removing a number of the successional symbols from the left side of the update first data item, the update suffix item being the residual part of the update first data item without the removed symbols,
c) encrypting the update suffix item with the suffix cryptographic key for obtaining an encrypted update suffix item and encrypting the update first data item with a first cryptographic key for obtaining an encrypted update first data item,
d) providing a storage request to the database, the storage request comprising instructions to store in the database the encrypted update suffix item, the encrypted update first data item and a first referential connection assigning said encrypted update suffix item to the encrypted update first data item,
e) repeating steps b)-d) with different numbers of the successional removed symbols, the numbers being in between a minimum and a maximum, wherein the maximum is given by the total number of symbols of the update first data item minus a predefined minimal word length.

### Claim 17 (depends on 16)

The client computer of claim 16, wherein the suffix items form a partially ordered set in a first relation of the database, the partial order being formed with respect to the suffix items in non-encrypted form, the application program being operational to perform the steps of
i. sequentially requesting and decrypting encrypted suffix items, wherein each request of the sequential requesting is performed by comparing the position of the update suffix item in the partial order with the position of the decrypted suffix items in the partial order, wherein the sequential requesting is performed until a position in the partial order for storing the update suffix item in the first relation is determined,
ii. in case a position for storing the update suffix item in the first relation is determined, providing the storage request to the database, the storage request comprising the encrypted update suffix item and the position determined in step i).

### Claim 18 (depends on 17)

The client computer of claim 17, wherein step i) comprises:
a) requesting a current encrypted suffix item from the database,
b) in response to said requesting of the current encrypted suffix item, receiving from the database the current encrypted suffix item,
c) decrypting the current encrypted suffix item for obtaining a current decrypted suffix item,
d) in case the update suffix item is located at a position in the partial order preceding the current decrypted suffix item, providing a request for determining the availability of a new encrypted suffix item in the first relation immediately preceding the current encrypted suffix item,
e) in case the update suffix item is located at a position in the partial order succeeding the current decrypted suffix item, providing a request for determining the availability of a new encrypted suffix item in the first relation immediately succeeding the current encrypted suffix item,
f) in case the new encrypted suffix item is available in the first relation, requesting the new encrypted suffix item and in response to said requesting receiving the new encrypted suffix item, and repeating steps c)-f) with the current encrypted suffix item in step c) being the new encrypted suffix item,
g) in case the new encrypted suffix item is unavailable in the first relation, encrypting the update suffix item with the first cryptographic key for obtaining an encrypted update suffix item and providing the storage request of step ii) to the server, the storage request comprising the encrypted update suffix item and a position information, the position information instructing the server to store the encrypted update suffix item in the first relation at a position in the partial order immediately preceding or succeeding the position of the current encrypted suffix item, depending if the update suffix item is preceding or succeeding the current decrypted suffix item with respect to the partial order.

### Claim 19 (depends on 17)

The client computer of claim 17, wherein step i) comprises:
a) requesting a current encrypted suffix item from the database,
b) in response to said requesting of the current encrypted suffix item, receiving from the database the current encrypted suffix item,
c) decrypting the current encrypted suffix item for obtaining a current decrypted suffix item,
d) providing a request for a new encrypted suffix item, wherein the request for the new encrypted suffix item comprises information that the new encrypted suffix item is to be retrieved from a position in the partial order immediately preceding or succeeding the position of the current encrypted suffix item, depending if the update suffix item is preceding or succeeding the current decrypted suffix item with respect to the partial order, and in response to said provision of the request for the new encrypted suffix item, receiving and decrypting the new encrypted suffix item,
e) in case the update suffix item is not located at a position in the partial order between the position of the new decrypted suffix item and the current decrypted suffix item, repeating steps c)-d) with the new encrypted suffix item being the current encrypted suffix item in step c), until the update suffix item is located at a position in the partial order between the position of the new decrypted suffix item and the current decrypted suffix item,
f) encrypting the update suffix item with the first cryptographic key for obtaining an encrypted update first data item,
wherein step ii) comprises
g) providing the storage request to the database, the storage request comprising the encrypted update suffix item and a position information, the position information instructing the database to store the encrypted update suffix item in the first relation at a position in the partial order between the new decrypted suffix item and the current decrypted suffix item.

### Claim 20

A method for updating a databases stored on a server, the server being coupled to the client computer via the network, wherein the database comprises first data items and suffix items, wherein each suffix item describes a suffix of at least one first data item of the first data items, wherein for each suffix item a first referential connection exists in the database assigning said suffix item to the at least one first data item comprising the suffix of said suffix item, wherein each suffix item is encrypted with a suffix cryptographic key in the database, wherein each first data item is encrypted with a first cryptographic key in the database, wherein the method comprises at the client computer:
a) receiving an update first data item, the update first data item comprising a set of successional symbols,
b) creating an update suffix item by removing a number of the successional symbols from the left side of the update first data item, the update suffix item being the residual part of the update first data item without the removed symbols,
c) encrypting the update suffix item with the suffix cryptographic key for obtaining an encrypted update suffix item and encrypting the update first data item with a first cryptographic key for obtaining an encrypted update first data item,
d) providing a storage request to the database, the storage request comprising instructions to store in the database the encrypted update suffix item, the encrypted update first data item and a first referential connection assigning said encrypted update suffix item to the encrypted update first data item,
e) repeating steps b)-d) with different numbers of the successional removed symbols, the numbers being in between a minimum and a maximum, wherein the maximum is given by the word length of the update first data item minus a predefined minimal word length.

### Claim 21

(canceled)
