0% found this document useful (0 votes)
279 views6 pages

MDT Presentation Set 2

This document discusses trace capabilities in LTE networks including: 1. Cell trace and subscriber trace can collect detailed signaling data and UE measurements for troubleshooting and optimization. 2. Minimization of Drive Tests (MDT) supports collecting trace information including timing advance and UE measurements to reduce drive testing. 3. Trace content is operator configurable to select specific messages and control data volume. Timing advance values are captured but do not provide location information.

Uploaded by

PNG networks
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
279 views6 pages

MDT Presentation Set 2

This document discusses trace capabilities in LTE networks including: 1. Cell trace and subscriber trace can collect detailed signaling data and UE measurements for troubleshooting and optimization. 2. Minimization of Drive Tests (MDT) supports collecting trace information including timing advance and UE measurements to reduce drive testing. 3. Trace content is operator configurable to select specific messages and control data volume. Timing advance values are captured but do not provide location information.

Uploaded by

PNG networks
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Minimization of Drive Tests (MDT) RL40

Detailed trace data collection allows detailed analysis

Cell trace based MDT Data with TCE


S-GW MME
• Timing Advance information NetAct
• Measurement information provided by periodic
UE-measurements

Supports
• MDT Profiles: Collecting of trace information
from eNB in a preconfigured use case specific „normal“ trace data + periodic UE
way measurements +
Timing Advance
• Usage during network deployment, optimization
and operation

LTE953
LTE Extended Trace Support RL30

- Configurable Trace content


Operator adjustable trace content

Operator configurable selection for trace information:


• Trace granularity free selectable
• Based on the ASN.1 protocol, the operator can choose which messages will be taken into the
trace record, e.g. only the handover messages
• Scalable trace content allows to manage data stream more specifically
• Follows 3GPP definition with usage of “vendor specific extension”
• GUI support by NetAct Trace Viewer

Note: RL20 trace depth for cell trace / subscriber trace with fixed trace depth “maximum”

LTE644
LTE Timing Advance Evaluation RL30

Trace data with timing advance (TA) values

• TA reports per UE in eNB accumulated


• Captured in real time
• Recorded to
• Trace data of cell trace and subscriber trace

• Note: TA values provide no location information

LTE459
Cell Trace RL20
Trace Support
Trace features for analysis of conditions in network:
Cell & Subscriber / User Equipment Trace
• Cell trace for supervision of
(LTE163): Signal Based
cell conditions NetAct TraceCM for spec.
TraceViewer subscribers via HSS
• Subscriber trace for
supervision on UE behavior (LTE814, LTE 162):
and conditions Management Based traceCM
iOMS for cell tracing
• Supported itf:
• eUu: RRC
3rd-Party
3rd-Party Trace
Protocol Security S1AP: Signal Based
• S1: S1AP Protocol report TraceCM MME
Analyzer via IP Gateway
• X2: X2AP
Analyzer
• NetAct Trace Viewer:
central point for feature Protocol Traceltf
via IPsec
admin
• 3rd party output supported X2
eNodeB eNodeB
Management Based Trace X2AP: Signal Based
Signal Based Trace TraceCM
Protocol Trace reports

Feature ID(s): LTE433 Cell Trace, LTE163 Subscriber Trace


RL20
Cell Trace
OPEX savings with remote tracing:
Optimal troubleshooting and Network optimization
Tracing of subscriber data from remote location
• Eliminates the need to send out service staff (compared to
subscriber trace)
• IMSI not needed for tracing of data
Trouble shooting in the event of:
• Bad HO performance or no HO in
specific cells
• High call drop rate in specific cells
• QoS alarm – it can collect additional symptoms
Network optimization with Cell Trace and
• History of call handling procs (e.g call setup, call release,
handover, etc.) in cell base
• Radio quality measurement values, channel configuration /
usage for traced cell and adjacent cells
RL20
Subscriber / Equipment Trace
OPEX savings via efficient analysis tools

Drive test support


• Activate Mobile Subscriber Trace with IMSI numbers of drive testers
via EM
• Signaling and Control information, radio quality measurement reports,
adjacent cells information during drive test on different locations can
be evaluated
• No expensive measurement equipment needed
Customer complaint clarification by starting Mobile Subscriber Trace
using IMSI number and evaluating the measurement reports
Tracing of specific type of mobile equipment by using Mobile
Subscriber Trace using an IMEI number

Triggered from MME

You might also like