Zte Umts Ur15 Enhanced DL Cell - Fach Feature Guide

Enhanced DL CELL_FACH
Feature Guide
Version Date Author Reviewer Notes
Compared with UR14,

Update “ Figure 3-2MAC-ehs Header”
V1.00 2016/03/22 Sha Xiubin Ke Yazhu Add CCCH congestion strategy: refer to the
content about downlink CCCH signals in the
chapter Admission Control
© 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 ............................................................................................... 4
2 Overview ............................................................................................................ 4
2.1 Feature Introduction ............................................................................................. 4
2.1.1 ZWF26-01-011 Enhanced DL CELL_FACH ......................................................... 4
2.2 License Control .................................................................................................... 5
2.3 Correlation with Other Features ........................................................................... 5
3 Technical Description ....................................................................................... 6

3.1 ZWF26-01-011 Enhanced DL CELL_FACH ......................................................... 6
3.1.1 Overview .............................................................................................................. 6
3.1.2 Control Policies of RNC ..................................................................................... 12
3.1.3 Scheduling Policies in Node B ........................................................................... 16
4 Parameters....................................................................................................... 17
4.1 ZWF26-01-011 Enhanced DL CELL_FACH Related Parameters....................... 17
4.1.1 Traffic Volume Related Parameters for Enhanced DL CELL_FACH .................. 17
4.1.2 Scheduling Priority Queue Related Parameters for Enhanced DL CELL_FACH 21
4.1.3 Controlling Parameters for Enhanced DL CELL_FACH ..................................... 25
5 Related Counters and Alarms ........................................................................ 28

5.1 Related Counters ............................................................................................... 28
5.1.1 ZWF26-01-011 Enhanced DL CELL_FACH Related Counters........................... 28
5.2 Related Alarms .................................................................................................. 31
6 Engineering Guide .......................................................................................... 31

6.1 Application Scenario .......................................................................................... 31
6.2 Feature Activation Procedure ............................................................................. 31
6.3 Feature Validation Procedure ............................................................................ 35
6.4 Feature Deactivation Procedure......................................................................... 36
6.5 Network Impact .................................................................................................. 36
7 Abbreviation .................................................................................................... 37
8 Reference Document....................................................................................... 38

FIGURES
Figure 3-1 Channels Mapped on HS-DSCH in the Enhanced DL CELL_FACH State ......... 7
Figure 3-2 MAC-ehs Header ............................................................................................... 8
Figure 3-3 HSDPA Adjustment with Enhanced DL CELL_FACH but without Enhanced UL
CELL_FACH ........................................................................................................................11
Figure 6-1 Parameters configuration interface 1 ................................................................32
TABLES
Table 2-1 License Control List ............................................................................................ 5

Table 3-1 Configuration Policies for the Cells in the Enhanced DL CELL_FACH Queue over
Uu/Iub Interface ..................................................................................................................... 9
Table 3-2 Values of RLC PDU SIZE for different Logical Channels....................................10
Table 3-3 Traffic Volume Related Parameters List for Enhanced DL CELL_FACH ............13
Table 4-1 Traffic Volume Related Parameters for Enhanced DL CELL_FACH ..................17
Table 4-2 Scheduling Priority Queue Related Parameters for Enhanced DL CELL_FACH 21
Table 4-3 EFACH_Default .................................................................................................25
Table 4-4 Controlling Parameters for Enhanced DL CELL_FACH .....................................25
Table 5-1 Enhanced DL CELL_FACH Related Counters ...................................................28
Table 6-1 Feature Validation Procedure.............................................................................35
Table 6-2 RNC parameter list ............................................................................................36

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]
Involved NEs:
NE Name Related or Not Special Requirements
√ The UE must support the enhanced DL
UE
CELL_FACH feature.
√ The Node B must support the enhanced DL
Node B
CELL_FACH feature.
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 ZWF26-01-011 Enhanced DL CELL_FACH
The common H-RNTI, HS-SCCH and HS-DSCH configuration information are added to
the system broadcast, and then UE can use HSDPA resource in CELL_FACH state after
reading the cell broadcast. In addition Enhanced DL CELL_FACH allows UE receive
HS-DSCH data in CELL_FACH states. Therefore HS-DSCH is regarded as universal

channel, and can be used in CELL_DCH and CELL_FACH states instead of CELL_DCH
state only. The enhanced DL CELL_FACH feature regards the HS-DSCH as a common
channel in the CELL_FACH state. For UE in CELL_FACH state, UTRAN can send
SYSTEM INFORMATION CHANGE INDICATION message on BCCH over HS-DSCH,
UTRAN can also send signaling and data of DCCH, CCCH and DTCH over HS-DSCH.
Whether the UE supports the enhanced DL CELL_FACH feature is added to the UE

capability information, and the UE should inform the UTRAN of this information in the
RRC Connection Setup Complete message. If the UE supports this feature, it prefers to
receiving the signaling and data in the HS-DSCH rather than in the S-CCPCH in the
CELL_FACH state.
After this feature is enabled, the SRB is beared on HSPA during the channel transferring,
which reduces the delay of message transmission in the control plane. In addition, the
HS-DSCH can be used for transmission in the CELL_FACH state which enhances the
peak bit rate of UE in CELL_FACH state, the frequency of state switching between
CELL_FACH and CELL_DCH due to data burst can be reduced.
2.2 License Control
Table 2-1 License Control List
License Control Configured Sales

Feature ID Feature Name
Item NE Unit
Enhanced Cell FACH Enhanced Cell

ZWF26-01-B RNC Cell
Package FACH Package
2.3 Correlation with Other Features
1. Required Features
ZWF23-01-A Basic HSDPA
ZWF26-01-001 Enhanced DL L2

2. Mutually Exclusive Features
None
3. Affected Features
None
3 Technical Description
3.1 ZWF26-01-011 Enhanced DL CELL_FACH
3.1.1 Overview
The WCDMA system defines four kinds of connection states - CELL_DCH, CELL_FACH,
CELL_PCH and URA_PCH.
When there is not much user data to be transmitted, the UTRAN can make the UE
transfer to the CELL_FACH state to save the dedicated resources. When there is no user
data to be transmitted temporarily, the UE can be transferred to the CELL_PCH or
URA_PCH state to save the UE power. But channel transfer takes time. If the user has
some data to be transmitted suddenly (for example, the user jumps to the next web page
after reading the current one for a long time), he will have to wait for a longer time. As a
result, the delay of channel handover is a key KPI of the QoS. Reduce the delay to
improve the PS data user experience. To achieve this, HSPA+ has improved the wireless
interfaces. The 3GPP introduced the enhanced DL CELL_FACH feature in R7, aiming at:
 To enhance the peak rate of the UE by adopting HSDPA in the CELL_FACH state;
 To decrease the transmission delay in the CELL_FACH state on the user plane;
 To shorten the delay of converting from the CELL_FACH state to CELL_DCH state;
 To save power through the UE’s discontinuously receiving the data in the
