dsTest supports Message Service Center (MSC)/Visitor Location Register (VLR) client simulation and GMSC/SMS-SC server emulation capabilities for the Mobile Application Part (MAP) E interface. Test SMS-Gateway MSC (GMSC) E interfaces in UMTS networks with our VLR Emulator node. Use the E Interface application to emulate an SMS-GMSC generating MT short messages towards an MSC/VLR. For more information regarding how to use dsTest for MAP functional and compliance testing, see our page on Conformance Testing. MAP is specified in 3GPP TS 29.002. The E interface is specified in 3GPP TS 23.040 and 3GPP TS 23.204.
Rich sets of SMS, MAP, and TCAP operational measurements are 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.
The E Interface application implements the MAP-MT-FORWARD-SHORT-MESSAGE and MAP-MO-FORWARD-SHORT-MESSAGE services. dsTest supports application context versions 1, 2, and 3 for these services.
MSC/VLR Testing (Server Emulation)
Our E Interface application provide an E Interface protocol test tool that can be used to simulate an SMS-GMSC’s E interface to determine the SMS processing capacity and performance of client MSC/VLR nodes. 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.
GMSC Testing (Client Simulation)
The VLR Emulator node 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.