CA2507083A1 - Methods and systems for directory information lookup - Google Patents
Methods and systems for directory information lookup Download PDFInfo
- Publication number
- CA2507083A1 CA2507083A1 CA002507083A CA2507083A CA2507083A1 CA 2507083 A1 CA2507083 A1 CA 2507083A1 CA 002507083 A CA002507083 A CA 002507083A CA 2507083 A CA2507083 A CA 2507083A CA 2507083 A1 CA2507083 A1 CA 2507083A1
- Authority
- CA
- Canada
- Prior art keywords
- contact
- information
- user
- service center
- server
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42221—Conversation recording systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/09—Third party charged communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
- H04M3/387—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using subscriber identification cards
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/436—Arrangements for screening incoming calls, i.e. evaluating the characteristics of a call before deciding whether to answer it
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4931—Directory assistance systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4936—Speech interaction details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/36—Memories
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/40—Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/12—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place intelligent networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/66—Third party billing, i.e. third party can also be the predetermined telephone line of the caller if he is calling from another telephone set
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
- H04M3/382—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using authorisation codes or passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42204—Arrangements at the exchange for service or number selection by voice
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
- H04M3/4931—Directory assistance systems
- H04M3/4933—Directory assistance systems with operator assistance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/537—Arrangements for indicating the presence of a recorded message, whereby the presence information might include a preview or summary of the message
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13034—A/D conversion, code compression/expansion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13093—Personal computer, PC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/1322—PBX
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13224—Off-net subscriber, dial in to/out from network, teleworking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13282—Call forward, follow-me, call diversion
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Human Computer Interaction (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
Systems and methods are provided for obtaining contact-related information associated with a party using an identifier. The identifier may include a calling party number, a previously-dialed number, and/or a number specified by a user. The identifier could also include an e-mail address, an instant messenger address, a photograph, etc. A request for contact-related information may be initiated by a user and/or a device associated with the user. The request may include an identifier associated with a party. Methods and systems may retrieve contact-related information associated with the party using the identifier. Methods and systems may leverage one or more networks to retrieve the contact-related information. Contact information may be retrieved in order to add a contact to a user~s address book.
Description
METHODS AND SYSTEMS FOR DIRECTORY INFORMATION LOOKUP
DESCRIPTION OF THE INVENTION
Technical Field [001] The present invention generally relates to communication systems and, more specifically, to methods and systems for obtaining directory information.
Back r [003] A wide variety of means exist for communication between users.
For example, a user may conduct phone calls via a home phone, work phone, and mobile phone. In addition, users may also communicate using devices such as PC's, PDA's, pagers, etc. using manners of communicating as email and instant messaging.
[004] Unfortunately, managing such a wide variety of communication means can be difficult. In particular, as a user changes location, communication with the user may vary. For example, while on travel, it may only be possible to reach a user by mobile phone. However, the user may best be reached by email while at work. Also, the user may wish to implement various rules for receiving and controlling communications. For example, to be reached at home, the user may want the home phone to ring three times before forwarding the call to a mobile phone. As another example, the user may wish to be paged each time an email is received from a particular person while away from the office.
[005] Typically, to implement communication management, a person must individually manage each communication device separately. Thus, when the user wishes to change how communication is managed, the user may have to deal with numerous devices and, perhaps, service centers.
[006] Further, conventional systems ofFer limited incoming call management options. One common option in conventional systems is "Caller ID," which enables a receiving party to view a calling party's telephone number. Some systems, (e.g., digital cell phones) automatically store all
DESCRIPTION OF THE INVENTION
Technical Field [001] The present invention generally relates to communication systems and, more specifically, to methods and systems for obtaining directory information.
Back r [003] A wide variety of means exist for communication between users.
For example, a user may conduct phone calls via a home phone, work phone, and mobile phone. In addition, users may also communicate using devices such as PC's, PDA's, pagers, etc. using manners of communicating as email and instant messaging.
[004] Unfortunately, managing such a wide variety of communication means can be difficult. In particular, as a user changes location, communication with the user may vary. For example, while on travel, it may only be possible to reach a user by mobile phone. However, the user may best be reached by email while at work. Also, the user may wish to implement various rules for receiving and controlling communications. For example, to be reached at home, the user may want the home phone to ring three times before forwarding the call to a mobile phone. As another example, the user may wish to be paged each time an email is received from a particular person while away from the office.
[005] Typically, to implement communication management, a person must individually manage each communication device separately. Thus, when the user wishes to change how communication is managed, the user may have to deal with numerous devices and, perhaps, service centers.
[006] Further, conventional systems ofFer limited incoming call management options. One common option in conventional systems is "Caller ID," which enables a receiving party to view a calling party's telephone number. Some systems, (e.g., digital cell phones) automatically store all
2 incoming calls in a rolling list as they are received. However, such systems typically provide limited FIFO storage and usually store only the received numbers. Further, current systems do not allow users to retrieve contact information from a calling party number on demand and to add contact information to a contact list. Also, with current systems, users cannot easily select a listing from multiple listings.
[007] Methods, systems, and articles of manufacture consistent with certain embodiments of the present invention are directed to obviating one or more of the issues set forth above.
SUMMARY
[008] Systems and methods consistent with the present invention may obtain contact information associated with a party using an identifier (e.g., a telephone number). In certain embodiments consistent with the present invention, systems and methods may receive a request for contact-related information associated with a party. Consistent with principles of the present invention, the request may include an identifier associated with the party.
The identifier for which contact information is requested may be a telephone number received by a user (e.g., a calling party number), previously dialed by the user (e.g., from an outgoing call history or log), and/or specified by the user. The identifier could also include an e-mail address, an instant messenger address, a photograph, etc. The request for contact information may be initiated by a user and/or a device associated with the user. Methods and systems may retrieve contact-related information associated with the party using the identifying information. Methods and systems may leverage one or more networks to retrieve the contact-related information. In certain embodiments of the present invention, systems and methods may transmit a query that includes the identifier to a data operations center, which, in response, may retrieve and provide contact information. A user may access the contact information via, for example, a user terminal. In certain implementations, systems and methods consistent with the present invention
[007] Methods, systems, and articles of manufacture consistent with certain embodiments of the present invention are directed to obviating one or more of the issues set forth above.
SUMMARY
[008] Systems and methods consistent with the present invention may obtain contact information associated with a party using an identifier (e.g., a telephone number). In certain embodiments consistent with the present invention, systems and methods may receive a request for contact-related information associated with a party. Consistent with principles of the present invention, the request may include an identifier associated with the party.
The identifier for which contact information is requested may be a telephone number received by a user (e.g., a calling party number), previously dialed by the user (e.g., from an outgoing call history or log), and/or specified by the user. The identifier could also include an e-mail address, an instant messenger address, a photograph, etc. The request for contact information may be initiated by a user and/or a device associated with the user. Methods and systems may retrieve contact-related information associated with the party using the identifying information. Methods and systems may leverage one or more networks to retrieve the contact-related information. In certain embodiments of the present invention, systems and methods may transmit a query that includes the identifier to a data operations center, which, in response, may retrieve and provide contact information. A user may access the contact information via, for example, a user terminal. In certain implementations, systems and methods consistent with the present invention
3 may obtain contact information in order to add a contact to a user's address book or contact list.
[009] Both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention in any manner whatsoever.
BRIEF DESCRIPTION OF THE DRAWINGS
[010] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the description, serve to explain principles of the invention. In the drawings:
[011] Fig. 1 is a diagram of an exemplary data processing and telecommunications environment in which features and aspects consistent with the principals of the present invention may be implemented;
[012] Fig. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[013] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[014] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[015] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[016] Fig. 6 is a diagram illustrating an environment in which features and aspects consistent with certain embodiments of the present invention may be implemented;
[017] Fig. 7 is a flowchart depicting stages of a method consistent with certain embodiments of the present invention;
[018] Fig. 8 illustrates exemplary information which may be communicated by elements of the environment depicted in Fig. 6 in certain a embodiments of the present invention; and [019] Figs. 9A and 9B illustrate example programming code consistent with certain embodiments of the present invention.
[009] Both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention in any manner whatsoever.
BRIEF DESCRIPTION OF THE DRAWINGS
[010] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the description, serve to explain principles of the invention. In the drawings:
[011] Fig. 1 is a diagram of an exemplary data processing and telecommunications environment in which features and aspects consistent with the principals of the present invention may be implemented;
[012] Fig. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[013] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[014] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[015] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[016] Fig. 6 is a diagram illustrating an environment in which features and aspects consistent with certain embodiments of the present invention may be implemented;
[017] Fig. 7 is a flowchart depicting stages of a method consistent with certain embodiments of the present invention;
[018] Fig. 8 illustrates exemplary information which may be communicated by elements of the environment depicted in Fig. 6 in certain a embodiments of the present invention; and [019] Figs. 9A and 9B illustrate example programming code consistent with certain embodiments of the present invention.
4 DETAILED DESCRIPTION
[021] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the figures to refer to the same or like elements. The accompanying figures illustrate exemplary embodiments and implementations consistent with the present invention, but the description of those embodiments does not indicate or imply that other embodiments or implementations do not fall within the scope of present invention. It is to be understood that other implementations may be utilized and that structural and method changes may be made without departing from the scope of present invention.
[022] Fig. 1 is a block diagram of a data processing and telecommunications environment 100, in which features and aspects consistent with the present invention may be implemented. The number of components in environment 100 is not limited to what is shown and other variations in the number of arrangements of components are possible, consistent with embodiments of the invention. The components of Fig. 1 may be implemented through hardware, software, and/or firmware. Data processing and telecommunications environment 100 may include a data network 102, a voice network 104, and a service center 106. A user 110 may use a user terminal 112 to interface with data network 102 and may use phones 114, 116, and 118 to interface with voice network 104. Calling party 120 may use phone 122 to call a user, such as user 110, at any one of phones 114, 116, and 118.
[023] Data network 102 provides communications between the various entities depicted in environment 100 of Fig. 1, such as user terminal 112 and service center 106. Data network 102 may be a shared, public, or private network and encompass a wide area or local area. Data network 102 may be implemented through any suitable combination of wired and/or wireless communication networks. By way of example, data network 102 may be implemented through a wide area network (WAN), local area network (LAN), an intranet and/or the Internet. Further, the service center 106 may be connected to multiple data networks 102, such as, for example, to a wireless carrier network and to the Internet.
[024] Voice network 104 may provide telephony services to allow a calling party, such as calling party 120, to place a telephone call to user 110.
In one embodiment, voice network 104 may be implemented using a network, such as the Public Switched Telephone Network ("PSTN"). Alternatively, voice network 104 may be implemented using voice-over Internet Protocol ("VoIP") technology. In addition, voice network 104 may be implemented using both PSTN and VoIP technology consistent with the principles of the present invention. Further, service center 106 may be connected to multiple voice networks 104, such as for example, Verizon'sTM Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[025] Service center 106 provides a platform for managing communications over data network 102 and voice network 104. Service center 106 also provides gateway functions, such as code and protocol conversioris, to transfer communications between data network 102 and voice network 104. Service center 106 may be implemented using a combination of hardware, software, and/or firmware. For example, service center 106 may be implemented using a plurality of general purpose computers or servers coupled by a network (not shown). Although service center 106 is shown with direct connections to data network 102 and voice network 104, any number and type of network elements may be interposed between service center 106, data network 102, and voice network 104.
[026] User terminal 112 provides user 110 an interface to data network 102. For example, user terminal 112 may be implemented using any device capable of accessing the Internet, such as a general purpose computer or personal computer equipped with a modem. User terminal 112 may also be implemented in other devices, such as the BlackberryT"", and Ergo AudreyTM. Furthermore, user terminal 112 may be implemented in wireless devices, such as pagers, mobile phones (with data access functions), and Personal Digital Assistants ("PDA") with network connections.
[027] User terminal 112 also allows user 110 to communicate with service center 106. For example, user 110 may use instant messaging ("IM") to communicate with service center 106. In addition, user terminal 112 may use other aspects of TCP/IP including the hypertext transfer protocol ("HTTP"); the user datagram protocol ("UDP"); the file transfer protocol ("FTP"); the hypertext markup language ("HTML"); and the extensible markup language ("XML").
[028] Furthermore, user terminal 112 may communicate directly with service center 106. For example, a client application may be installed on user terminal 112, which directly communicates with service center 106. Also, user terrriinal 112 may communicate with service center 106 via a proxy.
[029] Phones 114, 116, 118, and 122 interface with voice network 104. Phones 114, 116, 118, and 122 may be implemented using known devices, including wireline phones and mobile phones. Although phones 114, 116, 118, and 122 are shown directly connected to voice network 104, any number of intervening elements, such as a private branch exchange ("PBX"), may be interposed between phones 114, 116, 118, and 122 and voice network 104.
[030] Fig. 2 is a block diagram of a user terminal consistent with the present invention. User terminal 112 includes a central processing unit (CPU) 200, a memory 202, a storage module 204, a network interface 206, an input interface 208, an output interface 210, an input device 216, and an output device 218.
[031] CPU 200 provides control and processing functions for user terminal 112. Although Fig. 2 illustrates a single CPU, user terminal 112 may include multiple CPUs. CPU 200 may also include, for example, one or more of the following: a co-processor, memory, registers, and other processing devices and systems as appropriate. CPU 200 may be implemented, for example, using a PentiumT"" processor provided from Intel Corporation.
[032] Memory 202 provides a primary memory for CPU 200, such as for program code. Memory 202 may be embodied with a variety of components of subsystems, including a random access memory ("RAM") and a read-only memory ("ROM"). When user terminal 112 executes an application installed in storage module 204, CPU 200 may download at least a portion of the program code from storage module 204 into memory 202. As CPU 200 executes the program code, CPU 200 may also retrieve additional portions of program code from storage module 204.
[033] Storage module 204 may provide mass storage for user terminal 112. Storage module 204 may be implemented with a variety of components or subsystems including, for example, a hard drive, an optical drive, CD ROM
drive, DVD drive, a general-purpose storage device, a removable storage device, and/or other devices capable of storing information. Further, although storage module 204 is shown within user terminal 112, storage module 204 may be implemented external to user terminal 112.
[034] Storage module 204 includes program code and information for user terminal 112 to communicate with service center 106. Storage module 204 may include, for example, program code for a calendar application, such as GroupWise provided by Novell Corporation or Outlook provided by Microsoft Corporation; a client application, such as a Microsoft Network Messenger Service (MSNMS) client or America Online Instant Messenger (AIM) client; and an Operating System (OS), such as the Windows Operation System provided by Microsoft Corporation. In addition, storage module 204 may include other program code and information, such as program code for TCP/IP communications; kernel and device drivers; configuration information, such as a Dynamic Host Configuration Protocol (DHCP) configuration; a web browser, such as Internet Explorer provided by Microsoft Corporation, or Netscape Communicator provided by Netscape Corporation; and any other software that may be installed on user terminal 112.
[035] Network interface 206 provides a communications interface between user terminal 112 and data network 102. Network interface 206 may receive and transmit communications for user terminal 112. For example, network interface 206 may be a modem, or a local area network ("LAN") port.
[036] Input interface 208 receives input from user 110 via input device 212 and provides the input to CPU 200. Input device 212 may include, for example, a keyboard, a microphone, and a mouse. Other types of input devices may also be implemented consistent with the principles of the present invention.
[037] Output interface 210 provides information to user 110 via output device 214. Output device 214 may include, for example, a display, a printer, and a speaker. Other types of output devices may also be implemented consistent with the principles of the present invention.
[038] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention. As shown, voice network 104 includes an intelligent service control point (ISCP) 302, service transfer points (STP) and 306, service switching points (SSP) 308 and 310, a line information database (LIDB) 312, an ISCP Service Provisioning And Creation Environment (SPACE) 314, a Recent Change Environment 316, and an Intelligent Peripheral (IP) 320.
[039] Voice network 104 may be implemented using the PSTN and SS7 as a signaling protocol. The SS7 protocol allows voice network 104 to provide features, such as call forwarding, caller-ID, three-way calling, wireless services such as roaming and mobile subscriber authentication, local number portability, and toll-free/toll services. The SS7 protocol provides various types of messages to support the features of voice network 104. For example, these SS7 messages may include Transaction Capabilities Applications Part ("TCAP") messages to support event "triggers," and queries and responses between ISCP 302 and SSPs 308 and 310.
[040] ISCP 302 may also be, for example, a standard service control point (SCP) or an Advanced Intelligent Network (AIN) SCP. ISCP 302 provides translation and routing services of SS7 messages to support the features of voice network 104, such as call forwarding. In addition, ISCP 302 may exchange information with the service center 106 using TCP/IP or SS7.
ISCP 302 may be implemented using a combination of known hardware and software. Although ISCP 302 is shown with a direct connection to service center 106 through ISCP SPACE 314, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP 302 and service center 106.
[041] STPs 304 and 306 relay SS7 messages within voice network 104. For example, STP 304 may route SS7 messages between SSPs 308 and 310. STP 302 may be implemented using known hardware and software from manufacturers such as NORTELT"" and LUCENT TechnologiesT"".
[042] SSPs 308 and 310 provide an interface between voice network 104 and phones 114 and 120, respectively, to setup, manage, and release telephone calls within voice network 104. SSPs 308 and 310 may be implemented as a voice switch, an SS7 switch, or a computer connected to a switch. SSPs 308 and 310 exchange SS7 signal units to support a telephone call between calling party 120 and user 110. For example, SSPs 308 and 310 may exchange SS7 messages, such as TCAP messages, within message signal units ("MSU") to control calls, perform database queries to configuration database 312, and provide maintenance information.
[043] Line Information Database (LIDB) 312 comprises one or more known databases to support the features of voice network 104. For example, LIDB 312 may include subscriber information, such as a service profile, name and address, and credit card validation information.
[044] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of ISCP 302 or be separate from ISCP 302. For example, the TelcordiaT"' ISCP may include an environment similar to SPACE
314 as part of the product. Further, ISCP SPACE 314 may include one or more servers. ISCP SPACE 314 is the point in the ISCP platform where customer record updates may be made.
[045] In one embodiment, customer records may be stored in ISCP
SPACE 314 such that the records may be updated and sent to ISCP 302.
These records may include information regarding how to handle calls directed to the customer. For example, these customer records may include information regarding whether or not calls for the customer are to be forwarded to a different number, andlor whether or not the call should be directed to an IP, such as a voice mail system, after a certain number of rings.
Additionally, one ISCP SPACE 314 may provide updates to one or more ISCPs 302 via an ISCP network (not shown).
[046] Additionally, voice network 104 may include one or more recent change engines 316 such as, for example, an Enterprise Recent Change engine (eRC); an Assignment, Activation, and Inventory System (AAIS); or a multi-services platform (MSP). As an example, the eRC and AAIS may be used in voice networks 104 located in the western part of the United States, while an MSP may be used in networks in the eastern part. The recent change engines may be used to update switch and ISCP databases. For example, a recent change engine may deliver database updates to SSPs and to ISCPs, such that when updating databases, these recent change engines emulate human operators. Additionally, if the instructions are to be sent to an ISCP 302, the recent change engine may first send the instructions to ISCP
SPACE 314, which then propagates the instructions to ISCP 302 as discussed above. Further, an MSP may be used, for example, for providing updates to both SSPs 308 or 310 and ISCPs 302. Or, for example, an eRC
may be used for providing updates to SSPs 308 or 310, while an AAIS is used for providing updates to ISCPs 302.
[047] Additionally, voice network 104 may include one or more intelligent peripherals (IP). For example, in Fig. 4, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing services, such as voice mail services.
[048] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention. As shown, service center 106 may include firewalls 402 and 404, one or more digital companion servers 406, one or more communication portal servers 408, one or more network access servers 410, and a voice portal 412. Voice portal 412 may include a voice portal application server 414 and a voice recognition server 416. A network 418 may be used to interconnect the firewalls and servers. Additionally, back end servers) 420 may be provided between service center 106 and voice network 104.
[049] Firewalls 402 and 404 provide security services for communications between service center 106, data network 102, and voice network 104, respectively. For example, firewalls 402 and 404 may restrict communications between user terminal 112 and one or more servers within service center 106. Any security policy may be implemented in firewalls 402 and 404 consistent with the principles of the present invention. Firewalls 402 and 404 may be implemented using a combination of known hardware and software, such as the Raptor Firewall provided by the Axent Corporation.
Further, firewalls 402 and 404 may be implemented as separate machines within service center 106, or implemented on one or more machines external to service center 106.
[050] Network 418 may be any type of network, such as an Ethernet or FDDI network. Additionally, network 418 may also include switches and routers as appropriate without departing from the scope of the invention.
Further, additional firewalls may be present in network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[051] Each server (406, 408, 410, 414, 416, 420) may be any type of server or computer, such as a Unix or DOS based server or computer. The servers may implement various logical functions, such as those described below. In Fig. 4, a different server is illustrated as being used for each logical function. In other embodiments, the logical functions may be split across multiple servers, multiple servers may be used to implement a single function, all functions may be performed by a single server, etc.
[052] In general, a digital companion server 406 may provide the software and hardware for providing specific services of the service center.
Exemplary services include, for example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, digital companion server 406 may facilitate acquisition of contact information associated with a caller upon receipt of the caller's telephone number (i.e., a Calling Party Number).
[053] A communication portal server 408 may provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. Network access servers 410 may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may be used for transmitting and/or receiving information from/to an ISCP 302 or an SSP 308 or 310 of voice network 104.
[054] Voice portal 412 includes software and hardware for receiving and processing instructions from a customer via voice. For example, a customer may dial a specific number for voice portal 412. Then the customer using speech may instruct service center 106 to modify the services to which the customer subscribes. Voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. Voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. Application function 414 may take, for example, the output from voice recognition function 416, convert it to a format suitable for service center 106 and forward the information to one or more servers (406, 408, 410) in service center 106.
[055] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention. As illustrated, the logical architecture may be split into four planes: client side plane 502, application service plane 504, network access plane 506, and the voice network plane 508.
[056] Client side plane 502 includes the user terminals 112 A and 112_B that a user may use to send and/or receive information to/from the service center 106. Additionally, client side 502 includes the user's phones) 114. As discussed above, user terminals 112 may be any type of device a user may use for communicating with Service Center 106. For example, user terminal 112 A may be a PDA running a program for communicating with Service Center 106, while user terminal 112_B may be a desktop type computer running a web browser for communicating with Service Center 106 via the Internet. Additionally, the user may have one or more phones 114, such as, for example, one or more standard landline telephones and/or wireless phones.
[057] Application service plane 504 includes digital companion servers) 406, communication portal servers) 408, and voice portal 412.
These entities may communicate between one another using, for example, web services or any other suitable protocols. Web services are a standardized way of integrating Web-based applications using the Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) open standards over an Internet protocol (IP) backbone.
[058] As illustrated, a digital companion server 406 may provide the following functions: a client proxy 512, a web server 514, an application server function 516, a calendar server function 518, a notification server function 520, and a database function 522. Each of these functions may be performed in hardware, software, and/or firmware. Further, these functions may each be executed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[059] Client proxy function 512 provides a proxy function for the digital companion that may be used for security purposes. This client proxy function 512 may be included in a separate server such that all communications sent from the other digital companion functions/servers to a user terminal 112 via data network 102 go through client proxy 512. Also, if client proxy 512 is included on a separate server, for example, an additional firewall may be provided between client proxy 512 and the other digital companion servers to provide additional security.
[060] Web server 514 provides functionality for receiving traffic over data network 102 from a customer. For example, web server 514 may be a standard web server that a customer may access using a web browser program, such as Internet Explorer or Netscape Communicator.
[061] Application server function 516 encompasses the general functions performed by digital companion servers) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific applications provided by the service center.
These services may include, for example, interfacing with other function(s), software, and/or hardware to provide a customer with the capability of managing their calls online. For example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, application server function 516 may facilitate obtaining contact information associated with a Calling Party Number (CPN) when the customer receives an incoming call from the CPN.
[062] Additionally, application server function 516 may interface with one or more external devices, such as an external web server, for retrieving or sending information. For example, application server function 516 may interface with a voice network's data center 556 (e.g., verizon.com) to determine the services to which the customer subscribes (e.g., call waiting, call forwarding, voice mail, etc.).
[063] Calendar server function 518 may provide the capability of scheduling events, logging when certain events occurred, triggering the application-functions to perform a function at a particular time, etc.
[064] Notification server function 520 provides the capability to send information from service center 106 to a user terminal 112. For example, notification server function 520 at the direction of application server function 516 may send a notification to user terminal 112 that the user is presently receiving a phone call at user's phone 114.
[065] Database function 522 provides the storage of information useable by the various applications executed by the digital companion servers. These databases may be included in, for example, one or more external storage devices connected to the digital companion servers.
Alternatively, the databases may be included in storage devices within the digital companion servers themselves. The storage devices providing database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[066] As discussed above, communication portal servers) 408 provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. As illustrated in Fig. 5, a communication portal server 408 may provide the following functions: a web server function 526, an application server function 528, a contacts database function 530, and/or a customer profile function 532. Each of these functions may be performed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[067] Web server function 526, as with web server function 522 of the digital companion servers, provides functionality for receiving traffic over data network 102 from a customer. For example, the web server may be a standard web server that a customer may access using a web browser, such as Internet Explorer or Netscape Communicator.
[068] Application server function 528 encompasses the general functions performed by communication portal servers 408. For example, these functions may include interfacing with the voice network to retrieve and/or modify customer profile information, and creating and editing an address book for the user. Additionally, application server function 528 may include the functionality of sending and/or receiving information to/from external servers and/or devices. For example, communication portal servers 408 may be connected to a network, such as, the Internet. Application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages webpage.
Application function 528 could then contact these external services 552 to retrieve information, such as an address for a person in the user's address book.
[069] In another example, application server function 528 of communication portal 408 may interface a single sign on (SSO) server 554.
SSO 554 may be used to allow users to access all services to which the user subscribes, on the basis of a single authentication that is performed when they initially access the network.
[070] Contacts database 530 includes storage devices for storing an address book for the user. This address book may be any type of address book. For example, the user's address book may, include the names, phone numbers, and addresses of people and/or organisations. These storage devices may be internal or external to communication portal servers 408 or some combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[071] Customer profile database 532 includes storage devices for storing customer profile information for the user. These storage devices may be the same or separate storage devices used for the contacts database.
The customer profile may include information regarding the user's account for their voice network. For example, this information may include the user's name, billing address, and other account information. Additionally, the customer profile may include information regarding voice services to which the user subscribes, such as, for example, call waiting, voice mail, etc.
[072] Additionally, application services plane 504 of the architecture may include a voice portal 412. As discussed above, voice portal 412 may include, for example, a voice recognition function 416 and an application server function 414, and be used for receiving and processing instructions from a customer via voice. The voice recognition function may be implemented using hardware and/or software capable of providing voice recognition capabilities. This hardware and/or software may be a commercially available product, such as the Voice Application platform available from Tellme Networks, Incorporated. Application server function 414 of voice portal 412 may include hardware and/or software for exchanging information between digital companion servers 406 and voice recognition function 416. Additionally, application server function 414 may be included on a separate server, included in the hardware and software providing voice recognition function 416, included in digital companion servers 406, etc.
[073] Network Access plane 506 of the architecture includes the functions for providing connectivity between application service plane 502 and voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[074] As discussed above, recent change engines 316 may be used to update switches and ISCP databases included in voice network 104. In one embodiment, recent change engines 316 may include an AAIS 544, an eRC 546, and/or an MSP 548. Additionally, a proxy 542 may be used between digital companion servers 406 and recent change engines 542 for security purposes.
[075] Network access servers 410 may be included in the service center 106 and may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may include a Caller ID (CID) functionality for retrieving caller ID
information from voice network 104, a click to dial (CTD) functionality for instructing an intelligent peripheral (IP) in the voice network to place a call via an SSP, and/or a real time call management (RTCM) functionality for interfacing with an ISCP of the voice network.
[076] Network Access,plane 506 may also include one or more back end servers) 420. These back end servers) 420 may include hardware and/or software for interfacing service center 106 and voice network 104.
Back end servers) 420 may be connected to service center 106 by a network, by a direct connection, or in any other suitable manner. Further, back end servers) 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner.
[077] Back end servers) 420 may include, for example, a server providing a voice mail retrieval and notification function. For example, this voice mail retrieval and notification function may include the capability to receive notifications when a user receives a voice mail, physically call a user's voice mail system, enter the appropriate codes to retrieve the voice mail, retrieve the voice mail, convert the voice mail to a digital file, and send it to digital companion servers 406.
[078] Additionally, back end servers) 420 may also include, for example, a directory assistance server. This directory assistance server may, for example, interface service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of voice network 104. A RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of voice network 104 for name and/or address information associated with a phone number and receiving the name and/or phone number in response to this request.
Additional details of the RDA gateway and DOC are described below in connection with Fig. 6.
[079] In another example, back end servers) 420 may include a wireless Internet gateway that is used for interfacing with a mobile switching center (MSC) of a wireless voice network. As with the above-described back end servers) 420, this wireless Internet gateway may be used for converting requests and information between the formats used by service center 106 and those used by the wireless voice network.
[080] In yet another example, back end servers) 420 may include a conference blasting server for instructing a conference bridge in voice network 104 to dial out via an SSP to the participants of a voice conference. Or for example, the back end servers) may include a server for instructing an IP of the voice network to place a call between two parties by dialing out to each of the parties. Back end servers) 420 may also include the capability to instruct the bridge or IP device to call an audio digitizing device that can listen to the conference, convert the audio signals to digital format, and forward the digitized signals to a user device via, for example, an audio streaming server.
The audio streaming server may, for example, allow a user to connect to it via, for example, the Internet. Additionally, the audio streaming device may buffer or record the signals to permit the user to pause, rewind, and/or fast-forward thru the conference.
[081] In yet another example, back end servers) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a SMS gateway in voice network 104. This may be used for example to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the users chosing.
[082] Voice network plane 508 includes the hardware and software included in voice network 104, as discussed above with reference to Fig. 3.
For example, voice network plane 508 may include ISCP SPACE 314, ISCP
302, intelligent peripherals 320, and SSP 308. Additionally, voice network plane 508 may also include the hardware and software included in a wireless carrier's network, such as, for example, the mobile switching center, etc.
[083] For clarity of explanation, system 100 is described herein with reference to the discrete functional elements illustrated in Figs. 1-5.
However, it should be understood that the functionality of these elements and modules may overlap and/or may exist in a fewer or greater number of elements and modules. Elements of system 100 may, depending on the implementation, lack certain illustrated components and/or contain, or be coupled to, additional or varying components not shown. Moreover, all or part of the functionality of the elements illustrated in Figs. 1-5 may co-exist or be distributed among several geographically dispersed locations.
[084] In certain embodiments, methods and systems consistent with present invention may perform a Reverse Directory Assistance (RDA) lookup.
As used herein, the term "RDA lookup" refers to obtaining contact-related information associated with a party by way of a telephone number or other identifier associated with that party. As used herein, the term "party"
encompasses any entity for which contact-related information may be retrieved, such as individuals, groups, businesses, retail establishments, service providers, etc. Consistent with embodiments of the present invention, contact-related information may include one or more of a name, home address, business address, home telephone number, business telephone number, cell phone number, instant messenger address, IP address, biometric information (e.g., fingerprints, voice prints, retinal scans, etc.) visual information (e.g., digital images, photographs, etc.), audio information, personal information (e.g., birth date, favorite movies, favorite songs, etc.), public records, credit reports, police records, driving records, banking statements, and contact-related information associated with relatives and/or friends. In certain embodiments, contact-related information may include information associated with, or retrieved via, one or more networks.
[085] Although a telephone number is used herein to explain principles and aspects of the present invention, the present invention contemplates the use of other identifiers to retrieve information associated with parties, such as e-mail addresses, fax numbers, Caller ID information, predetermined ID codes, network addresses, photographs, digital images, audio signals, video signals, etc. For example, a photo of an individual may be used to retrieve contact-related information associated with that individual.
[086] Consistent with principles of the present invention, an RDA
lookup may be triggered by a Calling Party Number (CPN). For example, upon user 110 receiving (via telephones 114, 116, etc.) a call from a caller (having an associated CPN), contact information may be obtained for the caller using the received CPN. Additionally or alternatively, an RDA lookup may used to obtain information associated with telephone numbers stored in a history (or call log) of incoming and/or outgoing calls. Further, a user could specify a telephone number for which to obtain contact information by for, example, inputting the number to user terminal 112. In one embodiment of the present invention, user 110 could initiate an RDA lookup. Also, one or more systems associated with user 110 (e.g., user terminal 112 and server 406) could automatically initiate an RDA lookup. Consistent with embodiments of the present invention, contact information may be obtained in order to add a party to a user's address book or contact list, which may, as mentioned above, be maintained by contacts database 530.
[087] Fig. 6 illustrates an environment 600 in which RDA processes consistent with embodiments of the present invention may be implemented.
As illustrated, environment 600 may include service center 106, data network 102, back end server 420, an RDA Gateway 610, an RDA proxy server 620, a directory network 630, a Data Operations Center (DOC) 640, and a listings lexicon 650.
[088] As mentioned above, back end server 420 may include hardware and/or software for interfacing service center 106 with voice network 104. In one example, back end server 420 may include or leverage one or more search engines. Back end server 420 may be connected to service center 106 via a network (e.g., corporate network 675), a direct connection, or in any other suitable manner. Further, back end server 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner. In environment 600, back end servers) 420 may include or be configured to operate as one or more RDA application server(s). As such, back end server 420 may interface service center 106 with RDA Gateway 610 of voice network 104.
[089] In certain embodiments, one or more firewalls (e.g., firewall 404) may be interposed between back end server 420 and one or more servers within service center 106 to provide security services. Such firewalls may be implemented external to service center 106, as illustrated in Fig. 6, and/or implemented within service center 106.
[090] RDA Gateway 610 may include one or more devices, components and/or processes (e.g., implemented in software, firmware, and/or hardware) configured to facilitate information exchange between back end server 420 and voice network 104. In certain configurations, RDA
Gateway 610 may perform routing functions, switching functions, code conversions, and/or protocol conversions. RDA Gateway 610 may, consistent with embodiments of the present invention, accept messages and requests from back end server 420, issue requests/queries for contact information, and provide information, which may include contact information, back to server 420. In one example, RDA Gateway 610 may accept HTTP messages from back end sever 420 and respond to server 420 using XML. Alternatively, the Standard Generalized Markup Language (SGML) and/or any other language that facilitates the creating and sharing of common information formats may be employed. In one embodiment, RDA Gateway 610 may send server 420 a Document Type Definition (DTD), which describes response format(s). In addition, or as alternative to a DTD, any other schema and/or means for validating a language (e.g., XML) may be employed for describing response formats. Additional details of responses are discussed below in connection with Figs. 7 and 8.
[091] As illustrated in Fig. 6, RDA Gateway 610 may be coupled to a directory network 630. Directory network 630 may, in certain implementations, be coupled to or included in voice network 104. Directory network 630 may include any combination of components and/or services configured to provide contact-related information. Directory network 630 may include, for example, Verizon'sT"" LiveSource National Directory Assistance network and/or any other directory and/or operator service network.
[092] In exemplary implementations, directory network 630 may include or be coupled to DOC 640. DOC 640 may include one or more devices, mechanisms, and/or services for maintaining, and/or processing requests for, contact-related information. In environment 600, DOC 640 may include or be coupled to a lexicon 650, which may be a compilation of contact-related information (e.g., listing information) associated with callers.
Lexicon 650 may, for example, be implemented via one or more databases, such as a relational database, a distributed database, and/or an object-oriented programming database. Information included in lexicon 650 may be obtained, maintained, and updated via one or more telephone companies (e.g., VerizonT""), listing house sources, andlor operator referrals. Listing information may include, but is not limited to, one or more of: a phone number, name, street, city, state, zip code, non published flag, and billing type (e.g., local or national).
[093] In certain embodiments, environment 600 may include RDA
proxy server 620, which may serve as an application level proxy server that allows known/trusted messages to pass between service center 106 and RDA
Gateway 610. RDA proxy server 620 may, for instance, log errors and attempts by other devices to gain access to the trusted network segment.
[094] Fig. 7 is a flowchart depicting exemplary stages in an RDA
lookup process consistent with embodiments of the present invention. The illustrated process may begin with an RDA lookup request (stage 710). In certain implementations, an RDA lookup request may be initiated by user 110 and/or a device associated with user 110 in response to a user action/input.
Initiating (or triggering) an RDA request may involve generating and/or transmitting, as well as causing the generation/transmission of, the request.
In one example, user terminal 112 may transmit, in response to instructions received by user 110, an RDA lookup request for a particular telephone number to digital companion server 406 in service center 106. User 110 may, in certain instances, trigger an RDA lookup for a CPN upon viewing a CPN
from a caller ID display. Further, a user could trigger an RDA lookup request by for, example, inputting a telephone number to, or selecting a telephone number from, user terminal 112. User 110 may, additionally or alternatively, trigger an RDA lookup by selecting a telephone number from a history of incoming and/or outgoing calls (i.e., a call log), which may be stored, for example, by one or more elements within service center 106 and accessible by user terminal 112. In certain embodiments of the present invention, user 110 may be prompted to initiate an RDA lookup request. For example, server 406 and/or user terminal 112 may prompt user .110 to initiate an RDA request when an outgoing or incoming call occurs or is logged. User 110 may, for instance, initiate an RDA request in order to add a contact to an address book or contact list (e.g., stored by contacts database 530).
[095] Consistent with embodiments of the present invention, an RDA
lookup request may be initiated (stage 710) by a device associated with user 110 automatically, without user action/input and with or without a user's knowledge. In one example, an RDA lookup request may be initiated (e.g., by user terminal 112 and/or server 406) when an incoming call is received by a calling device associated with user 110 (e.g., telephone 114). Additionally, an RDA request could be initiated automatically by user terminal 112 and/or service center 106 (via server 406) when a contact is being added to user 110's contact list. That is, obtaining contact information for a telephone number could be part of the process of adding a contact to the contact list.
Consistent with principles of the present invention, incoming and/or outgoing calls may be logged by one or more elements in service center 106 (e.g., server 406), and service center 106 may (e.g., via server 406) automatically initiate RDA requests for such numbers. Such requests may be automatically initiated to add contacts to a user's address book. In certain embodiments, RDA processes may be leverage to update or refresh a user's address book.
In such embodiments, RDA lookup requests may be initiated automatically and/or on demand in order to update a user's address book with current contact-related information. In one example, a user may input a command (e.g., via user terminal 112) that initiates one or more RDA lookup requests in order to refresh the address book. Additionally, or alternatively, RDA lookup requests may be periodically initiated, without user intervention, in order to refresh the address book.
[096] After an RDA lookup request is initiated, the request may be forwarded to back end server 420 (stage 720). In certain embodiments, the RDA lookup request may be transmitted from service center 106 (e.g., from server 406) to back end server 420. The RDA lookup request may also be routed through firewall 404. Upon receiving the request, back end server 420 may authenticate the request and transmit an RDA query to RDA Gateway 610 (stage 730). Authenticating the request may be optional.
[097] In certain embodiments, upon receiving the request (stage 720), back end server 420 may, in addition or as alternative to transmitting an RDA
query to RDA Gateway 610, leverage one or more search engines and/or network services (e.g., Google, Super Pages) to retrieve certain contact-related information. In one example, back end server 420 may leverage one or more search engines to retrieve certain contact-related information (e.g., public records from the Internet) and, in addition, transmit an RDA request for other information (e.g., listing information) to RDA Gateway 610. In other examples, back end server 420 may retrieve contact-related information, and RDA Gateway 610 may be unnecessary. In such cases where RDA Gateway 610 is not leveraged, stages 730-750 may not be performed in the process of Fia. 7.
[098] An RDA query transmitted from back end server 420 to RDA
Gateway 610 (stage 730) may, in one implementation, include the telephone number for which contact information is desired and an identifier associated with user 110 (customer ID). As explained above, the telephone number for which contact information is requested may be a telephone number received by user 110 (e.g., a calling party number), previously dialed by user 110 (e.g., from an outgoing call history or log), and/or specified/selected by user 110.
The customer ID may, for example, include user 110's primary telephone number. In certain embodiments of the present invention, the RDA query may be transmitted or routed from back end server 420 to RDA Gateway 610 through RDA proxy server 620. Back end server 420 may, in certain embodiments, transmit the RDA query to RDA Gateway 610 via HTTP. In one example, the RDA query may be in the form of a Universal Resource Locator (URL) having the following exemplary format:
http://RDAGateway/RDAQuery.aspx?customerlD=2129999999&IookuplD=21255512 In the above example URL, RDAGatevvay may be a name or IP address associated with RDA Gateway 610; customerlD may be the primary telephone of user 110; and IookuplD may be the telephone on which the query is performed.
[099] Upon receiving the RDA query, RDA Gateway 610 may forward the query to DOC 640 (stage 740). As described above, DOC 640 may include or be coupled to listing lexicon 650, which may be implemented via one or more database(s). Accordingly, RDA Gateway 610 may query the listing lexicon for contact information associated with the telephone number included in the query. Consistent with principles of the present invention, RDA Gateway 610 may expect a response from listing lexicon 650 as described in an Interface Protocol Specification provided by a database vendor. In response to the RDA query, DOC 640 may provide (e.g., to RDA
Gateway 610) listing information associated with the telephone number in the query. For example, a phone number, name, street, city, state, and/or zip code may be returned. Additionally or alternatively, one or more flags and/or errors may be returned. For example, if the particular party associated with the telephone number of interest has indicated that contact information is to remain private, a non-published flag may be returned from DOC 640. DOC
640 may also provide an indication of an internal processing error or timeout period expiration. Information provided by DOC 640 may also include a billing type (e.g., local or national) for user 110. Consistent with principles of the present invention, single listings and/or multiple listings may be provided by DOC 640 for a given telephone number. For example, families may list spouses and children separately and with the same number, and small business may list multiple parties with a particular number.
[0100] After sending the RDA query to DOC 640, RDA Gateway 610 may send a response to back end server 420 (stage 750). At this stage, RDA
Gateway 610 may also record the customer ID to facilitate billing. The response may, in one example, include (or reflect) information provided by and received from DOC 640. RDA Gate'viray 610 may, in one configuration, respond to back end server 420 via XML. RDA Gateway 610 may therefore convert/format information received from DOC 640 to an XML message and route the message to back end server 420. As mentioned above, RDA
Gateway 610 may send server 420 a Document Type Definition (DTD), which describes response format(s). RDA Gateway 610 may, in certain configurations, support one or more of the following response types: Single Listing, Multiple Listings, Non-Published Listings, No Listing, Invalid Phone Number, Service Not Available, Database Error, Query Timeout. Table 1 of Fig. 8 illustrates the above-mentioned responses and their corresponding conditions; Figs. 9A and 9B collaboratively illustrate XML format 900, which depicts an example XML format for each response.
[0101] Consistent with embodiments of the present invention, the response to back end server 420 may include contact-related information (e.g., listing information) associated with the telephone number of interest, which may be received from DOC 640. For example, the response from Gateway 610 to back end server 420 may include one or more of: a phone number, name, street, city, state, zip code. The response may also include network-related information, public records, family information, images, audio information, etc. In addition, the response may include (or reflect) one or more flags and/or errors, as discussed above.
[0102] In the illustrated process of Fig. 7, back end server 420 may forward RDA lookup results to one or more components in service center 106 (stage 760). For example, such results (e.g., listing information, flags, errors, etc. received from DOC 640 via RDA Gateway 610) may be transmitted to server 406. In addition, or as an alternative, contact-related information retrieved by back end server 420 using one or more search engines and/or network services may be transmitted to server 406. The process of Fig. 7 may then provide user 110 with access to the RDA lookup results (stage 770).
Access may, for example, be provided via server 406 and user terminal 112.
Providing access to RDA lookup results (stage 770) may involve presenting user 110 with listing information associated with the telephone number of interest. Providing access to RDA lookup results may also involve notifying user 110 that one or more errors occurred or that information is not available (e.g., not published) for the telephone number of interest.
[0103] After access is provided to user 110 (stage 770), user 110 may respond to the RDA lookup results (stage 780). In one example, where listing information is obtained, user 110 may select listing information (stage 780) to add to the contact list. For example, user 110 may input a command to user terminal 112 that causes the listing information to be inserted in the contact list. In certain embodiments, user terminal 112 may, in response to such a command, communicate with service center 106 (e.g., server 406), thereby causing the information to be added to the contact list. In some instances, as mentioned above, multiple listings for a number may be obtained and presented to the user. In such instances, user 110 may select one or more of the listings to add to the contact list. If errors have occurred or information is not available for a particular number, user 110 may initiate another RDA
lookup request for the same or different number. In alternative embodiments, user 110 may select listing information for other processing (e.g., by server 406). Responding to results (stage 780) may also involve responding to one or more error messages.
[0104] The steps illustrated in the flowchart of Fig. 7 are consistent with exemplary implementations of the instant invention. Further, it should be understood that the sequence of events described in Fig. 7 are exemplary and not intended to be limiting. Thus, other method steps may be used, and even with the method depicted in Fig. 7, the particular order of events may vary without departing from the scope of the present invention. Moreover, certain steps may not be present and additional steps may be implemented in Fig. 7.
In addition, it should be understood that the stages of Fig. 7 may be modified with departing from the scope of the present invention. For example, in certain implementation, information may be exchanged between DOC 640 and back end server 420 without the use of RDA Gateway 610.
[0105] Embodiments consistent with the invention may be implemented in various environments. Further, the processes described herein are not inherently related to any particular apparatus and may be implemented by any suitable combination of components. Moreover, various types of general purpose devices may be used in accordance with the teachings described herein.
[0106] The exemplary systems and methods consistent with present invention described above are illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0107] The present invention has been described in relation to particular examples which are intended in all respects to be illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0108] Additionally, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only. To this end, it is to be understood that inventive aspects lie in less than all features of a single foregoing disclosed embodiment, implementation, or configuration. Thus, the true scope and spirit of the invention depends on the following claims.
[021] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the figures to refer to the same or like elements. The accompanying figures illustrate exemplary embodiments and implementations consistent with the present invention, but the description of those embodiments does not indicate or imply that other embodiments or implementations do not fall within the scope of present invention. It is to be understood that other implementations may be utilized and that structural and method changes may be made without departing from the scope of present invention.
[022] Fig. 1 is a block diagram of a data processing and telecommunications environment 100, in which features and aspects consistent with the present invention may be implemented. The number of components in environment 100 is not limited to what is shown and other variations in the number of arrangements of components are possible, consistent with embodiments of the invention. The components of Fig. 1 may be implemented through hardware, software, and/or firmware. Data processing and telecommunications environment 100 may include a data network 102, a voice network 104, and a service center 106. A user 110 may use a user terminal 112 to interface with data network 102 and may use phones 114, 116, and 118 to interface with voice network 104. Calling party 120 may use phone 122 to call a user, such as user 110, at any one of phones 114, 116, and 118.
[023] Data network 102 provides communications between the various entities depicted in environment 100 of Fig. 1, such as user terminal 112 and service center 106. Data network 102 may be a shared, public, or private network and encompass a wide area or local area. Data network 102 may be implemented through any suitable combination of wired and/or wireless communication networks. By way of example, data network 102 may be implemented through a wide area network (WAN), local area network (LAN), an intranet and/or the Internet. Further, the service center 106 may be connected to multiple data networks 102, such as, for example, to a wireless carrier network and to the Internet.
[024] Voice network 104 may provide telephony services to allow a calling party, such as calling party 120, to place a telephone call to user 110.
In one embodiment, voice network 104 may be implemented using a network, such as the Public Switched Telephone Network ("PSTN"). Alternatively, voice network 104 may be implemented using voice-over Internet Protocol ("VoIP") technology. In addition, voice network 104 may be implemented using both PSTN and VoIP technology consistent with the principles of the present invention. Further, service center 106 may be connected to multiple voice networks 104, such as for example, Verizon'sTM Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[025] Service center 106 provides a platform for managing communications over data network 102 and voice network 104. Service center 106 also provides gateway functions, such as code and protocol conversioris, to transfer communications between data network 102 and voice network 104. Service center 106 may be implemented using a combination of hardware, software, and/or firmware. For example, service center 106 may be implemented using a plurality of general purpose computers or servers coupled by a network (not shown). Although service center 106 is shown with direct connections to data network 102 and voice network 104, any number and type of network elements may be interposed between service center 106, data network 102, and voice network 104.
[026] User terminal 112 provides user 110 an interface to data network 102. For example, user terminal 112 may be implemented using any device capable of accessing the Internet, such as a general purpose computer or personal computer equipped with a modem. User terminal 112 may also be implemented in other devices, such as the BlackberryT"", and Ergo AudreyTM. Furthermore, user terminal 112 may be implemented in wireless devices, such as pagers, mobile phones (with data access functions), and Personal Digital Assistants ("PDA") with network connections.
[027] User terminal 112 also allows user 110 to communicate with service center 106. For example, user 110 may use instant messaging ("IM") to communicate with service center 106. In addition, user terminal 112 may use other aspects of TCP/IP including the hypertext transfer protocol ("HTTP"); the user datagram protocol ("UDP"); the file transfer protocol ("FTP"); the hypertext markup language ("HTML"); and the extensible markup language ("XML").
[028] Furthermore, user terminal 112 may communicate directly with service center 106. For example, a client application may be installed on user terminal 112, which directly communicates with service center 106. Also, user terrriinal 112 may communicate with service center 106 via a proxy.
[029] Phones 114, 116, 118, and 122 interface with voice network 104. Phones 114, 116, 118, and 122 may be implemented using known devices, including wireline phones and mobile phones. Although phones 114, 116, 118, and 122 are shown directly connected to voice network 104, any number of intervening elements, such as a private branch exchange ("PBX"), may be interposed between phones 114, 116, 118, and 122 and voice network 104.
[030] Fig. 2 is a block diagram of a user terminal consistent with the present invention. User terminal 112 includes a central processing unit (CPU) 200, a memory 202, a storage module 204, a network interface 206, an input interface 208, an output interface 210, an input device 216, and an output device 218.
[031] CPU 200 provides control and processing functions for user terminal 112. Although Fig. 2 illustrates a single CPU, user terminal 112 may include multiple CPUs. CPU 200 may also include, for example, one or more of the following: a co-processor, memory, registers, and other processing devices and systems as appropriate. CPU 200 may be implemented, for example, using a PentiumT"" processor provided from Intel Corporation.
[032] Memory 202 provides a primary memory for CPU 200, such as for program code. Memory 202 may be embodied with a variety of components of subsystems, including a random access memory ("RAM") and a read-only memory ("ROM"). When user terminal 112 executes an application installed in storage module 204, CPU 200 may download at least a portion of the program code from storage module 204 into memory 202. As CPU 200 executes the program code, CPU 200 may also retrieve additional portions of program code from storage module 204.
[033] Storage module 204 may provide mass storage for user terminal 112. Storage module 204 may be implemented with a variety of components or subsystems including, for example, a hard drive, an optical drive, CD ROM
drive, DVD drive, a general-purpose storage device, a removable storage device, and/or other devices capable of storing information. Further, although storage module 204 is shown within user terminal 112, storage module 204 may be implemented external to user terminal 112.
[034] Storage module 204 includes program code and information for user terminal 112 to communicate with service center 106. Storage module 204 may include, for example, program code for a calendar application, such as GroupWise provided by Novell Corporation or Outlook provided by Microsoft Corporation; a client application, such as a Microsoft Network Messenger Service (MSNMS) client or America Online Instant Messenger (AIM) client; and an Operating System (OS), such as the Windows Operation System provided by Microsoft Corporation. In addition, storage module 204 may include other program code and information, such as program code for TCP/IP communications; kernel and device drivers; configuration information, such as a Dynamic Host Configuration Protocol (DHCP) configuration; a web browser, such as Internet Explorer provided by Microsoft Corporation, or Netscape Communicator provided by Netscape Corporation; and any other software that may be installed on user terminal 112.
[035] Network interface 206 provides a communications interface between user terminal 112 and data network 102. Network interface 206 may receive and transmit communications for user terminal 112. For example, network interface 206 may be a modem, or a local area network ("LAN") port.
[036] Input interface 208 receives input from user 110 via input device 212 and provides the input to CPU 200. Input device 212 may include, for example, a keyboard, a microphone, and a mouse. Other types of input devices may also be implemented consistent with the principles of the present invention.
[037] Output interface 210 provides information to user 110 via output device 214. Output device 214 may include, for example, a display, a printer, and a speaker. Other types of output devices may also be implemented consistent with the principles of the present invention.
[038] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention. As shown, voice network 104 includes an intelligent service control point (ISCP) 302, service transfer points (STP) and 306, service switching points (SSP) 308 and 310, a line information database (LIDB) 312, an ISCP Service Provisioning And Creation Environment (SPACE) 314, a Recent Change Environment 316, and an Intelligent Peripheral (IP) 320.
[039] Voice network 104 may be implemented using the PSTN and SS7 as a signaling protocol. The SS7 protocol allows voice network 104 to provide features, such as call forwarding, caller-ID, three-way calling, wireless services such as roaming and mobile subscriber authentication, local number portability, and toll-free/toll services. The SS7 protocol provides various types of messages to support the features of voice network 104. For example, these SS7 messages may include Transaction Capabilities Applications Part ("TCAP") messages to support event "triggers," and queries and responses between ISCP 302 and SSPs 308 and 310.
[040] ISCP 302 may also be, for example, a standard service control point (SCP) or an Advanced Intelligent Network (AIN) SCP. ISCP 302 provides translation and routing services of SS7 messages to support the features of voice network 104, such as call forwarding. In addition, ISCP 302 may exchange information with the service center 106 using TCP/IP or SS7.
ISCP 302 may be implemented using a combination of known hardware and software. Although ISCP 302 is shown with a direct connection to service center 106 through ISCP SPACE 314, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP 302 and service center 106.
[041] STPs 304 and 306 relay SS7 messages within voice network 104. For example, STP 304 may route SS7 messages between SSPs 308 and 310. STP 302 may be implemented using known hardware and software from manufacturers such as NORTELT"" and LUCENT TechnologiesT"".
[042] SSPs 308 and 310 provide an interface between voice network 104 and phones 114 and 120, respectively, to setup, manage, and release telephone calls within voice network 104. SSPs 308 and 310 may be implemented as a voice switch, an SS7 switch, or a computer connected to a switch. SSPs 308 and 310 exchange SS7 signal units to support a telephone call between calling party 120 and user 110. For example, SSPs 308 and 310 may exchange SS7 messages, such as TCAP messages, within message signal units ("MSU") to control calls, perform database queries to configuration database 312, and provide maintenance information.
[043] Line Information Database (LIDB) 312 comprises one or more known databases to support the features of voice network 104. For example, LIDB 312 may include subscriber information, such as a service profile, name and address, and credit card validation information.
[044] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of ISCP 302 or be separate from ISCP 302. For example, the TelcordiaT"' ISCP may include an environment similar to SPACE
314 as part of the product. Further, ISCP SPACE 314 may include one or more servers. ISCP SPACE 314 is the point in the ISCP platform where customer record updates may be made.
[045] In one embodiment, customer records may be stored in ISCP
SPACE 314 such that the records may be updated and sent to ISCP 302.
These records may include information regarding how to handle calls directed to the customer. For example, these customer records may include information regarding whether or not calls for the customer are to be forwarded to a different number, andlor whether or not the call should be directed to an IP, such as a voice mail system, after a certain number of rings.
Additionally, one ISCP SPACE 314 may provide updates to one or more ISCPs 302 via an ISCP network (not shown).
[046] Additionally, voice network 104 may include one or more recent change engines 316 such as, for example, an Enterprise Recent Change engine (eRC); an Assignment, Activation, and Inventory System (AAIS); or a multi-services platform (MSP). As an example, the eRC and AAIS may be used in voice networks 104 located in the western part of the United States, while an MSP may be used in networks in the eastern part. The recent change engines may be used to update switch and ISCP databases. For example, a recent change engine may deliver database updates to SSPs and to ISCPs, such that when updating databases, these recent change engines emulate human operators. Additionally, if the instructions are to be sent to an ISCP 302, the recent change engine may first send the instructions to ISCP
SPACE 314, which then propagates the instructions to ISCP 302 as discussed above. Further, an MSP may be used, for example, for providing updates to both SSPs 308 or 310 and ISCPs 302. Or, for example, an eRC
may be used for providing updates to SSPs 308 or 310, while an AAIS is used for providing updates to ISCPs 302.
[047] Additionally, voice network 104 may include one or more intelligent peripherals (IP). For example, in Fig. 4, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing services, such as voice mail services.
[048] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention. As shown, service center 106 may include firewalls 402 and 404, one or more digital companion servers 406, one or more communication portal servers 408, one or more network access servers 410, and a voice portal 412. Voice portal 412 may include a voice portal application server 414 and a voice recognition server 416. A network 418 may be used to interconnect the firewalls and servers. Additionally, back end servers) 420 may be provided between service center 106 and voice network 104.
[049] Firewalls 402 and 404 provide security services for communications between service center 106, data network 102, and voice network 104, respectively. For example, firewalls 402 and 404 may restrict communications between user terminal 112 and one or more servers within service center 106. Any security policy may be implemented in firewalls 402 and 404 consistent with the principles of the present invention. Firewalls 402 and 404 may be implemented using a combination of known hardware and software, such as the Raptor Firewall provided by the Axent Corporation.
Further, firewalls 402 and 404 may be implemented as separate machines within service center 106, or implemented on one or more machines external to service center 106.
[050] Network 418 may be any type of network, such as an Ethernet or FDDI network. Additionally, network 418 may also include switches and routers as appropriate without departing from the scope of the invention.
Further, additional firewalls may be present in network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[051] Each server (406, 408, 410, 414, 416, 420) may be any type of server or computer, such as a Unix or DOS based server or computer. The servers may implement various logical functions, such as those described below. In Fig. 4, a different server is illustrated as being used for each logical function. In other embodiments, the logical functions may be split across multiple servers, multiple servers may be used to implement a single function, all functions may be performed by a single server, etc.
[052] In general, a digital companion server 406 may provide the software and hardware for providing specific services of the service center.
Exemplary services include, for example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, digital companion server 406 may facilitate acquisition of contact information associated with a caller upon receipt of the caller's telephone number (i.e., a Calling Party Number).
[053] A communication portal server 408 may provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. Network access servers 410 may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may be used for transmitting and/or receiving information from/to an ISCP 302 or an SSP 308 or 310 of voice network 104.
[054] Voice portal 412 includes software and hardware for receiving and processing instructions from a customer via voice. For example, a customer may dial a specific number for voice portal 412. Then the customer using speech may instruct service center 106 to modify the services to which the customer subscribes. Voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. Voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. Application function 414 may take, for example, the output from voice recognition function 416, convert it to a format suitable for service center 106 and forward the information to one or more servers (406, 408, 410) in service center 106.
[055] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention. As illustrated, the logical architecture may be split into four planes: client side plane 502, application service plane 504, network access plane 506, and the voice network plane 508.
[056] Client side plane 502 includes the user terminals 112 A and 112_B that a user may use to send and/or receive information to/from the service center 106. Additionally, client side 502 includes the user's phones) 114. As discussed above, user terminals 112 may be any type of device a user may use for communicating with Service Center 106. For example, user terminal 112 A may be a PDA running a program for communicating with Service Center 106, while user terminal 112_B may be a desktop type computer running a web browser for communicating with Service Center 106 via the Internet. Additionally, the user may have one or more phones 114, such as, for example, one or more standard landline telephones and/or wireless phones.
[057] Application service plane 504 includes digital companion servers) 406, communication portal servers) 408, and voice portal 412.
These entities may communicate between one another using, for example, web services or any other suitable protocols. Web services are a standardized way of integrating Web-based applications using the Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) open standards over an Internet protocol (IP) backbone.
[058] As illustrated, a digital companion server 406 may provide the following functions: a client proxy 512, a web server 514, an application server function 516, a calendar server function 518, a notification server function 520, and a database function 522. Each of these functions may be performed in hardware, software, and/or firmware. Further, these functions may each be executed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[059] Client proxy function 512 provides a proxy function for the digital companion that may be used for security purposes. This client proxy function 512 may be included in a separate server such that all communications sent from the other digital companion functions/servers to a user terminal 112 via data network 102 go through client proxy 512. Also, if client proxy 512 is included on a separate server, for example, an additional firewall may be provided between client proxy 512 and the other digital companion servers to provide additional security.
[060] Web server 514 provides functionality for receiving traffic over data network 102 from a customer. For example, web server 514 may be a standard web server that a customer may access using a web browser program, such as Internet Explorer or Netscape Communicator.
[061] Application server function 516 encompasses the general functions performed by digital companion servers) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific applications provided by the service center.
These services may include, for example, interfacing with other function(s), software, and/or hardware to provide a customer with the capability of managing their calls online. For example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, application server function 516 may facilitate obtaining contact information associated with a Calling Party Number (CPN) when the customer receives an incoming call from the CPN.
[062] Additionally, application server function 516 may interface with one or more external devices, such as an external web server, for retrieving or sending information. For example, application server function 516 may interface with a voice network's data center 556 (e.g., verizon.com) to determine the services to which the customer subscribes (e.g., call waiting, call forwarding, voice mail, etc.).
[063] Calendar server function 518 may provide the capability of scheduling events, logging when certain events occurred, triggering the application-functions to perform a function at a particular time, etc.
[064] Notification server function 520 provides the capability to send information from service center 106 to a user terminal 112. For example, notification server function 520 at the direction of application server function 516 may send a notification to user terminal 112 that the user is presently receiving a phone call at user's phone 114.
[065] Database function 522 provides the storage of information useable by the various applications executed by the digital companion servers. These databases may be included in, for example, one or more external storage devices connected to the digital companion servers.
Alternatively, the databases may be included in storage devices within the digital companion servers themselves. The storage devices providing database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[066] As discussed above, communication portal servers) 408 provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. As illustrated in Fig. 5, a communication portal server 408 may provide the following functions: a web server function 526, an application server function 528, a contacts database function 530, and/or a customer profile function 532. Each of these functions may be performed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[067] Web server function 526, as with web server function 522 of the digital companion servers, provides functionality for receiving traffic over data network 102 from a customer. For example, the web server may be a standard web server that a customer may access using a web browser, such as Internet Explorer or Netscape Communicator.
[068] Application server function 528 encompasses the general functions performed by communication portal servers 408. For example, these functions may include interfacing with the voice network to retrieve and/or modify customer profile information, and creating and editing an address book for the user. Additionally, application server function 528 may include the functionality of sending and/or receiving information to/from external servers and/or devices. For example, communication portal servers 408 may be connected to a network, such as, the Internet. Application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages webpage.
Application function 528 could then contact these external services 552 to retrieve information, such as an address for a person in the user's address book.
[069] In another example, application server function 528 of communication portal 408 may interface a single sign on (SSO) server 554.
SSO 554 may be used to allow users to access all services to which the user subscribes, on the basis of a single authentication that is performed when they initially access the network.
[070] Contacts database 530 includes storage devices for storing an address book for the user. This address book may be any type of address book. For example, the user's address book may, include the names, phone numbers, and addresses of people and/or organisations. These storage devices may be internal or external to communication portal servers 408 or some combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[071] Customer profile database 532 includes storage devices for storing customer profile information for the user. These storage devices may be the same or separate storage devices used for the contacts database.
The customer profile may include information regarding the user's account for their voice network. For example, this information may include the user's name, billing address, and other account information. Additionally, the customer profile may include information regarding voice services to which the user subscribes, such as, for example, call waiting, voice mail, etc.
[072] Additionally, application services plane 504 of the architecture may include a voice portal 412. As discussed above, voice portal 412 may include, for example, a voice recognition function 416 and an application server function 414, and be used for receiving and processing instructions from a customer via voice. The voice recognition function may be implemented using hardware and/or software capable of providing voice recognition capabilities. This hardware and/or software may be a commercially available product, such as the Voice Application platform available from Tellme Networks, Incorporated. Application server function 414 of voice portal 412 may include hardware and/or software for exchanging information between digital companion servers 406 and voice recognition function 416. Additionally, application server function 414 may be included on a separate server, included in the hardware and software providing voice recognition function 416, included in digital companion servers 406, etc.
[073] Network Access plane 506 of the architecture includes the functions for providing connectivity between application service plane 502 and voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[074] As discussed above, recent change engines 316 may be used to update switches and ISCP databases included in voice network 104. In one embodiment, recent change engines 316 may include an AAIS 544, an eRC 546, and/or an MSP 548. Additionally, a proxy 542 may be used between digital companion servers 406 and recent change engines 542 for security purposes.
[075] Network access servers 410 may be included in the service center 106 and may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may include a Caller ID (CID) functionality for retrieving caller ID
information from voice network 104, a click to dial (CTD) functionality for instructing an intelligent peripheral (IP) in the voice network to place a call via an SSP, and/or a real time call management (RTCM) functionality for interfacing with an ISCP of the voice network.
[076] Network Access,plane 506 may also include one or more back end servers) 420. These back end servers) 420 may include hardware and/or software for interfacing service center 106 and voice network 104.
Back end servers) 420 may be connected to service center 106 by a network, by a direct connection, or in any other suitable manner. Further, back end servers) 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner.
[077] Back end servers) 420 may include, for example, a server providing a voice mail retrieval and notification function. For example, this voice mail retrieval and notification function may include the capability to receive notifications when a user receives a voice mail, physically call a user's voice mail system, enter the appropriate codes to retrieve the voice mail, retrieve the voice mail, convert the voice mail to a digital file, and send it to digital companion servers 406.
[078] Additionally, back end servers) 420 may also include, for example, a directory assistance server. This directory assistance server may, for example, interface service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of voice network 104. A RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of voice network 104 for name and/or address information associated with a phone number and receiving the name and/or phone number in response to this request.
Additional details of the RDA gateway and DOC are described below in connection with Fig. 6.
[079] In another example, back end servers) 420 may include a wireless Internet gateway that is used for interfacing with a mobile switching center (MSC) of a wireless voice network. As with the above-described back end servers) 420, this wireless Internet gateway may be used for converting requests and information between the formats used by service center 106 and those used by the wireless voice network.
[080] In yet another example, back end servers) 420 may include a conference blasting server for instructing a conference bridge in voice network 104 to dial out via an SSP to the participants of a voice conference. Or for example, the back end servers) may include a server for instructing an IP of the voice network to place a call between two parties by dialing out to each of the parties. Back end servers) 420 may also include the capability to instruct the bridge or IP device to call an audio digitizing device that can listen to the conference, convert the audio signals to digital format, and forward the digitized signals to a user device via, for example, an audio streaming server.
The audio streaming server may, for example, allow a user to connect to it via, for example, the Internet. Additionally, the audio streaming device may buffer or record the signals to permit the user to pause, rewind, and/or fast-forward thru the conference.
[081] In yet another example, back end servers) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a SMS gateway in voice network 104. This may be used for example to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the users chosing.
[082] Voice network plane 508 includes the hardware and software included in voice network 104, as discussed above with reference to Fig. 3.
For example, voice network plane 508 may include ISCP SPACE 314, ISCP
302, intelligent peripherals 320, and SSP 308. Additionally, voice network plane 508 may also include the hardware and software included in a wireless carrier's network, such as, for example, the mobile switching center, etc.
[083] For clarity of explanation, system 100 is described herein with reference to the discrete functional elements illustrated in Figs. 1-5.
However, it should be understood that the functionality of these elements and modules may overlap and/or may exist in a fewer or greater number of elements and modules. Elements of system 100 may, depending on the implementation, lack certain illustrated components and/or contain, or be coupled to, additional or varying components not shown. Moreover, all or part of the functionality of the elements illustrated in Figs. 1-5 may co-exist or be distributed among several geographically dispersed locations.
[084] In certain embodiments, methods and systems consistent with present invention may perform a Reverse Directory Assistance (RDA) lookup.
As used herein, the term "RDA lookup" refers to obtaining contact-related information associated with a party by way of a telephone number or other identifier associated with that party. As used herein, the term "party"
encompasses any entity for which contact-related information may be retrieved, such as individuals, groups, businesses, retail establishments, service providers, etc. Consistent with embodiments of the present invention, contact-related information may include one or more of a name, home address, business address, home telephone number, business telephone number, cell phone number, instant messenger address, IP address, biometric information (e.g., fingerprints, voice prints, retinal scans, etc.) visual information (e.g., digital images, photographs, etc.), audio information, personal information (e.g., birth date, favorite movies, favorite songs, etc.), public records, credit reports, police records, driving records, banking statements, and contact-related information associated with relatives and/or friends. In certain embodiments, contact-related information may include information associated with, or retrieved via, one or more networks.
[085] Although a telephone number is used herein to explain principles and aspects of the present invention, the present invention contemplates the use of other identifiers to retrieve information associated with parties, such as e-mail addresses, fax numbers, Caller ID information, predetermined ID codes, network addresses, photographs, digital images, audio signals, video signals, etc. For example, a photo of an individual may be used to retrieve contact-related information associated with that individual.
[086] Consistent with principles of the present invention, an RDA
lookup may be triggered by a Calling Party Number (CPN). For example, upon user 110 receiving (via telephones 114, 116, etc.) a call from a caller (having an associated CPN), contact information may be obtained for the caller using the received CPN. Additionally or alternatively, an RDA lookup may used to obtain information associated with telephone numbers stored in a history (or call log) of incoming and/or outgoing calls. Further, a user could specify a telephone number for which to obtain contact information by for, example, inputting the number to user terminal 112. In one embodiment of the present invention, user 110 could initiate an RDA lookup. Also, one or more systems associated with user 110 (e.g., user terminal 112 and server 406) could automatically initiate an RDA lookup. Consistent with embodiments of the present invention, contact information may be obtained in order to add a party to a user's address book or contact list, which may, as mentioned above, be maintained by contacts database 530.
[087] Fig. 6 illustrates an environment 600 in which RDA processes consistent with embodiments of the present invention may be implemented.
As illustrated, environment 600 may include service center 106, data network 102, back end server 420, an RDA Gateway 610, an RDA proxy server 620, a directory network 630, a Data Operations Center (DOC) 640, and a listings lexicon 650.
[088] As mentioned above, back end server 420 may include hardware and/or software for interfacing service center 106 with voice network 104. In one example, back end server 420 may include or leverage one or more search engines. Back end server 420 may be connected to service center 106 via a network (e.g., corporate network 675), a direct connection, or in any other suitable manner. Further, back end server 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner. In environment 600, back end servers) 420 may include or be configured to operate as one or more RDA application server(s). As such, back end server 420 may interface service center 106 with RDA Gateway 610 of voice network 104.
[089] In certain embodiments, one or more firewalls (e.g., firewall 404) may be interposed between back end server 420 and one or more servers within service center 106 to provide security services. Such firewalls may be implemented external to service center 106, as illustrated in Fig. 6, and/or implemented within service center 106.
[090] RDA Gateway 610 may include one or more devices, components and/or processes (e.g., implemented in software, firmware, and/or hardware) configured to facilitate information exchange between back end server 420 and voice network 104. In certain configurations, RDA
Gateway 610 may perform routing functions, switching functions, code conversions, and/or protocol conversions. RDA Gateway 610 may, consistent with embodiments of the present invention, accept messages and requests from back end server 420, issue requests/queries for contact information, and provide information, which may include contact information, back to server 420. In one example, RDA Gateway 610 may accept HTTP messages from back end sever 420 and respond to server 420 using XML. Alternatively, the Standard Generalized Markup Language (SGML) and/or any other language that facilitates the creating and sharing of common information formats may be employed. In one embodiment, RDA Gateway 610 may send server 420 a Document Type Definition (DTD), which describes response format(s). In addition, or as alternative to a DTD, any other schema and/or means for validating a language (e.g., XML) may be employed for describing response formats. Additional details of responses are discussed below in connection with Figs. 7 and 8.
[091] As illustrated in Fig. 6, RDA Gateway 610 may be coupled to a directory network 630. Directory network 630 may, in certain implementations, be coupled to or included in voice network 104. Directory network 630 may include any combination of components and/or services configured to provide contact-related information. Directory network 630 may include, for example, Verizon'sT"" LiveSource National Directory Assistance network and/or any other directory and/or operator service network.
[092] In exemplary implementations, directory network 630 may include or be coupled to DOC 640. DOC 640 may include one or more devices, mechanisms, and/or services for maintaining, and/or processing requests for, contact-related information. In environment 600, DOC 640 may include or be coupled to a lexicon 650, which may be a compilation of contact-related information (e.g., listing information) associated with callers.
Lexicon 650 may, for example, be implemented via one or more databases, such as a relational database, a distributed database, and/or an object-oriented programming database. Information included in lexicon 650 may be obtained, maintained, and updated via one or more telephone companies (e.g., VerizonT""), listing house sources, andlor operator referrals. Listing information may include, but is not limited to, one or more of: a phone number, name, street, city, state, zip code, non published flag, and billing type (e.g., local or national).
[093] In certain embodiments, environment 600 may include RDA
proxy server 620, which may serve as an application level proxy server that allows known/trusted messages to pass between service center 106 and RDA
Gateway 610. RDA proxy server 620 may, for instance, log errors and attempts by other devices to gain access to the trusted network segment.
[094] Fig. 7 is a flowchart depicting exemplary stages in an RDA
lookup process consistent with embodiments of the present invention. The illustrated process may begin with an RDA lookup request (stage 710). In certain implementations, an RDA lookup request may be initiated by user 110 and/or a device associated with user 110 in response to a user action/input.
Initiating (or triggering) an RDA request may involve generating and/or transmitting, as well as causing the generation/transmission of, the request.
In one example, user terminal 112 may transmit, in response to instructions received by user 110, an RDA lookup request for a particular telephone number to digital companion server 406 in service center 106. User 110 may, in certain instances, trigger an RDA lookup for a CPN upon viewing a CPN
from a caller ID display. Further, a user could trigger an RDA lookup request by for, example, inputting a telephone number to, or selecting a telephone number from, user terminal 112. User 110 may, additionally or alternatively, trigger an RDA lookup by selecting a telephone number from a history of incoming and/or outgoing calls (i.e., a call log), which may be stored, for example, by one or more elements within service center 106 and accessible by user terminal 112. In certain embodiments of the present invention, user 110 may be prompted to initiate an RDA lookup request. For example, server 406 and/or user terminal 112 may prompt user .110 to initiate an RDA request when an outgoing or incoming call occurs or is logged. User 110 may, for instance, initiate an RDA request in order to add a contact to an address book or contact list (e.g., stored by contacts database 530).
[095] Consistent with embodiments of the present invention, an RDA
lookup request may be initiated (stage 710) by a device associated with user 110 automatically, without user action/input and with or without a user's knowledge. In one example, an RDA lookup request may be initiated (e.g., by user terminal 112 and/or server 406) when an incoming call is received by a calling device associated with user 110 (e.g., telephone 114). Additionally, an RDA request could be initiated automatically by user terminal 112 and/or service center 106 (via server 406) when a contact is being added to user 110's contact list. That is, obtaining contact information for a telephone number could be part of the process of adding a contact to the contact list.
Consistent with principles of the present invention, incoming and/or outgoing calls may be logged by one or more elements in service center 106 (e.g., server 406), and service center 106 may (e.g., via server 406) automatically initiate RDA requests for such numbers. Such requests may be automatically initiated to add contacts to a user's address book. In certain embodiments, RDA processes may be leverage to update or refresh a user's address book.
In such embodiments, RDA lookup requests may be initiated automatically and/or on demand in order to update a user's address book with current contact-related information. In one example, a user may input a command (e.g., via user terminal 112) that initiates one or more RDA lookup requests in order to refresh the address book. Additionally, or alternatively, RDA lookup requests may be periodically initiated, without user intervention, in order to refresh the address book.
[096] After an RDA lookup request is initiated, the request may be forwarded to back end server 420 (stage 720). In certain embodiments, the RDA lookup request may be transmitted from service center 106 (e.g., from server 406) to back end server 420. The RDA lookup request may also be routed through firewall 404. Upon receiving the request, back end server 420 may authenticate the request and transmit an RDA query to RDA Gateway 610 (stage 730). Authenticating the request may be optional.
[097] In certain embodiments, upon receiving the request (stage 720), back end server 420 may, in addition or as alternative to transmitting an RDA
query to RDA Gateway 610, leverage one or more search engines and/or network services (e.g., Google, Super Pages) to retrieve certain contact-related information. In one example, back end server 420 may leverage one or more search engines to retrieve certain contact-related information (e.g., public records from the Internet) and, in addition, transmit an RDA request for other information (e.g., listing information) to RDA Gateway 610. In other examples, back end server 420 may retrieve contact-related information, and RDA Gateway 610 may be unnecessary. In such cases where RDA Gateway 610 is not leveraged, stages 730-750 may not be performed in the process of Fia. 7.
[098] An RDA query transmitted from back end server 420 to RDA
Gateway 610 (stage 730) may, in one implementation, include the telephone number for which contact information is desired and an identifier associated with user 110 (customer ID). As explained above, the telephone number for which contact information is requested may be a telephone number received by user 110 (e.g., a calling party number), previously dialed by user 110 (e.g., from an outgoing call history or log), and/or specified/selected by user 110.
The customer ID may, for example, include user 110's primary telephone number. In certain embodiments of the present invention, the RDA query may be transmitted or routed from back end server 420 to RDA Gateway 610 through RDA proxy server 620. Back end server 420 may, in certain embodiments, transmit the RDA query to RDA Gateway 610 via HTTP. In one example, the RDA query may be in the form of a Universal Resource Locator (URL) having the following exemplary format:
http://RDAGateway/RDAQuery.aspx?customerlD=2129999999&IookuplD=21255512 In the above example URL, RDAGatevvay may be a name or IP address associated with RDA Gateway 610; customerlD may be the primary telephone of user 110; and IookuplD may be the telephone on which the query is performed.
[099] Upon receiving the RDA query, RDA Gateway 610 may forward the query to DOC 640 (stage 740). As described above, DOC 640 may include or be coupled to listing lexicon 650, which may be implemented via one or more database(s). Accordingly, RDA Gateway 610 may query the listing lexicon for contact information associated with the telephone number included in the query. Consistent with principles of the present invention, RDA Gateway 610 may expect a response from listing lexicon 650 as described in an Interface Protocol Specification provided by a database vendor. In response to the RDA query, DOC 640 may provide (e.g., to RDA
Gateway 610) listing information associated with the telephone number in the query. For example, a phone number, name, street, city, state, and/or zip code may be returned. Additionally or alternatively, one or more flags and/or errors may be returned. For example, if the particular party associated with the telephone number of interest has indicated that contact information is to remain private, a non-published flag may be returned from DOC 640. DOC
640 may also provide an indication of an internal processing error or timeout period expiration. Information provided by DOC 640 may also include a billing type (e.g., local or national) for user 110. Consistent with principles of the present invention, single listings and/or multiple listings may be provided by DOC 640 for a given telephone number. For example, families may list spouses and children separately and with the same number, and small business may list multiple parties with a particular number.
[0100] After sending the RDA query to DOC 640, RDA Gateway 610 may send a response to back end server 420 (stage 750). At this stage, RDA
Gateway 610 may also record the customer ID to facilitate billing. The response may, in one example, include (or reflect) information provided by and received from DOC 640. RDA Gate'viray 610 may, in one configuration, respond to back end server 420 via XML. RDA Gateway 610 may therefore convert/format information received from DOC 640 to an XML message and route the message to back end server 420. As mentioned above, RDA
Gateway 610 may send server 420 a Document Type Definition (DTD), which describes response format(s). RDA Gateway 610 may, in certain configurations, support one or more of the following response types: Single Listing, Multiple Listings, Non-Published Listings, No Listing, Invalid Phone Number, Service Not Available, Database Error, Query Timeout. Table 1 of Fig. 8 illustrates the above-mentioned responses and their corresponding conditions; Figs. 9A and 9B collaboratively illustrate XML format 900, which depicts an example XML format for each response.
[0101] Consistent with embodiments of the present invention, the response to back end server 420 may include contact-related information (e.g., listing information) associated with the telephone number of interest, which may be received from DOC 640. For example, the response from Gateway 610 to back end server 420 may include one or more of: a phone number, name, street, city, state, zip code. The response may also include network-related information, public records, family information, images, audio information, etc. In addition, the response may include (or reflect) one or more flags and/or errors, as discussed above.
[0102] In the illustrated process of Fig. 7, back end server 420 may forward RDA lookup results to one or more components in service center 106 (stage 760). For example, such results (e.g., listing information, flags, errors, etc. received from DOC 640 via RDA Gateway 610) may be transmitted to server 406. In addition, or as an alternative, contact-related information retrieved by back end server 420 using one or more search engines and/or network services may be transmitted to server 406. The process of Fig. 7 may then provide user 110 with access to the RDA lookup results (stage 770).
Access may, for example, be provided via server 406 and user terminal 112.
Providing access to RDA lookup results (stage 770) may involve presenting user 110 with listing information associated with the telephone number of interest. Providing access to RDA lookup results may also involve notifying user 110 that one or more errors occurred or that information is not available (e.g., not published) for the telephone number of interest.
[0103] After access is provided to user 110 (stage 770), user 110 may respond to the RDA lookup results (stage 780). In one example, where listing information is obtained, user 110 may select listing information (stage 780) to add to the contact list. For example, user 110 may input a command to user terminal 112 that causes the listing information to be inserted in the contact list. In certain embodiments, user terminal 112 may, in response to such a command, communicate with service center 106 (e.g., server 406), thereby causing the information to be added to the contact list. In some instances, as mentioned above, multiple listings for a number may be obtained and presented to the user. In such instances, user 110 may select one or more of the listings to add to the contact list. If errors have occurred or information is not available for a particular number, user 110 may initiate another RDA
lookup request for the same or different number. In alternative embodiments, user 110 may select listing information for other processing (e.g., by server 406). Responding to results (stage 780) may also involve responding to one or more error messages.
[0104] The steps illustrated in the flowchart of Fig. 7 are consistent with exemplary implementations of the instant invention. Further, it should be understood that the sequence of events described in Fig. 7 are exemplary and not intended to be limiting. Thus, other method steps may be used, and even with the method depicted in Fig. 7, the particular order of events may vary without departing from the scope of the present invention. Moreover, certain steps may not be present and additional steps may be implemented in Fig. 7.
In addition, it should be understood that the stages of Fig. 7 may be modified with departing from the scope of the present invention. For example, in certain implementation, information may be exchanged between DOC 640 and back end server 420 without the use of RDA Gateway 610.
[0105] Embodiments consistent with the invention may be implemented in various environments. Further, the processes described herein are not inherently related to any particular apparatus and may be implemented by any suitable combination of components. Moreover, various types of general purpose devices may be used in accordance with the teachings described herein.
[0106] The exemplary systems and methods consistent with present invention described above are illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0107] The present invention has been described in relation to particular examples which are intended in all respects to be illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0108] Additionally, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only. To this end, it is to be understood that inventive aspects lie in less than all features of a single foregoing disclosed embodiment, implementation, or configuration. Thus, the true scope and spirit of the invention depends on the following claims.
Claims (33)
1. A method for obtaining contact information comprising:
receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and performing a process using the retrieved contact-related information.
receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and performing a process using the retrieved contact-related information.
2. The method of claim 1, wherein receiving a request including identifying information comprises receiving a request including one of a name, a telephone number, and a network identifier.
3. The method of claim 1, wherein receiving a request including identifying information comprises receiving a request including an e-mail address.
4. The method of claim 1, wherein receiving a request including identifying information comprises receiving a request including one of an audio signal, a video signal, a photograph, and a digital image.
5. The method of claim 1, wherein retrieving the contact-related information associated with the party comprises retrieving one or more of a home address, a business address, a digital image, an audio signal, a public record, and information associated with relatives of the party.
6. The method of claim 1, wherein retrieving the contact-related information comprises retrieving the contact-related information using a search engine.
7. The method of claim 1, wherein retrieving the contact-related information comprises retrieving the contact-related information using an operator network.
3. The method of claim 1, wherein performing a process comprises adding the contact-related information to an address book.
9. The method of claim 8, wherein adding the contact-related information to the address book is performed without user intervention.
10. A method for obtaining contact information, the method comprising:
receiving, by a service center, a request initiated by a user for contact information associated with a telephone number;
querying, by the service center and in response to the request, a directory means for the contact information;
receiving the contact information at the service center; and storing, via the service center, the contact information in a contact list associated with a user.
receiving, by a service center, a request initiated by a user for contact information associated with a telephone number;
querying, by the service center and in response to the request, a directory means for the contact information;
receiving the contact information at the service center; and storing, via the service center, the contact information in a contact list associated with a user.
11. The method of claim 10, wherein the telephone number for which contact information is requested includes a telephone number associated with a call received by the user.
12. The method of claim 10, wherein the telephone number for which contact information is requested includes a telephone number previously dialed by the user.
13. The method of claim 10, wherein the telephone number for which contact information is requested is specified by the user.
14. The method of claim 10 further comprising:
providing the user with access to the contact information.
providing the user with access to the contact information.
15. In a system having a user terminal, a service center, and a server, a method for obtaining contact information, the method comprising:
receiving, by the service center, a request from the user terminal for contact information associated with a telephone number;
forwarding the request from the service center to the server;
transmitting, in response to the request, a query including the telephone number from the server through a gateway to a directory means;
receiving the contact information by the server via the gateway;
forwarding the contact information from the server to the service center; and providing a user with access to the contact information.
receiving, by the service center, a request from the user terminal for contact information associated with a telephone number;
forwarding the request from the service center to the server;
transmitting, in response to the request, a query including the telephone number from the server through a gateway to a directory means;
receiving the contact information by the server via the gateway;
forwarding the contact information from the server to the service center; and providing a user with access to the contact information.
16. The method of claim 15, wherein transmitting a query including the telephone number from the server includes transmitting a query including the telephone and an identifier associated with a user of the user terminal.
17. The method of claim 15, wherein receiving the contact information by the server includes receiving the contact information from storage means associated with the directory means.
18. The method of claim 15, wherein receiving the contact information by the server includes receiving at least one of a name, a street, a city, a state, a zip code, a facsimile number, and an e-mail address associated with the telephone number.
19. The method of claim 15, wherein providing access to the contact information includes providing the user with access to the contact information via the user terminal.
20. The method of claim 15 further comprising:
storing the contact information in a contact list maintained by the service center.
storing the contact information in a contact list maintained by the service center.
21. A communications system comprising:
a user device, coupled to a network, configured to transmit a request for contact information associated with a telephone number;
a service center associated with the user device configured to receive the request for contact information from the network; and a first server, coupled to the service center, configured to:
query, in response to the request and using the telephone number, a directory means via a gateway to obtain the contact information, receive a response to the query from the directory means via the gateway; and forward the response received from the directory means to the service center.
a user device, coupled to a network, configured to transmit a request for contact information associated with a telephone number;
a service center associated with the user device configured to receive the request for contact information from the network; and a first server, coupled to the service center, configured to:
query, in response to the request and using the telephone number, a directory means via a gateway to obtain the contact information, receive a response to the query from the directory means via the gateway; and forward the response received from the directory means to the service center.
22. The system of claim 21, wherein the directory means is a directory assistance service maintained by at least one service provider.
23. The system of claim 21, wherein the directory means includes a storage device for maintaining the contact information.
24. The system of claim 21, wherein the user device is one of a general purpose computer, a personal computer, a Blackberry.TM. device, a Ergo Audrey.TM. device, a wireless device, and a Personal Digital Assistant.
25. The system of claim 21, wherein the service center includes a second server coupled to the network for receiving the request for contact information.
26. The system of claim 21, wherein the response received by the first server from the directory means and forwarded to the service center includes listing information, which includes at least one of a name, a street, a city, a state, a zip code, a facsimile number, and an e-mail address.
27. The system of claim 26, wherein the service center provides a user with access to the listing information via the network.
28. The system of claim 26, wherein the service center stores the listing information in a contact list associated with a user.
29. The system of claim 21, wherein the response received by the first server from the directory means and forwarded to the service center indicates that information associated with the telephone number is not available to the public.
30. The system of claim 21, wherein the response received by the first server from the directory means and forwarded to the service center indicates a billing type associated with the telephone number.
31. The system of claim 21, wherein the response received by the first server from the directory means and forwarded to the service center includes at least one error message.
32. A system for obtaining contact information comprising:
receiving means for receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving means for retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and processing means for performing a process using the retrieved contact-related information.
receiving means for receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving means for retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and processing means for performing a process using the retrieved contact-related information.
33. A computer-readable medium containing instructions for controlling a system to perform a method, the system including at least one processor for executing the instructions, the method comprising:
receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and performing a process using the retrieved contact-related information.
receiving a request for contact-related information associated with a party, the request including identifying information associated with the party;
retrieving the contact-related information associated with the party using the identifying information, the contact-related information being different from the identifying information; and performing a process using the retrieved contact-related information.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US42870402P | 2002-11-25 | 2002-11-25 | |
US60/428,704 | 2002-11-25 | ||
US43601802P | 2002-12-26 | 2002-12-26 | |
US60/436,018 | 2002-12-26 | ||
PCT/US2003/037699 WO2004049130A2 (en) | 2002-11-25 | 2003-11-25 | Methods and systems for directory information lookup |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2507083A1 true CA2507083A1 (en) | 2004-06-10 |
Family
ID=36889255
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002507083A Abandoned CA2507083A1 (en) | 2002-11-25 | 2003-11-25 | Methods and systems for directory information lookup |
Country Status (6)
Country | Link |
---|---|
US (1) | US8472606B2 (en) |
EP (1) | EP1570359A4 (en) |
JP (1) | JP2006507770A (en) |
AU (1) | AU2003293055A1 (en) |
CA (1) | CA2507083A1 (en) |
WO (1) | WO2004049130A2 (en) |
Families Citing this family (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7596218B2 (en) * | 2002-06-03 | 2009-09-29 | Local.Com Corporation | Enhanced directory assistance services in a telecommunications network |
US20050250483A1 (en) * | 2004-05-07 | 2005-11-10 | Malik Dale W | Caller look-up system |
US20050249172A1 (en) * | 2004-05-07 | 2005-11-10 | Malik Dale W | System to provide direction information to mobile communication devices |
US7792267B2 (en) * | 2004-05-25 | 2010-09-07 | International Business Machines Corporation | Automatic call completion in a directory assistance system |
US8606875B1 (en) * | 2004-06-30 | 2013-12-10 | Oracle America, Inc. | Method and system for automatic distribution and installation of a client certificate in a secure manner |
US9552599B1 (en) | 2004-09-10 | 2017-01-24 | Deem, Inc. | Platform for multi-service procurement |
GB0502844D0 (en) | 2005-02-11 | 2005-03-16 | Univ Edinburgh | Storing digital content for access using a captured image |
US7885397B2 (en) * | 2005-04-25 | 2011-02-08 | International Business Machines Corporation | On-demand seamless phone number updates |
EP1734465A1 (en) * | 2005-06-15 | 2006-12-20 | Chao-Hung WU | Method and system for the management of an address book of an electronic mailbox |
US20070008987A1 (en) * | 2005-07-06 | 2007-01-11 | Microsoft Corporation | Capturing contacts via people near me |
US7440445B1 (en) * | 2005-10-24 | 2008-10-21 | At&T Corp. | Method and apparatus for storing and activating universal resource locators and phone numbers |
US9117223B1 (en) | 2005-12-28 | 2015-08-25 | Deem, Inc. | Method and system for resource planning for service provider |
US7783575B2 (en) * | 2006-02-13 | 2010-08-24 | Rmg Networks, Inc. | Method and apparatus for connecting a network of electronic signs |
US8086488B2 (en) | 2006-02-13 | 2011-12-27 | Rmg Networks, Inc. | Method and apparatus for defining, distributing, and redeeming SMS and MMS coupons |
US8738639B1 (en) * | 2006-02-23 | 2014-05-27 | Verizon Data Services Llc | Methods and systems for an information directory providing audiovisual content |
EP1999645A4 (en) * | 2006-03-01 | 2010-07-07 | Wideport Com Inc 411 Ca | System and method for information retrieval |
WO2007101878A1 (en) * | 2006-03-08 | 2007-09-13 | Siemens Home And Office Communication Devices Gmbh & Co. Kg | Method and telephone for use of telephone book data stored in a telephone book data bank in a server |
US8086842B2 (en) | 2006-04-21 | 2011-12-27 | Microsoft Corporation | Peer-to-peer contact exchange |
US7869825B2 (en) | 2006-05-01 | 2011-01-11 | Mcgary Faith | Communication assistance system and method |
CN101496385A (en) * | 2006-05-24 | 2009-07-29 | 格莱珀技术集团公司 | Communication assistance system and method |
GB2440574A (en) * | 2006-08-04 | 2008-02-06 | New Voice Media Ltd | Computer telephony integration with search engine |
US9094515B2 (en) * | 2006-08-04 | 2015-07-28 | Newvoicemedia Limited | Method and apparatus for using a search engine advantageously within a contact center system |
US8335306B1 (en) * | 2006-10-03 | 2012-12-18 | Sprint Communications Company L.P. | Customer controlled hotline |
US8483381B2 (en) * | 2006-10-27 | 2013-07-09 | At&T Intellectual Property I, L.P. | Methods and apparatus to provide contact management with directory assistance |
US7831141B2 (en) | 2007-03-29 | 2010-11-09 | Sony Ericsson Mobile Communications Ab | Mobile device with integrated photograph management system |
US9075808B2 (en) | 2007-03-29 | 2015-07-07 | Sony Corporation | Digital photograph content information service |
JP2009003705A (en) * | 2007-06-21 | 2009-01-08 | Oki Data Corp | Communication terminal apparatus |
US20100197276A1 (en) * | 2007-08-14 | 2010-08-05 | Nec Corporation | Method of registering a telephone directory in a mobile phone and the mobile phone |
US8107930B1 (en) | 2007-08-21 | 2012-01-31 | Sprint Communications Company L.P. | Method and system for initiating a communication session |
US8185087B2 (en) | 2007-09-17 | 2012-05-22 | Telecommunication Systems, Inc. | Emergency 911 data messaging |
US8811585B1 (en) * | 2007-10-23 | 2014-08-19 | Sprint Communications Company L.P. | Communication routing plans that are based on communication device contact lists |
US9241063B2 (en) | 2007-11-01 | 2016-01-19 | Google Inc. | Methods for responding to an email message by call from a mobile device |
US8726165B1 (en) * | 2007-11-01 | 2014-05-13 | Google Inc. | Methods for auto-completing contact entry on mobile devices |
US9042526B2 (en) * | 2007-11-23 | 2015-05-26 | Bce Inc. | Method and apparatus for enabling a calling party to leave a voice message for a called party in response to a command provided by the calling party |
US9430538B2 (en) * | 2008-02-29 | 2016-08-30 | Red Hat, Inc. | Providing additional information and data in cooperation with a communication application |
KR101232110B1 (en) * | 2008-10-31 | 2013-02-12 | 에스케이플래닛 주식회사 | System and Method for Managing and Appling History Information of Terminal in Converged Personal Network Service Environment, and Converged Personal Network Service Server, Mobile Communication and End Device therefor |
US8676755B2 (en) | 2008-12-16 | 2014-03-18 | Microsoft Corporation | Contact entry population from call entity information |
EP2222062B1 (en) * | 2009-02-06 | 2017-05-10 | BlackBerry Limited | A mobile device with enhanced contact information and a method of using same |
US8135391B2 (en) | 2009-02-06 | 2012-03-13 | Research In Motion Limited | Mobile device with enhanced telephone call information and a method of using same |
US20100267367A1 (en) * | 2009-04-17 | 2010-10-21 | Sony Corporation | Methods and apparatus for automatic contact data updating |
US10552849B2 (en) | 2009-04-30 | 2020-02-04 | Deem, Inc. | System and method for offering, tracking and promoting loyalty rewards |
US8473472B2 (en) * | 2009-12-15 | 2013-06-25 | At & T Intellectual Property I, L.P. | Footprint tracking of contacts |
JP5754906B2 (en) * | 2010-09-27 | 2015-07-29 | キヤノン株式会社 | Image processing apparatus, control method thereof, and program |
US20120169459A1 (en) * | 2011-01-03 | 2012-07-05 | Relay Holdings, Llc | System and method for passively acquiring existing customers' mobile phone numbers from customer service logs |
US9449288B2 (en) | 2011-05-20 | 2016-09-20 | Deem, Inc. | Travel services search |
US9219822B2 (en) | 2011-09-09 | 2015-12-22 | Blackberry Limited | System and method for updating a contact list |
US20140185609A1 (en) * | 2012-12-28 | 2014-07-03 | Vonage Network, Llc | Systems and methods for providing information in a contact list |
US10521480B2 (en) | 2013-05-07 | 2019-12-31 | International Business Machines Corporation | Informative communication history |
US9667770B2 (en) | 2013-07-17 | 2017-05-30 | Flypsi, Inc. | Telephone network system and method |
CN104424336B (en) * | 2013-09-11 | 2018-11-09 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
ES2819203T3 (en) * | 2014-09-25 | 2021-04-15 | Fraunhofer Ges Forschung | Improved machine translation of caller ID |
JP2018516108A (en) * | 2015-04-08 | 2018-06-21 | リー,ジョセフ,ヨサップ | Game random number generation and audit system and method |
WO2018032100A1 (en) * | 2016-08-15 | 2018-02-22 | Gripevine Inc. | Complaint resolution system |
US11589203B2 (en) * | 2017-06-23 | 2023-02-21 | Collateral Opportunities, Llc | Method and system for requesting and sharing information between mobile devices and phone systems |
Family Cites Families (411)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE2443253A1 (en) * | 1974-09-10 | 1976-03-18 | Telstop S A | SYSTEM FOR MONITORING NUMBERS DIALED OVER A TELEPHONE LINE |
US4540850A (en) | 1983-04-29 | 1985-09-10 | At&T Bell Laboratories | Method and apparatus for controlling a conference |
US4600814A (en) | 1983-10-05 | 1986-07-15 | Manufacturing Administrations Management Systems, Inc. | Automated system for establishing telephone voice connections |
US5588037A (en) | 1984-09-14 | 1996-12-24 | Accessline Technologies, Inc. | Remote access telephone control system |
US5375161A (en) | 1984-09-14 | 1994-12-20 | Accessline Technologies, Inc. | Telephone control system with branch routing |
US5752191A (en) * | 1984-09-14 | 1998-05-12 | Accessline Technologies, Inc. | Telephone control system which connects a caller with a subscriber AT A telephone address |
US4734931A (en) * | 1986-03-21 | 1988-03-29 | American Telephone And Telegraph Company And At&T Information Systems Inc. | Integrated calling directory |
US5008926A (en) | 1986-07-17 | 1991-04-16 | Efrat Future Technology Ltd. | Message management system |
US5644727A (en) | 1987-04-15 | 1997-07-01 | Proprietary Financial Products, Inc. | System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing |
US4924496A (en) * | 1988-05-12 | 1990-05-08 | Romek Figa D/B/A Abraham & Sons | Automatic incoming telephone call originating number and party display system |
US5168515A (en) | 1989-11-27 | 1992-12-01 | Unifi Communications Corporation | Switchless automatic call distribution system |
US5274700A (en) | 1989-11-27 | 1993-12-28 | Unifi Communications Corporation | Methods of automatically rerouting an incoming telephone call placed over a network |
US5014303A (en) * | 1989-12-18 | 1991-05-07 | Bell Communications Research, Inc. | Operator services using speech processing |
JP3224384B2 (en) * | 1990-07-20 | 2001-10-29 | 富士通株式会社 | Call control method in intelligent network |
US5222125A (en) | 1991-09-03 | 1993-06-22 | At&T Bell Laboratories | System for providing personalized telephone calling features |
CA2076434C (en) * | 1991-10-09 | 1996-07-02 | Gary Joe Grimes | Incoming communications forwarding technique utilizing a called party location indicator |
US5329578A (en) | 1992-05-26 | 1994-07-12 | Northern Telecom Limited | Personal communication service with mobility manager |
US5982870A (en) | 1992-05-26 | 1999-11-09 | Bell Atlantic Network Services, Inc. | Method for concurrently establishing switch redirection for multiple lines of the public telephone network |
CA2100139C (en) * | 1992-09-29 | 1997-02-18 | William Walter Demlow | Information display provided to calling party |
US5440624A (en) | 1992-11-10 | 1995-08-08 | Netmedia, Inc. | Method and apparatus for providing adaptive administration and control of an electronic conference |
GB2272312A (en) | 1992-11-10 | 1994-05-11 | Ibm | Collaborative working in a network. |
US5327486A (en) | 1993-03-22 | 1994-07-05 | Bell Communications Research, Inc. | Method and system for managing telecommunications such as telephone calls |
US6717938B1 (en) * | 1999-04-15 | 2004-04-06 | J2 Global Communications, Inc. | System controlling use of a communication channel |
DE69402716T2 (en) | 1993-06-11 | 1997-12-11 | Northern Telecom Ltd | METHOD FOR SUPPLYING CALL MANAGEMENT SERVICES CONTROLLED BY THE USER |
US5533096A (en) | 1993-06-14 | 1996-07-02 | At&T Corp. | Send-all-calls feature for a wireless handset |
HU215619B (en) | 1993-06-15 | 1999-01-28 | Celltrace Communications Limited | Telecommunications system, further control modul for subscriber's units in telecommunications systems |
AU693462B2 (en) * | 1993-09-22 | 1998-07-02 | E-Talk Corporation | Method and system for automatically monitoring the performance quality of call center service representatives |
US5689641A (en) | 1993-10-01 | 1997-11-18 | Vicor, Inc. | Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signal |
US6594688B2 (en) * | 1993-10-01 | 2003-07-15 | Collaboration Properties, Inc. | Dedicated echo canceler for a workstation |
US5920847A (en) | 1993-11-01 | 1999-07-06 | Visa International Service Association | Electronic bill pay system |
US5535265A (en) | 1993-11-15 | 1996-07-09 | Ast Research, Inc. | Method and circuitry for controlling voice mail, call logging and call blocking functions using a modem |
JPH07219970A (en) | 1993-12-20 | 1995-08-18 | Xerox Corp | Method and apparatus for reproduction in acceleration format |
US5543343A (en) * | 1993-12-22 | 1996-08-06 | Sgs-Thomson Microelectronics, Inc. | Method fabricating an integrated circuit |
GB2285895A (en) | 1994-01-19 | 1995-07-26 | Ibm | Audio conferencing system which generates a set of minutes |
US5719925A (en) * | 1994-03-02 | 1998-02-17 | Peoples; John T. | Method for remotely controlling a telephone loop/channel from another telephone loop/channel |
US6628772B1 (en) * | 1994-04-28 | 2003-09-30 | Metro One Telecommunications, Inc. | Method for providing enhanced directory assistance upon command using out-of-band signaling |
CA2150060C (en) | 1994-07-08 | 2000-01-11 | John T. Biggs | Seamless multimedia conferencing system using enhanced endpoint devices |
US5483586A (en) | 1994-07-18 | 1996-01-09 | Sussman; Lester | Electronic on-line subscriber telephone directory |
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
US5652789A (en) | 1994-09-30 | 1997-07-29 | Wildfire Communications, Inc. | Network based knowledgeable assistant |
US6188756B1 (en) | 1994-10-11 | 2001-02-13 | Alexander Mashinsky | Efficient communication through networks |
US5715444A (en) | 1994-10-14 | 1998-02-03 | Danish; Mohamed Sherif | Method and system for executing a guided parametric search |
CA2159249C (en) * | 1994-11-21 | 1998-09-22 | Mark A. Fitser | Method for automatically establishing a conference call |
US5550907A (en) | 1994-12-23 | 1996-08-27 | Lucent Technologies Inc. | Personal communication using intelligent terminals |
KR0135777B1 (en) | 1995-01-25 | 1998-04-27 | 김광호 | Selecting calling phone |
DE69638018D1 (en) | 1995-02-13 | 2009-10-15 | Intertrust Tech Corp | Systems and procedures for managing secure transactions and protecting electronic rights |
US5623541A (en) * | 1995-02-17 | 1997-04-22 | Lucent Technologies Inc. | Apparatus to manipulate and examine the data structure that supports digit analysis in telecommunications call processing |
US5583564A (en) | 1995-04-24 | 1996-12-10 | Lucent Technologies Inc. | Intelligent call forwarding with videophone display of forwarding destination |
FI111893B (en) * | 1995-06-02 | 2003-09-30 | Nokia Corp | Procedure and apparatus for command control in a telephone |
GB2301987B (en) | 1995-06-05 | 2000-01-12 | Nokia Mobile Phones Ltd | Radio telephone text transmission system |
US5907324A (en) | 1995-06-07 | 1999-05-25 | Intel Corporation | Method for saving and accessing desktop conference characteristics with a persistent conference object |
US5710591A (en) | 1995-06-27 | 1998-01-20 | At&T | Method and apparatus for recording and indexing an audio and multimedia conference |
US5619555A (en) | 1995-07-28 | 1997-04-08 | Latitude Communications | Graphical computer interface for an audio conferencing system |
US5559875A (en) | 1995-07-31 | 1996-09-24 | Latitude Communications | Method and apparatus for recording and retrieval of audio conferences |
US5712903A (en) | 1995-08-21 | 1998-01-27 | Bell Atlantic Network Services, Inc. | Split intelligent peripheral for broadband and narrowband services |
US5638434A (en) | 1995-08-30 | 1997-06-10 | Mci Corporation | Conference system for dial-out telephone calls |
US5621787A (en) | 1995-09-13 | 1997-04-15 | Bell Atlantic Network Services, Inc. | Prepaid cash card |
US5717863A (en) | 1995-09-27 | 1998-02-10 | Intel Corporation | Method and apparatus for managing pc conference connection addresses |
US5751800A (en) * | 1995-12-15 | 1998-05-12 | Lucent Technologies Inc. | Screening of incoming telephone calls prior to call completion to the destination party |
US5764901A (en) | 1995-12-21 | 1998-06-09 | Intel Corporation | Record and playback in a data conference |
FI101661B1 (en) | 1996-01-08 | 1998-07-31 | Nokia Mobile Phones Ltd | Activate the phone's own answering machine according to the caller's number |
GB9603020D0 (en) | 1996-02-14 | 1996-04-10 | British Telecomm | Establishing communication |
US5805670A (en) | 1996-03-19 | 1998-09-08 | Life Safety Solutions, Inc. | Private notification system for communicating 9-1-1 information |
US6041103A (en) * | 1996-04-16 | 2000-03-21 | Lucent Technologies, Inc. | Interactive call identification |
US5918227A (en) * | 1996-05-06 | 1999-06-29 | Switchboard, Inc. | On-line directory service with a plurality of databases and processors |
US5745561A (en) * | 1996-05-31 | 1998-04-28 | Lucent Technologies Inc. | Multiple independent named call-coverage paths |
US5903845A (en) * | 1996-06-04 | 1999-05-11 | At&T Wireless Services Inc. | Personal information manager for updating a telecommunication subscriber profile |
JP3216992B2 (en) | 1996-06-14 | 2001-10-09 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Connection method in network system and server machine |
US5875242A (en) * | 1996-07-26 | 1999-02-23 | Glaser; Lawrence F. | Telecommunications installation and management system and method |
US6005870A (en) | 1996-08-12 | 1999-12-21 | At&T Corp. | Method for called party control of telecommunications network services |
US5747970A (en) * | 1996-09-24 | 1998-05-05 | Motorola, Inc. | Battery charger charging time control |
CA2266921A1 (en) | 1996-09-25 | 1998-04-02 | Andrew David Mercer | Network-based conference system |
US5724412A (en) * | 1996-10-07 | 1998-03-03 | U S West, Inc. | Method and system for displaying internet identification on customer premises equipment |
AU745141B2 (en) | 1996-10-09 | 2002-03-14 | Visa International Service Association | Electronic statement presentment system |
US5745884A (en) * | 1996-10-21 | 1998-04-28 | Mobile Area Networks, Inc. | System and method for billing data grade network use on a per connection basis |
US6243398B1 (en) | 1996-10-21 | 2001-06-05 | Vocaltec Communications Ltd. | System and method for personal multimedia communication over a packet switched network |
US5907547A (en) * | 1996-10-24 | 1999-05-25 | At&T Corp | System and method for establishing internet communications links |
US5944769A (en) | 1996-11-08 | 1999-08-31 | Zip2 Corporation | Interactive network directory service with integrated maps and directions |
US5872841A (en) * | 1996-11-14 | 1999-02-16 | Siemens Information And Comunication Newtworks, Inc. | Apparatus and method for scheduling a telephone call |
FI103845B (en) | 1996-11-14 | 1999-09-30 | Nokia Telecommunications Oy | Establishing calls using an intelligent network |
US5917817A (en) * | 1996-12-06 | 1999-06-29 | International Business Machines Corporation | User invocation of services in public switched telephone network via parallel data networks |
DE69603971T2 (en) | 1996-12-13 | 2000-03-30 | Ericsson Telefon Ab L M | Method and system for carrying out monetary transactions |
US6408191B1 (en) | 1996-12-31 | 2002-06-18 | Lucent Technologies Inc. | Arrangement for displaying message screens on a telephone terminal |
US6477374B1 (en) | 1997-01-03 | 2002-11-05 | Siemens Information And Communication Networks, Inc. | Apparatus and method for calendar based call routing |
JPH10240656A (en) | 1997-02-25 | 1998-09-11 | Fujitsu Ltd | Incoming call control system |
US6563914B2 (en) * | 1997-02-26 | 2003-05-13 | Call Sciences Limited | Personal web-based teleconferencing method and system |
US6775371B2 (en) * | 1997-03-13 | 2004-08-10 | Metro One Telecommunications, Inc. | Technique for effectively providing concierge-like services in a directory assistance system |
US6134318A (en) | 1997-03-19 | 2000-10-17 | At&T Corp | System and method for telemarketing through a hypertext network |
US6546005B1 (en) * | 1997-03-25 | 2003-04-08 | At&T Corp. | Active user registry |
US5945989A (en) | 1997-03-25 | 1999-08-31 | Premiere Communications, Inc. | Method and apparatus for adding and altering content on websites |
US6167119A (en) | 1997-03-28 | 2000-12-26 | Bell Atlantic Network Services, Inc. | Providing enhanced services through SIV and personal dial tone |
US6192123B1 (en) * | 1997-04-14 | 2001-02-20 | National Tech Team Inc. | Method and apparatus for initiating telephone calls using a data network |
US6333973B1 (en) | 1997-04-23 | 2001-12-25 | Nortel Networks Limited | Integrated message center |
US6282522B1 (en) | 1997-04-30 | 2001-08-28 | Visa International Service Association | Internet payment system using smart card |
US6480890B1 (en) | 1997-05-30 | 2002-11-12 | Alcatel Usa Sourcing, L.P. | World Wide Web interface to telecom service creation environment |
US6189026B1 (en) | 1997-06-16 | 2001-02-13 | Digital Equipment Corporation | Technique for dynamically generating an address book in a distributed electronic mail system |
JP3782867B2 (en) | 1997-06-25 | 2006-06-07 | 株式会社日立製作所 | Information reception processing method and computer / telephony integration system |
CA2240878A1 (en) | 1997-06-27 | 1998-12-27 | Vikram R. Saksena | Internet based ip multicast conferencing and reservation system |
US6058415A (en) | 1997-07-24 | 2000-05-02 | Intervoice Limited Partnership | System and method for integration of communication systems with computer-based information systems |
US6219413B1 (en) * | 1997-08-07 | 2001-04-17 | At&T Corp. | Apparatus and method for called-party telephone messaging while interconnected to a data network |
US6567671B2 (en) | 1997-08-11 | 2003-05-20 | At&T Wireless Services, Inc. | Wireless communication device with call screening |
US6931116B1 (en) | 1997-09-08 | 2005-08-16 | Mci Communications Corporation | Multiple routing options in a telecommunications service platform |
US6792084B1 (en) | 1997-09-08 | 2004-09-14 | Mci, Inc. | Single telephone number access to multiple communications services |
US6373836B1 (en) | 1997-09-15 | 2002-04-16 | Genesys Telecommunications Laboratories, Inc. | Apparatus and methods in routing internet protocol network telephony calls in a centrally-managed call center system |
US6377993B1 (en) | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US6535596B1 (en) * | 1997-09-29 | 2003-03-18 | Lucent Technologies Inc. | Call processing system utilizing subscriber services and preferences |
US6018571A (en) * | 1997-09-30 | 2000-01-25 | Mitel Corporation | System for interactive control of a computer and telephone |
US5960342A (en) | 1997-10-02 | 1999-09-28 | Samsung Telecommunications America, Inc. | Eliminated DTMF signaling in an integrated wireline-wireless system |
US5995595A (en) | 1997-10-14 | 1999-11-30 | Ameritech Corporation | Method of sharing and transferring information between ISDN telephones |
US6269369B1 (en) | 1997-11-02 | 2001-07-31 | Amazon.Com Holdings, Inc. | Networked personal contact manager |
US6310944B1 (en) * | 1997-12-17 | 2001-10-30 | Nortel Networks Limited | Method for adding context to communications |
US6018737A (en) * | 1997-12-18 | 2000-01-25 | Alcatel Usa Sourcing, L.P. | Universal personal telecommunications service for an advanced intelligent network |
US6122348A (en) | 1997-12-22 | 2000-09-19 | Nortel Networks Corporation | System and method for managing incoming communication events using multiple media options |
US6061432A (en) * | 1997-12-23 | 2000-05-09 | Bell Atlantic Network Services, Inc. | Voice mail system for obtaining routing information from signaling nodes |
US6215863B1 (en) | 1997-12-29 | 2001-04-10 | Ameritech Corporation | Method and apparatus for providing a station set with advanced telecommunications services |
US6480830B1 (en) | 1998-01-29 | 2002-11-12 | International Business Machines Corporation | Active calendar system |
US6442245B1 (en) | 1998-02-02 | 2002-08-27 | Unisys Corporation | System and method for providing voice messaging services utilizing a network connection |
US6856974B1 (en) | 1998-02-02 | 2005-02-15 | Checkfree Corporation | Electronic bill presentment technique with enhanced biller control |
US6298129B1 (en) | 1998-03-11 | 2001-10-02 | Mci Communications Corporation | Teleconference recording and playback system and associated method |
US6498841B2 (en) | 1998-03-19 | 2002-12-24 | Ameritech Corporation | Method and system for providing enhanced call waiting and caller identification |
US6519326B1 (en) * | 1998-05-06 | 2003-02-11 | At&T Corp. | Telephone voice-ringing using a transmitted voice announcement |
EP0957644A1 (en) * | 1998-05-13 | 1999-11-17 | BRITISH TELECOMMUNICATIONS public limited company | A billing system |
US6163692A (en) | 1998-05-28 | 2000-12-19 | Lucent Technologies, Inc. | Telecommunication network with mobile voice conferencing system and method |
US6219694B1 (en) | 1998-05-29 | 2001-04-17 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device having a shared electronic address |
US7209955B1 (en) * | 1998-05-29 | 2007-04-24 | Research In Motion Limited | Notification system and method for a mobile data communication device |
JP2000013414A (en) | 1998-06-25 | 2000-01-14 | Fujitsu Ltd | Intra-device supervisory and control system |
US6411605B1 (en) | 1998-07-08 | 2002-06-25 | Qwest Communications International, Inc. | Scheduler for telecommunications bridge |
JP3866418B2 (en) | 1998-07-09 | 2007-01-10 | 株式会社ナカヨ通信機 | Communication terminal |
US6269337B1 (en) | 1998-07-24 | 2001-07-31 | At&T Corp | Method and apparatus to provide enhanced directory assistance information in a communication network |
US6371484B1 (en) * | 1998-07-27 | 2002-04-16 | Tsuan Yuan | Casino card game |
US20020128033A1 (en) | 1998-11-30 | 2002-09-12 | Burgess Shelia Jean | Communications control method and apparatus |
US6310939B1 (en) | 1998-08-14 | 2001-10-30 | Lucent Technologies Inc. | Method and apparatus for screening a call as the call is transmitted to voice mail |
US6807258B1 (en) | 1998-08-25 | 2004-10-19 | Bellsouth Intellectual Property Corporation | Method and system for billing remote calls as if made from a primary line |
US6324269B1 (en) | 1998-08-25 | 2001-11-27 | Bellsouth Corporation | Method and system for billing remote calls as if made from a primary line |
US6775546B1 (en) | 1998-09-01 | 2004-08-10 | British Telecommunications Public Limited Company | Mobile telephone system |
US7222301B2 (en) * | 1998-09-11 | 2007-05-22 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment |
EA003432B1 (en) | 1998-09-15 | 2003-04-24 | Ин Тач Текнолоджиз Лимитед | Enhanced communication platform and a communication method using the platform |
US6876632B1 (en) * | 1998-09-25 | 2005-04-05 | Hitachi, Ltd. | Intelligent network with an internet call waiting function |
JP4484277B2 (en) | 1998-09-25 | 2010-06-16 | 株式会社日立製作所 | Service control device and gateway device |
US7836011B2 (en) * | 1998-10-01 | 2010-11-16 | Onepin, Inc. | Phone to phone data exchange |
US6374259B1 (en) | 1998-10-01 | 2002-04-16 | Onepin, Llc | Method and apparatus for storing and retreiving business contact information in computer system |
US6771949B1 (en) | 1998-10-09 | 2004-08-03 | Qwest Communications International, Inc. | Method and system for providing short message services outside of the wireless network |
US6298062B1 (en) | 1998-10-23 | 2001-10-02 | Verizon Laboratories Inc. | System providing integrated services over a computer network |
US6031896A (en) * | 1998-10-23 | 2000-02-29 | Gte Laboratories Incorporated | Real-time voicemail monitoring and call control over the internet |
JP3754833B2 (en) | 1998-10-27 | 2006-03-15 | 京セラ株式会社 | Communication terminal |
US6240449B1 (en) * | 1998-11-02 | 2001-05-29 | Nortel Networks Limited | Method and apparatus for automatic call setup in different network domains |
US6430176B1 (en) | 1998-11-06 | 2002-08-06 | Nortel Networks Limited | Multimedia channel management through PSTN signaling |
US7047416B2 (en) | 1998-11-09 | 2006-05-16 | First Data Corporation | Account-based digital signature (ABDS) system |
US6134548A (en) | 1998-11-19 | 2000-10-17 | Ac Properties B.V. | System, method and article of manufacture for advanced mobile bargain shopping |
US6161008A (en) | 1998-11-23 | 2000-12-12 | Nortel Networks Limited | Personal mobility and communication termination for users operating in a plurality of heterogeneous networks |
US6226374B1 (en) * | 1998-11-24 | 2001-05-01 | Qwest Communications International Inc. | Capacity provisioning for AIN |
JP3807857B2 (en) | 1998-11-26 | 2006-08-09 | シャープ株式会社 | E-mail system and e-mail server |
US6404873B1 (en) | 1998-12-01 | 2002-06-11 | Siemens Information And Communication Networks, Inc. | Subconference calling in a telephony-over-LAN environment |
US6285750B1 (en) | 1998-12-03 | 2001-09-04 | At&T Corp. | Method and apparatus for remotely controlling telephone call-forwarding |
US6366421B2 (en) | 1998-12-17 | 2002-04-02 | Texas Instruments Incorporated | Adjustable writer overshoot for a hard disk drive write head |
US6584122B1 (en) | 1998-12-18 | 2003-06-24 | Integral Access, Inc. | Method and system for providing voice and data service |
US6084628A (en) * | 1998-12-18 | 2000-07-04 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method of providing targeted advertising during video telephone calls |
EP1017210B1 (en) | 1998-12-22 | 2007-05-09 | Naxos Data LLC | Method to route an incoming call, telecommunication terminal, and arrangement for selecting a terminal suitable for the incoming call type |
US6408327B1 (en) | 1998-12-22 | 2002-06-18 | Nortel Networks Limited | Synthetic stereo conferencing over LAN/WAN |
US6349299B1 (en) | 1998-12-24 | 2002-02-19 | International Business Machines Corporation | System and method for storing electronic contact information into an electronic address book |
JP2000196756A (en) | 1998-12-25 | 2000-07-14 | Kansai Nippon Denki Tsushin System Kk | Incoming call transfer system |
US6885742B1 (en) * | 1998-12-29 | 2005-04-26 | Cingular Wireless Ii, Inc. | System and method for integrating call delivery for fixed-site and mobility services |
US6681119B1 (en) | 1998-12-31 | 2004-01-20 | Nortel Networks Ltd | Wireless communication system in which a call from a private branch exchange is selectively delivered to a mobile unit |
US6522734B1 (en) | 1998-12-31 | 2003-02-18 | Mci Worldcom, Inc. | Transaction billing for special service telephone numbers |
US6574470B1 (en) | 1998-12-31 | 2003-06-03 | At&T Corp. | Programmable ring-call forwarding in a wireless centrex services system |
US6363143B1 (en) * | 1999-01-19 | 2002-03-26 | Avaya Technology Corp. | Graphical and schedule-based definition of a call-coverage path |
US6584178B2 (en) * | 1999-01-28 | 2003-06-24 | Sbc Properties, L.P. | Method and system for termination blocking of message delivery service in a switch-based telecommunication system |
US20010012286A1 (en) | 1999-01-29 | 2001-08-09 | Emmanuel L. Huna | Method and apparatus for computer alert of device independent messages |
US6463145B1 (en) | 1999-01-29 | 2002-10-08 | Microsoft Corporation | Computer-implemented call forwarding options and methods therefor in a unified messaging system |
EP1028578A2 (en) | 1999-02-10 | 2000-08-16 | AT&T Corp. | Methods and apparatus for remotely accessing call originating information |
US6381323B1 (en) | 1999-02-16 | 2002-04-30 | Ameritech Corporation | Call programming apparatus and method |
JP2000270307A (en) | 1999-03-18 | 2000-09-29 | Canon Inc | Sound/video composite type interactive system, interactive controlling method and storing medium |
US6260050B1 (en) | 1999-03-23 | 2001-07-10 | Microstrategy, Inc. | System and method of adapting automatic output of service related OLAP reports to disparate output devices |
US6600736B1 (en) | 1999-03-31 | 2003-07-29 | Lucent Technologies Inc. | Method of providing transfer capability on web-based interactive voice response services |
US6690672B1 (en) | 1999-04-05 | 2004-02-10 | Avaya Inc. | Method and apparatus for placing an intelligent telephone call using an internet browser |
US6631186B1 (en) | 1999-04-09 | 2003-10-07 | Sbc Technology Resources, Inc. | System and method for implementing and accessing call forwarding services |
US6430289B1 (en) | 1999-04-13 | 2002-08-06 | Microsoft Corporation | System and method for computerized status monitor and use in a telephone network |
US6532285B1 (en) | 1999-04-14 | 2003-03-11 | Bellsouth Intellectual Property Corporation | Method and system for providing multiple services per trigger |
US6683939B1 (en) * | 1999-04-20 | 2004-01-27 | Microsoft Corporation | Method and apparatus for logging DTMF phone symbols dialed from an extension |
US6747970B1 (en) | 1999-04-29 | 2004-06-08 | Christopher H. Lamb | Methods and apparatus for providing communications services between connectionless and connection-oriented networks |
US6560329B1 (en) | 1999-04-29 | 2003-05-06 | Teloquent Communications Corporation | Automated call routing system |
US6373932B2 (en) | 1999-05-03 | 2002-04-16 | Hewlett-Packard Company | Configuration tracking system |
US6459913B2 (en) | 1999-05-03 | 2002-10-01 | At&T Corp. | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
US6609113B1 (en) | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
US20030069874A1 (en) | 1999-05-05 | 2003-04-10 | Eyal Hertzog | Method and system to automate the updating of personal information within a personal information management application and to synchronize such updated personal information management applications |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6668046B1 (en) | 1999-05-18 | 2003-12-23 | Motorola, Inc. | Method and system for generating a user's telecommunications bill |
US6473615B1 (en) | 1999-05-21 | 2002-10-29 | Ericsson Inc. | Selective call notification in a wireless network |
JP2001306616A (en) | 1999-05-25 | 2001-11-02 | Ichi Rei Yon Kk | Information providing display system |
US7379538B1 (en) * | 1999-06-04 | 2008-05-27 | Agere Systems Inc. | Telephone answering device which notifies a user based on call related information received from a calling party |
JP3940526B2 (en) | 1999-06-04 | 2007-07-04 | 株式会社東芝 | Telephone exchange equipment |
US6507644B1 (en) | 1999-06-08 | 2003-01-14 | Worldcom, Inc. | Pre-paid telephone calling card linked to a stored value account |
US20030147518A1 (en) | 1999-06-30 | 2003-08-07 | Nandakishore A. Albal | Methods and apparatus to deliver caller identification information |
US7149773B2 (en) | 1999-07-07 | 2006-12-12 | Medtronic, Inc. | System and method of automated invoicing for communications between an implantable medical device and a remote computer system or health care provider |
US6301609B1 (en) | 1999-07-07 | 2001-10-09 | Lucent Technologies Inc. | Assignable associate priorities for user-definable instant messaging buddy groups |
US6618710B1 (en) | 1999-07-07 | 2003-09-09 | International Business Machines Corporation | Apparatus and method for intelligent routing of electronic messages to pagers and computers |
US6768790B1 (en) | 1999-07-09 | 2004-07-27 | Pitney Bowes Inc. | Message automated information system and importance navigator |
US6470079B1 (en) | 1999-07-09 | 2002-10-22 | Who's Calling, Inc. | System and method for real-time reporting of advertising effectiveness |
US6963857B1 (en) | 1999-07-12 | 2005-11-08 | Jsa Technologies | Network-accessible account system |
US6611590B1 (en) | 1999-07-30 | 2003-08-26 | Avaya Technology Corp. | Enterprise-wide intelligent call center routing |
AU3771400A (en) | 1999-08-05 | 2001-03-05 | Princeton Protech Llc | Alarm reporting system using the internet and instant messaging |
US6547830B1 (en) | 1999-08-13 | 2003-04-15 | Pixo, Inc. | Methods and apparatuses for display and traversing of links in page character array |
US6327354B1 (en) * | 1999-08-17 | 2001-12-04 | Ameritech Corporation | Methods, systems, and articles for providing a family telecommunication service |
US6628194B1 (en) | 1999-08-31 | 2003-09-30 | At&T Wireless Services, Inc. | Filtered in-box for voice mail, e-mail, pages, web-based information, and faxes |
US6442748B1 (en) | 1999-08-31 | 2002-08-27 | Accenture Llp | System, method and article of manufacture for a persistent state and persistent object separator in an information services patterns environment |
US6373930B1 (en) | 1999-09-09 | 2002-04-16 | Sprint Communications Company L.P. | Method and system for monitoring telecommunications traffic |
US6873693B1 (en) | 1999-09-13 | 2005-03-29 | Microstrategy, Incorporated | System and method for real-time, personalized, dynamic, interactive voice services for entertainment-related information |
US6577622B1 (en) | 1999-09-27 | 2003-06-10 | 3Com Corp. | System and method for using a portable information device to establish a conference call on a telephony network |
US6718178B1 (en) * | 1999-10-01 | 2004-04-06 | Sprint Spectrum, L.P. | Automatic in-line messaging system |
US6704294B1 (en) * | 1999-10-13 | 2004-03-09 | Nortel Networks Limited | Establishment of a PSTN and internet multimedia collaboration session |
US6798753B1 (en) | 1999-10-14 | 2004-09-28 | International Business Machines Corporation | Automatically establishing conferences from desktop applications over the Internet |
US6594470B1 (en) | 1999-10-28 | 2003-07-15 | Nortel Networks Limited | System and method for remote management of call center operations |
US6738458B1 (en) | 1999-11-09 | 2004-05-18 | Bell South Intellectual Property Corporation | Methods and systems for changing the domain association of a mailbox in a messaging system |
US20020055351A1 (en) * | 1999-11-12 | 2002-05-09 | Elsey Nicholas J. | Technique for providing personalized information and communications services |
US6870921B1 (en) * | 1999-11-12 | 2005-03-22 | Metro One Telecommunications, Inc. | Enhanced directory assistance service providing individual or group directories |
US6389113B1 (en) * | 1999-11-16 | 2002-05-14 | Lucent Technologies Inc. | Dual-alerting paging system and monitoring of return call |
JP2001144859A (en) | 1999-11-17 | 2001-05-25 | Matsushita Electric Ind Co Ltd | Method and device for registering telephone directory information |
US6614786B1 (en) | 1999-11-24 | 2003-09-02 | Lucent Technologies Inc. | Enhanced dual mode telephone for internet telephony |
JP2001357312A (en) | 1999-11-24 | 2001-12-26 | Sega Corp | Information processor, file server, method and system for charging management, and recording medium with program recorded |
US6574324B1 (en) | 1999-11-24 | 2003-06-03 | Bellsouth Intellectual Property Corporation | System and method for long distance automatic call-back |
JP2001156921A (en) | 1999-11-30 | 2001-06-08 | Mega Chips Corp | Extension telephone transfer system |
ES2237022T3 (en) * | 1999-12-02 | 2005-07-16 | Sony International (Europe) Gmbh | INSTANT MESSAGING. |
US7174306B1 (en) * | 1999-12-02 | 2007-02-06 | Haseltine Systems, Inc. | Providing electronic access to consumer-customized nonverbal information regarding products and services |
DE19958707A1 (en) | 1999-12-06 | 2001-06-07 | Siemens Ag | Method of transmitting a text message |
US6853634B1 (en) | 1999-12-14 | 2005-02-08 | Nortel Networks Limited | Anonymity in a presence management system |
US6816468B1 (en) | 1999-12-16 | 2004-11-09 | Nortel Networks Limited | Captioning for tele-conferences |
US6735292B1 (en) * | 1999-12-17 | 2004-05-11 | Worldcom, Inc. | Method and system for priority call processing |
US6853713B1 (en) * | 1999-12-17 | 2005-02-08 | Nortel Networks Limited | Client-server network for managing internet protocol voice packets |
GB2391134B (en) | 1999-12-23 | 2004-05-12 | Mitel Knowledge Corp | Communication system architecture for voice first collaboration |
US6625258B1 (en) | 1999-12-27 | 2003-09-23 | Nortel Networks Ltd | System and method for providing unified communication services support |
US6577720B1 (en) | 1999-12-29 | 2003-06-10 | Nortel Networks Corporation | System and method for providing high-speed communications using a public terminal |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US7139728B2 (en) | 1999-12-30 | 2006-11-21 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US6373817B1 (en) * | 1999-12-30 | 2002-04-16 | At&T Corp. | Chase me system |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6917610B1 (en) | 1999-12-30 | 2005-07-12 | At&T Corp. | Activity log for improved call efficiency |
JP2001197210A (en) | 2000-01-07 | 2001-07-19 | Nippon Telegr & Teleph Corp <Ntt> | Method, system and controller for releasing telephone transfer setting, and recording medium |
GB0000464D0 (en) | 2000-01-10 | 2000-03-01 | British Telecomm | Telecommunications interface |
JP3889541B2 (en) | 2000-01-12 | 2007-03-07 | 三菱電機株式会社 | Wireless communication system, server and communication terminal, and group call control method |
DE10000826A1 (en) | 2000-01-12 | 2001-07-19 | Alcatel Sa | Methods, service computers, switching center, terminals and program modules for handling incoming telephone calls during an online data network session blocking a subscriber line |
US6275575B1 (en) | 2000-01-12 | 2001-08-14 | Right4Me.Com, Inc. | Method and system for coordinating and initiating cross-platform telephone conferences |
US6697796B2 (en) | 2000-01-13 | 2004-02-24 | Agere Systems Inc. | Voice clip search |
US7181417B1 (en) | 2000-01-21 | 2007-02-20 | Microstrategy, Inc. | System and method for revenue generation in an automatic, real-time delivery of personalized informational and transactional data |
US7822683B2 (en) | 2000-01-21 | 2010-10-26 | Microsoft Corporation | System and method for secure third-party development and hosting within a financial services network |
US7099835B2 (en) | 2000-01-31 | 2006-08-29 | Roadside Telematics Corporation | Methods and systems for providing life management and enhancement applications and services for telematics and other electronic medium |
US6744861B1 (en) | 2000-02-07 | 2004-06-01 | Verizon Services Corp. | Voice dialing methods and apparatus implemented using AIN techniques |
US20020046299A1 (en) * | 2000-02-09 | 2002-04-18 | Internet2Anywhere, Ltd. | Method and system for location independent and platform independent network signaling and action initiating |
IL150926A0 (en) | 2000-02-10 | 2003-02-12 | Jon Shore | Apparatus, systems and methods for wirelessly transacting financial transfers, electroniocally recordable authorization transfers, and other information transfers |
US6687362B1 (en) * | 2000-02-11 | 2004-02-03 | Hallmark Cards, Incorporated | Automatic address book update system |
US6459780B1 (en) | 2000-02-15 | 2002-10-01 | Verizon Services Corp. | Methods and apparatus for providing a called party call disposition options in real time |
US6697461B1 (en) | 2000-02-15 | 2004-02-24 | Bell Atlantic Services Network | Methods and apparatus for providing call screening and other communication services |
JP2001243231A (en) | 2000-02-25 | 2001-09-07 | Ntt Docomo Inc | Personal information registration system to mobile machine and mobile machine |
EP1130869B1 (en) | 2000-03-01 | 2005-06-01 | Sony International (Europe) GmbH | Management of user profile data |
US20030165223A1 (en) * | 2000-03-07 | 2003-09-04 | Timmins Timothy A. | Technique for providing a telecommunication service including information assistance |
GB2360373A (en) | 2000-03-15 | 2001-09-19 | Nadeem Ahmed | Computer apparatus for monitoring and updating accountancy records |
US6748068B1 (en) | 2000-03-27 | 2004-06-08 | Sbc Properties, L.P. | Method and system for providing enhanced caller identification information |
US20020022453A1 (en) | 2000-03-31 | 2002-02-21 | Horia Balog | Dynamic protocol selection and routing of content to mobile devices |
CA2404004A1 (en) | 2000-03-31 | 2001-10-11 | Nortel Networks Limited | Internet call waiting with voice mail system that provides monitoring during recording |
US6801610B1 (en) | 2000-04-07 | 2004-10-05 | Bellsouth Intellectual Property Corporation | System and method for automated conference call setup |
JP2001298545A (en) | 2000-04-11 | 2001-10-26 | Ntt Communications Kk | Multimedia conference service providing system of telephone using type |
US8903737B2 (en) | 2000-04-25 | 2014-12-02 | Accenture Global Service Limited | Method and system for a wireless universal mobile product interface |
US20020069060A1 (en) * | 2000-05-15 | 2002-06-06 | Samuel Cannavo | Method and system for automatically managing a voice-based communications systems |
AU2001261840A1 (en) * | 2000-05-16 | 2001-11-26 | Why, com, Inc. | Looking up a network resource location |
US7546337B1 (en) | 2000-05-18 | 2009-06-09 | Aol Llc, A Delaware Limited Liability Company | Transferring files |
EP1158814B1 (en) * | 2000-05-26 | 2008-03-26 | Nokia Siemens Networks Gmbh & Co. Kg | Method for destination control in an intelligent network |
DE10027659A1 (en) | 2000-06-03 | 2001-12-06 | Tenovis Gmbh & Co Kg | Method for generating a telephone book in a telephone device |
US6456234B1 (en) * | 2000-06-07 | 2002-09-24 | William J. Johnson | System and method for proactive content delivery by situation location |
JP3352449B2 (en) | 2000-06-08 | 2002-12-03 | ツインバード工業株式会社 | Lighting equipment |
US6807259B1 (en) | 2000-06-09 | 2004-10-19 | Nortel Networks, Ltd. | Audible calling line identification |
US20010054066A1 (en) | 2000-06-13 | 2001-12-20 | Louis Spitzer | Apparatus and method for transmitting information from signage to portable computing device, and system utilizing same |
AU2001268688A1 (en) | 2000-06-22 | 2002-01-02 | Eventra, Inc. | Method and system for supplier relationship management |
US6718026B1 (en) | 2000-06-30 | 2004-04-06 | Verizon Network Services, Inc. | Call forwarding methods and apparatus |
US20020071539A1 (en) | 2000-07-25 | 2002-06-13 | Marc Diament | Method and apparatus for telephony-enabled instant messaging |
JP2002044123A (en) | 2000-07-25 | 2002-02-08 | Nec Corp | Integrated messaging system |
JP2002044257A (en) | 2000-07-27 | 2002-02-08 | Dainippon Printing Co Ltd | Information providing system |
IE20010743A1 (en) | 2000-08-04 | 2002-04-17 | Mobileaware Technologies Ltd | An e-business mobility platform |
US20030167229A1 (en) | 2001-04-03 | 2003-09-04 | Bottomline Technologies, Inc. | Modular business transations platform |
JP2002057807A (en) | 2000-08-08 | 2002-02-22 | Nec Corp | Telephone directory management system for portable telephone |
US6907111B1 (en) * | 2000-08-09 | 2005-06-14 | Bellsouth Intellectual Property Corporation | Network and method for providing a name and number delivery telecommunications services with automatic speech recognition capability |
WO2002015519A2 (en) | 2000-08-17 | 2002-02-21 | Mobileum, Inc. | Method and system for wireless voice channel/data channel integration |
US6999563B1 (en) * | 2000-08-21 | 2006-02-14 | Volt Delta Resources, Llc | Enhanced directory assistance automation |
US6628770B1 (en) | 2000-08-31 | 2003-09-30 | Ericsson Inc. | Data mining of calls based on called party identity |
WO2002019648A2 (en) * | 2000-09-01 | 2002-03-07 | Muehlhaeuser Max | System and method for the wireless access of computer-based services in an attributable manner |
JP2002094696A (en) | 2000-09-13 | 2002-03-29 | Nec Access Technica Ltd | Device of turning accumulated voice into electronic mail and answer telephone service system |
US6442251B1 (en) | 2000-09-29 | 2002-08-27 | Palm Incorporated | Method and apparatus for taking a note while in a call |
US20020062251A1 (en) | 2000-09-29 | 2002-05-23 | Rajan Anandan | System and method for wireless consumer communications |
US20020040355A1 (en) | 2000-10-02 | 2002-04-04 | Weiner Steven D. | System and method for utility meter swipecard |
WO2002031760A2 (en) | 2000-10-13 | 2002-04-18 | Gemplus | Deployment of smart card based applications via mobile terminals |
US6757365B1 (en) | 2000-10-16 | 2004-06-29 | Tellme Networks, Inc. | Instant messaging via telephone interfaces |
US7031437B1 (en) | 2000-10-30 | 2006-04-18 | Nortel Networks Limited | Method and system for providing remote access to previously transmitted enterprise messages |
US20020085701A1 (en) | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified communication management based on presence information |
US20020078153A1 (en) | 2000-11-02 | 2002-06-20 | Chit Chung | Providing secure, instantaneous, directory-integrated, multiparty, communications services |
US6693897B1 (en) | 2000-11-10 | 2004-02-17 | Sbc Technology Resources, Inc. | Method and system of screening and control of telephone calls while using a packet-switched data network |
AU2381102A (en) * | 2000-11-20 | 2002-05-27 | British Telecomm | Method of managing resources |
US7317787B2 (en) | 2000-11-21 | 2008-01-08 | At&T Knowledge Ventures, L.P. | Voice enhancing for advance intelligent network services |
US7155001B2 (en) | 2001-10-24 | 2006-12-26 | Sbc Properties, L.P. | System and method for restricting and monitoring telephone calls |
DE10059327A1 (en) | 2000-11-29 | 2002-06-20 | Siemens Ag | Device and method for forwarding messages to end devices of various communication media |
DE10059175A1 (en) * | 2000-11-29 | 2002-06-20 | Siemens Ag | Method for diverting calls in a communications system with multiple terminals connects to a local area network for activating call rerouting from one terminal to another, for transferring information and for diverting a call. |
US6697473B2 (en) | 2000-12-04 | 2004-02-24 | Bobby G. Batten | Automated personalized telephone management system |
DE10060809A1 (en) | 2000-12-07 | 2002-06-20 | Aventis Pharma Gmbh | Substituted anthranilic acids, their use as medicaments or diagnostic agents, as well as medicaments containing them, and a combined pharmaceutical preparation with a sodium / hydrogen exchange (NHE) blocker |
US20020073163A1 (en) | 2000-12-12 | 2002-06-13 | Fuji Xerox Co., Ltd. | Systems and methods for supporting document centered discussion across heterogeneous devices and displays |
US20020077082A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited | Voice message presentation on personal wireless devices |
US20020075306A1 (en) | 2000-12-18 | 2002-06-20 | Christopher Thompson | Method and system for initiating communications with dispersed team members from within a virtual team environment using personal identifiers |
US20020075303A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited And Bell Canada | Method and system for creating a virtual team environment |
US6665388B2 (en) | 2000-12-20 | 2003-12-16 | Bellsouth Intellectual Property Corporation | System and method for monitoring incoming communications to a telecommunications device |
US7024209B1 (en) | 2000-12-20 | 2006-04-04 | Cisco Technology, Inc. | Unified messaging system configured for management of short message service-type messages |
US6847823B2 (en) * | 2000-12-20 | 2005-01-25 | Nokia Corporation | System and method for accessing local services with a mobile terminal |
US20020076027A1 (en) | 2000-12-20 | 2002-06-20 | Nortel Networks Limited | Fallback to message compose on synchronous call attempt |
US6792092B1 (en) | 2000-12-20 | 2004-09-14 | Cisco Technology, Inc. | Method and system for independent participant control of audio during multiparty communication sessions |
US20020080942A1 (en) | 2000-12-21 | 2002-06-27 | Clapper Edward O. | Origin-independent custom caller ID |
US20020083462A1 (en) | 2000-12-21 | 2002-06-27 | Arnott Robert J. | Apparatus and method for establishing audio and video conferencing |
US20020082028A1 (en) | 2000-12-22 | 2002-06-27 | Wittenkamp Peter David Forsling | Paging and selective call routing in a telecommunication environment |
US7209966B2 (en) | 2000-12-22 | 2007-04-24 | Openwave Systems Inc. | Method and system for facilitating mediated communication |
EP1348165A4 (en) | 2000-12-26 | 2009-01-28 | Polycom Inc | System and method for coordinating a conference using a dedicated server |
JP3833470B2 (en) | 2000-12-27 | 2006-10-11 | 三菱電機株式会社 | Multipoint communication system and multipoint communication method |
US20020085515A1 (en) | 2000-12-28 | 2002-07-04 | Jaynes Christopher O. | Object specific information relaying system |
US7388949B2 (en) | 2000-12-28 | 2008-06-17 | At&T Delaware Intellectual Property, Inc. | System and method for audio caller identification service |
US6647108B1 (en) | 2001-01-02 | 2003-11-11 | Verizon Services Corp. | Internet call manager |
CA2368404C (en) | 2001-01-18 | 2005-08-09 | Research In Motion Limited | Unified messaging system and method |
US20020103898A1 (en) | 2001-01-31 | 2002-08-01 | Moyer Stanley L. | System and method for using session initiation protocol (SIP) to communicate with networked appliances |
JP3929248B2 (en) | 2001-02-02 | 2007-06-13 | 株式会社イメ−ジパ−トナ− | Telephone conference system |
US7107312B2 (en) | 2001-02-06 | 2006-09-12 | Lucent Technologies Inc. | Apparatus and method for use in a data/conference call system for automatically collecting participant information and providing all participants with that information for use in collaboration services |
US20020147777A1 (en) | 2001-02-06 | 2002-10-10 | Hackbarth Randy L. | Apparatus and method for use in portal service for a team utilizing collaboration services |
JP2002237893A (en) | 2001-02-09 | 2002-08-23 | Nippon Telegr & Teleph Corp <Ntt> | Method and equipment for communication |
US6950402B2 (en) | 2001-02-15 | 2005-09-27 | Persona Software, Inc. | Web-enabled call management method and apparatus |
US7254220B1 (en) | 2001-02-16 | 2007-08-07 | Telesector Resources Group, Inc. | Methods and apparatus for obtaining and distributing voice mail information |
JP2002247148A (en) | 2001-02-18 | 2002-08-30 | Tanabe Junzo | Communication controller with phone incoming notice function and notice method |
DE60115835T2 (en) * | 2001-02-19 | 2006-07-06 | Alcatel | A method for handling incoming calls in a mobile terminal with a short-range interface, and mobile terminal and computer program therefor |
US7142646B2 (en) | 2001-02-27 | 2006-11-28 | Verizon Data Services Inc. | Voice mail integration with instant messenger |
US7912193B2 (en) * | 2001-02-27 | 2011-03-22 | Verizon Data Services Llc | Methods and systems for call management with user intervention |
US8750482B2 (en) * | 2001-02-27 | 2014-06-10 | Verizon Data Services Llc | Methods and systems for preemptive rejection of calls |
US7418090B2 (en) | 2002-11-25 | 2008-08-26 | Telesector Resources Group Inc. | Methods and systems for conference call buffering |
JP2002261834A (en) | 2001-02-27 | 2002-09-13 | Ntt Advanced Technology Corp | Method and system for processing communication |
US8774380B2 (en) * | 2001-02-27 | 2014-07-08 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
US7190773B1 (en) | 2001-02-27 | 2007-03-13 | Verizon Data Services Inc. | Device independent caller ID |
US20060276179A1 (en) | 2001-02-27 | 2006-12-07 | Reza Ghaffari | Methods and systems for integrating communications services |
US8488766B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for multiuser selective notification |
US8503639B2 (en) * | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Method and apparatus for adaptive message and call notification |
US8467502B2 (en) | 2001-02-27 | 2013-06-18 | Verizon Data Services Llc | Interactive assistant for managing telephone communications |
US20050220286A1 (en) | 2001-02-27 | 2005-10-06 | John Valdez | Method and apparatus for facilitating integrated access to communications services in a communication device |
KR20020071296A (en) | 2001-03-06 | 2002-09-12 | 삼성전자 주식회사 | Method for forwarding short message in mobile telecommunication system |
DE10110942A1 (en) | 2001-03-07 | 2002-09-26 | Siemens Ag | Automatic call list updating method for mobile telephone transmits call number to mobile telephone call list dependent on call events at associated fixed network terminal |
US6788772B2 (en) | 2001-03-07 | 2004-09-07 | Zvi Barak | System and method for controlling outgoing telephone calls |
US20020137530A1 (en) | 2001-03-08 | 2002-09-26 | Katyayini Karve | Cellular telephone with SMS message forwarding |
WO2002073984A1 (en) | 2001-03-09 | 2002-09-19 | Ayman, L.L.C. | Universal point of contact identifier system and method |
US20020137507A1 (en) | 2001-03-20 | 2002-09-26 | Techimage, Llp., | System and method for providing automatic multimedia messages service |
JP2002300306A (en) | 2001-03-30 | 2002-10-11 | Tsubasa System Co Ltd | Telephone number information distribution method, telephone number information distribution program, and telephone number information distribution system |
JP2002300290A (en) | 2001-04-02 | 2002-10-11 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for managing communication history information, program therefor and recording medium |
US20020178117A1 (en) | 2001-04-03 | 2002-11-28 | Bottomline Technologies (De) Inc. | Electronic bill presentment system with automated tax and fee adjustment |
US20020146105A1 (en) | 2001-04-05 | 2002-10-10 | International Business Machines Corporation | Interactive call forwarding |
US20020152165A1 (en) | 2001-04-12 | 2002-10-17 | International Business Machines Corporation | Method and apparatus for bill payments at an automatic teller machine |
US6661340B1 (en) | 2001-04-24 | 2003-12-09 | Microstrategy Incorporated | System and method for connecting security systems to a wireless device |
US6820055B2 (en) | 2001-04-26 | 2004-11-16 | Speche Communications | Systems and methods for automated audio transcription, translation, and transfer with text display software for manipulating the text |
US20030187992A1 (en) | 2001-05-07 | 2003-10-02 | Steenfeldt Rico Werni | Service triggering framework |
JP2002344652A (en) | 2001-05-21 | 2002-11-29 | Nec Access Technica Ltd | Mobile communication terminal and reply method by electronic mail |
DE10125284A1 (en) | 2001-05-23 | 2002-11-28 | Alcatel Sa | Procedure for selecting one of at least two devices |
US20050102382A1 (en) | 2001-06-04 | 2005-05-12 | Macgregor Glenn | System and method for network management using instant messaging |
US20030014488A1 (en) * | 2001-06-13 | 2003-01-16 | Siddhartha Dalal | System and method for enabling multimedia conferencing services on a real-time communications platform |
US6842460B1 (en) * | 2001-06-27 | 2005-01-11 | Nokia Corporation | Ad hoc network discovery menu |
US7076528B2 (en) | 2001-07-11 | 2006-07-11 | Symbol Technologies, Inc. | System and method for communicating messages between a host computer and a designated device |
US20030036380A1 (en) * | 2001-08-01 | 2003-02-20 | Skidmore Adrian Gary | Method of data transfer |
US6958984B2 (en) | 2001-08-02 | 2005-10-25 | Motorola, Inc. | Method and apparatus for aggregation of wireless resources of proximal wireless units to facilitate diversity signal combining |
US7315614B2 (en) * | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
US20030035381A1 (en) | 2001-08-16 | 2003-02-20 | Yihsiu Chen | Network-based teleconferencing capabilities utilizing data network call set-up requests |
KR20030020768A (en) | 2001-09-04 | 2003-03-10 | 주식회사 케이티 | Description of automatic voice call connection service method by construction of personal phone book database using speech recognition and its related methods |
US6658260B2 (en) * | 2001-09-05 | 2003-12-02 | Telecommunication Systems, Inc. | Inter-carrier short messaging service providing phone number only experience |
US20030058838A1 (en) * | 2001-09-06 | 2003-03-27 | Michael Wengrovitz | System and method for transmitting information via a call center SIP server |
US20030046071A1 (en) * | 2001-09-06 | 2003-03-06 | International Business Machines Corporation | Voice recognition apparatus and method |
US6870916B2 (en) | 2001-09-14 | 2005-03-22 | Lucent Technologies Inc. | Targeted and intelligent multimedia conference establishment services |
EP1294201A1 (en) * | 2001-09-18 | 2003-03-19 | Lucent Technologies Inc. | A method of forwarding text messages, a mobile telecommunications network, a register for a mobile telecommunications network, and a mobile telecommunications terminal |
US7082313B2 (en) * | 2001-09-24 | 2006-07-25 | Qualcomm Incorporated | Secure short message service |
US7362854B2 (en) * | 2001-09-28 | 2008-04-22 | Gateway Inc. | Portable electronic device having integrated telephony and calendar functions |
US6876736B2 (en) * | 2001-10-16 | 2005-04-05 | Adtran, Inc. | Call-routing mechanism for automatically performing number substitution in an integrated access device |
US7099288B1 (en) | 2001-10-16 | 2006-08-29 | Sprint Communications Company L.P. | Telephonic addressing for establishing simultaneous voice and computer network connections |
US6674459B2 (en) | 2001-10-24 | 2004-01-06 | Microsoft Corporation | Network conference recording system and method including post-conference processing |
US6996227B2 (en) | 2001-10-24 | 2006-02-07 | Motorola, Inc. | Systems and methods for storing information associated with a subscriber |
US6590603B2 (en) | 2001-10-31 | 2003-07-08 | Forgent Networks, Inc. | System and method for managing streaming data |
US20030083040A1 (en) | 2001-11-01 | 2003-05-01 | Todd Ruth | Method of logging call processing information in a mobile communication network |
US20030208541A1 (en) | 2001-11-10 | 2003-11-06 | Jeff Musa | Handheld wireless conferencing technology |
US20030092451A1 (en) * | 2001-11-15 | 2003-05-15 | Ibm Corporation | Method of mobile phone consolidation |
GB2382174A (en) | 2001-11-20 | 2003-05-21 | Hewlett Packard Co | Data formatting in a platform independent manner |
US20030104827A1 (en) | 2001-11-30 | 2003-06-05 | Brian Moran | Rerouting/reformating wireless messages for cross connectivity between service providers |
US7443970B2 (en) | 2001-12-17 | 2008-10-28 | International Business Machines Corporation | Logging calls according to call context |
US20030179743A1 (en) | 2001-12-18 | 2003-09-25 | Bosik Barry S. | Call management method responsive to network presence |
US20030112952A1 (en) | 2001-12-19 | 2003-06-19 | Wendell Brown | Automatically establishing a telephone connection between a subscriber and a party meeting one or more criteria |
US6668049B1 (en) | 2001-12-19 | 2003-12-23 | Bellsouth Intellectual Property Corporation | Systems and methods for intelligent third-party redirection of an incoming call via a display-based communication center |
US7116994B2 (en) | 2001-12-21 | 2006-10-03 | Nokia Corporation | Mobile network message to email redirection |
US6882714B2 (en) * | 2002-03-27 | 2005-04-19 | Sharp Laboratories Of America, Inc. | Universal call-log system and method for a home network telephone |
US7085357B2 (en) | 2002-01-31 | 2006-08-01 | Sharp Laboratories Of America, Inc. | System and method for external voice mail notification by a home network telephone answering device |
US7130390B2 (en) | 2002-02-01 | 2006-10-31 | Microsoft Corporation | Audio messaging system and method |
US7228335B2 (en) | 2002-02-19 | 2007-06-05 | Goodcontacts Research Ltd. | Method of automatically populating contact information fields for a new contract added to an electronic contact database |
US7167547B2 (en) | 2002-03-20 | 2007-01-23 | Bellsouth Intellectual Property Corporation | Personal calendaring, schedules, and notification using directory data |
US7043521B2 (en) * | 2002-03-21 | 2006-05-09 | Rockwell Electronic Commerce Technologies, Llc | Search agent for searching the internet |
US6957077B2 (en) | 2002-05-06 | 2005-10-18 | Microsoft Corporation | System and method for enabling instant messaging on a mobile device |
US6954524B2 (en) | 2002-06-07 | 2005-10-11 | Sbc Properties, L.P. | System and method for implementing and accessing call forwarding services |
US8005461B2 (en) | 2002-06-10 | 2011-08-23 | Research In Motion Limited | Voicemail notification messaging for mobile communication devices |
US6996409B2 (en) * | 2002-06-26 | 2006-02-07 | Level Z, L.L.C. | Multi-party concurrence through short message service exchanges |
US20040127256A1 (en) | 2002-07-30 | 2004-07-01 | Scott Goldthwaite | Mobile device equipped with a contactless smart card reader/writer |
US7254643B1 (en) | 2002-08-08 | 2007-08-07 | At&T Corp. | System and method for providing multi-media services to communication devices over a communications network |
US6956942B2 (en) | 2002-09-18 | 2005-10-18 | Sbc Properties, L.P. | Multi-modal address book |
US7212808B2 (en) | 2002-10-15 | 2007-05-01 | Wildseed Ltd. | Unified message box for wireless mobile communication devices |
US20040081292A1 (en) * | 2002-10-23 | 2004-04-29 | International Business Machines Corporation | System and method for managing personel telephony recording |
US7065198B2 (en) | 2002-10-23 | 2006-06-20 | International Business Machines Corporation | System and method for volume control management in a personal telephony recorder |
US7428580B2 (en) | 2003-11-26 | 2008-09-23 | Aol Llc | Electronic message forwarding |
US7130403B2 (en) | 2002-12-11 | 2006-10-31 | Siemens Communications, Inc. | System and method for enhanced multimedia conference collaboration |
US20040119814A1 (en) | 2002-12-20 | 2004-06-24 | Clisham Allister B. | Video conferencing system and method |
US7187932B1 (en) * | 2003-01-16 | 2007-03-06 | Cingular Wireless Ii, Llc | Autopopulation of address book entries |
US7068768B2 (en) | 2003-01-29 | 2006-06-27 | America Online, Inc. | Method for populating a caller's information to a host-based address book |
US8538386B2 (en) | 2004-03-01 | 2013-09-17 | Blackberry Limited | Communications system providing text-to-speech message conversion features using audio filter parameters and related methods |
US7139782B2 (en) | 2004-09-21 | 2006-11-21 | Hitachi, Ltd. | Method of and system for testing remote storage |
US7245929B2 (en) | 2005-07-05 | 2007-07-17 | Yahoo! Inc. | Enabling text messaging between a member and non-member of a community based on a common short code |
-
2003
- 2003-11-24 US US10/720,868 patent/US8472606B2/en active Active
- 2003-11-25 AU AU2003293055A patent/AU2003293055A1/en not_active Abandoned
- 2003-11-25 CA CA002507083A patent/CA2507083A1/en not_active Abandoned
- 2003-11-25 WO PCT/US2003/037699 patent/WO2004049130A2/en active Application Filing
- 2003-11-25 EP EP03790046A patent/EP1570359A4/en not_active Withdrawn
- 2003-11-25 JP JP2004555735A patent/JP2006507770A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
EP1570359A2 (en) | 2005-09-07 |
AU2003293055A1 (en) | 2004-06-18 |
AU2003293055A8 (en) | 2004-06-18 |
WO2004049130A3 (en) | 2004-08-19 |
US20050053220A1 (en) | 2005-03-10 |
JP2006507770A (en) | 2006-03-02 |
US8472606B2 (en) | 2013-06-25 |
WO2004049130A2 (en) | 2004-06-10 |
EP1570359A4 (en) | 2006-10-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8472606B2 (en) | Methods and systems for directory information lookup | |
CA2507091C (en) | Methods and systems for contact management | |
US7836147B2 (en) | Method and apparatus for address book contact sharing | |
CA2507492C (en) | Methods and systems for a call log | |
US8761816B2 (en) | Methods and systems for single number text messaging | |
US8503639B2 (en) | Method and apparatus for adaptive message and call notification | |
US8798251B2 (en) | Methods and systems for computer enhanced conference calling | |
CA2507097C (en) | Methods and systems for notification of call to device | |
EP1568193A2 (en) | Methods and systems for computer enhanced conference calling | |
CA2507085A1 (en) | Method and apparatus for adaptive message notification | |
US8824642B2 (en) | Method and apparatus for enabling a user to perform telecommunications operations | |
JP2006507776A (en) | Method and system for contact management | |
WO2004049679A1 (en) | Method and systems for single number text messaging |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |
Effective date: 20130710 |