IP Library › Granted Patent US 12,360,828
Granted Patent B2
US 12,360,828 · App. 17/387,726 · Granted Jul 15, 2025

Exposing a cloud API based on supported hardware

Inventors: Eran Kuris (Ra'anana, IL); Arie Bregman (Ra'anana, IL)
Assignee: Red Hat, Inc.
G06F9/542G06F9/547
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,360,828
App. No.
17/387,726
Granted
Jul 15, 2025
Kind
B2
Abstract

A system and method for exposing a cloud application programming interface (API) based on supported hardware of a cloud service system. The method includes executing a cloud service application to provide one or more services. The method includes maintaining, in a data storage, a plurality of linkages between a plurality of service identifiers corresponding to the one or more services of the cloud service application and a plurality of hardware identifiers. The method includes determining, based on the plurality of linkages and/or a hardware profile of the cloud service system, whether the cloud service system has a capability to provide access to the one or more services of the cloud service application. The method includes providing exposure to application programming interfaces (APIs) of at least one of the one or more services of the cloud service application.

Claims (57)

1. A method comprising:

executing, by a cloud service system, a cloud service application to provide one or more services;

maintaining, by the cloud service system in a data storage, a plurality of linkages between a plurality of service identifiers corresponding to the one or more services of the cloud service application and a plurality of hardware identifiers, each respective service identifier is associated with one or more hardware identifiers of the plurality of hardware identifiers;

determining, by the cloud service system based on the plurality of linkages and a hardware profile of the cloud service system, whether the cloud service system has a hardware capability to provide access to the one or more services of the cloud service application;

providing, by the cloud service system to a client device responsive to determining whether the cloud service system has the hardware capability to provide the access to the one or more services, exposure to application programming interfaces (APIs) of at least one of the one or more services of the cloud service application;

determining that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application;

blocking, by the cloud service system, the APIs of the at least one of the one or more services of the cloud service application from the client device to prevent the client device from accessing the APIs of the at least one of the one or more services of the cloud service application responsive to determining that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application; and

sending, by the cloud service system to the client device, a message indicating a plurality of services that are not supported by the hardware profile and descriptions of one or more hardware components that are missing from the hardware profile to execute the plurality of services.

2. The method of claim 1 , further comprising:

detecting, by the cloud service system, the hardware profile of the cloud service system.

3. The method of claim 1 , further comprising:

detecting an occurrence of a triggering event, wherein the determining as to whether the cloud service application has the hardware capability to provide the access to the one or more services of the cloud service application is responsive to detecting the occurrence of the triggering event.

4. The method of claim 3 , further comprising:

detecting, by the cloud service system, the occurrence of the triggering event by detecting a change in the hardware profile of the cloud service system.

5. The method of claim 4 , further comprising:

detecting, by the cloud service system, the change in the hardware profile by receiving an indication from an operating system of the cloud service system that the hardware profile of the cloud service system has changed.

6. The method of claim 4 , further comprising:

detecting, by the cloud service system, the change in the hardware profile by scanning the cloud service system to detect whether the hardware profile of the cloud service system has changed.

7. The method of claim 3 , further comprising:

detecting, by the cloud service system, the occurrence of the triggering event by receiving a request from the client device for exposure to an application programming interface (API) of a particular service of the cloud service application.

8. The method of claim 4 , further comprising:

detecting, by the cloud service system, the occurrence of the triggering event by detecting that the cloud service application has been updated to provide a different set of the one or more services.

9. The method of claim 1 , wherein providing exposure to the APIs of at least one of the one or more services comprises:

determining, by the cloud service system based on the plurality of linkages and the hardware profile of the cloud service system, that the cloud service system has the hardware capability to provide access to a first set of the one or more services of the cloud service application;

determining, by the cloud service system based on the plurality of linkages and the hardware profile of the cloud service system, that the cloud service system lacks the hardware capability to provide access to a second set of the one or more services of the cloud service application; and

providing, by the cloud service system to the client device, access to APIs of the first set of the one or more services of the cloud service system without providing access to APIs of the second set of the one or more services of the cloud service application.

10. The method of claim 1 , wherein maintaining the plurality of linkages in the data storage comprises:

detecting, by the cloud service system, that the cloud service application has been updated to provide a different set of the one or more services; and

updating, by the cloud service system, the plurality of linkages using one or more linkages corresponding to the different set of the one or more services.

11. A cloud service system comprising:

a data storage; and

a processing device, operatively coupled to the data storage, to:

execute a cloud service application to provide one or more services;

maintain, in the data storage, a plurality of linkages between a plurality of service identifiers corresponding to the one or more services of the cloud service application and a plurality of hardware identifiers, each respective service identifier is associated with one or more hardware identifiers of the plurality of hardware identifiers;

determine, based on the plurality of linkages and a hardware profile of the cloud service system, whether the cloud service system has a hardware capability to provide access to the one or more services of the cloud service application;

