Compressed Mode Log Analysis

Supratik Bhattacharjee

Restricted Distribution: This document contains critical information about QUALCOMM products and may not be distributed to anyone
that is not an employee of QUALCOMM without the approval of Configuration Management.
Export of this technology may be controlled by the United States Government. Diversion contrary to U.S. law prohibited.
®
QUALCOMM Proprietary
All data and information contained in or disclosed by this document is confidential and proprietary information of QUALCOMM
Incorporated, and all rights therein are expressly reserved. By accepting this material the recipient agrees that this material and the
information contained therein is held in confidence and in trust and will not be used, copied, or reproduced in whole or in part, nor its
contents revealed in any manner to others without the express written permission of QUALCOMM Incorporated.
QUALCOMM Incorporated
5775 Morehouse Dr.
San Diego, CA 92121-1714
Copyright © 2003 QUALCOMM Incorporated. All rights reserved.

80-xxxxx-x Rev A Page 1 QUALCOMM Proprietary

<Month Year>
 Agenda

• CM Basics
• How is CM Configured?
• How is CM Activated/Deactivated?
• How is CM/HO triggered?
• CM Parameters from various Networks.
• CM Keywords
• CM and SHO
• How to interpret PC Packets during CM?
• Common Failures

80-xxxxx-x Rev A Page 2 QUALCOMM Proprietary

<Month Year>
 CM Overview

• Purpose of CM is to create gaps during normal WCDMA DL and

UL Radio frame Transmission to enable the UE to measure
other WCDMA Frequencies or GSM Cells
• These measurements are then used by the NW to decide
whether the UE should perform handover to neighboring Inter-
RAT or Inter-frequency systems
• Generally this will be triggered at the edge of WCDMA coverage
• CM Patterns are defined based on a bunch of parameters as
shown in the diagram below
• There are 3 main types of CM.
– CM by SF Reduction ( Mainly used in case of AMR voice)
– CM by HLS ( Mainly used in case of PS data)
– CM by Puncturing ( Not Supported)

80-xxxxx-x Rev A Page 3 QUALCOMM Proprietary

<Month Year>
 CM Overview – contd.
#1 #2 #3 #4 #5 #TG PRC
T G p a tte rn 1 T G p a tte r n 2 T G p a tte rn 1 T G p a tte rn 2 T G p a tte r n 1 T G p a tte r n 2

T G p a tte r n 1 T G p a tte rn 2

T r a n s m is s i o n
T r a n s m is s i o n T r a n s m is s i o n T r a n s m is s i o n gap 2
gap 1 gap 2 gap 1

TGSN TGSN

TG L1 TG L2 TG L1 TG L2

TGD TGD

TG PL1 TG PL2

• Additional Parameters
– Scrambling Code Change ( On or Off)
– DeltaSIR, DeltaSIRAfter ( Up to 3 dB in units of 0.1 dB)
– RPP, ITP ( on or Off)
– DL Frame Type ( A or B)
– Allowed TGL Values in slots (3, 4, 5, 7, 10, 14)
– Allowed TGPL Values in frames ( Up to 144)
– Allowed TGD values in Slots ( Up to 269)

80-xxxxx-x Rev A Page 4 QUALCOMM Proprietary

<Month Year>
 How is CM Configured

• RadioBearerSetup/Release/Reconfiguration
• PhysicalChannelReconfiguration
• TransportChannelreconfiguration

80-xxxxx-x Rev A Page 5 QUALCOMM Proprietary

<Month Year>
 How is CM Activated/Deactivated

• Physical Channel Reconfiguration

• Transport Channel Reconfiguration
• Measurement Control

80-xxxxx-x Rev A Page 6 QUALCOMM Proprietary

<Month Year>
 How is CM triggered

• CM Activation is triggered by the following Events

– Event 2D
– Event 1F
• CM Deactivation is triggered by the following events
– Event 2F
– Event 1e
• GSM Handover is Triggered by following Event
– Event 3A
• GSM Handover can also be non Event Based

80-xxxxx-x Rev A Page 7 QUALCOMM Proprietary

<Month Year>
 CM Parameters from various NW

• Nokia
– 2 patterns with TGL = 7 and TGPL = 4 for CM by SF/2
– No Alternate Scrambling Code Change
– Positive DeltaSIR
– 1 patterns with TGL = 7 and TGPL = 3 for CM by HLS ( Only GSM RSSI)
– Event 1F/IE is used to activate/deactivate CM
– PhysicalChannelReconfiguration is used to program CM
– MCM is used to activate it
– Patterns are activated one at a time( GSM RSSI followed by BSIC)
– Handover command form NW come ones BSIC is verified and reported.
– CCO may come without BSIC verification if strongest ARFCN is unique
• Ericsson
– 3 patterns with TGL = 7 and TGPL = 8 for both CM by SF/2 and HLS
– Alternate Scrambling Code Change
– Positive DeltaSIR
– Event 2d/2F is used to activate/deactivate CM
– PhysicalChannelReconfiguration is used to program CM
– MCM is used to activate it
– Event 3A is used to trigger handover

80-xxxxx-x Rev A Page 8 QUALCOMM Proprietary

<Month Year>
 CM Parameters from various NW

• Siemens
– Pattern 1
» RSSI, TGL1 = 7, TGL2= 7,TGD = 53, TGPL = 8
– Pattern 2
» BSIC ID, TGL1 = 7, TGL2= 7,TGD = 38, TGPL = 12
– Pattern 3
» BSIC Reconf,TGL = 14,TGPL = 24
– Alternate Scrambling Code Change
– Positive DeltaSIR
– PhysicalChannelReconfiguration is used to program and
activate CM
– MCM is used later to program the cells
– Event 3A is used to trigger handover

80-xxxxx-x Rev A Page 9 QUALCOMM Proprietary

<Month Year>
 CM Parameters from various NW

• Nortel
– Finite Gap Patterns
– TGL = 14, TGPL = 6
– Alternate Scrambling Code Change
– Zero DeltaSIR
– CM is programmed using Radio Bearer Setup
– CM is activated using MCM
– Periodic reporting sent out as additional measurements with
intra-freq reports
– Pattern 1 for RSSI is activated for 48 frames
– Pattern 2 starts when pattern 1 ends and runs for 546 frames
– CM is activated once every 10 seconds
– NW decides based on MRM when to initiate handovers

80-xxxxx-x Rev A Page 10 QUALCOMM Proprietary

<Month Year>
 Keywords

• Signaling Messages
– reconfiguration
– Measurement
– Radiobearer
– Tgl
– Tgcfn
– codeChange
• F3 messages
– RL failure
– Reset
– Wind-up
– EventID e1a/e1b/e1c/e2d/e1f/e2f/e3a
– HLSYNC
– Going act
– srchcmmeas
– l1cmmeas
– Going Deact
– CM_MEAS
– BSIC
– ScrCodeChg

80-xxxxx-x Rev A Page 11 QUALCOMM Proprietary

<Month Year>
 Event 3A Generation

• Need to satisfy both thresholds ( WCDMA lower and GSM

Higher) to start TTT
• Need to have BSIC verified
• TTT needs to have expired
• TTT gets reset if WCDMA goes above threshold
• We only evaluate events at the end of GSM RSSI
measurements or if a new BSIC is verified

80-xxxxx-x Rev A Page 12 QUALCOMM Proprietary

<Month Year>
 BSIC Mismatch

• Look for F3 message “BSIC found diff”

• We now start a 1 second Forbidden timer for that cell
• Once it comes back it checks if we are getting same tone
• Look for F3 messge “Forbidden”
• We will take it out again for 1 second

80-xxxxx-x Rev A Page 13 QUALCOMM Proprietary

<Month Year>
 CM and SHO

• Check ActiveSetUpdate messages after CM is activated

• Find out whether it is Soft or Softer
• In case of Soft Handover (Addition of a strong cell)
observe SIR Estimate behavior.
• Siemens has an existing issue with CM in SHO

80-xxxxx-x Rev A Page 14 QUALCOMM Proprietary

<Month Year>
 How to interpret PC Log Packets

• Presence of CM is signified by star(*) in the UL/DL TPC bits

corresponding to the gap lengths
• For CM by SF/2
– SIR Target will go up by 3 dB for the frames which are compressed
– In case of positive DeltaSIR, it may go up even beyond that
• For CM by HLS
– SIR Target will only go up in case we have positive DeltaSIR
• SIR Estimate is also expected to go up during CM frames
• CM frames can have low or negative SIR if
– NW is not doing CM and we are doing CM
– Alternate Scrambling Code is turned on at UE and not on NW side or vice
versa
• Normal Frames have low or negative SIR
– NW is doing CM and we are not doing CM
• Both normal and CM frames have low SIR
– We are out of SYNC on opening the gaps

80-xxxxx-x Rev A Page 15 QUALCOMM Proprietary

<Month Year>
 Common Failures

• RL Failure
– CM Gaps being opened at one end only
– CM gaps are opened at wrong frames
– Alternate Scrambling Code related
– SHO related
– Degradation of RF conditions due to handover delays
• Handover Failure
– BSIC ID fails ( Low energy etc)
– BSIC ID mismatch
– Too many cells to be measured
– GSM failure resulting in WCDMA resume
– Non Optimum Event thresholds

80-xxxxx-x Rev A Page 16 QUALCOMM Proprietary

<Month Year>