KPI Workshop RAS06

1 © Nokia Siemens Networks RAS06 KPI & Counter Workshop / Reunanen Jussi / 19.12.2007For internal use

RAN 06 KPIs & CountersRAS06 Delta optimization

For internal use2 © Nokia Siemens Networks RAS06 KPI & Counter Workshop / Reunanen Jussi / 19.12.2007

Note

•This is short version from KPI workshop, purely for RAS06 update


Version HistoryVersion Comments By Counter & KPI

& PI “color”

Version 1.0 2004 Initial version Fabio Di Sarno, Luca Severini, Jussi Reunanen

Version 2.0 2005 Several corrections due to counter modifications -> 1.5.2 ED2. Course flow modified

Jussi Reunanen, Fabio Di Sarno, Luca Severini,

Version 3.0 4.4.2006

RAN´04 + Paging, LAU/RAU, SMS, PS State Change, MultiRAB

Jussi Reunanen et al.

Version 3.1

20.4.2006

RAN´04 additions to AC failures, inter system HHO and SRNC relocation additions, duplicated slides deleted

Jussi Reunanen et al.

Version 4.0 12.06.2006

RAS05 & HSDPA additions Jussi Reunanen & Mikko Toivonen

Version 4.1 14.08.2006

RAS05 Transport counters added (based on material from Raija Lilius)

Jussi Reunanen

Version 5.0 20.03.2007

RAS05.1 Updates Jussi Reunanen

Version 5.1 04.05.2007

RAS05.1 Updates, Corrections and field verification results

Jussi Reunanen

Version 5.3 14.1.2008

RAS06 and RAS05.1 ED Updates Jussi Reunanen


Performance Management Counters in RAS06

SABC SGSN

RNC

RNC

Cell Resource

(M1000)

Service Level

(M1001)

Traffic

(M1002)

L3 signalling on Iu interface

(M1003)

L3 signalling on Iub interface

(M1005)

MGWMSC/HLR

SGSN

RRC Signalling

(M1006)

Soft Handover

(M1007)

WCDMA

GSM

Inter System Handover

(M1010)

Location Services

(M1011)

Service Area Broadcast

(M1012)

RCPM RLC

(M1017)

AAL2 Path CAC Resource

(M550)

AAL2 Resource Reservation

(M8000)HSDPA in WBTS

(M5000)

Cell Throughput measurements

(M1023)

New For RAS6

Packet Call measurements

(M1022)

DSP

(M613)

RCPM OLPC

(M1016) Updated for RAS06

Intra System Handover

(M1008)

ATM Virtual Channel

(M530)


Illustration on RAN KPI

SRNC Relocation

RNC

UEBTS2

BTS1

RNC

Accessibility:RRC Setup & Access

RateRAB Setup & Access

RateCall Setup Success

Rate

XRetainability:

RRC Drop Rate

RAB Drop Rate

Mobility:SHO Success

RateSHO Overhead

Usage:Cell Availability

Ave. Uplink LoadAve. Downlink

Load X Pre-emption

SRNC


Counters and Tables mappingTABLETABLE COUNTERSCOUNTERS

Cell resource M1000Cx

Service level M1001Cx

Traffic M1002Cx

L3 signalling at Iu M1003Cx

L3 signalling at Iur M1004Cx

L3 signalling at Iub M1005Cx

RRC signalling M1006Cx

Soft handover M1007Cx

Intra-system hard handover M1008Cx

L3 relocation signalling M1009Cx

Inter-system handover M1010Cx

Location services M1011Cx

Service area broadcast M1012Cx

RCPM RLC M1017Cx

AAL2 Resource Reservation M800Cx

AAL2 Path CAC Resource M550Cx

HSDPA in WBTS M5000Cx

Not complete list


Cell Resources• HSPA power• Code Usage• BTS HW MeasurementsHSPA in BTS Measurements• HSDPA in BTS• HSUPA in BTSRRC Connection RAB Establishment (Packet Call Measurements)• R99 Activation (RAB setup time)• HSDPA Activation

– RAS06 HSDPA Traffic Measurements• HSUPA Activation

– RAS06 HSUPA Traffic Measurements• HSPA Channel Type SwitchingRAS06 Packet Call Measurements SummaryRAS06 Cell Throughput MeasurementsSoft Handover Measurements• HSPA Serving Cell Change• HSPA Inter RNC Cell Change

Agenda


PrxTotal measurements Cell Resources

Counter ID Counter Incremented IF

M1000C0 AVE_PRXTOT_CLASS_0 (Lrt<=UnloadedRT) AND (Lnrt<=UnloadedNRT)

M1000C2 AVE_PRXTOT_CLASS_1 HSUPA disabled:(PrxTotal<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled:(PrxNonEDPCH<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C4 AVE_PRXTOT_CLASS_2 HSUPA disabled:(PrxTotal>PrxTarget–PrxOffset) AND (PrxTotal<PrxTarget) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled:(PrxNonEDPCH>PrxTarget–PrxOffset) AND (PrxNonEDPCH<PrxTarget) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C6 AVE_PRXTOT_CLASS_3 HSUPA disabled:(PrxTotal>=PrxTarget) AND (PrxTotal<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled:(PrxNonEDPCH>=PrxTarget) AND (PrxNonEDPCH<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C8 AVE_PRXTOT_CLASS_4 HSUPA disabled:(PrxTotal>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled:(PrxNonEDPCH>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))


Uplink Lrt & Lnrt Estimation


M1000C34 AVE_LNRT_CLASS_0 (Lrt<=UnloadedRT) AND (Lnrt<=UnloadedNRT)

M1000C36 AVE_LNRT_CLASS_1 HSUPA disabled:(PrxTotal<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, no E-DCH users in cell:(PrxNonEDPCH<=PrxTarget–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, at least one E-DCH user in cell:(PrxNonEDPCH<=PrxTargetPS–PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C38 AVE_LNRT_CLASS_2 HSUPA disabled:(PrxTotal>PrxTarget–PrxOffset) AND (PrxTotal<PrxTarget) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, no E-DCH users in cell:(PrxNonEDPCH>PrxTarget–PrxOffset) AND (PrxNonEDPCH<PrxTarget) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, at least one E-DCH user in cell:(PrxNonEDPCH>PrxTargetPS–PrxOffset) AND (PrxNonEDPCH<PrxTargetPS) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C40 AVE_LNRT_CLASS_3 HSUPA disabled:(PrxTotal>=PrxTarget) AND (PrxTotal<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, no E-DCH users in cell:(PrxNonEDPCH>=PrxTarget) AND (PrxNonEDPCH<PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, at least one E-DCH user in cell:(PrxNonEDPCH>=PrxTargetPS) AND (PrxNonEDPCH<PrxTargetPS+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))

M1000C42 AVE_LNRT_CLASS_4 HSUPA disabled:(PrxTotal>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, no E-DCH users in cell:(PrxNonEDPCH>=PrxTarget+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))HSUPA enabled, at least one E-DCH user in cell:(PrxNonEDPCH>=PrxTargetPS+PrxOffset) AND ((Lrt>UnloadedRT) OR (Lnrt>UnloadedNRT))


PtxTotal measurements

X = collected sample of PtxTotal measurement

PtxTotal means the total transmitted power in a cell

• the counter value is already average in Watt

• dBm and real value is obtained dividing by 100

Includes the power for CCH and DCH (not HSPA – see clarification below for RAS06)

Cell Resources

BTS periodically reports the total transmission power value PtxTotal and

non-HSDPA power “Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission” if BTS supports only HSDPA -> referred as PtxNonHSDPA

or

non-HSPA power (“Transmitted carrier power of all codes not used for HS-PDSCH HS-SCCH E-AGCH E-RGCH or E-HICH transmission) if BTS supports HSUPA (and HSDPA) -> referred as PtxNonHSPA

to RNC in RRI messages

The reported values are in range 0…100% representing the power value relative to the cell maximum transmission power, defined by MIN[PtxCellMax, MaxDLPowerCapability]


PtxTotal measurements Cell Resources


M1000C14 AVE_PTXTOT_CLASS_0 No calls allocated in the cell.

M1000C16 AVE_PTXTOT_CLASS_1 HSDPA not in use:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxTotal) AND (PtxTotal < (PtxTarget-PtxOffset)) AND “Cell not empty”HSDPA enabled:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxNonHSPA) AND (PtxNonHSPA < (PtxTarget-PtxOffset)) AND “Cell not empty”

M1000C18 AVE_PTXTOT_CLASS_2 HSDPA not in use: (PtxTotal >= (PtxTarget-PtxOffset)) AND (PtxTotal < PtxTarget) AND “Cell not empty”HSDPA enabled:(PtxNonHSPA >= (PtxTarget-PtxOffset)) AND (PtxNonHSPA < PtxTarget) AND “Cell not empty”

M1000C20 AVE_PTXTOT_CLASS_3 HSDPA not in use: (PtxTotal >= (PtxTarget)) AND (PtxTotal < PtxTarget+PtxOffset) AND “Cell not empty”HSDPA enabled: (PtxNonHSPA >= PtxTarget) AND (PtxNonHSPA < PtxTarget+PtxOffset) AND “Cell not empty”

M1000C22 AVE_PTXTOT_CLASS_4 HSDPA not in use:PtxTotal > (PtxTarget+PtxOffset) AND “Cell not empty”HSDPA enabled:PtxNonHSPA>=(PtxTarget+PtxOffset) AND “Cell not empty”


Ptx Excluding HSDPA Power

Due to activation of HSDPA the BTS has to have Ptx measurements excluding the power used by HS-PDSCHs and HS-SCCH so that the AC can be performed according to new rules with HSDPA

BTS is measuring the total transmitted power excluding the power for HS-PDSCH codes and HS-SCCH codes and sends the measurements back to the RNC in NBAP:PRIVATE:RADIO RESOURCE MEASUREMENT REPORT message (3GPP Iub), two new counters are introduced for this purpose

Cell Resources

M1000C139 AVG_NON_HSDPA_PWR_DENOM • The denominator for the average non-HSDPA power ratio

• This counter is updated even if there are not any HS-DSCH allocations in the cell

M1000C139 AVG_NON_HSDPA_PWR_DENOM • The denominator for the average non-HSDPA power ratio


M1000C141 AVG_ACT_NON_HSDPA_PWR_DENOM • The denominator for the average non-HSDPA power ratio

• This counter is updated only if there are HS-DSCH allocations in the cell

M1000C141 AVG_ACT_NON_HSDPA_PWR_DENOM • The denominator for the average non-HSDPA power ratio


M1000C138 AVG_NON_HSDPA_PWR [%] • Transmitted carrier power of all codes not used for HS-PDSCH

or HS-SCCH transmission is the ratio between the total transmitted power of all codes not used for HS-PDSCH or HS-SCCH transmission on one DL carrier from one UTRAN access point, and the maximum transmission power possible to use on that DL carrier at that moment


M1000C138 AVG_NON_HSDPA_PWR [%] • Transmitted carrier power of all codes not used for HS-PDSCH



M1000C140 AVG_ACTIVE_NON_HSDPA_PWR [%] • Transmitted carrier power of all codes not used for HS-PDSCH



M1000C140 AVG_ACTIVE_NON_HSDPA_PWR [%] • Transmitted carrier power of all codes not used for HS-PDSCH



M1000C138 AVG_NON_HSDPA_PWR [%] • If HSUPA is enabled, the non-HSPA power is the transmitted

carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission





M1000C140 AVG_ACTIVE_NON_HSDPA_PWR [%]

• If HSUPA is enabled, the non-HSPA power is the transmitted carrier power of all codes not used for HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH or E-HICH transmission






HSPA Power

M1000C236 MIN_HSPA_DL_POWER [dBm]• The minimum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between

the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) valuesM1000C237 MAX_HSPA_DL_POWER [dBm]• The maximum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between

the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

M1000C236 MIN_HSPA_DL_POWER [dBm]• The minimum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between

the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) valuesM1000C237 MAX_HSPA_DL_POWER [dBm]• The maximum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between

the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

M1000C238 AVE_HSPA_DL_POWER• The average used HSPA power during the

measurement period• The used HSPA power is calculated from the

difference between the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

• Averaging done in W and converted to dBm• Measured results already divided by #samples M1000C239 HSPA_DL_POWER_SAMPLES• The number of samples for the used HSPA

power measurement

M1000C238 AVE_HSPA_DL_POWER• The average used HSPA power during the



• Averaging done in W and converted to dBm• Measured results already divided by #samples M1000C239 HSPA_DL_POWER_SAMPLES• The number of samples for the used HSPA

power measurement

HSDPA active

PtxTarget +PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

PtxNonHSPA

PtxTotal PtxHighHSDPAPwr

In RAS06 the Dynamic Resource Allocation feature can dynamically adjust the power share between HSDPA and R99

• This is done by adjusting the PtxTargetPS value (target for R99 NRT scheduling)

• Therefore new counters are needed to show the max,min and ave HSDPA power

Cell Resources


HSPA PowerCell

Resources







M1000C238 AVE_HSPA_DL_POWER [dBm]• The average used HSPA power during the



• Averaging done in W and converted to dBm• Measured results already divided by #samples

M1000C238 AVE_HSPA_DL_POWER [dBm]• The average used HSPA power during the



• Averaging done in W and converted to dBm• Measured results already divided by #samples







dBmkDENOMPTXTOT

kDENOMPTXTOTkCLASSPTXTOTAVE

dBm) (in Load DL Average RNC_102b

ClassesAllk

ClassesAllk

_

_

__

_____

dBmkDENOMPTXTOT

kDENOMPTXTOTkCLASSPTXTOTAVE

dBm) (in Load DL Average RNC_102b

ClassesAllk

ClassesAllk

_

_

__

_____


HSPA PowerCell

Resources


Ptx_Target_PS

M1000C234 AVE_PTX_TARGET_PS [dBm] • The average target threshold PtxTargetPS value

during the measurement period• The PtxTargetPS value is adjusted dynamically based

on the measurement reports received from the BTSM1000C235 PTX_TARGET_PS_DENOM• The number of samples for the target threshold

PtxTargetPS measurement

M1000C234 AVE_PTX_TARGET_PS [dBm] • The average target threshold PtxTargetPS value

during the measurement period• The PtxTargetPS value is adjusted dynamically based

on the measurement reports received from the BTSM1000C235 PTX_TARGET_PS_DENOM• The number of samples for the target threshold

PtxTargetPS measurement

Cell Resources

M1000C232 MIN_PTX_TARGET_PS [dBm]• The minimum target threshold PtxTargetPS

value during the measurement period• The PtxTargetPS value is adjusted

dynamically based on the measurement reports received from the BTS

M1000C233 MAX_PTX_TARGET_PS [dBm]• The maximum target threshold

PtxTargetPS value during the measurement period

• The PtxTargetPS value is adjusted dynamically based on the measurement reports received from the BTS

M1000C232 MIN_PTX_TARGET_PS [dBm]• The minimum target threshold PtxTargetPS

value during the measurement period• The PtxTargetPS value is adjusted

dynamically based on the measurement reports received from the BTS

M1000C233 MAX_PTX_TARGET_PS [dBm]• The maximum target threshold

PtxTargetPS value during the measurement period

• The PtxTargetPS value is adjusted dynamically based on the measurement reports received from the BTS

HSDPA active


PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

PtxNonHSPA



• This is done by adjusting the PtxTargetPS value (target for R99 NRT scheduling) and therefore there are new counters to measure this “tuning”


Ptx_RT & Measurements Cell Resources


M1000C93 AVE_PTX_RT_CLASS_0 No calls allocated in the cell.

M1000C95 AVE_PTX_RT_CLASS_1 HSDPA not in use:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxTotal) AND (PtxTotal < (PtxTarget-PtxOffset)) AND “Cell not empty”HSDPA enabled:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxNonHSPA) AND (PtxNonHSPA < (PtxTarget-PtxOffset)) AND “Cell not empty”

M1000C97 AVE_PTX_RT_CLASS_2 HSDPA not in use: (PtxTotal >= (PtxTarget-PtxOffset)) AND (PtxTotal < PtxTarget) AND “Cell not empty”HSDPA enabled:(PtxNonHSPA >= (PtxTarget-PtxOffset)) AND (PtxNonHSPA < PtxTarget) AND “Cell not empty”

M1000C99 AVE_PTX_RT_CLASS_3 HSDPA not in use: (PtxTotal >= (PtxTarget)) AND (PtxTotal < PtxTarget+PtxOffset) AND “Cell not empty”HSDPA enabled: (PtxNonHSPA >= PtxTarget) AND (PtxNonHSPA < PtxTarget+PtxOffset) AND “Cell not empty”

M1000C101 AVE_PTX_RT_CLASS_4 HSDPA not in use:PtxTotal > (PtxTarget+PtxOffset) AND “Cell not empty”HSDPA enabled:PtxNonHSPA>=(PtxTarget+PtxOffset) AND “Cell not empty”


Class Counter Incremented IF

M1000C44 AVE_PTX_NRT_CLASS_0 No calls allocated in the cell.

M1000C46 AVE_PTX_NRT_CLASS_1 No HSDPA users in cell:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxTotal) AND (PtxTotal < (PtxTarget-PtxOffset)) AND “Cell not empty”At least one HSDPA user in cell and static resource allocation in use:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxNonHSPA) AND (PtxNonHSPA < (PtxTargetHSDPA-PtxOffsetHSDPA))At least one HSDPA user in cell and dynamic resource allocation in use:((PtxPrimaryCCPCH + PtxPrimaryCPICH) < PtxNonHSPA) AND (PtxNonHSPA < (PtxTargetPS-PtxOffset))

M1000C48 AVE_PTX_NRT_CLASS_2 No HSDPA users in cell:(PtxTotal >= (PtxTarget-PtxOffset)) AND (PtxTotal < PtxTarget) AND “Cell not empty”At least one HSDPA user in cell and static resource allocation in use:(PtxNonHSPA >= (PtxTargetHSDPA-PtxOffsetHSDPA)) AND (PtxNonHSPA < PtxTargetHSDPA)At least one HSDPA user in cell and dynamic resource allocation in use:(PtxNonHSPA >= (PtxTargetPS-PtxOffset)) AND (PtxNonHSPA < PtxTargetPS)

M1000C50 AVE_PTX_NRT_CLASS_3 No HSDPA users in cell:(PtxTotal >= (PtxTarget)) AND (PtxTotal < PtxTarget+PtxOffset) AND “Cell not empty”At least one HSDPA user in cell and static resource allocation in use:(PtxNonHSPA >= PtxTargetHSDPA) AND (PtxNonHSPA < PtxTargetHSDPA+PtxOffsetHSDPA)At least one HSDPA user in cell and dynamic resource allocation in use:(PtxNonHSPA >= PtxTargetPS) AND (PtxNonHSPA < PtxTargetPS+PtxOffset)

M1000C52 AVE_PTX_NRT_CLASS_4 No HSDPA users in cell:PtxTotal > (PtxTarget+PtxOffset)At least one HSDPA user in cell and static resource allocation in use:(PtxNonHSPA>=(PtxTargetHSDPA+PtxOffsetHSDPA)) At least one HSDPA user in cell and dynamic resource allocation in use:(PtxNonHSPA>=(PtxTargetPS+PtxOffset))

Ptx_NRT Measurements Cell Resources


HSPA Power

M1000C236 MIN_HSPA_DL_POWER • The minimum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between the

PtxTotal and PtxNonHSPA (or PtxNonHSDPA) valuesM1000C237 MAX_HSPA_DL_POWER• The maximum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between the

PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

M1000C236 MIN_HSPA_DL_POWER • The minimum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between the

PtxTotal and PtxNonHSPA (or PtxNonHSDPA) valuesM1000C237 MAX_HSPA_DL_POWER• The maximum used HSPA power during the measurement period• The used HSPA power is calculated from the difference between the

PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

Cell Resources

M1000C238 AVE_HSPA_DL_POWER• The average used HSPA power during

the measurement period• The used HSPA power is calculated from

the difference between the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

M1000C239 HSPA_DL_POWER_SAMPLES

• The number of samples for the used HSPA power measurement

M1000C238 AVE_HSPA_DL_POWER• The average used HSPA power during

the measurement period• The used HSPA power is calculated from

the difference between the PtxTotal and PtxNonHSPA (or PtxNonHSDPA) values

M1000C239 HSPA_DL_POWER_SAMPLES

• The number of samples for the used HSPA power measurement

HSDPA active


PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

PtxNonHSPA



• This is done by adjusting the PtxTargetPS value (target for R99 NRT scheduling)

• Therefore new counters are needed to show the max,min and ave HSDPA power


HSPA Power Cell Resources

BTS periodically reports the total transmission power value PtxTotal and non-HSDPA power • “Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH

transmission” if BTS supports only HSDPAor• non-HSPA power (“Transmitted carrier power of all codes not used for HS-PDSCH HS-

SCCH E-AGCH E-RGCH or E-HICH transmission) if BTS supports HSUPAto RNC in RRI messages• These two are referenced as “HSxPA power” The reported values are in range 0…100% representing the power value relative to the cell maximum transmission power, defined by MIN[PtxCellMax, MaxDLPowerCapability] From the difference of reported PtxTotal and HSxPA power, RNC can calculate the used HSPA-power value and update that to statistics counters• The counters are updated only when there is at least one HSDPA allocation in the cellRNC updates the HSxPA power value counters when nbap_radio_resource_ind_s message including PtxTotal and HSxPA power information is received from BTS and there is at least one HSDPA allocation in the cellThe unit for all counter updates is watt


Code Allocation Requests

RAS06 includes following counters to count requested channelisation code allocations per spreading factor

Cell Resources

M1000C259 CHAN_CODE_SF4_REQUEST


















Agenda


BTS HW Measurement

sFor HSUPA reservation following counters can be used to monitor the CE reservation

BTS HW Measurement M5001– CE Usage

M5001C9 MAX_HSUPA_CE_UL, tells the maximum number of used Channel Elements for HSUPA in Uplink direction

M5001C10 MIN_HSUPA_CE_UL, tells the minimum number of used Channel Elements for HSUPA in Uplink direction

Counters are updated when resources used for HSUPA users are reduced

The counter is updated over the measurement period

M5001C9 MAX_HSUPA_CE_UL, tells the maximum number of used Channel Elements for HSUPA in Uplink direction

M5001C10 MIN_HSUPA_CE_UL, tells the minimum number of used Channel Elements for HSUPA in Uplink direction



M5001C11 AVG_HSUPA_CE_UL, tells the average number of used Channel Elements for HSUPA in Uplink direction


The value of the counter is the average value from all the samples during the measurement period

M5001C11 AVG_HSUPA_CE_UL, tells the average number of used Channel Elements for HSUPA in Uplink direction



M5001C12 MAX_HSUPA_CE_DL, tells the maximum number of used Channel Elements for HSUPA in Downlink direction

M5001C13 MIN_HSUPA_CE_DL, tells the minimum number of used Channel Elements for HSUPA in Downlink direction



M5001C12 MAX_HSUPA_CE_DL, tells the maximum number of used Channel Elements for HSUPA in Downlink direction

M5001C13 MIN_HSUPA_CE_DL, tells the minimum number of used Channel Elements for HSUPA in Downlink direction



M5001C14 AVG_HSUPA_CE_DL, tells the average number of used Channel Elements for HSUPA in Downlink direction



M5001C14 AVG_HSUPA_CE_DL, tells the average number of used Channel Elements for HSUPA in Downlink direction




BTS HW Measurement

sFor HSUPA reservation following counters can be used to monitor the CE reservation

BTS HW Measurement M5001– CE Usage

CEAVE_AVAIL_ M5001C2

CE_ULAVG_HSUPA_ M5001C11

[%] BTS in HSUPA UL for CE Utilized if Ratio Average RNC_948a


CE_ULAVG_HSUPA_ M5001C11

[%] BTS in HSUPA UL for CE Utilized if Ratio Average RNC_948a


CE_DLAVG_HSUPA_ M5001C10

[%] BTS in HSUPA DL for CE Utilized if Ratio Average RNC_947a


CE_DLAVG_HSUPA_ M5001C10

[%] BTS in HSUPA DL for CE Utilized if Ratio Average RNC_947a


Cell Resources• HSPA power• Code Usage• BTS HW MeasurementsHSPA in BTS Measurements• HSDPA in BTS• HSUPA in BTSRRC Connection RAB Establishment (Packet Call Measurements)• R99 Activation• HSDPA Activation



Agenda


HSPA TX-power

Common channels

DCH RT

DCH NRT

HS-DSCH+HS-SCCH+ E-

AGCH+E-RGCH+E-HICH

Max power

Non-controllable power

Controllable powernon-HSPApower measurements

Power measurementsfrom the Node-B to

the RNC

HSDPA in BTS


HSUPA DL PowerHSDPA in

BTS

In this measurement are calculated average/min/max values for Transmitted carrier power used for E-AGCH E-RGCH and E-HICH transmission measurement value

Counters are updated in 100 ms periods

M5000C145 HSUPA_DL_PWR_DIST_CLASS_01 - Number of measurement periods whose average power matches the power limits of class 1 (power < 0.1W)

M5000C146 HSUPA_DL_PWR_DIST_CLASS_02 - Number of measurement periods whose average power matches the power limits of class 2 (0.1W >= power < 0.2W)




M5000C150 HSUPA_DL_PWR_DIST_CLASS_06 - Number of measurement periods whose average power matches the power limits of class 6 (power >= 1.6W)

M5000C145 HSUPA_DL_PWR_DIST_CLASS_01 - Number of measurement periods whose average power matches the power limits of class 1 (power < 0.1W)





M5000C150 HSUPA_DL_PWR_DIST_CLASS_06 - Number of measurement periods whose average power matches the power limits of class 6 (power >= 1.6W)


HSDPA Modulations and Original Transmission

Original transmission per modulation type and per # codes are counted with M5000C49 – M5000C58

0

1000000

2000000

3000000

4000000

5000000

6000000

7000000

OR

IG_T

RA

NS

_1_C

OD

E_1

6QA

M (

Hsd

paw

)

OR

IG_T

RA

NS

_1_C

OD

E_Q

PS

K (

Hsd

paw

)

OR

IG_T

RA

NS

_2_C

OD

E_Q

PS

K (

Hsd

paw

)

OR

IG_T

RA

NS

_3_C

OD

E_Q

PS

K (

Hsd

paw

)

OR

IG_T

RA

NS

_4_C

OD

E_Q

PS

K (

Hsd

paw

)

OR

IG_T

RA

NS

_5_C

OD

E_Q

PS

K (

Hsd

paw

)

HSDPA in BTS

When the original MAC-hs PDU transmission with # codes, indicated in the counter name by QPSK modulation, is done in the BTS one of the counters below is incremented:M5000C49 ORIG_TRANS_1_CODE_QPSK M5000C50 ORIG_TRANS_2_CODE_QPSK M5000C51 ORIG_TRANS_3_CODE_QPSK M5000C52 ORIG_TRANS_4_CODE_QPSK M5000C53 ORIG_TRANS_5_CODE_QPSK

When the original MAC-hs PDU transmission with # codes, indicated in the counter name by QPSK modulation, is done in the BTS one of the counters below is incremented:M5000C49 ORIG_TRANS_1_CODE_QPSK M5000C50 ORIG_TRANS_2_CODE_QPSK M5000C51 ORIG_TRANS_3_CODE_QPSK M5000C52 ORIG_TRANS_4_CODE_QPSK M5000C53 ORIG_TRANS_5_CODE_QPSK

M5000C96 ORIG_TRANS_6_CODE_16QAMM5000C97 ORIG_TRANS_7_CODE_16QAMM5000C98 ORIG_TRANS_8_CODE_16QAMM5000C99 ORIG_TRANS_9_CODE_16QAMM5000C100 ORIG_TRANS_10_CODE_16QAMM5000C101 ORIG_TRANS_11_CODE_16QAMM5000C102 ORIG_TRANS_12_CODE_16QAMM5000C103 ORIG_TRANS_13_CODE_16QAMM5000C104 ORIG_TRANS_14_CODE_16QAMM5000C105 ORIG_TRANS_15_CODE_16QAM

M5000C96 ORIG_TRANS_6_CODE_16QAMM5000C97 ORIG_TRANS_7_CODE_16QAMM5000C98 ORIG_TRANS_8_CODE_16QAMM5000C99 ORIG_TRANS_9_CODE_16QAMM5000C100 ORIG_TRANS_10_CODE_16QAMM5000C101 ORIG_TRANS_11_CODE_16QAMM5000C102 ORIG_TRANS_12_CODE_16QAMM5000C103 ORIG_TRANS_13_CODE_16QAMM5000C104 ORIG_TRANS_14_CODE_16QAMM5000C105 ORIG_TRANS_15_CODE_16QAM

M5000C86 ORIG_TRANS_6_CODE_QPSKM5000C87 ORIG_TRANS_7_CODE_QPSKM5000C88 ORIG_TRANS_8_CODE_QPSKM5000C89 ORIG_TRANS_9_CODE_QPSKM5000C90 ORIG_TRANS_10_CODE_QPSKM5000C91 ORIG_TRANS_11_CODE_QPSKM5000C92 ORIG_TRANS_12_CODE_QPSKM5000C93 ORIG_TRANS_13_CODE_QPSKM5000C94 ORIG_TRANS_14_CODE_QPSKM5000C95 ORIG_TRANS_15_CODE_QPSK

M5000C86 ORIG_TRANS_6_CODE_QPSKM5000C87 ORIG_TRANS_7_CODE_QPSKM5000C88 ORIG_TRANS_8_CODE_QPSKM5000C89 ORIG_TRANS_9_CODE_QPSKM5000C90 ORIG_TRANS_10_CODE_QPSKM5000C91 ORIG_TRANS_11_CODE_QPSKM5000C92 ORIG_TRANS_12_CODE_QPSKM5000C93 ORIG_TRANS_13_CODE_QPSKM5000C94 ORIG_TRANS_14_CODE_QPSKM5000C95 ORIG_TRANS_15_CODE_QPSK

When the original MAC-hs PDU transmission with # codes, indicated in the counter name by QPSK modulation, is done in the BTS one of the counters below is incremented:M5000C54 ORIG_TRANS_1_CODE_16QAMM5000C55 ORIG_TRANS_2_CODE_16QAMM5000C56 ORIG_TRANS_3_CODE_16QAM M5000C57 ORIG_TRANS_4_CODE_16QAM M5000C58 ORIG_TRANS_5_CODE_16QAM

When the original MAC-hs PDU transmission with # codes, indicated in the counter name by QPSK modulation, is done in the BTS one of the counters below is incremented:M5000C54 ORIG_TRANS_1_CODE_16QAMM5000C55 ORIG_TRANS_2_CODE_16QAMM5000C56 ORIG_TRANS_3_CODE_16QAM M5000C57 ORIG_TRANS_4_CODE_16QAM M5000C58 ORIG_TRANS_5_CODE_16QAM


HSDPA Modulations and Re-Transmissions

Retransmission per modulation type and per # codes are counted with M5000C59 – M5000C68 counters

0

50000

100000

150000

200000

250000

300000

350000

400000

450000

500000

HSDPA in BTS

When the MAC-hs PDU retransmission with #codes, indicated by the counter name by QPSK modulation, is done in the BTS, one of the counters below is incremented:M5000C59 RETRANS_1_CODE_QPSKM5000C59 RETRANS_1_CODE_QPSKM5000C60 RETRANS_2_CODE_QPSKM5000C61 RETRANS_3_CODE_QPSKM5000C62 RETRANS_4_CODE_QPSKM5000C63 RETRANS_5_CODE_QPSK

When the MAC-hs PDU retransmission with #codes, indicated by the counter name by QPSK modulation, is done in the BTS, one of the counters below is incremented:M5000C59 RETRANS_1_CODE_QPSKM5000C59 RETRANS_1_CODE_QPSKM5000C60 RETRANS_2_CODE_QPSKM5000C61 RETRANS_3_CODE_QPSKM5000C62 RETRANS_4_CODE_QPSKM5000C63 RETRANS_5_CODE_QPSK

When the MAC-hs PDU retransmission with #codes, indicated by the counter name by 16QAM modulation, is done in the BTS, one of the counters below is incremented:M5000C64 RETRANS_1_CODE_16QAM M5000C65 RETRANS_2_CODE_16QAM M5000C66 RETRANS_3_CODE_16QAM M5000C67 RETRANS_4_CODE_16QAM M5000C68 RETRANS_5_CODE_16QAM

When the MAC-hs PDU retransmission with #codes, indicated by the counter name by 16QAM modulation, is done in the BTS, one of the counters below is incremented:M5000C64 RETRANS_1_CODE_16QAM M5000C65 RETRANS_2_CODE_16QAM M5000C66 RETRANS_3_CODE_16QAM M5000C67 RETRANS_4_CODE_16QAM M5000C68 RETRANS_5_CODE_16QAM

M5000C106 RETRANS_6_CODE_QPSKM5000C107 RETRANS_7_CODE_QPSKM5000C108 RETRANS_8_CODE_QPSKM5000C109 RETRANS_9_CODE_QPSKM5000C110 RETRANS_10_CODE_QPSKM5000C111 RETRANS_11_CODE_QPSKM5000C112 RETRANS_12_CODE_QPSKM5000C113 RETRANS_13_CODE_QPSKM5000C114 RETRANS_14_CODE_QPSKM5000C115 RETRANS_15_CODE_QPSK

M5000C106 RETRANS_6_CODE_QPSKM5000C107 RETRANS_7_CODE_QPSKM5000C108 RETRANS_8_CODE_QPSKM5000C109 RETRANS_9_CODE_QPSKM5000C110 RETRANS_10_CODE_QPSKM5000C111 RETRANS_11_CODE_QPSKM5000C112 RETRANS_12_CODE_QPSKM5000C113 RETRANS_13_CODE_QPSKM5000C114 RETRANS_14_CODE_QPSKM5000C115 RETRANS_15_CODE_QPSK

M5000C116 RETRANS_6_CODE_16QAMM5000C117 RETRANS_7_CODE_16QAMM5000C118 RETRANS_8_CODE_16QAMM5000C119 RETRANS_9_CODE_16QAMM5000C120 RETRANS_10_CODE_16QAMM5000C121 RETRANS_11_CODE_16QAMM5000C122 RETRANS_12_CODE_16QAMM5000C123 RETRANS_13_CODE_16QAMM5000C124 RETRANS_14_CODE_16QAMM5000C125 RETRANS_15_CODE_16QAM

M5000C116 RETRANS_6_CODE_16QAMM5000C117 RETRANS_7_CODE_16QAMM5000C118 RETRANS_8_CODE_16QAMM5000C119 RETRANS_9_CODE_16QAMM5000C120 RETRANS_10_CODE_16QAMM5000C121 RETRANS_11_CODE_16QAMM5000C122 RETRANS_12_CODE_16QAMM5000C123 RETRANS_13_CODE_16QAMM5000C124 RETRANS_14_CODE_16QAMM5000C125 RETRANS_15_CODE_16QAM


HSDPA MAC-d PDUs

BTS measures the number of incoming PDU in DL direction as well as buffer overflows

Amount of data received from the RNC in MAC-d PDUs i.e. MAC-d PDU size:

Amount of data in MAC-d PDUs discarded due to flow control buffer overflow:

HSDPA in BTS

The BTS counts the total number of received MAC-d PDUs with the counter M5000C7 MAC_D_PDU_TOT The BTS counts the total number of received MAC-d PDUs with the counter M5000C7 MAC_D_PDU_TOT

M5000C6 MAC_D_PDU_DROP_BTS_OWFL counter is incremented by the BTS when MAC-d PDU is dropped from BTS buffer due to overflow of the buffer

M5000C6 MAC_D_PDU_DROP_BTS_OWFL counter is incremented by the BTS when MAC-d PDU is dropped from BTS buffer due to overflow of the buffer

M5000C126 RECEIVED_HS_MACD_BITSM5000C126 RECEIVED_HS_MACD_BITS

M5000C127 DISCARDED_HS_MACD_BITSM5000C127 DISCARDED_HS_MACD_BITS


HSDPA Data Volume and Throughput

Transferred data volume at Iub can be calculated as:

HSDPA MAC-d net throughput at BTS [kbit/s] can be calculated as:

HSDPA in BTS

RNC_608A =

RNC_608A =

Mbit1000000

336_TOT MAC_D_PDUM5000C7

RNC_606B = RNC_606B =

skbits 60ationperiod_dur1000

336 OWFL_DROP_BTS_ MAC_D_PDUM5000C6-_TOT MAC_D_PDUM5000C7/

RNC_608b =

RNC_608b =

Mbit1000

SS_MACD_BITRECEIVED_H M5000C126


HSDPA Unscheduled TTIsHSDPA in

BTS

When data is not sent from the user buffers (queues), the counter is incremented by one for each unscheduled TTIs

Number of unscheduled TTIs (HSDPA idle time) when data is not sent from the user buffers (queues) M5000C44 TTI_NOT_SCHED_DATA_IN_BUFF

Number of unscheduled TTIs (HSDPA idle time) when data is not sent from the user buffers (queues) M5000C44 TTI_NOT_SCHED_DATA_IN_BUFF

Number of unscheduled TTIs when there is data in at least one of the user buffers M5000C45 TTI_NOT_SEND_DATA_FROM_BUFF

Number of unscheduled TTIs when there is data in at least one of the user buffers M5000C45 TTI_NOT_SEND_DATA_FROM_BUFF

Number of user buffers with data in the buffer for each TTI :

M5000C85 HSDPA_BUFF_WITH_DATA_PER_TTI

Tells the average amount of users per TTI for code mux cases

Number of user buffers with data in the buffer for each TTI :

M5000C85 HSDPA_BUFF_WITH_DATA_PER_TTI

Tells the average amount of users per TTI for code mux cases


HSDPA Scheduling Statistics: Shared Scheduler HSDPA in

BTS

Code Shared HSDPA Scheduler for BTS feature allows transmitting to all HSDPA capability cells (maximum three) within the same TTI

This measurement allows monitoring the WBTS scheduling efficiency by collecting measurement data of simultaneously code multiplexed HSDPA users in TTI level

M5000C76 HSDPA_USERS_0_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and one HSDPA user in the other cell (0-1).

M5000C77 HSDPA_USERS_0_2_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and two HSDPA users in the other cell (0-2)

M5000C78 HSDPA_USERS_0_3_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and three HSDPA users in the other cell (0-3)

M5000C79 HSDPA_USERS_1_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and no HSDPA users in the other cell (1-0)

M5000C80 HSDPA_USERS_1_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and one HSDPA user in the other cell (1-1)

M5000C81 HSDPA_USERS_1_2_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and two HSDPA users in the other cell (1-2)

M5000C82 HSDPA_USERS_2_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there are two HSDPA users in the target cell and no HSDPA users in the other cell (2-0)

M5000C83HSDPA_USERS_2_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there are two HSDPA users in the target cell and one HSDPA user in the other cell (2-1)

M5000C84HSDPA_USERS_3_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there are three HSDPA users in the target cell and no HSDPA users in the other cell (3-0)

Counters are incremneted for every TTI for which there is data in the HSDPA user buffers, the data (MAC-hs PDU) is scheduled to be sent to the user and the cell combination matches the counter description.

M5000C76 HSDPA_USERS_0_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and one HSDPA user in the other cell (0-1).

M5000C77 HSDPA_USERS_0_2_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and two HSDPA users in the other cell (0-2)

M5000C78 HSDPA_USERS_0_3_IN_CELLS - Number of scheduled HSDPA users per TTI when there are no HSDPA users in the target cell and three HSDPA users in the other cell (0-3)

M5000C79 HSDPA_USERS_1_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and no HSDPA users in the other cell (1-0)

M5000C80 HSDPA_USERS_1_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and one HSDPA user in the other cell (1-1)

M5000C81 HSDPA_USERS_1_2_IN_CELLS - Number of scheduled HSDPA users per TTI when there is one HSDPA user in the target cell and two HSDPA users in the other cell (1-2)

M5000C82 HSDPA_USERS_2_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there are two HSDPA users in the target cell and no HSDPA users in the other cell (2-0)

M5000C83HSDPA_USERS_2_1_IN_CELLS - Number of scheduled HSDPA users per TTI when there are two HSDPA users in the target cell and one HSDPA user in the other cell (2-1)

M5000C84HSDPA_USERS_3_0_IN_CELLS - Number of scheduled HSDPA users per TTI when there are three HSDPA users in the target cell and no HSDPA users in the other cell (3-0)

Counters are incremneted for every TTI for which there is data in the HSDPA user buffers, the data (MAC-hs PDU) is scheduled to be sent to the user and the cell combination matches the counter description.


HSDPA MAC-hs Efficiency

RNC_607B HSDPA MAC-hs efficiency (%)• HSDPA “Retransmission ratio” between BTS and HSDPA Capable UEs done by MAC-hs

– Based on successfully sent MAC-hs PDUs divided by totally sent MAC-hs PDUs

• Actually, this is the successfully sent MAC-hs PDUs divided by all transmitted MAC-hs PDUs including retransmissions

HSDPA in BTS

%100

CODE_16QAMRETRANS_5_ M5000C68CODE_16QAMRETRANS_4_ M5000C67

CODE_16QAMRETRANS_3_ M5000C66 CODE_16QAMRETRANS_2_ M5000C65CODE_16QAMRETRANS_1_ M5000C64

CODE_QPSKRETRANS_5_ M5000C63CODE_QPSKRETRANS_4_ M5000C62CODE_QPSKRETRANS_3_ M5000C61

CODE_QPSKRETRANS_2_ M5000C60CODE_QPSKRETRANS_1_ M5000C59QAM_5_CODE_16ORIG_TRANS M5000C58

QAM_4_CODE_16ORIG_TRANS M5000C57 QAM_3_CODE_16ORIG_TRANS M5000C56 QAM_2_CODE_16ORIG_TRANS M5000C55

QAM_1_CODE_16ORIG_TRANS M5000C54 SK_5_CODE_QPORIG_TRANS M5000C53 SK_4_CODE_QPORIG_TRANS M5000C52

SK_3_CODE_QPORIG_TRANS M5000C51 SK_2_CODE_QPORIG_TRANS M5000C50 SK_1_CODE_QPORIG_TRANS M5000C49

T_CL_5U_RETR_DIS MAC_HS_PDM5000C1 T_CL_4U_RETR_DIS MAC_HS_PDM5000C4 T_CL_3U_RETR_DIS MAC_HS_PDM5000C3


RNC_607B %100

CODE_16QAMRETRANS_5_ M5000C68CODE_16QAMRETRANS_4_ M5000C67






SK_3_CODE_QPORIG_TRANS M5000C51 SK_2_CODE_QPORIG_TRANS M5000C50 SK_1_CODE_QPORIG_TRANS M5000C49



RNC_607B


HSDPA MAC-hs Efficiency

RNC_607c HSDPA MAC-hs efficiency (%)• HSDPA “Retransmission ratio” between BTS and HSDPA Capable UEs done by MAC-hs

– Based on successfully sent MAC-hs PDUs divided by totally sent MAC-hs PDUs

• Actually, this is the successfully sent MAC-hs PDUs divided by all transmitted MAC-hs PDUs including retransmissions

HSDPA in BTS

%100

M_CODE_16QARETRANS_15 M5000C125+M_CODE_16QARETRANS_14 M5000C124+M_CODE_16QARETRANS_13 M5000C123+


CODE_16QAMRETRANS_9_ M5000C119+CODE_16QAMRETRANS_8_ M5000C118+CODE_16QAMRETRANS_7_ M5000C117+

CODE_16QAMRETRANS_6_ M5000C116+_CODE_QPSKRETRANS_15 M5000C115+_CODE_QPSKRETRANS_14 M5000C114+

_CODE_QPSKRETRANS_13 M5000C113+_CODE_QPSKRETRANS_12 M5000C112+_CODE_QPSKRETRANS_11 M5000C111+

_CODE_QPSKRETRANS_10 M5000C110+CODE_QPSKRETRANS_9_ M5000C109+CODE_QPSKRETRANS_8_ M5000C108+

CODE_QPSKRETRANS_7_ M5000C107+CODE_QPSKRETRANS_6_ M5000C106+6QAM_15_CODE_1ORIG_TRANS M5000C105+

6QAM_14_CODE_1ORIG_TRANS M5000C104+6QAM_13_CODE_1ORIG_TRANS M5000C103+6QAM_12_CODE_1ORIG_TRANS M5000C102+

6QAM_11_CODE_1ORIG_TRANS M5000C101+6QAM_10_CODE_1ORIG_TRANS M5000C100+QAM_9_CODE_16ORIG_TRANS M5000C99+

QAM_8_CODE_16ORIG_TRANS M5000C98+QAM_7_CODE_16ORIG_TRANS M5000C97+QAM_6_CODE_16ORIG_TRANS M5000C96+

PSK_15_CODE_QORIG_TRANS M5000C95+PSK_14_CODE_QORIG_TRANS M5000C94+PSK_13_CODE_QORIG_TRANS M5000C93+


SK_9_CODE_QPORIG_TRANS M5000C89+SK_8_CODE_QPORIG_TRANS M5000C88+SK_7_CODE_QPORIG_TRANS M5000C87+

SK_6_CODE_QPORIG_TRANS M5000C86+CODE_16QAMRETRANS_5_ M5000C68CODE_16QAMRETRANS_4_ M5000C67






SK_3_CODE_QPORIG_TRANS M5000C51 SK_2_CODE_QPORIG_TRANS M5000C50 SK_1_CODE_QPORIG_TRANS M5000C49 T_CL_5U_RETR_DIS MAC_HS_PDM5000C1 T_CL_4U_RETR_DIS MAC_HS_PDM5000C4 T_CL_3U_RETR_DIS MAC_HS_PDM5000C3


RNC_607c %100



CODE_16QAMRETRANS_9_ M5000C119+CODE_16QAMRETRANS_8_ M5000C118+CODE_16QAMRETRANS_7_ M5000C117+

CODE_16QAMRETRANS_6_ M5000C116+_CODE_QPSKRETRANS_15 M5000C115+_CODE_QPSKRETRANS_14 M5000C114+

_CODE_QPSKRETRANS_13 M5000C113+_CODE_QPSKRETRANS_12 M5000C112+_CODE_QPSKRETRANS_11 M5000C111+

_CODE_QPSKRETRANS_10 M5000C110+CODE_QPSKRETRANS_9_ M5000C109+CODE_QPSKRETRANS_8_ M5000C108+

CODE_QPSKRETRANS_7_ M5000C107+CODE_QPSKRETRANS_6_ M5000C106+6QAM_15_CODE_1ORIG_TRANS M5000C105+

6QAM_14_CODE_1ORIG_TRANS M5000C104+6QAM_13_CODE_1ORIG_TRANS M5000C103+6QAM_12_CODE_1ORIG_TRANS M5000C102+

6QAM_11_CODE_1ORIG_TRANS M5000C101+6QAM_10_CODE_1ORIG_TRANS M5000C100+QAM_9_CODE_16ORIG_TRANS M5000C99+

QAM_8_CODE_16ORIG_TRANS M5000C98+QAM_7_CODE_16ORIG_TRANS M5000C97+QAM_6_CODE_16ORIG_TRANS M5000C96+



SK_9_CODE_QPORIG_TRANS M5000C89+SK_8_CODE_QPORIG_TRANS M5000C88+SK_7_CODE_QPORIG_TRANS M5000C87+

SK_6_CODE_QPORIG_TRANS M5000C86+CODE_16QAMRETRANS_5_ M5000C68CODE_16QAMRETRANS_4_ M5000C67






SK_3_CODE_QPORIG_TRANS M5000C51 SK_2_CODE_QPORIG_TRANS M5000C50 SK_1_CODE_QPORIG_TRANS M5000C49 T_CL_5U_RETR_DIS MAC_HS_PDM5000C1 T_CL_4U_RETR_DIS MAC_HS_PDM5000C4 T_CL_3U_RETR_DIS MAC_HS_PDM5000C3


RNC_607c





Agenda


HSUPA MAC-e RetransmissionsHSUPA in

BTS

Number of MAC-e PDUs that are received correctly with the number of retransmissions indicated in the counter name in E-DCH Serving Cell (HSDPA serving cell)

M5000C128 MACE_PDU_RETR_00_COUNTER – no retransmissions

M5000C129 MACE_PDU_RETR_01_COUNTER – 1 retransmission

M5000C130 MACE_PDU_RETR_02_COUNTER











M5000C128 MACE_PDU_RETR_00_COUNTER – no retransmissions

M5000C129 MACE_PDU_RETR_01_COUNTER – 1 retransmission













HSUPA MAC-e PDUsHSUPA in

BTS

Number of MAC-e PDUs that are received correctly but the number of retransmissions is unknown

• Counter is incremented when a MAC-e PDU is correctly received but the number of retransmissions is not known

M5000C144 MACE_PDU_RETR_UNKNOWN_COUNTERM5000C144 MACE_PDU_RETR_UNKNOWN_COUNTER


HSUPA MAC-e PDUsHSUPA in

BTS

Number of DTXs (no transmission) detected in E-DCH Serving Cell

• Counter is incremented when a DTX is detected

Number of MAC-e PDUs that are not received correctly despite retransmission in E-DCH Serving Cell

• Counter is incremented when a new MAC-e PDU transmission is received and DTX detected but the previous MAC-e PDU was not succesfully received

Number of MAC-e PDUs that are received correctly but lost for an unknown reason, such as buffer overflow

• Counter is incremented when a MAC-e PDU is correctly received but lost for an unknown reason

M5000C141 MACE_PDU_DTX_COUNTERM5000C141 MACE_PDU_DTX_COUNTER

M5000C142 MACE_PDU_HARQ_FAIL_COUNTERM5000C142 MACE_PDU_HARQ_FAIL_COUNTER

M5000C143 MACE_PDU_LOST_COUNTERM5000C143 MACE_PDU_LOST_COUNTER


HSUPA MAC-es BLER

The measured Block Error Rate for HSUPA Radio Bearers in Uplink

• Block Error Rate calculated based on HARQ first and successful transmissions compared to all successful transmissions and failed transmissions

• This KPI is based on HSPA in WBTS Measurement

HSUPA in BTS

COUNTERHARQ_FAIL_ MACE_PDU_ M5000C142+UNTERRETR_12_CO MACE_PDU_ M5000C140+

UNTERRETR_11_CO MACE_PDU_ M5000C139+UNTERRETR_10_CO MACE_PDU_ M5000C138+





UNTERRETR_01_CO MACE_PDU_ M5000C129+UNTERRETR_00_CO MACE_PDU_M5000C128

UNTERRETR_00_CO MACE_PDU_M5000C128100100

[%] BLER es- MACHSUPA RNC_917a

COUNTERHARQ_FAIL_ MACE_PDU_ M5000C142+UNTERRETR_12_CO MACE_PDU_ M5000C140+






UNTERRETR_01_CO MACE_PDU_ M5000C129+UNTERRETR_00_CO MACE_PDU_M5000C128

UNTERRETR_00_CO MACE_PDU_M5000C128100100

[%] BLER es- MACHSUPA RNC_917a


Minimum HSUPA MAC-d throughput [kilobits/s] using the average over the measurement period

• Updated in 100 ms periods

Maximum HSUPA MAC-d throughput [kilobits/s] using the average over the measurement period


Average HSUPA MAC-d throughput [kilobits/s] using the average over the measurement period samples


HSUPA MAC-d ThroughputHSUPA in

BTS

M5000C151 HSUPA_MIN_MACD_THRM5000C151 HSUPA_MIN_MACD_THR

M5000C152 HSUPA_MAX_MACD_THRM5000C152 HSUPA_MAX_MACD_THR

M5000C153 HSUPA_AVE_MACD_THRM5000C153 HSUPA_AVE_MACD_THR


Minimum received HSUPA power using the average over the measurement period


Maximum received HSUPA power using the average over the measurement period


Average received HSUPA power using the average over the measurement period samples


HSUPA Received PowerHSUPA in

BTS

M5000C154 HSUPA_UL_PWR_MINM5000C154 HSUPA_UL_PWR_MIN

M5000C155 HSUPA_UL_PWR_MAXM5000C155 HSUPA_UL_PWR_MAX

M5000C156 HSUPA_UL_PWR_AVGM5000C156 HSUPA_UL_PWR_AVG


Number of samples used for received HSUPA power counters

• Updated each time a HSUPA UL Physical Channel power sample is calculated

HSUPA Received PowerHSUPA in

BTS

M5000C157 HSUPA_UL_PWR_SAMPLE_COUNTERM5000C157 HSUPA_UL_PWR_SAMPLE_COUNTER


Cell Resources• HSDPA power• Code Usage• BTS HW MeasurementsHSPA in BTS Measurements• HSDPA in BTS• HSUPA in BTSRRC Connection RAB Establishment (Packet Call Measurements)• R99 Activation (RAB setup time)• HSDPA Activation



Agenda


[RACH] RRC:RRC Connection Request

UEUE Node BNode B RNCRNC

NBAP: RL Setup Request

Start TX/RXStart TX/RXNBAP: RL Setup

Failure

AC to check to accept or reject RRC Connection

Request


Request

(M1005C10) SETUP_FAIL_RL_O_M_INTERV(M1005C11) SETUP_FAIL_RL_ALREADY_ACTIV(M1005C12) SETUP_FAIL_FIRST_RL_HW_RES(M1005C13) SETUP_FAIL_RL_NOT_ENOUGH_RES(M1005C14) SETUP_FAIL_RL_BTS_NOT_RESP(M1005C15) SETUP_FAIL_RL_BTS_GEN_REA

(M1005C10) SETUP_FAIL_RL_O_M_INTERV(M1005C11) SETUP_FAIL_RL_ALREADY_ACTIV(M1005C12) SETUP_FAIL_FIRST_RL_HW_RES(M1005C13) SETUP_FAIL_RL_NOT_ENOUGH_RES(M1005C14) SETUP_FAIL_RL_BTS_NOT_RESP(M1005C15) SETUP_FAIL_RL_BTS_GEN_REA

[FACH] RRC:RRC Connection Reject

RL allocation rejection triggers:RNC_330a=(M1001C4) RRC_CONN_STP_FAIL_BTS

RL allocation rejection triggers:RNC_330a=(M1001C4) RRC_CONN_STP_FAIL_BTS

RRC Setup Phase

In case the BTS rejects the attempt the DCH_ALLO_DURA_xxx and DCH_ALLO_xxx are NOT incremented


In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones:M1005C176 SETUP_FAIL_FIRST_RL_RNLM1005C177 SETUP_FAIL_FIRST_RL_TRLM1005C178 SETUP_FAIL_FIRST_RL_PROTM1005C179 SETUP_FAIL_FIRST_RL_MISCCounters are incremented in case of RRC Connection Setup or state transition to Cell_DCH

In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones:M1005C176 SETUP_FAIL_FIRST_RL_RNLM1005C177 SETUP_FAIL_FIRST_RL_TRLM1005C178 SETUP_FAIL_FIRST_RL_PROTM1005C179 SETUP_FAIL_FIRST_RL_MISCCounters are incremented in case of RRC Connection Setup or state transition to Cell_DCH

If RRC Connection is rejected the RNC will send RRC: RRC Connection Reject Message to the UE and increments counter: M1006C21 RRC_CONN_REJECT

If RRC Connection is rejected the RNC will send RRC: RRC Connection Reject Message to the UE and increments counter: M1006C21 RRC_CONN_REJECT

RRC Performance

Typical Reasons• Radio Network Layer Cause:

– Combining not supported– Combining Resources not available– Requested Tx Diversity Mode not supported– Number of DL codes not supported– Number of UL codes not supported– UL SF not supported– DL SF not supported– Dedicated Transport Channel Type not supported– Downlink Shared Channel Type not supported– Uplink Shared Channel Type not supported– CM not supported– DPC mode change not supported– Delayed Activation not supported

• Transport Layer Cause:– Transport Resources Unavailable

• Miscellaneous Cause:– O&M Intervention– Control processing overload– HW failure

Since RAS5.1 ED (CD2) following counters are incremented in addition to the above: M1005C14 SETUP_FAIL_RL_BTS_NOT_RESP – incremented in case BTS does not respond and supervision timer in RNC expires (to wait for response)

Since RAS5.1 ED (CD2) following counters are incremented in addition to the above: M1005C14 SETUP_FAIL_RL_BTS_NOT_RESP – incremented in case BTS does not respond and supervision timer in RNC expires (to wait for response)


RRC Access Phase



ALCAP:ERQ


[DCH] RRC: RRC Connection Setup Complete

L1 Synchronisation

Start TX/RXStart TX/RX


[FACH] RRC: RRC Connection Setup

NBAP: RL Setup Response


Request


Request

ALCAP:ECF

NBAP: Synchronisation Indication

Received RRC Connection Setup Complete –message triggers:(M1001C8) RRC_CONN_ACC_COMP and M1006C23 RRC_CONN_SETUP_COMPL_SENT

Received RRC Connection Setup Complete –message triggers:(M1001C8) RRC_CONN_ACC_COMP and M1006C23 RRC_CONN_SETUP_COMPL_SENT

The number RRC connection establishments by UEs that support: RFC2507 IP header compression - M1001C389 UE_SUPPORT_FOR_IPHC,release indicator release 4 - M1001C404 ACCESS_STRATUM_REL_IND_4, release indicator release 99 - M1001C405 ACCESS_STRATUM_REL_IND_99, GSM - M1001C406 UE_SUPPORT_GSMmulti-carrier CDMA - M1001C407 UE_SUPPORT_MULTICARRIER_CDMA,RX-TX time difference positioning capability type 2 - M1001C408 UE_RXTX_POSITION_CAPAB_2access stratum release indicator release 5 - M1001C552 ACCESS_STRATUM_REL_IND_5

The number RRC connection establishments by UEs that support: RFC2507 IP header compression - M1001C389 UE_SUPPORT_FOR_IPHC,release indicator release 4 - M1001C404 ACCESS_STRATUM_REL_IND_4, release indicator release 99 - M1001C405 ACCESS_STRATUM_REL_IND_99, GSM - M1001C406 UE_SUPPORT_GSMmulti-carrier CDMA - M1001C407 UE_SUPPORT_MULTICARRIER_CDMA,RX-TX time difference positioning capability type 2 - M1001C408 UE_RXTX_POSITION_CAPAB_2access stratum release indicator release 5 - M1001C552 ACCESS_STRATUM_REL_IND_5

The number of RRC connection establishments by UEs supporting HS-DSCH classes:1,2,3,4,5 or 6: M1001C548 UE_SUPP_HSDSCH_CLASS_1_67 or 8: M1001C549 UE_SUPP_HSDSCH_CLASS_7_89 or 10: M1001C550 UE_SUPP_HSDSCH_CLASS_9_10 11 or 12: M1001C551 UE_SUPP_HSDSCH_CLASS_11_12

The number of RRC connection establishments by UEs supporting HS-DSCH classes:1,2,3,4,5 or 6: M1001C548 UE_SUPP_HSDSCH_CLASS_1_67 or 8: M1001C549 UE_SUPP_HSDSCH_CLASS_7_89 or 10: M1001C550 UE_SUPP_HSDSCH_CLASS_9_10 11 or 12: M1001C551 UE_SUPP_HSDSCH_CLASS_11_12

The number of RRC connection establishments by UEs supporting Network Assisted GPS:

M1001C595 UE_SUPPORT_NW_AGPS

The number of RRC connection establishments by UEs supporting Network Assisted GPS:

M1001C595 UE_SUPPORT_NW_AGPS

RRC Performance

Access stratum release indicator release 6 – M1001C616 ACCESS_STRATUM_REL_IND_6The number of RRC connection establishments by UEs supporting E-DSCH Classes:M1001C610 UE_SUPP_EDCH_CATEGORY_1M1001C611 UE_SUPP_EDCH_CATEGORY_2M1001C612 UE_SUPP_EDCH_CATEGORY_3M1001C613 UE_SUPP_EDCH_CATEGORY_4M1001C614 UE_SUPP_EDCH_CATEGORY_5 M1001C615 UE_SUPP_EDCH_CATEGORY_6

Access stratum release indicator release 6 – M1001C616 ACCESS_STRATUM_REL_IND_6The number of RRC connection establishments by UEs supporting E-DSCH Classes:M1001C610 UE_SUPP_EDCH_CATEGORY_1M1001C611 UE_SUPP_EDCH_CATEGORY_2M1001C612 UE_SUPP_EDCH_CATEGORY_3M1001C613 UE_SUPP_EDCH_CATEGORY_4M1001C614 UE_SUPP_EDCH_CATEGORY_5 M1001C615 UE_SUPP_EDCH_CATEGORY_6





Agenda


RANAP: RAB Assignment Request


NBAP: RL Reconfiguration Prepare

NBAP: RL Reconfiguration Failure

AC to check to accept or reject RAB Assignment

Request


Request

RAB Establishment - CSIn case there is a failure to reconfigure the RL with the BTS one of the failure cause counters is updated:M1005C90 RECONF_ADD_FAIL_SRNC_OM_INTM1005C91 RECONF_ADD_FAIL_SRNC_ACTM1005C92 RECONF_ADD_FAIL_SRNC_HWRESM1005C93 RECONF_ADD_FAIL_SRNC_NOT_RESM1005C94 RECONF_ADD_FAIL_SRNC_BTS_NRM1005C95 RECONF_ADD_FAIL_SRNC_BTS_GR

In case there is a failure to reconfigure the RL with the BTS one of the failure cause counters is updated:M1005C90 RECONF_ADD_FAIL_SRNC_OM_INTM1005C91 RECONF_ADD_FAIL_SRNC_ACTM1005C92 RECONF_ADD_FAIL_SRNC_HWRESM1005C93 RECONF_ADD_FAIL_SRNC_NOT_RESM1005C94 RECONF_ADD_FAIL_SRNC_BTS_NRM1005C95 RECONF_ADD_FAIL_SRNC_BTS_GR

MGWMGW

RANAP: RAB Assignment Response:

Failure

RAB Establishment

In case the RAB assignment fails due to BTS, counters:M1003C13 RAB_ASS_NONSUCC_RNL and RNC_349a = M1001C81 RAB_STP_FAIL_CS_VOICE_BTS are updated – voice, RNC_356a = M1001C86 RAB_STP_FAIL_CS_CONV_BTS – CS data conversational

In case the RAB assignment fails due to BTS, counters:M1003C13 RAB_ASS_NONSUCC_RNL and RNC_349a = M1001C81 RAB_STP_FAIL_CS_VOICE_BTS are updated – voice, RNC_356a = M1001C86 RAB_STP_FAIL_CS_CONV_BTS – CS data conversational



In RAS05 and WN3.0 onwards:M1005C212 RECONF_ADD_FAIL_SRNC_RNLM1005C213 RECONF_ADD_FAIL_SRNC_TRLM1005C214 RECONF_ADD_FAIL_SRNC_PROTM1005C215 RECONF_ADD_FAIL_SRNC_MISC And in DRNCM1005C216 RECONF_ADD_FAIL_DRNC_RNLM1005C217 RECONF_ADD_FAIL_DRNC_TRLM1005C218 RECONF_ADD_FAIL_DRNC_PROTM1005C219 RECONF_ADD_FAIL_DRNC_MISC

In RAS05 and WN3.0 onwards:M1005C212 RECONF_ADD_FAIL_SRNC_RNLM1005C213 RECONF_ADD_FAIL_SRNC_TRLM1005C214 RECONF_ADD_FAIL_SRNC_PROTM1005C215 RECONF_ADD_FAIL_SRNC_MISC And in DRNCM1005C216 RECONF_ADD_FAIL_DRNC_RNLM1005C217 RECONF_ADD_FAIL_DRNC_TRLM1005C218 RECONF_ADD_FAIL_DRNC_PROTM1005C219 RECONF_ADD_FAIL_DRNC_MISC

In RAS5.1ED and RAS06 also counters:M1005C94 RECONF_ADD_FAIL_SRNC_BTS_NR and M1005C112 RECONF_ADD_FAIL_DRNC_BTS_NRare incremented in case BTS does not respond in time and response supervision timer expires in RNC







Request


Request

RAB Establishment - CS

RANAP: RAB Assignment Response:Success

ALCAP:ERQ

NBAP: RL Reconfiguration Ready

ALCAP:ECF

NBAP: Radio Link Reconfiguration Commit

[DCH] RRC: Radio Bearer Setup Complete

MGWMGW

[DCH] RRC: Radio Bearer Setup

RAB Establishment

M1001C604 RAB_SETUP_TIME_MAX_CS_VOICE

M1001C605 RAB_SETUP_TIME_MAX_CS_CONV

M1001C606 RAB_SETUP_TIME_MAX_CS_STR

The maximum CS RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment

M1001C604 RAB_SETUP_TIME_MAX_CS_VOICE

M1001C605 RAB_SETUP_TIME_MAX_CS_CONV

M1001C606 RAB_SETUP_TIME_MAX_CS_STR

The maximum CS RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment





Request


Request

RAB Establishment - PSSGSNSGSN

RAB Establishment




M1001C608 RAB_SETUP_TIME_MAX_PS_INTM1001C609 RAB_SETUP_TIME_MAX_PS_BACKGThe maximum PS Background/PS Interactive RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment.

M1001C608 RAB_SETUP_TIME_MAX_PS_INTM1001C609 RAB_SETUP_TIME_MAX_PS_BACKGThe maximum PS Background/PS Interactive RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment.





Request


Request


RAB Establishment



RANAP: RAB Assignment Response:Success[DCH] RRC: Measurement

Control

Direct Transfer : Activate PDP Context Accept[DCH] RRC: Measurement

ReportFrom DCH0/0

[DCH] RRC: Measurement Control

If RNC receives RRC: Measurement Report indicating event 4a when UE has been allocated DCH0/0 or in cell_PCH state RNC receives Cell Update indicating need for dedicated channel (i.e. cause UPLINK DATA TRANSMISSION), following counter is incremented:M1022C0 PS_SESSION_REQ_UL


AC to check to accept or reject Capacity request


RANAP: RAB Assignment RequestTriggers: M1003C8 RAB_ASS_REQ_BY_CNRNC_382a=M1001C72 RAB_STP_ATT_PS_BACKG, RNC_374a=M1001C71 RAB_STP_ATT_PS_INTER


[RACH] RRC: Cell UpdateFrom Cell_PCH

If the network wants to initiate any downlink activity and the UE is in Cell_PCH state, it needs to make a paging request. Counter M1022C1 PS_SESSION_REQ_DL is incremented when RNC receives RRC: CELL UPDATE message with the cause PAGING RESPONSE


NOTE: These counters are NOT incremented when resources (DMPG) are re-allocated due to: Direct switching from DCH xx/yy to HS-DSCH/E-DCH or HS-DSCH/DCH


In case of inter RNC HHO or SRNC relocation counter M1022C2 PS_SESSION_REQ_OTHER is incremented when RANAP: RELOCATION REQUEST message request is received Note: PS ISHO do not use relocation signaling as it is a normal PS call setup where the resources are reserved by UL/DL capacity request






Request


Request


RAB Establishment




Control


Report


In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and AC rejects the bit rate allocation and terminal stays at Cell_FACH or DCH0/0, following counters are incremented:M1022C9 PS_SETUP_FAIL_AC_INT M1022C10 PS_SETUP_FAIL_AC_BGR




Also PS call setup counters are incremented DEPENDING ON THE INITIALLY TRIED ALLOCATION M1022C3 PS_ATT_HSDSCH_EDCH_INT – HS-DSCH/E-DCH was requested by AC for Interactive classM1022C4 PS_ATT_HSDSCH_EDCH_BGR – HS-DSCH/E-DCH was requested by AC for Background classM1022C5 PS_ATT_HSDSCH_DCH_INT – HS-DSCH/DCH was requested by AC for Interactive classM1022C6 PS_ATT_HSDSCH_DCH_BGR – HS-DSCH/DCH was requested by AC for Background classM1022C7 PS_ATT_DCH_DCH_INT – DCH/DCH was requested by AC for Interactive classM1022C8 PS_ATT_DCH_DCH_BGR – DCH/DCH was requested by AC for Background class


