E2E Subscriber Trace Feature Description

E2E Subscriber Trace

This document describes the features of the LTE-EPC, providing detailed description of the definition,
implementation principle, service procedures, and networking applications of the E2E subscriber trace
feature.E2E subscriber trace indicates that call signaling on a specified subscriber is traced on multiple
network elements (NEs) and each NE sends the trace result to a specified device.With the tools provided
by the element management system (EMS), the following functions are available during E2E subscriber
trace:
 Creating, deleting, or checking a trace task
 Collecting trace signaling
 Analyzing collected signaling
By using the E2E subscriber trace feature, operators can easily trace a specified subscriber across the
entire network, and operation and maintenance (OM) engineers can locate faults more quickly. This
reduces the operation expenditure (OPEX) and subscriber complaints, and improves the customer
satisfaction. By using this feature, OM engineers, R&D engineers, and network optimization engineers
can complete the following tasks:
 Rectifying network faults
 Adjusting and optimizing the network
 Implementing the new feature Interoperability Testing.

Network Architecture
Major NEs

eNodeB
The functions of the evolved NodeB (eNodeB) are implemented by Huawei eRAN. To implement the E2E
subscriber trace feature, the eNodeB must support the following additional functions:
 Tracing S1-MME, X2, and LTE-Uu interface messages, adding time labels to traced
messages, and reporting the traced messages to the M2000
 Processing trace control parameters of the S1-MME interface, and starting and
stopping trace recording sessions
 Propagating or processing trace control parameters of the X2 interface
 Encrypting OM channels between the eNodeB and the M2000 according to Secure
Socket Layer (SSL).

MME
The functions of the mobility management entity (MME) are implemented by Huawei USN9810. To
implement the E2E subscriber trace feature, the MME must support the following additional functions:
 Tracing S1-MME, S3, S6a, S10, and S11 interface messages, adding time labels to
traced messages, and reporting the traced messages to the M2000
 Propagating trace control parameters to the serving gateway (S-GW), or to the target
S-GW when the S-GW changes
 Propagating trace control parameters to the eNodeB, or to the target eNodeB when
the eNodeB changes
 Propagating trace control parameters to the target MME
 Activating or deactivating trace sessions on the control plane or signaling plane
 Receiving the commands of starting, stopping, and checking the trace task from the
M2000
 Encrypting OM channels between the MME and the M2000 according to SSL.

S-GW
The functions of the S-GW are implemented by Huawei UGW9811. To implement the E2E subscriber
trace feature, the S-GW must support the following additional functions:
 Tracing S11, S5, S8, and S4 interface messages, adding time labels to traced
messages, and reporting the traced messages to the M2000
 Processing the trace control parameters of the S11 interface and activating or
deactivating trace sessions
 Propagating trace control parameters to the PDN gateway (P-GW)
 Encrypting OM channels between the S-GW and the M2000 according to SSL.
P-GW
The functions of the P-GW are implemented by Huawei UGW9811. To implement the E2E subscriber
trace feature, the P-GW must support the following additional functions:
 Tracing S5, S8, SGi, and Gx interface messages, adding time labels to traced
messages, and reporting the traced messages to the M2000
 Processing the trace control parameters of the S5 interface and activating or
deactivating trace sessions
 Encrypting OM channels between the P-GW and the M2000 according to SSL.

HSS
The functions of the home subscriber server (HSS) are implemented by Huawei SAE-HSS9820. To
implement the E2E subscriber trace feature, the HSS must support the following additional functions:
 Receiving the commands of starting, stopping, and checking the trace task from the
M2000
 Propagating trace control parameters to the MME through the S6a interface.

EMS
The functions of the EMS are implemented by Huawei M2000. To implement the E2E subscriber trace
feature, the M2000 must support the following additional functions:
 Sending the commands of starting, stopping, and checking the trace task to the MME
or HSS
 Receiving the traced messages reported by the eNodeB, MME, S-GW, and P-GW
 Displaying the trace result reported by each NE in the same window, filtering
messages according to NEs, and displaying the trace result of only a single NE in a
window
 Displaying traced messages of each NE in a window in a unified style
 Viewing historical trace results and periodically updating the displayed trace results
 Encrypting OM channels between the EMS and each NE according to SSL
 Setting the rights of subscriber trace commands.
Working Principle

E2E subscriber trace indicates that E2E signaling trace is performed on specific subscribers. An E2E
subscriber trace task can be initiated either by the HSS or the MME.
 E2E signaling trace task initiated by the HSS: The EMS sends control commands to
the HSS, and then the HSS initiates an E2E subscriber trace task. Generally, the HSS
initiates an E2E subscriber trace task for home subscribers.
 E2E signaling trace task initiated by the MME: The EMS directly sends control
commands to the MME, and then the MME initiates an E2E subscriber trace task.
Generally, the MME initiates an E2E subscriber trace task for foreign subscribers and
roaming subscribers.

The principle of E2E subscriber trace is as follows:

