WCDMA-Ran-Tuning-Report.pdf

WCDMA RAN Tuning Report Technical Reference


2003-08-13

 Ericsson AB 2003 All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright holder. TEMS is a trademark owned by Telefonaktiebolaget L M Ericsson, Sweden. All other trademarks belong to their respective owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

2 (16)

EAB/ZT-03:000090 Uen

Rev A

 Ericsson AB 2003

Open

2003-08-13


Contents


1. 2. 3. 4. 5.

Information Event Description Blocked Call Classification Dropped Call Classification Statistics Formula

4 4 10 11 12

5.1. 5.2. 5.3.

Accessibility Formulas Abnormal Disconnection Formulas Mobility Formulas

12 14 15

Open


Rev A

3 (16)


1.

2003-08-13

Information

This document provides a detailed description of trapped events, blocked call and dropped call classifications in the WCDMA RAN Tuning Report tool in TEMS DeskCat. The formulas used in the report to calculate the event statistics are also presented.

2.

Event Description

The following table provides the description of every event trapped in the TEMS DeskCat WCDMA RAN Tuning Report tool. Users can find these events in the UE Event MIF file generated by the WCDMA RAN Tuning Tool. Most events are divided into several subclasses; subclasses are mutually exclusive.

Event Name

Event Subclass

Description

Blocked Call

Random Access /Failure

Call Setup Failure (OriginatingConversationCall) where RRC Connection Request message is not sent after Call Attempt is initiated through Command Sequence in TEMS Investigation

Blocked Call

RRC Connection Setup not received

Call Setup Failure (OriginatingConversationCall) where RRC Connection Setup message is not received by UE after sending RRC Connection Request

Blocked Call

RRC Connection Complete not sent

Call Setup Failure (OriginatingConversationCall) where RRC Connection Complete message is not sent by UE after receiving RRC Connection Setup message

Blocked Call

RRC Connection Reject

Call Setup Failure (OriginatingConversationCall) where RRC Connection Reject message is received by the UE and no retry on RRC Connection Request

Blocked Call

Measurement Control not Call Setup Failure (OriginatingConversationCall) where received or CM Service Measurement Control message is not received by the UE and Request not sent CM Service Request message is not sent by the UE after RRC Connection Release message is sent by the UE

Blocked Call

Service Request not sent

Call Setup Failure (OriginatingConversationCall) where CM Service Request message is not sent by UE after receiving RRC Measurement Control message

Blocked Call

Call Proceeding not received

Call Setup Failure (OriginatingConversationCall) where Call Proceeding message is not received by the UE after sending CM Service Request message

Blocked Call

Radio Bearer Setup not received

Call Setup Failure (OriginatingConversationCall) where Radio Bearer Setup message is not sent by the UE after receiving Call Proceeding message

Blocked Call

Radio Bearer Setup Complete not sent

Call Setup Failure (OriginatingConversationCall) where Radio Bearer Setup Complete message is not sent by the UE after receiving Radio Bearer Setup message

4 (16)


Rev A


Open

2003-08-13


Event Name

Event Subclass

Description

Blocked Call

Alert or Connect not received

Call Setup Failure (OriginatingConversationCall) where neither Connect nor Alerting message is received by the UE after sending Radio Bearer Setup Complete message

Blocked Call

Connect Acknowledge not Call Setup Failure (OriginatingConversationCall) where sent Connect Acknowledge message is not sent by UE after receiving Alert or Connect message

Call Attempt

Command Sequence

Call Attempt

RRC Connection Request A Call Attempt is initiated through the RRC Connection Request (OriginatingConversationCall) without any prior Call Attempt from Command Sequence. This occurs when user initiated the call manually and not through the Command Sequence.

Call End

After Active Set Update (Addition)

Call is ended normally after receiving Active Set Update message with a new active set to be added

Call End

After Active Set Update (Removal)

Call is ended normally after receiving Active Set Update message with an existing active set to be removed

