Beruflich Dokumente
Kultur Dokumente
Feature Guide
Enhanced F-DPCH
Enhanced F-DPCH
Version Date Author Reviewer Revision History
Ke Yazhu, Ma
V1.0 2013/12/24 Cai Yaofang Yongchao, Yang First edition
Hong
TABLE OF CONTENTS
2 Overview ............................................................................................................ 4
2.1 Feature Introduction ............................................................................................. 4
2.1.1 ZWF26-01-010 Enhanced F-DPCH ..................................................................... 4
2.2 License Control .................................................................................................... 5
2.3 Correlation with Other Features ........................................................................... 6
7 Abbreviation .................................................................................................... 21
8 References ....................................................................................................... 22
FIGURES
TABLES
1 Feature Attributes
RNC Version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
Attribute: [Optional]
Involved NEs:
NE Name Related or Not Special Requirement
RNC
iTC -
MSC -
MGW -
SGSN -
GGSN -
HLR -
: Involved, -: Not involved.
2 Overview
UE1
UE2 UE3 UE10 UE2 UE3 UE1 UE1
UE1 ...
1 slot time
The enhanced F-DPCH feature has removed the restriction on F-DPCH timing offset, for
example, allow activating several F-DPCHs to use different timing offsets, which are
configured at the network side. This feature requires the UE to buffer a 1-bit TPC
command per slot.
Because the enhanced F-DPCH is introduced, the F-DPCH slot format defined in 3GPP
R6 is changed. Originally, the offset is a fixed value from the TPC field to the slot
boundary. After being changed, the offset is determined by one of the multiple F-DPCH
slot formats. Assuming that 30% of UEs are in the status of soft or softer handover, the
capacity of an enhanced F-DPCH is increased to 7 UEs actually.
1. Required Features
None
3. Affected Features
None
3 Technical Description
This feature is optional in 3GPP Rel-7. Because the slot formats for an F-DPCH are
extended, there are 10 options for TPC position in one time slot at an F-DPCH frame
offset. Compared with the F-DPCH in 3GPP Rel-6, an E-FDPCH increases the
multiplexing opportunity for the UE during a soft handover, which saves downlink
channelization code resources.
For the basic principles of an F-DPCH, refer to the ZTE UMTS F-DPCH & SRB over
HSDPA Feature Guide.
For convenient description, the F-DPCH in this feature guide denotes a usual F-DPCH,
and the E-FDPCH denotes an enhanced F-DPCH introduced in 3GPP Rel-7, that is, the
extended slot formats based on the F-DPCH in 3GPP Rel-6.
The differences between E-FDPCH and F-DPCH only reside in the multiplexing method,
dynamic radio bearer control and mobility management, while the same parts are not
described in this feature guide. For more details, refer to the ZTE UMTS F-DPCH & SRB
over HSDPA Feature Guide.
The frame structure of an E-FDPCH is the same as that of an F-DPCH, and is illustrated
in the following figure. The difference is the slot format.
In 3GPP Rel-6, a fixed slot format (Slot Format #0 in the following table) is used. In 3GPP
Rel-7, there are 10 slot formats. Each slot format corresponds to a different position of
the TPC field within an F-DPCH slot. Ten positions of 256 chips are denoted by Slot
Format #0#9. The exact number of bits of the OFF periods and the number of the TPC
field (NTPC) are described in the following table.
Table 3-1 F-DPCH Fields (Copied from Table 16C: F-DPCH Fields in 25.211)
0 3 1.5 256 20 2 2 16
1 3 1.5 256 20 4 2 14
2 3 1.5 256 20 6 2 12
3 3 1.5 256 20 8 2 10
4 3 1.5 256 20 10 2 8
5 3 1.5 256 20 12 2 6
6 3 1.5 256 20 14 2 4
7 3 1.5 256 20 16 2 2
8 3 1.5 256 20 18 2 0
9 3 1.5 256 20 0 2 18
Because the multiplexing is independent of each cell, the F-DPCH slot format is
configured by the CRNC. For Iur, the slot format is allocated by the DRNC and then
transfered to the SRNC. The UE during a soft hanover receives different slot formats
from different cells and combines multiple TPC commands about the same downlink slot
from the same radio link set.
The parameter for the E-FDPCH on the RNC level (Uhspa.rncEfdpchSupInd) is set
to Supported.
The Node B indicates that the cell supports the E-FDPCH through the F-DPCH Slot
Format Capability IE in the AUDIT RESPONSE message or other related
messages.
The UE indicates that it supports the E-FDPCH through the Enhanced F-DPCH
supported IE.
Note:
If the conditions for utilizing the E-FDPCH are met and SRBs can be carried on HSDPA,
and if there is a service carried on HSUPA, the conditions for SRBs carried on HSUPA
should be also met, otherwise, SRBs cannot be carried on HSDPA and the E-FDPCH
cannot be used. For details, referto the ZTE UMTS SRB over HSUPA Feature Guide.
For the cells and the UEs supporting the E-FDPCH, the multiplexing method of the
channelization code for the E-FDPCH is independent of the configured F-DPCH frame
offset, which means that the UEs with the same F-DPCH frame offset can use the same
channelization code in different slot formats. The RNC allocates an F-DPCH slot format
to each radio link through the Iub and the Uu interfaces.
Both Rel-6 UEs and Rel-7 UEs may exist in a cell supporting the E-FDPCH. In order to
allocate the same channelization code for the F-DPCH to UEs in these two versions, the
RNC allocates an idle TPC bit position first for Rel-6 UEs, and then detemines the
F-DPCH frame offset based on Slot Format #0 and the TPC bit position for the UE to
establish the first radio link.
The principle of dynamic radio bearer control for the E-FDPCH is almost the same as that
for the F-DPCH except for the parameters. Because the use of the F-DPCH is related to
SRBs, the signaling channel allocation in the RRC phase, and signaling channel
allocation in the RAB phase and Dynamic Channel Type Transfer are described as
follows.
If the following conditions are met in the RRC phase, the SRBs of the UE can be carried
on the HS-DSCH and there is an associated F-DPCH.
The conditions of using E-FDPCH are satisfied, refer to 3.1.2 Requirements for
Utilization of the E-FDPCH;
If either of the above conditions is not met or the SRB fails to be established on HSPA,
the RNC attempts to establish SRBs on the DCH at the rate of 3.4 kbps.
If the SRB is established on the DCH in the RRC phase, and if the following conditions
are met in the RAB phase, the SRBs of the UE in the RAB phase can be carried on the
HS-DSCH and there is an associated F-DPCH.
The conditions of using E-FDPCH are satisfied, refer to 3.1.2 Requirements for
Utilization of the E-FDPCH;
For the other scenarios of HS-DSCH serving cell change (including intra-frequency
and inter-frequency), transition from non HS-DSCH to HS-DSCH triggered by the
traffic volume in a cell, or relocation into the RNC, the conditions for E-FDPCH usage
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 specified period. For details, refer to the ZTE UMTS Handover Control
Feature Guide.
The principles of dynamic channel type transfer for the E-FDPCH are the same as those
for the F-DPCH. For details, refer to the ZTE UMTS F-DPCH & SRB over HSDPA
Feature Guide.
Code resource allocation for the E-FDPCH is only related to channelization code
allocation and scrambling code allocation for a new established F-DPCH. The allocation
method is the same as that for the F-DPCH. For details, refer to the ZTE UMTS F-DPCH
& SRB over HSDPA Feature Guide.
A cell supporting the E-FDPCH and a cell only supporting the F-DPCH may be adjacent
cells, but the F-DPCH multiplexing method in each cell is independent, so the two kinds
of cells can be in the same active set.
If a UE supports the E-FDPCH, then the following situation may occur: Cell 1 in the active
set allocates the F-DPCH based on the method in Rel-6 and cell 2 in the active set
allocates the F-DPCH based on the method in Rel-7.
When the serving HS-DSCH cell changes, if the F-DPCH/E-FDPCH is used in the source
cell, but the conditions to use the F-DPCH/E-FDPCH are not met in the target cell, the
transition from F-DPCH to DPCH will be triggered.
When the serving HS-DSCH cell changes, if DPCH is used in the source cell, and the
conditions to use F-DPCH/E-FDPCH is met in all the cells in the active set, the transition
from a DPCH to an F-DPCH will be triggered.
During a hard handover or relocation into the RNC, if the target cell meets the conditions
to use the E-FDPCH, an F-DPCH is allocated.
Note:
For the conditions to use the E-FDPCH, refer to 3.1.4.2 Signaling Channel Allocation in
the RAB. For mobility management for the F-DPCH, refer to the ZTE UMTS F-DPCH &
SRB over HSDPA Feature Guide.
Because the F-DPCH Slot Format Support Request IE cannot be carried in the Radio link
addition message across the Iur interface, the F-DPCH cell and the E-FDPCH cell
crossing the Iur interface cannot stay in an active set if the UE is using the E-FDPCH.
The following rules are used:
If all the neighboring cells of the DRNC configured on the SRNC support the
E-FDPCH, the SRNC sends the F-DPCH Slot Format Support Request IE to the
DRNC through the Radio Link Setup Request message or the Radio Link
Reconfiguration Preparation message. And then the SRNC sends the F-DPCH slot
format fed back by the DRNC to the UE.
If not all the neighboring cells of the DRNC configured on the SRNC support the
E-FDPCH, the SRNC does not send the F-DPCH Slot Format Support Request IE,
and all the neighboring cells of the DRNC are regarded as cells with the F-DPCH.
If there is a radio link on the DRNC which is using the E-FDPCH, and if a new radio
link to be added on the DRNC does not support the E-FDPCH, the cell cannot be
added to the active set.
If there is a radio link on the DRNC which is using the F-DPCH, and if a new radio
link to be added does not support the E-FDPCH, the radio link can only use the
F-DPCH.
If the E-FDPCH is used by the UE, and if a new radio link to be added supports
neither the E-FDPCH nor the F-DPCH, the cell cannot be added to the active set.
For a neighboring cell of the DRNC which is not configured on the SRNC, if the
value of the cells F-DPCH Support Indicator in Cell Capability Container FDD
fed back through the Iur interface is Support, the cell is regarded as a cell which
supports the F-DPCH; otherwise, the cell is regarded as a cell which does not
support the F-DPCH. If the value of the cells F-DPCH Slot Format Support
Indicator in Cell Capability Container FDD fed back through the Iur interface is
Support, the cell is regarded as a cell which supports the E-FDPCH; otherwise,
the cell is regarded as a cell which does not support the E-FDPCH.
This parameter
RNC Enhanced 0: Not
indicates whether 0: Not
UHspa.rncEfd F-DPCH Supported N/
the RNC supports Support 1: Supported
pchSupInd Support 1: A
the Enhanced ed
Indicator Supported
F-DPCH or not.
This parameter
Cell Enhanced 0: Not
UUtranCellFD indicates whether 0: Not
F-DPCH Supported N/
D.efdpchSupI the cell supports Support 1: Supported
Support 1: A
nd Enhanced F-DPCH ed
Indicator Supported
or not.
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
State
to
4: Not
Type of This parameter CELL_D Forced to
Forced,
Transport indicates the type of CH and CELL_DCH
Using
URncFunction Channel for transport channel N/ Using and Using
DCH/DCH
.initRrcOnDch Initial RRC and signaling rate A DCH/D DCH/DCH
with 13.6k
Connection for initial RRC CH with with 13.6k
Signalling
Setup connection setup. 13.6k Signalling
on
Signallin
Cell_DCH
g
State
5: Forced
to
CELL_DC
H and
Using
DCH/DCH
ZTE Confidential Proprietary with 27.2k 14
Signalling
6: Not
Forced,
Enhanced F-DPCH
C310030448 Max Number of including only HSDPA users in the best cell
6 Engineering Guide
The procedure describes how to find the GUI location of the parameters that are related
to the deployment of this feature. The values indicated by the captures may be not the
real value to be configured. For the real configuration value, refer to the last column of
the table in chapter 4.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > External Resource Configuration > External RNC
Function and double-click External UTRAN Cell, and set Neighboring Cell Enhanced
F-DPCH Support Indicator, see Figure 6-1.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service configuration and double-click Hspa
Configuration, and set RNC Enhanced F-DPCH Support Indicator and Indicator for
Whether to Judge Event 1F Condition When the Service is Setup on HSPA, see
Figure 6-2 and Figure 6-3.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration and double-click UTRAN Cell, and set Cell Enhanced
F-DPCH Support Indicator, see Figure 6-4.
In the configuration resource tree, select Modify Area > Managed Element and
double-click UMTS Logical Function Configuration, and set Type of Transport
Channel for Initial RRC Connection Setup, see Figure 6-5.
2. The RNC configures SRBs on HS and indicates the slot format in the Radio
RNC Enhanced
UHspa.rncEfdpchSupInd F-DPCH Support 0: Off 0: Off
Indicator
Cell Enhanced
UUtranCellFDD.efdpchSupInd F-DPCH Support 0: Off 0: Off
Indicator
For a description and configuration of the above parameters, refer to 6.2 Feature
Activation Procedure.
1. Equipment Performance
None
2. Network KPI
Because of the restriction that the TPC from different cells for a given UE must have the
same offset timing during a soft handover is removed for the E-FDPCH, the multiplexing
of code resources increases, more downlink channelization codes are saved, and the
average throughput and the user experience are improved.
Because the downlink Pilot of DPCCH is removed and the mechanism for the
reliability of TPC commands between the F-DPCH and the DPCH is different, and
the UE combines the different slot formats for TPC, the RTWP may be raised.
Because there are compatibility issues from some UEs, the following KPIs may be
deteriorated: CS RAB setup success rate (caused by concurrent PS services and
CS services with the PS services set up first), PS RAB setup success rate, and PS
call drop rate.
7 Abbreviation
Abbreviation Full Name
DPCCH Dedicated Physical Control Channel
8 References
[1] R1-062672
[2] ZTE UMTS F-DPCH & SRB over HSDPA Feature Guide