Call Restablisment

11/5/2014
RAN Feature Documentation
WCDMA RAN
Call Reestablishment
Feature Parameter Description
Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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 commercial contract made between Huawei and the customer. All or partial products,
services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by 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 a warranty of any kind, express or implied.
http://127.0.0.1:52199/hedex/hdx.do?fe=0&lib=GEB02251&v=05&homepage=resources/hedex-homepage.html
1/32
11/5/2014
Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
Document Versions
01 (2012-11-30)
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
3 Uplink RL Failure
3.1 Uplink RL Failure Detection
3.2 Call Reestablishment
3.2.1 Triggering
3.2.2 Implementation
4 SRB Reset
4.1 SRB Reset Detection
5 TRB Reset
5.2 TRB Reset Detection
6 Air-Interface Process Overlap

6.1 Air-Interface Process Overlap Detection
6.1.1 Scenario 1
6.1.2 Scenario 2
7 Air-Interface Process Timeout

7.1 Air-Interface Process Timeout Detection
7.1.1 Radio Bearer Setup Timeout
7.1.2 Physical Channel Reconfiguration Timeout
8 Related Features
8.1 Prerequisite Features
8.2 Mutually Exclusive Features
8.3 Impacted Features
9 Network Impact
9.1 System Capacity
9.2 Network Performance
10 Implementation
10.1 When to Use Call Reestablishment
10.2 Required Information
10.3 Planning
10.4 Deploying Call Reestablishment
10.4.1 Requirements
10.4.2 Data Preparation
10.4.3 Function Activation
10.4.4 MML Command Example
10.4.5 Activation Observation
10.4.6 Deactivation
10.5 Performance Monitoring
10.6 Parameter Optimization
10.7 Troubleshooting
11 Parameters
12 Counters
13 Glossary
14 Reference Documents
2/32
11/5/2014
1 About This Document

1.1 Scope
This document describes the WRFD-140103 Call Reestablishment feature, including basic principles, feature dependencies, network impact,
implementation, and parameters.
1.2 Intended Audience

This document is intended for personnel who:
l Need
to understand the call reestablishment feature
l Work
with Huawei products
l Are
familiar with UMTS basics
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
l Feature
change: refers to a change in the call reestablishment feature of a specific product version.
l Editorial
change: refers to a change in wording or the addition of information that was not described in the earlier version.
Document Versions
The document issues are as follows:
l 02(2013-06-20)
l 01(2012-11-30)
02(2013-06-20)
This is the second commercial release for RAN14.0.
Change Type
Change Description
Parameter Change
Feature
change
None
None
Feature
change
Added 6 Air-Interface Process Overlap
None
Added 7 Air-Interface Process Timeout

Added the processing of physical channel
reconfiguration in 6 Air-Interface Process Overlap
01 (2012-11-30)
This is the first commercial release 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.
l 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.
l 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:
l RL
failure
l SRB
reset
l Air-interface
process overlap
l Air-interface
process overlap
l PS
TRB reset
These causes can impact the following processes: active set update, physical channel reconfiguration, RB setup, SRB reconfiguration during dynamic
3/32
11/5/2014
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.
Figure 2-1 Causes and processes that trigger call reestablishment
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
CS services
Process
Active set update
Cause
SRB reset
RL failure
Measurement control
SRB reset
Physical channel reconfiguration during a hard

handover
SRB reset
Physical channel reconfiguration in compressed mode

Radio bearer reconfiguration
RL failure
SRB reset
RL failure
SRB reset
RL failure
Air-interface process timeout
Air-interface process overlap
Physical channel reconfiguration during a serving cell

update
SRB reset
RL failure
Physical channel reconfiguration for inter RNC-UE timer

relationship adjustment when a UE reports event 6G or
6F
SRB reset
RL failure
SRB reset
RB setup
PS services
SRB reset
Active set update
RL failure
Measurement control
SRB reset
RL failure
SRB reset
RB setup
4/32
11/5/2014

SRB reset
RB reconfiguration during DCCC

PS TRB Reset
None
SRB reset
Physical channel reconfiguration during a hard

handover
RL failure
SRB reset
Physical channel reconfiguration in compressed mode

RL failure
Physical channel reconfiguration during HSUPA power
adjustment
SRB reset
RL failure
Physical channel reconfiguration for inter RNC-UE timer

relationship adjustment when a UE reports event 6G or
6F
SRB reset
RL failure
SRB reset
Physical channel reconfiguration during a serving cell

change
RL failure
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:
l 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.
l 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.
When a UE's uplink RL sets are all out of synchronization, different events occur according to the situation:
l If
the call reestablishment feature is not enabled, the call drops or the UE access finally fails.
l 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 services
Off
RlRstrTmr
On
T313
Off
RlRstrTmr
On
RlRstrTmr
PS services
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.
5/32
11/5/2014
Table 3-2 Switches for call reestablishment triggered by an RL failure

Service
Service Switch
Process
Process Switch
Cause Switch
CS
services
RsvdPara1:RSVDBIT1_BIT24
PROCESSSWITCH4:PHY_RECFG_REEST_SWITCH
PS
services
Physical
channel
reconfiguration
RL failures can trigger call reestablishment without enabling process switches.
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.

3.2.1 Triggering
Call reestablishment triggered by an uplink RL failure can be performed under the same RNC or under different RNCs over the Iur interface.
Under the Same RNC

As mentioned in section 3.1 "Uplink RL Failure Detection", if the NodeB does not detect uplink RL synchronization before the RlRstrTmr or T313 timer
expires, the RNC sends to the NodeB the Radio Link Activation Command message containing the information element (IE) "deactivate." Upon receiving the
message, the NodeB stops downlink power transmission for the UE's RL sets. Then, the RNC starts the timer for call reestablishment (RsvdPara2 timer for
CS services and RsvdPara3 timer for PS services).
l If
the RNC does not receive the Cell Update message from the UE before the timer expires, the call drops or UE access fails.
l If
the RNC receives the Cell Update message from the UE before the timer expires, the RNC stops the timer and initiates call reestablishment.
Figure 3-1 shows the signaling procedure for call reestablishment triggered by an uplink RL failure under the same RNC.
Figure 3-1 Call reestablishment triggered by an uplink RL failure under the same RNC
6/32
11/5/2014
Under Different RNCs over the Iur Interface

Call reestablishment under different RNCs is controlled by the PROCESSSWITCH4:.IUR_RL_REEST_SWITCH.
Figure 3-2 shows the signaling procedure for call reestablishment triggered by an uplink RL failure under different RNCs over the Iur interface.
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:
l In
the former process, the RNC sends the Radio Link Activation Command to the NodeB.
l 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.)
l If
faulty RLs are restored before T314/T315 expires, the call reestablishment is successful. Interrupted services are restored or UE access succeeds.
l 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.
Figure 3-3 shows how call establishment is implemented.

Figure 3-3 Flowchart for call reestablishment
7/32
11/5/2014
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
8/32
11/5/2014
4.1 SRB Reset Detection

The RNC sends a message in acknowledged mode (AM) to a UE. However, the RNC does not receive a response from the UE before the number of SRB
RLC PDU retransmissions reaches the value of the NoDiscardMaxDAT parameter. If the AMRlcDiscardMode parameter is set to NO_DISCARD, the RNC
triggers an SRB reset and sends the Reset PDU message to the UE to reestablish RLC entities on both sides. Then one of the following occurs:
l If
the call reestablishment feature is not enabled, the RNC sends the Iu Release Request message to the core network.
l If
the call reestablishment feature is enabled, call reestablishment is triggered.
To enable the call reestablishment feature triggered by an SRB reset, enable the corresponding service, process, and cause switches listed in Table 4-1.
Table 4-1 Switches for call reestablishment triggered by an SRB reset
Service
Service Switch
Process
Cause Switch
CS services
Physical channel reconfiguration is controlled by

PROCESSSWITCH4:PHY_RECFG_REEST_SWITCH.
RB setup is controlled by
PROCESSSWITCH4:RB_SETUP_RL_REEST_SWITCH.
PS services
RB reconfiguration is controlled by
ReservedSwitch1:RESERVED_SWITCH_1_BIT14.
RB reconfiguration applies to a single PS service or to services
combined with a PS service.
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
9/32
11/5/2014

Physical channel reconfiguration
HoPhychRecfgTmr
RB setup
RbSetupRspTmr
SRB reconfiguration during dynamic channel

configuration control (DCCC)
RbRecfgRspTmr

The process of call reestablishment triggered by an SRB reset is the same as that triggered by an RL failure. For details, see section 3.2 "Call
Reestablishment."
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
5.2 TRB Reset Detection

The RNC sends an AM PDU to a UE initiating PS services in the CELL_DCH state. If the RNC does not receive a response from the UE, a TRB reset is
triggered. Then one of the following occurs:
l 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.
l 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

RsvdPara1:RSVDBIT1_BIT25 in the
SET URRCTRLSWITCH command.
When RsvdPara1 is set to
RSVDBIT1_BIT25-0, the switch for PS
service is enabled.
PDU sending is controlled by SET

UCORRMPARA:ReservedSwitch1:
RESERVED_SWITCH_1_BIT19
None
10/32
11/5/2014
Call reestablishment triggered by a TRB reset applies only to a single PS service of a UE in the CELL_DCH state.

The process of call reestablishment triggered by a TRB reset is the same as that triggered by an RL failure. For details, see 3.2 Call Reestablishment.
6 Air-Interface Process Overlap

Air-interface process overlap occurs in the following scenarios:
l Scenario
1: The RNC sends the Radio Bearer Setup or Radio Bearer Reconfiguration or Physical Channel Reconfiguratio message to a UE. If the RNC
does not receive a response from the UE before the RlRstrTmr or T313 timer expires, the RNC initiates call reestablishment for the UE.
l Scenario
2: After sending the Radio Bearer Setup or Radio Bearer Reconfiguration message or Physical Channel Reconfiguratio to a UE, the RNC
receives the Cell Update message containing the cause value "Radio Link Failure" or Rlc_Unrecoverable_Errorfrom the UE.
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.
6.1 Air-Interface Process Overlap Detection

6.1.1 Scenario 1
The RNC sends the Radio Bearer Setup or Radio Bearer Reconfiguration message or Physical Channel Reconfiguration to a UE. If the RNC does not
receive a response from the UE before the RlRstrTmr or T313 timer expires, the RNC initiates call reestablishment for the UE. Figure 6-1 shows the
procedure for scenario 1.
For details about whether to use RlRstrTmr or T313, see section 3.1 "Uplink RL Failure Detection."
Figure 6-1 Call reestablishment triggered by air-interface process overlap in scenario 1
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
RB
setup
PROCESSSWITCH4:RB_SETUP_RL_REEST_SWITCH
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
11/32
11/5/2014
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 Switch
Process
Process Switch
Cause Switch
Single PS
service
RB
reconfiguration
ReservedSwitch1:RESERVED_SWITCH_1_BIT14
CS+PS
combined
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
The
PHY_RECFG_REEST_SWITCH
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
services
The
PHY_RECFG_REEST_SWITCH
under the PROCESSSWITCH4
parameter controls whether call
reestablishment can be
triggered when physical
channel reconfiguration
overlaps cell update.
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:
l If
the call reestablishment feature is not enabled, the call drops or UE access fails.
l If
the call reestablishment feature is enabled, the RNC initiates call reestablishment, as shown in Figure 6-2.
Figure 6-2 Call reestablishment triggered by air-interface process overlap in scenario 2
12/32
11/5/2014
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
None
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 and SET

UCORRMPARA: ReservedSwitch1:
None
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
Reconfiguration
ProcessSwitch4: PHY_RECFG_REEST_SWITCH and SET

UCORRMPARA: ReservedSwitch1:
None

The process of call reestablishment triggered by process overlap is the same as that triggered by an RL failure. For details, see section 3.2 "Call
Reestablishment."
7 Air-Interface Process Timeout

13/32
11/5/2014
7.1 Air-Interface Process Timeout Detection

7.1.1 Radio Bearer Setup Timeout
The RNC sends the Radio Bearer Setup message to a UE. However, the RNC does not receive the Radio Bearer Setup Complete message from the UE
before the RbSetupRspTmr timer expires. Then either of the following occurs:
l If
the call reestablishment feature is not enabled, the RNC sends the Iu Release Request message to the core network and the call drops.
l If
the call reestablishment feature is enabled, the RNC does not send the Iu Release Request message to the core network but initiates call
reestablishment, as shown in the following figure.
Figure 7-1 Call reestablishment triggered by radio bearer setup timeout in scenario 1
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

RsvdPara1:RSVDBIT1_BIT24 in the SET
URRCTRLSWITCH command. When
RsvdPara1 is set to RSVDBIT1_BIT24-0, the
switch for CS service is enabled.
RB setup is controlled by SET UCORRMPARA:

ReservedSwitch1:RESERVED_SWITCH_1_BIT14 and SET
UCORRMPARA:ReservedSwitch1=
RESERVED_SWITCH_1_BIT20.
None

RsvdPara1:RSVDBIT1_BIT25 in the SET
URRCTRLSWITCH command. When
RsvdPara1 is set to RSVDBIT1_BIT25-0, the
switch for PS service is enabled.
7.1.2 Physical Channel Reconfiguration Timeout

After sending a Physical Channel Reconfiguration message to a UE, the RNC starts a timer whose length is determined by the HoPhychRecfgTmr
parameter that applies to the UMTS BSC6900. If the RNC does not receive a Physical Channel Reconfiguration Complete message from the UE before the
timer expires, physical channel reconfiguration timeout occurs. Then either of the following occurs:
l If
the call reestablishment feature is not enabled, the RNC sends an Iu Release Request message to the core network and the call drops.
l If
the call reestablishment feature is enabled, the RNC does not send an Iu Release Request message to the core network but initiates call
reestablishment, as shown in the following figure.
Figure 7-2 Call reestablishment triggered by physical channel reconfiguration timeout
14/32
11/5/2014
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

RSVDBIT1_BIT24-0, the switch for CS
service is enabled.
The PHY_RECFG_REEST_SWITCH under the

PROCESSSWITCH4 parameter and SET CORRMPARA
:ReservedSwitch1: RESERVED_SWITCH_1_BIT19 control
whether call reestablishment can be triggered by physical
channel reconfiguration timeout. Call reestablishment can be
triggered by physical channel reconfiguration timeout only
when these two switches are turned on.
None

