# US 2012/0255007 A1 · Systems and methods for managing applications

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

- Number: US 2012/0255007 A1
- Document ID: US20120255007A1
- Status: Published application
- Kind: A1
- Application number: 13/427,552
- Filed: 2012-03-22
- Published: 2012-10-04
- Earliest claimed: 2011-03-28
- Inventors: Ju-Ting YANG; Yin-Yeh Tseng
- Web page: https://patentgrep.com/patent/US20120255007A1

## CPC

- G06F 8/61: Installation
- G06F 9/46: Multiprogramming arrangements
- G06F 21/55: Detecting local intrusion or implementing counter-measures
- G06F 21/56: Computer malware detection or handling, e.g. anti-virus arrangements
- G06Q 10/10: Office automation; Time management
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A system for managing applications. The system includes a first device, a second device, a first interface and a second interface. The first device is responsible for exhibiting and providing the applications to one or more user(s). The second device is responsible for managing the applications which are uploaded by one or more developer(s) who have developed the applications. The first interface is provided for the second device to submit the applications to the first device. The second interface is provided for the first device to transmit at least a report message to the second device.

## Claims

### Claim 1

A system for managing a plurality of applications, comprising:
a first device, for exhibiting and providing the applications to one or more user(s);
a second device, for managing the applications which are uploaded by one or more developer(s) who have developed the applications;
a first interface, provided for the second device to submit the applications to the first device; and
a second interface, provided for the first device to transmit at least a report message to the second device.

### Claim 2 (depends on 1)

The system as claimed in claim 1, wherein the report message comprises a sale report of the applications.

### Claim 3 (depends on 1)

The system as claimed in claim 1, wherein the report message comprises a malicious report of the applications for reporting which application(s) is/are malicious application(s) and has/have to be removed or deleted from the first device.

### Claim 4 (depends on 1)

The system as claimed in claim 1, further comprising:
a third device, for facilitating the user(s) to browse and download the applications; and
a third interface, provided for the first device to transmit at least an update notification message to the third device, wherein the update notification message comprises update information of the applications.

### Claim 5 (depends on 1)

The system as claimed in claim 1, further comprising:
a fourth device, for providing a portal for the developer(s) to upload the applications; and
a fourth interface, provided for the second device to transmit at least a punishment notification message to the fourth device, wherein the punishment notification message comprises punishment information of the developer(s).

### Claim 6

A method for managing a plurality of applications, comprising:
transmitting the applications to a first device via a first interface by a second device, wherein the first device is responsible for exhibiting and providing the applications to one or more user(s) and the second device is responsible for managing the applications which are uploaded by one or more developer(s) who have developed the applications; and
transmitting a report message to the second device via a second interface by the first device,
wherein the report message comprises information regarding the applications, and
wherein the second interface defines a format of one or more message(s) to be transmitted from the first device to the second device.

### Claim 7 (depends on 6)

The method as claimed in claim 6, wherein the report message comprises a sale report of the applications.

### Claim 8 (depends on 6)

The method as claimed in claim 6, wherein the report message comprises a malicious report of the applications for reporting which application(s) is/are malicious application(s) and has/have to be removed or deleted from the first device.

### Claim 9 (depends on 6)

The method as claimed in claim 6, further comprising:
transmitting an update notification message to a third device via a third interface by the first device, wherein the third device is responsible for facilitating the user(s) to browse and download the applications and the update notification message comprises update information of the applications.

### Claim 10 (depends on 6)

The method as claimed in claim 6, further comprising:
transmitting a punishment notification message to a fourth device via a fourth interface by the second device, wherein the fourth device is responsible for providing a portal for the developer(s) to upload the applications and the punishment notification message comprises punishment information of the developer(s).

### Claim 11

A method for managing a plurality of applications, comprising:
providing a first interface between a first device and a second device, wherein the first device is responsible for exhibiting and providing the applications received from the second device to one or more user(s) and the second device is responsible for managing the applications which are uploaded by one or more developer(s) who have developed the applications; and
transmitting a report message from the first device to the second device via the first interface, wherein the report message comprises information regarding the applications.

### Claim 12 (depends on 11)

The method as claimed in claim 11, wherein the report message comprises a sale report of the applications.

### Claim 13 (depends on 11)

The method as claimed in claim 11, wherein the report message comprises a malicious report of the applications for reporting which application(s) is/are malicious application(s) and has/have to be removed or deleted from the first device.

