US20070300232A1 - Omnimodal messaging system - Google Patents
Omnimodal messaging system Download PDFInfo
- Publication number
- US20070300232A1 US20070300232A1 US11/899,474 US89947407A US2007300232A1 US 20070300232 A1 US20070300232 A1 US 20070300232A1 US 89947407 A US89947407 A US 89947407A US 2007300232 A1 US2007300232 A1 US 2007300232A1
- Authority
- US
- United States
- Prior art keywords
- message
- subsystems
- messaging
- metadata
- messages
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
- H04L51/066—Format adaptation, e.g. format conversion or compression
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
Definitions
- This invention relates in general to communications systems. More specifically, it relates to a generic, multi-media, multi-channel, messaging (server application) system.
- the messaging system is formed of loosely coupled subsystems that can handle message creation, receipt and response for any digitalizable message, in any format, via any popular messaging device, interface, or mode, that is received and delivered via any popular channel.
- Communications systems that interconnect users to transmit content are typically designed using an architecture, protocols, interfaces, end-user devices, etc., that are most effective for a given type of content, in a given format, transmitted on a known channel operating with a known protocol.
- a system for analog voice communications is often quite different from one for digital, data communications.
- a communication system is able to efficiently transmit messages of varying content and format using any of the common communications devices, channels, interfaces and modes.
- the variety of these options, and the competing design considerations inherent in the choices among these options has been an obstacle to the implementation of a generic or “universal” messaging system that can receive, process and deliver messages regardless of variations in these various system and message parameters.
- Past approaches to messaging systems have used the commonalities among the formats of the messages they process to design the most effective architecture for handling those formats. However, where commonalities are few, and where differences are significant, known approaches have cost or performance limitations.
- U.S. Pat. No. 6,345,288 discloses a communication system that transfers data, metadata and methods from a provider computer to a consumer computer via a network. Metadata is used to provide combined control between the consumer and provider computers of the types and content of information transferred. There is no separation of the metadata and message content, nor multi-modal synchronization of synchronous and asynchronous end user messages over multiple channels, as required in a truly universal communications system.
- U.S. Pat. No. 6,401,132 describes a content transformer operating on an input stream. There is no teaching of using such a transformer to provide a generic, multi-mode, multi-channel, synchronous and asynchronous communications over a network.
- U.S. Pat. No. 5,859,898 describes a Nynex system that can transmit both voice and data messages. However, it does not operate to accept multi-channel communication to the same device, there is no multi-modal synchronization, no integration to external messaging systems, the system is not massively distributed, and its operation does not separate and process independently the metadata and content of a message.
- Another principal object is to provide a Omnimodal messaging system with the foregoing advantages that also operates in conjunction with any common communications device, interface, or mode.
- Still another object is to provide these advantages for communications devices and protocols that are synchronous and asynchronous.
- a further object is to provide the foregoing advantages in a system that is also scalable.
- Yet another object is to provide the foregoing advantages while providing platform independent connections to external systems.
- Another object is to provide a communications system that can receive, process and deliver message content in any media as long as there is a logical mapping between the content types and a transformation module exists.
- the present invention viewed as a multimedia messaging system connects sender and recipient end-users.
- the system operates in a network or networks each having multiple sending and recipient nodes that can interface with other external messaging systems, messaging devices, or human operators.
- the messaging system includes three functional groups: interface/connector systems, core subsystems, and storage subsystems. They, in turn, are formed from ten subsystems.
- the interface/connector subsystems receive, process and deliver messages that include metadata and whose message content that can differ from message to message and type and be delivered to and from devices and computer platforms that can differ in type, over delivery channels, protocol and interface.
- the core subsystems including a content transformer, a multimedia messaging bus, and a metadata messaging bus, said buses interacting with all the interface/connector functional subsystems and the content transformer.
- the interface/connector, storage and core subsystems operate to:
- the end-users are enabled to manage their messages in an Omnimodal and in an asynchronous and synchronous manner including messages of different content types and formats in support of different interfaces, messaging devices, and modes of creation, receipt and response, via plural channels, using plural protocols, in support of plural messaging platforms.
- the core subsystems are loosely coupled—they interact, but they operate independently so that changes in one component does not necessarily require changes in other interconnected components.
- the present invention is a method for interconnecting plural communication devices communicating multimedia messages in a network or networks via sending and recipient nodes with messaging devices and systems or human operators external to the network or networks. It includes as steps:
- FIG. 1 is a block diagram showing the overall messaging server application architecture of the present invention
- FIG. 2 is a more detailed block diagram of the voice user interface gateway shown in FIG. 1 ;
- FIG. 3 is a more detailed block diagram of the data gateway shown in FIG. 1 illustrated to show pure HTTP and/or Web Service connections;
- FIG. 4 is more detailed block diagram of the messaging connector shown in FIG. 1 ;
- FIG. 5 is a more detailed block diagram of the content transformer shown in FIG. 1 .
- the messaging server application system 10 is designed to handle message creation, receipt, and response for any sort of digitizable message in any format, including, but not limited to, voicemail, email, short text (Short Message Service (SMS)), Multimedia Messaging Service (MMS), instant messages, and faxes, via any popular end user messaging device (phone, mobile phone, handheld computer, desktop/laptop computer, fax machine, converged devices), via any popular interface (Wireless Application Protocol (WAP) browser, voice interface, WAP/voice, SMS client, MMS client, Java client, Brew (Binary Run-time Environment for Wireless) client, web browser, thick IM client, etc.), in any mode (text, audio, still image, moving images, or combination thereof), and received or delivered via any popular channel (Public Switch Telephone Network (PSTN), Internet, etc.).
- PSTN Public Switch Telephone Network
- the messages handled by the system 10 can vary in content among the messages, or within the same message.
- the messaging server system 10 with these characteristics is termed, herein, “Omnimodal”. It typically operates as a “core application and application infrastructure” in a communications network or networks in the multiple sender, receiver and user modes of the same or varying design and operational characteristics.
- the messaging system 10 is assembled through machine-to-machine and/or human-to-machine interfaces.
- This generic or universal messaging system 10 uses a multi-media messaging server application architecture organized using a set of ten loosely-coupled subsystems: These subsystems, as detailed below, fall into three general functional groups 11 , 19 , and 26 .
- the first five of these subsystems 12 - 18 are interface/connector subsystems. They all interact with the world external to the application. They support all the interfaces. They also manage connections to external telecommunications and data networks as well as to external messaging systems. They are responsible for sending and receiving any popular kind of message in any popular mode for any popular device, as detailed above.
- the next three subsystems 20 , 22 , 24 can be thought of as the brains or core of the system. They extract message metadata (data about messages), including message type, format, mode of creation, address, originating device, subscriber, etc. They combine this metadata with information about the delivery and routing of the message provided by the networking infrastructure, information encapsulated in the user preferences and the user registry, as well as with instructions on how to process the message and the Metamessage itself. All these elements are contained within an element termed the “Metamessage” (Metamessage is “reflective”). The Metamessage is processed to determine what the system must do to deliver the original messaging; what content transformations (if any) need to be performed on the original message; what formats and interfaces will be used to deliver the original message. Original or transformed parts of the original message and/or a forerunner message may then be sent to external facing subsystems that then handle delivery.
- message metadata data about messages
- the Metamessage is processed to determine what the system must do to deliver the original messaging; what content
- the last set of subsystems, the Storage Subsystems 26 store all of the information used by the system, namely the messages themselves, Metamessages, subscriber preferences, and registry data.
- the system 10 handles any format, and avoids any architectural commitments that rely on format commonalties.
- the resulting system can be termed “format independent.”
- the core subsystems reduce any message to two sets of data—the message, and data about the message.
- the only assumption relied upon by the system is that all messages can be reduced to binary data.
- the Content Transformer 24 includes algorithms for converting message formats.
- the loosely-coupled nature of the subsystems enables modifications to one subsystem to occur without necessitating modifications to the others. As times goes on and new message formats are introduced into the market, this system will readily accommodate these new formats. An additional layer need not be added. To handle the new format, the system 10 simply adds a connector or interface to the interface/connector subsystems 12 - 18 , adds format conversion capability to the Content Transformer 24 , and adds any relevant compression technology to the storage subsystem 26 .
- the architecture itself need not change. “Loosely coupled” as used herein means that while the subsystems are operatively interconnected, they operate generally independently. For example, the content transformer operates asynchronously on message content as presented via the buses 20 and 22 . Also, a Metamessage is created and delivered on the bus 22 independently of the associated multi-media message content carried on the bus 20 . In the preferred form, the buses 20 and 22 are software buses, not hard wire buses, or the like.
- this subsystem 12 enables reception of any type of voice message through voice-specific channels 30 such as PSTN, IP telephony, packet-switched telephony, and other cellular telephony of which three representative channels are illustrated.
- the Voice Gateway 12 is an entry point that accommodates all of the different methods of connecting to the voice user interface, and makes all voice related interactions with the system appear the same to the rest of the system.
- the Voice Gateway 12 enables the other components of the system to treat voice without the concern for how the voice was obtained, or what format it is in.
- the Voice Gateway 12 itself is rendered with standards-compliant VoiceXML, thereby adhering to the Extensible Markup Language (XML) mandate of the architecture.
- XML Extensible Markup Language
- the Voice Gateway 12 includes functionality that enables it to synchronize multi-part messages that have one or more types of content. Since the Voice Gateway 12 is only designed to handle the voice portion of the content, through any voice channel, it will use a synchronization mechanism 32 (SMIL—Synchronized Multimedia Integration Language—compliant) to work with the Data Gateway 14 , the Multimedia Messaging Bus 20 , and other components in the system 10 .
- SMIL Synchronization Mechanism
- the Data Gateway 14 Much of the interaction between outside systems 34 (shown in FIG. 3 as three representative such systems 34 ) and the system 10 is done through the Data Gateway 14 .
- the Data Gateway 14 also handles connections for subscribers. The specific subscriber interfaces are rendered, by proxy, through the Content Transformer 24 and then sent out through the Data Gateway 14 .
- the Data Gateway enables reception of any type of data message through data specific channels 36 such as HTTP/XML, W-HTTP, i-mode, and BREW.
- the data gateway 14 offers access to the system 10 through various web service types including Simple Object Access Protocol (SOAP) 36 a and Xforms 36 b .
- SOAP 36 a allows external applications to communicate with the data gateway independent of the computer platform.
- SOAP 36 a can be thought of as an XML schema for remote procedure calls, like message retrieval.
- XForms enables rendering of generic interfaces.
- XForms interfaces can be transformed to specific user interface types at the node. In this way carriers can render proprietary subscriber interfaces that have pre-built interaction sets with the application.
- mobile carriers will be able to create their own subscriber interfaces in a more flexible and less costly way by simply creating one set of Extensible Stylesheet Language Transformations (XSLTs).
- XSLTs Extensible Stylesheet Language Transformations
- XForms 36 b is a World Wide Web Consortium (W3C) standard.
- W3C World Wide Web Consortium
- the subsystem 16 serves the same general function as the Data Gateway 14 , but is designed to receive/send any type of multimedia file or message format such as MMS, Moving Picture Experts Group (MPEG), MPEG-4, MPEG-7, FLIC, Audio Visual Interleaved (AVI), QuickTime Movie (MOV), Artificially Structured Films (ASF), Macromedia Flash, etc.
- MMS Moving Picture Experts Group
- MPEG-4 Moving Picture Experts Group
- MPEG-7 MPEG-7
- FLIC FLIC
- MOV QuickTime Movie
- AMF Artificially Structured Films
- Macromedia Flash etc.
- the subsystem 18 shown in FIG. 4 is designed to connect with external messaging systems such as Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP), Internet Messaging Access Protocol (IMAP), Short Message Service Center (SMSC), and Multimedia Messaging Service Center (MMSC).
- SMTP Simple Mail Transfer Protocol
- POP Post Office Protocol
- IMAP Internet Messaging Access Protocol
- SMSSC Short Message Service Center
- MMSC Multimedia Messaging Service Center
- the major task of the Multimodal Authenticator is to provide a secure mechanism for end users, be it user devices or foreign networks, to communicate with the Voice Genesis system.
- the Multimodal Authenticator provides authentication, authorization, and secure communication between all external interfaces to the Voice Genesis server systems and all foreign systems.
- This subsystem provides the following functionality: (1) Authenticating the user through a variety of modalities (voice-print, text-based password, etc.) In this way, we provide a user-friendly mechanism for authentication and authorization regardless of modality. (2) Integration with foreign systems that provide various levels of authorization or group-wise authentication. (3) A mechanism by which the distribution of users' messages amongst many different locations is made possible.
- the Multimodal Authenticator is used to facilitate an intelligent distribution of the data based on the last known connection status of the end user device.
- the Multimodal Authenticator enables the Voice Genesis servers to accept the same set of credentials for authentication and authorization.
- the Multimodal Authenticator is built by integrating existing standard authentication, authorization, and encryption mechanisms such as private-public key exchanges used in TLS/SSL. In cases where not relevant, such as voice printing (recognizing the user by using a pre-recorded voice segment that confirms liveliness and authentication), suitable known technique to modality is used to authenticate and authorize the user in a secure manner. While the Multimodal Authenticator is an amalgamation of existing authentication techniques and tools, it connects these tools and techniques together to offer a seamless and user-friendly authentication and authorization experience to the end users as well as facilitate ease of integration with foreign systems, each of which may have their own authentication and authorization systems.
- the Multimedia Messaging Bus 20 allows different types of media to be put in a queue and then processed. It solves several different requirements. First, it allows coordinated access to all of the contents of the message (regardless of what type of content is inside the message) by different processing subsystems (Content Transformer 24 , Storage Subsystem 26 , etc.). Second, it provides this access in a scalable and asynchronous manner. As a result spikes in message traffic do not cause the system 10 to halt. Finally, it permits the content of the message to be retrieved at run-time while the information about the message (on the Metadata Messaging Bus 22 ) is replicated to all of the different nodes on a distributed network.
- the Metadata Messaging Bus 22 transports Metamessages (as defined above) between subsystems, so subsystems can coordinate to process messages.
- the Interface/Connector Subsystems 11 create Metamessages that contain data about the original messages. These Metamessages are then placed on the Metadata Messaging Bus 22 .
- the Metamessages are themselves provided as messages on a queue. This enables the clients of the Multimedia Message Bus 22 to know needed information about the messages prior to actually processing the messages. This approach provides tunable performance and scalability.
- the subsystem 24 shown in detail in FIG. 5 transforms any popular message format into any other popular message format to facilitate message creation and delivery via any popular format, interface, device, mode, or channel.
- content transformation is done asynchronously, that is, on a deferred basis. This approach lessens the performance and scalability requirements inherent to synchronous systems. Transformation appears to be synchronous to the extent that processing resources are available. In other words, while the invention in its present preferred form operates asynchronously, that asynchronous operation can appear to be synchronous, e.g., if there is no queuing on the buses 20 and 22 .
- Transformable content includes any combination of text, still images, audio, and moving images. Because messages may include any combination of these content modes, the total number of combinations is twenty-four on both the sending and receiving side. These modes each contain multiple formats that must be supported.
- the set of subsystems 26 handles storage of the various content pieces of stored messages.
- the messages and parts of messages, whether text, still images, audio, and/or moving images, must be stored.
- These subsystems are comprised of several off the shelf components amongst which the most important are:
- the database 26 a is used to store the message metadata to facilitate searches, queries, and data mining.
- the database 26 a may also be used to store the text portion of messages.
- the multimedia or voice files are stored in their native format in a file storage systems 26 c and 26 b , respectively, and then be processed by the Content Transformer 24 to be played back to the user.
- the Content Transformer 24 can also write back to the Storage Subsystems 26 to use them as a caching mechanism, or to provide different types of file formats.
- file formats There are a variety of file formats each of which may require a particular type of storage as the system scales. Several standard compression methods are used to facilitate storage of various formats.
- the Storage Subsystems 26 a - c as shown are also designed to support streaming delivery of messages to recipients.
- LDAP Lightweight Directory Access Protocol
- JNDI Java Naming and Directory Interface
- the subsystems 26 can be considered as a single storage subsystem with sub-subsystems associated with various message types, and one or more sub-subsystem for message management and retrieval.
- bus is intended to include these alternative topologies. Still further, the two buses 20 and 22 can be implemented as a single bus using known transmission management techniques such as interleaving.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
- Communication Control (AREA)
Abstract
A messaging server application system handles message creation, receipt, and response for any sort of digitizable message in any format. It typically operates as a core application and application infrastructure in a communications network or networks in the multiple sender, receiver and user modes of the same or varying design and operational characteristics. The system uses an application architecture organized using a set of ten loosely-coupled subsystems falling into three general functional groups: interface/connector subsystems, core subsystems, and storage subsystems. The interface/connector subsystems include voice, data and multimedia gateways as well as message connectors and a multimodal authenticator. The core subsystems include a multimedia messaging bus, an independent metadata messaging bus, and a content transformer. The storage subsystem can include various storage subsystems. The core subsystems extract message metadata and combine this metadata with information about the delivery and routing of the message to form a “Metamessage”.
Description
- This invention relates in general to communications systems. More specifically, it relates to a generic, multi-media, multi-channel, messaging (server application) system. The messaging system is formed of loosely coupled subsystems that can handle message creation, receipt and response for any digitalizable message, in any format, via any popular messaging device, interface, or mode, that is received and delivered via any popular channel.
- Communications systems that interconnect users to transmit content are typically designed using an architecture, protocols, interfaces, end-user devices, etc., that are most effective for a given type of content, in a given format, transmitted on a known channel operating with a known protocol. A system for analog voice communications is often quite different from one for digital, data communications.
- Ideally, a communication system is able to efficiently transmit messages of varying content and format using any of the common communications devices, channels, interfaces and modes. However, the variety of these options, and the competing design considerations inherent in the choices among these options, has been an obstacle to the implementation of a generic or “universal” messaging system that can receive, process and deliver messages regardless of variations in these various system and message parameters. Past approaches to messaging systems have used the commonalities among the formats of the messages they process to design the most effective architecture for handling those formats. However, where commonalities are few, and where differences are significant, known approaches have cost or performance limitations. Some examples of attempts to provide a more versatile messaging system are provided by granted and applied-for patents.
- Published International Patent Application WO 01/09770, for example, describes a flexible rule-based information distribution system that selectively delivers messages generated by one or more originators to one or more recipients. The originator specifies rules to target a recipient, and a recipient also specifies rules by which to receive information. The rules refer to information that appears in user profiles and message data. There is no transformation of content, no synchronization of multi-modal, multi-channel communications, and no generic user interfaces to publish to multiple node interfaces.
- U.S. Pat. No. 6,345,288 discloses a communication system that transfers data, metadata and methods from a provider computer to a consumer computer via a network. Metadata is used to provide combined control between the consumer and provider computers of the types and content of information transferred. There is no separation of the metadata and message content, nor multi-modal synchronization of synchronous and asynchronous end user messages over multiple channels, as required in a truly universal communications system.
- U.S. Pat. No. 6,401,132 describes a content transformer operating on an input stream. There is no teaching of using such a transformer to provide a generic, multi-mode, multi-channel, synchronous and asynchronous communications over a network.
- U.S. Pat. No. 5,859,898 describes a Nynex system that can transmit both voice and data messages. However, it does not operate to accept multi-channel communication to the same device, there is no multi-modal synchronization, no integration to external messaging systems, the system is not massively distributed, and its operation does not separate and process independently the metadata and content of a message.
- Published US Patent Application No. US2002/0078151 discloses a system for communicating messages of various formats between diverse communications devices. It can transmit over PSTN or IP networks. However, it uses a layered design that builds on these networks, not an application architecture operable within a network or networks. It also operates on messages and their metadata in the traditional manner, as an integral message unit.
- In sum, while many solutions have been proposed or used for enhancing the capabilities of message communications systems, they solve some problems and add some capabilities, but there is no system that is truly universal and generic.
- It is therefore a principal object of this invention to provide an Omnimodal messaging system that can transmit multi-media messages received and delivered over multi-channels.
- Another principal object is to provide a Omnimodal messaging system with the foregoing advantages that also operates in conjunction with any common communications device, interface, or mode.
- Still another object is to provide these advantages for communications devices and protocols that are synchronous and asynchronous.
- A further object is to provide the foregoing advantages in a system that is also scalable.
- Yet another object is to provide the foregoing advantages while providing platform independent connections to external systems.
- Another object is to provide a communications system that can receive, process and deliver message content in any media as long as there is a logical mapping between the content types and a transformation module exists.
- The present invention viewed as a multimedia messaging system connects sender and recipient end-users. The system operates in a network or networks each having multiple sending and recipient nodes that can interface with other external messaging systems, messaging devices, or human operators. The messaging system includes three functional groups: interface/connector systems, core subsystems, and storage subsystems. They, in turn, are formed from ten subsystems.
- The interface/connector subsystems receive, process and deliver messages that include metadata and whose message content that can differ from message to message and type and be delivered to and from devices and computer platforms that can differ in type, over delivery channels, protocol and interface.
- The core subsystems including a content transformer, a multimedia messaging bus, and a metadata messaging bus, said buses interacting with all the interface/connector functional subsystems and the content transformer. The interface/connector, storage and core subsystems operate to:
-
- i. asynchronously, and with adequate processing resources, synchronously, produce, process and deliver a Metamessage on the meta data messaging bus independent of the processing and delivery of the original message, with the Metamessage containing instructions for processing the original message and the Metamessage used by the rest of the system to determine how it will process the original message;
- ii. reformat and translate all message content, if necessary, to a form compatible with the recipient; and
- iii. synchronize the receipt, processing and delivery of the messages to deliver such multimedia messages and to synchronize messages with other external messaging systems.
- Using this system the end-users are enabled to manage their messages in an Omnimodal and in an asynchronous and synchronous manner including messages of different content types and formats in support of different interfaces, messaging devices, and modes of creation, receipt and response, via plural channels, using plural protocols, in support of plural messaging platforms. The core subsystems are loosely coupled—they interact, but they operate independently so that changes in one component does not necessarily require changes in other interconnected components.
- Viewed as a process, the present invention is a method for interconnecting plural communication devices communicating multimedia messages in a network or networks via sending and recipient nodes with messaging devices and systems or human operators external to the network or networks. It includes as steps:
-
- interfacing with said networks, devices, systems and operators, and then separating the message being communicated into multimedia message output (or content) and related metada. A central aspect of this invention is the step of creating, processing and delivering a Metamessage on a bus independently of the multimedia message being delivered and processed.
- This processing includes reformatting and translating and storing message content as needed to be compatible with a recipient node. Another step involves synchronizing the receipt, processing, and delivery of the multimedia message content with external messaging systems.
- The invention will be more fully understood from the following detailed description which should be read in light of the accompanying drawings.
-
FIG. 1 is a block diagram showing the overall messaging server application architecture of the present invention; -
FIG. 2 . is a more detailed block diagram of the voice user interface gateway shown inFIG. 1 ; -
FIG. 3 is a more detailed block diagram of the data gateway shown inFIG. 1 illustrated to show pure HTTP and/or Web Service connections; -
FIG. 4 is more detailed block diagram of the messaging connector shown inFIG. 1 ; and, -
FIG. 5 is a more detailed block diagram of the content transformer shown inFIG. 1 . - The messaging
server application system 10 according to the present invention, shown in overview inFIG. 1 , is designed to handle message creation, receipt, and response for any sort of digitizable message in any format, including, but not limited to, voicemail, email, short text (Short Message Service (SMS)), Multimedia Messaging Service (MMS), instant messages, and faxes, via any popular end user messaging device (phone, mobile phone, handheld computer, desktop/laptop computer, fax machine, converged devices), via any popular interface (Wireless Application Protocol (WAP) browser, voice interface, WAP/voice, SMS client, MMS client, Java client, Brew (Binary Run-time Environment for Wireless) client, web browser, thick IM client, etc.), in any mode (text, audio, still image, moving images, or combination thereof), and received or delivered via any popular channel (Public Switch Telephone Network (PSTN), Internet, etc.). It is thus multi-modal. The messages handled by thesystem 10 can vary in content among the messages, or within the same message. Themessaging server system 10 with these characteristics is termed, herein, “Omnimodal”. It typically operates as a “core application and application infrastructure” in a communications network or networks in the multiple sender, receiver and user modes of the same or varying design and operational characteristics. Themessaging system 10 is assembled through machine-to-machine and/or human-to-machine interfaces. - This generic or
universal messaging system 10, termed herein as “Omnimodal”, uses a multi-media messaging server application architecture organized using a set of ten loosely-coupled subsystems: These subsystems, as detailed below, fall into three generalfunctional groups - Interface/
Connector Subsystems 11 - 1. Voice
User Interface Gateway 12 - 2.
Data Gateway 14 - 3.
Multimedia Gateway 16 - 4.
Message Connectors 18 - 5.
Multimodal Authenticator 15 -
Core Subsystems 19 - 6.
Multimedia Messaging Bus 20 - 7.
Metadata Messaging Bus 22 - 8.
Content Transformer 24 -
Storage Subsystems 26 - 9. Storage Subsystems (various) 26
- The first five of these subsystems 12-18 are interface/connector subsystems. They all interact with the world external to the application. They support all the interfaces. They also manage connections to external telecommunications and data networks as well as to external messaging systems. They are responsible for sending and receiving any popular kind of message in any popular mode for any popular device, as detailed above.
- The next three
subsystems - The last set of subsystems, the
Storage Subsystems 26, store all of the information used by the system, namely the messages themselves, Metamessages, subscriber preferences, and registry data. - The
system 10 handles any format, and avoids any architectural commitments that rely on format commonalties. The resulting system can be termed “format independent.” The core subsystems reduce any message to two sets of data—the message, and data about the message. The only assumption relied upon by the system is that all messages can be reduced to binary data. TheContent Transformer 24 includes algorithms for converting message formats. - The loosely-coupled nature of the subsystems enables modifications to one subsystem to occur without necessitating modifications to the others. As times goes on and new message formats are introduced into the market, this system will readily accommodate these new formats. An additional layer need not be added. To handle the new format, the
system 10 simply adds a connector or interface to the interface/connector subsystems 12-18, adds format conversion capability to theContent Transformer 24, and adds any relevant compression technology to thestorage subsystem 26. The architecture itself need not change. “Loosely coupled” as used herein means that while the subsystems are operatively interconnected, they operate generally independently. For example, the content transformer operates asynchronously on message content as presented via thebuses bus 22 independently of the associated multi-media message content carried on thebus 20. In the preferred form, thebuses - Subsystem Descriptions
-
Voice Gateway 12 - As shown in
FIG. 2 , thissubsystem 12 enables reception of any type of voice message through voice-specific channels 30 such as PSTN, IP telephony, packet-switched telephony, and other cellular telephony of which three representative channels are illustrated. TheVoice Gateway 12 is an entry point that accommodates all of the different methods of connecting to the voice user interface, and makes all voice related interactions with the system appear the same to the rest of the system. TheVoice Gateway 12 enables the other components of the system to treat voice without the concern for how the voice was obtained, or what format it is in. TheVoice Gateway 12 itself is rendered with standards-compliant VoiceXML, thereby adhering to the Extensible Markup Language (XML) mandate of the architecture. TheVoice Gateway 12 includes functionality that enables it to synchronize multi-part messages that have one or more types of content. Since theVoice Gateway 12 is only designed to handle the voice portion of the content, through any voice channel, it will use a synchronization mechanism 32 (SMIL—Synchronized Multimedia Integration Language—compliant) to work with theData Gateway 14, theMultimedia Messaging Bus 20, and other components in thesystem 10. -
Data Gateway 14 - Much of the interaction between outside systems 34 (shown in
FIG. 3 as three representative such systems 34) and thesystem 10 is done through theData Gateway 14. TheData Gateway 14 also handles connections for subscribers. The specific subscriber interfaces are rendered, by proxy, through theContent Transformer 24 and then sent out through theData Gateway 14. The Data Gateway enables reception of any type of data message through dataspecific channels 36 such as HTTP/XML, W-HTTP, i-mode, and BREW. Thedata gateway 14 offers access to thesystem 10 through various web service types including Simple Object Access Protocol (SOAP) 36 a and Xforms 36 b. SOAP 36 a allows external applications to communicate with the data gateway independent of the computer platform. SOAP 36 a can be thought of as an XML schema for remote procedure calls, like message retrieval. XForms enables rendering of generic interfaces. XForms interfaces can be transformed to specific user interface types at the node. In this way carriers can render proprietary subscriber interfaces that have pre-built interaction sets with the application. As a result, mobile carriers will be able to create their own subscriber interfaces in a more flexible and less costly way by simply creating one set of Extensible Stylesheet Language Transformations (XSLTs). Whereas a simple XML interface requires the customer to create workflow code, XForms streamlines this process by eliminating that requirement. XForms 36 b is a World Wide Web Consortium (W3C) standard. By providing these two distinct types of web service interfaces (SOAP and XForms), the application optimizes connectivity options for users of thesystem 10. The end result is an application that is more flexible and less costly to deploy than anything now available. -
Full Multimedia Gateway 16 - The
subsystem 16 serves the same general function as theData Gateway 14, but is designed to receive/send any type of multimedia file or message format such as MMS, Moving Picture Experts Group (MPEG), MPEG-4, MPEG-7, FLIC, Audio Visual Interleaved (AVI), QuickTime Movie (MOV), Artificially Structured Films (ASF), Macromedia Flash, etc. -
Message Connectors 18 - The
subsystem 18 shown inFIG. 4 is designed to connect with external messaging systems such as Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP), Internet Messaging Access Protocol (IMAP), Short Message Service Center (SMSC), and Multimedia Messaging Service Center (MMSC). This subsystem is able to exchange messages with other messaging systems outside of thesystem 10, as well as with theMultimedia Messaging Bus 20 andMetadata Messaging Bus 22. -
Multimodal Authenticator 15 - The major task of the Multimodal Authenticator is to provide a secure mechanism for end users, be it user devices or foreign networks, to communicate with the Voice Genesis system. The Multimodal Authenticator provides authentication, authorization, and secure communication between all external interfaces to the Voice Genesis server systems and all foreign systems. This subsystem provides the following functionality: (1) Authenticating the user through a variety of modalities (voice-print, text-based password, etc.) In this way, we provide a user-friendly mechanism for authentication and authorization regardless of modality. (2) Integration with foreign systems that provide various levels of authorization or group-wise authentication. (3) A mechanism by which the distribution of users' messages amongst many different locations is made possible. The Multimodal Authenticator is used to facilitate an intelligent distribution of the data based on the last known connection status of the end user device. (4) Integration with carrier authentication systems. This is done so that carriers can provide services using the
system 10 along side other services and the authentication is seamless to the end user. For example, if a user already has a user-name and password in the carrier network, the Multimodal Authenticator enables the Voice Genesis servers to accept the same set of credentials for authentication and authorization. - In implementation, the Multimodal Authenticator is built by integrating existing standard authentication, authorization, and encryption mechanisms such as private-public key exchanges used in TLS/SSL. In cases where not relevant, such as voice printing (recognizing the user by using a pre-recorded voice segment that confirms liveliness and authentication), suitable known technique to modality is used to authenticate and authorize the user in a secure manner. While the Multimodal Authenticator is an amalgamation of existing authentication techniques and tools, it connects these tools and techniques together to offer a seamless and user-friendly authentication and authorization experience to the end users as well as facilitate ease of integration with foreign systems, each of which may have their own authentication and authorization systems.
-
Multimedia Messaging Bus 20 - The
Multimedia Messaging Bus 20 allows different types of media to be put in a queue and then processed. It solves several different requirements. First, it allows coordinated access to all of the contents of the message (regardless of what type of content is inside the message) by different processing subsystems (Content Transformer 24,Storage Subsystem 26, etc.). Second, it provides this access in a scalable and asynchronous manner. As a result spikes in message traffic do not cause thesystem 10 to halt. Finally, it permits the content of the message to be retrieved at run-time while the information about the message (on the Metadata Messaging Bus 22) is replicated to all of the different nodes on a distributed network. -
Metadata Messaging Bus 22 - The
Metadata Messaging Bus 22 transports Metamessages (as defined above) between subsystems, so subsystems can coordinate to process messages. In order to provide a decoupling between messages and information about the messages in the presently preferred form of the invention, the Interface/Connector Subsystems 11 create Metamessages that contain data about the original messages. These Metamessages are then placed on theMetadata Messaging Bus 22. The Metamessages are themselves provided as messages on a queue. This enables the clients of theMultimedia Message Bus 22 to know needed information about the messages prior to actually processing the messages. This approach provides tunable performance and scalability. -
Content Transformer 24 - The
subsystem 24 shown in detail inFIG. 5 transforms any popular message format into any other popular message format to facilitate message creation and delivery via any popular format, interface, device, mode, or channel. In one form of the invention that is more easily implemented, content transformation is done asynchronously, that is, on a deferred basis. This approach lessens the performance and scalability requirements inherent to synchronous systems. Transformation appears to be synchronous to the extent that processing resources are available. In other words, while the invention in its present preferred form operates asynchronously, that asynchronous operation can appear to be synchronous, e.g., if there is no queuing on thebuses - Transformable content includes any combination of text, still images, audio, and moving images. Because messages may include any combination of these content modes, the total number of combinations is twenty-four on both the sending and receiving side. These modes each contain multiple formats that must be supported.
-
Storage Subsystems 26 - The set of
subsystems 26 handles storage of the various content pieces of stored messages. The messages and parts of messages, whether text, still images, audio, and/or moving images, must be stored. These subsystems are comprised of several off the shelf components amongst which the most important are: - Text Message Storage: The
database 26 a is used to store the message metadata to facilitate searches, queries, and data mining. Thedatabase 26 a may also be used to store the text portion of messages. - File Storage: The multimedia or voice files are stored in their native format in a
file storage systems Content Transformer 24 to be played back to the user. TheContent Transformer 24 can also write back to theStorage Subsystems 26 to use them as a caching mechanism, or to provide different types of file formats. There are a variety of file formats each of which may require a particular type of storage as the system scales. Several standard compression methods are used to facilitate storage of various formats. TheStorage Subsystems 26 a-c as shown are also designed to support streaming delivery of messages to recipients. - LDAP: A Lightweight Directory Access Protocol (LDAP) implementation is used with
storage subsystem 26 to find the location of the stored files. LDAP is a set of protocols based on standards within the X.500 standard, but simplified, and allows any type of Internet access. It runs almost any application and is compatible with all popular computer platforms. Java Naming and Directory Interface (JNDI) interfaces are provided to facilitate fail-over capabilities. - The
subsystems 26 can be considered as a single storage subsystem with sub-subsystems associated with various message types, and one or more sub-subsystem for message management and retrieval. - While this invention has been described with respect to its preferred embodiments, it will be understood that various modifications and alterations will occur to those skilled in the art from the foregoing detailed description and the accompanying drawings. For example, other numbers of subsystems can be used intercommunicating through other bus architectures besides two parallel buses that open multi-media messages and Metamessages. The
system 10 is readily scalable, up or down. In each variation, however, data about a message is separated from the message itself; a new message is then created to hold this data; the original message and new message are processed as independent messages; the new message is used by the system to determine how to process the original message. While it is possible to utilize non-bus network topologies, e.g. a star or ring topology, the bus implementation described and illustrated is presently preferred as the most readily implemented topology that touches all of the subsystems. As used herein, the term “bus” is intended to include these alternative topologies. Still further, the twobuses
Claims (2)
1-2. (canceled)
3. A method for interconnecting plural communication devices communicating multimedia messages and metadata in a network or networks via sending and recipient nodes with messaging devices and systems or human operators external to the network or networks, comprising:
interfacing with said networks, devices, systems and operators, separating the message being communicated into multimedia message output and related metadata,
creating, processing and delivering a metamessage on a bus independently of said multimedia message being delivered and processed,
said processing including reformatting and translating and storing message content as needed to be compatible with a recipient node, and
synchronizing said receipt, processing, and delivery of the multimedia message content and the external messaging systems.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/899,474 US20070300232A1 (en) | 2003-04-22 | 2007-09-06 | Omnimodal messaging system |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US46443603P | 2003-04-22 | 2003-04-22 | |
US10/830,611 US7277951B2 (en) | 2003-04-22 | 2004-04-22 | Omnimodal messaging system |
US11/899,474 US20070300232A1 (en) | 2003-04-22 | 2007-09-06 | Omnimodal messaging system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/830,611 Continuation US7277951B2 (en) | 2003-04-22 | 2004-04-22 | Omnimodal messaging system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070300232A1 true US20070300232A1 (en) | 2007-12-27 |
Family
ID=33310889
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/830,611 Expired - Fee Related US7277951B2 (en) | 2003-04-22 | 2004-04-22 | Omnimodal messaging system |
US11/899,474 Abandoned US20070300232A1 (en) | 2003-04-22 | 2007-09-06 | Omnimodal messaging system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/830,611 Expired - Fee Related US7277951B2 (en) | 2003-04-22 | 2004-04-22 | Omnimodal messaging system |
Country Status (10)
Country | Link |
---|---|
US (2) | US7277951B2 (en) |
EP (1) | EP1623335A4 (en) |
KR (1) | KR20060011963A (en) |
CN (1) | CN100416541C (en) |
AU (1) | AU2004232040A1 (en) |
BR (1) | BRPI0409618A (en) |
CA (1) | CA2522429A1 (en) |
MX (1) | MXPA05011205A (en) |
RU (1) | RU2005134907A (en) |
WO (1) | WO2004095197A2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097247A1 (en) * | 1999-12-30 | 2005-05-05 | James Morrow | Meta-message set with real-time and database aspects |
US20080215717A1 (en) * | 2005-04-27 | 2008-09-04 | International Business Machines Corporation | Web Based Unified Communication System and Method, and Web Communication Manager |
US20090195546A1 (en) * | 2008-02-05 | 2009-08-06 | Konica Minolta Business Technologies, Inc. | Image distribution apparatus, image distribution method, and image distribution program |
US20100063989A1 (en) * | 2008-09-11 | 2010-03-11 | At&T Intellectual Property I, L.P. | Apparatus and method for delivering media content |
Families Citing this family (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7302634B2 (en) | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US9886309B2 (en) | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US7966374B2 (en) * | 2002-07-01 | 2011-06-21 | Profiliq Software Inc. | Adaptive media messaging, such as for rich media messages incorporating digital content |
US7707317B2 (en) * | 2002-07-01 | 2010-04-27 | Prolifiq Software Inc. | Adaptive electronic messaging |
US7356622B2 (en) * | 2003-05-29 | 2008-04-08 | International Business Machines Corporation | Method and apparatus for managing and formatting metadata in an autonomous operation conducted by a third party |
EP1501320A1 (en) * | 2003-07-24 | 2005-01-26 | France Telecom | Method and system for placing messages in the inbox of a message service |
US20050078658A1 (en) * | 2003-10-09 | 2005-04-14 | Mclennan James | Automatic communication method and system |
GB0323625D0 (en) * | 2003-10-09 | 2003-11-12 | Thunderhead Ltd | Method and system for automatic modifiable messages |
US7610557B2 (en) * | 2003-10-09 | 2009-10-27 | Thunderhead Limited | Automatic response interface |
KR101005986B1 (en) * | 2003-11-14 | 2011-01-05 | 에스케이 텔레콤주식회사 | Method for forwarding multimedia message in mobile communication system |
US7873742B1 (en) * | 2003-11-20 | 2011-01-18 | Microsoft Corporation | Providing content per delivery endpoint |
US7434158B2 (en) * | 2003-12-10 | 2008-10-07 | International Business Machines Corporation | Presenting multimodal web page content on sequential multimode devices |
WO2006020938A2 (en) * | 2004-08-14 | 2006-02-23 | Kirusa, Inc. | Methods for identifying messages and communicating with users of a multimodal message service |
US20060047761A1 (en) * | 2004-08-30 | 2006-03-02 | Matsushita Electric Industrial Co., Ltd. | Mechanism to support transparent roaming between IMP service providers in wireless networks |
US8161117B2 (en) | 2004-09-03 | 2012-04-17 | Oracle International Corporation | Multi-media messaging |
US20060117009A1 (en) * | 2004-11-30 | 2006-06-01 | Joe Matthew D | Declarative aspects and aspect containers for application development |
US7617481B2 (en) * | 2004-11-30 | 2009-11-10 | Avanade Holdings Llc | Prescriptive architecture for application development |
CN100456753C (en) * | 2005-07-13 | 2009-01-28 | 华为技术有限公司 | Message matching method and system |
US7739696B2 (en) * | 2005-09-08 | 2010-06-15 | Honeywell International Inc. | Message translation systems and methods |
US20070208587A1 (en) * | 2005-12-08 | 2007-09-06 | Arun Sitaraman | Systems, software, and methods for communication-based business process messaging |
US20070162421A1 (en) * | 2006-01-12 | 2007-07-12 | Sybase, Inc. | Real-Time Messaging System for Bridging RDBMSs and Message Buses |
US7542982B2 (en) | 2006-09-05 | 2009-06-02 | International Business Machines Corporation | Message validation model |
US20080059577A1 (en) * | 2006-09-05 | 2008-03-06 | Suman Kumar Kalia | Scalable logical model for edi and system and method for creating, mapping and parsing edi messages |
US20080059506A1 (en) * | 2006-09-05 | 2008-03-06 | Suman Kumar Kalia | Method, system and schema for building a hierarchical model schema definition from a flat model definition |
US20080096532A1 (en) * | 2006-10-24 | 2008-04-24 | International Business Machines Corporation | Emotional state integrated messaging |
EP2087746B1 (en) * | 2006-11-13 | 2014-02-26 | Samsung Electronics Co., Ltd. | System and method for providing converged messaging service |
CN101083636B (en) * | 2007-07-18 | 2011-12-28 | 中兴通讯股份有限公司 | Method, equipment and system for realizing internet mail service and mobile application intercommunication |
KR100979202B1 (en) * | 2007-11-21 | 2010-09-01 | 한국전자통신연구원 | The method of message service and message service system |
GB0807296D0 (en) * | 2008-04-22 | 2008-05-28 | Thunderhead Ltd | Template author and method of driving data capture in document templates |
WO2009133544A1 (en) * | 2008-05-02 | 2009-11-05 | Markport Limited | A messaging device and server system |
US8881020B2 (en) * | 2008-06-24 | 2014-11-04 | Microsoft Corporation | Multi-modal communication through modal-specific interfaces |
US20110007732A1 (en) * | 2009-07-08 | 2011-01-13 | John Ward | Unified Communication System |
JP2011130279A (en) * | 2009-12-18 | 2011-06-30 | Sony Corp | Content providing server, content reproducing apparatus, content providing method, content reproducing method, program and content providing system |
US9183543B2 (en) * | 2010-02-19 | 2015-11-10 | Prolifiq Software Inc. | Tracking digital content objects |
CN102088464A (en) * | 2011-01-29 | 2011-06-08 | 廖锦新 | Protocol device and method for achieving data transmission of objects or apparatuses of various kinds of buses |
US9432237B2 (en) | 2011-02-16 | 2016-08-30 | Clearone, Inc. | VOIP device, VOIP conferencing system, and related method |
CN102256221B (en) * | 2011-05-07 | 2014-03-19 | 杭州仁盈科技有限公司 | Rapid multimedia color display transmission method |
US20130097333A1 (en) * | 2011-06-12 | 2013-04-18 | Clearone Communications, Inc. | Methods and apparatuses for unified streaming communication |
US8611506B2 (en) | 2011-07-08 | 2013-12-17 | Blackberry Limited | Methods and apparatus to facilitate voicemail interaction |
US9385981B2 (en) * | 2012-07-23 | 2016-07-05 | Google Inc. | System and method for providing multi-modal asynchronous communication |
WO2014052869A1 (en) * | 2012-09-28 | 2014-04-03 | Go Factory, LLC | A massively distributed cloud-based platform providing features as a service to support mobile and web applications |
US9749321B2 (en) | 2013-01-22 | 2017-08-29 | Prolifiq Software Inc. | System for multi-point publication syndication |
US11064326B2 (en) | 2013-10-03 | 2021-07-13 | Nokia Of America Corporation | Creating, joining, finding, discovering, restoring and relocating process-based channels |
US10728190B2 (en) * | 2017-06-29 | 2020-07-28 | Salesforce.Com, Inc. | Form based user interactions via messaging channels |
US11698891B2 (en) * | 2019-07-30 | 2023-07-11 | Salesforce.Com, Inc. | Database systems and related multichannel communication methods |
Citations (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5790809A (en) * | 1995-11-17 | 1998-08-04 | Mci Corporation | Registry communications middleware |
US5832221A (en) * | 1995-12-29 | 1998-11-03 | At&T Corp | Universal message storage system |
US5859898A (en) * | 1996-09-17 | 1999-01-12 | Nynex Science & Technology | Messaging architecture supporting digital and analog media |
US5892916A (en) * | 1997-12-23 | 1999-04-06 | Gehlhaar; Jeff B. | Network management system and method using a partial response table |
US5978834A (en) * | 1997-09-30 | 1999-11-02 | The United States Of America As Represented By The Secretary Of The Navy | Platform independent computer interface software responsive to scripted commands |
US6055240A (en) * | 1997-06-12 | 2000-04-25 | Nortel Networks Corporation | Method and apparatus for message management |
US6092114A (en) * | 1998-04-17 | 2000-07-18 | Siemens Information And Communication Networks, Inc. | Method and system for determining the location for performing file-format conversions of electronics message attachments |
US6111893A (en) * | 1997-07-31 | 2000-08-29 | Cisco Technology, Inc. | Universal protocol conversion |
US6125387A (en) * | 1997-09-30 | 2000-09-26 | The United States Of America Represented By The Secretary Of The Navy | Operating methods for robust computer systems permitting autonomously switching between alternative/redundant |
US6172988B1 (en) * | 1996-01-31 | 2001-01-09 | Tiernan Communications, Inc. | Method for universal messaging and multiplexing of video, audio, and data streams |
US6216173B1 (en) * | 1998-02-03 | 2001-04-10 | Redbox Technologies Limited | Method and apparatus for content processing and routing |
US20010047298A1 (en) * | 2000-03-31 | 2001-11-29 | United Video Properties,Inc. | System and method for metadata-linked advertisements |
US20010049721A1 (en) * | 1999-11-24 | 2001-12-06 | John Blair | Method and system for continuous interactive communication in an electronic network |
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US6401132B1 (en) * | 1999-08-03 | 2002-06-04 | International Business Machines Corporation | Subchaining transcoders in a transcoding framework |
US20020078151A1 (en) * | 2000-12-15 | 2002-06-20 | Wickam Bryce C. | System for communicating messages of various formats between diverse communication devices |
US6412011B1 (en) * | 1998-09-14 | 2002-06-25 | At&T Corp. | Method and apparatus to enhance a multicast information stream in a communication network |
US6430604B1 (en) * | 1999-08-03 | 2002-08-06 | International Business Machines Corporation | Technique for enabling messaging systems to use alternative message delivery mechanisms |
US20020128908A1 (en) * | 2000-09-15 | 2002-09-12 | Levin Brian E. | System for conducting user-specific promotional campaigns using multiple communications device platforms |
US20020133515A1 (en) * | 2001-03-16 | 2002-09-19 | Kagle Jonathan C. | Method and apparatus for synchronizing multiple versions of digital data |
US20020138582A1 (en) * | 2000-09-05 | 2002-09-26 | Mala Chandra | Methods and apparatus providing electronic messages that are linked and aggregated |
US20020184047A1 (en) * | 2001-04-03 | 2002-12-05 | Plotnick Michael A. | Universal ad queue |
US20030001880A1 (en) * | 2001-04-18 | 2003-01-02 | Parkervision, Inc. | Method, system, and computer program product for producing and distributing enhanced media |
US20030040300A1 (en) * | 2001-08-27 | 2003-02-27 | Alcatel | System of interoperability between MMS messages and SMS/EMS messages and an associated exchange method |
US20030061369A1 (en) * | 2001-09-24 | 2003-03-27 | Emre Aksu | Processing of multimedia data |
US20030065805A1 (en) * | 2000-06-29 | 2003-04-03 | Barnes Melvin L. | System, method, and computer program product for providing location based services and mobile e-commerce |
US20030132953A1 (en) * | 2002-01-16 | 2003-07-17 | Johnson Bruce Alan | Data preparation for media browsing |
US20030152203A1 (en) * | 2002-02-13 | 2003-08-14 | Berger Adam L. | Message accessing |
US20040002049A1 (en) * | 2002-07-01 | 2004-01-01 | Jay Beavers | Computer network-based, interactive, multimedia learning system and process |
US20040128342A1 (en) * | 2002-12-31 | 2004-07-01 | International Business Machines Corporation | System and method for providing multi-modal interactive streaming media applications |
US20040140989A1 (en) * | 2002-05-28 | 2004-07-22 | John Papageorge | Content subscription and delivery service |
US20050021826A1 (en) * | 2003-04-21 | 2005-01-27 | Sunil Kumar | Gateway controller for a multimodal system that provides inter-communication among different data and voice servers through various mobile devices, and interface for that controller |
US6963972B1 (en) * | 2000-09-26 | 2005-11-08 | International Business Machines Corporation | Method and apparatus for networked information dissemination through secure transcoding |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6826407B1 (en) | 1999-03-29 | 2004-11-30 | Richard J. Helferich | System and method for integrating audio and visual messaging |
CA2275840A1 (en) * | 1998-08-18 | 2000-02-18 | Lucent Technologies Inc. | Generalized messaging construct |
US6741992B1 (en) | 1999-07-29 | 2004-05-25 | Xtenit | Flexible rule-based communication system and method for controlling the flow of and access to information between computer users |
US20030140112A1 (en) * | 1999-11-04 | 2003-07-24 | Satish Ramachandran | Electronic messaging system method and apparatus |
EP1133101A1 (en) | 2000-03-07 | 2001-09-12 | BRITISH TELECOMMUNICATIONS public limited company | Data distribution |
US7058586B1 (en) | 2000-06-06 | 2006-06-06 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
CA2355420A1 (en) | 2000-08-30 | 2002-02-28 | Comverse Network Systems, Ltd. | Method and apparatus for mobile originated voice messaging |
US20020097692A1 (en) | 2000-12-29 | 2002-07-25 | Nokia Mobile Phones Ltd. | User interface for a mobile station |
EP1280326A1 (en) | 2001-07-25 | 2003-01-29 | The Sound of Data B.V. | Sending a voicemail message as an email attachment with a voice controlled interface for authentication |
US20030065724A1 (en) * | 2001-09-28 | 2003-04-03 | Openwave Systems Inc. | Managing messages in unified messaging systems |
US20040176114A1 (en) | 2003-03-06 | 2004-09-09 | Northcutt John W. | Multimedia and text messaging with speech-to-text assistance |
-
2004
- 2004-04-22 BR BRPI0409618-5A patent/BRPI0409618A/en not_active IP Right Cessation
- 2004-04-22 CA CA002522429A patent/CA2522429A1/en not_active Abandoned
- 2004-04-22 AU AU2004232040A patent/AU2004232040A1/en not_active Abandoned
- 2004-04-22 CN CNB2004800108646A patent/CN100416541C/en not_active Expired - Fee Related
- 2004-04-22 RU RU2005134907/09A patent/RU2005134907A/en not_active Application Discontinuation
- 2004-04-22 MX MXPA05011205A patent/MXPA05011205A/en not_active Application Discontinuation
- 2004-04-22 EP EP04750501A patent/EP1623335A4/en not_active Withdrawn
- 2004-04-22 US US10/830,611 patent/US7277951B2/en not_active Expired - Fee Related
- 2004-04-22 KR KR1020057020064A patent/KR20060011963A/en not_active Application Discontinuation
- 2004-04-22 WO PCT/US2004/012466 patent/WO2004095197A2/en active Application Filing
-
2007
- 2007-09-06 US US11/899,474 patent/US20070300232A1/en not_active Abandoned
Patent Citations (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6345288B1 (en) * | 1989-08-31 | 2002-02-05 | Onename Corporation | Computer-based communication system and method using metadata defining a control-structure |
US5790809A (en) * | 1995-11-17 | 1998-08-04 | Mci Corporation | Registry communications middleware |
US5832221A (en) * | 1995-12-29 | 1998-11-03 | At&T Corp | Universal message storage system |
US6172988B1 (en) * | 1996-01-31 | 2001-01-09 | Tiernan Communications, Inc. | Method for universal messaging and multiplexing of video, audio, and data streams |
US5859898A (en) * | 1996-09-17 | 1999-01-12 | Nynex Science & Technology | Messaging architecture supporting digital and analog media |
US6055240A (en) * | 1997-06-12 | 2000-04-25 | Nortel Networks Corporation | Method and apparatus for message management |
US6111893A (en) * | 1997-07-31 | 2000-08-29 | Cisco Technology, Inc. | Universal protocol conversion |
US5978834A (en) * | 1997-09-30 | 1999-11-02 | The United States Of America As Represented By The Secretary Of The Navy | Platform independent computer interface software responsive to scripted commands |
US6125387A (en) * | 1997-09-30 | 2000-09-26 | The United States Of America Represented By The Secretary Of The Navy | Operating methods for robust computer systems permitting autonomously switching between alternative/redundant |
US5892916A (en) * | 1997-12-23 | 1999-04-06 | Gehlhaar; Jeff B. | Network management system and method using a partial response table |
US6216173B1 (en) * | 1998-02-03 | 2001-04-10 | Redbox Technologies Limited | Method and apparatus for content processing and routing |
US6092114A (en) * | 1998-04-17 | 2000-07-18 | Siemens Information And Communication Networks, Inc. | Method and system for determining the location for performing file-format conversions of electronics message attachments |
US6412011B1 (en) * | 1998-09-14 | 2002-06-25 | At&T Corp. | Method and apparatus to enhance a multicast information stream in a communication network |
US6401132B1 (en) * | 1999-08-03 | 2002-06-04 | International Business Machines Corporation | Subchaining transcoders in a transcoding framework |
US6430604B1 (en) * | 1999-08-03 | 2002-08-06 | International Business Machines Corporation | Technique for enabling messaging systems to use alternative message delivery mechanisms |
US20010049721A1 (en) * | 1999-11-24 | 2001-12-06 | John Blair | Method and system for continuous interactive communication in an electronic network |
US20010047298A1 (en) * | 2000-03-31 | 2001-11-29 | United Video Properties,Inc. | System and method for metadata-linked advertisements |
US20030065805A1 (en) * | 2000-06-29 | 2003-04-03 | Barnes Melvin L. | System, method, and computer program product for providing location based services and mobile e-commerce |
US20020138582A1 (en) * | 2000-09-05 | 2002-09-26 | Mala Chandra | Methods and apparatus providing electronic messages that are linked and aggregated |
US20020128908A1 (en) * | 2000-09-15 | 2002-09-12 | Levin Brian E. | System for conducting user-specific promotional campaigns using multiple communications device platforms |
US6963972B1 (en) * | 2000-09-26 | 2005-11-08 | International Business Machines Corporation | Method and apparatus for networked information dissemination through secure transcoding |
US20020078151A1 (en) * | 2000-12-15 | 2002-06-20 | Wickam Bryce C. | System for communicating messages of various formats between diverse communication devices |
US20020133515A1 (en) * | 2001-03-16 | 2002-09-19 | Kagle Jonathan C. | Method and apparatus for synchronizing multiple versions of digital data |
US20020184047A1 (en) * | 2001-04-03 | 2002-12-05 | Plotnick Michael A. | Universal ad queue |
US20030001880A1 (en) * | 2001-04-18 | 2003-01-02 | Parkervision, Inc. | Method, system, and computer program product for producing and distributing enhanced media |
US20030040300A1 (en) * | 2001-08-27 | 2003-02-27 | Alcatel | System of interoperability between MMS messages and SMS/EMS messages and an associated exchange method |
US20030061369A1 (en) * | 2001-09-24 | 2003-03-27 | Emre Aksu | Processing of multimedia data |
US20030132953A1 (en) * | 2002-01-16 | 2003-07-17 | Johnson Bruce Alan | Data preparation for media browsing |
US20030152203A1 (en) * | 2002-02-13 | 2003-08-14 | Berger Adam L. | Message accessing |
US20040140989A1 (en) * | 2002-05-28 | 2004-07-22 | John Papageorge | Content subscription and delivery service |
US20040002049A1 (en) * | 2002-07-01 | 2004-01-01 | Jay Beavers | Computer network-based, interactive, multimedia learning system and process |
US20040128342A1 (en) * | 2002-12-31 | 2004-07-01 | International Business Machines Corporation | System and method for providing multi-modal interactive streaming media applications |
US20050021826A1 (en) * | 2003-04-21 | 2005-01-27 | Sunil Kumar | Gateway controller for a multimodal system that provides inter-communication among different data and voice servers through various mobile devices, and interface for that controller |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050097247A1 (en) * | 1999-12-30 | 2005-05-05 | James Morrow | Meta-message set with real-time and database aspects |
US7721006B2 (en) * | 1999-12-30 | 2010-05-18 | Bally Gaming, Inc. | Meta-message set with real-time and database aspects |
US20080215717A1 (en) * | 2005-04-27 | 2008-09-04 | International Business Machines Corporation | Web Based Unified Communication System and Method, and Web Communication Manager |
JP2008539627A (en) * | 2005-04-27 | 2008-11-13 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Web-based integrated communication system and method, and web communication manager |
US8565267B2 (en) | 2005-04-27 | 2013-10-22 | International Business Machines Corporation | Web based unified communication system and method, and web communication manager |
US20090195546A1 (en) * | 2008-02-05 | 2009-08-06 | Konica Minolta Business Technologies, Inc. | Image distribution apparatus, image distribution method, and image distribution program |
US8325191B2 (en) * | 2008-02-05 | 2012-12-04 | Konica Minolta Business Technologies, Inc. | Image distribution apparatus, image distribution method, and image distribution program |
US20100063989A1 (en) * | 2008-09-11 | 2010-03-11 | At&T Intellectual Property I, L.P. | Apparatus and method for delivering media content |
US9100458B2 (en) * | 2008-09-11 | 2015-08-04 | At&T Intellectual Property I, L.P. | Apparatus and method for delivering media content |
US9635411B2 (en) | 2008-09-11 | 2017-04-25 | At&T Intellectual Property I, L.P. | Apparatus and method for delivering media content |
US10425676B2 (en) | 2008-09-11 | 2019-09-24 | At&T Intellectual Property I, L.P. | Apparatus and method for delivering media content |
Also Published As
Publication number | Publication date |
---|---|
CN1799043A (en) | 2006-07-05 |
EP1623335A2 (en) | 2006-02-08 |
AU2004232040A1 (en) | 2004-11-04 |
US20040225753A1 (en) | 2004-11-11 |
US7277951B2 (en) | 2007-10-02 |
CN100416541C (en) | 2008-09-03 |
WO2004095197A3 (en) | 2005-10-27 |
WO2004095197A2 (en) | 2004-11-04 |
MXPA05011205A (en) | 2006-03-30 |
EP1623335A4 (en) | 2006-12-06 |
AU2004232040A2 (en) | 2004-11-04 |
RU2005134907A (en) | 2006-06-10 |
KR20060011963A (en) | 2006-02-06 |
CA2522429A1 (en) | 2004-11-04 |
BRPI0409618A (en) | 2006-04-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7277951B2 (en) | Omnimodal messaging system | |
US8316095B1 (en) | Computer-implemented system and method for facilitating conversation within a group through heterogeneous message delivery | |
TWI397277B (en) | System and method for unified messaging service | |
EP1370982B1 (en) | Realization of presence management | |
EP1488584B1 (en) | System and method for supporting message delivery in a network | |
US20050266884A1 (en) | Methods and systems for conducting remote communications | |
CN101317474B (en) | Message conversion equipment, system and conversion method | |
US20030158902A1 (en) | Multimedia instant communication system and method | |
CN1299492C (en) | Method for implementing multimedia short message intercommunion between instant communication tool and mobile phone | |
US20080207233A1 (en) | Method and System For Centralized Storage of Media and for Communication of Such Media Activated By Real-Time Messaging | |
WO2001052477A2 (en) | Methods and apparatus for executing an audio attachment using an audio web retrieval telephone system | |
JP2007513423A (en) | System and method for media-enabled messaging with publish-and-send functionality | |
US20030018795A1 (en) | Method and apparatus for providing extensible scalable transcoding of multimedia content | |
WO2009133544A1 (en) | A messaging device and server system | |
CN101083636A (en) | Method, equipment and system for realizing internet mail service and mobile application intercommunication | |
JP2005310156A (en) | Multimedia message conversion system and method using support language of terminal | |
CN101110786B (en) | Unified information system based on soft switching network | |
CN100452778C (en) | Multimedia content interaction system based on instantaneous communication and its realizing method | |
Healy et al. | Unified Internet Messaging | |
WO2006112825A2 (en) | Methods and systems for conducting remote communications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |