MAPS™ MAP Protocol Emulator
(Scripted Mobile Application Part Emulation)
Background
As illustrated in the diagram above, some of the GSM/UMTS circuit switched interfaces such as C (between HLR & MSC), D (between HLR and VLR),
E (between GMSC and MSC), F (between MSC and EIR), H (between HLR and AuC) and & Packet-switched interfaces such as Gc (between GGSN and HLR),
Gr (between SGSN and HLR), Gf (SGSN and EIR), Gd (between SGSN & SMS-GMSC) use Mobile Application Part (MAP) protocol carried within SS7 TCAP
messages The “radio” and “core” network partition is shown above for GSM and UMTS networks.. Elements and interfaces that comprise the core network
are briefly listed and described in the table below.:
|
|
|
Mobile Application Part (MAP) is an SS7 protocol which provides application layer services to the various nodes in GSM and UMTS networks. MAP can be
transported using 'traditional' SS7 protocols carried by Message Transfer Protocol (MTP) in TDM (T1 and E1) or over IP using SIGTRAN.
Common services provided by MAP are “location tracking”, “roaming”, “subscription information”, “short message service”, and many more.
| Interface |
Elements |
Purpose |
TDM (T1 or E1) |
IP |
| B |
MSC-VLR |
Generally an internal interface within the MSC. Used whenever the MSC needs access to data regarding a MS located in its area. |
√ |
√ |
| C |
MSC-HLR |
MSC server interrogates the HLR for routing information of a subscriber for a call or SMS directed to that subscriber |
√ |
√ |
| D |
VLR-HLR |
Used to exchange data related to the current location of a mobile station and to the management of that subscriber |
√ |
√ |
| E |
MSC-GMSC
MSC-SMSC |
Exchange of handover data between two adjacent MSCs for the purpose of seamless call and message flow |
√ |
√ |
| F |
MSC-EIR |
Used by the EIR to verify the status of the IMEI retrieved from the Mobile Station |
√ |
√ |
| G |
VLR-VLR |
Used to update a new VLR with IMSI and authentication info from old VLR, when a mobile subscriber moves from one VLR area to another (not shown in the
diagram) |
√ |
√ |
| H |
HLR-AuC |
HLR requests for authentication and ciphering data from the AuC for a Mobile Subscriber . |
√ |
√ |
| Gc |
GGSN-HLR |
Used by the GGSN to retrieve information about the location and supported services for a mobile subscriber for packet data services (GPRS, etc.) |
√ |
√ |
| Gr |
SGSN-HLR |
Used to exchange data related to the current location and management of a Mobile Subscriber (MS) and Mobile Equipment (ME) |
√ |
√ |
| Gf |
SGSN-EIR |
Used by the EIR to verify the status of the IMEI retrieved from the Mobile Station. |
√ |
√ |
| Gd |
SGSN-SMSC |
Used to transfer SMS over GPRS. |
√ |
√ |
Overview
GL’s MAPS™ (Message Automation & Protocol Simulation) product line bearing the same acronym, is used to emulate all the MAP interfaces listed
above – both TDM and IP.
GL’s MAPS™ is an advanced and versatile protocol simulator/tester that can simulate a variety of protocols encountered in the telecom
space, including ISDN, CAS, SS7, and many more. Now, it also supports all the GSM and UMTS MAP interfaces. In addition to supporting MAP network elements
connected by the interfaces listed, it also supports error tracking, regression testing, conformance testing, load testing, and call generation. It can run pre-defined
test scenarios against test objects in a controlled & deterministic manner.
MAPS™ MAP Emulator supports powerful utilities like Message Editor, Script Editor, and Profile Editor which allow new scenarios to be created or
existing scenarios to be modified using MAP messages and parameters.
GL also provides various set of protocol analyzer for on-line capture and decode of the signaling in real-time both during tests and as a stand-alone tracer
for live systems. Please visit Protocol Analysis page for more details.
Supported Protocol Standards
| Available Standards |
Supported Protocols |
Standard / Specification Used |
| MAP |
MAPR4 |
3GPP TS 29.002 V4.18.0 (2007-09) |
| TCAP |
ANSI T1.114-1996 |
| SCCP |
Q.713, CCITT (ITU-T) Blue Book |
| MTP3 |
Q.703, ITU-T Blue Book |
Main Features
- MAP protocol simulation over TDM (E1/T1)
- Emulator can be configured as MSC (VLR), HLR, GMSC, EIR, AuC, SMSC, SGSN and GGSN entities and emulate the respective interfaces
- User-friendly GUI for configuring the MAP signaling links
- Access to all MTP3, SCCP, and MAP R4 protocol fields such as TMSI, IMSI, MCC, MNC, MSIN, CCBS and more
- Ready scripts for monitoring other end, set reporting state for the requested service, report an event or call outcome, report remote subscriber
status procedures
- Logging of all messages in real-time
- Save and load configurations
- Supported on Windows® XP (or higher) operating systems
Test Configuration
The test configuration window allows users to configure MTP layer parameters to transmit and receive GSM messages over MTP layer. The configuration
window for MAPS™ MAP includes parameters for T1/E1 (GL) server and MTP Task along with MTP signaling.
Screen Shot of MAP Testbed Setup Configuration
Call Generation
Call Generation option allows the user to simulate outgoing communications where an outgoing call is initiated by sending call control messages using proper
scripts and profiles. The profile allows necessary parameters of call control messages to be changed during runtime. Shown below are some of sample call flows in
GSM MAP interfaces:
MAP/D Mobile Originating Call Flow
MAP/D Location Update Call Flow
MAP/C, MAP/D Retrieval Routing Information Call Flow
The screenshot below shows MAPS™ acting as MSC/VLR and sending the LocationUpdate message to HLR.
Call Generation at MSC/VLR Node
Call Reception
Call generated from other entity can be automatically detected in call reception window by pre-setting the required scripts in the Incoming Call Handler
window.
The screenshot below shows MAPS™ acting as HLR and responding to the LocationupdateRequest message from MSC.
Screenshot of Call Reception at HLR Node
Bulk Call Simulation
MAPS™ supports Bulk Call Simulation and Stress/Load Testing capabilities through Load Generation feature. Load Generation window helps users
configure Stress/Load Testing parameters such as Call per second (CPS) or Busy hour call attempts (BHCA), Max Simultaneous Calls and Burst parameters.
Screenshot of Load Generation Parameters
Customization of Call Flow and Messages Using Pre-Processing Tools
- Script Editor - The script editor allows the user to create / edit scripts and to define variables for the protocol fields. The script uses pre-defined
message templates to build call flow and perform send and receive actions. Script editor provides options to run the test for multiple iterations in sequential
or random flow. Commands allow retransmission of messages with specific interval.
Screenshot of Script Editor
- Profile Editor - Profiles are used to provide the user configured values to the fields in the Messages (i.e., Message Template in MAPS™)
through variables which are going to change during the course of a call.
Screenshot of Profile Editor
- Message Editor - The Message Template is a *.HDL file that comprises of protocol encoding parameters with preset values. It is required to create
a message template for every message in a protocol. The message templates are called within the scripts to perform scenario based testing.
Screenshot of Message Editor
Call Flow & Script Execution Control
Message Sequence - MAPS™ provides protocol trace with full message decoding, custom trace, and graphical ladder diagrams of call flow
with time stamp while simulation is running. Call flow graph allows to easily verifying the messages exchanged between MAPS™ and DUT.
See Call Generation and Call Reception for details
Script Contents & Script Flow - The Scripts Contents window displays the contents of the script selected for call generation or reception. The Script
Flow window displays the set of statements successfully executed by MAPS™ to help users in troubleshooting a particular the call scenario.
Events & Event Profile Editor - User-defined events allow redirection of script execution on-the-go. The custom parameters in the events can also
be changed during script execution using Event Profiles.
Screenshot of Script Contents and Script Flow
Screenshot of Event Config
Call Statistics, Events, Link Status
Call Statistics & Status - By default, all call handling scripts (irrespective of the type of the functions) are assessed by MAPS™ to provide
statistical information about total calls, active calls, completed calls, passed calls, and failed calls. It is also possible to characterize the statistical information
under different groups of call handling scripts under a unique heading. In addition, Call Generation and Call Reception windows provide useful call status &
script execution results.
Screenshot of Call Statistics and Status
Events Reporting – MAPS™ provides Event Log, Error Events, and Captured Errors windows that log the captured events and errors
encountered during the progress of the call.
Screenshot of Event Log
Buyer's Guide:
Please Note: The XX in the Item No. refers to the hardware platform, listed at the bottom of the Buyer's Guide, which the software will be
running on. Therefore, XX can either be HDT, HDE, HUT, HUE, UTA or UEA depending upon the hardware.
Specifications are subject to change without notice.
Back to Message Automation & Protocol Simulation
Index Page
![](javascript:myOpen("images/maps-map-web-testbed-setup.gif"))
![](javascript:myOpen("images/maps-map-web-load-generation.gif"))
![](javascript:myOpen("images/maps-map-web-script-editor.gif"))
![](javascript:myOpen("images/maps-map-web-profile-editor.gif"))
![](javascript:myOpen("images/maps-map-web-message-editor.gif"))
![](javascript:myOpen("images/maps-map-web-script-contents-script-flow.gif"))
![](javascript:myOpen("images/maps-map-web-event-profile-editor.gif"))
![](javascript:myOpen("images/maps-map-web-statistics.gif"))
![](javascript:myOpen("images/maps-map-web-event-log.gif"))
