Java ME Developer Guide

Chapter 9 - JSR-120 - Wireless Messaging API

a port number, the originating port number is set to an implementation specific value and any possible messages received to this port number are not delivered to the

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿ Please refer to the sections A.4.0 and A.6.0 of the JSR-120.

When a MIDlet in server mode requests a port number (identifier) to use and it is the first MIDlet to request this identifier it will be allocated. If other applications apply for the same identifier then an ￿￿￿￿￿￿￿￿￿￿￿ will be thrown when an attempt to open

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿ is made. If a system application is using this identifier, the MIDlet will not be allocated the identifier. The port numbers allowed for this request are restricted to SMS messages. In addition, a MIDlet is not allowed to send mes- sages to certain restricted ports, a ￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿ will be thrown if this is at- tempted.

JSR-120 Section A.6.0 Restricted Ports: 2805, 2923, 2948, 2949, 5502, 5503, 5508, 5511, 5512, 9200, 9201, 9203, 9207, 49996, 49999.

If you intend to use SMSC numbers then please review A.3.0 in the JSR-120 specific- ation. The use of an SMSC would be used if the MIDlet had to determine what recip- ient number to use.

9.4SMS Storing and Deleting Received Messages

When SMS messages are received by the MIDlet, they are removed from the SIM card memory where they were stored. The storage location (inbox) for the SMS mes- sages has a capacity of up to thirty messages. If any messages are older than five days then they will be removed, from the inbox by way of a FIFO stack.

9.5 SMS Message Types

The types of messages that can be sent are TEXT or BINARY, the method of encoding the messages are defined in GSM 03.38 standard (Part 4 SMS Data Coding Scheme). Refer to section A.5.0 of JSR-120 for more information.

DRAFT - Subject to Change [66/201]

Page 66
Image 66
Motorola maxx V6 manual SMS Storing and Deleting Received Messages, SMS Message Types, Draft Subject to Change 66/201