Benchmarks were done with an equal split of three different scenarios described below.
MO submission
In this scenario, the SCSCF sends a SIP message containing a short message to the IP-SM-GW, which then sends an MO-ForwardSM request to the SMSC. The Metaswitch Scenario Simulator performs the role of SMSC and SCSCF. OCS Charging is disabled for this test. For details of the message processing, see MO Submission Flows.
Latencies are measured at the SCSCF/ICSCF simulator, between the initial MESSAGE sent to IP-SM-GW, and the delivery report MESSAGE sent to the ICSCF by IP-SM-GW.
MT PS delivery
In this scenario, the SMSC delivers a MT SMS to the IP-SM-GW, which then sends the message over the PS network. CS fallback is not invoked, as the PS delivery is successful. The Metaswitch Scenario Simulator performs the role of SMSC, MSC, and HLR. OCS charging is disabled for this test. For details of changes made to proxied messages and details of message processing, see MT Delivery Flows.
Latencies are measured at the SMSC simulator, between the initial SRI_SM message sent to the IP-SM-GW, and the MT-FSM Res message recieved by the SMSC. This includes both the Routing Information for Short Message flows, and Forward Short Message flows for every message.
Third party registration
In this scenario, the IP-SM-GW receives and processes an initial third party registration. In order to maximise work done per registration, all registrations are initial. For details of message processing, see Registration Flows.
Latencies are not directly measured for this scenario. Latency in third party registration handling is not visible to the end user unless it is excessive enough to trigger test failures.
