US20060026232A1 - Methods, systems, and products for creating message logs - Google Patents
Methods, systems, and products for creating message logs Download PDFInfo
- Publication number
- US20060026232A1 US20060026232A1 US11/236,907 US23690705A US2006026232A1 US 20060026232 A1 US20060026232 A1 US 20060026232A1 US 23690705 A US23690705 A US 23690705A US 2006026232 A1 US2006026232 A1 US 2006026232A1
- Authority
- US
- United States
- Prior art keywords
- user
- information
- communications
- communication
- message 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/234—Monitoring or handling of messages for tracking messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- 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
- 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/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
-
- 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/5307—Centralised arrangements for recording incoming messages, i.e. mailbox systems for recording messages comprising any combination of audio and non-audio components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2066—Call type detection of indication, e.g. voice or fax, mobile of fixed, PSTN or IP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/45—Aspects of automatic or semi-automatic exchanges related to voicemail messaging
- H04M2203/4509—Unified messaging with single point of access to voicemail and other mail or messaging systems
-
- 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
- H04M2242/00—Special services or facilities
- H04M2242/22—Automatic class or number identification arrangements
-
- 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/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42042—Notifying the called party of information on the calling party
-
- 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/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42093—Notifying the calling party of information on the called or connected party
-
- 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/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42102—Making use of the called party identifier
- H04M3/4211—Making use of the called party identifier where the identifier is used to access a profile
-
- 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
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/0024—Services and arrangements where telephone services are combined with data services
- H04M7/0042—Services and arrangements where telephone services are combined with data services where the data service is a text-based messaging service
- H04M7/0045—Services and arrangements where telephone services are combined with data services where the data service is a text-based messaging service where the text-based messaging service is an instant messaging service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/0024—Services and arrangements where telephone services are combined with data services
- H04M7/0054—Services and arrangements where telephone services are combined with data services where the data service is an electronic mail service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1225—Details of core network interconnection arrangements
- H04M7/1235—Details of core network interconnection arrangements where one of the core networks is a wireless network
Definitions
- the inventions relate to communications, and particularly, to the management of information about a user's communications.
- a person may have a number of communication devices at his or her disposal.
- the person may communicate using, among other things, a telephone, a wireless unit, a pager, a facsimile (fax) machine, or a personal digital assistant (PDA).
- PDA personal digital assistant
- the person also may use a computer or other device to provide information and to communicate using a web site, electronic mail (e-mail) messages, instant messages, or chat room messages. Accordingly, a person may send and receive a lot of communications using a variety of devices.
- a person with a variety of communication devices has to individually monitor each of his or her devices, thereby expending significant time and effort. If the person cannot handle a communication in a “live” fashion on any particular device, a message, note, or other record may be made of the attempted communication. Thus, the monitoring of the communication devices also may require monitoring of the devices for messages for the user. Generally, a person uses his or her communication devices in an ad hoc manner, and so, the monitoring of messages across the variety of devices also may be done in an ad hoc manner. Thus, there is a need for a better way to keep track of all of the communications of a person.
- an attempt at communication with a person may be recorded or otherwise noted in a message that may be later accessed by the person.
- a caller may leave the person a message on his or her voicemail system.
- a communication such as an e-mail message or a fax may leave its own record of communication.
- certain types of communications and communication devices typically do not leave their own records or allow for a message to be left for the person.
- these “non-recorded” communications are difficult to find out about, to track, or to review.
- a person makes a telephone call to a friend, but the friend does not answer and does not have any answering system. The person generally does not have a way to keep track of the call attempts the person has made.
- assume the person has enabled an instant messaging service while working on his or her computer. Typically, there is no record made of an instant message that is sent or received.
- non-record communications As yet another example, assume the person engages in a chat room discussion by using his or her computer. Generally, the person's participation in the chat room discussion is not noted or otherwise recorded.
- the communications and communication devices that do not leave their own records or allow for a record, note, or message are referred to herein as “non-record” communications or “non-record” communication devices.
- a person may be negotiating a deal involving multiple parties. Each party participates in the negotiations by using his or her own preferred communication means and devices. The person may have a log of e-mails, an answering machine full of voice mail messages, and a stack of faxes relating to the negotiations. But one of the parties may be participating in the negotiations by using some type of communications device or mechanism that does not allow for records or logs of that type of communications. So, the person's attempts at communication with the “non-record” party may not be noted by the non-record party. The non-record party may be suspicious that such attempts at communication were ever made.
- an e-mail message may refer to a specific topic, and it would be to the person's advantage to review other data related to the specific topic. Moreover, it would be advantageous to carry out such a review as quickly and efficiently as possible.
- a message may refer to a work document, an electronic publication, or a web page which may be shared between the person and his or her communication partners. Using conventional methods, the person must individually identify, search and retrieve the work document. The activities carried out to obtain the work document may be time consuming, inefficient, and otherwise frustrating. Thus, there is a need to provide a person with information related to a message in an efficient and quick manner.
- a person generally has a lot of different types of communication devices.
- the person may prefer to receive certain types of communications through a certain type of device or at a certain time.
- the person may prefer not to receive communications of a certain type or during a certain time.
- a client may prefer to receive communications via his or her voicemail box. If the person sends an e-mail message to the client, there may arise a delay in communication. In addition, by sending the e-mail rather than leaving a voicemail message, the person may convey the impression that the person is insensitive to the client's preferences. Neither result is desirable. Thus, there is a need for a way to manage the communications of a person so that communications made to communicating partners are made automatically in accordance with the preferences of the respective communicating partner.
- the inventions described herein provide information about a user's communications.
- the inventions allow a user to obtain information correlated or corresponding to a communication.
- the inventions allow a user to take action based on the information about a communication or the correlated or corresponding information.
- An embodiment of the inventions includes a system for making information correlated to a communication automatically available to a user.
- the system includes a telecommunications (telecom) manager connected to a telecommunications network; a gateway connected to a data network; and a communications manager that may communicate with the telecom manager and the gateway.
- the communications manager may store information about a user's communication preferences. The preferences may include a preference for presentation of information correlated or corresponding to a communication.
- the communications manager receives information about a communication relating to a user from the telecom manager or from the gateway.
- the communication may include an instant message, a chat room message, or an attempt to reach the user by a caller using a wireline or wireless device.
- the communications manager uses the information to create an entry corresponding to the communication and to include the entry in a log.
- the log is displayed, and the user may select an entry from the log.
- the communications manager may check the user's preferences.
- the preferences may include a preference for the presentation of the information correlated to a communication.
- the communications manager obtains and presents the correlated information.
- the communications manager may obtain the information correlated to the communication from its own resources, from the telecom manager, or from the gateway.
- the communications manager may include a user's preferences.
- the preferences may include a request for display of information corresponding to a communication when the communication is initiated by the user.
- the initiated communication may include an instant message, a chat room message, or an attempt to reach the user by a caller using a wireline or wireless device.
- the communications manager may act according to the user's preference by noting the initiation of a communication by the user.
- the communications manager then may check the user's preferences for inclusion of the request for the display of information corresponding to the initiated communication. If the communications manager finds the request, then the communications manager may use communication information regarding the initiated communication to obtain and present the corresponding information. In addition, the communications manager may make the communication information regarding the initiated communication available in a log.
- Another embodiment of the inventions includes a method for making information correlated to a communication automatically available to a user.
- the communication may be an instant message, a chat room message, or an attempt at completing a wireline or wireless call to the user.
- the method stores a user's preference for presentation of information correlated to a communication.
- the method uses the information to create an entry corresponding to the communication, includes the entry in a message log, and displays the log.
- the method may receive an indication of selection of an entry from the message log.
- the method may check the preferences for the preference for the presentation of the information correlated to the communication.
- the method obtains and presents the correlated information.
- An initiated communication may include an instant message, a chat room message, or an attempt at completing a wireline or wireless call to the user.
- the method may act according to the preference when the method notes the initiation of the communication by the user.
- the method checks the user's preferences for the request for the display of the information corresponding to the initiated communication. Based on finding the request, the method may use the communication information regarding the initiated communication to obtain and present the corresponding information. In addition, the method may make the communication information regarding the initiated communication available in a message log.
- Yet another embodiment of the inventions includes a method for keeping track of communications of a user.
- the method may receive information regarding communications of the user from a gateway connected to a data network.
- the communications may include an instant message or chat room message to or from the user.
- the method stores the information in a message log by including an entry for each communication of the user, and particularly by including an entry for each instant message or chat room message of the user.
- the exemplary method also may receive information from a telecommunications manager connected to a telecommunications network regarding an attempt to reach the user via wireline or wireless call.
- the method stores the information regarding the attempt in an entry in the message log.
- the method may receive information regarding an attempt by the user to make a wireline or wireless call.
- the method stores information regarding the attempt in an entry in the message log.
- FIG. 1 is a block diagram of an exemplary environment for operation of the inventions described herein.
- FIG. 2 is an exemplary message log as may be used with the present inventions.
- FIG. 3 is a block diagram of exemplary of another exemplary operating environment for the inventions described herein.
- FIG. 4 is a table illustrating a user's profile information as may be used with the present inventions.
- FIG. 5 includes tables illustrating contact information as may be used with the present inventions.
- FIG. 6 illustrates a communications environment as may be used with the present inventions
- FIG. 7 is exemplary flow diagram of the CIR manager when a user receives a communication message or when a user selects a message log.
- FIG. 8 is an exemplary flow diagram of the CIR manager when a user sends a communication message to his or her communication partner.
- FIG. 9 is an exemplary flow diagram for performing a task requested by user in FIG. 5 or FIG. 6 , such as a request for document transmission.
- the inventions provide information about a user's communications, provide a user with information correlated or corresponding to a communication, and/or allow a user to take action based on the information about a communication or the correlated or corresponding information.
- CIR manager In a related patent application, a communications and information resource (CIR) manager is described. See U.S. patent application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager,” filed Sep. 28, 2001, which is incorporated herein by this reference.
- the CIR manager may be used to implement the inventions described in this application. Prior to describing the present inventions, some background about the CIR manager is provided.
- a CIR manager may function as a “super” manager with respect to the communications devices, services, and systems of a user.
- the CIR manager may be used to centralize communications activities and information such that the user does not have to (but may) use multiple communications devices.
- the CIR manager may be used to keep a log of all types of communications related to the user—whatever the device, whatever the service, whatever the network.
- An advantage of the CIR manager is the user does not have to check or use each type of device for its own type of messages.
- the CIR manager may obtain information from resources including third party resources so as to facilitate communications and information gathering activities of the user.
- the user is provided with a centralized, efficient, and user-friendly way to handle communications activities including ways to receive, view, listen to, play, respond to, store, log, monitor, delete, copy, forward, obtain, create, and to take other actions.
- the CIR manager provides the user with personalized management of communications and information resources.
- the CIR manager may provide the user with one or more of the following features and advantages:
- FIG. 1 Exemplary Operating Environment of a CIR Manager— FIG. 1
- CIR manager 10 may interact with a variety of systems, networks, and elements that may be directly connected to the CIR manager 10 , may be hosted by the same host(s) as the CIR manager 10 , may be functionally connected to the CIR manager 10 , and/or may be accessible to the CIR manager 10 either directly and/or through other systems, networks, and/or elements.
- FIG. 1 illustrates an exemplary operating environment of a CIR manager 10 implemented on a personal computer (PC) 24 .
- PC personal computer
- FIG. 1 illustrates an exemplary operating environment of a CIR manager 10 implemented on a personal computer (PC) 24 .
- PC personal computer
- the operating environment of FIG. 1 illustrates the CIR manager 10 may communicate through the PC 24 with another computer(s) 25 connected or otherwise networked with the PC 24 .
- the CIR manager 10 also may communicate through the Internet 26 with the following:
- the CIR manager 10 may have access to other computers 25 through local area networks (LANs), wide area networks (WANs), direct connections and other dial-up networks.
- LANs local area networks
- WANs wide area networks
- direct connections and other dial-up networks.
- the CIR manager 10 also may have access through the PC 24 to a global communications network such as the Internet 26 , and through the Internet 26 to other units, networks, and systems. Particularly, the CIR manager 10 may communicate with a gateway 28 connected to or operating on the Internet.
- the gateway 28 may be a service platform, or other device.
- the gateway 28 may be provided by the service provider of the CIR manager 10 , and may serve the CIR manager 10 .
- Communications activities to and from the CIR manager 10 on the PC 24 may be directed to the gateway 28 and/or may pass through the gateway 28 to other systems, networks, and/or elements. In passing through the gateway 28 , the communications activities may be facilitated by the gateway 28 .
- the CIR manager 10 may send a communication to the gateway 28 for routing to the appropriate element to handle such set-up activities.
- Administrative Center 36 may handle administrative matters including set-up activities for the service provider.
- the gateway 28 delivers or otherwise routes the communication to the Administrative Center 36 for the set-up activity.
- the Administrative Center 36 may respond to the gateway 28 with questions, information, and instructions for the CIR manager 10 .
- the gateway 28 may facilitate communications activities of the CIR manager 10 is to function as a router or director of communications and messages.
- the CIR manager 10 may forward a request for data to the gateway 28 .
- the gateway 28 may determine the data may be obtained from the information resource 30 .
- the gateway 28 then forwards the request for data or the appropriate message to the information resource 30 .
- the information resource 30 may respond to the CIR manager 10 or to the gateway 28 , which then communicates with the CIR manager 10 .
- the gateway 28 may facilitate communications activities between the CIR manager 10 and the PSTN 38 , and other elements reached through the PSTN 38 such as the telecom manager 40 , and the communications devices including the wireline unit 42 , the wireless unit 44 , the pager 46 , and the fax device 48 .
- the telecom manager 40 provides general functions and features related to communications of a user.
- the telecom manager 40 may be implemented in a computer, on a service platform, in a network node, or other device.
- the telecom manager 40 may include connections to devices and networks through integrated services digital network (ISDN) lines and signaling system 7 (SS7) data links.
- the telecom manager 40 may be capable of functions similar to those of a service switching point (SSP) or service node (SN) of an Advanced Intelligent Network (AIN).
- the telecom manager 40 may have the following capabilities: signaling, call set-up, routing, and access to databases.
- FIG. 2 Message Logs Function and a Message Log— FIG. 2
- the CIR manager 10 includes a Message Logs function, which as its name implies, enables the CIR manager to keep one or more message logs of the user's communications.
- a message log also may be referred to as a log.
- the exemplary Message Logs function of the CIR manager 10 relates to the organization, preferences, summary, and display of information pertaining to communications activities of a user.
- the Message Logs function may enable one or more summaries of new, reviewed, sent, or other communications.
- the Message Logs function may enable one or more call activity logs that keep track of calls or communications activities by the user.
- the Message Logs function allows the user to keep track of all types of communications activity including conventional messages such as voice mails, e-mails, faxes, and pages. Plus, the Message Logs function allows the user to keep track of other types of messages such as instant messages, conversations in a chat room, and attempts at contact made by others.
- FIG. 2 illustrates an exemplary message log 50 such as may be provided by the CIR manager 10 and used in connection with the inventions described herein.
- Message log 50 includes entries relating to the exemplary user's communications using the CIR manager 10 .
- message log 50 includes eight entries 52 , 54 , 56 , 58 , 60 , 62 , 64 , and 66 .
- Each entry includes data 68 , and in this example, each entry includes four types of data: “from” 70 ; “type” 72 ; “subject” 74 ; and “date” 76 .
- the from data 70 refers to the source or origin of the communication.
- the type data 72 refers to the type or kind of communication.
- the subject data 74 refers to the content, the substance, or other feature of the communication.
- the date data 76 refers to the date of receipt (or transmittal if from the user) of the communication.
- the user may obtain available additional information about the communications entered in the message log 50 through use of the inventions described herein.
- Entry 54 relates to a voice message (such as a voicemail message) from Bill Jones received on May 20, 1999 from telephone number: (703) 345-6789.
- the user may obtain additional information about the voicemail message from Bill Jones.
- FIG. 3 Another Exemplary Operating Environment of a CIR Manager— FIG. 3
- FIG. 3 illustrates another exemplary operating environment for the present inventions.
- a user 102 has a plurality of communication devices and media available for communications, commonly designated as 104 .
- the communication devices and media may include: a voicemail system as designated by the user's voice box 104 a ; an e-mail system as designated by the user's e-mail box 104 b ; an instant messaging system as designated by the user's instant message box 104 c ; a system for participating in a chat room as designated by the user's chat room box 104 d ; a web site or web page as designated by web 104 e ; a fax system as designated by fax 104 f ; a telephone (wireline device) 104 g ; (h) a wireless unit 104 h ; and a pager 104 i .
- the user 102 has a diverse means of communicating with his or her communication partners.
- the present inventions may be implemented through the use of a CIR manager 106 .
- the CIR manager 106 is hosted on computer or in a computing environment, such as a personal computer (PC) 108 .
- the CIR manager can be hosted on any computer device, wired and wireless.
- the connection 110 between the PC 108 hosting the CIR manager 106 and the Internet 112 is a persistent connection, preferably using broadband technology. More particularly, the connection 110 provides means to communicate with a gateway server (“gateway”) 114 .
- gateway server gateway server
- any wired or wireless connection can be used for the connection 110 .
- the CIR manager 106 provides a unified, one-stop view of the user's communications. For example, when Client A of the user 102 leaves a voicemail message for the user, the CIR manager 106 learns of the event, creates an entry for the event in a message log, and provides information regarding the voicemail message to the user 102 . If the user has expressed a preference to be provided with additional information, the CIR manager 106 may provide additional information regarding the voicemail message to the user.
- the CIR manager 106 learns of the event, creates an entry for the event in a message log, and provides information related to the chat room discussion. If the user has expressed a preference for additional information, the CIR manager 106 may provide additional information regarding the chat room message.
- the user may add information or otherwise characterize the entry for the chat room discussion. For example, assume a user finishes a chat room discussion. The CIR manager 106 creates an entry for the discussion. In the course of creation of the entry, the CIR manager 106 may query the user for input to be included in the entry regarding the chat room discussion. By this feature, the CIR manager 106 allows for the creation of entries that are useful to the user.
- the CIR manager 106 learns of the event, may provide information about the event, and creates an entry for the event in a message log. If the user has expressed a preference for additional information, the CIR manager 106 may provide additional information regarding the instant information to the user. As with the chat room discussion, the CIR manager 106 may give the user an opportunity to provide input such as “subject” or other information to be included in the entry for the instant message. Assume the user has included “adoption” in the subject field in the data of an entry relating to an instant message.
- the CIR manager 106 may categorize the entry for the instant message as related to other entries and messages including “adoption” in the subject field. Based on this categorization, the user 102 can retrieve the information relating to the instant communication having adoption in the subject field as well as relating to other communications having adoption in the subject field.
- the CIR manager 106 can provide a unified, one-stop view of the user's communications because the CIR manager 106 may be set up to communicate with the application program interface (“API”) for each of the providers and/or programs that enable corresponding communication devices and activities.
- API application program interface
- the ability of the CIR manager 106 to communicate with APIs and applications allows the CIR manager 106 to carry out a user's preferences with respect to the presentation of information relating to the user's communications.
- the CIR manager 106 may communicate with the plurality of the API's using any of conventional methods such as polling, event driven interrupts, and/or a token ring.
- the CIR manager 106 as hosted by PC 108 may communicate with a telecommunications manager 132 in the PSTN 130 by a wired or wireless connection.
- the CIR manager 106 learns of the communication events, generally creates entries corresponding to the events, and can categorize the communications, so that the user 102 can have a complete view of his or her communication activities.
- the CIR manager 106 may tag the data or part(s) of the data in an entry.
- the CIR manager 106 may use the tag to retrieve the data or part(s) of the data in an entry, or for other reasons.
- the tag may be a numerical tag or other tag or indicator.
- the CIR manager 106 may tag the data or part(s) of the data based on preferences of the user indicated at time of system set-up or at other times.
- a telecom manager 132 in the PSTN 130 notifies the CIR manager 106 of the call.
- the CIR manager 106 creates an entry for the telephone call in the message log even if the call goes unanswered.
- the CIR manager 106 may tag data (including part(s) of the data) in the entry the CIR manager 106 creates for the unanswered call.
- the CIR manager 106 may tag the data for several reasons. For example, the CIR manager 106 may tag the originating telephone number in the entry for the unanswered call so as to be able to obtain additional information about the unanswered call.
- the CIR manager 106 may use the tagged data (the originating telephone number) to obtain the additional information. Using the tagged data, the CIR manager 106 may check its own resources to determine whether it has additional information on the originating telephone number. Using the tagged data, the CIR manager 106 may contact the telecom manager 132 for additional information such as a reverse white pages listing corresponding to the originating telephone number.
- the CIR manager 106 may use the tagged data to retrieve the substance of the communication.
- the tagged data may provide information to the CIR manager 106 with respect to the path or route to take to retrieve the substance of the communication.
- the tagged data may provide the CIR manager 106 with information on the application(s) to call to retrieve the substance of the communication.
- the tagged data is not necessarily data included in the entry corresponding to the communication in the message log.
- the CIR manager 106 may receive information from the gateway 114 on a voicemail message for the user.
- the CIR manager 106 may tag data so as to obtain information on the retrieval through the gateway 114 of the substance of the voicemail message from a voicemail system.
- the user has a record of attempts made to contact him or her via a call to the user's telephone number.
- the entry for the unanswered call may be marked as an “unanswered call”.
- the CIR manager 106 may not be able to fill in all of the fields of the data in the entry. For example, the CIR manager 106 may be unable to fill in the subject field for an unanswered call. But the CIR manager 106 may substitute some other information (like “unanswered call”) in the subject field of the entry.
- the user may add any missing information or substitute other information in the entry.
- the telecom manager 132 notifies the CIR manager 106 .
- the CIR manager 106 creates an entry for the fax in the message log.
- the CIR manager 106 may tag data or part(s) of data in the entry the CIR manager 106 creates for the fax.
- the tagged data may be used by the CIR manager 106 to obtain additional information correlated or corresponding to the fax, or for other reasons.
- the user may be able to access the fax by activating the entry for the fax in the message log.
- the CIR manager 106 may query the user for input on desired actions. The user may indicate a desire to review the fax.
- the CIR manager 106 may use tagged data in the entry corresponding to the fax or other tagged data related to the fax to obtain the substance of the fax. The CIR manager 106 then may display the fax to the user on the computer screen or otherwise take actions to present the fax to the user.
- the telecom manager 132 in the PSTN 130 may communicate with the gateway 114 in the Internet 112 .
- the techniques and methods of communications between elements in the PSTN 130 and the Internet 112 are well known to those skilled in the art.
- the CIR manager 106 includes profile information 202 for the user 102 .
- profile information 202 for the user 102 includes, among other things, a list of the communication devices, such as a telephone, a cellular telephone, or a pager of the user 102 .
- the profile information file 202 also includes information regarding the user 102 's preferred methods of communication.
- the exemplary profile information 202 shows the preferences may include: (a) the time of the communication; (b) the identity of the communication partner(s); and (c) the subject matter of the communication. Of course, other preferences may be included or substituted.
- the profile information 202 also illustrates the user may set his or her preferences regarding the presentation of information in addition to, correlated to, or corresponding to a communication.
- additional, correlated, or corresponding information may include, inter alia, information to related communications, identifying information regarding communication originators or recipients, and information on subject matter mentioned in the communication or in information about the communication.
- Additional, correlated, or corresponding information also may include other entries, or communications sharing some feature in common with the entry (or related communication) for which the correlated information is sought.
- additional, correlated, or corresponding information may relate to documents and the like that may be referenced in a communication, or in an entry relating to a communication in a message log.
- an entry for an instant message may include through user input reference to a document such as “work report” in the subject field of the entry in the message log.
- the data relating to the “work report” in the subject field of the entry may be tagged so the CIR manager 106 may use the tagged data to obtain the document, or to obtain instructions on how to obtain the document.
- the user simply may activate the subject field of “work report” and obtain correlated information including access to or a copy of the referenced work report.
- the additional, correlated or corresponding information need not directly pertain to the entry used in finding the information. There may be an indirect or two or more step relationship between the entry and the additional, correlated, or corresponding information.
- the subject feature or subject data of an entry 80 a may include the telephone number: (704) 345-6789.
- the number implies the associated telephone is located in the State of North Carolina.
- an internet link to the Tourism Board of North Carolina may constitute correlated information to the entry including the telephone number (704) 345-6789.
- the preference for correlated information is set to “all”.
- the “all” setting indicates the user's preference for correlated information on all communications to/from whatever devices. For example, assume the user receives an e-mail, a page, and a fax. Information on each communication is entered into the message log. As part of creating each entry for the message log, the CIR manager 106 may tag data or part(s) of data in each entry so that correlated information may be retrieved respectively for each entry. The preference for correlated information may be set to include less than all devices.
- a user may indicate preference for correlated information based on a factor other than the type of device originating a communication to or from the user. For example, the user may choose one or more fields of an entry in the message log as holding the data to be tagged for obtaining correlated information or otherwise. To further this example, the user may indicate a preference for obtaining correlated information on each originator or source of a communication (the “from” field in an entry).
- the user may mix and match the various factors of a communication so as to indicate the user's preferences for correlated information. For example, the user may indicate a preference for correlated information on all communications to/from a pager and on the data in the subject fields of all communications.
- the profile information 202 relating to a user can be used, for example, to populate certain fields in a communication so the user 102 need not enter repeated information, such as for example, the date and time, the subject matter, and/or canned responses.
- the CIR manager 106 also has contact information 302 for the user 102 .
- Exemplary contact information 302 lists communication partners of the user 102 , collectively designated as 342 .
- each communication partner listed on the contact information 302 is associated with additional information that may be presented to the user on a “contact card”, collectively designated as 352 .
- a contact card 352 may contain, among other things, the types of communication devices used by the communication partner corresponding to the contact card.
- the contact card 352 may also include the preferred methods of communicating for the corresponding communication partner.
- the preference information in the contact card 352 can be time, subject matter, and other factor sensitive.
- the CIR manager 106 may include profile information for the user 102 as well as for each communication partner listed on the contact information 302 .
- the CIR manager 106 can either automatically update the contact information or otherwise facilitate the user 102 's entry of information regarding his or her communication partner(s).
- the CIR manager 106 may receive information about a communication to the user from Person A. The CIR manager 106 may be set so the CIR manager 106 checks the user's contact information to determine whether information on Person A is present in the contact information. If there is no information on Person A, the CIR manager 106 may add Person A's information to the contact information, if that is the preference set up (typically at service set-up) by the user. Alternatively, the CIR manager 106 may query the user as to whether Person A's information should be added.
- the CIR manager 106 may be set-up based on preferences of the user to compare the information received with Person A's communication to Person A's information in the contact information. If the comparison yields differences, the CIR manager 106 may automatically update Person A's contact information or may query the user whether to update Person A's contact information. To further this example, the CIR manager 106 may automatically enter new information regarding Person A, if he or she communicates with the user 102 via a previously unused communication device. As another example, if a new contact, Person ZZ communicates with the user 102 , the CIR manager 106 may query the user 102 to determine if the user wishes to enter the information regarding Person ZZ in the contact information 302 .
- the CIR manager 106 may enter information into a user's contact information 302 when a person or entity not included in the user's contact information makes or receives a communication to or from the user.
- the CIR manager 106 may automatically enter the new information or first query the user with respect to the entry of the information, per the preferences of the user. For example, assume a person sends the user an e-mail. The CIR manager 106 creates an entry for the e-mail in the message log. If the user has indicated a preference for automatic update of contact information on new communicating partners, then the CIR manager 106 may use the information received in association with the e-mail to create an entry in the contact information for the new communicating partner.
- the CIR manager 106 may be unable to fill in all of the information in the contact information regarding the new communicating partner.
- the CIR manager 106 may query the user for the missing information, or the CIR manager 106 may contact the new communicating partner for the missing information.
- the new communicating partner communicated by e-mail.
- the CIR manager 106 may send a reply e-mail requesting the missing information.
- the CIR manager 404 provides an interface for the user's communications regardless of whether the messages are sent or received by the user 402 and regardless of the type of the communications device.
- the CIR manager 404 generally provides the interface for the user's communications by reference information on the applications, programs, databases, sources, networks, and other resources that are involved with the user's communications. This information may be registered with the CIR manager 404 .
- the CIR manager is populated with the appropriate instructions on where to look for information and how to get the information.
- the CIR manager is provided with the appropriate instructions so the CIR manager may communicate with the telecom manager in the telecommunications network and with the gateway in the data network.
- the instructions provided to the CIR manager may be updated or changed as needed so as to accommodate a user's changing communication needs.
- the CIR manager may be provided information and instructions relating to the retrieval of correlated information.
- a user's profile information 406 may indicate a preference for the retrieval of correlated information under certain conditions.
- Specific data in an entry relating to a communication may be tagged so as to be used to retrieve the information.
- the tagged data may include numerical tags that include or reference instructions.
- the instructions may be included in the CIR manager so the CIR manager may access the instructions to obtain the correlated information.
- the CIR manager may include instructions on obtaining correlated information on the data in the subject field of an entry in the message log.
- the instructions may include a direction to the CIR manager to make a check of the CIR manager's resources, to query the gateway in the data network, to poll a particular application from a networked computer, or to take other action.
- the CIR manager carries out the instructions so as to retrieve the correlated information.
- the CIR manager may be updated or changed as needed so as to accommodate a user's changing communication needs.
- the CIR manager 404 has profile information 406 for the user 402 , and has contact information (client profile) collectively designated as 420 , for each of the user's clients or communicating partners, who are collectively designated as 410 .
- client profile For example, the client profile 420 a lists a cellular telephone and a facsimile machine for Client A 410 a .
- the profile information 420 b lists a pager and a telephone for Client B 410 b.
- a exemplary embodiment of the CIR manager 404 tags, associates, categorizes and identifies each message communicated to and from the user 402 per the preferences of the user or some default.
- the CIR manager 404 creates and/or facilitates the creation of an entry for a communication in message log 430 .
- the message log 420 includes entries, collectively identified as 431 .
- Each entry includes data that identifies a communication of the user 402 using fields (also referred to as identifiers or features).
- An entry 431 in message log 430 illustrates three fields of the data: (a) who element 432 ; (b) what element 434 ; and (c) when element 436 .
- the user may set-up the CIR manager 404 to include additional, fewer, or other identifiers in an entry. Using any identifiers, a message can be retrieved or reviewed by the user 402 . Typically, the data in the chosen identifier is tagged so the CIR manager 106 is provided with information or may obtain instructions on how and from where to retrieve the substance of the message. The identifiers in an entry relating to a communication in the message log also may be used to retrieve other information related to the communication.
- the fields of an entry in the message log may be used to obtain information correlating to the communication.
- correlated information also may include “corresponding information” or “additional information”. Further details on obtaining the correlated or corresponding information are found in the previously referenced and related U.S. patent application Ser. No. ______, entitled “Methods and Systems for Providing Information Correlated to a Communication”, filed concurrently with this application, and which is incorporated herein by reference.
- the CIR manager 404 uses data from an entry (such as data in a field, identifier, or feature) to retrieve information correlated to the communication.
- the data may be tagged such as with a numerical tag so as to provide the CIR manager 404 with instructions or information on the retrieval of the corresponding or correlated information.
- the CIR manager 10 may check its own resources, and/or may check resources that may be reached through the gateway and the Internet, or through the telecom manager 40 and the PSTN 38 , and/or in other ways.
- the CIR manager 404 creates an entry for each of the instant messages.
- the entries are included in the message log 430 .
- the CIR manager 404 may create an entry for an instant message automatically, if that is the user's preference, or may ask the user whether an entry should be created.
- the CIR manager 404 may ask the user 402 to enter one or more fields of information.
- the user receives an instant message.
- the instant message is sent to the user over the Internet through the gateway and to the CIR manager 404 prior to appearing on the user's computer screen.
- the CIR manager 404 receives or otherwise accesses information associated with and/or including the instant message.
- the CIR manager 404 uses the information to create an entry in the message log.
- the CIR manager 404 accesses information on the originator of the instant message and places the originator information in the who field 432 (also referred to as identifier or feature of the data). For the what field 434 of the entry, the CIR manager 404 may simply include “instant message” or the CIR manager select information associated with the instant message and include that information in the what field 434 . With respect to the when field 436 , the CIR manager 404 may obtain that information from the instant message, or the CIR manager 404 may use its own internal clock to include a time in the when field 436 of the entry corresponding to the instant message in the message log. The CIR manager 404 may query the user for information to be added, or changed with respect to any entry the CIR manager creates. Depending on the preferences of the user, the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication.
- the processes for creating entries in a message log for participation in a chat room, and for attempted calls (to or from the user)(wireless or wireline) are generally the same as described in the previous paragraphs for creating the entry for the instant message.
- the processes for creating entries in a message log for attempted calls (to or from the user)(wireless or wireline) are also generally the same as described in the previous paragraphs for creating the entry for the instant message except that the CIR manager 404 may receive information or access information about the attempted calls from the telecom manager, which may receive the information from the PSTN or other telecommunications network.
- the CIR manager 404 may receive or access information about the attempted calls from the gateway, which may receive the information from the Internet or other data network.
- the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication.
- the CIR manager 404 creates an entry in the message log for the telephone conversation.
- the CIR manager 404 may query the user for information to include as data in the pertinent entry in the message log.
- the CIR manager 404 may offer a menu with a list of options, a notepad or other device so the user 402 may enter information for the entry.
- the user may want to note issues discussed in the telephone conversation.
- the entry of information relating to a telephone conversation can also be automatic using, for example, digital signal processing techniques for audio signals.
- the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication.
- the CIR manager 404 can build data relationships for communications of the user 402 regardless of the user's communication methods.
- the data relationships can include, among other things: (a) relevant parties to a communication; (b) relevant information exchanged between the parties; and (c) relevant documents retrievable from a local storage device or a remote server via a network, such as the Internet.
- an exemplary flow diagram for the CIR manager 404 is presented for the case in which the user 402 receives a communication from Client A, or selects an entry from a message log where the entry corresponds to a communication.
- the communication may be a call (wireline or wireless), a fax, a page, a voicemail message, an e-mail message, an instant message, a chat room message, or even an attempt to reach the user by a caller using a wireline or wireless device.
- the user 402 receives, for example, a communication from Client A.
- the user 402 identifies or selects an entry from the message log. The entry corresponds to a particular message.
- the CIR manager 404 identifies information correlated, respectively depending on the previous action, to the communication from Client A or to the selected entry.
- the correlated information may include the communication itself, related messages, information and documents, including work-files, web pages, and electronic publications.
- the CIR manager 404 may identify and/or obtain the correlated information from its own resources, from the gateway in a data network, from the telecom manager in a telecom network, or otherwise.
- the CIR manager 404 may check whether the user desires to be presented with the correlated information.
- the CIR manager 404 may query the user with presentation options.
- the user's preference may be included in the user's profile information accessible by the CIR manager 404 .
- the CIR manager 404 may check for a preference such as a preference for the presentation of the information correlated to the communication. The CIR manager 404 then may act according to the preference.
- the CIR manager 404 may obtain the “identity” of the communicating party.
- the identity may be obtained from or using information associated with the communication such as information related to the originating or sending party.
- the CIR manager 404 may use the identity to identify and obtain related messages and documents.
- the CIR manager 404 also may use the identity to identify and obtain previous communications relating to Client A.
- the previous communications may include communications from, to, related to, or mentioning Client A.
- Another example is presented with respect to action 502 b when the user selects an entry from a message log.
- the entry corresponds to a particular communication.
- the CIR manager 404 may automatically identify messages and documents correlated to the communication corresponding to the entry selected by the user.
- the CIR manager 404 presents the correlated information to the user 402 , using for example, icons and/or displays for the messages and documents.
- the user 402 may request to view messages and/or documents presented at action 506 by, for example, selecting the appropriate icon(s).
- the CIR manager 404 performs the user's request received at action 508 by, for example, launching a browser to display a web page, retrieving a document, or transmitting a document.
- the user 402 may also request a search for a particular document or additional information that has not been presented to the user at action 506 . In such a case, the CIR manager 404 searches for messages and/or documents related to the search request and presents the additional information to the user 402 at action 510 .
- the CIR manager 404 can present to the user 402 all previous communications between the user 402 and Client A, documents identified by the CIR manager 404 as being related to Client A and the subject matter of previous communications, and any additional information the user 402 may request.
- the CIR manager 404 can facilitate the user's 402 retrieval of information related to Client Z.
- the CIR manager 404 includes information that Client Z has a web site, and thus can launch a web browser to display the web page of Client Z.
- the CIR manager 404 learns that the subject matter of Client B's message communicated on Apr. 15, 2001 is related to the subject matter of Client Z's message communicated on Aug. 10, 2001, and thus the CIR manager 404 may present message (or the entry in a message log) for Client B's communication on Apr. 15, 2001.
- the CIR manager 404 monitors for the end of the communication, or if the use of the services provided in connection with the flow diagram illustrated in FIG. 7 is terminated. If the flow diagram started with action 502 a , i.e., with a communication from Client A, the CIR manager 404 monitors for the end of the communication. The CIR manager 404 creates or facilitates the creation of an entry corresponding to the communication from Client A, and includes the entry in a message log in action 516 . Of course, the creation of an entry corresponding to the communication from Client A can occur at other points in the process described in connection with FIG. 7 . The process ends in action 520 .
- the CIR manager 404 monitors for the termination of the use of the services by the user 402 . If the communication does not end or if a termination of the use is not detected at action 512 , the user 402 may make additional requests, such as a request for a display of an identified document, or an search, which is illustrated as action 514 . In such case, the CIR manager 404 performs the user 402 's request, as discussed in connection with action 510 . After performing the additional request, or if the user 402 does not make an additional request, the CIR manager 404 continues to monitor for the end of the communication or the termination of the use at action 512 .
- the process may move to action 516 and create an entry in a message log with the entry relating to the activities of the user described above.
- no log entry is created when the user initiates the described process such as through the selection of an entry from the message log, i.e., action 502 a .
- the flow diagram ends at action 520 .
- the user 402 indicates an initiation of a communication to Client A.
- the CIR manager 404 determines whether Client A has a preferred method of communication. This determination can be made by checking Client A's profile information. If Client A has a preferred method, which can depend on a number of factors, such as the time of the day, the CIR manger 404 notifies or reminds the user 402 of the preferred method of communication at action 606 .
- the user 402 may stop or continue his or her communication initiative as illustrated by action 608 . If the user decides to end his or her initiative to communicate with Client A, then the method ends in stop action 630 . If the user decides to continue the initiative, the user may use Client A's preferred method as indicated by the CIR manager, or the user may use another method of communication. The method continues to action 610 .
- the CIR manager 404 identifies and presents information corresponding to the communication initiated by the user.
- the information corresponding to the communication initiated by the user may include previous communications between the user 402 and Client A, and other or related messages, documents, or other information including work-files, web pages, and electronic publications.
- the CIR manager 404 may identify and/or obtain the corresponding information from its own resources, from the gateway in a data network, from the telecom manager in a telecom network, or otherwise.
- the CIR manager 404 may check whether the user desires to be presented with the corresponding information.
- the CIR manager 404 may query the user with options.
- the user's preference may be included in the user's profile information accessible by the CIR manager 404 .
- the CIR manager 404 may check for a preference such as a request for the display of the information corresponding to the initiated communication. The CIR manager 404 then may act according to the preference.
- the present inventions allow the user to request information in addition to that corresponding information which has been presented to the user as explained in the previous paragraph.
- the information corresponding to the initiated communication may be categorized and the categories of corresponding information may be presented to the user. The user then may select from among the categories and obtain additional information.
- the CIR manager 404 determines whether the user 402 has made a request for additional information. If the user has made a request, then at action 616 , the CIR manager 404 performs the task requested by the user 402 .
- the CIR manager 404 monitors for end of the initiation of the communication by the user in action 618 .
- An end to the initiation of a communication may include sending or otherwise indicating that the communication be delivered, abandonment of the initiative, time-out, or other action.
- the CIR manager 404 monitors for a request from the user 402 at action 622 and performs the requested task at action 616 . After performing the request or if the user does not make an additional request at action 622 , the CIR manager 404 continues to monitor for the end of the initiation of the communication in action 618 . If an end of the initiation of the communication occurs, the CIR manager 404 may create and/or facilitate in action 620 an entry in the message log. The entry corresponds to the communication initiated by the user. The flow diagram ends at action 630 .
- an exemplary flow diagram for a task that can be requested by the user 402 such as action 510 in FIG. 7 or action 616 in FIG. 8 .
- Such a task may include the request for transmission of a document to a communication partner.
- a request for a document transmission is detected.
- the CIR manager 404 determines whether the requested document transmission can be facilitated in the communication mode chosen by the user 402 by, for example, comparing the size of the input buffer of a targeted communication device and the size of the document the user 402 wishes to send to the communication partner. If the answer to the determination is no, the CIR manger 404 determines other possibilities for transmitting the document at action 706 .
- Examples of other possibilities include: (a) breaking the document into smaller parcels; (b) calling another application for performing services such as compression and error correction; or (c) recommending another mode of transmission, among others.
- a transition may be made from action 706 to action 708 .
- the dotted line 710 represents that the transition is not always made, for example, if the user selects to end the request to transmit the document.
- the requested document is transmitted.
- the CIR manager 404 determines if quality transmission of the document has occurred. If the answer to this determination is no, the CIR manager 404 retransmits the document at action 714 .
- the retransmission of the document may also depend on the number of attempts made to transmit the same document. For example, if the number of attempts is greater than a default value, the CIR manager 404 may not retransmit the document.
- the example illustrated with FIG. 9 concerns the user 402 's request to transmit a document.
- the user may request other tasks, and if the user requests a task that can be better served by another application, the CIR manager 404 can call that application, whether the application resides on the local server or on a remote server.
Abstract
Description
- This application is a continuation of U.S. application Ser. No. 10/109,909, filed Mar. 29, 2002, entitled “Methods and Systems for One-Stop Communications Management” (Attorney Docket BS00103), and incorporated herein by reference in its entirety. This application is also a continuation-in-part of the co-pending and commonly owned U.S. application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager” (Attorney Docket BS99159), filed Sep. 28, 2001, and which is incorporated herein by this reference. This application also claims benefit of provisional application No. 60/362,033, filed Mar. 6, 2002 and entitled “Methods and Systems for Providing Information Correlated to a Communication,” and which is incorporated herein by reference.
- The inventions relate to communications, and particularly, to the management of information about a user's communications.
- Recent technological advances have made communication devices ubiquitous. Each device may satisfy a respective different aspect of the communication needs of a user. For example, a person may have a number of communication devices at his or her disposal. The person may communicate using, among other things, a telephone, a wireless unit, a pager, a facsimile (fax) machine, or a personal digital assistant (PDA). The person also may use a computer or other device to provide information and to communicate using a web site, electronic mail (e-mail) messages, instant messages, or chat room messages. Accordingly, a person may send and receive a lot of communications using a variety of devices.
- Typically, a person with a variety of communication devices has to individually monitor each of his or her devices, thereby expending significant time and effort. If the person cannot handle a communication in a “live” fashion on any particular device, a message, note, or other record may be made of the attempted communication. Thus, the monitoring of the communication devices also may require monitoring of the devices for messages for the user. Generally, a person uses his or her communication devices in an ad hoc manner, and so, the monitoring of messages across the variety of devices also may be done in an ad hoc manner. Thus, there is a need for a better way to keep track of all of the communications of a person.
- As noted, an attempt at communication with a person may be recorded or otherwise noted in a message that may be later accessed by the person. For example, a caller may leave the person a message on his or her voicemail system. Also, a communication such as an e-mail message or a fax may leave its own record of communication. But certain types of communications and communication devices typically do not leave their own records or allow for a message to be left for the person. Thus, these “non-recorded” communications are difficult to find out about, to track, or to review. For example, a person makes a telephone call to a friend, but the friend does not answer and does not have any answering system. The person generally does not have a way to keep track of the call attempts the person has made. As another example, assume the person has enabled an instant messaging service while working on his or her computer. Typically, there is no record made of an instant message that is sent or received.
- As yet another example, assume the person engages in a chat room discussion by using his or her computer. Generally, the person's participation in the chat room discussion is not noted or otherwise recorded. The communications and communication devices that do not leave their own records or allow for a record, note, or message are referred to herein as “non-record” communications or “non-record” communication devices.
- The inability to keep track of certain types of communications can prove a disadvantage especially in business circumstances. For example, a person may be negotiating a deal involving multiple parties. Each party participates in the negotiations by using his or her own preferred communication means and devices. The person may have a log of e-mails, an answering machine full of voice mail messages, and a stack of faxes relating to the negotiations. But one of the parties may be participating in the negotiations by using some type of communications device or mechanism that does not allow for records or logs of that type of communications. So, the person's attempts at communication with the “non-record” party may not be noted by the non-record party. The non-record party may be suspicious that such attempts at communication were ever made. But the person has no way to prove he or she made the attempts. The person is at a disadvantage because he or she cannot keep track of, access, or review the attempts at communicating with the “non-record” party. The inability to be able to keep track of, access, or review these “non-record” communications can lead to miscommunication, misunderstanding, missed opportunities, and even frustration. Thus, there is a need for a way to keep track of the communications of a person including non-record communications and communications made to and/or from the non-record communication devices.
- Some disadvantages of the non-record communications and non-record communication devices have been noted. But even communications that leave a record (such as an e-mail) have disadvantages. For example, an e-mail message may refer to a specific topic, and it would be to the person's advantage to review other data related to the specific topic. Moreover, it would be advantageous to carry out such a review as quickly and efficiently as possible. For example, a message may refer to a work document, an electronic publication, or a web page which may be shared between the person and his or her communication partners. Using conventional methods, the person must individually identify, search and retrieve the work document. The activities carried out to obtain the work document may be time consuming, inefficient, and otherwise frustrating. Thus, there is a need to provide a person with information related to a message in an efficient and quick manner.
- As noted, a person generally has a lot of different types of communication devices. The person may prefer to receive certain types of communications through a certain type of device or at a certain time. The person may prefer not to receive communications of a certain type or during a certain time. Thus, there is a need for a way to manage the communications of a person so that his or her preferences are respected and are automatically implemented.
- Similarly, family members, friends, business colleagues and other communicating partners of a person may have their respective communication preferences. The person could try to memorize all of the preferences. But that may be a lot of information to keep track of, and it may be easy to make errors. For example, a client may prefer to receive communications via his or her voicemail box. If the person sends an e-mail message to the client, there may arise a delay in communication. In addition, by sending the e-mail rather than leaving a voicemail message, the person may convey the impression that the person is insensitive to the client's preferences. Neither result is desirable. Thus, there is a need for a way to manage the communications of a person so that communications made to communicating partners are made automatically in accordance with the preferences of the respective communicating partner.
- In sum, there is a need for a unified messaging system that keeps track of all of a person's communications without the person having to monitor each of his or her communication devices including non-record communications and communications made to and/or from the non-record communication devices. There is also a need for a way to manage the communications of a person so that his or her preferences are respected and are automatically implemented. In addition, there is a need for a way to manage the communications of a person so that communications made to communicating partners are generally made automatically in accordance with the preferences of the respective communicating partner.
- The inventions described herein provide information about a user's communications.
- The inventions allow a user to obtain information correlated or corresponding to a communication. In addition, the inventions allow a user to take action based on the information about a communication or the correlated or corresponding information.
- An embodiment of the inventions includes a system for making information correlated to a communication automatically available to a user. The system includes a telecommunications (telecom) manager connected to a telecommunications network; a gateway connected to a data network; and a communications manager that may communicate with the telecom manager and the gateway. In addition, the communications manager may store information about a user's communication preferences. The preferences may include a preference for presentation of information correlated or corresponding to a communication.
- In the exemplary embodiment, the communications manager receives information about a communication relating to a user from the telecom manager or from the gateway. The communication may include an instant message, a chat room message, or an attempt to reach the user by a caller using a wireline or wireless device. The communications manager uses the information to create an entry corresponding to the communication and to include the entry in a log. The log is displayed, and the user may select an entry from the log. In response to an indication of the selection of an entry, the communications manager may check the user's preferences. The preferences may include a preference for the presentation of the information correlated to a communication. In response to finding the preference, the communications manager obtains and presents the correlated information. The communications manager may obtain the information correlated to the communication from its own resources, from the telecom manager, or from the gateway.
- As noted, the communications manager may include a user's preferences. The preferences may include a request for display of information corresponding to a communication when the communication is initiated by the user. The initiated communication may include an instant message, a chat room message, or an attempt to reach the user by a caller using a wireline or wireless device. The communications manager may act according to the user's preference by noting the initiation of a communication by the user. The communications manager then may check the user's preferences for inclusion of the request for the display of information corresponding to the initiated communication. If the communications manager finds the request, then the communications manager may use communication information regarding the initiated communication to obtain and present the corresponding information. In addition, the communications manager may make the communication information regarding the initiated communication available in a log.
- Another embodiment of the inventions includes a method for making information correlated to a communication automatically available to a user. The communication may be an instant message, a chat room message, or an attempt at completing a wireline or wireless call to the user. The method stores a user's preference for presentation of information correlated to a communication. In response to receiving information about a communication, the method uses the information to create an entry corresponding to the communication, includes the entry in a message log, and displays the log. The method may receive an indication of selection of an entry from the message log. In response to the indication, the method may check the preferences for the preference for the presentation of the information correlated to the communication. In response to finding the preference, the method obtains and presents the correlated information.
- Among the user's preferences may be included a request for display of information corresponding to a communication initiated by the user. An initiated communication may include an instant message, a chat room message, or an attempt at completing a wireline or wireless call to the user. The method may act according to the preference when the method notes the initiation of the communication by the user. The method checks the user's preferences for the request for the display of the information corresponding to the initiated communication. Based on finding the request, the method may use the communication information regarding the initiated communication to obtain and present the corresponding information. In addition, the method may make the communication information regarding the initiated communication available in a message log.
- Yet another embodiment of the inventions includes a method for keeping track of communications of a user. In this embodiment, the method may receive information regarding communications of the user from a gateway connected to a data network. The communications may include an instant message or chat room message to or from the user. The method stores the information in a message log by including an entry for each communication of the user, and particularly by including an entry for each instant message or chat room message of the user.
- The exemplary method also may receive information from a telecommunications manager connected to a telecommunications network regarding an attempt to reach the user via wireline or wireless call. The method stores the information regarding the attempt in an entry in the message log. Further, the method may receive information regarding an attempt by the user to make a wireline or wireless call. The method stores information regarding the attempt in an entry in the message log.
-
FIG. 1 is a block diagram of an exemplary environment for operation of the inventions described herein. -
FIG. 2 is an exemplary message log as may be used with the present inventions. -
FIG. 3 is a block diagram of exemplary of another exemplary operating environment for the inventions described herein. -
FIG. 4 is a table illustrating a user's profile information as may be used with the present inventions. -
FIG. 5 includes tables illustrating contact information as may be used with the present inventions. -
FIG. 6 illustrates a communications environment as may be used with the present inventions -
FIG. 7 is exemplary flow diagram of the CIR manager when a user receives a communication message or when a user selects a message log. -
FIG. 8 is an exemplary flow diagram of the CIR manager when a user sends a communication message to his or her communication partner. -
FIG. 9 is an exemplary flow diagram for performing a task requested by user inFIG. 5 orFIG. 6 , such as a request for document transmission. - Stated generally, the inventions provide information about a user's communications, provide a user with information correlated or corresponding to a communication, and/or allow a user to take action based on the information about a communication or the correlated or corresponding information.
- In a related patent application, a communications and information resource (CIR) manager is described. See U.S. patent application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager,” filed Sep. 28, 2001, which is incorporated herein by this reference. The CIR manager may be used to implement the inventions described in this application. Prior to describing the present inventions, some background about the CIR manager is provided.
- The CIR Manager
- A CIR manager may function as a “super” manager with respect to the communications devices, services, and systems of a user. In particular, the CIR manager may be used to centralize communications activities and information such that the user does not have to (but may) use multiple communications devices. For example, the CIR manager may be used to keep a log of all types of communications related to the user—whatever the device, whatever the service, whatever the network.
- An advantage of the CIR manager is the user does not have to check or use each type of device for its own type of messages. Another advantage is the CIR manager may obtain information from resources including third party resources so as to facilitate communications and information gathering activities of the user. With the CIR manager, the user is provided with a centralized, efficient, and user-friendly way to handle communications activities including ways to receive, view, listen to, play, respond to, store, log, monitor, delete, copy, forward, obtain, create, and to take other actions. Moreover, the CIR manager provides the user with personalized management of communications and information resources.
- In addition, in managing the communications and information resources of the user, the CIR manager may provide the user with one or more of the following features and advantages:
-
- Recognition of the user and of others as authorized by the user;
- Remembrance and implementation of authorized users' preferences;
- Aid in finding information and resources;
- Information related to authorized users' activities and communications including call management and detail;
- Service set-ups, configurations, changes, deletions, additions, updates, and synchronizations;
- Maintenance of user account and preference information, logs, activity logs, schedules, calendars, general directories, personal directories, and the like;
- Unified messaging including notice to the user relating to communications and/or other actions; and
- Suggestions, help, updates, reminders, warnings, alerts, and other comments.
The CIR manager may integrate the features described above pursuant to a user's preferences so as to provide efficient, organized, and user-friendly communications and information resource management.
- Even though the inventions are described herein by reference to a CIR manager installed in a personal computer (PC), the inventions may be practiced with another manager, and/or other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor based or programmable consumer electronics, mini-computers, mainframe computers, etc.
- Exemplary Operating Environment of a CIR Manager—
FIG. 1 - Exemplary functions of a
CIR manager 10 are described above. To provide these functions and others, theCIR manager 10 may interact with a variety of systems, networks, and elements that may be directly connected to theCIR manager 10, may be hosted by the same host(s) as theCIR manager 10, may be functionally connected to theCIR manager 10, and/or may be accessible to theCIR manager 10 either directly and/or through other systems, networks, and/or elements. -
FIG. 1 illustrates an exemplary operating environment of aCIR manager 10 implemented on a personal computer (PC) 24. For details of anexemplary PC 24 as may be used with theCIR manager 10, see the previously referenced related application U.S. patent application Ser. No. 09/966,703, entitled “Methods and Systems for a Communications and Information Resource Manager,” filed Sep. 28, 2001. - The operating environment of
FIG. 1 illustrates theCIR manager 10 may communicate through thePC 24 with another computer(s) 25 connected or otherwise networked with thePC 24. TheCIR manager 10 also may communicate through theInternet 26 with the following: -
- Other computer(s) 27;
- A
gateway 28 serving theCIR manager 10; - An
information resource 30 such as a database; - A
messaging system 32; - A
voicemail system 34; - An
administrative center 36; and - The public switched telephone network (PSTN) 38.
In addition, theCIR manager 10 may communicate through thePSTN 38 with the following: - A telecommunications manager 40;
- A telephone (wireline unit) 42;
- A
wireless unit 44; - A
pager 46; and - A fax device (not illustrated).
- The
CIR manager 10 may have access toother computers 25 through local area networks (LANs), wide area networks (WANs), direct connections and other dial-up networks. - The
CIR manager 10 also may have access through thePC 24 to a global communications network such as theInternet 26, and through theInternet 26 to other units, networks, and systems. Particularly, theCIR manager 10 may communicate with agateway 28 connected to or operating on the Internet. Thegateway 28 may be a service platform, or other device. Thegateway 28 may be provided by the service provider of theCIR manager 10, and may serve theCIR manager 10. Communications activities to and from theCIR manager 10 on thePC 24 may be directed to thegateway 28 and/or may pass through thegateway 28 to other systems, networks, and/or elements. In passing through thegateway 28, the communications activities may be facilitated by thegateway 28. - For example, assume a user is a new subscriber to the
CIR manager 10. In setting up the user for services available through theCIR manager 10, theCIR manager 10 may send a communication to thegateway 28 for routing to the appropriate element to handle such set-up activities. In an exemplary embodiment,Administrative Center 36 may handle administrative matters including set-up activities for the service provider. Thegateway 28 delivers or otherwise routes the communication to theAdministrative Center 36 for the set-up activity. TheAdministrative Center 36 may respond to thegateway 28 with questions, information, and instructions for theCIR manager 10. - Another way in which the
gateway 28 may facilitate communications activities of theCIR manager 10 is to function as a router or director of communications and messages. For example, theCIR manager 10 may forward a request for data to thegateway 28. Thegateway 28 may determine the data may be obtained from theinformation resource 30. Thegateway 28 then forwards the request for data or the appropriate message to theinformation resource 30. Theinformation resource 30 may respond to theCIR manager 10 or to thegateway 28, which then communicates with theCIR manager 10. - Further, the
gateway 28 may facilitate communications activities between theCIR manager 10 and thePSTN 38, and other elements reached through thePSTN 38 such as the telecom manager 40, and the communications devices including thewireline unit 42, thewireless unit 44, thepager 46, and thefax device 48. Generally, the telecom manager 40 provides general functions and features related to communications of a user. Specifically, the telecom manager 40 may be implemented in a computer, on a service platform, in a network node, or other device. The telecom manager 40 may include connections to devices and networks through integrated services digital network (ISDN) lines and signaling system 7 (SS7) data links. The telecom manager 40 may be capable of functions similar to those of a service switching point (SSP) or service node (SN) of an Advanced Intelligent Network (AIN). For example, the telecom manager 40 may have the following capabilities: signaling, call set-up, routing, and access to databases. - Message Logs Function and a Message Log—
FIG. 2 - The
CIR manager 10 includes a Message Logs function, which as its name implies, enables the CIR manager to keep one or more message logs of the user's communications. A message log also may be referred to as a log. In particular, the exemplary Message Logs function of theCIR manager 10 relates to the organization, preferences, summary, and display of information pertaining to communications activities of a user. For example, the Message Logs function may enable one or more summaries of new, reviewed, sent, or other communications. Also, the Message Logs function may enable one or more call activity logs that keep track of calls or communications activities by the user. - Advantageously, the Message Logs function allows the user to keep track of all types of communications activity including conventional messages such as voice mails, e-mails, faxes, and pages. Plus, the Message Logs function allows the user to keep track of other types of messages such as instant messages, conversations in a chat room, and attempts at contact made by others.
-
FIG. 2 illustrates an exemplary message log 50 such as may be provided by theCIR manager 10 and used in connection with the inventions described herein.Message log 50 includes entries relating to the exemplary user's communications using theCIR manager 10. In the example, message log 50 includes eightentries data 68, and in this example, each entry includes four types of data: “from” 70; “type” 72; “subject” 74; and “date” 76. The fromdata 70 refers to the source or origin of the communication. Thetype data 72 refers to the type or kind of communication. Thesubject data 74 refers to the content, the substance, or other feature of the communication. Thedate data 76 refers to the date of receipt (or transmittal if from the user) of the communication. - Advantageously, the user may obtain available additional information about the communications entered in the message log 50 through use of the inventions described herein. For example, assume the user desires more information about the communication relating to
entry 54.Entry 54 relates to a voice message (such as a voicemail message) from Bill Jones received on May 20, 1999 from telephone number: (703) 345-6789. As is explained in greater detail below, through use of the inventions, the user may obtain additional information about the voicemail message from Bill Jones. - Another Exemplary Operating Environment of a CIR Manager—
FIG. 3 -
FIG. 3 illustrates another exemplary operating environment for the present inventions. In this environment, auser 102 has a plurality of communication devices and media available for communications, commonly designated as 104. The communication devices and media may include: a voicemail system as designated by the user'svoice box 104 a; an e-mail system as designated by the user'se-mail box 104 b; an instant messaging system as designated by the user'sinstant message box 104 c; a system for participating in a chat room as designated by the user'schat room box 104 d; a web site or web page as designated byweb 104 e; a fax system as designated byfax 104 f; a telephone (wireline device) 104 g; (h) awireless unit 104 h; and apager 104 i. In sum, theuser 102 has a diverse means of communicating with his or her communication partners. - As noted above, the present inventions may be implemented through the use of a
CIR manager 106. Typically, theCIR manager 106 is hosted on computer or in a computing environment, such as a personal computer (PC) 108. However, the CIR manager can be hosted on any computer device, wired and wireless. Further, in a preferred embodiment, theconnection 110 between thePC 108 hosting theCIR manager 106 and theInternet 112 is a persistent connection, preferably using broadband technology. More particularly, theconnection 110 provides means to communicate with a gateway server (“gateway”) 114. As those skilled in the art will appreciate, any wired or wireless connection can be used for theconnection 110. - Briefly, the
CIR manager 106 provides a unified, one-stop view of the user's communications. For example, when Client A of theuser 102 leaves a voicemail message for the user, theCIR manager 106 learns of the event, creates an entry for the event in a message log, and provides information regarding the voicemail message to theuser 102. If the user has expressed a preference to be provided with additional information, theCIR manager 106 may provide additional information regarding the voicemail message to the user. - As another example, when the
user 102 engages in a chat room discussion, theCIR manager 106 learns of the event, creates an entry for the event in a message log, and provides information related to the chat room discussion. If the user has expressed a preference for additional information, theCIR manager 106 may provide additional information regarding the chat room message. Advantageously, the user may add information or otherwise characterize the entry for the chat room discussion. For example, assume a user finishes a chat room discussion. TheCIR manager 106 creates an entry for the discussion. In the course of creation of the entry, theCIR manager 106 may query the user for input to be included in the entry regarding the chat room discussion. By this feature, theCIR manager 106 allows for the creation of entries that are useful to the user. - As yet another example, when the
user 102 engages (receives or sends) in an instant communication, theCIR manager 106 learns of the event, may provide information about the event, and creates an entry for the event in a message log. If the user has expressed a preference for additional information, theCIR manager 106 may provide additional information regarding the instant information to the user. As with the chat room discussion, theCIR manager 106 may give the user an opportunity to provide input such as “subject” or other information to be included in the entry for the instant message. Assume the user has included “adoption” in the subject field in the data of an entry relating to an instant message. TheCIR manager 106 may categorize the entry for the instant message as related to other entries and messages including “adoption” in the subject field. Based on this categorization, theuser 102 can retrieve the information relating to the instant communication having adoption in the subject field as well as relating to other communications having adoption in the subject field. - The
CIR manager 106 can provide a unified, one-stop view of the user's communications because theCIR manager 106 may be set up to communicate with the application program interface (“API”) for each of the providers and/or programs that enable corresponding communication devices and activities. The ability of theCIR manager 106 to communicate with APIs and applications allows theCIR manager 106 to carry out a user's preferences with respect to the presentation of information relating to the user's communications. TheCIR manager 106 may communicate with the plurality of the API's using any of conventional methods such as polling, event driven interrupts, and/or a token ring. - The
CIR manager 106 as hosted byPC 108 may communicate with atelecommunications manager 132 in thePSTN 130 by a wired or wireless connection. When communications are received or sent via thePSTN 130, theCIR manager 106 learns of the communication events, generally creates entries corresponding to the events, and can categorize the communications, so that theuser 102 can have a complete view of his or her communication activities. Moreover, theCIR manager 106 may tag the data or part(s) of the data in an entry. TheCIR manager 106 may use the tag to retrieve the data or part(s) of the data in an entry, or for other reasons. The tag may be a numerical tag or other tag or indicator. TheCIR manager 106 may tag the data or part(s) of the data based on preferences of the user indicated at time of system set-up or at other times. - For example, when a call is directed to the telephone number corresponding to the user's
telephone 104 g, atelecom manager 132 in thePSTN 130 notifies theCIR manager 106 of the call. TheCIR manager 106 creates an entry for the telephone call in the message log even if the call goes unanswered. TheCIR manager 106 may tag data (including part(s) of the data) in the entry theCIR manager 106 creates for the unanswered call. TheCIR manager 106 may tag the data for several reasons. For example, theCIR manager 106 may tag the originating telephone number in the entry for the unanswered call so as to be able to obtain additional information about the unanswered call. Then, if the user seeks additional information about the unanswered call, theCIR manager 106 may use the tagged data (the originating telephone number) to obtain the additional information. Using the tagged data, theCIR manager 106 may check its own resources to determine whether it has additional information on the originating telephone number. Using the tagged data, theCIR manager 106 may contact thetelecom manager 132 for additional information such as a reverse white pages listing corresponding to the originating telephone number. - In addition or in alternative to using the tagged data to obtain additional information about a communication, the
CIR manager 106 may use the tagged data to retrieve the substance of the communication. The tagged data may provide information to theCIR manager 106 with respect to the path or route to take to retrieve the substance of the communication. In some cases, the tagged data may provide theCIR manager 106 with information on the application(s) to call to retrieve the substance of the communication. The tagged data is not necessarily data included in the entry corresponding to the communication in the message log. For example, theCIR manager 106 may receive information from thegateway 114 on a voicemail message for the user. TheCIR manager 106 may tag data so as to obtain information on the retrieval through thegateway 114 of the substance of the voicemail message from a voicemail system. - With the entries in the message log, the user has a record of attempts made to contact him or her via a call to the user's telephone number. The entry for the unanswered call may be marked as an “unanswered call”. In creating the entry regarding an attempted call (wireline or wireless), the
CIR manager 106 may not be able to fill in all of the fields of the data in the entry. For example, theCIR manager 106 may be unable to fill in the subject field for an unanswered call. But theCIR manager 106 may substitute some other information (like “unanswered call”) in the subject field of the entry. Advantageously, the user may add any missing information or substitute other information in the entry. - As another example, when a fax document is transmitted to the user, the
telecom manager 132 notifies theCIR manager 106. TheCIR manager 106 creates an entry for the fax in the message log. TheCIR manager 106 may tag data or part(s) of data in the entry theCIR manager 106 creates for the fax. The tagged data may be used by theCIR manager 106 to obtain additional information correlated or corresponding to the fax, or for other reasons. The user may be able to access the fax by activating the entry for the fax in the message log. In response to the activation of the entry for the fax, theCIR manager 106 may query the user for input on desired actions. The user may indicate a desire to review the fax. In response to the indication, theCIR manager 106 may use tagged data in the entry corresponding to the fax or other tagged data related to the fax to obtain the substance of the fax. TheCIR manager 106 then may display the fax to the user on the computer screen or otherwise take actions to present the fax to the user. - Referring again to
FIG. 3 , thetelecom manager 132 in thePSTN 130 may communicate with thegateway 114 in theInternet 112. The techniques and methods of communications between elements in thePSTN 130 and theInternet 112 are well known to those skilled in the art. - Profile Information—
FIG. 4 - Referring to
FIG. 4 , theCIR manager 106 includesprofile information 202 for theuser 102. For example,profile information 202 for theuser 102 includes, among other things, a list of the communication devices, such as a telephone, a cellular telephone, or a pager of theuser 102. The profile information file 202 also includes information regarding theuser 102's preferred methods of communication. Theexemplary profile information 202 shows the preferences may include: (a) the time of the communication; (b) the identity of the communication partner(s); and (c) the subject matter of the communication. Of course, other preferences may be included or substituted. - The
profile information 202 also illustrates the user may set his or her preferences regarding the presentation of information in addition to, correlated to, or corresponding to a communication. Such additional, correlated, or corresponding information may include, inter alia, information to related communications, identifying information regarding communication originators or recipients, and information on subject matter mentioned in the communication or in information about the communication. Additional, correlated, or corresponding information also may include other entries, or communications sharing some feature in common with the entry (or related communication) for which the correlated information is sought. Further, additional, correlated, or corresponding information may relate to documents and the like that may be referenced in a communication, or in an entry relating to a communication in a message log. - For example, an entry for an instant message may include through user input reference to a document such as “work report” in the subject field of the entry in the message log. The data relating to the “work report” in the subject field of the entry may be tagged so the
CIR manager 106 may use the tagged data to obtain the document, or to obtain instructions on how to obtain the document. Advantageously, the user simply may activate the subject field of “work report” and obtain correlated information including access to or a copy of the referenced work report. - The additional, correlated or corresponding information need not directly pertain to the entry used in finding the information. There may be an indirect or two or more step relationship between the entry and the additional, correlated, or corresponding information. For example, the subject feature or subject data of an entry 80 a may include the telephone number: (704) 345-6789. By its inclusion of the “704” area code, the number implies the associated telephone is located in the State of North Carolina. Thus, an internet link to the Tourism Board of North Carolina may constitute correlated information to the entry including the telephone number (704) 345-6789.
- In the
exemplary profile information 202 ofFIG. 4 , the preference for correlated information is set to “all”. In this example, the “all” setting indicates the user's preference for correlated information on all communications to/from whatever devices. For example, assume the user receives an e-mail, a page, and a fax. Information on each communication is entered into the message log. As part of creating each entry for the message log, theCIR manager 106 may tag data or part(s) of data in each entry so that correlated information may be retrieved respectively for each entry. The preference for correlated information may be set to include less than all devices. - In addition, through the
profile information 202 or otherwise, a user may indicate preference for correlated information based on a factor other than the type of device originating a communication to or from the user. For example, the user may choose one or more fields of an entry in the message log as holding the data to be tagged for obtaining correlated information or otherwise. To further this example, the user may indicate a preference for obtaining correlated information on each originator or source of a communication (the “from” field in an entry). Advantageously, the user may mix and match the various factors of a communication so as to indicate the user's preferences for correlated information. For example, the user may indicate a preference for correlated information on all communications to/from a pager and on the data in the subject fields of all communications. - Also, the
profile information 202 relating to a user can be used, for example, to populate certain fields in a communication so theuser 102 need not enter repeated information, such as for example, the date and time, the subject matter, and/or canned responses. - Contact Information—
FIG. 5 - Referring to
FIG. 5 , theCIR manager 106 also hascontact information 302 for theuser 102.Exemplary contact information 302 lists communication partners of theuser 102, collectively designated as 342. In addition, typically, each communication partner listed on thecontact information 302 is associated with additional information that may be presented to the user on a “contact card”, collectively designated as 352. A contact card 352 may contain, among other things, the types of communication devices used by the communication partner corresponding to the contact card. The contact card 352 may also include the preferred methods of communicating for the corresponding communication partner. As with theprofile information 202, the preference information in the contact card 352 can be time, subject matter, and other factor sensitive. In sum, theCIR manager 106 may include profile information for theuser 102 as well as for each communication partner listed on thecontact information 302. - In a preferred embodiment, the
CIR manager 106 can either automatically update the contact information or otherwise facilitate theuser 102's entry of information regarding his or her communication partner(s). As an example, theCIR manager 106 may receive information about a communication to the user from Person A. TheCIR manager 106 may be set so theCIR manager 106 checks the user's contact information to determine whether information on Person A is present in the contact information. If there is no information on Person A, theCIR manager 106 may add Person A's information to the contact information, if that is the preference set up (typically at service set-up) by the user. Alternatively, theCIR manager 106 may query the user as to whether Person A's information should be added. - If the contact information includes Person A's information, the
CIR manager 106 may be set-up based on preferences of the user to compare the information received with Person A's communication to Person A's information in the contact information. If the comparison yields differences, theCIR manager 106 may automatically update Person A's contact information or may query the user whether to update Person A's contact information. To further this example, theCIR manager 106 may automatically enter new information regarding Person A, if he or she communicates with theuser 102 via a previously unused communication device. As another example, if a new contact, Person ZZ communicates with theuser 102, theCIR manager 106 may query theuser 102 to determine if the user wishes to enter the information regarding Person ZZ in thecontact information 302. - Advantageously, the
CIR manager 106 may enter information into a user'scontact information 302 when a person or entity not included in the user's contact information makes or receives a communication to or from the user. TheCIR manager 106 may automatically enter the new information or first query the user with respect to the entry of the information, per the preferences of the user. For example, assume a person sends the user an e-mail. TheCIR manager 106 creates an entry for the e-mail in the message log. If the user has indicated a preference for automatic update of contact information on new communicating partners, then theCIR manager 106 may use the information received in association with the e-mail to create an entry in the contact information for the new communicating partner. TheCIR manager 106 may be unable to fill in all of the information in the contact information regarding the new communicating partner. TheCIR manager 106 may query the user for the missing information, or theCIR manager 106 may contact the new communicating partner for the missing information. In this example, the new communicating partner communicated by e-mail. TheCIR manager 106 may send a reply e-mail requesting the missing information. - Exchange of Communications—
FIG. 6 - Referring to
FIG. 6 , an exemplary method of organizing communications received and sent by theuser 402 is described. TheCIR manager 404 provides an interface for the user's communications regardless of whether the messages are sent or received by theuser 402 and regardless of the type of the communications device. TheCIR manager 404 generally provides the interface for the user's communications by reference information on the applications, programs, databases, sources, networks, and other resources that are involved with the user's communications. This information may be registered with theCIR manager 404. Generally, at system set-up, the CIR manager is populated with the appropriate instructions on where to look for information and how to get the information. For example, at system set-up, the CIR manager is provided with the appropriate instructions so the CIR manager may communicate with the telecom manager in the telecommunications network and with the gateway in the data network. The instructions provided to the CIR manager may be updated or changed as needed so as to accommodate a user's changing communication needs. - Also at system set-up, the CIR manager may be provided information and instructions relating to the retrieval of correlated information. As noted above, a user's
profile information 406 may indicate a preference for the retrieval of correlated information under certain conditions. Specific data in an entry relating to a communication may be tagged so as to be used to retrieve the information. The tagged data may include numerical tags that include or reference instructions. The instructions may be included in the CIR manager so the CIR manager may access the instructions to obtain the correlated information. For example, the CIR manager may include instructions on obtaining correlated information on the data in the subject field of an entry in the message log. The instructions may include a direction to the CIR manager to make a check of the CIR manager's resources, to query the gateway in the data network, to poll a particular application from a networked computer, or to take other action. The CIR manager carries out the instructions so as to retrieve the correlated information. The CIR manager may be updated or changed as needed so as to accommodate a user's changing communication needs. - The
CIR manager 404 hasprofile information 406 for theuser 402, and has contact information (client profile) collectively designated as 420, for each of the user's clients or communicating partners, who are collectively designated as 410. For example, theclient profile 420 a lists a cellular telephone and a facsimile machine forClient A 410 a. As another example, theprofile information 420 b lists a pager and a telephone forClient B 410 b. - A exemplary embodiment of the
CIR manager 404 tags, associates, categorizes and identifies each message communicated to and from theuser 402 per the preferences of the user or some default. For example, theCIR manager 404 creates and/or facilitates the creation of an entry for a communication in message log 430. The message log 420 includes entries, collectively identified as 431. Each entry includes data that identifies a communication of theuser 402 using fields (also referred to as identifiers or features). An entry 431 in message log 430 illustrates three fields of the data: (a) whoelement 432; (b) whatelement 434; and (c) whenelement 436. The user may set-up theCIR manager 404 to include additional, fewer, or other identifiers in an entry. Using any identifiers, a message can be retrieved or reviewed by theuser 402. Typically, the data in the chosen identifier is tagged so theCIR manager 106 is provided with information or may obtain instructions on how and from where to retrieve the substance of the message. The identifiers in an entry relating to a communication in the message log also may be used to retrieve other information related to the communication. - In particular, the fields of an entry in the message log may be used to obtain information correlating to the communication. The term “correlated information” also may include “corresponding information” or “additional information”. Further details on obtaining the correlated or corresponding information are found in the previously referenced and related U.S. patent application Ser. No. ______, entitled “Methods and Systems for Providing Information Correlated to a Communication”, filed concurrently with this application, and which is incorporated herein by reference.
- In sum, the
CIR manager 404 uses data from an entry (such as data in a field, identifier, or feature) to retrieve information correlated to the communication. In some embodiments, the data may be tagged such as with a numerical tag so as to provide theCIR manager 404 with instructions or information on the retrieval of the corresponding or correlated information. To retrieve the correlated or corresponding information, theCIR manager 10 may check its own resources, and/or may check resources that may be reached through the gateway and the Internet, or through the telecom manager 40 and thePSTN 38, and/or in other ways. - For example, when the
user 402 receives, transmits, or exchanges instant messages with Client C, theCIR manager 404 creates an entry for each of the instant messages. The entries are included in the message log 430. TheCIR manager 404 may create an entry for an instant message automatically, if that is the user's preference, or may ask the user whether an entry should be created. In addition, theCIR manager 404 may ask theuser 402 to enter one or more fields of information. - Assume for example, the user receives an instant message. The instant message is sent to the user over the Internet through the gateway and to the
CIR manager 404 prior to appearing on the user's computer screen. TheCIR manager 404 receives or otherwise accesses information associated with and/or including the instant message. TheCIR manager 404 uses the information to create an entry in the message log. - In this example, the
CIR manager 404 accesses information on the originator of the instant message and places the originator information in the who field 432 (also referred to as identifier or feature of the data). For the whatfield 434 of the entry, theCIR manager 404 may simply include “instant message” or the CIR manager select information associated with the instant message and include that information in the whatfield 434. With respect to the whenfield 436, theCIR manager 404 may obtain that information from the instant message, or theCIR manager 404 may use its own internal clock to include a time in the whenfield 436 of the entry corresponding to the instant message in the message log. TheCIR manager 404 may query the user for information to be added, or changed with respect to any entry the CIR manager creates. Depending on the preferences of the user, the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication. - The processes for creating entries in a message log for participation in a chat room, and for attempted calls (to or from the user)(wireless or wireline) are generally the same as described in the previous paragraphs for creating the entry for the instant message. The processes for creating entries in a message log for attempted calls (to or from the user)(wireless or wireline) are also generally the same as described in the previous paragraphs for creating the entry for the instant message except that the
CIR manager 404 may receive information or access information about the attempted calls from the telecom manager, which may receive the information from the PSTN or other telecommunications network. In some cases, theCIR manager 404 may receive or access information about the attempted calls from the gateway, which may receive the information from the Internet or other data network. Depending on the preferences of the user, the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication. - As another example, when the
user 402 holds a telephone conversation with Client Z, theCIR manager 404 creates an entry in the message log for the telephone conversation. TheCIR manager 404 may query the user for information to include as data in the pertinent entry in the message log. TheCIR manager 404 may offer a menu with a list of options, a notepad or other device so theuser 402 may enter information for the entry. For example, the user may want to note issues discussed in the telephone conversation. However, as those skilled in the art will appreciate, the entry of information relating to a telephone conversation can also be automatic using, for example, digital signal processing techniques for audio signals. Depending on the preferences of the user, the CIR manager may tag the data (or part(s) of data) in the fields of the entry so as to be able to retrieve the substance of the communication and/or information correlated to the communication. - In sum, the
CIR manager 404 can build data relationships for communications of theuser 402 regardless of the user's communication methods. The data relationships can include, among other things: (a) relevant parties to a communication; (b) relevant information exchanged between the parties; and (c) relevant documents retrievable from a local storage device or a remote server via a network, such as the Internet. - Exemplary Flow Diagram—
FIG. 7 - Referring to
FIG. 7 , an exemplary flow diagram for theCIR manager 404 is presented for the case in which theuser 402 receives a communication from Client A, or selects an entry from a message log where the entry corresponds to a communication. In eitheraction - At
action 502 a, theuser 402 receives, for example, a communication from Client A. Ataction 502 b, theuser 402 identifies or selects an entry from the message log. The entry corresponds to a particular message. Ataction 504, theCIR manager 404 identifies information correlated, respectively depending on the previous action, to the communication from Client A or to the selected entry. The correlated information may include the communication itself, related messages, information and documents, including work-files, web pages, and electronic publications. TheCIR manager 404 may identify and/or obtain the correlated information from its own resources, from the gateway in a data network, from the telecom manager in a telecom network, or otherwise. - In an embodiment, instead of automatically identifying the correlated information, the
CIR manager 404 may check whether the user desires to be presented with the correlated information. TheCIR manager 404 may query the user with presentation options. Alternatively, the user's preference may be included in the user's profile information accessible by theCIR manager 404. TheCIR manager 404 may check for a preference such as a preference for the presentation of the information correlated to the communication. TheCIR manager 404 then may act according to the preference. - For example, in response to
action 502 a of receiving a communication from Client A, theCIR manager 404 may obtain the “identity” of the communicating party. The identity may be obtained from or using information associated with the communication such as information related to the originating or sending party. TheCIR manager 404 may use the identity to identify and obtain related messages and documents. TheCIR manager 404 also may use the identity to identify and obtain previous communications relating to Client A. The previous communications may include communications from, to, related to, or mentioning Client A. - Another example is presented with respect to
action 502 b when the user selects an entry from a message log. The entry corresponds to a particular communication. In response to the selection of the entry, theCIR manager 404 may automatically identify messages and documents correlated to the communication corresponding to the entry selected by the user. - At
action 506, theCIR manager 404 presents the correlated information to theuser 402, using for example, icons and/or displays for the messages and documents. Ataction 508, theuser 402 may request to view messages and/or documents presented ataction 506 by, for example, selecting the appropriate icon(s). Ataction 510, theCIR manager 404 performs the user's request received ataction 508 by, for example, launching a browser to display a web page, retrieving a document, or transmitting a document. Ataction 508, theuser 402 may also request a search for a particular document or additional information that has not been presented to the user ataction 506. In such a case, theCIR manager 404 searches for messages and/or documents related to the search request and presents the additional information to theuser 402 ataction 510. - For example, referring to
FIG. 6 , if Client A calls the user on Nov. 6, 2001 to discuss his/her 2001 tax return, theCIR manager 404 can present to theuser 402 all previous communications between theuser 402 and Client A, documents identified by theCIR manager 404 as being related to Client A and the subject matter of previous communications, and any additional information theuser 402 may request. - Similarly, if Client Z calls the user on Nov. 6, 2001, the
CIR manager 404 can facilitate the user's 402 retrieval of information related to Client Z. In this example, theCIR manager 404 includes information that Client Z has a web site, and thus can launch a web browser to display the web page of Client Z. In addition, theCIR manager 404 learns that the subject matter of Client B's message communicated on Apr. 15, 2001 is related to the subject matter of Client Z's message communicated on Aug. 10, 2001, and thus theCIR manager 404 may present message (or the entry in a message log) for Client B's communication on Apr. 15, 2001. - Referring again to
FIG. 7 , ataction 512 theCIR manager 404 monitors for the end of the communication, or if the use of the services provided in connection with the flow diagram illustrated inFIG. 7 is terminated. If the flow diagram started withaction 502 a, i.e., with a communication from Client A, theCIR manager 404 monitors for the end of the communication. TheCIR manager 404 creates or facilitates the creation of an entry corresponding to the communication from Client A, and includes the entry in a message log inaction 516. Of course, the creation of an entry corresponding to the communication from Client A can occur at other points in the process described in connection withFIG. 7 . The process ends inaction 520. - If the flow diagram started with
action 502 b, i.e., theuser 402's selection of an entry corresponding to a particular communication, theCIR manager 404 monitors for the termination of the use of the services by theuser 402. If the communication does not end or if a termination of the use is not detected ataction 512, theuser 402 may make additional requests, such as a request for a display of an identified document, or an search, which is illustrated asaction 514. In such case, theCIR manager 404 performs theuser 402's request, as discussed in connection withaction 510. After performing the additional request, or if theuser 402 does not make an additional request, theCIR manager 404 continues to monitor for the end of the communication or the termination of the use ataction 512. - Once the communication or the service is ended, the process may move to
action 516 and create an entry in a message log with the entry relating to the activities of the user described above. In some embodiments, no log entry is created when the user initiates the described process such as through the selection of an entry from the message log, i.e.,action 502 a. The flow diagram ends ataction 520. - Exemplary Flow Diagram—
FIG. 8 - Referring to
FIG. 8 , an exemplary flow diagram of the actions that may be taken by exemplary embodiments in the case of a user initiating a communication with Client A. Ataction 602, theuser 402 indicates an initiation of a communication to Client A. Ataction 604, theCIR manager 404 determines whether Client A has a preferred method of communication. This determination can be made by checking Client A's profile information. If Client A has a preferred method, which can depend on a number of factors, such as the time of the day, theCIR manger 404 notifies or reminds theuser 402 of the preferred method of communication ataction 606. In response to theCIR manager 404's notification of Client A's preferred method of communication, theuser 402 may stop or continue his or her communication initiative as illustrated byaction 608. If the user decides to end his or her initiative to communicate with Client A, then the method ends instop action 630. If the user decides to continue the initiative, the user may use Client A's preferred method as indicated by the CIR manager, or the user may use another method of communication. The method continues toaction 610. - At
actions CIR manager 404 identifies and presents information corresponding to the communication initiated by the user. The information corresponding to the communication initiated by the user may include previous communications between theuser 402 and Client A, and other or related messages, documents, or other information including work-files, web pages, and electronic publications. TheCIR manager 404 may identify and/or obtain the corresponding information from its own resources, from the gateway in a data network, from the telecom manager in a telecom network, or otherwise. - In an embodiment, prior to identifying the corresponding information, the
CIR manager 404 may check whether the user desires to be presented with the corresponding information. TheCIR manager 404 may query the user with options. Alternatively, the user's preference may be included in the user's profile information accessible by theCIR manager 404. TheCIR manager 404 may check for a preference such as a request for the display of the information corresponding to the initiated communication. TheCIR manager 404 then may act according to the preference. - Advantageously, the present inventions allow the user to request information in addition to that corresponding information which has been presented to the user as explained in the previous paragraph. Alternatively, the information corresponding to the initiated communication may be categorized and the categories of corresponding information may be presented to the user. The user then may select from among the categories and obtain additional information. At
action 614, theCIR manager 404 determines whether theuser 402 has made a request for additional information. If the user has made a request, then ataction 616, theCIR manager 404 performs the task requested by theuser 402. If theCIR manager 404 has not received a request for additional information, or after performing the task requested by the user inaction 616, the CIR manager monitors for end of the initiation of the communication by the user inaction 618. An end to the initiation of a communication may include sending or otherwise indicating that the communication be delivered, abandonment of the initiative, time-out, or other action. - If the end of the initiation of the communication does not occur (within a specified time or otherwise), the
CIR manager 404 monitors for a request from theuser 402 ataction 622 and performs the requested task ataction 616. After performing the request or if the user does not make an additional request ataction 622, theCIR manager 404 continues to monitor for the end of the initiation of the communication inaction 618. If an end of the initiation of the communication occurs, theCIR manager 404 may create and/or facilitate inaction 620 an entry in the message log. The entry corresponds to the communication initiated by the user. The flow diagram ends ataction 630. - Exemplary Flow Diagram—
FIG. 9 - Referring to
FIG. 9 , an exemplary flow diagram for a task that can be requested by theuser 402 such asaction 510 inFIG. 7 oraction 616 inFIG. 8 . Such a task may include the request for transmission of a document to a communication partner. Ataction 702, a request for a document transmission is detected. Ataction 704, theCIR manager 404 determines whether the requested document transmission can be facilitated in the communication mode chosen by theuser 402 by, for example, comparing the size of the input buffer of a targeted communication device and the size of the document theuser 402 wishes to send to the communication partner. If the answer to the determination is no, theCIR manger 404 determines other possibilities for transmitting the document ataction 706. Examples of other possibilities include: (a) breaking the document into smaller parcels; (b) calling another application for performing services such as compression and error correction; or (c) recommending another mode of transmission, among others. Depending on the best possibilities that theCIR manager 404 determines independently and/or based on theuser 402's input, a transition may be made fromaction 706 toaction 708. The dottedline 710 represents that the transition is not always made, for example, if the user selects to end the request to transmit the document. - At
action 708, the requested document is transmitted. Ataction 712, theCIR manager 404 determines if quality transmission of the document has occurred. If the answer to this determination is no, theCIR manager 404 retransmits the document ataction 714. The retransmission of the document may also depend on the number of attempts made to transmit the same document. For example, if the number of attempts is greater than a default value, theCIR manager 404 may not retransmit the document. - The example illustrated with
FIG. 9 concerns theuser 402's request to transmit a document. However, the user may request other tasks, and if the user requests a task that can be better served by another application, theCIR manager 404 can call that application, whether the application resides on the local server or on a remote server. - The exemplary embodiments of the inventions described herein were chosen and described in order to explain the principles of the inventions and their practical applications so as to enable others skilled in the art to utilize the inventions including various embodiments and various modifications as are suited to the particular uses contemplated. The examples provided herein in the written description or in the drawings are not intended as limitations of the inventions. Other embodiments will suggest themselves to those skilled in the art. Therefore, the scope of the inventions is to be limited only by the claims below.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/236,907 US7441027B2 (en) | 2001-09-28 | 2005-09-28 | Methods, systems, and products for creating message logs |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/966,703 US7313617B2 (en) | 2001-09-28 | 2001-09-28 | Methods and systems for a communications and information resource manager |
US36203302P | 2002-03-06 | 2002-03-06 | |
US10/109,909 US7007085B1 (en) | 2001-09-28 | 2002-03-29 | Message log for wireline, voice mail, email, fax, pager, instant messages and chat |
US11/236,907 US7441027B2 (en) | 2001-09-28 | 2005-09-28 | Methods, systems, and products for creating message logs |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/966,703 Continuation US7313617B2 (en) | 2001-09-28 | 2001-09-28 | Methods and systems for a communications and information resource manager |
US10/109,909 Continuation US7007085B1 (en) | 2001-09-28 | 2002-03-29 | Message log for wireline, voice mail, email, fax, pager, instant messages and chat |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060026232A1 true US20060026232A1 (en) | 2006-02-02 |
US7441027B2 US7441027B2 (en) | 2008-10-21 |
Family
ID=35922952
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/109,909 Expired - Lifetime US7007085B1 (en) | 2001-09-28 | 2002-03-29 | Message log for wireline, voice mail, email, fax, pager, instant messages and chat |
US11/236,907 Expired - Lifetime US7441027B2 (en) | 2001-09-28 | 2005-09-28 | Methods, systems, and products for creating message logs |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/109,909 Expired - Lifetime US7007085B1 (en) | 2001-09-28 | 2002-03-29 | Message log for wireline, voice mail, email, fax, pager, instant messages and chat |
Country Status (1)
Country | Link |
---|---|
US (2) | US7007085B1 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080162648A1 (en) * | 2006-12-29 | 2008-07-03 | Wang Kai Benson Leung | Device and method of expressing information contained in a communication message sent through a network |
US20080273686A1 (en) * | 2007-05-01 | 2008-11-06 | Unison Technologies Llc | Systems and methods for scalable hunt-group management |
US20090041217A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with combined communication log |
US20090041052A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with user selectable reply format |
US20090041216A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with conditional communication handling |
US20090067595A1 (en) * | 2007-05-01 | 2009-03-12 | Unison Technologies Llc | Systems and methods for phone call management |
US20090119368A1 (en) * | 2007-11-02 | 2009-05-07 | International Business Machines Corporation | System and method for gathering conversation information |
US20100198927A1 (en) * | 2006-08-16 | 2010-08-05 | Tonnison James I | Enhanced Email System |
US20100235223A1 (en) * | 2009-03-16 | 2010-09-16 | Lyman Christopher M | System and method for automatic insertion of call intelligence in an information system |
US8650255B2 (en) | 2008-12-31 | 2014-02-11 | International Business Machines Corporation | System and method for joining a conversation |
US20160259601A1 (en) * | 2013-10-25 | 2016-09-08 | Next Print Technologies Aps | Method of handling a print job submitted to a cloud printing service for processing by an authenticated printing system and system for performing the method |
US20160259602A1 (en) * | 2013-10-25 | 2016-09-08 | Next Print Technologies Aps | Method of handling a guest print job for processing by an authenticated printing system and system for performing the method |
US20160267282A1 (en) * | 2013-10-25 | 2016-09-15 | Next Print Technologies Aps | Method of handling a document stored in a cloud storage system for processing by an authenticated printing system and system for performing the method |
US9955004B2 (en) | 2009-03-16 | 2018-04-24 | Fonality, Inc. | System and method for utilizing customer data in a communication system |
US10831765B1 (en) * | 2014-10-21 | 2020-11-10 | Zoosk, Inc. | System and method for providing information about users who performed internet-based activities |
Families Citing this family (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7313617B2 (en) | 2001-09-28 | 2007-12-25 | Dale Malik | Methods and systems for a communications and information resource manager |
US7472187B2 (en) * | 2001-09-28 | 2008-12-30 | At&T Intellectual Property I, L.P. | Communications and information resource manager |
US20030217098A1 (en) * | 2002-05-15 | 2003-11-20 | Microsoft Corporation | Method and system for supporting the communication of presence information regarding one or more telephony devices |
US20030217142A1 (en) * | 2002-05-15 | 2003-11-20 | Microsoft Corporation | Method and system for supporting the communication of presence information regarding one or more telephony devices |
US7539291B2 (en) | 2002-10-16 | 2009-05-26 | J2 Global Communications | Enhancing messaging services using translation gateways |
US20050083851A1 (en) * | 2002-11-18 | 2005-04-21 | Fotsch Donald J. | Display of a connection speed of an on-line user |
WO2004046876A2 (en) | 2002-11-18 | 2004-06-03 | America Online, Inc. | Enhanced buddy list interface |
US7412491B2 (en) * | 2003-04-30 | 2008-08-12 | International Business Machines Corporation | Method and apparatus for enhancing instant messaging systems |
US8184782B1 (en) * | 2003-09-17 | 2012-05-22 | Healthsense, Inc. | Method and apparatus for processing voice calls |
US20050080866A1 (en) * | 2003-10-14 | 2005-04-14 | Kent Larry G. | Selectively displaying time indications for instant messaging (IM) messages |
KR100547790B1 (en) * | 2003-10-31 | 2006-01-31 | 삼성전자주식회사 | Create individual information including call log and how to use the individual information |
US7383307B2 (en) * | 2004-01-07 | 2008-06-03 | International Business Machines Corporation | Instant messaging windowing for topic threads |
US7475110B2 (en) * | 2004-01-07 | 2009-01-06 | International Business Machines Corporation | Method and interface for multi-threaded conversations in instant messaging |
US7480696B2 (en) * | 2004-01-07 | 2009-01-20 | International Business Machines Corporation | Instant messaging priority filtering based on content and hierarchical schemes |
US20080040315A1 (en) * | 2004-03-31 | 2008-02-14 | Auerbach David B | Systems and methods for generating a user interface |
US7707142B1 (en) | 2004-03-31 | 2010-04-27 | Google Inc. | Methods and systems for performing an offline search |
US8041713B2 (en) | 2004-03-31 | 2011-10-18 | Google Inc. | Systems and methods for analyzing boilerplate |
US7664734B2 (en) * | 2004-03-31 | 2010-02-16 | Google Inc. | Systems and methods for generating multiple implicit search queries |
US9009153B2 (en) * | 2004-03-31 | 2015-04-14 | Google Inc. | Systems and methods for identifying a named entity |
US8631001B2 (en) * | 2004-03-31 | 2014-01-14 | Google Inc. | Systems and methods for weighting a search query result |
US7272601B1 (en) * | 2004-03-31 | 2007-09-18 | Google Inc. | Systems and methods for associating a keyword with a user interface area |
US7693825B2 (en) | 2004-03-31 | 2010-04-06 | Google Inc. | Systems and methods for ranking implicit search results |
US8131754B1 (en) | 2004-06-30 | 2012-03-06 | Google Inc. | Systems and methods for determining an article association measure |
US7788274B1 (en) | 2004-06-30 | 2010-08-31 | Google Inc. | Systems and methods for category-based search |
US20060176831A1 (en) * | 2005-02-07 | 2006-08-10 | Greenberg Joel K | Methods and apparatuses for selecting users to join a dynamic network conversation |
US9083564B2 (en) | 2005-10-13 | 2015-07-14 | At&T Intellectual Property I, L.P. | System and method of delivering notifications |
US20070192427A1 (en) * | 2006-02-16 | 2007-08-16 | Viktors Berstis | Ease of use feature for audio communications within chat conferences |
JP2009541930A (en) * | 2006-06-22 | 2009-11-26 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Low pressure gas discharge lamp |
US7548895B2 (en) * | 2006-06-30 | 2009-06-16 | Microsoft Corporation | Communication-prompted user assistance |
US8953756B2 (en) | 2006-07-10 | 2015-02-10 | International Business Machines Corporation | Checking for permission to record VoIP messages |
US8503622B2 (en) * | 2006-09-15 | 2013-08-06 | International Business Machines Corporation | Selectively retrieving VoIP messages |
WO2008042300A2 (en) * | 2006-09-29 | 2008-04-10 | Siemens Communications, Inc. | Identifying a voicemail and synchronizing a voicemail with a call log |
US20080107045A1 (en) * | 2006-11-02 | 2008-05-08 | Viktors Berstis | Queuing voip messages |
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) |
US8972504B2 (en) | 2007-11-16 | 2015-03-03 | International Business Machines Corporation | Forwarding un-responded to instant messages to electronic mail |
WO2009077901A1 (en) * | 2007-12-18 | 2009-06-25 | Koninklijke Philips Electronics N.V. | Method and system for enabling conversation |
US9508059B2 (en) | 2008-04-25 | 2016-11-29 | T-Mobile Usa, Inc. | Messaging device having a graphical user interface for initiating communication to recipients |
WO2009149133A2 (en) * | 2008-06-02 | 2009-12-10 | Tekelec | Methods, systems, and computer readable media for providing next generation network (ngn)-based end user services to legacy subscribers in a communications network |
US8290126B2 (en) * | 2008-12-19 | 2012-10-16 | CenturyLing Intellectual Property LLC | System and method for a visual voicemail interface |
US8345832B2 (en) * | 2009-01-09 | 2013-01-01 | Microsoft Corporation | Enhanced voicemail usage through automatic voicemail preview |
US8457602B2 (en) * | 2010-11-08 | 2013-06-04 | Cox Communications, Inc. | Hybrid communications mailbox |
US8705707B1 (en) * | 2012-09-14 | 2014-04-22 | Google Inc. | Labeling communcation device call logs |
US10771629B2 (en) | 2017-02-06 | 2020-09-08 | babyTel Inc. | System and method for transforming a voicemail into a communication session |
Citations (94)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US623027A (en) * | 1899-04-11 | Displaying device | ||
US631186A (en) * | 1898-04-08 | 1899-08-15 | George R Sherwood | Machine for removing pith from cornstalks. |
US676872A (en) * | 1900-05-22 | 1901-06-25 | Peter M Buckland | Feed-water regulator. |
US4706242A (en) * | 1985-03-28 | 1987-11-10 | Stc Plc | Digital telecommunication system |
US4935954A (en) * | 1988-12-28 | 1990-06-19 | At&T Company | Automated message retrieval system |
US5311583A (en) * | 1992-08-05 | 1994-05-10 | At&T Bell Laboratories | International priority calling system with callback features |
US5436965A (en) * | 1993-11-16 | 1995-07-25 | Automated Systems And Programming, Inc. | Method and system for optimization of telephone contact campaigns |
US5570417A (en) * | 1995-03-28 | 1996-10-29 | Lucent Technologies Inc. | System for automatically providing customer access to alternative telephony service providers |
US5592470A (en) * | 1994-12-21 | 1997-01-07 | At&T | Broadband wireless system and network architecture providing broadband/narrowband service with optimal static and dynamic bandwidth/channel allocation |
US5608786A (en) * | 1994-12-23 | 1997-03-04 | Alphanet Telecom Inc. | Unified messaging system and method |
US5644624A (en) * | 1994-05-23 | 1997-07-01 | Caldwell Communications Development, Inc. | Automatic telephone call origination and retry system and method of operation |
US5661783A (en) * | 1996-05-22 | 1997-08-26 | Assis; Offer | Electronic secretary |
US5708775A (en) * | 1995-04-19 | 1998-01-13 | Fuji Xerox Co., Ltd. | Fault information notification system localized at each network server |
US5802510A (en) * | 1995-12-29 | 1998-09-01 | At&T Corp | Universal directory service |
US5812654A (en) * | 1992-01-27 | 1998-09-22 | Sprint Communications Co. L.P. | Telecommunications network routing |
US5818447A (en) * | 1996-06-06 | 1998-10-06 | Microsoft Corporation | System and method for in-place editing of an electronic mail message using a separate program |
US5909589A (en) * | 1996-11-12 | 1999-06-01 | Lance T. Parker | Internet based training |
US5943417A (en) * | 1994-04-28 | 1999-08-24 | Metro One Telecommunications, Inc. | Method and system for personalized directory assistance services |
US5946386A (en) * | 1996-03-11 | 1999-08-31 | Xantel Corporation | Call management system with call control from user workstation computers |
US6052730A (en) * | 1997-01-10 | 2000-04-18 | The Board Of Trustees Of The Leland Stanford Junior University | Method for monitoring and/or modifying web browsing sessions |
US6055512A (en) * | 1997-07-08 | 2000-04-25 | Nortel Networks Corporation | Networked personal customized information and facility services |
US6065047A (en) * | 1996-01-24 | 2000-05-16 | America Online, Inc. | System for providing subscriber with access to a content area customized for the combination of subscriber's responses to topic prompt, subtopic prompt, and action prompt |
US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
US6134235A (en) * | 1997-10-08 | 2000-10-17 | At&T Corp. | Pots/packet bridge |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6205211B1 (en) * | 1998-08-04 | 2001-03-20 | Transnexus, Llc | Internet telephony call pricing center |
US6208721B1 (en) * | 1999-01-22 | 2001-03-27 | Lucent Technologies Inc. | Method and apparatus for identifying telephone callers who have been unsuccessful in reaching a called destination |
US6216104B1 (en) * | 1998-02-20 | 2001-04-10 | Philips Electronics North America Corporation | Computer-based patient record and message delivery system |
US6233317B1 (en) * | 1997-12-11 | 2001-05-15 | Unisys Corporation | Multiple language electronic mail notification of received voice and/or fax messages |
US6237027B1 (en) * | 1996-06-20 | 2001-05-22 | Sony Corporation | Electronic mail system, computer device, and remote notification method |
US6247043B1 (en) * | 1998-06-11 | 2001-06-12 | International Business Machines Corporation | Apparatus, program products and methods utilizing intelligent contact management |
US6266690B1 (en) * | 1999-01-27 | 2001-07-24 | Adc Telecommunications, Inc. | Enhanced service platform with secure system and method for subscriber profile customization |
US6272537B1 (en) * | 1997-11-17 | 2001-08-07 | Fujitsu Limited | Method for building element manager for a computer network element using a visual element manager builder process |
US6272150B1 (en) * | 1997-01-17 | 2001-08-07 | Scientific-Atlanta, Inc. | Cable modem map display for network management of a cable data delivery system |
US6282275B1 (en) * | 1998-08-07 | 2001-08-28 | Lucent Technologies Inc. | Telephone caller identification log with internet access |
US6301245B1 (en) * | 1998-06-09 | 2001-10-09 | Unisys Corporation | Universal Messaging system providing integrated voice, data and fax messaging services to PC/web-based clients, including a large object server for efficiently distributing voice/fax messages to web-based clients |
US6308328B1 (en) * | 1997-01-17 | 2001-10-23 | Scientific-Atlanta, Inc. | Usage statistics collection for a cable data delivery system |
US6338066B1 (en) * | 1998-09-25 | 2002-01-08 | International Business Machines Corporation | Surfaid predictor: web-based system for predicting surfer behavior |
US6345239B1 (en) * | 1999-08-31 | 2002-02-05 | Accenture Llp | Remote demonstration of business capabilities in an e-commerce environment |
US6351771B1 (en) * | 1997-11-10 | 2002-02-26 | Nortel Networks Limited | Distributed service network system capable of transparently converting data formats and selectively connecting to an appropriate bridge in accordance with clients characteristics identified during preliminary connections |
US6353852B1 (en) * | 1999-01-27 | 2002-03-05 | Adc Telecommunications, Inc. | Enhanced telephone service system with secure system and method for E-mail address registration |
US6360254B1 (en) * | 1998-09-15 | 2002-03-19 | Amazon.Com Holdings, Inc. | System and method for providing secure URL-based access to private resources |
US6404762B1 (en) * | 1998-06-09 | 2002-06-11 | Unisys Corporation | Universal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a session manager for maintaining a session between a messaging platform and the web-based clients |
US20020073142A1 (en) * | 2000-12-11 | 2002-06-13 | Thomas Moran | Messaging |
US20020078161A1 (en) * | 2000-12-19 | 2002-06-20 | Philips Electronics North America Corporation | UPnP enabling device for heterogeneous networks of slave devices |
US20020078151A1 (en) * | 2000-12-15 | 2002-06-20 | Wickam Bryce C. | System for communicating messages of various formats between diverse communication devices |
US6421725B1 (en) * | 2000-05-04 | 2002-07-16 | Worldcom, Inc. | Method and apparatus for providing automatic notification |
US6424966B1 (en) * | 1998-06-30 | 2002-07-23 | Microsoft Corporation | Synchronizing crawler with notification source |
US6424995B1 (en) * | 1996-10-16 | 2002-07-23 | Microsoft Corporation | Method for displaying information contained in an electronic message |
US20020099775A1 (en) * | 2001-01-25 | 2002-07-25 | Anoop Gupta | Server system supporting collaborative messaging based on electronic mail |
US20020099777A1 (en) * | 2001-01-25 | 2002-07-25 | Anoop Gupta | Integrating collaborative messaging into an electronic mail program |
US20020099776A1 (en) * | 2001-01-24 | 2002-07-25 | Cafarella Michael J. | Method and system for providing interactive telephony sessions |
US6430188B1 (en) * | 1998-07-08 | 2002-08-06 | Broadcom Corporation | Unified table for L2, L3, L4, switching and filtering |
US6430177B1 (en) * | 1998-06-09 | 2002-08-06 | Unisys Corporation | Universal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a content manager for receiving information from content providers and formatting the same into multimedia containers for distribution to web-based clients |
US6434747B1 (en) * | 2000-01-19 | 2002-08-13 | Individual Network, Inc. | Method and system for providing a customized media list |
US20020111813A1 (en) * | 2001-02-13 | 2002-08-15 | Capps Stephan P. | System and method for providing a universal and automatic communication access point |
US6453353B1 (en) * | 1998-07-10 | 2002-09-17 | Entrust, Inc. | Role-based navigation of information resources |
US6515968B1 (en) * | 1995-03-17 | 2003-02-04 | Worldcom, Inc. | Integrated interface for real time web based viewing of telecommunications network call traffic |
US6518984B1 (en) * | 1998-08-26 | 2003-02-11 | Apple Computer, Inc. | Record range control for browsing published databases |
US6526044B1 (en) * | 1999-06-29 | 2003-02-25 | Wandel & Goltermann Technologies, Inc. | Real-time analysis through capture buffer with real-time historical data correlation |
US6529954B1 (en) * | 1999-06-29 | 2003-03-04 | Wandell & Goltermann Technologies, Inc. | Knowledge based expert analysis system |
US6535585B1 (en) * | 2000-03-30 | 2003-03-18 | Worldcom, Inc. | System and method for notification upon successful message delivery |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6570885B1 (en) * | 1999-11-12 | 2003-05-27 | International Business Machines Corporation | Segment-controlled process for controlling castouts from a communication cache in a port in any of multiple nodes in a communications network |
US20030156134A1 (en) * | 2000-12-08 | 2003-08-21 | Kyunam Kim | Graphic chatting with organizational avatars |
US6631186B1 (en) * | 1999-04-09 | 2003-10-07 | Sbc Technology Resources, Inc. | System and method for implementing and accessing call forwarding services |
US6640241B1 (en) * | 1999-07-19 | 2003-10-28 | Groove Networks, Inc. | Method and apparatus for activity-based collaboration by a computer system equipped with a communications manager |
US6701348B2 (en) * | 2000-12-22 | 2004-03-02 | Goodcontacts.Com | Method and system for automatically updating contact information within a contact database |
US6731927B1 (en) * | 2000-07-14 | 2004-05-04 | Context Connect, Inc. | System and method for context association |
US6738462B1 (en) * | 2000-07-19 | 2004-05-18 | Avaya Technology Corp. | Unified communications automated personal name addressing |
US6745229B1 (en) * | 1997-09-26 | 2004-06-01 | Worldcom, Inc. | Web based integrated customer interface for invoice reporting |
US6757732B1 (en) * | 2000-03-16 | 2004-06-29 | Nortel Networks Limited | Text-based communications over a data network |
US6766369B1 (en) * | 1998-03-09 | 2004-07-20 | Net Zero, Inc. | Internet service error tracking |
US6768722B1 (en) * | 2000-06-23 | 2004-07-27 | At&T Corp. | Systems and methods for managing multiple communications |
US6772188B1 (en) * | 2000-07-14 | 2004-08-03 | America Online, Incorporated | Method and apparatus for communicating with an entity automatically identified in an electronic communication |
US6782086B2 (en) * | 2001-08-02 | 2004-08-24 | Intel Corporation | Caller ID lookup |
US6785379B1 (en) * | 1999-06-28 | 2004-08-31 | Aspect Communications Corporation | Call management system with call control form user workstation computers |
US6788926B1 (en) * | 1999-03-17 | 2004-09-07 | Telephia, Inc. | System and method for gathering data from wireless communications networks |
US6804716B1 (en) * | 1999-12-22 | 2004-10-12 | Bellsouth Intellectual Property Corporation | Network and method for call management |
US6804707B1 (en) * | 2000-10-20 | 2004-10-12 | Eric Ronning | Method and system for delivering wireless messages and information to personal computing devices |
US20050038863A1 (en) * | 2003-07-21 | 2005-02-17 | Richard Onyon | Device message management system |
US6879995B1 (en) * | 1999-08-13 | 2005-04-12 | Sun Microsystems, Inc. | Application server message logging |
US6895559B2 (en) * | 2000-12-12 | 2005-05-17 | Matsushita Mobile Communications Development Corporation Of U.S.A. | Auto-completion algorithm for dialing telephone numbers |
US20050149487A1 (en) * | 1998-10-01 | 2005-07-07 | Feyzi Celik | Method and apparatus for storing and retrieving business contact information in a computer system |
US6917610B1 (en) * | 1999-12-30 | 2005-07-12 | At&T Corp. | Activity log for improved call efficiency |
US6920208B1 (en) * | 2002-05-03 | 2005-07-19 | At&T Corp. | Call tracker |
US6928154B1 (en) * | 1999-02-26 | 2005-08-09 | Nortel Networks Limited | Remote caller identification telephone system and method with internet retrieval |
US6940958B2 (en) * | 2001-08-02 | 2005-09-06 | Intel Corporation | Forwarding telephone data via email |
US6948135B1 (en) * | 2000-06-21 | 2005-09-20 | Microsoft Corporation | Method and systems of providing information to computer users |
US6947979B1 (en) * | 2000-08-16 | 2005-09-20 | Entrust, Inc. | Controlling use of a network resource |
US6988128B1 (en) * | 2000-09-27 | 2006-01-17 | International Business Machines Corporation | Calendar events and calendar-driven application technique |
US7088805B1 (en) * | 2002-09-24 | 2006-08-08 | Bellsouth Intellectual Property Corporation | Method for polling a call log |
US7096232B2 (en) * | 2001-06-06 | 2006-08-22 | International Business Machines Corporation | Calendar-enhanced directory searches including dynamic contact information |
US7107275B2 (en) * | 1999-06-15 | 2006-09-12 | Microsoft Corporation | Edit command delegation program for editing electronic files |
Family Cites Families (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4969136A (en) * | 1986-08-08 | 1990-11-06 | Chamberlin David B | Communications network and method with appointment information communication capabilities |
US4975896A (en) * | 1986-08-08 | 1990-12-04 | Agosto Iii Nicholas A D | Communications network and method |
WO1997049251A1 (en) * | 1996-06-18 | 1997-12-24 | Compuserve Incorporated | Integrated voice, facsimile and electronic mail messaging system |
US6754181B1 (en) * | 1996-11-18 | 2004-06-22 | Mci Communications Corporation | System and method for a directory service supporting a hybrid communication system architecture |
US6167119A (en) | 1997-03-28 | 2000-12-26 | Bell Atlantic Network Services, Inc. | Providing enhanced services through SIV and personal dial tone |
US6014135A (en) | 1997-04-04 | 2000-01-11 | Netscape Communications Corp. | Collaboration centric document processing environment using an information centric visual user interface and information presentation method |
FR2762465A1 (en) * | 1997-04-22 | 1998-10-23 | Philips Electronics Nv | TELECOMMUNICATIONS EQUIPMENT, SYSTEM AND METHOD WITH MEANS FOR MANAGING SUBSCRIBER RECALL LIST |
US5987100A (en) | 1997-04-23 | 1999-11-16 | Northern Telecom Limited | Universal mailbox |
AU8496398A (en) | 1997-07-18 | 1999-02-10 | Net Exchange, Inc. | Apparatus and method for effecting correspondent-centric electronic mail |
US5978475A (en) | 1997-07-18 | 1999-11-02 | Counterpane Internet Security, Inc. | Event auditing system |
US6330079B1 (en) | 1997-09-08 | 2001-12-11 | Mci Communications Corporation | Integrated voicemail and faxmail platform for a communications system |
US6151584A (en) | 1997-11-20 | 2000-11-21 | Ncr Corporation | Computer architecture and method for validating and collecting and metadata and data about the internet and electronic commerce environments (data discoverer) |
US6169997B1 (en) * | 1998-04-29 | 2001-01-02 | Ncr Corporation | Method and apparatus for forming subject (context) map and presenting Internet data according to the subject map |
US6556666B1 (en) * | 1998-05-05 | 2003-04-29 | Siemens Information & Communication Networks, Inc. | Notification system for multimedia messaging systems |
US6735286B1 (en) * | 1998-05-29 | 2004-05-11 | Nortel Networks Limited | Telephone system integrated text based communication processes, apparatus and systems |
US6317485B1 (en) | 1998-06-09 | 2001-11-13 | Unisys Corporation | System and method for integrating notification functions of two messaging systems in a universal messaging system |
US6148329A (en) | 1998-07-20 | 2000-11-14 | Unisys Corporation | Method and system for maintaining the format of messages in a messaging system database |
BR9913963A (en) | 1998-09-15 | 2003-04-01 | In Touch Technologies Ltd | Enhanced communication platform and related communication method using the platform |
US6806977B1 (en) * | 1998-12-31 | 2004-10-19 | Automated Business Companies | Multiple integrated machine system |
US20010013050A1 (en) * | 1999-01-11 | 2001-08-09 | Shah Niraj A. | Buddy list aggregation |
US20010013069A1 (en) * | 1999-01-11 | 2001-08-09 | Infospace, Inc. | Data messaging aggregation |
US6711154B1 (en) | 1999-01-29 | 2004-03-23 | Microsoft Corporation | Apparatus and method for device independent messaging notification |
US6411685B1 (en) | 1999-01-29 | 2002-06-25 | Microsoft Corporation | System and method for providing unified messaging to a user with a thin web browser |
US6594255B1 (en) * | 1999-02-09 | 2003-07-15 | Tadiran Telecom Business Systems Ltd. | PBX with short messaging service on a telephone display |
US6981023B1 (en) | 1999-03-09 | 2005-12-27 | Michael Hamilton | Message routing |
US6820204B1 (en) * | 1999-03-31 | 2004-11-16 | Nimesh Desai | System and method for selective information exchange |
US6882709B1 (en) | 1999-04-14 | 2005-04-19 | General Instrument Corporation | Enhanced broadband telephony services |
US6747970B1 (en) * | 1999-04-29 | 2004-06-08 | Christopher H. Lamb | Methods and apparatus for providing communications services between connectionless and connection-oriented networks |
WO2000072285A1 (en) * | 1999-05-24 | 2000-11-30 | Heat-Timer Corporation | Electronic message delivery system utilizable in the monitoring oe remote equipment and method of same |
US6147975A (en) | 1999-06-02 | 2000-11-14 | Ac Properties B.V. | System, method and article of manufacture of a proactive threhold manager in a hybrid communication system architecture |
US6857024B1 (en) | 1999-10-22 | 2005-02-15 | Cisco Technology, Inc. | System and method for providing on-line advertising and information |
US20020091829A1 (en) | 2000-02-22 | 2002-07-11 | Wood Christopher (Noah) | Internet message management portal |
US6760601B1 (en) | 1999-11-29 | 2004-07-06 | Nokia Corporation | Apparatus for providing information services to a telecommunication device user |
US6807423B1 (en) * | 1999-12-14 | 2004-10-19 | Nortel Networks Limited | Communication and presence spanning multiple access networks |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6496838B1 (en) * | 1999-12-31 | 2002-12-17 | Qwest Communications International Inc. | Database reconciliation method and system |
WO2001050693A1 (en) | 2000-01-05 | 2001-07-12 | Www.Internet Solutions Limited | Messaging system |
AU2001230955A1 (en) | 2000-01-18 | 2001-07-31 | Richard Liming | System and method providing a spatial location context |
US7062535B1 (en) | 2000-04-03 | 2006-06-13 | Centerpost Communications, Inc. | Individual XML message processing platform |
US20020069048A1 (en) * | 2000-04-07 | 2002-06-06 | Sadhwani Deepak Kishinchand | Communication system |
JP2001290767A (en) | 2000-04-07 | 2001-10-19 | Sharp Corp | Information communication system, information terminal device, and program recording medium |
US6493437B1 (en) | 2000-04-26 | 2002-12-10 | Genuity Inc. | Advertising-subsidized PC-telephony |
US6973556B2 (en) * | 2000-06-19 | 2005-12-06 | Storage Technology Corporation | Data element including metadata that includes data management information for managing the data element |
US6829233B1 (en) | 2000-07-26 | 2004-12-07 | At&T Corp. | Internet telephony with interactive information |
US6665378B1 (en) * | 2000-07-31 | 2003-12-16 | Brenda Gates Spielman | IP-based notification architecture for unified messaging |
US6748056B1 (en) | 2000-08-11 | 2004-06-08 | Unisys Corporation | Coordination of a telephony handset session with an e-mail session in a universal messaging system |
US20030009530A1 (en) * | 2000-11-08 | 2003-01-09 | Laurent Philonenko | Instant message presence protocol for facilitating communication center activity |
US20020194274A1 (en) | 2000-12-23 | 2002-12-19 | Atub, Inc. | System, method and article of manufacture for a communication manager in an integrated scheduling and document management framework |
US6981223B2 (en) | 2001-03-19 | 2005-12-27 | Ecrio, Inc. | Method, apparatus and computer readable medium for multiple messaging session management with a graphical user interface |
US6763102B1 (en) | 2001-04-05 | 2004-07-13 | At&T Corp. | Method for handling incoming calls directed to a virtual communication service subscriber via a guest PBX |
US20020174188A1 (en) | 2001-04-30 | 2002-11-21 | Objectsoft, Inc. | Method and apparatus for exchanging contact information |
US7849409B2 (en) | 2001-05-31 | 2010-12-07 | Access Systems Americas, Inc. | System and method for transferring Web-based information |
US7835934B2 (en) * | 2003-05-21 | 2010-11-16 | Warranty Management Technologies LLC | System and method of work management |
-
2002
- 2002-03-29 US US10/109,909 patent/US7007085B1/en not_active Expired - Lifetime
-
2005
- 2005-09-28 US US11/236,907 patent/US7441027B2/en not_active Expired - Lifetime
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US623027A (en) * | 1899-04-11 | Displaying device | ||
US631186A (en) * | 1898-04-08 | 1899-08-15 | George R Sherwood | Machine for removing pith from cornstalks. |
US676872A (en) * | 1900-05-22 | 1901-06-25 | Peter M Buckland | Feed-water regulator. |
US4706242A (en) * | 1985-03-28 | 1987-11-10 | Stc Plc | Digital telecommunication system |
US4935954A (en) * | 1988-12-28 | 1990-06-19 | At&T Company | Automated message retrieval system |
US5812654A (en) * | 1992-01-27 | 1998-09-22 | Sprint Communications Co. L.P. | Telecommunications network routing |
US5311583A (en) * | 1992-08-05 | 1994-05-10 | At&T Bell Laboratories | International priority calling system with callback features |
US5889799A (en) * | 1993-11-16 | 1999-03-30 | Centerforce Technologies, Inc. | Method and system for optimization of telephone contact campaigns |
US5621790A (en) * | 1993-11-16 | 1997-04-15 | Aspi Software Development Company , Llc | Method and system for optimization of telephone contact campaigns |
US5436965A (en) * | 1993-11-16 | 1995-07-25 | Automated Systems And Programming, Inc. | Method and system for optimization of telephone contact campaigns |
US5943417A (en) * | 1994-04-28 | 1999-08-24 | Metro One Telecommunications, Inc. | Method and system for personalized directory assistance services |
US5966437A (en) * | 1994-04-28 | 1999-10-12 | Metro One Telecommunications, Inc. | Method and system for personalized directory assistance services |
US5644624A (en) * | 1994-05-23 | 1997-07-01 | Caldwell Communications Development, Inc. | Automatic telephone call origination and retry system and method of operation |
US5592470A (en) * | 1994-12-21 | 1997-01-07 | At&T | Broadband wireless system and network architecture providing broadband/narrowband service with optimal static and dynamic bandwidth/channel allocation |
US5608786A (en) * | 1994-12-23 | 1997-03-04 | Alphanet Telecom Inc. | Unified messaging system and method |
US6515968B1 (en) * | 1995-03-17 | 2003-02-04 | Worldcom, Inc. | Integrated interface for real time web based viewing of telecommunications network call traffic |
US5570417A (en) * | 1995-03-28 | 1996-10-29 | Lucent Technologies Inc. | System for automatically providing customer access to alternative telephony service providers |
US5708775A (en) * | 1995-04-19 | 1998-01-13 | Fuji Xerox Co., Ltd. | Fault information notification system localized at each network server |
US5802510A (en) * | 1995-12-29 | 1998-09-01 | At&T Corp | Universal directory service |
US6065047A (en) * | 1996-01-24 | 2000-05-16 | America Online, Inc. | System for providing subscriber with access to a content area customized for the combination of subscriber's responses to topic prompt, subtopic prompt, and action prompt |
US5946386A (en) * | 1996-03-11 | 1999-08-31 | Xantel Corporation | Call management system with call control from user workstation computers |
US5661783A (en) * | 1996-05-22 | 1997-08-26 | Assis; Offer | Electronic secretary |
US5818447A (en) * | 1996-06-06 | 1998-10-06 | Microsoft Corporation | System and method for in-place editing of an electronic mail message using a separate program |
US6237027B1 (en) * | 1996-06-20 | 2001-05-22 | Sony Corporation | Electronic mail system, computer device, and remote notification method |
US6424995B1 (en) * | 1996-10-16 | 2002-07-23 | Microsoft Corporation | Method for displaying information contained in an electronic message |
US6708202B1 (en) * | 1996-10-16 | 2004-03-16 | Microsoft Corporation | Method for highlighting information contained in an electronic message |
US5909589A (en) * | 1996-11-12 | 1999-06-01 | Lance T. Parker | Internet based training |
US6052730A (en) * | 1997-01-10 | 2000-04-18 | The Board Of Trustees Of The Leland Stanford Junior University | Method for monitoring and/or modifying web browsing sessions |
US6308328B1 (en) * | 1997-01-17 | 2001-10-23 | Scientific-Atlanta, Inc. | Usage statistics collection for a cable data delivery system |
US6272150B1 (en) * | 1997-01-17 | 2001-08-07 | Scientific-Atlanta, Inc. | Cable modem map display for network management of a cable data delivery system |
US6055512A (en) * | 1997-07-08 | 2000-04-25 | Nortel Networks Corporation | Networked personal customized information and facility services |
US6745229B1 (en) * | 1997-09-26 | 2004-06-01 | Worldcom, Inc. | Web based integrated customer interface for invoice reporting |
US6134235A (en) * | 1997-10-08 | 2000-10-17 | At&T Corp. | Pots/packet bridge |
US6351771B1 (en) * | 1997-11-10 | 2002-02-26 | Nortel Networks Limited | Distributed service network system capable of transparently converting data formats and selectively connecting to an appropriate bridge in accordance with clients characteristics identified during preliminary connections |
US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
US6272537B1 (en) * | 1997-11-17 | 2001-08-07 | Fujitsu Limited | Method for building element manager for a computer network element using a visual element manager builder process |
US6233317B1 (en) * | 1997-12-11 | 2001-05-15 | Unisys Corporation | Multiple language electronic mail notification of received voice and/or fax messages |
US6216104B1 (en) * | 1998-02-20 | 2001-04-10 | Philips Electronics North America Corporation | Computer-based patient record and message delivery system |
US6766369B1 (en) * | 1998-03-09 | 2004-07-20 | Net Zero, Inc. | Internet service error tracking |
US6301245B1 (en) * | 1998-06-09 | 2001-10-09 | Unisys Corporation | Universal Messaging system providing integrated voice, data and fax messaging services to PC/web-based clients, including a large object server for efficiently distributing voice/fax messages to web-based clients |
US6430177B1 (en) * | 1998-06-09 | 2002-08-06 | Unisys Corporation | Universal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a content manager for receiving information from content providers and formatting the same into multimedia containers for distribution to web-based clients |
US6404762B1 (en) * | 1998-06-09 | 2002-06-11 | Unisys Corporation | Universal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a session manager for maintaining a session between a messaging platform and the web-based clients |
US6247043B1 (en) * | 1998-06-11 | 2001-06-12 | International Business Machines Corporation | Apparatus, program products and methods utilizing intelligent contact management |
US6424966B1 (en) * | 1998-06-30 | 2002-07-23 | Microsoft Corporation | Synchronizing crawler with notification source |
US6430188B1 (en) * | 1998-07-08 | 2002-08-06 | Broadcom Corporation | Unified table for L2, L3, L4, switching and filtering |
US6453353B1 (en) * | 1998-07-10 | 2002-09-17 | Entrust, Inc. | Role-based navigation of information resources |
US6182142B1 (en) * | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6205211B1 (en) * | 1998-08-04 | 2001-03-20 | Transnexus, Llc | Internet telephony call pricing center |
US6282275B1 (en) * | 1998-08-07 | 2001-08-28 | Lucent Technologies Inc. | Telephone caller identification log with internet access |
US6518984B1 (en) * | 1998-08-26 | 2003-02-11 | Apple Computer, Inc. | Record range control for browsing published databases |
US6360254B1 (en) * | 1998-09-15 | 2002-03-19 | Amazon.Com Holdings, Inc. | System and method for providing secure URL-based access to private resources |
US6338066B1 (en) * | 1998-09-25 | 2002-01-08 | International Business Machines Corporation | Surfaid predictor: web-based system for predicting surfer behavior |
US20050149487A1 (en) * | 1998-10-01 | 2005-07-07 | Feyzi Celik | Method and apparatus for storing and retrieving business contact information in a computer system |
US6208721B1 (en) * | 1999-01-22 | 2001-03-27 | Lucent Technologies Inc. | Method and apparatus for identifying telephone callers who have been unsuccessful in reaching a called destination |
US6266690B1 (en) * | 1999-01-27 | 2001-07-24 | Adc Telecommunications, Inc. | Enhanced service platform with secure system and method for subscriber profile customization |
US6353852B1 (en) * | 1999-01-27 | 2002-03-05 | Adc Telecommunications, Inc. | Enhanced telephone service system with secure system and method for E-mail address registration |
US6928154B1 (en) * | 1999-02-26 | 2005-08-09 | Nortel Networks Limited | Remote caller identification telephone system and method with internet retrieval |
US6788926B1 (en) * | 1999-03-17 | 2004-09-07 | Telephia, Inc. | System and method for gathering data from wireless communications networks |
US6631186B1 (en) * | 1999-04-09 | 2003-10-07 | Sbc Technology Resources, Inc. | System and method for implementing and accessing call forwarding services |
US6564261B1 (en) * | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US7107275B2 (en) * | 1999-06-15 | 2006-09-12 | Microsoft Corporation | Edit command delegation program for editing electronic files |
US6785379B1 (en) * | 1999-06-28 | 2004-08-31 | Aspect Communications Corporation | Call management system with call control form user workstation computers |
US6526044B1 (en) * | 1999-06-29 | 2003-02-25 | Wandel & Goltermann Technologies, Inc. | Real-time analysis through capture buffer with real-time historical data correlation |
US6529954B1 (en) * | 1999-06-29 | 2003-03-04 | Wandell & Goltermann Technologies, Inc. | Knowledge based expert analysis system |
US6640241B1 (en) * | 1999-07-19 | 2003-10-28 | Groove Networks, Inc. | Method and apparatus for activity-based collaboration by a computer system equipped with a communications manager |
US6879995B1 (en) * | 1999-08-13 | 2005-04-12 | Sun Microsystems, Inc. | Application server message logging |
US6345239B1 (en) * | 1999-08-31 | 2002-02-05 | Accenture Llp | Remote demonstration of business capabilities in an e-commerce environment |
US6570885B1 (en) * | 1999-11-12 | 2003-05-27 | International Business Machines Corporation | Segment-controlled process for controlling castouts from a communication cache in a port in any of multiple nodes in a communications network |
US6804716B1 (en) * | 1999-12-22 | 2004-10-12 | Bellsouth Intellectual Property Corporation | Network and method for call management |
US6917610B1 (en) * | 1999-12-30 | 2005-07-12 | At&T Corp. | Activity log for improved call efficiency |
US6434747B1 (en) * | 2000-01-19 | 2002-08-13 | Individual Network, Inc. | Method and system for providing a customized media list |
US6757732B1 (en) * | 2000-03-16 | 2004-06-29 | Nortel Networks Limited | Text-based communications over a data network |
US6535585B1 (en) * | 2000-03-30 | 2003-03-18 | Worldcom, Inc. | System and method for notification upon successful message delivery |
US6421725B1 (en) * | 2000-05-04 | 2002-07-16 | Worldcom, Inc. | Method and apparatus for providing automatic notification |
US6948135B1 (en) * | 2000-06-21 | 2005-09-20 | Microsoft Corporation | Method and systems of providing information to computer users |
US6768722B1 (en) * | 2000-06-23 | 2004-07-27 | At&T Corp. | Systems and methods for managing multiple communications |
US6731927B1 (en) * | 2000-07-14 | 2004-05-04 | Context Connect, Inc. | System and method for context association |
US6772188B1 (en) * | 2000-07-14 | 2004-08-03 | America Online, Incorporated | Method and apparatus for communicating with an entity automatically identified in an electronic communication |
US6738462B1 (en) * | 2000-07-19 | 2004-05-18 | Avaya Technology Corp. | Unified communications automated personal name addressing |
US6947979B1 (en) * | 2000-08-16 | 2005-09-20 | Entrust, Inc. | Controlling use of a network resource |
US6988128B1 (en) * | 2000-09-27 | 2006-01-17 | International Business Machines Corporation | Calendar events and calendar-driven application technique |
US6804707B1 (en) * | 2000-10-20 | 2004-10-12 | Eric Ronning | Method and system for delivering wireless messages and information to personal computing devices |
US6910186B2 (en) * | 2000-12-08 | 2005-06-21 | Kyunam Kim | Graphic chatting with organizational avatars |
US20030156134A1 (en) * | 2000-12-08 | 2003-08-21 | Kyunam Kim | Graphic chatting with organizational avatars |
US20020073142A1 (en) * | 2000-12-11 | 2002-06-13 | Thomas Moran | Messaging |
US6895559B2 (en) * | 2000-12-12 | 2005-05-17 | Matsushita Mobile Communications Development Corporation Of U.S.A. | Auto-completion algorithm for dialing telephone numbers |
US20020078151A1 (en) * | 2000-12-15 | 2002-06-20 | Wickam Bryce C. | System for communicating messages of various formats between diverse communication devices |
US20020078161A1 (en) * | 2000-12-19 | 2002-06-20 | Philips Electronics North America Corporation | UPnP enabling device for heterogeneous networks of slave devices |
US6701348B2 (en) * | 2000-12-22 | 2004-03-02 | Goodcontacts.Com | Method and system for automatically updating contact information within a contact database |
US20020099776A1 (en) * | 2001-01-24 | 2002-07-25 | Cafarella Michael J. | Method and system for providing interactive telephony sessions |
US20020099777A1 (en) * | 2001-01-25 | 2002-07-25 | Anoop Gupta | Integrating collaborative messaging into an electronic mail program |
US20020099775A1 (en) * | 2001-01-25 | 2002-07-25 | Anoop Gupta | Server system supporting collaborative messaging based on electronic mail |
US20020111813A1 (en) * | 2001-02-13 | 2002-08-15 | Capps Stephan P. | System and method for providing a universal and automatic communication access point |
US7096232B2 (en) * | 2001-06-06 | 2006-08-22 | International Business Machines Corporation | Calendar-enhanced directory searches including dynamic contact information |
US6940958B2 (en) * | 2001-08-02 | 2005-09-06 | Intel Corporation | Forwarding telephone data via email |
US6782086B2 (en) * | 2001-08-02 | 2004-08-24 | Intel Corporation | Caller ID lookup |
US6920208B1 (en) * | 2002-05-03 | 2005-07-19 | At&T Corp. | Call tracker |
US7088805B1 (en) * | 2002-09-24 | 2006-08-08 | Bellsouth Intellectual Property Corporation | Method for polling a call log |
US20050038863A1 (en) * | 2003-07-21 | 2005-02-17 | Richard Onyon | Device message management system |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100198927A1 (en) * | 2006-08-16 | 2010-08-05 | Tonnison James I | Enhanced Email System |
US20080162648A1 (en) * | 2006-12-29 | 2008-07-03 | Wang Kai Benson Leung | Device and method of expressing information contained in a communication message sent through a network |
US20080273686A1 (en) * | 2007-05-01 | 2008-11-06 | Unison Technologies Llc | Systems and methods for scalable hunt-group management |
US7738650B2 (en) | 2007-05-01 | 2010-06-15 | Unison Technologies, Inc. | Systems and methods for scalable hunt-group management |
US20090067595A1 (en) * | 2007-05-01 | 2009-03-12 | Unison Technologies Llc | Systems and methods for phone call management |
US20090041052A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with user selectable reply format |
US7783023B2 (en) | 2007-05-16 | 2010-08-24 | Unison Technologies, Inc. | Systems and methods for providing unified collaboration systems with conditional communication handling |
US20090041216A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with conditional communication handling |
US20090041217A1 (en) * | 2007-05-16 | 2009-02-12 | Unison Technologies Llc | Systems and methods for providing unified collaboration systems with combined communication log |
US20090119368A1 (en) * | 2007-11-02 | 2009-05-07 | International Business Machines Corporation | System and method for gathering conversation information |
US8650255B2 (en) | 2008-12-31 | 2014-02-11 | International Business Machines Corporation | System and method for joining a conversation |
US20100235223A1 (en) * | 2009-03-16 | 2010-09-16 | Lyman Christopher M | System and method for automatic insertion of call intelligence in an information system |
US10318922B2 (en) * | 2009-03-16 | 2019-06-11 | Fonality, Inc. | System and method for automatic insertion of call intelligence in an information system |
US11501254B2 (en) | 2009-03-16 | 2022-11-15 | Sangoma Us Inc. | System and method for automatic insertion of call intelligence in an information system |
US11223720B2 (en) | 2009-03-16 | 2022-01-11 | Fonality, Inc. | System and method for utilizing customer data in a communication system |
US11113663B2 (en) | 2009-03-16 | 2021-09-07 | Fonality, Inc. | System and method for automatic insertion of call intelligence in an information system |
US9955004B2 (en) | 2009-03-16 | 2018-04-24 | Fonality, Inc. | System and method for utilizing customer data in a communication system |
US10834254B2 (en) | 2009-03-16 | 2020-11-10 | Fonality, Inc. | System and method for utilizing customer data in a communication system |
US20160259601A1 (en) * | 2013-10-25 | 2016-09-08 | Next Print Technologies Aps | Method of handling a print job submitted to a cloud printing service for processing by an authenticated printing system and system for performing the method |
US10001955B2 (en) * | 2013-10-25 | 2018-06-19 | Next Print Technologies Aps | Method of handling a print job submitted to a cloud printing service, and associated user credentials, for processing by an authenticated printing system and system for performing the method |
US9983835B2 (en) * | 2013-10-25 | 2018-05-29 | Next Print Technologies Aps | Method, performed by a server interposed between a user device and an authenticated printing system, of handling a guest print job for processing by the authenticated printing system and system for performing the method |
US9870479B2 (en) * | 2013-10-25 | 2018-01-16 | Next Print Technologies Aps | Method of handling a document stored in a cloud storage system and associated user credentials for processing by an authenticated printing system and system for performing the method |
US20160267282A1 (en) * | 2013-10-25 | 2016-09-15 | Next Print Technologies Aps | Method of handling a document stored in a cloud storage system for processing by an authenticated printing system and system for performing the method |
US20160259602A1 (en) * | 2013-10-25 | 2016-09-08 | Next Print Technologies Aps | Method of handling a guest print job for processing by an authenticated printing system and system for performing the method |
US10831765B1 (en) * | 2014-10-21 | 2020-11-10 | Zoosk, Inc. | System and method for providing information about users who performed internet-based activities |
US11386098B1 (en) * | 2014-10-21 | 2022-07-12 | Zoosk, Inc. | System and method for providing information about users who performed internet-based activities |
US11809437B1 (en) * | 2014-10-21 | 2023-11-07 | Zoosk, Inc. | System and method for providing information about users who performed internet-based activities |
Also Published As
Publication number | Publication date |
---|---|
US7441027B2 (en) | 2008-10-21 |
US7007085B1 (en) | 2006-02-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7007085B1 (en) | Message log for wireline, voice mail, email, fax, pager, instant messages and chat | |
US10902466B2 (en) | Methods and systems for a communications and information resource manager | |
US9723460B1 (en) | Device message management system | |
US7593925B2 (en) | Method and system for locating contact information collected from contact sources | |
US7562104B2 (en) | Method and system for collecting contact information from contact sources and tracking contact sources | |
US8560673B2 (en) | Methods, systems and products for presenting information correlated to communications | |
EP0782315B1 (en) | Universal directory service | |
US7978828B1 (en) | Methods and apparatus for multimedia tracking | |
US20090067592A1 (en) | Method And System For Associating Related Messages Of Different Types | |
US20060195472A1 (en) | Method and system for aggregating contact information from multiple contact sources | |
JPH09233118A (en) | General-purpose message storage system | |
JPH09219724A (en) | General-purpose message transmission system | |
US20050276397A1 (en) | System and method for providing availability information to a user | |
WO2003027880A1 (en) | Methods and systems for one-stop communications management | |
JP2008052422A (en) | Presence search apparatus and messaging system | |
JPH0662047A (en) | Destination change information and transfer processing system for transmission of electronic mail |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MALIK, DALE W.;REEL/FRAME:017041/0994 Effective date: 20020328 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T DELAWARE INTELLECTUAL PROPERTY, INC.;REEL/FRAME:031755/0841 Effective date: 20131204 |
|
AS | Assignment |
Owner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC., DELAWAR Free format text: CHANGE OF NAME;ASSIGNOR:AT&T BLS INTELLECTUAL PROPERTY, INC.;REEL/FRAME:032092/0504 Effective date: 20071101 Owner name: AT&T INTELLECTUAL PROPERTY, INC., DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:BELLSOUTH INTELLECTUAL PROPERTY CORPORATION;REEL/FRAME:032092/0433 Effective date: 20070427 Owner name: AT&T BLS INTELLECTUAL PROPERTY, INC., DELAWARE Free format text: CHANGE OF NAME;ASSIGNOR:AT&T INTELLECTUAL PROPERTY, INC.;REEL/FRAME:032092/0483 Effective date: 20070727 Owner name: FACEBOOK, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY I, L.P.;REEL/FRAME:032004/0872 Effective date: 20131223 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: META PLATFORMS, INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:FACEBOOK, INC.;REEL/FRAME:058961/0436 Effective date: 20211028 |