ZTE UMTS UR15 F-DPCH & SRB Over HSDPA Feature Guide

F-DPCH & SRB over HSDPA
Feature Guide

Version Date Author Reviewer Revision History
Compared with UR14, there is no change

V1.0 2016/4/15 Cai Yaofang Ma Yongchao
except software version.
© 2016 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 1

TABLE OF CONTENTS
1 Feature Attribute ............................................................................................... 5
2 Overview ............................................................................................................ 5
2.1 Feature Introduction ............................................................................................. 5
2.1.1 ZWF23-01-041 F-DPCH & SRB over HSDPA ...................................................... 5
2.2 License Control .................................................................................................... 6
2.3 Correlation with Other Features ........................................................................... 6
3 Technical Descriptions ..................................................................................... 7

3.1 Principle of Fractional Dedicated Physical Channel ............................................. 7
3.2 Principle of SRB over HSDPA .............................................................................. 9
3.3 Requirements for Utilization of F-DPCH and SRB over HSDPA ......................... 10
3.4 Multiplexing Method of F-DPCH ......................................................................... 11
3.5 Dynamic Radio Bearer Control for F-DPCH (Including SRB over HSDPA)......... 12
3.5.1 Signaling Channel Allocation in the RRC Phase ................................................ 12
3.5.2 Signaling Channel Allocation in the RAB Phase ................................................. 12
3.5.3 Transition of F-DPCH ......................................................................................... 13
3.6 Code Resource Allocation for F-DPCH .............................................................. 14
3.6.1 Channelization Code Allocation for F-DPCH ...................................................... 14
3.6.2 Scrambling Code Allocation for F-DPCH............................................................ 14
3.7 Power Control for F-DPCH................................................................................. 14
3.7.1 Initial Downlink Transmission Power for F-DPCH............................................... 14
3.7.2 F-DPCH Quality Target Control.......................................................................... 15
3.8 Admission Control for F-DPCH .......................................................................... 15
3.9 Congestion Control for F-DPCH ......................................................................... 16
3.10 Overload Control for F-DPCH ............................................................................ 16
3.11 Mobility Management for F-DPCH ..................................................................... 16
3.12 Optimization for UE Compatibility – Control Timing Adjustment of 256 Chips in
F-DPCH ............................................................................................................. 17
4 Parameters....................................................................................................... 18
5 Related Counters and Alarms ........................................................................ 22

5.1 Related Counters ............................................................................................... 22
5.2 Related Alarms .................................................................................................. 22
6 Engineering Guide .......................................................................................... 22

6.1 Application Scenario .......................................................................................... 22
6.2 Feature Activation Procedure ............................................................................. 23
6.3 Feature Validation Procedure............................................................................. 28

6.4 Feature Deactivation Procedure......................................................................... 29

6.5 Impact on the Network ....................................................................................... 29
7 Abbreviation .................................................................................................... 30
8 References ....................................................................................................... 30

FIGURES
Figure 6-1 Parameters for HSPA Configuration .................................................................23
Figure 6-2 Parameters configuration interface 2 ................................................................25
Figure 6-3 Parameter Configuration Interface 3 .................................................................26
Figure 6-6 Parameters Configuration Interface 6 ...............................................................27
Figure 6-7 Parameters Configuration Interface 7 ...............................................................28
TABLES
Table 2-1 License Control List ............................................................................................ 6
Table 3-1 F-DPCH Fields .................................................................................................... 8
Table 3-2 Scenarios for SRNC/DRNC adding a RL............................................................15
Table 4-1 Parameter List ...................................................................................................18
Table 5-1 Counter List .......................................................................................................22

1 Feature Attribute
RNC Version: [ZXWR RNC V3.15.10.20/ZXUR 9000 V4.15.10.20]
Node B Version: [ZXSDR V4.15.10]
Attribute: [Optional]
Related Network Element:

NE Name Related or Not Special Requirement
UE √ F-DPCH should be supported by UE.
Node B √ F-DPCH should be supported by Node B.
RNC √ None.
iTC - None.
MSC - None.
MGW - None.
SGSN - None.
GGSN - None.
HLR - None.
“√”: involved, “-“: not involved.
2 Overview
2.1 Feature Introduction
2.1.1 ZWF23-01-041 F-DPCH & SRB over HSDPA
ZTE’s UMTS RAN supports F-DPCH (Fractional DPCH) in 3GPP Rel-6. F-DPCH does
not carry any service data or signaling except the uplink inner loop power control
information (TPC commands). F-DPCH uses SF 256 channelization codes. The TPC
command per slot per user is 2 bits, and every slot of the SF 256 channel can transmit 20
bits data in a frame, which means that at most 10 users can share one F-DPCH. When
F-DPCH replaces the associated DPCH for HSDPA users, the consumption of downlink