Note: These counters are only incremented in case of initial allocation for terminal has been Cell_FACH (Cell_PCH) or DCH0/0.Successful Packet Call setup allocations and allocation attempts due to Incoming relocation or Inter-RNC HHOs are not counted separately.






Request


Request


RAB Establishment




Control


Report






In case there is a failure to reconfigure the RL SRB + 0/0 with the BTS one of the failure cause counters is updated:M1005C90 RECONF_ADD_FAIL_SRNC_OM_INTM1005C91 RECONF_ADD_FAIL_SRNC_ACTM1005C92 RECONF_ADD_FAIL_SRNC_HWRESM1005C93 RECONF_ADD_FAIL_SRNC_NOT_RESM1005C94 RECONF_ADD_FAIL_SRNC_BTS_NRM1005C95 RECONF_ADD_FAIL_SRNC_BTS_GR






In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:

M1005C212 RECONF_ADD_FAIL_SRNC_RNL M1005C213 RECONF_ADD_FAIL_SRNC_TRL M1005C214 RECONF_ADD_FAIL_SRNC_PROT M1005C215 RECONF_ADD_FAIL_SRNC_MISC

And in DRNC

M1005C216 RECONF_ADD_FAIL_DRNC_RNL M1005C217 RECONF_ADD_FAIL_DRNC_TRL M1005C218 RECONF_ADD_FAIL_DRNC_PROT M1005C219 RECONF_ADD_FAIL_DRNC_MISC

In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:

M1005C212 RECONF_ADD_FAIL_SRNC_RNL M1005C213 RECONF_ADD_FAIL_SRNC_TRL M1005C214 RECONF_ADD_FAIL_SRNC_PROT M1005C215 RECONF_ADD_FAIL_SRNC_MISC

And in DRNC








Request


Request


RAB Establishment




Control


Report












In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:M1005C220 RECONF_MOD_FAIL_SRNC_RNL M1005C221 RECONF_MOD_FAIL_SRNC_TRL M1005C222 RECONF_MOD_FAIL_SRNC_PROT M1005C223 RECONF_MOD_FAIL_SRNC_MISC

And in DRNC

M1005C224 RECONF_MOD_FAIL_DRNC_RNL M1005C225 RECONF_MOD_FAIL_DRNC_TRL M1005C226 RECONF_MOD_FAIL_DRNC_PROT M1005C227 RECONF_MOD_FAIL_DRNC_MISC

In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:M1005C220 RECONF_MOD_FAIL_SRNC_RNL M1005C221 RECONF_MOD_FAIL_SRNC_TRL M1005C222 RECONF_MOD_FAIL_SRNC_PROT M1005C223 RECONF_MOD_FAIL_SRNC_MISC

And in DRNC

M1005C224 RECONF_MOD_FAIL_DRNC_RNL M1005C225 RECONF_MOD_FAIL_DRNC_TRL M1005C226 RECONF_MOD_FAIL_DRNC_PROT M1005C227 RECONF_MOD_FAIL_DRNC_MISCIn RAS5.1ED and RAS06 also counters:M1005C100 RECONF_MOD_FAIL_SRNC_BTS_NR and M1005C118 RECONF_MOD_FAIL_DRNC_BTS_NRare incremented in case BTS does not respond in time and response supervision timer expires in RNC

In RAS5.1ED and RAS06 also counters:M1005C100 RECONF_MOD_FAIL_SRNC_BTS_NR and M1005C118 RECONF_MOD_FAIL_DRNC_BTS_NRare incremented in case BTS does not respond in time and response supervision timer expires in RNC





Request


Request


RAB Establishment




Control


Report










In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and BTS rejects the bit rate allocation and terminal stays at Cell_FACH or DCH0/0, following counters are incremented:M1022C11 PS_SETUP_FAIL_BTS_INT M1022C12 PS_SETUP_FAIL_BTS_BGR






Request


Request


RAB Establishment




Control


Report










In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and DMCU rejects the bit rate allocation and terminal stays at Cell_FACH or DCH0/0, following counters are incremented:M1022C13 PS_SETUP_FAIL_DMCU_INT M1022C14 PS_SETUP_FAIL_DMCU_BGR


DMCU reservationDMCU reservation





Request


Request


RAB Establishment




Control


Report




ALCAP:ERQ

ALCAP:ECF

NBAP: RL Reconfiguration Cancel







In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and CAC (or in general another Iub transmission failure) rejects the bit rate allocation and terminal stays at Cell_FACH or DCH0/0, following counters are incremented:M1022C15 PS_SETUP_FAIL_TRANS_INT M1022C16 PS_SETUP_FAIL_TRANS_BGR






Request


Request

RAB Establishment - PS

SGSNSGSN RAB Establishment




Control


Report




ALCAP:ERQ

ALCAP:ECF


[DCH] RRC: Radio Bearer Reconfiguration

Iu Release Request







In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and UE does not respond to the RB Reconfiguration message (or responds with failure) and terminal stays at Cell_FACH or DCH0/0, following counters are incremented:M1022C17 PS_SETUP_FAIL_UE_INT M1022C18 PS_SETUP_FAIL_UE_BGR

All other failures i.e. NOT AC, BTS, DMCU, TRANS or UE are counted as OTHER failures and following counters are incremented: M1022C17 PS_SETUP_FAIL_OTHER_INT M1022C18 PS_SETUP_FAIL_OTHER_BGR







Request


Request






Control


Report




ALCAP:ERQ

ALCAP:ECF



[DCH] RRC: Radio Bearer Reconfiguration Complete



After successful PS call setup (user plane resources are successfully setup) following counters are incremented DEPENDING ON THE INITIALLY TRIED ALLOCATION M1022C3 PS_ATT_HSDSCH_EDCH_INT – HS-DSCH/E-DCH was requested by AC for Interactive classM1022C4 PS_ATT_HSDSCH_EDCH_BGR – HS-DSCH/E-DCH was requested by AC for Background classM1022C5 PS_ATT_HSDSCH_DCH_INT – HS-DSCH/DCH was requested by AC for Interactive classM1022C6 PS_ATT_HSDSCH_DCH_BGR – HS-DSCH/DCH was requested by AC for Background classM1022C7 PS_ATT_DCH_DCH_INT – DCH/DCH was requested by AC for Interactive classM1022C8 PS_ATT_DCH_DCH_BGR – DCH/DCH was requested by AC for Background class








Request


Request






Control


Report




ALCAP:ERQ

ALCAP:ECF






After successful PS call setup (user plane resources are successfully setup) following counters are incremented DEPENDING ON THE SUCCESSFULL ALLOCATION M1022C21 HS_E_REQ_HS_E_ALLO_INT - HS-DSCH/E-DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C22 HS_E_REQ_HS_E_ALLO_BGR - HS-DSCH/E-DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic classM1022C23 HS_E_REQ_HS_D_ALLO_INT - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C24 HS_E_REQ_HS_D_ALLO_BGR - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic classM1022C25 HS_D_REQ_HS_D_ALLO_INT - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for INTERACTIVE traffic classM1022C26 HS_D_REQ_HS_D_ALLO_BGR - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for BACKGROUND traffic classM1022C27 HS_E_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C28 HS_E_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class

M1022C29 HS_D_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for INTERACTIVE traffic class

M1022C30 HS_D_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for BACKGROUND traffic class

M1022C31 D_D_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after DCH/DCH was initially requested for INTERACTIVE traffic class

M1022C32 D_D_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after DCH/DCH was initially requested for BACKGROUND traffic class














Request


Request



RANAP: RAB Assignment Response:

FailureIn case the RAB assignment fails due to BTS, counters:M1003C13 RAB_ASS_NONSUCC_RNL and RNC_370a=M1001C101 RAB_STP_FAIL_PS_DATA_STREAM_BTS are updated

In case the RAB assignment fails due to BTS, counters:M1003C13 RAB_ASS_NONSUCC_RNL and RNC_370a=M1001C101 RAB_STP_FAIL_PS_DATA_STREAM_BTS are updated

SGSN

SGSN

RAB EstablishmentRAB Establishment – PS Streaming (RAN04)



In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:M1005C212 RECONF_ADD_FAIL_SRNC_RNL M1005C213 RECONF_ADD_FAIL_SRNC_TRL M1005C214 RECONF_ADD_FAIL_SRNC_PROT M1005C215 RECONF_ADD_FAIL_SRNC_MISC

And in DRNC


In RAS05/WN3.0 the above failure counters are replaced by 3GPP specified ones and detailed causes behind the below counters are specified in 25.433 chapter 9.2.1.6:M1005C212 RECONF_ADD_FAIL_SRNC_RNL M1005C213 RECONF_ADD_FAIL_SRNC_TRL M1005C214 RECONF_ADD_FAIL_SRNC_PROT M1005C215 RECONF_ADD_FAIL_SRNC_MISC

And in DRNC

M1005C216 RECONF_ADD_FAIL_DRNC_RNL M1005C217 RECONF_ADD_FAIL_DRNC_TRL M1005C218 RECONF_ADD_FAIL_DRNC_PROT M1005C219 RECONF_ADD_FAIL_DRNC_MISCIn RAS5.1ED and RAS06 also counters:M1005C94 RECONF_ADD_FAIL_SRNC_BTS_NR and M1005C112 RECONF_ADD_FAIL_DRNC_BTS_NRare incremented in case BTS does not respond in time and response supervision timer expires in RNC







Request


Request


ALCAP:ERQ


ALCAP:ECF




SGSN

SGSN

RAB EstablishmentRAB Establishment – PS Streaming (RAN04)

M1001C607RAB_SETUP_TIME_MAX_PS_STRThe maximum PS Streaming RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment

M1001C607RAB_SETUP_TIME_MAX_PS_STRThe maximum PS Streaming RAB setup time defined as the amount of time that passes between an RANAP: RAB ASSIGNMENT REQUEST message and an RANAP: RAB ASSIGNMENT RESPONSE message during an RAB establishment





Agenda


HSDPA Activation, Cell DCH – HS-DSCHUE

RAB Establishment




[DCH] RRC: Measurement Report

From DCH0/0[RACH] RRC: Cell Update

From Cell_PCH











Measurement Report : e4a

RAB Establishment


The number of failed allocations for the HS-DSCH transport channel due to lack of radio resources for the UL DCH return channel for interactive or background class connections :M1002C401 REJ_HS_DSCH_RET_INT M1002C402 REJ_HS_DSCH_RET_BGR

After rejection the capacity request is sent back to the PS queue and the HS-DSCH channel type is not allowed for this capacity request any more.

The number of failed allocations for the HS-DSCH transport channel due to lack of radio resources for the UL DCH return channel for interactive or background class connections :M1002C401 REJ_HS_DSCH_RET_INT M1002C402 REJ_HS_DSCH_RET_BGR

After rejection the capacity request is sent back to the PS queue and the HS-DSCH channel type is not allowed for this capacity request any more.



When there is a request to set up HS-DSCH transport channel counter M1002C84 or C86 REQ_FOR_PS_INTERA/BACKG_UL_SRNC is incremented for the UL allocation

When there is a request to set up HS-DSCH transport channel counter M1002C84 or C86 REQ_FOR_PS_INTERA/BACKG_UL_SRNC is incremented for the UL allocation

In case of AC rejecting the capacity request for the UL return channel: then either M1002C92 REQ_PS_INTERA_REJ_UL_SRNC or M1002C93 REQ_PS_INTERA_REJ_DL_SRNC is incremented

In case of AC rejecting the capacity request for the UL return channel: then either M1002C92 REQ_PS_INTERA_REJ_UL_SRNC or M1002C93 REQ_PS_INTERA_REJ_DL_SRNC is incremented

Also the HS-DSCH return channel counter:M1002C401 REJ_HS_DSCH_RET_INT or M1002C402 REJ_HS_DSCH_RET_BGR is incremented

Also the HS-DSCH return channel counter:M1002C401 REJ_HS_DSCH_RET_INT or M1002C402 REJ_HS_DSCH_RET_BGR is incremented

In RAS05.1 with initial HS-DSCH Serving Cell Selection procedure the above mentioned rejection counters are incremented and then initial HS-DSCH Serving Cell Selection procedure is retried to the next candidate


The number of times when HS-DSCH downlink transport channel cannot be selected due to downlink power limits. This counter includes both interactive and background class connections. Counter is updated When HS-DSCH cannot be selected as downlink transport channel due to condition PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA. This counter is used only when HSDPA Static Resource Allocation is used. Counter M1002C521 or M1002C522 is updated along with this counter: M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)

The number of times when HS-DSCH downlink transport channel cannot be selected due to downlink power limits. This counter includes both interactive and background class connections. Counter is updated When HS-DSCH cannot be selected as downlink transport channel due to condition PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA. This counter is used only when HSDPA Static Resource Allocation is used. Counter M1002C521 or M1002C522 is updated along with this counter: M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)

If the user has AMR call on going and tries to setup HS-DSCH but that is rejected by AC then counter: M1002C403 REJ_HS_DSCH_AMR_BGR, M1002C483 REJ_HS_DSCH_AMR_INT is incremented together with C401/C402

If the user has AMR call on going and tries to setup HS-DSCH but that is rejected by AC then counter: M1002C403 REJ_HS_DSCH_AMR_BGR, M1002C483 REJ_HS_DSCH_AMR_INT is incremented together with C401/C402




RAB Establishment











HSDPA Activation, Cell DCH – HS-DSCH

Radio Link Reconfigure Failure

UE

NBAP: Radio Link Reconfigure Prepare


RAB Establishment












Radio Link Reconfigure Ready

UE



Radio Link Reconfiguration Cancel

RAB Establishment








DMCU reservationDMCU reservation






UE



Radio Link Reconfiguration Cancel

RAB Establishment












AAL2SIG:ECFAAL2SIG:ERQ


UE



Radio Link Reconfiguration CommitRRC: Radio Bearer Reconfiguration (DCH)

RRC: Radio Bearer Reconfiguration Failure (DCH)

RAB Establishment

















UE




RRC: Radio Bearer Reconfiguration Complete (DCH)

RAB Establishment





If at any time during the HS-DSCH setup the RNC decides to reject the HS-DSCH setup (including RNC internal transport), the counter: M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT orM1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR, is incremented

If at any time during the HS-DSCH setup the RNC decides to reject the HS-DSCH setup (including RNC internal transport), the counter: M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT orM1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR, is incremented



If either HS-DSCH or AMR DCH setup fails when the result would be HS-DSCH + AMR multi-RAB, one of the following counters is updated

M1002C404 SETUP_FAIL_HS_DSCH_AMR_BGR or

M1002C484 SETUP_FAIL_HS_DSCH_AMR_INT

One of the normal HS-DSCH setup failure counters (e.g. BTS, UE etc.) is also incremented in case HS-DSCH setup fails (on top of AMR) and in case AMR setup fails (on top of HS-DSCH) then the “normal” detailed AMR call setup failure counters is incremented.

The failure can happen in the following scenarios:

•The user has got AMR DCH active and HS-DSCH allocation is attempted unsuccessfull

•The user has got HS-DSCH allocated and AMR DCH is unsuccessfully established

•The user has got HS-DSCH + AMR multi-RAB active and the HS-DSCH serving cell change is unsuccessfully executed

If either HS-DSCH or AMR DCH setup fails when the result would be HS-DSCH + AMR multi-RAB, one of the following counters is updated

M1002C404 SETUP_FAIL_HS_DSCH_AMR_BGR or

M1002C484 SETUP_FAIL_HS_DSCH_AMR_INT

One of the normal HS-DSCH setup failure counters (e.g. BTS, UE etc.) is also incremented in case HS-DSCH setup fails (on top of AMR) and in case AMR setup fails (on top of HS-DSCH) then the “normal” detailed AMR call setup failure counters is incremented.

The failure can happen in the following scenarios:

•The user has got AMR DCH active and HS-DSCH allocation is attempted unsuccessfull

•The user has got HS-DSCH allocated and AMR DCH is unsuccessfully established

•The user has got HS-DSCH + AMR multi-RAB active and the HS-DSCH serving cell change is unsuccessfully executed

The number of HS-DSCH setup failures for incoming Inter-RNC HHO for background class connections. Also one of the basic HS-DSCH setup failure counters is updated along with this counter:

M1002C548 STP_F_HS_INTER_RNC_HHO_BGR,

M1002C547 STP_F_HS_INTER_RNC_HHO_INT

The number of HS-DSCH setup failures for incoming Inter-RNC HHO for background class connections. Also one of the basic HS-DSCH setup failure counters is updated along with this counter:







UE





Measurement Control

HS-DSCH: Capacity Request

HS-DSCH: Capacity Allocation

RAB Establishment



When the RNC has received an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE - after successful HS-DSCH MAC-d flow setup for interactive or background traffic class, counter: M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR , is incremented

When the RNC has received an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE - after successful HS-DSCH MAC-d flow setup for interactive or background traffic class, counter: M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR , is incrementedAC to check to

accept or reject Capacity request


Counter M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR , is also incremented in case of HS-DSCH Serving Cell ChangeCounter M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR , is also incremented in case of HS-DSCH Serving Cell Change

The sum of HS-DSCH MAC-d flow allocation durations in the SRNC for interactive or background class connections is updated with a 1-second sampling interval during the MAC-d flow allocation time:M1002C393 ALLO_DUR_HS_DSCH_FLOW_INT orM1002C397 ALLO_DUR_HS_DSCH_FLOW_BGR

The sum of HS-DSCH MAC-d flow allocation durations in the SRNC for interactive or background class connections is updated with a 1-second sampling interval during the MAC-d flow allocation time:M1002C393 ALLO_DUR_HS_DSCH_FLOW_INT orM1002C397 ALLO_DUR_HS_DSCH_FLOW_BGR

When the RNC has received an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE - after successful HS-DSCH return channel setup or bit rate modification, counter:M1002C386 ALLO_HS_DSCH_RET_64_INT, M1002C390 ALLO_HS_DSCH_RET_64_BGR , M1002C387 ALLO_HS_DSCH_RET_128_INT, M1002C391 ALLO_HS_DSCH_RET_128_BGR M1002C388 ALLO_HS_DSCH_RET_384_INT, M1002C392 ALLO_HS_DSCH_RET_384_BGR is incremented

When the RNC has received an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE - after successful HS-DSCH return channel setup or bit rate modification, counter:M1002C386 ALLO_HS_DSCH_RET_64_INT, M1002C390 ALLO_HS_DSCH_RET_64_BGR , M1002C387 ALLO_HS_DSCH_RET_128_INT, M1002C391 ALLO_HS_DSCH_RET_128_BGR M1002C388 ALLO_HS_DSCH_RET_384_INT, M1002C392 ALLO_HS_DSCH_RET_384_BGR is incremented

For HS-DSCH serving cell change:Counter M1002C393 ALLO_DUR_HS_DSCH_FLOW_INT orM1002C397 ALLO_DUR_HS_DSCH_FLOW_BGR, is stopped in old HS-DSCH serving cell and started in new HS-DSCH serving cell

For HS-DSCH serving cell change:Counter M1002C393 ALLO_DUR_HS_DSCH_FLOW_INT orM1002C397 ALLO_DUR_HS_DSCH_FLOW_BGR, is stopped in old HS-DSCH serving cell and started in new HS-DSCH serving cell

M1002C501 ALLO_HS_DSCH_RET_16_INT, M1002C502 ALLO_HS_DSCH_RET_16_BGR M1002C501 ALLO_HS_DSCH_RET_16_INT, M1002C502 ALLO_HS_DSCH_RET_16_BGR

The number of successful HS-DSCH allocations for incoming Inter-RNC HHO for interactive or background class connections. Also counter M1002C385 or M1002C389 is updated along with one of these counters. Counter is updated when the target-RNC of Inter-RNC HHO has successfully allocated resources for an HS-DSCH user plane and sends RANAP: RELOCATION REQUEST ACKNOWLEDGE to the core network:

M1002C545 ALLO_HS_INTER_RNC_HHO_INT,

M1002C546 ALLO_HS_INTER_RNC_HHO_BGR

The number of successful HS-DSCH allocations for incoming Inter-RNC HHO for interactive or background class connections. Also counter M1002C385 or M1002C389 is updated along with one of these counters. Counter is updated when the target-RNC of Inter-RNC HHO has successfully allocated resources for an HS-DSCH user plane and sends RANAP: RELOCATION REQUEST ACKNOWLEDGE to the core network:

M1002C545 ALLO_HS_INTER_RNC_HHO_INT,

M1002C546 ALLO_HS_INTER_RNC_HHO_BGR

In case one of following scenario is fulfilled:

The user has got AMR DCH active and HS-DSCH is successfully allocated

The user has got HS-DSCH allocated and AMR DCH is successfully established without dropping HS-DSCH to DCH 0/0

The user has got HS-DSCH + AMR multi-RAB active and the HS-DSCH serving cell change is executed

Counter : M1002C405 ALLO_HS_DSCH_AMR_BGR or M1002C485 ALLO_HS_DSCH_AMR_INT is incremented instead normal allocation counters

In case one of following scenario is fulfilled:

The user has got AMR DCH active and HS-DSCH is successfully allocated

The user has got HS-DSCH allocated and AMR DCH is successfully established without dropping HS-DSCH to DCH 0/0

The user has got HS-DSCH + AMR multi-RAB active and the HS-DSCH serving cell change is executed

Counter : M1002C405 ALLO_HS_DSCH_AMR_BGR or M1002C485 ALLO_HS_DSCH_AMR_INT is incremented instead normal allocation counters





UE





Measurement Control



RAB Establishment



The sum of 64, 128 or 384 kbps return channel allocation durations in the SRNC for interactive or background class connections is updated with a 1-second sampling interval during the DCH allocation time:M1002C394 ALLO_DUR_HS_DSCH_RET_64_INT, M1002C395 ALLO_DUR_HS_DSCH_RET_128_INT, M1002C396 ALLO_DUR_HS_DSCH_RET_384_INT,M1002C398 ALLO_DUR_HS_DSCH_RET_64_BGR, M1002C399 ALLO_DUR_HS_DSCH_RET_128_BGR, M1002C400 ALLO_DUR_HS_DSCH_RET_384_BGR

The sum of 64, 128 or 384 kbps return channel allocation durations in the SRNC for interactive or background class connections is updated with a 1-second sampling interval during the DCH allocation time:M1002C394 ALLO_DUR_HS_DSCH_RET_64_INT, M1002C395 ALLO_DUR_HS_DSCH_RET_128_INT, M1002C396 ALLO_DUR_HS_DSCH_RET_384_INT,M1002C398 ALLO_DUR_HS_DSCH_RET_64_BGR, M1002C399 ALLO_DUR_HS_DSCH_RET_128_BGR, M1002C400 ALLO_DUR_HS_DSCH_RET_384_BGR



