ZTE UMTS HSPA Evolution - Continuous Packet Connectivity Feature Guide - V8.5 - 201312

HSPA Evolution - Continuous
Packet Connectivity Feature

Guide
WCDMA RAN
HSPA Evolution - Continuous Packet Connectivity Feature Guide
HSPA Evolution - Continuous Packet Connectivity

Feature Guide
Version
V7.0
Date
2012-4-16
Author
Xu
Chunxiao
Reviewer
Jiang Qingsong
Revision History
Created
Updated to UR12
Lin Yumei
V8.0
2012-12-30
Cui Lili
Added relevant counters
Li Ling
Added CPC and F-DPCH counters
Added the parameters: UDtxDrxProfile (of
UDtxDrx
and
profileId
of
vsDataUDtxDrxProfile )
V8.5
2014-01-13
Zhang
Haiyan
Cui Lili
Described how to obtain the configurations of

the service-related DTX/DRX parameters
Added
the
parameter
URncFunction.GresPara12 and the related

description
2012 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
TABLE OF CONTENTS
1
Feature Attributes.............................................................................................. 5
Reference ........................................................................................................... 5
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.3
Overview ............................................................................................................ 6
Background of Continuous Packet Connectivity (CPC) ........................................ 6
ZWF26-01-A CPC ................................................................................................ 6
ZWF26-01-006 New UL DPCCH Slot Format ...................................................... 7
ZWF26-01-007 UL DTX ....................................................................................... 7
ZWF26-01-008 DL DRX ....................................................................................... 8
ZWF26-01-009 UL DRX in the Node B ................................................................ 8
ZWF26-01-005 HS-SCCH-less Operation ............................................................ 8
ZWF26-01-010 Enhanced F-DPCH ..................................................................... 9
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.2
4.2.1
4.2.2
Technical Descriptions ..................................................................................... 9

CPC ..................................................................................................................... 9
New UL DPCCH Slot Format ............................................................................... 9
UL DTX .............................................................................................................. 10
DL DRX ............................................................................................................. 14
UL DRX in the Node B ....................................................................................... 18
HS-SCCH-less Operation .................................................................................. 19
Enhanced F-DPCH ............................................................................................ 25
Background of E-FDPCH ................................................................................... 25
Key Technologies .............................................................................................. 30
5
5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.3
5.3.1
5.3.2
5.4
5.4.1
5.4.2
Parameters and Configurations ..................................................................... 30

Parameters Related to CPC ............................................................................... 30
Parameter List ................................................................................................... 30
Parameter Configurations .................................................................................. 30
Parameters Related to DTX-DRX ...................................................................... 31
Parameter List ................................................................................................... 31
Parameters Related to HS-SCCH-less Operation .............................................. 41
Parameter List ................................................................................................... 41
Parameters Related to Enhanced F-DPCH ........................................................ 44
Parameter List ................................................................................................... 44
6
6.1
6.2
Counters and Alarms ...................................................................................... 46

CPC Counters.................................................................................................... 46
F-DPCH Counters .............................................................................................. 47
Glossary ........................................................................................................... 47
FIGURES
Figure 4-1 UL DTX Pattern with Preambles and Postambles .............................................13
Figure 4-2 HS-SCCH Reception Pattern (2ms TTI E-DCH)................................................16
Figure 4-3 HS-SCCH Reception Pattern (10ms TTI E-DCH)..............................................16
Figure 4-4 UL DRX Procedure ...........................................................................................18
Figure 4-5 HS-SCCH Structure ..........................................................................................19
Figure 4-6 HS-PDSCH Multiplexing Configured with Multiple HS-SCCH Code Channels ..20
Figure 4-7 Frame Structure of F-DPCH .............................................................................25
Figure 4-8 Multiplexing Structure for Users Supporting the E-FDPCH ...............................28
Figure 4-9 Multiplexing Structure for Users Not Supporting the E-FDPCH .........................29
TABLES
Table 4-1 DPCCH Fields ...................................................................................................10
Table 4-2 F-DPCH Fields ...................................................................................................26
Table 4-3 F-DPCH/E-FDPCH Fields ..................................................................................27
Feature Attributes
System version: [RNC V3.12.10/RNC V4.12.10, Node B V4.12.10, OMMR V12.12.41,
OMMB V12.12.40]
Attribute: [Optional]
Involved NEs:
UE
Node B
RNC
MSCS
MGW
SGSN
GGSN
HLR
Note:
* -: Not involved
*: Involved
Dependency: [None]
Mutual exclusion: [None]
Reference
[1] 3GPP TS 25.999 V7.1.0 High Speed Packet Access (HSPA) evolution; Frequency
Division Duplex (FDD)
[2] 3GPP TS 25.211 V9.2.0 Physical channels and mapping of transport channels onto
physical channels (FDD)
[3] 3GPP TS 25.212 V9.4.0 Multiplexing and channel coding (FDD)
[4] 3GPP TS 25.213 V9.2.0 Spreading and modulation (FDD)
[5] 3GPP TS 25.214 V9.7.0 Physical layer procedures (FDD)
[6] 3GPP TS 25.215 V9.2.0 Physical layer; Measurements (FDD)
[7] 3GPP TS 25.321 V9.6.0 Medium Access Control (MAC) protocol specification
[8] 3GPP TS 25.322 V9.3.0 Radio Link Control (RLC) protocol specification
[9] 3GPP TS 25.433 V9.8.0 UTRAN Iub interface Node B Application Part (NBAP)
signaling
[10] 3GPP TS 25.435 V9.4.0 UTRAN Iub interface user plane protocols for Common
Transport Channel data streams
[11] 3GPP TS 25.331 V9.8.0 Radio Resource Control (RRC); Protocol specification
[12] 3GPP TS 25.308 V9.6.0 High Speed Downlink Packet Access (HSDPA); Overall
description; Stage 2
Overview
3.1
Background of Continuous Packet Connectivity

(CPC)
After HSPA is introduced in Release 5 and 6, the 3GPP starts to introduce new
technologies into Release 7 and later versions to enhance the capabilities and
performance of HSPA-based radio networks. HSPA networks will form an integral part of
future 3G systems and must provide a smooth path towards LTE. The CPC
described
in this document is included in this release.

Continuous Packet Connectivity (CPC) is used to avoid frequent connection
reestablishment, decrease transmission delay, and save power even if there is no data
transmission.
The purpose of the enhanced F-DPCH function is to improve DL channelized code
utilization efficiency and cell capacity.
3.2
ZWF26-01-A CPC
HSPA is introduced in 3GPP Release 5 and 6, as more packet services appear in
WCDMA networks. From end users perspectives: 1. Power consumption is the most
concerned issue. 2. Even if no data is received, the UE needs to transmit the DPCCH
and monitor the HS-SCCH. These features are intended to provide always-on
experience for end users by keeping the UEs in CELL_DCH for a longer time and
avoiding frequent state changes to low-activity states, as well as improving the capacity
for services.
Therefore, a set of Continuous Packet Connectivity (CPC) features (including UL DTX,
DL DRX, HS-SCCH-less, UL DRX in the Node B and new UL DPCCH slot format) are
introduced in Release 7.
UL DTX with low UL interference is used to increase UL service capacity and

reduce UE power consumption which is also applied to DL DRX.
HS-SCCH-less with low DL interference is used to increase DL service capacity and

reduce UE power consumption.
UL DRX in the Node B can reduce Node B processing resources. The new UL
DPCCH slot format is used to reduce UL control channel (no data transmission)
interference, thereby increasing UL capacity and reducing UE battery consumption.
3.2.1
ZWF26-01-006 New UL DPCCH Slot Format

According to 3GPP Release 6, the pilot domain occupies too many bits (8 bits at most) in
the DPCCH slot format for ensuring data decoding reliability. This strategy is used to
meet the needs of UL data transmission. When UL DTX is enabled, the purpose of
continuous DPCCH transmission (no UL data is
transmitted) is to perform
synchronization and power control, and achieve a rapid resumption of data transmission.
Therefore, new UL DPCCH slot format 4 (4 TPC symbols and 6 pilot symbols) is
introduced in 3GPP Release 7 to keep the balance between the reliability of channel
estimation and power control. As there is no TFCI or FBI field, the number of pilot bits is 6,
instead of 8. To improve power control reliability and reduce UL DPCCH transmit power,
the number of TPC bits is increased from 2 to 4.
3.2.2
ZWF26-01-007 UL DTX
According to 3GPP Release 6 and earlier, the UL DPCCH is transmitted all the time in
each slot. UL DTX introduced in Release 7 indicates that a UE will automatically execute
discontinuous uplink DPCCH transmission according to some patterns. If there is neither

