> 8.2 | OTAP Overview

> To use OTAP, the developer needs, apart from the device fitted with the Java enabled module, an http server, which is accessible over a TCP/IP connection either over GPRS or CSD, and an SMS sender, which can send Class1, PID $7d short messages. This is the PID reserved for a module’s data download.
> Figure 19: OTAP Overview
> The Java Application Server (http Server) contains the .jar and the .jad file to be loaded on the device. Access to these files can be protected by http basic authentication.
> The OTAP Controller (SMS Sender) controls the OTAP operations. It sends SMs, with or without additional parameters, to the devices that are to be operated. These devices then try to contact the http server and download new application data from it. The OTAP Controller will not get any response about the result of the operation. Optionally the server might get a result response over http.
> There are two types of OTAP operations:

> • | Install/Update: A new JAR and JAD file are downloaded and installed.

> • | Delete: A complete application (.jar, .jad, all application data and its directory) is deleted.