Description
Short Message Network Storage (SMNS) is a supplementary service defined in 3GPP TS 22.142 and TS 22.942 that enables the network to store short messages that a subscriber has sent or received. This service provides a centralized, network-based repository for SMS messages, allowing subscribers to access their message history from any device and ensuring that messages are not lost if the device is lost, damaged, or replaced. It is particularly useful for users who need to keep records of important messages or for legal and compliance purposes.
The service operates by intercepting messages at the SMSC or a dedicated storage entity. When a message is sent or received by a subscriber with SMNS active, a copy is stored in the network storage. The storage can be configured to retain messages for a specified period, after which they may be automatically deleted. Subscribers can retrieve stored messages via various interfaces, such as a web portal, USSD, or a dedicated application. The storage may also support search and filtering capabilities, allowing users to find specific messages.
Key components include the SMSC, which forwards copies of messages to the storage entity, and the storage database itself, which may be integrated with the HLR or a separate server. The service requires synchronization with the subscriber's profile to determine which messages to store (e.g., all messages, only sent, only received, or based on criteria). The storage entity must ensure data integrity, security, and privacy, as messages may contain sensitive information. Access to stored messages is typically protected by authentication and authorization mechanisms.
From an operational perspective, SMNS can be offered as a value-added service by operators, often with tiered storage plans. It can also be integrated with other services like Short Message Filtering and Forwarding; for example, filtered messages might still be stored for review. The service is access-independent, working across 2G, 3G, 4G, and 5G networks. It leverages the existing SMS infrastructure and does not require modifications to the radio access network.
SMNS has been part of 3GPP specifications since Release 8 and has remained unchanged in its definition through Rel-19, indicating its stability and continued relevance. As messaging evolves with Rich Communication Services (RCS) and other IP-based messaging, network storage concepts may extend to those domains, but SMNS specifically addresses traditional SMS.
Purpose & Motivation
Short Message Network Storage was introduced to address the limitations of device-based message storage. Before its introduction, subscribers could only store messages on their devices, which had limited capacity and were vulnerable to loss if the device was lost or damaged. Network-based storage provides a reliable and scalable solution, ensuring that messages are preserved regardless of the device state. It also enables access to message history from multiple devices, which is increasingly important in a multi-device world.
The service solves the problem of message retention for legal, business, and personal reasons. For enterprises, it provides a centralized archive for compliance and auditing. For individuals, it offers peace of mind and convenience. Additionally, it can help operators reduce churn by offering a valuable service that differentiates their offerings.
Historically, as SMS became a primary communication method, the need for network storage grew. 3GPP standardized SMNS in Release 8 as part of the supplementary services for short message service. The service has not required updates, reflecting its well-defined scope. It continues to be relevant, especially in regions where SMS is still heavily used for business and personal communication.
What changed in its specifications
The latest release-to-release comparison of specifications that define Short Message Network Storage. Each summary describes the whole specification, not only this term.
Rel-9 added VAS4SMS, independent VAS-SMS provisioning, limited message forwarding, and auto-reply loop prevention.
Full comparison in TS 22.142 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Short Message Network Storage, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.142 vj00 | Value-added Services for SMS Requirements | Rel-19 read |
| TR 22.942 vj00 | SMS Value-Added Services Requirements | Rel-19 read |