Mobile Information Device Profile (MIDP) Technical Review

Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

Slide 1

Chapter 5 Mobile Information Device Profile (MIDP) Technical Review

2000, Sun Microsystems, Inc. All rights reserved.

Slide 2

Objectives
Identify the relationship between Connected Limited Device Configuration (CLDC) and Mobile Information Device Profile (MIDP) Overview of MIDP Identify each layer of Mobile Information Device (MID)

. . . . .

Slide 3

MIDP and CLDC


Mobile Information Device Profile (MIDP) is designed to work on top of Connected Limited Device Configuration (CLDC) Software and Hardware Requirements for a Mobile Information Device (MID) are in addition to those for the broader range of Connected Limited Devices (CLD) Addressed in Java Community Process(sm): Process(sm): JSR-37 JSR-

. . . . .

Slide 4

MIDP Expert Group (MIDPEG)


. . . . . . . . . . . . . . . .
Nokia NTT DoCoMo Palm RIM Samsung Sharp Siemens Sony Sun Symbian Telecordia AOL

Ericsson Espial Group Fujitsu Hitachi J-Phone Tokyo Co. Matsushita Mitsubishi Motorola NEC DDI

. . . . . . . . . . . . . . . . . . . . . . . .

Slide 5

MIDP in J2ME platform


Profile Profile Profile Profile

JavaTM 2 Enterprise JavaTM 2 Edition Standard Edition

TV Screen Car Profile Phone Profile Profile

Foundation Profile
CDCCDC

MID Profile
CLDC

JavaTM 2 Micro Edition JavaTM Language


HotSpotTM JVMTM KVM

Smart Card Profile

Card VM

Slide 6

MIDP Scope
Define the architecture and the associated APIs required to enable an open application development environment for Mobile Information Devices (MID) Enable 3rd-party application development for 3rdthese devices Simplicity, rather than completeness is a main goal

. . . .

Slide 7

MIDP Scope: Primary Goals


Size: must fit in small footprint (128K ROM) Efficiency: Must run on low- end microprocessors low Must run in limited heap size (32 128K RAM) (32 Minimal creation of garbage Time to market

. . . . . .

Slide 8

MIDP Scope
What is NOT in MIDP Scope How an application actually gets on the device End-to-end security model End- to System or OEM specific application needs Any particular implementation

Slide 9

MIDP assumptions on MIDs


MIDP was developed with the following assumption on MIDs System software A minimal kernel to manage hardware with at least one schedulable entity to run the Java virtual machine (JVM) A mechanism to read and write from non-volatile memory A minimal capability to write to a bit-mapped graphics display Read and write access to the device's wireless networking A mechanism to provide a time base for use in time stamping the records written to persistent storage

Slide 10

MIDP Class Libraries


MIDP defines the following set of class libraries that map to the aforementioned assumptions. Application Lifecycle Package javax.microedition.midlet javax. microedition. User Interface Package javax.microedition.lcdui javax. microedition. Persistence Package javax.microedition.rms javax. microedition. Networking Package javax.microedition.io javax. microedition. Language and Utility Packages java.lang and java.util java.lang java.util

K K K K K K

. .

Slide 11

MIDP Architecture

Slide 12

MIDP Layers
Hardware Layer: This layer includes the device's CPU, ROM, and EEPROM Native System Software: This layer includes the operating system and the libraries used by the device's native applications. CLDC Classes Layer: This layer sits on top of the native system software. This layer contains the K Virtual Machine (KVM) and associated libraries defined within the CLDC specification. This layer provides the underlying Java functionality upon which higher-level Java APIs, highersuch as those defined in the MIDP , may be built. MIDP Classes Layer: Sits atop the CLDC layer to provide additional APIs for cellular phone, two-way pager, and PDA vertical markets. two-

. . . . . . . .

Slide 13

MIDP Layers (Contd)


OEM-Specific Classes: OEM OEMss additional device-specific classes to address devicedevice-specific application requirements. device Applications written using these APIs will not be portable across multiple MIDs. MIDs. MIDP Application Layer: Applications that can be created for a MID that use only APIs defined within of the MIDP and CLDC specifications. These applications, or "MIDlets," will be portable "MIDlets," across all MIDs. MIDs.

Notice that OEM-specification classes can be designed to interact with the MIDP and CLDC classes layer.

. . . .

Slide 14

MIDP Layers (Contd)


OEM-Specific Application Layer: OEM An OEM-specific application based on OEM-specific OEMOEMclasses that are not part of the MIDP specification. These applications are not portable across MIDs. MIDs. Native Application Layer: Application that is not written in Java and is built on top of the MID's existing native system software. Not portable across MIDs. MIDs.

Notice that OEM-specification classes can be designed to interact with the MIDP and CLDC classes layer.

. . . .

Slide 15

Summary
Difference between CLDC and MIDP Architecture of MIDP

. . .

Slide 16

Notes

You might also like