IP Library Granted Patent US 12,231,349
Granted Patent B2
US 12,231,349 · App. 18/338,683 · Granted Feb 18, 2025

Managing cloud acquisitions using distributed ledgers

Inventors: Cathal O'Connor (Waterford, IL); Brian Gallagher (Waterford, IL)
Assignee: Red Hat, Inc.
H04L47/762H04L9/3236H04L9/3247H04L47/781H04L47/822H04L47/828
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,231,349
App. No.
18/338,683
Granted
Feb 18, 2025
Kind
B2
Abstract

Systems and methods of the disclosure include: broadcasting, by a cloud resource provisioning component, to a cryptographically-protected distributed ledger, a first transaction comprising a cloud resource request for provisioning a cloud resource; transmitting, to one or more cloud providers, the cloud resource request; receiving, from a first cloud provider of the one or more cloud providers, a first cloud resource offer responsive to the cloud resource request; and broadcasting, to the cryptographically-protected distributed ledger, a second transaction comprising the first cloud resource offer.

Claims (71)

1. A method comprising:

transmitting, to one or more cloud providers, a cloud resource request to provision a cloud resource for a client;

broadcasting, to a distributed ledger, a first transaction comprising the cloud resource request responsive to transmitting the cloud resource request;

receiving, from a first cloud provider of the one or more cloud providers, first cloud resource parameters responsive to broadcasting the first transaction;

broadcasting, to the distributed ledger, a second transaction comprising the first cloud resource parameters;

receiving, from a blockchain client of the distributed ledger, a notification of smart contract-based validation of the first cloud resource parameters;

responsive to receiving the notification, transmitting, by a processing device, a message to the first cloud provider that causes the first cloud provider to provision a first cloud resource to the client according to the first cloud resource parameters; and

broadcasting, to the distributed ledger, a third transaction reflecting provisioning of the first cloud resource to the client.

2. The method of claim 1 , wherein the first cloud resource parameters comprise at least one of first parameters characterizing compute nodes, second parameters characterizing storage, or third parameters characterizing networking.

3. The method of claim 1 , further comprising:

storing the cloud resource request on the distributed ledger, wherein storing the cloud resource request comprises:

causing the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation.

4. The method of claim 1 , further comprising:

storing the cloud resource request on the distributed ledger, wherein storing the cloud resource request comprises:

causing the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by comparing a first cloud resource parameter specified by the cloud resource request to a second cloud resource parameter specified by the first cloud resource parameters.

5. The method of claim 1 , further comprising:

storing the cloud resource request on the distributed ledger, wherein storing the cloud resource request comprises:

causing the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation, wherein the smart contract code is to select, among two or more qualified cloud resource parameters, a cloud resource parameter that specifies a minimal cloud resource parameter.

6. The method of claim 1 , further comprising:

storing the cloud resource request on the distributed ledger, wherein storing the cloud resource request comprises:

causing the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by accepting an electronic signature of an originator of the cloud resource request.

7. The method of claim 1 , further comprising:

storing the cloud resource request on the distributed ledger, wherein storing the cloud resource request comprises:

causing the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by rejecting second cloud resource parameters that were received upon expiration of a predefined timeout triggered by the cloud resource request.

8. A system comprising:

a memory; and

a processing device, operatively coupled to the memory, to:

transmit, to one or more cloud providers, a cloud resource request to provision a cloud resource for a client;

broadcast, to a distributed ledger, a first transaction comprising the cloud resource request responsive to the transmission of the cloud resource request;

receive, from a first cloud provider of the one or more cloud providers, first cloud resource parameters responsive to the broadcast of the first transaction;

broadcast, to the distributed ledger, a second transaction comprising the first cloud resource parameters;

receive, from a blockchain client of the distributed ledger, a notification of smart contract-based validation of the first cloud resource parameters;

responsive to the reception of the notification, transmit a message to the first cloud provider that causes the first cloud provider to provision a first cloud resource to the client according to the first cloud resource parameters; and

broadcast, to the distributed ledger, a third transaction reflecting provisioning of the first cloud resource to the client.

9. The system of claim 8 , wherein the first cloud resource parameters comprise at least one of first parameters characterizing compute nodes, second parameters characterizing storage, or third parameters characterizing networking.

10. The system of claim 8 , wherein the processing device is further to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the processing device is to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation.

11. The system of claim 8 , wherein the processing device is further to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the processing device is to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by comparing a first cloud resource parameter specified by the cloud resource request to a second cloud resource parameter specified by the first cloud resource parameters.

12. The system of claim 8 , wherein the processing device is further to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the processing device is to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation, wherein the smart contract code is to select, among two or more qualified cloud resource parameters, a cloud resource parameter that specifies a minimal cloud resource parameter.

13. The system of claim 8 , wherein the processing device is further to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the processing device is to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by accepting an electronic signature of an originator of the cloud resource request.

14. The system of claim 8 , wherein the processing device is further to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the processing device is to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by rejecting second cloud resource parameters that were received upon expiration of a predefined timeout triggered by the cloud resource request.

15. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processing device, cause the processing device to:

