30/12/2019 FDD Full Signaling Trace (LR18+)

FDD Full Signaling Trace (LR18+)

Feature Guide

FDD Full Signaling Trace (LR18+)

Version Date Author Reviewer Notes
Add OMC and NDS IPv6 configuration in Chapter 4.3.1
Add the configuration of NDS IPv6 when sending the whole network level task in Chapter
V1.0 2018-09-30 Jiao Sijin Yu Fei
4.3.2
Add Constraints in Chapter 3.4
V1.1 2018-12-27 Li Hui Yu Fei Add Update NDS User Information
1. Add Changing FTP Username and Password for NDS Login in Chapter 3.4.
V1.2 2019-02-28 Li Hui Yu Fei 2. Update Constraints in Chapter 3.5.
3. Update Table 3-1 and 3-2.

TABLE OF CONTENTS
1 Introduction
1.1 Personal Data Security
1.2 Related Feature List and License Control
1.3 Correlation Other Features

2 Function Description

3 Technical Description
3.1 Technical Principle
3.2 Trace Recording Items and Tracing Depths
3.3 Northbound Output Strategy
3.4 Changing FTP Username and Password for NDS Login
3.5 Constraints

4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
4.1.2 EPC Requirements
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
4.1.4 UE Requirement
4.1.5 Transmission Bandwidth Requirements
4.2 Related parameters
4.3 Configuration Procedure
4.3.1 Parameter Configuration
4.3.2 Full Signaling Trace Task Configuration

5 Impact on Network

6 Abbreviations

FIGURES

Figure 4‑1 NDS Log Service address-IPV4

Figure 4‑2 NDS Log Service address-IPV6
Figure 4‑3 OMC channel setting1
Figure 4‑4 OMC channel setting-3
Figure 4‑5 Update NDS User Information
Figure 4‑6 System Tools Interface
Figure 4‑7 Standard Trace Task Management (1)
Figure 4‑8 Standard Trace Task Management (2)
Figure 4‑9 Standard Trace Scope

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 1/12
30/12/2019 FDD Full Signaling Trace (LR18+)
Figure 4‑10 Standard Trace Observation Object
Figure 4‑11 Standard Trace Parameters
Figure 4‑12 Trace All NEs
Figure 4‑13 Trace All NEs NDS IP configured as IPV4
Figure 4‑14 Trace All NEs NDS IP configured as IPV6
Figure 4‑15 Enabling Standard Trace Task
Figure 4‑16 Disabling Standard Trace Task
Figure 4‑17 File Path for Storing Full Signaling Data

TABLES
Table 1‑1 Related Feature List
Table 1‑2 Correlation with Other Feature
Table 3‑1 Three Tracing Depths Supported by ZTE Signaling Tracing Feature
Table 3‑2 Medium and Minimum E-UTRAN Tracing Depths

1 Introduction
This document provides the introduction, technical descriptions, parameter configuration, counters, alarms, and validation procedure of the LTE FDD Full signaling trace
feature.

The parameters, alarms and counters in this document are the same as those of the latest software version when this document is released. To obtain the MO, parameters,
alarms, and KPIs of the existing software version, please refer to the product manuals of the existing software version.

This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in this document respectively refer to "LTE FDD" and "LTE FDD-based eNodeB".

1.1 Personal Data Security

It is unavoidable that some features listed in this document may use some personal data, like IMSI, IMEI, MSISDN, or UEIP during the procedure of activating function in
order to accomplish 3GPP service process or 3GPP location process, to optimize subscriber service experience, and to facilitate system maintenance. When you activate
these functions, you should comply with your country's personal data or privacy protection laws and regulations. If you have any questions about this, please contact your
legal department to confirm that these functions can be legally activated.

1.2 Related Feature List and License Control

Table 1‑1 Related Feature List

No Feature List No. Feature List Name License Control

or not
1 ZLF37-00-001 LTE Full Signaling Trace Yes

1.3 Correlation Other Features

Table 1‑2 Correlation with Other Feature

Feature ID Feature Required Exclusive Impacted

Name Feature Feature Feature
ZLF37-00-001 LTE Full
Signaling None None None
Trace

