Definition
PSM (Power Saving Mode) is a low-power state defined by 3GPP for IoT terminals: after completing a data transmission, the terminal enters an idle state. After the network-allocated Active Time, if there is no further activity, it enters deep PSM sleep. At this time, the UE no longer listens for paging, the radio is turned off, and the current can drop to the microampere level. The terminal still maintains EPS/5GS attachment to the core network, and the context (including IP address and bearer information) is usually retained by the network until the TAU/Registration period expires or explicit detachment occurs. For devices holding IoT SIM cards, PSM is a key method to extend battery life in battery-powered scenarios, but it sacrifices the capability of being "always reachable."
"Session persistence" in engineering often refers to whether the TCP/UDP sessions or NAT mappings seen on the platform side remain valid when the terminal does not send packets for a long time. During PSM, the terminal does not exchange data; firewalls on the public path, carrier NATs, and customer-side routers may reclaim mappings due to timeout, causing the first packet to fail or requiring reconnection when the terminal wakes up. Therefore, session persistence strategies must be designed in conjunction with PSM timers and business heartbeat intervals, rather than relying solely on the intuition that "the SIM is always online."
Active Time, T3412 (LTE), or the equivalent registration update timer together determine how often the terminal must wake up to perform a mobility management update. If the IoT SIM card's data plan limits registration frequency or signaling costs, an overly short TAU cycle may lead to unexpected bills, requiring alignment between business and technology considerations.
Technical key points
PSM entry and exit are driven by the timer negotiation results in NAS signaling. The module requests T3324 (Active Time) and T3412 extension values from the network, and the network can accept, degrade, or reject some of the requests. Different operators support different maximum PSM durations. NB-IoT networks generally allow more aggressive parameters than LTE smartphones. While in PSM, the terminal is not paged, and downlink data can only be delivered when the terminal next initiates TAU or a service, unless the network has specific wake-up mechanisms (such as extended power-saving features in coordination with edge caching, still assuming the terminal wakes up).
The difference from eDRX is: eDRX still periodically listens for paging, whereas PSM basically cuts off downlink reachability. When mixed use occurs, it is usually first listening during the eDRX window, then entering PSM. 5G RedCap and NB-IoT differ slightly in the naming of power-saving parameters, but the IoT SIM card connection management logic is similar, and the dual registration behavior in 5GS and EPS should be referred to in the corresponding module manual.
The HSS/UDM user template to which the IoT SIM card IMSI belongs can carry default timer recommendations. The network may override the terminal request, causing discrepancies between laboratory and mass-production behaviors. It is recommended to record a negotiation result snapshot during network registration in the target deployment country.
IoT SIM cards and platform configuration
Card operators can preconfigure APNs and default timer profiles for industry cards so that terminals obtain more consistent PSM behavior after attaching. If the platform uses long connection MQTT, the Keepalive interval should be set to less than the minimum NAT timeout on the path, while being greater than the terminal's expected wake-up cycle, or reconnect immediately after wake-up. For UDP reporting businesses, a "wake-up handshake packet" can be defined at the application layer to rebuild the platform-side state machine.
When using VPDN or private networks, the enterprise-side firewall session timeout is often shorter than that of the carrier core network, so the idle timeout needs to be increased accordingly or changed to heartbeats initiated by the terminal. The connection management platform should support querying the last TAU time and traffic bursts by card number, to help determine whether PSM is working as expected.
Batch OTA upgrades need to avoid all devices on the entire network exiting PSM at the same time, otherwise it can cause a registration storm; it is recommended to use scheduled and grouped wake-ups with limited download speed. IoT SIM cards can cooperate with speed limit policies and dedicated upgrade APNs.
Operation and Troubleshooting
Common complaints are "devices are offline for days" and "downlink never arrives." First, confirm whether the terminal has really entered PSM rather than losing network: compare the module's CEREG status and the last active time at the base station. If TAU fails, causing implicit detachment, the terminal will obtain a new IP when it comes online again, and if the platform associates with the old IP, it will be considered an anomaly. Secondly, check whether TAU is blocked due to SIM regional lock or balance suspension, which may appear similar to excessively long PSM sleep.
On the packet capturing side, traffic is only visible in the terminal's transmission window, making remote diagnosis difficult. Lightweight logging of the last TAU result and the next expected wake-up time should be added on the device side. For occasional failure to wake up, check whether the module reduced transmission power under low battery voltage, causing TAU failure.
When troubleshooting with the operator, providing the ICCID, approximate time period, and cell TAC can shorten the signaling tracking time. If the customer has modified the PSM parameters on their own without performing field tests, it is recommended to revert to the template recommended by the card supplier and then reproduce the issue.
Compliance and Security
PSM reduces the terminal's exposure, and during long sleep periods, security patch pushes cannot be received in a timely manner. The architecture should allow certificate updates and vulnerability fixes to be prioritized after wake-up. Certain critical infrastructure standards require a minimum contact interval; the project needs to verify whether the PSM parameters meet regulatory minimum requirements. When user data crosses borders, long-sleep devices may move across countries, requiring assessment of roaming permissions in conjunction with location strategy.
For auditing, records of terminal registration, TAU successes, and failures should be retained to restore the timeline after a security incident.
Use Cases
Battery-powered devices with reporting intervals in hours or days, such as smart water and gas meters, environmental monitoring sensors, disposable tracking tags, and agricultural moisture nodes, generally use PSM. Fixed power devices that require extreme energy saving, such as streetlight controllers, can also enter PSM at night and only retain scheduled wake-ups. For vehicles requiring high real-time performance, PSM is usually disabled or only used for submodules after the engine is turned off.
SimtoLink provides IoT SIM card lifecycle management, power-saving parameter consultation, and connection quality reports, helping customers complete joint acceptance of PSM and session retention before mass deployment.