Cinterion
®
EHS6 AT Command Set
EHS6_ATC_V03.001 15/12/3
Confidential / Released
Page 225 of 513
Transparent Mode is activated with AT^SIST and then indicated by the "CONNECT" result code. The mode
eliminates the need for AT^SISW and AT^SISR read and write sequences.
• Non-Transparent Mode is packet oriented, i.e. data is transferred in separate packets. Maximum packet size
is 1500 bytes for TCP, 1460 bytes for UDP. To read and write data AT^SISW and AT^SISR sequences shall
be used. FTP, HTTP, SMTP employ Non-Transparent Mode, for Socket services it is optional.
To send or receive more than 1500 bytes, the read or write action shall be repeated until the data transfer has
completed. Each read or write action requires that the command response (of AT^SISR or AT^SISW) con-
firms that the service is ready to send or receive data. The read/write cycles can be controlled by URCs or
polling. For details see below, section "URC mode and polling mode".
To end an upload data stream set the <eodFlag> in the last AT^SISW command.
Listener services:
A listener is waiting for incoming remote client requests. EHS6 supports two listener types: Transparent TCP Lis-
tener and Standard TCP Listener.
After opening a listener with AT^SISO no "^SISW" URC appears. Instead, the "^SIS" URC with <urcCause>
"5" shows that the opened listener is ready and starts listening. Additionally, the service state can be verified with
AT^SISI which shows state "4" (Up - listening).
An incoming remote client request is indicated by the "^SIS" URC. For details please refer to Section 10.14,
Internet Service URC "^SIS", escpecially parameters <urcCause> and <urcInfoId>.
• Transparent TCP Listener:
- The Transparent TCP Listener can accept 1 remote client. The connection to the remote client does not
need an additional service profile, as it uses the Transparent TCP Listener instance, i.e. it is assigned to
the <srvProfileId> of the Transparent Listener.
- To define a listener service profile as Transparent TCP Listener the "etx" parameter is mandatory in the
address. See AT^SISS.
- AT^SISS allows some specific options for the Transparent TCP Listener service, such as:
- Autoconnect configured with parameters "autoconnect", "connecttimeout", "addrfilter";
- If autoconnect is enabled an incoming remote client is indicated by the "^SIS" URC with <urcCause> "3"
(Transparent) and <urcInfoId> "1" (= autoconnect enabled). The request is automatically accepted, i.e.
the service instantly changes to transparent data mode (indicated by "CONNECT" result code).
- If autoconnect is disabled, the remote client connect request is indicated by the "^SIS" URC with <urc-
Cause> "3" (Transparent) and <urcInfoId> "0" (= autoconnect disabled). The request can be accepted
with AT^SISO and AT^SIST, or rejected with AT^SISH. In all cases the same <srvProfileId> shall
be used.
If a remote client connection request is not accepted within the configured 'connecttimeout', it will be
rejected automatically, and the URC "^SIS" is sent with <urcCause> set to '4'.
- As long as one remote client is connected all other remote client requests are rejected automatically with-
out displaying the "^SIS" URC. The
<rejCounter> in the response of the AT^SISO read command indi-
cates such hidden rejects.
- AT^SISH disconnects a remote client, without closing the service, allowing the Transparent TCP Listener
to wait for the next remote client.
AT^SISC both disconnects the remote client and shuts down the Transparent TCP Listener.
- An example can be found in Section 10.14, Internet Service URC "^SIS" and Section 10.15.4, Transparent
TCP Listener: Accepting / Rejecting Incoming Remote Client
• Standard TCP Listener:
- The Standard Listener can accept several remote clients. Each incoming remote client connection request
is dynamically assigned to the next free service profile indicated as <srvProfileId> within the "^SIS"
URC. <urcCause> in the "^SIS" URC equals "1" (Non-Transparent). The dynamically assigned
<srvProfileId> shall be used to accept the remote client with AT^SISO, or to reject it with AT^SISC.
The number of acceptable remote clients depends on the number of free service profiles.
- To transfer data it is possible to proceed with Transparent Mode using AT^SIST, or Non-Transparent
Mode using AT^SISR and AT^SISW read / write sequences.
- An example can be found in Section 10.15.2, Configuring Non-Transparent Listener.
To Next Page
Loading...
