# US 2021/0263736 A1 · Semantic functional wrappers of services

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0263736 A1
- Document ID: US20210263736A1
- Status: Published application
- Kind: A1
- Application number: 17/184,328
- Filed: 2021-02-24
- Published: 2021-08-26
- Earliest claimed: 2020-02-24
- Assignees: Mobilize.Net Corporation
- Applicants: Mobilize.Net Corporation
- Inventors: Tom Button; Federico Zoufaly
- Web page: https://patentgrep.com/patent/US20210263736A1

## CPC

- G06F 8/76: Adapting program code to run in a different environment; Porting
- G06F 8/75: Structural analysis for program understanding
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 2209/541: Client-server
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Functional wrappers are scripts and related software that provide a way to group and invoke functionality comprising semantic intent in a legacy application. These functional wrappers allow programmatic access to functionality in legacy applications in contemporary software architectures without risk of porting errors. Additional functionality to provide features with presently expected, but not available at the time the legacy applications were developed, such as functional wrappers to provide parallelism and scaling, are disclosed. Finally, automatic generation of the functional wrappers are also disclosed.

## Claims

### Claim 1

A system comprising: a processor configured to execute computer-executable instructions, and a memory communicatively connected to the processor configured to store computer-executable instructions to perform the following:
receiving a request to perform a semantic intent;
identifying, via a service map software component, a software functional wrapper that corresponds to the semantic intent in the request; and
executing the software functional wrapper identified by the service map component, wherein the software functional wrapper is configured to invoke a plurality of user interface elements in a legacy software application corresponding to the semantic intent of the request.

### Claim 2 (depends on 1)

The system of claim 1, wherein the software functional wrapper is implemented as a script that invokes user interface element functionality via a journaling hook or operating system API thereby limiting risk of mis-entry.

### Claim 3 (depends on 1)

The system of claim 1, wherein the service map software component exposes its functionality via an application programming interface.

### Claim 4 (depends on 3)

The system of claim 3, further comprising performing a service point enabling invocation of an application programming interface of the service map software component over an internet protocol.

### Claim 5 (depends on 1)

The system of claim 1, wherein the computer-executable instructions further comprise generating a response to the request.

### Claim 6 (depends on 5)

The system of claim 5, wherein the generating includes generating a response that comprises providing information about at least one of error handling or exception handling.

### Claim 7 (depends on 1)

The system of claim 1, wherein the software functional wrapper is configured to invoke at least one of non-legacy software applications or software components corresponding to the semantic intent of the request.

### Claim 8 (depends on 7)

The system of claim 7, wherein the non-legacy software applications or components invoked by the software functional wrapper include at least one of the following:
an identity server;
a transaction monitor; or
a session manager.

### Claim 9 (depends on 7)

The system of claim 7, wherein the non-legacy software applications or components invoked by the software functional wrapper provides a semantic service function.

### Claim 10 (depends on 1)

The system of claim 1, wherein the legacy application invoked by the software functional wrapper is a port of the legacy application to a web application with a web page to cloud model-view-view-model (MVVM) architecture.

### Claim 11 (depends on 10)

The system of claim 10, wherein a web page application functionality of the web application is exposed by a web map software component that renders the web page application functionality via an application programming interface.

### Claim 12 (depends on 1)

The system of claim 1, wherein the software functional wrapper is one of multiple software functional wrappers corresponding to the semantic intent, in which each of the multiple software functional wrappers is associated with a different version indicator, and wherein the identifying includes identifying the software functional wrapper corresponding to the semantic intent of the request based at least on a version indicator of the software functional wrapper.

### Claim 13

A computer-implemented method to generate functional wrappers, comprising:
receiving, at a script generation software application, a legacy application;
analyzing, via the script generation software application, the legacy application to identify user interface elements;
analyzing, via the script generation software application, usage of the legacy application to identify functionality corresponding to semantic intent;
generating, via the script generation software application, virtual user interface elements comprised of wrappers of identified user elements;
generating, via a script generator software component of the script generation software application, a binder software map that maps user interface elements to the functionality identified as corresponding to the semantic intent; and
generating, via the script generator software component of the script generation software application, one or more scripts based at least on the user interface elements as wrapped by the generated virtual user interface elements and the functionality identified as corresponding to the semantic intent.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein a generated script is configured to invoke user interface element functionality via a journaling hook or operating system API thereby limiting risk of mis-entry

### Claim 15 (depends on 13)

The computer-implemented method of claim 13, wherein the analyzing the legacy application to identify the user interface elements including performing a static analysis that comprises scanning, via a scanner software component, source code of the legacy application to identify user interface element identifiers based on user identifier class types.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15, further comprising receiving, at the script generation software application, a preliminary map data file of potential user interface elements, and wherein the static analysis is based at least on the preliminary map data file of potential user interface elements.

### Claim 17 (depends on 15)

The computer-implemented method of claim 15, wherein the analyzing the usage of the legacy application incudes performing a dynamic analysis that comprises:
recording usage activity of a running instance of the legacy application via a recorder software component of the script generation software application;
extracting user interface elements invoked during run time via a recording parser software component of the script generation software application; and
mapping user interface elements identified during static analysis to user interface elements identified during dynamic analysis via a recording converter software component of the script generation software application.

### Claim 18 (depends on 17)

The computer-implemented method of claim 17, further comprising receiving a preliminary software data map, wherein the performing the dynamic analysis includes performing the dynamic analysis based at least on one or more of setup variables or environmental variables included in the preliminary software data map.

### Claim 19 (depends on 17)

The computer-implemented method of claim 17, further comprising receiving a preliminary recording setup data file, wherein performing the dynamic analysis includes performing the dynamic analysis based at least on pre-identified sets of functionality corresponding to the semantic intent included in the preliminary recording converter data file, the semantic intent used by the script generator software component to generate a script corresponding to each semantic intent included in the preliminary recording setup data file.

### Claim 20 (depends on 19)

The method of claim 19, further comprising deploying the generated scripts via storing in a repository at least one generated script, at least the virtual user interface wrappers invoked in the at least one generated script, and the binder software map.

### Claim 21

One or more non-transitory computer-readable media storing computer-executable instructions that upon execution cause one or more processors to perform acts comprising:
receiving a request to perform a semantic intent;
identifying a software functional wrapper corresponding to the semantic intent in the request;
executing the software functional wrapper to invoke a plurality of user interface elements in the legacy software application corresponding to the semantic intent of the request; and
instantiating, in response to the executing the software functional wrapper, an instance of a legacy application including at least one functionality to be invoked by the software functional wrapper, to clear a state of the legacy application and prevent reset errors.

### Claim 22 (depends on 21)

The one or more non-transitory computer-readable media of claim 21, wherein the acts further comprise maintaining a pre-instantiated pool of virtual machines each running an instance of the legacy application, wherein the instantiating the legacy application responsive to the executing of the software functional wrapper is via serving at least one instance of the virtual machines from the pre-instantiated pool.
