4.1 RAB management

32.4053GPPPerformance Management (PM)Performance measurementsRelease 17Telecommunication managementTSUniversal Terrestrial Radio Access Network (UTRAN)

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.1.1 Overview

4.1.1.1 Measurements are based on the success and failure of procedures

The proposed measurements are not merely based on the counting of a given type of message since a same message may be repeated by an implementation dependent process. The aim here is to provide implementation independent specification.

Proposed measurements are based on the success/failure of procedures identified in the reference documents. The end of a procedure implies a stable state of the communication between the two involved parties. This stable state is normally the object of a common understanding from the two parties. As a consequence, proposed measurements are attached either to the successful or the unsuccessful issue of a procedure.

4.1.1.2 Combination of Traffic Class and Core Network domains

A Radio Access Bearer (RAB) is characterized by several QOS parameters among them is the Traffic Class. Currently there are not any 3GPP specifications including TS 23.107 2 in which may be found restrictions related to the possible combinations between Traffic Class and Core Network domain.

Consequently, as a conservative position, this specification should leave open every possible combination between Traffic Class and Core Network domain as specification TS 23.107 2 does.

4.1.1.3 Considered Radio Access Bearer management procedures

Performance Measurement definitions in this subclause are based on TS 25.413 [5].

The following paragraphs are of interest for this purpose:

– RAB Assignment;

– RAB Release Request;

– RAB ASSIGNMENT REQUEST;

– RAB ASSIGNMENT RESPONSE;

– RAB RELEASE REQUEST.

These paragraphs show in particular the following diagrams.

Figure: RAB Assignment procedure. Successful operation

Figure: RAB Release Request procedure

4.1.1.4 Measurements relate to RAB establishment, modification and release

RAB management procedure includes RAB Assignment procedure and RAB Release Request procedure. The purpose of RAB Assignment procedure is to establish new RABs and/or to enable modifications and/or releases of already established RABs for a given UE. If RABs are failed to be established or modified, the involved services may fail. RAB release request can be initiated by CN or RNC when the services terminate normally or abnormally.

During daily maintenance of network, measurements regarding RAB establishment, modification and release are useful for operators to evaluate RAB management procedures, to analyze failure reasons of RAB establishment and RAB modification, and to analyze the causes of RAB release, especially in case RAB release abnormally.

4.1.2 RAB establishment for CS domain

4.1.2.0 Introduction

The five measurement types defined in the clause 4.1.2 for CS domain are subject to the "4 out of 5 approach".

4.1.2.1 Attempted RAB establishments for CS domain

a) This measurement provides the number of requested RAB in establishment attempts for CS domain. The measurement is split into subcounters per traffic class.

b) CC

c) On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for CS domain, each requested RAB in establishment attempts is added to the relevant measurement according to the traffic class requested. See TS 25.413 [5] and TS 23.107 [2]. For conversational service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
downlink<D>:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
As indicated above, and <D> are integer values that map to the conversational service specified uplink and downlink data rates respectively.

NOTE : The addition is performed with the condition that the RAB has not been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

d) Each measurement is an integer value.

e) RAB.AttEstabCS.Conv.<D>
RAB.AttEstabCS.Strm
RAB.AttEstabCS.Intact
RAB.AttEstabCS.Bgrd

f) RncFunction

g) Valid for circuit switched traffic

h) UMTS

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.2.2 Successful RAB establishments without queuing for CS domain

a) This measurement provides the number of successfully established RABs for CS domain in which a queuing process has not been involved. The measurement is split into subcounters per traffic class.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each successfully established RAB is added to the relevant measurement according to the traffic class requested in the RAB ASSIGNMENT REQUEST message. See TS 25.413 [5] and TS 23.107 [2]. For conversational service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
downlink<D>:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
As indicated above, and <D> are integer values that map to the conversational service specified uplink and downlink data rates respectively.

NOTE: The addition is performed with the condition that the RAB has not been mentioned as queued in a previous RANAP RAB ASSIGNMENT RESPONSE and the RAB has not been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

d) Each measurement is an integer value.

e) RAB.SuccEstabCSNoQueuing.Conv.<D>
RAB.SuccEstabCSNoQueuing.Strm
RAB.SuccEstabCSNoQueuing. Intact
RAB.SuccEstabCSNoQueuing.Bgrd.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.2.3 Failed RAB establishments without queuing for CS domain

a) This measurement provides the number of RABs failed to establish for CS domain in which a queuing process has not been involved. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each RAB failed to establish is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Establishment Failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailEstabCSNoQueuing.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.2.4 Successful RAB establishments with queuing for CS domain

a) This measurement provides the number of successfully established RABs for CS domain in which a queuing process has been involved. The measurement is split into subcounters per traffic class.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each successfully established RAB is added to the relevant measurement according to the traffic class. See TS 25.413 [5] and TS 23.107 [2]. For conversational service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
downlink<D>:
1: AMR rate (12.2 10.2 7.95 7.4 6.7 5.9 5.15 4.75) kbps
2: 12.2 kbps
3: 28.8 kbps
4: 32 kbps
5: 64 kbps
6: AMR -WB-rate (12.65, 8.8, 6.65) kbps
As indicated above, and <D> are integer values that map to the conversational service specified uplink and downlink data rates respectively.

NOTE: The addition is performed with the condition that the RAB has been mentioned as queued in a previous RANAP RAB ASSIGNMENT RESPONSE and the RAB has not been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

d) Each measurement is an integer value.

e) RAB.SuccEstabCSQueuing.Conv.<D>
RAB.SuccEstabCSQueuing.Strm
RAB.SuccEstabCSQueuing.Intact
RAB.SuccEstabCSQueuing.Bgrd

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.2.5 Failed RAB establishments with queuing for CS domain

a) This measurement provides the number of RABs failed to establish for CS domain in which a queuing process has been involved. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each RAB failed to establish is added to the relevant measurement according to the cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Establishment Failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailEstabCSQueuing.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.3 RAB establishment for PS domain

4.1.3.0 Introduction

The five measurement types defined in the clause 4.1.3 for PS domain are subject to the "4 out of 5 approach".

4.1.3.1 Attempted RAB establishments for PS domain

a) This measurement provides the number of requested RABs in establishment attempts for PS domain. The measurement is split into subcounters per traffic class.

b) CC

c) On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for PS domain, each requested RAB in establishment attempts is added to the relevant measurement according to the traffic class requested. See TS 25.413 [5] and TS 23.107 [2]. For streaming service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384kbps
downlink<D>:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384 kbps
As indicated above, and <D> are integer values that map to the streaming service specified uplink and downlink data rates respectively.

NOTE: The addition is performed with the condition that the RAB has not been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

d) Four integer values.

e) RAB.AttEstabPS.Conv
RAB.AttEstabPS.Strm.<D>
RAB.AttEstabPS.Intact
RAB.AttEstabPS.Bgrd

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.3.2 Successful RAB establishments without queuing for PS domain

a) This measurement provides the number of successfully established RABs for PS domain in which a queuing process has not been involved. The measurement is split into subcounters per traffic class.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each successfully established RAB is added to the relevant measurement according to the traffic class. See TS 25.413 [5] and TS 23.107 [2]. For streaming service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384kbps
downlink<D>:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384 kbps
As indicated above, and <D> are integer values that map to the streaming service specified uplink and downlink data rates respectively.

d) Four integer values.

e) RAB.SuccEstabPSNoQueuing.Conv
RAB.SuccEstabPSNoQueuing.Strm.<D>
RAB.SuccEstabPSNoQueuing.Intact
RAB.SuccEstabPSNoQueuing.Bgrd

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.3.3 Failed RAB establishments without queuing for PS domain

