MMB Scalable Multimedia Messaging Box for Mobile and

MMB: Scalable Multimedia Messaging Box for Mobile and Wireline Internet Milind M. Buddhikot mbuddhikot@bell-labs. com Department of High Speed Mobile Data Lucent Bell Labs Sumi Choi, Scott Miller (syc@arl. wustl. edu, scm@lucent. com) 8/30/2001 Milind M. Buddhikot 1

Outline Traditional messaging q Multimedia messaging q • New ideas: Concept of “media handles” and “media outbox” • Integration of profile driven Content Adaptation q Multimedia Messaging Box(MMB) architecture • Software components • Scalable cluster implementations q Demo 8/30/2001 Milind Buddhikot 2

Traditional Mail Messaging Model chair. lucent. com A’s Outlook SMTP/TCP/IP sendmail smtp. sprint. com smtp. service. com SMTP/TCP/IP sendmail Msg delivery IMAP/TCP/IP Msg viewing q Messages: IMAP Server sendmail A’s inbox bronx. dnrc. bell-labs. com sendmail smtp. aol. com B’s Outlook • Legacy: Documents (text, html, MSWord) and images. • New: Audio/video (Ex: MP 3 music files, group meetings ) Store-and-forward used for message routing/delivery q Inbox maintains delivered msgs for ‘A’ on bronx. dnrc q POP 3/IMAP allows ‘A’ to access the Inbox q Mail client (eg. outlook) for interfacing inbox via POP 3/IMAP q Messages stored in receiver A’s inbox q Messages come to the receiver (A) 8/30/2001 Milind Buddhikot 3

Drawbacks q Store-and-forward inappropriate for audio/video messages • Large video messages replicated many times q Enforcing explicit content ownership is difficult • Messages replicated by mail servers/receivers q Enforcing content access permissions difficult • Messages replicated/forwarded easily by receivers Solution: Concept of outbox and limited access to outbox q Lack of support for diverse access methods, devices • Clients (PC, Laptops, Pocket PC, PDA, cell phones) • Networks (wireless/wireline) Solution: Content Adaptation Service 8/30/2001 Milind Buddhikot 4

New Video Messaging Model A’s Outlook SMTP/TCP/IP sendmail IMAP/TCP/IP IMAP Server Outbox Server A’s inbox A’s Outbox Bronx. dnrc. bell-labs. com outbox. dnrc. bell-labs. com Key Concept: receiving party comes to the media. q Video clips sit in the sender A’s outbox on outbox. dnrc q People who get a message connect to the A’s outbox and view the video! q Key difference: now there is an inbox that only ‘A‘ sees and an outbox that he can let others see. q 8/30/2001 Milind Buddhikot 5

STEP 1: ‘A’ Records a message sendmail IMAP Server Media Handle A’s Record GUI Outbox Server A’s inbox A’s Outbox 2 Bronx. dnrc. bell-labs. com outbox. dnrc. belllabs. com Media. Clip 1 q Wireless Access + Core Network Media. Handle ‘A’ records/uploads Media. Clip and gets back a Media. Handle that describes the clip • Media. Handle contains <id, creator, created date, location, media type, expiry date, policies, …> 8/30/2001 Milind Buddhikot 6

STEP 2: ’A’ Sends ‘B’ a Video Message A’s Outlook Find B’s inbox on Att. network And deliver handle Using SMTP/TCP/IP sendmail Media Handle B@att. net A’s inbox IMAP Server Media Handle A’s Record GUI A’s Outbox Server Media. Clip Wireless Access + Core Network Media. Handle sendmail q IMAP Server Notice, ‘A’ sent ‘B’ the Media. Handle, not the Media. Clip 8/30/2001 Outbox Server Milind Buddhikot points 2 att. net Media Handle B’s inbox B’s Outbox 7

STEP 3: ‘B’ Gets the Media. Handle q B’s Outlook B’s outlook ran the playback GUI and gives it the handle sendmail IMAP Server Media Handle Outbox Server A’s inbox A’s Outbox Media. Clip Wireless Access + Core Network Media Handle Media. Handle att. net sendmail IMAP Server Outbox Server 8/30/2001 Milind Buddhikot Media Handle B’s inbox B’s Outbox 8