In case of successful capacity allocation : M1002C142-M1002C157 ALLO_PS_INTERA_xx_yL_IN_SRNC or M1002C158-M1002C173 ALLO_PS_BACKG_xx_yL_IN_SRNC And allocation duration counters :M1002C206-M1002C221 DUR_PS_INTERA_xx_yL_IN_SRNC or M1002C222-M1002C237 DUR_PS_BACKG_xx_yL_IN_SRNC

In case of successful capacity allocation : M1002C142-M1002C157 ALLO_PS_INTERA_xx_yL_IN_SRNC or M1002C158-M1002C173 ALLO_PS_BACKG_xx_yL_IN_SRNC And allocation duration counters :M1002C206-M1002C221 DUR_PS_INTERA_xx_yL_IN_SRNC or M1002C222-M1002C237 DUR_PS_BACKG_xx_yL_IN_SRNC

M1002C503 ALLO_DUR_HS_DSCH_RET_16_INT, M1002C504 ALLO_DUR_HS_DSCH_RET_16_BGRM1002C503 ALLO_DUR_HS_DSCH_RET_16_INT, M1002C504 ALLO_DUR_HS_DSCH_RET_16_BGR

The number of successful channel switches made directly from the DCH xx/yy to the HS-DSCH for the interactive or background traffic class.M1002C507 SWI_DCH_TO_HS_DSCH_INT or M1002C508SWI_DCH_TO_HS_DSCH_BGR is incremented

The number of successful channel switches made directly from the DCH xx/yy to the HS-DSCH for the interactive or background traffic class.M1002C507 SWI_DCH_TO_HS_DSCH_INT or M1002C508SWI_DCH_TO_HS_DSCH_BGR is incremented





UE





Measurement Control



RAB Establishment













UE





Measurement Control



RAB Establishment



















HSDPA attempts can be calculated as below

RAB Establishment

RSCH_DCH_BGPS_ATT_HSD M1022C6TSCH_DCH_INPS_ATT_HSD M1022C5

GRSCH_EDCH_BPS_ATT_HSD M1022C4NTSCH_EDCH_IPS_ATT_HSD M1022C3 Attempts HSDPA RNC_926a

RSCH_DCH_BGPS_ATT_HSD M1022C6TSCH_DCH_INPS_ATT_HSD M1022C5

GRSCH_EDCH_BPS_ATT_HSD M1022C4NTSCH_EDCH_IPS_ATT_HSD M1022C3 Attempts HSDPA RNC_926a


RAS06 HSDPA Traffic Measurements

HS-DSCH HS-DSCH

DCH DCH M1002C409 REL_ALLO_HS_DSCH_MOB_DCH_INT

M1002C412 REL_ALLO_HS_DSCH_MOB_DCH_BGR

M1002C407 REL_ALLO_NORM_HS_DSCH_INT

M1002C410 REL_ALLO_NORM_HS_DSCH_BGR

M1002C408 REL_ALLO_OTH_FAIL_HSDSCH_INT

M1002C411REL_ALLO_OTH_FAIL_HSDSCH_BGR

M1002C479 REL_ALLO_RL_FAIL_HS_DSCH_INT

M1002C482REL_ALLO_RL_FAIL_HS_DSCH_BGR

M1002C477 REL_ALLO_HS_DSCH_OTH_DCH_INT

M1002C480 REL_ALLO_HS_DSCH_OTH_DCH_BGR

M1002C417 =

M1002C414SETUP_FAIL_IUB_MAC_D_INT

M1002C418SETUP_FAIL_64_IUB_HSDSCH_INT



M1002C417 SETUP_FAIL_IUB_HS_TOTAL_INT

M1002C425 SETUP_FAIL_IUB_HS_TOTAL_BGR

M1002C416 SETUP_FAL_RNC_HS_DSCH_INT

M1002C413 SETUP_FAIL_BTS_HS_DSCH_INT

M1002C424 SETUP_FAIL_BTS HS DSCH_BGR

M1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR

M1002C401 REJ_HS_DSCH_RET_INT

M1002C402 REJ_HS_DSCH_RET_BGR

CRCRM1002C385 ALLO_HS_DSCH_FLOW_INT

M1002C386 ALLO_HS_DSCH_RET_64_INT



M1002C389 ALLO_HS_DSCH_FLOW_BGR

M1002C390 ALLO_HS_DSCH_RET_64_BGR



Cell_FACH Cell_FACH

M1002C425 =

M1002C422SETUP_FAIL_IUB_MAC_D_BGR

M1002C426SETUP_FAIL_64_IUB_HSDSCH_BGR

M1002C427SETUP_FAIL_128_IUB_HSDSCH_BG

M1002C427SETUP_FAIL_384_IUB_HSDSCH_BG

M1002C475DCH_SEL_MAX_HSDPA_USERS_INT

M1002C476DCH_SEL_MAX_HSDPA_USERS_BGR

M1002C478 REL_ALLO_HS_DSCH_PRE_EMP_INT

M1002C481 REL_ALLO_HS_DSCH_PRE_EMP_BGR

Drops

“Normal”

Sub categories

Failures

OK

RAB Establishment

M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)



M1002C505 SETUP_FAIL_16_IUB_HSDSCH_INT

M1002C506 SETUP_FAIL_16_IUB_HSDSCH_BGR




RAS06 HSPA Traffic Measurements

Release due to RL Failure counters:



M1002C539 REL_EDCH_RL_FAIL_INT

M1002C540 REL_EDCH_RL_FAIL_BGR

Are incremented If:

• a radio link failure happens during HSDPA call

• uplink RLC unrecoverable error happens (Cell Update by UE)

• RLC-entity in RNC reports RLC protocol reset


RAS06 HSDPA Traffic Measurements

When either HS-DSCH or AMR DCH (or both) is released normally from AMR + HS-DSCH multi-RAB combination on of the following counters is incremented:

M1002C406 REL_ALLO_NORM_HSDSCH_AMR_BGR

M1002C486 REL_ALLO_NORM_HSDSCH_AMR_INT

This can happen e.g. in the following situations:

•HS-DSCH is released normally as the PS RAB is released by the CN

•Transition to DCH 0/0 is done e.g. due to mobility or inactivity reason

•AMR RAB is released

•Serving cell change is performed

Also the one of the normal HS-DSCH release (and AMR) counters is incremented:



When either HS-DSCH or AMR DCH (or both) is released normally from AMR + HS-DSCH multi-RAB combination on of the following counters is incremented:

M1002C406 REL_ALLO_NORM_HSDSCH_AMR_BGR

M1002C486 REL_ALLO_NORM_HSDSCH_AMR_INT

This can happen e.g. in the following situations:

•HS-DSCH is released normally as the PS RAB is released by the CN

•Transition to DCH 0/0 is done e.g. due to mobility or inactivity reason

•AMR RAB is released

•Serving cell change is performed

Also the one of the normal HS-DSCH release (and AMR) counters is incremented:



RAB Establishment

If HS-DSCH allocation is released due to condition PtxNonHSDPA>=PtxTargetHSDPA+PtxOffsetHSDPA, counter M1000C149 CELL_RESOURCE_SPARE_2 with value 1 for the serving HS-DSCH cell.This counter is updated only in case Static Resource Allocation is used

If HS-DSCH allocation is released due to condition PtxNonHSDPA>=PtxTargetHSDPA+PtxOffsetHSDPA, counter M1000C149 CELL_RESOURCE_SPARE_2 with value 1 for the serving HS-DSCH cell.This counter is updated only in case Static Resource Allocation is used





Agenda


HSUPA Call Establishment

HSUPA cannot be established without HSDPA so always all the counters in previous slides apply for HSDPA (UL return channel is HSUPA instead of R99)

RAB Establishment

UE RNCNode B

PDP EstablishedMeasurement Report : e4a

Cell Update










HSUPA Call Establishment RAB Establishment

UE RNCNode B


The number of E-DCH allocation failures due to max HSUPA simultaneous users in cell or BTS : M1002C515 UL_DCH_SEL_MAX_HSUPA_USR_INT, M1002C516 UL_DCH_SEL_MAX_HSUPA_USR_BGRIn case of SHO and the channel type selection ends up into DCH already with the first checked branch, the counter are updated only for the cell which caused the DCH selection

The number of E-DCH allocation failures due to max HSUPA simultaneous users in cell or BTS : M1002C515 UL_DCH_SEL_MAX_HSUPA_USR_INT, M1002C516 UL_DCH_SEL_MAX_HSUPA_USR_BGRIn case of SHO and the channel type selection ends up into DCH already with the first checked branch, the counter are updated only for the cell which caused the DCH selection



Cell Update

If the BTS reports that no HSUPA cannot be allocated then counter (each BTS sends the Radio Resource Measurement reports to RNC indicating the HSUPA availability): M1002C517 UL_DCH_SEL_BTS_HW_INT or M1002C518 UL_DCH_SEL_BTS_HW_BGR is incremented

If the BTS reports that no HSUPA cannot be allocated then counter (each BTS sends the Radio Resource Measurement reports to RNC indicating the HSUPA availability): M1002C517 UL_DCH_SEL_BTS_HW_INT or M1002C518 UL_DCH_SEL_BTS_HW_BGR is incremented

The number of times when HS-DSCH downlink transport channel cannot be selected due to downlink power limits. This counter includes both interactive and background class connections. Counter is updated When HS-DSCH cannot be selected as downlink transport channel due to condition PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA. These counters are used only when HSDPA Static Resource Allocation is used. Counter M1002C521 DL_DCH_SEL_HSDPA_POWER_INT or M1002C522 DL_DCH_SEL_HSDPA_POWER_BGR is updated along with counter: M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)

The number of times when HS-DSCH downlink transport channel cannot be selected due to downlink power limits. This counter includes both interactive and background class connections. Counter is updated When HS-DSCH cannot be selected as downlink transport channel due to condition PtxTotal>PtxTargetHSDPA or PtxNC>PtxTargetHSDPA. These counters are used only when HSDPA Static Resource Allocation is used. Counter M1002C521 DL_DCH_SEL_HSDPA_POWER_INT or M1002C522 DL_DCH_SEL_HSDPA_POWER_BGR is updated along with counter: M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)



Note: These counters are only incremented in case of initial allocation for terminal has been Cell_FACH (Cell_PCH) or DCH0/0. Successful Packet Call setup allocations and allocation attempts due to Incoming relocation or Inter-RNC HHOs are not counted separately.

Note: These counters are only incremented in case of initial allocation for terminal has been Cell_FACH (Cell_PCH) or DCH0/0. Successful Packet Call setup allocations and allocation attempts due to Incoming relocation or Inter-RNC HHOs are not counted separately.





UE RNCNode B


NBAP: Radio Link Reconfigure PrepareNBAP: Radio Link Reconfigure Failure


The number of E-DCH setup failures due to BTS for background and interactive class connections: M1002C526 SETUP_FAIL_EDCH_BTS_BGR, M1002C525 SETUP_FAIL_EDCH_BTS_INT

The counters count the E-DCH setup failures, that can happen in:

• channel type switching from non-E-DCH (FACH, DCH xx/yy, HS-DSCH/DCH) to HS-DSCH/E-DCH

• initial allocation of user plane from DCH 0/0 to HS-DSCH/E-DCH

• soft/softer handover E-DCH branch addition

Note that the BTS failure counters are updated only for the cells in which the BTS failure occurred

The number of E-DCH setup failures due to BTS for background and interactive class connections: M1002C526 SETUP_FAIL_EDCH_BTS_BGR, M1002C525 SETUP_FAIL_EDCH_BTS_INT





Note that the BTS failure counters are updated only for the cells in which the BTS failure occurred

AC to check to accept or reject Capacity

request

AC to check to accept or reject Capacity

request

AC to continue or cancel the E-DCH setup based on acceptable (or

not) AS


not) AS

If the final E-DCH RLS is not acceptable, the E-DCH allocations will be cancelled and a new channel type selection is performed counter: M1002C519 EDCH_ALLO_CANC_NA_AS_INT or M1002C520 EDCH_ALLO_CANC_NA_AS_BGR is incremented, note that this failure cannot happen during FACH -> HS-DSCH/E-DCH state transition










UE RNCNode B


NBAP: Radio Link Reconfigure PrepareNBAP: Radio Link Reconfigure Ready

NBAP: Radio Link Reconfiguration Cancel

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:REL

AAL2SIG:ERQ

AAL2SIG:ECF

The number of E-DCH setup failures due to transport for background and interactive class connections: M1002C528 SETUP_FAIL_EDCH_TRANS_BGR, M1002C527 SETUP_FAIL_EDCH_TRANS_INT





Note that the transmission failure counters are updated only for the cells in which the transmission failure occurred

The number of E-DCH setup failures due to transport for background and interactive class connections: M1002C528 SETUP_FAIL_EDCH_TRANS_BGR, M1002C527 SETUP_FAIL_EDCH_TRANS_INT





Note that the transmission failure counters are updated only for the cells in which the transmission failure occurred










not) AS


not) AS



UE RNCNode B


NBAP: Radio Link Reconfigure PrepareRadio Link Reconfigure Ready


AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF


The number of E-DCH setup failures due to UE for background and interactive class connections: M1002C524 SETUP_FAIL_EDCH_UE_BGR, M1002C523 SETUP_FAIL_EDCH_UE_INT





Note that the UE failure counters are updated for all the cells in AS

The number of E-DCH setup failures due to UE for background and interactive class connections: M1002C524 SETUP_FAIL_EDCH_UE_BGR, M1002C523 SETUP_FAIL_EDCH_UE_INT





Note that the UE failure counters are updated for all the cells in AS











UE RNCNode B




AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF


The number of E-DCH setup failures for interactive class connections due to reasons not covered by the other failure counters, for example due to RNC internal failures: M1002C530 SETUP_FAIL_EDCH_OTHER_BGR, M1002C529 SETUP_FAIL_EDCH_OTHER_INT

The number of E-DCH setup failures for interactive class connections due to reasons not covered by the other failure counters, for example due to RNC internal failures: M1002C530 SETUP_FAIL_EDCH_OTHER_BGR, M1002C529 SETUP_FAIL_EDCH_OTHER_INT

The number of E-DCH setup failures for incoming Inter-RNC HHO for interactive class connections. Also one of the basic E-DCH setup failure counters is updated along with this counter: M1002C552STP_F_ED_INTER_RNC_HHO_BGR, M1002C551 STP_F_ED_INTER_RNC_HHO_INT

The number of E-DCH setup failures for incoming Inter-RNC HHO for interactive class connections. Also one of the basic E-DCH setup failure counters is updated along with this counter: M1002C552STP_F_ED_INTER_RNC_HHO_BGR, M1002C551 STP_F_ED_INTER_RNC_HHO_INT

All other failures i.e. NOT AC, BTS, DMCU, TRANS or UE causing terminal to stay at Cell_FACH or DCH0/0 are counted as OTHER failures and following counters are incremented: M1022C17 PS_SETUP_FAIL_OTHER_INT M1022C18 PS_SETUP_FAIL_OTHER_BGR

All other failures i.e. NOT AC, BTS, DMCU, TRANS or UE causing terminal to stay at Cell_FACH or DCH0/0 are counted as OTHER failures and following counters are incremented: M1022C17 PS_SETUP_FAIL_OTHER_INT M1022C18 PS_SETUP_FAIL_OTHER_BGR








HSUPA Call Establishment UE RNCNode B




AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF


The sum of E-DCH allocation durations for interactive class connections (1s sampling interval): M1002C533 ALLO_DUR_EDCH_INT, M1002C534 ALLO_DUR_EDCH_BGRThe sum of E-DCH allocation durations for interactive class connections (1s sampling interval): M1002C533 ALLO_DUR_EDCH_INT, M1002C534 ALLO_DUR_EDCH_BGR

The number of successful E-DCH allocations for interactive class connections, updated when RNC receives an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE after a successful E-DCH setup or upgrade from the DCH. The counter is updated also when the RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message after a successful addition of a cell into the E-DCH active set: M1002C531 ALLO_SUCCESS_EDCH_INT, M1002C532 ALLO_SUCCESS_EDCH_BGR

The number of successful E-DCH allocations for interactive class connections, updated when RNC receives an RRC: RADIO BEARER RECONFIGURATION COMPLETE message from the UE after a successful E-DCH setup or upgrade from the DCH. The counter is updated also when the RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message after a successful addition of a cell into the E-DCH active set: M1002C531 ALLO_SUCCESS_EDCH_INT, M1002C532 ALLO_SUCCESS_EDCH_BGR

The number of successful E-DCH allocations for incoming Inter-RNC HHO for background or interactive class connections. M1002C532 or M1002C531 is updated along with one these counters:M1002C550 ALLO_ED_INTER_RNC_HHO_BGR, M1002C549 ALLO_ED_INTER_RNC_HHO_INT

The number of successful E-DCH allocations for incoming Inter-RNC HHO for background or interactive class connections. M1002C532 or M1002C531 is updated along with one these counters:M1002C550 ALLO_ED_INTER_RNC_HHO_BGR, M1002C549 ALLO_ED_INTER_RNC_HHO_INT















UE RNCNode B




AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF


During the HSUPA call following counters measure the BTS HW limitation, counters are incremented with 1s periods (based on the Radio Resource Measurement reports from BTSs)M1000C268 BTS_HSUPA_HW_NOT_LIMITED_DUR : if the latest HW resource status is HSUPA configured and free EDCH capacity M1000C269 BTS_HSUPA_HW_LIMITED_DUR: if the latest HW resource status is HSUPA configured but HW limited M1000C270 BTS_HSUPA_NO_HW_CAPA_DUR : if the latest HW resource status is HSUPA configured and no free EDCH capacity

During the HSUPA call following counters measure the BTS HW limitation, counters are incremented with 1s periods (based on the Radio Resource Measurement reports from BTSs)M1000C268 BTS_HSUPA_HW_NOT_LIMITED_DUR : if the latest HW resource status is HSUPA configured and free EDCH capacity M1000C269 BTS_HSUPA_HW_LIMITED_DUR: if the latest HW resource status is HSUPA configured but HW limited M1000C270 BTS_HSUPA_NO_HW_CAPA_DUR : if the latest HW resource status is HSUPA configured and no free EDCH capacity

HSUPA Call Established

If there is AMR/E-DCH/HS-DSCH Multi-RAB created by:• The user has got E-DCH active and a successful AMR

allocation is performed so that NRT RAB stays mapped to E-DCH

• The user has got AMR active and a successful E-DCH allocation is successfully performed (can be initial allocation, soft handover branch addition or channel type switch)

Counter M1002C543 AMR_EDCH_ALLO is incremented

If there is AMR/E-DCH/HS-DSCH Multi-RAB created by:• The user has got E-DCH active and a successful AMR

allocation is performed so that NRT RAB stays mapped to E-DCH

• The user has got AMR active and a successful E-DCH allocation is successfully performed (can be initial allocation, soft handover branch addition or channel type switch)

Counter M1002C543 AMR_EDCH_ALLO is incremented



UE RNCNode B




AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF

AAL2SIG:ERQ

AAL2SIG:ECF


RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame delay build up or RNC HW overload. Following counters count those messages:M1022C69 IUB_DELAY_CC_DELAY_IND M1022C70 HW_OVERL_CC_DELAY_IND

RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame delay build up or RNC HW overload. Following counters count those messages:M1022C69 IUB_DELAY_CC_DELAY_IND M1022C70 HW_OVERL_CC_DELAY_IND

HSUPA Call Established

RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame frame loss due to Iub delay, traffic loss or RNC HW overload. Following counters count those messages:M1022C71 IUB_LOSS_CC_FRAME_LOSS_IND M1022C72 IUB_DELAY_CC_FRAME_LOSS_IND M1022C73 HW_OVERL_CC_FRAME_LOSS_IND

RNC sends HSUPA Congestion Control indications to the BTS based on detected received Iub FP frame frame loss due to Iub delay, traffic loss or RNC HW overload. Following counters count those messages:M1022C71 IUB_LOSS_CC_FRAME_LOSS_IND M1022C72 IUB_DELAY_CC_FRAME_LOSS_IND M1022C73 HW_OVERL_CC_FRAME_LOSS_IND

RNC counts the missed E-DCH frames and delayed E-DCH frames and successfully received E-DCH FP frames and following counters are incremented:M1022C75 MISSED_EDCH_FRAMESM1022C76 DELAYED_EDCH_FRAMES M1022C77 SUCC_REC_EDCH_FRAMES

RNC counts the missed E-DCH frames and delayed E-DCH frames and successfully received E-DCH FP frames and following counters are incremented:M1022C75 MISSED_EDCH_FRAMESM1022C76 DELAYED_EDCH_FRAMES M1022C77 SUCC_REC_EDCH_FRAMES



_BGRDSCH)_EDCHPS_ATT_HS_ M1022C4NTSCH_EDCH_IPS_ATT_HSD M1022C3 Attempts HSUPA RNC_928a _BGRDSCH)_EDCHPS_ATT_HS_ M1022C4NTSCH_EDCH_IPS_ATT_HSD M1022C3 Attempts HSUPA RNC_928a

INTL_EDCH_UE_ SETUP_FAIM1002C523BGRL_EDCH_UE_ SETUP_FAIM1002C524

NS_INTL_EDCH_TRA SETUP_FAIM1002C527NS_BGRL_EDCH_TRA SETUP_FAIM1002C528

ER_INTL_EDCH_OTH SETUP_FAIM1002C529ER_BGRL_EDCH_OTH SETUP_FAIM1002C530

_INTL_EDCH_BTS SETUP_FAIM1002C525_BGRL_EDCH_BTS SETUP_FAIM1002C526

R_BTS_HW_BGUL_DCH_SEL M1002C518T_BTS_HW_INUL_DCH_SEL M1002C517

_USR_INT_MAX_HSUPAUL_DCH_SEL M1002C515_USR_BGR_MAX_HSUPAUL_DCH_SEL M1002C516

_INTCANC_NA_ASEDCH_ALLO_ M1002C519_BGRCANC_NA_ASEDCH_ALLO_ M1002C520

RSS_EDCH_BGALLO_SUCCE M1002C532TSS_EDCH_INALLO_SUCCE M1002C531

s SelectionDCH-E RNC_923a

INTL_EDCH_UE_ SETUP_FAIM1002C523BGRL_EDCH_UE_ SETUP_FAIM1002C524

NS_INTL_EDCH_TRA SETUP_FAIM1002C527NS_BGRL_EDCH_TRA SETUP_FAIM1002C528

ER_INTL_EDCH_OTH SETUP_FAIM1002C529ER_BGRL_EDCH_OTH SETUP_FAIM1002C530

_INTL_EDCH_BTS SETUP_FAIM1002C525_BGRL_EDCH_BTS SETUP_FAIM1002C526

R_BTS_HW_BGUL_DCH_SEL M1002C518T_BTS_HW_INUL_DCH_SEL M1002C517

