3G KPIs Optimization Methods

To Troubleshoot and Optimize

17th May 2016

1
T-PIM Reports
3G SSS Accessibility(TPIM)
AFR_DCR(TPIM)

Retainability(TPIM)
PRACH Propagation Delay(NetACt)

Area2

2
CS and PS Call Flow diagrams

3
Accessibility Troubleshooting Flowchart
Voice Access
PS Access Failure
Failure

Voice Trouble
RRC or RAB?
Shooting Path RRC , RAB or RAB Packet Allocation
Page 2
0/0 Reconfiguration? Failure

PS Trouble Shoot
Path Conversational
Voice RAB Failure PS RRC Failure PS RAB Failure
RRC Failure

Common Path
PS-NAS Drop Rate
(at call setup)
Voice RAB PS RAB Setup
RRC Setup or Setup or RAB
RRC Access? It’s related to
or RAB Access?
CORE, escalate to
Access?
the Market(Check
if it’s RNC wide)

Voice RAB Setup Voice RAB Access PS RAB Setup PS RAB Access
RRC Setup Failure RRC Access Failure
Failure Failure Failure Failure

Failure Cause Analysis

Failure / Failure / Failure /

Failure / Failure / Iub Failure / Failure / RHTI Failure / Failure / Failure /
Handover Admission ICSU Failure / MS
Transport AAL2 Frozen BTS Allocation RNC BTS Radio
Control Control Overload

check the Coverage

Deep
available This is This Potentially a issue if only RF
Iub Congestion. analysis
resources related to counter hardware, few sites related
T1 issues, Before add Most happens required.
Identify during the congestion point out configuration has issue.
if the more T1, check in RNC wide or Check
the level RRC setup & should resource or resource problem. Bad
failure due SHO overhead. multiple sites common
of problem stage: be issues in issue in the UE problem coverage
to Iub Detail analysis connected to parts if
(RNC wide DL Codes, analyzed the RRMU. NodeB check if problem or
AAL2 can be done ICSU. Check problem
or cluster UL Load as failure Investigate CE usage, happens in Interfere
doesn’t from AAL2 CAC “List of Generic happens
level) (Prx total), due to RNC Num of user RNC wide. nce (UL
increase. resource Faults on
DL load Admission dimensioni in compress Also check or DL).
counters particular
(Downlink Control ng mode. the UL
sites.
Tx power) noise level.
Accessibility Troubleshooting Flowchart

Packet Allocation
Failure

Packet Call Setup Failures

Failure /
Failure / Failure / Failure /
Admission Failure / BTS Failure / UE
Transport DMCU Other
Control

Coverage
Check the Mainly caused by All other failures
Mainly caused Potentially a issue if only
availability lack of DMCU i.e. not AC, BTS,
by lack of IuB hardware, few sites
of resources. DMCU, TRANS or
resources (T1). configuration or has
resources Check the DSP UE are counted as
Detailed resource issue in problem. UE
the such as performance OTHER failures.
analysis can be the NodeB check problem if
DL Codes, measurements in Could be RF
done from CE usage at the problem
UL Load RNC. related, check bad
AAl2 CAC/ capacity report, happens in
(Prx total), Deep analysis coverage or
resource number of user RNC wide.
DL load required might be in compress Interference (UL or
reservation Also check
(Downlink an issue with the mode. DL).
counters. the UL noise
Tx power) DMCU HW.
level.
Accessibility Troubleshooting Per Cause – RRC Phases
Showing Failure Cause and phase Trigger

The RRC - Failure Analysis 1. RRC setup attempts.

2. RRC setup attempts per
RRC Procedure Review – Applicable CS or PS setup cause.
3. RRC setup failures due to
handover control
admission control
transport
(Transmission)
RNC internal
SETUP PHASE frozen BTS
Rejections Happens here BTS
Admission Rejections, DRRC command RNTI Allocation fail
IuB AAL2
ICSU overload
Access PHASE L1 Synchronization and RL 4. RRC setup failures per setup
synchronization happen cause.
here 5. RRC setup complete.
6.RRC access failures due to
radio interface
UE
Active Phase RNC internal
7. RRC access complete.
8. Special reason: RRC active
RRC Drop and Release release due to
happens here SRNC Relocation
Pre-emption
9. RRC active failures due to
Iu interface
(transport)
radio interface
(synchronization)
BTS
Iur interface (DRNC)
RNC internal
UE
10. RRC active complete.

6
Accessibility Troubleshooting Per Cause – RAB Access Phase CS Call
Showing Failure Cause and phase Trigger

The RAB - Failure Analysis

RAB Failure – Review CS Call

Admission /Rejection of RAB for CS

Reconfiguration on DCH request starts here
Allocation of resources in WBTS, transport

Resources Allocation readiness in UE

Waiting for UE to confirm

RAB Releases
Failures in Allocation under different cause

7
Accessibility Troubleshooting Per Cause – RAB Access Phase CS Call
Showing Failure Cause and phase Trigger

Admission /Rejection of RAB for PS

Reconfiguration on DCH request starts here
Allocation of resources in WBTS, transport

No Admission Rejection in PS if DCH sets at 0/0

Resources Allocation readiness in UE

Waiting for UE to confirm

RAB Releases
Failures in Allocation under different cause
Accessibility Call Flow RRC  RAB CS Calls 1. System Information (BCCH)
The UE reads the System Information that is broadcast on BCCH. The information is not read continuously. It is
only read if the information changes

2. RRC: RRC Connection Request (CCCH)

