White Paper T630/T628
Multimedia message service
Feature | Support in the T630/T628 | |
|
| |
MMS/CSD parameters and MMS/GPRS | MMS is bound to a WAP profile. A WAP profile is | |
parameters placement | bound to a Data Account. A Data Account contains | |
| either CSD parameters or GPRS parameters. | |
|
|
|
Possibility to | • | MMS/CSD: Yes |
eters in factory | • | MMS/GPRS: Yes |
|
|
|
Possibility to configure the MMS parameters | • | MMS/CSD: Yes |
by OTA provisioning | • | MMS/GPRS: Yes |
|
|
|
Possibility for all the parameters from the | • | MMS/CSD: Yes |
parameters set to be OTA provisioned at the | • | MMS/GPRS: Yes |
same time |
|
|
|
|
|
Possibility for only one parameter from the | • | MMS/CSD: No |
parameters set to be OTA provisioned | • | MMS/GPRS: No |
|
| |
OTA provisioning solution | OTA specified by Sony Ericsson and Nokia | |
|
|
|
MMS User Agent functional entity will be a | Yes |
|
separate entity from WAP browser: |
|
|
|
| |
MMS User Agent support | WAP WTA, WAP UAProf and WTA Public. | |
|
|
|
Supplier indication of realized inter operabil- | Yes |
|
ity tests between its MMS User Agent and |
|
|
MMS Relay/Server from other suppliers |
|
|
|
| |
Support of a standard or a proprietary proce- | Proprietary | |
dure for OTA provisioning of MMS parame- |
|
|
ters |
|
|
Functionalities that the user is able to set during message composition:
•message subject
•MSISDN recipient address
•
•message Cc recipient(s) address(es)
•delivery report request
•
•message priority
From where can the user insert multimedia | • | terminal memory |
elements into multimedia messages: | • | directly from camera |
|
|
|
Supplier indication if MMS User Agent will be | No |
|
able to handle a |
|
|
book |
|
|
|
|
|
Possibility for sent messages to be memo- | Yes |
|
rized into a folder in handset memory |
|
|
|
| |
Actions that the user can perform after mes- | • retrieve the message immediately | |
sage notification: | • | defer message retrieval |
| • | reject message |
|
|
|
63 | October 2003 |
