This disclosure concerns a technique for entering alphabetic phone numbers on a non-ITU Standard E.161 phone keypad arrangement, such as that utilized on mobile communication devices having either full QWERTY or reduced QWERTY formats.
When entering phone numbers that contain letters, for example, 1-800-FLOWERS, or when navigating some computer controlled answering systems, such as those that require entry of the last name of a person in a directory, the user is entering dual-tone multi-frequency (DTMF) codes for numbers that have certain letters associated with them in an ITU Standard E.161 phone keypad, shown in
One attempt to solve this problem is to require the user to hold down the ALT key and then multi-tap the letter keys until the appropriate letter is selected for each letter in the phone number. The name 1-800-FLOWERS appears on the display screen, but the user is not informed of the actual number being dialed.
Another related problem involves answering services that have automated menu systems that are controlled by DTMF codes. Inputting DTMF codes with these systems takes a long time to play the recorded messages that accompany the answering system menus. Furthermore, voice mail systems are also controlled over the phone by DTMF codes. This requires the user to either listen to all the control options or memorize which keys correspond to which options. One attempt to solve this is to provide the user with a reference card, but this involves the inconvenience of carrying the reference card around and pulling it out when needed.
This disclosure concerns a mobile communication device having a reduced format keyboard, as described in U.S. patent application Ser. No. 10/785,790, the disclosure of which is incorporated herein by reference in its entirety. This disclosure also concerns a full-size alphabetic format keyboard, such as that used on the BLACKBERRY 6230 device (a mobile communication device). Reduced format keyboards include the alphabetic characters, A-Z, and are arranged in a standard alphabetic keyboard format. The alphabetic characters are presented on fewer than twenty-six keys such that some alphabetic characters share keys with other alphabetic characters. The keyboard also includes a numeric phone arrangement of numbers 0-9, such that the mobile communication device may be used for sending and receiving phone calls, and for sending and receiving emails, among other types of messages, such as Short Message Service (SMS), or otherwise. Full-size keyboards include alphabetic characters A-Z that are arranged in a standard alphabetic keyboard format and a numeric phone arrangement of numbers 0-9 shares keys with the alphabetic characters.
The examples described herein provide different techniques for informing a user of the letters or functions that correspond to the numbers of a phone keypad. In a first example, shown in
In the example method, the user enters a command to pull up a help screen 25 that displays an ITU Standard E.161 phone key arrangement. For example, the user may select the “ALT” key 40, or some other control key to initiate a command to display the help screen 25 on the display 15. The help screen 25 could alternatively be displayed via a pull down menu activated by a thumbwheel or another key, or in any known way. It could also be displayed automatically upon putting the example mobile communication device 10 into a telephone mode. Any of these techniques could be programmed into the device's programming software.
Although the three middle columns of keys 32-34 on the keyboard 20 will normally function to enter DTMF codes corresponding to the alphabetic letters and numbers on the ITU Standard E.161 phone key arrangement, the help screen 25 informs the user of the alphabetic character that corresponds to the numeric indicia present on the keys. The DTMF codes will not be entered according to the alphabetic indicia printed on the keypad 20. The shape of the displayed keys on the help screen 25, as shown, corresponds to that of the keys in the three middle columns 32-34 on the keypad 20. This enhances the user recognition that the help screen 25 corresponds to the keypad 20. Alternatively, key shapes shown on the display do not have to be the same as those used on the keypad.
By using the help screen 25, the user can locate the key corresponding to the desired letter and press the corresponding key on the keypad 20 of the device 10 to obtain the appropriate DTMF code. For example, the phone number 1-800-FLOWERS would be entered by pressing the keys on the keyboard with the numeric indicia 1, 8, 0, 0, 3, 5, 6, 9, 3, 7, 7. As the number is entered, the numbers can be shown in the upper part of the display screen 15 that is not covered by the virtual representation of the middle column portion of the keypad, or on some other part of the screen 15. After the last number is pressed and the phone call is initiated by pressing, for example, the call key 42 in the second column 32, the help screen 25 may automatically disappear or it may stay up until the call is ended, for example, by pressing the call-end key 44. Alternatively, the user could be required to input a command, such as the “ALT” command, to make the help screen disappear.
The help screen 25 can also be used when entering alphabetic information after a call is initiated. For example, some answering services allow a user to dial the name of a person in the answering service directory. These answering services are programmed to receive alphabetic information from an ITU standard E.161 phone key arrangement. Thus, a user can pull up the help screen 25 and use the alphabetic letters displayed on the help screen keys as a guide to the corresponding keys on the keypad 20. In another example, the help screen 25 could be used to assist the user in entering alphanumeric information for relating reference numbers over the phone such as account numbers that include alphabetic characters.
In another example, a help screen 125 is programmable to include customized indicia displayed on the keys shown on the help screen 125. For example, as shown in
As shown in
Another example application includes a directory system implemented as shown in
In the example shown in
Alternatively, the ITU standard E.161 alphabetic arrangement could be used as the first help screen 325a, instead of just a single letter for each key. The second help screen 325b would then have a group of names corresponding to the grouping of letters on the ITU standard E.161 alphabetic arrangement.
The help screen can also be used with many other telephone menu systems that one might encounter in calling any organization that has an answering service with options. The answering service could send a data transmission with help information for navigating the menu system, or it could be stored on the mobile communication device. For example, a credit card company might have an option menu as shown in
In another example, shown in
In the second step 520, the user may specify a phone number and associate it with the stored help screen. Then in the third step 530 the user calls a phone number. After the phone number is called, in the fourth step 540, the processor on the mobile device determines whether the number called is a number associated with a stored help screen. If it is not, then no further action is taken 550, and the call takes place as normal. If the number called is associated with a stored help screen, then in a fifth step that help screen is displayed 560. The help screen may be closed when the call disconnects.
As an alternative to the technique shown in
In another example, shown in
In
To trigger dialing by letter instead of by number, as known in the art, the user can press the ALT key 640 in combination with an alphabetic key. The user may also use a multi-tap technique to dial by letter instead of number. A user could alternatively activate a control key or some other mechanism instead of using the ALT key 640.
The examples described above could be used to enter DTMF codes into a directory or other system once the recipient of a call has answered. The examples described above could also be utilized on a telephone that has a processor and a display capable of rendering a help screen showing text and associating it with keys on the keypad.
The above described features may also be used with a full-size standard key arrangement, such as the full QWERTY arrangement 1020 shown in
A help screen such as that shown in
The handheld mobile communication devices, presented in
The housing 712 may be elongated vertically, or may take on other sizes and shapes, including a clamshell housing structure, among other structures. The keyboard may include a mode selection key, or other hardware or software for switching between text entry and telephony entry.
In addition to the processing device 718, other parts of the mobile communication device 710 are shown schematically in
Operating system software executed by the processing device 718 is preferably stored in a persistent store, such as a flash memory 816, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element. In addition, system software, specific device applications, or parts thereof, may be temporarily loaded into a volatile store, such as a random access memory (RAM) 818. Communication signals received by the mobile communication device may also be stored to the RAM 818.
The processing device 718, in addition to its operating system functions, enables execution of software applications 830A-830N on the device 710. A predetermined set of applications that control basic device operations, such as data and voice communications 830A and 830B, may be installed on the device 710 during manufacture. In addition, a personal information manager (PIM) application may be installed during manufacture. The PIM is preferably capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items. The PIM application is also preferably capable of sending and receiving data items via a wireless network 840. Preferably, the PIM data items are seamlessly integrated, synchronized and updated via the wireless network 840 with the device user's corresponding data items stored or associated with a host computer system. An example system and method for accomplishing these steps is disclosed in “System And Method For Pushing Information From A Host System To A Mobile Device Having A Shared Electronic Address,” U.S. Pat. No. 6,219,694, which is owned by the assignee of the present application and expressly incorporated herein by reference.
Communication functions, including data and voice communications, are performed through the communication subsystem 800, and possibly through the short-range communications subsystem. The communication subsystem 800 includes a receiver 850, a transmitter 852, and one or more antennas 854, 856. In addition, the communication subsystem 800 also includes a processing module, such as a digital signal processor (DSP) 858, and local oscillators (LOs) 860. The specific design and implementation of the communication subsystem 800 is dependent upon the communication network in which the mobile communication device 710 is intended to operate. For example, a mobile communication device 710 may include a communication subsystem 800 designed to operate with the MOBITEX, DATATAC or General Packet Radio Service (GPRS) mobile data communication networks and also designed to operate with any of a variety of voice communication networks, such as AMPS, TDMA, CDMA, PCS, GSM, etc. Other types of data and voice networks, both separate and integrated, may also be utilized with the mobile communication device 710.
Network access requirements vary depending upon the type of communication system. For example, in the MOBITEX and DATATAC networks, mobile devices are registered on the network using a unique personal identification number or PIN associated with each device. In GPRS networks, however, network access is associated with a subscriber or user of a device. A GPRS device therefore requires a subscriber identity module, commonly referred to as a SIM card, in order to operate on a GPRS network.
When required network registration or activation procedures have been completed, the mobile communication device 710 may send and receive communication signals over the communication network 840. Signals received from the communication network 840 by the antenna 854 are routed to the receiver 850, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to-digital conversion of the received signal allows the DSP 858 to perform more complex communication functions, such as demodulation and decoding. In a similar manner, signals to be transmitted to the network 840 are processed (e.g. modulated and encoded) by the DSP 858 and are then provided to the transmitter 852 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 840 (or networks) via the antenna 856.
In addition to processing communication signals, the DSP 858 provides for control of the receiver 850 and the transmitter 852. For example, gains applied to communication signals in the receiver 850 and transmitter 852 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 858.
In a data communication mode, a received signal, such as a text message or web page download, is processed by the communication subsystem 800 and is input to the processing device 718. The received signal is then further processed by the processing device 718 for an output to the display 716, or alternatively to some other auxiliary I/O device 806. A device user may also compose data items, such as e-mail messages, using the keyboard 714 and/or some other auxiliary I/O device 806, such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device. The composed data items may then be transmitted over the communication network 840 via the communication subsystem 800.
In a voice communication mode, overall operation of the device is substantially similar to the data communication mode, except that received signals are output to a speaker 810, and signals for transmission are generated by a microphone 812. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the device 710. In addition, the display 716 may also be utilized in voice communication mode, for example to display the identity of a calling party, the duration of a voice call, or other voice call related information.
The short-range communications subsystem enables communication between the mobile communication device 710 and other proximate systems or devices, which need not necessarily be similar devices. For example, the short-range communications subsystem may include an infrared device and associated circuits and components, or a BLUETOOTH communication module to provide for communication with similarly-enabled systems and devices.
Although the keyboards or keypads described herein are in the context of a plurality of keys, the term keyboard or keypad may also be used equally in the context of a touchscreen or other touch-type keyboards.
While various features of the claimed embodiments are presented above, it should be understood that the features may be used singly or in any combination thereof. Therefore, the claimed embodiments are not to be limited to only the specific embodiments depicted herein.
Further, it should be understood that variations and modifications may occur to those skilled in the art to which the claimed embodiments pertain. The embodiments described herein are exemplary. The disclosure may enable those skilled in the art to make and use embodiments having alternative elements that likewise correspond to the elements recited in the claims. The intended scope may thus include other embodiments that do not differ or that insubstantially differ from the literal language of the claims. The scope of the example embodiments is accordingly defined as set forth in the patent claims.
This is a continuation application of application Ser. No. 12/973,555, filed Dec. 20, 2010 and which is entitled “DEVICE, SYSTEM, AND METHOD FOR INFORMING USERS OF FUNCTIONS AND CHARACTERS ASSOCIATED WITH TELEPHONE KEYS;” which is a continuation application of application Ser. No. 11/164,803, filed on Dec. 6, 2005, now U.S. Pat. No. 7,869,832, and which is entitled “DEVICE, SYSTEM, AND METHOD FOR INFORMING USERS OF FUNCTIONS AND CHARACTERS ASSOCIATED WITH TELEPHONE KEYS;” which claims the benefit of U.S. Provisional Application No. 60/724,458, filed Oct. 7, 2005 and which is entitled “SYSTEM AND METHOD FOR USING NAVIGATIONAL COMMANDS ON A MOBILE COMMUNICATION DEVICE AND FOR INPUTTING DTMF CODES;” said applications are hereby expressly incorporated into the present application by reference, including the entirety of the written descriptions, drawings, and figures.
Number | Name | Date | Kind |
---|---|---|---|
5917905 | Whipple et al. | Jun 1999 | A |
6219694 | Lazaridis et al. | Apr 2001 | B1 |
6243460 | Bhagavatula | Jun 2001 | B1 |
6307541 | Ho | Oct 2001 | B1 |
6483913 | Smith | Nov 2002 | B1 |
6519482 | Mittelstadt et al. | Feb 2003 | B1 |
6594484 | Hitchings, Jr. | Jul 2003 | B1 |
6711419 | Mori | Mar 2004 | B1 |
7007239 | Hawkins et al. | Feb 2006 | B1 |
7159180 | Ward | Jan 2007 | B2 |
7289768 | Kim | Oct 2007 | B2 |
7363059 | Lundy | Apr 2008 | B1 |
7869832 | Griffin | Jan 2011 | B2 |
8527010 | Griffin | Sep 2013 | B2 |
20010014615 | Dahm et al. | Aug 2001 | A1 |
20020025837 | Levy | Feb 2002 | A1 |
20020054676 | Zhao et al. | May 2002 | A1 |
20020181671 | Logan | Dec 2002 | A1 |
20030172046 | Scott | Sep 2003 | A1 |
20040198244 | Jarrad | Oct 2004 | A1 |
20040242279 | Costanzo et al. | Dec 2004 | A1 |
20040253973 | Nguyen | Dec 2004 | A1 |
20050129199 | Abe | Jun 2005 | A1 |
20050130642 | Scott | Jun 2005 | A1 |
20050157860 | Schnarel | Jul 2005 | A1 |
20050250547 | Salman | Nov 2005 | A1 |
20060007178 | Davis | Jan 2006 | A1 |
20060033706 | Haitani | Feb 2006 | A1 |
20060103623 | Davis | May 2006 | A1 |
20060168539 | Hawkins et al. | Jul 2006 | A1 |
20060224945 | Khan | Oct 2006 | A1 |
20070004460 | Tsampalis | Jan 2007 | A1 |
20070047722 | Kunimune | Mar 2007 | A1 |
20070279256 | Salman et al. | Dec 2007 | A1 |
Number | Date | Country |
---|---|---|
10027146 | Nov 2001 | DE |
0567333 | Oct 1993 | EP |
1263195 | Dec 2002 | EP |
1317117 | Jun 2003 | EP |
1416702 | May 2004 | EP |
2837941 | Oct 2003 | FR |
2402650 | Dec 2004 | GB |
03056784 | Jul 2003 | WO |
Entry |
---|
European Search Report in European Application No. 05257504.0, dated May 8, 2006, 4 pages. |
Office Action mailed Feb. 19, 2014; in corresponding Canadian patent application No. 2,562,972. |
Notice of Allowance and Fee(s) Due mailed Oct. 11, 2012; in corresponding European patent application No. 05257504.0. |
ITU-T Q.23; Telecommunication Standardization Sector of ITU; General Recommendations on Telephone Switching and Signalling; International Automatic and Semi-Automatic Working; Technical Features of Push-Button Telephone Sets; ITU-T Recommendation Q.23 (Extract from the Blue Book); Downloaded by EPO on Apr. 13, 2011. |
ITU-T E.161; Telecommunication Standardization Sector of ITU; Series E: Overall Network Operation, Telephone Service, Service Operation and Human Factors; International operation—Numbering plan of the international telephone service; Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network; ITU-T Recommendation E.161 (Formerly CCITT Recommendation); Downloaded by EPO on Apr. 13, 2011. |
Examination report mailed Mar. 8, 2012; in corresponding European patent application No. 05257504.0. |
Office Action mailed Mar. 22, 2012; in corresponding Canadian patent application No. 2,562,972. |
Examination Report mailed Aug. 19, 2008, in corresponding European patent application No. 05257504.0. |
Examination Report mailed Aug. 30, 2006, in corresponding European patent application No. 05257504.0. |
Office Action mailed Feb. 24, 2010, in corresponding Canadian patent application No. 2,562,972. |
Office Action mailed Mar. 7, 2011, in corresponding Canadian patent application No. 2,562,972. |
Office Action mailed Mar. 26, 2013, in corresponding Canadian patent application No. 2,562,972. |
Number | Date | Country | |
---|---|---|---|
20130305179 A1 | Nov 2013 | US |
Number | Date | Country | |
---|---|---|---|
60724458 | Oct 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12973555 | Dec 2010 | US |
Child | 13946733 | US | |
Parent | 11164803 | Dec 2005 | US |
Child | 12973555 | US |