Technology

All the CDT applications are Java based applications operating on the mobile phone. These applications will operate on all Java enabled devices.

Java is implemented in a sandbox type environment so on CDMA and GSM mobile devices, developers can develop the core application without regard to network technology. By utilising device specifications and documentation, the applications are optimised to serve both the CDMA and GSM markets. The applications are written to optimise themselves by interrogating the devices’ basic capabilities.

In relation to m-Crypt:API, the technical considerations are in the encryption. This is all performed within the Java/J2ME environment and utilises whatever the underlying network technology is available. All the applications have been engineered to operate on a basic Java enabled phone (basic series 30 device).

The applications perform two tests on the phone's capabilities to decide the amount of functionality it can exploit. On installation, an application interrogates the version of the Java runtime environment (i.e. MIDP-1.0 or MIDP-2.0). Depending on this, it will avail of push registry technology for automatic activation on message receipt. After installation it checks for the availability of the Wireless Messaging Java API (JSR-120, most devices). If available, the applications will exploit the additional functionality.

The application operates over WAP 1.0, 1.1, & 2.0 plus HTTP. It also operates over GPRS, EDGE and 3G. Specifically, the application relies on a valid GPRS/HTTP gateway from the mobile device to send and receive messages.

Java™ technology consists of both a programming language and a software platform. The core benefit of the Java platform is that it can run on top of several different operating systems, hiding the complexity of the device from the applications and application developers.

Java technology is used to provide an open application platform for developers, allowing them to create applications for devices that support the technology. A standardised platform gives wide scope for real creativity and frees the developers from dealing with the peculiarities of each different device.

Interoperability provided by the Java platform is also very valuable for mobile device users. Applications created with standard Java APIs should run in all compatible devices, no matter who has manufactured them.

The latest release of the Java platform is known as Java™ 2 Platform. The version for smaller devices, such as mobile devices, communicators, and PDAs, is known as Java™ 2 Platform, Micro Edition (J2ME™).

The J2ME platform is not a single specification for a piece of software. Instead, it is a collection of technologies and specifications designed for different parts of the small-device market.

The J2ME platform defines both Connected Limited Device Configuration (CLDC)-based Mobile Information Device Profile (MIDP) as well as Connected Device Configuration (CDC)-based Personal Profile.

MIDP is a profile for portable devices based on CLDC that have communications capability, such as mobile phones. It defines functionality such as usage of the user interface, persistence storage, networking, and application model. Almost all new devices support the MIDP profile. MIDP 2.0 is supported by the new devices, whereas older devices support MIDP 1.0. On top of MIDP, devices support various additional APIs.

Devices based on Series 80 Platform 2.0 support both MIDP 2.0 and Personal Profile.

By exploiting the Java environment allows the applications to be compatible across the widest range of mobile devices. The applications have been designed to run on minimalist implementation of the Java Runtime Environment, and integrate the capabilities of the device to offer greater functionality where appropriate. In effect, the applications do not care what device they are running on – the only requirement is that the device supports Java J2ME specifications.

“Short for Code-Division Multiple Access, CDMA is a digital cellular technology that uses spread-spectrum techniques. Unlike competing systems, such as GSM, that use TDMA, CDMA does not assign a specific frequency to each user. Instead, every channel uses the full available spectrum. Individual conversations are encoded with a pseudo-random digital sequence. CDMA consistently provides better capacity for voice and data communications than other commercial mobile technologies, allowing more subscribers to connect at any given time, and it is the common platform on which 3G technologies are built.

The question is often raised as to the applications CDMA and GSM compatibility. Since the applications are built using Java technology which is layered on top of the underlying operating system it does not affect use unless the chipset in use is Qualcomm. In this instance modifications may be required to cater for BREW. However, at this stage even BREW is providing full J2ME compliance.

By utilising standard J2ME and JSR specifications we can develop applications without regard for the underlying network technology.

All CDT applications are compatible with all Java enabled mobile phones. The core concept behind these applications is to encompass as many mobile devices as possible. To this extent a minimalist installation is under the 30k threshold on early Java enabled devices.

The applications have been fully tested on Samsung, Nokia, Motorola, Sony Ericsson, Siemens, Sagem, Sendo, Sharp & Panasonic devices at present. However, the applications will work on all Java CLDC 1.x / MIDP 1.0 and above devices.

The applications operate by creating a “web” connection to the backend servers. The applications are not concerned with how the device makes that connection or whether it uses 2.5G or 3G connectivity. Indeed the applications will also work with GSM dial up connections if 2.5G is not available. However, Java is rarely present on devices with just dial up capabilities alone.

Again, since the applications are operating inside the Java sandbox the underlying protocols and transport mechanisms are hidden and are provided via standard JSR implementations. The applications use the HTTP Connection inside the Java environment to make the best possible connection (2.5G or 3G).

All Java MIDP-1.0 devices must implement HTTP at a minimum to be compliant with the J2ME specification. Therefore all Java enabled phones must be capable of making an HTTP connection. For example WAP has been around for a long time and the advent of Java applications on the devices have taken advantage of this connectivity.