Professional Documents
Culture Documents
Huawei Utran Trace and Monitoring PDF
Huawei Utran Trace and Monitoring PDF
By the RNC signaling trace function, we can analyze the detail procedure of the fault.
Beside the air interface trace, RNC also supports terrestrial interface signaling trace,
which is very useful to locate the fault.
By real-time monitoring, we can check the performance of the objectives, such as
radio link, cell and board, which are important references for trouble shooting.
IU interface trace In case of RAB Assignment failure, RAB Release failure, paging
failure, IU Release failure, UE initial message failure ,relocation failure, IU interface
trace can be used for trouble shooting and to fix the problems.You can select the
following operations:
Tracing the messages processed by the specified SPU subsystem
Tracing the required types of message
Tracing all types of messages
Tracing signaling messages at the transport network layer
A maximum of six tracing tasks can be performed on the Iu interface for a subsystem.
Thus, a maximum number of (6 x Number of subsystems) tracing tasks can be
performed on the Iu interface simultaneously.
The trace task can run according to the schedule in the background, the trace log file
is saved in the FTP folder:/bam/version_a/ftp/trace/ in the BAM. The log file can be
download by FTP client, or by the WEB LMT, we can upload the log file by FTP.
An IU Trace Example
The message browse window displays the serial number, generation time, RFN,
tracing type, message direction, message type, user ID, subrack number, slot number,
subsystem number, and message content.
You can perform this task to identify the cause of the failure in the following
procedures: radio link setup, radio link reconfiguration. You can select the following
operations:
Tracing the messages processed by the specified CPUS subsystem
Tracing the required types of message
Tracing all types of messages
Tracing signaling messages at the transport network layer
For each subsystem, a maximum of six Iur interface tracing tasks can be performed
simultaneously
By this task ,IUB interface trace the NodeB Application Part (NBAP) messages ,we
can perform this task to identify the cause of the failure in the following procedures:
radio link setup, radio link reconfiguration, resource audit, cell setup, cell
reconfiguration, common transport channel setup, and system information update. To
start a tracing task, we can select the following operations:
Tracing messages of all the NodeBs
Tracing messages on all the ports of the specified NodeB
Tracing messages on the specified port of the specified NodeB
Tracing the messages processed by the specified CPUS subsystem
Selecting the types of traced messages
Tracing signaling messages at the transport network layer
For each subsystem, a maximum of six Iub interface tracing tasks can be performed
simultaneously.
The message browse window displays the serial number, generation time, RFN,
tracing type, message direction, message type, user ID, subrack number, slot number,
subsystem number, and message content.
By Uu interface trace ,we can perform this task to identify the cause of the failure in
the following procedures: RRC connection setup, radio bearer setup, physical
channel reconfiguration, and cell update. To start a tracing task, we can select the
following operations:
Tracing the messages in one or multiple BSC6900s and cells
Tracing all the types of messages on the Uu interface
Tracing the specified types of messages
A maximum of six Uu interface tracing tasks can be performed simultaneously. Each
Uu interface tracing task targets at a maximum of 32 cells.
An Uu Trace Example
The message browse window displays the serial number, generation time, RFN,
tracing type, message direction, message type, user ID, subrack number, slot number,
subsystem number, and message content.
This task can monitor the interworking of signaling on the standard interfaces, the
interworking of signaling on the user plane, and the uplink and downlink traffic during
a call. You can perform this task to locate the signaling problems of the VIP
subscribers, in combination with the drive test result.
The UE tracing task is to trace signaling messages of a UE on the Iu, Iur, Iub, and Uu
interfaces. The UE can be specified by IMSI, TMSI, P-TMSI, or IMEI.
In the Monitor meun , we can request UE or NodeB to report some measurement
result, which are helpful for trouble shooting, such as NodeB Sir measurement, UE tx
power measurement, UE rx BLER, downlink code channel tx power, downlink CPICH
Ec/No and RSCP.
A maximum of 12 UE tracing tasks can be performed simultaneously
The message browse window displays the serial number, generation time, RFN,
tracing type, message direction, message type, user ID, subrack number, slot number,
subsystem number, and message content.
This section describes how to trace the cell messages. The UE statistics can be
reported in the tracing result if required. The tracing results of the cell messages
provide reference for troubleshooting the CCH fault when the access success rate is
low or zero in the cell.
A maximum of six cell tracing tasks can be performed simultaneously; Each cell
tracing task targets at only one cell; Each cell tracing task targets at a maximum of
two S-CCPCHs.
The message browse window displays the details of a tracing message, including the
task number, task time, RFN, subrack number, slot number, subsystem number,
message direction, message type, message source, user ID, and message content.
After the monitoring task is started, a monitoring window is displayed, showing the
real-time monitoring results of CPU/DSP, radio link, cell, board and transmission by
list and chart, so as to monitor the system and service states.
This operation affects the CPU usage. Therefore, if the CPU usage reaches 80% or
higher, you are advised to set the monitoring period to five seconds.
After the monitoring task is started, a monitoring window is displayed, showing the
real-time monitoring result by list and chart. The task name and related parameters
are displayed on the title bar of the window.
The monitoring log files is saved in C:\Web LMT\output\MBSC\monitor by default.
CE Usage Monitoring
Answer:
RNC can not measure the CPICH directly, UE reports the measured results to
RNC in a real-time monitoring task.
During a normal service, RNC doesnt request UE measure the CPICH
periodically. Only after a monitoring task starts, RNC sends the measurement
control signaling to force UE report periodically. If the monitoring task stops,
RNC will send the measurement control again to stop the UEs measurement.
By the UE trace, we can confirm this.
d1 The casue is the dl power limitation. By modifying the RL power for voice can solve the problem. The
disadvantage is , this may affect the DL capacity and then affect the HSDPA throughput
d, 9/27/2010
d2 the ue drops, from signaling, we know call drops because of the RF reason, then from power trace, we
can confirm , because DL power limitation; at last , check the cfgmml, the downlink RL power cfg is not
reasonable, so increase the RL power for voice call, the problem is solved
d, 10/10/2010
HUAWEI UTRAN Trace and Monitoring P-42