IP Library › Granted Patent US 12,236,287
Granted Patent B2
US 12,236,287 · App. 18/326,467 · Granted Feb 25, 2025

Systems and methods for implementing an intelligent application program interface for an intelligent optimization platform

Inventors: Alexandra Johnson (San Francisco, CA); Patrick Hayes (San Francisco, CA); Scott Clark (San Francisco, CA)
Assignee: Intel Corporation
G06F9/54G06F11/3495G06N20/00
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,236,287
App. No.
18/326,467
Granted
Feb 25, 2025
Kind
B2
Abstract

Systems and methods for implementing an application programming interface (API) that controls operations of a machine learning tuning service for tuning a machine learning model for improved accuracy and computational performance includes an API that is in control communication the tuning service that: executes a first API call function that includes an optimization work request that sets tuning parameters for tuning hyperparameters of a machine learning model; and initializes an operation of distinct tuning worker instances of the service that each execute distinct tuning tasks for tuning the hyperparameters; executes a second API call function that identifies raw values for the hyperparameters; and generates suggestions comprising proposed hyperparameter values selected from the plurality of raw values for each of the hyperparameters; and executes a third API call function that returns performance metrics relating to a real-world performance of the subscriber machine learning model executed with the proposed hyperparameter values.

Claims (33)

1. A computer-readable storage device comprising machine-readable instructions to cause programmable circuitry to at least:

access a request to tune a machine learning model from a client, the request accessed at an application programming interface (API), the request conveyed to the API using a hypertext transfer protocol (HTTP) message, the request to include an identification of the machine learning model to be tuned and information to be used in the tuning of the machine learning model;

validate an API key provided via the request to tune the machine learning model;

after validating the API key, queue execution of the tuning of the machine learning model; and

provide a response message to the client.

2. The computer-readable storage device of claim 1 , wherein the response message is to include information about the queued execution of the requested tuning of the machine learning model.

3. The computer-readable storage device of claim 1 , wherein the request to tune the machine learning model is to include a stopping criterion.

4. The computer-readable storage device of claim 1 , wherein the request to tune the machine learning model is to include one or more hyperparameters to be used in the tuning of the machine learning model.

5. The computer-readable storage device of claim 1 , wherein the instructions are to cause the programmable circuitry to provide the API key to the client.

6. The computer-readable storage device of claim 1 , wherein the API is a representational state transfer (REST) API.

7. An apparatus comprising:

an interface;

machine-readable instructions;

programmable circuitry to execute the machine-readable instructions to at least:

access a request to tune a machine learning model from a client, the request accessed at an application programming interface (API), the request conveyed to the API using a hypertext transfer protocol (HTTP) message, the request to include an identification of the machine learning model to be tuned and information to be used in the tuning of the machine learning model;

validate an API key provided via the request to tune the machine learning model;

after validating the API key, queue execution of the tuning of the machine learning model; and

cause the interface to provide a response message to the client.

8. The apparatus of claim 7 , wherein the response message is to include information about the queued execution of the requested tuning of the machine learning model.

9. The apparatus of claim 7 , wherein the request to tune the machine learning model is to include a stopping criterion.

10. The apparatus of claim 7 , wherein the request to tune the machine learning model is to include one or more hyperparameters to be used in the tuning of the machine learning model.

11. The apparatus of claim 7 , wherein the programmable circuitry is to provide the API key to the client.

12. The apparatus of claim 7 , wherein the API is a representational state transfer (REST) API.

13. A method comprising:

accessing, by executing an instruction using programmable circuitry, a request to tune a machine learning model from a client, the request accessed at an application programming interface (API), the request conveyed to the API using a hypertext transfer protocol (HTTP) message, the request to include an identification of the machine learning model to be tuned and information to be used in the tuning of the machine learning model;

validating, by executing an instruction using the programmable circuitry, an API key provided via the request to tune the machine learning model;

after validating the API key, queuing execution of the tuning of the machine learning model; and

providing a response message to the client.

14. The method of claim 13 , wherein the response message is to include information about the queued execution of the requested tuning of the machine learning model.

15. The method of claim 13 , wherein the request to tune the machine learning model is to include a stopping criterion.

16. The method of claim 13 , wherein the request to tune the machine learning model is to include one or more hyperparameters to be used in the tuning of the machine learning model.

17. The method of claim 13 , further including providing the API key to the client.

18. The method of claim 13 , wherein the API is a representational state transfer (REST) API.

