03 GUL Interoperability Troubleshooting (Drive Test) V1.0

GUL Interoperability Troubleshooting
(Drive Test)
HUAWEI TECHNOLOGIES CO., LTD.

1 Classification and Evaluation
2 Factors
3 Analysis
Page 2
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
Classification and Evaluation
Source Classification Evaluation
CS (MO) service on LTE network fails.
CS (MT) service on LTE network fails, the terminal receive a message indicating that the call cannot be set
The MO CSFB fails/ the MT CSFB missing call
up or the call cannot be reached.
CSFB success rate lower than 99%, the E2E success rate lower than 97%, due to the MOC/MTC failure.
UE returns to the LTE network very slowly after the CSFB call
UE return to LTE network more than 5s after the CSFB call is terminated.
is finished.
For details about the standards for different scenarios, check the contract or baselines.
The indicators are as follows:
The CSFB call set up delay is long
L2U/L2T MTM CSFB: R8 redirection: 8s; R9 redirection: 7s; PSHO: 7s
L2G MTM CSFB: R8 redirection: 12s; R9 redirection: 8s
UE cannot reselect to LTE network or reselect to LTE network UE camps on the GU network too long cannot reselect the LTE network
Drive test slowly Take more than 10s to reselect the LTE network.
Issue UE is disconnected from LTE network due to the incorrect
inter-RAT No signal or no service on UE.
solution or configurations.
L2U PSHO success rate is low PSHO success rate is lower than 95%.
L2U/L2G redirection success rate is low Redirection success rate is lower than 99% (KPI baseline).
The delay of the redirections does not meet the standard.
Reference standard:
L2U R8 redirection: 1.5s
L2U/L2G redirection delay is long
L2U R9 redirection: 1.2s
L2G R8 redirection: 3s
L2G R9 redirection: 1.5s
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

1 Classification and evaluation
2 Factors
3 Analysis

Factors
The KPI formula is incorrect.
The GU&CN equipment version does not support interoperations with LTE. KPI mapping in a swapping scenario is incorrect.
The inter-RAT interoperability process is abnormal due to GU&CN causes. The KPI measurement range is inconsistent before and after an upgrade.
UE capability& Difference between Top UEs
KPI
Definition
Related Product Known issue of a version aversion
NE Version Bug of a product version

Missed or incorrect configuration Synchronized TOP sites
of neighboring GSM, UMTS
Neighbor Parameter
cell
Coverage & RF
Resource interference The switch, parameter, and threshold of inter-RAT interoperation in LTE and
Capacity & Equipment
GU side with incorrect configuration or inappropriately.
The target cell with the weak coverage.
The parameter on CN&UE with incorrect setting.
No dominate cell in the GUL coverage area, the inter-RAT interoperation frequently.
The license is not loaded.
Resource admission on the target side fails
The target CPU is overloaded
The source or the target site with the uplink
interference, or the RF channel is faulty.
The site with the alarms or the faults.

1 Classification and evaluation
2 Factors
3 Analysis

Analysis Action
Action Item
Action 1: Basic parameter check. Base on the problem scenario, to check the parameter. To conform all the parameter with the
correct setting.
Action 2: Known problem Check To analysis the version known problem, compare with the version used on line.
Action 3: Signaling analysis Base on the problem scenario, to collect the E2E signaling to analysis and segment.
1. Parameter check: the configuration of inter-RAT system neighbor cell need to pay attention, such as: carrier(TRX), PLMN, RNCID,
CellID, LAC, RAC, to make sure the info is consist with the configuration on line.
2. To check the product document and precaution, to find the known problem which affect on inter-RAT interoperation.

1 Big CSFB latency
2 Low CSFB success rate
3 UE return to LTE network slowly after CSFB
Analysis 4
Reselection/Handover to LTE network
(Disconnection/Camping Slowly/Ping -Pong)
5 U2L redirection/HO based on service fails.
6 Interoperability Issues Caused by Inter -

Vendor Interworking

Parameter Known Issue Signaling Analysis
Big CSFB latency
The latency of CSFB include two part, the one is the call request on LTE network, the other is the call set up and finished on 3G/2G
network. the parameters involved of the voice service not only in LTE part need to be checked, but also the parameter in 3G/2G network
need to be pay more attention.
L2U CSFB Parameter check L2G CSFB Parameter check
NE Category NE Category
Basic parameters Basic parameters
LTE eNodeB LTE eNodeB
R9 redirection R9 redirection
SRB rate configuration
R9 redirection
R9 redirection
UTRAN classmark report
DMCR
Classmark update
UMTS RNC GERAN BSC
(The DMCR technique can remove the optimization
delay of reading SIB11/12.)
BSS identity query
RAU request delay procedure

Sending the SI13 in BCCH ext
MME TAI list and LAI planning
MME TAI list and LAI planning
Optional NAS procedure after
Optional NAS procedure after CSFB MSC CSFB
MSC
Inter-MSC CSFB Inter-MSC CSFB
The details of the parameter please click the attachment:

Big CSFB latency
NE Problem Description Preventive Measure/Solution

To solve the RIM procedure failed issue between HW and other vendors'
eNodeB Upgrade the current version to BSC6900 V100R005C00SPC390 or later.
equipment.(R9 redirection scenarios)
1. Upgrade the current version to BSC6900 V900R015C00SPC520 or later.