Call End

After Active Set Update (Replacement)

Call is ended normally after receiving Active Set Update message with an existing active set to be replaced with a new active set

Call End

After Active Set Update Complete (Addition)

Call is ended normally after sending Active Set Update Complete message with a new active set added

Call End

After Active Set Update Complete (Removal)

Call is ended normally after sending Active Set Update Complete message with an existing active set removed

Call End

After Active Set Update Complete (Replacement)

Call is ended normally after sending Active Set Update Complete message with an existing active set replaced

Call End

During CS Call Setup

Call is ended normally during call setup

Call End

Normal

Call is ended normally after call setup

A Call Attempt is initiated through the Command Sequence

Call Established

Connect Acknowledge message is sent by UE during call setup

Call Setup

Either Alert or Connect message is received by UE during call setup

Dropped Call

Abnormal Change to Idle mode

An ongoing call (OriginatingConversationCall) is terminated abnormally with the receipt of BCCH System Information or System Information Block

Dropped Call

Abnormal Disconnect

An ongoing call (OriginatingConversationCall) is terminated abnormally with the receipt or sending of Disconnect message (cause ≠ {Normal Call Clearing, User Busy, No User Responding, User Alerting No Answer, Normal Unspecified})

Dropped Call

Abnormal RRC Connection Release

An ongoing call (OriginatingConversationCall) is terminated abnormally with the receipt of RRC Connection Release message (cause ≠ normal event)


Open


Rev A

5 (16)


2003-08-13

Event Name

Event Subclass

Description

Dropped Call


An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after receiving Active Set Update with a new active set to be added)

Dropped Call


An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after receiving Active Set Update with an existing active set to be removed)

Dropped Call


An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after receiving Active Set Update with an existing active set to be replaced with a new active set)

Dropped Call


An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after sending Active Set Update Complete with a new active set added)

Dropped Call


An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after sending Active Set Update Complete with an existing active set removed)

Dropped Call

After Active Set Update Complete (Replacement)

An ongoing call (OriginatingConversationCall) is terminated abnormally during soft handover (after sending Active Set Update Complete with an existing active set replaced)

Dropped Call

Multiple HO within threshold

An ongoing call (OriginatingConversationCall) is terminated abnormally where there is more than one Measurement Control messages within the user defined HO Drop Timer parameter prior to the drop

Dropped Call

Single Handover within threshold

An ongoing call (OriginatingConversationCall) is terminated abnormally where there is a single Measurement Control message within the user defined HO Drop Timer parameter prior to the drop

End of Log File


The log file is ended during soft handover (after receiving Active Set Update with a new active set to be added)

End of Log File


The log file is ended during soft handover (after receiving Active Set Update with an existing active set to be removed)

End of Log File


The log file is ended during soft handover (after receiving Active Set Update an existing active set to be replaced with a new active set)

End of Log File


The log file is ended during soft handover (after sending Active Set Update Complete with a new active set added)

End of Log File


The log file is ended during soft handover (after sending Active Set Update Complete with an existing active set removed)

End of Log File

After Active Set Update The log file is ended during soft handover (after sending Active Complete (Replacement) Set Update Complete with an existing active set replaced)

End of Log file

During Active State

6 (16)


The log file is ended during ongoing call (OriginatingConversationCall)

Rev A


Open

2003-08-13


Event Name

Event Subclass

Description

End of log file

During CS Call Setup

The log file is ended during call setup (OriginatingConversationCall)

Failed SHO Attempt

Addition

Soft-handover (with a new active set to be added) failure with UE sending Active Set Update Failure message.

Failed SHO Attempt

Removal

Soft-handover (with an existing active set to be removed) failure with UE sending Active Set Update Failure message.

Failed SHO Attempt

Replacement

Soft-handover (with an existing active set to be replaced with a new active set) failure with UE sending Active Set Update Failure message

RAB Setup

Radio Bearer Setup message is received by the UE during call setup (OriginatingConversationCall)