CELL_FACH state.

These measures mentioned above particularly benefit the “always on-line” service such
as PoC, Push email and VPN. This kind of service is characterized with frequent but
small burst data between the UE and the server.
3.1.1.1 Operating Principles of MAC Layer
In the enhanced DL CELL_FACH state, the logical channels such as BCCH, CCCH and
DCCH/DTCH are mapped on the HS-DSCH, as shown in Figure 3-1.
Figure 3-1 Channels Mapped on HS-DSCH in the Enhanced DL CELL_FACH State
RLC
DCCH DTCH CCCH BCCH PCCH
MAC
HS-DSCH
L1
HS-PDSCH HS-SCCH PICH
In the enhanced DL CELL_FACH state, the MAC layer adopts the MAC-ehs entity.
Moreover, to enable the UE to identify the logical channel types and the data which
belongs to it on the HS-DSCH, the protocol gives detailed definition to the composition of
the MAC header.
 MAC-d header for DTCH and DCCH (mapped on HS-DSCH)
In the CELL_FACH and CELL_PCH state, the structure of mac-d header includes:
 When the UE uses the dedicated H-RNTI, only MAC-ehs header is

contained;
 When the UE uses the common H-RNTI and the DCCH transmits SRB1,
MAC-ehs header + U-RNTI is contained.
MAC-ehs MAC SDU
MAC-ehs U-RNTI MAC SDU

 MAC header for BCCH
When the BCCH is mapped on the HS-DSCH, its MAC header includes the
MAC-ehs header and the logical channel id contained in the MAC-ehs header is set
to “1111”. The logical channel id corresponds to the H-RNTI indicated by the
HS-SCCH which is for broadcasting.
MAC-ehs MAC SDU
 MAC header for CCCH
When the CCCH is mapped on the HS-DSCH, there is no MAC-c header. The
MAC-c PDU format for CCCH mapped to HS-DSCH is as follows:
MAC SDU
The MAC-ehs header contains the following information.
Figure 3-2 MAC-ehs Header
LCH-ID1 L1 TSN1 SI1 F1 LCH-IDk Lk TSNk SIk Fk
MAC-ehs header Reordering PDU Reordering PDU Padding (opt)
Mac-ehs payload
Where:
 SI (Segmentation Indication) field indicates if the MAC-ehs SDU has been

segmented.
 LCH-ID (Logical Channel Identifier) field provides identification of the logical

channel at the receiver and the re-ordering buffer destination of a reordering SDU.
 TSN (Transmission Sequence Number) field provides an identifier for the

transmission sequence number on the HS-DSCH. The TSN field is used for
reordering purposes to support in-sequence delivery to higher layers.
 L (Length) field provides the length of the reordering SDU in octets. The reordering

SDU size can vary for each reordering SDU in the MAC-ehs PDU, and is set for
each reordering SDU individually.
 F (Flag) field is a flag indicating if more fields are present in the MAC-ehs header or
not. If the F field is set to "0" the F field is followed by an additional set of LCH-ID
and L fields and optionally TSN and SI fields. If the F field is set to "1" the F field is
followed by a reordering PDU. Each header extension corresponds to one
reordering SDU.
The advantage of this structure is: Multiple priority queues can be sent in one TTI’s
HARQ entity. One H-RNTI corresponds to one HARQ entity.
The RNC configures the information related with the queue of scheduling priority for the
Node B and UE for the sake of the enhanced DL CELL_FACH feature. The queue of
scheduling priority for the enhanced DL CELL_FACH feature is organized based on the
logical channel. The value of each cell in the priority queue is listed in Table 3-1.
Table 3-1 Configuration Policies for the Cells in the Enhanced DL CELL_FACH Queue
over Uu/Iub Interface
Logical Channel Type

CCCH SRB1
(UEFachPch.chTypeInd)
MAC-ehs queue identity UEFachPch.macehsQID[0] UEFachPch.macehsQID[1] UEFac
Scheduling Priority
UEFachPch.spi[0] UEFachPch.spi[1] UEFac
Indicator
T1 UEFachPch.t1[0] UEFachPch.t1[1] UEFac
MAC-ehs window size UEFachPch.macehsWinSize[0] UEFachPch.macehsWinSize[1] UEFac
Treset UEFachPch.treset[0] UEFachPch.treset[1] UEFac
For the enhanced DL CELL_FACH feature, the RNC can configure each queue of
scheduling priority a PDU discard timer for the Node B through IE of “Discard Timer”. If
“UEFachPch.dtCfgInd” is set to “1: True”, the RNC configures the Node B the “Discard
Timer” IE, and the value of the timer is decided by “UEFachPch.discardTimer”; if
“UEFachPch.dtCfgInd” is set to “0: False”, the RNC does not configure the Node B the
“Discard Timer” IE.

3.1.1.2 Operating Principles of RLC Layer
The RLC PDU SIZE in the RLC layer for the enhanced DL CELL_FACH feature:
 For the signaling RB, fixed size mode only;
 For the service RB, either fixed size mode or flexible size mode is acceptable. The
detailed flexible RLC PDU SIZE is described in the ZTE UMTS HSPA Enhanced L2
Feature Guide.
The value of RLC PDU SIZE is decided by the logical channel type and RLC PDU SIZE.
See the configuration policies below.
Table 3-2 Values of RLC PDU SIZE for different Logical Channels
Logical Channel Type

CCCH SRB1
(UEFachPch.chTypeInd)
RLC PDU SIZE for Fixed

