# US 2002/0059286 A1 · Trusted computing platform with dual key trees to support multiple public/private key systems

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

- Number: US 2002/0059286 A1
- Document ID: US20020059286A1
- Status: Published application
- Kind: A1
- Application number: 10/016,700
- Filed: 2001-11-02
- Published: 2002-05-16
- Earliest claimed: 2000-11-15
- Assignees: International Business Machines Corporation
- Inventors: David Carroll Challener
- Web page: https://patentgrep.com/patent/US20020059286A1

## CPC

- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 9/0836: {using tree structure or hierarchical structure}
- H04L 9/0897: {involving additional devices, e.g. trusted platform module [TPM], smartcard or USB}
- 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)

## Abstract

The present invention addresses the foregoing need by creating two identically structured storage trees with a single storage root key. As envisioned in the current art (e.g., the TCPA specification), all migratable keys will be stored in a migratable storage tree. These migratable keys will be storage keys except at the extreme end of any branch, where the key (known as a leaf key) will be a user key. However, an additional storage tree will also be created which shadows the migratable storage key. This second storage tree will be comprised entirely of non-migratable storage keys of the quicker loading type except for the leaf keys (which will be identical to the leaf keys in the migratable storage tree (MST). The second storage tree (SST) will have a storage key for every migratable storage key in the MST. The use authorization for the keys in the SST will be identical to the use authorization for the MST.

## Claims

### Claim 1

In a data processing system, a method comprising the steps of
creating a migratable storage tree with a storage root key; and
creating a non-migratable storage tree with the storage root key, wherein the migratable storage tree and the non-migratable storage tree are identically structured.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the migratable storage tree and the non-migratable storage tree are created by a trusted computing module in accordance with Trusted Computing Platform Alliance.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein the migratable storage tree comprises migratable keys and a user key, wherein the non-migratable storage tree comprises non-migratable keys and a user key.

### Claim 4 (depends on 1)

The method as recited in claim 1, wherein the non-migratable storage tree will include non-migratable storage keys corresponding to each migratable storage key in the migratable storage tree.

### Claim 5 (depends on 1)

The method as recited in claim 1, wherein use authorization in the non-migratable storage tree will be identical to use authorization in the migratable storage tree.

### Claim 6 (depends on 1)

The method as recited in claim 1, further comprising the steps of
requesting a migratable storage key; and
requesting a non-migratable storage key.

### Claim 7 (depends on 6)

The method as recited in claim 6, wherein the step of requesting a migratable storage key will identify a parent key in the migratable storage tree, and wherein the step of requesting a non-migratable storage key will identify a parent key in the non-migratable storage tree that corresponds to the parent key in the migratable storage tree.

### Claim 8 (depends on 1)

The method as recited in claim 1, further comprising the step of:
when a key loading request is made for a migratable storage key, loading a key from the non-migratable storage tree instead of loading a corresponding key from the migratable storage tree.

### Claim 9

In a data processing system, a method comprising the steps of:
splitting a request to create a new migratable storage key with given authentication data and a first parent key into first and second commands;
wherein the first command creates a migratable storage key with the given authentication data and the first parent key; and
wherein the second command requests creating a non-migratable storage key with the given authentication data and a second parent key which is determined from looking up a key that corresponds to the first parent key in a database.

### Claim 10 (depends on 9)

The method recited in claim 9, wherein the migratable storage key and the non-migratable storage key are associated in a database.

### Claim 11 (depends on 9)

The method recited in claim 9, wherein the non-migratable key is a multi-prime key.

### Claim 12 (depends on 9)

The method recited in claim 9, where the non-migratable key is an elliptic curve key.

### Claim 13 (depends on 9)

The method as recited in claim 9, further comprising the steps of:
creating a new migratable signing key with the given authentication data and a third parent key;
storing the new migratable signing key with the given authentication data and the third parent key;
storing the new migratable signing key with the given authentication data and a fourth parent key where the fourth parent key is a non-migratable key associated with the third parent key in a database.

### Claim 14 (depends on 13)

The method as recited in claim 13, further comprising the steps of:
requesting a signature by the new migratable signing key;
searching the database for the location of a key blob containing the new migratable signing key;
loading a copy of the new migratable signing key stored in the key blob created with the non-migratable parent key; and
signing with the new migratable signing key.

### Claim 15 (depends on 9)

The method as recited in claim 9, further comprising the steps of:
creating a new data stored by means of the first parent key;
storing the new data with the first parent key;
storing the new data with the second parent key where the second parent key is a non-migratable key associated with the third parent key in a database.

### Claim 16 (depends on 15)

The method as recited in claim 15, further comprising the steps of:
requesting data stored by the new migratable storage key;
searching the database for the location of a key blob associated with the new migratable storage key;
loading a copy of the key blob created with the non-migratable storage key; and
decrypting the data.

### Claim 17 (depends on 14)

The method as recited in claim 14, further comprising the steps of:
requesting migration of new migratable signing keys;
searching the database for the location of a key blob associated with a non-migratable parent of the key to be migrated;
processing the migration.

### Claim 18

In a data processing system, a method comprising the steps of:
creating a migratable storage tree with a storage root key; and
creating a non-migratable storage tree with the storage rootkey where the migratable storage tree and the non-migratable storage tree are identically structured with corresponding keys and authentication data.

### Claim 19 (depends on 18)

The method as recited in claim 18, wherein the migratable storage tree and the non-migratable storage tree are created by a trusted computing module in accordance with Trusted Computing Platform Alliance.

### Claim 20 (depends on 19)

The method as recited in claim 19, wherein the migratable storage tree comprises migratable keys and a user key, wherein the non-migratable storage tree comprises non-migratable keys and a user key.

### Claim 21 (depends on 18)

The method recited in claim 18, wherein the migratable storage tree comprises migratable keys and encrypted user data wherein the non-migratable storage tree comprises non-migratable keys and encrypted user data.

### Claim 22 (depends on 18)

The method as recited in claim 18, wherein the non-migratable storage tree will include non-migratable storage keys corresponding to each migratable storage key in the migratable storage tree.

### Claim 23 (depends on 18)

The method as recited in claim 18, wherein the non-migratable storage tree will include non-migratable storage keys corresponding to a subset of the migratable storage keys in the migratable storage tree.

### Claim 24 (depends on 18)

The method as recited in claim 18, wherein use authorization in the non-migratable storage tree will be identical to use authorization in the migratable storage tree.

### Claim 25 (depends on 18)

The method as recited in claim 18, wherein use authorization in the non-migratable storage tree can be deduced from user authorization in the migratable storage tree with additional data.

### Claim 26 (depends on 25)

The method as recited in claim 25, wherein the use authorization in the non-migratable storage tree is obtained by hashing the concatenation of the user authorization in the migratable storage tree with a fixed string.
