4.10 Hard handover

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

4.10.1 Void

4.10.2 Outgoing intra-NodeB hard handovers

4.10.2.0 Introduction

The three measurement types defined in the subclause 4.10.2 for outgoing intra-NodeB hard handovers are subject to the "2 out of 3 approach".

4.10.2.1 Attempted outgoing intra-NodeB hard handovers

  1. This measurement provides the number of attempted outgoing intra-NodeB hard handovers.
  2. CC.
  3. Transmission of a RRC message PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, or TRANSPORT CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of an outgoing intra-NodeB hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.AttOutIntraNodeB.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.2.2 Successful outgoing intra-NodeB hard handovers

  1. This measurement provides the number of successful outgoing intra-NodeB hard handovers.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing intra-NodeB hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.SuccOutIntraNodeB.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.2.3 Failed outgoing intra-NodeB hard handovers

  1. This measurement provides the number of failed outgoing intra-NodeB hard handovers per cause.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE sent from the UE to the source RNC, indicating a failed outgoing intra-NodeB hard handover. Failure causes are defined within TS 25.331 [4].

    Each expected RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  4. 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.
  5. The measurement name has the form HHO.FailOutIntraNodeB.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.3 Outgoing inter-NodeB, intra-RNC hard handovers

4.10.3.0 Introduction

The three measurement types defined in the subclause 4.10.3 for outgoing inter-NodeB, intra-RNC hard handovers are subject to the "2 out of 3 approach".

4.10.3.1 Attempted outgoing inter-NodeB, intra-RNC hard handovers

  1. This measurement provides the number of attempted outgoing inter-NodeB, intra-RNC hard handovers.
  2. CC.
  3. Transmission of a RRC message PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, or TRANSPORT CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of an outgoing inter-NodeB, intra-RNC hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.AttOutInterNodeBIntraRNC.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.3.2 Successful outgoing inter-NodeB, intra-RNC hard handovers

  1. This measurement provides the number of successful outgoing inter-NodeB, intra-RNC hard handovers.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing inter-NodeB, intra-RNC hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.SuccOutInterNodeBIntraRNC.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.3.3 Failed outgoing inter-NodeB, intra-RNC hard handovers

  1. This measurement provides the number of failed outgoing inter-NodeB, intra-RNC hard handovers per cause.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE sent from the UE to the source RNC, indicating a failed outgoing inter-NodeB, intra-RNC hard handover. Failure causes are defined within TS 25.331 [4].

    Each expected RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  4. 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.
  5. The measurement name has the form HHO.FailOutInterNodeBIntraRNC.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.4 Outgoing inter-RNC hard handovers via Iur

4.10.4.0 Introduction

The three measurement types defined in the subclause 4.10.4 for outgoing inter-RNC hard handovers are subject to the "2 out of 3 approach".