channelization codes for the associated DPCH is reduced, so more channelization codes
are available to HS-DSCH for more HSDPA users in a cell. The cell throughout is
improved accordingly.
As a result of F-DPCH carrying neither service data nor signaling, when F-DPCH
replaces the associated DPCH, RRC signaling and NAS layer signaling need to be
carried by HS-DSCH. ZTE’s UMTS RAN supports SRB over HS-DSCH, and all SRBs are
multiplexed to one MAC-d Flow. Proper QoS parameters are configured for SRB, for
example, ARP and SPI are set to the highest priority; Node B scheduler ensures SRB
transmission in a similar way as GBR; the reliability of the RRC signaling can be ensured.
This feature offers RRC signaling and NAS layer signaling transmission over HS-PDSCH.
It can speed up the signaling flow in the Uu interface, and reduce the call delay of
subsequent service establishment.
2.2 License Control
Table 2-1 License Control List
License Configured Sales

Feature ID Feature Name
Control Item NE Unit
ZWF23-01-041 WCDMA F-DPCH &

Cell Number RNC CELL
SRB over HSDPA
2.3 Correlation with Other Features
1. Dependency
ZWF23-01-A HSDPA Introduction Package
2. Mutual exclusion
None
3. Affected Features

None
3 Technical Descriptions
The function of F-DPCH is to share the given codes among users who only use the
HSDPA services (meaning there is no downlink DCH) to achieve more efficient
management of the code resources.
This feature is mandatory in 3GPP Rel-6. It is specified in 3GPP 25.306 (version 6.6.0)
that if a UE supports HS-PDSCH then this UE should also support F-DPCH. However the
compatibility of F-DPCH is not so good in the early stage of 3GPP Rel-6. To differentiate
the capacity of UEs, it is further specified in 3GPP 25.331 that the Support for F-DPCH
IE should be set to TRUE when F-DPCH is completely supported by the UE and
indicated in the RRC CONNECTION REQUEST, RRC CONNECTION SETUP
COMPLETE, UE CAPABILITY INFORMATION or INTER RAT HANDOVER INFO
message. If this IE does not exist, it indicates that F-DPCH is not completely supported.
This feature guide is based on the report of Support for F-DPCH to determine whether
F-DPCH is supported by a UE. If this IE is reported in the RRC CONNECTION
REQUEST message, F-DPCH can be established in the RRC phase.
The Node B indicates whether a cell supports F-DPCH by using the F-DPCH Capability
IE in the AUDIT RESPONSE message.
3.1 Principle of Fractional Dedicated Physical Channel
F-DPCH is introduced by 3GPP Rel-6 to replace the associated DPCH for an HSDPA
user. An F-DPCH only reserves the TPC field of the associated DPCH for power control
for uplink DPCCH. The following figure shows the F-DPCH frame structure. The
structure for DPCH is also illustrated.
Figure 3-1 Frame Structure of F-DPCH

The following fixed slot format is used for F-DPCH in 3GPP Rel-6.
Table 3-1 F-DPCH Fields
Channel Channel SF Bits/ Slot NOFF1 NTPC NOFF2

Bit Rate Symbol Bits/Slot Bits/Slot Bits/Slot
(kbps) Rate
(ksps)
3 1.5 256 20 2 2 16
As shown in the following figure, if the downlink timings of these channels are selected
properly, the code dimension is not necessary to distinguish UEs, which means that UEs
can use the same SF 256 channelization codes for an F-DPCH channel. Three UEs are
selected for illustrative purposes. Further study shows that the downlink channelization
code is used more efficiently when only TPC bits are transmitted without the pilot bits,
while minimizing impacts on the reliability of the uplink power control. Up to 10 UEs can
be multiplexed on a single code, see Figure 3-2.
Figure 3-2 Multiplex on an F-DPCH Channel

The timing relationship between the F-DPCH timing and the P-CCPCH frame timing is
similar to that between the downlink DPCH and the P-CCPCH. The offset is a multiple of
256 chips, for example, τF-DPCH,p = Tp * 256 chip, Tp є {0, 1, …, 149}. τF-DPCH,p denotes
F-DPCH frame offset.
The timing relationship between the F-DPCH timing and the uplink DPCCH is consistent
with that between the downlink DPCH and the uplink DPCCH: namely, that T0 is a
constant defined to be 1024 chips.
3.2 Principle of SRB over HSDPA
When F-DPCH is used, SRBs in downlink need to be carried on HSDPA.
The high-speed characteristic of HSDPA speeds up the signaling flow over the Uu
interface and thus reduces the call delay in the subsequent service setup when the SRBs
are carried by HSDPA. In addition, the downlink channelization codes can be saved
because of the multiplexing on an F-DPCH.
When the SRBs are carried on HSDPA, the DCCH is mapped to the HS-DSCH, the
SRBs are carried by an independent MAC-d Flow, and four SRBs are multiplexed to one

MAC-d flow. On the RNC, the appropriate MAC-d flow parameters are configured
according to the QoS of the SRBs. The parameters are as follows:
 The Allocation/Retention Priority (ARP) enjoys the highest priority.
 The Scheduling Priority Indicator (SPI) enjoys the highest priority.
 The MAC-hs guaranteed bit rate is configured.
 Discard Timer is configured to 4 s. When the HSDPA scheduler schedules the RRC
signaling on the Node B, the reliability of the RRC signaling is ensured.
3.3 Requirements for Utilization of F-DPCH and SRB

over HSDPA
When the following conditions are met, the SRBs can be carried on HS-DSCH and an
associated F-DPCH is established.
 The UHspa.RncFdpchSupInd parameter for F-DPCH on the RNC level is set to

Supported.
 The UUtranCellFDD.fDpchSuptInd parameter for F-DPCH on the cell level is set to

Supported.
 The Node B indicates that the cell supports F-DPCH.
 The UE indicates that it supports F-DPCH.
 There is no DCH in the downlink.
Note:
When the SRBs are carried on HSDPA, if there is a service carried on HSUPA, the
constraint condition of SRBs carried on HSUPA is removed from version UR14.10.11.
For details about SRBs carried on HSUPA, refer to the ZTE UMTS SRB over HSUPA
Feature Guide.

If there are multiple radio links in an active set, all the cells in the active set must support
F-DPCH.
For a neighboring cell of the inter-RNC, its capacity for F-DPCH is configured by
UExternalUtranCellFDD.fdpchSuptInd.
3.4 Multiplexing Method of F-DPCH
The SF of the channelization code for an F-DPCH is fixed to 256. In the following
scenarios:
 Establish the first radio link for a UE.
 Establish a new radio link for a UE during the soft handover.
 Establish a new radio link for a UE during the hard handover.
 The DPCH channel is transferred to the F-DPCH channel.
If when the conditions for using F-DPCH are met (refer to 3.5.2 Signaling Channel
Allocation in the RAB), and there is an idle TPC position available on an allocated
channelization code, the channelization code is multiplexed.
If when the conditions for using F-DPCH are met, and there is no available
channelization code for multiplexing or the idle TPC positions available cannot meet the
timing conditions, the RNC allocates an unused channelization code for F-DPCH.
Multiplexing on the same channelization code for an F-DPCH is achieved through

properly choosing the downlink timings for UEs. It means that the TPC bits for different
UEs on the same channelization code for an F-DPCH cannot overlap in terms of time.
The timing is set by the RNC through the chip offset in the Iub interface and the F-DPCH
frame offset in the Uu interface.

3.5 Dynamic Radio Bearer Control for F-DPCH

(Including SRB over HSDPA)
The use of F-DPCH involves the SRBs over HSDPA. Therefore, the description of SRB
over HSDPA is introduced with the description of the usage of F-DPCH in RRC and RAB
phase.
In addition, because the transition between DPCH and F-DPCH involves judging the
conditions for using F-DPCH, the transition of F-DPCH is also described in this chapter.
3.5.1 Signaling Channel Allocation in the RRC Phase
If the following conditions are met in the RRC phase, the SRBs of the UE can be carried
on HS-DSCH and an associated F-DPCH is established.
 The URncFunction.InitRrcOnDch parameter is set to 7: Forced to HSPA or 8: Not

Forced,Using HSPA Signalling on CELL_DCH state.
 The conditions for using F-DPCH are satisfied. For details, refer to 3.3
Requirements for Utilization of F-DPCH and SRB over HSDPA.
If either of the above mentioned conditions is not met or the SRB fails to be established
on HSPA, there will be an attempt to establish the SRB on the DCH with a rate of 3.4
kbps.
3.5.2 Signaling Channel Allocation in the RAB Phase
When the SRBs are carried on HS-DSCH in the RRC phase, if there is no DCH in the
downlink in the RAB phase, the SRBs on HS-DSCH and F-DPCH are maintained. If the
DCH is needed in the RAB, F-DPCH is transferred to DPCH. For details, refer to 3.5.3
Transition of F-DPCH.
When the SRBs are carried on DCH in the RRC phase, if the following conditions are met
in the RAB phase, the SRBs of the UE can be carried on HS-DSCH and an associated
F-DPCH is established.

 The conditions for using F-DPCH are satisfied. For details, refer to 3.3
