# US 2017/0302632 A1 · Computational systems and methods for encrypting data for anonymous storage

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

- Number: US 2017/0302632 A1
- Document ID: US20170302632A1
- Status: Published application
- Kind: A1
- Application number: 15/346,663
- Filed: 2016-11-08
- Published: 2017-10-19
- Earliest claimed: 2011-09-07
- Assignees: Elwha LLC
- Applicants: Elwha LLC
- Inventors: Marc E. Davis; Matthew G. Dyor; William Gates; Xeudong Huang; Roderick A. Hyde; Edward K.Y. Jung; Jordin T. Kare; Royce A. Levien; Richard T. Lord; Robert W. Lord; Qi Lu; Mark A. Malamud; Nathan P. Myhrvold; Satya Nadelia; Danny Allen Reed; Harry Shum; Clarence T. Tegreene; Lowell L. Wood, JR.
- Web page: https://patentgrep.com/patent/US20170302632A1

## CPC

- G06Q 10/10: Office automation; Time management
- G06Q 10/40: Business processes related to social networking or social networking services
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- 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

Methods, apparatuses, computer program products, devices and systems are described that carry out accepting from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption; encrypting the at least one instance of data to produce level-one-encrypted data; associating the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity; and transmitting the level-one-encrypted data and associated encrypted identifier.

## Claims

### Claim 1

A system comprising:
a machine configured to accept from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption;
a machine configured to encrypt the at least one instance of data to produce level-one-encrypted data;
a machine configured to associate the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity; and
a machine configured to transmit the level-one-encrypted data and associated encrypted identifier.

### Claim 2 (depends on 1)

The system of claim 1 wherein the machine configured to accept from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption comprises:
a machine configured to accept from a user identifier encryption entity an encrypted version of at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data.

### Claim 3 (depends on 2)

The system of claim 2 wherein the machine configured to accept from a user identifier encryption entity an encrypted version of at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data comprises:
a machine configured to accept from a user identifier encryption entity at least one hash corresponding to at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data.

### Claim 4 (depends on 1)

The system of claim 1 wherein the machine configured to accept from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption comprises:
a machine configured to accept from a user identifier encryption entity at least one encrypted persona corresponding to a user having at least one instance of data for encryption.

### Claim 5 (depends on 1)

The system of claim 1 wherein the machine configured to encrypt the at least one instance of data to produce level-one-encrypted data comprises:
a machine configured to encrypt the at least one instance of data via public key cryptography.

### Claim 6 (depends on 5)

The system of claim 5 wherein the machine configured to encrypt the at least one instance of data via public key cryptography comprises:
a machine configured to encrypt the at least one instance of data using a certificated public key.

### Claim 7 (depends on 6)

The system of claim 6 wherein the machine configured to encrypt the at least one instance of data using a certificated public key comprises:
a machine configured to encrypt the at least one instance of data using an RSA key.

### Claim 8 (depends on 1)

The system of claim 1 wherein the machine configured to encrypt the at least one instance of data to produce level-one-encrypted data comprises:
a machine configured to encrypt the at least one instance of data using a symmetric key to produce level-one-encrypted data.

### Claim 9 (depends on 1)

The system of claim 1 wherein the machine configured to encrypt the at least one instance of data to produce level-one-encrypted data comprises:
a machine configured to encrypt the at least one instance of data using a public key that is not held by a certificating authority.

### Claim 10 (depends on 1)

The system of claim 1 wherein the machine configured to encrypt the at least one instance of data to produce level-one-encrypted data comprises:
a machine configured to encrypt the at least one instance of data to produce level-one-encrypted data, wherein the machine is further configured to delete the at least one instance of data subsequent to producing the level-one-encrypted data.

### Claim 11 (depends on 1)

The system of claim 1 wherein the machine configured to associate the at least one encrypted identifier with the level-one-encrypted data, and wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity comprises:
a machine configured to associate as metadata the at least one encrypted identifier with the level-one-encrypted data, and wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity.

### Claim 12 (depends on 1)

The system of claim 1 wherein the machine configured to associate the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity comprises:
a machine configured to associate as descriptive metadata the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and further wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity.

### Claim 13 (depends on 12)

The system of claim 12 wherein the machine configured to associate as metadata the encrypted identifier with level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity comprises:
a machine configured to associate as descriptive metadata the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity, and further wherein a decryption key for decrypting the encrypted identifier is inaccessible to the level-one-encryption entity.

