ZTE Full Signaling Trace Solution

December 2nd, Slough

Fernando Jiménez Ramírez

RAN Product Manager
fernando.jimenez@zte.com.cn
Content

ZTE Full Signaling Trace for GU

ZTE Full Signaling Trace for LTE

Full Signaling Trace Solution for Ecuador

2
ZTE GU Full Signaling Trace System Architecture
Interface
The interface between NDS and
AS is based on FTP protocol.
Definition of the element

NDS (Network Data Server) - Gathering

the data from controllers, providing
uniform access interface
AS(Analysis Server) - Analysis of the
signaling data. Usually, it is always third-
party’s professional system, such as Arieso
GEO)
Third Party Client, providing GUI for users

Objective Collect the signaling statistic data for upper analysis system
© ZTE Corporation. All rights reserved.
Full Signaling Tracing Schedule

Enable signaling RNC/BSC runs

collection Function statistic process to Data reported to
in BSC/RNC produce the data NDS server
Controller in UMP/SBCX

Data Collection The statistic file is a The data can be

License = the Number binary format, less used for upper
of the BSC/RNC than 100M, the time system’s utilization
granularity is 5min.

© ZTE Corporation. All rights reserved.

Messages to be Collected
Messages to be Collected by ZTE GU Full Signaling Trace System

UMTS:
UU、IUB、IU、IUR Standard Interface Messages and UE
related signaling.

GSM:
UM、ABIS、 A、 GB Standard Interface Messages and UE
related signaling.

© ZTE Corporation. All rights reserved.

NDS Server Dimensioning Principle
The hardware configuration of NDS server is related to the data volume and the
BSC/RNC number. NDS Deployment Principle is listed as below.
The NDS Deployment Principle
Area NDS Number Supported RNC or BSC Number
Area 1 (UMTS V3) 1 NDS <=6 RNCs
Area 2 (UMTS V4) 1 NDS <=6 RNCs
Area 3 (GSM V4) 1 NDS <=10 BSCs

The total data volume and bandwidth

Average data/day Totally data for 3 NDS data save Bandwidth for each
Controller Type
(GB) days volume BSC/RNC
UMTS V3 106G/RNC 318G/RNC 6*318G=1.9T <150Mbps/RNC

UMTS V4 300G/RNC 900G/RNC 6*900G=5.4T <390Mbps/RNC

GSM V4 80G/BSC 240G/BSC 10*240G=2.4T <134Mbps/BSC

© ZTE Corporation. All rights reserved.
Typical NDS Configuration
One set of the typical NDS-GU configuration

Hardware Num Remarks