RRC Connection Originating Conversation Direct Retry Call

RRC Connection Setup message is received by the UE after receiving RRC Connection Reject message

RRC Connection Originating Conversation Request Call

UE sends RRC Connection Request (OriginatingConversationCall) message after Call Attempt is initiated through the Command Sequence in TEMS Investigation. Repeated RRC Connection Request will not generate additional event

RRC Connection Originating Conversation Request Retry Call

UE sends RRC Connection Request (OriginatingConversationCall) after receiving RRC Connection Reject

RRC Connection Originating Conversation Setup Call

UE receives RRC Connection Setup after sending RC Connection Request (OriginatingConversationCall)

RRC Connection Originating Conversation Setup Complete Call

UE sends RRC Connection Setup Complete after receiving RRC Connection Setup

RRC Established

UE receives Measurement Control or sends CM Service Request after sending RRC Connection Setup Complete

SHO Attempt

Addition

UE receives Active Set Update with a new active set to be added.

SHO Attempt

Removal

UE receives Active Set Update with an existing active set to be removed

SHO Attempt

Replacement

UE receives Active Set Update with an existing active set to be replaced with a new active set

SHO Attempt Retry

Addition

UE receives repeated Active Setup Update after sending Active Setup Update Complete message with a new active set added

SHO Attempt Retry

Removal

UE receives repeated Active Setup Update after sending Active Setup Update Complete message with an existing active set removed


Open


Rev A

7 (16)


2003-08-13

Event Name

Event Subclass

Description

SHO Attempt Retry

Replacement

UE receives repeated Active Setup Update after sending Active Setup Update Complete message with an existing active set replaced with a new active set

SHO Complete

Addition

UE successfully completed a soft handover with the receipt of Measurement Control message after sending Active Setup Update Complete message with a new active set added

SHO Complete

Removal

UE successfully completed a soft handover with the receipt of Measurement Control message after sending Active Setup Update Complete message with an existing active set removed

SHO Complete

Replacement

UE successfully completed a soft handover with the receipt of Measurement Control message after sending Active Setup Update Complete message with an existing active set replaced with a new active set

SHO Complete without Measurement Control

Addition

UE successfully completed a soft handover with the receipt of new Active Set Update message after sending Active Setup Update Complete message with a new active set added


Removal

UE successfully completed a soft handover with the receipt of new Active Set Update message after sending Active Setup Update Complete message with an existing active set removed


Replacement

UE successfully completed a soft handover with the receipt of new Active Set Update message after sending Active Setup Update Complete message with an existing active set replaced with a new active set

SHO Performed

Addition

UE sends Active Set Update Complete with a new active set added

SHO Performed

Removal

UE sends Active Set Update Complete with an existing active set removed

SHO Performed

Replacement

UE sends Active Set Update Complete with an existing active set replaced with a new active set

SHO Trigger

Event 1a or 1d

UE sends a Measurement Report message with Event 1a or 1d. Repeated Measurement Report with same event and Scrambling code will not generate additional event

SHO Trigger

Event 1b

UE sends a Measurement Report message with Event 1d. Repeated Measurement Report with same event and Scrambling code will not generate additional event

SHO Trigger

Event 1c

UE sends a Measurement Report message with Event 1c. Repeated Measurement Report with same event and Scrambling code will not generate additional event

Start of Log File

Active State

The log file started with Measurement Report message without Call Setup process

8 (16)


Rev A


Open

2003-08-13

Event Name

Event Subclass


Description

Start of Log Files Idle State

The log file started with either System Information or System Information Block message

UE Disconnected After Call Attempt

UE is disconnected immediately after Call Attempt is initiated from the Command Sequence in TEMS Investigation

UE Disconnected After Active Set Update (Addition)

UE is disconnected after receiving Active Set Update with a new active set to be added

UE Disconnected After Active Set Update (Removal)