RSVDBIT1_BIT25-0, the switch for PS
service is enabled.

The process of call reestablishment triggered by process overlap is the same as that triggered by an RL failure. For details, see section 3.2 "Call
Reestablishment."
8 Related Features
8.1 Prerequisite Features
None
8.2 Mutually Exclusive Features

None
8.3 Impacted Features

None
9 Network Impact
15/32
11/5/2014
9.1 System Capacity

None
9.2 Network Performance

When the call reestablishment feature is enabled in scenarios with weak coverage or significant signal fluctuation, calls will be reestablished for UEs with
service interruptions or access failures that are caused by link failures or control/user plane faults. As a result, the call drop rate decreases and the UE
access success rate increases. The exact gains depend on the coverage of the live network.
When a UE service is interrupted or the UE access fails, channel element (CE), code resources, and power resources are released for the UE. After call
reestablishment succeeds, the released resources are re-occupied by the UE.
The call reestablishment feature:
l Generally
l Does
interrupts CS services for at least 8 seconds
not affect network KPIs
l Affects
CS user experience
l Slightly
affects non-real-time PS user experience
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.2 Required Information

Before you enable this function, collect the following information:
l Causes
of call drops or access failures and the number and proportion of times that UEs are involved in the processes performed over the air interface
l Whether
the Iur interface is configured with and supports common channels
To support the call reestablishment feature under different RNCs, the Iur interface must support common channels.
10.3 Planning
None
10.4 Deploying Call Reestablishment

10.4.1 Requirements
None
10.4.2 Data Preparation

Parameter
Name
Parameter ID
Remarks
Data Source
Timer 302
T302
Set this parameter based on network conditions.

Otherwise, network performance will be greatly
affected. The recommended value is 2s.
Radio network plan

(internal)
Constant 302
N302

affected. The recommended value is 3.
Radio network plan

(internal)
Timer 313
T313

Default
value/recommended
value
Constant 313
N313

affected. The higher the value of this 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. The
recommended value is 20.
Radio network plan

(internal)
Constant 315
N315

Radio network plan

(internal)
Timer 314
T314

Radio network plan

(internal)
Timer 315
T315

Radio network plan

(internal)
Num of
Continuous
Out of Sync
Ind
NoutsyncInd

affected. The lower the value of this parameter, the
earlier call reestablishment is triggered by an RL failure.
Radio network plan

(internal)
16/32
11/5/2014

The recommended value is 50, but you can set this
parameter to a value even lower than the
recommended value to improve user experience.
Num of
Continuous in
Sync Ind
NInsyncInd

affected. The higher the value of this parameter, the
earlier call reestablishment is triggered by an RL failure.
The recommended value is 5, but you can set this
parameter to a value even higher than the
recommended value to improve user experience.
Radio network plan

(internal)
Radio Link
Failure Timer
Length
TRlFailure

Radio network plan

(internal)
Reserved
parameter 2
RsvdPara2
Timer for call reestablishment for CS services.
Radio network plan

(internal)
Reserved
parameter 3
RsvdPara3
Reserved
parameter 1

Timer for call reestablishment for PS services.
Switch that controls call reestablishment triggered by
SRB resets
Radio network plan

(internal)
Radio network plan

(internal)
Determine whether to enable this switch by referring to

section 10.2 "Required Information."
Reserved
parameter 1
Switch that controls call reestablishment caused by RL

failures. Determine whether to enable this switch by
referring to section 10.2 "Required Information."
Radio network plan

(internal)
CORRM
Algorithm
Reserved
Switch 1
Switch that controls call reestablishment caused by RB

reconfiguration during DCCC.
Default
value/recommended
value
Process
Control Switch
4
Process
Control Switch
4
PROCESSSWITCH4:PHY_RECFG_REEST_SWITCH
CORRM
Algorithm
Reserved
Switch 1
CORRM
Algorithm
Reserved
Switch 1
CORRM
Algorithm
Reserved
Switch 1
Reserved
parameter 1

Switch that controls call reestablishment caused by
process overlap.
physical channel reconfiguration.
Switch that controls call reestablishment caused by RB
reconfiguration (DCCC)
Default
value/recommended
value
Default
value/recommended
value
Default
value/recommended
value

physical channel reconfiguration.
Switch that controls call reestablishment caused by PS
TRB reset.
Switch that controls call reestablishment for CS
services.
Default
value/recommended
value
Default
value/recommended
value
Radio network plan

(internal)

Reserved
parameter 1
Switch that controls call reestablishment for PS

services.
Radio network plan

(internal)

Process
Control Switch
4
PROCESSSWITCH4:IUR_RL_REEST_SWITCH
Reserved
parameter 1
Switch that controls call reestablishment under different

RNCs.
Switch that controls call reestablishment triggered when
T313 expires after an RL failure.
Default
value/recommended
value
Radio network plan
(internal)
17/32
11/5/2014

Wait RB setup
response timer
RbSetupRspTmr
Set this parameter to 10s if

is enabled.
Radio network plan

(internal)
Wait RB
reconfiguration
response timer
RbRecfgRspTmr

ReservedSwitch1:RESERVED_SWITCH_1_BIT14 is
enabled.
Radio network plan

(internal)
HO active set
update
response timer
HoAsuTmr
Set this parameter to 10s.
Radio network plan

(internal)
HO PhyCh
reconfiguration
timer
HoPhychRecfgTmr

PROCESSSWITCH4:PHY_RECFG_REEST_SWITCH is
enabled.
Radio network plan

(internal)
10.4.3 Function Activation

Step 1 Set the following parameters appropriately:
1. Run the SET UCONNMODETIMER command to set Timer 302, Constant 302, Timer 313, Constant 313, Timer 314, Constant 315, and Timer 315.
2.
Run the MOD UCELL command to set 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 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
Step 11
Enable the switch that controls the call reestablishment feature triggered by PS TRB rreset
----End

SET UCONNMODETIMER: T302=D1400, N302=3, T313=3, N313=D20, T314=D12, T315=D10, N315=D20;
MOD UCELL: CellId=01, NInsyncInd=8, NOutsyncInd=8;
SET UCACALGOSWITCH: RsvdPara2=15000, RsvdPara3=30000;
SET URRCTRLSWITCH: PROCESSSWITCH4=PHY_RECFG_REEST_SWITCH-1& IUR_RL_REEST_SWITCH-1&RB_SETUP_RL_REEST_SWITCH-1,
RsvdPara1=RSVDBIT1_BIT22-0&RSVDBIT1_BIT23-0&RSVDBIT1_BIT24-0&RSVDBIT1_BIT25-0&RSVDBIT1_BIT28-0;
SET UCORRMPARA: ReservedSwitch1=RESERVED_SWITCH_1_BIT14-1;
18/32
11/5/2014

SET USTATETIMER: HoAsuTmr=10000,RbSetupRspTmr=10000, RbRecfgRspTmr =10000,HoPhychRecfgTmr=10000;
10.4.5 Activation Observation

