4.34 HSUPA related measurements

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

Performance Measurement definitions in this subclause are based on TS 25.331 [4] and TS 25.433 [7].

The following procedures are of interest for this purpose:

NBAP: RADIO LINK SETUP REQUEST

NBAP: RADIO LINK RECONFIGURATION PREPARE

NBAP: RADIO LINK RECONFIGURATION REQUEST

NBAP: RADIO LINK ADDITION REQUEST

NBAP: RADIO LINK SETUP RESPONSE

NBAP: RADIO LINK RECONFIGURATION READY

NBAP: RADIO LINK RECONFIGURATION RESPONSE

NBAP: RADIO LINK ADDITION RESPONSE

NBAP: RADIO LINK SETUP FAILURE

NBAP: RADIO LINK RECONFIGURATION FAILURE

NBAP: RADIO LINK RECONFIGURATION FAILURE

NBAP: RADIO LINK ADDITION FAILURE

RRC: RADIO BEARER SETUP

RRC: RADIO BEARER RECONFIGURATION

RRC: RADIO BEARER SETUP COMPLETE

RRC: RADIO BEARER RECONFIGURATION COMPLETE

RRC: RADIO BEARER SETUP FAILURE

RRC: RADIO BEARER RECONFIGURATION FAILURE

Figure : Radio Link Setup procedure, Successful Operation

Figure: Radio Link Setup procedure, Unsuccessful Operation

Figure: Radio Link Reconfiguration Preparation procedure, Successful Operation

Figure: Radio Link Reconfiguration Preparation procedure, Unsuccessful Operation

Figure: Radio Link Addition procedure, Successful Operation

Figure: Radio Link Addition procedure: Unsuccessful Operation

Figure: Radio Bearer Establishment, normal case

Figure: Radio Bearer Establishment, failure case

Figure: Radio bearer reconfiguration, normal flow

Figure: Radio bearer reconfiguration, failure case

4.34.1 HSUPA setup

4.34.1.1 Mac-d setup for HSUPA

4.34.1.1.0 Introduction

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

4.34.1.1.1 Attempted Mac-d setups for HSUPA
  1. This measurement provides the number of attempted Mac-d setups for HSUPA.
  2. CC

For FDD:

On transmission by the RNC of a NBAP message RADIO LINK SETUP REQUEST with the “E-DCH FDD Information” IE; Or on transmission by the RNC of a NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on transmission by the RNC of a NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on transmission by the RNC of a NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH FDD Information” IE. See TS 25.433 [7].

For TDD:

On transmission by the RNC of a NBAP message RADIO LINK SETUP REQUEST with the “E-DCH MAC-d Flows Information TDD” IE; Or on transmission by the RNC of a NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” IE; Or on transmission by the RNC of a NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” IE; Or on transmission by the RNC of a NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH MAC-d Flows Information TDD” IE. See TS 25.433 [7].

  1. A single integer value
  2. HSUPA.AttMacdSetup
  3. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  4. Valid for packet switched traffic
  5. UMTS
4.34.1.1.2 Successful Mac-d setups for HSUPA
  1. This measurement provides the number of successful Mac-d setups for HSUPA.
  2. CC

For FDD:

On receipt by the RNC of a NBAP message RADIO LINK SETUP RESPONSE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH FDD Information” IE; Or on receipt by the RNC of a NBAP message RADIO LINK RECONFIGURATION READY, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on receipt by the RNC of NBAP message RADIO LINK RECONFIGURATION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on receipt by the RNC of NBAP message RADIO LINK ADDITION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH FDD Information” IE. See TS 25.433 [7].

For TDD:

On receipt by the RNC of a NBAP message RADIO LINK SETUP RESPONSE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH MAC-d Flows Information TDD” IE; Or on receipt by the RNC of a NBAP message RADIO LINK RECONFIGURATION READY, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” IE; Or on receipt by the RNC of NBAP message RADIO LINK RECONFIGURATION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” IE; Or on receipt by the RNC of NBAP message RADIO LINK ADDITION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH MAC-d Flows Information TDD” IE. See TS 25.433 [7].

  1. A single integer value
  2. HSUPA.SuccMacdSetup
  3. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  4. Valid for packet switched traffic
  5. UMTS
