dsTest® supports both MSC/VLR emulation and client simulation capabilities for the E interface. Test SMS-GMSC E interfaces in UMTS networks with our Visitor Location Register (VLR) Emulator. Use the E Interface application to emulate an SMS-GMSC generating MT short messages towards an MSC.
A rich set of operational measurements is collected at specified intervals and stored in a SQLite database on the dsTest server. Real-time measurements may be retrieved through our dsClient™ CLI interface or graphed via our dsClient GUI interface.
Implementation
The E Interface application implements the MAP-MT-FORWARD-SHORT-MESSAGE service.
Server Emulation
The VLR Emulator accepts MT short messages for known subscribers and responds with the appropriate error if the subscriber is not known or if any errors in the message would prevent delivery to a subscriber in a real network.
Read more about our VLR Emulator.
Read more about SMS configurations.
Client Simulation
Our E Interface application can be used to simulate an SMS-GMSC’s E interface to determine the SMS processing capacity and performance of an MSC/VLR. The E Interface application allows users to validate MSC/VLR performance and capacity in a realistic network environment, replicating the deployment configuration.
- Execute timed chains of test events to forward messages to subscribers that may or may not be reachable, simulating real-world subscriber activity
Multiple GMSC nodes can be instantiated on a single server, each with scalable subscriber loads and transaction rates. In this mode, up to 1000 independent SMS-GMSC nodes may be simultaneously simulated. The nodes are fully independent and their subscriber configurations may also be independent, overlap, or be duplicated.
Read more about our Capacity and Performance.
Supporting Standards
- Technical realization of the Short Message Service (SMS) – 3GPP TS 23.040
- SMS over generic 3GPP Internet Protocol (IP) access – 3GPP TS 23.204
- MAP – 3GPP TS 29.002
- TCAP – ITU-T Q.773
- SCCP – ITU-T Q.711-714
- M3UA – RFC 4666
- SCTP – RFC 2960 (RFC 3309 checksum)