_USR_INT_MAX_HSUPAUL_DCH_SEL M1002C515_USR_BGR_MAX_HSUPAUL_DCH_SEL M1002C516

_INTCANC_NA_ASEDCH_ALLO_ M1002C519_BGRCANC_NA_ASEDCH_ALLO_ M1002C520

RSS_EDCH_BGALLO_SUCCE M1002C532TSS_EDCH_INALLO_SUCCE M1002C531

s SelectionDCH-E RNC_923a

TEDCH_UE_INETUP_FAIL_ 3 SM1002C52+BGRL_EDCH_UE_ SETUP_FAI M1002C524+

NS_INTL_EDCH_TRA SETUP_FAIM1002C527NS_BGRL_EDCH_TRA SETUP_FAI M1002C528+

ER_INTL_EDCH_OTH SETUP_FAI M1002C529+ER_BGRL_EDCH_OTH SETUP_FAI M1002C530+

_INTL_EDCH_BTS SETUP_FAI M1002C525+_BGRL_EDCH_BTS SETUP_FAI M1002C526+

R_BTS_HW_BGUL_DCH_SEL M1002C518+T_BTS_HW_INUL_DCH_SEL M1002C517+

_USR_INT_MAX_HSUPAUL_DCH_SEL M1002C515+_USR_BGR_MAX_HSUPAUL_DCH_SEL M1002C516+

_INTCANC_NA_ASEDCH_ALLO_ M1002C519+_BGRCANC_NA_ASEDCH_ALLO_ M1002C520+

RSS_EDCH_BGALLO_SUCCE M1002C532+TSS_EDCH_INALLO_SUCCE M1002C531


Traffic NRT RT fority Accessibil Resource HSUPA RNC_913a

TEDCH_UE_INETUP_FAIL_ 3 SM1002C52+BGRL_EDCH_UE_ SETUP_FAI M1002C524+

NS_INTL_EDCH_TRA SETUP_FAIM1002C527NS_BGRL_EDCH_TRA SETUP_FAI M1002C528+

ER_INTL_EDCH_OTH SETUP_FAI M1002C529+ER_BGRL_EDCH_OTH SETUP_FAI M1002C530+

_INTL_EDCH_BTS SETUP_FAI M1002C525+_BGRL_EDCH_BTS SETUP_FAI M1002C526+

R_BTS_HW_BGUL_DCH_SEL M1002C518+T_BTS_HW_INUL_DCH_SEL M1002C517+

_USR_INT_MAX_HSUPAUL_DCH_SEL M1002C515+_USR_BGR_MAX_HSUPAUL_DCH_SEL M1002C516+

_INTCANC_NA_ASEDCH_ALLO_ M1002C519+_BGRCANC_NA_ASEDCH_ALLO_ M1002C520+



Traffic NRT RT fority Accessibil Resource HSUPA RNC_913a


RAS06 HSUPA Traffic Measurements

HS-DSCH

+

E-DCH

HS-DSCH

+

E-DCH

HS-DSCH/DCH

+

DCH

HS-DSCH/DCH

+

DCH

M1002C409 REL_ALLO_HS_DSCH_MOB_DCH_INT

M1002C412REL_ALLO_HS_DSCH_MOB_DCH_BGR


M1002C410REL_ALLO_NORM_HS_DSCH_BGR

M1002C408 REL_ALLO_OTH_FAIL_HSDSCH_INT

M1002C411REL_ALLO_OTH_FAIL_HSDSCH_BGR



M1002C477 REL_ALLO_HS_DSCH_OTH_DCH_INT

M1002C480REL_ALLO_HS_DSCH_OTH_DCH_BGR

CRCR

Cell_FACH Cell_FACH M1002C475DCH_SEL_MAX_HSDPA_USERS_INT

M1002C476DCH_SEL_MAX_HSDPA_USERS_BGR

M1002C478 REL_ALLO_HS_DSCH_PRE_EMP_INT

M1002C481 REL_ALLO_HS_DSCH_PRE_EMP_BGR

Drops

“Normal”

Release Sub Categories

Failures

OK

M1000C144 CELL_RESOURCE_SPARE_1 (DL DCH SELECTED DUE TO HSDPA POWER)

M1002C531 ALLO_SUCCESS_EDCH_INTM1002C532 ALLO_SUCCESS_EDCH_BGR

M1002C548 STP_F_HS_INTER_RNC_HHO_BGR


M1002C552 STP_F_ED_INTER_RNC_HHO_BGR

M1002C551 STP_F_ED_INTER_RNC_HHO_INT

M1002C515 UL_DCH_SEL_MAX_HSUPA_USR_INT

M1002C516 UL_DCH_SEL_MAX_HSUPA_USR_BGR

M1002C517 UL_DCH_SEL_BTS_HW_INT

M1002C518 UL_DCH_SEL_BTS_HW_BGR

M1002C519 EDCH_ALLO_CANC_NA_AS_INT

M1002C520 EDCH_ALLO_CANC_NA_AS_BGR

M1002C550 ALLO_ED_INTER_RNC_HHO_BGR

M1002C549 ALLO_ED_INTER_RNC_HHO_INT

M1002C526 SETUP_FAIL_EDCH_BTS_BGR

M1002C525 SETUP_FAIL_EDCH_BTS_INT

M1002C528 SETUP_FAIL_EDCH_TRANS_BGR

M1002C527 SETUP_FAIL_EDCH_TRANS_INT

M1002C524 SETUP_FAIL_EDCH_UE_BGR

M1002C523 SETUP_FAIL_EDCH_UE_INT

M1002C530 SETUP_FAIL_EDCH_OTHER_BGR

M1002C529 SETUP_FAIL_EDCH_OTHER_INT

M1002C536 REL_EDCH_NORM_BGR

M1002C535 REL_EDCH_NORM_INT

M1002C537 REL_EDCH_HSDSCH_SCC_INT

M1002C538 REL_EDCH_HSDSCH_SCC_BGR

M1002C541 REL_EDCH_OTH_FAIL_INT

M1002C542 REL_EDCH_OTH_FAIL_BGR

M1002C539 REL_EDCH_RL_FAIL_INT

M1002C540 REL_EDCH_RL_FAIL_BGR

“Normal”

Release Sub Category





Agenda


Channel Type Switching for HSPA

In RAS06 it is possible that DCH x/y transport channel is reconfigured to HS-DSCH without going through DCH 0/0 configuration

When DCH x/y to HS-DSCH switch is done successfully, BRM shall update counter SWI_DCH_TO_HS_DSCH_INT or SWI_DCH_TO_HS_DSCH_BGR depending on the traffic class

One of the counters below is updated by value 1 only for the serving cell

M1002C507 SWI_DCH_TO_HS_DSCH_INT

M1002C508 SWI_DCH_TO_HS_DSCH_BGR

M1002C507 SWI_DCH_TO_HS_DSCH_INT

M1002C508 SWI_DCH_TO_HS_DSCH_BGR




Request


Request

SGSNSGSN




Control


Report




ALCAP:ERQ

ALCAP:ECF








If HSPA Capable terminal initiates RRC Connection Request to a cell that does not support HSPA (i.e. not part of HSDPA layer) then RRC Connection Re-Direction is used to move that terminal to cell/layer (same sector id) that supports HSPA

And visa versa i.e. non HSPA terminals will be moved from HSPA layer using RRC Connection re-direction procedure

Also HSPA load sharing can be activated between HSPA capable layers


UEUE Cell 1Cell 1 RNCRNC

ALCAP:ERQ


[DCH] RRC: RRC Connection Setup Complete

L1 Synchronisation



[FACH] RRC: RRC Connection Setup


AC decides to Direct the RRC Connection to

another frequency

AC decides to Direct the RRC Connection to

another frequency

ALCAP:ECF

NBAP: Synchronisation Indication

Node BNode B

Cell 2Cell 2


HSDPA capable terminals will be moved to the HSDPA layer from non-HSDPA layer: M1002C509 DCH_ALLO_NON_HSPA_TO_HSPA

The non-HSDPA capable termnals will be moved from HSDPA layer to non HSDPA layer: M1002C510 DCH_ALLO_HSPA_TO_NON_HSPA

HSDPA capable terminals will be moved to the HSDPA layer from non-HSDPA layer: M1002C509 DCH_ALLO_NON_HSPA_TO_HSPA

The non-HSDPA capable termnals will be moved from HSDPA layer to non HSDPA layer: M1002C510 DCH_ALLO_HSPA_TO_NON_HSPA

The number of DCH allocations for signaling link from the HSPA layer to the HSPA layer due to the Directed RRC Connection Setup procedure for the HSPA layer. M1002C511 DCH_ALLO_HSPA_TO_HSPA

The number of DCH allocations for signaling link from the HSPA layer to the HSPA layer due to the Directed RRC Connection Setup procedure for the HSPA layer. M1002C511 DCH_ALLO_HSPA_TO_HSPA



The FACH to DCH state transitions between HSPA and non-HSPA layer between HSPA layers are counted by counters below

UE RNC SGSNNode B

RRC: Measurement Control (DCH)

RRC: Radio Bearer Reconfiguration (FACH)

Data Flow


UE in Cell_DCH

RRC: Measurement Report (RACH) : e4a

RNC receives capacity request from UE or

internally from MAC-c

ALCAP:ERQ

ALCAP:ECF



The number of FACH to DCH state transitions directing the UE from the non-HSPA layer to the HSPA layer.M1002C512 FACH_DCH_NON_HSPA_TO_HSPAThe number of FACH to DCH state transitions directing the UE from the HSPA layer to the non-HSPA layer.M1002C513 FACH_DCH_HSPA_TO_NON_HSPAThe number of FACH to DCH state transitions directing the UE from one HSPA layer to another HSPA layer.M1002C514 FACH_DCH_HSPA_TO_HSPA

The number of FACH to DCH state transitions directing the UE from the non-HSPA layer to the HSPA layer.M1002C512 FACH_DCH_NON_HSPA_TO_HSPAThe number of FACH to DCH state transitions directing the UE from the HSPA layer to the non-HSPA layer.M1002C513 FACH_DCH_HSPA_TO_NON_HSPAThe number of FACH to DCH state transitions directing the UE from one HSPA layer to another HSPA layer.M1002C514 FACH_DCH_HSPA_TO_HSPA



After the channel switch is successfully completed, counters M1022C33-M1022C44 are updated after RRC: RADIO BEARER RECONFIGURATION COMPLETE message is received from RNCThe channel switch means any of the following scenarios• HS-DSCH/E-DCH <-> HS-DSCH/DCH• HS-DSCH/E-DCH <-> DCH/DCH (>0/0)• HS-DSCH/DCH <-> DCH/DCH (>0/0)

After the channel switch is successfully completed, counters M1022C33-M1022C44 are updated after RRC: RADIO BEARER RECONFIGURATION COMPLETE message is received from RNCThe channel switch means any of the following scenarios• HS-DSCH/E-DCH <-> HS-DSCH/DCH• HS-DSCH/E-DCH <-> DCH/DCH (>0/0)• HS-DSCH/DCH <-> DCH/DCH (>0/0)

UE RNCNode B

RRC: Radio Bearer Reconfiguration (DCH)


RL Modification

Iub Modification

M1022C33 PS_SWI_HS_E_TO_HS_D_INT : Channel switch from HS-DSCH/E-DCH to HS-DSCH/DCHM1022C34 PS_SWI_HS_E_TO_HS_D_BGR : Channel switch from HS-DSCH/E-DCH to HS-DSCH/DCHM1022C35 PS_SWI_HS_E_TO_D_D_INT : Channel switch from HS-DSCH/E-DCH to DCH/DCHM1022C36 PS_SWI_HS_E_TO_D_D_BGR : Channel switch from HS-DSCH/E-DCH to DCH/DCHM1022C37 PS_SWI_HS_D_TO_D_D_INT : Channel switch from HS-DSCH/DCH to DCH/DCHM1022C38 PS_SWI_HS_D_TO_D_D_BGR : Channel switch from HS-DSCH/DCH to DCH/DCHM1022C39 PS_SWI_HS_D_TO_HS_E_INT : Channel switch from HS-DSCH/DCH to HS-DSCH/E-DCHM1022C40 PS_SWI_HS_D_TO_HS_E_BGR : Channel switch from HS-DSCH/DCH to HS-DSCH/E-DCHM1022C41 PS_SWI_D_D_TO_HS_D_INT : Channel switch from DCH/DCH to HS-DSCH/DCHM1022C42 PS_SWI_D_D_TO_HS_D_BGR : Channel switch from DCH/DCH to HS-DSCH/DCHM1022C43 PS_SWI_D_D_TO_HS_E_INT : Channel switch from DCH/DCH to HS-DSCH/E-DCHM1022C44 PS_SWI_D_D_TO_HS_E_BGR : Channel switch from DCH/DCH to HS-DSCH/E-DCH

M1022C33 PS_SWI_HS_E_TO_HS_D_INT : Channel switch from HS-DSCH/E-DCH to HS-DSCH/DCHM1022C34 PS_SWI_HS_E_TO_HS_D_BGR : Channel switch from HS-DSCH/E-DCH to HS-DSCH/DCHM1022C35 PS_SWI_HS_E_TO_D_D_INT : Channel switch from HS-DSCH/E-DCH to DCH/DCHM1022C36 PS_SWI_HS_E_TO_D_D_BGR : Channel switch from HS-DSCH/E-DCH to DCH/DCHM1022C37 PS_SWI_HS_D_TO_D_D_INT : Channel switch from HS-DSCH/DCH to DCH/DCHM1022C38 PS_SWI_HS_D_TO_D_D_BGR : Channel switch from HS-DSCH/DCH to DCH/DCHM1022C39 PS_SWI_HS_D_TO_HS_E_INT : Channel switch from HS-DSCH/DCH to HS-DSCH/E-DCHM1022C40 PS_SWI_HS_D_TO_HS_E_BGR : Channel switch from HS-DSCH/DCH to HS-DSCH/E-DCHM1022C41 PS_SWI_D_D_TO_HS_D_INT : Channel switch from DCH/DCH to HS-DSCH/DCHM1022C42 PS_SWI_D_D_TO_HS_D_BGR : Channel switch from DCH/DCH to HS-DSCH/DCHM1022C43 PS_SWI_D_D_TO_HS_E_INT : Channel switch from DCH/DCH to HS-DSCH/E-DCHM1022C44 PS_SWI_D_D_TO_HS_E_BGR : Channel switch from DCH/DCH to HS-DSCH/E-DCH





Agenda


RAS06 Packet Call Setup Statistics

HS-DSCH

+

E-DCH

HS-DSCH

+

E-DCH

CRCR

M1022C3 PS_ATT_HSDSCH_EDCH_INT : HS-DSCH/E-DCH was requested by AC for Interactive class

M1022C4 PS_ATT_HSDSCH_EDCH_BGR : HS-DSCH/E-DCH was requested by AC for Background class

M1022C5 PS_ATT_HSDSCH_DCH_INT : HS-DSCH/DCH was requested by AC for Interactive class

M1022C6 PS_ATT_HSDSCH_DCH_BGR : HS-DSCH/DCH was requested by AC for Background class

M1022C7 PS_ATT_DCH_DCH_INT : DCH/DCH was requested by AC for Interactive class

M1022C8 PS_ATT_DCH_DCH_BGR : DCH/DCH was requested by AC for Background class

M1022C27 HS_E_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C28 HS_E_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class

M1022C29 HS_D_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for INTERACTIVE traffic classM1022C30 HS_D_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for BACKGROUND traffic class

M1022C31 D_D_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after DCH/DCH was initially requested for INTERACTIVE traffic classM1022C32 D_D_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after DCH/DCH was initially requested for BACKGROUND traffic class

M1022C11 PS_SETUP_FAIL_BTS_INT M1022C12 PS_SETUP_FAIL_BTS_BGR

M1022C9 PS_SETUP_FAIL_AC_INT M1022C10 PS_SETUP_FAIL_AC_BGR

M1022C13 PS_SETUP_FAIL_DMCU_INT M1022C14 PS_SETUP_FAIL_DMCU_BGR

M1022C15 PS_SETUP_FAIL_TRANS_INT M1022C16 PS_SETUP_FAIL_TRANS_BGR

M1022C17 PS_SETUP_FAIL_UE_INT M1022C18 PS_SETUP_FAIL_UE_BGR

M1022C19 PS_SETUP_FAIL_OTHER_INT M1022C20 PS_SETUP_FAIL_OTHER_BGR

Successful Setups

Setup Failures

INCREMENTED ONLY INCASE THE FAILURE LEADS TO TERMINAL STAYING @ CELL_FACH OR DCH0/0



M_D_D_BGRPS_REL_NOR M1022C50+M_D_D_INTPS_REL_NOR M1022C49+

M_HS_D_BGRPS_REL_NOR M1022C48+M_HS_D_INTPS_REL_NOR M1022C47+

M_HS_E_BGRPS_REL_NOR M1022C46+M_HS_E_INTPS_REL_NOR M1022C45+

BGR_FAIL_D_D_PS_REL_OTH M1022C68+INT_FAIL_D_D_PS_REL_OTH M1022C67+

_BGR_FAIL_HS_DPS_REL_OTH M1022C66+_INT_FAIL_HS_DPS_REL_OTH M1022C65+

_BGR_FAIL_HS_EPS_REL_OTH M1022C64+_INT_FAIL_HS_EPS_REL_OTH M1022C63+

GRFAIL_D_D_BPS_REL_RL_ M1022C62+NTFAIL_D_D_IPS_REL_RL_ M1022C61+

BGRFAIL_HS_D_PS_REL_RL_ M1022C60+INTFAIL_HS_D_PS_REL_RL_ M1022C59+

BGRFAIL_HS_E_PS_REL_RL_ M1022C58+INTFAIL_HS_E_PS_REL_RL_ M1022C57BGR_FAIL_D_D_PS_REL_OTH M1022C68+INT_FAIL_D_D_PS_REL_OTH M1022C67+




BGRFAIL_HS_D_PS_REL_RL_ M1022C60INTFAIL_HS_D_PS_REL_RL_ M1022C59+

BGRFAIL_HS_E_PS_REL_RL_ M1022C58+INTFAIL_HS_E_PS_REL_RL_ M1022C57

[%] Ratio Success SessionPacket RNC_922a

%100%100

M_D_D_BGRPS_REL_NOR M1022C50+M_D_D_INTPS_REL_NOR M1022C49+



BGR_FAIL_D_D_PS_REL_OTH M1022C68+INT_FAIL_D_D_PS_REL_OTH M1022C67+





BGRFAIL_HS_E_PS_REL_RL_ M1022C58+INTFAIL_HS_E_PS_REL_RL_ M1022C57BGR_FAIL_D_D_PS_REL_OTH M1022C68+INT_FAIL_D_D_PS_REL_OTH M1022C67+




BGRFAIL_HS_D_PS_REL_RL_ M1022C60INTFAIL_HS_D_PS_REL_RL_ M1022C59+


[%] Ratio Success SessionPacket RNC_922a

%100%100

100%-DCR



GRSCH_EDCH_BPS_ATT_HSD M1022C4+NTSCH_EDCH_IPS_ATT_HSD M1022C3

GRS_E_ALLO_BHS_E_REQ_H M1022C21+NTS_E_ALLO_IHS_E_REQ_H M1022C21

e[%]Perspectiv User from Ratio Success SetupHSUPA RNC_915a

GRSCH_EDCH_BPS_ATT_HSD M1022C4+NTSCH_EDCH_IPS_ATT_HSD M1022C3


e[%]Perspectiv User from Ratio Success SetupHSUPA RNC_915a

_DCH_BGRPS_ATT_DCH M1022C8+_DCH_INTPS_ATT_DCH M1022C7+

RSCH_DCH_BGPS_ATT_HSD M1022C6TSCH_DCH_INPS_ATT_HSD M1022C5+

GRSCH_EDCH_BPS_ATT_HSD M1022C4+NTSCH_EDCH_IPS_ATT_HSD M1022C3 D_ALLO_BGRD_D_REQ_D_ M1022C32+D_ALLO_INTD_D_REQ_D_ M1022C31+

R_D_ALLO_BGHS_D_REQ_D M1022C30+T_D_ALLO_INHS_D_REQ_D M1022C29+

R_D_ALLO_BGHS_E_REQ_D M1022C28T_D_ALLO_INHS_E_REQ_D M1022C27+

GRS_D_ALLO_BHS_D_REQ_H M1022C26+NTS_D_ALLO_IHS_D_REQ_H M1022C25+

GRS_D_ALLO_BHS_E_REQ_H M1022C24+NTS_D_ALLO_IHS_E_REQ_H M1022C23+


[%] Ratio Success Setup SessionPacket RNC_916

100










100

Any PS Request Can be Setup?

Requested HSDSCH+E-DCH can be setup or not?

RSCH_DCH_BGPS_ATT_HSD M1022C6+TSCH_DCH_INPS_ATT_HSD M1022C5

GRSCH_EDCH_BPS_ATT_HSD M1022C4+NTSCH_EDCH_IPS_ATT_HSD M1022C3 GRS_D_ALLO_BHS_D_REQ_H M1022C26+NTS_D_ALLO_IHS_D_REQ_H M1022C25+

GRS_D_ALLO_BHS_E_REQ_H M1022C24+NTS_D_ALLO_IHS_E_REQ_H M1022C23


e[%]Perspectiv User from Ratio Success SetupHSDPA RNC_914a

RSCH_DCH_BGPS_ATT_HSD M1022C6+TSCH_DCH_INPS_ATT_HSD M1022C5

GRSCH_EDCH_BPS_ATT_HSD M1022C4+NTSCH_EDCH_IPS_ATT_HSD M1022C3 GRS_D_ALLO_BHS_D_REQ_H M1022C26+NTS_D_ALLO_IHS_D_REQ_H M1022C25+

GRS_D_ALLO_BHS_E_REQ_H M1022C24+NTS_D_ALLO_IHS_E_REQ_H M1022C23


e[%]Perspectiv User from Ratio Success SetupHSDPA RNC_914a

Requested

HSDSCH+E-DCH/DCH can be setup or not?



_DCH_BGRPS_ATT_DCH M1022C8_DCH_INTPS_ATT_DCH M1022C7

D_ALLO_BGRD_D_REQ_D_ M1022C32D_ALLO_INTD_D_REQ_D_ M1022C31

[%] ePerspectiv Usert From Ratio Success SetupR99 RNC_943a

_DCH_BGRPS_ATT_DCH M1022C8_DCH_INTPS_ATT_DCH M1022C7

D_ALLO_BGRD_D_REQ_D_ M1022C32D_ALLO_INTD_D_REQ_D_ M1022C31

[%] ePerspectiv Usert From Ratio Success SetupR99 RNC_943a










100










100

Any PS Request Can be Setup?

Requested R99 can be setup or not?


RAS06 HSDPA Packet Call Setup Statistics

HS-DSCH

+

DCH

HS-DSCH

+

DCH

