Providing quality of service for certificate management system

Through the QoS manager and QoS arbitrator, certificate requests are managed in the certificate management system, multi-tenant operations and service quality allocation are provided, and digital asset supply delays in computerized equipment are solved, and transaction processing efficiency and system performance are improved.

CN119011149APending Publication Date: 2024-11-22INTEGRITY SECURITY SERVICES LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410973074.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-11-13
Filing Date
2019-11-13
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

When providing quality of service (QoS) levels, existing certificate management systems are difficult to effectively reduce or eliminate delays when supplying digital assets in computerized devices, especially in the case of concurrent requests by multiple clients, which complicates the delay problem. .

Method used

Using QoS manager and QoS arbitrator, it provides multi-tenant operations by managing and distributing certificate requests, ensuring that each client obtains the appropriate quality of service, using the public application programming interface (API) to receive and distribute certificate requests, and based on the request Priority, urgency and waiting time levels are serialized.

Benefits of technology

It effectively reduces the latency of certificate requests, ensures transaction processing efficiency in multi-client environments, avoids the delay problem of small requests affected by large requests, and improves the performance and scalability of certificate management services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011149A_ABST
    Figure CN119011149A_ABST
Patent Text Reader

Abstract

An example system receives a certificate request from a client. Each request indicates: a number of computerized devices requiring a certificate; a timestamp indicating when to transmit the request; and a client. The system includes a quality of service (QoS) manager that distributes requests from clients across queues of clients, each of the queues of clients corresponding to a particular client; and partitioning the request into smaller entry sub-packets corresponding to the subset of computerized devices requiring the certificate. It also includes a QoS arbiter that selects a sequence of entries to be placed on the QoS queue from the client queue based on the number of entries in the QoS queue, a latency level of the certificate management service, and a timestamp indicating when to transmit the request, wherein the QoS manager retrieves entries in the sequence selected by the QoS arbiter from the QoS queue and transmits them to the certificate management service.
Need to check novelty before this filing date? Find Prior Art

Description

This application is a divisional application of a patent application with an application date of November 13, 2019, application number 201911106219.9, and invention name “Providing Service Quality for Certificate Management System”. Technical Field

[0001] The present invention relates to systems, devices and methods for securely generating and provisioning certain types of digital assets, such as security credentials and digital certificates. More particularly, the present invention relates to improved systems, methods and techniques for providing quality of service (QoS) levels while securely provisioning digital assets in a computerized device so as to reduce or eliminate delays in provisioning digital assets in the computerized device. Background Art

[0002] As computers become increasingly miniaturized and commoditized, manufacturers are producing more and more devices that include one or more embedded computers or processors. The computer in a computerized device can control the operation of the device; collect, store, and share data; communicate with other computers and other computerized devices; and update its own software, among other things.

[0003] The Internet of Things (IoT) is a network of computerized physical devices with (one or more) embedded processors, electronics, software, data, sensors, actuators, and / or network connectivity that enable these devices to connect and exchange data via digital networks including the Internet, cellular networks, and other wireless networks. Typically, each "thing" is uniquely identifiable by its embedded computing system and can inter-operate within the existing Internet infrastructure.

[0004] In the IoT sense, “things” can refer to a wide variety of computerized devices, such as consumer appliances, enterprise equipment used in commercial and corporate settings, manufacturing machines, farming equipment, energy-consuming devices in homes and buildings (switches, power outlets, appliances, lighting systems, light bulbs, televisions, garage door openers, sprinkler systems, security systems, etc.), medical and nursing equipment, infrastructure management equipment, robots, drones, and transportation equipment and vehicles, etc.

[0005] For example, most, if not all, modern vehicles and transportation machinery (e.g., cars, trucks, aircraft, trains, ships, motorcycles, scooters, etc.) contain several embedded processors or embedded computers in their subsystems and are computer controlled in at least some aspects. Similarly, a growing number of modern transportation infrastructure equipment (e.g., traffic lights, traffic cameras, traffic sensors, bridge monitors, bridge control systems, etc.) contain at least one and often many embedded processors or embedded computer systems and are computer controlled in at least some aspects. These computer-controlled elements of the transportation network typically communicate with each other, passing various types of information back and forth, and they can react, respond, change their operation or otherwise depend on information communications received / sent to other vehicles in vehicle-to-vehicle (V2V; also referred to as vehicle-to-vehicle (C2C)) and / or communications from / to infrastructure elements in vehicle-to-infrastructure (V2I; also referred to as vehicle-to-infrastructure (C2I)) for safe, correct, efficient and reliable operation.

[0006] Computers in computerized devices operate according to their software and / or firmware and data. To ensure secure and proper operation, computerized devices must be properly initialized and updated with appropriate software, firmware, executable instructions, digital certificates (e.g., public key certificates), cryptographic keys, etc. (hereinafter collectively referred to as "digital assets" or "software") as intended by the manufacturer, so that the IoT consists only of devices that execute authorized, known good software and data. However, problems arise when unauthorized people or organizations (e.g., hackers) replace or change the software in computerized devices. Problems also arise when older software, untested software, unapproved software, and / or software with known program defects is installed in computerized devices.

[0007] In the fields of computer networking, packet switching networks, and telecommunications, Quality of Service (QoS) refers to a collection of technologies and techniques designed to provide improved services to selected users, customers, client devices, or network traffic. The goal of QoS is to provide guarantees on the performance of a service or network. QoS metrics may include delay, availability, latency, bandwidth, upload data transfer rate, download data transfer rate, and upload / download limits per session (i.e., the total amount of megabytes or gigabytes that can be uploaded and / or downloaded during a network session). A service or network may assign different QoS levels to different users and client devices. QoS may also guarantee a certain level of performance to a user or client device based on a request from an application. QoS guarantees are important when computing power or network capacity is limited, or when fulfilling a request is delay sensitive.

[0008] Therefore, it is desirable to provide improved systems, methods and techniques for providing QoS levels while securely provisioning digital assets in computerized devices (such as IoT devices, vehicles, and transportation infrastructure equipment) in order to reduce or eliminate delays in provisioning digital assets in computerized devices. Summary of the invention

[0009] Disclosed herein are systems, methods, and devices for providing QoS levels while implementing requests to generate certain types of digital assets, such as security credentials and digital certificates. In various implementations, the systems, methods, and devices use a QoS manager to provide QoS levels to clients requesting certificates from a certificate management system (CMS). In some implementations, the CMS hosts a certificate management service that accepts requests from the QoS manager to create and provide certain types of digital assets, such as security credentials and public key certificates. The QoS manager uses a QoS arbitrator to populate and manage QoS queues so that the CMS can appropriately manage independent and distinct requests based on their specific QoS levels. In various implementations, the certificate management service is capable of creating certificates for vehicle-to-vehicle and vehicle-to-infrastructure (V2X) devices and vehicle-to-vehicle and vehicle-to-infrastructure (C2X) devices. In various implementations, the system includes a QoS manager that provides QoS levels to clients submitting certificate requests. The QoS manager is communicatively connected to the certificate management service, which generates certificates, such as registration certificates and pseudonym certificates, in response to receiving requests for such certificates from the QoS manager.

[0010] As additionally described herein, the QoS manager enables the certificate management service to provide multi-tenant (e.g., multi-client) operation by providing QoS levels by managing an intermediate client queue corresponding to a tenant and using a QoS arbitrator to select a sequence of entries from the client queue to be placed on the QoS queue. For example, a custom workflow can be created and the custom configuration can be managed by the end entity with the aid of an entity management system.

[0011] In various implementations, a system provides a quality of service (QoS) level to multiple clients (e.g., tenants or customers) requesting certificates from a certificate management service. The system includes a public application programming interface (API) operable to receive certificate requests from multiple clients, wherein each certificate request indicates the number of computerized devices that need certificates, a timestamp indicating when the certificate request is transmitted, and a particular client requesting the certificate. The system also includes a QoS manager operable to distribute certificate requests from multiple clients across multiple intermediate client queues. Each of the multiple client queues corresponds to a particular client requesting a certificate. The QoS manager is also operable to divide certificate requests from clients in the client queues into sub-groups (i.e., smaller groups) of one or more entries, each of the one or more entries having a group size corresponding to a subset of the number of computerized devices that need certificates. The system also includes a QoS arbitrator operable to select a sequence of entries to be placed on a QoS queue from multiple client queues. The QoS arbitrator selects a sequence of entries from the client queues based at least in part on the number of entries in the QoS queue, the latency level of the certificate management service, and the corresponding timestamp indicating when the certificate request is transmitted. The QoS manager is also operable to retrieve entries from the QoS queue in a sequence selected by the QoS arbitrator, and then communicate the retrieved entries to the certificate management service via an internal registration authority API of the certificate management service.

[0012] In some implementations, the packet size corresponding to the subset of the number of computerized devices requiring credentials is a tunable value having a default value of one.

[0013] In some implementations, the computerized device corresponds to one or more of an on-board unit (OBU), an electronic control unit (ECU), and a roadside unit (RSU), wherein the OBU is configured to be installed in one or more of a vehicle, a vessel (e.g., a ship), an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless or wired communication module, and an IoT device, the ECU is configured to be installed in one or more of a vehicle, a vessel, an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless communication module, a wired communication module, and an IoT device, and the RSU is configured to be installed in one or more of a traffic control device, a wireless communication module, a digital billboard, and an electronic sign.

[0014] In some implementations, the plurality of clients include at least one dispenser appliance that acts as a proxy between a certificate management service and at least one computerized device that requires a certificate. The dispenser appliance may be located at a manufacturer's location, such as, for example, a factory. According to such implementations, the at least one computerized device may retrieve the certificate from the dispenser appliance after the dispenser appliance receives the certificate from the certificate management service. In other implementations, the plurality of clients include at least one server that acts as a proxy between the certificate management service and at least one computerized device that requires a certificate. According to such implementations, the at least one computerized device may retrieve the certificate from the server after the server receives the certificate from the certificate management service.

[0015] According to some implementations, each certificate request also indicates a client priority level of the client submitting the request, and wherein the QoS arbitrator is further operable to select a sequence of entries to be placed on the QoS queue from a plurality of client queues based at least in part on the corresponding client priority levels indicated in the certificate request. According to some such implementations, the QoS arbitrator is further operable to dynamically reorder the sequence of entries placed on the QoS queue based at least in part on the corresponding client priority levels indicated in additional certificate requests received from additional clients. In some such implementations, the client priority level for a client is based on a service tier associated with the client. According to some such implementations, a service tier corresponds to one of a plurality of levels ranging from a lowest service level to a highest service level. In some such implementations, a service tier is an alphanumeric string or a numerical value corresponding to one of a plurality of tiers.

[0016] In other implementations, each certificate request also indicates a request urgency level associated with the request, and the QoS arbitrator is operable to select a sequence of entries to be placed on the QoS queue from a plurality of client queues based at least in part on the respective request urgency levels indicated in the certificate request. According to some such implementations, the request urgency level for the certificate request is specified by the client submitting the certificate request. According to some such implementations, the request urgency level corresponds to one of a plurality of levels ranging from a lowest urgency option to a highest urgency option. In some such implementations, the request urgency level is an alphanumeric string or a numeric value corresponding to one of the plurality of levels.

[0017] In yet other implementations, the QoS arbitrator may be operable to select a sequence of entries from the plurality of client queues to be placed on the QoS queue using a round robin technique.

[0018] In still other implementations, the QoS arbitrator is operable to select a sequence of entries to be placed on a QoS queue from a plurality of client queues based on a dynamic priority assigned to each client queue, and wherein the respective dynamic priority assigned to each client queue is assigned by the QoS arbitrator based at least in part on the number of entries in each client queue.

[0019] In additional implementations, the public API is a representational state transfer (REST) ​​API operable to receive certificate requests from multiple clients via a communication network, the certificate requests including a request for a registration certificate; and transmit, on behalf of a certificate management service, a registration certificate generated by a registration certificate authority of the certificate management service to the multiple clients via the communication network. According to some such implementations, the certificate request also includes a request for a pseudonym certificate, and the public REST API is further operable to transmit, on behalf of the certificate management service, a pseudonym certificate generated by a pseudonym certificate authority of the certificate management service to the multiple clients via the communication network. According to some such implementations, the registration certificate is a public key certificate that identifies a custodian of the public key certificate as an authorized participant in an ecosystem including multiple computerized devices, and wherein each authorized participant in the ecosystem is capable of receiving one or more pseudonym certificates that enable communication with the multiple computerized devices.

[0020] In other implementations, the QoS arbitrator may be further operable to dynamically reorder the sequence of entries placed on the QoS queue based at least in part on additional credential requests received from additional clients.

[0021] In some implementations, a computer-implemented method provides a quality of service (QoS) level to a client requesting a certificate from a certificate management service. The computer-implemented method includes receiving certificate requests from a plurality of clients via a common application programming interface (API). Each certificate request indicates: the number of computerized devices that require a certificate; a timestamp indicating when the certificate request was transmitted; and a client identifier for the client requesting the certificate. In some implementations, the client identifier may include one or more of a unique alphanumeric string, an authentication token, and a client credential, such as, for example, a transport layer security (TLS) certificate or other type of digital certificate. The method also includes distributing, by a QoS manager, the certificate requests from the plurality of clients across a plurality of intermediate client queues, each of the plurality of client queues corresponding to a particular client requesting a certificate. The method also includes dividing, by the QoS manager, the client's request into sub-groups (i.e., smaller groups) of one or more entries, each of the one or more entries corresponding to a subset of the number of computerized devices that require a certificate. The method additionally includes selecting, by a QoS arbitrator, a sequence of entries to be placed on a QoS queue from the plurality of client queues based at least in part on the number of entries in the QoS queue, a latency level of the certificate management service, and corresponding timestamps indicating when the certificate request was transmitted. The method also includes retrieving, by the QoS manager, entries from the QoS queue in a sequence selected by the QoS arbitrator.The method also includes transmitting the retrieved entries to the certificate management service via an internal registration authority API of the certificate management service.

[0022] In some implementations, the QoS manager is communicatively connected to a CMS that hosts a certificate management service. In some implementations, the CMS communicates with the QoS manager via calls to an internal application programming interface (API) of the certificate management service. The CMS is configured to securely provide certificates via the QoS manager in response to requests from multiple clients. In additional or alternative implementations, the QoS manager can be hosted by the CMS.

[0023] In certain implementations where the QoS manager is operable to transmit requests for registration certificates to a registration authority of a CMS on behalf of multiple clients, the QoS manager is also operable to re-prioritize client queues or QoS queues before the client queues or QoS queues have been sent to the registration authority. For example, the QoS manager may prioritize clients requesting certificates before transmitting the client's request for registration certificates to the registration authority.

[0024] In other implementations, the registration certificate may be a public key certificate that identifies the custodian of the public key certificate as an authorized participant in an ecosystem including multiple computerized devices, and each authorized participant in the ecosystem may be able to receive one or more pseudonymous certificates that enable communications with the multiple computerized devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate the implementation of the present invention and, together with the specification, are used to explain the principles of the present invention. In the drawings: Figure 1A is a first portion of a swim-lane diagram illustrating an example of a process for securely provisioning credentials, such as certificates, consistent with implementations of the present invention; Figure 1B is a second portion of a swim lane diagram illustrating an example of a process for securely provisioning credentials, such as certificates, consistent with implementations of the present invention; Figure 2 is a block diagram of an example operating environment for a certificate management service and a single client consistent with implementations of the present invention; Figure 3 is a data flow diagram illustrating an example data flow between a single client and a CMS consistent with implementations of the present invention; Figure 4 is a block diagram of an example certificate management service operating in a two client environment consistent with implementations of the present invention; Figure 5 is a data flow diagram illustrating an example data flow between two clients and a CMS consistent with implementations of the present invention; Figure 6 is a block diagram of an example certificate management service operating in a multi-client environment consistent with implementations of the present invention; Figure 7 is a data flow diagram illustrating an example data flow between multiple clients and a CMS consistent with an implementation of the present invention; Figure 8 is a block diagram of an example certificate management service employing a QoS manager to provide QoS levels to multiple clients consistent with an implementation of the present invention; Fig. 9 is a block diagram of an example of a system for implementing a QoS manager consistent with implementations of the present invention; Fig.10 is a data flow diagram illustrating example data flows between multiple clients and a certificate management system employing a QoS manager consistent with implementations of the present invention; and Fig.11is a block diagram of an example of a computing system that may be used to host systems and methods consistent with implementations of the present invention.

[0026] Specific implementation method Reference will now be made in detail to various implementations of the present invention, examples of which are illustrated in the accompanying drawings. Wherever convenient, the same reference numerals will be used throughout the drawings to refer to the same or like parts.

[0027] To ensure safety and proper operation in the field, embedded devices (e.g., electronic control units (ECUs) used in vehicles) need to be properly initialized during manufacturing by provisioning digital assets (such as security assets). Digital assets may include various digital certificates, encryption keys, unique identifiers, and software. In most cases, the CMS or certificate management services that generate these digital assets and the manufacturing plant are located in different regional locations, which are conventionally interconnected via unsecured Internet communications. Therefore, it is desirable to create an end-to-end secure channel from the origin of these digital assets to the device so that the digital assets cannot be accessed or modified by malicious parties or accidentally. Typically, different manufacturing plants and tenants (e.g., customers and clients) require different numbers of digital assets (e.g., bundles of different sizes of digital certificates). Therefore, it is also desirable to minimize delays in providing these digital assets due to computing capacity bottlenecks or communication bandwidth limitations associated with large requests.

[0028] Conventional certificate management systems (CMS) and certificate management services have disadvantages because they issue certificates on a first-come, first-served basis. This creates a technical problem because when a large request is made and received by a customer, requests that come to the certificate management system or service after the large request must wait for the large request to complete. Conventional techniques for minimizing delays or bottlenecks associated with waiting for large certificate requests to be fulfilled include having independent certificate management services with dedicated equipment for each customer. The problem in this conventional approach is that allocating dedicated equipment is expensive, inefficient, and contrary to providing a multi-customer solution because equipment dedicated to a given customer may be idle while other equipment dedicated to another customer is at maximum capacity. Systems, methods, and devices consistent with the present disclosure solve these and other problems of conventional certificate management systems and services. An example solution solves these problems by adopting a fair approach that allows multiple customers (e.g., clients) to submit overlapping or concurrent certificate requests without starving any one client of supply.

[0029] Provisioning generally refers to the set of actions taken to prepare a computerized device with appropriate data and software. It may also include the set of actions taken to properly install the device in the operating environment of the device, thereby making the device ready for operation. The actions include loading appropriate digital assets (e.g., operating system, device drivers, middleware, applications, digital certificates, etc.) into the digital storage device (e.g., memory) of the device, and appropriately customizing and configuring certain digital assets on the device (if necessary), which may be unique to each particular device. The actions may also include verifying that the computerized device is a legitimate device created by a legitimate device manufacturer and not a copied or counterfeit device.

[0030] Actions may also include correctly installing the device into its operating environment, and testing it to verify that it is operating properly. The ability to safely provision only known good devices is complicated by the fact that a device may be built by one manufacturer and later installed into a larger system or device by another manufacturer (e.g., an on-board unit (OBU) built by a component manufacturer may be installed into a car built by an automobile manufacturer). An incorrectly installed device may not function correctly.

[0031] Various implementations consistent with the present invention provide for implementing QoS levels for certificate requests as part of a workflow for secure provisioning of computerized devices, including IoT devices. Such implementations are used to prevent large certificate requests from some clients from creating bottlenecks or undue delays at the expense of smaller requests from other clients.

[0032] Various implementations consistent with the present invention may also use a QoS manager with a QoS arbitrator to split large certificate requests into smaller, more manageable pieces that are placed on QoS queues to efficiently implement certificate requests as part of a secure provisioning and management platform that can be provided as a service to device and system manufacturers.

[0033] Figure 1A and 1B 1 is a swim lane diagram illustrating an example process 100 for securely provisioning credentials such as certificates consistent with implementations of the present invention. In particular, Figure 1A and 1B The example process 100 illustrated in FIG. 1 includes exchanging requests and responses between CMS components to provide certificates to V2X devices. However, the implementations described herein are not limited to V2X devices, and the disclosed principles may be applied to other types of computerized devices and computer-controlled devices, such as C2X devices. That is, the CMS may host a certificate management service that functions as a V2X or C2X certificate management service. Figure 1A and 1BThe example process 100 depicted in FIG. 1 provides credentials to a V2X device. Figure 1A and 1B Depicted are components of an example CMS in the context of V2X flows of requests and responses.

[0034] In various implementations, some or all of process 100 or the illustrated operations may be performed by code executing on a computing system (which may include one or more processors or one or more computing subsystems), by a hardware-only system, or by a system that is a hybrid of the two. Figure 1A and 1B As shown at the top of FIG. 1 , the entities involved in process 100 include a distributor appliance 108 located at a manufacturer (not shown), a registration authority 120 hosted by a CMS (e.g., a CMS hosting a certificate management service), linking authorities 150, 160, a pseudonymous certificate authority 140, and a registration certificate authority 130. In various implementations, these entities can communicate with each other to perform tasks as part of process 100 for providing certificates, as described below with respect to Figure 1A and 1B and as described throughout this disclosure.

[0035] In some implementations, the CMS host may be a system that hosts a certificate management service. The CMS communicates with the QoS manager. In some implementations, such communication is via calls to an internal application programming interface (API) of the certificate management service.

[0036] The CMS includes a registration authority 120, one or more linking authorities 150, 160, a pseudonymous certificate authority 140, and a registration certificate authority 130. An example CMS may include one or more application platforms that run applications for the registration authority 120. These application platforms are communicatively connected to one or more computing engines that perform cryptographic calculations required by the registration authority 120. The one or more application platforms may include one or more virtual machines (VMs) or one or more hardware platforms (e.g., servers, computers, or other computer hardware capable of hosting and executing software applications). The CMS may also include one or more VMs that run the registration certificate authority 130 and that are communicatively connected to one or more computing engines that perform cryptographic calculations required by the registration certificate authority 130. The registration certificate authority 130 is operable to generate a registration certificate and conditionally transmit the registration certificate to the registration authority 120. Hosting Figure 1A and 1BThe example CMS host of the registration authority 120 may also include one or more VMs that run an application for a pseudonymous certificate authority 140 and that are communicatively connected to one or more computing engines that perform cryptographic calculations required by the pseudonymous certificate authority 140. The pseudonymous certificate authority 140 is operable to generate a pseudonymous certificate and conditionally transmit it to the registration authority 120. The CMS host may also include one or more VMs that run first and second linking mechanisms 150, 160 and that are communicatively connected to one or more computing engines that perform cryptographic calculations required by the first and second linking mechanisms 150, 160. The respective applications for the first linking mechanism 150 and the second linking mechanism 160 may be operable to generate a link value and conditionally transmit it to the registration authority 120.

[0037] Hosting Figure 1A and 1B The CMS host of the registration authority 120 shown in may also include one or more application platforms that run applications for the registration authority 120 and are communicatively connected to one or more computing engines that perform cryptographic calculations required by the registration authority 120. The CMS host may additionally include one or more application platforms that run applications for the registration certificate authority 130 and are communicatively connected to one or more computing engines that perform cryptographic calculations required by the registration certificate authority 130, which are operable to generate a registration certificate and conditionally transmit the registration certificate to the registration authority 120. The CMS host may also include one or more application platforms that run applications for the pseudonym certificate authority 140 and are communicatively connected to one or more computing engines that perform cryptographic calculations required by the pseudonym certificate authority 140, which are operable to generate a pseudonym certificate and conditionally transmit the pseudonym certificate to the registration authority 120. In addition, the CMS host may include one or more application platforms that run applications for the first linking authority 150 and are communicatively connected to one or more computing engines that perform cryptographic calculations required by the first linking authority 150. Finally, the CMS host may also include one or more application platforms that run applications for the second linking mechanism 160 and are communicatively connected to one or more computation engines that perform cryptographic calculations required by the second linking mechanism 160. The linking mechanisms 150, 160 may be operable to generate a link value and conditionally communicate the link value to the registration mechanism 120.

[0038] In still other implementations, the registration certificate authority 130 may be operable to generate a registration certificate in response to receiving a request for a registration certificate from the registration authority 120; the pseudonym certificate authority 140 may be operable to generate a pseudonym certificate in response to receiving a request for a pseudonym certificate from the registration authority 120; and the first linking authority 150 and the second linking authority 160 may be operable to generate a link value in response to receiving a request for a link value from the registration authority 120. In alternative or additional implementations, the registration certificate authority 130 may be operable to generate a registration certificate in response to receiving a request directly from a computerized device. That is, there are multiple ways to obtain a registration certificate, and Figure 1A and 1B The example process 100 shown in FIG. 1 is merely an example method.

[0039] like Figure 1A As shown in the example of , process 100 begins with operations 105-135 related to registration. The primary role of the registration certificate authority 130 is to implement a request from the registration authority 120 to issue a registration certificate to an end-user device (such as, for example, the dispenser appliance 108). As described below with reference to Figure 1A As described in the example registration-related operations 105-135 shown in , the registration certificate authority 130 can interact directly with the registration authority 120 to issue a requested registration certificate to the dispenser appliance 108. In an additional or alternative implementation, the registration certificate authority 130 can communicate directly with the dispenser device 108, which is operable to act as a proxy between the CMS hosting the certificate management service and the computerized device requiring the registration certificate, wherein the computerized device requires the registration certificate, and a server having a proxy that acts as a client requesting the registration certificate. For example, the registration certificate authority 130 can communicate directly with the dispenser appliance 108 located at a manufacturer's location (e.g., a manufacturer's factory).

