APPLICATION PROGRAMMING INTERFACE (API) ENGINE

• US 20160054982A1
• Filed: 08/20/2014
• Published: 02/25/2016
• Est. Priority Date: 08/20/2014
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: ITANI, Abdul, GARTNER, Patrick John
• Granted Patent: US 9,678,723 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

Systems and methods for an application programming interface (API) engine are disclosed. Some implementations include receiving, via a user interface, a selection of a first graphical element representing a first component of an API that is to be generated, where the first component is associated with a first set of one or more reusable programming actions, receiving, via the user interface, instructions to drag the selected first graphical element and another selected second graphical element to a graphical workspace associated with the user interface to connect the first and the second graphical element, combining the first set of reusable programming actions with a second set of reusable programming actions when the selected second graphical element is connected with the first graphical component on the graphical workspace and automatically displaying software code representing the API based on the combination.

Claims

1. A method comprising:

receiving, via a user interface of a processor-based system, a selection of a first graphical element representing a first component of an application programming interface (API) that is to be generated, wherein the first component is associated with a first set of one or more reusable programming actions;

receiving instructions, via the user interface of the processor-based system, to drag the selected first graphical element to a graphical workspace associated with the user interface;

receiving, via the user interface of the processor-based system via, a selection of a second graphical element representing a second component of the API, wherein the second component is associated with a second set of one or more reusable programming actions;

receiving instructions, via the user interface of the processor-based system, to drag the selected second graphical element and connect the selected second graphical element with the first graphical component on the graphical workspace;

combining the first set of reusable programming actions with the second set of reusable programming actions when the selected second graphical element is connected with the first graphical component on the graphical workspace; and

upon the combining, automatically displaying software code representing the API, wherein the software code is embedded in the other software applications to perform the first set and the second set of the one or more reusable programming actions.

2. The method of claim 1, wherein the first graphical element and the second graphical element are connected in parallel to perform the first set and the second set of the one or more reusable programming actions in parallel.

3. The method of claim 1, further comprising:

parsing the first graphical component representing the first set of reusable programming actions and the second graphical component representing the second set of reusable programming actions as a dependency graph of actions; and

executing the actions starting with actions that have no dependencies, until all actions are complete or a fatal error occurs.

4. The method of claim 3, further comprising:

storing information about the status and data shared between the first set of reusable programming actions and the second set of reusable programming actions.

5. The method of claim 1, further comprising:

allowing another set of reusable programming actions to reference the first graphical component representing first set of reusable programming actions or the second graphical component representing the second set of reusable programming actions.

6. The method of claim 1, further comprising:

introducing one or more conditions via the first set of reusable programming actions or the second set of reusable programming actions, wherein the conditions include flags that can used at runtime to determine if an action is eligible for execution.

7. The method of claim 1, further comprising:

adding the first graphical element and the second graphical element to the workspace with a service name as a key.

8. The method of claim 1 further comprising:

generating an action dependency graph representing the combined first set of reusable programming actions and the second set of reusable programming actions;

transforming extensible markup language (XML) of the action dependency graph into an action graph object; and

iterating through each action in the action graph object to build indexes required to satisfy one or more queries.

9. The method of claim 8, wherein the queries include one or more of:

retrieving fully qualified action class name from a particular action'"'"'s name;

retrieving the particular action'"'"'s children; and

retrieving the particular action'"'"'s parents.

10. The method of claim 8, further comprising:

rejecting the action dependency graph at startup when it is determined that the graph is invalid or contains ambiguities, wherein the ambiguities include one or more of;

inability to locate a class matching a fully qualified class name assembled from the action dependency graph;

inclusion of identifiers in the action dependency graph that deviate from configured naming conventions;

or

a parentless action in the action dependency graph.

11. The method of claim 1, further comprising:

providing a copy of a parent connection map to each action in the combined first set of reusable programming actions and the second set of reusable programming actions;

when n actions have the same parent, creating n−

1 copies of connections to the parent so that each action can have a separate parent connection map; and

