3GPP TSG-T2 #5 / ETSI SMG4
Helsinki, FINLAND, 6-9 September 1999	TSGT2#5(99)683	

Agenda Item:	7

Source:	BT Cellnet

Title:	Multimedia Messaging Service Requirements	

Document for:	Discussion

___________________________________________________________________________

Introduction

For third generation a number of service requirements for multi-media messaging are proposed for discussion.  It is proposed that these requirements are taken into consideration when developing a multi-media messaging system for 3GPP.  These include:

Universality of Access
A user can access their MM messages through a number of different access points, which should include 3G, 2G networks, the Internet etc. and where possible the user should experience the same MMI  to the server interface. (Access through the 2G network may be limited due to the terminal capability). 

Alerting Mechanisms
The user shall still be alerted of the MM message in an appropriate manner depending on the user state (ie alerting mechanisms shall be dependent on the UE being in active or idle mode).

Multiple Mediums
MM messages can be composed of either a single medium (eg voice) or multi-media (eg Voice and video).  It is anticipated the server need only support 3 media at anyone time, (voice, video and data).
 
Media Conversion and Control
The network shall support conversion between MM message types, this shall be controlled by the user and may have default settings depending on the user environment and or the UEs state, eg Text To Speech when in car.

Server Awareness of UE Capability
The server shall be aware of the UE's capability and shall deliver a MM message / notification in a manner compatible with the UE's capability.

Push Mechanism
The MMM server shall support the push mechanism, as supported for SMS 03.40.

Message Profiling
The user shall define what media types and notification shall be delivered to him eg voice only or text only.

Storage of Multi-Media Messaging
MM messages shall be stored in the network, until expired, or deleted by the user.  The MM messages that are downloaded shall be stored in the UE if the user gives permission.  The user  shall be able to create, read, update and delete MM messages when they are off line.  When the user connects again with the network these shall be updated automatically with the network and any new MM messages shall be sent if the user has requested this.

Prioritisation
The sender and recipient of the MM message can prioritise the importance of the MM messages.  However, the recipient user shall have ultimate control regarding the delivery of the MM messages.

Message Screening
This will allow the user to set defaults in the server that will delete unwanted messages without viewing, ie delete "junk mail".

Concurrency
It shall be possible for MMS delivery to occur whilst the phone is active on a speech or data call.