Measurement of RAB release per cell

Overview
The RAB release can be classified into the following types:
1) The RAB release initiated by the RNC. When the RNC detects that the UE has no data to transmit for a long period or the RNC
RN is
faulty (for example, the SRB resets or the AAL2 link on the Iu interface is faulty), the RNC sends to the CN a RAB RELEASE
REQUEST
UEST message to release the RAB or an IU RELEASE REQUEST message to release the Iu connection. If the cause value is
"User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection
Release", the RAB release is considered as normal release; otherwise, the RAB release is considered as abnormal release. For details,
see the middle of the figure.
2) The RAB release initiated by the CN. The RNC initiates the RAB release by sending the RAB ASSIGNMENT REQUEST
RE
message
and initiates the Iu connection release by sending the IU RELEASE COMMAND message. All the RAB releases initiated by the CN
are considered as normal releases. For details, see the left part of the figure.
3) The RAB release initiated by the UE.
E. The UE initiates the RAB release by sending the SIGNALING CONNECTION RELEASE
INDICATION message. According to the domain information in the message, the RNC sends an IU RELEASE REQUEST message
to the CN node (SGSN or MSC) to release the Iu connection. A
After
fter the Iu connection is released, the RNC initiates the RRC release if
no Iu connection exists in another domain. All the RAB releases initiated by the UE are considered as normal releases. For details,
de
see
the right part of the figure.

Figure 1 Drop Flow

The sub procedures mentioned in figure 1 are as following.

Figure 2 Drop Sub Flow

Table 2 describes the measurement points shown in Figure2.

Measurement points
A
B
C
D
E
F
G
H
I
J
K
L

Description
VS.RAB.NormRel.CS
VS.RAB.NormRel.AMR,VS.RAB.NormRel.CS64,VS.RAB.NormRel.CS.Str
VS.RAB.NormRel.CS.HSPA.Conv
VS.RAB.AbnormRel.CS
VS.RAB.AbnormRel.AMR,VS.Abnorm.Rel.CS.Str
VS.RAB.AbnormRel.CS.HSPA.Conv
VS.RAB.NormRel.PS
VS.RAB.NormRel.PS.Conv, VS.RAB.NormRel.PS.Str
VS.RAB.NormRel.PS.CCH
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.Conv, VS.RAB.AbnormRel.PS.Str
VS.RAB.AbnormRel.PS.CCH

Counter Relationship

Counter

Sub Counter

VS.RAB.AbnormRel.CS.RF

VS.RAB.AbnormRel.CS.RF.ULSync
VS.RAB.AbnormRel.CS.RF.UuNoReply
VS.RAB.AbnormRel.CS.RF.SRBReset

VS.RAB.AbnormRel.PS.RF

VS.RAB.AbnormRel.PS.RF.ULSync
VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.RF.TRBReset

VS.RAB.AbnormRel.CS

VS.RAB.AbnormRel.CS.RF
VS.RAB.AbnormRel.CS.OM
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.IuAAL2
VS.RAB.AbnormRel.CS.OLC

VS.RAB.AbnormRel.PS

VS.RAB.AbnormRel.PS.RF
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC

VS.RAB.AbnormRel.AMR

VS.RAB.AbnormRel.AMR.12.2
VS.RAB.AbnormRel.AMR.7.95
VS.RAB.AbnormRel.AMR.5.9
VS.RAB.AbnormRel.AMR.4.75

VS.RAB.AbnormRel.AMRWB VS.RAB.AbnormRel.AMRWB.23.85
VS.RAB.AbnormRel.AMRWB.23.05
VS.RAB.AbnormRel.AMRWB.19.85
VS.RAB.AbnormRel.AMRWB.18.25
VS.RAB.AbnormRel.AMRWB.15.85
VS.RAB.AbnormRel.AMRWB.14.25
VS.RAB.AbnormRel.AMRWB.12.65
VS.RAB.AbnormRel.AMRWB.8.85
VS.RAB.AbnormRel.AMRWB.6.6
VS.RAB.AbnormRel.AMRWB.2.0

VS.RAB.NormRel.PSR99

VS.RAB.NormRel.PS.CCH

VS.RAB.AbnormRel.PSR99

VS.RAB.AbnormRel.PS.CCH

VS.RAB.NormRel.AMRWB

VS.RAB.NormRel.AMRWB.23.85
VS.RAB.NormRel.AMRWB.23.05
VS.RAB.NormRel.AMRWB.19.85
VS.RAB.NormRel.AMRWB.18.25
VS.RAB.NormRel.AMRWB.15.85
VS.RAB.NormRel.AMRWB.14.25
VS.RAB.NormRel.AMRWB.12.65
VS.RAB.NormRel.AMRWB.8.85
VS.RAB.NormRel.AMRWB.6.60

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.