4 Functionality related measurements

32.4533GPPPerformance Management (PM)Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS)Release 17Telecommunication managementTS

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

The measurements defined in this clause are related to the functionality aspect performance. The detailed measurements for each function are defined in the following subclauses.

4.1 Measurements related to HeNB-GW

A HeNB GW is optional in a HeNB subsystem. If the HeNB is connected by means of the standard S1 interface to the HeNB GW, more specifically through HeNB GW to the MME (Mobility Management Entity) by means of the S1-MME interface and to the Serving Gateway (S-GW) by means of the S1-U interface.

NOTE 1: These measurements are only effective when HeNB GW is included in HeNS.

4.1.1 Signalling Plane related measurements

4.1.1.1 Numbers of incoming SCTP packets on the S1 interface, from HeNB to HeNB GW

a) This measurement provides the number of SCTP data packets sent from HeNB to HeNB GW which have been accepted and processed by the SCTP protocol entity on the S1 interface.

b) CC.

c) Receipt of a SCTP data PDU from HeNB to HeNB GW on the S1-MME interface.

d) A single integer value.

e) S1.IncSctpPkt

f) HeNBGWFunction

g) Valid for packet switching

h) EPS

4.1.1.2 Numbers of outgoing SCTP packets on the S1 interface, from HeNB GW to HeNB

a) This measurement provides the number of SCTP data packets sent from HeNB GW to HeNB which have been generated by the SCTP protocol entity on the S1 interface.

b) CC.

c) Transmission of a SCTP data PDU from HeNB GW to HeNB on the S1-MME interface.

d) A single integer value.

e) S1.OutSctpPkt

f) HeNBGWFunction

g) Valid for packet switching

h) EPS

4.1.1.3 Numbers of octets of incoming SCTP packets on the S1 interface, from HeNB to HeNB GW

a) This measurement provides the number of octets of SCTP data packets sent from HeNB to HeNB GW which have been accepted and processed by the SCTP protocol entity on the S1 interface.

b) CC.

c) Receipt of a SCTP data PDU from HeNB to HeNB GW on the S1 interface.

d) A single integer value.

e) S1.IncSctpOct

f) HeNBGWFunction

g) Valid for packet switching

h) EPS

4.1.1.4 Numbers of octets of outgoing SCTP packets on the S1 interface, from HeNB GW to HeNB

a) This measurement provides the number of octets of SCTP data packets sent from HeNB GW to HeNB which have been generated by the SCTP protocol entity on the S1 interface.

b) CC.

c) Transmission of a SCTP data PDU from HeNB GW to HeNB on the Iuh interface.

d) A single integer value.

e) S1.OutSctpOct

f) HeNBGWFunction

g) Valid for packet switching

h) EPS

4.1.2 User plane related measurements

4.1.2.1 Numbers of incoming GTP-U packets of S1 interface, from HeNB to HeNB GW

a) This measurement provides the number of GTP-U data packets on the user plane, sent from HeNB to HeNB GW on S1 interface.

b) CC.

c) Receipt of an GTP-U data PDU from HeNB to HeNB GW on the user plane of S1 interface.

d) A single integer value.

e) S1.IncPsPkt

f) HeNBGWFunction

g) Valid for packet switched traffic

h) EPS

4.1.2.2 Numbers of outgoing GTP-U packets of S1 interface, from HeNB GW to HeNB

a) This measurement provides the number of GTP-U data packets sent on the user plane, from HeNB GW to HeNB on S1 interface.

b) CC.

c) Transmission of an GTP-U data PDU from HeNB GW to HeNB on the user plane of S1 interface.

d) A single integer value.

e) S1.OutPsPkt

f) HeNBGWFunction

g) Valid for packet switched traffic

h) EPS

4.1.2.3 Numbers of octets of incoming GTP-U packets of S1 interface, from HeNB to HeNB GW

a) This measurement provides the number of octets of GTP-U data packets on the user plane, sent from HeNB to HeNB GW on S1 interface.

b) CC.