[0040] At 105, the manufacturer's dispenser appliance 108 requests a registration certificate from a registration authority 120, wherein the registration certificate is to be provisioned to (e.g., used by) the computerized device, and wherein the request may identify the computerized device as the destination of the registration certificate. The request may be, for example, the manufacturer's dispenser appliance 108 requesting a registration certificate for a new computerized device (e.g., a new product). A registration certificate is a public key certificate that identifies its holder as an authorized participant in an ecosystem, wherein all participants must share a valid registration certificate (such as, for example, the U.S. Department of Transportation (USDOT) V2X ecosystem), and wherein authorized participants are also able to receive pseudonymous certificates that enable communication and operation of devices within the ecosystem (e.g., to enable communication and operation between vehicles and roadside infrastructure in the example of the USDOT's V2X ecosystem).

[0041] At 110, a request for a registration certificate is received at the registration authority 120 and then transmitted from the registration authority 120 to the registration certificate authority 130. In various implementations, the operation may involve the registration authority 120 decrypting and verifying the request using a list of unapproved devices (e.g., a blacklist), which includes signature verification, checking the revocation status of the device (e.g., a computerized device) that is the destination of the registration certificate, and determining whether the requester (e.g., the dispenser appliance 108) is allowed to request a registration certificate from the registration authority 120. For example, operation 110 may include determining whether the user from the manufacturer is an authorized user (e.g., part of the staff). In some implementations, the registration authority 120 may also determine at 110 whether the computerized device (e.g., a product) for receiving the registration certificate is approved for use. In some instances, a list of approved devices (e.g., a whitelist) may be provided by a regulator and used by a provisioning controller to make this determination. After verifying the request for the registration certificate, the request is transmitted from the registration authority 120 to the registration certificate authority 130. The request may be sent as an enrollment certificate generation request created by the registration authority 120 .

[0042] At 115, a request for a registration certificate is received at the registration certificate authority 130. In response to receiving the request, at 120, the registration certificate authority 130 generates the requested registration certificate and transmits the generated registration certificate back to the registration authority 120. At 125, the registration certificate is received at the registration authority 120, and at 130, the registration authority 120 transmits the registration certificate to the dispenser appliance 108. At 135, the dispenser appliance 108 receives the registration certificate. At this point, the dispenser appliance 108 can provision the registration certificate to the device so that the device can use the registration certificate and complete registration-related operations.

[0043] Operation 140-199 involves provisioning a pseudonym certificate. In some implementations, operation 140-199 for requesting, generating, and provisioning a pseudonym certificate includes using a QoS manager ( Figure 1A and 1B Not shown, but see Figure 8 and 9QoS managers 801 and 901 of the manufacturer) to provide QoS levels to multiple clients requesting pseudonymous certificates. At 140, the distributor appliance 108 requests a pseudonymous certificate from the registration authority 120. The pseudonymous certificate will be supplied to the computerized device (e.g., used by it), and the request may identify the computerized device as the destination for the pseudonymous certificate. The request may be, for example, a manufacturer's distributor appliance 108 requesting a pseudonymous certificate for a computerized device that previously received a registration certificate (e.g., a registered computerized device). The request for a pseudonymous certificate may include a client request for a certain amount of public key certificates (e.g., one week's worth, one month's worth, or one year's worth).

[0044] At 145, a request for a pseudonym certificate is received at the registration authority 120, which then initiates the provisioning of the pseudonym certificate.

[0045] At operations 152-170, the linking mechanism 150, 160 interacts directly with the registration mechanism 120 to fulfill the request for link values. At 150, the registration mechanism 120 transmits to the linking mechanism 1 150 a request for a first set of link values ​​(LA1).

[0046] At 155, in response to receiving the request for the first set of link values, linking mechanism 1 150 generates and / or transmits the first set of link values ​​to registration mechanism 120. That is, linking mechanism 1 150 may transmit the first set of previously generated link values ​​(i.e., pre-generated link values), or linking mechanism 1 150 may generate and then transmit the first set of link values ​​without pre-generated values. At 157, the first set of link values ​​is received at registration mechanism 120. At 160, registration mechanism 120 transmits a request for a second set of link values ​​(LA2) to linking mechanism 2 160.

[0047] Next, if Figure 1B As shown in , at 165, in response to receiving the request for the second set of link values, linking mechanism 2 160 generates and / or transmits the second set of link values ​​to registration mechanism 120. In various implementations, linking mechanism 2 160 may transmit a pre-generated second set of link values, or alternatively, linking mechanism 2 160 may generate and transmit the second set of link values. At 170, the second set of link values ​​is received at registration mechanism 120.

[0048] In some implementations, Figure 1A and 1BThe linking authorities 150, 160 shown in FIG. 1 can link the identity of the certificate requester (i.e., the unique identifier of the certificate requester) to the issued pseudonymous certificate for revocation purposes. That is, linking authority 1 150 and linking authority 2 160 respectively provide the first and second set linking values ​​as the unique identifier of the device of the certificate requester to the pseudonymous certificate issued by the pseudonymous certificate authority 140 (as part of process 100). At operations 152 and 162, linking authority 1 150 and linking authority 2 160 receive the request for the linking value sent from the registration authority 120, and then provide the requested linking value to the registration authority 120 at operations 155 and 165.

[0049] Continue to refer Figure 1B At 175, the registration authority 120 transmits a request for a pseudonym certificate to the pseudonym certificate authority 140. The request may be sent as a batch of pseudonym certificate generation requests created by the registration authority 120.

[0050] At 180, a request for a pseudonym certificate is received at the pseudonym certificate authority 140. In response to receiving the request, at 185, the pseudonym certificate authority 140 generates the requested pseudonym certificate and transmits the generated pseudonym certificate back to the registration authority 120. At 190, the pseudonym certificate is received at the registration authority 120.

[0051] At 195, the dispenser appliance 108 may send a plurality of requests to the registration authority 120 to query whether the requested pseudonym certificate is ready (i.e., generated and available). In some implementations, the query of operation 195 may be sent at any time after the request for the pseudonym certificate is sent at operation 142. For example, after the request for the pseudonym certificate is sent to the registration authority 120 at operation 142, the dispenser appliance 108 may then periodically send queries to the registration authority 120 to determine whether the requested pseudonym certificate is read. In this example, one or more of the queries of operation 195 may be sent in parallel with operations 145-190 (i.e., when the pseudonym certificate is generated).

[0052] At 198, when the pseudonym certificate is ready, the registration authority 120 transmits the pseudonym certificate to the dispenser appliance 108. At 199, the dispenser appliance 108 receives the pseudonym certificate. At this point, the dispenser appliance 108 can provision the pseudonym certificate to the device so that the device can use the pseudonym certificate, and the operation for provisioning the pseudonym certificate is completed.

[0053] In additional or alternative implementations, a process similar to process 100 described above may be used to provide credentials to other computerized devices (such as, for example, C2X devices). Figure 1A and 1BA CMS with components similar to those shown in FIG. 1 can provide certificates to one or more onboard units (OBUs), electronic control units (ECUs), or roadside units (RSUs). Such OBUs and ECUs can be configured to be installed in vehicles, vessels (e.g., ships), aircraft (e.g., airplanes and drones), spacecraft, medical devices, robots, wireless or wired communication modules, and IoT devices. Similarly, RSUs can be installed in traffic control devices (e.g., traffic signals), electronic sign system devices, and digital display devices (e.g., electronic billboards).

[0054] It should be understood that this article is about Figure 2-9 The described QoS manager, QoS arbitrator, and QoS queues may be used to provide QoS levels to clients requesting certificates in a V2X context as well as a C2X context.

[0055] Figure 2 An example operating environment 200 is depicted in which a single client 202 interacts with a certificate management service 280. In some implementations, the certificate management service 280 may be a V2X certificate management service. In additional or alternative implementations, the certificate management service 280 may be a C2X certificate management service. As shown, the client 202 may submit a request for a certificate to one or more computerized devices via a network 235. Figure 2 In the example of , network 235 is the Internet. In some implementations, the computerized device corresponds to one or more of a vehicle, a vessel (e.g., a ship), an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless or wired communication module, and an IoT device. For example, the computerized device may correspond to an OBU or ECU of a vessel, an aircraft, a spacecraft, a robot, a drone, a medical device, an IoT device, or a vehicle. Additionally, for example, the computerized device may correspond to an RSU of a digital billboard, an electronic sign, or a traffic control device (e.g., a traffic signal, a traffic light, or an electronic traffic sign system).

[0056] In operating environment 200, a request for a certificate is received by a client-side representation state transfer (REST) ​​API 205 of a certificate management service 280. Figure 2 As shown in , the client REST API 205 can be a public API, and the certificate management service 280 can be a V2X or C2X certificate management service. The certificate management service 280 accepts the request for the certificate, completes the task within the time frame, and then returns the result (e.g., the generated certificate) to the client 202 via the network 235. In some implementations, the time frame can be a few minutes, a few hours, or a few days, depending on the processing capacity of the certificate management service 280.

[0057] The certificate management service 280 includes components for generating requested certificates. Figure 2 In the example of , these components include registration authority 220, registration certificate authority 230, pseudonym certificate authority 240, linking authority 1 250 and linking authority 2 260.

[0058] In additional or alternative implementations, the components of the certificate management service 280 may vary depending on whether the certificate management service 280 is configured as a V2X or C2X certificate management service. For example, where the certificate management service 280 is used as a C2X certificate management service, the certificate management service 280 may include a long-term certificate authority (LTCA) configured to implement a role similar to that of the registration certificate authority 230. Similarly, when the certificate management service 280 is implemented as a C2X certificate management service, the certificate management service 280 may include an authority (AA) that implements a role similar to that of the pseudonymous certificate authority 240. The components of the certificate management service 280 are described in the following paragraphs.

[0059] In an example, the certificate management service 280 may be implemented as a CMS. Various implementations of the certificate management service 280 may be used for extremely high volume device transaction and certificate generation processing. In various implementations, the certificate management service 280 may be implemented using multiple servers, multiple hardware security modules (HSMs), multiple compute or compute engines, and multiple application platforms. In an example implementation, the application platforms may each include one or more virtual machines (VMs) for hosting the registration authority 220, the registration certificate authority 230, the pseudonym certificate authority 240, and the linking authorities 250 and 260. In additional or alternative implementations, the application platforms may each include one or more hardware platforms, such as, for example, an application server, a computer, or other computer hardware capable of hosting and executing software applications. Figure 2 In the example of , the application platform for the registration certificate authority 230 may be one or more VMs running the application for the registration certificate authority 130, and the application platform for the pseudonymous certificate authority 240 may be one or more VMs operable to host and run the application for the pseudonymous certificate authority 240. Similarly, the application platform for the linking authority 1 250 may be one or more VMs configured to host and run the linking authority 1 application, and the application platform for the linking authority 2 260 may be one or more VMs operable to host and run the linking authority 2 application. Non-limiting examples of the certificate management service 280 may be implemented in a private data center, a cloud data center (such as, for example, Amazon Web Services (AWS) from Amazon), or in a hybrid of private and cloud data centers.

[0060] In some implementations, the certificate management service 280 may provide security certificates such as, for example, registration certificates and pseudonym certificates for use by the manufacturer's dispenser appliance 108, which may be described in detail in relation to Figure 1A and 1B In some implementations, the certificate management service 280 can interact with a digital asset management system (DAMS) to provide Figure 1A and 1B The dispenser appliance 108 shown in FIG. 1 provides the credentials.

[0061] like Figure 2 As shown in FIG. 2 , the architecture of the certificate management service 280 includes a registration authority 220, a registration certificate authority 230, a pseudonym certificate authority 240, a link authority 1 250, and a link authority 2 260. Each of these components can utilize a corresponding dedicated computing engine (not shown) to perform tasks. For example, the registration authority 220 can utilize a registration authority computing engine, the registration certificate authority 230 can utilize a registration certificate authority computing engine, the pseudonym certificate authority 240 can utilize a pseudonym certificate authority computing engine, the link authority 1 250 can utilize a link authority 1 computing engine, and the link authority 2 260 can utilize a link authority 2 computing engine. The functionality of each of these components is described in the following paragraphs.

[0062] The architecture of the certificate management service 280 advantageously separates non-security related applications from security functions. Figure 2 As shown in the example of , the registration authority 220, the enrollment certificate authority 230, the pseudonymous certificate authority 240, and the linking authorities 250, 260 are implemented as applications on their own VMs, which execute on their own dedicated computing engines, all of which are separated from any non-security related applications and functions. This provides technical and security advantages and improvements over conventional systems, where the performance of the HSM is slow, or the cloud service provider cannot provision the HSM, or where their proper management of the HSM is uncertain. In the certificate management service 280, all cryptographic operations requiring the HSM are performed in the computing engine (e.g., one or more of the computing engines).

[0063] By separating critical security functions from each other and onto separate compute engines, such as Figure 2 As shown in , for example, computationally intensive cryptographic and security functions (e.g., elliptic curve butterfly expansion calculations or elliptic curve digital signatures) performed by the registration authority 220, the registration certificate authority 230, the pseudonym certificate authority 240, and the linking authorities 250, 260 are performed significantly faster than existing registration authority systems. Figure 8-10A Quality of Service (QoS) manager is described, which is designed to enable significant improvements in transaction processing in a multi-client environment by enabling "bottleneck" applications to be individually scaled as needed. Thus, implementations consistent with the present disclosure provide a unique, technically advantageous system architecture to reduce bottlenecks associated with existing registry systems. For example, if a registry application running on the registry 220 needs to be scaled, additional VMs can be added, and no changes may be required in the secure computing capabilities of the (one or more) registry compute engines. Alternatively, if secure computing is the limiting performance, additional secure registry compute engines can be added. This same multi-dimensional scaling is true for other components of the certificate management service 280. These capabilities provide significant performance improvements and scalability over existing secure credential management systems (SCMS).