provide, to a client device responsive to determining whether the cloud service system has the hardware capability to provide the access to the one or more services, exposure to application programming interfaces (APIs) of at least one of the one or more services of the cloud service application;

determine that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application;

block, by the cloud service system, the APIs of the at least one of the one or more services of the cloud service application from the client device to prevent the client device from accessing the APIs of the at least one of the one or more services of the cloud service application responsive to determining that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application; and

send, by the cloud service system to the client device, a message indicating a plurality of services that are not supported by the hardware profile and descriptions of one or more hardware components that are missing from the hardware profile to execute the plurality of services.

12. The cloud service system of claim 11 , wherein the processing device is further to:

detect an occurrence of a triggering event, wherein the determining as to whether the cloud service application has the hardware capability to provide the access to the one or more services of the cloud service application is responsive to detecting the occurrence of the triggering event.

13. The cloud service system of claim 12 , wherein the processing device is further to:

detect the occurrence of the triggering event by detecting a change in the hardware profile of the cloud service system.

14. The cloud service system of claim 13 , wherein the processing device is further to:

detect the change in the hardware profile by receiving an indication from an operating system of the cloud service system that the hardware profile of the cloud service system has changed.

15. The cloud service system of claim 13 , wherein the processing device is further to:

detect the change in the hardware profile by scanning the cloud service system to detect whether the hardware profile of the cloud service system has changed.

16. The cloud service system of claim 12 , wherein the processing device is further to:

detect the occurrence of the triggering event by receiving a request from the client device for exposure to an application programming interface (API) of a particular service of the cloud service application.

17. A non-transitory computer-readable medium storing instructions that, when executed by a processing device of a cloud service system, cause the processing device to:

execute, by the processing device, a cloud service application to provide one or more services;

maintain, in a data storage, a plurality of linkages between a plurality of service identifiers corresponding to the one or more services of the cloud service application and a plurality of hardware identifiers, each respective service identifier is associated with one or more hardware identifiers of the plurality of hardware identifiers;

determine, based on the plurality of linkages and a hardware profile of the cloud service system, whether the cloud service system has a hardware capability to provide the access to the one or more services of the cloud service application;

provide, to a client device responsive to determining whether the cloud service system has the hardware capability to provide the access to the one or more services, exposure to application programming interfaces (APIs) of at least one of the one or more services of the cloud service application;

determine that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application;

block, by the cloud service system, the APIs of the at least one of the one or more services of the cloud service application from the client device to prevent the client device from accessing the APIs of the at least one of the one or more services of the cloud service application responsive to determining that the cloud service system no longer has the hardware capability to provide access to the one or more services of the cloud service application; and

send, by the cloud service system to the client device, a message indicating a plurality of services that are not supported by the hardware profile and descriptions of one or more hardware components that are missing from the hardware profile to execute the plurality of services.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 28, 2021
From: KURIS, ERAN; BREGMAN, ARIE
To: RED HAT, INC.
Reel/Frame 057010/0290 →
Continuity (1)
Related Publication 20230031610A1 · Feb 2, 2023
References Cited (25)
US 5909593A · Abbondonzio · 1999 [cited by examiner]
US 9661064B2 · Kranz et al. · 2017 [cited by applicant]
US 9690815B2 · Cronin et al. · 2017 [cited by applicant]
US 9729506B2 · Call et al. · 2017 [cited by applicant]
US 9733953B2 · Hall · 2017 [cited by applicant]
US 10033833B2 · Fu · 2018 [cited by examiner]
US 20140215312A1 · Hicks et al. · 2014 [cited by applicant]
US 20150046583A1 · Celi, Jr. · 2015 [cited by examiner]
US 20150195303A1 · Holden et al. · 2015 [cited by applicant]
US 20160124742A1 · Rangasamy et al. · 2016 [cited by applicant]
US 20160267153A1 · Witkop · 2016 [cited by examiner]
US 20180210768A1 · Dai et al. · 2018 [cited by applicant]
US 20180324062A1 · Chen · 2018 [cited by examiner]
US 20190028360A1 · Douglas · 2019 [cited by examiner]
US 20190097900A1 · Rodriguez · 2019 [cited by examiner]
US 20200162359A1 · Borkar et al. · 2020 [cited by applicant]
US 20200249936A1 · Barfield, Jr. · 2020 [cited by examiner]
US 20210064433A1 · Nakfour · 2021 [cited by applicant]
US 20210294679A1 · Thakur · 2021 [cited by examiner]
US 20220139143A1 · Avitan · 2022 [cited by examiner]
CN 109660392 · 2019 [cited by applicant]
WO 20200190256A1 · 2020 [cited by applicant]
“WSO2 API Manager”, located at https://wso2.com/api-manager/, Jun. 4, 2021; 6 pages. [cited by applicant]
“Google Cloud APIs”, located at https://cloud.google.com/apis/docs/overview, May 28, 2021; 4 pages. [cited by applicant]
Extended European Search Report mailed Feb. 25, 2022 for European Application No. 21198744.1. [cited by applicant]