Technology guide · Messaging

SMS Technologies
& Protocols

A practical view of SMSCs, SMPP, SS7/MAP, routing, delivery receipts, encoding, throughput, security and modern messaging operations.

Rightech SolutionsUpdated 15 September 2026Technical reference

SMS delivery is store-and-forward. Acceptance by an upstream platform confirms submission—not necessarily handset delivery. Final status depends on downstream networks and the available receipt information.

01

SMS traffic models

P2PPerson-to-person traffic between subscribers.
A2PApplication-to-person traffic such as service messages and alerts.
P2APerson-to-application traffic, often replies or short-code interactions.
Two-wayA coordinated outbound and inbound messaging service supporting conversation flows.
02

How SMS moves

An application or enterprise platform submits a message to an aggregator, carrier or SMSC. Routing logic selects the next hop. In mobile signalling environments, the SMSC obtains routing information and attempts delivery through the serving network. If the handset is unavailable, the SMSC may retain and retry the message within its validity period.

ESME

An external short messaging entity—commonly the application or platform connected over SMPP.

SMSC

The short message service centre that accepts, stores, routes and attempts message delivery.

HLR / HSS

Subscriber data and routing functions; exact roles depend on the mobile generation and architecture.

MSC / SGSN / IMS

Serving-domain elements involved in reaching the subscriber, depending on network technology.

Aggregator

Connects multiple customers and networks, applying routing, commercial and operational controls.

03

SMPP connectivity

SMPP is widely used between messaging applications, aggregators and SMSCs. A session normally binds as transmitter, receiver or transceiver. Common protocol data units include bind_transceiver, submit_sm, deliver_sm, data_sm, enquire_link and unbind.

Operational SMPP controls

  • Negotiate bind mode, credentials, source address and TON/NPI rules.
  • Set window size and throughput limits without exhausting outstanding requests.
  • Maintain the session with enquire-link and controlled reconnect behaviour.
  • Correlate sequence numbers, message IDs and delivery receipts.
  • Define character encoding, concatenation, validity period and receipt format.
04

SS7, MAP and Diameter

Traditional mobile SMS uses SS7 signalling and Mobile Application Part operations for routing and delivery. SIGTRAN can carry SS7 signalling over IP networks. LTE/EPC deployments can use Diameter procedures, while IMS and newer messaging environments may introduce further interworking. The precise path depends on the operator architecture, roaming state and service configuration.

05

Encoding, length and concatenation

The GSM 7-bit default alphabet permits up to 160 septets in one 140-octet SMS payload. Characters from its extension table consume two septets. UCS-2 permits up to 70 16-bit characters in one segment. Concatenation adds a user data header, reducing the payload per segment; therefore visible character count alone does not reliably predict segment count.

06

Routing, throughput and delivery

Good messaging operations balance quality, compliance, capacity and cost. Route selection may consider destination, sender type, traffic profile, latency, historical delivery, commercial policy and regulatory constraints. Throughput is measured in messages or protocol operations per second, but multipart SMS can create several billable segments.

Submission response

Confirms whether the immediate SMPP request was accepted or rejected.

Delivery receipt

Reports a downstream state such as delivered, expired, rejected or undeliverable, subject to network support.

Latency

Measure submission, provider acceptance and final-receipt timing separately.

Route quality

Assess successful delivery, receipt integrity, stability, filtering and destination-specific behaviour.

07

Security, compliance and fraud

Access control

Restrict peers, protect bind credentials and encrypt transport where supported.

Sender integrity

Validate sender identifiers and follow country and operator registration requirements.

Content controls

Apply lawful, proportionate filtering and prohibit deceptive, abusive or fraudulent content.

Traffic monitoring

Detect unusual velocity, destinations, repeated content, pumping and artificial traffic.

Data protection

Minimise and protect message content, numbers, receipts and operational logs.

Consent and policy

Respect applicable consent, opt-out, quiet-hour and permitted-use requirements.

Primary references include the ITU-T Q.700 SS7 overview and the applicable 3GPP mobile messaging specifications. SMPP behaviour should follow the agreed interface version and bilateral profile.