US 10,372,518 B2Granted

Extensible single point orchestration system for application program interfaces

AssigneeAccenture Global Solutions Limited

InventorsSteven O'Kennedy, James Daniel Dickerson, Jeremy Light, Bogumil Swiecki, Ian James Harris, Amit K. Mallick

Life of this patent

Estimating the term…

Loading patent…

Abstract

An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

Claims20

Dependent claims

An extensible single point orchestration system for application program interfaces (APIs) comprising:

a processor configured to receive a service request from an application, the service request comprising a request for services and a developer API key;
the processor configured to execute a context service to generate, based on the service request, an identifier of one of a plurality of configuration entities stored in memory, a plurality of parameters, and a service type indication, the service type indication comprising an aggregation service type or a selection service type;
the processor configured to apply a first stored configuration entity identified with the identifier to a first core capability service, in response to the service type indication being the aggregation service type, and dynamically adapt the first core capability service to generate a plurality of different API specific service call messages, the different API specific service call messages comprising respective API keys for each of a plurality of different external third party provider services and at least some of the parameters, the respective API keys injected into the different API specific service call messages based on the developer API key included in the service request;
and
the processor configured to apply a second stored configuration entity identified with the identifier to a second core capability service, in response to the service type indication being the selection service type, and dynamically adapt the second core capability service to generate an API specific service call message, the API specific service call message comprising an API key of only one of the plurality of different external third party provider services and at least some of the parameters, the API key injected into the API specific service call message based on the developer API key included in the service request.

2 more elements

An extensible key management system comprising:

a processor executable to:
proxy a service call message received from an application, the service call message for an external application program interface (API) of a third party provider service;
parse the service call message;
identify a developer API key included in the service call message, the developer API key associated with the application;
retrieve a sub-key for the external API, the sub-key previously stored in association with the developer API key, the application and the external API of the third party provider service;
replace the developer API key with the sub-key for the external API;
and
proxy the service call message with the sub-key to the external API of the third party provider service.

5 more elements

A non-transitory computer readable medium that includes instructions executable by a processor, the computer readable medium comprising:

instructions executable by the processor to associate an application with a first application program interface (API) proxy for a first external API of a first third party provider service;
instructions executable by the processor to associate the application with a second API proxy for a second external API of a second third party provider service;
instructions executable by the processor to obtain a first sub-key for the first external API when the application is associated with the first API proxy;
instructions executable by the processor to obtain a second sub-key for the second external API when the application is associated with the second API proxy;
instructions executable by the processor to store the first sub-key in a data store in a first association with a developer API key, the application and the first external API, the developer API key owned by a developer of the application;
instructions executable by the processor to store the second sub-key in the data store in a second association with said developer API key, the application and the second external API;
instructions executable by the processor to receive a first service call message from the application for the first external API that includes the developer API key;
instructions executable by the processor to receive a second service call message from the application for the second external API that includes said developer API key;
instructions executable by the processor to replace the developer API key with the first sub-key in the first service call message based on the first association stored in the data store;
and
instructions executable by the processor to replace the developer API key with the second sub-key in the second service call message based on the second association.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/007,996Filed 13 Jun 2018 · continuation
Priority: 17 Mar 2017
Published: US 2018/0357114 A113 Dec 2018
Granted: 6 Aug 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification27 codes

G06F 9/547
Interprogram communication: remote procedure calls [RPC]; Web services
G06F 9/54
Multiprogramming arrangements: interprogram communication
G06F 9/541
Interprogram communication: via adapters, e.g. between incompatible applications
G06F 21/00
Security arrangements for protecting computers, components thereof, programs or data against unauthorised

Family

Application62/473,194Us provisional application · filed 17 Mar 2017
Application15/659,421Parent of this continuation · filed 25 Jul 2017
US 2018/0357114 A1Pre-grant publication · published 13 Dec 2018
US 10,042,685 B1Parent of this continuation
US 10,372,518 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key