WO2006127524A1

WO2006127524A1 - Mobile communication device and method using aliases to manage contact information

Info

Publication number: WO2006127524A1
Application number: PCT/US2006/019587
Authority: WO
Inventors: Janine Dolgas; Mark Robinson
Original assignee: Kyocera Wireless Corp.
Priority date: 2005-05-20
Filing date: 2006-05-19
Publication date: 2006-11-30
Also published as: WO2006127524B1; US20060281490A1; US7706832B2

Abstract

An alias can be used to access address book information across multiple communication applications. The alias can also be a screen name, for example, an instant messenger screen name. However, the alias can be used to access more than just instant messenger contact information; it can be used to access other information, including telephone numbers, SMS, EMS and MMS contact information as well as instant messenger contact information. Additionally, the single alias can be used to access instant messenger contact information across multiple instant messenger services. An alias can be assigned that is easy to remember; for example, it can be a shortened version of the contact's name, or a nickname.

Description

SYSTEMS AND METHODS FOR USING ALIASES TO MANAGE CONTACT INFORMATION IN A MOBILE COMMUNICATION DEVICE

BACKGROUND

1. Field of the Invention

The field of the invention relates generally to mobile communication devices and more particularly to managing contact information for a plurality of communication applications running on a mobile communication device.

2, Background Information

Conventional mobile communication devices, such as cellular telephones and Personal Digital Assistants (PDAs) with communication capability, can be configured to support a variety of communication applications, or services, including, for example, voice communication services, Short-Message-Service (SMS), Enhanced Message Service (EMS), Multimedia Messaging Service (MMS), and Instant Messaging (IM). Conventional mobile communication devices often include an ""address book" to keep track of contact information for a plurality of contacts; however, maintaining contact information for a large number of contacts can become unwieldy, making conventional address books difficult to use.

This problem is compounded when a mobile communication device is configured to support multiple communication applications, because each contact can potential be associated with a different contact identifier for each communication application. For example, each contact can have a unique telephone number, SMS address or identifier, IM address or identifier, etc. Accordingly, conventional address books can become filled with enough information that they are difficult to navigate and use.

Conventional address books typically provide several navigation methods. For example, the user can scroll through each entry one entry at a time. Such an approach is generally manageable when the address book is small, but quickly becomes unmanageable, or at least time consuming, as the address book grows. In many cases the user can also enter a letter, for example, the first letter of a last name, to limit the number of entries that must be subsequently searched. This can still be time-consuming for long lists. A user can sometimes enter more characters to further limit the number of entries to be searched, even zeroing in on the precise entry. This can require that several characters be entered to select a contact. A speed dial approach can alsoιbe used to allow quick access to entries in an address book. In such an approach, a contact is associated with a defined storage location. For example, a communication device can have perhaps 1 to 99, or more, defined storage locations for this purpose. A user can then access a contact by entering an identifier, such as a number, that identifies the associated storage location. A drawback to this approach, however, is that a typical user can only remember the storage identifier for a relatively small number of contacts. Thus, the user ends up scrolling through the speed dial locations anyway.

SUMMARY OF THE INVENTION

One way to quickly access address book information is through the use of aliases. An alias can be assigned that is easy to remember; for example, it can be a shortened version of the contact's name, or a nickname. The alias can also be a screen name, for example, an instant messenger screen name; however, the alias can be used to access more than just instant messenger contact information. For example, the alias can be used to access address book information, including telephone numbers, SMS, EMS, IM and MMS contact information.

In one aspect, a single alias can even be used to access IM contact information for multiple IM services.

These and other features, aspects, and embodiments of the invention are described below in the section entitled "Detailed Description."

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments of the inventions are described in conjunction with the attached drawings, in which:

Figure 1 is a diagram illustrating an address book that includes aliases in accordance with one embodiment;

Figure 2 is a diagram illustrating an association between an aliases and a plurality of contact identifiers included in a contact entry of the address book of figure 1;

Figure 3 is a flow chart illustrating an example method for using an alias to send a communication in accordance with one embodiment;

Figure 4 is a diagram illustrating an association between an alias and multiple IM identifiers; Figure 5 is flow chart illustrating an example method for using an alias to respond to a message in accordance with one embodiment;

Figure 6 is a flow chart illustrating an example method for allowing a user to select between multiple contact identifiers associated with the same communication application in accordance with one embodiment; and