E-DCH nor HS-DPCCH transmission, the UE will automatically stop continuous DPCCH
transmission and apply a known DPCCH activity pattern to reduce DPCCH transmission
and maintain uplink synchronization between the Node B and the UE.
When the E-DCH or HS-DPCCH starts transmitting data, the rapid resumption of
DPCCH transmission will be ready. To maintain uplink synchronization during the
inactivity, the DPCCH activity pattern must keep transmission state in a certain period of
time. There are two periods of time in UL DTX: UE_DTX_cycle_2 and UE_DTX_cycle_1.
3.2.3
ZWF26-01-008 DL DRX
DRX, to allow the UE to periodically switch off the receiver circuitry and save battery
power, and the network should use uplink DTX in combination with downlink DRX. DL
DRX periodically receives data using a known HS-SCCH reception pattern. During the
period of UL DTX, to make the UE remaining in a sleeping state more effectively DL
DRX and UL DTX should be consistent in transmission timing. This mechanism is
guaranteed through RNC parameters.
3.2.4
ZWF26-01-009 UL DRX in the Node B

As described in Release 6, the Node B must continuously detect E-DPCCH in each slot.
With the introduction of UL DRX in Release 7, during the period of UL DRX, the Node B
can discontinuously detect E-DPCCH to reduce Node B resources. UL DRX must be
activated when UL DTX is in activation.
3.2.5
ZWF26-01-005 HS-SCCH-less Operation

Aimed at real-time services such as VoIP, CS AMR over HSDPA, video, audio, and low
data package service continually transmitted in other downlink, the primary purpose of
introducing HS-SCCH-less is to reduce HS-SCCH control load, increase capacity, and
reduce HSDPA real-time service delay.
3.3
ZWF26-01-010 Enhanced F-DPCH

As mentioned in 3GPP Release 6, F-DPCH multiplexing between UEs can only be
achieved by time-multiplexing. In the case of soft handover, due to the unchangeable
timing relation based on the combination of RLs, the multiplexing opportunities of UEs
during soft handover will be greatly reduced. Therefore, 10 slot formats have been
introduced in F-DPCH to stagger slot positions and increase multiplexing opportunities.
Technical Descriptions
4.1
CPC
The CPC includes several functions described in the following sections. The
CpcSuptInd parameter is introduced to specify whether to support the CPC function in a
cell.
The new UL DPCCH slot format, UL DTX/ DL DRX, and HS-SCCH-less operation can be
applied independently. If the UL DRX in the Node B needs to be used, the UL DTX
should also be applied.
To support the DTX/DRX function, at least two switches should be ON: CpcSuptInd and
DtxDrxSwch. It should be noted that both UL DTX and DL DRX are controlled by the
DtxDrxSwch parameter. More switching parameters related to specified services are
described in the subsequent part.
To support the HS-SCCH-less operation, at least two switches should be ON:
CpcSuptInd and HsscLessSwch. More switching parameters related to specified
services are described in the subsequent part.
4.1.1
New UL DPCCH Slot Format

The new slot format (slot#4) defined in Release 7 is used in UL DTX. The UE slot format
can be configured or adjusted through the SRNC based on UE capabilities according to
different scenarios. There is no switch control for the use of UL DPCCH slot format 4,
which means that the activation/deactivation of the UL DPCCH slot format function only
depends on UE capabilities and specified algorithms, instead of any switch parameters
(including CpcSuptInd) or the activation/deactivation of any other CPC functions. The
parameters of the DPCCH slot format defined in 3GPP are listed as below.
Note: Generally, the new UL PDCCH slot format will improve the DPCCH transmit power
by 2 to 4 dB.
Table 4-1
DPCCH Fields
Slot
Channel
Channel
SF
Bits/
Bits/
Frame
Slot
Npilot
NTPC
NTFCI
NFBI
Transmitt
Format
Bit Rate
Symbol
(kbps)
Rate
per Radio
(kbps)
Frame
ed Slots
15
15
256
150
10
15
0A
15
15
256
150
10
10-14
0B
15
15
256
150
10
8-9
15
15
256
150
10
8-15
15
15
256
150
10
15
2A
15
15
256
150
10
10-14
2B
15
15
256
150
10
8-9
15
15
256
150
10
8-15
15
15
256
150
10
8-15
4.1.2
UL DTX
In order to use and manage the DTX/DRX function, the RNC provides the DtxDrxSwch
parameter to indicate whether DTX/DRX is allowed or not. Different strategies would be
provided in DTX/DRX according to different services.
For the real-time (RT) service, all non-voice CS services (such as fax and video) cannot
use DTX/DRX because of transmission continuity. Only the VoIP, AMR or I/B service will
possibly use discontinuous transmission. For the voice services (VoIP or CS Voice over
HSDPA) with short intervals during data transmission, the RtDtxSwch parameter can be
configured in the RNC flexibly to enable or disable this feature.
10
For the same reason, UL DTX will be controlled by the NrtDtxSwch parameter in the
RNC for non-real-time services.
Depending on different service characteristics, different services will require different
DTX/DRX configurations. The UDtxDrx and UDtxDrxProfile parameters are defined for
different sets of the DTX/DRX configuration. ZTE RAN equipment defines 2 default sets
of the DTX/DRX configuration: one is for voice services such as CS Voice over HSPA
and VoIP, and the other is for normal PS services. Of course, ZTE RAN equipment allows
the operator to define more sets of the DTX/DRX configuration if necessary. After the
DTX/DRX configuration is defined, the service should choose the defined DTX/DRX
configuration. The refUDtxDrxProfile parameter is used for the DTX/DRX configuration.
In terms of mobility, ZTE RAN equipment adopts the CpcDtxDrxSuptInd parameter to
indicate whether the neighboring DRNC cell can support the CPC DTX/DRX (It works
only when the RNC cannot get the CPC capability information of the neighboring DRNC
cell).
Note:
Service-related DTX/DRX parameters can be obtained by following these steps:
1)
Search UDtxDrxProfile from USubSrv.refUDtxDrxProfile.
2)
Get the corresponding profileId.
3)
Get the record information of the child MO UDtxDrx under the UDtxDrxProfile
instance (the configuration under UDtxDrx with the same UDtxDrxProfile value.)
4)
Get the UE DTX/DRX configuration information used by this service in the

USubSrv.
When discontinuous uplink DPCCH transmission is activated, the UE will activate the
periodic E-TFC selection every other MAC DTX cycle sub-frames, if there is no E-DCH
transmission for the consecutive MAC Inactivity Threshold-1 (corresponding to the
MacInactThresh parameter indicating the MAC inactivity threshold used for the periodic
E-TFC selection in every other MAC DTX cycle TTIs) E-DCH TTIs. There are two MAC
DTX cycle TTIs: MAC DTX cycle for 2ms TTI (MacDtxCycTti2 for 2ms E-DCH TTI) or
MAC DTX cycle for 10ms TTI (MacDtxCycTti10). If the actual maximum UE DTX cycle
of the neighboring DRNC cell cannot be achieved, the corresponding MaxDtxCyc
11
parameter is used to indicate the maximum UE DTX cycle supported by the neighboring
cell for continuous packet connectivity during the DTX-DRX operation.
UL DTX technical principles
UL DTX can be deactivated or activated by layer-1 HS-SCCH orders.

When UL DTX is activated, the UE will not transmit the uplink DPCCH in a slot if all of the
following conditions are met:
1.
There is no HARQ-ACK transmission on HS-DPCCH overlapping with the UL

DPCCH slot.
2.
There is no CQI transmission on HS-DPCCH overlapping with the UL DPCCH slot.
3.
There is no E-DCH transmission in the UL DPCCH slot.
4.
The slot is in DTX mode on the UL_DPCCH.
5.
The UL DPCCH preamble or postamble is not transmitted in the slot.
The DPCCH discontinuous transmission procedure in the UL DTX is described as