The Mobile user decides to initiate a voice call. The first message the UE will send on CCCH is RRC Connection
Request. This will contain among other things, Initial UE Identity and Establishment Cause (i.e.MOC,MTC for
CS, PS High Priority Signaling like, Low Priority Signalling

3. NBAP: Radio Link Setup Request

The SRNC sends this message to Node B. It will pass the Cell Id, TFS, TFCS, frequency, UL Scrambling code,
etc to Node B.

4. NBAP: Radio Link Setup Response

Node B allocates the resources and starts PHY Reception. While transmitting the response it includes the
Transport layer addressing information that includes the Binding Identity of the AAL2 for Iub data transport
bearer

5. ALCAP: Establish REQ

The AAL2 binding identity (Iub Data Transport Bearer Id) is passed to ALCAP protocol in Node B. The Iub Data
Transport bearer is now bounf to DCH.

6. ALCAP: Establish CNF

Establish confirm from ALCAP in Node B
RRC
7: DCH-FP: Downlink Synchronization
The Node B and SRNC establishes synchronization for the Iub Data Transport bearer by means of exchange of
the appropriate DCH Frame Protocol frames.

8: DCH-FP: Uplink Synchronization

Once the UL synchronization is achieved, Node B starts DL transmission.

9: RRC: RRC Connection Setup (CCCH)

RRC Connection Setup message is sent on CCCH with the parameters required to establish DCH. Also the state
indicator will be set to DCH for the voice (or CS) call.

10: NBAP: Radio Link Restore Indication

Once the UE establishes Radio Link, Node B will send RL Restore indication to the SRNC.
A
11: RRC: RRC Connection Setup Complete (DCCH) RC Connection Setup complete will be sent on DCCH.
Integrity and Ciphering related parameters and UE capability information will be sent back to SRNC
Accessibility Call Flow RRC  RAB CS Calls
12: RRC: Initial Direct Transfer [CM Service Request]
First NAS message is now sent by the UE. It indicates that a UE orginated Voice call is required. The UE identity (TMSI) will also be
passed in this message
13: RANAP: Initial UE Message [CM Service Request]
The NAS message will be forwarded to appropriate CN Domain (CS Domain in this case). Along with the CM service request, it will
B also include LAI and SAI.
14: RANAP: Direct Transfer [Authentication Request]
MSC/VLR needs to perform authentication to make sure that the UE is genuine. For this reason it will challenge the UE with a
Authentication token and RAND (random number)
15: RRC: Downlink Direct Transfer [Authentication Request]
SRNC transfers the NAS message to the UE
16: RRC: Uplink Direct Transfer [Authentication Response]
UE computes the response (RES) and sends it back in the NAS message
Authentication 17: RANAP: Direct Transfer [Authentication Response]
SRNC relays the response to the MSC/VLR. The MSC/VLR will compare the response RES with the expected response XRES. If they
are the same then the procedure will continue.
18: RANAP: Security Mode Command
MSC/VLR sends the Security Mode Command to start Ciphering and Integrity Protection. Ciphering is optional while Integrity
Protection is mandatory. The Algorithms, etc are known to the MSC/VLR and the UE and only the ones that are common between
them are used.
19: RRC: Security Mode Command
RRC Forwards the Security Mode command received from MSC/VLR to the UE.
20: RRC: Security Mode Complete
The UE configures the Ciphering and Integity Protection and responds back to the network. The response message is Integrity
Protected for further safety. Ciphering is started at Ciphering activation time. Since this is a Circuit switched call, the Ciphering will
be started in MAC. In case of AM and UM bearers it is started in RLC.
21: RANAP: Security Mode Complete
The network forwards the Security Mode Complete message to MSC/VLR.
22: RANAP: Direct Transfer [TMSI Reallocation Command]
The network may decide to re-allocate the TMSI to the UE. It sends a DT message which includes the NAS TMSI Reallocation
Command.
23: RRC: DL Direct Transfer [TMSI Reallocation Command]
The RNC relays the DT message to the UE.
24: RRC: UL Direct Transfer [TMSI Reallocation Complete]
The UE takes the new TMSI and responds with the Complete message
25: RANAP: Direct Transfer [TMSI Reallocation Complete]
The RNC relays the message to t
he CN domain
RAB Allocation 26: RRC: UL Direct Transfer [Setup]
The UE now sends the 'Setup' message in UL Direct Transfer message. This will include all the required parameters for setting up
the voice call. It will include the number that UE wishes to be contacted and the bearer capability
27: RANAP: Direct Transfer [Setup]
The network relays the message to the MSC/VLR
28: RANAP: Direct Transfer [Call Proceeding]
The MSC/VLR sends Call Proceeding to the UE indicating that it is now starting with the RAB establishment procedure.
29: RRC: DL Direct Transfer [Call Proceeding]
The network relays it to the UE.
Accessibility Call Flow RRC  RAB 30: RANAP: RAB Assignment Request
The CN initiates establishment of the Radio Access Bearer using the RAB Assignment Request message. This message includes the QoS
of the call being established, the Transport Address, Iu Transport association, etc.
RAB Continuation
C 31: ALCAP: Establish REQ
SRNC initiates the set-up of Iu Data Transport bearer using ALCAP protocol. The request contains the AAL2 Binding Identity to Bind the
Iu Data Transport Bearer to the RAB. (Note that this is not done in case of PS RAB)
32: ALCAP: Establish CNF
The CN responds with the ALCAP Establish CNF
33: NBAP: Radio Link Reconfiguration Prepare
SRNC requests Node B to prepare establishment of DCH to carry the RAB. It passes the TFS, TFCS and Power Control Information in the
message.
34: NBAP: Radio Link Reconfiguration Ready
Node B allocates the resources and responds with the Ready message. It sends back the AAL2 address and the AAL2 binding Id for the
Iub data transport bearer.
35: ALCAP: Establish REQ
SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. The request contains the AAL2 Binding Identity to bind the Iub
Data Transport Bearer to DCH.
36: ALCAP: Establish CNF
The Node B responds with the Establish Confirm.
37: DCH-FP: Downlink Synchronization
The Node B and SRNC establish synchronism for the Iub Data Transport Bearer by means of exchange of the appropriate DCH frame
protocol frames. SRNC sends the DL Synchronization frames.
38: DCH-FP: Uplink Synchronization
The Node B responds with the UE Synchronization frames.
39: NBAP: Radio Link Reconfiguration Complete
Finally the SRNC instructs the Node B of the CFN at which the new configuration will come into effect.
40: RRC: Radio Bearer Setup
SRNC sends the RB Setup message to add the new DCH's. The message will be received using the old configuration.
41: RRC: Radio Bearer Setup Response
After the activation time the UE will respond with complete message using the new configuration.
42: RANAP: RAB Assignment Reponses
The SRNC responds with the response to the MSC/VLR.
43: ISUP: Initial Address Message
MSC/VLR sends the Initial Address Message to the PSTN. The message tells the PSTN to reserve an idle trunk circuit from originating
switch to the destination switch.
44: ISUP: Address Complete Message
The ACM message is sent to indicate that the remote end of the trunk circuit has been reserved.
45: RANAP: Direct Transfer [Alert]
The Alert message is sent to the SRNC. This message contains the ACM received from the PSTN.
46: RRC: Direct Transfer [Alert]
The Alert message is forwarded to the UE. The Alert message will initiate the ringing tone on the handset.
47: ISUP: Answer Message
When the person that is being called picks up his phone, an Answer message is sent to the MSC/VLR.
48: RANAP: Direct Transfer [Connect]
The MSC/VLR sends the Connect message to the SRNC via Direct Transfer message. The Connect message indictaes that the End User
has answered the call.
49: RRC: DL Direct Transfer [Connect]
The SRNC forwards the Connect message to the UE.
50: RRC: UL Direct Transfer [Connect Acknowledge]
The UE confirms the reception of the Connect message using the Connect Acknowledge and sending it via Direct Transfer
51: RANAP: Direct Transfer [Connect Acknowledge]
The Network forwards the Connect Acknowledge to the MSC/VLR. The call has now been successfully
established.
RRC Setup Phase Failure Causes
RRC failure counters for all type of services or establishment causes (not just voice)

• RRC Request Reject due to Handover Control

When the RNC decides to reject the RRC connection request because the handover control entity reports a failure.
Identify, if the problem is RNC wide or spread over a group of cells and will require further investigation (i.e. ICSU Card)

• RRC Request Reject due to Admission Control

The RNC will check the available resources during the RRC setup stage; DL Codes, UL Load (Prx total), DL load (Downlink Tx power). (Note
the RNC does not check for CE in the NodeB)
Detailed analysis can be done to find exactly which resource is causing the admission problem from traffic and cell resource counters.
Check MHA Gain in the commissioning file and hardware issues affecting UL Noise.
Compare FeederLoss (commissioning file, also in BTSSC object) with CableLoss (WCEL parameter).

• RRC Request Reject due to Transport Failure (include failure due to AAL2)
Transport failures are mostly due to T1 related issues which can be checked from BER counters. This counter will also include the number of
times the T1 was congested (AAL2 blocking).
Detailed analysis can be done from AAl2 resource reservation counters.

• RRC Request Reject due to RNC Internal Failure

This counter is pegged if the RNC can not assign the failure to any other failure counters or if there is a RNC hardware/software/resource
problem/L2 failure.
This counter needs to be monitored for any step changes for it might indicate RNC is having some internal problem like hanging resources.

• RRC Request Reject due to Frozen BTS

This counter pegs in the event when the RNC rejected the RRC setup to ensure the setup of high priority calls.
This is related to congestion & should be analyzed as per RRC Request Reject due to Admission Control
12
RRC Access Phase Failure Causes

• RRC Connections Access Failure due to Radio Reasons

These failures are mostly RF related and can be split between:

• Bad Coverage (Low RSCP)
• Interference (Low Ec/No)
Root cause analysis will in most cases require drive test analysis.
Also verify that the uplink PRXnoise for these sites is within acceptable range.

• RRC Connections Access Failure due to MS Failures

The cause for this counter can be coverage even though L1 synchronization has been achieved it can still be that a sudden
loss in coverage was experienced. If only one site is showing a high count for this counter the most likely cause is that it is
coverage related. If this is an RNC wide problem it needs to be determine if it is a specific UE type that is causing the
problem, this will require advance analysis .
Also verify that the uplink PRXnoise for the site is within acceptable range.

• RRC Connections Access Failure due to RNC Failures

If the counter is showing a step change it might be related to a new software load that was loaded on the RNC or core
network side. To trouble shoot these problem it will require in-depth analysis on the RNC which should be done by Tier 2. If
only particular sites are showing a high count for this counter investigate if there is any common point of failure for these cells
( Same RNC, same Transmission path/ hardware) Also investigate if the T1 for these sites are error free ( Look at the cell
availability and BER for T1)

13
RRC Setup Phase Failure Causes
• RRC Request Reject due to RNTI Allocation Failure
This counter point out resource issues in the RRMU. Investigate RNC dimensioning.

• RRC Request Reject due to Iub AAL2 Transport

This counter points out T1 capacity problems between RNC and NodeB..Before a T1 upgrade is raised for cells having a high count in
Iub congestion a detail analysis must be done to investigate if the congestion can be resolved by improving the Soft Handover Overhead (by
down tilt or parameter change).Detailed analysis can be done from AAl2 CAC/ resource reservation counters.

• RRC Request Reject due to ICSU Overload

It is unlikely that this will be a cell specific issue and would rather be an RNC wide or multiple sites connected to the ICSU. There is a
few know problems in the RNC that are related to the ICSU load and dimensioning issues, see “List of Generic Faults LGF-RNC-2008-07
Radio Controllers WCDMA RNC RN2.2, RN3.0” on NOLS for more details.

• RRC Request Reject due BTS

This counter is showing that there is potentially a hardware, configuration or resource issue in the NodeB.
Resource problems can be verified from the CE usage counters, if the traffic is low and the CE usage is high it is due to hanging
resources. If the traffic is high it might be that there is not enough license keys for CE. (Compare the max CE used counters with installed
license keys in the WBTS) Also check the number of users in Compressed Mode(verified with TMO Baseline parameter setting). If the
number of users in compressed mode is high when there is no traffic in the cell it is also indicates that there is hanging resources in the cell.

A site reset normally corrects these problems, if the problem does not clear or repeats a ticket should be open with the field technicians
to investigate. Potential issues on the site that can cause this problem can be:
 Incorrect configuration data (audit the commissioning file for any discrepancies)
 Corrupt files in the NodeB (Recommissioning should resolve this problem)
 Corrupt software in the NodeB (Software upgrade/ downgrade can be used to reload the software in the site)
 Faulty hardware (System module). It has been seen that replacing the system module resolved this problem. Note in these
instances there were no alarms on the site to indicate that there was a hardware issue.

14
Voice RAB Setup Failure Causes
• Voice RAB Setup Failure Due to Admission Control
Same as RRC admission control, only difference is that now the exact number of voice attempts rejected due to admission can be seen rather than the total for all the
services.

• Voice RAB Setup Failure Due to BTS

Same as RRC setup failures due to BTS

• Voice RAB Setup Failure Due to Transport (includes failures due to AAL2 Iub)
Same as RRC setup failures due to Transport

• Voice RAB Setup Failure Due to RNC

Same as RRC setup failures due to RNC

• Voice RAB Setup Failure Due to Frozen BTS

Same as RRC setup failures due to Frozen BTS

• Voice RAB Setup Failure Due to AAL2 Iub

Same as RRC setup failures due to AAL2
• Voice RAB Setup Failure Due to Non-support Request
CS RAB setup attempt is not started due to requested parameters are not supported by the RNC. (CS data calls) It should be looked into if this is a specific device
that is requesting the unsupported RAB configuration, this investigation can only be done with the help of K18 or similar advance tracing equipment.

• Voice RAB Setup Failure Due to UE Capability

Same as above, voice RAB Failure Due to Non-supported Request.

Voice RAB Access Failure Causes

• Voice RAB Access Failure Due to UE
Same as RRC access failures due to MS
• Voice RAB Access Failure Due to RNC Internal Failures
Same as RRC setup failures due to RNC

15
Call Drop Analysis Overview

16
Call Drop analysis-1
• If cells is having high call drops ,check its neighboring cells with any faulty alarms
• Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur, MS, RNC)
• Check SHO KPI if performance < 90% ( leads to radio failure)
 Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)
 Detect badly performing neighbors using HO success rate per adjacency counters (M1013)
 High incoming HO failure rate in all ADJS – check sync alarms
 Assessing neighbor list plan and visualization check with map
 Evaluate HO control parameters and trigger threshold
• Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
 Check missing neighbor (M1015), GSM frequency plan neighbor RNC and MSC database consistency audit, check alarm of
reference clock in 3G or in 2G, check 2G TCH congestion
 Check RRC Drop ISHO RT / NRT
• Detecting DL or UL path loss problem if RAB drop due to radio (dominant call drop cause > 50%)
 Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC
 Mapping radio failures with Tx power and CPICH related parameters ->CPICHToRefRABOffset, PTXDPCH MAX
 Check Call reestablishment timer -> T315 (rec.10s)
 Ecno distribution for bad coverage issue (M1007C38-M1007C47)
17
Call Drop analysis-2

• Check core network parameter setting if RAB_ACT_FAIL_XXX_IU

 Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU
• If high RAB_ACT_FAIL_XXX_BTS
 Check if any BTS faulty alarm (7653 cell faulty alarm)
 If no alarms, COCO detach/attach
• If high RAB_ACT_FAIL_XXX_MS
 Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimization)

18
RAB & RRC Active Failures

19
 Mobility Failure Categories

HSDPA SHO
ISHO Failure
Failure
Intra-system
SHO Failure HHO Failure

20
 ISHO Failure

Unsuccessful UTRAN cannot perform

No Cell Found Radio Drops
ISHO attempt ISHO

Check Neighbour Trigger ISHO earlier or

