MAPS™ UMTS for IuPS Interface Emulator
(Scripted UMTS IuPS Emulation over IP)
Background
UMTS is 3rd generation mobile technology evolved from GSM technology and uses W-CDMA as radio access technology. With increased spectral
efficiency and high bandwidth the UMTS network can support high-bandwidth data, digitized voice and video data to the wireless users. The underlying
transport layer for UMTS can be asynchronous transfer mode (ATM), or an IP. IP based UMTS supports integrated services such as multimedia and global
roaming to mobile users.
|
|
|
The IP based UMTS network consists of the following components -
- Radio Network Controller (RNC)
- Mobile Switching Centre (MSC)
- Serving GPRS Support Node (SGSN)
- Gateway GPRS Support Node (GGSN)
- NodeB
- Femto Home NodeB (Femto Cell) and Femto Home Node Gateway (HNB-GW)
Overview
GL’s Message Automation & Protocol Simulation (MAPS™) designed for testing UMTS IuPS interface can simulate RNC
(Radio Network Controller), and 3G SGSN (3G Serving GPRS Support Node) by generating RANAP and DTAP signaling messages over
SCTP as Transport layer in an IP network as defined by 3GPP standards.
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™ - IuPS (Item # PKS164)
GL Communications supports the following UMTS analyzers and simulators:
Main Features
- Simulates RNC, and SGSN entities.
- Generates and supports all Mobility Management, Session Management, RANAP and DTAP messages.
- User controlled access to RANAP, and DTAP messages.
- Ready scripts for Routing Area Updating, GPRS Attach, and Detach procedures for quick testing.
- Supports Authentication, TMSI Reallocation, Encryption, and other optional procedures
- Provides fault insertion, and erroneous call flows testing capability.
- Impairments can be applied to messages to simulate error conditions
- Supports customization of call flows and message templates using Script editor and Message editor.
- Supports scripted call generation and automated call reception.
- Provides detail protocol trace with full message decoding, and graphical ladder diagrams of call flow with time stamp
- Call flow graph allows to easily verify the messages exchanged with DUT
- Displays call status, results, call information, total iterations to be done, and completed iterations
- Script based & protocol independent software architecture.
- Provides call statistics and associated captured events and error events during call simulation.
Supported Protocol Standards
UMTS IuPS Protocol Stack
| Supported Protocols |
Specification Used |
| IuPS Interface |
| SCCP |
Q.713, CCITT (ITU-T) Blue Book |
| M3UA |
RFC 3332 |
| RANAP |
3GPP TS 25.413 V9.1.0 |
| GMM / SM |
3GPP TS 24.008 V5.16.0 (2006-06) |
| SMS |
3GPP TS 03.40 V7.5.0 & 3GPP TS 04.11 V7.1.0 GSM 03.38 version 7.2.0 Release 1998 |
Test Configuration
The test configuration window allows users to configure the necessary parameters in order to establish communication between MAPS™ and the DUT.
The MAPS™ UMTS configuration window consists of SCTP configuration for Iu--PS interfaces.
Screenshot of Testbed Setup to configure MAPS™ as IuPS Nodes
Call Generation
Typical Call Flow between the UMTS IuPS network entities
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. Messages are exchanged between the
MAPS™ and the DUT. MAPS™ application acts as either the Caller or resides at the network terminal acting as Callee.
The IuPS Interface Emulator simulates RANAP signaling and call control messages between the RNC and SGSN nodes. In this document, we are considering
the call flow between the RNC and SGSN nodes for Attach Request and Routing Area Updating (RAU).
Testing SGSN (Attach Procedure)
As depicted in figure below, MAPS™ - IuPS acts as RNC processing the call flow and responds to messages from SGSN Node.
MAPS™ UMTS IuPS configured as RNC
The MAPS™ - acts as RNC and initiates the Attach Procedure by sending Attach Request to the DUT (SGSN). The DUT on receipt of ATTACH REQUEST
message should send a CC connection confirm message in response as shown in the figure below. Also MAPS™ then completes the call as in IuPS Call
Scenario.
Call Generation at RNC 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.
Testing RNC
As seen in the figure below, MAPS™ acts as SGSN, and tests the DUT that is configured as RNC. MAPS™ responses to the messages received
from RNC
MAPS™ UMTS IuPS configured as SGSN
This test is performed to ensure that the MAPS™ (SGSN) on receipt of ATTACH REQUEST message from RNC, sends a CC connection confirm message
in response. MAPS™ then completes the call flow.
Call Reception at SGSN 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
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
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.
Buyer's Guide:
Specifications are subject to change without notice.
Back to Message Automation & Protocol Simulation Index Page
![](javascript:myOpen("images/maps-umts-iups-web-testbed-setup.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-load-generation.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-script-editor.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-profile-editor.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-message-editor.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-script-content-flow.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-statistics.gif"))
![](javascript:myOpen("images/maps-umts-iups-web-event-log.gif"))
