Date post: | 23-Dec-2015 |
Category: |
Documents |
Upload: | rosaline-holmes |
View: | 214 times |
Download: | 0 times |
8/30/2001 Milind M. Buddhikot 1
MMB: Scalable Multimedia Messaging Boxfor Mobile and Wireline Internet
Milind M. Buddhikot
[email protected] of High Speed Mobile Data
Lucent Bell Labs
Sumi Choi, Scott Miller
8/30/2001 Milind Buddhikot 2
Outline
Traditional messaging Multimedia messaging
• New ideas: Concept of “media handles” and “media outbox”
• Integration of profile driven Content Adaptation
Multimedia Messaging Box(MMB) architecture• Software components
• Scalable cluster implementations
Demo
8/30/2001 Milind Buddhikot 3
Traditional Mail Messaging Model
Messages: • Legacy: Documents (text, html, MSWord) and images.• New: Audio/video (Ex: MP3 music files, group meetings )
Store-and-forward used for message routing/delivery Inbox maintains delivered msgs for ‘A’ on bronx.dnrc POP3/IMAP allows ‘A’ to access the Inbox Mail client (eg. outlook) for interfacing inbox via POP3/IMAP Messages stored in receiver A’s inbox
Messages come to the receiver (A)
bronx.dnrc.bell-labs.com
A’sinbox
IMAPServer
sendmail
IMAP/TCP/IP
SMTP/TCP/IP
Msg delivery
Msg viewing
A’s Outlook
sendmailSMTP/TCP/IP sendmail
sendmail
smtp.aol.com
chair.lucent.com smtp.sprint.comsmtp.service.com
B’s Outlook
8/30/2001 Milind Buddhikot 4
Drawbacks
Store-and-forward inappropriate for audio/video messages• Large video messages replicated many times
Enforcing explicit content ownership is difficult• Messages replicated by mail servers/receivers
Enforcing content access permissions difficult• Messages replicated/forwarded easily by receivers
Solution:
Concept of outbox and limited access to outbox 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 5
New Video Messaging Model
Key Concept: receiving party comes to the media. Video clips sit in the sender A’s outbox on outbox.dnrc
People who get a message connect to the A’s outbox and view the video!
Key difference: now there is an inbox that only ‘A‘ sees and an outbox that he can let others see.
A’sOutbox outbox.dnrc.bell-
labs.com
Bronx.dnrc.bell-labs.comA’s
inboxIMAP
Server
sendmail
IMAP/TCP/IP
SMTP/TCP/IP
OutboxServer
A’sOutlook
8/30/2001 Milind Buddhikot 6
A’sOutbox
A’sinbox
IMAPServer
sendmail
OutboxServer outbox.dnrc.bell-
labs.com
Bronx.dnrc.bell-labs.com
STEP 1: ‘A’ Records a message
‘A’ records/uploads MediaClip and gets back a MediaHandle that describes the clip
• MediaHandle contains <id, creator, created date, location, media type, expiry date, policies,…>
Wireless Access+ Core Network
A’s Record GUI
1
2
MediaHandle
MediaClip
MediaHandle
8/30/2001 Milind Buddhikot 7
STEP 2:’A’ Sends ‘B’ a Video Message
Notice, ‘A’ sent ‘B’ the MediaHandle, not the MediaClip
A’sOutlook
B’sOutbox
B’sinbox
IMAPServer
sendmail
OutboxServer
att.netMediaHandle
A’sOutbox
A’sinbox
IMAPServer
sendmail
OutboxServer
MediaClip
MediaHandle
MediaHandle
Wireless Access+ Core Network
A’s Record GUI
MediaHandle
Find B’s inbox onAtt.net networkAnd deliver handleUsing SMTP/TCP/IP
points2
8/30/2001 Milind Buddhikot 8
STEP3: ‘B’ Gets the MediaHandle
B’s outlook ran the playback GUI and gives it the handle
MediaHandle
MediaHandle
Wireless Access+ Core Network
B’sOutlook
A’sOutbox
A’sinbox
IMAPServer
sendmail
OutboxServer
MediaClip
MediaHandle
B’sOutbox
B’sinbox
IMAPServer
sendmail
OutboxServer
att.netMediaHandle
8/30/2001 Milind Buddhikot 9
Wireless Access+ Core Network
STEP 4: ‘B’ Watches the Video Message
Before clip is played back ‘B’ may have to be authenticated by A’s Outbox server!
MediaHandle
A’sOutbox
A’sinbox
IMAPServer
sendmail
OutboxServer
MediaClip
MediaHandleRTP
RTSP
Data Connection
RTSP Control Connection
for FF/RW, Pause, Stop, Random Search,
RTP used for the media data
8/30/2001 Milind Buddhikot 10
Adding Content Adaptation
‘A’ has recorded his video clip in 1.5 Mbps MPEG2 format with 640 x 480 CIF resolution
‘B’ only has a PDA capable of playing H.263 video from a wireless connection of 144 Kbps
Content adaptation adapts A’s video clip for B’s need.(MPEG2, 640x480 (CIF), 1.5 Mbps) (H.263, 160x20 (QCIF), 144 Kbps)
Outbox server must support content conversions of • MPEG1,2,4, AVI, REAL, H.263, CMF for video
• MP3, Wave, AVI, MPEG, Real for audio
8/30/2001 Milind Buddhikot 11
Seeking Scalability: Splitting the Outbox
A’s outbox split into two (logical or physical) boxes: A’s Handle Box and A’s Media Box
HandleBox stores the handles MediaBox stores the media (a/v) clips Can be implemented on physically different resources thus virtualizing
the outbox
A’sinbox
IMAPServer
sendmail
Media clip1
MediaHandle
A’sMediaBox
A’sHandleBox
Media/MsgServer
HandleServer
A’s Mailboxes
SMTP/TCP/IP
IMAP/TCP/IP
IMAP++/TCP/IP
RTSP/TCP/IP
RTP/UDP/IP
A’s Outbox
8/30/2001 Milind Buddhikot 12
Recap
A’s mailboxes now consist of• Inbox (for regular messages)
• Outbox = HandleBox + MediaBox(for sending multimedia messages)
Legacy Inbox• Inbox written to by SMTP server
• Inbox read by IMAP/POP3 server
New Outbox• HandleBox written and read by HandleBox Server
Handlebox can be a traditional IMAP folder!
• MediaBox written/read by MediaBox Server
MMB: Media Message Box
8/30/2001 Milind M. Buddhikot 13
MMB: Media Message Box
8/30/2001 Milind Buddhikot 14
Media Message Box (MMB)
MMB box supports legacy inbox and new outboxes MMB box supports
• SMTP forwarding (sendmaild)• IMAP/POP access (to legacy Inbox)• Interfaces for creating and managing handles (in HandleBox)• Upload and Streaming Recording (to MediaBox)• Content adaptation server and Profile server• Media access from message receivers
MMB
Scott’sMailboxes
Katie’sMailboxes
Tom’sMailboxes
C1000
Mailboxes
Mobile& WirelineInternet
AAA andProfileServer
Scott, KatieTom’s Profile
8/30/2001 Milind Buddhikot 15
Scalability of MMB
MailBoxBricks • Client inbox, Client HandleBox
MediaBoxBricks• Store media files of clients
Concept of Virtual Outbox• Each user is assigned to one
MailBoxBrick
• Multiple MediaBoxBricks form distributed storage for multimedia files
MailBoxBrick maintains “virtual outbox map”• which media belong to which
messages
• which messages belong to which user
EtherSwitch
MediaBoxBrick(N-1)
MediaBoxBrick0
MediaBoxBrick 1
MailBoXBrick
MailBoXBrick
MailBoXBrick
8/30/2001 Milind Buddhikot 16
Advantages
Scalability• Adding New bricks on the fly when more space is needed.
• Transcoding of each clip done locally at each MediaBoxBrick Parallelism in transcoding
Fault tolerance and Load-balance• Controlled message replication
8/30/2001 Milind Buddhikot 17
MailBox Brick Implementation
Single Linux box with • SendmailD, IMAPd
• HandleD
• Media Access Interface
Handle server• Interfaces Handleboxes
(implemented as a IMAP folder)
• Allocates, deallocates handles
Media Access Interface• Servlets on TomCat provide web
based media access from receivers
• Authenticates users
• Interfaces Gamma content adaptation server
To adptation server
SMTP/TCP/IP
IMAP/TCP/IP
IMAP/TCP/IP
HTTP/TCP/IP
IMAPServer
HandleServer
inboxes
Handleboxes
JAVAMAIL
TomCatWebServer
sendmail
HTTPServlet
8/30/2001 Milind Buddhikot 18
Media Brick Implementation
Linux box with• Media storage
• Media provider
• Gamma content adaptation server
Media storage• Multimedia messages are stored
ftp upload Streaming recording (not
implemented)
Media provider• Plays back a media when requested
Streaming through Darwin Directly from TomCat
Content adaptation• Gamma content adaptation server
• transforms when required
Media boxes
GammaContent
AdaptationServer
Darwin
ftpd
TCP/IP
RTSP/TCP/IP
RTP/UDP/IP
8/30/2001 Milind Buddhikot 19
Demo Setup
Developed• Outbox
• KNIEF client modifications
Three clients• Laptop
• Picturebook
• PDA
KNIFE
Email Client
Sony Laptop
SonyPicturebookW/ Camera
WinCE
Win98
PocketPC
To HandleD, ftpd
Sumi
Salim
Milind
Media boxesTomCat
WebServer
GammaContent
AdaptationServer sau.dnrc
(media brick)
ProfileServer
(Tomcat)
IMAPServer
HandleD
inboxes
Handleboxes
JAVAMAIL
TomCatWebServer
sendmail
HTTPServlet
Darwin
ftpd
deity.dnrc (mail, media brick)
soho.dnrc
8/30/2001 Milind Buddhikot 20
Sequence of Demo
Steps Video messaging
1. Create a handle with a MPEG movie file
2. Send the handle to a group of people (Sumi, Milind, and Salim)
3. Sumi receives the handle from a Laptop and access the media
4. Milind from a Picuturebook
5. Salim from a PDA
6. A handle appears on the inbox of each.
7. Retrieve and display the movie from the outbox
Other media format1. 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 M. Buddhikot 21
Summary and Conclusions
8/30/2001 Milind Buddhikot 22
Summary and Conclusions
A scalable Multimedia Messaging platform • important component of 3G wireless and other networks
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 23
MailBoxBrick 10
m1 Brick4
m2 Brick8
mk Brickj
CM
Client M
m1 Brick4
m2 Brick5
mk Bricki
C2
Client 2
Virtual Outbox Map
Ex: <C1 , C2 …. CM> are clients served by MMB Client C1 Scott’s Virtual Outbox == (MailBoxBrick10, MediaBoxBrick0,4,6)
• assigned Scott’s (inbox, HandleBox) on MailBoxBrick10
Scott has video messages < m1, m2, …. mk>. HandleBox server (handleD) on MailBoxBrick10 assigns these messages to
different MediaBoxBricks 0,4,6 creating distributed MediaBox for C1 (Scott)• m1 to 6, m2 to 0, mk to 4 etc.• Message atomically stored at a brick
No striping of messages
MediaBoxBrick(N-1)
MediaBoxBrick0
MediaBoxBrick4
MediaBoxBrick 6
Media Store
m1 Brick4
m2 Brick0
mk Brick6
C1
Scott