c) Receipt of an GTP-U data PDU from HeNB to HeNB GW on the user plane of S1 interface.

d) A single integer value.

e) S1.IncPsOct

f) HeNBGWFunction

g) Valid for packet switched traffic

h) EPS

4.1.2.4 Numbers of octets of outgoing GTP-U packets of S1 interface, from HeNB GW to HeNB

a) This measurement provides the number of octets of GTP-U data packets on the user plane, sent from HeNB GW to HeNB on S1 interface.

b) CC.

c) Transmission of an GTP-U data PDU from HeNB GW to HeNB on the user plane of S1 interface.

d) A single integer value.

e) S1.OutPsOct

f) HeNBGWFunction

g) Valid for packet switched traffic

h) EPS

4.2 Measurements related to HeNB

4.2.1 Measurements related to CSG service

4.2.1.1 Overview

A Closed Subscriber Group identifies subscribers of an operator who are permitted to access one or more cells of the PLMN but which have restricted access (CSG cells).

The CSG inbound mobility procedure provides means for UEs switching from other cells to CSG HeNBs or to Hybrid Cells in RRC_CONNECTED mode. The procedure is triggered when the target HeNB receives a HANDOVER REQUEST message from the MME, including the CSG id and – for handover to a hybrid cell – CSG Membership Status. In case the target HeNB is connected to MME through HeNB GW, the HANDOVER REQUEST message should be sent from the HeNB GW. The successful CSG inbound mobility rate poses an important impact on the QoE, therefore it is essential to define related measurements

The CSG inbound mobility procedure is initiated by MME.

Performance measurement definitions in this subclause are based on 3GPP TS 36.413 [6].

The following paragraphs are of interest for this purpose:

HANDOVER REQUEST
HANDOVER REQUEST ACKNOWLEDGE
HANDOVER FAILURE

These paragraphs show in particular the following diagram.

Figure 1 CSG UE Inbound Procedure: Successful Operation

Figure 2 CSG UE Inbound Procedure: Unsuccessful Operation

4.2.1.2 Mean number of attached CSG UEs in HeNB

This measurement provides the mean number of attached CSG UEs in the HeNB.
SI
This measurement is obtained by sampling at a pre-defined interval the number of CSG UEs in the HeNB and then taking the arithmetic mean (see TS 36.300 [5]).
A single integer value
CSG.MeanNbrUsr
HeNB
Valid for circuit and packet switched traffic
EPS

4.2.1.3 Inbound CSG mobility measurements

The three measurement types defined in the subclause 4.2.1.3 are subject to the "2 out of 3 approach".

4.2.1.3.1 Attempted inbound mobility for UEs to CSG cells or Hybrid cells in RRC_CONNECTED mode

This measurement provides the number of attempted inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode
CC
Receipt by the HeNB of a S1AP message HANDOVER REQUEST from the MME/HeNB GW with the “CSG id” IE, and “CSG Membership Status” IE for handover to a hybrid cell (see TS 36.413 [6]).
A single integer value.
CSG.AttInboundMobility
HeNB
Valid for circuit and packet switched traffic
EPS

4.2.1.3.2 Successful inbound mobility for UEs to CSG cells or Hybrid cells in RRC_CONNECTED mode

This measurement provides the number of successful inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode
CC
Transmission by the HeNB of a S1AP message HANDOVER REQUEST ACKNOWLEDGE to the MME/HeNB GW, corresponding to the receipt by the HeNB of a S1AP message HANDOVER REQUEST from the MME/HeNB GW with the “CSG id” IE, and “CSG Membership Status” IE for handover to a hybrid cell (see TS 36.413 [6]).
A single integer value.
CSG.SuccInboundMobility
HeNB
Valid for circuit and packet switched traffic
EPS

4.2.1.3.3 Failed inbound mobility for UEs to CSG cells or Hybrid cells in RRC_CONNECTED mode

