IP Library Granted Patent US 7,634,085
Granted Patent B1
US 7,634,085 · App. 11/090,451 · Granted Dec 15, 2009

Identity-based-encryption system with partial attribute matching

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,634,085
App. No.
11/090,451
Granted
Dec 15, 2009
Kind
B1
Abstract

Systems and methods for supporting an identity-based-encryption (IBE) scheme with partial attribute matching capabilities are provided. Plaintext may be encrypted into ciphertext using an IBE public key that is based on an attribute set w. A recipient of the ciphertext may have the attributes in an overlapping but different attribute set w′. The recipient may request an IBE private key for decrypting the ciphertext from an IBE private key generator. After verifying the recipient's credentials, the IBE private key generator may generate IBE private key components based on the recipient's attribute set w′. The recipient may use an IBE private key SK constructed from the IBE private key components to decrypt the ciphertext. Decryption will be successful even though attribute set w′ is different from attribute set w, provided that the overlap |w∩w′| is greater than a threshold value.

Claims (52)

1. A computer-implemented method for using identity-based-encryption (IBE) with partial attribute matching to support secure communications, wherein an attribute overlap threshold d with an integer value defines a required degree of attribute matching for successful decryption, comprising:

at a sender, running an IBE encryption engine with computing equipment to encrypt plaintext M to produce ciphertext E, wherein the IBE encryption engine uses as inputs the plaintext M, IBE public parameters, and an IBE public key associated with an intended recipient, wherein the IBE public key associated with the recipient includes a set of attributes w that correspond to conditions that the intended recipient is to satisfy before being permitted to perform decryption operations; and

at a given recipient, running an IBE decryption engine with computing equipment to decrypt the ciphertext E to produce the plaintext M, wherein the IBE decryption engine uses as inputs the ciphertext E and an IBE private key SK associated with the given recipient, wherein the IBE private key SK contains IBE private key components, each of which corresponds to a respective attribute in an attribute set w′ of attributes of the given recipient, wherein w′ is not equal to w, and wherein in order to decrypt the ciphertext E to produce the plaintext M it is necessary that there is an overlap |w∩w′| between the attribute set w and the attribute set w′ that is equal to or greater than the attribute overlap threshold d.

2. The method defined in claim 1 further comprising:

at the given recipient, requesting the IBE private key components corresponding to attribute set w′ from an IBE private key generator; and

establishing for the IBE private key generator that the given recipient has each of the attributes in the attribute set w′.

3. The method defined in claim 1 further comprising:

requesting that an IBE private key generator provide the IBE private key components to the given recipient over a communications network, wherein requesting that the IBE private key generator provide the IBE private key components comprises providing the IBE private key generator with the attribute set w′ and recipient credentials that certify that the given recipient has each of the attributes in attribute set w′; and

at the IBE private key generator, authenticating the recipient credentials to verify that the given recipient has each of the attributes in the attribute set w′; and

if the given recipient has each of the attributes, providing the requested IBE private key components from the IBE private key generator to the given recipient over the communications network.

4. The method defined in claim 1 wherein an IBE private key generator provides the IBE private key components to the given recipient over a communications network, the method further comprising using the IBE private key generator to generate and publish the IBE public parameters, wherein the IBE private key generator uses a master secret MK and a parameter n in generating the IBE public parameters, wherein the parameter n represents the maximum number of attributes allowed in a valid attribute set w′.

5. The method defined in claim 1 wherein an IBE private key generator provides the IBE private key components to the given recipient over a communications network, the method further comprising using the IBE private key generator to generate and publish the IBE public parameters, wherein the IBE private key generator uses a master secret MK and a parameter m in generating the IBE public parameters, wherein the parameter m represents the maximum number of attributes allowed in a valid attribute set w′ and represents the maximum number of distinct attributes supported by the IBE private key generator.

6. The method defined in claim 1 further comprising obtaining the attribute set w and the attribute set w′ using biometric sensors.

