# US 2012/0254042 A1 · Integrated Mobile/Server Applications

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

- Number: US 2012/0254042 A1
- Document ID: US20120254042A1
- Status: Published application
- Kind: A1
- Application number: 13/435,729
- Filed: 2012-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Google Inc.
- Inventors: Peter LUDEMANN
- Web page: https://patentgrep.com/patent/US20120254042A1

## CPC

- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04M 15/43: {Billing software details}
- H04M 15/61: {based on the service used}
- H04W 4/24: Accounting or billing
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Methods and systems for providing integrated mobile/server applications are provided. An application may be received at a server from a third party. A request for information may be received at the server from a user's device and a token that identifies a user on the user's device, wherein the request and the token were transmitted by the user's device. It may be determined, by the server, that the user is authorized to make a request of the application. A response to the request using the application may be generated using the application. Accounting may be performed by the server so that the user can be billed according to a billing preference of the third party.

## Claims

### Claim 1

A computer-implemented method, comprising:
receiving, by a server, an application from a third party;
receiving, by the server, a request for information from a user's device and a token that identifies a user on the user's device, wherein the request and the token were transmitted by the user's device;
determining, by the server, that the user is authorized to make a request of the application;
generating, by the server, a response to the request using the application using the application; and
performing, by the server, accounting according to an accounting preference of the third party associated with the application.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, farther comprising:
determining, by the server, an identity of the user based on the token.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein receiving comprises:
receiving, by the server, the request from a load balancing server, wherein the load balancing server is configured to choose to send the request to the server based on the load of the server.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein generating comprises:
interacting, by the server, with a server of the third party.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the token is generated based on at least one account of the user with a second application installed on the server.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the request was generated by a second application, wherein the second application was installed on the user's device by a marketplace server and wherein the token was generated by the marketplace server.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, further comprising:
installing the application on an application server.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, wherein the determining comprises:
determining that the user is authorized to make requests of the application based on authorization information of the third party.

### Claim 9 (depends on 8)

The computer-implemented method of claim 8, further comprising:
storing the authorization information in a locally-accessible database.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the request was generated by an application installed on the user's device, wherein the application installed on the user's device is an HTML application.

### Claim 11

A server, comprising:
an authorization engine configured to determine whether a user is authorized to make requests for information of an application installed on the server responsive to a received request generated by a device of the user, wherein the request was transmitted by the user's device;
an application engine configured to execute the application to generate a response to the request responsive to a determination that the user is authorized to make requests of the application; and
an accounting engine configured to bill the user according to a preference of the third party.

### Claim 12 (depends on 11)

The server of claim 11, further comprising:
an authentication engine configured to determine an identity of the user based on a token received along with the request.

### Claim 13 (depends on 11)

The server of claim 11, wherein the application engine is configured to interact with a server of the third party to generate the response to the request.

### Claim 14 (depends on 11)

The server of claim 11, wherein the server is configured such that the third party can install the application on the application engine.

### Claim 15 (depends on 11)

The server of claim 11, wherein the server is configured to receive the request from a load balancing server and wherein the load balancing server is configured to choose to send the request to one of many servers based on the load on the server.

### Claim 16 (depends on 11)

The server of claim 11, wherein the request was generated by a second application, wherein the second application is installed on the user's device.

### Claim 17 (depends on 11)

The server of claim 11, wherein the accounting engine is configured to interact with the third party to set the preference.

### Claim 18 (depends on 11)

The server of claim 11, wherein the application engine is coupled to a database configured to store a list of registered users authorized to make requests of the application, and can store additional per-user information in the database.

### Claim 19 (depends on 18)

The server of claim 18, wherein the authorization engine is configured to query the database with information identifying the user.

### Claim 20 (depends on 12)

The server of claim 12, wherein the token is generated based on an account that the user has with a second application installed on the server.