4.34.1.1.3 Failed Mac-d setups for HSUPA
  1. This measurement provides the number of failed Mac-d setups for HSUPA. The measurement is split into subcounters per cause.
  2. CC

For FDD:

On receipt by the RNC of a NBAP message RADIO LINK SETUP FAILURE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH FDD Information” IE; Or on receipt by the RNC of a NBAP message RADIO LINK RECONFIGURATION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on receipt by the RNC of NBAP message RADIO LINK RECONFIGURATION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or on receipt by the RNC of NBAP message RADIO LINK ADDITION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH FDD Information” IE.

Each expected NBAP message RADIO LINK SETUP RESPONSE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH FDD Information” IE; Or RADIO LINK RECONFIGURATION READY, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or RADIO LINK RECONFIGURATION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” or “E-DCH FDD Information” IE; Or RADIO LINK ADDITION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH FDD Information” IE not received by the RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

For TDD:

On receipt by the RNC of a NBAP message RADIO LINK SETUP FAILURE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH MAC-d Flows Information TDD” IE; Or on receipt by the RNC of a NBAP message RADIO LINK RECONFIGURATION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” IE; Or on receipt by the RNC of NBAP message RADIO LINK RECONFIGURATION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” IE; Or on receipt by the RNC of NBAP message RADIO LINK ADDITION FAILURE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH MAC-d Flows Information TDD” IE.

Each expected NBAP message RADIO LINK SETUP RESPONSE, corresponding to transmission of the NBAP message RADIO LINK SETUP REQUEST with the “E-DCH MAC-d Flows Information TDD” IE; Or RADIO LINK RECONFIGURATION READY, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION PREPARE with the “E-DCH MAC-d Flows To Add” IE; Or RADIO LINK RECONFIGURATION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK RECONFIGURATION REQUEST with the “E-DCH MAC-d Flows To Add” IE; Or RADIO LINK ADDITION RESPONSE, corresponding to the transmission of the NBAP message RADIO LINK ADDITION REQUEST with the “E-DCH MAC-d Flows Information TDD” IE not received by the RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

Each failed Mac-d setup for HSUPA is added to the relevant measurement according to the failure cause. Possible failure causes are included in TS 25.433 [7]. The sum of all supported per cause measurements shall equal the total number of failed Mac-d setups for HSUPA. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  1. 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.
  2. HSUPA.FailMacdSetup.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  3. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  4. Valid for packet switched traffic
  5. UMTS

4.34.1.2 RB setup for HSUPA

4.34.1.2.0 Introduction

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