### Claim 14 (depends on 11)

The method as claimed in claim 11, further comprising:
providing a second interface between the first device and a third device, wherein the third device is responsible for facilitating the user(s) to browse and download the applications; and
transmitting an update notification message from the first device to the third device via the second interface, wherein the update notification message comprises update information of the applications.

### Claim 15 (depends on 11)

The method as claimed in claim 11, further comprising:
providing a third interface between the second device and a fourth device, wherein the fourth device is responsible for providing a portal for the developer(s) to upload the applications; and
transmitting a punishment notification message from the second device to the fourth device via the third interface, wherein the punishment notification message comprises punishment information of the developer(s).

### Claim 16

A method for notifying a first device of a status of an application, comprising:
transmitting an application state transition notification message from a second device to the first device when a state transition of the application has occurred, wherein the application state transition notification message comprises information regarding at least a current state of the application and a reason of the state transition; and
transmitting an application state transition response message from the first device to the second device in response to the application state transition notification message.

### Claim 17 (depends on 16)

The method as claimed in claim 16, wherein the application state transition notification message further comprises information regarding a previous state of the application.

### Claim 18 (depends on 16)

The method as claimed in claim 16, wherein the first device is a storefront component in a Telco's Application Store (TAS) system, the second device is a developer support component in the TAS system, and the application state transition notification message is transmitted via a TAS-1 interface, and wherein the status of the application is maintained by the developer support component.

### Claim 19 (depends on 16)

The method as claimed in claim 16, wherein the first device is a developer support component in a Telco's Application Store (TAS) system, the second device is a storefront component in the TAS system, and the application state transition notification message is transmitted via a TAS-6 interface, and wherein the status of the application is maintained by the storefront component.

### Claim 20 (depends on 16)

The method as claimed in claim 16, wherein the application state transition notification message is transmitted when the current state of the application has transited from an online state to an offline state, and wherein in the online state, the application is able to be downloaded or purchased by a client while in the offline state, the application is unable to be downloaded or purchased by a client.

### Claim 21 (depends on 16)

The method as claimed in claim 16, wherein the application state transition notification message is transmitted when the current state of the application has transited from an online state to an end state, and wherein in the online state, the application is able to be downloaded or purchased by a client while in the end state, application is deleted or revoked.

### Claim 22 (depends on 19)

The method as claimed in claim 19, wherein the application state transition notification message is transmitted when the current state of the application has transited to an online state, and wherein in the online state, the application is able to be downloaded or purchased by a client.

### Claim 23 (depends on 19)

The method as claimed in claim 19, wherein the application state transition notification message is transmitted when the current state of the application has transited to an invalidated state, and wherein in the invalidated state, the application is invalidated.

### Claim 24 (depends on 16)

The method as claimed in claim 16, wherein the application state transition notification message comprises an identity field for indicating an identity of the second device, an application count filed for indicating a number of application which has encountered the state transition in an application list, and the application list field for listing identity(ies) of application(s) to be notified, description(s) of the state transition(s) and reason(s) of the state transition(s).

### Claim 25 (depends on 24)

The method as claimed in claim 24, wherein t he description of state transition is an integer to represent whether the current state of the application has transited from an online state to an offline state or from an online state to an end state, or an integer to represent whether the current state of the application has transited to an online state or an invalidated state.

### Claim 26

A method for notifying a first device of a status of an application, comprising:
transmitting an application status check request message from the first device to a second device; and
transmitting an application status check response message from the second device to the first device in response to the application status check request message, wherein the application status check response message comprises information regarding at least a current state of the application.

### Claim 27 (depends on 26)

The method as claimed in claim 26, wherein the first device is a developer's portal component in a Telco's Application Store (TAS) system, the second device is a developer support component in the TAS system, and the application status check request message is transmitted via a TAS-5 interface, and wherein the status of the application is maintained by the developer support component.

### Claim 28 (depends on 26)

The method as claimed in claim 26, wherein the application status check request message comprises a first identity field for indicating an identity of the first device and a second identity field for indicating an identity of the application to be checked.

### Claim 29 (depends on 26)

The method as claimed in claim 26, wherein the application status check response message comprises a status field for indicating the current state of the application and a reason field for indicating reason for the application not being able to transit to an online state.

### Claim 30 (depends on 29)

The method as claimed in claim 29, wherein the current state carried in the status field is selected from a group comprising a submitted state, an audited state, a tested state and the online state.
