Professional Documents
Culture Documents
ZTE UMTS HSPA Evolution Continuous Packet Connectivity Feature Guide V8 5 201312 PDF
ZTE UMTS HSPA Evolution Continuous Packet Connectivity Feature Guide V8 5 201312 PDF
ZTE UMTS HSPA Evolution Continuous Packet Connectivity Feature Guide V8 5 201312 PDF
Xu
V7.0 2012-4-16 Jiang Qingsong Created
Chunxiao
Updated to UR12
Lin Yumei
V8.0 2012-12-30 Cui Lili Added relevant counters
Li Ling
Added CPC and F-DPCH counters
TABLE OF CONTENTS
1 Feature Attributes.............................................................................................. 5
2 Reference ........................................................................................................... 5
3 Overview ............................................................................................................ 6
3.1 Background of Continuous Packet Connectivity (CPC) ........................................ 6
3.2 ZWF26-01-A CPC ................................................................................................ 6
3.2.1 ZWF26-01-006 New UL DPCCH Slot Format ...................................................... 7
3.2.2 ZWF26-01-007 UL DTX ....................................................................................... 7
3.2.3 ZWF26-01-008 DL DRX ....................................................................................... 8
3.2.4 ZWF26-01-009 UL DRX in the Node B ................................................................ 8
3.2.5 ZWF26-01-005 HS-SCCH-less Operation ............................................................ 8
3.3 ZWF26-01-010 Enhanced F-DPCH ..................................................................... 9
7 Glossary ........................................................................................................... 47
FIGURES
TABLES
Table 4-1 DPCCH Fields ...................................................................................................10
Table 4-2 F-DPCH Fields ...................................................................................................26
Table 4-3 F-DPCH/E-FDPCH Fields ..................................................................................27
1 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]
2 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)
[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
3 Overview
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.
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.
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.
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.
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
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.
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.
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.
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.
4 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.
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.
Slot Channel Channel SF Bits/ Bits/ Npilot NTPC NTFCI NFBI Transmitt
Format Bit Rate Symbol Frame Slot ed Slots
# (kbps) Rate per Radio
(kbps) Frame
0 15 15 256 150 10 6 2 2 0 15
2 15 15 256 150 10 5 2 2 1 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.
For the same reason, UL DTX will be controlled by the NrtDtxSwch parameter in the
RNC for non-real-time services.
Note:
3) Get the record information of the child MO UDtxDrx under the UDtxDrxProfile
instance (the configuration under UDtxDrx with the same UDtxDrxProfile value.)
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
parameter is used to indicate the maximum UE DTX cycle supported by the neighboring
cell for continuous packet connectivity during the DTX-DRX operation.
When UL DTX is activated, the UE will not transmit the uplink DPCCH in a slot if all of the
following conditions are met:
During the UL DTX activation, the UE will transmit the DPCCH preamble and postamble
for synchronization. The specific procedures are described as follows:
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.
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 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
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 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.
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
- F-DPCH
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
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
- 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
subframe4 subframe0 subframe1 subframe2 subframe3 subframe4 subframe0 subframe1 subframe2
UE_DRX_cycle
- HS-SCCH Subframe0 Subframe1 Subframe2 Subframe3 Subframe4 Subframe0 Subframe1 Subframe2 Subframe3 Subframe4
S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
HS-PDSCH
- HS-PDSCH S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
HS-PDSCH
- HS-DPCCH S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
1280 chips
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
- F-DPCH
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
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
- 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
subframe4 subframe0 subframe1 subframe2 subframe3 subframe4 subframe0 subframe1 subframe2
UE_DRX_cycle
- HS-SCCH Subframe0 Subframe1 Subframe2 Subframe3 Subframe4 Subframe0 Subframe1 Subframe2 Subframe3 Subframe4
S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
HS-PDSCH
- HS-PDSCH S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
HS-PDSCH
- HS-DPCCH S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3 S_DRX=4 S_DRX=0 S_DRX=1 S_DRX=2 S_DRX=3
1280 chips
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).
5) For a real-time service, if RtDtxSwch is ON, it can use DTX; if RtDrxSwch 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.
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.
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.
UE Buffer
E-DCH
Transmission
MAC_Inactivity_
threshold
CFN
DPCCH
Detect
Data
Ndata 1 bits
Tslot = 2560 chips, 40 bits
1 subframe: Tf = 2 ms
As seen in the above figure, the number of bits transmitted during HS-SCCH 2ms TTI is
fixed.
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
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.
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.
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
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.
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.
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.
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
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:
2. The other reserved HS-SCCH-less code channels will be considered when the
pre-configured code channel is occupied.
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
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;
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.
512 chips
TPC
(Tx OFF) (Tx OFF)
NTPC bits
1 radio frame: Tf = 10 ms
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:
Channel F-DPCH
Slot Format Channel Bit
Symbol SF Bits/ Slot Bits/Slot
# Rate (kbps)
Rate (ksps) NTPC
0 3 1.5 256 2 2
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, F-
1, , 149}.
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.
0 3 1.5 256 20 2 2 16
1 3 1.5 256 20 4 2 14
2 3 1.5 256 20 6 2 12
3 3 1.5 256 20 8 2 10
4 3 1.5 256 20 10 2 8
5 3 1.5 256 20 12 2 6
6 3 1.5 256 20 14 2 4
7 3 1.5 256 20 16 2 2
8 3 1.5 256 20 18 2 0
9 3 1.5 256 20 0 2 18
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.
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.
PCCPCH slot
Pink is occupied 256 chip margin; yellow is occupied 256 chip margin by new
multiplexing user
256 slot margin use 0 1 2 3 4 5 6 7 8 9 0 1
of maintenance and
suppositional F-
DPCH
F-DPCH when
TPC
UE1 accessing
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.
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 0 1 2 3 4 5 6 7 8 9 0 1
of maintenance and
suppositional F-
DPCH
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 TPC
(UE1)
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.
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.
The E-FDPCH function is configured on the RNC side, the main parameters include:
RncFdpchSupInd, FdpchSuptInd, FdpchSuptInd, RncEfdpchSupInd,
EfdpchSupInd, and EfdpchSupInd.
OMC path
Parameter configuration
This parameter indicates whether the cell supports the CPC function or not.
7 UDtxDrxProfile(of
vsDataUDtxDrxPr UE DTX/DRX Profile Object ID
ofile)
19 DtxCyc2InactTrd1
Inactivity Threshold for UE DTX Cycle 2 for 10ms TTI
0
26 CpcDtxDrxSuptIn
CPC DTX-DRX Support Indicator
d
29 UDtxDrxProfile(of
UE DTX/DRX Profile Object ID
UDtxDrx )
30 profileId( of
vsDataUDtxDrxPr UE DTX/DRX Configuration Index
ofile )
OMC path
Parameter 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.
OMC path
Parameter 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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
OMC path
Parameter configuration
OMC path
Parameter configuration
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for the E-TFC selection in unit of
sub-frames when E-DCH 2ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for the E-TFC selection in
unit of sub-frames when E-DCH 10ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the MAC inactivity threshold used for the E-TFC selection in
unit of TTIs.
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for UL DTX_1 in unit of
sub-frames when E-DCH 2ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for UL DTX_1 in unit of
sub-frames when E-DCH 10ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for UL DTX_2 in unit of
sub-frames when E-DCH 2ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the discontinuous cycle used for UL DTX_2 in unit of
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
This parameter indicates the DTX inactivity threshold controlled by UE DTX cycle 2 in
unit of TTIs when E-DCH 2ms TTI is used.
OMC path
Parameter configuration
This parameter indicates the DTX inactivity threshold controlled by UE DTX cycle 2
in unit of TTIs when E-DCH 10ms TTI is used.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
This parameter indicates the prior DTX timer length reported through the CQI in unit of
sub-frames.
OMC path
Parameter configuration
This parameter indicates the HS-SCCH cycle for UE monitoring in unit of sub-frames.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
This parameter indicates whether the CPC DTX-DRX operation is supported by the
neighboring cell or not.
OMC path
Parameter configuration
This parameter indicates the maximum UE DTX cycle supported by the neighboring
DRNC cell for CPC DTX-DRX operation.
OMC path
Parameter 47
Parameter configuration
Bit 5 is the VIP user DTX/DRX configuration switch (0: Close; 1: Open).
OMC path
Parameter configuration
OMC path
Parameter configuration
OMC path
Parameter configuration
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.
OMC path
Parameter configuration
OMC path
Parameter 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.
OMC path
Parameter configuration
This parameter indicates whether the CPC HS-SCCH-less operation is supported by the
neighboring cell or not.
OMC path
Parameter configuration
Bit 4 is the VIP user HS-SCCH-less configuration switch (0: Close; 1: Open).
OMC path
Parameter configuration
OMC path
Parameter configuration
This parameter indicates whether the RNC supports the enhanced F-DPCH or not.
OMC path
Parameter configuration
OMC path
Parameter configuration
This parameter indicates whether the neighboring DRNC cell supports the F-DPCH.
OMC path
Parameter configuration
OMC path
Parameter configuration
This parameter indicates whether the neighboring DRNC cell supports the enhanced
F-DPCH.
OMC path
Parameter configuration
This parameter indicates whether the cell supports the enhanced F-DPCH or not.
7 Glossary
AM Acknowledge Mode
B Background
C Conversation
CN Core Network
DL Downlink
FP Frame Protocol
I Interactive
L2 Layer 2
LI Length Indicator
P-T-M Point-to-Multipoint
P-T-P Point-to-Point
RB Radio Bearer
RL Radio Link
PO Power Offset
S Streaming
SF Spreading Factor
SN Sequence Number
TF Transport Format
UE User Equipment
UL Uplink
UM Unacknowledged Mode