Definitions for missing improve 3G coverage to Review and adjust Determine which neighbour
or incorrect compensate for sudden loss neighbour plan relationships with ISHO
neighbours of coverage (Cell by Cell problem
Basis)

Check and correct

BCCH and BSIC Undertake Determine if issue is HW or
Definitions Parameter Changes Core network relation issue, or
associated with if the target cell is defined in
ISHO the target MSC etc.

Undertake Parameter
Changes associated
with ISHO
Review and adjust
neighbour plan

21
 SHO Failure

Physical
Interference Neighbour Plan NRT Dylo and SHO
Resource Issues

Use Ec/No classes

in association with
Determine any HW issues Review and adjust Confirm that Dylo is taking
e1A trigger to
neighbour plan place.
determine level of
interference

Check for Transmission

Blocking Undertake
Improve coverage in Parameter Change Adjust parameters to ensure
area of poor to improve SHO that Dylo is taking place
dominance to reduce definitions
level of interference
Check for Admission
Control Blocking

Check for CE Congestion

Blocking

22
 HSDPA SHO Failure

Interference Physical Resource

Neighbour Plan
Issues

Use Ec/No classes in

association with e1A Determine any HW issues Review and adjust
trigger to determine neighbour plan
level of interference

Check for Transmission

Blocking Undertake
Improve coverage in
Parameter Change
area of poor
to improve SHO
dominance to reduce
definitions
level of interference

Check for Admission

Control Blocking

Check for CE Congestion

Blocking

23
 Intra-system HHO Failure

Core Network UTRAN

Check ATM SCCP Determine CAC failure

Parameters for counts/RNC Internal failures
incorrect settings

Use K18 together with Check RL addition failure

Core MSC or SGSN counts
engineer to find issue

24
Voice Accessibility
The KPI measures user ability to access the mobile network for circuit switched voice calls. The metrics consists of 3 components of CS
Access call; RRC, NAS drop at call setup and RAB. The RRC part of the equation measures Conversational (originating and terminating)
calls. The RRC measures Conversational Voice and Data (CSV+CSD) while RAB part measures only Speech for both originating and
terminating causes. The NAS (non-access stratum) (signalling) part is now included as a NAS drop rate component, measuring the
percentage of RRC SRBs that dropped before RAB phase.