In call reestablishment triggered under the same RNC, track the IOS signaling according to Figure 3-1. If the NBAP_RL_ACT_CMD message can be
tracked, the call reestablishment feature is enabled on the live network.
In call reestablishment triggered under different RNCs, track the IOS signaling according to Figure 3-2. If the RNSAP_RL_DEL_REQ message can be
tracked, the call reestablishment feature is enabled on the live network.
10.4.6 Deactivation
Step 1 Disable the switches that control the call reestablishment feature for CS and PS services.
1. 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.
1. 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.
1. 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.
1. 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.
1. 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
Step 8 Disable the switch that controls the call reestablishment feature triggered by PS TRB rreset
Step 9 Disable the switch that controls the call reestablishment feature under different RNCs.
1. 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

// Deactivating call reestablishment
SET URRCTRLSWITCH: PROCESSSWITCH4=PHY_RECFG_REEST_SWITCH-0& RB_REL_RL_REEST_SWITCH-0&IUR_RL_REEST_SWITCH0&RB_SETUP_RL_REEST_SWITCH-0, RsvdPara1=RSVDBIT1_BIT22-1&RSVDBIT1_BIT23-1&RSVDBIT1_BIT24-1&RSVDBIT1_BIT251&RSVDBIT1_BIT28-1;
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.5 Performance Monitoring

After the call reestablishment feature is enabled for CS services, observe the following KPIs:
l Call
drop rate: [VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR + VS.RAB.NormRel.AMR)] x 100%
l RAB
setup success rate: [(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR)] x 100%
19/32
11/5/2014
After the call reestablishment feature is enabled, the preceding KPIs should be improved or the same as those before the function was enabled. If the KPIs
deteriorated, optimize them.
After the call reestablishment feature is enabled for PS services, observe the following KPIs:
l Call
drop rate: [VS.RAB.AbnormRel.PS/(VS.RAB.AbnormRel.PS + VS.RAB.NormRel.PS)] x 100%
l RAB
setup success rate: [(VS.RAB.SuccEstabPS.Conv+VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Int

+VS.RAB.SuccEstabPS.Bkg)/(VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str+VS.RAB.AttEstabPS.Int +VS.RAB.AttEstabPS.Bkg)]x100%
After the call reestablishment feature is enabled, the preceding KPIs should be improved or the same as those before the function was enabled. If the KPIs
deteriorated, optimize them.
10.6 Parameter Optimization

To strike a balance between KPIs and user experience, modify the following parameters based on network conditions: T302, N302, T313, N313, N315,
T314(CS), T315(PS), NinsyncInd, NoutsyncInd, TRlFailure, RsvdPara2 (CS), and RsvdPara3 (PS). Because parameter modification greatly affects
network performance, contact Huawei technical support personnel before you modify the parameters.
10.7 Troubleshooting
None.
11 Parameters
Table 11-1 Parameter description
Parameter ID
NE
AMRlcDiscardMode BSC6900
MML Command
Feature ID
ADD UTYPSRBRLC WRFD020900

MOD UTYPSRBRLC
Feature Name
Description
Logical Channel
Management
Meaning:This parameter specifies whether the AM RLC

entity discards the Service Data Units (SDUs) that need
to be sent and the discard mode. This parameter is
applicable only in the RLC AM mode.
- If this parameter is set to
TIMER_BASED_WITH_EXPLICIT_SIGNALLING,
"ExplicitTimerDiscard" is required for triggering SDU
discard. If the transmission time exceeds a preset
value, the TX end discards this SDU. At the same time,
it sends a Move Receiving Window (MRW) command to
the RX end, indicating the discard, to update the RX
window. In this mode, "ExplicitTimerMRW",
"ExplicitTimerDiscard", and "ExplicitMaxMRW" need to
be set.
- If this parameter is set to
DISCARD_AFTER_MAX_DAT_RETRANSMISSIONS,
"MaxDAT" is required for triggering SDU discard. If the
number of transmissions of a PDU exceeds a preset
value, the TX end discards the corresponding SDU. At
the same time, it sends an MRW command to the RX
end, indicating this discard, to update the RX window. In
this mode, "MaxDAT", "TimerMRW", and "MaxMRW"
need to be set.
- If this parameter is set to NO_DISCARD, the TX end
does not discard any SDU. If the number of
transmissions of a PDU exceeds a preset value, the AM
RLC entity will be reset. In this mode,
"NoDiscardMaxDAT" needs to be set.
For details of this parameter, refer to the 3GPP TS
25.322.
This parameter is an advanced parameter. To modify
this parameter, contact Huawei Customer Service
Center for technical support.
GUI Value
Range:TIMER_BASED_WITH_EXPLICIT_SIGNALLING,
NO_DISCARD
Actual Value
Range:TIMER_BASED_WITH_EXPLICIT_SIGNALLING,
NO_DISCARD
Unit:None
Default Value:None
HoAsuTmr
BSC6900
SET USTATETIMER WRFD020202

WRFD020203
Intra RNC Soft Handover Meaning:A timer to RNC wait for the response to active
set update in soft handover procedure.
Inter RNC Soft Handover
Note: The value range of "HoAsuTmr" is 1 to 300000 in
the current version. In a later version, the value range
20/32
11/5/2014

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
HoPhychRecfgTmr
BSC6900

WRFD020304
WRFD020301
Inter Frequency Hard

Handover Based on
Coverage
Meaning:A timer to RNC wait for the response to

physical channel reconfiguration in hard handover
procedure.

Handover Based on DL
QoS
Note: The value range of "HoPhychRecfgTmr" 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
Intra Frequency Hard

Handover

Unit:ms
Default Value:5000
N302
BSC6900
SET
WRFDUCONNMODETIMER 010101
3GPP R9 Specifications
Meaning:Maximum number of retransmissions of CELL

UPDATE/URA UPDATE.Protocol default value is 3.
GUI Value Range:0~7
Unit:None
Default Value:3
N313
BSC6900
SET
Meaning:Maximum number of successive "out of sync"

indications received from L1. Protocol default value is
20.
GUI Value Range:D1, D2, D4, D10, D20, D50, D100,
D200
Actual Value Range:1, 2, 4, 10, 20, 50, 100, 200
Unit:None
Default Value:D50
N315
BSC6900
SET
Meaning:Maximum number of successive "in sync"

indications received from L1 when T313 is activated.
Protocol default value is 1.
GUI Value Range:D1, D2, D4, D10, D20, D50, D100,
D200, D400, D600, D800, D1000
Actual Value Range:1, 2, 4, 10, 20, 50, 100, 200, 400,
600, 800, 1000
Unit:None
Default Value:D1
NInsyncInd
BSC6900
ADD UCELLSETUP WRFD022000

MOD UCELL
Physical Channel
Management
Meaning:This parameter defines the times of

successive in-sync indications required for the NodeB to
trigger the radio link recovery process.The radio link set
remains in the initial state until it has received a certain
number (the number is defined by NInsyncInd) of
successive in-sync indications from L1, and then the
NodeB triggers the radio link recovery process, which
indicates that the radio link set has been synchronized.
Once the radio link recovery process is triggered, the
radio link set is considered to be in the synchronized
state. In the radio link maintenance process,
NInsyncInd is used together with the successive out-ofsync indication counter.
21/32
11/5/2014

Unit:None
Default Value:5
NoDiscardMaxDAT
BSC6900
ADD UTYPSRBRLC WRFD020900

MOD UTYPSRBRLC
Logical Channel
Management
Meaning:This parameter is applicable to only the AM

RLC entity whose "AMRlcDiscardMode" is set to
NO_DISCARD. This parameter specifies the maximum
number of transmissions of a PDU before the RLC
entity is reset. When the mode is set to NO_DISCARD,
the RLC entity will be directly reset if the number of
retransmissions of a PDU reaches the value defined by
this parameter. The number of retransmissions at the
RLC layer increases when the Uu interface signal
quality deteriorates. In this situation, set the parameter
to a large value. For details of this parameter, refer to
the 3GPP TS 25.322.
GUI Value Range:D1, D2, D3, D4, D5, D6, D7, D8, D9,
D10, D15, D20, D25, D30, D35, D40
Actual Value Range:1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20,
25, 30, 35, 40
Unit:None
Default Value:None
NOutsyncInd
BSC6900

MOD UCELL
Physical Channel
Management
Meaning:This parameter defines the times of

successive in-sync indications required for starting the
radio link failure timer. When the radio link 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 outof-sync.
Unit:None
Default Value:50
PROCESSSWITCH4 BSC6900
SET
URRCTRLSWITCH
WRFD020302
WRFD010510
WRFD140205
WRFD020304

Handover Based on
Coverage
Meaning:1) AMR_HHO_FAIL_ROLLBACK_SWITCH
(Hard Handover Failure Rollback Switch for CS AMR
Speech Services)
3.4/6.8/13.6/27.2Kbps
RRC Connection and
Radio Access Bearer
Establishment and
Release
When this switch is turned on, the BSC6900 supports

rollback caused by failed hard handovers of CS AMR
speech services. It is recommended that the timer T312
be set to 1 second (SET UCONNMODETIMER:
T312=1;) before turning on this switch. If the timer T312
is not set to 1 second, AMR noise will occur on some
Voice Service Experience UEs.
Improvement for Weak
Reception Ues
When this switch is turned off, the BSC6900 does not
support rollback caused by failed hard handovers of CS
AMR speech services, leading to call drops.
Handover Based on DL
QoS
2) RRC_CONN_SETUP_OPT_SWITCH (RRC
CONNECTION SETUP Message Optimization Switch)
When this switch is turned on, optimization of the RRC
CONNECTION SETUP message takes effect.
When this switch is turned off, optimization of the RRC
CONNECTION SETUP message does not take effect.
3) PS_F2D_OVERLAP_CELLUPT_SWITCH (Switch for
Simultaneous PS Service Setup F2D and Cell Update
Procedures)
During the PS service setup, the BSC6900 undoes a
CELL_FACH-to-CELL_DCH (F2D for short) procedure
when it receives a Cell Update message with the cause
value "cell reselection" during the F2D procedure.
When this switch is turned on, the BSC6900 temporarily
does not send the RANAP_RAB_ASSIGNMENT_RESP
message to the CN after the F2D procedure is undone
and waits until the Cell Update message is processed
22/32
11/5/2014

and the PS service is set up successfully.
When this switch is turned off, the BSC6900 directly
responds to the CN with a
RANAP_RAB_ASSIGNMENT_RESP message with the
cause value "IU_UNSPEC_FAIL" after the F2D
procedure is undone, indicating that the PS service fails
to be set up.
4) TCP_ACK_ACCELERATOR_SWITCH (Switch for
Throughput Increase in the Case of Simultaneous
uplink and downlink Transmissions)
This switch is turned on to increase the total throughput
in the uplink and downlink only when uplink and
downlink HSPA data is transmitted simultaneously. In
other scenarios, you are advised to turn off the switch.
When this switch is turned on, the function of increasing
the total throughput in the case of simultaneous uplink
and downlink transmissions takes effect.
When this switch is turned off, the function of increasing
the total throughput in the case of simultaneous uplink
and downlink transmissions does not take effect.
5) PHY_RECFG_REEST_SWITCH (Switch for RL
Reestablishments During the Physical Channel
Reconfiguration)
When this switch is turned on, a UE sends the BSC6900
a Cell Update message with the cause value "Radio
Link Failure" and the BSC6900 reestablishes the radio
link for the UE under the following conditions:
The UE has not responded to the Physical Channel
Reconfiguration message.
The BSC6900 detects interrupted downlink
transmission on SRB2 or the NodeB reports that all
radio links of the UE are out of synchronization.
reestablish the radio link for the UE under the preceding
conditions.
6) IUR_RL_REEST_SWITCH (Iur RL Reestablishment
Switch)
When this switch is turned on, a UE sends the BSC6900
a Cell Update message with the cause value "Radio
Link Failure" and the BSC6900 reestablishes the radio
link for the UE under the following conditions:
The UE has a radio link for the DRNC.
The BSC6900 does not perform any procedures or it
performs an active set update or physical channel
reconfiguration procedure.
The BSC6900 detects that the SRB2 is disconnected in
the downlink or the NodeB reports that all radio links of
the UE are out of synchronization.
reestablish the radio link for the UE under the preceding
conditions.
7) RB_SETUP_RL_REEST_SWITCH (Switch for RL
Reestablishment or Cell Update During an RB Setup)
When this switch is turned on and the BSC6900 is
waiting for a UE's response during a radio bearer (RB)
setup CELL_DCH-to-CELL_DCH (D2D) procedure:
The BSC6900 reestablishes a radio link (RL) for the UE
if the BSC6900 detects a signaling radio bearer (SRB)
reset at layer 2 (L2) or all uplink RLs for the UE are out
of synchronization upon expiration of the RL Restore
timer. For the RL reestablishment triggered by SRB
reset detected by BSC6900, the switch
CELLUPT_RLFAILURE_SRBREESTAB_SWITCH under
"PROCESSSWITCH2" in the "SET URRCTRLSWITCH"
command should be turned on.
The BSC6900 performs a cell update if the BSC6900
receives a CELL UPDATE message with the cause
value of RL FAILURE, RLC UNRECOVERABLE
ERROR, or REENTERED SERVICE AREA.
When this switch is turned off and the BSC6900 is
waiting for a UE's response during an RB setup D2D
23/32
11/5/2014

procedure, the BSC6900 does not perform an RL
reestablishment or cell update even if the trigger
conditions are met.
8) RRC_CELLFACH_TRB_RESET_TO_F2D_SWITCH
(The CELL_FACH-to-CELL_DCH state (F2D) transition
switch by TRB reset)
When the BSC6900 receives a TRB reset request from
a UE in the CELL_FACH state, the BSC6900 cannot
respond to the UE with a confirm message if the FACH
is congested. The
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITCH
parameter specifies whether a UE performs an F2D
transition if the number of TRB reset requests from the
UE to the BSC6900 reaches a specified threshold.
If the switch is turned on, the UE moves from the
CELL_FACH state to the CELL_DCH state.
If the switch is turned on, the UE does not move from
the CELL_FACH state to the CELL_DCH state.
This function helps to reduce the number of call drops
caused by the BSC6900 not responding to the TRB
reset requests during FACH congestion.
9) SEND_MSG_NULL_SWITCH (MM NULL Message
Switch)
Whether the BSC6900 sends an MM NULL message to
the CS CN. If the switch
RNC_CS_QUERY_UE_IMEI_SWITCH under
PROCESSSWITCH2 in the SET URRCTRLSWITCH
command is turned on, testing the interworking
between the BSC6900 and the CN is required. If the CN
needs to verify the serial number of direct transfer
messages, turn on this switch.
The BSC6900 rather than the CS CN sends an
IDENTITY REQUEST message to a UE to obtain its
IMEI. Upon receiving an IDENTITY RESPONSE
message from the UE:
The BSC6900 sends an MM NULL message to the CS
CN if this switch is turned on.
The BSC6900 does not send an MM NULL message to
the CS CN if this switch is turned off.
10) CS_HHO_ASYNC_CTRL_SWITCH(Asynchronous
Reconfigure Switch for CS HHO)
When this switch is turned on, the BSC6900 does not
put the activation time information element (IE) in the
hard handover configuration message for CS services.
After receiving the message, the UE immediately
activates the configuration.
When this switch is turned off, the BSC6900 puts the
activation time IE in the hard handover configuration
message for CS services. After receiving the message,
the UE activates the configuration at the specified
activation time.
11) PS_HHO_ASYNC_CTRL_SWITCH(Asynchronous
Reconfigure Switch for PS HHO)
hard handover configuration message for PS services.
After receiving the message, the UE immediately
activates the configuration.
message for PS services. After receiving the message,
the UE activates the configuration at the specified
activation time.
12) IUR_HHO_ASYNC_CTRL_SWITCH(Asynchronous
Reconfigure Switch for Iur HHO)
hard handover configuration message across the Iur
interface. After receiving the message, the UE
immediately activates the configuration.
message across the Iur interface. After receiving the
24/32
11/5/2014

