White Paper M600
Feature | Support in the M600 | |
|
| |
Possibility to configure the MMS parameters | • MMS circuit switched: Yes | |
by OTA provisioning | • MMS packet switched: Yes | |
|
| |
Possibility for all the parameters from the | • MMS circuit switched: Yes | |
parameters set to be OTA provisioned at the | • MMS packet switched: Yes | |
same time |
|
|
|
| |
Possibility for only one parameter from the | Using Device Management: | |
parameters set to be OTA provisioned | • MMS circuit switched: Yes | |
| • MMS packet switched: Yes | |
| Using Client Provisioning: | |
| • MMS circuit switched: No | |
| • MMS packet switched: No | |
|
| |
OTA provisioning solution | OMA Device Management and | |
| OMA Client Provisioning supported | |
|
| |
MMS User Agent functional entity will be a | Yes | |
separate entity from Web browser: |
|
|
|
| |
MMS User Agent support | OMA UAProf. | |
|
| |
Supplier indication of realized interoperability | Yes | |
tests between its MMS User Agent and MMS |
|
|
Relay/Server from other suppliers |
|
|
|
| |
Support of a standard or a proprietary proce- | OMA Device Management and | |
dure for OTA provisioning of MMS parame- | OMA Client Provisioning | |
ters |
|
|
|
|
|
Functionalities that the user is able to set | • | message subject |
during message composition: | • | MSISDN recipient address |
| • | email recipient address |
| • message Cc recipient(s) address(es) | |
| • | delivery report request |
| • | |
| • | message priority |
| • | validity period |
|
|
|
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 |
|
|
|
76 | February 2006 |
