# US 2017/0373835 A1 · Key management system and method

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

- Number: US 2017/0373835 A1
- Document ID: US20170373835A1
- Status: Published application
- Kind: A1
- Application number: 15/192,755
- Filed: 2016-06-24
- Published: 2017-12-28
- Earliest claimed: 2016-06-24
- Assignees: NTT Research, Inc.
- Applicants: NTT Innovation Institute 1 LLC
- Inventors: Go Yamamoto
- Web page: https://patentgrep.com/patent/US20170373835A1

## CPC

- H04L 9/0618: {Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation}
- H04L 9/0841: {involving Diffie-Hellman or related key agreement protocols}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/302: {involving the integer factorization problem, e.g. RSA or quadratic sieve [QS] schemes}
- H04L 2209/24: Key scheduling, i.e. generating round keys or sub-keys for block encryption
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for private key management in a public key encryption system are disclosed. In one embodiment, the system and method may utilize a “fake” private key to provide the private key management.

## Claims

### Claim 1

A key management method for public key encryption, comprising:
storing, remotely from an entity, a plurality of set of keys for entities in the system that have decryption capabilities, the set of keys for each entity having a private key of the entity and a fake private key corresponding to the private key of the entity;
receiving, from the entity, a piece of ciphertext content and a fake private key; and
obtaining, when the piece of ciphertext content is being decrypted for a particular entity, the private key of the entity based on the key private key.

### Claim 2 (depends on 1)

The method of claim 1 further comprising generating, by the cryptographic component, a new private key for the particular entity and a fake private key that corresponds to the new private key for the particular entity and sending, by the cryptographic component, the fake private key to the particular entity.

### Claim 3 (depends on 2)

The method of claim 2 further comprising decrypting the piece of ciphertext content using the private key of the entity.

### Claim 4 (depends on 1)

The method of claim 1, wherein obtaining the private key for the particular entity further comprises extracting a uniform resource locator of the cryptographic component from key information and retrieving the new private key of the particular entity based on the uniform resource locator of the cryptographic component and the private fake key.

### Claim 5 (depends on 1)

The method of claim 1, wherein each entity is a computing device with application that has decryption capabilities.

### Claim 6 (depends on 1)

The method of claim 1, wherein each entity is one of an application having a decryption capability, a device having a decryption capability and a user that uses an application with a decryption capability.

### Claim 7 (depends on 1)

The method of claim 1, wherein the fake private key for the particular entity further comprises a pointer to new private key for the particular entity.

### Claim 8

A key management system, comprising:
one or more entities, each entity having a public key decryption capability using a private key of the entity and a key store;
a cryptographic component, connected to the entities by a computer network, having a metadata encoder that generates a new private key for a particular entity and generates a fake private key that corresponds to the new private key; and
wherein the cryptographic component sends the fake private key to the particular entity.

### Claim 9 (depends on 8)

The system of claim 8, wherein the cryptographic component performs a decryption process based on a request from the particular client wherein the request includes a piece of ciphertext and the fake private key and the cryptographic component obtains the new private key of the particular entity based on the fake private key to permit the decryption of the ciphertext using the new private key of the particular entity.

### Claim 10 (depends on 9)

The system of claim 9, wherein each entity has a decryption module that performs the decryption of the ciphertext using the new private key of the particular entity.

### Claim 11 (depends on 10)

The system of claim 10, wherein the decryption module further comprises a parser module that receives key information and a meta-information extractor module obtains the new private key for the particular entity based on the fake private key.

### Claim 12 (depends on 11)

The system of claim 11, wherein the meta-information extractor module extracts a uniform resource locator of the cryptographic component from the key information and retrieves the new private key of the particular entity based on the uniform resource locator of the cryptographic component.

### Claim 13 (depends on 8)

The system of claim 8, wherein each entity is a computing device with application that has decryption capabilities.

### Claim 14 (depends on 8)

The system of claim 8, wherein each entity is one of an application having a decryption capability, a device having a decryption capability and a user that uses an application with a decryption capability.

### Claim 15 (depends on 8)

The system of claim 8, wherein the fake private key for the particular entity further comprises a pointer to new private key for the particular entity.

### Claim 16

A public key encryption system, comprising:
one or more entities, each entity having a public key decryption capability using a private key of the entity and a key store;
a cryptographic component, connected to the entities by a computer network, having a metadata encoder that generates a new private key for a particular entity and generates a fake private key that corresponds to the new private key; and
wherein the cryptographic component sends the fake private key to the particular entity.

### Claim 17 (depends on 16)

The system of claim 16, wherein the cryptographic component performs a decryption process based on a request from the particular client wherein the request includes a piece of ciphertext and the fake private key and the cryptographic component obtains the new private key of the particular entity based on the fake private key to permit the decryption of the ciphertext using the new private key of the particular entity.

### Claim 18 (depends on 17)

The system of claim 17, wherein each entity has a decryption module that performs the decryption of the ciphertext using the new private key of the particular entity.

### Claim 19 (depends on 18)

The system of claim 18, wherein the decryption module further comprises a parser module that receives key information and a meta-information extractor module obtains the new private key for the particular entity based on the fake private key.

### Claim 20 (depends on 19)

The system of claim 19, wherein the meta-information extractor module extracts a uniform resource locator of the cryptographic component from the key information and retrieves the new private key of the particular entity based on the uniform resource locator of the cryptographic component.

### Claim 21 (depends on 16)

The system of claim 16, wherein each entity is a computing device with application that has decryption capabilities.

### Claim 22 (depends on 16)

The system of claim 16, wherein each entity is one of an application having a decryption capability, a device having a decryption capability and a user that uses an application with a decryption capability.

### Claim 23 (depends on 16)

The system of claim 16, wherein the fake private key for the particular entity further comprises a pointer to new private key for the particular entity.

### Claim 24

A key management method, comprising:
generating a private key for an entity;
storing the generated private key in a key management component having a key storage remote from the entity;
generating, at a key management component, a fake private key that acts as a pointer to the generated private key; and
sending the fake private key to the entity to store in a key storage, wherein the entity decrypts a piece of ciphertext by making a request using the fake private key.

### Claim 25 (depends on 24)

The method of claim 24 further comprising generating a public key for the entity wherein the entity is a new entity.

### Claim 26 (depends on 24)

The method of claim 24, wherein generating the private key for an entity further comprises generating a new private key for an existing entity.

### Claim 27 (depends on 24)

The method of claim 24, wherein the entity is a computing device having a decryption capability.

### Claim 28 (depends on 24)

The method of claim 24, wherein the entity is one of an application having a decryption capability, a device having a decryption capability and a user that uses an application with a decryption capability.

### Claim 29 (depends on 24)

The method of claim 24, wherein the fake private key for the particular entity further comprises a pointer to new private key for the particular entity.
