STANDARDIZED METHOD AND SYSTEMS FOR PROVIDING CONFIGURABLE KEYPADS

• US 20090073126A1
• Filed: 06/16/2008
• Published: 03/19/2009
• Est. Priority Date: 07/16/2007
• Status: Abandoned Application

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: SRIVASTAVA, Aditya Narain
• Application Number:
  US12/139,823
• Publication Number:
  US 20090073126A1
• Time in Patent Office: Days
• US Class Current: 345/168
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 3/0238 Programmable keyboards key guide holders G06F3/0224
• CPC Class Codes: G06F 3/038 Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
• CPC Class Codes: G06F 3/041 Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A keypad protocol is provided as part of mobile device system software to serve as a standard interface between application software and keypads and other user-interfaces. The keypad protocol can provide a common set of interfaces and APIs to facilitate development of applications that are compatible with a wide variety of keypads, including keypads that may be developed after applications are fielded. Similarly the keypad protocol can provide a common set of data structures and interfaces for accepting key press event notifications from and providing configuration information to keypads made by a variety of manufacturers. The keypad protocol can inform applications of the keypads activated and connected to the mobile device and useable by the application. Applications can inform the keypad protocol of a keypad selected for use as well as configure how the selected keypad should interface with the application.

Claims

1. A method for interfacing a keypad with an application operating on a mobile device, comprising:

receiving a keypad configuration instruction from the application in a keypad protocol;

receiving a key press event signal in the keypad protocol;

determining a key value associated with the key press event using the received keypad configuration instruction in the keypad protocol; and

communicating the key value to the application.

2. The method of claim 1, further comprising storing the keypad configuration instruction in a keypad translation table, wherein the key value associated with the key press event is determined using the keypad translation table.

3. The method of claim 1, further comprising:

issuing a query from the keypad protocol to determine activated keypads connected to the mobile device;

storing a list of activated keypads connected to the mobile device;

informing the application of activated keypads connected to the mobile device; and

receiving in the keypad protocol a keypad selection from the application.

4. The method of claim 3, further comprising informing the application of keypad capabilities.

5. The method of claim 1, further comprising:

receiving in the keypad protocol a request for available keypads from the application;

informing the application of activated keypads connected to the mobile device in response to the request received from the application; and

receiving in the keypad protocol a keypad selection from the application.

6. The method of claim 5, wherein the request from available keypads is received from the application in form of an application program interface (API).

7. The method of claim 5, wherein the keypad selection is received from the application in form of an application program interface (API).

8. The method of claim 3, further comprising:

receiving in the keypad protocol a graphic from the application related to a key; and

configuring the selected keypad to display the received graphic file.

9. The method of claim 8, wherein the received graphic is a graphic file.

10. The method of claim 8, wherein the received graphic is a pointer to a graphic file stored in memory of the mobile device.

11. A mobile device, comprising:

a processor;

a keypad coupled to the processor; and

a memory coupled to the processor,

wherein the processor is configured with software instructions to perform steps comprising;

receiving a keypad configuration instruction from an application in a keypad protocol;

receiving a key press event signal in the keypad protocol;

determining a key value associated with the key press event using the received keypad configuration instruction in the keypad protocol; and

communicating the key value to the application.

12. The mobile device of claim 11, wherein the processor is configured with software instructions to perform steps further comprising storing the keypad configuration instruction in a keypad translation table, wherein the key value associated with the key press event is determined using the keypad translation table.

13. The mobile device of claim 11, wherein the processor is configured with software instructions to perform steps further comprising:

issuing a query from the keypad protocol to determine activated keypads connected to the mobile device;

storing a list of activated keypads connected to the mobile device;

informing the application of activated keypads connected to the mobile device; and

receiving in the keypad protocol a keypad selection from the application.

14. The mobile device of claim 13, wherein the processor is configured with software instructions to perform steps further comprising informing the application of keypad capabilities.

15. The mobile device of claim 13, wherein the processor is configured with software instructions to perform steps further comprising:

receiving in the keypad protocol a request for available keypads from the application;

informing the application of activated keypads connected to the mobile device in response to the request received from the application; and

