Академический Документы
Профессиональный Документы
Культура Документы
Feature Guide
F-DPCH & SRB over HSDPA
TABLE OF CONTENTS
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
4 Parameters....................................................................................................... 18
7 Abbreviation .................................................................................................... 30
8 References ....................................................................................................... 30
FIGURES
Figure 3-1 Frame Structure of F-DPCH............................................................................... 8
Figure 3-2 Multiplex on an F-DPCH Channel ...................................................................... 9
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-4 Parameter Configuration Interface 4 .................................................................26
Figure 6-5 Parameter Configuration Interface 5 .................................................................27
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.14.10.14/ZXUR 9000 V4.14.10.14]
Attribute: [Optional]
RNC None.
iTC - None.
MSC - None.
MGW - None.
SGSN - None.
GGSN - None.
HLR - None.
: involved, -: not involved.
2 Overview
ZTEs 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. ZTEs 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.
1. Dependency
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.
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.
The following fixed slot format is used for F-DPCH in 3GPP Rel-6.
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.
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.
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:
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.
When the following conditions are met, the SRBs can be carried on HS-DSCH and an
associated F-DPCH is established.
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.
The SF of the channelization code for an F-DPCH is fixed to 256. In the following
scenarios:
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.
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.
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.
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 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.
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.
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 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.
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.
F-DPCH uses the same scrambling codes as their phase reference channel (P-CPICH or
S-CPICH).
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.
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.
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).
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 for F-DPCH/E-FDPCH is
The 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.
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.
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.
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, a radio link addition will not be
triggered by 1A/1C, and an intra-frequency hard handover with a transition from F-DPCH
to DPCH is triggered by 1D.
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, a radio link addition
will be triggered by 1A/1C (DL DPCH is configured), and the serving cell changing with a
transition from DPCH to F-DPCH is triggered by 1D.
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.
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
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
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,
F-DPCH & SRB over HSDPA
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
This parameter indicates the
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
This parameter indicates the
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
Counter ID Name
C310030448 Max Number of including only HSDPA users in the best cell
6 Engineering Guide
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.
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.
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 [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.
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.
Expected
In step1, the SRB of the service is established on HSDPA.
Result
For a description and configuration of the above parameters, refer to section 6.2.
None
2. Network KPI
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.
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
8 References
[1] 3GPP TR 25899-610