Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 用户手册
产品代码
6203
Java User’s Guide
5.2 Remote SIM Access
39
wm_java_usersguide_v19
Page 28 of 109
2012-01-27
Confidential / Released
5.2
Remote SIM Access
While Remote SIM Access (RSA) is normally closely coupled with the GSM 07.10 multiplexer
there are some things to keep in mind when using it with Java.
•
there are some things to keep in mind when using it with Java.
•
Java must not be started when RSA and/or the GSM 07.10 multiplexer is activated.
•
When activating the RSA mode (AT^SRSA) via a Java AT Command channel while Java
is running the parameter <muxChan> of the AT^SRSA command is ignored and RSA is
activated on the channel where the command was issued. The Input- and Outputstream
can then be used to transfer RSA protocol data.
is running the parameter <muxChan> of the AT^SRSA command is ignored and RSA is
activated on the channel where the command was issued. The Input- and Outputstream
can then be used to transfer RSA protocol data.
5.3
Power Saving
The module supports several power saving modes which can be configured by the AT com-
mand AT+CFUN
mand AT+CFUN
. Power saving affects the Java application in two ways. First, it limits ac-
cess to the serial interface (RS-232-API) and the GPIO pins. Second, power saving efficiency
is directly influenced by the way a Java application is programmed.
is directly influenced by the way a Java application is programmed.
Java hardware access limitations:
•
•
In NON-CYCLIC SLEEP mode (cfun=0) the serial interface cannot be accessed. Toggling
RTS does end NON-CYCLIC SLEEP mode. In CYCLIC SLEEP mode (CFUN=7 or 9) the
serial interface can be used with hardware flow control (CTS/RTS).
RTS does end NON-CYCLIC SLEEP mode. In CYCLIC SLEEP mode (CFUN=7 or 9) the
serial interface can be used with hardware flow control (CTS/RTS).
•
In all SLEEP modes the GPIO polling frequency is reduced so that only signal changes
which are less than 0.2Hz can be detected properly. Furthermore, the signal must be con-
stant for at least 2.7s to detect any changes. For further details see AT^SCPOL in
which are less than 0.2Hz can be detected properly. Furthermore, the signal must be con-
stant for at least 2.7s to detect any changes. For further details see AT^SCPOL in
or
.
Java power saving efficiency:
•
•
As long as any Java thread is active, power consumption cannot be reduced, regardless
whether any SLEEP mode has been activated or not. A Java application designed to be
power efficient should not have any unnecessarily active threads (e.g. no busy loops).
Threads waiting in a blocking method (e.g. read) do not hinder power saving.
whether any SLEEP mode has been activated or not. A Java application designed to be
power efficient should not have any unnecessarily active threads (e.g. no busy loops).
Threads waiting in a blocking method (e.g. read) do not hinder power saving.
•
When using networking functionality close all connectors and hang-up the bearer manually
(using ATH for circuit switched connections) every time you intend to reduce power con-
sumption. Disable the network idle timeout (=0).
(using ATH for circuit switched connections) every time you intend to reduce power con-
sumption. Disable the network idle timeout (=0).
When going to low power mode there always might be a transition time of around 10s till low
power consumption state is reached.
power consumption state is reached.
5.3.1
Power Saving While GPRS is Active
It is also possible that the module saves power while the GPRS PDP context is activated but
without ongoing data traffic. To save power in GPRS mode it is required to enable a power sav-
ing mode (e.g. AT+CFUN=9) and put all threads into a sleep state. Also, data connections shall
be in a blocking read (serial interface and/or GPRS connections).
without ongoing data traffic. To save power in GPRS mode it is required to enable a power sav-
ing mode (e.g. AT+CFUN=9) and put all threads into a sleep state. Also, data connections shall
be in a blocking read (serial interface and/or GPRS connections).