Академический Документы
Профессиональный Документы
Культура Документы
Issue 02
Date 2014-09-15
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.........................................................................................................................................8
2.1 General Principles of HSDPA........................................................................................................................................8
2.2 HSDPA Channels...........................................................................................................................................................9
2.2.1 HS-DSCH and HS-PDSCH.........................................................................................................................................9
2.2.2 HS-SCCH..................................................................................................................................................................10
2.2.3 HS-DPCCH...............................................................................................................................................................10
2.2.4 DPCCH and DPCH/F-DPCH....................................................................................................................................10
2.3 Impact of HSDPA on NEs............................................................................................................................................10
2.4 HSDPA Functions........................................................................................................................................................11
2.4.1 HSDPA Control Plane Functions..............................................................................................................................11
2.4.2 HSDPA User Plane Functions...................................................................................................................................13
3 Control Plane................................................................................................................................14
3.1 Bearer Mapping............................................................................................................................................................15
3.2 SRB over HSDPA........................................................................................................................................................16
3.2.1 Overview...................................................................................................................................................................16
3.2.2 F-DPCH Basic Principles..........................................................................................................................................16
3.2.3 Impacts on Other Functions.......................................................................................................................................20
3.2.4 Weak Coverage- and Low Load-based SRB H2D....................................................................................................21
3.3 Access Control..............................................................................................................................................................25
3.4 Mobility Management..................................................................................................................................................25
3.5 HSDPA over Iur...........................................................................................................................................................26
3.6 Channel Switching........................................................................................................................................................27
3.7 Load Control.................................................................................................................................................................29
3.8 Power Resource Management......................................................................................................................................29
3.9 Code Resource Management........................................................................................................................................30
3.9.1 HS-SCCH Code Resource Management...................................................................................................................30
3.9.2 HS-PDSCH Code Resource Management.................................................................................................................31
4 User Plane.....................................................................................................................................35
4.1 Flow Control and Congestion Control..........................................................................................................................36
4.1.1 Flow Control..............................................................................................................................................................36
4.1.2 Congestion Control....................................................................................................................................................37
4.2 Impact of HSDPA on the RLC and MAC-d Entities....................................................................................................37
4.2.1 Impact on the RLC Entity..........................................................................................................................................37
4.2.2 Impact on the MAC-d Entity.....................................................................................................................................38
4.3 MAC-hs Scheduling.....................................................................................................................................................38
4.3.1 Determining the Candidate Set..................................................................................................................................39
4.3.2 Calculating Scheduling Priorities..............................................................................................................................40
4.3.3 Time and HS-PDSCH Codes Multiplex....................................................................................................................44
4.4 HARQ...........................................................................................................................................................................45
4.4.1 HARQ Retransmission Principles.............................................................................................................................45
4.4.2 Soft Combining During HARQ.................................................................................................................................46
4.4.3 Preamble and Postamble............................................................................................................................................46
4.5 TFRC Selection............................................................................................................................................................48
4.6 Enhanced HSDPA Code Utilization.............................................................................................................................50
4.7 HSDPA Remaining Power Appending.........................................................................................................................50
4.8 CQI Adjustment Based on Dynamic BLER Target......................................................................................................51
4.9 BLER Optimization for HSDPA Burst Services..........................................................................................................52
4.10 Modulation Scheme....................................................................................................................................................53
6 Related Features...........................................................................................................................59
6.1 WRFD-010610 HSDPA Introduction Package............................................................................................................59
6.2 WRFD-010652 SRB over HSDPA...............................................................................................................................59
6.3 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target............................................................................60
6.4 WRFD-140221 HSDPA Scheduling based on UE Location........................................................................................60
6.5 Enhanced HSDPA Code Utilization.............................................................................................................................60
7 Network Impact...........................................................................................................................62
7.1 WRFD-010610 HSDPA Introduction Package............................................................................................................62
7.2 WRFD-010652 SRB over HSDPA...............................................................................................................................62
7.3 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target............................................................................64
7.4 WRFD-140221 HSDPA Scheduling based on UE Location........................................................................................64
7.5 Enhanced HSDPA Code Utilization.............................................................................................................................64
8 Engineering Guidelines.............................................................................................................66
8.1 WRFD-010610 HSDPA Introduction Package............................................................................................................66
9 Parameters...................................................................................................................................152
10 Counters....................................................................................................................................323
11 Glossary.....................................................................................................................................384
12 Reference Documents.............................................................................................................385
1.1 Scope
This document describes HSDPA, including its technical principles, related features, network
impact, and engineering guidelines.
NE Type NE Model
LampSite DBS3900
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
RAN16.0 02 (2014-09-15)
This issue includes the following changes.
Feature Optimized the weak coverage- and low load-based SRB None
change H2D function. For details, see the following sections:
l 3.2.4 Weak Coverage- and Low Load-based SRB
H2D
l 7.2 WRFD-010652 SRB over HSDPA
l 8.3 WRFD-010652 SRB over HSDPA
RAN16.0 01 (2014-04-30)
This issue includes the following changes.
Editorial Added the descriptions about the feature and function None
change differences between NodeBs of different types. For
details, see section 1.4 Differences Between Base
Station Types.
Feature change Add the enhanced HSDPA code utilization function. For details, see
l 4.6 Enhanced HSDPA Code Utilization the following
sections: Added
l 6.5 Enhanced HSDPA Code Utilization the
l 7.5 Enhanced HSDPA Code Utilization CODEOPTSW
l 8.20 Enhanced HSDPA Code Utilization parameter.
WRFD- HSDPA Y Y Y Y Y Y
010610 Introduct
ion
Package
WRFD- QPSK NA NA Y Y Y Y
0106101 Modulati
7 on
WRFD- 15 Codes Y Y Y Y Y Y
0106100 per Cell
1
WRFD- Time Y Y Y Y Y Y
0106101 and HS-
8 PDSCH
Codes
Multiple
x
WRFD- HSDPA NA NA Y Y Y Y
0106100 H-ARQ
9 &
Scheduli
ng
(MAX
C/I, RR
and PF)
WRFD- HSDPA Y Y Y Y Y Y
0106100 Static
5 Code
Allocati
on and
RNC-
Controll
ed
Dynamic
Code
Allocati
on
WRFD- HSDPA Y Y Y Y Y Y
0106101 Dynamic
9 Power
Allocati
on
WRFD- HSDPA Y Y Y Y Y Y
0106101 Flow
0 Control
WRFD- HSDPA Y Y Y Y Y Y
0106100 UE
2 Category
1 to 28
WRFD- DL NA NA Y Y Y Y
010629 16QAM
Modulati
on
WRFD- Dynamic Y Y Y Y Y Y
010631 Code
Allocati
on Based
on
NodeB
WRFD- HSDPA Y Y Y Y Y Y
010611 Enhance
d
Package
WRFD- Scheduli Y Y Y Y Y Y
0106110 ng based
3 on EPF
and GBR
WRFD- HS- Y Y Y Y Y Y
0106111 DPCCH
3 Preambl
e
Support
WRFD- HSDPA Y Y Y Y Y Y
010651 over Iur
WRFD- SRB Y Y Y Y Y Y
010652 over
HSDPA
WRFD- CQI NA NA Y Y Y Y
030010 Adjustm
ent
Based on
Dynamic
BLER
Target
WRFD- HSDPA NA NA Y Y Y Y
140221 Scheduli
ng Based
on UE
Location
WRFD- HSDPA Y Y Y Y Y Y
010650 13.976M
bps per
User
NOTE
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is
not involved, that is, a feature does not require the support of the NE.
The features described in this document are implemented in the same way on macro, micro, and
LampSite base stations.
2 Overview
Fast scheduling Fast scheduling introduced into the NodeB determines the UEs for data
transmission in each TTI (2 ms) and dynamically allocates resources to
these UEs. It improves the usage of system resources and increases the
system capacity.
For details about how Huawei RAN implements fast scheduling, see
section 4.3 MAC-hs Scheduling.
Fast HARQ Fast hybrid automatic repeat request (HARQ) is used to rapidly request
the retransmission of erroneously received data.
Specifically, when the UE detects an erroneous data transmission, it
saves the received data and requests the NodeB to retransmit the original
data at the physical layer. Before decoding, the UE performs soft
combining of the saved data and the retransmitted data. The combining
fully uses the data transmitted each time and therefore increases the
decoding success rate. In addition, the retransmission delay at the
physical layer is reduced greatly, compared with that at the RLC layer.
For details about how Huawei RAN implements fast HARQ, see section
4.4 HARQ.
Fast AMC To compensate for channel variations, the DCH performs power control.
To achieve this goal, HSDPA also performs fast adaptive modulation
and coding (AMC), that is, adjusts the modulation scheme and coding
rate in each TTI. AMC is based on the channel quality indicator (CQI)
reported by the UE, and its purpose is to select an appropriate
transmission rate to meet channel conditions. When the channel
conditions are good, 16QAM or 64QAM can be used to provide higher
transmission rates. When the channel conditions are poor, QPSK can be
used to ensure the transmission quality.
For details about how Huawei RAN implements fast AMC, see section
4.5 TFRC Selection.
The MAC-hs, a new MAC sublayer, is introduced into the UE and NodeB to support HSDPA.
Unlike the DCH, the HS-DSCH cannot support soft handover. The reason is that this type of
handover requires different cells to use the same radio resource for sending the same data to the
UE, but the scheduling function can be performed only within the cell.
2.2.2 HS-SCCH
HS-SCCH is a high-speed shared control channel. It carries the control information related to
the HS-PDSCH. The control information includes the UE identity, HARQ-related information,
and information about transport format and resource combination (TFRC). For each transmission
of the HS-DSCH, one HS-SCCH is required to carry the related control information. One cell
can be configured with several HS-SCCHs. The number of HS-SCCHs determines the maximum
number of UEs that can be scheduled simultaneously in each TTI.
2.2.3 HS-DPCCH
HS-DPCCH is a high speed dedicated physical control channel. In the uplink, each HSDPA UE
must be configured with an HS-DPCCH. This channel is mainly used by the UE to report the
CQI and whether a transport block is correctly received. The information about the transport
block is used for fast retransmission at the physical layer. The CQI is used for AMC and
scheduling to allocate Uu resources.
The HSDPA UE must be configured with dedicated physical control channels in both the uplink
and the downlink.
The uplink DPCCH is used for closed-loop power control by working with the DPCH or F-
DPCH. In addition, the uplink DPCCH power is used as a reference for the HS-DPCCH power.
The downlink DPCH is used for inner-loop power control and as a reference for the HS-PDSCH
power.
Like the downlink DPCH, the F-DPCH is also used for inner-loop power control. The difference
is that each UE must have a downlink DPCH (SF256) whereas 10 UEs can share an F-DPCH
(SF256) to save downlink channel codes.
On the control plane of the network side, the RNC processes the signaling about HSDPA cell
configuration, HS-DSCH related channel configuration, and mobility management. On the user
plane of the network side, the RLC layer and MAC-d of the RNC are unchanged. At the NodeB,
the MAC-hs is added to implement HSDPA scheduling, Uu resource allocation, AMC, and Iub
flow control. The MAC-hs implements these management functions in a short time. Therefore,
it reduces both unnecessary delays and processing complexity caused by Iub message exchange.
On the UE side, the MAC-hs is added between the MAC-d and the physical layer for data
reception. To support HSDPA (without considering HSPA evolution), 3GPP defines 12 UE
categories. These UEs support different peak rates at the physical layer, ranging from 912 kbit/
1 5 3 7298 1.2
2 5 3 7298 1.2
3 5 2 7298 1.8
4 5 2 7298 1.8
5 5 1 7298 3.6
6 5 1 7298 3.6
7 10 1 14411 7.2
8 10 1 14411 7.2
9 15 1 20251 10.2
10 15 1 27952 14.4
11 5 2 3630 0.9
12 5 1 3630 1.8
Figure 2-2 shows the HSDPA control plane functions based on the service connection setup
and maintenance procedure.
power and codes are the bottleneck resources of the cell. Resource management can
increase the HSDPA capacity.
Power resource management reserves power for channels of different types and allocates
power for them. For details, see section 3.8 Power Resource Management.
Code resource management allocates and reserves code resources for channels of different
types. In addition, it collects and reshuffles idle code resources.
For details, see section 3.9 Code Resource Management.
The service data is passed to the RLC layer and MAC-d of the RNC for processing and
encapsulation. Then, the MAC-d PDU is formed and passed through the Iub/Iur interface to the
NodeB/RNC. To avoid congestion, the flow control and congestion control functions control
the traffic on the Iub/Iur interface through the HS-DSCH frame protocol (3GPP TS 25.435).
After the MAC-d PDU is received by the NodeB, it is passed through the MAC-hs to the physical
layer and then sent out through the Uu interface. The MAC-hs provides MAC-hs scheduling,
TFRC selection, and HARQ. MAC-hs scheduling determines the HSDPA users in the cell for
data transmission. TFRC selection determines the transmission rates and Uu resources to be
allocated to the HSDPA UEs. HARQ is used to implement the hybrid automatic repeat request
function.
3 Control Plane
Videophone No No
Streaming No No
Interactive Yes No
Background Yes No
During the service setup, the RNC selects appropriate channels based on the UE capability, cell
capability, and service parameters to optimize the use of cell resources and ensure the QoS.
Huawei RAN supports the setting of the types of RABs carried on the HS-DSCH according to
service requirements. For details, see Radio Bearers Feature Parameter Description.
3.2.1 Overview
Introduction
l SRB over HSDPA
SRB over HSDPA enables a UE's downlink signaling radio bearers (SRBs) to be carried
on the HS-DSCH.
SRB over HSDPA is introduced in 3GPP Release 6 and is supported by RAN10.0 and later
versions.
l F-DPCH
After SRB over HSDPA takes effect, the A-DPCH is replaced by an F-DPCH. If a UE uses
SRB over HSDPA, the transmit power control (TPC) command is transmitted to the UE
on an F-DPCH.
The F-DPCH carries only the TPC commands sent from the NodeB to UEs.
Benefits
Compared with SRB over DCH, SRB over HSDPA provides the following benefits:
However, this feature increases the call drop ratio of HSDPA services.
For details about the benefits and network impacts of SRB over HSDPA, see section 7.2
WRFD-010652 SRB over HSDPA.
If a UE is configured with the F-DPCH, all the RBs (including SRBs and TRBs) for this UE are
mapped onto the HS-PDSCH, and the DPDCH does not need to be configured. (TRB is short
for traffic radio bearer.) The F-DPCH replaces the A-DPCH and carries only TPC commands
because the pilot and transport format combination indicator (TFCI) are no more required.
For details about the frame formats of the A-DPCH and F-DPCH, see the following sections in
3GPP TS 25.211 V9.0.0:
In 3GPP Release 6, each timeslot of the F-DPCH frame can use only timeslot format 0, and
therefore the bit position of the TPC command is fixed. In 3GPP Release 7, the enhanced F-
DPCH with timeslot formats 1 to 9 is introduced. Table 3-2 lists the F-DPCH frame formats.
0 3 1.5 256 20 2 2 16
1 3 1.5 256 20 4 2 14
2 3 1.5 256 20 6 2 12
3 3 1.5 256 20 8 2 10
4 3 1.5 256 20 10 2 8
5 3 1.5 256 20 12 2 6
6 3 1.5 256 20 14 2 4
7 3 1.5 256 20 16 2 2
8 3 1.5 256 20 18 2 0
9 3 1.5 256 20 0 2 18
F-DPCH Multiplexing
An F-DPCH can be shared by up to 10 UEs through time division multiplexing, as shown in
Figure 3-2. These UEs can be differentiated by using different time offset.
An F-DPCH can be shared by up to 10 UEs, and the RNC uses ten symbols to specify the resource
usage of an F-DPCH. If an F-DPCH has available symbols, a new UE can use this F-DPCH
when it is admitted to the cell. Otherwise, the RNC allocates a new F-DPCH to the UE after
admission.
Enhanced F-DPCH
In 3GPP Release 6, the TPC commands sent on the F-DPCH in different cells to a UE must have
the same time offset. Therefore, when a UE adds a radio link during a soft handover, the UE
needs to apply for a new F-DPCH if the F-DPCH configured for the target cell does not have an
available symbol with the same time offset (as illustrated in Figure 3-3). As a result, F-DPCH
channelization codes cannot be fully utilized.
In 3GPP Release 7, the TPC commands sent on the F-DPCH in different cells to a UE can have
different time offsets with the introduction of the enhanced F-DPCH with nine timeslot formats
(as shown in Table 3-2). Therefore, during a soft handover, a UE can use the F-DPCH configured
for the target cell if the F-DPCH has an available symbol (as shown in Figure 3-4). In this way,
F-DPCH channelization codes can be fully utilized.
The TPC commands from different cells may require a timeslot to aggregate because the
enhanced F-DPCH can be configured with different timeslot formats. As a result, the aggregated
TPC commands can only be used to adjust the transmit power on the uplink DPCCH in the next
timeslot. Compared with the F-DPCH in 3GPP Release 6, the enhanced F-DPCH cannot perform
uplink power control in time. In 3GPP Release 6, the TPC commands from different cells require
only one tenth of a timeslot to aggregate because the TPC commands are basically mapped to
the same position in an F-DPCH frame. In this case, the aggregated TPC commands can be used
to adjust the transmit power on the uplink DPCCH in the current timeslot.
Radio Bearers
l During RRC connection setup, SRBs can be carried on the HS-DSCH if the following
conditions are met:
– The SrbChlType(BSC6900,BSC6910) parameter is set to HSDPA or HSPA.
– The SrbChlTypeRrcEffectFlag(BSC6900,BSC6910) parameter is set to TRUE.
l During TRB setup, SRBs that were not previously carried on the HS-DSCH can be
reconfigured on the HS-DSCH if the following conditions are met:
– The SrbChlType(BSC6900,BSC6910) parameter is set to HSDPA or HSPA.
– All the downlink TRBs for a UE are carried on the HS-DSCH.
NOTE
The RNC configures the F-DPCH and SRB over HSDPA functions for a UE only when all cells in the
active set for the UE support the F-DPCH.
During RRC connection setup, if SRBs are carried on the HS-DSCH, not on the DCH, UEs can
initiate only hard handovers in the downlink and the gains produced by maximum-ratio
combination of soft handovers are sacrificed. In this case, the RAB setup success ratio decreases.
Therefore, it is recommended that the SrbChlTypeRrcEffectFlag(BSC6900,BSC6910)
parameter be set to FALSE.
The RAN supports the handover between cells supporting SRB over DCH and cells supporting
SRB over HS-DSCH. For example, if the target cell for a handover supports SRB over HS-
DSCH but the source cell does not, a UE can use SRB over HS-DSCH after being handed over
to the target cell. If the target cell for a handover does not support SRB over HS-DSCH but the
source cell does, SRBs of a UE are switched from the HS-DSCH to the DCH after the UE is
handed over to the target cell.
Scheduling
On the HS-DSCH, the NodeB preferentially schedules the SRBs.
TFRC Selection
To reduce the impact of this feature on the HSDPA call drop ratio, the NodeB reduces the value
of the channel quality indicator (CQI) reported by a UE when performing the transport format
and resource combination (TFRC) selection. In this way:
l When power resources in a cell are sufficient, the NodeB increases the transmit power of
the SRB queue. The transmit power can be increased to a value equal to the smaller of the
available HSPA power in the current transmission time interval (TTI) and the value of the
EXTRAPOWERFORSRB parameter.
l When power resources in a cell are insufficient, the NodeB reduces the size of the data
block to be sent in the SRB queue. The size can be reduced to the same value as that of a
MAC-ehs packet data unit (PDU).
For details about how to calculate the size of a MAC-ehs PDU, see section 4.2.1 Impact
on the RLC Entity.
Overview
The weak coverage- and low load-based SRB switchover from the HS-DSCH to the DCH (SRB
H2D) function is used to counteract the increase in the HSDPA call drop ratio caused by SRB
over HSDPA. You can select the DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH check
box under the DraSwitch2(BSC6900,BSC6910)parameter in the SET
UCORRMALGOSWITCH command to enable this function.
With this function, SRBs of a UE using SRB over HS-DSCH are switched from the HS-DSCH
to the DCH when the UE is located in weak-coverage areas and a low-load cell. Using this
approach counteracts the increase in the HSDPA call drop ratio, but sacrifices the positive gains
produced by SRB over HS-DSCH in code resources. However, when a UE is located in good-
coverage areas or a high-load cell, the UE continues to use SRB over HS-DSCH, providing
positive gains in code resources.
For a UE in access mode or a UE in connected mode, the RNC determines whether to trigger
the weak coverage- and low load-based SRB H2D function. In this document, the UE in access
mode refers to a UE that has just entered the CELL_DCH state, and the UE in connected mode
refers to a UE transmitting data in the CELL_DCH state.
The RNC triggers this function for a UE in access mode only in the following scenarios:
l The load of the downlink non-HSPA power load state is less than or equal to that of the
state specified by the SrbH2DNonHLoadState(BSC6900,BSC6910) parameter.
The downlink non-HSPA power load state of a cell is classified into light state, normal
state, loaded state, heavy state, and overload state. For detailed descriptions of these states,
see Load Measurement Feature Parameter Description.
l The spreading factor (SF) corresponding to the remaining code of a cell is greater than or
equal to the value of the CellLdrSfResThd(BSC6900,BSC6910) parameter in the ADD/
MOD UCELLLDR command.
The cell in this section refers to the serving cell or best cell where services are set up.
l For a UE in access mode, the RNC obtains the RSCP and Ec/N0 from the messages and
events reported by the UE in the following scenarios:
– RRC connection setup (such as state transition from idle to CELL_DCH) scenario where
the RRC CONNECTION REQUEST message is reported
– P2D or U2D state transition scenario where the CELL UPDATE message is reported
– F2D state transition scenario where event 4A based on the uplink traffic volume is
reported
l For a UE in connected mode, the RNC obtains the RSCP and Ec/N0 as follows:
The RNC initiates the periodic intra-frequency measurement and requires a UE to
periodically report the RSCP and Ec/N0 of intra-frequency cells. For details, see Handover
Feature Parameter Description.
The RSCP and Ec/N0 values are valid for the period specified by the EcN0EffectTime
(BSC6900,BSC6910)parameter, starting from the time the RNC receives a message or event
containing the RSCP and Ec/N0. The EcN0EffectTime(BSC6900,BSC6910)parameter can be
set by running the RNC-level command SET UFRC or the cell-level command ADD/MOD
UCELLFRC. When the EcN0EffectTime(BSC6900,BSC6910)parameter is set both at the cell
level and at the RNC level, the cell-level setting prevails.
During RRC connection setup, TRB setup, or state transition, the RSCP and Ec/N0 may become
invalid. For example, in a combined hard handover and SRNS relocation or inter-RAT handover
from GSM to UMTS, the RSCP and Ec/N0 become invalid during the RRC connection setup
or TRB setup. In this case, the RNC determines whether a UE is located in weak-coverage areas
as follows:
The RNC determines that a UE using this feature is located in weak-coverage areas when any
of the following conditions is met:
l The value of the latest valid RSCP reported by a UE is less than or equal to the value of
the SrbOverHsdpaRscpDownThd parameter.
l The value of the latest valid Ec/N0 reported by a UE is less than or equal to the value of
the SrbOverHsdpaEcn0DownThd parameter.
The RNC determines that a UE using this feature is located in good-coverage areas when the
following conditions are met:
l The value of the latest valid RSCP reported by a UE is greater than the value of the
SrbOverHsdpaRscpUpThd parameter.
l The value of the latest valid Ec/N0 reported by a UE is greater than the value of the
SrbOverHsdpaEcn0UpThd parameter.
These parameters are set by running the SET UCHLQUALITYEVALUATE command. Table
3-3 defines these parameters.
In most cases, the RNC determines whether a UE is located in weak-coverage areas by using
the RSCP or Ec/N0 of the low-load cell. If a UE does not report the RSCP or Ec/N0 of the low-
load cell, for example, in RAB DRD scenarios, the RNC determines whether the UE is located
in weak-coverage areas by using the RSCP or Ec/N0 of the cell where the RRC connection is
set up.
SRB H2D/D2H
l The RNC triggers a reconfiguration procedure to switch downlink SRBs from the HS-
DSCH to the DCH if the UE is located in a low-load cell in weak coverage areas.
the DCH back to the HS-DSCH only when the UE is in connected mode. The SRB D2H in this
scenario is valid only when RESERVED_SWITCH_11_BIT5 under the RsvSwitch11
(BSC6900,BSC6910) parameter in the SET UALGORSVPARA command is set to 1. In
addition, the UE cannot perform the following operations before the service release:
l Periodic DRD for SRB over HS-DSCH
l SRB D2H retry during traffic-volume-based DCCC rate increase
When the downlink SRBs of a UE in connected mode are carried on the DCH, the RNC triggers
a reconfiguration procedure to switch downlink SRBs from the DCH to the HS-DSCH upon
receiving the periodic measurement report from the UE if the following conditions are met:
l The reports from the UE are valid in three consecutive measurement periods.
l The UE is located in good coverage areas or a high-load cell when the three measurement
reports are reported.
If RESERVED_SWITCH_11_BIT5 under the RsvSwitch11(BSC6900,BSC6910) parameter
in the SET UALGORSVPARA command is set to 0, the UEs in connected mode whose the
SRBs have been switched from the HS-DSCH to the DCH due to non-coverage or non-load
reasons can perform the preceding SRB D2H retry operations before the service release. The
preceding SRB D2H retry operations consider neither coverage nor load and increase the call
drop possibility in weak coverage areas. Therefore, RESERVED_SWITCH_11_BIT5 must
be set to 1 to counteract the impact on the HSDPA call drop ratio.
increase both the handover frequency and the sensitivity of HS-DSCH switching to signal
variations in the serving cell. Raising this threshold can reduce the handover frequency but may
increase the probability of the HS-DSCH service being discontinuous or even dropping on the
cell edge. For the HS-DSCH service, Huawei supports inter-cell intra-frequency handover, inter-
cell inter-frequency handover, and inter-RAT handover.
Mobility management may trigger the switching from the HS-DSCH to the DCH. If the UE with
the HS-DSCH service cannot set up the HS-DSCH connection with the target cell, the channel
switching function, together with mobility management, switches the HS-DSCH to the DCH.
When the HS-DSCH connection is available, the channel switching function switches the DCH
back to the HS-DSCH. When the HSDPA user returns from the DCH cell to the HSDPA cell,
the DCH is set up to ensure successful handover. A certain period (ChannelRetryHoTimerLen
(BSC6900,BSC6910)) later after the handover, the channel switching function switches the
DCH to the HS-DSCH. For details, see Handover Feature Parameter Description and section
3.6 Channel Switching.
NE Requirement
CN None
NodeB None
Basic Principle
HSDPA over Iur is introduced in 3GPP Release 5. This feature can be applied when the HSDPA
serving cell is under the drifting RNC (DRNC).
HSDPA over Iur provides the following functions:
l HSDPA service management over Iur
HSDPA service management over Iur involves HSDPA service setup, modification,
release, and state transition over the Iur interface.
The HSDPA service of a UE can be set up, modified, or released over the Iur interface if
one of the following conditions is met:
Table 3-5 lists new state transition and new channel switching.
Here, the switching between HS-DSCH and FACH can be triggered by traffic volume, which
is similar to the switching between DCH and FACH. For details, see State Transition Feature
Parameter Description.
In addition, when the cell load is too high, load control may also trigger the switching from the
HS-DSCH to the FACH to relieve congestion. For details, see Load Control Feature Parameter
Description.
As the HS-DSCH is introduced later, it is inevitable that some cells support the HS-DSCH but
others do not. This is also the case with UEs. When a service is set up, the channel switching
function selects an appropriate bearer channel based on the cell capability and UE capability to
ensure the QoS while efficiently using the cell resources. When the user is moving, the channel
switching function adjusts the channel type based on the UE capability to ensure service
continuity while improving user experience.
Triggers for switching from the HS-DSCH to the DCH are as follows:
l The HS-DSCH is selected during the service setup but neither the resources of the serving
cell nor the resources of the inter-frequency same-coverage neighboring cell are sufficient.
In this case, the HS-DSCH is switched to the DCH. This function is achieved by means of
non-periodic directed retry decision (DRD). For details about non-periodic DRD, see
Directed Retry Decision Feature Parameter Description.
l The HS-DSCH serving cell changes. The UE attempts to set up a new HS-DSCH connection
with the new best cell. In such a case, the possible scenarios are as follows:
– If the new best cell does not support the HS-DSCH, the UE cannot set up the HS-DSCH
connection. In this case, the HS-DSCH is switched to the DCH.
– If the new best cell supports the HS-DSCH but a new HS-DSCH connection cannot be
set up because the resources are insufficient, the DCH connection is set up and the HS-
DSCH is switched to this DCH.
For details, see Handover Feature Parameter Description.
l The user moves from a cell supporting the DCH but not supporting the HS-DSCH to a cell
supporting the HS-DSCH. In this case, the DCH connection is also set up because the DCH
supports soft handover, which can increase the handover success rate.
In one of the cases described previously, the DCH connection is set up in a cell supporting the
HS-DSCH or in an inter-frequency same-coverage neighboring cell supporting the HS-DSCH.
Then, the DCH is switched to the HS-DSCH by either of the following mechanisms:
l The downlink power resources are first reserved for common physical channels and
allocated to the DPCH. The remaining power resources are available for HSPA, including
HSUPA and HSDPA.
l The HSPA power resources are first allocated to the HSUPA downlink control channels,
including the E-AGCH, E-RGCH, and E-HICH. The remaining power resources are
available for HSDPA.
l The HSDPA power resources are first allocated to the downlink control channel HS-SCCH.
For details, see Power Control Feature Parameter Description. The remaining power
resources are allocated to the traffic channel HS-PDSCH.
For details on power resource allocation, see section 4.5 TFRC Selection.
Every TTI, the NodeB detects the power usage of R99 channels to determine the power available
for HSPA. To reserve the power for R99 power control itself, the power margin PwrMgn needs
to be set on the NodeB side. In addition, the power allocated to HSPA must not exceed the
maximum permissible power HspaPower(BSC6900,BSC6910), which can be set on the RNC
side.
For details on uplink HS-DPCCH power control, see Power Control Feature Parameter
Description.
The NodeB supports HS-DSCH transmissions to multiple users in parallel in a TTI. If more than
one HS-PDSCH code can be allocated by the NodeB, then code multiplexing can be used to
allocate the codes to multiple users to improve resource usage and system throughput.
The dynamic HS-SCCH code allocation function is introduced to save HS-SCCH and E-RGCH/
EHICH codes and to enable the HS-PDSCH to use 15 SF16 codes. With this function, the RNC
and NodeB dynamically allocate codes to the HS-SCCH and E-RGCH/EHICH without
sacrificing the functions of the HS-SCCH and E-RGCH/EHICH. This function improves
HSDPA throughput. This function takes effect only when DynHsscchAllocSwitch is set to on.
It is recommended for cells where the number of HSDPA users is small.
The transport channel HS-DSCH is mapped on one or several High-Speed Physical Downlink
Shared Channels (HS-PDSCHs) which are simultaneously received by the UE. As indicated in
3GPP specifications, there are up to 15 HS-PDSCHs per cell with the spreading factor fixed to
16.
The number of the HS-PDSCHs per NodeB is configurable and dependent on the license. The
license specifies the maximum number of SF16 codes purchased by the operator. The license
works at the NodeB level, which means all cells under a NodeB share the license. The NodeB
can dynamically allocate license codes to the HS-PDSCHs between cells based on the actual
requirements. The number of available HS-PDSCH codes for a cell is the number of license
codes allocated by the NodeB or the number of HS-PDSCH codes allocated by the function of
HS-PDSCH code resource management, whichever is smaller.
The function of HS-PDSCH code resource management is used to share the cell code resources
between DPCH and HS-PPDCH in a cell. As the DPCH and the HS-PDSCH coexist in a cell,
sharing the cell code resources between them is of critical importance in HSDPA code resource
management.
The function of HS-PDSCH code resource management supports both RNC-level and NodeB-
level code resource management. RNC-controlled static or dynamic code allocation is enabled
through the parameter AllocCodeMode(BSC6900,BSC6910). NodeB-controlled dynamic code
allocation is enabled through the parameter DynCodeSw.
too many DCH users from being admitted and to ensure the basic data transmission of
the HS-PDSCH.
– The maximum number of HS-PDSCH codes is specified by the cell-level parameter
HsPdschMaxCodeNum(BSC6900,BSC6910). The purpose of this setting is to prevent
too many codes from being allocated for the HS-PDSCH and to prevent DCH users
from preempting codes during admission.
– The number of codes that can be shared between HS-PDSCH and DPCH is equal to the
value of HsPdschMaxCodeNum(BSC6900,BSC6910) minus the value of
HsPdschMinCodeNum(BSC6900,BSC6910), as shown in Figure 3-9. When a code
that can be shared is idle, it can be allocated to the HS-PDSCH if the idle code is adjacent
to the allocated HS-PDSCH codes.
The dynamic code allocation controlled by the NodeB is more flexible than the dynamic code
allocation controlled by the RNC. The dynamic code allocation controlled by the NodeB shortens
the code allocation duration and reduces the number of Iub signaling messages transmitted for
code reallocation.
If NodeB-controlled dynamic code allocation is enabled, the RNC-controlled dynamic code
allocation is disabled dynamically.
Huawei recommends the following code allocation modes, where the first mode is preferred:
l Configure the RNC to use static code allocation and the NodeB to use dynamic code
allocation.
l If the NodeB does not support dynamic code allocation, configure the RNC to use dynamic
code allocation.
If not all the NodeBs controlled by an RNC support dynamic code allocation, the RNC-controlled
dynamic code allocation is recommended. In this case, the NodeB-controlled dynamic code
allocation can also be enabled for those supporting NodeBs.
Dynamic code tree reshuffling takes effect only when the following conditions are met:
l The cell is not in the basic congestion state that is triggered by code resource. For details
about basic congestion state, see Load Control Feature Parameter Description.
l The switch parameter CodeAdjForHsdpaSwitch(BSC6900,BSC6910) is set to ON. In this
case, the RNC moves the codes occupied by R99 users leftward along the code tree and
thereby releases shared codes that are close to HS-PDSCH codes. Figure 3-11 shows how
this works.
When the RNC-controlled dynamic code allocation or the NodeB-Controlled Dynamic Code
Allocation is enabled, codes released by means of dynamic code tree reshuffling can be used by
the HS-PDSCH to improve throughput for HSDPA users.
Whether the F-DPCH codes can be reallocated through dynamic code tree reshuffling is
determined by the parameter DlSfAdmAlgoSwitch(BSC6900,BSC6910):
FDPCH_SF_ALLOC_OPT_SWITCH in the MML command ADD
UCELLALGOSWITCH
When dynamic code tree reshuffling takes effect, the RNC reshuffles the codes used by the
DPCH/F-DPCH to provide more continuous SF16 codes for HSDPA through this function. This
function is described as follows:
Every time the codes used by the DPCH are changed, the RNC will choose an SF16 subtree that
is not used by HS-PDSCH from right to left. The selected subtree must meet the following
conditions:
l The selected subtree belongs to the code trees that can be shared between HS-PDSCH and
DPCH.
l The number of DPCHs and F-DPCHs on the selected subtree is smaller than or equal to
the threshold specified by the parameter CodeAdjForHsdpaUserNumThd
(BSC6900,BSC6910).
When the above conditions are met, the RNC will select this subtree for reshuffling and relocate
the users to the positions where the codes are idle.
4 User Plane
Figure 4-1 shows the basic principles of flow control and congestion control.
Figure 4-1 Basic principles of Iub flow control and congestion control
1. The NodeB measures the buffered data amount of each MAC-hs queue and the average Uu
transmission rate.
l If the buffering time is too short, you can infer that the RNC slows down the data
transmission, that is, the Iub transmission rate is lower than the Uu transmission rate. In
this case, the pre-allocated Iub bandwidth is adjusted to a value greater than the average
Uu transmission rate.
l If the buffering time is appropriate, the pre-allocated Iub bandwidth is adjusted to the
average Uu transmission rate.
l If the buffering time is too long, the pre-allocated Iub bandwidth is adjusted to a value
smaller than the average Uu transmission rate.
For details on flow control, see Transmission Resource Management Feature Parameter
Description.
The amount of data to be transmitted is sent by the RNC to each MAC-hs queue through the
Capacity Request message. Based on this amount and the total Iub bandwidth available for
HSDPA, the congestion control function adjusts the bandwidth pre-allocated to each MAC-hs
queue. Therefore, congestion control ensures that the total bandwidth actually allocated to all
the MAC-hs queues is not higher than the total available Iub bandwidth.
The total Iub bandwidth available for HSDPA depends on the variations in HSDPA packet delay
and the situation of packet loss. HSDPA shares the bandwidth with the DCH and control
signaling, and the DCH and control signaling has higher priorities than HSDPA. Therefore, when
the HSDPA packet delay or packet loss increases, you can infer that the number of DCHs or the
amount of control signaling increases. In such a case, the bandwidth available for HSDPA
decreases and the bandwidth actually allocated for HSDPA decreases.
For details on congestion control, see Transmission Resource Management Feature Parameter
Description.
NOTE
For the Iur interface, flow control and congestion control are also applied. The control principles and
processing procedures are the same as those for the Iub interface.
With the limited Uu resources for HSDPA in a cell, the user expects to maximize the service
rate while the telecom operator expects to maximize the system capacity. MAC-hs scheduling
is used to coordinate the Uu resources, user experience, and system capacity. It is implemented
at the NodeB MAC-hs.
The scheduling algorithm consists of two steps. At first, the algorithm determines which initial
transmission queues or retransmission processes can be put into the candidate set for scheduling.
Then, the algorithm calculates their priorities based on factors such as the CQI, user fairness,
and differentiated services. If the algorithm is weighted more towards the channel quality of the
UE, the HSDPA cell can have a higher capacity but user fairness and differentiated services may
be affected. If the algorithm is weighted more towards user fairness and differentiated services,
the system capacity may be affected.
Huawei provides five scheduling algorithms: maximum C/I (MAXCI), round-robin (RR),
proportional fair (PF), Enhanced Proportional Fair (EPF), and EPF based on UE location
(EPF_LOC). The EPF and EPF_LOC are optional.
l If the UE starts the compressed mode, its data cannot be put into the candidate set during
the GAP.
l If the UE category requires the UE to wait for several TTIs before it can be scheduled again,
its data cannot be put into the candidate set in this period. The UE of category 1 or 2 needs
to wait for 3 TTIs, and the UE of category 3, 4, and 11 must wait for 2 TTIs.
l If the number of retransmissions of a data packet reaches or exceeds the maximum number,
the data of this UE cannot be put into the candidate set. The data should be discarded.
Huawei supports that the maximum number of retransmissions is set on a service basis:
– MaxNonConverHarqRt: the maximum number of non-conversational service
retransmissions in the CELL_DCH state
– MAXEFACHHARQRT: In versions earlier than RAN15.0, the UTRAN does not
support feedback on the uplink HS-DPCCH from UEs in the enhanced CELL_FACH
state. Therefore, the UEs perform blind HARQ retransmissions. This parameter
specifies the maximum number of HARQ retransmissions for a UE in the enhanced
CELL_FACH state.
– MAXEFACHHSHARQRT: From RAN15.0, the UTRAN supports feedback on the
uplink HS-DPCCH from UEs in the enhanced CELL_FACH state. The UE in the
enhanced CELL_FACH state can report ACK, NACK, or CQI in the uplink. This
parameter specifies the maximum number of HARQ retransmissions for a UE in the
enhanced CELL_FACH state that supports HS-DPCCH feedback.
l The CQI reported by the UE is 0.
l There is no data in the Mac-ehs or Mac-hs queue for the UE.
l The uplink channel quality of UEs is poor and the uplink channels of these UEs are carrying
PS conversational services or SRBs.
NOTE
The MAC-hs can schedule data packets and select Transport Format and Resource Combine (TFRC)
entities for UEs whose uplink channel quality is poor and CQI is not 0 when the following conditions are
met:
l The MAC-hs queue contains the data packets of these UEs and the data size is not 0.
l The scheduling time does not fall into the GAP.
For new data packets, the MAC-hs calculates the scheduling priority for the follow-up data
packet scheduling and TFRC entity selection based on the principle that applies to a CQI of 12
(CQI adjustments are not performed). For data packets to be retransmitted, the MAC-hs
schedules these data packets and selects TFRC entities in the same way as it operates on UEs
with good uplink channel quality.
UE Location No No No No Yes
MAXCI Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission
queues. The retransmission processes are sorted in first-in first-out (FIFO) mode. The initial
transmission queues are sorted in the CQI order. A higher CQI means a higher data priority.
The MAXCI algorithm aims to maximize the system capacity but cannot ensure user fairness
and differentiated services.
The UE estimates the CQI based on the assumption that the transmit power of the HS-PDSCH
on the network side is as follows:
where
RR Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission
queues. The retransmission processes are sorted in FIFO mode. The initial transmission queues
are sorted in the order of the waiting time in the MAC-hs queue. A longer waiting time means
a higher data priority.
The RR algorithm aims to ensure user fairness but cannot provide differentiated services. Not
considering the CQI reported by the UE leads to lower system capacity.
PF Algorithm
The retransmission processes unconditionally have higher priorities than the initial transmission
queues. The retransmission processes are sorted in FIFO mode. The initial transmission queues
are sorted in the order of R/r. Here, R represents the throughput corresponding to the CQI reported
by the UE, and r represents the throughput achieved by the UE. A greater R/r value means a
higher data priority.
The PF algorithm aims to make a tradeoff between system capacity and user fairness. It provides
the user with an average throughput that is proportional to the actual channel quality. The system
capacity provided by PF is between the system capacity provided by RR and that provided by
MAXCI.
EPF Algorithm
The EPF algorithm (WRFD-01061103 Scheduling based on EPF and GBR) is an enhanced
algorithm developed based on the PF algorithm. The EPF algorithm defines more priorities than
the PF algorithm to better meet the QoS requirements of different services. The EPF algorithm
can meet the requirements of telecom operators related to user fairness and differentiated services
and also provide a high system capacity.
The EPF algorithm follows certain criteria to prioritize queues:
l Service types are the first to be considered. They are prioritized in a sequence: SRB and
IMS > voice services > streaming services > BE services.
l Different services of the same type are prioritized as follows:
– Retransmission queues are prioritized over initial transmission queues.
– Guaranteed bit rate (GBR) queues that have not arrived are prioritized over GBR queues
that have already arrived.
– Queues with high SPI weights are prioritized over those with low SPI weights.
– High bit rate (HBR) queues that have not arrived are prioritized over HBR queues that
have already arrived.
User fairness is implemented in EPF as follows:
l EFP algorithm guarantees the user fairness in the same way as that PF algorithm. HBR and
Resource Limit is used in EPF to limit the use of single users and improve fairness.
l HBR is used to determine the throughput expected by the user based on a study on user
experience.
– When the rate for a user reaches the HBR, the scheduling probability for the user is
decreased. The HBR is specified by the parameter HappyBR(BSC6900,BSC6910) on
the RNC side.
l Resource Limit is used to prevent the users in areas with poor coverage from consuming
too many cell resources so that there is no decrease in system capacity.
– When the resource limitation switch (RscLmSw) is on, the algorithm allocates the
lowest priority to a queue whose power consumption exceeds the threshold. If the power
available to the queue is limited, the queue's priority is always considered as meeting
the GBR. The ratio of the maximum available power of a queue to the total power of
the cell is specified by the NodeB MML command SET
ULOCELLRSCLMTPARA.
Differentiated service is implemented in EPF as follows:
For details on the parameters related to QoS management, such as the GBR, SPI, SPI weight,
and HBR, see QoS Management Feature Parameter Description.
EPF_LOC Algorithm
UEs' location in a cell can be defined as a near, middle, or far distance from the NodeB. HSDPA
UEs closer to the NodeB have better channel environments and report higher CQIs, as shown
in Figure 4-2.
With the EPF/PF algorithm, UEs that have the same SPI weight value but are at different
distances from the NodeB have roughly equal scheduling opportunities.
CQIs indirectly reflect UE locations. A CQI reported by a UE implies the UE's location, a near,
middle, or far distance either between the UE and the NodeB, or between the UEs within a cell.
Assuming that there are two UEs far from the NodeB and the CQIs reported by them are 15 and
13, respectively, the UE that reports the CQI 15 has more scheduling opportunities and higher
downlink throughput.
NOTE
The PF and EPF algorithms consider the value R/r, where R is the throughput corresponding to the CQI
reported by the UE. The EPF_LOC algorithm is based on the EPF algorithm. In addition to R/r, the
EPF_LOC algorithm also considers UE locations indicated by CQIs.
If a larger value is set for the LOCWEIGHT parameter, UE locations weigh more in the
EPF_LOC algorithm. Theoretically, this results in a higher downlink throughput of the cell and
greater differentiation between UEs at different distances from the NodeB. UEs closer to the
NodeB have more scheduling opportunities and higher throughput, which is the other way
around for UEs farther from the NodeB.
l UEs closer to the NodeB have more scheduling opportunities and therefore higher
throughput. This improves the cell throughput.
l UEs farther from the NodeB have fewer scheduling opportunities and therefore lower
throughput.
To ensure user experience at cell edges, it is recommended that GBRs be configured for all BE
services. To configure GBRs, run the SET UUSERGBR command on the RNC.
NOTE
The EPF_LOC algorithm gives more scheduling opportunities to UEs closer to the NodeB and
increases the downlink overall throughput of the cell. Cell throughput gains relate to UEs' CQIs.
With EPF_LOC algorithm, HSDPA UEs at cell edges have fewer scheduling opportunities and
lower throughput. If GBRs are not configured for BE services, HSDPA UEs at cell edges may
have to wait a long time before they have scheduling opportunities. As a result, traffic radio
bearers (TRBs) are more likely to reset and the call drop rate increases. The magnitude of this
impact depends on factors such as UE location distribution and service distribution in the cell.
It is recommended that GBRs be configured for BE services to ensure network performance.
After scheduling, HSDPA users will be allocated to different time and code. Figure 4-3 shows
the time division and code division over the air interface for HSDPA users in one cell.
Figure 4-3 HSDPA scheduling based on time division and code division
The feature of time and HS-PDSCH codes multiplex enables the allocation of different codes
in the same TTI to different users or the time division multiplexing of the same code in different
TTIs for different users to provide the utilization of code resources and the system throughput.
The parallel data transmission of multiple users over HS-DSCH requires more HS-SCCH codes
and HS-PDSCH codes within a single TTI. Code multiplexing is adopted and is found useful
when the NodeB has more HS-PDSCH codes for allocation than those supported by the UE. For
instance, the UE supports 5 codes and the NodeB has 10 codes available in a single TTI. The
code multiplexing can increase the resource utilization and system throughput.
4.4 HARQ
The main purpose of introducing HARQ is to reduce the retransmission delay and improve the
retransmission efficiency. HARQ enables fast retransmission at the physical layer. Before
decoding, the UE combines the retransmitted data and the previously received data, making full
use of the data transmitted each time. In addition, HARQ can fine-tune the effective rate to
compensate for the errors made by TFRC section.
l If the UE reports an ACK, the NodeB transmits the next new data.
l If the UE reports an NACK, the NodeB retransmits the original data. After receiving the
data, the UE performs soft combining of this data and the data received before, decodes
the combined data, and then reports an ACK or NACK to the NodeB.
RLC retransmission on the DCH involves the RNC, and therefore the RTT is relatively long. In
comparison, HARQ involves only the physical layer and MAC-hs of the NodeB and those of
the UE, and therefore the RTT is reduced to only 6 TTIs (12 ms).
After a transmission, the HARQ process must wait at least 10 ms before it can transmit the next
new data or retransmit the original data. Therefore, to improve transmission efficiency, other
HARQ processes can transmit data during the waiting time. A maximum of six HARQ processes
can be configured in each of the NodeB HARQ entity and the UE HARQ entity. Note that not
all UE categories support six HARQ processes. For example, the UEs of some categories can
receive data every one or two TTIs. Therefore, only two or three HARQ processes can be
configured. The RAN can automatically choose the most appropriate configuration based on UE
capability.
For HARQ retransmission between the NodeB and the UE, two combining strategies are
available. They are Chase Combining (CC) and Incremental Redundancy (IR). In the case of
CC, all retransmitted data is the same as previously transmitted data. In the case of IR, the
retransmitted data may be different from the previously transmitted data. In comparison, IR has
a higher gain than CC but requires more buffer space. CC can be regarded as a special case of
IR. The IR strategy is hard-coded in Huawei RAN.
Overview
High-speed dedicated physical control channel (HS-DPCCH) preamble is a feature that enables
the transmission of a special preamble subframe before an ACK/NACK subframe on the HS-
DPCCH or a special postamble subframe after an ACK/NACK subframe.
Item Requirement
CN None
Item Requirement
Basic Principle
The HS-DPCCH carries uplink feedback signaling related to downlink HS-DSCH transmission.
The signaling consists of Hybrid-ARQ Acknowledgement (HARQ-ACK) and Channel-Quality
Indication (CQI).
Before the HS-DPCCH preamble feature was introduced,
l If a UE receives correct information on the HS-SCCH sent from the NodeB, the UE checks
whether data transmitted on the HS-PDSCH is correctly received, and then reports ACK/
NACK to the NodeB in the first timeslot of subframes on the HS-DPCCH.
l If a UE does not receive correct information on the HS-SCCH sent from the NodeB, the
UE will not send any data to the NodeB in the first timeslot of subframes on the HS-DPCCH.
In the case of interference, the NodeB considers that the UE is in DTX mode. As a result,
the NodeB may decode data transmitted on the HS-DPCCH as ACK/NACK by mistake.
More interference indicates a higher probability that the NodeB decodes data by mistake.
According to section "8.11.2.1 Definition and applicability" in 3GPP TS 25.141 V9.11.0,
the rate of data decoded by mistake cannot exceed 1%. To reduce the rate of data decoded
by mistake, the UE should increase the ACK/NACK transmit power.
The HS-DPCCH preamble feature provides an enhanced way to reduce decoding errors. A
special preamble is sent before an ACK/NACK on the HS-DPCCH. In this way, the probability
of mis-decoding is reduced, because a decoding error can occur only when the NodeB decodes
at least two successive timeslots erroneously. As a result, the same performance of the HARQ-
ACK field detection function is maintained with lower power.
l Determining the amount of data that can be transmitted by the queue or queues
l Determining the modulation scheme of the queue or queues
l Allocating appropriate power and channelization codes to the queue or queues
1. Based on the capabilities of UEs whose data is buffered in the scheduled MAC-hs queue,
the algorithm searches for the corresponding TFRC mapping table.
2. Based on the CQI reported by the UE, available power, and available channelization codes,
the algorithm searches the TFRC mapping table for the TBSmax, that is, the maximum
MAC-hs transport block size (TBS). Note that the available power for every HSDPA user
is restricted by MXPWRPHUSR.
3. Based on the TBSmax and the amount of data buffered in the queue, the algorithm
determines the most appropriate MAC-hs TBS (TBSused).
If the data buffered in the MAC-hs queue is enough to fill the space for carrying data in a
transport block with the TBSmax, then the TBSmax is taken as the TBS to be used
(TBSused). The TBSmax, however, may be much larger than the data buffered in the MAC-
hs queue. If this TBS is used, too many padding bits reduce the spectrum efficiency. To
solve this problem, the algorithm searches the TFRC mapping table backward for the CQI
or the number of codes to obtain the most appropriate TBS and the corresponding
modulation scheme. This TBS should be the smallest one in the TBS set that can carry the
buffered data. The power and code resources determined through backward searching are
taken as the ones for allocation.
4. Based on the TBSused, the algorithm determines the most appropriate power, codes, and
modulation scheme.
Huawei supports three backward-searching methods, which are specified by the parameter
RscAllocM on the NodeB side:
l If the parameter is set to Code_Pri, the TFRC algorithm prefers the use of codes. Under
the precondition that the transport block with the TBS is large enough to carry the buffered
data, the algorithm first reduces the power. If the corresponding CQI decreases to the
smallest one but the precondition is still met, the algorithm attempts to reduce the number
of codes. This setting is applicable the outdoor macro base station with limited power.
l If the parameter is set to Power_Pri, the TFRC algorithm prefers the use of power. Under
the precondition that the transport block with the TBS is large enough to carry the buffered
data, the algorithm first reduces the number of codes. If the number of codes decreases to
1 but the precondition is still met, the algorithm attempts to reduce the power. This setting
is applicable to indoor application with limited codes.
l If the parameter is set to PowerCode_Bal, the TFRC algorithm balances the use of power
and the use of codes. Under the precondition that the transport block with the TBS is large
enough to carry the buffered data, the algorithm reduces the power and codes in a balanced
mode. This setting protects the codes or power from being used up, improving the resource
usage and increasing the cell capacity.
Figure 4-6 shows the backward-searching methods used when the parameter is set to
Code_Pri or Power_Pri.
Figure 4-6 Backward-searching methods used when the parameter is set to Code_Pri or
Power_Pri
Figure 4-7 shows the backward-searching methods used when the parameter is set to
PowerCode_Bal.
Figure 4-7 Backward-searching methods used when the parameter is set to PowerCode_Bal
The enhanced HSDPA code utilization function helps fully utilize the remaining code resources.
When the RscAllocM parameter (determining the backward-searching method) is set to
PowerCode_Bal, the TFRC selection algorithm prefers the use of codes for the last queue
carrying streaming, interactive, or background data of a UE in CELL_DCH state (including
initial transmission and retransmission) in a TTI. Under the precondition that the transport block
with the TBS is large enough to carry the buffered data, the enhanced HSDPA code utilization
function first reduces the power. If the corresponding CQI decreases to the smallest one but the
precondition still persists, the enhanced HSDPA code utilization function does not attempt to
reduce the number of codes but uses the current codes and power to transmit the buffered data.
The enhanced HSDPA code utilization function increases code utilization, reduces downlink
cell load, and improves downlink channel quality without lowering cell capacity, thereby
enhancing user experience. The enhanced HSDPA code utilization function also alleviates the
increase of downlink cell load caused by the HSDPA remaining power appending algorithm.
When the licensed HSDPA codes are insufficient, the enhanced HSDPA code utilization
function may aggravate code resource congestion and reduce cell capacity, even if the cell has
remaining power resources. In this situation, it is good practice to expand the capacity of licensed
HSDPA codes and then enable the function. For details, see section 8.20.1 When to Use
Enhanced HSDPA Code Utilization.
The enhanced HSDPA code utilization function is controlled by the CODEOPTSW parameter
of the SET ULOCELLMACHSPARA command.
This function requires HSDPA-capable UTRAN and UEs, but is not applicable to MIMO-
enabled UEs, UEs enabled with the HS-SCCH less operation function, or E-FACH UEs.
NOTE
The enhanced HSDPA code utilization function does not take effect when the RscAllocM parameter is set
to Code_Pri or Power_Pri on the NodeB side.
The HSDPA remaining power appending algorithm helps fully utilize the remaining power
resources. This algorithm appends certain power to the HS-PDSCH power calculated by the
TFRC selection algorithm if the last queue in a TTI carries streaming, interactive, or background
data of a UE in CELL_DCH state (including initial transmission and retransmission). After the
introduction of the HSDPA remaining power appending algorithm, the NodeB parameter
EXTRAPOWER is added to the SET ULOCELLMACHSPARA command for specifying the
maximum amount of power that can be allocated to HS-PDSCH power from the remaining power
resources in the cell in question. This parameter is in units of 0.25 dB. The value of this parameter
must be equal to or less than the cell remaining power in a TTI.
With the increase in downlink power, the downlink load is also increased. When the downlink
load becomes heavy, network KPIs are deteriorated. Therefore, the EXTRAPOWER parameter
cannot be set to a too large value.
Before enabling the HSDPA remaining power appending algorithm, ensure that HSDPA has
been enabled on the network and that UEs support HSDPA.
NOTE
When the EXTRAPOWER parameter is set to 0, the HSDPA remaining power appending algorithm does
not take effect.
When the CQI adjustment based on a fixed BLER target algorithm is enabled on the NodeB, the HSDPA
remaining power appending algorithm does not take effect. IBLER stands for initial block error rate.
Overview
The CQI measures the channel conditions of a UE and is reported from the UE to the NodeB.
Without this feature, the NodeB determines an appropriate TBS based on the reported CQI,
system resources, and the TFRC policy. If the reported CQI and related conditions remain the
same, the NodeB does not change the TBS because it does not consider the ever-changing radio
environments.
The constant changes in radio environments, caused by multipath effects and UE mobility, lead
to fluctuating channel quality. Under these circumstances, choosing a TBS based on the reported
CQI makes it difficult to always achieve the optimum downlink throughput.
With the feature CQI adjustment based on dynamic BLER target, the NodeB monitors the
channel quality fluctuations for HSDPA users in a cell in real time and dynamically selects a
proper BLER target based on the monitoring result. The NodeB then uses the BLER target to
adjust the CQI reported by the UE. Based on the adjusted CQI, the NodeB determines an
appropriate TBS to achieve higher downlink throughput for HSDPA users and higher cell
throughput.
NOTE
The BLER described in this section refers to the SBLER at the MAC-(e)hs layer and reflects the average
block error rate at the MAC layer. Accordingly, the BLER target described in this section refers to the
SBLER target at the MAC-(e)hs layer.
The required BLER target may be high in some environments; therefore this feature is not
suitable for networks that limit the BLER target.
This feature requires that both the network and UE support HSDPA. This feature is applicable
to all HSDPA terminals except for the terminals that are configured with MIMO. Different
terminals may have different performance for the same TB size. Some terminals may have
greater BLERs. This feature adjusts the TB size for terminals based on data transmission
performance to achieve optimized performance.
This feature can be enabled by selecting the CQI_ADJ_BY_DYN_BLER check box under the
CQIADJALGOFNONCON parameter.
1. Based on the CQI reported by the UE, the NodeB checks the actual radio environment,
which is affected by multipath effects and UE mobility.
2. Based on the actual radio environment and channel quality of the UE, the NodeB obtains
an optimum BLER target, which helps to achieve the highest possible throughput for the
UE.
3. Based on the ACK, NACK, or DTX indication from the UE in the current TTI and on the
optimum BLER target, the NodeB calculates the CQI offset, which can be a positive or
negative number. The NodeB then uses the CQI offset to adjust the CQI.
4. Based on the adjusted CQI, the NodeB selects an appropriate TBS by using the TFRC
algorithm.
As shown in Figure 4-8, downlink data transmission has been started at TTIm but the CQI
measured at TTIn is used at TTIm. At TTIn, the UE measured the CQI without estimating the
interference caused by sudden load changes. In this case, the BLER at TTIm is high. This prolongs
the delay in initiating data transmission and negatively affects burst service throughput.
Figure 4-8 Delay prolongs due to the reporting and processing of the CQI
To address the TTI inaccuracy issue, the BLER Optimization for HSDPA Burst Services
function is introduced. This function performs the following operations:
Through the preceding operations, this function ensures that the reported CQI matches the
current channel quality when the UE is engaged in initial HSDPA data transmission or processing
downlink burst services. In this way, this function decreases the BLER at TTIm and increases
burst service throughput.
The BLER Optimization for HSDPA Burst Services function is controlled by the
BURSTBLEROPTSW parameter in the SET ULOCELLMACHSPARA command.
To use this function, the target network must support HSDPA and some UEs are HSDPA-
capable. This function takes effect on all HSDPA-capable UEs.
NOTE
Before using this function in RAN15.0, set the pilot power to 10% of the cell's maximum transmit power
(usually, the pilot power is -10 dB) and the maximum power output (MPO) constant to the default value
2.5 dB.
l When the UE is in the unfavorable radio environment, the transmission can adopt the low-
order QPSK modulation mode and small transport blocks to ensure communication quality.
l When the UE is in the favorable radio environment, the transmission can adopt the high-
order 16QAM modulation scheme and large transport blocks to reach a high peak rate.
QPSK modulation is a basic downlink data modulation function that is used after HSDPA is
introduced.
Compared with the QPSK modulation scheme, the 16QAM modulation scheme is a higher-order
downlink data modulation scheme. This feature enables the peak rate on the Uu interface to
reach 14.4 Mbit/s.
64QAM
3GPP R5 introduces 16QAM to increase the peak rate per user and expands the system capacity,
whereas 64QAM introduced in 3GPP R7 protocols is a further enhancement of 16QAM.
With downlink 64QAM, a higher-order modulation scheme than 16QAM can be used when the
channel is of higher quality. Theoretically, 64QAM supports a peak data rate of 21 Mbit/s and
at the same time increases the average throughput of the system. Simulation shows that compared
with 16QAM, 64QAM can increase the average throughput by 7% and 16% respectively in
macro cell and in micro cell, if the UEs in the cells use the type 3 receivers.
The 3GPP R7 protocols define the categories of the UEs that support 64QAM, and add the
information elements (IEs) that support 64QAM in the reporting of local cell capability. The
RNC determines whether the RL between the NodeB and the UE supports 64QAM according
to the local cell capability reported by the NodeB and the UE capability. If the RL supports
64QAM, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use 64QAM
according to the following aspects:
Compared with the 16QAM modulation scheme, the 64QAM modulation scheme is a higher-
order downlink data modulation scheme. This feature enables the peak rate on the Uu interface
to reach 21 Mbit/s.
l The conversational service (including the CS voice and VoIP) has a relatively high
requirement for service delay and a certain requirement for BLER.
l The streaming service has a requirement for guaranteed bit rate (GBR).
l The FTP service has a high requirement for BLER and error-free transmission. In addition,
this service requires higher service rates to provide better user experience.
l The HTTP service has a high requirement for error-free transmission and a certain
requirement for response delay. In addition, this service requires shorter delay to provide
better user experience.
HSDPA QoS management is implemented by related HSDPA functions. The following table
lists the relationships between HSDPA functions and QoS indicators.
Mobility √
management
HSDPA bearer √ √
mapping
Load control √ √ √
RLC √
retransmission
Flow control √ √ √
Congestion √
control
HARQ √
MAC-hs √ √ √
scheduling
TFRC selection √
These relationships between HSDPA functions and QoS indicators are described as follows:
l Mobility management
Service continuity is implemented by mobility management.
For details, see section 3.4 Mobility Management and Handover Feature Parameter
Description.
l Bearer mapping
HSDPA bearers increase the service rate greatly and reduce the service delay.
For details, see section 3.1 Bearer Mapping.
l Load control
The network resources are limited. Therefore, when a large number of users attempt to
access the network, the access control function is required to control the access to ensure
the QoS of the admitted users.
The network resources consumed by the admitted users vary with the changed channel
qualities, which may lead to network congestion. To relieve congestion, the overload
control function is required to ensure the QoS of most users.
For details on load control, see Load Control Feature Parameter Description.
l RLC retransmission and HARQ
To achieve error-free transmission and improve transmission efficiency, HSDPA
introduces HARQ at the physical layer. HARQ, however, cannot completely ensure error-
free transmission. Therefore, it should work with RLC retransmission and TCP
retransmission.
For details, see sections 4.2 Impact of HSDPA on the RLC and MAC-d Entities and 4.4
HARQ.
l Flow control and congestion control
By allocating appropriate Iub bandwidth to users, the flow control function reduces the
transmission time. Therefore, it prevents too much data from waiting in the buffer at the
MAC-hs and avoids unnecessary RLC retransmissions. In addition, it protects service data
from overflowing from the buffer at the MAC-hs.
Through congestion detection and congestion control, the congestion control function
reduces the packet loss probability.
For details, see section 4.1 Flow Control and Congestion Control.
l MAC-hs scheduling
Based on the waiting time, achieved service rate, and GBR, the MAC-hs scheduling
function sorts the users to meet the requirements for transmission delay and transmission
rate on the Uu interface. For details, see section 4.3 MAC-hs Scheduling.
l TFRC selection
Based on the available power, available codes, actual channel quality, and actual data
amount, the TFRC selection function selects appropriate transport blocks and modulation
schemes to increase data rates. For details, see section 4.5 TFRC Selection.
6 Related Features
Impacted Features
l WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
When an HSDPA cell is not configured with its baseline pilot power, the BLER increases
in certain scenarios, which leads to decreased throughput. In such scenarios, the MPO can
be modified based on the pilot power to decrease the BLER. However, it is recommended
that the CQI Adjustment Based on Dynamic BLER Target feature be enabled to ensure a
low BLER in different power configuration scenarios.
Impacted Features
l WRFD-160103 Terminal Black List
When the WRFD-160103 Terminal Black List feature is enabled, the RNC can add some
UEs to the blacklist to prevent these UEs' SRB from carrying on the HSDPA channels.
Impacted Features
None
Impacted Features
None
Impacted Features
l WRFD-030011 MIMO Prime
l WRFD-010684 2x2 MIMO
l WRFD-010693 DL 64QAM+MIMO
l WRFD-010699 DC-HSDPA+MIMO
l WRFD-150223 4C-HSDPA+MIMO
l WRFD-150227 DB-HSDPA+MIMO
When one or more MIMO-related features are enabled and the last priority queue to be
scheduled is of the MIMO user type, the enhanced HSDPA code utilization function does
not take effect. If the MIMO user proportion is high, gains yielded by the enhanced HSDPA
code utilization function are decreased.
7 Network Impact
Network Performance
The HSDPA Introduction Package feature provides:
l Maximized power resource utilization
HSDPA Introduction Package adjusts the downlink power and data rate based on channel
quality, maximizing the power resource utilization.
l Shorter delay
With TTIs of 2 ms and 10 ms, which provide shorter scheduling intervals, the fast
scheduling algorithm enables the NodeB to quickly schedule and retransmit data.
l Higher uplink cell throughput
HARQ helps increase the downlink cell throughput.
introduced to replace the A-DPCH and carry only TPC commands, thereby saving downlink
non-HSDPA power resources. An F-DPCH can be shared by up to 10 UEs, thereby saving
downlink code resources.
l Increased CPU resource consumption on BSC6900 interface boards
SRB over HSDPA doubles the number of session setups in scenarios such as service setup,
handover, and state transition from CELL_FACH to CELL_DCH, thereby increasing CPU
resource consumption on BSC6900 interface boards (excluding FG2a and GOUa boards).
The reasons are as follows:
According to sections 11.2.4 "DCH Transport Channel", 11.2.7 "HS-DSCH Transport
Channel", and 11.2.8 "E-DCH Transport Channel" in 3GPP TS 25.401 V9.0.0, if downlink
SRBs are carried on the HS-DSCH while uplink SRBs are carried on the DCH or E-DCH,
two Frame Protocol (FP) entities need to be set up for SRBs. In this case, two data flows
need to be set up, of which one for transmitting uplink data and the other for downlink data.
As a result, two sessions need to be set up. If both the uplink and downlink SRBs are carried
on the DCH, only one FP entity needs to be set up for transmitting uplink and downlink
data.
As session setup has been optimized for FG2a and GOUa boards in the BSC6900 and all
interface boards in the BSC6910, SRB over HSDPA will not increase CPU resource
consumption on these boards.
CPU resources consumed by each UE increase by 30% on interface boards after SRB over
HSDPA is enabled. For example, a UE uses 0.1% of CPU resources to set up a service
before SRB over HSDPA is enabled. After this feature is enabled, the UE uses 0.13% of
CPU resources to set up a service. CPU usage on interface boards is directly proportional
to the number of UEs whose downlink SRBs are carried on the HS-DSCH.
Network Performance
Compared with SRB over DCH, SRB over HSDPA has the following impacts:
enabled, SRB over HSDPA may deteriorate the HSDPA call drop ratio by more than
10%.
– Increase transmit power on the HS-DSCH carrying SRBs during the TFRC selection.
(For detailed operations, see section 4.5 TFRC Selection) The proportion of resources
consumed by downlink SRBs is small compared with the total amount of resources
consumed by downlink SRBs and TRBs. Therefore, increasing transmit power slightly
reduces the gains produced by this feature in downlink capacity. This impact can be
ignored.
Network Performance
Calculation for adjusting the CQI increases the downlink load of the NodeB DSP slightly.
Network Performance
With this feature, HSDPA UEs at cell edges have fewer scheduling opportunities and lower
throughput. If GBRs are not configured for BE services, HSDPA UEs at cell edges may have
to wait a long time before they have scheduling opportunities. As a result, traffic radio bearers
(TRBs) are more likely to reset and the call drop rate increases. The magnitude of this impact
depends on factors such as UE location distribution and service distribution in the cell. It is
recommended that GBRs be configured for BE services to ensure network performance.
Network Performance
Average HSDPA cell load is reduced by up to approximately 3%. When the HSDPA user queue
buffer has data to transmit, HS-PDSCH transmit power is reduced by approximately 5% to 10%.
When the HSDPA user queue buffer has data to transmit, HS-PDSCH code utilization is
increased by approximately 5% to 20%.
The CS/PS call drop rate and CS/PS RAB establishment success rate may increase slightly due
to the reduced downlink cell load.
8 Engineering Guidelines
Requirements
l Dependencies on Hardware
For the NodeB:
– The NDLP and NBBI boards in the NodeB do not support this feature.
– The DBS3800 must be configured with the HBBU/EBBC/EBBCd board or all these
boards. These boards must support HSDPA.
– The BTS3812E and BTS3812AE must be configured with the HBBI, EBOI, or EBBI
board. Alternatively, they must be configured with at least one HDLP/EDLP/EDPLd
board and one HULP/EULP/EULPd board.
– The 3900 series base stations support HSDPA.
l Dependencies on Other Features
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 6: In RAN Sharing scenarios, a feature is activated for the primary and secondary
operators separately. In MOCN scenarios, a feature is activated only for the primary
operator. The licensed values can be set by running the SET LICENSE command.
l Dependencies on the Transport Network
After HSDPA is introduced, the downlink peak data rate per user can reach 14.4 Mbit/s.
In this case, the bandwidth of an Iub over ATM transport network must reach 20 Mbit/s or
higher and the bandwidth of an Iub over IP transport network must reach 18 Mbit/s or
higher. However, the Iub bandwidth in commercial networks must be higher because R99
services exist in these networks. For the specific Iub bandwidth in a commercial network,
you must refer to the results of network planning and network optimization.
l Others
The UE is HSDPA-capable.
Data Preparation
Table 8-1 lists the data to prepare before deploying HSDPA Introduction Package.
Step 2 Run the RNC MML command ADD UCELLHSDPA. In this step, set Code Number for HS-
PDSCH and Code Max Number for HS-PDSCH to 15 and set other HSDPA-related
parameters based on the network plan.
Step 3 Run the RNC MML command ACT UCELLHSDPA to activate this feature.
NOTE
1. Run the RNC MML command ADD ATMTRF to configure new records of ATM
traffic based on network planning requirements.
2. Run the RNC MML command LST TRMMAP to query the transmission resource
mapping.
3. Run the RNC MML command ADD AAL2PATH to set associated parameters
according to the network plan. TX traffic record index and RX traffic record index of
the AAL2 path to be added must be the same as those set in the ADD ATMTRF
command. In addition, AAL2 Path Type should be set according to the mapping between
service types and AAL paths.
4. Run the NodeB MML command ADD AAL2PATH to configure an AAL2 path for
HSDPA based on network planning requirements.
l In an IP network:
1. Run the RNC MML command LST ADJMAP to query whether resource management
mapping is configured for the adjacent node.
If configured, check the TRMMAP index of the adjacent node.
If not configured, run the RNC MML command LST TRMMAP to query the default
TRMMAP ID used by the adjacent node based on the settings of Interface Type and
Transport Type. For example, if Interface Type is set to Iub Interface, then the value
for TRMMAP ID will be 1.
2. Run the RNC MML command LST TRMMAP to check whether the IP path mapping
to the HSDPA service is configured according to the TRMMAP ID used by the adjacent
node.
If configured, no further action is required.
If not configured, run the RNC MML command ADD IPPATH to configure the IP path
mapping to the HSDPA service.
----End
NOTE
To ensure that HSDPA services can be successfully set up, HSDPA services must be mapped to the
corresponding AAL2 paths or IP paths. To prevent ongoing services from being affected, you can add new
AAL2 or IP paths.
The following ATM configurations are recommended:
l To enable the peak data rate per user to reach 14.4 Mbit/s, the Synchronous Transport Module level-1
(STM-1) standard must be complied with. Note that the ATM over multi-E1 transmission scheme
cannot support a peak data rate per user of 14.4 Mbit/s.
l The bandwidth of AAL2 paths is 20 Mbit/s and the bandwidth of intermediate transmission devices is
not lower than 20 Mbit/s.
The following IP configurations are recommended:
l To enable the peak data rate per user to reach 14.4 Mbit/s, the bandwidth of IP paths is 18 Mbit/s and
the bandwidth of intermediate transmission devices is not lower than 18 Mbit/s.
l For IP RANs, the recommended IP bandwidth is 18 Mbit/s because the physical bandwidth of IP paths
must be higher than the Uu-interface data rate. For port configurations on the two ends in IP RANs,
the port data rate must be 100 Mbit/s and the full duplex mode must be used.
l MML Command Examples
//Modifying the protocol version for a NodeB
MOD UNODEB: NodeBId=1, NodeBProtclVer=R9;
When configuring the HSUPA Introduction Package 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 8-2, Table 8-3, and
Table 8-4. 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
Table 8-2 Configuring the parameters on the CME (Activating HSDPA Introduction Package)
Code HsPdschCodeNum
Number for (BSC6900,BSC6910
HS-PDSCH )
Service type ST
(BSC6900,
BSC6910)
Rate unit UT
(BSC6900,
BSC6910)
Minimum MCR
cell rate (BSC6900,
BSC6910)
2 TRMMAP RNC - - No
NOTE
Use this MO to query
transport resource
mapping.
Bearing CARRYT
type (BSC6900,
BSC6910)
Bearing CARRYF
subrack No. (BSC6900,
BSC6910)
TX traffic TXTRFX
record index (BSC6900,
BSC6910)
RX traffic RXTRFX
record index (BSC6900,
BSC6910)
Slot No. SN
Subboard SBT
Type
Bearer Port PT
Type
Join JNRSCGRP
Transmissio
n Resource
Group
VPI VPI
VCI VCI
Rate Unit RU
Bearer ST
Service
Type
Receive RCR
Cell Rate
1 ADJMAP RNC - - No
NOTE
Use this MO to check
whether transport
resource mapping is
configured for an
adjacent node.
2 TRMMAP RNC - - No
NOTE
Use this MO to query
transport resource
mapping.
Transport TRANST
Type
Local IP IPADDR
address
Peer IP PEERIPADD
address R
Forward TXBW
Bandwidth
Backward RXBW
Bandwidth
Activation Observation
Run the RNC MML command DSP UCELL to check whether HSDPA Introduction Package
has been activated. If the value of the Cell HSDPA State parameter is AVAILABLE(HSDPA
Available cell), this feature has been activated.
Step 2 Run the RNC MML command DSP UCELL to check whether HSDPA Introduction Package
has been deactivated. If the value of the Cell HSDPA State parameter is UNAVAILABLE
(HSDPA Unavailable cell), this feature has been deactivated.
----End
When configuring the HSUPA Introduction Package 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 8-5. 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
8.1.6 Troubleshooting
None
8.2.1 Requirements
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package must have been configured
before this feature is activated.
l 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 3#: it is recommended that the license allocation proportion of a feature be
consistent with that of the capacity license item "HSDPA Throughput-1KBPS". The
licensed values can be set by running the SET LICENSE command. If the parameter in
this command is set to AutoAssign, the licensed values are automatically allocated among
the primary and secondary operators. If the parameter in this command is set to
ManualAssign, you also need to specify the related license parameters to implement
manual license allocation.
l Other Prerequisites
The neighboring RNC supports this feature.
Hsdpa cap ind over IurHsdpaSuppInd Set this parameter to Radio network plan
IUR for NRNC (BSC6900,BSC6910 ON. (internal)
)
8.2.3 Activation
Using MML Commands
Step 1 Run the RNC MML command MOD UEXT3GCELL to configure the neighboring RNC's cell
with HSDSCH. In this step, select the HSDSCH support indicator check box under the
parameter Cell Capability Container.
Step 2 Run the RNC MML command MOD UNRNC. In this step, set Hsdpa cap ind over IUR for
NRNC to ON.
----End
When configuring the HSDPA over Iur 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
----End
8.2.5 Deactivation
Using MML Commands
Step 1 Run the RNC MML command MOD UNRNC. In this step, set Hsdpa cap ind over IUR for
NRNC to OFF.
Step 2 Run the RNC MML command MOD UEXT3GCELL. In this step, deselect the HSDSCH
support indicator check box under the parameter Cell Capability Container.
----End
When configuring the HSDPA over Iur 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 8-8. 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
The more the number the UEs supporting SRB over HSDPA on the network, the larger the gain
produced by SRB over HSDPA is. For the distribution of UEs supporting SRB over HSDPA,
contact Huawei technical support.
Requirements
l Feature
The WRFD-010610 HSDPA Introduction Package feature has been activated.
l Hardware
– Dependency on RNC hardware
None
– Dependency on NodeB hardware
For the BTS3812E, BTS3812A, and BTS3812AE, the EBBI, EBOI, or EDLP board
must be configured.
For the DBS3800, the EBBC or EBBCd board must be configured.
For the 3900 series base stations, the WBBPb, WBBPd, or WBBPf board must be
configured.
l 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 3: It is recommended that the license allocation proportion of a feature be consistent
with that of the license item "HSDPA Throughput-1KBPS". The licensed values can be set
by running the SET LICENSE command.
l Other requirements
– The RNC software version must be V900R016C00SPC620 or later.
NOTE
(For details about these two IEs, see section "RRC CONNECTION REQUEST" in
3GPP TS 25.331 V7.10.0 10.2.39.)
Figure 8-1 Support for F-DPCH and Support for Enhanced F-DPCH IEs
– The path for transmitting SRBs has been configured. The steps to check whether the
path for transmitting SRBs has been configured are as follows:
Scenarios in which ATM transmission is used
1. Run the RNC MML command LST ADJNODE to query the value of Adjacent Node
ID based on the NodeB ID and the adjacent node type (Iub interface).
2. Run the RNC MML command LST ADJMAP with the Adjacent Node ID parameter set
to the value obtained in Step 1 to query Gold user TRMMAP index, Silver user
TRMMAP index, and Bronze user TRMMAP index under the NodeB.
3. Run the RNC MML command LST TRMMAP with the TRMMAP index parameters set
to the values obtained in Step 2 to query HSDPA Signal primary path and HSDPA Signal
secondary path for gold, silver, and bronze subscribers.
NOTE
Before SRB over HSDPA is enabled, at least one of HSDPA Signal primary path and HSDPA
Signal secondary path for UEs must be set to NULL. Otherwise, run the RNC MML command
MOD TRMMAP with the HSDPA Signal primary path parameter set to EF (recommended value).
4. Run the RNC MML command LST AAL2PATH with the Adjacent Node ID parameter
set to the value obtained in Step 1 to query AAL2 Path Type.
If... Then...
The AAL2 Path Type Different types of services can share the same path
parameter is set to bandwidth. That is, the NodeB has been configured with a
SHARE path to allow SRBs to be carried over HSDPA.
The AAL2 Path Type Run the RNC MML command MOD AAL2PATH with the
parameter is set to R99 Adjacent Node ID parameter set to the value obtained in
Step 1 to set the AAL2 Path Type parameter to SHARE.
If... Then...
2. Run the RNC MML command LST ADJMAP with the Adjacent Node ID parameter set
to the value obtained in Step 1 to query Gold user TRMMAP index, Silver user
TRMMAP index, and Bronze user TRMMAP index under the NodeB.
3. Run the RNC MML command LST TRMMAP with the TRMMAP index parameters set
to the values obtained in Step 2 to query HSDPA Signal primary path and HSDPA Signal
secondary path for gold, silver, and bronze subscribers.
NOTE
Before SRB over HSDPA is enabled, at least one of HSDPA Signal primary path and HSDPA
Signal secondary path for UEs must be set to NULL. Otherwise, run the RNC MML command
MOD TRMMAP with the HSDPA Signal primary path parameter set to EF (recommended value).
4. Run the RNC MML command LST IPPATH with the Adjacent Node ID parameter set
to the value obtained in Step 1 to query the value of IP path type (the interface type is Iub
Interface).
The NodeB has been configured with a path to allow SRBs to be carried over HSDPA when
any of the following conditions is met:
l The value of IP path type contains the values of HSDPA Signal primary path and
HSDPA Signal secondary path obtained in Step 3.
l The IP path type parameter is set to QoS Path. This setting indicates that different
types of services can share the same path bandwidth.
If the preceding conditions are not met, run the RNC MML command ADD IPPATH to
set the IP path type parameter to values of HSDPA Signal primary path and HSDPA
Signal secondary path obtained in Step 3.
Data Preparation
Table 8-9 lists the data to prepare before deploying SRB over HSDPA.
Table 8-9 Data to prepare before activating the SRB over HSDPA feature
Precautions
Before enabling SRB over HSDPA, enable PS IMEI acquisition to allow the RNC to obtain the
type approval codes (TACs) of UEs. By doing this, UEs that are incompatible with SRB over
HSDPA can be blacklisted. International mobile equipment identities (IMEIs) can be obtained
in any of the following ways:
Activation
Step 2 Run the RNC MML command SET UFRCCHLTYPEPARA and set the following parameters:
l Set the Type of Channel Preferably Carrying Signaling RBparameter toHSDPA
(UL_DCH,DL_HSDSCH). If SRB over HSUPA is enabled, set this parameter toHSPA
(UL_EDCH,DL_HSDSCH).
l After this step is performed, SRB over HSDPA and F-DPCH are activated.
l If the Effective Flag of Signaling RB Channel Type parameter is set toTRUE, you need to run the
RNC MML commandSET URRCTRLSWITCHand select
theRRC_CONN_STATE_TO_NODEB_SWITCHcheck box under theFunction Switch parameter
to reduce the impact of SRB over HS-DSCH on the RAB setup success ratio.
Step 3 Run the RNC MML command MOD CELLALGOSWITCH with theCell Hspa Enhanced
function switch parameter set toE_F_DPCH_ON to enable the E-FDPCH function.
Step 4 Set the parameters related to SRB H2D and power appending to the SRB queue to counteract
the increase in the HSDPA call drop ratio:
1. Run the RNC MML command SET UCORRMALGOSWITCHand select
theDRA_BASE_COVER_LOAD_SRB_H2D_SWITCHcheck box under theDynamic
Resource Allocation Switch 2 parameter to enable the weak coverage- and low load-based
SRB H2D function.
2. Run the RNC MML command SET UCHLQUALITYEVALUATE and set the
parameters as follows:
l Set the DL Non-HSPA Power Initial Load State for SRB H2Dparameter
toDL_OVERRLOAD_STATE (recommended value). That is, set the initial state of
the downlink low non-HSPA load in the weak coverage- and low load-based SRB H2D
function to overload state.
l Set the following thresholds for determining whether UEs are located in weak-coverage
areas:
- Set the SrbOverHsdpaRscpDownThdparameter to-110 (recommended value).
- Set the SrbOverHsdpaRscpUpThdparameter to-105 (recommended value).
- Set the SrbOverHsdpaEcn0DownThdparameter to17 (recommended value).
- Set the SrbOverHsdpaEcn0UpThdparameter to23 (recommended value).
3. Run the RNC MML command SET UFRC with theFake EcNo parameter set to17
(recommended value). By doing this, the RNC determines whether UEs in access mode
are located in weak-coverage areas by using the value of this parameter when no valid Ec/
N0 is reported.
4. Run the RNC MML command SET UALGORSVPARA. In this step, set bit 5 ofReserved
Switch 11 to1 to enable SRB D2H based on coverage and load.
5. Run the RNC MML command SET UALGORSVPARA. In this step, set bit 14
ofReserved Switch 7 to0 to disable SRB H2D based on code resources.
6. Run the RNC MML command SET UALGORSVPARA. In this step, set bit 12
ofReserved Switch 11to1.
7. Run the NodeB MML command SET ULOCELLMACHSPARA with theExtra Power
For Srbparameter set to2. By doing this, the NodeB will reduce the CQI reported by a UE
by 2 dB to adjust the transmit power of the SRB queue or the size of the data block to be
sent in the SRB queue.
8. Run the RNC MML command SET UFDPCHRLPWR. In this step, setFDPCH
Maximum Reference Powerto30andFDPCH Minimum Reference Power to-150.
9. Run the RNC MML command SET UCORRMALGOSWITCH with bit31 ofCORRM
Algorithm Reserved Switch 1 set to 1.
Step 5 (Optional) If SRB over HSDPA does not require periodic retry, run the RNC MML command
SET UFRC and deselect theSRB_OVER_HSDPAcheck box under theHSPA Technologies
Retried by UEs parameter.
Step 6 Perform the following operations to blacklist UEs that are incompatible with SRB over HSDPA:
1. (Optional) Run the RNC MML command SET URRCTRLSWITCHand select
theRNC_PS_QUERY_UE_IMEI_SWITCH (PS IMEI Request Switch)check box
under theProcess Control Switch 2 parameter to enable PS IMEI acquisition.
NOTE
SN Description TAC
7 MotorolaXT890 35253105
Step 7 To reduce the risk of call drops caused by inter-RNC handovers, run the RNC MML command
MOD UEXT3GCELL and deselect theFDPCH_SUPPORTcheck box under theCell
Capability Container parameter.
Step 8 Run the RNC MML command SET UCORRMALGOSWITCH. In this step,
deselectCMP_UU_FDPCH_COMPAT_SWITCH under theCompatibility Switch
parameter to disable the compatibility processing for the UE F-DPCH capability.
Step 9 Enable the call reestablishment feature for PS services to counteract the impact on the HSDPA
call drop ratio.
1. Set the following parameters appropriately:
l Run the SET UCONNMODETIMER command to setTimer 302,Constant
302,Timer 313,Constant 313,Constant 315, andTimer 315.
l Run the SET USTATETIMERcommand to setTimer for Wait for Cell Update
Specific to PS UE.
l Run the SET USTATETIMERcommand and setHO active set update response
timer,HO PhyCh reconfiguration timer, andWait RB reconfiguration response
timer.
2. Enable the switches that control the call reestablishment function for PS services.
Run the SET URRCTRLSWITCHcommand and selectPS_RL_SETUP_SWITCH
(PS_RL_SETUP_SWITCH) underOptimization Switch.
3. Enable the switches that control the call reestablishment function triggered by RL out-of-
synchronization problems and SRB resets.
Run the SET URRCTRLSWITCHcommand and
selectSRB_RESET_RL_SETUP_SWITCH(SRB_RESET_RL_SETUP_SWITCH)
andRLFAIL_RL_SETUP_SWITCH(RLFAIL_RL_SETUP_SWITCH)
underOptimization Switch.
4. Set the timer for the Active Set Update process.
Run the SET URRCTRLSWITCHcommand and selectASU_RL_RESET_SWITCH
(ASU_RL_RESET_SWITCH)underOptimization Switch.
Run the SET USTATETIMERcommand to setHO active set update response timer.
5. Enable the switch that control the call reestablishment function triggered by measurement
control.
Run the SET URRCTRLSWITCHcommand and selectMC_RL_RESET_SWITCH
(MC_RL_RESET_SWITCH) underOptimization Switch.
6. Enable the switch that control the call reestablishment function triggered by PDU sending.
Run the SET URRCTRLSWITCHcommand and
selectTRB_RESET_RL_REEST_SWITCH underProcess Control Switch 4.
7. Enable the switch that controls the call reestablishment function triggered by physical
channel reconfiguration.
Run the SET URRCTRLSWITCHcommand and
selectPHY_RECFG_REEST_SWITCH underProcess Control Switch 4.
Run the SET USTATETIMER command to setHO PhyCh reconfiguration timer.
8. Enable the switch that controls the call reestablishment function triggered by RB setup.
Run the SET URRCTRLSWITCHcommand and
selectRB_SETUP_ENHANCE_RL_REEST_SWITCHunderProcess Control Switch
4.
9. Enable the switch that controls the call reestablishment function triggered by RB
reconfiguration during DCCC.
Run the SET URRCTRLSWITCHcommand and
selectRB_RECFG_RL_REEST_SWITCH(RB_RECFG_RL_REEST_SWITCH)
underOptimization Switch.
The RAB assignment timer on the CN side must be set to a value greater than 15s for the call
reestablishment triggered by inter-RAT handovers.
12. Enable the enhanced switch that controls whether call reestablishment can be triggered by
physical channel reconfiguration timeout.
Run the SET URRCTRLSWITCHcommand and
selectPHYCHRECFG_ENH_RL_REEST_SWITCHunderProcess Control Switch 4.
13. Enable the enhanced switch that controls whether call reestablishment can be triggered by
radio bearer reconfiguration timeout during the DCCC procedure.
Run the SET URRCTRLSWITCHcommand and
selectRBRECFG_ENH_RL_REEST_SWITCHunderProcess Control Switch 4.
14. Enable the enhanced switch that controls whether call reestablishment can be triggered by
the timeout of radio bearer reconfiguration timeout in during procedures other than DCCC.
Run the SET URRCTRLSWITCHcommand and
selectNON_DCCC_RBRECFG_RL_REEST_SWITCHunderImprovement Switch.
15. Enable the switch that controls whether call reestablishment can be triggered by security
mode setup timeout.
Run the SET URRCTRLSWITCHcommand and
selectSMC_RL_REEST_SWITCHunderImprovement Switch.
16. Run the SET URRCTRLSWITCHcommand and
selectRL_RESTORE_SWITCHunderOptimization Switch.
17. Run the SET URRCTRLSWITCHcommand and select
UE_SRB_RESET_SWITCHunderOptimization Switch.
----End
//Setting the fake Ec/N0 to 17, corresponding to the actual value –16 dB
SET UFRC: FakeEcNo=17;
//Enabling the function of adjusting the transmit power of the SRB queue and the
size of the data block to be sent in the SRB queue
//Deselecting the FDPCH_SUPPORT check box under the Cell Capability Container
parameter
MOD UEXT3GCELL: NRncId=1, CellId=1, CellCapContainerFdd=FDPCH_SUPPORT-0;
//Disabling compatibility processing for UE F-DPCH capability
SET UCORRMALGOSWITCH: CmpSwitch=CMP_UU_FDPCH_COMPAT_SWITCH-0;
//Enabling the call reestablishment feature for PS services //Modifying related
timers based on user experience
SET UCONNMODETIMER: T302=D1400, N302=3, T313=3, N313=D20,T315=D10, N315=D20;
//Setting the PS service reestablishment switches to on
SET URRCTRLSWITCH: OptimizationSwitch=PS_RL_SETUP_SWITCH-1;
//Setting the cross-Iur link reestablishment switch to on
SET URRCTRLSWITCH: PROCESSSWITCH4=IUR_RL_REEST_SWITCH-1;
//Setting the switches for triggering call reestablishment in case of out-of-
synchronization, SRB reset, and TRB reset to on
SET URRCTRLSWITCH: PROCESSSWITCH4=TRB_RESET_RL_REEST_SWITCH-1,
OptimizationSwitch=SRB_RESET_RL_SETUP_SWITCH-1&RLFAIL_RL_SETUP_SWITCH-1&RL_RESTORE
_SWITCH-1;
//Setting the active set update switch and measurement control link reestablishment
switch to on
SET URRCTRLSWITCH: OptimizationSwitch=ASU_RL_RESET_SWITCH-1&MC_RL_RESET_SWITCH-1;
//Setting the physical channel reconfiguration switch and physical channel
reconfiguration enhancement switch to on
SET URRCTRLSWITCH:
PROCESSSWITCH4=PHY_RECFG_REEST_SWITCH-1&PHYCHRECFG_ENH_RL_REEST_SWITCH-1;
//Setting the RB setup enhancement switch to on
SET URRCTRLSWITCH: PROCESSSWITCH4=RB_SETUP_ENHANCE_RL_REEST_SWITCH-1;
//Setting the RB reconfiguration switch, RB reconfiguration enhancement switch, and
non-DCCC RB reconfiguration switch to on
SET URRCTRLSWITCH: PROCESSSWITCH4=RBRECFG_ENH_RL_REEST_SWITCH-1,
OptimizationSwitch=RB_RECFG_RL_REEST_SWITCH-1,
ImprovementSwitch=NON_DCCC_RBRECFG_RL_REEST_SWITCH-1;
//Setting the switch for call reestablishment in security mode to on
SET URRCTRLSWITCH: ImprovementSwitch=SMC_RL_REEST_SWITCH-1;
//Setting the switch for call reestablishment after cancellation of an inter-RAT
handover to on
SET URRCTRLSWITCH: PROCESSSWITCH4=IRATHO_HOCANCEL_RL_REEST_SWITCH-1;
//Setting the switch UE_SRB_RESET_SWITCH to on
SET URRCTRLSWITCH: OptimizationSwitch=UE_SRB_RESET_SWITCH-1;
When configuring the SRB over HSDPA 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 8-10. For instructions
on how to perform the CME single configuration, seeCME 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,
pressF1 on the wizard interface to obtain online help.
----End
TAC TAC
Description Description
Activation Observation
l Checking whether SRB over HSDPA takes effect
Observe the value of the VS.HSDPA.SRBoH.UE.Mean.Cell counter, which measures the
average number of UEs supporting the SRB over HSDPA feature in a cell. If the counter
value is not zero, this feature takes effect on the cell.
l Checking whether the E-FDPCH function takes effect
Create a Uu interface trace task on the RNC LMT and select RB SETUP under Uu Message
Type to trace Uu interface signaling messages. Then, check the value of SlotFormat, as
shown in Figure 8-2.
If the value of SlotFormat for a UE using E-FDPCH ranges from 1 to 9, E-FDPCH takes
effect. Note that E-FDPCH may also take effect if SlotFormat is set to 0 for a UE using
this function.
Deactivation
After step 1 is performed, SRB over HSDPA and F-DPCH are deactivated.
Step 2 Run the RNC MML command MOD CELLALGOSWITCH with the Cell Hspa Enhanced
function switch parameter set to E_F_DPCH_OFF to disable E-FDPCH.
Step 3 Run the RNC MML command SET UCORRMALGOSWITCH and deselect the
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH check box under the Dynamic
Resource Allocation Switch 2 parameter to disable the weak coverage- and low load-based
SRB H2D function.
Step 4 Run the NodeB MML command SET ULOCELLMACHSPARA with the Extra Power For
Srb parameter set to 0 to disable the function of adjusting the transmit power of the SRB queue
and the size of the data block to be sent in the SRB queue.
Step 5 Run the RNC MML command SET UALGORSVPARA. In this step, set bit 5 of Reserved
Switch 11 to 0.
Step 6 Run the RNC MML command SET UALGORSVPARA. In this step, set bit 14 of Reserved
Switch 7 to 1.
Step 7 Run the RNC MML command SET UALGORSVPARA. In this step, set bit 12 of Reserved
Switch 11 to 0.
Step 8 Run the RNC MML command SET URRCTRLSWITCH to disable the call reestablishment
feature for PS services.
----End
With this feature, F-DPCH saves downlink code resources. After this feature is enabled, the
following symptoms occur in the top cells with a large number of UEs using SRB over HS-
DSCH during busy hours: The value of the VS.PdschCodeAvail.Mean counter increases
drastically.
Select the VS.HSDPA.SRBoH.UE.Mean.Cell counters whose values are greater than or equal
to 4 for all cells in either a half-hour or a one-hour period during peak hours. If the percentage
of the selected counters in all such counters exceeds 30% for a cell, the cell is a top cell. If the
number of top cells is less than 3, only a few number of UEs are using SRB over HS-DSCH,
and the gains produced by SRB over HSDPA in code resources cannot be observed.
Step 1 Perform drive tests at a place near the base station and with little path loss.
Step 2 Measure the call setup delay after SRB over HSDPA is activated.
1. Activate SRB over HSDPA.
Step 3 In the same drive test environment, measure the call setup delay after SRB over HSDPA is
deactivated.
1. Deactivate SRB over HSDPA.
2. Use the same HSDPA UE to originate a PS service.
3. Calculate the interval between the time the UE sends an RRC CONNECTION REQUEST
message and the time the UE receives an ACTIVATE PDP CONTEXT ACCEPT message.
----End
Compare the call setup delay after feature activation and deactivation to evaluate the gains
produced by SRB over HSDPA in the call setup delay. The gains produced by SRB over HSDPA
in the call setup delay vary depending on the number and size of SRBs transmitted on the HS-
DSCH during the call setup.
If SRB over HSDPA does not take effect during the RRC connection setup, SRB packets
transmitted on the HS-DSCH include such signaling messages as ACTIVATE PDP CONTEXT
ACCEPT and MEASUREMENT CONTROL during the call setup.
l Before SRB over HSDPA is enabled, the preceding messages included in SRB packets
require multiple SRB RLC packets to transmit. It takes 40 ms to transmit an SRB RLC
packet whose transport block is 148 bits in size. The larger SRBs require a longer period
to transmit.
You can run the ADD UTYPSRBDYNTF command and set the TBSIZE
(BSC6900,BSC6910) parameter to adjust the size of a transport block, and run the ADD/
MOD UTYPSRBSEMISTATICTF command and set the TTI(BSC6900,BSC6910)
parameter to change the TTI of an SRB RLC packet.
l After SRB over HSDPA is enabled, the preceding messages included in SRB packets may
require only 2 ms to transmit because the 2 ms TTI is used, reducing the call setup delay
significantly.
Scenarios Where the HSDPA RAB Setup Success Ratio Decreases and the HSDPA
Call Drop Ratio Increases
l Setting the parameters of the SRB H2D function
If SRB over HSDPA increases the HSDPA call drop ratio by 10% at least, perform the
following operations to reduce the PS call drop ratio:
– Increase the values of the SrbOverHsdpaRscpDownThd(BSC6900,BSC6910) and
SrbOverHsdpaRscpUpThd(BSC6900,BSC6910) parameters in the RNC MML
command SET UCHLQUALITYEVALUATE. Larger values indicate a higher
probability that UEs are located in weak-coverage areas. In this case, the number of
UEs whose SRBs are switched from the HS-DSCH to the DCH increases in weak-
coverage areas and low load cells, thereby controlling the increase in the PS call drop
ratio. However, the positive gains produced by SRB over HSDPA are also reduced.
– Increase the value of the SrbH2DNonHLoadState(BSC6900,BSC6910) parameter in
the RNC MML command SET UCHLQUALITYEVALUATE. A larger value
indicates a higher probability that UEs are located in low-load cells. In this case, the
number of UEs whose SRBs are switched from the HS-DSCH to the DCH increases in
weak-coverage areas and low load cells, thereby controlling the increase in the PS call
drop ratio. However, the positive gains produced by SRB over HSDPA are also reduced.
– Increase the value of the CellLdrSfResThd(BSC6900,BSC6910) parameter in the RNC
MML command MOD UCELLLDR. A larger value indicates a higher probability that
UEs are located in low-load cells. In this case, the number of UEs whose SRBs are
switched from the HS-DSCH to the DCH increases in weak-coverage areas and low
load cells, thereby controlling the increase in the PS call drop ratio. However, the
positive gains produced by SRB over HSDPA are also reduced.
The UE's rate has a significant impact on Ec/N0. Therefore, it is not recommended that you
adjust the upper and lower Ec/N0 thresholds for enabling SRBs to be carried on the HS-
DSCH. That is, it is not recommended that you modify the values of the
SrbOverHsdpaEcn0DownThd and SrbOverHsdpaEcn0UpThd parameters in the SET
UCHLQUALITYEVALUATE command.
l Blacklisting UEs that are incompatible with SRB over HSDPA
Perform the following operations to check whether call drops occur on a type of UEs in
certain a scenario:
1. Observe the counters in the following formula to check whether most of call drops
occur on HSDPA UEs:
Rate of RABs abnormally released for HSDPA UEs = VS.HSDPA.RAB.AbnormRel/
(VS.HSDPA.RAB.AbnormRel + VS.HSDPA.RAB.NormRel)
2. Observe the number of RABs abnormally released for UEs using SRB over HSDPA
to check whether most of call drops occur on theses UEs.
3. If most of call drops occur on UEs using SRB over HSDPA, check whether a type of
UEs experience the call drops in a certain scenario.
If a type of UEs experience call drops in a certain scenario, this type of UEs is incompatible
with SRB over HSDPA in such scenario. In this case, run the RNC MML command ADD
UIMEITAC and select SPECUSER_SRB_OVER_HSDPA_DISABLED_SWITCH
check box under the Special User Function Switch3 parameter to blacklist these UEs.
8.3.6 Troubleshooting
None
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".
Data Preparation
None
Activation
This feature is activated after the license controlling this feature is activated.
Activation Observation
None
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
None
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package on which the 15 Codes per Cell
feature depends has been configured.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
Table 8-11 lists the data to prepare before deploying 15 Codes per Cell.
Before running the RNC MML command MOD UCELLHSDPA, run the RNC MML command DEA
UCELLHSDPA to deactivate HSDPA, configure HSDPA, and run the RNC MML command ACT
UCELLHSDPA to reactivate HSDPA.
Before running the RNC MML command MOD UCELLHSDPA, run the RNC MML command DEA
UCELLEFACH to deactivate the enhanced CELL_FACH feature, configure enhanced CELL_FACH,
and run the RNC MML command ACT UCELLEFACH to reactivate enhanced CELL_FACH.
By default, each cell is configured with four HS-SCCH codes. If a cell has four HS-SCCH codes, the cell
can use only 14 HS-PDSCH codes. If you want to configure 15 HS-PDSCH codes for the cell, run the RNC
MML command MOD UCELLHSDPA with Code Number for HS-SCCH set to 1.
Step 1 Run the RNC MML command MOD UCELLHSDPA and set Code Number for HS-SCCH
to 1.
Step 2 Run the RNC MML command MOD UCELLHSDPA with Allocate Code Mode set to Manual
(Manual) and Code Number for HS-PDSCH set to 15.
----End
When configuring the 15 Codes per Cell 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 8-12. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
NOTE
Before configuring HSDPA-related parameters for a cell (CME single configuration: UMTS Cell
Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch modification center:
Modifying UMTS Cell Parameters in Batches), deactivate HSDPA (CME single configuration: UMTS
Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters. Set ACTSTATUS to
Deactivated; CME batch configuration: No supported), configure HSDPA, and reactivate HSDPA (CME
single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA
Parameters. Set ACTSTATUS to Activated; CME batch configuration: No supported).
Before configuring parameters related to enhanced CELL_FACH for a cell (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell HSDPA Parameters; CME batch
modification center: Modifying UMTS Cell Parameters in Batches), deactivate enhanced CELL_FACH
(CME single configuration: UMTS Cell Configuration Express > Cell Parameters > Cell Enhanced
FACH parameters. Set Validation indication to Deactivated; CME batch configuration: No supported),
configure enhanced CELL_FACH, and reactivate enhanced CELL_FACH (CME single configuration:
UMTS Cell Configuration Express > Cell Parameters > Cell Enhanced FACH parameters. Set
Validation indication to Activated; CME batch configuration: No supported).
By default, the number of HS-SCCH codes for each cell is 4. If the default number is used, the HS-PDSCH
can use only 14 SF16 codes. To enable the HS-PDSCH to use all 15 SF16 codes, set the value of Code
Number for HS-SCCH to 1 (CME single configuration: UMTS Cell Configuration Express > Cell
Parameters > Cell HSDPA Parameters; CME batch modification center: Modifying UMTS Cell
Parameters in Batches).
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
Activation Observation
Step 1 Initialize UMTS monitoring on the RNC LMT, as shown in Figure 8-3. Click Submit. A real-
time monitoring window is displayed.
Step 2 Check whether 15 SF16 codes are occupied by the HS-PDSCH in the Cell Performance
Monitoring window.
Expected result:
----End
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The configurations of the features on which this feature depends are complete. This feature
depends on the feature WRFD-010610 HSDPA Introduction Package.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
None
Activation
This feature does not need to be activated.
Activation Observation
This feature does not need to be verified.
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The configurations of the features on which this feature depends are complete. This feature
depends on the feature WRFD-010610 HSDPA Introduction Package.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
Table 8-13 lists the data to prepare before deploying HSDPA H-ARQ & Scheduling (MAX C/
I, RR, and PF).
Table 8-13 Data to prepare before deploying HSDPA H-ARQ & Scheduling (MAX C/I, RR,
and PF)
Run the NodeB MML command SET ULOCELLMACHSPARA with Scheduling Method
set to MAXCI(Max C/I Algorithm), RR(Round Robin Algorithm), or PF(PF Algorithm).
l MML Command Examples
//Activating HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF)
SET ULOCELLMACHSPARA: ULOCELLID=0, SM=MAXCI;
When configuring the HSDPA H-ARQ & Scheduling (MAX C/I, RR, and PF) 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
Activation Observation
Run the NodeB MML command LST ULOCELLMACHSPARA to query the value of the
Scheduling Method parameter.
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
Before this feature is activated, the feature WRFD-010610 HSDPA Introduction Package
must be configured.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
Table 8-15 lists the data to prepare before deploying HSDPA Static Code Allocation and RNC-
Controlled Dynamic Code Allocation.
Table 8-15 Data to prepare before deploying HSDPA Static Code Allocation and RNC-
Controlled Dynamic Code Allocation
l If Allocate Code Mode is set to Manual, set Code Number for HS-PDSCH to specify
the number of HS-PDSCH codes.
l If Allocate Code Mode is set to Automatic, set Code Max Number for HS-PDSCH to
specify the maximum number of HS-PDSCH codes and set Code Min Number for HS-
PDSCH to specify the minimum number of HS-PDSCH codes.
l MML Command Examples
//Activating HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Manual, HsPdschCodeNum=5,
HsScchCodeNum=4;
MOD UCELLHSDPA: CellId=11, AllocCodeMode=Automatic, HsPdschMaxCodeNum=5,
HsPdschMinCodeNum=1;
When configuring the HSDPA Static Code Allocation and RNC-Controlled Dynamic Code Allocation
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 8-16 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 on the wizard interface to obtain online help.
----End
Observation
Step 1 Run the RNC MML command LST UCELLHSDPA to query code allocation mode.
Step 2 On the RNC LMT, click to display Cell Performance Monitoring. Set Monitor Item to Cell
Code Tree Monitor and click Submit. The Cell Performance Monitoring tab page is displayed.
Step 3 View the number of codes allocated to the HS-PDSCH in the cell. If Allocate Code Mode is
set to Manual, the monitoring window of cell code tree usage shows that the number of codes
allocated to the HS-PDSCH remains unchanged. If Allocate Code Mode is set to Automatic,
the monitoring window of cell code tree usage shows that the number of codes allocated to the
HS-PDSCH varies with service access requests in the cell. For example, the number of codes
allocated to the HS-PDSCH increases with the increase of HSDPA access requests and decreases
with the decrease of HSDPA access requests.
----End
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package must be configured before this
feature is activated.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
Table 8-17 lists the data to prepare before deploying HSDPA Flow Control.
l When Flow Control Switch is set to STATIC_BW_SHAPING, the NodeB does not
adjust the available bandwidth for HSDPA users based on delay and packet loss on the Iub
interface. Then, subtracting Iub bandwidth used by R99 from Iub bandwidth configured,
the NodeB performs Iub shaping and distributes flow to HSDPA users.
l When Flow Control Switch is set to DYNAMIC_BW_SHAPING, the NodeB adjusts the
available bandwidth for HSDPA users based on delay and packet loss on the Iub interface.
Then, considering the data rate on the air interface, the NodeB performs Iub shaping and
distributes flow to HSDPA users.
l When Flow Control Switch is set to NO_BW_SHAPING, the NodeB does not adjust the
bandwidth based on delay and packet loss on the Iub interface. The NodeB reports the
conditions about the air interface to the RNC, and then the RNC allocates the bandwidth.
l When Flow Control Switch is set to BW_SHAPING_ONOFF_TOGGLE, the flow
control policy for the ports of the NodeB is either DYNAMIC_BW_SHAPING or
NO_BW_SHAPING in accordance with the congestion detection mechanism of the
NodeB. This flow control algorithm is recommended.
l MML Command Examples
//Activating HSDPA Flow Control and configuring the adaptive flow control algorithm
SET DLFLOWCTRLPARA: SRN=0, SN=6, BEAR=ATM, SBT=BASE_BOARD, PT=IMA, PN=0, SWITCH=
BW_SHAPING_ONOFF_TOGGLE, TD=2, DR=1, ITM=TERRESTRIAL;
When configuring the HSDPA Flow Control 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
Activation Observation
Step 1 Choose Monitor > UMTS Monitoring > Connection Performance Monitoring on the RNC
LMT. Create UL Throughput Bandwidth and DL Throughput Bandwidth tasks.
Step 2 Assume that the current Iub bandwidth is 4 MHz and the bandwidth usage is 100%. Enable an
HSDPA-capable UE1 to access the network and originate a PS service. Record the throughput
of UE1.
Expected result:
Step 3 Enable an HSDPA-capable UE2 to access the network (with the same configuration as UE1)
and originate a download service. Record the throughput of the two UEs.
Expected result:
The throughput of UE1 decreases after UE2 accesses the network. When the throughput of the
two UEs is stable, the total bandwidth of the two UEs is 4 MHz. If user priority, service type
and Security Parameter Index (SPI) of the two UEs are the same, the final ratio of the two UEs'
throughput is 1:1.
----End
Deactivation
You can deactivate the current algorithm by selecting one of the other flow control algorithms.
Requirements
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
The feature WRFD-010610 HSDPA Introduction Package that the HSDPA UE Category
1 to 28 feature depends on has been activated.
l License
This feature is controlled by the license for the WRFD-010610 HSDPA Introduction
Package feature. For details about this license, see Requirements.
Data Preparation
None
Activation
This feature does not need to be activated.
Activation Observation
This feature does not need to be verified.
Deactivation
This feature does not need to be deactivated.
Requirements
l Dependencies on Hardware
– UE should have the capability of HSDPA besides Category 11 and Category 12:
category 1,2,3,4,5,6,7,8,9,10,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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 1: Some license control items, for example, Dynamic CE Function (per NodeB),
can be allocated only through the common group. For the NodeB license allocation among
multiple operators, see License Management Feature Parameter Description.
Data Preparation
Table 8-19 lists the data to prepare before deploying DL 16QAM Modulation.
HSDPA Introduction Package must be activated before activating this feature. For the method of activating
HSDPA Introduction Package, see the section 8.1 WRFD-010610 HSDPA Introduction Package.
Run the NodeB MML command SET ULOCELLMACHSPARA with 16QAM Switch set to
OPEN(open).
l MML Command Examples
//Activating DL 16QAM Modulation
SET ULOCELLMACHSPARA: CME16QAMSW=OPEN;
When configuring the DL 16QAM Modulation 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
Activation Observation
NOTE
For the 16QAM modulation of the HSDPA UE, the NodeB license control item must be enabled.
As defined in 3GPP 25.306, the UE in category 8 can support both the QPSK and 16QAM modulation
schemes. However, only the 16QAM modulation scheme enables the throughput of category 8 UE to reach
5 Mbit/s. The throughput of category 8 UE can reach 5 Mbit/s only the radio environment is favorable.
Perform the following steps to check whether the download rate can reach 5 Mbit/s.
Step 1 Use the UE to start a PS interactive service of DL 7200 kbit/s. The PS service is carried on the
HS-DSCH. The UE keeps in Cell-DCH state.
Step 2 Start FTP (10 threads) to download given files, which are larger than 1 GB. By monitoring the
DL throughput and bandwidth, you find that the PS downloading service is normal and the bit
rate is higher than 5 Mbit/s.
----End
When configuring the DL 16QAM Modulation 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 the parameter described in Table 8-21 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 on the wizard interface to obtain online help.
----End
Requirements
l Dependencies on Hardware
This feature does not depend on the hardware.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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 1: Some license control items, for example, Dynamic CE Function (per NodeB),
can be allocated only through the common group. For the NodeB license allocation among
multiple operators, see License Management Feature Parameter Description.
Data Preparation
Table 8-22 lists the data to prepare before deploying Dynamic Code Allocation Based on NodeB.
Table 8-22 Data to prepare before deploying Dynamic Code Allocation Based on NodeB
HSDPA Introduction Package must be activated before activating this feature. For the method of activating
HSDPA Introduction Package, see the section 8.1 WRFD-010610 HSDPA Introduction Package.
Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code
Switch set to OPEN(open).
When configuring the Dynamic Code Allocation Based on NodeB 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 the parameter described in Table 8-23 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 on the wizard interface to obtain online help.
----End
Activation Observation
l Using MML commands:
Step 1 Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code
Switch set to CLOSE(close).
Step 5 Use a UE of category 8 or higher to download 200 MB files from the FTP server in the serving
cell.
Step 6 Choose Service>Trace Management>Interface Trace Task>User from the navigation tree
in the Maintenance tab page on NodeB LMT, and select (DL)Hsdpa User Enhanced Schedule
Data, as shown in Figure 8-4.
Step 8 Run the NodeB MML command SET ULOCELLMACHSPARA with Dynamic Code
Switch set to OPEN(open).
Step 9 Trace the (DL)Hsdpa User Enhanced Schedule Data message and check the value for
ucMaxPdschCodeNum. If the value is larger than 5, the feature has been enabled, as shown in
Figure 8-6.
----End
When configuring the Dynamic Code Allocation Based on NodeB 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 the parameter described in Table 8-24 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 on the wizard interface to obtain online help.
----End
Requirements
l Dependencies on Hardware
– This feature does not have any special requirements for hardware.
– UE should support the functions related to HSDPA Enhanced Package.
l Dependencies on Other Features
The WRFD-010610 HSDPA Introduction Package feature that the HSDPA Enhanced
Package feature depends has been configured.
l License
This feature is not under license control.
Data Preparation
None
Activation/Activation Observation/Deactivation
For details on how to activate, verify, and deactivate the WRFD-010611 HSDPA Enhanced
Package feature, see the following documents:
When configuring the HS-DPCCH Preamble Support 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 the parameter described in Table 8-25 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 on the wizard interface to obtain online help.
----End
Activation Observation
On the RNC LMT, start an Iub-interface message tracing task. In the tracing results, check
whether the RRC_RRC_CONN_SETUP or RRC_RB_SETUP message contains the "harq-
Preamble-Mode" IE whose value is 1, as shown in Figure 8-7.
l When SRB over DCH is achieved, the RRC_RB_SETUP message contains the "harq-
Preamble-Mode" IE whose value is 1.
l When SRB over HSDPA is achieved since the RB setup phase, the RRC_RB_SETUP
message contains the "harq-Preamble-Mode" IE whose value is 1.
l When SRB over HSDPA is achieved since the RRC connection setup phase, the
RRC_RRC_CONN_SETUP message contains the "harq-Preamble-Mode" IE whose value
is 1.
When configuring the HS-DPCCH Preamble Support 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 the parameter described in Table 8-26 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 on the wizard interface to obtain online help.
----End
Requirements
l Dependencies on Hardware
This feature does not have any special requirements for hardware.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l License
This feature is not under license control.
Data Preparation
Table 8-27 lists the data to prepare before deploying Scheduling based on EPF and GBR.
Table 8-27 Data to prepare before deploying Scheduling based on EPF and GBR
NOTE
When configuring the Scheduling based on EPF and GBR 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 the parameter described in Table 8-28 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 on the wizard interface to obtain online help.
----End
Activation Observation
Run the NodeB MML command LST ULOCELLMACHSPARA and check whether
Scheduling Method is set to EPF.
When configuring the Scheduling based on EPF and GBR 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 the parameter described in Table 8-29 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 on the wizard interface to obtain online help.
----End
This feature is not recommended if operators request a fixed target block error rate (BLER).
Requirements
l Dependencies on Hardware
– The BTS3812E and BTS3812AE must be configured with the EBBI, EBOI, or EDLP
board.
– The BBU3806 must be configured with the EBBC or EBBCd board.
– The BBU3900 must be configured with the WBBPb, WBBPd or WBBPf board.
l Dependencies on Other Features
WRFD-010610 HSDPA Introduction Package
l 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 through
both the common group and private groups. In this case, the licensed value specified by
the private group is preferentially used, and the licensed value specified by the common
group is used on a first-come, first-served basis. For the NodeB license allocation among
multiple operators, see License Management Feature Parameter Description.
Data Preparation
Table 8-30 lists the data to prepare before deploying CQI Adjustment Based on Dynamic BLER
Target.
Table 8-30 Data to prepare before deploying CQI Adjustment Based on Dynamic BLER Target
NOTE
When configuring the CQI Adjustment Based on Dynamic BLER Target 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 the parameter described in Table 8-31 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 on the wizard interface to obtain online help.
----End
Activation Observation
Run the NodeB MML command LST ULOCELLMACHSPARA. In this step, ensure that CQI
Adjust Algorithm Switch of non-Conversational Service is set to
CQI_ADJ_BY_DYN_BLER.
When configuring the CQI Adjustment Based on Dynamic BLER Target 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 the parameter described in Table 8-31 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 on the wizard interface to obtain online help.
----End
The values of the preceding counters increase after this feature is activated. Note that gains
brought by this feature vary in different scenarios.
It is recommended that you observe the gains brought by this feature in scenarios that meet the
following conditions:
In most cases, the gains can be observed in the scenarios that meet the preceding conditions. If
the gains cannot be observed, observe the gains based on drive test results.
8.16.6 Troubleshooting
None
If telecom operators intend to give up some equity among UEs for higher HSDPA cell
throughput, enable this feature for parts of or the entire network.
l The busy hour proportion is greater than 20%. Alternatively, in a day, the average traffic
volume within one hour exceeds the value of the
VS.HSDPA.MeanChThroughput.TotalBytes counter for at least 5 times.
l VS.DataOutput.Rab > Max(64 kbit/s, GBR x 1.5)
l VS.DataTtiRatio.Mean > 800
l VS.DataOutput.Mean/(VS.DataTtiRatio.Mean -
VS.HSDPA.InactiveDataTtiRation.Mean) ≥ 4000
l VS.HSDPA.UE.Mean.Cell ≥ 8
NOTE
Requirements
l Dependencies on RNC Hardware
– This feature does not depend on the RNC hardware.
l Dependencies on NodeB Hardware
– All 3900 series base stations must support this feature. To support this feature, the 3900
series base stations must be configured with the WBBPb, WBBPd, or WBBPf board.
– The DBS3800 must support this feature. To support this feature, the DBS3800 series
base stations must be configured with the EBBC or EBBCd board.
– The BTS3812E/BTS3812A/BTS3812AE supports this feature. To support this feature,
the BTS3812E/BTS3812A/BTS3812AE must be configured with the EBBI, EDLP or
EBOI board.
l Dependencies on Other Features
This feature depends on the following features:
– WRFD-010610 HSDPA Introduction Package
– WRFD-010611 HSDPA Enhanced Package
l 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 through
both the common group and private groups. In this case, the licensed value specified by
the private group is preferentially used, and the licensed value specified by the common
group is used on a first-come, first-served basis. For the NodeB license allocation among
multiple operators, see License Management Feature Parameter Description.
l Others Prerequisites
It is recommended that GBRs be configured on the RNC for all BE services to guarantee
basic user experience.
Data Preparation
Table 8-33 lists the data to prepare before deploying HSDPA Scheduling Based on UE Location.
Table 8-33 Data to prepare before deploying HSDPA Scheduling Based on UE Location
When configuring the HSDPA Scheduling based on UE Location 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 8-34. 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
Activation Observation
Run the NodeB MML command LST ULOCELLMACHSPARA. If the command output
shows that the value of Scheduling Method is EPF_LOC(Location based EPF), this feature
has been activated for the target cell.
When configuring the HSDPA Scheduling based on UE Location 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 the parameter described in Table 8-35 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 on the wizard interface to obtain online help.
----End
Step 1 Locate a hotspot cell based on the information in section 8.17.2 Information to Be Collected.
Step 2 Calculate the HSDPA throughput of the hotspot cell using the following formula:
Step 4 Check whether the HSDPA throughput of the hotspot cell increases after this feature is activated.
The increase in the HSDPA throughput depends on factors such as UE distribution and the traffic
model.
Step 5 Conduct a drive test to verify feature gains if there are a small number of hotspot cells.
----End
2. Place a UE near the cell center and another UE far away from the cell center.
3. Use the test UEs to download large files.
4. Query changes in the HSDPA throughput for the test cell.
8.17.6 Troubleshooting
None
When the downlink load is light, the HSDPA remaining power appending algorithm helps
decrease the downlink BLER and improve user experience. However, this algorithm increases
the downlink load. When the downlink load becomes heavy, network KPIs are deteriorated.
Therefore, the EXTRAPOWER parameter cannot be set to a too large value. The recommended
value for this parameter is 4, which is equal to 1 dB.
l When the value of the VS.DataTtiRatio.Mean counter for a cell is greater than 50%, for
example, in densely populated urban areas, the HSDPA remaining power appending
algorithm may decrease the CQI and cell throughput. Under this condition, the
EXTRAPOWER parameter should be set to a value equal to or less than 4.
l When the value of the VS.DataTtiRatio.Mean counter for a cell is less than 10%, for
example, in suburban areas, the EXTRAPOWER parameter can be set to a comparatively
large value, for example, 12 (equal to 3 dB), to improve user experience.
l Network KPIs
– CS call drop rate
– PS call drop rate
– CS RAB setup success rate
Requirements
l Dependencies on Hardware
None
l Dependencies on Other Features
None
l License
None
Data Preparation
Table 8-36 lists the data to prepare before deploying HSDPA Remaining Power Appending.
Table 8-36 Data to prepare before deploying HSDPA Remaining Power Appending
When configuring the HSDPA Remaining Power Appending function 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 8-37. 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
Activation Observation
Check the value of the RNC counter VS.MeanTCP for the following results:
l The value of this counter is less than 80% before this algorithm is enabled.
l The value of this counter is increased by a value less than the value specified by the Extra
Power parameter after this algorithm is enabled.
Alternatively, check the downlink BLER. If the downlink BLER is significantly decreased after
this algorithm is enabled, this algorithm is effective. The downlink BLER can be calculated
using the following formula:
where
When configuring the HSDPA Remaining Power Appending function 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 8-38. 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
deteriorate or cannot meet the Acceptance Criterion (APC). Then, check the values of network
KIPs.
Increase the value of the Extra Power parameter by one if the values of network KPIs are better
than the APC, a certain number of remaining power resources are left, and the BLER is large.
Then, check the values of network KIPs.
Decrease the value of the Extra Power parameter by one if cell throughput decreases due to the
decrease in the mean CQI and increase in the value of the VS.DataTtiRatio.Mean counter.
8.18.6 Troubleshooting
None
Before using this function, set the pilot power to 10% of the cell's maximum transmit power
(usually, the pilot power is set to -10 dB) and the MPO constant to the default value 2.5 dB.
l VS.AckTotal
l VS.NackTotal
l VS.DtxTotal
l VS.DataOutput.Mean
l VS.DataTtiRatio.Mean
l VS.HSDPA.InactiveDataTtiRatio.Mean
Run the LST UCELL command to query the maximum transmit power of a cell and the LST
UPCPICH command to query the P-CPICH configurations of the cell. Then, check whether the
P-CPICH transmit power subtracted by the maximum transmit power is -10 dB.
Run the LST UCELLHSDPA command to check whether the value of the HS-PDSCH MPO
Constant parameter is 2.5dB.
Requirements
None
Data Preparation
Table 8-39 lists the data to prepare before deploying BLER Optimization for HSDPA Burst
Services.
Table 8-39 Data to prepare before deploying BLER Optimization for HSDPA Burst Services
When configuring the BLER Optimization for HSDPA Burst Services function 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 8-40. 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
Activation Observation
Step 1 Check the values of the NodeB counters: VS.AckTotal, VS.NackTotal, and VS.DtxTotal.
Step 2 Use the following formula to obtain the BLER of HSDPA burst services before and after function
enabling:
If the BLER decreases after function enabling, the function has taken effect. Otherwise, the
function does not take effect yet.
Step 3 Use the following formula to obtain the cell throughput before and after function enabling:
----End
If the cell throughput increases after function enabling, the function has taken effect. Otherwise,
the function does not take effect yet.
When configuring the BLER Optimization for HSDPA Burst Services function 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 8-41. 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
VS.PdschCodeUtil.Mean.Data indicates the average usage of HS-PDSCH code resources when at least
one HSDPA user has data to transmit in the queue buffer.
l If the average number of licensed HSDPA codes per cell is less than 10, it is good practice
to expand the capacity of licensed HSDPA codes and then enable the function.
To enable the enhanced HSDPA code utilization function, the Resource Allocate Method
parameter in the SET ULOCELLMACHSPARA command must be set to
POWERCODE_BAL.
It is good practice to enable the enhanced HSDPA code utilization function for NodeBs deployed
for continuous coverage in an area, thereby yielding the gains brought by the reduced downlink
network load.
8.20.3 Deployment
This section describes how to activate, verify, and deactivate enhanced HSDPA code utilization.
Requirements
l Hardware
– Dependency on RNC hardware
None
– Dependency on NodeB hardware
3900 series base stations configured with the WBBPb, WBBPd, or WBBPf board
support the enhanced HSDPA code utilization function.
l Feature
WRFD-010610 HSDPA Introduction Package
l License
None
This feature is not under license control.
Data Preparation
Table 8-42 lists the data to prepare before deploying the enhanced HSDPA code utilization
function.
Table 8-42 Data to prepare before deploying the enhanced HSDPA code utilization function
To enable the enhanced HSDPA code utilization function, the Resource Allocate Method parameter in
the SET ULOCELLMACHSPARA command must be set to POWERCODE_BAL.
Run the SET ULOCELLMACHSPARA command on the NodeB side with Resource Allocate
Method set to POWERCODE_BAL(Balance between Code and Power) and Code
Utilization Optimization Switch set to ON(ON).
When configuring the function 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 8-43. 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
Activation Observation
Check the values of RNC counter VS.MeanTCP and NodeB counters
VS.PdschCodeUtil.Mean.Data, VS.PdschCodeUsed.Mean, VS.PdschPwrRatio.Data, and
VS.PdschPwrRatio.Mean. If the values of VS.MeanTCP, VS.PdschPwrRatio.Data, and
VS.PdschPwrRatio.Mean decrease and the values of VS.PdschCodeUtil.Mean.Data and
VS.PdschCodeUsed.Mean increase, this function has been activated.
When configuring the function 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 8-44. 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
KPI Monitoring
The CS/PS call drop rate and CS/PS RAB setup success rate do not deteriorate or even slightly
increase after the enhanced HSDPA code utilization function is enabled.
codes. Enable this function when code resources are sufficient. VS.PdschCodeUtil.Mean.Data
indicates the average usage of HS-PDSCH code resources when at least one HSDPA user has
data to transmit in the queue buffer.
8.20.6 Troubleshooting
None
9 Parameters
CODEO BTS390 SET WRFD- HSDPA Meaning: Indicates the switch for code utilization
PTSW 0, ULOCE 010610 Introduc optimization. If this switch is turned on, the HSDPA
BTS390 LLMAC tion code utilization rate increases but the power usage
0 HSPAR Package decreases. If this switch is turned off, code utilization
WCDM A optimization does not take effect.
A LST GUI Value Range: OFF(OFF), ON(ON)
ULOCE Unit: None
LLMAC
HSPAR Actual Value Range: OFF, ON
A Default Value: OFF(OFF)
PWSH BTS390 ADD WRFD- HSDPA Meaning: Indicates the policy of power sharing between
M 0, NODEB 010610 Introduc cells. If this parameter is set to R99CELLTOHCELL,
BTS390 PAGRP tion only one-way power sharing from the source cell
0 MOD Package (SLOCELL) to the target cell (DLOCELL) is supported.
WCDM NODEB If this parameter is set to HCELLTOHCELL, bilateral
A PAGRP power sharing between local cell 1 (SLOCELL) and
local cell 2 (DLOCELL) is supported.
LST
NODEB GUI Value Range: R99CELLTOHCELL(R99 cell to
PAGRP HSDPA cell), HCELLTOHCELL(HSDPA cell to
HSDPA cell)
Unit: None
Actual Value Range: R99CELLTOHCELL,
HCELLTOHCELL
Default Value: R99CELLTOHCELL(R99 cell to
HSDPA cell)
EXTRA BTS390 SET None None Meaning: Indicates the maximum power used for
POWER 0, ULOCE scheduled users after the scheduling.
BTS390 LLMAC GUI Value Range: 0~40
0 HSPAR
WCDM A Unit: 0.25dB
A LST Actual Value Range: 0~40
ULOCE Default Value: 0
LLMAC
HSPAR
A
BURST BTS390 SET None None Meaning: When this switch is turned on, estimated
BLERO 0, ULOCE channel environment errors are corrected for burst
PTSW BTS390 LLMAC services and full buffer services at the startup of data
0 HSPAR transmission to optimize the BLER.
WCDM A GUI Value Range: OFF(OFF), ON(ON)
A LST Unit: None
ULOCE
LLMAC Actual Value Range: OFF, ON
HSPAR Default Value: OFF(OFF)
A
HspaEn BSC690 ADD WRFD- HSDPA Meaning: If E_F_DPCH are selected, the corresponding
hSwitch 0 UCELL 010611 Enhance function will be enabled; otherwise, disabled.
ALGOS WRFD- d GUI Value Range: E_F_DPCH_OFF, E_F_DPCH_ON
WITCH 010652 Package
Unit: None
MOD SRB
UCELL over Actual Value Range: E_F_DPCH_OFF,
ALGOS HSDPA E_F_DPCH_ON
WITCH Default Value: E_F_DPCH_OFF
HspaEn BSC691 ADD WRFD- HSDPA Meaning: If E_F_DPCH are selected, the corresponding
hSwitch 0 UCELL 010611 Enhance function will be enabled; otherwise, disabled.
ALGOS WRFD- d GUI Value Range: E_F_DPCH_OFF, E_F_DPCH_ON
WITCH 010652 Package
Unit: None
MOD SRB
UCELL over Actual Value Range: E_F_DPCH_OFF,
ALGOS HSDPA E_F_DPCH_ON
WITCH Default Value: E_F_DPCH_OFF
SrbChlT BSC690 SET WRFD- HSPA+ Meaning: Type of channel that preferably carries the
ype 0 UFRCC 010698 Uplink signaling RB. - DCH: Both uplink and downlink are
HLTYP WRFD- 11.5Mbi preferably carried on DCH. - HSDPA: Uplink is
EPARA 010510 t/s per preferably carried on DCH, and downlink is preferably
User carried on HS-DSCH. - HSUPA: Uplink is preferably
WRFD- carried on E-DCH, and downlink is preferably carried
010612 3.4/6.8/1
3.6/27.2 on DCH. - HSPA: Uplink is preferably carried on E-
WRFD- Kbps DCH, and downlink is preferably carried on HS-DSCH.
010652 RRC GUI Value Range: DCH(UL_DCH,DL_DCH),
Connect HSDPA(UL_DCH,DL_HSDSCH), HSUPA
ion and (UL_EDCH,DL_DCH), HSPA
Radio (UL_EDCH,DL_HSDSCH)
Access Unit: None
Bearer
Establis Actual Value Range: DCH, HSDPA, HSUPA, HSPA
hment Default Value: DCH(UL_DCH,DL_DCH)
and
Release
HSUPA
Introduc
tion
Package
SRB
over
HSDPA
SrbChlT BSC691 SET WRFD- HSPA+ Meaning: Type of channel that preferably carries the
ype 0 UFRCC 010698 Uplink signaling RB. - DCH: Both uplink and downlink are
HLTYP WRFD- 11.5Mbi preferably carried on DCH. - HSDPA: Uplink is
EPARA 010510 t/s per preferably carried on DCH, and downlink is preferably
User carried on HS-DSCH. - HSUPA: Uplink is preferably
WRFD- carried on E-DCH, and downlink is preferably carried
010612 3.4/6.8/1
3.6/27.2 on DCH. - HSPA: Uplink is preferably carried on E-
WRFD- Kbps DCH, and downlink is preferably carried on HS-DSCH.
010652 RRC GUI Value Range: DCH(UL_DCH,DL_DCH),
Connect HSDPA(UL_DCH,DL_HSDSCH), HSUPA
ion and (UL_EDCH,DL_DCH), HSPA
Radio (UL_EDCH,DL_HSDSCH)
Access Unit: None
Bearer
Establis Actual Value Range: DCH, HSDPA, HSUPA, HSPA
hment Default Value: DCH(UL_DCH,DL_DCH)
and
Release
HSUPA
Introduc
tion
Package
SRB
over
HSDPA
SrbChlT BSC690 SET WRFD- 3.4/6.8/1 Meaning: Whether the configured type of channel that
ypeRrcE 0 UFRCC 010510 3.6/27.2 preferably carries the signaling RB is effective in the
ffectFla HLTYP WRFD- Kbps case of RRC connection establishment.
g EPARA 0106111 RRC GUI Value Range: FALSE, TRUE
2 Connect
ion and Unit: None
WRFD- Radio Actual Value Range: TRUE, FALSE
150232 Access Default Value: False
WRFD- Bearer
010652 Establis
hment
and
Release
HSDPA
DRD
Multiba
nd
Direct
Retry
Based
on UE
Location
SRB
over
HSDPA
SrbChlT BSC691 SET WRFD- 3.4/6.8/1 Meaning: Whether the configured type of channel that
ypeRrcE 0 UFRCC 010510 3.6/27.2 preferably carries the signaling RB is effective in the
ffectFla HLTYP WRFD- Kbps case of RRC connection establishment.
g EPARA 0106111 RRC GUI Value Range: FALSE, TRUE
2 Connect
ion and Unit: None
WRFD- Radio Actual Value Range: TRUE, FALSE
150232 Access Default Value: False
WRFD- Bearer
010652 Establis
hment
and
Release
HSDPA
DRD
Multiba
nd
Direct
Retry
Based
on UE
Location
SRB
over
HSDPA
ULOCE BTS390 SET None None Meaning: Indicates the reserved parameter 4.
LLRSV 0, ULOCE GUI Value Range: 0~4294967295
DPARA BTS390 LLRSV
4 0 DPARA Unit: None
WCDM LST Actual Value Range: 0~4294967295
A ULOCE Default Value: 0
LLRSV
DPARA
EXTRA BTS390 SET WRFD- SRB Meaning: Indicates the extra power for the SRB queue.
POWER 0, ULOCE 010652 over If SRBs are carried over HSDPA, the transmit power
FORSR BTS390 LLMAC HSDPA increases when there is remaining cell power or the data
B 0 HSPAR volume to be transmitted decreases when there is no
WCDM A remaining cell power. This reduces the BLER of the
A LST SRB queue, decreases the HSDPA service drop rate, and
ULOCE increases the HSDPA handover success rate.
LLMAC GUI Value Range: 0~10
HSPAR Unit: dB
A
Actual Value Range: 0~10
Default Value: 0
RsvSwit BSC690 SET None None Meaning: RRM algorithm reserved U32 Switch Para 4.
ch4 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_4_BIT1,
RESERVED_SWITCH_4_BIT2,
RESERVED_SWITCH_4_BIT3,
RESERVED_SWITCH_4_BIT4,
RESERVED_SWITCH_4_BIT5,
RESERVED_SWITCH_4_BIT6,
RESERVED_SWITCH_4_BIT7,
RESERVED_SWITCH_4_BIT8,
RESERVED_SWITCH_4_BIT9,
RESERVED_SWITCH_4_BIT10,
RESERVED_SWITCH_4_BIT11,
RESERVED_SWITCH_4_BIT12,
RESERVED_SWITCH_4_BIT13,
RESERVED_SWITCH_4_BIT14,
RESERVED_SWITCH_4_BIT15,
RESERVED_SWITCH_4_BIT16,
RESERVED_SWITCH_4_BIT17,
RESERVED_SWITCH_4_BIT18,
RESERVED_SWITCH_4_BIT19,
RESERVED_SWITCH_4_BIT20,
RESERVED_SWITCH_4_BIT21,
RESERVED_SWITCH_4_BIT22,
RESERVED_SWITCH_4_BIT23,
RESERVED_SWITCH_4_BIT24,
RESERVED_SWITCH_4_BIT25,
RESERVED_SWITCH_4_BIT26,
RESERVED_SWITCH_4_BIT27,
RESERVED_SWITCH_4_BIT28,
RESERVED_SWITCH_4_BIT29,
RESERVED_SWITCH_4_BIT30,
RESERVED_SWITCH_4_BIT31,
RESERVED_SWITCH_4_BIT32
Unit: None
Actual Value Range: RESERVED_SWITCH_4_BIT1,
RESERVED_SWITCH_4_BIT2,
RESERVED_SWITCH_4_BIT3,
RESERVED_SWITCH_4_BIT4,
RESERVED_SWITCH_4_BIT5,
RESERVED_SWITCH_4_BIT6,
RESERVED_SWITCH_4_BIT7,
RESERVED_SWITCH_4_BIT8,
RESERVED_SWITCH_4_BIT9,
RESERVED_SWITCH_4_BIT10,
RESERVED_SWITCH_4_BIT11,
RESERVED_SWITCH_4_BIT12,
RESERVED_SWITCH_4_BIT13,
RESERVED_SWITCH_4_BIT14,
RESERVED_SWITCH_4_BIT15,
RESERVED_SWITCH_4_BIT16,
RESERVED_SWITCH_4_BIT17,
RESERVED_SWITCH_4_BIT18,
RESERVED_SWITCH_4_BIT19,
RESERVED_SWITCH_4_BIT20,
RESERVED_SWITCH_4_BIT21,
RESERVED_SWITCH_4_BIT22,
RESERVED_SWITCH_4_BIT23,
RESERVED_SWITCH_4_BIT24,
RESERVED_SWITCH_4_BIT25,
RESERVED_SWITCH_4_BIT26,
RESERVED_SWITCH_4_BIT27,
RESERVED_SWITCH_4_BIT28,
RESERVED_SWITCH_4_BIT29,
RESERVED_SWITCH_4_BIT30,
RESERVED_SWITCH_4_BIT31,
RESERVED_SWITCH_4_BIT32
Default Value:
RESERVED_SWITCH_4_BIT1:0,RESERVED_SWI
TCH_4_BIT2:0,RESERVED_SWITCH_4_BIT3:0,R
ESERVED_SWITCH_4_BIT4:0,RESERVED_SWIT
CH_4_BIT5:0,RESERVED_SWITCH_4_BIT6:0,RE
SERVED_SWITCH_4_BIT7:0,RESERVED_SWITC
H_4_BIT8:0,RESERVED_SWITCH_4_BIT9:0,RES
ERVED_SWITCH_4_BIT10:0,RESERVED_SWITC
H_4_BIT11:0,RESERVED_SWITCH_4_BIT12:0,RE
SERVED_SWITCH_4_BIT13:0,RESERVED_SWIT
CH_4_BIT14:0,RESERVED_SWITCH_4_BIT15:0,R
ESERVED_SWITCH_4_BIT16:0,RESERVED_SWI
TCH_4_BIT17:0,RESERVED_SWITCH_4_BIT18:0,
RESERVED_SWITCH_4_BIT19:0,RESERVED_SW
ITCH_4_BIT20:0,RESERVED_SWITCH_4_BIT21:0
,RESERVED_SWITCH_4_BIT22:0,RESERVED_S
WITCH_4_BIT23:0,RESERVED_SWITCH_4_BIT2
4:0,RESERVED_SWITCH_4_BIT25:0,RESERVED_
SWITCH_4_BIT26:0,RESERVED_SWITCH_4_BIT
27:0,RESERVED_SWITCH_4_BIT28:0,RESERVED
_SWITCH_4_BIT29:0,RESERVED_SWITCH_4_BI
T30:0,RESERVED_SWITCH_4_BIT31:0,RESERVE
D_SWITCH_4_BIT32:0
RsvSwit BSC691 SET None None Meaning: RRM algorithm reserved U32 Switch Para 4.
ch4 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_4_BIT1,
RESERVED_SWITCH_4_BIT2,
RESERVED_SWITCH_4_BIT3,
RESERVED_SWITCH_4_BIT4,
RESERVED_SWITCH_4_BIT5,
RESERVED_SWITCH_4_BIT6,
RESERVED_SWITCH_4_BIT7,
RESERVED_SWITCH_4_BIT8,
RESERVED_SWITCH_4_BIT9,
RESERVED_SWITCH_4_BIT10,
RESERVED_SWITCH_4_BIT11,
RESERVED_SWITCH_4_BIT12,
RESERVED_SWITCH_4_BIT13,
RESERVED_SWITCH_4_BIT14,
RESERVED_SWITCH_4_BIT15,
RESERVED_SWITCH_4_BIT16,
RESERVED_SWITCH_4_BIT17,
RESERVED_SWITCH_4_BIT18,
RESERVED_SWITCH_4_BIT19,
RESERVED_SWITCH_4_BIT20,
RESERVED_SWITCH_4_BIT21,
RESERVED_SWITCH_4_BIT22,
RESERVED_SWITCH_4_BIT23,
RESERVED_SWITCH_4_BIT24,
RESERVED_SWITCH_4_BIT25,
RESERVED_SWITCH_4_BIT26,
RESERVED_SWITCH_4_BIT27,
RESERVED_SWITCH_4_BIT28,
RESERVED_SWITCH_4_BIT29,
RESERVED_SWITCH_4_BIT30,
RESERVED_SWITCH_4_BIT31,
RESERVED_SWITCH_4_BIT32
Unit: None
Actual Value Range: RESERVED_SWITCH_4_BIT1,
RESERVED_SWITCH_4_BIT2,
RESERVED_SWITCH_4_BIT3,
RESERVED_SWITCH_4_BIT4,
RESERVED_SWITCH_4_BIT5,
RESERVED_SWITCH_4_BIT6,
RESERVED_SWITCH_4_BIT7,
RESERVED_SWITCH_4_BIT8,
RESERVED_SWITCH_4_BIT9,
RESERVED_SWITCH_4_BIT10,
RESERVED_SWITCH_4_BIT11,
RESERVED_SWITCH_4_BIT12,
RESERVED_SWITCH_4_BIT13,
RESERVED_SWITCH_4_BIT14,
RESERVED_SWITCH_4_BIT15,
RESERVED_SWITCH_4_BIT16,
RESERVED_SWITCH_4_BIT17,
RESERVED_SWITCH_4_BIT18,
RESERVED_SWITCH_4_BIT19,
RESERVED_SWITCH_4_BIT20,
RESERVED_SWITCH_4_BIT21,
RESERVED_SWITCH_4_BIT22,
RESERVED_SWITCH_4_BIT23,
RESERVED_SWITCH_4_BIT24,
RESERVED_SWITCH_4_BIT25,
RESERVED_SWITCH_4_BIT26,
RESERVED_SWITCH_4_BIT27,
RESERVED_SWITCH_4_BIT28,
RESERVED_SWITCH_4_BIT29,
RESERVED_SWITCH_4_BIT30,
RESERVED_SWITCH_4_BIT31,
RESERVED_SWITCH_4_BIT32
Default Value:
RESERVED_SWITCH_4_BIT1:0,RESERVED_SWI
TCH_4_BIT2:0,RESERVED_SWITCH_4_BIT3:0,R
ESERVED_SWITCH_4_BIT4:0,RESERVED_SWIT
CH_4_BIT5:0,RESERVED_SWITCH_4_BIT6:0,RE
SERVED_SWITCH_4_BIT7:0,RESERVED_SWITC
H_4_BIT8:0,RESERVED_SWITCH_4_BIT9:0,RES
ERVED_SWITCH_4_BIT10:0,RESERVED_SWITC
H_4_BIT11:0,RESERVED_SWITCH_4_BIT12:0,RE
SERVED_SWITCH_4_BIT13:0,RESERVED_SWIT
CH_4_BIT14:0,RESERVED_SWITCH_4_BIT15:0,R
ESERVED_SWITCH_4_BIT16:0,RESERVED_SWI
TCH_4_BIT17:0,RESERVED_SWITCH_4_BIT18:0,
RESERVED_SWITCH_4_BIT19:0,RESERVED_SW
ITCH_4_BIT20:0,RESERVED_SWITCH_4_BIT21:0
,RESERVED_SWITCH_4_BIT22:0,RESERVED_S
WITCH_4_BIT23:0,RESERVED_SWITCH_4_BIT2
4:0,RESERVED_SWITCH_4_BIT25:0,RESERVED_
SWITCH_4_BIT26:0,RESERVED_SWITCH_4_BIT
27:0,RESERVED_SWITCH_4_BIT28:0,RESERVED
_SWITCH_4_BIT29:0,RESERVED_SWITCH_4_BI
T30:0,RESERVED_SWITCH_4_BIT31:0,RESERVE
D_SWITCH_4_BIT32:0
command. 13.
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH: Whether to validate the load based intelligent state
transition algorithm. When this switch is set to on and
the
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH under the "DraSwitch" parameter in the "ADD
UCELLDCCC" command is set to on, the RNC
performs state transition according to the following
parameters: "HiLdBeD2FStateTransTimer" in the
"SET UUESTATETRANSTIMER" command,
"HiLdCellDchPSInactTimer" in the "SET
UPSINACTTIMER" command, and
"HiLdBeDLF2DHTvmThd" and
"HiLdBeULF2DETvmThd" in the "SET
UUESTATETRANS" command. 14.
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH:
Whether the coverage-based and load-based algorithm
for dynamic reconfiguration of the channel mapped to
downlink signaling radio bearers (SRBs) takes
effect.When this switch is turned off, the algorithm does
not take effect. When this switch is turned on, The
algorithm takes effect. Operations of the algorithm: 1.
Access mode: The algorithm also considers coverage
and loads to determine whether the downlink SRBs can
be carried on the HS-DSCH when a UE transits from
the idle, CELL_FACH, CELL_PCH, or URA_PCH
state to the CELL_DCH state during an RRC connection
setup, RAB setup, or RAB modification or when a
CELL_DCH UE experiences an incoming inter-RAT
handover or an incoming combined hard handover and
SRNS relocation. 2. Connected mode: After a UE
accesses a cell, the algorithm determines whether to
deliver periodic RSCP and Ec/N0 measurement control
messages. When the RNC receives periodic
measurement reports on the RSCP and Ec/N0, the
algorithm determines whether to initiate the SRB
reconfiguration process.
GUI Value Range:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH,
DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWIT
CH,
DRA_BASE_COVER_BE_E2D_INITSEL_SWITCH
, DRA_BASE_COVER_BE_E2D_SWITCH,
DRA_D2F_OVER_IUR_SWITCH,
DRA_CSPS_0K_RATE_UP_SWITCH,
DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH,
DRA_PS_STATE_TRANS_WHEN_CS_REL_SWIT
CH, DRA_BASE_COVER_E2D_DCCC_SWITCH,
DRA_WEB_FACH_DELAY_OPT_SWITCH,
DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH,
DRA_D2P_WHEN_PS_INACT_SWITCH,
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH,
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH
Unit: None
Actual Value Range:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH,
DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWIT
CH,
DRA_BASE_COVER_BE_E2D_INITSEL_SWITCH
, DRA_BASE_COVER_BE_E2D_SWITCH,
DRA_D2F_OVER_IUR_SWITCH,
DRA_CSPS_0K_RATE_UP_SWITCH,
DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH,
DRA_PS_STATE_TRANS_WHEN_CS_REL_SWIT
CH, DRA_BASE_COVER_E2D_DCCC_SWITCH,
DRA_WEB_FACH_DELAY_OPT_SWITCH,
DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH,
DRA_D2P_WHEN_PS_INACT_SWITCH,
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH,
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH
Default Value:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH:
0,DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWI
TCH:
0,DRA_BASE_COVER_BE_E2D_INITSEL_SWITC
H:0,DRA_BASE_COVER_BE_E2D_SWITCH:
0,DRA_D2F_OVER_IUR_SWITCH:
0,DRA_CSPS_0K_RATE_UP_SWITCH:
1,DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH:
0,DRA_PS_STATE_TRANS_WHEN_CS_REL_SWI
TCH:
0,DRA_BASE_COVER_E2D_DCCC_SWITCH:
0,DRA_WEB_FACH_DELAY_OPT_SWITCH:
0,DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH
:0,DRA_D2P_WHEN_PS_INACT_SWITCH:
0,DRA_INTELL_STATE_TRANS_ON_LOAD_SWI
TCH:
0,DRA_BASE_COVER_LOAD_SRB_H2D_SWITC
H:0
command. 13.
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH: Whether to validate the load based intelligent state
transition algorithm. When this switch is set to on and
the
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH under the "DraSwitch" parameter in the "ADD
UCELLDCCC" command is set to on, the RNC
performs state transition according to the following
parameters: "HiLdBeD2FStateTransTimer" in the
"SET UUESTATETRANSTIMER" command,
"HiLdCellDchPSInactTimer" in the "SET
UPSINACTTIMER" command, and
"HiLdBeDLF2DHTvmThd" and
"HiLdBeULF2DETvmThd" in the "SET
UUESTATETRANS" command. 14.
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH:
Whether the coverage-based and load-based algorithm
for dynamic reconfiguration of the channel mapped to
downlink signaling radio bearers (SRBs) takes
effect.When this switch is turned off, the algorithm does
not take effect. When this switch is turned on, The
algorithm takes effect. Operations of the algorithm: 1.
Access mode: The algorithm also considers coverage
and loads to determine whether the downlink SRBs can
be carried on the HS-DSCH when a UE transits from
the idle, CELL_FACH, CELL_PCH, or URA_PCH
state to the CELL_DCH state during an RRC connection
setup, RAB setup, or RAB modification or when a
CELL_DCH UE experiences an incoming inter-RAT
handover or an incoming combined hard handover and
SRNS relocation. 2. Connected mode: After a UE
accesses a cell, the algorithm determines whether to
deliver periodic RSCP and Ec/N0 measurement control
messages. When the RNC receives periodic
measurement reports on the RSCP and Ec/N0, the
algorithm determines whether to initiate the SRB
reconfiguration process.
GUI Value Range:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH,
DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWIT
CH,
DRA_BASE_COVER_BE_E2D_INITSEL_SWITCH
, DRA_BASE_COVER_BE_E2D_SWITCH,
DRA_D2F_OVER_IUR_SWITCH,
DRA_CSPS_0K_RATE_UP_SWITCH,
DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH,
DRA_PS_STATE_TRANS_WHEN_CS_REL_SWIT
CH, DRA_BASE_COVER_E2D_DCCC_SWITCH,
DRA_WEB_FACH_DELAY_OPT_SWITCH,
DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH,
DRA_D2P_WHEN_PS_INACT_SWITCH,
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH,
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH
Unit: None
Actual Value Range:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH,
DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWIT
CH,
DRA_BASE_COVER_BE_E2D_INITSEL_SWITCH
, DRA_BASE_COVER_BE_E2D_SWITCH,
DRA_D2F_OVER_IUR_SWITCH,
DRA_CSPS_0K_RATE_UP_SWITCH,
DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH,
DRA_PS_STATE_TRANS_WHEN_CS_REL_SWIT
CH, DRA_BASE_COVER_E2D_DCCC_SWITCH,
DRA_WEB_FACH_DELAY_OPT_SWITCH,
DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH,
DRA_D2P_WHEN_PS_INACT_SWITCH,
DRA_INTELL_STATE_TRANS_ON_LOAD_SWIT
CH,
DRA_BASE_COVER_LOAD_SRB_H2D_SWITCH
Default Value:
DRA_BASE_COVER_BE_E2D_INITSEL_OPT_SW
ITCH:
0,DRA_PCPICH_ECN0_ON_RACH_UPDATE_SWI
TCH:
0,DRA_BASE_COVER_BE_E2D_INITSEL_SWITC
H:0,DRA_BASE_COVER_BE_E2D_SWITCH:
0,DRA_D2F_OVER_IUR_SWITCH:
0,DRA_CSPS_0K_RATE_UP_SWITCH:
1,DRA_CSPS_BOTH_ULDL_RATE_UP_SWITCH:
0,DRA_PS_STATE_TRANS_WHEN_CS_REL_SWI
TCH:
0,DRA_BASE_COVER_E2D_DCCC_SWITCH:
0,DRA_WEB_FACH_DELAY_OPT_SWITCH:
0,DRA_D2F_LIMIT_WITH_CS_IU_CON_SWITCH
:0,DRA_D2P_WHEN_PS_INACT_SWITCH:
0,DRA_INTELL_STATE_TRANS_ON_LOAD_SWI
TCH:
0,DRA_BASE_COVER_LOAD_SRB_H2D_SWITC
H:0
RsvSwit BSC690 SET None None Meaning: RRM algorithm reserved U32 Switch Para 7.
ch7 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_7_BIT1,
RESERVED_SWITCH_7_BIT2,
RESERVED_SWITCH_7_BIT3,
RESERVED_SWITCH_7_BIT4,
RESERVED_SWITCH_7_BIT5,
RESERVED_SWITCH_7_BIT6,
RESERVED_SWITCH_7_BIT7,
RESERVED_SWITCH_7_BIT8,
RESERVED_SWITCH_7_BIT9,
RESERVED_SWITCH_7_BIT10,
RESERVED_SWITCH_7_BIT11,
RESERVED_SWITCH_7_BIT12,
RESERVED_SWITCH_7_BIT13,
RESERVED_SWITCH_7_BIT14,
RESERVED_SWITCH_7_BIT15,
RESERVED_SWITCH_7_BIT16,
RESERVED_SWITCH_7_BIT17,
RESERVED_SWITCH_7_BIT18,
RESERVED_SWITCH_7_BIT19,
RESERVED_SWITCH_7_BIT20,
RESERVED_SWITCH_7_BIT21,
RESERVED_SWITCH_7_BIT22,
RESERVED_SWITCH_7_BIT23,
RESERVED_SWITCH_7_BIT24,
RESERVED_SWITCH_7_BIT25,
RESERVED_SWITCH_7_BIT26,
RESERVED_SWITCH_7_BIT27,
RESERVED_SWITCH_7_BIT28,
RESERVED_SWITCH_7_BIT29,
RESERVED_SWITCH_7_BIT30,
RESERVED_SWITCH_7_BIT31,
RESERVED_SWITCH_7_BIT32
Unit: None
Actual Value Range: RESERVED_SWITCH_7_BIT1,
RESERVED_SWITCH_7_BIT2,
RESERVED_SWITCH_7_BIT3,
RESERVED_SWITCH_7_BIT4,
RESERVED_SWITCH_7_BIT5,
RESERVED_SWITCH_7_BIT6,
RESERVED_SWITCH_7_BIT7,
RESERVED_SWITCH_7_BIT8,
RESERVED_SWITCH_7_BIT9,
RESERVED_SWITCH_7_BIT10,
RESERVED_SWITCH_7_BIT11,
RESERVED_SWITCH_7_BIT12,
RESERVED_SWITCH_7_BIT13,
RESERVED_SWITCH_7_BIT14,
RESERVED_SWITCH_7_BIT15,
RESERVED_SWITCH_7_BIT16,
RESERVED_SWITCH_7_BIT17,
RESERVED_SWITCH_7_BIT18,
RESERVED_SWITCH_7_BIT19,
RESERVED_SWITCH_7_BIT20,
RESERVED_SWITCH_7_BIT21,
RESERVED_SWITCH_7_BIT22,
RESERVED_SWITCH_7_BIT23,
RESERVED_SWITCH_7_BIT24,
RESERVED_SWITCH_7_BIT25,
RESERVED_SWITCH_7_BIT26,
RESERVED_SWITCH_7_BIT27,
RESERVED_SWITCH_7_BIT28,
RESERVED_SWITCH_7_BIT29,
RESERVED_SWITCH_7_BIT30,
RESERVED_SWITCH_7_BIT31,
RESERVED_SWITCH_7_BIT32
Default Value:
RESERVED_SWITCH_7_BIT1:1,RESERVED_SWI
TCH_7_BIT2:1,RESERVED_SWITCH_7_BIT3:1,R
ESERVED_SWITCH_7_BIT4:1,RESERVED_SWIT
CH_7_BIT5:1,RESERVED_SWITCH_7_BIT6:1,RE
SERVED_SWITCH_7_BIT7:1,RESERVED_SWITC
H_7_BIT8:1,RESERVED_SWITCH_7_BIT9:1,RES
ERVED_SWITCH_7_BIT10:1,RESERVED_SWITC
H_7_BIT11:1,RESERVED_SWITCH_7_BIT12:1,RE
SERVED_SWITCH_7_BIT13:1,RESERVED_SWIT
CH_7_BIT14:1,RESERVED_SWITCH_7_BIT15:1,R
ESERVED_SWITCH_7_BIT16:1,RESERVED_SWI
TCH_7_BIT17:1,RESERVED_SWITCH_7_BIT18:1,
RESERVED_SWITCH_7_BIT19:1,RESERVED_SW
ITCH_7_BIT20:1,RESERVED_SWITCH_7_BIT21:1
,RESERVED_SWITCH_7_BIT22:1,RESERVED_S
WITCH_7_BIT23:1,RESERVED_SWITCH_7_BIT2
4:1,RESERVED_SWITCH_7_BIT25:1,RESERVED_
SWITCH_7_BIT26:1,RESERVED_SWITCH_7_BIT
27:1,RESERVED_SWITCH_7_BIT28:1,RESERVED
_SWITCH_7_BIT29:1,RESERVED_SWITCH_7_BI
T30:1,RESERVED_SWITCH_7_BIT31:1,RESERVE
D_SWITCH_7_BIT32:1
RsvSwit BSC691 SET None None Meaning: RRM algorithm reserved U32 Switch Para 7.
ch7 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_7_BIT1,
RESERVED_SWITCH_7_BIT2,
RESERVED_SWITCH_7_BIT3,
RESERVED_SWITCH_7_BIT4,
RESERVED_SWITCH_7_BIT5,
RESERVED_SWITCH_7_BIT6,
RESERVED_SWITCH_7_BIT7,
RESERVED_SWITCH_7_BIT8,
RESERVED_SWITCH_7_BIT9,
RESERVED_SWITCH_7_BIT10,
RESERVED_SWITCH_7_BIT11,
RESERVED_SWITCH_7_BIT12,
RESERVED_SWITCH_7_BIT13,
RESERVED_SWITCH_7_BIT14,
RESERVED_SWITCH_7_BIT15,
RESERVED_SWITCH_7_BIT16,
RESERVED_SWITCH_7_BIT17,
RESERVED_SWITCH_7_BIT18,
RESERVED_SWITCH_7_BIT19,
RESERVED_SWITCH_7_BIT20,
RESERVED_SWITCH_7_BIT21,
RESERVED_SWITCH_7_BIT22,
RESERVED_SWITCH_7_BIT23,
RESERVED_SWITCH_7_BIT24,
RESERVED_SWITCH_7_BIT25,
RESERVED_SWITCH_7_BIT26,
RESERVED_SWITCH_7_BIT27,
RESERVED_SWITCH_7_BIT28,
RESERVED_SWITCH_7_BIT29,
RESERVED_SWITCH_7_BIT30,
RESERVED_SWITCH_7_BIT31,
RESERVED_SWITCH_7_BIT32
Unit: None
Actual Value Range: RESERVED_SWITCH_7_BIT1,
RESERVED_SWITCH_7_BIT2,
RESERVED_SWITCH_7_BIT3,
RESERVED_SWITCH_7_BIT4,
RESERVED_SWITCH_7_BIT5,
RESERVED_SWITCH_7_BIT6,
RESERVED_SWITCH_7_BIT7,
RESERVED_SWITCH_7_BIT8,
RESERVED_SWITCH_7_BIT9,
RESERVED_SWITCH_7_BIT10,
RESERVED_SWITCH_7_BIT11,
RESERVED_SWITCH_7_BIT12,
RESERVED_SWITCH_7_BIT13,
RESERVED_SWITCH_7_BIT14,
RESERVED_SWITCH_7_BIT15,
RESERVED_SWITCH_7_BIT16,
RESERVED_SWITCH_7_BIT17,
RESERVED_SWITCH_7_BIT18,
RESERVED_SWITCH_7_BIT19,
RESERVED_SWITCH_7_BIT20,
RESERVED_SWITCH_7_BIT21,
RESERVED_SWITCH_7_BIT22,
RESERVED_SWITCH_7_BIT23,
RESERVED_SWITCH_7_BIT24,
RESERVED_SWITCH_7_BIT25,
RESERVED_SWITCH_7_BIT26,
RESERVED_SWITCH_7_BIT27,
RESERVED_SWITCH_7_BIT28,
RESERVED_SWITCH_7_BIT29,
RESERVED_SWITCH_7_BIT30,
RESERVED_SWITCH_7_BIT31,
RESERVED_SWITCH_7_BIT32
Default Value:
RESERVED_SWITCH_7_BIT1:1,RESERVED_SWI
TCH_7_BIT2:1,RESERVED_SWITCH_7_BIT3:1,R
ESERVED_SWITCH_7_BIT4:1,RESERVED_SWIT
CH_7_BIT5:1,RESERVED_SWITCH_7_BIT6:1,RE
SERVED_SWITCH_7_BIT7:1,RESERVED_SWITC
H_7_BIT8:1,RESERVED_SWITCH_7_BIT9:1,RES
ERVED_SWITCH_7_BIT10:1,RESERVED_SWITC
H_7_BIT11:1,RESERVED_SWITCH_7_BIT12:1,RE
SERVED_SWITCH_7_BIT13:1,RESERVED_SWIT
CH_7_BIT14:1,RESERVED_SWITCH_7_BIT15:1,R
ESERVED_SWITCH_7_BIT16:1,RESERVED_SWI
TCH_7_BIT17:1,RESERVED_SWITCH_7_BIT18:1,
RESERVED_SWITCH_7_BIT19:1,RESERVED_SW
ITCH_7_BIT20:1,RESERVED_SWITCH_7_BIT21:1
,RESERVED_SWITCH_7_BIT22:1,RESERVED_S
WITCH_7_BIT23:1,RESERVED_SWITCH_7_BIT2
4:1,RESERVED_SWITCH_7_BIT25:1,RESERVED_
SWITCH_7_BIT26:1,RESERVED_SWITCH_7_BIT
27:1,RESERVED_SWITCH_7_BIT28:1,RESERVED
_SWITCH_7_BIT29:1,RESERVED_SWITCH_7_BI
T30:1,RESERVED_SWITCH_7_BIT31:1,RESERVE
D_SWITCH_7_BIT32:1
RsvU32 BSC690 SET None None Meaning: RRM algorithm reserved U32 para 4. The 32-
Para4 0 UALGO bit parameter is reserved for further change request use.
RSVPA Disuse statement: This parameter is used temporarily in
RA patch versions and will be replaced with a new
parameter in later versions. The new parameter ID
reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: 0~4294967295
Unit: None
Actual Value Range: 0~4294967295
Default Value: 0
RsvU32 BSC691 SET None None Meaning: RRM algorithm reserved U32 para 4. The 32-
Para4 0 UALGO bit parameter is reserved for further change request use.
RSVPA Disuse statement: This parameter is used temporarily in
RA patch versions and will be replaced with a new
parameter in later versions. The new parameter ID
reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: 0~4294967295
Unit: None
Actual Value Range: 0~4294967295
Default Value: 0
SrbH2D BSC690 SET WRFD- SRB Meaning: Downlink non-HSPA light load initial state
NonHLo 0 UCHLQ 010652 over for the coverage-based and load-based algorithm for
adState UALIT HSDPA dynamic reconfiguration of the channel mapped to
YEVAL downlink SRBs. If the load of the best cell is in this state
UATE or a lighter state, the cell is in a light load state.
Otherwise, the cell is in a heavy load state.
GUI Value Range: DL_LIGHT_STATE,
DL_NORMAL_STATE, DL_LOADED_STATE,
DL_HEAVY_STATE, DL_OVERRLOAD_STATE
Unit: None
Actual Value Range: DL_LIGHT_STATE,
DL_NORMAL_STATE, DL_LOADED_STATE,
DL_HEAVY_STATE, DL_OVERRLOAD_STATE
Default Value: DL_LOADED_STATE
SrbH2D BSC691 SET WRFD- SRB Meaning: Downlink non-HSPA light load initial state
NonHLo 0 UCHLQ 010652 over for the coverage-based and load-based algorithm for
adState UALIT HSDPA dynamic reconfiguration of the channel mapped to
YEVAL downlink SRBs. If the load of the best cell is in this state
UATE or a lighter state, the cell is in a light load state.
Otherwise, the cell is in a heavy load state.
GUI Value Range: DL_LIGHT_STATE,
DL_NORMAL_STATE, DL_LOADED_STATE,
DL_HEAVY_STATE, DL_OVERRLOAD_STATE
Unit: None
Actual Value Range: DL_LIGHT_STATE,
DL_NORMAL_STATE, DL_LOADED_STATE,
DL_HEAVY_STATE, DL_OVERRLOAD_STATE
Default Value: DL_LOADED_STATE
CellLdr BSC690 ADD WRFD- Load Meaning: Threshold for reserved SF in a cell. This
SfResTh 0 UCELL 150216 Based parameter is used to determine whether the code load
d LDR WRFD- PS reshuffling (LDR) is allowed.
MOD 150217 Redirect GUI Value Range: SF4(SF4), SF8(SF8), SF16(SF16),
UCELL ion from SF32(SF32), SF64(SF64), SF128(SF128), SF256
WRFD- UMTS
LDR 020108 (SF256)
to LTE
WRFD- Unit: None
Load
150215 Based Actual Value Range: SF4, SF8, SF16, SF32, SF64,
WRFD- PS SF128, SF256
140226 Handov Default Value: SF8(SF8)
WRFD- er from
140102 UMTS
to LTE
WRFD-
020106 Code
Resourc
WRFD-
e
150231
Manage
WRFD- ment
150219
SRVCC
WRFD- from
020126 LTE to
WRFD- UMTS
020103 with PS
Handov
WRFD-
er
020129
Fast
WRFD-
Return
140218
from
WRFD- UMTS
150220 to LTE
CS
Fallback
Guarant
ee for
LTE
Emerge
ncy
Calls
Load
Reshuffl
ing
RIM
Based
UMTS
Target
Cell
Selectio
n for
LTE
Coverag
e Based
PS
Redirect
ion from
UMTS
to LTE
Mobility
Between
UMTS
and LTE
Phase 1
Inter
Frequen
cy Load
Balance
PS
Service
Redirect
ion from
UMTS
to LTE
Service-
Based
PS
Handov
er from
UMTS
to LTE
Coverag
e Based
PS
Handov
er from
UMTS
to LTE
CellLdr BSC691 ADD WRFD- Load Meaning: Threshold for reserved SF in a cell. This
SfResTh 0 UCELL 150216 Based parameter is used to determine whether the code load
d LDR WRFD- PS reshuffling (LDR) is allowed.
MOD 150217 Redirect GUI Value Range: SF4(SF4), SF8(SF8), SF16(SF16),
UCELL ion from SF32(SF32), SF64(SF64), SF128(SF128), SF256
WRFD- UMTS
LDR 020108 (SF256)
to LTE
WRFD- Unit: None
Load
150215 Based Actual Value Range: SF4, SF8, SF16, SF32, SF64,
WRFD- PS SF128, SF256
140226 Handov Default Value: SF8(SF8)
WRFD- er from
140102 UMTS
to LTE
WRFD-
020106 Code
Resourc
WRFD-
e
150231
Manage
WRFD- ment
150219
SRVCC
WRFD- from
020126 LTE to
WRFD- UMTS
020103 with PS
Handov
WRFD-
er
020129
Fast
WRFD-
Return
140218
from
WRFD- UMTS
150220 to LTE
CS
Fallback
Guarant
ee for
LTE
Emerge
ncy
Calls
Load
Reshuffl
ing
RIM
Based
UMTS
Target
Cell
Selectio
n for
LTE
Coverag
e Based
PS
Redirect
ion from
UMTS
to LTE
Mobility
Between
UMTS
and LTE
Phase 1
Inter
Frequen
cy Load
Balance
PS
Service
Redirect
ion from
UMTS
to LTE
Service-
Based
PS
Handov
er from
UMTS
to LTE
Coverag
e Based
PS
Handov
er from
UMTS
to LTE
EcN0Eff BSC690 ADD WRFD- 3.4/6.8/1 Meaning: Time period for valid Ec/No or RSCP. This
ectTime 0 UCELL 010510 3.6/27.2 parameter defines the time period during which the
FRC WRFD- Kbps reported values of Ec/No or RSCP are considered as
MOD 010690 RRC valid values. The time period starts from the time the
UCELL Connect system receives the first Ec/No or RSCP.
WRFD- ion and
FRC 010507 GUI Value Range: 0~65535
Radio
WRFD- Access Unit: ms
150232 Bearer Actual Value Range: 0~65535
WRFD- Establis Default Value: 5000
010612 hment
and
WRFD-
Release
020400
TTI
Switch
for BE
Services
Based
on
Coverag
e
Rate
Negotiat
ion at
Admissi
on
Control
Multiba
nd
Direct
Retry
Based
on UE
Location
HSUPA
Introduc
tion
Package
DRD
Introduc
tion
Package
EcN0Eff BSC691 ADD WRFD- 3.4/6.8/1 Meaning: Time period for valid Ec/No or RSCP. This
ectTime 0 UCELL 010510 3.6/27.2 parameter defines the time period during which the
FRC WRFD- Kbps reported values of Ec/No or RSCP are considered as
MOD 010690 RRC valid values. The time period starts from the time the
UCELL Connect system receives the first Ec/No or RSCP.
WRFD- ion and
FRC 010507 GUI Value Range: 0~65535
Radio
WRFD- Access Unit: ms
150232 Bearer Actual Value Range: 0~65535
WRFD- Establis Default Value: 5000
010612 hment
and
WRFD-
Release
020400
TTI
Switch
for BE
Services
Based
on
Coverag
e
Rate
Negotiat
ion at
Admissi
on
Control
Multiba
nd
Direct
Retry
Based
on UE
Location
HSUPA
Introduc
tion
Package
DRD
Introduc
tion
Package
FakeEc BSC690 SET WRFD- TTI Meaning: Substitute of the real-time P-CPICH Ec/N0
No 0 UFRC 010690 Switch when a UE establishes a service or transits from the
for BE CELL_FACH or CELL_PCH state to the CELL_DCH
Services state and the RNC does not receive the P-CPICH Ec/N0
Based value reported by the UE or the P-CPICH Ec/N0 value
on reported by the UE after the period specified by the
Coverag EcN0EffectTime parameter expires. This parameter is
e used for determining whether UEs are under weak
coverage in the following algorithms: coverage-based
BE service initial TTI selection algorithm, the algorithm
for determining whether BE services on the UE will
switch from HSUPA channels to R99 channels, the
coverage- and load- based algorithm for dynamic
configuration of the channel mapped to downlink SRBs
in access mode, and the algorithm for Small Target
Retransmit on RSCP and RTWP. Value 50 of this
parameter indicates that this parameter is invalid. In this
case, a UE is not in a weak coverage area even if the
RNC does not receive the P-CPICH Ec/N0 value
reported by the UE or the P-CPICH Ec/N0 value
reported by the UE after the period specified by the
"EcN0EffectTime" parameter expires.
GUI Value Range: 0~50
Unit: 0.5dB
Actual Value Range: -24.5~0.5(Actual Value = (GUI
Value - 49(offset)) x 0.5)
Default Value: 50
FakeEc BSC691 SET WRFD- TTI Meaning: Substitute of the real-time P-CPICH Ec/N0
No 0 UFRC 010690 Switch when a UE establishes a service or transits from the
for BE CELL_FACH or CELL_PCH state to the CELL_DCH
Services state and the RNC does not receive the P-CPICH Ec/N0
Based value reported by the UE or the P-CPICH Ec/N0 value
on reported by the UE after the period specified by the
Coverag EcN0EffectTime parameter expires. This parameter is
e used for determining whether UEs are under weak
coverage in the following algorithms: coverage-based
BE service initial TTI selection algorithm, the algorithm
for determining whether BE services on the UE will
switch from HSUPA channels to R99 channels, the
coverage- and load- based algorithm for dynamic
configuration of the channel mapped to downlink SRBs
in access mode, and the algorithm for Small Target
Retransmit on RSCP and RTWP. Value 50 of this
parameter indicates that this parameter is invalid. In this
case, a UE is not in a weak coverage area even if the
RNC does not receive the P-CPICH Ec/N0 value
reported by the UE or the P-CPICH Ec/N0 value
reported by the UE after the period specified by the
"EcN0EffectTime" parameter expires.
GUI Value Range: 0~50
Unit: 0.5dB
Actual Value Range: -24.5~0.5(Actual Value = (GUI
Value - 49(offset)) x 0.5)
Default Value: 50
RsvU32 BSC690 SET None None Meaning: RRM algorithm reserved U32 para 8. The 32-
Para8 0 UALGO bit parameter is reserved for further change request use.
RSVPA Disuse statement: This parameter is used temporarily in
RA patch versions and will be replaced with a new
parameter in later versions. The new parameter ID
reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: 0~4294967295
Unit: None
Actual Value Range: 0~4294967295
Default Value: 0
RsvU32 BSC691 SET None None Meaning: RRM algorithm reserved U32 para 8. The 32-
Para8 0 UALGO bit parameter is reserved for further change request use.
RSVPA Disuse statement: This parameter is used temporarily in
RA patch versions and will be replaced with a new
parameter in later versions. The new parameter ID
reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: 0~4294967295
Unit: None
Actual Value Range: 0~4294967295
Default Value: 0
SrbOver BSC690 SET WRFD- SRB Meaning: RSCP threshold for the coverage-based and
HsdpaR 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
scpDow UALIT HSDPA the channel mapped to downlink SRBs in weak
nThd YEVAL coverage areas. If the valid RSCP value of the best cell
UATE is less than or equal to the value of this parameter, the
UE is located in a weak coverage area.
GUI Value Range: -115~-25
Unit: dBm
Actual Value Range: -115~-25
Default Value: -90
SrbOver BSC690 SET WRFD- SRB Meaning: Ec/N0 threshold for the coverage-based and
HsdpaE 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
cn0Dow UALIT HSDPA the channel mapped to downlink SRBs in weak
nThd YEVAL coverage areas. If the valid Ec/N0 value of the best cell
UATE is less than or equal to the value of this parameter, the
UE is located in a weak coverage area.
GUI Value Range: 0~49
Unit: dB
Actual Value Range: -24.5~0(Actual Value = GUI
Value x 0.5 - 24.5 dB)
Default Value: 29
SrbOver BSC690 SET WRFD- SRB Meaning: RSCP threshold for the coverage-based and
HsdpaR 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
scpUpT UALIT HSDPA the channel mapped to downlink SRBs in strong
hd YEVAL coverage areas. If the valid RSCP and Ec/N0 of the best
UATE cell are greater than the corresponding RSCP and Ec/
N0 thresholds for strong coverage areas, the UE is
located in a strong coverage area.
GUI Value Range: -115~-25
Unit: dBm
Actual Value Range: -115~-25
Default Value: -80
SrbOver BSC690 SET WRFD- SRB Meaning: Ec/N0 threshold for the coverage-based and
HsdpaE 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
cn0UpT UALIT HSDPA the channel mapped to downlink SRBs in strong
hd YEVAL coverage areas. If the valid RSCP and Ec/N0 of the best
UATE cell are greater than the corresponding RSCP and Ec/
N0 thresholds for strong coverage areas, the UE is
located in a strong coverage area.
GUI Value Range: 0~49
Unit: dB
Actual Value Range: -24.5~0(Actual Value = GUI
Value x 0.5 - 24.5 dB)
Default Value: 35
RsvSwit BSC690 SET None None Meaning: RRM algorithm reserved U32 Switch Para 11.
ch11 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_11_BIT1,
RESERVED_SWITCH_11_BIT2,
RESERVED_SWITCH_11_BIT3,
RESERVED_SWITCH_11_BIT4,
RESERVED_SWITCH_11_BIT5,
RESERVED_SWITCH_11_BIT6,
RESERVED_SWITCH_11_BIT7,
RESERVED_SWITCH_11_BIT8,
RESERVED_SWITCH_11_BIT9,
RESERVED_SWITCH_11_BIT10,
RESERVED_SWITCH_11_BIT11,
RESERVED_SWITCH_11_BIT12,
RESERVED_SWITCH_11_BIT13,
RESERVED_SWITCH_11_BIT14,
RESERVED_SWITCH_11_BIT15,
RESERVED_SWITCH_11_BIT16,
RESERVED_SWITCH_11_BIT17,
RESERVED_SWITCH_11_BIT18,
RESERVED_SWITCH_11_BIT19,
RESERVED_SWITCH_11_BIT20,
RESERVED_SWITCH_11_BIT21,
RESERVED_SWITCH_11_BIT22,
RESERVED_SWITCH_11_BIT23,
RESERVED_SWITCH_11_BIT24,
RESERVED_SWITCH_11_BIT25,
RESERVED_SWITCH_11_BIT26,
RESERVED_SWITCH_11_BIT27,
RESERVED_SWITCH_11_BIT28,
RESERVED_SWITCH_11_BIT29,
RESERVED_SWITCH_11_BIT30,
RESERVED_SWITCH_11_BIT31,
RESERVED_SWITCH_11_BIT32
Unit: None
Actual Value Range:
RESERVED_SWITCH_11_BIT1,
RESERVED_SWITCH_11_BIT2,
RESERVED_SWITCH_11_BIT3,
RESERVED_SWITCH_11_BIT4,
RESERVED_SWITCH_11_BIT5,
RESERVED_SWITCH_11_BIT6,
RESERVED_SWITCH_11_BIT7,
RESERVED_SWITCH_11_BIT8,
RESERVED_SWITCH_11_BIT9,
RESERVED_SWITCH_11_BIT10,
RESERVED_SWITCH_11_BIT11,
RESERVED_SWITCH_11_BIT12,
RESERVED_SWITCH_11_BIT13,
RESERVED_SWITCH_11_BIT14,
RESERVED_SWITCH_11_BIT15,
RESERVED_SWITCH_11_BIT16,
RESERVED_SWITCH_11_BIT17,
RESERVED_SWITCH_11_BIT18,
RESERVED_SWITCH_11_BIT19,
RESERVED_SWITCH_11_BIT20,
RESERVED_SWITCH_11_BIT21,
RESERVED_SWITCH_11_BIT22,
RESERVED_SWITCH_11_BIT23,
RESERVED_SWITCH_11_BIT24,
RESERVED_SWITCH_11_BIT25,
RESERVED_SWITCH_11_BIT26,
RESERVED_SWITCH_11_BIT27,
RESERVED_SWITCH_11_BIT28,
RESERVED_SWITCH_11_BIT29,
RESERVED_SWITCH_11_BIT30,
RESERVED_SWITCH_11_BIT31,
RESERVED_SWITCH_11_BIT32
Default Value:
RESERVED_SWITCH_11_BIT1:0,RESERVED_SW
ITCH_11_BIT2:0,RESERVED_SWITCH_11_BIT3:0
,RESERVED_SWITCH_11_BIT4:0,RESERVED_S
WITCH_11_BIT5:0,RESERVED_SWITCH_11_BIT
6:0,RESERVED_SWITCH_11_BIT7:0,RESERVED_
SWITCH_11_BIT8:0,RESERVED_SWITCH_11_BI
T9:0,RESERVED_SWITCH_11_BIT10:0,RESERVE
D_SWITCH_11_BIT11:0,RESERVED_SWITCH_11
_BIT12:0,RESERVED_SWITCH_11_BIT13:0,RESE
RVED_SWITCH_11_BIT14:0,RESERVED_SWITC
H_11_BIT15:0,RESERVED_SWITCH_11_BIT16:0,
RESERVED_SWITCH_11_BIT17:0,RESERVED_S
WITCH_11_BIT18:0,RESERVED_SWITCH_11_BI
T19:0,RESERVED_SWITCH_11_BIT20:0,RESERV
ED_SWITCH_11_BIT21:0,RESERVED_SWITCH_1
1_BIT22:0,RESERVED_SWITCH_11_BIT23:0,RES
ERVED_SWITCH_11_BIT24:0,RESERVED_SWIT
CH_11_BIT25:0,RESERVED_SWITCH_11_BIT26:0
,RESERVED_SWITCH_11_BIT27:0,RESERVED_S
WITCH_11_BIT28:0,RESERVED_SWITCH_11_BI
T29:0,RESERVED_SWITCH_11_BIT30:0,RESERV
ED_SWITCH_11_BIT31:0,RESERVED_SWITCH_1
1_BIT32:0
RsvSwit BSC691 SET None None Meaning: RRM algorithm reserved U32 Switch Para 11.
ch11 0 UALGO The 32-bit parameter is reserved for further change
RSVPA request use. Disuse statement: This parameter is used
RA temporarily in patch versions and will be replaced with
a new parameter in later versions. The new parameter
ID reflects the parameter function. Therefore, this
parameter is not recommended for the configuration
interface.
GUI Value Range: RESERVED_SWITCH_11_BIT1,
RESERVED_SWITCH_11_BIT2,
RESERVED_SWITCH_11_BIT3,
RESERVED_SWITCH_11_BIT4,
RESERVED_SWITCH_11_BIT5,
RESERVED_SWITCH_11_BIT6,
RESERVED_SWITCH_11_BIT7,
RESERVED_SWITCH_11_BIT8,
RESERVED_SWITCH_11_BIT9,
RESERVED_SWITCH_11_BIT10,
RESERVED_SWITCH_11_BIT11,
RESERVED_SWITCH_11_BIT12,
RESERVED_SWITCH_11_BIT13,
RESERVED_SWITCH_11_BIT14,
RESERVED_SWITCH_11_BIT15,
RESERVED_SWITCH_11_BIT16,
RESERVED_SWITCH_11_BIT17,
RESERVED_SWITCH_11_BIT18,
RESERVED_SWITCH_11_BIT19,
RESERVED_SWITCH_11_BIT20,
RESERVED_SWITCH_11_BIT21,
RESERVED_SWITCH_11_BIT22,
RESERVED_SWITCH_11_BIT23,
RESERVED_SWITCH_11_BIT24,
RESERVED_SWITCH_11_BIT25,
RESERVED_SWITCH_11_BIT26,
RESERVED_SWITCH_11_BIT27,
RESERVED_SWITCH_11_BIT28,
RESERVED_SWITCH_11_BIT29,
RESERVED_SWITCH_11_BIT30,
RESERVED_SWITCH_11_BIT31,
RESERVED_SWITCH_11_BIT32
Unit: None
Actual Value Range:
RESERVED_SWITCH_11_BIT1,
RESERVED_SWITCH_11_BIT2,
RESERVED_SWITCH_11_BIT3,
RESERVED_SWITCH_11_BIT4,
RESERVED_SWITCH_11_BIT5,
RESERVED_SWITCH_11_BIT6,
RESERVED_SWITCH_11_BIT7,
RESERVED_SWITCH_11_BIT8,
RESERVED_SWITCH_11_BIT9,
RESERVED_SWITCH_11_BIT10,
RESERVED_SWITCH_11_BIT11,
RESERVED_SWITCH_11_BIT12,
RESERVED_SWITCH_11_BIT13,
RESERVED_SWITCH_11_BIT14,
RESERVED_SWITCH_11_BIT15,
RESERVED_SWITCH_11_BIT16,
RESERVED_SWITCH_11_BIT17,
RESERVED_SWITCH_11_BIT18,
RESERVED_SWITCH_11_BIT19,
RESERVED_SWITCH_11_BIT20,
RESERVED_SWITCH_11_BIT21,
RESERVED_SWITCH_11_BIT22,
RESERVED_SWITCH_11_BIT23,
RESERVED_SWITCH_11_BIT24,
RESERVED_SWITCH_11_BIT25,
RESERVED_SWITCH_11_BIT26,
RESERVED_SWITCH_11_BIT27,
RESERVED_SWITCH_11_BIT28,
RESERVED_SWITCH_11_BIT29,
RESERVED_SWITCH_11_BIT30,
RESERVED_SWITCH_11_BIT31,
RESERVED_SWITCH_11_BIT32
Default Value:
RESERVED_SWITCH_11_BIT1:0,RESERVED_SW
ITCH_11_BIT2:0,RESERVED_SWITCH_11_BIT3:0
,RESERVED_SWITCH_11_BIT4:0,RESERVED_S
WITCH_11_BIT5:0,RESERVED_SWITCH_11_BIT
6:0,RESERVED_SWITCH_11_BIT7:0,RESERVED_
SWITCH_11_BIT8:0,RESERVED_SWITCH_11_BI
T9:0,RESERVED_SWITCH_11_BIT10:0,RESERVE
D_SWITCH_11_BIT11:0,RESERVED_SWITCH_11
_BIT12:0,RESERVED_SWITCH_11_BIT13:0,RESE
RVED_SWITCH_11_BIT14:0,RESERVED_SWITC
H_11_BIT15:0,RESERVED_SWITCH_11_BIT16:0,
RESERVED_SWITCH_11_BIT17:0,RESERVED_S
WITCH_11_BIT18:0,RESERVED_SWITCH_11_BI
T19:0,RESERVED_SWITCH_11_BIT20:0,RESERV
ED_SWITCH_11_BIT21:0,RESERVED_SWITCH_1
1_BIT22:0,RESERVED_SWITCH_11_BIT23:0,RES
ERVED_SWITCH_11_BIT24:0,RESERVED_SWIT
CH_11_BIT25:0,RESERVED_SWITCH_11_BIT26:0
,RESERVED_SWITCH_11_BIT27:0,RESERVED_S
WITCH_11_BIT28:0,RESERVED_SWITCH_11_BI
T29:0,RESERVED_SWITCH_11_BIT30:0,RESERV
ED_SWITCH_11_BIT31:0,RESERVED_SWITCH_1
1_BIT32:0
Channel BSC690 SET WRFD- HSUPA Meaning: This parameter specifies the value of the
RetryHo 0 UCOIF 0106140 2ms TTI channel retry handover timer. When handover is
TimerLe TIMER 3 Dynami performed and some higher HSPA or HSPA plus
n WRFD- c technique is supported, UTRAN will trigger the
021101 Channel reconfiguration for the higher techniques. Pingpang will
Configu happen when the reconfiguration is triggered
WRFD- immediately when handover succeeds, because
010685 ration
Control handover procedure is frequently. In order to avoid the
WRFD- (DCCC) pingpang, this timer will start after handover procedure
010652 is performed, and the reconfiguration will not be
Downlin
WRFD- triggered until the timer expires.
k
010686 Enhance GUI Value Range: 0~999
WRFD- d L2 Unit: s
010687 SRB Actual Value Range: 0~999
WRFD- over Default Value: 2
010684 HSDPA
WRFD- CPC -
0106140 DTX /
4 DRX
WRFD- CPC -
010683 HS-
WRFD- SCCH
150209 less
operatio
WRFD- n
010636
2x2
WRFD- MIMO
021200
HSUPA
2ms/
10ms
TTI
Handov
er
Downlin
k
64QAM
DB-
HSDPA
SRB
over
HSUPA
HCS
(Hierarc
hical
Cell
Structur
e)
Channel BSC691 SET WRFD- HSUPA Meaning: This parameter specifies the value of the
RetryHo 0 UCOIF 0106140 2ms TTI channel retry handover timer. When handover is
TimerLe TIMER 3 Dynami performed and some higher HSPA or HSPA plus
n WRFD- c technique is supported, UTRAN will trigger the
021101 Channel reconfiguration for the higher techniques. Pingpang will
Configu happen when the reconfiguration is triggered
WRFD- immediately when handover succeeds, because
010685 ration
Control handover procedure is frequently. In order to avoid the
WRFD- (DCCC) pingpang, this timer will start after handover procedure
010652 is performed, and the reconfiguration will not be
Downlin
WRFD- triggered until the timer expires.
k
010686 Enhance GUI Value Range: 0~999
WRFD- d L2 Unit: s
010687 SRB Actual Value Range: 0~999
WRFD- over Default Value: 2
010684 HSDPA
WRFD- CPC -
0106140 DTX /
4 DRX
WRFD- CPC -
010683 HS-
WRFD- SCCH
150209 less
operatio
WRFD- n
010636
2x2
WRFD- MIMO
021200
HSUPA
2ms/
10ms
TTI
Handov
er
Downlin
k
64QAM
DB-
HSDPA
SRB
over
HSUPA
HCS
(Hierarc
hical
Cell
Structur
e)
IurHsdp BSC690 ADD WRFD- HSDPA Meaning: Indicating whether to enable HSDPA on the
aSuppIn 0 UNRNC 010651 over Iur Iur interface. When this parameter is set to OFF, an
d MOD HSDPA UE's downlink channel is changed from an
UNRNC HSDSCH to a DCH if the UE initiates a serving cell
change process to the DRNC. If the UE attempts to add
a cell under the DRNC to the active set, new radio links
can be set up only over DCHs. When this parameter is
set to ON, the Iur interface supports HSDPA.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
IurHsdp BSC691 ADD WRFD- HSDPA Meaning: Indicating whether to enable HSDPA on the
aSuppIn 0 UNRNC 010651 over Iur Iur interface. When this parameter is set to OFF, an
d MOD HSDPA UE's downlink channel is changed from an
UNRNC HSDSCH to a DCH if the UE initiates a serving cell
change process to the DRNC. If the UE attempts to add
a cell under the DRNC to the active set, new radio links
can be set up only over DCHs. When this parameter is
set to ON, the Iur interface supports HSDPA.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF
PWRM BTS390 SET WRFD- HSDPA Meaning: Indicates the power margin reserved for R99
GN 0, ULOCE 0106100 Power channels. It specifies the power percentage relative to
BTS390 LLMAC 4 Control the maximum cell transmit power.
0 HSPAR GUI Value Range: 0~100
WCDM A
A Unit: %
LST
ULOCE Actual Value Range: 0~100
LLMAC Default Value: 5
HSPAR
A
HspaPo BSC690 ADD WRFD- HSDPA Meaning: This parameter specifies the offset between
wer 0 UCELL 0106100 Power the total HSPA power and the maximum transmission
HSDPA 4 Control power of a cell. The total HSPA power is the maximum
MOD value of HSPA dynamical power can be adjusted. For
UCELL details about this parameter, see 3GPP TS 25.308.
HSDPA GUI Value Range: -500~0
Unit: 0.1dB
Actual Value Range: -50~0
Default Value: 0
HspaPo BSC691 ADD WRFD- HSDPA Meaning: This parameter specifies the offset between
wer 0 UCELL 0106100 Power the total HSPA power and the maximum transmission
HSDPA 4 Control power of a cell. The total HSPA power is the maximum
MOD value of HSPA dynamical power can be adjusted. For
UCELL details about this parameter, see 3GPP TS 25.308.
HSDPA GUI Value Range: -500~0
Unit: 0.1dB
Actual Value Range: -50~0
Default Value: 0
HsScch BSC690 ADD WRFD- Time Meaning: This parameter decides the maximum number
CodeNu 0 UCELL 0106101 and HS- of HSDPA subscribers that the NodeB can schedule in
m HSDPA 8 PDSCH a TTI period. For detailed information of this parameter,
MOD WRFD- Codes see 3GPP TS 25.308.
UCELL 010610 Multiple GUI Value Range: 1~15
HSDPA x
WRFD- Unit: None
020108 HSDPA
Introduc Actual Value Range: 1~15
tion Default Value: 4
Package
Code
Resourc
e
Manage
ment
HsScch BSC691 ADD WRFD- Time Meaning: This parameter decides the maximum number
CodeNu 0 UCELL 0106101 and HS- of HSDPA subscribers that the NodeB can schedule in
m HSDPA 8 PDSCH a TTI period. For detailed information of this parameter,
MOD WRFD- Codes see 3GPP TS 25.308.
UCELL 010610 Multiple GUI Value Range: 1~15
HSDPA x
WRFD- Unit: None
020108 HSDPA
Introduc Actual Value Range: 1~15
tion Default Value: 4
Package
Code
Resourc
e
Manage
ment
DynHss BSC690 ADD WRFD- HSDPA Meaning: Switch for controlling whether the NodeB
cchAllo 0 UCELL 0106100 Static dynamically allocates spreading codes (SCs) to HSPA
cSwitch HSDPA 5 Code services based on traffic requirements. A new policy of
MOD Allocati allocating SCs to HSPA services applies under the
UCELL on and following conditions: 1 This switch is turned on. 2
HSDPA RNC- HSDPA and HSUPA functions are activated before the
Controll cell is set up. The RNC allocates SCs to HS-SCCH, E-
ed RGCH, and E-HICH based on the new policy. The
Dynami NodeB dynamically reallocates the SCs to the HS-
c Code PDSCH for HSPA services based on traffic
Allocati requirements. This new policy increases the number of
on SCs available for the HS-PDSCH to a maximum of 15,
increasing HSDPA throughput. If not all the preceding
conditions are met, the old policy applies,
compromising chances of 15 SCs being available for the
HS-PDSCH.
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(OFF)
AllocCo BSC690 ADD WRFD- HSDPA Meaning: HS-PDSCH code allocation mode: Manual or
deMode 0 UCELL 0106100 Static Automatic. If Manual is chosen, parameter " Code
HSDPA 5 Code Number for HS-PDSCH " determines HS-PDSCH code
MOD WRFD- Allocati number to be allocated. If Automatic is chosen,
UCELL 010631 on and according to the number of codes occupied by R99
HSDPA RNC- services, allocate HS-PDSCH code number between
WRFD- Controll configured " Code Max Number for HS-PDSCH " and
0106100 ed " Code Min Number for HS-PDSCH ". For detailed
1 Dynami information of this parameter, see 3GPP TS 25.308.
c Code GUI Value Range: Manual(Manual), Automatic
Allocati (Automatic)
on
Unit: None
Dynami
c Code Actual Value Range: Manual, Automatic
Allocati Default Value: Automatic(Automatic)
on
Based
on Node
B
15
Codes
per Cell
AllocCo BSC691 ADD WRFD- HSDPA Meaning: HS-PDSCH code allocation mode: Manual or
deMode 0 UCELL 0106100 Static Automatic. If Manual is chosen, parameter " Code
HSDPA 5 Code Number for HS-PDSCH " determines HS-PDSCH code
MOD WRFD- Allocati number to be allocated. If Automatic is chosen,
UCELL 010631 on and according to the number of codes occupied by R99
HSDPA RNC- services, allocate HS-PDSCH code number between
WRFD- Controll configured " Code Max Number for HS-PDSCH " and
0106100 ed " Code Min Number for HS-PDSCH ". For detailed
1 Dynami information of this parameter, see 3GPP TS 25.308.
c Code GUI Value Range: Manual(Manual), Automatic
Allocati (Automatic)
on
Unit: None
Dynami
c Code Actual Value Range: Manual, Automatic
Allocati Default Value: Automatic(Automatic)
on
Based
on Node
B
15
Codes
per Cell
DYNCO BTS390 SET WRFD- Dynami Meaning: Indicates the Dynamic Code Switch. The
DESW 0, ULOCE 010631 c Code function will be enabled if this parameter is set to OPEN.
BTS390 LLMAC Allocati When this switch is turned on, the cell codes are used
0 HSPAR on efficiently, and the system capacity is improved.
WCDM A Based GUI Value Range: OPEN(open), CLOSE(close)
A LST on Node
B Unit: None
ULOCE
LLMAC Actual Value Range: OPEN, CLOSE
HSPAR Default Value: OPEN(open)
A
HsPdsch BSC690 ADD WRFD- HSDPA Meaning: Number of HS-PDSCH codes. For details
CodeNu 0 UCELL 0106100 Static about this parameter, see 3GPP TS 25.308.
m HSDPA 5 Code GUI Value Range: 1~15
MOD WRFD- Allocati
on and Unit: None
UCELL 010631
HSDPA RNC- Actual Value Range: 1~15
WRFD- Controll
0106100 Default Value: 5
ed
1 Dynami
c Code
Allocati
on
Dynami
c Code
Allocati
on
Based
on Node
B
15
Codes
per Cell
HsPdsch BSC691 ADD WRFD- HSDPA Meaning: Number of HS-PDSCH codes. For details
CodeNu 0 UCELL 0106100 Static about this parameter, see 3GPP TS 25.308.
m HSDPA 5 Code GUI Value Range: 1~15
MOD WRFD- Allocati
on and Unit: None
UCELL 010631
HSDPA RNC- Actual Value Range: 1~15
WRFD- Controll
0106100 Default Value: 5
ed
1 Dynami
c Code
Allocati
on
Dynami
c Code
Allocati
on
Based
on Node
B
15
Codes
per Cell
HsPdsch BSC690 ADD WRFD- HSDPA Meaning: The parameter specifies the minimum
MinCod 0 UCELL 0106100 Static number of the HS-PDSCH codes. This parameter is
eNum HSDPA 5 Code valid only when "Allocate Code Mode" is set to
MOD WRFD- Allocati Automatic. The number of codes used by the HS-
UCELL 010631 on and PDSCH is dynamically set between "Code Min Number
HSDPA RNC- for HS-PDSCH" and "Code Max Number for HS-
WRFD- Controll PDSCH", based on the idle state of the code tree. When
0106100 ed the non-H services need more code resources, the non-
1 Dynami H service will gradually occupy the codes used by the
c Code HS-PDSCH. The number of codes the HS-DPSCH
Allocati reserved is not less than the value of "Code Min Number
on for HS-PDSCH". For detailed information of this
Dynami parameter, see 3GPP TS 25.308.
c Code GUI Value Range: 1~15
Allocati Unit: None
on
Based Actual Value Range: 1~15
on Node Default Value: 1
B
15
Codes
per Cell
HsPdsch BSC691 ADD WRFD- HSDPA Meaning: The parameter specifies the minimum
MinCod 0 UCELL 0106100 Static number of the HS-PDSCH codes. This parameter is
eNum HSDPA 5 Code valid only when "Allocate Code Mode" is set to
MOD WRFD- Allocati Automatic. The number of codes used by the HS-
UCELL 010631 on and PDSCH is dynamically set between "Code Min Number
HSDPA RNC- for HS-PDSCH" and "Code Max Number for HS-
WRFD- Controll PDSCH", based on the idle state of the code tree. When
0106100 ed the non-H services need more code resources, the non-
1 Dynami H service will gradually occupy the codes used by the
c Code HS-PDSCH. The number of codes the HS-DPSCH
Allocati reserved is not less than the value of "Code Min Number
on for HS-PDSCH". For detailed information of this
Dynami parameter, see 3GPP TS 25.308.
c Code GUI Value Range: 1~15
Allocati Unit: None
on
Based Actual Value Range: 1~15
on Node Default Value: 1
B
15
Codes
per Cell
HsPdsch BSC690 ADD WRFD- HSDPA Meaning: The parameter determines the maximum
MaxCod 0 UCELL 0106100 Static number of HS-PDSCH codes. This parameter is valid
eNum HSDPA 5 Code only when "Allocate Code Mode" is set to "Automatic".
MOD WRFD- Allocati The number of codes used by the HS-PDSCH is
UCELL 010631 on and dynamically set between "Code Min Number for HS-
HSDPA RNC- PDSCH" and "Code Max Number for HS-PDSCH",
WRFD- Controll based on whether the code tree is idle or busy. When the
0106100 ed code resource used by the non-HSPA services is little,
1 Dynami the HS-PDSCH uses the rest idle codes as much as
c Code possible, and the maximum number of idle codes
Allocati (SF=16 continuous codes) is equal to the value of "Code
on Max Number for HS-PDSCH". For detailed
Dynami information of this parameter, see 3GPP TS 25.308.
c Code GUI Value Range: 1~15
Allocati Unit: None
on
Based Actual Value Range: 1~15
on Node Default Value: 5
B
15
Codes
per Cell
HsPdsch BSC691 ADD WRFD- HSDPA Meaning: The parameter determines the maximum
MaxCod 0 UCELL 0106100 Static number of HS-PDSCH codes. This parameter is valid
eNum HSDPA 5 Code only when "Allocate Code Mode" is set to "Automatic".
MOD WRFD- Allocati The number of codes used by the HS-PDSCH is
UCELL 010631 on and dynamically set between "Code Min Number for HS-
HSDPA RNC- PDSCH" and "Code Max Number for HS-PDSCH",
WRFD- Controll based on whether the code tree is idle or busy. When the
0106100 ed code resource used by the non-HSPA services is little,
1 Dynami the HS-PDSCH uses the rest idle codes as much as
c Code possible, and the maximum number of idle codes
Allocati (SF=16 continuous codes) is equal to the value of "Code
on Max Number for HS-PDSCH". For detailed
Dynami information of this parameter, see 3GPP TS 25.308.
c Code GUI Value Range: 1~15
Allocati Unit: None
on
Based Actual Value Range: 1~15
on Node Default Value: 5
B
15
Codes
per Cell
CodeAd BSC690 ADD WRFD- HSDPA Meaning: Whether to enable the HSDPA-based code
jForHsd 0 UCELL 0106100 Static reshuffling function. When the HSDPA-based code
paSwitc HSDPA 5 Code reshuffling function is enabled, codes occupied by R99
h MOD Allocati services are reshuffled in descending order of the code
UCELL on and number to release the shared code resources of adjacent
HSDPA RNC- HSDPA UEs.
Controll GUI Value Range: OFF(OFF), ON(ON)
ed
Dynami Unit: None
c Code Actual Value Range: OFF, ON
Allocati Default Value: ON(ON)
on
CodeAd BSC691 ADD WRFD- HSDPA Meaning: Whether to enable the HSDPA-based code
jForHsd 0 UCELL 0106100 Static reshuffling function. When the HSDPA-based code
paSwitc HSDPA 5 Code reshuffling function is enabled, codes occupied by R99
h MOD Allocati services are reshuffled in descending order of the code
UCELL on and number to release the shared code resources of adjacent
HSDPA RNC- HSDPA UEs.
Controll GUI Value Range: OFF(OFF), ON(ON)
ed
Dynami Unit: None
c Code Actual Value Range: OFF, ON
Allocati Default Value: ON(ON)
on
CodeAd BSC690 ADD WRFD- HSDPA Meaning: H-based code tree reshuffle user number
jForHsd 0 UCELL 0106100 Static threshold. When the switch "Code Adjust Switch for
paUserN HSDPA 5 Code HSDPA" is enabled, if the number of users on the tree
umThd MOD Allocati to be reshuffled is no greater than this parameter, the
UCELL on and reshuffle is allowed. Otherwise, the reshuffle is given
HSDPA RNC- up. This parameter limits the number of users involved
Controll in one reshuffle so that reshuffle on mass users at a time
ed is avoided.
Dynami GUI Value Range: 1~16
c Code
Allocati Unit: None
on Actual Value Range: 1~16
Default Value: 3
CodeAd BSC691 ADD WRFD- HSDPA Meaning: H-based code tree reshuffle user number
jForHsd 0 UCELL 0106100 Static threshold. When the switch "Code Adjust Switch for
paUserN HSDPA 5 Code HSDPA" is enabled, if the number of users on the tree
umThd MOD Allocati to be reshuffled is no greater than this parameter, the
UCELL on and reshuffle is allowed. Otherwise, the reshuffle is given
HSDPA RNC- up. This parameter limits the number of users involved
Controll in one reshuffle so that reshuffle on mass users at a time
ed is avoided.
Dynami GUI Value Range: 1~16
c Code
Allocati Unit: None
on Actual Value Range: 1~16
Default Value: 3
MAXN BTS390 SET WRFD- HSDPA Meaning: Indicates the MAX HARQ Retransmission
ONCON 0, ULOCE 0106100 H-ARQ Times of Non-Conversational service in CELL DCH
VERHA BTS390 LLMAC 9 & state.
RQRT 0 HSPAR Scheduli GUI Value Range: 0~10
WCDM A ng
A (MAX Unit: None
LST
ULOCE C/I, RR Actual Value Range: 0~10
LLMAC and PF) Default Value: 4
HSPAR
A
MAXEF BTS390 SET WRFD- Downlin Meaning: Indicates the maximum number of blind
ACHHA 0, ULOCE 010688 k HARQ retransmissions for E-FACH users.
RQRT BTS390 LLMAC Enhance GUI Value Range: 0~10
0 HSPAR d
WCDM A CELL_F Unit: None
A LST ACH Actual Value Range: 0~10
ULOCE Default Value: 2
LLMAC
HSPAR
A
MAXEF BTS390 SET WRFD- Uplink Meaning: Indicates the maximum number of HARQ
ACHHS 0, ULOCE 010701 Enhance retransmissions when the UE in CELL_FACH supports
HARQR BTS390 LLMAC d the feedbacks over the HS-DPCCH.
T 0 HSPAR CELL_F GUI Value Range: 0~10
WCDM A ACH
A Unit: None
LST
ULOCE Actual Value Range: 0~10
LLMAC Default Value: 4
HSPAR
A
SM BTS390 SET WRFD- HSDPA Meaning: Indicates the HSDPA Scheduling Method.
0, ULOCE 0106100 H-ARQ PF: The differences between channel environments of
BTS390 LLMAC 9 & users are considered in order to ensure equity among
0 HSPAR Scheduli users. Enhanced PF: This algorithm is an enhancement
WCDM A ng to PF. Channel quality is considered in order to reach
A LST (MAX high resource efficiency and gain a high system
ULOCE C/I, RR capacity. Round Robin: Scheduling opportunities are
LLMAC and PF) allocated among users simply and effectively on a
HSPAR polling basis. The system throughput is low. Max C/I:
A This algorithm brings about the maximum possible
system throughput, but it cannot ensures equity between
users or meet users' QoS requirements.
GUI Value Range: EPF(Enhanced PF), PF(PF), RR
(Round Robin), MAXCI(Max C/I), EPF_LOC
(Location based EPF)
Unit: None
Actual Value Range: EPF, PF, RR, MAXCI, EPF_LOC
Default Value: EPF(Enhanced PF)
HsPdsch BSC690 ADD WRFD- HSDPA Meaning: This parameter named Measure Power Offset
MPOCo 0 UCELL 010610 Introduc Constant is used to compute measurement power offset.
nstEnum HSDPA WRFD- tion Measurement power offset is used by UE to obtain total
MOD 0106100 Package received HS-PDSCH power. The calculation for
UCELL 4 HSDPA Measure Power Offset is shown below: Measure Power
HSDPA Power Offset = Max(-6, Min(13,CellMaxPower -
Control PcpichPower - Measure Power OffsetConstant)). For
details of the IE "Measure Power Offset", see 3GPP TS
25.214.
GUI Value Range: Minus3.0DB(-3.0dB), Minus2.5DB
(-2.5dB), Minus2.0DB(-2.0dB), Minus1.5DB(-1.5dB),
Minus1.0DB(-1.0dB), Minus0.5DB(-0.5dB), 0.0DB
(0.0dB), 0.5DB(0.5dB), 1.0DB(1.0dB), 1.5DB(1.5dB),
2.0DB(2.0dB), 2.5DB(2.5dB), 3.0DB(3.0dB), 3.5DB
(3.5dB), 4.0DB(4.0dB), 4.5DB(4.5dB), 5.0DB(5.0dB),
5.5DB(5.5dB), 6.0DB(6.0dB), 6.5DB(6.5dB), 7.0DB
(7.0dB), 7.5DB(7.5dB), 8.0DB(8.0dB), 8.5DB(8.5dB),
9.0DB(9.0dB), 9.5DB(9.5dB), 10.0DB(10.0dB),
10.5DB(10.5dB), 11.0DB(11.0dB), 11.5DB(11.5dB),
12.0DB(12.0dB), 12.5DB(12.5dB), 13.0DB(13.0dB),
13.5DB(13.5dB), 14.0DB(14.0dB), 14.5DB(14.5dB),
15.0DB(15.0dB), 15.5DB(15.5dB), 16.0DB(16.0dB),
16.5DB(16.5dB), 17.0DB(17.0dB), 17.5DB(17.5dB),
18.0DB(18.0dB), 18.5DB(18.5dB), 19.0DB(19.0dB)
Unit: dB
Actual Value Range: -3.0, -2.5, -2.0, -1.5, -1.0, -0.5, 0.0,
0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5, 6.0, 6.5,
7.0, 7.5, 8.0, 8.5, 9.0, 9.5, 10.0, 10.5, 11.0, 11.5, 12.0,
12.5, 13.0, 13.5, 14.0, 14.5, 15.0, 15.5, 16.0, 16.5, 17.0,
17.5, 18.0, 18.5, 19.0
Default Value: 2.5DB(2.5dB)
HsPdsch BSC691 ADD WRFD- HSDPA Meaning: This parameter named Measure Power Offset
MPOCo 0 UCELL 010610 Introduc Constant is used to compute measurement power offset.
nstEnum HSDPA WRFD- tion Measurement power offset is used by UE to obtain total
MOD 0106100 Package received HS-PDSCH power. The calculation for
UCELL 4 HSDPA Measure Power Offset is shown below: Measure Power
HSDPA Power Offset = Max(-6, Min(13,CellMaxPower -
Control PcpichPower - Measure Power OffsetConstant)). For
details of the IE "Measure Power Offset", see 3GPP TS
25.214.
GUI Value Range: Minus3.0DB(-3.0dB), Minus2.5DB
(-2.5dB), Minus2.0DB(-2.0dB), Minus1.5DB(-1.5dB),
Minus1.0DB(-1.0dB), Minus0.5DB(-0.5dB), 0.0DB
(0.0dB), 0.5DB(0.5dB), 1.0DB(1.0dB), 1.5DB(1.5dB),
2.0DB(2.0dB), 2.5DB(2.5dB), 3.0DB(3.0dB), 3.5DB
(3.5dB), 4.0DB(4.0dB), 4.5DB(4.5dB), 5.0DB(5.0dB),
5.5DB(5.5dB), 6.0DB(6.0dB), 6.5DB(6.5dB), 7.0DB
(7.0dB), 7.5DB(7.5dB), 8.0DB(8.0dB), 8.5DB(8.5dB),
9.0DB(9.0dB), 9.5DB(9.5dB), 10.0DB(10.0dB),
10.5DB(10.5dB), 11.0DB(11.0dB), 11.5DB(11.5dB),
12.0DB(12.0dB), 12.5DB(12.5dB), 13.0DB(13.0dB),
13.5DB(13.5dB), 14.0DB(14.0dB), 14.5DB(14.5dB),
15.0DB(15.0dB), 15.5DB(15.5dB), 16.0DB(16.0dB),
16.5DB(16.5dB), 17.0DB(17.0dB), 17.5DB(17.5dB),
18.0DB(18.0dB), 18.5DB(18.5dB), 19.0DB(19.0dB)
Unit: dB
Actual Value Range: -3.0, -2.5, -2.0, -1.5, -1.0, -0.5, 0.0,
0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0, 4.5, 5.0, 5.5, 6.0, 6.5,
7.0, 7.5, 8.0, 8.5, 9.0, 9.5, 10.0, 10.5, 11.0, 11.5, 12.0,
12.5, 13.0, 13.5, 14.0, 14.5, 15.0, 15.5, 16.0, 16.5, 17.0,
17.5, 18.0, 18.5, 19.0
Default Value: 2.5DB(2.5dB)
HappyB BSC690 SET WRFD- HSDPA Meaning: Happy bit rate. This parameter defines the
R 0 UUSER 0106101 Flow happy bit rate of the best effort (BE) service with
HAPPY 0 Control different user priorities. The RNC sends the happy bit
BR WRFD- Differen rate to the NodeB through the Iub interface. When the
020806 tiated NodeB resource is limited and the HS-DSCH bit rate of
Service the user exceeds the Happy bit rate, the HS-DSCH
WRFD- scheduling priority will be decreased. When this
0106110 Based
on SPI parameter is set to 0, it indicates that NodeB will not
3 adjust the HS-DSCH scheduling priority. This value of
Weight
parameter can be set by "HappyBR" in the "ADD
Scheduli UOPERUSERHAPPYBR" command. If the value of
ng based "HappyBR" in the "ADD UOPERUSERHAPPYBR"
on EPF command is larger than 5000, it will be set to the
and minimum of the "HappyBR" parameter value in the
GBR "SET UUSERHAPPYBR" and 5000.
GUI Value Range: 0~27900
Unit: kbit/s
Actual Value Range: 0~27900
Default Value: 0
HappyB BSC691 SET WRFD- HSDPA Meaning: Happy bit rate. This parameter defines the
R 0 UUSER 0106101 Flow happy bit rate of the best effort (BE) service with
HAPPY 0 Control different user priorities. The RNC sends the happy bit
BR WRFD- Differen rate to the NodeB through the Iub interface. When the
020806 tiated NodeB resource is limited and the HS-DSCH bit rate of
Service the user exceeds the Happy bit rate, the HS-DSCH
WRFD- scheduling priority will be decreased. When this
0106110 Based
on SPI parameter is set to 0, it indicates that NodeB will not
3 adjust the HS-DSCH scheduling priority. This value of
Weight
parameter can be set by "HappyBR" in the "ADD
Scheduli UOPERUSERHAPPYBR" command. If the value of
ng based "HappyBR" in the "ADD UOPERUSERHAPPYBR"
on EPF command is larger than 5000, it will be set to the
and minimum of the "HappyBR" parameter value in the
GBR "SET UUSERHAPPYBR" and 5000.
GUI Value Range: 0~27900
Unit: kbit/s
Actual Value Range: 0~27900
Default Value: 0
RSCLM BTS390 SET WRFD- Scheduli Meaning: Indicates the Resource Limiting Switch. The
SW 0, ULOCE 0106110 ng based function will be enabled if this parameter is set to OPEN.
BTS390 LLMAC 3 on EPF When the resource usage is above the threshold, the
0 HSPAR and throughput may be improved (for example, large GBRs
WCDM A GBR configured for users at the cell edge).
A LST GUI Value Range: OPEN(open), CLOSE(close)
ULOCE Unit: None
LLMAC
HSPAR Actual Value Range: OPEN, CLOSE
A Default Value: OPEN(open)
SPI BSC690 SET WRFD- HSUPA Meaning: Relative priority when RAB data in the PS
0 USPIW 010612 Introduc domain is scheduled. The larger the value of this
EIGHT WRFD- tion parameter, the higher the scheduling priority. Values
0106120 Package 2-11 indicate the scheduling priorities of background
9 HSUPA and interactive services.Value 12 indicates the
HARQ scheduling priority of the streaming service. Value 13
WRFD- indicates the scheduling priority of the conversational
020806 and Fast
UL service. Value 14 indicates the scheduling priority of the
WRFD- Scheduli IMS signaling. Value 15 indicates the scheduling
0106110 ng in priority of the SRB service. Values 0 and 1 are reserved
3 Node B for other services.
SPI BSC691 SET WRFD- HSUPA Meaning: Relative priority when RAB data in the PS
0 USPIW 010612 Introduc domain is scheduled. The larger the value of this
EIGHT WRFD- tion parameter, the higher the scheduling priority. Values
0106120 Package 2-11 indicate the scheduling priorities of background
9 HSUPA and interactive services.Value 12 indicates the
HARQ scheduling priority of the streaming service. Value 13
WRFD- indicates the scheduling priority of the conversational
020806 and Fast
UL service. Value 14 indicates the scheduling priority of the
WRFD- Scheduli IMS signaling. Value 15 indicates the scheduling
0106110 ng in priority of the SRB service. Values 0 and 1 are reserved
3 Node B for other services.
SpiWeig BSC690 SET WRFD- Scheduli Meaning: Weight for service scheduling priority. This
ht 0 USPIW 0106110 ng based weight is used in two algorithms. In scheduling
EIGHT 3 on EPF algorithm, it is used to adjust the handling priority for
WRFD- and different services. In Iub congestion algorithm, it is used
020806 GBR to allocate bandwidth for different services. If the
Differen weight is higher, it is more possible to increase the
WRFD- handling priority of the user or get more Iub bandwidth,
150204 tiated
Service respectively.
Based GUI Value Range: 1~100
on SPI Unit: %
Weight
Actual Value Range: 1~100
Platinu
m User Default Value: 100
Prioritizi
ng
SpiWeig BSC691 SET WRFD- Scheduli Meaning: Weight for service scheduling priority. This
ht 0 USPIW 0106110 ng based weight is used in two algorithms. In scheduling
EIGHT 3 on EPF algorithm, it is used to adjust the handling priority for
WRFD- and different services. In Iub congestion algorithm, it is used
020806 GBR to allocate bandwidth for different services. If the
Differen weight is higher, it is more possible to increase the
WRFD- handling priority of the user or get more Iub bandwidth,
150204 tiated
Service respectively.
Based GUI Value Range: 1~100
on SPI Unit: %
Weight
Actual Value Range: 1~100
Platinu
m User Default Value: 100
Prioritizi
ng
LOCWE BTS390 SET WRFD- EPF_LO Meaning: Indicates the weight of the EPF_LOC (user
IGHT 0, ULOCE 140221 C location-based EPF) algorithm. A larger parameter
BTS390 LLMAC value indicates more factors that should be considered
0 HSPAR for user location-based HSDPA scheduling scheme.
WCDM A GUI Value Range: 0, 1, 2, 3
A LST Unit: None
ULOCE
LLMAC Actual Value Range: 0, 1, 2, 3
HSPAR Default Value: 1
A
MXPW BTS390 SET WRFD- HSDPA Meaning: Indicates the Max Power Per Hs-user.
RPHUS 0, ULOCE 0106100 H-ARQ GUI Value Range: 1~100
R BTS390 LLMAC 9 &
0 HSPAR Scheduli Unit: %
WCDM A ng Actual Value Range: 1~100
A LST (MAX Default Value: 100
ULOCE C/I, RR
LLMAC and PF)
HSPAR
A
RSCAL BTS390 SET WRFD- HSDPA Meaning: Indicates the Resource Allocate Method.
LOCM 0, ULOCE 0106100 H-ARQ Radio resources indicate HSDPA available power
BTS390 LLMAC 9 & resources and code resources. Code Priority: The code
0 HSPAR Scheduli resource priority allocation scheme mainly applies to
WCDM A ng scenarios where power resources are limited. In
A LST (MAX scenarios where power resources are not limited, this
ULOCE C/I, RR scheme lowers the system throughput. Power Priority:
LLMAC and PF) The power resource priority allocation scheme mainly
HSPAR applies to scenarios where code resources are limited.
A In scenarios where code resources are not limited, this
scheme lowers the system throughput. Balance between
Code and Power: The power-code balanced scheme
avoids exhaustion of either type of resources, improves
the resource use efficiency and improves the cell
capacity.
GUI Value Range: CODE_PRI(Code Priority),
POWER_PRI(Power Priority), POWERCODE_BAL
(Balance between Code and Power)
Unit: None
Actual Value Range: CODE_PRI, POWER_PRI,
POWERCODE_BAL
Default Value: POWERCODE_BAL(Balance between
Code and Power)
ULOCE BTS390 SET None None Meaning: Indicates the reserved parameter 1.
LLRSV 0, ULOCE GUI Value Range: RSVDBIT1(Reserved Switch 1),
DPARA BTS390 LLRSV RSVDBIT2(Reserved Switch 2), RSVDBIT3
1 0 DPARA (Reserved Switch 3), RSVDBIT4(Reserved Switch 4),
WCDM LST RSVDBIT5(Reserved Switch 5), RSVDBIT6
A ULOCE (Reserved Switch 6), RSVDBIT7(Reserved Switch 7),
LLRSV RSVDBIT8(Reserved Switch 8), RSVDBIT9
DPARA (Reserved Switch 9), RSVDBIT10(Reserved Switch
10), RSVDBIT11(Reserved Switch 11), RSVDBIT12
(Reserved Switch 12), RSVDBIT13(Reserved Switch
13), RSVDBIT14(Reserved Switch 14), RSVDBIT15
(Reserved Switch 15), RSVDBIT16(Reserved Switch
16), RSVDBIT17(Reserved Switch 17), RSVDBIT18
(Reserved Switch 18), RSVDBIT19(Reserved Switch
19), RSVDBIT20(Reserved Switch 20), RSVDBIT21
(Reserved Switch 21), RSVDBIT22(Reserved Switch
22), RSVDBIT23(Reserved Switch 23), RSVDBIT24
(Reserved Switch 24), RSVDBIT25(Reserved Switch
25), RSVDBIT26(Reserved Switch 26), RSVDBIT27
(Reserved Switch 27), RSVDBIT28(Reserved Switch
28), RSVDBIT29(Reserved Switch 29), RSVDBIT30
(Reserved Switch 30), RSVDBIT31(Reserved Switch
31), RSVDBIT32(Reserved Switch 32)
Unit: None
Actual Value Range: RSVDBIT1, RSVDBIT2,
RSVDBIT3, RSVDBIT4, RSVDBIT5, RSVDBIT6,
RSVDBIT7, RSVDBIT8, RSVDBIT9, RSVDBIT10,
RSVDBIT11, RSVDBIT12, RSVDBIT13,
RSVDBIT14, RSVDBIT15, RSVDBIT16,
RSVDBIT17, RSVDBIT18, RSVDBIT19,
RSVDBIT20, RSVDBIT21, RSVDBIT22,
RSVDBIT23, RSVDBIT24, RSVDBIT25,
RSVDBIT26, RSVDBIT27, RSVDBIT28,
RSVDBIT29, RSVDBIT30, RSVDBIT31,
RSVDBIT32
Default Value: RSVDBIT1:OFF, RSVDBIT2:OFF,
RSVDBIT3:OFF, RSVDBIT4:OFF, RSVDBIT5:OFF,
RSVDBIT6:OFF, RSVDBIT7:OFF, RSVDBIT8:OFF,
RSVDBIT9:OFF, RSVDBIT10:OFF,
RSVDBIT11:OFF, RSVDBIT12:OFF,
RSVDBIT13:OFF, RSVDBIT14:OFF,
RSVDBIT15:OFF, RSVDBIT16:OFF,
RSVDBIT17:OFF, RSVDBIT18:OFF,
RSVDBIT19:OFF, RSVDBIT20:OFF,
RSVDBIT21:OFF, RSVDBIT22:OFF,
RSVDBIT23:OFF, RSVDBIT24:OFF,
RSVDBIT25:OFF, RSVDBIT26:OFF,
RSVDBIT27:OFF, RSVDBIT28:OFF,
RSVDBIT29:OFF, RSVDBIT30:OFF,
RSVDBIT31:OFF, RSVDBIT32:OFF
CQIADJ BTS390 SET WRFD- HSDPA Meaning: Indicates the Channel Quality Indicator(CQI)
ALGOF 0, ULOCE 0106100 Power Adjust Algorithm Switch of non-Conversational
NONCO BTS390 LLMAC 4 Control Service. Not CQI Adjust Algorithm: CQI correction is
N 0 HSPAR not performed. CQI Adjusted by IBLER: CQI
WCDM A correction is performed for non-conversational services
A LST based on the fixed IBLER. The IBLER will converge to
ULOCE this target value. CQI Adjusted by Dynamic BLER: CQI
LLMAC correction is performed for non-conversational services
HSPAR based on the dynamic BLER target value. The BLER
A target value will be dynamically adjusted based on
channel quality fluctuations, thereby achieving optimal
throughput. The BLER will converge to the target value
through CQI correction.
GUI Value Range: NO_CQI_ADJ(Not CQI Adjust
Algorithm), CQI_ADJ_BY_IBLER(CQI Adjusted by
IBLER), CQI_ADJ_BY_DYN_BLER(CQI Adjusted
by Dynamic BLER)
Unit: None
Actual Value Range: NO_CQI_ADJ,
CQI_ADJ_BY_IBLER, CQI_ADJ_BY_DYN_BLER
Default Value: NO_CQI_ADJ(Not CQI Adjust
Algorithm)
NodeBP BSC690 ADD WRFD- DC- Meaning: Protocol version supported by the NodeB.
rotclVer 0 UNODE 010699 HSDPA This parameter is modified based on the actual protocol
B WRFD- +MIMO version of the NodeB when the NodeB protocol version
MOD 010698 HSPA+ upgrade, otherwise it will cause features supported by
UNODE Uplink the new protocol version unavailable.
WRFD-
B 11.5Mbi GUI Value Range: R99, R4, R5, R6, R7, R8, R9
010651
t/s per Unit: None
WRFD- User
010652 Actual Value Range: R99, R4, R5, R6, R7, R8, R9
HSDPA
WRFD- Default Value: R9
over Iur
010693
SRB
WRFD- over
010695 HSDPA
WRFD- DL
010694 64QAM
WRFD- +MIMO
010697 UL
WRFD- Layer 2
010696 Improve
ment
WRFD-
010686 UL
16QAM
WRFD-
140203 E-
DPCCH
WRFD- Boostin
020126 g
WRFD- DC-
010703 HSDPA
WRFD- CPC -
010702 DTX /
WRFD- DRX
010689 HSPA+
WRFD- Uplink
010101 23 Mbit/
s per
WRFD-
User
010687
Mobility
WRFD-
Between
010685
UMTS
WRFD- and LTE
010683 Phase 1
WRFD- HSPA+
010680 Downlin
WRFD- k
010681 84Mbit/
WRFD- s per
010618 User
WRFD- Enhance
0106140 d DRX
3 HSPA+
WRFD- Downlin
010636 k
42Mbps
WRFD-
per User
010635
3GPP
R9
Specific
ations
CPC -
HS-
SCCH
less
operatio
n
Downlin
k
Enhance
d L2
Downlin
k
64QAM
HSPA+
Downlin
k
28Mbps
per User
HSPA+
Downlin
k
21Mbps
per User
IMS
Signalin
g over
HSPA
HSUPA
2ms TTI
SRB
over
HSUPA
HSUPA
over Iur
NodeBP BSC691 ADD WRFD- DC- Meaning: Protocol version supported by the NodeB.
rotclVer 0 UNODE 010699 HSDPA This parameter is modified based on the actual protocol
B WRFD- +MIMO version of the NodeB when the NodeB protocol version
MOD 010698 HSPA+ upgrade, otherwise it will cause features supported by
UNODE Uplink the new protocol version unavailable.
WRFD-
B 11.5Mbi GUI Value Range: R99, R4, R5, R6, R7, R8, R9
010651
t/s per Unit: None
WRFD- User
010652 Actual Value Range: R99, R4, R5, R6, R7, R8, R9
HSDPA
WRFD- Default Value: R9
over Iur
010693
SRB
WRFD- over
010695 HSDPA
WRFD- DL
010694 64QAM
WRFD- +MIMO
010697 UL
WRFD- Layer 2
010696 Improve
ment
WRFD-
010686 UL
16QAM
WRFD-
140203 E-
DPCCH
WRFD- Boostin
020126 g
WRFD- DC-
010703 HSDPA
WRFD- CPC -
010702 DTX /
WRFD- DRX
010689 HSPA+
WRFD- Uplink
010101 23 Mbit/
s per
WRFD-
User
010687
Mobility
WRFD-
Between
010685
UMTS
WRFD- and LTE
010683 Phase 1
WRFD- HSPA+
010680 Downlin
WRFD- k
010681 84Mbit/
WRFD- s per
010618 User
WRFD- Enhance
0106140 d DRX
3 HSPA+
WRFD- Downlin
010636 k
42Mbps
WRFD-
per User
010635
3GPP
R9
Specific
ations
CPC -
HS-
SCCH
less
operatio
n
Downlin
k
Enhance
d L2
Downlin
k
64QAM
HSPA+
Downlin
k
28Mbps
per User
HSPA+
Downlin
k
21Mbps
per User
IMS
Signalin
g over
HSPA
HSUPA
2ms TTI
SRB
over
HSUPA
HSUPA
over Iur
TRFX BSC690 ADD WRFD- HSDPA Meaning: Traffic index. ATM traffic record indexes are
0 ATMTR 010610 Introduc used by the upper layers of the ATM layer. The upper
F WRFD- tion layers consist of the SAAL link, AAL2 path, and IPoA
MOD 050305 Package PVC. Each ATM traffic record is uniquely numbered
ATMTR UBR+ within a RNC by using an ATM traffic record index. An
WRFD- ATM traffic record index ranges from 100 to 1999 (1 to
F 050301 ATM
QoS 99 are reserved for internal use). The numbering is not
RMV WRFD- necessarily consecutive. Specify different number
ATMTR Class
010697 ranges for different interfaces. For example, specify the
F ATM range of 100 to 199 for ATM traffic record indexes over
Transmi Iub, the range of 200 to 299 for ATM traffic record
ssion indexes over Iur, the range of 300 to 399 for ATM traffic
Introduc record indexes over Iu-CS, and the range of 400 to 499
tion for ATM traffic record indexes over Iu-PS. Specify
Package different ranges of ATM traffic record indexes for
E- different links over an interface. For example, over the
DPCCH Iub interface, specify the range of 100 to 149 for ATM
Boostin traffic record indexes of SAAL links, the range of 150
g to 179 for ATM traffic record indexes of AAL2 paths,
and the range of 180 to 189 for ATM traffic record
indexes of IPoA PVCs.
GUI Value Range: 100~1999
Unit: None
Actual Value Range: 100~1999
Default Value: None
TRFX BSC691 ADD WRFD- HSDPA Meaning: Traffic index. ATM traffic record indexes are
0 ATMTR 010610 Introduc used by the upper layers of the ATM layer. The upper
F WRFD- tion layers consist of the SAAL link, AAL2 path, and IPoA
MOD 010697 Package PVC. Each ATM traffic record is uniquely numbered
ATMTR E- within a RNC by using an ATM traffic record index. An
F DPCCH ATM traffic record index ranges from 100 to 1999 (1 to
Boostin 99 are reserved for internal use). The numbering is not
RMV necessarily consecutive. Specify different number
ATMTR g
ranges for different interfaces. For example, specify the
F range of 100 to 199 for ATM traffic record indexes over
Iub, the range of 200 to 299 for ATM traffic record
indexes over Iur, and the range of 300 to 399 for ATM
traffic record indexes over Iu-CS. Specify different
ranges of ATM traffic record indexes for different links
over an interface. For example, over the Iub interface,
specify the range of 100 to 149 for ATM traffic record
indexes of SAAL links, the range of 150 to 179 for ATM
traffic record indexes of AAL2 paths, and the range of
180 to 189 for ATM traffic record indexes of IPoA
PVCs.
GUI Value Range: 100~1999
Unit: None
Actual Value Range: 100~1999
Default Value: None
AAL2P BSC690 ADD WRFD- Dedicate Meaning: Service type of carried over the PATH. For
ATHT 0 AAL2P 0213050 d Iub R99, only the R99 service can be carried. For HSPA,
ATH 1 Transmi only the HSPA service can be carried. For SHARE, R99
MOD WRFD- ssion and HSPA services can be carried at the same time.
AAL2P 0503010 Control GUI Value Range: R99(R99), HSPA(HSPA), SHARE
ATH 4 Dynami (SHARE)
c AAL2 Unit: None
Connect
ions in Actual Value Range: R99, HSPA, SHARE
Iub/ Default Value: None
IuCS/Iur
Interface
AAL2P BSC691 ADD WRFD- Dedicate Meaning: Service type of carried over the PATH. For
ATHT 0 AAL2P 0213050 d Iub R99, only the R99 service can be carried. For HSPA,
ATH 1 Transmi only the HSPA service can be carried. For SHARE, R99
MOD WRFD- ssion and HSPA services can be carried at the same time.
AAL2P 0503010 Control GUI Value Range: R99(R99), HSPA(HSPA), SHARE
ATH 4 Dynami (SHARE)
c AAL2 Unit: None
Connect
ions in Actual Value Range: R99, HSPA, SHARE
Iub/ Default Value: None
IuCS/Iur
Interface
PATHT BSC690 ADD WRFD- One Meaning: This parameter specifies the type of an IP
0 IPPATH 020111 Tunnel path. It indicates the priority of the user plane data that
WRFD- IP is carried on the IP path. The mapping between the
050402 Transmi priority of the user plane data and IP path is configured
ssion through the "ADD TRMMAP" command. An IP path is
WRFD- of either the QoS type or the non-QoS type. For
050403 Introduc
tion on example, the IP paths used to carry BE data, AF data,
WRFD- Iub and EF data are all of the non-QoS type. Different data
050404 Interface can share the bandwidth of a QoS-type IP path. The
WRFD- bandwidth of a non-QoS type IP path, however, cannot
Hybrid be shared. IP path in hybrid IP transmission can be
050409 Iub IP further categorized into high-priority IP path and low-
Transmi priority IP path (identified as LQ_xx). When the bearing
ssion type of the physical port is PPP or MP, the IP path is
ATM/IP recommended to be configured as a high-priority path.
Dual When the physical port is an Ethernet port, the IP path
Stack is recommended to be configured as a low-priority path.
Node B For the non-QoS type IP path, the priority of EF data is
IP higher than that of AF data, which in turn is higher than
Transmi that of BE data. The actual priority of user plane data,
ssion however, is set through the "SET PHBMAP" command.
Introduc GUI Value Range: BE(BE), AF11(AF11), AF12
tion on (AF12), AF13(AF13), AF21(AF21), AF22(AF22),
Iu AF23(AF23), AF31(AF31), AF32(AF32), AF33
Interface (AF33), AF41(AF41), AF42(AF42), AF43(AF43), EF
(EF), QoS(QoS), LQ_BE(LQ_BE), LQ_AF11
(LQ_AF11), LQ_AF12(LQ_AF12), LQ_AF13
(LQ_AF13), LQ_AF21(LQ_AF21), LQ_AF22
(LQ_AF22), LQ_AF23(LQ_AF23), LQ_AF31
(LQ_AF31), LQ_AF32(LQ_AF32), LQ_AF33
(LQ_AF33), LQ_AF41(LQ_AF41), LQ_AF42
(LQ_AF42), LQ_AF43(LQ_AF43), LQ_EF(LQ_EF),
LQ_QOS(LQ_QOS)
Unit: None
Actual Value Range: QoS, BE, AF11, AF12, AF13,
AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42,
AF43, EF, LQ_QOS, LQ_BE, LQ_AF11, LQ_AF12,
LQ_AF13, LQ_AF21, LQ_AF22, LQ_AF23,
LQ_AF31, LQ_AF32, LQ_AF33, LQ_AF41,
LQ_AF42, LQ_AF43, LQ_EF
Default Value: None
CellId BSC690 ACT None None Meaning: The logical cell ID uniquely identifies a cell
0 UCELL in a radio network. The logical cell ID is configured at
HSDPA the RNC. The RNC sends the cell ID to the base station
ADD during a cell setup procedure. The mapping between
UCELL logical cell IDs and local cell IDs are configured at the
HSDPA RNC. The RNC supports a maximum of 5100 logical
cells. Logical cells are uniquely but not necessarily
DEA consecutively numbered within a RNC. For example,
UCELL you can set the ID of a logical cell to 0 and that of another
HSDPA logical cell to 2. For clear and easy identification, adhere
MOD to the following numbering principles: Specify different
UCELL number ranges for logical cells in different subracks.
HSDPA For example, you can specify the range of 0 to 899 for
RMV the logical cells in subrack 0 (MPS) and the range of
UCELL 900 to 1799 for the logical cells in subrack 1 (EPS).For
HSDPA detailed information about this parameter, see 3GPP TS
25.401.
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: None
CellId BSC691 ACT None None Meaning: The logical cell ID uniquely identifies a cell
0 UCELL in a radio network. The logical cell ID is configured at
HSDPA the RNC. The RNC sends the cell ID to the base station
ADD during a cell setup procedure. The mapping between
UCELL logical cell IDs and local cell IDs are configured at the
HSDPA RNC. The RNC supports a maximum of 20000 logical
cells. Logical cells are uniquely but not necessarily
DEA consecutively numbered within a RNC. For example,
UCELL you can set the ID of a logical cell to 0 and that of another
HSDPA logical cell to 2. For clear and easy identification, adhere
MOD to the following numbering principles: Specify different
UCELL number ranges for logical cells in different subracks.
HSDPA For example, you can specify the range of 0 to 899 for
RMV the logical cells in subrack 0 (MPS) and the range of
UCELL 900 to 1799 for the logical cells in subrack 1 (EPS).For
HSDPA detailed information about this parameter, see 3GPP TS
25.401. This parameter is set by "ADD UCELLSETUP"
GUI Value Range: 0~65535
Unit: None
Actual Value Range: 0~65535
Default Value: None
ST BSC690 ADD WRFD- HSDPA Meaning: Service type of the ATM. When traffic index
0 ATMTR 010610 Introduc is used by the SAAL, IPoA PVC, VPCLCX link, or
F WRFD- tion AAL2 path of the AOUc/UOIc board, the service type
050305 Package UBR and UBR_PLUS must be configured with the
UBR+ PCR.
WRFD-
050301 ATM GUI Value Range: UBR_PLUS, UBR, NRTVBR,
QoS RTVBR, CBR
WRFD- Class
010697 Unit: None
ATM Actual Value Range: UBR_PLUS, UBR, NRTVBR,
Transmi RTVBR, CBR
ssion
Introduc Default Value: None
tion
Package
E-
DPCCH
Boostin
g
ST BSC691 ADD WRFD- HSDPA Meaning: Service type of the ATM. When traffic index
0 ATMTR 010610 Introduc is used by the SAAL, IPoA PVC, or AAL2 path of the
F WRFD- tion AOUc/UOIc board, the service type UBR and
010697 Package UBR_PLUS must be configured with the PCR.
E- GUI Value Range: UBR_PLUS, UBR, NRTVBR,
DPCCH RTVBR, CBR
Boostin Unit: None
g
Actual Value Range: UBR, CBR, RTVBR, NRTVBR,
UBR_PLUS
Default Value: None
PCR BSC690 ADD WRFD- HSDPA Meaning: Peak rate of the ATM traffic. When the ATM
0 ATMTR 010610 Introduc traffic record indexes corresponding to the service type
F WRFD- tion UBR, RTVBR or NRTVBR are used by AOUa, AEUa
050305 Package or UOIa(ATM), the peak cell rate (PCR), if configured,
UBR+ must be lower than 60000 KBIT/S or 141510 CELL/S.
WRFD-
010697 ATM GUI Value Range: 30~353207
QoS Unit: None
WRFD- Class
050301 Actual Value Range: 30~353207
E-
WRFD- DPCCH Default Value: None
0503010 Boostin
7 g
ATM
Transmi
ssion
Introduc
tion
Package
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
PCR BSC691 ADD WRFD- HSDPA Meaning: Peak rate of the ATM traffic.
0 ATMTR 010610 Introduc GUI Value Range: 30~353207
F WRFD- tion
Package Unit: None
050305
UBR+ Actual Value Range: 30~353207
WRFD-
010697 ATM Default Value: None
QoS
WRFD- Class
050301
E-
WRFD- DPCCH
0503010 Boostin
7 g
ATM
Transmi
ssion
Introduc
tion
Package
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
MCR BSC690 ADD WRFD- HSDPA Meaning: Minimum guarantee rate of the ATM
0 ATMTR 010610 Introduc traffic.The "Minimum cell rate" of the AOUc or UOIc
F WRFD- tion board cannot be greater than 13.8 Mbit/s.
050305 Package GUI Value Range: 30~70754
WRFD- UBR+ Unit: None
010697 ATM
QoS Actual Value Range: 30~70754
WRFD- Class Default Value: None
050301
E-
WRFD- DPCCH
0503010 Boostin
7 g
ATM
Transmi
ssion
Introduc
tion
Package
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
MCR BSC691 ADD WRFD- HSDPA Meaning: Minimum guarantee rate of the ATM
0 ATMTR 010610 Introduc traffic.The "Minimum cell rate" of the AOUc or UOIc
F WRFD- tion board cannot be greater than 13.8 Mbit/s.
050305 Package GUI Value Range: 30~70754
WRFD- UBR+ Unit: None
010697 ATM
QoS Actual Value Range: 30~70754
WRFD- Class Default Value: None
050301
E-
WRFD- DPCCH
0503010 Boostin
7 g
ATM
Transmi
ssion
Introduc
tion
Package
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
ANI BSC690 ADD WRFD- Hybrid Meaning: Uniquely identifies an adjacent node.
0 AAL2P 050403 Iub IP Adjacent nodes are uniquely but not necessarily
ATH WRFD- Transmi consecutively numbered within RNC.
BLK 050404 ssion GUI Value Range: 0~65534
AAL2P WRFD- ATM/IP Unit: None
ATH 0213050 Dual
Stack Actual Value Range: 0~65534
MOD 1
AAL2P Node B Default Value: None
WRFD-
ATH 0503010 Dedicate
RMV 4 d Iub
AAL2P Transmi
WRFD- ssion
ATH 140207 Control
UBL WRFD-
AAL2P Dynami
140208 c AAL2
ATH
Connect
ions in
Iub/
IuCS/Iur
Interface
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC
Iub
Transmi
ssion
Resourc
e Pool in
RNC
ANI BSC691 ADD WRFD- Iu/Iur IP Meaning: Uniquely identifies an adjacent node.
0 AAL2P 150244 Transmi Adjacent nodes are uniquely but not necessarily
ATH WRFD- ssion consecutively numbered within RNC.
BLK 0503010 Based GUI Value Range: 0~65534
AAL2P 4 on
Dynami Unit: None
ATH WRFD- c Load Actual Value Range: 0~65534
MOD 150243 Balance
AAL2P Default Value: None
ATH Dynami
c AAL2
RMV Connect
AAL2P ions in
ATH Iub/
UBL IuCS/Iur
AAL2P Interface
ATH Iub IP
Transmi
ssion
Based
on
Dynami
c Load
Balance
PATHI BSC690 ADD WRFD- Dynami Meaning: ID of one AAL2 path between two AAL2
D 0 AAL2P 0503010 c AAL2 nodes. The PATHID of the same AAL2 path configured
ATH 4 Connect between two AAL2 nodes must be the same. The value
BLK WRFD- ions in should not be equal to 0.
AAL2P 050404 Iub/ GUI Value Range: 1~4294967295
ATH IuCS/Iur
WRFD- Interface Unit: None
MOD 0213050 Actual Value Range: 1~4294967295
1 ATM/IP
AAL2P
Dual Default Value: None
ATH
Stack
RMV Node B
AAL2P
Dedicate
ATH
d Iub
UBL Transmi
AAL2P ssion
ATH Control
PATHI BSC691 ADD WRFD- Dynami Meaning: ID of one AAL2 path between two AAL2
D 0 AAL2P 0503010 c AAL2 nodes. The PATHID of the same AAL2 path configured
ATH 4 Connect between two AAL2 nodes must be the same. The value
BLK WRFD- ions in should not be equal to 0.
AAL2P 050404 Iub/ GUI Value Range: 1~4294967295
ATH IuCS/Iur
WRFD- Interface Unit: None
MOD 0213050 Actual Value Range: 1~4294967295
1 ATM/IP
AAL2P
Dual Default Value: None
ATH
Stack
RMV Node B
AAL2P
Dedicate
ATH
d Iub
UBL Transmi
AAL2P ssion
ATH Control
CARRY BSC690 ADD WRFD- Dedicate Meaning: Lower layer link type of bearing the Path.
T 0 AAL2P 0213050 d Iub UNI: see"ADD UNILNK"; IMA: see"ADD
ATH 1 Transmi IMALNK"; FRAATM: see"ADD FRALNK"; NCOPT:
MOD WRFD- ssion see"LST OPT"; ATMLOGICPORT: see"ADD
AAL2P 0503010 Control ATMLOGICPORT"; NULL: used when testing.
ATH 4 Dynami GUI Value Range: UNI(UNI Link), IMA(IMA Group),
WRFD- c AAL2 FRAATM(FRAATM Link), NCOPT(Optical Port),
150213 Connect ATMLOGICPORT(ATM Logical Port), NULL
ions in (NULL)
Iub/ Unit: None
IuCS/Iur
Interface Actual Value Range: UNI, IMA, FRAATM, NCOPT,
ATMLOGICPORT, NULL
MOCN
Indepen Default Value: None
dent Iub
Transmi
ssion
Resourc
e
Allocati
on
CARRY BSC691 ADD WRFD- Dedicate Meaning: Lower layer link type of bearing the Path.
T 0 AAL2P 0213050 d Iub UNI: see"ADD UNILNK"; IMA: see"ADD
ATH 1 Transmi IMALNK"; FRAATM: see"ADD FRALNK"; NCOPT:
MOD WRFD- ssion see"LST OPT"; ATMLOGICPORT: see"ADD
AAL2P 0503010 Control ATMLOGICPORT"; NULL: used when testing.
ATH 4 Dynami GUI Value Range: UNI(UNI Link), IMA(IMA Group),
WRFD- c AAL2 FRAATM(FRAATM Link), NCOPT(Optical Port),
150213 Connect ATMLOGICPORT(ATM Logical Port), NULL
ions in (NULL)
Iub/ Unit: None
IuCS/Iur
Interface Actual Value Range: UNI, IMA, FRAATM, NCOPT,
ATMLOGICPORT, NULL
MOCN
Indepen Default Value: None
dent Iub
Transmi
ssion
Resourc
e
Allocati
on
CARRY BSC690 ADD WRFD- Dedicate Meaning: Subrack number of bearing the AAL2 path.
F 0 AAL2P 0213050 d Iub GUI Value Range: 0~11
ATH 1 Transmi
ssion Unit: None
MOD WRFD-
AAL2P 0503010 Control Actual Value Range: 0~11
ATH 4 Dynami Default Value: None
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
CARRY BSC691 ADD WRFD- Dedicate Meaning: Subrack number of bearing the AAL2 path.
F 0 AAL2P 0213050 d Iub GUI Value Range: 0~11
ATH 1 Transmi
ssion Unit: None
MOD WRFD-
AAL2P 0503010 Control Actual Value Range: 0~11
ATH 4 Dynami Default Value: None
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
CARRY BSC690 ADD WRFD- Dedicate Meaning: Number of the slot bearing the AAL2 link.
SN 0 AAL2P 0213050 d Iub GUI Value Range: 0~5;8~27
ATH 1 Transmi
ssion Unit: None
MOD WRFD-
AAL2P 0503010 Control Actual Value Range: 0~5, 8~27
ATH 4 Dynami Default Value: None
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
CARRY BSC691 ADD WRFD- Dedicate Meaning: Number of the slot bearing the AAL2 link.
SN 0 AAL2P 0213050 d Iub GUI Value Range: 0~27
ATH 1 Transmi
ssion Unit: None
MOD WRFD-
AAL2P 0503010 Control Actual Value Range: 0~27
ATH 4 Dynami Default Value: None
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
TXTRF BSC690 ADD WRFD- Overboo Meaning: TX traffic record index of the AAL2 Path on
X 0 AAL2P 050405 king on the out RNC port (ATM layer PVC traffic). The traffic
ATH WRFD- ATM index is configured in the ATM traffic table (see "LST
MOD 050406 Transmi ATMTRF").
AAL2P ssion GUI Value Range: 100~1999
WRFD-
ATH 0213050 ATM Unit: None
1 QoS
Introduc Actual Value Range: 100~1999
WRFD- tion on Default Value: None
0503010 Hub
4 Node B
WRFD- (Overbo
0503010 oking on
6 Hub
WRFD- Node B
0503010 Transmi
7 ssion)
Dedicate
d Iub
Transmi
ssion
Control
Dynami
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Call
Admissi
on
Based
on Used
AAL2
Path
Bandwi
dth
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
TXTRF BSC691 ADD WRFD- Overboo Meaning: TX traffic record index of the AAL2 Path on
X 0 AAL2P 050405 king on the out RNC port (ATM layer PVC traffic). The traffic
ATH WRFD- ATM index is configured in the ATM traffic table (see "LST
MOD 050406 Transmi ATMTRF").
AAL2P ssion GUI Value Range: 100~1999
WRFD-
ATH 0213050 ATM Unit: None
1 QoS
Introduc Actual Value Range: 100~1999
WRFD- tion on Default Value: None
0503010 Hub
4 Node B
WRFD- (Overbo
0503010 oking on
6 Hub
WRFD- Node B
0503010 Transmi
7 ssion)
Dedicate
d Iub
Transmi
ssion
Control
Dynami
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Call
Admissi
on
Based
on Used
AAL2
Path
Bandwi
dth
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
RXTRF BSC690 ADD WRFD- Overboo Meaning: RX traffic record index of the AAL2 Path on
X 0 AAL2P 050405 king on the out RNC port (ATM layer PVC traffic). The traffic
ATH WRFD- ATM index is configured in the ATM traffic table (see "LST
MOD 050406 Transmi ATMTRF").
AAL2P ssion GUI Value Range: 100~1999
WRFD-
ATH 0213050 ATM Unit: None
1 QoS
Introduc Actual Value Range: 100~1999
WRFD- tion on Default Value: None
0503010 Hub
4 Node B
WRFD- (Overbo
0503010 oking on
6 Hub
WRFD- Node B
0503010 Transmi
7 ssion)
Dedicate
d Iub
Transmi
ssion
Control
Dynami
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Call
Admissi
on
Based
on Used
AAL2
Path
Bandwi
dth
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
RXTRF BSC691 ADD WRFD- Overboo Meaning: RX traffic record index of the AAL2 Path on
X 0 AAL2P 050405 king on the out RNC port (ATM layer PVC traffic). The traffic
ATH WRFD- ATM index is configured in the ATM traffic table (see "LST
MOD 050406 Transmi ATMTRF").
AAL2P ssion GUI Value Range: 100~1999
WRFD-
ATH 0213050 ATM Unit: None
1 QoS
Introduc Actual Value Range: 100~1999
WRFD- tion on Default Value: None
0503010 Hub
4 Node B
WRFD- (Overbo
0503010 oking on
6 Hub
WRFD- Node B
0503010 Transmi
7 ssion)
Dedicate
d Iub
Transmi
ssion
Control
Dynami
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Call
Admissi
on
Based
on Used
AAL2
Path
Bandwi
dth
CBR, rt-
VBR,
nrt-
VBR,
UBR
ATM
QoS
Classes
NT BTS390 ADD WRFD- Dynami Meaning: Indicates the type of AAL2 path. If the local
0, AAL2P 0503010 c AAL2 end node is selected, the AAL2 path is used by local
BTS390 ATH 4 Connect services. If the switching node is selected, the AAL2
0 DSP ions in path is used to connect to the controller through the
WCDM AAL2P Iub/ HUB BS. If the adjacent node is selected, the AAL2 path
A ATH IuCS/Iur is used to connect to the lower-level BS through the
Interface HUB BS.
MOD
AAL2P GUI Value Range: LOCAL(End Node), HUB
ATH (Switching Node), ADJNODE(Adjacent Node)
PATHI BTS390 ADD WRFD- Dynami Meaning: Indicates the number of the AAL2 path.
D 0, AAL2P 0503010 c AAL2 GUI Value Range: 1~4294967295
BTS390 ATH 4 Connect
0 ions in Unit: None
DSP
WCDM AAL2P Iub/ Actual Value Range: 1~4294967295
A ATH IuCS/Iur Default Value: None
Interface
MOD
AAL2P
ATH
RMV
AAL2P
ATH
LST
AAL2P
ATH
SN BTS390 ADD None None Meaning: Indicates the number of the slot where the
0, AAL2P AAL2 path is located.
BTS390 ATH GUI Value Range: 0~7
0 LST
WCDM Unit: None
AAL2P
A ATH Actual Value Range: 0~7
Default Value: None
SBT BTS390 ADD None None Meaning: Indicates the type of sub-board on the board
0, AAL2P where the AAL2 path is established.
BTS390 ATH GUI Value Range: BASE_BOARD(Base Board),
0 LST UNCHANNELLED_COVERBOARD(Unchannelled
WCDM AAL2P Cover Board), E1_COVERBOARD(E1 Cover Board),
A ATH BACK_BOARD(Back Board)
Unit: None
Actual Value Range: BASE_BOARD,
UNCHANNELLED_COVERBOARD,
E1_COVERBOARD, BACK_BOARD
Default Value: None
PT BTS390 ADD None None Meaning: Indicates the type of port on which the AAL2
0, AAL2P path is carried.
BTS390 ATH GUI Value Range: IMA(IMA Group), UNI(UNI Link),
0 LST STM1(STM1), FRAATM(FRAATM Link)
WCDM AAL2P
A Unit: None
ATH
Actual Value Range: IMA, UNI, STM1, FRAATM
Default Value: None
JNRSC BTS390 ADD WRFD- Transmi Meaning: Indicates whether the AAL2 path joins a
GRP 0, AAL2P 0213040 ssion transmission resource group.
BTS390 ATH 6 Recours GUI Value Range: DISABLE(Disable), ENABLE
0 LST e (Enable)
WCDM AAL2P Sharing
A on Iub/ Unit: None
ATH
Iur Actual Value Range: DISABLE, ENABLE
Interface Default Value: DISABLE(Disable)
VPI BTS390 ADD WRFD- ATM Meaning: Indicates the Virtual Path Identifier (VPI) of
0, AAL2P 0503010 over the AAL2 path.
BTS390 ATH 1 E1T1 on GUI Value Range: 0~255
0 LST WRFD- Iub
WCDM Interface Unit: None
AAL2P 0503010
A ATH 3 ATM Actual Value Range: 0~255
over Default Value: None
Non-
channeli
zed
STM-1/
OC-3c
on Iub/
Iu/Iur
Interface
VCI BTS390 ADD WRFD- ATM Meaning: Indicates the Virtual Channel Identifier (VCI)
0, AAL2P 0503010 over of the AAL2 path.
BTS390 ATH 1 E1T1 on GUI Value Range: 32~511
0 LST WRFD- Iub
WCDM Interface Unit: None
AAL2P 0503010
A ATH 3 ATM Actual Value Range: 32~511
over Default Value: None
Non-
channeli
zed
STM-1/
OC-3c
on Iub/
Iu/Iur
Interface
RU BTS390 ADD WRFD- ATM Meaning: Indicates the unit of the Peak Cell Rate (PCR),
0, AAL2P 0503010 over Minimum Cell Rate (MCR), Sustainable Cell Rate
BTS390 ATH 1 E1T1 on (SCR), and Receive Cell Rate (RCR). 1 cell/s is equal
0 MOD WRFD- Iub to 0.424 kbit/s. If the rate is converted from cell/s to kbit/
WCDM AAL2P 0503010 Interface s, the result value must be rounded down to the nearest
A ATH 3 ATM integer. For example, 73 cell/s is converted to 30 kbit/
over s.
LST WRFD-
AAL2P 0503010 Non- GUI Value Range: KBPS(Kbit/s), CELL/S(cell/s)
ATH 6 channeli Unit: None
zed
STM-1/ Actual Value Range: KBPS, CELL/S
OC-3c Default Value: KBPS(Kbit/s)
on Iub/
Iu/Iur
Interface
Call
Admissi
on
Based
on Used
AAL2
Path
Bandwi
dth
ST BTS390 ADD WRFD- CBR, rt- Meaning: Indicates the type of the service carried on the
0, AAL2P 0503010 VBR, AAL2 path. In flow control, services carried by an
BTS390 ATH 7 nrt- AAL2 path are classified into five categories: the
0 MOD WRFD- VBR, Constant Bit Rate (CBR) service, Real-Time Variable
WCDM AAL2P 050305 UBR Bit Rate (RTVBR) service, Non-Real-Time Variable
A ATH ATM Bit Rate (NRTVBR) service, Unspecified Bit Rate Plus
QoS (UBR+) service, and Unspecified Bit Rate (UBR)
LST Classes service.
AAL2P
ATH UBR GUI Value Range: CBR(CBR), RTVBR(RTVBR),
+ATM NRTVBR(NRTVBR), UBR+(UBR+), UBR(UBR)
QoS Unit: None
Class
Actual Value Range: CBR, RTVBR, NRTVBR, UBR
+, UBR
Default Value: RTVBR(RTVBR)
PCR BTS390 ADD WRFD- Call Meaning: Indicates the Peak Cell Rate (PCR) of the
0, AAL2P 0503010 Admissi AAL2 path, which is the maximum cell burst rate
BTS390 ATH 6 on supported by the AAL2 path. The value of this
0 MOD Based parameter is subject to the actual network. Setting the
WCDM AAL2P on Used parameter to an improper value affects the service
A ATH AAL2 quality.
Path GUI Value Range: 30~49529
LST Bandwi
AAL2P dth Unit: None
ATH Actual Value Range: 30~49529
Default Value: None
SCR BTS390 ADD WRFD- CBR, rt- Meaning: Indicates the Sustainable Cell Rate (SCR) of
0, AAL2P 0503010 VBR, the AAL2 path. The value of this parameter is subject
BTS390 ATH 7 nrt- to the actual network. Setting the parameter to an
0 MOD WRFD- VBR, improper value affects the service quality. The SCR
WCDM AAL2P 0503010 UBR value determines the average rate at which cells are sent
A ATH 1 ATM over a Variable Bit Rate (VBR) connection.
QoS GUI Value Range: 30~49526
LST Classes
AAL2P Unit: None
ATH ATM
over Actual Value Range: 30~49526
E1T1 on Default Value: None
Iub
Interface
RCR BTS390 ADD WRFD- HSDPA Meaning: Indicates the rate at which cells are received.
0, AAL2P 0106101 Flow This parameter must be set to be consistent with the TX
BTS390 ATH 0 Control bandwidth at the controller. Inaccurate RX bandwidth
0 MOD in the flow control algorithm affects flow control.
WCDM AAL2P GUI Value Range: 30~129717
A ATH
Unit: None
LST
Actual Value Range: 30~129717
AAL2P
ATH Default Value: None
ANI BSC690 ADD WRFD- Hybrid Meaning: Uniquely identifies an adjacent node.
0 IPPATH 050403 Iub IP Adjacent nodes are uniquely but not necessarily
BLK WRFD- Transmi consecutively numbered within RNC.
IPPATH 050404 ssion GUI Value Range: 0~65534
MOD WRFD- ATM/IP Unit: None
IPPATH 0213050 Dual
Stack Actual Value Range: 0~65534
RMV 1
Node B Default Value: None
IPPATH WRFD-
0503010 Dedicate
UBL d Iub
IPPATH 4
Transmi
WRFD- ssion
140207 Control
WRFD- Dynami
140208 c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC
Iub
Transmi
ssion
Resourc
e Pool in
RNC
ITFT BSC690 ADD WRFD- Overboo Meaning: Type of the adjacent node.
0 IPPATH 050408 king on GUI Value Range: IUB(Iub Interface), IUR(Iur
MOD WRFD- IP Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS
IPPATH 0213050 Transmi Interface)
1 ssion
Unit: None
WRFD- Dedicate
d Iub Actual Value Range: IUB, IUR, IUCS, IUPS
050403
Transmi Default Value: None
WRFD- ssion
050404 Control
WRFD- Hybrid
050424 Iub IP
Transmi
ssion
ATM/IP
Dual
Stack
Node B
Traffic
Priority
Mappin
g onto
Transmi
ssion
Resourc
es
TRANS BSC690 ADD WRFD- Overboo Meaning: Transport type of the adjacent node to which
T 0 IPPATH 050408 king on the path belongs. This parameter is valid only when
WRFD- IP "Interface Type" is set to "IUB".
050402 Transmi GUI Value Range: IP(IP), HYBRID_IP(HYBRID IP)
ssion
Unit: None
IP
Transmi Actual Value Range: IP, HYBRID_IP
ssion Default Value: None
Introduc
tion on
Iub
Interface
IPADD BSC690 ADD WRFD- IP Meaning: Local IP address of an IP path. The local IP
R 0 IPPATH 050402 Transmi address must be the configured IP address (including
WRFD- ssion the IP address and port address of the interface board).
050403 Introduc GUI Value Range: Valid IP Address
tion on
WRFD- Iub Unit: None
050404 Interface Actual Value Range: Valid IP Address
WRFD- Hybrid Default Value: None
150211 Iub IP
MRFD- Transmi
211502 ssion
WRFD- ATM/IP
050409 Dual
MRFD- Stack
211501 Node B
MRFD- RNC in
211504 Pool
Load
Sharing
IP-
Based
BSC and
RNC
Co-
Transmi
ssion on
MBSC
Side
IP
Transmi
ssion
Introduc
tion on
Iu
Interface
IP-
Based
Multi-
mode
Co-
Transmi
ssion on
BS side
(GBTS)
TDM-
Based
Multi-
mode
Co-
Transmi
ssion via
Backpla
ne on BS
side
(GBTS)
PEERIP BSC690 ADD WRFD- IP Meaning: The peer IP address should not be the same
ADDR 0 IPPATH 050402 Transmi as the local address.
WRFD- ssion GUI Value Range: Valid IP Address
050403 Introduc
tion on Unit: None
WRFD- Iub Actual Value Range: Valid IP Address
050404 Interface Default Value: None
WRFD- Hybrid
150211 Iub IP
WRFD- Transmi
050409 ssion
WRFD- ATM/IP
021311 Dual
Stack
Node B
RNC in
Pool
Load
Sharing
IP
Transmi
ssion
Introduc
tion on
Iu
Interface
MOCN
Introduc
tion
Package
PEERM BSC690 ADD WRFD- IP Meaning: Subnet mask of the peer IP.
ASK 0 IPPATH 050409 Transmi GUI Value Range: Valid IP Address
WRFD- ssion
Introduc Unit: None
050402
tion on Actual Value Range: Valid IP Address
WRFD- Iu
050403 Default Value: 255.255.255.255
Interface
WRFD- IP
050404 Transmi
WRFD- ssion
020111 Introduc
tion on
Iub
Interface
Hybrid
Iub IP
Transmi
ssion
ATM/IP
Dual
Stack
Node B
One
Tunnel
HSPAPLUS_MIMO_SUPPORT(MIMO support
indicator), FLEX_MACD_PDU_SIZE_SUPPORT
(flexible MAC-d PDU Size support indicator),
FDPCH_SLOT_FORMAT_SUPPORT(F-DPCH slot
format support indicator),
HSPAPLUS_DL_64QAM_SUPPORT(downlink
64QAM support indicator)
Unit: None
Actual Value Range: DELAY_ACTIVATION_SUP-
PORT, HSDSCH_SUPPORT, FDPCH_SUPPORT,
EDCH_SUPPORT, EDCH_2MS_TTI_SUPPORT,
EDCH_2SF2_AND_2SF4_SUPPORT,
EDCH_2SF2_SUPPORT, EDCH_2SF4_SUPPORT,
EDCH_SF4_SUPPORT, EDCH_SF8_SUPPORT,
EDCH_HARQ_IR_COMBIN_SUPPORT,
EDCH_HARQ_CHASE_COMBIN_SUPPORT,
CPC_DTX_DRX_SUPPORT,
CPC_HS_SCCH_LESS_OPER_SUPPORT,
HSPAPLUS_MIMO_SUPPORT,
FLEX_MACD_PDU_SIZE_SUPPORT,
FDPCH_SLOT_FORMAT_SUPPORT,
HSPAPLUS_DL_64QAM_SUPPORT
Default Value: None
HSPAPLUS_MIMO_SUPPORT(MIMO support
indicator), FLEX_MACD_PDU_SIZE_SUPPORT
(flexible MAC-d PDU Size support indicator),
FDPCH_SLOT_FORMAT_SUPPORT(F-DPCH slot
format support indicator),
HSPAPLUS_DL_64QAM_SUPPORT(downlink
64QAM support indicator)
Unit: None
Actual Value Range: DELAY_ACTIVATION_SUP-
PORT, HSDSCH_SUPPORT, FDPCH_SUPPORT,
EDCH_SUPPORT, EDCH_2MS_TTI_SUPPORT,
EDCH_2SF2_AND_2SF4_SUPPORT,
EDCH_2SF2_SUPPORT, EDCH_2SF4_SUPPORT,
EDCH_SF4_SUPPORT, EDCH_SF8_SUPPORT,
EDCH_HARQ_IR_COMBIN_SUPPORT,
EDCH_HARQ_CHASE_COMBIN_SUPPORT,
CPC_DTX_DRX_SUPPORT,
CPC_HS_SCCH_LESS_OPER_SUPPORT,
HSPAPLUS_MIMO_SUPPORT,
FLEX_MACD_PDU_SIZE_SUPPORT,
FDPCH_SLOT_FORMAT_SUPPORT,
HSPAPLUS_DL_64QAM_SUPPORT
Default Value: None
RetryCa BSC690 SET WRFD- HSUPA Meaning: This parameter specifies which HSPA
pability 0 UFRC 0106140 2ms TTI technologies can be retried by UEs. When the HSPA
3 DC- technologies are selected and currently UE is not using
WRFD- HSDPA them, "RNC" will initiate these HSPA technologies
010699 +MIMO retry for UE.This parameter takes effect only when
services running on the UE are carried over the HSPA
WRFD- Macro- channel.
151209 Micro
GUI Value Range: SRB_OVER_HSDPA,
WRFD- DC-
SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
150207 HSDPA
DL_L2_ENHANCE, DTX_DRX,
WRFD- 4C- HSSCCH_LESS_OPERATION, MIMO_64QAM,
010652 HSDPA DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
WRFD- SRB EDPCCH_BOOSTING, DCMIMO_HSDPA,
010686 over DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
HSDPA DBMIMO_HSDPA, DB_HSDPA
WRFD-
010687 CPC - Unit: None
WRFD- E-
010696 DPCCH
Boostin
WRFD- g
150223
UL
WRFD-
16QAM
010693
DB-
HSDPA
+MIMO
DB-
HSDPA
3C-
HSDPA
SRB
over
HSUPA
DC-
HSDPA
MC-
HSDPA
+MIMO
DL
64QAM
+MIMO
RetryCa BSC691 SET WRFD- HSUPA Meaning: This parameter specifies which HSPA
pability 0 UFRC 0106140 2ms TTI technologies can be retried by UEs. When the HSPA
3 DC- technologies are selected and currently UE is not using
WRFD- HSDPA them, "RNC" will initiate these HSPA technologies
010699 +MIMO retry for UE.This parameter takes effect only when
services running on the UE are carried over the HSPA
WRFD- Macro- channel.
151209 Micro
GUI Value Range: SRB_OVER_HSDPA,
WRFD- DC-
SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
150207 HSDPA
DL_L2_ENHANCE, DTX_DRX,
WRFD- 4C- HSSCCH_LESS_OPERATION, MIMO_64QAM,
010652 HSDPA DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
WRFD- SRB EDPCCH_BOOSTING, DCMIMO_HSDPA,
010686 over DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
HSDPA DBMIMO_HSDPA, DB_HSDPA
WRFD-
010687 CPC - Unit: None
WRFD- E-
010696 DPCCH
Boostin
WRFD- g
150223
UL
WRFD-
16QAM
010693
DB-
HSDPA
+MIMO
DB-
HSDPA
3C-
HSDPA
SRB
over
HSUPA
DC-
HSDPA
MC-
HSDPA
+MIMO
DL
64QAM
+MIMO
SPECUSER_DL_BLER_MEAS_DISABLED_SWIT
CH,
SPECUSER_AGPS_MEAS_DISABLED_SWITCH,
SPECUSER_UE_TX_PWR_MEAS_DISABLED_S
WITCH,
SPECUSER_CELLID_RTT_MEAS_DISABLED_S
WITCH,
FAST_H_SERV_CELL_CHANGE_DISABLED_SW
ITCH, SPECUSER_R6_EFACH_CMP_SWITCH
Default Value: P2F_REDIR_DISABLED_SWITCH:
0,SPECUSER_SRB_OVER_HSDPA_DISABLED_S
WITCH:0,
SPECUSER_CPC_DTX_DRX_DISABLED_SWITC
H:0, SPECUSER_EFACH_DISABLED_SWITCH:0,
SPECUSER_ERACH_DISABLED_SWITCH:
0,SPECUSER_PCH_FACH2EFACH_DISABLED_S
WITCH:0,SPECUSER_INHIBIT_D2P_SWITCH:
0,H_SERV_CELL_CHG_MSG_OPT_DISABLED_S
WITCH:
0,EFACH_ERACH_UE_D2P_DISABLED_SWITCH
:
0,SPECUSER_DL_BLER_MEAS_DISABLED_SWI
TCH:
0,SPECUSER_AGPS_MEAS_DISABLED_SWITCH
:
0,SPECUSER_UE_TX_PWR_MEAS_DISABLED_S
WITCH:
0,SPECUSER_CELLID_RTT_MEAS_DISABLED_S
WITCH:
0,FAST_H_SERV_CELL_CHANGE_DISABLED_S
WITCH:0,SPECUSER_R6_EFACH_CMP_SWITCH:
0
SPECUSER_DL_BLER_MEAS_DISABLED_SWIT
CH,
SPECUSER_AGPS_MEAS_DISABLED_SWITCH,
SPECUSER_UE_TX_PWR_MEAS_DISABLED_S
WITCH,
SPECUSER_CELLID_RTT_MEAS_DISABLED_S
WITCH,
FAST_H_SERV_CELL_CHANGE_DISABLED_SW
ITCH, SPECUSER_R6_EFACH_CMP_SWITCH
Default Value: P2F_REDIR_DISABLED_SWITCH:
0,SPECUSER_SRB_OVER_HSDPA_DISABLED_S
WITCH:0,
SPECUSER_CPC_DTX_DRX_DISABLED_SWITC
H:0, SPECUSER_EFACH_DISABLED_SWITCH:0,
SPECUSER_ERACH_DISABLED_SWITCH:
0,SPECUSER_PCH_FACH2EFACH_DISABLED_S
WITCH:0,SPECUSER_INHIBIT_D2P_SWITCH:
0,H_SERV_CELL_CHG_MSG_OPT_DISABLED_S
WITCH:
0,EFACH_ERACH_UE_D2P_DISABLED_SWITCH
:
0,SPECUSER_DL_BLER_MEAS_DISABLED_SWI
TCH:
0,SPECUSER_AGPS_MEAS_DISABLED_SWITCH
:
0,SPECUSER_UE_TX_PWR_MEAS_DISABLED_S
WITCH:
0,SPECUSER_CELLID_RTT_MEAS_DISABLED_S
WITCH:
0,FAST_H_SERV_CELL_CHANGE_DISABLED_S
WITCH:0,SPECUSER_R6_EFACH_CMP_SWITCH:
0
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
Unit: None
Actual Value Range:
LOAD_IRAT_HO_RNC_FILL_TL,
SEND_IDT_JUDGE_IU_RESET,
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWIT
CH, RNC_CS_QUERY_UE_IMEI_SWITCH,
RNC_PS_QUERY_UE_IMEI_SWITCH,
FACH_DTCH_CONGEST_P2D,
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITC
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,
USRPLN_PRORATION_SHARED_ALO,
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
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,USRPLN_PRORATION_SHARED_ALO:
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
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
Unit: None
Actual Value Range:
LOAD_IRAT_HO_RNC_FILL_TL,
SEND_IDT_JUDGE_IU_RESET,
RNC_RBRECFG_DRD_FAIL_ROLLBACK_SWIT
CH, RNC_CS_QUERY_UE_IMEI_SWITCH,
RNC_PS_QUERY_UE_IMEI_SWITCH,
FACH_DTCH_CONGEST_P2D,
RNC_RBSETUP_DRD_FAIL_ROLLBACK_SWITC
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,
USRPLN_PRORATION_SHARED_ALO,
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
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,USRPLN_PRORATION_SHARED_ALO:
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
Manage CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:
ment This parameter specifies to enable AMR through DRD
DC- two-step procedure function. When SRB is set up on
HSUPA DCH, and "RNC" decides to setup the AMR through
DRD procedure, When the switch is enabled, "RNC"
3C- will execute blind handover to the target cell, and then
HSDPA setup the AMR RBs on the target cell, When the switch
is disabled, "RNC" will setup the AMR RBs on the
target cell directly. 8.
CMP_UU_AMR_SID_MUST_CFG_SWITCH: For
narrowband AMR services, when the switch is on, the
SID frame is always configured; when the switch is not
on, the SID frame is configured on the basis of CN
assignment. 9.
CMP_UU_FDPCH_COMPAT_SWITCH: When the
switch is OFF, if the information element that indicates
the F-DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. In other case, it
means UE does not support F-DPCH. When the switch
is ON, if the information element that indicates the F-
DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. If that information
element does not exist, UE supports F-DPCH when all
the conditions meets: a) the version of UE is Release 6.
b) UE supports HS-PDSCH. 10.
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
When the switch is on, the RAB assignment request and
the subsequent RB setup procedure proceed if the RLC
AM capabilities of the UE fail to meet the minimum
RLC TX/RX window buffer requirement of the RAB to
be setup. When the switch is not on, the RAB
assignment request is rejected. 11.
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH: When this switch is on, the cell individual
offset (CIO) of the best cell is always set to 0 in the
INTRA-FREQUENCY MEASUREMENT
CONTROL messages. Otherwise, the CIO information
of the best cell is not carried in the INTRA-
FREQUENCY MEASUREMENT CONTROL
messages. 12.
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH: When the switch is on, the cell synchronization
information traced by the IOS need to be reported during
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWIT
CH,
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_S
WITCH,
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH, CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH,
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH,
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_RAB_6_CFG_ROHC_SWITCH,
CMP_RAB_7_CFG_ROHC_SWITCH,
CMP_RAB_8_CFG_ROHC_SWITCH,
CMP_RAB_9_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH
Unit: None
Actual Value Range:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH,
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITC
H,
CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
CH, CMP_IUR_SHO_DIVCTRL_SWITCH,
CMP_UU_ADJACENT_FREQ_CM_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_UU_AMR_SID_MUST_CFG_SWITCH,
CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH,
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH,
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWIT
CH,
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_S
WITCH,
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_RAB_6_CFG_ROHC_SWITCH,
CMP_RAB_7_CFG_ROHC_SWITCH,
CMP_RAB_8_CFG_ROHC_SWITCH,
CMP_RAB_9_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH,
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH
Default Value:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH:
0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWIT
CH:
0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SW
ITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:
0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:
0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH
:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:
0,CMP_UU_FDPCH_COMPAT_SWITCH:
0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_
SWITCH:
0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_S
WITCH:
0,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWI
TCH:
0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_
SWITCH:
1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH:
1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_RAB_5_CFG_ROHC_SWITCH:
0,CMP_RAB_6_CFG_ROHC_SWITCH:
0,CMP_RAB_7_CFG_ROHC_SWITCH:
0,CMP_RAB_8_CFG_ROHC_SWITCH:
0,CMP_RAB_9_CFG_ROHC_SWITCH:
0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:
Manage CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:
ment This parameter specifies to enable AMR through DRD
DC- two-step procedure function. When SRB is set up on
HSUPA DCH, and "RNC" decides to setup the AMR through
DRD procedure, When the switch is enabled, "RNC"
3C- will execute blind handover to the target cell, and then
HSDPA setup the AMR RBs on the target cell, When the switch
is disabled, "RNC" will setup the AMR RBs on the
target cell directly. 8.
CMP_UU_AMR_SID_MUST_CFG_SWITCH: For
narrowband AMR services, when the switch is on, the
SID frame is always configured; when the switch is not
on, the SID frame is configured on the basis of CN
assignment. 9.
CMP_UU_FDPCH_COMPAT_SWITCH: When the
switch is OFF, if the information element that indicates
the F-DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. In other case, it
means UE does not support F-DPCH. When the switch
is ON, if the information element that indicates the F-
DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. If that information
element does not exist, UE supports F-DPCH when all
the conditions meets: a) the version of UE is Release 6.
b) UE supports HS-PDSCH. 10.
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
When the switch is on, the RAB assignment request and
the subsequent RB setup procedure proceed if the RLC
AM capabilities of the UE fail to meet the minimum
RLC TX/RX window buffer requirement of the RAB to
be setup. When the switch is not on, the RAB
assignment request is rejected. 11.
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH: When this switch is on, the cell individual
offset (CIO) of the best cell is always set to 0 in the
INTRA-FREQUENCY MEASUREMENT
CONTROL messages. Otherwise, the CIO information
of the best cell is not carried in the INTRA-
FREQUENCY MEASUREMENT CONTROL
messages. 12.
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH: When the switch is on, the cell synchronization
information traced by the IOS need to be reported during
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWIT
CH,
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_S
WITCH,
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH, CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH,
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH,
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_RAB_6_CFG_ROHC_SWITCH,
CMP_RAB_7_CFG_ROHC_SWITCH,
CMP_RAB_8_CFG_ROHC_SWITCH,
CMP_RAB_9_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH
Unit: None
Actual Value Range:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH,
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITC
H,
CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
CH, CMP_IUR_SHO_DIVCTRL_SWITCH,
CMP_UU_ADJACENT_FREQ_CM_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_UU_AMR_SID_MUST_CFG_SWITCH,
CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH,
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH,
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWIT
CH,
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_S
WITCH,
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_RAB_6_CFG_ROHC_SWITCH,
CMP_RAB_7_CFG_ROHC_SWITCH,
CMP_RAB_8_CFG_ROHC_SWITCH,
CMP_RAB_9_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH,
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH
Default Value:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH:
0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWIT
CH:
0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SW
ITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:
0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:
0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH
:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:
0,CMP_UU_FDPCH_COMPAT_SWITCH:
0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_
SWITCH:
0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_S
WITCH:
0,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWI
TCH:
0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_
SWITCH:
1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH:
1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_RAB_5_CFG_ROHC_SWITCH:
0,CMP_RAB_6_CFG_ROHC_SWITCH:
0,CMP_RAB_7_CFG_ROHC_SWITCH:
0,CMP_RAB_8_CFG_ROHC_SWITCH:
0,CMP_RAB_9_CFG_ROHC_SWITCH:
0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:
TAC_F BSC690 ADD WRFD- Termina Meaning: The function of the TAC.If Fast_Dormancy
UNC 0 UIMEIT 160103 l Black is selected, the TAC specifies the UEs that are enabled
AC WRFD- List with the Fast Dormancy feature; if
MOD 020500 Enhance HSDPA_RB_Setup_Cmp_CRC is selected, the TAC
UIMEIT d Fast specifies that the UEs want to establish services on
AC Dorman HSDPA, however, the RNC sets up services on the
cy DCH, and retries on HSDPA later; if Special_User_En-
RMV hance is selected, the TAC specifies the UEs that are
UIMEIT enabled with the Special User Enhance feature.
AC
GUI Value Range: Fast_Dormancy,
HSDPA_RB_Setup_Cmp_CRC, Special_User_En-
hance
Unit: None
Actual Value Range: Fast_Dormancy,
HSDPA_RB_Setup_Cmp_CRC, Special_User_En-
hance
Default Value: None
TAC BSC690 ADD WRFD- Termina Meaning: Type Allocation Code (TAC) is proportion of
0 UIMEIT 160103 l Black the International Mobile Station Equipment Identity
AC WRFD- List (IMEI) and represent the first eight digits of the IMEI.
MOD 020500 Enhance TAC is used to differentiate between the MSs of
UIMEIT d Fast different models. This parameter consists of an eight
AC Dorman digit string. If the string is less than eight digits, the
cy system fills the higher orders with 0s to achieve an eight
RMV digit string.
UIMEIT
AC GUI Value Range: 0~99999999
Unit: None
Actual Value Range: 0~99999999
Default Value: None
TBSize BSC690 ADD WRFD- Transpo Meaning: This parameter specifies the number of bits
0 UTYPS 021000 rt in a TB used by the transport channel. This parameter
RBDYN Channel is an advanced parameter. To modify this parameter,
TF Manage contact Huawei Customer Service Center for technical
RMV ment support.
UTYPS GUI Value Range: 0~4992
RBDYN Unit: bit
TF
Actual Value Range: 0~4992
Default Value: 148
TBSize BSC691 ADD WRFD- Transpo Meaning: This parameter specifies the number of bits
0 UTYPS 021000 rt in a TB used by the transport channel. This parameter
RBDYN Channel is an advanced parameter. To modify this parameter,
TF Manage contact Huawei Customer Service Center for technical
RMV ment support.
UTYPS GUI Value Range: 0~4992
RBDYN Unit: bit
TF
Actual Value Range: 0~4992
Default Value: 148
TTI BSC690 ADD WRFD- Transpo Meaning: This parameter specifies the inter-arrival time
0 UTYPS 021000 rt of TBS. It is equal to the periodicity at which a TBS is
RBSEM Channel transferred by the physical layer on the radio interface.
ISTATI Manage For details of this parameter, see 3GPP TS 25.212. This
CTF ment parameter is an advanced parameter. To modify this
MOD parameter, contact Huawei Customer Service Center for
UTYPS technical support.
RBSEM GUI Value Range: D10, D20, D40, D80
ISTATI Unit: ms
CTF
Actual Value Range: 10, 20, 40, 80
Default Value: D40
TTI BSC691 ADD WRFD- Transpo Meaning: This parameter specifies the inter-arrival time
0 UTYPS 021000 rt of TBS. It is equal to the periodicity at which a TBS is
RBSEM Channel transferred by the physical layer on the radio interface.
ISTATI Manage For details of this parameter, see 3GPP TS 25.212. This
CTF ment parameter is an advanced parameter. To modify this
MOD parameter, contact Huawei Customer Service Center for
UTYPS technical support.
RBSEM GUI Value Range: D10, D20, D40, D80
ISTATI Unit: ms
CTF
Actual Value Range: 10, 20, 40, 80
Default Value: D40
SrbOver BSC691 SET WRFD- SRB Meaning: RSCP threshold for the coverage-based and
HsdpaR 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
scpDow UALIT HSDPA the channel mapped to downlink SRBs in weak
nThd YEVAL coverage areas. If the valid RSCP value of the best cell
UATE is less than or equal to the value of this parameter, the
UE is located in a weak coverage area.
GUI Value Range: -115~-25
Unit: dBm
Actual Value Range: -115~-25
Default Value: -90
SrbOver BSC691 SET WRFD- SRB Meaning: RSCP threshold for the coverage-based and
HsdpaR 0 UCHLQ 010652 over load-based algorithm for dynamic reconfiguration of
scpUpT UALIT HSDPA the channel mapped to downlink SRBs in strong
hd YEVAL coverage areas. If the valid RSCP and Ec/N0 of the best
UATE cell are greater than the corresponding RSCP and Ec/
N0 thresholds for strong coverage areas, the UE is
located in a strong coverage area.
GUI Value Range: -115~-25
Unit: dBm
Actual Value Range: -115~-25
Default Value: -80
SWITC BTS390 ADD WRFD- HSDPA Meaning: Indicates the switch for the DL flow control
H 0, DLFLO 0106101 Flow algorithm. If this parameter is set to
BTS390 WCTRL 0 Control DYNAMIC_BW_SHAPING, flow allocation for
0 PARA HSDPA users is performed according to the delay and
WCDM SET packet loss of the transmission interface board in
A DLFLO STATIC_BW_SHAPING mode. This function requires
WCTRL the network controller using the switch of the 3GPP R6
PARA protocol. Therefore, you are advised to use this function
with the RNC that complies with the 3GPP R6 protocol.
LST If this parameter is set to NO_BW_SHAPING, the BS
DLFLO does not allocate bandwidth according to the
WCTRL configuration and delay of the transmission interface
PARA board. The BS reports the air interface conditions to the
controller, and then the controller allocates bandwidth.
When this parameter is set to NO_BW_SHAPING, the
backpressure function must be enabled on the controller
side. If this parameter is set to
BW_SHAPING_ONOFF_TOGGLE, the BS
automatically selects either DYNAMIC_BW_SHAP-
ING or NO_BW_SHAPING during a flow congestion
detection on a port. That is, DYNAMIC_BW_SHAP-
ING is selected if congestion is detected;
NO_BW_SHAPING is selected if congestion is not
detected for a certain period of time.
GUI Value Range: STATIC_BW_SHAPING
(STATIC_BW_SHAPING), DYNAMIC_BW_SHAP-
ING(DYNAMIC_BW_SHAPING),
NO_BW_SHAPING(NO_BW_SHAPING),
BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)
Unit: None
Actual Value Range: STATIC_BW_SHAPING,
DYNAMIC_BW_SHAPING, NO_BW_SHAPING,
BW_SHAPING_ONOFF_TOGGLE
Default Value: BW_SHAPING_ONOFF_TOGGLE
(BW_SHAPING_ONOFF_TOGGLE)
CME16 BTS390 SET WRFD- DL Meaning: Indicates the 16QAM Switch. The function
QAMS 0, ULOCE 010629 16QAM will be enabled if this parameter is set to OPEN. When
W BTS390 LLMAC Modulat this switch is turned on, the cell throughput improves.
0 HSPAR ion GUI Value Range: OPEN(open), CLOSE(close)
WCDM A
A Unit: None
LST
ULOCE Actual Value Range: OPEN, CLOSE
LLMAC Default Value: OPEN(open)
HSPAR
A
Hsdpcch BSC690 ADD WRFD- HS- Meaning: Whether the HARQ Preamble function is
Preambl 0 UCELL 0106111 DPCCH supported. When a UE supports the HARQ Preamble
eSwitch HSDPA 3 Preambl function, ACK, NACK, CQI, preamble, and postamble
MOD e messages can be carried over the HS-DPCCH. For
UCELL Support details about this parameter, see 3GPP TS 25.214.
HSDPA GUI Value Range: Mode0, Mode1
Unit: None
Actual Value Range: Mode0, Mode1
Default Value: Mode0
Hsdpcch BSC691 ADD WRFD- HS- Meaning: Whether the HARQ Preamble function is
Preambl 0 UCELL 0106111 DPCCH supported. When a UE supports the HARQ Preamble
eSwitch HSDPA 3 Preambl function, ACK, NACK, CQI, preamble, and postamble
MOD e messages can be carried over the HS-DPCCH. For
UCELL Support details about this parameter, see 3GPP TS 25.214.
HSDPA GUI Value Range: Mode0, Mode1
Unit: None
Actual Value Range: Mode0, Mode1
Default Value: Mode0
MaxHsd BSC690 ADD WRFD- 128 Meaning: Maximum number of users supported by the
paUserN 0 UCELL 010654 HSDPA HSDPA channel. The user in this parameter refers to the
um CAC WRFD- Users user with services on the HSDPA channel, regardless of
MOD 0106100 per Cell the number of RABs carried on the HSDPA channel.
UCELL 3 HSDPA Maximum HSDPA user number cannot exceed the
CAC Admissi HSDPA capability of the NodeB product, In practice,
WRFD- the value can be set based on the cell type and the
010653 on
Control richness of the available HSDPA power and code
WRFD- resources.
020101 96
HSDPA GUI Value Range: 0~192
WRFD- Users Unit: None
160208 per Cell Actual Value Range: 0~192
WRFD- Admissi
160209 Default Value: 64
on
WRFD- Control
0106111 160
2 HSPA
Users
per Cell
192
HSPA
Users
per Cell
HSDPA
DRD
MaxHsd BSC691 ADD WRFD- 128 Meaning: Maximum number of users supported by the
paUserN 0 UCELL 010654 HSDPA HSDPA channel. The user in this parameter refers to the
um CAC WRFD- Users user with services on the HSDPA channel, regardless of
MOD 0106100 per Cell the number of RABs carried on the HSDPA channel.
UCELL 3 HSDPA Maximum HSDPA user number cannot exceed the
CAC Admissi HSDPA capability of the NodeB product, In practice,
WRFD- the value can be set based on the cell type and the
010653 on
Control richness of the available HSDPA power and code
WRFD- resources.
020101 96
HSDPA GUI Value Range: 0~192
WRFD- Users Unit: None
160208 per Cell Actual Value Range: 0~192
WRFD- Admissi
160209 Default Value: 64
on
WRFD- Control
0106111 160
2 HSPA
Users
per Cell
192
HSPA
Users
per Cell
HSDPA
DRD
10 Counters
WRFD-010629
LTE: None
UMTS: QPSK
WRFD-010610 Modulation
WRFD-010610
17
LTE: None
UMTS:
WRFD-010611
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
UMTS:
WRFD-010610
LTE: None
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
12 Reference Documents