CRCR

Successful SetupsM1022C3 PS_ATT_HSDSCH_EDCH_INT : HS-DSCH/E-DCH was requested by AC for Interactive class






M1022C25 HS_D_REQ_HS_D_ALLO_INT - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for INTERACTIVE traffic classM1022C26 HS_D_REQ_HS_D_ALLO_BGR - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/DCH was initially requested for BACKGROUND traffic class









M1022C23 HS_E_REQ_HS_D_ALLO_INT - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic class

M1022C24 HS_E_REQ_HS_D_ALLO_BGR - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class

Setup Failures



RAS06 HSPA Packet Call Setup Statistics

HS-DSCH

+

E-DCH

HS-DSCH

+

E-DCH

CRCR

M1022C3 PS_ATT_HSDSCH_EDCH_INT : HS-DSCH/E-DCH was requested by AC for Interactive class






M1022C21 HS_E_REQ_HS_E_ALLO_INT - HS-DSCH/E-DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C22 HS_E_REQ_HS_E_ALLO_BGR - HS-DSCH/E-DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class

M1022C23 HS_E_REQ_HS_D_ALLO_INT - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C24 HS_E_REQ_HS_D_ALLO_BGR - HS-DSCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class

M1022C27 HS_E_REQ_D_D_ALLO_INT - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for INTERACTIVE traffic classM1022C28 HS_E_REQ_D_D_ALLO_BGR - DCH/DCH is successfully aIlocated after HS-DSCH/E-DCH was initially requested for BACKGROUND traffic class







Successful Setups

Setup Failures



RAS06 PS Call Release

HS-DSCH HS-DSCH

DCH DCH

CRCR

M1022C45 PS_REL_NORM_HS_E_INT

M1022C46 PS_REL_NORM_HS_E_BGR

Normal Releases

HS-DSCH

+

E-DCH

HS-DSCH

+

E-DCH

M1022C47 PS_REL_NORM_HS_D_INT

M1022C48 PS_REL_NORM_HS_D_BGR

M1022C49 PS_REL_NORM_D_D_INT

M1022C50 PS_REL_NORM_D_D_BGR

M1022C51 PS_REL_PRE_EMP_HS_E_INT

M1022C52 PS_REL_PRE_EMP_HS_E_BGR

M1022C53 PS_REL_PRE_EMP_HS_D_INT

M1022C54 PS_REL_PRE_EMP_HS_D_BGR

M1022C55 PS_REL_PRE_EMP_D_D_INT

M1022C56 PS_REL_PRE_EMP_D_D_BGR

DropsM1022C57 PS_REL_RL_FAIL_HS_E_INT

M1022C58 PS_REL_RL_FAIL_HS_E_BGR

M1022C59 PS_REL_RL_FAIL_HS_D_INT

M1022C60 PS_REL_RL_FAIL_HS_D_BGR

M1022C61 PS_REL_RL_FAIL_D_D_INT

M1022C62 PS_REL_RL_FAIL_D_D_BGR

M1022C63 PS_REL_OTH_FAIL_HS_E_INT

M1022C64 PS_REL_OTH_FAIL_HS_E_BGR

M1022C65 PS_REL_OTH_FAIL_HS_D_INT

M1022C66 PS_REL_OTH_FAIL_HS_D_BGR

M1022C67 PS_REL_OTH_FAIL_D_D_INT

M1022C68 PS_REL_OTH_FAIL_D_D_BGR


Normal Release counters:







are incremented in following cases:

• RAB Released Normally (normal end of the call)

• Transition to DCH0/0, Cell_FACH or Cell_PCH due to inactivity or low utilisation

• Outgoing SRNC relocation

• Inter RNC hard handover

• Inter system hard handover


Release due to Pre-Emption counters:







are incremented in case higher priority call pre-empts the existing connection i.e. RT over NRT

Release due to RL Failure counters:

M1022C57 PS_REL_RL_FAIL_HS_E_INT






are incremented in case RL Failure is received from BTS and cannot be acquired back during specific time (see Dropped RAB analysis in coming slides for further info)

Release due to Other Failure counters:







are incremented in case the PS allocation is released due to any other reason expect normal, pre-emption or RL failure



M_D_D_BGRPS_REL_NOR M1022C50M_D_D_INTPS_REL_NOR M1022C49

BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61BGR_FAIL_D_D_PS_REL_OTH M1022C68INT_FAIL_D_D_PS_REL_OTH M1022C67

GRFAIL_D_D_BPS_REL_RL_ M1022C62NTFAIL_D_D_IPS_REL_RL_ M1022C61

[%] ePerspectiv User End from Ratio SuccessR99 RNC_944a

1





[%] ePerspectiv User End from Ratio SuccessR99 RNC_944a

1





[%] ePerspectiv User End from Ratio Call Dropped R99





[%] ePerspectiv User End from Ratio Call Dropped R99


RAS06 HSPA Call Release

HS-DSCH HS-DSCH

DCH DCH

CRCR



Normal Releases

HS-DSCH

+

E-DCH

HS-DSCH

+

E-DCH











DropsM1022C57 PS_REL_RL_FAIL_HS_E_INT













HSDPA Success Ratio

The HSDPA Success Ratio for Interactive and Background Services from user perspective

• This KPI is based on Packet Call Measurement

%100

920_











ePerspectiv User From Ratio SuccessHSDPA aRNC

%100

920_











ePerspectiv User From Ratio SuccessHSDPA aRNC


HSUPA Success Ratio

The HSUPA Success Ratio for Interactive and Background Services from user perspective

• This KPI is based on Packet Call Measurement (M1022)

100%






100%

ePerspectiv User From Ratio SuccessHSUPA RNC_921a

100%






100%

ePerspectiv User From Ratio SuccessHSUPA RNC_921a





Agenda


Cell Throughput Measurements

• M1023C0 SIGN_RB_DCH_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the signaling radio bearer in the uplink direction during the

measurement interval– The counter is updated at 20-second intervals, and when the connection is released or the active set is

changed– Unit is Byte

• M1023C1 SIGN_RB_DCH_DL_DATA_VOL– The amount of MAC-d PDU data transferred in the signalling radio bearer in the downlink direction during

the measurement inteval– The counter is updated at 20-second intervals, and when the connection is released or the active set is


The RAS06 includes new cell level counters to measure throughput individually for different connection types i.e. SRB, CS DATA + CS VOICE, PS RT, PS NRT, PS HSPA and separately for UL and DLNew counters are shown below:



• M1023C2 CS_DCH_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the CS Call DCH in the uplink direction during the

measurement interval– This counter includes AMR, CS Streaming, and CS Conversational calls– The counter is updated at 20-second intervals, and when the connection is released or the active set is


• M1023C3 CS_DCH_DL_DATA_VOL– The amount of MAC-d PDU data transferred in the CS Call DCH in the downlink direction during the



• M1023C4 RT_PS_DCH_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the RT PS DCH in the uplink direction during the



• M1023C5 RT_PS_DCH_DL_DATA_VOL– The amount of MAC-d PDU data transferred in the RT PS DCH in the downlink direction during the



• M1023C2 CS_DCH_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the CS Call DCH in the uplink direction during the

measurement interval– This counter includes AMR, CS Streaming, and CS Conversational calls– The counter is updated at 20-second intervals, and when the connection is released or the active set is


• M1023C3 CS_DCH_DL_DATA_VOL– The amount of MAC-d PDU data transferred in the CS Call DCH in the downlink direction during the



• M1023C4 RT_PS_DCH_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the RT PS DCH in the uplink direction during the



• M1023C5 RT_PS_DCH_DL_DATA_VOL– The amount of MAC-d PDU data transferred in the RT PS DCH in the downlink direction during the





• M1023C6 NRT_DCH_UL_DATA_VOL

– The amount of MAC-d PDU data transferred in the NRT DCH in the uplink direction during the measurement interval, excluding HS-DSCH return channels

– The counter is updated at 20-second intervals, and when the connection is released or the active set is changed

– Unit is Byte

• M1023C7 NRT_DCH_DL_DATA_VOL

– The amount of MAC-d PDU data transferred in the NRT DCH in the downlink direction during the measurement interval

– The counter is updated at 20-second intervals, and when the connection is released or the active set is changed

– Unit is Byte



• M1023C8 HS_DSCH_DATA_VOL– The amount of MAC-d PDU data transferred with the HS-DSCH in the downlink direction during the



• M1023C9 NRT_DCH_HSDPA_UL_DATA_VOL– The amount of MAC-d PDU data transferred in the NRT DCH in the uplink direction during the

measurement interval, including only the HS-DSCH return channels– The counter is updated at 20-second intervals, and when the connection is released or the active set is

changed.– Unit is Byte

• M1023C10 NRT_EDCH_UL_DATA_VOL– The amount of MAC-es PDU data transferred in the E-DCH in the uplink direction during the measurement

interval– The MAC-es PDU includes MAC-d PDU data and the 6 bits MAC-es header– The counter is updated at 20-second intervals, and when the connection is released or the active set is




E-DCH Throughput can be measured by RNC_952a

60ATIONPERIOD_DUR1000

8TA_VOLSDPA_UL_DANRT_EDCH_H M1023C10

[kbit/s] RNC at Throughput Average es- MACHSUPA aRNC

952_



[kbit/s] RNC at Throughput Average es- MACHSUPA aRNC

952_

1000


[kbit] RNC at Volume Data es- MACHSUPA aRNC

931_

1000


[kbit] RNC at Volume Data es- MACHSUPA aRNC

931_



HS-DSCH Throughput


8TA_VOLHS_DSCH_DA M1023C8

[kbit/s] RNC at Throughput Average d- MACHSDPA



[kbit/s] RNC at Throughput Average d- MACHSDPA

1000


[kbit] RNC at Volume Data d- MACSDPAH

1000


[kbit] RNC at Volume Data d- MACSDPAH



R99 NRT Throughput DL


8_DATA_VOLNRT_DCH_DL M1023C7

[kbit/s] RNC at Throughput Average d- MACDL NRT R99



[kbit/s] RNC at Throughput Average d- MACDL NRT R99

1000


[kbit] RNC at Volume Data d- MACDL RTN R

99

1000


[kbit] RNC at Volume Data d- MACDL RTN R

99



R99 NRT Throughput UL


8_DATA_VOLNRT_DCH_UL M1023C6

[kbit/s] RNC at Throughput Average d- MACUL NRT R99



[kbit/s] RNC at Throughput Average d- MACUL NRT R99

1000


[kbit] RNC at Volume Data d- MACUL RTN R

99

1000


[kbit] RNC at Volume Data d- MACUL RTN R

99





Agenda


RNCRNCBTSBTS

RRC: Active Set Update

Decision toset up new RL


RRC: Measurement Report (e1a / e1c)

NBAP: Radio Link Setup Response


ALCAP:ERQ

ALCAP:ECF

RRC: Active Set Update Complete

UEUE

NBAP: Radio Link Setup Request – for Soft Handover

NBAP: Radio Link Addition Request – for Softer Handover

NBAP: Radio Link Addition Response

Soft Handover CountersHandovers;

SHO

When a UE with E-DCH allocated requests with 1A or 1C event to add a cell in to the active set, the handover control attempts to add the cell in the E-DCH active set if HSUPA is enabled for the cell and the cell is controlled by SRNCIt is possible that the cell cannot be added into E-DCH AS, e.g. due to maximum number of E-DCH users in cell, and in that case the cell is added only to DCH active set only (in that case a retry timer is started in RNC to make a new addition attempt some time later)

Counter M1007C67 CELL_ADD_ATT_UE_REQ_EDCH_AS is updated for each cell that is attempted to be added into E-DCH AS due to UE reporting event 1A or 1CIf 1A or 1C event includes two cells, then the counter is updated for both cells by 1

When a UE with E-DCH allocated requests with 1A or 1C event to add a cell in to the active set, the handover control attempts to add the cell in the E-DCH active set if HSUPA is enabled for the cell and the cell is controlled by SRNCIt is possible that the cell cannot be added into E-DCH AS, e.g. due to maximum number of E-DCH users in cell, and in that case the cell is added only to DCH active set only (in that case a retry timer is started in RNC to make a new addition attempt some time later)

Counter M1007C67 CELL_ADD_ATT_UE_REQ_EDCH_AS is updated for each cell that is attempted to be added into E-DCH AS due to UE reporting event 1A or 1CIf 1A or 1C event includes two cells, then the counter is updated for both cells by 1

Counter M1007C70 CELL_ADD_ATT_RETRY_EDCH_AS is updated by value 1 for each cell that are attempted to add into E-DCH active set due to retry timer

Counter M1007C70 CELL_ADD_ATT_RETRY_EDCH_AS is updated by value 1 for each cell that are attempted to add into E-DCH active set due to retry timer

Note : If adding a cell into E-DCH active set (or DCH active set) fails due to parallel procedure, then none of the counters are updated. Note : If adding a cell into E-DCH active set (or DCH active set) fails due to parallel procedure, then none of the counters are updated.


RNCRNCBTSBTS

RRC: Active Set Update



RRC: Measurement Report (e1a / e1c)

NBAP: Radio Link Setup Request



ALCAP:ERQ

ALCAP:ECF

RRC: Active Set Update Complete

UEUE

RRC: Active Set Update Failure

Soft Handover CountersHandovers;

SHO

When a new Iub branch for E-DCH is successfully established, counter M1022C74 SUCC_EDCH_FP_BRANCH_SETUP is incremented by value 1 for the WBTS-WCEL object related to that branch

Branch here stands for a new Iub connection for which a new Frame Protocol connection is established, i.e. adding E-DCH Softer handover branch does not cause a new FP branch to be created but adding a soft handover branch to another base station is a new FP branch.

If two or three E-DCH radio links are added to the same BTS with one radio link setup operation, that would mean only one FP branch setup. In this case the counter is updated for the cell which was the first one in the E-DCH cell list given by HA3.

When a new Iub branch for E-DCH is successfully established, counter M1022C74 SUCC_EDCH_FP_BRANCH_SETUP is incremented by value 1 for the WBTS-WCEL object related to that branch

Branch here stands for a new Iub connection for which a new Frame Protocol connection is established, i.e. adding E-DCH Softer handover branch does not cause a new FP branch to be created but adding a soft handover branch to another base station is a new FP branch.

If two or three E-DCH radio links are added to the same BTS with one radio link setup operation, that would mean only one FP branch setup. In this case the counter is updated for the cell which was the first one in the E-DCH cell list given by HA3.

Counter M1007C68 CELL_ADD_SUCC_EDCH_AS is updated by 1 for each cell that was successfully added into E-DCH AS either as a result of UE reporting 1A/1C event or as a result of retry timer triggered addition

Counter M1007C68 CELL_ADD_SUCC_EDCH_AS is updated by 1 for each cell that was successfully added into E-DCH AS either as a result of UE reporting 1A/1C event or as a result of retry timer triggered addition

Counter M1007C69 CELL_ADDED_ONLY_TO_DCH_AS is updated by value 1 for each cell that were attempted to add into E-DCH active set, but for some reason they were added only to DCH active set

Counter M1007C69 CELL_ADDED_ONLY_TO_DCH_AS is updated by value 1 for each cell that were attempted to add into E-DCH active set, but for some reason they were added only to DCH active set

Note : If adding a cell into E-DCH active set (or DCH active set) fails due to parallel procedure, then none of the counters are updated. Note : If adding a cell into E-DCH active set (or DCH active set) fails due to parallel procedure, then none of the counters are updated.


Average Active Set Size KPI (CELL)

Theoretical definition:

T_NRT_IN_ACT_SETHREE_CELL M1007C21T_RT_IN_ACT_SETHREE_CELL M1007C2

NRTN_ACT_SET_TWO_CELL_I M1007C20RTN_ACT_SET_TWO_CELL_I M1007C1

NRTN_ACT_SET_ONE_CELL_I M1007C19RTN_ACT_SET_ONE_CELL_I M1007C0

3T_NRT_IN_ACT_SETHREE_CELL M1007C21T_RT_IN_ACT_SETHREE_CELL M1007C2

2NRTN_ACT_SET_TWO_CELL_I M1007C20RTN_ACT_SET_TWO_CELL_I M1007C1








Cell Level Formula for RT+NRT calls:

UEofNumberTotal

ASSwithUEASSwithUEASSwithUE

___