4.10.4.1 Attempted outgoing inter-RNC hard handovers via Iur

  1. This measurement provides the number of attempted outgoing inter-RNC hard handovers via Iur.
    This measurement is only valid for FDD mode.
  2. CC.
  3. Transmission of a RRC message PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, or TRANSPORT CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of an outgoing inter-RNC hard handover via Iur (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.AttOutInterRNCIur.
  6. UtranCellFDD
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.4.2 Successful outgoing inter-RNC hard handovers via Iur

  1. This measurement provides the number of successful outgoing inter-RNC hard handovers via Iur.
    This measurement is only valid for FDD mode.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing inter-RNC hard handover via Iur (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.SuccOutInterRNCIur.
  6. UtranCellFDD
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.4.3 Failed outgoing inter-RNC hard handovers via Iur

  1. This measurement provides the number of failed outgoing inter-RNC hard handovers via Iur per cause.
    This measurement is only valid for FDD mode.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE sent from the UE to the source RNC, indicating a failed outgoing inter-RNC hard handover via Iur. Failure causes are defined within TS 25.331 [4].

    Each expected RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  4. 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.
  5. The measurement name has the form HHO.FailOutInterRNCIur.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranCellFDD
  7. Valid for circuit switched and packet switched traffic.

4.10.5 Relocation preparation for outgoing inter-RNC hard handovers switching in the CN

4.10.5.0 Introduction

The three measurement types defined in the subclause 4.10.5 for relocation preparation for outgoing inter-RNC hard handovers switching in the CN are subject to the "2 out of 3 approach".

4.10.5.1 Attempted relocation preparation for outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides the number of attempted relocation preparation for outgoing inter-RNC hard handovers switching in the CN.
  2. CC.
  3. Transmission of a RANAP message RELOCATION REQUIRED from the source RNC to the CN (Source side), indicating an attempted relocation preparation of a outgoing inter-RNC hard handover switching in the CN (see TS 25.413 [5]).
  4. A single integer value.
  5. HHO.AttRelocPrepOutInterRNCCN.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.5.2 Successful relocation preparation for outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides the number of successful relocation for outgoing inter-RNC hard handovers switching in the CN.
  2. CC.
  3. Receipt of a RANAP message RELOCATION COMMAND sent from the CN (Source side) to the source RNC, indicating a successful relocation preparation of a outgoing inter-RNC hard handover switching in the CN (see TS 25.413 [5]).
  4. A single integer value.
  5. HHO.SuccAttRelocPrepOutInterRNCCN.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.5.3 Failed relocation preparation for outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides number of failed relocation for outgoing inter-RNC hard handovers switching in the CN per cause.
  2. CC.
  3. Receipt of a RANAP message RELOCATION PREPARATION FAILURE sent from the CN (Source side) to the source RNC, indicating a failed relocation preparation for outgoing inter-RNC hard handover switching in the CN. Failure causes are defined within TS 25.413 [5]. The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.
  4. 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.
  5. The measurement name has the form HHO.FailRelocPrepOutInterRNCCN.Cause
    where Cause identifies the name of the failure cause.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.6 Outgoing inter-RNC hard handovers switching in the CN

4.10.6.0 Introduction

The three measurement types defined in the subclause 4.10.6 for outgoing inter-RNC hard handovers switching in the CN are subject to the "2 out of 3 approach".

4.10.6.1 Attempted outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides the number of attempted outgoing inter-RNC hard handovers switching in the CN related to UEs.
  2. CC.
  3. Transmission of a RRC message PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, or TRANSPORT CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of an inter-RNC hard handover switching in the CN (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.AttOutInterRNCCN.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.6.2 Successful outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides the number of successful outgoing inter-RNC hard handovers switching in the CN related to UEs.
  2. CC.
  3. Receipt of a RANAP message Iu RELEASE COMMAND sent from the CN (Source side) to the source RNC, indicating a successful inter-RNC hard handover switching in the CN (see TS 25.413 [5]).
  4. A single integer value.
  5. HHO.SuccOutInterRNCCN.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.6.3 Failed outgoing inter-RNC hard handovers switching in the CN

  1. This measurement provides the number of failed outgoing inter-RNC hard handovers switching in the CN related to UEs.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE sent from the UE to the source RNC, indicating a failed inter-RNC hard handover switching in the CN. Failure causes are defined within TS 25.331 [4].

    Each expected RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  4. 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.
  5. The measurement name has the form HHO.FailOutInterRNCCN.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.

4.10.7 Outgoing hard handovers per neighbour cell relation

4.10.7.0 Introduction

The three measurement types defined in the subclause 4.10.7 for outgoing hard handovers per neighbour cell relation are subject to the "2 out of 3 approach".

4.10.7.1 Attempted outgoing hard handovers per neighbour cell relation

  1. This measurement provides the number of attempted outgoing hard handovers per neighbour cell relation.
  2. CC.
  3. Transmission of a RRC message PHYSICAL CHANNEL RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, or TRANSPORT CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of an outgoing hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.AttOut.
  6. UtranRelation.
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.
  9. This measurement is mainly dedicated to Network Operator Maintenance and Vendor Performance Modelling Communities.

4.10.7.2 Successful outgoing hard handovers per neighbour cell relation

  1. This measurement provides the number of successful outgoing hard handovers per neighbour cell relation.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing hard handover (see TS 25.331 [4]).
  4. A single integer value.
  5. HHO.SuccOut.
  6. UtranRelation.
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.
  9. This measurement is mainly dedicated to Network Operator Maintenance and Vendor Performance Modelling Communities.

4.10.7.3 Failed outgoing hard handovers per neighbour cell relation

  1. This measurement provides the number of failed outgoing hard handovers per neighbour cell relation per cause.
  2. CC.
  3. Receipt of a RRC message PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE sent from the UE to the source RNC, indicating a failed outgoing hard handover. Failure causes are defined within TS 25.331 [4].

    Each expected RRC message PHYSICAL CHANNEL RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, PHYSICAL CHANNEL RECONFIGURATION FAILURE, RADIO BEARER SETUP FAILURE, RADIO BEARER RECONFIGURATION FAILURE, RADIO BEARER RELEASE FAILURE, or TRANSPORT CHANNEL RECONFIGURATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    The sum of all supported per cause measurements shall equal the total number of failed events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  4. 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.
  5. The measurement name has the form HHO.FailOut.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranRelation.
  7. Valid for circuit switched and packet switched traffic.
  8. UMTS.
  9. This measurement is mainly dedicated to Network Operator Maintenance and Vendor Performance Modelling Communities.