4.34.1.2.1 Attempted RB setups for HSUPA
  1. This measurement provides the number of attempted radio bearer setups for HSUPA.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER SETUP with the “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to setup”; Or on transmission by the RNC of a RRC message RADIO BEARER RECONFIGURATION with “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to reconfigure” if the previous “Uplink transport channel type” of this RB is not the “E-DCH”. See TS 25.331 [4].
  4. A single integer value
  5. HSUPA.AttRBSetup
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.1.2.2 Successful RB setups for HSUPA
  1. This measurement provides the number of successful radio bearer setups for HSUPA.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER SETUP COMPLETE, corresponding to the transmission of the RRC message RADIO BEARER SETUP with the “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to setup”; Or on receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION COMPLETE, corresponding to the transmission of the RRC message RADIO BEARER RECONFIGURATION with “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to reconfigure” if the previous “Uplink transport channel type” of this RB is not the “E-DCH”. See TS 25.331 [4].
  4. A single integer value
  5. HSUPA.SuccRBSetup
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.1.2.3 Failed RB setups for HSUPA
  1. This measurement provides the number of failed radio bearer setups for HSUPA. The measurement is split into subcounters per cause.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER SETUP FAILURE, corresponding to the transmission of the RRC message RADIO BEARER SETUP with the “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to setup”; Or on receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION FAILURE, corresponding to the transmission of the RRC message RADIO BEARER RECONFIGURATION with “Uplink transport channel type” set to “E-DCH” or in the “RB mapping info” IE of the “RB information to reconfigure” if the previous “Uplink transport channel type” of this RB is not the “E-DCH”.

    Each expected RRC message RADIO BEARER SETUP COMPLETE, corresponding to the transmission of the RRC message RADIO BEARER SETUP with the “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to setup”; Or RADIO BEARER RECONFIGURATION COMPLETE, corresponding to the transmission of the RRC message RADIO BEARER RECONFIGURATION with “Uplink transport channel type” set to “E-DCH” in the “RB mapping info” IE of the “RB information to reconfigure” if the previous “Uplink transport channel type” of this RB is not the “E-DCH” not received by the RNC is added to the measurement cause ‘No Reply’ (not specified in TS 25.331 [4]).

    Each failed RB setup for HSUPA is added to the relevant measurement according to the failure cause. Possible failure causes are included in TS 25.331 [4]. The sum of all supported per cause measurements shall equal the total number of failed RB setups for HSUPA. 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 plus a possible sum value identified by the .sum suffix.
  5. HSUPA.FailRBSetup.Cause
    where Cause identifies the failure cause.
    The cause ‘No Reply’ is identified by the .NoReply suffix.
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS

4.34.2 Active set related to HSUPA

4.34.2.1 Radio link additions to the E-DCH active set (UE side)

4.34.2.1.0 Introduction

The three measurement types defined for the radio link additions to the E-DCH active set (UE side) are subject to the "2 out of 3 approach".

4.34.2.1.1 Attempted radio link additions to the E-DCH active set (UE side)
  1. This measurement provides the number of attempted radio link additions to the E-DCH active set (UE side). This measurement shall be increased for each attempted radio link addition (UE side). This measurement is only valid for FDD mode.
  2. CC
  3. On transmission by the serving RNC of a RRC message ACTIVE SET UPDATE from the RNC to the UE, IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH information" to indicate which radio link to add to the E-DCH active set. Within an ACTIVE SET UPDATE message more than one radio link can be added. Each existing radio link addition information element shall be considered separately (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttEdchAddUESide
  6. UtranCellFDD
  7. Valid for packet switched traffic
  8. UMTS
4.34.2.1.2 Successful radio link additions to the E-DCH active set (UE side)
  1. This measurement provides the number of successful radio link additions to the E-DCH active set (UE side). This measurement shall be increased for each successful radio link addition (UE side). This measurement is only valid for FDD mode.
  2. CC
  3. On receipt by the serving RNC of a RRC message ACTIVE SET UPDATE COMPLETE from the UE to the RNC, in response to an ACTIVE SET UPDATE message with one or more existing IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH information" to indicate which radio link to add to the E-DCH active set. One ACTIVE SET UPDATE COMPLETE message can be related to more than one added radio link. Each successful added radio link shall be considered separately (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccEdchAddUESide
  6. UtranCellFDD
  7. Valid for packet switched traffic
  8. UMTS
4.34.2.1.3 Failed radio link additions to the E-DCH active set (UE side)
  1. This measurement provides the number of failed radio link additions to the E-DCH active set (UE side) during E-DCH active set update procedure (UE side) for each cell per cause. For each failure cause a separate subcounter is defined. Every failed radio link addition (UE side) shall be considered separately. This measurement is only valid for FDD mode.
  2. CC
  3. Receipt of an ACTIVE SET UPDATE FAILURE message (RRC) sent by UE to the RNC in response to an ACTIVE SET UPDATE message with one or more existing IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH information" to indicate which radio link to add to the E-DCH active set or an expected ACTIVE SET UPDATE COMPLETE message not received by the RNC. Each message can be related to more than one radio link.