To solve the key SIB message with the long broadcast period
2. Enable Flash CSFB that is based on R9 redirection CSFB.
In the Flex scenarios, the RNC cannot replay the "Direct Information
Upgrade the current version to BSC6900 V900R014C00SPC535/V900R015C00SPH518 or later.
Transfer" message which include the RIM info to CN correctly.
UMTS RNC The SIB3 message cannot contain the Deferred measurement control
Upgrade the current version to BSC6900 V900R014C00SPC535 or later.
reading.
The service access delay is long when a CSFB UE returns to the UMTS Upgrade the current version to BSC6900 V900R015C00SPH518 or later. For details, see descriptions and
network. impact analysis in release notes.
An inter-RAT migration fails, causing that the CSFB procedure cannot be
Upgrade the current version to BSC6900 V900R014C00SPH532 or later.
triggered or the delay increases.
In interoperability between GSM and LTE networks, no respond message is

1. When the RIM procedure involves Huawei LTE eNodeB, modify the eNodeB switch.
GSM BSC received after the LTE network sends the RAN INFORMATION REQUEST
2. When the RIM procedure involves other vendors, upgrade the current version to V900R014C00SPC535.
to the GSM network.
P1 1. Enable the DMCR function in the UTRAN network.

(Qualcomm The L2U with R9 redirection function of Qualcomm 8960 chip is incomplete. 2. If the LTE-to-UMTS R9 redirection function is normal on Qualcomm chip 8974/9615, the eNodeB does
8960 chip) not need to enable DMCR.
Details:

Big CSFB latency
MO CSFB based on R8 redirection MO CSFB based on PSHO
UE eNodeB RNC MME MSC SGSN UE eNodeB RNC MME MSC SGSN
1.Extended Service Request 1. Extended Service Request

(containing a CS Fallback Indicator)
(containing a CS Fallback Indicator) Part 1: UE set up a CS call
(CSFB)request on LTE
2. S1-AP Message
(containing a CS Fallback Indicator)
network, CS fall back to 3G
2.S1-AP Message with CS Fallback Indicator by redirection or PSHO.
S1-AP Response Message
S1-AP Reponse Message
3. Optional measurement report
3.Optional measurement report

4. PS handover preparation phase
4. RRC Connection Release with UTRAN frequency
Handover Command
Handover
S1 UE context release Command
5. LAU, combined RAU/LAU, or RAU and LAU 5.CS call establishment procedure with LAU or combined RAU/LAU
Part 2: Location update
Part 3: set up the voice

6.CS call establishment procedure 6.PS handover execution phase
service at 3G network

Big CSFB latency Parameter Known Issue Signaling Analysis
L2U Redirection:
ESR – RRC Release – RRC RRC Connection Setup CM service

MO CSFB
Connection Connection Setup CMP – CM service Request – Call Call Proceeding-- Altering E2E
Procedures
Release CMP Request Proceeding
Delay baseline 200 1000 0 800 3400 5400

Release – RRC
MT CSFB Call Proceeding ESR – RRC RRC Connection Setup –
NA Connection Setup
Procedures – ESR Connection Release Setup CMP – Setup Altering
CMP
Delay baseline 400 200 1000 600 900
L2U PSHO:
ESR – MobilityFromEUTRAC 3G Handover to UTRAN

MO CSFB ommand->3G CM service Request
MobilityFromEUTRA Handover to UTRAN Complete – CM service Call Proceeding-- Altering E2E
Procedures – Call Proceeding
Command Complete Request
Delay Base on MR: 700

200 200 800 2800 4700
baseline Blind: 100
MobilityFromEUTRACommand- 3G Handover to
MT CSFB Call Proceeding ESR – Setup –
NA >3G Handover to UTRAN UTRAN Complete–
Procedures – ESR MobilityFromEUTRACommand Complete Altering
Setup
Delay
400 700 200 600 900
baseline

Big CSFB latency Parameter Known Issue Signaling Analysis
L2G Redirection:
Reference Delay
CSFB Delay Segment Optimization Action
(ms)
Idle mode: 205
Extended Service request-
Intra-LTE delay Connected mode: None
>RRCConnectionRelease
50
Delay of the UE in searching RRCConnectionRelease->First GERAN
1000 Depending on UE capability
the GERAN network SI
Delay of the UE in reading the First GERAN SI->CM Service 1. Enable Flash CSFB.
1000-2000
GERAN network SI request/Location Update Request 2. Send SI13 on BCCH ext. This decreases the delay by 1s to 1.2s.
MOC 1. Plan TAI list and LAI on the RAN side to prevent the LAU procedure.
2. Disable unnecessary IMEI query process on the CN. This decreases the delay by 500 ms.
3. Disable the authentication process on the CN in CSFB scenarios. This decreases the delay by 1s
CM service request/ Location Update to 1.5s.
Delay of the UE in initiating an Request ->Call proceeding 1500-4000
4. Disable the encryption process on the CN. This decreases the delay by 200 ms to 700 ms.
MO call on the GERAN network 5. Disable UTRAN Classmark report on the BSC. This decreases the delay by 235 ms.
6. Disable IMSI query on the BSC. This decreases the delay by 235 ms.
7. Enable classmark update optimization on the BSC. This decreases the delay by 235 ms.
Call proceeding->alerting 5600-7500 Refer to optimization actions on the MOC.
Idle mode: 205
Extended Service request- The paging delay in idle state is affected by the eNodeB paging cycle. In commercial-use networks,
Intra-LTE delay Connected mode:
>RRCConnectionRelease set this parameter considering UE power consumption and paging delay.
50
Delay of the UE in searching RRCConnectionRelease->First GERAN
1000 Depending on UE capability
the GERAN network SI
MTC Delay of the UE in reading the 1. Enable Flash CSFB.

First GERAN SI->Paging response 1000-2000
GERAN network SI 2. Send SI13 on BCCH ext. This decreases the delay by 1s to 1.2s.
The same as optimization actions on the MOC side in the segment CM service request/ Location
Delay of the UE in initiating an Paging response->call confirmed 600-3000
Update Request ->Call proceeding
MO call on the GERAN network
Call confirmed->alerting 600-1400 Restricted by GERAN network load. The optimization method is to be provided.

1 Big CSFB latency
Analysis 4
Interoperability Issues Caused by Inter -

6 Vendor Interworking

Low CSFB success rate Parameter Known Issue Signaling Analysis
 Low CSFB success rate

 CS (MO) service on LTE network fails
 CS (MT) service on LTE network fails (miss call): the terminal receive a message indicating that the call
cannot be set up or the call cannot be reached
 There are many element relative to CSFB E2E service, the license and switch of CSFB on every element is
not the same. The CSFB fails, the parameter on the E2E element need to be checked according to the CSFB
service application requirement.
 The parameter need to be checked:

A large proportion of MT CSFB calls may fail for UEs in the idle mode: the value of Paging DRX(rf32) in the
S1 Paging message and the value of the Default Paging cycle(rf128) on the air interface is different when
connect with other vendor's MME. The MT CSFB call failed after the CS call failed fall back to 2G3G network,
or CSFB was cancelled.
The CSFB process will be failed, when the MME sends an initial UE Context setup or Mod UE Context
Until there is the uplink signaling or service request received by UE.
UEtime the eNodeB is performing an
request message containing the CSFB indicator to the eNodeB, at same
intra-F HO procedure, so eNodeB will replay a CSFB preparation failure.
CSFB to UMTS basedAfter FR is fail:

on PSHO enable, UE search for the target LTE cell
For redirection-based L2G CSFB,
when resources for thewith
RNCthecell
bigare
delay dueLDR
in the to the inappropriate G/U2L
state.
RNC BSC cell codeneighbor if UEs access fake base stations,
eNodeB when UMTS resources planning; the MT CS
or CE resources arecall will be fail when
congested.
thefake base station CSFB calls will be failed.
UE searching for LTE cell.
P-GW MME MSC

The details please
In inter-MSC scenarios, the MSCs must support the MTRR or MTRF (MTRF is recommend). Otherwise, MT CSFB calls fail. click the attachment:
In MSC pool networking, IMSIs are used for initiating MT CSFB calls, the MT CSFB will be failed probability.
When Huawei USN9810 V900R012C00SPH311 is connected with the MSC is another vendor, MT CSFB calls fail with a certain probability.
During the inter-RAT TAU procedure, the ePC triggers the detach procedure due to the Update Bearer procedure for the QoS parameter change with the CSFB
procedure at the same time, the CSFB service will be failed.

If CSFB call failures still occur after parameter check and known problem troubleshooting, perform E2E signaling tracing, analyze and
locate problems segment by segment.
RIM procedure failure Check the if the eNodeB receive the RIM info: Received: focus on locating problems on the eNodeB side
DSP UTRANRIMINFO/DSP GERANRIMINFO Not Received: to check the standard signaling on the NE which
relative to the RIM procedure, find the failure and locate.
Check and Analysis Action
Check whether the UE sends an "Extended Service request message" Not Send: collect the UE logs, send to R&D engineers for analysis.
EIUSMOD TEMPOR
Check whether the eNodeB has receivedINCIDIDUNT
the message which contains theCS
Both MO&MT CSFB call failed Fallback Indicator over the S1 interface:
If NOT: contact MME engineers for problem analysis.
INITIAL CONTEXT SETUP REQUEST/
UE CONTEXT MODIFICATION REQUEST
The eNodeB can triggered the redirection/PSHO process to enable the UE If NOT: Check the eNodeB parameter configuration, and correctly
access to the target UTRAN or GERAN network. turn on the related algorithm switches.
The eNodeB has triggered the redirection/PSHO process but the UE didn't Collect related E2E data, and send the data to R&D engineers for
setup a CS call in the target GSM/UMTS network. analysis.
Check and Analysis Action

MSC sends a Paging request message to the MME over the SGs interface. If NOT: contact MSC engineers for problem analysis.
MSC pool networking, the Paging request message sent by the MSC over the SGs
interface must contain the TMSI IE.
Check the Paging request message sent by the MSC over the SGs interface contains the TMSI IE.
Non-MSC pool networking, the MSC is not requested to contain the TMSI IE in the Paging
request message.
Connect mode: check the "CS service notification" message sent from the MME to the UE.
If NOT: contact MME engineers for problem analysis.
Idle mode: check the "S1AP Paging"(CN domain=cs) message sent by the MME.
MT CSFB call failure If the SGs Paging request message sent by the MSC contains the TMSI IE, the CS
Check the "CS service notification/S1AP Paging" message sent by the MME include the UE ID is TMSI/S-
service notification or S1AP Paging message sent by the MME must contain TMSI/S-
(miss call) TMSI or IMSI.
TMSI for initiating the paging process.
If NOT:receive any CSFB paging message, analyze the problem by referring to X
Check whether the UE have received the "CS service notification message/Uu interface paging" message.
Solutions for Paging Failures.
If NOT: the UE may be in a poor LTE coverage area:
UE in idle mode can access the LTE network to respond to the paging request.
Optimize the LTE network coverage; L2U/L2G reselection threshold.

1 Big CSFB latency
Analysis 4


UE return to LTE network slowly Parameter Known Issue Signaling Analysis
After CSFB, the delay of UE return to LTE network depend on the UTRAN/GERAN network strategy and Fast Return.
Parameter
UTRAN networkcheck _UMTS
Fast Return

Parameter check _GSM:

Suggest
GERAN to use the
CSFB callversion
After aV900R014C00SPC520 WCDMA
is terminated,
andtheRNC R14C00SPH538/R15C00SPH512
RNCare
later should andnetwork
enable the UE return to LTE
recommended after. as quickly as possible.
TheR14 versiontwo
following without license,
methods R15
can be version is the commercial feature, the FR controlled by license.
used:
•
Feature and license Information:
Fast Return: After the call is released, the RNC sends an RRC release message, which contains an LTE frequency as the redirection frequency. the UE can return to the
Feature ID Feature Name License description Element
Feature
LTE ID at first timeFeature
network Name License Control Item ID License Control Item Name
WRFD-140226 Fast Returnafter the
from UMTScall release
to LTE Fast Return from UMTS to LTE( per Erl) RNC
• Reselection: After
WRFD-140226 Fast returning
FastLTE
to the idleLTE
Reselection
Return from UMTSatto2G
state, theReturn
CS Fast UE returns to the LTE network using
from UMTS to LTE(per kbps) RNC
the reselection means.
GBFD-511312 LGMIFLRGCR Fast LTE Reselection at 2G CS Call Release (per TRX)
Call Release
 Key
GERAN parameters:
network
Version Fast Return :
Element MO Parameter ID Suggestion Configuration
 Reselection:
MO In a co-coverage area of the GSM
Parameter
UCORRMALGOSWITCH ID and LTE networks,
HoSwitch after
Need a CSHO_UMTS_TO_LTE_FAST_RETURN_SWITCH,
to select call in the
Setting GSM
Notes or network
Impact is terminated, the the
to enable UEFRcamps in the call release cell and starts cell
in RNC level
reselection
R14 measurements. When an LTE neighboring
UALGORSVPARA
cell meets Suggest
RsvSwitch3
the cellto reselection conditions, the UE return to the LTE network through cell reselection. Because the UE
select RESERVED_SWITCH_3_BIT12, to enable the FR. Notice: R14SPH535 start to support this parameter.
GLTENCELL SPTRAPIDSEL Set this parameter to SUPPORT for neighboring LTE cells.
needs to receive system messages and perform cell reselection measurements before initiating GSM-to-LTE cell reselection, the time for the UE to return to the LTE
FASTRETURNMEASSPT RsvSwitch4
UALGORSVPARA [R15] Set this parameter
Suggest to select to OFF.
RESERVED_SWITCH_4_BIT15, to enable the FR between Iur. Notice: R14SPH535 start to support this parameter.
network is long.
GCELLPRIEUTRANSYS
EUTRANPRI/ UTRANPRI Set EUTRAN Priority to a value greater than that of UTRAN Priority.
 Fast LTE Reselection:UCORRMALGOSWITCH HoSwitch
When the Fast LTE Reselection at 2G CS Need
Call to select HO_UMTS_TO_LTE_FAST_RETURN_SWITCH
Release feature is enabled, a UE will return to the LTE network according to the cell selection indicator
RNC
AITFOTHPARA DecodeCSFBInd
UCORRMPARA
after the CS call in the GSM [R15]
PerfEnhanceSwitch3
network is released. The UE doesSetnot
this parameter
Suggest
need toto to On cell
when this featurecalculations
is valid only for
PERFENH_PS_FAST_RETURN_LTE_SWITH
perform reselection andCSFB
can calls.
directly select a target LTE cell, improving the cell
R15
reselection speed. UCELLHOCOMM
AVer Need to select HO_UMTS_TO_LTE_FAST_RETURN_SWITCH
GSM_PHASE_2Plus
FastReturnToLTESwitch
Cell
BSCBASIC AbisVer Suggest to select PERFENH_PS_FAST_RETURN_LTE_SWITCH
GSM_PHASE_2Plus
UALGORSVPARA RsvSwitch4 Suggest to select RESERVED_SWITCH_4_BIT15, to enable the FR between Iur. Notice: R15SPH512 start to support this parameter.
UmVer GSM_PHASE_2Plus
R14&R15 Cell ADD EARFCN; NPriority RNC need to add the EARFCN, the priority must be higher than UMTS.
UCELLNFREQPRIOINFO

NE Issue Description Impact of the Issue Preventive Measure/Solution