transmit, to one or more cloud providers, a cloud resource request to provision a cloud resource for a client;

broadcast, to a distributed ledger, a first transaction comprising the cloud resource request responsive to the transmission of the cloud resource request;

receive, from a first cloud provider of the one or more cloud providers, first cloud resource parameters responsive to the broadcast of the first transaction;

broadcast, to the distributed ledger, a second transaction comprising the first cloud resource parameters;

receive, from a blockchain client of the distributed ledger, a notification of smart contract-based validation of the first cloud resource parameters;

responsive to the reception of the notification, transmit, by the processing device, a message to the first cloud provider that causes the first cloud provider to provision a first cloud resource to the client according to the first cloud resource parameters; and

broadcast, to the distributed ledger, a third transaction reflecting provisioning of the first cloud resource to the client.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the first cloud resource parameters comprise at least one of first parameters characterizing compute nodes, second parameters characterizing storage, or third parameters characterizing networking.

17. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions, when executed by the processing device, further cause the processing device to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the instructions, when executed by the processing device, cause the processing device to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation.

18. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions, when executed by the processing device, further cause the processing device to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, instructions, when executed by the processing device, cause the processing device to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation, wherein the smart contract code is to select, among two or more qualified cloud resource parameters, a cloud resource parameter that specifies a minimal cloud resource parameter.

19. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions, when executed by the processing device, further cause the processing device to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the instructions, when executed by the processing device, cause the processing device to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by accepting an electronic signature of an originator of the cloud resource request.

20. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions, when executed by the processing device, further cause the processing device to:

store the cloud resource request on the distributed ledger, wherein to store the cloud resource request, the instructions, when executed by the processing device, cause the processing device to:

cause the distributed ledger to store, in association with the cloud resource request, a smart contract code to implement cloud resource parameter validation by rejecting second cloud resource parameters that were received upon expiration of a predefined timeout triggered by the cloud resource request.

Assignments (3)
CHANGE OF NAME Recorded Mar 3, 2026
From: RED HAT, INC.
To: RED HAT, LLC
Reel/Frame 074913/0759 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2023
From: O'CONNOR, CATHAL; GALLAGHER, BRIAN
To: RED HAT, INC.
Reel/Frame 065011/0623 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 21, 2023
From: O'CONNOR, CATHAL; GALLAGHER, BRIAN
To: RED HAT, INC.
Reel/Frame 064015/0679 →
Continuity (2)
Continuation 17592851 · Feb 4, 2022
Related Publication 20230336499A1 · Oct 19, 2023
References Cited (33)
US 8244559B2 · Horvitz · 2012 [cited by examiner]
US 10686799B2 · Kelly · 2020 [cited by applicant]
US 10694032B2 · Byrne · 2020 [cited by examiner]
US 11063745B1 · Du · 2021 [cited by examiner]
US 11128437B1 · Nossik · 2021 [cited by examiner]
US 11558392B2 · Lee · 2023 [cited by applicant]
US 11641579B1 · Mukherjee · 2023 [cited by examiner]
US 11706155B1 · O'Connor · 2023 [cited by examiner]
US 20130031028A1 · Martin · 2013 [cited by applicant]
US 20170109815A1 · Bai · 2017 [cited by applicant]
US 20180060106A1 · Madtha · 2018 [cited by applicant]
US 20180060894A1 · Beveridge · 2018 [cited by applicant]
US 20180062928A1 · Beveridge · 2018 [cited by applicant]
US 20180063021A1 · Beveridge · 2018 [cited by applicant]
US 20180063026A1 · Beveridge · 2018 [cited by applicant]
US 20180063235A1 · Beveridge · 2018 [cited by applicant]
US 20180095997A1 · Beveridge · 2018 [cited by applicant]
US 20180260251A1 · Beveridge · 2018 [cited by applicant]
US 20190058709A1 · Kempf · 2019 [cited by examiner]
US 20190334726A1 · Kelly · 2019 [cited by examiner]
US 20200019865A1 · Wang · 2020 [cited by examiner]
US 20200076884A1 · Li · 2020 [cited by examiner]
US 20200136843A1 · Chalakudi · 2020 [cited by applicant]
US 20200334773A1 · Spangenberg · 2020 [cited by examiner]
US 20200394654A1 · Concannon · 2020 [cited by applicant]
US 20200401578A1 · Shi · 2020 [cited by applicant]
US 20210281428A1 · Kempf · 2021 [cited by applicant]
US 20210288918A1 · Sciancalepore · 2021 [cited by examiner]
US 20210409409A1 · Palanisamy · 2021 [cited by examiner]
US 20220358185A1 · Newman · 2022 [cited by examiner]
US 20230013119A1 · Gaur · 2023 [cited by examiner]
Nguyen et al., “Integration of Blockchain and Cloud of Things: Architecture, Applications and Challenges”, Student Member, Senior Member; IEEE, Aug. 28, 2020, 29 pages https://arxiv.org/pdf/1908.09058.pdf. [cited by applicant]
“Amazon Managed Blockchain”, Amazon Web Services, Inc., 2021, 14 pages https://aws.amazon.com/managed-blockchain/. [cited by applicant]