STEP 4: ‘B’ Watches the Video Message q Before clip is played back ‘B’ may have to be authenticated by A’s Outbox server! sendmail IMAP Server RTSP Control Connection for FF/RW, Pause, Stop, Random Search, Outbox Server A’s inbox A’s Outbox Media. Clip Wireless Access + Core Network RTP Media. Handle Media Handle Data Connection RTP used for the media data 8/30/2001 Milind Buddhikot 9

Adding Content Adaptation ‘A’ has recorded his video clip in 1. 5 Mbps MPEG 2 format with 640 x 480 CIF resolution q ‘B’ only has a PDA capable of playing H. 263 video from a wireless connection of 144 Kbps q à Content adaptation adapts A’s video clip for B’s need. (MPEG 2, 640 x 480 (CIF), 1. 5 Mbps) (H. 263, 160 x 20 (QCIF), 144 Kbps) à Outbox server must support content conversions • MPEG 1, 2, 4, AVI, REAL, H. 263, CMF for video • MP 3, Wave, AVI, MPEG, Real for audio 8/30/2001 Milind Buddhikot of 10

Seeking Scalability: Splitting the Outbox SMTP/TCP/IP IMAP/TCP/IP sendmail IMAP Server A’s inbox A’s Mailboxes A’s Outbox IMAP++/TCP/IP RTSP/TCP/IP RTP/UDP/IP q q Handle Server A’s Handle. Box Media/Msg Server A’s Media. Box Media. Handle Media clip 1 A’s outbox split into two (logical or physical) boxes: A’s Handle Box and A’s Media Box Handle. Box stores the handles Media. Box stores the media (a/v) clips Can be implemented on physically different resources thus virtualizing the outbox 8/30/2001 Milind Buddhikot 11

Recap q A’s mailboxes now consist of • Inbox (for regular messages) • Outbox = Handle. Box + Media. Box (for sending multimedia messages) Legacy Inbox • Inbox written to by SMTP server • Inbox read by IMAP/POP 3 server q New Outbox • Handle. Box written and read by Handle. Box Server q Handlebox can be a traditional IMAP folder! • Media. Box written/read by Media. Box Server MMB: Media Message Box 8/30/2001 Milind Buddhikot 12

MMB: Media Message Box 8/30/2001 Milind M. Buddhikot 13

Media Message Box (MMB) Scott’s Mailboxes Katie’s Mailboxes Mobile & Wireline Internet Scott, Katie Tom’s Profile MMB Tom’s Mailboxes AAA and Profile Server C 1000 Mailboxes MMB box supports legacy inbox and new outboxes q MMB box supports q • • • 8/30/2001 SMTP forwarding (sendmaild) IMAP/POP access (to legacy Inbox) Interfaces for creating and managing handles (in Handle. Box) Upload and Streaming Recording (to Media. Box) Content adaptation server and Profile server Media access from message receivers Milind Buddhikot 14

Scalability of MMB q Mail. Box. Bricks • Client inbox, Client Handle. Box Media. Box Brick 0 Mail. Bo. X Brick Media. Box Brick 1 Mail. Bo. X Brick q Media. Box. Bricks • Store media files of clients q Concept of Virtual Outbox • Each user is assigned to one Ether Switch • Media. Box Brick (N-1) q Mail. Box. Brick Multiple Media. Box. Bricks form distributed storage for multimedia files Mail. Box. Brick maintains “virtual outbox map” • which media belong to which • 8/30/2001 Milind Buddhikot messages which messages belong to which user 15

Advantages q Scalability • Adding New bricks on the fly when more space is needed. • Transcoding of each clip done locally at each Media. Box. Brick Ø Parallelism in transcoding q Fault tolerance and Load-balance • Controlled message replication 8/30/2001 Milind Buddhikot 16

