White Paper M600
Feature | Support in M600 |
|
|
save the message in the Inbox | Yes |
|
|
forward the message | Yes |
|
|
know the remaining capacity storage | Yes |
|
|
Supported ways for replying to a received |
|
SMS: |
|
|
|
via SMS | Yes |
|
|
via phone call (set up a call to the | Yes |
number contained in the message body) |
|
|
|
via USSD session | No |
|
|
Possibility to offer the user the ability of | Yes, using phonebook groups or entering multiple num- |
sending an SMS to a list of recipients | bers manually. |
|
|
Possibility to write an email address as a | No |
recipient address |
|
|
|
SMS storage | In handset and SIM. |
|
|
Nokia Picture Messaging | No |
|
|
Enhanced message service
Feature | Support in the M600 |
|
|
Level of compliance supported by the | Enhanced Messaging Service (EMS) according to the |
handset regarding the specifications | standard 3GPP™ TS 23.040 v4.3.0, with the addition of |
described in release 99. | the ODI feature from 3GPP™ TS 23.040 v5.0.0. |
|
|
Number of messages that the handset is | TBD |
able to handle to generate a concatenated |
|
message |
|
|
|
Capacity storage | TBD |
|
|
Outgoing messages | It is possible to: |
| • see how many short messages an EMS message |
| consists of before sending it. |
| • choose whether to send the message or not after |
| writing it. |
|
|
Incoming messages | • A signal is heard once all parts of the message have |
| been received. |
| • It is possible to |
| sage. Sounds, pictures, and animations can be |
| inserted in a new message, if the object is not pro- |
| tected using ODI. |
|
|
Concatenated messages | A receipt is received in the handset when all parts of a |
| concatenated message have been delivered. |
|
|
74 | February 2006 |