[0064] In some implementations, respective application platforms for the registration authority 220, enrollment certificate authority 230, pseudonym certificate authority 240, and linking authorities 250, 260 are communicatively connected to the compute engine via respective sets of input message queues so that these components of the certificate management service 280 can be scaled independently of each other.

[0065] As mentioned above and Figure 2 As shown in the non-limiting example of , each of the registration authority 220, the certificate authority 230, 240, and the linking authority 250, 260 can be implemented as an application on their own virtual machine (VM). In an additional or alternative implementation, one or more of the registration authority 220, the certificate authority 230, 240, and the linking authority 250, 260 can be executed on a hardware platform (e.g., a server or a computing engine). The role and functionality of each of these applications executed on an application platform (e.g., a VM or a hardware platform) is described in the following paragraphs.

[0066] In various implementations, the registration authority 220 can be an authority in a provisioning network that verifies user requests for digital certificates or other types of digital security assets and enables certificate authorities (e.g., the registration certificate authority 230 and the pseudonymous certificate authority 240) to issue digital certificates. In various implementations, the registration authority 220 can be similar to registration authorities known in public key infrastructure (PKI) systems. In various implementations, the client REST API 205 can pass certificate requests to the registration authority 220, which can be implemented as a representational state transfer (REST) ​​web service. In various implementations, there can be multiple instances of the registration authority 220 executing at the same time. This similarly represents Figure 2. The registration authority functionality of the certificate management service 280 is decentralized in that its functionality can be performed by multiple instances of the registration authority 220 implemented as a REST web service. The primary role for the registration authority 220 is to grant and fulfill certificate provisioning requests while keeping the signing pseudonym certificate authority 240 aware of which certificates end up in a particular computerized device. The registration authority 220 interacts directly with the pseudonym certificate authority 240, linking authorities 250, 260 via message queues in order to fulfill its role within the certificate management service 280.

