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

MAPS™ UMTS for IuCS, IuH Interfaces Emulator
(Scripted UMTS IuCS and IuH Emulation over IP)

MAPS™ UMTS IuCs, IuH Interface Emulator Software Ver 3.7.12 | Download Now!


Background

Universal Mobile Telecommunications System (UMTS) is a 3rd generation mobile technology that can support greater data rates for voice and video data to the wireless end users. The underlying transport layer for UMTS can be Asynchronous Transfer Mode (ATM), or Internet Protocol (IP).

The UMTS network consists of the following elements -

  • NodeB - supporting broadband mobile users
  • Radio Network Controller (RNC) - manages radio resources (NodeBs) and routes traffic to circuit and packet switched elements
  • Mobile Switching Centre (MSC) - circuit switching element for voice
  • Serving GPRS Support Node (SGSN) - packet switching element for data and video
  • Femto Home NodeB (Femto Cell) - for enhanced coverage indoors and to offload the radio access network
  • Femto Home Node Gateway (HnB-GW) - provides wired broadband interface

To emulate various components in IuCS and IuH interfaces of UMTS network, GL utilizes its MAPS™ foundation architecture – a versatile platform for detailed emulation of a wide variety of protocols. MAPS™ supports emulation of many protocols like ISDN, SS7, GSM, LTE, SIP, Megaco, MGCP, SIGTRAN, and many others.

MAPS™ UMTS IuCS can emulate the RNC (Radio Network Controller) and the MSC (Mobile Switching Centre) by generating RANAP signaling messages over SCTP and SSCOP (ATM).



IuCS and IuH over IP

GL’s Message Automation & Protocol Simulation (MAPS™) designed for UMTS IuH interface can simulate Femto Home Node B (HnB), and a Femto Home Node Gateway (HnB-GW) by generating RANAP and DTAP signaling messages over SCTP Transport layer. A femtocell is a small cellular base station designed for use in residential or small business environments. Femtocells can offload the RAN and provide better coverage, plus improved data download & upload speeds. IuH links Femto Access Point (HnB) and a Femto Gateway (HnB-GW).

MAPS™ UMTS IuCS can emulate the RNC (Radio Network Controller) and the MSC (Mobile Switching Centre) by generating RANAP and DTAP signaling messages over SCTP. It includes ready scripts to simulate Location Update, Call Control MO (Mobile Originating), and Mobile Terminating (MT) procedures.

The application gives the users the unlimited ability to edit messages and control scenarios (message sequence). “Message sequences” are generated through scripts. “Messages” are created using message templates.