Requirements for Utilization of F-DPCH and SRB over HSDPA;
 If the UHspa.Event1fHsInd parameter is set to 1: True and the reporting criteria for
event 1F is configured to the UE (namely measurement control message of event
1F is sent to the UE), event 1F needs to be considered and there should be no
event 1F reported which marks the bad channel quality. Otherwise, there is no need
to consider the channel quality measured by event 1F.
For the other scenarios when the HS-DSCH serving cell changes (including
intra-frequency and inter-frequency), or transition from non-HS-DSCH to HS-DSCH
triggered by the traffic volume in a cell, or relocation into the RNC, the conditions for
using F-DPCH are the same as those for signaling channel allocation in the RAB phase.
Note:
Event 1f indicates that the quality of a primary CPICH becomes worse than an absolute
threshold during a period. For details, refer to the ZTE UMTS Handover Control Feature
Guide.
3.5.3 Transition of F-DPCH
The transition between DPCH and F-DPCH is based on channel transition for the
service.
If the channel of a service is transferred, the transition between DPCH and F-DPCH is
triggered as follows:
 If F-DPCH is configured to a UE and a new sevice of the UE needs to be

established on DCH, the transition from F-DPCH to DPCH is triggered.
 If the service is switched from DCH to HS-DSCH and the conditions for using
F-DPCH are satisfied, the transition from D-PCH to F-DPCH is triggered.
Note:
For the conditions for using F-DPCH, refer to 3.5.2 Signaling Channel Allocation in the
RAB.

3.6 Code Resource Allocation for F-DPCH
Code resource allocation for F-DPCH is only related to the allocation of a channelization
code and a scrambling code for a newly established F-DPCH.
3.6.1 Channelization Code Allocation for F-DPCH
A channelization code needs to be allocated by the RNC when an F-DPCH is established.

The method is the same as that for the downlink DPCH, namely selecting channelization
codes with the smallest code number in the allocable downlink CCs with the required SF.
For details, refer to the ZTE UMTS Code Resource Allocation Feature Guide.
3.6.2 Scrambling Code Allocation for F-DPCH
F-DPCH uses the same scrambling codes as their phase reference channel (P-CPICH or
S-CPICH).
3.7 Power Control for F-DPCH
The characteristic of the F-DPCH field is the same as that of the DPCH control field. So
the method for configuring the power for F-DPCH uses the same method for configuring
the DPCH service type. The service type for the F-DPCH TPC field is regarded as a
service with a rate of 1.5 kbps (set by the parameter USrvPc.srvType = 7).
The RNC configures the power control parameters for the Node B and the UE. The
quality of the radio links is controlled by these parameters, which further affects capacity
and the user experience.
3.7.1 Initial Downlink Transmission Power for F-DPCH
The method for calculating the initial downlink transmission power of an F-DPCH is the
same as that of a downlink DPCH. For details, refer to the ZTE UMTS Power Control
Feature Guide.

In addition, when the initial downlink transmission power is calculated, PowerOffset is

introduced for different scenarios. PowerOffset is configured by the corresponding
parameters in the following table.
Table 3-2 Scenarios for SRNC/DRNC adding a RL
The NE Name for

Scenarios PowerOffset
Adding a RL
SRNC Call setup UCelInfoFDD.pOSetup
SRNC Soft or softer handover
DRNC Add a RL for F-DPCH

UCelInfoFDD.pOSoftHO
transmission and there is no
service on this RL
SRNC Hard handover for F-DPCH
DRNC Add a RL with the SRB on the UCelInfoFDD.pOSrbHardHO

DPDCH
3.7.2 F-DPCH Quality Target Control
TPC control information instead of service data and signaling is carried on F-DPCH. So
the outer loop power control based on the BLER quality criteria is not applicable, with the
closed loop power control based on the quality target of downlink TPC command error
rate for F-DPCH being used instead. The RNC sets a quality target for F-DPCH. The UE
autonomously sets an SIR target value and adjusts it in order to achieve the same quality
as the quality target set by the RNC. Thus the reliability of the TPC field is guaranteed.
If F-DPCH and E-DCH are used, the E-AGCH power offset, E-RGCH power offset and
E-HICH power offset are related to the power of F-DPCH TPC field, and the values of
these power offset are obtained from the record indexed by the service type of F-DPCH
(USrvPc.srvType = 7).
3.8 Admission Control for F-DPCH
There is no impact on the admission control for HSDPA services after F-DPCH is
introduced. As a single F-DPCH has multiple UEs, and the CE (Channel Element) for

