Integration Manual
Table Of Contents
- Document Information
- Contents
- 1 System description
- 1.1 Overview
- 1.2 Architecture
- 1.3 Pin-out
- 1.4 Operating modes
- 1.5 Power management
- 1.6 System functions
- 1.7 RF connection
- 1.8 (U)SIM interface
- 1.9 Serial communication
- 1.9.1 Serial interfaces configuration
- 1.9.2 Asynchronous serial interface (UART)
- 1.9.2.1 UART features
- 1.9.2.2 UART signal behavior
- 1.9.2.3 UART and power-saving
- 1.9.2.4 UART application circuits
- Providing the full RS-232 functionality (using the complete V.24 link)
- Providing the TxD, RxD, RTS, CTS and DTR lines only (not using the complete V.24 link)
- Providing the TxD, RxD, RTS and CTS lines only (not using the complete V.24 link)
- Providing the TxD and RxD lines only (not using the complete V24 link)
- Additional considerations
- 1.9.3 USB interface
- 1.9.4 SPI interface
- 1.9.5 MUX protocol (3GPP TS 27.010)
- 1.10 DDC (I2C) interface
- 1.11 Audio Interface
- 1.12 General Purpose Input/Output (GPIO)
- 1.13 Reserved pins (RSVD)
- 1.14 Schematic for LISA-U2 module integration
- 1.15 Approvals
- 1.15.1 European Conformance CE mark
- 1.15.2 US Federal Communications Commission notice
- 1.15.3 Innovation, Science, Economic Development Canada notice
- 1.15.4 Australian Regulatory Compliance Mark
- 1.15.5 ICASA Certification
- 1.15.6 KCC Certification
- 1.15.7 ANATEL Certification
- 1.15.8 CCC Certification
- 1.15.9 Giteki Certification
- 2 Design-In
- 3 Features description
- 3.1 Network indication
- 3.2 Antenna detection
- 3.3 Jamming Detection
- 3.4 TCP/IP and UDP/IP
- 3.5 FTP
- 3.6 HTTP
- 3.7 SSL/TLS
- 3.8 Dual stack IPv4/IPv6
- 3.9 AssistNow clients and GNSS integration
- 3.10 Hybrid positioning and CellLocate®
- 3.11 Control Plane Aiding / Location Services (LCS)
- 3.12 Firmware update Over AT (FOAT)
- 3.13 Firmware update Over the Air (FOTA)
- 3.14 In-Band modem (eCall / ERA-GLONASS)
- 3.15 SIM Access Profile (SAP)
- 3.16 Smart Temperature Management
- 3.17 Bearer Independent Protocol
- 3.18 Multi-Level Precedence and Pre-emption Service
- 3.19 Network Friendly Mode
- 3.20 Power saving
- 4 Handling and soldering
- 5 Product Testing
- Appendix
- A Migration from LISA-U1 to LISA-U2 series
- A.1 Checklist for migration
- A.2 Software migration
- A.2.1 Software migration from LISA-U1 series to LISA-U2 series modules
- A.3 Hardware migration
- A.3.1 Hardware migration from LISA-U1 series to LISA-U2 series modules
- A.3.2 Pin-out comparison LISA-U1 series vs. LISA-U2 series
- A.3.3 Layout comparison LISA-U1 series vs. LISA-U2 series
- B Glossary
- Related documents
- Revision history
- Contact
LISA-U2 series - System Integration Manual
UBX-13001118 - R25 Features description Page 145 of 182
LISA-U2 modules support the Direct Link mode for TCP and UDP sockets. Sockets can be set in Direct
Link mode to establish a transparent end-to-end communication with an already connected TCP or
UDP socket via the serial interface. In Direct Link mode, data sent to the serial interface from an
external application processor is forwarded to the network and vice-versa.
To avoid data loss while using Direct Link, enable HW flow control on the serial interface.
3.4.1 Multiple PDP contexts and sockets
Two PDP context types are defined:
“external” PDP context: IP packets are built by the DTE, the MT’s IP instance only runs the IP relay
function
“internal” PDP context: the PDP context (relying on the MT’s TCP/IP stack) is configured,
established and handled via the data connection management packet switched data commands
described in u-blox AT commands manual [2]
Multiple PDP contexts are supported. The DTE can access these PDP contexts either alternatively
through the physical serial port, or simultaneously through the virtual serial ports of the multiplexer
(multiplexing mode MUX), with the following constraints:
Using the MT’s embedded TCP/IP stack, only 1 internal PDP context is supported. This IP instance
supports up to 7 sockets
Using only external PDP contexts, it is possible to have at most 3 IP instances (with 3 different IP
addresses) simultaneously. If in addition the internal PDP context is used, at most 2 external PDP
contexts can be activated
Secondary PDP contexts (PDP contexts sharing the IP address of a primary PDP context) are also
supported. Traffic Flow Filters for such secondary contexts shall be specified according to 3GPP TS
23.060 [18].
At most 2 secondary PDP contexts can be activated, since the maximum number of PDP contexts,
both normal and secondary, is always 3.
3.5 FTP
LISA-U2 modules support the File Transfer Protocol and Secure 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 [2].
FTP files can also be transferred using the FTP Direct Link:
FTP download: the data coming from the FTP server is forwarded to the application processor via
the serial interface (for FTP without Direct Link mode, the data is always stored in the module’s
FFS)
FTP upload: the data coming from the application processor via the serial interface is forwarded
to the FTP server (for FTP without Direct Link mode, the data is read from the module’s FFS)
When Direct Link is used for a FTP file transfer, only the file content pass through the serial interface,
whereas all the FTP commands handling is managed internally by the FTP application.
Due to the limited size of the FFS module, FTP direct link is useful to transfer files with a size greater
than the FFS.
To avoid data loss while using direct link, enable HW flow control on the serial interface.