message, the UE activates the configuration at the
specified activation time.
13) R8_UE_SEL_DPUE_SWITCH (Switch for
Preferentially Allocating DPUe Resources to UEs That
Comply with 3GPP Release 8 or Later)
When this switch is turned on, the BSC6900
preferentially allocates DPUe resources in any subrack
to UEs that comply with 3GPP Release 8 or later.
When this switch is turned off, the BSC6900
preferentially allocates DPU resources in the subrack
that the UEs access to UEs that comply with 3GPP
Release 8 or later. The BSC6900 allocates DPU
resources in other subracks only when the amount of
consumed DPU resources in this subrack exceeds a
preset threshold for inter-subrack resource sharing.
14) F2P_DATATRANS_OPTIMIZE_SWITCH(Switch for
Optimized Data Transmission before a State Transition
from CELL_FACH to CELL_PCH or URA_PCH)
Whether the BSC6900 queries the RLC state before
and after a UE moves from the CELL_FACH state to
the CELL_PCH or URA_PCH state due to event 4B.
A UE in the CELL_FACH state can move to the
CELL_PCH or URA_PCH state even when there is
downlink data transmission for the UE. When this
occurs, data packets are suspended on the BSC6900
side. This switch is introduced to solve this problem.
When this switch is turned on, the BSC6900 queries the
RLC state before a UE moves from the CELL_FACH
state to the CELL_PCH or URA_PCH state due to event
4B. If the state query fails, the UE does not perform the
state transition. If the state query succeeds, the UE
continues with the state transition. The BSC6900
queries the RLC state again after the state transition is
complete and before the L2 link is deactivated. If there
is SRB3, SRB4, or TRB data to be transmitted to the UE
on the RLC, the paging procedure is triggered.
When this switch is turned off, the original state
transition from CELL_FACH to CELL_PCH or
URA_PCH is used.
GUI Value
Range:PS_F2D_OVERLAP_CELLUPT_SWITCH,
AMR_HHO_FAIL_ROLLBACK_SWITCH,
PHY_RECFG_REEST_SWITCH,
IUR_RL_REEST_SWITCH,
RB_SETUP_RL_REEST_SWITCH,
RRC_CONN_SETUP_OPT_SWITCH,
TCP_ACK_ACCELERATOR_SWITCH,
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITCH,
SEND_MSG_NULL_SWITCH,
CS_HHO_ASYNC_CTRL_SWITCH,
PS_HHO_ASYNC_CTRL_SWITCH,
IUR_HHO_ASYNC_CTRL_SWITCH,
R8_UE_SEL_DPUE_SWITCH,
F2P_DATATRANS_OPTIMIZE_SWITCH
Actual Value
Range:PS_F2D_OVERLAP_CELLUPT_SWITCH,
AMR_HHO_FAIL_ROLLBACK_SWITCH,
PHY_RECFG_REEST_SWITCH,
IUR_RL_REEST_SWITCH,
RB_SETUP_RL_REEST_SWITCH,
RRC_CONN_SETUP_OPT_SWITCH,
TCP_ACK_ACCELERATOR_SWITCH,
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITCH,
SEND_MSG_NULL_SWITCH,
CS_HHO_ASYNC_CTRL_SWITCH,
PS_HHO_ASYNC_CTRL_SWITCH,
IUR_HHO_ASYNC_CTRL_SWITCH,
R8_UE_SEL_DPUE_SWITCH,
F2P_DATATRANS_OPTIMIZE_SWITCH
Unit:None
Default Value:PS_F2D_OVERLAP_CELLUPT_SWITCH0&AMR_HHO_FAIL_ROLLBACK_SWITCH0&PHY_RECFG_REEST_SWITCH0&IUR_RL_REEST_SWITCH-
25/32
11/5/2014

0&RB_SETUP_RL_REEST_SWITCH0&RRC_CONN_SETUP_OPT_SWITCH0&TCP_ACK_ACCELERATOR_SWITCH0&RRC_CELLFACH_TRB_RESET_TO_F2D_SWITCH0&SEND_MSG_NULL_SWITCH0&CS_HHO_ASYNC_CTRL_SWITCH0&PS_HHO_ASYNC_CTRL_SWITCH0&IUR_HHO_ASYNC_CTRL_SWITCH0&R8_UE_SEL_DPUE_SWITCH0&F2P_DATATRANS_OPTIMIZE_SWITCH-0
RbRecfgRspTmr
BSC6900
Meaning:A timer used to wait for the RB reconfiguration

response from UE in the RB procedure. Refer to the
Note.
Unit:ms
Default Value:5000
RbSetupRspTmr
BSC6900
Meaning:A timer to RNC wait for the RB setup response

from UE in the RB procedure. Refer to the Note.
Unit:ms
Default Value:5000
ReservedSwitch1
BSC6900
SET UCORRMPARA None
None
Meaning:CORRM algorithm reserved switch 1. The

switch is reserved for further change request use.
Disuse statement: This parameter is used temporarily in
patch versions and will be replaced with a new
parameter in later versions. The new parameter ID
reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range:RESERVED_SWITCH_1_BIT1,
RESERVED_SWITCH_1_BIT2,
Actual Value Range:RESERVED_SWITCH_1_BIT1,
26/32
11/5/2014