Figure 7 is a diagram illustrating an example mobile communication device configured to contain the address book of figure 1 and implement the methods of figures 3, 5, and 6.

DETAILED DESCRIPTION

In the systems and methods described below, an alias is associated with contact entries in an address book included in a communication device. The alias can then be used to access the appropriate contact identifier for a specific communication application. For example, if a user of a mobile communication devices is trying to send an SMS message to a specific contact, then the alias can be used to select the contacts SMS address. The aliases are provided by the user and can, therefore, be easier to remember than, e.g., a speed dial location. Moreover, a single alias can be used to select the appropriate contact identifier for each communication application supported.

For purposes of this specification and the claims that follow, the term contact identifier is intended to refer to the number, address, or other identifier used to establish a communication with the contact using a given communication application (e.g, a telephone number, SMS number, email address, etc.).

Figure 1 is a diagram illustrating an address book 100 configured in accordance with one embodiment of the systems and methods described herein. As can be seen, address book 100 comprises a plurality of contact entries 102. Contact entries 102, can for example, comprise contact information such as the name of the contact, address, business, title, etc., as with many conventional address books. Further, each contact entry can contain one or more contact identifiers for the associated contact. In addition, however, an alias 104 is associated with each contact entry 102. Alias 104 can be a moniker that is associated with the contact by the user. Alias 104 can, for example, be a name, nickname, initials, abbreviation, screen name, etc. Preferably, an alias 104 associated with a specific contact will be easy to remember.

Generally, each contact entry 102 is associated with a single alias 104; however, depending on the embodiment, a contact can be associated with a plurality of aliases 104. A single alias 104 can also be associated with more than one montact entry 102. Additionally, in certain embodiments, certain contact entries 102 may not be associated with an alias 104.

Thus, the contact entry 102 - alias 104 association generates an association between the contact identifiers included in the contact entry and the associated alias. This is illustrated in the diagram of figure 2. As can be seen, the contact entry 102 can include a plurality of contact identifiers 202. These can include a home telephone number, mobile telephone number, work telephone number, IM identifier, SMS contact identifier, EMS contact identifier, MMS contact identifier, etc. In many embodiments, contact identifiers 202 will only include identifiers for communication applications supported by the associated communication device; however, in certain embodiments, contact identifiers for unsupported communication applications can also be stored in contact entry 102. Each of these contact identifiers 202 is associated with the corresponding alias 104. The association between contact identifiers 202 and alias 104 can allow for quick access to contact information and identifiers as described in detail below.

It will be appreciated that there are many methods by which the alias information can be entered and associated with a contact entry. For example, the user can be allowed to enter the aliases into the user's communication device when the user is entering other contact information. In certain embodiments, a software program running on a computer can be used to enter and manage contact and alias information, which can then be downloaded to the communication device.

Figure 3 is flow chart illustrating an example method for using an alias for establishing a communication from the perspective of a communication device in accordance with one embodiment of the systems and methods described herein. First, the communication device can be configured to initiate a communication application, in step 302, in response to an action taken by the user. For example, the user can activate an SMS application supported by the communication device. This will cause the communication device to launch the SMS application and wait for a SMS identifier to be entered in to the device.

Instead of entering an SMS identifier, however, the user can input an alias, which will be received by the device in step 308. The alias can, for example, be input through a user interface associated with the communication device. The device can then map the alias provide in step 304 to the associated contact entry in step 310. The device can be configured to then determine and select the appropriate contact identifier 202, e.g., the associated SMS identifier, in step 312. In other words, the SMS application, or a software program or application configured to run on the communication device, can be configured to scroll through the contact identifiers associated with the corresponding contact entry and select the one the corresponds to, or is appropriate for, the SMS application. Other method for determining or retrieving the appropriate contact identifier may also be used. For example, a function may be defined that retrieves the appropriate contact for the address book data using an application (or application identification) and an alias (or alias identification).

If the communication application selected is a data application, such as an SMS application, then the user can, prior to entering the alias, enter the data, or message, to be transmitted in step 304. In alternative embodiments, or implementations, the data can be entered after the alias is entered (step 308) and the associated contact identifier is selected (step 312). If the application is a data application, then the data can be sent in step 316, once the contact identifier, e.g., SMS identifier, is selected. But if the application is a voice application, for example, then a connection can be made, e.g., a call can be placed, using the selected contact identifier in step 318.