UE is disconnected after receiving Active Set Update with an existing active set to be removed

UE Disconnected After Active Set Update (Replacement)

UE is disconnected after receiving Active Set Update with an existing active set to be replaced with a new active set

UE Disconnected After Active Set Update Complete (Addition)

UE is disconnected after sending Active Set Update Complete with a new active set added

UE Disconnected After Active Set Update Complete (Removal)

UE is disconnected after sending Active Set Update Complete with an existing active set removed

UE Disconnected After Active Set Update Complete (Replacement)

UE is disconnected after sending Active Set Update Complete with an existing active set replaced with a new active set

UE Disconnected During Active State

UE is disconnected during active mode and not in Soft Handover or Call Setup process

UE Disconnected During CS Call Setup

UE is disconnected during Call Setup (OriginatingConversationCall)

Notes about the WCDMA RAN Tuning Events


•

Soft Handover during Call Setup will not generate an event e.g. SHO Attempt etc.

•

Only Originating Conversation Call will be trapped. No event will be generated for other call e.g. Packet Switch call, Registration or Mobile Terminating Circuited Switch Call.

•

No event will be generated for Inter-system Handover

•

UE Disconnected events include loss of connection between the UE and the PC due to frozen UE or UE that is switched off manually. If UE freezes and the log file is ended before restarting the UE, a corresponding End of Log file event will be generated instead of UE Disconnect

Open


Rev A

9 (16)


3.

2003-08-13

Blocked Call Classification

Blocked Call Classification

Description

Random Access /Failure

Call Setup Failure (OriginatingConversationCall) where RRC Connection Request message is not sent after Call Attempt is initiated through Command Sequence in TEMS Investigations

RRC Connection Setup not received

Call Setup Failure (OriginatingConversationCall) where RRC Connection Setup message is not received by UE after sending RRC Connection Request

RRC Connection Complete not sent

Call Setup Failure (OriginatingConversationCall) where RRC Connection Complete message is not sent by UE after receiving RRC Connection Setup message

RRC Connection Reject

Call Setup Failure (OriginatingConversationCall) where RRC Connection Reject message is received by the UE and no retry on RRC Connection Request

Measurement Control not received or CM Service Request not sent

Call Setup Failure (OriginatingConversationCall) where Measurement Control message is not received by the UE and CM Service Request message is not sent by the UE after RRC Connection Release message is sent by the UE

Service Request not sent

Call Setup Failure (OriginatingConversationCall) where CM Service Request message is not sent by UE after receiving RRC Measurement Control message

Call Proceeding not received Call Setup Failure (OriginatingConversationCall) where Call Proceeding message is not received by the UE after sending CM Service Request message Radio Bearer Setup not received

Call Setup Failure (OriginatingConversationCall) where Radio Bearer Setup message is not sent by the UE after receiving Call Proceeding message

Radio Bearer Setup Complete not sent

Call Setup Failure (OriginatingConversationCall) where Radio Bearer Setup Complete message is not sent by the UE after receiving Radio Bearer Setup message

Alert or Connect not received

Call Setup Failure (OriginatingConversationCall) where neither Connect or Alerting message is received by the UE after sending Radio Bearer Setup Complete message

Connect Acknowledge not sent

Call Setup Failure (OriginatingConversationCall) where Connect Acknowledge message is not sent by UE after receiving Alert or Connect message

If the Blocked Call event is followed by RRC Connection Request with cause value = Registration, the Blocked Call Class will have suffix “- Next Event: Registration.”

10 (16)


Rev A


Open

2003-08-13

4.


Dropped Call Classification

Every dropped call is classified according to the conditions prior to the drop. Drop call reasons are classified according to several radio environment criteria where the thresholds are user-defined. The following user parameters are changeable in the user interface for Drop Call Classification: • • • •

Drop RSCP Drop Ec/No Drop TxPower Drop DL BLER

Dropped Call Classification

RSCP

Ec/No

TXPWR

BLER

