Professional Documents
Culture Documents
Issue 06
Date 2015-08-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 a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview.........................................................................................................................................9
2.1 Introduction....................................................................................................................................................................9
2.2 Benefits...........................................................................................................................................................................9
2.3 Architecture..................................................................................................................................................................9
4 SRB Reset......................................................................................................................................23
4.1 SRB Reset Detection....................................................................................................................................................23
4.1.1 Detection Principle....................................................................................................................................................23
4.1.2 Switches for Call Reestablishment Triggered by an SRB Reset...............................................................................23
4.2 Call Reestablishment....................................................................................................................................................25
4.2.1 Triggering..................................................................................................................................................................26
4.2.2 Implementation..........................................................................................................................................................26
5 TRB Reset......................................................................................................................................27
5.1 TRB Reset Detection....................................................................................................................................................27
5.1.1 Detection Principle....................................................................................................................................................27
5.1.2 Switches for Call Reestablishment Triggered by a TRB Reset.................................................................................27
5.2 Call Reestablishment....................................................................................................................................................28
5.2.1 Triggering..................................................................................................................................................................28
5.2.2 Implementation..........................................................................................................................................................28
8 Related Features...........................................................................................................................51
9 Network Impact...........................................................................................................................52
10 Engineering Guidelines...........................................................................................................54
10.1 When to Use Call Reestablishment............................................................................................................................54
10.2 Required Information.................................................................................................................................................54
10.3 Planning......................................................................................................................................................................55
10.4 Deployment................................................................................................................................................................55
10.4.1 Requirements...........................................................................................................................................................55
10.4.2 Data Preparation......................................................................................................................................................56
10.4.3 Activation................................................................................................................................................................62
10.4.4 Activation Observation............................................................................................................................................68
10.4.5 Deactivation.............................................................................................................................................................68
10.5 Performance Monitoring.............................................................................................................................................73
10.6 Parameter Optimization..............................................................................................................................................75
10.7 Troubleshooting..........................................................................................................................................................75
11 Parameters...................................................................................................................................76
12 Counters....................................................................................................................................185
13 Glossary.....................................................................................................................................186
14 Reference Documents.............................................................................................................187
1.1 Scope
This document describes the WRFD-140103 Call Reestablishment, including its technical
principles, related features, network impact, and engineering guidelines.
NE Type NE Model
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN15.0 06 (2015-08-30)
This issue includes the following changes.
RAN15.0 05 (2014-09-15)
This issue includes the following changes.
RAN15.0 04 (2014-03-31)
This issue includes the following changes.
RAN15.0 03 (2013-09-30)
This issue includes the following changes.
RAN15.0 02 (2013-06-30)
This issue includes the following changes.
RAN15.0 01 (2013-04-28)
This issue does not include any changes.
l Changed RsvdPara1
(BSC6900,BSC6910):
RSVDBIT1_BIT26 to
OptimizationSwitch
(BSC6900,BSC6910):
UE_SRB_RESET_SWITCH.
WRFD- Call Y Y Y Y Y Y
140103 Reestabl
ishment
NOTE
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is
not involved, that is, a feature does not require the support of the NE.
The features described in this document are implemented in the same way on macro, micro, and
LampSite base stations.
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.
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 out-of-synchronization problem
or a signaling radio bearer (SRB) reset.
l Call reestablishment initiated by the RAN: After the RAN detects a service interruption or
an access failure (possibly due to a signaling radio bearer (SRB) reset or an uplink RL out-
of-synchronization problem) before the UE does, the RAN stops the UE's downlink RL
sets to enable the UE to detect downlink RL out-of-synchronization problem as soon as
possible. Upon detecting a downlink RL out-of-synchronization problem, the UE sends a
call reestablishment request to the RAN to restore services.
2.2 Benefits
Call reestablishment initiated by the RAN improves user experience.
2.3 Architecture
Causes That Can Trigger Call Reestablishment
The causes that can trigger call reestablishment after a service interruption or an access failure
are as follows:
l RL out-of-synchronization problem
l SRB reset
l PS TRB reset
l Air interface process timeout
l Air interface process overlap
Table 2-1 Mapping between service types, triggering processes, and triggering causes
Physical Hard √ √ √ √
channel handove
reconfig r
uration
Compres √ √ √
sed
mode
setup
Serving √ √ √ √
cell
update
Inter-RAT handover √ √ √
RB setup √ √ √ √
RB reconfiguration √ √ √ √
Measurement control √ √ √
command issuing
PS Power adjustments √ √ √ √
for HSUPA channels
PS data transmission √
RB release √ √ √ √
NOTE
The cause "RL out-of-synchronization problem" can trigger call reestablishment in processes not listed in
Table 2-1.
The other causes can trigger call reestablishment only in processes listed in Table 2-1.
After you select UE_DCH_CU_RL_REEST_SWITCH under the OptimizationSwitch7
(BSC6900,BSC6910) parameter, the RNC performs call reestablishment after receiving a CELL UPDATE
message from a UE with the cause value Radio Link Failure or RLC Unrecoverable Error as a response to
one of the following messages delivered by the RNC:
You are also advised to select the PSREL_DUETO_CSFAIL_OPTIMIZE_SWITCH check box under
the OptimizationSwitch(BSC6900,BSC6910) parameter to ensure the call drop rate benefits provided by
turning on the UE_DCH_CU_RL_REEST_SWITCH.
l Service switches
Service switches include a CS service switch and a PS service switch. Enable a service
switch before enabling a process or cause switch.
l Process switches
All triggering processes listed in Table 2-1 except PS data transmission have a switch.
l Cause switches
All causes except "Air interface process timeout" have a switch.
Call reestablishment can be triggered only when required switches are enabled.
For details about service/process/cause switches of call reestablishment, see descriptions in the
follow-up chapters.
l If the number of "in-sync" indications received by the NodeB reaches the value of the
NINSYNCIND(BSC6900,BSC6910) parameter before the TRlFailure
(BSC6900,BSC6910) timer expires, the NodeB stops and resets the TRlFailure
(BSC6900,BSC6910) timer.
l If the number of "in-sync" indications received by the NodeB does not reach the value of
the NINSYNCIND(BSC6900,BSC6910) parameter before the TRlFailure
(BSC6900,BSC6910) timer expires, the NodeB considers that an RL out-of-
synchronization problem has occurred and identifies the RL set where the problem is
located. (An RL set contains all the RLs of a UE under a NodeB.)
NOTE
When a UE's uplink RL sets are all out of synchronization, the events that occur depend on the
situation:
l When the call reestablishment function is not enabled, the call drops or the UE access finally
fails.
l When the call reestablishment function is enabled, the RNC activates a synchronization
timer. If the NodeB does not detect uplink RL synchronization before the timer expires,
call reestablishment is initiated.
On T313(BSC6900,BSC6910)
NOTE
NOTE
witch(BSC6900,BSC6910) (BSC6900,BSC6910)
parameter parameter.
NOTE
l The switch for CS+PS combined services is the same as that for CS services.
l 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 out-of-synchronization problem can be
performed under the same RNC or under different RNCs over the Iur interface.
l If the RNC does not receive the Cell Update message from the UE before the timers expire,
the call drops or UE access fails.
l If the RNC receives the Cell Update message from the UE before the timers expire, the
RNC stops the timers and initiates call reestablishment.
Figure 3-1 shows the signaling procedure for call reestablishment triggered by an uplink RL
out-of-synchronization problem under the same RNC.
Figure 3-2 shows the signaling procedure for call reestablishment triggered by an uplink RL
failure under different RNCs over the Iur interface.
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.
In Figure 3-2, NodeB (Cell A) is under the SRNC and NodeB (Cell B) is under the DRNC.
Before the uplink RL out-of-synchronization problem, the UE has established an RL with each
NodeB. After the uplink RL out-of-synchronization problem, the UE attempts to establish a new
RL only with NodeB (Cell B).
3.2.2 Implementation
Figure 3-3 shows how call establishment is implemented.
1. After the NodeB stops downlink power transmission for a UE's RLs, the UE starts the T313
(BSC6900,BSC6910) timer if the number of "out-sync" indications received consecutively
from Layer 1 reaches the value of the N313(BSC6900,BSC6910) parameter.
NOTE
The higher the value of the N313(BSC6900,BSC6910) parameter, the harder it will be for the UE to
detect an RL out-of-synchronization problem and the longer the UE may stay on the verge of RL
out-of-synchronization problem.
2. If the number of "in-sync" indications received consecutively from Layer 1 does not reach
the value of the N315(BSC6900,BSC6910) parameter before the T313
(BSC6900,BSC6910) 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(BSC6900,BSC6910) timer as well as the T314(BSC6900,BSC6910) timer
for CS services or the T315(BSC6900,BSC6910) timer for PS services.
3. If the UE does not receive the Cell Update Confirm message from the RAN side after the
T302(BSC6900,BSC6910) timer expires, the UE retransmits the Cell Update message until
the T314(BSC6900,BSC6910)/T315(BSC6900,BSC6910) timer expires: (The number of
retransmissions is determined by the value of the T302(BSC6900,BSC6910) parameter.)
l If faulty RLs are restored before T314(BSC6900,BSC6910)/T315(BSC6900,BSC6910)
expires, the call reestablishment is successful. Interrupted services are restored or UE access
succeeds.
l If faulty RLs are not restored before T314(BSC6900,BSC6910)/T315
(BSC6900,BSC6910) expires, the call reestablishment fails. Services are released or UE
access fails.
NOTE
l The network side receives the RADIO LINK FAILURE INDICATION message from the
NodeB.
The UE transits to the common channel. Then, according to the traffic volume, it transits to a
dedicated channel to finish the call reestablishment. If an SRB resets during the D2P state
transition, the call reestablishment is performed in the same way as that performed during an
SRB reset.
If there is data in the RLC buffer after the D2P state transition is successful, you can run the
RNC MML command SET UALGORSVPARA with RESERVED_SWITCH_5_BIT13
under RsvSwitch5(BSC6900,BSC6910) set to 0 and run the RNC MML command SET
URRCTRLSWITCH with F2P_DATATRANS_OPTIMIZE_SWITCH under
PROCESSSWITCH4(BSC6900,BSC6910) set to 1 to send paging messages to the UE again.
4 SRB Reset
l If the call reestablishment function is not enabled, the RNC sends the Iu Release Request
message to the core network.
l If the call reestablishment function is enabled, call reestablishment is triggered.
NOTE
l The switch for CS+PS combined services is the same as that for CS services.
l 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 process timer so that call
reestablishment is more likely to be triggered by an SRB reset. The following table lists the
mapping between processes and timers.
Process Timer
RB reconfiguration RbRecfgRspTmr(BSC6900,BSC6910)
RB setup RbSetupRspTmr(BSC6900,BSC6910)
4.2.1 Triggering
Figure 4-1 shows the signaling procedure for call reestablishment triggered by an SRB reset.
4.2.2 Implementation
Except that the trigger cause is different, the process of call reestablishment triggered by an SRB
reset is the same as that triggered by an RL out-of-synchronization problem. For details, see
3.2.2 Implementation.
5 TRB Reset
l If the call reestablishment function 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 function 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.
NOTE
Call reestablishment triggered by a TRB reset applies only to a single PS service of a UE in the CELL_DCH
state.
5.2.1 Triggering
Figure 5-1 shows the signaling procedure for call reestablishment triggered by a TRB reset.
5.2.2 Implementation
Except that the trigger cause is different, the process of call reestablishment triggered by a TRB
reset is the same as that triggered by an RL out-of-synchronization problem. For details, see
section 3.2.2 Implementation.
l Scenario 1: The RNC sends the Radio Bearer Setup message to a UE but does not receive
an ACK message.
l Scenario 2: The RNC sends the Radio Bearer Setup message to a UE and receives an ACK
message. However, the RNC does not receive the Radio Bearer Setup Complete message
from the UE.
Scenario 1
The RNC sends the Radio Bearer Setup message to a UE but does not receive an ACK message
before the RbSetupRspTmr(BSC6900,BSC6910) timer expires. The radio Bearer Setup fails
and either of the following occurs:
l If the call reestablishment function is not enabled, the RAN requests the UE to release the
Iu interface resources and the call drops.
l If the call reestablishment function is enabled, the RNC does not request the UE to release
the Iu interface resources but initiates call reestablishment.
In this scenario, the call reestablishment function is controlled by the service switch and process
switch, as described in Table 6-1.
Table 6-1 Switches for call reestablishment triggered by radio bearer setup timeout in scenario
1
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Figure 6-1 shows the signaling procedure for call reestablishment triggered by radio bearer setup
timeout in scenario 1.
Figure 6-1 Call reestablishment triggered by radio bearer setup timeout in scenario 1
Scenario 2
The RNC sends the Radio Bearer Setup message to a UE and receives an ACK message.
However, the RNC does not receive the Radio Bearer Setup Complete message from the UE
before the RbSetupRspTmr(BSC6900,BSC6910) timer expires. Then either of the following
occurs:
l If the call reestablishment function is not enabled, the RNC sends the Iu Release Request
message to the core network and the call drops.
l If the call reestablishment function is enabled, the RNC does not send the Iu Release
Request message to the core network but initiates call reestablishment.
In this scenario, the call reestablishment function is controlled by the service switch and process
switch, as described in Table 6-2.
Table 6-2 Switches for call reestablishment triggered by radio bearer setup timeout in scenario
2
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l 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 function is controlled by the service switch and process
switch, as described in Figure 6-2.
Figure 6-2 Call reestablishment triggered by radio bearer setup timeout in scenario 2
l Scenario 1: The RNC sends the Radio Bearer Release message to a UE but does not receive
an ACK message.
l Scenario 2: The RNC sends the Radio Bearer Release message to a UE and receives an
ACK message. However, the RNC does not receive the Radio Bearer Release Complete
message from the UE.
NOTE
All the radio bearer releases mentioned in this section are releases of PS services
Scenario 1
The RNC sends the Radio Bearer Release message to a UE but does not receive an ACK message
before the RbRelRspTmr(BSC6900,BSC6910) timer expires. Then either of the following
occurs:
l If the call reestablishment function is not enabled, the RNC sends the Iu Release Request
message to the core network and the call drops.
l If the call reestablishment function is enabled, the RNC does not send the Iu Release
Request message to the core network and call reestablishment is triggered.
To enable the call reestablishment function triggered by radio bearer release timeout, enable the
service and process switches listed in Table 6-3.
Table 6-3 Switches for call reestablishment triggered by radio bearer release timeout in scenario
1
NOTE
l The call reestablishment function triggered by radio bearer release timeout applies only to CS+PS
combined services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished only for
CS service.
Figure 6-3 shows the signaling procedure for call reestablishment triggered by radio bearer
release timeout in scenario 1.
Figure 6-3 Call reestablishment triggered by radio bearer release timeout in scenario 1
Scenario 2
The RNC sends the Radio Bearer Release message to a UE and receives an ACK message.
However, the RNC does not receive the Radio Bearer Release Complete message from the UE
before the RbRelRspTmr(BSC6900,BSC6910) timer expires. Then either of the following
occurs:
l If the call reestablishment function is not enabled, the RNC sends the Iu Release Request
message to the core network and the call drops.
l If the call reestablishment function is enabled, the RNC does not send the Iu Release
Request message to the core network and call reestablishment is triggered.
To enable the call reestablishment function in this scenario, enable the service and process
switches listed in Table 6-4.
Table 6-4 Switches for call reestablishment triggered by radio bearer release timeout in scenario
2
Service Switch Process Switch Cause Switch
NOTE
l The call reestablishment function triggered by radio bearer release timeout applies only to CS+PS
combined services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Figure 6-4 shows the signaling procedure for call reestablishment triggered by radio bearer
release timeout in scenario 2.
Figure 6-4 Call reestablishment triggered by radio bearer release timeout in scenario 2
Table 6-5 Switches for call reestablishment triggered by radio bearer reconfiguration
timeout
NOTE
When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Figure 6-5 shows the signaling procedure for call reestablishment triggered by radio bearer
reconfiguration timeout.
l If the call reestablishment function is not enabled, the RNC sends an Iu Release Request
message to the core network and the call drops.
l If the call reestablishment function is enabled, the RNC does not send an Iu Release Request
message to the core network but initiates call reestablishment.
To enable the call reestablishment function in this scenario, enable the service and process
switches listed in Table 6-6.
Table 6-6 Switches for call reestablishment triggered by physical channel reconfiguration
timeout
NOTE
When call reestablishment is triggered for CS+PS combined services, both CS and PS services are
reestablished.
Figure 6-6 shows the signaling procedure for call reestablishment triggered by physical channel
reconfiguration timeout.
l If the call reestablishment function is not enabled, the RNC sends an Iu Release Request
message to the core network and the call drops.
l If the call reestablishment function is enabled, the RNC does not send an Iu Release Request
message to the core network but initiates call reestablishment.
To enable the call reestablishment function in this scenario, enable the service and process
switches listed in Table 6-7.
Table 6-7 Switches for call reestablishment triggered by security mode setup timeout
NOTE
Call reestablishment triggered by security mode setup timeout applies to scenarios where a UE has
set up a single service or combined services but the UE experiences a security mode setup failure
when attempting to set up another service.
Figure 6-7 shows the signaling procedure for call reestablishment triggered by security
mode setup timeout.
The RNC initiates call reestablishment if the UE does not acknowledge the following messages
or the UE does not send the complete message to the RNC for the following message:
The signaling procedures are similar to those of air-interface process timeout. For details, see
6.1 Air-Interface Process Timeout Detection.
To enable the call reestablishment function in this scenario, enable the service, process, and
cause switches.
Table 7-1 Switches for call reestablishment triggered by air-interface process overlap in scenario
1 (ACK of the Radio Bearer Setup message is not received.)
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-2 Switches for call reestablishment triggered by air-interface process overlap in scenario
2 (ACK of the Radio Bearer Setup message is received.)
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-3 Switches for call reestablishment triggered by air-interface process overlap in scenario
1 (ACK of the Radio Bearer Release message is not received.)
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-4 Switches for call reestablishment triggered by air-interface process overlap in scenario
2 (ACK of the Radio Bearer Release message is received.)
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-5 Switches for call reestablishment triggered by air-interface process overlap in scenario
1 (ACK of the Radio Bearer Reconfiguration message for a single PS service is not received.)
Table 7-6 lists the switches for call reestablishment triggered when the RNC does not receive
the ACK of the Radio Bearer Reconfiguration message for CS+PS combined services.
Table 7-6 Switches for call reestablishment triggered by air-interface process overlap in scenario
1 (ACK of the Radio Bearer Reconfiguration message for CS+PS combined services is not
received.)
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-7 Switches for call reestablishment triggered when the UE does not send a Physical
Channel Reconfiguration Complete message to the RNC for a single PS service
Table 7-8 lists the switches for call reestablishment triggered when the UE does not send the
RNC a Physical Channel Reconfiguration Complete message for CS+PS combined services.
Table 7-8 Switches for call reestablishment triggered when the UE does not send a Physical
Channel Reconfiguration Complete message to the RNC for CS+PS combined services
NOTE
l The switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-9 Switches for call reestablishment triggered when the UE does not send the RNC a
Security Mode Complete message
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
Table 7-10 lists the switches for call reestablishment triggered when the UE does not send the
RNC a Security Mode Complete message. These switches apply to scenarios where the UE has
set up a CS service and attempts to set up a new service.
Table 7-10 Switches for call reestablishment triggered when the UE does not send the RNC a
Security Mode Complete message
NOTE
l The service switch for CS+PS combined services is the same as that for CS services.
l When call reestablishment is triggered for CS+PS combined services, calls are reestablished for both
CS and PS services.
8 Related Features
Prerequisite Features
None
Impacted Features
None
9 Network Impact
System Capacity
No impact.
Network Performance
When the call reestablishment function 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 function affects end user experience. This function generally affects
CS user experience with more occurrences of mute voice and garbled noise, which can be
observed by the following counters:
l VS.AMRNB.ULSilent.OccurNum(BSC6900,BSC6910)
l VS.AMRNB.DLSilent.OccurNum(BSC6900,BSC6910)
l VS.AMRWB.ULSilent.OccurNum(BSC6900,BSC6910)
l VS.AMRWB.DLSilent.OccurNum(BSC6900,BSC6910)
l VS.AMRNB.ULGarbledVoice.OccurNum(BSC6900,BSC6910)
l VS.AMRWB.ULGarbledVoice.OccurNum(BSC6900,BSC6910)
l VS.AMRNB.DLGarbledVoice.OccurNum(BSC6900,BSC6910)
l VS.AMRWB.DLGarbledVoice.OccurNum(BSC6900,BSC6910)
When the call reestablishment function is enabled for the inter-RAT handover, the values of the
KPIs IRATHO.AttOutCS(BSC6900,BSC6910) and IRATHO.AttOutPSUTRAN
(BSC6900,BSC6910) will increase and the handover success rate also increases because inter-
RAT handovers are initiated again after call reestablishment is complete.
After the D2P reconfiguration and reestablishment algorithm is enabled, D2P state transition
attempts and successful D2P state transitions increase. Meanwhile, call drops or second RRC
connection setup attempts during CELL_DCH-to-CELL_PCH state transitions increase. That
is, the values of the following counters increase:
10 Engineering Guidelines
NOTE
To enable call reestablishment due to different trigger causes, processes, or service types, different
switches need to be turned on. When the calculation result of the formula for CS or PS services is
greater than 30%, it is recommended that all corresponding switches for CS or PS services be turned
on.
l Whether switches for performance measurement of failed call reestablishment attempts
during RB setup procedures have been turned on
Check whether RESERVED_SWITCH_5_BIT6 under RsvSwitch5
(BSC6900,BSC6910) and RESERVED_SWITCH_10_BIT29 under RsvSwitch10
(BSC6900,BSC6910) have been set to ON. If they are not set to ON, it is recommended
that the following commands be executed to set them to ON:
SET UALGORSVPARA: RsvSwitch5=RESERVED_SWITCH_5_BIT6-1;
SET UALGORSVPARA: RsvSwitch10=RESERVED_SWITCH_10_BIT29-1;
After the preceding switches are set to ON, the RNC counts call reestablishment attempts
that fail in the following scenarios:
– Scenario 1: In the RAB setup process, the RNC delivers a RADIO BEARER SETUP
message to the UE but does not receive an ACK message from the UE. It initiates a call
reestablishment process but the process fails.
– Scenario 2: In the RAB setup process, the RNC delivers a RADIO BEARER SETUP
message to the UE but does not receive an ACK message from the UE. Instead, it
receives a cell update request with the cause value "radio link failure" or "RLC
Unrecoverable error" and the cell update process fails.
– Scenario 3: In the RAB setup process, the RNC delivers a RADIO BEARER SETUP
message to the UE and receives a cell update request with a cause value "cell
reselection." However, the call update process fails.
l Value of the RAB assignment request response timer on the CN side
Value of the RAB assignment request response timer on the CN side, which must be greater
than the value of RbSetupRspTmr(BSC6900,BSC6910) plus the timer
CSRLReEstCellUpdateTmr(BSC6900,BSC6910) (for CS services) or
PSRLReEstCellUpdateTmr(BSC6900,BSC6910) (for PS services).
10.3 Planning
None
10.4 Deployment
10.4.1 Requirements
None
10.4.3 Activation
Step 2 Enable the switches that control the call reestablishment function for CS and PS services.
Step 3 Enable the switches that control the call reestablishment function triggered by RL out-of-
synchronization problems and SRB resets.
Step 4 Set the timer for the Active Set Update process.
l Run the SET URRCTRLSWITCH command and select ASU_RL_RESET_SWITCH
(ASU_RL_RESET_SWITCH) under Optimization Switch.
l Run the SET USTATETIMER command to set HO active set update response timer.
Step 5 Enable the switch that control the call reestablishment function triggered by measurement
control.
Step 6 Enable the switch that control the call reestablishment function triggered by TRB resets.
Step 7 Enable the switch that controls the call reestablishment function triggered by physical channel
reconfiguration.
l Run the SET URRCTRLSWITCH command and select
PHY_RECFG_REEST_SWITCH under Process Control Switch 4.
l Run the SET USTATETIMER command to set HO PhyCh reconfiguration timer.
Step 8 Enable the switch that controls the call reestablishment function triggered by RB setup.
NOTE
The RAB assignment timer needs to be configured on the CN side and its value must be greater than the
value of RbSetupRspTmr(BSC6900,BSC6910) plus the timer CSRLReEstCellUpdateTmr
(BSC6900,BSC6910) (for CS services) or PSRLReEstCellUpdateTmr(BSC6900,BSC6910) (for PS
services)..
Step 9 Enable the switch that controls the call reestablishment function triggered by RB reconfiguration
during DCCC.
l Run the SET URRCTRLSWITCH command and select
RB_RECFG_RL_REEST_SWITCH(RB_RECFG_RL_REEST_SWITCH) under
Optimization Switch.
l Run the SET USTATETIMER command to set Wait RB reconfiguration response
timer.
Step 10 Enable the switch that controls the call reestablishment function triggered by RB release.
Step 11 Enable the switch that controls the call reestablishment function under different RNCs.
Step 12 Enable the switch that controls the call reestablishment function triggered by inter-RAT
handover.
Step 13 Enable the enhanced switch that controls whether call reestablishment can be triggered by
physical channel reconfiguration timeout.
Step 14 Enable the enhanced switch that controls whether call reestablishment can be triggered by radio
bearer reconfiguration timeout during the DCCC procedure.
Step 15 Enable the enhanced switch that controls whether call reestablishment can be triggered by the
timeout of radio bearer reconfiguration timeout in during procedures other than DCCC.
Step 16 Enable the switch that controls whether call reestablishment can be triggered by security mode
setup timeout.
NOTE
Set the security mode response timer on the CN side to a value greater than the security mode timer
(RRCSECRTMODECMPTMR(BSC6900,BSC6910)) plus the timer T314(BSC6900,BSC6910) on the
RNC side.
Step 17 Run the SET URRCTRLSWITCH command and select RL_RESTORE_SWITCH under
Optimization Switch.
Step 18 (Optional) Enable the D2P reconfiguration and reestablishment algorithm. It is recommended
that you consult Huawei engineers before enabling the algorithm.
1. Run the RNC MML command SET UALGORSVPARA with
RESERVED_SWITCH_10_BIT19 (D2P reconfiguration and reestablishment switch)
under Reserved Switch 10 set to 1 and bits 24 to 31 (timer for RL recovery before D2P
reconfiguration and reestablishment in the single RL scenario) under Reserved U32
Parameter 4 set to proper values.
2. Run the RNC MML command SET UALGORSVPARA with
RESERVED_SWITCH_5_BIT13 under Reserved Switch 5 cleared.
3. Run the RNC MML command SET URRCTRLSWITCH with
F2P_DATATRANS_OPTIMIZE_SWITCH under Process Control Switch 4 selected.
----End
NOTE
The value of RsvU32Para4 is calculated based on the site configuration. For
example: The original value of RsvdPara4 is set to 8388608 (1000 0000 0000 0000
0000 0000 0000 0000) and it is changed to 192937984 (1011 0110 0000 0000 0000
0000) by setting bit 24 to bit 31 to 11.
When configuring the DPCH Maximum Power Restriction feature on the CME, perform a single
configuration first, and then perform a batch modification if required. Configure the parameters of a single
object before a batch modification. Perform a batch modification before logging out of the parameter setting
interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 10-2. For instructions on how to perform the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
----End
Num of NoutsyncIn
Continuous d
Out of Sync (BSC6900,
Ind BSC6910)
Process PROCESSS
Control WITCH4
Switch 4 (BSC6900,
BSC6910)
Improvemen Improvemen
t Switch tSwitch
(BSC6900,
BSC6910)
HO PhyCh HoPhychRe
reconfigurati cfgTmr
on timer (BSC6900,
NOTE BSC6910)
Set this
parameter if
PROCESSS
WITCH4
(BSC6900,
BSC6910):
PHY_RECF
G_REEST_
SWITCH is
enabled.
Wait RB RbRecfgRsp
reconfigurati Tmr
on response (BSC6900,
timer BSC6910)
NOTE
Set this
parameter if
Optimizatio
nSwitch
(BSC6900,
BSC6910):
RB_RECFG
_RL_REES
T_SWITCH
is enabled.
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
function is enabled on the live network.
After the call reestablishment function is enabled, the values of the IRATHO.AttOutCS
(BSC6900,BSC6910) and IRATHO.AttOutPSUTRAN(BSC6900,BSC6910) counters
increase.
10.4.5 Deactivation
Step 2 Disable the switches that control the call reestablishment function triggered by RL out-of-
synchronization problems and SRB resets.
Step 3 Disable the switches that control the call reestablishment function triggered by active set update.
Step 4 Disable the switch that control the call reestablishment function triggered by measurement
control.
Step 5 Disable the switch that control the call reestablishment function triggered by TRB resets.
Step 6 Disable the switch that controls the call reestablishment function triggered by physical channel
reconfiguration.
Step 7 Disable the switch that controls the call reestablishment function triggered by RB setup.
Step 8 Disable the switch that controls the call reestablishment function triggered by RB
reconfiguration.
Step 9 Disable the switch that controls the call reestablishment function triggered by RB release.
Step 10 Disable the switch that controls the call reestablishment function under different RNCs.
Step 11 Disable the switch that controls the call reestablishment function triggered by inter-RAT
handover.
Step 12 Disable the enhanced switch that controls whether call reestablishment can be triggered by
physical channel reconfiguration timeout.
Step 13 Disable the enhanced switch that controls whether call reestablishment can be triggered by radio
bearer reconfiguration timeout during the DCCC procedure.
Step 14 Disable the enhanced switch that controls whether call reestablishment can be triggered by radio
bearer reconfiguration timeout during procedures other than DCCC.
Step 15 Disable the switch that controls whether call reestablishment can be triggered by security mode
setup timeout.
Step 17 Set the following parameters to the values they were before the function was enabled:
l 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.
l 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.
l Run the SET USTATETIMER command to reset Timer for Wait for Cell Update Specific
to CS UE and Timer for Wait for Cell Update Specific to PS UE to their original values.
l Run the SET USTATETIMER to reset the following parameters to their original values:
HO active set update response timer, HO PhyCh reconfiguration timer, and Wait RB
reconfiguration response timer.
----End
NOTE
When you deactivate the call reestablishment function, change the values of the following parameters back
to their settings before this function was activated: T302(BSC6900,BSC6910), N302
(BSC6900,BSC6910), T313(BSC6900,BSC6910), N313(BSC6900,BSC6910), N315
(BSC6900,BSC6910), T314(BSC6900,BSC6910)(CS), T315(BSC6900,BSC6910)(PS), NInsyncInd
(BSC6900,BSC6910), NoutsyncInd(BSC6900,BSC6910), TRlFailure(BSC6900,BSC6910),
RbRecfgRspTmr(BSC6900,BSC6910), HoAsuTmr(BSC6900,BSC6910) and HoPhychRecfgTmr
(BSC6900,BSC6910). Otherwise, network performance will be greatly affected.
When configuring the DPCH Maximum Power Restriction feature on the CME, perform a single
configuration first, and then perform a batch modification if required. Configure the parameters of a single
object before a batch modification. Perform a batch modification before logging out of the parameter setting
interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 10-3. For instructions on how to perform the CME single configuration, see
CME Single Configuration Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
----End
NOTE
When you deactivate the call reestablishment function, change the values of the following parameters back
to their settings before this function was activated: T302(BSC6900,BSC6910), N302
(BSC6900,BSC6910), T313(BSC6900,BSC6910), N313(BSC6900,BSC6910), N315
(BSC6900,BSC6910), T314(BSC6900,BSC6910)(CS), T315(BSC6900,BSC6910)(PS), NInsyncInd
(BSC6900,BSC6910), NoutsyncInd(BSC6900,BSC6910), TRlFailure(BSC6900,BSC6910),
RbRecfgRspTmr(BSC6900,BSC6910), HoAsuTmr(BSC6900,BSC6910) and HoPhychRecfgTmr
(BSC6900,BSC6910). Otherwise, network performance will be greatly affected.
4 USTAT RNC Timer for Wait for Cell Update CSRLReEstC Yes
ETIME Specific to CS UE ellUpdateTm
R r
(BSC6900,
BSC6910)
l Values of the following counters, which measure the number of CS RABs abnormally
released due to RF reasons, will decrease:
– VS.RAB.AbnormRel.CS.RF(BSC6900,BSC6910)
– VS.RAB.AbnormRel.CS.RF.ULSync(BSC6900,BSC6910)
– VS.RAB.AbnormRel.CS.RF.SRBReset(BSC6900,BSC6910)
l Values of the following counters, which measure the number of CS RAB establishment
failures due to RF reasons, will decrease:
– VS.RAB.FailEstabCS.RNL(BSC6900,BSC6910)
– VS.RAB.FailEstabCS.IubFail(BSC6900,BSC6910)
– VS.RAB.FailEstabCS.UuFail(BSC6900,BSC6910)
– VS.RAB.FailEstabCS.SRBReset(BSC6900,BSC6910)
– VS.RAB.FailEstabCS.CellUpd(BSC6900,BSC6910)
– VS.RAB.FailEstabCS.UuNoReply(BSC6900,BSC6910)
After the call reestablishment function 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 function is enabled, the values of the IRATHO.AttOutCS
(BSC6900,BSC6910) and IRATHO.AttOutPSUTRAN(BSC6900,BSC6910) counters
should increase.
PS Services
After the call reestablishment function is enabled for PS services, observe the following KPIs:
– VS.RAB.FailEstabPS.IubFail(BSC6900,BSC6910)
– VS.RAB.FailEstabPS.UuFail(BSC6900,BSC6910)
– VS.RAB.FailEstabPS.SRBReset(BSC6900,BSC6910)
– VS.RAB.FailEstabPS.CellUpd(BSC6900,BSC6910)
– VS.RAB.FailEstabPS.UuNoReply(BSC6900,BSC6910)
After the call reestablishment function 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 function is enabled, the values of the IRATHO.AttOutCS
(BSC6900,BSC6910) and IRATHO.AttOutPSUTRAN(BSC6900,BSC6910) counters
should increase.
10.7 Troubleshooting
None
11 Parameters
RESERVED_SWITCH_10_BIT21,
RESERVED_SWITCH_10_BIT22,
RESERVED_SWITCH_10_BIT23,
RESERVED_SWITCH_10_BIT24,
RESERVED_SWITCH_10_BIT25,
RESERVED_SWITCH_10_BIT26,
RESERVED_SWITCH_10_BIT27,
RESERVED_SWITCH_10_BIT28,
RESERVED_SWITCH_10_BIT29,
RESERVED_SWITCH_10_BIT30,
RESERVED_SWITCH_10_BIT31,
RESERVED_SWITCH_10_BIT32
Unit: None
Actual Value Range:
RESERVED_SWITCH_10_BIT1,
RESERVED_SWITCH_10_BIT2,
RESERVED_SWITCH_10_BIT3,
RESERVED_SWITCH_10_BIT4,
RESERVED_SWITCH_10_BIT5,
RESERVED_SWITCH_10_BIT6,
RESERVED_SWITCH_10_BIT7,
RESERVED_SWITCH_10_BIT8,
RESERVED_SWITCH_10_BIT9,
RESERVED_SWITCH_10_BIT10,
RESERVED_SWITCH_10_BIT11,
RESERVED_SWITCH_10_BIT12,
RESERVED_SWITCH_10_BIT13,
RESERVED_SWITCH_10_BIT14,
RESERVED_SWITCH_10_BIT15,
RESERVED_SWITCH_10_BIT16,
RESERVED_SWITCH_10_BIT17,
RESERVED_SWITCH_10_BIT18,
RESERVED_SWITCH_10_BIT19,
RESERVED_SWITCH_10_BIT20,
RESERVED_SWITCH_10_BIT21,
RESERVED_SWITCH_10_BIT22,
RESERVED_SWITCH_10_BIT23,
RESERVED_SWITCH_10_BIT24,
RESERVED_SWITCH_10_BIT25,
RESERVED_SWITCH_10_BIT26,
RESERVED_SWITCH_10_BIT27,
RESERVED_SWITCH_10_BIT28,
RESERVED_SWITCH_10_BIT29,
RESERVED_SWITCH_10_BIT30,
RESERVED_SWITCH_10_BIT31,
RESERVED_SWITCH_10_BIT32
Default Value:
RESERVED_SWITCH_10_BIT1-0&RESERVED_S
WITCH_10_BIT2-0&RESERVED_SWITCH_10_BI
T3-0&RESERVED_SWITCH_10_BIT4-0&RESERV
ED_SWITCH_10_BIT5-0&RESERVED_SWITCH_1
0_BIT6-0&RESERVED_SWITCH_10_BIT7-0&RES
ERVED_SWITCH_10_BIT8-0&RESERVED_SWIT
CH_10_BIT9-0&RESERVED_SWITCH_10_BIT10-
0&RESERVED_SWITCH_10_BIT11-0&RESERVE
D_SWITCH_10_BIT12-0&RESERVED_SWITCH_1
0_BIT13-0&RESERVED_SWITCH_10_BIT14-0&R
ESERVED_SWITCH_10_BIT15-0&RESERVED_S
WITCH_10_BIT16-0&RESERVED_SWITCH_10_B
IT17-0&RESERVED_SWITCH_10_BIT18-0&RESE
RVED_SWITCH_10_BIT19-0&RESERVED_SWIT
CH_10_BIT20-0&RESERVED_SWITCH_10_BIT21
-0&RESERVED_SWITCH_10_BIT22-0&RESERVE
D_SWITCH_10_BIT23-0&RESERVED_SWITCH_1
0_BIT24-0&RESERVED_SWITCH_10_BIT25-0&R
ESERVED_SWITCH_10_BIT26-0&RESERVED_S
WITCH_10_BIT27-0&RESERVED_SWITCH_10_B
IT28-0&RESERVED_SWITCH_10_BIT29-0&RESE
RVED_SWITCH_10_BIT30-0&RESERVED_SWIT
CH_10_BIT31-0&RESERVED_SWITCH_10_BIT32
-0
RESERVED_SWITCH_10_BIT3,
RESERVED_SWITCH_10_BIT4,
RESERVED_SWITCH_10_BIT5,
RESERVED_SWITCH_10_BIT6,
RESERVED_SWITCH_10_BIT7,
RESERVED_SWITCH_10_BIT8,
RESERVED_SWITCH_10_BIT9,
RESERVED_SWITCH_10_BIT10,
RESERVED_SWITCH_10_BIT11,
RESERVED_SWITCH_10_BIT12,
RESERVED_SWITCH_10_BIT13,
RESERVED_SWITCH_10_BIT14,
RESERVED_SWITCH_10_BIT15,
RESERVED_SWITCH_10_BIT16,
RESERVED_SWITCH_10_BIT17,
RESERVED_SWITCH_10_BIT18,
RESERVED_SWITCH_10_BIT19,
RESERVED_SWITCH_10_BIT20,
RESERVED_SWITCH_10_BIT21,
RESERVED_SWITCH_10_BIT22,
RESERVED_SWITCH_10_BIT23,
RESERVED_SWITCH_10_BIT24,
RESERVED_SWITCH_10_BIT25,
RESERVED_SWITCH_10_BIT26,
RESERVED_SWITCH_10_BIT27,
RESERVED_SWITCH_10_BIT28,
RESERVED_SWITCH_10_BIT29,
RESERVED_SWITCH_10_BIT30,
RESERVED_SWITCH_10_BIT31,
RESERVED_SWITCH_10_BIT32
Default Value:
RESERVED_SWITCH_10_BIT1-0&RESERVED_S
WITCH_10_BIT2-0&RESERVED_SWITCH_10_BI
T3-0&RESERVED_SWITCH_10_BIT4-0&RESERV
ED_SWITCH_10_BIT5-0&RESERVED_SWITCH_1
0_BIT6-0&RESERVED_SWITCH_10_BIT7-0&RES
ERVED_SWITCH_10_BIT8-0&RESERVED_SWIT
CH_10_BIT9-0&RESERVED_SWITCH_10_BIT10-
0&RESERVED_SWITCH_10_BIT11-0&RESERVE
D_SWITCH_10_BIT12-0&RESERVED_SWITCH_1
0_BIT13-0&RESERVED_SWITCH_10_BIT14-0&R
ESERVED_SWITCH_10_BIT15-0&RESERVED_S
WITCH_10_BIT16-0&RESERVED_SWITCH_10_B
IT17-0&RESERVED_SWITCH_10_BIT18-0&RESE
RVED_SWITCH_10_BIT19-0&RESERVED_SWIT
CH_10_BIT20-0&RESERVED_SWITCH_10_BIT21
-0&RESERVED_SWITCH_10_BIT22-0&RESERVE
D_SWITCH_10_BIT23-0&RESERVED_SWITCH_1
0_BIT24-0&RESERVED_SWITCH_10_BIT25-0&R
ESERVED_SWITCH_10_BIT26-0&RESERVED_S
WITCH_10_BIT27-0&RESERVED_SWITCH_10_B
IT28-0&RESERVED_SWITCH_10_BIT29-0&RESE
RVED_SWITCH_10_BIT30-0&RESERVED_SWIT
CH_10_BIT31-0&RESERVED_SWITCH_10_BIT32
-0
When this switch is turned off, the RNC does not delete
the existing Iur radio links during the RNC performing
radio link reestablishment.
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 RNC is waiting
for a UE's response during a radio bearer (RB) setup
CELL_DCH-to-CELL_DCH (D2D) procedure:
The RNC reestablishes a radio link (RL) for the UE if
the RNC 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 RNC, the switch
CELLUPT_RLFAILURE_SRBREESTAB_SWITCH
under "PROCESSSWITCH2" in the "SET
URRCTRLSWITCH" command should be turned on.
The RNC performs a cell update if the RNC 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 RNC is waiting
for a UE's response during an RB setup D2D procedure,
the RNC does not perform an RL reestablishment or cell
update even if the trigger conditions are met.
8)
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITC
H (The CELL_FACH-to-CELL_DCH state (F2D)
transition switch by TRB reset)
When the RNC receives a TRB reset request from a UE
in the CELL_FACH state, the RNC cannot respond to
the UE with a confirm message if the FACH is
congested. The
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITC
H parameter specifies whether a UE performs an F2D
transition if the number of TRB reset requests from the
UE to the RNC 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 off, 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 RNC not responding to the TRB reset
requests during FACH congestion.
When this switch is turned on, the RNC 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 RNC 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.
13) PS_HHO_ASYNC_CTRL_SWITCH
(Asynchronous Reconfigure Switch for PS HHO)
When this switch is turned on, the RNC does not put the
activation time information element (IE) in the hard
handover configuration message for PS services. After
receiving the message, the UE immediately activates the
configuration.
When this switch is turned off, the RNC puts the
activation time IE in the hard handover configuration
message for PS services. After receiving the message,
the UE activates the configuration at the specified
activation time.
14) IUR_HHO_ASYNC_CTRL_SWITCH
(Asynchronous Reconfigure Switch for Iur HHO)
When this switch is turned on, the RNC does not put the
activation time information element (IE) in the hard
handover configuration message across the Iur
interface. After receiving the message, the UE
immediately activates the configuration.
When this switch is turned off, the RNC puts the
activation time IE in the hard handover configuration
message across the Iur interface. After receiving the
message, the UE activates the configuration at the
specified activation time.
15) 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 RNC preferentially
allocates DPUe resources in any subrack to UEs that
comply with 3GPP Release 8 or later.
When this switch is turned off, the RNC preferentially
allocates DPU resources in the subrack that the UEs
access to UEs that comply with 3GPP Release 8 or later.
The RNC allocates DPU resources in other subracks
PHYCHRECFG_ENH_RL_REEST_SWITCH,
RBRECFG_ENH_RL_REEST_SWITCH,
SMC_STOP_RLC_SWITCH,
GTP_SN_IN_RAB_REL_INIT_BY_UTRAN_SWIT
CH, CMP_IU_QOS_GTP_PDU_SN_SWITCH,
DL_TRB_RESET_BUFF_SWITCH,
RRC_CELLFACH_DL_TRB_RESET_TO_F2D_SW
ITCH,
RAB_ASS_MOD_TNL_ADDR_SUP_SWITCH
Unit: None
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_SWITC
H, SEND_MSG_NULL_SWITCH,
FD_PCH_IUR_CS_OPT_SWITCH,
CELLUPT_T314_T315_TIMEOUT_OPT_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,
IRATHO_HOCANCEL_RL_REEST_SWITCH,
TRB_RESET_RL_REEST_SWITCH,
RB_REL_RL_REEST_SWITCH,
RB_SETUP_ENHANCE_RL_REEST_SWITCH,
RAB_SETUPMOD_CNT_FIX_SWITCH,
FAST_RETURN_LTE_BY_CELL_SELECT_SWIT
CH,
UL_DUAL_MODE_UE_D2P_OR_D2I_SWITCH,
PHYCHRECFG_ENH_RL_REEST_SWITCH,
RBRECFG_ENH_RL_REEST_SWITCH,
SMC_STOP_RLC_SWITCH,
GTP_SN_IN_RAB_REL_INIT_BY_UTRAN_SWIT
CH,
CMP_IU_QOS_GTP_PDU_SN_SWITCH,
DL_TRB_RESET_BUFF_SWITCH,
RRC_CELLFACH_DL_TRB_RESET_TO_F2D_SW
ITCH,
RAB_ASS_MOD_TNL_ADDR_SUP_SWITCH
Default Value:
PS_F2D_OVERLAP_CELLUPT_SWITCH-0&AMR
_HHO_FAIL_ROLLBACK_SWITCH-0&PHY_REC
FG_REEST_SWITCH-0&IUR_RL_REEST_SWITC
H-0&RB_SETUP_RL_REEST_SWITCH-0&RRC_C
ONN_SETUP_OPT_SWITCH-0&TCP_ACK_ACCE
LERATOR_SWITCH-0&RRC_CELLFACH_TRB_R
ESET_TO_F2D_SWITCH-0&SEND_MSG_NULL_
SWITCH-0&FD_PCH_IUR_CS_OPT_SWITCH-0&
CELLUPT_T314_T315_TIMEOUT_OPT_SWITCH-
0&CS_HHO_ASYNC_CTRL_SWITCH-0&PS_HHO
_ASYNC_CTRL_SWITCH-0&IUR_HHO_ASYNC_
CTRL_SWITCH-0&R8_UE_SEL_DPUE_SWITCH-
0&F2P_DATATRANS_OPTIMIZE_SWITCH-0&IR
ATHO_HOCANCEL_RL_REEST_SWITCH-0&TR
B_RESET_RL_REEST_SWITCH-0&RB_REL_RL_
REEST_SWITCH-0&RB_SETUP_ENHANCE_RL_
REEST_SWITCH-0&RAB_SETUPMOD_CNT_FIX
_SWITCH-0&FAST_RETURN_LTE_BY_CELL_SE
LECT_SWITCH-0&UL_DUAL_MODE_UE_D2P_O
R_D2I_SWITCH-0&PHYCHRECFG_ENH_RL_RE
EST_SWITCH-0&RBRECFG_ENH_RL_REEST_S
WITCH-0&SMC_STOP_RLC_SWITCH-1>P_S
N_IN_RAB_REL_INIT_BY_UTRAN_SWITCH-1&
CMP_IU_QOS_GTP_PDU_SN_SWITCH-0&DL_TR
B_RESET_BUFF_SWITCH-0&RRC_CELLFACH_
DL_TRB_RESET_TO_F2D_SWITCH-0&RAB_ASS
_MOD_TNL_ADDR_SUP_SWITCH-1
When this switch is turned off, the RNC does not delete
the existing Iur radio links during the RNC performing
radio link reestablishment.
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 RNC is waiting
for a UE's response during a radio bearer (RB) setup
CELL_DCH-to-CELL_DCH (D2D) procedure:
The RNC reestablishes a radio link (RL) for the UE if
the RNC 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 RNC, the switch
CELLUPT_RLFAILURE_SRBREESTAB_SWITCH
under "PROCESSSWITCH2" in the "SET
URRCTRLSWITCH" command should be turned on.
The RNC performs a cell update if the RNC 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 RNC is waiting
for a UE's response during an RB setup D2D procedure,
the RNC does not perform an RL reestablishment or cell
update even if the trigger conditions are met.
8)
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITC
H (The CELL_FACH-to-CELL_DCH state (F2D)
transition switch by TRB reset)
When the RNC receives a TRB reset request from a UE
in the CELL_FACH state, the RNC cannot respond to
the UE with a confirm message if the FACH is
congested. The
RRC_CELLFACH_TRB_RESET_TO_F2D_SWITC
H parameter specifies whether a UE performs an F2D
transition if the number of TRB reset requests from the
UE to the RNC 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 off, 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 RNC not responding to the TRB reset
requests during FACH congestion.
When this switch is turned on, the RNC 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 RNC 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.
13) PS_HHO_ASYNC_CTRL_SWITCH
(Asynchronous Reconfigure Switch for PS HHO)
When this switch is turned on, the RNC does not put the
activation time information element (IE) in the hard
handover configuration message for PS services. After
receiving the message, the UE immediately activates the
configuration.
When this switch is turned off, the RNC puts the
activation time IE in the hard handover configuration
message for PS services. After receiving the message,
the UE activates the configuration at the specified
activation time.
14) IUR_HHO_ASYNC_CTRL_SWITCH
(Asynchronous Reconfigure Switch for Iur HHO)
When this switch is turned on, the RNC does not put the
activation time information element (IE) in the hard
handover configuration message across the Iur
interface. After receiving the message, the UE
immediately activates the configuration.
When this switch is turned off, the RNC puts the
activation time IE in the hard handover configuration
message across the Iur interface. After receiving the
message, the UE activates the configuration at the
specified activation time.
15) F2P_DATATRANS_OPTIMIZE_SWITCH
(Switch for Optimized Data Transmission before a State
Transition from CELL_FACH to CELL_PCH or
URA_PCH)
Whether the RNC 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
when the
PHYCHRECFG_ENH_RL_REEST_SWITCH check
box under the "PROCESSSWITCH4" parameter in the
"SET URRCTRLSWITCH" command is selected.
24)RBRECFG_ENH_RL_REEST_SWITCH
Whether to preferentially process a CELL UPDATE
message when RB reconfiguration is in progress. The
RNC receives a CELL UPDATE message from a UE
with a cause value of "radio link failure", "RLC
unrecoverable error", or "re-entering service area" when
expecting a response from the UE to the RB
reconfiguration process. In this scenario, the RNC
preferentially processes the CELL UPDATE message
if the switch is turned on.
When this switch is turned off, the RNC does not
preferentially process the CELL UPDATE message in
the preceding scenario. This parameter takes effect only
when the RB_RECFG_RL_REEST_SWITCH check
box under the "OptimizationSwitch" parameter in the
"SET URRCTRLSWITCH" command is selected.
25)SMC_STOP_RLC_SWITCH
Whether to stop RLC entities (except RLC entities used
by SRB2) for security-mode-enabled UEs whose user
signaling (except cell-related signaling) is processed by
their overflow RNCs due to load sharing and that are in
the security mode.
When this switch is turned on, the RNC stops RLC
entities (except RLC entities used by SRB2) for such
UEs. This prevents call drops that are caused by the
ciphering activation time inconsistency between the
UEs and RNC.
When this switch is turned off, the RNC suspends RLC
entities (except RLC entities used by SRB2) for such
UEs.
26)
GTP_SN_IN_RAB_REL_INIT_BY_UTRAN_SWIT
CH
Whether the RAB RELEASE REQUEST or IU
RELEASE COMPLETE message carries the IE GTP
PDU SN during the release procedure initiated by the
UTRAN of the PS domain.
When this switch is turned on, the RAB RELEASE
REQUEST or IU RELEASE COMPLETE message
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_SWITC
H, SEND_MSG_NULL_SWITCH,
FD_PCH_IUR_CS_OPT_SWITCH,
CELLUPT_T314_T315_TIMEOUT_OPT_SWITCH,
CS_HHO_ASYNC_CTRL_SWITCH,
PS_HHO_ASYNC_CTRL_SWITCH,
IUR_HHO_ASYNC_CTRL_SWITCH,
F2P_DATATRANS_OPTIMIZE_SWITCH,
IRATHO_HOCANCEL_RL_REEST_SWITCH,
TRB_RESET_RL_REEST_SWITCH,
RB_REL_RL_REEST_SWITCH,
RB_SETUP_ENHANCE_RL_REEST_SWITCH,
RAB_SETUPMOD_CNT_FIX_SWITCH,
FAST_RETURN_LTE_BY_CELL_SELECT_SWIT
CH,
UL_DUAL_MODE_UE_D2P_OR_D2I_SWITCH,
PHYCHRECFG_ENH_RL_REEST_SWITCH,
RBRECFG_ENH_RL_REEST_SWITCH,
SMC_STOP_RLC_SWITCH,
GTP_SN_IN_RAB_REL_INIT_BY_UTRAN_SWIT
CH,
CMP_IU_QOS_GTP_PDU_SN_SWITCH,
DL_TRB_RESET_BUFF_SWITCH,
RRC_CELLFACH_DL_TRB_RESET_TO_F2D_SW
ITCH,
RAB_ASS_MOD_TNL_ADDR_SUP_SWITCH
Default Value:
PS_F2D_OVERLAP_CELLUPT_SWITCH-0&AMR
_HHO_FAIL_ROLLBACK_SWITCH-0&PHY_REC
FG_REEST_SWITCH-0&IUR_RL_REEST_SWITC
H-0&RB_SETUP_RL_REEST_SWITCH-0&RRC_C
ONN_SETUP_OPT_SWITCH-0&TCP_ACK_ACCE
LERATOR_SWITCH-0&RRC_CELLFACH_TRB_R
ESET_TO_F2D_SWITCH-0&SEND_MSG_NULL_
SWITCH-0&FD_PCH_IUR_CS_OPT_SWITCH-0&
CELLUPT_T314_T315_TIMEOUT_OPT_SWITCH-
0&CS_HHO_ASYNC_CTRL_SWITCH-0&PS_HHO
_ASYNC_CTRL_SWITCH-0&IUR_HHO_ASYNC_
CTRL_SWITCH-0&F2P_DATATRANS_OPTIMIZE
12)TAKE_ACTIVE_TIME_DRD_SWITCH
Whether to refuse to include an activation time to a
RADIO BEARER SETUP message when the DRD
process is in progress.
When this switch is turned on, an activation time is not
included to a RADIO BEARER SETUP message if the
DRD process is in progress.
When this switch is turned off, an activation time is
included to a RADIO BEARER SETUP message if the
DRD process is in progress.
13)CS_DISCONNECT_OPT_SWITCH
Whether the RNC performs optimized processing if the
UE does not respond within 3 seconds after receiving a
DIRECT TRANSFER message from the CN during a
CS call release. The value of the IE Message Type in
the DIRECT TRANSFER message is Disconnect.
When this switch is turned on, the RNC creates a
DIRECT TRANSFER message and sends it to the CN.
The value of the IE Message Type in the DIRECT
TRANSFER message is Release.
When this switch is turned off, the RNC does not create
the DIRECT TRANSFER message.
14)NON_DCCC_RBRECFG_RL_REEST_SWITCH
1: This switch is turned on. The RNC reestablishes an
RL for a UE when both of the following conditions are
met:
- The RNC is waiting for the UE's response in an RB
reconfiguration procedure in cases other than DCCC.
- The RNC detects a timeout or SRB reset or the NodeB
reports that all RLs for the UE are out of
synchronization.
If the RNC receives a CELL UPDATE message with
the cause value "RL FAILURE" or "RLC
UNRECOVERABLE ERROR" while waiting for the
UE's response, the RNC performs a cell update.
0: This switch is turned off. The RNC does not
reestablish an RL for the UE in the preceding scenario.
15)SMC_RL_REEST_SWITCH
1: This switch is turned on. When the RNC is waiting
for a UE's response in the security mode procedure, the
RL for the UE is reestablished if the RNC detects a
timeout or SRB reset or if the NodeB reports that all RLs
for the UE are out of synchronization.
12)TAKE_ACTIVE_TIME_DRD_SWITCH
Whether to refuse to include an activation time to a
RADIO BEARER SETUP message when the DRD
process is in progress.
When this switch is turned on, an activation time is not
included to a RADIO BEARER SETUP message if the
DRD process is in progress.
When this switch is turned off, an activation time is
included to a RADIO BEARER SETUP message if the
DRD process is in progress.
13)CS_DISCONNECT_OPT_SWITCH
Whether the RNC performs optimized processing if the
UE does not respond within 3 seconds after receiving a
DIRECT TRANSFER message from the CN during a
CS call release. The value of the IE Message Type in
the DIRECT TRANSFER message is Disconnect.
When this switch is turned on, the RNC creates a
DIRECT TRANSFER message and sends it to the CN.
The value of the IE Message Type in the DIRECT
TRANSFER message is Release.
When this switch is turned off, the RNC does not create
the DIRECT TRANSFER message.
14)NON_DCCC_RBRECFG_RL_REEST_SWITCH
1: This switch is turned on. The RNC reestablishes an
RL for a UE when both of the following conditions are
met:
- The RNC is waiting for the UE's response in an RB
reconfiguration procedure in cases other than DCCC.
- The RNC detects a timeout or SRB reset or the NodeB
reports that all RLs for the UE are out of
synchronization.
If the RNC receives a CELL UPDATE message with
the cause value "RL FAILURE" or "RLC
UNRECOVERABLE ERROR" while waiting for the
UE's response, the RNC performs a cell update.
0: This switch is turned off. The RNC does not
reestablish an RL for the UE in the preceding scenario.
15)SMC_RL_REEST_SWITCH
1: This switch is turned on. When the RNC is waiting
for a UE's response in the security mode procedure, the
RL for the UE is reestablished if the RNC detects a
timeout or SRB reset or if the NodeB reports that all RLs
for the UE are out of synchronization.
RbRelR BSC690 SET WRFD- 3GPP Meaning: A timer to RNC wait for the RB release
spTmr 0 USTAT 010101 R9 response from UE in the RB procedure. Refer to the
ETIME Specific Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
RbRelR BSC691 SET WRFD- 3GPP Meaning: A timer to RNC wait for the RB release
spTmr 0 USTAT 010101 R9 response from UE in the RB procedure. Refer to the
ETIME Specific Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
One CS 4)
Service FD_PCH_REENTERSA_FORCE_RRC_REL_SWIT
and CH.
Three Whether to enable the RNC to release the RRC
PS connection of an EFD-capable UE that received an
Services SCRI message from the PS domain of the CN if the UE
Paging sends the RNC a CELL UPDATE message after
UE in reentering a service area. When this switch is turned on,
Idle, the RNC releases the RRC connection of such a UE in
CELL_P the preceding scenario. This solves the problem that a
CH, network becomes inaccessible when such a UE reenters
URA_P a service area.
CH State 1: This switch is turned on. The RNC directly releases
(Type 1) the RRC connection after receiving the CELL UPDATE
Rate message from the Enhanced Fast Dormancy-capable
Negotiat that leaves and then reenters the service area.
ion at 0: This switch is turned off. The RNC processes the
Admissi CELL UPDATE message received from the Enhanced
on Fast Dormancy-capable UE that leaves and then
Control reenters the service area.
5)UE_CRC_COMPATIBLE_SWITCH.
Whether the RNC normally releases connections when
it detects failed cyclic redundancy check (CRC) on RB
SETUP COMPLETE or RB RECONFIGURATION
COMPLETE messages received from HSDPA UEs.
1: This switch is turned on. The RNC normally releases
the connections when it detects the failed CRC.
0: This switch is turned off. The RNC abnormally
releases the connections when it detects the failed CRC.
6)RNC_P2D_DRD_SWITCH.
Whether the RNC performs the directed retry decision
(DRD) when it receives a CELL UPDATE message
with the cause value "uplink data transmission" or "
paging response" during UEs' state transition from
CELL_PCH or URA_PCH to CELL_DCH.
1: This switch is turned on. The RNC performs the DRD
in the preceding scenario.
0: This switch is turned off. The RNC does not perform
the DRD in the preceding scenario.
7)P2D_SWITCH
Whether to transit a UE from the CELL_PCH or
URA_PCH state to the CELL_DCH state when the
following conditions are met: the UE sends the RNC a
11)CS_RL_SETUP_SWITCH
Whether the RNC reestablishes a radio link (RL) when
SRBs of a CS service reset or all its RLs are out of
synchronization.
1: This switch is turned on. The RNC reestablishes an
RL in the preceding scenario.
0: This switch is turned off. The RNC does not
reestablish an RL in the preceding scenario.
12)PS_RL_SETUP_SWITCH
1: This switch is turned on. PS services can trigger active
link re-establishment.
0: This switch is turned off. PS services cannot trigger
active link re-establishment.
13)UE_SRB_RESET_SWITCH
Whether the RNC reestablishes a radio link (RL) when
it receives a CELL UPDATE message carrying SRB
reset information.
1: This switch is turned on. The RNC does not release
the RRC connection and it reestablishes an RL.
0: This switch is turned off. The RNC releases the RRC
connection.
14)RL_RESTORE_SWITCH
Switch for the radio link restoration timer
1: This switch is turned on. If there are CS services and
the last radio link fails, the RNC waits for the radio link
to restore before the timer T313 expires.
0: This switch is turned off. If there are CS services and
the last radio link fails, the RNC waits for the radio link
to restore before the original timer expires.
15)RNC_EFD_D2F_SWITCH
Whether to enable RNC-level UE state transition from
CELL_DCH to CELL_FACH (D2F) for fast dormancy-
capable UEs.
1: This switch is turned on. The D2F state transition is
enabled for the fast dormancy-capable UEs..
0: This switch is turned off. The state transition from
CELL_DCH to CELL_PCH (D2P) is enabled for the
fast dormancy-capable UEs
16)RNC_RB_SCRI_NOT_DROP_SWITCH
Whether the RB release due to SCRI during RB
reconfiguration is calculated as a call drop
(F2D_NO_RSP_RRCREL_SWITCH),
CS_SETUP_P2D_SWITCH
(CS_SETUP_P2D_SWITCH),
SYSHO_CIPHER_IE_SWITCH
(SYSHO_CIPHER_IE_SWITCH),
P2P_GTPU_NOT_CFG_SWITCH
(P2P_GTPU_NOT_CFG_SWITCH),
RB_SETUP_CIPHER_TIME_ADJ_SWITCH
(RB_SETUP_CIPHER_TIME_ADJ_SWITCH),
CS_PRI_MOD_NOT_INT_SWITCH
(CS_PRI_MOD_NOT_INT_SWITCH),
RAB_SETUP_TMSI_REALLOC_BUF_SWITCH
(RAB_SETUP_TMSI_REALLOC_BUF_SWITCH),
IU_FAULT_REL_PS_RES_SWITCH
(IU_FAULT_REL_PS_RES_SWITCH),
RB_RECFG_RL_REEST_SWITCH
(RB_RECFG_RL_REEST_SWITCH),
F2P_DT_MSG_BUFFER_SWITCH
(F2P_DT_MSG_BUFFER_SWITCH),
SCRI_COMPATIBLE_SWITCH
(SCRI_COMPATIBLE_SWITCH),
GTPU_ERR_IND_DEF_SWITCH
(GTPU_ERR_IND_DEF_SWITCH),
IUR_SRV_CELL_CHG_MACHS_RESET_SWITCH
(IUR_SRV_CELL_CHG_MACHS_RESET_SWITC
H)
Unit: None
Actual Value Range:
PAGGING_NUM_CTRL_SWITCH,
ASU_RL_RESET_SWITCH,
MC_RL_RESET_SWITCH,
FD_PCH_REENTERSA_FORCE_RRC_REL_SWIT
CH,
UE_CRC_COMPATIBLE_SWITCH,
RNC_P2D_DRD_SWITCH,
P2D_SWITCH,
AMR_F2D_OVERLAP_CELLUPT_SWITCH,
SRB_RESET_RL_SETUP_SWITCH,
RLFAIL_RL_SETUP_SWITCH,
CS_RL_SETUP_SWITCH,
PS_RL_SETUP_SWITCH,
UE_SRB_RESET_SWITCH,
RL_RESTORE_SWITCH,
RNC_EFD_D2F_SWITCH,
RNC_RB_SCRI_NOT_DROP_SWITCH,
RRC_RECONN_SWITCH,
RRC_REPEAT_PFM_SWITCH,
F2D_NO_RSP_RRCREL_SWITCH,
CS_SETUP_P2D_SWITCH,
SYSHO_CIPHER_IE_SWITCH,
P2P_GTPU_NOT_CFG_SWITCH,
RB_SETUP_CIPHER_TIME_ADJ_SWITCH,
CS_PRI_MOD_NOT_INT_SWITCH,
RAB_SETUP_TMSI_REALLOC_BUF_SWITCH,
IU_FAULT_REL_PS_RES_SWITCH,
RB_RECFG_RL_REEST_SWITCH,
F2P_DT_MSG_BUFFER_SWITCH,
SCRI_COMPATIBLE_SWITCH,
GTPU_ERR_IND_DEF_SWITCH,
IUR_SRV_CELL_CHG_MACHS_RESET_SWITCH
Default Value:
PAGGING_NUM_CTRL_SWITCH-0&ASU_RL_RE
SET_SWITCH-0&MC_RL_RESET_SWITCH-0&FD
_PCH_REENTERSA_FORCE_RRC_REL_SWITCH
-0&UE_CRC_COMPATIBLE_SWITCH-0&RNC_P2
D_DRD_SWITCH-0&P2D_SWITCH-0&AMR_F2D
_OVERLAP_CELLUPT_SWITCH-0&SRB_RESET_
RL_SETUP_SWITCH-0&RLFAIL_RL_SETUP_SW
ITCH-0&CS_RL_SETUP_SWITCH-0&PS_RL_SET
UP_SWITCH-0&UE_SRB_RESET_SWITCH-0&RL
_RESTORE_SWITCH-0&RNC_EFD_D2F_SWITC
H-1&RNC_RB_SCRI_NOT_DROP_SWITCH-0&R
RC_RECONN_SWITCH-0&RRC_REPEAT_PFM_S
WITCH-1&F2D_NO_RSP_RRCREL_SWITCH-0&C
S_SETUP_P2D_SWITCH-0&SYSHO_CIPHER_IE_
SWITCH-0&P2P_GTPU_NOT_CFG_SWITCH-1&R
B_SETUP_CIPHER_TIME_ADJ_SWITCH-1&CS_P
RI_MOD_NOT_INT_SWITCH-0&RAB_SETUP_T
MSI_REALLOC_BUF_SWITCH-0&IU_FAULT_RE
L_PS_RES_SWITCH-0&RB_RECFG_RL_REEST_
SWITCH-0&F2P_DT_MSG_BUFFER_SWITCH-0&
SCRI_COMPATIBLE_SWITCH-0>PU_ERR_IN
D_DEF_SWITCH-0&IUR_SRV_CELL_CHG_MAC
HS_RESET_SWITCH-1
One CS 4)
Service FD_PCH_REENTERSA_FORCE_RRC_REL_SWIT
and CH.
Three Whether to enable the RNC to release the RRC
PS connection of an EFD-capable UE that received an
Services SCRI message from the PS domain of the CN if the UE
Paging sends the RNC a CELL UPDATE message after
UE in reentering a service area. When this switch is turned on,
Idle, the RNC releases the RRC connection of such a UE in
CELL_P the preceding scenario. This solves the problem that a
CH, network becomes inaccessible when such a UE reenters
URA_P a service area.
CH State 1: This switch is turned on. The RNC directly releases
(Type 1) the RRC connection after receiving the CELL UPDATE
Rate message from the Enhanced Fast Dormancy-capable
Negotiat that leaves and then reenters the service area.
ion at 0: This switch is turned off. The RNC processes the
Admissi CELL UPDATE message received from the Enhanced
on Fast Dormancy-capable UE that leaves and then
Control reenters the service area.
5)UE_CRC_COMPATIBLE_SWITCH.
Whether the RNC normally releases connections when
it detects failed cyclic redundancy check (CRC) on RB
SETUP COMPLETE or RB RECONFIGURATION
COMPLETE messages received from HSDPA UEs.
1: This switch is turned on. The RNC normally releases
the connections when it detects the failed CRC.
0: This switch is turned off. The RNC abnormally
releases the connections when it detects the failed CRC.
6)RNC_P2D_DRD_SWITCH.
Whether the RNC performs the directed retry decision
(DRD) when it receives a CELL UPDATE message
with the cause value "uplink data transmission" or "
paging response" during UEs' state transition from
CELL_PCH or URA_PCH to CELL_DCH.
1: This switch is turned on. The RNC performs the DRD
in the preceding scenario.
0: This switch is turned off. The RNC does not perform
the DRD in the preceding scenario.
7)P2D_SWITCH
Whether to transit a UE from the CELL_PCH or
URA_PCH state to the CELL_DCH state when the
following conditions are met: the UE sends the RNC a
11)CS_RL_SETUP_SWITCH
Whether the RNC reestablishes a radio link (RL) when
SRBs of a CS service reset or all its RLs are out of
synchronization.
1: This switch is turned on. The RNC reestablishes an
RL in the preceding scenario.
0: This switch is turned off. The RNC does not
reestablish an RL in the preceding scenario.
12)PS_RL_SETUP_SWITCH
1: This switch is turned on. PS services can trigger active
link re-establishment.
0: This switch is turned off. PS services cannot trigger
active link re-establishment.
13)UE_SRB_RESET_SWITCH
Whether the RNC reestablishes a radio link (RL) when
it receives a CELL UPDATE message carrying SRB
reset information.
1: This switch is turned on. The RNC does not release
the RRC connection and it reestablishes an RL.
0: This switch is turned off. The RNC releases the RRC
connection.
14)RL_RESTORE_SWITCH
Switch for the radio link restoration timer
1: This switch is turned on. If there are CS services and
the last radio link fails, the RNC waits for the radio link
to restore before the timer T313 expires.
0: This switch is turned off. If there are CS services and
the last radio link fails, the RNC waits for the radio link
to restore before the original timer expires.
15)RNC_EFD_D2F_SWITCH
Whether to enable RNC-level UE state transition from
CELL_DCH to CELL_FACH (D2F) for fast dormancy-
capable UEs.
1: This switch is turned on. The D2F state transition is
enabled for the fast dormancy-capable UEs..
0: This switch is turned off. The state transition from
CELL_DCH to CELL_PCH (D2P) is enabled for the
fast dormancy-capable UEs
16)RNC_RB_SCRI_NOT_DROP_SWITCH
Whether the RB release due to SCRI during RB
reconfiguration is calculated as a call drop
(F2D_NO_RSP_RRCREL_SWITCH),
CS_SETUP_P2D_SWITCH
(CS_SETUP_P2D_SWITCH),
SYSHO_CIPHER_IE_SWITCH
(SYSHO_CIPHER_IE_SWITCH),
P2P_GTPU_NOT_CFG_SWITCH
(P2P_GTPU_NOT_CFG_SWITCH),
RB_SETUP_CIPHER_TIME_ADJ_SWITCH
(RB_SETUP_CIPHER_TIME_ADJ_SWITCH),
CS_PRI_MOD_NOT_INT_SWITCH
(CS_PRI_MOD_NOT_INT_SWITCH),
RAB_SETUP_TMSI_REALLOC_BUF_SWITCH
(RAB_SETUP_TMSI_REALLOC_BUF_SWITCH),
IU_FAULT_REL_PS_RES_SWITCH
(IU_FAULT_REL_PS_RES_SWITCH),
RB_RECFG_RL_REEST_SWITCH
(RB_RECFG_RL_REEST_SWITCH),
F2P_DT_MSG_BUFFER_SWITCH
(F2P_DT_MSG_BUFFER_SWITCH),
SCRI_COMPATIBLE_SWITCH
(SCRI_COMPATIBLE_SWITCH),
GTPU_ERR_IND_DEF_SWITCH
(GTPU_ERR_IND_DEF_SWITCH),
IUR_SRV_CELL_CHG_MACHS_RESET_SWITCH
(IUR_SRV_CELL_CHG_MACHS_RESET_SWITC
H)
Unit: None
Actual Value Range:
PAGGING_NUM_CTRL_SWITCH,
ASU_RL_RESET_SWITCH,
MC_RL_RESET_SWITCH,
FD_PCH_REENTERSA_FORCE_RRC_REL_SWIT
CH,
UE_CRC_COMPATIBLE_SWITCH,
RNC_P2D_DRD_SWITCH,
P2D_SWITCH,
AMR_F2D_OVERLAP_CELLUPT_SWITCH,
SRB_RESET_RL_SETUP_SWITCH,
RLFAIL_RL_SETUP_SWITCH,
CS_RL_SETUP_SWITCH,
PS_RL_SETUP_SWITCH,
UE_SRB_RESET_SWITCH,
RL_RESTORE_SWITCH,
RNC_EFD_D2F_SWITCH,
RNC_RB_SCRI_NOT_DROP_SWITCH,
RRC_RECONN_SWITCH,
RRC_REPEAT_PFM_SWITCH,
F2D_NO_RSP_RRCREL_SWITCH,
CS_SETUP_P2D_SWITCH,
SYSHO_CIPHER_IE_SWITCH,
P2P_GTPU_NOT_CFG_SWITCH,
RB_SETUP_CIPHER_TIME_ADJ_SWITCH,
CS_PRI_MOD_NOT_INT_SWITCH,
RAB_SETUP_TMSI_REALLOC_BUF_SWITCH,
IU_FAULT_REL_PS_RES_SWITCH,
RB_RECFG_RL_REEST_SWITCH,
F2P_DT_MSG_BUFFER_SWITCH,
SCRI_COMPATIBLE_SWITCH,
GTPU_ERR_IND_DEF_SWITCH,
IUR_SRV_CELL_CHG_MACHS_RESET_SWITCH
Default Value:
PAGGING_NUM_CTRL_SWITCH-0&ASU_RL_RE
SET_SWITCH-0&MC_RL_RESET_SWITCH-0&FD
_PCH_REENTERSA_FORCE_RRC_REL_SWITCH
-0&UE_CRC_COMPATIBLE_SWITCH-0&RNC_P2
D_DRD_SWITCH-0&P2D_SWITCH-0&AMR_F2D
_OVERLAP_CELLUPT_SWITCH-0&SRB_RESET_
RL_SETUP_SWITCH-0&RLFAIL_RL_SETUP_SW
ITCH-0&CS_RL_SETUP_SWITCH-0&PS_RL_SET
UP_SWITCH-0&UE_SRB_RESET_SWITCH-0&RL
_RESTORE_SWITCH-0&RNC_EFD_D2F_SWITC
H-1&RNC_RB_SCRI_NOT_DROP_SWITCH-0&R
RC_RECONN_SWITCH-0&RRC_REPEAT_PFM_S
WITCH-1&F2D_NO_RSP_RRCREL_SWITCH-0&C
S_SETUP_P2D_SWITCH-0&SYSHO_CIPHER_IE_
SWITCH-0&P2P_GTPU_NOT_CFG_SWITCH-1&R
B_SETUP_CIPHER_TIME_ADJ_SWITCH-1&CS_P
RI_MOD_NOT_INT_SWITCH-0&RAB_SETUP_T
MSI_REALLOC_BUF_SWITCH-0&IU_FAULT_RE
L_PS_RES_SWITCH-0&RB_RECFG_RL_REEST_
SWITCH-0&F2P_DT_MSG_BUFFER_SWITCH-0&
SCRI_COMPATIBLE_SWITCH-0>PU_ERR_IN
D_DEF_SWITCH-0&IUR_SRV_CELL_CHG_MAC
HS_RESET_SWITCH-1
IT14-0&RSVDBIT1_BIT15-0&RSVDBIT1_BIT16-0
&SYSHO_CSIN_PERMIT_SWITCH-1&RSVDBIT1
_BIT18-1&RSVDBIT1_BIT19-1&RSVDBIT1_BIT2
0-1&RSVDBIT1_BIT21-1&RSVDBIT1_BIT22-1&R
SVDBIT1_BIT23-1&RSVDBIT1_BIT24-1&RSVDB
IT1_BIT25-1&RSVDBIT1_BIT26-1&RSVDBIT1_B
IT27-1&RSVDBIT1_BIT28-1&RSVDBIT1_BIT29-1
&RSVDBIT1_BIT30-1&RSVDBIT1_BIT31-0&RSV
DBIT1_BIT32-1
&SYSHO_CSIN_PERMIT_SWITCH-1&RSVDBIT1
_BIT18-1&RSVDBIT1_BIT19-1&RSVDBIT1_BIT2
0-1&RSVDBIT1_BIT21-1&RSVDBIT1_BIT22-1&R
SVDBIT1_BIT23-1&RSVDBIT1_BIT24-1&RSVDB
IT1_BIT25-1&RSVDBIT1_BIT26-1&RSVDBIT1_B
IT27-1&RSVDBIT1_BIT28-1&RSVDBIT1_BIT29-1
&RSVDBIT1_BIT30-1&RSVDBIT1_BIT31-0&RSV
DBIT1_BIT32-1
NOutsy BSC691 ADD WRFD- Physical Meaning: Number of times of successive in-sync
ncInd 0 UCELL 022000 Channel indications required for starting the radio link failure
SETUP Manage timer. When the radio link set is in the synchronized
MOD ment state, the NodeB starts the timer after it receives
UCELL 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".
"TRlFailure" specifies the length of the timer. 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: 1~256
Unit: None
Actual Value Range: 1~256
Default Value: 50
NOutsy BSC690 ADD WRFD- Physical Meaning: Number of times of successive in-sync
ncInd 0 UCELL 022000 Channel indications required for starting the radio link failure
SETUP Manage timer. When the radio link set is in the synchronized
MOD ment state, the NodeB starts the timer after it receives
UCELL 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".
"TRlFailure" specifies the length of the timer. 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: 1~256
Unit: None
Actual Value Range: 1~256
Default Value: 50
TRlFail BSC690 ADD WRFD- Physical Meaning: Radio link failure timer duration. When the
ure 0 UCELL 022000 Channel radio link set is in the synchronized state, the NodeB
SETUP Manage starts the timer after it receives successive out-of-sync
MOD ment indications of the number defined by NOutsyncInd. The
UCELL 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
Unit: 0.1s
Actual Value Range: 0~25.5
Default Value: 50
TRlFail BSC691 ADD WRFD- Physical Meaning: Radio link failure timer duration. When the
ure 0 UCELL 022000 Channel radio link set is in the synchronized state, the NodeB
SETUP Manage starts the timer after it receives successive out-of-sync
MOD ment indications of the number defined by NOutsyncInd. The
UCELL 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
Unit: 0.1s
Actual Value Range: 0~25.5
Default Value: 50
NInsync BSC690 ADD WRFD- Physical Meaning: Number of times of successive in-sync
Ind 0 UCELL 022000 Channel indications required for the NodeB to trigger the radio
SETUP Manage link recovery process. The radio link set remains in the
MOD ment initial state until it has received a number (the number
UCELL 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.
GUI Value Range: 1~256
Unit: None
Actual Value Range: 1~256
Default Value: 5
NInsync BSC691 ADD WRFD- Physical Meaning: Number of times of successive in-sync
Ind 0 UCELL 022000 Channel indications required for the NodeB to trigger the radio
SETUP Manage link recovery process. The radio link set remains in the
MOD ment initial state until it has received a number (the number
UCELL 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.
GUI Value Range: 1~256
Unit: None
Actual Value Range: 1~256
Default Value: 5
T313 BSC690 SET WRFD- 3GPP Meaning: Timer 313. T313 starts when a UE detects
0 UCONN 010101 R9 N313 successive "out of sync" indications from Layer
MODET Specific 1 and stops when the UE detects N315 successive "in
IMER ations sync" indications form Layer 1. When T313 expires, the
radio link setup fails. The protocol-defined default value
is 3. The value of this parameter is contained in SIB1
messages.
GUI Value Range: 0~15
Unit: s
Actual Value Range: 0~15
Default Value: 3
T313 BSC691 SET WRFD- 3GPP Meaning: Timer 313. T313 starts when a UE detects
0 UCONN 010101 R9 N313 successive "out of sync" indications from Layer
MODET Specific 1 and stops when the UE detects N315 successive "in
IMER ations sync" indications form Layer 1. When T313 expires, the
radio link setup fails. The protocol-defined default value
is 3. The value of this parameter is contained in SIB1
messages.
GUI Value Range: 0~15
Unit: s
Actual Value Range: 0~15
Default Value: 3
N313 BSC690 SET WRFD- 3GPP Meaning: Maximum number of successive "out of sync"
0 UCONN 010101 R9 indications received from Layer 1. The protocol-defined
MODET Specific default value is 20. The value of this parameter is
IMER ations contained in SIB1 messages.
GUI Value Range: D1, D2, D4, D10, D20, D50, D100,
D200
Unit: None
Actual Value Range: 1, 2, 4, 10, 20, 50, 100, 200
Default Value: D50
N313 BSC691 SET WRFD- 3GPP Meaning: Maximum number of successive "out of sync"
0 UCONN 010101 R9 indications received from Layer 1. The protocol-defined
MODET Specific default value is 20. The value of this parameter is
IMER ations contained in SIB1 messages.
GUI Value Range: D1, D2, D4, D10, D20, D50, D100,
D200
Unit: None
Actual Value Range: 1, 2, 4, 10, 20, 50, 100, 200
Default Value: D50
N315 BSC690 SET WRFD- 3GPP Meaning: Maximum number of successive "in sync"
0 UCONN 010101 R9 indications received from Layer 1 after T313 starts. The
MODET Specific protocol-defined default value is 1. The value of this
IMER ations parameter is contained in SIB1 messages.
GUI Value Range: D1, D2, D4, D10, D20, D50, D100,
D200, D400, D600, D800, D1000
Unit: None
Actual Value Range: 1, 2, 4, 10, 20, 50, 100, 200, 400,
600, 800, 1000
Default Value: D1
N315 BSC691 SET WRFD- 3GPP Meaning: Maximum number of successive "in sync"
0 UCONN 010101 R9 indications received from Layer 1 after T313 starts. The
MODET Specific protocol-defined default value is 1. The value of this
IMER ations parameter is contained in SIB1 messages.
GUI Value Range: D1, D2, D4, D10, D20, D50, D100,
D200, D400, D600, D800, D1000
Unit: None
Actual Value Range: 1, 2, 4, 10, 20, 50, 100, 200, 400,
600, 800, 1000
Default Value: D1
T302 BSC690 SET WRFD- 3GPP Meaning: Timer 302. T302 starts when a UE sends a
0 UCONN 010101 R9 CELL UPDATE/URA UPDATE message and stops
MODET Specific when the UE receives a CELL UPDATE CONFIRM/
IMER ations URA UPDATE CONFIRM message. When T302
expires, the UE resends a CELL UPDATE/URA
UPDATE message if the value of the counter V302 is
smaller than or equal to that of the parameter N302. If
the value of V302 is larger than that of N302 when T302
expires, the UE enters the idle mode. The protocol-
defined default value is 4000. The value of this
parameter is contained in SIB1 messages.
GUI Value Range: D100, D200, D400, D600, D800,
D1000, D1200, D1400, D1600, D1800, D2000, D3000,
D4000, D6000, D8000
Unit: ms
Actual Value Range: 100, 200, 400, 600, 800, 1000,
1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000
Default Value: D2000
T302 BSC691 SET WRFD- 3GPP Meaning: Timer 302. T302 starts when a UE sends a
0 UCONN 010101 R9 CELL UPDATE/URA UPDATE message and stops
MODET Specific when the UE receives a CELL UPDATE CONFIRM/
IMER ations URA UPDATE CONFIRM message. When T302
expires, the UE resends a CELL UPDATE/URA
UPDATE message if the value of the counter V302 is
smaller than or equal to that of the parameter N302. If
the value of V302 is larger than that of N302 when T302
expires, the UE enters the idle mode. The protocol-
defined default value is 4000. The value of this
parameter is contained in SIB1 messages.
GUI Value Range: D100, D200, D400, D600, D800,
D1000, D1200, D1400, D1600, D1800, D2000, D3000,
D4000, D6000, D8000
Unit: ms
Actual Value Range: 100, 200, 400, 600, 800, 1000,
1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000
Default Value: D2000
RbSetup BSC690 SET WRFD- 3GPP Meaning: A timer to RNC wait for the RB setup
RspTmr 0 USTAT 010101 R9 response from UE in the RB procedure. Refer to the
ETIME Specific Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
RbSetup BSC691 SET WRFD- 3GPP Meaning: A timer to RNC wait for the RB setup
RspTmr 0 USTAT 010101 R9 response from UE in the RB procedure. Refer to the
ETIME Specific Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
RESERVED_SWITCH_5_BIT3,
RESERVED_SWITCH_5_BIT4,
RESERVED_SWITCH_5_BIT5,
RESERVED_SWITCH_5_BIT6,
RESERVED_SWITCH_5_BIT7,
RESERVED_SWITCH_5_BIT8,
RESERVED_SWITCH_5_BIT9,
RESERVED_SWITCH_5_BIT10,
RESERVED_SWITCH_5_BIT11,
RESERVED_SWITCH_5_BIT12,
RESERVED_SWITCH_5_BIT13,
RESERVED_SWITCH_5_BIT14,
RESERVED_SWITCH_5_BIT15,
RESERVED_SWITCH_5_BIT16,
RESERVED_SWITCH_5_BIT17,
RESERVED_SWITCH_5_BIT18,
RESERVED_SWITCH_5_BIT19,
RESERVED_SWITCH_5_BIT20,
RESERVED_SWITCH_5_BIT21,
RESERVED_SWITCH_5_BIT22,
RESERVED_SWITCH_5_BIT23,
RESERVED_SWITCH_5_BIT24,
RESERVED_SWITCH_5_BIT25,
RESERVED_SWITCH_5_BIT26,
RESERVED_SWITCH_5_BIT27,
RESERVED_SWITCH_5_BIT28,
RESERVED_SWITCH_5_BIT29,
RESERVED_SWITCH_5_BIT30,
RESERVED_SWITCH_5_BIT31,
RESERVED_SWITCH_5_BIT32
Default Value:
RESERVED_SWITCH_5_BIT1-1&RESERVED_SW
ITCH_5_BIT2-1&RESERVED_SWITCH_5_BIT3-1
&RESERVED_SWITCH_5_BIT4-1&RESERVED_S
WITCH_5_BIT5-1&RESERVED_SWITCH_5_BIT6
-1&RESERVED_SWITCH_5_BIT7-1&RESERVED
_SWITCH_5_BIT8-1&RESERVED_SWITCH_5_BI
T9-1&RESERVED_SWITCH_5_BIT10-1&RESERV
ED_SWITCH_5_BIT11-1&RESERVED_SWITCH_5
_BIT12-1&RESERVED_SWITCH_5_BIT13-1&RES
ERVED_SWITCH_5_BIT14-1&RESERVED_SWIT
CH_5_BIT15-1&RESERVED_SWITCH_5_BIT16-1
&RESERVED_SWITCH_5_BIT17-1&RESERVED_
SWITCH_5_BIT18-1&RESERVED_SWITCH_5_BI
T19-1&RESERVED_SWITCH_5_BIT20-1&RESER
VED_SWITCH_5_BIT21-1&RESERVED_SWITCH
_5_BIT22-1&RESERVED_SWITCH_5_BIT23-1&R
ESERVED_SWITCH_5_BIT24-1&RESERVED_SW
ITCH_5_BIT25-1&RESERVED_SWITCH_5_BIT26
-1&RESERVED_SWITCH_5_BIT27-1&RESERVE
D_SWITCH_5_BIT28-1&RESERVED_SWITCH_5_
BIT29-1&RESERVED_SWITCH_5_BIT30-1&RESE
RVED_SWITCH_5_BIT31-1&RESERVED_SWITC
H_5_BIT32-1
RESERVED_SWITCH_5_BIT3,
RESERVED_SWITCH_5_BIT4,
RESERVED_SWITCH_5_BIT5,
RESERVED_SWITCH_5_BIT6,
RESERVED_SWITCH_5_BIT7,
RESERVED_SWITCH_5_BIT8,
RESERVED_SWITCH_5_BIT9,
RESERVED_SWITCH_5_BIT10,
RESERVED_SWITCH_5_BIT11,
RESERVED_SWITCH_5_BIT12,
RESERVED_SWITCH_5_BIT13,
RESERVED_SWITCH_5_BIT14,
RESERVED_SWITCH_5_BIT15,
RESERVED_SWITCH_5_BIT16,
RESERVED_SWITCH_5_BIT17,
RESERVED_SWITCH_5_BIT18,
RESERVED_SWITCH_5_BIT19,
RESERVED_SWITCH_5_BIT20,
RESERVED_SWITCH_5_BIT21,
RESERVED_SWITCH_5_BIT22,
RESERVED_SWITCH_5_BIT23,
RESERVED_SWITCH_5_BIT24,
RESERVED_SWITCH_5_BIT25,
RESERVED_SWITCH_5_BIT26,
RESERVED_SWITCH_5_BIT27,
RESERVED_SWITCH_5_BIT28,
RESERVED_SWITCH_5_BIT29,
RESERVED_SWITCH_5_BIT30,
RESERVED_SWITCH_5_BIT31,
RESERVED_SWITCH_5_BIT32
Default Value:
RESERVED_SWITCH_5_BIT1-1&RESERVED_SW
ITCH_5_BIT2-1&RESERVED_SWITCH_5_BIT3-1
&RESERVED_SWITCH_5_BIT4-1&RESERVED_S
WITCH_5_BIT5-1&RESERVED_SWITCH_5_BIT6
-1&RESERVED_SWITCH_5_BIT7-1&RESERVED
_SWITCH_5_BIT8-1&RESERVED_SWITCH_5_BI
T9-1&RESERVED_SWITCH_5_BIT10-1&RESERV
ED_SWITCH_5_BIT11-1&RESERVED_SWITCH_5
_BIT12-1&RESERVED_SWITCH_5_BIT13-1&RES
ERVED_SWITCH_5_BIT14-1&RESERVED_SWIT
CH_5_BIT15-1&RESERVED_SWITCH_5_BIT16-1
&RESERVED_SWITCH_5_BIT17-1&RESERVED_
SWITCH_5_BIT18-1&RESERVED_SWITCH_5_BI
T19-1&RESERVED_SWITCH_5_BIT20-1&RESER
VED_SWITCH_5_BIT21-1&RESERVED_SWITCH
_5_BIT22-1&RESERVED_SWITCH_5_BIT23-1&R
ESERVED_SWITCH_5_BIT24-1&RESERVED_SW
ITCH_5_BIT25-1&RESERVED_SWITCH_5_BIT26
-1&RESERVED_SWITCH_5_BIT27-1&RESERVE
D_SWITCH_5_BIT28-1&RESERVED_SWITCH_5_
BIT29-1&RESERVED_SWITCH_5_BIT30-1&RESE
RVED_SWITCH_5_BIT31-1&RESERVED_SWITC
H_5_BIT32-1
RESERVED_SWITCH_BIT5,
RESERVED_SWITCH_BIT6,
RESERVED_SWITCH_BIT7,
RESERVED_SWITCH_BIT8,
RESERVED_SWITCH_BIT9,
RESERVED_SWITCH_BIT10,
RESERVED_SWITCH_BIT11,
RESERVED_SWITCH_BIT12,
RESERVED_SWITCH_BIT13,
RESERVED_SWITCH_BIT14,
RESERVED_SWITCH_BIT15,
RESERVED_SWITCH_BIT16,
RESERVED_SWITCH_BIT17,
RESERVED_SWITCH_BIT18,
RESERVED_SWITCH_BIT19,
RESERVED_SWITCH_BIT20,
RESERVED_SWITCH_BIT21,
RESERVED_SWITCH_BIT22,
RESERVED_SWITCH_BIT23,
RESERVED_SWITCH_BIT24,
RESERVED_SWITCH_BIT25,
RESERVED_SWITCH_BIT26,
RESERVED_SWITCH_BIT27,
RESERVED_SWITCH_BIT28,
RESERVED_SWITCH_BIT29,
RESERVED_SWITCH_BIT30,
RESERVED_SWITCH_BIT31,
RESERVED_SWITCH_BIT32
Default Value:
RESERVED_SWITCH_BIT1-0&RESERVED_SWIT
CH_BIT2-0&RESERVED_SWITCH_BIT3-0&RESE
RVED_SWITCH_BIT4-0&RESERVED_SWITCH_
BIT5-0&RESERVED_SWITCH_BIT6-0&RESERVE
D_SWITCH_BIT7-0&RESERVED_SWITCH_BIT8-
0&RESERVED_SWITCH_BIT9-0&RESERVED_S
WITCH_BIT10-0&RESERVED_SWITCH_BIT11-0
&RESERVED_SWITCH_BIT12-0&RESERVED_S
WITCH_BIT13-0&RESERVED_SWITCH_BIT14-0
&RESERVED_SWITCH_BIT15-0&RESERVED_S
WITCH_BIT16-0&RESERVED_SWITCH_BIT17-0
&RESERVED_SWITCH_BIT18-0&RESERVED_S
WITCH_BIT19-0&RESERVED_SWITCH_BIT20-0
&RESERVED_SWITCH_BIT21-0&RESERVED_S
WITCH_BIT22-0&RESERVED_SWITCH_BIT23-0
&RESERVED_SWITCH_BIT24-0&RESERVED_S
WITCH_BIT25-0&RESERVED_SWITCH_BIT26-0
&RESERVED_SWITCH_BIT27-0&RESERVED_S
WITCH_BIT28-0&RESERVED_SWITCH_BIT29-0
&RESERVED_SWITCH_BIT30-0&RESERVED_S
WITCH_BIT31-0&RESERVED_SWITCH_BIT32-0
RESERVED_SWITCH_BIT5,
RESERVED_SWITCH_BIT6,
RESERVED_SWITCH_BIT7,
RESERVED_SWITCH_BIT8,
RESERVED_SWITCH_BIT9,
RESERVED_SWITCH_BIT10,
RESERVED_SWITCH_BIT11,
RESERVED_SWITCH_BIT12,
RESERVED_SWITCH_BIT13,
RESERVED_SWITCH_BIT14,
RESERVED_SWITCH_BIT15,
RESERVED_SWITCH_BIT16,
RESERVED_SWITCH_BIT17,
RESERVED_SWITCH_BIT18,
RESERVED_SWITCH_BIT19,
RESERVED_SWITCH_BIT20,
RESERVED_SWITCH_BIT21,
RESERVED_SWITCH_BIT22,
RESERVED_SWITCH_BIT23,
RESERVED_SWITCH_BIT24,
RESERVED_SWITCH_BIT25,
RESERVED_SWITCH_BIT26,
RESERVED_SWITCH_BIT27,
RESERVED_SWITCH_BIT28,
RESERVED_SWITCH_BIT29,
RESERVED_SWITCH_BIT30,
RESERVED_SWITCH_BIT31,
RESERVED_SWITCH_BIT32
Default Value:
RESERVED_SWITCH_BIT1-0&RESERVED_SWIT
CH_BIT2-0&RESERVED_SWITCH_BIT3-0&RESE
RVED_SWITCH_BIT4-0&RESERVED_SWITCH_
BIT5-0&RESERVED_SWITCH_BIT6-0&RESERVE
D_SWITCH_BIT7-0&RESERVED_SWITCH_BIT8-
0&RESERVED_SWITCH_BIT9-0&RESERVED_S
WITCH_BIT10-0&RESERVED_SWITCH_BIT11-0
&RESERVED_SWITCH_BIT12-0&RESERVED_S
WITCH_BIT13-0&RESERVED_SWITCH_BIT14-0
&RESERVED_SWITCH_BIT15-0&RESERVED_S
WITCH_BIT16-0&RESERVED_SWITCH_BIT17-0
&RESERVED_SWITCH_BIT18-0&RESERVED_S
WITCH_BIT19-0&RESERVED_SWITCH_BIT20-0
&RESERVED_SWITCH_BIT21-0&RESERVED_S
WITCH_BIT22-0&RESERVED_SWITCH_BIT23-0
&RESERVED_SWITCH_BIT24-0&RESERVED_S
WITCH_BIT25-0&RESERVED_SWITCH_BIT26-0
&RESERVED_SWITCH_BIT27-0&RESERVED_S
WITCH_BIT28-0&RESERVED_SWITCH_BIT29-0
&RESERVED_SWITCH_BIT30-0&RESERVED_S
WITCH_BIT31-0&RESERVED_SWITCH_BIT32-0
NoDisca BSC690 ADD WRFD- Logical Meaning: Maximum number of transmissions of a PDU
rdMaxD 0 UTYPR 020900 Channel before the RLC entity is reset. This parameter is
AT ABRLC Manage applicable to only the AM RLC entity whose
MOD ment "AMRlcDiscardMode" is set to NO_DISCARD. In this
UTYPR mode, the RLC entity will be directly reset if the number
ABRLC of retransmissions of an SDU 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, see 3GPP TS 25.322.
GUI Value Range: D1, D2, D3, D4, D5, D6, D7, D8,
D9, D10, D15, D20, D25, D30, D35, D40
Unit: None
Actual Value Range: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20,
25, 30, 35, 40
Default Value: None
NoDisca BSC691 ADD WRFD- Logical Meaning: Maximum number of transmissions of a PDU
rdMaxD 0 UTYPR 020900 Channel before the RLC entity is reset. This parameter is
AT ABRLC Manage applicable to only the AM RLC entity whose
MOD ment "AMRlcDiscardMode" is set to NO_DISCARD. In this
UTYPR mode, the RLC entity will be directly reset if the number
ABRLC of retransmissions of an SDU 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, see 3GPP TS 25.322.
GUI Value Range: D1, D2, D3, D4, D5, D6, D7, D8,
D9, D10, D15, D20, D25, D30, D35, D40
Unit: None
Actual Value Range: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20,
25, 30, 35, 40
Default Value: None
Unit: None
Actual Value Range:
TIMER_BASED_WITH_EXPLICIT_SIGNALLING,
DISCARD_AFTER_MAX_DAT_RETRANSMIS-
SIONS, NO_DISCARD
Default Value: None
Unit: None
Actual Value Range:
TIMER_BASED_WITH_EXPLICIT_SIGNALLING,
DISCARD_AFTER_MAX_DAT_RETRANSMIS-
SIONS, NO_DISCARD
Default Value: None
RbRecfg BSC690 SET WRFD- 3GPP Meaning: A timer used to wait for the RB
RspTmr 0 USTAT 010101 R9 reconfiguration response from UE in the RB procedure.
ETIME Specific Refer to the Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
RbRecfg BSC691 SET WRFD- 3GPP Meaning: A timer used to wait for the RB
RspTmr 0 USTAT 010101 R9 reconfiguration response from UE in the RB procedure.
ETIME Specific Refer to the Note.
R ations GUI Value Range: 300~300000
Unit: ms
Actual Value Range: 300~300000
Default Value: 5000
N302 BSC690 SET WRFD- 3GPP Meaning: Maximum number of retransmissions of the
0 UCONN 010101 R9 CELL UPDATE/URA UPDATE message. The
MODET Specific protocol-defined default value is 3. The value of this
IMER ations parameter is contained in SIB1 messages.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 3
N302 BSC691 SET WRFD- 3GPP Meaning: Maximum number of retransmissions of the
0 UCONN 010101 R9 CELL UPDATE/URA UPDATE message. The
MODET Specific protocol-defined default value is 3. The value of this
IMER ations parameter is contained in SIB1 messages.
GUI Value Range: 0~7
Unit: None
Actual Value Range: 0~7
Default Value: 3
12 Counters
13 Glossary
14 Reference Documents