a. The EMS sends a trace command to the HSS through a management link. The HSS
triggers E2E subscriber trace, including creating, checking, and deleting a trace task.
b. The HSS propagates trace control parameters to the MME through the S6a interface.
The MME propagates the trace control parameters to the S-GW through the S11
interface and to the eNodeB through the S1-MME interface. The S-GW propagates the
trace control parameters to the P-GW through the S5/S8 interface.
c. The MME, S-GW, P-GW, and eNodeB trace signaling and upload the trace result to
the EMS through a trace data link. The EMS displays trace signaling.
Trace control parameters are as follows:
 IMSI/MSISDN
An IMSI/MSISDN identifies a subscriber. E2E signaling of a subscriber can be traced
based on an international mobile subscriber identity (IMSI) or a mobile station
international ISDN number (MSISDN).
 Trace session ID
A trace session ID uniquely identifies a trace session.
 Trace depth
Trace depth indicates the level of detail of the message content reported by an NE. At
present, only the maximum depth is supported, that is, the complete message is
reported.
 Trace NE list
Trace NE list indicates the NEs including the eNodeB, MME, S-GW, and P-GW that
trace messages in trace sessions. Each NE determines the NEs to which the trace data
is propagated according to the trace NE list.
 Trace interface list
Trace interface list indicates the trace interface list for each NE to be traced. The trace
interface list instructs the NEs to trace and report the messages of a specified
interface.
 Trace event
Trace event specifies when a trace recording session is started or stopped. Each NE of this version
propagates rather than processes the trace event.

For each E2E subscriber trace task, a trace session must be activated first, and the trace result is
reported to a specific NE. After the trace task is complete, the trace session must be deactivated. To
ensure that the subscriber is traced both before and after the handover, the handover-based trace must
be performed. For details, see the following sections.

LTE E2E Single-User tracking task collection guidance

NE version and License requirements

The E2E subscriber trace feature is the optional feature in the LTE-EPC solution. The USN9810 and
M2000 licenses are required for this feature

NE Version Requirements
EMS M2000 V200R010
eNodeB eRAN V100R002C00
MME USN9810 V900R001C03
S-GW UGW9811 V900R001C03
P-GW UGW9811 V900R001C03
HSS SAE-HSS9820 V900R006C02
Guide Steps
1. Login on M2000 Server.
2. Select Monitoring -> signaling tracing -> signaling tracing management

3. Choose LTE/EPC END to End User Trace.

4. The following dialog box appears, fill in the name of the track, to track the user's IMSI /
MSISDN number, select issued by MME to track tasks, click Next.
User Number

The subscriber information of a trace task, the user number can be the International Mobile
Subscriber Identity (IMSI) or Mobile Station International ISDN Number (MSISDN)

Value Range

IMSI: an integer number ranging from 6 to 15 Digits.

MSISDN: an integer number ranging from 1 to 15 Digits.

Reference Number
The ID of a task that uniquely identifies a trace task, the value range is an integer number from
0 to 65535, the value is generated randomly by the system. It's recommended to retain this
value.

When creating a virtual subscriber track task on the wireless OSS, specify the corresponding
user trace ID that was set when you created the LTE/EPC End to End User trace task on the
CN OSS to ensure that the wireless OSS obtains the trace results from the eNodeB.

5. The following dialog box appears, select the required standard opening track, and tap
finish.
When the eNodeB and MME respectively monitored by two M2000 management, in
addition to start "LTE / EPC End-to-End User Trace" task in the M2000 where the MME
is located, also you need to start "LTE Virtual UE Trace" task in the M2000 where the
eNodeB is located, the reference No must be the same like the one in step 4 .

When you finish tracking period stop tracking the task, double-click the task to open a
browser window, select "Save All ...".the final collection of virtual user tracking package
should have two different files with the file name extension.
Performance monitoring collection

Note: This is a monitoring task to select up to 30 NE, eNodeB need to be prepared to monitor
the activities of the UE, each task cannot be more than 24 hours tracking, if you need to track
more than 24 hours of data, you need to restart the tracking task.
1. Login on M2000 Server.
2. Select Monitoring -> signaling tracing -> signaling tracing management

3. Choose LTE/EPC END to End User Trace.

4. Choose User Performance Monitoring
5. The following dialog box appears, fill in the track name, and the selected track NE, fill in
the end time, Task (recommended to choose Client Task stored in the client, note that
the data from the client to save downloaded every day, to avoid losing), click Next.

6. Tracking reference number to fill in then click finish.

7. Check your Monitoring Task.
 8. You can easily Export and save the data.

User Details tracking

Note: Every task cannot be more than 4 hours tracking, if you need to track more than four
hours of data, you need to restart the tracking task.
1. Login on M2000 Server.
2. Select Monitoring -> signaling tracing -> signaling tracing management
3. Choose LTE/EPC END to End User Trace.
4. Choose Information Collection/ User Detail Trace.

5. The following dialog box appears, fill in the track name, and the selected track NE, fill in
the end time, Task (recommended to choose Client Task stored in the client, pay
attention to save the downloaded data from the client, to avoid losing), click Next.

6. Click finish
7. Export data, the file name will contain User_Detail_Trace, if the UE moves in multiple
cells managed by the M2000, each eNB will have a corresponding record mark mouth
tmf file information. tmf file eNB side can only be opened with the FMA.