3GPP TSG-T2 SWG 3 adhoc
Braunschweig, Germany
27-29 June 2001	T2M010072	

Agenda Item:	

Source:	Siemens AG	

Title:	MMS and USIM

Document for:	Discussion

___________________________________________________________________________
1.	Introduction

2G and 3G mobile systems use the (U)SIM  which plugged into a mobile phone enables a subscriber to use the mobile communication service she has subscribed to. Moreover, user preferences and settings as well as user’s personal information can be stored on the (U)SIM.

2.	SMS and (U)SIM

When SMS is used as messaging service, the SMS related information like the short message itself, short message parameters, short message status report, etc. can be stored on the (U)SIM. Four elementary files on the (U)SIM are dedicated to SMS-related information as shown in the figure below. These are EFSMS for the storage of short messages, EFSMSS for SMS status information, EFSMSR for SMS reports and EFSMSP where SMS parameters are stored. These SMS parameters like e.g. the SMSC address are intended for user assistance in the preparation of mobile-originated SMs and provide operators with a tool to preconfigure the SMS service.

3.	MMS and (U)SIM

Unlike SMS, for MMS-related information there is no storage possibilities on the (U)SIM.  
The MMS service has a couple of features which would benefit from related information being stored on the (U)SIM. As of today a user’s MMS service is only available on a single terminal/device. If a user changes her terminal all MMS-related information and settings are lost. This inconvenience can be overcome by storing the necessary information on the (U)SIM.

If e.g. a user changes her terminal before downloading an MM she already got notified of, the information (notification) about this new MM may be lost. She could not download it from a terminal different from the one she used when she was notified. In a similar way a user would benefit from the ability to store delivery reports (mobile-terminated) and read-reply reports (mobile-terminated and mobile-originated) on the (U)SIM.  Ideally, the storage of entire MMs or parts of MMs on the (U)SIM could be envisaged – although (U)SIM capacity limitations may restrict such a use case.

Similar to SMS the MMS service should be able to store MMS parameters on the (U)SIM. The user can define default values for those parameters which are common for mobile-originated messages (MMs, Read-reply reports) which makes her experience a more comfortable service. Moreover, the service provider may preconfigure certain parameters, which allows for an automated processing of the MMS service by the terminal.  Preconfigured MMS parameters could be the MMS Relay/Server address, the originator address, default recipient address(es), a default expiry time and earliest time of delivery. But also the user’s preferences for message class, sender visibility, delivery report request, read reply report request and priority may be added. For compatibility reasons the MMS version and MMS implementation type (WAP, others ...) may be stored additionally.

3.	Proposal

For this reason there is a need for specifying the storing of MMS related information on the USIM. With this the user has consistent access to the MMS service independent of whatever terminal/device she uses at a certain point of time.

It is proposed to send an LS to 3GPP T3 asking for a solution to store MMS related information on the (U)SIM. The scope could be to store the following MMS related information:
-	The MMS related parameters:
o	MMS Relay/Server address 
o	originator address
o	recipient address 
o	expiry time
o	earliest time of delivery
o	message class
o	sender visibility request
o	delivery report request
o	read reply report request
o	priority
o	MMS implementation and version.
-	The MMS notification.
-	The entire and/or parts of Multimedia Messages.
-	The MMS delivery report.
-	The MMS read-reply report.  

A draft LS is attached including a high-level presentation of MMS.