Professional Documents
Culture Documents
Call Reestablishment Ran14 PDF
Call Reestablishment Ran14 PDF
RAN
Feature Parameter Description
Issue 03
Date 2013-11-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
WCDMA RAN
Call Reestablishment Contents
Contents
1 About This Document ................................................................................................................. 1
1.1 Scope ............................................................................................................................................... 1
1.2 Intended Audience............................................................................................................................ 1
1.3 Change History................................................................................................................................. 1
2 Overview......................................................................................................................................... 3
2.1 Introduction....................................................................................................................................... 3
2.2 Benefits ............................................................................................................................................ 3
2.3 Architecture ...................................................................................................................................... 3
9 Network Impact........................................................................................................................... 30
9.1 System Capacity ............................................................................................................................ 30
9.2 Network Performance .................................................................................................................... 30
10 Implementation......................................................................................................................... 31
10.1 When to Use Call Reestablishment ............................................................................................. 31
10.2 Required Information .................................................................................................................... 31
10.3 Planning ....................................................................................................................................... 31
10.4 Deploying Call Reestablishment .................................................................................................. 31
10.4.1 Requirements ...................................................................................................................... 31
10.4.2 Data Preparation ................................................................................................................. 31
10.4.3 Function Activation .............................................................................................................. 34
10.4.4 MML Command Example .................................................................................................... 36
10.4.5 Activation Observation ......................................................................................................... 36
10.4.6 Deactivation ......................................................................................................................... 36
10.4.7 MML Command Example .................................................................................................... 37
10.5 Performance Monitoring ............................................................................................................... 37
10.6 Parameter Optimization ............................................................................................................... 38
10.7 Troubleshooting ............................................................................................................................ 38
11 Parameters................................................................................................................................. 39
12 Counters..................................................................................................................................... 72
13 Glossary ..................................................................................................................................... 73
14 Reference Documents ............................................................................................................ 74
03 (2013-11-30)
This issue includes the following changes.
02 (2013-06-20)
This issue includes the following changes.
01 (2012-11-30)
This document is created for RAN14.0.
2 Overview
2.1 Introduction
Call reestablishment is a function by which radio links (RLs) are reestablished when a service
interruption or an access failure occurs in temporary coverage holes and in tunnels, elevators, and
buildings that cause significant signal quality fluctuation.
Call reestablishment can be initiated by a UE or the RAN.
Call reestablishment initiated by a UE: The UE sends a call reestablishment request to the network to
restore services upon detecting a downlink RL failure or a signaling radio bearer (SRB) reset.
Call reestablishment initiated by the RAN: The RAN informs the UE to start call reestablishment upon
detecting a service interruption or an access failure.
This document describes only call reestablishment initiated by the RAN.
2.2 Benefits
The RAN detects a service interruption or an access failure before a UE does and stops downlink power
transmission to initiate call reestablishment. Call reestablishment improves user experience by
increasing the radio access bearer (RAB) setup success rate and reducing the call drop rate.
2.3 Architecture
The possible causes of a service interruption or an access failure are as follows:
RL failure
SRB reset
Air-interface process overlap
Air-interface process overlap
PS TRB reset
These causes can impact the following processes: active set update, physical channel reconfiguration,
RB setup, SRB reconfiguration during dynamic channel configuration control (DCCC), and measurement
control.
Before releasing RLs due to the preceding causes in those processes, the RAN detects the service
interruption or access failure and initiates call reestablishment, as shown in Figure 2-1.
RL failure can trigger call reestablishment even if the processes in Figure 2-1 are not active. RB reset, air-interface
process overlap, TRB reset and air-interface process timeout must occur in one of the processes before call
reestablishment is triggered.
Call reestablishment is controlled by service switch, process switch, and cause switch parameters.
Enable the corresponding service switch before enabling a process switch or a cause switch.
Table 2-1 shows the signaling messages and causes for call reestablishment.
Table 2-1 Switch parameter mapping
Service Process Cause
CS SRB reset
services Active set update
RL failure
Measurement control SRB reset
SRB reset
RB setup
Air-interface process overlap
PS
SRB reset
services
Active set update
RL failure
SRB reset
Measurement control
RL failure
SRB reset
RB setup
Air-interface process overlap
SRB reset
Air-interface process overlap
RB reconfiguration during DCCC
Air-interface process timeout
RL failure
SRB reset
Physical channel reconfiguration during a hard
handover RL failure
Air-interface process timeout
SRB reset
Physical channel reconfiguration in
compressed mode
RL failure
SRB reset
Physical channel reconfiguration during a
serving cell change RL failure
Air-interface process timeout
The active set update and measurement control processes do not have process switch parameters.
3 Uplink RL Failure
3.1 Uplink RL Failure Detection
The NodeB monitors uplink RL quality. If the number of "out-sync" indications received by the NodeB
reaches the value of the NOUTSYNCIND parameter, the NodeB starts the TRlFailure timer. The
detection process continues according to the situation:
If the number of "in-sync" indications received by the NodeB reaches the value of the NINSYNCIND
parameter before the TRlFailure timer expires, the NodeB stops and resets the TRlFailure timer.
If the number of "in-sync" indications received by the NodeB does not reach the value of the
NINSYNCIND parameter before the TRlFailure timer expires, the NodeB considers that an RL failure
has occurred and identifies the RL set where the failure is located. (An RL set contains all the RLs of a
UE under a NodeB.)
The higher the value of the NOUTSYNCIND parameter, the harder it will be for RL failures to be triggered. The higher the
value of the NINSYNCIND parameter, the harder it will be for RLs to be synchronized. If either parameter is set to a high
value, RLs will be on the verge of RL failure for a long time, and user experience will be poor for both CS and PS services.
Set NOUTSYNCIND to a value less than the default and NINSYNCIND to a value higher than the default. This way, RL
failures are easily triggered for call reestablishment to improve user experience.
The default value of NOUTSYNCIND is 50 and NINSYNCIND is 5.
When a UE's uplink RL sets are all out of synchronization, different events occur according to the
situation:
If the call reestablishment feature is not enabled, the call drops or the UE access finally fails.
If the call reestablishment feature is enabled, the RNC activates a synchronization timer.
Table 3-1 shows the mapping between services, RsvdPara1:RSVDBIT1_BIT28 switch status, and
synchronization timers.
Table 3-1 Mapping between services, RsvdPara1:RSVDBIT1_BIT28 switch status, and synchronization
timers
Service RsvdPara1:RSVDBIT1_BIT28 Switch Status Synchronization Timer
CS Off RlRstrTmr
services
On T313
PS Off RlRstrTmr
services
On RlRstrTmr
If the NodeB does not detect uplink RL synchronization before the timer expires, call reestablishment is
initiated.
Enable the RsvdPara1:RSVDBIT1_BIT28 switch for CS services so that uplink and downlink RLs are monitored by the
same synchronization timer.
When the RsvdPara1:RSVDBIT1_BIT28 switch is enabled, the synchronization timer used to initiate RL establishment is
RlRstrTmr. The T313 timer is used only when the UE's RL sets are all out of synchronization.
To enable the call reestablishment feature triggered by an RL failure, enable the corresponding service
and cause switches listed in Table 3-2.
Table 3-2 Switches for call reestablishment triggered by an RL failure
Service Service Switch Process Switch Cause Switch
CS services RsvdPara1:RSVD Physical channel reconfiguration RsvdPara1:RSVDBIT1_BI
BIT1_BIT24 is controlled by T23
PS services RsvdPara1:RSVD PROCESSSWITCH4:PHY_RECF
BIT1_BIT25 G_REEST_SWITCH.
RB reconfiguration is controlled by
PROCESSSWITCH4:RB_RECFG
_RL_REEST_SWITCH.
The service switch for CS+PS combined services is the same as that for CS services.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
Figure 3-1 Call reestablishment triggered by an uplink RL failure under the same RNC
Figure 3-2 Call reestablishment triggered by an uplink RL failure under different RNCs over the Iur interface
The difference between call reestablishment triggered by an uplink RL failure under the same RNC and
that triggered by an uplink RL failure under different RNCs is summarized as follows:
In the former process, the RNC sends the Radio Link Activation Command to the NodeB.
In the latter process, the SRNC sends the Radio Link Deletion Request message to the DRNC, and
upon receiving the Radio Link Deletion Response message from the NodeB, the DRNC waits for the
UE's Cell Update message.
3.2.2 Implementation
The call reestablishment process is implemented as follows:
1. After the NodeB stops downlink power transmission for a UE's RLs, the UE starts the T313 timer if
the number of "out-sync" indications received consecutively from Layer 1 reaches the value of the
N313 parameter.
The higher the value of the N313 parameter, the harder it will be for the UE to detect an RL failure and the longer the UE
stays on the verge of RL failure.
2. If the number of "in-sync" indications received consecutively from Layer 1 does not reach the value of
the N315 parameter before the T313 timer expires, the UE transmits the Cell Update message with
the cause value "Radio Link Failure" to the RNC for call reestablishment. Meanwhile, the UE starts
the T302 timer as well as the T314 timer for CS services or the T315 timer for PS services.
3. If the UE does not receive the Cell Update Confirm message from the RAN side after the T302 timer
expires, the UE retransmits the Cell Update message until the T314/T315 timer expires: (The number
of retransmissions is determined by the value of the N302 parameter.)
If faulty RLs are restored before T314/T315 expires, the call reestablishment is successful. Interrupted
services are restored or UE access succeeds.
If faulty RLs are not restored before T314/T315 expires, the call reestablishment fails. Services are
released or UE access fails.
Set the T313, N313, N315, and T314 parameters appropriately so that UEs can quickly detect RL failures.
4 SRB Reset
Figure 4-1 shows the signaling procedure for call reestablishment triggered by an SRB reset.
Figure 4-1 Call reestablishment triggered by an SRB reset
The service switch for CS+PS combined services is the same as that for CS services.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
After you enable the process switch, change the length of the corresponding process timer so that call
reestablishment is more likely to be triggered by an SRB reset. Table 4-2 shows the mapping between
processes and timers.
Table 4-2 Mapping between processes and timers
Process Timer
Active set update HoAsuTmr
Physical channel reconfiguration HoPhychRecfgTmr
RB setup RbSetupRspTmr
SRB reconfiguration during dynamic channel RbRecfgRspTmr
configuration control (DCCC)
5 TRB Reset
Figure 5-1 shows the signaling procedure for call reestablishment triggered by a TRB reset.
Figure 5-1 Call reestablishment triggered by a TRB reset
If the call reestablishment feature is not enabled, the RNC sends the Iu Release Request message to
the core network and the UE's PS services are interrupted.
If the call reestablishment feature is enabled, the RNC does not send the Iu Release Request
message to the core network and call reestablishment is triggered. After the call reestablishment, the
UE is still in the CELL_DCH state.
To enable the call reestablishment feature in this scenario, enable the service and process switches
listed in the following table.
Table 5-1 Switches for call reestablishment triggered by a TRB reset
Service Switch Process Switch Cause
Switch
The PS service is controlled by PDU sending is controlled by SET None
RsvdPara1:RSVDBIT1_BIT25 UCORRMPARA:ReservedSwitch
in the SET URRCTRLSWITCH 1: RESERVED_SWITCH_1_BIT26
command. When RsvdPara1 is
set to RSVDBIT1_BIT25-0, the
switch for PS service is enabled.
Call reestablishment triggered by a TRB reset applies only to a single PS service of a UE in the CELL_DCH state.
If the RNC receives the Cell Update message containing the cause value "RLC Unrecoverable Error" from the UE, only
the RsvdPara1:RSVDBIT1_BIT26 switch needs to be enabled to perform call reestablishment.
For details about whether to use RlRstrTmr or T313, see section 3.1 "Uplink RL Failure Detection."
To enable the call reestablishment feature for scenario 1, enable the corresponding service, process,
and cause switches listed in Table 6-1 and Table 6-2.
Table 6-1 lists the switches for call reestablishment triggered when the RNC does not receive ACK of the
Radio Bearer Setup message from the UE.
Table 6-1 Switches for call reestablishment triggered when the RNC does not receive ACK of the Radio
Bearer Setup message from the UE
Service Service Switch Process Process Switch Cause Switch
CS services RsvdPara1:RS RB setup PROCESSSWITC RsvdPara1:RSVDBIT1_BI
VDBIT1_BIT24 H4:RB_SETUP_R T23
The service switch for CS+PS combined services is the same as that for CS services.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
Table 6-2 lists the switches for call reestablishment triggered when the RNC does not receive ACK of the
Radio Bearer Reconfiguration message from the UE.
Table 6-2 Switches for call reestablishment triggered when the RNC does not receive ACK of the Radio
Bearer Reconfiguration message from the UE
Service Service Process Process Switch Cause Switch
Switch
Single PS RsvdPara1: RB reconfiguration ReservedSwitch1:RESER RsvdPara1:RSVD
service RSVDBIT1_ VED_SWITCH_1_BIT14 BIT1_BIT23
BIT25
CS+PS RsvdPara1:
combined RSVDBIT1_
services BIT24
The service switch for CS+PS combined services is the same as that for CS services.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
The following table lists the switches for call reestablishment triggered when the RNC does not receive
ACK of the Physical Channel Reconfiguration Complete message for a single PS service.
Table 6-3 Switches for call reestablishment triggered when the RNC does not receive ACK of Physical
Channel Reconfiguration Complete message for a single PS service
Service Service Switch Process Switch Cause Switch
PS services RsvdPara1:RSVDBIT1_BI The RsvdPara1:RSVDBIT1_BI
T25 PHY_RECFG_REEST_SW T23
ITCH under the
PROCESSSWITCH4
parameter controls whether
call reestablishment can be
triggered when physical
channel reconfiguration
overlaps cell update.
The following table lists the switches for call reestablishment triggered when the RNC does not receive
ACK of the Physical Channel Reconfiguration Complete message for CS+PS combined services.
Table 6-4 Switches for call reestablishment triggered when the UE does not send the RNC a Physical
Channel Reconfiguration Complete message for CS+PS combined service
Service Service Switch Process Switch Cause Switch
CS+PS combined RsvdPara1:RSVDBIT1 The RsvdPara1:RSVDBIT1
services _BIT24 PHY_RECFG_REEST_ _BIT23
SWITCH under the
PROCESSSWITCH4
parameter controls
whether call
reestablishment can be
triggered when physical
channel reconfiguration
overlaps cell update.
The service switch for CS+PS combined services is the same as that for CS services.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
6.1.2 Scenario 2
After sending the Radio Bearer Setup or Radio Bearer Reconfiguration message to a UE, the RNC
receives the Cell Update message containing the cause value "Radio Link Failure" or RLC
Unrecoverable error from the UE. Then one of the following occurs:
If the call reestablishment feature is not enabled, the call drops or UE access fails.
If the call reestablishment feature is enabled, the RNC initiates call reestablishment, as shown in
Figure 6-2.
The RNC does not send the Radio Link Activation Command message containing the "deactivate" IE to the NodeB.
Therefore, the NodeB does not stop downlink power transmission for the UE's RL sets. Instead, the RNC initiates call
reestablishment upon receiving the Cell Update message from the UE.
To enable the call reestablishment feature for scenario 2, enable the corresponding service, process,
and cause switches listed in Table 6-5 and Table 6-6.
Table 6-5 lists the switches for call reestablishment triggered when the RNC does not receive ACK of the
Radio Bearer Setup message from the UE in scenario 2.
Table 6-5 Switches for call reestablishment triggered when the RNC does not receive ACK of the Radio
Bearer Setup message from the UE
Process Process Switch Cause Switch
RB setup PROCESSSWITCH4:RB_SETUP_RL_REEST_SWITCH None
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
Table 6-6 lists the switches for call reestablishment triggered when the RNC does not receive ACK of the
Radio Bearer Reconfiguration message from the UE in scenario 2.
Table 6-6 Switches for call reestablishment triggered when the RNC does not receive ACK of the Radio
Bearer Reconfiguration message from the UE (PS or CS+PS)
Process Process Switch Cause Switch
RB reconfiguration ReservedSwitch1:RESERVED_SWITCH_1_BIT14 None
and SET UCORRMPARA: ReservedSwitch1:
RESERVED_SWITCH_1_BIT20
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
Table 6-7 Switches for call reestablishment triggered when the RNC does not receive ACK of the Physical
Channel Reconfiguration message from the UE (PS or CS+PS)
Process Process Switch Cause Switch
Physical Channel ProcessSwitch4: PHY_RECFG_REEST_SWITCH None
Reconfiguration and SET UCORRMPARA: ReservedSwitch1:
RESERVED_SWITCH_1_BIT19
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
In this scenario, the call reestablishment feature is controlled by the service switch and process switch,
as described in the following table.
Table 7-1 Switches for call reestablishment triggered by radio bearer setup timeout
Service Switch Process Switch Cause
Switch
The CS service is controlled by RB setup is controlled by SET UCORRMPARA: None
RsvdPara1:RSVDBIT1_BIT24 in the ReservedSwitch1:RESERVED_SWITCH_1_BIT1
SET URRCTRLSWITCH command. 4 and SET UCORRMPARA:ReservedSwitch1=
When RsvdPara1 is set to
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
The following table lists the switches for call reestablishment triggered by physical channel
reconfiguration timeout.
Table 7-2 Switches for call reestablishment triggered by physical channel reconfiguration timeout
Service Switch Process Switch Cause Switch
The CS service is controlled by The PHY_RECFG_REEST_SWITCH under the None
RsvdPara1:RSVDBIT1_BIT24 in PROCESSSWITCH4 parameter and SET
the SET URRCTRLSWITCH CORRMPARA :ReservedSwitch1:
command. When RsvdPara1 is RESERVED_SWITCH_1_BIT19 control whether
set to RSVDBIT1_BIT24-0, the call reestablishment can be triggered by physical
switch for CS service is enabled. channel reconfiguration timeout. Call
reestablishment can be triggered by physical
The PS service is controlled by channel reconfiguration timeout only when these
RsvdPara1:RSVDBIT1_BIT25 in two switches are turned on.
the SET URRCTRLSWITCH
command. When RsvdPara1 is
set to RSVDBIT1_BIT25-0, the
switch for PS service is enabled.
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both CS and PS
services.
8 Related Features
8.1 Prerequisite Features
None
9 Network Impact
9.1 System Capacity
None
10 Implementation
10.1 When to Use Call Reestablishment
Use call reestablishment in temporary coverage holes and in tunnels, elevators, and buildings that cause
significant radio signal fluctuation.
10.3 Planning
None
3. Run the SET UCACALGOSWITCH command to set Reserved parameter 2 and Reserved
parameter 3.
4. Run the SET URRCTRLSWITCH command to set Reserved parameter 1 to RSVDBIT1_BIT28.
Step 2 Enable the switches that control the call reestablishment feature for CS and PS services.
1. Run the SET URRCTRLSWITCH command and select RSVDBIT1_BIT24 and RSVDBIT1_BIT25
under Reserved parameter 1.
Step 3 Enable the switches that control the call reestablishment feature triggered by RL failures and
SRB resets.
1. Run the SET URRCTRLSWITCH command and select RSVDBIT1_BIT22 and RSVDBIT1_BIT23
under Reserved parameter 1.
Step 4 Set the timer for the Active Set Update process.
1. Run the SET USTATETIMER command to set HO active set update response timer.
Step 5 Enable the switch that controls the call reestablishment feature triggered by physical channel
reconfiguration.
1. Run the SET URRCTRLSWITCH command and select PHY_RECFG_REEST_SWITCH under
Process Control Switch 4.
2. Run the SET USTATETIMER command to set HO PhyCh reconfiguration timer.
Step 6 Enable the switch that controls the call reestablishment feature triggered by RB setup.
1. Run the SET URRCTRLSWITCH command and select RB_SETUP_RL_REEST_SWITCH under
Process Control Switch 4.
2. Run the SET USTATETIMER command to set Wait RB setup response timer.
Step 7 Enable the switch that controls the call reestablishment feature triggered by RB reconfiguration.
1. Run the SET UCORRMPARA command and select RESERVED_SWITCH_1_BIT14 under CORRM
Algorithm Reserved Switch 1.
2. Run the SET USTATETIMER command to set Wait RB reconfiguration response timer.
Step 8 Enable the switch that controls the call reestablishment feature under different RNCs.
Run the SET URRCTRLSWITCH command and select IUR_RL_REEST_SWITCH under Process
Control Switch 4.
Step 9 Enable the switch that controls the call reestablishment feature triggered by RB reconfiguration
Run the SET UCORRMPARA command and select RESERVED_SWITCH_1_BIT20 under CORRM
Algorithm Reserved Switch 1.
Step 10 Enable the switch that controls the call reestablishment feature triggered by physical channel
reconfiguration
Run the SET UCORRMPARA command and select RESERVED_SWITCH_1_BIT19 under CORRM
Algorithm Reserved Switch 1.
Step 11 Enable the switch that controls the call reestablishment feature triggered by PS TRB rreset
Run the SET UCORRMPARA command and select RESERVED_SWITCH_1_BIT26 under CORRM
Algorithm Reserved Switch 1.
----End
10.4.6 Deactivation
Step 1 Disable the switches that control the call reestablishment feature for CS and PS services.
Run the SET URRCTRLSWITCH command and clear RSVDBIT1_BIT24 and RSVDBIT1_BIT25
under Reserved parameter 1.
Step 2 Disable the switches that control the call reestablishment feature triggered by RL failures and
SRB resets.
Run the SET URRCTRLSWITCH command and clear RSVDBIT1_BIT22 and RSVDBIT1_BIT23
under Reserved parameter 1.
Step 3 Disable the switch that controls the call reestablishment feature triggered by physical channel
reconfiguration.
Run the SET URRCTRLSWITCH command and clear PHY_RECFG_REEST_SWITCH under
Process Control Switch 4.
Step 4 Disable the switch that controls the call reestablishment feature triggered by RB setup.
Run the SET URRCTRLSWITCH command and clear RB_SETUP_RL_REEST_SWITCH under
Process Control Switch 4.
Step 5 Disable the switch that controls the call reestablishment feature triggered by RB reconfiguration.
Run the SET UCORRMPARA command and clear RESERVED_SWITCH_1_BIT14 under CORRM
Algorithm Reserved Switch 1.
Step 6 Disable the switch that controls the call reestablishment feature triggered by RB reconfiguration
Run the SET UCORRMPARA command and clear RESERVED_SWITCH_1_BIT20 under CORRM
Algorithm Reserved Switch 1.
Step 7 Disable the switch that controls the call reestablishment feature triggered by physical channel
reconfiguration
Run the SET UCORRMPARA command and clear RESERVED_SWITCH_1_BIT19 under CORRM
Algorithm Reserved Switch 1.
Step 8 Disable the switch that controls the call reestablishment feature triggered by PS TRB rreset
Run the SET UCORRMPARA command and clear RESERVED_SWITCH_1_BIT26 under CORRM
Algorithm Reserved Switch 1.
Step 9 Disable the switch that controls the call reestablishment feature under different RNCs.
Run the SET URRCTRLSWITCH command and clear IUR_RL_REEST_SWITCH under Process
Control Switch 4.
Step 10 Run the SET URRCTRLSWITCH command and clear RSVDBIT1_BIT28 under Reserved
parameter 1.
Step 11 (Optional) Set the following parameters to the values they were before the function was enabled:
1. Run the SET UCONNMODETIMER command to reset the following parameters to their original
values: Timer 302, Constant 302, Timer 313, Constant 313, Timer 314, Constant 315, and Timer
315.
2. Run the MOD UCELL command to reset the following parameters to their original values: Num of
Continuous in Sync Ind, Num of Continuous Out of Sync Ind, and Radio Link Failure Timer
Length.
3. Run the SET UCACALGOSWITCH command to reset Reserved parameter 2 and Reserved
parameter 3 to their original values.
4. Run the SET USTATETIMER to reset the following parameters to their original values: HO active set
update response timer, HO PhyCh reconfiguration timer, Wait RB setup response timer, and
Wait RB reconfiguration response timer.
----End
NOTE
When you deactivate the call reestablishment feature, change the values of the following parameters back to their settings
before this function was activated: T302, N302, T313, N313, N315, T314(CS), T315(PS), NinsyncInd, NoutsyncInd,
TRlFailure, RsvdPara2(CS), RsvdPara3(PS), RbSetupRspTmr, RbRecfgRspTmr, HoAsuTmr and
HoPhychRecfgTmr. Otherwise, network performance will be greatly affected.
10.7 Troubleshooting
None
11 Parameters
Table 11-1 Parameter description
Paramet NE MML Feature ID Feature Name Description
er ID Command
HoAsuT BSC69 SET WRFD-020202 Intra RNC Soft Meaning:A timer to RNC wait
mr 00 USTATETI Handover for the response to active set
MER WRFD-020203 update in soft handover
Inter RNC Soft procedure.
Handover
Note: The value range of
"HoAsuTmr" is 1 to 300000 in
the current version. In a later
version, the value range
changes into 100 to 300000. In
the current version, if you enter
a value within the range of 1 to
100 including 1, this value can
still be synchronized and issued
but the system regards the
value as 5000, the
recommended value.
Therefore, you are advised not
to enter a value smaller than
100.
GUI Value Range:1~300000
Actual Value Range:1~300000
HoPhyc BSC69 SET WRFD-020302 Inter Frequency Hard Meaning:A timer to RNC wait
hRecfgT 00 USTATETI Handover Based on for the response to physical
mr MER WRFD-020304 Coverage channel reconfiguration in hard
WRFD-020301 handover procedure.
Inter Frequency Hard
Handover Based on DL Note: The value range of
QoS "HoPhychRecfgTmr" is 1 to
300000 in the current version.
Intra Frequency Hard In a later version, the value
Handover range changes into 100 to
300000. In the current version,
if you enter a value within the
range of 1 to 100 including 1,
this value can still be
synchronized and issued but
the system regards the value as
5000, the recommended value.
Therefore, you are advised not
to enter a value smaller than
100.
GUI Value Range:1~300000
Actual Value Range:1~300000
Unit:ms
Default Value:5000
RbRecfg BSC69 SET WRFD-010101 3GPP R9 Specifications Meaning:A timer used to wait
RspTmr 00 USTATETI for the RB reconfiguration
MER response from UE in the RB
procedure. Refer to the Note.
GUI Value Range:300~300000
Actual Value
Range:300~300000
Unit:ms
Default Value:5000
RbSetup BSC69 SET WRFD-010101 3GPP R9 Specifications Meaning:A timer to RNC wait
RspTmr 00 USTATETI for the RB setup response from
MER UE in the RB procedure. Refer
to the Note.
GUI Value Range:300~300000
Actual Value
Range:300~300000
Unit:ms
Default Value:5000
RlRstrT BSC69 SET WRFD-010101 3GPP R9 Specifications Meaning:A timer to RNC wait
mr 00 USTATETI for radio link restoration
MER indication in the radio link
procedure.
Note: The value range of
"RlRstrTmr" is 1 to 300000 in
the current version. In a later
version, the value range
changes into 100 to 300000. In
the current version, if you enter
a value within the range of 1 to
100 including 1, this value can
still be synchronized and issued
but the system regards the
value as 11000, the
recommended value.
Therefore, you are advised not
to enter a value smaller than
100.
GUI Value Range:1~300000
Actual Value Range:1~300000
Unit:ms
Default Value:11000
TRlFailu BSC69 ADD WRFD-022000 Physical Channel Meaning:Radio link failure timer
re 00 UCELLSET Management duration. When the radio link
UP set is in the synchronized state,
the NodeB starts the timer after
it receives successive
out-of-sync indications of the
number defined by
NOutsyncInd. The NodeB shall
stop and reset the timer after
receiving successive in-sync
indications of the number
defined by NInsyncInd. When
the timer expires, the NodeB
triggers the radio link failure
process, and indicates which
radio link set is out-of-sync.
GUI Value Range:0~255
Actual Value Range:0~25.5
12 Counters
There are no specific counters associated with this feature.
13 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
14 Reference Documents
1. 3GPP TS 25.331, "Radio Resource Control (RRC); Protocol specification"
2. 3GPP TS 25.214, "Physical layer procedures (FDD)"