Top Banner
NETACT 5.2 AS AN OPTIMIZATION TOOL FUNDAMENTALS OF HOW TO DO OPTIMIZATION WITH NETACT 5.2 22.11.2011
34
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 3G NETACT OPTIMIZATION

NETACT 5.2 AS AN OPTIMIZATION TOOL

FUNDAMENTALS OF HOW TO DO OPTIMIZATION WITH NETACT 5.2

22.11.2011

Page 2: 3G NETACT OPTIMIZATION

NETACT 5.2 TOOLS CONTENT

• Adaptation Information Browser– Counter Browser– Parameter Browser

• Reporting Suite– NSN 3GRAN RU20– Content Browser

• CM Analyser (Consistency Check)

Page 3: 3G NETACT OPTIMIZATION

ADAPTATION INFORMATION BROWSER

Page 4: 3G NETACT OPTIMIZATION
Page 5: 3G NETACT OPTIMIZATION
Page 6: 3G NETACT OPTIMIZATION

REPORTING SUITE

Page 7: 3G NETACT OPTIMIZATION
Page 8: 3G NETACT OPTIMIZATION
Page 9: 3G NETACT OPTIMIZATION

Content Browser

Page 10: 3G NETACT OPTIMIZATION
Page 11: 3G NETACT OPTIMIZATION
Page 12: 3G NETACT OPTIMIZATION

CONSISTENCY CHECK

Page 13: 3G NETACT OPTIMIZATION
Page 14: 3G NETACT OPTIMIZATION
Page 15: 3G NETACT OPTIMIZATION

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

Page 16: 3G NETACT OPTIMIZATION

RRC ACC FAIL DUE TO RADIO INT SYNCH

Description: 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 inter-system handovers and inter-RNC hard handovers

Page 17: 3G NETACT OPTIMIZATION

RRC ACC FAIL DUE TO UU INT

Description: 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

Page 18: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO HC

Description: 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

Page 19: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO AC

Description: 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.

Page 20: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO BTS REASONS

Description: 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

Page 21: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO TRANS

Description: 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

Page 22: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO RNC INTER REASONS

Description: 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.

Page 23: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO FROZEN BTS

Description: 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.

Page 24: 3G NETACT OPTIMIZATION

RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL

Description: 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.

Page 25: 3G NETACT OPTIMIZATION

RRC SETUP FAIL DUE TO IUB AAL2 TRANS

Description: 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.

Page 26: 3G NETACT OPTIMIZATION

RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTION

Description: The number of RRC connections rejected due to emergency call redirection.

Dependencies with other counters:M1001C41: EMERGENCY CALL FAILURESM1006C70: RRC CONN REJECT DUE TO RRC CONNECTION SETUP REDIRECTION

Page 27: 3G NETACT OPTIMIZATION

RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD

Description: 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.

Page 28: 3G NETACT OPTIMIZATION

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

Page 29: 3G NETACT OPTIMIZATION

DROPS DUE TO THE AIR INTERFACE

In 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.

M1022C208HS-DSCH/E-DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMINGM1022C209HS-DSCH/DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMINGM1022C210DCH/DCH PACKET CALL REL DUE TO RL FAIL FOR STREAMING

Page 30: 3G NETACT OPTIMIZATION

DROPS DUE TO A LACK OF RESOURCES

These counters indicate that other reasons, for example problems in resources, cause drops. M1022C211HS-DSCH/E-DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMINGM1022C212HS-DSCH/DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMINGM1022C213DCH/DCH PACKET CALL REL DUE TO OTHER FAIL FOR STREAMING

Page 31: 3G NETACT OPTIMIZATION

DROPS DUE TO A LOSS OF SYNCHRONIZATION

If 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 FAILand/or M1005C74 RL DEL ON DRNC DUE TO ACT RL SYN FAILThese counters indicate that RL is deleted due to synchronisation loss.

Page 32: 3G NETACT OPTIMIZATION

DROPS DUE TO HARDWARE OVERLOAD / LICENSES

If 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.

M1005C69RL DEL ON SRNC DUE TO BTS HW OVERLM1005C70RL DEL ON SRNC DUE TO BTS EQUIP FAILand/or M1005C75RL DEL ON DRNC DUE TO BTS HW OVERL M1005C76 RL DEL ON DRNC DUE TO BTS EQUIP FAILThe counters indicate that RL is deleted due to hardware resource problems.

Page 33: 3G NETACT OPTIMIZATION

MOBILITY DROPS

In NSN networks, these counters indicates all drops that occured due to mobility.M1008C217: HS-DSCH SERVING CELL CHANGES FAILED DUE TO UEM1008C218: DSCH SERVING CELL CHANGES FAILED DUE TO BTSM1008C219: HS-DSCH SERVING CELL CHANGES FAILED DUE TO TRANSPORTM1008C220: HS-DSCH SERVING CELL CHANGES FAILED DUE TO ACM1008C221: HS-DSCH SERVING CELL CHANGES FAILED DUE TO OTHER REASONM1008C8: RRC CONNECTION DROPS DURING HHO CAUSED BY SHO INCAPABILITY FOR RTIt 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.

Page 34: 3G NETACT OPTIMIZATION

THANK YOU