GSM, TDM and TDMA,

Core interfaces T1 E1
but now migrating to IP

WCDMA, Same Core

network as 2G

LTE, OFDMA, SC-FDMA,

All IP

1
❑ Each LAB test system emulates all the 2G/3G/4G network
elements and traffic types within the Wireless infrastructure.

❑ Provides a base network environment that enables the

researchers to test applications, devices, and services prior to
deployment on real-time networks

2
❑ Multi-protocol, Multi-technology Platform.
❑ Simulate any node, and any interface in network with MAPS™
(except Air interface).
❑ Supports Emulation, Conformance, and Load testing of a
variety of protocols over IP, TDM, and Wireless networks.

3
GL Communications Inc

4
5
Various GSM GPRS network procedures are supported  Mobile to simulated UE SMS (CS)
simulating the 2G elements and multi-interfaces:  Mobile Web Browsing (PS)
 Mobile-to-Mobile Voice Call (CS)
 Mobile Originated Call (MOC)  Simulated UE web browsing (PS)
 Mobile Terminated Call (MTC)  Attach Procedures
 Simulated UE to mobile voice call (CS)  Identity Procedures

 Mobile to Simulated UE voice call (CS)  PDP Context Creation, Activation,

Update Deactivation and Deletion
 Simulated UE to simulated UE voice call (CS)
Procedures
 Mobile-to-Mobile SMS Call (CS)
 Mobile Originated SMS  Web Browsing GPRS Session
 Mobile Terminated SMS  Detach Procedures

 Simulated UE to mobile SMS (CS)

6
7
• Real BTS • Real BTS • Real BTS • Real BTS
• Sysmo BTS GSM Cell • Sysmo BTS GSM Cell • Sysmo BTS GSM Cell • Sysmo BTS GSM Cell
• Mobile Phones • Mobile Phones • Mobile Phones • Mobile Phones
• SIMs • SIMs • SIMs • SIMs
• Abis
• Abis • Abis • Gb
• PKS134 MAPS™ GSM Abis IP
• PKS134 MAPS™ GSM Abis IP • A • PKS134 MAPS™ GSM Abis IP • PKS131 MAPS™ SGSN Multi-
• A • PKS137 MAPS™ GSM A IP • A Interface
• C, D, and E • ETH102 Mobile Traffic-GW
• PKS137 MAPS™ GSM A IP • PKS137 MAPS™ GSM A IP
• PKS102 RTP Core (only @ MSC) • PKS132 MAPS™ MAP IP • PKS102 RTP Core (only @ MSC) • Gn Gp
• High Density Bulk Calling • PKS166 MAPS™ Gn Gp
• C, D • C, D
• MAPS™ High Density RTP • ETH102 Mobile Traffic-GW
• PKS132 MAPS™ MAP IP Generator • PKS132 MAPS™ MAP IP
• Gr
• High Density Bulk Calling • ISUP
• PKS132 MAPS™ MAP IP
• MAPS™ High Density RTP • XX649 MAPS™ SS7 TDM with T1 E1
Generator • Real BTS Hardware • High Density Bulk Calling
• Sysmo BTS GSM Cell • PKS145 Media Gateway Conversion
• PacketLoad 4x10G Data Traffic
• Mobile Phones, SIMs
• Analog Simulation Generator
• Gb
• XX624 MAPS ™ FXO FXS tProbe™ T1 E1
• PKS131 MAPS™ SGSN Multi-Interface
Hardware
• Gr, Gd
Or
• PKS132 MAPS™ MAP IP
• XX651 MAPS ™ CAS with T1 E1 Hardware
• High Density Bulk Calling
and APS
• PacketLoad 4x10G Data Traffic
Generator
8
9
• Abis • Abis • Abis • Gb
• PKS134 MAPS™ GSM Abis IP • PKS134 MAPS™ GSM Abis IP • PKS134 MAPS™ GSM Abis IP • PKS131 MAPS™ GPRS Gb
• A • A • A • PKS131 MAPS™ SGSN Multi-
• PKS137 MAPS™ GSM A IP Interface
• PKS137 MAPS™ GSM A IP • PKS137 MAPS™ GSM A IP
• PKS102 RTP Core (only @ MSC) • ETH103 MobileTrafficCore Gb
• C,D, and E • PKS102 RTP Core (only @ MSC)
• ETH102 MobileTrafficCore GW
• C, D • C, D
• PKS132 MAPS™ MAP IP • Gn Gp
• PKS132 MAPS™ MAP IP • PKS132 MAPS™ MAP IP
• High Density Bulk Calling • PKS166 MAPS™ Gn Gp
• High Density Bulk Calling • MAPS™ High Density RTP • ISUP • ETH102 MobileTrafficCore GW
• MAPS™ High Density RTP Generator • XX649 MAPS™ SS7 TDM with T1 E1 • Gr
Generator Hardware
• PKS132 MAPS™ MAP IP
• PKS145 Media Gateway Conversion
• Analog Simulation • High Density Bulk Calling
• Gb
• XX624 MAPS™ FXO FXS tProbe™ T1 E1 • PacketLoad 4x10G Data Traffic
• PKS131 MAPS™ GPRS Gb Hardware Generator
• PKS131 MAPS™ SGSN Multi-Interface Or
• ETH103 MobileTrafficCore Gb • XX651 MAPS™ CAS with T1 E1 Hardware
• Gr, Gd and APS
• PKS132 MAPS™ MAP IP

