Browser-based email system with user interface for audio/video capture

Abstract

A browser-based email system has a thin client connected to a host mail server. The thin client implements a browser. The host mail server provides pages to the thin client, which can be rendered by the browser to present an email service to a user. The thin client is equipped to receive audio and video data and supports a user interface to facilitate capture of the audio or video data for inclusion in an email message. After a data stream is captured and stored locally at the client, the browser submits a request to the host mail server that contains a token in lieu of the data stream. The host mail server returns a response specifying a new page that contains the email message. The response also includes the token and indicates a location in the new page at which the audio or video data is to be rendered. Upon receiving the response, the browser inserts the data stream into the new page at the location and renders the new page. After the user has reviewed the email message, the user can send the email message, causing the browser to submit another request to the host mail server that contains both the email message and the audio or video data. Upon receiving this second request, the host mail server converts the email message and the audio or video data to a MIME message and forwards the MIME message to the intended recipient.

Description

TECHNICAL FIELD

[0001] The present invention relates to browser-based email systems.

BACKGROUND

[0002] Email systems facilitate the exchange of electronic mail over a network, such as a LAN (local area network), WAN (wide area network), or public network (e.g., Internet). Most people are familiar with traditional computer email systems, which are constructed on a client-server model. The email system involves a server-based mail program residing on the server computer to manage the exchange of email messages over one or more networks and a client-based mail program residing on the client to implement a mailbox that receives and holds the email messages for a user. The client-based mail program also implements a graphical user interface that enables the user to open and read mail, or to create new mail messages.

[0003] To support the client-based mail program, the traditional computer email systems assume that the clients are full functioning general-purpose computers with their own operating system, processing resources, memory resources, and so forth. Examples of such clients include workstations, desktop computers, laptops, and the like.

[0004] With the advent of alternative client products having limited processing capabilities and memory, more server centric email systems have evolved that rely on the Internet and the World Wide Web (Web) as the delivery vehicle. These scaled down or “thin” clients are typically constructed with just enough functionality to enable access to the server computer over a network. The thin client commonly implements a browser, but does not have the ability to execute other application programs, such as traditional client-based mail programs.

[0005] Examples of thin clients include low cost computers known as “network computers” or “NCs” and television set-top boxes (STBs). NCs and STBs provide limited local processing, but are primarily reliant on the server for most processing.

[0006] Browser-based email systems are well suited for thin clients. The client mailbox is maintained at a server and the client accesses the mailbox using standard Web protocol, such as HTTP (hypertext transport protocol). The server serves images of the mailbox and opened mail messages as standard pages written in a markup language, such as HTML (hypertext markup language). The client browser renders the pages so that the user perceives a full functioning email system.

[0007] This invention is directed to improving browser-based email systems.

SUMMARY

[0008] This invention concerns a browser-based email system having a thin client connected to a host mail server. The thin client implements a browser. The host mail server provides pages to the thin client, which can be rendered by the browser to present an email service to a user. One page contains a mail message screen that allows a user to construct an email message.

[0009] According to one aspect of the invention, the email system allows the thin client to capture audio and video data for inclusion with the email message. The thin client is equipped with a microphone and video input to receive audio and video data. The client browser supports a user interface that includes pop-up capture panels for both audio and video, with each capture panel enabling the user to record a selected clip and add the clip to the email message. The captured data clip is stored locally at the client.

[0010] After a data stream is captured, the browser submits a request to the host mail server that contains a token in lieu of the data clip. The host mail server returns a response specifying a new page that contains the email message. The response also includes the token and indicates a location in the new page at which the audio or video data is to be rendered. Upon receiving the response, the browser inserts the audio or video data into the new page at the location and renders the new page.

[0011] After the user has reviewed the email message, the user can click a “Send” link on the rendered email page to send the email message to an intended recipient. Upon activation of the “Send” link, the browser submits another request to the host mail server that contains both the email message and the audio or video data. Upon receiving this second request, the host mail server converts the email message and the audio or video data to a MIME message and forwards the MIME message to the intended recipient, where it can be rendered in full.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 illustrates a browser-based email system.

[0013] FIG. 2 illustrates a client in the email system.

