CA2507492C - Methods and systems for a call log - Google Patents
Methods and systems for a call log Download PDFInfo
- Publication number
- CA2507492C CA2507492C CA2507492A CA2507492A CA2507492C CA 2507492 C CA2507492 C CA 2507492C CA 2507492 A CA2507492 A CA 2507492A CA 2507492 A CA2507492 A CA 2507492A CA 2507492 C CA2507492 C CA 2507492C
- Authority
- CA
- Canada
- Prior art keywords
- user
- information
- network
- call
- log
- 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/22—Arrangements for supervision, monitoring or testing
- H04M3/2218—Call detail recording
-
- 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
- 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/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/22—Arrangements for supervision, monitoring or testing
- H04M3/36—Statistical metering, e.g. recording occasions when traffic exceeds capacity of trunks
-
- 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/42221—Conversation recording 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/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/55—Aspects of automatic or semi-automatic exchanges related to network data storage and management
- H04M2203/551—Call history
-
- 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/01—Details of billing arrangements
- H04M2215/0164—Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
-
- 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/48—Arrangements for recalling a calling subscriber when the wanted subscriber ceases to be busy
-
- 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
A call log (Fig. 6, 610) associated with outgoing calls originating from calling devices (118) may be established and maintained. Filter parameters may be set to specify which outgoing calls to log. Outgoing call information associated with calls originating from a user's calling devices may be obtained and transmitted to a service center (406). A server in the service center may determine whether or not to log the outgoing call information based on the filter settings. The outgoing call information may be stored in the call log, which may reside in a database in the service center. The user may access the call log from a user terminal and/or the calling devices. The call log may be used to add contacts to a contact list and facilitate data analyses.
Description
METHODS AND SYSTEMS FOR A CALL LOG
DESCRIPTION OF THE INVENTION
Technical Field [001] The present invention generally relates to communication systems and, more specifically, to methods and systems for logging and managing outgoing call information.
Background [003] A wide variety of means exist for communication between users.
For example, a user may conduct phone calls via a home phone, work phone, and mobile phone. In addition, users may also communicate using devices such as PC's, PDA's, pagers, etc. using, for example, email and instant messaging.
[004] Unfortunately, managing such a wide variety of communication means can be difficult. In particular, as a user changes location, communication with the user may vary. For example, while on travel, it may only be possible to reach a user by mobile phone. However, the user may best be reached by email while at work. Also, the user may wish to implement various rules for receiving and controlling communications. For example, to be reached at home, the user may want the home phone to ring three times before forwarding the call to a mobile phone. As another example, the user may wish to be paged each time an email is received from a particular person while away from the office.
[005] Typically, to implement communication management, a person must individually manage each communication device separately. Thus, when the user wishes to change how communication is managed, the user may have to deal with numerous devices and, perhaps, service centers.
[006] Further, call management is becoming increasingly difficult given the variety of communication devices and services. Especially with outgoing calls, conventional communication system provide users with limited features. One feature often provided by conventional systems is "redial,"
which enables a user to initiate a call to a previously dialed number without re-inputting that number. Certain systems (e.g., digital cell phones) allow users to locally store phone numbers in a contact list, which is usually a FIFO or rolling list with limited storage capacity. In such systems, the user typically must perform an action to insert phone numbers in the contact list. For example, in a cell phone, the user must enter in phone numbers via a keypad and instruct the device to save the entered numbers. Certain systems may automatically store all outgoing and incoming calls in a rolling list as they are dialed and received; however, such systems typically provide limited FIFO
storage and usually store only the numbers. Current communication systems do not provide users with filtering and exclusion options for outgoing call storage, and these systems do not allow users to obtain caller information from the dialed numbers. Moreover, conventional systems do not facilitate coordination and management of outgoing calls originating from several devices (e.g., cell phones, laptops, PDAs, J2ME phones, BREW phones, etc. ).
[007] Methods, systems, and articles of manufacture consistent with certain embodiments of the present invention are directed to obviating one or more of the issues set forth above.
SUMMARY
[008] Systems and methods consistent with the present invention may log information associated with outgoing calls in a call log. In one embodiment of the present invention, systems and methods may be provided for receiving instructions from a user that specify filtering preferences for logging outgoing calls. For example, a user may specify a list of telephone numbers that, when dialed, should be excluded from or included in the call log. In one embodiment, the user may specify filter settings via a user terminal coupled to a server. Methods and systems consistent with the present invention may obtain outgoing call information associated with a call originating from a calling device and destined to a called device. For example, a programmable wireless telephone may be configured to capture outgoing call information (e.g., a dialed telephone number). In another example, outgoing call information may be obtained via a service control point associated with a landline telephone. Consistent with principles of the present invention, outgoing call information may be transmitted to a server residing in a service center. Systems and methods consistent with the present invention may determine whether or not to log the outgoing call information based on the filter settings (e.g., the server may consult the exclusion list). If an outgoing call passes through filtering, the outgoing call information may be stored in a call log, which may, in certain implementations, reside in a database in the service center. Systems and methods consistent with the present invention may provide the user with access to the call log (e.g., via the user terminal):
[009] In certain embodiments consistent with the present invention, systems and methods may use the call log to add contacts to a contact list.
Consistent with principles of the present invention, contact-related information associated with a called party may be retrieved using the call log. For example, a server in the service center may retrieve contact-related information using the dialed number. The retrieved contact information may then be added to the contact list.
[010] In certain embodiments consistent with the present invention, systems and methods may perform data analyses using the call log. For example, calling patterns and/or frequencies may be processed via information in the call log and presented to the user.
[011] In certain embodiments consistent with the present invention, systems and methods may log and manage calls associated with a plurality of devices. Methods and systems may obtain information associated with outgoing calls originating from each of a plurality of source communication devices and destined to one or more destination devices. For example, information associated with outbound calls originating from a user's cell phone, landline phone, and PDA may be obtained. Methods and systems consistent with the present invention may store the outgoing call information associated with each of a user's devices in a call log. In certain embodiments, users may set filtering settings for each device, and outgoing calls from each device may be stored in the call log based on the filtering settings. The call log may be accessible by the user terminal andlor one or more of the devices.
[012] Both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention in any manner whatsoever.
BRIEF DESCRIPTION OF THE DRAWINGS
[013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the description, serve to explain principles of the invention. In the drawings:
[014] 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;
[015] Fig. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[016] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[017] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[018] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[019] Fig. 6 is a diagram graphically illustrating methods consistent with certain embodiments of the present invention; and [020] Fig. 7 is a flowchart depicting stages of a method consistent with certain embodiments of the present invention.
DESCRIPTION OF THE INVENTION
Technical Field [001] The present invention generally relates to communication systems and, more specifically, to methods and systems for logging and managing outgoing call information.
Background [003] A wide variety of means exist for communication between users.
For example, a user may conduct phone calls via a home phone, work phone, and mobile phone. In addition, users may also communicate using devices such as PC's, PDA's, pagers, etc. using, for example, email and instant messaging.
[004] Unfortunately, managing such a wide variety of communication means can be difficult. In particular, as a user changes location, communication with the user may vary. For example, while on travel, it may only be possible to reach a user by mobile phone. However, the user may best be reached by email while at work. Also, the user may wish to implement various rules for receiving and controlling communications. For example, to be reached at home, the user may want the home phone to ring three times before forwarding the call to a mobile phone. As another example, the user may wish to be paged each time an email is received from a particular person while away from the office.
[005] Typically, to implement communication management, a person must individually manage each communication device separately. Thus, when the user wishes to change how communication is managed, the user may have to deal with numerous devices and, perhaps, service centers.
[006] Further, call management is becoming increasingly difficult given the variety of communication devices and services. Especially with outgoing calls, conventional communication system provide users with limited features. One feature often provided by conventional systems is "redial,"
which enables a user to initiate a call to a previously dialed number without re-inputting that number. Certain systems (e.g., digital cell phones) allow users to locally store phone numbers in a contact list, which is usually a FIFO or rolling list with limited storage capacity. In such systems, the user typically must perform an action to insert phone numbers in the contact list. For example, in a cell phone, the user must enter in phone numbers via a keypad and instruct the device to save the entered numbers. Certain systems may automatically store all outgoing and incoming calls in a rolling list as they are dialed and received; however, such systems typically provide limited FIFO
storage and usually store only the numbers. Current communication systems do not provide users with filtering and exclusion options for outgoing call storage, and these systems do not allow users to obtain caller information from the dialed numbers. Moreover, conventional systems do not facilitate coordination and management of outgoing calls originating from several devices (e.g., cell phones, laptops, PDAs, J2ME phones, BREW phones, etc. ).
[007] Methods, systems, and articles of manufacture consistent with certain embodiments of the present invention are directed to obviating one or more of the issues set forth above.
SUMMARY
[008] Systems and methods consistent with the present invention may log information associated with outgoing calls in a call log. In one embodiment of the present invention, systems and methods may be provided for receiving instructions from a user that specify filtering preferences for logging outgoing calls. For example, a user may specify a list of telephone numbers that, when dialed, should be excluded from or included in the call log. In one embodiment, the user may specify filter settings via a user terminal coupled to a server. Methods and systems consistent with the present invention may obtain outgoing call information associated with a call originating from a calling device and destined to a called device. For example, a programmable wireless telephone may be configured to capture outgoing call information (e.g., a dialed telephone number). In another example, outgoing call information may be obtained via a service control point associated with a landline telephone. Consistent with principles of the present invention, outgoing call information may be transmitted to a server residing in a service center. Systems and methods consistent with the present invention may determine whether or not to log the outgoing call information based on the filter settings (e.g., the server may consult the exclusion list). If an outgoing call passes through filtering, the outgoing call information may be stored in a call log, which may, in certain implementations, reside in a database in the service center. Systems and methods consistent with the present invention may provide the user with access to the call log (e.g., via the user terminal):
[009] In certain embodiments consistent with the present invention, systems and methods may use the call log to add contacts to a contact list.
Consistent with principles of the present invention, contact-related information associated with a called party may be retrieved using the call log. For example, a server in the service center may retrieve contact-related information using the dialed number. The retrieved contact information may then be added to the contact list.
[010] In certain embodiments consistent with the present invention, systems and methods may perform data analyses using the call log. For example, calling patterns and/or frequencies may be processed via information in the call log and presented to the user.
[011] In certain embodiments consistent with the present invention, systems and methods may log and manage calls associated with a plurality of devices. Methods and systems may obtain information associated with outgoing calls originating from each of a plurality of source communication devices and destined to one or more destination devices. For example, information associated with outbound calls originating from a user's cell phone, landline phone, and PDA may be obtained. Methods and systems consistent with the present invention may store the outgoing call information associated with each of a user's devices in a call log. In certain embodiments, users may set filtering settings for each device, and outgoing calls from each device may be stored in the call log based on the filtering settings. The call log may be accessible by the user terminal andlor one or more of the devices.
[012] Both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention in any manner whatsoever.
BRIEF DESCRIPTION OF THE DRAWINGS
[013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the description, serve to explain principles of the invention. In the drawings:
[014] 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;
[015] Fig. 2 is a diagram of an exemplary user terminal, consistent with the principals of the present invention;
[016] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention;
[017] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention;
[018] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention;
[019] Fig. 6 is a diagram graphically illustrating methods consistent with certain embodiments of the present invention; and [020] Fig. 7 is a flowchart depicting stages of a method consistent with certain embodiments of the present invention.
5~
DETAILED DESCRIPTION
[021] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the figures to refer to the same or like elements. The accompanying figures illustrate exemplary embodiments and implementations consistent with the present invention, but the description of those embodiments does not indicate or imply that other embodiments or implementations do not fall within the scope of present invention. It is to be understood that other implementations may be utilized and that structural and method changes may be made without departing from the scope of present invention.
[022] Fig. 1 is a block diagram of a data processing and telecommunications environment 100, in which features and aspects consistent with the present invention may be implemented. The number of components in environment 100 is not limited to what is shown and other variations in the number of arrangements of components are possible, consistent with embodiments of the invention. The components of Fig. 1 may be implemented through hardware, software, and/or firmware. Data processing and telecommunications environment 100 may include a data network 102, a voice network 104, and a service center 106. A user 110 may use a user terminal 112 to interface with data network 102 and may use phones 114, 116, arid 118 to interface with voice network 104. Calling party 120 may use phone 122 to call a user, such as user 110, at any one of phones 114, 116, and 118.
[023] Data network 102 provides communications between the various entities depicted in environment 100 of Fig. 1, such as user terminal 112 and service center 106. Data network 102 may be a shared, public, or private network and encompass a wide area or local area. Data network 102 may be implemented through any suitable combination of wired and/or wireless communication networks. By way of example, data network 102 may be implemented through a wide area network (WAN), local area network (LAN), an intranet andlor the Internet. Further, the service center 106 may be connected to multiple data networks 102, such as, for example, to a wireless carrier network and to the Internet.
[024] Voice network 104 may provide telephony services to allow a calling party, such as calling party 120, to place a telephone call to user 110.
In one embodiment, voice network 104 may be implemented using a network, such as the Public Switched Telephone Network ("PSTN"). Alternatively, voice network 104 may be implemented using voice-over Internet Protocol ("VoIP") technology. In addition, voice network 104 may be implemented using both PSTN and VoIP technology consistent with the principles of the present invention. Further, service center 106 may be connected to multiple voice networks 104, such as for example, Verizon'sT"" Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[025] Service center 106 provides a platform for managing communications over data network 102 and voice network 104. Service center 106 also provides gateway functions, such as code and protocol 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.
[026] User terminal 112 provides user 110 an interface to data network 102. For example, user terminal 112 may be implemented using any device capable of accessing the Internet, such as a general purpose computer or personal computer equipped with a modem. User terminal 112 may also be implemented in other devices, such as the BlackberryT"", and Ergo AudreyT"". Furthermore, user terminal 112 may be implemented in wireless devices, such as pagers, mobile phones (with data access functions), and Personal Digital Assistants ("PDA") with network connections.
[027] User terminal 112 also allows user 110 to communicate with service center 106. For example, user 110 may use instant messaging ("IM") to communicate with service center 106. In addition, user terminal 112 may use other aspects of TCPIIP including the hypertext transfer protocol ("HTTP"); the user datagram protocol ("UDP"); the file transfer protocol ("FTP"); the hypertext markup language ("HTML"); and the extensible markup language ("XML").
[028] Furthermore, user terminal 112 may communicate directly with service center 106. For example, a client application may be installed on user terminal 112, which directly communicates with service center 106. Also, user terminal 112 may communicate with service center 106 via a proxy.
[029] Phones 114, 116, 118, and 122 interface with voice network 104. Phones 114, 116, 118, and 122 may be implemented using known devices, including wireline phones and mobile phones. In certain embodiments of the present invention, phones 114, 116, 118, and 122 may include programmable calling devices such as BREW phones, J2ME phones, PDAs, and laptops and may be compatible with PSTN and/or VoIP
techne~logy. Although phones 114, 116, 118, and 122 are shown directly connected to voice network 104, any number of intervening elements, such as a private branch exchange ("PBX"), may be interposed between phones 114, 116, 118, and 122 and voice network 104.
[030] Fig. 2 is a block diagram of user terminal 112 consistent with the present invention. User terminal 112 includes a central processing unit (CPU) 200, a memory 202, a storage module 204, a network interface 206, an input interface 208, an output interface 210, an input device 216, and an output device 218.
[031] CPU 200 provides control and processing functions for user terminal 112. Although Fig. 2 illustrates a single CPU, user terminal 112 may include multiple CPUs. CPU 200 may also include, for example, one or more of the following: a co-processor, memory, registers, and other processing devices and systems as appropriate. CPU 200 may be implemented, for example, using a PentiumT"" processor provided from Intel Corporation.
[032] Memory 202 provides a primary memory for CPU 200, such as for program code. Memory 202 may be embodied with a variety of components of subsystems, including a random access memory ("RAM") and a read-only memory ("ROM"). When user terminal 112 executes an application installed in storage module 204, CPU 200 may download at least a portion of the program code from storage module 204 into memory 202. As CPU 200 executes the program code, CPU 200 may also retrieve additional portions of program code from storage module 204.
[033] Storage module 204 may provide mass storage for user terminal 112. Storage module 204 may be implemented with a variety of components or subsystems including, for example, a hard drive, an optical drive, CD ROM
drive, DVD drive, a general-purpose storage device, a removable storage device, and/or other devices capable of storing information. Further, although storage module 204 is shown within user terminal 112, storage module 204 may be implemented external to user terminal 112.
[034] Storage module 204 includes program code and information for user terminal 112 to communicate with service center 106. Storage module 204 may include, for example, program code for a calendar application, such as GroupWise provided by Novell Corporation or Outlook provided by Microsoft Corporation; a client application, such as a Microsoft Network Messenger Service (MSNMS) client or America Online Instant Messenger (AIM) client; and an Operating System (OS), such as the Windows Operation System provided by Microsoft Corporation. In addition, storage module 204 may include other program code and information, such as program code for TCP/IP communications; kernel and device drivers; configuration information, such as a Dynamic Host Configuration Protocol (DHCP) configuration; a web browser, such as Internet Explorer provided by Microsoft Corporation, or Netscape Communicator provided by Netscape Corporation; and any other software that may be installed on user terminal 112.
[035] Network interface 206 provides a communications interface between user terminal 112 and data network 102. Network interface 206 may receive and transmit communications for user terminal 112. For example, network interface 206 may be a modem, or a local area network ("LAN") port.
[036] Input interface 208 receives input from user 110 via input device 212 and provides the input to CPU 200. Input device 212 may include, for example, a keyboard, a microphone, and a mouse. Other types of input devices may also be implemented consistent with the principles of the present invention.
[037] Output interface 210 provides information to user 110 via output device 214. Output device 214 may include, for example, a display, a printer, and a speaker. Other types of output devices may also be implemented consistent with the principles of the present invention.
[038] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention. As shown, voice network 104 includes an intelligent service control point (ISCP) 302, service transfer points (STP) and 306, service switching points (SSP) 308 and 310, a line information database (LIDB) 312, an ISCP Service Provisioning And Creation Environment (SPACE) 314, a Recent Change Environment 316, and an Intelligent Peripheral (IP) 320.
[039] Voice network 104 may be implemented using the PSTN and SS7 as a signaling protocol. The SS7 protocol allows voice network 104 to provide features, such as call forwarding, caller-ID, three-way calling, wireless services such as roaming and mobile subscriber authentication, local number portability, and toll-free/toll services. The SS7 protocol provides various types of messages to support the features of voice network 104. For example, these SS7 messages may include Transaction Capabilities Applications Part ("TCAP") messages to support event "triggers," and queries and responses between ISCP 302 and SSPs 308 and 310.
[040] ISCP 302 may also be, for example, a standard service control point (SCP) or an Advanced Intelligent Network (AIN) SCP. ISCP 302 provides translation and routing services of SS7 messages to support the features of voice network 104, such as call forwarding. In addition, ISCP 302 may exchange information with the service center 106 using TCP/IP or SS7.
ISCP 302 may be implemented using a combination of known hardware and software. Although ISCP 302 is shown with a direct connection to service center 106 through ISCP SPACE 314, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP 302 and service center 106.
[041] STPs 304 and 306 relay SS7 messages within voice network 104. For example, STP 304 may route SS7 messages between SSPs 308 and 310. STP 302 may be implemented using known hardware and software from manufacturers such as NORTELT"' and LUCENT TechnologiesT""
[042] SSPs 308 and 310 provide an interface between voice network 104 and phones 114 and 120, respectively, to setup, manage, and release telephone calls within voice network 104. SSPs 308 and 310 may be implemented as a voice switch, an SS7 switch, or a computer connected to a switch. SSPs 308 and 310 exchange SS7 signal units to support a telephone call between calling party 120 and user 110. For example, SSPs 308 and 310 may exchange SS7 messages, such as TCAP messages, within message signal units ("MSU") to control calls, perform database queries to configuration database 312, and provide maintenance information.
[043] Line Information Database (LIDB) 312 comprises one or more known databases to support the features of voice network 104. For example, LIDB 312 may include subscriber information, such as a service profile, name and address, and credit card validation information.
[044] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of ISCP 302 or be separate from ISCP 302. For example, the TelcordiaT"" ISCP may include an environment similar to SPACE
314 as part of the product. Further, ISCP SPACE 314 may include one or more servers. ISCP SPACE 314 is the point in the ISCP platform where customer record updates may be made.
[045] In one embodiment, customer records may be stored in ISCP
SPACE 314 such that the records may be updated and sent to ISCP 302.
These records may include information regarding how to handle calls directed to the customer. For example, these customer records may include information regarding whether or not calls for the customer are to be forwarded to a different number, 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).
[046] Additionally, voice network 104 may include one or more recent change engines 316 such as, for example, an Enterprise Recent Change engine (eRC); an Assignment, Activation, and Inventory System (AAIS); or a multi-services platform (MSP). As an example, the eRC and AAIS may be used in voice networks 104 located in the western part of the United States, while an MSP may be used in networks in the eastern part. The recent change engines may be used to update switch and ISCP databases. For example, a recent change engine may deliver database updates to SSPs and to ISCPs, such that when updating databases, these recent change engines emulate human operators. Additionally, if the instructions are to be sent to an ISCP 302, the recent change engine may first send the instructions to ISCP
SPACE 314, which then propagates the instructions to ISCP 302 as discussed above. Further, an MSP may be used, for example, for providing updates to both SSPs 308 or 310 and ISCPs 302. Or, for example, an eRC
may be used for providing updates to SSPs 308 or 310, while an AAIS is used for providing updates to ISCPs 302.
[047] Additionally, voice network 104 may include one or more intelligent peripherals (IP). For example, in Fig. 4, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing services, such as voice mail services.
[048] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention. As shown, service center 106 may include firewalls 402 and 404, one or more digital companion servers 406, one or more communication portal servers 408, one or more network access servers 410, and a voice portal 412. Voice portal 412 may include a voice portal application server 414 and a voice recognition server 416. A network 418 may be used to interconnect the firewalls and servers. Additionally, back end servers) 420 may be provided between service center 106 and voice network 104.
[049] Firewalls 402 and 404 provide security services for communications between service center 106, data network 102, and voice network 104, respectively. For example, firewalls 402 and 404 may restrict communications between user terminal 112 and one or more servers within service center 106. Any security policy may be implemented in firewalls 402 and 404 consistent with the principles of the present invention. Firewalls 402 and 404 may be implemented using a combination of known hardware and software, such as the Raptor Firewall provided by the Axent Corporation.
Further, firewalls 402 and 404 may be implemented as separate machines within service center 106, or implemented on one or more machines external to service center 106.
[050] Network 418 may be any type of network, such as an Ethernet or FDDI network. Additionally, network 418 may also include switches and routers as appropriate without departing from the scope of the invention.
Further, additional firewalls may be present in network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[051 ] Each server (406, 408, 410, 414, 416, 420) may be any type of server or computer, such as a Unix or DOS based server or computer. The servers may implement various logical functions, such as those described below. In Fig. 4, a different server is illustrated as being used for each logical function. In other embodiments, the logical functions may be split across multiple servers, multiple servers may be used to implement a single function, all functions may be performed by a single server, etc.
[052] In general, a digital companion server 406 may provide the software and hardware for providing specific services of the service center.
Exemplary services include, for example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name andlor address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, digital companion server 406 may log and perform operations on outgoing calf information associated with a particular subscriber (i.e., user 110). Outgoing call information may be logged/recorded from any of user 110's devices (e.g., 114, 116, 118).
[053] A communication portal server 408 may provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. Network access servers 410 may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may be used for transmitting and/or receiving information from/to an ISCP 302 or an SSP 308 or 310 of voice network 104.
[054] Voice portal 412 includes software and hardware for receiving and processing instructions from a customer via voice. For example, a customer may dial a specific number for voice portal 412. Then the customer using speech may instruct service center 106 to modify the services to which the customer subscribes. Voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. Voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. Application function 414 may take, for example, the output from voice recognition function 416, convert it to a format suitable for service center 106 and forward the information to one or more servers (406, 408, 410) in service center 106.
[055] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention. As illustrated, the logical architecture may be split into four planes: client side plane 502, application service plane 504, network access plane 506, and voice network plane 508.
[056] Client side plane 502 includes the user terminals 112 A and 112_B that a user may use to send and/or receive information to/from the service center 106. Additionally, client side 502 includes the user's phones) 114. As discussed above, user terminals 112 may be any type of device a user may use for communicating with Service Center 106. For example, user terminal 112 A may be a PDA running a program for communicating with Service Center 106, while user terminal 112_B may be a desktop type computer running a web browser for communicating with Service Center 106 via the Internet. Additionally, the user may have one or more phones 114, such as, for example, one or more standard landline telephones and/or wireless phones.
[057] Application service plane 504 includes digital companion servers) 406, communication portal servers) 408, and voice portal 412.
These entities may communicate between one another using, for example, web services or any other suitable protocols. Web services are a standardised way of integrating Web-based applications using the Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) open standards over an Internet protocol (IP) backbone.
[058] As illustrated, a digital companion server 406 may provide .the following functions: a client proxy 512, a web server 514, an application server function 516, a calendar server function 5_18, a notification server function 520, and a database function 522. Each of these functions may be performed in hardware, software, andlor firmware. Further, these functions may each be executed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[059] Client proxy function 512 provides a proxy function for the digital companion that may be used for security purposes. This client proxy function 512 may be included in a separate server such that all communications sent from the other digital companion functions/servers to a user terminal 112 via data network 102 go through client proxy 512. Also, if client proxy 512 is included on a separate server, for example, an additional firewall may be provided between the client proxy 512 and the other digital companion servers to provide additional security.
[060] Web server 514 provides functionality for receiving traffic over data network 102 from a customer. For example, web server 514 may be a standard web server that a customer may access using a web browser program, such as Internet Explorer or Netscape Communicator.
[061] Application server function 516 encompasses the general functions performed by digital companion servers) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific applications provided by the service center.
These services may include, for example, interfacing with other function(s), software, andlor hardware to provide a customer with the capability of managing their calls online. For example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, application server function 516 may facilitate logging and processing outgoing call information associated with a particular subscriber. Application server function 516 may log/record outgoing call information from any of a particular user 110's devices (e.g., 114, 116, 118). Application server function 516 may store the outgoing calf information, display the information to a subscriber (110), and perform various operations on the information.
[062] Additionally, application server function 516 may interface with one or more external devices, such as an external web server, for retrieving or sending information. For example, application server function 516 may interface with a voice network's data center 556 (e.g., verizon.com) to determine the services to which the customer subscribes (e.g., call waiting, call forwarding, voice mail, etc.).
[063] Calendar server function 518 may provide the capability of scheduling events, logging when certain events occurred, triggering the application-functions to perform a function at a particular time, etc.
[064] Notification server function 520 provides the capability to send information from service center 106 to a user terminal 112. For example, notification server function 520 at the direction of application server function 516 may send a notification to user terminal 112 that the user is presently receiving a phone call at user's phone 114.
[065] Database function 522 provides the storage of information useable by the various applications executed by the digital companion servers. These databases may be included in, for example, one or more external storage devices connected to the digital companion servers.
Alternatively, the databases may be included in storage devices within the digital companion servers themselves. The storage devices providing database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[066] As discussed above, communication portal servers) 408 provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. As illustrated in Fig. 5, a communication portal server 408 may provide the following functions: a web server function 526, an application server function 528, a contacts database function 530, and/or a customer profile function 532. Each of these functions may be performed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[067] Web server function 526, as with web server function 522 of the digital companion servers, provides functionality for receiving traffic over data network 102 from a customer. For example, the web server may be a standard web server that a customer may access using a web browser, such as Internet Explorer or Netscape Communicator.
[068] Application server function 528 encompasses the general functions performed by communication portal servers 406. For example, these functions may include interfacing with the voice network to retrieve and/or modify customer profile information, and creating and editing an address book for the user. Additionally, application server function 528 may include the functionality of sending andlor receiving information to/from external servers and/or devices. For example, communication portal servers 408 may be connected to a network, such as, the Internet. Application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages webpage.
Application function 528 could then contact these external services 552 to retrieve information, such as an address for a person in the user's address book.
[069] In another example, application server function 528 of communication portal 408 may interface a single sign on (SSO) server 554.
SSO 554 may be used to allow users to access all services to which the user subscribes, on the basis of a single authentication that is performed when they initially access the network.
[070] Contacts database 530 includes storage devices for storing an address book for the user. This address book may be any type of address book. For example, the user's address book may include the names, phone numbers, and addresses of people and/or organizations. These storage devices may be internal or external to communication portal servers 406 or same combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[071] Customer profile database 532 includes storage devices for storing customer profile information for the user. These storage devices may be the same or separate storage devices used for the contacts database.
The customer profile may include information regarding the user's account for their voice network. For example, this information may include the user's name, billing address, and other account information. Additionally, the customer profile may include information regarding voice services to which the user subscribes, such as, for example, call waiting, voice mail, etc.
[072] Additionally, application services plane 504 of the architecture may include a voice portal 412. As discussed above, voice portal 412 may include, for example, a voice recognition function 416 and an application server function 414, and be used for receiving and processing instructions from a customer via voice. The voice recognition function may be implemented using hardware and/or software capable of providing voice recognition capabilities. This hardware and/or software may be a commercially available product, such as the Voice Application platform available from Tellme Networks, Incorporated. Application server function 414 of voice portal 412 may include hardware and/or software for exchanging information between digital companion servers 406 and voice recognition function 416. Additionally, application server function 414 may be included on a separate server, included in the hardware and software providing voice recognition function 416, included in digital companion servers 406, etc.
[073] Network Access plane 506 of the architecture includes the functions for providing connectivity between application service plane 502 and voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[074] As discussed above, recent change engines 316 may be used to update switches and ISCP databases included in voice network 104. In one embodiment, recent change engines 316 may include an AAIS 544, an eRC 546, and/or an MSP 548. Additionally, a proxy 542 may be used between digital companion servers 406 and recent change engines 542 for security purposes.
[075] Network access servers 410 may be included in the service center 106 and may provide the hardware and software for sending and receiving information to voice network 410 in processing the applications provided by the service center. For example, network access servers 410 may include a Caller iD (CID) functionality for retrieving caller ID
information from voice network 104, a click to dial (CTD) functionality for instructing an intelligent peripheral (IP) in the voice network to place a call via an SSP, and/or a real time call management (RTCM) functionality for interfacing with an ISCP of the voice network.
[076] Network Access plane 506 may also include one or more back end servers) 420. These back end servers) 420 may include hardware and/or software for interfacing service center 106 and voice network 104.
Back end servers) 420 may be connected to service center 106 by a network, by a direct connection, or in any other suitable manner. Further, back end servers) 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner.
[077] Back end servers) 420 may include, for example, a server providing a voice mail retrieval and notification function. For example, this voice mail retrieval and notification function may include the capability to receive notifications when a user receives a voice mail, physically call a user's voice mail system, enter the appropriate codes to retrieve the voice mail, retrieve the voice mail, convert the voice mail to a digital file, and send it to digital companion servers 406.
[078] Additionally, back end servers) 420 may also include, for example, a directory assistance server. This directory assistance server may, for example, interface service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of voice network 104. A RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of voice network 104 for name and/or address information associated with a phone number and receiving the name and/or phone number in response to this request.
[079] In another example, back end servers) 420 may include a wireless Internet gateway that is used for interfacing with a mobile switching center (MSC) of a wireless voice network. As with the above-described back end servers) 420, this wireless Internet gateway may be used for converting requests and information between the formats used by service center 106 and those used by the wireless voice network.
[080] In yet another example, back end servers) 420 may include a conference blasting server for instructing a conference bridge in the voice network 106 to dial out via an SSP to the participants of a voice conference.
Or for example, the back end servers) may include a server for instructing an IP of the voice network to place a call between two parties by dialing out to each of the parties. Back end servers) 420 may also include the capability to instruct the bridge or IP device to call an audio digitizing device that can listen to the conference, convert the audio signals to digital format, and forward the digitized signals to a user device via, for example, an audio streaming server.
The audio streaming server may, for example, allow a user to connect to it via, for example, the Internet. Additionally, the audio streaming device may buffer or record the signals to permit the user to pause, rewind, and/or fast-forward thru the conference.
[081] In yet another example, back end servers) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a SMS gateway in voice network 104. This may be used for example to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the user's choosing.
[082] Voice network plane 508 includes the hardware and software included in voice network 104, as discussed above with reference to Fig. 3.
For example, voice network plane 508 may include ISCP SPACE 314, ISCP
302, intelligent peripherals 320, and SSP 308. Additionally, voice network plane 508 may also include the hardware and software included in a wireless carrier's network, such as, for example, the mobile switching center, etc.
[083] For clarity of explanation, system 100 is described herein with reference to the discrete functional elements illustrated in Figs. 1-5.
However, it should be understood that the functionality of these elements and modules may overlap and/or may exist in a fewer or greater number of elements and modules. Elements of system 100 may, depending on the implementation, lack certain illustrated components and/or contain, or be coupled to, additional or varying components not shown. Moreover, all or part of the functionality of the elements illustrated in Figs. 1-5 may co-exist or be distributed among several geographically dispersed locations.
[084] As described above, outgoing call information from any of a user's (e.g., 110) devices may be stored in a call log. As used herein, the term "log" refers to a compilation or listing of data. Forms of the term "log"
also refer to the act of compiling, storing, and/or recording information. A
"call log" refers herein to a log of information associated with outbound calls originating from one or more devices associated with a particular user. A
"call" may include a telephone call placed from one or more communication devices (e.g., landline phone, cell phone, etc.). The term "call" may also encompass other types of communications, such as e-mails, instant messages, facsimiles, etc.
[085] Fig. 6 diagrammatically illustrates an overview of call log processes and features consistent with certain embodiments of the present invention. As depicted in Fig. 6, user 110, as a calling party, may place a call using a calling device (e.g., telephone 118) to a called party 605. Methods and systems consistent with the present invention may obtain information associated with the outgoing call and store the information in a call log 610.
1n certain embodiments of the present invention, the call log may be implemented via one or more data files andlor structures residing on (or distributed among) one or more storage devices. For example, as illustrated in Fig. 6, call log 610 may be stored via database function 522. Additionally or alternatively, all or part of call log 610 may reside in storage 204 on user terminal 112. In one embodiment, call log 610 may include, for each outbound call, one or more of the following data elements: the dialed number, information associated with the calling device and/or party, information associated with the called device and/or party, and a time stamp.
[086] In certain embodiments of the present invention, call log 601 may include or reference contact-related information associated with called parties. Consistent with principles of the present invention, such contact-related information may include one or more of a name, home address, business address, home telephone number, business telephone number, cell phone number, instant messenger address, IP address, biometric information (e.g., fingerprints, voice prints, retinal scans, etc.) visual information (e.g., digital images, photographs, etc.), audio information, personal information (e.g., birth date, favorite movies, favorite songs, etc.), public records, credit reports, police records, driving records, banking statements, and contact-related information associated with relatives and/or friends. In certain embodiments, contact-related information may include information associated with, or retrieved via, one or more networks.
[087] User 110 may access call log 610 via, for example, user terminal 112 or telephone 118. In certain embodiments, information in the calf fog may be organized hierarchically, enabling users to explore detailed information (e.g., details of a specific call), as well as broader views (e.g., overall tailing patterns, etc). Additional features associated with the call log are discussed below.
[088] In exemplary embodiments, systems and methods consistent with the present invention may provide to the user filtering and/or processing options for the call log. For example, user 110 may set up an exclusion list in order to preclude entry of certain calls from the call log. The exclusion list may be based on, for example, any one or combination of the following:
outgoing number types (e.g., 800 numbers, 411, etc.), called device types and called party location. Also, the exclusion list may, in one configuration, enable user 110 to exclude calls to certain parties during certain time periods. In one embodiment, user 110 may establish, access, and modify the exclusion list via user terminal 112 and digital companion server 406. Additional details of call log filtering and processing are discussed below.
[089] In certain embodiments of the present invention, outgoing call information originating from a plurality of calling devices associated with a user may be logged and managed. For example, calls originating from a cell phone, landline phone (e.g., 118), and PDA associated with user 110 may be logged. User 110 may set specific filtering settings for logging calls placed from each calling device. In one embodiment, such filtering setting may be specified through the exclusion list. The exclusion list could therefore specify certain types of outgoing calls from each of a user's calling devices that should be excluded from the call log. For example, user 110 could exclude 800 calls from a landline phone and 411 calls from a cell phone. User 110 could also specify, for example, that all calls made from a particular device should be excluded from or included in the call log. User 110 could also specify that calls made to certain parties should be excluded from or included in the call log. Certain filtering settings may allow users to specify that calls made during a certain time period or time of day should be included or excluded in the call log. In addition, certain filtering settings may allow users to log (or exclude from the calf log) all calls that fail or that are received by a message service. In certain embodiments, filtering settings may be dynamically changed for each of a user's devices. Information associated with outgoing calls from each device may be stored, subject to the filtering settings, in the call log. In certain implementations of the present invention, the type of information stored in the call log may vary for each calling device.
[090] Fig. 7 is a flowchart depicting exemplary stages in a call log process consistent with certain embodiments of the present invention. The illustrated call log process may enable a user 110 to establish, set, and/or select filter parameters and/or preferences (i.e., build exclusion list) for the call log (stage 701 ). In one embodiment of the present invention, user 110 may set specific filter parameters for each of a plurality of devices, as discussed above. Application function 516 and/or user terminal 112 may, in certain implementations, include software, firmware, and/or hardware, for implementing filters, and a Graphical User Interface (GUI) for facilitating user access and interaction. In certain embodiments of the present invention, user 110 may access, input, and modify filtering parameters and/or preferences via user terminal 112.
[091] As mentioned above, systems and methods consistent with the present invention may obtain information associated with outgoing calls.
Obtaining information associated with outgoing calls may, in the call log process of Fig. 7, involve configuring one or more calling devices associated with user 110 (stage 710). In one embodiment of the present invention, user 110 may use a landline telephone coupled to voice network 104 in order to place calls to other parties. Accordingly, configuring calling devices may include setting an AIN (Advanced Intelligent Network) Off-Hook Delay ("OHD") trigger on a communication line associated with the landline telephone. The OHD trigger may be encountered in the call flow when the telephone goes "off hook" and the caller enters a number. That is, the OHD trigger may wait for a telephone number to be entered by a user.
[092] In certain embodiments of the present invention, user 110 may use one or more programmable calling devices to place calls, such as a BREW phone, a J2ME phone, a PDA, and/or a laptop coupled to voice network 104. Such programmable calling devices may be compatible with PSTN and/or VoIP technology and, in certain implementations, be similar in structure to user terminal 112. Accordingly, configuring calling devices (stage 710) may include configuring the programmable calling device to capture and optionally cache outgoing call information, thereby enabling outgoing call information to be obtained. A programmable calling device may, in one embodiment, receive configuration data and/or instructions from server 406, which may cause the device to capture outgoing call information. Such data could, for example, be downloaded from the Internet or automatically transmitted from server 406 to the programmable calling device. A given programmable calling device may also be pre-configured to capture outgoing call information or configured by instructions input to a local storage drive (e.g., CD-ROM drive, floppy drive, etc.). As discussed above, information associated with outbound calls originating from a plurality of calling devices may be stored in the call log. Accordingly, OHD triggers may be set for one or more landline phones and, one or more programmable calling devices may be configured to capture outgoing call information, thereby enabling outgoing call information from each calling device to be obtained.
[093] Consistent with principles of the present invention, user 110 may initiate a call to a called party 605 (stage 720). 1n certain embodiments, user 110 may place a call via one or more landline telephones, wireless telephones, pagers, etc. Additionally or alternatively, user 110 could place a call via one or more digital cell phones, PDAs, J2ME phones, BREW phones, laptops, and/or other programmable calling devices. Telephony services may be provided by voice network 104.
[094] Once user 110 initiates a call, the process of Fig. 7 may obtain information associated with the outbound call (stage 730). In one example, such information may include the dialed number and a time of placing the calf.
For landline phones, the illustrated process may involve querying AlN SCP
(302) in voice network 104. For example, when the handset of a landline telephone goes "off-hook" and user 110 enters the called party number, the OHD trigger may cause a query to be transmitted to the AIN SCP (302).
Upon receiving the query, a Service Logic Program (SLP) in 1SCP 302 for the subscriber's line may be initiated. The SLP may include one or more hardware, software, and/or firmware components for processing call information and/or routing call information among and between various components and/or systems included in (or coupled to) service center 106.
The SLP in ISCP 302 may use GDI TCP/IP to transmit information associated with the outgoing call, including the outbound dialed number, to digital companion server 406 in service center 106 (stage 740).
[095] With programmable calling devices, obtaining information associated with outbound calls (stage 730) may involve capturing call information via the calling device. Accordingly, the calling device may transmit (stage 740) the captured outgoing call information to digital companion server 406 in service center 106. In certain embodiments of the present invention, the call information may be transmitted from the programmable calling device to service center 106, via network 102 and/or network 104 when the call is made. However, the outbound call information may, additionally or alternatively, be transmitted from the programmable calling device subsequent to the occurrence of the outbound call and/or in response to a request from server 406. Outgoing call information may be transmitted wirelessly to service center 106. In alternative embodiments, outgoing call data may be transmitted over a wired network link and may be transmitted via TCP/IP.
[096] Upon receiving the outgoing call information (stage 740), server 406 may route the information to application function 516 for processing. In certain implementations, application function 516 may determine (stage 750) whether or not the outbound call information should be included in the call log.
Application function 516 may use the filtering parameters (stage 701 ) to determine whether a particular call should be logged. In alternative embodiments, the determination of whether the call should be logged (stage 750) may be performed by ISCP 302 and may occur prior to transmitting the call information to application function 516. If it is determined that the call should be excluded from the call log (e.g., because the dialed number is included in the exclusion list), processing of the call may cease and application 516 may standby for additional outbound calls (stage 720). lf, however, it is determined that the outbound call should be logged (stage 750), application function 516 may log the outgoing call information (stage 760). !n one embodiment of the present invention, outgoing call information may be logged in call log 610, which may, as explained above, be stored via database function 522. As mentioned above, information logged in call log 610 may include the dialed number, information associated with the calling andlor called device, and a time stamp indicating when the call was placed.
[097] Once the outgoing call information is togged (stage 760), the illustrated process may provide the user with access to the call log (stage 770). Providing access may involve visually and/or audibly presenting information in the call log to user 110. In one embodiment of the present invention, the stored information may be displayed to and/or accessed by user 110 via user data network 120 and/or voice network 104. For example, user 110 may access the call log via user terminal 112 A and/or 112 B coupled to data network 120. Additionally or alternatively, user 110 may access the call log via voice network 104 through, for example, voice portal 414. In certain embodiments of the present invention, user 110 may access the call iog via one or more calling devices (e.g., a digital cell phone coupled to°data network 120 and/or voice network 104).
[098] The steps illustrated in the flowchart of Fig, 7 are consistent with exemplary implementations of the instant invention. Further, it should be understood that the sequence of events described in Fig. 7 are exemplary and not intended to be limiting. Thus, other method steps may be used, and even with the method depicted in Fig. 7, the particular order of events may vary without departing from the scope of the present invention. For example, filter parameters (e.g., the exclusion list) may be set (stage 701 ), accessed, and modified at any time. Also, calling devices may be configured (stage 710) prior to the user setting filters (stage 701 ). Moreover, certain steps may not be present and additional steps may be implemented in Fig. 7.
[099] Consistent with principles of the present invention, various operations and analyses may be pertormed using the call log. In certain embodiments, the call log may be used to add contacts to a contact list (e.g., the above-mentioned address book stared via contacts database 530).
Server 406 may, in certain implementations, permit a customer to add contacts to a contact list or address book. User 110 may access the contact list via user terminal 112 andlor voice network 104. The contact list may include names, business and/or home addresses, e-mail addresses, contact numbers, facsimile numbers, and/or other identifying information associated with contacts. In one embodiment, the dialed number may be inserted from the call log into the contact list. In addition, or as an alternative, contact-related information may be obtained and inserted in the contact list when a contact is added. Contact information associated with a particular called party may be obtained using information (e.g., the dialed number) listed in the call log.
[0100] Consistent with embodiments of the present invention contact-related information may be obtained via one or more networks and/or network-based services. In certain embodiments, methods and systems may leverage one or more elements included in or coupled fio service center 106 and/or voice network 1041 may to retrieve contact information. In one example, back end server 420 may include or be configured as a Reverse Directory Assistance (RDA) server. As such, back end server 420 may interface service center 106 with an RDA Gateway of voice network 104 and may be leveraged by one or more RDA processes to retrieve contact information associated with logged dialed numbers. In certain embodiments of the present invention, the RDA Gateway may accept messages and requests from back end server 420, issue requests/queries for contact information to the DOC of voice network 104, and provide responsive information, including the contact information, back to server 420.
[0701) In certain embodiments, application server function 528 in communication portal server 408 may retrieve contact information associated with logged dialed numbers from sources such as web based services 552.
[0102] Contacts may be added to the contact list automatically and/or on demand. That is, the dialed number and/or contact information associated with a called party may be automatically added to the contact list in response to an outbound call to the called party or may be added to the contact list in response to a command from user 110. For example, back end server 420 may, in conjunction with service center 106 (e.g., servers 406 and/or 408) and voice network 104, automatically retrieve and add contact information associated with a called party to the contact list when application function receives the outbound call information (stage 740). In certain embodiments of the present invention, contacts are added to the contact list once, regardless of the number of calls to that dialed number. Methods and systems consistent with the present invention may determine whether a particular dialed number represents a new contact or one that was previously logged or entered in the contact list by user 110. In one configuration, server 406 (e.g., via application function 516) and/or back end server 420 (e.g., configured as an RDA server) may perform this determination. If a given dialed number was previously logged or entered, the current outbound call may not be added. If, however, the dialed number in the call log represents a new contact, a new contact entry may be created and contact information associated with the number may be retrieved and added to the contact list, thereby adding the new contact to the contact list. In certain embodiments, user 110 could be notified via user terminal 112 of additions to the contact list.
[0103] Additionally, a user may cause or initiate the addition of a contact to the contact list. In certain embodiments, user 110 may be prompted to specify whether a called party should be placed in the contact list. For example, server 406 may prompt user 110 via user terminal 112 to specify whether or not a called party should be inserted in the contact list at the time of the outbound call to that party, Users could also add previously called parties to the contact list via the call log. In one example, a user may select a dialed number in the call log and, in response, contact information associated with the dialed number may be retrieved (e.g., via RDA processes) and added to the contact list. If the contact is not a new contact, a corresponding message may be displayed to the user, and the user may be prompted to specify whether the contact should be added. In exemplary embodiments of the present invention, the user may specify and alter the manner in which contacts are added to the contact list via, for example, user terminal 112, which may interface with elements in server 406, communication portal server 408, and/or back end server 420. For example, user 110 may set and change preferences via application function 516. In addition, user 110 may dynamically change the manner in which contacts are added to the contact list at any time. In one implementation of the invention, user 110 may set contact list preferences for the call log when filters are set (stage 701 ).
[0104] In certain embodiments of the present invention, data analyses may be performed using the call log. For example, the call log may enable a user to view calling patterns andlor frequencies. In one instance, a user could view all outgoing calls (or those to a particular party) occurring in a particular time period (e.g., one month). In certain embodiments, data analyses may be device-specific. That is, data analyses may be performed for each of the user's calling devices. In one example, the user could view calling patterns for and/or the calls originating from each of a plurality of calling devices.
Further, one or more different analyses could be performed for each calling device, depending on device type and/or user-specified parameters and instructions.
[0105] In exemplary implementations, server 406 may be configured to perform such analyses (e.g., via application function 516) using the call log.
Additionally or alternatively, user terminal 112 may include program code for performing the analyses. The results of the analyses may, in one example, be stored by database function 522 and/or storage 204. The user may access results of the analyses via user data network 120 and/or voice network 104. In one example, a user may access the call log (stage 770) and then initiate certain analyses and view results. Additionally or alternatively, the user may preset analyses to be performed and set parameters associated with such analyses in a manner similar to that described above in connection with stage 701 of Fig. 7. Users may then automatically receive (via data network 120 and/or voice network 104) analyses reports periodically and/or upon viewing the call log.
[0106] Embodiments consistent with the invention may be implemented in various environments. Further, the processes described herein are not inherently related to any particular apparatus and may be implemented by any suitable combination of components. Moreover, various types of general purpose devices may be used in accordance with the teachings described herein.
[0107] The exemplary systems and methods consistent with present invention described above are illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0108] The present invention has been described in relation to particular examples which are intended in all respects to be illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0109] Additionally, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only. To this end, it is to be understood that inventive aspects lie in less than all features of a single foregoing disclosed embodiment, implementation, or configuration. Thus, the true scope and spirit of the invention depends on the following claims.
DETAILED DESCRIPTION
[021] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the figures to refer to the same or like elements. The accompanying figures illustrate exemplary embodiments and implementations consistent with the present invention, but the description of those embodiments does not indicate or imply that other embodiments or implementations do not fall within the scope of present invention. It is to be understood that other implementations may be utilized and that structural and method changes may be made without departing from the scope of present invention.
[022] Fig. 1 is a block diagram of a data processing and telecommunications environment 100, in which features and aspects consistent with the present invention may be implemented. The number of components in environment 100 is not limited to what is shown and other variations in the number of arrangements of components are possible, consistent with embodiments of the invention. The components of Fig. 1 may be implemented through hardware, software, and/or firmware. Data processing and telecommunications environment 100 may include a data network 102, a voice network 104, and a service center 106. A user 110 may use a user terminal 112 to interface with data network 102 and may use phones 114, 116, arid 118 to interface with voice network 104. Calling party 120 may use phone 122 to call a user, such as user 110, at any one of phones 114, 116, and 118.
[023] Data network 102 provides communications between the various entities depicted in environment 100 of Fig. 1, such as user terminal 112 and service center 106. Data network 102 may be a shared, public, or private network and encompass a wide area or local area. Data network 102 may be implemented through any suitable combination of wired and/or wireless communication networks. By way of example, data network 102 may be implemented through a wide area network (WAN), local area network (LAN), an intranet andlor the Internet. Further, the service center 106 may be connected to multiple data networks 102, such as, for example, to a wireless carrier network and to the Internet.
[024] Voice network 104 may provide telephony services to allow a calling party, such as calling party 120, to place a telephone call to user 110.
In one embodiment, voice network 104 may be implemented using a network, such as the Public Switched Telephone Network ("PSTN"). Alternatively, voice network 104 may be implemented using voice-over Internet Protocol ("VoIP") technology. In addition, voice network 104 may be implemented using both PSTN and VoIP technology consistent with the principles of the present invention. Further, service center 106 may be connected to multiple voice networks 104, such as for example, Verizon'sT"" Voice Network, voice networks operated by other carriers, and wireless carrier networks.
[025] Service center 106 provides a platform for managing communications over data network 102 and voice network 104. Service center 106 also provides gateway functions, such as code and protocol 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.
[026] User terminal 112 provides user 110 an interface to data network 102. For example, user terminal 112 may be implemented using any device capable of accessing the Internet, such as a general purpose computer or personal computer equipped with a modem. User terminal 112 may also be implemented in other devices, such as the BlackberryT"", and Ergo AudreyT"". Furthermore, user terminal 112 may be implemented in wireless devices, such as pagers, mobile phones (with data access functions), and Personal Digital Assistants ("PDA") with network connections.
[027] User terminal 112 also allows user 110 to communicate with service center 106. For example, user 110 may use instant messaging ("IM") to communicate with service center 106. In addition, user terminal 112 may use other aspects of TCPIIP including the hypertext transfer protocol ("HTTP"); the user datagram protocol ("UDP"); the file transfer protocol ("FTP"); the hypertext markup language ("HTML"); and the extensible markup language ("XML").
[028] Furthermore, user terminal 112 may communicate directly with service center 106. For example, a client application may be installed on user terminal 112, which directly communicates with service center 106. Also, user terminal 112 may communicate with service center 106 via a proxy.
[029] Phones 114, 116, 118, and 122 interface with voice network 104. Phones 114, 116, 118, and 122 may be implemented using known devices, including wireline phones and mobile phones. In certain embodiments of the present invention, phones 114, 116, 118, and 122 may include programmable calling devices such as BREW phones, J2ME phones, PDAs, and laptops and may be compatible with PSTN and/or VoIP
techne~logy. Although phones 114, 116, 118, and 122 are shown directly connected to voice network 104, any number of intervening elements, such as a private branch exchange ("PBX"), may be interposed between phones 114, 116, 118, and 122 and voice network 104.
[030] Fig. 2 is a block diagram of user terminal 112 consistent with the present invention. User terminal 112 includes a central processing unit (CPU) 200, a memory 202, a storage module 204, a network interface 206, an input interface 208, an output interface 210, an input device 216, and an output device 218.
[031] CPU 200 provides control and processing functions for user terminal 112. Although Fig. 2 illustrates a single CPU, user terminal 112 may include multiple CPUs. CPU 200 may also include, for example, one or more of the following: a co-processor, memory, registers, and other processing devices and systems as appropriate. CPU 200 may be implemented, for example, using a PentiumT"" processor provided from Intel Corporation.
[032] Memory 202 provides a primary memory for CPU 200, such as for program code. Memory 202 may be embodied with a variety of components of subsystems, including a random access memory ("RAM") and a read-only memory ("ROM"). When user terminal 112 executes an application installed in storage module 204, CPU 200 may download at least a portion of the program code from storage module 204 into memory 202. As CPU 200 executes the program code, CPU 200 may also retrieve additional portions of program code from storage module 204.
[033] Storage module 204 may provide mass storage for user terminal 112. Storage module 204 may be implemented with a variety of components or subsystems including, for example, a hard drive, an optical drive, CD ROM
drive, DVD drive, a general-purpose storage device, a removable storage device, and/or other devices capable of storing information. Further, although storage module 204 is shown within user terminal 112, storage module 204 may be implemented external to user terminal 112.
[034] Storage module 204 includes program code and information for user terminal 112 to communicate with service center 106. Storage module 204 may include, for example, program code for a calendar application, such as GroupWise provided by Novell Corporation or Outlook provided by Microsoft Corporation; a client application, such as a Microsoft Network Messenger Service (MSNMS) client or America Online Instant Messenger (AIM) client; and an Operating System (OS), such as the Windows Operation System provided by Microsoft Corporation. In addition, storage module 204 may include other program code and information, such as program code for TCP/IP communications; kernel and device drivers; configuration information, such as a Dynamic Host Configuration Protocol (DHCP) configuration; a web browser, such as Internet Explorer provided by Microsoft Corporation, or Netscape Communicator provided by Netscape Corporation; and any other software that may be installed on user terminal 112.
[035] Network interface 206 provides a communications interface between user terminal 112 and data network 102. Network interface 206 may receive and transmit communications for user terminal 112. For example, network interface 206 may be a modem, or a local area network ("LAN") port.
[036] Input interface 208 receives input from user 110 via input device 212 and provides the input to CPU 200. Input device 212 may include, for example, a keyboard, a microphone, and a mouse. Other types of input devices may also be implemented consistent with the principles of the present invention.
[037] Output interface 210 provides information to user 110 via output device 214. Output device 214 may include, for example, a display, a printer, and a speaker. Other types of output devices may also be implemented consistent with the principles of the present invention.
[038] Fig. 3 is a diagram of a voice network, consistent with the principles of the present invention. As shown, voice network 104 includes an intelligent service control point (ISCP) 302, service transfer points (STP) and 306, service switching points (SSP) 308 and 310, a line information database (LIDB) 312, an ISCP Service Provisioning And Creation Environment (SPACE) 314, a Recent Change Environment 316, and an Intelligent Peripheral (IP) 320.
[039] Voice network 104 may be implemented using the PSTN and SS7 as a signaling protocol. The SS7 protocol allows voice network 104 to provide features, such as call forwarding, caller-ID, three-way calling, wireless services such as roaming and mobile subscriber authentication, local number portability, and toll-free/toll services. The SS7 protocol provides various types of messages to support the features of voice network 104. For example, these SS7 messages may include Transaction Capabilities Applications Part ("TCAP") messages to support event "triggers," and queries and responses between ISCP 302 and SSPs 308 and 310.
[040] ISCP 302 may also be, for example, a standard service control point (SCP) or an Advanced Intelligent Network (AIN) SCP. ISCP 302 provides translation and routing services of SS7 messages to support the features of voice network 104, such as call forwarding. In addition, ISCP 302 may exchange information with the service center 106 using TCP/IP or SS7.
ISCP 302 may be implemented using a combination of known hardware and software. Although ISCP 302 is shown with a direct connection to service center 106 through ISCP SPACE 314, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP 302 and service center 106.
[041] STPs 304 and 306 relay SS7 messages within voice network 104. For example, STP 304 may route SS7 messages between SSPs 308 and 310. STP 302 may be implemented using known hardware and software from manufacturers such as NORTELT"' and LUCENT TechnologiesT""
[042] SSPs 308 and 310 provide an interface between voice network 104 and phones 114 and 120, respectively, to setup, manage, and release telephone calls within voice network 104. SSPs 308 and 310 may be implemented as a voice switch, an SS7 switch, or a computer connected to a switch. SSPs 308 and 310 exchange SS7 signal units to support a telephone call between calling party 120 and user 110. For example, SSPs 308 and 310 may exchange SS7 messages, such as TCAP messages, within message signal units ("MSU") to control calls, perform database queries to configuration database 312, and provide maintenance information.
[043] Line Information Database (LIDB) 312 comprises one or more known databases to support the features of voice network 104. For example, LIDB 312 may include subscriber information, such as a service profile, name and address, and credit card validation information.
[044] ISCP Service Provisioning and Creation Environment (SPACE) 314 may be included as part of ISCP 302 or be separate from ISCP 302. For example, the TelcordiaT"" ISCP may include an environment similar to SPACE
314 as part of the product. Further, ISCP SPACE 314 may include one or more servers. ISCP SPACE 314 is the point in the ISCP platform where customer record updates may be made.
[045] In one embodiment, customer records may be stored in ISCP
SPACE 314 such that the records may be updated and sent to ISCP 302.
These records may include information regarding how to handle calls directed to the customer. For example, these customer records may include information regarding whether or not calls for the customer are to be forwarded to a different number, 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).
[046] Additionally, voice network 104 may include one or more recent change engines 316 such as, for example, an Enterprise Recent Change engine (eRC); an Assignment, Activation, and Inventory System (AAIS); or a multi-services platform (MSP). As an example, the eRC and AAIS may be used in voice networks 104 located in the western part of the United States, while an MSP may be used in networks in the eastern part. The recent change engines may be used to update switch and ISCP databases. For example, a recent change engine may deliver database updates to SSPs and to ISCPs, such that when updating databases, these recent change engines emulate human operators. Additionally, if the instructions are to be sent to an ISCP 302, the recent change engine may first send the instructions to ISCP
SPACE 314, which then propagates the instructions to ISCP 302 as discussed above. Further, an MSP may be used, for example, for providing updates to both SSPs 308 or 310 and ISCPs 302. Or, for example, an eRC
may be used for providing updates to SSPs 308 or 310, while an AAIS is used for providing updates to ISCPs 302.
[047] Additionally, voice network 104 may include one or more intelligent peripherals (IP). For example, in Fig. 4, an IP 320 is illustrated as being connected to SSP 308. These IPs may be used for providing services, such as voice mail services.
[048] Fig. 4 is a block diagram of a service center, consistent with the principles of the present invention. As shown, service center 106 may include firewalls 402 and 404, one or more digital companion servers 406, one or more communication portal servers 408, one or more network access servers 410, and a voice portal 412. Voice portal 412 may include a voice portal application server 414 and a voice recognition server 416. A network 418 may be used to interconnect the firewalls and servers. Additionally, back end servers) 420 may be provided between service center 106 and voice network 104.
[049] Firewalls 402 and 404 provide security services for communications between service center 106, data network 102, and voice network 104, respectively. For example, firewalls 402 and 404 may restrict communications between user terminal 112 and one or more servers within service center 106. Any security policy may be implemented in firewalls 402 and 404 consistent with the principles of the present invention. Firewalls 402 and 404 may be implemented using a combination of known hardware and software, such as the Raptor Firewall provided by the Axent Corporation.
Further, firewalls 402 and 404 may be implemented as separate machines within service center 106, or implemented on one or more machines external to service center 106.
[050] Network 418 may be any type of network, such as an Ethernet or FDDI network. Additionally, network 418 may also include switches and routers as appropriate without departing from the scope of the invention.
Further, additional firewalls may be present in network 418, for example, to place one or more of servers 406, 408, 410, or voice portal 412 behind additional firewalls.
[051 ] Each server (406, 408, 410, 414, 416, 420) may be any type of server or computer, such as a Unix or DOS based server or computer. The servers may implement various logical functions, such as those described below. In Fig. 4, a different server is illustrated as being used for each logical function. In other embodiments, the logical functions may be split across multiple servers, multiple servers may be used to implement a single function, all functions may be performed by a single server, etc.
[052] In general, a digital companion server 406 may provide the software and hardware for providing specific services of the service center.
Exemplary services include, for example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name andlor address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, digital companion server 406 may log and perform operations on outgoing calf information associated with a particular subscriber (i.e., user 110). Outgoing call information may be logged/recorded from any of user 110's devices (e.g., 114, 116, 118).
[053] A communication portal server 408 may provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. Network access servers 410 may provide the hardware and software for sending and receiving information to voice network 104 in processing the applications provided by the service center. For example, network access servers 410 may be used for transmitting and/or receiving information from/to an ISCP 302 or an SSP 308 or 310 of voice network 104.
[054] Voice portal 412 includes software and hardware for receiving and processing instructions from a customer via voice. For example, a customer may dial a specific number for voice portal 412. Then the customer using speech may instruct service center 106 to modify the services to which the customer subscribes. Voice portal 412 may include, for example, a voice recognition function 416 and an application function 414. Voice recognition function 416 may receive and interpret dictation, or recognize spoken commands. Application function 414 may take, for example, the output from voice recognition function 416, convert it to a format suitable for service center 106 and forward the information to one or more servers (406, 408, 410) in service center 106.
[055] Fig. 5 illustrates a logical architecture of an exemplary system, consistent with the present invention. As illustrated, the logical architecture may be split into four planes: client side plane 502, application service plane 504, network access plane 506, and voice network plane 508.
[056] Client side plane 502 includes the user terminals 112 A and 112_B that a user may use to send and/or receive information to/from the service center 106. Additionally, client side 502 includes the user's phones) 114. As discussed above, user terminals 112 may be any type of device a user may use for communicating with Service Center 106. For example, user terminal 112 A may be a PDA running a program for communicating with Service Center 106, while user terminal 112_B may be a desktop type computer running a web browser for communicating with Service Center 106 via the Internet. Additionally, the user may have one or more phones 114, such as, for example, one or more standard landline telephones and/or wireless phones.
[057] Application service plane 504 includes digital companion servers) 406, communication portal servers) 408, and voice portal 412.
These entities may communicate between one another using, for example, web services or any other suitable protocols. Web services are a standardised way of integrating Web-based applications using the Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) open standards over an Internet protocol (IP) backbone.
[058] As illustrated, a digital companion server 406 may provide .the following functions: a client proxy 512, a web server 514, an application server function 516, a calendar server function 5_18, a notification server function 520, and a database function 522. Each of these functions may be performed in hardware, software, andlor firmware. Further, these functions may each be executed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[059] Client proxy function 512 provides a proxy function for the digital companion that may be used for security purposes. This client proxy function 512 may be included in a separate server such that all communications sent from the other digital companion functions/servers to a user terminal 112 via data network 102 go through client proxy 512. Also, if client proxy 512 is included on a separate server, for example, an additional firewall may be provided between the client proxy 512 and the other digital companion servers to provide additional security.
[060] Web server 514 provides functionality for receiving traffic over data network 102 from a customer. For example, web server 514 may be a standard web server that a customer may access using a web browser program, such as Internet Explorer or Netscape Communicator.
[061] Application server function 516 encompasses the general functions performed by digital companion servers) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific applications provided by the service center.
These services may include, for example, interfacing with other function(s), software, andlor hardware to provide a customer with the capability of managing their calls online. For example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, permitting a customer to make calls directly from their address book, scheduling a call to be placed at a specific time, or permitting the customer to look at the name and/or address associated with a phone number. Additionally, these services may include permitting the customer to listen to their voice mail on-line, forwarding their calls based on a scheduler and/or the calling parties number, setting up conference calls on-line, etc.
Consistent with principles of the present invention, application server function 516 may facilitate logging and processing outgoing call information associated with a particular subscriber. Application server function 516 may log/record outgoing call information from any of a particular user 110's devices (e.g., 114, 116, 118). Application server function 516 may store the outgoing calf information, display the information to a subscriber (110), and perform various operations on the information.
[062] Additionally, application server function 516 may interface with one or more external devices, such as an external web server, for retrieving or sending information. For example, application server function 516 may interface with a voice network's data center 556 (e.g., verizon.com) to determine the services to which the customer subscribes (e.g., call waiting, call forwarding, voice mail, etc.).
[063] Calendar server function 518 may provide the capability of scheduling events, logging when certain events occurred, triggering the application-functions to perform a function at a particular time, etc.
[064] Notification server function 520 provides the capability to send information from service center 106 to a user terminal 112. For example, notification server function 520 at the direction of application server function 516 may send a notification to user terminal 112 that the user is presently receiving a phone call at user's phone 114.
[065] Database function 522 provides the storage of information useable by the various applications executed by the digital companion servers. These databases may be included in, for example, one or more external storage devices connected to the digital companion servers.
Alternatively, the databases may be included in storage devices within the digital companion servers themselves. The storage devices providing database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
[066] As discussed above, communication portal servers) 408 provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of customer's voice network 104. As illustrated in Fig. 5, a communication portal server 408 may provide the following functions: a web server function 526, an application server function 528, a contacts database function 530, and/or a customer profile function 532. Each of these functions may be performed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
[067] Web server function 526, as with web server function 522 of the digital companion servers, provides functionality for receiving traffic over data network 102 from a customer. For example, the web server may be a standard web server that a customer may access using a web browser, such as Internet Explorer or Netscape Communicator.
[068] Application server function 528 encompasses the general functions performed by communication portal servers 406. For example, these functions may include interfacing with the voice network to retrieve and/or modify customer profile information, and creating and editing an address book for the user. Additionally, application server function 528 may include the functionality of sending andlor receiving information to/from external servers and/or devices. For example, communication portal servers 408 may be connected to a network, such as, the Internet. Application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages webpage.
Application function 528 could then contact these external services 552 to retrieve information, such as an address for a person in the user's address book.
[069] In another example, application server function 528 of communication portal 408 may interface a single sign on (SSO) server 554.
SSO 554 may be used to allow users to access all services to which the user subscribes, on the basis of a single authentication that is performed when they initially access the network.
[070] Contacts database 530 includes storage devices for storing an address book for the user. This address book may be any type of address book. For example, the user's address book may include the names, phone numbers, and addresses of people and/or organizations. These storage devices may be internal or external to communication portal servers 406 or same combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
[071] Customer profile database 532 includes storage devices for storing customer profile information for the user. These storage devices may be the same or separate storage devices used for the contacts database.
The customer profile may include information regarding the user's account for their voice network. For example, this information may include the user's name, billing address, and other account information. Additionally, the customer profile may include information regarding voice services to which the user subscribes, such as, for example, call waiting, voice mail, etc.
[072] Additionally, application services plane 504 of the architecture may include a voice portal 412. As discussed above, voice portal 412 may include, for example, a voice recognition function 416 and an application server function 414, and be used for receiving and processing instructions from a customer via voice. The voice recognition function may be implemented using hardware and/or software capable of providing voice recognition capabilities. This hardware and/or software may be a commercially available product, such as the Voice Application platform available from Tellme Networks, Incorporated. Application server function 414 of voice portal 412 may include hardware and/or software for exchanging information between digital companion servers 406 and voice recognition function 416. Additionally, application server function 414 may be included on a separate server, included in the hardware and software providing voice recognition function 416, included in digital companion servers 406, etc.
[073] Network Access plane 506 of the architecture includes the functions for providing connectivity between application service plane 502 and voice network 104. For example, this plane may include the recent change engines 316, network access servers 410, and/or back end servers 420.
[074] As discussed above, recent change engines 316 may be used to update switches and ISCP databases included in voice network 104. In one embodiment, recent change engines 316 may include an AAIS 544, an eRC 546, and/or an MSP 548. Additionally, a proxy 542 may be used between digital companion servers 406 and recent change engines 542 for security purposes.
[075] Network access servers 410 may be included in the service center 106 and may provide the hardware and software for sending and receiving information to voice network 410 in processing the applications provided by the service center. For example, network access servers 410 may include a Caller iD (CID) functionality for retrieving caller ID
information from voice network 104, a click to dial (CTD) functionality for instructing an intelligent peripheral (IP) in the voice network to place a call via an SSP, and/or a real time call management (RTCM) functionality for interfacing with an ISCP of the voice network.
[076] Network Access plane 506 may also include one or more back end servers) 420. These back end servers) 420 may include hardware and/or software for interfacing service center 106 and voice network 104.
Back end servers) 420 may be connected to service center 106 by a network, by a direct connection, or in any other suitable manner. Further, back end servers) 420 may connect to one or more devices in voice network 104 by a network, a direct connection, or in any other suitable manner.
[077] Back end servers) 420 may include, for example, a server providing a voice mail retrieval and notification function. For example, this voice mail retrieval and notification function may include the capability to receive notifications when a user receives a voice mail, physically call a user's voice mail system, enter the appropriate codes to retrieve the voice mail, retrieve the voice mail, convert the voice mail to a digital file, and send it to digital companion servers 406.
[078] Additionally, back end servers) 420 may also include, for example, a directory assistance server. This directory assistance server may, for example, interface service center 106 with a Reverse Directory Assistance Gateway (RDA Gateway) of voice network 104. A RDA Gateway is a device for issuing requests to a Data Operations Center (DOC) of voice network 104 for name and/or address information associated with a phone number and receiving the name and/or phone number in response to this request.
[079] In another example, back end servers) 420 may include a wireless Internet gateway that is used for interfacing with a mobile switching center (MSC) of a wireless voice network. As with the above-described back end servers) 420, this wireless Internet gateway may be used for converting requests and information between the formats used by service center 106 and those used by the wireless voice network.
[080] In yet another example, back end servers) 420 may include a conference blasting server for instructing a conference bridge in the voice network 106 to dial out via an SSP to the participants of a voice conference.
Or for example, the back end servers) may include a server for instructing an IP of the voice network to place a call between two parties by dialing out to each of the parties. Back end servers) 420 may also include the capability to instruct the bridge or IP device to call an audio digitizing device that can listen to the conference, convert the audio signals to digital format, and forward the digitized signals to a user device via, for example, an audio streaming server.
The audio streaming server may, for example, allow a user to connect to it via, for example, the Internet. Additionally, the audio streaming device may buffer or record the signals to permit the user to pause, rewind, and/or fast-forward thru the conference.
[081] In yet another example, back end servers) 420 may include a Single Number Short Message Service (SN SMS) server for interfacing the service center 106 with a SMS gateway in voice network 104. This may be used for example to permit the customer to have SMS messages addressed to their home phone number directed to an SMS capable device of the user's choosing.
[082] Voice network plane 508 includes the hardware and software included in voice network 104, as discussed above with reference to Fig. 3.
For example, voice network plane 508 may include ISCP SPACE 314, ISCP
302, intelligent peripherals 320, and SSP 308. Additionally, voice network plane 508 may also include the hardware and software included in a wireless carrier's network, such as, for example, the mobile switching center, etc.
[083] For clarity of explanation, system 100 is described herein with reference to the discrete functional elements illustrated in Figs. 1-5.
However, it should be understood that the functionality of these elements and modules may overlap and/or may exist in a fewer or greater number of elements and modules. Elements of system 100 may, depending on the implementation, lack certain illustrated components and/or contain, or be coupled to, additional or varying components not shown. Moreover, all or part of the functionality of the elements illustrated in Figs. 1-5 may co-exist or be distributed among several geographically dispersed locations.
[084] As described above, outgoing call information from any of a user's (e.g., 110) devices may be stored in a call log. As used herein, the term "log" refers to a compilation or listing of data. Forms of the term "log"
also refer to the act of compiling, storing, and/or recording information. A
"call log" refers herein to a log of information associated with outbound calls originating from one or more devices associated with a particular user. A
"call" may include a telephone call placed from one or more communication devices (e.g., landline phone, cell phone, etc.). The term "call" may also encompass other types of communications, such as e-mails, instant messages, facsimiles, etc.
[085] Fig. 6 diagrammatically illustrates an overview of call log processes and features consistent with certain embodiments of the present invention. As depicted in Fig. 6, user 110, as a calling party, may place a call using a calling device (e.g., telephone 118) to a called party 605. Methods and systems consistent with the present invention may obtain information associated with the outgoing call and store the information in a call log 610.
1n certain embodiments of the present invention, the call log may be implemented via one or more data files andlor structures residing on (or distributed among) one or more storage devices. For example, as illustrated in Fig. 6, call log 610 may be stored via database function 522. Additionally or alternatively, all or part of call log 610 may reside in storage 204 on user terminal 112. In one embodiment, call log 610 may include, for each outbound call, one or more of the following data elements: the dialed number, information associated with the calling device and/or party, information associated with the called device and/or party, and a time stamp.
[086] In certain embodiments of the present invention, call log 601 may include or reference contact-related information associated with called parties. Consistent with principles of the present invention, such contact-related information may include one or more of a name, home address, business address, home telephone number, business telephone number, cell phone number, instant messenger address, IP address, biometric information (e.g., fingerprints, voice prints, retinal scans, etc.) visual information (e.g., digital images, photographs, etc.), audio information, personal information (e.g., birth date, favorite movies, favorite songs, etc.), public records, credit reports, police records, driving records, banking statements, and contact-related information associated with relatives and/or friends. In certain embodiments, contact-related information may include information associated with, or retrieved via, one or more networks.
[087] User 110 may access call log 610 via, for example, user terminal 112 or telephone 118. In certain embodiments, information in the calf fog may be organized hierarchically, enabling users to explore detailed information (e.g., details of a specific call), as well as broader views (e.g., overall tailing patterns, etc). Additional features associated with the call log are discussed below.
[088] In exemplary embodiments, systems and methods consistent with the present invention may provide to the user filtering and/or processing options for the call log. For example, user 110 may set up an exclusion list in order to preclude entry of certain calls from the call log. The exclusion list may be based on, for example, any one or combination of the following:
outgoing number types (e.g., 800 numbers, 411, etc.), called device types and called party location. Also, the exclusion list may, in one configuration, enable user 110 to exclude calls to certain parties during certain time periods. In one embodiment, user 110 may establish, access, and modify the exclusion list via user terminal 112 and digital companion server 406. Additional details of call log filtering and processing are discussed below.
[089] In certain embodiments of the present invention, outgoing call information originating from a plurality of calling devices associated with a user may be logged and managed. For example, calls originating from a cell phone, landline phone (e.g., 118), and PDA associated with user 110 may be logged. User 110 may set specific filtering settings for logging calls placed from each calling device. In one embodiment, such filtering setting may be specified through the exclusion list. The exclusion list could therefore specify certain types of outgoing calls from each of a user's calling devices that should be excluded from the call log. For example, user 110 could exclude 800 calls from a landline phone and 411 calls from a cell phone. User 110 could also specify, for example, that all calls made from a particular device should be excluded from or included in the call log. User 110 could also specify that calls made to certain parties should be excluded from or included in the call log. Certain filtering settings may allow users to specify that calls made during a certain time period or time of day should be included or excluded in the call log. In addition, certain filtering settings may allow users to log (or exclude from the calf log) all calls that fail or that are received by a message service. In certain embodiments, filtering settings may be dynamically changed for each of a user's devices. Information associated with outgoing calls from each device may be stored, subject to the filtering settings, in the call log. In certain implementations of the present invention, the type of information stored in the call log may vary for each calling device.
[090] Fig. 7 is a flowchart depicting exemplary stages in a call log process consistent with certain embodiments of the present invention. The illustrated call log process may enable a user 110 to establish, set, and/or select filter parameters and/or preferences (i.e., build exclusion list) for the call log (stage 701 ). In one embodiment of the present invention, user 110 may set specific filter parameters for each of a plurality of devices, as discussed above. Application function 516 and/or user terminal 112 may, in certain implementations, include software, firmware, and/or hardware, for implementing filters, and a Graphical User Interface (GUI) for facilitating user access and interaction. In certain embodiments of the present invention, user 110 may access, input, and modify filtering parameters and/or preferences via user terminal 112.
[091] As mentioned above, systems and methods consistent with the present invention may obtain information associated with outgoing calls.
Obtaining information associated with outgoing calls may, in the call log process of Fig. 7, involve configuring one or more calling devices associated with user 110 (stage 710). In one embodiment of the present invention, user 110 may use a landline telephone coupled to voice network 104 in order to place calls to other parties. Accordingly, configuring calling devices may include setting an AIN (Advanced Intelligent Network) Off-Hook Delay ("OHD") trigger on a communication line associated with the landline telephone. The OHD trigger may be encountered in the call flow when the telephone goes "off hook" and the caller enters a number. That is, the OHD trigger may wait for a telephone number to be entered by a user.
[092] In certain embodiments of the present invention, user 110 may use one or more programmable calling devices to place calls, such as a BREW phone, a J2ME phone, a PDA, and/or a laptop coupled to voice network 104. Such programmable calling devices may be compatible with PSTN and/or VoIP technology and, in certain implementations, be similar in structure to user terminal 112. Accordingly, configuring calling devices (stage 710) may include configuring the programmable calling device to capture and optionally cache outgoing call information, thereby enabling outgoing call information to be obtained. A programmable calling device may, in one embodiment, receive configuration data and/or instructions from server 406, which may cause the device to capture outgoing call information. Such data could, for example, be downloaded from the Internet or automatically transmitted from server 406 to the programmable calling device. A given programmable calling device may also be pre-configured to capture outgoing call information or configured by instructions input to a local storage drive (e.g., CD-ROM drive, floppy drive, etc.). As discussed above, information associated with outbound calls originating from a plurality of calling devices may be stored in the call log. Accordingly, OHD triggers may be set for one or more landline phones and, one or more programmable calling devices may be configured to capture outgoing call information, thereby enabling outgoing call information from each calling device to be obtained.
[093] Consistent with principles of the present invention, user 110 may initiate a call to a called party 605 (stage 720). 1n certain embodiments, user 110 may place a call via one or more landline telephones, wireless telephones, pagers, etc. Additionally or alternatively, user 110 could place a call via one or more digital cell phones, PDAs, J2ME phones, BREW phones, laptops, and/or other programmable calling devices. Telephony services may be provided by voice network 104.
[094] Once user 110 initiates a call, the process of Fig. 7 may obtain information associated with the outbound call (stage 730). In one example, such information may include the dialed number and a time of placing the calf.
For landline phones, the illustrated process may involve querying AlN SCP
(302) in voice network 104. For example, when the handset of a landline telephone goes "off-hook" and user 110 enters the called party number, the OHD trigger may cause a query to be transmitted to the AIN SCP (302).
Upon receiving the query, a Service Logic Program (SLP) in 1SCP 302 for the subscriber's line may be initiated. The SLP may include one or more hardware, software, and/or firmware components for processing call information and/or routing call information among and between various components and/or systems included in (or coupled to) service center 106.
The SLP in ISCP 302 may use GDI TCP/IP to transmit information associated with the outgoing call, including the outbound dialed number, to digital companion server 406 in service center 106 (stage 740).
[095] With programmable calling devices, obtaining information associated with outbound calls (stage 730) may involve capturing call information via the calling device. Accordingly, the calling device may transmit (stage 740) the captured outgoing call information to digital companion server 406 in service center 106. In certain embodiments of the present invention, the call information may be transmitted from the programmable calling device to service center 106, via network 102 and/or network 104 when the call is made. However, the outbound call information may, additionally or alternatively, be transmitted from the programmable calling device subsequent to the occurrence of the outbound call and/or in response to a request from server 406. Outgoing call information may be transmitted wirelessly to service center 106. In alternative embodiments, outgoing call data may be transmitted over a wired network link and may be transmitted via TCP/IP.
[096] Upon receiving the outgoing call information (stage 740), server 406 may route the information to application function 516 for processing. In certain implementations, application function 516 may determine (stage 750) whether or not the outbound call information should be included in the call log.
Application function 516 may use the filtering parameters (stage 701 ) to determine whether a particular call should be logged. In alternative embodiments, the determination of whether the call should be logged (stage 750) may be performed by ISCP 302 and may occur prior to transmitting the call information to application function 516. If it is determined that the call should be excluded from the call log (e.g., because the dialed number is included in the exclusion list), processing of the call may cease and application 516 may standby for additional outbound calls (stage 720). lf, however, it is determined that the outbound call should be logged (stage 750), application function 516 may log the outgoing call information (stage 760). !n one embodiment of the present invention, outgoing call information may be logged in call log 610, which may, as explained above, be stored via database function 522. As mentioned above, information logged in call log 610 may include the dialed number, information associated with the calling andlor called device, and a time stamp indicating when the call was placed.
[097] Once the outgoing call information is togged (stage 760), the illustrated process may provide the user with access to the call log (stage 770). Providing access may involve visually and/or audibly presenting information in the call log to user 110. In one embodiment of the present invention, the stored information may be displayed to and/or accessed by user 110 via user data network 120 and/or voice network 104. For example, user 110 may access the call log via user terminal 112 A and/or 112 B coupled to data network 120. Additionally or alternatively, user 110 may access the call log via voice network 104 through, for example, voice portal 414. In certain embodiments of the present invention, user 110 may access the call iog via one or more calling devices (e.g., a digital cell phone coupled to°data network 120 and/or voice network 104).
[098] The steps illustrated in the flowchart of Fig, 7 are consistent with exemplary implementations of the instant invention. Further, it should be understood that the sequence of events described in Fig. 7 are exemplary and not intended to be limiting. Thus, other method steps may be used, and even with the method depicted in Fig. 7, the particular order of events may vary without departing from the scope of the present invention. For example, filter parameters (e.g., the exclusion list) may be set (stage 701 ), accessed, and modified at any time. Also, calling devices may be configured (stage 710) prior to the user setting filters (stage 701 ). Moreover, certain steps may not be present and additional steps may be implemented in Fig. 7.
[099] Consistent with principles of the present invention, various operations and analyses may be pertormed using the call log. In certain embodiments, the call log may be used to add contacts to a contact list (e.g., the above-mentioned address book stared via contacts database 530).
Server 406 may, in certain implementations, permit a customer to add contacts to a contact list or address book. User 110 may access the contact list via user terminal 112 andlor voice network 104. The contact list may include names, business and/or home addresses, e-mail addresses, contact numbers, facsimile numbers, and/or other identifying information associated with contacts. In one embodiment, the dialed number may be inserted from the call log into the contact list. In addition, or as an alternative, contact-related information may be obtained and inserted in the contact list when a contact is added. Contact information associated with a particular called party may be obtained using information (e.g., the dialed number) listed in the call log.
[0100] Consistent with embodiments of the present invention contact-related information may be obtained via one or more networks and/or network-based services. In certain embodiments, methods and systems may leverage one or more elements included in or coupled fio service center 106 and/or voice network 1041 may to retrieve contact information. In one example, back end server 420 may include or be configured as a Reverse Directory Assistance (RDA) server. As such, back end server 420 may interface service center 106 with an RDA Gateway of voice network 104 and may be leveraged by one or more RDA processes to retrieve contact information associated with logged dialed numbers. In certain embodiments of the present invention, the RDA Gateway may accept messages and requests from back end server 420, issue requests/queries for contact information to the DOC of voice network 104, and provide responsive information, including the contact information, back to server 420.
[0701) In certain embodiments, application server function 528 in communication portal server 408 may retrieve contact information associated with logged dialed numbers from sources such as web based services 552.
[0102] Contacts may be added to the contact list automatically and/or on demand. That is, the dialed number and/or contact information associated with a called party may be automatically added to the contact list in response to an outbound call to the called party or may be added to the contact list in response to a command from user 110. For example, back end server 420 may, in conjunction with service center 106 (e.g., servers 406 and/or 408) and voice network 104, automatically retrieve and add contact information associated with a called party to the contact list when application function receives the outbound call information (stage 740). In certain embodiments of the present invention, contacts are added to the contact list once, regardless of the number of calls to that dialed number. Methods and systems consistent with the present invention may determine whether a particular dialed number represents a new contact or one that was previously logged or entered in the contact list by user 110. In one configuration, server 406 (e.g., via application function 516) and/or back end server 420 (e.g., configured as an RDA server) may perform this determination. If a given dialed number was previously logged or entered, the current outbound call may not be added. If, however, the dialed number in the call log represents a new contact, a new contact entry may be created and contact information associated with the number may be retrieved and added to the contact list, thereby adding the new contact to the contact list. In certain embodiments, user 110 could be notified via user terminal 112 of additions to the contact list.
[0103] Additionally, a user may cause or initiate the addition of a contact to the contact list. In certain embodiments, user 110 may be prompted to specify whether a called party should be placed in the contact list. For example, server 406 may prompt user 110 via user terminal 112 to specify whether or not a called party should be inserted in the contact list at the time of the outbound call to that party, Users could also add previously called parties to the contact list via the call log. In one example, a user may select a dialed number in the call log and, in response, contact information associated with the dialed number may be retrieved (e.g., via RDA processes) and added to the contact list. If the contact is not a new contact, a corresponding message may be displayed to the user, and the user may be prompted to specify whether the contact should be added. In exemplary embodiments of the present invention, the user may specify and alter the manner in which contacts are added to the contact list via, for example, user terminal 112, which may interface with elements in server 406, communication portal server 408, and/or back end server 420. For example, user 110 may set and change preferences via application function 516. In addition, user 110 may dynamically change the manner in which contacts are added to the contact list at any time. In one implementation of the invention, user 110 may set contact list preferences for the call log when filters are set (stage 701 ).
[0104] In certain embodiments of the present invention, data analyses may be performed using the call log. For example, the call log may enable a user to view calling patterns andlor frequencies. In one instance, a user could view all outgoing calls (or those to a particular party) occurring in a particular time period (e.g., one month). In certain embodiments, data analyses may be device-specific. That is, data analyses may be performed for each of the user's calling devices. In one example, the user could view calling patterns for and/or the calls originating from each of a plurality of calling devices.
Further, one or more different analyses could be performed for each calling device, depending on device type and/or user-specified parameters and instructions.
[0105] In exemplary implementations, server 406 may be configured to perform such analyses (e.g., via application function 516) using the call log.
Additionally or alternatively, user terminal 112 may include program code for performing the analyses. The results of the analyses may, in one example, be stored by database function 522 and/or storage 204. The user may access results of the analyses via user data network 120 and/or voice network 104. In one example, a user may access the call log (stage 770) and then initiate certain analyses and view results. Additionally or alternatively, the user may preset analyses to be performed and set parameters associated with such analyses in a manner similar to that described above in connection with stage 701 of Fig. 7. Users may then automatically receive (via data network 120 and/or voice network 104) analyses reports periodically and/or upon viewing the call log.
[0106] Embodiments consistent with the invention may be implemented in various environments. Further, the processes described herein are not inherently related to any particular apparatus and may be implemented by any suitable combination of components. Moreover, various types of general purpose devices may be used in accordance with the teachings described herein.
[0107] The exemplary systems and methods consistent with present invention described above are illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0108] The present invention has been described in relation to particular examples which are intended in all respects to be illustrative rather than restrictive. Different combinations of hardware, software, and firmware may be suitable for practicing embodiments of the present invention.
[0109] Additionally, other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only. To this end, it is to be understood that inventive aspects lie in less than all features of a single foregoing disclosed embodiment, implementation, or configuration. Thus, the true scope and spirit of the invention depends on the following claims.
Claims (36)
1. A method for logging calls comprising the steps implemented by one or more computers of:
receiving, from a user of a calling device, instructions that specify filter settings for logging outgoing calls to a plurality of parties in a call log, wherein the instructions indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log;
obtaining outgoing call information associated with an outgoing call originating from the calling device and destined to a called device associated with one of the parties, the outgoing call information reflecting a dialed number;
determining whether or not to log the outgoing call information based on the filter settings; and storing the outgoing call information in the call log in response to a determination to log the outgoing call information.
receiving, from a user of a calling device, instructions that specify filter settings for logging outgoing calls to a plurality of parties in a call log, wherein the instructions indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log;
obtaining outgoing call information associated with an outgoing call originating from the calling device and destined to a called device associated with one of the parties, the outgoing call information reflecting a dialed number;
determining whether or not to log the outgoing call information based on the filter settings; and storing the outgoing call information in the call log in response to a determination to log the outgoing call information.
2. The method of claim 1, further comprising:
providing the user of the calling device with access to the call log.
providing the user of the calling device with access to the call log.
3. The method of claim 1, wherein obtaining outgoing call information further comprises obtaining information associated with the user of the calling device and the party associated with the called device.
4. The method of claim 1, wherein obtaining information associated with the user of the calling device and the party associated with the called device includes obtaining a calling party telephone number and the dialed telephone number, respectively.
5. The method of claim 1 further comprising:
retrieving contact-related information associated with the user of the called device, using the outgoing call information; and adding the contact information to a contact list.
retrieving contact-related information associated with the user of the called device, using the outgoing call information; and adding the contact information to a contact list.
6. The method of claim 5, wherein retrieving contact-related information includes retrieving at least one of a name, a home address, a business address, or an e-mail address associated with the user of the called device.
7. The method of claim 5, wherein retrieving contact-related information includes retrieving a photograph.
8. The method of claim 5, wherein retrieving contact-related information includes retrieving information included in a public record.
9. The method of claim 1 further comprising:
performing at least one data analysis using the call log.
performing at least one data analysis using the call log.
10. The method of claim 9, wherein performing at least one data analysis includes displaying outgoing call patterns.
11. The method of claim 1, wherein receiving instructions from the user of the calling device that specify filter settings includes receiving instructions that indicate at least one outgoing call to include in the call log.
12. The method of claim 1, wherein determining whether or not to log the outgoing call information includes consulting the filter settings.
13. The method of claim 1, wherein the calling device is a landline telephone and wherein obtaining outgoing call information includes:
setting a trigger on a communication line associated with the landline telephone;
querying a service control point in response to the trigger; and initiating a service logic program in the service control point.
setting a trigger on a communication line associated with the landline telephone;
querying a service control point in response to the trigger; and initiating a service logic program in the service control point.
14. The method of claim 13 further including: transmitting at least the dialed telephone number to a server from the service logic program.
15. The method of claim 1, wherein the calling device is a programmable device and wherein obtaining outgoing call information includes capturing the outgoing call information by the programmable device.
16. The method of claim 15 further including: transmitting at least the dialed telephone number to a server from the programmable device.
17. A call log system comprising:
a first network providing telephony services;
a calling device input port, coupled to the first network, configured to interface a user with the first network;
a second network for facilitating data transfer;
a service center coupled to the first network and the second network, the service center comprising:
a first application function for generating a call log according to user-specified preferences, the call log including information associated with telephone calls originating from a user of a calling device to a plurality of parties, wherein the preferences indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log; and a storage function for storing the call log;
a user terminal input port, coupled to the second network and configured to interact with the service center, for enabling the user of the calling device to specify the preferences and access the call log.
a first network providing telephony services;
a calling device input port, coupled to the first network, configured to interface a user with the first network;
a second network for facilitating data transfer;
a service center coupled to the first network and the second network, the service center comprising:
a first application function for generating a call log according to user-specified preferences, the call log including information associated with telephone calls originating from a user of a calling device to a plurality of parties, wherein the preferences indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log; and a storage function for storing the call log;
a user terminal input port, coupled to the second network and configured to interact with the service center, for enabling the user of the calling device to specify the preferences and access the call log.
18. The system of claim 17, wherein the first network is a Public Switched Telephone Network (PSTN).
19. The system of claim 17, wherein the first network is operable to perform Voice over Internet Protocol (VolP).
20. The system of claim 17, wherein the first network includes a Public Switched Telephone Network (PSTN) and wherein the calling device input port is an interface receiving information from a landline telephone.
21. The system of claim 20, wherein the information associated with the telephone calls includes a dialed telephone number and wherein a service control point coupled to the PSTN transmits the dialed telephone number to the server.
22. The system of claim 17, wherein the calling device input port is an interface receiving information from a programmable device.
23. The system of claim 22, wherein the information associated with the telephone calls includes at least a dialed telephone number and wherein the dialed telephone number is received by the service center.
24. The system of claim 17, wherein the second network includes at least one of a wide area network (WAN), a local area network (LAN), an intranet, and the Internet.
25. The system of claim 17, wherein the storage function includes at least one database.
26. The system of claim 17, wherein the application function includes program code for performing at least one data analysis using the call log.
27. The system of claim 26, wherein the data analysis includes determining outgoing call patterns.
28. The system of claim 17, wherein the service center retrieves, via a second application function, contact information associated with recipients of the telephone calls originating from the calling device using the call log.
29. The system of claim 28, wherein the information associated with the telephone calls includes at least dialed telephone numbers and wherein the second application function retrieves contact information associated with at least one of the dialed telephone numbers from an Internet-based service.
30. The system of claim 28, wherein the contact information includes at least one of a name, a home address, a business address, or an e-mail address.
31. The system of claim 28, wherein the service center further comprises a contacts database function configured to store the retrieved contact information.
32. The system of claim 17, wherein the user terminal is one of a general purpose computer, a personal computer, a wireless device, a pager, a mobile phone having data access functions, and a Personal Digital Assistants (PDA).
33. A computer-readable medium containing instructions for controlling at least one processor to perform a method for logging calls, the method comprising:
receiving, from a user of a calling device, instructions that specify filter settings for logging outgoing calls to a plurality of parties in a call log, wherein the instructions received from the user indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log;
obtaining outgoing call information associated with an outgoing call originating from the calling device and destined to a called device associated with one of the parties, the outgoing call information reflecting a dialed number;
determining whether or not to log the outgoing call information based on the filter settings; and storing the outgoing call information in the call log in response to a determination to log the outgoing call information.
receiving, from a user of a calling device, instructions that specify filter settings for logging outgoing calls to a plurality of parties in a call log, wherein the instructions received from the user indicate that calls from the user of the calling device to a first one of the parties are to be excluded from the call log;
obtaining outgoing call information associated with an outgoing call originating from the calling device and destined to a called device associated with one of the parties, the outgoing call information reflecting a dialed number;
determining whether or not to log the outgoing call information based on the filter settings; and storing the outgoing call information in the call log in response to a determination to log the outgoing call information.
34. The method according to claim 5, wherein the dialed number is added to the contact list automatically.
35. The method according to claim 5, wherein the dialed number is added to the contact list in response to a command from the user.
36. The method according to claim 1, further comprising retrieving contact information associated with the dialed number in the log using reverse directory assistance.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US42870402P | 2002-11-25 | 2002-11-25 | |
US60/428,704 | 2002-11-25 | ||
US43601802P | 2002-12-26 | 2002-12-26 | |
US60/436,018 | 2002-12-26 | ||
PCT/US2003/037874 WO2004049136A2 (en) | 2002-11-25 | 2003-11-25 | Methods and systems for a call log |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2507492A1 CA2507492A1 (en) | 2004-06-10 |
CA2507492C true CA2507492C (en) | 2013-07-23 |
Family
ID=36889266
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA2507492A Expired - Fee Related CA2507492C (en) | 2002-11-25 | 2003-11-25 | Methods and systems for a call log |
Country Status (6)
Country | Link |
---|---|
US (1) | US8488761B2 (en) |
EP (1) | EP1568198A4 (en) |
JP (1) | JP4588454B2 (en) |
AU (1) | AU2003295971A1 (en) |
CA (1) | CA2507492C (en) |
WO (1) | WO2004049136A2 (en) |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6832245B1 (en) | 1999-12-01 | 2004-12-14 | At&T Corp. | System and method for analyzing communications of user messages to rank users and contacts based on message content |
US7774711B2 (en) | 2001-09-28 | 2010-08-10 | Aol Inc. | Automatic categorization of entries in a contact list |
US6909910B2 (en) | 2002-02-01 | 2005-06-21 | Microsoft Corporation | Method and system for managing changes to a contact database |
US7221748B1 (en) * | 2002-11-12 | 2007-05-22 | Bellsouth Intellectual Property Corporation | Method for linking call log information to address book entries and replying using medium of choice |
US7945674B2 (en) | 2003-04-02 | 2011-05-17 | Aol Inc. | Degrees of separation for handling communications |
US7263614B2 (en) | 2002-12-31 | 2007-08-28 | Aol Llc | Implicit access for communications pathway |
US20050032518A1 (en) * | 2003-03-26 | 2005-02-10 | Rajan Nandan Sunder | Attribute based communication |
US20040205127A1 (en) | 2003-03-26 | 2004-10-14 | Roy Ben-Yoseph | Identifying and using identities deemed to be known to a user |
ITPI20030101A1 (en) * | 2003-12-05 | 2005-06-06 | Cdc Srl | METHOD AND APPARATUS FOR THE MANAGEMENT OF GLOBALITY |
TWM258512U (en) * | 2004-02-25 | 2005-03-01 | Carry Computer Eng Co Ltd | A digital voice record apparatus that has phone recording function |
US8898239B2 (en) | 2004-03-05 | 2014-11-25 | Aol Inc. | Passively populating a participant list with known contacts |
JP4154372B2 (en) * | 2004-07-28 | 2008-09-24 | 富士通株式会社 | Mobile device |
US7324505B2 (en) * | 2004-12-24 | 2008-01-29 | Christopher Hoover | Sustained VOIP call logs using PoC contact lists |
US8031645B2 (en) * | 2005-04-08 | 2011-10-04 | Qualcomm Incorporated | Archival of session data exchanged with a wireless communication network |
CN100466792C (en) * | 2005-10-29 | 2009-03-04 | 华为技术有限公司 | Method for recording and output call journal information and application and system |
CN100372419C (en) * | 2005-11-29 | 2008-02-27 | 华为技术有限公司 | System and method for analyzing call in mobile communication system |
US8126120B2 (en) | 2005-12-12 | 2012-02-28 | Tellme Networks, Inc. | Providing missed call and message information |
US9762623B1 (en) * | 2005-12-22 | 2017-09-12 | Apple Inc. | Automatic call initiation in response to selecting tags in electronic documents and applications |
GB0624577D0 (en) * | 2006-12-08 | 2007-01-17 | Skype Ltd | Communication Systems |
US8745680B2 (en) * | 2007-01-06 | 2014-06-03 | At&T Intellectual Property I, Lp | Techniques for call integration with a television set-top box (STB) |
US7765261B2 (en) | 2007-03-30 | 2010-07-27 | Uranus International Limited | Method, apparatus, system, medium and signals for supporting a multiple-party communication on a plurality of computer servers |
US7765266B2 (en) | 2007-03-30 | 2010-07-27 | Uranus International Limited | Method, apparatus, system, medium, and signals for publishing content created during a communication |
US7950046B2 (en) | 2007-03-30 | 2011-05-24 | Uranus International Limited | Method, apparatus, system, medium, and signals for intercepting a multiple-party communication |
US8627211B2 (en) | 2007-03-30 | 2014-01-07 | Uranus International Limited | Method, apparatus, system, medium, and signals for supporting pointer display in a multiple-party communication |
US8702505B2 (en) | 2007-03-30 | 2014-04-22 | Uranus International Limited | Method, apparatus, system, medium, and signals for supporting game piece movement in a multiple-party communication |
US8060887B2 (en) | 2007-03-30 | 2011-11-15 | Uranus International Limited | Method, apparatus, system, and medium for supporting multiple-party communications |
US8180807B2 (en) * | 2007-11-27 | 2012-05-15 | At&T Intellectual Property I, L.P. | System and method of determining relationship information |
JP5206135B2 (en) * | 2008-06-09 | 2013-06-12 | 富士通モバイルコミュニケーションズ株式会社 | Mobile device |
US20100284284A1 (en) * | 2009-05-08 | 2010-11-11 | Qualcomm Incorporated | VOICE OVER INTERNET PROTOCOL (VoIP) ACCESS TERMINAL |
US8462919B2 (en) | 2009-09-09 | 2013-06-11 | Deutsche Telekom Ag | System and method for call logging and retrieval |
US9020122B2 (en) * | 2010-05-19 | 2015-04-28 | Avaya Inc. | Method and apparatus for tagging outgoing telephony calls |
US10068670B2 (en) | 2012-08-16 | 2018-09-04 | Ginger.io, Inc. | Method for modeling behavior and depression state |
WO2014028888A2 (en) | 2012-08-16 | 2014-02-20 | Ginger.io, Inc. | Method for modeling behavior and health changes |
US10741285B2 (en) | 2012-08-16 | 2020-08-11 | Ginger.io, Inc. | Method and system for providing automated conversations |
US10740438B2 (en) | 2012-08-16 | 2020-08-11 | Ginger.io, Inc. | Method and system for characterizing and/or treating poor sleep behavior |
US10346542B2 (en) * | 2012-08-31 | 2019-07-09 | Verint Americas Inc. | Human-to-human conversation analysis |
US10521480B2 (en) | 2013-05-07 | 2019-12-31 | International Business Machines Corporation | Informative communication history |
US10194010B1 (en) * | 2017-09-29 | 2019-01-29 | Whatsapp Inc. | Techniques to manage contact records |
US11163961B2 (en) | 2018-05-02 | 2021-11-02 | Verint Americas Inc. | Detection of relational language in human-computer conversation |
US11822888B2 (en) | 2018-10-05 | 2023-11-21 | Verint Americas Inc. | Identifying relational segments |
US11710576B2 (en) | 2021-05-24 | 2023-07-25 | OrangeDot, Inc. | Method and system for computer-aided escalation in a digital health platform |
Family Cites Families (425)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US5168515A (en) | 1989-11-27 | 1992-12-01 | Unifi Communications Corporation | Switchless automatic call distribution system |
US5274700A (en) | 1989-11-27 | 1993-12-28 | Unifi Communications Corporation | Methods of automatically rerouting an incoming telephone call placed over a network |
US5014303A (en) * | 1989-12-18 | 1991-05-07 | Bell Communications Research, Inc. | Operator services using speech processing |
JP3224384B2 (en) * | 1990-07-20 | 2001-10-29 | 富士通株式会社 | Call control method in intelligent network |
US5222125A (en) | 1991-09-03 | 1993-06-22 | At&T Bell Laboratories | System for providing personalized telephone calling features |
CA2076434C (en) * | 1991-10-09 | 1996-07-02 | Gary Joe Grimes | Incoming communications forwarding technique utilizing a called party location indicator |
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 |
CA2100139C (en) | 1992-09-29 | 1997-02-18 | William Walter Demlow | Information display provided to calling party |
US5440624A (en) | 1992-11-10 | 1995-08-08 | Netmedia, Inc. | Method and apparatus for providing adaptive administration and control of an electronic conference |
GB2272312A (en) | 1992-11-10 | 1994-05-11 | Ibm | Collaborative working in a network. |
US5327486A (en) | 1993-03-22 | 1994-07-05 | Bell Communications Research, Inc. | Method and system for managing telecommunications such as telephone calls |
US6717938B1 (en) * | 1999-04-15 | 2004-04-06 | J2 Global Communications, Inc. | System controlling use of a communication channel |
DE69402716T2 (en) | 1993-06-11 | 1997-12-11 | Northern Telecom Ltd | METHOD FOR SUPPLYING CALL MANAGEMENT SERVICES CONTROLLED BY THE USER |
US5533096A (en) | 1993-06-14 | 1996-07-02 | At&T Corp. | Send-all-calls feature for a wireless handset |
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 |
US5920847A (en) | 1993-11-01 | 1999-07-06 | Visa International Service Association | Electronic bill pay system |
US5535265A (en) * | 1993-11-15 | 1996-07-09 | Ast Research, Inc. | Method and circuitry for controlling voice mail, call logging and call blocking functions using a modem |
JPH07219970A (en) | 1993-12-20 | 1995-08-18 | Xerox Corp | Method and apparatus for reproduction in acceleration format |
US5543343A (en) * | 1993-12-22 | 1996-08-06 | Sgs-Thomson Microelectronics, Inc. | Method fabricating an integrated circuit |
GB2285895A (en) | 1994-01-19 | 1995-07-26 | Ibm | Audio conferencing system which generates a set of minutes |
US5719925A (en) * | 1994-03-02 | 1998-02-17 | Peoples; John T. | Method for remotely controlling a telephone loop/channel from another telephone loop/channel |
US6628772B1 (en) | 1994-04-28 | 2003-09-30 | Metro One Telecommunications, Inc. | Method for providing enhanced directory assistance upon command using out-of-band signaling |
CA2150060C (en) | 1994-07-08 | 2000-01-11 | John T. Biggs | Seamless multimedia conferencing system using enhanced endpoint devices |
US5483586A (en) | 1994-07-18 | 1996-01-09 | Sussman; Lester | Electronic on-line subscriber telephone directory |
US5742905A (en) | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
US5652789A (en) | 1994-09-30 | 1997-07-29 | Wildfire Communications, Inc. | Network based knowledgeable assistant |
US6188756B1 (en) | 1994-10-11 | 2001-02-13 | Alexander Mashinsky | Efficient communication through networks |
US5715444A (en) * | 1994-10-14 | 1998-02-03 | Danish; Mohamed Sherif | Method and system for executing a guided parametric search |
CA2159249C (en) * | 1994-11-21 | 1998-09-22 | Mark A. Fitser | Method for automatically establishing a conference call |
US5550907A (en) | 1994-12-23 | 1996-08-27 | Lucent Technologies Inc. | Personal communication using intelligent terminals |
KR0135777B1 (en) | 1995-01-25 | 1998-04-27 | 김광호 | Selecting calling phone |
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 |
JP3341201B2 (en) * | 1995-08-23 | 2002-11-05 | 日本電信電話株式会社 | Network information management device |
JP3210926B2 (en) * | 1995-08-23 | 2001-09-25 | 日本電信電話株式会社 | Communication service control system and method |
US5638434A (en) | 1995-08-30 | 1997-06-10 | Mci Corporation | Conference system for dial-out telephone calls |
US5621787A (en) | 1995-09-13 | 1997-04-15 | Bell Atlantic Network Services, Inc. | Prepaid cash card |
US5717863A (en) | 1995-09-27 | 1998-02-10 | Intel Corporation | Method and apparatus for managing pc conference connection addresses |
US5751800A (en) * | 1995-12-15 | 1998-05-12 | Lucent Technologies Inc. | Screening of incoming telephone calls prior to call completion to the destination party |
US5764901A (en) | 1995-12-21 | 1998-06-09 | Intel Corporation | Record and playback in a data conference |
FI101661B1 (en) | 1996-01-08 | 1998-07-31 | Nokia Mobile Phones Ltd | Activate the phone's own answering machine according to the caller's number |
GB9603020D0 (en) | 1996-02-14 | 1996-04-10 | British Telecomm | Establishing communication |
US5805670A (en) | 1996-03-19 | 1998-09-08 | Life Safety Solutions, Inc. | Private notification system for communicating 9-1-1 information |
US6041103A (en) | 1996-04-16 | 2000-03-21 | Lucent Technologies, Inc. | Interactive call identification |
US5918227A (en) * | 1996-05-06 | 1999-06-29 | Switchboard, Inc. | On-line directory service with a plurality of databases and processors |
US5745561A (en) * | 1996-05-31 | 1998-04-28 | Lucent Technologies Inc. | Multiple independent named call-coverage paths |
US5903845A (en) * | 1996-06-04 | 1999-05-11 | At&T Wireless Services Inc. | Personal information manager for updating a telecommunication subscriber profile |
JP3216992B2 (en) | 1996-06-14 | 2001-10-09 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Connection method in network system and server machine |
US5875242A (en) * | 1996-07-26 | 1999-02-23 | Glaser; Lawrence F. | Telecommunications installation and management system and method |
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 |
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 |
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 |
US5945989A (en) | 1997-03-25 | 1999-08-31 | Premiere Communications, Inc. | Method and apparatus for adding and altering content on websites |
US6546005B1 (en) * | 1997-03-25 | 2003-04-08 | At&T Corp. | Active user registry |
US6167119A (en) | 1997-03-28 | 2000-12-26 | Bell Atlantic Network Services, Inc. | Providing enhanced services through SIV and personal dial tone |
US6192123B1 (en) * | 1997-04-14 | 2001-02-20 | National Tech Team Inc. | Method and apparatus for initiating telephone calls using a data network |
US6333973B1 (en) | 1997-04-23 | 2001-12-25 | Nortel Networks Limited | Integrated message center |
US6282522B1 (en) | 1997-04-30 | 2001-08-28 | Visa International Service Association | Internet payment system using smart card |
US6480890B1 (en) | 1997-05-30 | 2002-11-12 | Alcatel Usa Sourcing, L.P. | World Wide Web interface to telecom service creation environment |
US6189026B1 (en) * | 1997-06-16 | 2001-02-13 | Digital Equipment Corporation | Technique for dynamically generating an address book in a distributed electronic mail system |
JP3782867B2 (en) | 1997-06-25 | 2006-06-07 | 株式会社日立製作所 | Information reception processing method and computer / telephony integration system |
CA2240878A1 (en) | 1997-06-27 | 1998-12-27 | Vikram R. Saksena | Internet based ip multicast conferencing and reservation system |
US6058415A (en) * | 1997-07-24 | 2000-05-02 | Intervoice Limited Partnership | System and method for integration of communication systems with computer-based information systems |
US6219413B1 (en) * | 1997-08-07 | 2001-04-17 | At&T Corp. | Apparatus and method for called-party telephone messaging while interconnected to a data network |
US6567671B2 (en) | 1997-08-11 | 2003-05-20 | At&T Wireless Services, Inc. | Wireless communication device with call screening |
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 |
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 |
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 |
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 |
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 |
US20020128033A1 (en) | 1998-11-30 | 2002-09-12 | Burgess Shelia Jean | Communications control method and apparatus |
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 |
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 |
JP4484277B2 (en) | 1998-09-25 | 2010-06-16 | 株式会社日立製作所 | Service control device and gateway device |
US6876632B1 (en) * | 1998-09-25 | 2005-04-05 | Hitachi, Ltd. | Intelligent network with an internet call waiting function |
US7509349B2 (en) | 1998-10-01 | 2009-03-24 | Onepin, Inc. | Method and apparatus for storing and retrieving business contact information in a computer system |
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 |
US7836011B2 (en) * | 1998-10-01 | 2010-11-16 | Onepin, Inc. | Phone to phone data exchange |
US6724867B1 (en) * | 1998-10-06 | 2004-04-20 | Daniel A. Henderson | Method and apparatus for automatic message transfer from a remote messaging system to a local communication device |
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 |
US6031896A (en) * | 1998-10-23 | 2000-02-29 | Gte Laboratories Incorporated | Real-time voicemail monitoring and call control over the internet |
US6298062B1 (en) | 1998-10-23 | 2001-10-02 | Verizon Laboratories Inc. | System providing integrated services over a computer network |
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 |
US6349299B1 (en) * | 1998-12-24 | 2002-02-19 | International Business Machines Corporation | System and method for storing electronic contact information into an electronic address book |
JP2000196756A (en) | 1998-12-25 | 2000-07-14 | Kansai Nippon Denki Tsushin System Kk | Incoming call transfer system |
US6885742B1 (en) * | 1998-12-29 | 2005-04-26 | Cingular Wireless Ii, Inc. | System and method for integrating call delivery for fixed-site and mobility services |
US6681119B1 (en) | 1998-12-31 | 2004-01-20 | Nortel Networks Ltd | Wireless communication system in which a call from a private branch exchange is selectively delivered to a mobile unit |
US6574470B1 (en) | 1998-12-31 | 2003-06-03 | At&T Corp. | Programmable ring-call forwarding in a wireless centrex services system |
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 |
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 |
US6628194B1 (en) | 1999-08-31 | 2003-09-30 | At&T Wireless Services, Inc. | Filtered in-box for voice mail, e-mail, pages, web-based information, and faxes |
US6442748B1 (en) | 1999-08-31 | 2002-08-27 | Accenture Llp | System, method and article of manufacture for a persistent state and persistent object separator in an information services patterns environment |
US6373930B1 (en) | 1999-09-09 | 2002-04-16 | Sprint Communications Company L.P. | Method and system for monitoring telecommunications traffic |
US6873693B1 (en) | 1999-09-13 | 2005-03-29 | Microstrategy, Incorporated | System and method for real-time, personalized, dynamic, interactive voice services for entertainment-related information |
US6577622B1 (en) | 1999-09-27 | 2003-06-10 | 3Com Corp. | System and method for using a portable information device to establish a conference call on a telephony network |
US6718178B1 (en) * | 1999-10-01 | 2004-04-06 | Sprint Spectrum, L.P. | Automatic in-line messaging system |
US6704294B1 (en) * | 1999-10-13 | 2004-03-09 | Nortel Networks Limited | Establishment of a PSTN and internet multimedia collaboration session |
US6798753B1 (en) | 1999-10-14 | 2004-09-28 | International Business Machines Corporation | Automatically establishing conferences from desktop applications over the Internet |
US6594470B1 (en) | 1999-10-28 | 2003-07-15 | Nortel Networks Limited | System and method for remote management of call center operations |
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 |
US6870921B1 (en) | 1999-11-12 | 2005-03-22 | Metro One Telecommunications, Inc. | Enhanced directory assistance service providing individual or group directories |
US20020055351A1 (en) * | 1999-11-12 | 2002-05-09 | Elsey Nicholas J. | Technique for providing personalized information and communications services |
JP2001144859A (en) | 1999-11-17 | 2001-05-25 | Matsushita Electric Ind Co Ltd | Method and device for registering telephone directory information |
US6614786B1 (en) | 1999-11-24 | 2003-09-02 | Lucent Technologies Inc. | Enhanced dual mode telephone for internet telephony |
US6574324B1 (en) | 1999-11-24 | 2003-06-03 | Bellsouth Intellectual Property Corporation | System and method for long distance automatic call-back |
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 |
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 |
US6735292B1 (en) * | 1999-12-17 | 2004-05-11 | Worldcom, Inc. | Method and system for priority call processing |
US6853713B1 (en) | 1999-12-17 | 2005-02-08 | Nortel Networks Limited | Client-server network for managing internet protocol voice packets |
GB2391134B (en) | 1999-12-23 | 2004-05-12 | Mitel Knowledge Corp | Communication system architecture for voice first collaboration |
US6625258B1 (en) | 1999-12-27 | 2003-09-23 | Nortel Networks Ltd | System and method for providing unified communication services support |
US6577720B1 (en) | 1999-12-29 | 2003-06-10 | Nortel Networks Corporation | System and method for providing high-speed communications using a public terminal |
US7139728B2 (en) | 1999-12-30 | 2006-11-21 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US6373817B1 (en) * | 1999-12-30 | 2002-04-16 | At&T Corp. | Chase me system |
US6917610B1 (en) * | 1999-12-30 | 2005-07-12 | At&T Corp. | Activity log for improved call efficiency |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
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 |
US6275575B1 (en) | 2000-01-12 | 2001-08-14 | Right4Me.Com, Inc. | Method and system for coordinating and initiating cross-platform telephone conferences |
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 |
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 |
US6697461B1 (en) | 2000-02-15 | 2004-02-24 | Bell Atlantic Services Network | Methods and apparatus for providing call screening and other communication services |
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 |
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 |
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 |
CA2404004A1 (en) | 2000-03-31 | 2001-10-11 | Nortel Networks Limited | Internet call waiting with voice mail system that provides monitoring during recording |
US20020022453A1 (en) | 2000-03-31 | 2002-02-21 | Horia Balog | Dynamic protocol selection and routing of content to mobile devices |
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 |
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 |
JP2002044123A (en) | 2000-07-25 | 2002-02-08 | Nec Corp | Integrated messaging system |
US20020071539A1 (en) * | 2000-07-25 | 2002-06-13 | Marc Diament | Method and apparatus for telephony-enabled instant messaging |
JP2002044257A (en) | 2000-07-27 | 2002-02-08 | Dainippon Printing Co Ltd | Information providing system |
US20030167229A1 (en) | 2001-04-03 | 2003-09-04 | Bottomline Technologies, Inc. | Modular business transations platform |
IE20010743A1 (en) | 2000-08-04 | 2002-04-17 | Mobileaware Technologies Ltd | An e-business mobility 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 |
JP2002084359A (en) * | 2000-09-07 | 2002-03-22 | Matsushita Electric Ind Co Ltd | Portable information terminal, communication method, and recording medium |
JP2002094696A (en) | 2000-09-13 | 2002-03-29 | Nec Access Technica Ltd | Device of turning accumulated voice into electronic mail and answer telephone service system |
US6442251B1 (en) | 2000-09-29 | 2002-08-27 | Palm Incorporated | Method and apparatus for taking a note while in a call |
US20020062251A1 (en) | 2000-09-29 | 2002-05-23 | Rajan Anandan | System and method for wireless consumer communications |
US20020040355A1 (en) | 2000-10-02 | 2002-04-04 | Weiner Steven D. | System and method for utility meter swipecard |
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 |
US7031437B1 (en) | 2000-10-30 | 2006-04-18 | Nortel Networks Limited | Method and system for providing remote access to previously transmitted enterprise messages |
US20020085701A1 (en) | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified communication management based on presence information |
US20020078153A1 (en) | 2000-11-02 | 2002-06-20 | Chit Chung | Providing secure, instantaneous, directory-integrated, multiparty, communications services |
US6693897B1 (en) | 2000-11-10 | 2004-02-17 | Sbc Technology Resources, Inc. | Method and system of screening and control of telephone calls while using a packet-switched data network |
DE60103085T2 (en) | 2000-11-20 | 2004-11-25 | British Telecommunications P.L.C. | METHOD FOR MANAGING RESOURCES |
US7317787B2 (en) | 2000-11-21 | 2008-01-08 | At&T Knowledge Ventures, L.P. | Voice enhancing for advance intelligent network services |
US7155001B2 (en) | 2001-10-24 | 2006-12-26 | Sbc Properties, L.P. | System and method for restricting and monitoring telephone calls |
DE10059327A1 (en) | 2000-11-29 | 2002-06-20 | Siemens Ag | Device and method for forwarding messages to end devices of various communication media |
DE10059175A1 (en) * | 2000-11-29 | 2002-06-20 | Siemens Ag | Method for diverting calls in a communications system with multiple terminals connects to a local area network for activating call rerouting from one terminal to another, for transferring information and for diverting a call. |
US6697473B2 (en) | 2000-12-04 | 2004-02-24 | Bobby G. Batten | Automated personalized telephone management system |
DE10060809A1 (en) | 2000-12-07 | 2002-06-20 | Aventis Pharma Gmbh | Substituted anthranilic acids, their use as medicaments or diagnostic agents, as well as medicaments containing them, and a combined pharmaceutical preparation with a sodium / hydrogen exchange (NHE) blocker |
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 |
US20020075306A1 (en) * | 2000-12-18 | 2002-06-20 | Christopher Thompson | Method and system for initiating communications with dispersed team members from within a virtual team environment using personal identifiers |
US20020075303A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited And Bell Canada | Method and system for creating a virtual team environment |
US20020077082A1 (en) | 2000-12-18 | 2002-06-20 | Nortel Networks Limited | Voice message presentation on personal wireless devices |
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 |
US6792092B1 (en) | 2000-12-20 | 2004-09-14 | Cisco Technology, Inc. | Method and system for independent participant control of audio during multiparty communication sessions |
US7024209B1 (en) | 2000-12-20 | 2006-04-04 | Cisco Technology, Inc. | Unified messaging system configured for management of short message service-type messages |
US20020076027A1 (en) | 2000-12-20 | 2002-06-20 | Nortel Networks Limited | Fallback to message compose on synchronous call attempt |
US20020080942A1 (en) | 2000-12-21 | 2002-06-27 | Clapper Edward O. | Origin-independent custom caller ID |
US20020083462A1 (en) | 2000-12-21 | 2002-06-27 | Arnott Robert J. | Apparatus and method for establishing audio and video conferencing |
US20020082028A1 (en) | 2000-12-22 | 2002-06-27 | Wittenkamp Peter David Forsling | Paging and selective call routing in a telecommunication environment |
US7209966B2 (en) | 2000-12-22 | 2007-04-24 | Openwave Systems Inc. | Method and system for facilitating mediated communication |
EP1348165A4 (en) | 2000-12-26 | 2009-01-28 | Polycom Inc | System and method for coordinating a conference using a dedicated server |
JP3833470B2 (en) | 2000-12-27 | 2006-10-11 | 三菱電機株式会社 | Multipoint communication system and multipoint communication method |
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 |
US6647108B1 (en) | 2001-01-02 | 2003-11-11 | Verizon Services Corp. | Internet call manager |
CA2368404C (en) | 2001-01-18 | 2005-08-09 | Research In Motion Limited | Unified messaging system and method |
US20020103898A1 (en) | 2001-01-31 | 2002-08-01 | Moyer Stanley L. | System and method for using session initiation protocol (SIP) to communicate with networked appliances |
JP3929248B2 (en) | 2001-02-02 | 2007-06-13 | 株式会社イメ−ジパ−トナ− | Telephone conference system |
US7107312B2 (en) | 2001-02-06 | 2006-09-12 | Lucent Technologies Inc. | Apparatus and method for use in a data/conference call system for automatically collecting participant information and providing all participants with that information for use in collaboration services |
US20020147777A1 (en) | 2001-02-06 | 2002-10-10 | Hackbarth Randy L. | Apparatus and method for use in portal service for a team utilizing collaboration services |
JP2002237893A (en) | 2001-02-09 | 2002-08-23 | Nippon Telegr & Teleph Corp <Ntt> | Method and equipment for communication |
US6950402B2 (en) | 2001-02-15 | 2005-09-27 | Persona Software, Inc. | Web-enabled call management method and apparatus |
US7254220B1 (en) | 2001-02-16 | 2007-08-07 | Telesector Resources Group, Inc. | Methods and apparatus for obtaining and distributing voice mail information |
JP2002247148A (en) | 2001-02-18 | 2002-08-30 | Tanabe Junzo | Communication controller with phone incoming notice function and notice method |
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 |
US8774380B2 (en) * | 2001-02-27 | 2014-07-08 | Verizon Patent And Licensing Inc. | 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 |
US7142646B2 (en) | 2001-02-27 | 2006-11-28 | Verizon Data Services Inc. | Voice mail integration with instant messenger |
US7912193B2 (en) * | 2001-02-27 | 2011-03-22 | Verizon Data Services Llc | Methods and systems for call management with user intervention |
US8503639B2 (en) | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Method and apparatus for adaptive message and call notification |
JP2002261834A (en) | 2001-02-27 | 2002-09-13 | Ntt Advanced Technology Corp | Method and system for processing communication |
US20050220286A1 (en) | 2001-02-27 | 2005-10-06 | John Valdez | Method and apparatus for facilitating integrated access to communications services in a communication device |
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 |
US7190773B1 (en) | 2001-02-27 | 2007-03-13 | Verizon Data Services Inc. | Device independent caller ID |
US20060276179A1 (en) | 2001-02-27 | 2006-12-07 | Reza Ghaffari | Methods and systems for integrating communications services |
US8488766B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for multiuser selective notification |
KR20020071296A (en) | 2001-03-06 | 2002-09-12 | 삼성전자 주식회사 | Method for forwarding short message in mobile telecommunication system |
US6788772B2 (en) * | 2001-03-07 | 2004-09-07 | Zvi Barak | System and method for controlling outgoing telephone calls |
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 |
US20020137530A1 (en) | 2001-03-08 | 2002-09-26 | Katyayini Karve | Cellular telephone with SMS message forwarding |
WO2002073984A1 (en) | 2001-03-09 | 2002-09-19 | Ayman, L.L.C. | Universal point of contact identifier system and method |
US20020137507A1 (en) | 2001-03-20 | 2002-09-26 | Techimage, Llp., | System and method for providing automatic multimedia messages service |
JP2002300306A (en) | 2001-03-30 | 2002-10-11 | Tsubasa System Co Ltd | Telephone number information distribution method, telephone number information distribution program, and telephone number information distribution system |
JP2002300290A (en) | 2001-04-02 | 2002-10-11 | Nippon Telegr & Teleph Corp <Ntt> | Method and system for managing communication history information, program therefor and recording medium |
US20020178117A1 (en) | 2001-04-03 | 2002-11-28 | Bottomline Technologies (De) Inc. | Electronic bill presentment system with automated tax and fee adjustment |
US20020146105A1 (en) | 2001-04-05 | 2002-10-10 | International Business Machines Corporation | Interactive call forwarding |
US20020152165A1 (en) | 2001-04-12 | 2002-10-17 | International Business Machines Corporation | Method and apparatus for bill payments at an automatic teller machine |
US6661340B1 (en) | 2001-04-24 | 2003-12-09 | Microstrategy Incorporated | System and method for connecting security systems to a wireless device |
US6820055B2 (en) | 2001-04-26 | 2004-11-16 | Speche Communications | Systems and methods for automated audio transcription, translation, and transfer with text display software for manipulating the text |
US20030187992A1 (en) | 2001-05-07 | 2003-10-02 | Steenfeldt Rico Werni | Service triggering framework |
JP2002344652A (en) | 2001-05-21 | 2002-11-29 | Nec Access Technica Ltd | Mobile communication terminal and reply method by electronic mail |
DE10125284A1 (en) | 2001-05-23 | 2002-11-28 | Alcatel Sa | Procedure for selecting one of at least two devices |
US20050102382A1 (en) | 2001-06-04 | 2005-05-12 | Macgregor Glenn | System and method for network management using instant messaging |
US20030014488A1 (en) * | 2001-06-13 | 2003-01-16 | Siddhartha Dalal | System and method for enabling multimedia conferencing services on a real-time communications platform |
US6842460B1 (en) * | 2001-06-27 | 2005-01-11 | Nokia Corporation | Ad hoc network discovery menu |
US7076528B2 (en) | 2001-07-11 | 2006-07-11 | Symbol Technologies, Inc. | System and method for communicating messages between a host computer and a designated device |
US20030036380A1 (en) * | 2001-08-01 | 2003-02-20 | Skidmore Adrian Gary | Method of data transfer |
US6958984B2 (en) | 2001-08-02 | 2005-10-25 | Motorola, Inc. | Method and apparatus for aggregation of wireless resources of proximal wireless units to facilitate diversity signal combining |
US7315614B2 (en) | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
US20030035381A1 (en) | 2001-08-16 | 2003-02-20 | Yihsiu Chen | Network-based teleconferencing capabilities utilizing data network call set-up requests |
KR20030020768A (en) | 2001-09-04 | 2003-03-10 | 주식회사 케이티 | Description of automatic voice call connection service method by construction of personal phone book database using speech recognition and its related methods |
US6658260B2 (en) * | 2001-09-05 | 2003-12-02 | Telecommunication Systems, Inc. | Inter-carrier short messaging service providing phone number only experience |
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 |
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 |
US6996227B2 (en) * | 2001-10-24 | 2006-02-07 | Motorola, Inc. | Systems and methods for storing information associated with a subscriber |
US6674459B2 (en) | 2001-10-24 | 2004-01-06 | Microsoft Corporation | Network conference recording system and method including post-conference processing |
US6590603B2 (en) | 2001-10-31 | 2003-07-08 | Forgent Networks, Inc. | System and method for managing streaming data |
US20030083040A1 (en) * | 2001-11-01 | 2003-05-01 | Todd Ruth | Method of logging call processing information in a mobile communication network |
US20030208541A1 (en) | 2001-11-10 | 2003-11-06 | Jeff Musa | Handheld wireless conferencing technology |
US20030092451A1 (en) * | 2001-11-15 | 2003-05-15 | Ibm Corporation | Method of mobile phone consolidation |
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 |
US20030112952A1 (en) | 2001-12-19 | 2003-06-19 | Wendell Brown | Automatically establishing a telephone connection between a subscriber and a party meeting one or more criteria |
US6668049B1 (en) | 2001-12-19 | 2003-12-23 | Bellsouth Intellectual Property Corporation | Systems and methods for intelligent third-party redirection of an incoming call via a display-based communication center |
US7116994B2 (en) | 2001-12-21 | 2006-10-03 | Nokia Corporation | Mobile network message to email redirection |
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 |
US6882714B2 (en) * | 2002-03-27 | 2005-04-19 | Sharp Laboratories Of America, Inc. | Universal call-log system and method for a home network telephone |
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 |
JP2003298737A (en) * | 2002-03-29 | 2003-10-17 | Tamura Electric Works Ltd | Telephone device management system, server, telephone device and program |
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 |
US6956942B2 (en) | 2002-09-18 | 2005-10-18 | Sbc Properties, L.P. | Multi-modal address book |
US7212808B2 (en) | 2002-10-15 | 2007-05-01 | Wildseed Ltd. | Unified message box for wireless mobile communication devices |
US20040081292A1 (en) * | 2002-10-23 | 2004-04-29 | International Business Machines Corporation | System and method for managing personel telephony recording |
US7065198B2 (en) | 2002-10-23 | 2006-06-20 | International Business Machines Corporation | System and method for volume control management in a personal telephony recorder |
US7428580B2 (en) | 2003-11-26 | 2008-09-23 | Aol Llc | Electronic message forwarding |
US7130403B2 (en) | 2002-12-11 | 2006-10-31 | Siemens Communications, Inc. | System and method for enhanced multimedia conference collaboration |
US20040119814A1 (en) | 2002-12-20 | 2004-06-24 | Clisham Allister B. | Video conferencing system and method |
US7187932B1 (en) * | 2003-01-16 | 2007-03-06 | Cingular Wireless Ii, Llc | Autopopulation of address book entries |
US7068768B2 (en) | 2003-01-29 | 2006-06-27 | America Online, Inc. | Method for populating a caller's information to a host-based address book |
US8538386B2 (en) | 2004-03-01 | 2013-09-17 | Blackberry Limited | Communications system providing text-to-speech message conversion features using audio filter parameters and related methods |
US7139782B2 (en) | 2004-09-21 | 2006-11-21 | Hitachi, Ltd. | Method of and system for testing remote storage |
US7245929B2 (en) | 2005-07-05 | 2007-07-17 | Yahoo! Inc. | Enabling text messaging between a member and non-member of a community based on a common short code |
-
2003
- 2003-11-24 US US10/720,870 patent/US8488761B2/en not_active Expired - Fee Related
- 2003-11-25 WO PCT/US2003/037874 patent/WO2004049136A2/en active Application Filing
- 2003-11-25 EP EP03787186A patent/EP1568198A4/en not_active Withdrawn
- 2003-11-25 CA CA2507492A patent/CA2507492C/en not_active Expired - Fee Related
- 2003-11-25 AU AU2003295971A patent/AU2003295971A1/en not_active Abandoned
- 2003-11-25 JP JP2004555780A patent/JP4588454B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
WO2004049136A2 (en) | 2004-06-10 |
WO2004049136A3 (en) | 2004-07-01 |
AU2003295971A1 (en) | 2004-06-18 |
CA2507492A1 (en) | 2004-06-10 |
EP1568198A2 (en) | 2005-08-31 |
AU2003295971A8 (en) | 2004-06-18 |
US8488761B2 (en) | 2013-07-16 |
US20050117729A1 (en) | 2005-06-02 |
JP2006507777A (en) | 2006-03-02 |
EP1568198A4 (en) | 2006-10-11 |
JP4588454B2 (en) | 2010-12-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2507492C (en) | Methods and systems for a call log | |
CA2507091C (en) | Methods and systems for contact management | |
US7836147B2 (en) | Method and apparatus for address book contact sharing | |
US8503639B2 (en) | Method and apparatus for adaptive message and call notification | |
US8472606B2 (en) | Methods and systems for directory information lookup | |
US8761355B2 (en) | Methods and systems for notification of call to device | |
US8798251B2 (en) | Methods and systems for computer enhanced conference calling | |
CA2507097C (en) | Methods and systems for notification of call to device | |
WO2004049677A2 (en) | Methods and systems for computer enhanced conference calling | |
CA2507085A1 (en) | Method and apparatus for adaptive message notification | |
JP2006507776A (en) | Method and system for contact management | |
WO2004049679A1 (en) | Method and systems for single number text messaging |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20151125 |