IP Library › Granted Patent US 11,706,207
Granted Patent B1
US 11,706,207 · App. 18/057,968 · Granted Jul 18, 2023

Application programming interface for certificate management systems

Inventor: Daniel R. Fynaardt (Capistrano Beach, CA)
Assignee: INTEGRITY SECURITY SERVICES LLC
H04L63/0823G06F9/547H04L63/0884H04L63/102H04L9/088H04L9/3263
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 11,706,207
App. No.
18/057,968
Filed
Nov 22, 2022
Granted
Jul 18, 2023
Kind
B1
Art Unit
2439
USPC
726/4
Abstract

A system can include a certificate application programming interface (API) device that is operable to receive, via an application programming interface (API), an enrollment request for the at least one computerized device. The certificate API device can also generate, via the API, an enrollment package and an end entity certificate package for the at least one computerized device by obtaining the enrollment package and the end entity certificate package from a certificate management service (CMS). The certificate API device can also transmit, via the API, the enrollment package and the end entity certificate package to the at least one computerized device. The system can also include the CMS that is operable to provide the enrollment package and the end entity certificate package to the certificate API device.

Claims (60)

1. A system for securely provisioning at least one computerized device comprising:

a certificate application programming interface (API) device that is communicatively connected to the at least one computerized device via a first secure communication channel, and that is operable to receive a digital asset and to load the digital asset into the at least one computerized device, the digital asset comprising an enrollment package and an end entity certificate package, wherein the certificate API device is also operable to:

receive, via an API, an enrollment request for the at least one computerized device, wherein the enrollment request facilitates vehicle to vehicle or vehicle to infrastructure communications;

generate, via the API, the enrollment package for the at least one computerized device by transmitting at least one enrollment certificate request to a certificate management service (CMS), which generates one or more enrollment certificates for the enrollment package;

generate, via the API, the end entity certificate package for the at least one computerized device by transmitting at least one end entity certificate request to the CMS, which generates one or more end entity certificates for the end entity certificate package; and

transmit, via the API, the enrollment package and the end entity certificate package to the at least one computerized device, wherein the enrollment package and the end entity certificate package are configured to modify the at least one computerized device, which enables the at least one computerized device to exchange secure communications with additional computerized devices,

wherein the CMS is connected via a second secure communication channel to the certificate API device, and

wherein the CMS provides the one or more enrollment certificates and the one or more end entity certificates to the certificate API device.

2. The system of claim 1 , wherein the certificate API device is operable to:

receive, via the API, a request for a computerized device status for the at least one computerized device; and

transmit, via the API, a response to the request, the response comprising metadata indicating whether an enrollment certificate has been received from the CMS for the at least one computerized device.

3. The system of claim 1 , wherein the certificate API device is operable to:

receive, via the API, a request for an enrollment status for a group of computerized devices; and

transmit, via the API, a response to the request, the response comprising metadata indicating a number of enrollment certificates and end entity certificates received for the group of computerized devices.

4. The system of claim 1 , wherein the enrollment request comprises a computerized device identifier corresponding to an externally accessible serial number for the at least one computerized device.

5. The system of claim 1 , wherein the at least one computerized device comprises an electronic control unit of an automobile.

6. The system of claim 1 , wherein the certificate API device is operable to receive and archive a wrapped key for a matching enrollment package in response to detecting that one of the at least one computerized device comprises volatile memory.

7. The system of claim 6 , wherein the certificate API device is operable to retrieve and transmit the wrapped key with metadata so that it is properly associated with the one of the at least one computerized device.

8. The system of claim 1 , wherein the certificate API device is operable to provide the enrollment package and the end entity certificate package to the at least one computerized device without a connection to an external network.

9. The system of claim 1 , wherein the at least one computerized device is a road-side unit (RSU), and wherein the certificate API device is operable to provide the enrollment package to the at least one computerized device without providing the end entity certificate package but optionally with providing application certificates.

10. The system of claim 9 , wherein the road-side unit is a street light sensor or a construction warning sensor.

11. The system of claim 1 , wherein the certificate API device is operable to generate the end entity certificate package by bundling one or more end entity certificates retrieved from the CMS.