1 (invalid) 1 (invalid) 1 (invali
Size mode
RLC PDU SIZE for

UEFachPch.mxMaccSizeFix[0] UEFachPch.mxMaccSizeFix[1] UEFach
Flexible size mode
3.1.1.3 The Measurement Mechanism of UE in the Enhanced DL CELL_FACH State
The inter-cell reselection flows remain after the enhanced CELL_FACH is achieved. In
other words, the UE must finish the measurement in the measurement occasion to
support the inter-frequency and inter-RAT cell reselection.
When the UE receives the HS-DSCH in the CELL_FACH state, its measurement
duration is 10ms.
The Node B and UE use the dedicated H-RNTI and measurement occasion cycle length
coefficient to calculate the measurement cycle of the UE. The scheduler of Node B
ensures the UE to receive HS-SCCH and HS-PDSCH beyond its measurement cycle.
The Node B and UE start the measurement from the SFN which satisfies the following
formula:
SFN = H-RNTI mod M_REP + n * M_REP (3.1.1.3-1)

 “H-RNTI” is the valid H-RNTI saved by the UE. Use the common H-RNTI in case
there is no dedicated H-RNTI.
k
 “M_REP” is the measurement occasion cycle length; its value is “2 ”. “k” is the
measurement occasion cycle length coefficient; its value is “3”.
 n =0,1,2… The SFN must be smaller than its maximum value.
3.1.1.4 Link Adjustment
When the UE adopts the enhanced DL CELL_FACH state and UL RACH, it is able to
report the measurement result of the P-CPICH channel via RRC message on RACH only.
And then the RNC sends the result to the Node B to adjust the transmit power of
HS-SCCH and HS-DSCH. See the detailed flow in Figure 3-3.
Figure 3-3 HSDPA Adjustment with Enhanced DL CELL_FACH but without Enhanced
UL CELL_FACH
HS-DSCH DATA Frame for Enhanced CELL_FACH
RRC message/RACH/PRACH
UE (…, IE „Measured results on RACH”, …) RNC
1..n MAC-d PDU

etc.
Header Payload
Node B
new field:Transmit Power Level
When the enhanced CELL_FACH state is adopted in both DL and UL (with the common
E-DCH is being used), the channel quality can be sent through the common E-DCH.
3.1.1.5 Operating Flow of Enhanced DL CELL_FACH State
As for the cells that meet the conditions of activating described in chapter 3.1.2.1 How to
Enable Enhanced DL CELL_FACH, the RNC configures the “HS-DSCH common
system information” IE for the UE and Node B. This IE is sent to the UE through the

system broadcasting message and to the Node B through the physical sharing channel
reconfiguration message.
For the network: If the RNC configures the Node B the “HS-DSCH common system
information” IE, and the UE supports the enhanced DL CELL_FACH, the HS-DSCH is
used to transmit data to the UE in the CELL_FACH state; otherwise, the FACH is used to
transmit data to the UE in the CELL_FACH state.
For the UE: After the UE has received the “HS-DSCH common system information” IE,
and in the meantime the UE supports the enhanced DL CELL_FACH, the UE monitors
only the HS-DSCH in the CELL_FACH state; otherwise, the UE monitors only the FACH
in the CELL_FACH state.
3.1.2 Control Policies of RNC
The RNC controls whether to enable the enhanced DL CELL_FACH feature. The
algorithm change concerned with the RNC involves the DRBC algorithm, access control
algorithm and load control algorithm. The following four chapters give detailed
description.
3.1.2.1 How to Enable Enhanced DL CELL_FACH
The enhanced DL CELL_FACH feature is controlled by

“UUtranCellFDD.eFACHSpptInd”.
When the following three conditions are met, the enhanced DL CELL_FACH feature can
be enabled.
 “UUtranCellFDD.eFACHSpptInd” is set to “1: Supported”;
 The Node B feeds back that the corresponding cell supports the enhanced DL
CELL_FACH (The auditing response or resource state indication message indicates
that Enhanced FACH Capability: Enhanced FACH Capable and HS-DSCH
Resources --> Resource Operational State = Enabled and HS-DSCH Resources-->
Availability State = available);
 The Node B feeds back that the corresponding cell supports the enhanced DL L2
(see details in ZTE UMTS HSPA Enhanced L2 Feature Guide).

When the enhanced DL CELL_FACH feature is enabled in the cell and the UE in the
CELL_FACH state supports this feature, the RNC and Node B will send the data to the
UE through the HS-DSCH.
3.1.2.2 DRBC Algorithm
The channel transfer policies after the enhanced DL CELL_FACH state is introduced are
similar to those of common CELL_FACH state. All transfer between CELL_FACH and
other RRC states is triggered by traffic. Since the transmission efficiency of the
CELL_FACH (FACH) and CELL_FACH (HS-DSCH) is different, it is essential to
configure a set of traffic measurement parameters for the enhanced DL CELL_FACH
separately, which is independent of the CELL_FACH (FACH) traffic measurement
parameters (parameters corresponding to the UComHsdschEvUpTrv object are added).
These parameters independently control the duration of the UE to transfer from the
enhanced DL CELL_FACH state to the CELL_DCH state.
The table below lists the service measurement parameters of the enhanced DL
CELL_FACH state and how to get the parameters. They are taken from the
UComHsdschEvUpTrv object. Please refer to the parameters corresponding to the
UFachEvUpTrv object described in ZTE UMTS Dynamic Radio Bearer Control Feature
Guide for how to use these parameters.
Table 3-3 Traffic Volume Related Parameters List for Enhanced DL CELL_FACH
Parameter Name Control Parameter
UE Traffic Volume Measurement

UComHsdschEvUpTrv.ueTrvMCfgNo
Configuration Index
Measurement report transmission

UComHsdschEvUpTrv.measRptTrMod
mode
UP traffic measurement quantity UComHsdschEvUpTrv.measQuantity
Average time of traffic measurement UComHsdschEvUpTrv.averageTime
Indicator of whether to report the

UComHsdschEvUpTrv.rptRlcBufInd
traffic measurement RLC Buffer

Parameter Name Control Parameter
UE Traffic Volume Measurement

UComHsdschEvUpTrv.ueTrvMCfgNo
Configuration Index
Payload

traffic measurement Average of RLC UComHsdschEvUpTrv.rptRlcAveInd
Buffer Payload

traffic measurement Variance of RLC UComHsdschEvUpTrv.rptRlcVarInd
Buffer Payload
Number of UP traffic measurement

UComHsdschEvUpTrv.measEvtNum
event
Indicator of UP traffic measurement

UComHsdschEvUpTrv.meaEvtId
report event
4A/4B event threshold for the traffic

measurement of CELL_FACH UComHsdschEvUpTrv.rptThres
HS-DSCH
Time from the event occurrence to

UComHsdschEvUpTrv.trigTime
reporting the event
Pending time from triggering the

event to triggering the same event UComHsdschEvUpTrv.pendingTime
again
3.1.2.3 Admission Control
Since the resources such as transmission bandwidth

(UCelInfoFDD.eFachPchBandWidth) reserved for the enhanced DL CELL_FACH state
are restricted, the number of user in the enhanced DL CELL_FACH state cannot
increase without restrictions; otherwise, the QoS of the current service might be
influenced.
In addition, the number of dedicated H-RNTI reserved for the enhanced DL CELL_FACH
state is also restricted. As a result, the number of user in the enhanced DL CELL_FACH
state must not exceed that of dedicated H-RNTI reserved for the enhanced DL
CELL_FACH state.

When new service or signaling requests for accessing the HS-DSCH which is in the
CELL_FACH state: if either of the following two conditions is met, the access request is
rejected due to the restricted number of user on the HS-DSCH which is in the enhanced
DL CELL_FACH state; otherwise, the access request is accepted.
 The number of user (excluding the signaling only) whose service is carried on the
HS-DSCH which is in the CELL_FACH state in the current cell is greater than or
equals to the maximum user threshold “UCelInfoFDD.dLEFACHUserNum”.
 The number of user (including the signaling only) whose service is carried on the
HS-DSCH which is in the CELL_FACH state in the current cell is greater than or
equals to the number of dedicated H-RNTI which is in the CELL_FACH state. (In
the current version, the number of dedicated H-RNTI in the CELL_FACH state is
255).
Additional, since the resources such as transmission bandwidth

(UCelInfoFDD.eFachPchBandWidth) reserved for the enhanced DL CELL_FACH state
are restricted, downlink CCCH signals is limit on common HS-DSCH MAC Flow, or affect
the UEs’ rrc processes such as rrc connection, CellUpdate and UraUpdate. The
CCCH congestion strategy refers to the chapter of CCCH Congestion Control in the
document of ZTE UMTS Admission Control Feature Guide.
Note: While a cell configures both common HS-DSCH MAC flow and SCCHCH, either
common channel may be in downlink CCCH congestion state. For simplifying the
process, either common channel is in downlink CCCH congestion state, all UEs of all
common channels including SCCPCHs and common HS-DSCH MAC flow process the
same congestion control strategy.
3.1.2.4 Load Control Algorithm
When the cell is overloaded in the DL, transfer the UE that bears the HSDPA service
from the CELL_DCH state to CELL_FACH state to reduce the load brought by the
dedicated channel. This rule works as well after the enhanced DL CELL_FACH is
introduced.

3.1.2.5 Power Control for BCCH on Enhanced DL CELL_FACH
For BCCH on enhanced DL CELL_FACH, the HS-PDSCH power and HS-SCCH power
come from UCHspa.eFachBcchHsdschPwr and UCHspa.eFachBcchHsscchPwr
respectively.
3.1.2.6 Faulty UE Detection
The Enhanced DL CELL-FACH faulty UE detection function is controlled by the

parameter URncInfo.dlEfachFaultyUeSw. In the detection function, if the RRC SETUP
message fails in CCCH/common HS-DSCH channel, but succeeds in CCCH/FACH
channel, the RNC determines the DL EFACH UE as a DL EFACH faulty UE. The DL
EFACH faulty UEs are forbidden to transfer to CELL-FACH status or PCH status.
3.1.3 Scheduling Policies in Node B
There are two CELL_FACH states according to the UL resources utilization, one is
common E-DCH and the other is RACH. When the common E-DCH is adopted in the UL,
the UE feeds back the CQI and ACK/NACK through the HS-DPCCH, and then the Node
B schedules due to the received CQI; when the UE is not configured the common E-DCH,
it sends the measurement report through the RACH, and the value measured is the
Ec/No of the P-CPICH channel.
The scheduling by Node B differentiates the broadcasting H-RNTI (namely BH-RNTI)

and non-broadcasting H-RNTI (excluding BH-RNTI). How to decide the TB SIZE in these
two occasions: Based on the available power and available channel number of
HS-PDSCH allowed to use in the CELL_FACH, the TB SIZE the UE is capable of
sending is got according to the level 12 capability of UE.

4 Parameters
4.1 ZWF26-01-011 Enhanced DL CELL_FACH Related

Parameters
4.1.1 Traffic Volume Related Parameters for Enhanced DL CELL_FACH
Table 4-1 Traffic Volume Related Parameters for Enhanced DL CELL_FACH
Recomme
Parameter GUI Value Default
Parameter Description Unit nded
Name Name Range Value
Value
This parameter indicates the

Time
average time window for the
Interval
UComHsds measurement, which is only (20,
for Taking
chEvUpTrv. valid when the 40, ..,
an ms 100ms 100ms
averageTim measurement quantity is 260)ms,
Average
e Average RLC buffer payload step 20ms
or a
or Variance of RLC buffer
Variance
payload.

event identity of the traffic
UE Traffic volume measurement
Volume performed by UE.
UComHsds
Measure
chEvUpTrv. (4a, 4b) N/A [4a, 4b] [4a, 4b]
ment MAX_UE_TRV_MEAS_EV
meaEvtId
Event ENT is the maximum
Identity number of UE traffic volume
measurement event, which
equals to 2.
Event 1..MAX_U
UComHsds Number E_TRV_M
This parameter indicates
chEvUpTrv. of UE EAS_EVE
event number of UE traffic N/A 2 2
measEvtNu Traffic NT
volume measurement.
m Volume where
Measure MAX_UE

Recomme
Value
ment _TRV_ME
AS_EVEN
T=2
1: RLC
This parameter indicates the buffer
measurement object of the payload,
traffic volume measurement 2:
that RNC user plane Average
UComHsds Averag
Measure performs.For the definitions RLC Average
chEvUpTrv. e RLC
ment of RLC buffer payload, buffer N/A RLC buffer
measQuanti buffer
Quantity Average RLC buffer payload payload
ty payload
payload, and Variance of 3:
RLC buffer payload,please Variance
refer to the 3GPP TS25.321 of RLC
protocol. buffer
payload

RLC mode that is used by
the traffic volume
measurement report. If the
AM mode is used, when
RNC receives the SDU with
0:
wrong SDU labels (not
Acknowle
continuous), it can ask the
dged
Measure UE to transmit the SDU 0:
UComHsds Mode 0:
ment again. If the UM mode is Acknow
chEvUpTrv. RLC Acknowled
Report used, the retransmission is N/A ledged
measRptTr 1: ged Mode
Transfer not needed. In general, the Mode
Mod Unackno RLC
Mode important measurements RLC
wledged
must use the AM mode to
Mode
report the measurement
RLC
result. Otherwise, only the
UM mode is available
(reduce the data traffic for
the measurement report and
improve the system
capacity).

Recomme
Value

pending time after trigger.
This timer is started in the
UE when a measurement
report has been triggered by
(250,
a given event. The UE is
500,
then forbidden to send new
UComHsds Pending 1000,
measurement reports [2000,
chEvUpTrv. Time 2000, [2000,
triggered by the same event ms 4000]m
pendingTim After 4000, 4000]ms
during this time period, s
e Trigger 8000,
instead the UE waits until
16000)
the timer expires.
ms
MAX_UE_TRV_MEAS_EV
ENT is the maximum
number of UE traffic
equals to 2.
Average
UComHsds of RLC
whether the Average of RLC
chEvUpTrv. Buffer 0: False
Buffer Payload is reported in N/A 1:True 1:True
rptRlcAveIn Payload 1: True
the traffic volume
d for Each
measurement.
RB
RLC This parameter indicates

UComHsds
Buffer whether RLC Buffer
chEvUpTrv. 0: False
Payload Payload is reported in the N/A 1: True 1: True
rptRlcBufIn 1: True
for Each traffic volume
d
RB measurement.
Variance
UComHsds of RLC
whether Variance of RLC
chEvUpTrv. Buffer 0: False
Buffer Payload is reported in N/A 0: False 0: False
rptRlcVarIn Payload 1: True
the traffic volume
d for Each
measurement.
RB
UComHsds Traffic This parameter indicates the (8, 16,

[2k, 8] [2k, 8]
chEvUpTrv. Volume reporting threshold of event 32, 64, bytes
bytes bytes]
rptThres Threshold 4A and 4B for traffic volume 128, 256,

Recomme
Value
of Event measurement on HS-DSCH 512,
4A/4B for Channel in CELL_FACH. If 1024, 2K,
HS-DSC the traffic volume becomes 3K, 4K,
H larger than the threshold of 6K, 8K,
Channel event 4A, a report of 4A 12K, 16K,
in event will be triggered; and 24K, 32K,
CELL_FA if the traffic volume 48K , 64K,
CH becomes smaller than the 96K,
threshold of event 4B, a 128K,
report of 4B event will be 192K,
triggered. 256K,
MAX_UE_TRV_MEAS_EV 384K,
ENT is the maximum 512K,
number of UE traffic volume 768K)
measurement event, which bytes
equals to 2.

