1. Field of the Invention
This invention relates generally to the field of keyboard user interfaces. In particular, the invention provides a multifunctional keyboard for a mobile communication device and method of operating the same.
2. Description of the Related Art
Advances in communication technology have created a convergence between the fields of data and telephony communications. Traditional communication devices, however, typically include two separate interfaces; one for telephony communication, and one for data communication. Other known communication devices utilize the limited character mapping available on a typical telephone keypad to perform data entry functions. For instance, current telephone keypads map keys to characters on a one-to-many basis: 12 keys (1, 2, 3, 4, 5, 6, 7, 8, 9,*, 0, #) correspond to 26 characters (ABC, DEF, GHI, JKL, MNO, PQRS, TUV, WXYZ). In addition, most such telephone keypads do not include many of the characters from the American Standard Code for Information Interchange (ASCII) character code. In other known communication devices, including many cellular phones, data may be entered with a typical telephone keypad by repeatedly pressing a key to cycle through a number of associated character codes. For instance, repeatedly pressing the keypad key “2” on a typical cellular phone may cycle through the characters A, B, C, a, b, c, and 2.
A multifunctional keyboard for a mobile communication device includes a keyboard, a processor and a keyboard mode control software module. The keyboard has a plurality of letter keys, wherein each letter key is configured to generate a keyboard output signal. The processor is coupled to the keyboard and is configured to convert each keyboard output signal generated by the letter keys into a character code and/or a telephony tone signal. The keyboard mode control software module operates on the processor, and controls whether the processor converts the keyboard output signals from the letter keys into character codes or telephony tone signals.
a and 3b illustrate an additional exemplary multifunctional keyboard for a communication device in which a plurality of character entry keys can function as either letter entry keys or number entry keys;
a is a top view of an additional mobile communication device utilizing a multifunctional keyboard;
b is a side view of the additional mobile communication device shown in
Referring now to the drawing figures,
The multifunctional keyboard 10 is multifunctional in the sense that it operates in at least two modes: a telephony mode and a data mode. In the telephony mode, a key 12 pressed on the multifunctional keyboard results in a telephony tone signal for communicating with a voice communication network. The telephony tone signal may, for example, be a Dual Tone Multi Frequency (DTMF) signal commonly used for dialing a phone number in voice communication networks. In the data mode, pressing the same key 12 on the multifunctional keyboard 10 will result in the generation of a character code, such as an American Standard Code for Information Interchange (ASCII) character code.
In a preferred embodiment, the multifunctional keyboard 10 may also operate in a joint mode. In the joint mode of operation, depressing keys on the multifunctional keyboard 10 results in the simultaneous generation of both telephony tone signals and character codes. For example, pushing the Q key may result in both an ASCII code for the letter Q and a DTMF signal representing the number seven (7).
a and 3b illustrate an additional exemplary multifunctional keyboard 30, 31 for a communication device in which a plurality of character entry keys can function as either letter entry keys 32 or number entry keys 35. Similar to the multifunctional keyboards 10, 20 described above with reference to
Preferably, the character entry keys that function as both number entry and letter entry keys, depending upon the entry mode, have both a number and a letter printed on the key. For example, the “Q” key shown in
In an alternative embodiment, the multifunctional keyboard 30, 31 may be provided in conjunction with a displayed software user interface. For instance, the multifunctional keyboard 30, 31 may by represented on a display, such as a liquid crystal display (“LCD”). In this embodiment, touching the LCD within the boundaries of a drawn key representation is equivalent to pressing a key on the keyboard 30, 31. In addition, an LCD embodiment of the multifunctional keyboard 30, 31 may include a function in which the symbols displayed on each drawn key change with the operational mode to emphasize the particular telephony signal and/or character code to be generated by each key.
a is a top view of an additional mobile communication device 40A utilizing a multifunctional keyboard 30. The communication device 40A preferably includes a speaker 46A and a microphone 48A fixedly mounted on the device. When positioned near the device user's head, the speaker 46A and the microphone 48A may, for example, be used to establish a voice communication though the communication device 40A.
b is a side view 42A of the additional mobile communication device 40A shown in
The processor 56 receives keyboard output signals from the multifunctional keyboard 51 and converts these output signals into telephony tone signals, character codes or both. The mode of operation (data, telephony or joint) for the multifunctional keyboard 51 is preferably determined by the keyboard mode control software module 54 based on either the current requirements of the device 50, a selection by the user of the device 50, or possibly based on some other triggering event. The keyboard mode control software 54 may, for example, set the device 50 to a particular keyboard mode when a software application is executed on the device 50 and possibly when a particular operation is executed by the software application. For instance, if an address book application is executed, the keyboard mode control software 54 will preferably automatically set the multifunctional keyboard 51 to a preferred mode. When entering or editing an address book entry, data mode is the preferred mode for editing or entering a name, email address, or street address field, whereas joint mode is the preferred mode for editing or entering a telephone number field. Conversely, when retrieving an address book entry, data mode is the preferred mode for retrieving a name, email address, or street address, whereas either telephony mode, joint mode or data mode may be the preferred mode for retrieving a telephone number depending upon the purpose for which it is being retrieved. For instance, if a telephone number is retrieved from an address book in order to initiate a voice communication, the number will preferably be retrieved in telephony or joint mode.
The configuration store 61 and the service store 63 located in the memory device 62 are preferably used by the keyboard mode control software 54 to determine which operational mode (data, telephony or joint) is required for a particular application. In a preferred embodiment, however, the operational mode of the keyboard 51 may also be selected or overridden by a user of the mobile device 50. For instance, with reference to
Similarly, the letter entry or number entry modes for the keyboard embodiment 30, 31 shown in
Referring again to
The tone signal generation circuitry 52 may be used by the processor 56 to generate the telephony tone signals while the multifunctional keyboard 51 is in telephony or joint mode. In an alternative embodiment, however, digital telephony tone signals may be generated directly by the processor 56, or by a digital signal processor. In addition to telephony tone signals, the tone signal generation circuitry 52 may also generate audible tones preferably at the option of the communication device user. The audible tones may be used, for example, to notify the user when a key is pressed on the multifunctional keyboard 51. In alternative embodiments, the tone signal generator may generate distinctive tones when a telephony tone signal or character code is generated.
In addition to the components and software relating to the multifunctional keyboard 51, the main module 53 also preferably includes a pair of antennas 58, 60 (although a single antenna structure could be used), a memory device 62, an LCD display 64, at least one rechargeable battery 66, a long-range RF transceiver 68, one or more short-range RF transceivers 70, a power supply and recharging circuit 72, a cradle interface circuit 74, and an auxiliary input device such as a thumbwheel 76. The main module 53 may also include a pressure-sensitive writing tablet. Operationally, the long-range RF transceiver 68 is used to send and receive information from a long-range wireless network, and the one or more short-range RF transceivers 60 are used to send and receive information from the ear bud module 55, and possibly from other local devices such as an RF interface cradle, or a local printer coupled to a LAN, or other types of printing or display devices.
The ear bud module 55 is preferably an RF-enabled ear-piece that may be connected to (both mechanically and electrically) the main module 53 as described above. The ear bud module 55 preferably includes a microphone and a speaker 78, a short-range wireless transceiver 80, an antenna 82, a rechargeable battery 84, and possibly an integral processor 86. Operationally, the short-range wireless transceiver 80 is used to establish an RF link between the ear bud module 55 and the main module 53.
Once a mode change has been triggered in step 94, the type of service (data, telephony or joint) required by the device 50 is determined in steps 96 and 100. The required service may be determined, for example, by accessing the service store 63 locally maintained in a memory location 62 on the device 50. The service store 63 preferably includes a log indicating the type of service required by each software application on the device 50 and also preferably includes a default service. For the purposes of the illustration shown in
In step 96, the system determines whether the software application currently operating on the device (or other triggering event) requires the multifunctional keyboard 51 to operate in joint mode. If so, then the multifunctional keyboard 51 is set to joint mode in step 98. Otherwise, the device 50 determines whether telephony mode is required in step 100. If the current software application (or other triggering event) requires telephony mode, then the keyboard 51 is set to telephony mode in step 102. If neither joint mode nor telephony mode are required, however, then the multifunctional keyboard 51 is set to data mode, its default mode of operation, in step 104. The modes of operation are detailed below with reference to
While the multifunctional keyboard 51 is in a particular operational mode, an asynchronous mode change may preferably be initiated upon the receipt of an additional trigger. This type of mode change is asynchronous in the sense that the change may preferably be initiated at any point during the operational modes described below with reference to
In a preferred embodiment, more than one application may be running on the device 50 at the same time, possibly requiring concurrent operation of more than one keyboard mode. For instance, if several applications are executing on the device 51, one application may be in the foreground (the active application) while the other applications are in the background (the idle applications). In this instance, the multifunctional keyboard 51 will preferably operate in the mode associated with the foreground application. Then, as the device user (or the device itself) switches from the foreground application to an idle application, an asynchronous trigger is preferably generated to change keyboard modes. Preferably, before the device 50 switches from one application and associated keyboard mode to another, the current mode associated with the foreground application is stored in the service store 63. Then, when the idle application returns to the foreground and becomes active, the stored keyboard mode associated with the application is detected from the service store 63.
In step 120, the device 50 generates a character code and/or telephony tone signal corresponding to the key pressed by the user and a corresponding keyboard output signal from the multifunctional keyboard 51. As described above, the signal generated in step 120 depends upon the operational mode of the multifunctional keyboard 51. If the multifunctional keyboard 51 is in joint mode, then the system 50 generates both a character code and a telephony tone signal in step 120. If the multifunctional keyboard 51 is in telephony mode, then the system 50 generates a telephony tone signal. If the multifunctional keyboard 51 is in data mode, then a character code is generated. Once the appropriate character and/or telephony tone signal has been generated in step 120, the system 50 determines whether the current application or other triggering event requiring the current keyboard mode is complete in step 122. If the application is complete, then the system exits its current keyboard mode in step 124 and returns to an idle state. Otherwise, the system 50 remains in the current mode and awaits another keystroke at step 114. As was described above with reference to
In addition to the embodiments described above with reference to
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art.
This application is a continuation of the application titled “Multifunctional Keyboard For A Mobile Communication Device And Method Of Operating The Same,” application Ser. No. 12/607,468, filed Oct. 28, 2009, which in turn is a continuation of the application titled, “Multifunctional Keyboard For A Mobile Communication Device And Method Of Operating The Same,” application Ser. No. 10/004,001, filed Nov. 1, 2001, now U.S. Pat. No. 7,634,080 issued Dec. 15, 2009, which is related to the following prior provisional application: “Apparatus And Method For Telephony Tone Signals and Character Codes Generation For QWERTY Keyboards Or The Like,” U.S. Provisional Application No. 60/246,321, filed Nov. 7, 2000. These prior applications, including the entire written description and drawing figures, are hereby incorporated into the present application by reference. This application is further related to application titled “Multifunctional Keyboard For A Mobile Communication Device And Method Of Operating The Same,” application Ser. No. 12/908,311, filed Oct. 20, 2010 and to application titled “Multifunctional Keyboard For A Mobile Communication Device And Method Of Operating The Same,” application Ser. No. 12/908,328 filed Oct. 20, 2010.
Number | Name | Date | Kind |
---|---|---|---|
4430639 | Bennett et al. | Feb 1984 | A |
4503288 | Kessler | Mar 1985 | A |
D278341 | Scheid | Apr 1985 | S |
4613247 | McGunnigle | Sep 1986 | A |
D293241 | Wan et al. | Dec 1987 | S |
4799254 | Dayton et al. | Jan 1989 | A |
4888815 | Ahlemeyer et al. | Dec 1989 | A |
4999795 | Lapeyre | Mar 1991 | A |
5184830 | Okada et al. | Feb 1993 | A |
5217295 | Tortola et al. | Jun 1993 | A |
5334976 | Wang | Aug 1994 | A |
5336002 | Russo | Aug 1994 | A |
5367298 | Axhelm | Nov 1994 | A |
5375165 | Haber et al. | Dec 1994 | A |
D357253 | Wong | Apr 1995 | S |
5410141 | Koenck et al. | Apr 1995 | A |
5426449 | Danziger | Jun 1995 | A |
5436954 | Nishiyama et al. | Jul 1995 | A |
5457454 | Sugano | Oct 1995 | A |
5500643 | Grant | Mar 1996 | A |
5581593 | Engelke et al. | Dec 1996 | A |
5606712 | Hidaka | Feb 1997 | A |
5611031 | Hertzfeld et al. | Mar 1997 | A |
5660488 | Miller | Aug 1997 | A |
D383756 | Henderson et al. | Sep 1997 | S |
5672108 | Lam et al. | Sep 1997 | A |
D386497 | Huslig et al. | Nov 1997 | S |
5737394 | Anderson et al. | Apr 1998 | A |
D397369 | Rissman | Aug 1998 | S |
D397728 | Yuen et al. | Sep 1998 | S |
D399537 | Chi et al. | Oct 1998 | S |
5818437 | Grover et al. | Oct 1998 | A |
5825353 | Will | Oct 1998 | A |
5841374 | Abraham | Nov 1998 | A |
D403362 | Fai | Dec 1998 | S |
5848356 | Jambhekar et al. | Dec 1998 | A |
5893798 | Stambolic et al. | Apr 1999 | A |
5920308 | Kim | Jul 1999 | A |
5931873 | Cisar | Aug 1999 | A |
5952942 | Balakrishnan et al. | Sep 1999 | A |
5963197 | Bacon et al. | Oct 1999 | A |
5974238 | Chase, Jr. | Oct 1999 | A |
5982520 | Weiser et al. | Nov 1999 | A |
5995026 | Sellers | Nov 1999 | A |
6006351 | Peretz et al. | Dec 1999 | A |
6014429 | LaPorta et al. | Jan 2000 | A |
6023779 | Fullam et al. | Feb 2000 | A |
6046732 | Nishimoto | Apr 2000 | A |
6047047 | Aldridge et al. | Apr 2000 | A |
6047196 | Makela et al. | Apr 2000 | A |
6049697 | Scozzarella et al. | Apr 2000 | A |
6052070 | Kivela et al. | Apr 2000 | A |
6081584 | Hidaka | Jun 2000 | A |
6094197 | Buxton et al. | Jul 2000 | A |
6102594 | Strom | Aug 2000 | A |
6107994 | Harada et al. | Aug 2000 | A |
6107997 | Ure | Aug 2000 | A |
6148261 | Obradovich et al. | Nov 2000 | A |
6157323 | Tso et al. | Dec 2000 | A |
6212412 | Rogers et al. | Apr 2001 | B1 |
6218966 | Goodwin et al. | Apr 2001 | B1 |
6241406 | Yan | Jun 2001 | B1 |
6243789 | Hasbun et al. | Jun 2001 | B1 |
6297795 | Kato et al. | Oct 2001 | B1 |
6429855 | Pabon et al. | Aug 2002 | B2 |
6662020 | Aaro et al. | Dec 2003 | B1 |
6690417 | Yoshida et al. | Feb 2004 | B1 |
6868145 | Nelson | Mar 2005 | B1 |
6965372 | Woods | Nov 2005 | B1 |
20100048261 | Zhao et al. | Feb 2010 | A1 |
Number | Date | Country |
---|---|---|
0760291 | Mar 1997 | EP |
0898222 | Feb 1999 | EP |
WO9937025 | Jul 1999 | WO |
WO0030381 | May 2000 | WO |
Entry |
---|
Nokia: User's Manual, 9357109 Issue 2 EN, Jun. 7, 1998 (126 pages). |
Number | Date | Country | |
---|---|---|---|
20110304552 A1 | Dec 2011 | US |
Number | Date | Country | |
---|---|---|---|
60246321 | Nov 2000 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12607468 | Oct 2009 | US |
Child | 13193899 | US | |
Parent | 10004001 | Nov 2001 | US |
Child | 12607468 | US |