White Paper T610/612
Multimedia message service
Feature | Support in the T610/612 | |
|
| |
MMS/CSD parameters and MMS/GPRS | MMS is bound to a WAP profile. A WAP profile is bound to | |
parameters placement | a Data Account. A Data Account contains either CSD | |
| parameters or GPRS parameters. | |
|
|
|
Possibility to | • | MMS/CSD: Yes |
in factory | • | MMS/GPRS: Yes |
|
|
|
Possibility to configure the MMS parameters by | • | MMS/CSD: Yes |
OTA provisioning | • | MMS/GPRS: Yes |
|
|
|
Possibility for all the parameters from the parame- | • | MMS/CSD: Yes |
ters set to be OTA provisioned at the same time | • | MMS/GPRS: Yes |
|
|
|
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 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 operability | Yes |
|
tests between its MMS User Agent and MMS |
|
|
Relay/Server from other suppliers |
|
|
|
| |
Support of a standard or a proprietary procedure | Proprietary | |
for OTA provisioning of MMS parameters |
|
|
|
|
|
Functionalities that the user is able to set during | • | message subject |
message composition: | • | MSISDN recipient address |
| • | |
| • message Cc recipient(s) address(es) | |
| • | delivery report request |
| • | |
| • | message priority |
|
|
|
From where can the user insert multimedia ele- | • | terminal memory |
ments into multimedia messages: | • | directly from camera |
|
|
|
Supplier indication if MMS User Agent will be | No |
|
able to handle a |
|
|
|
|
|
Possibility for sent messages to be memorized into | Yes |
|
a folder in handset memory |
|
|
|
| |
Actions that the user can perform after message | • retrieve the message immediately | |
notification: | • | defer message retrieval |
| • | reject message |
|
|
|
53
