LEON-G100 / LEON-G200 - System Integration Manual
GSM.G1-HW-09002-G3
Preliminary
Feature description
Page 105 of 125
3.5
FTP
LEON-G100 / LEON-G200 modules support the File Transfer Protocol functionalities via AT commands. Files are
read and stored in the local file system of the module. For more details about AT commands see the
u-blox AT
Commands Manual
3.6
HTTP
HTTP client is implemented in LEON. HEAD, GET, POST, DELETE and PUT operations are available. The file size to
be uploaded / downloaded depends on the free space available in the local file system (FFS) at the moment of
the operation. Up to 4 HTTP client contexts to be used simultaneously.
For more details about AT commands see the
u-blox AT Commands Manual
3.7
SMTP
LEON-G100 / LEON-G200 modules supports SMTP client functionalities. It is possible to specify the common
parameters (e.g. server data, authentication method, etc.) can be specified, to send an email to a SMTP server.
Emails can be sent with or without attachment. Attachments are store in the local module file system.
For more details about AT commands see the
u-blox AT Commands Manual
3.8
GPS
The LEON-G100 / LEON-G200 modules allow a simple and fast connection with the u-blox GPS modules (u-blox
5 family and above). Via the DDC bus it’s possible to communicate and exchange data, while the available GPIOs
can handle the GPS device power on/off.
For information about implementing u-blox GPS with LEON-G100 / LEON-G200 modules, including using u-blox’
AssistNow Assisted GPS (A-GPS) service see the
GPS Integration Application Note
3.9
Jamming detection
In real network situations modules can experience various kind of out-of-coverage conditions: limited service
conditions when roaming to networks not supporting the specific SIM, limited service in cells which are not
suitable or barred due to operators’ choices, no cell condition when moving to poorly served or highly interfered
areas. In the latter case, interference can be artificially injected in the environment by a noise generator covering
a given spectrum, thus obscuring the operator’s carriers entitled to give access to the GSM service.
The Jamming Detection Feature detects such “artificial” interference and reports the start and stop of such
condition to the client, which can react appropriately by e.g. switching off the radio transceiver in order to
reduce the power consumption and monitoring the environment at constant periods.
The feature consists in detecting, at radio resource level, an anomalous source of interference and signaling it to
the client with an unsolicited indication when the detection is entered or released. The jamming condition occurs
when:
The module has lost synchronization with the serving cell and cannot select any other cell
The band scan reveals at least n carriers with power level equal or higher than threshold
On all such carriers, no synchronization is possible
The number of minimum disturbing carriers and the power level threshold can be configured by the client by
using the AT+UCD command [2].
The jamming condition is cleared when any of the above mentioned statements does not hold.
The congestion (i.e. jamming) detection feature can be enabled and configured by the +UCD AT command (for
more details refer to the
u-blox AT Commands Manual