the time difference from the
event being detected to the
event being reported. Only
when the event is detected
and still meets all
requirements of event (0, 10,
triggering within the 20, 40,
triggering the 60, 80,
duration,
event can be triggered and 100, 120,
UComHsds [80,
Time to reported. 160, 200, [80,
chEvUpTrv. ms 2560]m
Trigger The larger which equals to, 240, 320, 2560]ms
trigTime s
the stricter the judgment is 640,
for the event to be triggered. 1280,
The parameter must be set 2560,
in accordance with the 5000) ms
actual requirements. If it is
too large, the quality of calls
may be influenced.
MAX_UE_TRV_MEAS_EV
ENT is the maximum
number of UE traffic volume

Recomme
Value
equals to 2.

configuration index of the
UE traffic volume
UE Traffic measurement. There are
UComHsds Volume different sets of
chEvUpTrv. Measure measurement configuration
0..65535 N/A N/A 11
ueTrvMCfg ment values in accordance with
No Configura different measurement
tion Index purposes and measurement
volumes. This parameter
can be used to index
different configurations.
4.1.2 Scheduling Priority Queue Related Parameters for Enhanced DL

CELL_FACH
Table 4-2 Scheduling Priority Queue Related Parameters for Enhanced DL

CELL_FACH
Recomme
Value
Channel
ENUMER
Type This parameter indicates the
ATED(0,
Indicator channel type of the
1, 2, 3); 0:
for Downlink Enhanced EFACH
UEFachPch CCCH; 1: EFACH_D
Enhance FACH/PCH Priority Queue. N/A _Defaul
.chTypeInd SRB1; 2: efault
d Each queue has a fixed t
Other
FACH/PC channel type that is
SRB; 3:
H Priority configured in the OMC-R.
DTCH
Queue
UEFachPch This parameter indicates the ENUMER EFACH

Discard EFACH_D
.discardTim discard timer for a Downlink ATED(20, ms _Defaul
Timer efault
er Enhanced FACH/PCH 40, 60, t

Recomme
Value
Priority Queue, which 80, 100,
defines the time to live for a 120, 140,
MAC-ehs SDU starting from 160, 180,
its entry into an HSDPA 200, 250,
Priority Queue. The NodeB 300, 400,
uses this parameter to 500, 750,
discard out-of-data 1000,
MAC-ehs SDUs from the 1250,
HSDPA Priority Queues. 1500,
1750,
2000,
2500,
3000,
3500,
4000,
4500,
5000,
7500)
D: 0…26
ENUMER
ATED(10,
re-ordering release timer
20, 30,
(T1) for the Downlink
40, 50,
Enhanced FACH/PCH
Re-orderi 60, 70,
Queue. It is used to avoid EFACH
UEFachPch ng 80, 90, EFACH_D
congestion of UE Mac-hs ms _Defaul
.t1 Release 100, 120, efault
buffer. When the timer T1 t
timer (T1) 140, 160,
expires, MAC-ehs PDUs
200, 300,
that are received properly
400);unit:
need to be delivered to the
ms
upper layer.
D: 0…15
Reset This parameter indicates the

Timer Reset Timer for Downlink In
ENUMER
Controllin Enhanced FACH/PCH multipl EFACH
UEFachPch ATED(1, EFACH_D
g the Priority Queue, which es of _Defaul
.treset 2, 3, 4) efault
Reset of controls the reset of the T1 t
D: 0…3
the MAC-ehs reordering values
MAC-ehs functionality for DL

Recomme
Value
Reorderin Enhanced CELL_FACH,
g which is a multiple of T1
Functiona timer. It is used to control
lity the reset of the MAC-ehs
reordering for a UE in
CELL_FACH or CELL_PCH
state.

whether the Discard Timer
is configured for the
Downlink Enhanced
FACH/PCH Queue. If the
Discard Discard Timer is configured,
Timer the SDU in Downlink EFACH
UEFachPch 0: False EFACH_D
Configura Enhanced FACH/PCH N/A _Defaul
.dtCfgInd 1: True efault
tion Queue will be discarded t
Indication when it exists in the queue
for a period that is longer
than the configured Discard
Timer. If the Discard Timer
is not configured, the default
value will be used.

MAC-ehs queue ID of the
UEFachPch MAC-ehs EFACH
Downlink Enhanced INTEGER EFACH_D
.macehsQI Queue N/A _Defaul
FACH/PCH Queue. Each (0..7) efault
D Identity t
queue has a queue ID that
is configured in the OMC-R.

MAC-ehs window size for
ENUMER
the Downlink Enhanced
ATED (4,
UEFachPch MAC-ehs FACH/PCH Queue, which is EFACH
6, 8, 12, EFACH_D
.macehsWi Window used for MAC-ehs PDU Byte _Defaul
16, 24, efault
nSize Size retransmission. The larger t
32)
the parameter is, the more
D: 0…6
the MAC-ehs PDUs that can
stay in the MAC-ehs queue

Recomme
Value
are, the lower the PDU
discard rate is, and the
longer the traffic delay is.
The smaller the parameter
is, the fewer the MAC-ehs
PDUs that can stay in the
MAC-ehs queue are, the
higher the PDU discard rate
is, and the shorter the traffic
delay is.

maximum MAC-c PDU size
Maximum
of a flexible PDU on the
MAC-c
UEFachPch enhanced FACH/PCH. This INTEGER EFACH
PDU Size EFACH_D
.mxMaccSiz parameter is set to the (1..1504) Byte _Defaul
for efault
eFlx maximum MAC-c PDU size Byte t
Flexible
that all UEs can support on
RLC PDU
the downlink enhanced
CELL_FACH/PCH.

maximum MAC-c PDU size
of a fixed PDU on the
Maximum
enhanced FACH/PCH. This
UEFachPch MAC-c INTEGER EFACH
parameter is set based on EFACH_D
.mxMaccSiz PDU Size (1..1504) Byte _Defaul
the RLC PDU size of the efault
eFix for Fixed Byte t
R99 FACH corresponding to
RLC PDU
the logical channel (the RLC
PDU size remains
unchanged).
Schedulin This parameter indicates the