[0014] FIG. 3 is a block diagram of a set-top box employed in the client.

[0015] FIG. 4 is a block diagram of the software/hardware architecture of the client.

[0016] FIG. 5 illustrates an email page rendered by a Web browser.

[0017] FIG. 6 illustrates an audio capture panel overlaid on the email page of FIG. 5.

[0018] FIG. 7 illustrates a video capture panel overlaid on the email page of FIG. 5.

[0019] FIG. 8 illustrates the email page of FIG. 5, but with a video or audio clip attached.

[0020] FIGS. 9 and 10 are a flowchart illustrating steps in a method for capturing audio and video clips within an email message.

DETAILED DESCRIPTION

[0021] This invention concerns a browser-based email system and method for capturing audio and video clips within an email message. The invention is described generally in the context of thin clients, and more specifically in a preferred context of a browser-based set-top box (STB). In particular, aspects of this invention may be implemented in a system that integrates Web access and television so that users can access Web content on the Internet through a standard television set. The system includes a set-top box having a television tuner and standard network interface devices to enable simultaneously viewing of both television programs and web programming. One example of this system is the “WebTV®” Internet system, maintained by WebTV Networks, Inc. of Palo Alto, Calif. It is noted, however, that aspects of this invention may be implemented in contexts other than television and set-top boxes.

[0022] System Overview

[0023] FIG. 1 shows a browser-based email system 20 having a client 22 connected to a host mail server 24 via a network 26. Other remote mail servers 28 are also coupled to the network. The system is representative of an Internet system in which the client and servers are interconnected via the Internet 26. The client 22 and servers 26 and 28 connect to the Internet 26 via conventional means, such as a direct-dial telephone, ISDN (Integrated Services Digital Network), or other similar connection.

[0024] Although not shown, the client 22 and servers 26 and 26 may use an intermediary Internet Service Provider (ISP) to facilitate connection to the Internet 26. In other configurations, the client 22 may connect directly to the host mail server 24 via a second network, such as a cable or telephone network.

[0025] The client 22 is preferably a thin client having enough processing and storage capabilities to support a Web browser. As one exemplary implementation, the client 22 includes a set-top box in conjunction with a television set to delivery both television and Web programming. This exemplary implementation is described below in more detail with reference to FIG. 2. Other implementations of a thin client (e.g., network computer) may alternatively be implemented within the context of the email system.

[0026] The client 22 implements a hyperlink browser 30 to browse the Web and to use the email system. The Web browser 30 presents a user interface (UI) 32 that includes a screen space to display rendered pages written in a markup language, such as HTML. The UI 32 provides separate windows or exposable panels that enable a user to capture audio, video, other types of data clips for inclusion in a mail message. The client also has a storage 34 to store the data clips.

[0027] The host mail server 24 implements a mail service 36 to facilitate the exchange of email messages with the remote mail servers 28 over the network 26. The mail service 36 has a mailbox for the client 22 that receives and holds email messages addressed to the client. The mail service 36 extends email functionality to the client 22 by creating pages that appear, when rendered by the client browser 30, as an interface to an email program. For instance, when the user first enters the email service, the initial page might contain a listing of email messages arranged chronologically according to their delivery date.

[0028] If the user wishes to open one of the mail messages, the user clicks a button or hyperlink that causes the client to send a request to the mail service 36 at the host mail server 24. In response, the mail service 36 opens the requested mail message, constructs a new HTML page containing the contents of the mail message, and downloads the HTML page to the client 22. The user can then undertake other email functions, such as replying to a message or creating a new message, with each action resulting in the mail service 36 creating and downloading an HTML page with an appropriate image. Thus, to the user, the client appears to be running a local email program.

[0029] Exemplary Client

[0030] FIG. 2 shows the client 22 according to one exemplary implementation. It includes a set-top box 40, an ordinary television set 42, and a remote control 44. The client 22 uses the television set 42 as a display device for displaying video data and the browser UI. The set-top box 40 is coupled to the television set 42 by a video link 46, such as RF (radio frequency), S-video, composite video, or other equivalent form of video link. Although the client shows the STB implemented separately from the television set, the STB functionality may alternatively be integrated into the television set.