In certain instances, a contact can have multiple contact identifiers for a given communication application. For example, a contact can have multiple telephone numbers as illustrated in figure 3. A user can also have multiple identifiers for other communication applications. Figure 4, for example, illustrates the situation where multiple IM identifiers 402 and 404 are associated with a single contact and alias 104. Two IM identifier are illustrated in figure 4 by way of example only. It will be understood that more than two identifiers for a given communication application can be associated with a single alias, such as the the three telephone numbers in figure 3. In such situations, the user can be prompted to select the appropriate identifier.

On example method for prompting the user to select one of multiple contact identifiers associated with the same communication application is illustrated by the flow chart of figure 6. In figure 6, once it is determined that there are multiple contact identifiers associated with the contact for the selected communication application, the user can be prompted to select the appropriate identifier in step 602. For example, the contact identifiers can be displayed on a display associated with the communication device. The user can then select the appropriate identifier, e.g., by scrolling to the appropriate identifier or entering a number associated with the appropriate identifier, which will be received in step 604. The selected identifier can then be associated with the outgoing message or co mmunication in step 606, which can then be sent or initiated in step 608.

Figure 5 is a flow chart illustrating an example method for using an alias to respond to, or forward a message, or incoming communication, in accordance with one embodiment of the systems and methods described herein. In step 502, a message, or incoming communication, is received. The user can then select to activate the communication application associated with the message so that the user can view or hear the message. This will cause the communication device to initiate the communication application in step 504. The user can then select to respond to, or forward the message in step 506, which can cause the application to prompt the user for an alias in step 508.

In one embodiment, the contact identifier associated with the received message can appear as a default alias when the user elects to forward or respond to the message. If the user wants to send the response to another party, an additional party, or if no default is used, then the user can enter the appropriate alias in step 510. In step 512, the alias can be mapped to the appropriate contact entry and the appropriate contact identifier can be selected from contact identifiers 202.

The user can be prompted repeatedly until the user has entered the aliases associated with all contacts to which the user desires to forward the message. Once the user is done entering aliases, the message can be forwarded in step 514. But first, the user can be given the option to enter further data, such as a reply message, in step 516, depending on the embodiment and the type of communication involved.

It will be appreciated that the prompt of step 508 can be for a contact identifier, to which the user instead responds with an alias. Accordingly, the device should be configured to recognize an alias, from a contact identifier, and map it to the associated contact entry.

Certain communication applications can incorporate voice recognition. In such instances, the voice recognition component can be trained on the aliases associated with the contact entries. For example, after activating a particular communication application, the user can speak the alias into the device, cause in the device to map the alias to the appropriate contact entry and retrieve the appropriate contact identifier.

Figure 7 is a diagram of a mobile communication device 700 configured to implement the systems and methods described above. As can be seen, in the example of figure 7, device 700 includes an antenna 702 and a radio 704. Radio 704 can be configured to modulate signals to be transmitted with a carrier frequency and transmit them via antenna 702. Radio 704 can also be configured to demodulate, signals received via antenna 702. Processor 706 can be configured to process the transmit and receive signals.

Processor 706 can comprise multiple processors or processing circuits, such as Digital signal Processors (DSPs), audio processors, math coprocessors, etc. These processors and/or processing circuits can be included in a single Integrated Circuit (IC), or several ICs, and can be packaged in a single chip package or multiple chip packages. Radio 704 can be any standard or customized radio configured to transmit signals wirelessly over the air. Antenna 702 can comprise a single or antenna or multiple antennas, e.g., for spatial diversity. In fact antenna 702 can actually comprise one or more arrays of antennas.

Device 700 can also include a memory 714 coupled with processor 706, which can be configured to store instructions 718 and data that can be used by processor 714 to control the operation of device 700. In addition, memory 714 can be configured to store an address book 720, which can comprise contact information and associated aliases as described above. Memory 714 can also store applications such as communication applications 716, which can include, e.g., a SMS application, MMS application, EMS application, IM application, etc. Memory 714 can also store alias program 712.

Thus, a user can cause one of the communication applications 716 to be launched (step 302), e.g., via commands entered through a user interface 710 coupled with processor 706. Once launched, the select communication application can then prompt the user for a contact identifier, e.g., the application can cause a prompt to be displayed on display 708. The user can, in response to the prompt, input an alias (step 308), e.g., through user interface 710. Alias program 712 can be configured to then recognize that an alias was provided, map the alias to the corresponding contact entry (step 310) in address book 720, and select the appropriate contact identifier (step 312). The selected communication application can then send, or initiate, a communication using the contact identifier (step 316).

