SYSTEMS AND METHODS FOR MANAGING APPLICATIONS

• US 20120255007A1
• Filed: 03/22/2012
• Published: 10/04/2012
• Est. Priority Date: 03/28/2011
• Status: Abandoned Application

• Current Assignee: HTC Corporation
• Original Assignee: HTC Corporation
• Inventors: YANG, Ju-Ting, Tseng, Yin-Yeh
• Application Number:
  US13/427,552
• Publication Number:
  US 20120255007A1
• Time in Patent Office: Days
• US Class Current: 726/23
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 21/56 Computer malware detection or handling, e.g. anti-virus arrangements
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

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

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.

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

3. 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.

4. 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.

5. 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).

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.

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

8. 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.

9. 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.

10. 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).

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.

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

13. 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.

14. 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.

15. 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).

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.

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

18. 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.

19. 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.

20. 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.

21. 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.

22. 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.

23. 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.

24. 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).

25. 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.

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.

27. 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.

28. 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.

29. 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.

30. 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.