Mobitex is a packet-switched, narrowband PCS community, designed for huge-area wi-fi data communications. It become developed in 1984 with the aid of Eritel, an Ericsson subsidiary, a nd there are actually over 30 Mobitex networks in operation worldwide.
Profiles layer based on a configuration and additional API's for user interface, persistent storage and factors necessary for developing wireless applications.
Mobile Information Device (MIDP) Profile - MIDP is specification published for the use of Java, mobile devices, and embedded system. It is a part of Java Micro Edition (Java ME) framework and top of a Connected Limited Device Configuration (CLDC). Its provides a standard platform for small, resource-limited, and wireless-connected mobile information devices. MIDP requires CLDC for implementation.
Personal Digital Assistance (PDAP) Profile - PDAP is specifically designed for Palmtop or similar devices with limited power, typical battery operated, user interface displays like a pointing device and character input, with minimum of 512kb (and maximum 16MB) combined ROM (read only memory) and RAM (random access memory) hardware.
Personal Profile - Personal profile specification repacks the Personal Java APIs Environment to provide J2ME specification for devices that need a high degree of Internet connectivity. This profile builds on top of foundation profile.
Personal Basic Profile - This profile is intended to provide basic Graphical User Interface (GUI) capabilities to devices where the high-fidelity, feature-rich Personal Profile is not fully utilized or necessary means which running the CDC and Foundation Profile.
Remote Method Invocation (RMI) Profile - RMI profile also builds on top of Foundation profile and supports inter-application RMI over TCP/IP connections for applications written to the Foundation Profile. It's provides the infrastructure to marshal objects as the parameters and return values of remote method calls while the dynamic class loading is utilized to make the marshalled objects available to a particular JVM during a remote call.
Foundation Profile - The Foundation profiles specified for devices that can support a rich networked J2ME environment. It provides services for other device-specific profiles (such as Personal profile and RMI profile) to be layered on top of it. This profile specific design for CDC profiles that provide Graphical User Interface (GUI), Data storage, and distribution of java networking.
The MIDlet lifecycle is the fundamental for creation of any MIDlet. The lifecycle includes the execution states such as creation, start, pause and exiting operations and a set of valid transitions. To manage the downloading and lifecycle of MIDlets, there is software by name Application Management Software. A runtime environment is provided by the AMS. The runtime environment enforces the permissions, security and the execution states and is provided the required scheduling and system classes.
Java Application Descriptor file and Java Archive are the two components that any MIDlet suite is delivered. The JAD file describes the MDIlet suite. The description comprises of the MIDlet suites name, location and size of the JAR file and other configuration and profile requirements.
The MIDlet life-cycle is fundamental to creating any MIDlet.
1.The life-cycle defines the execution states of a MIDlet creation, start, pause, and exit
2.A MIDlet is either in the active state or the paused state.
3.When it is first loaded by the MIDP runtime environment, it will be in the paused state.
4.The runtime will generally call the method startApp() to signal that the MIDlet should now activate itself.
5.Whenever the application is idle, the runtime can put the MIDlet back into the paused state.
6.When it is paused, the application will not receive user interface events.
7.The runtime will call pauseApp() to indicate that it has done this.
8.When the operator is finished with the MIDlet, the runtime will destroy it.
9.Before it does this, it calls the method destroyApp() method.
10.The MIDlet must deallocate resources here as it does when it enters the paused state.
11.In the MIDP documents, `destroyed' is described as being one of the states that the MIDlet may be in.
The Generic Connection Framework (GCF) makes it clean for wireless gadgets to make community connections. It is a part of CLDC and CDC and is living in the javax.Microedition.Io bundle.
Compact HTML (cHTML) is a subset of HTML which is designed for small gadgets. The fundamental functions of HTML which are excluded from cHTML are: JPEG photo, Table, Image map, Multiple individual fonts and styles, Background coloration and picture, Frame and Style sheet.
Also referred to as IS-136, CDMA2000 is a third generation wireless era. Supports speeds ranging from 144Kbps to 2Mbps.
Class X is "derived from" class Y if class X extends class Y. See also subclass, superclass.
Wireless Transaction Protocol (WTP) is WAP's transaction protocol that works between the session protocol WSP and security protocol WTLS. WTP chops data packets into lower level datagrams and concatenates received datagrams into useful data. WTP also keeps track of received and sent packets and does re-transmissions and acknowledgment sending when needed.
WMLScript is a subset of the JavaScript scripting language designed as part of the WAP standard to provide a convenient mechanism to access mobile phone's peripheral functions.
Wireless Datagram Protocol (WDP) works as the transport layer of WAP. WDP processes datagrams from upper layers to formats required by different physical datapaths, bearers, that may be for example GSM SMS or CDMA Packet Data. WDP is adapted to the bearers available in the device so upper layers don't need to care about the physical level.
Wideband Code-Division Multiple Access (W-CDMA), also known as IMT-2000, is a 3rd generation wireless technology. Supports speeds up to 384Kbps on a wide-area network, or 2Mbps locally.
The Wireless Application Environment (WAE) provides a application framework for small devices. WAE leverages other technologies such as WAP, WTP, and WSP.
The Visitor Location Register (VLR) is a database that contains temporary information about subscribers.
Developed by Nortel Networks, Universal Mobile Telecommunications Service (UMTS) is a standard that will provide cellular users a consistent set of technologies no matter where they are located worldwide. UMTS utilizes W-CDMA technology.
Universal Description, Discovery, and Integration (UDDI) is an XML-based standard for describing, publishing, and finding Web services. UDDI is a specification for a distributed registry of Web services.
Telematics is a location-based service that routes event notification and control data over wireless networks to and from mobile devices installed in automobiles. Telematics makes use of GPS technology to track vehicle latitude and longitude, and displays maps in LED consoles mounted in dashboards. It connects to remote processing centers that turn provide server-side Internet and voice services, as well as access to database resources.
T9 is a text input method for mobile phones and other small devices. It replaces the "multi-tap" input method by guessing the word that you are trying to enter. T9 may be embedded in a device by the manufacturer. Note that even if the device supports T9, the Java implementation may or may not use it. Check your documentation for details.
The Simple Object Access Protocol (SOAP) is an XML- based protocol that allows objects of any type to communicated in a distributed environment. SOAP is used in developing Web Services.
A deck is a collection of one or more WML cards that can be downloaded, to a mobile phone, as a single entity.
Frequency-division multiple-access (FDMA) is a mechanism for sharing a radio frequency band among multiple users by dividing it into a number of smaller bands.
JavaHQ is the Java platform control center on your Palm OS device.
LCDUI is a shorthand way of referring to the MIDP user interface APIs, contained in the javax.microedition.lcdui package. Strictly speaking, LCDUI stands for Liquid Crystal Display User Interface. It's a user interface toolkit for small device screens which are commonly LCD screens.
The RMI Optional Package (RMI OP) is a subset of J2SE 1.3's RMI functionality used in CDC-based profiles that incorporate the Foundation Profile, such as the Personal Basis Profile and the Personal Profile. The RMIOP cannot be used with CLDC-based profiles because they lack object serialization and other important features found only in CDC-based profiles. RMIOP supports most of the J2SE RMI functionality, including the Java Remote Method Protocol, marshalled objects, distributed garbage collection, registry-based object lookup, and network class loading, but not HTTP tunneling or the Java 1.1 stub protocol.
Remote method invocation (RMI) is a feature of J2SE that enables Java objects running in one virtual machine to invoke methods of Java objects running in another virtual machine, seamlessly.
The public service telephone network (PSTN) is the traditional, land-line based system for exchanging phone calls.
Modulation is the method by which a high-frequency digital signal is grafted onto a lower-frequency analog wave, so that digital packets are able to ride piggyback on the analog airwave.
Mobitex is a packet-switched, narrowband PCS network, designed for wide-area wireless data communications. It was developed in 1984 by Eritel, an Ericsson subsidiary, a nd there are now over 30 Mobitex networks in operation worldwide.
The Next Generation MIDP specification is currently under development by the Java Community Process. Planned improvements include XML parsing and cryptographic support.
The Mobile Information Device Profile (MIDP) is a specification for a J2ME profile. It is layered on top of CLDC and adds APIs for application life cycle, user interface, networking, and persistent storage.
MIDlets are packaged and distributed as MIDlet suites. A MIDlet suite can contain one or more MIDlets. The MIDlet suite consists of two files, an application descriptor file with a .jad extension and an archive file with a .jar file. The descriptor lists the archive file name, the names and class names for each MIDlet in the suite, and other information. The archive file contains the MIDlet classes and resource files.