when an action has multiple parents, combining connection maps from the multiple parents into one map.

12. An application programming interface (API) engine comprising:

a communication interface configured to enable communication via a mobile network;

a processor coupled with the communication interface;

a storage device accessible to the processor; and

an executable program in the storage device, wherein execution of the program by the processor configures the server to perform functions, including functions to;

receive, via a user interface of a processor-based system, a selection of a first graphical element representing a first component of an application programming interface (API) that is to be generated, wherein the first component is associated with a first set of one or more reusable programming actions;

receive, via the user interface of the processor-based system, instructions to drag the selected first graphical element to a graphical workspace associated with the user interface;

receive, via the user interface of the processor-based system via, a selection of a second graphical element representing a second component of the API, wherein the second component is associated with a second set of one or more reusable programming actions;

receive, via the user interface of the processor-based system, instructions to drag the selected second graphical element and connect the selected second graphical element with the first graphical component on the graphical workspace; and

combine the first set of reusable programming actions with the second set of reusable programming actions when the selected second graphical element is connected with the first graphical component on the graphical workspace; and

upon the combination, automatically display software code representing the API, wherein the software code is embedded in the other software applications to perform the first set and the second set of the one or more reusable programming actions.

13. The API engine of claim 12, wherein the first graphical element and the second graphical element are connected in parallel to perform the first set and the second set of the one or more reusable programming actions in parallel.

14. The API engine of claim 12, wherein execution of the program by the processor configures the server to perform functions, including functions to:

parse the first graphical component representing the first set of reusable programming actions and the second graphical component representing the second set of reusable programming actions as a dependency graph of actions; and

execute the actions starting with actions that have no dependencies, until all actions are complete or a fatal error occurs.

15. The API engine of claim 14, wherein execution of the program by the processor configures the server to perform functions, including functions to

store information about the status and data shared between the first set of reusable programming actions and the second set of reusable programming actions.

16. The API engine of claim 12, wherein execution of the program by the processor configures the server to perform functions, including functions to:

allow another set of reusable programming actions to reference the first graphical component representing first set of reusable programming actions or the second graphical component representing the second set of reusable programming actions.

17. The API engine of claim 12, wherein execution of the program by the processor configures the server to perform functions, including functions to:

introduce one or more conditions via the first set of reusable programming actions or the second set of reusable programming actions, wherein the conditions include flags that can used at runtime to determine if an action is eligible for execution.

18. The API engine of claim 12, wherein execution of the program by the processor configures the server to perform functions, including functions to:

add the first graphical element and the second graphical element to the workspace with a service name as a key.

19. The API engine of claim 12, wherein execution of the program by the processor configures the server to perform functions, including functions to:

generate an action dependency graph representing the combined first set of reusable programming actions and the second set of reusable programming actions;

transform extensible markup language (XML) of the action dependency graph into an action graph object; and

iterate through each action in the action graph object to build indexes required to satisfy one or more queries.

20. A non-transitory computer-readable medium comprising instructions which, when executed by one or more computers, cause the one or more computers to:

receive, via a user interface of a processor-based system, a selection of a first graphical element representing a first component of an application programming interface (API) that is to be generated, wherein the first component is associated with a first set of one or more reusable programming actions;

receive, via the user interface of the processor-based system, instructions to drag the selected first graphical element to a graphical workspace associated with the user interface;

receive, via the user interface of the processor-based system via, a selection of a second graphical element representing a second component of the API, wherein the second component is associated with a second set of one or more reusable programming actions;

receive, via the user interface of the processor-based system, instructions to drag the selected second graphical element and connect the selected second graphical element with the first graphical component on the graphical workspace; and

combine the first set of reusable programming actions with the second set of reusable programming actions when the selected second graphical element is connected with the first graphical component on the graphical workspace; and

upon the combination, automatically display software code representing the API, wherein the software code is embedded in the other software applications to perform the first set and the second set of the one or more reusable programming actions.