MAP Forward Short Message and Delivery Report Flow in Mobile Networks

For most Australians, the humble SMS remains a daily habit, used for everything from ordering a flat white in Melbourne to coordinating rideshares in Brisbane and checking tide times along the Mornington Peninsula. Behind every text lies a chain of signaling exchanges that ride on the Mobile Application Part of the SS7 stack and its modern successors.

MAP sits in Layer 7 of the GSM signaling architecture and remains the lingua franca for store-and-forward short messages, even as networks evolve toward 4G Diameter and 5G HTTP/2 service-based interfaces. Operators such as Telstra, Optus and TPG Telecom still depend on it for interconnect with international carriers and legacy SMSCs.

The MAP_FORWARD_SHORT_MESSAGE operation moves a single SMS between network elements, while the SM-Delivery-Report tells the originating side how the handset actually received it. Together they form the heartbeat of person-to-person messaging in this country, where mobile behaviour includes ABC emergency warnings, Triple Zero call setup, and the rich two-factor authentication ecosystem used by the Big Four banks.

This walkthrough traces the transfer path from a sender's handset in Sydney to a recipient's device in Perth, then follows the delivery report on its return leg. The focus stays practical: which message types fire, which timers govern them, and where failures typically surface in modern core networks.

MAP and the Mobile Network Stack

MAP is the transaction-oriented application layer that runs on top of TCAP, SCCP and either MTP3 or SIGTRAN's M3UA/SCTP transport. In a 2G or 3G core the chain ends at the MSC, while in a 4G EPC the equivalent control point is the MME for attach and the SMS-GMSC/SMS-IWMSC for message routing.

An SMS routed across Australia will often pass through three operator domains: the sender's home PLMN, an interconnect partner that may be a transit carrier, and the recipient's home PLMN. The SM-MT and SM-MO service profiles defined in 3GPP TS 29.002 govern how MAP dialogue IDs and operation codes are assigned so that messages are not confused with USSD or supplementary service requests.

Mobile Originated Forwarding Flow

When a phone in Adelaide sends a text, the serving MSC collects the RP-DATA from the handset and builds a TPDU that gets wrapped inside a MAP_MO-FORWARD_SM invoke. The MSC picks the destination SMSC by subscriber profile lookup, then opens a TCAP dialogue using the SMSC's global title.

SCCP routing handles the addressing, often using an E.214 mobile global title translated through the home location register. Once the SMSC acknowledges the dialogue with a TC-CONTINUE or component return, the MSC releases the SCCP/TCAP context. Captures from a live Vodafone Australia trace confirm that the entire MO leg typically completes in well under 600 ms across the SIGTRAN hop that is widely documented in telecom training literature and design notes such as the Masha Leilm resource.

Mobile Terminated Delivery Path

For delivery, the SMSC performs a SendRoutingInfoForSM-LCS query to find the current serving node, then issues a MAP_FORWARD_SHORT_MESSAGE toward the recipient's MSC or SGSN. In 4G coverage the same operation is delivered to the MME over Diameter S6a-adjacent interfaces and reaches the device via NAS signalling.

When the message lands, the handset returns an RP-ACK, and the serving node translates that into a delivery report component. The report carries the original service center time stamp, the disposition code (delivered, memory available, absent subscriber, or failure), and the protocol identifier so that the originating SMSC can present a meaningful receipt to the sender.

SM-Delivery-Report Mechanism

The delivery report is its own MAP operation, MAP_REPORT_SM_DELIVERY_STATUS, which is sent back along the same dialogue chain or, if the original dialogue is closed, in a fresh TCAP conversation. Operators in Australia commonly tag the TP-Parameter-Indicator to request a status report even when the sender has not explicitly asked for one, because ACCC guidelines on consumer transparency have made reliable delivery feedback important.

Report flooding is a known issue during major public events, such as the Sydney New Year fireworks or the Melbourne Cup, when bursts of ticket confirmations trigger wave after wave of acks. Smart SMSCs apply gapping timers and per-subscriber rate limits to prevent feedback storms from saturating SCCP links.

Signaling Layers: TCAP, SCCP, M3UA

TCAP packages the MAP operations into components and dialogues, while SCCP provides connectionless or connection-oriented transport with global title translation. Modern cores replace the legacy MTP3 transport with M3UA over SCTP, which lets SIGTRAN traffic share IP infrastructure with other carrier services.

Engineers validating a new SMS route typically trace through Wireshark dissectors to confirm the TCAP message type, then verify the SCCP called-party address and the M3UA routing context. A mismatch between the OPC/DPC codes or the routing key will surface as a TCAP reject with the cause "abnormalDialogue", which is often the first clue that a peering configuration has drifted.

4G and 5G Migration: Diameter and HTTP/2

In 4G, the SM transfer function in the MME is exposed over Diameter as the SGd reference point, defined in 3GPP TS 29.272. The same MAP semantics are preserved through translation tables, so the application-level behaviour of forward short message and delivery report is unchanged from the operator's perspective.

The 5G core moves SMS into a service-based architecture, where the SMSF exposes Nsmsf_SMService operations over HTTP/2. SMS still anchors on IMS when RCS is active, but plain SMS-Fallback continues to ride through EPC signalling for the foreseeable future.

Observability and Common Failures

Monitoring the MAP short message flow requires probes at the SIGTRAN gateway, the SMSC and the interconnect border. Key counters include forward short message attempts, TCAP user errors, and the ratio of reports received within the operator copy transfer timer window.

Field notes that surface repeatedly on Australian jobs:

  • Missing HLR subscription data after a port to a new provider
  • GT routing black holes between transit and destination carriers
  • Diameter result code 3006 "No Element Manager Available" during LTE-to-5G inter-PLMN handovers

Operational practices that keep the path healthy include keeping the SCCP subsystem number for MAP in the local subsystem table reset, validating SMSC address translation after any prefix change, and confirming the routing context against the carrier team guide.

Reminders from Local Deployments

A few practical reminders for engineers working the message path on Australian soil:

  • Always confirm the MCC/MNC pair before tracing, because MTCs from inbound Pacific roamers often arrive with non-standard VLR addresses
  • The default SMSC address in the HLR should be E.164-formatted with the +61 country prefix; bare 04xxxxxxxx numbers will be rejected by modern SMSCs
  • When staging captures in Brisbane or Perth, plan for higher latency on the SIGTRAN hop because of the long fibre paths to Sydney and Melbourne aggregation points
  • Schedule message floods away from scheduled Triple Zero test windows so SMSC gapping does not mask genuine emergency alerting traffic
Aspect 2G/3G MAP 4G Diameter SGd 5G HTTP/2 Nsmsf
Transport SCCP/M3UA/SCTP SCTP/Diameter HTTP/2/JSON
Operation map_forwardShortMessage SGd submit Nsmsf_SMService
Delivery report map_reportSMDeliveryStatus Diameter AVP HTTP/2 callback
Typical latency 100-400 ms 80-250 ms 50-150 ms

A reliable delivery path is built on disciplined global title planning, accurate HLR records, and well-tuned gapping, because every part of the MAP forward short message and delivery report flow ultimately depends on the care taken in these three areas. Operators that invest in continuous probing at the SIGTRAN gateway tend to be the first to detect a routing drift, and the first to restore service when an interconnect peer falters across the busy Australian core.