This measurement provides the number of failed successful inbound mobility for UEs to CSG cells or hybrid cells in RRC_CONNECTED mode
CC
Transmission by the HeNB of a S1AP message HANDOVER FAILURE to the MME/HeNB GW, corresponding to the receipt by the HeNB of a S1AP message HANDOVER REQUEST from the MME/HeNB GW with the “CSG id” IE, and “CSG Membership Status” IE for handover to a hybrid cell (see TS 36.413 [6]).
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.
CSG.FailedInboundMobility. Cause

where Cause identifies the failure cause.

HeNB
Valid for circuit and packet switched traffic
EPS

4.2.2 Measurements related to RRC

4.2.2.1 Overview

Performance Measurement definitions in this subclause are based on 3PGG TS 36.413 [6].

The following paragraphs are of interest for this purpose:

RRC CONNECTION REQUEST
RRC CONNECTION SETUP COMPLETE
RRC CONNECTION REJECT

These paragraphs show in particular the following diagrams.

Figure 3 RRC connection establishment, successful

Figure 4 RRC connection establishment, network reject

4.2.2.2 RRC connection establishments

The three measurement types defined in the clause 4.2.2.2 for HeNB are subject to the "2 out of 3 approach".

4.2.2.2.1 Attempted RRC connection establishments

This measurement provides the number of RRC connection establishment attempts for each establishment cause.
CC
Receipt of an RRC CONNECTION REQUEST message by the HeNB from the UE. Each RRC Connection Request message received is added to the relevant per cause measurement. The possible causes are included in TS 36.331 [7]. The sum of all supported per cause measurements shall equal the total number of RRC Connection Establishment attempts. 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 RRC.AttConnEstab.Cause
where Cause identifies the Establishment Cause.
HeNB
Valid for packet switched traffic
EPS

4.2.2.2.2 Successful RRC connection establishments

This measurement provides the number of successful RRC establishments for each establishment cause.
CC
Receipt by the HeNB of a RRC CONNECTION SETUP COMPLETE message following a RRC establishment attempt. Each RRC Connection Setup Complete message received is added to the relevant per cause measurement. The possible causes are included in TS 36.331 [7]. The sum of all supported per cause measurements shall equal the total number of RRC Connection Establishments. 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 RRC.SuccConnEstab.Cause
where Cause identifies the Establishment Cause.
HeNB
Valid for packet switched traffic
EPS

4.2.2.2.3 Failed RRC connection establishments

This measurement provides the number of RRC establishment failures for each rejection cause.
CC
Transmission of an RRC CONNECTION REJECT message by the HeNB to the UE or an expected RRC Connection Setup Complete message not received by the HeNB. Each failed RRC connection establishment is added to the relevant per establishment cause measurement. The possible causes are included in TS 36.331 [7].
The sum of all supported per cause measurements shall equal the total number of RRC connection establishment failures. 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 RRC. FailConnEstab.Cause
where Cause identifies the Rejection Cause.
HeNB
Valid for packet switched traffic
EPS

4.2.3 Measurements related to E-RAB

4.2.3.1 Overview

Performance Measurement definitions in this subclause are based on 3PGG TS 36.413 [6].

The following paragraphs are of interest for this purpose:

INITIAL CONTEXT SETUP REQUEST
INITIAL CONTEXT SETUP RESPONSE
INITIAL CONTEXT SETUP FAILURE
UE CONTEXT RELEASE REQUEST
E-RAB SETUP REQUEST;
E-RAB SETUP RESPONSE;
E-RAB RELEASE INDICATION.

These paragraphs show in particular the following diagrams.

Figure 5 Initial Context Setup procedure. Successful operation

Figure 6 Initial Context Setup procedure. Unsuccessful operation

Figure 7 UE Context Release Request procedure. Successful operation

Figure 8 E-RAB Setup procedures

Figure 9 E-RAB Release INDICATION procedure. Successful operation

4.2.3.2 Initial E-RAB setup

The three measurement types defined in the clause 4.2.3.2 for HeNB are subject to the "2 out of 3 approach".

