Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 用户手册

8.12 Incremental OTAP



wm_java_usersguide_v19

Page 53 of 109

2012-01-27

Confidential / Released

3. Prepare the http server. The server must be accessible from your device over TCP/IP. That

means there is a route from your device over the air interface to the http server and back.
When in doubt, write a small Java application using the httpConnection Interface to test it.

4. Prepare the JAR and JAD files which are to be loaded over the air. Make sure that these

files conform to the requirements listed in 

 and that they represent a valid appli-

cation which can be started by AT^SJRA.

5. Put the files (JAR and JAD) on the http Server. The files can either be publicly available or

protected through basic authentication. When in doubt try to download the files from the
server by using a common Web browser on a PC, which can reach your http server over
TCP/IP.

6. Prepare the SM sender. The sender must be able to send SMs, which conform to 

, to your device. When in doubt try to send “normal” SMs to your device which can than

be read out from the AT command interface.

7. Test with a local device. Send a suitable short message to your device, which completes

the necessary parameter, sets and starts the operation. The operation is finished when the
device reboots. You can now check the content of the file system and if the correct jar and
jad files were loaded into the correct location.

8. Analyze errors. If the above test failed, looking at your device’s behavior and your http serv-

ers access log can give you a hint as to what went wrong:
-

f the device did not terminate the running Java application and did not reboot, not even
after the safety timeout, either your SM was not understood (probably in the wrong for-
mat) or it did not properly authenticate (probably used the wrong password) or your
parameter set is incomplete for the requested operation.

- If the device terminated the running Java application, but did not access your http server,

and rebooted after the safety timeout, there were most likely some problems when open-
ing the network connection. Check your network parameters.

- If the device downloaded the jad and possibly even the jar file but then rebooted without

saving them in the file system, most likely one of the errors outlined in 

occurred. These are also the only errors which will return a response. They are posted to
the http server if the jad file contains the required URL.

9. Start update of remote devices. If you were able to successfully update your local device,

which is hopefully a mirror of all your remote devices, you can start the update of all other
devices.

As an extension of the standard OTAP procedure the Java Application can be provisioned in 
an incremental way to save some bandwidth when downloading a new version to a large num-
ber of deployed devices.

In order to make use of this feature the application has to be developed in a modular way. That 
means that the classes have to be split up into multiple jar files with corresponding jad files. 
There can be only one jar file containing the "midlet" class which is called the midlet, all the 
others are called liblets.

A liblets jar and jad file have to fullfil the same requirements as a midlets:
•

The attributes name, version and vendor have to exist in both files with the same value

•

The jar size needs to be present in the jad file and has to correspond with the jars file size

•

The jar URL has to be present in the jad file and point to a valid location

The attribute names are slightly different.