WO2001031509A2 - Systeme et procede d'acces et de stockage rapides d'informations de contact au moyen d'un dispositif de communication - Google Patents

Systeme et procede d'acces et de stockage rapides d'informations de contact au moyen d'un dispositif de communication Download PDF

Info

Publication number
WO2001031509A2
WO2001031509A2 PCT/US2000/029444 US0029444W WO0131509A2 WO 2001031509 A2 WO2001031509 A2 WO 2001031509A2 US 0029444 W US0029444 W US 0029444W WO 0131509 A2 WO0131509 A2 WO 0131509A2
Authority
WO
WIPO (PCT)
Prior art keywords
contact
entry
database
user
entries
Prior art date
Application number
PCT/US2000/029444
Other languages
English (en)
Other versions
WO2001031509A3 (fr
Inventor
Eric J. Lekven
Diego A. Kaplan
Original Assignee
Qualcomm Incorporated
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
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to AU13443/01A priority Critical patent/AU1344301A/en
Publication of WO2001031509A2 publication Critical patent/WO2001031509A2/fr
Publication of WO2001031509A3 publication Critical patent/WO2001031509A3/fr

Links

Classifications

    • 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/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/27463—Predictive input, predictive dialling by comparing the dialled sequence with the content of a telephone directory

Definitions

  • the present invention relates generally to communications systems, and more particularly, to a method and system for accessing and storing information in a communications system.
  • Electronic phone books are used to store phone numbers electronically in telephones or other communications devices.
  • electronic phone books store information that would be included in a paper telephone book issued by a local telephone company, such as a name or entity to be called and the telephone number of the person or entity.
  • Storing phone book information electronically within a telephone simplifies use of the telephone because a user can retrieve phone numbers needed to place calls directly from the telephone. Carrying the information needed to place calls within the telephone avoids having to find a paper telephone book or carry telephone numbers separately such as in a personal address and telephone book, personal organizational planner, or personal notes.
  • the phone book information is readily available to a user in the same device that is used to place a call.
  • a user makes a selection in the keypad of the telephone indicating a desire to store information in the electronic phone book.
  • the user then enters the information to be stored into the telephone. For example, if a user wants to enter a family member's telephone number, the user makes a selection on the keypad of their telephone to request an update of their electronic phone book.
  • the user responds to menu prompts to input information, such as a family member's name and the family member's telephone number.
  • the user requests to store the information in the electronic phone book of the telephone. The user retrieves the information at a later time by selecting the keypad command to retrieve information from the electronic phone book.
  • Traditional electronic phone books do not afford the flexibility of different types of storage. For example, traditional electronic phone books do not differentiate between long term or permanent storage and short term or temporary storage.
  • a user can typically search for electronic phone book information in one of two ways.
  • the user can search for a name or other alphabetic information. For example, a user may wish to retrieve the phone book entry for a person named James. The user would direct the telephone to perform a name search.
  • the user would enter a sequence of digits on a keypad that correspond to a sequence of letters in the word "James.” The telephone would respond by displaying phonebook entries that contain names matching the alphabetic equivalent of the entered digit sequence.
  • the user can search for a phone number or other numeric information. When performing a numeric search, a user would direct the telephone to perform a phone number search.
  • the user would enter a sequence of digits on a keypad. The telephone would respond by displaying phonebook entries that contain phone number sequences that match the entered digit sequence.
  • a disadvantage in this manner of searching is that a user will first have to select the type of search that needs to be performed. Also, a user may have to perform an alphabetic search as well as a numeric search before retrieving the desired information. Furthermore, the alphabetic search would require the use of multiple key entries to enter a single alphabetic character.
  • the present invention provides a novel system and method for rapidly accessing and storing contact information.
  • contact information is rapidly accessed and stored through the use of a communications network interface device.
  • the present invention accesses and stores traditional contact information such as name and destination number. Also, the present invention accesses and stores information that changes based on the use of the communications network interface device.
  • the present invention embodies a method and system for searching an alphanumeric contact database where the contact database contains a plurality of contact entries.
  • the method and system includes the steps of: (a) initializing a matched value list to include the plurality of contact entries, (b) generating a data signal on a keypad, (c) if the data signal represents a digit, appending the digit to a digit sequence, (d) determining whether the digit sequence is within a valid searching range, (e) if the digit sequence is within the valid searching range, then (el) for each contact entry in the matched value list, determining whether the digit sequence is contained within the contact entry, (e2) if the digit sequence is not contained within the contact entry, removing the contact entry from the matched value list and generating a new matched value list including only those contact entries that contain the digit sequence, (f) displaying said new matched value list, and (g) repeating steps (c)-(f) for each additional data signal generated in step (b).
  • the system and method includes sorting each entry of the new matched value list according to sorting criteria before displaying
  • the present invention also embodies a method and system for entering a contact entry into an alphanumeric contact database, containing a plurality of contact entries.
  • the method and system includes the steps of: (a) receiving a contact entry, (b) searching the contact database to determine whether the contact entry is included within the contact database, (c) if the contact entry is not included within the contact database, determining whether space is available in the contact database, to store the contact entry, (d) if space is available in the contact database, then temporarily storing the contact entry in the contact database, (e) prompting the user to determine whether the temporarily stored contact entry is to be stored permanently, and (f) permanently storing the contact entry in the contact database if the user determines that the temporarily stored contact entry is to be stored permanently in the contact database.
  • the system and method receives phone numbers from an automated data service.
  • FIG. 1 is a block diagram of a communications network interface device according to a preferred embodiment of the present invention
  • FIG. 2 A is a block diagram of software of a communications network interface device according to a preferred embodiment
  • FIG. 2B is a block diagram of an exemplary contact information manager implementation according to a preferred embodiment
  • FIG. 3 is a flowchart illustrating the operation of a communications network interface device environment according to a preferred embodiment
  • FIG. 4A is a flowchart illustrating the operation of call initiation according to a preferred embodiment
  • FIG. 4B is a flowchart illustrating the operation of rapid contact information searching according to a preferred embodiment.
  • FIG. 5 is a flowchart illustrating the operation of updating contact information according to a preferred embodiment.
  • contact information is stored and accessed automatically by a contact information manager within a communications network interface device.
  • the contact information manager can store and access information based on information automatically obtained through use of the communications network interface device.
  • One embodiment of the communications network interface device is a mobile telephone that operates in a mobile telephone system such as a cellular or satellite system.
  • the invention can be used in any telephone, whether wired or wireless, that displays contact information.
  • FIG. 1 is a block diagram of a communications network interface device 104.
  • communications network interface device 104 is a wireless telephone. Examples of wireless telephones include portable, mobile or fixed cellular and satellite phones. Examples of communications network interface device 104 also include any other device that interfaces with a communications network such as a wired telephone in a personal computer.
  • Communications network interface device 104 includes a user input device 106, such as a keypad, a processor 108, an interface 110, and a memory 112.
  • User input device 106 may be a keypad on a telephone, a keyboard on a personal computer or any other device that can accept user input.
  • Interface 110 is any connectivity that allows electrical components within communications network interface device 104 to be interconnected and transmits electrical signals.
  • Memory 112 also referred to as storage medium, is any storage medium. Examples of memory 112 include short term memory, long term memory, nonvolatile memory, removable memory such as a floppy disk, or any other memory that can be used to store computer code or information processed by computer software. Memory 112 may be dispersed among one or more hardware storage medium components. In a preferred embodiment, memory 112 can retain stored data even when wireless telephone 104 is powered down.
  • Communications network interface device 104 is used by a caller to transmit signals to and receive signals from a communications network (not shown) in order to complete a call to a recipient.
  • An exemplary communication network is a mobile telephone system using CDMA such as the network described in U.S. Patent No. 5,103,459 entitled “System and Method for Generating Signal Waveforms in the CDMA Cellular Telephone System” issued April 17, 1992 to the assignee of the present invention and incorporated herein by reference.
  • User input device 106 is connected to interface 110 for connectivity with processor 108 and memory 112. Interface 110 is connected to memory 112 and processor 108. User input device 106 is within user interface 107. User interface 107 also includes one or more software components that reside in memory 112 and are processed by processor 108.
  • communications network interface device 104 is not physically connected to equipment in a communications network. Rather, communications network interface device 104 transmits signals to and receives signals from a base station within a communications network via an antenna or satellite that is within range and has capacity to handle the communication. In alternate embodiments where a communications network does not include cellular technology or satellites, communications network interface device 104 is physically connected to an exchange within a communications network. The functionality of communications network interface device 104 can be described with respect to an exemplary call by referencing the components illustrated in FIG. 1 that would be used to carry the particular call. A user places a call using communications network interface device 104. A large number of users each using a communications network interface device 104 may place calls via a communications network simultaneously. Each individual communications network interface device 104 is a unit that accepts input from a user.
  • communication network interface device 104 is a wireless telephone or other wireless equipment that can transmit and /or receive signals via antennas or satellites and initiate and/or receive calls.
  • Wireless telephones are stand alone units without physical connections that transmit signals to or receive signals from wireless communication networks.
  • Other devices that may be used to place a call include a paging receiver, a wireless personal computer, and any other device that can transmit and /or receive signals via a wireless communications network.
  • communications network interface devices 104 are any communications devices which can interface via direct connection with the communications network and initiate and /or receive calls such as wired phones, personal computers, and facsimile machines.
  • a phone card or computer program product may be used which would include memory comprising the present invention.
  • FIG. 2 A is a block diagram of communications network interface device 104.
  • Memory 112 within communications network interface device 104, stores lines of code which are processed by processor 108.
  • the lines of code are commands from a computer programming language that are processed by processor 108 to perform functions.
  • Software components comprising lines of code from a computer programming language reside in memory 112 of communications network interface device 104. These software components are processed by processor 108 and include a user interface software 204, a call processing component 206, and a contact information manager 208.
  • User interface software 204 comprises one or more software modules that store the information for a particular call for the duration of the call.
  • a software module is a block of computer program code that performs a specified function. If user interface software 204 is implemented with multiple software modules, the software modules may be within one subroutine and /or computer program or dispersed through multiple subroutines and/or programs.
  • User interface software 204 can store fields of information. Examples of fields that would be stored by user interface software 204 are the destination number, the time of a call, and the length of a call, and any other information that may be obtained by use of communications network interface device 104 with respect to a particular call. User interface software 204 receives information, such as the destination number, from user input device 106. In addition, user interface software 204 has the capability to calculate values based on information received, such as the duration of a call. User interface software 204 also temporarily stores information in temporary memory such as in Random Access Memory (RAM).
  • RAM Random Access Memory
  • Call processing component 206 performs processing of a telephone call in order to terminate the call through a communications network to a recipient.
  • Call processing component 206 receives a destination number dialed by the user from user input device 106.
  • Call processing component 206 performs the processing necessary to route a call through the communications network to the end recipient. For example, in a cellular communications network, call processing component 206 would transmit the information needed to send a call to an antenna, then via a digital link to a mobile telephone switch in order to connect to the end recipient.
  • the destination number entered by the user on user input device 106 is the number corresponding to another communications network interface device.
  • Call processing component 206 also receives destination numbers from the communications network. These destination numbers are provided by automatic data services. An example of such an automatic data service is Caller ID.
  • Call processing component 206 performs processing that needs to be completed by communications network interface device 104 to transmit calls via communications network and complete calls to the end recipient's communication network interface device. Similar to user interface software 204, call processing component 206 may be one or more software modules within one subroutine and /or program or dispersed through multiple subroutines and /or programs.
  • Contact information manager 208 maintains contact information including destination numbers and names associated with each of the destination numbers, such as the name of a person or entity. Contact information manager 208 may also maintain other contact information such as street addresses associated with destination numbers. Additional dynamic data fields that change based on the use of communications network interface device 104 may be tracked by contact information manager 208. Exemplary dynamic fields include the frequency of outgoing calls sent to each of the destination numbers, the frequency of incoming calls received from the destination numbers, other fields as illustrated in Table 1 below, and any other field containing information that would be dynamically modified based on the use of communications network interface device 104. Examples of such dynamic fields are set out below in Table 1.
  • Maintained in contact information manager 208 by deleting an existing value and recording a new value of the average duration calculated using the duration of the current outgoing call for each call initiated. The calculation is made using a stored average and the stored frequency of calls. The stored average and frequency of calls are multiplied and the length of the current call is added to the result. The new average is calculated by dividing the summation by a new frequency of calls which is the stored frequency of calls plus 1.
  • Answer status of last indicates whether outgoing call the last call was answered by the recipient or whether the initiating user received a ring but no answer.
  • Maintained in contact information manager 208 by deleting the existing value and updating the field with the appropriate completion information for each new call initiated. This may be useful by telemarketing users in recalling only recipients who did not answer.
  • the call completion indicates percentage of calls that history successfully completed to a destination number. Maintained in contact information manager 208 by deleting an existing value and recording a new value of the average completion rate for each call initiated. The calculation is made using a stored average and the stored frequency of calls. The stored average and frequency of calls are multiplied and, if the call completed successfully, the result is incremented by one. The new completion average is calculated by dividing the summation by a new frequency of calls which is the stored frequency of calls plus 1.
  • Time of last incoming call The time the latest call to the destination number was field received by a user via communications network interface device 104. Maintained in contact information manager 208 by deleting an existing value and recording a new value of the time a call is received for each call received.
  • Length of last incoming The duration of the latest call to the destination call field number that was received by a user via communications network interface device 104. Maintained in contact information manager 208 by deleting an existing value and recording a new value of the duration of the last incoming call for each call received.
  • Average length of The average length of calls received from the incoming call field destination number by communications network interface device 104 Maintained in contact information manager 208 by deleting an existing value and recording a new value of the average duration calculated using the duration of the current incoming call for each call initiated. The calculation is made using a stored average and the stored frequency of calls. The stored average and frequency of calls are multiplied and the length of the current call is added to the result. The new average is calculated by dividing the summation by a new frequency of calls which is the stored frequency of calls plus 1. Longest length of The length of the longest call from the destination incoming call field number received by communications network interface device 104. Maintained in contact information manager 208 by deleting an existing value and recording a new value of the duration only if the duration of the last call is longer than the stored value.
  • Answer status of last indicates whether incoming call the last call was answered by the recipient or whether the initiating user received a ring but no answer.
  • Maintained in contact information manager 208 by deleting the existing value and updating the field with the appropriate completion information for each new call initiated. This may be useful by telemarketing users in recalling only recipients who did not answer.
  • Incoming call completion indicates percentage of calls that history successfully completed to a destination number. Maintained in contact information manager 208 by deleting an existing value and recording a new value of the average completion rate for each call initiated. The calculation is made using a stored average and the stored frequency of calls. The stored average and frequency of calls are multiplied and, if the call completed successfully, the result is incremented by one. The new completion average is calculated by dividing the summation by a new frequency of calls which is the stored frequency of calls plus 1.
  • contact information manager 208 maintains static data fields that do not change based on the use of communications network interface device 104.
  • Static data fields include one or more contact identifiers, such as the destination number of a contact and possibly a contact name, such as the name of the person or entity associated with the destination number.
  • Additional static data fields may include a field indicating whether a particular destination number transmits voice or data, a price per minute field containing the price per minute to send a call to a particular destination number, a quality of the link field stored for destination numbers corresponding to a data link, the street address associated with a destination number, and any other field that does not change based on use of communications network interface device 104.
  • contact information manager 208 provides a user with multiple options for the searching and retrieval of contact information.
  • a user may prompt contact information manager 208 to search for and retrieve contact information that matches various user selected searching criteria.
  • An example of such searching criteria is the set of contacts having certain information fields that contain distinct symbol sequences.
  • a user may input a retrieval selection for the format in which the user wishes to receive the contact information.
  • Retrieval selections are one or more specifications of presentation of contact information provided by a user in a hierarchal order.
  • a user may specify to have contact information sorted or specify any other operation that can be performed on the retrieved contact information to provide a specified presentation format. In addition to specifying an operation to be performed, such as sorting or formatting, the user can also specify which fields should be analyzed to prepare the data for presentation.
  • a user may want to receive contact information found according to certain searching criteria and have this contact information sorted according to the number of outgoing calls for a particular destination number, from most to least.
  • the user enters the appropriate searching criteria and retrieval selections into user input device 106 to retrieve contact information and sort the frequency of call fields in this contact information from the highest frequency of outgoing calls to the lowest frequency of outgoing calls.
  • a user may also make a secondary selection of sorting in alphabetical order based on the contact name field. In the example, a user is presented with the contact information sorted starting with the destination number with the highest frequency of outgoing calls. If two destination numbers have the same call frequency, the destination numbers are sorted alphabetically based on the contact name. A user could select to browse the contact information in decreasing frequency of outgoing calls.
  • Various alternative retrieval selections are possible. Flexibility and variety in searching and retrieval selections provides users with ease of obtaining contact information stored in memory 112 and maintained by contact information manager 208.
  • FIG. 2B is a diagram illustrating an exemplary contact information manager 208 implementation with multiple databases, including a voice contact information database 212A to store voice contact information and a data contact information database 212B to store data contact information.
  • contact information manager 208 may include only one type of database, depending on the type of communications network interface device 104 in use. Both voice contact information database 212A and data contact information database 212B store names, 218A and 218B, associated with a corresponding destination numbers, 220A and 220B, respectively.
  • Voice contact information database 212A comprises dynamic fields 222A and static fields 224A.
  • data contact information database 212B comprises dynamic fields 222B and static fields 224B.
  • Dynamic fields 222 A stored in voice contact information database 212A may include any of the data fields shown in Table 1.
  • Voice contact information database 212A may also store static fields 224A such as contact names, street addresses and /or the price per minute to call each of the destination numbers. Similar to the dynamic fields stored by voice contact information database 212A, dynamic fields 222B stored by data contact information database 212B may include any of the fields shown in Table 1.
  • Data contact information database 212B may also store static fields 224B such as link quality and link data rate.
  • Voice contact information database 212A and data contact information database 212B further comprise destination number fields 220A and 220B, respectively. These data fields contain network addresses. In a preferred embodiment, a network address is a phone number.
  • FIG. 3 is a flowchart 302 illustrating the operation of communications network interface device 104.
  • the operation of communications network interface device 104 in a specific active communication, such as placing a call to a recipient communications network interface device (not shown), will be described with respect to the components shown in FIGS. 1 and 2.
  • Communications network interface device 104 is initially in a standby state. In this state, there are no user communications or calls in progress, and a user has not started entering any destination numbers or other call set up information into user input device 106 of communications network interface device 104.
  • step 306 a user initiates a call by inputting a destination number or other call set up information into user input device 106 of communications network interface device 104.
  • communications network interface device 104 is no longer in a standby state.
  • a user may select to initiate a call by retrieving a destination number or other call set up information stored by contact information manager 208.
  • a user retrieves destination numbers or call set up information stored by contact information manager 208 through interaction with user input device 106. The operation of retrieving a number stored by contact information manager 208 will be described in further detail with reference to FIGS. 4A and 4B.
  • user interface software 204 allows a user to manually enter a destination number via user input device 106.
  • the destination number or other call set up information is transmitted to interface 110 to be processed by call processing software component 206 residing in memory 112.
  • Call processing software component 206 performs the processing needed by communications network interface device 104 to connect the call via the communications network to a recipient using a second communications network interface device.
  • user interface software 204 accepts or calculates any additional information needed to be tracked. This additional information may be accepted from user input device 106, contact information manager 208, call processing software component 206, or memory 112. An example of such information is the start time of the call.
  • communications network interface device 104 signals to a communications network.
  • Processing of call processing component 206 causes a signal to be sent from communications network interface device 104 to the communications network.
  • the signal that is sent from communications network interface device 104 contains information needed to establish a call to a recipient via a communications network, such as the destination number of the recipient's communications network interface device. Signaling between components within the communications network follows standards established by the industry such as the American National Standards Institute (ANSI) Signaling System Number 7 (SS7) standard or other standards known to those skilled in the art.
  • SS7 Signaling System Number 7
  • contact information is updated in memory 112 of communications network interface device 104. Call processing for initiation of the call is complete when a user initiating the call using communications network interface device 104 is connected to a recipient using another communications network interface device (not shown). When call processing is complete, information is transferred from user interface software 204 to contact information manager 208.
  • the call proceeds until one of the parties, either the user initiating the call or a recipient, terminates the call in a known manner, such as by entering "END" using a keypad of a mobile telephone, logging off on a personal computer, or placing the receiver onto the base of a telephone (going "on-hook”).
  • processing is performed by the components of the communications network and call processing component 206 of communications network interface device 104 to notify all components that the call is completed and to provide information needed for billing the call.
  • user interface software 204 performs any remaining needed calculations and /or processing, such as calculating the duration of the call, and sending contact information to contact information manager 208. After contact information manager 208 has been updated, user interface software 204 discontinues tracking the information and prepares to receive information for the next call. Alternatively, the information may be saved by user interface software 204 and transferred to contact information manager 208 when a user powers down communications network interface device 104. The operation of updating contact information manager 208 will be described in further detail with respect to FIG. 5.
  • the contact entries matching such a retrieval selection are Joe, Ted, and Jim, then the contact information is sorted and presented to the user in the following order: Joe's destination number (20 outgoing calls), Ted's destination number (15 outgoing calls), followed by Jim's destination number (10 outgoing calls).
  • a user selects a particular retrieved destination phone number and then touches a "SEND" key on user input device 106 of the communications network interface device 104 to initiate the call in a known manner.
  • a user initiates the call using the appropriate mechanism for call initiation for that particular communications network interface device 104.
  • Multi-tap text entry techniques enable users to enter particular letters by pressing individual digit keys a certain number of times in quick succession. For example, as shown in Table 2, the letters “G", "H", and “I” correspond to digit key 4. With multi-tap text entry, the number of times a particular key needs to be pressed depends on the order that the letters are printed on the key. Using digit key 4 as an example, a user would enter "H” using a multi-tap technique by pressing digit key 4 twice in quick succession. To enter 'G' using a multi-tap technique, a user would press digit key 4 only once.
  • FIG. 4B is a flowchart illustrating a rapid contact search according to a preferred embodiment.
  • This search begins with step 420 where contact information manager 208 initializes a matched value list.
  • This list contains an initial set of contact entries.
  • this initial set comprises all contact information managed by contact information manager 208.
  • this initial set includes only portions of the contact information that are contained in selected databases.
  • the matched value list will form the basis of all searching.
  • Contact information manager 208 manages and maintains the matched value list. In an alternate embodiment, after contact information manager 208 initializes the matched value list, management and maintenance of this list is transferred to user interface software 204.
  • a user enters a data symbol through user input device 106.
  • This symbol is a number on a telephone keypad. Alternatively, this symbol could be a key from a computer keyboard, or any data symbol generated through the interaction of a user or an automated device with communications network interface device 104.
  • User interface software 204 processes this step.
  • step 424 the data symbol entered in step 422 is appended by user interface software 204 to a digit sequence. If this data symbol is the first data symbol received since communications network interface device 104 was in a standby state, user interface software 204 creates a new digit sequence that begins with this data symbol.
  • step 440 user interface software determines whether the digit sequence has been edited. In a preferred embodiment a user may edit the digit sequence by deleting or changing certain digits in the digit sequence. If the digit sequence has been edited, step 442 is performed. In step 442, the matched value list is reinitialized.
  • digit sequences comprising only a few digits are outside the valid searching range because they would result in too many matches.
  • certain digit sequences may be reserved for special types of user interaction with communications network interface device 104.
  • An example of a special type of user interaction with communications network interface device 104 is speed dialing where one or more digits represent a memory location, the contents of which are to be directly dialed.
  • a digit sequence is contained in a numeric field if the numeric field matches the digit sequence in order starting at any of one or more identified initial points in the numeric field. These initial points are determined by digit offsets within the field or, in the case of a numeric field representing a phone number, by knowledge of the dialing plan. For example, if a match is attempted between an entered digit sequence and a numeric field representing a telephone number, offsets would exist that correspond to the beginning of the numeric field's area code digits, and the numeric field's local number digits. If an exact match is found starting from any of the appropriate offset positions, then the numeric field is said to contain the digit key sequence.
  • a match between an entered digit sequence and a numeric field may exist in any contiguous portion of the field, not just at identified initial points.
  • a digit sequence is contained in an alphabetic sequence if the digit sequence matches a portion of the sequence of numerically equivalent values that results when each alphabetic character of the alphabetic sequence is mapped to an equivalent digit.
  • Table 2 provides an exemplary mapping of alphabetic characters to equivalent digits.
  • Embodiments could ignore spaces and punctuation characters contained in alphabetic fields.
  • Embodiments could also require matching patterns to begin at certain points in the alphabetic field.
  • Other constraints could be placed on the matching technique.
  • One such constraint compares digit sequences containing a single digit with the numerical equivalent of certain significant characters in an alphabetic field. An example of such a significant character is the first letter in a name.
  • step 422 a user presses digit key "3" on a wireless telephone keypad because the letter "D" is represented by this digit key. This digit creates a new digit sequence in accordance with step 424. If this digit is within a valid searching range as determined by step 426, step 428 examines fields to determine whether the entered sequence is contained in any fields.
  • step 430 contact entries are removed from the matched value list if the digit sequence is not contained in any of the entries' fields.
  • the matched value list is displayed. This display is in accordance with any sorting or retrieval settings selected by a user through user input device 106. All or only a portion of the contact entry fields may be displayed according to the retrieval settings selected by a user.
  • the matched value list can consist of many entries. Therefore, an embodiment enables a user to scroll through the entries of the matched value list through operation of user input device 106.
  • step 434 a user can select to either repeat the process of steps 422 through 432 or select to initiate a call using the contact information according to step 406.
  • the repetitive execution of steps 422 through 432 produces a successively smaller matched value list.
  • Table 3 illustrates a sample voice contact information database 212A containing three contact entries. As shown in the second and third columns of this table, each of these entries comprises a name field, and a destination number field. The fourth column of Table 3 illustrates the numerical equivalent of each entry's name field. These numerical equivalents are determined using the letter to digit mappings provided in Table 2.
  • the numerical equivalents in Table 3 are based on the alphabetic text portions of each name field. For instance, the name field for entry number 1 in Table 3 is "John @ work”. The numerical equivalent of this field is determined by eliminating the non-alphabetic character "@”, converting each alphabetic word into its numerical equivalent using the mapping provided in Table 2, and concatenating these numerical equivalents to form the name field's numerical equivalent. In the case of the name field "John @ work”, the numerical equivalents of "John” and "work” are "5646" and "9675", respectively. Concatenated together, these numerical equivalents form the name field's numerical equivalent "56469675", as shown in Table 3.
  • alphabetic fields may also comprise digits. In these fields, the digits are neither eliminated nor converted.
  • Tables 4 and 5 provide examples of rapid contact searches according to a preferred embodiment.
  • Table 4 provides an example of a search conducted using a numeric field
  • Table 5 provides an example of a search conducted using a text field.
  • Each row of these tables illustrates an iteration of a database search. The top row represents the beginning of the search and the bottom row represents the end of the search.
  • Tables 4 and 5 each have three columns.
  • the entries in these columns illustrate an entered digit sequence, a matched value list, and an exemplary display.
  • the matched value list is not shown in the second column until a digit sequence within a valid searching range is entered.
  • the exemplary display entries shows the entered digit sequence, the first entry of the matched value list, and the number of matches.
  • the display entries also show functional activity of portable electronic device 104, such as when a destination number is being called.
  • searching does not begin until an entered digit sequence is within a valid searching range.
  • entered digit sequences are within a valid searching range when they comprise three or more digits that are not set aside for a special purpose.
  • "911" and "411" are examples of digit sequences that are set aside for special purposes.
  • Table 4 illustrates a database search for contact entry 1, as shown in Table 3. A user conducts this search by keying in digits associated with the numerical destination number field.
  • the first iteration of this search is illustrated in top row of Table 4.
  • a user enters the digit "5" through user input device 106.
  • the digit sequence is "5" and is not within a valid searching range.
  • the second iteration is shown.
  • a user enters another digit "5" through user input device 106.
  • the entered digit sequence is "55" and is also not within a valid searching range.
  • the entered digit sequence has been appended with another "5" through user input device 106.
  • the digit sequence is "555" and is within a valid searching range. Consequently, a matched value list is displayed.
  • the exemplary display in the third column of Table 4 displays the matching field of first ranked entry in the matched value list.
  • the portion of the displayed entry in bold typeface is the entered digit sequence.
  • the entry containing the destination number field 555-1212 is the first ranked entry in the matched value list.
  • contact entries can be sorted according to various schemes.
  • the display also shows the other field of this contact entry, "John @ work”.
  • the number of matches is displayed. The number of matches also equals the size of the matched value list.
  • entries 1 and 3 there are two entries having fields containing the digit sequence "555". These are entries 1 and 3. After the user has entered the digit sequence "555", the user has found the desired entry. As indicated in the bottom row of Table 4, the user presses send and the display indicates that the destination number for "John @ work" is being called. If the user desired another entry represented in the matched value list, the user could search for this entry by scrolling through the list and selecting the desired entry. Alternatively, the user could enter more digits to narrow the matched value list until the desired entry is found.
  • Table 5 also illustrates a database search for contact entry 1, as shown in Table 3.
  • the search illustrated in this table was conducted by entering digits associated with the alphabetic name field.
  • the search goes through more than one iteration.
  • the matched value list contains entries that were matched according to the numerical equivalent of their name fields.
  • this search results in the user finding contact entry 1, as shown in Table 3. The send key is pressed and a call is placed to the destination number for this contact entry.
  • FIG. 5 is a flowchart illustrating the operation of updating contact information. This operation performs the function of step 310 in FIG. 3, where communications network interface device 104 is used to place a call. In addition, this operation can be an independent process, where a user desires to update contact information without placing a call.
  • a user may desire to change a contact entry from short term to long term at a time other than when a call is placed.
  • Contact entries fall under two classifications or markings: long term and short term.
  • Long term, or permanent, contact entries contain data that pertains to contacts intentionally stored by a user.
  • Short term, or temporary, contact entries consist of data automatically entered into a contact database. Long term contact entries cannot be deleted from a contact database without user permission. Similarly, the static fields of long term contact entries cannot be modified without user permission. In contrast, short term contact entries can be modified and deleted without user permission. For example, the modification and deletion of short term contact entries could be initiated by automatic processes. Short term entries could also be automatically deleted to create space in memory 112 for the creation of long term entries or newer short term entries.
  • step 504 user interface software 204 sends a query to contact information manager 208 to see if certain contact information is stored.
  • user interface software 204 sends a query to contact information manager 208 to determine if the contact information (i.e., the destination number) is already stored in memory 112.
  • a query is sent to contact information manager 208 from user interface software 204 or other component resident in communications network interface device 104 at a time not associated with the placing of a call to determine if contact information is already stored in memory 112. This query could originate from user input device 106 or from an automatic data service.
  • Step 506 is performed next.
  • contact information manager 208 determines if the contact information is stored in memory 112. If the contact information is stored, then the process proceeds to step 508 to update the existing fields in the existing contact entry.
  • contact information manager 208 updates the fields in memory 112 for the existing contact entry. These updates may be in response to specific commands entered by a user through user interface 106. Alternatively, these updates may be automatic when the content entry relates to a call in progress.
  • Updates may be obtained from user interface software 204 multiple times during a call.
  • contact information manager 208 may update a contact entry's dynamic fields such as a counter field which stores the number of times a call is placed to a particular destination number. This field could be updated immediately upon completion of call processing to set up a call.
  • duration of the call may be sent to contact information manager 208 to update a longest length of call field.
  • Contact information manager 208 may perform calculations such as comparing the length of a call with the length of the call already stored and storing the length of the new call if it is longer than the length of the call stored. Alternatively, contact information manager 208 may compute an average call length using a statistical algorithm.
  • step 510 contact information manager 208 creates a new entry for the contact information if there is available space in memory 112. Contact information manager 208 may delete existing short term entries to create sufficient space in memory 112. Contact information manager 208 marks this entry as short term. For example, if a user has entered a particular destination number for the first time, then an entry does not exist in contact information manager 208 for that particular destination phone number. Therefore, contact information manager 208 creates a new entry in the database for the new destination number. In step 512, contact information manager 208 requests information from the user regarding the new entry. For example, the destination number must be included in the new entry.
  • a user may input the destination or the destination number may be automatically transferred from user interface software 204.
  • a user may want to store the name of the person or entity associated with the destination number if it is not available automatically.
  • a user enters this information via user input device 106.
  • alphabetic characters are entered by a user through a multi-tap text entry technique when user interface device 106 is a keypad on a portable telephone.
  • step 512 is not performed. Upon completion of updating the database with information needed, the process proceeds from step 512 to step 508.
  • step 514 contact information manager 208 determines if the stored contact entry is marked long term or short term. If the contact entry is marked long term, the operation of updating contact information 310 is complete. Otherwise, step 516 is performed.
  • step 516 a user selects whether to mark this short term contact entry as long term.
  • communications network interface device 104 through user input device 106, prompts a user for this selection.
  • a user makes the desired selection through user input device 106.

Abstract

Dans cette invention, un dispositif à interface réseau de communications permet de mémoriser et d'accéder rapidement aux informations de contact. Un utilisateur recherche une base de données alphanumérique de contact qui contient un groupe de plusieurs entrées de contact. Les entrées de contact extraites sont mémorisées et affichées. Les entrées de contact sont reçues et introduites dans une base de données de contact alphanumérique en vue d'un stockage temporaire ou permanent. Ces entrées de contact peuvent être reçues par entrée manuelle ou par un service de données automatisé.
PCT/US2000/029444 1999-10-26 2000-10-25 Systeme et procede d'acces et de stockage rapides d'informations de contact au moyen d'un dispositif de communication WO2001031509A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU13443/01A AU1344301A (en) 1999-10-26 2000-10-25 System and method for rapidly accessing and storing contact information based onuse of a communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US42054599A 1999-10-26 1999-10-26
US09/420,545 1999-10-26

Publications (2)

Publication Number Publication Date
WO2001031509A2 true WO2001031509A2 (fr) 2001-05-03
WO2001031509A3 WO2001031509A3 (fr) 2001-09-13

Family

ID=23666911

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/029444 WO2001031509A2 (fr) 1999-10-26 2000-10-25 Systeme et procede d'acces et de stockage rapides d'informations de contact au moyen d'un dispositif de communication

Country Status (2)

Country Link
AU (1) AU1344301A (fr)
WO (1) WO2001031509A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1259051A1 (fr) * 2001-05-11 2002-11-20 Tenovis GmbH & Co. KG Méthode et appareil de complétement automatique de numéros de téléphone utilisant une base de données
EP1603312A1 (fr) * 2004-06-01 2005-12-07 Samsung Electronics Co., Ltd. Procédé d'exécution de fonctions au moyen du numéro de téléphone recherché dans un terminal mobile
WO2016034062A1 (fr) * 2014-09-03 2016-03-10 北京奇虎科技有限公司 Procédé et dispositif de consultation d'informations

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708804A (en) * 1994-07-25 1998-01-13 International Business Machines Corp. Apparatus and method therefor of intelligently searching for information in a personal communications device
US5797098A (en) * 1995-07-19 1998-08-18 Pacific Communication Sciences, Inc. User interface for cellular telephone
WO1999015952A2 (fr) * 1997-09-25 1999-04-01 Tegic Communications, Inc. Systeme de resolution d'ambiguites pour clavier reduit
EP0924594A2 (fr) * 1997-12-19 1999-06-23 Nokia Mobile Phones Ltd. Dispositif et méthode d'entrée de texte dans un appareil mobile et appareil correspondant
EP0930760A2 (fr) * 1998-01-14 1999-07-21 Nokia Mobile Phones Ltd. Méthode et appareil de saisie d'information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708804A (en) * 1994-07-25 1998-01-13 International Business Machines Corp. Apparatus and method therefor of intelligently searching for information in a personal communications device
US5797098A (en) * 1995-07-19 1998-08-18 Pacific Communication Sciences, Inc. User interface for cellular telephone
WO1999015952A2 (fr) * 1997-09-25 1999-04-01 Tegic Communications, Inc. Systeme de resolution d'ambiguites pour clavier reduit
EP0924594A2 (fr) * 1997-12-19 1999-06-23 Nokia Mobile Phones Ltd. Dispositif et méthode d'entrée de texte dans un appareil mobile et appareil correspondant
EP0930760A2 (fr) * 1998-01-14 1999-07-21 Nokia Mobile Phones Ltd. Méthode et appareil de saisie d'information

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1259051A1 (fr) * 2001-05-11 2002-11-20 Tenovis GmbH & Co. KG Méthode et appareil de complétement automatique de numéros de téléphone utilisant une base de données
DE10123045A1 (de) * 2001-05-11 2002-11-21 Tenovis Gmbh & Co Kg Verfahren zur Eingabe einer Rufnummer in ein Telekommunikationsgerät sowie Telekommunikationsgerät
EP1603312A1 (fr) * 2004-06-01 2005-12-07 Samsung Electronics Co., Ltd. Procédé d'exécution de fonctions au moyen du numéro de téléphone recherché dans un terminal mobile
US7515941B2 (en) 2004-06-01 2009-04-07 Samsung Electronics Co., Ltd Method for performing functions using telephone number searched for in mobile terminal
WO2016034062A1 (fr) * 2014-09-03 2016-03-10 北京奇虎科技有限公司 Procédé et dispositif de consultation d'informations

Also Published As

Publication number Publication date
WO2001031509A3 (fr) 2001-09-13
AU1344301A (en) 2001-05-08

Similar Documents

Publication Publication Date Title
CA2387526C (fr) Systeme et procede de gestion d'informations de contact se fondant sur l'utilisation d'un dispositif de communications
US5768362A (en) Multiple field entry telephone directory for a cellular telephone
KR100719130B1 (ko) 인공지능 셀룰러폰에 있어서의 국제전화를 하는 다이어링방법
EP1780642B1 (fr) Telephone mobile et terminal d"informations mobile
US6411822B1 (en) Communication terminal
US6049796A (en) Personal digital assistant with real time search capability
EP0901263B1 (fr) Téléphone mobile et méthode de traitement de numéros téléphoniques dans un téléphone mobile
AU707694B2 (en) Network directory methods and systems for a cellular radiotelephone
US7463909B1 (en) Method, device, and database for providing communication addresses for communication devices
US5977887A (en) Data storage apparatus
US8874106B2 (en) Method and apparatus for providing automatic international and local call dialing in a mobile communication terminal
EP1924064B1 (fr) Téléphone portable
WO1999009729A1 (fr) Procede permettant de localiser des entrees memorisees dans un repertoire electronique et dispositif de communication connexe
US20020159583A1 (en) Bookmarking method and apparatus for an electronic phone book
WO2001031509A2 (fr) Systeme et procede d'acces et de stockage rapides d'informations de contact au moyen d'un dispositif de communication
WO1999055058A1 (fr) Systeme d'informations personnalisees
KR100529470B1 (ko) 이동통신 단말기의 전화번호 저장 방법
US20050129219A1 (en) Method and apparatus for dialing from a directory for a communication terminal
KR100360271B1 (ko) 휴대 통신 단말기의 전화번호 등록 및 검색 방법
CN1989494A (zh) 便携电话以及便携信息终端
GB2289826A (en) Method for accessing subscriber databases
KR20040008837A (ko) 이동 통신 단말기의 전화번호 자동 완성 방법
GB2305575A (en) Method for accessing subscriber databases
KR20030018471A (ko) 이동통신 단말기의 사업자 번호 자동 다이얼 방법
KR20000018534A (ko) 문자 입력에 의한 자동 다이얼링 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP