Professional Documents
Culture Documents
Issue 01
Date 2015-03-25
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.........................................................................................................................................5
3 Basic Principles..............................................................................................................................6
3.1 Overview........................................................................................................................................................................6
3.2 Carrier Attributes............................................................................................................................................................7
3.3 Channel Mapping...........................................................................................................................................................7
3.4 UE Categories.................................................................................................................................................................8
3.5 MAC Entities..................................................................................................................................................................8
3.6 Iub/Uu Interface Evolution...........................................................................................................................................12
4 Technical Description.................................................................................................................14
4.1 Overview......................................................................................................................................................................14
4.2 Activation and Deactivation of the Secondary Carrier.................................................................................................16
4.3 Scheduling....................................................................................................................................................................16
4.4 Radio Bearers...............................................................................................................................................................17
4.5 Mobility Management..................................................................................................................................................18
4.5.1 Measurement Control................................................................................................................................................18
4.5.2 Soft Handover............................................................................................................................................................19
4.5.3 Hard Handover..........................................................................................................................................................23
4.5.4 Handover Between RNCs..........................................................................................................................................24
4.6 Load Control.................................................................................................................................................................24
4.6.1 RAB DRD..................................................................................................................................................................24
4.6.2 CAC...........................................................................................................................................................................25
4.6.3 LDR and OLC...........................................................................................................................................................26
4.6.4 Queuing and Preemption...........................................................................................................................................26
5 Related Features...........................................................................................................................28
6 Network Impact...........................................................................................................................30
7 Engineering Guidelines.............................................................................................................32
7.1 When to Use DC-HSUPA............................................................................................................................................33
7.2 Required Information...................................................................................................................................................33
7.3 Planning........................................................................................................................................................................35
7.4 Deployment..................................................................................................................................................................35
7.4.1 Requirements.............................................................................................................................................................35
7.4.2 Data Preparation........................................................................................................................................................37
7.4.3 Precautions.................................................................................................................................................................38
7.4.4 Activation..................................................................................................................................................................38
7.4.5 Activation Observation..............................................................................................................................................41
7.4.6 Deactivation...............................................................................................................................................................43
7.5 Performance Monitoring...............................................................................................................................................44
7.6 Parameter Optimization................................................................................................................................................45
7.7 Troubleshooting............................................................................................................................................................46
8 Parameters.....................................................................................................................................47
9 Counters......................................................................................................................................138
10 Glossary.....................................................................................................................................145
11 Reference Documents.............................................................................................................146
1.1 Scope
This document describes WRFD-140204 Dual-Carrier High Speed Uplink Packet Access (DC-
HSUPA), including its technical principles, related features, network impact, and engineering
guidelines.
NE Type NE Model
Micro BTS3902E
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.
RAN17.1 01 (2015-03-25)
This issue does not include any changes.
WRFD-14 DC- Y Y Y Y Y
0204 HSUPA
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 feature described in this document is implemented in the same way on macro, micro, and
LampSite NodeBs.But the BTS3902E does not support all new and enhanced features and
functions in RAN17.1. For details, see 1.3 Change History.
2 Overview
In versions earlier than 3GPP Release 8, a UE uses only a single carrier for data transmission.
The use of a single carrier for HSDPA and HSUPA transmission is referred to as SC-HSDPA
and SC-HSUPA in this document.
DC-HSUPA uses two carriers for HSUPA transmission of a UE. Compared with SC-HSUPA,
DC-HSUPA increases the single-user peak rate from 5.76 Mbit/s to 11.5 Mbit/s. When used
with WRFD-010694 UL 16QAM, DC-HSUPA increases the uplink single-user peak rate to 23
Mbit/s.
3 Basic Principles
3.1 Overview
DC-HSUPA allows a UE to transmit data simultaneously on two uplink adjacent carriers with
the same coverage. DC-HSUPA enables a UE to establish an E-DCH transport channel in two
cells, as shown in Figure 3-1.
Carrier attributes, channel mapping, UE categories, MAC entities, and the Iub/Uu interface have
been evolved in 3GPP specifications to work with DC-HSUPA.
The primary and secondary carriers must meet the following conditions:
l The primary and secondary carriers must use adjacent frequencies and belong to the same
NodeB.
l UEs have a respective E-DCH active set for the primary and secondary carriers for soft and
softer handovers on these two carriers.
3.4 UE Categories
Only UEs belonging to E-DCH categories 8 and higher support DC-HSUPA. Table 3-1 lists E-
DCH categories 8 and 9. For details about E-DCH categories, see 3GPP TS 25.306.
NOTE
l When four spreading factors are transmitted in parallel, two codes shall be SF2 and two SF4.
l UEs belonging to E-DCH category 8 do not support uplink 16QAM.
l UEs belonging to E-DCH category 9 support uplink 16QAM.
The MAC-is and MAC-i entities on the UE, NodeB, and RNC sides have been evolved in 3GPP
specifications to support DC-HSUPA. Figure 3-3 shows DC-HSUPA service flows in the
UTRAN.
UE MAC-i/is
Figure 3-4 shows the MAC-i/is architecture on the UE side. The red box marks the HARQ entity
introduced by DC-HSUPA. A MAC-i/is entity has one common TSN entity for both E-DCH
transport channels. However, there is one HARQ entity for each E-DCH transport channel. For
details about the MAC-i/is entity on the UE side, see section "MAC-i/is entity - UE Side" in
3GPP 25.321.
NodeB MAC-i
Figure 3-5 shows the MAC-i architecture on the NodeB side. The red box marks the HARQ
entity introduced by DC-HSUPA.
There is only one MAC-i entity for each DC-HSUPA UE on the NodeB side. Compared with
the MAC-i entity for SC-HSUPA, the MAC-i entity for DC-HSUPA has an HARQ entity for
the HARQ transmission of data packets at the MAC-i layer on the secondary carrier. The two
E-DCH transport channels of a DC-HSUPA UE use their respective HARQ entities. For details
about the MAC-i entity on the UTRAN side, see section "MAC-i entity - UTRAN Side" in 3GPP
25.321.
RNC MAC-is
Figure 3-6 shows the MAC-is architecture on the RNC side. The red lines mark the added MAC-
d flows on the secondary carrier. DC-HSUPA requires that the RNC supports reordering and
disassembly of MAC-d flows from two carriers of a NodeB.
In addition, the length of the TSN field in the MAC-is header is increased from 6 bits to 14 bits
in order to tolerate a larger range of data packet disorder. For details about the MAC-i entity on
the UTRAN side, see section "MAC-i entity - UTRAN Side" in 3GPP 25.321.
Iub Evolution
The NodeB reports cell capability to the RNC using an AUDIT RESPONSE or RESOURCE
STATUS INDICATION message if any of the following occurs: The cell receives an AUDIT
REQUEST message.
If a cell supports DC-HSUPA, the NodeB notifies the RNC of the cell capability using the Cell
Capability Container IE in the Local Cell Information IE.
During radio link establishment, the following messages incorporate new or enhanced IEs to
indicate information about the NodeB transport bearer and secondary carrier:
In addition, the function of exchanging information about the secondary UL frequency has been
added to NodeB Application Part (NBAP) procedures over the Iub interface. This function
allows the controlling radio network controller (CRNC) to exchange information about the
secondary uplink carrier with the NodeB. This function involves two messages:
l SECONDARY UL FREQUENCY REPORT: The CRNC uses this message to inform the
NodeB about the activation status of the secondary uplink carrier of the UE.
l SECONDARY UL FREQUENCY UPDATE INDICATION: The NodeB uses this
message to inform the CRNC about updates to the activation status of the secondary uplink
carrier of the UE.
DC-HSUPA supports E-DCH UL flow multiplexing mode on the user plane of the Iub interface.
In this mode, the NodeB uses one transport bearer to transmit MAC-d flows from both primary
and secondary carriers to the serving radio network controller (SRNC). During uplink radio link
establishment on the secondary carrier, the SRNC notifies the NodeB of the transport bearer
mode. The NodeB transmits MAC-d flows in E-DCH UL DATA FRAME TYPE 2 (MAC-i)
format through the primary and secondary carriers to the SRNC on one transport bearer.
Uu Evolution
The following Uu interface messages incorporate new or enhanced IEs for indicating secondary
DC-HUSPA carrier information, including the channels, radio access bearers (RABs), and
capabilities:
4 Technical Description
4.1 Overview
This section describes how the existing functions evolve to work with DC-HSUPA.
Function Evolution
Activation When DC-HSUPA services are initially set up, the default state of the secondary
and carrier is deactivated.
deactivati When the secondary carrier is deactivated, the UE does not transmit data on the
on secondary carrier. Uplink E-DCH data and control information, as well as
DPCCH data for closed-loop power control are not transmitted on the secondary
carrier. The NodeB also does not send E-DCH scheduling and HARQ
information on the secondary carrier.
For details, see section 4.2 Activation and Deactivation of the Secondary
Carrier.
NOTE
When DC-HSDPA or MC-HSDPA is deactivated, DC-HSUPA is also deactivated.
Radio The RNC specifies the radio bearer policy of DC-HSUPA, that is, determines
bearers whether to enable the DC-HSUPA feature for the associated radio bearers. For
details, see section 4.4 Radio Bearers.
Function Evolution
Mobility The RNC controls DC-HSUPA measurements, soft handovers, and hard
managem handovers. For details, see 4.5 Mobility Management.
ent
Load The RAB directed retry decision (DRD), call admission control (CAC), load
control reshuffling (LDR), overload congestion (OLC), and queuing and preemption
functions have been evolved to work with DC-HSUPA. For details, see section
4.6 Load Control.
Power Closed loop power control and outer loop power control are performed
control separately on the two carriers of a DC-HSUPA UE. That is, the RNC maintains
the SIRtarget of two carriers separately according to the average number of
retransmissions.
HSUPA The RNC dynamically adjusts the TTI for a DC-HSUPA UE. The standard of
TTI adjusting the TTI for a DC-HSUPA UE is the same as that for an SC-HSUPA
selection UE. When the TTI of the DC-HSUPA UE is changed from 2 ms to 10 ms, DC-
HSUPA is disabled and only SC-HSUPA is available to the UE. When the TTI
is changed to 10 ms to 2 ms, DC-HSUPA is enabled on the UE supporting DC-
HSUPA. For details, see HSUPA TTI Selection Feature Parameter
Description.
Dynamic When the dynamic cell shutdown feature has been enabled, the RNC counts DC-
cell HSUPA UEs only on the primary carrier among HSUPA UEs when determining
shutdown the number of HSUPA UEs on the uplink carrier.
Iub flow DC-HSUPA requires that the E-DCH UL flow multiplexing mode be used over
control the Iub interface. When the two carriers of a DC-HSUPA UE share the Iub
bandwidth, the buffered data volume equals the sum of the buffered data volume
on the primary and secondary carriers. The Iub flow control procedure for a DC-
HSUPA UE is the same as that for an SC-HSUPA UE. For details, see
Transmission Resource Management Feature Parameter Description.
NodeB CE During the admission process, channel element (CE) consumption of a DC-
consumpti HSUPA UE is calculated based on the guaranteed bit rate (GBR) on the primary
on carrier. On the secondary carrier, the UE consumes two NodeB CEs by default.
After the connection is established, NodeB CE consumption calculation of the
DC-HSUPA UE on each carrier is the same as that of an SC-HSUPA UE, which
is based on the SFs on the uplink E-DCH of the corresponding carrier.
4.3 Scheduling
DC-HSUPA UEs are collaboratively scheduled on primary and secondary carriers. The MAC-
i scheduler dynamically adjusts the scheduling priorities of DC-HSUPA UEs on these two
carriers based on the carrier uplink load, thereby achieving uplink load sharing between these
two carriers.
The MAC-i scheduler adjusts the priority of one DC-HSUPA UE on two carriers at a time to
ensure that DC-HSUPA UEs have the same priority as SC-HSUPA UEs on a lightly load carrier.
That is, DC-HSUPA UEs obtain a fair chance to be scheduled with SC-HSUPA UEs. On a
heavily loaded carrier, the DC-HSUPA UEs have a lower priority than SC-HSUPA UEs and
can use only the remaining uplink resources of SC-HSUPA UEs.
When calculating the scheduling priorities of a DC-HSUPA UE, the MAC-i scheduler uses the
sum of data rates of the DC-HSUPA UE on the two carriers as the UE's throughput.
When the independent active sets function is enabled, UEs can use DC-HSUPA when the serving
cell in the SC-HSUPA active set supports DC-HSUPA and the NodeB serving the other cells in
the SC-HSUPA active set supports the independent active sets function introduced in RAN17.1.
When DC-HSUPA services are established, cells in the E-DCH active sets for the primary and
secondary carriers are configured as follows:
l The serving cell of SC-HSUPA services is used as the primary cell. In Figure 4-1, cell A
is the primary cell.
l The secondary cell is the one that forms a DC-HSUPA group with the primary cell. In
Figure 4-1, cell F is the secondary cell.
l As for the non-serving cells in the E-DCH active set for the secondary carrier, they and
their counterparts in the E-DCH active set for the primary carrier must operate in the same
frequencies as those of cells A and F. An example of non-serving cells in the E-DCH active
set for the secondary carrier is cell G.
l Single service
– For PS streaming services, the uplink maximum bit rate (MBR) is greater than or equal
to UlStrThsOnHsupa(BSC6900,BSC6910) and StreamHsupa2msTtiRateThs
(BSC6900,BSC6910).
– For BE services, the uplink MBR must be greater than or equal to
UlBeTraffThsOnHsupa(BSC6900,BSC6910) and BeHsupa2msTtiRateThs
(BSC6900,BSC6910).
l Combined services
– DC-HSUPA applies to combined services only when all services of the combined
services can use HSPA RABs and one service of the combined services can use DC-
HSUPA RABs. Otherwise, DC-HSUPA does not apply to combined services.
– When DC-HSUPA is enabled for non-scheduling combined services, the data of these
services will be transmitted only on the primary carrier.
If a DC-HSUPA radio bearer rolls back to an SC-HSUPA radio bearer due to mobility in
scenarios where the independent active set function is enabled, the radio bearer cannot be
reconfigured to use DC-HSUPA again within the period of time specified by
DCHsupaHRetryPenaltyTime(BSC6900,BSC6910).
Inter-Frequency Measurements
Inter-frequency measurements refer to the measurements performed by DC-HSUPA UEs on
frequencies other than the primary carrier frequency.
F1, F2, and F3 are adjacent frequencies; a UE supporting DC-HSUPA establishes a radio bearer
on F2.
l If the UE uses DC-HSUPA and the secondary carrier frequency is F3, the RNC can initiate
the inter-frequency measurements without activating compressed mode only on F3.
l If the UE uses only the primary carrier for data transmission, the RNC can initiate the inter-
frequency measurements without activating compressed mode on F1 or F3.
Intra-Frequency Measurements
The RNC instructs the UE to perform measurements only on the primary carrier frequency when
the independent active sets function is disabled. The intra-frequency measurements on the
primary carrier frequency are same as that on the carrier frequency of SC-HSUPA.
When the independent active sets function is enabled, the RNC instructs the UE to perform
measurements on both the primary and secondary carrier frequencies. The intra-frequency
measurements on the primary carrier frequency are same as those on the carrier frequency of
SC-HSUPA. The secondary carrier supports only events 1A, 1B, 1C, and 1F. For details, see
Figure 4-2 E-DCH active sets for the primary and secondary carriers
If a cell that does not support DC-HSUPA is added to the E-DCH active set, DC-HSUPA UEs
will be reconfigured as SC-HSUPA UEs.
soft handover parameters same as those for the serving carrier of SC-HSUPA UEs, and the
secondary carrier uses a set of new soft handover parameters.
When a neighboring cell of the primary carrier meeting any of the following conditions is added
to the E-DCH active set for the primary carrier, DC-HSUPA UEs are reconfigured as SC-HSUPA
UEs:
l The cell does not support HSUPA, UL Layer 2 Improvement, or F-DPCH. Alternatively,
the cell supports only HSUPA 10 ms TTI.
l The cell is under a neighboring RNC.
l The NodeB of the cell does not support the independent active sets function.
When the serving cell is removed from the E-DCH active set for the secondary carrier, DC-
HSUPA UEs are reconfigured as SC-HSUPA UEs.
Figure 4-3 UE still using DC-HSUPA after reporting event 1D on the primary carrier
In Figure 4-3, the E-DCH active set for the primary carrier includes cell A (primary cell)
and cell B, and the E-DCH active set for the secondary carrier includes cell D (secondary
cell) and cell E. The UE's serving cell is changed from cell A to cell B, which also supports
DC-HSUPA. In addition, the cell that forms a DC-HSUPA cell group with cell B is in the
E-DCH active set for the secondary carrier. Therefore, the UE still uses DC-HSUPA after
reporting event 1D on the primary carrier.
In Figure 4-4, the E-DCH active set for the primary carrier includes cell A (primary cell)
and cell B, and the E-DCH active set for the secondary carrier includes only cell D
(secondary cell). The UE's serving cell is changed from cell A to cell B, which may or may
not support DC-HSUPA. When cell B supports DC-HSUPA, the cell that forms a DC-
HSUPA cell group with cell B is not in the E-DCH active set for the secondary carrier.
Therefore, the UE is reconfigured as an SC-HSUPA UE after reporting event 1D on the
primary carrier.
l The UE reports event 1A on the primary carrier, and a non-serving cell, cell C, is added to
the E-DCH active set for the active carrier, as shown in Figure 4-5.
Figure 4-5 Active set update triggered by event 1A on the primary carrier
In Figure 4-5, the E-DCH active set for the primary carrier includes only cell A (primary
cell), and the E-DCH active set for the secondary carrier includes only cell D (secondary
cell). After an intra-frequency neighboring cell of the primary cell, cell B, is added to the
E-DCH active set for the primary carrier, the UE still uses DC-HSUPA for data
transmission.
l The UE reports event 1B on the primary carrier, and a non-serving cell, cell B, is removed
from the E-DCH active set for the primary carrier, as shown in Figure 4-6.
Figure 4-6 Active set update triggered by event 1B on the primary carrier
In Figure 4-6, the E-DCH active set for the primary carrier includes cell A (primary cell)
and cell B, and the E-DCH active set for the secondary carrier includes cell D (secondary
carrier) and cell E. After cell B is removed from the E-DCH active set for the primary
carrier, the UE still uses DC-HSUPA for data transmission.
l The UE reports event 1A on the secondary carrier, and cell F is added to the E-DCH active
set for the secondary carrier, as shown in Figure 4-7.
Figure 4-7 E-DCH active set for the secondary carrier update triggered by event 1A on the
secondary carrier
In Figure 4-7, the E-DCH active set for the primary carrier includes only cell A (primary
cell), and the E-DCH active set for the secondary carrier includes only cell D (secondary
cell). After an intra-frequency neighboring cell of the secondary cell, cell E, is added to the
E-DCH active set for the secondary carrier, the UE still uses DC-HSUPA for data
transmission.
l The UE reports event 1B or 1F on the secondary carrier, and a non-serving cell, cell E, is
removed from the E-DCH active set for the secondary carrier, as shown in Figure 4-8.
Figure 4-8 Removal of a non-serving cell from the E-DCH active set for the secondary
carrier after event 1B or 1F on the secondary carrier
l The UE reports event 1B or 1F on the secondary carrier, and a serving cell, cell D, is
removed from the E-DCH active set for the secondary carrier. After the cell removal, a DC-
HSUPA UE is reconfigured as an SC-HSUPA UE, as shown in Figure 4-9.
If any cell in the E-DCH active set does not support uplink 16QAM, DC-HSUPA with uplink
16QAM will roll back to DC-HSUPA without uplink 16QAM.
In addition, an SC-HSUPA active set supports a maximum of six cells as stipulated by section
10.3.7.39 "Intra-frequency measurement reporting criteria" in 3GPP TS 25.331 (V10.0.0). An
E-DCH active set for the primary or secondary carrier supports a maximum of four cells.
Upon completion of the handover, if the DC-HSUPA feature is included in HSPA technologies
that can be retried by UEs (DC-HSUPA under the RetryCapability(BSC6900,BSC6910)
parameter is selected) and the target cell supports DC-HSUPA, the RNC attempts to reconfigure
the UE as a DC-HSUPA UE through the periodic DRD triggered by HSPA+ technological
satisfaction.
When the independent active sets function is enabled, the RNC performs periodic DRD to make
an RB with DC-HSUPA carry the UE if the following conditions are met:
DCHsupaHRetryPenaltyTime(BSC6900,BSC6910) expires.
The serving cell in the SC-HSUPA active set supports DC-HSUPA and the independent active
sets function.
The NodeB of the other cells in the SC-HSUPA active set support the independent active sets
function.
During the periodic DRD, cells in the E-DCH active sets for the primary and secondary carriers
are configured as follows:
l The serving cell of SC-HSUPA services is used as the primary serving cell.
l The secondary cell is the one that forms a DC-HSUPA group with the primary cell.
l As for the non-serving cells in the E-DCH active set for the secondary carrier, they and
their counterparts in the E-DCH active set for the primary carrier must operate in the same
frequencies as those of cells A and F shown in Figure 4-1. An example of non-serving cells
in the E-DCH active set for the secondary carrier is cell G.
4.6.2 CAC
The RNC performs admission on DC-HSUPA UEs based on air interface resources, NodeB
credit resources, Iub resources, and number of HSUPA UEs.
If the admission fails, DC-HSUPA users may switch to the DCH. For details, see section 3.5.4
"E2D Reconfiguration After a Soft Handover Failure" in Handover Feature Parameter
Description.
l Algorithm 1: CAC based on current cell load and new service load increment
– a. For DC-HSUPA services, if the sum of the current uplink load and new service load
increment on either the primary or secondary carrier is less than UlCellTotalThd
(BSC6900,BSC6910), the DC-HSUPA UE can be admitted to the network. The uplink
load increment introduced by a DC-HSUPA UE is calculated based on the GBR and
needs to be considered only on the primary carrier.
– b. Non-scheduling services on the DC-HSUPA UE are admitted on the primary carrier.
The admission method is the same as that for an SC-HSUPA UE.
– c. CAC based on the provided bit rate (PBR) is not performed on the DC-HSUPA UE.
l Algorithm 2: CAC based on the number of equivalent users (ENU)
– The uplink ENU resource consumed by the DC-HSUPA UEs that have been admitted
is calculated only on the primary carrier. The calculation method is the same as that of
an SC-HSUPA UE.
– The RNC decides whether to admit a DC-HSUPA UE based on uplink ENU resources
on the primary carrier. The decision is the same as that for an SC-HSUPA UE.
l Algorithm 3: CAC based on current cell load
The admission method used by this algorithm is the same as that used by algorithm 1. The
difference is that this algorithm considers only the current uplink load in the cell and does
not consider the new service load increment. That is, the new service load increment is
zero.
l Algorithm 4: CAC based on actual uplink service load
When the current uplink load on both primary and secondary carriers is lower than
UlCellTotalThd(BSC6900,BSC6910), admission of the DC-HSUPA UE is successful.
– Current uplink load estimation: The uplink load introduced by the DC-HSUPA UE is
calculated and then apportioned on the primary and secondary carriers based on the UE
rate ratio per carrier.
– Uplink load increment estimation: The uplink load increment introduced by a DC-
HSUPA UE is calculated based on the GBR.
HSUPA UEs whose primary carriers are the same as those for DC-HSUPA UEs preempting
resources. The preemption policy remains unchanged after the introduction of DC-HSUPA.
5 Related Features
Prerequisite Features
l DC-HSUPA depends on the following features:
– WRFD-010614 HSUPA Phase 2
– WRFD-010695 UL Layer 2 Improvement
– WRFD-010652 SRB over HSDPA
– WRFD-010636 SRB over HSUPA
– WRFD-010696 DC-HSDPA
– WRFD-010638 Dynamic CE Resource Management
– WRFD-01061403 HSUPA 2ms TTI
l With DC-HSUPA, the uplink peak rate of users can reach 11.5 Mbit/s when the following
feature is deployed:
– WRFD-010698 HSPA+ Uplink 11.5Mbit/s per User
l With DC-HSUPA, the uplink peak rate of users can reach 23 Mbit/s when the following
features are deployed:
– WRFD-010694 UL 16QAM
– WRFD-010697 E-DPCCH Boosting
– WRFD-140203 HSPA+ Uplink 23Mbps per User
Impacted Features
l WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier
In Multi-carrier
The function of Traffic-Based Activation and Deactivation of the Supplementary Carrier
In Multi-carrier of DC-HSDPA is invalid for users who are configured with DC-HSUPA.
l WRFD-01061404 HSUPA 2ms/10ms TTI Handover or algorithm of coverage-based BE
service fallback from E-DCH to DCH
In areas far from the NodeB, DC-HSUPA UE throughput is lower than the SC-HSUPA UE
throughput because of uplink power insufficiency of DC-HSUPA when the function of
6 Network Impact
System Capacity
l Number of system users
The number of DC-HSUPA UEs supported by each baseband board in a NodeB is half the
number of SC-HSUPA UEs. When the number of DC-HSUPA UEs is separately calculated
on the primary and secondary carriers, DC-HSUPA does not affect the number of supported
system users.
When the independent active sets function is enabled, the system can accommodate more
DC-HSUPA users if DC-HSUPA cells have non-contiguous coverage or if the primary
carrier provides contiguous coverage but the secondary carrier provides non-contiguous
coverage.
l System throughput
Carrier uplink load increases because the secondary carrier uses the DPCCH for power
control. The increase is not noticeable when there is a small number of DC-HSUPA UEs.
When there are a large number of online DC-HSUPA UEs in the CELL_DCH state, the
overhead for the DPCCH raises the uplink load over the air interface. The uplink capacity
is reduced as a result. It is recommended that the function of activating/deactivating the
secondary carrier based on RTWP be enabled. With this function, the NodeB deactivates
the uplink secondary carriers for DC-HSUPA UEs when uplink load congestion occurs,
thereby alleviating the uplink load congestion.
When the independent active sets function is enabled, the uplink interference of the
secondary carrier to neighboring cells is reduced, and the access success rate of the
secondary cell is increased.
Network Performance
l Hardware
A DC-HSUPA UE consumes one more licensed CE than an SC-HSUPA UE.
l Coverage
DC-HSUPA coverage is slightly inferior to SC-HSUPA coverage because the secondary
carrier uses the DPCCH for power control and therefore consumes additional uplink power.
When DC-HSUPA coverage is poor, the function of activating/deactivating the secondary
carrier based on uplink transmit power can be enabled. With this function, the NodeB
deactivates the secondary carrier when certain conditions are met, reducing the overhead
for the DPCCH on the secondary carrier. The DC-HSUPA coverage should not be inferior
to SC-HSUPA coverage when the secondary carrier is deactivated. When this function is
disabled, this defect can be relieved by enabling the HSUPA TTI Selection feature or
coverage-based BE service fallback from the E-DCH to DCH algorithm.
7 Engineering Guidelines
This chapter provides engineering guidelines for DC-HSUPA. For details about how to enable
the uplink peak rate of 11.5 Mbit/s or 23 Mbit/s with DC-HSUPA, see HSPA Evolution Feature
Parameter Description.
The proportion of UEs supporting DC-HSUPA is large if the following condition is met, where 5%
indicates the single-user uplink load rate consumed by the DPCCH.
l NumofDCUEs = VS.HSUPA.DC.PRIM.UE.Mean.Cell(BSC6900,BSC6910) +
VS.HSUPA.DC.SEC.UE.Mean.Cell(BSC6900,BSC6910)
l BackgroundNoise can be queried by running the RNC MML command LST UCELLCAC.
l TargetRoT = , where
MaxTargetUlLoadFactor can be queried by running the LST UCELLHSUPA command.
l If the independent active sets function which is introduced in RAN17.1 is enabled, it is
recommended that all NodeBs under the same RNC support the independent active sets
function. Otherwise, a DC-HSUPA radio bearer falls back to an SC-HSUPA radio bearer
during mobility.
– If the uplink peak rate of DC-HSUPA UEs needs to reach 23 Mbit/s, the sum of the
values of the following counters applicable to UEs belonging to HSUPA category 9 and
above must be greater than or equal to 1.
7.3 Planning
RF Planning
Two adjacent frequencies are available, and the spacing between these two frequencies must be
less than or equal to 5 MHz.
Network Planning
The two cells that form a DC-HSUPA cell group must belong to the same sector and be served
by the same BBU. In addition, these two cells must have DC-HSDPA enabled.
7.4 Deployment
7.4.1 Requirements
l Hardware
This feature has the following requirements on the NodeB hardware:
– The 3900 series base stations must be configured with the WBBPb, WBBPd, WBBPf,
or UBBPd board.
To reach the peak rate of 23 Mbit/s, the maximum transmission unit (MTU) must be set to
1500 when the RNC is configured with the FG2a or GOUa board. If the MTU cannot be
set to 1500, the FG2a or GOUa board must be replaced by other boards.
NOTE
To query the type of an RNC board, run the DSP BRD command.
To query the MTU, run the LST ETHPORT command.
l Feature
For details about the power configuration in the following scenarios, see the engineering
guidelines for the WRFD-010697 E-DPCCH Boosting feature in Uplink16QAM+E-
DPCCH Boosting Feature Parameter Description.
– When the uplink peak rate needs to reach 11.5 Mbit/s, uplink 16QAM is not enabled
and the UL Layer 2 Improvement feature is enabled.
– When the uplink peak rate needs to reach 23 Mbit/s, both the uplink 16QAM and UL
Layer 2 Improvement features are enabled.
Parameters related to the DC-HSUPA features are as follows:
If RAN Sharing is enabled, the licensed value is allocated among the primary and secondary
operators according to the value of the "License Allocation for Multiple Operators
parameter."
Method 2: Some license control items, for example, UL CE Num, can be allocated to both
the common group and private groups. In this case, the licensed value specified by the
private group is preferentially used, and the licensed value allocated to the common group
is used on a first-come, first-served basis. For NodeB license allocation in multi-operator
scenarios, see License Management Feature Parameter Description.
l Others
– Two DC-HSUPA cells must be on intra-band adjacent carriers that provide the same
coverage.
– Two adjacent frequencies are available, and the spacing between these two frequencies
must be less than or equal to 5 MHz. DC-HSDPA has been configured for these two
frequencies in the downlink. For details, see the Engineering Guidelines chapter of
Multi-Carrier HSDPA Feature Parameter Description.
– Only UEs belonging to E-DCH categories 8 and higher support DC-HSUPA.
Cell edge user (CEU) ULSECCELLDEA The recommended Radio network plan
rate threshold for the CTCOVTHR value is 500 kbit/s. (internal plan)
function of
activating/
deactivating the
secondary carrier
7.4.3 Precautions
For the 3900 series macro base stations and micro base stations, you are advised to run the DEA
UCELL command to deactivate the cells to be added to a DC-HSUPA cell group before
activating DC-HSUPA. Otherwise, online UEs in these cells experience call drops.
7.4.4 Activation
This feature can be activated in a batch using the CME. For detailed operations, see the following section
in the CME product documentation or online help: Managing the CME > CME Guidelines > Enhanced
Feature Management > Feature Operation and Maintenance.
Step 1 Run the NodeB MML command ADD NODEBMULTICELLGRP to configure Multiple
Carrier Cell Group Type and Multiple Carrier Cell Group ID.
NOTE
The cell group ID, which is specified by multiCellGrpId, must be unique under a NodeB.
The cell group ID can be viewed by running the NodeB MML command LST
NODEBMULTICELLGRP.
Step 2 Run the NodeB MML command ADD NODEBMULTICELLGRPITEM to add a local cell
to the DC-HSUPA multi-carrier cell group. Repeat this step for each local cell to be added.
Step 3 To enable the DC-HSUPA algorithm on the RNC, run the RNC MML command SET
UCORRMALGOSWITCH. In this step, select CFG_HSUPA_DC_SWITCH under
Channel Configuration Strategy Switch.
Step 4 To configure the cell capability on the RNC, run the RNC MML command MOD
UCELLALGOSWITCH. In this step, select DC_HSUPA(Cell DC-HSUPA Function
Switch) under Cell Hspa Plus function switch.
NOTE
Step 5 To configure the DC-HSUPA periodic retry capability, run the RNC MML command SET
UFRC command. In this step, select DC_HSUPA under HSPA Technologies Retried by
UEs.
NOTE
Ensure that the periodic DRD have been enabled before enabling the DC-HSUPA periodic retry. That is,
UL_L2_ENHANCE, SRB_OVER_HSDPA, SRB_OVER_HSUPA, and DC_HSDPA in the
RetryCapability parameter are selected.
Step 6 Enable the function of activating/deactivating the secondary carrier based on RTWP.
Run the NodeB MML command SET ULOCELLMACEPARA to enable the function of
activating/deactivating the DC-HSUPA secondary carrier based on RTWP. In this step, set
ULSECCELLACTOPTSW to ON.
Step 7 Set the CEU rate threshold for the function of activating/deactivating the secondary carrier.
Run the NodeB MML command SET ULOCELLMACEPARA command with
ULSECCELLDEACTCOVTHR set to an appropriate value. The recommended value is 500
kbit/s.
Step 8 (Optional) Enable the independent active sets function. Run the RNC MML command SET
UCORRMALGOSWITCH with HO_DC_HSUPA_IND_TWO_ACTIVESET selected
under the HandOver Switch2 parameter.
----End
Configure the parameters of a single object before a batch modification. 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 7-3. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 while running the wizard to obtain online help.
l Signaling trace
1. In the Navigation Tree pane on the RNC LMT, click the Trace tab. In the displayed
Trace Navigation Tree pane, double-click UMTS Services. On the unfolded list,
double-click Uu Interface Trace. In the displayed Uu Interface Trace dialog box,
select RRC_RB_SETUP to trace Uu interface signaling messages of DC-HSUPA
cells.
2. Perform dialing tests on FTP services of a DC-HSUPA UE and ensure that HSUPA
services have been set up.
3. On the Trace tab page of the RNC LMT, check whether the RRC_RB_SETUP
messages contain the ul-SecondaryCellInfoFDD information element (IE). If the IE
is contained, the DC-HSUPA feature has been activated, as shown in Figure 7-1.
7.4.6 Deactivation
Step 2 (Optional) Disable the function of activating/deactivating the secondary carrier based on RTWP.
Run the NodeB MML command SET ULOCELLMACEPARA to disable the function of
activating/deactivating the DC-HSUPA secondary carrier based on RTWP. In this step, set
ULSECCELLACTOPTSW to OFF.
Step 3 (Optional) Lower the CEU rate threshold so that the secondary carrier cannot be easily
deactivated.
Step 4 (Optional) Run the RNC MML command SET UCORRMALGOSWITCH with
HO_DC_HSUPA_IND_TWO_ACTIVESET deselected under the HandOver Switch2
parameter.
----End
If the RAB setup success rate decreases or call drop rate increases for DC-HSUPA services after
DC-HSUPA is enabled, it is recommended that the rate threshold for the function of activating
or deactivating the secondary carrier based on uplink transmit power be increased or the
WRFD-01061404 HSUPA 2ms/10ms TTI Handover feature be enabled.
NOTE
7.7 Troubleshooting
Table 7-4 lists the alarms related to DC-HSUPA.
8 Parameters
HO_REPORT_SWITCH,
HO_IMSI_MM_SWITCH
Default Value: HO_UL_UOLC_SWITCH:0,
HO_DC_HSUPA_IND_TWO_ACTIVESET:0,
HO_MC_EXT_LTE_BAND_SWITCH:0,
HO_U2L_BASE_UE_LTE_MEAS_CAP_SWITCH:
0, HO_REPORT_SWITCH:0,
HO_IMSI_MM_SWITCH:0
WRFD- Backgro 13. E_DRX: When the switch is on, E_DRX can be
0106090 und configured for the HSUPA service.
2 Traffic 14. DC_HSUPA: When this switch is turned on, the DC-
WRFD- Class on HSUPA function can be enabled for HSUPA services.
010702 HSDPA
15. HSDPA_4C_MIMO: Whether the MC-HSDPA
Interacti +MIMO feature is allowed for HSDPA services. When
WRFD-
ve and this switch is turned on, the MC-HSDPA+MIMO (3C-
010701
Backgro HSDPA+MIMO and 4C-HSDPA+MIMO) feature is
WRFD- und allowed for HSDPA services.
010609 Traffic
16. HSDPA_4C: Whether the 3C-HSDPA or 4C-
WRFD- Class on
HSDPA feature is allowed for HSDPA services. When
010510 HSUPA
this switch is turned on, the 3C-HSDPA or 4C-HSDPA
WRFD- DC- feature is allowed for HSDPA services.
010688 HSUPA
17. DBMIMO_HSDPA: Whether the DB-HSDPA
WRFD- Combin +MIMO feature is allowed for HSDPA services. When
010686 ation of this switch is turned on, the DB-HSDPA+MIMO
Two CS feature is allowed for HSDPA services.
WRFD- Services
010687 18. DB_HSDPA: Whether the DB-HSDPA feature is
(Except
allowed for HSDPA services. When this switch is
WRFD- for Two
turned on, the DB-HSDPA feature is allowed for
010684 AMR
HSDPA services.
WRFD- Speech
Services 19. HSDPA_SFDC(HSDPA_SFDC): Whether a cell
010685 supports the SFDC HSDPA function. When this switch
)
WRFD- is set to on, the cell supports the SFDC HSDPA
Combin
010683 function. This switch is reserved for the MF-HSDPA
ation of
WRFD- (multiflow HSDPA) function and cannot be used in the
Two CS
021000 current version.
Services
and One 20. HSDPA_DF3C(HSDPA_DF3C): Whether a cell
WRFD-
PS supports the DF3C HSDPA function. When this switch
010503
Service is set to on, the cell supports the DF3C HSDPA function.
WRFD- This switch is reserved for the MF-HSDPA(multiflow
(Except
0106150 HSDPA) function and cannot be used in the current
for Two
2 version.
AMR
WRFD- Speech GUI Value Range: 64QAM(Cell 64QAM Function
0106150 Services Switch), MIMO(Cell MIMO Function Switch),
3 ) E_FACH(Cell E_FACH Function Switch), DTX_DRX
WRFD- Combin (Cell DTX_DRX Function Switch),
010502 ation of HS_SCCH_LESS_OPERATION(Cell HS_SCCH
One CS LESS OPERATION Function Switch),
WRFD- DL_L2ENHANCED(Cell DL L2ENHANCED
0106150 Service
and One Function Switch), 64QAM_MIMO(Cell 64QAM
4 +MIMO Function Switch), UL_16QAM(Cell UL
PS
WRFD- Service 16QAM Function Switch), DC_HSDPA(Cell DC-
0106150 HSDPA Function Switch), UL_L2ENHANCED(Cell
5 UL L2ENHANCED Function Switch),
Downlin
k
Enhance
d L2
Downlin
k
64QAM
Transpo
rt
Channel
Manage
ment
Interacti
ve QoS
Class
Combin
ation of
One CS
Service
and Two
PS
Services
Combin
ation of
Three
PS
Services
Streami
ng QoS
Class
Combin
ation of
One CS
Service
and
Three
PS
Services
Combin
ation of
Four PS
Services
Uplink
Control
Channel
OLPC
Physical
Channel
Manage
ment
4C-
HSDPA
DB-
HSDPA
+MIMO
Flexible
Dual
Carrier
HSDPA
MC-
HSDPA
+MIMO
Logical
Channel
Manage
ment
DB-
HSDPA
Multiple
RAB
Package
(PS
RAB >=
2)
Streami
ng
Traffic
Class on
HSUPA
Streami
ng
Traffic
Class on
HSDPA
WRFD- Backgro 13. E_DRX: When the switch is on, E_DRX can be
0106090 und configured for the HSUPA service.
2 Traffic 14. DC_HSUPA: When this switch is turned on, the DC-
WRFD- Class on HSUPA function can be enabled for HSUPA services.
010702 HSDPA
15. HSDPA_4C_MIMO: Whether the MC-HSDPA
Interacti +MIMO feature is allowed for HSDPA services. When
WRFD-
ve and this switch is turned on, the MC-HSDPA+MIMO (3C-
010701
Backgro HSDPA+MIMO and 4C-HSDPA+MIMO) feature is
WRFD- und allowed for HSDPA services.
010609 Traffic
16. HSDPA_4C: Whether the 3C-HSDPA or 4C-
WRFD- Class on
HSDPA feature is allowed for HSDPA services. When
010510 HSUPA
this switch is turned on, the 3C-HSDPA or 4C-HSDPA
WRFD- DC- feature is allowed for HSDPA services.
010688 HSUPA
17. DBMIMO_HSDPA: Whether the DB-HSDPA
WRFD- Combin +MIMO feature is allowed for HSDPA services. When
010686 ation of this switch is turned on, the DB-HSDPA+MIMO
Two CS feature is allowed for HSDPA services.
WRFD- Services
010687 18. DB_HSDPA: Whether the DB-HSDPA feature is
(Except
allowed for HSDPA services. When this switch is
WRFD- for Two
turned on, the DB-HSDPA feature is allowed for
010684 AMR
HSDPA services.
WRFD- Speech
Services 19. HSDPA_SFDC(HSDPA_SFDC): Whether a cell
010685 supports the SFDC HSDPA function. When this switch
)
WRFD- is set to on, the cell supports the SFDC HSDPA
Combin
010683 function. This switch is reserved for the MF-HSDPA
ation of
WRFD- (multiflow HSDPA) function and cannot be used in the
Two CS
021000 current version.
Services
and One 20. HSDPA_DF3C(HSDPA_DF3C): Whether a cell
WRFD-
PS supports the DF3C HSDPA function. When this switch
010503
Service is set to on, the cell supports the DF3C HSDPA function.
WRFD- This switch is reserved for the MF-HSDPA(multiflow
(Except
0106150 HSDPA) function and cannot be used in the current
for Two
2 version.
AMR
WRFD- Speech GUI Value Range: 64QAM(Cell 64QAM Function
0106150 Services Switch), MIMO(Cell MIMO Function Switch),
3 ) E_FACH(Cell E_FACH Function Switch), DTX_DRX
WRFD- Combin (Cell DTX_DRX Function Switch),
010502 ation of HS_SCCH_LESS_OPERATION(Cell HS_SCCH
One CS LESS OPERATION Function Switch),
WRFD- DL_L2ENHANCED(Cell DL L2ENHANCED
0106150 Service
and One Function Switch), 64QAM_MIMO(Cell 64QAM
4 +MIMO Function Switch), UL_16QAM(Cell UL
PS
WRFD- Service 16QAM Function Switch), DC_HSDPA(Cell DC-
0106150 HSDPA Function Switch), UL_L2ENHANCED(Cell
5 UL L2ENHANCED Function Switch),
Downlin
k
Enhance
d L2
Downlin
k
64QAM
Transpo
rt
Channel
Manage
ment
Interacti
ve QoS
Class
Combin
ation of
One CS
Service
and Two
PS
Services
Combin
ation of
Three
PS
Services
Streami
ng QoS
Class
Combin
ation of
One CS
Service
and
Three
PS
Services
Combin
ation of
Four PS
Services
Uplink
Control
Channel
OLPC
Physical
Channel
Manage
ment
4C-
HSDPA
DB-
HSDPA
+MIMO
Flexible
Dual
Carrier
HSDPA
MC-
HSDPA
+MIMO
Logical
Channel
Manage
ment
DB-
HSDPA
Multiple
RAB
Package
(PS
RAB >=
2)
Streami
ng
Traffic
Class on
HSUPA
Streami
ng
Traffic
Class on
HSDPA
UlStrTh BSC690 SET WRFD- HSUPA Meaning: Rate threshold for decision to use E-DCH to
sOnHsu 0 UFRCC 010612 Introduc carry PS streaming services. When the maximum UL
pa HLTYP WRFD- tion rate is higher than or equal to this threshold, the service
EPARA 010632 Package will be carried on E-DCH. Otherwise, it will be carried
Streami on DCH.
WRFD-
010701 ng GUI Value Range: D8, D16, D32, D64, D128, D144,
Traffic D256, D384
Class on Unit: kbit/s
HSUPA
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Uplink
Enhance Default Value: D256
d
CELL_F
ACH
UlStrTh BSC691 SET WRFD- HSUPA Meaning: Rate threshold for decision to use E-DCH to
sOnHsu 0 UFRCC 010612 Introduc carry PS streaming services. When the maximum UL
pa HLTYP WRFD- tion rate is higher than or equal to this threshold, the service
EPARA 010632 Package will be carried on E-DCH. Otherwise, it will be carried
Streami on DCH.
WRFD-
010701 ng GUI Value Range: D8, D16, D32, D64, D128, D144,
Traffic D256, D384
Class on Unit: kbit/s
HSUPA
Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384
Uplink
Enhance Default Value: D256
d
CELL_F
ACH
StreamH BSC690 SET WRFD- HSUPA Meaning: Rate threshold of 2ms TTI on the E-DCH for
supa2ms 0 UFRC 0106140 2ms TTI the PS streaming service. The 2ms TTI is used on the
TtiRate 3 TTI E-DCH when it is supported by the cell and UE and
Ths WRFD- Switch when the max rate of the HSUPA PS streaming service
010690 for BE exceeds this threshold. Otherwise, 10ms TTI is used.
WRFD- Services GUI Value Range: D8, D16, D32, D64, D128, D144,
010632 Based D256, D384, D608
on Unit: kbit/s
Coverag
e Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
608
Streami
ng Default Value: D384
Traffic
Class on
HSUPA
StreamH BSC691 SET WRFD- HSUPA Meaning: Rate threshold of 2ms TTI on the E-DCH for
supa2ms 0 UFRC 0106140 2ms TTI the PS streaming service. The 2ms TTI is used on the
TtiRate 3 TTI E-DCH when it is supported by the cell and UE and
Ths WRFD- Switch when the max rate of the HSUPA PS streaming service
010690 for BE exceeds this threshold. Otherwise, 10ms TTI is used.
WRFD- Services GUI Value Range: D8, D16, D32, D64, D128, D144,
010632 Based D256, D384, D608
on Unit: kbit/s
Coverag
e Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
608
Streami
ng Default Value: D384
Traffic
Class on
HSUPA
UlBeTra BSC690 SET WRFD- Interacti Meaning: This parameter specifies the rate threshold for
ffThsOn 0 UFRCC 0106120 ve and decision to use E-DCH to carry UL PS domain
Hsupa HLTYP 6 Backgro background/interactive services. When the maximum
EPARA WRFD- und UL service rate is higher than or equal to this threshold,
150250 Traffic the service will be carried on E-DCH. Otherwise, it will
Class on be carried on DCH.
WRFD- HSUPA
010612 GUI Value Range: D8, D16, D32, D64, D128, D144,
3C- D256, D384, D608, D1280, D2048, D2720, D5440
WRFD- HSDPA
010701 Unit: kbit/s
HSUPA Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
Introduc 608, 1280, 2048, 2720, 5440
tion
Package Default Value: D608
Uplink
Enhance
d
CELL_F
ACH
UlBeTra BSC691 SET WRFD- Interacti Meaning: This parameter specifies the rate threshold for
ffThsOn 0 UFRCC 0106120 ve and decision to use E-DCH to carry UL PS domain
Hsupa HLTYP 6 Backgro background/interactive services. When the maximum
EPARA WRFD- und UL service rate is higher than or equal to this threshold,
150250 Traffic the service will be carried on E-DCH. Otherwise, it will
Class on be carried on DCH.
WRFD- HSUPA
010612 GUI Value Range: D8, D16, D32, D64, D128, D144,
3C- D256, D384, D608, D1280, D2048, D2720, D5440
WRFD- HSDPA
010701 Unit: kbit/s
HSUPA Actual Value Range: 8, 16, 32, 64, 128, 144, 256, 384,
Introduc 608, 1280, 2048, 2720, 5440
tion
Package Default Value: D608
Uplink
Enhance
d
CELL_F
ACH
BeHsup BSC690 SET WRFD- HSUPA Meaning: This parameter specifies the rate threshold of
a2msTti 0 UFRC 0106140 2ms TTI 2ms TTI on the E-DCH for HSUPA BE service. When
RateThs 3 CE the cell capability and UE capability allows 2ms TTI,
WRFD- Overboo 2ms TTI on the E-DCH is used if the PS BE service
140212 king carried on HSUPA with uplink rate isn't less than this
threshold. Otherwise, 10ms TTI is used.
WRFD- Interacti
0106120 ve and GUI Value Range: D8, D16, D32, D64, D128, D144,
6 Backgro D256, D384, D608, D1280, D2048, D2720
BeHsup BSC691 SET WRFD- HSUPA Meaning: This parameter specifies the rate threshold of
a2msTti 0 UFRC 0106140 2ms TTI 2ms TTI on the E-DCH for HSUPA BE service. When
RateThs 3 CE the cell capability and UE capability allows 2ms TTI,
WRFD- Overboo 2ms TTI on the E-DCH is used if the PS BE service
140212 king carried on HSUPA with uplink rate isn't less than this
threshold. Otherwise, 10ms TTI is used.
WRFD- Interacti
0106120 ve and GUI Value Range: D8, D16, D32, D64, D128, D144,
6 Backgro D256, D384, D608, D1280, D2048, D2720
DCHsup BSC690 SET WRFD- DC- Meaning: Penalty time of periodical retries to DC-
aHRetry 0 UCOIF 140204 HSUPA HSUPA after DC-HSUPA falls back to SC-HSUPA
Penalty TIMER when the DC-HSUPA independent active set function
Time is enabled. Periodical retries include blind periodical
retries and measurement-based periodical retries. It is
recommended that the parameter value be greater than
the value of the "ChannelRetryTimerLen" parameter.
GUI Value Range: 1~255
Unit: s
Actual Value Range: 1~255
Default Value: 10
DCHsup BSC691 SET WRFD- DC- Meaning: Penalty time of periodical retries to DC-
aHRetry 0 UCOIF 140204 HSUPA HSUPA after DC-HSUPA falls back to SC-HSUPA
Penalty TIMER when the DC-HSUPA independent active set function
Time is enabled. Periodical retries include blind periodical
retries and measurement-based periodical retries. It is
recommended that the parameter value be greater than
the value of the "ChannelRetryTimerLen" parameter.
GUI Value Range: 1~255
Unit: s
Actual Value Range: 1~255
Default Value: 10
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:
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:
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. The HSDPA_SFDC and HSDPA_DF3C
151209 Micro switch are reserved for the MF-HSDPA(multiflow
WRFD- DC- HSDPA) function and cannot be used in the current
150207 HSDPA version.
WRFD- 4C- GUI Value Range: SRB_OVER_HSDPA,
010652 HSDPA SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
WRFD- SRB DL_L2_ENHANCE, DTX_DRX,
010686 over HSSCCH_LESS_OPERATION, MIMO_64QAM,
HSDPA DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
WRFD- EDPCCH_BOOSTING, DCMIMO_HSDPA,
010687 CPC - DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
WRFD- DTX / DBMIMO_HSDPA, DB_HSDPA, HSDPA_SFDC,
010684 DRX HSDPA_DF3C
WRFD- CPC - Unit: None
010685 HS-
SCCH Actual Value Range: SRB_OVER_HSDPA,
WRFD- less SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
010695 operatio DL_L2_ENHANCE, DTX_DRX,
WRFD- n HSSCCH_LESS_OPERATION, MIMO_64QAM,
010683 DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
2x2 EDPCCH_BOOSTING, DCMIMO_HSDPA,
WRFD- MIMO DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
010697 DBMIMO_HSDPA, DB_HSDPA, HSDPA_SFDC,
Downlin
WRFD- k HSDPA_DF3C
010694 Enhance Default Value: SRB_OVER_HSDPA:
WRFD- d L2 0,SRB_OVER_HSUPA:0,TTI_2MS:0,MIMO:
150227 UL 1,64QAM:1,DL_L2_ENHANCE:1,DTX_DRX:
WRFD- Layer 2 1,HSSCCH_LESS_OPERATION:1,MIMO_64QAM:
150209 Improve 0,DC_HSDPA:0,UL_L2_ENHANCE:0,UL_16QAM:
ment 0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:
WRFD- 0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:
150250 Downlin 0,DBMIMO_HSDPA:0,DB_HSDPA:
WRFD- k 0,HSDPA_SFDC:0, HSDPA_DF3C:0
170203 64QAM
WRFD- E-
010636 DPCCH
Boostin
WRFD- g
010696
UL
WRFD-
16QAM
150223
WRFD- DB-
010693 HSDPA
+MIMO
DB-
HSDPA
3C-
HSDPA
Uplink
Control
Channel
OLPC
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. The HSDPA_SFDC and HSDPA_DF3C
151209 Micro switch are reserved for the MF-HSDPA(multiflow
WRFD- DC- HSDPA) function and cannot be used in the current
150207 HSDPA version.
WRFD- 4C- GUI Value Range: SRB_OVER_HSDPA,
010652 HSDPA SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
WRFD- SRB DL_L2_ENHANCE, DTX_DRX,
010686 over HSSCCH_LESS_OPERATION, MIMO_64QAM,
HSDPA DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
WRFD- EDPCCH_BOOSTING, DCMIMO_HSDPA,
010687 CPC - DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
WRFD- DTX / DBMIMO_HSDPA, DB_HSDPA, HSDPA_SFDC,
010684 DRX HSDPA_DF3C
WRFD- CPC - Unit: None
010685 HS-
SCCH Actual Value Range: SRB_OVER_HSDPA,
WRFD- less SRB_OVER_HSUPA, TTI_2MS, MIMO, 64QAM,
010695 operatio DL_L2_ENHANCE, DTX_DRX,
WRFD- n HSSCCH_LESS_OPERATION, MIMO_64QAM,
010683 DC_HSDPA, UL_L2_ENHANCE, UL_16QAM,
2x2 EDPCCH_BOOSTING, DCMIMO_HSDPA,
WRFD- MIMO DC_HSUPA, HSDPA_4C_MIMO, HSDPA_4C,
010697 DBMIMO_HSDPA, DB_HSDPA, HSDPA_SFDC,
Downlin
WRFD- k HSDPA_DF3C
010694 Enhance Default Value: SRB_OVER_HSDPA:
WRFD- d L2 0,SRB_OVER_HSUPA:0,TTI_2MS:0,MIMO:
150227 UL 1,64QAM:1,DL_L2_ENHANCE:1,DTX_DRX:
WRFD- Layer 2 1,HSSCCH_LESS_OPERATION:1,MIMO_64QAM:
150209 Improve 0,DC_HSDPA:0,UL_L2_ENHANCE:0,UL_16QAM:
ment 0,EDPCCH_BOOSTING:0,DCMIMO_HSDPA:
WRFD- 0,DC_HSUPA:0,HSDPA_4C_MIMO:0,HSDPA_4C:
150250 Downlin 0,DBMIMO_HSDPA:0,DB_HSDPA:
WRFD- k 0,HSDPA_SFDC:0, HSDPA_DF3C:0
170203 64QAM
WRFD- E-
010636 DPCCH
Boostin
WRFD- g
010696
UL
WRFD-
16QAM
150223
WRFD- DB-
010693 HSDPA
+MIMO
DB-
HSDPA
3C-
HSDPA
Uplink
Control
Channel
OLPC
SRB
over
HSUPA
DC-
HSDPA
MC-
HSDPA
+MIMO
DL
64QAM
+MIMO
MULTI BTS390 ADD WRFD- DC- Meaning: Specifies the type of a multiple carrier cell
CELLG 0, NODEB 010696 HSDPA group.
RPTYP BTS390 MULTI WRFD- DC- GUI Value Range: HSDPA(HSDPA), HSUPA
E 0 CELLG 140204 HSUPA (HSUPA)
WCDM RP
A WRFD- DB- Unit: None
LST 150209 HSDPA
NODEB Actual Value Range: HSDPA, HSUPA
MULTI WRFD- 4C- Default Value: HSDPA(HSDPA)
CELLG 150207 HSDPA
RP WRFD- 3C-
150250 HSDPA
WRFD- Flexible
150208 Dual
WRFD- Carrier
150223 HSDPA
WRFD- MC-
150227 HSDPA
+MIMO
WRFD-
010699 DB-
HSDPA
+MIMO
DC-
HSDPA
+MIMO
MULTI BTS390 ADD None None Meaning: Uniquely identifies a multiple carrier cell
CELLG 0, NODEB group.
RPID BTS390 MULTI GUI Value Range: 0~95
0 CELLG
WCDM RP Unit: None
A ADD Actual Value Range: 0~95
NODEB Default Value: None
MULTI
CELLG
RPITE
M
LST
NODEB
MULTI
CELLG
RP
LST
NODEB
MULTI
CELLG
RPITE
M
RMV
NODEB
MULTI
CELLG
RP
RMV
NODEB
MULTI
CELLG
RPITE
M
ULOCE BTS390 ADD None None Meaning: Indicates the Local Cell ID. The local cell ID
LLID 0, ULOCE is unique for one NodeB.
BTS390 LL GUI Value Range: 0~268435455
0 ADD
WCDM Unit: None
ULOCE
A Actual Value Range: 0~268435455
LLBBU
NIT Default Value: None
BLK
ULOCE
LL
DSP
ULOCE
LL
DSP
ULOCE
LLDES
ENS
DSP
ULOCE
LLRES
LST
ULOCE
LL
LST
ULOCE
LLBBU
NIT
LST
ULOCE
LLPRI
LST
ULOCE
LLTL
MOD
ULOCE
LL
RMV
ULOCE
LL
RMV
ULOCE
LLBBU
NIT
SET
ULOCE
LLDES
ENS
SET
ULOCE
LLPRI
SET
ULOCE
LLTL
UBL
ULOCE
LL
ULSEC BTS390 SET WRFD- DC- Meaning: Indicates to enable RTWP-based secondary
CELLA 0, ULOCE 140204 HSUPA DC-HSUPA cell activation and deactivation.
CTOPT BTS390 LLMAC GUI Value Range: OFF(OFF), ON(ON)
SW 0 EPARA
WCDM Unit: None
LST
A ULOCE Actual Value Range: OFF, ON
LLMAC Default Value: OFF(OFF)
EPARA
ULSEC BTS390 SET WRFD- DC- Meaning: Indicates the minimum rate threshold
CELLD 0, ULOCE 140204 HSUPA supported by the uplink transmit power for ensuring the
EACTC BTS390 LLMAC minimum coverage of activated DC-HSUPA UEs on
OVTHR 0 EPARA the secondary carrier. To be specific, to meet the
WCDM LST minimum coverage requirements of activated DC-
A ULOCE HSUPA cell edge UEs (CEUs) on the secondary carrier,
LLMAC the maximum rate threshold supported by the uplink
EPARA transmit power cannot be lower than this threshold.
Otherwise, the CEUs on the secondary carrier need to
be deactivated.
GUI Value Range: 0~1000
Unit: 10kbps
Actual Value Range: 0~10000, step:10
Default Value: 0
HSUPA 9. DRA_HSDPA_DL_FLOW_CONTROL_SWITCH:
Introduc When the switch is on, flow control is enabled for
tion HSDPA services in AM mode.
Package 10. DRA_HSDPA_STATE_TRANS_SWITCH: When
Active the switch is on, the status of the UE RRC that carrying
Queue HSDPA services can be changed to CELL_FACH at the
Manage RNC. If a PS BE service is carried over the HS-DSCH,
ment the switch PS_BE_STATE_TRANS_SWITCH should
(AQM) be on simultaneously. If a PS real-time service is carried
SRB over the HS-DSCH, the switch
over PS_NON_BE_STATE_TRANS_SWITCH should be
HSUPA on simultaneously.
HSDPA 11. DRA_HSUPA_DCCC_SWITCH: When the switch
Flow is on, the DCCC algorithm is used for HSUPA. The
Control DCCC switch must be also on before this switch takes
effect.
HSDPA
State 12. DRA_HSUPA_STATE_TRANS_SWITCH: When
Transiti the switch is on, the status of the UE RRC that carrying
on HSUPA services can be changed to CELL_FACH at the
RNC. If a PS BE service is carried over the E-DCH, the
HSUPA switch PS_BE_STATE_TRANS_SWITCH should be
DCCC on simultaneously. If a PS real-time service is carried
over the E-DCH, the switch
PS_NON_BE_STATE_TRANS_SWITCH should be
on simultaneously.
13. DRA_IP_SERVICE_QOS_SWITCH: Switch of
the algorithm for increasing the quality of subscribed
services. When this parameter is set to ON, the service
priority weight of the subscriber whose key parameters
(IP Address, IP Port, and IP Protocol Type) match the
specified ones can be adjusted. In this way, the QoS is
improved.
14. DRA_PS_BE_STATE_TRANS_SWITCH: When
this switch is turned on, UEs can be transited among the
CELL_DCH, CELL_FACH, CELL_PCH, and
URA_PCH states when they are processing PS BE
services.
15. DRA_PS_NON_BE_STATE_TRANS_SWITCH:
When this switch is turned on, UEs can be transited
between the CELL_DCH and CELL_FACH states
when they are processing real-time PS services.
16. DRA_R99_DL_FLOW_CONTROL_SWITCH:
Under a poor radio environment, the QoS of high speed
services drops considerably and the TX power is overly
high. In this case, the RNC can set restrictions on low
24.
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H: Whether to activate the coverage-based initial TTI
selection algorithm specific to BE services. When this
switch is turned on and conditions on 2 ms TTI specific
to BE services has been met, the RNC determines uplink
coverage wideness of specific cells based on the Ec/N0
values reported by UEs during RRC connection. If the
uplink coverage of the cells is weak, the RNC allocates
a 10 ms TTI to BE services as their initial TTI.
25. DRA_F2U_SWITCH: Whether to enable state
transition from CELL_FACH to URA_PCH.When this
switch is turned on, a UE can directly move from the
CELL_FACH to URA_PCH state. When this switch is
turned off, a UE must move from the CELL_FACH to
CELL_PCH and then to URA_PCH state.
26. DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH:
Whether to validate the initial selection function for
load-based happy bit delay condition. This function can
be used to improve the HSUPA throughput per UE.The
alternative happy bit delay condition (specified by the
AltHBDelaycnd parameter in the ADD
UTYPRABHSPA command) is selected when the
following conditions are met: This switch is turned on,
the HSUPA UE initially accesses the cell, and the cell
uplink load is not limited.The happy bit delay time
(specified by the HBDelaycnd parameter in the ADD
UTYPRABHSPA command) is selected when any of
the preceding three conditions is not met.
GUI Value Range: DRA_AQM_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH,
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_RES_BE_TTI_RECFG_SWITCH,
DRA_DCCC_SWITCH,
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH,
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_DCCC_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH,
DRA_IP_SERVICE_QOS_SWITCH,
DRA_PS_BE_STATE_TRANS_SWITCH,
DRA_PS_NON_BE_STATE_TRANS_SWITCH,
DRA_R99_DL_FLOW_CONTROL_SWITCH,
DRA_THROUGHPUT_DCCC_SWITCH,
DRA_VOICE_SAVE_CE_SWITCH,
DRA_VOICE_TTI_RECFG_SWITCH,
DRA_CSPS_NO_PERIOD_RETRY_SWITCH,
DRA_SMART_FAST_STATE_TRANS_SWITCH,
DRA_PCH_UE_SMART_P2D_SWITCH,
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH,
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H, DRA_F2U_SWITCH,
DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH
Unit: None
Actual Value Range: DRA_AQM_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH,
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_RES_BE_TTI_RECFG_SWITCH,
DRA_DCCC_SWITCH,
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH,
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_DCCC_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH,
DRA_IP_SERVICE_QOS_SWITCH,
DRA_PS_BE_STATE_TRANS_SWITCH,
DRA_PS_NON_BE_STATE_TRANS_SWITCH,
DRA_R99_DL_FLOW_CONTROL_SWITCH,
DRA_THROUGHPUT_DCCC_SWITCH,
DRA_VOICE_SAVE_CE_SWITCH,
DRA_VOICE_TTI_RECFG_SWITCH,
DRA_CSPS_NO_PERIOD_RETRY_SWITCH,
DRA_SMART_FAST_STATE_TRANS_SWITCH,
DRA_PCH_UE_SMART_P2D_SWITCH,
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH,
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H, DRA_F2U_SWITCH,
DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH
Default Value: DRA_AQM_SWITCH:0,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H:0,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH
:1,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH:
0,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH:
HSUPA 9. DRA_HSDPA_DL_FLOW_CONTROL_SWITCH:
Introduc When the switch is on, flow control is enabled for
tion HSDPA services in AM mode.
Package 10. DRA_HSDPA_STATE_TRANS_SWITCH: When
Active the switch is on, the status of the UE RRC that carrying
Queue HSDPA services can be changed to CELL_FACH at the
Manage RNC. If a PS BE service is carried over the HS-DSCH,
ment the switch PS_BE_STATE_TRANS_SWITCH should
(AQM) be on simultaneously. If a PS real-time service is carried
SRB over the HS-DSCH, the switch
over PS_NON_BE_STATE_TRANS_SWITCH should be
HSUPA on simultaneously.
HSDPA 11. DRA_HSUPA_DCCC_SWITCH: When the switch
Flow is on, the DCCC algorithm is used for HSUPA. The
Control DCCC switch must be also on before this switch takes
effect.
HSDPA
State 12. DRA_HSUPA_STATE_TRANS_SWITCH: When
Transiti the switch is on, the status of the UE RRC that carrying
on HSUPA services can be changed to CELL_FACH at the
RNC. If a PS BE service is carried over the E-DCH, the
HSUPA switch PS_BE_STATE_TRANS_SWITCH should be
DCCC on simultaneously. If a PS real-time service is carried
over the E-DCH, the switch
PS_NON_BE_STATE_TRANS_SWITCH should be
on simultaneously.
13. DRA_IP_SERVICE_QOS_SWITCH: Switch of
the algorithm for increasing the quality of subscribed
services. When this parameter is set to ON, the service
priority weight of the subscriber whose key parameters
(IP Address, IP Port, and IP Protocol Type) match the
specified ones can be adjusted. In this way, the QoS is
improved.
14. DRA_PS_BE_STATE_TRANS_SWITCH: When
this switch is turned on, UEs can be transited among the
CELL_DCH, CELL_FACH, CELL_PCH, and
URA_PCH states when they are processing PS BE
services.
15. DRA_PS_NON_BE_STATE_TRANS_SWITCH:
When this switch is turned on, UEs can be transited
between the CELL_DCH and CELL_FACH states
when they are processing real-time PS services.
16. DRA_R99_DL_FLOW_CONTROL_SWITCH:
Under a poor radio environment, the QoS of high speed
services drops considerably and the TX power is overly
high. In this case, the RNC can set restrictions on low
24.
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H: Whether to activate the coverage-based initial TTI
selection algorithm specific to BE services. When this
switch is turned on and conditions on 2 ms TTI specific
to BE services has been met, the RNC determines uplink
coverage wideness of specific cells based on the Ec/N0
values reported by UEs during RRC connection. If the
uplink coverage of the cells is weak, the RNC allocates
a 10 ms TTI to BE services as their initial TTI.
25. DRA_F2U_SWITCH: Whether to enable state
transition from CELL_FACH to URA_PCH.When this
switch is turned on, a UE can directly move from the
CELL_FACH to URA_PCH state. When this switch is
turned off, a UE must move from the CELL_FACH to
CELL_PCH and then to URA_PCH state.
26. DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH:
Whether to validate the initial selection function for
load-based happy bit delay condition. This function can
be used to improve the HSUPA throughput per UE.The
alternative happy bit delay condition (specified by the
AltHBDelaycnd parameter in the ADD
UTYPRABHSPA command) is selected when the
following conditions are met: This switch is turned on,
the HSUPA UE initially accesses the cell, and the cell
uplink load is not limited.The happy bit delay time
(specified by the HBDelaycnd parameter in the ADD
UTYPRABHSPA command) is selected when any of
the preceding three conditions is not met.
GUI Value Range: DRA_AQM_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH,
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_RES_BE_TTI_RECFG_SWITCH,
DRA_DCCC_SWITCH,
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH,
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_DCCC_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH,
DRA_IP_SERVICE_QOS_SWITCH,
DRA_PS_BE_STATE_TRANS_SWITCH,
DRA_PS_NON_BE_STATE_TRANS_SWITCH,
DRA_R99_DL_FLOW_CONTROL_SWITCH,
DRA_THROUGHPUT_DCCC_SWITCH,
DRA_VOICE_SAVE_CE_SWITCH,
DRA_VOICE_TTI_RECFG_SWITCH,
DRA_CSPS_NO_PERIOD_RETRY_SWITCH,
DRA_SMART_FAST_STATE_TRANS_SWITCH,
DRA_PCH_UE_SMART_P2D_SWITCH,
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH,
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H, DRA_F2U_SWITCH,
DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH
Unit: None
Actual Value Range: DRA_AQM_SWITCH,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH,
DRA_BASE_RES_BE_TTI_L2_OPT_SWITCH,
DRA_BASE_RES_BE_TTI_RECFG_SWITCH,
DRA_DCCC_SWITCH,
DRA_HSDPA_DL_FLOW_CONTROL_SWITCH,
DRA_HSDPA_STATE_TRANS_SWITCH,
DRA_HSUPA_DCCC_SWITCH,
DRA_HSUPA_STATE_TRANS_SWITCH,
DRA_IP_SERVICE_QOS_SWITCH,
DRA_PS_BE_STATE_TRANS_SWITCH,
DRA_PS_NON_BE_STATE_TRANS_SWITCH,
DRA_R99_DL_FLOW_CONTROL_SWITCH,
DRA_THROUGHPUT_DCCC_SWITCH,
DRA_VOICE_SAVE_CE_SWITCH,
DRA_VOICE_TTI_RECFG_SWITCH,
DRA_CSPS_NO_PERIOD_RETRY_SWITCH,
DRA_SMART_FAST_STATE_TRANS_SWITCH,
DRA_PCH_UE_SMART_P2D_SWITCH,
DRA_BASE_RES_BE_TTI_INIT_SEL_SWITCH,
DRA_BASE_COVER_BE_TTI_INIT_SEL_SWITC
H, DRA_F2U_SWITCH,
DRA_BASE_LOAD_HBD_INIT_SEL_SWITCH
Default Value: DRA_AQM_SWITCH:0,
DRA_BASE_ADM_CE_BE_TTI_L2_OPT_SWITC
H:0,
DRA_BASE_ADM_CE_BE_TTI_RECFG_SWITCH
:1,
DRA_BASE_COVER_BE_TTI_L2_OPT_SWITCH:
0,
DRA_BASE_COVER_BE_TTI_RECFG_SWITCH:
14. CMP_SINGLE_PTT_USE_DL_ENL2_SWITCH:
Whether to enable the DL Layer 2 Improvement feature
for E_PCH-incapable UEs processing only PTT
services. When this switch is turned on, the DL Layer 2
Improvement feature is enabled for E_PCH-incapable
UEs processing only PTT services. When this switch is
turned off, the DL Layer 2 Improvement feature is not
enabled for E_PCH-incapable UEs processing only
PTT services.
15.
CMP_F2D_RLC_ONESIDE_REBUILD_SWITCH:
Whether the RLC entity can be re-established in only
the uplink or downlink during the state transition from
CELL_FACH to CELL_DCH (F2D for short). When
this switch is turned off, the RLC entity must be re-
established in both uplink and downlink during the F2D
state transition. When this switch is turned on, the RLC
entity can be re-established in only the uplink or
downlink during the F2D state transition. For details,
see 3GPP TS 25.331.
16. CMP_DRD_SRBOVERH_SWITCH: Whether
signaling radio bearers (SRBs) can be switched over
from FACH or DCHs to HSPA channels during directed
retry. When this switch is turned off, SRBs can be
switched over from FACH or DCHs to HSPA channels
during directed retry. When this switch is turned on,
SRBs cannot be switched over from FACH or DCHs to
HSPA channels during directed retry. Note: This is a
general switch for prohibiting SRBs from being
switched over from FACH or DCHs to HSPA channels
during directed retry. To enable the prohibition to take
effect during RB setups, turn on the
CMP_RBSETUP_DRD_SRBOVERH_SWITCH
under the "CmpSwitch3" parameter. To enable the
prohibition to take effect during RB reconfiguration,
turn on the
CMP_RBCFG_DRD_SRBOVERH_SWITCH under
the "CmpSwitch3" parameter.
17. CMP_AMRC_FIXED_INITRATE_SWITCH:
Whether the RNC considers the cell congestion state
when determining the initial AMR rate mode during an
AMR service setup and whether to use the same rate
mode for the uplink and downlink during RB
reconfigurations for WB-AMR services in the case of
code congestion. When this switch is set to off, the RNC
considers the cell congestion state during an AMR
21.
CMP_MBDR_CALL_TYPE_OTHER_AS_AMR_S
WITCH: Whether a conversational service of a UE
complying with 3GPP Release 6 and later are allowed
for inter-RAT measurement-based directed retry
(MBDR) if CallType of the conversational service is
Other.
22.
CMP_SRNSR_WAMR_MODE_0_RESTORE_SWIT
CH: Whether the 0 kbit/s transport format is added on
the Iu interface during an incoming static relocation of
a WB-AMR speech service. When this switch is turned
off, the 0 kbit/s transport format is added on the Iu
interface if the Uu interface has the 0 kbit/s transport
format. When this switch is turned on, the 0 kbit/s
transport format is added on the Iu interface if both the
Uu interface and the RAB parameters in the
RELOCATION REQUEST message have the 0 kbit/s
transport format.
23. CMP_GSM_NCELL_BAND_1900M_SWITCH:
Whether the frequency band of an inter-RAT
neighboring cell must set to 1900 MHz. When this
switch is turned on, the frequency band in the following
messages is set to 1900 MHz: SIB11 and SIB12 system
information, inter-RAT measurement control, inter-
RAT handover, inter-RAT redirection, and inter-RAT
neighboring cell information sent back by the DRNC.
When this switch is turned off, the frequency band of
the inter-RAT neighboring cell is set as required.
24.
CMP_ACTIVESET_REPORT_WITH_SYN_SWITC
H: Whether the intra-frequency measurement reports of
UEs must contain synchronization information about
the cells in the active set. When this switch is turned off,
the intra-frequency measurement reports of UEs must
contain synchronization information about the cells in
the active set. When this switch is turned on, the intra-
frequency measurement reports of UEs do not need to
contain synchronization information about the cells in
the active set.
25. CMP_READSFN_IND_IN_SIB_SWITCH:
Whether the RNC carries an indication to read the
system frame number (SFN) of an intra-frequency
neighboring cell from SIB11 or SIB12. When this
switch is turned off, the RNC carries the indication not
to read the SFN of the intra-frequency neighboring cell
CMP_RELOCIN_IUUPVER_NOTCHG_SWITCH,
CMP_IUBR_DM_RTT_ALTERNATIVE_FMT_SWI
TCH, CMP_IUR_CMCF_SWITCH,
CMP_STTD_RL_ADD_SWITCH,
CMP_STTD_ASU_SWITCH,
CMP_RAB_DRD_ROLLBACK_PUNISH_SWITCH,
CMP_WBAMR_SUBFLOW_SWITCH,
CMP_IUR_CELLCAP_BITMAP_TRANSFORM_S
WITCH, CMP_MOCN_PLMN_SEL_SWITCH,
CMP_LOSSLESS_RELOC_RLCPDUSIZECHG_SW
ITCH,
CMP_CS_FIXED_RATE_WHEN_PS_EXIST_SWIT
CH, CMP_SRB_H_AMR_DRD_HHO_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_ENH_SWI
TCH,
CMP_SINGLE_PTT_USE_DL_ENL2_SWITCH,
CMP_F2D_RLC_ONESIDE_REBUILD_SWITCH,
CMP_DRD_SRBOVERH_SWITCH,
CMP_AMRC_FIXED_INITRATE_SWITCH,
CMP_DL_LOAD_BALANCE_SWITCH,
CMP_AMR_A_SUBFLOW_ZERO_BLOCK_SWIT
CH,
CMP_IUR_MULTI_RL_ADD_RETRY_SWITCH,
CMP_MBDR_CALL_TYPE_OTHER_AS_AMR_S
WITCH,
CMP_SRNSR_WAMR_MODE_0_RESTORE_SWIT
CH,
CMP_GSM_NCELL_BAND_1900M_SWITCH,
CMP_ACTIVESET_REPORT_WITH_SYN_SWITC
H,
CMP_READSFN_IND_IN_SIB_SWITCH,
CMP_UE_NOT_USE_DL_ENL2_EXIST_PTT_SWI
TCH,
CMP_RELOC_IN_FACH_DEL_DCH_SWITCH,
CMP_CELL_UPDATE_FACH_TRFFIC_MC_OPT,
CMP_MR_AGPS_MC_MSG_SEND_OPT_SWITCH
Default Value:
CMP_RELOCIN_IUUPVER_NOTCHG_SWITCH:
0,CMP_IUBR_DM_RTT_ALTERNATIVE_FMT_S
WITCH:0,CMP_IUR_CMCF_SWITCH:
0,CMP_STTD_RL_ADD_SWITCH:
0,CMP_STTD_ASU_SWITCH:
0,CMP_RAB_DRD_ROLLBACK_PUNISH_SWITC
14. CMP_SINGLE_PTT_USE_DL_ENL2_SWITCH:
Whether to enable the DL Layer 2 Improvement feature
for E_PCH-incapable UEs processing only PTT
services. When this switch is turned on, the DL Layer 2
Improvement feature is enabled for E_PCH-incapable
UEs processing only PTT services. When this switch is
turned off, the DL Layer 2 Improvement feature is not
enabled for E_PCH-incapable UEs processing only
PTT services.
15.
CMP_F2D_RLC_ONESIDE_REBUILD_SWITCH:
Whether the RLC entity can be re-established in only
the uplink or downlink during the state transition from
CELL_FACH to CELL_DCH (F2D for short). When
this switch is turned off, the RLC entity must be re-
established in both uplink and downlink during the F2D
state transition. When this switch is turned on, the RLC
entity can be re-established in only the uplink or
downlink during the F2D state transition. For details,
see 3GPP TS 25.331.
16. CMP_DRD_SRBOVERH_SWITCH: Whether
signaling radio bearers (SRBs) can be switched over
from FACH or DCHs to HSPA channels during directed
retry. When this switch is turned off, SRBs can be
switched over from FACH or DCHs to HSPA channels
during directed retry. When this switch is turned on,
SRBs cannot be switched over from FACH or DCHs to
HSPA channels during directed retry. Note: This is a
general switch for prohibiting SRBs from being
switched over from FACH or DCHs to HSPA channels
during directed retry. To enable the prohibition to take
effect during RB setups, turn on the
CMP_RBSETUP_DRD_SRBOVERH_SWITCH
under the "CmpSwitch3" parameter. To enable the
prohibition to take effect during RB reconfiguration,
turn on the
CMP_RBCFG_DRD_SRBOVERH_SWITCH under
the "CmpSwitch3" parameter.
17. CMP_AMRC_FIXED_INITRATE_SWITCH:
Whether the RNC considers the cell congestion state
when determining the initial AMR rate mode during an
AMR service setup and whether to use the same rate
mode for the uplink and downlink during RB
reconfigurations for WB-AMR services in the case of
code congestion. When this switch is set to off, the RNC
considers the cell congestion state during an AMR
21.
CMP_MBDR_CALL_TYPE_OTHER_AS_AMR_S
WITCH: Whether a conversational service of a UE
complying with 3GPP Release 6 and later are allowed
for inter-RAT measurement-based directed retry
(MBDR) if CallType of the conversational service is
Other.
22.
CMP_SRNSR_WAMR_MODE_0_RESTORE_SWIT
CH: Whether the 0 kbit/s transport format is added on
the Iu interface during an incoming static relocation of
a WB-AMR speech service. When this switch is turned
off, the 0 kbit/s transport format is added on the Iu
interface if the Uu interface has the 0 kbit/s transport
format. When this switch is turned on, the 0 kbit/s
transport format is added on the Iu interface if both the
Uu interface and the RAB parameters in the
RELOCATION REQUEST message have the 0 kbit/s
transport format.
23. CMP_GSM_NCELL_BAND_1900M_SWITCH:
Whether the frequency band of an inter-RAT
neighboring cell must set to 1900 MHz. When this
switch is turned on, the frequency band in the following
messages is set to 1900 MHz: SIB11 and SIB12 system
information, inter-RAT measurement control, inter-
RAT handover, inter-RAT redirection, and inter-RAT
neighboring cell information sent back by the DRNC.
When this switch is turned off, the frequency band of
the inter-RAT neighboring cell is set as required.
24.
CMP_ACTIVESET_REPORT_WITH_SYN_SWITC
H: Whether the intra-frequency measurement reports of
UEs must contain synchronization information about
the cells in the active set. When this switch is turned off,
the intra-frequency measurement reports of UEs must
contain synchronization information about the cells in
the active set. When this switch is turned on, the intra-
frequency measurement reports of UEs do not need to
contain synchronization information about the cells in
the active set.
25. CMP_READSFN_IND_IN_SIB_SWITCH:
Whether the RNC carries an indication to read the
system frame number (SFN) of an intra-frequency
neighboring cell from SIB11 or SIB12. When this
switch is turned off, the RNC carries the indication not
to read the SFN of the intra-frequency neighboring cell
CMP_RELOCIN_IUUPVER_NOTCHG_SWITCH,
CMP_IUBR_DM_RTT_ALTERNATIVE_FMT_SWI
TCH, CMP_IUR_CMCF_SWITCH,
CMP_STTD_RL_ADD_SWITCH,
CMP_STTD_ASU_SWITCH,
CMP_RAB_DRD_ROLLBACK_PUNISH_SWITCH,
CMP_WBAMR_SUBFLOW_SWITCH,
CMP_IUR_CELLCAP_BITMAP_TRANSFORM_S
WITCH, CMP_MOCN_PLMN_SEL_SWITCH,
CMP_LOSSLESS_RELOC_RLCPDUSIZECHG_SW
ITCH,
CMP_CS_FIXED_RATE_WHEN_PS_EXIST_SWIT
CH, CMP_SRB_H_AMR_DRD_HHO_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_ENH_SWI
TCH,
CMP_SINGLE_PTT_USE_DL_ENL2_SWITCH,
CMP_F2D_RLC_ONESIDE_REBUILD_SWITCH,
CMP_DRD_SRBOVERH_SWITCH,
CMP_AMRC_FIXED_INITRATE_SWITCH,
CMP_DL_LOAD_BALANCE_SWITCH,
CMP_AMR_A_SUBFLOW_ZERO_BLOCK_SWIT
CH,
CMP_IUR_MULTI_RL_ADD_RETRY_SWITCH,
CMP_MBDR_CALL_TYPE_OTHER_AS_AMR_S
WITCH,
CMP_SRNSR_WAMR_MODE_0_RESTORE_SWIT
CH,
CMP_GSM_NCELL_BAND_1900M_SWITCH,
CMP_ACTIVESET_REPORT_WITH_SYN_SWITC
H,
CMP_READSFN_IND_IN_SIB_SWITCH,
CMP_UE_NOT_USE_DL_ENL2_EXIST_PTT_SWI
TCH,
CMP_RELOC_IN_FACH_DEL_DCH_SWITCH,
CMP_CELL_UPDATE_FACH_TRFFIC_MC_OPT,
CMP_MR_AGPS_MC_MSG_SEND_OPT_SWITCH
Default Value:
CMP_RELOCIN_IUUPVER_NOTCHG_SWITCH:
0,CMP_IUBR_DM_RTT_ALTERNATIVE_FMT_S
WITCH:0,CMP_IUR_CMCF_SWITCH:
0,CMP_STTD_RL_ADD_SWITCH:
0,CMP_STTD_ASU_SWITCH:
0,CMP_RAB_DRD_ROLLBACK_PUNISH_SWITC
9 Counters
10 Glossary
11 Reference Documents