huawei utran trace and monitoring

HUAWEI UTRAN Trace and Monitoring

Confidential Information of Huawei. No Spreading Without Permission

P-0



P-1



P-2



P-3



P-4

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.



P-5



P-6



P-7

Procedure for Creating a Tracing Task The LMT sends a binary command to the OMU to create the task The OMU assigns an ID to the task and forwards the command to the

debugging module of the specified board. After receiving the command, the debugging module records the filter

parameters of the trace data in the filter table and notifies the service module. The service module updates the local filter table according to the message

from the debugging module. The OMU forwards the traced messages to the LMT that creates the task

according to the task ID. The LMT translates the messages and displays them on the tracing window.

Only the user has the relevant rights can perform message tracing operations, includes：

admin, USER, OPERATOR, ADMINISTRATOR, and CUSTOM entitled to use command group G_10（That is, all users except the GUEST-level user and CUSTOM-level users that are not entitled to use command group G_10 can perform the tracing tasks online.）



P-8



P-9

Huawei RNC supports following trace functions: Interface basis trace, include: IU interface, IUR interface, IUB interface, Uu

interface，and the IU-PC interface which is for location services.; UE basis trace: IOS (information of the subscribers)trace; Cell basis trace and MNCDT (missing neighbor CDT); IP link trace;



P-10

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.



P-11

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.

An IU Trace Example



P-12

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



P-13

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.



P-14


An IUB Trace Example



P-15

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.



P-16


An Uu Trace Example



P-17

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



P-18


An UE Message Trace Example



P-19

IOS(information of subscribers) task can trace several connected subscribers in a cell(RNC can select the trace target, the number of the targets can be set in “RRC” or “RAB” menu), and like the “UE message trace”, this task can request UE or NodeB to report some measurement results(set in “monitor” menu).

Assume that the specified number of continuous calls is N. If N calls are already being traced, the system does not trace any newly accessed calls. If the number becomes less than N because of the termination of a traced call, the system automatically traces a new call.

A maximum of six IOS tracing tasks can be performed simultaneously. Each task targets a maximum of 30 calls and 32 cells.

You need to specify the number of successive calls to be traced, tracing cell range, sampling criteria, and tracing time. The calls that meet the sampling criteria are traced within the specified tracing time. When creating a new call tracing task, you can define the sampling criteria by setting the RAB parameter constraints and the RRC Est Cause. Once the call meets the criteria, the tracing of the call is not stopped even if the RAB parameters of the RRC establishment cause are changed during the call. If the initial settings of the RAB parameters or the RRC establishment cause value of a call does not meet the criteria, the BSC6900 does not trace the call even if these parameters are modified to meet the criteria during the call. You can specify the message types to be traced by selecting the event types. You can also select one or more cells to trace.



P-20

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.



P-21

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.

Cell Message trace Example



P-22



P-23



P-24

The internal procedure for creating a real-time monitoring task is:

When you create a monitoring task on the LMT, the LMT sends a binary command to the OMU to create the task.

The OMU assigns a number to the task and sends the command to the debugging module of the specified board

After receiving the command, the debugging module records the filter parameters in the filter table and notifies the service module

The service module updates the local filter table according to the messages from the debugging module

The service module compares the collected data against the local filter table and reports the qualified messages to the OMU

The OMU forwards the data to the LMT that crea

tes the task according to the task ID The LMT displays the data in a chart or a list on the interface

A maximum of 64 monitoring tasks can be performed simultaneously on the same LMT

You must have the required rights to perform real-time monitoring operations on the BSC6900.

Except GUEST-level users and CUSTOM users that are not entitled to command group G_10, all the other levels of users can perform the real-time monitoring.



P-25



P-26

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.



P-27

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.



P-28

Example of Monitoring CPU/DSP Usage:



P-29

By this task following resources can be monitored ： IMA group throughput; UNI link throughput ; SAAL link throughput ; IPOA PVC throughput ; AAL2 PATH throughput ; FE/GE throughput ; PPP link throughput ; MLPPP group throughput ; SCTP link throughput ; IP PATH throughput ; Logical port throughput ; OM throughput ; Logical port bandwidth;



P-30

Example of Monitoring IP PATH:



P-31

The following targets may be monitored: Monitoring Cell P-CPICH TX Power Monitoring UL RX Total Wideband Power of a Cell Monitoring DL TX Power in a Cell Monitoring User Volume in Cell Monitoring Node Synchronization Monitoring UL CAC Monitoring DL CAC Monitoring the Number of UL Equivalent Users Monitoring the Number of DL Equivalent Users Monitoring the Cell Code Tree Monitoring the Minimum Required Power of the HS-DSCH Monitoring the Bit Rate Provided by the HS-DSCH Monitoring the Bit Rate Provided by the E-DCH Monitoring UL Throughput of a Cell Monitoring DL Throughput of a Cell Monitoring Cell CE Monitoring the FDPCH SYMBOL



P-32

An Example of Cell RTWP Monitoring



P-33

Cell Tx Power Monitoring



P-34

CE Usage Monitoring



P-35

This monitoring is an IMSI based, include: Monitoring P-CPICH Ec/No and RSCP Monitoring SIR of the Uplink RLS Monitoring the Enhanced Outer Loop Power Control Monitoring the SIR Error Values of UL RLSs Monitoring DL Code TX Power Monitoring the UE TX Power Monitoring UL Traffic Monitoring DL Traffic Monitoring UL Throughput and Bandwidth Monitoring DL Throughput and Bandwidth Monitoring Handover Delay Monitoring the BLER of the DL Transport Channel Monitoring the AMR Mode



P-36

Uplink DCH SIR Monitoring



P-37

Downlink DCH code tx power Monitoring



P-38

CPICH Ec/No & RSCP Monitoring



P-39

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 doesn’t 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 UE’s measurement.

By the UE trace, we can confirm this.



P-40



P-41

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 throughputd, 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 solvedd, 10/10/2010



P-42

huawei utran trace and monitoring

Documents

huawei rnc

iu interface trace

interface basis trace

trace data

air interface trace

permission p

ue basis trace

following trace functions