a) This measurement provides the number of RABs failed to establish for PS in which a queuing process has not been involved. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each RAB failed to establish is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Establishment Failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailEstabPSNoQueuing.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.3.4 Successful RAB establishments with queuing for PS domain

a) This measurement provides the number of successfully established RABs for PS domain in which a queuing process has been involved. The measurement is split into subcounters per traffic class.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each successfully established RAB is added to the relevant measurement according to the traffic class.
See TS 25.413 [5] and TS 23.107 [2]. For streaming service, the relevant measurement according to the data rates requested, see TS 25.993 [13] as follows:
uplink:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384kbps
downlink<D>:
1: 14.4 kbps
2: 28.8 kbps
3: 57.6 kbps
4: 64 kbps
5: 128 kbps
6: 384 kbps
As indicated above, and <D> are integer values that map to the streaming service specified uplink and downlink data rates respectively.

d) Four integer values.

e) RAB.SuccEstabPSQueuing.Conv
RAB.SuccEstabPSQueuing.Strm.<D>
RAB.SuccEstabPSQueuing.Intact
RAB.SuccEstabPSQueuing.Bgrd

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.3.5 Failed RAB establishments with queuing for PS domain

a) This measurement provides the number of RABs failed to establish for PS domain in which a queuing process has been involved. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each RAB failed to establish is added to the relevant measurement according to the cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Establishment Failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailEstabPSQueuing.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.4 RAB modification for CS domain

4.1.4.0 Introduction

The five measurement types defined in the clause 4.1.4 for CS domain are subject to the "4 out of 5 approach".

4.1.4.1 Attempted RAB modifications for CS domain

This measurement provides the number of requested RABs in modification attempts for CS domain. The measurement is split into subcounters per traffic class.
CC
On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for CS domain, each requested RAB in modification attempts is added to the relevant measurement according to the traffic class requested. See TS 25.413 and TS 23.107.

NOTE: The addition is performed with the condition that the RAB has been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

Four integer values.
RAB.AttModCS.Conv
RAB.AttModCS.Strm
RAB.AttModCS.Intact
RAB.AttModCS.Bgrd
RncFunction
Valid for circuit switched traffic
UMTS

4.1.4.2 Successful RAB modifications without queuing for CS domain

This measurement provides the number of successfully modified RABs for CS domain in which a queuing process has not been involved. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each successfully modified RAB is added to the relevant measurement according to the traffic class requested in the RAB ASSIGNMENT REQUEST message. See TS 25.413 [5] and TS 23.107 [2].

NOTE: The addition is performed with the condition that the RAB has not been mentioned as queued in a previous RANAP RAB ASSIGNMENT RESPONSE and the RAB has been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

Four integer values.
RAB.SuccModCSNoQueuing.Conv
RAB.SuccModCSNoQueuing.Strm
RAB.SuccModCSNoQueuing.Intact
RAB.SuccModCSNoQueuing.Bgrd
RncFunction
Valid for circuit switched traffic
UMTS

4.1.4.3 Failed RAB modifications without queuing for CS domain

This measurement provides the number of RABs failed to modify for CS domain in which a queuing process has not been involved. The measurement is split into subcounters per failure cause.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each RAB failed to modify is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Modification Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.FailModCSNoQueuing.Cause
where Cause identifies the failure cause.
RncFunction
Valid for circuit switched traffic
UMTS

4.1.4.4 Successful RAB modifications with queuing for CS domain

This measurement provides the number of successfully modified RABs for CS domain in which a queuing process has been involved. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each successfully modified RAB is added to the relevant measurement according to the traffic class.
See TS 25.413 [5] and TS 23.107 [2].

NOTE: The addition is performed with the condition that the RAB has been mentioned as queued in a previous RANAP RAB ASSIGNMENT RESPONSE and the RAB has been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

