GL Communications Inc.
 
 
Home >  VoIP Analysis and Simulation  >  MAPS™

MAPS™ MAP Emulator
(Scripted Mobile Application Part Emulation over IP/TDM)

MAPS™ MAP Protocol Emulator Software Ver 5.7.21 | Download Now!


Background

Mobile Application Part (MAP) is an application layer protocol used by various elements in GSM, UMTS, and GPRS mobile core networks to provide services to mobile phone users.

MAP can be transported using 'traditional' SS7 protocols in TDM (T1 and E1) or over IP using SIGTRAN.

SIGTRAN is a stack of networking protocols having Stream Control Transport Protocol (SCTP) for stream management over IP, and a bunch of user adaptation (UA) layers over it. Supported adaptation layers are M2PA (MTP2 Peer-to-Peer), M3UA (MTP 3 User), and M2UA (MTP2 User).

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. The "radio" and "core" network partition is shown above for GSM and UMTS networks. Elements and interfaces that comprise the core network are briefly described below.
 
Common services provided by MAP are "Location Tracking", "Roaming", "Subscription Information", "Short Message Service", and many more.

Interface Elements Purpose TDM
(T1/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 SIP, MGCP, UMTS, GSM, MLPPP, MEGACO, ISDN, CAS, SS7, and many more. MAPS™ MAP supports emulation of 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 MTP3 layer (over TDM) and M3UA, M2PA layers (over IP) messages and parameters.

MAPS™ MAP currently supports the various procedures emulating MSC (VLR), HLR, EIR, and SMSC entities and H, C, D, E, F interfaces in the network. Supported procedures include Location Update, Retrieve Roaming Number, Remote User Status, Check IMEI Service, and others.

The product also supports send/receive SMS (Short Message Service) simultaneously using signaling channel with the voice/data/fax service over GSM network.

GL also provides various set of protocol analyzers 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.

Possible applications include:

  • Multi-protocol, Multi-interface Simulation
  • Provides fault insertion, and erroneous call flows testing capability.
  • Performance testing, Load Testing, Function al testing, Regression testing and Conformance testing of network elements.
  • Ready scripts makes testing procedure simpler, less time consuming and hence time to market products.
  • Test response of network against protocol message modification, or corruption
  • Inter-operability testing of networks
  • Wrap-around testing (WAT)
  • SMS Testing from within the Wireless Infrastructure using MAPS™

Supported Protocols Standards

Over TDM
Supported Protocols Standard / Specification Used
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
   
Over IP
Supported Protocols Standard / Specification Used
MAPR4 3GPP TS 29.002 V4.18.0 (2007-09)
TCAP ANSI T1.114-1996
SCCP Q.713, CCITT (ITU-T) Blue Book
MTP3 ITU-T Q.782
M2PA RFC 4165
M3UA RFC 3332
SCTP RFC 4960

Typical Call Procedures

Shown below are the typical MAP procedure over IP and TDM interfaces:

MAP/D Mobile Originating
Call Flow

MAP/D Location Update
Call Flow

MAP/C, MAP/D Retrieval Routing Information Call Flow
     
Mobile Terminating (MT) and
Mobile Originating (MO) SMS Procedures
Remote User Status
Procedure

Check IMEI Status
Procedure

     
   

GPRS Location Update Procedure

   

Call Generation and Reception

MAPS™ is configured as MSC/VLR which initiates the LocationUpdate procedure by sending the updateLocationArg message to HLR. MAP_UPDATE_LOCATION service is used by the VLR to update the location information stored in the HLR. This is performed using the UpdateLocationArg_MSCVLR.gls script.


MAPS™ can also be configured as HLR which receives the request message from MSC and simulates complete LocationUpdate procedure.

MAP Call Generation at MSC/VLR Node MAP Call Reception at HLR Node

General MAPS™ Features


Call Simulation and Control

The signaling and traffic simulation in a call is completely implemented using scripts. Commands in the scripts are executed in controlled way to simulate protocol and traffic behavior. Most of the commands used in the scripts are generic and independent of specific protocol.

MAPS™ application acts as either the Caller or resides at the network terminal acting as Callee. The Call Generation feature simulates an outgoing call by sending call control messages to the DUT using scripts and profiles. The profiles allow necessary parameters of call control messages to be changed during runtime. Call generated from other entity can be automatically detected in call reception window by pre-setting the required answer scripts in the Incoming Call Handler.

The call control scripts can also automatically handle the traffic over the established call. MAPS™ supports transmission and detection of various traffic types over  IP (RTP, GTP), ATM, & TDM - such as, digits, voice file, single tone, dual tones, fax, sms, email, http, ftp, and video. MAPS™ also includes support for wide range of codec rates – visit www.gl.com/traffic-simulation.html and www.gl.com/voice-codecs.html webpage for more details.

Message Sequence - Each call scenario provides the trace with full decoding of the messages exchanged between the MAPS™ and the DUT, and graphical ladder diagrams of the call flow with time stamp. Impairments can be applied to messages to simulate error conditions that occur in real-time networks.

Event-Driven Control - Scripts execution, being event-based, allows redirection of script execution on-the-go with user-defined events. The custom parameters in the events can also be changed during script execution using event profiles.

Script Contents & Script Flow - The script flow and the contents window displays the Script Name, Sub-script Name, Script line number, and script statements to be successfully executed, which help the users in troubleshooting a particular call scenario.

Bulk Call Simulation and Load Testing

MAPS™ supports automated stress/load testing capabilities through Load Generation and Bulk Call Simulation features. Bulk Call Simulation allows quick configurations to easily create multiple test entries with different scripts and profiles. Multiple tests can be run simultaneously or sequentially (queue up tasks in succession). Load generation feature further allows specifying the patterns with which the bulk calls can be generated. Load generation can be customized with different statistical distribution patterns such as Uniform, Ramp, Sawtooth, Fixed, Normal, Step, and Step-Sawtooth distribution. Call duration also can be randomized using similar statistical distribution. This feature also helps users configure Stress/Load Testing parameters such as Call per second (CPS), Max Active Call, Minimum and Maximum Call Rates, Start Call Rates, and other parameters.

Scheduler

Scheduler can be used to schedule the simulation of bulk calls or manual calls at a specific start time. The pre-saved master configuration files for test setup and call simulation are automatically loaded to automate the test procedure.

Customization of Test Setup Parameters

The test setup profiles (.xml files) allow users to configure the necessary parameters in order to establish communication between MAPS™ and the DUT. It includes configuring parameters of the network nodes, the network properties, and transport related configurations such as T1/E1 timeslots, IP Address and port numbers for both MAPS™ and the DUT.

Once the transport layer is configured properly, protocol specific signaling messages and traffic can be transmitted and received successfully. All parameters setup in test setup are global and are accessible to all scripts. These parameters initialize protocol engines and the transport modules specific to the protocol.

Customization of Test Parameters, Call Flow, and Protocol Messages Using Pre-Processing Tools

  • Message Editor - The Message Templates (GL’s proprietary *.HDL files) 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.
  • Profile Editor – Profiles (*.xml files) are used to change the values of the fields in the messages (i.e. Message Template in MAPS™) during the course of a call. The multiple profiles with varying parameter values that allow users to configure call instances in call generation and to receive calls.
  • Script Editor - The script editor allows the user to create / edit scripts and to define variables for the fields in the messages. 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.

Command Line Interface

Supports scripting through a Command Line Interface (CLI) such as the Python, and TCL, using MAPS™ client-server functionality (requires additional license)

MAPS™ can be configured as server-side application, to enable remote controlling of the application through multiple command-line based clients. Supported clients include C++, TCL, Python and others. TCL provides a simple scripting language, with programming facilities such as looping, procedures, and variables. The TCL Client application includes a MapsTclIfc.dll file, a packaged library that enables communication with the Server from a TCL environment.

User can remotely perform all functions such as start test bed setup, load scripts and profiles, apply user events such as send digits/file/tones, detect digits/file/tones, dial, originate call, terminate call, start and stop traffic and so on. User can also generate and receive calls through commands. This client application is distributed along with MAPS™ Server application. Multiple MAPS™ CLI servers can be controlled remotely from single client application (such as TCL, Python, etc).

Call Statistics, Events, Link Status

Call Status & Message Statistics - 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, Failed Calls, and Calls/Sec. It is also possible to categorize the statistical information as per the call handling scripts. In addition, Call Generation and Call Reception windows provide useful call status & script execution results.

In addition, Message Stats option for any specific protocol, logs number of times the messages are being transmitted (Tx Count) and received (Rx Count), thus allowing user to monitor the occurring events.

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.

Link Status - Link Status window indicates transport related information of the protocol, for example, if SCTP is used as transport, it indicates if the association is Up or Down in the Link Status window. MAPS™ IuCS ATM uses SSCOP transport and the associated link status is indicated as Up or Down in the Link Status window.

Screenshots




Screen Shot of MAPIP Testbed Setup Configuration Screen Shot of MAP Testbed Setup Configuration Screenshot of Load Generation Parameters Screenshot of Script Editor



Screenshot of Profile Editor Screenshot of Message Editor Screenshot of Script Contents and Script Flow Screenshot of Call Statistics
Screenshot of Message Statistics Screenshot of Event Log Screenshot of SCTP Link Status Screenshot of MTP Link Status

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 ETA or EEA (Octal/Quad Boards), PTA or PEA (tProbe Units), UTA or UEA (USB Units), HUT or HUE (Universal Cards), and HDT or HDE (HD cards) depending upon the hardware.

Item No. MAPS™ for TDM Network
(requires T1 or E1 Hardware and Basic Software)
XX694 MAPS™ MAP Emulator
XX696 MAPS™ CAP Emulator
XX649 MAPS™ SS7 Emulator
XX647 MAPS™ SS7 Conformance
XX652 MAPS™ MC-MLPPP Conformance
XX648 MAPS™ ISDN & LAPD Emulator
XX642 MAPS™ ISDN & LAPD Conformance Emulator
XX692 MAPS™ GSM A Emulator
XX693 MAPS™ GSM Abis Emulator
XX651 MAPS™ CAS Emulator
XX656 MAPS™ INAP Emulator
XX682 MAPS™ IUP Emulator
XX624 MAPS™ FXO FXS Emulator (only for tProbe)
  Related Hardware
FTE001

ETE001
QuadXpress T1E1 Main Board (Quad Port– requires additional licenses) 

OctalXpress T1E1 Main Board plus Daughter Board (Octal Port– requires additional licenses)
PTE001 tProbe™ Dual T1 E1 Laptop Analyzer with Basic Analyzer Software
HTE001 Universal T1 E1 PCI Card with Basic Analyzer Software
UTE001 Portable USB based Dual T1 or E1 Laptop Analyzer with Basic Analyzer Software
Item No. MAPS™ for Wireless Network
  Related Software
PKS140 MAPS™ LTE S1 Emulator
PKS142 MAPS™ LTE eGTP (S3, S4, S5, S8, S10, S11 & S16) Emulator
PKS141 MAPS™ LTE X2 AP Emulator
PKS160 MAPS™ UMTS IuCS IP Emulator
MAPS™ UMTS IuH IP Emulator
PKS164 MAPS™ UMTS IuPS Emulator
PKS166 MAPS™ UMTS Gn Gp Emulator
LTS220 MAPS UMTS IuCS ATM Emulator over OC-3 / STM-1
requires LTS214 + LightSpeed1000™ Hardware; optional LTS217
LTS214 OC-3 / STM-1 SSCOP Server
LTS320 MAPS UMTS IuCS ATM Emulator over OC-12 / STM-4
requires LTS314 + LightSpeed1000™ Hardware; optional LTS317
LTS314 OC-12 / STM-4 SSCOP Server
PKS131 MAPS™ Gb Emulator over IP for BSC & SGSN
  Related Hardware
LTS100 Lightspeed1000™ - Dual OC3/12 STM1/4 PCIe Card
 Item No. MAPS™ for IP Network
PKS151 MAPS™ CAMEL IP Emulator
PKS122
PKS123
MAPS™ MEGACO Emulator
MAPS™ MEGACO Conformance Test Suite (Test Scripts)
PKS124
MAPS – MGCP Protocol Emulation with Conformance Test Suite
PKS120
PKS121
MAPS™ SIP Emulator
SIP Conformance Test Suite (Test Scripts)
PKS126 MAPS™ SIP I Emulator
PKS130 MAPS™ SIGTRAN Emulator
PKS132 MAPS™ MAP IP Emulator
PKS135 MAPS™ ISDN SIGTRAN (ISDN IP)
PKS134 MAPS GSM Abis IP Emulator
PKS137 MAPS™ GSM A IP Emulator
PKS149 MAPS™ Skinny Emulator
PKS155 MAPS™ BICC IP Emulator
PKS136 MAPS™ INAP Emulator (ANSI, ITU)
PKS139 MAPS™ Diameter Emulator
Item No. Traffic Options
XX610
XX620
XX646
File based Record/Playback
Transmit/Detect digits (Place Call/ Answer Call)
Multi-Channel TRAU Tx/Rx Emulation and Analysis
PKS102 RTP Soft Core for RTP Traffic Generation
PKS200 RTP Pass Through Fax Emulation
ETH100

ETH101

ETH102

ETH103
PacketCheck™ - Packet GTP Traffic Simulation

Mobile Traffic Core-GTP


Mobile Traffic Core-Gateway

Mobile Traffic Core - GPRS Gb
LTS217 OC-3 / STM-1 AAL2 Traffic Core
LTS317 OC-12 / STM-4 AAL2 Traffic Core
Item No. Related Software
XX120 SS7 Analyzer Software
OLV120 Offline/ Remote SS7 Analyzer Software
XX100 ISDN Analyzer Software
OLV100 Offline/ Remote ISDN Analyzer Software
XX150 T1 or E1 Real-time GSM Protocol Analyzer
OLV150 Offline T1 or E1 GSM Protocol Analyzer
XX165 T1 or E1 Real-time UMTS Protocol Analyzer
PKS100 PacketGen™ with PacketScan™
PKV100 PacketScan™ (Online and Offline)
PKB100
PKB105
RTP Toolbox™
G.168 Echo Canceller Test Compliance Suite
PKV105 SIGTRAN Analyzer (requires PKV100)
PKV107 LTE Real-time LTE Protocol Analyzer (Requires PKV100)
 
 
Home Page Sitemap Global Presence Email