# US 2013/0159468 A1 · Computer implemented method, computer system, electronic interface, mobile computing device and computer readable medium > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2013/0159468 A1 - Document ID: US20130159468A1 - Status: Published application - Kind: A1 - Application number: 13/331,824 - Filed: 2011-12-20 - Published: 2013-06-20 - Earliest claimed: 2011-12-20 - Assignees: Sap SE - Inventors: Stefan Kusterer; Ralf Handl; G. Kalyani; Reiner P. Hammerich; Martin Zurmuehl; Hendrik C. R. Lock - Web page: https://patentgrep.com/patent/US20130159468A1 ## CPC - G06F 15/16: Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs {(coordinating program control therefor G06F9/52; in regulating and control system G05B)} - G06F 9/00: Arrangements for program control, e.g. control units (program control for peripheral devices G06F13/10) - H04L 67/2895: Intermediate processing functionally located close to the data provider application, e.g. reverse proxies - H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) - H04W 4/18: Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract The present disclosure describes computer implemented methods, computer systems, electronic interfaces, mobile computing devices, and computer readable mediums for processing a request from a mobile application residing on a mobile computing device. One method may include receiving the request for data from the mobile application residing on the mobile device at an interface. The method may further include determining an interface service to be executed and executing the interface service. The method can then obtain, at the interface, from the execution of the interface service, a consumption model comprising one or more data models and associated data. The method may further include translating the consumption model and the associated data into an open source protocol, and sending a response from the interface including the translated consumption model and the associated data to the mobile application on the mobile device. ## Claims ### Claim 1 A computer implemented method for processing a request from a mobile application residing on a mobile computing device, comprising: receiving, at an interface, the request for data from the mobile application residing on the mobile computing device; determining, at the interface, an interface service to be executed; executing, at the interface, the interface service; obtaining, at the interface, from the execution of the interface service, a consumption model comprising one or more data models and associated data; translating, at the interface, the consumption model and the associated data into an open source protocol; and sending, from the interface, a response including the translated consumption model and the associated data to the mobile application on the mobile device. ### Claim 2 (depends on 1) The method of claim 1, wherein the interface is an OData Channel and the open source protocol is an OData protocol. ### Claim 3 (depends on 1) The method of claim 1, wherein the translated consumption model is exposed in OData at the interface. ### Claim 4 (depends on 1) The method of claim 1, wherein the request received from the mobile device is an HTTP request indicating the interface service to be executed. ### Claim 5 A computer system for processing a request from a mobile application residing on a mobile device, comprising: an interface operable to: receive the request for data from the mobile application residing on the mobile device; determine an interface service to be executed; execute the interface service; obtain a consumption model comprising one or more data models and associated data; translate the consumption model and the associated data into an open source protocol; and send a response including the translated consumption model and the associated data to the mobile application on the mobile device; a business application server, comprising: a model provider operable to determine the one or more data models associated with the interface service; a data adapter operable to determine the data associated with the one or more data models; and an interface integration component operable to generate the consumption model comprising the one or more data models and the associated data. ### Claim 6 (depends on 5) The system of claim 5, wherein the interface is an OData Channel and the open source protocol is an OData protocol. ### Claim 7 (depends on 5) The system of claim 5, wherein the translated consumption model is exposed in OData at the interface. ### Claim 8 (depends on 5) The system of claim 5, wherein the request received from the mobile device is an HTTP request indicating the interface service to be executed. ### Claim 9 (depends on 5) The system of claim 5, wherein the interface and the business application server communicate via remote function calls. ### Claim 10 (depends on 5) The system of claim 5, wherein the interface executes the interface service via a remote function call. ### Claim 11 (depends on 5) The system of claim 5, wherein the business application server sends the consumption model to the interface via a remote function call. ### Claim 12 An electronic interface operable to: receive a request for data from a mobile application residing on the mobile device; determine an interface service to be executed; execute the interface service; obtain a consumption model comprising one or more data models and associated data; translate the consumption model and the associated data into an open source protocol; and send a response including the translated consumption model and the associated data to the mobile application on the mobile device. ### Claim 13 (depends on 12) The interface according to claim 12, wherein the interface is operable to obtain the consumption model from a business application server, and wherein the interface is separate from the business application server. ### Claim 14 A mobile computing device, comprising: a mobile application performing the steps of: sending a request for data from the mobile application encoded in an open source protocol to a proprietary business application; obtaining from the business application a consumption model comprising one or more data models and associated data encoded in an open source protocol. ### Claim 15 (depends on 14) The mobile computing device of claim 14, wherein the request is an HTTP request encoded in OData. ### Claim 16 (depends on 14) The mobile computing device of claim 14, wherein the translated consumption model is encoded in OData. ### Claim 17 (depends on 14) The mobile computing device of claim 14, further comprising an OData client library enabling communications in OData. ### Claim 18 A non-transitory computer readable medium for processing a request from a mobile application residing on a mobile device, comprising computer executable instructions that, when executed, perform the steps of: receiving the request for data from the mobile application residing on the mobile device; determining an interface service to be executed; executing the interface service; obtaining from the execution of the interface service, a consumption model comprising one or more data models and associated data; translating the consumption model and the associated data into an open source protocol; and sending a response including the translated consumption model and the associated data to the mobile application on the mobile device.