4.11 Relocation

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

4.11.1 Relocations for CS domain

4.11.1.1 Relocation preparations with UE involved for CS domain

4.11.1.0 Introduction

The three measurement types defined in the subclause 4.11.1.1.n for relocation preparations with UE involved for CS domain are subject to the "2 out of 3 approach".

4.11.1.1.1 Attempted relocation preparations with UE involved for CS domain
  1. This measurement provides the number of attempted relocation preparations with UE involved for CS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUIRED from the source RNC to the CS CN (Source side) with Relocation Type set to "UE involved in relocation of SRNS", indicating an attempted relocation preparation with UE involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttPrepUEInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.1.2 Successful relocation preparations with UE involved for CS domain
  1. This measurement provides the number of successful relocation preparations with UE involved for CS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION COMMAND sent from the CS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE involved in relocation of SRNS", indicating a successful relocation preparation with UE involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccPrepUEInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.1.3 Failed relocation preparations with UE involved for CS domain
  1. This measurement provides the number of failed relocation preparations with UE involved for CS domain per cause.
  2. CC
  3. Receipt of a RANAP message RELOCATION PREPARATION FAILURE sent from the CS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE involved in relocation of SRNS", indicating a failed relocation preparation with UE involved for CS domain. Failure causes are defined within TS 25.413 [5].

    Each expected RANAP message RELOCATION COMMAND or RELOCATION PREPARATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in 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 RELOC.FailPrepUEInvolCS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS

4.11.1.2 Relocation preparations with UE not involved for CS domain

4.11.1.2.0 Introduction

The three measurement types defined in the subclause 4.11.1.2.n for relocation preparations with UE not involved for CS domain are subject to the "2 out of 3 approach".

4.11.1.2.1 Attempted relocation preparations with UE not involved for CS domain
  1. This measurement provides the number of attempted relocation preparations with UE not involved for CS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUIRED from the source RNC to the CS CN (Source side) with Relocation Type set to "UE not involved in relocation of SRNS", indicating an attempted relocation preparation with UE not involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttPrepUENotInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.2.2 Successful relocation preparations with UE not involved for CS domain
  1. This measurement provides the number of successful relocation preparations with UE not involved for CS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION COMMAND sent from the CS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a successful relocation preparation with UE not involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccPrepUENotInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.2.3 Failed relocation preparations with UE not involved for CS domain
  1. This measurement provides the number of failed relocation preparations with UE not involved for CS domain per cause.
  2. CC
  3. Receipt of a RANAP message RELOCATION PREPARATION FAILURE sent from the CS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a failed relocation preparation with UE not involved for CS domain. Failure causes are defined within TS 25.413 [5].

    Each expected RANAP message RELOCATION COMMAND or RELOCATION PREPARATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in 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 RELOC.FailPrepUENotInvolCS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS

4.11.1.3 Relocation resource allocations with UE involved for CS domain

4.11.1.3.0 Introduction

The three measurement types defined in the subclause 4.11.1.3.n for relocation resource allocations with UE involved for CS domain are subject to the "2 out of 3 approach".

4.11.1.3.1 Attempted relocations resource allocations with UE involved for CS domain
  1. This measurement provides the number of attempted relocation resource allocations with UE involved for CS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION REQUEST sent from the CS CN (Target side) to the target RNC with Relocation Type set to "UE involved in relocation of SRNS", indicating an attempted relocation resource allocation with UE involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttResAllocUEInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.3.2 Successful relocation resource allocations with UE involved for CS domain
  1. This measurement provides the number of successful relocation resource allocations with UE involved for CS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUEST ACKNOWLEDGE from the target RNC to the CS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE involved in relocation of SRNS", indicating a successful relocation resource allocation with UE involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccResAllocUEInvolCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.3.3 Failed relocation resource allocations with UE involved for CS domain
  1. This measurement provides the number of failed relocation resource allocations with UE involved for CS domain per cause.
  2. CC
  3. Transmission of a RANAP message RELOCATION FAILURE from the target RNC to the CS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE involved in relocation of SRNS", indicating a failed relocation resource allocation with UE involved for CS domain. 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 RELOC.FailResAllocUEInvolCS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS

4.11.1.4 Relocation resource allocations with UE not involved for CS domain

4.11.1.4.0 Introduction

The three measurement types defined in the subclause 4.11.1.4.n for relocation resource allocations with UE not involved for CS domain are subject to the "2 out of 3 approach".

4.11.1.4.1 Attempted relocations resource allocations with UE not involved for CS domain
  1. This measurement provides the number of attempted relocation resource allocations with UE not involved for CS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION REQUEST sent from the CS CN (Target side) to the target RNC with Relocation Type set to "UE not involved in relocation of SRNS", indicating an attempted relocation resource allocation with UE not involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttResAllocUENotInvolCS
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.4.2 Successful relocation resource allocations with UE not involved for CS domain
  1. This measurement provides the number of successful relocation resource allocations with UE not involved for CS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUEST ACKNOWLEDGE from the target RNC to the CS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a successful relocation resource allocation with UE not involved for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccResAllocUENotInvolCS
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS
4.11.1.4.3 Failed relocation resource allocations with UE not involved for CS domain
  1. This measurement provides the number of failed relocation resource allocations with UE not involved for CS domain per cause.
  2. CC
  3. Transmission of a RANAP message RELOCATION FAILURE from the target RNC to the CS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a failed relocation resource allocation with UE not involved for CS domain. 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 RELOC.FailResAllocUENotInvolCS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS

4.11.1.5 Relocations for CS domain

4.11.1.5.1 Successful relocations for CS domain
  1. This measurement provides the number of successful relocations for CS domain (‘UE involved’ and ‘UE not involved’ Relocations).
  2. CC
  3. Receipt of a RANAP message Iu RELEASE COMMAND sent from the CS CN (Source side) to the source RNC in response to a RELOCATION REQUIRED message, indicating a successful relocation for CS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccCS.
  6. RncFunction
  7. Valid for circuit switched traffic
  8. UMTS

4.11.2 Relocations for PS domain

4.11.2.1 Relocation preparations with UE involved for PS domain

4.11.2.1.0 Introduction

The three measurement types defined in the subclause 4.11.2.1.n for relocation preparations with UE involved for PS domain are subject to the "2 out of 3 approach".

4.11.2.1.1 Attempted relocation preparations with UE involved for PS domain
  1. This measurement provides the number of attempted relocation preparations with UE involved for PS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUIRED from the source RNC to the PS CN (Source side) with Relocation Type set to "UE involved in relocation of SRNS", indicating an attempted relocation preparation with UE involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttPrepUEInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.1.2 Successful relocation preparations with UE involved for PS domain
  1. This measurement provides the number of successful relocation preparations with UE involved for PS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION COMMAND sent from the PS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE involved in relocation of SRNS", indicating a successful relocation preparation with UE involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccPrepUEInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.1.3 Failed relocation preparations with UE involved for PS domain
  1. This measurement provides the number of failed relocation preparations with UE involved for PS domain per cause.
  2. CC
  3. Receipt of a RANAP message RELOCATION PREPARATION FAILURE sent from the PS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE involved in relocation of SRNS", indicating a failed relocation preparation with UE involved for PS domain. Failure causes are defined within TS 25.413 [5].

    Each expected RANAP message RELOCATION COMMAND or RELOCATION PREPARATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in 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 RELOC.FailPrepUEInvolPS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS

4.11.2.2 Relocation preparations with UE not involved for PS domain

4.11.2.2.0 Introduction

The three measurement types defined in the subclause 4.11.2.2.n for relocation preparations with UE not involved for PS domain are subject to the "2 out of 3 approach".