Four integer values.
RAB.SuccModCSQueuing.Conv
RAB.SuccModCSQueuing.Strm
RAB.SuccModCSQueuing.Intact
RAB.SuccModCSQueuing.Bgrd
RncFunction
Valid for circuit switched traffic
UMTS

4.1.4.5 Failed RAB modifications with queuing for CS domain

This measurement provides the number of RABs failed to modify for CS domain in which a queuing process has been involved. The measurement is split into subcounters per failure cause.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each RAB failed to modify is added to the relevant measurement according to the cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Modification Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.FailModCSQueuing.Cause
where Cause identifies the failure cause.
RncFunction
Valid for circuit switched traffic
UMTS

4.1.5 RAB modification for PS domain

4.1.5.0 Introduction

The five measurement types defined in the clause 4.1.5 for PS domain are subject to the "4 out of 5 approach".

4.1.5.1 Attempted RAB modifications for PS domain

This measurement provides the number of requested RABs in modification attempts for PS domain. The measurement is split into subcounters per traffic class.
CC
On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for PS domain, each requested RAB in modification attempts is added to the relevant measurement according to the traffic class requested.
See TS 25.413 [5] and TS 23.107 [2].

NOTE: The addition is performed with the condition that the RAB has been setup or modified successfully in a previous RANAP RAB ASSIGNMENT RESPONSE or RELOCATION REQUEST ACKNOWLEDGE.

Four integer values.
RAB.AttModPS.Conv
RAB.AttModPS.Strm
RAB.AttModPS.Intact
RAB.AttModPS.Bgrd.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.5.2 Successful RAB modifications without queuing for PS domain

This measurement provides the number of successfully modified RABs for PS domain in which a queuing process has not been involved. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each successfully modified RAB is added to the relevant measurement according to the traffic class.
See TS 25.413 [5] and TS 23.107 [2].

Four integer values.
RAB.SuccModPSNoQueuing.Conv
RAB.SuccModPSNoQueuing.Strm
RAB.SuccModPSNoQueuing.Intact
RAB.SuccModPSNoQueuing.Bgrd.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.5.3 Failed RAB modifications without queuing for PS domain

This measurement provides the number of RABs failed to modify for PS in which a queuing process has not been involved. The measurement is split into subcounters per failure cause.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each RAB failed to modify is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Modification Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.FailModPSNoQueuing.Cause
where Cause identifies the failure cause.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.5.4 Successful RAB modifications with queuing for PS domain

This measurement provides the number of successfully modified RABs for PS domain in which a queuing process has been involved. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each successfully modified RAB is added to the relevant measurement according to the traffic class.
See TS 25.413 [5] and TS 23.107 [2].

Four integer values.
RAB.SuccModPSQueuing.Conv
RAB.SuccModPSQueuing.Strm
RAB.SuccModPSQueuing.Intact
RAB.SuccModPSQueuing.Bgrd.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.5.5 Failed RAB modifications with queuing for PS domain

This measurement provides the number of RABs failed to modify for PS domain in which a queuing process has been involved. The measurement is split into subcounters per failure cause.
CC
On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each RAB failed to modify is added to the relevant measurement according to the cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Modification Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.FailModPSQueuing.Cause
where Cause identifies the failure cause.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.6 RAB release request by CN for CS domain

4.1.6.0 Introduction

The three measurement types defined in the clause 4.1.6 for CS domain are subject to the "2 out of 3 approach".

4.1.6.1 Attempted RAB releases for CS domain

a) This measurement provides the number of requested RABs in release attempts for CS domain. The measurement is split into subcounters per release cause.

b) CC

c) On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for CS domain, each requested RAB in release attempts is added to the relevant measurement according to the release cause requested. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Attempts. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first. See TS 25.413 [5] and TS 23.107 [2].

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.AttRelCS.Cause
where Cause identifies the release cause.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.6.2 Successful RAB releases for CS domain