### Claim 14 (depends on 1)

The system of claim 1 wherein the machine configured to transmit the level-one-encrypted data and associated encrypted identifier comprises:
a machine configured to transmit the level-one-encrypted data and associated encrypted identifier to a level-two-encryption entity.

### Claim 15

A computer-implemented method comprising:
accepting from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption;
encrypting the at least one instance of data to produce level-one-encrypted data;
associating the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity; and
transmitting the level-one-encrypted data and associated encrypted identifier.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15 wherein accepting from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption comprises:
accepting from a user identifier encryption entity an encrypted version of at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data.

### Claim 17 (depends on 16)

The computer-implemented method of claim 16 wherein accepting from a user identifier encryption entity an encrypted version of at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data comprises:
accepting from a user identifier encryption entity at least one hash corresponding to at least one of a device identifier, a username, a real name, an alias, a unique identifier, a date, a date and time, or biometric data.

### Claim 18 (depends on 15)

The computer-implemented method of claim 15 wherein accepting from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption comprises:
accepting from a user identifier encryption entity at least one encrypted persona corresponding to a user having at least one instance of data for encryption.

### Claim 19 (depends on 15)

The computer-implemented method of claim 15 wherein encrypting the at least one instance of data to produce level-one-encrypted data comprises:
encrypting the at least one instance of data via public key cryptography.

### Claim 20 (depends on 19)

The computer-implemented method of claim 19 wherein encrypting the at least one instance of data via public key cryptography comprises:
encrypting the at least one instance of data using a certificated public key.

### Claim 21 (depends on 20)

The computer-implemented method of claim 20 wherein encrypting the at least one instance of data using a certificated public key comprises:
encrypting the at least one instance of data using an RSA key.

### Claim 22 (depends on 15)

The computer-implemented method of claim 15 wherein encrypting the at least one instance of data to produce level-one-encrypted data comprises:
encrypting the at least one instance of data using a symmetric key to produce level-one-encrypted data.

### Claim 23 (depends on 15)

The computer-implemented method of claim 15 wherein encrypting the at least one instance of data to produce level-one-encrypted data comprises:
encrypting the at least one instance of data using a public key that is not held by a certificating authority.

### Claim 24 (depends on 15)

The computer-implemented method of claim 15 wherein encrypting the at least one instance of data to produce level-one-encrypted data comprises:
encrypting the at least one instance of data to produce level-one-encrypted data, wherein the machine is further configured to delete the at least one instance of data subsequent to producing the level-one-encrypted data.

### Claim 25 (depends on 15)

The computer-implemented method of claim 15 wherein associating the at least one encrypted identifier with the level-one-encrypted data, and wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity comprises:
associating as metadata the at least one encrypted identifier with the level-one-encrypted data, and wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity.

### Claim 26 (depends on 15)

The computer-implemented method of claim 15 wherein associating the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity comprises:
associating as descriptive metadata the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and further wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity.

### Claim 27 (depends on 26)

The computer-implemented method of claim 26 wherein associating as metadata the encrypted identifier with level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity comprises:
associating as descriptive metadata the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key is inaccessible to the user identifier encryption entity, and wherein the encrypted identifier functions as a key-pair designator for a level-one-encryption entity, and further wherein a decryption key for decrypting the encrypted identifier is inaccessible to the level-one-encryption entity.

### Claim 28 (depends on 15)

The computer-implemented method of claim 15 wherein transmitting the level-one-encrypted data and associated encrypted identifier comprises:
transmitting the level-one-encrypted data and associated encrypted identifier to a level-two-encryption entity.

### Claim 29

A computer program product comprising:
an article of manufacture including a signal-bearing medium bearing:
(1) one or more instructions for accepting from a user identifier encryption entity at least one encrypted identifier corresponding to a user having at least one instance of data for encryption;
(2) one or more instructions for encrypting the at least one instance of data to produce level-one-encrypted data;
(3) one or more instructions for associating the at least one encrypted identifier with the level-one-encrypted data, wherein a level-one decryption key for the level-one-encrypted data is inaccessible to the user identifier encryption entity; and
(4) one or more instructions for transmitting the level-one-encrypted data and associated encrypted identifier.

### Claim 30 (depends on 29)

The computer program product of claim 29, wherein the signal-bearing medium comprises:
at least one of:
a computer-readable medium;
a recordable medium; or
a communications medium.

### Claim at position 31

31-35. (canceled)
