1 / 19

MMS Evolution Past, Present , Future

MMS Evolution Past, Present , Future. Jerry Shih. Outline. History of MMS Project Where to Focus on Actions What is the Next Step. Historical Background. High Interests in the Industry Resulting in Parallel Efforts 3GPP Started the MMS Technical Specification Work in R99

salvador-huerta
Download Presentation

MMS Evolution Past, Present , Future

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MMS EvolutionPast, Present , Future Jerry Shih Jerry Shih

  2. Outline • History of MMS Project • Where to Focus on Actions • What is the Next Step Jerry Shih

  3. Historical Background • High Interests in the Industry Resulting in Parallel Efforts • 3GPP Started the MMS Technical Specification Work in R99 • 3GPP Developed the MMS Network Reference Architecture which was Commonly Adopted Among Different Fora • Initially, 7 Reference Points (MM1-MM7) were Identified in the Architecture and were Expanded to 10 In the Latest Release • 3GPP Technical Specifications only Cover MM1, MM4 and MM7 • WAP Forum (WAPF) Worked on Stage 3 of MM1 Reference Point • With OMA Creation, WAPF work was Transferred to OMA • 3GPP2 Started Their MMS Work Based on 3GPP R5 Specs • 3GPP2 Developed Additional MM1 Interface based on SIP and MM3 Interface Based on EMAIL Jerry Shih

  4. The Industry Landscape Jerry Shih

  5. Problems with the Industry The Many Different Fora Working on MMS Created Confusion with the Following Problems: • Waste of Industry Resources • Too Many Meetings to Cover/Follow • Multiple Points for New Work Proposal • Multiple Decision Points for the Industry • Duplication of Similar Effort • Divergence of Functionality • Dangers of Backward and Forward Compatibility • Difficult in Interoperability Practices Hence in Global Roaming • Delay in Product Development Jerry Shih

  6. Converged MMS Efforts • OMA Hosted a MMS Workshop on November 7, 2003 Looking for a Better Way Moving Forward • All Related MMS Fora (Such as OMA, 3GPP, 3GPP2, GSMA, CDG and Individual Companies) were Invited to Present Their Views • Strong Consensus for a Unified MMS Industrial Activity in the Meeting • Recommended to Combine Technology Independent Technical Specifications Development in One Place – OMA • Progress Toward this Converged MMS Specification Development is Slow (many non-technical issues such as IPR and maintenance for existing Specs) • The Starting Point is Post 3GPP R6 (OMA 1.3) Time Frame • OMA MMSG Created the Landing Pad Task Force to Work On Recommendations on how to Move Forward Jerry Shih

  7. OMA (MMS, WAP,IM,Location, Games etc) Core Network 3GPP2 3GPP Radio Access Network 3GPP2 3GPP cdma2000 UMTS/EDGE Future MMS Specs Development Service Enabling Plane Jerry Shih

  8. OMA • Formed in June 2002 • WAP Forum • Location Interoperability Forum (LIF) • SyncML Initiative • MMS-IOP • Wireless Village • Mobile Gaming Interoperability Forum (MGIF) • Mobile Wireless Internet Forum (MWIF) • Goals: • Deliver Technical Specs for Service Enablers to Reduce Industry Implementation Efforts • Ensure Interoperability (device, geographies, service providers, operators, networks, technologies) • Catalyst for the Consolidation of Standards • Provide Value and Benefits to all OMA Members Jerry Shih

  9. OMA MMS 1.1 Summary • Service Enabler Published in July2004 • MMS Enabler 1.1 Contains the Protocol Specifications for MMS Client Communications. • It uses WAP with the Functions of PUT, GET and PUSH • Furthermore it Contains the MMS Conformance Document Version 2.0 (Define the MMS SMIL Presentation Language) • The MMS Conformance Document 2.0 was Established by a Closed Manufacturer Group to Achieve Interoperability. • Main Restrictions to 30 kByte on Message Size and a Selection of Media Formats (AMR, GIF, WBMP) • The Attempt to Ensure Interoperability was not Successful Jerry Shih

  10. OMA MMS 1.2 Objectives • End-to-end Interoperability for mass market Person-to- Person MMS service • Accelerated Commercial Availability (Major Push from GSMA) • Persistent Network Based MM Storage • Security on MM Content (Image Rich, Video) Jerry Shih

  11. Main Elements for Interoperability • Narrow the Scope for End-to-End Interoperability • No Mobile Device will Support all Available Media Types both for Technical and Economic Reasons • Core MM Content Domain Created • MM Content Classes Defined in Core MM Content Domain • Guide the Mobile Device to Compliant with the Interoperability Scope • MM Creation Mode (Restricted, Warning, and Free) • Content Adaptation • Major and Minor Adaptation Development Jerry Shih

  12. New Functionality in MMS 1.2 • Terminal Capability Negotiation • MMBox • Digital Rights Management (DRM) Jerry Shih

  13. OMA MMS 1.3 Objectives • Person-to-Application, Content-to-Person Use Cases • Better Content Protection • Support User Device Evolution • Message Template Application Jerry Shih

  14. Classification of MMS Messaging • Image Messaging -- Multimedia messaging using Image Basic, Image Rich and Megapixel MM content classes which are optimized for person-to-person use cases but also usable for content-to-person use cases • Video Messaging – Multimedia messaging using Video Basic and Video Rich MM content classes which are optimized for person-to-person use cases but also usable for content-to-person and person-to-application use cases • Content Messaging – Multimedia messaging using Content Basic or Content Rich MM content classes which are optimized for person-to-application and content-to-person services but also usable to person-to-person services with assisting techniques. Jerry Shih

  15. Content Messaging • Emphasis on Content Provider Use Cases • MMS Post Card Service • Consumer Headline News Clips • Consumer Webcam • Multiplayer Chess Game • Better Content Protection • Two new MM Content Classes Defined • Content Basic Content Class • Content Rich Content Class • No Content Adaptation is Defined • End-to-End Interoperability is not Defined Jerry Shih

  16. Message Template • Different way to Construct a Multimedia Message • Service Provider Service • Simplify the Composition of Feature-rich MM • Examples: • MMS Originated Postcards • Greeting Cards • Multimedia Stationary • MMS Based Voting Jerry Shih

  17. Summary • OMA MMS 1.3 Service Enabler Introduces: • New Content Messaging (new Content MM Content Domain) • New Message Template Concept • Enhanced Voice Codec for Audio (AAC+) • Enhanced Video (SVG Tiny) • Enriched Image (1600 * 1200) (Megapixel and Content Rich content classes) • Better Content Protection (full DRM) • Sophisticated Presentation (PSS SMIL) • Optional Re-submission Mode Jerry Shih

  18. MMS Next Step • OMA MMS 1.3 Marks the end of the Current Technical Development • MMS 1.1 Service Enabler Package Published in 7-2004 • MMS 1.2 Candidate Enabler Package Approved in 06-2004 and Service Enabler Package Approved in 3-2005 • MMS 1.3 Technical Development Completed in 3-2005 • Focus is on Service Deployment and Interoperability • Will see MMS 1.2 Deployed in 2005 • MMS 1.3 could be Deployed in 2006 • Future Enhancements: • Spam and Fraud Control • User Service Management • Reliability and Maintainability Jerry Shih

  19. Backup Slides Jerry Shih

More Related