Integration Manual
Table Of Contents
- Contents
- 1 System description
- 1.1 Overview
- 1.2 Architecture
- 1.3 Pin-out
- 1.4 Operating modes
- 1.5 Supply interfaces
- 1.5.1 Module supply input (VCC)
- 1.5.1.1 VCC supply requirements
- 1.5.1.2 VCC current consumption in 2G connected mode
- 1.5.1.3 VCC current consumption in 3G connected mode
- 1.5.1.4 VCC current consumption in LTE connected mode
- 1.5.1.5 VCC current consumption in cyclic low power idle mode / active mode
- 1.5.1.6 VCC current consumption in fixed active mode
- 1.5.2 Generic digital interfaces supply output (V_INT)
- 1.5.1 Module supply input (VCC)
- 1.6 System function interfaces
- 1.7 Antenna interfaces
- 1.8 SIM interfaces
- 1.9 Data communication interfaces
- 1.10 eMMC interface
- 1.11 Digital Audio interfaces
- 1.12 ADC interfaces
- 1.13 General Purpose Input/Output
- 1.14 Reserved pins (RSVD)
- 1.15 System features
- 1.15.1 Network indication
- 1.15.2 Jamming detection
- 1.15.3 IP modes of operation
- 1.15.4 Dual stack IPv4 and IPv6
- 1.15.5 Embedded TCP/IP and UDP/IP
- 1.15.6 Embedded FTP and FTPS
- 1.15.7 Embedded HTTP and HTTPS
- 1.15.8 SSL and TLS
- 1.15.9 Firmware update Over AT (FOAT)
- 1.15.10 Firmware update Over The Air (FOTA)
- 1.15.11 Power Saving
- 2 Design-in
- 2.1 Overview
- 2.2 Supply interfaces
- 2.2.1 Module supply (VCC)
- 2.2.1.1 General guidelines for VCC supply circuit selection and design
- 2.2.1.2 Guidelines for VCC supply circuit design using a switching regulator
- 2.2.1.3 Guidelines for VCC supply circuit design using a LDO linear regulator
- 2.2.1.4 Guidelines for VCC supply circuit design using a rechargeable battery
- 2.2.1.5 Guidelines for VCC supply circuit design using a primary battery
- 2.2.1.6 Additional guidelines for VCC supply circuit design
- 2.2.1.7 Guidelines for the external battery charging circuit
- 2.2.1.8 Guidelines for external charging and power path management circuit
- 2.2.1.9 Guidelines for removing VCC supply
- 2.2.1.10 Guidelines for VCC supply layout design
- 2.2.1.11 Guidelines for grounding layout design
- 2.2.2 Generic digital interfaces supply output (V_INT)
- 2.2.1 Module supply (VCC)
- 2.3 System functions interfaces
- 2.4 Antenna interface
- 2.5 SIM interfaces
- 2.6 Data communication interfaces
- 2.7 eMMC interface
- 2.8 Digital Audio interface
- 2.9 ADC interfaces
- 2.10 General Purpose Input/Output
- 2.11 Reserved pins (RSVD)
- 2.12 Module placement
- 2.13 Module footprint and paste mask
- 2.14 Thermal guidelines
- 2.15 Design-in checklist
- 3 Handling and soldering
- 4 Approvals
- 5 Product testing
- 6 FCC Notes
- Appendix
- Glossary
- Related documents
- Revision history
- Contact
TOBY-L3 series - System Integration Manual
TSD-19090601 - R13 System Integration Manual Page 58 of 143
For more details about the embedded FTP and FTPS functionalities, see the TOBY-L3 series AT commands
manual [2].
1.15.7 Embedded HTTP and HTTPS
TOBY-L3 series modules provide the embedded Hyper-Text Transfer Protocol (HTTP) and Hyper-Text
Transfer Protocol Secure (HTTPS) services via AT commands for sending requests to a remote HTTP(HTTPS)
server, receiving the server response and transparently storing it in the module’s Flash File System, it can
also be transferred the HTTP or HTTPS data between the remote HTTP or HTTPS server and the external
application processor via serial interfaces (USB, UART) in HTTP or HTTPS Direct link mode:
HTTP (or HTTPS) download: data coming from the HTTP or HTTPS server is forwarded to the host
processor via USB / UART serial interfaces (for HTTP or HTTPS without Direct Link mode, the data is
always stored in the module’s Flash File System)
HTTP (or HTTPS) upload: data coming from the host processor via USB / UART serial interface is
forwarded to the HTTP or HTTPS server (for HTTP or HTTPS without Direct Link mode, the data is read
from the module’s Flash File System)
When Direct Link is used for a HTTP or HTTPS file transfer, only the file content pass through USB / UART
serial interface, whereas all the HTTP or HTTPS commands handling is managed internally by the embedded
HTTP(S) application.
For more details about the embedded HTTP and HTTPS functionalities, see the TOBY-L3 series AT commands
manual [2].
1.15.8 SSL and TLS
TOBY-L3 series modules support the Secure Socket Layer (SSL) / Transport Layer Security (TLS) with
certificate key sizes up to 4096 bits to provide security over the FTP and HTTP protocols.
The SSL/TLS support provides different connection security aspects:
Server authentication: use of the server certificate verification against a specific trusted certificate or a
trusted certificate list
Client authentication: use of the client certificate and the corresponding private key
Data security and integrity: data encryption and Hash Message Authentication Code (HMAC) generation
The security aspects used during a connection depend on the SSL/TLS configuration and features supported.
For a complete list of supported SSL/TLS configurations and settings see the TOBY-L3 series AT commands
manual [2].
1.15.9 Firmware update Over AT (FOAT)
This feature allows upgrading the module firmware over USB / UART serial interfaces, using AT commands.