# US 2012/0255008 A1 · Method of Handling Malicious Application in Telco's Application Store System and Related Communication Device

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

- Number: US 2012/0255008 A1
- Document ID: US20120255008A1
- Status: Published application
- Kind: A1
- Application number: 13/433,291
- Filed: 2012-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Inventors: Ju-Ting Yang; Yin-Yeh Tseng
- Web page: https://patentgrep.com/patent/US20120255008A1

## CPC

- G06Q 10/00: Administration; Management
- H04L 63/14: {for detecting or protecting against malicious traffic}
- 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)

## Abstract

A method of handling a malicious application for a client of a service system is disclosed. The method comprises transmitting a malicious application report message to a storefront of the service system when detecting a malicious application, for reporting the malicious application to the storefront; and receiving a malicious application response message in response to the malicious application report message, wherein the malicious application response message is transmitted by the storefront.

## Claims

### Claim 1

A method of handling a malicious application, for a client of a service system, the method comprising:
transmitting a malicious application report message to a storefront of the service system when detecting a malicious application, for reporting the malicious application to the storefront; and
receiving a malicious application response message in response to the malicious application report message, wherein the malicious application response message is transmitted by the storefront.

### Claim 2 (depends on 1)

The method of claim 1, wherein the malicious application report message comprises at least one of an identification of the client, an identification of the malicious application, a comment and a reporting time.

### Claim 3 (depends on 2)

The method of claim 2, wherein the malicious application report message comprises the identification of the client, the identification of the malicious application, and the comment.

### Claim 4 (depends on 3)

The method of claim 3, wherein the comment comprises a cause or a suggestion for transmitting the malicious application report message.

### Claim 5 (depends on 1)

The method of claim 1, wherein the malicious application response message comprises a result.

### Claim 6 (depends on 5)

The method of claim 5, wherein the result comprises information of whether the storefront successfully receives the malicious application report message.

### Claim 7 (depends on 1)

The method of claim 1, wherein the service system is a Telco's Application Store (TAS) system developed by Open Mobile Alliance (OMA).

### Claim 8 (depends on 7)

The method of claim 7, wherein the client transmits the malicious application report message to the storefront via a TAS-2 interface, and receives the malicious application response message transmitted by the storefront via the TAS-2 interface.

### Claim 9

A method of handling at least one malicious application, for a storefront of a service system, the service system comprising a client, the storefront and a developer support, the method comprising:
transmitting a malicious application notification message to the developer support when the at least one malicious application reported by the client is stored at the storefront, for reporting the at least one malicious application to the developer support; and
receiving a malicious application notification response message in response to the malicious application notification message, wherein the malicious application notification response message is transmitted by the developer support.

### Claim 10 (depends on 9)

The method of claim 9, wherein the malicious application notification message comprises the number of the at least one malicious application, at least one identification of the at least one malicious application and a comment.

### Claim 11 (depends on 10)

The method of claim 10, wherein the comment comprises a cause or a suggestion for transmitting the malicious application notification message.

### Claim 12 (depends on 9)

The method of claim 9, wherein the malicious application notification response message comprises a result.

### Claim 13 (depends on 12)

The method of claim 12, wherein the result comprises information of whether the developer support successfully receives the malicious application notification message.

### Claim 14 (depends on 9)

The method of claim 9, wherein the service system is a Telco's Application Store (TAS) system developed by Open Mobile Alliance (OMA).

### Claim 15 (depends on 14)

The method of claim 14, wherein the storefront transmits the malicious application notification message to the developer support via a TAS-6 interface, and receives the malicious application notification response message transmitted by the developer support via the TAS-6 interface.