[0031] The set-top box 40 includes hardware and/or software for receiving and decoding a TV signal 48, such as an NTSC, Phase Alternate Lines (PAL), Sequential Couleur Avec Memoire (SECAM), High Definition Television (HDTV), or other TV signal, and providing video data to the television set via video link 46. The STB 40 includes a standard modem and an ISDN modem to support a telephone connection 50 or an ISDN connection 52. The set-top box 40 has an IR interface 54 to receive IR signals from the remote control 44. Power line 56 provides power to the STB 40.

[0032] FIG. 3 shows the internal components of the set-top box 40. It has a central processing unit (CPU) 60 coupled to an application-specific integrated circuit (ASIC) 62. The CPU 60 executes software designed to implement features of the present invention and to control operation of the client. ASIC 62 contains circuitry to implement certain features provided by the client and forms a communications chip that interfaces other STB components.

[0033] ASIC 20 is coupled to a Read Only Memory (ROM) 64 and a Random Access Memory (RAM) 66. ROM 64 stores program code for implementing the browser software to be executed by the set-top box 40. ROM 64 may be a programmable ROM (PROM) or any form of erasable PROM (EPROM) or Flash memory.

[0034] The IR interface 54 detects IR signals transmitted by remote control 44 and converts them to electrical signals input to the ASIC 62. A television decoder 68 decodes television signals received from a television source, such as cable, satellite, or antenna. ASIC 20 is coupled to an audio digital-to-analog converter (DAC) 70 and a video encoder 72, which provide audio and video output to the television. ASIC 62 is further coupled to a standard telephone modem 74 and an ISDN modem 76.

[0035] The STB 40 is also equipped with a microphone input 78 to receive audio input and a video input 80 to receive video input from, for example, a video camera. The storage 34 is coupled to ASIC 20 to store the audio/video clips captured at the client. The storage 34 includes any suitable medium for storing electronic data, such as magnetic disks, optical disks, and the like.

[0036] Browser Software

[0037] FIG. 4 shows various components of the client browser software 30 and the functional relationships between the components. The client receives Web pages over the network connection in the form of HTML documents. Each HTML document is initially input to a communications manager 90, which performs functions to receive the HTML document over the network connection including handling high-level communications protocols, such as HTTP (Hypertext Transport Protocol), TCP/IP (Transmission Control Protocol/Internet Protocol), and so forth. The communications manager 90 provides a received HTML document to the HTML parser 92 and a streams manager 94. The HTML parser 92 converts the HTML document descriptions to a displayable format. The streams manager 94 controls and coordinates movement of data throughout the client, including the flow of television video streams to the display 42.

[0038] The HTML parser 92 passes images (e.g., JPEG or GIF) provided in the HTML document to a graphics engine 96, which is responsible for measuring and drawing images. The images and text are then passed to a layout engine 98, which arranges them in a prescribed layout for presentation on the display 42.

[0039] An input system 100 handles various signal inputs to the set-top box 40, including IR signals received from the remote control 44, audio streams received via the microphone input 78, and video streams received via the video input 80. The IR signals received at the input system 100 are representative of choices made by the user. These choices are passed to a selection handler 102, which identifies the choices and initiates an appropriate response (e.g., loading a new page, bringing up a window, begin/end capture of audio or video, etc.). The input system 100 passes the audio and video streams to the streams manager 94. Upon a decision by the user to capture the audio or video streams, the streams manager 94 stores the desired clip in the storage 34.

[0040] The UI 32 is coupled to receive the video received by the input system 100 from the video input. During capture of the video, the UI 32 presents the live video so that the viewer can see what clip is being captured.

[0041] Audio/Video Capture UI

[0042] FIG. 5 shows an email page 110 rendered by the browser UI 32. The email page 110 is accessed and displayed by selecting an appropriate hypertext link on a home page. The email page 110 includes a logo 112, a workspace 114, and multiple links 116-122. The workspace 114 has a text area 124, with “From”, “To”, and “Subject” lines, and a “Send” button 126. The user can enter a new mail message using this screen.

