Patent Application
20090100378
The present application relates generally to the user interface for an instant messaging (IM) messaging application and more particularly for a system and method for adding address book verbs to the IM application menus.
Communication devices such as personal computers, wireless mobile telephones, personal data assistants, etc. often provide data communication abilities to users. One currently popular form of such communication is Instant Messaging or IM facilitated by an IM application having a graphical user interface (GUI) whereby two or more users of different communication devices can engage in a conversational data communication exchange.
To permit IM message exchange, a user may invite another to agree to receive IM messages and be included in the user's list of IM contacts (sometimes called an IM friend or buddy in view of the agreement to be a potential IM message recipient). The availability of the user or particular IM contacts for conversations may be maintained in accordance with respective presence information. To begin an IM conversation, a user selects a buddy represented by a IM contact list entry of a list of contacts and inputs a message. Additional IM contacts may be invited to engage in a group message, as desired. While IM messaging was originally directed to text, newer protocols support file transports and voice over data communications.
In addition to conducting an IM conversation with a buddy, an IM user may want to communicate with the buddy using another available communication ability provided by the communication device such as phone, email, text messaging, etc. Contact information such as phone numbers, email addresses, etc. for these communication abilities for the buddy may have been previously entered and stored in an address book application by the user. Finding and invoking the buddy's address book contact information for the particular communication ability may be time consuming and difficult. The user typically must switch applications and leave the IM application interface. Exiting and invoking the address book interface or other communication ability interface may be inconvenient and time consuming, requiring a number of user inputs.
Thus it is desirable to provide an IM interface to other communication abilities that can be used to contact the other user.
In order that the subject matter may be readily understood, embodiments are illustrated by way of examples in the accompanying drawings, in which:
Persons of ordinary skill in the art will appreciate that the teachings herein are applicable to messages received via wired or wireless communication and though a wireless communication device and network including wireless communication capabilities are discussed in the examples, no limitations should be imposed.
A system and method for alternatively communicating with an Instant Messaging (IM) contact from an IM application using address book verbs is provided. In an IM application, a context sensitive menu of options is presented to permit a user to invoke alternative communication capabilities (e.g. email, voice, SMS, etc.) of the communication device with the IM contact. Address book contact information stored separately from the IM application is pulled for the IM contact and, for available alternative contact information, respective actions are presented as options (e.g. ‘Call contact’, ‘Email contact’, ‘SMS contact’, etc.). If particular contact information (e.g. phone number is not available) associated alternative communication actions are not presented. Selection of an action invokes the associated alternative application with the appropriate contact information from the IM application.
Typically, controller 106 is embodied as a central processing unit (CPU) which runs operating system software in a memory component (not shown). Controller 106 will normally control overall operation of mobile station 102, whereas signal processing operations associated with communication functions are typically performed in RF transceiver circuitry 108. Controller 106 interfaces with device display 112 to display received information, stored information, user inputs, and the like. Keyboard 114, which may be a telephone type keypad or full alphanumeric keyboard, is normally provided for entering data for storage in mobile station 102, information for transmission to network 104, a telephone number to place a telephone call, commands to be executed on mobile station 102, and possibly other or different user inputs.
Mobile station 102 sends communication signals to and receives communication signals from network 104 over a wireless link via antenna 110. RF transceiver circuitry 108 performs functions similar to those of a radio network (RN) 128, including for example modulation/demodulation and possibly encoding/decoding and encryption/decryption. It is also contemplated that RF transceiver circuitry 108 may perform certain functions in addition to those performed by RN 128. It will be apparent to those skilled in art that RF transceiver circuitry 108 will be adapted to particular wireless network or networks in which mobile station 102 is intended to operate.
Mobile station 102 includes a battery interface 122 for receiving one or more rechargeable batteries 124. Battery 124 provides electrical power to electrical circuitry in mobile station 102, and battery interface 122 provides for a mechanical and electrical connection for battery 124. Battery interface 122 is coupled to a regulator 126 which regulates power to the device. When mobile station 102 is fully operational, an RF transmitter of RF transceiver circuitry 108 is typically turned on only when it is sending to network, and is otherwise turned off to conserve resources. Similarly, an RF receiver of RF transceiver circuitry 108 is typically periodically turned off to conserve power until it is needed to receive signals or information (if at all) during designated time periods.
Mobile station 102 operates using a memory module 120, such as a Subscriber Identity Module (SIM) or a Removable User Identity Module (R-UIM), which is connected to or inserted in mobile station 102 at an interface 118. As an alternative to a SIM or an R-UIM, mobile station 102 may operate based on configuration data programmed by a service provider into an internal memory which is a non-volatile memory. Mobile station 102 may consist of a single unit, such as a data communication device, a cellular telephone, a multiple-function communication device with data and voice communication capabilities, a personal digital assistant (PDA) enabled for wireless communication, or a computer incorporating an internal modem. Alternatively, mobile station 102 may be a multiple-module unit comprising a plurality of separate components, including but in no way limited to a computer or other device connected to a wireless modem. In particular, for example, in the mobile station block diagram of
Mobile station 102 communicates in and through wireless communication network 104. In the embodiment of
During operation, mobile station 102 communicates with RN 128 which performs functions such as call-setup, call processing, and mobility management. RN 128 includes a plurality of base station transceiver systems that provide wireless network coverage for a particular coverage area commonly referred to as a “cell”. A given base station transceiver system of RN 128, such as the one shown in
The wireless link shown in communication system 100 of
For all mobile stations 102 registered with a network operator, permanent data (such as mobile station 102 user's profile) as well as temporary data (such as mobile station's 102 current location) are stored in a HLR/AC 138. In case of a voice call to mobile station 102, HLR/AC 138 is queried to determine the current location of mobile station 102. A Visitor Location Register (VLR) of MSC 130 is responsible for a group of location areas and stores the data of those mobile stations that are currently in its area of responsibility. This includes parts of the permanent mobile station data that have been transmitted from HLR/AC 138 to the VLR for faster access. However, the VLR of MSC 130 may also assign and store local data, such as temporary identifications. Mobile station 102 is also authenticated on system access by HLR/AC 138. In order to provide packet data services to mobile station 102 in a CDMA2000-based network, RN 128 communicates with PDSN 132. PDSN 132 provides access to the Internet 144 (or intranets, Wireless Application Protocol (WAP) servers, etc.) through IP network 134. PDSN 132 also provides foreign agent (FA) functionality in mobile IP networks as well as packet transport for virtual private networking. PDSN 132 has a range of IP addresses and performs IP address management, session maintenance, and optional caching. RADIUS server 136 is responsible for performing functions related to authentication, authorization, and accounting (AAA) of packet data services, and may be referred to as an AAA server.
Wireless communication network 104 also includes a Push-to-talk over Cellular (PoC) server 137 which may be coupled to IP network 134. PoC server 137 operates to facilitate PoC individual and group communication sessions between mobile stations within network 104. A conventional PoC communication session involves a session connection between end users of mobile stations, referred to as session “participants”, who communicate one at a time in a half-duplex manner much like conventional walkie-talkies or two-way radios.
Those skilled in art will appreciate that wireless network 104 may be connected to other systems, possibly including other networks, not explicitly shown in
Mobile station 202 will normally incorporate a communication subsystem 211, which includes a receiver 212, a transmitter 214, and associated components, such as one or more (preferably embedded or internal) antenna elements 216 and 218, local oscillators (LOs) 213, and a processing module such as a digital signal processor (DSP) 220. Communication subsystem 211 is analogous to RF transceiver circuitry 108 and antenna 110 shown in
Mobile station 202 may send and receive communication signals over the network after required network registration or activation procedures have been completed. Signals received by antenna 216 through the network are input to receiver 212, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and like, and in example shown in
Network access is associated with a subscriber or user of mobile station 202, and therefore mobile station 202 requires a memory module 262, such as a Subscriber Identity Module or “SIM” card or a Removable User Identity Module (R-UIM), to be inserted in or connected to an interface 264 of mobile station 202 in order to operate in the network. Alternatively, memory module 262 may be a non-volatile memory which is programmed with configuration data by a service provider so that mobile station 202 may operate in the network. Since mobile station 202 is a mobile battery-powered device, it also includes a battery interface 254 for receiving one or more rechargeable batteries 256. Such a battery 256 provides electrical power to most if not all electrical circuitry in mobile station 202, and battery interface 254 provides for a mechanical and electrical connection for it. The battery interface 254 is coupled to a regulator (not shown in
Mobile station 202 includes a microprocessor 238 (which is one implementation of controller 106 of
Microprocessor 238, in addition to its operating system functions, preferably enables execution of software applications on mobile station 202. A predetermined set of applications which control basic device operations, including at least data and voice communication applications, will normally be installed on mobile station 202 during its manufacture. A preferred application that may be loaded onto mobile station 202 may be a personal information manager (PIM) application having the ability to organize and manage data items relating to user such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores are available on mobile station 202 and SIM 262 to facilitate storage of PIM data items and other information.
The PIM application preferably has the ability to send and receive data items via the wireless network. In a preferred embodiment, PIM data items are seamlessly integrated, synchronized, and updated via the wireless network, with the mobile station user's corresponding data items stored and/or associated with a host computer system thereby creating a mirrored host computer on mobile station 202 with respect to such items. This is especially advantageous where the host computer system is the mobile station user's office computer system. Additional applications may also be loaded onto mobile station 202 through network, an auxiliary I/O subsystem 228, serial port 230, short-range communications subsystem 240, or any other suitable subsystem 242, and installed by a user in RAM 226 or preferably a non-volatile store (not shown) for execution by microprocessor 238. Such flexibility in application installation increases the functionality of mobile station 202 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile station 202.
In a data communication mode, a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem 211 and input to microprocessor 238. Microprocessor 238 will preferably further process the signal for output to display 222 or alternatively to auxiliary I/O device 228. A user of mobile station 202 may also compose data items, such as e-mail messages, for example, using keyboard 232 in conjunction with display 222 and possibly auxiliary I/O device 228. Keyboard 232 is preferably a complete alphanumeric keyboard and/or telephone-type keypad. These composed items may be transmitted over a communication network through communication subsystem 211.
For voice communications, the overall operation of mobile station 202 is substantially similar, except that the received signals would be output to speaker 234 and signals for transmission would be generated by microphone 236. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on mobile station 202. Although voice or audio signal output is preferably accomplished primarily through speaker 234, display 222 may also be used to provide an indication of the identity of a calling party, duration of a voice call, or other voice call related information, as some examples.
Serial port 230 in
Short-range communications subsystem 240 of
Mobile station 202 may be adapted to provide instant messaging communications via programming instructions and data stored or otherwise available to the device 202 such as by way of an IM application. IM provides a conversational dialog typically involving the exchange of primarily text-based messages between a user of device 202 and at least one other user of another device (not shown) adapted for IM communication. As persons of ordinary skill in the art will appreciate, an IM system or “presence and instant messaging system” allows users to subscribe to each other and be notified of changes in state (e.g. availability for instant message communication) and for users to send each other short instant messages. IM is discussed in further detail in “RFC 2778—A Model for Presence and Instant Messaging”, maintained by the Internet Society and available at http://www.ietf.org/rfc/rfc2778.txt. As such, adapted mobile station 202 provides a user agent for IM communication in an IM system.
Often, IM applications are provided as standalone applications separate from other communication applications on device 202 such as separately from email applications or phone applications, etc. The IM application maintains a contact list (often with the assistance of a remote IM server (not shown)) that is separate from an address book of contact information that may be otherwise available to device 202 via an address book interface and which address book is typically integrated with the device's email and/or phone application. As such, IM contact information is not usually stored in the address book and most address book contact information is not maintained in the contact list.
In order to invite another user to be an IM contact of the user of device 202, the other user's email address is often supplied to the IM application by the IM user of device 202 to send the invitation. However, another data message address, such as a PIN, could also be used instead. Thus the IM contact list can store a non-IM address for an IM contact.
Advantageously, as described further below, the IM application and address book may be adapted so that the IM application can obtain address book information for an IM contact with which the IM application can then present context sensitive options for a user to invoke other communication abilities with the IM contact.
GUI 1002 provides support for a contact list oriented interface for controlling aspects of the presence and IM functions using list of IM contacts 1006. Additional IM contact list entries may include entries for current conversations 1008. Other IM contact list entries may include IM group entries for organizing individual IM contacts, and pending or unavailable IM contacts in accordance with presence information (not shown in
Address book application 1010 manages address book contact information. Address book application 1010 usually provides user access to contact data store 1011 to update or maintain such information and provides API access to email or other communication applications to obtain contact information with which to respectively communicate with the contact. Contact data store 1011 stores the contact records 1012. Typically, a contact record may contain contact information such as a contacts name, title and company, email addresses, phone numbers (e.g. one or more for home, work, fax, pager, etc.) mailing addresses, PIN (i.e. a personal identification number for a user's mobile station within a particular service provider network), etc. Some service provider's permit data messaging using PIN addressing.
Address book application 1010 provides an interface that permits other applications to retrieve information from contact data store 1011. Contact data store 1011 may employ various storage schemes (e.g. plain text or binary data) for contact records 1012. Data compression may also be applied to contact records stored in the contact data store.
Persons of ordinary skill in the art will appreciate that IM Application 1004 may, in some embodiments, directly access the contact data store 1011 in order to decrease the search time or to avoid interacting with the address book application 1010 among other reasons obvious in the art. When there is direct access to the contact data store 1011, precautions may have to be taken to prevent multiple applications from simultaneously accessing and corrupting the contact data store.
In accordance with the present matter, contextual menus 1016 may be created by the system and method for adding address book verbs to the IM application menus. As such, the GUI 1002 may use the contextual menu containing the user selected IM contact's relevant address book verbs as part of the IM application menus.
As will be understood by those of ordinary skill in the art, it is sometimes difficult to make bright-line distinctions between components such as, GUI, IM application and contextual menu components 1002, 1004 and 1016 or address book application 1010 and contact data store 1011. As well, it is understood that the components 1000 interface with other such components (not shown) on or for mobile station 202 such as operating system, communication sub-system, PIM components, etc.
Contextual menu 604 is invoked by moving the focus 406 to designate the contact, in this example, “Chuck” 412. Menu options 606, 608, 610 in the contextual menu 604 may be navigated such as by moving the focus 612 up and down the screen. Menu options 606, 608 and 610 are generated from the associated contact information 304 to 310 for the IM contact 312 using the system and method for adding address book verbs to the IM application menus described further herein below (see
Generally, it is possible to associate an action verb or address book verb that represents a communication ability with an associated contact information entry, e.g. 304 to 312. As will be understood by those of ordinary skill in the art, communication devices such as a mobile phone may support multiple communication abilities and multiple action verbs may be associated with each ability. For example, contact information such as a mobile phone number can be associated with the action or address book verbs “Call”, “SMS Text”, and “MMS”.
In this example, menu option “Call Charles” 606 consists of an address book verb “Call” which is associated with one or more phone numbers in the contact information (e.g. 306 and 310) and the IM contact's first name “Charles” from 302. Menu option “SMS Text Charles” 608 and “MMS Charles” 610 consists of the address book verbs “SMS Text” and “MMS” which is associated with the mobile phone number contact information 310 and the IM contacts first name “Charles” from 302. Contact information entries 304 and 308 are empty and do not generate a corresponding entry in the contextual menu 602.
Navigational element 714 indicates that additional contextual menu entries may appear off screen below. Menu options 706, 708, 710 and 712 are generated from the associated address book contact information 324, 330 and 332 for the IM contact 322 using the system and method for adding address book verbs to the IM application menus describe below (see
Operations 800 provide a general overview of the actions required for adding address book verbs to the IM application menus. In the example of
At step 802, the user is presented with a contact list view (e.g. view 400) by GUI 1002 upon starting the IM application 1004. Operations 800 in response to certain pre-requisite user input such as menu driven commands or predetermined keystrokes, etc. (step 804) may branch to perform respective operations. In the simplified view, there is shown step 806 for selecting a particular IM contact from the contact list 1006 and step 808 for starting an IM conversation with an IM contact selected from the contact list 1006.
From the IM contact information, the initial email or other address used for the buddy invitation or, possibly, the contact's name is available to the IM application 1004 through user selection of the contact (step 806) or from the IM conversation window with the IM contact (step 808). In response to user input invoking the display of the contextual menu (step 810) the associated IM contact information (e.g. email address) can be used to find an address book contact record 1012 in the contact data store 1011 to prepare the address book verbs required (step 812). Step 812 is further described as operations 900 in
In one embodiment, an API for the address book application 1010 is provided to the IM application to pull information, invoking a search of the contact data store 1011 for the contact record 1012 associated with the selected IM contact (step 902). The particular address book contact record 1012 is then examined to determine which contact information entries are available. The respective associated information is provided to the IM application to create the context sensitive menu portion (e.g. 604 or 705). At step 904 it is determined which address book verbs are to be used (step 904). Some address book contact information (e.g. a phone number) will provide multiple communication abilities (e.g. phone and SMS) that require multiple address book verbs. At step 906, text for the contextual menu 1016 is generated from mapping each required contact information entry to the appropriate address book verb (i.e. action). Contextual menu text with the address book verbs is then passed to the GUI 1002 (step 908). In one embodiment, the IM application 1004 performs the steps 902, 904, 906 and 908 as described. Persons of ordinary skill in the art appreciate that different criteria may be used in determining what contact information is relevant, for example, whether the entry is completed or if the communication method is currently available. Those of ordinary skill in the art will also understand that there may not be a bright-line distinction between steps 904 and 906 and that the steps may be combined and performed together.
Various storage schemes (e.g. linked lists) and memory allocation schemes for current IM conversations 1008, current conversation messages 1014 and contextual menus 1016 may be employed. Particular contextual menus 1016 may be linked to the GUI 1002 via pointers or other known techniques for associating one structure with another.
While discussed with reference to a handheld mobile device such as a smart PDA or smart phone, IM applications may be implemented on other computing devices such as personal computers (laptops, desktops), workstations and the like configured for network communications. IM applications and IM games are commercially available (e.g. AIM™ from AOL, Yahoo! Messenger™, MSN Messenger™, etc.) for many platforms such as PCs with various Windows® or Windows compatible operating systems with sufficient memory and video capabilities. Additional software requirements may include an Internet browser and plug-ins and support for Java (e.g. JVM or plug-in support) as well as an available Internet connection.
Advantageously, alternative data communication capabilities other than IM using the same IM application can be invoked as well as voice communications from the IM application interface. Such reduces keystrokes or other user input and takes advantage of address book contact information that can be centrally maintained for use by different applications.
The above-described embodiments are intended to be examples only. Those of skill in the art may effect alterations, modifications and variations to the particular embodiments without departing from the scope of the application. The subject matter described herein in the recited claims intends to cover and embrace all suitable changes in technology.