follows:
The
UL
DTX
pre-defines
two
discontinuous
DPCCH
transmission
periods:
UE_DTX_cycle_2 and UE_DTX_cycle_1 (respectively corresponding to DtxCyc1Tti2,

DtxCyc1Tti10 and DtxCyc2Tti2, DtxCyc2Tti10 in the case of 2ms TTI and 10ms TTI).
UE_DTX_cycle_2 is a multiple of UE_DTX_cycle_1. If there is not any uplink
transmission, the period of DPCCH periodic transmission is the UE_DTX_cycle_1
sub-frame. The number of sub-frames transmitted in each period is controlled by the
UE_DPCCH_burst_1 parameter (corresponding to DpcchBurst1). If there is not any
E-DCH transmission for the consecutive Inactivity_Threshold_for_UE_DTX_cycle_2
(DtxCyc2InactTrd2 or DtxCyc2InactTrd10 in the case of 2msTTI and 10msTTI) E-DCH
TTIs, the period should be changed to the UE_DTX_cycle_2 sub-frame. The number of
sub-frames transmitted in each period is controlled by the UE_DPCCH_burst_2
parameter
(corresponding
to
DpcchBurst2).
The
UE_DTX_cycle_1
and
UE_DPCCH_burst_1 parameters will be invalid.

The UL DTX pattern is illustrated in Figure 4-1.
12
Figure 4-1
UL DTX Pattern with Preambles and Postambles
During the UL DTX activation, the UE will transmit the DPCCH preamble and postamble
for synchronization. The specific procedures are described as follows:
1.
Preamble and postamble for the DPCCH transmission

If a UE starts the DPCCH transmission based on the uplink DPCCH burst pattern at
the start of slot s and finish its DPCCH transmission at the end of slot t, the UE
will start the DPCCH transmission at the start of slot s-2 and continue the DPCCH
transmission till the end of slot t+1.
2.
Preamble and postamble for the E-DCH transmission

If a UE starts the E-DPCCH and E-DPDCH transmission on an E-DCH TTI, the UE
will start the DPCCH transmission 2 slots prior to the E-DCH TTI and continue the
DPCCH transmission during the E-DCH TTI, consecutive E-DCH TTIs, and 1 slot
after the last consecutive E-DCH TTI.
If
there
is
not
any
E-DCH
transmission
for
the
last
Inactivity_Threshold_for_UE_DTX_cycle_2 E-DCH TTI and the UE starts the

E-DPCCH and E-DPDCH transmission on a E-DCH TTI, the UE will start the
DPCCH transmission on the UE_DTX_long_preamble_length (determining in
slots the length of the preamble associated with the UE_DTX_cycle_2) slots prior to
the E-DCH TTI, and continue the DPCCH transmission during the E-DCH TTI,
consecutive E-DCH TTIs, and 1 slot after the last consecutive E-DCH TTI.
3.
Preamble and postamble for the HS-DPCCH transmission

If a UE starts the HARQ-ACK transmission, the UE will start the DPCCH
transmission 2 slots prior to the DPCCH slot that coincides or overlaps with the start
of the HARQ-ACK field. The UE will continue the DPCCH transmission during the
13
HARQ-ACK field and until the end of the first full DPCCH slot after the end of the
HARQ-ACK field.
If a UE starts the CQI transmission, the UE will start the DPCCH transmission 3
slots prior to the DPCCH slot that coincides or overlaps with the start of the CQI
field, and continue the DPCCH transmission during the CQI field and until the end
of the first full DPCCH slot after the end of the CQI field.
If
there
is
no
any
E-DCH
transmission
for
the
last
Inactivity_Threshold_for_UE_DTX_cycle_2 E-DCH TTIs and the UE starts the CQI

transmission,
the
UE
will
start
the
DPCCH
transmission
(UE_DTX_long_preamble_length + 1) slots prior to the DPCCH slot that coincides or

overlaps with the start of the CQI field, and continue the DPCCH transmission during the
CQI field and until the end of the first full DPCCH slot after the end of the CQI field.
If a UE is in DTXDRX state and there is no data transmission for a long time, the UE
should be transitioned to URA_PCH state. The RNC introduces the DxHsBo0E4bThd
parameter. This parameter defines the times of the 4B events reporting for the state
transitioned from HSPA (CELL_DCH) state to URA_PCH state when the UE is in
DTXDRX state. When the UE is in DTXDRX state, the RAN will make the UE transition to
URA_PCH state, if the RLC buffers are empty in both uplink and downlink as well as the
times of 4B events reporting reaches the DxHsBo0E4bThd.
4.1.3
DL DRX
DL DRX Technical Principles
DL DRX can be deactivated or activated by layer-1 HS-SCCH orders. DL DRX is a

complement to UL DTX for limiting the receiving time of the UE on the downlink. When
DL DRX is enabled, the UE needs not receive downlink physical channels (such as
HS_SCCH, E-AGCH, and E-RGCH), except for the following cases:
1.
The UE shall receive E-HICH (sub-) frame corresponding to an E-DCH

transmission.
2.
The UE shall receive an HS-SCCH subframe due to the HS-SCCH reception

pattern.
14
3.
The UE shall receive an HS-PDSCH subframe due to correctly received HS-SCCH.
4.
The UE has received an HS-SCCH or an HS-PDSCH sub-frame during the last

Inactivity_Threshold_for_UE_DRX_cycle sub-frames, which is not an HS-SCCH
order.
5.
The UE has detected the E-AGCH transmission from the serving E-DCH cell.
6.
The UE has detected the E-RGCH transmission. Item 5 and item 6 are related to
the GrantMonInactTrd and DrxGrantMon parameters.
The GrantMonInactTrd parameter defines the number of sub-frames
(E-AGCH/E-RGCH) which are continuously monitored by the UE after the

transmission of E-DCH scheduling information, as well as indicates the
inactivity threshold of which UE will monitor the full E-AGCH in the serving
E-DCH cell and the full E-RGCH in E-DCH active set.
The DrxGrantMon parameter indicates whether the UE shall monitor the full
E-AGCH in the serving E-DCH cell and the full E-RGCH in E-DCH active set
when E-AGCH/E-RGCH overlaps with the start of discontinuous HS-SCCH
reception.
The HS-SCCH reception pattern is illustrated in Figure 4-2 for a 2ms TTI E-DCH and
Figure 4-3 for a 10ms TTI E-DCH.
15
Figure 4-2
HS-SCCH Reception Pattern (2ms TTI E-DCH)
- P-CCPCH
- F-DPCH
- Uplink DPCCH
Radio Frame, SFN mod 2 = 0
slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot slot
12 13 14
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14
0
1
2
3
4
5
6
7
8
12 13 14
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14
0
1
2
3
4
5
6
7
8
subframe4
subframe0
subframe1
subframe2
subframe3
subframe4
subframe0
subframe1
subframe2
Associated F-DPCH CFN=n
DPCH , n
T0 chips
DRX
HS-SCCH Discontinuous reception radio frame CFN_DRX = n

UE_DRX_cycle
- HS-SCCH
Subframe0
S_DRX=4
Subframe1
S_DRX=0
Subframe3
S_DRX=2
Subframe2
S_DRX=1
Subframe4
S_DRX=3
Subframe0
S_DRX=4
Subframe1
S_DRX=0
Subframe2
S_DRX=1
Subframe4
S_DRX=3
Subframe3
S_DRX=2
HS-PDSCH
- HS-PDSCH
- HS-DPCCH
S_DRX=4
S_DRX=0
S_DRX=1
S_DRX=2
HS-PDSCH
S_DRX=4
S_DRX=0
S_DRX=1
S_DRX=2
S_DRX=3
S_DRX=3
S_DRX=4
S_DRX=4
S_DRX=0
S_DRX=0
S_DRX=1
S_DRX=1
S_DRX=2
S_DRX=2
S_DRX=3
S_DRX=3
1280 chips
The grey sub-frames correspond to the HS-SCCH reception pattern (UE_DRX_cycle=4),

which is related to the DrxCycle parameter. This parameter indicates the HS-SCCH
reception pattern length (namely, the period for monitoring the HS-SCCH in unit of
sub-frames).
Figure 4-3
HS-SCCH Reception Pattern (10ms TTI E-DCH)
- P-CCPCH
- F-DPCH
- Uplink DPCCH
12 13 14
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14
0
1
2
3
4
5
6
7
8
12 13 14
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14
0
1
2
3
4
5
6
7
8
subframe4
subframe0
subframe1
subframe2
subframe3
subframe4
subframe0
subframe1
subframe2
Associated F-DPCH CFN=n
DPCH , n
T0 chips
DRX
HS-SCCH Discontinuous reception radio frame CFN_DRX = n

