dsTest supports server emulation and client simulation capabilities for the 3GPP LTE Mobile Application Part (MAP) J interface in UMTS networks. Use our Home Location Register (HLR) Emulator to test the J interfaces of GSM Service Control Functions (gsmSCFs). Test the capacity and performance of an HLR with our MAP J Interface application client simulation. For more information regarding how to use dsTest for MAP functional and compliance testing, see our page on Conformance Testing. Customize your MAP/TCAP messages and message flows using our SmartEvents and SmartTCAP features. MAP is specified in 3GPP TS 29.002.
Comprehensive sets of Mobile Application Part (MAP), Transaction Capabilities Application Part (TCAP) and infrastructure operational measurements (OMs) 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 analyzed with our dsClient GUI.
The 3GPP MAP J interface application implements the following services from the HLR to the gsmSCF:
The 3GPP MAP J interface application implements the following services from the gsmSCR to the HLR:
gsmSCF Testing (Server Emulation)
The HLR emulator initiates the appropriate service when indicated, eliminating the need to dedicate a production server to lab activities. It provides Mobile Subscriber data repository, authentication information, and routing information services for the J interface—all of the functionality required by a HLR 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 using our SmartEvents feature. 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 HLR emulator can support any mixture of interfaces, up to 1000 connections. Using concurrent interfaces also enables interaction between the interfaces. Multiple J interfaces enable support for mobility, for example. Extend the 3G functionality of your HLR Emulator with additional interfaces:
- C – SMS, Service Center messages between MSC to HLR;
- D/D’ – Subscriber info authentication, update, purge and insert
- Gr – Subscriber authentication, profile, and location services for SGSNs;
- Gf – EIR Simulation;
- Gc – GPRS services for GGSNs.
Multiple gsmSCF simulators can be instantiated on a single server. In this mode each server can support multiple interfaces, up to an aggregate of 1000 connections. The simulators are fully independent and their subscriber databases may be independent, overlap, or be duplicated.
HLR Testing (Client Simulation)
The J Interface application simulates a gsmSCF’s J interface interface to determine the impact of new HLR features and standards before they are deployed in a network. The J 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 gsmSCF-initiated procedures.
Multiple gsmSCF nodes can be instantiated on a single server, each with scalable subscriber loads and transaction rates. In this mode the J interfaces of up to 1000 independent gsmSCF nodes may be simultaneously running. 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
- MAP Dictionary
- Diameter Dictionary
- Diameter Result Codes
- RADIUS Dictionary
- S1 Dictionary
- GTPv1 Dictionary
- GTPv2 Dictionary
- GTP Cause Codes
- SIP Response Codes