Formula: 100*(1 - (decode( ( (nvl(servlev.moc_conv_call_atts,0) + nvl(servlev.mtc_conv_call_atts,0)) - (nvl(servlev.rrc_acc_rel_mo_conv,0) +

nvl(servlev.rrc_acc_rel_mt_conv,0)) - (nvl(servlev.rrc_att_rep_mo_conv,0) + nvl(servlev.rrc_att_rep_mt_conv,0)) + nvl(rrc.cell_update_att_cs_call,0) +
(nvl(servlev.emergency_call_atts,0) - nvl(servlev.rrc_acc_rel_emergency,0) - nvl(servlev.rrc_att_rep_emergency,0)) ) , 0, null, (
(nvl(servlev.moc_conv_call_atts,0) + nvl(servlev.mtc_conv_call_atts,0)) - (nvl(servlev.rrc_acc_rel_mo_conv,0) + nvl(servlev.rrc_acc_rel_mt_conv,0)) -
(nvl(servlev.moc_conv_call_fails,0) + nvl(servlev.mtc_conv_call_fails,0)) + nvl(rrc.cell_update_succ_cs_call,0) + (nvl(servlev.emergency_call_atts,0) -
nvl(servlev.emergency_call_fails,0) - nvl(servlev.rrc_acc_rel_emergency,0)) )/( (nvl(servlev.moc_conv_call_atts,0) + nvl(servlev.mtc_conv_call_atts,0)) -
(nvl(servlev.rrc_acc_rel_mo_conv,0) + nvl(servlev.rrc_acc_rel_mt_conv,0)) - (nvl(servlev.rrc_att_rep_mo_conv,0) + nvl(servlev.rrc_att_rep_mt_conv,0)) +
nvl(rrc.cell_update_att_cs_call,0) + (nvl(servlev.emergency_call_atts,0) - nvl(servlev.rrc_acc_rel_emergency,0) - nvl(servlev.rrc_att_rep_emergency,0)) )
)) * (decode( (servlev.succ_rrc_setup_conv) , 0, null, (nvl(servlev.succ_rrc_setup_conv,0) - nvl(servlev.srb_act_fail_conv,0)) /
(servlev.succ_rrc_setup_conv) )) * (decode( (nvl(servlev.rab_stp_att_cs_voice,0) + nvl(servlev.rab_reloc_stp_att_cs_voice,0) +
nvl(servlev.rab_stp_fail_cs_not_supp_par,0) + nvl(servlev.rab_stp_fail_cs_ue_capa,0)) , 0, null, (nvl(servlev.rab_acc_comp_cs_voice,0) +
nvl(servlev.rab_reloc_acc_comp_cs_voice,0)) / (nvl(servlev.rab_stp_att_cs_voice,0) + nvl(servlev.rab_reloc_stp_att_cs_voice,0) +
nvl(servlev.rab_stp_fail_cs_not_supp_par,0) + nvl(servlev.rab_stp_fail_cs_ue_capa,0)) )))
Table: SERVLEV nokrww_ps_servlev_{OBJ_AGG}_{TIME_AGG} RRC nokrww_ps_rrc_{OBJ_AGG}_{TIME_AGG}

25
Voice Retainability
The KPI measures the Circuit Switch Voice (Speech) call drop rate. The number of RAB active drop for CS Voice (CSV) caused by Iu
transport failure or radio interface synchronization failure or BTS failure or requested procedure failure in drift RNC (Iur) or RNC internal
failure or UE is not responding to an RRC message

Formula: 100*(decode( ( nvl(servlev.rab_act_comp_cs_voice,0) + nvl(servlev.rab_act_rel_cs_voice_srnc,0) + nvl(servlev.rab_act_rel_cs_voice_isho,0) +

nvl(servlev.rab_act_rel_cs_voice_hho,0) + nvl(servlev.rab_act_rel_cs_voice_p_emp,0) + nvl(servlev.rab_act_fail_cs_voice_iu,0) +
nvl(servlev.rab_act_fail_cs_voice_radio,0) + nvl(servlev.rab_act_fail_cs_voice_bts,0) + nvl(servlev.rab_act_fail_cs_voice_iur,0) +
nvl(servlev.rab_act_fail_cs_voice_rnc,0) + nvl(servlev.rab_act_fail_cs_voice_ue,0) + nvl(servlev.rab_act_fail_cs_voice_trans,0) ) , 0, null, (
nvl(servlev.rab_act_rel_cs_voice_p_emp,0) + nvl(servlev.rab_act_fail_cs_voice_iu,0) + nvl(servlev.rab_act_fail_cs_voice_radio,0) +
nvl(servlev.rab_act_fail_cs_voice_bts,0) + nvl(servlev.rab_act_fail_cs_voice_iur,0) + nvl(servlev.rab_act_fail_cs_voice_rnc,0) +
nvl(servlev.rab_act_fail_cs_voice_ue,0) + nvl(servlev.rab_act_fail_cs_voice_trans,0) )/( nvl(servlev.rab_act_comp_cs_voice,0) +
nvl(servlev.rab_act_rel_cs_voice_srnc,0) + nvl(servlev.rab_act_rel_cs_voice_isho,0) + nvl(servlev.rab_act_rel_cs_voice_hho,0) +
nvl(servlev.rab_act_rel_cs_voice_p_emp,0) + nvl(servlev.rab_act_fail_cs_voice_iu,0) + nvl(servlev.rab_act_fail_cs_voice_radio,0) +
nvl(servlev.rab_act_fail_cs_voice_bts,0) + nvl(servlev.rab_act_fail_cs_voice_iur,0) + nvl(servlev.rab_act_fail_cs_voice_rnc,0) +
nvl(servlev.rab_act_fail_cs_voice_ue,0) + nvl(servlev.rab_act_fail_cs_voice_trans,0) ) ))
Table: SERVLEV nokrww_ps_servlev_{OBJ_AGG}_{TIME_AGG}

26
 PS Access Failure Rate (GCR)
This metric measures the PS access failure rate for both interactive and background calls from a user prespective