4.11.2.2.1 Attempted relocation preparations with UE not involved for PS domain
  1. This measurement provides the number of attempted relocation preparations with UE not involved for PS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUIRED from the source RNC to the PS CN (Source side) with Relocation Type set to "UE not involved in relocation of SRNS", indicating an attempted relocation preparation with UE not involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttPrepUENotInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.2.2 Successful relocation preparations with UE not involved for PS domain
  1. This measurement provides the number of successful relocation preparations with UE not involved for PS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION COMMAND sent from the PS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a successful relocation preparation with UE not involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccPrepUENotInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.2.3 Failed relocation preparations with UE not involved for PS domain
  1. This measurement provides the number of failed relocation preparations with UE not involved for PS domain per cause.
  2. CC
  3. Receipt of a RANAP message RELOCATION PREPARATION FAILURE sent from the PS CN (Source side) to the source RNC, in response to a RELOCATION REQUIRED message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a failed relocation preparation with UE not involved for PS domain. Failure causes are defined within TS 25.413 [5].

    Each expected RANAP message RELOCATION COMMAND or RELOCATION PREPARATION FAILURE not received by the source RNC is added to the measurement cause ‘No Reply’ (not specified in 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 RELOC.FailPrepUENotInvolPS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS

4.11.2.3 Relocation resource allocations with UE involved for PS domain

4.11.2.3.0 Introduction

The three measurement types defined in the subclause 4.11.2.3.n for relocation resource allocations with UE involved for PS domain are subject to the "2 out of 3 approach".

4.11.2.3.1 Attempted relocations resource allocations with UE involved for PS domain
  1. This measurement provides the number of attempted relocation resource allocations with UE involved for PS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION REQUEST sent from the PS CN (Target side) to the target RNC with Relocation Type set to "UE involved in relocation of SRNS", indicating an attempted relocation resource allocation with UE involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttResAllocUEInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.3.2 Successful relocation resource allocations with UE involved for PS domain
  1. This measurement provides the number of successful relocation resource allocations with UE involved for PS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUEST ACKNOWLEDGE from the target RNC to the PS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE involved in relocation of SRNS", indicating a successful relocation resource allocation with UE involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccResAllocUEInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.3.3 Failed relocation resource allocations with UE involved for PS domain
  1. This measurement provides the number of failed relocation resource allocations with UE involved for PS domain per cause.
  2. CC
  3. Transmission of a RANAP message RELOCATION FAILURE from the target RNC to the PS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE involved in relocation of SRNS", indicating a failed relocation resource allocation with UE involved for PS domain. 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 RELOC.FailResAllocUEInvolPS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS

4.11.2.4 Relocation resource allocations with UE not involved for PS domain

4.11.2.4.0 Introduction

The three measurement types defined in the subclause 4.11.2.4.n for relocation resource allocations with UE not involved for PS domain are subject to the "2 out of 3 approach".

4.11.2.4.1 Attempted relocations resource allocations with UE not involved for PS domain
  1. This measurement provides the number of attempted relocation resource allocations with UE not involved for PS domain.
  2. CC
  3. Receipt of a RANAP message RELOCATION REQUEST sent from the PS CN (Target side) to the target RNC with Relocation Type set to "UE not involved in relocation of SRNS", indicating an attempted relocation resource allocation with UE not involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.AttResAllocUENotInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.4.2 Successful relocation resource allocations with UE not involved for PS domain
  1. This measurement provides the number of successful relocation resource allocations with UE not involved for PS domain.
  2. CC
  3. Transmission of a RANAP message RELOCATION REQUEST ACKNOWLEDGE from the target RNC to the PS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a successful relocation resource allocation with UE not involved for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccResAllocUENotInvolPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS
4.11.2.4.3 Failed relocation resource allocations with UE not involved for PS domain
  1. This measurement provides the number of failed relocation resource allocations with UE not involved for PS domain per cause.
  2. CC
  3. Transmission of a RANAP message RELOCATION FAILURE from the target RNC to the PS CN (Target side), in response to a RELOCATION REQUEST message with Relocation Type set to "UE not involved in relocation of SRNS", indicating a failed relocation resource allocation with UE not involved for PS domain. 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 RELOC.FailResAllocUENotInvolPS.Cause
    where Cause identifies the failure cause.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS

4.11.2.5 Relocations for PS domain

4.11.2.5.1 Successful relocations for PS domain
  1. This measurement provides the number of successful relocations for PS domain (‘UE involved’ and ‘UE not involved’ Relocations).
  2. CC
  3. Receipt of a RANAP message Iu RELEASE COMMAND sent from the PS CN (Source side) to the source RNC in response to a RELOCATION REQUIRED message, indicating a successful relocation for PS domain (see TS 25.413 [5]).
  4. A single integer value
  5. RELOC.SuccPS.
  6. RncFunction
  7. Valid for packet switched traffic.
  8. UMTS