Application programming interface for certificate management systems

Inventors

Fynaardt, Daniel R.

Assignees

Integrity Security Services LLC

Interested in licensing this patent?

MTEC can help explore whether this patent might be available for licensing for your application.

Publication Number

US-11706207-B1

Patent

Publication Date

2023-07-18

Expiration Date


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.

Core Innovation

The invention describes an API-based certificate management architecture for securely provisioning at least one computerized device. A certificate API device is communicatively connected to the computerized device via a first secure communication channel, receives a digital asset, and loads the digital asset into the computerized device. The digital asset comprises an enrollment package and an end entity certificate package.

The certificate API device receives, via an API, an enrollment request for the at least one computerized device, where the enrollment request facilitates vehicle to vehicle or vehicle to infrastructure communications. Via the API, the certificate API device generates an enrollment package by transmitting at least one enrollment certificate request to a certificate management service (CMS), and the CMS generates one or more enrollment certificates for the enrollment package.

The certificate API device also generates the end entity certificate package by transmitting at least one end entity certificate request to the CMS, and the CMS generates one or more end entity certificates for the end entity certificate package. The certificate API device transmits, via the API, the enrollment package and the end entity certificate package to the at least one computerized device, where the packages are configured to modify the computerized device to enable secure communications with additional computerized devices.

Claims Coverage

The document includes three independent claims: a system claim, a method claim, and a non-transitory computer-readable media claim. Across the independent claims, the inventive features center on API-based enrollment requests, CMS generation of an enrollment package and an end entity certificate package, and transmission of both packages to modify a computerized device for secure communications.

API-based secure provisioning using an enrollment package and end entity certificate package

A certificate API device is connected to at least one computerized device via a first secure communication channel, receives a digital asset comprising an enrollment package and an end entity certificate package, and is operable to load the digital asset into the computerized device.

API enrollment request enabling vehicle to vehicle or vehicle to infrastructure communications

The certificate API device receives, via an API, an enrollment request for at least one computerized device, wherein the enrollment request facilitates vehicle to vehicle or vehicle to infrastructure communications.

CMS-generated enrollment certificates for an enrollment package and CMS-generated end entity certificates for an end entity certificate package

The certificate API device generates, via the API, an enrollment package 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, and generates, via the API, an end entity certificate package 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.

Secure API transmission of enrollment package and end entity certificate package to modify the device for secure communications

The certificate API device transmits, via the API, the enrollment package and the end entity certificate package to the at least one computerized device, wherein the packages are configured to modify the computerized device to enable the computerized device to exchange secure communications with additional computerized devices.

CMS connected to the certificate API device via a secure communication channel

The CMS is connected via a second secure communication channel to the certificate API device, and the CMS provides the one or more enrollment certificates and the one or more end entity certificates to the certificate API device.

Asynchronous API transmission using non-transitory media instructions

One or more non-transitory computer-readable media cause a processor, via an API, to receive an enrollment request, generate an enrollment package and an end entity certificate package by transmitting certificate requests to a CMS, and asynchronously transmit the packages to the at least one computerized device to enable exchanging secure communications with additional computerized devices.

Across the independent claims, the coverage is directed to an API-based certificate provisioning workflow in which an enrollment request facilitates vehicle to vehicle or vehicle to infrastructure communications, a CMS generates an enrollment package and an end entity certificate package, and the certificate API device or API-executing instructions transmit those packages to modify the computerized device for exchanging secure communications with additional computerized devices.

Stated Advantages

Not explicitly described in patent.

Documented Applications

Not explicitly described in patent.

JOIN OUR MAILING LIST

Stay Connected with MTEC

Keep up with active and upcoming solicitations, MTEC news and other valuable information.