UE_DRX_cycle
- HS-SCCH
Subframe0
S_DRX=4
Subframe1
S_DRX=0
Subframe3
S_DRX=2
Subframe2
S_DRX=1
Subframe4
S_DRX=3
Subframe0
S_DRX=4
Subframe1
S_DRX=0
Subframe2
S_DRX=1
Subframe3
S_DRX=2
Subframe4
S_DRX=3
HS-PDSCH
- HS-PDSCH
- HS-DPCCH
S_DRX=4
S_DRX=0
S_DRX=1
HS-PDSCH
S_DRX=4
S_DRX=0
S_DRX=1
S_DRX=2
S_DRX=2
S_DRX=3
S_DRX=3
S_DRX=4
S_DRX=4
S_DRX=0
S_DRX=0
S_DRX=1
S_DRX=1
S_DRX=2
S_DRX=2
S_DRX=3
S_DRX=3
1280 chips
16
The
grey
sub-frames
correspond
to
the
HS-SCCH
reception
pattern
(UE_DRX_cycle=5).
Activation Strategy
DTX can be activated without DRX, but DRX has to be activated with DTX. In order to
enhance flexibility, DTX and DRX can be controlled separately.
For the real-time (RT) service, all non-voice CS services (such as fax and video) cannot
use DTX/DRX because of transmission continuity. Only the VoIP, AMR or I/B service will
possibly use discontinuous transmission. For the voice services (VoIP or CS Voice over
HSDPA) with short intervals during data transmission, the RNC switch parameter
(RtDtxSwch) and the DRX parameter (RtDrxSwch) can be configured
flexibly to
enable or disable this feature.

For the same reason, UL DTX will be controlled by the RNC switch parameter
(NrtDtxSwch) and the DRX parameter (NrtDrxSwch) for non-real-time services.
When all the conditions below are satisfied, the DTX or DRX function will be enabled:
1) It is not a VIP user, or a VIP user but a switch for allowing DTX/DRX function is
OPEN (bit 5 of the gResPara47 parameter).
2) Both the UE and Node B support DTX/DRX.
3) The cell CPC license switch (CpcSuptInd) is SUPPORT.
4) No DCH channel exists.
5) For a real-time service, if RtDtxSwch is ON, it can use DTX; if RtDrxSwch is ON, it
can also use DRX.
6) For a non-real-time service, if NrtDtxSwch is ON, it can use DTX; if NrtDrxSwch is
ON, it can also use DRX.
7) When several services are concurrent, if only one service cannot use DTX, it will not
use DTX. If it cannot use DTX, it will not use DRX.
When any activation condition changes, it is necessary to reconsider whether DTX/DRX
17
can be activated or not. When one service can use DTX/DRX but another concurrent
service cannot use DTX/DRX, this user cannot use DTX/DRX. However, when all the
services that cannot use DTX/DRX are released, the user can use DTX/DRX again. If all
the RBs are released and only signaling is left, the user cannot use DTX/DRX.
4.1.4
UL DRX in the Node B

Once UL DRX on the Node B side is enabled, the Node B can discontinuously detect
DPCCH on the premise of acquiring the re-transmission time in advance after the E-DCH
deactivation. The MAC_DTX_cycle parameter configured in the RNC strictly limits the
re-transmission time after the UE E-DCH deactivation. The MAC_Inactivity_Threshold
parameter indicates that, when there is no E-DCH transmission in the continuous
MAC_Inactivity_Threshold slots, the Node B will start discontinuous DPCCH detection
that is periodically done every other MAC_DTX_cycle slot. There is no control switch for
UL DRX configuration. UL DRX is illustrated in Figure 4-4.
Figure 4-4
UL DRX Procedure
UE Buffer
E-DCH
Transmission
MAC_Inactivity_
threshold
UE_DTX_ MAC_DTX_Cycle
DRX_Offset
MAC_DTX_Cycle
MAC_DTX_Cycle MAC_DTX_Cycle
CFN
DPCCH
Detect
18
4.1.5
HS-SCCH-less Operation
4.1.5.1
HS-SCCH-less Operation Principles

