Technical information

Appendix B: Default MIDlet Features
July 15, 2008 G24 KJAVA User’s Guide B-3
SMS Updates / Requests Listener
The DM starts an SMS listener which allows updates and requests to be sent to the unit. The SMS
sent to this listener must meet a specific format.
Upon initialization, the DM reads the OSC property "oem.dm.smslistener", if set to "on", which
is the default value, it starts listening to SMS messages. To turn off the listener set the property to
"off". Using these messages, updates and requests can be sent to the unit.
Message Format
The SMS has to be sent to port 16001. The message is constructed from fields and values. The
field and value are separated by a colon, and the fields are separated by an LF (line feed, "\n")
sign or a CR (carriage return, "\r") sign. LF and CR are treated as the same character.
Example
:
action:value
field1:value
field2:value
field3:value
Additional notes:
• Every message must contain an "action" field which defines the update or request type.
• The order of the fields has no importance.
• If there is more than one occurrence of a field, the last occurrence will be used.
• The field strings and value strings are not case-sensitive.
• All field strings and value strings are trimmed.
Messages Types
Supported messages:
• Java/Mms Session Update
• OTA Download Triggering
• Fault Report Addresses Update
• Fault Report Triggering
• Ping
Java/MMS Session Update
This message updates the "Java Session" or "Mms Session" web sessions.
Additional notes:
• The only difference between the two is the action field.
• If the message contains a field with an invalid value, the message is dismissed.
• To set a field to its default value, don't include the field in the message.
• The update replaces the full Web Session, not specific fields. Old values are not saved.