# US 2013/0159379 A1 · App system platform

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

- Number: US 2013/0159379 A1
- Document ID: US20130159379A1
- Status: Published application
- Kind: A1
- Application number: 13/327,060
- Filed: 2011-12-15
- Published: 2013-06-20
- Earliest claimed: 2011-12-15
- Assignees: Sap SE
- Inventors: Srdjan Boskovic
- Web page: https://patentgrep.com/patent/US20130159379A1

## CPC

- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments illustrated and described herein provide systems, methods, and software of an app system platform that enables apps to provide rich user experiences in accessing and utilizing functionality of an enterprise-class computing system, such as an ERP system. Some such embodiments include groups of mapper objects in a web framework for each supported app that handle specific data types communicated between the app and a web platform. The mapper objects transform data between app consumable formats and formats of connector objects. The connector objects operate to transform data between the respective connector object formats and data formats of consumable by an enterprise-class computing system via interfaces. These and other embodiments are illustrated and described herein.

## Claims

### Claim 1

A method comprising:
receiving, by a web server via a network, a data request from an app, the data request encoded according to a data interchange protocol;
selecting an object mapper, from a plurality of object mappers, to process the data request based on at least one of the app from which the data request was received and the data interchange protocol, the object mapper present and executable in a web application server supporting at least one app;
invoking the selected object mapper to transform the data request into the format of the connector object associated with the object mapper, the invoked object mapper executable within a web framework of a computing device;
forwarding the data request by the invoked object mapper to the connector object associated with the object mapper;
invoking the connector object associated with the object mapper to transform the data request into a data format of at least one communication module of a backend computing application the connector object is adapted to communicate with, the invoked connector object present and executable in the web application server; and
forwarding the encoded data request to the backend computing application.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data request received by the web server is a request for user interface definition data from which the requesting app can render at least a portion of a user interface.

### Claim 3 (depends on 1)

The method of claim 1, wherein the data request received by the web server is a request for application data, the request encoded in a standards-based, lightweight data interchange format protocol.

### Claim 4 (depends on 1)

The method of claim 1, wherein a number of connector objects executable within the web framework is at least equal to a number of a plurality of communication modules of the backend computing application.

### Claim 5 (depends on 4)

The method of claim 4, wherein each connector object is dedicated to a defined or a combination of defined data interchange protocols of a communication module of the backend computing application.

### Claim 6 (depends on 4)

The method of claim 4, wherein the selected object mapper is one of a plurality of object mappers and the web application server includes, for each supported app, an object mapper associated with each respective connector object.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, by the connector object and in response to the data request forwarded to the backend computing application, the requested data, the requested data received encoded according to the data format of at least one communication module of a backend computing application;
transforming, by the connector object, the received data into a format of the connector object;
forwarding, by the connector object, the data in the format of the connector object to the selected object mapper;
transforming, by the selected object mapper, the data received from the connector object to the data interchange protocol in which the data request was received from the app; and
forwarding, via the web server, the data transformed to the data interchange protocol to the app.

### Claim 8

A computer-readable medium, with instructions stored thereon, which when executed by at least one processor of at least one computing device cause the at least one computing device to perform actions comprising:
receiving, by a web server via a network, a data request from an app, the data request encoded according to a data interchange protocol;
selecting an object mapper, from a plurality of object mappers, to process the data request based on at least one of the app from which the data request was received and the data interchange protocol, the object mapper present and executable in a web application server supporting at least one app;
invoking the selected object mapper to transform the data request into the format of the connector object associated with the object mapper, the invoked object mapper executable within a web framework of a computing device;
forwarding the data request by the invoked object mapper to the connector object associated with the object mapper;
invoking the connector object associated with the object mapper to transform the data request into a data format of at least one communication module of a backend computing application the connector object is adapted to communicate with, the invoked connector object present and executable in the web application server; and
forwarding the encoded data request to the backend computing application.

### Claim 9 (depends on 8)

The computer-readable medium of claim 8, wherein the data request received by the web server is a request for user interface definition data from which the requesting app can render at least a portion of a user interface.

### Claim 10 (depends on 8)

The computer-readable medium of claim 8, wherein the data request received by the web server is a request for application data, the request encoded in a standards-based, lightweight data interchange format protocol.

### Claim 11 (depends on 8)

The computer-readable medium of claim 8, wherein a number of connector objects executable within the web framework is at least equal to a number of a plurality of communication modules of the backend computing application.

### Claim 12 (depends on 11)

The computer-readable medium of claim 11, wherein each connector object is dedicated to a defined or a combination of defined data interchange protocols of a communication module of the backend computing application.

### Claim 13 (depends on 11)

The computer-readable medium of claim 11, wherein the selected object mapper is one of a plurality of object mappers and the web application server includes, for each supported app, an object mapper associated with each respective connector object.

### Claim 14 (depends on 8)

The computer-readable medium of claim 8, with further instructions stored thereon, which when executed by the at least one processor of the at least one computing device cause the at least one computing device to perform further actions comprising:
receiving, by the connector object and in response to the data request forwarded to the backend computing application, the requested data, the requested data received encoded according to the data format of at least one communication module of a backend computing application;
transforming, by the connector object, the received data into a format of the connector object;
forwarding, by the connector object, the data in the format of the connector object to the selected object mapper;
transforming, by the selected object mapper, the data received from the connector object to the data interchange protocol in which the data request was received from the app; and
forwarding, via the web server, the data transformed to the data interchange protocol to the app.

### Claim 15

A system comprising:
at least one computing device including at least one processor, at least one memory device, and at least one network interface device;
a web server application stored in the at least one memory device and executable by the at least one processor to receive, process, and respond to data requests received via the at least one network interface device from an app;
a web application server stored in the at least one memory device and executable by the at least one processor to provide an execution environment for modules that execute to service data requests received via the web server, the modules including:
a plurality of object mapper modules that execute to process the data request based on at least one of an app from which the data request was received and a data interchange protocol the request is encoded in, each object mapper module executable:
to transform data between the data interchange protocol of the app and a format of a connector object module associated with the particular object mapper module;
to forward transformed data of a data request to the connector object module associated with the particular object mapper module; and
to forward transformed data received from the respective associated connector object module to the web server;
a plurality of connector object modules that execute to process data requests forwarded by an object mapper module and data in response to data requests forwarded to a backend computing application, each connector object module executable to:
transform data between the format of the respective connector object module into at least one data interchange protocol of a backend computing application;
to forward transformed data of a data request to the backend computing application; and
to forward transformed data received from the backend computing application to the respective mapper object module from which the data request was received.

### Claim 16 (depends on 15)

The system of claim 15, wherein a number of connector object modules stored and executable within the execution environment of the web application server is at least equal to a number of a plurality of communication modules of the backend computing application where each communication module of the backend computing application is dedicated to a defined data type.

### Claim 17 (depends on 16)

The system of claim 16, wherein the plurality of object mapper modules includes a set of object mapper modules for each app supported by the system, a number of object mapper modules included in each set of object mapper modules equal to the number of connector object modules.

### Claim 18 (depends on 16)

The system of claim 16, wherein the defined data types for which a respective connector object module is stored and executable within the execution environment of the web application server include a data type for remote function calls, a data type for Representation State Transfer (RESTful) data, and at least one web services data type.

### Claim 19 (depends on 15)

The system of claim 15, wherein the connector object modules connect backend computing application functionality to the web application server and the object mapper modules map the backend computing application functionality from the web application server to the app.

### Claim 20 (depends on 15)

The system of claim 15, wherein the app is a native, lightweight application of a smartphone device.