[0043] Link 116 is a hypertext link to a mail list that lists incoming mail messages chronologically. Link 118 is a hypertext link to a list of addresses that the user might wish to select an intended recipient. Links 120 and 122 are used to facilitate audio and video capture for inclusion of an audio or sound clip in the email message. Actuation of link 120 brings up an audio capture panel that provides UI functions to enable a user to capture an audio stream input into the microphone. Actuation of link 122 brings up a video capture panel that provides UI functions to enable a user to capture a video stream from the video input or from the television signal.

[0044] FIG. 6 shows the audio capture panel 130 overlaid on the email page 110 in response to activation of “Recording” link 120. The audio capture panel 130 has a switch 132 that allows the user to capture audio signals from either the TV feed or from the microphone input 78. When a valid audio signal is present, an audio waveform (real or picture) appears in box 134. The user can capture an audio clip by pressing a “Record” button 136.

[0045] In response to activating the “Record” button 136, the browser records and processes the audio in such a way to significantly reduce the amount of audio data stored at the set-top box for a given duration. The browser receives an audio signal from the TV feed of microphone input 78. The audio signal is sampled at a high sampling rate in stereo. As an example, the signal might be sampled at 44.1 kHz in 16-bit stereo. The browser software initially converts the audio signal from stereo to monophonic and then resamples the signal at a lower sampling rate with appropriate anti-alias filtering and decimation to maintain audio quality. For example, the audio signal is resampled at 8 kHz mono with 4 bits per sample. Converting to monophonic and decreasing the sampling rate substantially compress the amount of audio data needed to represent the audio signal.

[0046] The converted audio signal is then compressed using adaptive differential pulse code modulation (ADPCM) and stored in the standard WAV format. These processes reduce the size and transmission time and allow email recipients to play the sound with a standard audio playback application.

[0047] The sound compression is performed in real time so that full high resolution sound need not be stored in the limited memory of the set-top box. By reducing the amount of data to be stored per time segment, longer audio clips can be captured. The technique described above increases the duration of the compressed audio clip by over 40 times as compared to an uncompressed audio clip.

[0048] After the user collects a desired sound clip, the user clicks the “Add to Message” button 138 to add the audio clip to the bottom of the mail message. The STB stores the audio clip as a WAV file in the storage 34 in response to activation of the “Add to Message” button 138.

[0049] FIG. 7 shows the video capture panel 150 overlaid on the email page 110 in response to activation of the “Photo” link 122. The video capture panel 150 has a switch 152 that allows the user to capture video streams from either the TV or from the video input 80. When a valid video signal is present, the video stream appears in box 154. The user can capture a video clip by pressing a “Freeze” button 156, which causes a still image to appear in the box 154. Choosing the “Freeze” button 156 again restarts the video stream in the box 154 to enable the user to capture a different clip in the video stream.

[0050] In response to activating the “Freeze” button 156, the browser copies an image from the video input buffer. In one implementation, the browser copies one field from each frame (e.g., the odd lines in an interlaced frame), thereby omitting one-half of the data in the video frame. This process eliminates artifacts caused by motion in the video and reduces the amount of data to be stored for a given image.

[0051] The set-top box then resizes the image to a smaller a smaller size appropriate for display as part of email UI. The resizing uses anti-aliased scaling to maintain a high quality image. After it is resized, it is compressed with JPEG compression, a standard compression format for photographs. These two steps significantly decrease the size of the data that needs to be transmitted, and easily allow the email recipients to display the photograph.

[0052] In the case of a video clip involving multiple frames (as opposed to a single still image frame), the set-top box performs essentially the same steps above, but initially captures a reduced number of frames from the streaming video. For example, if the video input is at 60 frames/sec, the set-top box might capture one-fourth of the frames, or 15 frames/sec, to reduce the amount of data to be included in the email message. After resizing, the reduced-size video clip is compressed using MPEG, a standard compression format for video.

[0053] The user then adds the video clip to the email message by clicking the “Add to Message” button 158. The STB stores the video clip locally in the storage 34 in response to activation of the “Add to Message” button 158.

[0054] FIG. 8 shows a new email page 170 with the audio/video clip 172 attached to the bottom of the email message. The email page 170 has a “Remove” button 174 that allows the user the option of removing the audio/video clip 172.

[0055] Audio/Video Capture Operation

[0056] FIGS. 9 and 10 show steps in a method for capturing audio or video signals for inclusion in an email message. The steps are performed by computer-executable instructions stored in memory at the set-top box and the host mail service. Alternatively, the steps might be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

[0057] At step 200, the user activates the link to the email page 110. In response, the browser sends a request over to the host email service 36, which generates and serves the email page 110 (step 202). The page is written in markup language, such as HTML. The browser renders the email page 110 as illustrated in FIG. 5 (step 204). At this point, the user can optionally enter text to write an email message.

[0058] At step 206, the user activates either the “Recording” link 120 or the “Photo” link 122. Activation of link 120 causes the audio capture panel 130 to appear over the email page 110, as shown in FIG. 6. Activation of link 122 causes the video capture panel 150 to appear over the email page 110, as shown in FIG. 7.

[0059] At step 208, the user employs the capture panels 130 or 150 to capture an audio or video clip. The user clicks the “Record” or “Freeze” buttons in the respective panels to record the audio or video clip. These clips are stored in storage 34 (step 210).

[0060] After the user has captured the desired audio or video clip, the user adds the clip to the email message by clicking the “Add to Message” button 138 or 158 in the capture panels (step 212). Activation of the button causes the browser to send a request for new HTML email page that shows both the message and the attached clip. However, rather than sending across the entire video or audio clip, the browser simply inserts a token that is representative of the attached clip. The token may include such information as the name of the audio or video file, the size of the video image, and so forth. This results in a substantial savings in transmission time as the large size audio or video files are not needlessly transferred over to the host mail server merely to be transferred back again with the next page.

[0061] At step 214, the host mail service generates a response specifying a new HTML page containing the email message. The response also includes the token and indicates a location in the new page at which the audio or video data is to be rendered. The host mail service returns the response to the client.

[0062] At step 216, the browser extracts the token and retrieves the audio or video file referenced by the token from the storage 34. The browser inserts the image or sound bite at the indicated location in the HTML email page. The browser then renders the HTML email page with the image or sound bite shown attached to the bottom (step 218).

[0063] Although the addition of an audio or video clip involves a round trip request/response cycle with the host mail service, this process is hidden to the user. That is, to the user, the UI experience simply involves capturing the audio/video clip and hitting the “Add to Message” button. A new screen appears rapidly with the clip attached to the bottom of the message.

[0064] When the message is complete, the user clicks the “Send” link 126 in the email screen (step 220 in FIG. 10). In response, the browser sends the text and audio/video file over to the host mail service using a conventional POST command of HTTP. The host mail service converts the text and audio/video files to a MIME message (step 222 in FIG. 10), and forwards the MIME message to the intended recipient (step 224 in FIG. 10). The intended recipient can then render the MIME message using a browser to read and see or listen to the attached clip.

[0065] Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.

Claims

1. In a browser-based email system having a client and a host mail server, the client having a browser, the host mail server providing pages that present an email service to a user when the pages are rendered by the browser, a method for adding audio or video data to an email message comprising the following steps: rendering, at the client, a page for entering an email message; presenting, at the client, a user interface to capture audio or video data to be included as part of the email message; in response to a user command to add the audio or video data to the email message, submitting a request from the client to the host mail server, the request containing a token in lieu of the audio or video data; returning a response from the host mail server to the client, the response specifying a new page that contains the email message, the response including the token and indicating a location in the new page at which the audio or video data is to be rendered; inserting, at the client, the audio or video data at the location in the new page; and rendering, at the client, the new page.

2. A method as recited in claim 1, further comprising the following steps: storing, at the client, the audio or video data captured using the user interface; and retrieving, at the client, the audio or video data represented by the token when the response is received from the host mail server.

3. A method as recited in claim 1, further comprising the step of submitting, in response to a user command to send the email message, a request containing the email message and the audio or video data from the client to the host mail server.

4. A method as recited in claim 3, further comprising the step of converting, at the host mail server, the email message and the audio or video data to a MIME message.

5. In a browser-based email system, a method for capturing audio or video data for inclusion in an email message comprising the following steps: receiving a first page for entering an email message; rendering the first page; presenting a user interface having at least one control that enables recordation of the audio or video data and inclusion of the audio or video data in the email message; and upon actuation of the control in the user interface, submitting a request to a host mail server for a second page that contains the email message with the audio or video data included therein.

6. A method as recited in claim 5, further comprising the following steps: receiving a response specifying a new page that contains the email message and the audio or video data; and rendering the new page.

7. A method as recited in claim 5, wherein the request contains a token in lieu of the audio or video data.

8. A method as recited in claim 7, farther comprising the following steps: receiving a response specifying a new page that contains the email message, the response including the token and indicating a location in the new page at which the audio or video data is to be rendered; and rendering the new page.

9. A browser-based email system comprising: a thin client having a browser; a host mail server to serve pages to the thin client, which can be rendered by the browser to present an email service to a user; the thin client having a user interface to enable capture of a data stream for inclusion in an email message; whereupon capture of the data stream, the browser submits a request to the host mail server that contains a token in lieu of the data stream; whereupon receipt of the request, the host mail server returns a response specifying a new page that contains the email message, the response including the token and indicating a location in the new page at which the audio or video data is to be rendered; and whereupon receipt of the response, the browser inserts the data stream into the new page at the location and renders the new page.

10. A browser-based email system as recited in claim 9, wherein the client stores the data stream locally-and retrieves the data stream when the token is returned from the host mail server.

11. A browser-based email system as recited in claim 9, wherein the client is embodied as a set-top box.

12. A browser-based email system as recited in claim 9, wherein the user interface comprises capture panel having a display box indicating whether a data stream is being received and at least one control that enables capture of the datastream.

13. A browser-based email system as recited in claim 9, where in response to a user command to send the email message, the browser submits a second request to the host mail server that contains the email message and the audio or video data.

14. A browser-based email system as recited in claim 13, whereupon receipt of the second request, the host mail server converts the email message and the audio or video data to a MIME message and forwards the MIME message to an intended recipient.

15. A thin client comprising: a processor; a memory coupled to the processor; a data input to receive a data stream; a browser program stored in the memory and executable on the processor, the browser rendering pages written in a markup language to present an email interface for reading and writing email messages; and a user interface stored in the memory and executable on the processor to enable capture of the data stream received at the data input for inclusion in an email message.

16. A thin client as recited in claim 15, wherein upon a user command to add the data stream to the email message, the browser submits a request to a host mail server for a second page that contains the email message with the data stream included therein.

17. A thin client as recited in claim 16, wherein the browser receives a response specifying a new page that contains the email message and indicating a location in the second page at which the data stream is to be rendered.

18. A thin client as recited in claim 16, embodied as a set-top box.

19. In a browser-based email system having a thin client interconnected to a host mail server, computer-readable media residing at the thin client and the host mail server having computer-executable instructions for performing the following steps: rendering, at the client, a page for entering an email message; presenting, at the client, a user interface to capture audio or video data to be included as part of the email message; in response to a user command to add the audio or video data to the email message, submitting a request from the client to the host mail server, the request containing a token in lieu of the audio or video data; returning a response from the host mail server to the client, the response specifying a new page that contains the email message, the response including the token and indicating a location in the new page at which the audio or video data is to be rendered; inserting, at the client, the audio or video data at the location in the new page; and rendering, at the client, the new page.

20. Computer-readable media as recited in claim 19, further comprising computer-executable instructions for performing the step of submitting, in response to a user command to send the email message, a request containing the email message and the audio or video data from the client to the host mail server.

21. Computer-readable media as recited in claim 20, further comprising computer-executable instructions for performing the step of converting, at the host mail server, the email message and the audio or video data to a MIME message.

22. In a thin client, a user interface executing on the client comprising a primary screen and at least one capture panel that is accessible from the primary screen, the capture panel having at least one control that enables capture of a data stream being input into the client.

23. A user interface as recited in claim 22, wherein the primary screen comprises an email screen and the data stream is captured for inclusion in an email message.