WO2007134302A2 - Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie - Google Patents

Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie Download PDF

Info

Publication number
WO2007134302A2
WO2007134302A2 PCT/US2007/068906 US2007068906W WO2007134302A2 WO 2007134302 A2 WO2007134302 A2 WO 2007134302A2 US 2007068906 W US2007068906 W US 2007068906W WO 2007134302 A2 WO2007134302 A2 WO 2007134302A2
Authority
WO
WIPO (PCT)
Prior art keywords
address field
field value
message
user
list
Prior art date
Application number
PCT/US2007/068906
Other languages
English (en)
Other versions
WO2007134302A3 (fr
Inventor
Robert Haitani
Sachin Kansal
Original Assignee
Palm Inc.
Donald, Richard J.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/434,504 external-priority patent/US20060288298A1/en
Priority claimed from US11/434,502 external-priority patent/US20060288297A1/en
Application filed by Palm Inc., Donald, Richard J. filed Critical Palm Inc.
Priority to EP07783746A priority Critical patent/EP2024872A4/fr
Publication of WO2007134302A2 publication Critical patent/WO2007134302A2/fr
Publication of WO2007134302A3 publication Critical patent/WO2007134302A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/26—Devices for calling a subscriber
    • H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
    • H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
    • H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
    • H04M1/27453—Directories allowing storage of additional subscriber data, e.g. metadata
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/26—Devices for calling a subscriber
    • H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
    • H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
    • H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
    • H04M1/27467—Methods of retrieving data
    • H04M1/2748—Methods of retrieving data by matching character strings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails

Definitions

  • the disclosed embodiments relate generally to the field of electronic communications.
  • the disclosed embodiments relate to a system, method and technique for enabling users to interact with address fields of messaging applications.
  • Computing devices particularly handheld and portable devices, have evolved to include numerous types of communication capabilities and functionality.
  • handheld devices exist that operate as cellular phones, messaging terminals, Internet devices, while including personal information management (PIM) software and photo-management applications.
  • PIM personal information management
  • Internet Protocol services exist that can transform Internet-enabled machines into telephony and messaging devices. Even stand-alone telephones that connect to traditional Public
  • PSTN Switched Telephone Networks
  • MMS Message Service
  • FIG. 1 illustrates a system for enabling users to interact and use address fields in connection with operation of one or more messaging applications, according to an embodiment of the invention.
  • FIG. 2 illustrates a contact lookup system for use with messaging applications, under an embodiment of the invention.
  • FIG. 3 A-FIG. 3B illustrate an implementation of the use of lookup component in connection with a messaging application, according to an embodiment of the invention.
  • FIG. 4 illustrates a method for maintaining an MRU list, under an embodiment of the invention.
  • FIG. 5A illustrates components for implementing a method such as described with FIG. 4, according to one or more embodiments.
  • FIG. 5B illustrates MRU lists for different messaging applications, under an embodiment of the invention.
  • FIG. 6 is a table that illustrates how a search string value can be used to identify address field values from both a contact record database and a MRU list, under an embodiment of the invention.
  • FIG. 7A illustrates a method in which the delimiter for an address of a message is inserted automatically, at least in part, once the address field value for the message is determined.
  • FIG. 7B illustrates an address field on which addresses can be inserted, using an embodiment such as shown by FIG. 7A.
  • FIG. 8 A illustrates an embodiment in which an address field value is placed in a selected or partially selected state for purpose of displaying or enabling the user to view information associated with the address field value, under one or more embodiments of the invention.
  • FIG. 8B illustrates an implementation of FIG. 8 A, under an embodiment of the invention.
  • FIG. 9A illustrates a method for truncating an address field value of a message, under an embodiment of the invention.
  • FIG. 9B and FIG. 9C provide an illustration of a truncation of an address field value, under an embodiment of the invention
  • FIG. 1OA illustrates components for enabling the viewing of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention.
  • FIG. 1OB illustrates a method for enabling the viewing of contact record information in connection with a displayed address field value, under one or more embodiments of the invention.
  • FIG. 1 IA illustrates components for enabling the editing and altering of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention.
  • FIG. 1 IB illustrates a method for enabling the editing and altering of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention.
  • FIG. 12A-12E are illustrations of a user-interface or address window presented with a given messaging application, describing a sequence of events by which the user can select and edit and address field value, under one or more embodiments of the invention.
  • FIG. 13 illustrates a method where editing operations of an address field can be incorporated into the operational state of a device, under an embodiment of the invention.
  • FIG. 14 illustrates a hardware diagram of a mobile computing device configured according to an embodiment of the invention.
  • Embodiments described herein facilitate the use and interaction of address fields and operations of messaging applications in different kinds of computer systems.
  • one or more embodiments described herein facilitate the use of address fields in messaging programs of various kinds, for purposes that include: (i) enabling location and selection of a new recipient address for a given message; (ii) enable retrieval and viewing of information associated with message addresses; (iii) optimize the viewing of message addresses on small form-factor devices (e.g. mobile computing devices); and/or (iv) enable address field editing in a manner that requires minimal user-effort.
  • Embodiments described in this application may be implemented on any type of computer that is connected to a network or communication medium to enable transmission and/or reception of messages carried over networks.
  • a mobile computing device such as a cellular computing device, wireless messaging device, personal digital assistant, or hybrid/multi-functional device for enabling cellular voice and data transmissions.
  • These devices typically have relatively limited display sizes, processing resources, and display area.
  • the ease of use and flexibility provided by embodiments described herein, in connection with addressing messages has benefit to such devices, as functionality described in connection with such embodiments compensates for the relatively more limited resources such devices typically have.
  • embodiments described herein may also be implemented by desktop computers, laptop computers, and large profile computers.
  • An embodiment described herein enables a user to operate a messaging application on a computing device.
  • An input is received for an address field of a message that is to be transmitted from a messaging application.
  • a contact record is associated from the input with the message.
  • a recipient address is selected from the identified contact record for use as an address field value.
  • An input is detected from the user, and subsequently, the user is enabled to edit the address field value.
  • the user is enabled to edit the address field value by either allowing the user to select a new recipient address from the identified contact record, or by allowing the user to create an alternative recipient address that is not part of the contact record.
  • an input is received from the user that specifies a recipient address for an address field value of a message.
  • An identifier of a contact record is displayed that contains the recipient address of the address field value.
  • information, additional to the recipient address, from the contact record is displayed.
  • information is identified about a recipient of a message that is composed or transmitted from the computing device using the one or more messaging applications.
  • a list entry may be formed, where, if an address field value of the message is associated with a contact record, the contact name or identifier is included in the list entry.
  • the list entry may display a recipient address of that message.
  • the list may be updated to reflect recipients that have been most recently messaged.
  • input is received for an address field of a message.
  • the recipient address of the address field is established from the input for the message.
  • the recipient address, or an alternative identifier associated with the recipient address is then displayed in a view.
  • the view is the address line on which the recipient address is provided.
  • the view may be in the form of a window or other display. The user can edit the recipient address from the view.
  • One or more embodiments further provide for a view, panel, or interface (alternatively or collectively referred to as a "panel" containing an address field in which a user can select, compose or otherwise specify an address field value.
  • Logic may be associated with the panel to enable the user to edit the address field value on the address line, even after the address field value is established atomically for messaging operations.
  • address field refers to a property of a message that is provided an address or other identifier of a recipient.
  • An example of an address field is the "TO:" field in an email or text message.
  • address field value means one or more values assigned to an address field of a messaging application.
  • An address field value may have a display component and a recipient address.
  • the display component of the address field value includes characters that are displayed to the user for the address field value at a given instance.
  • the recipient address includes characters that identify the address, location and/or destination of the message that is to be transmitted.
  • the address may correspond to the email address, while the display component may be a name of a contact record in which the email address may be found.
  • the address component of the address field value is selectively or intermittingly viewable to the user. The following is illustrative:
  • the address field is "TO:"
  • the address field value is "John” ⁇ John.Doe@palm.com>
  • the display component of the address field value is "John”
  • the address portion of the address field value is John.Doe@palm.com.
  • the address portion may be hidden, or selectively/intermittingly viewable.
  • the display component of the address field value is also not always necessary, as the address field value may correspond to just the address (e.g. John.Doe@palm.com).
  • embodiments described herein facilitate the user in overcoming some of the limitations normally present with such small- form factor devices.
  • embodiments described herein facilitate the user's ability to enter input for an address field value, to view the address field value, and also to view information associated with the address field value (e.g. information from an associated contact record).
  • embodiments described herein promote an intuitive approach for user's to communicate with desired recipients, regardless of the type of transport selected for the communication.
  • Computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on many cell phones and personal digital assistants (PDAs)), and magnetic memory.
  • Computers, terminals, network enabled devices e.g. mobile devices such as cell phones
  • processors, memory, and instructions stored on computer-readable mediums are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums.
  • a programmatic module or component may include a program, a subroutine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions.
  • a module or component can exist on a hardware component independently of other modules or components.
  • a module or component can be a shared element or process of other modules, programs or machines.
  • FIG. 1 illustrates a system for enabling users to interact and use address fields in connection with operation of one or more messaging applications, according to an embodiment of the invention.
  • a system 100 includes multiple messaging applications that can be operated to send different kinds of messages.
  • the messaging applications include an email application 110, a Short Message Service (SMS) application 120, and a Multimedia Message Service (MMS) application 130.
  • SMS Short Message Service
  • MMS Multimedia Message Service
  • Each of these applications are representative of a particular kind of transport, enabling handling of messages of particular types and formats for the particular application.
  • Numerous other kinds of messaging or communication applications may be incorporated with one or more embodiments of the invention. For example, instant messaging applications, or even communication applications that involve voice data may be used with one or more embodiments described herein.
  • System 100 includes a library 140 of resources that are shared by the different messaging applications 1 10-130 for purpose of enabling use and interaction of address fields with messaging applications.
  • the library 140 includes components that include one or more of a rendering engine 162, an addressing editor 164, a lookup feature 166, and a list manager 168. Each of these components may be used and/or operated through each of the messaging applications 110-130.
  • system 100 may have access and use of a contact database 150.
  • the contact database 150 includes multiple contact records 152 identifying persons or entities that a user of the system 100 may exchange communications with or otherwise contact.
  • Information that may be maintained by individual contact records 152 may include a first name, last name, company/employer name, phone number list (including home phone number, mobile number, fax number), email address, alternative email address, and instant messenger identifier.
  • An SMS or MMS identifier other than a mobile phone number may also be specified.
  • the individual contact records 152 may include contact record identifiers, which are displayed to identify the record in various contexts. In many typical cases, the contact record identifier corresponds to values provided by the field for the first name, last name or combination thereof (e.g.
  • the library 140 includes an indexer 146 that indexes data from the contact database 150.
  • Other types of databases, record stores, and record types e.g. event logs, calendar records
  • the indexer 146 generates an index 145 from data contained in individual records of contact database 150.
  • the index 145 may associate strings of characters on different contact record fields with pointers to individual records that contain those character strings on the various contact record fields. In this way, the index 145 may enable a search interface to identify individual records 152 that match search criteria specified by a user, including search criteria that is in the form of a character string.
  • index structures and search algorithms may be used to match contact records to search criteria.
  • the character string of the search criteria is matched to select field values of a contact record.
  • the character string may be compared to field values that, in a given contact record, correspond to a first name, last name, company name, phone number (e.g. home phone number, mobile number, fax number), email address, alternative email address, and instant messenger identifier.
  • the search interface may be provided by the lookup component 166.
  • the lookup component 166 is configured to enable a user to enter a series of alphanumeric character entries.
  • lookup component 166 scans the index 145 to identify records with field values that match the entered series of letters and numbers.
  • the lookup component 166 (or the rendering engine 162) returns information from the contact database 150. This information may correspond to the display of select field values from individual contact records 152 that match the alphanumeric entry of the user.
  • the information identified from individual contact records 152 is filtered to exclude fields, values or information that is not pertinent to the messaging application from which the lookup component 166 is operated.
  • the lookup component 166 may exclude, for example, non-mobile phone numbers and the person's home address, but include field values assigned to the email addresses and the mobile number fields of the contact record.
  • the lookup component 166 enables a person to select a contact record for an address field without having to manually enter all the characters of the contact record or its recipient address. Rather, the user may enter one or more characters into a text entry field provided as part of the lookup component 166.
  • the lookup component 166 uses the entered characters to identify from the index 145 contact records that have fields that match the entered values.
  • the matching contact records are displayed to the user in some form, and the user can enter navigation and selection input to select a record for an address field value.
  • the display component of the address field value may correspond to an identifier of the contact record.
  • the recipient address may correspond to one of the field values from the contact record identified as the address field value.
  • each of the messaging applications 110-130 may enable use of the lookup component 166.
  • the lookup component 166 uses the alphanumeric entry of the user to scan the index 145 for field values that are pertinent to the particular application from which the lookup component 166 is called.
  • the lookup component 166 may be called through use of the email application 110.
  • a specific character entry causes a scan of the index 145, but only for field values that are deemed pertinent to the email application 1 10. These field values may be different than those scanned for another application, such as SMS application 120 or MMS application 130.
  • the field values scanned are the first name and last name of the contact record, as well as the corporate entity of the contact record. What is used as the recipient address may correspond to a field value contained in the record. This field value may be determined programmatically, based on the messaging application that uses the lookup component 166. Alternatively, multiple possible recipient address may be contained in a given contact record, and the user may need to specify which recipient address to use.
  • the rendering engine 162 affects the manner and content that is displayed with or as the address field value of a composed message.
  • system 100 has information about the recipient identified in the address field value of a composed message. This information may be in the form of (i) a name of the person, (ii) alternative address of the recipient, and/or (iii) information derived or contained in a contact record associated with the recipient.
  • the rendering engine 162 enables other information from the contact record to be viewed by the user selecting or putting the address field value in focus.
  • the rendering engine 162 enables the view of the additional information to take place in the presence of the composed message, so that the user can view the additional information with the address field value.
  • a fly-out window may be used to temporally display information from the contact record of a recipient to a user.
  • the address editor 164 enables the address field value of a composed message to be edited, even after the address field value has been established edited by the messaging application. An address field value may be deemed established when the messaging application on which the message is composed recognizes the address field value as an atomic object. As an atomic object, the entire address field value may, for example, be deleted with one action.
  • the address editor 164 enables the address field value to be edited "in-line" on an addressed message.
  • the address of a message e.g. email or SMS
  • the address of a message can be edited on the line where the address field value was entered and then subsequently displayed, even when the address field is established as an atomic object.
  • many existing applications allow uses to enable the address field value after it is established, but in a separate window or display area.
  • the ability to perform in-line edits on addressed messages promotes ease of use, as the small screen limits the ability to enable edits on separate windows or interfaces.
  • the list manager 168 is another mechanism that enables a user of the device to select an address field value without manually entering the recipient address in its entirety.
  • the list manager 168 may maintain one or more lists, where each entry on a given list corresponds to a recently transmitted or composed message.
  • the user may select to view a given list and make a selection of a list entry. In one implementation, this would provide the user with an alternative to selecting an address field value through use of the lookup component 166, or through manual entry of the entire address field value.
  • the list or lists maintained by the list manager 168 are "most recently used" lists (e.g. the ten most recently used).
  • different lists, or different sets of list entries may be provided for each messaging application 110-130 that uses the library 140.
  • the user may operate the email application 110 to view a short list of recent addresses used through operation of that application.
  • the user may then operate the SMS application 120 to view different list entries through operation of that application.
  • FIG. 1 illustrates the library 140 shared by the different messaging components as having numerous components, other embodiments provide for fewer or more components to be shared amongst the applications. Several embodiments are described below, which may or may not be implemented with other components and functionality described with FIG. 1.
  • FIG. 2 illustrates a contact lookup system for use with messaging applications, under an embodiment of the invention.
  • a contact lookup feature such as described by FIG. 2 may be shared across multiple messaging applications for purpose of enabling a user to enter alphanumeric characters in search of matching contact records.
  • components described with the lookup system of FIG. 2 may correspond to elements described with FIG. 1 (e.g. lookup component 166), which are shared amongst applications.
  • the user can take the additional step of selecting a particular matching contact record, or selecting an address field value contained in one of the matching contact records.
  • the address field value includes the contact record identifier as the display component, and an address value (e.g. mobile phone number or email address) as the recipient address of the address field value.
  • the lookup component 210 includes a message application interface 212 and a record retrieval function 214.
  • the lookup component 210 may interface with a contact record database 250, as well as with an index 240.
  • the lookup component 210 is provided for the email application 202, the SMS application 204, and the MMS application 206, although other types of messaging and communication applications are also contemplated.
  • Sandra of these applications may be operated to access and use the lookup component 210.
  • the user operates one of the messaging applications to enter a search string 222 for the lookup component 210.
  • the user may use selection input on the address field to view or activate the interface 212 of the lookup component 210.
  • the user can enter an alphanumeric search string (e.g. through operation of a keyboard).
  • the search string may correspond to, for example, (i) the first few characters of a first name or last name of a contact record, (ii) multiple characters that correspond to a combination of initials, or a combination of first and last name of a contact record (e.g. initials of first and last name, or two letters from first name, one from last name), (iii) corporate name, or (iv) other field value of a contact record, such as the field value of one of the address fields.
  • the following lookup rules may be applied to a given search string: First two letters that are entered are matched as follows: (i) First name, last name (ii) Last name, first name, (iii) First name only, and (iv) Last name only.
  • the third letter is interpreted as follows: (i) Next letter in first name, (ii) Next letter in last name only, (iii) Second letter in last name (first letter matching first name).
  • lookup algorithms may be employed with embodiments described herein.
  • the algorithms may be shared or distributed through a library and interface that is shared by multiple messaging applications.
  • Another lookup algorithm provides for the use of a space character between two characters in an input sequence.
  • the lookup algorithm matches a sequence of two or more characters based on the following: (i) first initial / last name, (ii) last initial / first name, (iii) first name, and (iv) last name.
  • the space character is used as a delimiter between first and last name.
  • the search sequence "bob jo" can match "Bobby Johnson" or "Bob Jorkney” or "Joe Bobanson".
  • lookup component 210 may be shared by the different messaging applications, the functionality of the lookup component 210 may be tailored for the particular messaging application. For example, when email application 202 is operated in connection with the lookup component 210, the string 222 may be compared against field values for email addresses. As another example, if the messaging application that uses the lookup component 210 is an instant messaging application, the reverse lookup of the characters may be directed towards a field value that is known to provide an instant messaging identifier.
  • the interface 212 may receive the search string 222, and submit perform a scan 224 or search of the index 240 using the search string 222.
  • the index 240 is structured so that the search string 222 implements a search protocol, defining what fields are to be searched, and how the search string 222 may be divided or sequenced to match a given field value. For example, two characters that are letters may be searched against (i) first two characters of the first names, (ii) first two characters of last names, or (iii) initials of first name and last name. Two characters that are numbers may be searched against fields that are phone numbers only. In this way, the index search may carry over different combinations of the search string 222 to identify matching records from the contact database 250.
  • the identification of the records may be carried to the interface 212 in the form of identifiers 226 of contact records that were deemed to be matching.
  • Record identifiers 226 are communicated to the record retrieval function 214, which locates the corresponding records from the database 250.
  • the record retrieval function 214 may then inspect individual records and retrieve record information 228 from those inspected records.
  • the record information 228 is then displayed to the user. In an embodiment shown by FIG. 2, the record information is displayed to the user by the rendering engine 162.
  • the user may be provided a choice of selecting a contact record for insertion of an address field value in a given message, or alternatively viewing information from the contact record identified from the index 240.
  • FIG. 3 B illustrate an implementation of the use of lookup component 210 in connection with a messaging application.
  • a view 272 of an open, unaddressed message is presented to the user from which the user can address a message, provide a subject line and/or compose a body.
  • An address field 273 is shown that the user can address the message, although more than one address field can be used (e.g. "CC" or "BCC").
  • the lookup component 210 may be initiated by the user entering characters in the address field 273, and/or by the user selecting the address field ("TO").
  • a fly-out window 275 is displayed in response to the user's character entry.
  • the window 275 may display contact records identifiers 282 that match the user's input in the address field 273.
  • the rendering engine 162 may display the window 275 in response to the character entry.
  • the record information 228 may be displayed in the form of field values 283.
  • the user can scroll or navigate in the window 275 to see additional record information.
  • the user can also select a contact record, and/or one of the field values 283 displayed with one of the contact records in the window 275.
  • FIG. 3B illustrates the result of the user selecting an address field value from the window 275.
  • the user selects a contact record identifier, and then the recipient messaging identifier for use with the message is automatically selected by some selection rule (e.g. "always use the email address, unless specified otherwise").
  • the user specifies one of the field values, such as the mobile number of an email address contained in the record information for a particular contact record.
  • the recipient messaging identifier portion of the address field value is provided or based on the selected field value.
  • the display component portion of the address field value may or may not correspond to the contact record identifier.
  • the address field value 278 corresponds to the recipient address.
  • a set of filter rules 260 influence or control what portion of the record information 228 is displayed from interface 212 so that record information 228 is pertinent to messaging. For example, certain fields may be assumed to not be pertinent to messaging: email addresses and mobile phone numbers. Other fields may be assumed to not be usable as recipient messaging identifiers: home phone numbers, mailing address, title, notes, fax number.
  • the filter rules 260 when implemented, cause the record information 228 to be filtered so that when it is rendered to the user, what is displayed are field values that can be used as addresses for messaging applications.
  • the filter rules 260 may be based on what application is running, so that the displayed field value provides an address or identifier for that particular application. For example, for an instant messaging application, the displayed record information may omit all field values for phone numbers and messaging, but for the instant messenger identifier of the intended recipient.
  • the lookup component 210 allows the user to (i) quickly specify, through a small set of alphanumeric entries, a contact record identifier as an address field value, and (ii) have the recipient address determined and inserted for the address field value, either automatically or through selection/navigation input.
  • the user does not have to enter the entire recipient address, or even know what the recipient address is when entering the address field value. The user may simply rely on knowing the name of the person who he wishes to contact, and the recipient address can subsequently be identified programmatically when the contact record is identified, or by the user (through navigation/selection input).
  • MOST RECENTLY USED LISTS MOST RECENTLY USED LISTS
  • Embodiments described herein enable the use of one or more lists in connection with operation of the some or all of the messaging applications that can be operated on a computer or mobile computing device.
  • one or more embodiments provide for a most-recently used (“MRU") list to be associated with different messaging applications.
  • the MRU list may be maintained separate from the contact database, and provide the user with another alternative means by which an address field value can be selected for a message.
  • a MRU list is updated with the transmission of individual messages from a given outgoing message. For example, when a message is transmitted from a mobile computing device, each recipient address of the outgoing message is added to the MRU list for that application. The new entries take the place of old entries, so that the MRU list reflects recent communications.
  • FIG. 4 illustrates a method for maintaining an MRU list, under an embodiment of the invention.
  • a method of FIG. 4 is described in the context of a mobile computing device, such as one that transmits and receives data over cellular networks.
  • a mobile computing device such as one that transmits and receives data over cellular networks.
  • other embodiments may implement a method such as described with other kinds of computers.
  • a message is composed or transmitted from the mobile computing device.
  • the message may be transmitted using anyone of many messaging applications that can be operated on a computing device, including an email application, an SMS application, an MMS application, or an instant messaging application.
  • step 415 a determination is made as to whether an address field value of the composed or transmitted message specifies a contact record stored on the mobile computing device. For example, the user may spell out an email address, not realizing the email address is in a contact record.
  • step 415 If the determination in step 415 is that the address value of the outgoing message does specify a contact record, then a list entry corresponding to the contact record identifier is added to a MRU list in step 420. While the list entry may be displayed as the contact identifier, but some designation may be made as to which field value of the identified contact record contains the recipient address of the outgoing message.
  • the address field value of a message may specify a contact record identifier, in which case the recipient address may be contained by that record. In other cases, the address field value displays only the recipient address, and this identifier may or may not correspond to one of the contact records. If in step 415, the address field value does not display or correspond to a contact record identifier, then in step 430 the recipient address is identified. A determination is made in step 435 as to whether the recipient address has correlation to one of the contact records.
  • functionality described with the lookup component 210 may be used to perform a reverse-look up operation, where the address of the transmitted message is compared against field values of the contact records stored on the mobile computing device.
  • the index 240 may also be used to identify field values in contact records having the message.
  • step 435 If the determination in step 435 is that there is correlation between the recipient address identified in step 430 and one of the contact records, then step 420 is performed, where the list entry is made with the contact record identifier that contains the recipient address. Otherwise, in step 440, the recipient address is used as the list entry.
  • FIG. 5A illustrates components for implementing a method such as described with FIG. 4, according to one or more embodiments.
  • a list manager 510 may maintain and update a list 512.
  • the list manager 510 may be incorporated into the shared library 140 to maintain the list for one or more of the messaging applications 520.
  • the list 512 that is maintained and updated by the list manager 510 may be maintained in a manner similar to the index 145. Specifically, the list 512 may be maintained in RAM, where it is permanent, unless there is a hard reset event.
  • the list manager 510 may be shared by multiple messaging applications 520.
  • the messaging application 520 may correspond to, for example, email, SMS, MMS, or instant messaging applications.
  • the application supplies the list manager 510 with the address field value.
  • the address field value may include either a contact record identifier, a recipient address that has a corresponding contact record identifier, or a recipient address that has no corresponding contact record identifier.
  • the list manager 510 may perform a method such as described with FIG. 4 to determine a list entry 532, so that each outgoing message generates at least one list entry.
  • the list entry 532 may correspond to either a contact record identifier or a recipient address.
  • the list manager 510 forwards each list entry 532 to a master list 540.
  • the list manager 510 may also include an application code or identifier 544 that identifies the particular messaging application 520 that generated an individual list entry 532.
  • the application code 544 enables master list 540 to be a source from which different MRU list 552s can be generated for each of the messaging applications 520.
  • the application code 544 enables subsets of list entries 532 to be identified from the master list 540. Each subset of list entries 532 may be presented as a separate MRU list 552 that can be called from one of the corresponding messaging applications 520.
  • the recipient address of an SMS message and of an outgoing e-mail message may each form separate list entries 532 on the master list 540, but each of the recipient address has a different application code 544 which identifies the particular list entry as belonging to the SMS messaging application or email messaging application respectively.
  • the rendering component 550 may be used to identify subsets of list entries 532, and to form MRU list 552 from those list entries for use with individual messaging applications 520.
  • the rendering component 550 may correspond to the rendering engine 162 of the library 140, which is shared by the different messaging applications 520.
  • each generated MRU list 552 enables each generated MRU list 552 to be used to perform one or more of the following: (i) view address field values of recent or most recent outgoing messages using the given messaging application; (ii) when applicable, view the contact record information associated or identified by the address field value, and enable the user to select recipient address from the displayed record information; (iii) select a recipient address for a new outgoing message, using either the message recipient identifier that corresponds to the list entry, or one of the recipient address that is included in a contact record identifier by the list entry.
  • each list entry 532 is an actionable data item, in that selection of the list entry may result in different operations being performed.
  • a full selection of a list entry e.g. double click
  • a partial selection e.g. placement in focus
  • individual list entries may be used to address messages and view information such as contact record information (as the case may apply).
  • the address field value identified by each list entry 532 may also be subjected to a view and edit operation by the user.
  • the edit to the address field value may be performed "in-line" on the message.
  • the edit of the address field value may cause the rendering component
  • FIG. 5B illustrates MRU lists 552 for different messaging applications, under an embodiment of the invention.
  • a separate MRU list 552 may be maintained for the email application, the MMS application, and the SMS application.
  • Each MRU list 552 comprises multiple list entries 532.
  • the number of list entries 532 on each list 552 may be designated at some number (e.g. 10), so that the addition of each list entry 532 to the MRU list means the oldest list entry is dropped from the MRU list 552.
  • individual list entries may be displayed as contact record identifiers 558, or recipient addresses 562.
  • an additional code 564 indicates which field value from that contact record was used as the address of the outgoing message.
  • the contents of the list 540 may be made available to the lookup functionality, so that when a lookup operation is performed, the sources checked include both the contact record database 250 and the list 540 (or alternatively one or all of the MRU lists 552).
  • the data sources checked by the lookup component 210 include the index 240 (which points to the contact database) and the list 540.
  • different protocols may be used when checking the list 540, as opposed to the contact record database 250. This may be a result of the use of the index 240 when checking the record database 250.
  • matching the search string 222 to a contact database may include (i) matching a first character to a first name, and a second character to a last name (initials search), or (ii) a reverse address lookup. Under one implementation, for example, when the search string 222 is used against the list 540, neither the initial search or the reverse address lookup are performed.
  • different search or matching algorithms may be used to match one search string to address field values and contact records from two different sources: the contact record database 250 (via an index 240) and the list 540.
  • FIG. 6 is a table that illustrates how a search string value can be used to identify address field values from both a contact record database and a MRU list, under an embodiment of the invention.
  • a far left column 610 represents a search string value 602.
  • Adjacent middle columns 620 and 630 show the source (contact database or MRU list) from which a match to the search string value 602 was found.
  • a far right column 640 shows rendered results 612 of the lookup function as a result of searching against the contact database and the MRU list.
  • the rendered results 612 may be provided by the rendering engine 162 (FIG. 1).
  • FIG. 6 illustrates several examples of how lookup functionality can be integrated with the MRU list, and the configurations and scenarios presented should only be considered as optional features or configurations.
  • the search string value 602 is used to identify a contact record identifier (first name, last name).
  • the protocol permits the search string value 602 to be used to identify initials, or the first letter of the first name and last name.
  • the MRU contains a contact record identifier as a list entry. The search of the list entry and the contact database yields the same result.
  • the lookup component knows that certain protocols, such as first initial last initial search, apply to all contact record identifiers in the search domain, regardless of whether the contact record identifier is in the MRU list or in the contact database.
  • the search string value 602 is changed so that it only matches one of the email addresses of the contact record shown.
  • the third case illustrates an implementation in which email addresses are only searched as part of the lookup functionality when the email addresses are one of the list entries for the MRU list.
  • the email address is either not present in any contact records of the database, or the list manager is configured to not convert email addresses and other recipient address to contact record identifiers.
  • the result that matches the search string value 602 is only in the MRU list, and the lookup component in the case provided does not search email addresses or other field values of individual contact records.
  • the fourth case illustrates an implementation where the search string value is only used to search contact record identifiers of the contact database, and not other field values, such as email addresses in contact records. As such, if one of the contact records has a field value (email address field) that matches the search string value, but the list entry does not use that address, the search string returns no results. [090] With regard to the examples provided by FIG. 6, it should be apparent that numerous variations and alterations are possible. As shown by FIG. 6, it should be apparent that numerous variations and alterations are possible. As shown by FIG.
  • delimiters indicate when one address field value ends and another starts.
  • the addresses provided for each recipient may be delimited by a character such as a semi-colon or comma.
  • delimiters With mobile devices and other small-form factor devices, the insertion of delimiters is typically a multi-step effort. Even with small form-factor devices that offer QWERTY keyboards, the character that designates the delimiter is often an alternative mode of another key. With devices that use a numeric keypad layout (such as those that use predictive text), delimiters can be even more difficult to find and use. With regard to small form factor devices in general, fewer key strikes and input actions is preferred, particularly in address messaging.
  • FIG. 7 A illustrates a method in which the delimiter for an address of a message is inserted automatically, at least in part, once the address field value for the message is determined.
  • a method such as described with FIG. 7 A may be used with any of the embodiments described elsewhere in this application.
  • a method of FIG. 7A is described in the context of a system such as shown and described with FIG. 1.
  • reference to elements of FIG. 1 is intended to describe only a suitable element for performing a step, sub-step or action being described.
  • step 710 user-input for an address field is received.
  • the input may be in the form of selection input, such as through use of lookup functionality, list entry selection of an MRU list, or other operation where the user selects a data item corresponding to the desired address.
  • the input may also correspond to character entry, where the user spells out, for example, an email address or mobile phone number as the recipient location for a message.
  • the input that the user selects for the address field may not necessarily correspond to the message address, but rather invoke the message address by association.
  • the input may identify a contact name (e.g. name of recipient), rather than the actual message address in long form.
  • step 720 the address of the message is identified as being complete.
  • the message address may be specified in one of several ways. Some of the possible ways in which the message address is identified as complete are shown with the sub-steps described below.
  • Sub-steps 722 and 724 provide that the user-input specifies or selects a contact record, and an address from the specified or selected contact record is then inserted for the address field of the message.
  • a contact record may be specified by the user performing a lookup using a small number of search strings. The contact record may also be selected using navigation or other features where the contact record identifier is displayed or the contact record is made available.
  • the user may specify a name of a person to look at that person's contact record, then the user may select the mobile phone number from that contact record.
  • Sub-steps 732 and 734 provide that the user's input specifies or selects a list entry from one of the MRU lists, then the address identified by the selected list entry is inserted in the address field of the message. Under one implementation, specification of the list entry also automatically selects an address, even when the list entry specifies a contact record.
  • Sub-step 742 provides for the case where the user spells out the address or contact identifier for use as an address field value. For example, the user may enter each character of an email address, mobile phone number, or contact name.
  • step 750 provides that the delimiter used by the particular messaging application is automatically inserted after the completed message address. For example, some messaging applications use a semicolon, while others a colon.
  • step 755 a determination is made as to whether the user wishes to enter another address for a message.
  • the automatic placement of the delimiter in the address field results in the cursor or prompt to be positioned just after the inserted delimiter, so that the next addressee of the same message can be specified without the user having to enter a space or otherwise position the cursor on the display.
  • the method is done, and the address field is complete. Otherwise, if the user has additional addressees, the method returns to step 710, where the user enters input to specify or select the next address for the outgoing message.
  • the delimiter insertion is performed by the rendering engine 162.
  • the logic that inserts the delimiter may also count the number .of delimiters that are used in a given message, to ensure that no delimiter is automatically inserted in the address field when the maximum number of addressees permitted by the application are provided for in the address field of the message.
  • step 750 a determination is made as to how many delimiters are present (or whether more addressees can be included after insertion of one more delimiter), and if another addressee or delimiter cannot be inserted, the method ends without re-performing step 750.
  • FIG. 7B illustrates an address field 780 on which addresses can be inserted, using an embodiment such as shown by FIG. 7A.
  • the user specifies a mobile number 782, an email address 784, and an alternative phone number 788.
  • the mobile number 782 may be selected by the user looking up or otherwise selecting the contact record for "Wolf Larson”.
  • the delimiter 785 is programmatically and automatically inserted after the first entry.
  • the email address 784 may be selected or identified from the contact record for "Wolf Larson". The act of selecting an address field value from a list or other presentation causes automatic insertion of the delimiter 785.
  • the delimiter 785 is programmatically and automatically inserted after the second entry.
  • the delimiter 785 may be inserted by any of the following: (i) a programmatic determination that the address provided is complete - for example, upon ten numbers being inserted (in a domestic phone number), the delimiter 785 may be inserted automatically; (ii) the user may perform some action or trigger (other than a character input that specifies the delimiter) to insert the third delimiter. For example, the user may press selection input after completing the phone number to trigger insertion of the third delimiter 785.
  • an address field value may have information associated with it.
  • the address field value may correspond to a contact name, in which case the associated information includes information contained in the contact record.
  • the address field value may also include a message address without a contact name, in which case associated information may include the contact name, or the known name of the recipient identified by the message address.
  • the address field value is an abbreviated name or moniker for a person, and the additional information identifies the person's full name and/or message address.
  • numerous other kinds of information may be stored or maintained to be associated with a given recipient. For example, information that is associated with a message address may correspond to the last message sent to the user, or time and date of the previous communication to that recipient.
  • FIG. 8A illustrates an embodiment in which an address field value is placed in a selected or partially selected state for purpose of displaying or enabling the user to view information associated with the address field value.
  • An embodiment such as shown and described with FIG. 8A may be described in the context of a system such as described with FIG. 1. As such, reference may be made to elements of FIG. 1 for purpose of illustrating a suitable component for performing a step, sub-step, or operation being described.
  • Step 810 an address field value of an addressed, transmitted or stored message is displayed.
  • the user may complete addressing an email, or the user may select to view addressing information from an email in an sent folder or inbox folder.
  • Step 820 provides that input is received indicating that the user wishes to see information associated with the address field value.
  • the detection is of input that places a given address field value in a selected or partially selected state. For example, the user may place in focus an address field, so that the address field is highlighted. In a focus state, additional input may cause further actions to be performed. For example, another selection input following placement of the address field value into the focus state may cause the address field value to be lost its atomic state and to be placed in an editing mode.
  • step 830 information associated with the address field value is displayed.
  • the address field value corresponds to a contact name
  • placement of the address field value in focus causes information from the corresponding contact record to be displayed.
  • the user's input to select viewing additional information is a lookup operation.
  • the lookup component 166 may retrieve contact record information for a contact name identified in the address field.
  • the rendering engine 162 subsequently displays the contact record information.
  • the information displayed from the contact record is centric, or at least pertinent to the messaging application that the message being addressed is generated from.
  • the contact record information displayed shows field values that are legitimate email addresses. This may exclude non-mobile phone numbers, fax numbers, and home numbers.
  • the contact record information shows field values likely to be pertinent to the user from the given application.
  • the email application while the user may be able to send an email to a mobile phone, the user is more likely to want to send the email to an email address, as transmission between phones is likely to be in the form of an SMS or MMS communication.
  • FIG. 8B illustrates an implementation of FIG. 8A, under an embodiment of the invention.
  • an address field 850 includes an address field identifier 852 represented by a contact name.
  • the contact name 852 has associated with it information from a corresponding contact record.
  • the user may provide input to indicate a desire to see information associated with the address field value (e.g. place the address field identifier 852).
  • a window 860 is generated in which select information from the record of the contact name is displayed.
  • the information selected for the contact record may be information that is most pertinent to the use of the particular messaging application. For example, when the email application is in use, the address field information from the contact record may display alternative email addresses when the address field is provided.
  • the contact name 862 an email address
  • a mobile number 866 (which may receive email messages) are displayed.
  • FIG. 9A illustrates a method for truncating an address field value of a message, under an embodiment of the invention.
  • step 910 the display component of an address field value is identified.
  • the display component of the address field value is the message address.
  • embodiments may also apply to the case where the address field value corresponds to a contact name.
  • step 915 a determination is made as to whether the address field value exceeds a designated length.
  • the number of characters that form the address field value are compared against a number indicating the need to distribute the address field value on more than one line.
  • the designated character number may be a static designation, meaning the number never changes.
  • the designated character number may be dependent on the particular usage and conditions. For example, the display window where the address is being composed may be made smaller by the preference of the user. Alternatively, an embodiment may take into account the fact that another message addresses is present on the same line, and that it may be preferable to place all addresses on one line.
  • the determination of the length of the message address may be based on factors other than character count.
  • other implementations may utilize screen position, or measure a physical length of the message address.
  • step 915 determines whether the address field value does not exceed a size limit. If the determination in step 915 is that the address field value does not exceed a size limit, then step 920 provides that the address field value is displayed with no alterations or truncations.
  • step 930 the display component of the address field value is truncated.
  • this corresponds to the message address (e.g. the email address).
  • Other implementations may provide for the contact name to be truncated. Truncation may follow rules or protocols, so that preferred information about the address message is viewable.
  • the user may wish to enter a message address. Numerous techniques exist to enable the user to edit the address field (see FIG. 1 IA and FIG. HB). An embodiment recognizes that in an edit mode, it is better to display the entire address field value to the user. Accordingly, as an optional and occasional step, step 940 provides that if the address field value is placed in an edit mode, the message address is displayed in its entirety.
  • FIG. 9B and FIG. 9C provide an illustration of a truncation of an address field value, under an embodiment of the invention.
  • truncation is performed for the case where the address field value is a recipient address.
  • An implementation shown by FIG. 9B and FIG. 9C provide for the case where the recipient address is an email address.
  • the address field value corresponds to an email address 962, having a name component 972 and a domain portion 974.
  • FIG. 9B illustrates an untruncated email address, in which the name component 972 is longer than normal.
  • 9C illustrates the same email address 962 truncated, so that it can be viewed on one line, or otherwise fit to accommodate a given space.
  • Truncation can be rendered in numerous ways. For example, an abbreviated symbol may be used to indicate truncation occurred. Such a symbol may correspond to ellipses "" or other characters. Still further, truncation may correspond to a simple removal operation, with no characters indicating truncation occurred. With reference to an embodiment such as described with FIG. 1, the rendering component 162 may be used to perform the truncation.
  • one or more truncation rules may be applied to enable viewing of an email address in an addressing field.
  • the truncation rules provide that what is truncated first (as a priority) is the portion of the name component 972 that can be assumed to be attributable to letters of a person's last name. The last name portion of the name component 972 is truncated thus truncated before truncating any other portion of the email address 962.
  • Embodiments described with FIG. 9A and 9B may be implemented with different kinds of messaging applications, and with messages in various stages or states. For example, one or more embodiments described above may be implemented on an email in an open state (including in a state of composition), or to an email listed in a folder (inbox, sent item). Furthermore, embodiments described above may be implemented with types of messages other than email. [128] ADDRESS FIELD VIEWING
  • One or more embodiments described herein provide for the viewing of contact record information from address field values that include contact names. In particular, one or more embodiments provide for displaying contact record information to the user in response to some action that user performs on the address field or its value. The information is displayed with minimal interference to the user's operation of the messaging application from which the contact record information was requested.
  • FIG. 1OA illustrates components for enabling the viewing of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention.
  • a messaging application 1010 communicates with a rendering engine 1020.
  • the rendering engine 1020 may be one the resources in a library that is shared amongst different applications.
  • a system such as described with FIG. 1OA may be implemented through the system 100, as described with FIG. 1, with the rendering engine 1020 having correspondence to the rendering engine 162 of FIG. 1.
  • the messaging application 1010 e.g. email application
  • the user enters view input 1014, which is communicated to the rendering engine 1020.
  • the input may be in the form of the user entering selection input (e.g. through use of a multidirectional member) on an address field, causing a contact name that appears as the address field value to appear in focus.
  • the rendering engine 1020 is able to identify and retrieve record information 1024 from a contact database 1040.
  • the record information 1024 may be filtered with rules 1025, either by the rendering engine 1020 or by another component that assists the rendering engine 1020 (e.g. a lookup component) is retrieving the record information.
  • the filter rules 1025 may remove information from the contact record that includes field values that are not pertinent for use of the messaging application 1010. For example, in the case of email, home phone numbers are removed from the information in the contact record.
  • the rendering engine 1020 displays pertinent record information 1012 to the user.
  • the pertinent information 1012 may correspond to the legitimate email addresses that the contact record specifies for the particular name.
  • FIG. 1OB illustrates a method for enabling the viewing of contact record information in connection with a displayed address field value, under one or more embodiments of the invention.
  • a method such as described with FIG. 1 OB may be used in connection with, for example, a system such as described by the system of FIG. 1OA. Accordingly, reference to elements of FIG. 1OA, or any other figure, is intended to show only suitable elements, components or functionality for performing a given step, sub-step or operation.
  • step 1050 view input is detected by the messaging application 1010.
  • the view input is detected on an established address field value.
  • An established address field value is one that the messaging application 1010 recognizes as an atomic data item. For example, when a user enters an address field value, the messaging application 1010 waits until a determination that the address field value is complete. Then it underlines the address field value (or performs some other display rendering). From that point, the data item may be treated atomically, or as a single data item.
  • the contact record name is used to retrieve information from a corresponding contact record.
  • the contact record name, or data contained with it inherently includes pointers that enable the rendering engine 1020 to locate the record in a contact database.
  • the pointer is obtained from another source, using the contact record identifier. For example, the pointer may be obtained from an index 146 (FIG. 1).
  • Step 1070 provides that the contact information that is retrieved is filleted for the particular messaging application in use.
  • the filter applied to the record information is the same for all messaging applications.
  • a more concerted effort is made to enable the filter rules 1025 to extract all field values other than those that are legitimate recipient addresses for the particular messaging application 1010 in use.
  • Step 1080 provides that filtered contact information is displayed to the user.
  • a window or other display functionality can be used to display the contact record information.
  • a flared window may be used to display the contact record information at one time.
  • an in-line view may be provided right on the address field, which intermittingly displays one recipient address, then another from the contact record. The user can then select one of the recipient addresses, and use navigation or scrolling to view on the address line.
  • address field viewing may be used to cause editing of the address field value of a given message.
  • a step 1090 may be provided to enable edit and select from displayed contact information.
  • the user may specify a contact name, which automatically causes insertion of a first email address for that contact (e.g. the contact's work email). The user can then select to view contact information for that person, and use the information to select another email address for that contact (e.g. the person's home email address).
  • a contact name which automatically causes insertion of a first email address for that contact (e.g. the contact's work email). The user can then select to view contact information for that person, and use the information to select another email address for that contact (e.g. the person's home email address).
  • ADDRESS EDITING [141]
  • One or more embodiments described herein provide for a user to have the ability to perform edit operations on an address that is established in the address field of a message.
  • the edits may be performed in-line, meaning that the address field value can be altered in the address line of a message, even after the address that is subjected to editing was established (and thus treated atomically by the messaging application).
  • FIG. 1 IA illustrates components for enabling the editing and altering of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention.
  • a system includes a messaging application 1 110, an address editor 1120, and a contact database 1 130.
  • the address editor 1120 may correspond to one the resources in a library that is shared amongst different messaging applications.
  • a system such as described with FIG. 1 IA may be implemented through the system 100, as described with FIG. 1, with the address editor 1120 having correspondence to the address editor 164.
  • the messaging application 1110 may display an established address field value, which means an address field value is displayed and its recipient address is recognized atomically by the messaging application. From this state, a user-input may be detected to edit the address field value.
  • the user- input may be entered through use of navigational and selection input, such as through use of a multi-directional member or mechanism having a selection button.
  • the input is made through the user viewing contact record information from the rendering engine 1020 (see FIG. 10A). In another embodiment, the input is made in-line, with no separate viewing of the contact record information. In either case, the address editor 1120 receives an edit input 1116.
  • the address editor 1120 can direct or cause removal of the atomic status of the address field value that is being held by the messaging application.
  • the address field value can then be placed in edit mode, so that the user can alter or edit it.
  • the operations performed include (i) transparent deletion or disassociation of the address field value by the messaging application 1110 from the message, (ii) simultaneous holding in editable form of the address field value by the address editor (or by the messaging application) for purpose of receiving edits and alterations, and (iii) insertion of the recioient address of the edited address field value as a new address field value for the messaging application.
  • the user can delete or change existing characters (both letters and numbers), as well as adding new characters to the recipient address of the address field value.
  • contact record information 1124 can be retrieved by or for the address editor.
  • the contact name may include inherent pointers that enable retrieval of the record information 1124, although other components and resources may be used in the alternative (e.g. an index).
  • the address editor 1120 retrieves only an instance of the contact record that corresponds to the contact name. When edit mode is selected, the address editor 1120 holds the record information 1124 for substitution into the address field of the message being addressed.
  • the user can either (i) edit the existing address, as described in the preceding paragraph, (ii) substitute a new recipient address from the contact record of the same contact name provided for in the address field, or (iii) edit an alternative address field from the contact record information 1124, and substitute the recipient message identifier of that edit operation into the address field.
  • one embodiment provides that the address editor 1120 operates with an instance of the contact record from which the information 1124 was retrieved. As such, alteration to that contact information is not stored in the contact database.
  • an embodiment provides that the contact name is dropped from the address field value. The result is that the new recipient address is displayed.
  • FIG. 1 IB illustrates a method for enabling the editing and altering of contact record information from an addressed field of a messaging application, under one or more embodiments of the invention. A method such as described with FIG. 1 IB may be used in connection with, for example, a system such as described by the system of FIG. 1 IA. Accordingly, reference to elements of FIG.
  • step 1150 input is received from which a recipient address may be identified. A determination is then made in step 1152 as to whether the recipient address is a contact name. If the recipient address is a contact name, step 1155 provides that the contact name is displayed as the address field value, in association with the recipient address. Else, step 1158 provides that the contact record is displayed.
  • step 1160 the recipient address is established, meaning the messaging application 1110 will treat it as an atomic data item.
  • Step 1164 provides that edit mode selection is detected for the address field value.
  • step 1168 provides that the atomic status of the address field value is removed. In one embodiment, this may correspond to, for example, the address field value being transparently disassociated from a message that is being addressed, and then represented by functionality corresponding to the address editor 1120.
  • step 1170 provides that editing of the recipient address is enabled.
  • editing of the entire address field value including the contact name (when applicable) is enabled. Different editing processes may be performed, depending on an implementation of an embodiment described.
  • Sub-step 1172 provides one editing operation that may be enabled, in which an in-line edit can be performed. With an in-line edit, the recipient address is edited in the line of the address field. This may involve adding characters, deleting characters, and otherwise modifying the address field value.
  • step 1174 provides that an alternative recipient address from the contact record of the same contact name is displayed.
  • step 1178 provides that the user can select an alternative recipient address from the contact record of the contact name in the address field value under edit
  • step 1180 provides that the user is enabled to select, then edit an alternative recipient addresses from the contact record of the contact name in the address field value under edit.
  • the edit may be in the form of addition and/or deletion of characters that comprise the recipient address.
  • step 1184 a determination is made in step 1184 as to whether the newlv specified edited address is in the contact database. If the determination is negative, step 1194 provides that the edited recipient address is displayed and established atomically for the messaging application. Otherwise, if the determination is positive, then step 1190 provides that the contact name containing the newly specified recipient address is displayed as the address field value, and the newly specified recipient address is established atomically by the messaging application.
  • FIG. 12A-12E are illustrations of a user-interface or address window presented with a given messaging application, describing a sequence of events by which the user can select and edit and address field value, under one or more embodiments of the invention.
  • FIG. 12A an address field window 1210 of a messaging application is shown.
  • the address field window 1210 may include multiple address lines 1212 in the address field 1214.
  • FIG. 12C illustrate alternative results of a view or edit selection input made on one of the address field values 1215.
  • the view or edit selection input may correspond to the user placing one of the address field values 1215 in focus.
  • the result of the view or edit selection is that the recipient address 1222 of the selected address field value 1215 is displayed.
  • recipient address is displayed when the selected address field value is placed in focus.
  • FIG. 12B illustrates the display of the recipient address used from that contact record, but other embodiments and implementations may utilize a window or other mechanism to display more information from the same contact record.
  • alternative recipient addresses from that same contact record may be displayed on the address line of the selected address field value.
  • FIG. 12D shows that the selected address field view 1215 is made to display the underline recinient address 1222. This may be done with various types of user-interaction, such as through additional selection from view input, or simply through placing the selected address field value in a focused or partially selected state.
  • FIG. 12E a newly specified recipient address 1232 is shown, in place of the previous recipient address 1222 under edit.
  • the newly specified recipient address 1232 is formed by a simple substitution of one character in the recipient address 1222.
  • FIG. 12E shows the case where the newly specified recipient address 1232 is not associated with a contact record in the contact database.
  • a reverse lookup can be performed on the newly specified address, and if the lookup results in identification of a contact record, then the address line would display the contact name of that identified record.
  • FIG. 13 illustrates a method where editing operations of an address field can be incorporated into the operational state of a device, under an embodiment of the invention.
  • small computing devices carry keyboards and keypads that, due to the limited real-estate, require use of key states.
  • some mobile computing devices require a number mode selection to interpret key strikes from select keys on the keyboard as numbers.
  • a method such as illustrated by FIG. 13 facilitates the switching between editing address fields and enabling keypad operations by ensuring the key state of the device is returned to what it was before address editing was initiated.
  • step 1310 the key state of a keypad or keyboard on the computing device is recorded.
  • edit mode is enabled and selected by the user in step 1320.
  • the key state for use with the edit mode of the address field is selected. In one embodiment, this made be done automatically, or programmatically. For example, in the case where the messaging application is an SMS message, a default key state may be used in which case key strikes that have alternating number/letter values are presumed to be numbers. The receipt of a non-numeric input (e.g. key strike that has no number value) may switch out of the state, or the user may select out of the state. In another implementation, however, the key state for use with the edit mode of the address field is manually selected.
  • step 1340 the edit mode of the address field is detected as ending. This may correspond to, for example, establishment of the address field value after its edit mode is triggered (meaning the likelihood that the user has done something to specify the alteration).
  • step 1350 the key state of the keypad or keyboard is returned to the key state recorded in step 1310, upon completion of the edit mode. This step may be performed automatically. Thus, for example, if the user edited a phone number in the address field, the key state may return to recognizing those same keys as letters.
  • step 1350 the key state of the keypad or keyboard is returned to the key state recorded in step 1310, upon completion of the edit mode. This step may be performed automatically. Thus, for example, if the user edited a phone number in the address field, the key state may return to recognizing those same keys as letters.
  • FIG. 14 illustrates a hardware diagram of a mobile computing device configured according to an embodiment of the invention.
  • a mobile computing device 1400 such as shown by FIG. 14 may correspond to a device that is multi-functional, having as at least one primary function, cellular telephonic capabilities. Accordingly, the computing device 1400 includes a central processor 1420, a power module 1440, and a radio subsystem 1450.
  • the central processor 1420 communicates with: audio system 1410, camera 1412, Flash memory 1414, RAM memory 1416 (where for example, the index 146 may be maintained), and short range radio module 1418 (e.g. Bluetooth and/or Wireless Fidelity component).
  • the power module 1440 powers the central processor 1420 and the radio subsystem 1450.
  • Other components that communicate with the processor 420 and which are powered by power module 440 include a display 1430 (which may be contact-sensitive) and one or more input/output mechanisms (e.g. buttons, keyboards etc.).
  • the power module 1440 may correspond to a battery pack (e.g. rechargeable) or a powerline connection or component. Numerous other components and variations are possible to the hardware architecture of the computing device 1400, thus an embodiment such as shown by FIG. 14 is just illustrative of one implementation for an embodiment of the invention.
  • the radio subsystem 1450 may include a radio processor 1460, a radio memory 1462, and a receiver/transmitter 1464. While other components may be provided with the radio subsystem 1450, the basic components shown provide the ability for the mobile computing device to perform radio-frequency communications, including telephonic communications. In an embodiment, many, if not all, of the components under the control of the central processor 1420 are not required by the radio subsystem 1450 when a call is connected or ongoing.
  • the radio processor 1460 may communicate with central processor 1420 using a serial line 1478. In one embodiment, central processor 1420 executes logic (by way of programming, code, instructions) corresponding to the shared library 140 of FIG. 1 , and components described with the library 140.
  • the memory components 1414, 1416 may be used to store programs and instructions for carrying out any of the embodiments described herein.
  • the central processor 1420 may access and execute these instructions to perform or implement one or more embodiments described herein.
  • the memory components 1414, 1416 may also store or hold contact records and/or the contact database referred to by one or more embodiments described herein.
  • the display 1430 may display to the user the various interfaces from which embodiments described herein are provided (e.g. message address editing).
  • the radio subsystem 1450 may be used to transmit and receive messages through the various transports and applications described herein. [168] OTHER EMBODIMENTS
  • one or more embodiments contemplate use of a small-form factor computing device (e.g. mobile device) on which display area is limited.
  • a determination may be made as to where the list or view is to be presented, so that more of the list or view may be displayed without requiring the user to scroll up or down.
  • the screen area below and above the point from which a window, list or other view is to be generated is calculated. The portion of the display area having the most available space is used to present the list, window or other view.
  • Such an embodiment may be applied, to for example, presentation of an MRU list as described above.
  • visual or other feedback may be provided to the user to inform the user about success or failure of operations that user performs.
  • color coding may be used to inform the user as to whether the recipient address/address field value is established (and this atomic), or whether there is a problem with the entry (e.g. text was used in a field requiring only phone number, or phone number was too short to be legitimate).
  • An error may be displayed in an alternative color, indicating non-established and erroneous status.
  • a blue address field may signify an established address field value, while red denotes non-established, and erroneous address field value.
  • While embodiments described herein are provided in the context of computers, and more particularly mobile computing devices, one or more other embodiments may be implemented on web-based messaging systems.
  • Web-based messaging systems may be executed through a browser, or other application that can render images and data provided on a website.
  • the messaging applications may be substituted for a browser, or a multi-purpose application that has browsing capabilities.
  • a messaging application may be part of a larger suite of web-based products that include a contact database and messaging applications that can extend across protocols (e.g. email to SMS). Such applications may be accessed by different kinds of mobile computing devices.
  • Features and functionality such as described with any of the embodiments described herein may be integrated or incorporated with such web-based messaging applications or suites, particularly when the computer accessing such web based products is a mobile computing device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Une entrée est reçue pour un champ d'adresse d'un message à transmettre à partir d'une application de messagerie. Un enregistrement de contact est associé à partir de l'entrée avec le message. Une adresse de destinataire est choisie dans l'enregistrement de contact identifié à utiliser comme valeur de champ d'adresse. Une entrée est détectée par l'utilisateur, et par la suite, l'utilisateur peut éditer la valeur de champ d'adresse. Dans un mode de réalisation, l'utilisateur peut éditer la valeur de champ d'adresse en choisissant une nouvelle adresse de destinataire dans l'enregistrement de contact identifié, ou en créant une autre adresse de destinataire ne faisant pas partie de l'enregistrement de contact.
PCT/US2007/068906 2006-05-14 2007-05-14 Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie WO2007134302A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07783746A EP2024872A4 (fr) 2006-05-14 2007-05-14 Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/434,504 US20060288298A1 (en) 1999-08-12 2006-05-14 System, method and technique for enabling users to interact with address fields of messaging applications
US11/434,502 2006-05-14
US11/434,504 2006-05-14
US11/434,502 US20060288297A1 (en) 1999-08-12 2006-05-14 System, method and technique for enabling users to interact and edit address fields of messaging applications

Publications (2)

Publication Number Publication Date
WO2007134302A2 true WO2007134302A2 (fr) 2007-11-22
WO2007134302A3 WO2007134302A3 (fr) 2008-11-27

Family

ID=38694772

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/068906 WO2007134302A2 (fr) 2006-05-14 2007-05-14 Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie

Country Status (2)

Country Link
EP (1) EP2024872A4 (fr)
WO (1) WO2007134302A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2632095A3 (fr) * 2012-02-24 2013-10-30 BlackBerry Limited Extraction et présentation de données de contact au niveau d'un dispositif électronique

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6279018B1 (en) * 1998-12-21 2001-08-21 Kudrollis Software Inventions Pvt. Ltd. Abbreviating and compacting text to cope with display space constraint in computer software
CN1791129B (zh) * 1999-12-08 2011-04-13 株式会社Ntt都科摩 无线通信终端及其自动配置方法和模式切换方法
CN101291361A (zh) * 2001-12-26 2008-10-22 运营研究有限公司 统一查看在移动设备上的通信事件的用户界面和方法
US7747690B2 (en) * 2003-12-29 2010-06-29 International Business Machines Corporation Method for extracting and managing message addresses
US7451397B2 (en) * 2004-12-15 2008-11-11 Microsoft Corporation System and method for automatically completing spreadsheet formulas

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP2024872A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2632095A3 (fr) * 2012-02-24 2013-10-30 BlackBerry Limited Extraction et présentation de données de contact au niveau d'un dispositif électronique

Also Published As

Publication number Publication date
EP2024872A4 (fr) 2011-07-27
WO2007134302A3 (fr) 2008-11-27
EP2024872A2 (fr) 2009-02-18

Similar Documents

Publication Publication Date Title
US20150195241A1 (en) System, method and technique for enabling users to interact with address fileds of messaging applications
US20060288297A1 (en) System, method and technique for enabling users to interact and edit address fields of messaging applications
US11023678B2 (en) User interface for a handheld device
US10986048B2 (en) Method and system for using subjects in instant messaging sessions on a mobile device
US8280437B2 (en) Contact-centric user-interface features for computing devices
US8001120B2 (en) Recent contacts and items
US7502606B2 (en) Computer-readable medium, method, and device for associating information with a contact
US20040119732A1 (en) Contact picker
WO2003058519A9 (fr) Système amélioré de gestion d'e-mails
US20120322427A1 (en) Integrated dialing
US20020142758A1 (en) Message communication device
CA2692964A1 (fr) Systeme et procede d'amelioration de la saisie des adresses
EP2024872A2 (fr) Système, procédé et technique permettant aux utilisateurs d'interagir et d'éditer des champs d'adresses d'applications de messagerie

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07783746

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007783746

Country of ref document: EP