Unit:None
Default Value:RESERVED_SWITCH_1_BIT10&RESERVED_SWITCH_1_BIT20&RESERVED_SWITCH_1_BIT30&RESERVED_SWITCH_1_BIT40&RESERVED_SWITCH_1_BIT50&RESERVED_SWITCH_1_BIT61&RESERVED_SWITCH_1_BIT70&RESERVED_SWITCH_1_BIT80&RESERVED_SWITCH_1_BIT90&RESERVED_SWITCH_1_BIT100&RESERVED_SWITCH_1_BIT110&RESERVED_SWITCH_1_BIT120&RESERVED_SWITCH_1_BIT130&RESERVED_SWITCH_1_BIT140&RESERVED_SWITCH_1_BIT150&RESERVED_SWITCH_1_BIT160&RESERVED_SWITCH_1_BIT170&RESERVED_SWITCH_1_BIT180&RESERVED_SWITCH_1_BIT190&RESERVED_SWITCH_1_BIT200&RESERVED_SWITCH_1_BIT210&RESERVED_SWITCH_1_BIT220&RESERVED_SWITCH_1_BIT230&RESERVED_SWITCH_1_BIT240&RESERVED_SWITCH_1_BIT250&RESERVED_SWITCH_1_BIT260&RESERVED_SWITCH_1_BIT270&RESERVED_SWITCH_1_BIT280&RESERVED_SWITCH_1_BIT290&RESERVED_SWITCH_1_BIT300&RESERVED_SWITCH_1_BIT310&RESERVED_SWITCH_1_BIT32-0
RlRstrTmr
BSC6900
Meaning:A timer to RNC wait for radio link restoration

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
Unit:ms
Default Value:11000
RsvdPara1
BSC6900
SET
URRCTRLSWITCH
WRFD010101
Meaning:2) NAS_QOS_MOD_SWITCH (QoS Change

Switch for NAS)
When the switch is turned on, for UEs whose HS-DSCH
category is smaller than 13, if the maximum downlink
rate specified in the PDP activation requests from the
UEs exceeds 16 Mbit/s, the requests are sent to the CN
after the rate is changed to 16 Mbit/s.
When the switch is turned off, the PDP activation
27/32
11/5/2014

requests are sent to the CN without changing the
maximum downlink rate.
15) RSVDBIT1_BIT15 (Reserved Parameter 1 Bit 15)
When the switch is turned on, the RNC enables the
function of AMR mute detection.
When the switch is turned off, the RNC disables the
function of AMR mute detection.
When the switch is turned on, the RNC can perform
DRDs during the P2D procedure.
When the switch is turned off, the RNC cannot perform
DRDs during the P2D procedure.
17) SYSHO_CSIN_PERMIT_SWITCH (2G-to-3G CS
Handover Switch)
When the switch is turned on, inter-RAT CS handovers
from 2G cells to 3G cells are allowed.
When the switch is turned off, inter-RAT CS handovers
from 2G cells to 3G cells are not allowed.
When this switch is turned on, the RNC performs a
state transition from CELL_PCH or URA_PCH to
CELL_FACH (P2F) upon receiving a CELL UPDATE
message with the cause value "uplink data
transmission" or "paging response".
When this switch is turned off, if receiving a CELL
UPDATE message with the cause value "uplink data
transmission" or "paging response," the RNC performs
a state transition from CELL_PCH or URA_PCH to
CELL_DCH (P2D) in either of the following scenarios:
(1)Congestion occurs on the FACH.
(2)Congestion occurs on the DCCH, and the value of
the Establishment cause information element (IE) in the
message is Originating Conversational Call,
Terminating Conversational Call, or Emergency Call.
When the switch is turned on, for UEs that are
establishing AMR services and shifting from the
CELL_FACH state to the CELL_DCH state, the RNC
stops establishing AMR services to handle cell update if
the RNC receives from the UEs a cell update message
containing the cause value "cell reselection."
When the switch is turned off, for UEs that are
establishing AMR services and shifting from the
CELL_FACH state to the CELL_DCH state, if the RNC
receives from the UEs a cell update message
containing the cause value "cell reselection," the RNC
stops establishing AMR services to handle cell update
and resumes AMR services only after cell update is
completed.
When the switch is turned on, the RNC does not trigger
cell update with the cause value "RL Failure" if the RNC
detects interrupted downlink transmission on SRB2.
When the switch is turned off, the RNC triggers cell
update with the cause value "RL Failure" and
reestablishes radio links if the RNC detects interrupted
downlink transmission on SRB2.
When the switch is turned on, the RNC does not trigger
cell update with the cause value "RL Failure" reported
by a UE if the associated NodeB reports to the RNC
that all radio links for the UE experience
synchronization loss.
When the switch is turned off, the RNC triggers cell
update with the cause value "RL Failure" reported by a
UE and reestablishes radio links, if the associated
NodeB reports to the RNC that all radio links for the UE
experience synchronization loss.
28/32
11/5/2014

When the switch is turned on, for UEs using CS
services, the RNC does not trigger cell update with the
cause value "RL Failure" reported by a UE, if the RNC
detects interrupted downlink transmission on SRB2, or if
the associated NodeB reports to the RNC that all radio
links for the UE experience synchronization loss.
When the switch is turned off, for UEs using CS
services, the RNC triggers cell update with the cause
value "RL Failure" reported by a UE and reestablishes
radio links, if the RNC detects interrupted downlink
transmission on SRB2, or if the associated NodeB
reports to the RNC that all radio links for the UE
When the switch is turned on, for UEs using PS services
only, the RNC does not reestablish radio links for a UE
if the RNC detects interrupted downlink transmission on
SRB2, or if the associated NodeB reports to the RNC
that all radio links for the UE experience
synchronization loss.
When the switch is turned off, for UEs using PS services
only, the RNC triggers cell update with the cause value
"RL Failure" reported by a UE and reestablishes radio
link, if the RNC detects interrupted downlink
transmission on SRB2, or if the associated NodeB
reports to the RNC that all radio links for the UE
When the switch is turned on, the RNC does not
reestablish radio links for a UE if the UE reports to the
RNC cell update caused by SRB reset.
When the switch is turned off, the RNC reestablishes
radio links for a UE if the UE reports to the RNC cell
update caused by SRB reset.
When the switch is turned on, for UEs using CS
services, if a NodeB reports to the RNC that all radio
links for a UE experience synchronization loss, the RNC
starts the RL Restore timer whose duration is specified
by the RlRstrTmr parameter in the SET USTATETIMER
command. After the timer has expired, the RNC triggers
cell update with the cause value "radio link failure" and
reestablishes radio links for the UE.
When the switch is turned off, for UEs using CS
services, if a NodeB reports to the RNC that all radio
links for a UE experience synchronization loss, the RNC
starts the RL Restore timer whose duration is specified
by the T313 parameter in the SET
UCONNMODETIMER command. After the timer has
expired, the RNC triggers cell update with the cause
value "radio link failure" and reestablishes radio links for
the UE.
When the switch is turned off, the RNC performs the
CELL_DCH-to-CELL_FACH (D2F for short) procedure
on UEs that support fast dormancy.
When the switch is turned on, the RNC performs the
CELL_DCH-to-CELL_PCH (D2P for short) procedure on
UEs that support fast dormancy.
interface.
GUI Value Range:RSVDBIT1_BIT1,
NAS_QOS_MOD_SWITCH, RSVDBIT1_BIT3,
RSVDBIT1_BIT4, RSVDBIT1_BIT5, RSVDBIT1_BIT6,
RSVDBIT1_BIT7, RSVDBIT1_BIT8, RSVDBIT1_BIT9,
RSVDBIT1_BIT10, RSVDBIT1_BIT11,
RSVDBIT1_BIT16, SYSHO_CSIN_PERMIT_SWITCH,
29/32
11/5/2014