[0067] In some implementations, the registry 220 (and Figure 2 The other components of the certificate management service 280 can be connected to a database. The certificate management service 280 can use a data store or a collection of databases for data storage and retrieval. For example, the database used can be composed of one or more database logical or physical units, each of which has one or more tables to achieve data separation when necessary. As used herein, the term "database" refers to one or more databases or data stores. In some implementations, the use of multiple databases can allow for Figure 2 The data separation between the other components of the registration authority 220 and the registration authority 220. For example, such use of multiple databases allows for data separation between the registration authority 220, the certificate authorities 230, 240 and the linking authorities 250, 260.

[0068] In a preferred implementation, the database(s) used by the certificate management service 280 is a collection of one or more fast access, low latency databases. In some implementations, the database(s) may be a NoSQL database or database service, such as, for example, the DynamoDB data service provided by Amazon Web Services. In various implementations, the data stored in the database is application dependent, but may include certificates issued in the past, various linking authority values, data about devices to which certificates have been issued, operator actions, etc. Note that the data may be unencrypted, encrypted, or some combination thereof.

[0069] In various implementations, the certificate management service 280 includes a registration certificate authority 230 and a pseudonymous certificate authority 240 because the digital certificates generated by the registration authority 220 are divided into different segments - for example, a registration digital certificate and a pseudonymous digital certificate.

[0070] The registration certificate authority 230 is a decentralized component of the certificate management service 280 because there may be multiple instances of the registration certificate authority 230 executing at the same time. For example, in some implementations, there may be multiple instances of the registration certificate authority 230 executing simultaneously. The registration certificate authority 230 may receive a request for a registration certificate from the registration authority 220. The primary role of the registration certificate authority 230 is to fulfill the request from the registration authority 220 to provide an end-user device (such as, for example, Figure 1A and 1B The dispenser appliance 108 shown in FIG. 100 issues a registration certificate. Figure 1A As described, the registration authority 130 interacts directly with the registration authority 120 in order to fulfill its role within the CMS.

[0071] The pseudonym certificate authority 240 is a decentralized component of the CMS in that there may be multiple instances of the pseudonym certificate authority 240 executing simultaneously. For the pseudonym certificate authority 240, in various implementations, there may be multiple instances of the pseudonym certificate authority 240 executing in parallel at the same time. The pseudonym certificate authority 240 may receive requests for pseudonym certificates from the registration authority 220. The primary role of the pseudonym certificate authority 240 is to fulfill requests from the registration authority 220 to issue pseudonym certificates to, for example, Figure 1A and 1B The pseudonym certificate is issued by an end-user device such as the dispenser appliance 108 shown in FIG. In some implementations, the pseudonym certificate authority 240 implements the request for a short-term pseudonym certificate for V2V functionality. Figure 5 As described, the pseudonymous certificate authority 240 interacts directly with the registration authority 220 in order to implement its functions within the CMS.

[0072] In various implementations, Figure 2 The linking authorities 250, 260 shown in the figure link the identity of the certificate requester (i.e., the unique identifier of the device of the certificate requester) to the issued pseudonym certificate for revocation purposes. That is, the linking authority 1 250 and the linking authority 2 260 provide the corresponding link value as the unique identifier of the device of the certificate requester to the issued pseudonym certificate. The linking authority 1 250 and the linking authority 2 260 can receive a request for the link value from the registration authority 220, and then provide the requested link value to the registration authority 220. The linking authorities 250, 260 interact directly with the registration authority 220 to implement the request for the link value.

[0073] In various implementations, the compute engines include an HSM, which allows these components to perform secure computations without undue threat from hackers. In some embodiments, the compute engines can be designed to perform secure computations themselves without the need for an embedded HSM - in such implementations, they implement an HSM.

[0074] In various implementations, different HSM versions may be used in the CMS. For example, the HSM may include an embedded HSM installed as a plug-in card within one or more computing engines. In such an example implementation, the embedded HSM may be installed in one or more computing engines as a peripheral component interconnect (PCI) HSM or a PCI Express (PCIe) HSM. In addition, for example, the HSM in the certificate management service 280 may include an external network-attached or network-connected HSM that is separate from the computing engines in their own housing.

[0075] Those skilled in the art will recognize that Figure 2 The components and implementation details shown in the example are presented for clarity and simplicity of explanation. Other components, processes, implementation details and variations may be used without departing from the principles of the present invention, as the example is not intended to be limiting and many variations are possible.

[0076] Figure 3 is a data flow diagram illustrating an example data flow between a single client 302 and a CMS 380 consistent with an implementation of the present invention. Figure 3 In the example of , CMS 380 may be implemented as a V2X or C2X CMS. According to some implementations, CMS 380 may host a certificate management service, such as the one described above with reference to Figure 2 Describes the certificate management service 280.

[0077] like Figure 3 As shown in , a client 302 transmits a request 310 for a certificate for one or more computerized devices. In some implementations, the computerized device may be an ECU or OBU configured to be installed in a vehicle. In additional or alternative implementations, the computerized device may be an RSU configured to be installed in traffic control equipment (e.g., traffic lights, electronic traffic sign systems), digital billboards, and other roadside electronic sign systems. In some implementations, each certificate request 310 indicates the number of computerized devices for which a certificate is required, a timestamp indicating when the certificate request 310 was transmitted; and a request for a certificate (e.g., for Figure 3 In some implementations, the identifier for the client (i.e., the client identifier) ​​may include or may be one or more of a unique alphanumeric string, an authentication token, and a client credential (such as, for example, a TLS certificate or other type of digital certificate).

[0078] CMS 380 accepts request 310 and completes the requested task by generating the requested certificate bundle within computing time 315. The certificate bundle is created by CMS 380 within computing time 315, which is a time frame (e.g., minutes, hours, or days). Computing time 315 may vary depending on various factors, such as the workload of CMS 380, the number of computerized devices that require certificates (as indicated in request 310), and the latency level of CMS 380. After generating the certificate bundle (i.e., after computing time 315 has elapsed), CMS 380 then returns the result as a response 325 that is transmitted back to client 302.

[0079] Figure 4 is a block diagram of an example operating environment 400. In particular, Figure 4 Depicted is a certificate management service 480 operating in two client environments consistent with an implementation of the present invention. For brevity, only the certificate management service 480 related to Figure 2 Compared to Figure 4 Differences within.

[0080] exist Figure 4 In the example operating environment 400, two clients 402, 422 (e.g., Client 1 and Client 2) can interact concurrently with a certificate management service 480. As shown, both client 402 and client 422 can submit corresponding concurrent requests for certificates for one or more computerized devices via a network 435. Figure 4 In the example of , network 435 is the Internet. In some implementations, the computerized device corresponds to one or more of a vehicle, a ship, an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless or wired communication module, and an IoT device (e.g., an IoT appliance, an IoT sensor, an IoT switch, an IoT controller, or a wearable IoT device). For example, the computerized device may correspond to an OBU or ECU of a ship, an aircraft, a spacecraft, a robot, a drone, a medical device, an IoT device, or a vehicle. In addition, for example, the computerized device may correspond to an RSU of a digital billboard, an electronic sign, or a traffic control device (e.g., a traffic signal, a traffic light, or an electronic traffic sign system).

[0081] In operating environment 400, a request for a certificate is received by client REST API 405 of certificate management service 480. Figure 4As depicted in , the client REST API 405 may be a public API, and the certificate management service 480 may be a V2X or C2X certificate management service. The certificate management service 480 accepts requests for certificates, completes the task within a time frame, and then returns the results (e.g., the generated certificate) to the client 402, 422 via the network 435. The certificate management service 480 includes components for generating the requested certificate. Figure 4 In the example of , these components include registration authority 420, registration certificate authority 430, pseudonym certificate authority 440, linking authority 1 450 and linking authority 4 460.

[0082] In additional or alternative implementations, the components of the certificate management service 480 may vary depending on whether the certificate management service 480 is configured as a V2X or C2X certificate management service. Figure 2 As described, in an implementation where the certificate management service 480 is used as a C2X certificate management service, the certificate management service 480 may include a long-term certificate authority (LTCA) configured to implement a role similar to that of the registration certificate authority 430. Similarly, when the certificate management service 480 is implemented as a C2X certificate management service, the certificate management service 480 may include an authority that implements a role similar to that of the pseudonymous certificate authority 440.

[0083] In the operating environment 400, there are two concurrent clients 402, 422, both of which can request work from the same certificate management service 480. In the example, client 402 (e.g., client 1) can transmit a request for a large number of computerized devices (e.g., >100,000 vehicles) via network 435, following the certificate request of client 1, and client 422 (e.g., client 2) can transmit a request for certificates for a relatively small number of computerized devices (e.g., <50 vehicles). For a simple certificate management service (V2X or C2X) without a QoS manager, these two requests will be handled in order on a first-come, first-served basis. In this example, client 422 (e.g., client 2) must wait for the job of client 1 to complete before providing any response. That is, even though the request of client 2 is relatively small, the time delay may still be hours or days (i.e., the length of time it takes to fulfill the large request from client 402), rather than the mere minutes it would otherwise take to fulfill the request of client 2.

[0084] Advantageously, rather than enabling a certificate management service to provide QoS levels to multiple clients, the implementations disclosed herein employ a QoS manager (e.g., see Figure 8 and 9QoS managers 801 and 901) so that clients such as client 422 do not experience excessive delays associated with waiting for earlier, large requests to be fulfilled. Figure 8-10 As described, the QoS manager may be used by the certificate management service 480 to distribute certificate requests from the clients 402, 422 across two corresponding intermediate client queues, each of which corresponds to a particular client requesting a certificate (e.g., client 402 or client 422). The QoS manager may also divide the client's requests into smaller groups (i.e., subgroups) of one or more entries, where each entry corresponds to a subset of the number of computerized devices for which the client requires certificates.

[0085] Figure 5 5 is a data flow diagram illustrating an example data flow between two clients 502, 522 and CMS 580 consistent with an implementation of the present invention. Figure 3 Compared to Figure 5 Differences within.

[0086] exist Figure 5 In the example illustrated in , CMS 580 may be a V2X CMS or a C2X CMS. According to some implementations, CMS 580 may host a certificate management service, such as the one described above with reference to Figure 4 Describes the certificate management service 480.

[0087] like Figure 5 As shown in FIG, a client 502 (e.g., client 1) transmits a large request 510 for certificates for a large number of computerized devices (e.g., 110,000 vehicles), and after the large request 510 from client 502, client 522 (e.g., client 2) then transmits a small request 512 for certificates for a smaller number of computerized devices (e.g., 40 vehicles). In various implementations, each certificate request 510, 512 indicates: the number of computerized devices that require certificates (e.g., 110,000 for the large request 510 and 40 for the small request 512); a timestamp indicating when the certificate request was transmitted; and the client requesting the certificate (e.g., a corresponding identifier for client 502 for the large request 510 and client 522 for the small request 512). For example, each certificate request 510, 512 may include a client identifier for the corresponding client 502, 522 requesting the certificate. In some implementations, the client identifier uniquely identifies the client 502 or 522 and may be a unique alphanumeric string, an authentication token, or a client credential such as, for example, a TLS certificate or other type of digital certificate corresponding to the client 502 or 522 .

[0088] Figure 5 It shows how a simple CMS 580 in the absence of a QoS manager can handle two requests 510, 512 in order on a first-come, first-served basis. Once the large request 510 is received by the CMS 580, the CMS 580 requires computing time 515 to perform the calculations required to generate the certificate bundle required to fulfill the large request 510. Figure 5 , once the requested certificate bundle has been generated, a response 525 with the requested certificate bundle is transmitted from CMS 580 to client 502. That is, client 502 will only wait for computation 515 before receiving response 525. In this example, client 522 (e.g., client 2) must wait for a wait time 516 to receive a response 527 to requestlet 512. As shown, the wait time 516 for client 522 includes the entire computation time 515 required for client 1's job to be completed, as well as the additional computation time 517 required to implement requestlet 512 before providing response 527 to requestlet 512. That is, even though Client 2's small request 512 is for far fewer certificates than the large request 510, and can be fulfilled much faster by CMS 580, the wait time 516 may still be hours or days (i.e., the computation time 515 required for the large request 510 from Client 502 to be fulfilled and the computation time 517 for the small request 512 to be fulfilled), rather than the mere minutes it would otherwise take to fulfill Client 2's small request 512.

[0089] Figure 6 6 is a block diagram of an example certificate management service 680 operating in a multi-client environment 600 consistent with an implementation of the present invention. Figure 6 Zhongyu Figure 2 and 4 Compared to the differences that occurred.

[0090] exist Figure 6 , the example operating environment 600 includes multiple clients 602, 622 (e.g., client 1 and client 2), 623, ... 62n that can interact concurrently with a certificate management service 680. As shown, a group of n clients 602, 622, 623, ... 62n can each submit a respective request for a certificate for one or more computerized devices via a network 635 (e.g., the Internet). While this may result in a similar process to that described above with reference to Figure 4 and Figure 5 The delay described is a delay, but the problem may be compounded if the clients 602, 622, 623, ... 62n include multiple large requestors, particularly if small requests are submitted after large requests have been received by the certificate management service 680.

[0091] In the operating environment 600, a request for a certificate is received by a client REST API 605 of a certificate management service 680 (e.g., a public API of a V2X or C2X certificate management service). The certificate management service 680 accepts the request for a certificate, completes the task within a time frame, and then returns the result (e.g., the generated certificate) to the client 602, 622, 623, ... 62n via the network 635. The certificate management service 680 includes components for generating the requested certificate. Figure 6 In the example of , these components include registration authority 620, registration certificate authority 630, pseudonym certificate authority 640, linking authority 1 650 and linking authority 660.

[0092] In additional or alternative implementations, the components of the certificate management service 680 may vary depending on whether the certificate management service 680 is configured as a V2X or C2X certificate management service. Figure 2 and 4 As described, in an implementation where the certificate management service 680 is used as a C2X certificate management service, the certificate management service 680 may include an LTCA configured to implement a role similar to that of the registration certificate authority 630. Similarly, when the certificate management service 680 is implemented as a C2X certificate management service, the certificate management service 680 may include an authority that implements a role similar to that of the pseudonymous certificate authority 640.

[0093] In the operating environment 600, there are multiple concurrent clients 602, 622, 623, ... 62n (e.g., a group of n clients) that can each request work from the same certificate management service 680. In the example, clients 602, 622 (e.g., clients 1 and 2) can transmit a large request for a large number of computerized devices (e.g., >100,000 vehicles) via the network 635, after the certificate requests of client 1 and client 2, and another client 623 can transmit another large request for certificates. Then, the last client 62n in the group of n clients can transmit a small request for a relatively small number of computerized devices (e.g., <50 vehicles). For a simple certificate management service (V2X or C2X) without a QoS manager, these requests will be handled in order on a first-come, first-served basis. In this example, client 62n (e.g., the last client in the n clients) must wait for the previous client's job to complete before providing any response. That is, even though the request from client 62n may be relatively small, the time delay may be hours or days (i.e., still the length of time it takes to fulfill the large request from clients 602, 622, 623), rather than the mere minutes it would otherwise take to fulfill the request from client 62n.

[0094] To address the above issues, the implementation disclosed herein advantageously employs a QoS manager (e.g., see Figure 8 and Fig. 9 QoS managers 801 and 901) so that clients such as client 62n do not experience excessive delays associated with waiting for earlier, large requests to be fulfilled. Figure 8-10 As described, the QoS manager can be used by the certificate management service 680 to distribute certificate requests from clients 602, 622, 623, ... 62n across n corresponding intermediate client queues, each of the n client queues corresponding to a particular client that has requested a certificate. The QoS manager can also divide the certificate requests of the clients in the client queues into smaller groups of one or more entries, each of the one or more entries having a group size corresponding to a subset of the number of computerized devices that need certificates.

[0095] Figure 7 702, 722, 723, ... 72n) and CMS 780 according to an implementation of the present invention. Figure 3 and Figure 5 Compared to Figure 7 Differences within.

[0096] exist Figure 7 In the example illustrated in FIG. 7 , CMS 780 may be a V2X CMS or a C2X CMS. In some implementations, CMS 780 may host a certificate management service, such as the one described above with reference to FIG. Figure 6 Describes the certificate management service 680.

[0097] like Figure 7As shown in FIG. 7 , client 702 (e.g., client 1) transmits a large request 710 for certificates for a large number of computerized devices (e.g., 110,000 vehicles), after the large request 710 from client 702, client 722 (e.g., client 2) then transmits another large request 711, and after that, client 723 transmits yet another large request 713. After large requests 710, 711, and 713 have been received by CMS 780, client 72n transmits a small request 712 for certificates for a relatively small number of computerized devices (e.g., 40 vehicles). In some implementations, each certificate request 710, 711, 712, 713 includes data fields indicating: the number of computerized devices that require a certificate (e.g., 110,000 for large request 710 and 40 for small request 712); a timestamp indicating when this particular certificate request was transmitted (e.g., a date and time indicating the hour, minute, and second of the transmission); and the client requesting the certificate (e.g., a corresponding identifier for clients 702, 722, and 723 for large requests 710, 711, and 713 and client 72n for small request 712). For example, each certificate request 710, 711, 712, 713 may include a client identifier for the corresponding client 702, 722, 72n, 723 requesting a certificate. In some implementations, the client identifier uniquely identifies one of the clients 702, 722, 723, or 72n and may include or may be a unique alphanumeric string, an authentication token, or a client credential, such as, for example, a TLS certificate or other type of digital certificate.

[0098] Figure 7 714. It is shown how CMS 780 handles multiple requests 710, 711, 712, 713 in order, first come, first served, without a QoS manager. Due to the large requests 710, 711, 713 received by CMS 780, CMS 780 requires lengthy, sequential computation time 715, 717, and 718 to generate the large number of requested certificates. For example, CMS 780 requires computation time 715 to perform the computations required to generate the certificate bundle required to fulfill the large request 710 from client 702. Figure 7 In the example of , once the certificate bundle requested by client 702 has been generated, a response 725 with the certificate bundle is transmitted from CMS 780 back to client 702. That is, client 702 only needs to wait for computation 715 before receiving response 725. In this example, client 722 (e.g., client 2) must wait for computation time 715 and additional computation time 717 to receive response 727.

[0099] Finally, due to the fact that its small request 712 was submitted after the large requests 710, 711 and 713, the client 72n with the small request 712 must wait for the longest time of all clients 702, 722, 723, 72n. That is, without using a QoS manager (e.g., see the description below), Figure 8 and 9 In the case of QoS managers 801 and 901), the client 72n will experience a lengthy wait time 716 before providing a response 727 to the small request 712.

[0100] like Figure 7 As shown in , client 72n must endure wait time 716 before receiving response 729 to small request 712. This is because wait time 716 for client 72n includes the entire compute time 715 required to complete the job of client 1, in addition to computation time 717 for completing the request of client 2, computation time 718 for completing the request from client 723, and computation time 719 required to implement small request 712. That is, even if client 72n submits small request 712 for far fewer certificates than large requests 710, 711, and 713, wait time 716 may still be a duration of several hours or days. This is because wait time 716 is the sum of the combined computation time 715, 717, and 718 required for large requests 710, 711, 713 from clients 702, 722, 723 to be implemented and computation time 719 for small request 712 to be implemented. When not used in the following references, Figure 8 and 9 In the case of the QoS managers 801 and 901 discussed, there is no mechanism for fulfilling a small request 712 from a client 72n without first waiting for fulfillment of the earlier submitted large requests 710, 711, and 713. Figure 8-10 As described, the QoS manager enables a CMS or certificate management service to provide QoS levels in a multi-client environment.

[0101] Figure 8 82n in a multi-client environment 800 using a QoS manager 801 to provide QoS levels to multiple clients 802, 822, 823, ... 82n. For the sake of brevity, only the following description is related to Figure 2 , Figure 4 and Figure 6 Compared to Figure 8 Differences within.

[0102] exist Figure 8In the example multi-client environment 800, multiple clients 802, 822 (e.g., clients 1 and 2 out of a total of n clients), 823, ... 82n can interact concurrently with a certificate management service 880. The group of n clients 802, 822, 823, ... 82n can each submit a respective request for a certificate for one or more computerized devices via a network 835 (e.g., the Internet). Although this may result in the same as in the example above with reference to Figure 4 , 5 Delays similar to those described in 7, but the problem is complicated if clients 802, 822, 823, ... 82n submit multiple large requests, especially if small requests are submitted after large requests have been received by the certificate management service 880.

[0103] The certificate management service 880 includes components for implementing requests for certificates submitted by clients 802, 822, 823, ... 82n. Figure 8 As illustrated in FIG. 8 , these components include a QoS manager 801 , a public registry API 805 , a registry 820 , an internal API 825 of the registry 820 , a registration certificate authority 830 , a pseudonymous certificate authority 840 , a link authority 1 850 , and a link authority 8 860 .

[0104] In various implementations, the public registry API 805 is operable to receive certificate requests from n clients 802, 822, 823, ... 82n, where each certificate request indicates the following: the number of computerized devices for which a certificate is required; a timestamp indicating when the certificate request was transmitted; and the client requesting the certificate. For example, each certificate request may include a client identifier for one of the n clients 802, 822, 823, ... 82n requesting a certificate. In some implementations, the client identifier uniquely identifies one of the clients 802, 822, 823, ... 82n and may include one or more of a unique alphanumeric string, an authentication token, and a client credential (such as, for example, a TLS certificate or other type of digital certificate).

[0105] In additional or alternative embodiments, each request may also indicate a corresponding client priority level, which may be based on a service layer associated with the client. In some implementations, a service layer is a numerical value corresponding to one of a plurality of layers in a range from the lowest service level to the highest service level (e.g., service layers 1-10, where 1 is the lowest service level, 5 is a medium service level, and 10 is the highest service level). According to additional or alternative embodiments, each request may also indicate a request urgency level associated with the request. For example, a request urgency level for a certificate request may be specified by a client submitting a certificate request. Such a request urgency level may be a numerical value corresponding to one of a plurality of levels in a range from the lowest urgency option to the highest urgency option (e.g., in 1-10, 1 is the lowest urgency, 5 is for medium urgency requests, and 10 is for the most urgent requests). In various embodiments, a client may make a choice to pay a fee to a service provider (e.g., an entity providing certificate management service 880 or another entity) for priority and urgency levels increased on a per-client or per-request basis. Similarly, the client may choose to selectively lower the priority and urgency levels for certain non-urgent and low priority requests in exchange for a rebate or other incentive.

[0106] Advantageously, Figure 8 The implementation shown in employs a QoS manager 801 to enable a certificate management service 880 to provide QoS levels to clients 802, 822, 823, ... 82n so that clients such as client 82n do not experience excessive delays associated with waiting for an earlier, large request to be implemented. For example, the QoS manager 801 may be used by the certificate management service 880 to distribute certificate requests from clients 802, 822, 823, ... 82n across n corresponding intermediate client queues, each of which corresponds to a particular client having a requested certificate. The QoS manager 801 may also divide the certificate requests of the clients in the client queues into smaller groups of one or more entries, each of which has a group size corresponding to a subset of the number of computerized devices that require a certificate. In some implementations, the group size is a user-tunable parameter having a default value of 1.

[0107] QoS manager 801 acts as an intermediary between clients 802, 822, 823, ... 82n and certificate management service 880. QoS manager 801 can accept certificates from any number of clients (e.g., Figure 8QoS manager 801 may split large requests into smaller requests and feed those smaller requests to separate client queues (not shown, but see below). Fig. 9 91n in the client queues 903, 907, 909, ... 91n). This allows smaller requests to be completed earlier and can support any number of clients. In addition, by using the QoS manager 801, if additional small requests come in, they will be allowed to complete earlier than if the CMS or certificate management service lacked a QoS manager.

[0108] In a multi-client environment 800, a request for a certificate is received by a registration authority API 805 (e.g., a public API) of a QoS manager 801. The QoS manager 801 accepts the request for a certificate on behalf of a certificate management service 880. In various implementations, the QoS manager 801 is operable to distribute certificate requests from n clients 802, 822, 823, ... 82n across n intermediate client queues, where each of the n client queues corresponds to a particular client requesting a certificate. The QoS manager 801 may also be configured to divide the requests of a particular client in the client queue of that client into sub-groups (i.e., smaller groups) of one or more entries, where each of the one or more entries has a group size corresponding to a subset of the number of computerized devices for which the client requires a certificate. As described below with reference to Fig. 9 As described in more detail, in some implementations, the QoS manager 801 includes a QoS arbitrator (not shown, but see Fig. 9 The QoS arbitrator 904 of the present invention. The QoS arbitrator is operable to select a sequence of entries to be placed on the QoS queue from the plurality of client queues based at least in part on the number of entries in the QoS queue, the latency level of the certificate management service 880, and the corresponding timestamp indicating when the certificate request was transmitted. According to some implementations, the QoS manager 801 is operable to retrieve entries from the QoS queue in the sequence selected by the QoS arbitrator, and transmit the retrieved entries to the certificate management service 880 via the internal API 825 of the registration authority 820. The QoS manager 801 then forwards the entries from the QoS queue to the certificate management service 880 via a call to the internal API 825 of the registration authority 820 of the certificate management service 880. The certificate management service 880 then completes the task forwarded to it by the QoS manager 801 within the time frame, and then returns the result (e.g., the generated certificate) to the QoS manager 801. The QoS manager 801 then forwards the result via the registry API 805 and the network 835 as a response to the clients 802, 822, 823, ... 82n.

[0109] In the operating environment 800, there are multiple concurrent clients 802, 822, 823, ... 82n (e.g., a group of n clients) that can interact concurrently with the QoS manager 801, which acts as an intermediary between the n clients and the certificate management service 880. In the example, a client 802, 822 (e.g., client 1 and 2) can transmit a large request for a large number of computerized devices (e.g., >100,000 vehicles) via the network 835, after the certificate request of client 1 and client 2, and another client 823 can transmit another large request for a certificate. Then, the last client 82n in the group of n clients can transmit a small request for a relatively small number of computerized devices (e.g., <50 vehicles). As described above, for the certificate management service 880 with the QoS manager 801, these requests will be placed on the client queue and divided and processed in increments (e.g., subsets of a given packet size) as needed to provide QoS levels to the clients 802, 822, 823, ... 82n. That is, instead of having to handle requests in order on a first-come, first-served basis without regard to the varying size or priority of the requests, the QoS manager 801 is advantageously used to avoid having to process requests sequentially. For example, instead of requiring the last client (e.g., client 82n) to wait for all previous clients' jobs to complete before providing any response, the QoS manager 801 enables the certificate management service 880 to enable a later-arriving but smaller request from client 82n to be completed without undue delay (i.e., hours or days - the length of time it would take to still fulfill a large request from a previous client 802, 822, 823).

[0110] Fig. 9 9 is a block diagram of an example of a system 900 for implementing a QoS manager 901 in accordance with an implementation of the present invention. Figure 8 Compared to Fig. 9 Differences within.

[0111] exist Fig. 9 , the example system 900 includes multiple clients 902, 922 (e.g., clients 1 and 2 out of a total of n clients), 923, ... 92n that can interact concurrently with a QoS manager 901, which acts as an intermediary between the clients and a certificate management service 980. The multiple clients 902, 922, 923, ... 92n can each communicate with the QoS manager 901 via a network 935 (e.g., Fig. 9 The Internet in the non-limiting example of ) submits a corresponding request for a certificate for one or more computerized devices.

[0112] The certificate management service 980 includes a component for implementing a request for a certificate submitted by a client 902, 922, 923, ... 92n. In various implementations, the public registration authority API 905 is operable to receive certificate requests from n clients 902, 922, 923, ... 92n, wherein each certificate request indicates the following: the number of computerized devices for which a certificate is required; a timestamp indicating when the certificate request is transmitted; and the client requesting the certificate. In additional or alternative embodiments, each request may also indicate a corresponding client priority level, which may be based on a service layer associated with the client. In some implementations, a service layer is an alphanumeric string or numerical value corresponding to one of a plurality of layers in a range from the lowest service level to the highest service level (e.g., service layers 1-10, where 1 represents the lowest or bronze service layer, 5 represents the middle or silver layer, 7 represents the high or gold layer, and 10 represents the highest or platinum layer). According to additional or alternative embodiments, each request may also indicate a request urgency level associated with the request. For example, the request urgency level for a certificate request may be specified by the client submitting the certificate request. Such a request urgency level may be an alphanumeric string or numeric value corresponding to one of a plurality of levels ranging from a lowest urgency option to a highest urgency option (e.g., 1-10, where 1 is for low urgency requests, 5 is the default for normal urgency requests, 7 is for very urgent requests, and 10 is for extremely urgent requests). In various embodiments, one or more of the clients 902, 922, 923, ... 92n may make an option to pay a fee to a service provider (e.g., an entity providing the QoS manager 901 or another entity) for increased priority and urgency levels on a per-client or per-request basis. Similarly, a client may make an option to selectively reduce priority and urgency levels for certain non-urgent and low priority requests in exchange for a discount or other incentive.

[0113] Advantageously, the system 900 employs a QoS manager 901 to enable the certificate management service 980 to provide QoS levels to clients 902, 922, 923, ... 92n so that clients such as client 92n do not experience excessive delays associated with waiting for earlier, large requests to be fulfilled. For example, the QoS manager 901 can be used by the certificate management service 980 to distribute certificate requests from clients 902, 922, 923, ... 92n across n corresponding intermediate client queues 903, 907, 909, ... 91n, where each of these n client queues corresponds to a particular client having a requested certificate. Fig. 9In the example of , client queue 903 corresponds to client 902 , client queue 907 corresponds to client 922 , client queue 909 corresponds to client 923 , and client queue 91 n corresponds to client 92 n .

[0114] like Fig. 9 As shown in , the QoS manager 901 may also divide the certificate requests of the clients in the client queue into smaller groups of one or more entries, each of which has a group size corresponding to a subset of the number of computerized devices that need certificates. Fig. 9 In the non-limiting example of , the group size is 50 (e.g., certificates for 50 vehicles). However, it should be understood that in alternative implementations, the group size can be any number, and the certificates can be used for any computerized device (i.e., not limited to vehicles). For example, the group size can vary by client, and in some implementations, the size is 1 computerized device per queue entry in the client queues 903, 907, 909, ... 91n. In alternative or additional implementations, the group size is a user-tunable parameter with a default value of 1. In alternative implementations, the system 900 may use a pooled queue approach instead Fig. 9 For example, the client queues do not need to utilize the dedicated client queues 903, 907, 909, ... 91n shown in FIG. Fig. 9 The number of client queues shown in has a one-to-one mapping with each of the n clients and is dedicated to each client. That is, instead of a system 900 with a dedicated (predetermined) client queue for each customer, a pooled queue implementation can utilize a queue pool and allocate a given queue from the queue pool only when the client is active. That is, using a pooled queue implementation, a queue can be allocated to a client only when the client has submitted a certificate request (i.e., when the client is active). One benefit of a dedicated queue implementation is that the system 900 does not require any logic or execution of instructions to allocate queues when the client changes the client state from inactive to active or from active to inactive. One benefit of a pooled queue implementation is that when searching for active jobs to be placed on a QoS queue 906, the work that the QoS arbitrator 904 must perform can be optimized. That is, using a pooled queue implementation, the QoS arbitrator 904 will only need to scan the queues of active clients with currently pending certificate requests (as opposed to potentially having to scan empty dedicated client queues for inactive clients).

[0115] The QoS manager 901 acts as an intermediary between the clients 902, 922, 923, ... 92n and the certificate management service 980. The QoS manager 901 can accept certificates from any number of clients (e.g., Fig. 9) and holds them in the intermediate client queues 903, 907, 909, ... 91n. Fig. 9 As shown in , the QoS manager 901 splits the large request into smaller requests and feeds those smaller requests into separate, corresponding ones of the client queues 903, 907, 909, ... 91n. This allows the smaller requests to be completed much earlier and can support any number of clients. In addition, by using the QoS manager 901, if additional small requests come in after the large request has been received, those small requests will be allowed to be completed much faster than a CMS or certificate management service that lacks the QoS manager 901.

[0116] In the system 900, the request for the certificate is received by the registration authority API 905 (e.g., a public API) of the QoS manager 901. The QoS manager 901 accepts the request for the certificate on behalf of the certificate management service 980. In various implementations, the QoS manager 901 is operable to distribute the certificate request across n intermediate client queues from n clients 902, 922, 923, ... 92n, wherein each of the n client queues corresponds to a special client requesting a certificate. The QoS manager 901 may also be configured to divide the request of a particular client in the client queue of the client into smaller packets of one or more entries, wherein each of the one or more entries has a packet size corresponding to a subset of the number of computerized devices for which the client needs a certificate (see, for example, parts 1, 2, 3, 4, ... x in the client queue 903). That is, the QoS manager 901 may split the large certificate request from a given client into smaller pieces, and place those smaller pieces in the client queue of the client.

[0117] In various implementations, the QoS manager 901 includes a QoS arbitrator 904. The QoS arbitrator 904 selects entries from the client queues to be placed in the QoS queue 906. In some implementations, the QoS arbitrator 904 is operable to select a sequence of entries from the client queues 903, 907, 909, ... 91n to be placed on the QoS queue 906 using a round-robin technique. That is, the QoS arbitrator 904 may sequentially select entries from each of the client queues 903, 907, 909, ... 91n, moving in order from the first client queue 903, and proceeding in sequence through each of the other client queues 907, 909, ... 91n. The QoS arbitrator 904 throttles the entries by placing only enough entries on the QoS queue 906 as needed. For example, the QoS queue 906 may be limited to the number of entries allowed. To improve the efficiency of system 900, the number of allowed entries can be set to a value large enough to ensure that the certificate management service 980 is always busy, but small enough to minimize waiting time. That is, the queue depth of QoS queue 906 is limited, and this limit is known by QoS arbitrator 904.

[0118] The QoS arbiter 904 may try to minimize the size of the QoS queue 906 in order to allow new requests to enter and be placed on the QoS queue 906. In some implementations, even though the QoS arbiter 904 may place items in the QoS queue 906 in a certain order, a later arriving but high priority request may be inserted at the head of the queue rather than at the tail of the QoS queue 906. In other words, new entries in the QoS queue 906 are typically placed or set at the tail of the QoS queue 906. Fig. 9 The head of the QoS queue 906 is the entry for client 1 at the bottom of the QoS queue 906 (e.g., client 1 (x50)). The entry at the head of the QoS queue 906 will be the next entry to the certificate management service 980 via the internal API 925. However, in some instances, the QoS arbitrator 904 may make a choice to insert a new entry at the head of the QoS queue 906 or anywhere between the head and the tail. For example, the placement of an entry in the QoS queue 906 by the QoS arbitrator 904 may be based on the client priority level indicated in the certificate request and / or the certificate request urgency.

[0119] In some implementations, the QoS arbitrator 904 may also be operable to dynamically reorder the sequence of entries placed on the QoS queue 906 based at least in part on additional certificate requests received from additional clients (e.g., requests received from new clients subsequent to the request from client 92n). Additionally, for example, the sequence of entries in the QoS queue 906 may be determined by the QoS arbitrator 904 based on a dynamic priority assigned to each of the client queues 903, 907, 909, ... 91n, wherein the respective dynamic priority assigned to each of the client queues 903, 907, 909, ... 91n is assigned by the QoS arbitrator based at least in part on the number of entries in each of the client queues 903, 907, 909, ... 91n.

[0120] In various implementations, the QoS arbitrator 904 is operable to select a sequence of entries to be placed on the QoS queue 906 from among n client queues 903, 907, 909, ... 91n based at least in part on the number of entries in the QoS queue 906, the latency level of the certificate management service 980, and corresponding timestamps indicating when the certificate request was transmitted.

[0121] exist Fig. 9In the example of , the QoS arbitrator 904 has selected a sequence of entries to be placed on the QoS queue 906 from a plurality of clients (e.g., client 1, client 2 ... client n) using a round-robin technique. In an additional or alternative implementation, the QoS arbitrator 904 may also be operable to select a sequence of entries to be placed on the QoS queue 906 from the n client queues 903, 907, 909, ... 91n based on a request urgency level or a client priority level that may be indicated in a certificate request. For example, instead of using a round-robin technique to select a sequence of entries between all clients 902, 922, 923, ... 92n from the client queues 903, 907, 909, ... 91n, the QoS arbitrator 904 may select a sequence of entries based on a rule that changes the balance between the clients. For example, the sequence of entries may be determined based on respective client priority levels indicating higher priority, higher paying clients (e.g., certain vehicle manufacturers) and lower priority, lower paying clients (e.g., certain universities that may only want to pay for free time processing). In this example, the QoS arbitrator 904 will place entries from higher priority clients before entries from lower priority clients on the QoS queue 906. Also, for example, the sequence of entries may be determined based on respective request urgency levels, wherein the QoS arbitrator 904 places entries corresponding to more urgent requests before entries corresponding to less urgent requests on the QoS queue 906. In additional implementations, the QoS arbitrator 904 may select the sequence of entries for the QoS queue 906 based on a rate limiting rule indicating that the certificate management service 980 should not process more than a certain number of certificates per client per unit of time (e.g., limiting a given client to no more than x number of certificates per hour or day).

[0122] In system 900, a given client of clients 902, 922, 923, ... 92n may have multiple concurrent certificate requests. In some implementations, QoS manager 901 may not distinguish between multiple requests from the same client. In alternative or additional implementations, QoS manager 901 may also divide concurrent requests from a single client into slices based on rules. According to an example implementation, QoS manager 901 may divide the client's requests based on the corresponding request urgency level provided by the client to system 900 and the rule for executing the urgency level among the requests from the client. In this example implementation, QoS manager 901 may direct QoS arbitrator 904 to process the parts of multiple requests from the client in what order based on the urgency level provided by a given client for each of its certificate requests. In another implementation, the client may allow QoS manager 901 to use a round-robin technique to select an entry sequence across all of the client's certificate requests.

[0123] In additional or alternative implementations, the QoS arbitrator 904 may also be operable to select a sequence of entries from the n client queues 903, 907, 909, ... 91n to be placed on the QoS queue 906 based on a request urgency level or a client priority level that may be indicated in a certificate request. Fig. 9 As shown in , the QoS arbitrator 904 has selected a sequence of entries to be placed on the QoS queue 906 from a plurality of clients (eg, client 1, client 2, ... client n).

[0124] In some implementations, the certificate management service 980 extracts entries from the QoS queue 906 via a call to the internal API 925. However, as described above, a new request (from a new client, not one of 902, 922, 923, 92n) or a new request from one of the clients 902, 922, 923, 92n with a higher priority than other entries in the QoS queue 906, then the QoS arbitrator 904 may extract the new higher priority entry in the QoS queue 906 as the next entry to be processed by the CMS 980. In an implementation, the QoS arbitrator 904 may temporarily freeze or pause the QoS queue 906 and not allow the certificate management service 980 to extract any more entries from the QoS queue 906 until the new higher priority entry is placed on the QoS queue 906. In an alternative implementation, the QoS arbitrator 904 may remove the lower priority entry from the QoS queue 906 to replace it with the higher priority entry, and the QoS arbitrator 904 may place the removed entry back on the corresponding client queue.

[0125] According to some implementations, the QoS manager 901 is operable to retrieve entries from the QoS queue 906 in a sequence selected by the QoS arbitrator 904, and transmit the retrieved entries to the certificate management service 980 via the internal API 925. The QoS manager 901 then forwards the entries from the QoS queue to the certificate management service 980 via a call to the internal API 925 of the registry of the certificate management service 980. The certificate management service 980 then completes the tasks forwarded to it by the QoS manager 901 within the time frame, and then returns the results (e.g., the generated certificates) to the QoS manager 901. The QoS manager 901 then forwards the results as a response to the clients 902, 922, 923, ... 92n via the registry API 905 and the network 935.

[0126] In system 900, there are multiple clients 902, 922, 923, ... 92n (e.g., a group of n clients) that can each request work from the same certificate management service 980 via QoS manager 901. That is, multiple concurrent clients 902, 922, 923, ... 92n can interact concurrently with QoS manager 901 acting as an intermediary between n clients and certificate management service 980. Fig. 9 In the example shown in , clients 902, 922 (e.g., client 1 and client 2) may transmit a large request for a large number of computerized devices (e.g., >100,000 vehicles) via network 935, and after client 1's and client 2's certificate requests, another client 923 may transmit another large request for a certificate. Then, the last client 92n in the group of n clients may transmit a small request for a relatively small number of computerized devices (e.g., <50 vehicles). As described above, for a system 900 including a QoS manager 901, these requests will be placed on client queues 903, 907, 909, ... 91n and in increments (e.g., Fig. 9 92n) to provide QoS levels to clients 902, 922, 923, ... 92n. That is, instead of having to sequentially handle requests from clients 902, 922, 923, ... 92n on a first-come, first-served basis without regard to the varying sizes or priorities of the requests, the QoS manager 901 advantageously prevents the system 900 from having to process the requests in a sequential order. For example, rather than requiring the last client (e.g., client 92n) to wait for the jobs of the preceding clients to complete before providing any responses, the QoS manager 901 enables the certificate management service 980 to implement a later-arriving but smaller request from client 92n to be completed without a significant delay (i.e., hours or days - the length of time it takes for a large request from a preceding client 902, 922, 923 to be implemented).

[0127] Fig.10 1003, 1007, 1009, ... 101n and CMS 1080 using a QoS manager according to an implementation of the present invention. Figure 7 Compared to Fig.10 Differences within.

[0128] exist Fig.10 In the example depicted in , CMS 1080 may be a V2X CMS or a C2X CMS. In some implementations, CMS 1080 may host a certificate management service, such as the one described above with reference to Fig. 9In some implementations, a QoS arbitrator (e.g., as described above with reference to Fig. 9 The QoS manager 901 and QoS arbitrator 904 described above may select entries to be submitted to the CMS 1080 from among the n client queues 1003 , 1007 , 1009 , . . . 101 n .

[0129] like Fig.10 As shown in FIG, CMS 1080 receives a large request 1010 for certificates from client queue 1003 for a first client (e.g., Client 1), and after large request 1010, receives another large request 1013 for a second client (e.g., Client 2) from client queue 1007, and after that, receives yet another large request 1014 from client queue 1009. After large requests 1010, 1013, and 1014 have been received by CMS 1080, a small request 1012 for certificates for a relatively small number of computerized devices (e.g., 50 vehicles) is received from client queue 101n. In some implementations, each certificate request 1010, 1013, 1014, 1012 includes data fields indicating: the number of computerized devices requiring a certificate (e.g., 110,000 for large request 1010 and 50 for small request 1112); a timestamp indicating when this particular certificate request was transmitted (e.g., a date and time indicating the hour, minute, and second of the transmission); and the client requesting the certificate (e.g., corresponding identifiers of clients 1002, 1022, and 1023 for large requests 1010, 1011, and 1013 and client 102n for small request 1012).

[0130] Fig.10 1080 with a QoS manager is shown to handle multiple requests 1010, 1012, 1013, 1014. By using the QoS manager and its QoS arbitrator, a later arriving smaller request 1012 can be implemented without having to wait for the large request 1010, 1013, 1014 to be implemented first. That is, Fig.10It is shown how a smaller request 1012 from a client queue 101n does not need to wait for all of the preceding requests 1010, 1013, 1014 to complete. In other words, the lengthy, sequential computation time associated with completing all of the large requests 1010, 1013, 1014 does not need to elapse before the CMS 1080 implements the small request 1012. This is accomplished by the QoS manager dividing the requests 1010, 1012, 1013, 1014 into portions that are placed into the client queues 1003, 1007, 1009, ... 101n. These portions are sub-groups (i.e., smaller groups) of one or more entries, each of which has a group size corresponding to a subset of the number of computerized devices that require certificates. In Fig.10 In a non-limiting example of , the packet size is 50 and the certificate is requested for a vehicle. In an alternative or additional embodiment, the packet size is a tunable value with a default value of 1, and the certificate can be used for various computerized devices that require security credentials.

[0131] like Fig.10 As shown in , CMS 1080 requires computing time 1015 to perform the calculations required to generate the first part of the certificate bundle required to fulfill the large request 1010 from client 1002 (e.g., part 1 of the request from client 1). Fig.10 In the example of , only portion 1 of the certificate bundle requested by client 1002 (e.g., client 1) is generated before moving to the first portion of the large request 1013 from client 1022 (e.g., portion 1 of the request from client 2), which requires computation time 1017. Next, portion 1 of the large request 1014 from client 1023 is processed, which requires computation time 1018. Then, the small request 1012 from client 102n is processed in computation time 1016. By using a QoS manager to divide the large request, client 102n only needs to wait for the amount of time that portions 1 of the large requests 1010, 1013, 1014 from clients 1002, 1022, 1023 are completed. This is true despite the fact that small request 1012 is submitted after large requests 1010, 1011, and 1013. In the case where a QoS manager is not used (e.g., see the description above), Fig. 9 In the case of a QoS manager 901), the client 102n will experience a lengthy wait time before a response to the small request 1012 is provided because the client 102n will have to wait for all parts of the large request 1010, 1013, 1014 to be completed before the small request 1012 will be implemented.

[0132] like Fig.10As shown in , before receiving a response to the small request 1012, the client 102n only needs to wait for all of the part 1 computation times 1015, 1017, 1018, and 1016. This is because the waiting time for the client 102n does not include the entire computation time required to complete all parts of the large request 1010, 1013, 1014. Instead, in addition to the computation time 1016 for completing the small request 1012, the client 102n must also wait for the relatively small computation time 1015, 1017, and 1018 for completing the first part of the large request 1010, 1013, 1014. That is, even if the client 102n submits the small request 1012 after the large requests 1010, 1011, and 1013, the waiting time will be much shorter than if the QoS manager is not used. This is because without the QoS manager to split the large request 1010, 1013, 1014 into parts, the waiting time for the client 102n will be the sum of the entire combined computation time required to implement the large request 1010, 1013, 1014 from the client 1002, 1022, 1023 and the computation time 1016 of the small request 1012 to be implemented. Fig. 9 In the case of the QoS manager 901 discussed, there is no mechanism for fulfilling a small request 1012 from a client 102n without first having to wait for fulfillment of earlier submitted large requests 1010, 1013, and 1014. That is, the QoS manager enables the CMS 1080 to provide QoS levels in a multi-client environment.

[0133] Next, after the small request 1012 has been fulfilled, CMS1080 processes portion 2 of the large request 1010 from client 1002, which requires computation time 1015'. Next, portion 2 of the large request 1013 from client 1022 (e.g., portion 2 of the request from client 2) is processed, which requires computation time 1017'. Then, portion 2 of the large request 1014 from client 1023 is processed, which requires computation time 1018'. At this point, since the small request 1012 from client 102n has been fulfilled, CMS1080 processes portion 3 of the large request 1010 from client 1002, which requires computation time 1015". The remainder of the large requests 1010, 1013, and 1014 will be processed in this manner until these requests have been fulfilled.

[0134] In some implementations, a QoS arbitrator (e.g., Fig. 9The QoS arbitrator 904 of the CMS 1080 can dynamically reorder the sequence of entries placed on the QoS queue used by the CMS 1080. In this way, the sequence of the request portion processed by the CMS 1080 can be dynamically changed. For example, the entry sequence can be changed in response to the QoS manager receiving an additional certificate request from an additional client (i.e., a request after the small request 1012 from the new client). In addition, for example, the entry sequence can be based on the client priority level indicated in the certificate request and / or the certificate request urgency. Moreover, for example, the entry sequence can be changed based on the dynamic priority assigned to each of the client queues 1003, 1007, 1009, ... 101n, wherein the corresponding dynamic priority assigned to each of the client queues 1003, 1007, 1009, ... 101n is assigned by the QoS arbitrator at least in part based on the number of entries in each of the client queues 1003, 1007, 1009, ... 101n.

[0135] Fig.11 1-10 , such as the computing system 1100. Figure 1A and 1B The distributor appliance 108, the registration authority 120, the linking authorities 150, 160, the pseudonym certificate authority 140 and the registration certificate authority 130, Figure 2 , Figure 4 , Figure 6 and Figure 8 Certificate management service 280, 480, 680, 880 components, Fig. 9 QoS manager 901, and Figure 3 , Figure 5 , Figure 7 and Fig.10 Certificate management system (CMS) 380, 580, 780, 1080, etc. In some implementations, a series of computing systems similar to computing system 1100 can each be customized with specialized hardware and / or programmed as a specialized server to implement one of the components of Figures 1-10, which can communicate with each other via network 1135.

[0136] exist Fig.11In the example shown in , computing system 1100 includes multiple components, such as CPU 1105, memory 1110, (one or more) input / output (I / O) devices 1125, hardware security module (HSM) 1140, and non-volatile storage device 1120. System 1100 can be implemented in various ways. For example, an implementation as an integrated platform (such as a server, workstation, personal computer, laptop computer, etc.) can include CPU 1105, memory 1110, non-volatile storage device 1120 and I / O device 1125. In such a configuration, components 1105, 1110, 1120 and 1125 can be connected and communicated through a local data bus, and can access data repository 1130 (e.g., implemented as a separate data source or database system) via an external I / O connection. The I / O component(s) 1125 may be connected to external devices through a direct communication link (e.g., a hardwired or local wifi connection), through a network such as a local area network (LAN) or a wide area network (WAN, such as a cellular telephone network or the Internet), and / or through other suitable connections. The system 1100 may be stand-alone, or it may be a subsystem of a larger system.

[0137] CPU 1105 may be one or more known processors or processing devices, such as those from Intel Corporation of Santa Clara, California. TM Core manufactured by the company TM AMD , Inc. of Sunnyvale, California TM Athlon manufactured by the company TM The memory 1110 may be one or more fast storage devices configured to store instructions and information executed or used by the CPU 1105 to perform certain functions, methods and processes related to implementations of the present invention. The storage device 1120 may be a volatile or non-volatile, magnetic, semiconductor, tape, optical or other type of storage device or computer-readable medium, including devices such as CDs and DVDs, as well as solid-state devices intended for long-term storage.

[0138] In the illustrated implementation, memory 1110 contains one or more programs or applications 1115 loaded from storage device 1120 or from a remote system (not shown) that, when executed by CPU 1105, perform various operations, procedures, processes, or methods consistent with the present invention. Alternatively, CPU 1105 may execute one or more programs located remotely from system 1100. For example, system 1100 may access one or more remote programs via network 1135 that, when executed, perform functions and processes related to implementations of the present invention.

[0139] In some implementations, memory 1110 may include program(s) 1115 for performing the specialized functions and operations described herein for the CMS host with the registration authority 120, the distributor appliance 108, the certificate management service 280, 480, 680, 880, the CMS 380, 580, 780, 1080, the QoS manager 801, 901, and / or the QoS arbitrator 904. In some implementations, memory 1110 may also include other programs or applications that implement other methods and processes that provide auxiliary functionality to the present invention.

[0140] The memory 1110 may also be configured with other programs (not shown) not related to the present invention and / or an operating system (not shown) that performs several functions known in the art when executed by the CPU 1105. As an example, the operating system may be Microsoft Windows TM , Unix TM , Linux TM 、Apple Computers TM Operating system or other operating systems. The choice of operating system and even the use of an operating system is not critical to the present invention.

[0141] The HSM 1140 may be a device with its own processor that securely generates and stores digital security assets and / or securely performs various cryptographic and sensitive calculations. The HSM 1140 protects digital security assets such as cryptographic keys and other sensitive data from possible access by attackers. In some implementations, the HSM may be a plug-in card or board that is directly attached to the computing system 1100.

[0142] (One or more) I / O devices 1125 may include one or more input / output devices that allow data to be received and / or transmitted by the system 1100. For example, the I / O devices 1125 may include one or more input devices that enable data to be input from a user, such as a keyboard, a touch screen, a mouse, etc. In addition, the I / O devices 1125 may include one or more output devices that enable data to be output or presented to a user, such as a display screen, a CRT monitor, an LCD monitor, a plasma display, a printer, a speaker device, etc. The I / O devices 1125 may also include one or more digital and / or analog communication input / output devices that allow the computing system 1100 to communicate with other machines and devices, such as digitally. Other configurations and / or quantities of input and / or output devices may be incorporated into the I / O devices 1125.

[0143] In the illustrated implementation, the system 1100 is connected to a network 1135 (such as the Internet, a private network, a virtual private network, a cellular network, or other network or a combination of these), which in turn can be connected to various systems and computing machines, such as servers, personal computers, laptops, client devices, etc. In general, the system 1100 can input data from external machines and devices and output data to external machines and devices via the network 1135.

[0144] exist Fig.11 In the exemplary implementation shown in , the repository 1130 is an independent data source external to the system 1100, such as a database. In other implementations, the repository 1130 can be hosted by the system 1100. In various implementations, the repository 1130 can manage and store data used to implement systems and methods consistent with the present invention. For example, the repository 1130 can manage and store data structures containing status and log information for each computerized device having a certificate supplied by the dispenser appliance 108.

[0145] Repository 1130 may include one or more databases that store information and are accessed and / or managed by system 1100. As an example, repository 1130 may be an Oracle TM Database, Sybase TM Databases or other related databases. However, systems and methods consistent with the present invention are not limited to separate data structures or databases, or even to the use of databases or data structures.

[0146] Those of ordinary skill in the art will recognize that Fig.11 The components and implementation details of the systems in are examples presented for simplicity and clarity of explanation. Other components and implementation details may be used.

[0147] Although the foregoing examples use specific examples of computerized devices such as OBUs, ECUs, and RSUs, for clarity of explanation, the present invention is not limited to those specific examples. Various implementations consistent with the present invention may be used with a variety of computerized devices such as medical devices (e.g., dialysis machines, infusion pumps, etc.); robots; drones; autonomous vehicles; and wireless communication modules (e.g., embedded universal integrated circuit cards (eUICCs)), etc.).

[0148] The various operations of the applications described herein may be performed at least in part by one or more VMs. In additional or alternative implementations, the operations of the applications described herein may be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more application operations, functions, and roles described herein. As used herein, the term "processor-implemented module" refers to a hardware module implemented using one or more processors.

[0149] Similarly, the methods described herein may be implemented at least in part by a processor, wherein one or more processors in particular are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors or processor-implemented modules. In addition, one or more processors may also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS). For example, at least some of the operations may be performed by a group of computers (as an example of a machine including a processor), wherein the operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).

