MAPS™ UMTS for IuCS, IuH Interfaces Emulator
(Scripted UMTS IuCS and IuH Emulation over IP)
Background
Universal Mobile Telecommunications System (UMTS) is a 3rd generation mobile technology evolved from GSM (2nd generation) technology.
It uses W-CDMA (Wideband CDMA) as radio access technology. With increased spectral efficiency and higher bandwidth, the UMTS network can support
greater data rates as well as 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 IP based 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
- and Femto Home Node Gateway (HnB-GW) - provides wired broadband interface
To emulate the various components of UMTS, 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 and DTAP signaling
messages over SCTP. RANAP and DTAP are:
- RANAP – is a control plane protocol (Iu interface) between RNC (Radio Network Controller) and CN (Core Network) in the UMTS stack.
- DTAP - is a layer 3 protocol between the MSC (Mobile Switching Center) and the MS (Mobile Station)
Overview
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 as 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™ also supports RTP traffic simulation (requires additional licensing) over UMTS-IuCS and UMTS-IuH interfaces. RTP traffic simulation supports the
following actions for almost all standard codecs:
- Transmitting Voice File
- Transmitting DTMF, MF Digits and other Tones and Dual Tones
- Recording Voice Files
- Monitoring Single and Dual Tones, DTMF and MF digits
- Loopback, Talk using Microphone, Play to Speaker
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)
GL Communications also supports the following UMTS analyzers and simulators:
Main Features
- Simulates RNC, MSC, Home NodeB (HnB) and Home NodeB Gateway (HN GW) entities.
- Generates and process all Mobility Management, Session Management, RANAP and DTAP messages.
- User controlled access to RANAP, and DTAP messages.
- Ready scripts for Mobile Originating, Mobile Terminating, Location Updating 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 RTP traffic generation and reception (requires additional license)
- Supported Codecs:
- G.711 (A-law / Mu-law - 64kbps), G.711 App II (ALaw and MuLaw with VAD Support), G.729, G.729B (8 kbps), G.726
(5 bit 40 kbps/4 bit 32 kbps/3 bit 24 kbps/2 bit 16 kbps), G726 (40/32/24/16 kbps with VAD), GSM (13.2 kbps)
- AMR (4.75, 5.15, 5.9, 6.7, 7.4, 7.95, 10.2, & 12.2 kbps) (optional codec)
- AMR_WB
- EVRC (Rates - 1/8, ½ and 1), EVRC0 (optional codec), EVRC_B (Rates - 1/8, ¼, ½, and 1), EVRCB0 (optional codec), EVRC_C
- SMV (Modes - 0, 1, 2 and 3- Available if licenses are provided or owned, please call GL)
- iLBC (for 20msec), iLBC_13_33 (for 30msec)
- SPEEX, G722, G722.1, SPEEX_WB, iSAC (optional codec)
- Supports customization of call flows and message templates using Script editor and Message editor.
- Supports scripted call generation and automated call reception.
- Provides protocol trace with full message decoding, and graphical ladder diagrams of call flow with time stamp
- Script based & protocol independent software architecture.
- Provides call statistics and associated captured events and error events during call simulation.
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 |
| 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 |
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 IuCS, and IuH interfaces.
Screenshot of Testbed Setup to configure MAPS™ as UMTS
IuCS and IuH Nodes
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. 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.
IuCS Interface
In IuCS interface, MAPS™ acts as either RNC to test MSC (DUT) or MSC to test RNC (DUT) and simulates the following call flow scenarios:
Testing MSC (Mobile Originating Call (MOC) Flow)
Mobile Originating Call Scenario
The MOC call is initiated by the user equipment (UE). On receiving the CM Service Request message from UE, the network initiates authentication
procedures. After the authentication procedures, the request is accepted and the Call Control procedures will start and the call is established.
The MAPS™ acts as RNC and initiates the Mobile Originating Call flow by sending CM Service Request to the DUT (MSC). The DUT on receipt of a
CM SERVICE REQUEST message sends a CC connection confirm message in response MAPS™ then completes the call as in Mobile Originating Call (MOC)
call flow.
MAPS™ UMTS IuCS configured to act as RNC
MOC Call Generation Flow at RNC Node
Whenever Mobile Station (MS) moves out of its location to a new location then it needs to inform the network about its new location. The UE initiates
the call by sending location update message to network & on receiving acknowledgment, the LU call gets terminated.
The MAPS™ can act as RNC initiating the Location Updating Call flow by sending Location Updating Request to the Network (MSC). The DUT on
receipt of a LOCAION UPDATING REQUEST message sends a CC Connection Confirm message in response MAPS™ then simulates the completes the
call as in Location Updating Call (LUC) call flow.
Screenshot of Location Updating Call Scenario
Screenshot of LUC Call Generation Flow at RNC Node
Testing RNC (Mobile Terminating Call (MTC) Flow)
The MTC is initiated by Network by sending Paging message towards UE. Here, the UE is the receiver of a call. UE will send the Paging Response message.
The rest of the call flow is same as a MOC call. MAPS™ can act as Mobile Station Controller (MSC) processing the call flow by initiating the Paging message
to the Mobile Station (RNC). The DUT (RNC) on receipt of a Paging message sends a Paging Response message back to MSC. MAPS™ then completes the
call as in Mobile Terminating Call (MTC) flow.
Screenshot of Mobile Terminating Call Scenario
Screenshot of MAPS™ UMTS configuration at MSC node
Screenshot of MTC Call Generation Flow at MSC Node
IuH Interface
The IuH Interface Emulator simulates RANAP signaling and call control messages between the HnB-GW and HnB nodes. MOC, MTC, and LU call
flows scenarios have been explained for the interface.
Testing HnB-GW (Mobile Originating Call (MOC) Flow)
MAPS™ acts as HnB and tests the DUT that is configured to act as Home Node B- Gateway (HnB-GW). Here, MAPS™ initiates the Mobile
Originating Call messages towards HnB-GW and responds to messages from HnB-GW (DUT).
The test is performed to ensure that the MAPS™ (HnB) sends CM SERVICE REQUEST to DUT (HnB-GW). The DUT on receipt of a
CM SERVICE REQUEST message starts Authentication Procedure by sending Authentication Request message as depicted in
the figure.
Screenshot of Mobile Originating Call (MOC) Flow
Screenshot of MAPS™ UMTS IuH configuration at HnB node
Screenshot of MOC Call Generation Flow at HnB Node
Testing HnB-GW (Location Updating Call (LUC) Flow)
Whenever mobile station (MS) moves out of its location to a new location then it needs to inform the network about its new location. The test is performed
to ensure that the MAPS™ (HnB), UE initiates the Location Updating procedure by sending LOCATION UPDATING REQUEST to DUT (HnB-GW). HnB-GW on
receipt of Location Updating Request message starts Authentication Procedure by sending Authentication Request message as depicted in the figure, provided
as a link below.
Screenshot of Location Updating Call (LUC) Flow
Screenshot of LUC Call Generation Flow at HnB Node
Testing HnB (Mobile Terminating Call (MTC) Flow)
MAPS™ acts as HnB-GW and test the DUT that is configured as HnB (Home Node B). Here, MAPS™ initiates the Mobile Terminating Call
messages towards HnB and responds to messages from HnB (DUT). IuH interface signaling scenario (messages between HnB (Home Node B) and
HnB-GW (Home Node B - Gateway)) is same as IuCS Call scenario.
The test is performed to ensure that the MAPS™ (HnB-GW) at network initiates the paging procedure for CS services by sending PAGING
request to DUT (HnB).The DUT (RNC) on receipt of a Paging message sends a Paging Response message back to MSC. MAPS™ then completes the call
as in Mobile Terminating Call (MTC) call flow.
Screenshot of Mobile Terminating Call (MTC) Flow
Screenshot of MAPS™ UMTS IuH configuration at HnB Gateway node
Screenshot of MTC Call Generation Flow at HnB-GW 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.
IuCS Interface
Testing RNC (MOC Call Flow)
This test is performed to ensure that the MAPS™ (MSC) on receipt of a CM SERVICE REQUEST message from RNC, sends a CC Connection Confirm
message in response. MAPS™ then completes the call as in Mobile Originating Call (MOC) call flow.
MOC Call Reception Flow at MSC Node
Testing RNC (LUC Call Flow)
This test is performed to ensure that the MAPS™ (MSC) on receipt of a LOCATION UPDATING REQUEST message from RNC, replies with CC
connection confirm message as depicted in the figure.
Screenshot of LUC Call Reception Flow at MSC Node
Testing MSC (MTC)
This test is performed to ensure that the MAPS™ (RNC) on receipt of a PAGING Message from MSC, replies with PAGING RESPONSE message as
depicted in the figure. MAPS™ (RNC) then completes the call as in MTC call flow.
Screenshot of MTC Call Reception Flow at RNC Node
IuH Interface
Testing HnB (MOC)
This test is performed to ensure that the MAPS™ (HnB-GW) on receiving service request initiates Authentication Procedure, sends Authentication
Request message as a response to HnB (DUT).
MOC Call Reception Flow at HnB-GW Node
Testing HnB (LUC Call Flow)
This test is performed to ensure that the MAPS™ (HnB-GW) on receiving LOCATION UPDATING REQUEST initiates Authentication process, sends
Authentication Request message as a response to HnB (DUT).
Screenshot of LUC Call Reception Flow at HnB-GW Node
Testing HnB-GW (MTC Call Flow)
This test is performed to ensure that the MAPS™ (HnB) on receipt of a PAGING Message from HnBGW, replies with PAGING RESPONSE message
as depicted in the figure. Also, MAPS™ (HnB) simulates the complete call flow as in MTC call flow.
Screenshot of MTC Call Reception Flow at RNC 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-iucs-iuh-web-testbedsetup.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-lucflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-luc-callgen.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-mtcflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-mapsmsc.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-mtc-callgen.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-mocflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-mapsHNB.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-moc-callgen.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-lucflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-luc-callgen.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-mtcflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-mapsHNBGW.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-mtc-callgen.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-luc-callrec.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iucs-mtc-callrec.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-luc-callrev.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-iuh-mtc-callrev.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-loadgeneration.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-script-editor.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-profile-editor.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-message-editor.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-scriptcontents-scriptflow.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-callstatistics.gif"))
![](javascript:myOpen("images/maps-umts-iucs-iuh-web-eventlog.gif"))
