Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 ユーザーズマニュアル
製品コード
6203
Java User’s Guide
5.12 Performance
39
wm_java_usersguide_v19
Page 36 of 109
2012-01-27
Confidential / Released
5.12.3.1
Plain Serial Interface
Scenario: A device is connected to ASC0 (refer to
). The Java application must
handle data input and output streams. A simple Java application (with only one thread) which
loops incoming data directly to output, reaches data rates up to 180kbit/s. Test conditions:
hardware flow control enabled (<autorts> and <autocts>), 8N1, and baud rate on ASC0 set to
230kbaud (
loops incoming data directly to output, reaches data rates up to 180kbit/s. Test conditions:
hardware flow control enabled (<autorts> and <autocts>), 8N1, and baud rate on ASC0 set to
230kbaud (
theoretical maximum: 184kbit/s net data rate).
Figure 17: Scenario for testing data rates on ASC1
5.12.3.2
Voice Call in Parallel
, but with a voice call added. The application reflects in-
coming data directly to output and, additionally, handles an incoming voice call. The data rates
are also up to 180kbit/s. Test conditions: same as in
are also up to 180kbit/s. Test conditions: same as in
.
Figure 18: Scenario for testing data rates on ASC1 with a voice call in parallel
5.12.3.3
Scenarios with GPRS/EGDE Connection
The biggest challenges to the module performance are setting up a GPRS/EDGE connection,
receiving data on javax.microedition.io interfaces and sending or receiving the data on the
RS232 API with the help of a Java application.
receiving data on javax.microedition.io interfaces and sending or receiving the data on the
RS232 API with the help of a Java application.