F-DPCH/E-FDPCH is reserved in Node B, only the admission control of downlink

channelization code is involved.
Admission control of downlink channelization code for F-DPCH is the same as that for
DPCH. For details, refer to the ZTE UMTS Admission Control Feature Guide.
3.9 Congestion Control for F-DPCH
Channelization code allocation for F-DPCH may fail when a channelization code is
requested. Because the function of the channelization code for F-DPCH is the same as
that for the associated DPCH in the HSDPA service, the process for the congestion is the
same as that of the associated DPCH in the HSDPA service (refer to the ZTE UMTS
HSDPA Introduction Feature Guide for details). The cause for the failure of
channelization code allocation for F-DPCH is recorded as Downlink DCH no code.
When a pre-emption is triggered by an F-DPCH user, the selection of the pre-empted

users is the same as that in the pre-emption triggered by a DPCH user.
In case of congestion in channelization codes, the users using F-DPCH cannot be

pre-empted by the DPCH users.
3.10 Overload Control for F-DPCH
F-DPCH is equivalent to the associated DPCH that only carries signaling for the HSDPA
service. The overload control method for this service is the same as that for the
associated DPCH. For details, refer to the ZTE UMTS HSDPA Introduction Feature
Guide.
3.11 Mobility Management for F-DPCH
When the soft handover is triggered and a new radio link needs to be added into the
active set, if F-DPCH is used in the source cell, and the conditions for using F-DPCH are
not met in the target cell, two strategies: channel transition from F-DPCH to DPCH and
then soft handover, or hard handover with channel transition from F-DPCH to DPCH until

event 1D is reported, which of them is performed is controlled by the parameter

UExtCelInfoFDD.h2LSoHoSw. For details, refer to “3.2.8.5 Soft Handover between Cells
with Different Capabilities” of ZTE UMTS Handover Control Feature Guide.
When the serving HS-DSCH cell changes, if F-DPCH is used in the source cell, and the
conditions for using F-DPCH are not met in the target cell, the transition from F-DPCH to
DPCH is triggered.
When the serving HS-DSCH cell changes, if the DPCH is used in the source cell, and the
conditions for using F-DPCH are met in all the cells in the active set, the transition from
DPCH to F-DPCH is triggered.
For a hard handover or relocation into the RNC, if the target cell meets the conditions for
using F-DPCH, an F-DPCH is allocated.
Note:
For the conditions for using F-DPCH, refer to 3.5.2 Signaling Channel Allocation in the
RAB.
3.12 Optimization for UE Compatibility – Control Timing

Adjustment of 256 Chips in F-DPCH
During the radio link reconfiguration for channel transition from the DPCH to F-DPCH
(not E-FDPCH), 256 chips can be adjusted for the channelization code multiplexing (DL
DPCH Timing Adjustment is indicated over the Iub interface). But there may be an IOT
compatibility issue for some UEs in chip adjustment (for example, CELL UPDATE
occurs). To avoid this kind of IOT issue, the UHspa.chip256adjust parameter is added to
stop chip adjustment during the reconfiguration mentioned above in version UR13.10.11.
If there is a UE IOT issue due to the time advance or delay in the radio link
reconfiguration for the channel transition from DPCH to F-DPCH, set the
UHspa.chip256adjust parameter to 0: No Adjust to avoid the IOT issue. Otherwise, set
the UHspa.chip256adjust parameter to 1: Adjust to increase the channelization code
utilization in the downlink.

4 Parameters
Table 4-1 Parameter List
Recom
Paramete
GUI Name Parameter Description Range Unit Default mendat
r Name
ion
RNC 0: Not
UHspa.rnc This parameter indicates 0: Not 1:
F-DPCH Supported
FdpchSup whether the RNC supports N/A Support Support
Support 1:
Ind the F-DPCH or not. ed ed
Indicator Supported
Cell 0: Not
UUtranCel This parameter indicates 0: Not 1:
F-DPCH Supported
lFDD.fDpc whether the cell supports N/A Support Support
Support 1:
hSuptInd F-DPCH. ed ed
Indicator Supported
UExternal 0:
F-DPCH This parameter indicates 1: Not 0:
UtranCell Supported
Support whether the neighboring cell N/A Support Support
FDD.fdpc 1: Not
Indicator supports F-DPCH. ed ed
hSuptInd Supported
This parameter indicates the

