Mimo (Ran19.1 01) PDF
Mimo (Ran19.1 01) PDF
Mimo (Ran19.1 01) PDF
Issue 01
Date 2017-09-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: [email protected]
Contents
2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 4
2.2 Benefits........................................................................................................................................................................... 4
8 Network Impact........................................................................................................................... 24
8.1 WRFD-010684 2x2 MIMO.......................................................................................................................................... 24
8.2 WRFD-010693 Downlink 64QAM+MIMO................................................................................................................ 24
8.3 WRFD-010704 Flexible HSPA+ Technology Selection.............................................................................................. 25
8.4 WRFD-010700 Performance Improvement of MIMO and HSDPA Co-carrier...........................................................25
9 Engineering Guidelines............................................................................................................. 26
9.1 WRFD-010684 2x2 MIMO.......................................................................................................................................... 26
9.1.1 When to Use 2x2 MIMO........................................................................................................................................... 26
9.1.2 Required Information................................................................................................................................................ 26
9.1.3 Planning..................................................................................................................................................................... 27
9.1.3.1 RF Planning............................................................................................................................................................ 27
9.1.3.2 Network Planning................................................................................................................................................... 27
9.1.3.3 Hardware Planning................................................................................................................................................. 27
9.1.4 Deployment............................................................................................................................................................... 29
9.1.4.1 Requirements.......................................................................................................................................................... 30
9.1.4.2 Precautions..............................................................................................................................................................31
9.1.4.3 Data Preparation and Feature Activation................................................................................................................31
9.1.4.3.1 Using MML Commands...................................................................................................................................... 31
9.1.4.3.2 MML Command Examples................................................................................................................................. 32
9.1.4.4 Activation Observation...........................................................................................................................................33
9.1.4.5 Deactivation............................................................................................................................................................34
9.1.4.5.1 Using MML Commands...................................................................................................................................... 34
9.1.4.5.2 MML Command Examples................................................................................................................................. 34
9.1.4.5.3 Using the CME.................................................................................................................................................... 34
9.1.5 Performance Monitoring............................................................................................................................................35
9.1.6 Parameter Optimization............................................................................................................................................. 36
9.1.7 Troubleshooting......................................................................................................................................................... 36
9.2 WRFD-010693 Downlink 64QAM+MIMO................................................................................................................ 36
9.2.1 When to Use Downlink 64QAM+MIMO................................................................................................................. 36
9.2.2 Required Information................................................................................................................................................ 36
9.2.3 Network Planning...................................................................................................................................................... 36
9.2.4 Deployment............................................................................................................................................................... 36
9.2.4.1 Requirements.......................................................................................................................................................... 37
9.2.4.2 Data Preparation and Feature Activation................................................................................................................38
9.2.4.2.1 Data Preparation.................................................................................................................................................. 38
9.2.4.2.2 Using MML Commands...................................................................................................................................... 39
9.2.4.2.3 MML Command Examples................................................................................................................................. 39
9.2.4.2.4 Using the CME.................................................................................................................................................... 40
10 Parameters................................................................................................................................... 55
11 Counters.................................................................................................................................... 115
12 Glossary..................................................................................................................................... 128
13 Reference Documents............................................................................................................. 129
1.1 Scope
This document describes multiple-input multiple-output (MIMO), including its technical
principles, related features, network impact, and engineering guidelines. This document
covers the following features:
NE NE Model
Micro BTS3911E
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
RAN19.1 01 (2017-09-30)
Compared with the Issue 02 (2016-10-30) of RAN18.1, Issue 01 (2017-09-30) of RAN19.1
includes the following changes.
Feature Add the description that 5900 macro base stations None
change support this feature.
2 Overview
2.1 Introduction
MIMO is an antenna technology for wireless communications in which multiple antennas are
used on both the transmitter and the receiver. MIMO can increase transmission rates through
spatial multiplexing and improve channel quality through space diversity without increasing
transmit power or bandwidth. The research of MIMO standard starts from 3GPP Release 5
and finalizes at 3GPP Release 7 with two standard solutions:
l PARC (Per-antenna rate control): The PARC solution evolves from the theory that the
number of open-loop MIMO links can reach the Shannon capacity limit. The PARC
solution applies to UTRA TDD.
l D-TxAA (Double Transmit antenna array): The D-TxAA solution uses the spatial
multiplexing technology to transmit multiple data flows. The D-TxAA solution applies
to UTRA FDD.
2.2 Benefits
l In the initial network deployment phase, MIMO and HSDPA both operate in the same
cell to fully utilize frequency resources and reduce network costs. If the frequency
resources are sufficient, you can set up cells capable of only MIMO to maximize the
advantages of the spatial diversity gains of MIMO. Specifically, MIMO improves the
channel quality without increasing the TX power or bandwidth.
l MIMO increases the single-user peak rate and the cell throughput.
On a NodeB, the MAC-ehs scheduling determines whether to transmit one or two transport
blocks (TBs) in a TTI. When two TBs are transmitted, the NodeB can simultaneously transmit
both primary (blue) and secondary (red) data flows. The primary data flow is always present,
but the presence of the secondary data flow depends on the channel environment.
First, the NodeB performs channel coding, scrambling, and spectrum spreading on TBs of the
primary data flow S1 and secondary data flow S2. Each TB is processed in the same way as
that in non-MIMO mode.
Then, the NodeB performs MIMO precoding on S1 and S2 to ensure the two data flows are in
good orthogonality to minimize interference. The precoding formula is as follows:
w1 to w4 indicate four precoding weights, which are provided by the NodeB and UE in
channel evaluation.
The UE evaluates the channel quality of each antenna based on the pilot signal. The pilot
transmission mode determines whether the two TX antennas transmit the same or different
pilot signals. For details, see 3.2 Pilot Transmit Mode.
The UE reports the precoding weights based on the quality of received pilot power. The
information containing the precoding weights is the precoding control indication (PCI). The
PCI and channel quality indicator (CQI) are included in the CQI field to the NodeB by the UE
over the HS-DPCCH. Based on the report, the NodeB decides whether to send one or two
TBs in a TTI and determines the size of transport resource blocks and the modulation mode of
each TB.
MIMO uses the same control channel as that when MIMO is not introduced, except that the
transmitted signalings are different. The format of transport signalings on the HS-SCCH and
HS-DPCCH are changed to process the additional information of MIMO.
l TB size of each data flow
l Modulation and coding scheme of each data flow
l CQI of each antenna
l Reported or used antenna precoding weights
l More signalings to the UE for dual-flow transmission
l More feedback information from the UE
MIMO optimized the frame structure on the HS-DPCCH, and the new structure is named HS-
SCCH type 3. For details, see 3.3 Radio Bearer. The messages transmitted over the Iub and
Uu interfaces are enhanced to transmit the MIMO-related information. For details, see 3.4
Enhanced Messages for MIMO.
HSPA+ uses 2x2 MIMO in the downlink to increase single-user throughput and system
capacity. The peak rate of 2x2 MIMO at the MAC layer can reach 28 Mbit/s.
To enable 2x2 MIMO, set HspaPlusSwitch (BSC6900, BSC6910) to MIMO and select
CFG_HSDPA_MIMO_SWITCH under the CfgSwitch (BSC6900, BSC6910) parameter.
To enable DC-HSDPA+MIMO, set DCMIMO_HSDPA under the HspaPlusSwitch
(BSC6900, BSC6910) parameter to ON.
3.2.1 Overview
In a MIMO-capable cell, UEs configured with MIMO require the pilot signal from the NodeB
for estimating the channel conditions between multiple RX antennas and multiple TX
antennas. The UE can estimate the channel conditions of each TX antenna in the following
two modes:
l Pilot transmit diversity mode
In pilot transmit diversity mode, the pilot signals are carried on the P-CPICH and are
transmitted through the two antenna ports. One antenna sends the modulation pattern of
antenna port 1 of the P-CPICH. The other antenna sends the modulation pattern of
antenna port 2 of the P-CPICH.
In Space Time Transmit Diversity (STTD) mode, the receiver that serves UEs performing
HSDPA services is changed from a frequency domain equalizer (FEQ) receiver to a rake
receiver, with deteriorated performance. Therefore, the PSP mode is recommended.
The STTD mode optimizes power allocation. Different from no-diversity cells, the total
power allocated to each channel in the pilot transmit diversity cells is the same. For example,
the TX power of a cell is 20 W, the power margin is 10% (2 W), the TX power on the P-
CPICH is 1 W, and the TX power on the CC H is 1 W. Figure 3-2 shows power allocation
between two antennas in pilot transmit diversity mode.
Figure 3-2 Power allocation between two antennas in pilot transmit diversity mode.
Run the RNC MML command ADD UCELLSETUP to enable a cell to support STTD and
set the transmit diversity mode of each channel in STTD mode. For the AICH, PICH, and S-
CCPCH, run the RNC MML commands ADD UAICH, ADD UPICH, and ADD
USCCPCHBASIC, respectively, with STTDInd (BSC6900, BSC6910) set to TRUE.
In PSP mode when both MIMO and HSDPA are enabled, the MIMO signals and pilot signals
carried on the S-CPICH might cause interference to HSDPA UEs that do not use MIMO,
increasing the performance loss. To reduce such performance loss, the intelligent interference
control (IIC) technique can be used. For detailed information about IIC, see section 5.4
Intelligent Interference Control.
The resource status indication procedure is initiated by the NodeB to report the status of
NodeB physical resources to the CRNC.
During the resource status indication procedure, if the local cell is MIMO-capable when it is
set up, the NodeB includes the "MIMO Capability" IE, which is set to MIMO Capable for
the local cell in the RESOURCE STATUS INDICATION message.
Audit Procedure
The audit procedure is initiated by the CRNC. In this procedure, the configuration and status
of the logical resources in the NodeB are audited, and for each MIMO-capable local cell, the
NodeB includes the MIMO Capability IE that is set to MIMO Capable in the AUDIT
RESPONSE message.
During the cell setup or reconfiguration procedure, if the MIMO Pilot Configuration IE is
included in the CELL SETUP REQUEST or CELL RECONFIGURATION REQUEST
message, then the parameters defining the pilot configuration for MIMO are stored in the
NodeB and applied when the MIMO mode is activated.
During the radio link setup procedure, if the MIMO Activation Indicator IE is included in the
HS-DSCH FDD Information IE in the RADIO LINK SETUP REQUEST message, then the
NodeB activates the MIMO mode for the HS-DSCH Radio Link. In addition, the NodeB
decides the UE reporting configuration (N/M ratio) for MIMO and includes the MIMO N/M
Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK SETUP
RESPONSE message. The HARQ Memory Partitioning Information Extension for MIMO IE
is also included in the RADIO LINK SETUP RESPONSE message.
The N/M ratio is used to indicate the reporting period of CQI type A or B.
In this procedure, the MIMO-related elements are the same as those in the radio link setup
procedure.
If these prerequisites are met, Transport format and resource combination (TFRC) checks the
traffic volume supported in dual-stream transmission mode and single-stream transmission
mode. If more data can be transmitted in dual-stream transmission mode, this mode is
configured.
In each TTI, the TFRC algorithm determines whether the conditions for using the dual-stream
transmission mode are met. If the conditions are met, dual-stream transmission is performed
in this TTI. Otherwise, single-stream transmission is performed in this TTI. For details about
TFRC, see HSDPA Feature Parameter Description.
4.1 Overview
To increase the downlink rate, the downlink 64QAM+MIMO technology is introduced in
3GPP R8. With this technology, the UE can use both the MIMO and 64 QAM to receive
HSDPA data. Theoretically, the downlink peak rate can reach 42 Mbit/s. The UE uses
downlink 64QAM in MIMO mode to increase the number of bits of each symbol, as shown in
Figure 4-1.
When setting up a PS streaming service or PS BE service, the UE can use Downlink MIMO
+64QAM if the following conditions are met:
l Both the network and the UE support Downlink MIMO, Downlink 64 QAM, Downlink
MIMO+64QAM, and Downlink Enhanced L2, and these features have been activated.
l The downlink HS-DSCH and uplink E-DCH/DCH serve as transmission channels.
l The HspaPlusSwitch (BSC6900, BSC6910) parameter is set to 64QAM_MIMO on the
RNC.
l The CfgSwitch (BSC6900, BSC6910) parameter is set to
CFG_MIMO_AND_64QAM_SWITCH on the RNC.
l The DL64QAMMIMO parameter is set to TRUE on the NodeB.
l The MIMO64QAMorDCHSDPASwitch (BSC6900, BSC6910) parameter is set to
MIMO_64QAM. Alternatively, DC-HSDPA is not activated.
In combined services, the bearer scheme is determined by the service with the highest rate.
For example, in VoIP and BE (384 kbit/s) combined services, if the VoIP service rate is lower
than 384 kbit/s, and the BE service uses MIMO, the combined service will use MIMO.
Table 4-1 CQI mapping table for downlink MIMO with 64QAM
HS-DSCH Category Used CQI Mapping Table
19 F J
20 G K
For details about the CQI mapping table, see 3GPP TS 25.214.
5.1 Overview
If the frequency resources are sufficient, cells dedicated for only MIMO users can be set up.
In the initial phase of network construction, MIMO and HSDPA both operate in the same cell
to save frequency resources and reduce network costs. Figure 5-1 shows the recommended
scenario of MIMO with HSDPA (MIMO+HSDPA).
As shown in Figure 5-1, assume that f1 serves an R99+HSDPA cell and f2 serves a MIMO
+HSDPA+R99 cell. The pilot transmit mode of f2 is PSP mode. The baseband output signals
of the two cells are transmitted after being mapped to two PAs through virtual antenna
mapping (VAM). MIMO Prime is also used to improve the UE receive quality.
With this networking, the signals of MIMO and secondary CPICH have an impact on non-
MIMO HSDPA UEs and may lead to performance loss. Huawei introduces the IIC technique
to reduce the performance loss of non-MIMO HSDPA UEs using equalization receivers.
In conclusion, Huawei adopts the PSP, VAM, MIMO Prime, and IIC techniques together to
improve the performance of a MIMO+HSDPA cell. Figure 5-2 illustrates how these
techniques work together as a whole.
The following sections describe VAM, MIMO Prime, and IIC. For details about PSP, see
section 3.2.3 Primary/Secondary Common Pilot (PSP).
The virtual antenna mapping (VAM) function is used to balance the transmit power of two
power amplifiers (PAs) and fully utilize the transmit power, and is mostly used when the cell
is in primary and secondary pilot (PSP) mode. Figure 5-3 shows the VAM principles.
Data of virtual antenna 1 (V1) and virtual antenna 2 (V2) are evenly distributed on two
physical antennas through the VAM conversion matrix, as shown in Figure 5-3. Therefore,
the transmit power must be balanced on two physical antennas.
The VAM conversion matrix is listed as follows:
The values of h1, h2, h3, and h4 are pre-defined. The P1 and P2 are roughly the same.
In MIMO+HSDPA cells, the V1 input data comes from MIMO, CCH, R99, and HSDPA, and
the V2 input data comes from MIMO.
When the cell supports MIMO and HSDPA co-carrier, it is recommended that MIMO Prime
be enabled when the following conditions are met:
l The license control items for MIMO and HSDPA co-carrier and MIMO Prime have been
activated.
l The VAM function has been enabled.
When the MIMOPRIMESW parameter is set to OPEN(open), MIMO Prime is enabled in
non-MIMO cells. This parameter does not need to be specified in MIMO cells.
For details, see MIMO Prime Feature Parameter Description.
When the PSP mode is used, signals transmitted from the secondary antenna cannot be
identified by HSDPA UEs. Therefore, the receiver of the legacy HSDPA UE does not
suppress the multipath interference caused by these signals. As a result, the performance of
legacy HSDPA services degrades. The IIC function intelligently monitors the proportion of
individual users in a cell and dynamically allocates the total available power to MIMO users
and HSDPA users. In this manner, the IIC function controls the interference of the signals
transmitted through the secondary antenna on the HSDPA signals without deteriorating the
HSDPA performance.
When IIC is applied, if the primary and secondary common pilots are allocated different
powers, the IIC performance may deteriorate. Therefore, it is recommended that the power of
primary and secondary common pilots be the same when applying IIC function. That is, it is
recommended that the parameter ScpichPower (BSC6900, BSC6910) be set to a value
between -5 and 150.
Whether the DC-HSDPA cells support MIMO depends on the cell configurations. DC-
HSDPA, MIMO, and the combination of the two features provide different benefits.
DC-HSDPA UEs have higher throughput in lightly-loaded cells while MIMO UEs have
higher throughput in heavily-loaded cells. Accordingly, Huawei introduced the dynamic
selection algorithm for DC-HSDPA and MIMO. The algorithm determines whether to use
DC-HSDPA or MIMO to set up new services based on the number of HSDPA UEs and
downlink load of the serving cell, thereby increasing throughput and improving user
experience.
This feature is controlled by CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH under the
CfgSwitch (BSC6900, BSC6910) parameter.
The DC-HSDPA and MIMO dynamic selection algorithm affects neither the original DRD
algorithm nor the HSPA+ technological satisfaction levels. The optimal technique is selected
only after the RNC selects an appropriate cell using the DRD algorithm and selects DC-
HSDPA or MIMO for the service.
NOTE
The selected cell must support DC-HSDPA and at least one cell in the DC-HSDPA cell group where the
selected cell belongs must support MIMO.
Figure 6-1 shows a two-carrier network where two cells form a DC-HSDPA cell group. If the
RNC selects cell 1 for new services by using the DRD algorithm and selects DC-HSDPA or
MIMO for the UEs, it also decides:
l If cell 1 supports MIMO, the downlink transmit power of cell 2 exceeds SecCellTcpThd
(BSC6900, BSC6910) and the number of HSDPA UEs in cell 2 exceeds
SecCellHUserNumThd (BSC6900, BSC6910), then the RNC selects cell 1 for new
services and selects MIMO for the UEs.
l If cell 2 supports MIMO, the downlink transmit power of cell 1 exceeds SecCellTcpThd
(BSC6900, BSC6910) and the number of HSDPA UEs in cell 1 exceeds
SecCellHUserNumThd (BSC6900, BSC6910), then the RNC selects cell 2 for new
services and selects MIMO for the UEs.
l Otherwise, the RNC directly selects DC-HSDPA for the UEs in cell 1.
If the RNC selects cell 1 for new services without using the DRD algorithm and selects
MIMO for the UEs, then the RNC decides:
l If cell 1 supports MIMO, the downlink transmit power of cell 2 exceeds SecCellTcpThd
(BSC6900, BSC6910) and the number of HSDPA UEs in cell 2 exceeds
SecCellHUserNumThd (BSC6900, BSC6910), then the RNC selects cell 1 for new
services and selects MIMO for the UEs.
l Otherwise, the RNC directly selects DC-HSDPA for the UEs in cell 1.
NOTE
In cells served by primary and secondary carriers, the number of HSDPA UEs are the total number of
DC-HSDPA and non-DC-HSDPA UEs.
Gains introduced by this feature vary according to the UE distribution and penetration rate.
l This feature introduces significant gains if most UEs in a cell are likely to locate near to
the cell center. Otherwise, this feature cannot introduce noticeable gains.
l Gains introduced by this feature increase with the penetration rate of UEs capable of this
feature. If the UE penetration rate is low, this feature cannot introduce noticeable gains.
If the load on DCHs of the two DC-HSDPA carriers is high, for example, constantly higher
than 40%, this feature should be disabled. If this feature is enabled when the load is high, the
throughput will be affected.
7 Related Features
Impacted Features
Feature Function Description
ID Name
N/A HS-DPCCH If the UE is not configured with MIMO, only one data
flow on the HS-DPCCH contains the ACK/NACK and
CQI information.
If the UE is configured with MIMO, the precoding on the
HS-DPCCH is different. Specifically, one or two data
flows must contain the ACK/NACK, PCI, and CQI
information.
Impacted Features
Feature Function Description
ID Name
N/A HS-SCCH Less When MIMO+64QAM and HS-SCCH Less Operation are
Operation simultaneously enabled, the DL MIMO+64QAM feature
preferentially takes effect.
Impacted Features
None.
Impacted Features
None.
8 Network Impact
Network Performance
With Closed Loop Transmitting Diversity (CLTD), 2x2 MIMO can increase the data rates of
UEs at the cell edge and therefore extend coverage of the cell.
However, 2x2 MIMO also increases the digital signal processor (DSP) load of the NodeB.
HS-DPCCH data processing of dual-stream MIMO increases the DSP load. The DSP load
significantly increases when HS-DPCCH is established on the WBBPe board.
Compared with WRFD-010683 Downlink 64QAM, this feature has the same impact on the
system capacity as WRFD-010684 2x2 MIMO. For details, see System Capacity.
Network Performance
Compared with WRFD-010684 2x2 MIMO, this feature has no impact on the network
performance.
Compared with WRFD-010683 Downlink 64QAM, this feature has the same impact on the
network performance as WRFD-010684 2x2 MIMO. For details, see Network Performance.
Network Performance
No impact.
Network Performance
If an MIMO carrier uses VAM but a non-MIMO carrier does not use VAM, the success rate of
DRDs between a cell using the MIMO carrier and a cell using the non-MIMO carrier is low.
This problem can be solved by turning on the DRD rollback switch. To turn on the
DRDrollback switch, run the SET URRCTRLSWITCH command with the
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWITCH and
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITCH check boxes under the
PROCESSSWITCH2 (BSC6900, BSC6910) parameter selected.
9 Engineering Guidelines
Counters NE Description
9.1.3 Planning
9.1.3.1 RF Planning
An RF module supporting two transmit channels supports 2x2 MIMO. If an RF module
supports only one transmit channel, two RF modules must be interconnected to support 2x2
MIMO. An RRU3801C (20 W) must be interconnected with another RRU3801C (20 W) to
support 2x2 MIMO.
The transmit power for MIMO is planned as follows: For an existing network, if a carrier is
changed from a non-MIMO carrier to an MIMO carrier, the transmit power must remain
unchanged (For example, if the transmit power of a non-MIMO carrier is 20 W, the transmit
power for an MIMO carrier is 2x10 W). For new networks, MIMO carriers and non-MIMO
carriers are the same in their power specifications, with 40 W recommended.
Figure 9-1 Example of the hardware configuration of a NodeB that is enabled with 2x2
downlink MIMO (1)
Figure 9-2 Example of the hardware configuration of a NodeB that is enabled with 2x2
downlink MIMO (2)
It is recommended that that the same type of RRU, the same length of feeders, and the same
length of jumpers be used to reduce delay difference between two RF channels. Different
types of RRUs can be used if the delay difference between two RF channels is lower than 1/8
chip.
If both dual-polarized antennas and single-polarized antennas can be used, dual-polarized
antennas are recommended to reduce the difficulty in hardware installation. If single-
polarized antennas must be used, the two single-polarized antennas must be mounted
vertically to each other and a certain distance must be reserved between them to keep
channels irrelevant to each other. Theoretically, the channels of two antennas are irrelevant to
each other if the distance between the two antennas is greater than half wavelength. However,
using two independent antennas may compromise coverage performance.
9.1.4 Deployment
9.1.4.1 Requirements
Other Features
l For details, see 7.1 WRFD-010684 2x2 MIMO.
l MAC-ehs, a sub-function of Downlink Enhanced L2, is responsible for scheduling and
TFRC selection for MIMO users.
Hardware
l 3900 series macro base stations must be configured with the UBBP, WBBPb, WBBPd,
or WBBPf board.
l 5900 series macro base stations must be configured with the UBBP board.
l Two RF modules must be interconnected to support 2x2 MIMO when a Huawei-
delivered RF module supports only one transmit channel.
l An RRU3801C (20 W) must be interconnected with another RRU3801C (20 W) to
support 2x2 MIMO.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the License Allocation for Multiple
Operators parameter.
Method 2: Some license control items, for example, UL CE Num, can be allocated to both the
common group and private groups. In this case, the licensed values specified by the private
group are preferentially used, and the licensed value specified by the common group is used
on a first-come, first-served basis. For NodeB license allocation in multi-operator scenarios,
see License Management Feature Parameter Description.
Other Requirements
l The UE is of category 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 30 or 32, as specified by the
3GPP protocols.
l For details about the hardware deployment related to MIMO, see "2x2 MIMO
Configuration" in NodeB Technical Description.
l To support the peak rate of 28 Mbit/s in downlink MIMO mode, the CN needs to comply
with 3GPP Release 7. The CN that complies with 3GPP Release 6 supports 8 Mbit/s in
the uplink and 16 Mbit/s in the downlink.
9.1.4.2 Precautions
Before enabling this feature in an activated cell, you need to:
l Deactivate the cell. This will interrupt services in the cell. Therefore, enable the feature
when the traffic of the cell is light.
l Ensure that there are sufficient baseband resources on the baseband processing board.
Otherwise, this feature cannot be activated.
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.
Step 2 Run the RNC MML command SET UFRC to set common parameters among the
fundamental resource configuration (FRC) parameters. In this step, set Preferred MIMO or
64QAM character to MIMO.
NOTE
l MIMO and 64QAM cannot be enabled together for UEs of 3GPP R7.
l If Preferred MIMO or 64QAM character is set to MIMO, MIMO is preferentially configured for
the UE.
l Before verifying the feature, set Preferred MIMO or 64QAM character to MIMO. After the
verification, set this parameter to a proper value according to the network plan.
Step 3 (Optional) Run the RNC MML command SET UFRC to set common parameters among the
fundamental resource configuration (FRC) parameters. In this step, set HSPA Technologies
Retried by UEs to MIMO.
Step 4 Run the RNC MML command MOD UCELLALGOSWITCH turn on the cell-level MIMO
switch and Downlink Enhanced L2 switch. In this step, set Cell Hspa Plus function switch
to MIMO, DL_L2ENHANCED(Cell DL L2ENHANCED Function Switch), and
UL_L2ENHANCED(Cell UL L2ENHANCED Function Switch).
Step 5 Run the RNC MML command DEA UCELL to deactivate the cell.
Step 6 Configure the related data on the NodeB and add sectors according to the MIMO hardware
configuration scheme. For details, see NodeB Technical Description. The following procedure
takes the RRU3804 as an example to describe how to configure data for the change from one
RRU3804 to two cascading RRU3804s.
1. Optional: Run the NodeB MML command ADD RRUCHAIN to create an RRU chain.
2. Run the NodeB MML command ADD RRU to add an RRU to the chain.
NOTE
Step 7 On the NodeB, remove the old local cell and establish a new local cell.
Run the NodeB MML command MOD ULOCELL to modify the local cell. In this step, set
both Support VAM and Two Tx Way to TRUE(TRUE).
Step 9 Run the RNC MML command ACT UCELL to activate the cell.
Step 10 Run the RNC MML command ACT UCELLMIMO to activate the MIMO-related parameter
settings.
----End
2. Use the UE to establish an HSDPA service. Check whether the value of the information
element (IE) dl-TransportChannelType in rb-MappingInfo of the RRC_RB_SETUP
message is hsdsch.
3. In the traced Uu interface data, check whether the RRC_RB_SETUP message contains
the IE mimoParameters.
– If the RRC_RB_SETUP message contains the IE mimoParameters, as shown in
Figure 9-4, this feature has been activated.
– If the RRC_RB_SETUP message does not contain the IE mimoParameters, this
feature is not activated.
9.1.4.5 Deactivation
Step 2 Run the RNC MML command DEA UCELLMIMO to deactivate the MIMO-related
parameter settings.
Step 3 On the NodeB, remove the old local cell and establish a new local cell.
1. Run the NodeB MML command MOD ULOCELL to modify the local cell.
2. In this step, set both Support VAM and Two Tx Way to FALSE(FALSE).
Step 4 Disable the PSP function on the RNC side.
Run the RNC MML command RMV USCPICH to remove a secondary common pilot
channel (SCPICH).
Step 5 Run the RNC MML command MOD UCELLALGOSWITCH. In this step, deselect
MIMO(Cell MIMO Function Switch) under HspaPlusSwitch.
Step 6 Run the RNC MML command ACT UCELL to activate the cell.
----End
When configuring the 2x2 MIMO 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.
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
Counter NE Description
9.1.7 Troubleshooting
If both MIMO and HSDPA are enabled on a network and the benefits obtained by the UE do
not meet expectations, check the following items:
If the problem persists, check the ratio of MIMO UEs to non-MIMO UEs and the scheduling
ratio of MIMO single streams to MIMO dual streams.
9.2.4 Deployment
This section describes how to activate, verify, and deactivate the optional feature
WRFD-010693 Downlink 64QAM+MIMO.
9.2.4.1 Requirements
Other Features
For details, see 7.1 WRFD-010684 2x2 MIMO.
Hardware
MIMO requires two transmit channels. When RRUs with a single transmit channel are used,
for example, the RRU3804, two RRUs must be interconnected to support MIMO. When
RRUs with two transmit channels are used, for example, the RRU3808, only one RRU is
required.
3900 series macro base stations must be configured with the UBBP, WBBPb, WBBPd, or
WBBPf board.
5900 series macro base stations must be configured with the UBBP board.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the License Allocation for Multiple
Operators parameter.
Method 2: Some license control items, for example, UL CE Num, can be allocated to both the
common group and private groups. In this case, the licensed values specified by the private
group are preferentially used, and the licensed value specified by the common group is used
on a first-come, first-served basis. For NodeB license allocation in multi-operator scenarios,
see License Management Feature Parameter Description.
Other Requirements
The UE must belong to HS-DSCH category 19, 20, 27, 28, or later.
l Before feature verification, perform step 3. If the preferred technology planned for a cell is not
64QAM+MIMO, restore the configuration based on the network plan after feature verification.
l Before enabling periodic DRD for downlink 64QAM+MIMO, enable periodic DRD for other
features on which this feature depends. That is, select the 64QAM and MIMO check boxes under
the HSPA Technologies Retried by UEs parameter.
Step 4 Run the RNC MML command MOD UCELLALGOSWITCH to turn on the cell-level
64QAM+MIMO switch. In this step, select 64QAM_MIMO(Cell 64QAM+MIMO
Function Switch) under the Cell HSPA+ function switch parameter.
----End
CfgSwitch=CFG_HSDPA_64QAM_SWITCH-1&CFG_HSDPA_MIMO_SWITCH-1&CFG_HSDPA_MIMO_WITH_64Q
AM_SWITCH-1;
SET UFRC: RetryCapability=MIMO_64QAM-1, MIMO64QAMorDCHSDPASwitch=MIMO_64QAM;
MOD UCELLALGOSWITCH: CellId=1,
HspaPlusSwitch=64QAM-1&MIMO-1&DL_L2ENHANCED-1&64QAM_MIMO-1;
NOTE
When configuring the 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 listed in the table in "Data Preparation" section from top to bottom on the
CME. 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 while running the wizard to obtain online help.
To check whether a parameter supports batch modification, see the Remarks column in the
table in "Data Preparation" section.
----End
9.2.4.4 Deactivation
Parameter Name Parameter ID Setting Notes Remarks
----End
9.2.7 Troubleshooting
For details, see 9.1.7 Troubleshooting.
If there is more than one carrier, configure carriers to support MIMO or HSDPA on a per
carrier basis. This reduces the impact on the performance of HSDPA UEs and maximizes
MIMO benefits. The MIMO and HSDPA co-carrier configuration can be enabled on other
carriers if the number of MIMO UEs increases.
9.3.4 Deployment
9.3.4.1 Requirements
Other Features
l WRFD-010610 HSDPA Introduction Package
l WRFD-010685 Downlink Enhanced L2
l WRFD-010684 2x2 MIMO
l WRFD-010680 HSPA+ Downlink 28Mbps per User
Hardware
l The DBS3900 and BTS3900/BTS3900A must be configured with the WBBPb, WBBPd,
or WBBPf board.
l All radio frequency modules support this feature except 20W RRU3801Cs, 8U WRFUs,
MTRUs, , and RF modules (GSM only).
l The RRU3908 V2 module and MRFU V2 module of RAN14.0 support this feature.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the License Allocation for Multiple
Operators parameter.
Method 2: Some license control items, for example, UL CE Num, can be allocated to both the
common group and private groups. In this case, the licensed values specified by the private
group are preferentially used, and the licensed value specified by the common group is used
on a first-come, first-served basis. For NodeB license allocation in multi-operator scenarios,
see License Management Feature Parameter Description.
Other Requirements
The UE is of category 15, 16, 17, 18, 19, 20, 25, 26, 27, 28, 30 or 32, as specified by the
3GPP protocols.
9.3.4.2 Precautions
Before enabling the feature in an existing cell, you need to deactivate the cell. This, however,
will interrupt services in the cell. Therefore, you should enable the feature when the traffic of
the cell is light.
Enabling this feature will make a cell become unavailable if the RRU carrying the cell meets
the following condition: TT is set to RING and BM is set to HOT in the RRUCHAIN
configuration.
Step 2 Add RRUs and sectors. For details about how to add RRUs and sectors, see NodeB Technical
Description.
Step 3 On the NodeB, remove the old local cell and establish a new local cell.
1. Run the NodeB MML command MOD ULOCELL to modify the local cell. In this step,
set Support VAM, Two Tx Way, and Precoding Weight Set Restriction Switch to
TRUE(TRUE).
Step 4 Run the NodeB MML command SET ULOCELLMACHSPARA. In this step, set IIC
Switch to OPEN(open).
Step 5 Configure the PSP function on the RNC side.
1. Run the RNC MML command MOD UCELLSETUP to modify the cell basic
information. In this step, set TX Diversity Indication to FALSE.
2. Run the RNC MML command ADD USCPICH to add a secondary common pilot
channel (SCPICH).
Step 6 Run the RNC MML command ACT UCELL to activate the cell. In this step, set Validation
indication to Activated.
----End
When configuring the Performance Improvement of MIMO and HSDPA Co-carrier 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 according to the operation sequence in Table 9-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
9.3.4.5 Deactivation
Step 2 On the NodeB, remove the old local cell and establish a new local cell.
Run the NodeB MML command MOD ULOCELL to modify the local cell. In this step, set
both Support VAM and Two Tx Way to FALSE(FALSE).
Step 3 Run the NodeB MML command SET ULOCELLMACHSPARA to disable the IIC
algorithm. In this step, set IIC Switch to CLOSE(close).
Step 4 Disable the PSP function on the RNC side.
Run the RNC MML command RMV USCPICH to remove a secondary common pilot
channel (SCPICH).
Step 5 Run the RNC MML command ACT UCELL to activate the cell. In this step, set Validation
indication to Activated.
----End
When configuring the Performance Improvement of MIMO and HSDPA Co-carrier 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.
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
9.3.7 Troubleshooting
For details, see 9.1.7 Troubleshooting.
9.4.4 Deployment
9.4.4.1 Requirements
Other Features
For details, see 7.3 WRFD-010704 Flexible HSPA+ Technology Selection.
Hardware
3900 series macro base stations must be configured with the UBBP, WBBPb, WBBPd, or
WBBPf board.
5900 series macro base stations must be configured with the UBBP board.
License
For details about how to activate the license, see License Management Feature Parameter
Description.
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary and
secondary operators according to the value of the License Allocation for Multiple
Operators parameter.
Other Requirements
The UE has the HSDPA category 25 or higher capability, including HSDPA category 25, 26,
27, and 28.
9.4.4.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.
NOTE
When configuring the 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 listed in the table in "Data Preparation" section from top to bottom on the
CME. 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 while running the wizard to obtain online help.
To check whether a parameter supports batch modification, see the Remarks column in the
table in "Data Preparation" section.
----End
Expected result: As shown in Figure 9-5, the RRC_RB_SETUP message in the Uu tracing
result contains the mimoParameters IE when the downlink power of the secondary cell
covered by the DC carrier group is greater than or equal to DL TX Power Threshold of
Secondary Cell set in Step 1 and the number of HSDPA users is greater than or equal to
Threshold of HSDPA Users in Secondary Cell set in Step 1. The RRC_RB_SETUP
message in the Uu tracing result contains the dl-SecondaryCellInfoFDD IE (as shown in
Figure Figure 9-6) when the downlink power of the secondary cell covered by the DC carrier
group is smaller than DL TX Power Threshold of Secondary Cell set in Step 1 and the
number of HSDPA users is smaller than Threshold of HSDPA Users in Secondary Cell set
in Step 1.
9.4.4.5 Deactivation
Parameter Parameter Setting Notes Remarks
Name ID
9.4.7 Troubleshooting
For details, see 9.1.7 Troubleshooting.
10 Parameters
Streami
ng QoS
Class
Combin
ation of
One CS
Service
and
Three
PS
Services
Combin
ation of
Four PS
Services
Uplink
Control
Channel
OLPC
Physical
Channel
Manage
ment
4C-
HSDPA
DB-
HSDPA
+MIMO
Flexible
Dual
Carrier
HSDPA
MC-
HSDPA
+MIMO
Logical
Channel
Manage
ment
DB-
HSDPA
Multiple
RAB
Packag
e(PS
RAB >=
2)
Streami
ng
Traffic
Class on
HSUPA
Streami
ng
Traffic
Class on
HSDPA
WRFD- Two PS 14. DC_HSUPA: When this switch is turned on, the
0106090 Services DC-HSUPA function can be enabled for HSUPA
2 3C- services.
WRFD- HSDPA 15. HSDPA_4C_MIMO: Whether the MC-HSDPA
010702 Interacti +MIMO feature is allowed for HSDPA services.
WRFD- ve and When this switch is turned on, the MC-HSDPA
010701 Backgro +MIMO (3C-HSDPA+MIMO and 4C-HSDPA
und +MIMO) feature is allowed for HSDPA services.
WRFD-
Traffic 16. HSDPA_4C: Whether the 3C-HSDPA or 4C-
010609
Class on HSDPA feature is allowed for HSDPA services. When
WRFD- HSDPA this switch is turned on, the 3C-HSDPA or 4C-
010510 HSDPA feature is allowed for HSDPA services.
Interacti
WRFD- ve and 17. DBMIMO_HSDPA: Whether the DB-HSDPA
010688 Backgro +MIMO feature is allowed for HSDPA services.
WRFD- und When this switch is turned on, the DB-HSDPA
010686 Traffic +MIMO feature is allowed for HSDPA services.This
Class on switch does not take effect for the inter-NodeB DB-
WRFD-
HSUPA HSDPA feature.
010687
DC- 18. DB_HSDPA: Whether the DB-HSDPA feature is
WRFD-
HSUPA allowed for HSDPA services. When this switch is
010684
Combin turned on, the DB-HSDPA feature is allowed for
WRFD- ation of HSDPA services, This switch does not take effect for
010685 Two CS the inter-NodeB DB-HSDPA feature.
WRFD- Services 19. HSDPA_SFDC(HSDPA_SFDC): Whether a cell
010683 (Except supports the SFDC HSDPA function. When this
WRFD- for Two switch is set to ON, the cell supports the SFDC
021000 AMR HSDPA function. This switch is reserved for the MF-
Speech HSDPA(multiflow HSDPA) function and cannot be
WRFD-
Services used in the current version.
010503
)
WRFD- 20. HSDPA_DF3C(HSDPA_DF3C): Whether a cell
Combin supports the DF3C HSDPA function. When this
0106150 ation of
2 switch is set to ON, the cell supports the DF3C
Two CS HSDPA function. This switch is reserved for the MF-
WRFD- Services HSDPA(multiflow HSDPA) function and cannot be
0106150 and One used in the current version.
3 PS
Service 21. INTERNBDB_HSDPA: Whether the Inter-NodeB
WRFD- DB-HSDPA feature is allowed for HSDPA services.
010502 (Except
for Two When this switch is turned on, the Inter-NodeB DB-
WRFD- AMR HSDPA feature is allowed for HSDPA services.
0106150 Speech 22. FDPCH_CAPABILITY_INVALID: Whether to
4 Services disable the FDPCH capability for a cell. When this
WRFD- ) switch is turned on, the cell does not have FDPCH
0106150 Combin capability. When this switch is turned off, the cell has
5 ation of FDPCH capability if the cell supports the FDPCH.
WRFD- One CS GUI Value Range: 64QAM(Cell 64QAM Function
170203 Service Switch), MIMO(Cell MIMO Function Switch),
2x2
MIMO
Downlin
k
Enhance
d L2
Downlin
k
64QAM
Transpo
rt
Channel
Manage
ment
Interacti
ve QoS
Class
Combin
ation of
One CS
Service
and Two
PS
Services
Combin
ation of
Three
PS
Services
Streami
ng QoS
Class
Combin
ation of
One CS
Service
and
Three
PS
Services
Combin
ation of
Four PS
Services
Uplink
Control
Channel
OLPC
Physical
Channel
Manage
ment
4C-
HSDPA
DB-
HSDPA
+MIMO
Flexible
Dual
Carrier
HSDPA
MC-
HSDPA
+MIMO
Logical
Channel
Manage
ment
DB-
HSDPA
Multiple
RAB
Packag
e(PS
RAB >=
2)
Streami
ng
Traffic
Class on
HSUPA
Streami
ng
Traffic
Class on
HSDPA
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,
CFG_HSUPA_DC_SWITCH,
CFG_HSDPA_4C_MIMO_SWITCH,
CFG_HSDPA_4C_SWITCH,
CFG_HSDPA_DBMIMO_SWITCH,
CFG_HSDPA_DB_SWITCH,
CFG_RCS_E_SWITCH,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH, CFG_HSDPA_SFDC_SWITCH,
CFG_HSDPA_DF3C_SWITCH,
CFG_SRB_BICASTING_SWTICH
Unit: None
Actual Value Range:
CFG_DL_BLIND_DETECTION_SWITCH,
CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_MIMO_SWITCH,
CFG_HSPA_DTX_DRX_SWITCH,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH,
CFG_IMS_SUPPORT_SWITCH,
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
H, CFG_LOSSLESS_RELOC_CFG_SWITCH,
CFG_MULTI_RAB_SWITCH,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,
CFG_PDCP_RFC2507_HC_SWITCH,
CFG_PDCP_RFC3095_HC_SWITCH,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,
CFG_HSDPA_DC_SWITCH,
CFG_HSUPA_16QAM_SWITCH,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,
CFG_PTT_SWITCH,
CFG_EDPCCH_BOOSTING_SWITCH,
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,
CFG_HSUPA_DC_SWITCH,
CFG_HSDPA_4C_MIMO_SWITCH,
CFG_HSDPA_4C_SWITCH,
CFG_HSDPA_DBMIMO_SWITCH,
CFG_HSDPA_DB_SWITCH,
CFG_RCS_E_SWITCH,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH, CFG_HSDPA_SFDC_SWITCH,
CFG_HSDPA_DF3C_SWITCH,
CFG_SRB_BICASTING_SWTICH
Default Value:
CFG_DL_BLIND_DETECTION_SWITCH:1,
CFG_HSDPA_64QAM_SWITCH:1,
CFG_HSDPA_MIMO_SWITCH:1,
CFG_HSPA_DTX_DRX_SWITCH:0,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH:0,
CFG_IMS_SUPPORT_SWITCH:1,
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
H:0, CFG_LOSSLESS_RELOC_CFG_SWITCH:0,
CFG_MULTI_RAB_SWITCH:1,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:0,
CFG_PDCP_RFC2507_HC_SWITCH:0,
CFG_PDCP_RFC3095_HC_SWITCH:0,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:0,
CFG_HSDPA_DC_SWITCH:0,
CFG_HSUPA_16QAM_SWITCH:0,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:0,
CFG_PTT_SWITCH:0,
CFG_EDPCCH_BOOSTING_SWITCH:0,
CFG_HSDPA_DCMIMO_SWITCH:0,
CFG_FREE_USER_SWITCH:0,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
0, CFG_HSUPA_DC_SWITCH:0,
CFG_HSDPA_4C_MIMO_SWITCH:0,
CFG_HSDPA_4C_SWITCH:0,
CFG_HSDPA_DBMIMO_SWITCH:0,
CFG_HSDPA_DB_SWITCH:0,
CFG_RCS_E_SWITCH:0,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH:0,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH:0, CFG_HSDPA_SFDC_SWITCH:0,
CFG_HSDPA_DF3C_SWITCH:0,
CFG_SRB_BICASTING_SWTICH:0
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,
CFG_HSUPA_DC_SWITCH,
CFG_HSDPA_4C_MIMO_SWITCH,
CFG_HSDPA_4C_SWITCH,
CFG_HSDPA_DBMIMO_SWITCH,
CFG_HSDPA_DB_SWITCH,
CFG_RCS_E_SWITCH,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH, CFG_HSDPA_SFDC_SWITCH,
CFG_HSDPA_DF3C_SWITCH,
CFG_SRB_BICASTING_SWTICH
Unit: None
Actual Value Range:
CFG_DL_BLIND_DETECTION_SWITCH,
CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_MIMO_SWITCH,
CFG_HSPA_DTX_DRX_SWITCH,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH,
CFG_IMS_SUPPORT_SWITCH,
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
H, CFG_LOSSLESS_RELOC_CFG_SWITCH,
CFG_MULTI_RAB_SWITCH,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,
CFG_PDCP_RFC2507_HC_SWITCH,
CFG_PDCP_RFC3095_HC_SWITCH,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,
CFG_HSDPA_DC_SWITCH,
CFG_HSUPA_16QAM_SWITCH,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,
CFG_PTT_SWITCH,
CFG_EDPCCH_BOOSTING_SWITCH,
CFG_HSDPA_DCMIMO_SWITCH,
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,
CFG_HSUPA_DC_SWITCH,
CFG_HSDPA_4C_MIMO_SWITCH,
CFG_HSDPA_4C_SWITCH,
CFG_HSDPA_DBMIMO_SWITCH,
CFG_HSDPA_DB_SWITCH,
CFG_RCS_E_SWITCH,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH, CFG_HSDPA_SFDC_SWITCH,
CFG_HSDPA_DF3C_SWITCH,
CFG_SRB_BICASTING_SWTICH
Default Value:
CFG_DL_BLIND_DETECTION_SWITCH:1,
CFG_HSDPA_64QAM_SWITCH:1,
CFG_HSDPA_MIMO_SWITCH:1,
CFG_HSPA_DTX_DRX_SWITCH:0,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH:0,
CFG_IMS_SUPPORT_SWITCH:1,
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
H:0, CFG_LOSSLESS_RELOC_CFG_SWITCH:0,
CFG_MULTI_RAB_SWITCH:1,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:0,
CFG_PDCP_RFC2507_HC_SWITCH:0,
CFG_PDCP_RFC3095_HC_SWITCH:0,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:0,
CFG_HSDPA_DC_SWITCH:0,
CFG_HSUPA_16QAM_SWITCH:0,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:0,
CFG_PTT_SWITCH:0,
CFG_EDPCCH_BOOSTING_SWITCH:0,
CFG_HSDPA_DCMIMO_SWITCH:0,
CFG_FREE_USER_SWITCH:0,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
0, CFG_HSUPA_DC_SWITCH:0,
CFG_HSDPA_4C_MIMO_SWITCH:0,
CFG_HSDPA_4C_SWITCH:0,
CFG_HSDPA_DBMIMO_SWITCH:0,
CFG_HSDPA_DB_SWITCH:0,
CFG_RCS_E_SWITCH:0,
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SWI
TCH:0,
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH:0, CFG_HSDPA_SFDC_SWITCH:0,
CFG_HSDPA_DF3C_SWITCH:0,
CFG_SRB_BICASTING_SWTICH:0
STTDIn BSC690 ADD WRFD- Transmi Meaning: This parameter indicates whether the
d 0 USCCP 010203 t SCCPCH shall use STTD or not. For detailed
CHBAS WRFD- Diversit information of this parameter, see 3GPP 25.346.
IC 010684 y GUI Value Range: TRUE, FALSE
MOD WRFD- 2x2 Unit: None
USCCP 010704 MIMO
CH Actual Value Range: TRUE, FALSE
WRFD- Flexible
HSPA+ Default Value: False
022000
Technol
WRFD- ogy
010700 Selectio
n
Physical
Channel
Manage
ment
Perform
ace
Improve
ment of
MIMO
and
HSDPA
Co-
carrier
STTDIn BSC691 ADD WRFD- Transmi Meaning: This parameter indicates whether the
d 0 USCCP 010203 t SCCPCH shall use STTD or not. For detailed
CHBAS WRFD- Diversit information of this parameter, see 3GPP 25.346.
IC 010684 y GUI Value Range: TRUE, FALSE
MOD WRFD- 2x2 Unit: None
USCCP 010704 MIMO
CH Actual Value Range: TRUE, FALSE
WRFD- Flexible
HSPA+ Default Value: False
022000
Technol
WRFD- ogy
010700 Selectio
n
Physical
Channel
Manage
ment
Perform
ace
Improve
ment of
MIMO
and
HSDPA
Co-
carrier
MIMO6 BSC690 SET WRFD- DRD Meaning: This switch is used to configure the priority
4QAMo 0 UFRC 020400 Introduc of MIMO_64QAM or DC-HSDPA. According to
rDCHS WRFD- tion different protocols, the following situations may
DPASwi 151209 Package occur: MIMO and DC-HSDPA cannot be used
tch Macro- together; both 64QAM and DC-HSDPA are
WRFD- supported, but cannot be used together. In this case,
010696 Micro
DC- "MIMO64QAMorDCHSDPASwitch" is used to
HSDPA configure the priorities of the features. When the
priority of MIMO is higher than that of DC-HSDPA,
DC- the priority of 64QAM is higher than that of DC-
HSDPA HSDPA. When the priority of DC-HSDPA is higher
than that of MIMO, the priority of DC-HSDPA is
higher than that of 64QAM.
GUI Value Range: MIMO_64QAM, DC_HSDPA
Unit: None
Actual Value Range: MIMO_64QAM, DC_HSDPA
Default Value: DC_HSDPA
MIMO6 BSC691 SET WRFD- DRD Meaning: This switch is used to configure the priority
4QAMo 0 UFRC 020400 Introduc of MIMO_64QAM or DC-HSDPA. According to
rDCHS WRFD- tion different protocols, the following situations may
DPASwi 151209 Package occur: MIMO and DC-HSDPA cannot be used
tch Macro- together; both 64QAM and DC-HSDPA are
WRFD- supported, but cannot be used together. In this case,
010696 Micro
DC- "MIMO64QAMorDCHSDPASwitch" is used to
HSDPA configure the priorities of the features. When the
priority of MIMO is higher than that of DC-HSDPA,
DC- the priority of 64QAM is higher than that of DC-
HSDPA HSDPA. When the priority of DC-HSDPA is higher
than that of MIMO, the priority of DC-HSDPA is
higher than that of 64QAM.
GUI Value Range: MIMO_64QAM, DC_HSDPA
Unit: None
Actual Value Range: MIMO_64QAM, DC_HSDPA
Default Value: DC_HSDPA
VAM BTS390 ADD WRFD- Perform Meaning: Indicates the local cell Support Virtual
0, ULOCE 010700 ance Antenna Mapping(VAM).
BTS390 LL WRFD- Improve GUI Value Range: FALSE(FALSE), TRUE(TRUE)
0 MOD 030011 ment of
WCDM MIMO Unit: None
ULOCE WRFD-
A, LL and Actual Value Range: FALSE, TRUE
BTS590 010684 HSDPA
LST Default Value: FALSE(FALSE)
0, Co-
BTS590 ULOCE carrier
0 LL
MIMO
WCDM Prime
A
2×2
MIMO
MIMOP BTS390 SET WRFD- MIMO Meaning: Indicates the MIMO Prime Switch. The
RIMES 0, ULOCE 030011 Prime function will be enabled if this parameter is set to
W BTS390 LLMAC OPEN.
0 HSPAR GUI Value Range: OPEN(open), CLOSE(close)
WCDM A
A, Unit: None
LST
BTS590 ULOCE Actual Value Range: OPEN, CLOSE
0, LLMAC Default Value: CLOSE(close)
BTS590 HSPAR
0 A
WCDM
A
IICSW BTS390 SET WRFD- Perform Meaning: Indicates the Intelligent Interference Control
0, ULOCE 010700 ance Switch. The function will be enabled if this parameter
BTS390 LLMAC Improve is set to OPEN. For MIMO+HSDPA co-carrier cells,
0 HSPAR ment of when this switch is turned on, performance for
WCDM A MIMO HSDPA users is boosted but performance for MIMO
A, LST and users slightly decrease. When this switch is close,
BTS590 ULOCE HSDPA performance for MIMO users remains unchanged and
0, LLMAC Co- performance for HSDPA users decreases.
BTS590 HSPAR carrier GUI Value Range: OPEN(open), CLOSE(close)
0 A
WCDM Unit: None
A Actual Value Range: OPEN, CLOSE
Default Value: CLOSE(close)
ScpichP BSC690 ADD WRFD- Perform Meaning: Transmit power of the SCPICH in a cell,
ower 0 USCPIC 010700 ace which is the power offset relative to the PCPICH.
H Improve GUI Value Range: -350~150
MOD ment of
MIMO Unit: 0.1dB
UCELL
and Actual Value Range: -35~15
HSDPA Default Value: 0
Co-
carrier
ScpichP BSC691 ADD WRFD- Perform Meaning: Transmit power of the SCPICH in a cell,
ower 0 USCPIC 010700 ace which is the power offset relative to the PCPICH.
H Improve GUI Value Range: -350~150
MOD ment of
MIMO Unit: 0.1dB
UCELL
and Actual Value Range: -35~15
HSDPA Default Value: 0
Co-
carrier
PRECD BTS390 ADD WRFD- 2×2 Meaning: This parameter is the control switch for
WSRS 0, ULOCE 010684 MIMO precoding control indication in the local cell.
W BTS390 LL GUI Value Range: FALSE(FALSE), TRUE(TRUE)
0 MOD
WCDM Unit: None
ULOCE
A, LL Actual Value Range: FALSE, TRUE
BTS590 Default Value: FALSE(FALSE)
0,
BTS590
0
WCDM
A
SecCell BSC690 SET WRFD- DC- Meaning: Downlink transmit power threshold of a
TcpThd 0 UFRC 010699 HSDPA DC-HSDPA secondary cell. When DC-HSDPA and
WRFD- +MIMO MIMO Selection Switch is turned on, MIMO is
010684 2x2 enabled in the primary cell if the downlink transmit
MIMO power of the secondary cell is greater than or equal to
WRFD- the value of this parameter and the number of HSDPA
010696 DC- users in the secondary cell is greater than or equal to
HSDPA "SecCellHUserNumThd". Otherwise, DC-HSDPA is
enabled.
GUI Value Range: 1~100
Unit: %
Actual Value Range: 1~100
Default Value: 80
SecCell BSC691 SET WRFD- DC- Meaning: Downlink transmit power threshold of a
TcpThd 0 UFRC 010699 HSDPA DC-HSDPA secondary cell. When DC-HSDPA and
WRFD- +MIMO MIMO Selection Switch is turned on, MIMO is
010684 2x2 enabled in the primary cell if the downlink transmit
MIMO power of the secondary cell is greater than or equal to
WRFD- the value of this parameter and the number of HSDPA
010696 DC- users in the secondary cell is greater than or equal to
HSDPA "SecCellHUserNumThd". Otherwise, DC-HSDPA is
enabled.
GUI Value Range: 1~100
Unit: %
Actual Value Range: 1~100
Default Value: 80
SecCell BSC690 SET WRFD- DC- Meaning: Threshold of the number of HSDPA users in
HUserN 0 UFRC 010699 HSDPA a DC-HSDPA secondary cell. When DC-HSDPA and
umThd WRFD- +MIMO MIMO Selection Switch is turned on, MIMO is
010696 DC- enabled in the primary cell if the number of HSDPA
HSDPA users in the secondary cell is greater than or equal to
the value of this parameter and the downlink transmit
power of the secondary cell is greater than or equal to
"SecCellTcpThd". Otherwise, DC-HSDPA is enabled.
GUI Value Range: 1~100
Unit: None
Actual Value Range: 1~100
Default Value: 4
SecCell BSC691 SET WRFD- DC- Meaning: Threshold of the number of HSDPA users in
HUserN 0 UFRC 010699 HSDPA a DC-HSDPA secondary cell. When DC-HSDPA and
umThd WRFD- +MIMO MIMO Selection Switch is turned on, MIMO is
010696 DC- enabled in the primary cell if the number of HSDPA
HSDPA users in the secondary cell is greater than or equal to
the value of this parameter and the downlink transmit
power of the secondary cell is greater than or equal to
"SecCellTcpThd". Otherwise, DC-HSDPA is enabled.
GUI Value Range: 1~100
Unit: None
Actual Value Range: 1~100
Default Value: 4
H, PS_NOTIFYCN_NOTDOWNSIZE_SWITCH,
ASU_RSP_TIMEOUT_HANDLE_SWITCH,
RB_RECFG_USER_INACT_SWITCH,
RRC_SCRI_NORM_REL_SWITCH,
CELLUPT_RLFAILURE_SRBREESTAB_SWITCH,
CU_OVERLAP_DSCR_SWITCH,
TRB_RST_DSCR_SWITCH,
RNC_FD_SCRI_FORCE_REL_SWITCH,
FP_IUUP_TRACE_SWITCH,
RNC_PCHR_OUTPUT_CTRL_SWITCH,
DTMF_SWITCH,
FAST_CS_FB_BASEDON_RIM_SWITCH,
L2U_SRVCC_WITH_PS_HO_SWITCH,
ULTRA_FLASH_CSFB_SWITCH,
RNC_PS_QUERY_UE_IMEISV_SWITCH,
NRNC_EXTENDED_RNCID_SWITCH
Default Value: LOAD_IRAT_HO_RNC_FILL_TL:
0,SEND_IDT_JUDGE_IU_RESET:
0,RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWI
TCH:1,RNC_CS_QUERY_UE_IMEI_SWITCH:
0,RNC_PS_QUERY_UE_IMEI_SWITCH:
0,FACH_DTCH_CONGEST_P2D:
0,RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWIT
CH:0,PS_NOTIFYCN_NOTDOWNSIZE_SWITCH:
0,ASU_RSP_TIMEOUT_HANDLE_SWITCH:
0,RB_RECFG_USER_INACT_SWITCH:
0,RRC_SCRI_NORM_REL_SWITCH:
0,CELLUPT_RLFAILURE_SRBREESTAB_SWITC
H:0,CU_OVERLAP_DSCR_SWITCH:
0,TRB_RST_DSCR_SWITCH:
0,RNC_FD_SCRI_FORCE_REL_SWITCH:
0,FP_IUUP_TRACE_SWITCH:
1,RNC_PCHR_OUTPUT_CTRL_SWITCH:
1,DTMF_SWITCH:
1,FAST_CS_FB_BASEDON_RIM_SWITCH:
0,L2U_SRVCC_WITH_PS_HO_SWITCH:
0,ULTRA_FLASH_CSFB_SWITCH:
0,RNC_PS_QUERY_UE_IMEISV_SWITCH:
0,NRNC_EXTENDED_RNCID_SWITCH:0
H, PS_NOTIFYCN_NOTDOWNSIZE_SWITCH,
ASU_RSP_TIMEOUT_HANDLE_SWITCH,
RB_RECFG_USER_INACT_SWITCH,
RRC_SCRI_NORM_REL_SWITCH,
CELLUPT_RLFAILURE_SRBREESTAB_SWITCH,
CU_OVERLAP_DSCR_SWITCH,
TRB_RST_DSCR_SWITCH,
RNC_FD_SCRI_FORCE_REL_SWITCH,
FP_IUUP_TRACE_SWITCH,
RNC_PCHR_OUTPUT_CTRL_SWITCH,
DTMF_SWITCH,
FAST_CS_FB_BASEDON_RIM_SWITCH,
L2U_SRVCC_WITH_PS_HO_SWITCH,
ULTRA_FLASH_CSFB_SWITCH,
RNC_PS_QUERY_UE_IMEISV_SWITCH,
NRNC_EXTENDED_RNCID_SWITCH
Default Value: LOAD_IRAT_HO_RNC_FILL_TL:
0,SEND_IDT_JUDGE_IU_RESET:
0,RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWI
TCH:1,RNC_CS_QUERY_UE_IMEI_SWITCH:
0,RNC_PS_QUERY_UE_IMEI_SWITCH:
0,FACH_DTCH_CONGEST_P2D:
0,RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWIT
CH:0,PS_NOTIFYCN_NOTDOWNSIZE_SWITCH:
0,ASU_RSP_TIMEOUT_HANDLE_SWITCH:
0,RB_RECFG_USER_INACT_SWITCH:
0,RRC_SCRI_NORM_REL_SWITCH:
0,CELLUPT_RLFAILURE_SRBREESTAB_SWITC
H:0,CU_OVERLAP_DSCR_SWITCH:
0,TRB_RST_DSCR_SWITCH:
0,RNC_FD_SCRI_FORCE_REL_SWITCH:
0,FP_IUUP_TRACE_SWITCH:
1,RNC_PCHR_OUTPUT_CTRL_SWITCH:
1,DTMF_SWITCH:
1,FAST_CS_FB_BASEDON_RIM_SWITCH:
0,L2U_SRVCC_WITH_PS_HO_SWITCH:
0,ULTRA_FLASH_CSFB_SWITCH:
0,RNC_PS_QUERY_UE_IMEISV_SWITCH:
0,NRNC_EXTENDED_RNCID_SWITCH:0
MaxTxP BSC690 ADD WRFD- Open Meaning: Sum of the maximum transmit power of all
ower 0 UCELL 020501 Loop DL channels in a cell. For detailed information of this
SETUP Power parameter, see 3GPP TS 25.433.
MOD Control GUI Value Range: 0~500
UCELL Unit: 0.1dBm
Actual Value Range: 0~50
Default Value: 430
MaxTxP BSC691 ADD WRFD- Open Meaning: Sum of the maximum transmit power of all
ower 0 UCELL 020501 Loop DL channels in a cell. For detailed information of this
SETUP Power parameter, see 3GPP TS 25.433.
MOD Control GUI Value Range: 0~500
UCELL Unit: 0.1dBm
Actual Value Range: 0~50
Default Value: 430
TxDiver BSC690 ADD WRFD- Physical Meaning: Whether to activate the transmit diversity
sityInd 0 UCELL 022000 Channel mode for common channels in a cell. Transmit
SETUP WRFD- Manage diversity enables the transmit end to use two or more
MOD 150209 ment antennas for transmitting signals. Each antenna is
UCELL DB- assigned with different weight coefficients, such as
WRFD- amplitude and phase, to improve the reception
SETUP 010684 HSDPA
performance of the receive end.
WRFD- 2x2
MIMO GUI Value Range: TRUE, FALSE
010203
Transmi Unit: None
WRFD-
010704 t Actual Value Range: TRUE, FALSE
Diversit Default Value: None
WRFD- y
010700
Flexible
HSPA+
Technol
ogy
Selectio
n
Perform
ace
Improve
ment of
MIMO
and
HSDPA
Co-
carrier
TxDiver BSC691 ADD WRFD- Physical Meaning: Whether to activate the transmit diversity
sityInd 0 UCELL 022000 Channel mode for common channels in a cell. Transmit
SETUP WRFD- Manage diversity enables the transmit end to use two or more
MOD 150209 ment antennas for transmitting signals. Each antenna is
UCELL DB- assigned with different weight coefficients, such as
WRFD- amplitude and phase, to improve the reception
SETUP 010684 HSDPA
performance of the receive end.
WRFD- 2x2
MIMO GUI Value Range: TRUE, FALSE
010203
Transmi Unit: None
WRFD-
010704 t Actual Value Range: TRUE, FALSE
Diversit Default Value: None
WRFD- y
010700
Flexible
HSPA+
Technol
ogy
Selectio
n
Perform
ace
Improve
ment of
MIMO
and
HSDPA
Co-
carrier
TT BTS390 ADD None None Meaning: Indicates the type of the topology. In a ring
0, RRUCH topology, the service data is transmitted on the fiber
BTS390 AIN optic cable that carries the HDLC link. In a load
0 MOD sharing topology, the service data is transmitted on
WCDM RRUCH two fiber optic cables simultaneously, which enhances
A, AIN the transmission capability. The physical connection
BTS390 in the ring topology is similar to that in the load
0 LTE, DSP sharing topology. The trunk chain enables multiple
BTS590 RRUCH CPRI fiber optic cables to simultaneously transmit
0, AINPH service data.
BTS590 YTOPO
GUI Value Range: CHAIN(CHAIN), RING(RING),
0 LST LOADBALANCE(LOADBALANCE),
WCDM RRUCH TRUNK_CHAIN(TRUNK_CHAIN)
A, AIN
BTS590 Unit: None
0 LTE Actual Value Range: CHAIN, RING,
LOADBALANCE, TRUNK_CHAIN
Default Value: None
BM BTS390 ADD None None Meaning: Indicates the backup mode of the RRU
0, RRUCH chain/ring. There are two modes: cold backup and hot
BTS390 AIN backup. Cold backup indicates that when the link on
0 MOD one end of the chain/ring fails, the service is disrupted
WCDM RRUCH for a short period of time, and then re-established on
A, AIN the other end of the chain/ring. Hot backup indicates
BTS390 that when the link on one end of the chain/ring fails,
0 LTE, LST the service is taken over by the other end of the chain/
BTS590 RRUCH ring immediately. There is only one RRU on the
0, AIN chain/ring in hot backup mode. In the RRUCHAIN
BTS590 MO, if TT is set to RING and BM is set to HOT, the
0 head CPRI port and the tail CPRI port of the RRU
WCDM ring must be on different baseband boards.
A, GUI Value Range: COLD(COLD), HOT(HOT)
BTS590
0 LTE Unit: None
Actual Value Range: COLD, HOT
Default Value: COLD(COLD)
TTW BTS390 ADD WRFD- 2×2 Meaning: Indicates whether the cell supports 2T
0, ULOCE 010684 MIMO mode.
BTS390 LL WRFD- Transmi GUI Value Range: FALSE(FALSE), TRUE(TRUE)
0 MOD 010203 t
WCDM Unit: None
ULOCE WRFD- Diversit
A, LL y Actual Value Range: FALSE, TRUE
BTS590 040203
LST RRU Default Value: FALSE(FALSE)
0,
BTS590 ULOCE Redunda
0 LL ncy
WCDM
A
DlStrTh BSC691 SET WRFD- HSDPA Meaning: Rate threshold for decision to use HS-
sOnHsd 0 UFRCC 010610 Introduc DSCH to carry DL PS streaming services. When the
pa HLTYP WRFD- tion maximum DL service rate is higher than or equal to
EPARA 150250 Package this threshold, the service will be carried on HS-
3C- DSCH. Otherwise, it will be carried on DCH.
WRFD-
010701 HSDPA GUI Value Range: D8, D16, D32, D64, D128, D144,
Uplink D256, D384
WRFD-
010630 Enhance Unit: kbit/s
d Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
CELL_F
ACH Default Value: D64
Streami
ng
Traffic
Class on
HSDPA
DlStrTh BSC690 SET WRFD- HSDPA Meaning: Rate threshold for decision to use HS-
sOnHsd 0 UFRCC 010610 Introduc DSCH to carry DL PS streaming services. When the
pa HLTYP WRFD- tion maximum DL service rate is higher than or equal to
EPARA 150250 Package this threshold, the service will be carried on HS-
3C- DSCH. Otherwise, it will be carried on DCH.
WRFD-
010701 HSDPA GUI Value Range: D8, D16, D32, D64, D128, D144,
Uplink D256, D384
WRFD-
010630 Enhance Unit: kbit/s
d Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
CELL_F
ACH Default Value: D64
Streami
ng
Traffic
Class on
HSDPA
DlBeTra BSC690 SET WRFD- HSDPA Meaning: Rate threshold for decision to use HS-
ffThsOn 0 UFRCC 010610 Introduc DSCH to carry DL PS background/interactive
Hsdpa HLTYP WRFD- tion services. When the maximum DL service rate is
EPARA 150250 Package higher than or equal to this threshold, the service will
3C- be carried on HS-DSCH. Otherwise, it will be carried
WRFD- on DCH.
010701 HSDPA
Uplink GUI Value Range: D8, D16, D32, D64, D128, D144,
WRFD- D256, D384, D512, D768, D1024, D1536, D1800,
0106100 Enhance
d D2048, D3600, D7200, D8640, D10100, D13900
8
CELL_F Unit: kbit/s
ACH Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
Interacti 512, 768, 1024, 1536, 1800, 2048, 3600, 7200, 8640,
ve and 10100, 13900
Backgro Default Value: D64
und
Traffic
Class on
HSDPA
DlBeTra BSC691 SET WRFD- HSDPA Meaning: Rate threshold for decision to use HS-
ffThsOn 0 UFRCC 010610 Introduc DSCH to carry DL PS background/interactive
Hsdpa HLTYP WRFD- tion services. When the maximum DL service rate is
EPARA 150250 Package higher than or equal to this threshold, the service will
3C- be carried on HS-DSCH. Otherwise, it will be carried
WRFD- on DCH.
010701 HSDPA
Uplink GUI Value Range: D8, D16, D32, D64, D128, D144,
WRFD- D256, D384, D512, D768, D1024, D1536, D1800,
0106100 Enhance
d D2048, D3600, D7200, D8640, D10100, D13900
8
CELL_F Unit: kbit/s
ACH Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
Interacti 512, 768, 1024, 1536, 1800, 2048, 3600, 7200, 8640,
ve and 10100, 13900
Backgro Default Value: D64
und
Traffic
Class on
HSDPA
11 Counters
12 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
13 Reference Documents