# US 2012/0254609 A1 · Method for transferring encrypted messages

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

- Number: US 2012/0254609 A1
- Document ID: US20120254609A1
- Status: Published application
- Kind: A1
- Application number: 13/483,502
- Filed: 2012-05-30
- Published: 2012-10-04
- Earliest claimed: 2006-12-04
- Inventors: Gernot HOFSTÄDTER; Richard Adolf Dittrich
- Web page: https://patentgrep.com/patent/US20120254609A1

## CPC

- H04L 63/0464: {using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for transferring encoded messages between at least two users, particularly cryptographic protocol, includes message transaction taking place by inserting an authentication device which decodes the messages received from the users and sends especially encoded messages to the users. The method includes the following steps: a1) the user (A) sends a message (NAj) to the authentication device (AE); a2) the authentication device (AE) creates a transaction identification record (TID); a3) the authentication device (AE) sends a message (NAEj) containing the transaction identification record (TID) to the user (A); a4) the user (A) creates a message (NAz) that is encoded by a key (SAz) and contains the transaction identification record (TID); h) the message (NAz) is sent to a second user (B); i) the second user (B) creates a message (NBj) that includes the encoded message (NAz) and is encoded by another key (SB); j) the message (NBj) is sent to the authentication device (AE).

## Claims

### Claim 1

A method of transferring encrypted messages between at least two users, in particular a cryptographic protocol, wherein the transaction of the messages takes place with the interposition of an authentication device which decrypts the messages received from the users and in turn sends in particular encrypted messages to the users, and includes the following steps:
a1) sending of a message (NA1) by the user (A) to the authentication device (AE),
a2) production of a transaction identification data set (TID) by the authentication device (AE),
a3) sending of a message (NAE1) containing the transaction identification data set (TID) by the authentication device (AE) to the user (A),
a4) production of a message (NA2) encrypted with a key (SA2) and containing the transaction identification data set (TID) by the user (A);
b) sending of the message (NA2) to a second user (B),
c) production of a message (NB1) containing the encrypted message (NA2) and encrypted with a further key (SB) by the second user (B),
d) sending of the message (NB1) to the authentication device (AE),
e) decryption of the message (NB1), (NA2) using the corresponding keys (SB1), (SA2) by the authentication device (AE),
f) production of a message (NAE2) by the authentication device (AE) with reference to the clear texts (A2), (B1) contained in the decrypted messages (NA2), (NB1), and
g) sending of the message (NAE2) to the first user (A) or the second user (B).

### Claim 2 (depends on 1)

A method as set forth in claim 1 wherein the encrypted message (NA2) produced by the first user (A) includes a transaction identification data set (TID), preferably a transaction identification number.

### Claim 3 (depends on 2)

A method as set forth in claim 2 wherein the message (NAE1) transferred by the authentication device (AE) to the user (A) besides the transaction identification data set (TID) includes items of transaction information (Tinf) which are encrypted with a key (SAE) and which are preferably dynamic.

### Claim 4 (depends on 2)

A method as set forth in claim 2 wherein the message (NA1) from the first user (A) to the authentication device (AE) and/or the message (NAE1) from the authentication device (AE) to the user (A) is/are at least partially encrypted prior to the transfer.

### Claim 5 (depends on 2)

A method as set forth in claim 2 wherein the authentication device (AE) has an authentication server (AS) and a data server (DS), wherein the authentication server (AS) produces a database entry (DB) which is or can be associated with the message (NA1) sent by the first user (A) to the authentication device (AE) on the database server.

### Claim 6 (depends on 5)

A method as set forth in claim 5 wherein the transaction identification data set (TID) is or can be uniquely associated with the database entry (DB).

### Claim 7 (depends on 1)

A method as set forth in claim 1 characterised by the steps:
e1) decryption of the messages (NB1), (NA2) using the corresponding keys (SB1), (SA2) by the authentication device (AE),
e2) comparison, co-ordination or combination of the clear texts (A2), B1) contained in the decrypted messages (NA2), (NB1), and
f) production of a message (NAE2) referring to the result of comparison, co-ordination or combination of the clear texts (A2), (B1) by the authentication device (AE).

### Claim 8 (depends on 1)

A method as set forth in claim 1 characterised by the steps:
e1) decryption of the messages (NB1), (NA2) using the corresponding keys (SB1), (SA2) by the authentication device (AE),
e2) comparison, co-ordination or combination of the clear texts (A2), B1) contained in the decrypted messages (NA2), (NB1),
e3) setting of an action (E) referring to the result of the comparison, co-ordination or combination, and
f) production of a message (NAE2) referring to the set action (E), by the authentication device (AE).

### Claim 9 (depends on 1)

A method as set forth in claim 1 characterised by the steps:
f) production of a message (NAE2) intended for the first user (A) and a message (NAE2′) intended for the second user (B) by the authentication device (AE) with reference to clear texts (A2), (B1) contained in the received and decrypted messages (NA2), (NB1), and
g) sending of the message (NAE2) to the first user (A) and the message (NAE2′) to the second user (B).

### Claim 10 (depends on 1)

A method as set forth in claim 1 wherein the message or messages (NAE2), (NAE2′) are encrypted prior to sending by the authentication device (AE) with the keys (SB2), (SA3) associated with the respective users (A, B).

### Claim 11 (depends on 1)

A method as set forth in claim 1 wherein the transfer of the messages (NA1, NA2, NB1, NAE1, NAE2, NAE2′) is effected by way of a network, preferably by way of the Internet.

### Claim 12 (depends on 1)

A method as set forth in claim 1 wherein at least one of the encrypted messages (NA2), (NB1), (NA2) contains a clear text (A), (B) and a transaction identification data set (TID).

### Claim 13 (depends on 12)

A method as set forth in claim 12 wherein at least one of the encrypted messages (NA2), (NB1), (NA2) further contains encrypted, preferably dynamic items of transaction information (Tinf).

### Claim 14 (depends on 1)

A method as set forth in claim 1 wherein at least one user (A, B) has at least one secret key (SA, SB) with the authentication device (AE).

### Claim 15 (depends on 14)

A method as set forth in claim 14 wherein each user (A, B) respectively has at least one secret key (SA, SB) with the authentication device (AE).

### Claim 16 (depends on 15)

A method as set forth in claim 15 wherein the messages (NA1), (NA2), (NB1), (NAE1), (NAE2), (NAE2′) are transferred in accordance with a symmetric cryptographic protocol.

### Claim 17 (depends on 14)

A method as set forth in claim 14 wherein the key or keys (SA, SB) between the user or users (A, B) and the authentication device (AE) is/are distributed by means of a mobile data carrier (6) on which the key (SA, SB) is stored and/or which is adapted to generate the key (SA, SB), wherein a respective dedicated data carrier is or can be associated with each user (A, B).

### Claim 18 (depends on 17)

A method as set forth in claim 17 wherein the mobile data carrier (6) associated with a user (A) is adapted to generate a plurality of preferably one-time keys (SA1, SA2), wherein the respective user (A) has all keys (SA1), (SA2) generated by the data carrier (6) associated with him jointly with the authentication device (AE).

### Claim 19 (depends on 1)

A hardware encryption device, in particular for use in a method as set forth in claim 1, wherein the encryption device is formed by a mobile data carrier (6) which has a memory unit (7), a computing unit (8) for generating at least one preferably one-time key (SA, SB) and an interface (9), preferably a USB interface.

### Claim 20 (depends on 19)

An encryption device as set forth in claim 19 wherein it has a biometric access control device (10).

### Claim 21 (depends on 20)

An encryption device as set forth in claim 20 wherein the biometric access control device (10) has a sensor for recognising a fingerprint.

### Claim 22 (depends on 1)

Use of a USB stick as an encryption device in cryptography, in particular in a method as set forth in claim 1.

### Claim 23 (depends on 22)

A USB stick as set forth in claim 22 wherein the USB stick has a fingerprint recognition function.
