Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Issue Draft A
Date 2014-01-20
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.........................................................................................................................................3
3 Technical Description...................................................................................................................4
4 Related Features.............................................................................................................................6
5 Network Impact.............................................................................................................................7
6 Engineering Guidelines...............................................................................................................8
6.1 When to Use MIMO Prime............................................................................................................................................8
6.1.1 Scenarios Recommended for Feature Deployment.....................................................................................................8
6.1.2 Impact and Workaround..............................................................................................................................................8
6.2 Network Planning.........................................................................................................................................................10
6.3 Deployment..................................................................................................................................................................13
6.3.1 Requirements.............................................................................................................................................................13
6.3.2 Precautions.................................................................................................................................................................14
6.3.3 Activation..................................................................................................................................................................14
6.3.4 Activation Observation..............................................................................................................................................15
6.3.5 Deactivation...............................................................................................................................................................15
6.3.6 MML Command Examples.......................................................................................................................................15
6.4 Performance Monitoring...............................................................................................................................................16
7 Parameters.....................................................................................................................................19
8 Counters........................................................................................................................................62
9 Glossary.........................................................................................................................................64
10 Reference Documents...............................................................................................................65
1.1 Scope
This document describes WRFD-030011 MIMO Prime, including its technical principles,
related features, network impact, and engineering guidelines.
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
Draft A (2014-01-20)
Compared with Issue 01 (2013-04-28) of RAN15.0, Draft A (2014-01-30) of RAN16.0 includes
the following changes.
2 Overview
Virtual antenna mapping (VAM) uses a transformation matrix to split every signal from a cell
into two, distributes the two signals to two respective power amplifiers (PAs), and the PAs then
send the two signals to two respective physical antennas with the same power.
Because the two signals arrive at the UE through different paths, a phase difference (Q1) occurs.
The value of Q1 is related to the UE location and cannot be controlled by the universal terrestrial
radio access network (UTRAN). As a result, when the UE combines the two signals, the quality
of the combined signal may increase or decrease. The MIMO Prime feature adds an initial phase
difference (Q0) to reduce Q1, thereby increasing the quality of the combined signal.
MIMO Prime improves the signal quality of High Speed Downlink Packet Access (HSDPA)
UEs to increase the HSDPA UE throughput and cell capacity. This feature depends on HSDPA
and VAM.
3 Technical Description
With MIMO Prime, the NodeB determines and dynamically adjusts the optimum initial phase
for a cell as follows:
1. The NodeB tries all the initial phases provided by VAM for a cell and records channel
quality indicators (CQIs) reported by UEs.
2. Based on these CQIs, the NodeB determines the optimum initial phase for the cell and locks
the optimum initial phase for a certain period of time.
3. The NodeB periodically repeats this process to adapt to channel quality changes.
Figure 3-1 shows a phase rotator with which the NodeB dynamically adjusts the optimum initial
phase of a cell served by antenna 2 based on the CQIs reported by UEs.
Optimum initial phase adjustment can improve the quality of combined signals for most UEs
and therefore helps increase UE throughput.
In cells where MIMO Prime is enabled, phase adjustment always applies to the signal from
antenna 2 if any HSDPA user is transmitting data.
The NodeB automatically adjusts the initial phase on a per cell basis and UEs in a cell use the
same initial phase. However, each UE has its own Q1.
When only one UE camps on a cell, optimum initial phase adjustment can improve the quality
of combined signals on the UE side.
When more than one UE camps on the cell, optimum initial phase adjustment cannot definitely
improve the quality of combined signals for all the UEs in the cell. Therefore, MIMO Prime
cannot provide noticeable gains when more than one UE camps on a cell and these UEs have a
large difference in Q1.
The parameter that specifies whether to enable MIMO Prime in non-MIMO cells is
MIMOPRIMESW.
4 Related Features
Prerequisite Features
WRFD-010610 HSDPA
Impacted Features
None
5 Network Impact
System Capacity
MIMO Prime increases the throughput by 5% to 10% of a cell where MIMO has not been
activated. The increase in cell throughput depends on the cell traffic model, which includes the
number of UEs and the behavior and location of the UEs. This feature yields notable gains for
UEs at the cell center or cell edge.
Network Performance
MIMO Prime affects network performance as follows:
l In multicarrier networks enabled with service steering, activating MIMO Prime decreases
the HSPA radio access bearer (RAB) setup success rate.
l Activating MIMO Prime increases cell throughput but feature gains vary with UE locations.
Generally, features gains for cell edge users are greater than or equal to those for cell center
users.
For details about the related workarounds, see section 6.1.2 Impact and Workaround.
6 Engineering Guidelines
Activate this feature in cells with contiguous coverage, high cell throughput, and a large number
of HSDPA UEs.
MIMO Prime is dependent on HSDPA but not on MIMO. Therefore, MIMO Prime can be
activated in non-MIMO cells. When the local cell is MIMO-capable, see MIMO Feature
Parameter Description.
Table 6-1 Impact of MIMO Prime on network KPIs and the related solutions
Table 6-2 Impact of MIMO Prime on service KPIs and the related solutions
l The delay difference between the transmit channel on one RRU and that on another RRU
is shorter than 1/4 chip.
l The two RRUs use the same transmit power.
l The two RRUs use the chain or star topology.
The following figures show different connections between the BBU and RRUs.
6.3 Deployment
This chapter describes how to activate, verify, and deactivate the basic feature WRFD-030011
MIMO Prime.
6.3.1 Requirements
l Dependencies on Hardware
Only the 40 W RRU3801C, RRU3804, RRU3806, RRU3808, RRU3805, WRFUd,
RRU3828, RRU3829, RRU3928, RRU3938, RRU3929, MRFUd, MRFUe, RRU3942,
RRU3824, RRU3826, RRU3838, WRFUa, WRFUe, RRU3938, RRU3926, RRU3936,
850 MHz/900 MHz/1900 MHz RRU3908 V1 and 1900 MHz/2100 MHz WRFU support
this feature. RRU3908 V2 and MRFU V2 in RAN14.0 and later versions support this
feature.
Two RRU modules, each with one TX channel, are required to support this feature.
The BTS3812E/AE does not support this feature.
The DBS3800 does not support this feature.
The DBS3800 supports this feature only when the enhanced downlink baseband board,
such as the EBBC or EBBCd board, is configured.
The BTS3900, BTS3900A, or DBS3900 supports this feature only when the WBBPb,
WBBPd, or WBBPf board is configured.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l License
The license "MIMO Prime (per Cell)" has been activated on the NodeB side. For details
about how to activate the license, see License Management Feature Parameter
Description.
6.3.2 Precautions
Because the downlink bandwidth for transmit diversity is twice the downlink bandwidth for non-
transmit diversity, the number of transmit diversity cells supported by a CPRI port is less than
the number of non-transmit diversity cells supported by the CPRI port.
For the 3900 series base stations, BTS3902E, and BTS3803E, you are advised to run the DEA
UCELL command to deactivate the cells to be added to a MIMO Prime cell group before
activating MIMO Prime. Otherwise, online UEs in these cells experience call drops.
For the DBS3800, BTS3812E, BTS3812A, and BTS3812AE, you must run the DEA UCELL
command to deactivate the cells to be added to a MIMO Prime cell group before activating
MIMO Prime.
6.3.3 Activation
Step 1 On the NodeB LMT, set Diversity Mode for the sector for the cell as follows:
1. Run the NodeB MML command MOD SECTOREQM (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > Sector; CME batch
modification center: Modifying Physical NodeB Parameters in Batches) to modify the RX
and TX modes of a sector.
2. Run the NodeB MML command MOD ULOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Sector ; CME batch modification
center: Modifying Physical NodeB Parameters in Batches) to configure the local cell. In
this step, set Support VAM to TRUE(TRUE).
NOTE
l MIMO Prime is based on the VAM technique. VAM depends on the configuration of dual-antenna
receive diversity for the sector, not the value of Two Tx Way for the local cell. For details, see chapter
3 "Technical Description." When the local cell is not MIMO-capable, it's suggested to set Two Tx
Way to FALSE for the local cell. When the local cell is MIMO-capable, see MIMO Feature Parameter
Description.
l When Two Tx Way is set to FALSE for the local cell, configure dual transmitting way for the sector
by referring to section "Scenario 9" of NodeB Carrier Management Feature Parameter Description.
When Two Tx Way is set to TRUE, configure that by referring to section "Scenario 10" of NodeB
Carrier Management Feature Parameter Description.
Step 2 Run the NodeB MML command SET ULOCELLMACHSPARA (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > Locell Algorithm
Parameters > MAC Parameters > MACHSPARA; CME batch modification center:
Modifying Physical NodeB Parameters in Batches). In this step, set MIMO Prime Switch to
OPEN(open).
----End
6.3.5 Deactivation
1. On the NodeB, remove the old local cell and establish a new local cell.
Run the NodeB MML command MOD ULOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > Sector ; CME batch modification
center: Modifying Physical NodeB Parameters in Batches) to configure the local cell. In
this step, set Support VAM to FALSE(FALSE).
2. Run the NodeB MML command SET ULOCELLMACHSPARA (CME single
configuration: NodeB Configuration Express > IUB_NodeB > Radio Layer > Locell
Algorithm Parameters > MAC Parameters > MACHSPARA; CME batch modification
center: Modifying Physical NodeB Parameters in Batches). In this step, set MIMO Prime
Switch to CLOSE(close).
Counter Description
Counter Description
It is recommended that feature gains be evaluated based on the HSDPA throughput and power
efficiency of the target cell.
Before this feature is activated, monitor the HSDPA throughput and power efficiency of the
target cell for two weeks without any testing.
After this feature is activated, monitor the HSDPA throughput and power efficiency of the target
cell for two weeks without any testing.
Compare the two sets of monitoring results for HSDPA throughput and power efficiency. The
HSDPA throughput and power efficiency are expected to increase after feature activation. UE
distribution and service model affect feature gains.
7 Parameters
RNC handles
the INITIAL UE
message from a
CN node if the Iu
interface is in the
reset state. 3)
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH (RB
Reconfiguration
DRD Rollback
Switch) 1: This
switch is turned
on. The RNC
supports
rollback caused
by failed
directed retry
decisions
(DRDs) of RB
reconfiguration.
0: This switch is
turned off. The
RNC does not
support rollback
caused by failed
DRDs of RB
reconfiguration.
4)
RNC_CS_QUE
RY_UE_IMEI_
SWITCH (CS
IMEI Request
Switch) 1: This
switch is turned
on. The RNC
rather than the
CN sends an
IDENTITY
REQUEST
message to
obtain the
international
mobile
equipment
identity (IMEI)
of a UE. Note:
When the CN
checks the serial
number of direct
transfer
messages and
the
SEND_MSG_N
ULL_SWITCH
switch is turned
off, turning on
this switch leads
to inconsistency
in the serial
number of direct
transfer
messages
between the CN
and the UE. This
causes CS
service setup
failures.
Therefore, you
are not advised
to turn on this
switch. Before
turning on this
switch, test the
interworking
between the
RNC and the
CN. If the CN
checks the serial
number of direct
transfer
messages, turn
on
SEND_MSG_N
ULL_SWITCH
under
"PROCESSSWI
TCH4" in the
"SET
URRCTRLSWI
TCH"
command. 0:
This switch is
turned off. The
RNC does not
send an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 5)
RNC_PS_QUE
RY_UE_IMEI_
SWITCH (PS
IMEI Request
Switch) 1: This
switch is turned
on. The RNC,
rather than the
CN, sends an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 0: This
switch is turned
off. The RNC
does not send an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 6)
FACH_DTCH_
CONGEST_P2
D (P2D Switch
for Congested
FACH or
DTCH) 1: This
switch is turned
on. UEs using
PS services
trigger the
CELL_PCH-to-
CELL_DCH
procedure (P2D
procedure for
short) on a
congested
FACH or
DTCH. 0: This
switch is turned
off. UEs using
PS services do
not trigger the
P2D procedure
on a congested
FACH or
DTCH. 7)
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH (RB
Establishment
DRD Rollback
Switch) 1: This
switch is turned
on. The RNC
supports
rollback caused
by failed DRDs
of RB
establishment.
0: This switch is
turned off. The
RNC does not
support rollback
caused by failed
DRDs of RB
establishment.
However, the
RNC cannot
control the
scenario where
the RB fast setup
function is used
for RB
establishment
accompanied by
DRDs. 8)
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
(Switch for Not
Triggering Rate
Reduction
Negotiation
Between the CN
and the RNC
After a PS
Service Access
Failure) 1: This
switch is turned
on. The access
rate is not
negotiated
between the
RNC and the CN
if a PS service
fails to be
admitted. 0: This
switch is turned
off. The access
rate is
negotiated
between the
RNC and the CN
if a PS service
fails to be
admitted. 9)
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH
(Switch for
Performing the
Optimized Soft-
Handover
Timeout
Procedure) 1:
This switch is
turned on. The
RNC considers
that it has
received an
ACTIVE SET
UPDATE
COMPLETE
message during
soft handover
procedure after
the message has
expired. 0: This
switch is turned
off. RABs are
directly released
during soft
handover
procedure after
the ACTIVE
SET UPDATE
COMPLETE
message has
expired. 10)
RB_RECFG_U
SER_INACT_S
WITCH (Switch
for Performing
the Optimized
RRC
Connection
Release
Procedure with
No Data
Transmitted on
the UE upon UE
State Transition
Timeout) 1: This
switch is turned
on. The RNC
initiated the
release process
with the cause of
user inactive
when the UE
have no data to
transmit. 0: This
switch is turned
off. The RNC
initiated the
release process
with other
causes when the
UE have no data
to transmit. 11)
RRC_SCRI_N
ORM_REL_S
WITCH (Switch
for Performing
the Optimized
RRC
Connection
Release
Procedure on
Receipt of a
SIGNALLING
CONNECTION
RELEASE
INDICATION
Message) 1:
This switch is
turned on. The
RNC initiated
the normal
release process
after receive
SIGNALLING
CONNECTION
RELEASE
INDICATION
message from
UE. 0: This
switch is turned
off. The RNC
does not handle
SIGNALLING
CONNECTION
RELEASE
INDICATION
message during
the process. 12)
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH (Switch
for SRB
Reestablishment
During a Cell
Update with the
Cause Value of
RL Failure) 1:
This switch is
turned on. SRBs
are reestablished
during cell
update
procedure with
the "RL Failure"
cause value. 0:
This switch is
turned off. SRBs
are not
reestablished
during cell
update
procedure with
Layer 2 data
transmission
error occurs. 15)
RNC_FD_SCRI
_FORCE_REL_
SWITCH
(Signaling
Connection
Release Switch
for UEs
Supporting Fast
Dormancy) 1:
This switch is
turned on. If the
RNC receives a
SIGNALING
CONNECTION
RELEASE
INDICATION
from UE with
the cause of "UE
Requested PS
Data session
end", the RNC
triggers the state
transition for the
UE. Otherwise,
the RNC
releases the
signaling
connection. 0:
This switch is
turned off. If the
RNC receives a
SIGNALING
CONNECTION
RELEASE
INDICATION
from UE, the
RNC triggers
the state
transition for the
UE. 16)
USRPLN_PRO
RATION_SHA
RED_ALO
(Algorithm
Switch for Inter-
Subrack Load
Sharing on the
User Plane) 1:
This switch is
turned on. Load
sharing can be
performed based
on the ratio of
available user
plane resources
to total user
plane resources
in a subrack. 0:
This switch is
turned off. Load
sharing cannot
be performed
based on the
ratio of available
user plane
resources to
total user plane
resources in a
subrack. 17)
FP_IUUP_TRA
CE_SWITCH
(Switch for
Tracing UEs
Failing in FP
Synchronization
) 1: This switch
is turned on.
UEs using FP
can be traced in
terms of data
streams. 0: This
switch is turned
off. UEs using
FP cannot be
traced in terms
of data streams.
18)
RNC_PCHR_O
UTPUT_CTRL
_SWITCH
(Switch for
Reducing PCHR
Log Information
for Normal
Procedure) The
switch
RNC_PCHR_O
UTPUT_CTRL
_SWITCH
controls whether
the RNC
reduces
information
recorded in a
PCHR log for a
normal
procedure. 1:
This switch is
turned on. The
RNC reduces
information in a
performance
call history
record (PCHR)
log recorded
during a normal
procedure and
reports only the
following
information
blocks: -
RRC_RELEAS
E-
CS_RAB_SET
UP -
PS_RAB_SET
UP -
CS_RAB_REL
-PS_RAB_REL
-SHO -
SYS_HO_OUT
-
INTRA_FREQ_
NET_OPT -
STAT -
CS_RAB_QUA
LITY_STAT -
PS_RAB_QUA
LITY_STAT A
procedure is
abnormal only
when either of
the following
conditions is
met: -The RRC
connection
setup fails. -The
RAB setup fails.
-The RAB is
abnormally
released. -The
value of the
information
element (IE)
NAS-PDU
contained in a
DIRECT
TRANSFER
message is
ATTACH
REJECT, RAU
REJECT, or
LAU REJECT.
0: This switch is
turned off. The
RNC does not
reduce
information
recorded in a
PCHR log. 19)
DTMF_SWITC
H (DTMF
Switch) 1: This
switch is turned
on. The RNC
starts tracing
after receiving a
special
RANAP_DIRE
CT_TRANSFE
R message from
a UE. 0: This
switch is turned
off. The RNC
does not start
tracing after
receiving a
special
RANAP_DIRE
CT_TRANSFE
R message from
a UE. 20)
FAST_CS_FB_
BASEDON_RI
M_SWITCH
(Switch for fast
CSFB based on
RIM) 1: This
switch is turned
on. The RNC
supports fast
CSFB(CS
fallback) based
on RIM. 0: This
switch is turned
off. The RNC
does not support
fast CSFB(CS
fallback) based
on RIM. 21)
L2U_SRVCC_
WITH_PS_HO
_SWITCH
Whether to
support LTE-to-
UMTS CS and
PS handovers
simultaneously.
1: This switch is
turned on. LTE-
to-UMTS CS
and PS
handovers can
happen
simultaneously.
0: This switch is
turned off. LTE-
to-UMTS CS
and PS
handovers
cannot happen
simultaneously.
22)
ULTRA_FLAS
H_CSFB_SWIT
CH(Ultra-Flash
CSFB Function
Switch)
Whether the
Ultra-Flash
CSFB function
takes effect. 1:
This switch is
turned on. The
RNC supports
the Ultra-Flash
CSFB function,
and the delay of
CSFB is
reduced,
improving user
experience. 0:
This switch is
turned off. The
RNC does not
support the
Ultra-Flash
CSFB function,
and the delay of
CSFB is long,
affecting user
experience. 23)
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
(Support RNC
PS Querying UE
IMEISV)
Whether the
RNC sends an
Identity Request
message to the
UE, requesting
the UE's
international
mobile station
equipment
identity and
software version
(IMEISV). 1:
This switch is set
to on. The RNC
sends an Identity
Request
message to the
UE, requesting
the UE's
IMEISV. 0: This
switch is set to
off. The RNC
does not send an
Identity Request
message to the
UE. If this
switch is
enabled together
with the
RNC_PS_QUE
RY_UE_IMEI_
SWITCH, the
RNC queries the
UE's IMEISV,
not IMEI.
Disuse
Statement:This
switch
USRPLN_PRO
RATION_SHA
RED_ALO will
be deleted from
later versions.
Although the
configuration
interface in this
version supports
delivery of the
setting of this
switch, the
system does not
use this switch.
Therefore, this
switch is not
recommended.
GUI Value
Range:LOAD_I
RAT_HO_RNC
_FILL_TL,
SEND_IDT_JU
DGE_IU_RESE
T,
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH,
RNC_CS_QUE
RY_UE_IMEI_
SWITCH,
RNC_PS_QUE
RY_UE_IMEI_
SWITCH,
FACH_DTCH_
CONGEST_P2
D,
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH,
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
,
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH,
RB_RECFG_U
SER_INACT_S
WITCH,
RRC_SCRI_N
ORM_REL_S
WITCH,
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH,
CU_OVERLAP
_DSCR_SWIT
CH,
TRB_RST_DS
CR_SWITCH,
RNC_FD_SCRI
_FORCE_REL_
SWITCH,
USRPLN_PRO
RATION_SHA
RED_ALO,
FP_IUUP_TRA
CE_SWITCH,
RNC_PCHR_O
UTPUT_CTRL
_SWITCH,
DTMF_SWITC
H,
FAST_CS_FB_
BASEDON_RI
M_SWITCH,
L2U_SRVCC_
WITH_PS_HO
_SWITCH,
ULTRA_FLAS
H_CSFB_SWIT
CH,
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
Unit:None
Actual Value
Range:LOAD_I
RAT_HO_RNC
_FILL_TL,
SEND_IDT_JU
DGE_IU_RESE
T,
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH,
RNC_CS_QUE
RY_UE_IMEI_
SWITCH,
RNC_PS_QUE
RY_UE_IMEI_
SWITCH,
FACH_DTCH_
CONGEST_P2
D,
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH,
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
,
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH,
RB_RECFG_U
SER_INACT_S
WITCH,
RRC_SCRI_N
ORM_REL_S
WITCH,
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH,
CU_OVERLAP
_DSCR_SWIT
CH,
TRB_RST_DS
CR_SWITCH,
RNC_FD_SCRI
_FORCE_REL_
SWITCH,
USRPLN_PRO
RATION_SHA
RED_ALO,
FP_IUUP_TRA
CE_SWITCH,
RNC_PCHR_O
UTPUT_CTRL
_SWITCH,
DTMF_SWITC
H,
FAST_CS_FB_
BASEDON_RI
M_SWITCH,
L2U_SRVCC_
WITH_PS_HO
_SWITCH,
ULTRA_FLAS
H_CSFB_SWIT
CH,
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
Default
Value:LOAD_I
RAT_HO_RNC
_FILL_TL:
0,SEND_IDT_J
UDGE_IU_RE
SET:
0,RNC_RBREC
FG_DRD_FAIL
_ROLLBACK_
SWITCH:
1,RNC_CS_QU
ERY_UE_IMEI
_SWITCH:
0,RNC_PS_QU
ERY_UE_IMEI
_SWITCH:
0,FACH_DTC
H_CONGEST_
P2D:
0,RNC_RBSET
UP_DRD_FAIL
_ROLLBACK_
SWITCH:
0,PS_NOTIFY
CN_NOTDOW
NSIZE_SWITC
H:
0,ASU_RSP_TI
MEOUT_HAN
DLE_SWITCH:
0,RB_RECFG_
USER_INACT_
SWITCH:
0,RRC_SCRI_
NORM_REL_S
WITCH:
0,CELLUPT_R
LFAILURE_SR
BREESTAB_S
WITCH:
0,CU_OVERL
AP_DSCR_SW
ITCH:
0,TRB_RST_D
SCR_SWITCH:
0,RNC_FD_SC
RI_FORCE_RE
L_SWITCH:
0,USRPLN_PR
ORATION_SH
ARED_ALO:
0,FP_IUUP_TR
ACE_SWITCH:
1,RNC_PCHR_
OUTPUT_CTR
L_SWITCH:
1,DTMF_SWIT
CH:
1,FAST_CS_F
B_BASEDON_
RIM_SWITCH:
0,L2U_SRVCC
_WITH_PS_H
O_SWITCH:
0,ULTRA_FLA
SH_CSFB_SWI
TCH:
0,RNC_PS_QU
ERY_UE_IMEI
SV_SWITCH:0
RNC handles
the INITIAL UE
message from a
CN node if the Iu
interface is in the
reset state. 3)
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH (RB
Reconfiguration
DRD Rollback
Switch) 1: This
switch is turned
on. The RNC
supports
rollback caused
by failed
directed retry
decisions
(DRDs) of RB
reconfiguration.
0: This switch is
turned off. The
RNC does not
support rollback
caused by failed
DRDs of RB
reconfiguration.
4)
RNC_CS_QUE
RY_UE_IMEI_
SWITCH (CS
IMEI Request
Switch) 1: This
switch is turned
on. The RNC
rather than the
CN sends an
IDENTITY
REQUEST
message to
obtain the
international
mobile
equipment
identity (IMEI)
of a UE. Note:
When the CN
checks the serial
number of direct
transfer
messages and
the
SEND_MSG_N
ULL_SWITCH
switch is turned
off, turning on
this switch leads
to inconsistency
in the serial
number of direct
transfer
messages
between the CN
and the UE. This
causes CS
service setup
failures.
Therefore, you
are not advised
to turn on this
switch. Before
turning on this
switch, test the
interworking
between the
RNC and the
CN. If the CN
checks the serial
number of direct
transfer
messages, turn
on
SEND_MSG_N
ULL_SWITCH
under
"PROCESSSWI
TCH4" in the
"SET
URRCTRLSWI
TCH"
command. 0:
This switch is
turned off. The
RNC does not
send an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 5)
RNC_PS_QUE
RY_UE_IMEI_
SWITCH (PS
IMEI Request
Switch) 1: This
switch is turned
on. The RNC,
rather than the
CN, sends an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 0: This
switch is turned
off. The RNC
does not send an
IDENTITY
REQUEST
message to
obtain the IMEI
of a UE. 6)
FACH_DTCH_
CONGEST_P2
D (P2D Switch
for Congested
FACH or
DTCH) 1: This
switch is turned
on. UEs using
PS services
trigger the
CELL_PCH-to-
CELL_DCH
procedure (P2D
procedure for
short) on a
congested
FACH or
DTCH. 0: This
switch is turned
off. UEs using
PS services do
not trigger the
P2D procedure
on a congested
FACH or
DTCH. 7)
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH (RB
Establishment
DRD Rollback
Switch) 1: This
switch is turned
on. The RNC
supports
rollback caused
by failed DRDs
of RB
establishment.
0: This switch is
turned off. The
RNC does not
support rollback
caused by failed
DRDs of RB
establishment.
However, the
RNC cannot
control the
scenario where
the RB fast setup
function is used
for RB
establishment
accompanied by
DRDs. 8)
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
(Switch for Not
Triggering Rate
Reduction
Negotiation
Between the CN
and the RNC
After a PS
Service Access
Failure) 1: This
switch is turned
on. The access
rate is not
negotiated
between the
RNC and the CN
if a PS service
fails to be
admitted. 0: This
switch is turned
off. The access
rate is
negotiated
between the
RNC and the CN
if a PS service
fails to be
admitted. 9)
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH
(Switch for
Performing the
Optimized Soft-
Handover
Timeout
Procedure) 1:
This switch is
turned on. The
RNC considers
that it has
received an
ACTIVE SET
UPDATE
COMPLETE
message during
soft handover
procedure after
the message has
expired. 0: This
switch is turned
off. RABs are
directly released
during soft
handover
procedure after
the ACTIVE
SET UPDATE
COMPLETE
message has
expired. 10)
RB_RECFG_U
SER_INACT_S
WITCH (Switch
for Performing
the Optimized
RRC
Connection
Release
Procedure with
No Data
Transmitted on
the UE upon UE
State Transition
Timeout) 1: This
switch is turned
on. The RNC
initiated the
release process
with the cause of
user inactive
when the UE
have no data to
transmit. 0: This
switch is turned
off. The RNC
initiated the
release process
with other
causes when the
UE have no data
to transmit. 11)
RRC_SCRI_N
ORM_REL_S
WITCH (Switch
for Performing
the Optimized
RRC
Connection
Release
Procedure on
Receipt of a
SIGNALLING
CONNECTION
RELEASE
INDICATION
Message) 1:
This switch is
turned on. The
RNC initiated
the normal
release process
after receive
SIGNALLING
CONNECTION
RELEASE
INDICATION
message from
UE. 0: This
switch is turned
off. The RNC
does not handle
SIGNALLING
CONNECTION
RELEASE
INDICATION
message during
the process. 12)
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH (Switch
for SRB
Reestablishment
During a Cell
Update with the
Cause Value of
RL Failure) 1:
This switch is
turned on. SRBs
are reestablished
during cell
update
procedure with
the "RL Failure"
cause value. 0:
This switch is
turned off. SRBs
are not
reestablished
during cell
update
procedure with
Layer 2 data
transmission
error occurs. 15)
RNC_FD_SCRI
_FORCE_REL_
SWITCH
(Signaling
Connection
Release Switch
for UEs
Supporting Fast
Dormancy) 1:
This switch is
turned on. If the
RNC receives a
SIGNALING
CONNECTION
RELEASE
INDICATION
from UE with
the cause of "UE
Requested PS
Data session
end", the RNC
triggers the state
transition for the
UE. Otherwise,
the RNC
releases the
signaling
connection. 0:
This switch is
turned off. If the
RNC receives a
SIGNALING
CONNECTION
RELEASE
INDICATION
from UE, the
RNC triggers
the state
transition for the
UE. 16)
USRPLN_PRO
RATION_SHA
RED_ALO
(Algorithm
Switch for Inter-
Subrack Load
Sharing on the
User Plane) 1:
This switch is
turned on. Load
sharing can be
performed based
on the ratio of
available user
plane resources
to total user
plane resources
in a subrack. 0:
This switch is
turned off. Load
sharing cannot
be performed
based on the
ratio of available
user plane
resources to
total user plane
resources in a
subrack. 17)
FP_IUUP_TRA
CE_SWITCH
(Switch for
Tracing UEs
Failing in FP
Synchronization
) 1: This switch
is turned on.
UEs using FP
can be traced in
terms of data
streams. 0: This
switch is turned
off. UEs using
FP cannot be
traced in terms
of data streams.
18)
RNC_PCHR_O
UTPUT_CTRL
_SWITCH
(Switch for
Reducing PCHR
Log Information
for Normal
Procedure) The
switch
RNC_PCHR_O
UTPUT_CTRL
_SWITCH
controls whether
the RNC
reduces
information
recorded in a
PCHR log for a
normal
procedure. 1:
This switch is
turned on. The
RNC reduces
information in a
performance
call history
record (PCHR)
log recorded
during a normal
procedure and
reports only the
following
information
blocks: -
RRC_RELEAS
E-
CS_RAB_SET
UP -
PS_RAB_SET
UP -
CS_RAB_REL
-PS_RAB_REL
-SHO -
SYS_HO_OUT
-
INTRA_FREQ_
NET_OPT -
STAT -
CS_RAB_QUA
LITY_STAT -
PS_RAB_QUA
LITY_STAT A
procedure is
abnormal only
when either of
the following
conditions is
met: -The RRC
connection
setup fails. -The
RAB setup fails.
-The RAB is
abnormally
released. -The
value of the
information
element (IE)
NAS-PDU
contained in a
DIRECT
TRANSFER
message is
ATTACH
REJECT, RAU
REJECT, or
LAU REJECT.
0: This switch is
turned off. The
RNC does not
reduce
information
recorded in a
PCHR log. 19)
DTMF_SWITC
H (DTMF
Switch) 1: This
switch is turned
on. The RNC
starts tracing
after receiving a
special
RANAP_DIRE
CT_TRANSFE
R message from
a UE. 0: This
switch is turned
off. The RNC
does not start
tracing after
receiving a
special
RANAP_DIRE
CT_TRANSFE
R message from
a UE. 20)
FAST_CS_FB_
BASEDON_RI
M_SWITCH
(Switch for fast
CSFB based on
RIM) 1: This
switch is turned
on. The RNC
supports fast
CSFB(CS
fallback) based
on RIM. 0: This
switch is turned
off. The RNC
does not support
fast CSFB(CS
fallback) based
on RIM. 21)
L2U_SRVCC_
WITH_PS_HO
_SWITCH
Whether to
support LTE-to-
UMTS CS and
PS handovers
simultaneously.
1: This switch is
turned on. LTE-
to-UMTS CS
and PS
handovers can
happen
simultaneously.
0: This switch is
turned off. LTE-
to-UMTS CS
and PS
handovers
cannot happen
simultaneously.
22)
ULTRA_FLAS
H_CSFB_SWIT
CH(Ultra-Flash
CSFB Function
Switch)
Whether the
Ultra-Flash
CSFB function
takes effect. 1:
This switch is
turned on. The
RNC supports
the Ultra-Flash
CSFB function,
and the delay of
CSFB is
reduced,
improving user
experience. 0:
This switch is
turned off. The
RNC does not
support the
Ultra-Flash
CSFB function,
and the delay of
CSFB is long,
affecting user
experience. 23)
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
(Support RNC
PS Querying UE
IMEISV)
Whether the
RNC sends an
Identity Request
message to the
UE, requesting
the UE's
international
mobile station
equipment
identity and
software version
(IMEISV). 1:
This switch is set
to on. The RNC
sends an Identity
Request
message to the
UE, requesting
the UE's
IMEISV. 0: This
switch is set to
off. The RNC
does not send an
Identity Request
message to the
UE. If this
switch is
enabled together
with the
RNC_PS_QUE
RY_UE_IMEI_
SWITCH, the
RNC queries the
UE's IMEISV,
not IMEI.
Disuse
Statement:This
switch
USRPLN_PRO
RATION_SHA
RED_ALO will
be deleted from
later versions.
Although the
configuration
interface in this
version supports
delivery of the
setting of this
switch, the
system does not
use this switch.
Therefore, this
switch is not
recommended.
GUI Value
Range:LOAD_I
RAT_HO_RNC
_FILL_TL,
SEND_IDT_JU
DGE_IU_RESE
T,
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH,
RNC_CS_QUE
RY_UE_IMEI_
SWITCH,
RNC_PS_QUE
RY_UE_IMEI_
SWITCH,
FACH_DTCH_
CONGEST_P2
D,
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH,
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
,
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH,
RB_RECFG_U
SER_INACT_S
WITCH,
RRC_SCRI_N
ORM_REL_S
WITCH,
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH,
CU_OVERLAP
_DSCR_SWIT
CH,
TRB_RST_DS
CR_SWITCH,
RNC_FD_SCRI
_FORCE_REL_
SWITCH,
USRPLN_PRO
RATION_SHA
RED_ALO,
FP_IUUP_TRA
CE_SWITCH,
RNC_PCHR_O
UTPUT_CTRL
_SWITCH,
DTMF_SWITC
H,
FAST_CS_FB_
BASEDON_RI
M_SWITCH,
L2U_SRVCC_
WITH_PS_HO
_SWITCH,
ULTRA_FLAS
H_CSFB_SWIT
CH,
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
Unit:None
Actual Value
Range:LOAD_I
RAT_HO_RNC
_FILL_TL,
SEND_IDT_JU
DGE_IU_RESE
T,
RNC_RBRECF
G_DRD_FAIL_
ROLLBACK_S
WITCH,
RNC_CS_QUE
RY_UE_IMEI_
SWITCH,
RNC_PS_QUE
RY_UE_IMEI_
SWITCH,
FACH_DTCH_
CONGEST_P2
D,
RNC_RBSETU
P_DRD_FAIL_
ROLLBACK_S
WITCH,
PS_NOTIFYC
N_NOTDOWN
SIZE_SWITCH
,
ASU_RSP_TIM
EOUT_HAND
LE_SWITCH,
RB_RECFG_U
SER_INACT_S
WITCH,
RRC_SCRI_N
ORM_REL_S
WITCH,
CELLUPT_RL
FAILURE_SRB
REESTAB_SW
ITCH,
CU_OVERLAP
_DSCR_SWIT
CH,
TRB_RST_DS
CR_SWITCH,
RNC_FD_SCRI
_FORCE_REL_
SWITCH,
USRPLN_PRO
RATION_SHA
RED_ALO,
FP_IUUP_TRA
CE_SWITCH,
RNC_PCHR_O
UTPUT_CTRL
_SWITCH,
DTMF_SWITC
H,
FAST_CS_FB_
BASEDON_RI
M_SWITCH,
L2U_SRVCC_
WITH_PS_HO
_SWITCH,
ULTRA_FLAS
H_CSFB_SWIT
CH,
RNC_PS_QUE
RY_UE_IMEIS
V_SWITCH
Default
Value:LOAD_I
RAT_HO_RNC
_FILL_TL:
0,SEND_IDT_J
UDGE_IU_RE
SET:
0,RNC_RBREC
FG_DRD_FAIL
_ROLLBACK_
SWITCH:
1,RNC_CS_QU
ERY_UE_IMEI
_SWITCH:
0,RNC_PS_QU
ERY_UE_IMEI
_SWITCH:
0,FACH_DTC
H_CONGEST_
P2D:
0,RNC_RBSET
UP_DRD_FAIL
_ROLLBACK_
SWITCH:
0,PS_NOTIFY
CN_NOTDOW
NSIZE_SWITC
H:
0,ASU_RSP_TI
MEOUT_HAN
DLE_SWITCH:
0,RB_RECFG_
USER_INACT_
SWITCH:
0,RRC_SCRI_
NORM_REL_S
WITCH:
0,CELLUPT_R
LFAILURE_SR
BREESTAB_S
WITCH:
0,CU_OVERL
AP_DSCR_SW
ITCH:
0,TRB_RST_D
SCR_SWITCH:
0,RNC_FD_SC
RI_FORCE_RE
L_SWITCH:
0,USRPLN_PR
ORATION_SH
ARED_ALO:
0,FP_IUUP_TR
ACE_SWITCH:
1,RNC_PCHR_
OUTPUT_CTR
L_SWITCH:
1,DTMF_SWIT
CH:
1,FAST_CS_F
B_BASEDON_
RIM_SWITCH:
0,L2U_SRVCC
_WITH_PS_H
O_SWITCH:
0,ULTRA_FLA
SH_CSFB_SWI
TCH:
0,RNC_PS_QU
ERY_UE_IMEI
SV_SWITCH:0
8 Counters
9 Glossary
10 Reference Documents