Formula: 100*(1 - ( ( (decode( ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) + nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - (

nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) + nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.rrc_att_rep_mo_interactive,0) +
nvl(servlev.rrc_att_rep_interactive,0) + nvl(servlev.rrc_att_rep_mo_background,0) + nvl(servlev.rrc_att_rep_mt_background,0) + nvl(servlev.rrc_att_rep_mo_subscribed,0) ) ) , 0, 1, (case when ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0)
+ nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - ( nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) +
nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.moc_inter_call_fails,0) + nvl(servlev.mtc_inter_call_fails,0) + nvl(servlev.moc_backg_call_fails,0) + nvl(servlev.mtc_backg_call_fails,0) +
nvl(servlev.moc_subsc_traf_call_fails,0) ) ) > ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) + nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - (
nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) + nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.rrc_att_rep_mo_interactive,0) +
nvl(servlev.rrc_att_rep_interactive,0) + nvl(servlev.rrc_att_rep_mo_background,0) + nvl(servlev.rrc_att_rep_mt_background,0) + nvl(servlev.rrc_att_rep_mo_subscribed,0) ) ) or ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) +
nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - ( nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) +
nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.moc_inter_call_fails,0) + nvl(servlev.mtc_inter_call_fails,0) + nvl(servlev.moc_backg_call_fails,0) + nvl(servlev.mtc_backg_call_fails,0) +
nvl(servlev.moc_subsc_traf_call_fails,0) ) ) < 0 or ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) + nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - (
nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) + nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.rrc_att_rep_mo_interactive,0) +
nvl(servlev.rrc_att_rep_interactive,0) + nvl(servlev.rrc_att_rep_mo_background,0) + nvl(servlev.rrc_att_rep_mt_background,0) + nvl(servlev.rrc_att_rep_mo_subscribed,0) ) ) < 0 then 1 else ( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) +
nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - ( nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) +
nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.moc_inter_call_fails,0) + nvl(servlev.mtc_inter_call_fails,0) + nvl(servlev.moc_backg_call_fails,0) + nvl(servlev.mtc_backg_call_fails,0) +
nvl(servlev.moc_subsc_traf_call_fails,0) ) )/( ( nvl(servlev.moc_inter_call_atts,0) + nvl(servlev.mtc_inter_call_atts,0) + nvl(servlev.moc_backg_call_atts,0) + nvl(servlev.mtc_backg_call_atts,0) + nvl(servlev.moc_subsc_traf_call_atts,0) ) - (
nvl(servlev.rrc_acc_rel_mo_interactive,0) + nvl(servlev.rrc_acc_rel_interactive,0) + nvl(servlev.rrc_acc_rel_mo_background,0) + nvl(servlev.rrc_acc_rel_mt_background,0) + nvl(servlev.rrc_acc_rel_mo_subscribed,0) ) - ( nvl(servlev.rrc_att_rep_mo_interactive,0) +
nvl(servlev.rrc_att_rep_interactive,0) + nvl(servlev.rrc_att_rep_mo_background,0) + nvl(servlev.rrc_att_rep_mt_background,0) + nvl(servlev.rrc_att_rep_mo_subscribed,0) ) ) end) )) * (decode( (nvl(servlev.succ_rrc_setup_intera,0) +
nvl(servlev.succ_rrc_setup_backg,0)) , 0, 1, (case when (nvl(servlev.succ_rrc_setup_intera,0) + nvl(servlev.succ_rrc_setup_backg,0) - nvl(servlev.srb_act_fail_intera,0) - nvl(servlev.srb_act_fail_backg,0)) > (nvl(servlev.succ_rrc_setup_intera,0) +
nvl(servlev.succ_rrc_setup_backg,0)) or (nvl(servlev.succ_rrc_setup_intera,0) + nvl(servlev.succ_rrc_setup_backg,0) - nvl(servlev.srb_act_fail_intera,0) - nvl(servlev.srb_act_fail_backg,0)) < 0 or (nvl(servlev.succ_rrc_setup_intera,0) +
nvl(servlev.succ_rrc_setup_backg,0)) < 0 then 1 else (nvl(servlev.succ_rrc_setup_intera,0) + nvl(servlev.succ_rrc_setup_backg,0) - nvl(servlev.srb_act_fail_intera,0) - nvl(servlev.srb_act_fail_backg,0)) / (nvl(servlev.succ_rrc_setup_intera,0) +
nvl(servlev.succ_rrc_setup_backg,0)) end) )) * (decode( (nvl(servlev.rab_stp_att_ps_inter,0) + nvl(servlev.rab_stp_att_ps_backg,0) + nvl(servlev.rab_reloc_stp_att_ps_int,0) + nvl(servlev.rab_reloc_stp_att_ps_bgr,0)) , 0, 1, (case when
(nvl(servlev.rab_acc_comp_ps_inter,0) + nvl(servlev.rab_acc_comp_ps_backg,0) + nvl(servlev.rab_reloc_acc_comp_ps_int,0) + nvl(servlev.rab_reloc_acc_comp_ps_bgr,0)) > (nvl(servlev.rab_stp_att_ps_inter,0) + nvl(servlev.rab_stp_att_ps_backg,0) +
nvl(servlev.rab_reloc_stp_att_ps_int,0) + nvl(servlev.rab_reloc_stp_att_ps_bgr,0)) or (nvl(servlev.rab_acc_comp_ps_inter,0) + nvl(servlev.rab_acc_comp_ps_backg,0) + nvl(servlev.rab_reloc_acc_comp_ps_int,0) + nvl(servlev.rab_reloc_acc_comp_ps_bgr,0)) < 0 or
(nvl(servlev.rab_stp_att_ps_inter,0) + nvl(servlev.rab_stp_att_ps_backg,0) + nvl(servlev.rab_reloc_stp_att_ps_int,0) + nvl(servlev.rab_reloc_stp_att_ps_bgr,0)) < 0 then 1 else (nvl(servlev.rab_acc_comp_ps_inter,0) + nvl(servlev.rab_acc_comp_ps_backg,0) +
nvl(servlev.rab_reloc_acc_comp_ps_int,0) + nvl(servlev.rab_reloc_acc_comp_ps_bgr,0)) / (nvl(servlev.rab_stp_att_ps_inter,0) + nvl(servlev.rab_stp_att_ps_backg,0) + nvl(servlev.rab_reloc_stp_att_ps_int,0) + nvl(servlev.rab_reloc_stp_att_ps_bgr,0)) end) )) ) *
(decode( ( nvl(pktcall.ps_att_hsdsch_edch_int,0) + nvl(pktcall.ps_att_hsdsch_edch_bgr,0) + nvl(pktcall.ps_att_hsdsch_dch_int,0) + nvl(pktcall.ps_att_hsdsch_dch_bgr,0) + nvl(pktcall.ps_att_dch_dch_int,0) + nvl(pktcall.ps_att_dch_dch_bgr,0) ) , 0, 1, (case when (
nvl(pktcall.hs_e_req_hs_e_allo_int,0) + nvl(pktcall.hs_e_req_hs_e_allo_bgr,0) + nvl(pktcall.hs_e_req_hs_d_allo_int,0) + nvl(pktcall.hs_e_req_hs_d_allo_bgr,0) + nvl(pktcall.hs_d_req_hs_d_allo_int,0) + nvl(pktcall.hs_d_req_hs_d_allo_bgr,0) +
nvl(pktcall.hs_e_req_d_d_allo_int,0) + nvl(pktcall.hs_e_req_d_d_allo_bgr,0) + nvl(pktcall.hs_d_req_d_d_allo_int,0) + nvl(pktcall.hs_d_req_d_d_allo_bgr,0) + nvl(pktcall.d_d_req_d_d_allo_int,0) + nvl(pktcall.d_d_req_d_d_allo_bgr,0) ) > (
nvl(pktcall.ps_att_hsdsch_edch_int,0) + nvl(pktcall.ps_att_hsdsch_edch_bgr,0) + nvl(pktcall.ps_att_hsdsch_dch_int,0) + nvl(pktcall.ps_att_hsdsch_dch_bgr,0) + nvl(pktcall.ps_att_dch_dch_int,0) + nvl(pktcall.ps_att_dch_dch_bgr,0) ) or (
nvl(pktcall.hs_e_req_hs_e_allo_int,0) + nvl(pktcall.hs_e_req_hs_e_allo_bgr,0) + nvl(pktcall.hs_e_req_hs_d_allo_int,0) + nvl(pktcall.hs_e_req_hs_d_allo_bgr,0) + nvl(pktcall.hs_d_req_hs_d_allo_int,0) + nvl(pktcall.hs_d_req_hs_d_allo_bgr,0) +
nvl(pktcall.hs_e_req_d_d_allo_int,0) + nvl(pktcall.hs_e_req_d_d_allo_bgr,0) + nvl(pktcall.hs_d_req_d_d_allo_int,0) + nvl(pktcall.hs_d_req_d_d_allo_bgr,0) + nvl(pktcall.d_d_req_d_d_allo_int,0) + nvl(pktcall.d_d_req_d_d_allo_bgr,0) ) < 0 or (
nvl(pktcall.ps_att_hsdsch_edch_int,0) + nvl(pktcall.ps_att_hsdsch_edch_bgr,0) + nvl(pktcall.ps_att_hsdsch_dch_int,0) + nvl(pktcall.ps_att_hsdsch_dch_bgr,0) + nvl(pktcall.ps_att_dch_dch_int,0) + nvl(pktcall.ps_att_dch_dch_bgr,0) ) < 0 then 1 else (
nvl(pktcall.hs_e_req_hs_e_allo_int,0) + nvl(pktcall.hs_e_req_hs_e_allo_bgr,0) + nvl(pktcall.hs_e_req_hs_d_allo_int,0) + nvl(pktcall.hs_e_req_hs_d_allo_bgr,0) + nvl(pktcall.hs_d_req_hs_d_allo_int,0) + nvl(pktcall.hs_d_req_hs_d_allo_bgr,0) +
nvl(pktcall.hs_e_req_d_d_allo_int,0) + nvl(pktcall.hs_e_req_d_d_allo_bgr,0) + nvl(pktcall.hs_d_req_d_d_allo_int,0) + nvl(pktcall.hs_d_req_d_d_allo_bgr,0) + nvl(pktcall.d_d_req_d_d_allo_int,0) + nvl(pktcall.d_d_req_d_d_allo_bgr,0) )/(
nvl(pktcall.ps_att_hsdsch_edch_int,0) + nvl(pktcall.ps_att_hsdsch_edch_bgr,0) + nvl(pktcall.ps_att_hsdsch_dch_int,0) + nvl(pktcall.ps_att_hsdsch_dch_bgr,0) + nvl(pktcall.ps_att_dch_dch_int,0) + nvl(pktcall.ps_att_dch_dch_bgr,0) ) end) )) ))
Table: SERVLEV nokrww_ps_servlev_{OBJ_AGG}_{TIME_AGG} PKTCALL nokrww_ps_pktcall_{OBJ_AGG}_{TIME_AGG}

