|CLDC1.0||Connected Limited Device Configuration 1.0|
The Connected Limited Device Configuration (CLDC) defines the base set of application
programming interfaces and a virtual machine for resource-constrained devices like mobile phones, pagers,
and mainstream personal digital assistants. When coupled with a profile such as the Mobile Information Device Profile (MIDP),
it provides a solid Java platform for developing applications to run on devices with limited memory, processing power,
and graphical capabilities.
|CLDC1.1||Connected Limited Device Configuration 1.1|
Add the following to CLDC 1.0:
— Floating point maths support
— Weak references support
|MIDP1.0||Mobile Information Device Profile 1.0|
The Mobile Information Device Profile (MIDP),
when combined with the Connected Limited Device Configuration (CLDC),
is the Java runtime environment for today's most popular compact mobile information devices,
such as cell phones and mainstream PDAs.
|MIDP2.0||Mobile Information Device Profile 2.0|
Adds the following to MIDP1.0:
— UDP/Sockets/Secure Sockets/Server Sockets and access to serial ports
— Additional image formats (GIF / JPG / WMB)
— PCM (Pulse Code Modulation) wave format and/or additional sampled/synthetic sound formats
— Copy protection of MIDlet suites
— Discovery/Installation of MIDlets via other mechanisms (InfraRed/Bluetooth/etc)
— Custom 'built-from-scratch' UIs (e.g. www.thinlet.com)
|MIDP3.0||Mobile Information Device Profile 3.0|
Adds the following to MIDP2.0:
— No information at the moment
|JTWI||Java Technology for the Wireless Industry 1.0|
This JSR provides an overall architectural description as well as an integrated TCK and RI
to coordinate selected JCP efforts for the wireless industry.
|WSAPI||J2ME Web Services Specification|
The purpose of this specification is to define an optional package that provides standard access from J2ME to web services.
|CHAPI||Content Handler API|
Enabling J2ME applications to handle multi-media and web content can give developers and users
a seamless and integrated user environment on mobile phones and wireless devices.
|WMA1.0||Wireless Messaging API 1.0|
— Includes support for Short Message Service (SMS), Unstructured Supplementary Service Data (USSD) and Cell Broadcast Service (CBS)
— Push capabilities (launching a MIDlet on message receipt)
|WMA2.0||Wireless Messaging API 2.0|
— Extends JSR120 with support for Multimedia Message Service (MMS), MIME attachments and multipart messages
— Allows for MMS content to be protected using Digital Rights Management (DRM)
|MMAPI||Mobile Media API|
— MMAPI provides support for accessing and controlling time-based media such as audio and video
— MMAPI is a superset of MIDP 2.0 multimedia capabilities, adding support for playback and capture of image and video
|PDAP||PIM & File Data API|
— Add Remove phone contacts
— Calandar events and recurring events
— File access, Secure Digital card, Memory Stick card
— Ringtone location is platform dependent – but maybe accessible
— No write access to system filesystem areas
— Search for Bluetooth devices
— Query device profiles and capabilities
— Open stream connection to device
|SATSA||Security and Trust API|
— Provides support for the management of user certificates
— Provides support for user authentication using certificates
— Allows for J2ME applications to communicate with SmartCard-based applications and also
to general purpose encryption functionalities
— Provides security through the addition of a Security Element usable in operations
|M3G||Mobile 3D Graphics|
— Provide an efficient 3D Graphics API suitable for the J2ME platform (focused on CLDC/MIDP)
— Supports scene graph API (high-level) and immediate API (low-level, subset of OpenGL)
— Provides importer functions for textures, meshes, animations, and scene hierarchies
— Includes tight integration with MIDP
|PB||Personal Basis 1.0|
— Provides the Xlet application lifecycle as well as traditional Java Application lifecycle
— Provides a GUI framework for lightweight component toolkits
— Provides the full API from the Foundation Profile – less constraints than MIDP
— Considered as functionally equivalent to Java 1.1.8 with a more modern JVM
— Slimming operation of the Swing GUI toolkit from J2SE
— Java 2D graphics engine preserved
— Imaging API and Image load/save framework preserved
— Input Method framework preserved
— Pluggable Look And Feel dropped
An Optional Package that enables developers to write mobile location-based applications
for resource-limited devices. The API works on the J2ME CLDC v1.1 and CDC configurations.
|MSAPI||Mobile Sensor API|
The API provides general Sensor API that extends the usability and
choice of sensors for J2ME applications. It defines generic sensor functionality optimized
for the resource-constrained devices like mobile devices.
|CCAPI||Contactless Communications API|
This specification defines J2ME Optional Packages for
contactless communication, one package for bi-directional communication and the other for accessing
read-only information. As currently proposed, JSR 257 would set the stage for both one-way and bi-directional data capture
and data integration from RFID, barcode and other existing and standard approaches.
|MIAPI||Mobile Internationalization API|
This JSR defines an API that provides culturally correct data formatting,
sorting of text strings and application resource processing for J2ME MIDlets running in MIDP over CLDC.
|AMMSAPI||Advanced Multimedia Supplements API|
This specification defines an optional package for advanced multimedia functionality which is targeted
to run as an supplement in connection with MMAPI (JSR-135) in J2ME/CLDC environment.
|SVGAPI||Scalable 2D Vector Graphics API|
This specification defines an optional package API for rendering scalable 2D vector graphics,
including image files in W3C Scalable Vector Graphics (SVG) format.
SIP API for J2ME defines a multipurpose SIP API for J2ME clients.
It enables SIP applications to be executed in memory limited terminals, especially targeting to mobile phones.
MSA aims to reduce fragmentation for the Java community in two ways:
MSA defines a clear set of component JSRs that must be supported (mandatory JSRs) on next-generation mobile phones.
MSA gives less room for interpretation in the implementation of the JSRs by clarifying the conditions for interaction between them and for optional JSRs.
The mandatory APIs supported through MSA include 3D graphics, personal information management, Bluetooth™, Scalable Vector Graphics (SVG), web services, location services and payment services for Java ME (Micro Edition). Sony Ericsson has supported several of these APIs in its earlier Java Platform versions but with MSA there is finally industry alignment and a clear set of expectations on the implementation of these JSRs. With MSA, the mass-market mobile phone becomes an increasingly capable platform for enterprise development and it will be possible to ensure secure data storage and communication and create new innovative applications.
MSA reduces variations in the platform environment and creates a predictable environment for application developers, reducing porting issues when creating new applications and games for mass-market feature-rich phones.