g Priority priority of Mac-ehs for the
Indicator Downlink Enhanced
INTEGER EFACH
UEFachPch for FACH/PCH Queue. It is EFACH_D
(0..15), N/A _Defaul
.spi Enhance used for Mac-ehs efault
step 1 t
d scheduling. The larger the
FACH/PC parameter is, the higher the
H Priority priority is.

Recomme
Value
Queue
4.1.2.1 EFACH_Default
Table 4-3 EFACH_Default
Parameter Name values for different logical channels
CCCH SRB1 Else DTC

SRB H
UEFachPch.macehsQID 1 0 2 3
UEFachPch.chTypeInd 0 1 2 3
UEFachPch.spi 15 14 13 0
UEFachPch.t1 50 50 50 50
UEFachPch.dtCfgInd True True True False
UEFachPch.discardTimer 1000 4000 4000 4000
UEFachPch.macehsWinSize 16 16 16 16
UEFachPch.treset 2 2 2 2
UEFachPch.mxMaccSizeFlx 1(not 1(not 1(not 600

used) used) used)
UEFachPch.mxMaccSizeFix 18 22 18 82
4.1.3 Controlling Parameters for Enhanced DL CELL_FACH
Table 4-4 Controlling Parameters for Enhanced DL CELL_FACH
Recomme
Value
Transport This parameter indicates the
UCelInfoFD
Band transport bandwidth (0..8000)
D.eFachPc
Width for allocated for the Downlink kbps, step kbps 64 64
hBandWidt
Downlink Enhanced CELL_FACH, 1 kbps
h
Enhance CELL_PCH and URA_PCH,

Recomme
Value
d which can not be used by
CELL_FA other channels.
CH,CELL
_PCH
and
URA_PC
H
whether the Downlink
Enhanced CELL_FACH can
Downlink be supported by the cell. By
Enhance using this feature, the
0: Not
UUtranCell d downlink data in 0: Not
Supported 1:
FDD.eFAC CELL_FA CELL_FACH state will be N/A Support
1: Supported
HSpptInd CH carried on HS-DSCH, which ed
Supported
Support can improve the
Indicator performance in
CELL_FACH state, and
shorten the delay in RRC
setup.
maximum number of users
that can be carried on
Downlink Enhanced
CELL_FACH, used for user
Maximum
admission control. When the
Number
number of users on
of Users
Downlink Enhanced
UCelInfoFD on
CELL_FACH (HS-DSCH
D.dLEFAC Downlink 0..255 N/A 64 64
channel in CELL_FACH
HUserNum Enhance
state) (dedicated H-RNTI in
d
enhanced CELL_FACH
CELL_FA
state allocated) exceeds
CH
DLEFACHUserNum, the
Downlink Enhanced
CELL_FACH rejects any
new services. Otherwise,
the Downlink Enhanced

Recomme
Value
CELL_FACH can admit new
services.
HS-PDSCH power for
BCCH in enhanced
CELL_FACH state. It is a
power offset relative to the
HS-PDS
configured P-CPICH power
CH
in a cell. The larger the
Power for
parameter is, the better the
eFachBcch BCCH in (-35..15)d
QoS of BCCH in enhanced dB 0 0
HsdschPwr Enhance B, step
CELL_FACH state is, and
d 0.1dB
the smaller the cell capacity
CELL_FA
is. The smaller the
CH state
parameter is, the worse the
QoS of BCCH in enhanced
CELL_FACH state is, and
the larger the cell capacity
is.
HS-SCCH power for BCCH
in enhanced CELL_FACH
state. It is a power offset
HS-SCC relative to the configured
H Power P-CPICH power in a cell.
for BCCH The larger the parameter is,
eFachBcch in the better the QoS of BCCH (-35..15)d
dB 0 0
HsscchPwr Enhance in enhanced CELL_FACH B, step
d state is, and the smaller the 0.1dB
CELL_FA cell capacity is. The smaller
CH state the parameter is, the worse
the QoS of BCCH in
enhanced CELL_FACH
state is, and the larger the
cell capacity is.
URncInfo.dl Switch of This parameter indicates
0: Off
EfachFaulty DL whether or not the RNC N/A 0: Off 0
1: On
UeSw EFACH supports DL EFACH faulty

Recomme
Value
Faulty UE UE detection function.
Detection Value 1 means that the RNC
Function supports the detection
function. For a UE, if the
RRC SETUP message fails
in CCCH/common
HS-DSCH channel, but
succeeds in CCCH/FACH
channel, the RNC
determines the DL EFACH
UE as a DL EFACH faulty
UE. The DL EFACH faulty
UEs are forbidden to
transfer to CELL-FACH
status or PCH status.
Value 0 means that the RNC
does not supports the
detection function.
5 Related Counters and Alarms
5.1 Related Counters
5.1.1 ZWF26-01-011 Enhanced DL CELL_FACH Related Counters
Table 5-1 Enhanced DL CELL_FACH Related Counters
No. Counter Name
C310416317 Transport Channel Changing attempt, HS-DSCH to FACH ,in

CELL_FACH
C310416318 Transport Channel Changing attempt, FACH to HS-DSCH ,in
CELL_FACH
C310416319 Transport Channel Changing attempt, HS-DSCH of
CELL_FACH to HS-DSCH of CELL_DCH


CELL_FACH to DCH of CELL_DCH
CELL_DCH to HS-DSCH of CELL_FACH
C310416325 Transport Channel Changing attempt, DCH of CELL_DCH to
HS-DSCH of CELL_FACH
C310416327 Transport Channel Changing success, HS-DSCH to FACH ,in
CELL_FACH
C310416328 Transport Channel Changing success, FACH to HS-DSCH ,in
CELL_FACH
C310416329 Transport Channel Changing success, HS-DSCH of
CELL_FACH to HS-DSCH of CELL_DCH
CELL_FACH to DCH of CELL_DCH
CELL_DCH to HS-DSCH of CELL_FACH
C310416335 Transport Channel Changing success, DCH of CELL_DCH to

HS-DSCH of CELL_FACH
C310030782 Number of Cell-Fach and HS/R user in the best cell
C310030783 Max Number of Cell-Fach and HS/R user in the best cell
C310030784 AverageNumber of Cell-Fach and HS/R user in the best cell
C310630582 Max Number of Cell-Fach and HS/R user in RNC
C310086316 Number of successful RRC connection access,