– Each failed attempt to add a radio link to the E-DCH active set shall be considered separately and added to the relevant per cause measurement. Failure causes are defined within TS 25.331 [4].

– Each expected ACTIVE SET UPDATE COMPLETE message not received by the 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 failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

  1. 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.
  2. HSUPA.FailEdchAddUESide.Cause
  3. UtranCellFDD
  4. Valid for packet switched traffic
  5. UMTS

4.34.2.2 Radio link deletions to the E-DCH active set (UE side)

4.34.2.2.1 Attempted radio link deletions to the E-DCH active set (UE side)
  1. This measurement provides the number of attempted radio link deletions to the E-DCH active set (UE side). This measurement shall be increased for each attempted radio link deletion (UE side). This measurement is only valid for FDD mode.
  2. CC
  3. On transmission by the serving RNC of a RRC message ACTIVE SET UPDATE from the RNC to the UE, IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH release indicator" to indicate which radio link to remove from the E-DCH active set. Within an ACTIVE SET UPDATE message more than one radio link can be deleted. Each existing radio link deletion information element shall be considered separately (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttEdchDelUESide
  6. UtranCellFDD
  7. Valid for packet switched traffic
  8. UMTS
4.34.2.2.2 Successful radio link deletions to the E-DCH active set (UE side)
  1. This measurement provides the number of successful radio link deletions to the E-DCH active set (UE side). This measurement shall be increased for each successful radio link deletion (UE side). This measurement is only valid for FDD mode.
  2. CC
  3. On receipt by the serving RNC of a RRC message ACTIVE SET UPDATE COMPLETE from the UE to the RNC, in response to an ACTIVE SET UPDATE message with one or more existing IE "E-DCH reconfiguration information": IE "Primary CPICH info" used for the reference ID along with the IE "E-HICH release indicator" to indicate which radio link to remove from the E-DCH active set. One ACTIVE SET UPDATE COMPLETE message can be related to more than one deleted radio link. Each successful deleted radio link shall be considered separately (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccEdchDelUESide
  6. UtranCellFDD
  7. Valid for packet switched traffic
  8. UMTS

4.34.3 Serving E-DCH cell change

4.34.3.1 Outgoing serving E-DCH cell change

4.34.3.1.1 Attempted outgoing serving E-DCH cell change
  1. This measurement provides the number of attempted outgoing serving E-DCH cell change.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, TRANSPORT CHANNEL RECONFIGURATION, or PHYSICAL CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of outgoing serving E-DCH cell change (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttOutCellChange
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.3.1.2 Successful outgoing serving E-DCH cell change
  1. This measurement provides the number of successful outgoing serving E-DCH cell change.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, or PHYSICAL CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing serving E-DCH cell change (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccOutCellChange
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS

4.34.3.2 Outgoing serving E-DCH cell change per neighbour cell relation

4.34.3.2.1 Attempted outgoing serving E-DCH cell change per neighbour cell relation
  1. This measurement provides the number of attempted outgoing serving E-DCH cell change per neighbour cell relation.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER SETUP, RADIO BEARER RECONFIGURATION, RADIO BEARER RELEASE, TRANSPORT CHANNEL RECONFIGURATION, or PHYSICAL CHANNEL RECONFIGURATION from the source RNC to the UE, indicating the attempt of outgoing serving E-DCH cell change (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttOut
  6. UtranRelation
  7. Valid for packet switched traffic
  8. UMTS
4.34.3.2.2 Successful outgoing serving E-DCH cell change per neighbour cell relation
  1. This measurement provides the number of successful outgoing serving E-DCH cell change per neighbour cell relation.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER SETUP COMPLETE, RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER RELEASE COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, or PHYSICAL CHANNEL RECONFIGURATION COMPLETE sent from the UE to the source RNC, indicating a successful outgoing serving E-DCH cell change (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccOut
  6. UtranRelation
  7. Valid for packet switched traffic
  8. UMTS

4.34.4 Mean number of HSUPA users of a serving E-DCH cell

  1. This measurement provides the mean number of simultaneous HSUPA users in a serving E-DCH cell.
  2. SI.
  3. This measurement is obtained by sampling at a pre-defined interval the number of simultaneous users in a serving E-DCH cell and then taking the arithmetic mean.
  4. A single real value.
  5. HSUPA.MeanNbrUser
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.

4.34.5 Measurements related to channel switches between RACH/DCH and E-DCH

4.34.5.1 Measurements related to channel switches from RACH/DCH to E-DCH

4.34.5.1.1 Attempted channel switches from RACH to E-DCH
  1. This measurement provides the number of attempted channel switches from RACH to E-DCH in the serving E-DCH cell.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RELEASE, CELL UPDATE CONFIRM, or TRANSPORT CHANNEL RECONFIGURATION to UE, with the condition that channel switches only from RACH to E-DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttRachToEdch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.1.2 Successful channel switches from RACH to E-DCH
  1. This measurement provides the number of successful channel switches from RACH to E-DCH in the serving E-DCH cell.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETEP, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE from UE, with the condition that channel switches only from RACH to E-DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccRachToEdch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.1.3 Attempted channel switches from DCH to E-DCH
  1. This measurement provides the number of attempted channel switches from DCH to E-DCH in the serving E-DCH cell.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER RECONFIGURATION, RADIO BEARER SETUPP, RADIO BEARER RELEASE, CELL UPDATE CONFIRM, or TRANSPORT CHANNEL RECONFIGURATION to UE, with the condition that channel switches from DCH to E-DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttDchToEdch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.1.4 Successful channel switches from DCH to E-DCH
  1. This measurement provides the number of successful channel switches from DCH to E-DCH in the serving E-DCH cell.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE from UE, with the condition that channel switches from DCH to E-DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccDchToEdch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS

4.34.5.2 Measurements related to channel switches from E-DCH to RACH/DCH

4.34.5.2.1 Attempted channel switches from E-DCH to RACH
  1. This measurement provides the number of attempted channel switches from E-DCH to RACH in the serving E-DCH cell.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER RECONFIGURATION, RADIO BEARER SETUP, RADIO BEARER RELEASE, CELL UPDATE CONFIRM, or TRANSPORT CHANNEL RECONFIGURATION to UE, with the condition that channel switches only from E-DCH to RACH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttEdchToRach
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.2.2 Successful channel switches from E-DCH to RACH
  1. This measurement provides the number of successful channel switches from E-DCH to RACH in the serving E-DCH cell.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE from UE, with the condition that channel switches only from E-DCH to RACH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccEdchToRach
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.2.3 Attempted channel switches from E-DCH to DCH
  1. This measurement provides the number of attempted channel switches from E-DCH to DCH in the serving E-DCH cell.
  2. CC
  3. On transmission by the RNC of a RRC message RADIO BEARER RECONFIGURATION, RADIO BEARER SETUPP, RADIO BEARER RELEASE, CELL UPDATE CONFIRM, or TRANSPORT CHANNEL RECONFIGURATION to UE, with the condition that channel switches from E-DCH to DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.AttEdchToDch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS
4.34.5.2.4 Successful channel switches from E-DCH to DCH
  1. This measurement provides the number of successful channel switches from E-DCH to DCH in the serving E-DCH cell.
  2. CC
  3. On receipt by the RNC of a RRC message RADIO BEARER RECONFIGURATION COMPLETE, RADIO BEARER SETUP COMPLETE, RADIO BEARER RELEASE COMPLETE, or TRANSPORT CHANNEL RECONFIGURATION COMPLETE from UE, with the condition that channel switches from E-DCH to DCH (see TS 25.331 [4]).
  4. A single integer value
  5. HSUPA.SuccEdchToDch
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic
  8. UMTS

4.34.6 Measurements related to MAC-e feedback decoding

4.34.6.1 Number of received MAC-e PDUs

  1. This measurement provides the number of received MAC-e PDUs including acknowledged and unacknowledged PDUs during the period of measurement, detected in MAC-e layer in the serving E-DCH cell.
  2. CC.
  3. On receipt by the NodeB of a PDU of MAC-e from UE.
  4. A single integer value.
  5. HSUPA.NbrMacePdu
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.

4.34.6.2 Number of received acknowledged MAC-e PDUs

  1. This measurement provides the number of successfully received MAC-e PDUs that has been acknowledged to the UE during the period of measurement, detected in MAC-e layer in the serving E-DCH cell.
  2. CC.
  3. On transmission by the NodeB of a ACK on E-HICH from NodeB to UE indicating a correct receiption a MAC-e PDU.
  4. A single integer value.
  5. HSUPA.NbrAckdMacePdu
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.

4.34.7 Number of octets of acknowledged MAC-e PDUs

  1. This measurement provides the number of octets of uplink acknowledged MAC-e PDUs in the E-DCH cell.
  2. CC.
  3. On receipt by the NodeB of an acknowledged PDU on the MAC-e layer. The number of octets of MAC-e layer in one E-DCH cell is calculated by sum of size of each MAC-e PDU header including MAC-e PDU header.
  4. A single integer value.
  5. HSUPA.NbrAckdMaceOcts
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.

4.34.8 HSUPA Release measurements

4.34.8.1 Normal HSUPA Release

4.34.8.1.1 RNC initiated release due to user inactivity
  1. This measurement provides the number of times when the UE is removed from E-DCH transport channel due to user inactivity in the serving E-DCH cell.
  2. CC.
  3. On transmission by the RNC of the RRC: RADIO BEARER RECONFIGURATION or RRC: RADIO BEARER RELEASE or RRC CONNECTION RELEASE message that indicates an E-DCH release when RNC detected UE has no data to send in a predefined interval (equals to the RANAP cause 16 user inactivity).
  4. A single integer value.
  5. HSUPA.SuccEdchReleaseUserInact
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.
4.34.8.1.2 RNC initiated release due to switch to DCH/RACH

The measurement definition is in section 4.34.5.2.

4.34.8.1.3 RNC initiated release due to serving E-DCH cell change

The measurement definition is in section 4.34.3.

4.34.8.1.4 CN initiated release
  1. This measurement provides the number of times when the UE is removed from E-DCH transport channel due to a release initiated by the Core Network in the serving E-DCH cell.
  2. CC.
  3. On reception by the RNC of RANAP RAB ASSIGNMENT REQUEST or RANAP IU RELEASE COMMAND that results an E-DCH release. The release of E-DCH is executed by the transmission of the RRC RADIO BEARER RECONFIGURATION or RRC RADIO BEARER RELEASE or RRC CONNECTION RELEASE message.
  4. A single integer value.
  5. HSUPA.SuccCnInitEdchRelease
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.

4.34.8.2 Abnormal RB releases for E-DCH

  1. This measurement provides the number of times when the UE is removed from E-DCH transport channel, and trigger reason is not a normal release, e.g. user inactivity, switch to DCH/RACH, serving E-DCH cell changes or CN initiated release.
  2. CC.
  3. On receipt by the RNC of the RRC: RADIO BEARER RECONFIGURATION COMPLETE corresponding to the transmission of the RRC message RADIO BEARER RECONFIGURATION, or RRC: RADIO BEARER RELEASE COMPLETE corresponding to the transmission of the RRC message RADIO BEARER RELEASE. Or when the UE does not respond to RRC: RADIO BEARER RECONFIGURATION or RRC: RADIO BEARER RELEASE message, and the E-DCH release does not categorize as a normal release, e.g. user inactivity, switch to DCH/RACH, serving E-DCH cell changes or CN initiated release.
  4. A single integer value.
  5. HSUPA.AbnormalEdchRelease
  6. UtranCellFDD
    UtranCellTDDLcr
    UtranCellTDDHcr
  7. Valid for packet switched traffic.
  8. UMTS.