4.2.3.2.1 Number of initial E-RABs attempted to setup

This measurement provides the number of initial E-RABs attempted to setup. The measurement is split into subcounters per E-RAB QoS level (QCI).
CC
On receipt by the HeNB of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RABs in the message is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [6]. The sum of all supported per QCI measurements shall equal the total number of SAE Bearers attempted to setup. In case only a subset of per QCI 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 QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form ERAB.EstabInitAttNbr.QCI
where QCI identifies the E-RAB level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.3.2.2 Number of initial E-RABs successfully established

This measurement provides the number of initial E-RABs successfully established. The measurement is split into subcounters per E-RAB QoS level (QCI).
CC
On transmission by the HeNB of an INITIAL CONTEXT SETUP RESPONSE message, each E-RAB successfully established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [6]. The sum of all supported per QCI measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per QCI 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 QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form ERAB.EstabInitSuccNbr.QCI
where QCI identifies the E-RAB level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.3.2.3 Number of initial E-RABs failed to setup

This measurement provides the number of initial E-RABs failed to setup. The measurement is split into subcounters per failure cause.
CC
On transmission by the HeNB of an INITIAL CONTEXT SETUP RESPONSE, or INITIAL CONTEXT SETUP FAILURE message, each E-RAB failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 36.413 [6]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to setup. 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 ERAB.EstabInitFailNbr.Cause
where Cause identifies the cause resulting in the initial E-RAB setup failure.
HeNB
Valid for packet switched traffic
EPS

4.2.3.3 E-RAB setup

The three measurement types defined in the clause 4.2.3.3 for HeNB are subject to the "2 out of 3 approach".

4.2.3.3.1 Number of E-RABs attempted to setup

This measurement provides the number of E-RABs attempted to setup. The measurement is split into subcounters per E-RAB QoS level (QCI).
CC
On receipt by the HeNB of a E-RAB SETUP REQUEST message, each requested E-RAB in the message is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [6]. The sum of all supported per QCI measurements shall equal the total number of additional E-RABs attempted to setup. In case only a subset of per QCI 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 QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form ERAB. EstabAttNbr.QCI
where QCI identifies the E-RAB level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.3.3.2 Number of E-RABs successfully established

This measurement provides the number of E-RABs successfully established. The measurement is split into subcounters per E-RAB QoS level (QCI).
CC
On transmission by the HeNB of a E-RAB SETUP RESPONSE message, each E-RAB successfully established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [6]. The sum of all supported per QCI measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per QCI 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 QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form ERAB.EstabSuccNbr.QCI
where QCI identifies the E-RAB level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.3.3.3 Number of E-RABs failed to setup

This measurement provides the number of E-RABs failed to setup. The measurement is split into subcounters per failure cause.
CC
On transmission by the HeNB of a E-RAB SETUP RESPONSE message, each E-RAB failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 36.413 [6]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to setup. 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 ERAB. EstabFailNbr.Cause
where Cause identifies the cause resulting in the additional E-RAB setup failure.
HeNB
Valid for packet switched traffic
EPS

4.2.3.4 E-RAB release request by HeNS

4.2.3.4.1 Number of E-RABs requested to release initiated by HeNB per QCI

This measurement provides the number of E-RABs requested to release initiated by HeNB. The measurement is split into subcounters per E-RAB QoS level (QCI).
CC
On transmission by the HeNB of a E-RAB RELEASE INDICATION or UE CONTEXT RELEASE REQUEST message, each corresponding E-RAB requested to release is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413 [6]. The sum of all supported per QCI measurements shall equal the total number of E-RABs requested to release initiated by HeNB. In case only a subset of per QCI 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 QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form ERAB.RelEnbNbr.QCI
where QCI identifies the E-RAB level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.3.4.2 Number of E-RABs requested to release initiated by HeNB per cause

