White Paper W950
Preliminary version - PA4
Multimedia messaging service
Feature |
| Support in the W950 |
| |
|
|
|
| |
Support of MMS protocol stack version | 1.2 |
|
| |
|
| |||
MMS/circuit switched parameters and MMS/ | MMS is bound to a Data Account. A Data Account con- | |||
packet switched parameters placement | tains either circuit switched parameters or packet | |||
|
| switched parameters. |
| |
|
|
|
| |
Possibility to | • | MMS circuit switched: Yes |
| |
ters in factory |
| • | MMS packet switched: Yes |
|
|
|
|
| |
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 | y | |
parameters set to be OTA provisioned at the | • | MMS packet switched: Yes | ||
|
|
|
| |
same time |
|
| l | |
|
|
|
| |
|
|
| ||
Possibility for only one parameter from the | Using Device Management: |
| ||
parameters set to be OTA provisioned | • | MMS circuit switched: Yes |
| |
|
| • | MMS packet switched: Yes |
|
|
|
| On |
|
|
| Using Client Provisioning: |
| |
|
| • | MMS circuit switched: No |
|
|
| • | MMS packeteswitched: No |
|
OTA provisioning solution |
| OMA DevicesManagement and |
| |
|
| OMA Client Provisioning supported | ||
| U |
| ||
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 |
| ||
| ternal |
|
| |
dure for OTA provisioning of MMS parameters | OMA Client Provisioning |
| ||
n |
|
|
| |
Functionalities thatIthe user is able to set dur- | • | Message subject |
| |
ing message composition: |
| • | MSISDN recipient address |
|
or |
| • | email recipient address |
|
| • | Message Cc recipient(s) address(es) | ||
| • | delivery report request |
| |
| • |
| ||
F |
|
| ||
| • | message priority |
| |
| • | validity period |
| |
|
|
| ||
|
|
| ||
From where can the user insert multimedia ele- • | Terminal memory |
| ||
ments into multimedia messages: |
|
|
| |
|
|
|
| |
Supplier indication if MMS User Agent will be | No |
|
| |
able to handle a |
|
|
| |
|
|
| ||
Possibility for sent messages to be memorized | Yes |
| ||
into a folder in handset memory |
|
|
| |
|
|
|
|
|
60 | June 2006 |