Feature
Supplier indication if MMS User Agent will be
able to handle a network-based address book
Possibility for sent messages to be memorized into
a folder in handset 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 video
Multimedia codecs/formats supported for image
MMS User Agent provides:
Supported formats for message presentation:
Storage capacity dedicated to multimedia mes-
sages (Kb)
Maximum message size that can be handled by the
handset for message
Possibility to configure unconditional message
modification (such as media modification in mes-
sages)
MMS User Agent will report problems to user in
case of:
Performance and technical characteristics
Support in the T226
No
Yes
•
retrieve the message immediately
•
defer message retrieval
•
reject message
•
reply to the sender of the message
•
reply to the sender and to Cc people
•
forward the message
•
delete the message
•
save message into terminal
AMR, AAC
None
Baseline JPG, GIF 89a
•
text formatting facilities (only textsize)
•
colored text/background (Viewer/player supports col-
ored text and background. Not editable in composer)
•
predictive writing
•
message body + attachments
(email presentation)
•
SMIL version as described in "Nokia/Ericsson MMS
Conformance document
(not WML and SMIL 2.0 Boston)
~400kb available for user data (images, sounds, MMS,...)
30 kb for sending, 50 kb for receiving
Yes
•
message not sent causes no user subscription to service,
if included in ResponseText (please see WAP209)
•
message not sent causes required functionality not sup-
ported by MMS Relay/Server, if included in Response-
Text (please see WAP209)
•
message not sent causes insufficient credit (in case of
prepaid charging), if included in ResponeText (please
see WAP209)
T226 White Paper
July 2003 (Rev C)
46