If the best cell for the UE is a cell under the DRNC, the RNC does not include Upgrade the current version to
UEs cannot return to the LTE network using the Fast Return an LTE frequency in the RRC connection release message. As a result, the V900R014C00SPH538/V900R015C00SPH512 or later versions.
feature. UE cannot reselect to an LTE cell using the Fast Return feature.
WCDMA RNC A UMTS/LTE dual-mode UE initiates a CSFB procedure. After the UE is Upgrade the current version to V900R014C00SPC535 or later
handed over from the LTE network to the UMTS network, the UE cannot versions and enable the Fast Return feature.
Dual-mode UEs cannot return to the LTE network from the
return to the LTE network through fast reselection in the following scenarios:
UMTS network through fast reselection.
•Scenario 1: PS services are in progress when the CS call is released.
•Scenario 2: Iu-PS signaling connections exist when the CS call is released.
When a UE that complies with 3GPP Release 8 is the called party of a CSFB Upgrade the current version to V900R014C00SPC520 or later
UEs that comply with 3GPP Release 8 cannot return to the call in an inter-location area (LA) scenario, the UE cannot return to the LTE versions.
LTE network from the GSM network through fast reselection. network through fast reselection. Enable the GSM-to-LTE fast reselection function, and set bit 20
of BSCRESERVEDPARA21 to 1.
GERAN BSC
When the GSM-to-LTE fast reselection function is enabled If the channel release message contains the TARGET_PCID IE and this IE Upgrade the current version to V900R014C00SPC520 or later
and the channel release message contains the indicates that the LTE cell is unavailable, the UE cannot return to the LTE versions.
TARGET_PCID information element (IE), UEs may fail to network through fast reselection.
return to the LTE network through fast reselection.
The UE with the autonomous fast return function cannot return to the LTE 1) Determine the LTE coverage conditions based on reports of
The UE autonomous fast return fails for the following
network quickly. LTE measurements performed on the GSM network or the
reasons: 1) Weak coverage of the LTE network; 2)
UE measurement result in idle state.
Abnormal service drop on the GSM network, during which
2) Analyze the causes of service drops that occur on the GSM
the channel release message is not sent.
network.
Currently, most networks of China Mobile do not support fast UEs that are not official terminals of China Mobile do not support the It is recommended that China Mobile enable the G2L cell
return from GERAN or G2L cell reselection. Therefore, UEs autonomous fast return feature. These UEs return to the LTE network slowly reselection function or the Fast Return function on the network
in these networks are required to be capable of autonomous after CSFB calls are released. side.
fast return. However, UEs that are not official terminals of Otherwise, this problem cannot be resolved.
Network policy
China Mobile, such as roaming UEs and iPhone 5s released
in Hong Kong, do not support the autonomous fast return
feature. As a result, these UEs return to the LTE network
slowly after CSFB calls are released.

 View the traced messages to check whether the UTRAN/GERAN network immediately sends the “RRC
Connection Release/Channel Release message” that carries the LTE target carriers after finishing a CS call.
 If the UTRAN/GERAN network does not send the message, collect single-user signaling messages and the
product logs on the RNC/BSC, and provide them to the maintenance engineers for problem locating.

1 Big CSFB latency
Analysis 4


Reselection/Handover Issues Parameter Known Issue Signaling Analysis
UE Reselection/Handover Issue Analysis
UE cannot camp on the LTE network: During the inter-RAT reselection, redirection, or handover procedure, the LAU/RAU/TAU update
is rejected and the UE cannot camp on the LTE network, or need long time to camp on the LTE network. Almost, due to the signal or
measurement reasons.
The problems may be caused by RAN- and core network-related reasons, which are generally incorrect data configuration or
conflicts between camping and reselection policies of different standards.
Preferentially check inter-RAT interoperability parameters based on problem scenarios, especially for ping-pong reselections. Ensure
that the difference between the G2L/U2L reselection threshold and the threshold for LTE measurement is 2 dB or more.


The UE updates its location area after being handed over from an LTE cell Upgrade the current version to V900R014C00SPH538 or later versions.
to a UMTS cell. After the location update is complete, the RNC delivers the
Ping-pong handovers between UMTS and LTE cells service-based measurement configuration related to the LTE network to
occur. the UE. If the UE reports an LTE cell that meets the handover or
redirection conditions, the RNC immediately hands over or redirects the
UE back to the LTE cell.
WCDMA RNC The handover fails or ping-pong redirections occur, affecting user Upgrade the current version to V900R014C00SPH538 or later versions.
The RNC hands over or redirects a UE that has not been
experience.
registered in the LTE network to an LTE cell.
After the UE is redirected from an LTE FDD cell to a UMTS cell, the RNC Upgrade the current version to V900R014C00SPH532 or later versions.
Ping-pong redirections between UMTS and LTE FDD cells redirects the UE back to the LTE FDD cell if the UE reports the event 3C
occur. measurement report of the LTE FDD cell, resulting in ping-pong
redirections.
Inconsistent protocol understanding between the UE and Once this issue occurs, the UE repeatedly reestablishes its RRC SriLowLoadThd parameter for the eNodeB of the LTE TDD network must be set to
the eNodeB results in an RRC connection reconfiguration connections and cannot process services for a long period. match uplink-downlink configurations:
failure during the E-RAB modification procedure after the Uplink-downlink configuration 0 or 1:
UE returns from the GSM/UMTS network to the LTE MOD CellPucchAlgo: LocalCellId = 0, SriLowLoadThd = 5;
network. As a result, the UE repeatedly reestablishes its Uplink-downlink configuration 2 or 5:
RRC connection. MOD CellPucchAlgo: LocalCellId = 0, SriLowLoadThd = 0;
eNodeB If more than three target-RAT frequencies are configured for the LTE or According to the test conclusion, you are advised to perform the following optimization
Multiple TD-SCDMA frequencies are configured for the TD-SCDMA network, the network reselection is slow, which prolongs the on the live network:
eNodeB, resulting in a slow L2T reselection. Similarly, if delay of reselection. 1. Configure three 3G frequencies (no more than four 3G frequencies) on the LTE
multiple LTE frequencies are configured for the TD- network.
SCDMA network, the TD-SCDMA-to-LTE reselection is 2. Configure no more than three LTE frequencies on the 2G network.
slow. 3. Configure no more than three LTE frequencies (neighboring LTE cells must be
completely configured) on the 3G network.

Reselection
U2L/G2L Reselection
L2U/L2G Reselection
Issue Description Check and Analysis
Redirection Action
Issue Description Check and Analysis Action
This
Check issue
andismake
related
sureto the
the inter-RAT
U/G access network: message
reselection L2U/L2GSIB6 Check Redirection
the L2U/L2G reselection parameters
The UE does not trigger 1. Check whether the U/G access network supports U2L/G2L
UE cannot initiate reselection (L2U)/SIB7 (L2G) have send successful by eNodeB. on the eNodeB, If the eNodeB does not
reselection to the 3G/2G reselection, and the UMTS network has send SIB19. Checksendthe U and G access network
to the LTE network after Check the reselection priority between L/U/G, make sure the successfully the message.
2. To confirm is
configuration the LTE carriers
correct. and carrier
The service priority
interruption infoduring
delay setting
thecorrectly, parameter
redirection will setting and also get the help
be increased.
move the
During intoblind
the redirection,
networkLTE coverage the UEtheaccesses a carrier, which
carrier reselection proiority
It is of thetoLTE
related the is higher than
neighboring U/G U and
cell G.
configuration from
on the U&G engineers.
eNodeB: Check the neighboring WCDMA/TD-SCDMA/GERAN carrier/cell
area
is not the carrier include in the "RRC Connection Release" for reselection to LTE is configured in conformity
3.
UE Make
must sure threshold
supports the Configure
target U/G the BlindHoPriority/ConnFreqPriority
frequency band. parameter
Check the according to
inter-RAT the neighboring
interoperation U/G
capability configurations.
message from the LTE network.
with the network plan. carrier/cell, and ensure that carriers with a high of priority
the UE. are in a good coverage condition.
UE radio conditions should reach the reselection requirment. If NOT: move the UE to an area out of the
The inter-RAT RAU fails. This problem is generallyThis related to the
problem UE and core
is generally relatednetwork.
to the UE Analyze
andLTESGSN, Contact
analyzeMME
coverage. engineers
the mssages for SGSN
on the issue first. Contact SGSN engineers for issue analysis and locating.
the
Thismessages on thetoMME
issue is related the UEsideandfirst.
SGSN, analyze the signaling Contactanalysis and locating.
SGSN engineers for issue analysis 1. Change a UE that supports R9 redirection.
The inter-RAT RAU fails. Check the value of "EMM cause" in the TAU reject message if possible.
messages on the SGSN side 1.Checkfirst.whether the UE supports R9 redirection. and locating. 2. Turn on the RIM-related switches by referring to the configuration
If the value is "No EPS bearer context activated", the cause may be one
R9Inter-RAT
redirectionTAU
is configured for the eNodeB, but
failed after of the following: R8 2.Check whether the R9 redirection is licensed/enabled at the eNodeB/MME/SGSN/RNC/BSC. guide for each product.
redirection is still triggered.
the UE reselect to the LTE 3.Check whether the eNodeB has obtained the neighboring cell SI of the target network through 3. If the neighboring cell SI is not obtained, collect eNodeB, MME,
1. The UE has deactivated theall PDP
RIM contexts.
procedure. TAU failures are normal. SGSN, and RNC/BSC signaling messages, and get the help from
network. R&D.
2. The UE has accessed a GGSN which does not have the P-GW
Contact CN engineers for a solution.
capability.
Contact the GGSN/P-GW engineers to
3. The cdr version of the integrated gateway GGSN setting incorrectly.
PS HOmodify L2Uthe configuration.
Check whether the UE has the PSHO capability. If the UE does not support PSHO, use a UE that supports PSHO.
If the UE does not report event B1/B2, check whether the WCDMA/TD-SCDMA neighboring
The L2U PSHO feature has been enabled on the eNodeB, but For measurement-based PSHO, check whether the UE reports event
cell configurations match with the live network. If the neighboring cell configurations are
the PSHO procedure is not triggered. The redirection procedure B1/B2.
correct, send UE logs to R&D engineers for troubleshooting.
is triggered.
The UE moves too fast. (The blind A2 threshold is met before event
This problem is normal.
B1/B2 is reported.)
After triggering the PSHO and sending a HANDOVER
Trace messages on MME/SGSN/RNC, and locate the NE where the
REQUIRED message to the MME, the eNodeB receives a After locating the NE, contact engineers of the NE to jointly resolve the problem.
handover preparation failure occurs.
HANDOVER PREPARATION FAILURE message.
The eNodeB sends a MobilityFromEUTRACommand message
to the UE, but the UE fails to access the target UMTS cell.
Collect UE logs, and send them to the R&D engineers for troubleshooting.
Instead, the UE initiates an RRC connection reestablishment
procedure.

1 Big CSFB latency
Analysis 4


U2L base on redirection/HO fails Parameter Known Issue Signaling Analysis
Redirection/HO based on service: the user with the PS service only in the UMTS network, when the UE move to the LTE coverage area, the UE can redirection/HO to
LTE network.
The version of RNC R14 only support based on measurement U2L redirection/HO, the RNC R15 support the blind U2L redirection.
PSHO requires that the UE, MME and target LTE network all support U2L PSHO
The following table describes the key parameters for service-based U2L redirection/handover used in BSC6900 V900R014:
Feature MO Parameter ID Setting Notes or Impact

ULTECELL SuppPSHOFlag Set this parameter based on whether a neighboring LTE cell supports PSHO.
WRFD-020129 If only the redirection mechanism is required, set this parameter to NotSupport.
Service-Based PS If the POSO mechanism is required, set this parameter to Support.
Service Redirection
[RNC-level] UU2LTEHONCOV LTEMeasTypOf3C, U2LTEFilterCoef, Set parameters related to event 3C measurements based on the network planning.
from UMTS to LTE
[Cell-level] U2LTEMeasTime, LTEMeasQuanOf3C,
Hystfor3C, TrigTime3C, TargetRatThdRSRP,
UCELLU2LTEHONCOV TargetRatThdRSRQ
WRFD-140218 UTYPRABBASIC EUTRANSHIND This parameter specifies whether a service bearer allows the handover to an LTE network.
Set this parameter to HO_TO_EUTRAN_SHOULD_BE_PERFORM.
Service-Based PS
Handover from UMTS UCORRMALGOSWITCH HoSwitch Select HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH to
to LTE enable service-based UMTS-to-LTE redirection.
Select HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PSHO_OUT_SWITCH to
enable service-based UMTS-to-LTE PS handover.
ADD ULTECELL / The UMTS cell in use must be configured with the neighboring LTE cell.
ADD ULTENCELL /

