IP Library Granted Patent US 8,544,106
Granted Patent B2
US 8,544,106 · App. 12/848,184 · Granted Sep 24, 2013

System and method for enabling access to a protected hardware resource

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 8,544,106
App. No.
12/848,184
Granted
Sep 24, 2013
Kind
B2
Abstract

Systems and methods are disclosed for enabling access to a protected hardware resource. A hardware component includes at least one protected hardware resource. A unique hardware ID and a unique cryptographically secure or randomly generated enable value (EV) are integrated in the hardware component at the time of manufacturing. At run-time, special software generates or receives from an external source an enable register (ER) value and a comparison is made with the stored enable value. If the ER value and the EV match, access to the protected hardware resource is allowed.

Claims (33)

1. A method for selectively enabling access to a protected resource, the method comprising:

providing a unique hardware ID associated with a hardware component having a protected resource;

receiving a restricted software module based on at least the unique hardware ID;

executing the restricted software module on the hardware component to generate or access an enable register (ER) value;

comparing the ER value with a unique stored enable value (EV) stored in a secure location in the hardware component and the protected resource; and

allowing access to the protected resource if the ER value and the EV match.

2. The method of claim 1 , wherein providing the unique hardware ID is achieved through secure communication and authentication.

3. The method of claim 1 , wherein receiving the restricted software module is achieved through secure communication and authentication.

4. The method of claim 1 , wherein the EV has a relationship to the hardware ID.

5. The method of claim 4 , wherein the relationship is defined by one of a proprietary function or a standard cryptographic function.

6. The method of claim 1 , wherein the EV is not related to the hardware ID by any mathematical relationship.

7. The method of claim 1 , wherein the protected resource is a cryptographic engine or module.

8. The method of claim 1 , wherein access to the protected resource is allowed for a predetermined amount of time.

9. The method of claim 1 , wherein access to the protected resource is allowed for a predetermined number of uses.

10. A method for enabling access to a protected resource, the method comprising:

receiving a unique hardware ID associated with a hardware component having a protected resource; and

providing a restricted software module based on at least the unique hardware ID, wherein the restricted software module is configured to generate or access an enable register (ER) value; wherein the restricted software module is configured to compare the ER value with a unique stored enable value (EV) stored in a secure location in the hardware component and the protected resource and to allow access to the protected resource if the ER value and the EV match.

11. The method of claim 10 , wherein receiving the unique hardware ID is achieved through secure communication and authentication.

12. The method of claim 10 , wherein providing the restricted software module is achieved through secure communication and authentication.

13. The method of claim 10 , wherein the EV has a relationship to the hardware ID.

14. The method of claim 13 , wherein the relationship is one of a proprietary function or a standard cryptographic function.

15. The method of claim 10 , wherein the EV is not related to the hardware ID by any mathematical relationship.

16. The method of claim 10 , wherein the protected resource is a cryptographic engine or module.

17. The method of claim 10 , wherein access to the protected resource is allowed for a predetermined amount of time.

18. The method of claim 10 , wherein access to the protected resource is allowed for a predetermined number of uses.

19. A hardware component, comprising:

a unique hardware ID associated with the hardware component;

a protected resource;

a permanently stored unique enable value (EV) associated with the hardware component and the protected resource, wherein the EV is stored in a secure location within the hardware component; and

a restricted software module based on at least the unique hardware ID for selectively enabling access to the protected resource, wherein the restricted software module is executed by the hardware component to:

generate or access an enable register (ER) value;

compare the ER value with the EV; and

allow access to the protected resource if the ER value and the EV match.

Assignments (7)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2020
From: CAVIUM INTERNATIONAL
To: MARVELL ASIA PTE, LTD.
Reel/Frame 053179/0320 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 17, 2020
From: CAVIUM, LLC
To: CAVIUM INTERNATIONAL
Reel/Frame 051948/0807 →
CHANGE OF NAME Recorded Jan 11, 2019
From: CAVIUM, INC.
To: CAVIUM, LLC
Reel/Frame 049367/0717 →
RELEASE OF SECURITY INTEREST Recorded Jul 6, 2018
From: JP MORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: CAVIUM, INC; CAVIUM NETWORKS LLC; QLOGIC CORPORATION
Reel/Frame 046496/0001 →
SECURITY AGREEMENT Recorded Aug 17, 2016
From: CAVIUM, INC.; CAVIUM NETWORKS LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 039715/0449 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2012
From: HAIDER, AMER; BARNER, STEVEN CRAIG; KESSLER, RICHARD EUGENE
To: CAVIUM, INC.
Reel/Frame 028636/0110 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2012
From: HAIDER, AMER; BARNER, STEVEN CRAIG; KESSLER, RICHARD EUGENE
To: CAVIUM NETWORKS
Reel/Frame 028406/0021 →