TPC
F-DPCH TPC command
UHspa.tpc Command (0.01..0.1)
error rate target, and is used N/A 0.05 0.05
ErrTarget Error Rate step 0.01
to adjust the SIR target of
Target
the F-DPCH.

type of sub-services. It is
used to number each
sub-service.0..5 are used for
signaling services and 7 (for 7 (for
USrvPc.sr Sub-service
6..250 are used for single 0..65534 N/A F-DPC F-DPC
vType Type
services. Odd numbers H) H)
are configured for downlink
services and even numbers
are configured for uplink
services.

Indicator for
Whether to
Judge
This parameter indicates
UHspa.ev Event 1F
whether to judge event 1F 0: False
ent1fHsIn Condition N/A 0: False 0: False
condition when the service 1: True
d When the
is setup on HSPA.
Service is
Setup on
HSPA

0: Forced
to
CELL_DC
H and
Using
DCH/DCH
Low Rate
Signalling
1: Forced
to
CELL_DC
H and
Using
DCH/DCH
with 13.6k
Signalling
2: Forced
to FACH
3: Not
Forced,
Using
DCH/DCH
with
DCH/DCH
Low Rate
Signalling
on
Cell_DCH Forced Forced
State to to
4: Not CELL_ CELL_
Type of
Forced, DCH DCH
Transport This parameter indicates the
URncFunc Using and and
Channel for type of transport channel
tion.initRrc DCH/DCH N/A Using Using
Initial RRC and signaling rate for initial
OnDch with 13.6k DCH/D DCH/D
Connection RRC connection setup.
Signalling CH with CH with
Setup
on 13.6k 13.6k
Cell_DCH Signalli Signalli
State ng ng
5: Forced
to
CELL_DC
H and
Using
DCH/DCH
ZTE Confidential Proprietary with 27.2k 20
Signalling
6: Not
Forced,
Power
Offset for
Downlink This parameter indicates the
UCelInfoF DPCH power offset for calculating
-50..50,
DD.pOSet Initial the downlink DPCH initial dB 0dB 0dB
step 0.1
up Power power during the RAB/SRB
Calculation establishment.
when Call
Setup
Power
Offset for
Downlink
DPCH
UCelInfoF power offset for calculating
Initial -50..50,
DD.pOSof the downlink DPCH initial dB 0dB 0dB
Power step 0.1
tHO power during the soft or
Calculation
softer handover.
when Soft
or Softer
Handover
Power
Offset for
power offset for calculating
Downlink
the downlink DPCH initial
DPCH
UCelInfoF power during the SRB hard
Initial -50..50,
DD.pOSrb handover on the dB 4dB 4dB
Power step 0.1
HardHO DPDCH .During the
Calculation
F-DPCH hard handover, this
when SRB
parameter is also used to
Hard
calculate the transmit power.
Handover
This parameter indicates

whether DL DPCH timing
adjustment (a timing
Switch
advance or delay of 256
Used to
UHspa.chi chips) is allowed during 0: No
control DL 0: No
p256adjus radio link reconfiguration Adjust N/A N/A
DPCH Adjust
t from DPCH to F-DPCH or 1: Adjust
Timing
TDM-based E-DCH
Adjustment
scheduling for
reconfiguration to HSUPA
2ms TTI.

5 Related Counters and Alarms
5.1 Related Counters
Table 5-1 Counter List
Counter ID Name
C310424276 Summation Number of Code Node Used, SF=256
C310424283~ Distribution Of Code Node Occupied, SF=256

C310424314
C310032022 Number of F-DPCH users in the best cell
C310032023 Average Number of F-DPCH users in the best cell
C310032026 Number of F-DPCH users in the non best cell
C310032027 Average Number of F-DPCH users in the non best cell
C310030436 Number of including only HSDPA users in the best cell
C310030448 Max Number of including only HSDPA users in the best cell
C310030460 Average Number of including only HSDPA users in the best

cell
5.2 Related Alarms
This feature has no related alarm.
6 Engineering Guide
6.1 Application Scenario
1. Scenario for Enabling F-DPCH
One F-DPCH channel can be used by up to 10 users in time-multiplex mode and thus the
downlink channelization code resources are saved. Therefore, the number of

