1. SIP and MMS Jonathan Rosenberg Chief Scientist

2. SIP 2003 2 What Is It? European Technology for Enhanced Messaging Specified by 3GPP, WAP Forum Different from SMS No SS7 Uses many IETF technologies MIME SMTP

3. SIP 2003 3 What Are The Features? Messaging Using Multimedia Content Required content types Text Audio (AMR) Still Image (JPEG) Video (H.263) Optional content types Audio: MP3, MIDI, AAC Image: GIF MSISDN (Phone Number) or Email Addressing Delivery Timing Delayed delivery Expiration Anonymous Sending Confirmations Delivery confirmation Recipient suppression Read confirmation Recipient Controls Notification is sent when message arrives User can reject the message, forward the message or read the message Streaming Delivery Prepaid Reply-Charging Subject, Priority, Class for Messages

4. SIP 2003 4 Network Architecture MM3... MM1 MM4 MM6 MM5 MM7 External Server #1 (e.g. email) External Server #2 (e.g. Fax) External Server #3 (e.g. UMS) External Server #N MM3 MMS VAS Applications MMS Relay/Server Relay Server MM2 “Foreign” MMS Relay/Server MMS User Agent A MMS User Agent B MMS User Databases HLR

5. SIP 2003 5 What Are The Problems? Problems for Users No way to know if intended recipient has MMS No way to know if intended recipient has their phone on No way to know if intended recipient supports the media type to be sent No way to know if intended recipient wants to receive an MMS of a specific size and type Problems for Operators Duplication of registration and user management between SIP and MMS (WAP)

6. SIP 2003 6 Solution: SIP! SIP for Presence Solves the User-level Problems With MMS Presence State Can Include an “MMS Tuple” Which Indicates Whether recipient supports MMS What media types they support Whether they want to receive an MMS now or not Size limits The Sender Uses a Presence Client (i.e., Buddy List) and Can See Their MMS Presence Selecting a Buddy Allows Options for Sending an IM Sending an SMS Sending an MMS (if presence indicates it’s possible)

7. SIP 2003 7 Presence Document for MMS IETF Presence Information Document Format (PIDF) Easily Extended to Handle MMS XML Namespace Can Be Used for MMS <impp:presence xmlns:impp="urn:ietf:params:xml:ns:cpim-pidf“ xlmns:mms=“urn:ietf:params:xml:ns:cpim-mms” entity="pres:someone@example.com"> open true video/h263 image/tiff 10000 tel:09012345678 Several New Tags Defined mms-capable media-type max-size

8. SIP 2003 8 Alternative Solutions Segmented Architecture Clients support SIMPLE and MMS Total separation of SIP and WAP/MMS in the network Receiver MMS-Only Architecture Sender supports SIMPLE and MMS Receiver only supports MMS WAP gateway provides presence information to SIP presence server UAProf documents WAP push OTA registrations Receiver Integrated Architecture Uses SIP for the MM1 interface

9. SIP 2003 9 Segmented Architecture WAP Gateway WAP HTTP SMTP PAP Push OTA SIP Sender Domain Recipient Domain MMSC SIP Proxy MMSC SIP Proxy Presence Server PPG

10. SIP 2003 10 Receiver MMS-Only Architecture WAP Gateway PPG WAP HTTP SMTP PAP Push OTA SIP Sender Domain Recipient Domain SIP MMSC SIP Proxy MMSC SIP Proxy Presence Server

11. SIP 2003 11 Pros/Cons SegmentedReceiver MMS-Only + No Client Changes – Client Changes on Both Sides + Receiver Can Easily Control the Presence Status – Requires Both SIP and MMS Registration Procedures – WAP Gateway Changes +/ – Client Changes on One Side – Receiver Can’t Easily Control Presence Status +/ – Requires Only MMS Registration Procedures

12. SIP 2003 12 A Third Solution: SIP-Based MM1 MM1 Interface Is Between the Device and the MMSC Includes both client-server transactions (fetch content, delivery status notifications) Includes push transactions Push Mechanisms Require Registration, Authentication Functions These are also provided by SIP Idea: Use a Single Unified Registration/authentication Mechanism SIP REGISTER Deliver MMS Messages in the Content of a MESSAGE Request Towards the Handset Client/server Pull Still Uses WAP/HTTP SIP Message Request( M-Notification.ind) MMS UA MM1_notification.REQ MM1_retrieve.REQ MM1_retrieve.RES MM1_notification.RES MMS Relay /Server SIP Message Response SIP Message Request( M-NotifyResp.ind) SIP Message Response

13. SIP 2003 13 SIP-Based MM1 Architecture WAP Gateway WAP HTTP SMTP SIP Sender Domain Recipient Domain WAP Pull SIP MMSC SIP Proxy MMSC SIP Proxy Presence Server

14. SIP 2003 14 Benefits of this Model Single Unified Registration Model Used for MMS, SIP SIP-enabled Client Can Properly Set Presence Status for Receiving MMS PUBLISH request Helps Unify IM and MMS IM and MMS notifications both carried in MESSAGE requests Single unified inboxes, message logs, histories, blocking features can be applied Still Requires Clients to Support Both MMS and SIP, but WAP Push Capabilities Are Not Required No Changes Required to WAP Gateway, but Does Require MMSC Changes Standards-based 3GPP2 Has Agreed to Standardize the Usage of SIP for MM1

15. SIP 2003 15 Conclusion SIP Can Greatly Enhance MMS Presence Can Benefit the Overall User Experience Using SIP MESSAGE for MMS Delivery Can Help Unify MMS and IM

16. Information Resource Jonathan Rosenberg Chief Scientist +1 973.952.5000 jdrosen@dynamicsoft.com