This measurement provides the number of E-RABs requested to release initiated by HeNB. The measurement is split into subcounters per cause.
CC
On transmission by the HeNB of a E-RAB RELEASE INDICATION or UE CONTEXT RELEASE REQUEST message, each corresponding E-RAB requested to release is added to the relevant measurement per cause. Possible causes are included in TS 36.413 [6].
Each measurement is an integer value. The number of measurements is equal to the number of supported causes.
The measurement names have the form ERAB.RelEnbNbr.cause
where cause identifies the reason for the E-RABs release request initiated by HeNB.
HeNB
Valid for packet switched traffic
EPS

4.2.3.5 E-RAB for Direct User Plane Path between HeNB and LGW

4.2.3.5.1 Number of Direct User Plane Path

The three measurement types defined in the clauses 4.2.3.5.2, 4.2.3.5.3 and 4.2.3.5.4 are subject to the "2 out of 3 approach".

4.2.3.5.1 Number of Direct User Plane Path attempted to setup

This measurement provides the number of direct user plane path between HeNB and Local GW attempted to setup.
CC
On receipt by the HeNB of an INITIAL CONTEXT SETUP REQUEST message (for initial E-RAB setup) or E-RAB SETUP REQUEST message (for other E-RAB setup) and the PDN connection is established for Local IP Access, each requested E-RABs in the message is added to the relevant measurement. The message includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. The Correlation ID is equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5). (3GPP TS 23.401[3]).
Integer.
The measurement name has the form ERAB.EstabDirectPathLGWAttNbr.
HeNB
Valid for packet switched traffic
EPS

4.2.3.5.2 Number of Direct User Plane Path successfully established

This measurement provides the number of direct user plane path between HeNB and Local GWsuccessfully established.
CC
On transmission by the HeNB of an INITIAL CONTEXT SETUP RESPONSE message(for initial E-RAB setup) or E-RAB SETUP RESPONSE message (for other E-RAB setup)and the PDN connection is established for Local IP Access, each E-RAB successfully established is added to the relevant measurement.
Integer.
The measurement name has the form ERAB.EstabDirectPathLGWSuccNbr.
HeNB
Valid for packet switched traffic
EPS

4.2.3.5.3 Number of Direct User Plane Path failed to setup

This measurement provides the number of direct user plane path between HeNB and Local GW E-RABs failed to setup.
CC
On transmission by the HeNB of an INITIAL CONTEXT SETUP RESPONSE/INITIAL CONTEXT SETUP FAILURE message (for initial E-RAB setup) or E-RAB SETUP RESPONSE message (for other E-RAB setup) and the PDN connection is established for Local IP Access, each E-RAB failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 36.413[6]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to setup. 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 ERAB.EstabDirectPathLGWFailNbr.Cause, where Cause identifies the cause resulting in the E-RAB setup failure.
HeNB
Valid for packet switched traffic
EPS

4.2.4 Measurements related to handover

4.2.4.1 Overview

Performance Measurement definitions in this subclause are based on 3PGG TS 36.413 [6].

The following paragraph is of interest for this purpose:

– HANDOVER REQUEST

– HANDOVER REQUEST ACKNOWLEDGE

– RRC CONNECTION RECONFIGURATION

– RRC CONNECTION RECONFIGURATION COMPLETE

– RRC CONNECTION REESTABLISHMENT

– MOBILITY FROM EUTRA COMMAND

– UE CONTEXT RELEASE COMMAND

These paragraphs show in particular the following diagrams:

Figure10: Handover resource allocation: successful

Figure11: RRC connection reconfiguration, successful

Figure12: RRC connection reconfiguration, failure

Figure13: Mobility from E-UTRA, successful

Figure14: Mobility from E-UTRA, failure

Figure15: UE Context Release procedure. Successful

4.2.4.2 eNB related Handovers

4.2.4.2.1 Attempted outgoing handover to eNB per handover cause

This measurement provides the number of attempted outbound handover to eNB per handover cause.
CC.
Transmission of the RRCConnectionReconfiguration message from HeNB to the UE, indicationg the handover to eNB (see TS 36.331 [7]). The sum of all supported per cause measurements shall equal the total number of handover to eNB events. 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 supported plus a possible sum value identified by the .sum suffix.
HO. ToeNBAtt.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.2.2 Successful outgoing handover to eNB per handover cause

