Adaptive interface for cross-platform component generation

• US 9,983,869 B2
• Filed: 07/31/2014
• Issued: 05/29/2018
• Est. Priority Date: 07/31/2014
• Status: Active Grant

• Current Assignee: The MathWorks, Inc.
• Original Assignee: The MathWorks, Inc.
• Inventors: Webb, Peter Hartwell
• Primary Examiner(s): Armouche, Hadi S
• Assistant Examiner(s): HOLMES, ANGELA R
• Application Number:
  US14/448,671
• Publication Number:
  US 20160034276A1
• Time in Patent Office: 1,398 Days
• Field of Search: 726 2
• CPC Class Codes: G06F 21/105 Arrangements for software license management or administration, e.g. for managing licenses at corporate level
• CPC Class Codes: G06F 21/125 by manipulating the program code, e.g. source code, compiled code, interpreted code, machine code
• CPC Class Codes: G06F 21/6281 at program execution time, where the protection is within the operating system
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting

Abstract

Exemplary embodiments provide adapted components that may be used by a computer program under different execution contexts. The adapted components may include platform independent source code which may be executed regardless of the execution context in which the component is deployed. Adaptation logic may wrap the execution context independent component in a wrapper. The wrapper may perform data marshaling between the execution context independent component and a computer program invoking the execution context independent component, or the host system on which the computer program is deployed. The execution context independent component may be adapted to a new execution context dynamically the first time that the execution context independent component is invoked in the execution context. Thereafter, the execution context independent component may be invoked statically without the need to re-adapt the component.

Claims

1. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:

receive a component request from a client, the component request specifying;

a requested component, the requested component being executable, and

an execution context, the execution context comprising;

an attribute that relates to circumstances under which the requested component is executed;

process the received component request to access or generate an interface for the specified execution context for invoking the requested component in the specified execution context and to forward the interface to the client;

generate an adapted component based on the received component request, the adapted component;

having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client, and

implementing the requested component;

wherein the component request further specifies one or more local components; and

wherein generating a response to the component request comprises;

analyzing the one or more local components,

identifying if there is a missing component, the missing component used by the requested component,

where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and

execute the requested component.

2. The medium of claim 1, wherein the component is executed as a part of a simulation.

3. The medium of claim 1, wherein the component request further specifies a type or order for at least one input to the requested component.

4. The medium of claim 1, wherein the requested component is not compatible with the execution context prior to being adapted.

5. The medium of claim 1, further storing instructions that, when executed by one or more processors, cause the one or more processors to:

dynamically generate the adapted component when the component request is received.

6. The medium of claim 1, wherein the attribute of the execution context comprises at least one of:

a programming language,

a target architecture,

a host platform, and

an execution model.

7. The medium of claim 6, wherein the wrapper is a host-platform-specific wrapper that calls execution context independent code, the execution context independent code implementing the requested component.

8. The medium of claim 7, wherein the host-platform-specific wrapper is identified by a wrapper name, and the wrapper name corresponds to a name for the requested component.

9. The medium of claim 1, wherein the adapted component performs data marshaling for the requested component.

10. The medium of claim 1, further storing instructions that, when executed by one or more processors, cause the one or more processors to:

retrieve the adapted component from a library.

11. The medium of claim 1, further storing instructions that, when executed by one or more processors, cause the one or more processors to:

analyze the component request,

determine one or more dependent functions called by the requested component, the determining based at least in part on the analyzing,

acquire the one or more dependent functions, and

adapt the one or more dependent functions to the execution context of the adapted component so that the requested component may invoke the one or more dependent functions.

12. The medium of claim 1, further storing instructions that, when executed by one or more processors, cause the one or more processors to:

receive authentication, and

generate or execute the adapted component only if authorized to access the requested component in the execution context specified in the component request.

13. The medium of claim 1, wherein the adapted component contains licensing metadata specifying a permitted entity, the permitted entity being allowed to use the adapted component.

14. The medium of claim 13, wherein the licensing metadata further specifies at least one of:

a usage limit, a supported architecture, a type of interface generated for the adapted component, information for debugging the adapted component, a valid execution model for the adapted component, information relating to viewing or modifying source code for the adapted component, and a supported environment for the adapted component.

15. A computer-implemented method comprising:

receiving, using one or more processors, a component request from a client, the component request specifying;

a requested component, the requested component being executable, and

an execution context, the execution context comprising an attribute that relates to the circumstances under which the requested component is executed;

processing, using the one or more processors, the component request to access or generate an interface for an execution context for invoking the requested component in the execution context and to forward the interface to the client;

generating, using one or more processors, a response to the component request, the response comprising an adapted component, the adapted component;

having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client, and

implementing the requested unit of functionality;

wherein the component request further specifies one or more local components;

wherein generating the response to the component request comprises;

analyzing the one or more local components,

identifying if there is a missing component, the missing component used by the requested component,

where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and

executing the request component.

16. The method of claim 15, further comprising:

dynamically generating the adapted component when the component request is received.

17. The method of claim 15, wherein the component request further specifies a host platform of the client, the host platform describing one or more system parameters of the client, and the adapted component is further compatible with the host platform.

18. The method of claim 17, wherein the wrapper is a host-platform-specific wrapper that calls platform independent code implementing the requested component.

19. The method of claim 18, wherein the host-platform-specific wrapper is identified by a wrapper name, and the wrapper name corresponds to a name of the requested unit of functionality.

20. A system comprising:

a non-transitory storage medium storing;

a library of components; and

one or more processors configured to;

process a component request from a client to access or generate an interface for an execution context for invoking the requested component in the execution context and to forward the interface to the client, the component request specifying;

the execution context comprising an attribute that relates to the circumstances under which the requested component is executed, and

a requested unit of functionality;

identify a target component in the library, the target component compatible with the component request;

generate a response to the component request, the response comprising an adapted component, the adapted component;

having a wrapper that translates input to the component into a format that is understandable by the component and/or translates output from the component into a format that is understandable to the client

having been generated from the target component,

implementing the requested unit of functionality;

wherein the component request further specifies one or more local components; and

wherein generating the response to the component request comprises;

analyzing the one or more local components,

identifying if there is a missing component, the missing component used by the requested component,

where there is a missing component, retrieving the missing component from an external component library, and adding the missing component to the adapted component; and

execute the requested component.