CA2774362C - Methods and systems for call management with user intervention - Google Patents
Methods and systems for call management with user intervention Download PDFInfo
- Publication number
- CA2774362C CA2774362C CA2774362A CA2774362A CA2774362C CA 2774362 C CA2774362 C CA 2774362C CA 2774362 A CA2774362 A CA 2774362A CA 2774362 A CA2774362 A CA 2774362A CA 2774362 C CA2774362 C CA 2774362C
- Authority
- CA
- Canada
- Prior art keywords
- call
- customer
- notification
- response
- control point
- 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.)
- Expired - Fee Related
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/40—Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2005—Temporarily overriding a service configuration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2011—Service processing based on information specified by a party before or during a call, e.g. information, tone or routing selection
-
- 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
Abstract
Methods and systems for managing a call in real-time are disclosed. Methods and systems consistent with the present invention manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user from a service control point and sends a notification of the call to a device associated with the user. The service center receives a response to the notification from the user. Thereafter, the service center instructs the service control point to connect the call based on the response.
Description
METHODS AND SYSTEMS FOR CALL MANAGEMENT WITH USER INTERVENTION
TECHNICAL FIELD
[0004] The present invention relates generally to data processing systems and, more particularly, to a method and system for managing calls in real-time with user intervention.
BACKGROUND
[0005] 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 such as email and instant messaging.
[0006] 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.
[0007] A user may also wish to treat a phone call differently dependent on who is calling the user. For example, if a user receives a call from a caller that the user does not want to speak to at the moment, the user may want to send that call directly to voice mail. Also, if a user receives a call from a number that displays no caller ID information or that the user otherwise does not recognize, the user may wish to somehow specially treat the call because the caller is a potential telemarketer.
[0008] Current call management systems make it possible for a user to receive notification of a call on a communications device, and then to either take the call or divert it to voice mail to the user's discretion.
Current call management systems also make it possible to automatically intercept and specially treat a call that displays no caller ID information.
TECHNICAL FIELD
[0004] The present invention relates generally to data processing systems and, more particularly, to a method and system for managing calls in real-time with user intervention.
BACKGROUND
[0005] 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 such as email and instant messaging.
[0006] 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.
[0007] A user may also wish to treat a phone call differently dependent on who is calling the user. For example, if a user receives a call from a caller that the user does not want to speak to at the moment, the user may want to send that call directly to voice mail. Also, if a user receives a call from a number that displays no caller ID information or that the user otherwise does not recognize, the user may wish to somehow specially treat the call because the caller is a potential telemarketer.
[0008] Current call management systems make it possible for a user to receive notification of a call on a communications device, and then to either take the call or divert it to voice mail to the user's discretion.
Current call management systems also make it possible to automatically intercept and specially treat a call that displays no caller ID information.
[0009] Current call management systems, however, do not enable a user to perform other functions as a call is being received, such as forwarding a phone call received on one device to another device, manually initiating protection from telemarketers, or otherwise managing a call in real-time.
Accordingly, there is a need for a method and system for a method and system for managing calls in real-time with user intervention.
SUMMARY OF THE INVENTION
[0010] Methods and systems consistent with the principles of the invention manage a call. A service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also sends a notification of the call to a device associated with the customer and receives a response to the notification from the customer. Thereafter, the service center instructs the service control point to connect the call based on the response.
[0011] Other methods and systems consistent with the principles of the invention also manage a call. A
service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also retrieves data corresponding to the customer using the information pertaining to the call, sends a notification of the call to a device associated with the customer, and receives a response to the notification from the customer. Thereafter, the service center instructs the service control point to connect the call based on the response.
[0012] Other methods and systems consistent with the principles of the invention manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user.
The service center also sends a notification of the call to a first device associated with the user and receives a response to the notification from the user. Thereafter, a service control point forwards the call to a second device based on the response. The user provides a telephone number for the second device.
[0013] Other methods and systems consistent with the principles of the invention also manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user. The service center also retrieves data corresponding to the user using the information pertaining to the call and selects a device associated with the user to receive a notification of the call based on the retrieved data corresponding to the user. Additionally, the service center provides the notification to the selected device for display on the selected device and receives a response to the notification from the user. Thereafter, a service control point initiates a call screening process based on the response.
[0014] Other methods and systems consistent with the principles of the invention also manage a call. A
service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also retrieves data corresponding to the customer using the information pertaining to the call, determines features enabled for the customer based on the information pertaining to the call, selects a device associated with the customer to receive a notification of the call based on the retrieved data, provides the notification to the selected device, and receives a response to the notification from the customer.
Thereafter, the service center instructs the service control point to connect the call based on the response.
[0015] Other methods and systems consistent with the principles of the invention also manage a call. A
device associated with a customer receives a notification of a call to the customer, wherein the device is determined based on retrieved data corresponding to the customer and the retrieved data was retrieved using information pertaining to the call. The device also receives input from the customer indicative of a response to the notification and sends response information to a server reflective of the response to the notification. Thereafter, the server instructs a service control point to connect the call based on the response to the notification.
[0016] Other methods and systems consistent with the principles of the invention also manage a call. A
service control point sends information to a service center pertaining to a call to a customer. The service center is operable to retrieve data corresponding to the customer using the information pertaining to the call; send a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, and the device is one of a plurality of devices associated with the customer; and provide response information reflective of a response to the notification from the customer. The service control point receives the response information from the service center and connects the call based on the response information.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one embodiment of the invention and, together with the description, serve to explain the principles of the invention.
[0018] 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;
[0019] FIG. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[0020] FIG. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[0021] FIG. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[0022] FIG. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[0023] FIG. 6 is a diagram of an exemplary network access server consistent with the principles of the present invention;
[0024] FIG. 7 is a diagram of an exemplary application server consistent with the principles of the present invention;
[0025] FIG. 8 is a diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention;
[0026] FIGS. 9A and 9B comprise another diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention;
[0027] FIG. 10 is a diagram of an exemplary user interface including customer-selectable real-time call management options consistent with the present invention; and [0028] FIG. 11 is a diagram of an exemplary user interface that enables a customer to change preferences consistent with the present invention.
DETAILED DESCRIPTION
[0029] 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 drawings to refer to the same or like parts. While the description includes exemplary embodiments, other embodiments are possible, and changes may be made to the embodiments described without departing from the spirit and scope of the invention. The following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and their equivalents.
Overview [0030] Methods and systems consistent with the present invention manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user from a service control point. The service center also retrieves data corresponding to the user using the information pertaining to the call and sends a notification of the call to a device associated with the user. The device is determined based on the retrieved data. Based on a response to the notification from the user, the service center instructs the service control point to connect the call by providing the service control point with response information reflective of the response. The service control point thereafter receives the response information from the service center and connects the call based on the response information.
Network Environment [0031] 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 anyone of phones 114, 116, and 118.
[0032] 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.
[0033] 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 on a voice over broadband network, such as a network using voice-over Internet Protocol ("VoIP") technology. Additionally, in other embodiments, the voice network may be a video over broadband network, such as, for example, a network for providing 2-way video communications. In another example, the voice network may be a wireless broadband network, such as, for example, a network using WiFi (i.e., IEEE 802.11 (b) and/or (g)). In yet another example, the voice network 104 may be a wireless voice network(s), such as, for example, a cellular or third-generation cellular network). In addition, voice network 104 may be implemented using any single or combination of the above-described technologies 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's.TM.
Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[0034] 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 conversions, 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.
[0035] 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 Blackberry.TM., and Ergo Audrey.TM..
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.
[0036] 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").
[0037] 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 terminal 112 may communicate with service center 106 via a proxy.
[0038] 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.
[0039] FIG. 2 is a block diagram of a user terminal consistent with the present invention. User terminal 112 may include 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.
[0040] 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 Pentium.TM. processor provided from Intel Corporation.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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) 304 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, an Intelligent Peripheral (IP) 320, and a switch access 322. Although this embodiment of a voice network 104 is described as a PSTN, as discussed above in other embodiments, the voice network 104 may be, for example, a voice or video over broadband network a wireless broadband, a wireless voice network, etc.
[0048] 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.
[0049] ISCP 302 may also be, for example, a standard service control point (SCP), an Advanced Intelligent Network (AIN) SCP, a soft switch, or any other network call controller. 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 include service logic used to provide a switch, such as SSP 308 or 310, with specific call processing instructions. ISCP 302 may also store data related to various features that a user may activate. Such features may include, for example, call intercept and voice mail. ISCP 302 may be implemented using a combination of known hardware and software. ISCP 302 is shown with a direct connection to service center 106 and a connection to ISCP SPACE 314, however, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP
302, ISCP SPACE 314, and service center 106. Further, information exchanged between the ISCP 302 and service center 106 may use, for example, the SR-3389 General Data Interface (GDI) for TCP/IP.
[0050] 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 304 or 306 may be implemented using known hardware and software from manufacturers such as NORTEL.TM. and LUCENT
Technologies.TM..
[0051] 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.
[0052] 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.
Although, in this figure, LIDB
312 is illustrated as directly connected to ISCP 302, LIDB 312 may be connected to ISCP 302 through an STP (e.g., 304 and 306). Additionally, this communication link may use, for example, the GR-2838 General Dynamic Interface (GDI) for SS7.
[0053] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of the ISCP 302 or be separate from the ISCP 302. For example, the Telcordia.TM. 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.
[0054] In one embodiment, customer records may be stored in the ISCP SPACE 314 such that the records may be updated and sent to the 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, and/or 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).
[0055] Additionally, the 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 MIS 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 the ISCP SPACE 314, which then propagates the instructions to the ISCP 302 as discussed above. Further, an MSP or eRC may be used, for example, for providing updates to both the SSPs 308 or 310 and the ISCPs 302. Or, for example, an eRC may be used for providing updates to the SSPs 308 or 310, while an AAIS is used for providing updates to the ISCPs 302.
[0056] Updates sent to the SSPs 308 or 310 may be sent from the recent change engine 316 via a switch access 322 that may, for example, convert the updates into the appropriate protocol for the SSP 308 or 310. For example, recent change engine 316 may send updates to the SSPs 308 or 310 via TCP/IP. The switch access 322 may then convert the updates from TCP/IP to X.25. This switch access 322 may be implemented using hardware and/or software. These connections may include any number of elements, such as, for example, switches, routers, hubs, etc. and may be, for example, an internal data network for the voice network 104.
[0057] The voice network 104 may also include one or more intelligent peripherals (IP). For example, in FIG. 3, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing functions for interaction between users and the voice network, such as voice mail services, digit collection, customized announcements, voice recognition, etc. Moreover, the communications between the SSP 308 and IP 320 may use the Primary Rate interface (PRi) (e.g., the 1129 protocol) protocol.
Additionally, the IP 320 may be capable of sending and receiving information to/from the Service Center 106. These communications may use, for example, the SR-3511 protocol. Further, although FIG. 3 illustrates this connection as a direct connection, this connection may include any number of elements including routers, switches, hubs, etc., and may be via, for example, an internal data network for the voice network 104.
[0058] 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. The 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 server(s) 420 may be provided between the service center 106 and the voice network 104.
[0059] 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 appropriate 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.
[0060] 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 the network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[0061] Each server (406, 408, 410, 414, 416, 420) may be any appropriate 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.
[0062] 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, real-time call management, etc. In one embodiment, real-time call management enables a user to perform several functions as a call is being received, such as sending a call to voice mail, sending a call received on one device to another device, manually initiating protection from telemarketers, playing an announcement for the caller, scheduling a call back, bridging a caller onto a current call, etc.
[0063] 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. The network access servers 410 may provide the hardware and software for sending and receiving information to the voice network 104 in processing the applications provided by the service center. For example, the 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 the voice network 104.
[0064] The 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 the voice portal 412.
Then the customer using speech may instruct the service center 105 to modify the services to which the customer subscribes. The voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. The voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. The application function 414 may take, for example, the output from the voice recognition function 416, convert it to a format suitable for the service center 106 and forward the information to one or more servers (406, 408, 410) in the service center 106.
[0065] 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 502, application service 504, network access 506, and the voice network 508.
[0066] Client side 502 includes user terminals 112_A and 112_6 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 phone(s) 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 the Service Center 106, while user terminal 112_6 may be a desktop type computer running a web browser for communicating with the 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.
[0067] The application service plane 504 includes the digital companion server(s) 406, communication portal server(s) 408, and the 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.
[0068] 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.
[0069] The 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 the data network 102 go through the client proxy 512. Also, if the client proxy 512 is included on a separate server, for example, an additional firewall may be provided between the client proxy 512 and the other digital companion servers to provide additional security.
[0070] Web server 514 provides functionality for receiving traffic over the 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.
[0071] Application server function 516 encompasses the general functions performed by the digital companion server(s) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific services 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, enabling call management with user intervention in real-time, etc.
[0072] Additionally, the 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, the 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.).
[0073] 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.
[0074] Notification server function 520 provides the capability to send information from the service center 106 to a user terminal 112. For example, the notification server function 520 at the direction of the application server function 516 may send a notification to the user terminal 112 that the user is presently receiving a phone call at the user's phone 114. This notification may be, for example, an instant message pop-up window that provides an identification of the caller as well as the number being called. The notification may also have a number of user-selectable buttons or items associated with it that enable the user to manage a call in real-time.
[0075] 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 the database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[0076] As discussed above, the communication portal server(s) 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.
[0077] Web server function 526, as with web server function 514 of the digital companion servers, provides functionality for receiving traffic over the 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.
[0078] The application server function 528 encompasses the general functions performed by the 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, the application server function 528 may include the functionality of sending and/or receiving information to/from external servers and/or devices.
For example, the communication portal servers 408 may be connected to a network, such as, the Internet. The application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages web page. The application server 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.
[0079] In another example, the application server function 528 of the 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.
[0080] Moreover, the application server function 528, similar to application server 516, may provide functionality to facilitate services performed 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, enabling call management with user intervention in real-time, etc.
[0081] The contacts database 530 includes storage devices for storing an address book for the user. This address book may be any appropriate type of address book. For example, the user's address book may include the names, phone numbers, and addresses of people and/or organizations. These storage devices may be internal or external to the communication portal servers 406 or some combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[0082] The 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.
[0083] The application services plane 504 of the architecture may also include a voice portal 412. As discussed above, the 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.
The application server function 414 of the voice portal 412 may include hardware and/or software for exchanging information between the digital companion servers 406 and the voice recognition function 416. Additionally, the application server function 414 may be included on a separate server, included in the hardware and software providing the voice recognition function 416, included in the digital companion servers 406, etc.
[0084] The Network Access plane 506 of the architecture includes the functions for providing connectivity between the application service plane 502 and the voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[0085] As discussed above, recent change engines 316 may be used to update switches and ISCP
databases included in the voice network 104. In one embodiment, the 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 the digital companion servers 406 and the recent change engines 542 for security purposes.
[0086] The 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 the voice network 410 in processing the applications provided by the service center. For example, the network access servers 410 may include a Caller ID (CID) functionality for retrieving caller ID information from the 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.
[0087] Network Access plane 506 may also include one or more back end server(s) 420. These back end server(s) 420 may include hardware and/or software for interfacing the service center 106 and the voice network 104. The back end server(s) 420 may be connected to the service center 106 by a network, by a direct connection, or in any other suitable manner. Further, the back end server(s) 420 may connect to one or more devices in the voice network 104 by a network, a direct connection, or in any other suitable manner.
[0088] The back end server(s) 420 may include, for example, a server providing a voice mail retrieval and notification function. 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 the digital companion servers 406.
[0089] Additionally, these back end server(s) 420 may also include, for example, a directory assistance server. This directory assistance server may interface the service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of the voice network 104. An RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of the 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.
[0090] In another example, the back end server(s) 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 server(s) 420, this wireless internet gateway may be used for converting requests and information between the formats used by the service center 106 and those used by the wireless voice network.
[0091] In yet another example, the back end server(s) 420 may include a conference blasting server for instructing a conference bridge in the voice network 106 to dial out via an SSP to the participants of a voice conference. Alternatively, for example, the back end server(s) 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. The back end server(s) 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.
[0092] In yet another example, the back end server(s) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a Short Message Service (SMS) gateway in the voice network 104. This may be used to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the users choosing.
[0093] The voice network plane 508 includes the hardware and software included in the voice network 104, as discussed above with reference to FIG. 3. For example, the voice network plane 508 may include the ISCP SPACE 314, the ISCP 302, the intelligent peripherals 320, and the SSP
308. Additionally, the 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.
[0094] FIG. 6 shows an exemplary network access server 410 consistent with the present invention. As noted above in conjunction with FIGS. 4 and 5, network access server 410 may include functionality that enables real-time call management. Real-time call management (RTCM) server 602 may be used to perform this functionality. For example, RTCM server 602 may facilitate call management by receiving information indicative of an incoming call from an ISCP 302, forwarding a request related to that information to digital companion server 406, receiving a response to the request, and causing the ISCP
302 to connect the call based on the response. One of ordinary skill in the art will recognize that other functionality may also be included in a network access server 410 in addition to RTCM server 602.
[0095] FIG. 7 shows an exemplary application server 516 consistent with the present invention. As noted above in conjunction with FIG. 5, application server 516 may include functionality that facilitates real-time call management. RTCM application 702 may be used to perform this functionality. For example, RTCM application 702 may facilitate call management by receiving a request corresponding to an incoming call, looking up customer-specific information, and providing information to a notification server that may notify a customer of an incoming call and present the customer with several options on handling the call. One of ordinary skill in the art will recognize that other functionality may also be included in an application server 516 in addition to RTCM application 702. One of ordinary skill in the art will also recognize that RTCM application 702 may be located in application server 528 instead of or in addition to application 516.
Real-Time Call Management [0096] FIG. 8 is a diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention. Although the steps of the flowchart are described in a particular order, one skilled in the art will appreciate that these steps may be performed in a modified or different order. Further, one or more of the steps in FIG. 8 may be performed concurrently or in parallel.
[0097] As illustrated in FIG. 8, a calling party first initiates a call to a digital companion customer (step 802). For example, calling party 120 may use a phone, such as phone 122, to call a digital companion customer, such as user 110. In response to the initiation of a call, service center 106 may send a notification of the incoming call to the customer at a communications device (step 804). The notification may present a number of customer-selectable options associated with it that enable the customer to manage a call in real-time. For example, the notification may present different options that permit a customer to send a call to voice mail, send a call received on one device to another device, perform a call screening operation, accept a call, play an announcement, place a call on hold, schedule a call back operation, perform an automatic call back operation, or bridge the caller onto the current call. Once the customer selects one of the call management options (e.g., by pressing an appropriate button on a touch-sensitive display), service center 106 causes the call to be connected based on the customer's response to the notification (step 806).
[0098] FIGS. 9A and 9B comprise an expanded diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention.
Although the steps of the flowchart are described in a particular order, one skilled in the art will appreciate that these steps may be performed in a modified or different order. Further, one or more of the steps in FIG. 9 may be performed concurrently or in parallel.
[0099] As illustrated in FIGS. 9A and 9B, a calling party first initiates a call to a digital companion customer (step 902). For example, calling party 120 may use a phone, such as phone 122, to call a digital companion customer, such as user 110. In one embodiment, the call may be routed from a phone to a voice network, such as voice network 104, where an SSP 308 or 310 may intercept the call (step 904).
The SSP 308 or 310 may intercept the call because it encountered a trigger, such as a terminating attempt trigger or a specific digit string trigger, associated with the call.
For example, a trigger may be set at SSP 308 or 310 on each of the lines corresponding to a digital companion customer. In this manner, a trigger is set to detect calls received at the SSP that are directed to telephone numbers of digital companion customers. In addition, triggers may be set on lines corresponding to digital companion customers that have the real-time call management feature enabled.
As such, calls to telephone numbers associated with digital companion customers having real-time call management are detected by the triggers. For the purposes of this description, it is those calls that the SSP intercepts. In an alternative environment, such as a soft switch environment, functionality similar to a trigger may be utilized to intercept calls.
[0100] After intercepting the call, SSP 308 or 310 sends a query to ISCP 302 requesting further instructions. In response, ISCP 302 sends call information to a network access server 410 (step 906).
More particularly, ISCP 302 may send call information to RTCM server 602. In one embodiment, the call information may be sent to network access server 410 via a Generic Data Interface (GDI), using a message structure associated with GDI (e.g., GetData, SendData, or InvokeApp).
The call information sent to RTCM server 602 may also be sent in an encrypted form.
[0101] The call information may include, for example, call state data, a call intercept parameter, a voice mail parameter, time zone data, user ID, called number data, calling name data, calling number data, and calling party number (CPN) presentation information. One of ordinary skill in the art will appreciate that additional information may be included with the call information, or that some of the previously noted information may be omitted from the call information.
[0102] Call state data may provide the current call state based on processing (e.g., AIN processing) that has already occurred for the call. For example, some possible values for call state data may be indicative of a call being authorized for termination, a call being to a call intercept (CI) service node or IP, a call being from a Cl service node or IP, a call being a priority call from the Cl service node or IP, a call having a Cl error encountered on a call to a CI service node or IP, or a call being on the first leg of a click-to-dial call.
[0103] The call intercept parameter identifies when a customer has call intercept. In one embodiment, a call intercept feature allows a customer to stop invalid numbers that typically appear as "unavailable,"
"private," "anonymous," or "out of area" on a caller ID display. The feature may tell callers that unidentified calls are not accepted and ask them to record a name. If an unidentified caller does not record a name or enter an override code, the called party's phone will not ring, thus eliminating interruptions from unidentified callers.
[0104] The voice mail parameter identifies when a subscriber has voice mail capability. Time zone data refers to the customer's time zone. Called number data refers to the number of a called device associated with the subscriber. User ID refers to a parameter that may have one of two values. If a distinctive ring feature is present, then user ID is set to a primary number value. If no such feature is present, then user ID is set to the same value as the called number.
Distinctive ring, for example, may provide a customer with additional telephone numbers on a single line, with their own unique ringing pattern. A customer's primary number is the main number associated with the line.
[0105] Calling number data refers to the number of the caller. This parameter may contain such a number when it is available. In addition, the parameter may contain a calling party address when the information is made available by a previously executed AIN service. Otherwise, the calling number parameter may include some arbitrary string of digits or characters (e.g., ten zeros) when the caller ID
information does or does not match a particular format.
[0106] Calling name data refers to the name of the calling party. This parameter may be retrieved, for example, by ISCP 302 from a database such as LIDB 312. It may be typically possible to retrieve the calling name when the database was populated with this data by a previously executed AIN service. If the calling name is not successfully retrieved, then the calling name parameter may include, for example, an arbitrary string of digits or characters (e.g., zeros) indicative of situations where there was no response from LIDB 312, there was an erroneous response from LIDB 312, there was no name returned from LIDB 312, the format of the caller ID is not in conformance, or the caller ID presentation is restricted.
[0107] ISCP 302 also sends an announcement to an SSP where the call is being handled. The announcement can be some kind of recording that is played for the calling party. This announcement has the effects of preventing a call timer in the SSP from expiring and giving the calling party an indication that the call is progressing. The ISCP 302 may continue to cause the announcement to be played while waiting for a response from the RTCM server 602.
[0108] Upon receiving the call information from the ISCP 302, the RTCM server 602 may decrypt the information, if necessary, and forward the received information to application server 516 (step 908). For example, the RTCM server 602 may dispatch the received call information to RTCM application 702. The RTCM application 702 may then determine whether the customer associated with the triggered phone number (e.g., destination/dialed phone number) is logged into the digital companion system (step 910).
RTCM application 702 makes this determination, for example, by performing a lookup in a database, such as database 522, using the called number as an index. Based on the called number, RTCM
application 702 can determine a digital companion customer ID. This digital companion customer ID may have a number of access points (e.g., user terminals 112) associated with it.
RTCM application 702 may lookup entries in database 522 that correspond to the digital companion customer ID to determine whether the customer is currently logged onto the system using any access points. For example, whenever a customer is logged onto the system using an access point, an indication of such is stored in database 522. If RTCM application 702 finds such an indication in database 522, then it knows that the customer is logged on, and it knows which access point the customer is using.
[0109] If the customer is not logged on anywhere, then there is no way for service center 106 to communicate with the customer using digital companion operations. Instead, service center 106 logs the call (step 912). When the customer logs in at a later time, the customer is provided with an indication that the customer was called. Calls may be logged, for example, in database 522 or in other storage on digital companion server 406 or communication portal server 408.
The call may be subsequently routed without digital companion processing (e.g., call may be completed as dialed, if possible) (step 914).
[0110] If the customer is logged on, then RTCM application 702 retrieves call preference information from a database (step 920). In one embodiment, the database storing this call preference information may be database 522, customer profile database 532, or another database used to stored customer-related data. The call preference information may include, for example, call block lists, lists of forwarding devices or telephone numbers, voice mail preferences, lists of recordings that the customer can set as pre-recorded messages, etc.
[0111] RTCM application 702 may also proceed to determine whether the call intercept feature and/or voice mail features are enabled for the called party by examining the call information received from the RTCM server 602 (step 922). RTCM application 702 makes this determination so that it knows which options should be made available to a called party using RTCM. One of ordinary skill in the art will appreciate that the RTCM application 702 may also check for any other feature that can be enabled and disabled (e.g., call screening). RTCM application 702 also determines the CPN
presentation value associated with the call by examining the call information received from the RTCM server 602 (step 924). The CPN presentation value is determined so that the calling party's CPN
information can either be displayed or not displayed for the customer.
[0112] Thereafter, RTCM application 702 may provide the collected information (e.g., call information, call preference information, and access point information) to notification server 520 and instruct notification server 520 to send an RTCM notification to the customer associated with the called number (e.g., by providing an indication of the access point that the customer is using to the notification server 520). Notification server 520 has open connections to all devices (e.g., user terminals 112) that are logged on. When notification server 520 receives information from RTCM
application 702, it uses the information to route an RTCM notification to the customer at the appropriate access point (step 926). In one embodiment, the RTCM notification may be sent using a protocol such as HTTP (Hypertext Transfer Protocol), Java, or a similar protocol.
[0113] As noted above with reference to FIG. 8, the RTCM notification may be a notification of the incoming call to the customer. The notification may include a display having a number of customer-selectable buttons associated with it that enable the customer to manage a call in real-time. For example, the notification may have different buttons that permit a customer to send a call to voice mail, send a call received on one device to another device, perform a call screening operation, accept a call, play an announcement, place a call on hold, schedule a call back operation, perform an automatic call back operation, perform a call block operation, or bridge a caller onto the current call (e.g., initiate a conference call).
[0114] The notification may provide the customer with different options dependent on the features for which the customer is authorized and has enabled. For example, if the customer does not have call intercept enabled, then the RTCM notification will not include a user-selectable area corresponding to the telemarketer zap operation. If the customer does not have voice mail enabled, then the RTCM
notification will not include a user-selectable area corresponding to voice mail. One of ordinary skill in the art will appreciate that any feature that can be enabled and disabled may be used as a basis for altering the RTCM notification (e.g., call screening, conference call, etc.).
[0115] Once it has received the RTCM notification, the customer's selected device displays the RTCM
notification, including the customer-selectable buttons associated with it.
The device does not yet ring.
Even though the device is not yet ringing, the caller may hear on the calling device (e.g., the phone or other device used to place the call) a ringing tone or an announcement indicating that the call is proceeding. RTCM server 602 then waits for a response from the customer (step 928). Response information may include, for example, call disposition information, forwarding number information, nature of forwarding number information, carrier access code, announcement type, and ring cadence.
One of ordinary skill in the art will appreciate that additional data may be included with the response data, or that some of the previously noted data may be omitted from the response data.
[0116] Call disposition information may provide an indication of the customer's choice for how the call should be handled. For example, call disposition information may include an indication of sending a call to voice mail, sending a call received on one device to another device (e.g., call forwarding), performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, or bridging a caller onto the current call.
[0117] When a call forwarding operation is invoked, forwarding number information includes a number to which the call should be forwarded. Nature of forwarding number information identifies the nature of the call forwarding number. For example, a number may be a national number or an international number.
[0118] Carrier access code may be a sequence of digits indicative of a specific carrier when a call should be routed using the specific carrier.
[0119] Announcement type identifies an announcement that should be played to the caller. This parameter, for example, may be used when the customer selects the play announcement option.
[0120] Ring cadence may be indicative of the ring cadence value that should be applied for the call. For example, different values may be used to designate normal cadence; short, short cadence; and short, short, long cadence; or any other possible cadences.
[0121] If, after a predetermined period of time, the notification server 520 has not received a response, then the call is accepted for the device receiving the RTCM notification (step 930). For example, after the period of time, the RTCM notification may disappear from the device's display and the device may start ringing. The customer may answer the call if he or she is available and chooses to do so. One of ordinary skill in the art will appreciate that other default actions may occur instead of allowing the call to go through. For example, a busy signal may be played, the call may be sent to voice mail, the call may be forwarded to a preferred forwarding number, an announcement may be played, etc.
[0122] If the customer responds by selecting one of the RTCM options, then the RTCM notification disappears from the display, and the RTCM server 602 receives the response and encrypts it, if necessary (step 932). RTCM server 602 proceeds to instruct ISCP 302 to route the incoming call based on the response from the customer (step 934). In one embodiment, RTCM server 602 instructs ISCP 302 by sending ISCP 302 the response information via a connection such as a GDI link.
The ISCP 302 may decrypt the response data, if necessary, and route the call based on the response. For example, the service logic associated with ISCP 302 may take different actions based on the call disposition information and other information included in the response. Exemplary call routing options include place call on hold (step 936), forward call to another device (step 938), screen call (step 940), voice mail (step 942), accept call (step 944), play announcement (step 946), schedule call back (step 948), auto call back (step 950), conference call (step 952), and block call (step 954).
[0123] Selecting the place call on hold option (step 936) temporarily causes the call to be delayed until the customer is ready to speak or otherwise deal with the call. For example, when the caller is placed on hold, an announcement may be played for the caller (e.g., "The party you are trying to reach is currently on a call, but wishes to talk with you. Please stay on the line.") The popup may remain on the screen in this case and display the time elapsed since placing the caller on hold.
[0124] If a customer decides to forward the call to another device (step 938), then RTCM server 602 instructs ISCP 302 to route the call to a device other than the one on which the RTCM notification was received. In one embodiment, the customer may preset the phone number of the device to which the call should be forwarded. This device may be one of a plurality of devices that are normally associated with the customer (e.g., part of a list of devices stored in a digital companion database). The device may also be a device that is not one of the customer's normal potential preferred devices, but the customer has some reason that he or she wants to receive calls on the device (e.g., the device is physically close to the customer's temporary location, etc.).
[0125] In an alternative embodiment, upon selecting the forward call option, the customer may be presented with a query asking what number the call should be forwarded to. The customer may respond to the query by entering a phone number or selecting a number from a list of predetermined numbers.
[0126] When the call screening option (step 940) is selected, the RTCM server 602 causes a series of steps to occur for screening potential telemarketers or other unwanted callers. For example, when the RTCM notification indicates that the call is from a blocked, unavailable, or otherwise undesirable number, the customer may select the call screening option. The calling party may then be presented with an announcement requesting the calling party to leave a spoken name, a PIN (personal identification number), or a voice message. In one embodiment, the announcement may be accompanied by a Special Instruction Tone (SIT) cadence.
[0127] If the calling party leaves a name, the customer's device may then ring. The ring may be accompanied by a notification that gives the customer the option of taking the call, diverting the call to voice mail, deny the call, etc. The customer's device that rings may be preset or manually provided by the customer in response to a query. The device may also be whatever device originally received the RTCM notification. The call is routed according to the customer's selection.
If the calling party enters a valid PIN, the calling party's call may be connected to the customer right away.
[0128] When the voice mail option is selected (step 942), the RTCM server 602 may instruct ISCP 302 to route the call to the customer's current preferred voice mail number. The preferred voice mail number may be preset or manually provided by the customer in response to a query. For example, when the customer selects the send to voice mail option, the popup (e.g., RTCM
notification) goes away and the incoming call is sent to either a present voice mail box or a voice mail box provided by the customer in response to a query given to the customer after the popup went away.
[0129] When the accept call option is selected (step 944), the RTCM server 602 may instruct ISCP 302 to route the call to the device on which the customer received the RTCM
notification. If the customer is connected to the Internet via dial-up access on the same phone line that the call is to be routed, the customer's Internet session may be immediately disconnected so that the call may be answered.
[0130] In cases where the play announcement option (step 946) is selected, the RTCM server 602 may instruct ISCP 302 to cause a predetermined recorded announcement to be played for the calling party.
For example, the customer may wish to tell particular callers that he or she is not available, without giving them the option of leaving a voice message. One of ordinary skill in the art will recognize that other announcements may be played.
[0131] When the schedule call back option is selected (step 948), the RTCM
server 602 may instruct ISCP
302 to cause an announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach is currently on a call but will call you back later." The RTCM server may also cause a prompt to be presented to the customer asking for the customer to set up a callback event in the digital companion calendar. This callback event may, with the customer's approval, send an e-mail or other message to the caller showing the intended date and time of the callback, if the caller is also a digital companion customer or has an e-mail address or other device indicator (e.g., phone number of a mobile phone capable of receiving text messages) in a contacts list associated with the called customer. When the time and date of the callback occur, a call may be automatically placed from the called customer to the calling party.
[0132] When the auto call back option is selected (step 950), the RTCM server 602 may instruct ISCP 302 to cause an announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach is currently on a call but will call you back as soon as that call is finished." When the customer's line is free (e.g., the customer is done with the previous call), a call may be automatically placed from the customer to the calling party.
[0133] When the conference call option is selected (step 952), the RTCM server may instruct ISCP 302 to cause the calling party to be bridged onto the current call. For example, the called customer may be on a telephone call with a first party when a second party calls the customer. If the customer selects the conference call option, the a RTCM server 602 instructs ISCP 302 to create a conference call between the customer, the first party, and the second party. For example, in response to a request from RTCM
server 602, ISCP 302 may instruct a switch handling the existing call between the customer and the first party to bridge the incoming call from the second party with the existing call. One of ordinary skill in the art will appreciate that the calling party can be bridged onto a conference call between the customer and multiple other parties instead of bridged onto a normal call between the customer and one other party.
[0134] When the block call option is selected (step 954), the RTCM server 602 may instruct ISCP 302 to cause a predetermined recorded announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach does not wish to speak to you." The calling party's number may also optionally be added to a call block list of numbers with which the customer does not wish to speak.
[0135] FIG. 10 is a diagram of an exemplary user interface 1000 including customer-selectable real-time call management options. User interface 1000 may be a display on a customer device, such as user terminal 112 or phone 114, that is currently showing an RTCM notification. The RTCM notification includes an area 1002 indicating that the customer has an incoming call. Area 1002 also provides an identification of the caller as well as the number being called. The number being called may belong to the device displaying the RTCM notification or another device. The RTCM has a number of user-selectable areas 1004-1022 associated with it, allowing the customer to decide how an incoming call is routed. In one embodiment, the customer may select one of these user-selectable areas through any suitable input methods. For example, the customer may click on the desired option using a mouse, touch an appropriate area of a touchscreen, enter input on a keypad, etc., in order to choose the manner in which the incoming call is routed.
[0136] Selecting area 1004 enables the customer to answer the call on the device that received the RTCM notification (e.g., the device the includes user interface 1000).
Selecting area 1006 forwards the call the voice mail as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1008 initiates a call screening feature as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1010 places the call on hold as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1012 forwards the call to another device of the customer's choosing as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1014 plays an announcement for the calling party as discussed above with reference to FIGS. 9A and 9B. Selecting area 1016 enables a customer to schedule a call back event on a calendar as discussed above with reference to FIGS. 9A and 9B. Selecting area 1018 enables a customer to cause the calling party to be automatically called back after the current call as discussed above with reference to FIGS. 9A and 9B. Selecting area 1020 bridges call party onto the current call as discussed above with reference to FIGS. 9A and 9B. Selecting area 1022 cause a recording to be played indicating that the customer does not wish to speak to the calling party and optionally cause the calling party's telephone number to be added to a call block list, as discussed above with reference to FIGS. 9A and 9B.
[0137] FIG. 11 is a diagram of an exemplary user interface 1100 that enables a customer to change preferences consistent with the present invention. As illustrated in FIG. 11, a customer may have the ability to enable or disable real-time call management for a given device. The customer also may select particular devices to handle different actions. For example, a customer may set specific phone numbers to handle features such as answer calls, send to voice mail, forward call, and/or telemarketer zap (e.g., call screening). One of ordinary skill in the art will appreciate that other features may also have phone numbers set for them. The customer also has the option of viewing various other settings associated with the customer, such as a list of numbers that are call blocked, call back settings, etc.
[0138] While the present invention has been described in connection with various embodiments, many modifications will be readily apparent to those skilled in the art. One skilled in the art will also appreciate that all or part of the systems and methods consistent with the present invention may be stored on or read from computer-readable media, such as secondary storage devices, like hard disks, floppy disks, and CD-ROM; a carrier wave received from a network such as the Internet; or other forms of ROM or RAM. Accordingly, embodiments of the invention are not limited to the above described embodiments and examples, but instead is defined by the appended claims in light of their full scope of equivalents.
Accordingly, there is a need for a method and system for a method and system for managing calls in real-time with user intervention.
SUMMARY OF THE INVENTION
[0010] Methods and systems consistent with the principles of the invention manage a call. A service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also sends a notification of the call to a device associated with the customer and receives a response to the notification from the customer. Thereafter, the service center instructs the service control point to connect the call based on the response.
[0011] Other methods and systems consistent with the principles of the invention also manage a call. A
service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also retrieves data corresponding to the customer using the information pertaining to the call, sends a notification of the call to a device associated with the customer, and receives a response to the notification from the customer. Thereafter, the service center instructs the service control point to connect the call based on the response.
[0012] Other methods and systems consistent with the principles of the invention manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user.
The service center also sends a notification of the call to a first device associated with the user and receives a response to the notification from the user. Thereafter, a service control point forwards the call to a second device based on the response. The user provides a telephone number for the second device.
[0013] Other methods and systems consistent with the principles of the invention also manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user. The service center also retrieves data corresponding to the user using the information pertaining to the call and selects a device associated with the user to receive a notification of the call based on the retrieved data corresponding to the user. Additionally, the service center provides the notification to the selected device for display on the selected device and receives a response to the notification from the user. Thereafter, a service control point initiates a call screening process based on the response.
[0014] Other methods and systems consistent with the principles of the invention also manage a call. A
service center receives information pertaining to a call to a customer from a service control point, the service control point being operable to determine how a call is connected. The service center also retrieves data corresponding to the customer using the information pertaining to the call, determines features enabled for the customer based on the information pertaining to the call, selects a device associated with the customer to receive a notification of the call based on the retrieved data, provides the notification to the selected device, and receives a response to the notification from the customer.
Thereafter, the service center instructs the service control point to connect the call based on the response.
[0015] Other methods and systems consistent with the principles of the invention also manage a call. A
device associated with a customer receives a notification of a call to the customer, wherein the device is determined based on retrieved data corresponding to the customer and the retrieved data was retrieved using information pertaining to the call. The device also receives input from the customer indicative of a response to the notification and sends response information to a server reflective of the response to the notification. Thereafter, the server instructs a service control point to connect the call based on the response to the notification.
[0016] Other methods and systems consistent with the principles of the invention also manage a call. A
service control point sends information to a service center pertaining to a call to a customer. The service center is operable to retrieve data corresponding to the customer using the information pertaining to the call; send a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, and the device is one of a plurality of devices associated with the customer; and provide response information reflective of a response to the notification from the customer. The service control point receives the response information from the service center and connects the call based on the response information.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one embodiment of the invention and, together with the description, serve to explain the principles of the invention.
[0018] 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;
[0019] FIG. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[0020] FIG. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[0021] FIG. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[0022] FIG. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[0023] FIG. 6 is a diagram of an exemplary network access server consistent with the principles of the present invention;
[0024] FIG. 7 is a diagram of an exemplary application server consistent with the principles of the present invention;
[0025] FIG. 8 is a diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention;
[0026] FIGS. 9A and 9B comprise another diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention;
[0027] FIG. 10 is a diagram of an exemplary user interface including customer-selectable real-time call management options consistent with the present invention; and [0028] FIG. 11 is a diagram of an exemplary user interface that enables a customer to change preferences consistent with the present invention.
DETAILED DESCRIPTION
[0029] 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 drawings to refer to the same or like parts. While the description includes exemplary embodiments, other embodiments are possible, and changes may be made to the embodiments described without departing from the spirit and scope of the invention. The following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and their equivalents.
Overview [0030] Methods and systems consistent with the present invention manage a call in real-time based on input from a user. A service center receives information pertaining to a call to the user from a service control point. The service center also retrieves data corresponding to the user using the information pertaining to the call and sends a notification of the call to a device associated with the user. The device is determined based on the retrieved data. Based on a response to the notification from the user, the service center instructs the service control point to connect the call by providing the service control point with response information reflective of the response. The service control point thereafter receives the response information from the service center and connects the call based on the response information.
Network Environment [0031] 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 anyone of phones 114, 116, and 118.
[0032] 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.
[0033] 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 on a voice over broadband network, such as a network using voice-over Internet Protocol ("VoIP") technology. Additionally, in other embodiments, the voice network may be a video over broadband network, such as, for example, a network for providing 2-way video communications. In another example, the voice network may be a wireless broadband network, such as, for example, a network using WiFi (i.e., IEEE 802.11 (b) and/or (g)). In yet another example, the voice network 104 may be a wireless voice network(s), such as, for example, a cellular or third-generation cellular network). In addition, voice network 104 may be implemented using any single or combination of the above-described technologies 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's.TM.
Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[0034] 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 conversions, 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.
[0035] 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 Blackberry.TM., and Ergo Audrey.TM..
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.
[0036] 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").
[0037] 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 terminal 112 may communicate with service center 106 via a proxy.
[0038] 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.
[0039] FIG. 2 is a block diagram of a user terminal consistent with the present invention. User terminal 112 may include 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.
[0040] 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 Pentium.TM. processor provided from Intel Corporation.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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) 304 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, an Intelligent Peripheral (IP) 320, and a switch access 322. Although this embodiment of a voice network 104 is described as a PSTN, as discussed above in other embodiments, the voice network 104 may be, for example, a voice or video over broadband network a wireless broadband, a wireless voice network, etc.
[0048] 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.
[0049] ISCP 302 may also be, for example, a standard service control point (SCP), an Advanced Intelligent Network (AIN) SCP, a soft switch, or any other network call controller. 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 include service logic used to provide a switch, such as SSP 308 or 310, with specific call processing instructions. ISCP 302 may also store data related to various features that a user may activate. Such features may include, for example, call intercept and voice mail. ISCP 302 may be implemented using a combination of known hardware and software. ISCP 302 is shown with a direct connection to service center 106 and a connection to ISCP SPACE 314, however, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP
302, ISCP SPACE 314, and service center 106. Further, information exchanged between the ISCP 302 and service center 106 may use, for example, the SR-3389 General Data Interface (GDI) for TCP/IP.
[0050] 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 304 or 306 may be implemented using known hardware and software from manufacturers such as NORTEL.TM. and LUCENT
Technologies.TM..
[0051] 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.
[0052] 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.
Although, in this figure, LIDB
312 is illustrated as directly connected to ISCP 302, LIDB 312 may be connected to ISCP 302 through an STP (e.g., 304 and 306). Additionally, this communication link may use, for example, the GR-2838 General Dynamic Interface (GDI) for SS7.
[0053] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of the ISCP 302 or be separate from the ISCP 302. For example, the Telcordia.TM. 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.
[0054] In one embodiment, customer records may be stored in the ISCP SPACE 314 such that the records may be updated and sent to the 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, and/or 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).
[0055] Additionally, the 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 MIS 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 the ISCP SPACE 314, which then propagates the instructions to the ISCP 302 as discussed above. Further, an MSP or eRC may be used, for example, for providing updates to both the SSPs 308 or 310 and the ISCPs 302. Or, for example, an eRC may be used for providing updates to the SSPs 308 or 310, while an AAIS is used for providing updates to the ISCPs 302.
[0056] Updates sent to the SSPs 308 or 310 may be sent from the recent change engine 316 via a switch access 322 that may, for example, convert the updates into the appropriate protocol for the SSP 308 or 310. For example, recent change engine 316 may send updates to the SSPs 308 or 310 via TCP/IP. The switch access 322 may then convert the updates from TCP/IP to X.25. This switch access 322 may be implemented using hardware and/or software. These connections may include any number of elements, such as, for example, switches, routers, hubs, etc. and may be, for example, an internal data network for the voice network 104.
[0057] The voice network 104 may also include one or more intelligent peripherals (IP). For example, in FIG. 3, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing functions for interaction between users and the voice network, such as voice mail services, digit collection, customized announcements, voice recognition, etc. Moreover, the communications between the SSP 308 and IP 320 may use the Primary Rate interface (PRi) (e.g., the 1129 protocol) protocol.
Additionally, the IP 320 may be capable of sending and receiving information to/from the Service Center 106. These communications may use, for example, the SR-3511 protocol. Further, although FIG. 3 illustrates this connection as a direct connection, this connection may include any number of elements including routers, switches, hubs, etc., and may be via, for example, an internal data network for the voice network 104.
[0058] 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. The 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 server(s) 420 may be provided between the service center 106 and the voice network 104.
[0059] 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 appropriate 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.
[0060] 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 the network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[0061] Each server (406, 408, 410, 414, 416, 420) may be any appropriate 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.
[0062] 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, real-time call management, etc. In one embodiment, real-time call management enables a user to perform several functions as a call is being received, such as sending a call to voice mail, sending a call received on one device to another device, manually initiating protection from telemarketers, playing an announcement for the caller, scheduling a call back, bridging a caller onto a current call, etc.
[0063] 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. The network access servers 410 may provide the hardware and software for sending and receiving information to the voice network 104 in processing the applications provided by the service center. For example, the 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 the voice network 104.
[0064] The 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 the voice portal 412.
Then the customer using speech may instruct the service center 105 to modify the services to which the customer subscribes. The voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. The voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. The application function 414 may take, for example, the output from the voice recognition function 416, convert it to a format suitable for the service center 106 and forward the information to one or more servers (406, 408, 410) in the service center 106.
[0065] 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 502, application service 504, network access 506, and the voice network 508.
[0066] Client side 502 includes user terminals 112_A and 112_6 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 phone(s) 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 the Service Center 106, while user terminal 112_6 may be a desktop type computer running a web browser for communicating with the 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.
[0067] The application service plane 504 includes the digital companion server(s) 406, communication portal server(s) 408, and the 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.
[0068] 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.
[0069] The 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 the data network 102 go through the client proxy 512. Also, if the client proxy 512 is included on a separate server, for example, an additional firewall may be provided between the client proxy 512 and the other digital companion servers to provide additional security.
[0070] Web server 514 provides functionality for receiving traffic over the 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.
[0071] Application server function 516 encompasses the general functions performed by the digital companion server(s) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific services 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, enabling call management with user intervention in real-time, etc.
[0072] Additionally, the 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, the 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.).
[0073] 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.
[0074] Notification server function 520 provides the capability to send information from the service center 106 to a user terminal 112. For example, the notification server function 520 at the direction of the application server function 516 may send a notification to the user terminal 112 that the user is presently receiving a phone call at the user's phone 114. This notification may be, for example, an instant message pop-up window that provides an identification of the caller as well as the number being called. The notification may also have a number of user-selectable buttons or items associated with it that enable the user to manage a call in real-time.
[0075] 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 the database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[0076] As discussed above, the communication portal server(s) 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.
[0077] Web server function 526, as with web server function 514 of the digital companion servers, provides functionality for receiving traffic over the 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.
[0078] The application server function 528 encompasses the general functions performed by the 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, the application server function 528 may include the functionality of sending and/or receiving information to/from external servers and/or devices.
For example, the communication portal servers 408 may be connected to a network, such as, the Internet. The application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages web page. The application server 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.
[0079] In another example, the application server function 528 of the 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.
[0080] Moreover, the application server function 528, similar to application server 516, may provide functionality to facilitate services performed 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, enabling call management with user intervention in real-time, etc.
[0081] The contacts database 530 includes storage devices for storing an address book for the user. This address book may be any appropriate type of address book. For example, the user's address book may include the names, phone numbers, and addresses of people and/or organizations. These storage devices may be internal or external to the communication portal servers 406 or some combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[0082] The 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.
[0083] The application services plane 504 of the architecture may also include a voice portal 412. As discussed above, the 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.
The application server function 414 of the voice portal 412 may include hardware and/or software for exchanging information between the digital companion servers 406 and the voice recognition function 416. Additionally, the application server function 414 may be included on a separate server, included in the hardware and software providing the voice recognition function 416, included in the digital companion servers 406, etc.
[0084] The Network Access plane 506 of the architecture includes the functions for providing connectivity between the application service plane 502 and the voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[0085] As discussed above, recent change engines 316 may be used to update switches and ISCP
databases included in the voice network 104. In one embodiment, the 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 the digital companion servers 406 and the recent change engines 542 for security purposes.
[0086] The 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 the voice network 410 in processing the applications provided by the service center. For example, the network access servers 410 may include a Caller ID (CID) functionality for retrieving caller ID information from the 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.
[0087] Network Access plane 506 may also include one or more back end server(s) 420. These back end server(s) 420 may include hardware and/or software for interfacing the service center 106 and the voice network 104. The back end server(s) 420 may be connected to the service center 106 by a network, by a direct connection, or in any other suitable manner. Further, the back end server(s) 420 may connect to one or more devices in the voice network 104 by a network, a direct connection, or in any other suitable manner.
[0088] The back end server(s) 420 may include, for example, a server providing a voice mail retrieval and notification function. 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 the digital companion servers 406.
[0089] Additionally, these back end server(s) 420 may also include, for example, a directory assistance server. This directory assistance server may interface the service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of the voice network 104. An RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of the 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.
[0090] In another example, the back end server(s) 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 server(s) 420, this wireless internet gateway may be used for converting requests and information between the formats used by the service center 106 and those used by the wireless voice network.
[0091] In yet another example, the back end server(s) 420 may include a conference blasting server for instructing a conference bridge in the voice network 106 to dial out via an SSP to the participants of a voice conference. Alternatively, for example, the back end server(s) 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. The back end server(s) 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.
[0092] In yet another example, the back end server(s) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a Short Message Service (SMS) gateway in the voice network 104. This may be used to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the users choosing.
[0093] The voice network plane 508 includes the hardware and software included in the voice network 104, as discussed above with reference to FIG. 3. For example, the voice network plane 508 may include the ISCP SPACE 314, the ISCP 302, the intelligent peripherals 320, and the SSP
308. Additionally, the 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.
[0094] FIG. 6 shows an exemplary network access server 410 consistent with the present invention. As noted above in conjunction with FIGS. 4 and 5, network access server 410 may include functionality that enables real-time call management. Real-time call management (RTCM) server 602 may be used to perform this functionality. For example, RTCM server 602 may facilitate call management by receiving information indicative of an incoming call from an ISCP 302, forwarding a request related to that information to digital companion server 406, receiving a response to the request, and causing the ISCP
302 to connect the call based on the response. One of ordinary skill in the art will recognize that other functionality may also be included in a network access server 410 in addition to RTCM server 602.
[0095] FIG. 7 shows an exemplary application server 516 consistent with the present invention. As noted above in conjunction with FIG. 5, application server 516 may include functionality that facilitates real-time call management. RTCM application 702 may be used to perform this functionality. For example, RTCM application 702 may facilitate call management by receiving a request corresponding to an incoming call, looking up customer-specific information, and providing information to a notification server that may notify a customer of an incoming call and present the customer with several options on handling the call. One of ordinary skill in the art will recognize that other functionality may also be included in an application server 516 in addition to RTCM application 702. One of ordinary skill in the art will also recognize that RTCM application 702 may be located in application server 528 instead of or in addition to application 516.
Real-Time Call Management [0096] FIG. 8 is a diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention. Although the steps of the flowchart are described in a particular order, one skilled in the art will appreciate that these steps may be performed in a modified or different order. Further, one or more of the steps in FIG. 8 may be performed concurrently or in parallel.
[0097] As illustrated in FIG. 8, a calling party first initiates a call to a digital companion customer (step 802). For example, calling party 120 may use a phone, such as phone 122, to call a digital companion customer, such as user 110. In response to the initiation of a call, service center 106 may send a notification of the incoming call to the customer at a communications device (step 804). The notification may present a number of customer-selectable options associated with it that enable the customer to manage a call in real-time. For example, the notification may present different options that permit a customer to send a call to voice mail, send a call received on one device to another device, perform a call screening operation, accept a call, play an announcement, place a call on hold, schedule a call back operation, perform an automatic call back operation, or bridge the caller onto the current call. Once the customer selects one of the call management options (e.g., by pressing an appropriate button on a touch-sensitive display), service center 106 causes the call to be connected based on the customer's response to the notification (step 806).
[0098] FIGS. 9A and 9B comprise an expanded diagram of an exemplary flowchart of a method for real-time call management in a manner consistent with the present invention.
Although the steps of the flowchart are described in a particular order, one skilled in the art will appreciate that these steps may be performed in a modified or different order. Further, one or more of the steps in FIG. 9 may be performed concurrently or in parallel.
[0099] As illustrated in FIGS. 9A and 9B, a calling party first initiates a call to a digital companion customer (step 902). For example, calling party 120 may use a phone, such as phone 122, to call a digital companion customer, such as user 110. In one embodiment, the call may be routed from a phone to a voice network, such as voice network 104, where an SSP 308 or 310 may intercept the call (step 904).
The SSP 308 or 310 may intercept the call because it encountered a trigger, such as a terminating attempt trigger or a specific digit string trigger, associated with the call.
For example, a trigger may be set at SSP 308 or 310 on each of the lines corresponding to a digital companion customer. In this manner, a trigger is set to detect calls received at the SSP that are directed to telephone numbers of digital companion customers. In addition, triggers may be set on lines corresponding to digital companion customers that have the real-time call management feature enabled.
As such, calls to telephone numbers associated with digital companion customers having real-time call management are detected by the triggers. For the purposes of this description, it is those calls that the SSP intercepts. In an alternative environment, such as a soft switch environment, functionality similar to a trigger may be utilized to intercept calls.
[0100] After intercepting the call, SSP 308 or 310 sends a query to ISCP 302 requesting further instructions. In response, ISCP 302 sends call information to a network access server 410 (step 906).
More particularly, ISCP 302 may send call information to RTCM server 602. In one embodiment, the call information may be sent to network access server 410 via a Generic Data Interface (GDI), using a message structure associated with GDI (e.g., GetData, SendData, or InvokeApp).
The call information sent to RTCM server 602 may also be sent in an encrypted form.
[0101] The call information may include, for example, call state data, a call intercept parameter, a voice mail parameter, time zone data, user ID, called number data, calling name data, calling number data, and calling party number (CPN) presentation information. One of ordinary skill in the art will appreciate that additional information may be included with the call information, or that some of the previously noted information may be omitted from the call information.
[0102] Call state data may provide the current call state based on processing (e.g., AIN processing) that has already occurred for the call. For example, some possible values for call state data may be indicative of a call being authorized for termination, a call being to a call intercept (CI) service node or IP, a call being from a Cl service node or IP, a call being a priority call from the Cl service node or IP, a call having a Cl error encountered on a call to a CI service node or IP, or a call being on the first leg of a click-to-dial call.
[0103] The call intercept parameter identifies when a customer has call intercept. In one embodiment, a call intercept feature allows a customer to stop invalid numbers that typically appear as "unavailable,"
"private," "anonymous," or "out of area" on a caller ID display. The feature may tell callers that unidentified calls are not accepted and ask them to record a name. If an unidentified caller does not record a name or enter an override code, the called party's phone will not ring, thus eliminating interruptions from unidentified callers.
[0104] The voice mail parameter identifies when a subscriber has voice mail capability. Time zone data refers to the customer's time zone. Called number data refers to the number of a called device associated with the subscriber. User ID refers to a parameter that may have one of two values. If a distinctive ring feature is present, then user ID is set to a primary number value. If no such feature is present, then user ID is set to the same value as the called number.
Distinctive ring, for example, may provide a customer with additional telephone numbers on a single line, with their own unique ringing pattern. A customer's primary number is the main number associated with the line.
[0105] Calling number data refers to the number of the caller. This parameter may contain such a number when it is available. In addition, the parameter may contain a calling party address when the information is made available by a previously executed AIN service. Otherwise, the calling number parameter may include some arbitrary string of digits or characters (e.g., ten zeros) when the caller ID
information does or does not match a particular format.
[0106] Calling name data refers to the name of the calling party. This parameter may be retrieved, for example, by ISCP 302 from a database such as LIDB 312. It may be typically possible to retrieve the calling name when the database was populated with this data by a previously executed AIN service. If the calling name is not successfully retrieved, then the calling name parameter may include, for example, an arbitrary string of digits or characters (e.g., zeros) indicative of situations where there was no response from LIDB 312, there was an erroneous response from LIDB 312, there was no name returned from LIDB 312, the format of the caller ID is not in conformance, or the caller ID presentation is restricted.
[0107] ISCP 302 also sends an announcement to an SSP where the call is being handled. The announcement can be some kind of recording that is played for the calling party. This announcement has the effects of preventing a call timer in the SSP from expiring and giving the calling party an indication that the call is progressing. The ISCP 302 may continue to cause the announcement to be played while waiting for a response from the RTCM server 602.
[0108] Upon receiving the call information from the ISCP 302, the RTCM server 602 may decrypt the information, if necessary, and forward the received information to application server 516 (step 908). For example, the RTCM server 602 may dispatch the received call information to RTCM application 702. The RTCM application 702 may then determine whether the customer associated with the triggered phone number (e.g., destination/dialed phone number) is logged into the digital companion system (step 910).
RTCM application 702 makes this determination, for example, by performing a lookup in a database, such as database 522, using the called number as an index. Based on the called number, RTCM
application 702 can determine a digital companion customer ID. This digital companion customer ID may have a number of access points (e.g., user terminals 112) associated with it.
RTCM application 702 may lookup entries in database 522 that correspond to the digital companion customer ID to determine whether the customer is currently logged onto the system using any access points. For example, whenever a customer is logged onto the system using an access point, an indication of such is stored in database 522. If RTCM application 702 finds such an indication in database 522, then it knows that the customer is logged on, and it knows which access point the customer is using.
[0109] If the customer is not logged on anywhere, then there is no way for service center 106 to communicate with the customer using digital companion operations. Instead, service center 106 logs the call (step 912). When the customer logs in at a later time, the customer is provided with an indication that the customer was called. Calls may be logged, for example, in database 522 or in other storage on digital companion server 406 or communication portal server 408.
The call may be subsequently routed without digital companion processing (e.g., call may be completed as dialed, if possible) (step 914).
[0110] If the customer is logged on, then RTCM application 702 retrieves call preference information from a database (step 920). In one embodiment, the database storing this call preference information may be database 522, customer profile database 532, or another database used to stored customer-related data. The call preference information may include, for example, call block lists, lists of forwarding devices or telephone numbers, voice mail preferences, lists of recordings that the customer can set as pre-recorded messages, etc.
[0111] RTCM application 702 may also proceed to determine whether the call intercept feature and/or voice mail features are enabled for the called party by examining the call information received from the RTCM server 602 (step 922). RTCM application 702 makes this determination so that it knows which options should be made available to a called party using RTCM. One of ordinary skill in the art will appreciate that the RTCM application 702 may also check for any other feature that can be enabled and disabled (e.g., call screening). RTCM application 702 also determines the CPN
presentation value associated with the call by examining the call information received from the RTCM server 602 (step 924). The CPN presentation value is determined so that the calling party's CPN
information can either be displayed or not displayed for the customer.
[0112] Thereafter, RTCM application 702 may provide the collected information (e.g., call information, call preference information, and access point information) to notification server 520 and instruct notification server 520 to send an RTCM notification to the customer associated with the called number (e.g., by providing an indication of the access point that the customer is using to the notification server 520). Notification server 520 has open connections to all devices (e.g., user terminals 112) that are logged on. When notification server 520 receives information from RTCM
application 702, it uses the information to route an RTCM notification to the customer at the appropriate access point (step 926). In one embodiment, the RTCM notification may be sent using a protocol such as HTTP (Hypertext Transfer Protocol), Java, or a similar protocol.
[0113] As noted above with reference to FIG. 8, the RTCM notification may be a notification of the incoming call to the customer. The notification may include a display having a number of customer-selectable buttons associated with it that enable the customer to manage a call in real-time. For example, the notification may have different buttons that permit a customer to send a call to voice mail, send a call received on one device to another device, perform a call screening operation, accept a call, play an announcement, place a call on hold, schedule a call back operation, perform an automatic call back operation, perform a call block operation, or bridge a caller onto the current call (e.g., initiate a conference call).
[0114] The notification may provide the customer with different options dependent on the features for which the customer is authorized and has enabled. For example, if the customer does not have call intercept enabled, then the RTCM notification will not include a user-selectable area corresponding to the telemarketer zap operation. If the customer does not have voice mail enabled, then the RTCM
notification will not include a user-selectable area corresponding to voice mail. One of ordinary skill in the art will appreciate that any feature that can be enabled and disabled may be used as a basis for altering the RTCM notification (e.g., call screening, conference call, etc.).
[0115] Once it has received the RTCM notification, the customer's selected device displays the RTCM
notification, including the customer-selectable buttons associated with it.
The device does not yet ring.
Even though the device is not yet ringing, the caller may hear on the calling device (e.g., the phone or other device used to place the call) a ringing tone or an announcement indicating that the call is proceeding. RTCM server 602 then waits for a response from the customer (step 928). Response information may include, for example, call disposition information, forwarding number information, nature of forwarding number information, carrier access code, announcement type, and ring cadence.
One of ordinary skill in the art will appreciate that additional data may be included with the response data, or that some of the previously noted data may be omitted from the response data.
[0116] Call disposition information may provide an indication of the customer's choice for how the call should be handled. For example, call disposition information may include an indication of sending a call to voice mail, sending a call received on one device to another device (e.g., call forwarding), performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, or bridging a caller onto the current call.
[0117] When a call forwarding operation is invoked, forwarding number information includes a number to which the call should be forwarded. Nature of forwarding number information identifies the nature of the call forwarding number. For example, a number may be a national number or an international number.
[0118] Carrier access code may be a sequence of digits indicative of a specific carrier when a call should be routed using the specific carrier.
[0119] Announcement type identifies an announcement that should be played to the caller. This parameter, for example, may be used when the customer selects the play announcement option.
[0120] Ring cadence may be indicative of the ring cadence value that should be applied for the call. For example, different values may be used to designate normal cadence; short, short cadence; and short, short, long cadence; or any other possible cadences.
[0121] If, after a predetermined period of time, the notification server 520 has not received a response, then the call is accepted for the device receiving the RTCM notification (step 930). For example, after the period of time, the RTCM notification may disappear from the device's display and the device may start ringing. The customer may answer the call if he or she is available and chooses to do so. One of ordinary skill in the art will appreciate that other default actions may occur instead of allowing the call to go through. For example, a busy signal may be played, the call may be sent to voice mail, the call may be forwarded to a preferred forwarding number, an announcement may be played, etc.
[0122] If the customer responds by selecting one of the RTCM options, then the RTCM notification disappears from the display, and the RTCM server 602 receives the response and encrypts it, if necessary (step 932). RTCM server 602 proceeds to instruct ISCP 302 to route the incoming call based on the response from the customer (step 934). In one embodiment, RTCM server 602 instructs ISCP 302 by sending ISCP 302 the response information via a connection such as a GDI link.
The ISCP 302 may decrypt the response data, if necessary, and route the call based on the response. For example, the service logic associated with ISCP 302 may take different actions based on the call disposition information and other information included in the response. Exemplary call routing options include place call on hold (step 936), forward call to another device (step 938), screen call (step 940), voice mail (step 942), accept call (step 944), play announcement (step 946), schedule call back (step 948), auto call back (step 950), conference call (step 952), and block call (step 954).
[0123] Selecting the place call on hold option (step 936) temporarily causes the call to be delayed until the customer is ready to speak or otherwise deal with the call. For example, when the caller is placed on hold, an announcement may be played for the caller (e.g., "The party you are trying to reach is currently on a call, but wishes to talk with you. Please stay on the line.") The popup may remain on the screen in this case and display the time elapsed since placing the caller on hold.
[0124] If a customer decides to forward the call to another device (step 938), then RTCM server 602 instructs ISCP 302 to route the call to a device other than the one on which the RTCM notification was received. In one embodiment, the customer may preset the phone number of the device to which the call should be forwarded. This device may be one of a plurality of devices that are normally associated with the customer (e.g., part of a list of devices stored in a digital companion database). The device may also be a device that is not one of the customer's normal potential preferred devices, but the customer has some reason that he or she wants to receive calls on the device (e.g., the device is physically close to the customer's temporary location, etc.).
[0125] In an alternative embodiment, upon selecting the forward call option, the customer may be presented with a query asking what number the call should be forwarded to. The customer may respond to the query by entering a phone number or selecting a number from a list of predetermined numbers.
[0126] When the call screening option (step 940) is selected, the RTCM server 602 causes a series of steps to occur for screening potential telemarketers or other unwanted callers. For example, when the RTCM notification indicates that the call is from a blocked, unavailable, or otherwise undesirable number, the customer may select the call screening option. The calling party may then be presented with an announcement requesting the calling party to leave a spoken name, a PIN (personal identification number), or a voice message. In one embodiment, the announcement may be accompanied by a Special Instruction Tone (SIT) cadence.
[0127] If the calling party leaves a name, the customer's device may then ring. The ring may be accompanied by a notification that gives the customer the option of taking the call, diverting the call to voice mail, deny the call, etc. The customer's device that rings may be preset or manually provided by the customer in response to a query. The device may also be whatever device originally received the RTCM notification. The call is routed according to the customer's selection.
If the calling party enters a valid PIN, the calling party's call may be connected to the customer right away.
[0128] When the voice mail option is selected (step 942), the RTCM server 602 may instruct ISCP 302 to route the call to the customer's current preferred voice mail number. The preferred voice mail number may be preset or manually provided by the customer in response to a query. For example, when the customer selects the send to voice mail option, the popup (e.g., RTCM
notification) goes away and the incoming call is sent to either a present voice mail box or a voice mail box provided by the customer in response to a query given to the customer after the popup went away.
[0129] When the accept call option is selected (step 944), the RTCM server 602 may instruct ISCP 302 to route the call to the device on which the customer received the RTCM
notification. If the customer is connected to the Internet via dial-up access on the same phone line that the call is to be routed, the customer's Internet session may be immediately disconnected so that the call may be answered.
[0130] In cases where the play announcement option (step 946) is selected, the RTCM server 602 may instruct ISCP 302 to cause a predetermined recorded announcement to be played for the calling party.
For example, the customer may wish to tell particular callers that he or she is not available, without giving them the option of leaving a voice message. One of ordinary skill in the art will recognize that other announcements may be played.
[0131] When the schedule call back option is selected (step 948), the RTCM
server 602 may instruct ISCP
302 to cause an announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach is currently on a call but will call you back later." The RTCM server may also cause a prompt to be presented to the customer asking for the customer to set up a callback event in the digital companion calendar. This callback event may, with the customer's approval, send an e-mail or other message to the caller showing the intended date and time of the callback, if the caller is also a digital companion customer or has an e-mail address or other device indicator (e.g., phone number of a mobile phone capable of receiving text messages) in a contacts list associated with the called customer. When the time and date of the callback occur, a call may be automatically placed from the called customer to the calling party.
[0132] When the auto call back option is selected (step 950), the RTCM server 602 may instruct ISCP 302 to cause an announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach is currently on a call but will call you back as soon as that call is finished." When the customer's line is free (e.g., the customer is done with the previous call), a call may be automatically placed from the customer to the calling party.
[0133] When the conference call option is selected (step 952), the RTCM server may instruct ISCP 302 to cause the calling party to be bridged onto the current call. For example, the called customer may be on a telephone call with a first party when a second party calls the customer. If the customer selects the conference call option, the a RTCM server 602 instructs ISCP 302 to create a conference call between the customer, the first party, and the second party. For example, in response to a request from RTCM
server 602, ISCP 302 may instruct a switch handling the existing call between the customer and the first party to bridge the incoming call from the second party with the existing call. One of ordinary skill in the art will appreciate that the calling party can be bridged onto a conference call between the customer and multiple other parties instead of bridged onto a normal call between the customer and one other party.
[0134] When the block call option is selected (step 954), the RTCM server 602 may instruct ISCP 302 to cause a predetermined recorded announcement to be played for the calling party. For example, the announcement could be "the party you are trying to reach does not wish to speak to you." The calling party's number may also optionally be added to a call block list of numbers with which the customer does not wish to speak.
[0135] FIG. 10 is a diagram of an exemplary user interface 1000 including customer-selectable real-time call management options. User interface 1000 may be a display on a customer device, such as user terminal 112 or phone 114, that is currently showing an RTCM notification. The RTCM notification includes an area 1002 indicating that the customer has an incoming call. Area 1002 also provides an identification of the caller as well as the number being called. The number being called may belong to the device displaying the RTCM notification or another device. The RTCM has a number of user-selectable areas 1004-1022 associated with it, allowing the customer to decide how an incoming call is routed. In one embodiment, the customer may select one of these user-selectable areas through any suitable input methods. For example, the customer may click on the desired option using a mouse, touch an appropriate area of a touchscreen, enter input on a keypad, etc., in order to choose the manner in which the incoming call is routed.
[0136] Selecting area 1004 enables the customer to answer the call on the device that received the RTCM notification (e.g., the device the includes user interface 1000).
Selecting area 1006 forwards the call the voice mail as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1008 initiates a call screening feature as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1010 places the call on hold as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1012 forwards the call to another device of the customer's choosing as discussed above with reference to FIGS. 9A and 9B.
Selecting area 1014 plays an announcement for the calling party as discussed above with reference to FIGS. 9A and 9B. Selecting area 1016 enables a customer to schedule a call back event on a calendar as discussed above with reference to FIGS. 9A and 9B. Selecting area 1018 enables a customer to cause the calling party to be automatically called back after the current call as discussed above with reference to FIGS. 9A and 9B. Selecting area 1020 bridges call party onto the current call as discussed above with reference to FIGS. 9A and 9B. Selecting area 1022 cause a recording to be played indicating that the customer does not wish to speak to the calling party and optionally cause the calling party's telephone number to be added to a call block list, as discussed above with reference to FIGS. 9A and 9B.
[0137] FIG. 11 is a diagram of an exemplary user interface 1100 that enables a customer to change preferences consistent with the present invention. As illustrated in FIG. 11, a customer may have the ability to enable or disable real-time call management for a given device. The customer also may select particular devices to handle different actions. For example, a customer may set specific phone numbers to handle features such as answer calls, send to voice mail, forward call, and/or telemarketer zap (e.g., call screening). One of ordinary skill in the art will appreciate that other features may also have phone numbers set for them. The customer also has the option of viewing various other settings associated with the customer, such as a list of numbers that are call blocked, call back settings, etc.
[0138] While the present invention has been described in connection with various embodiments, many modifications will be readily apparent to those skilled in the art. One skilled in the art will also appreciate that all or part of the systems and methods consistent with the present invention may be stored on or read from computer-readable media, such as secondary storage devices, like hard disks, floppy disks, and CD-ROM; a carrier wave received from a network such as the Internet; or other forms of ROM or RAM. Accordingly, embodiments of the invention are not limited to the above described embodiments and examples, but instead is defined by the appended claims in light of their full scope of equivalents.
Claims (58)
1. A method, comprising:
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
determining call management features enabled for the customer based on the information pertaining to the call;
selecting a device associated with the customer to receive a notification of the call based on the retrieved data, the notification indicating the enabled call management features;
providing the notification to the selected device;
displaying the notification indicating the enabled call management features;
receiving a response to the notification from the customer; and instructing the service control point to connect the call based on the response.
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
determining call management features enabled for the customer based on the information pertaining to the call;
selecting a device associated with the customer to receive a notification of the call based on the retrieved data, the notification indicating the enabled call management features;
providing the notification to the selected device;
displaying the notification indicating the enabled call management features;
receiving a response to the notification from the customer; and instructing the service control point to connect the call based on the response.
2. An apparatus comprising:
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for selecting a device associated with the customer to receive the notification based on the data corresponding to the customer;
means for sending a notification of the call to the device for display on the device, the notification indicating a called number;
means for determining if a response to the notification is received from the customer; and means for instructing the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification.
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for selecting a device associated with the customer to receive the notification based on the data corresponding to the customer;
means for sending a notification of the call to the device for display on the device, the notification indicating a called number;
means for determining if a response to the notification is received from the customer; and means for instructing the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification.
3. The apparatus of claim 2, wherein a switch intercepts the call upon encountering a trigger.
4. The apparatus of claim 3, wherein the service control point sends an announcement to the switch.
5. The apparatus of claim 4, wherein the announcement is played for a calling party while the service control point is waiting for a response.
6. The apparatus of claim 2, wherein the information pertaining to the call comprises at least one of call state data, a call intercept indicator, a voice mail indicator, time zone data, user ID, called number data, calling name data, calling number data, and calling party number presentation information.
7. The apparatus of claim 2, further comprising:
means for determining features that are enabled for the customer based on the information pertaining to the call.
means for determining features that are enabled for the customer based on the information pertaining to the call.
8. The apparatus of claim 7, wherein the retrieved data comprises an indication of an access point that the customer is using.
9. The apparatus of claim 7, wherein the retrieved data comprises at least one of an indication of an access point that the customer is using, a call block list, a list of forwarding devices, a list of forwarding numbers, voice mail preferences, and a list of recordings.
10. The apparatus of claim 7, the means for retrieving comprising:
means for determining a customer identification using called number data; and means for finding an indication of an access point being used by the customer, utilizing the customer identification.
means for determining a customer identification using called number data; and means for finding an indication of an access point being used by the customer, utilizing the customer identification.
11. The apparatus of claim 2, wherein the notification comprises a plurality of customer-selectable call disposition options.
12. The apparatus of claim 11, wherein the notification comprises an indication of a calling number and a called number.
13. The apparatus of claim 11, wherein the notification is displayed on the device associated with the customer.
14. The apparatus of claim 11, wherein the call disposition options comprise at least one of sending a call to voice mail, forwarding a call to another device, performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, and initiating a conference call.
15. The apparatus of claim 7, wherein the notification comprises a plurality of customer-selectable call disposition options limited by the features determined to be enabled.
16. The apparatus of claim 2, the means for instructing comprising:
means for sending the service control point response information indicative of a response to the notification from the customer.
means for sending the service control point response information indicative of a response to the notification from the customer.
17. The apparatus of claim 2, wherein the response information includes at least one of call disposition information, forwarding number information, nature of forwarding number information, carrier access code, announcement type, and ring cadence.
18. The apparatus of claim 17, wherein the call disposition information comprises an indication of at least one of sending a call to voice mail, forwarding a call to another device, performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, and initiating a conference call.
19. The apparatus of claim 2, the means for instructing comprising:
means for instructing the service control point to forward the call to another device based on the response to the notification.
means for instructing the service control point to forward the call to another device based on the response to the notification.
20. The apparatus of claim 19, wherein the call is forwarded to another device having a phone number entered by the customer.
21. The apparatus of claim 19, wherein the call is forwarded to another device having a phone number selected from a list by the customer.
22. An apparatus comprising:
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for sending a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data;
means for displaying the notification with customer-selectable options for managing the call;
means for receiving a response to the notification from the customer; and means for instructing the service control point to connect the call based on the response.
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for sending a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data;
means for displaying the notification with customer-selectable options for managing the call;
means for receiving a response to the notification from the customer; and means for instructing the service control point to connect the call based on the response.
23. An apparatus, comprising:
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for determining call management features enabled for the customer based on the information pertaining to the call;
means for selecting a device associated with the customer to receive a notification of the call based on the retrieved data;
means for providing the notification to the selected device, the notification including a display of the enabled call management features;
means for receiving a response to the notification from the customer; and means for instructing the service control point to connect the call based on the response.
means for receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
means for retrieving data corresponding to the customer using the information pertaining to the call;
means for determining call management features enabled for the customer based on the information pertaining to the call;
means for selecting a device associated with the customer to receive a notification of the call based on the retrieved data;
means for providing the notification to the selected device, the notification including a display of the enabled call management features;
means for receiving a response to the notification from the customer; and means for instructing the service control point to connect the call based on the response.
24. An apparatus comprising:
a memory having a program that: receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected; retrieves data corresponding to the customer using the information pertaining to the call; selects a device associated with the customer to receive the notification based on the data corresponding to the customer; sends a notification of the call to a device associated with the customer for display on the device;
determines if a response to the notification is received from the customer; and instructs the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification; and a processor that runs the program.
a memory having a program that: receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected; retrieves data corresponding to the customer using the information pertaining to the call; selects a device associated with the customer to receive the notification based on the data corresponding to the customer; sends a notification of the call to a device associated with the customer for display on the device;
determines if a response to the notification is received from the customer; and instructs the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification; and a processor that runs the program.
25. An apparatus, comprising:
a memory having a program that:
receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieves data corresponding to the customer using the information pertaining to the call;
sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data and the notification includes a display of customer-selectable options for managing the call;
receives a response to the notification from the customer; and instructs the service control point to connect the call based on the response; and a processor that runs the program.
a memory having a program that:
receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieves data corresponding to the customer using the information pertaining to the call;
sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data and the notification includes a display of customer-selectable options for managing the call;
receives a response to the notification from the customer; and instructs the service control point to connect the call based on the response; and a processor that runs the program.
26. An apparatus, comprising:
a memory having a program that:
receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieves data corresponding to the customer using the information pertaining to the call;
determines call management features enabled for the customer based on the information pertaining to the call;
selects a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled call management features;
provides the notification to the selected device;
receives a response to the notification from the customer; and instructs the service control point to connect the call based on the response; and a processor that runs the program.
a memory having a program that:
receives, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieves data corresponding to the customer using the information pertaining to the call;
determines call management features enabled for the customer based on the information pertaining to the call;
selects a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled call management features;
provides the notification to the selected device;
receives a response to the notification from the customer; and instructs the service control point to connect the call based on the response; and a processor that runs the program.
27. A computer-readable medium storing instructions which, when executed by a processor, will cause the processor to perform the method of:
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
selecting a device associated with the customer to receive the notification based on the data corresponding to the customer;
sending a notification of the call to the device for display on the device;
determining if a response to the notification is received from the customer;
and instructing the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification.
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
selecting a device associated with the customer to receive the notification based on the data corresponding to the customer;
sending a notification of the call to the device for display on the device;
determining if a response to the notification is received from the customer;
and instructing the service control point to connect the call to the selected device if a predetermined period of time expires before receiving the response to the displayed notification.
28. The computer-readable medium of claim 27, wherein a switch intercepts the call.
29. The computer-readable medium of claim 28, wherein the switch intercepts the call upon encountering a trigger.
30. The computer-readable medium of claim 28, wherein the service control point sends an announcement to the switch.
31. The computer-readable medium of claim 30, wherein the announcement is played for a calling party as long as the service control point is waiting for a response.
32. The computer-readable medium of claim 27, wherein the information pertaining to the call comprises at least one of call state data, a call intercept indicator, a voice mail indicator, time zone data, user ID, called number data, calling name data, calling number data, and calling party number presentation information.
33. The computer-readable medium of claim 27, the method further comprising:
determining features that are enabled for the customer based on the information pertaining to the call.
determining features that are enabled for the customer based on the information pertaining to the call.
34. The computer-readable medium of claim 27, the method further comprising:
providing the notification to the selected device for display on the selected device.
providing the notification to the selected device for display on the selected device.
35. The computer-readable medium of claim 33, further comprising:
providing the notification to the selected device for display on the selected device.
providing the notification to the selected device for display on the selected device.
36. The computer-readable medium of claim 35, wherein the retrieved data comprises an indication of an access point that the customer is using.
37. The computer-readable medium of claim 35, wherein the retrieved data comprises at least one of an indication of an access point that the customer is using, a call block list, a list of forwarding devices, a list of forwarding numbers, voice mail preferences, and a list of recordings.
38. The computer-readable medium of claim 35, the retrieving comprising:
determining a customer identification using called number data; and finding an indication of an access point being used by the customer, utilizing the customer identification.
determining a customer identification using called number data; and finding an indication of an access point being used by the customer, utilizing the customer identification.
39. The computer-readable medium of claim 27, wherein the notification comprises a plurality of customer-selectable call disposition options.
40. The computer-readable medium of claim 39, wherein the notification comprises an indication of a calling number and a called number.
41. The computer-readable medium of claim 39, wherein the notification is displayed on the device associated with the customer.
42. The computer-readable medium of claim 39, wherein the call disposition options comprise at least one of sending a call to voice mail, forwarding a call to another device, performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, and initiating a conference call.
43. The computer-readable medium of claim 32, wherein the notification comprises a plurality of customer-selectable call disposition options limited by the features determined to be enabled.
44. The computer-readable medium of claim 27, the instructing comprising:
sending the service control point response information indicative of a response to the notification from the customer.
sending the service control point response information indicative of a response to the notification from the customer.
45. The computer-readable medium of claim 44, wherein the response information includes at least one of call disposition information, forwarding number information, nature of forwarding number information, carrier access code, announcement type, and ring cadence.
46. The computer-readable medium of claim 45, wherein the call disposition information comprises an indication of at least one of sending a call to voice mail, forwarding a call to another device, performing a call screening operation, accepting a call, playing an announcement, placing a call on hold, scheduling a call back operation, performing an automatic call back operation, performing a call block operation, and initiating a conference call.
47. The computer-readable medium of claim 27, the instructing comprising:
instructing the service control point to forward the call to another device based on the response to the notification.
instructing the service control point to forward the call to another device based on the response to the notification.
48. The computer-readable medium of claim 47, wherein the call is forwarded to another device having a phone number entered by the customer.
49. The computer-readable medium of claim 47, wherein the call is forwarded to another device having a phone number selected from a list by the customer.
50. A computer-readable medium storing instructions which, when executed by a processor, will cause the processor to perform the method of:
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
determining features enabled for the customer based on the information pertaining to the call;
selecting a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled features;
providing the notification to the selected device;
receiving a response to the notification from the customer;
and instructing the service control point to connect the call based on the response.
receiving, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how the call is connected;
retrieving data corresponding to the customer using the information pertaining to the call;
determining features enabled for the customer based on the information pertaining to the call;
selecting a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled features;
providing the notification to the selected device;
receiving a response to the notification from the customer;
and instructing the service control point to connect the call based on the response.
51. A method for managing a call, comprising:
receiving notification of a call to a customer at a device associated with the customer, wherein the device is determined based on retrieved data corresponding to the customer, and the retrieved data was retrieved using information pertaining to the call;
displaying the notification with customer-selectable options for managing the call;
receiving input from the customer indicative of a response to the notification; and sending, to a server, response information reflective of the response to the notification, wherein the server instructs a service control point to connect the call based on the response to the notification.
receiving notification of a call to a customer at a device associated with the customer, wherein the device is determined based on retrieved data corresponding to the customer, and the retrieved data was retrieved using information pertaining to the call;
displaying the notification with customer-selectable options for managing the call;
receiving input from the customer indicative of a response to the notification; and sending, to a server, response information reflective of the response to the notification, wherein the server instructs a service control point to connect the call based on the response to the notification.
52. A device for use in real-time based on input from a user, comprising:
a memory having a program that: receives notification of a call to the user at the device, wherein the device is one of a plurality of devices associated with the user, the device is determined based on retrieved data corresponding to the user, and the retrieved data was retrieved using information pertaining to the call; displays the notification with customer-selectable options for managing the call; receives input from the customer indicative of a response to the notification; and sends response information to a server reflective of the response to the notification, wherein the server instructs a service control point to connect the call based on the response to the notification;
a user interface that displays the notification; and a processor that runs the program.
a memory having a program that: receives notification of a call to the user at the device, wherein the device is one of a plurality of devices associated with the user, the device is determined based on retrieved data corresponding to the user, and the retrieved data was retrieved using information pertaining to the call; displays the notification with customer-selectable options for managing the call; receives input from the customer indicative of a response to the notification; and sends response information to a server reflective of the response to the notification, wherein the server instructs a service control point to connect the call based on the response to the notification;
a user interface that displays the notification; and a processor that runs the program.
53. A method, comprising:
sending, to a service center, information pertaining to a call to a customer, wherein the service center: retrieves data corresponding to the customer using the information pertaining to the call; sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, the device is one of a plurality of devices associated with the customer, and the notification includes a display of customer-selectable options for managing the call; and provides response information reflective of a response to the notification from the customer;
receiving the response information from the service center; and connecting the call based on the response information.
sending, to a service center, information pertaining to a call to a customer, wherein the service center: retrieves data corresponding to the customer using the information pertaining to the call; sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, the device is one of a plurality of devices associated with the customer, and the notification includes a display of customer-selectable options for managing the call; and provides response information reflective of a response to the notification from the customer;
receiving the response information from the service center; and connecting the call based on the response information.
54. An apparatus, comprising:
means for sending, to a service center, information pertaining to a call to a customer, wherein the service center: retrieves data corresponding to the customer using the information pertaining to the call; sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, the device is one of a plurality of devices associated with the customer, and the notification includes a display of customer-selectable options for managing the call; and provides response information reflective of a response to the notification from the customer;
means for receiving the response information from the service center; and means for connecting the call based on the response information.
means for sending, to a service center, information pertaining to a call to a customer, wherein the service center: retrieves data corresponding to the customer using the information pertaining to the call; sends a notification of the call to a device associated with the customer, wherein the device is determined based on the retrieved data, the device is one of a plurality of devices associated with the customer, and the notification includes a display of customer-selectable options for managing the call; and provides response information reflective of a response to the notification from the customer;
means for receiving the response information from the service center; and means for connecting the call based on the response information.
55. A system, comprising:
a voice network including a service control point operable to determine how a call is connected;
a data network;
a plurality of devices associated with a user;
a service center operable to: receive information pertaining to the call to the user from the service control point; retrieve data corresponding to the user using the information pertaining to the call; send a notification of the call to a device associated with the user via the data network, wherein the device is determined based on the retrieved data and is one of the plurality of devices associated with the user; and instruct the service control point to connect the call based on a response to the notification from the user by providing the service control point with response information reflective of the response, wherein the service control point receives the response information from the service center and connects the call based on the response information; and at least one of the plurality of devices associated with the user displays the notification with customer-selectable options for managing the call.
a voice network including a service control point operable to determine how a call is connected;
a data network;
a plurality of devices associated with a user;
a service center operable to: receive information pertaining to the call to the user from the service control point; retrieve data corresponding to the user using the information pertaining to the call; send a notification of the call to a device associated with the user via the data network, wherein the device is determined based on the retrieved data and is one of the plurality of devices associated with the user; and instruct the service control point to connect the call based on a response to the notification from the user by providing the service control point with response information reflective of the response, wherein the service control point receives the response information from the service center and connects the call based on the response information; and at least one of the plurality of devices associated with the user displays the notification with customer-selectable options for managing the call.
56. An apparatus comprising:
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to send a notification of the call to a device associated with the customer for display on the device, wherein the first server instructs the service control point to connect the call to the device if a predetermined period of time expires before receiving the response to the displayed notification;
wherein the device is selected to receive the notification based on data corresponding to the customer, the data being retrieved using information pertaining to the call.
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to send a notification of the call to a device associated with the customer for display on the device, wherein the first server instructs the service control point to connect the call to the device if a predetermined period of time expires before receiving the response to the displayed notification;
wherein the device is selected to receive the notification based on data corresponding to the customer, the data being retrieved using information pertaining to the call.
57. An apparatus comprising:
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to retrieve data corresponding to the customer using the information pertaining to the call and send a notification of the call to a device associated with the customer, the notification including a display of customer-selectable options for managing the call, wherein the device is determined based on the retrieved data, wherein the first server receives a response to the notification from the customer and instructs the service control point to connect the call based on the response.
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to retrieve data corresponding to the customer using the information pertaining to the call and send a notification of the call to a device associated with the customer, the notification including a display of customer-selectable options for managing the call, wherein the device is determined based on the retrieved data, wherein the first server receives a response to the notification from the customer and instructs the service control point to connect the call based on the response.
58. An apparatus comprising:
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to retrieve data corresponding to the customer using the information pertaining to the call, determine call management features enabled for the customer based on the information pertaining to the call, select a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled call management features, and provide the notification to the selected device, wherein the first server receives a response to the notification from the customer and instructs the service control point to connect the call based on the response.
a first server operable to receive, from a service control point, information pertaining to a call to a customer, the service control point being operable to determine how a call is connected; and a second server operable to retrieve data corresponding to the customer using the information pertaining to the call, determine call management features enabled for the customer based on the information pertaining to the call, select a device associated with the customer to receive a notification of the call based on the retrieved data, the notification including a display of the enabled call management features, and provide the notification to the selected device, wherein the first server receives a response to the notification from the customer and instructs the service control point to connect the call based on the response.
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 | ||
CA2507127A CA2507127C (en) | 2002-11-25 | 2003-11-25 | Methods and systems for call management with user intervention |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2507127A Division CA2507127C (en) | 2002-11-25 | 2003-11-25 | Methods and systems for call management with user intervention |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2774362A1 CA2774362A1 (en) | 2004-06-10 |
CA2774362C true CA2774362C (en) | 2014-04-15 |
Family
ID=32397150
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2774362A Expired - Fee Related CA2774362C (en) | 2002-11-25 | 2003-11-25 | Methods and systems for call management with user intervention |
Country Status (3)
Country | Link |
---|---|
US (5) | US8472931B2 (en) |
JP (2) | JP2009189048A (en) |
CA (1) | CA2774362C (en) |
Families Citing this family (218)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6928300B1 (en) * | 2000-11-09 | 2005-08-09 | Palmsource, Inc. | Method and apparatus for automated flexible configuring of notifications and activation |
US8751571B2 (en) | 2001-02-27 | 2014-06-10 | Verizon Data Services Llc | Methods and systems for CPN triggered collaboration |
US8503650B2 (en) | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Methods and systems for configuring and providing conference calls |
US8503639B2 (en) | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Method and apparatus for adaptive message and call notification |
US8873730B2 (en) | 2001-02-27 | 2014-10-28 | Verizon Patent And Licensing Inc. | Method and apparatus for calendared communications flow control |
US8488761B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for a call log |
US8472428B2 (en) | 2001-02-27 | 2013-06-25 | Verizon Data Services Llc | Methods and systems for line management |
US8750482B2 (en) | 2001-02-27 | 2014-06-10 | Verizon Data Services Llc | Methods and systems for preemptive rejection of calls |
US8494135B2 (en) | 2001-02-27 | 2013-07-23 | Verizon Data Services Llc | Methods and systems for contact management |
US7912193B2 (en) * | 2001-02-27 | 2011-03-22 | Verizon Data Services Llc | Methods and systems for call management with user intervention |
US8467502B2 (en) * | 2001-02-27 | 2013-06-18 | Verizon Data Services Llc | Interactive assistant for managing telephone communications |
US8472931B2 (en) | 2002-11-25 | 2013-06-25 | Telesector Resources Group, Inc. | Methods and systems for automatic communication line management based on device location |
US8472606B2 (en) | 2001-02-27 | 2013-06-25 | Verizon Data Services Llc | Methods and systems for directory information lookup |
US8761363B2 (en) | 2001-02-27 | 2014-06-24 | Verizon Data Services Llc | Methods and systems for automatic forwarding of communications to a preferred device |
US8488766B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for multiuser selective notification |
US8798251B2 (en) | 2001-02-27 | 2014-08-05 | Verizon Data Services Llc | Methods and systems for computer enhanced conference calling |
US6976017B1 (en) | 2001-02-27 | 2005-12-13 | Verizon Data Services Inc. | Method and apparatus for context based querying |
US8774380B2 (en) * | 2001-02-27 | 2014-07-08 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
US7903796B1 (en) | 2001-02-27 | 2011-03-08 | Verizon Data Services Llc | Method and apparatus for unified communication management via instant messaging |
US6750897B1 (en) | 2001-08-16 | 2004-06-15 | Verizon Data Services Inc. | Systems and methods for implementing internet video conferencing using standard phone calls |
US9392120B2 (en) | 2002-02-27 | 2016-07-12 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
US6985720B2 (en) * | 2002-07-12 | 2006-01-10 | Qualcomm, Incorporated | Apparatus and method for transparent and integrated wireless messaging in a multi-mode environment |
WO2004051949A1 (en) * | 2002-11-29 | 2004-06-17 | Eun Young Chung | System and method for providing integrated communication id |
US7653192B1 (en) * | 2002-12-20 | 2010-01-26 | Nortel Networks Limited | Multimedia augmented conference bridge |
US20040207724A1 (en) * | 2003-04-17 | 2004-10-21 | Siemens Information And Communication Networks, Inc. | System and method for real time playback of conferencing streams |
JP4021372B2 (en) * | 2003-05-29 | 2007-12-12 | 株式会社東芝 | Telephone exchange method and system |
US7616950B2 (en) | 2003-09-04 | 2009-11-10 | At&T Intellectual Property I, L.P. | Call forwarding control device and method of call management |
US8526977B2 (en) | 2003-09-23 | 2013-09-03 | At&T Intellectual Property I, L.P. | Location based call routing for call answering services |
US7769392B2 (en) * | 2003-09-23 | 2010-08-03 | At&T Intellectual Property I, L.P. | Method and system for forwarding wireless communications |
US7660856B2 (en) * | 2003-10-06 | 2010-02-09 | Microsoft Corporation | Method and system for web-based event notification |
US7577427B2 (en) | 2003-11-05 | 2009-08-18 | At&T Intellectual Property I, L.P. | System and method of transitioning between cellular and voice over internet protocol communication |
US7734294B2 (en) | 2004-01-12 | 2010-06-08 | At&T Intellectual Property, I,L.P. | Intelligent interactive call handling |
US7680259B2 (en) * | 2004-01-12 | 2010-03-16 | At&T Intellectual Property, I,L.P. | Rule-based intelligent call forwarding |
US20050185634A1 (en) * | 2004-02-24 | 2005-08-25 | Benco David S. | Method and system for providing network support for messaging between short message service (SMS) subscribers and instant messaging (IM) subscribers |
JP4365239B2 (en) * | 2004-02-25 | 2009-11-18 | パイオニア株式会社 | Network conferencing system |
CN100488303C (en) * | 2004-04-08 | 2009-05-13 | 深圳市点睛科技有限公司 | Method of terminal and called communication with mobile terminal relation |
US7916849B2 (en) * | 2004-06-02 | 2011-03-29 | Clearone Communications, Inc. | Systems and methods for managing the gating of microphones in a multi-pod conference system |
US8644525B2 (en) * | 2004-06-02 | 2014-02-04 | Clearone Communications, Inc. | Virtual microphones in electronic conferencing systems |
US7864937B2 (en) * | 2004-06-02 | 2011-01-04 | Clearone Communications, Inc. | Common control of an electronic multi-pod conferencing system |
US8031853B2 (en) * | 2004-06-02 | 2011-10-04 | Clearone Communications, Inc. | Multi-pod conference systems |
US20050272408A1 (en) * | 2004-06-04 | 2005-12-08 | Deanna Wilkes-Gibbs | Method for personal notification indication |
US7133513B1 (en) * | 2004-07-21 | 2006-11-07 | Sprint Spectrum L.P. | Method and system for transcribing voice content of an on-going teleconference into human-readable notation |
US7580837B2 (en) | 2004-08-12 | 2009-08-25 | At&T Intellectual Property I, L.P. | System and method for targeted tuning module of a speech recognition system |
US7333773B2 (en) * | 2004-09-16 | 2008-02-19 | International Business Machines Corporation | Coordination of cellular telephones in a residential area to obviate need for wired residential service |
US7936863B2 (en) * | 2004-09-30 | 2011-05-03 | Avaya Inc. | Method and apparatus for providing communication tasks in a workflow |
US8270320B2 (en) | 2004-09-30 | 2012-09-18 | Avaya Inc. | Method and apparatus for launching a conference based on presence of invitees |
US8107401B2 (en) | 2004-09-30 | 2012-01-31 | Avaya Inc. | Method and apparatus for providing a virtual assistant to a communication participant |
US8180722B2 (en) | 2004-09-30 | 2012-05-15 | Avaya Inc. | Method and apparatus for data mining within communication session information using an entity relationship model |
DE102004053597B4 (en) * | 2004-11-05 | 2008-05-29 | Infineon Technologies Ag | A method for automatically generating and / or controlling a telecommunications conference with a plurality of subscribers, telecommunication conference terminal and telecommunication conference server |
WO2006051584A1 (en) * | 2004-11-10 | 2006-05-18 | Fujitsu Limited | Contents server, and contents service system |
US7242751B2 (en) | 2004-12-06 | 2007-07-10 | Sbc Knowledge Ventures, L.P. | System and method for speech recognition-enabled automatic call routing |
US7693133B2 (en) * | 2004-12-30 | 2010-04-06 | Alcatel-Lucent Usa Inc. | System and method for conference calling with VOIP terminal |
US7751551B2 (en) | 2005-01-10 | 2010-07-06 | At&T Intellectual Property I, L.P. | System and method for speech-enabled call routing |
US7664058B1 (en) * | 2005-02-02 | 2010-02-16 | At&T Corp. | Method and apparatus for providing spontaneous multi-way telephone conversation with inserted messaging |
US8964965B1 (en) * | 2005-02-03 | 2015-02-24 | Microsoft Technology Licensing, Llc | Smart capture |
FR2882485A1 (en) * | 2005-02-18 | 2006-08-25 | Thomson Licensing Sa | Routing device for e.g. domestic network, has unit to automatically select multimedia terminal that receives/emits flow based on its location and/or capacity and/or availability, and control device to receive flow from selected terminal |
US8825108B2 (en) * | 2005-04-06 | 2014-09-02 | Qwest Communications International Inc. | Call handling on dual-mode wireless handsets |
US9363370B2 (en) * | 2005-04-06 | 2016-06-07 | Qwest Communications International Inc. | Methods of delivering calls on dual-mode wireless handsets |
US9363384B2 (en) * | 2005-04-06 | 2016-06-07 | Qwest Communications International Inc. | Systems for delivering calls on dual-mode wireless handsets |
US8989813B2 (en) * | 2005-04-06 | 2015-03-24 | Qwest Communications International Inc. | Handset registration in a dual-mode environment |
US8457614B2 (en) | 2005-04-07 | 2013-06-04 | Clearone Communications, Inc. | Wireless multi-unit conference phone |
US20060240877A1 (en) * | 2005-04-22 | 2006-10-26 | Viktor Filiba | System and method for providing in-coming call alerts |
US20060244818A1 (en) * | 2005-04-28 | 2006-11-02 | Comotiv Systems, Inc. | Web-based conferencing system |
US7657020B2 (en) | 2005-06-03 | 2010-02-02 | At&T Intellectual Property I, Lp | Call routing system and method of using the same |
US8005204B2 (en) | 2005-06-03 | 2011-08-23 | At&T Intellectual Property I, L.P. | Call routing system and method of using the same |
GB2428347A (en) * | 2005-07-09 | 2007-01-24 | Ring2 Comm Ltd | Recording telephone conversations in a conference call environment |
US20070038740A1 (en) * | 2005-08-10 | 2007-02-15 | Nortel Networks Limited | Notification service |
US8432897B2 (en) * | 2005-08-29 | 2013-04-30 | At&T Intellectual Property I, L.P. | System and method of presenting caller identification information at a voice over internet protocol communication device |
US8081747B2 (en) | 2005-08-29 | 2011-12-20 | At&T Intellectual Property I, Lp | System and method of managing telephone calls within a voice over internet protocol telephone system |
US9088877B1 (en) * | 2005-09-16 | 2015-07-21 | Avaya, Inc. | Systems and methods for initiating communication between IM clients and mobile clients |
US7940702B1 (en) * | 2005-09-23 | 2011-05-10 | Avaya Inc. | Method and apparatus for allowing communication within a group |
US20070079260A1 (en) * | 2005-10-04 | 2007-04-05 | Bhogal Kulvir S | Method and apparatus to transmit a calendar event in target calendaring system format |
US7477909B2 (en) * | 2005-10-31 | 2009-01-13 | Nuance Communications, Inc. | System and method for conducting a search using a wireless mobile device |
US20070180020A1 (en) * | 2005-10-31 | 2007-08-02 | My-T Llc | System, Method, and Computer Program Product for Internet Tool |
KR100659253B1 (en) * | 2005-11-07 | 2006-12-20 | 삼성전자주식회사 | Method for searching of bluetooth device in portable terminal |
US8036911B2 (en) * | 2005-11-11 | 2011-10-11 | Carefusion 303, Inc. | System and method for managing patient care through automated messaging |
US8379821B1 (en) | 2005-11-18 | 2013-02-19 | At&T Intellectual Property Ii, L.P. | Per-conference-leg recording control for multimedia conferencing |
US20070140143A1 (en) * | 2005-12-19 | 2007-06-21 | Harris John M | Communication device and method for managing a communication link in a network |
US20070198637A1 (en) * | 2006-01-04 | 2007-08-23 | Scott Deboy | Conferencing system with data file management |
US20070156829A1 (en) * | 2006-01-05 | 2007-07-05 | Scott Deboy | Messaging system with secure access |
US20070239827A1 (en) * | 2006-02-13 | 2007-10-11 | Scott Deboy | Global chat system |
US20070286366A1 (en) * | 2006-03-17 | 2007-12-13 | Scott Deboy | Chat presence system |
US8442197B1 (en) * | 2006-03-30 | 2013-05-14 | Avaya Inc. | Telephone-based user interface for participating simultaneously in more than one teleconference |
US20070263603A1 (en) * | 2006-04-17 | 2007-11-15 | Lucent Technologies, Inc. | VoIP PERSONAL CALL RECORDER |
US20070269025A1 (en) * | 2006-05-19 | 2007-11-22 | Shieh Johnny M | Managing Customer Access to a Communication Recorded by A Provider in Association with a Transaction |
US20070276910A1 (en) * | 2006-05-23 | 2007-11-29 | Scott Deboy | Conferencing system with desktop sharing |
KR20070113543A (en) * | 2006-05-25 | 2007-11-29 | (주)케이티에프테크놀로지스 | Method for displaying caller information of portable terminal |
US20080077664A1 (en) * | 2006-05-31 | 2008-03-27 | Motorola, Inc. | Method and apparatus for distributing messages in a communication network |
US20070282793A1 (en) * | 2006-06-01 | 2007-12-06 | Majors Kenneth D | Computer desktop sharing |
US7639634B2 (en) * | 2006-06-02 | 2009-12-29 | Cisco Technology, Inc. | Method and System for Joining a virtual talk group |
US20080037514A1 (en) * | 2006-06-27 | 2008-02-14 | International Business Machines Corporation | Method, system, and computer program product for controlling a voice over internet protocol (voip) communication session |
US20080005239A1 (en) * | 2006-06-28 | 2008-01-03 | Brian Podl | System and method for capturing collaborative data at a multi-function peripheral (MFP) |
US20080005245A1 (en) * | 2006-06-30 | 2008-01-03 | Scott Deboy | Conferencing system with firewall |
US8326276B2 (en) * | 2006-06-30 | 2012-12-04 | At&T Intellectual Property I, Lp | Proximity based call management |
CN101485189A (en) * | 2006-06-30 | 2009-07-15 | 网络电话时代有限公司 | Method and apparatus for visual message indication in a VOIP system |
KR20080003959A (en) * | 2006-07-04 | 2008-01-09 | 삼성전자주식회사 | Bluetooth apparatus possible to select profile and method for transmission data thereof |
US9210252B2 (en) * | 2006-07-13 | 2015-12-08 | Alcatel Lucent | End-user device personalized application notification feature |
US20080043964A1 (en) * | 2006-07-14 | 2008-02-21 | Majors Kenneth D | Audio conferencing bridge |
US20080021968A1 (en) * | 2006-07-19 | 2008-01-24 | Majors Kenneth D | Low bandwidth chat system |
US20080065999A1 (en) * | 2006-09-13 | 2008-03-13 | Majors Kenneth D | Conferencing system with document access |
US20080066001A1 (en) * | 2006-09-13 | 2008-03-13 | Majors Kenneth D | Conferencing system with linked chat |
US20080065727A1 (en) * | 2006-09-13 | 2008-03-13 | Majors Kenneth D | Conferencing system with improved access |
JP2008072655A (en) * | 2006-09-15 | 2008-03-27 | Fujitsu Ltd | Service communication control method, service relaying apparatus and service communication control system |
US8682980B2 (en) * | 2006-10-03 | 2014-03-25 | International Business Machines Corporation | Providing chat histories to invitees |
US20080134278A1 (en) * | 2006-12-05 | 2008-06-05 | General Instrument Corporation | Set-Top Box and Method for Operating the Set-Top Box Using a Mobile Telephone |
US8280914B2 (en) * | 2006-12-07 | 2012-10-02 | Sap Ag | Service desk interface |
US8706169B2 (en) * | 2006-12-28 | 2014-04-22 | Yahoo! Inc. | Interface overlay |
US20080170525A1 (en) * | 2007-01-12 | 2008-07-17 | Microsoft Corporation | Adaptive optimizations for connecting to a wireless network |
US8171087B2 (en) * | 2007-01-16 | 2012-05-01 | Oracle International Corporation | Thread-based conversation management |
US9294609B2 (en) * | 2007-02-27 | 2016-03-22 | Sony Corporation | Events on multiple phones |
US8488587B1 (en) * | 2007-04-02 | 2013-07-16 | Avaya Inc. | Method and apparatus performing automatic resource distribution |
US20080253544A1 (en) * | 2007-04-12 | 2008-10-16 | Microsoft Corporation | Automatically aggregated probabilistic personal contacts |
KR100812372B1 (en) * | 2007-04-24 | 2008-03-11 | 박승복 | Apparatus for notifying mobile phone call and method thereof |
US9241078B2 (en) * | 2007-06-28 | 2016-01-19 | Microsoft Technology Licensing, Llc | Virtual contact identifier |
US20090096573A1 (en) | 2007-10-10 | 2009-04-16 | Apple Inc. | Activation of Cryptographically Paired Device |
US9106450B2 (en) | 2007-11-01 | 2015-08-11 | International Business Machines Corporation | System and method for communication management |
US9602295B1 (en) | 2007-11-09 | 2017-03-21 | Avaya Inc. | Audio conferencing server for the internet |
US8934476B2 (en) * | 2007-11-26 | 2015-01-13 | Cisco Technology, Inc. | Enabling AD-HOC data communication over established mobile voice communications |
EP2229649A1 (en) * | 2007-12-10 | 2010-09-22 | International Business Machines Corporation | Method and system for entering data into a web page |
US8654951B1 (en) * | 2007-12-20 | 2014-02-18 | Avay Inc. | Method and apparatus for synchronizing transcripts and recordings of a bridge conference and using the same to navigate through the recording |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
CA2720398C (en) | 2008-04-02 | 2016-08-16 | Twilio Inc. | System and method for processing telephony sessions |
US8787872B2 (en) * | 2008-05-05 | 2014-07-22 | Telecommunication Systems, Inc. | Ingress/egress call module |
US8149997B2 (en) * | 2008-05-30 | 2012-04-03 | Telecommunication Systems, Inc. | Protocol converting 9-1-1 emergency messaging center |
US7903587B2 (en) * | 2008-05-30 | 2011-03-08 | Telecommunication Systems, Inc. | Wireless emergency services protocols translator between ansi-41 and VoIP emergency services protocols |
US8102972B2 (en) * | 2008-06-05 | 2012-01-24 | Telecommunication Systems, Inc. | Emergency services selective router interface translator |
US8150015B1 (en) * | 2008-06-10 | 2012-04-03 | Sprint Communications Company L.P. | System and method of phone bridging |
US20090327425A1 (en) * | 2008-06-25 | 2009-12-31 | Microsoft Corporation | Switching between and dual existence in live and recorded versions of a meeting |
WO2010040010A1 (en) | 2008-10-01 | 2010-04-08 | Twilio Inc | Telephony web event system and method |
US10552819B1 (en) * | 2008-10-07 | 2020-02-04 | Amazon Technologies, Inc. | Media enhanced mobile payments |
US8693660B2 (en) | 2008-10-16 | 2014-04-08 | Plantronics, Inc. | Auto-dial and connection into conference calls |
US8041378B2 (en) | 2008-12-19 | 2011-10-18 | Cisco Technology, Inc. | System and method for providing channel configurations in a communications environment |
US8290124B2 (en) * | 2008-12-19 | 2012-10-16 | At&T Mobility Ii Llc | Conference call replay |
US8126494B2 (en) * | 2008-12-19 | 2012-02-28 | Cisco Technology, Inc. | System and method for providing a trunked radio and gateway |
US20100161727A1 (en) * | 2008-12-19 | 2010-06-24 | Cisco Technology, Inc. | System and Method for Accelerating a Wide Area Notification |
JP5801991B2 (en) * | 2008-12-25 | 2015-10-28 | 株式会社Nttドコモ | Incoming call control server and incoming call control method |
US9407748B2 (en) * | 2009-01-29 | 2016-08-02 | Centurylink Intellectual Property Llc | System and method for providing broadband notification |
WO2010101935A1 (en) | 2009-03-02 | 2010-09-10 | Twilio Inc. | Method and system for a multitenancy telephone network |
US8892439B2 (en) * | 2009-07-15 | 2014-11-18 | Microsoft Corporation | Combination and federation of local and remote speech recognition |
US8588385B2 (en) * | 2009-07-31 | 2013-11-19 | Cisco Technology, Inc. | Rich caller ID with communication history |
US8547880B2 (en) * | 2009-09-30 | 2013-10-01 | Avaya Inc. | Method and system for replaying a portion of a multi-party audio interaction |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US8495142B2 (en) * | 2010-03-11 | 2013-07-23 | Cisco Technology, Inc. | System and method for providing data channel management in a network environment |
US8412786B2 (en) * | 2010-04-20 | 2013-04-02 | Sprint Communications Company L.P. | Decomposition and delivery of message objects based on user instructions |
US9112980B2 (en) * | 2010-04-30 | 2015-08-18 | American Teleconferencing Services, Ltd. | Systems and methods for selectively reviewing a recorded conference |
US20150279354A1 (en) * | 2010-05-19 | 2015-10-01 | Google Inc. | Personalization and Latency Reduction for Voice-Activated Commands |
US9338064B2 (en) | 2010-06-23 | 2016-05-10 | Twilio, Inc. | System and method for managing a computing cluster |
US20120208495A1 (en) | 2010-06-23 | 2012-08-16 | Twilio, Inc. | System and method for monitoring account usage on a platform |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
US8868650B1 (en) * | 2010-07-12 | 2014-10-21 | Sprint Communications Company L.P. | Consolidating multi-party communications |
US8223948B2 (en) | 2010-08-23 | 2012-07-17 | Incontact, Inc. | Multi-tiered media services for globally interconnecting businesses and customers |
US8744065B2 (en) | 2010-09-22 | 2014-06-03 | Avaya Inc. | Method and system for monitoring contact center transactions |
US9736312B2 (en) | 2010-11-17 | 2017-08-15 | Avaya Inc. | Method and system for controlling audio signals in multiple concurrent conference calls |
KR101776958B1 (en) * | 2010-12-27 | 2017-09-08 | 삼성전자주식회사 | Method and apparatus for calling service multipoint in portable terminal |
US8649268B2 (en) | 2011-02-04 | 2014-02-11 | Twilio, Inc. | Method for processing telephony sessions of a network |
US20120213339A1 (en) * | 2011-02-18 | 2012-08-23 | Research In Motion Limited | Method and system for recording a conference call |
US9531818B2 (en) * | 2011-03-01 | 2016-12-27 | Lenovo (Beijing) Limited | Information notification methods, apparatuses and electronic devices |
WO2012162397A1 (en) | 2011-05-23 | 2012-11-29 | Twilio, Inc. | System and method for connecting a communication to a client |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
US20140044123A1 (en) | 2011-05-23 | 2014-02-13 | Twilio, Inc. | System and method for real time communicating with a client application |
EP2759123B1 (en) | 2011-09-21 | 2018-08-15 | Twilio, Inc. | System and method for authorizing and connecting application developers and users |
US10182147B2 (en) | 2011-09-21 | 2019-01-15 | Twilio Inc. | System and method for determining and communicating presence information |
US20130115910A1 (en) * | 2011-11-03 | 2013-05-09 | Cox Communications, Inc. | Systems and Methods of Intelligent Find Me Follow Me Services |
US9264537B2 (en) | 2011-12-05 | 2016-02-16 | Telecommunication Systems, Inc. | Special emergency call treatment based on the caller |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
CN103368821A (en) * | 2012-04-10 | 2013-10-23 | 中兴通讯股份有限公司 | Voice-message sending method and system and integrated-message server and clients |
CN103379017B (en) | 2012-04-13 | 2018-03-16 | 中兴通讯股份有限公司 | Voice leaving method and system, converged message server and client |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US20130304928A1 (en) | 2012-05-09 | 2013-11-14 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
GB201210600D0 (en) | 2012-06-14 | 2012-08-01 | Microsoft Corp | Call invites |
GB201210596D0 (en) | 2012-06-14 | 2012-08-01 | Microsoft Corp | Notification of communication events |
CN103338146B (en) * | 2012-06-14 | 2017-09-22 | 微软技术许可有限责任公司 | The notice of communication event |
GB2504461B (en) | 2012-06-14 | 2014-12-03 | Microsoft Corp | Notification of communication events |
GB201210598D0 (en) * | 2012-06-14 | 2012-08-01 | Microsoft Corp | Notification of communication events |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9515769B2 (en) * | 2013-03-15 | 2016-12-06 | Src, Inc. | Methods and systems for exploiting sensors of opportunity |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9240966B2 (en) | 2013-06-19 | 2016-01-19 | Twilio, Inc. | System and method for transmitting and receiving media messages |
WO2015001492A1 (en) | 2013-07-02 | 2015-01-08 | Family Systems, Limited | Systems and methods for improving audio conferencing services |
US9274858B2 (en) | 2013-09-17 | 2016-03-01 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US10666524B2 (en) * | 2014-04-11 | 2020-05-26 | Genband Us Llc | Collaborative multimedia communication |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US10320883B2 (en) * | 2014-05-21 | 2019-06-11 | Samsung Electronics Co., Ltd. | Device for and method of transmitting file |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US10666696B2 (en) * | 2014-09-05 | 2020-05-26 | Minerva Project, Inc. | System and method for a virtual conference interactive timeline |
US9749428B2 (en) | 2014-10-21 | 2017-08-29 | Twilio, Inc. | System and method for providing a network discovery service platform |
US9812126B2 (en) * | 2014-11-28 | 2017-11-07 | Microsoft Technology Licensing, Llc | Device arbitration for listening devices |
US10116496B2 (en) * | 2015-01-26 | 2018-10-30 | International Business Machines Corporation | Method of improving cloud resiliency |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US9973551B2 (en) * | 2015-02-10 | 2018-05-15 | Cisco Technology, Inc. | System, method, and logic for managing content in a virtual meeting |
US20160253629A1 (en) * | 2015-02-26 | 2016-09-01 | Salesforce.Com, Inc. | Meeting initiation based on physical proximity |
US20160285929A1 (en) * | 2015-03-27 | 2016-09-29 | Intel Corporation | Facilitating dynamic and seamless transitioning into online meetings |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
CN107409161B (en) * | 2015-12-04 | 2019-07-23 | 华为技术有限公司 | It shifts communication event and handles the method, apparatus and terminal of communication event |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10298769B2 (en) * | 2016-07-22 | 2019-05-21 | Lenovo (Singapore) Pte. Ltd. | Call transfer between devices |
US10764428B2 (en) * | 2017-12-29 | 2020-09-01 | Trysit Nitidharmatut | Simultaneous voice and data content driven commercial data platform |
US11032423B2 (en) | 2017-12-29 | 2021-06-08 | Trysit Nitidharmatut | Simultaneous voice and data content driven commercial data platform |
US11553082B2 (en) | 2017-12-29 | 2023-01-10 | Trysit Nitidharmatut | Simultaneous voice and data content driven commercial data platform |
US10477013B1 (en) * | 2018-11-19 | 2019-11-12 | Successful Cultures, Inc | Systems and methods for providing caller identification over a public switched telephone network |
US11290855B1 (en) * | 2020-09-29 | 2022-03-29 | T-Mobile Usa, Inc. | Instance-based message delivery |
Family Cites Families (475)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US626374A (en) * | 1899-06-06 | Ornamental knob or end piece for cords | ||
US466910A (en) * | 1892-01-12 | Machine for covering wire | ||
US2001004A (en) * | 1935-05-14 | wantz | ||
US847502A (en) * | 1906-06-04 | 1907-03-19 | American Car & Foundry Co | Side deck for passenger-car roofs. |
FR2285033A1 (en) * | 1974-09-10 | 1976-04-09 | Telstop Sa | SYSTEM FOR CONTROL OF CALLED TELEPHONE NUMBERS |
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 |
US5375161A (en) | 1984-09-14 | 1994-12-20 | Accessline Technologies, Inc. | Telephone control system with branch routing |
US5588037A (en) | 1984-09-14 | 1996-12-24 | Accessline Technologies, Inc. | Remote access telephone control system |
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 |
US5113431A (en) | 1989-10-31 | 1992-05-12 | At&T Bell Laboratories | Distributed control teleconferencing voice bridge |
US5274700A (en) | 1989-11-27 | 1993-12-28 | Unifi Communications Corporation | Methods of automatically rerouting an incoming telephone call placed over a network |
US5168515A (en) | 1989-11-27 | 1992-12-01 | Unifi Communications Corporation | Switchless automatic call distribution system |
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 |
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 |
US5329578A (en) * | 1992-05-26 | 1994-07-12 | Northern Telecom Limited | Personal communication service with mobility manager |
JPH06113020A (en) * | 1992-09-25 | 1994-04-22 | Nippon Telegr & Teleph Corp <Ntt> | Automatic number changing system |
CA2100139C (en) * | 1992-09-29 | 1997-02-18 | William Walter Demlow | Information display provided to calling party |
GB2272312A (en) | 1992-11-10 | 1994-05-11 | Ibm | Collaborative working in a network. |
US5440624A (en) | 1992-11-10 | 1995-08-08 | Netmedia, Inc. | Method and apparatus for providing adaptive administration and control of an electronic conference |
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 |
PL312223A1 (en) | 1993-06-15 | 1996-04-01 | Celltrace Communications Ltd | Telecommunication system |
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 |
US6594688B2 (en) * | 1993-10-01 | 2003-07-15 | Collaboration Properties, Inc. | Dedicated echo canceler for a workstation |
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 |
JPH07107171A (en) * | 1993-10-04 | 1995-04-21 | Hitachi Ltd | Communication means changing system |
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 |
US5483587A (en) | 1994-06-08 | 1996-01-09 | Linkusa Corporation | System and method for call conferencing |
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 |
EP0717545A3 (en) | 1994-12-13 | 1998-06-17 | AT&T Corp. | Interactive telephone networking service |
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 |
US5892900A (en) | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
DE69637733D1 (en) | 1995-02-13 | 2008-12-11 | Intertrust Tech Corp | SYSTEMS AND METHOD FOR SAFE TRANSMISSION |
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 |
JPH0964977A (en) * | 1995-08-25 | 1997-03-07 | Matsushita Electric Ind Co Ltd | Electronic exchange |
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 |
JP3398278B2 (en) * | 1996-04-26 | 2003-04-21 | 日本電信電話株式会社 | Communication method and communication system |
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 |
US5926535A (en) | 1996-08-05 | 1999-07-20 | International Business Machines Corporation | Third party call control |
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 |
WO1998013995A1 (en) * | 1996-09-25 | 1998-04-02 | British Telecommunications Public Limited Company | 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 |
DE69739173D1 (en) | 1996-10-09 | 2009-01-29 | Visa Int Service Ass | ELECTRONIC SYSTEM FOR PRESENTING EXPLANATIONS |
US6243398B1 (en) | 1996-10-21 | 2001-06-05 | Vocaltec Communications Ltd. | System and method for personal multimedia communication over a packet switched network |
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 |
US5805607A (en) | 1996-10-22 | 1998-09-08 | Advanced Micro Devices, Inc. | Method for user-controlled I/O switching during in-circuit programming of CPLDs through the IEEE 1149.1 test access port |
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 |
FI103845B1 (en) | 1996-11-14 | 1999-09-30 | Nokia Telecommunications Oy | Call setup via 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 |
US5916302A (en) | 1996-12-06 | 1999-06-29 | International Business Machines Corporation | Multimedia conferencing using parallel networks |
US6011579A (en) | 1996-12-10 | 2000-01-04 | Motorola, Inc. | Apparatus, method and system for wireline audio and video conferencing and telephony, with network interactivity |
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 |
US6144671A (en) | 1997-03-04 | 2000-11-07 | Nortel Networks Corporation | Call redirection methods in a packet based communications network |
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 |
US5995608A (en) | 1997-03-28 | 1999-11-30 | Confertech Systems Inc. | Method and apparatus for on-demand teleconferencing |
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 |
US6379538B1 (en) * | 1997-06-05 | 2002-04-30 | Lucid Treatment Systems, Inc. | Apparatus for separation and recovery of liquid and slurry abrasives used for polishing |
US6189026B1 (en) | 1997-06-16 | 2001-02-13 | Digital Equipment Corporation | Technique for dynamically generating an address book in a distributed electronic mail system |
US6243366B1 (en) | 1997-06-20 | 2001-06-05 | At&T Corp. | Method and apparatus for providing interactive two-way communications using a single one-way channel in satellite systems |
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 |
US6792084B1 (en) | 1997-09-08 | 2004-09-14 | Mci, Inc. | Single telephone number access to multiple communications services |
US6931116B1 (en) | 1997-09-08 | 2005-08-16 | Mci Communications Corporation | Multiple routing options in a telecommunications service platform |
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 |
US6574661B1 (en) | 1997-09-26 | 2003-06-03 | Mci Communications Corporation | Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client |
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 |
US6092102A (en) | 1997-10-24 | 2000-07-18 | University Of Pittsburgh Of The Commonwealth System Of Higher Education | System and method for notifying users about information or events of an enterprise |
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 |
US6856974B1 (en) | 1998-02-02 | 2005-02-15 | Checkfree Corporation | Electronic bill presentment technique with enhanced biller control |
US6442245B1 (en) | 1998-02-02 | 2002-08-27 | Unisys Corporation | System and method for providing voice messaging services utilizing a network connection |
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 |
US6145096A (en) | 1998-05-06 | 2000-11-07 | Motive Communications, Inc. | Method, system and computer program product for iterative distributed problem solving |
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 |
US7209955B1 (en) | 1998-05-29 | 2007-04-24 | Research In Motion Limited | Notification system and method for a mobile data communication device |
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 |
US6587890B1 (en) | 1998-06-12 | 2003-07-01 | Mci Communications Corporation | Switch controller application programmer interface |
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 |
US6324269B1 (en) | 1998-08-25 | 2001-11-27 | Bellsouth Corporation | Method and system for billing remote calls as if made from a primary line |
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 |
US6772436B1 (en) | 1998-09-01 | 2004-08-03 | International Business Machines Corporation | Interactive audio conferencing system |
US6775546B1 (en) | 1998-09-01 | 2004-08-10 | British Telecommunications Public Limited Company | Mobile telephone system |
US6154646A (en) | 1998-09-10 | 2000-11-28 | Telefonaktiebolaget L M Ericsson | System and method for real-time interactive selection of call treatment in a radio telecommunications network |
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 |
BR9913963A (en) | 1998-09-15 | 2003-04-01 | In Touch Technologies Ltd | Enhanced communication platform and related 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 |
US7349907B2 (en) | 1998-10-01 | 2008-03-25 | Onepin, Inc. | Method and apparatus for storing and retrieving business contact information in a computer system |
US6374259B1 (en) | 1998-10-01 | 2002-04-16 | Onepin, Llc | Method and apparatus for storing and retreiving business contact information in computer system |
US7509349B2 (en) | 1998-10-01 | 2009-03-24 | Onepin, Inc. | Method and apparatus for storing and retrieving business contact information in a 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 |
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 |
CA2282158A1 (en) | 1998-12-23 | 2000-06-23 | Nortel Networks Corporation | Local and remote notification of messages waiting and automatic retrieval of such messages |
JP2000196771A (en) * | 1998-12-24 | 2000-07-14 | Nec Corp | Telephone directory management system |
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 |
US6574470B1 (en) | 1998-12-31 | 2003-06-03 | At&T Corp. | Programmable ring-call forwarding in a wireless centrex services system |
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 |
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 |
US6560329B1 (en) | 1999-04-29 | 2003-05-06 | Teloquent Communications Corporation | Automated call routing system |
US6747970B1 (en) | 1999-04-29 | 2004-06-08 | Christopher H. Lamb | Methods and apparatus for providing communications services between connectionless and connection-oriented networks |
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 |
US6594352B1 (en) | 1999-05-14 | 2003-07-15 | Operator Service | Method and system for automatically providing a customer billing identifier for a directory assistance extension call to a switch in a public telephone network |
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 |
JP3940526B2 (en) | 1999-06-04 | 2007-07-04 | 株式会社東芝 | Telephone exchange equipment |
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 |
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 |
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 |
US6301609B1 (en) | 1999-07-07 | 2001-10-09 | Lucent Technologies Inc. | Assignable associate priorities for user-definable instant messaging buddy groups |
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 |
US6470079B1 (en) | 1999-07-09 | 2002-10-22 | Who's Calling, Inc. | System and method for real-time reporting of advertising effectiveness |
US6768790B1 (en) | 1999-07-09 | 2004-07-27 | Pitney Bowes Inc. | Message automated information system and importance navigator |
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 |
US6542596B1 (en) | 1999-08-12 | 2003-04-01 | Bellsouth Intellectual Property Corporation | System and method for privacy management |
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 |
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 |
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 |
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 |
FI108216B (en) | 1999-10-08 | 2001-12-14 | Marioff Corp Oy | Installation to extinguish fire, spray head |
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 |
SE517492C2 (en) | 1999-10-18 | 2002-06-11 | Ericsson Telefon Ab L M | Method and apparatus for connecting a connection in a telecommunications system |
US6594470B1 (en) | 1999-10-28 | 2003-07-15 | Nortel Networks Limited | System and method for remote management of call center operations |
US6882838B1 (en) | 1999-11-04 | 2005-04-19 | Lucent Technologies Inc. | System and method for providing dynamic call disposition service to wireless terminals |
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 |
US6546262B1 (en) | 1999-11-12 | 2003-04-08 | Altec Lansing Technologies, Inc. | Cellular telephone accessory device for a personal computer 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 |
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 |
US6614786B1 (en) | 1999-11-24 | 2003-09-02 | Lucent Technologies Inc. | Enhanced dual mode telephone for internet telephony |
JP2001156921A (en) | 1999-11-30 | 2001-06-08 | Mega Chips Corp | Extension telephone transfer system |
EP1104964B1 (en) * | 1999-12-02 | 2005-03-23 | 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 |
US6853713B1 (en) | 1999-12-17 | 2005-02-08 | Nortel Networks Limited | Client-server network for managing internet protocol voice packets |
US6735292B1 (en) | 1999-12-17 | 2004-05-11 | Worldcom, Inc. | Method and system for priority call processing |
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 |
US7139728B2 (en) | 1999-12-30 | 2006-11-21 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6937713B1 (en) | 1999-12-30 | 2005-08-30 | At&T Corp. | IP call forward profile |
US6917610B1 (en) | 1999-12-30 | 2005-07-12 | At&T Corp. | Activity log for improved call efficiency |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US6373817B1 (en) | 1999-12-30 | 2002-04-16 | At&T Corp. | Chase me system |
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 |
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 |
JP3889541B2 (en) | 2000-01-12 | 2007-03-07 | 三菱電機株式会社 | Wireless communication system, server and communication terminal, and group call control method |
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 |
US6724887B1 (en) * | 2000-01-24 | 2004-04-20 | Verint Systems, Inc. | Method and system for analyzing customer communications with a contact center |
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 |
EP1257983A2 (en) | 2000-02-10 | 2002-11-20 | Jon Shore | Apparatus, systems and methods for wirelessly transacting financial transfers, electronically 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 |
ES2239564T3 (en) | 2000-03-01 | 2005-10-01 | Sony International (Europe) Gmbh | USER PROFILE DATA MANAGEMENT. |
US20030165223A1 (en) | 2000-03-07 | 2003-09-04 | Timmins Timothy A. | Technique for providing a telecommunication service including information assistance |
US7881962B2 (en) | 2000-03-14 | 2011-02-01 | Verizon Business Global Llc | Early-payment discount for E-billing system |
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 |
US7546337B1 (en) | 2000-05-18 | 2009-06-09 | Aol Llc, A Delaware Limited Liability Company | Transferring files |
DE50015061D1 (en) * | 2000-05-26 | 2008-05-08 | Nokia Siemens Networks Gmbh | Method for target control in a smart 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 |
GB0014251D0 (en) * | 2000-06-12 | 2000-08-02 | Hewlett Packard Co | Business innovation method and system |
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 |
US20020069096A1 (en) | 2000-06-22 | 2002-06-06 | Paul Lindoerfer | Method and system for supplier relationship management |
JP2002016673A (en) | 2000-06-28 | 2002-01-18 | Toshiba Corp | Mobile wireless terminal |
US6718026B1 (en) | 2000-06-30 | 2004-04-06 | Verizon Network Services, Inc. | Call forwarding methods and apparatus |
US6694351B1 (en) | 2000-06-30 | 2004-02-17 | Cisco Technology, Inc. | Call optimization in meet-me conference calls |
US7050558B1 (en) | 2000-06-30 | 2006-05-23 | Barry Paul Pershan | Methods and apparatus for enabling/disabling calling forwarding service |
US7167552B1 (en) | 2000-06-30 | 2007-01-23 | Cisco Technology, Inc. | Quorums in meet-me conference calls |
AU7593601A (en) | 2000-07-14 | 2002-01-30 | Atabok Inc | Controlling and managing digital assets |
JP2002041522A (en) * | 2000-07-24 | 2002-02-08 | 4D Communications Inc | Personal information disclosure system and electronic mail distribution system |
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 |
AU2001285023A1 (en) | 2000-08-17 | 2002-02-25 | 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 |
US20020062251A1 (en) | 2000-09-29 | 2002-05-23 | Rajan Anandan | System and method for wireless consumer communications |
US6442251B1 (en) | 2000-09-29 | 2002-08-27 | Palm Incorporated | Method and apparatus for taking a note while in a call |
US20020040355A1 (en) | 2000-10-02 | 2002-04-04 | Weiner Steven D. | System and method for utility meter swipecard |
US7191234B2 (en) | 2000-10-13 | 2007-03-13 | 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 |
GB2368225B (en) | 2000-10-17 | 2003-12-10 | Hewlett Packard Co | Inviting assistant entity into a network communication session |
US20020085701A1 (en) | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified communication management based on presence information |
US7031437B1 (en) * | 2000-10-30 | 2006-04-18 | Nortel Networks Limited | Method and system for providing remote access to previously transmitted enterprise messages |
US20020078153A1 (en) * | 2000-11-02 | 2002-06-20 | Chit Chung | Providing secure, instantaneous, directory-integrated, multiparty, communications services |
US6564553B2 (en) * | 2000-11-09 | 2003-05-20 | Bosch Braking Systems Co., Ltd. | Braking pressure intensifying master cylinder |
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 |
DE60103085T2 (en) * | 2000-11-20 | 2004-11-25 | British Telecommunications P.L.C. | METHOD FOR MANAGING RESOURCES |
US7155001B2 (en) | 2001-10-24 | 2006-12-26 | Sbc Properties, L.P. | System and method for restricting and monitoring telephone calls |
JP2002157807A (en) | 2000-11-21 | 2002-05-31 | Funai Electric Co Ltd | Rotary tray rotating mechanism using magnetic force |
US7317787B2 (en) | 2000-11-21 | 2008-01-08 | At&T Knowledge Ventures, L.P. | Voice enhancing for advance intelligent network services |
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 |
US6788775B1 (en) | 2000-12-11 | 2004-09-07 | Bellsouth Intellectual Property Corporation | System and method for passcode validation during telephone call processing |
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 |
US20020076025A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited And Bell Canada | Method and system for automatic handling of invitations to join communications sessions in a virtual team environment |
US20020077082A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited | Voice message presentation on personal wireless devices |
US20020075303A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited And Bell Canada | Method and system for creating a virtual team environment |
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 |
US20020076027A1 (en) | 2000-12-20 | 2002-06-20 | Nortel Networks Limited | Fallback to message compose on synchronous call attempt |
US7024209B1 (en) * | 2000-12-20 | 2006-04-04 | Cisco Technology, Inc. | Unified messaging system configured for management of short message service-type messages |
US6792092B1 (en) | 2000-12-20 | 2004-09-14 | Cisco Technology, Inc. | Method and system for independent participant control of audio during multiparty communication sessions |
US6847823B2 (en) * | 2000-12-20 | 2005-01-25 | Nokia Corporation | System and method for accessing local services with a mobile terminal |
US6665388B2 (en) | 2000-12-20 | 2003-12-16 | Bellsouth Intellectual Property Corporation | System and method for monitoring incoming communications to a telecommunications device |
US20020083462A1 (en) | 2000-12-21 | 2002-06-27 | Arnott Robert J. | Apparatus and method for establishing audio and video conferencing |
US20020080942A1 (en) * | 2000-12-21 | 2002-06-27 | Clapper Edward O. | Origin-independent custom caller ID |
US7209966B2 (en) * | 2000-12-22 | 2007-04-24 | Openwave Systems Inc. | Method and system for facilitating mediated communication |
US20020082028A1 (en) | 2000-12-22 | 2002-06-27 | Wittenkamp Peter David Forsling | Paging and selective call routing in a telecommunication environment |
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 |
US20020087469A1 (en) | 2000-12-28 | 2002-07-04 | Ravi Ganesan | Technique of registration for and direction of electronic payments in real-time |
US7388949B2 (en) | 2000-12-28 | 2008-06-17 | At&T Delaware Intellectual Property, Inc. | System and method for audio caller identification service |
US20020085515A1 (en) | 2000-12-28 | 2002-07-04 | Jaynes Christopher O. | Object specific information relaying system |
US7069298B2 (en) | 2000-12-29 | 2006-06-27 | Webex Communications, Inc. | Fault-tolerant distributed system for collaborative computing |
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 |
JP3862154B2 (en) * | 2001-01-18 | 2006-12-27 | オムロン株式会社 | Communication mediation system |
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 |
US7136461B1 (en) * | 2001-02-16 | 2006-11-14 | Telesector Resources Group, Inc. | Method and apparatus for implementing voice messaging using E-mail |
JP2002247148A (en) | 2001-02-18 | 2002-08-30 | Tanabe Junzo | Communication controller with phone incoming notice function and notice method |
EP1235387B1 (en) | 2001-02-19 | 2005-12-14 | Alcatel | Method for handling calls received at a wireless mobile terminal comprising a short range interface, and wireless mobile terminal and computer program therefor |
US7606909B1 (en) | 2001-02-20 | 2009-10-20 | Michael Ely | Method and apparatus for a business contact center |
US8467502B2 (en) | 2001-02-27 | 2013-06-18 | Verizon Data Services Llc | Interactive assistant for managing telephone communications |
US7142646B2 (en) | 2001-02-27 | 2006-11-28 | Verizon Data Services Inc. | Voice mail integration with instant messenger |
US20060276179A1 (en) | 2001-02-27 | 2006-12-07 | Reza Ghaffari | Methods and systems for integrating communications services |
JP2002261834A (en) | 2001-02-27 | 2002-09-13 | Ntt Advanced Technology Corp | Method and system for processing communication |
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 |
US7190773B1 (en) | 2001-02-27 | 2007-03-13 | Verizon Data Services Inc. | Device independent caller ID |
US8472931B2 (en) | 2002-11-25 | 2013-06-25 | Telesector Resources Group, Inc. | Methods and systems for automatic communication line management based on device location |
US20050220286A1 (en) | 2001-02-27 | 2005-10-06 | John Valdez | Method and apparatus for facilitating integrated access to communications services in a communication device |
US8774380B2 (en) * | 2001-02-27 | 2014-07-08 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
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 |
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 |
US6988132B2 (en) | 2001-03-15 | 2006-01-17 | Microsoft Corporation | System and method for identifying and establishing preferred modalities or channels for communications based on participants' preferences and contexts |
US7561872B1 (en) | 2001-03-19 | 2009-07-14 | At&T Intellectual Property I, L.P. | Methods and systems for accessing communications services |
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 |
US20020187794A1 (en) | 2001-05-04 | 2002-12-12 | Comverse Network Systems, Ltd. | SMS automatic reply and automatic handling |
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 |
US20030046071A1 (en) * | 2001-09-06 | 2003-03-06 | International Business Machines Corporation | Voice recognition apparatus and method |
US20030058838A1 (en) * | 2001-09-06 | 2003-03-27 | Michael Wengrovitz | System and method for transmitting information via a call center SIP server |
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 |
JP3674561B2 (en) * | 2001-09-25 | 2005-07-20 | 日産自動車株式会社 | Shift control device for automatic clutch transmission |
FI114129B (en) | 2001-09-28 | 2004-08-13 | Nokia Corp | Conference call arrangement |
US7313617B2 (en) | 2001-09-28 | 2007-12-25 | Dale Malik | Methods and systems for a communications and information resource manager |
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 |
US7102643B2 (en) | 2001-11-09 | 2006-09-05 | Vibe Solutions Group, Inc. | Method and apparatus for controlling the visual presentation of data |
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 |
US7116972B1 (en) | 2001-11-16 | 2006-10-03 | Sprint Spectrum L.P. | Method and system for control over call handling |
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 |
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 |
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 |
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 |
US8285255B2 (en) * | 2002-06-10 | 2012-10-09 | Research In Motion Limited | Voicemail user interface methods and apparatus 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 |
US6839417B2 (en) | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
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 |
DE10255489A1 (en) | 2002-11-27 | 2004-06-09 | Deutsche Telekom Ag | Communications system for controlling call forwarding between mobile radio and fixed networks activates call forwarding when short range connection exists between fixed net terminal, mobile device |
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 |
US7321920B2 (en) | 2003-03-21 | 2008-01-22 | Vocel, Inc. | Interactive messaging system |
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,970 patent/US8472931B2/en active Active
- 2003-11-24 US US10/720,859 patent/US7418090B2/en not_active Expired - Fee Related
- 2003-11-24 US US10/720,825 patent/US8761816B2/en not_active Expired - Lifetime
- 2003-11-24 US US10/720,943 patent/US7912199B2/en not_active Expired - Fee Related
- 2003-11-24 US US10/720,920 patent/US8761355B2/en active Active
- 2003-11-25 CA CA2774362A patent/CA2774362C/en not_active Expired - Fee Related
-
2009
- 2009-04-28 JP JP2009109689A patent/JP2009189048A/en active Pending
-
2010
- 2010-06-11 JP JP2010134128A patent/JP2010193532A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
US20040264654A1 (en) | 2004-12-30 |
JP2009189048A (en) | 2009-08-20 |
JP2010193532A (en) | 2010-09-02 |
US8761355B2 (en) | 2014-06-24 |
US20050053214A1 (en) | 2005-03-10 |
US7418090B2 (en) | 2008-08-26 |
US8761816B2 (en) | 2014-06-24 |
US7912199B2 (en) | 2011-03-22 |
US20040213212A1 (en) | 2004-10-28 |
US20050053217A1 (en) | 2005-03-10 |
US8472931B2 (en) | 2013-06-25 |
CA2774362A1 (en) | 2004-06-10 |
US20050148351A1 (en) | 2005-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9392120B2 (en) | Methods and systems for call management with user intervention | |
CA2774362C (en) | Methods and systems for call management with user intervention | |
US7912193B2 (en) | Methods and systems for call management with user intervention | |
US8774380B2 (en) | Methods and systems for call management with user intervention | |
US8750482B2 (en) | Methods and systems for preemptive rejection of calls | |
US8767925B2 (en) | Interactive assistant for managing telephone communications | |
US8488766B2 (en) | Methods and systems for multiuser selective notification | |
US8761363B2 (en) | Methods and systems for automatic forwarding of communications to a preferred device | |
US20060276179A1 (en) | Methods and systems for integrating communications services | |
US20120106728A1 (en) | Methods and systems for integrating communications services | |
US8751571B2 (en) | Methods and systems for CPN triggered collaboration | |
US20110176666A1 (en) | Methods and systems for line management | |
US8472428B2 (en) | Methods and systems for line management | |
CA2507490A1 (en) | Methods and systems for automatic communication line management based on device location | |
CA2507127C (en) | Methods and systems for call management with user intervention | |
JP4473137B2 (en) | Method and system for preemptively rejecting a telephone call | |
EP1568169A2 (en) | Methods and systems for automatic forwarding of communications to a preferred device | |
EP1568196A1 (en) | Methods and systems for line management | |
EP1568201A1 (en) | Methods and systems for cpn triggered collaboration | |
WO2004049183A1 (en) | Methods and systems for multiuser selective notification |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20161125 |