# US 2024/0275600 A1 · Secure element, method for registering tokens, and token reference register

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

- Number: US 2024/0275600 A1
- Document ID: US20240275600A1
- Status: Published application
- Kind: A1
- Application number: 18/681,044
- Filed: 2022-07-12
- Published: 2024-08-15
- Earliest claimed: 2021-08-04
- Assignees: Giesecke+Devrient Advance52 GmbH
- Applicants: Giesecke+Devrient Advance52 GmbH
- Inventors: Raoul-Thomas HERBORG; Daniel ALBERT
- Web page: https://patentgrep.com/patent/US20240275600A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06Q 20/0655: {e-cash managed centrally}
- G06Q 20/105: {involving programming of a portable memory device, e.g. IC cards, "electronic purses"}
- G06Q 20/3678: {e-cash details, e.g. blinded, divisible or detecting double spending}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4033: {Local solvency checks}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A secure element relates to a token reference register and to a method for registering tokens of an electronic transaction system. Each token of the transaction system comprises at least a token value and a private part of a token-individual key pair as token elements.

## Claims

### Claim at position 1

-18. (canceled)

### Claim 19

A method for registering tokens of an electronic transaction system, wherein each token of the transaction system comprises at least a token value and a private part of a token-individual key pair as token elements, the method comprising the method steps of:
receiving, in a token reference register of the transaction system, a registration request comprising at least one token reference uniquely assigned to a token of the transaction system,
wherein the token reference comprises at least the token value of the token and a public part of the token-individual key pair as token reference elements,
wherein the public part of the token-individual key pair was obtained by applying a cryptographic one-way function to the private part of the token-individual key pair of the token,
verifying, using a verification unit of the token reference register, whether the at least one token reference of the received registration request is stored in the token reference register, and
storing the at least one token reference in a memory unit of the token reference register in order to register the token uniquely assigned to this token reference in the transaction system if it is established in the verification step that the at least one token reference of the received registration request is not stored in the token reference register.

### Claim 20 (depends on 19)

The method according to claim 19, wherein in the verification step by the verification unit of the token reference register, the following is also established:
whether the token reference can be assigned to a token in the received registration request; and/or
whether the received registration request is syntactically correct; and/or
whether a sum of token values of all token references within the registration request is zero.

### Claim 21 (depends on 19)

The method according to claim 19, wherein the public key part of the token-individual key pair of the token reference simultaneously is a database index in the token reference register.

### Claim 22 (depends on 19)

The method according to claim 19, wherein the received registration request is signed with the private part of the token-individual key pair in order to be able to verify an assignment of the token reference to the token.

### Claim 23 (depends on 19)

The method according to claim 19, wherein the registration request is received by a subscriber unit, in particular a secure element; and/or the registration request relates to a modification of at least one previously registered token, and at least the token reference of the at least one previously registered token and the at least one token reference of the token to be registered, which is the modification of the previously registered token.

### Claim 24 (depends on 19)

The method according to claim 19, wherein the token reference register also comprises:
the one or more memory units for storing token references for registering the token in the transaction system; and/or
the one or more verification units for verifying received registration requests; and/or
one or more check units for checking the received registration request, in particular for syntactic correctness and/or sum of the token values in the registration request, before the verification; and/or
a check unit for checking a total token value of all token values of registered tokens of the transaction system; and/or
a new registration unit for registering new tokens or deleted tokens as implemented by a token issuer.

### Claim 25 (depends on 19)

The method according to claim 19, wherein the token reference comprises at least one of the further token reference elements:
a count value,
an identity of a subscriber unit or of an owner of the subscriber unit, and/or
a pseudonym of a subscriber entity or of an owner of the subscriber unit.

### Claim 26 (depends on 23)

The method according to claim 23, wherein the registration request is a splitting of a token, and the registration request comprises a token reference of the token to be split and a token reference of the split token to be registered.

### Claim 27 (depends on 26)