This measurement provides the number of successful outbound handover to eNB per handover cause.
CC.
Receipt of a S1AP message UE CONTXT RELEASE COMMAND sent from the MME to the HeNB, indicating a successful handover to eNB with specific cause (see TS 36.413 [6]).The sum of all supported per cause measurements shall equal the total number of outgoing intra-eNB handover events. 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 supported plus a possible sum value identified by the .sum suffix
HO. ToeNBSucc.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.2.3 Failed outgoing handover to eNB per handover cause

This measurement provides the number of failed outbound handover to eNB per handover cause.
CC
Transmission of the RRCConnectionReestablishmentRequest message by the UE to the HeNB, indicating the RRC connection reestablishment(see TS 36.331 [7]).The sum of all supported per cause measurements shall equal the total number of handover from eNB events. 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 supported plus a possible sum value identified by the .sum suffix
HO. ToeNBFail.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.2.4 Attempted incoming handover from eNB per handover cause

This measurement provides the number of attempted inbound handover from eNB per handover cause.
CC.
Receipt of a S1AP message HANDOVER REQUEST sent from the MME to the HeNB (see TS 36.413 [6]). The sum of all supported per cause measurements shall equal the total number of handover from eNB events. 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 supported plus a possible sum value identified by the .sum suffix.
HO. FromeNBAtt.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.2.5 Successful incoming handover from eNB per handover cause

This measurement provides the number of successful inbound handover from eNB per handover cause.
CC.
Receipt of a RRCConnectionReconfigurationComplete message sent from theUE to the HeNB, indicating a successful handover from eNB with specific cause (see TS 36.331 [7]).The sum of all supported per cause measurements shall equal the total number of handover from eNB events. 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 supported plus a possible sum value identified by the .sum suffix
HO. FromeNBSucc.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.2.6 Failed incoming handover from eNB per handover cause

This measurement provides the number of failed inbound handover from eNB per handover cause.
CC
Transmission of the RRCConnectionReestablishmentRequest message by the UE to the eNB, indicating the RRC connection reestablishment(see TS 36.331 [7]).The sum of all supported per cause measurements shall equal the total number of handover from eNB events. 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 supported plus a possible sum value identified by the .sum suffix
HO. FromeNBFail.Cause
where Cause identifies the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.3 Inter-RAT Handovers

4.2.4.3.1 Attempted outgoing handovers to UTRAN per handover cause

This measurement provides the number of attempted outgoing handovers to UTRAN per cause and target cell specific.
CC.
Transmission of the MobilityFromEUTRACommand message from the HeNB to the UE indicating the attempt of an outgoing handover from HeNS to UTRAN with a specific cause (see TS 36.331 [7]). The sum of all supported per cause measurements shall equal the total number of outgoing handover to UTRAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToUtranAtt.Cause
where Cause identifies the cause for handover
HeNB
Valid for packet switched traffic
EPS

4.2.4.3.2 Successful outgoing handovers to UTRAN per handover cause

This measurement provides the number of successful outgoing handovers to UTRAN per cause target cell specific.
CC.
Receipt of a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME to the HeNB, indicating a successful handover initiated due to a specific cause (see TS 36.413 [6]).The sum of all supported per cause measurements shall equal the total number of outgoing handover to UTRAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToUtranSucc.Cause
where Cause indicating the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.3.3 Failed outgoing handovers to UTRAN per handover cause

This measurement provides the number of failed outgoing handovers to UTRAN per cause target cell specific.
CC
Transmission of the RRCConnectionReestablishmentRequest message by the UE to the HeNB, indicating the RRC connection reestablishment(see TS 36.331 [7]). The sum of all supported per cause measurements shall equal the total number of outgoing handover to UTRAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToUtranFail.Cause
where Cause indicating the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.3.4 Attempted outgoing handovers to GERAN per handover cause