[0150] The execution of certain operations may be distributed among processors, not only residing within a single machine, but also deployed across multiple machines. In some example embodiments, the processor or processor-implemented modules may be located in a single regional location (e.g., within an office environment, a manufacturing environment, or a server farm). In other example embodiments, the processor or processor-implemented modules may be distributed across multiple regional locations.

[0151] Other implementations of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.It is intended that the specification and examples be considered exemplary only, with the true scope of the invention being indicated by the following claims.

Claims

1. A system for providing a quality of service (QoS) level to a client requesting a certificate from a certificate management service, wherein the system comprises: An application programming interface (API) operable to receive certificate requests from a plurality of clients, each certificate request comprising information indicating: the number of computerized devices requiring certification; a timestamp indicating when the certificate request was transmitted; as well as specifying a client identifier of a client requesting the certificate; A QoS manager operable to: distributing the certificate requests from the plurality of clients across a plurality of client queues, each of the plurality of client queues corresponding to a particular client requesting a certificate; dividing the certificate requests of the clients in the client queue into subgroups of one or more entries, each of the one or more entries having a group size corresponding to the subset of the number of computerized devices requiring certificates; as well as The retrieved entries are communicated from the plurality of client queues to the credential management service.

2. A system according to claim 1, wherein the system includes a QoS arbitrator operable to select a sequence of entries from the multiple client queues to be placed on the QoS queue based at least in part on the number of entries in the QoS queue, a latency level of the certificate management service, or a timestamp indicating when the certificate request was transmitted.