HS-DPSCHs is increased, and the average throughput and the user experience are
improved. So you are recommended to activate this feature after this feature is deployed.
2. Precautions for Enabling F-DPCH
Some UEs may have compatibility issues. Therefore, this feature should be activated in
multiple cells first. If UEs and this feature are compatible, this feature can be activated in
the entire network. Otherwise it cannot be deployed in the network.
6.2 Feature Activation Procedure
The purpose of this chapter is just to guide the reader how to find the GUI location of the
parameters which are related to the deployment of this feature. The values indicated by
the captures possibly are not the real value to configure. Please refer to the last column
of table in chapter 4 for the practical configuration value.
In the configuration resource tree window, open the [IModify Area->Managed

Element->UMTS Logical Function Configuration->Service configuration->Hspa
Configuration] interface and set the parameter “RNC F-DPCH Support Indicator”, “TPC
Command Error Rate Target”, ”Indicator for Whether to Judge Event 1F Condition When
the Service is Setup on HSPA”, as shown in Figure 6-1
Figure 6-1 Parameters for HSPA Configuration


In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration->UTRAN Cell] interface and set the parameter
“Cell F-DPCH Support Indicator”, as shown in Figure 6-2.
Figure 6-2 Parameters configuration interface 2
In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration-> External Resource Configuration->External RNC
Function->External UTRAN Cell] interface and set the parameter “F-DPCH Support
Indicator”, as shown in Figure 6-3.

Figure 6-3 Parameter Configuration Interface 3
In the configuration resource tree window, open the [Modify Area->Managed

Element->UMTS Logical Function Configuration->Service configuration-> Service
Function->Power Control Profile Related to Service->Power Control Related to Service]
interface and set the parameter ”Sub-Service Type”, as shown in Figure 6-4.


Element->UMTS Logical Function Configuration] interface and set the parameter” Type
of Transport Channel for Initial RRC Connection Setup” as shown in Figure 6-5.

Element->UMTS Logical Function Configuration] interface and set the parameter” Power
Offset for Downlink DPCH Initial Power Calculation when Call Setup”, “Power Offset for
Downlink DPCH Initial Power Calculation when Soft or Softer Handover”,” Power Offset
for Downlink DPCH Initial Power Calculation when SRB Hard Handover “as shown in
Figure 6-6.
Figure 6-6 Parameters Configuration Interface 6


Element->UMTS Logical Function Configuration->Service configuration->Hspa
Configuration] interface and set the parameter “Switch Used to control DL DPCH Timing
Adjustment “as shown in Figure 6-7.
Figure 6-7 Parameters Configuration Interface 7
6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item F-DPCH&SRB over HSDPA

Test Item F-DPCH&SRB over HSDPA
1. The WCDMA system is ready.
2. Cell 1 supports HSUPA, HSDPA and DCH.
Prerequisit 3. UE 1 camps on Cell 1 in Idle mode.

e
4. UE 1 supports F-DPCH.
5. UE 1 has subscribed to an interactive or background service, and MBR =
UL2 Mbps/ DL2 Mbps.
1. UE 1 activates a PS service in Cell 1 and starts FTP downloading. The
service is established on EDCH/ HS-DSCH.

Steps
2. Maintain the service for 90 s.
3. Deactivate the PDP.
Expected
In step1, the SRB of the service is established on HSDPA.
Result
6.4 Feature Deactivation Procedure
Table 6-2 RNC Parameter List 2
Managed Object. logic Default Deactivation

GUI Name
name Value Value
UUtranCellFDD.fDpchS Cell F-DPCH Support

0:Off 0:Off
uptInd Indicator
RNC F-DPCH Support

UHspa.rncFdpchSupInd 0:Off 0:Off
Indicator
For a description and configuration of the above parameters, refer to section 6.2.
6.5 Impact on the Network
1. Equipment Performance Influence

None
2. Network KPI
The benefits for enabling F-DPCH are as follows:
One F-DPCH channel can be used by up to 10 users in time-multiplex mode and thus the
downlink channelization code resources are saved. Therefore, the average throughput
and the user experience are improved.
The possible negative effects are as follows:
 As the downlink Pilot of DPCCH is removed and the mechanism for the reliability of
TPC commands between F-DPCH and DPCH is different, monitoring whether the
RTWP is raised in implementation is needed.
 Because some UEs may have compatibility issues, the following KPIs may
deteriorate: ratio of successful CS RAB establishment (caused by first the
establishment a PS service and then a CS service simultaneously), ratio of
successful PS RAB establishment and ratio of PS call drop.
7 Abbreviation
Abbreviation Full Name
BLER Block Error Ratio
F-DPCH Fractional Dedicated Physical Channel
P-CCPCH Primary Common Control Physical Channel
P-CPICH Primary CPICH
SRB Signalling Radio Bearer
TPC Transmit Power Control
8 References
[1] 3GPP TR 25899-610
[2] ZTE UMTS Handover Control Feature Guide

[3] ZTE UMTS Code Resource Allocation Feature Guide
[4] ZTE UMTS Power Control Feature Guide
[5] ZTE UMTS Admission Control Feature Guide
[6] ZTE UMTS HSDPA Introduction Feature Guide
[7] ZXUR 9000 UMTS(V4.15.10.20)Radio Network Controller Radio Parameter

Reference
[8] ZXUR 9000 UMTS(V4.15.10.20)Radio Network Controller Ground Parameter

Reference
[9] ZXUR 9000 UMTS(V4.15.10.20)Radio Network Controller Performance Counter

Reference
[10] ZXWR RNC(V3.15.10.20)Radio Network Controller Radio Parameter Reference
[11] ZXWR RNC(V3.15.10.20)Radio Network Controller Ground Parameter Reference
[12] ZXWR RNC(V3.15.10.20)Radio Network Controller Performance Counter Reference

ZTE UMTS UR15 F-DPCH & SRB Over HSDPA Feature Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE UMTS UR15 F-DPCH & SRB Over HSDPA Feature Guide

Uploaded by

Copyright:

Available Formats

F-DPCH & SRB over HSDPA

F-DPCH & SRB over HSDPA

Compared with UR14, there is no change

© 2016 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 5

3 Technical Descriptions ..................................................................................... 7

5 Related Counters and Alarms ........................................................................ 22

6 Engineering Guide .......................................................................................... 22

ZTE Confidential Proprietary 2

6.4 Feature Deactivation Procedure......................................................................... 29

ZTE Confidential Proprietary 3

ZTE Confidential Proprietary 4

Node B Version: [ZXSDR V4.15.10]

Related Network Element:

UE √ F-DPCH should be supported by UE.

Node B √ F-DPCH should be supported by Node B.

2.1 Feature Introduction

2.1.1 ZWF23-01-041 F-DPCH & SRB over HSDPA

ZTE Confidential Proprietary 5

2.2 License Control

Table 2-1 License Control List

License Configured Sales

ZWF23-01-041 WCDMA F-DPCH &

2.3 Correlation with Other Features

ZWF23-01-A HSDPA Introduction Package

ZTE Confidential Proprietary 6

3.1 Principle of Fractional Dedicated Physical Channel

Figure 3-1 Frame Structure of F-DPCH

ZTE Confidential Proprietary 7

Table 3-1 F-DPCH Fields

Channel Channel SF Bits/ Slot NOFF1 NTPC NOFF2

Figure 3-2 Multiplex on an F-DPCH Channel

ZTE Confidential Proprietary 8

3.2 Principle of SRB over HSDPA

When F-DPCH is used, SRBs in downlink need to be carried on HSDPA.

ZTE Confidential Proprietary 9

 The Allocation/Retention Priority (ARP) enjoys the highest priority.

 The Scheduling Priority Indicator (SPI) enjoys the highest priority.

 The MAC-hs guaranteed bit rate is configured.

3.3 Requirements for Utilization of F-DPCH and SRB

 The UHspa.RncFdpchSupInd parameter for F-DPCH on the RNC level is set to

 The UUtranCellFDD.fDpchSuptInd parameter for F-DPCH on the cell level is set to

 The Node B indicates that the cell supports F-DPCH.

 The UE indicates that it supports F-DPCH.

 There is no DCH in the downlink.

ZTE Confidential Proprietary 10

3.4 Multiplexing Method of F-DPCH

 Establish the first radio link for a UE.

 Establish a new radio link for a UE during the soft handover.

 Establish a new radio link for a UE during the hard handover.

 The DPCH channel is transferred to the F-DPCH channel.

Multiplexing on the same channelization code for an F-DPCH is achieved through

ZTE Confidential Proprietary 11

3.5 Dynamic Radio Bearer Control for F-DPCH

3.5.1 Signaling Channel Allocation in the RRC Phase

 The URncFunction.InitRrcOnDch parameter is set to 7: Forced to HSPA or 8: Not

3.5.2 Signaling Channel Allocation in the RAB Phase

ZTE Confidential Proprietary 12

3.5.3 Transition of F-DPCH

 If F-DPCH is configured to a UE and a new sevice of the UE needs to be

ZTE Confidential Proprietary 13

3.6 Code Resource Allocation for F-DPCH