MMB: Scalable Multimedia Messaging Box for Mobile and Wireline Internet Milind M.
Download
Report
Transcript MMB: Scalable Multimedia Messaging Box for Mobile and Wireline Internet Milind M.
MMB: Scalable Multimedia Messaging Box
for Mobile and Wireline Internet
Milind M. Buddhikot
[email protected]
Department of High Speed Mobile Data
Lucent Bell Labs
Sumi Choi, Scott Miller
([email protected], [email protected])
8/30/2001
Milind M. Buddhikot
1
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
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
IMAP
Server
sendmail
A’s
inbox
bronx.dnrc.bell-labs.com
Messages:
sendmail
smtp.aol.com
B’s
Outlook
• 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)
8/30/2001
Milind Buddhikot
3
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
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.
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.
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
MediaClip
1
Wireless Access
+ Core Network
MediaHandle
‘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,…>
8/30/2001
Milind Buddhikot
6
STEP 2:’A’ Sends ‘B’ a Video Message
A’s
Outlook
Find B’s inbox on
Att.net network
And deliver handle
Using SMTP/TCP/IP
sendmail
Media
Handle
[email protected]
A’s
inbox
IMAP
Server
Media
Handle
A’s Record
GUI
A’s
Outbox
Outbox
Server
MediaClip
Wireless Access
+ Core Network
MediaHandle
sendmail
IMAP
Server
Notice, ‘A’ sent ‘B’ the
MediaHandle, not the
MediaClip
8/30/2001
Outbox
Server
Milind Buddhikot
points2
att.net
Media
Handle
B’s
inbox
B’s
Outbox
7
STEP3: ‘B’ Gets the MediaHandle
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
MediaClip
Wireless Access
+ Core Network
MediaHandle
att.net
sendmail
Media
Handle
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
Before clip is played back ‘B’
may have to be authenticated
by A’s Outbox server!
sendmail
IMAP
Server
RTSP
RTSP Control Connection
for FF/RW, Pause, Stop,
Random Search,
Outbox
Server
A’s
inbox
A’s
Outbox
MediaClip
Wireless Access
+ Core Network
RTP
MediaHandle
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 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
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
Handle
Server
A’s
HandleBox
Media/Msg
Server
A’s
MediaBox
MediaHandle
Media clip1
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
8/30/2001
Milind Buddhikot
11
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 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
C1000
Mailboxes
MMB box supports legacy inbox and new outboxes
MMB box supports
•
•
•
•
•
•
8/30/2001
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
Milind Buddhikot
14
Scalability of MMB
MailBoxBricks
• Client inbox, Client HandleBox
MediaBox
Brick0
MailBoX
Brick
MediaBox
Brick 1
MailBoX
Brick
MailBoX
Brick
MediaBoxBricks
• Store media files of clients
Concept of Virtual Outbox
• Each user is assigned to one
Ether
Switch
•
MediaBox
Brick
(N-1)
MailBoxBrick
Multiple MediaBoxBricks form
distributed storage for multimedia
files
MailBoxBrick maintains
“virtual outbox map”
• which media belong to which
•
8/30/2001
Milind Buddhikot
messages
which messages belong to which
user
15
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
16
MailBox Brick Implementation
SMTP/TCP/IP
IMAP/TCP/IP
inboxes
sendmail
IMAP
Server
IMAP/TCP/IP
• SendmailD, IMAPd
• HandleD
• Media Access Interface
Handleboxes
JAVAMAIL
Handle
Server
To adptation
server
8/30/2001
TomCat
WebServer
HTTP
Servlet
Handle server
• Interfaces Handleboxes
•
HTTP/TCP/IP
Single Linux box with
(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
Milind Buddhikot
17
Media Brick Implementation
• Media storage
• Media provider
• Gamma content adaptation server
TCP/IP
ftpd
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)
Media provider
• Plays back a media when requested
Streaming through Darwin
Directly from TomCat
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
• Outbox
• KNIEF client
inboxes
modifications
Handleboxes
JAVAMAIL
KNIFE
Win98
Sony
Picturebook
W/ Camera
To HandleD,
ftpd
WinCE
HandleD
ftpd
HTTP
Servlet
soho.dnrc
Profile
Server
(Tomcat)
TomCat
WebServer
Developed
Three clients
• Laptop
• Picturebook
• PDA
Darwin
Milind
Media
boxes
TomCat
WebServer
PocketPC
Salim
8/30/2001
Gamma
Content
Adaptation
Server
sau.dnrc
(media brick)
Milind Buddhikot
19
Sequence of Demo
Steps
Video messaging
1.
2.
3.
4.
5.
6.
7.
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
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
22
Virtual Outbox Map
MediaBox
Brick0
MailBox
Brick 10
Client 2
Client M
CM
m1 Brick4
C2
m1 Brick4
Scott
C1
m1 Brick4
m2 Brick8
m2 Brick5
m2 Brick0
mk Brickj
mk Bricki
mk Brick6
MediaBox
Brick4
MediaBox
Brick 6
Media Store
MediaBox
Brick
(N-1)
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
8/30/2001
Milind Buddhikot
23