DL-EFACH/UL-RACH
C310086310 Number of successful RRC connection preparation,
DL-EFACH/UL-RACH
Transport Channel Changing attempt, HS-DSCH of
C310417382
CELL_DCH to PCH of CELL_PCH or URA_PCH
C310417383
CELL_DCH to HS-DSCH of CELL_PCH or URA_PCH
Transport Channel Changing attempt, DCH of CELL_DCH to
C310417384
HS-DSCH of CELL_PCH or URA_PCH
C310417386
CELL_FACH to PCH of CELL_PCH or URA_PCH
C310417387
CELL_FACH to HS-DSCH of CELL_PCH or URA_PCH
Transport Channel Changing attempt, FACH of CELL_FACH to
C310417388

Transport Channel Changing attempt, HS-DSCH of CELL_PCH

C310417390
or URA_PCH to HS-DSCH of CELL_DCH
C310417391
or URA_PCH to DCH of CELL_DCH
C310417392
or URA_PCH to HS-DSCH of CELL_FACH
C310417393
or URA_PCH to FACH of CELL_FACH
Transport Channel Changing attempt, PCH of CELL_PCH or
C310417394
URA_PCH to HS-DSCH of CELL_DCH
Transport Channel Changing attempt, PCH of CELL_PCH or
C310417395
URA_PCH to HS-DSCH of CELL_FACH
Transport Channel Changing success, HS-DSCH of
C310417398
CELL_DCH to PCH of CELL_PCH or URA_PCH
C310417399
CELL_DCH to HS-DSCH of CELL_PCH or URA_PCH
Transport Channel Changing success, DCH of CELL_DCH to
C310417400
C310417402
CELL_FACH to PCH of CELL_PCH or URA_PCH
C310417403
CELL_FACH to HS-DSCH of CELL_PCH or URA_PCH
Transport Channel Changing success, FACH of CELL_FACH to
C310417404
C310417406
CELL_PCH or URA_PCH to HS-DSCH of CELL_DCH
C310417407
CELL_PCH or URA_PCH to DCH of CELL_DCH
C310417408
CELL_PCH or URA_PCH to HS-DSCH of CELL_FACH
C310417409
CELL_PCH or URA_PCH to FACH of CELL_FACH
Transport Channel Changing success, PCH of CELL_PCH or
C310417410
URA_PCH to HS-DSCH of CELL_DCH
Transport Channel Changing success, PCH of CELL_PCH or
C310417411
URA_PCH to HS-DSCH of CELL_FACH

5.2 Related Alarms
This feature has no related alarm.
6 Engineering Guide
6.1 Application Scenario
1. This feature is usually applied to the following scenario:
When there is service such as “always on-line” which is characterized with frequent
but small data burst, the enhanced DL CELL_FACH feature is suggested to be
enabled to improve the user experience and the network performance. This feature
is also suggested to be deployed in the region where code resource or CE
resources are limited and the number of users is large.
The enhanced DL CELL_FACH feature switch is a switch in cell level; operator can
activate it in cells where they want.
2. Necessary conditions to enable this feature:
None
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 [Modify Area->Managed

Element->UMTS Logical Function Configuration->Service Configuration->Measurement
Configuration->Traffic Volume Measurement Profile->UP Traffic Volume Measurement
Configuration for HS-DSCH in CELL_FACH] interface and set the parameters "Time

Interval for Taking an Average or a Variance", "UE Traffic Volume Measurement Event
Identity", "Event Number of UE Traffic Volume Measurement", "Measurement Quantity",
"Measurement Report Transfer Mode", "Pending Time After Trigger", "Average of RLC
Buffer Payload for Each RB","RLC Buffer Payload for Each RB", "Variance of RLC Buffer
Payload for Each RB", "Traffic Volume Threshold of Event 4A/4B for HS-DSCH Channel
in CELL_FACH" and "Time to Trigger" , as shown in Figure 6-1.
Figure 6-1 Parameters configuration interface 1
In the configuration resource tree window, open the [Modify Area->Managed Element->
UMTS Logical Function Configuration->UTRAN Cell->EFachPch Configuration] interface
and set the parameters "Channel Type Indicator for Enhanced FACH/PCH Priority
Queue", "Discard Timer", "Re-ordering Release timer (T1)", "Reset Timer Controlling the
Reset of the MAC-ehs Reordering Functionality", "Discard Timer Configuration
Indication", "MAC-ehs Queue Identity", "MAC-ehs Window Size", "Maximum MAC-c PDU
Size for Flexible RLC PDU", "Maximum MAC-c PDU Size for Fixed RLC PDU" and
"Scheduling Priority Indicator for Enhanced FACH/PCH Priority Queue", as shown in
Figure 6-2.

UMTS Logical Function Configuration->UTRAN Cell->Extended Info of UTRAN Cell]
interface and set the parameters "Transport Band Width for Downlink Enhanced
CELL_FACH, CELL_PCH and URA_PCH" and “Maximum Number of Users on Downlink
Enhanced CELL_FACH”, as shown in Figure 6-3 and Figure 6-4.

UMTS Logical Function Configuration->UTRAN Cell] interface and set the parameter
"Downlink Enhanced CELL_FACH Support Indicator”, as shown in Figure 6-5.

6.3 Feature Validation Procedure
Table 6-1 Feature Validation Procedure
Test Item Enhanced DL CELL_FACH
1. WCDMA system is ready.

2. Both RNC and NodeB enable enhanced DL CELL_FACH.
3. Cell1 supports HSUPA, HSDPA and DCH.
Preconditio 4. Cell1 enables enhanced DL CELL_FACH.

ns 5. UE1 camps on Cell1 in Idle mode.
6. UE1 supports enhanced DL CELL_FACH.
7. UE1 subscribes interactive or background service, MBR=
UL2Mbps/ DL21Mbps.
1. UE1 activates a PS call in Cell1.

2. No need download any file, let UE channel switch from DCH to
Test Steps
FACH.
3. Deactivate the PDP after 5 minutes.
1. Check the NBAP message AuditResp to verify if the NodeB

supports Enhanced DL_FACH before step 1.
2. In step 1, check the rrcConnectionRequest message whether the
UE support EFACH function or not.
Anticipative
3. After step 2, check the IE “RRC State Indicator” in the message
Result
“Radio Bearer Reconfiguration” to confirm that the value is
"CELL_FACH". Check the IE “Transport Channel Type” IE to
confirm that the value is "HSDSCH".
4. Check the PS service normal.

6.4 Feature Deactivation Procedure
Table 6-2 RNC parameter list
Managed Object. Default Value Deactivation

GUI Name
logic name Value
Downlink Enhanced
UUtranCellFDD.eF CELL_FACH Support 0: Not 0: Not
ACHSpptInd Indicator Supported Supported
For the above parameters’ description and configuration, please refer to chapter 6.2
6.5 Network Impact
1. Impact on the device
None
2. Impact on the network KPI
i. The advantages of activating this feature are:
The enhanced DL CELL_FACH feature has the FACH's advantage of not