• High Density Bulk Calling

• PacketLoad 4x10G Data Traffic
Generator
10
GTP-u SM

SNDCP GMM
CM | MM | RR | SMS MAP
LLC MM | CC | RR | SMS BSSAP TCAP
ISUP
SCCP SCCP
BSSGP BTSM MTP3 MTP Level 3
M3UA M3UA GTP-u
NS M2PA MTP Level 2
TCP SCTP GTP
SCTP UDP
Physical Layer MTP Level 1
IP IP IP IP
Gb Abis A C, D, E, Gr Gn SS7
11
Supported Protocols Standard / Specification Used

SCCP Q.713, CCITT (ITU-T) Blue Book

MTP3 ITU-T Q.704

BSSMAP / DTAP 3GPP TS 08.08 V8.9.0

MM 3GPP TS 04.08 V7.17.0

CC 3GPP TS 04.08 V7.17.0

RR 3GPP TS 04.18 V8.13.0

3GPP TS 03.40 V7.5.0 &

SMS
3GPP TS 04.11 V7.1.0 GSM 03.38 version 7.2.0 Release 1998

12
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

GTP TS 29.060 V9.2.0 (2010-03)

13
Supported Protocols Standard / Specification Used

BSSGP 3GPP TS 08.18 V8.10.0 (2002-05)

LLC 3GPP TS 04.64 V8.7.0 (2001-12)

NS (Network Service) GSM 8.16 (ETSI TS 101 299 V8.0.0)

GMM 3GPP 24.008

SMG (GPRS Session Mgmt) 3GPP TS 24.008 V5.16.0 (2006-06) (Release 5)

SNDCP 3GPP TS 04.64 V8.7.0 (2001-12)

14
Supported Protocols Specification Used
SCCP Q.713, CCITT (ITU-T) Blue Book
SCTP RFC 4960
TCP RFC 793
M3UA RFC 3332

BSSMAP/DTAP 3GPP TS 08.08 V8.9.0, 3GPP TS 48.008 V10.0.0 (2011-01)

MM / CC 3GPP TS 04.08 V7.17.0

RR 3GPP TS 04.18 V8.13.0

3GPP TS 03.40 V7.5.0 & 3GPP TS 04.11 V7.1.0 GSM 03.38

SMS
version 7.2.0 Release 1998