This measurement provides the number of attempted outgoing handovers to GERAN per cause and target cell specific.
CC.
Transmission of the MobilityFromEUTRACommand message from the HeNB to the UE indicating the attempt of an outgoing handover from HeNS to GERAN with a specific cause (see TS 36.331 [7]). The sum of all supported per cause measurements shall equal the total number of outgoing handover to GERAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToGeranAtt.Cause
where Cause identifies the cause for handover
HeNB
Valid for packet switched traffic
EPS

4.2.4.3.5 Successful outgoing handovers to GERAN per handover cause

This measurement provides the number of successful outgoing handovers to GERAN per cause target cell specific.
CC.
Receipt of a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME to the HeNB, indicating a successful handover initiated due to a specific cause (see TS 36.413 [6]).The sum of all supported per cause measurements shall equal the total number of outgoing handover to GERAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToGeranSucc.Cause
where Cause indicating the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.4.3.6 Failed outgoing handovers to GERAN per handover cause

This measurement provides the number of failed outgoing handovers to GERAN per cause target cell specific.
CC.
Transmission of the RRCConnectionReestablishmentRequest message by the UE to the HeNB, indicating the RRC connection reestablishment(see TS 36.331 [7]). The sum of all supported per cause measurements shall equal the total number of outgoing handover to UTRAN events. 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 supported plus a possible sum value identified by the .sum suffix.
HO.ToGeranFail.Cause
where Cause indicating the cause for handover.
HeNB
Valid for packet switched traffic
EPS

4.2.5 Measurements related to PDCP SDU bit-rate

4.2.5.1 Average DL cell PDCP SDU bit-rate

This measurement provides the average cell bit-rate of PDCP SDUs on the downlink. This represents the ingress rate of user plane traffic to the HeNB (via S1). The measurement is split into subcounters per SAE Bearer QoS level (QCI).
CC
This measurement is obtained according to the Scheduled IP Throughput definition in 3GPP TS 36.314 [8].
Each measurement is an integer value representing the bit-rate measured in kb/s. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB.PdcpSduBitrateDl.QCI
where QCI identifies the SAE Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.5.2 Average UL cell PDCP SDU bit-rate

This measurement provides the average cell bit-rate of PDCP SDUs on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. The measurement is split into subcounters per SAE Bearer QoS level (QCI).
CC
This measurement is obtained according to the Scheduled IP Throughput definition in 3GPP TS 36.314 [8].
Each measurement is an integer value representing the bit-rate measured in kb/s. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB. PdcpSduBitrateUl.QCI
where QCI identifies the SAE Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.5.3 Maximum DL cell PDCP SDU bit-rate

This measurement provides the maximum cell bit-rate of PDCP SDUs on the downlink. This represents the maximum ingress rate of user plane traffic to the HeNB (via S1). This is a sum counter measured across all QCIs.
SI
This measurement is obtained according to the Scheduled IP Throughput definition in 3GPP TS 36.314 [8].
A single integer value representing the maximum bit-rate measured in kb/s.
DRB.PdcpSduBitrateDlMax
HeNB
Valid for packet switched traffic
EPS

4.2.5.4 Maximum UL cell PDCP SDU bit-rate

This measurement provides the maximum cell bit-rate of PDCP SDUs measured on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. This is a sum counter measured across all QCIs.
SI
This measurement is obtained according to the scheduled IP throughput definition in 3GPP TS 36.314 [8].
A single integer value representing the maximum bit-rate measured in kb/s.
DRB.PdcpSduBitrateUlMax
HeNB
Valid for packet switched traffic
EPS

4.2.6 Measurements related to Packet Delay and Drop Rate

4.2.6.1 Average DL PDCP SDU delay

This measurement provides the average (arithmetic mean) PDCP SDU delay on the downlink. The measurement is split into subcounters per ERAB Bearer QoS level (QCI).
DER (n=1)
This measurement is obtained according to the definition in 3GPP TS 36.314 [8].
Each measurement is an integer value representing the mean delay in ms. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB.PdcpSduDelayDl.QCI
where QCI identifies the ERAB Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.6.2 DL PDCP SDU drop rate

