US 7,062,535 B1Grant

Individual XML message processing platform

Issue Date:2006-06-13

•34 Claims

•38 Drawing Sheets

Abstract

A communications platform (Centerpost) is disclosed containing a message processing platform along with an XML message format (SmartMessage) which provides for the reception, organization, summarization, filing, storage, synthesis, routing, formatting, and intelligent processing of XML-based electronic messages and SMTP electronic mail from corporations and other senders to fully integrate individuals' existing e-mail boxes, cellular telephones, paging equipment, facsimile machines, wireless and wired telephones, and other devices. The Centerpost platform utilizes a nickname-based routing to enable device specific sending without knowledge of the specific device address. The Centerpost platform provides sender-defined information folios, which enable synthesized filing, viewing and storage of all received SmartMessages, and the platform allows semi-private access control for the user, which allows access by others. The platform also utilizes a web-based user interface, which greatly simplifies the user's viewing, control and configuration of the individual user's particular platform. The Centerpost SmartDelivery platform also allows for corporations to utilize the Centerpost functions for its customers without requiring those customers to have a Centerpost account. The platform also provides for Amateur Informants, which facilitate the use of the Centerpost system for individuals and small businesses. The platform also provides for 2-way XML messages, a Centerpost subscriber web page, an endpoint wallet, which allows subscribers to easily transfer their endpoint information, a message based endpoint configuration, which automatically sets up a new messaging device as an endpoint.

Metadata

Assignee

CenterPost Communications, Inc.

Inventors

Juergen Stark
Craig Goren

Application Information

Application Number:US 09/661,499

Filing Date:2000-09-14

Priority Date:2000-04-03

Art Unit:2155

Classifications

IPC:

G06F15/16

Patent Drawings (38 sheets)

Description

[0001] This non-provisional application is based on the provisional patent application Ser. No. 60/194,254, entitled Consumer XML Message Processing Platform, filed on Apr. 3, 2000.

[0002] A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

[0003] Cross reference is made to a related invention disclosed in U.S. patent application entitled Method And System For Content Driven Electronic Messaging, filed concurrently, the subject matter of which is owned by the present applicants and the teachings of which are incorporated herein by reference.

[0004] Cross reference is also made to a related invention disclosed in U.S. patent application entitled Method of Controlling Access to Personal Resources, filed concurrently, the subject matter of which is owned by the present applicants and the teachings of which are incorporated herein by reference.

Background of the Invention

[0005] The present invention pertains to a communications platform, and more specifically the present invention pertains to a message processing platform that enables individuals to receive, store, synthesize and intelligently process XML-based electronic messages and standard SMTP email from corporations or any other senders in a way that fully integrates individuals' existing email boxes, cell phones, pagers, fax machines, telephones, and other devices.

[0006] Despite the limitations of existing technologies, the electronic communications market is enormous and growing very rapidly. There are over 260 million email boxes worldwide and 9.2 billion messages sent daily in the United States alone. Mobile data appliances are likewise growing rapidly with over 208 million digital wireless phone subscribers worldwide today. Similarly, Internet appliances are expected to explode to 55 million connected devices by 2002. As shown in FIG. 1, there exists a need for a new communications platform capable of fully integrating individuals' existing email boxes, cell phones, pagers, fax machines, telephones, and other devices, to take full advantage of these exploding markets.

[0007] A novel communications platform is needed by businesses and consumers due to 1) inherent limitations of email, 2) lack of integration between consumer “endpoints” (email addresses, wireless devices, fax machines, etc.) and 3) exploding electronic communications complexity.

[0008] First, email is not a suitable medium for corporations to interact with their customers in anything but a “newsletter” fashion. Email does not, by definition, contain anything more intelligent than a sender's address, an urgent/non-urgent tag, a subject line, and a text body. Email, by definition, typically goes into a user's single inbox where it is opened, read, and stored or deleted. Once more and more corporations send their customers email messages, the receiver quickly has a problem with inbox overload. Email also cannot be relied upon for urgent messages or alerts since users check email with varying frequency. Further, email cannot be easily automatically sorted, synthesized, filed, re-formatted or summarized. Today, in order to automatically file or process incoming email, a user has to manually setup message-specific rules such as a search of the subject line or specify an action based on a specific sender's address. As corporations and individuals send increasing volumes of text messages a more intelligent way to process, store, and synthesize these messages is needed. It will not be convenient, for example, to open every message from a person's credit card vendor to see that payments have been posted, transactions have been processed, or bills have been mailed. These messages should be intelligently stored so that the consumer can view a synthesized status or see detail if desired.

[0009] Second, many individuals use a variety of electronic communication addresses for their email boxes, wireless phones, pagers, fax machines, instant messaging, etc. There is no way to effectively integrate those devices: pagers, email boxes, telephones and fax machines are ignorant of each other. There are webmail and email solutions that will forward email messages to pagers or cell phones or convert email text to a fax message or a voice message. None of these solutions intelligently determine the correct destination of each specific incoming message without the user's manual control or message-specific rules being setup beforehand. Existing services, for example, will not automatically understand that a flight cancellation alert should go to any device a receiver has that is likely to deliver the message immediately but a special fares notice from the same airline should go to a lower immediacy, less intrusive device. Many unified messaging solutions force users to give up existing addresses and phone numbers and do not process intelligent incoming messages. These platforms only enable to receiver to convert and listen to messages from a variety of platforms. While some will find a subscriber by trying multiple phone numbers, there is no real intelligent routing based on the content of the incoming message since the incoming message is generally a voicemail or an email.

[0010] Third, communications complexity is exploding for corporations and individuals. New “connected” devices are being introduced every day—each with different capabilities, formatting, protocol requirements, and addresses. Individuals have new choices in the types of information they can receive and the devices upon which that information can be received and viewed. Existing message connections between individuals and/or corporations are typically point-to-point. If a corporation wants to send a message to a customer's pager, that corporation sends a message directly to that pager's address. Likewise if an individual wants to send a text message to a friend's specific endpoint, that person in many cases has to know and remember multiple email addresses, a PCS wireless phone text address, a fax number, a pager number, etc. If the receiving individual ever changes pagers or wireless phone providers, that individual has to remember to provide all possible sending parties with the new device-specific address.

[0011] As wireless PDAs, cars, home appliances, and other devices all begin to have their own electronic messaging address, the existing point-to-point, address-specific messaging approach will become extremely burdensome and complex for senders and receivers. This problem is exacerbated by the need to limit access to a specific individual's communications world but enable access for friends and family without having to share passwords. FIG. 2 shows these above-listed limitations on the current state of electronic messaging.

Summary of the Invention

[0012] The present invention is a type of communications platform also known generally as a “MessageML Processing Platform”, of which the “Centerpost Platform” is one example of this type of platform. This novel communications platform enables individuals to receive, store, synthesize, format and intelligently process XML-based electronic messages and standard SMTP email from corporations or any other senders in a way that fully integrates individuals' existing email boxes, cell phones, pagers, fax machines, telephones, and other devices. This novel communications platform reduces complexity, lowers costs, and increases capabilities for corporations that interact electronically with their customers. The communications platform also enables many valuable notification applications for corporations such as airlines, brokerages, financial institutions, and retailers, among others. For individuals, the present invention delivers valuable information while simplifying the management of all electronic communications. The invention is needed due to inherent limitations of email, lack of integration between individual “endpoints” (email addresses, wireless devices, fax machines, etc.) and exploding electronic communications complexity.

[0013] The present invention enables corporations and third parties to define and create applications using a common, centralized platform. The invention can be used 1) by individuals via a web-mail like offering, 2) by telecommunications and internet service providers on a hosted or licensed basis, 3) by corporations on a hosted or licensed basis, or 4) by other service providers on a hosted or licensed basis.

[0014] FIG. 3A shows a schematic view of the present invention as applied to electronic messaging between corporations and individuals. This novel platform is also intended to function between corporations, and between individuals, and is not merely limited to communications between corporations and individuals. FIG. 3B shows some examples of the flow of communication using such a centralized, user-centric hub. FIG. 3C lists some of the example interactions using the Centerpost platform.

Detailed Description of the Figures

[0015] FIG. 1 is a block diagram detailing the need for a novel communications platform capable of utilizing intelligent messages and integrating endpoints;

[0016] FIG. 2 is a schematic diagram displaying electronic messaging without the novel communications platform;

[0017] FIGS. 3A through 3C are block diagrams and charts displaying and indicating electronic messaging with the novel communications platform, along with examples of interactions available due to the platform;

[0018] FIG. 4 is a block diagram illustrating the interrelationship between the elements of the SmartMessage of the present invention, and the interrelationship between the SmartMessage, the Stylesheets, and the activity and event payloads of the present invention;

[0019] FIG. 5 is an example of code for a SmartMessage of the present invention;

[0020] FIG. 6 is a block diagram illustrating the interrelationship between activity classes and event classes of the present invention;

[0021] FIGS. 7A and 7B-1 to 7B-10 are examples of code for an Informant Stylesheet and a SmartMessage Stylesheet of the present invention;

[0022] FIG. 8 is a block diagram illustrating the interrelationship between the elements of the SmartMessage of the present invention, including the receipt function;

[0023] FIGS. 9A-D are an example of code for a receipt SmartMessage Stylesheet of the present invention;

[0024] FIGS. 10A through 10F shows examples of website pages containing endpoint setup and management information in accordance with the present invention;

[0025] FIG. 11 shows an example of a website page containing delivery information in accordance with the present invention;

[0026] FIG. 12 is a diagram illustrating the architecture of the communications platform of the present invention;

[0027] FIG. 13 is a diagram illustrating the flow of the SmartMessage of the present invention;

[0028] FIG. 14 shows an example of a website page containing folio information in accordance with the present invention;

[0029] FIG. 15A through 15C show examples of website pages containing message information in accordance with the present invention.

Detailed Description of the Invention

[0030] The novel communications platform contains specific components to the invention that enable a complete solution to the inherent limitations found in current communication platforms. These components include the capability for individuals to receive raw XML electronic messages (including those sent from particular corporations); a novel XML message format and structure called “MessageML” which enables corporations and others to create their own message formats, which can be processed by the new communications platform; an intelligent processing, storage, conversion, and routing engine in a scalable architecture that is aware of each individual's communications environment; “nickname-based routing” to enable device-specific sending without the specific device address; information “folios” which enable synthesized viewing and storage of all received electronic messages composed in MessageML format (also known as “SmartMessages”), and which are organized into sender definable “activities” and “events;” and a web-based user-configured interface to enable simple viewing, control, and configuration. The novel communications platform also allows access to its user-configured interface from other communications channels in addition to the Internet, such as through a mobile phone using a WAP browser or voice recognition.

[0031] The novel communications platform, through its SmartDelivery system, allows for corporations to utilize the functions inherent in the platform for its own customers, without requiring those customers to have their own platform or a MessageML account. The novel communications platform also provides a service whereby knowledgeable individuals, or Amateur Informants, facilitate the use of the platform for individuals and small businesses by allowing these individuals or small businesses to utilize the functions of the novel platform without the need to learn to use XML coding. The platform also provides for 2-way XML messages, whereby the recipient of a SmartMessage can automatically respond regardless of the endpoint that the message is received on and the response will be delivered back to the sender in XML format.

[0032] The novel communications platform also provides for a platform subscriber web page whereby designated personal information of the individual is accessible on a secure basis; an endpoint wallet, which allows subscribers to easily transfer their endpoint information to other web pages and the like; and a message based endpoint configuration, in which a SmartMessage from a communication device automatically sets up that device as an endpoint in the user's SmartDelivery or SmartMessage account.

[0033] Similar to electronic mail, XML electronic messages can currently be sent over existing Internet and SMTP transport networks. However, currently XML electronic messages can generally only be received by corporate systems in business-to-business communications. The present invention provides the first capability for individuals to receive XML electronic messages or SmartMessages.

[0034] A SmartMessage 10 is an XML document sent by an Informant to a novel communications platform like Centerpost. An Informant is a sender of SmartMessages 110 or MessageML electronic messages. Informants can be corporations, other types of organizations, or individuals. FIG. 4 shows an example of a SmartMessage 10. A SmartMessage 10 carries Event content 12, or “payload”, (such as a flight cancellation or a shipment confirmation), and is associated with and updates an Activity 14 (such as a travel itinerary or DVD order). FIG. 6 shows the relationship between the activity classes 14 and event classes 12. In use, a SmartMessage 10 is sent to individual recipients through a MessageML Service Provider such as Centerpost. The SmartMessage 10 and the MessageML system is described in a patent application filed concurrently herewith, entitled Method and System for Content Driven Electronic Messaging, and incorporated herein by reference. FIG. 5 shows the code for a sample SmartMessage.

[0035] Meta-data, such as formatting information, is found by referencing the associated Informant stylesheet 16 (which describes the informant) and the associated SmartMessage stylesheet 18 (which describes the activity and event). FIGS. 7A and 7B-1 to 7B-10 show examples of an Informant stylesheet 16 and a SmartMessage Stylesheet 18, respectively. An Informant stylesheet 16 describes the meta-data about the Informant, such as its name, website address, industry category, and the like. Another role of the Informant Stylesheet 16 is to provide information about and authenticate the sender of the message. The Informant Stylesheet 16 usually resides on the Informant's web server and is versioned by its filename. A MessageML platform like the novel Centerpost communications platform caches these stylesheets.

[0036] The SmartMessage Stylesheet 18 serves three main functions. The SmartMessage Stylesheet 18 defines activity and event class meta data and organization; defines the XML schemas of the activity 14 and event class 12 payloads (content); and defines how the payload is rendered for specific endpoints 20. The SmartMessage stylesheet 18 also informs the platform of the types of messages (or “event classes”) that have been created and may be sent by that Informant. The SmartMessage Stylesheet 18 generally resides on one of the Informant's web servers, but Informants can also share a common stylesheet on a shared server.

[0037] A MessageML platform like Centerpost caches these stylesheets in its own database so it can refer to them quickly without accessing the Internet. A single SmartMessage Stylesheet XML document can contain meta-data about several SmartMessage activities and events.

[0038] The SmartMessage protocol has been developed to create an open, extensible message format used by the MessageML platform. The SmartMessage protocol enables corporations and other senders to create their own message formats that can be processed by the platform.

[0039] SmartMessages 10 contain standardized XML-tags that enable the platform to understand the nature of the message and forward, copy, format, convert, store, consolidate, summarize, or stop the communication accordingly. The XML tags describe things like the message immediacy, reach, sensitivity, and purpose. XML SmartMessages 10 are self-describing and self-formatting via stylesheets. In addition, the XML messages are fully extensible by senders to encompass their own fields and definitions. These tags are used by the platform to automatically determine how to display, summarize, and process incoming messages. With XML, the communications platform can more intelligently process, sort, synthesize, format and route messages.

[0040] The novel communications platform is a highly scalable and reliable XML messaging engine capable of processing messages based on highly dynamic and openly definable logic. The platform is fully aware of each individual user's entire communications environment, such as email boxes, cell phones, pagers, fax machines, telephones, etc. as well as the devices of spouses, assistants, friends, and co-workers, whom the user may wish to receive a copy of a message depending on its specific content. The communications platform automatically processes based on the pre-defined defaults, the user's preferences regarding his electronic endpoints (email boxes, wireless devices, etc.) and the attributes of the message itself. This embedded intelligence, for example, would send travel weather alerts to the user's home fax but flight cancellations to the user's cellphone with a copy to the assistant's work fax. Users can modify the rules if they prefer to deviate from the systems defaults. With this novel communications platform, individuals only define their endpoints once in a single spot and retain a lifetime electronic address for all of their endpoints.

[0041] The communications platform also contains escalation rules that allow further intelligence in message routing and delivery. FIG. 8 shows a high-level perspective of the entities involved in the architecture of the present invention. A receipt 22 can be generated by the communications platform and sent back to the Informant 24 through the SmartMessage Transfer Agent 26. For example, if the receipt 22 of an urgent message is not confirmed by the endpoint 20 designated by the user, the platform can route the message to another endpoint until the receipt of the message by the user is confirmed. This additional intelligence also may incorporate location-based sensing and device-sensing capabilities. For example, the platform may change routing directions based on device-sensing technology that allows the platform to determine whether the device is on or off, or based on location-sensing technology that tells the platform where the device is located. FIGS. 9A-D are an example of the code pertaining to a Receipt SmartMessage Stylesheet.

[0042] FIGS. 10A through 10F show examples of the display screens for the endpoint setup and management pertaining to the novel communications platform. In order to utilize the novel platform, a subscriber must configure one or all of the endpoints 20 to be used on the platform. Once in the platform's website, the user can enter the endpoints web page to add a particular endpoint 20 to the communications platform. FIG. 10A is a screen print of the endpoint setup page for the Centerpost communications platform. On this web page, each of the subscriber's endpoints 20 is defined, including the type of endpoint 28, any nickname 30 given to that endpoint, a description 32, device settings and options 34. FIG. 10B is an example of a web page that describes the details 36 for a particular endpoint, in this case, the subscriber's HTML Email. The subscriber can modify the details for this endpoint at this page, i.e., route certain SmartMessages to this endpoint, route all SmartMessages to this endpoint, etc.

[0043] The platform will allow the user to view and interact with the interface used to control his endpoints, from other communications channels aside from a website, such as from a voice phone using voice recognition or a WAP browser. The user thus will be able to, for example, adjust delivery preferences and folio preferences from his PDA or mobile phone.

[0044] FIG. 10C is an example of a web page that allows the subscriber to modify certain advanced options 38 for a particular endpoint. For example, the types of messages that the user would like to receive at this endpoint, etc.

[0045] Once all of the information has been entered for a particular endpoint 20, the subscriber enters the Save Endpoint 40 web page as shown in FIG. 10D. This page allows the user to save all of the information previously entered pertaining to that particular endpoint. FIGS. 10E and 10F show the screen prints for the Endpoint Test 42 web pages. The subscriber can use these pages to test his endpoint and the configuration thereof.

[0046] FIG. 11 is a screen print of the delivery web page pertaining to the Centerpost communications platform. The delivery page provides historical information to the subscriber, including whether messages were delivered, when they were sent and received, the endpoint they were delivered to, etc. The delivery page example shown in FIG. 11 is for the user's personal delivery information and is divided into three different categories: Informant 44, Activity & SmartMessage 46, and Endpoints 48. However, like all of the other pages described herein, the delivery page could be configured in a multitude of different ways.

[0047] FIG. 12 shows an example of the deployment architecture for the communications platform 100 of the present invention. In this example, a SmartMessage 10 is delivered, either using the Simple Mail Transfer Protocol (SMTP) 50 or the Hypertext Transfer Protocol (HTTP) 52, to a receiving server 54. The message is transmitted to routing and processing servers 56 or transaction servers 58 (or both). Transaction servers 58 interact with web portal servers 60, which are accessible by customers 62 of the system and by particular guests 64. Transaction servers 58 also interact with various storage servers 66 to access user data information 66 such as customer profiles, folios, messages, and other data. Further, the routing and processing servers 56 may deliver messages and other information to various other servers 70 for formatting and delivery to particular endpoints 20. These servers include email, phone or pager, text-to-voice, instant message, facsimile and US mail servers, among others. The messages are then delivered to the particular endpoints 20. Further processing may include an acknowledgement 72 (or lack thereof), which may be sent back to the original sender through the transaction server 58 and web portal server 60. Also, firewalls 74 can be incorporated throughout the platform architecture in order to safeguard information transmitted over the communications platform 100.

[0048] FIG. 13 represents the simplified flow of a message from the sending source 24, 62, 64 to a SmartMessage processing server. As described above, SmartMessages 10 can be delivered to a SmartMessage processing platform for processing using two of the most commonly used protocols on the internet today—SMTP and HTTP 50, 52.

[0049] Initially, (as shown as A in FIG. 13) the Sender 24, 62, 64 generates a SmartMessage 10 and packages it in an email to be sent via SMTP 50, or in a HTTP 52 form to be posted through the HTTP protocol. The SmartMessage 10 travels via the protocol through the Internet 76 and is routed to the platform “mail” server (if sent via SMTP 50) or “web” server (if sent via HTTP 52). The mail/web server processes the incoming package and extracts the SmartMessage 10 from the HTTP 52 request or SMTP 50 mail message. Then the SmartMessage 10 is validated and processed. The SmartMessage 10 is then stored and potentially transmitted and formatted to the recipient's chosen endpoints 20, such as email, wireless, fax, etc.

[0050] Another aspect of the present invention is nickname-based routing, which enables outside senders to address specific endpoints 20 such as a user's pager, cell phone, or fax machine by sending messages to the receiver's main address preceded by a specific nickname. For example, a message could be sent to [email protected] and be routed directly to John Doe's cell phone. Similarly the message could be sent to JohnDoe+Homephone@(centerpost.com and be routed to the receiver's home telephone. The receiver flexibly defines the endpoint 20 such as “Cellphone” or “Homephone” which can be used by senders and also enables or disables direct, nickname-based routing. Nickname-based routing eliminates the need for the sender to memorize multiple, potentially changing addresses for the receiver. Also, the invention will enable dynamic nicknames such as [email protected] which will route an outbound message through the platform and out to the specific fax number on behalf of John Doe's account. In this way, users can send messages out through multiple gateways.

[0051] Another aspect of the present invention is the use of information folios to organize the information that an individual receives. Even though email currently can be organized into folders, it must be done either by the user or by crude filtering methodologies in the user's email program. However, SmartMessages can automatically organize, synthesize, and update themselves. FIG. 14 shows an example of a website containing a folio in accordance with the present invention. Folios also will be accessible to users from multiple devices such as the user's PDA or mobile phone.

[0052] Information folios intelligently store, display, and synthesize incoming SmartMessages 10. Folios are organized into “activities” and “events,” and can include such information as the Informant 24, the activity 14 and SmartMessage 10, the date 78 and the description 80. Both are definable by the sender. Events apply to activities. Activities can include 1) a bank statement for a given month, 2) an order from an online book seller, 3) a travel itinerary, 4) home alarm status, or 5) messages from a specific person, etc. Events post to an activity and update the activity status based on the definition set by the sender.

[0053] For the above examples, events would be 1) a bank statement posting such as payment received, 2) the order confirmation or shipping confirmation, 3) airline booking or rental car confirmation, 4) home alarm events such as a triggered alarm, or 5) individual messages from the specific person, etc. Folios enable complex, detailed information to be automatically organized and summarized based on open, flexible, sender-defined requirements. A folio is like an intelligent, automatic filing assistant. Once given basic instructions, the platform will organize messages, retrieve messages, alert you when important messages come in, etc. Also the “assistant” will know how to respond in a variety of situations including trying to contact the user through a variety of means.

[0054] FIGS. 15A through 15F are screen print examples of the Folio aspect of the novel communications platform 100 of the present invention. FIG. 15A is a screen print of a SmartMessage, in this example a SmartMessage from FutureAir, that is automatically sorted and entered into the proper Activity when received. The subscriber can view this SmartMessage at any time to obtain all of the information sent by FutureAir in its SmartMessage. In this case the SmartMessage indicated that Jane Doe's flight number 219 was cancelled due to bad weather.

[0055] FIG. 15B is a screen print displaying the Delivery information for the particular SmartMessage. In this example, the screen displays the different endpoints that the message was sent to along with the status, date, and time.

[0056] FIG. 15C is a screen print of the history for a particular SmartMessage, in this case, the history for the FutureAir flight described above. The history shows that flight 219 has been cancelled along with details for each time a SmartMessage was sent to the subscriber. The SmartMessage was automatically organized and placed into the proper Folio for review by the subscriber.

[0057] The “activity” element provides information about the activity associated with the SmartMessage 10. An activity is a categorization of events. For example, an activity may be “Travel Itinerary” with such related events as “Flight Cancellation”, “Flight Arrival Time”, etc., and includes the following attributes.

[0058]


Attributes	purpose

activity-class	The class name of the activity. This activity class name
	must be defined by the Informant and must match a valid
	activity class (activity-class-name attribute) in the
	referenced SmartMessage Stylesheet
	(<smXML>\smartmessage-stylesheet-version). The
	matching activity-class-name in the SmartMessage
	Stylesheet contains metadata, the XML schema and
	endpoint specific XSL documents about the activity and
	more importantly defines the valid event classes for the
	activity class itself.
activity-id	A unique ID to identify the activity instance. Successive
	SmartMessages received with the same activity ID will be
	grouped by this ID. For example, multiple event classes
	like “Flight Arrival Time”, “Flight Cancellation”, etc. can
	be grouped under a single activity class called “01/01/200
	Travel Itinerary” by associating the event classes with that
	ID.
activity-url	An associated URL to the activity. This may simply link
	back to the Informants web site or may contain query
	strings in the URL to link back to the recipient's account
	page.
activity-title	A descriptive title of the activity.
activity-	A short description of the activity status.
status
closed-date	Date the activity was closed in ISO 8601 format. This date
	can be post-dated. If this attribute is empty the activity is
	assumed to be open.

[0059] Another aspect of the present invention is a website that enables users to quickly define their communications environment and control their electronic communications platform in an intuitive, friendly way; in other words, a point-and-click, drag-and-drop, intelligent communications center. The present invention provides an intelligent, self-configuring, easily controllable personal communications hub, as well as a powerful web-based vehicle to view, organize, and store information. When an individual changes cell phone, pager, or email providers, he or she need only change the address once on the website. This change of a particular endpoint will automatically become part of the user's communication environment, thereby precluding the need for others to have the updated information. As endpoints such as pagers or mobile phones become more and more “intelligent,” they will ultimately automatically configure themselves on the platform. Thus, when a user buys, for example, a new cellphone, the platform will receive a SmartMessage from the provider and that endpoint will be automatically setup.

[0060] Another aspect of the present invention is an intelligent message delivery platform (Centerpost SmartDelivery), complete with a user interface, which provides many of the advantages of MessageML, without the need for an individual to open a new MessageML account. A corporation can utilize the Centerpost SmartDelivery platform as a service whereby the corporate customers can benefit from the Centerpost platform from the corporation's web site.

[0061] SmartDelivery is a service that can be offered via the Centerpost Platform as that platform is described above. The SmartDelivery service allows individuals to experience the benefits of MessageML only on messages from the company sponsoring the SmartDelivery service, or on messages from outside parties approved by the company sponsoring the SmartDelivery service. The SmartDelivery service provides a user interface, which is seamlessly integrated into the corporation's existing web site. These SmartDelivery accounts can be specific to a given corporation, providing these corporations the ability to send SmartMessages (as described herein) to their customers or users through the Centerpost platform. The corporation may also house the user's messaging interface on the corporation's own website.

[0062] The SmartDelivery service is designed to provider users with as much of the functionality of the SmartMessage service, without requiring these users to establish a new MessageML account. Instead of creating a new Centerpost account, users can easily complete a user profile on the partner corporation's website, which will identify their endpoints and other information. By completing the user profile, using an easy point and click interface, users can control which messages they receive from the partner corporation, and on which endpoints these messages are received. This function can be accomplished within their existing (or a new) account on the partner corporation's website. For example, after logging in to a user's existing account on a brokerage firm's website, brokerage customers users may be able to set up and manage their SmartDelivery account directly on the brokerage's website, similar to other features located on the brokerage's website.

[0063] The SmartDelivery service is necessary because corporations want to offer the advanced messaging features as described above without requiring users to create new accounts. SmartDelivery may include all or a subset of the functionality offered in the Centerpost SmartMessage platform, including folios, endpoints, delivery, settings, etc. Consequently, the Centerpost SmartDelivery service provides a benefit to users as well as to corporations. Users can have messages delivered to a single or multiple endpoints in a matter of seconds. Thus, if a user is not sure whether he will be in his office or in transit, a message can be sent to his office telephone and his cellular telephone at the same time, thereby assuring that the user will receive the message as soon as possible. Additionally, users can easily control which messages they receive on which endpoints with an easy to use graphical interface. Users can also set up their inbox in a manner such that all messages received (and sent) are available for viewing in a single, self-organizing inbox.

[0064] With the Centerpost SmartDelivery Service, corporations can send information to their customers on a wide variety of devices (e.g., email, voice, fax, wireless, Instant Messenger). The corporation's customer service representatives can see an audit trail of all messages sent by the corporation, including time-stamped delivery reports.

[0065] The information or content pertaining to a particular corporation's SmartDelivery service will only be accessible through the corporation's website. In other words, users will be required to access the SmartDelivery service for a particular corporation through, for example, the user's accounts with that corporation. The functionality will be integrated into the corporation's website using a web page or frame to display Centerpost content. Certain elements of the interface may be customized in order to integrate the Centerpost content with the look and feel of the corporation's website.

[0066] In order to implement the Centerpost SmartDelivery platform, each corporation offering the SmartDelivery service would have its own domain of user names. The provider will be responsible for logging the user into their SmartDelivery account on the provider's website. SmartDelivery providers will have full read access to their customers' SmartDelivery accounts.

[0067] Only messages from the SmartDelivery provider (or selected partners of that provider) will be capable of being delivered to a user's SmartDelivery account with that provider. The corporation's platform could be configured such that one corporation could not send messages through the other corporation's SmartDelivery account. Thus, messages received from a sender not associated with the particular corporation, or an invalid sender, will be rejected by the system, unless the system is configured to let those messages be delivered. For example, if one stock brokerage company attempted to send a message to the SmartDelivery account of another brokerage firm's customer, the message would not be received by the customer's SmartDelivery account. However, if an airline, with the brokerage firm's permission, sent a message to the brokerage firm customer's SmartDelivery account, that message would be delivered to the account. Similarly, customers could not access their other SmartDelivery accounts with one provider through the website of another provider. (In other words, customers could not access their SmartDelivery account with an airline through their SmartDelivery account with a brokerage firm, or vice versa, unless both SmartDelivery providers permitted it.) However, if users established a SmartMessage account, messages from their various SmartDelivery accounts could be forwarded to their SmartMessage account without modifying the SmartMessage content. Consequently, these messages would then be managed and coordinated by the Centerpost Platform with full SmartMessage functionality.

[0068] Users can choose to forward all of their messages to a Centerpost SmartMessage account. All of the SmartMessages that a user would normally receive at the corporation's SmartDelivery account will be routed to that user's Centerpost SmartMessage account and will be found in the user's SmartDelivery Folio. While the user will not need to access the folio on the corporation's website, the corporation will have the ability to view the user's messages (those that were originally sent to the user at the corporation's SmartDelivery account) through their administrative or customer support site.

[0069] Another aspect of the present invention is a component of the Centerpost Platform, the Amateur Informant. An Amateur Informant is an entity that creates and sends SmartMessages through the Centerpost Platform. The objective of the Amateur Informant is to simplify the process of creating SmartMessages, such that individuals, schools, small businesses, etc. can take advantage of the benefits inherent in an XML platform such as the Centerpost Platform. The Amateur Informant provides for the creation and publication of SmartMessages without the usually necessary coding using XML.

[0070] The Amateur Informant is required by entities, such as schools and other not-for-profit organizations, individuals, and small businesses, that can benefit from the functionality of SmartMessages, but do not have the technical infrastructure or the individuals that can create SmartMessages in XML, nor the individuals that can manage an XML Message Processing Platform, including information such as the mailing lists, the receivers of the messages, etc. These functions can be expensive and time-consuming. The Amateur Informant is designed to eliminate these barriers.

[0071] The Amateur Informant will be accessed through the web. Essential elements of this aspect of the invention include a web-based designer that will allow informants to easily create SmartMessages and SmartMessage style sheets (as described herein). The informants information can be hosted on a web page specific to that informant, which is located on the Amateur Informant website. In addition, this aspect of the invention will incorporate a way for the informant to manage a mailing list, for example, on the Amateur Informant system, without the need to create the informant's own web-based mailing system. For certain applications, i.e., a school mailing list, the receiver of the messages may be allowed certain responsibilities, such as adding or removing names to or from the mailing list, etc. The Amateur Informant also integrates the sending of SmartMessages into a standard, widely used electronic mail program.

[0072] The Amateur Informant aspect of the present invention may contain standard SmartMessages that an informant could send. These standard SmartMessages could include, for example, a delivery SmartMessage with the text “I just sent you something”, along with the information necessary to track the packages via UPS or Federal Express. Other examples of standard SmartMessages might be an invitation SmartMessage, a newsletter SmartMessage, a reminder SmartMessage, and a change of address SmartMessage, a picture/movie/sound SmartMessages, and a joke SmartMessage.

[0073] Another aspect of the present invention is a component of the Centerpost Platform, SmartResponses, which incorporates into the platform the ability for an informant to define and drive automatic 2-way messaging interaction with message senders. Currently, informants are unable to facilitate automatic, real-time, convenient and meaningful 2-way messaging with the recipients of their messages. This aspect of the present invention solves this problem.

[0074] With this aspect of the invention, informants send a SmartMessage with a request for a response from the recipient, which is contained in the SmartMessage payload. The recipient will be able to choose from a list of responses originally defined by the informant and carried in the SmartMessage payload. The Centerpost Platform will gather the recipient's answer to the question in the most appropriate form for the device the recipient is using, format the response into the informant's desired format, and send the response back to the informant. With this form of 2-way messaging, the sender has the ability to define in its initial message the content of the XML message it will receive back in response from the recipient, depending on the response selected by the recipient. The content of the initial message, the potential responses by the recipient, and the XML-based messages that will be sent back to the sender all are carried as part of the payload of the initial message. Thus, if a 2-way XML message is received on a cellular telephone, the recipient should be able to respond either by using the keys on the cellular telephone, or by giving a verbal response, which the system will process using voice recognition technology. If the message is received on his PDA, the recipient should be able to reply automatically using the PDA.

[0075] For example, if a stock broker sends a SmartMessage to a client informing him that a stock is doing well, and that client receives the message on his cellular telephone, the client, will be able to respond to the message through his cellular telephone to inform his broker that he wants to buy 200 shares of the stock. In the case of an airline, an individual receiving a SmartMessage that his flight has been cancelled, would have the opportunity to rebook the flight by responding to the XML message.

[0076] Another aspect of the present invention is a component of the Centerpost Platform, the Personal Portal, which provides access to a subscriber's selected personal information on a secure basis to the subscriber's friends, family, and colleagues.

[0077] The Personal Portal provides a subscriber's friends, family, and colleagues with access to the subscriber's contact information, communications endpoints, and location. The Personal Portal comprises a web page that displays information pertaining to the subscriber, i.e., the subscriber's addressable endpoint nicknames, personal information, and current location all could be viewed from this page. The web page could be an endpoint or show a sub-section of the subscriber's folio. As an example, a subscriber could post a travel itinerary to this web page, so colleagues could view flight information, etc. Access to the page could be controlled by the semi-private security system described in a patent application entitled Method Of Controlling Access To Personal Resources, filed concurrently and incorporated herein by reference.

[0078] Another aspect of the present invention is a feature of the Centerpost Platform, the endpoint wallet, which provides an XML-based repository of a user's message delivery information and preferences. This may include information such as the user's device addresses, settings, and default delivery options. The endpoint wallet is associated with a specific user, and is independent of the user's accounts.

[0079] This aspect of the present invention provides a set of information delivery instructions that a user can carry with them to each website. Thus, when a user visits a retail site, for example, if he has an electronic wallet, his information, including address, credit card number, and shipping information is automatically entered into the website. Similarly, if a user visits a retail site that requests the user to set up notification messages (as described herein), i.e., order confirmation, shipment information, or billing, the endpoint wallet automatically transfers the information to the user's list of endpoints, including the way the user wants information routed by default.

[0080] The account platform will recognize the existence of an endpoint wallet, and the user will then confirm that information from the endpoint wallet should be transferred to, or used to populate messaging set-up fields. The endpoint wallet can reside on both the user's device and the Centerpost server.

[0081] The objective of this aspect of the invention is to facilitate users attempting to set up and manage endpoints, and also trying to direct the flow of information to those particular endpoints. When a user establishes a new SmartDelivery or SmartMessaging account, the endpoint wallet will populate device information and settings in the account automatically, obviating the need for the user to re-enter these settings and preferences each time a new account is opened.

[0082] Another aspect of the present invention is a SmartMessage that automatically sets up a new messaging device or account as an endpoint in a user's SmartMessage account. For example, if an individual purchases a new cellular telephone, that telephone (or service provider) could send a SmartMessage to the user's designated SmartMessage or SmartDelivery account setting itself up as an endpoint.

[0083] If the user has no SmartMessage or SmartDelivery account, this message will create a new account and then add the sending device as an endpoint. This invention will minimize the individual's time and effort in setting up and maintaining endpoints. The Centerpost messaging platform will have the capability to watch for these messages and process them appropriately.

[0084] With the present invention, among other applications, individuals can receive a variety of valuable event-driven alerts as well as regular text messages, automatically process those alerts leveraging their email boxes, faxes, wireless devices, folios, and other people, view the details or synthesis of the SmartMessages that have been received, send SmartMessages to other subscribers, and intelligently route and process emails. By sending SmartMessages, corporations can create all types of valuable alerting features that extend beyond email and reduce spamming. Since the invention takes care of complex formatting, routing, and processing functions, corporations can reduce their messaging development cost and complexity.

[0085] The invention's SmartMessages enable corporations and individuals to interact in compelling ways that are not effective with email or web browsing. Folios further enable this information to be captured, synthesized, and viewed is a highly organized manner.

[0086] Certain example applications are listed below (see FIG. 3C for additional example applications).

An airline can electronically accompany customers through their travel itinerary:

- [0087] Send ticket confirmation to work email inbox.
- [0088] Send confirmation of rental car booking
- [0089] Send destination weather report to home fax machine 24 hours prior to departure to aid packing.
- [0090] Send gate, baggage claim area, and local traffic report to pager 30 minutes prior to landing.
- [0091] Send a flight delay alert 1 hour before scheduled departure
- [0092] Send flight landing confirmation to secretary's email.
- [0093] The above events can be posted to an activity created around a specific trip itinerary.
  Security monitoring companies can keep homeowners aware of activity:
- [0094] Send alarm notifications to all of spouses' endpoints: work email, pager, PCS phone, and fax.
- [0095] Send consolidated alarm on/off activity to personal email once/week
- [0096] The above events can be posted to an activity created around the home alarm status
  Television and media companies can keep customers aware of changing offerings:
- [0097] Send TV programming episode information to personal email 24 hours in advance.
- [0098] Send NFL football programming to pager every Sunday morning.
- [0099] Send special interest radio programming to work email each morning at start of business.
- [0100] Send announcements of movie premiers and local theater info as they occur.
- [0101] Send rental movie titles once/week to personal email.
- [0102] The above events can be posted to activities organized around program types or time frames.
  Financial service firms can send customers all sorts of information, and know their customers will find it manageable because they are SmartMessages:
- [0103] Send security price, volume, and analyst estimate change alerts to work email and pager.
- [0104] Send check clearing notification to personal email.
- [0105] Send trade confirmation to personal email.
- [0106] Send portfolio positions report to personal email once every business day.
- [0107] Activities can be created around a person's portfolio, the monthly investment statement, or watch lists.
  Retailers and manufacturers can proactively keep customers informed of their order flow:
- [0108] Send order confirmations to personal email.
- [0109] Send shipment and order confirmations to a “folio” for subsequent easy retrieval and review.
- [0110] Send updates on status of long-running or custom-manufactured orders, such as backorder arrived, in route to dealer, and product in test.
- [0111] Activities can be created around specific orders.

[0112] Similarly, the invention enables users to communicate using SmartMessages with other platform users. For example, one user could send a “changed home address” SmartMessage to another user and have it automatically updated in the receiver's address book folio.

[0113] The receiving entity does not have to be an individual. As appliances, cars, telemetry devices, and other network devices are connected to the Internet, they can directly receive SmartMessages about maintenance status, parts orders, etc.

[0114] The foregoing detailed description of the invention is intended to be illustrative and not intended to limit the scope of the invention. Changes and modifications are possible with respect to the foregoing description, and it is understood that the invention may be practiced otherwise than that specifically described herein and still be within the scope of the claims.

Claims

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

The invention claimed is:

1. A communications platform that enables users to receive electronic messages from corporations and others comprising a nickname-based routing system, said nickname-based routing system comprising logic for:

receiving an electronic message;

parsing the electronic message to determine a designation for a user;

parsing the electronic message to determine a nickname of an endpoint designated in the electronic message, the nickname of the endpoint being distinct from the designation for the user, the nickname for the endpoint being selected from a plurality of nicknames and being dynamically dependent on the endpoint selected;

accessing a database, based on the determined designation of the user and the determined nickname of the endpoint, to determine an address and type of an endpoint to route the electronic message to based on the nickname, the database correlating the designation of the user to the plurality of nicknames of endpoints the database correlating the plurality of nicknames to a plurality of addresses;

determining a type of endpoint;

formatting at least a portion of the electronic message based on the determined type of endpoint; and

sending at least a portion of the formatted message to the determined address of the endpoint,

where the nickname for the endpoint eliminates a sender to memorize the plurality of addresses for the plurality of endpoints.

2. The communications platform in claim 1, wherein said endpoint comprises an electronic mail box, a wired or wireless telephone, a facsimile machine, a paging device, or a personal digital assistant.

3. The communications platform in claim 2, wherein said nickname-based routing system comprises at least one address containing a nickname.

4. The communications platform in claim 3, wherein said nickname comprises information pertaining to said user's name and endpoint.

5. The communications platform in claim 4, wherein said nickname further comprises information pertaining to said endpoint.

6. The communications platform in claim 5, wherein said information pertaining to said endpoint comprises a telephone number, a facsimile number, a pager number, an electronic address or a resident address.

7. The communications platform in claim 1, wherein the electronic message is addressed to the communications platform.

8. The communications platform in claim 1, wherein the designation for the user comprises a user's name.

9. The communications platform in claim 1, wherein the nickname is selected from the group consisting of phone and fax.

10. The communications platform in claim 1, wherein the nickname was previously designated by the user.

11. The communications platform in claim 1, wherein determining a type of endpoint to route the electronic message to is further based on the designation for the user.

12. The communications platform in claim 1, wherein determining an address of the endpoint comprises accessing the database to determine the address of the endpoint based on the nickname and based on the designation for the user.

13. The communications platform in claim 1, wherein the nickname for the endpoint is selected from a plurality of nicknames.

14. The communications platform in claim 13, wherein the designation for the user is non-changeable for a specific user.

15. The communications platform in claim 14, wherein format for the electronic message comprises the designation of the user, a connector, the nickname, and the address of the communication platform.

16. The communications platform in claim 1, wherein the electronic message includes an @ symbol, and wherein the nickname of the endpoint is prior to the @ symbol in the electronic message.

17. The communications platform in claim 16, wherein the designation of the user is prior to the @ symbol in the electronic message.

18. The communications platform in claim 16, wherein the nickname of the endpoint is prior to the @ symbol in the electronic message.

19. The communications platform in claim 1, wherein the nickname of the endpoint is not a domain name.

20. The communications platform in claim 1, wherein the electronic message comprises a domain name of the communications platform, the domain name for the communications platform being separate from the nickname of the endpoint.

21. The communications platform in claim 20, wherein the nickname for the endpoint is not used to route the electronic message to the domain name for the communications platform.

22. The communications platform in claim 1, wherein the nickname for the endpoint is not an address.

23. The communications platform in claim 1, wherein a plurality of users have user designations; and

wherein the database correlates, for each of the user designations, an address for an endpoint associated with the nickname, with the addresses of the endpoints being different for each of the user designations.

24. A communications platform that enables users to receive electronic messages from corporations and others comprising a nickname-based routing system, said nickname-based routing system comprising logic for:

receiving an electronic message addressed to the communications platform with fields for a nickname of an endpoint and an address of the endpoint the nickname of the endpoint being selected from a plurality of nicknames and being dynamically dependent on the endpoint selected;

parsing the electronic message to determine the nickname of the endpoint designated in the electronic message;

parsing the electronic message for the address of the endpoint designated in the electronic message;

accessing a database to determine type of the endpoint to route the electronic message to based on the nickname the database correlating the nickname to a type of endpoint;

formatting at least a portion of the electronic message based on the determined type of endpoint; and

sending at least a portion of the formatted message to the determined address of the endpoint,

where sending the electronic message using the nickname of the endpoint and the address of the endpoint enables a sender to dynamically define the nickname in the electronic message.

25. The communications platform in claim 24, wherein the address of the communications platform comprises an internet address.

26. The communications platform in claim 25, wherein the address of the communications platform comprises a .com address.

27. The communications platform in claim 25, wherein the address of the endpoint comprises a telephone number.

28. The communications platform in claim 24, wherein the electronic message comprises a field for a designation of a user; and

further comprising parsing the electronic message to determine the designation for a user; and

wherein sending at least a portion of the formatted message to the determined address of the endpoint comprises sending at least a portion of the formatted message to the determined address of the endpoint on behalf of the determined designation of the user.

29. The communications platform in claim 24, wherein the address comprises a numeric address.

30. The communications platform in claim 24, wherein the electronic message includes an @ symbol, and wherein the address of the endpoint is prior to the @ symbol in the electronic message.

31. The communications platform in claim 24, wherein the nickname of the endpoint is not a domain name.

32. The communications platform in claim 24, wherein the electronic message comprises a domain name of the communications platform, the domain name for the communications platform being separate from the nickname of the endpoint.

33. The communications platform in claim 32, wherein the nickname for the endpoint is not used to route the electronic message to the domain name for the communications platform.

34. The communications platform in claim 24, wherein the nickname for the endpoint is not an address.

Patent Citations (50)

Patent	Date	Inventor	Cited By
US5073852(A)	1991-12-01	Siegel et al.	Examiner
US5400020(A)	1995-03-01	Jones et al.	Applicant
US5579472(A)	1996-11-01	Keyworth et al.	Examiner
US5623260(A)	1997-04-01	Jones	Applicant
US5657010(A)	1997-08-01	Jones	Applicant
US5668543(A)	1997-09-01	Jones	Applicant
US5708780(A)	1998-01-01	Levergood et al.	Applicant
US5742763(A)	1998-04-01	Jones	Examiner
US5796394(A)	1998-08-01	Wicks et al.	Applicant
US5805810(A)	1998-09-01	Maxwell	Examiner
US5819046(A)	1998-10-01	Johnson	Examiner
US5828314(A)	1998-10-01	Park	Examiner
US5870549(A)	1999-02-01	Bobo, II	Applicant
US5875437(A)	1999-02-01	Atkins	Applicant
US5899995(A)	1999-05-01	Millier et al.	Applicant
US5937161(A)	1999-08-01	Mulligan et al.	Applicant
US6029148(A)	2000-02-01	Zurstrassen	Applicant
US6052673(A)	2000-04-01	Leon et al.	Applicant
US6073166(A)	2000-06-01	Forsén	Applicant
US6151624(A)	2000-11-01	Teare et al.	Applicant
US6154738(A)	2000-11-01	Call	Applicant
US6157945(A)	2000-12-01	Balma et al.	Applicant
US6161129(A)	2000-12-01	Rochkind	Examiner
US6167409(A)	2000-12-01	DeRose et al.	Applicant
US6185603(B1)	2001-02-01	Henderson et al.	Applicant
US6212550(B1)	2001-04-01	Segur	Applicant
US6216165(B1)	2001-04-01	Woltz et al.	Applicant
US6219714(B1)	2001-04-01	Inhwan et al.	Applicant
US6278936(B1)	2001-08-01	Jones	Applicant
US6313760(B1)	2001-11-01	Jones	Applicant
US6314402(B1)	2001-11-01	Monaco et al.	Applicant
US6314434(B1)	2001-11-01	Shigemi et al.	Examiner
US6317060(B1)	2001-11-01	Jones	Applicant
US6347340(B1)	2002-02-01	Coelho et al.	Examiner
US6363254(B1)	2002-03-01	Jones et al.	Applicant
US6363323(B1)	2002-03-01	Jones	Applicant
US6411891(B1)	2002-06-01	Jones	Applicant
US6415207(B1)	2002-07-01	Jones	Applicant
US6430272(B1)	2002-08-01	Maruyama et al.	Examiner
US6438583(B1)	2002-08-01	McDowell et al.	Examiner
US6442591(B1)	2002-08-01	Haynes et al.	Examiner
US6513019(B1)	2003-01-01	Lewis	Examiner
US6542515(B1)	2003-04-01	Kumar et al.	Examiner
US6542935(B1)	2003-04-01	Ishii	Examiner
US6836792(B1)	2004-12-01	Chen	Examiner
EP792044(A2)	1997-08-01		Applicant
WO1/76119(A2)	2000-10-01		Applicant
WO1/75604(A1)	2001-10-01		Applicant
WO1/76264(A2)	2001-10-01		Applicant
WO1/80130(A1)	2001-10-01		Applicant

Non-Patent Literature (4)

Arbanowski, Stefan and Van Der Meer, Sven, “Service Personalization for Unified Messaging Systems,” Computers and Communications, 1999. Proceedings. IEEE International Symposium on Red Sea, Egypt Jul. 6-8, 1999, Los Alamitos, CA, USA, IEEE Comp. Soc., US, Jul. 6, 1999, pp. 156-163.Applicant
International Business Machines Corporation: “Multi-modal data access” Research Disclosure, Kenneth Mason Publications, Hampshire, GB, vol. 426, No. 114, Oct. 1999, 8 pages.Applicant
Patel, Ahmed and Gaffney, Kevin, “A technique for multi-network access to multimedia messages,” Computer Communications, Elsevier Science Publishers BV, Amersterdam, NL, vol. 20, No. 5, Jul. 1, 1997, pp. 324-337.Applicant
Van Der Meer, Sven, Arbanowski, Stefan and Magedanz, Dr. Thomas, “An Approach for a 4th Generation Messaging System,” Autonomous Decentralized Systems, 1999. Integration of Heterogeneous Systems. Proceedings. The Fourth International Symposium on Tokyo, Japan, Mar. 21-23, 1999, Los Alamitos, CA, USA, IEEE Comput. Soc., US, Mar. 21, 1999, 10 pages.Applicant

Abstract