The application is available as

  • MAPS™ - IuCS and IuH (Item # PKS160)
  • RTP Traffic Options in MAPS™ UMTS IuCS and MAPS™ UMTS IuH (Item # PKS102)
  • Traffic Options over Iu-UP protocol layer in MAPS™ UMTS IuCS (Item # PKS103)

MAPS™ IuCS supports Auto and User-defined RTP traffic simulation over transport protocol with additional RTP Core licensing (PKS102). RTP traffic simulation supports various traffic types like send and receive tone, digits, files, and loopback are supported for almost all standard codecs.

MAPS™ IuCS emulator is enhanced to also support  Iu-UP (Iu User Plane Interface) protocol layer of the Radio Network with additional licensing (PKS103) to carry RTP traffic (AMR payload part) over Iu interface in support mode of operation for predefined SDU size.

MAPS™ IuCS ATM

GL's LightSpeed1000™ hardware platform (PCIe Card) with quad optical ports supports simulation of UMTS IuCs interface over ATM layer using MAPS™ IuCS ATM. The LightSpeed1000™ comes with software for overall monitoring, protocol analysis and emulation, and bert. The hardware can also be easily configured / programmed for delaying of ATM Cells or PPP packets.

MAPS™ IuCS ATM uses SSCOP server for establishing SSCOP links over which RANAP,ALCAP, and DTAP signaling will be carried for making calls. SSCOP Server is a GL's WCS based server module that provides SSCOP, AAL5 and AAL2 layer services. Following licenses are required for MAPS™ IuCS ATM:

  • OC3 / STM1 MAPS UMTS IuCS over ATM, requires (Item # LTS220)
  • OC3 / STM1 SSCOP Server (Item # LTS214)
  • OC3 / STM1 AAL2 Traffic Core (Item # LTS217)

Over successfully established call, traffic can be generated. MAPS™ IuCS ATM internally uses AAL2 Traffic Generator for traffic generation. Various traffic types like Tone, Digits and File playback are supported.

Main Features

  • Simulates RNC, MSC, Home NodeB (HnB) and Home NodeB Gateway (HN GW) entities.
  • Generates and process all Mobility Management, Session Management, RANAP, ALCAP, and DTAP messages over SSCOP.
  • User controlled access to RANAP, and DTAP signaling messages over SCTP.
  • Ready scripts for Mobile Originating, Mobile Terminating, Location Updating procedures for quick testing
  • Supports RAB Assignment, Authentication, TMSI Reallocation, Encryption, and other optional procedures
  • SSCOP links over which RANAP and ALCAP signaling will be carried further for making calls
  • SSCOP Server (GL's WCS based server module) provides SSCOP, AAL5 and AAL2 layer services
  • Supports various traffic types including Tone, Digits and File playback over AAL2
  • Supports traffic over Iu UP protocol layer and also over normal RTP sessions (requires additional licenses).
  • All Codec supported including - G.711, G.711 App II with VAD, G.729, G.726, G.726 with VAD, GSM, AMR NB and WB, EVRC, SMV, iLBC, SPEEX NB and WB, G722, and G722.1. Visit Voice Codecs webpage for more comprehensive information.

 

Supported Protocols Standards

UMTS IuCS Protocol Stack

UMTS IuH Protocol Stack

Supported Protocols Specification Used
IuCS Interface
SCCP Q.713, CCITT (ITU-T) Blue Book
MTP3 Q.703, ITU-T Blue Book
RANAP 3GPP TS 25.413 V9.1.0
MM / CC 3GPP TS 24.008 V5.16.0 (2006-06)
RR 3GPP TS 04.18 V8.13.0
SMS 3GPP TS 03.40 V7.5.0 & 3GPP TS 04.11 V7.1.0 GSM 03.38 version 7.2.0 Release 1998

Iu-UP
Iu User Plane Interface

3GPP TS 25.415
IuH Interface
RUA 3GPP TS 25468 V9.1.0
RANAP 3GPP TS 25.413 V9.1.0
MM / CC 3GPP TS 04.08 V7.17.0
RR 3GPP TS 04.18 V8.13.0
SMS 3GPP TS 03.40 V7.5.0 & 3GPP TS 04.11 V7.1.0 GSM 03.38 version 7.2.0 Release 1998


UMTS IuCS ATM base Protocol Stack
Supported Protocols Specification Used
  IuCS ATM Interface
SSCOP ITU-T Q.2110
MTP3b ITU-T Recommendation Q.2210
AAL Type 2 (ALCAP) ITU-T Recommendation Q.2630.1
RANAP 3GPP TS 25.413 V9.1.0
MM / CC 3GPP TS 24.008 V5.16.0 (2006-06)
RR 3GPP TS 04.18 V8.13.0
SMS 3GPP TS 03.40 V7.5.0 & 3GPP TS 04.11 V7.1.0 GSM 03.38 version 7.2.0 Release 1998
Iu-UP
Iu User Plane Interface
3GPP TS 25.415

Call Simulation over IuCS ATM

In IuCS interface, MAPS™ acts as either RNC to test MSC (DUT) or MSC to test RNC (DUT) and simulates the following call control procedures:

Call Control MO – (Mobile Originating) Procedure

Typical Call Control MO Procedure
over IuCS ATM
Call Control MO Procedures at
RNC Node over IuCS ATM

Call Control MO Procedures at
MSC Node over IuCS ATM

Mobile Terminating Call (MTC) Procedure

MAPS™ can be configured to act as Mobile Station Controller (MSC) to process the Mobile Terminating (MT) call procedure by initiating the Paging message with the Mobile Station (RNC). MAPS™ (RNC) then completes the call as in call control MT procedure.

Typical Call Control MT Procedure
over IuCS ATM
MT Procedure at RNC Node
over IuCS ATM

MT Procedure at MSC Node
over IuCS ATM

Call Simulation over IuCS IP

In IuCS interface, MAPS™ acts as either RNC to test MSC (DUT) or MSC to test RNC (DUT) and simulates the following call control procedures:

Testing MSC (Location Update and Mobile Originating procedures)

Typical Call Control MO Procedure over IuCS IP

Call Control MO Procedures at RNC Node
over IuCS IP (Call Generation)

Call Control MO procedure at MSC Node
over IuCS IP (Call Reception)

Testing RNC (Mobile Terminating Call – MTC Procedure)

MAPS™ can be configured to act as Mobile Station Controller (MSC) to process the Mobile Terminating (MT) call procedure with the Mobile Station (RNC). MAPS™ (RNC) then completes the call as in call control MT procedure.

Typical Mobile Terminating Call Scenario

MTC Call Generation Flow at MSC Node

MTC Call Generation Flow at RNC Node

Call Simulation over IuH IP

MAPS™ IuH interface emulator simulates MOC, MTC, and LU call procedures between the HnB-GW and HnB nodes.

Testing Home NodeB Gateway (Location Updating Call - LUC Procedure)

MAPS™ as HnB initiates the Location Updating messages towards HnB-GW and responds to messages from HnB-GW (DUT).

MAPS™ (HnB-GW) on receiving LOCATION UPDATING REQUEST initiates Authentication process, sends Authentication Request message as a response to HnB (DUT).

Typical Location Updating Call (LUC)
Flow over IuH IP

Screenshot of LUC Call Generation
Flow at HnB Node

Screenshot of LUC Call Reception
Flow at HnB-GW Node

Testing Home NodeB Gateway (Mobile Originating Call – MOC Procedure)

MAPS™ acts as HnB and initiates the Mobile Originating messages towards HnB-GW and responds to messages from HnB-GW (DUT).
 MAPS™ (HnB-GW) on receiving service request initiates Authentication Procedure, sends Authentication Request message as a response to HnB (DUT).

Typical Mobile Originating Call (MOC)
Flow over IuH IP

MOC Call Generation Flow at HnB Node

MOC Call Reception Flow at HnB-GW Node

Testing Femto Home NodeB (Mobile Terminating Call – MTC Procedure)

MAPS™ as HnB-GW and initiates the paging procedure for CS services towards HnB and responds to messages from HnB (DUT). MAPS™ then completes the call as in Mobile Terminating Call (MTC) call flow.

MAPS™ (HnB) on receipt of a PAGING Message from HnB-GW, replies with PAGING RESPONSE message as depicted in the screenshots below.

Typical Mobile Terminating Call (MTC) Flow

MTC Call Generation Flow at HnB-GW Node

MTC Call Reception Flow at RNC 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.

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. Item Description
  MAPS™ UMTS IuCS IuH over IP
PKS160


PKS102
Message Automation & Protocol Simulation (MAPS™) - UMTS-IuCS
Message Automation & Protocol Simulation (MAPS™) - UMTS-IuH

RTP Soft Core for RTP Traffic Generation
  MAPS™ UMTS IuCS ATM with LightSpeed1000™  
LTS100 Lightspeed1000™ - Dual OC3/12 STM1/4 PCIe Card
LTS105 Lightspeed1000™ - Portable Dual OC3/12 STM1/4 USB Unit
LTS220 OC-3 / STM-1 MAPS UMTS IuCS over ATM, requires LTS214
LTS214 OC-3 / STM-1 SSCOP Server
LTS217 OC-3 / STM-1 AAL2 Traffic Core
LTS320 OC-12 / STM-4 MAPS UMTS IuCS over ATM, requires LTS314
LTS314 OC-12 / STM-4 SSCOP Server
LTS317 OC-12 / STM-4 AAL2 Traffic Core
  Related Software
PKS164 MAPS™ UMTS IuPS interface
XX165 T1 or E1 UMTS Protocol Analyzer
OLV165 Offline UMTS Protocol Analyzer
LTS206 OC-3 / STM-1 UMTS Protocol Analysis
LTS306 OC-12 / STM-4 UMTS Protocol Analysis
PKS140 MAPS™ LTE S1 Emulator
PKS142 MAPS™ LTE eGTP Emulator
PKS120

PKS121

PKS122

PKS123

PKS124

PKS125

PKS130
MAPS™ SIP Emulator

MAPS™ SIP Conformance Test Suite (Test Scripts)

MAPS™ MEGACO Emulator

MAPS™ MEGACO Conformance Test Suite (Test Scripts)

MAPS™ MGCP Emulator

MAPS™ MGCP Conformance Test Suite (Test Scripts)

MAPS™ SIGTRAN Emulator
PKS100 PacketGen™ with PacketScan™
PKV100 PacketScan™ (Online and Offline)
PKB100 RTP Toolbox™
PKS110 Packet H.323
IPN010 IPNetSim™ - 100Mbps of through bandwidth
IPN100 IPNetSim™ - 1Gbps of through bandwidth
IPN400 IPNetSim™ - 1Gbps w/ 4 links through bandwidth

 

 
 
Home Page Sitemap Global Presence Email