This measurement provides the fraction of IP packets (PDCP SDUs) which are dropped on the downlink. Only user-plane traffic (DTCH) is considered. A dropped packet is one whose context is removed from the HeNB without any part of it having been transmitted on the air interface. Packets discarded during handover are excluded from the count. The measurement is split into subcounters per ERAB Bearer QoS level (QCI).
SI
This measurement is obtained according to the definition in 3GPP TS 36.314 [8]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a drop rate subcounter calculated across all QCIs will be provided first.
Each measurement is an integer value representing the drop rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB.PdcpSduDropRateDl.QCI
where QCI identifies the target ERAB Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.7 Measurements related to Packet Loss Rate

4.2.7.1 DL PDCP SDU air interface loss rate

This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully transmitted) on the downlink air interface. Only user-plane traffic (DTCH) is considered. A lost packet is one whose context is removed from the HeNB after an attempt has been made to transmit part or all of the packet on the air interface but the whole packet has not been successfully transmitted. The measurement is split into subcounters per ERAB Bearer QoS level (QCI).
SI
This measurement is obtained according to the definition in 3GPP TS 36.314 [8]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter calculated across all QCIs will be provided first.
Each measurement is an integer value representing the air interface loss rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB. PdcpSduAirLossRateDl.QCI
where QCI identifies the target ERAB Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.7.2 UL PDCP SDU loss rate

This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully received) on the uplink. Only user-plane traffic (DTCH) and only PDCP SDUs that have entered PDCP (and given a PDCP sequence number) are considered. The measurement is split into subcounters per ERAB Bearer QoS level (QCI).
SI
This measurement is obtained according to the definition in 3GPP TS 36.314 [8]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter calculated across all QCIs will be provided first.
Each measurement is an integer value representing the loss rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix.
The measurement name has the form DRB.PdcpSduLossRateUl.QCI
where QCI identifies the target ERAB Bearer level quality of service class.
HeNB
Valid for packet switched traffic
EPS

4.2.8 Measurements related to Radio Resource Usage

4.2.8.1 DL Total PRB Usage

a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink for any purpose.

b) SI.

c) This measurement is obtained according to the definition in 3GPP TS 36.314 [8].

d) A single integer value from 0 to 100.

e) RRU.PrbTotDl, which indicates the DL PRB Usage for all traffic.

f) HeNB.

g) Valid for packet switched traffic.

h) EPS.

4.2.8.2 UL Total PRB Usage

a) This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink for any purpose.

b) SI

c) This measurement is obtained according to the definition in 3GPP TS 36.314 [8].

d) A single integer value from 0 to 100.

e) RRU.PrbTotUl, which indicates the UL PRB Usage for all traffic

f) HeNB

g) Valid for packet switched traffic

h) EPS

4.2.8.3 Average number of active UEs on the DL

a) This measurement provides the average number of UEs that have DTCH data queued on the downlink. The measurement is split into subcounters per E-RAB QoS level (QCI).

b) SI

c) This measurement is obtained according to the definition in 3GPP TS 36.314 [8]. Separate counters are maintained for each QCI.

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

e) The measurement name has the form
DRB.UEActiveDl.QCI
where QCI identifies the E-RAB level quality of service class.

f) HeNB

g) Valid for packet switched traffic

h) EPS

4.2.8.4 Average number of active UEs on the UL

a) This measurement provides the average number of UEs that have DTCH data queued on the uplink.

b) SI

c) This measurement is obtained according to the definition in 3GPP TS 36.314 [8]. Separate counters are maintained for each QCI.

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

e) The measurement name has the form
DRB.UEActiveUl.QCI
where QCI identifies the E-RAB level quality of service class.

f) HeNB

g) Valid for packet switched traffic

h) EPS

Annex A: Use cases for performance measurements definition