DELL PER920 (No HDD)4CPU 2GHz(or 1
above)/Memory:8*8GB
DELL PER920 HardDisk-D5:600G(6G SAS,10K,2.5") 2
HBA CARD (Dual-Port) 1
FUJITSU DX100 S3 Disk Array(2.5“) 1
FUJITSU DX100 S3 Disk 600G 10 Based on Data Volume
FUJITSU ETERNUS Multipath Software 1

Redhat Linux 1

© ZTE Corporation. All rights reserved.

BSC/RNC Configuration Principle

The BSC/RNC Upgrade Configuration Principle

1. One UMP board needs to be added in slave shelf for RNC V4/BSC V4
One SBCX and one RSVB board need to be added in switch shelf or resource shelf
for RNC V3
If there is no extra slots in existing system, then an additional shelf and related
boards should also be added.

2.Besides HW upgrade, SW should be upgraded to UR13

© ZTE Corporation. All rights reserved.

 Successful Integration with Arieso in MTN
Time Schedule for Integration with Arieso
Nov,2013 Dec, 2013 Feb, 2014 April,2014

Internal delivery 1.System integration test in 1.IOT in testbed Simulate high-

version is ready R&D lab, bug fix and
regression test
2.ZTE provide ftp server for
joint debugging, MTN pull file
from ZTE internal lab
3.ZTE evaluate requirements
and implement in joint
debugging
2.ZTE evaluate capacity and peak-
requirements and load stability test
implement in joint
debugging
The Collected Signaling data Imported to
GEO Successfully !

© ZTE Corporation. All rights reserved.

Content

ZTE Full Signaling Trace for GU

ZTE Full Signaling Trace for LTE

Full Signaling Trace Solution for Ecuador

10
ZTE LTE Full Signaling Trace System Architecture
Interface
The interface between NMS and
NDS is northbound interface,
based on FTP protocol.
Definition of the element
NDS (Network Data Server) - Gathering
the data from controllers, providing
uniform access interface
UDT(Unified Data Trace) - a trace tool
integrated in EMS, used for launching a
trace command
Objective
Collect the signaling statistic data
for upper analysis system

© ZTE Corporation. All rights reserved.

 > 内部公开

Two Ways of LTE Call Tracing

Trace Framework based on IMSI Trace Framework based on Cell

1.Trace Session
（IMSI）
S1
5.Trace Record /
S1 IMSI

3.TraceStart MME 4.CellTrafficTrace MME

EM
6.Trace Record

3.Trace Record 6.Trace Record

5.Trace Record
Adapter
NDS NDS
4.Trace Record

Adapter 1.Trace Session

eNodeB
eNodeB

EM
2.Random Access 2.Random Access
Uu
Uu

UE UE

12
© ZTE Corporation. All rights reserved.
Messages to be Collected and Files to be Generated
Messages to be Collected by ZTE LTE Full Signaling Trace System
Standard signaling (S1, X2 and Uu) based on IMSIs or Cells.
Tracing file format, granularity and size
The tracing file is XML format, compliant with 3GPP TS32.422.
The trace data granularity is 5 minutes. Trace data file generating period
supports customer setting. The optional periods are 5 minutes, 10 minutes and 15
minutes.
The NDS generates trace file according to Trace data granularity for a specific UE
or a specific cell, and the file size is related to the collected period and UE number.
For example: if 10 minutes is set as Trace generating period for IMSI based
tracing, each Trace data file will contain 10 minutes’(2 file data granularity) data
for the specific UE.
© ZTE Corporation. All rights reserved.
NDS Server Dimensioning Principle
The NDS Deployment Principle
Scale of Cell NDS Server
<=4000 Cell 1* NDS (4*12C 2.3Hz，Memory 64G，Hard disk 2*600G+Raid：20*600G)
<=8000 Cell 2* NDS (4*12C 2.3Hz，Memory 64G，Hard disk 2*600G+Raid：20*600G)
<=12000 Cell 3* NDS (4*12C 2.3Hz，Memory 64G，Hard disk 2*600G+Raid：20*600G)
<=16000 Cell 4* NDS (4*12C 2.3Hz，Memory 64G，Hard disk 2*600G+Raid：20*600G)

The bandwidth between eNB and NDS, between NDS and NMS is decided by several factors,
such as traced UE numbers, data size sampled per second, etc. ZTE will give out detail
required for it based on different scenario.
The eNodeB Upgrade Principle

1. LTE Data Collection License = the Number of NDS server

2.UDT(Unified Data Trace) integrated in EMS, used for launching a trace command
3.eNB SW should be upgraded to LR14
© ZTE Corporation. All rights reserved.
Typical NDS Configuration
One set of the typical NDS-L configuration

Hardware Num Remarks

DELL PER920 (No HDD)4CPU 2GHz(or 1
above)/Memory:8*8GB
DELL PER920 HardDisk-D5:600G(6G SAS,10K,2.5") 2
HBA CARD (Dual-Port) 1
FUJITSU DX100 S3 Disk Array(2.5“) 1
FUJITSU DX100 S3 Disk 600G 20 Based on Data Volume
FUJITSU ETERNUS Multipath Software 1

Redhat Linux 1

© ZTE Corporation. All rights reserved.

Content

ZTE Full Signaling Trace for GU

ZTE Full Signaling Trace for LTE

Full Signaling Trace Solution for Ecuador

16
Ecuador: Current Network Overview

• 4 BSC(V3) and 6 RNC(V3) in existing network and 1 RNC(V4) to be installed.

Data collection point Controller Type Controller Number

Data collection point 1
RNC V3 4
(Guayaquil)
Data collection point 2 RNC V3 2
(Quito) RNC V4 1

Note: Call Tracing for BSC(V3) is not planned yet.

© ZTE Corporation. All rights reserved.

Ecuador : GU Signaling Trace Solution
--Network Upgrade for Signaling
AS
Add 2 NDS, including
server, disk array, switch

(Guayaquil) (Quito)

RNC upgrade: add SBCX boards for V3 RNC

add UMP boards for V4 RNC

Besides HW upgrade, SW should

4 RNC(V3) in same room 2 RNC(V3) and 1 RNC(V4)in same room be upgraded to UR13
© ZTE Corporation. All rights reserved.
NDS Configuration for GU Signaling Trace in Ecuador
Hardware Num Remarks
DELL PER920 (No HDD)4CPU 2GHz(or 2
above)/Memory:8*8GB
DELL PER920 HardDisk-D5:600G(6G SAS,10K,2.5") 6
HBA CARD (Dual-Port) 2
FUJITSU DX100 S3 Disk Array(2.5“) 2
FUJITSU DX100 S3 Disk 600G 27 Based on Data Volume
FUJITSU ETERNUS Multipath Software 2

Redhat Linux 2
Software & Service Num Remarks
NDS Collection SW 7 Based on RNC num
NDS itf-N Connection 7 Based on RNC num
NDS Installation & Connection 7 Based on RNC num
Signaling Reporting SW 7 Based on RNC num
NDS SW Maintenance 1
Field Service 1
© ZTE Corporation. All rights reserved.
Ecuador : RNC(V3) Upgrade
Before After

• Add 1 SBCX (front board)

and 1 RSVB (back board)
in Switch Shelf

© ZTE Corporation. All rights reserved.

Ecuador : RNC(V4) New Deployment
RNC(V4) New Deployment
• Add 2 UMP boards (1+1 backup) in
slot5/6 in Resource Shelf,
considering the signaling tracing
function from the beginning

© ZTE Corporation. All rights reserved.

NDS Configuration for LTE Signaling Trace in Ecuador
Assumption of Ecuador LTE Network Scale: 326 sites, 978 cells.
Recommended configuration for O2 Network Assumption
Hardware Num Remarks

DELL PER920 (No HDD)4CPU 2GHz(or above)/Memory:8*8GB 1

DELL PER920 HardDisk-D5:600G(6G SAS,10K,2.5") 2

HBA CARD (Dual-Port) 1

FUJITSU DX100 S3 Disk Array(2.5“) 1

FUJITSU DX100 S3 Disk 600G 20 Based on Data Volume

FUJITSU ETERNUS Multipath Software 1

Redhat Linux 1

Software & Service Num Remarks

NDS Collection SW 1 Based on eNodeB num
NDS itf-N Connection 1 Based on eNodeB num
NDS Installation & Connection 1 Based on eNodeB num
NDS SW Maintenance 1
Field Service 1

© ZTE Corporation. All rights reserved.

www.zte.com.cn