RP SME-Address

Description

RP-SMEA, or RP SME-Address, is a key parameter within the Relay Protocol (RP) data structure used for Short Message Service (SMS) communication over the IP Multimedia Subsystem (IMS). An SME (Short Message Entity) is any entity that can originate or terminate a short message; this is most commonly a mobile subscriber's UE, but can also be an application or service. The RP-SMEA field contains the address of this entity. In the context of mobile-terminated SMS (message sent to a UE), the RP-SMEA in the RP-DATA message carries the address of the originating SME (the sender). In mobile-originated SMS or in response messages like RP-ACK, it carries the address of the destination or responding SME.

The technical format of the RP-SMEA is derived from the address formats used in legacy SMS over circuit-switched networks. It typically contains an address type (e.g., international number, national number, alphanumeric) and the digit string itself, such as an MSISDN (e.g., +1234567890). Within the RP PDU, the RP-SMEA is positioned alongside other fields like the RP-MTI and RP-UI. When an IP Short Message Gateway (IP-SM-GW) receives an SMS submission from a UE via SIP, it extracts the RP-SMEA from the RP-DATA to identify the sender. Conversely, when the IP-SM-GW receives an SMS from the legacy SMSC via MAP, it places the sender's address from the MAP message into the RP-SMEA field of the RP-DATA before embedding it into a SIP MESSAGE destined for the recipient UE.

Its role is crucial for address resolution, routing, and presentation. The UE uses the RP-SMEA to display the sender's number for an incoming message. Furthermore, in network routing logic, the RP-SMEA may be used for applying service logic, such as spam filtering or billing. It also plays a part in generating delivery reports; when a UE sends an RP-ACK (delivery report) back to the network, it includes its own address as the RP-SMEA, allowing the IP-SM-GW to correlate the report with the original message and forward it to the correct SMSC and ultimately to the original sender. This end-to-end address transparency is vital for the SMS service to function correctly across the hybrid network involving both IMS and legacy circuit-switched core network elements.

Purpose & Motivation

The RP-SMEA was defined to preserve the critical addressing information of SMS in the transition from circuit-switched to IMS-based delivery. In traditional GSM/UMTS SMS, the sender and recipient addresses were carried within the MAP protocol layers. As SMS began to be transported over IMS using SIP, there was a risk of losing this essential metadata if it was not explicitly defined within the new protocol encapsulation. The RP layer, including the RP-SMEA field, was created to serve as a container for this SMS-specific signaling, ensuring that the addressing information remained intact and unambiguous when carried inside SIP, which has its own addressing scheme (SIP URIs) for routing sessions.

This solved a fundamental interworking problem: mapping between E.164 telephone numbers (used in the legacy SMS world) and SIP URIs (used in IMS). The IP-SM-GW acts as the translation point. It uses the RP-SMEA from the RP message to perform number-based routing and subscriber identification, which is necessary to interface with the legacy Home Location Register (HLR) and SMSC. Without a standardized field like RP-SMEA to carry the MSISDN, the IP-SM-GW would have to infer the sender/recipient address from other, potentially less reliable SIP headers, which could lead to incorrect message delivery, broken calling line identification presentation (CLIP), and failed delivery reports. Thus, RP-SMEA ensures backward compatibility and service continuity for one of the most ubiquitous telecommunication services during network evolution.