15
16
❑ Mobile Originated Call (MOC)
❑ CHANNEL REQUEST
❑ AUTHENTICATION, CIPHERING, VALDATION
❑ CALL SETUP REQUEST
❑ ALLOCATING DEDICATED VOICE CHANNEL OVER AIR INTERFACE
❑ Mobile Terminated Call (MTC)
❑ PAGING
❑ IDENTITY & AUTHENTICATION, CIPHERING
❑ LOCATION UPDATE
❑ CALL SETUP REQUEST
❑ ALLOCATING DEDICATED VOICE CHANNEL OVER AIR INTERFACE
❑ LOCATION UPDATE (LU) CALL

17
18
19
20
21
❑ Mobile Terminated SMS
❑ Mobile Originated SMS

22
23
24
25
26
❑ CHANNEL REQUEST PROCEDURE

❑ SIGNALING CHANNEL ASSIGN PROCEDURES

❑ CM SERVICE REQUEST PROCEDURES

❑ AUTHENTICATION PROCEDURES

❑ TRAFFIC CHANNEL ASSIGN PROCEDURES

❑ RTP MEDIA PROCEDURES

❑ RELEASE PROCEDURES

27
28
1 Attach Request
2 Authentication
3 Update GPRS Location
4 Attach Accept
5 Attach Complete
6 Activate PDP Context
7 Create PDP Context
8 Respond with IP/DNS Address
9 Activate PDP Context Response
10 HTTP Traffic

29
30
31
❑ The RTP HD server network appliance
supports generation of high volume of
calls with traffic for load testing 2G/3G
networks

❑ Specialized 1U rackmount appliance,

achieve up to 20,000 endpoints per
appliance (5000 simultaneous calls with
duplex traffic per port)

❑ Available with 4 x 1 Gbps NIC ports (SFP)

32
❑ The load (high density real-time traffic and signaling)
simulated in the above lab setup across 2G/3G/4G
networks can be evenly distributed in round-robin
fashion over the 4x HD ports on the RTP HD system, so
that incoming requests may be evenly distributed among
all of them.
❑ Each HD port is capable of 5000 simultaneous calls with
duplex traffic. Once the port limit is reached the load is
distributed across the remaining HD ports available in
the system.
❑ 2G SETUP
❑ BSC connected to Port 0 (P0), Port 1 (P1)
❑ MSC connected to Port 2 (P2), Port 3 (P3)
❑ 3G SETUP
❑ MSC connected to Port 0 (P0), Port 1 (P1)
❑ RNC connected to Port 2 (P2), Port 3 (P3)

33
❑ PacketLoad 4 x 10Gbps (PKS174) is a Data Traffic Generator 2U Rack Appliance with 4 x 10Gbps NIC
interfaces: total capacity of up to 40 Gbits/sec Stateful TCP/HTTP Traffic.
❑ It supports massive simulation of UEs (up to 500,000) with high density (up to 4 Gbps or 40 Gbps) mobile data
traffic simulation for both UMTS, and LTE networks.
❑ The solution allows to encapsulate the generated packet data within GTP headers and transmit through the
gateway points such as SGSN & GGSN, or SGW & PGW. It allows simultaneous simulation of multiple sessions
per user to verify bearer allocation bandwidth at the end points. Currently, the solution offers stateful
TCP/HTTP, and PCAP Replay traffic types.
❑ PacketLoad supports HTTP traffic simulation with the base requirements such as port number, server IP
address, and pre-canned HTTP traffic file.

34
35
❑ ATTACH PROCEDURES

❑ IDENTITY PROCEDURES

❑ ROUTING AREA PROCEDURES

❑ PDP CONTEXT CREATION, ACTIVATION, UPDATION, DEACTIVATION and DELETION

PROCEDURES

❑ WEB BROWSING SESSION

❑ DETACH PROCEDURES

36
37
38
39
40
41
42
❑ Cycle through the nodes in Remote
Controller and verify the Link Status of the
following nodes:

Simulated BSC (AoIP) ←→ MSC

BSC GW (Abis + AoIP) ←→ MSC (10.10.1.11)

