T226 White Paper
July 2003 (Rev C)
46
Performance and technical characteristics
Supplier indication if MMS User Agent will be
able to handle a network-based address book
No
Possibility for sent messages to be memorized into
a folder in handset memory
Yes
Actions that the user can perform after message
notification:
• retrieve the message immediately
• defer message retrieval
• reject message
Actions that the user can perform after message
retrieval:
• 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
Multimedia codecs/formats supported for audio AMR, AAC
Multimedia codecs/formats supported for video None
Multimedia codecs/formats supported for image Baseline JPG, GIF 89a
MMS User Agent provides: • text formatting facilities (only textsize)
• colored text/background (Viewer/player supports col-
ored text and background. Not editable in composer)
• predictive writing
Supported formats for message presentation: • message body + attachments
(email presentation)
• SMIL version as described in “Nokia/Ericsson MMS
Conformance document
(not WML and SMIL 2.0 Boston)
Storage capacity dedicated to multimedia mes-
sages (Kb)
~400kb available for user data (images, sounds, MMS,...)
Maximum message size that can be handled by the
handset for message
30 kb for sending, 50 kb for receiving
Possibility to configure unconditional message
modification (such as media modification in mes-
sages)
Yes
MMS User Agent will report problems to user in
case of:
• 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)
Feature Support in the T226