# US 2019/0377557 A1 · Data processing simulator

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

- Number: US 2019/0377557 A1
- Document ID: US20190377557A1
- Status: Published application
- Kind: A1
- Application number: 16/003,435
- Filed: 2018-06-08
- Published: 2019-12-12
- Earliest claimed: 2018-06-08
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Raphael Dibbern; Olaf Tennie
- Web page: https://patentgrep.com/patent/US20190377557A1

## CPC

- G06F 8/38: for implementing user interfaces
- G06F 9/455: Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F 8/10: Requirements analysis; Specification techniques
- G06F 8/20: Software design
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and system including an application server; a framework including a simulator module; a display; a storage device; and a simulator processor in communication with the simulator module and operative to execute processor-executable process steps to cause the system to: receive a metadata file for an application; receive a request from a user interface associated with the application; transmit the request to the simulator module; generate, in response to the received request, one or more simulated data elements at the simulator module based on the metadata and a communication protocol; and display the one or more simulated data elements on the display. Numerous other aspects are provided.

## Claims

### Claim 1

A system comprising:
an application server;
a framework including a simulator module;
a display;
a storage device; and
a simulator processor in communication with the simulator module and operative to execute processor-executable process steps to cause the system to:
receive a metadata file for an application;
receive a request from a user interface associated with the application for execution of the application, wherein execution of the application is expected to return a particular data element in response to the request;
transmit the request to the simulator module;
generate, in response to the received request for execution of the application, and without using business logic of the application for execution, one or more simulated data elements that correspond the particular data elements, at the simulator module based on the metadata and a communication protocol; and
display the one or more simulated data elements on the display.

### Claim 2

(canceled)

### Claim 3 (depends on 1)

The system of claim 1, wherein the metadata file includes a data type that describes a structure for the simulated data elements generated by the simulator module.

### Claim 4 (depends on 3)

The system of claim 3, wherein each of the simulated one or more data elements meets requirements for the data type in the metadata file.

### Claim 5 (depends on 1)

The system of claim 1, wherein the request adheres to a well-defined communication protocol format.

### Claim 6 (depends on 1)

The system of claim 1, wherein the request includes a simulator module activator.

### Claim 7 (depends on 6)

The system of claim 6, wherein transmitting the request to the simulator module further comprises processor-executable process steps to cause the system to:
determine the request includes the simulator module activator.

### Claim 8 (depends on 1)

The system of claim 1, wherein the metadata file describes a structure for the simulated data elements generated by the simulator module.

### Claim 9 (depends on 3)

The system of claim 3, wherein the generated one or more simulated data elements each include a field name included in the request and a number, and wherein each simulated data element is unique.

### Claim 10 (depends on 3)

The system of claim 3, further comprising:
an additional data source, and wherein the simulator module uses data from the additional data source to generate each of the one or more simulated data elements.

### Claim 11

A computer-implemented method comprising:
receiving a metadata file for an application at an application server;
receiving a request from a user interface associated with the application at a framework for execution of the application, wherein execution of the application is expected to return a particular data element in response to the request;
transmitting the request to a simulator module;
generating, via the simulator module, and in response to the received request for execution of the application, and without using business logic of the application for execution, one or more simulated data elements that correspond to the particular data elements, at the simulator module based on the metadata and a communication protocol; and
displaying the one or more simulated data elements on the display.

### Claim 12 (depends on 11)

The method of claim 11, wherein the request adheres to a well-defined communication protocol format.

### Claim 13 (depends on 11)

The method of claim 11, wherein the request includes a simulator module activator.

### Claim 14 (depends on 13)

The method of claim 13, wherein transmitting the request to the simulator module further comprises:
determining the request includes the simulator module activator.

### Claim 15 (depends on 11)

The method of claim 11, wherein the metadata file describes a structure for the simulated data elements generated by the simulator module.

### Claim 16 (depends on 11)

The method of claim 11, wherein the metadata file includes a data type that describes a structure for the simulated data elements generated by the simulator module.

### Claim 17 (depends on 16)

The method of claim 16, wherein each of the simulated one or more data elements meets requirements for the data type in the metadata file.

### Claim 18

A non-transitory computer-readable medium storing program code, the program code executable by a computer system to cause the computer system to:
receive a metadata file for an application;
receive a request from a user interface associated with the application for execution of the application, wherein execution of the application is expected to return a particular data element in response to the request;
transmit the request to the simulator module;
generate, in response to the received request for execution of the application, and without using business logic of the application for execution, one or more simulated data elements that correspond to the particular data elements, at the simulator module based on the metadata and a communication protocol; and
display the one or more simulated data elements on the display.

### Claim 19 (depends on 18)

The medium of claim 18, wherein the request adheres to a well-defined communication protocol format.

### Claim 20

(canceled)
