Sony Ericsson K220 White Paper page 30

Feature
Supplier indication of realized
interoperability tests between its MMS User
Agent and MMS Relay/Server from other
suppliers
Support of a standard or a proprietary
procedure for OTA provisioning of MMS
parameters
Functionalities that the user is able to set
during message composition:
The user can insert multimedia elements into
multimedia messages from:
Possibility for sent messages to be
memorized into a folder in the phone
memory
Actions that the user can perform after
message notification:
Actions that the user can perform after
message retrieval:
Multimedia codecs/formats supported for
audio
Multimedia codecs/formats supported for
image
Supported formats for message
presentation:
Maximum message size that can be handled
by the phone for message
MMS User Agent will report problems to
user in case of:
Support
Yes
Proprietary
• Message subject
• Email recipient address
• Message Cc recipient(s) address(es)
• Delivery report request
• MSISDN recipient address
• File Manager
• Camera
• Contacts
• Calendar
Yes
• Auto Download
• Always Ask
• Ask in roaming
• Reply to the sender of the message (MMS)
• Forward the message (SMS/MMS)
• Delete the message
• Call the sender of a message
• View details
• Save items
I-Melody and MIDI
JPEG, GIF87, GIF89A, WBMP, BMP
• Message body + attachments (email presentation)
• SMIL version as described in OMA MMS IOP docu-
ment version 1.0
Content Class and Creation mode are applied. Also
maximum size is possible to customize.
• Message not sent causes no user subscription to serv-
ice, if included in ResponseText (please see WAP209).
• Message not sent causes required functionality not
supported by MMS Relay/Server, if included in
ResponseText (please see WAP209).
• Message not sent causes insufficient credit (in case of
prepaid charging), if included in ResponseText (see
WAP209).
30
White paper K220
February 2007