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

产品代码
6203
下载
页码 109
Java User’s Guide
8.9 OTAP Tracer
54
wm_java_usersguide_v19
Page 52 of 109
2012-01-27
Confidential / Released
In some networking infrastructures there may be an interference between OTAP started on
a circuit-switched bearer (CS) and an existing CS call. As a result, an OTAP failure may
occur. 
If such a scenario is likely to happen in your application environment we recommend that a
delay of around 15s be set between hanging up the CS call and starting OTAP over CSD.
This means that you cannot use the standard SM trigger for OTAP because there are no
15s time when shutting down the running Java application. Instead, trigger OTAP from your
application (e.g. receive trigger SM from application, hang up CS call, wait 15s, start OTAP
by AT command).
In emergency cases (when your Java application is malfunctioning) you can still use the SM
trigger for OTAP but you probably need to try several times to make sure that there is no
CS call at the time OTAP starts over CSD.
8.9
OTAP Tracer
For easy debugging of the OTAP scenario, the OTAP procedure can be traced over the serial 
interface. The trace output shows details of the OTAP procedure and the used parameters. To 
enable the OTAP trace output use the AT command AT^SCFG, e.g.
AT^SCFG=Trace/Syslog/OTAP,1
The serial interface on which you issue this command is then exclusively used for the OTAP 
tracer. All other functionality which is normally present (AT commands or CommConnection 
and System.out in Java) is not available when the tracer is on.
This feature is intended to be used during development phase and not in deployed devices.
8.10
Security
Java Security as described in 
 also has consequences for OTAP. If the module is in 
secured mode the MIDlet signature is also relevant to the OTAP procedure. This means:
If the application is an unsigned version of an installed signed version of the same applica-
tion then status code 910 is returned.
If the applications signature does not match the module’s certificate then status code 909
is returned.
8.11
How To
This chapter is a step-by-step guide for using OTAP.
1. Do you need OTAP? Is there any chance that it might be necessary to update the Java
application, install a new one or delete it? It could be that device is in the field and you can-
not or do not want to update it over the serial line. If the answer is “yes” then read through
the following steps, if the answer is “no” then consider simply setting the OTAP SMS pass-
word to protect your system. Then you are finished with OTAP.
2. Take a look at the parameters (
), which control OTAP. You need to decide which
of them you want to allow to be changed over the air (by SMS) and which you do not. This
is mainly a question of security and what can fit into a short message. Then set the
“unchangeable” parameters with the AT command (AT^SJOTAP).