Preventive
Problem Description Impact
Measure/Solution
If the neighboring LTE FDD or LTE TDD cell of the UMTS cell is configured with more than four frequencies, the
The number of LTE FDD or LTE TDD frequencies is more than four during LTE measurement control delivered by the RNC indicates that this LTE FDD or LTE TDD cell also have more Upgrade the current version to
measurement control. than four frequencies. In this case, a UE cannot correctly measure the number of LTE frequencies, and V900R014C00SPH538 or later.
therefore the UE cannot be redirected to or be handed over to the LTE cell.
The RNC hands over or redirects a UE that is not registered in the LTE Upgrade the current version to
The handover fails or ping-pong redirection occurs, affecting user experience.
network to an LTE cell. V900R014C00SPH538 or later.
The UE updates its location area after being handed over from an LTE cell to a UMTS cell. After location
updating, the RNC delivers the UE service-based LTE measurement control. If the UE reports an LTE cell that Upgrade the current version to
A UE performs ping-pong handovers between UMTS and LTE cells. meets the handover or redirection conditions, the RNC immediately hands over or redirects the UE back to the V900R014C00SPH538 or later.
LTE cell.
If HSPA/HSPA+ services cannot coexist with the compressed mode and service-based UMTS-to-LTE handover
The compressed mode of the service-based LTE measurement control Upgrade the current version to
or redirection takes effect, the RNC repeatedly switches between the two service bearer channels: DCH and
causes ping-pong handovers on the channel. V900R014C00SPH538 or later.
EDCH/HS-DSCH.
The CPU usage of the SPU board increases when service-based UMTS-to- When service-based UMTS-to-LTE handover or redirection takes effect, the more the neighboring LTE cells are Upgrade the current version to
LTE handover or redirection takes effect. configured on the UMTS cell, the more the CPU usage of the SPU board increases. V900R014C00SPH538 or later.
UEs performing an intra- or inter-RAT migration to the UMTS network Upgrade the current version to
Service-based UMTS-to-LTE redirection cannot take effect.
cannot be redirected to an LTE network. V900R014C00SPH538 or later.
UEs performing PS services cannot be handed over from a UMTS network After DRD is performed during PS service establishment or reconfiguration, the UEs cannot be handed over or Upgrade the current version to
to an LTE network after DRD is performed. redirected from a UMTS cell to an LTE cell even if the conditions are met. V900R014C00SPH512 or later.
If both HSDPA services and HSPA+ services can coexist with the compressed mode and a UE performing DC-
The UEs performing DC-HSDPA services cannot be handed over or Upgrade the current version to
HSDPA services starts the compressed mode, the UE does not send the LTE measurement report and the
redirected from a UMTS cell to an LTE cell. V900R015C00SPH516 or later.
RNC cannot hand over or redirect the UE to an LTE network.

 For redirection, check whether the RRC release message delivered by the RNC contains LTE frequency information.
 For inter-RAT handover, check whether the problem occurs during handover preparation or handover execution based on
the handover procedure.
 Collect logs on the RNC side and single-UE signaling messages. Then, provide the information for R&D engineers.

1 Big CSFB latency
Analysis 4
Interoperability Issues Caused by

6 Inter-Vendor Interworking

Interoperability Issues Caused by Inter-Vendor Interworking
 Interconnections with other vendors' devices exist on live networks, mainly in the following scenarios:
1) The RAN device (3G or LTE) are provided by Huawei and another vendor.
2) The core network device is provided by another vendor, and the RAN device is provided by Huawei.
 When identifying the interoperability issues, check whether the issues are caused by Huawei devices or other vendors' devices
based on Huawei parameter baseline.
For details about the key parameters, see GUL Parameter Baseline & Consistency Check. If Huawei network parameters comply
with the baseline, check whether the issues are known ones.

After Flash CSFB is enabled on the eNodeB, it In eRAN6.0 and later versions, enable the standard coding
The 3G network devices are provided by another vendor. When Flash CSFB is enabled, the eNodeB actually cannot be initiated during DT. by using the following command:
cannot obtain the RAN information management (RIM) information of the corresponding external cell. MOD GLOBALPROCSWITCH:
RimCodingPolicy=StandardCoding;
The 3G network devices are provided by another vendor. When Flash CSFB or RIM is enabled, the size of Because the eNodeB deletes the RRC On the eNodeB side, change the maximum number of cells
the 3G cell system information received by the eNodeB is too large as the system information in the RIM Connection release message used for CSFB carried in the redirection message to 3 (recommended value)
WCDMA
information contains SIB11. When there are too many UTRAN cells (eight) carried in the redirection redirection, the UE cannot be redirected to the 3G using the following command:
RNC
message configured by the eNodeB, the size of the RRC Connection release message sent by the network for the CS service, resulting in the CSFB MOD INTERRATHOCOMM: CellInfoMaxUtranCellNum=3;
eNodeB is too large. As a result, the L2 on the eNodeB deletes the RRC Connection release message. call failure.
The 3G network devices are provided by another vendor. When Flash CSFB or RIM is enabled, the size of Because the eNodeB cannot obtain the RIM Contact the other vendor to disable the function of including
the RIM RSP message exceeds 320 bytes (maximum size configured on the eNodeB) as the system message, Flash CSFB fails. SIB11 in the RIM RSP message.
information in the RIM information contains SIB11. The eNodeB cannot store this RIM message and fails
to obtain the system information. As a result, Flash CSFB fails.
The eNodeB is provided by another vendor. The UMTS-to-LTE PSHO is enabled on Huawei RNC. When The UMTS-to-LTE PSHO fails. The UE capability is optional. Contact the other vendor to
the RRC Connection complete message sent by the UE does not carry the UE capability, the handover make modification.
eNodeB
preparation message sent by Huawei RNC does not carry this information either. As a result, the eNodeB
responds with a handover preparation failure message.
During the TAU, the NSN MME directly rejects the Contact NSN MME to modify the paging policies.
MSC SGs Paging request. As a result, MT CSFB
CN The NSN MME fails to page the called party during a TAU, resulting in CSFB failure.
fails.

 In the scenario of interconnection of devices provided by different vendors, check whether the parameter baselines of Huawei devices are correct. Based on the known issues, analyze