12. The system of claim 1 , wherein the certificate API device is operable to generate the enrollment package by bundling one or more enrollment certificates retrieved from the CMS.

13. A method for securely provisioning at least one computerized device comprising:

receiving, via an application programming interface (API), an enrollment request for at least one computerized device, wherein the enrollment request enables vehicle to vehicle or vehicle to infrastructure communications;

generating, via the API, an enrollment package, based at least on the enrollment request, for the at least one computerized device by obtaining the enrollment package from a certificate management service (CMS);

generating, via the API, an end entity certificate package for the at least one computerized device by obtaining the end entity certificate package from the CMS; and

transmitting, via the API, the enrollment package and the end entity certificate package to the at least one computerized device, the enrollment package and the end entity certificate package to modify the at least one computerized device to enable exchanging secure communications with additional computerized devices.

14. The method of claim 13 , comprising:

requesting, via the API, a computerized device status for the at least one computerized device from the CMS.

15. The method of claim 13 , comprising:

requesting, via the API, an enrollment status for a group of computerized devices from the CMS.

16. The method of claim 13 , wherein the enrollment request comprises a computerized device identifier corresponding to an externally accessible serial number for the at least one computerized device and, if needed, an associated wrapped key and device information.

17. The method of claim 13 , wherein the at least one computerized device comprises an electronic control unit of an automobile.

18. The method of claim 13 , comprising:

retrieving a wrapped key in response to detecting the at least one computerized device comprises volatile memory.

19. The method of claim 18 , comprising:

transmitting the wrapped key to the at least one computerized device.

20. The method of claim 13 , comprising:

retrieving the enrollment package and the end entity certificate package without a connection to an external network.

21. One or more non-transitory computer-readable media comprising a plurality of computer-executable instructions for an application programming interface (API) that uses a digital asset comprising an enrollment package and an end entity certificate package, wherein the plurality of computer-executable instructions, when executed by a processor, causes the processor to:

receive, via the API, an enrollment request for at least one computerized device, wherein the enrollment request facilitates vehicle to vehicle or vehicle to infrastructure communications;

generate, via the API, the enrollment package for the at least one computerized device by transmitting at least one enrollment certificate request to a certificate management service (CMS), which generates one or more enrollment certificates for the enrollment package;

generate, via the API, the end entity certificate package for the at least one computerized device by transmitting at least one end entity certificate request to the CMS, which generates one or more end entity certificates for the end entity certificate package; and

asynchronously transmit, via the API, the enrollment package and the end entity certificate package to the at least one computerized device, wherein the enrollment package and the end entity certificate package are configured to modify the at least one computerized device, which enables the at least one computerized device to exchange secure communications with additional computerized devices.

22. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to provide the enrollment package and the end entity certificate package to the at least one computerized device without a connection to an external network.

23. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to:

receive, via the API, a request for a computerized device status for the at least one computerized device.

24. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to:

receive, via the API, a request for an enrollment status for a group of computerized devices.

25. The one or more non-transitory computer-readable media of claim 21 , wherein the enrollment request comprises a computerized device identifier corresponding to an externally accessible serial number for the at least one computerized device.

26. The one or more non-transitory computer-readable media of claim 21 , wherein the at least one computerized device comprises an electronic control unit of an automobile.

27. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to:

obtain a wrapped key for the at least one computerized device, which comprises volatile memory.

28. The one or more non-transitory computer-readable media of claim 27 , wherein the plurality of computer-executable instructions causes the processor to:

transmit the wrapped key to the at least one computerized device.

29. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to:

provide the enrollment package and the end entity certificate package without a connection to an external network.

30. The one or more non-transitory computer-readable media of claim 21 , wherein the plurality of computer-executable instructions causes the processor to:

generate the enrollment package by bundling the one or more enrollment certificates.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2022
From: FYNAARDT, DANIEL R.
To: INTEGRITY SECURITY SERVICES LLC
Reel/Frame 061908/0807 →
Cited By (6)
US 12,483,543 US 12,562,966 US 12,706,898 US 12,719,850 US 12,726,368 US 12,737,503