Continuity (8)
Continuation 17516296 · Nov 1, 2021
Continuation 16741895 · Jan 14, 2020
Continuation 16559846 · Sep 4, 2019
Continuation 16450891 · Jun 24, 2019
Continuation 16359107 · Mar 20, 2019
Continuation 16173737 · Oct 29, 2018
Provisional Application 62578886 · Oct 30, 2017
Related Publication 20230385129A1 · Nov 30, 2023
References Cited (56)
US 7363281B2 · Jin · 2008 [cited by applicant]
US 8364613B1 · Lin · 2013 [cited by applicant]
US 9786036B2 · Annapureddy · 2017 [cited by applicant]
US 9858529B2 · Adams · 2018 [cited by applicant]
US 10217061B2 · Hayes et al. · 2019 [cited by applicant]
US 10282237B1 · Johnson · 2019 [cited by applicant]
US 10379913B2 · Johnson · 2019 [cited by applicant]
US 10445150B1 · Johnson · 2019 [cited by applicant]
US 10528891B1 · Cheng · 2020 [cited by applicant]
US 10558934B1 · Cheng · 2020 [cited by applicant]
US 10565025B2 · Johnson · 2020 [cited by applicant]
US 10607159B2 · Hayes · 2020 [cited by applicant]
US 10621514B1 · Cheng · 2020 [cited by applicant]
US 10740695B2 · Cheng · 2020 [cited by applicant]
US 11163615B2 · Johnson et al. · 2021 [cited by applicant]
US 11270217B2 · Tee · 2022 [cited by applicant]
US 11709719B2 · Johnson · 2023 [cited by applicant]
US 20070019065A1 · Mizes · 2007 [cited by applicant]
US 20080183648A1 · Goldberg · 2008 [cited by applicant]
US 20090244070A1 · Mattikalli et al. · 2009 [cited by applicant]
US 20100083196A1 · Liu · 2010 [cited by applicant]
US 20150282003A1 · Noerpel · 2015 [cited by examiner]
US 20150288573A1 · Baughman · 2015 [cited by applicant]
US 20160078361A1 · Brueckner · 2016 [cited by examiner]
US 20160110657A1 · Gibiansky · 2016 [cited by examiner]
US 20160132787A1 · Drevo · 2016 [cited by applicant]
US 20160232540A1 · Gao · 2016 [cited by applicant]
US 20170124487A1 · Szeto · 2017 [cited by applicant]
US 20180121797A1 · Prabhu · 2018 [cited by applicant]
US 20180129892A1 · Bahl · 2018 [cited by applicant]
US 20180240041A1 · Koch · 2018 [cited by applicant]
US 20180336493A1 · Hayes · 2018 [cited by applicant]
US 20180356949A1 · Wang · 2018 [cited by applicant]
US 20190129764A1 · Johnson · 2019 [cited by applicant]
US 20190156229A1 · Tee · 2019 [cited by applicant]
US 20190213326A1 · Dykes · 2019 [cited by examiner]
US 20190220755A1 · Carbune · 2019 [cited by applicant]
US 20200111018A1 · Golovin · 2020 [cited by applicant]
US 20200202254A1 · Hayes · 2020 [cited by applicant]
US 20200302342A1 · Cheng · 2020 [cited by applicant]
Zou et al., “Regularization and Variable Selection via the Elastic Net,” Journal of the Royal Statistical Society, vol. 67, Issue 2, Apr. 2005, 20 pages. [cited by applicant]
Zhou et al., “Combining Global and Local Surrogate Models to Accelerate Evolutionary Optimization,” IEEE Transactions on Systems, Man, and Cybernetics—Part C: Applications and Reviews, vol. 37, No. 1, dated Jan. 2007, 1… [cited by applicant]
Gardner et al., “Bayesian Optimization with Inequality Constraints,” Proceedings of the 31st International Conference in Machine Learning, Beijing, China, Jun. 2014, 10 pages. [cited by applicant]
Bergstra et al., “Hyperopt: a Python Library for Model Selection and Hyperparameter Optimization,” Computational Science & Discovery, Jul. 2015, 25 pages. [cited by applicant]
Golovin et al., “Google Vizier: A Service for Black-Box Optimization,” KDD '17, Aug. 13-17, 2017, Halifax, NS, Canada, dated Aug. 13, 2017, 10 pages. [cited by applicant]
Diaz et al., “An Effective Algorithm for Hyperparameter Optimization of Neural Networks,” IBM Journal of Research and Development, vol. 61, No. 4/5, dated Sep. 8, 2017, 20 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/173,737, dated Jan. 28, 2019, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/359,107, dated May 8, 2019, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/450,891, dated Aug. 7, 2019, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/559,846, dated Oct. 16, 2019, 11 pages. [cited by applicant]
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 16/559,846, dated Dec. 17, 2019, 4 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/741,895, dated Mar. 19, 2021, 7 pages. [cited by applicant]
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in U.S. Appl. No. 16/741,895, dated Apr. 7, 2021, 3 pages. [cited by applicant]
United State Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/741,895, dated Jun. 30, 2021, 8 pages. [cited by applicant]
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in U.S. Appl. No. 17/516,296, mailed on Mar. 2, 2023, 9 pages. [cited by applicant]
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 17/516,296, dated Jun. 12, 2023, 2 pages. [cited by applicant]