The method according to claim 26, wherein for splitting the token the following method steps are carried out in a subscriber unit:
creating a new private part of a token-individual key pair for a first split token,
applying a cryptographic function to the new private part in order to obtain a corresponding public part of the token-individual key pair for the first split token;
creating a new private part of a token-individual key pair for a second split token;
applying a cryptographic function to the new private part to obtain a corresponding public part of the token-individual key pair for the second split token;
splitting the token value into a first token part value and into a second token part value,
wherein the sum of the first token part value and the second token part value corresponds to the token value of the token to be split;
creating a token reference for the first split token comprising the first token part value and the public part of the token-individual key pair of the first split token;
creating a token reference for the second split token comprising the second token part value and the public part of the token-individual key pair of the second split token; and
creating the registration request using the token reference of the token to be split, the token reference for the first split token and the token reference for the second split token.

### Claim 28 (depends on 23)

The method according to claim 23, wherein the registration request relates to a switching of a token to be switched to a switched token, and the registration request comprises a token reference of the token to be switched and the token reference of the switched token.

### Claim 29 (depends on 28)

The method according to claim 28, wherein for switching the token the following method steps are carried out in a subscriber unit:
creating a new private part of a token-individual key pair,
applying a cryptographic function to the new private part in order to obtain a public part of the token-individual key pair for the switched token;
creating the registration request using the token reference for the token to be switched and the public part of the token-individual key pair for the switched token.

### Claim 30 (depends on 23)

The method according to claim 23, wherein the registration request is a connection of at least two tokens and comprises a token reference of the connected token and a token reference of each of the tokens to be connected.

### Claim 31 (depends on 30)

The method according to claim 30, wherein for connecting the token the following method steps are carried out in a subscriber unit:
creating a new private part of a token-individual key pair,
applying a cryptographic function to the new private part to obtain a corresponding public part of the token-individual key pair for the connected token;
calculating the token value for the connected token by forming the sum of the respective token values of the tokens to be connected;
creating a token reference for the connected token comprising the calculated token value and the public part of the token-individual key pair for the connected token; and
creating the registration request using each token reference of the tokens to be connected and the token reference for the connected token.

### Claim 32 (depends on 19)

The method according to claim 19, wherein the registration request has been sent by a token issuer, and
wherein the registration request relates to a creation of a token or a deletion of a token.

### Claim 33 (depends on 19)

A token reference register for a transaction system, configured to perform the method steps according to claim 19.

### Claim 34 (depends on 33)

The token reference register according to claim 33, comprising:
at least one memory unit for storing token references for registering tokens in the transaction system;
at least one verification unit for verifying whether a token reference of a received registration request is stored in the token reference register,
a new registration unit for registering a token newly generated by a token issuer or a token deleted by a token issuer,
optionally a check unit for checking the received registration request before the verification by the verification unit, and
optionally a check unit for checking a total sum of the token values of registered token of the transaction system stored in the memory unit.

### Claim 35

A secure element which is configured as a subscriber unit of a transaction system,
for the direct exchange of tokens with a further subscriber unit, wherein each token of the transaction system comprises at least one token value and a private part of a token-individual key pair as token elements,
for creating a modified token from an existing token to be modified,
wherein a token reference uniquely assigned to the modified token of the transaction system comprises at least the token value of the token and a public part of the token-individual key pair as token reference elements,
wherein the public part of the token-individual key pair is obtained by applying a cryptographic one-way function to the private part of the token-individual key pair of the token, and
for providing a registration request to a token reference register of the transaction system,
wherein the registration request has at least the token reference uniquely assigned to the token of the transaction system.

### Claim 36 (depends on 33)

A transaction system comprising:
a register layer with a token reference register according to claim 33 for registering token references; and
a direct transaction layer with a plurality of subscriber units which are designed at least partially as a secure element which is configured as a subscriber unit of a transaction system,
for the direct exchange of tokens with a further subscriber unit, wherein each token of the transaction system comprises at least one token value and a private part of a token-individual key pair as token elements,
for creating a modified token from an existing token to be modified,
wherein a token reference uniquely assigned to the modified token of the transaction system comprises at least the token value of the token and a public part of the token-individual key pair as token reference elements,
wherein the public part of the token-individual key pair is obtained by applying a cryptographic one-way function to the private part of the token-individual key pair of the token, and
for providing a registration request to a token reference register of the transaction system,
wherein the registration request has at least the token reference uniquely assigned to the token of the transaction system.