RSVDBIT1_BIT32
Actual Value Range:This parameter is set to 0 or 1
according to the related domains.
Unit:None
Default Value:RSVDBIT1_BIT10&NAS_QOS_MOD_SWITCH-0&RSVDBIT1_BIT30&RSVDBIT1_BIT4-0&RSVDBIT1_BIT50&RSVDBIT1_BIT6-0&RSVDBIT1_BIT70&RSVDBIT1_BIT8-0&RSVDBIT1_BIT90&RSVDBIT1_BIT10-0&RSVDBIT1_BIT110&RSVDBIT1_BIT12-0&RSVDBIT1_BIT130&RSVDBIT1_BIT14-0&RSVDBIT1_BIT150&RSVDBIT1_BIT160&SYSHO_CSIN_PERMIT_SWITCH1&RSVDBIT1_BIT18-1&RSVDBIT1_BIT191&RSVDBIT1_BIT20-1&RSVDBIT1_BIT211&RSVDBIT1_BIT22-1&RSVDBIT1_BIT231&RSVDBIT1_BIT24-1&RSVDBIT1_BIT251&RSVDBIT1_BIT26-1&RSVDBIT1_BIT271&RSVDBIT1_BIT28-1&RSVDBIT1_BIT291&RSVDBIT1_BIT30-1&RSVDBIT1_BIT310&RSVDBIT1_BIT32-1
RsvdPara2
BSC6900
SET
WRFDUCACALGOSWITCH 020101
Admission Control
Meaning:Reserved parameter 2.
interface.
Unit:None
Default Value:0
RsvdPara3
BSC6900
SET
WRFDUCACALGOSWITCH 020101
Admission Control
Meaning:Reserved parameter 3.
interface.
Unit:None
Default Value:0
T302
BSC6900
SET
Meaning:T302 is started after the UE transmits the

CELL UPDATE/URA UPDATE message and stopped
after the UE receives the CELL UPDATE
CONFIRM/URA UPDATE CONFIRM message. CELL
UPDATE/URA UPDATE will be resent upon the expiry of
the timer if V302 less than or equal to N302; otherwise,
the UE will enter idle mode. Protocol default value is
4000.
GUI Value Range:D100, D200, D400, D600, D800,
D1000, D1200, D1400, D1600, D1800, D2000, D3000,
D4000, D6000, D8000
Actual Value Range:100, 200, 400, 600, 800, 1000,
1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000
Unit:ms
Default Value:D2000
T313
BSC6900
SET
Meaning:T313 is started after the UE detects

consecutive N313 "out of sync" indications from L1.
T313 is stopped after the UE detects consecutive N315
"in sync" indications from L1.It indicates Radio Link (RL)
30/32
11/5/2014

failure upon expiry. Protocol default value is 3.
Unit:s
Default Value:3
T314
BSC6900
SET
Meaning:T314 is started when the criteria for radio link

failure are fulfilled and only radio bearers (RBs)
associated with T314 exist.T314 is stopped after the
Cell Update procedure has been completed. Protocol
default value is 12.
In case of the RL failure when the UE is in CELL_DCH
state, If the RL cannot be successfully reconfigured by
CELL UPDATE CONFIRM before the expiry of the
corresponding T314 (or T315), CELL UPDATE will be
resent for RL reconfiguration (this operation relates to
T302 and N302). It is recommended that T314 be set to
greater than T302*N302. The smaller the value of T314
is, the higher the call drop rate of the corresponding
service is. When T314 expires and the UE is performing
a CS service, or T315 expires and the UE is performing
a PS service,the BSC6900 releases the RRC
connection.
GUI Value Range:D0, D2, D4, D6, D8, D12, D16, D20
Unit:s
Default Value:D0
T315
BSC6900
SET
Meaning:T315 is started when the criteria for radio link

failure are fulfilled, and only the radio bearer associated
with T315 exists.T315 is stopped after the Cell Update
procedure has been completed. Protocol default value
is 180.
In case of the RL failure when the UE is in CELL_DCH
state, T315 (or T314) is started and CELL UPDATE is
sent. If the RL cannot be successfully reconfigured by
CELL UPDATE CONFIRM before the expiry of the
corresponding T315 (or T314), CELL UPDATE will be
resent for RL reconfiguration (this operation relates to
T302 and N302). It is recommended that T315 be set to
greater than T302*N302. The smaller the value of T315
is, the higher the call drop rate of the corresponding
service is. When T314 expires and the UE is performing
a CS service, or T315 expires and the UE is performing
a PS service,the BSC6900 releases the RRC
connection.
GUI Value Range:D0, D10, D30, D60, D180, D600,
D1200, D1800
Unit:s
Default Value:D0
TRlFailure
BSC6900

MOD UCELL
Physical Channel
Management
Meaning:Radio link failure timer duration. When the

radio link 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.
Actual Value Range:0~25.5
Unit:0.1s
Default Value:50
12 Counters
31/32
11/5/2014
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)"
32/32

Call Restablisment

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Call Restablisment

Uploaded by

Copyright:

Available Formats

11/5/2014

RAN Feature Documentation

Trademarks and Permissions

RAN Feature Documentation

6 Air-Interface Process Overlap

7 Air-Interface Process Timeout

RAN Feature Documentation

1 About This Document

1.2 Intended Audience

to understand the call reestablishment feature

with Huawei products

familiar with UMTS basics

1.3 Change History

Added 6 Air-Interface Process Overlap

Added 7 Air-Interface Process Timeout

RAN Feature Documentation

channel configuration control (DCCC), and measurement control.

Physical channel reconfiguration during a hard

Physical channel reconfiguration in compressed mode

Physical channel reconfiguration during a serving cell

Physical channel reconfiguration for inter RNC-UE timer

RAN Feature Documentation

Air-interface process overlap

Physical channel reconfiguration during a hard

Physical channel reconfiguration in compressed mode

Physical channel reconfiguration for inter RNC-UE timer

Physical channel reconfiguration during a serving cell

RsvdPara1:RSVDBIT1_BIT28 Switch Status

RAN Feature Documentation

Table 3-2 Switches for call reestablishment triggered by an RL failure

RL failures can trigger call reestablishment without enabling process switches.

3.2 Call Reestablishment

Under the Same RNC

RAN Feature Documentation

Under Different RNCs over the Iur Interface

Figure 3-3 shows how call establishment is implemented.

RAN Feature Documentation

RAN Feature Documentation

4.1 SRB Reset Detection

the call reestablishment feature is enabled, call reestablishment is triggered.

Physical channel reconfiguration is controlled by

Active set update

RAN Feature Documentation

SRB reconfiguration during dynamic channel

4.2 Call Reestablishment

5.2 TRB Reset Detection

The PS service is controlled by

PDU sending is controlled by SET

RAN Feature Documentation

5.3 Call Reestablishment

6 Air-Interface Process Overlap

6.1 Air-Interface Process Overlap Detection

Figure 6-1 Call reestablishment triggered by air-interface process overlap in scenario 1

RAN Feature Documentation

Figure 6-2 Call reestablishment triggered by air-interface process overlap in scenario 2

RAN Feature Documentation

ReservedSwitch1:RESERVED_SWITCH_1_BIT14 and SET

ProcessSwitch4: PHY_RECFG_REEST_SWITCH and SET

6.2 Call Reestablishment

7 Air-Interface Process Timeout

RAN Feature Documentation

7.1 Air-Interface Process Timeout Detection

The CS service is controlled by

RB setup is controlled by SET UCORRMPARA: