Specifications
Table Of Contents
- Contents
- Tables
- Figures
- 1 Introduction
- 2 Interface Characteristics
- 2.1 Application Interface
- 2.2 RF Antenna Interface
- 2.3 GNSS Antenna Interface
- 2.4 Sample Application
- 3 Operating Characteristics
- 4 Mechanical Dimensions, Mounting and Packaging
- 5 Regulatory and Type Approval Information
- 6 Document Information
- 7 Appendix
Cinterion
®
PLSx3 Hardware Interface Description
2.1 Application Interface
60
t PLSx3_HID_v01.003 2021-03-12
Public / Released
Page 28 of 121
2.1.3.1 Reducing Power Consumption
While a USB connection is active, the module will never switch into SLEEP mode. Only if the
USB interface is in Suspended state or Detached (i.e., VUSB_IN = 0) is the module able to
switch into SLEEP mode thereby saving power. There are two possibilities to enable power re-
duction mechanisms:
• Recommended implementation of USB Suspend/Resume/Remote Wakeup:
The USB host should be able to bring its USB interface into the Suspended state as
described in the “Universal Serial Bus Specification Revision 2.0“
1
. For this functionality to
work, the VUSB_IN line should always be kept enabled. On incoming calls and other events
PLSx3 will then generate a Remote Wakeup request to resume the USB host controller.
See also [3] (USB Specification Revision 2.0, Section 10.2.7, p.282):
"If USB System wishes to place the bus in the Suspended state, it commands the Host Con-
troller to stop all bus traffic, including SOFs. This causes all USB devices to enter the Sus-
pended state. In this state, the USB System may enable the Host Controller to respond to
bus wakeup events. This allows the Host Controller to respond to bus wakeup signaling to
restart the host system."
• Implementation for legacy USB applications not supporting USB Suspend/Resume:
As an alternative to the regular USB suspend and resume mechanism it is possible to
employ the RING0 line to wake up the host application in case of incoming calls or events
signalized by URCs while the USB interface is in Detached state (i.e., VUSB_IN = 0). Every
wakeup event will force a new USB enumeration. Therefore, the external application has to
carefully consider the enumeration timings to avoid loosing any signaled events. For details
on this host wakeup functionality see Section 2.1.10.4. To prevent existing data call con-
nections from being disconnected while the USB interface is in detached state (i.e., VUS-
B_IN=0) it is possible to call AT&D0, thus ignoring the status of the DTR line (see also [1]).
1. The specification is ready for download on http://www.usb.org/developers/docs/