requiring dedicated resources and HS-DSCH's virtue of high transmission rate.
This feature is also suitable for the cells carrying services with frequent but
small data burst, which can alleviate the strain on the resources, makes these
cells accommodate more users. The more EFACH terminal exists, the greater
the gain is.
When there is service of frequent but small data burst in the cell, the enhanced
DL CELL_FACH feature allows the transmission of big data blocks in the
CELL_FACH state. In this way, the possibility of frequently converting to the
CELL_DCH state is reduced, which enhances the network resources
utilization, reduces the overall network signaling load, saves the UE power,
saves part of the dedicated resources and accommodates more users.

The throughput of enhanced DL CELL_FACH will be higher than that of FACH,

the users have better experience.
ii. The disadvantages of activating this feature are:
The cell's overall down link throughput may fluctuate: The enhanced DL
CELL_FACH users use HS-PDSCH channel to transmit data, these channels
was originally used by CELL_DCH state user, so data throughput of
CELL_DCH state users will decline if too many enhanced DL CELL_FACH
user take up too much HS-PDSCH channel, it will make the whole cell data
throughput dropped. It is required that operators make a balance between the
cell capacity and cell throughput. However, It is also possible the total number
of users in the cell is increased, increased data throughput from the new user
may be able to compensate the loss of throughput in CELL_DCH state, so the
total throughput of the cell also possible rise.
PS call drop rate maybe rise: Before the uplink Enhanced CELL_FACH is
deployed, there is no CQI \ ACK \ NACK feedback for the down link Enhanced
CELL_FACH data transmission, therefore, the transmission efficiency is not so
high as that of HS-DSCH in the CELL-DCH state, the call drop rate maybe
increases.
Notes:
After the deployment of the enhanced DL CELL_FACH feature, utilization of

the uplink RACH will increase and the RACH channel maybe gets congested.
If RACH is congested, it is suggested to adjust the threshold of traffic
measurement threshold of the enhanced DL CELL_FACH to restrict the
number of users in the enhanced DL CELL_FACH, modifying the UL transport
format of RACH is also an alternative way.
7 Abbreviation
Abbreviations Full Characteristics
3GPP 3rd Generation Partnership Project
BCCH Broadcast Control Channel

CCCH Common Control Channel
CQI Channel Quality Indicator
DCCH Dedicated Control Channel
DL Downlink
FDD Frequency Division Duplex
FACH Forward Access Channel
FP Frame Protocol
HSDPA High Speed Downlink Packet Access
HS-PDSCH High Speed Physical Downlink Shared Channel
HS-SCCH High Speed Shared Control Channel
PDU Protocol Data Unit
QoS Quality of Service
RAB Radio Access Bearer
RACH Random Access Channel
RNC Radio Network Controller
SDU Service Data Unit
SIB System Information Block
UE User Equipment
UL Up Link
UM Unacknowledged Mode
UTRAN UMTS Terrestrial Radio Access Network
UMTS Universal Mobile Telecommunication System
8 Reference Document
ZXUR 9000 UMTS (V4.15.10.20) Radio Network Controller Radio Parameter Reference
ZXUR 9000 UMTS (V4.15.10.20) Radio Network Controller Performance Counter

Reference
ZXWR RNC (V3.15.10.20) Radio Network Controller Radio Parameter Reference
ZXWR RNC (V3.15.10.20) Radio Network Controller Performance Counter Reference

ZTE UMTS HSPA Enhanced L2 Feature Guide
ZTE UMTS Dynamic Radio Bearer Control Feature Guide

Zte Umts Ur15 Enhanced DL Cell - Fach Feature Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Zte Umts Ur15 Enhanced DL Cell - Fach Feature Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Enhanced DL CELL_FACH

Compared with UR14,

© 2016 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 1

1 Feature Attribute ............................................................................................... 4

3 Technical Description ....................................................................................... 6

5 Related Counters and Alarms ........................................................................ 28

6 Engineering Guide .......................................................................................... 31

ZTE Confidential Proprietary 2

Table 2-1 License Control List ............................................................................................ 5

ZTE Confidential Proprietary 3

Node B version: [ZXSDR V4.15.10]

2.1 Feature Introduction

2.1.1 ZWF26-01-011 Enhanced DL CELL_FACH

ZTE Confidential Proprietary 4

Whether the UE supports the enhanced DL CELL_FACH feature is added to the UE

2.2 License Control

Table 2-1 License Control List

License Control Configured Sales

Enhanced Cell FACH Enhanced Cell

2.3 Correlation with Other Features

ZWF23-01-A Basic HSDPA

ZTE Confidential Proprietary 5

2. Mutually Exclusive Features

3.1 ZWF26-01-011 Enhanced DL CELL_FACH

ZTE Confidential Proprietary 6

3.1.1.1 Operating Principles of MAC Layer

Figure 3-1 Channels Mapped on HS-DSCH in the Enhanced DL CELL_FACH State

DCCH DTCH CCCH BCCH PCCH

 MAC-d header for DTCH and DCCH (mapped on HS-DSCH)

 When the UE uses the dedicated H-RNTI, only MAC-ehs header is

MAC-ehs MAC SDU

MAC-ehs U-RNTI MAC SDU

ZTE Confidential Proprietary 7

 MAC header for BCCH

MAC-ehs MAC SDU

 MAC header for CCCH

The MAC-ehs header contains the following information.

Figure 3-2 MAC-ehs Header

LCH-ID1 L1 TSN1 SI1 F1 LCH-IDk Lk TSNk SIk Fk

MAC-ehs header Reordering PDU Reordering PDU Padding (opt)

 SI (Segmentation Indication) field indicates if the MAC-ehs SDU has been

 LCH-ID (Logical Channel Identifier) field provides identification of the logical

 TSN (Transmission Sequence Number) field provides an identifier for the

ZTE Confidential Proprietary 8

Logical Channel Type

MAC-ehs queue identity UEFachPch.macehsQID[0] UEFachPch.macehsQID[1] UEFac

T1 UEFachPch.t1[0] UEFachPch.t1[1] UEFac

MAC-ehs window size UEFachPch.macehsWinSize[0] UEFachPch.macehsWinSize[1] UEFac

Treset UEFachPch.treset[0] UEFachPch.treset[1] UEFac

ZTE Confidential Proprietary 9

3.1.1.2 Operating Principles of RLC Layer

 For the signaling RB, fixed size mode only;

Logical Channel Type

RLC PDU SIZE for Fixed

RLC PDU SIZE for

3.1.1.3 The Measurement Mechanism of UE in the Enhanced DL CELL_FACH State

SFN = H-RNTI mod M_REP + n * M_REP (3.1.1.3-1)

ZTE Confidential Proprietary 10

 n =0,1,2… The SFN must be smaller than its maximum value.

3.1.1.4 Link Adjustment

HS-DSCH DATA Frame for Enhanced CELL_FACH

1..n MAC-d PDU