How ZTE NDS Works

NDS Architecture & Main Functions

2 FST/MR
3rd Party Tool/NMS NDS Main Functions

① Collect L3DC Raw data from NE periodically

according to the configured strategy.
Processed data
1 L3DC Raw Data 3
② Generate various northbound interface files

NDS for 3rd NMS.

③ Provide pre-processed data to ZTE tool

Netmax/VMAX
System
NE Management CM/PM Data

UME

2
Q&A -1
L3DC Solution is part of OSS/EMS and is not a separated solution.

Why ZTE separate EMS and L3DC solution

In ZTE RAN OSS Solution, UME is designed to manage RAN

NEs and NDS is designed for optimization data collection.
1 L3DC Raw Data
L3DC Collection They have their own focus.

NDS
We separate the them for the sake of providing more flexible
and combinable options to different operators. (Some small
operators may not pay attention to L3DC data).
NE Management
NE Management
Therefore, we usually provide UME as the basic part, and NDS
UME as the optional part for operators who have L3DC
requirements.

3
Q&A -2
L3DC Data must be readable by the other system/application (Opened and not Encrypted).

Data is encrypted only for Transmission

form NE to NDS
Not Encrypted

2 FST/MR The L3DC Data transmitted from NE to NDS server is

3rd Party Tool/NMS
mounts of fragment of L3DC information. It needs to be
Encrypted for transmit
proceesed on NDS for consolidation.

1 L3DC Raw Data

The reason why ZTE encrypt data is to ensure the security
NDS of information transmission (from site to core room).

ZTE does not encrypt the data sent by NDS to the 3rd party
NMS.

4
Q&A -3
L3DC Data delivered from NE directly to OSS/EMS without any mediation server.

Why ZTE need NDS as the mediation server

Through the explanation of the previous 2 questions,
customer may have the idea why ZTE needs to deploy NDS
2 FST/MR servers.
3rd Party Tool/NMS

Firstly, in order to provide flexible solution for various

1 L3DC Raw Data operators, we designed NDS solution is separated from
EMS.
NDS
Secondly, the L3DC data provided by NE are fragments. We
need NDS server to integrate, process and even complete
the customization required by customers.

5
Q&A -4
L3DC Data is kept in the OSS/EMS only as normal backup and should be able to be delivered to other system
directly using standard format and protocol without any processing in OSS/EMS.

Which kind of L3DC data is supported by NDS

2 FST/MR There are two kinds of data that NDS can provide to the 3rd party
3rd Party Tool/NMS NMS via NBI (for 4/5G): FST (full signaling trace) & MR Data
(Measurement Report)

For FST data, we will provided the oringnal information with xml
Processed data files. Details may refer to the Annex I of this slides.
3

MR data is processed data by NDS with csv file. We provides the

NDS default attributes of MR table. If cusotmer need any customization,
then we need a discussion and some time for development.

Netmax/VMAX

6 MR Data table Example

Annex I - Full Signalling Trace
 FST NBI Content
• Standard L3 signaling include the NG-C,Xn-C,X2-C,E1,F1, Uu interfaces.
• XML format follow 3GPP 38.413, 38.423, 38.473, 36.423, 38.331. Message Name Interface Direction 3GPPProtocol
RRCSetupRequest UU UE to Network TS38.331
RRCReject UU Network to UE TS38.331
MeasurementReport UU UE to Network TS38.331
RRCReconfiguration UU Network to UE TS38.331
5GC RRCSetup UU Network to UE TS38.331
RRCReconfigurationComplete UU UE to Network TS38.331
AMF UPF
RRCResume UU Network to UE TS38.331

NG
- C NG-
U
RRCReestablishmentRequest UU UE to Network TS38.331
Xn-C RRCSetupComplete UU UE to Network TS38.331
X2-C E1
gNB gNB gNB gNB-CU-C gNB-CU-U RRCRelease UU Network to UE TS38.331
Xn-U
RRCSystemInfoRequest UU UE to Network TS38.331
F1
RRCReestablishmentComplete UU UE to Network TS38.331
gNB-DU gNB-DU
RRCReestablishment UU Network to UE TS38.331
RRCResumeComplete UU UE to Network TS38.331
Uu SecurityModeCommand UU Network to UE TS38.331
UECapabilityInformation UU UE to Network TS38.331

UE
 FST NBI File Sample
FST sample file:
The hexadecimal code marked is the details of the UU interface information. B20200428.1022+ 0800-g No d e B.g No d e B610961.46001F095291.xm l
3GPP TS 38.331 38.331 File:
38331-g70.d
ocx

Chapter 5.5.5 Measurement Reporting

MR data Description Reference details

At present, following
information of severing
cell and neighbour cells
can be extracted from FST:
Chapter 6.2 RRC Message •PCI
MR Data Code Stream Format Description

•RSRP

•RSRQ

•Frequency
 284.000

Thank You 264,000

182,000

133,000

123,000