Method and system for an application framework for a wireless device

• US 20050288001A1
• Filed: 08/25/2004
• Published: 12/29/2005
• Est. Priority Date: 06/23/2004
• Status: Abandoned Application

• Current Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Original Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Inventors: Foster, Derek John, Yoshida, Lori
• Application Number:
  US10/926,255
• Publication Number:
  US 20050288001A1
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 80/12 Application layer protocols, e.g. WAP [Wireless Application Protocol]

Abstract

Methods and systems for managing applications by an application manager within a man machine interface (MMI) application framework are disclosed. Aspects of the method may include creating an active application context upon launching a first application by the application manager. The active application context may be transitioned into a suspended application context upon suspending the first application by the application manager. The suspended application context may be stored in an application manager context stack. The stored suspended application context may be acquired from the application manager context stack upon receipt of an exit message by the application manager. The application manager context stack may comprise a last-in-first-out (LIFO) context stack. The first application associated with said suspended application context may be reactivated upon removal of the suspended application context from the application manager context stack.

Claims

1. A method for managing applications within a MMI application framework, the method comprising:

creating an active application context upon launching a first application by an application manager;

transitioning said active application context into a suspended application context upon suspending said first application by said application manager;

storing said suspended application context in an application manager context stack; and

acquiring said stored suspended application context from said application manager context stack upon receipt of an exit message by said application manager.

2. The method of claim 1, wherein said application manager context stack comprises a last-in-first-out (LIFO) context stack.

3. The method of claim 1, further comprising reactivating said first application associated with said suspended application context upon removal of said suspended application context from said application manager context stack.

4. The method of claim 1, further comprising restoring state information associated with said first application prior to resuming said first application.

5. The method of claim 1, wherein said exit message is generated upon termination of a currently active application.

6. The method of claim 1, further comprising storing said active context and said suspended context associated with said first application by said application manager.

7. The method of claim 1, further comprising assigning a context identifier to said first application by said application manager upon activation of said first application.

8. The method of claim 1, further comprising assigning a launch identifier to said first application upon activation of said first application.

9. The method of claim 8, further comprising generating a service request by said first application to another application utilizing said assigned launch identifier.

10. The method of claim 1, further comprising activating said first application upon receiving a service request from another application by said first application.

11. The method of claim 1, further comprising activating said first application upon handling an external system event by said first application.

12. A machine-readable storage having stored thereon, a computer program having at least a code section for managing applications within a MMI application framework, the at least a code section being executable by a machine to perform steps comprising:

creating an active application context upon launching a first application by an application manager;

transitioning said active application context into a suspended application context upon suspending said first application by said application manager;

storing said suspended application context in an application manager context stack; and

acquiring said stored suspended application context from said application manager context stack upon receipt of an exit message by said application manager.

13. The machine-readable storage of claim 12, wherein said application manager context stack comprises a last-in-first-out (LIFO) context stack.

14. The machine-readable storage of claim 12, further comprising code for reactivating said first application associated with said suspended application context upon removal of said suspended application context from said application manager context stack.

15. The machine-readable storage of claim 12, further comprising code for restoring state information associated with said first application prior to resuming said first application.

16. The machine-readable storage of claim 12, wherein said exit message is generated upon termination of a currently active application.

17. The machine-readable storage of claim 12, further comprising code for storing said active context and said suspended context associated with said first application by said application manager.

18. The machine-readable storage of claim 12, further comprising code for assigning a context identifier to said first application by said application manager upon activation of said first application.

19. The machine-readable storage of claim 12, further comprising code for assigning a launch identifier to said first application upon activation of said first application.

20. The machine-readable storage of claim 19, further comprising code for generating a service request by said first application to another application utilizing said assigned launch identifier.

21. The machine-readable storage of claim 12, further comprising code for activating said first application upon receiving a service request from another application by said first application.

22. The machine-readable storage of claim 12, further comprising code for activating said first application upon handling an external system event by said first application.

23. A system for managing applications within a MMI application framework, the system comprising:

an application manager;

an active application context created upon launching a first application by said application manager, wherein said active application context transitions to a suspended application context upon suspending said first application by said application manager;

an application manager context stack that stores said suspended application context; and

said application manager acquires said stored suspended application context from said application manager context stack upon receipt of an exit message.

24. The system of claim 23, wherein said application manager context stack comprises a last-in-first-out (LIFO) context stack.

25. The system of claim 23, wherein said first application is reactivated with said suspended application context upon removal of said suspended application context from said application manager context stack.

26. The system of claim 23, wherein state information associated with said first application is restored prior to resuming said first application.

27. The system of claim 23, wherein said exit message is generated upon termination of a currently active application.

28. The system of claim 23, wherein said active context and said suspended context associated with said first application are stored by said application manager.

29. The system of claim 23, further comprising a context identifier that is assigned to said first application by said application manager upon activation of said first application.

30. The system of claim 23, further comprising a launch identifier that is assigned to said first application upon activation of said first application.

31. The system of claim 30, further comprising a service request that is generated by said first application to another application utilizing said assigned launch identifier.

32. The system of claim 23, wherein said first application is activated upon receipt of a service request from another application by said first application.

33. The system of claim 23, wherein said first application is activated upon handling an external system event by said first application.