Skip to content

Messaging (SMS)⚓︎

Short messages for Mobile Assets on the mobile operator's public radio network, served by the Expeto SMSC in Expeto Gateway (xRouter): mobile-originated and mobile-terminated messages over MAP and over SGd, exchange with application servers over SMPP, concatenated and binary messages, delivery reports, store-and-forward for absent devices, and routing rules.

ID Test Category Applies to
EXP-MSG-001 UE to UE SMS over MAP Functional 4G · Public radio · Single node, HA cluster, Geo-redundant
EXP-MSG-002 UE to application SMS over MAP and SMPP Functional 4G · Public radio · Single node, HA cluster, Geo-redundant
EXP-MSG-003 Application to UE SMS over SMPP and MAP, concatenated, binary and receipted Functional 4G · Public radio · Single node, HA cluster, Geo-redundant
EXP-MSG-004 MO and MT SMS over SGd Functional 4G · Public radio · Single node, HA cluster, Geo-redundant
EXP-MSG-005 Store-and-forward for an absent UE Functional 4G · Public radio · Single node, HA cluster, Geo-redundant
EXP-MSG-006 Message routing rules Functional 4G · Public radio · Single node, HA cluster, Geo-redundant

EXP-MSG-001 — UE to UE SMS over MAP⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 20 min

Objective. A Mobile Asset on the mobile operator's public radio network sends a text message to another Mobile Asset. The operator's core relays it over MAP to the Expeto SMSC, which locates the recipient through the HSS and delivers it over MAP to the recipient's serving node, and both legs are recorded in xControl.

Preconditions

  • Platform
    • The Expeto SMSC in xRouter is enabled with MAP over SIGTRAN toward the operator's signalling network, and the mobile operator routes short messages for the Expeto SMSC global title to it.
  • Mobile Asset
    • Two Mobile Assets, A and B, each with an MSISDN, both attached through the public radio network (EXP-POL-002).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A signalling capture at xRouter's SIGTRAN interface (capture point 7).
    • Access to the CLI.

Procedure

# Where Action Expected result
1 UE On UE A, send a text message to UE B's MSISDN. Note the time. UE A reports the message as sent.
2 Capture Inspect the capture. The messages match the sequence under Expected signalling.
3 UE Observe UE B. The message arrives within 30 seconds with the text sent.
4 xControl Open Mobile Asset A's Event Log and select SMS, then Mobile Asset B's. A's log shows the outgoing message with source MAP; B's log shows the delivered message with a delivery success and no failure cause.
5 CLI Run cd /lte, then read smsc. No message for A or B remains stored.

Expected signalling

Capture points: SIGTRAN at xRouter (point 7), S6c between the SMSC and the HSS.

4G (EPS) sequence

  1. MO-ForwardSM (mo-forwardSM invoke) from the operator's serving node to the Expeto SMSC, and its result
  2. SendRoutingInfoForSM from the SMSC to the HSS for B's MSISDN, returning B's IMSI and serving node
  3. MT-ForwardSM (mt-forwardSM invoke) from the SMSC to B's serving node, and its result

Pass criteria

  • The message is delivered within 30 seconds with its content intact.
  • Both legs appear in the capture and in the SMS event logs of the two Mobile Assets, with no failure cause.
  • No message remains stored in the SMSC after delivery.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log; CLI output.
References: 3GPP TS 23.040 §10 (Short message procedures); 3GPP TS 29.002 §12.2 (MO-ForwardSM); 3GPP TS 29.002 §12.9 (MT-ForwardSM); 3GPP TS 29.002 §12.1 (SendRoutingInfoForSM).

EXP-MSG-002 — UE to application SMS over MAP and SMPP⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 20 min
Prerequisite procedures EXP-MSG-001 — UE to UE SMS over MAP

Objective. A Mobile Asset sends a text message to an application's short code or number. The Expeto SMSC receives it over MAP, matches a routing rule for the destination, and delivers it to the application server bound over SMPP.

