White paper G900c
Feature | Support in G900c |
|
|
Possibility for only one parameter from the | Using Device Management: |
parameters set to be OTA provisioned | • MMS |
| • MMS |
| Using Client Provisioning: |
| • MMS |
| • MMS |
|
|
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 | Yes |
interoperability tests between its MMS User |
|
Agent and MMS Relay/Server from other |
|
suppliers |
|
|
|
Support of a standard or a proprietary | OMA Device Management and OMA Client Provisioning |
procedure for OTA provisioning of MMS |
|
parameters |
|
Functionalities that the user is able to set during message composition:
•Message subject
•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 | • | Phone memory |
elements into an MMS message: | • | Memory card |
|
|
|
Supplier indication if MMS User Agent will | No |
|
be able to handle a |
|
|
book |
|
|
|
| |
Possibility for sent messages to be | Yes | |
memorized into a folder in phone memory |
|
|
|
|
|
Actions that the user can perform after | • | Retrieve message immediately |
message notification: | • | Defer message retrieval |
| • | Reject message |
|
|
|
Actions that the user can perform after | • | Reply to sender |
message retrieval: | • | Reply to sender and to Cc people |
| • | Forward message |
| • | Delete message |
| • Save message into terminal | |
|
|
|
73 | August 2008 |