the signaling to determine whether the issue is caused by the other vendor's devices.
 The signaling analysis process is similar to that of other issues mentioned above. If the signaling information shows that the other vendor's device rejects a request or returns a failure
message, collect the signaling information and send it to the R&D engineers for further analysis. Push the other vendor to check the signaling failure issue.
According to the experiences, the following issues are likely to cause the interconnection failure:
1) During the handover preparation, after Huawei RAN sends a handover preparation message, the core network or RAN of the other vendor returns a handover preparation failure message.
2) During the RIM interaction, after Huawei RAN sends a RIM Request, the core network or RAN of the other vendor does not respond or the size of the response message exceeds the threshold.
3) In the CSFB scenario, the core network of the other vendor encounters paging problems.
Determine whether the issues are caused by the other vendor‘s devices based on the table:
Issue Category Check and Analysis Action Closed-loop Action
Inter-RAT handover issues When Huawei device initiates the handover and sends the Handover request message, check whether the core 1) If the core network of the other vendor directly returns a handover preparation failure
network or RAN of the other vendor returns a handover preparation failure message. message, check whether the target cell for which the handover preparation request is sent is
consistent with that configured on the core network or RAN of the other vendor.
2) If the RAN of the other vendor returns a handover preparation failure message, check
whether the target network is congested based on the failure cause. If other issues exist, urge
the other vendor to solve the issues.
The RIM message cannot be Trace the signaling over the S1 interface and Iu-PS/GB interface. Check whether the eNodeB has sent the RIM If the signaling issue is caused by the devices provided by other vendors, urge the other
obtained. request message or whether the RNC/BSC has returned the RIM response message. If issues exist during this vendor to solve the issues.
process, check whether the problematic NE is provided by other vendors according to the signaling information.
CSFB paging failure 1) When the core network is provided by another vendor, according to the UL MO call setup time point, determine If the core network is provided by another vendor does not normally sends the paging
the DL MT paging time point, to confirm whether the core network normally sends the paging message. For the message, urge the other vendor to solve the issues.
dialing test at a specified point, trace the signaling over the S1 and Uu interfaces. For the DT, check the DT logs to
determine whether cross-processes exist, for example, the paging and TAU update, reselection, or handover are
implemented at the same time point.
2) If the paging message is sent, check whether state inconsistency exists. For example, the core network considers
that the UE is in the idle state, but the eNodeB considers that the UE is still in the connected state.

Thank you
www.huawei.com
Copyright©2009 Huawei Technologies Co., Ltd. All Rights Reserved.

The information contained in this document is for reference purpose only, and is subject to
change or withdrawal according to specific customer requirements and conditions.

03 GUL Interoperability Troubleshooting (Drive Test) V1.0

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

03 GUL Interoperability Troubleshooting (Drive Test) V1.0

Diunggah oleh

Hak Cipta:

Format Tersedia

GUL Interoperability Troubleshooting

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

NE Version Bug of a product version

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

2 Low CSFB success rate

3 UE return to LTE network slowly after CSFB

5 U2L redirection/HO based on service fails.

6 Interoperability Issues Caused by Inter -

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

RAU request delay procedure

The details of the parameter please click the attachment:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

NE Problem Description Preventive Measure/Solution

1. Upgrade the current version to BSC6900 V900R015C00SPC520 or later.

In interoperability between GSM and LTE networks, no respond message is

P1 1. Enable the DMCR function in the UTRAN network.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

1.Extended Service Request 1. Extended Service Request

3.Optional measurement report

Part 3: set up the voice

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

ESR – RRC Release – RRC RRC Connection Setup CM service

Delay baseline 200 1000 0 800 3400 5400

ESR – MobilityFromEUTRAC 3G Handover to UTRAN

Delay Base on MR: 700

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

MTC Delay of the UE in reading the 1. Enable Flash CSFB.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

2 Low CSFB success rate

3 UE return to LTE network slowly after CSFB

5 U2L redirection/HO based on service fails.

Interoperability Issues Caused by Inter -

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 Low CSFB success rate

 The parameter need to be checked:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

CSFB to UMTS basedAfter FR is fail:

P-GW MME MSC

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

Check and Analysis Action

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

2 Low CSFB success rate

3 UE return to LTE network slowly after CSFB

5 U2L redirection/HO based on service fails.

Interoperability Issues Caused by Inter -

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

NE Issue Description Impact of the Issue Preventive Measure/Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

2 Low CSFB success rate

3 UE return to LTE network slowly after CSFB

5 U2L redirection/HO based on service fails.

Interoperability Issues Caused by Inter -

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

UE Reselection/Handover Issue Analysis

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

NE Issue Description Impact of the Issue Preventive Measure/Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25