PDA

View Full Version : Question Event 2D HOCOMM InterFreq and InterRat coexist



kentck86
2011-12-01, 11:40 AM
Hi all,

I am doing optimization for Huawei network. Currently i faced an issue where InterFreq and InterRat coexist,

Currently, my cell was configured to
INTERRATR99PSTHD2DECN0 -14
INTERRATR99PSTHD2FECN0 -12
INTERRATR99PSTHD2DRSCP -108
INTERRATR99PSTHD2FRSCP -104

INTERFREQR99PSTHD2DECN0 -14
INTERFREQR99PSTHD2FECN0 -12
INTERFREQR99PSTHD2DRSCP -95
INTERFREQR99PSTHD2FRSCP -92


However, it was observed IRAT event was triggered based on the Interfrequency event 2D threshold: -95 as per depicted.
22480
22481

Afterward, i came across on the checking of CellHOCOMM setting it is founded the cell was configured to: COEXISTMEASTHDCHOICE:COEXIST_MEAS_THD_CHOICE_INTERFREQ


Can anyone tell me should i configure the
COEXISTMEASTHDCHOICE to

COEXIST_MEAS_THD_CHOICE_INTERFREQ OR COEXIST_MEAS_THD_CHOICE_INTERRAT ?

thank you

agenov
2011-12-01, 02:23 PM
doesnt matter. It only depends on what you want as thresholds for compressed mode. You may leave it as it is and just change different thresholds per your strategy.



Hi all,

I am doing optimization for Huawei network. Currently i faced an issue where InterFreq and InterRat coexist,

Currently, my cell was configured to
INTERRATR99PSTHD2DECN0 -14
INTERRATR99PSTHD2FECN0 -12
INTERRATR99PSTHD2DRSCP -108
INTERRATR99PSTHD2FRSCP -104

INTERFREQR99PSTHD2DECN0 -14
INTERFREQR99PSTHD2FECN0 -12
INTERFREQR99PSTHD2DRSCP -95
INTERFREQR99PSTHD2FRSCP -92


However, it was observed IRAT event was triggered based on the Interfrequency event 2D threshold: -95 as per depicted.
22480
22481

Afterward, i came across on the checking of CellHOCOMM setting it is founded the cell was configured to: COEXISTMEASTHDCHOICE:COEXIST_MEAS_THD_CHOICE_INTERFREQ


Can anyone tell me should i configure the
COEXISTMEASTHDCHOICE to

COEXIST_MEAS_THD_CHOICE_INTERFREQ OR COEXIST_MEAS_THD_CHOICE_INTERRAT ?

thank you

jayk
2011-12-02, 01:36 AM
I will suggest to change interfreq thresholds. Interfreq HO is of no use due to RSCP

INTERFREQR99PSTHD2DRSCP -109
INTERFREQR99PSTHD2FRSCP -106

wolverine
2011-12-02, 04:18 AM
Hi, the UE is configured with a single event 2D. The parameter COEXISTMEASTHDCHOICE determines which of the two is used for the cell in question. From the HEDEX library..

During the concurrent inter-frequency and inter-RAT measurement, the parameter
CoexistMeasThdChoice decides the event 2D threshold:
 When the parameter is set to COEXIST_MEAS_THD_CHOICE_INTERFREQ, the inter-frequency
measurement threshold for event 2D is used.
 When the parameter is set to COEXIST_MEAS_THD_CHOICE_INTERRAT, the inter-RAT
measurement threshold for event 2D is used

So according to what you told us, everything is as designed.

jayk
2011-12-03, 02:02 AM
I think thresholds setting matters more than parameter setting of COEXISTMEASTHDCHOICE. COEXISTMEASTHDCHOICE is set to COEXIST_MEAS_THD_CHOICE_INTERFREQ in network, I am working but we keep INTERFREQR99PSTHD2DRSCP -109, INTERFREQR99PSTHD2FRSCP -106. Always Inter-Rat is triggered before Inter-Freq.

kentck86
2011-12-04, 05:32 PM
I think thresholds setting matters more than parameter setting of COEXISTMEASTHDCHOICE. COEXISTMEASTHDCHOICE is set to COEXIST_MEAS_THD_CHOICE_INTERFREQ in network, I am working but we keep INTERFREQR99PSTHD2DRSCP -109, INTERFREQR99PSTHD2FRSCP -106. Always Inter-Rat is triggered before Inter-Freq.

Jayk...i guess for better user experience wise we should always strategy as Inter-freq triggered first before Inter-RAT for PS services. Anyone agree with me?

melkaiy
2011-12-04, 06:05 PM
kentck86 i agree with you sir.

we should always trigger the inter-freq first before Inter-RAT if you are utilizing 2 carriers of umts.

melkaiy
2011-12-04, 06:14 PM
I think you should change the ec/io threshold of inter-freq and inter-RAT .

ec/io values of inter-RAT should be lower than inter-freq.

for me I will configure COEXIST_MEAS_THD_CHOICE_INTERRAT if your are utilizing only one carrier.


please add reps if this one helps... :)

gprastomo
2011-12-04, 07:26 PM
im not 100% agree,It should based on the strategy.
If you have continuous 2 frequency WCDMA, 1st for R99, 2nd for HSDPA, so i dont think so the interfreq is good, its better directly ho to IRAT.

Its better to have interfreq HO on the border between 2 carriers and 1 carrier, since the coverage between 1st and 2nd is same. In the continuous 2 frequency coverage its better to have SHO and IRAT, Interfreq only for DRRC.

wolverine
2011-12-04, 08:55 PM
Hi kentck86,

Can you copy paste the contents of the physical channel reconfiguration message (after the measurement report of event 2d) to see how the compressed mode patterns are configured on your system?

jayk
2011-12-05, 01:33 AM
Jayk...i guess for better user experience wise we should always strategy as Inter-freq triggered first before Inter-RAT for PS services. Anyone agree with me?

Interfreq at -92 may create ping-pong handovers between 1st and 2nd carriers. InterFreqHo is better on base of EcIo but not on RSCP. I had suggested a change in RSCP values based on my experience.

kentck86
2011-12-05, 11:31 AM
Hi kentck86,

Can you copy paste the contents of the physical channel reconfiguration message (after the measurement report of event 2d) to see how the compressed mode patterns are configured on your system?



Hi Wolverine,

Please find the physical channel reconfiguration message as follows and kindly advise.


PHYSICAL_CHANNEL_RECONFIGURATION (3GPP TS 25.331 ver 7.11.0 Rel 7)


DL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode
Bin : 44 A6 BB 18 (= 1151777560)
rrc-MessageSequenceNumber : 7
message
physicalChannelReconfiguration
later-than-r3
rrc-TransactionIdentifier : 2
criticalExtensions
criticalExtensions
r5
physicalChannelReconfiguration-r5
activationTime : 208
rrc-StateIndicator : cell-DCH
modeSpecificInfo
fdd :
dl-CommonInformation
modeSpecificInfo
fdd
dpch-CompressedModeInfo
tgp-SequenceList
tgp-SequenceList value 1
tgpsi : 2
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : gsm-CarrierRSSIMeasurement
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
tgp-SequenceList value 2
tgpsi : 3
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : gsm-initialBSICIdentification
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
nidentifyAbort : 66
tgp-SequenceList value 3
tgpsi : 1
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : fdd-Measurement
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
dl-InformationPerRL-List
dl-InformationPerRL-List value 1
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 482
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 72
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 26
scramblingCodeChange : codeChange
tpc-CombinationIndex : 0
cell-id
Bin : 6A 51 09 7 (= 111480983)
dl-InformationPerRL-List value 2
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 474
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 73
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 27
scramblingCodeChange : codeChange
tpc-CombinationIndex : 0
cell-id
Bin : 6A 51 09 6 (= 111480982)
dl-InformationPerRL-List value 3
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 288
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 43
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 30
scramblingCodeChange : noCodeChange
tpc-CombinationIndex : 1
cell-id
Bin : 6A 50 2F 5 (= 111477493)


Data (hex):
A2 53 5D 8C 3A B4 10 00 F4 00
22 98 08 00 8D FE 0F 44 C3 54
26 00 46 FF 07 A2 61 A0 C4 02
00 46 FF 07 A2 61 95 1E 20 09
01 A6 81 A9 44 25 E8 ED 00 49
0D 36 0D 4A 21 2D 44 80 01 58
69 E9 6A 50 2F 50

kentck86
2011-12-05, 11:47 AM
im not 100% agree,It should based on the strategy.
If you have continuous 2 frequency WCDMA, 1st for R99, 2nd for HSDPA, so i dont think so the interfreq is good, its better directly ho to IRAT.

Its better to have interfreq HO on the border between 2 carriers and 1 carrier, since the coverage between 1st and 2nd is same. In the continuous 2 frequency coverage its better to have SHO and IRAT, Interfreq only for DRRC.

Hi Sir,

I would agree on your statement if the cell is 2 carriers cell. However,currently my cell is having 3 carriers. Currently the system was configured F1 for R99, F2 & F3 for HSPA. Thus, i guess interfreq HO is a better way. Please comment. thank you

kentck86
2011-12-05, 11:51 AM
Hi all,

I am doing optimization for Huawei network. Currently i faced an issue where InterFreq and InterRat coexist,

Currently, my cell was configured to
INTERRATR99PSTHD2DECN0 -14
INTERRATR99PSTHD2FECN0 -12
INTERRATR99PSTHD2DRSCP -108
INTERRATR99PSTHD2FRSCP -104

INTERFREQR99PSTHD2DECN0 -14
INTERFREQR99PSTHD2FECN0 -12
INTERFREQR99PSTHD2DRSCP -95
INTERFREQR99PSTHD2FRSCP -92


However, it was observed IRAT event was triggered based on the Interfrequency event 2D threshold: -95 as per depicted.
22480
22481

Afterward, i came across on the checking of CellHOCOMM setting it is founded the cell was configured to: COEXISTMEASTHDCHOICE:COEXIST_MEAS_THD_CHOICE_INTERFREQ


Can anyone tell me should i configure the
COEXISTMEASTHDCHOICE to

COEXIST_MEAS_THD_CHOICE_INTERFREQ OR COEXIST_MEAS_THD_CHOICE_INTERRAT ?

thank you


Hi All,

Additional Infos i founded for this cell:

1st Carrier CellHOCOMM was configured to:
COEXIST_MEAS_THD_CHOICE_INTERFREQ

2nd Carrier CellHOCOMM was configured to:
COEXIST_MEAS_THD_CHOICE_INTERRAT

3rd Carrier CellHOCOMM was configured to:
COEXIST_MEAS_THD_CHOICE_INTERRAT

Anyone can advise what is the issue.

gprastomo
2011-12-05, 02:52 PM
Hi My friend,

even 3 carriers, if you have continuous 3 carriers site i would prefer No Interfreq (Interfreq only for DRRC). Only border between 3 carriers and 2 carriers or 1 carrier have interfreq.
If you have continuous 3 carriers so better to have SHO intrafreq rather than interfreq.
Imagine that you have bad coverage that trigger the interfreq, so ue will move to interfreq of the same cell, since the coveragee F1,f2,f3 are the same, so the those interfreq target cell have bad coverage as well, so in this case this interfreq is useless.
If it IFHO to another cell, its not good idea, its better to have SHO to another cell rather than IFHO to another cell. Then if coverage is bad so directly IRAT.

kentck86
2011-12-05, 10:33 PM
Hi My friend,

even 3 carriers, if you have continuous 3 carriers site i would prefer No Interfreq (Interfreq only for DRRC). Only border between 3 carriers and 2 carriers or 1 carrier have interfreq.
If you have continuous 3 carriers so better to have SHO intrafreq rather than interfreq.
Imagine that you have bad coverage that trigger the interfreq, so ue will move to interfreq of the same cell, since the coveragee F1,f2,f3 are the same, so the those interfreq target cell have bad coverage as well, so in this case this interfreq is useless.
If it IFHO to another cell, its not good idea, its better to have SHO to another cell rather than IFHO to another cell. Then if coverage is bad so directly IRAT.

Hi Friend,

Now i get what you meant, in our system here we are more likely to trigger interfreq HO by LDR action for PS services. By the way, mind to describe more about DRRC please?

wolverine
2011-12-06, 01:09 AM
Hi, so it seems that the system configures compressed mode patterns for both inter-freq and IRAT measurements. However to see which one is activated I also need to see the measurement control messages that follow. Can you paste those as well?

You see if only the IRAT compressed mode is activated then naturally all your HHOs will be to 2G.


Hi Wolverine,

Please find the physical channel reconfiguration message as follows and kindly advise.


PHYSICAL_CHANNEL_RECONFIGURATION (3GPP TS 25.331 ver 7.11.0 Rel 7)


DL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode
Bin : 44 A6 BB 18 (= 1151777560)
rrc-MessageSequenceNumber : 7
message
physicalChannelReconfiguration
later-than-r3
rrc-TransactionIdentifier : 2
criticalExtensions
criticalExtensions
r5
physicalChannelReconfiguration-r5
activationTime : 208
rrc-StateIndicator : cell-DCH
modeSpecificInfo
fdd :
dl-CommonInformation
modeSpecificInfo
fdd
dpch-CompressedModeInfo
tgp-SequenceList
tgp-SequenceList value 1
tgpsi : 2
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : gsm-CarrierRSSIMeasurement
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
tgp-SequenceList value 2
tgpsi : 3
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : gsm-initialBSICIdentification
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
nidentifyAbort : 66
tgp-SequenceList value 3
tgpsi : 1
tgps-Status : deactivate
tgps-ConfigurationParams
tgmp : fdd-Measurement
tgprc : 0
tgsn : 4
tgl1 : 7
tgd : 270
tgpl1 : 8
rpp : mode1
itp : mode0
ul-DL-Mode
ul-and-dl
ul : sf-2
dl : sf-2
dl-FrameType : dl-FrameTypeA
deltaSIR1 : 12
deltaSIRAfter1 : 6
dl-InformationPerRL-List
dl-InformationPerRL-List value 1
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 482
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 72
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 26
scramblingCodeChange : codeChange
tpc-CombinationIndex : 0
cell-id
Bin : 6A 51 09 7 (= 111480983)
dl-InformationPerRL-List value 2
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 474
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 73
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 27
scramblingCodeChange : codeChange
tpc-CombinationIndex : 0
cell-id
Bin : 6A 51 09 6 (= 111480982)
dl-InformationPerRL-List value 3
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode : 288
servingHSDSCH-RL-indicator : false
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst : mayBeUsed
dpch-FrameOffset : 43
dl-ChannelisationCodeList
dl-ChannelisationCodeList value 1
sf-AndCodeNumber
sf128 : 30
scramblingCodeChange : noCodeChange
tpc-CombinationIndex : 1
cell-id
Bin : 6A 50 2F 5 (= 111477493)


Data (hex):
A2 53 5D 8C 3A B4 10 00 F4 00
22 98 08 00 8D FE 0F 44 C3 54
26 00 46 FF 07 A2 61 A0 C4 02
00 46 FF 07 A2 61 95 1E 20 09
01 A6 81 A9 44 25 E8 ED 00 49
0D 36 0D 4A 21 2D 44 80 01 58
69 E9 6A 50 2F 50

kentck86
2011-12-06, 02:58 PM
Hi, so it seems that the system configures compressed mode patterns for both inter-freq and IRAT measurements. However to see which one is activated I also need to see the measurement control messages that follow. Can you paste those as well?

