16
Mobile Information Device
Native System Software
CLDC
MIDP
OEM
Classes
MIDP-Compliant
Apps
OEM
Apps
Native
Apps
Mobile Information Device
Native System Software
CLDC
MIDP
OEM
Classes
MIDP-Compliant
Apps
OEM
Apps
Native
Apps
Figure 1 Java Platform
The Configuration Layer used in the V3x
is the Connected Limited Device Configuration
1.1 (CLDC 1.1) and the Profile Layer used is the Mobile Information Device Profile 2.0
(MIDP 2.0). Together, the CLDC and MIDP provide common APIs for I/O, simple math
functionality, UI, and more.
For more information on J2ME, see the Sun™ J2ME documentation
(
http://java.sun.com/j2me/
).
The Motorola J2ME Platform
Functionality not covered by the CLDC and MIDP APIs is left for individual OEMs to
implement and support. By adding to the standard APIs, manufacturers can allow
developers to access and take advantage of the unique functionality of their handsets.
The V3x contains OEM APIs for extended functionality ranging from enhanced UI to
advanced data security. While the V3x can run any application written in standard MIDP,
it can also run applications that take advantage of the unique functionality provided by
these APIs. These OEM APIs are described in this guide.
Resources and API’s Available
MIDP 2.0 will provide support to the following functional areas on the V3x
:
MIDP 2.0
•
Application delivery and billing
•
Application lifecycle
•
Application signing model and privileged security model
•
End-to-end transactional security (HTTPS)
•
MIDlet push registration (server push model)
•
Networking