a) This measurement provides the number of successfully released RABs for CS domain. The measurement is split into subcounters per release cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each successfully released RAB is added to the relevant measurement according to the release cause requested in the RAB ASSIGNMENT REQUEST message. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Successes. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.
See TS 25.413 [5] and TS 23.107 [2].

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.SuccRelCS.Cause
where Cause identifies the release cause.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.6.3 Failed RAB releases for CS domain

a) This measurement provides the number of RABs failed to release for CS domain. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for CS domain, each RAB failed to release is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailRelCS.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for circuit switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.6.4 Void

4.1.6.5 Void

4.1.7 RAB release request by CN for PS domain

4.1.7.0 Introduction

The three measurement types defined in the clause 4.1.7 for PS domain are subject to the "2 out of 3 approach".

4.1.7.1 Attempted RAB releases for PS domain

a) This measurement provides the number of requested RABs in release attempts for PS domain. The measurement is split into subcounters per release cause.

b) CC

c) On receipt by the RNC of a RANAP RAB ASSIGNMENT REQUEST message for PS domain, each requested RAB in release attempts is added to the relevant measurement according to the release cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Attempts. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first. See TS 25.413 [5] and TS 23.107 [2].

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.AttRelPS.Cause
where Cause identifies the release cause.

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.7.2 Successful RAB releases for PS domain

a) This measurement provides the number of successfully released RABs for PS domain. The measurement is split into subcounters per release cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each successfully released RAB is added to the relevant measurement according to the release cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Successes. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first. See TS 25.413 [5] and TS 23.107 [2].

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) e) The measurement name has the form RAB.SuccRelPS.Cause
where Cause identifies the release cause.

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.7.3 Failed RAB releases for PS domain

a) This measurement provides the number of RABs failed to release for PS. The measurement is split into subcounters per failure cause.

b) CC

c) On transmission by the RNC of a RANAP RAB ASSIGNMENT RESPONSE message for PS domain, each RAB failed to release is added to the relevant measurement according to the failure cause. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Failures. In case only a subset of per cause measurements is supported, a sum measurement subtype will be provided first.

d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.

e) The measurement name has the form RAB.FailRelPS.Cause
where Cause identifies the failure cause.

f) RncFunction.

g) Valid for packet switched traffic.

h) UMTS.

i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

4.1.7.4 Void

4.1.7.5 Void

4.1.8 RAB setup time

4.1.8.1 RAB CS connection set-up time (Mean)

This measurement provides the mean time during each granularity period for a RNC to establish a RAB CS connection.
DER (n=1).
This measurement is obtained by accumulating the time intervals for each successful RAB establishment between the receipt by the RNC of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a RAB for CS domain, and the first corresponding (based on RAB ID) transmission by the RNC of a RANAP "RAB ASSIGNMENT RESPONSE" message for successfully established RABs over a granularity period using DER, see TS 25.413 [5]. This end value of the time will then be divided by the number of successfully established RABs observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.
Each measurement is an integer value.(in milliseconds).
RAB.SuccEstabCSSetupTimeMean
RncFunction
Valid for circuit switched traffic
UMTS

4.1.8.2 RAB CS connection set-up time (Maximum)

This measurement provides the maximum time during each granularity period for a RNC to establish a RAB CS connection.
GAUGE.
This measurement is obtained by monitoring the time intervals for each successful RAB establishment between the receipt by the RNC of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a RAB for CS domain, and the first corresponding (based on RAB ID) transmission by the RNC of a RANAP "RAB ASSIGNMENT RESPONSE" message for successfully established RABs see TS 25.413 [5]. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.
Each measurement is an integer value.(in milliseconds).
RAB.SuccEstabCSSetupTimeMax
RncFunction
Valid for circuit switched traffic
UMTS

4.1.8.3 RAB PS connection set-up time (Mean)