3. The system of claim 2, wherein the QoS manager is operable to transmit the retrieved entries from the plurality of client queues to the certificate management service by obtaining the retrieved entries from the QoS queue in the sequence selected by the QoS arbitrator.

4. The system of claim 3, wherein: The OBU is operable to be installed in one or more of a vehicle, a ship, an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless communication module, a wired communication module, and an Internet of Things IoT device; The ECU is operable to be installed in one or more of a vehicle, a ship, an aircraft, a spacecraft, a medical device, a robot, a drone, a wireless communication module, a wired communication module, and an IoT device; and The RSU is operable to be installed in one or more of a traffic control device, a wireless communication module, a digital billboard, and an electronic sign.

5. The system of claim 3 , wherein each certificate request further comprises additional information indicating a client priority level of a client submitting the request, and wherein the QoS arbitrator is further operable to select the sequence of entries to be placed on the QoS queue from the plurality of client queues based at least in part on the respective client priority levels indicated in the certificate request, Wherein the client priority level for the client is based on a service level associated with the client, and wherein the service level corresponds to one of a plurality of levels ranging from a lowest service level to a highest service level.

6. The system of claim 3, wherein each certificate request further comprises additional information indicating a client priority level of a client submitting the request, and wherein the QoS arbitrator is further operable to select the sequence of entries to be placed on the QoS queue from the plurality of client queues based at least in part on the respective client priority levels indicated in the certificate request, The QoS arbitrator is further operable to dynamically reorder the sequence of entries placed on the QoS queue based at least in part on respective client priority levels indicated in additional credential requests received from additional clients.

