NETACT 5.2 AS AN OPTIMIZATION TOOLFUNDAMENTALS OF HOW TO DO OPTIMIZATION WITH NETACT 5.222.11.2011

NETACT 5.2 TOOLS CONTENT Adaptation Information Browser Counter Browser Parameter Browser Reporting Suite NSN 3GRAN RU20 Content Browser CM Analyser (Consistency Check)

ADAPTATION INFORMATION BROWSER

REPORTING SUITE

Content Browser

CONSISTENCY CHECK

ACCESSABILITY RRC ACC FAIL DUE TO RADIO INT SYNCH RRC ACC FAIL DUE TO UU INT RRC SETUP FAIL DUE TO HC RRC SETUP FAIL DUE TO AC RRC SETUP FAIL DUE TO BTS REASONS RRC SETUP FAIL DUE TO TRANS RRC SETUP FAIL DUE TO RNC INTER REASONS RRC SETUP FAIL DUE TO FROZEN BTS RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL RRC SETUP FAIL DUE TO IUB AAL2 TRANS RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTION RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD

RRC ACC FAIL DUE TO RADIO INT SYNCHDescription: The number of RRC access failures caused by radio interface synchronization failure. When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6 seconds, and the RNC has not received the NBAP message which indicates that L1 synchronization has been established between UE and BTS. This counter is updated also in case of intersystem handovers and inter-RNC hard handovers

RRC ACC FAIL DUE TO UU INTDescription: The number of RRC access failures caused by UE. When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6 seconds, and the RNC has received the NBAP message which indicates that L1 synchronisation has been established between UE and BTS. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

RRC SETUP FAIL DUE TO HCDescription: The number of RRC setup failures caused by Handover Control. When the RNC decides to reject the RRC connection request because the handover control entity reports a failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. (For more information, see section Failure and abnormal release causes.) This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

RRC SETUP FAIL DUE TO ACDescription: The number of RRC setup failures caused by Admission Control. When the RNC decides to reject the RRC connection request because the admission control entity reports a failure (excluding frozen BTS reason). After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

RRC SETUP FAIL DUE TO BTS REASONSDescription: The number of RRC setup failures caused by BTS. Updated: When the RNC decides to reject the RRC connection request due to unsuccessful radio link setup. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

RRC SETUP FAIL DUE TO TRANSDescription: The number of RRC setup failures caused by Transport. When the RNC decides to reject the RRC connection request due to transport failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

RRC SETUP FAIL DUE TO RNC INTER REASONSDescription: The number of RRC setup failures caused by RNC internal reason. Updated: When the RNC decides to reject the RRC connection request due to RNC internal failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers.

RRC SETUP FAIL DUE TO FROZEN BTSDescription: The number of RRC setup failures caused by frozen BTS. Updated: When the RNC decides to reject the RRC connection request, because the admission control entity blocks the radio link establishment, to ensure the setup of high priority calls. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers.

RRC CONN SETUP FAIL DUE TO RNTI ALLO FAILDescription: Number of RRC setup failures caused by RNTI allocation failure. Updated: When the RNC decides to reject the RRC connection request due to RNTI allocation failure caused by RRMU overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

RRC SETUP FAIL DUE TO IUB AAL2 TRANSDescription: The number of RRC setup failures caused by Iub AAL2 transport resource shortage. When the RNC decides to reject the RRC connection request due to Iub transport resource shortage between RNC and WBTS. After this the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in case of inter-system handovers, and inter-RNC hard handovers.

RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTIONDescription: The number of RRC connections rejected due to emergency call redirection. Dependencies with other counters: M1001C41: EMERGENCY CALL FAILURES M1006C70: RRC CONN REJECT DUE TO RRC CONNECTION SETUP REDIRECTION

RRC CONN SETUP FAIL DUE TO ICSU OVERLOADDescription: The number of RRC setup failures caused by ICSU overload. Updated: When the RNC decides to reject the RRC connection request due to ICSU overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

RETAINABILITY DROPS DUE TO THE AIR INTERFACE DROPS DUE TO A LACK OF RESOURCES DROPS DUE TO A LOSS OF SYNCHRONIZATION DROPS DUE TO HARDWARE OVERLOAD / LICENSES MOBILITY DROPS

DROPS DUE TO THE AIR INTERFACEIn the case of too high a drop rate, check the following counters in Measurement: Service level (RRC and RAB connections) (M1001) in RNC Counters - RNW Part indicating the possible reasons for the drops. M1022C208 HS-DSCH/E-DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMING M1022C209 HS-DSCH/DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMING M1022C210 DCH/DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMING

DROPS DUE TO A LACK OF RESOURCESThese counters indicate that other reasons, for example problems in resources, cause drops. M1022C211 HS-DSCH/E-DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMING M1022C212 HS-DSCH/DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMING M1022C213 DCH/DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMING

DROPS DUE TO A LOSS OF SYNCHRONIZATIONIf the drop rate is too high because of the radio interface there can be synchronisation problems in the network. A check of the following L3 signalling measurement in Iub counters should be done: M1005C68 RL DEL ON SRNC DUE TO ACT RL SYN FAIL and/or M1005C74 RL DEL ON DRNC DUE TO ACT RL SYN FAIL These counters indicate that RL is deleted due to synchronisation loss.

DROPS DUE TO HARDWARE OVERLOAD / LICENSESIf the drop rate is high due to other failure reasons, there can be HW overload or other equipment problems. A check of the L3 Signalling Measurement at Iub counters. M1005C69 RL DEL ON SRNC DUE TO BTS HW OVERL M1005C70 RL DEL ON SRNC DUE TO BTS EQUIP FAIL and/or M1005C75 RL DEL ON DRNC DUE TO BTS HW OVERL M1005C76 RL DEL ON DRNC DUE TO BTS EQUIP FAIL The counters indicate that RL is deleted due to hardware resource problems.

MOBILITY DROPSIn NSN networks, these counters indicates all drops that occured due to mobility. M1008C217: HS-DSCH SERVING CELL CHANGES FAILED DUE TO UE M1008C218: DSCH SERVING CELL CHANGES FAILED DUE TO BTS M1008C219: HS-DSCH SERVING CELL CHANGES FAILED DUE TO TRANSPORT M1008C220: HS-DSCH SERVING CELL CHANGES FAILED DUE TO AC M1008C221: HS-DSCH SERVING CELL CHANGES FAILED DUE TO OTHER REASON M1008C8: RRC CONNECTION DROPS DURING HHO CAUSED BY SHO INCAPABILITY FOR RT It will be also beneficial to monitor the KPI: ISHO DR RT SHO Drop Rate RT, contains real drops, not all failed ISHOs. Inter RNC RT ISHO attempt includes cases when UE has also any additional NRT service.

THANK YOU