This measurement provides the mean time during each granularity period for a RNC to establish a RAB PS connection.
DER (n=1).
This measurement is obtained by accumulating the time intervals for each successful RAB establishment between the receipt by the RNC of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a RAB for PS domain, and the first corresponding (based on RAB ID) transmission by the RNC of a RANAP "RAB ASSIGNMENT RESPONSE" message for successfully established RABs over a granularity period using DER, see TS 25.413 [5]. This end value of the time will then be divided by the number of successfully established RABs observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialised at the beginning of each granularity period.
Each measurement is an integer value.(in milliseconds).
RAB.SuccEstabPSSetupTimeMean
RncFunction
Valid for packet switched traffic.
UMTS

4.1.8.4 RAB PS connection set-up time (Maximum)

This measurement provides the maximum time during each granularity period for a RNC to establish a RAB PS connection.
GAUGE.
This measurement is obtained by monitoring the time intervals for each successful RAB establishment between the receipt by the RNC of a RANAP "RAB ASSIGNMENT REQUEST" message to establish a RAB for PS domain, and the first corresponding (based on RAB ID) transmission by the RNC of a RANAP "RAB ASSIGNMENT RESPONSE" message for successfully established RABs see TS 25.413 [5]. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.
Each measurement is an integer value.(in milliseconds).
RAB.SuccEstabPSSetupTimeMax
RncFunction
Valid for packet switched traffic.
UMTS

4.1.9 RAB release request by UTRAN

4.1.9.1 RAB release requests for CS domain

This measurement provides the number of RABs requested to release by UTRAN for CS domain split into subcounters per cause.
CC
On transmission by the RNC of a RANAP RAB RELEASE REQUEST message for CS domain, each RAB requested to be released is added to the relevant per cause measurement. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Requests for the CS domain. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.RelReqCS.Cause
where Cause identifies the release cause.
RncFunction
Valid for circuit switched traffic
UMTS

4.1.9.2 RAB release requests for PS domain

This measurement provides the number of RABs requested to release by UTRAN for PS domain split into subcounters per cause.
CC
On transmission by the RNC of a RANAP RAB RELEASE REQUEST message for PS domain, each RAB requested to be released is added to the relevant per cause measurement. Possible causes are included in TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of RAB Release Requests for the PS domain. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix.
The measurement name has the form RAB.RelReqPS.Cause
where Cause identifies the release cause.
RncFunction
Valid for packet switched traffic.
UMTS

4.1.9.3 The number of RAB related to the Iu release request for CS domain

This measurement provides the number of RAB related to the Iu release request for CS domain. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP IU RELEASE REQUEST message for CS domain, each RAB related to the RANAP IU RELEASE REQUEST message is added to the relevant measurement according to the traffic class requested when the RANAP message IU RELEASE REQUEST is sent to the CS CN.
Each measurement is an integer value
RAB.NbrIuRelReqCS.Conv
RAB.NbrIuRelReqCS.Strm
RAB.NbrIuRelReqCS.Intact
RAB.NbrIuRelReqCS.Bgrd
UtranCellFDD
UtranCellTDDLcr
UtranCellTDDHcr
Valid for circuit switched traffic
UMTS

4.1.9.4 The number of RAB related to the Iu release request for PS domain

This measurement provides the number of RAB related to the Iu release request for PS domain. The measurement is split into subcounters per traffic class.
CC
On transmission by the RNC of a RANAP IU RELEASE REQUEST message for PS domain, each RAB related to the RANAP IU RELEASE REQUEST message is added to the relevant measurement according to the traffic class requested when the RANAP message IU RELEASE REQUEST is sent to the PS CN.
Each measurement is an integer value.
RAB.NbrIuRelReqPS.Conv
RAB.NbrIuRelReqPS.Strm
RAB.NbrIuRelReqPS.Intact
RAB.NbrIuRelReqPS.Bgrd
UtranCellFDD
UtranCellTDDLcr
UtranCellTDDHcr
Valid for packet switched traffic.
UMTS