2 Function Description
Some commonly-used network O&M analysis methods such as drive tests and performance statistics just reflect the overall specifications of a network working under
certain conditions instead of showing the real network quality for users. What frequently happens is that network specifications are perfect while the user experience is
poor. In addition, user complaints often fail to be resolved by performance statistics. In this case, the LTE full signaling collection function developed by ZTE provides users
with all signaling data files in standard .XML format meeting 3GPP protocol requirements.

Full signaling tracing is a non-real-time task, which report signaling data to an NDS-L server that stores the data for further use by other analysis tools. The Full signaling
tracing feature can be used for some eNodeBs (cells) or all eNodeBs. The full signaling reporting function, as a part of LTE operation and maintenance, collects and reports
signaling over the S1, X2, and UU interfaces in the application layer of all UEs accessing the eNodeB. Through the online or offline analysis of the signaling and events,
carriers can provide the following services: UE monitoring, network maintenance, fault troubleshooting, network planning, and network optimization.

It should be noted that the networks of China Unicom require that the equipment from different vendors support the northbound Trace files in two formats: XML files
following 3GPP protocols and original binary code stream files meeting China Unicom Trace specifications. In addition, the data collected from the whole networks of China
Unicom must be original binary code stream files. Operators can set the output format of northbound Trace files to XML or original binary code stream on the configuration
GUI of the NDS-L server. Only one format can be generated at a time. For China Telecom and other carriers, full signaling data refers to the northbound Trace .XML files
meeting 3GPP specifications.

3 Technical Description

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 2/12
30/12/2019 FDD Full Signaling Trace (LR18+)

3.1 Technical Principle

When a full signaling collection task is delivered to the eNodeB, the eNodeB sends signaling data to the ZTE NDS-L collection server through the FTP channel. The NDS-L
server translates the signaling into an XML file for farther data analysis.

This document focuses on tracing record, tracing depth, and northbound output strategy.

The collection procedure is detailed as follows:

1. The parameters of the collection task are configured in the Standard Trace node of the UDT integrated on the EMS/OMMB, including the traced NEs, interfaces,
tracing depth, NDS-L server IP address, collection parameters, and FTP information.

2. After receiving the collection task, the NEs (eNodeBs, cells, or UEs) selected by the task collect standard signaling for a single specified UE or all UEs based on the
task parameters, and report the collected signaling to the NDS-L server in original binary code stream format. If signaling filter function is enabled in the task, only the
specific signaling is collected. In addition, full signaling trace supports IPv4 or IPv6 protocol stack.

3. The NDS-L server parses the original code stream, generates XML files satisfying 3GPP specifications, compresses the XML files of all eNodeBs to .ZIP compress
package in terms of time for operators.

3.2 Trace Recording Items and Tracing Depths

ZTE signaling tracing feature supports three tracing depths in the current version: maximum, medium, and minimum. Different tracing depths determine the signaling items
reported in the northbound XML files and whether they are decoded (M: Mandatory; O: Optional; CM: Conditional mandatory; X: Not reported. For details, refer to 3GPP TS
32.422.)

Table 3‑1 Three Tracing Depths Supported by ZTE Signaling Tracing Feature

Interface Format Tracing Depth Description

RRC (except Decoded Minimum Medium Maximum Message name
special Record
measurement) M M O expansion
Traces the
O O O
eNodeB ID.
Traces the
dedicated IEs
parsed from the
RRC messages
M M X between the
eNodeB and
UEs. Refer to
the next table in
this section.
ASN.1 Original Uu
interface
messages:
Traces the RRC
messages
X X M between the
eNodeB and
UEs and
provides ASN.1
code information
of the messages.
S1 Decoded M M O Message name
Record
O O O
expansion
Traces the
eNodeB ID.
Traces the MME
M M X
ID of the MME
connected to the
eNodeB.
Traces the
dedicated IEs
parsed from the
S1-AP
messages
M M X
between the
eNodeB and CN.
Refer to the next
table in this
section.
ASN.1 Original S1-AP
messages:
Traces the S1-
AP messages
between the
X X M eNodeB and CN
and provides
ASN.1 code
information of
the messages.
X2 Decoded M M O Message name
Record
O O O expansion

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 3/12
30/12/2019 FDD Full Signaling Trace (LR18+)
Interface Format Tracing Depth Description
Traces the
eNodeB ID.
M M X Traces the
neighboring
eNodeB ID.
Traces the
dedicated IEs
parsed from the
X2-AP
messages
M M X
between the
eNodeB and its
neighbor. Refer
to the next table
in this section.
ASN.1 Original X2-AP
messages:
Traces the X2-
AP messages
between the
X X M
eNodeB and its
neighbor and
provides ASN.1
code information
of the messages.
RRC (special Decoded Uu interface IEs
measurement in the RRC
X M X
only) measurement
report
ASN.1 RRC
X X M measurement
report

Table 3‑2 Medium and Minimum E-UTRAN Tracing Depths

Interface Protocol IE Name Message Name Tracing Depth 3GPP

Name Name Specifications
Reference
Minimum Medium

Uu RRC
Cs fallback MOBILITY FROM
M M TS 36.331
indicator EUTRA COMMAND

CN domain PAGING M M TS 36.331

S-TMSI PAGING M M TS 36.331

Re- RRC CONNECTION

establishment REESTABLISHMENT M M TS 36.331
Cause REQUEST

RRC CONNECTION
Wait time CM CM TS 36.331
REJECT

Release RRC CONNECTION

M M TS 36.331
Cause RELEASE

Redirection RRC CONNECTION

M M TS 36.331
Information RELEASE

Establishment RRC CONNECTION

CM CM TS 36.331
Cause REQUEST

Selected RRC CONNECTION

CM CM TS 36.331
PLMN-Identity SETUP COMPLETE

Registered RRC CONNECTION

CM CM TS 36.331
MME SETUP COMPLETE

UE CAPABILITY
Rat-Type M M TS 36.331
INFORMATION

Measured MEASUREMENT
X M TS 36.331
Results REPORT

HANDOVER FROM
EUTRA PREPARATION
CDMA2000- REQUEST
O O TS 36.331
Type UL HANDOVER
PREPARATION
TRANSFER

Target RAT MOBILITY FROM

O O TS 36.331
Type EUTRA COMMANDH

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 4/12
30/12/2019 FDD Full Signaling Trace (LR18+)

All messages where it is

E-RAB ID M M TS 36.413
present

E-RAB SETUP
REQUEST
E-RAB Level
E-RAB MODIFY
QoS M M TS 36.413
REQUEST
Parameters
INITIAL CONTEXT
SETUP REQUEST

INITIAL CONTEXT
SETUP FAILURE
UE CONTEXT
RELEASE REQUEST
UE CONTEXT
RELEASE COMMAND
UE CONTEXT
MODIFICATION
FAILURE
HANDOVER
Cause REQUIRED M M TS 36.413
HANDOVER
PREPARATION
FAILURE
HANDOVER REQUEST
HANDOVER FAILURE
HANDOVER CANCEL
PATH SWITCH
REQUEST FAILURE
NAS NON DELIVERY
INDICATION

HANDOVER
S1 S1AP REQUIRED
Handover HANDOVER
M M TS 36.413
Type COMMAND
HANDOVER
REQUEST

HANDOVER NOTIFY
PATH SWITCH
E-UTRAN REQUEST
CM CM TS 36.413
CGI INITIAL UE MESSAGE
UPLINK NAS
TRANSPORT

HANDOVER NOTIFY
PATH SWITCH
TAI REQUEST M M TS 36.413
UPLINK NAS
TRANSPORT

HANDOVER
Target ID M M TS 36.413
REQUIREDHANDOVER

DOWNLINK S1
CDMA2000
CDMA2000 O O TS 36.413
HO Status
TUNNELING

DOWNLINK S1
CDMA2000
CDMA2000 O O TS 36.413
RAT Type
TUNNELING

CDMA2000 UPLINK S1 CDMA2000

O O TS 36.413
Sector ID TUNNELING

CDMA2000
UPLINK S1 CDMA2000
HO Required O O TS 36.413
TUNNELING
Indication

All messages where it is

E-RAB id M M TS 36.423
present

E-RAB Level
HANDOVER REQUEST M M TS 36.423
QoS
HANDOVER REQUEST
HANDOVER
Cause PREPARATION M M TS 36.423
X2 X2AP FAILURE
HANDOVER CANCEL

Target Cell ID HANDOVER REQUEST M M TS 36.423

GUMMEI HANDOVER REQUEST M M TS 36.423

UE History
HANDOVER REQUEST M M TS 36.423
Information

3.3 Northbound Output Strategy

Full signaling trace data are divided into three types: UE-level data, cell-level data and eNodeB-level data. NDS-L is expected to display in different scenarios, the data are
reported in the following ways:

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 5/12
30/12/2019 FDD Full Signaling Trace (LR18+)
1. RAN-sharing/non RAN-sharing scenario, when eNodeB-level data is reported, PLMN information is invalid value;
2. RAN-sharing and common carrier sharing scenario, when cell-level data is reported, PLMN information is invalid value;
3. RAN-sharing and dedicated carrier sharing scenario, when cell-level data is reported, PLMN information is correct PLMN information;
4. In non-RAN sharing scenario, when cell-level data is reported, PLMN information is correct PLMN information;
5. When UE-level data is reported, PLMN information is correct PLMN information.

When PLMM information is invalid, the corresponding data will be northbound output for each operator in the sharing scenario. When certain PLMN information can be
determined, the data will be northbound output to the corresponding operator who own this PLMN information.

3.4 Changing FTP Username and Password for NDS Login

To guarantee the security of FTP transmission link, it is allowed to change the FTP username and password for NDS login.

1. At OMMB Dynamic Management interface, the FTP username and password for NDS login can be changed.

2. eNodeB saves the configured FTP username and password.

3. When eNodeB sends an FTP link setup request to NDS, this FTP link can be set up successfully if the changed username and password can be found in the
username and password list configured for NDS.

3.5 Constraints
1. Dual CC dual main scene: requires two CC transmission protocols to be consistent, and configured as IPv6 or IPv4 at the same time;

2. Single CC dual IP: requires two IP transmission protocols to be consistent and configured as IPv6 or IPv4 at the same time.

3. If FTP user name and password is modified in NDS, ensure the configuration is consistent with that of NDS server.

4 Engineering Guide

4.1 Requirements

4.1.1 Hardware Requirements

NDS-L server needs to be configured.

4.1.2 EPC Requirements

None

4.1.3 Frequency Band, Frequency and Bandwidth Requirements

None

4.1.4 UE Requirement

None

4.1.5 Transmission Bandwidth Requirements

S1 bandwidth satisfy the requirements of eNodeB some cells’ throughput

4.2 Related parameters

None

4.3 Configuration Procedure

4.3.1 Parameter Configuration

1. NDS-L Log Server Configuration

On EMS Configuration Management Interface, click System Parameter->Log Service Object->Log, and set NDS-L log information so that NDS-L IP address will be auto
added when configuration a Standard Trace task.

The NDS-L log server configuration method is described as follows:

Notes:

l Log type: NDS index in system tool task tracking parameters, currently supporting "NDS1[0]" or "NDS2[1]", default configuration NDS1[0], NDS1[0] and NDS2[1]
fully consistent;

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 6/12
30/12/2019 FDD Full Signaling Trace (LR18+)
l Log server address: The IP should be NDS server IP, the same as the OMC channel NDS server IP; if the eNB is configured to be a IPV6 environment, the NDS
server IP address needs to fill in the IPV6 address; if the environment is originally a IPV4 environment, it is transformed into a IPV6 environment. Report NDS to
normal enough;

l The mode of log transmission: The configuration is consistent with the choice of the NDS server when the server starts. In the case of personal data privacy
protection, the SFTP transmission must be used,

l Log report port: Same as the port configured by the NDS server.

Figure 4‑1 NDS Log Service address-IPV4

Figure 4‑2 NDS Log Service address-IPV6

2. OMC channel Configuration

OMC channel setting is to set a channel between eNodeB and NDS-L, so that data collected by eNodeB can be transferred to NDS-L. Setting step is described as follows:

On EMS Configuration Management Interface, double-Click Modify Area-> Transmission Network->OMC Channel.

Figure 4‑3 OMC channel setting1