You see if only the IRAT compressed mode is activated then naturally all your HHOs will be to 2G.


Hi,

Kindly find the measurement control message as follows:


2


MEASUREMENT_CONTROL (3GPP TS 25.331 ver 7.11.0 Rel 7)


DL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode
Bin : 60 FC 1A D1 (= 1627134673)
rrc-MessageSequenceNumber : 4
message
measurementControl
later-than-r3
rrc-TransactionIdentifier : 1
criticalExtensions
r4
measurementControl-r4
measurementIdentity : 3
measurementCommand
setup
interFrequencyMeasurement
interFreqCellInfoList :
interFreqMeasQuantity
reportingCriteria
interFreqReportingCriteria
filterCoefficient : fc3
modeSpecificInfo
fdd
freqQualityEstimateQuantity-FDD : cpich-RSCP
interFreqReportingQuantity
utra-Carrier-RSSI : false
frequencyQualityEstimate : false
nonFreqRelatedQuantities
dummy : noReport
cellIdentity-reportingIndicator : false
cellSynchronisationInfoReportingIndicator : false
modeSpecificInfo
fdd
cpich-Ec-N0-reportingIndicator : false
cpich-RSCP-reportingIndicator : false
pathloss-reportingIndicator : false
reportCriteria
interFreqReportingCriteria
interFreqEventList
interFreqEventList value 1
event2d
usedFreqThreshold : -95
usedFreqW : 0
hysteresis : 4
timeToTrigger : tt320
interFreqEventList value 2
event2f
usedFreqThreshold : -92
usedFreqW : 0
hysteresis : 4
timeToTrigger : ttt1280
measurementReportingMode
measurementReportTransferMode : acknowledgedModeRLC
periodicalOrEventTrigger : eventTrigger
v4d0NonCriticalExtensions
v590NonCriticalExtensions
measurementControl-v590ext
rrc-TransactionIdentifier-MSP-v590ext : 0


Data (hex):
B0 7E 0D 68 A2 2B 08 38 33 40
06 58 A0 09 74 5C 04 D5 00




2


MEASUREMENT_CONTROL (3GPP TS 25.331 ver 7.11.0 Rel 7)


DL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode
Bin : C1 BF A8 95 (= 3250563221)
rrc-MessageSequenceNumber : 3
message
measurementControl
later-than-r3
rrc-TransactionIdentifier : 0
criticalExtensions
r4
measurementControl-r4
measurementIdentity : 2
measurementCommand
setup
interFrequencyMeasurement
interFreqCellInfoList :
interFreqMeasQuantity
reportingCriteria
interFreqReportingCriteria
filterCoefficient : fc3
modeSpecificInfo
fdd
freqQualityEstimateQuantity-FDD : cpich-Ec-N0
interFreqReportingQuantity
utra-Carrier-RSSI : false
frequencyQualityEstimate : false
nonFreqRelatedQuantities
dummy : noReport
cellIdentity-reportingIndicator : false
cellSynchronisationInfoReportingIndicator : false
modeSpecificInfo
fdd
cpich-Ec-N0-reportingIndicator : false
cpich-RSCP-reportingIndicator : false
pathloss-reportingIndicator : false
reportCriteria
interFreqReportingCriteria
interFreqEventList
interFreqEventList value 1
event2d
usedFreqThreshold : -14
usedFreqW : 0
hysteresis : 4
timeToTrigger : tt320
interFreqEventList value 2
event2f
usedFreqThreshold : -12
usedFreqW : 0
hysteresis : 4
timeToTrigger : ttt1280
measurementReportingMode
measurementReportTransferMode : acknowledgedModeRLC
periodicalOrEventTrigger : eventTrigger
v4d0NonCriticalExtensions
v590NonCriticalExtensions
measurementControl-v590ext
rrc-TransactionIdentifier-MSP-v590ext : 0


Data (hex):
E0 DF D4 4A 9A 23 04 38 33 00
06 5B 28 09 75 9C 04 D5 00


thank you