7. The system of claim 3, wherein each credential request further indicates a request urgency level associated with the request, and wherein the QoS arbitrator is operable to select the sequence of entries from the plurality of client queues to be placed on the QoS queue based at least in part on the respective request urgency levels indicated in the credential requests, Wherein a request urgency level for a certificate request is specified by a client submitting the certificate request, and wherein the request urgency level corresponds to one of a plurality of levels ranging from a lowest urgency option to a highest urgency option.

8. The system of claim 2, wherein the QoS arbitrator is operable to select the sequence of entries from the plurality of client queues to be placed on the QoS queue using a round-robin technique.

9. The system of claim 1, wherein the computerized device requiring a certificate corresponds to one or more of an on-board unit (OBU), an electronic control unit (ECU), and a roadside unit (RSU).

10. The system of claim 1, wherein the plurality of clients includes at least one distributor appliance or server operable to act as a proxy between the certificate management service and at least one computerized device requiring a certificate.

11. The system of claim 1 , wherein the certificate requests from the plurality of clients include requests for enrollment certificates, and wherein the API is further operable to: A registration certificate generated by a registration certificate authority of the certificate management service is transmitted to the plurality of clients.

12. The system of claim 11, wherein: The certificate request also includes a request for a pseudonym certificate; The API is further operable to transmit, on behalf of the certificate management service, a pseudonymous certificate generated by a pseudonymous certificate authority of the certificate management service to the plurality of clients via the communication network; The plurality of clients includes at least one distributor appliance operable to act as a proxy between the credential management service and at least one computerized device requiring a credential; as well as The at least one computerized device is operable to retrieve a certificate from the dispenser appliance.

13. A computer-implemented method for providing a Quality of Service (QoS) level to a client requesting a certificate from a certificate management service, wherein the method comprises: receiving certificate requests from a plurality of clients via an application programming interface, API, each certificate request including information indicating a number of computerized devices requiring a certificate, a timestamp indicating when the certificate request was transmitted, and a client identifier specifying a client requesting the certificate; distributing, by a QoS manager, the certificate requests from the plurality of clients across a plurality of client queues, each of the plurality of client queues corresponding to a particular client requesting a certificate; as well as dividing, by the QoS manager, the client's request into sub-groups of one or more entries, each of the one or more entries having a group size corresponding to the subset of the number of computerized devices requiring a certificate; as well as The retrieved entries are communicated from the plurality of client queues to the credential management service.

14. The computer-implemented method of claim 13, further comprising selecting, by a QoS arbitrator, the retrieved entry from the plurality of client queues based at least in part on a latency level of the credential management service or a timestamp indicating when the credential request was transmitted.

15. The computer-implemented method of claim 14, wherein selecting the retrieved entry from the plurality of client queues comprises using a round-robin technique.

16. A computer-implemented method according to claim 14, wherein the selection of the retrieved entries from the multiple client queues is based on a dynamic priority assigned to each of the client queues, and wherein the corresponding dynamic priority assigned to each of the client queues is assigned by the QoS arbitrator based at least in part on the number of entries in each of the client queues.

17. The computer-implemented method of claim 14, further comprising communicating, using the QoS manager, the retrieved entries from the plurality of client queues to the certificate management service by obtaining the retrieved entries from the QoS queue in the sequence selected by the QoS arbitrator.

18. A computer-implemented method according to claim 17, wherein each certificate request also includes additional information indicating a client priority level of the client submitting the request, and wherein the method further includes using the QoS arbitrator to select the sequence of entries to be placed in the QoS queue from the multiple client queues based at least in part on the client priority level indicated in each certificate request.

19. The computer-implemented method of claim 18, wherein the client priority level for the client is based on a service level associated with the client, and wherein the service level corresponds to one of a plurality of levels ranging from a lowest service level to a highest service level.

20. The computer-implemented method of claim 18, further comprising using the QoS arbitrator to dynamically reorder the sequence of entries placed in the QoS queue based at least in part on respective client priority levels indicated in additional credential requests received from additional clients.

21. The computer-implemented method of claim 17, wherein each credential request further includes additional information indicating a request urgency level associated with the request, and wherein the method further comprises the QoS arbitrator selecting the sequence of entries to be placed in the QoS queue from the plurality of client queues based at least in part on the request urgency level indicated in each credential request, Wherein a request urgency level for a certificate request is specified by a client submitting the certificate request, and wherein the request urgency level corresponds to one of a plurality of levels ranging from a lowest urgency option to a highest urgency option.

22. The computer-implemented method of claim 13, wherein the computerized device requiring a certificate corresponds to one or more of an on-board unit (OBU), an electronic control unit (ECU), and a roadside unit (RSU).

23. The computer-implemented method of claim 13, wherein the certificate requests from the plurality of clients comprise requests for enrollment certificates, and wherein the method further comprises: A registration certificate generated by a registration certificate authority of the certificate management service is transmitted to the plurality of clients.

24. The computer-implemented method of claim 23, further comprising transmitting, on behalf of the certificate management service, a pseudonymous certificate generated by a pseudonymous certificate authority of the certificate management service to the plurality of clients via a communications network, wherein the certificate request further comprises a request for a pseudonymous certificate, wherein the plurality of clients include at least one distributor appliance, the at least one distributor appliance being operable to act as a proxy between the certificate management service and at least one computerized device requiring a certificate, and wherein the at least one computerized device being operable to retrieve the certificate from the at least one distributor appliance.