Cinterion
®
EHS6 AT Command Set
EHS6_ATC_V03.001
15/12/3
Confidential / Released
Page 226 of 513
Socket service used with UDP protocol
The significant differences between the TCP and UDP protocols imply that UDP sometimes requires particular
procedures or even specific parameters. Details on how to handle UDP services can be found in extra notes or
are included in the general parameter descriptions.
The EHS6 offers two kinds of Socket service with UDP protocol.
•
UDP Client:
Intended for connections to a given remote host. In this case the IP address and the UDP port of
the remote host are set as a fixed parameter in the service profile. The UDP Client can use Transparent Mode
and Non-Transparent Mode.
•
Non-Transparent UDP Endpoint:
IP address and UDP port of the remote hosts are handled in each read
(
) and write (
) request. This enables the host application to communicate with different
remote hosts.
See example in Section
Secure connection (TLS)
All services support Transport Layer Security (TLS), except UDP client and Socket Listener. To set TLS simply
add "s" to the address type, such as socktcps, ftps, https, smtps. For details see
parameter "address". To create customized TLS certificates please refer to
. The processes
of switching on/off certificate verification and adding/removing certificates for socktcps, ftps and smtps are same
as those of https. Please refer to the description for https in
. The certificates should be
installed on the FFS, and the boundary is determined by the size of FFS.
Two design strategies for using Internet Service AT commands - URC mode or polling mode:
The EHS6 offers two modes of controlling an Internet session opened with
. To select the mode that
best suits the preferences of your application design use the
command, parameter "Tcp/WithURCs"
(refer to
• URC mode (delivery default):
The progress of an Internet session is URC driven. The URCs notify the host whether data can be sent or
received, whether data transfer has completed, whether the service can be closed or whether an error has
occurred. This mechanism eliminates the need to poll the service until the necessary progress information is
received.
To enable the URC mode select:
="Tcp/WithURCs",on.
• Polling mode:
In polling mode, the presentation of URCs related to the Internet Services is disabled. The host is responsible
to retrieve all the status information needed for controlling the Internet session. This is done by polling, where
the host application keeps sending the commands
,
To enable the polling mode select:
="Tcp/WithURCs",off.
The disabled URCs are the following: "
" URC, "
" URC and "
" URC for parameter
=0 (Internet service events), but not for
=1 or 2 (needed for Socket listener and always
enabled).
Maximum number of profiles defined / used:
• Up to 6 connection profiles can be created (with
).
• Up to 10 service profiles can be created (with
• A connection profile can be created on one interface and then viewed or changed on all other interfaces.
• A service profile can be used only on one interface at a time:
- Service profiles can only be opened on the interface where they have been defined with
.
- Accordingly, on each interface the read commands
? and
? deliver full status informa-
tion for the service profiles configured / opened on this interface, while service profiles related to other
interfaces are only listed by
and service type name (=
value "srv-
Type") without any status parameters.
- Changes to a service profile are allowed only on the same interface where it was created, trying to change
it on another interface is denied with "+CME ERROR: invalid index". If queried with the read command
? the entire profile is returned on the interface where the service profile was created, while on all
other interfaces only the service type of the profile is stated.