3)3__(2)2__()1__(

COUNTER COUNTER REFLECTS REFLECTS THEORETHICAL THEORETHICAL DEFINITIONDEFINITION

TOTAL NUMBER OF TOTAL NUMBER OF RADIO LINKS (=UE) RADIO LINKS (=UE) CONNECTED TO THE CONNECTED TO THE CELL UNDER CELL UNDER OBSERVATIONOBSERVATION

-HOW BIG IS SHO AREA?-HOW BIG IS SHO AREA?-HOW MUCH DL CAPACITY ARE WE USING FOR SHO?-HOW MUCH DL CAPACITY ARE WE USING FOR SHO?

Handovers; SHO

Cell Level Formula for HS-DSCH and HS-DSCH + E-DCH allocated call

T_HSDPA_IN_ACT_SETHREE_CELL M1007C50

HSDPAN_ACT_SET_TWO_CELL_I M1007C49

HSDPAN_ACT_SET_ONE_CELL_I M1007C48

3T_HSDPA_IN_ACT_SETHREE_CELL M1007C50

2HSDPAN_ACT_SET_TWO_CELL_I M1007C49








S_DURA_IN_EDCH_ATHREE_CELL M1007C65

DURAN_EDCH_AS_TWO_CELL_I M1007C64

DURAN_EDCH_AS_ONE_CELL_I M1007C63

3S_DURA_IN_EDCH_ATHREE_CELL M1007C65

2DURAN_EDCH_AS_TWO_CELL_I M1007C64









Average Active Set Size KPI (Cluster)

3







3








Cluster Level Formula for RT+NRT calls

UEofNumberTotal

ASSwithUEASSwithUEASSwithUE

___

3)3__(2)2__()1__(

TOTAL NUMBER OF BEST SERVER TOTAL NUMBER OF BEST SERVER RADIO LINKS (=UE) RADIO LINKS (=UE) CONNECTED TO THE RNC UNDER CONNECTED TO THE RNC UNDER OBSERVATIONOBSERVATION

BECAUSE OF DOUBLE AND TRIPLE BECAUSE OF DOUBLE AND TRIPLE RADIORADIOLINKS COUNTING, ACTIVE SET SIZE IS LINKS COUNTING, ACTIVE SET SIZE IS ALREADY ALREADY INCLUDED IN COUNTERS WHEN INCLUDED IN COUNTERS WHEN CLUSTER LEVEL CLUSTER LEVEL FORMULA IS CONSIDEREDFORMULA IS CONSIDERED

-HOW BIG IS SHO AREA?-HOW BIG IS SHO AREA?- HOW MUCH DL CAPACITY ARE WE USING FOR SHO?- HOW MUCH DL CAPACITY ARE WE USING FOR SHO?

Handovers; SHO













Cluster Level Formula for HS-DSCH and and HS-DSCH + E-DCH calls

3







3








Soft Handover Overhead KPI (CELL)


Cell Level Formula for RT+NRT calls:

1

_____

____%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotalOverheadSHO

-HOW BIG IS SHO AREA?-HOW BIG IS SHO AREA?-HOW MUCH DL CAPACITY ARE WE ARE WE USING FOR SHO?-HOW MUCH DL CAPACITY ARE WE ARE WE USING FOR SHO?

%100

1







RNC_79B Overhead Handover Soft

%100

1







RNC_79B Overhead Handover Soft

TOTAL NUMBER OF TOTAL NUMBER OF RADIO LINKS (=UE) RADIO LINKS (=UE) CONNECTED TO CONNECTED TO THE CELL UNDER THE CELL UNDER OBSERVATIONOBSERVATION

COUNTER COUNTER REFLECTS REFLECTS THEORETHICTHEORETHICAL AL DEFINITIONDEFINITION

Handovers; SHO

Cell Level Formula for HS-DSCH and HS-DSCH+E-DCH calls:

%1001







%1001







%1001







%1001








Soft Handover Overhead KPI (Cluster)


The cluster based equation becomes inaccurate when there is inter-RNC soft handover because the above counters can be updated only by ServingRNC

1

_____

____%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotalOverheadSHO

-HOW BIG IS SHO AREA?-HOW BIG IS SHO AREA?-HOW MUCH DL CAPACITY ARE WE ARE WE USING FOR SHO?-HOW MUCH DL CAPACITY ARE WE ARE WE USING FOR SHO?

Handovers; SHO

100%1

3







Area Overhead, Handover SoftRNC_192B

100%1

3







Area Overhead, Handover SoftRNC_192B

Cluster Level Formula for RT+NRT calls

100%1







100%1







Cluster Level Formula for HS-DSCH and HS-DSCH+E-DCH calls

100%1

3







100%1

3











Agenda


HS-DSCH & E-DCH Serving Cell Change Handovers; HS-DSCH

SCCUE

Original Serving Cell

Node B 1HSDPA Traffic


Measurement Report (DCH) – e1A

RRC: Active Set Update (DCH)

NBAP: Radio Link Setup

NBAP: Radio Link SynchronisationRRC: Active Set Update Complete (DCH)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

RRC: Measurement Control


RRC: Physical Channel Reconfiguration


RRC: Physical Channel Reconfiguration Complete (DCH)

Measurement Report (DCH)


Target Serving Cell Node B 2 RNC

Decision to initiate HS-DSCH SCC


The number of HS-DSCH serving cell change procedure initiations per cause: M1008C213 SCC_STARTED_CPICH_ECNO M1008C214 SCC_STARTED_UL_SIR_ERROR M1008C215 SCC_STARTED_ACTIVE_SET_UPD M1008C216 SCC_STARTED_OTHER_REASON Updated in the current HSDPA Serving Cell (i.e. old serving cell) i.e. source cellCounter NOT updated in case SCC is rejected due to parallel procedure not allowed reason also in that case none of the failure counters is incremented!

The number of HS-DSCH serving cell change procedure initiations per cause: M1008C213 SCC_STARTED_CPICH_ECNO M1008C214 SCC_STARTED_UL_SIR_ERROR M1008C215 SCC_STARTED_ACTIVE_SET_UPD M1008C216 SCC_STARTED_OTHER_REASON Updated in the current HSDPA Serving Cell (i.e. old serving cell) i.e. source cellCounter NOT updated in case SCC is rejected due to parallel procedure not allowed reason also in that case none of the failure counters is incremented!

One SCC procedure includes attempts to

any or all AS cells


any or all AS cells

The number of E-DCH serving cell change procedure initiations : M1008C239 EDCH_SCC_STARTED Updated in current HS-DSCH/E-DCH Serving Cell Note that E-DCH service cell is changed when HS-DSCH serving cell changes

The number of E-DCH serving cell change procedure initiations : M1008C239 EDCH_SCC_STARTED Updated in current HS-DSCH/E-DCH Serving Cell Note that E-DCH service cell is changed when HS-DSCH serving cell changes


Handovers; HS-DSCH

SCCUE




















In case the AC decides to reject the serving cell change, counter M1008C220 SCC_FAILED_DUE_TO_AC is incremented in the current serving HSDPA cellAC reasons: maximum number of HSDPA users were already allocated in the target cells or in case of first MAC-d flow under the target cell then also R99 power might be too high (depending on HSDPApriority either PtxNC only or PtxTotal)

In case the AC decides to reject the serving cell change, counter M1008C220 SCC_FAILED_DUE_TO_AC is incremented in the current serving HSDPA cellAC reasons: maximum number of HSDPA users were already allocated in the target cells or in case of first MAC-d flow under the target cell then also R99 power might be too high (depending on HSDPApriority either PtxNC only or PtxTotal)


any or all AS cells


any or all AS cells

In case HS-DSCH cell changes are prevented by timer HSDPACellChangeMinInterval or HSDPACellChangeRepetitionTime, counter M1008C224 SCC_PREVENTED_DUE_TO_TIMER is incremented in the current serving HSDPA cell

In case HS-DSCH cell changes are prevented by timer HSDPACellChangeMinInterval or HSDPACellChangeRepetitionTime, counter M1008C224 SCC_PREVENTED_DUE_TO_TIMER is incremented in the current serving HSDPA cell

HS-DSCH & E-DCH Serving Cell Change

There are no failure counters for E-DCH serving cell change, but the failures are seen through HS-DSCH serving cell change counters

If all SCC candidates can only have DCH, then E-DCH->DCH downgrade would happen in a successful SCC




Handovers; HS-DSCH

SCCUE


















NBAP: Radio Link Reconfiguration ReadyNBAP: Radio Link Reconfiguration Failure





The number of HS-DSCH setup failures due to BTS in the SRNC for interactive or background class connections for HS-DSCH SCC increments the same counters as for initial setup:M1002C416 SETUP_FAIL_BTS_HS_DSCH_INT or M1002C424 SETUP_FAIL_BTS_HS_DSCH_BGR M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C218 SCC_FAILED_DUE_TO_BTS is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell. Counter not incremented correctly, Electra 1-288060911

The number of HS-DSCH setup failures due to BTS in the SRNC for interactive or background class connections for HS-DSCH SCC increments the same counters as for initial setup:M1002C416 SETUP_FAIL_BTS_HS_DSCH_INT or M1002C424 SETUP_FAIL_BTS_HS_DSCH_BGR M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C218 SCC_FAILED_DUE_TO_BTS is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell. Counter not incremented correctly, Electra 1-288060911


any or all AS cells


any or all AS cells







Handovers; HS-DSCH

SCCUE























The number of HS-DSCH MAC-d flow setup failures due to RNC external reasons in the SRNC for interactive or background class connections for HS-DSCH SCC increments the same counter as original setup:M1002C414 SETUP_FAIL_IUB_MAC_D_INT or M1002C422 SETUP_FAIL_IUB_MAC_D_BGR is incremented (this does NOT include the Shared HSDPA Allocation). M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C219 SCC_FAILED_DUE_TO_TRANSM is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.

The number of HS-DSCH MAC-d flow setup failures due to RNC external reasons in the SRNC for interactive or background class connections for HS-DSCH SCC increments the same counter as original setup:M1002C414 SETUP_FAIL_IUB_MAC_D_INT or M1002C422 SETUP_FAIL_IUB_MAC_D_BGR is incremented (this does NOT include the Shared HSDPA Allocation). M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C219 SCC_FAILED_DUE_TO_TRANSM is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.


any or all AS cells


any or all AS cells







Handovers; HS-DSCH

SCCUE



















ALCAP : ERQ


ALCAP : ECF

NBAP: Radio Link Reconfiguration CommitNBAP: Radio Link Reconfiguration Commit

RRC: Radio Bearer Reconfiguration





When the RNC has received an RRC: RADIO BEARER RECONFIGURATION FAILURE message from the UE during the HS-DSCH setup or a timer waiting for the RRC: RADIO BEARER RECONFIGURATION COMPLETE message expires, counter M1002C415 SETUP_FAIL_UE_HS_DSCH_INT or M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR, is incremented M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C217 SCC_FAILED_DUE_TO_UE is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.

When the RNC has received an RRC: RADIO BEARER RECONFIGURATION FAILURE message from the UE during the HS-DSCH setup or a timer waiting for the RRC: RADIO BEARER RECONFIGURATION COMPLETE message expires, counter M1002C415 SETUP_FAIL_UE_HS_DSCH_INT or M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR, is incremented M1002 is incremented in the NEW (target) serving cell.

Also counter M1008C217 SCC_FAILED_DUE_TO_UE is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.


any or all AS cells


any or all AS cells







Handovers; HS-DSCH

SCCUE



















ALCAP : ERQ


ALCAP : ECF







If at any time during the HS-DSCH setup the RNC decides to reject the HS-DSCH setup (including RNC internal transport), the counter: M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT orM1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR, is incrementedM1002 is incremented in the NEW (target) serving cell.

Also counter M1008C221 SCC_FAILED_DUE_TO_OTHER is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.

If at any time during the HS-DSCH setup the RNC decides to reject the HS-DSCH setup (including RNC internal transport), the counter: M1002C413 SETUP_FAIL_RNC_HS_DSCH_INT orM1002C421 SETUP_FAIL_RNC_HS_DSCH_BGR, is incrementedM1002 is incremented in the NEW (target) serving cell.

Also counter M1008C221 SCC_FAILED_DUE_TO_OTHER is incremented. If there were two candidate cells and they failed for different reasons, the error code of the first candidate cell shall be used for counter update. M1008 is incremented in the OLD (source) serving cell.


any or all AS cells


any or all AS cells







Handovers; HS-DSCH

SCCUE


















NBAP: Radio Link Reconfiguration ReadyNBAP: Radio Link Reconfiguration Ready

ALCAP : ERQ


ALCAP : ECF





When RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter: M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR is incremented in the Target cell and M1002C393 ALLO_DURA_HS_DSCH_FLOW_INT or M1002C397 ALLO_DURA_HS_DSCH_FLOW_BGR is started in the Target cell

When RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter: M1002C385 ALLO_HS_DSCH_FLOW_INT or M1002C389 ALLO_HS_DSCH_FLOW_BGR is incremented in the Target cell and M1002C393 ALLO_DURA_HS_DSCH_FLOW_INT or M1002C397 ALLO_DURA_HS_DSCH_FLOW_BGR is started in the Target cellWhen RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter: M1002C407 REL_ALLO_NORM_HS_DSCH_INT or M1002C410 REL_ALLO_NORM_HS_DSCH_BGR is incremented in the Source cell and and M1002C393 ALLO_DURA_HS_DSCH_FLOW_INT or M1002C397 ALLO_DURA_HS_DSCH_FLOW_BGR is stopped in the Source cell

When RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter: M1002C407 REL_ALLO_NORM_HS_DSCH_INT or M1002C410 REL_ALLO_NORM_HS_DSCH_BGR is incremented in the Source cell and and M1002C393 ALLO_DURA_HS_DSCH_FLOW_INT or M1002C397 ALLO_DURA_HS_DSCH_FLOW_BGR is stopped in the Source cell







Handovers; HS-DSCH

SCCUE


















NBAP: Radio Link Reconfiguration ReadyNBAP: Radio Link Reconfiguration Ready

ALCAP : ERQ


ALCAP : ECF





When RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter M1008C222 SCC_INTRA_BTS_SUCCESSFUL (new serving cell belongs to the same BTS as old serving cell) or M1008C223 SCC_INTER_BTS_SUCCESSFUL (new serving cell belongs to different BTS than old serving cell) is incremented in the new serving cell (target cell)

When RRC: Radio Bearer Reconfiguration Complete –message has been received by the RNC as an indication of successful HS-DSCH serving cell change counter M1008C222 SCC_INTRA_BTS_SUCCESSFUL (new serving cell belongs to the same BTS as old serving cell) or M1008C223 SCC_INTER_BTS_SUCCESSFUL (new serving cell belongs to different BTS than old serving cell) is incremented in the new serving cell (target cell)


Counter M1008C240 EDCH_SCC_INTRA_BTS_SUCCESS is incremented for the new HS-DSCH/E-DCH serving cell when intra-BTS HS-DSCH serving cell was successfully performed so that E-DCH is still allocated for the UECounter M1008C241 EDCH_SCC_INTER_BTS_SUCCESS is incremented for the new HS-DSCH/E-DCH serving cell when inter-BTS HS-DSCH serving cell was successfully performed so that E-DCH is still allocated for the UE.

Counter M1008C240 EDCH_SCC_INTRA_BTS_SUCCESS is incremented for the new HS-DSCH/E-DCH serving cell when intra-BTS HS-DSCH serving cell was successfully performed so that E-DCH is still allocated for the UECounter M1008C241 EDCH_SCC_INTER_BTS_SUCCESS is incremented for the new HS-DSCH/E-DCH serving cell when inter-BTS HS-DSCH serving cell was successfully performed so that E-DCH is still allocated for the UE.

counter M1008C242 EDCH_DOWNG_DCH_IN_SCC is incremented for the new HS-DSCH serving cell when HS-DSCH serving cell change was successful, but uplink was downgraded from E-DCH to DCH

counter M1008C242 EDCH_DOWNG_DCH_IN_SCC is incremented for the new HS-DSCH serving cell when HS-DSCH serving cell change was successful, but uplink was downgraded from E-DCH to DCH



The E-DCH Serving Cell Change initiations can be calculated as below

The HS-DSCH Serving Cell Change initiations can be calculated as below

Handovers; HS-DSCH

SCC

STARTEDSCCEDCH M1008C239Attemps SCCHSUPA aRNC __929_

EASONED_OTHER_R SCC_STARTM1008C216SET_UPDED_ACTIVE_ SCC_STARTM1008C215

ERRORED_UL_SIR_ SCC_STARTM1008C214CNOED_CPICH_E SCC_STARTM1008C213Attemps SCCHSDPA aRNC 927_

EASONED_OTHER_R SCC_STARTM1008C216SET_UPDED_ACTIVE_ SCC_STARTM1008C215

ERRORED_UL_SIR_ SCC_STARTM1008C214CNOED_CPICH_E SCC_STARTM1008C213Attemps SCCHSDPA aRNC 927_

TARTEDEDCH_SCC_S M1008C239

UCCESSNTER_BTS_SEDCH_SCC_I M1008C241+UCCESSNTRA_BTS_SEDCH_SCC_I M1008C240

Rate SuccessChange Cell ServingHSUPA RNC_918a

%100TARTEDEDCH_SCC_S M1008C239

UCCESSNTER_BTS_SEDCH_SCC_I M1008C241+UCCESSNTRA_BTS_SEDCH_SCC_I M1008C240

Rate SuccessChange Cell ServingHSUPA RNC_918a

%100





Agenda


HSPA Inter-RNC Cell Change ProcedureHandovers; HS-DSCH

SCC

SRNC Relocation Decision

SRNC operation started

UP switching

User plane set -up

RANAP:Relocation Required RANAP:Relocation Request

RANAP:Relocation Request Ack

RANAP:Relocation complete

RRC:UTRAN Mobility Information

RANAP:Relocation Command

RNSAP:Relocation Commit

RANAP:Relocation Detect

RRC:UTRAN Mobility Information Confirm

RANAP:Iu Release

RANAP:Iu Release Complete

SRNCSRNC UEUECNCN DRNCDRNC

RRC: Transport Channel Reconfiguration

RRC: Transport Channel Reconfiguration Complete

M1008C243 INTER_RNC_HHO_ATT_HSPA_SCC is incremented when SRNC decides to initiate inter RNC HHONote that this counter IS NOT incremented in case of inter RNC HHO failure due to parallel procedureCounter is updated into old HSDPA serving cell (source serving cell).

M1008C243 INTER_RNC_HHO_ATT_HSPA_SCC is incremented when SRNC decides to initiate inter RNC HHONote that this counter IS NOT incremented in case of inter RNC HHO failure due to parallel procedureCounter is updated into old HSDPA serving cell (source serving cell).

M1008C244 INTER_RNC_HHO_SUCC_HSPA_SCC is incremented when inter RNC HHO and SRNC relocation are performed successfully.Counter is updated into old HSDPA serving cell (source serving cell).

M1008C244 INTER_RNC_HHO_SUCC_HSPA_SCC is incremented when inter RNC HHO and SRNC relocation are performed successfully.Counter is updated into old HSDPA serving cell (source serving cell).



SCC



RANAP:Relocation Request Nack

RANAP:Relocation Failure

SRNCSRNC UEUECNCN DRNCDRNC M1008C243 INTER_RNC_HHO_ATT_HSPA_SCC is incremented when SRNC decides to initiate inter RNC HHONote that this counter IS NOT incremented in case of inter RNC HHO failure due to parallel procedure Counter is updated into old HSDPA serving cell (source serving cell).

M1008C243 INTER_RNC_HHO_ATT_HSPA_SCC is incremented when SRNC decides to initiate inter RNC HHONote that this counter IS NOT incremented in case of inter RNC HHO failure due to parallel procedure Counter is updated into old HSDPA serving cell (source serving cell).

M1008C245 UNSUCC_INTER_RNC_HHO_SCC is incremented in case the inter RNC HHO fails and RNC receives RANAP: RELOCATION PREPATION FAILURE message from the CN, or the RNC does not receive an RANAP: RELOCATION COMMAND message from the CN within a certain time period.Failure cause could be: radio resource congestion in the target cell, radio link setup/addition failure in the target BTS, Radio link failure in the target cell, relocation preparation procedure failure in the CN, or relocation resource allocation procedure failure in the target RNC

Counter is updated into old HSDPA serving cell (source serving cell).

Also counter M1008C9 UTRAN_NOT_ABLE_EXEC_HHO_NRT or M1008C10 UE_NOT_ABLE_EXEC_HHO_NRT is updated

M1008C245 UNSUCC_INTER_RNC_HHO_SCC is incremented in case the inter RNC HHO fails and RNC receives RANAP: RELOCATION PREPATION FAILURE message from the CN, or the RNC does not receive an RANAP: RELOCATION COMMAND message from the CN within a certain time period.Failure cause could be: radio resource congestion in the target cell, radio link setup/addition failure in the target BTS, Radio link failure in the target cell, relocation preparation procedure failure in the CN, or relocation resource allocation procedure failure in the target RNC

Counter is updated into old HSDPA serving cell (source serving cell).

Also counter M1008C9 UTRAN_NOT_ABLE_EXEC_HHO_NRT or M1008C10 UE_NOT_ABLE_EXEC_HHO_NRT is updated





RANAP:Relocation Failure



SCC

M1008C246 INTER_RNC_HHO_DROP_SCC is incremented in case the call drops due to any reason after the inter RNC HHO decision (SRNC relocation decision) is done

M1008C246 INTER_RNC_HHO_DROP_SCC is incremented in case the call drops due to any reason after the inter RNC HHO decision (SRNC relocation decision) is done



UP switching

User plane set -up









RANAP:Iu Release







SCC

Following counters are incremented in target inter RNC Cell Change cell when the procedure is successfully completed.

M1022C78 HS_E_REQ_HS_E_ALLO_HHO-HS-DSCH/E-DCH was requested and successfully allocated

M1022C79 HS_E_REQ_HS_D_ALLO_HHO -HS-DSCH/E-DCH was requested but HS-DSCH/DCH was successfully allocated

M1022C80 HS_D_REQ_HS_D_ALLO_HHO-HS-DSCH/DCH was requested and successfully allocated

M1022C81 HS_E_REQ_D_D_ALLO_HHO -HS-DSCH/E-DCH was requested but only DCH/DCH was successfully allocated

M1022C82 HS_D_REQ_D_D_ALLO_HHO -HS-DSCH/DCH was requested but only DCH/DCH was successfully allocated

Following counters are incremented in target inter RNC Cell Change cell when the procedure is successfully completed.

M1022C78 HS_E_REQ_HS_E_ALLO_HHO-HS-DSCH/E-DCH was requested and successfully allocated

M1022C79 HS_E_REQ_HS_D_ALLO_HHO -HS-DSCH/E-DCH was requested but HS-DSCH/DCH was successfully allocated

M1022C80 HS_D_REQ_HS_D_ALLO_HHO-HS-DSCH/DCH was requested and successfully allocated

M1022C81 HS_E_REQ_D_D_ALLO_HHO -HS-DSCH/E-DCH was requested but only DCH/DCH was successfully allocated

M1022C82 HS_D_REQ_D_D_ALLO_HHO -HS-DSCH/DCH was requested but only DCH/DCH was successfully allocated



UP switching

User plane set -up









RANAP:Iu Release






HSUPA Retainability

The retainability of all successfully allocated E-DCH resources for NRT traffic

• This KPI is based on Traffic Measurement

BGRTHER_FAIL_REL_EDCH_O M1002C542+INTTHER_FAIL_REL_EDCH_O M1002C541+

L_FAIL_BGRREL_EDCH_R M1002C540+L_FAIL_INTREL_EDCH_R M1002C539+

BGRSDSCH_SCC_REL_EDCH_H M1002C538INTSDSCH_SCC_REL_EDCH_H M1002C537+

ORM_BGRREL_EDCH_N M1002C536+ORM_INTREL_EDCH_N M1002C535


ORM_BGRREL_EDCH_N M1002C536ORM_INTREL_EDCH_N M1002C535

100%

Traffic NRT fority Retainabil Resource HSUPA RNC_919a

BGRTHER_FAIL_REL_EDCH_O M1002C542+INTTHER_FAIL_REL_EDCH_O M1002C541+

L_FAIL_BGRREL_EDCH_R M1002C540+L_FAIL_INTREL_EDCH_R M1002C539+


ORM_BGRREL_EDCH_N M1002C536+ORM_INTREL_EDCH_N M1002C535


ORM_BGRREL_EDCH_N M1002C536ORM_INTREL_EDCH_N M1002C535

100%

Traffic NRT fority Retainabil Resource HSUPA RNC_919a


RAS06 DSP Performance & RCPM OLPC update

Cell Resources• HSDPA power• Code Usage• BTS HW MeasurementsHSPA in BTS Measurements• HSDPA in BTS• HSUPA in BTSRRC Connection • RAB Establishment (Packet Call Measurements)• R99 Activation• HSDPA Activation• HSUPA Activation• HSPA Channel Type Switching• RAS06 Packet Call Measurements SummaryRAS06 Cell Throughput MeasurementsSoft Handover Measurements• HSPA Serving Cell Change• HSPA Inter RNC Cell ChangeRAS06 DSP Performance & RCPM OLPC Measurements


DSP Performance Measurements in RNC (613/265H)

Peak Number of Simultaneous HSDPA connection over the RNC over the reporting period, RNC_954a

Note that the available counter must be divided by two because it includes both the 1) Iub user plane service and 2) PDCP layer service

Note that in RAS05.1 the same above counter needs to be divided by 3

DSP Measurements

2

___57613954_

CALLSPEAKNRTDHSDPACM

aRNC2

___57613954_

CALLSPEAKNRTDHSDPACM

aRNC


RCPM Measurements - OLPC

OLPC collects the statistics for the number of HARQ retransmissions

AMR RB UL BLER, RNC_953a

RCPM - OLPC Measurement

s

M1016C19 UL_EDCH_HARQ_RETRANS M1016C19 UL_EDCH_HARQ_RETRANS

%100

RBs AMR All

RBs AMR All

UL_CRC_OKS M1016C4SUL_CRC_NOK M1016C5

SUL_CRC_NOK M1016C5

RNC_953a %100

RBs AMR All

RBs AMR All

UL_CRC_OKS M1016C4SUL_CRC_NOK M1016C5

SUL_CRC_NOK M1016C5

RNC_953a


Troughput Distribution

These counters are updated when a connection is cleared, the AM RLC entity reports the throughput measurement values to the L3 entity

• Then the corresponding class of the throughput distribution is incremented by one

The number of connections with 0...4 kbit/s downlink gross throughput : M1017C34 USER_DL_THRP_DIST_CLASS_1









The number of connections with >1024 kbit/s downlink gross throughput : M1017C43 USER_DL_THRP_DIST_CLASS_10










The number of connections with >1024 kbit/s downlink gross throughput : M1017C43 USER_DL_THRP_DIST_CLASS_10

RCPM - RLC Measurement

s

The number of connections with 1024…2 mbit/s downlink gross throughput : M1017C43 USER_DL_THRP_DIST_CLASS_10

The number of connections with 2...4 mbit/s downlink gross throughput : M1017C50 USER_DL_THRP_DIST_CLASS_11


The number of connections with >8 mbit/s downlink gross throughput : M1017C52 USER_DL_THRP_DIST_CLASS_13

The number of connections with 1024…2 mbit/s downlink gross throughput : M1017C43 USER_DL_THRP_DIST_CLASS_10



The number of connections with >8 mbit/s downlink gross throughput : M1017C52 USER_DL_THRP_DIST_CLASS_13


Troughput Distribution

UL throughput counters are updated when a connection is cleared, the AM RLC entity reports the throughput measurement values to the L3 entity

• Then the corresponding class of the throughput distribution is incremented by one only for the E-DCH active set cells

RCPM - RLC Measurement

s

The number of connections with <250 kbit/s uplink gross throughput : M1017C53 USER_UL_THRP_DIST_CLASS_1

The number of connections with 250kbit/s … <500 kbit/s uplink gross throughput : M1017C54 USER_UL_THRP_DIST_CLASS_2

The number of connections with 500 kbit/s … <1 mbit/s uplink gross throughput : M1017C55 USER_UL_THRP_DIST_CLASS_3

The number of connections with 1 mbit/s … < 1.5 mbit/s uplink gross throughput : M1017C56 USER_UL_THRP_DIST_CLASS_4

The number of connections with >1.5 mbit/s uplink gross throughput : M1017C57 USER_UL_THRP_DIST_CLASS_5

The number of connections with <250 kbit/s uplink gross throughput : M1017C53 USER_UL_THRP_DIST_CLASS_1

The number of connections with 250kbit/s … <500 kbit/s uplink gross throughput : M1017C54 USER_UL_THRP_DIST_CLASS_2

The number of connections with 500 kbit/s … <1 mbit/s uplink gross throughput : M1017C55 USER_UL_THRP_DIST_CLASS_3

The number of connections with 1 mbit/s … < 1.5 mbit/s uplink gross throughput : M1017C56 USER_UL_THRP_DIST_CLASS_4

The number of connections with >1.5 mbit/s uplink gross throughput : M1017C57 USER_UL_THRP_DIST_CLASS_5

Date post:	22-Dec-2015
Category:	Documents
Upload:	bagoes-mardanie
View:	52 times
Download:	1 times

KPI Workshop RAS06

Documents