Method and system for handling events in an application framework for a wireless device

• US 20050286457A1
• Filed: 08/25/2004
• Published: 12/29/2005
• Est. Priority Date: 06/23/2004
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Foster, Derek John, Yoshida, Lori, Zhang, Richard
• Granted Patent: US 7,395,082 B2
• Time in Patent Office: Days
• US Class Current: 370/315
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

Methods and systems for application framework development for wireless devices are provided herein. Aspects of the method may include acquiring an MMI event from an MMI event queue within the MMI wireless framework. An identity of the acquired MMI event may be determined and the acquired MMI event may be dispatched to an event handler based on the determined identity of the acquired event. If the acquired MMI event comprises a timing event, the acquired MMI event may be dispatched to an MMI event owner within the MMI wireless framework. If the acquired MMI event comprises a keypad event, the acquired MMI event may be dispatched to a currently active MMI view within the MMI wireless framework. If the acquired MMI event comprises an addressed event, the acquired MMI event may be dispatched to a destination handler within the MMI wireless framework.

Claims

1. A method for managing a plurality of events within a man machine interface (MMI) application framework, the method comprising:

acquiring an MMI event from an MMI event queue within the MMI wireless framework;

determining an identity of said acquired MMI event; and

dispatching said acquired MMI event to an event handler based on said determined identity of said acquired event.

2. The method according to claim 1, further comprising:

if said acquired MMI event comprises a timing event, dispatching said acquired MMI event to an MMI event owner within the MMI wireless framework;

if said acquired MMI event comprises a keypad event, dispatching said acquired MMI event to a currently active MMI view within the MMI wireless framework;

if said acquired MMI event comprises an addressed event, dispatching said acquired MMI event to a destination handler within the MMI wireless framework;

if said acquired MMI event comprises a platform event, dispatching said acquired MMI event to at least one registered handler within the MMI wireless framework;

if said acquired MMI event comprises an unaddressed application specific event, dispatching said acquired MMI event to an application manager within the MMI wireless framework; and

if said acquired MMI event comprises an unaddressed non-application specific event, dispatching said acquired MMI event to a current target handler within the wireless framework.

3. The method according to claim 2, further comprising terminating an event timer upon receipt of said timing event by said MMI event owner.

4. The method according to claim 2, further comprising identifying a depressed key by said currently active MMI view upon receipt of said keypad event.

5. The method according to claim 2, further comprising dispatching said addressed event to at least one application, said at least one application comprising a phonebook application, a call control application, or a messaging application.

6. The method according to claim 2, wherein said platform event comprises a platform API interrupt message.

7. The method according to claim 2, further comprising delegating said unaddressed application specific event to a handling application by said application manager.

8. The method according to claim 2, further comprising matching said unaddressed non-application specific event with a message within a message chain of said current target handler.

9. The method according to claim 2, further comprising, if said acquired MMI event comprises a platform event, registering at-least one handler for acquiring said MMI event.

10. The method according to claim 2, further comprising deriving at least one of the plurality of events from a message handling class within the MMI application framework.

11. The method according to claim 2, further comprising deleting said acquired MMI event from said MMI event queue after dispatching said acquired MMI event.

12. A machine-readable storage having stored thereon, a computer program having at least one code section for managing a plurality of events within a man machine interface (MMI) application framework, the at least one code section being executable by a machine for causing the machine to perform steps comprising:

acquiring an MMI event from an MMI event queue within the MMI wireless framework;

determining an identity of said acquired MMI event; and

dispatching said acquired MMI event to an event handler based on said determined identity of said acquired event.

13. The machine-readable storage according to claim 12, further comprising code for:

if said acquired MMI event comprises a timing event, dispatching said acquired MMI event to an MMI event owner within the MMI wireless framework;

if said acquired MMI event comprises a keypad event, dispatching said acquired MMI event to a currently active MMI view within the MMI wireless framework;

if said acquired MMI event comprises an addressed event, dispatching said acquired MMI event to a destination handler within the MMI wireless framework;

if said acquired MMI event comprises a platform event, dispatching said acquired MMI event to at least one registered handler within the MMI wireless framework;

if said acquired MMI event comprises an unaddressed application specific event, dispatching said acquired MMI event to an application manager within the MMI wireless framework; and

if said acquired MMI event comprises an unaddressed non-application specific event, dispatching said acquired MMI event to a current target handler within the wireless framework.

14. The machine-readable storage according to claim 13, further comprising code for terminating an event timer upon receipt of said timing event by said MMI event owner.

15. The machine-readable storage according to claim 13, further comprising code for identifying a depressed key by said currently active MMI view upon receipt of said keypad event.

16. The machine-readable storage according to claim 13, further comprising dispatching said addressed event to at least one application, said at least one application comprising a phonebook application, a call control application, or a messaging application.

17. The machine-readable storage according to claim 13, wherein said platform event comprises a platform API interrupt message.

18. The machine-readable storage according to claim 13, further comprising code for delegating said unaddressed application specific event to a handling application by said-application manager.

19. The machine-readable storage according to claim 13, further comprising code for matching said unaddressed non-application specific event with a message within a message chain of said current target handler.

20. The machine-readable storage according to claim 13, further comprising code for, if said acquired MMI event comprises a platform event, registering at least one handler for acquiring said MMI event.

21. The machine-readable storage according to claim 13, further comprising code for deriving at least one of the plurality of events from a message handling class within the MMI application framework.

22. The machine-readable storage according to claim 13, further comprising code for deleting said acquired MMI event from said MMI event queue after dispatching said acquired MMI event.

23. A system for managing a plurality of events within a man machine interface (MMI) application framework, the system comprising:

an MMI event queue from which an MMI event is acquired within the MMI wireless framework; and

an event handler to which said acquired MMI event is dispatched based on a determined identity of said acquired MMI event.

24. The system according to claim 23, further comprising:

an MMI event owner within the MMI wireless framework to which said MMI event is dispatched if said acquired MMI event comprises a timing event;

a currently active MMI view within the MMI wireless framework to which said MMI event is dispatched if said MMI event comprises a keypad event;

a destination handler within the MMI wireless framework to which said MMI event is dispatched if said MMI event comprises an addressed event;

at least one registered handler within the MMI wireless framework to which said MMI event is dispatched if said MMI event comprises a platform event;

an application manager within the MMI wireless framework to which said MMI event is dispatched if said MMI event comprises an unaddressed application specific event; and

a current target handler within the MMI wireless framework to which said MMI event is dispatched if said MMI event comprises an unaddressed non-application specific application specific event.

25. The system according to claim 24, further comprising an event timer that is terminated upon receipt of said timing event by said MMI event owner.

26. The system according to claim 24, wherein said currently active MMI view identifies a depressed key upon receipt of said keypad event.

27. The system according to claim 24, wherein said addressed event is dispatched to at least one application, said at least one application comprising a phonebook application, a call control application, or a messaging application.

28. The system according to claim 24, wherein said platform event comprises a platform API interrupt message.

29. The system according to claim 24, wherein said unaddressed application specific event is delegated to a handling application by said application manager.

30. The system according to claim 24, wherein said unaddressed non-application specific event is matched with a message within a message chain of said current target handler.

31. The system according to claim 24, wherein at least one handler is registered for acquiring said MMI event, if said acquired MMI event comprises a platform event.

32. The system according to claim 24, wherein said acquired MMI event is derived from a message handling class within the MMI application framework.

33. The system according to claim 24, wherein said acquired MMI event is deleted from said MMI event queue after dispatching said acquired MMI event.