This page describes the scenarios and methodology used when running the benchmarks.

On this page...

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 Opencloud Scenario Simulator performs the role of SMSC and SCSCF. For details of the message processing, see MO Submission Flows

  1. The SCSCF sends a SIP Message containing a valid RP-Data payload to the IP-SM-GW.

  2. The IP-SM-GW responds to the SCSCF with a 202 Accepted message.

  3. The IP-SM-GW sends a TCAP OpenRequest to the SMSC.

  4. The SMSC replies with an OpenAccept.

  5. The IP-SM-GW sends an MO-ForwardSM request to the SMSC.

  6. The SMSC replies with an MO-ForwardSM response, and closes the TCAP dialog.

  7. The IP-SM-GW sends a SIP Message containing an RP-ACK to the SCSCF.

  8. The SCSCF replies with a 200 OK.

mo submission with report successful

CS Delivery

In this scenario, the SMSC delivers a MT SMS to the IP-SM-GW, which then sends the message over the CS network. The OpenCloud Scenario Simulator performs the role of SMSC, MSC, and HLR. For details of changes made to proxied messages and details of message processing, see MT Delivery Flows.

  1. The SMSC sends an OpenRequest containing a SendRoutingInfoForSM request to the IP-SM-GW.

  2. The IP-SM-GW proxies that message to the HLR.

  3. The HLR replies with a SendRoutingInfoForSM response.

  4. The IP-SM-GW proxies that response to the SMSC, and closes the dialog to the SMSC.

  5. The SMSC sends an OpenRequest containing an MT-ForwardSM request to the IP-SM-GW.

  6. The IP-SM-GW sends an empty OpenRequest to the MSC.

  7. The MSC response with an OpenAccept

  8. The IP-SM-GW sends the MT-Forward-SM request to the MSC on the established dialog

  9. The MSC closes the dialog

  10. The IP-SM-GW sends an OpenAccept to the SMSC, and closes the dialog.

mt cs delivery mapv2 successful
Previous page Next page