27
 PS RAB Drop Rate (GCR)
This metrics measures the Packet Switched RAB drop rate. The RAB active drop for PS data caused by Iu transport failure or radio
interface synchronisation failure or BTS failure or requested procedure failure in drift RNC (Iur) or RNC internal failure or UE is not
responding to an RRC message.

Formula: 100*(decode( ( nvl(servlev.rab_act_fail_ps_strea_iu,0) + nvl(servlev.rab_act_fail_ps_strea_radio,0) + nvl(servlev.rab_act_fail_ps_strea_bts,0) + nvl(servlev.rab_act_fail_ps_strea_iur,0) +

nvl(servlev.rab_act_fail_ps_strea_rnc,0) + nvl(servlev.rab_act_fail_ps_strea_ue,0) + nvl(servlev.rab_act_fail_ps_inter_iu,0) + nvl(servlev.rab_act_fail_ps_inter_radio,0) +
nvl(servlev.rab_act_fail_ps_inter_bts,0) + nvl(servlev.rab_act_fail_ps_inter_iur,0) + nvl(servlev.rab_act_fail_ps_inter_rnc,0) + nvl(servlev.rab_act_fail_ps_inter_ue,0) +
nvl(servlev.rab_act_fail_ps_backg_iu,0) + nvl(servlev.rab_act_fail_ps_backg_radio,0) + nvl(servlev.rab_act_fail_ps_backg_bts,0) + nvl(servlev.rab_act_fail_ps_backg_iur,0) +
nvl(servlev.rab_act_fail_ps_backg_rnc,0) + nvl(servlev.rab_act_fail_ps_backg_ue,0) + nvl(servlev.rab_act_fail_ps_strea_trans,0) + nvl(servlev.rab_act_fail_ps_inter_trans,0) +
nvl(servlev.rab_act_fail_ps_backg_trans,0) + nvl(servlev.rab_act_comp_ps_strea,0) + nvl(servlev.rab_act_rel_ps_strea_srnc,0) + nvl(servlev.rab_act_rel_ps_strea_hho,0) +
nvl(servlev.rab_act_rel_ps_strea_isho,0) + nvl(servlev.rab_act_comp_ps_inter,0) + nvl(servlev.rab_act_rel_ps_inter_srnc,0) + nvl(servlev.rab_act_rel_ps_inter_hho,0) +
nvl(servlev.rab_act_rel_ps_inter_isho,0) + nvl(servlev.rab_act_comp_ps_backg,0) + nvl(servlev.rab_act_rel_ps_backg_srnc,0) + nvl(servlev.rab_act_rel_ps_backg_hho,0) +
nvl(servlev.rab_act_rel_ps_bgr_isho,0) ) , 0, null, ( nvl(servlev.rab_act_fail_ps_strea_iu,0) + nvl(servlev.rab_act_fail_ps_strea_radio,0) + nvl(servlev.rab_act_fail_ps_strea_bts,0) +
nvl(servlev.rab_act_fail_ps_strea_iur,0) + nvl(servlev.rab_act_fail_ps_strea_rnc,0) + nvl(servlev.rab_act_fail_ps_strea_ue,0) + nvl(servlev.rab_act_fail_ps_inter_iu,0) +
nvl(servlev.rab_act_fail_ps_inter_radio,0) + nvl(servlev.rab_act_fail_ps_inter_bts,0) + nvl(servlev.rab_act_fail_ps_inter_iur,0) + nvl(servlev.rab_act_fail_ps_inter_rnc,0) +
nvl(servlev.rab_act_fail_ps_inter_ue,0) + nvl(servlev.rab_act_fail_ps_backg_iu,0) + nvl(servlev.rab_act_fail_ps_backg_radio,0) + nvl(servlev.rab_act_fail_ps_backg_bts,0) +
nvl(servlev.rab_act_fail_ps_backg_iur,0) + nvl(servlev.rab_act_fail_ps_backg_rnc,0) + nvl(servlev.rab_act_fail_ps_backg_ue,0) + nvl(servlev.rab_act_fail_ps_strea_trans,0) +
nvl(servlev.rab_act_fail_ps_inter_trans,0) + nvl(servlev.rab_act_fail_ps_backg_trans,0) - nvl(servlev.rab_act_fail_ps_int_pch,0) - nvl(servlev.rab_act_fail_ps_backg_pch,0) )/(
nvl(servlev.rab_act_fail_ps_strea_iu,0) + nvl(servlev.rab_act_fail_ps_strea_radio,0) + nvl(servlev.rab_act_fail_ps_strea_bts,0) + nvl(servlev.rab_act_fail_ps_strea_iur,0) +
nvl(servlev.rab_act_fail_ps_strea_rnc,0) + nvl(servlev.rab_act_fail_ps_strea_ue,0) + nvl(servlev.rab_act_fail_ps_inter_iu,0) + nvl(servlev.rab_act_fail_ps_inter_radio,0) +
nvl(servlev.rab_act_fail_ps_inter_bts,0) + nvl(servlev.rab_act_fail_ps_inter_iur,0) + nvl(servlev.rab_act_fail_ps_inter_rnc,0) + nvl(servlev.rab_act_fail_ps_inter_ue,0) +
nvl(servlev.rab_act_fail_ps_backg_iu,0) + nvl(servlev.rab_act_fail_ps_backg_radio,0) + nvl(servlev.rab_act_fail_ps_backg_bts,0) + nvl(servlev.rab_act_fail_ps_backg_iur,0) +
nvl(servlev.rab_act_fail_ps_backg_rnc,0) + nvl(servlev.rab_act_fail_ps_backg_ue,0) + nvl(servlev.rab_act_fail_ps_strea_trans,0) + nvl(servlev.rab_act_fail_ps_inter_trans,0) +
nvl(servlev.rab_act_fail_ps_backg_trans,0) + nvl(servlev.rab_act_comp_ps_strea,0) + nvl(servlev.rab_act_rel_ps_strea_srnc,0) + nvl(servlev.rab_act_rel_ps_strea_hho,0) +
nvl(servlev.rab_act_rel_ps_strea_isho,0) + nvl(servlev.rab_act_comp_ps_inter,0) + nvl(servlev.rab_act_rel_ps_inter_srnc,0) + nvl(servlev.rab_act_rel_ps_inter_hho,0) +
nvl(servlev.rab_act_rel_ps_inter_isho,0) + nvl(servlev.rab_act_comp_ps_backg,0) + nvl(servlev.rab_act_rel_ps_backg_srnc,0) + nvl(servlev.rab_act_rel_ps_backg_hho,0) +
nvl(servlev.rab_act_rel_ps_bgr_isho,0) ) ))
Table: SERVLEV nokrww_ps_servlev_{OBJ_AGG}_{TIME_AGG}

28
Example-UMTS – MHA Performance
Activity:
• Enabled parameter “MHA” on WCEL level as MHA were commissioned
in BTS Manager(MHA defined on BTS Manager)
• Audit performed from 3G dump on WCEL
• Correction on MHA in WCEL improved the Voice Drop Rate(%)

29 © Nokia Solutions and Networks 2014

For Internal use
Example-PPH10230E1-2 Performance

• Cell was overshooting earlier but after downtilting(from 3 to 5) cell is now

serving areas near to the site as shown in PRACH snapshots

• This analysis can be done by generating PRACH propagation delay from

T-PIM/NETACT or using Actix.

30 © Nokia Solutions and Networks 2014

For Internal use
Example-UPH30195F11 Performance

• Cell was overshooting earlier but after downtilting(from 2 to 4) cell is now

serving areas near to the site as shown in PRACH snapshots

• This analysis can be done by generating PRACH propagation delay from

T-PIM/NETACT or using Actix.

31 © Nokia Solutions and Networks 2014

For Internal use
Example-UPH20106A11 Performance

• Implemented FMCx edge settings & deleted 2G external neighbors,

Significant improvement seen in Voice Drop Rate & IRAT HO Failures.

32 © Nokia Solutions and Networks 2014

For Internal use