dsTest supports server emulation and client simulation capabilities for the 3GPP LTE Mobile Application Part (MAP) D and D’ interfaces in UMTS networks. Use our Home Location Register (HLR) Emulator to test the D interfaces of Visitor Location Registers (VLRs) and the D’ interfaces of WLAN AAAs. Test the capacity and performance of an HLR with our MAP D Interface application client simulation. 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.
Use the D’ interface application as part of your 3GPP WLAN Interworking/Wi-Fi Offload testing scenarios, testing either the AAA or HLR.
Rich sets of Mobile Application Part (MAP) and Transaction Capabilities Application Part (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 3GPP MAP D interface application implements the following services:
- Authentication Information Retrieval
- Authentication Failure Report
- Update Location
- Cancel Location
- Insert Subscriber Data
- Restore Data
- Purge MS
- Ready for SMS
- Provide Roaming Number
A complete set of events that can be generated with the D/D’ interface can be found here.
VLR/AAA Testing (Server Emulation)
The server emulator initiates the appropriate service such as Cancel Location or Insert Subscriber Data when indicated, eliminating the need to dedicate a production server to lab activities. The HLR Emulator provides Mobile Subscriber data repository, authentication information, and routing information services for the D interface—all of the functionality required by a VLR plus all of the benefits of an emulator.
You can manually trigger server-initiated procedures by executing a test event chain with a run-time command or during an automated test. You can also use the control interface to change an emulator’s behavior. Simulate a non-responsive server by pausing the emulator or simulate intermittent issues by pausing and resuming. Disable individual subscribers during the test run, generating unknown subscriber errors.
One server emulator can support any mixture of interfaces, up to 1000 connections. Using concurrent interfaces also enables interaction between the interfaces. Multiple D interfaces enable support for mobility, for example. Extend the 3G functionality of your HLR Emulator with additional interfaces:
- Gr—Subscriber authentication, profile, and location services for SGSNs;
- Gf—EIR Simulation;
- Gc—GPRS services for GGSNs.
Multiple HLR Emulators can be instantiated on a single server. In this mode each emulator can support multiple interfaces, up to an aggregate of 1000 client connections across all emulators. The emulators are fully independent and their subscriber databases may be independent, overlap, or be duplicated.
HLR Testing (Client Simulation)
The D Interface application simulates a VLR’s D interface or a WLAN AAA’s D’ interface to determine the impact of new HLR features and standards before they are deployed in a network. The D Interface application also allows you to validate HLR performance and capacity in a realistic network environment, replicating the deployment configuration.
Execute timed chains of test events with a run-time command or during an automated test to trigger VLR-initiated procedures.
- Start and stop specified subscriber sessions, simulating real-world subscriber activity
- Generate Restore Data requests
Multiple VLR nodes can be instantiated on a single server, each with scalable subscriber loads and transaction rates. In this mode the D interfaces of up to 1000 independent VLR nodes may be simultaneously running and mobility may be 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.
- MAP – 3GPP TS 29.002
- TCAP – ITU-T Q.773
- SCCP – ITU-T Q.711-714
- M3UA – RFC 4666
- SCTP – RFC 4960
- Specification Map
General Reference Guides
- Diameter Dictionary
- Diameter Result Codes
- RADIUS Dictionary
- S1 Dictionary
- GTPv1 Dictionary
- GTPv2 Dictionary
- GTP Cause Codes