Alias program 712 can actually comprise part of the communication applications 716 or can be an overlay that works in conjunction with each of communication applications 716.

It should be noted that memory 714 can be one or multiple device contained in one ore multiple circuit packages. For example, memory 714 can include static or dynamic memory, erasable memory, removable memory, etc.

While certain embodiments and/or implementations of the inventions have been described above, it will be understood that the embodiments described are by way of example only. Accordingly, the inventions shouldn't be limited based on the described embodiments. Rather, the scope of the inventions described herein should only be limited in light of the claims that follow when taken in conjunction with the above description and accompanying drawings.

What is claimed is:

Claims

1. A mobile communication device, comprising: an address book comprising a plurality of contact entries and an plurality of aliases, each contact entry comprising a plurality of contract identifiers and each alias associated with one of the plurality of contact entries; and a communication application configured to receive a particular alias of the plurality of aliases, determine the associated contact entry for the particular alias, and determine the appropriate contact identifier from the plurality of contact identifiers associated with the particular alias and the communication application.

2. The mobile communication device of claim 1, wherein the communication application is further configured to use the determined contact identifier to send a communication.

3. The mobile communication device of claim 1, wherein the communication application is a voice communication services, and wherein the determined contact identifier is a telephone number.

4. The mobile communication device of claim 1, wherein the communication application is a Short-Message-Service, and wherein the determined contact identifier is a Short-Message-Service identifier.

5. The mobile communication device of claim 1, wherein the communication application is an Enhanced Message Service, and wherein the determined contact identifier is an Enhanced Message Service identifier.

6. The mobile communication device of claim 1, wherein the communication application is a Multimedia Messaging Service, and wherein the determined contact identifier is a Multimedia Messaging Service identifier.

7. The mobile communication device of claim 1, wherein the communication application is an Instant Messaging Service, and wherein the determined contact identifier is an Instant Messaging Service identifier.

8. The mobile communication device of claim 1, wherein each of the plurality of contact identifiers is associated with a corresponding communication application.

9. The mobile communication device of claim 8, wherein more than one of the plurality of contact identifiers associated with the contact entry is associated with the communication application, and wherein the communication application is configure to prompt a user to select which of the associated contact identifiers is the appropriate contact identifier.

10. The mobile communication device of claim 1, wherein the communication application is configured to receive an incoming communication and allow a user to respond by entering an aliases to which the response is directed, and wherein the communication application is configured to receive the alias, map the received alias to the associated contact entry and select the appropriate contact identifier from the plurality of contact identifiers associated with the selected contact entry.

11. A managing contact information in a mobile communication device, comprising: initiating a communication application; receiving an alias; mapping the received alias to an associated contact entry; determining the appropriate contact identifier, from a plurality of contact identifiers included in the contact entry, the appropriate contact identifier based on the communication application and the alias; and using the contact identifier to send a communication.

12. The method of claim 11, further comprising: receiving contact information associated with a plurality of contact entries, each contact entry comprising a plurality of contact identifiers; storing the received contact information; receiving an alias for each contact entry; storing the received aliases; and associating each received alias with one of the plurality of contact entries.

13. The method of claim 11, wherein the communication application is a voice communication services, and wherein the selected contact identifier is a telephone number.

14. The method of claim 11, wherein the communication application is a Short- Message-Service, and wherein the selected contact identifier is a Short-Message-Service identifier.

15. The method of claim 11, wherein the communication application is an Enhanced Message Service, and wherein the selected contact identifier is an Enhanced Message Service identifier.

16. The method of claim 11, wherein the communication application is a Multimedia Messaging Service, and wherein the selected contact identifier is a Multimedia Messaging Service identifier.

17. The method of claim 11, wherein the communication application is an Instant Messaging Service, and wherein the selected contact identifier is an Instant Messaging Service identifier.

18. The method of claim 11, further comprising prompting the user to select which of multiple contact identifiers associated with the same communication application is the appropriate contact identifier.

19. The method of claim 11, further comprising: receiving an incoming communication receiving an alias; mapping the received alias to the associated contact entry; and selecting the appropriate contact identifier from the plurality of contact identifiers associated with the selected contact entry.

20. The method of claim 19, further comprising sending a response to the received message to the contact associated with the contact entry using the selected contact identifier.