10atie_mms evolution past, present, future

8/6/2019 10ATIE_MMS Evolution Past, Present, Future

1/19

4-7-2005 Jerry Shih 1

MMS EvolutionPast, Present , Future

Jerry Shih


2/19


Outline

History of MMS Project

Where to Focus on Actions

What is the Next Step


3/19


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 whichwas Commonly Adopted Among Different Fora

Initially, 7 Reference Points (MM1-MM7) were Identified in theArchitecture 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 andMM3 Interface Based on EMAIL


4/19


The Industry Landscape


5/19


Problems with the Industry

The Many Different Fora Working on MMS CreatedConfusion 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 GlobalRoaming

Delay in Product Development


6/19


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 maintenancefor 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


7/19


Future MMS Specs Development

Core Network

Radio Access

Network

OMA(MMS, WAP,IM,Location, Games etc)

3GPP2

3GPP2 3GPP

3GPP

cdma2000 UMTS/EDGE

Service Enabling

Plane


8/19


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


9/19


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


10/19


OMA MMS 1.2 Objectives

End-to-end Interoperability for massmarket Person-to- Person MMS service

Accelerated Commercial Availability (MajorPush from GSMA)

Persistent Network Based MM Storage

Security on MM Content (Image Rich, Video)


11/19


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


12/19


New Functionality in MMS 1.2

Terminal Capability Negotiation

MMBox

Digital Rights Management (DRM)


13/19


OMA MMS 1.3 Objectives

Person-to-Application, Content-to-Person

Use Cases

Better Content Protection Support User Device Evolution

Message Template Application


14/19


Classification of MMS Messaging

Image Messaging -- Multimedia messaging using ImageBasic, Image Rich and Megapixel MM content classeswhich are optimized for person-to-person use cases butalso usable for content-to-person use cases

Video Messaging Multimedia messaging using VideoBasic and Video Rich MM content classes which areoptimized for person-to-person use cases but also usablefor content-to-person and person-to-application use cases

Content Messaging Multimedia messaging usingContent Basic or Content Rich MM content classes which

are optimized forperson-to-application and content-to-person services but also usable to person-to-personservices with assisting techniques.


15/19


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


16/19


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


17/19


Summary

OMA MMS 1.3 Service EnablerIntroduces:

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 ContentRich content classes)

Better Content Protection (full DRM) Sophisticated Presentation (PSS SMIL)

Optional Re-submission Mode


18/19


MMS Next Step

OMA MMS 1.3 Marks the end of the Current TechnicalDevelopment 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


19/19


10atie_mms evolution past, present, future

Documents