文档名称 文档密级：

Case Name： IRAT HHO Not Happen Caused by Siemens IRAT HHO Lisence
Description： In I Country, B 3G project, we found that the IRAT HHO from HUAWEI 3G to
Moto 2G not happen. And Moto 2G connect to Siemens Core. There are 3
RNCs’ coverage is same as Moto.
Alarm： NULL
Reason 1. From the KPI daily report, these 3 RNC CS and PS do not have IRAT
Analyze： HHO, the attempt is there, it is means that the IRAT neighbor and RNC
switch are all been defined right.

2. We check the RNC CFG, the regarding IRAT switch is open.

SET HOCOMM:
COEXISTMEASTHDCHOICE=COEXIST_MEAS_THD_CHOICE_INTERFREQ
SET INTERFREQHOCOV:
INTERFREQREPORTMODE=PERIODICAL_REPORTING,
INTERFREQFILTERCOEF=D3,
HYSTFOR2D=4, HYSTFOR2F=4,
WEIGHTFORUSEDFREQ=0,
TIMETOTRIG2F=D1280,
INTERFREQCSTHD2DECN0=-14,
INTERFREQR99PSTHD2DECN0=-14,
INTERFREQR99PSTHD2FECN0=-12,
INTERFREQCSTHD2DRSCP=-95,
INTERFREQR99PSTHD2DRSCP=-95,
INTERFREQR99PSTHD2FRSCP=-92,
TARGETFREQCSTHDECN0=-12,
TARGETFREQHTHDECN0=-12,
TARGETFREQR99PSTHDRSCP=-92,
USEDFREQCSTHDECN0=-12,
USEDFREQHTHDECN0=-12,
USEDFREQR99PSTHDRSCP=-92,
INTERFREQMEASTIME=60;
SET CORRMALGOSWITCH:
PRDREPORTINTERVAL=D500,
HYSTFORPRDINTERFREQ=0,
TIMETOTRIG2D=D320,
TIMETOTRIGFORPRDINTERFREQ=0,
INTERFREQCSTHD2FECN0=-12,
INTERFREQHTHD2DECN0=-14,
INTERFREQHTHD2FECN0=-12,
INTERFREQCSTHD2FRSCP=-92,
INTERFREQHTHD2DRSCP=-95,
INTERFREQHTHD2FRSCP=-92,
TARGETFREQR99PSTHDECN0=-12,
TARGETFREQCSTHDRSCP=-92,
TARGETFREQHTHDRSCP=-92,
USEDFREQR99PSTHDECN0=-12,
USEDFREQCSTHDRSCP=-92,
USEDFREQHTHDRSCP=-92,

2019-7-10 华为机密，未经许可不得扩散 第1页, 共5页

 文档名称 文档密级：

HOSWITCH=SOFT_HANDOVER_SWITCH-
1&INTRA_FREQUENCY_HARD_HANDOVER_SWITCH-
1&ACT_SET_QUAL_SWITCH-1&SIGNAL_HO_SWITCH-
0&INTER_FREQ_HHO_SWITCH-0&INTER_RAT_CS_OUT_SWITCH-
1&INTER_RAT_PS_OUT_SWITCH-1
3. We can check from the above information, the parameter for HUAWEI 3G
RNC is correct, so we doubt there is some issue happen in Moto BSC, so
we check the Moto BSC parameter as below.

From the above information, we can know that the Moto BSC already open
the regarding IRAT HHO switch.
4. After check HUAWEI RNC and Moto BSC, we found that all the IRAT HHO
switch is open, and the IRAT neighbor is also been defined well. And from
RNC and HUAWEI Core sides, we did the signaling trace. Find out that
before the IRAT HHO, HUAWEI Core need prepare the IRAT HHO, at this
time the IRAT HHO fail, so the IRAT attempt counter is 0. The reject reason
is no-resource-available. Now we know, this issue must caused by the
Siemes Core.

2019-7-10 华为机密，未经许可不得扩散 第2页, 共5页

 文档名称 文档密级：

5. After we check Siemens Core, we found that the External 3G to 2G lisence

is empty. Customer did not buy the lisence from Siemens, so that the
Siemens reject the IRAT HHO.
6. So the issue is been located, after discuss with HUAWEI core, we can
convert the 3G signaling to 2G signaling, so Siemens can read the
message and the IRAT HHO can happen. The parameter which are setted
in HUAWEI core is as below:
Handover Parameters for Siemens Adjecent
LAC Parameter Value
Siemens Adjacent
Global cell ID LAC
LA cell name TEST_SIEMENS_HO
MSC number of the LA cell MSC ID
VLR number of the LA cell VLR Number
Mobile network code FFF
Perform roaming analysis NO
Restrict incoming call NO
Restrict outgoing call NO
Location area category LAI
Location area type Adjacent VLR
Multi-area name NULL
IDP Location Number Address Attribute International Number

2019-7-10 华为机密，未经许可不得扩散 第3页, 共5页

 文档名称 文档密级：

Non Broadcast LAI Flag NO

Domain name PUBLIC
Server name LOCAL
Cipher Mode Setting NO
Encryption Algorithm <NULL>
Classmark2 RFC 111.00
Cell Type CGI
Containing Classmark3 IE YES
Containing Chosen Encry Algorithm IE NO
Containing Imsi IE NO
Half Rate Channel Permitting Flag FORBID
Containing DTX IE NO
Containing Integrity Protection IE YES
Containing OBssToNBss IE YES
Containing SRncToTRnc IE YES
Containing Bssmap Service HandOver IE YES
Only Contain FR Speech Version 1 Flag NO
Contain Current Speech Version Flag YES
Support whole net configuration or not when SNA NO
Not Send Classmark Request NO
Inter MSC Handover/Relocation MAP Not Carry
Codeclist NO
Not containing Alternative RAB Configuration NO
Inter MSC Handover Not Support Active Trace NO
Reserved Bit 24 1.00
Inter MSC Handover Not Support HSCSD NO
Reserved Bit 26-Reserved Bit 31 111111
Hot LAI NO
Reserved Bit 1-Reserved Bit 31 0

A. SAI is contained: The option is valid only when Handover Type is set to
GSM to UMTS handover. If the option is selected, the format of origination side
cell handover in the Handover Request message is SAI; otherwise, the
format is GCI. The value is SAI by default. – parameter was set to GCI

B. Chosen encryption algorithm is contained: If the option is selected, the

Chosen Encryption Algorithm IE is contained in the Handover Request
message; otherwise, the Chosen Encryption Algorithm IE is not contained in
the Handover Request message. Parameter set to no

2019-7-10 华为机密，未经许可不得扩散 第4页, 共5页

 文档名称 文档密级：

C. Cipher mode setting – Parameter set to no

7. After change the parameter, the IRAT HHO happen in our test and also can
be found in our daily report:

Suggestion： IRAT HHO related to many part of network, so after we check from RF side and
HUAWEI core side, it is necessary to check other vendor’s equipment. So that
we need cooperate with customer and other depatment closely.
attachment：

Bellary_RNC_303_IOS_2010-05-06-15-32-19.rar

2019-7-10 华为机密，未经许可不得扩散 第5页, 共5页