HS-SCCH introduced in Release 5 is a fixed-rate (60 Kbps, SF = 128) downlink physical
channel used to carry downlink signaling related to HS-PDSCH transmission. The
signaling carried on HS-SCCH with the QPSK modulation mode includes two parts
illustrated in Figure 4-5. The first part (Slot#0) information including the channel code and
modulation scheme which will be decoded during slot#1 is used to start HS-PDSCH
descrambling/dispreading at the start of Slot#2 for the avoidance of chip data buffering
on the UE side. The second part (Slot#1 & Slot#2) information including transport-block
size indicator, HARQ process number, RV parameter, and new data indicator which will
be decoded after the end of Slot#2 is applied to realize HS-PDSCH de-rate matching,
soft bit combining, Turbo decoding, and so on. However, if the information is not decoded,
the HS-PDSCH decoded chip data will be buffered.
Figure 4-5
HS-SCCH Structure
Data
Ndata 1 bits
Tslot = 2560 chips, 40 bits
Slot #0
Slot#1
Slot #2
1 subframe: Tf = 2 ms
As seen in the above figure, the number of bits transmitted during HS-SCCH 2ms TTI is
fixed.
Depending on the maximum number of users supported by code multiplexing, the
UTRAN will assign multiple HS-SCCHs with corresponding numbers. Each terminal can
monitor at most four HS-SCCHs. The number of HS-SCCHs can be reasonably
configured on the basis of HSDPA power and code channel resources. Generally, the
number of scheduled users in one TTI cannot exceed four to reduce HS-SCCH power
consumption and code channel resources. When the terminal continuously receives data,
19
the HS-SCCH will use the same code channel between TTIs to reduce the UE
complexity and increase the signaling reliability.
In the HSDPA, when the configured number of HS-SCCH code channel deciding
code-multiplexing schedule is only configured to one for the cell by the RNC, the
HS-PDSCH shared by multiple users can only serve one user in a TTI by
time-multiplexing. The scheduler will try to configure usable HSDPA resources (power
and code channel resources) in the cell for the same user.
When multiple HS-SCCH code channels are configured, the number of users scheduled
in one TTI must not exceed the number of code channels configured for HS-SCCH.
Figure 4-6
HS-PDSCH Multiplexing Configured with Multiple HS-SCCH Code Channels
In the HSDPA defined in Release 5, the UE must continuously monitor the HS-SCCH.
After obtaining the correlative control information through the specified HSDPA Radio
Network Temporary Identifier (H-RNTI), the UE will receive data from the corresponding
HS-PDSCH.
When compared with large data packet transmissions, the HS-SCCH overhead is
relatively small, but the transmission overhead of VoIP packets is relatively large.
Therefore, Release 7 introduces the HS-SCCH-less operation which may not transmit
HS-SCCH to increase VoIP capacity by introducing a special HS-PDSCH sub-frame
format. In the case of HS-SCCH-less operation with the introduction of new HS-SCCH
20
type 2 format (TS 25.212) and new CRC solution 2 for HS-DSCH, the UE blinding
detection instead of HS-SCCH transmission will be done during the first HS-PDSCH data
transmission when SRNC will pre-assign one or two HS-PDSCH code channels and at
most four types of MAC-hs transport block size for the purpose of the UE blinding
detection. During the first UE transmission, the correct decoding will send back the ACK
and conversely the UE will temporarily store the data but not send back the NACK. If the
first data transmission fails, the data retransmission, which needs HS-SCCH but does
not depend on the UE blinding detection any longer, should be started twice at most.
HS-SCCH-less operation without data transmission at the first time can reduce
HS-SCCH transmission interference, decrease HS-SCCH overhead, and increase
system capacity.
HS-SCCH-less operation using QPSK HS-PDSCH modulation mode cannot be
configured when the UE is in MIMO mode. Therefore, HS-SCCH-less operation is
applicable to small data services, especially for VoIP and other small data packet
services continually transmitted on the downlink (such as game and interactive
multimedia inquiring).
4.1.5.2
Key Technologies
4.1.5.2.1
RNC-Side Configuration
Depending on service characteristics on the RNC side, VoIP/CS AMR over HSPA can
use HS-SCCH-less. For other services, non-VoIP/CS AMR over HSPA services can
flexibly provide a specific switch to control the use of HS-SCCH-less which is disallowed
for the services whose thresholds are higher than the configured rate thresholds.
On the basis of above analysis, CELL_DCH HS-SCCH-less operation will be configured
if the following conditions are fulfilled:
A.
The RNC HS-SCCH-less switch (HsscLessSwch defined in HSPA+ Parameter

description->HS-SCCH-less parameter) should be ON, and the CPC cell support
switch (CpcSuptInd) should be ON.
B.
The service type will be VoIP, CS AMR or non-VoIP/CS AMR that uses the switch
(NVHsscLessSwch defined in HSPA+ Parameter description->HS-SCCH-less
21
parameter) to start up HS-SCCH-less. The biggest service speed is smaller than or

equal to the speed threshold (MaxRateWithNVHs defined in HSPA+ Parameter
description->HS-SCCH-less parameter controlling HS-SCCH-less use of
non-VoIP/CS AMR services). The cell CPC license (CpcSuptInd) is set to
SUPPORT.
C.
The DCH will be inexistent in the uplink and downlink. Specifically, there has not
been DPDCH in the uplink and F-DPCH is configured in the downlink. See also
3GPP TS 25.331 Actions related to HS_SCCH_LESS_STATUS variable.
D.
The UE will support HS-SCCH-less. According to the present protocol, the UE will
not support HS-SCCH-less if the HS-SCCH-less HS-DSCH operation support IE
is not included in the air-interface message.
E.
The HS-DSCH serving cell will support HS-SCCH-less. The Node B is indicated by
the Continuous Packet Connectivity HS-SCCH-less Capability parameter in the
Audio Response, RESOURCE STATUS INDICATION, and other messages.
F.
It is not a VIP user or it is a VIP user but the switch for allowing the VIP user to adopt
HS-SCCH-less is OPEN (bit 4 of the gResPara47 parameter).
With the HS-SCCH parameter configured, the Node B and UE will transmit and monitor
the frame format (type 1) of common HS-SCCH, so the concurrent services will start up
HS-SCCH-less if any service satisfies the above conditions.
Whenever the above HS-SCCH-less activation condition changes, the HS-SCCH-less
operation activation will be determined again. To fulfill mobility management, the
CpcHslessSuptInd parameter is used to indicate whether CPC HS-SCCH-less
operation is supported by the neighboring DRNC cell or not, if the actual HS-SCCH-less
ability of the neighboring DRNC cell cannot be obtained.
When the RRC connection is established, it will not configure HS-SCCH-less. During the
RB setup, reconfiguration and release, it will determine whether to configure
HS-SCCH-less according to the concurrent service situation. If all the RBs are released
and only signaling is left, it will not configure HS-SCCH-less.
22
4.1.5.2.2
Node B-Side Scheduling

On the Node B side, there are at most four types of MAC-hs TB format due to the
HS-SCCH-less operation. The Node B will distribute one or two HS-PDSCH OVSF
channel codes specially used for HS-SCCH-less data transmission. When the first
HS-PDSCH transmission during which the concomitant HS-SCCH would not be
transmitted is successfully decoded, the ACK will be fed back to the Node B. Conversely,
when the decoding is failed without any NACK feedback, the Node B will process the
HS-PDSCH re-transmission (at most twice) and transmit the concomitant HS-SCCH
using new HS-SCCH type 2. For the re-transmission, the ACK/NACK feedback which
has the same method as that of HS-SCCH type 1 will be implemented in HS-DPCCH. As
mentioned above, the HS-SCCH-less operation configured by the UE is not coercively
required. The UE can continue the HS-SCCH type 1 receiving and try to schedule using
common HS-SCCH type 1 in HS-SCCH-less mode configured by the HSDPA scheduler.
Because the characteristic for the concomitant HS-SCCH control channel not to be
transmitted during the first transmission in HS-SCCH-less mode is absolutely different
from the scheduling criteria and procedures of other users, HS-SCCH-less users should
be independently considered to add the scheduling pattern of the first transmission to the
scheduling pattern design. The scheduling information of one HS-SCCH-less user who is
satisfied with the scheduling condition will be written into the new defined scheduling
pattern. The re-transmission identifier will be cleared when the ACK is received. The
procedure for processing HS-SCCH-less user re-transmission includes the scanning of
the new defined scheduling pattern and the search of the user required to
re-transmission. Due to the concomitant HS-SCCH control channel, the scheduling
information of re-transmissions (at most twice) will be written into the scheduling pattern
of the common user.
4.1.5.2.3
Scheduling Algorithm Supporting the HS-SCCH-less Operation

During a new transmission, the scheduling priority of the user supporting HS-SCCH-less
operation (including real-time VoIP/CS services or non-real-time packet services) will be
calculated. When one or two specific code channels are configured for multiple users, a
user with a higher priority will use the specified code channel. A user with a lower priority,
whose preconfigured code channel is used by the user with the higher priority, will be
23
delayed to be scheduled in the next TTI. According to the CQI feedback, the scheduled
UE will select one of four transport block sizes.
The HS-SCCH-less operation will support two re-transmissions within the limited time. In
HS-SCCH type 2, the last transmission indicator IE used for the HARQ combination of
the re-transmission and new transmission will indicate the time relation between them.
When the re-transmitted HS-SCCH-less UE is configured with the code channel, the
following steps are included:
1.
The UE will use the pre-configured code channel.
2.
The other reserved HS-SCCH-less code channels will be considered when the
pre-configured code channel is occupied.
3.
The non-reserved HS-SCCH-less code channels will be considered.
HS-SCCH-less can increase the capacity of the users supporting this operation. Due to
the increasing of the Full Buffer service throughput with the moderate number of
HSSCCH_LESS users and the little increasing of the Full Buffer service throughput with
the smaller number of HS-SCCH-less users on the basis of released HS-SCCH, the UE
supporting HS-SCCH-less can quit this operation to save the battery power loss. Under
the HS-SCCH-less operation, more battery power loss is caused by the DRX
performance reducing for the blinding detection of four transport blocks and HS-PDSCH
detection. When the HS-SCCH-less operation that cannot be configured in MIMO mode
is deactivated, the Node B will only schedule HS-SCCH type 1. Furthermore, the
HS-SCCH-less scheduling will be considered on the basis of the HS-SCCH-less
activation time after which Node B scheduler will decide whether HS-SCCH-less is used.
4.1.5.2.4
Judgment of the Support of HS-SCCH order under HS-SCCH-less Operation for the
UE
Node B should know whether UE supports HS-SCCH order under HS-SCCH-less in
order to consider this capability when schedules. The judgment is made by RNC as
follows:
24
When one of the following conditions is satisfied, UE does not support HS-SCCH
order under HS-SCCH-less operation:
UE is before REL 8;
UE does not support HS-SCCH Less;
UE is REL8 or later version, and UE supports HS-SCCH Less, but bit4 of

GresPara12
is 0.
When UE is REL8 or later version, and bit4 of GresPara12
is 1, and UE supports
HS-SCCH Less, UE is considered to support HS-SCCH order under HS-SCCH-less

operation.
4.2
Enhanced F-DPCH
4.2.1
Background of E-FDPCH
F-DPCH is introduced in 3GPP Release 6. For the purpose of downlink code resource
saving, one F-DPCH can be used by multiple users in time-multiplexing. When F-DPCH
is configured, the UE is not required to be configured with the associated DPCH. The
following figure shows the frame structure of the F-DPCH with the fixed SF=256.
Figure 4-7
Frame Structure of F-DPCH
512 chips
(Tx OFF)
TPC
NTPC bits
(Tx OFF)
Tslot = 2560 chips
Slot #0
Slot #1
Slot #i
Slot #14
1 radio frame: Tf = 10 ms
25
There is only one F-DPCH slot format in 3GPP Release 6. The exact number of bits in
the F-DPCH fields (NTPC) is shown in the following table:
Table 4-2
F-DPCH Fields
Slot Format Channel Bit

#
0
Rate (kbps)
3
F-DPCH
Channel
Symbol
SF
Bits/Slot
Bits/ Slot
Rate (ksps)
1.5
NTPC
256
According to the F-DPCH frame structure, the TPC bit in the same slot only occupies 256
chips and the other bits in this slot use DTX. Therefore, at most 10 UEs can be
multiplexed into an F-DPCH (there are 2560 chips in one slot).
The F-DPCH timing may be different for different UEs, but the offset from the P-CCPCH
frame timing is a multiple of 256 chips, for example, F1, , 149}.
In 3GPP Release 6, the F-DPCH multiplexing only can be implemented in
time-multiplexing. In case of soft handover, the F-DPCH multiplexing opportunity for the
UE will be greatly reduced due to the unchangeable timing relation between PCCPCH in
combination of multiple RLs. In order to resolve this problem, ten fixed slot formats have
been introduced into the F-DPCH multiplexing in Release 7. Their characteristics are
different from each one and the locations of TPC bit fields in one slot are staggered. In
case of the same timing deviation, the F-DPCH multiplexing for different users can be
implemented by configuring different slot formats. Compared with 3GPP Release 6, the
Enhanced F-DPCH (E-FDPCH) improves the multiplexing opportunity for the UE during
soft handover and achieves full multiplexing.
4.2.1.1
F-DPCH Multiplexing Technique

In order to solve the time-multiplexing problem during soft handover, 10 slot formats have
been introduced in the F-DPCH to stagger the slot positions and the locations of TPC bit
fields in one slot. Therefore, the E-FDPCH, as compared with that in Release 6, is to
increase the multiplexing opportunity for the UE during soft handover and achieves full
multiplexing.
26
4.2.1.2
E-FDPCH Slot Structure and Frame Format

(Tx OFF)
NOFF1 bits
(Tx OFF)
NOFF2 bits
TPC
NTPC bits
Tslot = 2560 chips
Slot #0 Slot #1
Slot #i
Slot #14
1 radio frame: Tf = 10 ms
Table 4-3
Slot
F-DPCH/E-FDPCH Fields
Channel
Channel
Bits/
NOFF1
NTPC
NOFF2
Format # Bit Rate
Symbol
Slot
Bits/Slot
Bits/Slot
Bits/Slot
(kbps)
Rate
SF
(ksps)
0
1.5
256
20
16
1.5
256
20
14
1.5
256
20
12
1.5
256
20
10
1.5
256
20
10
1.5
256
20
12
1.5
256
20
14
1.5
256
20
16
1.5
256
20
18
1.5
256
20
18
As seen in the above table, different slot format gives the different positions of TPC bits
transmitted in one slot. The F-DPCH slot format is configured through the CRNC. The set
of multiplexing is independent for different cells.
27
4.2.1.3
E-FDPCH Multiplexing Technique
4.2.1.4
The living network and UE capabilities should be considered for the E-FDPCH
multiplexing deployment.
For the Node B and UE enabled with the E-FDPCH function, the multiplexing is
independent to the F-DPCH frame offset configuration, and the UEs (same configuration
of F-DPCH frame offset) can be multiplexed by different slot formats, as shown in the
following figure.
Figure 4-8
Multiplexing Structure for Users Supporting the E-FDPCH
PCCPCH slot
Pink is occupied 256 chip margin; yellow is occupied 256 chip margin by new
multiplexing user
256 slot margin use
of maintenance and
suppositional FDPCH
F-DPCH when
UE1 accessing
TPC
The first idle

256 chip
margin is 1.
DOFF decides: UE1

slot start relative to
256 chip margin of
Y=2.
256 chip margin (F-DPCH) occupied by TPC bit is 9 and

the slot format is 8.
TPC
F-DPCH when
UE1 accessing
DOFF decides: UE1 slot start
relative to 256 chip margin of Y=1.
256 chip margin (F-DPCH) occupied by

TPC bit is 3 and the slot format is 2.
The first idle 256 chip margin is 4.
There is only one slot format available in the F-DPCH cell (3GPP Release 6), so the
F-DPCH frame offset is also the only one factor to be considered in multiplexing. But for
the E-FDPCH cell, the UEs (in Release 6 and Release 7) may be in the cell
simultaneously. In order to multiplex the F-DPCH channel for the UEs in Release 6 and
Release 7, an amendment solution is introduced. The multiplexing method of UEs (in
Release 6 and Release 7) is shown in the following figure.
28
Figure 4-9
Multiplexing Structure for Users Not Supporting the E-FDPCH
PCCPCH slot
Pink is occupied 256 chip margin; yellow is occupied 256 chip margin by new
multiplexing user
256 slot margin use
of maintenance and
suppositional FDPCH
TPC
F-DPCH when
UE1 accessing
256 chip margin (F-DPCH) occupied by TPC bit is Z=1.

The first idle
DOFF decides: UE1
256 chip
slot start relative to
margin is X=1. 256 chip margin of
Y=2.
After multiplexing
(UE1)
TPC
After multiplexing, UE1 start slot is prior to two, -(Y+Z)+X, 256

chip.
TPC
F-DPCH when
UE1 accessing
256 chip margin (F-DPCH) occupied by TPC bit is Z=1.
DOFF decides: UE2 slot start

relative to 256 chip margin of Y=1.
After multiplexing
(UE2)
The first idle 256 chip margin is X=4.

TPC
After multiplexing, UE2 start slot is later to two, -(Y+Z)+X, 256

chip.
Regardless of whether the UE has the E-DFPCH capability or not, time-multiplexing in

the E-FDPCH cell can be used. Actually, the enhanced multiplexing algorithm also deals
with the 256-chip margin of TPC. Therefore, the multiplexing of UEs in Release 6 and
Release 7 can be used in the F-DPCH with the same channel code in the E-FDPCH cell.
The two differences between Release 6 and Release 7(and beyond) for UEs are
described as follows:
For UEs in Release 6, an amendment solution is used. For UEs in Release 7, the
original solution is used and the multiplexing F-DPCH uses the same channel code.
For UEs in Release 6, the F-DPCH slot format should not be transmitted to the UEs.
For UEs in Release 7, the F-DPCH slot format should be transmitted to the UEs.
29
4.2.2
Key Technologies
4.2.2.1
Mobility Management Affected by the E-FDPCH

The cells supporting or not supporting the E-FDPCH may be adjacent cells. The F-DPCH
multiplexing technique in each cell is independent. So these two kinds of cells can be in
the same active set.
4.2.2.2
RNC Configuration Strategy

The E-FDPCH function is configured on the RNC side, the main parameters include:
RncFdpchSupInd,
FdpchSuptInd,
FdpchSuptInd,
RncEfdpchSupInd,
EfdpchSupInd, and EfdpchSupInd.
Parameters and Configurations
5.1
Parameters Related to CPC
5.1.1
Parameter List
Name
1
CpcSuptInd
Interface Name
Cell CPC Support Indicator
5.1.2
Parameter Configurations
5.1.2.1
Cell CPC Support Indicator
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell
Parameter configuration
This parameter indicates whether the cell supports the CPC function or not.
30
5.2
Parameters Related to DTX-DRX
5.2.1
Parameter List
Name
Interface Name
DtxDrxSwch
DTX/DRX Switch
RtDtxSwch
DTX Switch for RT
RtDrxSwch
DRX Switch for RT
NrtDtxSwch
DTX Switch for NRT
NrtDrxSwch
DRX Switch for NRT
UDtxDrx
UE DTX/DRX Configuration Object ID
UDtxDrxProfile(of
vsDataUDtxDrxPr
UE DTX/DRX Profile Object ID
ofile)
8
refUDtxDrxProfile
Used UDtxDrxProfile
MacDtxCycTti2
MAC DTX Cycle for 2ms TTI
10
MacDtxCycTti10
11
MacInactThresh
MAC Inactivity Threshold
12
DtxCyc1Tti2
UE DTX Cycle 1 for 2ms TTI
13
DtxCyc1Tti10
14
DtxCyc2Tti2
15
DtxCyc2Tti10
16
DpcchBurst1
UE DPCCH Burst_1
17
DpcchBurst2
UE DPCCH Burst_2
18
DtxCyc2InactTrd2
Inactivity Threshold for UE DTX Cycle 2 for 2ms TTI
19
DtxCyc2InactTrd1
0
20
DtxLongPreLegth
UE DTX Long Preamble Length
21
CqiDtxTimer
CQI DTX Timer
22
DrxCycle
UE DRX Cycle
23
DrxCycInactTrd
Inactivity Threshold for UE DRX Cycle
24
GrantMonInactTrd
Inactivity Threshold for UE Grant Monitoring
25
DrxGrantMon
UE DRX Grant Monitoring
31
Name
26
CpcDtxDrxSuptIn
d
Interface Name
CPC DTX-DRX Support Indicator
27
MaxDtxCyc
Max UE DTX Cycle
28
GresPara47
Global Reserved Parameter 47
29
UDtxDrxProfile(of
UDtxDrx )
30
profileId( of
vsDataUDtxDrxPr
UE DTX/DRX Configuration Index
ofile )
5.2.2
5.2.2.1
DTX/DRX Switch
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->Service Configuration
This parameter is the main DTX/DRX switch to indicate whether the RNC grants
DTX/DRX. When the switch is on, DTX/DRX is granted; otherwise, DTX/DRX is
forbidden.
5.2.2.2
DTX Switch for RT
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Configuration->Hspa Configuration
This parameter is the DTX switch for speech to indicate whether the RNC grants DTX.
When the switch is on, DTX is granted; otherwise, DTX is forbidden.
32
5.2.2.3
DRX Switch for RT
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter is the DRX switch for speech to indicate whether the RNC grants DRX.
When the switch is on, DRX is granted; otherwise, DRX is forbidden.
5.2.2.4
DTX Switch for NRT
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter is the DTX switch for non-real-time services indicating whether DTX is
allowed to be used. If the switch is On, the non-real-time services are allowed to use
DTX. Otherwise, they are not allowed to use it.
5.2.2.5
DRX Switch for NRT
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter is the DRX switch for non-real-time services indicating whether DRX is
allowed to be used. If the switch is On, the non-real-time services are allowed to use
DRX. Otherwise, they are not allowed to use it.
33
5.2.2.6
UE DTX/DRX Configuration Object ID
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UE DTX/DRX Profile->UE DTX/DRX Configuration
This parameter indicates the UE DTX/DRX profile object ID.
5.2.2.7
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->UE DTX/DRX Profile
5.2.2.8
Used UDtxDrxProfile
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
Configuration->Service Function->Service Basic Configuration
This parameter is the UE DTX/DRX configuration index which indicates a set of

DTX/DRX configurations. Each service obtains the DTX/DRX parameters according to
the UE DTX/DRX configuration index.
5.2.2.9
OMC path
34
GUI:
Managed
Element
->UMTS
Logical
Function
This parameter indicates the discontinuous cycle used for the E-TFC selection in unit of
sub-frames when E-DCH 2ms TTI is used.
5.2.2.10
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the discontinuous cycle used for the E-TFC selection in
unit of sub-frames when E-DCH 10ms TTI is used.
5.2.2.11
MAC Inactivity Threshold
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the MAC inactivity threshold used for the E-TFC selection in
unit of TTIs.
5.2.2.12
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
35
This parameter indicates the discontinuous cycle used for UL DTX_1 in unit of
5.2.2.13
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
5.2.2.14
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
5.2.2.15
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
36
5.2.2.16
UE DPCCH Burst_1
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the number of DPCCH sub-frames used for the RL
synchronization in DTX controlled by UE DTX Cycle 1 in unit of sub-frames.
5.2.2.17
UE DPCCH Burst_2
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the number of DPCCH sub-frames used for the RL
synchronization in DTX controlled by UE DTX Cycle 2 in unit of sub-frames.
5.2.2.18
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the DTX inactivity threshold controlled by UE DTX cycle 2 in
unit of TTIs when E-DCH 2ms TTI is used.
37
5.2.2.19
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the DTX inactivity threshold controlled by UE DTX cycle 2
in unit of TTIs when E-DCH 10ms TTI is used.
5.2.2.20
UE DTX Long Preamble Length
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the number of prior transmitted DPCCH slots after the UE
enters DTX controlled by UE DTX cycle 2 in unit of slots.
5.2.2.21
CQI DTX Timer
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the prior DTX timer length reported through the CQI in unit of
sub-frames.
38
5.2.2.22
UE DRX Cycle
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the HS-SCCH cycle for UE monitoring in unit of sub-frames.
5.2.2.23
Inactivity Threshold for UE DRX Cycle
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the inactivity threshold for UE transferring to monitor HS-SCCH
every other sub-frame cycle of UE DRX in unit of sub-frames.
5.2.2.24
Inactivity Threshold for UE Grant Monitoring
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the inactivity threshold for UE monitoring full E-AGCH in the
E-DCH serving cell and full E-RGCH in the E-DCH active set after E-DCH data
transmission in unit of TTIs.
5.2.2.25
UE DRX Grant Monitoring
OMC path
39
GUI:
Managed
Element
->UMTS
Logical
Function
This parameter indicates whether UE shall monitor full E-AGCH in E-DCH serving cell
when the start of E-AGCH/E-RGCH/HS-SCCH DRX overlap in E-DCH active set after
E-DCH data transmission.
5.2.2.26
CPC DTX-DRX Support Indicator
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates whether the CPC DTX-DRX operation is supported by the
neighboring cell or not.
5.2.2.27
Max UE DTX Cycle
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates the maximum UE DTX cycle supported by the neighboring
DRNC cell for CPC DTX-DRX operation.
5.2.2.28
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->Global Reserved
40
Parameter 47
Bit 5 is the VIP user DTX/DRX configuration switch (0: Close; 1: Open).
5.2.2.29
UE DTX/DRX Profile Object ID (of UDtxDrx)
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
5.2.2.30
UE DTX/DRX Configuration Index
OMC path
GUI: Managed
Element
->UMTS Logical
Function
Configuration->UE DTX/DRX Profile
This parameter is the UE DTX/DRX configuration index which indicates a set of

DTX/DRX configurations.
5.3
Parameters Related to HS-SCCH-less Operation
5.3.1
Parameter List
Name
Interface Name
HsscLessSwch
HS-SCCH Less Switch
NVHsscLessSwch
HS-SCCH Less Switch for Non-VoIP/AMR
MaxRateWithNVHs
Maximum Bit Rate with HS-SCCH Less for Non-VoIP/AMR
41
Name
Interface Name
CpcHslessSuptInd
CPC HS-SCCH less Support Indicator
GresPara47
GRESPARA12
5.3.2
5.3.2.1
HS-SCCH Less Switch
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter is the HS-SCCH-less switch to indicate whether the RNC grants
HS-SCCH-less. When the switch is on, HS-SCCH-less is granted; otherwise,
HS-SCCH-less is forbidden.
5.3.2.2
HS-SCCH Less Switch for Non-VoIP/AMR
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter is the HS-SCCH-less switch for non-VoIP/AMR services to indicate

whether the RNC grants HS-SCCH-less for non-VoIP/AMR services. When the switch is
on, HS-SCCH-less is granted; otherwise, HS-SCCH-less is forbidden.
5.3.2.3
Maximum Bit Rate with HS-SCCH Less for Non-VoIP/AMR
OMC path
42
GUI: Managed Element ->UMTS Logical Function Configuration
This parameter is the HS-SCCH-less rate threshold for a non-VoIP/AMR service. When
the switches of both HS-SCCH-less and HS-SCCH-less for the non-VoIP/AMR service
are on, the non-VoIP/AMR service can use the HS-SCCH-less function even if the
assigned maximum bit rate is smaller than the rate threshold.
5.3.2.4
CPC HS-SCCH less Support Indicator
OMC path
GUI: Managed Element ->UMTS Logical Function Configuration->External Resource

Configuration->External RNC Function->External UTRAN Cell
This parameter indicates whether the CPC HS-SCCH-less operation is supported by the
neighboring cell or not.
5.3.2.5
OMC path

Parameter 47
Bit 4 is the VIP user HS-SCCH-less configuration switch (0: Close; 1: Open).
5.3.2.6
OMC path

Parameter 12
43
Bit 4 indicates whether the support capability of HS-SCCH orders in HS-SCCH-less

operation should be sent to Node B for REL 8 and onwards UE.
5.4
Parameters Related to Enhanced F-DPCH
5.4.1
Parameter List
Name
Interface Name
RncEfdpchSupInd
RNC Enhanced F-DPCH Support Indicator
RncFdpchSupInd
RNC F-DPCH Support Indicator
FDpchSuptInd
F-DPCH Support Indicator
FDpchSuptInd
Cell F-DPCH Support Indicator
EfdpchSupInd
Neighboring Cell Enhanced F-DPCH Support Indicator
EfdpchSupInd
Cell Enhanced F-DPCH Support Indicator
5.4.2
5.4.2.1
RNC Enhanced F-DPCH Support Indicator
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
This parameter indicates whether the RNC supports the enhanced F-DPCH or not.
5.4.2.2
RNC F-DPCH Support Indicator
GUI:
OMC path
Managed
Element
->UMTS
Logical
Function
44
This parameter indicates whether the RNC supports the F-DPCH.
5.4.2.3
F-DPCH Support Indicator
OMC path

This parameter indicates whether the neighboring DRNC cell supports the F-DPCH.
5.4.2.4
Cell F-DPCH Support Indicator
OMC path
This parameter indicates whether the cell supports the F-DPCH.
5.4.2.5
Neighboring Cell Enhanced F-DPCH Support Indicator
OMC path

This parameter indicates whether the neighboring DRNC cell supports the enhanced
F-DPCH.
45
5.4.2.6
Cell Enhanced F-DPCH Support Indicator
OMC path
This parameter indicates whether the cell supports the enhanced F-DPCH or not.
Counters and Alarms
6.1
CPC Counters
No.
Counter Name
C310183496
Number of attempted CPC(hs-scch less) RB setup
C310186958
Number of attempted CPC(dtx/drx) RB setup
C310183501
Number of failed
CPC(hs-scch less) RB setup
C310186959
Number of failed
CPC(dtx/drx) RB setup
C311863506
Total number of
C311866960
Total number of
C310253511
Number of RAB abnormal release for CPC(hs-scch less)
C310256961
Number of RAB abnormal release for CPC(dtx/drx)
C310040553
Holding time of CPC(hs-scch less),Conversational class,on best cell
C310040554
Holding time of CPC(hs-scch less),Streaming class,on best cell
C310040555
Holding time of CPC(hs-scch less),Interactive class,on best cell
C310040556
Holding time of CPC(hs-scch less),Background class,on best cell
C310040871
Holding time of CPC(dtx/drx),Conversational class,on best cell
C310040872
Holding time of CPC(dtx/drx),Streaming class,on best cell
C310040873
Holding time of CPC(dtx/drx),Interactive class,on best cell
C310040874
Holding time of CPC(dtx/drx),Background class,on best cell
C310030560
Number of CPC(hs-scch less) users in the best cell
C310030875
Number of CPC(dtx/drx) users in the best cell
C310030564
Max Number of CPC(hs-scch less) users in the best cell
CPC(hs-scch less) RB release

CPC(dtx/drx) RB release
46
6.2
C310030876
Max Number of CPC(dtx/drx) users in the best cell
C310030568
Average Number of CPC(hs-scch less) users in the best cell
C310030877
Average Number of CPC(dtx/drx) users in the best cell
C310030581
Number of Conversational class in CPC(hs-scch less) in the best cell
C310030582
Number of Streaming class in
CPC(hs-scch less) in the best cell
C310030583
Number of Interactive class in
C310030584
Number of Background class in
C310030878
Number of Conversational class in CPC(dtx/drx) in the best cell
C310030879
Number of Streaming class in
CPC(dtx/drx) in the best cell
C310030880
Number of Interactive class in
C310030881
Number of Background class in
C310630624
Max Number of CPC(hs-scch less) users in RNC
C310630627
Max Number of CPC(dtx/drx) users in RNC
C310800129
Max Number of CPC(hs-scch less) users in NodeB
C310800148
Max Number of CPC(dtx/drx) users in NodeB
C310800147
Current Number of CPC(hs-scch less) users in NodeB
C310800149
Current Number of CPC(dtx/drx) users in NodeB
C372490203
Number of DL_DRX User
C372490204
Number of UL_DTX User
C372490205
Ratio of DL_DRX User
C372490206
Ratio of UL_DTX User
F-DPCH Counters
No.
C311786820
Counter Name
Number of UE in F-DPCH Code Reassign due to Code Re-assignment
Number of DPCH /F-DPCH Code Reassign Failure due to Code
C311785738
Re-assignment
C311786827
Number of UE to Release F-DPCH due to Code Re-assignment
Glossary
AM
Acknowledge Mode
47
AMC
Adaptive Modulation and Coding
Background
Conversation
CPC
Continuous Packet Connectivity
CN
Core Network
CQI
Channel Quality Indicator
DCCH
Dedicated Control Channel
DCH
Dedicated Channel
DL
Downlink
DRBC
Dynamic Radio Bearer Control
DTCH
Dedicated Traffic Channel
E-DCH
Enhanced uplink DCH
FACH
Forward Access Channel
F-DPCH
Fractional DPCH
FDD
Frequency Division Duplex
FP
Frame Protocol
GBR
Guaranteed Bit Rate
HS-DSCH
High Speed Downlink Shared Channel
HS-SCCH
High Speed Shared Control Channel
HSDPA
High Speed Downlink Packet Access
HSPA
High Speed Packet Access
48
Interactive
IMS
IP Multimedia Subsystem
L2
Layer 2
LCH
Logical CHannel
LI
Length Indicator
MAC
Media Access Control
MaxBR
Maximum Bit Rate
MBMS
Multimedia Broadcast Multicast Service
MCCH
MBMS point-to-multipoint Control Channel
MSCH
MBMS point-to-multipoint Scheduling Channel
MTCH
MBMS point-to-multipoint Traffic Channel
NBAP
Node B Application Protocol
PCH
Paging Channel
PDP
Packet Data Protocol
PDU
Protocol Data Unit
P-T-M
Point-to-Multipoint
P-T-P
Point-to-Point
QAM
Quadrature Amplitude Modulation
QoS
Quality of Service
QPSK
Quadrature Phase Shift Keying
RAB
Radio access bearer
49
RACH
Random Access Channel
RANAP
Radio Access Network Application Protocol
RB
Radio Bearer
RL
Radio Link
RLC
Radio Link Control
RNC
Radio Network Controller
RNSAP
Radio Network Subsystem Application Protocol
ROHC
Robust Header Compression
RRC
Radio Resource Control
RTCP
Real time Control Protocol
RTT
Round Trip Time
PO
Power Offset
Streaming
S-CCPCH
Secondary Common Control Physical Channel
SDU
Service Data Unit
SF
Spreading Factor
SIP
Session Initiation Protocol
SN
Sequence Number
SUFI
SUper FIeld
TTI
Transmission Time Interval
TF
Transport Format
50
TFCS
Transport Format Combination Set
TxP
Transmission Power
UE
User Equipment
UL
Uplink
UM
Unacknowledged Mode
UTRAN
Universal Terrestrial Radio Access Network
VoIP
Voice over IP
51

ZTE UMTS HSPA Evolution - Continuous Packet Connectivity Feature Guide - V8.5 - 201312

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE UMTS HSPA Evolution - Continuous Packet Connectivity Feature Guide - V8.5 - 201312

Загружено:

Авторское право:

Доступные форматы

HSPA Evolution - Continuous

Packet Connectivity Feature

HSPA Evolution - Continuous Packet Connectivity Feature Guide

HSPA Evolution - Continuous Packet Connectivity

Added relevant counters

Described how to obtain the configurations of

URncFunction.GresPara12 and the related

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

Technical Descriptions ..................................................................................... 9

Parameters and Configurations ..................................................................... 30

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

Counters and Alarms ...................................................................................... 46

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

Background of Continuous Packet Connectivity

in this document is included in this release.

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

UL DTX with low UL interference is used to increase UL service capacity and

HS-SCCH-less with low DL interference is used to increase DL service capacity and

ZWF26-01-006 New UL DPCCH Slot Format

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

discontinuous uplink DPCCH transmission according to some patterns. If there is neither

ZWF26-01-009 UL DRX in the Node B

ZWF26-01-005 HS-SCCH-less Operation

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

ZWF26-01-010 Enhanced F-DPCH

New UL DPCCH Slot Format

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

Search UDtxDrxProfile from USubSrv.refUDtxDrxProfile.

Get the corresponding profileId.

Get the UE DTX/DRX configuration information used by this service in the

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

UL DTX technical principles

UL DTX can be deactivated or activated by layer-1 HS-SCCH orders.

There is no HARQ-ACK transmission on HS-DPCCH overlapping with the UL

There is no CQI transmission on HS-DPCCH overlapping with the UL DPCCH slot.

There is no E-DCH transmission in the UL DPCCH slot.

The slot is in DTX mode on the UL_DPCCH.

The UL DPCCH preamble or postamble is not transmitted in the slot.

The DPCCH discontinuous transmission procedure in the UL DTX is described as

UE_DTX_cycle_2 and UE_DTX_cycle_1 (respectively corresponding to DtxCyc1Tti2,

UE_DPCCH_burst_1 parameters will be invalid.

ZTE Confidential Proprietary

HSPA Evolution - Continuous Packet Connectivity Feature Guide

UL DTX Pattern with Preambles and Postambles

Preamble and postamble for the DPCCH transmission

Preamble and postamble for the E-DCH transmission

Inactivity_Threshold_for_UE_DTX_cycle_2 E-DCH TTI and the UE starts the

Preamble and postamble for the HS-DPCCH transmission