DL Coverage

Low

Any

Any

Any

DL Interference

High

Low

Any

Any

High DL BLER High UL TX Power

High

High

Low

High

High

High

High

Low

High UL TX Power and DL BLER

High

High

High

High

No Data

No Data

Any

Any

Any

No Data

High

No Data

Any

Any

No Data

High

High

No Data

Any

No Data

High

High

Any

No Data

Not Classified

None of above

1

The following conditions apply: 1. RSCP equals: • Low if CPICH_RSCP < Drop RSCP • High if CPICH_RSCP >= Drop RSCP 2. Ec/No equals: • Low if CPICH_ Ec/N0 < Drop Ec/No • High if CPICH_ Ec/N0 >= Drop Ec/No 3. TXPWR equals: • Low if UE TX Power < Drop TxPower • High if UE TX Power >= Drop TxPower 4. BLER equals: • Low if DL_BLER < Drop DL BLER • High if DL_BLER >= Drop DL BLER

1

Any values or No data logged e.g. Low, High or No data


Open


Rev A

11 (16)


2003-08-13

In addition to the radio environment, the Dropped Call Class may contain an extra suffix or prefix based on the following conditions (this is not applicable if the Dropped Call is ‘Not Classified’): •

If the Dropped Call event has subclass Abnormal RRC Connection Release with cause value = unspecified, the Drop Call Class will have a prefix “Network Commanded Release -”

•

If the Dropped Call event is followed by RRC Connection Request with cause value = Registration, the Drop Call Class will have suffix “- Next Event: Registration”

5.

Statistics Formula

The objects (chart, table and texts) provided by TEMS DeskCat usually present the calculated statistics based on the occurred events. This section provides the formulas used to calculate the statistics. All formulas are mainly based on the occurrences of the events. The symbol

∑ event (event _ subclass) means the total occurrences of the followed

event.

5.1. Accessibility Formulas Total CS Call Attempt

CsAttemptSum = ∑ Call Attempt (any subclass)

Total CS Call Attempt (Excludes abnormal failures) Some call attempts will not lead to establishment due to the following nonnetwork related problems: •

User ends the call during call setup

•

The measurement log file ends during call setup, which leads to insufficient data to judge the setup

•

Connection to the UE broken

•

UE Freeze during the call setup

The total number of Call Attempts excluding these non-network related problem is given by following formula:

CsAttemptSum − ∑ CallEndduringCSSetup    − ∑ Endof log file( DuringCSSetup)   ` CsAttemptActualSum =  − ∑ UEDsiconnect ( DuringCS Setup )    − ∑ UEDsiconnect ( AfterCallAttempt )   

12 (16)


Rev A


Open

2003-08-13


Total RRC Connection Set-up Successes

RrcEstablishSum = ∑ RRCEstablished

RRC Connection Setup Success Rate

RrcEstablishSuccessRate = 100 ×

∑ RRCEstablished CsAttemptSum

Total CS RAB Setup Successes

CsRabEstablishSum = ∑ CallSetup

RAB Setup Success Rate

CsRabSetupSuccessRate = 100 ×

∑ CallSetup CsAttemptSum

Total CS Call Setup Successes

CsEstablishSuccessSum = ∑ CallEstablished

CS Call Setup Success Rate

CsCallSetupSuccessRate =

100 × ∑ CallEstablished

CSAttemptSum − ∑ CallEndDuringCSSetup    − ∑ EndofLogDuringCSSetup 

CS Call Setup Success Rate excluding UE Problem

CsCallSetupActualSuccessRate =

100 × ∑ CallEstablished

[CSAttemptActualSum]

CS Call Setup Failure

CsCallSetu pFailureRate = 100 − CsCallSetu pSuccessRate

Total Complete CS Call

CsCallEndSum = ∑ CallEnd (φ )

where φ is any of the following subclasses:


Open

•

Normal

•

After Active Set Update

•

After Active Set Update Complete


Rev A

13 (16)


2003-08-13

5.2. Abnormal Disconnection Formulas Total CS Dropped Call

CsDropSum = ∑ DroppedCall ( AnySubclass )

Total Unknown Abnormal Disconnection

∑ CallEstablished − ∑ CallEnd (φ )  − DroppedCall ( AnySubclass )   ∑  CsDropOtherSum =   − UEDisconnect (φ )  ∑   − ∑ EndofLog (φ ) 

where φ is any of the following subclasses: •

Normal or During Active state

•

After Active Set Update

•

After Active Set Update Complete

Note: This formula will give an inaccurate result if a call is ongoing when the log file starts. CS Dropped Call Rate

CsDropRate =

100 × ∑ DroppedCall ( AnySubclass)

∑ CallEstablished − ∑ CallEnd (φ )   − ∑ Endof log file(φ )     − ∑ UEDsiconnect (φ )    

where φ belongs to any of the following event sub-classes: •

Normal or During Active state

•

After Active Set Update (Addition, Removal or Replacement)

•

After Active Set Update Complete (Addition, Removal or Replacement)

Note: This formula will give an inaccurate result if a call is ongoing when the log file starts. Total CS Dropped During Soft/Softer Handover

  ∑ DroppedCall ( AfterActiveSetUpate) CsDropSHOSum =   + ∑ DroppedCall ( AfterActiveSetUpdateComplete)

14 (16)


Rev A


Open

2003-08-13


Retainability Rate

   ∑ DroppedCall ( Anysub − class )  Cs Re tainabilityRate = 1 −   CsDurationTotal     MHT where MHT = Voice Call Mean Holding Time (User Defined) Call Time between Drop

CsTimeBtwDrop =

CsDurationTotal ∑ DroppedCall ( AnySubclass)

5.3. Mobility Formulas Total Soft/Softer Handover Trigger (Measurement Report)

SHOTriggerSum = ∑ SHOTrigger ( AnySubclass)

Percentage of HO Trigger lead to Active Set Update

SHOTriggerSucessRate =

100 × ∑ SHOAttempt ( AnySubclass )

∑ SHOTrigger ( AnySubclass)

Percentage of HO Trigger lead to HO Complete

SHOTriggerCompleteSuccessRate = 100 ×

∑ SHOComplete( AnySubclass) ∑ SHOTrigger ( AnySubclass)   − ∑ Endof log file(γ )     − ∑ UEDsiconnect (γ )   − ∑ CallEnd (γ )  

where γ belongs to any of the following event sub-classes: •


•


This formula counts any Call End (normal), End of Log file, UE Disconnect that occurs after SHO Trigger as a failure. In addition, SHO Trigger that does not lead to SHO Attempt due to queuing in the SHO algorithm is counted as a failure.


Open


Rev A

15 (16)


2003-08-13

Soft/Softer Handover Success Rate

  ∑ SHOComplete( AnySubclass) +   SHOCompleteNoMeasurementControl ( AnySubclass ) ∑  SHOSuccesRate = 100 × ∑ SHOAttempt ( AnySubclass) − ∑ CallEnd (γ )   − ∑ Endof log file(γ )     − ∑ UEDsiconnect (γ )    

where γ belongs to any of the following event sub-classes: •


•


Total Soft/Softer Handover Failures

 ∑ FailedSHO Atttempt ( AnySubclass )    ShoFailSum =  + ∑ DroppedCall ( DuringSHOAttempt )   + ∑ DroppedCall ( DuringSHOPerformed )  

Handover Stability Rate Formula

 ∑ DroppedCall (β )  ShoStabilityRate = 1 −   ∑ ShoAttempt ( AnySubclass ) 

where β belongs to any of the following event sub-classes:

16 (16)

•

Single Measurement Control within threshold

•

Multiple Measurement Controls within threshold

•


•



Rev A


Open

WCDMA-Ran-Tuning-Report.pdf

Recommend Documents