Short Message Receipt

Description

Short Message Receipt (SMR) is a supplementary service defined in 3GPP TS 22.142 and described in the feasibility study TS 22.942. It operates within the Short Message Service (SMS) framework and provides the calling party (the originator of a short message) with status information about messages they have submitted. Rather than relying solely on lower-layer acknowledgements, SMR introduces an application-level receipt mechanism that can confirm whether a message was delivered, and in some configurations, whether it was read or otherwise processed by the recipient.

Architecturally, SMR leverages the existing SMS infrastructure: the Short Message Service Centre (SMSC) acts as the central store-and-forward node, while the Home Location Register (HLR) and Visitor Location Register (VLR) provide routing and subscriber status information. When a subscriber activates the SMR service, the network records this in the subscriber's profile. Upon submission of a short message, the SMSC can generate a receipt once the message has been successfully delivered to the recipient's Mobile Station (MS) or when delivery fails. The receipt is itself a short message delivered back to the originating MS, carrying status indicators such as 'delivered', 'failed', or 'pending'.

The service supports both single and multiple receipts. A single receipt typically confirms final delivery status, while multiple receipts can provide intermediate status updates — for example, one receipt when the message reaches the SMSC and another when it is delivered to the recipient. This flexibility allows operators to offer tiered receipt services and gives users granular visibility into message handling. The exact number and content of receipts are governed by operator configuration and the capabilities negotiated between the MS and the network.

SMR interacts with several other SMS features, including the More Messages to Send (MMS) flag, the TP-Status-Report facility in the SMS-DELIVER and SMS-SUBMIT protocol data units, and the Status Report Request indicator. The receipt mechanism is distinct from the low-level SMS status report defined in TS 23.040, although the two can be used together. SMR is primarily a service-level concept, ensuring that the receipt is meaningful to the end user rather than just to the protocol stack.

From a deployment perspective, SMR is widely used in applications such as message delivery confirmation for enterprise messaging, two-factor authentication, and consumer messaging where users expect read or delivery receipts. Because it is defined as a supplementary service, it can be provisioned per subscriber and controlled via the SIM/USIM and operator management systems. Its longevity across Releases 8 through 19 reflects the continued importance of SMS as a reliable, ubiquitous messaging channel, even in the era of rich messaging services.

Purpose & Motivation

Short Message Receipt exists to solve a fundamental limitation of basic SMS: the sender has no inherent way of knowing whether a submitted message actually reached its destination. Basic SMS is a store-and-forward service, and without a receipt mechanism, the sender can only infer success from the absence of an error. SMR was created to provide explicit, network-generated confirmation of message status, improving reliability and user confidence.

The service was motivated by both consumer and enterprise needs. Consumers wanted confirmation that important messages — such as appointment reminders or personal communications — were delivered. Enterprises and service providers needed delivery confirmation for transactional messaging, including banking alerts, authentication codes, and marketing campaigns, where knowing the outcome of each message is essential for billing, compliance, and customer experience.

Historically, early SMS implementations offered only low-level status reports at the protocol layer, which were not always exposed to the user and could be ambiguous. SMR standardizes a service-level receipt that is meaningful to the end user and can be provisioned and managed as a supplementary service. This standardization ensures interoperability across networks and devices, allowing receipts to work even when the sender and recipient are on different operators' networks.