receiving in the keypad protocol a keypad selection from the application.

16. The mobile device of claim 15, wherein the request from available keypads is received from the application in form of an application program interface (API).

17. The mobile device of claim 15, wherein the keypad selection is received from the application in form of an application program interface (API).

18. The mobile device of claim 13, wherein the processor is configured with software instructions to perform steps further comprising:

receiving in the keypad protocol a graphic from the application related to a key; and

configuring the keypad to display the received graphic file.

19. The mobile device of claim 18, wherein the received graphic is a graphic file.

20. The mobile device of claim 18, wherein the received graphic is a pointer to a graphic file stored in memory of the mobile device.

21. A tangible storage medium having stored thereon processor-executable software instructions configured to cause a processor of a mobile device to perform steps comprising:

receiving a keypad configuration instruction from an application in a keypad protocol;

receiving a key press event signal in the keypad protocol;

determining a key value associated with the key press event using the received keypad configuration instruction in the keypad protocol; and

communicating the key value to the application.

22. The tangible storage medium of claim 21, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps comprising storing the keypad configuration instruction in a keypad translation table, wherein the key value associated with the key press event is determined using the keypad translation table.

23. The tangible storage medium of claim 21, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps comprising:

issuing a query from the keypad protocol to determine activated keypads connected to the mobile device;

storing a list of activated keypads connected to the mobile device;

informing the application of activated keypads connected to the mobile device; and

receiving in the keypad protocol a keypad selection from the application.

24. The tangible storage medium of claim 23, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps comprising informing the application of keypad capabilities.

25. The tangible storage medium of claim 21, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps comprising:

receiving in the keypad protocol a request for available keypads from the application;

informing the application of activated keypads connected to the mobile device in response to the request received from the application; and

receiving in the keypad protocol a keypad selection from the application.

26. The tangible storage medium of claim 25, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps so that the request from available keypads is received from the application in form of an application program interface (API).

27. The tangible storage medium of claim 25, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps so that the keypad selection is received from the application in form of an application program interface (API).

28. The tangible storage medium of claim 23, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps comprising:

receiving in the keypad protocol a graphic from the application related to a key; and

configuring the selected keypad to display the received graphic file.

29. The tangible storage medium of claim 28, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps such that the received graphic is a graphic file.

30. The tangible storage medium of claim 28, wherein the tangible storage medium has processor-executable software instructions configured to cause a processor of a mobile device to perform further steps such that the received graphic is a pointer to a graphic file stored in memory of the mobile device.

31. A mobile device, comprising:

means for receiving a keypad configuration instruction from an application in a keypad protocol;

means for receiving a key press event signal in the keypad protocol;

means for determining a key value associated with the key press event using the received keypad configuration instruction in the keypad protocol; and

means for communicating the key value to the application.

32. The mobile device of claim 31, further comprising means for storing the keypad configuration instruction in a keypad translation table,

wherein the key value associated with the key press event is determined using the keypad translation table.

33. The mobile device of claim 31, further comprising:

means for issuing a query from the keypad protocol to determine activated keypads connected to the mobile device;

means for storing a list of activated keypads connected to the mobile device;

means for informing the application of activated keypads connected to the mobile device; and

means for receiving in the keypad protocol a keypad selection from the application.

34. The mobile device of claim 33, further comprising means for informing the application of keypad capabilities.

35. The mobile device of claim 31, further comprising:

means for receiving in the keypad protocol a request for available keypads from the application;

means for informing the application of activated keypads connected to the mobile device in response to the request received from the application; and

means for receiving in the keypad protocol a keypad selection from the application.

36. The mobile device of claim 35, wherein the request from available keypads is received from the application in form of an application program interface (API).

37. The mobile device of claim 35, wherein the keypad selection is received from the application in form of an application program interface (API).

38. The mobile device of claim 33, further comprising:

means for receiving in the keypad protocol a graphic from the application related to a key; and

means for configuring the selected keypad to display the received graphic file.

39. The mobile device of claim 38, wherein the received graphic is a graphic file.

40. The mobile device of claim 38, wherein the received graphic is a pointer to a graphic file stored in memory of the mobile device.