Preconditions

  • Platform
    • An SMSC routing rule maps the application's destination address to destinationRoute: SMPP for the application's system id.
  • Mobile Asset
    • Mobile Asset A attached through the public radio network (EXP-POL-002).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • An SMPP test client bound to the SMSC as a receiver with the application's system id.
    • A signalling capture at xRouter (capture points 7 and 9).
  • Procedures executed first

Procedure

# Where Action Expected result
1 UE On UE A, send a text message to the application's destination address. Note the time. UE A reports the message as sent.
2 Test host Observe the SMPP test client. A deliver_sm arrives within 30 seconds with A's MSISDN as source, the application's address as destination and the text sent; the client answers deliver_sm_resp.
3 Capture Inspect the capture. MO-ForwardSM arrives over MAP and the same message leaves over SMPP; no MT-ForwardSM is attempted.
4 xControl Open Mobile Asset A's Event Log and select SMS. The message is recorded with source MAP and route SMPP, delivered, with no failure cause.

Expected signalling

Capture points: SIGTRAN at xRouter (point 7), SMPP (point 9).

4G (EPS) sequence

  1. MO-ForwardSM from the operator's serving node to the Expeto SMSC, and its result
  2. SMPP deliver_sm from the SMSC to the bound application, and deliver_sm_resp

Pass criteria

  • The application receives the message within 30 seconds with source, destination and text intact.
  • The event log records the message with source MAP and route SMPP and no failure cause.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.
References: 3GPP TS 29.002 §12.2 (MO-ForwardSM); SMPP Protocol Specification v3.4 §4.6 (deliver_sm).

EXP-MSG-003 — Application to UE SMS over SMPP and MAP, concatenated, binary and receipted⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-MSG-001 — UE to UE SMS over MAP

Objective. An application server submits messages to a Mobile Asset over SMPP: a plain text, a concatenated text longer than one segment, and a binary message. The Expeto SMSC delivers each over MAP to the recipient's serving node, the UE reassembles the concatenated text, and the application receives a delivery receipt for each message.

Preconditions

  • Mobile Asset
    • Mobile Asset B attached through the public radio network (EXP-POL-002).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • An SMPP test client bound to the SMSC as a transmitter and receiver, able to request delivery receipts.
    • A signalling capture at xRouter (capture points 7 and 9).
  • Procedures executed first

Procedure

# Where Action Expected result
1 Test host Submit a plain text message (under 160 characters) to B's MSISDN with a delivery receipt requested (registered_delivery). The SMSC answers submit_sm_resp with a message identifier.
2 UE Observe UE B. The message arrives within 30 seconds with the text intact.
3 Test host Observe the SMPP test client. A deliver_sm delivery receipt arrives for the message identifier with the delivered state.
4 Test host Submit a 200-character text message with a delivery receipt requested. The SMSC accepts it.
5 Capture Inspect the capture. The message is delivered as two MT-ForwardSM segments with a user data header (concatenation reference, total 2, sequence 1 and 2).
6 UE Observe UE B. The full 200-character text is shown as one message.
7 Test host Submit an 8-bit binary message (for example 100 bytes of a known pattern, data coding 8-bit) to B's MSISDN. The SMSC accepts it and the UE (or a data-SMS capable application on it) receives the exact bytes.
8 xControl Open Mobile Asset B's Event Log and select SMS. Three delivered messages are recorded with source SMPP and route MAP and no failure cause.

Expected signalling

Capture points: SMPP (point 9), SIGTRAN at xRouter (point 7).

4G (EPS) sequence

  1. SMPP submit_sm / submit_sm_resp for each message
  2. SendRoutingInfoForSM from the SMSC to the HSS, then MT-ForwardSM to B's serving node, one per segment, each with its result
  3. SMPP deliver_sm carrying the delivery receipt, and deliver_sm_resp

Pass criteria

  • Each message is delivered within 30 seconds with content intact; the concatenated message is shown as one message; the binary payload is received byte for byte.
  • The application receives a delivery receipt in the delivered state for each message.
  • The event log records the three messages with source SMPP and route MAP and no failure cause.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.
References: SMPP Protocol Specification v3.4 §4.4 (submit_sm); 3GPP TS 23.040 §9.2.3.24 (TP-User-Data (concatenated short messages)); 3GPP TS 29.002 §12.9 (MT-ForwardSM).

EXP-MSG-004 — MO and MT SMS over SGd⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min

Objective. Where the mobile operator's MME delivers short messages over Diameter, a Mobile Asset's mobile-originated message reaches the Expeto SMSC over SGd and a mobile-terminated message is delivered to the UE over SGd, without the circuit-switched network.

Preconditions

  • Platform
    • The Expeto SMSC in xRouter has the SGd application enabled (hss.diameter.applications.sgdGdd: true) and a Diameter peer to the operator's MME or SMS router.
    • The HSS advertises SMS in MME to the operator's MME (agent.hss.nodeConfig.hssConfig.smsInMme: true), so that the MME registers for SMS over SGd.
    • The operator's MME supports SGd toward the Expeto SMSC.
  • Mobile Asset
    • Two Mobile Assets, A and B, each with an MSISDN, attached through the public radio network (EXP-POL-002).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A signalling capture at xRouter's Diameter interface (capture point 8) and at S6a (capture point 4).
    • An SMPP test client bound to the SMSC.

Procedure

# Where Action Expected result
1 Capture Inspect the Update Location Answer for Mobile Asset A on S6a. The answer advertises SMS in MME, so the MME handles A's short messages over SGd.
2 UE On UE A, send a text message to UE B's MSISDN. UE A reports the message as sent.
3 Capture Inspect the Diameter capture. The operator's MME sends MO-Forward-Short-Message-Request (OFR) to the Expeto SMSC and receives the answer (OFA); the SMSC then sends MT-Forward-Short-Message-Request (TFR) toward B's MME and receives the answer (TFA).
4 UE Observe UE B. The message arrives within 30 seconds with the text intact.
5 Test host Submit a text message from the SMPP test client to UE A's MSISDN. The SMSC accepts it and delivers it with TFR / TFA; UE A receives it within 30 seconds.
6 xControl Open the Event Log of A and B and select SMS. The messages are recorded with source or route DIAMETER and no failure cause.

Expected signalling

Capture points: Diameter SGd at xRouter (point 8), S6a (point 4).

4G (EPS) sequence

  1. Update Location Answer with the SMS-in-MME indication
  2. MO-Forward-Short-Message-Request / Answer (OFR / OFA) from the MME to the SMSC
  3. SendRoutingInfoForSM to the HSS, then MT-Forward-Short-Message-Request / Answer (TFR / TFA) from the SMSC to the recipient's MME

Pass criteria

  • Both messages are delivered within 30 seconds with their content intact, entirely over Diameter.
  • The event logs record the messages with the Diameter source or route and no failure cause.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.
References: 3GPP TS 29.338 §5.3 (SGd interface procedures); 3GPP TS 29.338 §6.3 (MO-Forward-Short-Message and MT-Forward-Short-Message); 3GPP TS 23.040 §10 (Short message procedures).

EXP-MSG-005 — Store-and-forward for an absent UE⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 30 min
Prerequisite procedures EXP-MSG-003 — Application to UE SMS over SMPP and MAP, concatenated, binary and receipted

Objective. A message to a Mobile Asset that is switched off is held by the Expeto SMSC, the HSS is told the message is waiting, and the message is delivered when the device returns, with a delivery receipt to the sender.

Preconditions

Procedure

# Where Action Expected result
1 Test host Submit a text message to B's MSISDN with a delivery receipt requested. Note the time. The SMSC answers submit_sm_resp.
2 Capture Inspect the capture. The delivery attempt fails with an absent-subscriber indication, and the SMSC sends ReportSMDeliveryStatus to the HSS, which sets the message-waiting indication.
3 CLI Run cd /lte, then read smsc. The message is listed as stored, with B as receiver, its retry count and its route.
4 xControl Open Mobile Asset B's Event Log and select SMS. The failed attempt is recorded with the absent-subscriber cause and the message is pending.
5 UE Power on UE B and let it attach. The UE attaches; the message arrives within one minute of the attach.
6 Capture Inspect the capture. On the attach, the HSS alerts the SMSC (ReadyForSM or AlertServiceCentre) and the SMSC delivers the stored message with MT-ForwardSM.
7 Test host Observe the SMPP test client. A delivery receipt in the delivered state arrives for the message identifier.
8 CLI Run read smsc again. The message is no longer stored.

Expected signalling

Capture points: SIGTRAN at xRouter (point 7), SMPP (point 9).

4G (EPS) sequence

  1. SMPP submit_sm / submit_sm_resp
  2. SendRoutingInfoForSM, then MT-ForwardSM failing with absent subscriber, then ReportSMDeliveryStatus to the HSS
  3. On the UE's attach, ReadyForSM or AlertServiceCentre from the HSS to the SMSC
  4. MT-ForwardSM to the serving node, then SMPP deliver_sm carrying the delivery receipt

Pass criteria

  • The message is held while the UE is off and delivered within one minute of the UE attaching, with content intact.
  • The sender receives a delivery receipt in the delivered state.
  • The SMSC holds no copy after delivery.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log; CLI output.
References: 3GPP TS 23.040 §3.2.7 (Alert-SC (message waiting)); 3GPP TS 23.040 §10.3 (Short message mobile terminated); 3GPP TS 29.002 §12.8 (ReadyForSM); 3GPP TS 29.002 §12.4 (AlertServiceCentre).

EXP-MSG-006 — Message routing rules⚓︎

Attribute Value
Status Accepted
Category Functional
Components xRouter, xControl
Applies to 4G · Public radio · Single node, HA cluster, Geo-redundant
Duration About 20 min
Prerequisite procedures EXP-MSG-001 — UE to UE SMS over MAP

Objective. The Expeto SMSC applies its routing rules: a destination configured to be rejected returns a failure to the sender, a destination configured to be discarded is dropped silently, and the rules can be removed to restore delivery.

Preconditions

  • Platform
    • Two SMSC routing rules exist, one with destinationRoute: REJECT for destination address R and one with destinationRoute: DISCARD for destination address D, and you can change the rules.
  • Mobile Asset
    • Mobile Asset A attached through the public radio network (EXP-POL-002).
  • Tooling and access
    • Log in to xControl with an account that holds the ADMIN role.
    • A signalling capture at xRouter (capture point 7).
  • Procedures executed first

Procedure

# Where Action Expected result
1 UE On UE A, send a text message to address R. UE A reports a delivery failure.
2 Capture Inspect the capture. The MO-ForwardSM is answered with an error; no MT-ForwardSM follows.
3 UE On UE A, send a text message to address D. UE A reports the message as sent; nothing is delivered anywhere.
4 Capture Inspect the capture. The MO-ForwardSM is answered with success; no further message follows.
5 xControl Open Mobile Asset A's Event Log and select SMS. The first message is recorded as Rejected and the second as Discarded.
6 Tester Remove both rules and send a message to R again. The message is delivered as in EXP-MSG-001.

Pass criteria

  • A rejected destination returns a failure to the sender and nothing is forwarded.
  • A discarded destination is accepted from the sender and nothing is forwarded.
  • The event log records Rejected and Discarded; removing the rules restores delivery.

Postconditions

  • Restore the routing rules the deployment had before the test.

Evidence collected: 3GPP signalling capture (pcap); xControl session event log.