If the eNB is configured to be an IPv6 environment, you need to add an OMC channel from eNB to NDS IPv6 address.

Figure 4‑4 OMC channel setting-3

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 7/12
30/12/2019 FDD Full Signaling Trace (LR18+)

3. Synchronizing modified data to the eNodeB

4.3.1.1 Update NDS User Information

On NetNumen Dynamic Management Interface, click Update NDS User Information. Select the NE ID，click run，set User name and Password.

Note:

User name and password must be consistent with NDS FTP user name and password.

For NDS FTP user name password modification, see ZTE UniPOS NDS-LN V18.40.23 Release System Installation and Maintenance Manual.

Figure 4‑5 Update NDS User Information

4.3.2 Full Signaling Trace Task Configuration

4.3.2.1 Step

1. Enter System Tools interface as shown in the figure below.

Figure 4‑6 System Tools Interface

2. Select Standard Trace and enter the task name.

Figure 4‑7 Standard Trace Task Management (1)

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 8/12
30/12/2019 FDD Full Signaling Trace (LR18+)

Figure 4‑8 Standard Trace Task Management (2)

3. Select cells of NEs which need to be tracked. After selecting Trace Scope, click [Next], then enter [Observation Object].

Figure 4‑9 Standard Trace Scope

4. Standard Trace task Observation Object is as shown in the figure below. According to the requirements, select the corresponding observation object, then click [Next]

Figure 4‑10 Standard Trace Observation Object

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 9/12
30/12/2019 FDD Full Signaling Trace (LR18+)

S1_Paging&Uu_Paging may have influence to eNB, if no necessary don’t select it

5. After selecting Standard Trace Observation Object, enter [Trace parameters] as shown in the figure below.

Figure 4‑11 Standard Trace Parameters

Trace Parameters Configuration：

1. Start date means task beginning time, End date means task ending time. If the time zone task is set, after the base station time is modified, the task needs to be
resynchronized to take effect.

2. Select ALL Day means the task for the whole day. If ALL Day is not selected, the time range can be configured, and the maximum time range is 5.

3. The max, medium and min trace depth is selected according to the requirements;

4. For NDS Receiver, select NDS1[0] or NDS2[1]; Here, the NDS-L receiver is the log type of the log service object configured above, and is selected according to
the actual configuration.

5. Select Filtering Message ID.

6. When select the Trace All NEs task, if there is an individual eNB in the whole network without NDS log server address, then the log server information can be manually
configured at the tracking parameter interface. When the eNB is configured for IPV6, NDS IP needs to be configured as IPV6 address, and attention is concerned with
personal data. In the privacy protection scenario, NDS must use SFTP transmission mode..

Figure 4‑12 Trace All NEs

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 10/12
30/12/2019 FDD Full Signaling Trace (LR18+)

Figure 4‑13 Trace All NEs NDS IP configured as IPV4

Figure 4‑14 Trace All NEs NDS IP configured as IPV6

7. Click task synchronization button.

Figure 4‑15 Enabling Standard Trace Task

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 11/12
30/12/2019 FDD Full Signaling Trace (LR18+)

8. Disabling Standard Trace Task

Select a synchronized task and click task stop button, delete stopped task. New, modified task can be done by the same method, see the following figure.

Figure 4‑16 Disabling Standard Trace Task

4.3.2.2 Data Acquisition

After the standard Trace task is successfully synchronized, the data is reported to the NDS-L server when the UE accesses the cell for service operations. Users obtains
the data from NDS-L server and fill in the user name and password according to the actual configuration. For example, to collect eNodeB Trace standard signaling, log in.
In the file ““NORTH_FILE”, the file path for storing full signaling trace task data /NORTHFILE/TRACE_CELL/TDD-LTE/. The sub-directory is filed based on time.

Figure 4‑17 File Path for Storing Full Signaling Data

5 Impact on Network
After the full signaling tracking function is enabled, if there are too many UEs access or the UE frequently performs services such as access and release, excessive
signaling will have a certain impact on on system performance and suspends signaling reporting when the performance load exceeds a certain value.

Opening S1paging and Uupaging may lead to large amount of data impact, affecting the performance of the eNodeB. If the operator has no clear requirements, it is
recommended not to select.

6 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 12/12