7. The method defined in claim 1 further comprising transmitting the ciphertext from the sender to the given recipient using email.

8. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters.

9. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters; and

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host.

10. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters;

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host; and

at the sender, obtaining the IBE public parameters from the IBE public parameter host over a communications network.

11. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters;

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host;

at the sender, obtaining the IBE public parameters from the IBE public parameter host over a communications network; and

at the sender, following encryption of the plaintext M to produce the ciphertext E, sending the ciphertext E to the given recipient over the communications network.

12. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters;

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host;

at the sender, obtaining the IBE public parameters from the IBE public parameter host over a communications network;

at the sender, following encryption of the plaintext M to produce the ciphertext E, sending the ciphertext E to the given recipient over the communications network;

at the given recipient, receiving the ciphertext E from the sender; and

at the given recipient, requesting the IBE private key SK from the IBE private key generator.

13. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters;

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host;

at the sender, obtaining the IBE public parameters from the IBE public parameter host over a communications network;

at the sender, following encryption of the plaintext M to produce the ciphertext E, sending the ciphertext E to the given recipient over the communications network;

at the given recipient, receiving the ciphertext E from the sender; and

at the given recipient, requesting the IBE private key SK from the IBE private key generator, wherein the IBE private key request includes recipient credentials that establish that the given recipient has each of the attributes in the attribute set w′.

14. The method defined in claim 1 further comprising:

using an IBE private key generator to generate the IBE public parameters;

publishing the IBE public parameters generated by the IBE private key generator on an IBE public parameter host;

at the sender, obtaining the IBE public parameters from the IBE public parameter host over a communications network;

at the sender, following encryption of the plaintext M to produce the ciphertext E, sending the ciphertext E to the given recipient over the communications network;

at the given recipient, receiving the ciphertext E from the sender;

at the given recipient, requesting the IBE private key SK from the IBE private key generator, wherein the IBE private key request includes recipient credentials that establish that the given recipient has each of the attributes in the attribute set w′; and

at the private key generator, verifying the recipient credentials and, if the credentials are authentic, transmitting the IBE private key components for the IBE private key SK from the IBE private key generator to the given recipient over the communications network.

15. The method defined in claim 1 wherein at least one of the IBE private key components corresponds to a biometric attribute of the given recipient.

16. The method defined in claim 1 wherein the set of attributes w includes at least one biometric attribute of the given recipient.

Assignments (11)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
CHANGE OF NAME Recorded Dec 22, 2021
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 058569/0152 →
CHANGE OF NAME Recorded Dec 17, 2018
From: VOLTAGE SECURITY, INC.
To: VOLTAGE SECURITY, LLC
Reel/Frame 051198/0611 →
MERGER AND CHANGE OF NAME Recorded Dec 17, 2018
From: VOLTAGE SECURITY, LLC; ENTIT SOFTWARE LLC
To: ENTIT SOFTWARE LLC
Reel/Frame 051199/0074 →
MERGER Recorded Oct 22, 2018
From: VOLTAGE SECURITY, LLC
To: ENTIT SOFTWARE LLC
Reel/Frame 047253/0802 →
ENTITY CONVERSION AND CHANGE OF NAME Recorded Oct 22, 2018
From: VOLTAGE SECURITY, INC.
To: VOLTAGE SECURITY, LLC
Reel/Frame 047276/0434 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
RELEASE OF SECURITY INTEREST Recorded Feb 27, 2015
From: VENTURE LENDING & LEASING VI, INC.; VENTURE LENDING & LEASING VII, INC.
To: VOLTAGE SECURITY, INC.
Reel/Frame 035110/0726 →
SECURITY AGREEMENT Recorded Feb 7, 2014
From: VOLTAGE SECURITY, INC.
To: VENTURE LENDING & LEASING VI, INC.; VENTURE LENDING & LEASING VII, INC.
Reel/Frame 032170/0273 →