Mail. Box Brick Implementation SMTP/TCP/IP IMAP/TCP/IP q sendmail IMAP Server JAVAMAIL IMAP/TCP/IP inboxes Handleboxes • Sendmail. D, IMAPd • Handle. D • Media Access Interface q Handle Server To adptation server 8/30/2001 Tom. Cat Web. Server HTTP Servlet Handle server • Interfaces Handleboxes (implemented • q HTTP/TCP/IP Single Linux box with as a IMAP folder) Allocates, deallocates handles Media Access Interface • Servlets on Tom. Cat provide web • • based media access from receivers Authenticates users Interfaces Gamma content adaptation server Milind Buddhikot 17

Media Brick Implementation q • Media storage • Media provider • Gamma content adaptation server TCP/IP ftpd q RTSP/TCP/IP Media storage • Multimedia messages are stored Darwin RTP/UDP/IP Gamma Content Adaptation Server Linux box with Media boxes Ø ftp upload Ø Streaming recording (not implemented) q Media provider • Plays back a media when requested Ø Streaming through Darwin Ø Directly from Tom. Cat q Content adaptation • Gamma content adaptation server • transforms when required 8/30/2001 Milind Buddhikot 18

Demo Setup deity. dnrc (mail, media brick) Email Client Sumi Sony Laptop sendmail IMAP Server q • Outbox • KNIEF client inboxes modifications Handleboxes JAVAMAIL KNIFE Win 98 Sony Picturebook W/ Camera To Handle. D, ftpd Win. CE q Handle. D ftpd HTTP Servlet soho. dnrc Profile Server (Tomcat) Tom. Cat Web. Server Developed Three clients • Laptop • Picturebook • PDA Darwin Milind Media boxes Tom. Cat Web. Server Pocket. PC Salim 8/30/2001 Gamma Content Adaptation Server sau. dnrc (media brick) Milind Buddhikot 19

Sequence of Demo Steps q Video messaging 1. 2. 3. 4. 5. 6. 7. q Create a handle with a MPEG movie file Send the handle to a group of people (Sumi, Milind, and Salim) Sumi receives the handle from a Laptop and access the media Milind from a Picuturebook Salim from a PDA A handle appears on the inbox of each. Retrieve and display the movie from the outbox Other media format 1. Create a handle with a powerpoint file (treated as another type of media) 2. Send it to a receiver 3. Adapted content shown on the receiver’s device 8/30/2001 Milind Buddhikot 20

Summary and Conclusions 8/30/2001 Milind M. Buddhikot 21

Summary and Conclusions q A scalable Multimedia Messaging platform • important component of 3 G wireless and other networks q Our Contributions: • • • Idea of Media Handles and Handleboxes Scalable Virtual outbox Integration of Gamma transcoding support for content adaptation Software Implementation on Linux platform utilizing existing software Integration with other services possible Ø SMSC, Billing (in progress) 8/30/2001 Milind Buddhikot 22

Virtual Outbox Map Media. Box Brick 0 Mail. Box Brick 10 Client 2 Client M CM q q m 1 Brick 4 C 2 m 1 Brick 4 Scott C 1 m 1 Brick 4 m 2 Brick 8 m 2 Brick 5 m 2 Brick 0 mk Brickj mk Bricki mk Brick 6 Media. Box Brick 4 Media. Box Brick 6 Media Store Media. Box Brick (N-1) Ex: <C 1 , C 2 …. CM> are clients served by MMB Client C 1 Scott’s Virtual Outbox == (Mail. Box. Brick 10, Media. Box. Brick 0, 4, 6) • assigned Scott’s (inbox, Handle. Box) on Mail. Box. Brick 10 Scott has video messages < m 1, m 2, …. mk>. Handle. Box server (handle. D) on Mail. Box. Brick 10 assigns these messages to different Media. Box. Bricks 0, 4, 6 creating distributed Media. Box for C 1 (Scott) • m 1 to 6, m 2 to 0, mk to 4 etc. • Message atomically stored at a brick Ø No striping of messages 8/30/2001 Milind Buddhikot 23