BSC GW (Abis + AoIP) ←→ BTS (10.10.1.7)

MSC ←→ BSC (10.10.1.13)

MSC ←→ BSC GW (10.10.1.10)
MSC ←→ HLR (2G) (10.10.1.12)
MSC ←→ SMSC (2G) (10.10.1.17)
MSC ←→ HLR (3G) (10.10.1.22)
MSC ←→ SMSC (3G) (10.10.1.27)
MSC ←→ MGC (10.10.1.19)
MSC ←→ MSC (3G) (10.10.1.21) (6905)
Link Status for 3G connections are available if the 3G setup is running MSC ←→GMSC(3G) (10.10.1.21) (7905) BICC
43
 Phone numbers are defined in the table
below

 Dial the MSISDN of the desired phone

IMSI MSISDN
901701234561001 9017061001
901701234561002 9017061002
901701234561003 9017061003
901701234561004 9017061004
901701234561005 9017061005
901701234561006 9017061006

44
 Phone numbers are defined in the table
below

 Send SMS to the MSISDN of the desired

phone

IMSI MSISDN
901701234561001 9017061001
901701234561002 9017061002
901701234561003 9017061003
901701234561004 9017061004
901701234561005 9017061005
901701234561006 9017061006

45
46
❑ INTER NETWORK CALLS
❑ 2G USER CALLING 3G USER
❑ 2G USER CALLING 4G USER
❑ ROAMING CALLS
❑ 2G USER CALLING 3G ROAMING USER
❑ 2G USER CALLING 4G ROAMING USER

47
❑ When a voice call or SMS call is
placed from UE1 to UE2, MSC
on 2G network receives call
from UE1 and checks for the
received MSISDN registration
using MAP table. If MAP is
found then call is routed within
same network otherwise call is
routed to 3G MSC. MSC in the
3G network routes the request
to 3G user.

48
❑ 3G MSC extracts called
MSISDN from the received
Initial Address Message and if
the user registration is verified
with the network, Paging is
initiated towards RNC.

❑ 3G MSC On reception of
PAGING, RNC will respond with
Paging Response and end-to-
end call is established from 2G
user to 3G user.

49
❑ When a voice call is placed
from UE1 to UE2, MSC on 2G
network receives call from UE1
and checks for the received
MSISDN registration using MAP
table. If MAP is found then MSC
checks 4G CSV. If MSISDN is
available in 4G CSV then call is
routed to MGC.

50
51
52
 HLR performing Cancel Location with
Previous Registered MSC
❑ When 2G user calls 4G roaming user, MSC receives Call and checks Called MSISDN registration in MSC.
❑ Flexible MAPS™ architecture to test emerging technologies including UMTS, LTE better known as 3G, 4G, IP
networks (such as SIP, MGCP, MEGACO, SIGTRAN), and legacy networks (such as CAS, SS7 and ISDN)

❑ Multi-Interface and Protocol Simulation over different transports layers - IP network (TCP, UDP, SCTP, IPv4 and
IPv6), TDM network (MTP2, and LAPD) links

❑ Multi-Homing feature is supported in SCTP for simulating multiple nodes

❑ Automation Features –

❑ Execution of the multiple calls sequentially or randomly to handle incoming and outgoing calls

❑ Automation via CLI clients (TCL, Python, ...)

❑ Scheduler to load pre-defined test bed setups and configuration files to automate test process at
specified time.

❑ Control multiple nodes via Remote Access and run tests

58
❑ Load, Stress, and Performance, Testing to measure the capability of an entity for various traffic conditions.

❑ Load /Stress test with different statistical distribution patterns with capacity of 2000 simultaneous calls,

@ 500 call per second rate

❑ Control and operate MAPS™ remotely, also gather statistics, logs and reports.

❑ Traffic Simulation to perform end-to-end testing of various traffic - mobile traffic simulation over GTP,
transmit/record real time voice traffic, DTMF and MF digits, user defined single/dual tones over established
channels

59