US20090136009A1 - Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications - Google Patents

Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications Download PDF

Info

Publication number
US20090136009A1
US20090136009A1 US12/244,035 US24403508A US2009136009A1 US 20090136009 A1 US20090136009 A1 US 20090136009A1 US 24403508 A US24403508 A US 24403508A US 2009136009 A1 US2009136009 A1 US 2009136009A1
Authority
US
United States
Prior art keywords
communication
user
communications
group
communication device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/244,035
Inventor
Claire Svetlana Vishik
Lalitha Suryanarayana
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Intellectual Property I LP
Original Assignee
AT&T Intellectual Property I LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AT&T Intellectual Property I LP filed Critical AT&T Intellectual Property I LP
Priority to US12/244,035 priority Critical patent/US20090136009A1/en
Assigned to AT&T INTELLECTUAL PROPERTY I, L.P. reassignment AT&T INTELLECTUAL PROPERTY I, L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SURYANARAYANA, LALITHA, VISHIK, CLAIRE SVETLANA
Publication of US20090136009A1 publication Critical patent/US20090136009A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/22Arrangements for supervision, monitoring or testing
    • H04M3/2281Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0894Policy-based network configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/20Aspects of automatic or semi-automatic exchanges related to features of supplementary services
    • H04M2203/2044Group features, e.g. closed user group
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/45Aspects of automatic or semi-automatic exchanges related to voicemail messaging
    • H04M2203/4536Voicemail combined with text-based messaging
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42042Notifying the called party of information on the calling party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42059Making use of the calling party identifier
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42085Called party identification service
    • H04M3/42093Notifying the calling party of information on the called or connected party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42085Called party identification service
    • H04M3/42102Making use of the called party identifier
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42136Administration or customisation of services
    • H04M3/42153Administration or customisation of services by subscriber
    • H04M3/42161Administration or customisation of services by subscriber via computer interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42382Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks

Definitions

  • the present disclosure relates to methods and systems for multi-modal communications.
  • Unified messaging offers technologies to consolidate communications in multiple formats and make them available from one interface.
  • call forwarding can be used to forward calls from each phone to a single one of the phones. Call forwarding allows the individual to screen calls received on various handsets for the same purpose. However, some calls may be missed if the individual is not using the handset to which the calls are forwarded. Communications in other formats usually are tabulated and managed separately.
  • Caller Identification (ID) functionality has improved telephone service by allowing users to control aspects of responding to telephone calls.
  • the individual may be unable to identify an initial caller using caller ID.
  • FIG. 1 is a block diagram of an embodiment of a system for processing communications for a user-defined group of communication devices
  • FIG. 2 is a flow chart of an embodiment of a method of processing communications for the user-defined group of communication devices
  • FIG. 3 is an example of computer program code to represent an entry in the log database
  • FIG. 4 is an example of computer program code to define a device group
  • FIG. 5 is an example of a communications tree as displayed by the Web interface.
  • FIG. 6 shows an example of the aggregated list for hypothetical calls from hypothetical parties.
  • Embodiments of the present invention allow users to create a group of communication devices used for the same purpose (e.g. work). Caller ID functionality on each phone is aggregated over the group of devices to allow users to obtain, in real-time or near-real-time, a list of calls made to all devices in the group. Users can respond to all calls from the device that is currently active, which either may or may not be a telephone. Limitations of non-Internet wireline phones are described in greater detail herein. Thus, calls and other communications requiring immediate attention can be returned quickly regardless of which device they were initially addressed.
  • non-voice forms of communications such as text messaging
  • voice and non-voice are also aggregated in the list.
  • the structure of all communications, voice and non-voice, is made visible to users through a single graphical interface.
  • annotation, data mining, analysis and modeling of communication threads are facilitated by uniquely identifying each communication, and generating a hierarchical representation based thereon. Still further, search and retrieval of individual communications can be performed if archiving is enabled.
  • FIG. 1 is a block diagram of an embodiment of a system for processing communications for a user-defined group of communication devices
  • FIG. 2 is a flow chart of an embodiment of a method of processing communications for the user-defined group of communication devices.
  • FIG. 1 Illustrated in FIG. 1 are multiple communication devices 10 , 12 , 14 , 16 and 18 of a user 20 . Although five communication devices 10 , 12 , 14 , 16 and 18 are depicted in FIG. 1 for purposes of illustration and example, the system can be used in conjunction with any number of communication devices of the user 20 .
  • the communication devices 10 , 12 , 14 , 16 and 18 may facilitate voice-based and/or text-based communications for the user 20 .
  • Examples of the communication devices 10 , 12 , 14 , 16 and 18 include, but are not limited to, a wireless telephone, a landline telephone, an Internet telephone, a portable computer, a personal digital assistant, a messaging device, and a paging device.
  • the communication devices 10 , 12 , 14 , 16 and 18 have different communication addresses, which may comprise different physical network addresses and/or different logical network addresses.
  • a network address can comprise either a telephone number, an Internet telephone number, an electronic mail address, an Internet protocol address, an instant messaging address, or a paging number. It is noted that a converged device may have logically different communication addresses, even if the network address is the same and the device is the same, for different communication applications. It is also noted that the telephone numbers may comprise a virtual telephone number.
  • the communication devices 10 , 12 , 14 , 16 and 18 being the user's work telephone, work e-mail device, home telephone, cellular telephone and pager, respectively.
  • each of the communication devices 10 , 12 , 14 , 16 and 18 is provided a knowledge management (KM) client user interface 24 , 26 , 30 , 32 and 34 , respectively.
  • the KM client user interfaces 24 , 26 , 30 , 32 and 34 cooperate with a capture module 36 to enable the user 20 to monitor, screen and return calls and other communications from any device in a group defined by the user 20 .
  • the method comprises an act of creating a user-defined device group that identifies a plurality of communication devices and/or communication lines of the user 20 .
  • the user 20 creates the user-defined device group via a Web interface 42 or another user interface such as an Instant Messaging client or a graphical user interface (GUI).
  • GUI graphical user interface
  • the user 20 defines which of his/her communication devices 10 , 12 , 14 , 16 and 18 are to be part of the device group.
  • the capture module 36 interfaces and interacts with a database that stores and maintains logical identifiers to the devices and access modes defined in the device group.
  • the database may comprise an ENUM database, for example.
  • Address translation and mapping of an identifier of a device or communication access mode can be stored in a public or private ENUM.
  • instant messaging has an associated screen name
  • email has an associated simple mail transfer protocol (SMTP) address
  • phone number has an associated E.164-type number
  • IP telephone has an associated IP address.
  • the ENUM or other database can further indicate a status of an active device in the device group.
  • the method comprises designating at least one of the communication devices in the user-defined device group to receive an aggregated list of communications made with the communication devices in the user-defined device group.
  • the user can make the designation using the Web interface 42 .
  • the user can designate all of the communications devices in the user-defined device group to receive the aggregated list.
  • Some devices such as conventional landline telephones, may not be capable of providing the aggregated list, but nevertheless may be included in the user-defined device group.
  • all telephones that are designated either have access to the Internet 46 or are wireless access protocol (WAP)-enabled.
  • WAP wireless access protocol
  • the method comprises detecting a communication made using a communication device in the user-defined device group.
  • the communication may comprise a telephone call, an electronic mail message, a voice message, an instant message, or a pager message.
  • the communication may be either received or transmitted by the user 20 from/to another party.
  • Other media of communication can be included as they appear and begin to be supported on multiple devices, e.g. video calls.
  • the act of detecting can be performed by at least one of signaling system 7 (SS7) triggers, an automatic forwarding of e-mail or metadata about e-mail in a mail transfer protocol such as simple mail transfer protocol (SMTP), program code in a short messaging service center (SMSC) or an instant messaging server, and a session initiation protocol (SIP) signaling mechanism.
  • SS7 signaling system 7
  • SMTP simple mail transfer protocol
  • SMSC short messaging service center
  • SIP session initiation protocol
  • the capture module 36 captures the communication and logs onto a KM server 54 .
  • the KM server 54 provides a log database 56 that logs communications, including the aggregated list of communications, made by the user 20 .
  • the KM server 54 stores an entry in the log database 56 based on the communication.
  • the entry includes information identifying which device in the user-defined device group is involved in the communication, which is the “active” device, whether the communication was initiated by the user (e.g. the user 20 has placed a telephone call to another party) or another party (e.g. another party has placed a telephone call to the user 20 ), and optionally information identifying the other party of the communication.
  • the entry can provide links to the above information.
  • log database 56 examples include, but are not limited to, an XML database, a relational database management system (RDBMS) database, an object-oriented database (OODB) and a text file.
  • RDBMS relational database management system
  • OODB object-oriented database
  • presence information can be communicated to one or more network elements (not illustrated).
  • the presence information comes from the active device on which calls are received to indicate that the user 20 is present and available on the active device.
  • the presence information may indicate a communication mode of the active device.
  • the method comprises providing the entry to each communication device designated to receive the aggregated list.
  • the entry is communicated to each designated device via either the Internet 46 or a wireless data network.
  • Each designated device can display the entry using its respective KM client user interface.
  • the list created as call/message information from various devices is forwarded to the designated device(s).
  • the user 20 can sort the aggregated list by time (which is a default option), by origination point, or by name, for example. Further using the KM client user interface, the user 20 can scroll the aggregated list and select a particular entry to initiate a response to a received communication associated with the particular entry. The response may comprise returning a telephone call, forwarding for further action, sending an electronic mail message, sending a pager message, or sending an instant message, for example. Acts indicated by blocks 50 , 52 and optionally 60 are performed to process the response communication. Optionally, the KM client user interface either can link the list to the user's address book or can update the address book based on an entry.
  • the acts indicated by blocks 50 , 52 and 60 can be repeated for each of one or more additional communications made with communication devices in the user-defined device group. For example, based on detecting a first communication made using a first communication device in the group, a first entry for the aggregated list is generated and provided to the communication device(s) designated to receive the aggregated list. Thereafter, based on detecting a second communication made using a second communication device in the group, a second entry for the aggregated list is generated and provided to the communication device(s) designated to receive the aggregated list.
  • the first communication can be made using a first mode of a converged communication device
  • the second communication can be made using a second mode of the converged communication device.
  • the same converged communication device may have a voice call mode for a voice communication and a messaging mode for a messaging communication such as short message service (SMS).
  • SMS short message service
  • the method comprises the KM server 54 processing the captured entries in the log database 56 to display information to the user 20 via a Web interface 66 or another user interface such as a GUI.
  • the entries may be processed by an analysis and modeling system 68 for retrieval and analysis using text and multimedia processing and statistical analysis.
  • the entries are processed to allow the user 20 to analyze the communications and interaction patterns to gain knowledge about a model of his/her communications within a certain context. For example, if a response call/message originates from the single aggregated list, its relationship with other preceding and subsequent calls/messages can be retrieved via the Web interface 66 or another interface as a thread similar to e-mail threads on electronic bulletin boards.
  • the analysis and modeling system 68 can automate the processing using off-the-shelf or enhanced tools, or can be done manually.
  • the analysis and modeling system 68 can be interfaced with an external system such as a billing system or a sales force automation system.
  • An ontology or hierarchy of communication threads can be automatically generated by the KM server 54 .
  • the dynamics of multiple conversations are made visible to the user 20 via the Web interface 66 .
  • This is beneficial in sales and marketing communications, online education and training communications, and various social communications.
  • the hierarchical representation of communications allows various modeling applications to be performed by the analysis and modeling system 68 . Examples of the modeling applications include, but are not limited to, predicting the success of contract negotiations, optimizing group work, and optimizing calling and/or Internet plans for various situations.
  • the calls and messages in the log database 56 have identifiers (IDs) to represent inheritance.
  • the KM server 54 can represent the calls and messages as a tree that is displayed to the user 20 via the Web interface 66 or another interface.
  • the method comprises receiving input from the user 20 via the Web interface 66 .
  • the input can comprise annotations and/or other additional information to associated with particular communications in the log database 56 .
  • the nature and type of annotation for each communication is flexible dependent upon the application, purpose and user.
  • the annotations may be multi-modal.
  • the input can comprise commands to indicate how the user wants to organize the communications, for example, how the user wants to categorize the information or otherwise view the communications as a tree.
  • the input can comprise commands to search for particular communications or communication topics in the log database 56 . If archiving is enabled, full content can be searched as well.
  • the input can comprise commands to link entries, e.g. to link the first entry and the second entry.
  • the Web interface 66 can support a private link command to make the link visible only to one or more designated users, such as the owner of the device group.
  • the KM server 54 responds by updating the Web interface 66 based on the user input, as indicated by returning to block 64 .
  • Multiple iterations of interaction between the user 20 and the KM server 54 via the Web interface 66 can occur to allow the user 20 to analyze the communication and interaction patterns.
  • the user may forecast, improve productivity, or optimize a service bundle, for example.
  • communications can be archived and retrieved later by the KM server 54 .
  • business models based on group interactions can be developed.
  • An example of a business model is pricing for a bundle of voice and text communications for families.
  • a family plan can be developed based on the analysis to provide some member the ability to answer messages without initiating communications. Two other specific examples of analysis are as follows.
  • a sales person analyzes his/her communications with prospects. He/she notices that a first prospect very rarely returns phone calls, but writes e-mail on a regular basis. The sales person decides to use predominantly text-based means to communication with the first prospect. A second prospect almost never returns communicate in any format. Upon noticing this, the sales person decides to make inactive a line associated with the second prospect. However, the sales person decides to more actively pursue the second prospect as a potential client because of a significantly greater than average activity index.
  • the sales person decides to analyze the success of communications for the past six months.
  • the KM server 54 retrieves data from the log database 56 , analyzes the data using the analysis and modeling system 68 , and presents via the Web interface 66 information showing that almost all prospects have a lower than usual activity index.
  • the sales person can use this information as a market predictor or as a signal to review the approach to the sales process.
  • flow of the method can return to block 40 in FIG. 2 , wherein the user 20 either modifies an existing device group, disbands an existing device group, or creates a new device group via the Web interface 42 .
  • An existing device group can be modified either by adding another communication device thereto, or removing a communication device therefrom.
  • a device group can identify a communication line, such as a phone line, or a virtual line on demand enabled by Voice over Internet Protocol (VoIP) for example.
  • VoIP Voice over Internet Protocol
  • Some converged devices, such as those which enable VoIP as well as TDM, are each considered as multiple devices or lines as used herein.
  • the aggregated list is kept unchanged in response to subsequent communications made using the device. For example, consider a third communication device that is removed from the device group. Thereafter, if a third communication is made using the third communication device, the aggregated list is kept unchanged based on the third communication.
  • the aggregated list is updated in response to subsequent communications made using the device. For example, consider a fourth communication device that is added to the device group. Thereafter, a fourth communication made using the fourth communication device is detected, and an entry based thereon is generated and provided to the communication device(s) designated to receive the aggregated list.
  • no aggregated list is provided in response to subsequent communications using the devices/lines in the previously-active device group.
  • the devices/lines go back to the conventional paradigm after the device group is disbanded.
  • FIG. 3 is an example of computer program code to represent an entry in the log database 56 .
  • the code is represented in an eXtensible Markup Language (XML)-derivative language such as Resource Description Framework (RDF).
  • XML eXtensible Markup Language
  • RDF Resource Description Framework
  • the code comprises tags and values to define a title (e.g. “Message from the CIO”), an annotation (e.g. “He believes we need to continue discussions to arrive at agreement on price points”), a contact name (e.g. “John Doe”), a device involved in the communication (e.g. a second wireless phone), a device ID to identify the device (e.g. 666777845), a date of the communication (e.g. 2004-01-05), a type of communication (e.g. voice mail), a format of the communication (e.g. voice or text), and an identifier of the communication (e.g. “t-5550149-ph”).
  • Use of the communication identifier in a tagged language, such as XML or its successors, facilitates the definition of relationships between entries in the log database 56 , e.g. relationships between calls and/or messages.
  • FIG. 4 is an example of computer program code to define a device group.
  • the code comprises tags and values to define a device group identifier (e.g. “657483”), a device group name (e.g. “MyPhones”), an identifier of a device in the group (e.g. “657499d-65”, a type of the device (e.g. a landline phone), a device address (e.g. the phone number “512-555-1025”), a status of the device (e.g. “active”), synchronous update mode parameters, asynchronous update mode parameters, a sending protocol, a receiving protocol and a device priority (e.g. make this device the first priority in the group).
  • a device group identifier e.g. “657483”
  • MyPhones e.g. “MyPhones”
  • an identifier of a device in the group e.g. “657499d-65”
  • a type of the device
  • FIG. 5 is an example of a communications tree as displayed by the Web interface 66 .
  • an annotation describing or summarizing the nature of the communication, an indication of which device in the user-defined device group was involved in the communication, and a date of the communication. Further, each communication indicates if it is a reply/response to another communication, and indicates which other communication is its parent in the tree.
  • a time stamp and an identifier may also be provided.
  • the user uses a Web browser to create, disband, or edit a group of devices via the Web interface 42 .
  • a Web browser to create, disband, or edit a group of devices via the Web interface 42 .
  • he/she may edit the group to include his/her office phone, home phone, work cellular phone and PDA in the group.
  • the user designates the work cellular phone to receive the aggregated list of calls on its caller ID. Alternatively, all devices in the group can display the list.
  • FIG. 6 shows an example of the aggregated list for hypothetical calls from hypothetical parties. The list is based on five entries in the log database 56 .
  • the list contains the name, if available, and number associated with the origination of each call as well as the designation of the device where the call was received if it is not the device displaying the list.
  • a first entry in the list indicates a call from Allen Smith received by the user's main phone, e.g. the user's cellular phone which is designated to receive the list.
  • a second entry in the list indicates a call from a company received by the user's home phone.
  • a “t3” designation a third entry in the list indicates a pager message from the company received by the user's pager. The third entry indicates a message to call the sender at a particular telephone number.
  • a fourth entry in the list indicates a call to the user's work phone.
  • a fifth entry in the list indicates a call to the user's main phone.
  • the user can scroll through the list of calls, select a call that appears to be important, and press a “return” button on the KM client user interface of the cellular phone to return the call. As illustrated in FIG. 6 , the user may select the second entry, and press the “return” button to call back the company.
  • the cellular phone may be set to ring when an important call is received on a different phone in the group. Further, the cellular phone may highlight calls in the list that have important originations. These features are set by the user through the Web interface 42 used for defining the group.
  • the user disbands the group via the Web interface 42 when the group is no longer needed. For example, the user may disband the group when he/she returns from the trip. The user disbands the group either because he/she now has easier access to all of the telephones, or because he/she will need a different group of devices for a different project.
  • An example of the user organizing threads based on communication entries is as follows. This example shows a specific case of how relationships between communications can be developed to organize the communications in a ontology or taxonomy such as a user-defined categorization.
  • the user logs into a Web site that provides the Web interface 66 .
  • the user selects an “interactions” tab or another user-selectable control of the Web interface 66 to initiate thread creation features.
  • the user commands a search for all threads that include a certain name or phone number.
  • the KM server 54 performs the search based on entries in the log database 56 , and returns one or more threads.
  • the user deems the thread to be important. Accordingly, the user names the thread and annotates some of the entries in the thread using the Web interface 66 .
  • the user places the thread in a folder indicating a main topic of the thread. For example, the user may place the thread in a “new products” folder.
  • the user links the thread with one or more other threads that contain relevant information.
  • An example of the user executing the modeling functionality of the KM server 54 is as follows.
  • the user selects a particular thread using the Web interface 66 .
  • the user selects a “data mining” tab or another user-selectable control of the Web interface 66 to initiate data mining features.
  • the user selects a “success predictor” control of the Web interface 66 and runs it.
  • the analysis and modeling system 68 determines a probability of a contract being signed within two months based on rules in the system, preset parameters and a numerical thread composition value.
  • the Web interface 66 displays success predictor indicators for all threads in the “new products” folder. The user views the display and discovers that there are multiple threads with higher indicators of success.
  • the user decides to limit his/her involvement in the project represented by the particular thread but not abandon the project altogether.
  • Components of the system disclosed herein can have various security and privacy features.
  • Components of a group of connected devices can be invisible to all but a pre-configured group of the devices based on identifiers.
  • Some communications, annotations, links and supporting information can be password protected or encrypted.
  • Log entries and output can by anonymized to protect the privacy of participants.
  • Security can be set up for each communication thread to accommodate the requirements of all participants. Selected entries can be made invisible or expire and be deleted after a predefined time period.
  • Some communications, based on user-defined or system-established exclusions, may be excluded from capturing by the capture module 36 for reasons such as privacy and confidentiality.
  • Each of the herein-disclosed components can include one or more computer processors that are directed by computer-readable program code stored by an associated computer-readable medium to perform the acts disclosed herein.
  • inventions of the method and system disclosed herein allow users to capture relationships and interdependencies between communications in voice, text and other formats. This is beneficial for users who use multiple communication devices, multiple physical or virtual lines, and multiple communication modes (e.g. voice or data) of about equal importance.
  • the system can handle communications from one or more wireless networks 80 , the Internet 46 , and a public switched telephone network (PSTN) 82 . Via the Internet 46 , the system can handle e-mail 84 , Voice over IP (VoIP) 86 , and instant messaging 88 communications.
  • PSTN public switched telephone network
  • a knowledge management tool allows users to visualize, model, forecast and analyze these relationships for the communications.
  • the system can be used as a value-added extension to current or future unified messaging (UM) paradigms, or can exist independently from them.
  • UM unified messaging
  • the communication list application can be used in conjunction with ENUM, which is a standard to associate a telephone number with an IP address.
  • Information about the device group can be stored in an ENUM database.
  • a mapping of a communication address to an identifier of a device or access mode of communication can be stored in a public or private ENUM.
  • This architecture allows for communicating presence information to the appropriate network elements.
  • the active device on which calls are received may indicate that the user is currently present and available on the active device or communication mode.
  • the method and system described herein can handle multiple users, each of whom defines his/her own device group.
  • a group can be defined by one individual on behalf of another individual.
  • an assistant for a lawyer can define a device group for the lawyer.
  • the method and system supports sharing and transmitting the information concerning the device group to other users, e.g. those in address books have their communications directed, routed and forwarded accordingly to the active device or preferred device in the group.

Abstract

Systems and method of capturing multi-modal communications are provided. A particular method includes detecting a first communication made using a first communication device in a group of communication devices of a user, where the group of communication devices is defined by the user. The method also includes generating a first entry in an aggregated list of communications based on the first communication. The first entry includes information identifying the first communication device.

Description

    CLAIM OF PRIORITY
  • This application is a Continuation patent application of, and claims priority from, U.S. patent application Ser. No. 10/843,689, filed on May 11, 2004 and entitled “KNOWLEDGE MANAGEMENT, CAPTURE AND MODELING TOOL FOR MULTI-MODAL COMMUNICATIONS,” which is hereby incorporated by reference in its entirety.
  • FIELD OF THE DISCLOSURE
  • The present disclosure relates to methods and systems for multi-modal communications.
  • DESCRIPTION OF THE RELATED ART
  • Many individuals use several different telephones for the same purpose. For example, a sales executive may use a main office telephone, a home office telephone and a cellular telephone all for the purpose of making business-related sales. Recently, other modes of communication, such as instant messaging and e-mail, have become an integral part of many processes. Unified messaging offers technologies to consolidate communications in multiple formats and make them available from one interface. To aggregate calls received by the individual's phones, call forwarding can be used to forward calls from each phone to a single one of the phones. Call forwarding allows the individual to screen calls received on various handsets for the same purpose. However, some calls may be missed if the individual is not using the handset to which the calls are forwarded. Communications in other formats usually are tabulated and managed separately.
  • Caller Identification (ID) functionality has improved telephone service by allowing users to control aspects of responding to telephone calls. However, using the aforementioned call forwarding method, the individual may be unable to identify an initial caller using caller ID.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention is pointed out with particularity in the appended claims. However, other features are described in the following detailed description in conjunction with the accompanying drawings in which:
  • FIG. 1 is a block diagram of an embodiment of a system for processing communications for a user-defined group of communication devices;
  • FIG. 2 is a flow chart of an embodiment of a method of processing communications for the user-defined group of communication devices;
  • FIG. 3 is an example of computer program code to represent an entry in the log database;
  • FIG. 4 is an example of computer program code to define a device group;
  • FIG. 5 is an example of a communications tree as displayed by the Web interface; and
  • FIG. 6 shows an example of the aggregated list for hypothetical calls from hypothetical parties.
  • DESCRIPTION OF THE DRAWINGS
  • Embodiments of the present invention allow users to create a group of communication devices used for the same purpose (e.g. work). Caller ID functionality on each phone is aggregated over the group of devices to allow users to obtain, in real-time or near-real-time, a list of calls made to all devices in the group. Users can respond to all calls from the device that is currently active, which either may or may not be a telephone. Limitations of non-Internet wireline phones are described in greater detail herein. Thus, calls and other communications requiring immediate attention can be returned quickly regardless of which device they were initially addressed.
  • Other non-voice forms of communications, such as text messaging, are also aggregated in the list. The structure of all communications, voice and non-voice, is made visible to users through a single graphical interface.
  • Further, annotation, data mining, analysis and modeling of communication threads are facilitated by uniquely identifying each communication, and generating a hierarchical representation based thereon. Still further, search and retrieval of individual communications can be performed if archiving is enabled.
  • Embodiments of the present invention are described with reference to FIG. 1, which is a block diagram of an embodiment of a system for processing communications for a user-defined group of communication devices, and FIG. 2, which is a flow chart of an embodiment of a method of processing communications for the user-defined group of communication devices.
  • Illustrated in FIG. 1 are multiple communication devices 10, 12, 14, 16 and 18 of a user 20. Although five communication devices 10, 12, 14, 16 and 18 are depicted in FIG. 1 for purposes of illustration and example, the system can be used in conjunction with any number of communication devices of the user 20. The communication devices 10, 12, 14, 16 and 18 may facilitate voice-based and/or text-based communications for the user 20. Examples of the communication devices 10, 12, 14, 16 and 18 include, but are not limited to, a wireless telephone, a landline telephone, an Internet telephone, a portable computer, a personal digital assistant, a messaging device, and a paging device.
  • The communication devices 10, 12, 14, 16 and 18 have different communication addresses, which may comprise different physical network addresses and/or different logical network addresses. As used herein, a network address can comprise either a telephone number, an Internet telephone number, an electronic mail address, an Internet protocol address, an instant messaging address, or a paging number. It is noted that a converged device may have logically different communication addresses, even if the network address is the same and the device is the same, for different communication applications. It is also noted that the telephone numbers may comprise a virtual telephone number.
  • For purposes of illustration and example, consider the communication devices 10, 12, 14, 16 and 18 being the user's work telephone, work e-mail device, home telephone, cellular telephone and pager, respectively.
  • As indicated by block 22 in FIG. 2, each of the communication devices 10, 12, 14, 16 and 18 is provided a knowledge management (KM) client user interface 24, 26, 30, 32 and 34, respectively. The KM client user interfaces 24, 26, 30, 32 and 34 cooperate with a capture module 36 to enable the user 20 to monitor, screen and return calls and other communications from any device in a group defined by the user 20.
  • As indicated by block 40, the method comprises an act of creating a user-defined device group that identifies a plurality of communication devices and/or communication lines of the user 20. The user 20 creates the user-defined device group via a Web interface 42 or another user interface such as an Instant Messaging client or a graphical user interface (GUI). Using the Web interface 42, the user 20 defines which of his/her communication devices 10, 12, 14, 16 and 18 are to be part of the device group. In one embodiment, the capture module 36 interfaces and interacts with a database that stores and maintains logical identifiers to the devices and access modes defined in the device group. The database may comprise an ENUM database, for example. Address translation and mapping of an identifier of a device or communication access mode can be stored in a public or private ENUM. For example, instant messaging has an associated screen name, email has an associated simple mail transfer protocol (SMTP) address, a phone number has an associated E.164-type number, and an IP telephone has an associated IP address. The ENUM or other database can further indicate a status of an active device in the device group.
  • As indicated by block 44, the method comprises designating at least one of the communication devices in the user-defined device group to receive an aggregated list of communications made with the communication devices in the user-defined device group. The user can make the designation using the Web interface 42. If desired, the user can designate all of the communications devices in the user-defined device group to receive the aggregated list. Some devices, such as conventional landline telephones, may not be capable of providing the aggregated list, but nevertheless may be included in the user-defined device group. Preferably, all telephones that are designated either have access to the Internet 46 or are wireless access protocol (WAP)-enabled.
  • As indicated by block 50, the method comprises detecting a communication made using a communication device in the user-defined device group. The communication may comprise a telephone call, an electronic mail message, a voice message, an instant message, or a pager message. The communication may be either received or transmitted by the user 20 from/to another party. Other media of communication can be included as they appear and begin to be supported on multiple devices, e.g. video calls. The act of detecting can be performed by at least one of signaling system 7 (SS7) triggers, an automatic forwarding of e-mail or metadata about e-mail in a mail transfer protocol such as simple mail transfer protocol (SMTP), program code in a short messaging service center (SMSC) or an instant messaging server, and a session initiation protocol (SIP) signaling mechanism.
  • As indicated by block 52, the capture module 36 captures the communication and logs onto a KM server 54. The KM server 54 provides a log database 56 that logs communications, including the aggregated list of communications, made by the user 20. The KM server 54 stores an entry in the log database 56 based on the communication. The entry includes information identifying which device in the user-defined device group is involved in the communication, which is the “active” device, whether the communication was initiated by the user (e.g. the user 20 has placed a telephone call to another party) or another party (e.g. another party has placed a telephone call to the user 20), and optionally information identifying the other party of the communication. Alternatively, the entry can provide links to the above information. Archiving of full or partial communications can be provided as an additional function. Examples of the log database 56 include, but are not limited to, an XML database, a relational database management system (RDBMS) database, an object-oriented database (OODB) and a text file.
  • Optionally, presence information can be communicated to one or more network elements (not illustrated). The presence information comes from the active device on which calls are received to indicate that the user 20 is present and available on the active device. The presence information may indicate a communication mode of the active device.
  • As indicated by block 60, the method comprises providing the entry to each communication device designated to receive the aggregated list. In one embodiment, the entry is communicated to each designated device via either the Internet 46 or a wireless data network. Each designated device can display the entry using its respective KM client user interface. Thus, the list created as call/message information from various devices is forwarded to the designated device(s).
  • Using the KM client user interface, the user 20 can sort the aggregated list by time (which is a default option), by origination point, or by name, for example. Further using the KM client user interface, the user 20 can scroll the aggregated list and select a particular entry to initiate a response to a received communication associated with the particular entry. The response may comprise returning a telephone call, forwarding for further action, sending an electronic mail message, sending a pager message, or sending an instant message, for example. Acts indicated by blocks 50, 52 and optionally 60 are performed to process the response communication. Optionally, the KM client user interface either can link the list to the user's address book or can update the address book based on an entry.
  • The acts indicated by blocks 50, 52 and 60 can be repeated for each of one or more additional communications made with communication devices in the user-defined device group. For example, based on detecting a first communication made using a first communication device in the group, a first entry for the aggregated list is generated and provided to the communication device(s) designated to receive the aggregated list. Thereafter, based on detecting a second communication made using a second communication device in the group, a second entry for the aggregated list is generated and provided to the communication device(s) designated to receive the aggregated list.
  • It is noted that the first communication can be made using a first mode of a converged communication device, and the second communication can be made using a second mode of the converged communication device. Thus, the same converged communication device may have a voice call mode for a voice communication and a messaging mode for a messaging communication such as short message service (SMS).
  • As indicated by blocks 62 and 64, the method comprises the KM server 54 processing the captured entries in the log database 56 to display information to the user 20 via a Web interface 66 or another user interface such as a GUI. The entries may be processed by an analysis and modeling system 68 for retrieval and analysis using text and multimedia processing and statistical analysis. The entries are processed to allow the user 20 to analyze the communications and interaction patterns to gain knowledge about a model of his/her communications within a certain context. For example, if a response call/message originates from the single aggregated list, its relationship with other preceding and subsequent calls/messages can be retrieved via the Web interface 66 or another interface as a thread similar to e-mail threads on electronic bulletin boards. The analysis and modeling system 68 can automate the processing using off-the-shelf or enhanced tools, or can be done manually. The analysis and modeling system 68 can be interfaced with an external system such as a billing system or a sales force automation system.
  • An ontology or hierarchy of communication threads can be automatically generated by the KM server 54. As a result, the dynamics of multiple conversations are made visible to the user 20 via the Web interface 66. This is beneficial in sales and marketing communications, online education and training communications, and various social communications. Further, the hierarchical representation of communications allows various modeling applications to be performed by the analysis and modeling system 68. Examples of the modeling applications include, but are not limited to, predicting the success of contract negotiations, optimizing group work, and optimizing calling and/or Internet plans for various situations.
  • In one embodiment, the calls and messages in the log database 56 have identifiers (IDs) to represent inheritance. Using the inheritance IDs, the KM server 54 can represent the calls and messages as a tree that is displayed to the user 20 via the Web interface 66 or another interface.
  • As indicated by block 70, the method comprises receiving input from the user 20 via the Web interface 66. The input can comprise annotations and/or other additional information to associated with particular communications in the log database 56. The nature and type of annotation for each communication is flexible dependent upon the application, purpose and user. The annotations may be multi-modal. Alternatively, the input can comprise commands to indicate how the user wants to organize the communications, for example, how the user wants to categorize the information or otherwise view the communications as a tree. As another alternative, the input can comprise commands to search for particular communications or communication topics in the log database 56. If archiving is enabled, full content can be searched as well. As a further alternative, the input can comprise commands to link entries, e.g. to link the first entry and the second entry. The Web interface 66 can support a private link command to make the link visible only to one or more designated users, such as the owner of the device group.
  • The KM server 54 responds by updating the Web interface 66 based on the user input, as indicated by returning to block 64. Multiple iterations of interaction between the user 20 and the KM server 54 via the Web interface 66 can occur to allow the user 20 to analyze the communication and interaction patterns. Based on the user's analysis, the user may forecast, improve productivity, or optimize a service bundle, for example. As an option, communications can be archived and retrieved later by the KM server 54. In addition to modeling and analysis, business models based on group interactions can be developed. An example of a business model is pricing for a bundle of voice and text communications for families. Continuing with this example, a family plan can be developed based on the analysis to provide some member the ability to answer messages without initiating communications. Two other specific examples of analysis are as follows.
  • EXAMPLE 1
  • A sales person analyzes his/her communications with prospects. He/she notices that a first prospect very rarely returns phone calls, but writes e-mail on a regular basis. The sales person decides to use predominantly text-based means to communication with the first prospect. A second prospect almost never returns communicate in any format. Upon noticing this, the sales person decides to make inactive a line associated with the second prospect. However, the sales person decides to more actively pursue the second prospect as a potential client because of a significantly greater than average activity index.
  • EXAMPLE 2
  • The sales person decides to analyze the success of communications for the past six months. The KM server 54 retrieves data from the log database 56, analyzes the data using the analysis and modeling system 68, and presents via the Web interface 66 information showing that almost all prospects have a lower than usual activity index. The sales person can use this information as a market predictor or as a signal to review the approach to the sales process.
  • At any time, flow of the method can return to block 40 in FIG. 2, wherein the user 20 either modifies an existing device group, disbands an existing device group, or creates a new device group via the Web interface 42. An existing device group can be modified either by adding another communication device thereto, or removing a communication device therefrom.
  • It is noted that a device group can identify a communication line, such as a phone line, or a virtual line on demand enabled by Voice over Internet Protocol (VoIP) for example. Some converged devices, such as those which enable VoIP as well as TDM, are each considered as multiple devices or lines as used herein.
  • After a device is removed from the device group, the aggregated list is kept unchanged in response to subsequent communications made using the device. For example, consider a third communication device that is removed from the device group. Thereafter, if a third communication is made using the third communication device, the aggregated list is kept unchanged based on the third communication.
  • After a device is added to the device group, the aggregated list is updated in response to subsequent communications made using the device. For example, consider a fourth communication device that is added to the device group. Thereafter, a fourth communication made using the fourth communication device is detected, and an entry based thereon is generated and provided to the communication device(s) designated to receive the aggregated list.
  • After a device group is disbanded, no aggregated list is provided in response to subsequent communications using the devices/lines in the previously-active device group. In one embodiment, the devices/lines go back to the conventional paradigm after the device group is disbanded.
  • FIG. 3 is an example of computer program code to represent an entry in the log database 56. In this example, the code is represented in an eXtensible Markup Language (XML)-derivative language such as Resource Description Framework (RDF).
  • The code comprises tags and values to define a title (e.g. “Message from the CIO”), an annotation (e.g. “He believes we need to continue discussions to arrive at agreement on price points”), a contact name (e.g. “John Doe”), a device involved in the communication (e.g. a second wireless phone), a device ID to identify the device (e.g. 666777845), a date of the communication (e.g. 2004-01-05), a type of communication (e.g. voice mail), a format of the communication (e.g. voice or text), and an identifier of the communication (e.g. “t-5550149-ph”). Use of the communication identifier in a tagged language, such as XML or its successors, facilitates the definition of relationships between entries in the log database 56, e.g. relationships between calls and/or messages.
  • Use of a tagged language, such as XML or its successors, also facilitates the definition of groups of devices. FIG. 4 is an example of computer program code to define a device group. The code comprises tags and values to define a device group identifier (e.g. “657483”), a device group name (e.g. “MyPhones”), an identifier of a device in the group (e.g. “657499d-65”, a type of the device (e.g. a landline phone), a device address (e.g. the phone number “512-555-1025”), a status of the device (e.g. “active”), synchronous update mode parameters, asynchronous update mode parameters, a sending protocol, a receiving protocol and a device priority (e.g. make this device the first priority in the group).
  • FIG. 5 is an example of a communications tree as displayed by the Web interface 66. Associated with each entry in the tree is an annotation describing or summarizing the nature of the communication, an indication of which device in the user-defined device group was involved in the communication, and a date of the communication. Further, each communication indicates if it is a reply/response to another communication, and indicates which other communication is its parent in the tree. A time stamp and an identifier may also be provided.
  • A detailed example of a user using an embodiment of the method and system is as follows.
  • 1. The user uses a Web browser to create, disband, or edit a group of devices via the Web interface 42. For example, if he/she is traveling to California, he/she may edit the group to include his/her office phone, home phone, work cellular phone and PDA in the group.
  • 2. The user designates the work cellular phone to receive the aggregated list of calls on its caller ID. Alternatively, all devices in the group can display the list. FIG. 6 shows an example of the aggregated list for hypothetical calls from hypothetical parties. The list is based on five entries in the log database 56.
  • 3. The list contains the name, if available, and number associated with the origination of each call as well as the designation of the device where the call was received if it is not the device displaying the list. By having no designation, a first entry in the list indicates a call from Allen Smith received by the user's main phone, e.g. the user's cellular phone which is designated to receive the list. By having a “t2” designation, a second entry in the list indicates a call from a company received by the user's home phone. By having a “t3” designation, a third entry in the list indicates a pager message from the company received by the user's pager. The third entry indicates a message to call the sender at a particular telephone number. By having a “t4” designation, a fourth entry in the list indicates a call to the user's work phone. By having no designation, a fifth entry in the list indicates a call to the user's main phone.
  • 4. The user can scroll through the list of calls, select a call that appears to be important, and press a “return” button on the KM client user interface of the cellular phone to return the call. As illustrated in FIG. 6, the user may select the second entry, and press the “return” button to call back the company.
  • 5. The cellular phone may be set to ring when an important call is received on a different phone in the group. Further, the cellular phone may highlight calls in the list that have important originations. These features are set by the user through the Web interface 42 used for defining the group.
  • 6. The user disbands the group via the Web interface 42 when the group is no longer needed. For example, the user may disband the group when he/she returns from the trip. The user disbands the group either because he/she now has easier access to all of the telephones, or because he/she will need a different group of devices for a different project.
  • An example of the user organizing threads based on communication entries is as follows. This example shows a specific case of how relationships between communications can be developed to organize the communications in a ontology or taxonomy such as a user-defined categorization.
  • 1. The user logs into a Web site that provides the Web interface 66.
  • 2. The user selects an “interactions” tab or another user-selectable control of the Web interface 66 to initiate thread creation features.
  • 3. Using the Web interface 66, the user commands a search for all threads that include a certain name or phone number. The KM server 54 performs the search based on entries in the log database 56, and returns one or more threads.
  • 4. Using the Web interface 66, the user selects a thread to explore in detail.
  • 5. The user deems the thread to be important. Accordingly, the user names the thread and annotates some of the entries in the thread using the Web interface 66.
  • 6. Using the Web interface 66, the user places the thread in a folder indicating a main topic of the thread. For example, the user may place the thread in a “new products” folder.
  • 7. Using the Web interface 66, the user links the thread with one or more other threads that contain relevant information.
  • An example of the user executing the modeling functionality of the KM server 54 is as follows.
  • 1. The user selects a particular thread using the Web interface 66.
  • 2. The user clicks on a “modeling” tab or another user-selectable control of the Web interface 66 to initiate modeling features.
  • 3. The user selects a “data mining” tab or another user-selectable control of the Web interface 66 to initiate data mining features.
  • 4. The user selects a “success predictor” control of the Web interface 66 and runs it.
  • 5. The analysis and modeling system 68 determines a probability of a contract being signed within two months based on rules in the system, preset parameters and a numerical thread composition value.
  • 6. The Web interface 66 displays success predictor indicators for all threads in the “new products” folder. The user views the display and discovers that there are multiple threads with higher indicators of success.
  • 7. The user decides to limit his/her involvement in the project represented by the particular thread but not abandon the project altogether.
  • Components of the system disclosed herein can have various security and privacy features. Components of a group of connected devices can be invisible to all but a pre-configured group of the devices based on identifiers. Some communications, annotations, links and supporting information can be password protected or encrypted. Log entries and output can by anonymized to protect the privacy of participants. Security can be set up for each communication thread to accommodate the requirements of all participants. Selected entries can be made invisible or expire and be deleted after a predefined time period. Some communications, based on user-defined or system-established exclusions, may be excluded from capturing by the capture module 36 for reasons such as privacy and confidentiality.
  • Each of the herein-disclosed components can include one or more computer processors that are directed by computer-readable program code stored by an associated computer-readable medium to perform the acts disclosed herein.
  • In conclusion, embodiments of the method and system disclosed herein allow users to capture relationships and interdependencies between communications in voice, text and other formats. This is beneficial for users who use multiple communication devices, multiple physical or virtual lines, and multiple communication modes (e.g. voice or data) of about equal importance. The system can handle communications from one or more wireless networks 80, the Internet 46, and a public switched telephone network (PSTN) 82. Via the Internet 46, the system can handle e-mail 84, Voice over IP (VoIP) 86, and instant messaging 88 communications.
  • Further, a knowledge management tool allows users to visualize, model, forecast and analyze these relationships for the communications. The system can be used as a value-added extension to current or future unified messaging (UM) paradigms, or can exist independently from them. The communication list application can be used in conjunction with ENUM, which is a standard to associate a telephone number with an IP address. Information about the device group can be stored in an ENUM database. A mapping of a communication address to an identifier of a device or access mode of communication can be stored in a public or private ENUM.
  • This architecture allows for communicating presence information to the appropriate network elements. In this case, the active device on which calls are received may indicate that the user is currently present and available on the active device or communication mode.
  • The method and system described herein can handle multiple users, each of whom defines his/her own device group. A group can be defined by one individual on behalf of another individual. For example, an assistant for a lawyer can define a device group for the lawyer. Further, the method and system supports sharing and transmitting the information concerning the device group to other users, e.g. those in address books have their communications directed, routed and forwarded accordingly to the active device or preferred device in the group.
  • It will be apparent to those skilled in the art that the disclosed embodiments may be modified in numerous ways and may assume many embodiments other than the particular forms specifically set out and described herein.
  • The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims (24)

1. A method, comprising:
detecting a first communication made using a first communication device in a group of communication devices of a user, where the group of communication devices is defined by the user; and
generating a first entry in an aggregated list of communications based on the first communication, the first entry including information identifying the first communication device.
2. The method of claim 1, further comprising sending at least the first entry in the aggregated list of communications to at least one designated communication device.
3. The method of claim 2, further comprising receiving input from the user designating the at least one designated communication device.
4. The method of claim 1, wherein two or more of communication devices of the group of communication devices have different communication addresses.
5. The method of claim 1, further comprising receiving input from the user specifying communication devices to be included in the group of communication devices.
6. The method of claim 1, further comprising:
after generating the first entry, detecting a second communication made using a second communication device in the group of communication devices of the user;
generating a second entry in the aggregated list of communications based on the second communication, the second entry including information identifying the second communication device.
7. The method of claim 6, further comprising sending at least a portion of the aggregated list to at least one communication device designated to receive the aggregated list of communications.
8. The method of claim 1, further comprising receiving input from the user to edit the group of communication devices.
9. The method of claim 1, wherein the communication devices of the group of communication devices include at least one landline telephone or Internet telephone of the user, at least one wireless telephone of the user, and at least one electronic mail device of the user.
10. The method of claim 1, wherein the first communication comprises a first telephone call made to the first communication device.
11. The method of claim 1, wherein the first communication comprises a text message or a multimedia message sent to the first communication device.
12. The method of claim 1, wherein the first communication comprises a first telephone call made from the first communication device.
13. The method of claim 1, further comprising receiving annotation input from the user and storing a first annotation associated with the first entry in response to the annotation input.
14. The method of claim 1, further comprising receiving organization input and organizing the aggregated list of communications in response to the organization input.
15. The method of claim 1, further comprising receiving linking input and linking the first entry to one or more other entries of the aggregated list of communications in response to the linking input.
16. A system, comprising:
a capture module to detect a first communication made using a first communication device of a device group, to generate a first entry to an aggregated list of communications based on the first communication, and to provide the first entry to at least one communication device of the device group designated to receive the aggregated list of communications;
wherein the first entry including information identifying the first communication device; and
wherein the device group identifies a plurality of communication devices of a user, the communication devices having different communication addresses.
17. The system of claim 16, wherein the at least one communication device designated to receive the aggregated list of communications includes the first communication device.
18. The system of claim 17, wherein the at least one communication device designated to receive the aggregated list of communications includes a second communication device of the device group.
19. The system of claim 16, wherein the capture module distinguishes communications made with different modes of communication of a particular communication device.
20. The system of claim 16, wherein the capture module distinguishes communications for different logical communication addresses of a particular communication device.
21. The system of claim 16, wherein the capture module includes at least one of a Web interface and an Instant Messaging interface to receive input to modify the device group.
22. The system of claim 16, wherein the capture module excludes one or more communications from the aggregate list of communications based on one or more predetermined exclusion rules.
23. The system of claim 16, further comprising a knowledge management component responsive to the capture module, the knowledge management component to create an ontology or hierarchy of communication threads based on the aggregated list of communications.
24. The system of claim 16, wherein the capture module interfaces and interacts with an ENUM database that stores logical identifiers of the plurality of communication devices of the user.
US12/244,035 2004-05-11 2008-10-02 Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications Abandoned US20090136009A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/244,035 US20090136009A1 (en) 2004-05-11 2008-10-02 Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/843,689 US7450696B2 (en) 2004-05-11 2004-05-11 Knowledge management, capture and modeling tool for multi-modal communications
US12/244,035 US20090136009A1 (en) 2004-05-11 2008-10-02 Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/843,689 Continuation US7450696B2 (en) 2004-05-11 2004-05-11 Knowledge management, capture and modeling tool for multi-modal communications

Publications (1)

Publication Number Publication Date
US20090136009A1 true US20090136009A1 (en) 2009-05-28

Family

ID=35309328

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/843,689 Active 2027-03-03 US7450696B2 (en) 2004-05-11 2004-05-11 Knowledge management, capture and modeling tool for multi-modal communications
US12/244,035 Abandoned US20090136009A1 (en) 2004-05-11 2008-10-02 Knowledge Management, Capture and Modeling Tool for Multi-Modal Communications

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/843,689 Active 2027-03-03 US7450696B2 (en) 2004-05-11 2004-05-11 Knowledge management, capture and modeling tool for multi-modal communications

Country Status (1)

Country Link
US (2) US7450696B2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070280457A1 (en) * 2006-06-02 2007-12-06 Aberethy Michael N Missed call integration with voicemail and granular access to voicemail
WO2014107455A1 (en) * 2013-01-03 2014-07-10 Amazon Technologies, Inc. Annotations of resources

Families Citing this family (64)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7450696B2 (en) * 2004-05-11 2008-11-11 At&T Intellectual Property I, L.P. Knowledge management, capture and modeling tool for multi-modal communications
US7921365B2 (en) 2005-02-15 2011-04-05 Microsoft Corporation System and method for browsing tabbed-heterogeneous windows
EP1932330A4 (en) * 2005-04-12 2011-05-04 Telecomm Systems Inc Temporary enum gateway
US8677377B2 (en) 2005-09-08 2014-03-18 Apple Inc. Method and apparatus for building an intelligent automated assistant
US20070088680A1 (en) * 2005-10-14 2007-04-19 Microsoft Corporation Simultaneously spawning multiple searches across multiple providers
DE102006004819B4 (en) * 2006-01-27 2007-12-20 Nokia Siemens Networks Gmbh & Co.Kg A multi-party communication method, arrangement, communication management server and communication terminal for carrying out a communication procedure with a plurality of participants
US7764951B2 (en) * 2006-04-20 2010-07-27 Cisco Technology, Inc. Techniques for tracking communication frequency across communication modalities
GB2439121B (en) * 2006-06-15 2009-10-21 Motorola Inc Apparatus and method for content item annotation
US9318108B2 (en) 2010-01-18 2016-04-19 Apple Inc. Intelligent automated assistant
KR101407055B1 (en) * 2006-10-13 2014-06-13 티-모바일 인터내셔널 아게 Method and device for exchanging messages in a mobile radio network
US8726297B2 (en) * 2007-06-28 2014-05-13 Microsoft Corporation Search tool that aggregates disparate tools unifying communication
US8996376B2 (en) 2008-04-05 2015-03-31 Apple Inc. Intelligent text-to-speech conversion
US8280962B2 (en) * 2008-04-08 2012-10-02 Cisco Technology, Inc. Service communication list
US20090254608A1 (en) * 2008-04-08 2009-10-08 David Butt Service communication list
EP2226979B1 (en) * 2009-03-03 2012-05-30 Alcatel Lucent Method for generating a report of the logs operated by a terminal through the Internet.
US10241752B2 (en) 2011-09-30 2019-03-26 Apple Inc. Interface for a virtual digital assistant
US10241644B2 (en) 2011-06-03 2019-03-26 Apple Inc. Actionable reminder entries
US9431006B2 (en) 2009-07-02 2016-08-30 Apple Inc. Methods and apparatuses for automatic speech recognition
US8682667B2 (en) 2010-02-25 2014-03-25 Apple Inc. User profiling for selecting user specific voice input processing information
US9721563B2 (en) 2012-06-08 2017-08-01 Apple Inc. Name recognition system
US9547647B2 (en) * 2012-09-19 2017-01-17 Apple Inc. Voice-based media searching
AU2013224669B2 (en) * 2012-10-12 2019-05-16 Cogware Pty Ltd A method and system for managing information for user participation
WO2014197334A2 (en) 2013-06-07 2014-12-11 Apple Inc. System and method for user-specified pronunciation of words for speech synthesis and recognition
US9430463B2 (en) 2014-05-30 2016-08-30 Apple Inc. Exemplar-based natural language processing
US10498899B2 (en) * 2014-06-16 2019-12-03 Karen Paulson Communication logging system
US9338493B2 (en) 2014-06-30 2016-05-10 Apple Inc. Intelligent automated assistant for TV user interactions
US9668121B2 (en) 2014-09-30 2017-05-30 Apple Inc. Social reminders
US10567477B2 (en) 2015-03-08 2020-02-18 Apple Inc. Virtual assistant continuity
US9578173B2 (en) 2015-06-05 2017-02-21 Apple Inc. Virtual assistant aided communication with 3rd party service in a communication session
US10671428B2 (en) 2015-09-08 2020-06-02 Apple Inc. Distributed personal assistant
US10747498B2 (en) 2015-09-08 2020-08-18 Apple Inc. Zero latency digital assistant
US10366158B2 (en) 2015-09-29 2019-07-30 Apple Inc. Efficient word encoding for recurrent neural network language models
US11010550B2 (en) 2015-09-29 2021-05-18 Apple Inc. Unified language modeling framework for word prediction, auto-completion and auto-correction
US10691473B2 (en) 2015-11-06 2020-06-23 Apple Inc. Intelligent automated assistant in a messaging environment
US10049668B2 (en) 2015-12-02 2018-08-14 Apple Inc. Applying neural network language models to weighted finite state transducers for automatic speech recognition
US10223066B2 (en) 2015-12-23 2019-03-05 Apple Inc. Proactive assistance based on dialog communication between devices
US10685290B2 (en) * 2015-12-29 2020-06-16 International Business Machines Corporation Parameter management through RDMA atomic operations
US10630835B2 (en) 2016-03-08 2020-04-21 T-Mobile Usa, Inc. Content sharing between related devices
US10446143B2 (en) 2016-03-14 2019-10-15 Apple Inc. Identification of voice inputs providing credentials
US9934775B2 (en) 2016-05-26 2018-04-03 Apple Inc. Unit-selection text-to-speech synthesis based on predicted concatenation parameters
US9972304B2 (en) 2016-06-03 2018-05-15 Apple Inc. Privacy preserving distributed evaluation framework for embedded personalized systems
US10249300B2 (en) 2016-06-06 2019-04-02 Apple Inc. Intelligent list reading
US10356745B2 (en) 2016-06-08 2019-07-16 T-Mobile Usa, Inc. Device and/or line event awareness and smart synchronization
US10049663B2 (en) 2016-06-08 2018-08-14 Apple, Inc. Intelligent automated assistant for media exploration
DK179309B1 (en) 2016-06-09 2018-04-23 Apple Inc Intelligent automated assistant in a home environment
US10509862B2 (en) 2016-06-10 2019-12-17 Apple Inc. Dynamic phrase expansion of language input
US10490187B2 (en) 2016-06-10 2019-11-26 Apple Inc. Digital assistant providing automated status report
US10192552B2 (en) 2016-06-10 2019-01-29 Apple Inc. Digital assistant providing whispered speech
US10586535B2 (en) 2016-06-10 2020-03-10 Apple Inc. Intelligent digital assistant in a multi-tasking environment
US10067938B2 (en) 2016-06-10 2018-09-04 Apple Inc. Multilingual word prediction
DK179343B1 (en) 2016-06-11 2018-05-14 Apple Inc Intelligent task discovery
DK201670540A1 (en) 2016-06-11 2018-01-08 Apple Inc Application integration with a digital assistant
DK179415B1 (en) 2016-06-11 2018-06-14 Apple Inc Intelligent device arbitration and control
DK179049B1 (en) 2016-06-11 2017-09-18 Apple Inc Data driven natural language event detection and classification
US10043516B2 (en) 2016-09-23 2018-08-07 Apple Inc. Intelligent automated assistant
US10593346B2 (en) 2016-12-22 2020-03-17 Apple Inc. Rank-reduced token representation for automatic speech recognition
DK201770439A1 (en) 2017-05-11 2018-12-13 Apple Inc. Offline personal assistant
DK179745B1 (en) 2017-05-12 2019-05-01 Apple Inc. SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT
DK179496B1 (en) 2017-05-12 2019-01-15 Apple Inc. USER-SPECIFIC Acoustic Models
DK201770431A1 (en) 2017-05-15 2018-12-20 Apple Inc. Optimizing dialogue policy decisions for digital assistants using implicit feedback
DK201770432A1 (en) 2017-05-15 2018-12-21 Apple Inc. Hierarchical belief states for digital assistants
DK179560B1 (en) 2017-05-16 2019-02-18 Apple Inc. Far-field extension for digital assistant services
US10701310B2 (en) 2017-06-23 2020-06-30 T-Mobile Usa, Inc. Video call continuity between devices via a telecommunications network
US10306071B1 (en) * 2017-09-15 2019-05-28 Fuze, Inc. Providing a unified communication history of a multi-modal communication

Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5323444A (en) * 1991-08-16 1994-06-21 U S West Advanced Technologies, Inc. Emergency call system with call capacity/last chance routing feature
US5379337A (en) * 1991-08-16 1995-01-03 U S West Advanced Technologies, Inc. Method and system for providing emergency call service
US5448630A (en) * 1991-07-15 1995-09-05 Barstow; L. Ed Secure programmable telecommunication timer
US5548749A (en) * 1993-10-29 1996-08-20 Wall Data Incorporated Semantic orbject modeling system for creating relational database schemas
US6240168B1 (en) * 1998-10-29 2001-05-29 Picazo Communications Method and apparatus for controlling a computer to implement telephone functions with a displayed telephone of variable size
US20010014143A1 (en) * 1996-10-10 2001-08-16 Envision Telephony, Inc. Non-random call center supervisory method and apparatus
US6295527B1 (en) * 1998-02-13 2001-09-25 Cisco Technology, Inc. Real-time user-defined creation of network device information collections
US20020024947A1 (en) * 2000-11-03 2002-02-28 Omer Luzzatti Communications availability
US20020158898A1 (en) * 2001-04-30 2002-10-31 Hsieh Vivian G. Graphical user interfaces for viewing and configuring devices in an automated provisioning environment
US20020174225A1 (en) * 2001-05-04 2002-11-21 Smith Mark C. Fractional replication in a directory server
US20030035522A1 (en) * 2001-08-14 2003-02-20 Carl Mansfield System and method for data backup in a home network telephone
US6560222B1 (en) * 1998-04-03 2003-05-06 Vertical Networks, Inc. Systems and methods for multiple voice and data communications using intelligently bridged TDM and packet buses and methods for performing telephony and data functions using the same
US6584490B1 (en) * 1998-10-30 2003-06-24 3Com Corporation System and method for providing call-handling services on a data network telephone system
US6611682B1 (en) * 1998-09-01 2003-08-26 Telefonaktiebolaget Lm Ericsson(Publ) Mobile telephone apparatus and method for call divert service
US6611533B1 (en) * 1999-01-13 2003-08-26 Nortel Networks Limited Public telephone network, intelligent network, and internet protocol network services interworking
US6636242B2 (en) * 1999-08-31 2003-10-21 Accenture Llp View configurer in a presentation services patterns environment
US6640249B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Presentation services patterns in a netcentric environment
US20030225879A1 (en) * 2001-12-28 2003-12-04 Jan Chipchase Communication log for an electronic device
US6690929B1 (en) * 1998-08-03 2004-02-10 Lucent Technologies Inc. Dynamic quality-of-service and pricing in communication system
US6703930B2 (en) * 2001-10-05 2004-03-09 Hewlett-Packard Development Company, L.P. Personal alerting apparatus and methods
US6707889B1 (en) * 1999-08-24 2004-03-16 Microstrategy Incorporated Multiple voice network access provider system and method
US6714635B1 (en) * 2002-09-10 2004-03-30 Voyant Technologies, Inc. Method for reservation-less instant group conferencing
US6738616B1 (en) * 1999-03-15 2004-05-18 Bellsouth Intellectual Property Corporation Automatic telephone service forwarding device
US20040097235A1 (en) * 2002-11-14 2004-05-20 Siegel Neil G. Voice hub processing
US6748057B2 (en) * 1998-06-05 2004-06-08 Netnumber, Inc. Method and apparatus for correlating a unique identifier, such as a PSTN telephone number, to an internet address to enable communications over the internet
US6748318B1 (en) * 1993-05-18 2004-06-08 Arrivalstar, Inc. Advanced notification systems and methods utilizing a computer network
US6748054B1 (en) * 1997-09-08 2004-06-08 Worldcom, Inc. Single telephone number access to multiple communications services
US6748062B2 (en) * 1997-04-25 2004-06-08 Sbc Properties, L.P. Method and system for generating a billing record
US6754323B1 (en) * 2001-12-19 2004-06-22 Bellsouth Intellectual Property Corporation Establishing a conference call from a call-log
US20040121790A1 (en) * 2002-04-03 2004-06-24 Ricoh Company, Ltd. Techniques for archiving audio information
US6768788B1 (en) * 1999-09-13 2004-07-27 Microstrategy, Incorporated System and method for real-time, personalized, dynamic, interactive voice services for property-related information
US6772109B2 (en) * 1997-06-10 2004-08-03 International Business Machines Corporation Message handling method, message handling apparatus, and memory media for storing a message handling apparatus controlling program
US20040233892A1 (en) * 2001-05-16 2004-11-25 Roberts Linda Ann Priority caller alert
US20040268265A1 (en) * 2003-06-30 2004-12-30 Berger Kelly D. Multi-mode communication apparatus and interface for contacting a user
US20050032527A1 (en) * 2003-08-08 2005-02-10 Networks In Motion, Inc. Method and system for collecting synchronizing, and reporting telecommunication call events and work flow related information
US6941345B1 (en) * 1999-12-03 2005-09-06 Nortel Networks Limited Real-time, text-based messaging between devices in plural communities
US6968050B1 (en) * 2002-03-27 2005-11-22 Verizon Services Corp. Methods and apparatus for authenticating and authorizing ENUM registrants
US7206806B2 (en) * 2001-05-30 2007-04-17 Pineau Richard A Method and system for remote utilizing a mobile device to share data objects
US7450696B2 (en) * 2004-05-11 2008-11-11 At&T Intellectual Property I, L.P. Knowledge management, capture and modeling tool for multi-modal communications
US7467210B1 (en) * 2004-04-02 2008-12-16 Cisco Technology, Inc. Method and system for automatically collecting information relating to calls to one or more associated endpoint devices

Patent Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5448630A (en) * 1991-07-15 1995-09-05 Barstow; L. Ed Secure programmable telecommunication timer
US5323444A (en) * 1991-08-16 1994-06-21 U S West Advanced Technologies, Inc. Emergency call system with call capacity/last chance routing feature
US5379337A (en) * 1991-08-16 1995-01-03 U S West Advanced Technologies, Inc. Method and system for providing emergency call service
US6748318B1 (en) * 1993-05-18 2004-06-08 Arrivalstar, Inc. Advanced notification systems and methods utilizing a computer network
US5548749A (en) * 1993-10-29 1996-08-20 Wall Data Incorporated Semantic orbject modeling system for creating relational database schemas
US20010014143A1 (en) * 1996-10-10 2001-08-16 Envision Telephony, Inc. Non-random call center supervisory method and apparatus
US6748062B2 (en) * 1997-04-25 2004-06-08 Sbc Properties, L.P. Method and system for generating a billing record
US6772109B2 (en) * 1997-06-10 2004-08-03 International Business Machines Corporation Message handling method, message handling apparatus, and memory media for storing a message handling apparatus controlling program
US6748054B1 (en) * 1997-09-08 2004-06-08 Worldcom, Inc. Single telephone number access to multiple communications services
US6295527B1 (en) * 1998-02-13 2001-09-25 Cisco Technology, Inc. Real-time user-defined creation of network device information collections
US6560222B1 (en) * 1998-04-03 2003-05-06 Vertical Networks, Inc. Systems and methods for multiple voice and data communications using intelligently bridged TDM and packet buses and methods for performing telephony and data functions using the same
US6748057B2 (en) * 1998-06-05 2004-06-08 Netnumber, Inc. Method and apparatus for correlating a unique identifier, such as a PSTN telephone number, to an internet address to enable communications over the internet
US6690929B1 (en) * 1998-08-03 2004-02-10 Lucent Technologies Inc. Dynamic quality-of-service and pricing in communication system
US6611682B1 (en) * 1998-09-01 2003-08-26 Telefonaktiebolaget Lm Ericsson(Publ) Mobile telephone apparatus and method for call divert service
US6240168B1 (en) * 1998-10-29 2001-05-29 Picazo Communications Method and apparatus for controlling a computer to implement telephone functions with a displayed telephone of variable size
US6584490B1 (en) * 1998-10-30 2003-06-24 3Com Corporation System and method for providing call-handling services on a data network telephone system
US6611533B1 (en) * 1999-01-13 2003-08-26 Nortel Networks Limited Public telephone network, intelligent network, and internet protocol network services interworking
US6738616B1 (en) * 1999-03-15 2004-05-18 Bellsouth Intellectual Property Corporation Automatic telephone service forwarding device
US6707889B1 (en) * 1999-08-24 2004-03-16 Microstrategy Incorporated Multiple voice network access provider system and method
US6636242B2 (en) * 1999-08-31 2003-10-21 Accenture Llp View configurer in a presentation services patterns environment
US6640249B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Presentation services patterns in a netcentric environment
US6768788B1 (en) * 1999-09-13 2004-07-27 Microstrategy, Incorporated System and method for real-time, personalized, dynamic, interactive voice services for property-related information
US6941345B1 (en) * 1999-12-03 2005-09-06 Nortel Networks Limited Real-time, text-based messaging between devices in plural communities
US20020024947A1 (en) * 2000-11-03 2002-02-28 Omer Luzzatti Communications availability
US20020158898A1 (en) * 2001-04-30 2002-10-31 Hsieh Vivian G. Graphical user interfaces for viewing and configuring devices in an automated provisioning environment
US20020174225A1 (en) * 2001-05-04 2002-11-21 Smith Mark C. Fractional replication in a directory server
US20040233892A1 (en) * 2001-05-16 2004-11-25 Roberts Linda Ann Priority caller alert
US7206806B2 (en) * 2001-05-30 2007-04-17 Pineau Richard A Method and system for remote utilizing a mobile device to share data objects
US20030035522A1 (en) * 2001-08-14 2003-02-20 Carl Mansfield System and method for data backup in a home network telephone
US6703930B2 (en) * 2001-10-05 2004-03-09 Hewlett-Packard Development Company, L.P. Personal alerting apparatus and methods
US6754323B1 (en) * 2001-12-19 2004-06-22 Bellsouth Intellectual Property Corporation Establishing a conference call from a call-log
US20030225879A1 (en) * 2001-12-28 2003-12-04 Jan Chipchase Communication log for an electronic device
US6968050B1 (en) * 2002-03-27 2005-11-22 Verizon Services Corp. Methods and apparatus for authenticating and authorizing ENUM registrants
US20040121790A1 (en) * 2002-04-03 2004-06-24 Ricoh Company, Ltd. Techniques for archiving audio information
US6714635B1 (en) * 2002-09-10 2004-03-30 Voyant Technologies, Inc. Method for reservation-less instant group conferencing
US20040097235A1 (en) * 2002-11-14 2004-05-20 Siegel Neil G. Voice hub processing
US20040268265A1 (en) * 2003-06-30 2004-12-30 Berger Kelly D. Multi-mode communication apparatus and interface for contacting a user
US20050032527A1 (en) * 2003-08-08 2005-02-10 Networks In Motion, Inc. Method and system for collecting synchronizing, and reporting telecommunication call events and work flow related information
US7467210B1 (en) * 2004-04-02 2008-12-16 Cisco Technology, Inc. Method and system for automatically collecting information relating to calls to one or more associated endpoint devices
US7450696B2 (en) * 2004-05-11 2008-11-11 At&T Intellectual Property I, L.P. Knowledge management, capture and modeling tool for multi-modal communications

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070280457A1 (en) * 2006-06-02 2007-12-06 Aberethy Michael N Missed call integration with voicemail and granular access to voicemail
US8594634B2 (en) * 2006-06-02 2013-11-26 International Business Machines Corporation Missed call integration with voicemail and granular access to voicemail
WO2014107455A1 (en) * 2013-01-03 2014-07-10 Amazon Technologies, Inc. Annotations of resources

Also Published As

Publication number Publication date
US7450696B2 (en) 2008-11-11
US20050254481A1 (en) 2005-11-17

Similar Documents

Publication Publication Date Title
US7450696B2 (en) Knowledge management, capture and modeling tool for multi-modal communications
US11831590B1 (en) Apparatus and method for context-driven determination of optimal cross- protocol communication delivery
CN101711469B (en) Voicemail filtering and transcription
JP5615922B2 (en) Mashups and presence found on the phone
US7257769B2 (en) System and method for indicating an annotation for a document
US7484213B2 (en) Agent architecture employed within an integrated message, document and communication system
US7027463B2 (en) System and method for multi-tiered rule filtering
CN101730879B (en) Voicemail filtering and transcription
US8560673B2 (en) Methods, systems and products for presenting information correlated to communications
US7441027B2 (en) Methods, systems, and products for creating message logs
US9843626B2 (en) Method, system and apparatus for controlling an application
US9026647B2 (en) Systems and methods for a social media network/business platform interface
US20140325002A1 (en) Methods and systems for a communications and information resource manager
US20060031340A1 (en) Apparatus and method for advanced attachment filtering within an integrated messaging platform
US20100174560A1 (en) Method, system and apparatus for assembling data associated with an emergency call event
US20060088144A1 (en) Method and apparatus for associating messages with data elements
CN101711381A (en) Voicemail filtering and transcription system
US20070172042A1 (en) Call urgency screening
US20160112358A1 (en) Apparatus and method for intelligent suppression of incoming multi-format multi-protocol communications
US20180188896A1 (en) Real-time context generation and blended input framework for morphing user interface manipulation and navigation
EP2723052A2 (en) System and method for in-context collaboration
JP2006126966A (en) Call center system
EP2095584B1 (en) Method and apparatus for one number mapping directory presence service

Legal Events

Date Code Title Description
AS Assignment

Owner name: AT&T INTELLECTUAL PROPERTY I, L.P., NEVADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VISHIK, CLAIRE SVETLANA;SURYANARAYANA, LALITHA;REEL/FRAME:021621/0562

Effective date: 20040813

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION