EP1310066A2 - Procedes et systemes de composition et de transmission de communications riches en contenu - Google Patents

Procedes et systemes de composition et de transmission de communications riches en contenu

Info

Publication number
EP1310066A2
EP1310066A2 EP01923240A EP01923240A EP1310066A2 EP 1310066 A2 EP1310066 A2 EP 1310066A2 EP 01923240 A EP01923240 A EP 01923240A EP 01923240 A EP01923240 A EP 01923240A EP 1310066 A2 EP1310066 A2 EP 1310066A2
Authority
EP
European Patent Office
Prior art keywords
content
server
communication
content server
message
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.)
Withdrawn
Application number
EP01923240A
Other languages
German (de)
English (en)
Inventor
Aaron M. Shapiro
Theodore John Roberts, Jr.
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Silverpop Systems Inc
Original Assignee
Avienda Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Avienda Technologies Inc filed Critical Avienda Technologies Inc
Publication of EP1310066A2 publication Critical patent/EP1310066A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • 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/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
    • 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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10—Multimedia information
    • 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

Definitions

  • This invention relates to systems for distributed delivery of content-rich cornmunications and, more particularly, to methods and systems for composing and transmitting content-rich communications (such as an electronic mail message) using a distributed network of content servers.
  • Email of today is typically text-only with the ability to add digital material (more generally referred to as content) via file attachments.
  • Email is conventionally transmitted and received using standard mail protocols, such as Simple Mail Transfer Protocol (SMTP) and Post Office Protocol (POP), respectively.
  • SMTP Simple Mail Transfer Protocol
  • POP Post Office Protocol
  • SMTP is a protocol for sending email messages between mail servers within a network.
  • Most email systems that send email over the global internet use SMTP to send messages from one mail server to another.
  • the email messages are retrieved using POP or other mail protocols, such as the newer Internet Message Access Protocol (EVIAP).
  • EVIAP Internet Message Access Protocol
  • Rockettalk provides a service that allows users to record audio content and email content as the message itself.
  • the resulting email message cannot include any other multimedia content or even text. This is considered by some to be a less than robust solution to providing rich content messaging. Additionally, if the audio message is lengthy, the email message itself grows to an undesirable size.
  • Signaturemail provides a service that allows content as part of an email message by facilitating the inclusion of a signature block on the bottom of an email or sending a voice message by email.
  • This is only a single feature set instead of a robust tool that can integrate a variety of multimedia content elements into an email message. Furthermore, including such content as part of the message
  • Synchronized Multimedia Integration Language enables Web developers to divide multimedia content into separate files and streams (audio, video, text, and images), send them to a user's computer individually, and then have them displayed together as if they were a single multimedia stream.
  • SMIL is based upon extensible Markup Language (XML) and is related to how web content can be delivered.
  • XML extensible Markup Language
  • SMLL is focused on web serving and not email messaging.
  • it still requires an undesirably large email message (albeit in parts) to be received by the intended recipient.
  • the same information is required to be downloaded through the network's mail servers and then re-assembled causing the need for additional processing and annoying wait periods on the recipient's end.
  • Akamai Technologies of Cambridge, MA has discovered a way in which to deliver multimedia content in a distributed fashion for use by users logging into websites.
  • Akamai provides distributed web caches of content so that users are not logging into a single web content server and causing congestion and poor interactive performance when many users attempt to access the single web content server.
  • the content distributed to Akamai's servers is static and broadcast to multiple servers. In this manner, the serving load is distributed to avoid congestion of a single web server and ultimately to improve the interactive performance of the website.
  • Akamai system intelligently determines which of the multiple copies of the content stored on Akamai servers to access for delivery to the user.
  • the Akamai model of having the same static content maintained on multiple servers for delivery to a requesting user does not resolve the problems noted above with content-rich communications such as content-rich email message delivery.
  • the Akamai model is focused on web content delivery and does not readily translate into a solution for email message delivery.
  • the multimedia content associated with the message is only used once or twice by a potential recipient.
  • the Akamai model becomes problematic for email content used that is only infrequently used because redundantly placing the multimedia content of a large number of email messages onto a large number of servers is time consuming, memory wasteful, and inefficient. Memory storage for each server and network bandwidth is simply wasted broadcasting all of this multimedia content out when it is only used a few times.
  • Methods, systems and articles of manufacture consistent with the present invention overcome the shortcomings of existing systems by using one or more dynamic content servers in a network to improve how content-rich communications are created, delivered, and viewed.
  • Methods, systems, and articles of manufacture consistent with the present invention include a method for transmitting content-rich communications, such as an electronic mail message.
  • content associated with the communication is identified.
  • the content may be accessed from a local memory storage device, captured and then accessed from a multimedia capturing device (such as a scanner), or accessed from within the content server.
  • the identified content is then provided to the content server, typically by transferring the identified content to the content server in a stream of data.
  • methods, systems, and articles of manufacture describe a computer system within a networked environment for transmitting an electronic mail message having a processor, a memory storage device coupled to the processor, and a communications interface also coupled to the processor.
  • the communications interface is also coupled to a content server on the network.
  • the memory storage device maintains content associated with the electronic mail message while the processor can access and identify the content within the memory storage device.
  • the processor can provide the identified content to the content server using the communications interface and then generate information to be sent within the electronic mail message. This information is typically a minimal amount of data (e.g., an instruction set) that references the identified content on the content server.
  • the processor can transmit the electronic mail message via the communications interface to an email client node associated with an intended recipient.
  • methods, systems, and articles of manufacture as embodied and broadly described herein, describe a computer-readable medium, which contains instructions for transmitting an electronic mail message using a content server within a data communication network.
  • content is accessed and identified to be associated with the electronic mail message.
  • the identified content is provided to the content server.
  • all of the content for the message is provided or preferably streamed onto the content server, a minimal amount of information is generated to be sent within the mail message.
  • the information references the identified content on the content server typically using an HTML instruction set.
  • the electronic mail message is then transmitted to an intended recipient without file attachments, without causing a large amount of data to be sent within the message and providing the referenced content for access on the content server.
  • FIG. 1, consisting of FIGS. 1A-1G, are computer screen shot illustrations showing how a front-end client application is used to create and transmit a content- rich email message consistent with an embodiment of the present invention
  • FIG. 3 consisting of FIGS ' . 3A-3E, are computer screen shot illustrations showing how an email client application is used to view a content-rich email message consistent with an embodiment of the present invention
  • FIG. 4 is a block diagram of an exemplary networked system suitable for use with methods and systems consistent with an embodiment of the present invention
  • FIG. 6 is a detailed diagram illustrating client/server interactions between modules on a front-end node, a dynamic content server and an email client node consistent with an embodiment of the present invention
  • FIG. 7 is a flow chart illustrating typical steps for composing and transmitting a content-rich message using a distributed network of content servers consistent with an embodiment of the present invention.
  • a front-end client-side messaging interface that, when advantageously combined with a back-end dynamic content server, fundamentally changes how content-rich communications can be created, delivered, and viewed.
  • the front-end client software can used as a standalone module or coupled with an existing software module (such as an existing mail program) to enhance the functionality of the existing software module when composing and sending content-rich communications.
  • the front-end client software is capable of controlling peripherals, such as scanners, digital cameras, video recorders, and sound recording devices. This allows a user to easily capture and access multimedia data, such as personal videos, sounds, or scanned images, for incorporation into a communication.
  • the communication (such as an enhanced email message) is being composed on the screen
  • content elements of the communication are cleverly streamed out to the dynamic content server instead of actually attaching them to the communication.
  • the dynamic content server stores the content in an optimized location within the network to make it quickly and easily accessible to the intended recipient.
  • This minimal amount of information typically includes some basic content and instructions referencing the content maintained on the dynamic content server.
  • the communication advantageously has a small memory footprint allowing for quick downloads avoiding undesirable delays.
  • messages and “communication” broadly encompasses any mechanism permitting two systems or even two distinct software modules to pass information from one to the other. Examples of such "messages” or “communications” include but are not limited to electronic mail messages; serial or parallel communications between devices; packets; modulated radio frequency signals; infrared signals; modulated light on a fiber optic network, etc.
  • FIG. 1 which includes FIGS. 1A-1G, is a series of exemplary computer screen shot illustrations showing how a front-end client application is used to compose a dynamic content-rich communication (such as an enhanced email message) consistent with an embodiment of the present invention.
  • FIG. 2 and FIG. 3A-3E are a series of exemplary computer screen shots illustrating how the content-rich message appears in an inbox and how it appears when opened for viewing by the intended recipient.
  • a user When a user composes an email message, the user selects one of the drop down menus 115 available on menu bar 105 as illustrated in FIG. IB. For example, a library menu icon on menu bar 105 can be selected to display a series of template choices. The user is able to select one of the templates, such as the "Bubbles" template. Essentially, the template is a set of pre-existing content for use in the email message. As illustrated in FIG. IC, selecting the "Bubbles" template causes a background graphic image along with pre-selected or boilerplate basic content 120 (such as an animation of bubbles moving across the monitor) to appear within window 100.
  • pre-selected or boilerplate basic content 120 such as an animation of bubbles moving across the monitor
  • this additional content may include an audio file formatted in a conventional .MP3 format, a video file formatted in a conventional JPG format, or other multimedia content available on the storage device named "my files.”
  • the additional content appears on the basic background 120 within window 100 as shown in FIG. IE.
  • a graphic representation 130 of the sender's name, address and telephone number appear at a designated part in the body of the mail message.
  • a series of still images 135 has also been selected. The images 135 appear at another location within the body of the message.
  • a sound file was selected to provide some background music when the intended recipient opens and views the email message. The sound file and controls for playing such content also appear within the body of the message as audio indicator 140 and audio controls 145.
  • the front-end client application not only operates as a composition tool, but is also able to control peripheral devices capable of capturing multimedia content.
  • the computer running the front-end client application illustrated in FIG. IF is capable of controlling a video capturing device, such as a digital camera, video camera, a image scanner, or any other kind of device that digitizes or otherwise captures multimedia content.
  • the front-end client application displays captured video content and controls for the video capturing device in a video capture panel 150. Using this panel 150, the user is able to look through potential video footage to find the desired video content for the email message.
  • Predefined templates may be used by the sender to compose an email message having pre-designated locations for different types of content (e.g., video, images, graphics, audio, animation, text, etc.). However, the sender can move those locations using conventional drag and drop techniques known to those skilled in the art or may start "from scratch" without a template with pre-designated locations.
  • the video content is also provided (e.g., formatted into a streamed format and transmitted as a substantially continuous stream of data according to a streaming protocol) to the server for storage.
  • the video content joins the other stored content from the composed email message.
  • the sender uses the 1.1 front-end client application to compose the email message and streams its content to a server prior to transmitting the email message.
  • FIG. 2 is a computer screen shot illustration showing the contents of an inbox for an email client application consistent with an embodiment of the present invention.
  • inbox window 200 displayed by the email client application has a menu bar 205 that is used to select and view email messages, such as messages 215, 220.
  • message area 210 is a conventional email message having its multimedia content sent within bulky file attachments.
  • this conventional message 215 has a memory footprint of approximately 3.2 Mbytes.
  • the second message 220 in message area 210 is an email message composed and transmitted in accordance with an embodiment of the present invention and does not have such bulky file attachments.
  • this second message 220 has a relatively small memory footprint.
  • this second message 220 has a memory footprint of approximately 4 Kbytes.
  • the second message 220 created and transmitted in accordance with an embodiment of the present invention is easily and quickly delivered through existing mail servers on the Internet computer network.
  • FIG. 3 consisting of FIGS. 3A-3E, are computer screen shot illustrations showing how the email client application displays dynamic content-rich email message consistent with an embodiment of the present invention.
  • the email client application displays an email header 305 and a body portion 310 of the email message in response to selecting the second message 220.
  • the email client application interprets the minimal amount of information actually contained within the second message 220 to display some basic content (such as the "bubbles" animation content shown in the body 310 of the email message) while the application also accesses the referenced content by sending a request to the server maintaining the content.
  • the content for the email message is accessed from the server.
  • the server transfers the content from the appropriate memory storage (such as an optimized location within the network) to the requesting email client application.
  • the recipient is unaware of any transition from the basic content sent along with the email message to the streamed content from the server that appears as content 320 within the body of the email message.
  • it is advantageous to optimize the amount of basic content sent along with the actual email message to avoid latency problems and delays when viewing the email message by the intended recipient.
  • FIGS. 1-3 show how content-rich messages having a small memory footprint can be created, sent, and viewed while still using a virtually limitless amount of content and while avoiding the problems associated with sending such content as file attachments.
  • the content illustrated within the body of the email message can be dynamic in that it may change after the email is created but before the intended recipient views the content. For example, a sender may create an email with certain images but later desire to update those images to give the intended recipient the most up to date content possible. Additionally, the content may be considered dynamic in the sense of where within the network it is positioned or re-positioned as will be discussed in more detail below. Thus, dynamic content is made available within the body of an email message for an increasingly robust and media-rich communication experience.
  • FIG. 4 depicts an exemplary distributed network 400 suitable for practicing methods and implementing systems consistent with the present invention.
  • This network 400 is distributed in that it has processing, storage, and other functions which are handled by separate computing units (nodes) rather than by a single main computer.
  • a network 400 may be implemented in a variety of forms (computing elements on a simple bus structure, a local area network (LAN), a wide area network (WAN), the global Internet, a broadband network with set-top communication devices, a wireless network of mobile communicating devices, etc.) that provides an intercommunication medium between its nodes.
  • LAN local area network
  • WAN wide area network
  • the global Internet the global Internet
  • broadband network with set-top communication devices a wireless network of mobile communicating devices, etc.
  • exemplary network 400 is labeled as separate network segments (referred to as subnetworks 420A, 420B, and 420C). While each of these subnetworks are interconnected and are actually part of network 400, it is merely convenient to label them separately into subnetworks to emphasize the different geographic locations of parts of network 400. Those skilled in the art will realize that each of these subnetworks can also be considered a network by itself and may also interconnect other nodes (not shown) or other networks (not shown).
  • subnetwork 420 A interconnects a front-end node 405, a conventional web server 425, a conventional mail server 430, a dynamic content server 440 A, each of which are physically located in the San Francisco, California area.
  • network 400 Other parts of network 400 include subnetwork 420B located in the Atlanta area (interconnecting another dynamic content server 440B and two email client nodes 435A and 435B to network 400) and subnetwork 420C located in the Frankfurt, Germany area. Subnetwork 420C interconnects yet another dynamic content server 440C and another email client node 435 C to network 400.
  • Front-end node 405 is generally considered to be a network node having a processor, memory in which to run programs and create messages and a communications interface to connect to network 420A.
  • front-end node 405 is a conventional personal computer (such as an
  • Front-end node 405 further includes a conventional Ethernet network interface card for connecting to network 400 via a gateway (not shown) from a LAN
  • Front-end node 405 may alternatively use a conventional modem (not shown) to connect to network 400 via a WAN (not shown) that is part of subnetwork 420 A.
  • front-end node 405 can be used to view web pages by sending an appropriately formatted request to web server 425.
  • Front-end node 405 can also send conventional email by sending an appropriately formatted message from front-end node 405 to mail server 430, which will eventually route the message to its intended destination (such as an email client node on the network 400) when requested to do so.
  • a user can create a content-rich email message (similar to that illustrated above regarding FIGS. 1-3) using front-end node 405.
  • front-end node 405 is coupled to a variety of local computer peripherals 410 and remote content storage 415.
  • the coupling may be accomplished via a simple bus connection to the peripheral, a network connection to the peripherals or through a separate interface, such as an USB connection, IEEE-488 bus connection or an RS-232 connection.
  • the precise connection used with the local computer peripherals 410 will depend on the exact type of peripheral used.
  • the local computer peripherals 410 typically include a scanner 411, a local content storage device 412 and a video capture device 413.
  • Local content storage device 412 and remote content storage 415 typically maintain multimedia content such as images, electronic presentations, word processing documents, pre-defined templates and other content useful for making a content-rich email message.
  • email client node 435B is a network node implemented in a personal digital assistant (PDA) form factor while email client node 435C is a network node implemented in a desktop personal computer form factor.
  • PDA personal digital assistant
  • email client node 435C is a network node implemented in a desktop personal computer form factor.
  • any communication device e.g., computer, PDA, mobile radio, cellular phone, set-top receiver, etc.
  • any given node on network 400 may have the functionality of both a front-end node and an email client node.
  • a variety of implementations are possible for an email client node.
  • each is essentially a back-end server that manages dynamic content referenced to be part of email messages.
  • a dynamic content server stores and maintains a database of user created content (such as personal video, digital camera images, personal sound recording) along with a library of existing or commercial content (commercial video clips, commercial sound studio files, etc.) for use when composing a content-rich email message on the front- end node 405.
  • the dynamic content server is a node having at least one processor, memory coupled to the processor for storing content referenced by messages, and a communications interface allowing the processor to be coupled to or in communication with other nodes on network 400.
  • the dynamic content server may be implemented as a single processor, a personal computer, a minicomputer, a mainframe, a multiprocessing machine, a supercomputer, or a distributed sub-network of processing devices.
  • each of the dynamic content servers is a group of FullOnTM computers designed and distributed by VA Linux Systems of Sunnyvale, California.
  • FullOnTM computer is a rack-mountable, dual-processor system with between 128
  • Each FullOnTM computer has two
  • Pentium® LU microprocessors from Intel Corporation and runs the Linux Operating
  • a dynamic content server may be implemented in any of a variety of server and network topologies using computer hardware and software from a variety of sources. Still other embodiments consistent with the present invention may implement a dynamic content server using fault-tolerant integrated service control points within a wireless or landline advanced intelligent telecommunications network (ALN). Additionally, one skilled in the art will appreciate that while a dynamic content server may be implemented as a separate server node, it may also be incorporated into other network nodes, such as web server
  • mail server node 430 would simply be programmed with the functionality described below associated with the back-end dynamic content servers 440.
  • the content is stored on one of the dynamic content servers 440 A- C.
  • the intended recipient uses one of the email client nodes 435A-C to access their email.
  • the email client node used by the recipient requests the content from one of the dynamic content servers.
  • the content can be cleverly pre-positioned within the network 400.
  • the content is initially stored close to an anticipated access point for the communication (i.e., the node from which the communication will likely be viewed and from which the content will likely be requested).
  • the content is intelligently managed by the dynamic content servers and kept optimally close to where the recipient will likely request it.
  • the dynamic content servers advantageously help to reduce latency and improve performance from the intended recipient's perspective.
  • the content should be maintained on the dynamic content server that is physically closer to that node (i.e., dynamic content server 440B). How the determination is made regarding which of the dynamic content servers is closest to the anticipated access point is generally based on factors related to the recipient (such as the recipient's message accessing profile and the recipient's domain name address) and factors related to sender (such as a history of where the sender sends email messages or a language characteristic associated with the message). Additionally, if the content changes or if any of these factors change, the content may be subsequently moved to an updated or more optimal location within the network (i.e., the location of another dynamic content server in the network based on an updated estimation of the access point for the message).
  • FIG. 5 simplifies the FIG. 4 block diagram an exemplary networked system of nodes, servers, and their intercommunication connections suitable for use with methods and systems consistent with an embodiment of the present invention.
  • front-end node 405 is shown connected to mail server 430, which is further connected to email client node 435.
  • conventional email is composed using a mail application module on front-end node 405 for delivery to mail server 430 via an SMTP formatted message.
  • email client node 435 can retrieve such conventional email via a POP3 formatted message or an AP formatted message.
  • a recipient views such conventional email on email client node 435 only after a full email transmission (i.e., the header, body of the message, and all file attachments) has been completed.
  • a full email transmission i.e., the header, body of the message, and all file attachments
  • an embodiment of the present invention takes advantage of one or more dynamic content servers 440 (also referred to as the GLOBAL MESSAGING NETWORKTM Platform from Avienda Technologies) when composing, delivering, receiving and viewing content-rich communications such as email messages.
  • dynamic content servers 440 also referred to as the GLOBAL MESSAGING NETWORKTM Platform from Avienda Technologies
  • front-end node 405 accesses a source for content 505, including controllable peripherals 410 and remote storage 415, gathers content and creates a content-rich message.
  • a minimal part of the email message is sent to mail server 430 for ultimate delivery to email client node 435.
  • the content associated with the message is streamed to dynamic content server 440 via a conventional hypertext transfer protocol (HTTP) network connection.
  • HTTP hypertext transfer protocol
  • FIG. 6 illustrates the client/server interactions between front-end node 405, one of the dynamic content servers 440 and one of the email client node 435 consistent with an embodiment of the present invention.
  • the front-end node 405, dynamic content server 440 and the email client server 435 are each illustrated as containing software modules that interact with each other.
  • Such software modules operate within memory of the particular network nodes and, as mentioned previously, provide functionality when used in conjunction with one or more processors (e.g., discrete electronic components, microcontrollers, microprocessors, optical processors, bio-processors, or any other kind of device that is able to process representations of information) and the interfacing hardware and software enabling intercommunication between the nodes.
  • processors e.g., discrete electronic components, microcontrollers, microprocessors, optical processors, bio-processors, or any other kind of device that is able to process representations of information
  • a front-end client application or module 610 is shown within memory of the front-end node 405.
  • Front-end client module 610 is responsible for creating and transmitting content-rich communications and is preferably referred to as the POWER MESSAGINGTM Platform from Avienda Technologies.
  • front- end client module 610 is implemented as a standalone software tool used to create a content-rich communication (such as an email message) that is delivered without file attachments, without the use of separate plug-in software, and without incurring lengthy downloads.
  • front-end client module 610 is implemented as a web- based communication application that allows users to access front-end client node 405 as a website hosting server.
  • front-end client module 610 operates as a web-based mail application (similar to web-based email products from
  • front-end client module 610 is implemented as an extension to an existing communications application program 605 (e.g., communication programs such as the Microsoft OutlookTM electronic mail application or the web-based mail application from Hotmail.com) to enable enhanced functionality with the existing application program 605.
  • front-end client module 610 is responsible for controlling various computer peripherals used to capture content, streaming the content to a dynamic content server and sending the rest of the email message to the mail server.
  • front-end client module 610 uses software interfacing mechanisms in order to share information between it and the application module 605.
  • existing communications application module 605 integrates select functionality of front-end client module 610 (such as its ability to control peripherals and capture content) and uses front-end client module 610 to determine what parts of the message are sent conventionally and what parts are more advantageously streamed to a dynamic content server.
  • the software interfacing mechanisms implementing such integration of program modules are conventional object linking and embedding (OLE), ActiveX controls and other common object model (COM) technology made available by Microsoft Corporation.
  • OLE object linking and embedding
  • COM common object model
  • COM technology is used to allow disparate technologies to interact and communicate information. More specifically, COM technology defines a binary standard that enables two applications to communicate through object-oriented interfaces without requiring either of the applications to know anything about the other's implementation.
  • front-end client module 610 interacts with OLE objects and ActiveX controls available within the existing application module 605.
  • the application module 605 When executed, it initializes its ActiveX controls.
  • front-end client module 610 is essentially able to instruct the ActiveX control responsible for the toolbar to include a button that allows the user to send a message as an enhanced email message using the front-end client module 610.
  • front-end client module 610 controls computer peripherals (such as local computer peripherals 410) to capture and access content for placement within the message.
  • captured and accessed content includes video files 615, image files 620, audio files 630 and graphics files 635 (including static and animated graphics). These files may be captured through media input devices or may be already stored in local content storage device 412 and remote content storage 415.
  • Front-end client module 610 further allows a user to import and convert standard text files 625 containing word processing documents, electronic presentations or spreadsheets.
  • the text files 625 may include Microsoft Word formatted document files, Microsoft PowerPoint formatted presentation files, or
  • Front- end client module 610 typically converts these files into a format (such as a conventional HTML format) that can be easily referenced within the instruction set sent along with the email message.
  • front-end client module 610 causes this conversion to occur by sending the text file 625 to dynamic content server, which preferably performs the conversion process. This advantageously allows the dynamic content server to shoulder the conversion workload while freeing up the front-end client module 610 to do other tasks. However, it is contemplated that these conversion tasks could be done by front-end client node 405 or any other node on network 400.
  • Front-end client module 610 can also use or import content for use within the body of the email message by accessing a library database 660 within one of the dynamic servers 440 on the network.
  • Third parties can provide such media libraries for use by others. Examples of such third party content library database 660 would include templates (e.g., personal message template, corporate memo template, etc.), graphics libraries, video databases from a television company or a library of sound files licensed from a sound studio.
  • front-end client module 610 accesses a selected part of such a library database 660 by making an HTTP connection to dynamic content server 440.
  • Front-end common gateway interface (CGI) script 640 serves the connection request for content by communicating with front-end content daemon 645 within dynamic content server 440.
  • CGI common gateway interface
  • front-end content daemon 645 manages the content within dynamic content server 440.
  • Those skilled in the art will be familiar with using a CGI script as a conventional software mechanism for handling server requests from the network.
  • daemons are background processes custom written to perform specific tasks and are commonly used within UNIX-based operating environments.
  • third party content library databases 660 can be used to increase the potential multimedia content palette for the email composer.
  • Front-end client module 610 typically includes tools used to manipulate the content elements as they are accessed and placed in a desired layout.
  • the layout is predefined with designated locations for different types of content (e.g., images, sound, video, textual information on who is sending the message, etc.).
  • the layout is not predefined allowing the user to creatively place and format the content to appear in a desired manner using known drag-and-drop techniques.
  • front-end client module 610 further allows placement of controls, such as a start button, stop button, volume level, rewind button, etc., into the body of the message. Additionally, front-end client module 610 may have its own integrated set of tools for creating content, such as drawing tools, text tools, image processing and manipulation tools, word wrapping tools, video editing tools, and animation tools. The ability of the front-end client module 610 to provided such an integrated tool that is capable of handling various types of content in differing formats with a robust tool set to edit, manipulate and create an effective content-rich message is a distinct advantage in this embodiment of the present invention.
  • the content As the content is placed into the body of the message, the content is provided to the dynamic content server 440 to be maintained until the recipient views the message.
  • streaming to dynamic content server 440 begins as soon as the content is placed.
  • other embodiments of the present invention may begin streaming the content after a determination is made as to whether the message is ready to be sent and a complete set of content has been selected and placed.
  • each content element is formatted into a stream of data according a conventional streaming protocol, preferably the Advanced Streaming Format (ASF) developed by Microsoft Corporation.
  • ASF Advanced Streaming Format
  • ASF is a streaming multimedia file format but that other streaming formats may also work with the principles of the present invention.
  • Examples of other possible streaming formats include without limitation ActiveMovie, AVI, RealAudio, RealVideo, QuickTime, Real Time Streaming Protocol (RTSP) that uses Real Time Transport Protocol (RTP) to format packets of multimedia content, and any other communication protocol that allows for data to be transferred and processed as a steady or time sensitive stream.
  • the ASF streaming format for all content, it is further contemplated that not all content sent to and from the dynamic content server is streamed.
  • the audio and video content may be streamed according to the ASF streaming format while the images may be sent and kept in their native file format.
  • the user causes a daemon (not shown) within front-end client module 610 to cue the message for transmittal.
  • This daemon analyzes the message content and determines if any content from the third party content library database 660 (also called an organizational library) or the user stored content database 665 (also called the global library) have been used.
  • the daemon also makes sure the message has the required address(s) of the referenced content stored on the appropriate dynamic content server, sending the SMTP message and verifying that the message was actually sent.
  • streamed content is provided to front-end CGI script 640 on dynamic content server 440 for processing and routing by front-end content daemon 645 to the appropriate storage location via an application programming interface (API).
  • front-end content daemon 645 causes the streamed data to be stored using methods defined by the API.
  • the streamed data may be stored in differing formats. For example, audio content and video content are generally stored as ASF streams while images are typically stored in their native file format (e.g., bitmap fo ⁇ nat, JPG format, GIF format, etc.).
  • the content is stored without regard to how the parts of the content (e.g., audio, video, images, etc.) are sent out in response to a request.
  • the communication is an HTML based message
  • a request for the objects is sent to a dynamic content server.
  • each of the objects is independently streamed back to the requesting node without regarding to a sequence of the content.
  • Determining the desired location for content associated with a communication is another aspect of an embodiment of the present invention that provides an advantage in helping to reduce latency and avoid congestion and delays on the recipient's end.
  • the dynamic content is pre-positioned into a desired location on the network to optimize delivery of the dynamic content.
  • This desired location is proximate to an anticipated access point for the particular commumcation that references that content.
  • This anticipated access point is intelligently determined based on historical or sender/recipient profile information and can be subsequently or even periodically re-determined to ensure the content is maintained in an optimum network location at any given moment.
  • the estimation is made depending on factors such as the sender's own access point location, the sender's transmission patterns and a language characteristic of the message. For example, a sender composes and sends a content-rich message to a recipient without a history of accessing messages using the dynamic content server. When the server reviews a transmission history on the sender indicating that 80% of email messages transmitted from this sender are accessed in the Atlanta, Georgia area, then front-end content daemon 645 will store the content on dynamic content server 440B physically located in Atlanta, Georgia.
  • the message's content is typically stored on the dynamic content server that is closest to the front-end node from which the message was sent. If the server scans the content itself, the server may be able to determine a language characteristic (e.g., some of the content is in the French language or that the title is written in Chinese). Those skilled in the art will realize that existing character encoding schemes, such as UNICODE, and efficient inline language determination methods provide the ability to make such a determination. Armed with this information, the dynamic content server is able to make a more intelligent assessment of the anticipated access point and a better determination of the desired location for the message's content.
  • a language characteristic e.g., some of the content is in the French language or that the title is written in Chinese.
  • this information along with information on the sender can be intelligently used as factors in a variety of weighted decision systems or even using an expert or artificial intelligence system as part of the dynamic content server to make the determination of the desired or optimal location for the message's content.
  • the dynamic content server When a recipient receives a content-rich communication (such as an email message) and accesses the communication's content, the dynamic content server (namely a content retrieval daemon 655) records and tracks the actual node from which the particular recipient is accessing the communication. Over time, the dynamic content server builds a profile of previous communication accessing activities (including parameters on node location, time of day, and the day of the week when the recipient accessed the relevant content). The efforts of the content retrieval daemon 655 to track and build this set of information on the recipient's message accessing activities can then be cleverly used by the front-end content daemon 645 when making the determination of where to store the content for a new message.
  • front-end content daemon 645 is responsible for subsequently making additional determinations of the desired location for the content stored within user stored content database 665 and transferring the appropriate stored content to another dynamic content server as needed. While re-determining the desired location for content is typically performed by front-end content daemon 645 once per shift (i.e., three times a day), an additional optimization can be made. This optimization involves reviewing when or where (e.g., the time of day) that the intended recipient historically accesses their messages and scheduling a re-evaluation of the desired location near but prior to that time of day.
  • front-end content daemon 645 or a separate process running on each dynamic content server may periodically or even continually monitor content stored in user stored content database 665 and identify the appropriate time to re-evaluation the desired location for each content. At the identified time, such re-evaluations are performed and, if necessary, the related content is then transferred to another dynamic content server to help reduce latency and provide an even more robust communications delivery system.
  • front-end content daemon 645 or a separate process running on each dynamic content server may periodically or even continually monitor content stored in user stored content database 665 and identify the appropriate time to re-evaluation the desired location for each content. At the identified time, such re-evaluations are performed and, if necessary, the related content is then transferred to another dynamic content server to help reduce latency and provide an even more robust communications delivery system.
  • similar daemons and processes running on those servers will later re-evaluate the position of the transferred content.
  • the content for a new email message is stored in Atlanta area dynamic content server 440B. This position was selected because the particular recipient accessed their email messages from Frankfurt, Germany but on the weekends they accessed their messages from Atlanta, Georgia. If the intended recipient did not read the message until the following week on Tuesday and the content remained in an Atlanta area server, the dynamic content would be relatively remote from where the recipient is likely to access the message.
  • the dynamic content server re-determines the desired location for the message's content on Monday and finds that the new or updated anticipated access point was now Frankfurt, Germany. Accordingly, the content stored on the Atlanta area dynamic content server 440B is transferred to the Frankfurt area dynamic content server 440C. In this manner, the system provides for dynamic content and dynamic updating of where such content is located on the network.
  • a dynamic content server such as dynamic content server 440
  • a conventional mail server such as mail server 430
  • a conventional mail server such as mail server 430
  • a single physical server such as dynamic content server 440
  • a conventional SMTP message and its associated content are sent to the same node.
  • the SMTP message maybe conventionally routed and processed for delivery to the email client node requesting the message.
  • both the SMTP message and its contents may be pre-positioned in an optimal network location and transferred to better network locations depending upon an anticipated access point for the message. In this manner, the intended recipient can advantageously, efficiently and quickly deliver and access both the message and the message's content.
  • dynamic content server 440 is also able to provide a variety of tracking features related to the content.
  • the dynamic content server (typically via content retrieval daemon 655) can track when the content has been requested and from where (e.g., the IP address of the requesting email client node). If the recipient forwards the message to another recipient, that recipient must send another request for the content to the dynamic content server.
  • the dynamic content server can allow or prevent content from being forwarded to anyone other than the intended recipient.
  • the sender may indicate when composing the message that the message's content is sensitive and should not be forward to others.
  • front-end client module 610 When streaming that content to dynamic content server, front-end client module 610 communicates this restriction to front-end content daemon 645, which forwards this restriction information to content retrieval daemon 655.
  • front-end content daemon 645 When another recipient attempts to get the restricted content by sending a request to email client CGI script 650 which is then handled by content retrieval daemon 655, the content is not streamed back out to the requesting email client node.
  • an auto-deleting feature can be implemented within a dynamic content server to automatically delete content associated with a particular message.
  • the content may be composed on the front-end client module to have a limited shelf-life. If so, front-end client module 610 sends an indication of such a shelf life to dynamic content server when streaming the content to it and after a designated amount of time, the content is deleted from the user stored content database 665.
  • the content may be set to delete after a designated number of accesses instead of after the designated amount of time. If the email client independently deletes the message prior to viewing the content, an indicator is preferably sent back to the dynamic content server so that the user-created dynamic content stored in the user stored content database 665 can be deleted.
  • the dynamic content server may also be implemented to handle security protocols related to the content. Some of the content may be personal, confidential or proprietary.
  • the dynamic content server (as well as the front-end client module 610 and the receiving email client module 670) may use custom or commercially available security protocols that may be overlaid onto content streams as they exit the front-end node 405 and the dynamic content server 440 in order to provide a secure email environment.
  • a conventional triple DES security protocol is preferred to be overlaid on outgoing streams of content to provide secure messaging.
  • Other security protocols may be used as well.
  • the email client module 670 gets the message having a minimized amount of information included within it.
  • This minimal information typically includes an HTML instruction set defining the layout for the body of the message and referencing particular content stored in user stored content database 665 on dynamic content server 440.
  • HTML instruction set is essentially a set of instructions defining the layout and content within that layout using HTML terms.
  • an embodiment of the present invention contemplates using any type of instruction set or, more broadly described, any kind of information that references the content associated with the email message as the minimal information sent with the email message.
  • Some basic content may also include the minimal information received.
  • the basic content contains content describing the background graphics for the body of the email message, a graphical representation of information on the sender (such as the sender's name and email address) along with a short animation, such as a series of bubbles appearing (as illustrated in FIGS. 3A-3B).
  • email client module 670 can display this basic content to provide the illusion of seamless speed and no delays while the module 670 is requesting and processing the streamed content from the dynamic content server.
  • Email client module 670 Once the minimal set of information is received by email client module 670, the information is analyzed and interpreted to determine information about the body of message. This determined information includes the header information for the message (e.g., sender information, recipient information, and subject line information) and references to content stored on the dynamic content server 440. Email client module 670 then attempts to access the content by generating a request that is sent over an HTTP network connection to the dynamic content server 440.
  • This determined information includes the header information for the message (e.g., sender information, recipient information, and subject line information) and references to content stored on the dynamic content server 440.
  • Email client module 670 attempts to access the content by generating a request that is sent over an HTTP network connection to the dynamic content server 440.
  • a proxy server sits between email client module 670 and dynamic content server 440.
  • the proxy server intercepts all requests to the dynamic content server 440 to see if the it can fulfill the request from local storage without having to access the real server (i.e., dynamic content server 440).
  • the proxy server is preferably implemented as a SQUID proxy cache available from vendors such as Pushcache.com, Inc., Austin, Texas and Industrial Code and Logic located in Cambridge, Ontario, Canada.
  • the proxy server determines if the requested content is located locally on the email client node 435. If the requested content is stored locally, a reference is returned to the requesting daemon that is part of email client module 670. Otherwise, the proxy server sends a request to a content server (typically the nearest dynamic content server 440) where the content is located.
  • a content server typically the nearest dynamic content server 440
  • the request is received by email client CGI script 650 and passed onto content retrieval daemon 655.
  • Content retrieval daemon 655 queries and gathers the appropriate content from user stored content database 665. If the requested content is located on another content server, then the correct user stored content database is accessed to gather the requested content. The content is then provided in a stream back to the requesting email client module 670 through the proxy server.
  • the requested content is typically stored within the proxy server's local storage in a least used memory queue so that future requests may be locally served.
  • the least used memory queue operates to keep popularly requested content while discarding and writing over less frequently requested content.
  • step 705 content is identified for the message.
  • this content may be located in local storage (such as local content storage 411 or remote content storage 415) or in storage on the dynamic content server (such as in third party content library database 660).
  • the content may also be identified by capturing it using a local peripheral, such as a scanner 411 or video capture device 413.
  • the identified content is accessed.
  • the content is accessed from the local storage, remote storage or other local peripheral and brought back to front-end client module 610.
  • selected video footage captured using video recording device 413 is accessed and read as video content by front-end client module 610 as shown in FIG. IF.
  • the front-end client module 610 is merely an extension or thin application that extends the functionality of an existing mail application module 605
  • the content is identified and accessed when the front-end client module 610 communicates with the existing mail application module 605 regarding content for the message.
  • the location for such accessed content is determined within the body of the message. For example, in the exemplary embodiment illustrated in FIG. 1G, the video content is placed in the center of the message atop one of the graphic images already shown on the background 120.
  • the content is provided to a dynamic content server in a formatted stream of data.
  • This is conventionally referred to as streaming content to memory on the dynamic content server.
  • a streaming protocol is used to format the content.
  • this streaming protocol is ASF for audio and video streams.
  • the protocol used for static images is typically HTTP sockets.
  • step 725 if there is no more content to add to the message, then the message is deemed to be complete or done and step 725 proceeds to step 730.
  • step 725 proceeds back to step 705 because there remains additional content to be added to the message.
  • an instruction set is created that references the content that has been streamed to the dynamic content server.
  • this instruction set is typically a set of HTML instructions defining the multimedia layout within the body of the language. Furthermore, this set of HTML instructions references the particular content for each part of the layout.
  • a minimal amount of information is then transmitted to the intended recipient.
  • This minimal amount of information typically includes the references to the content on the dynamic content server. Additionally, the minimal amount of information usually includes a predetermined subset of content (sometimes called basic content) that will initially be viewed by the intended recipient when they open the transmitted message and while the content on the dynamic content server is being streamed into the body of the transmitted message.
  • a predetermined subset of content sometimes called basic content
  • program modules illustrated in FIG. 6 may be implemented in a variety of ways and include multiple other modules, programs, applications, scripts, processes, threads, or code sections that all functionally interrelate with each other to accomplish the individual tasks described above for each module, script, and daemon.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Les procédés, les systèmes et les articles de fabrication de cette invention permettent de composer et de transmettre une communication (telle qu'un message électronique) au moyen d'un serveur de contenu à l'intérieur d'un réseau de communications. Le contenu associé à la communication est identifié, généralement en accédant à la mémoire ou en capturant des dispositifs périphériques. Un emplacement destiné au contenu identifié est ensuite déterminé à l'intérieur d'une présentation pour le corps de la communication. Le contenu est ensuite envoyé vers un serveur de contenu dynamique au lieu d'être relié à la communication elle-même. Lorsque tout le contenu destiné à la communication a été identifié et envoyé au serveur, une quantité minimum d'informations est transmise au destinataire déterminé à l'intérieur de la communication. Cette quantité minimale d'informations transmises comprend une série d'instruction faisant référence au contenu de la communication stockée sur le serveur.
EP01923240A 2000-04-10 2001-04-10 Procedes et systemes de composition et de transmission de communications riches en contenu Withdrawn EP1310066A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US54565200A 2000-04-10 2000-04-10
US545652 2000-04-10
PCT/US2001/011589 WO2001078334A2 (fr) 2000-04-10 2001-04-10 Procedes et systemes de composition et de transmission de communications riches en contenu

Publications (1)

Publication Number Publication Date
EP1310066A2 true EP1310066A2 (fr) 2003-05-14

Family

ID=24177049

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01923240A Withdrawn EP1310066A2 (fr) 2000-04-10 2001-04-10 Procedes et systemes de composition et de transmission de communications riches en contenu

Country Status (3)

Country Link
EP (1) EP1310066A2 (fr)
AU (1) AU2001249952A1 (fr)
WO (1) WO2001078334A2 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3968277B2 (ja) * 2002-08-26 2007-08-29 株式会社日立製作所 メールサーバ、そのメールサーバを実現するためのプログラム及び携帯端末
US8037127B2 (en) 2006-02-21 2011-10-11 Strangeloop Networks, Inc. In-line network device for storing application-layer data, processing instructions, and/or rule sets
US8166114B2 (en) 2006-02-21 2012-04-24 Strangeloop Networks, Inc. Asynchronous context data messaging
US8626840B2 (en) 2006-11-17 2014-01-07 Comverse Ltd. Method and system for generating a referencing secondary electronic mail message from a primary electronic mail message
US9906620B2 (en) 2008-05-05 2018-02-27 Radware, Ltd. Extensible, asynchronous, centralized analysis and optimization of server responses to client requests
US9549039B2 (en) 2010-05-28 2017-01-17 Radware Ltd. Accelerating HTTP responses in a client/server environment
WO2012101585A1 (fr) 2011-01-28 2012-08-02 Strangeloop Networks, Inc. Hiérarchisation du rendu d'une image sur la base d'une position à l'intérieur d'une page web
WO2012160499A1 (fr) * 2011-05-23 2012-11-29 Strangeloop Networks, Inc. Rendu optimisé de contenu dynamique
WO2013038320A1 (fr) 2011-09-16 2013-03-21 Strangeloop Networks, Inc. Accélérateur de ressource mobile
US11184303B2 (en) 2017-12-29 2021-11-23 Titus Deac Brevity-codified messaging system and process with pre-composed messages made of prefabricated icons, and methods of use

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5781901A (en) * 1995-12-21 1998-07-14 Intel Corporation Transmitting electronic mail attachment over a network using a e-mail page
US20020049852A1 (en) * 1999-12-06 2002-04-25 Yen-Jen Lee Global messaging with distributed adaptive streaming control

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0178334A2 *

Also Published As

Publication number Publication date
WO2001078334A3 (fr) 2002-05-16
WO2001078334A2 (fr) 2001-10-18
AU2001249952A1 (en) 2001-10-23

Similar Documents

Publication Publication Date Title
US6965926B1 (en) Methods and systems for receiving and viewing content-rich communications
US7631259B2 (en) System and method for media-enabled messaging having publish-and-send feature
US9723460B1 (en) Device message management system
US20020049852A1 (en) Global messaging with distributed adaptive streaming control
US8407292B2 (en) E-mail protocol optimized for a mobile environment and gateway using same
US6816884B1 (en) System and method for creating conversationally-styled summaries from digesting email messages
US6925495B2 (en) Method and system for delivering and monitoring an on-demand playlist over a network using a template
US6509910B1 (en) Method and system for interfacing with a digital media frame network
US7606911B1 (en) System and method for providing status information from multiple information sources in a single display
US6535228B1 (en) Method and system for sharing images using a digital media frame
US7155477B2 (en) Method and system for continuous interactive communication in an electronic network
US20050223073A1 (en) Attaching applets to messaging communications
WO2001010128A1 (fr) Messager video instantane
US20040172472A1 (en) System and method for providing status information from multiple information sources in a single display
JP2003508855A (ja) １グループの参加者間の情報通信システム
US8086719B2 (en) Bypassing uploading of data from a wireless device using outbound attachment caching
JPH09101928A (ja) 情報提供装置
RU2323527C2 (ru) Система и способ обслуживания передачи мультимедийных сообщений
EP1310066A2 (fr) Procedes et systemes de composition et de transmission de communications riches en contenu
EP1310067A2 (fr) Procedes et systemes de traitement de contenu de communications riches en contenu
Metso1A et al. Mobile Multimedia Services–Content Adaptation
CN101589588A (zh) 用于电子邮件网关的方法和装置
Hou et al. Multimedia Messaging Systems
KR20000053723A (ko) 동영상 메일링 방법
WO2008034149A2 (fr) Système d'hébergement et de dissémination de données pour dispositifs mobiles

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20021104

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SILVERPOP SYSTEMS INC.

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20051031