Rel 99 and other features (RU20)

Module 3

1 © Nokia Siemens Networks RN30094EN20GLA0

Content

Agenda and objectives

RECAP RU 10 extended improvements
Feature Overview - what's new
Rel 99 and other features within RU20
HSPA plus features within RU20
EP 1 features
Performance measurements features
Site solutions, transport and operational features

2 © Nokia Siemens Networks RN30094EN20GLA0

RU20 Rel 99 and other features

• Fast L1 Synchronisation
• 24 kbps Paging Channel
• Common Channel Setup
• Direct Resource Allocation for HSPA
• Power Saving Mode for WBTS

3 © Nokia Siemens Networks RN30094EN20GLA0

Abstract
Fast L1 Synchronization
UE Node B RNC M1001C0
Three phase for RRC
Counter
[RACH] RRC:RRC Connection Request
AC to check to accept
or reject RRC
Connection Request
RRC Connection Setup NBAP: RL Setup Request Allocation of UTRAN
phase Start TX/RX

NBAP: RL Setup Response

resources
ALCAP:ERQ
ALCAP:ECF
M1001C0
[FACH] RRC: RRC Connection Setup 1. KPI
M1001C1 M1001C1
Start TX/RX
RRC Connection Access
L1 Synchronisation
phase
New NBAP: Synchronisation Indication Waiting for UE reply
improvement
within RU20
[DCH] RRC: RRC Connection
M1001C8
Setup Complete
RRC Connection Active phase
RRC active complete drop Pre-Emption SRNS Relocation
Abstract
Fast L1 Synchronization
 Quicker access due to post verification of QoS
 If CPHY-Sync-IND primitive quality is
UE starts transmitting
sufficiently good, UE starts 70 ms quicker without
The total delay before UE starts UL
transmission is reduced by 70 ms. Post Verification

40 ms window
[DCH] RRC Setup Complete
40 ms window
RRC Connection Access phase
40 ms window
50 ms window
Node B starts transmitting
40 ms window

[FACH]: RRC Connection Setup UE starts transmitting UE stops transmitting if

with Post Verification verification check fails

10 ms radio
frames
40 ms window
UE starts receiving,
mobile is listing on FACH Post verification
UE L1 collects 40 ms
check
of quality
measurements
Fast L1 Synchronization
RAN1322

• UE is supporting 3GPP Rel6 (or newer) baseline

• No other features required
• No hardware requirement in UTRA
- Feature is part of basic software package (BSW)

TS 25.214

6 © Nokia Siemens Networks RN30094EN20GLA0

Fast L1 Synchronisation Wenn UE synch. ankündigt dann RL setup request
RNC info an W-BTS über capability von UE
Radio Resource Control Signaling

• Rel 6 UE supports
Fast L1 Synchronisation

• RNC sets “Post Verification

Period” IE to TRUE

• For all Radio Links

• RRC messages:
• RRC Connection Setup
• Cell Update Confirm
• Radio Bearer Setup
• Radio Bearer
Reconfiguration

7 © Nokia Siemens Networks RN30094EN20GLA0

Without Post Verification (I)

• Node B starts transmitting the DPCCH or F-DPCH after NBAP Radio Link Setup
• UE starts receiving after decoding the RRC Connection Setup message
• UE RRC layer starts T312 (previously read from SIB1)
• UE L1 achieves downlink chip and frame synchronisation
• UE L1 collects 40 ms of quality measurements
• generates a CPHY-Sync-IND primitive if quality is sufficiently good
• CPHY-Sync-IND primitive is forwarded to UE RRC layer
• UE can then generate further CPHY-Sync-IND primitives every subsequent 10 ms based upon
the preceeding 40 ms of quality measurements
• CPHY-Sync-IND primitives are forwarded to UE RRC layer
• UE RRC layer counts CPHY-Sync-IND primitives
• UE RRC layer compares the number of primitives with the value of N312 (previously read from
SIB1)
• If the number of primitives reaches N312 prior to T312 expiring then RRC layer considers the
downlink dedicated channel to be established
• UE starts to transmit uplink DPCCH

8 © Nokia Siemens Networks RN30094EN20GLA0

Without Post Verification (II)
• Example below shown for N312 = 4 (default)
• Total delay before UE is able to start transmitting is greater than 70 ms
• Assumes that UE is in good coverage and in-sync primitives are generated on every occasion

UE checks
Node B starts transmitting UE starts transmitting
link QoS

10 ms radio
frames
40 ms window
1st in-sync
UE starts primitive
receiving
40 ms window
Delay while UE receives UE listing
RRC Connection Setup 2nd in-sync
message on the FACH on FACH primitive
40 ms window
3rd in-sync
primitive
40 ms window
4th in-sync
primitive
9 © Nokia Siemens Networks RN30094EN20GLA0
With Post Verification (I)

• Node B starts transmitting the DPCCH or F-DPCH after NBAP Radio Link Setup
• UE starts receiving after decoding the RRC Connection Setup message
• UE RRC layer starts T312 (previously read from SIB1)
• UE L1 achieves downlink chip and frame synchronisation
• UE starts to transmit uplink DPCCH
• Post verification is completed:

• UE L1 collects 40 ms of quality measurements

– generates a CPHY-Sync-IND primitive if quality is sufficiently good
– CPHY-Sync-IND primitive is forwarded to UE RRC layer
– Single CPHY-Sync-IND primitive completes post verification
• If post verification fails, the UE stops transmitting

10 © Nokia Siemens Networks RN30094EN20GLA0

With Post Verification (II)

• UE transmit timing no longer depends upon N312

• Total delay before UE starts UL transmission is reduced by 70 ms (N312=4)
• UE stops transmitting after 40 ms if the post verification fails

Node B starts UE starts transmitting UE stops transmitting if

transmitting verification check fails

10 ms radio
frames

40 ms window

UE starts Post verification

receiving check

11 © Nokia Siemens Networks RN30094EN20GLA0

Establishment of DL DPCCHs/DPDCHs
A UE must check the synchronisation status of every radio frame of downlink dedicated
channels.
The synchronisation status is reported to the higher layer.

The reporting criteria split in two phases:

Phase 1: Physical channel establishment
• During the first 160 ms after the establishment of a dedicated physical downlink channel
• If the DPCCH quality from measurements > Qin over a period of 40 ms  In-sync
messages are sent to the higher layers

When a physical dedicated channel establishment is initiated by the UE, the UE shall start a
timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in
sync" indications, the physical channel is considered established and the timer T312 is
stopped and reset.
If the timer T312 expires before the physical channel is established, the UE shall consider
this as a "physical channel failure".

12 © Nokia Siemens Networks RN30094EN20GLA0

Physical channel establishment criteria
Default values:
• N312: 4
• T312: 10 sec

• UE initiates synchronisation
procedure

• Physical channel failure

Start T312 T312 = 0

in sync indicators
• Physical channel is
N312 consecutive considered established
times • The timer T312 is stopped
Stop T312
and reset

13 © Nokia Siemens Networks RN30094EN20GLA0

DL synchronisation status
Phase 2:
This phase starts 160 ms after the dedicated physical channel (was considered to be) established.
The UE performs measurements and estimates the DPCCH quality over the previous 160 ms period.
An out of sync is detected, if EITHER
• The UE estimates the DPCCH quality over the previous 160 ms period to be worse than a threshold
Qout.
OR
• The 20 most recently received transport blocks with a non-zero length CRC attached, as observed
on all TrCHs using non-zero length CRC, have been received with incorrect CRC.

An in sync is reported to the higher layers, when both

• The UE estimates the DPCCH quality over the previous 160 ms period to be better than a threshold
Qin.
AND
• At least one transport block with a non-zero length CRC attached, as observed on all TrCHs using
non-zero length CRC, is received in a TTI ending in the current frame with correct CRC.
Qout and Qin defined by 3GPP for BTS conformance testing
NSN hardcoded values (Flexi BTS)
Qout = 8
Qin = 8
14 © Nokia Siemens Networks RN30094EN20GLA0
In Sync and Out of Sync on DL DPCCHs/DPDCHs
At least one TB in the last radio
in sync indication 20 last TBs received
frame received with correct CRC
with incorrect CRC

AND

DPCCH_Ec/Io OR out of sync indication

160 ms

Qin

160 ms Qout

time
Toff Ton

UE shuts power off UE shuts power on

(adopted from TS25.101 V5)
15 © Nokia Siemens Networks RN30094EN20GLA0
 Radio Link Failure in the CELL_DCH, Timing
• The UE is in the CELL_DCH sub-state.

• N313 consecutive out of syn indicators from the PHY layer were delivered to the higher layers. The UE starts
timer T313.

•If the PHY layer determines N315 in sync indicators and T313 has not yet expired, the T313 timer is
stopped.

•If timer T313 expires, a radio link failure is detected. The UE clears the dedicated physical channel
configuration,
•Performs actions as defined for the ongoing procedure.
•If there is no ongoing procedure, or no actions are specified for an ongoing procedure, then
the UE has to perform a cell update, indicating the cause “radio link failure“.

• T313
•Range: 0..15 seconds. Default value is 3 seconds.
• N313:
•Range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800 and 1000. Default value is 20.
• N315
•Range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, and 1000. Default value is 1.

(continued)
16 © Nokia Siemens Networks RN30094EN20GLA0
Radio Link Failure in the CELL_DCH, Timing

Default values: serving cell

• N313: 20
• T313: 3s
• N315: 1
• T314: 12s
• T315: 180s non-serving
neighbouring cell

radio bearer
re-establishment time

Start T313 T313 = 0

out of sync indicators in sync • Start cell re-selection 

indicators
• Cell Update message
N313 consecutive cause: Radio Link Failure
N315 consecutive
times • Start T314 & T315
times Stop T313
17 © Nokia Siemens Networks RN30094EN20GLA0
 Radio Link Failure in the CELL_DCH, Timing
• How much time to we have to re-establish a bearer?
• A bearer can be associated with a bearer re-establishment timer (T314 and T315), which defines the time to re-establish it after
a cell or URA update.
• T314 is controlling transparent and unacknowledged mode bearers.
• T315 is controlling acknowledged mode bearers
• After radiolink failure UE moves from in the sub-state CELL_DCH to CELL_FACH
• UE initiates a Cell or URA Update and
• If T314 = 0 AND T315 = 0  all radio resources are released and UE moves to IDLE
• If T314 = 0 AND no RBs with T315  all radio resources are released and UE moves to IDLE
• If T314 = 0 then release all RBs with T314
• If T315 = 0 then release all RBs with T315
• If T314 > 0 AND There are radio bearers associated with T314, then the timer T314 is started
• If T314 > 0 AND There are no radio bearers associated with T314 or T315, then the timer T314 is started
• If T315 > 0 AND There are radio bearers associated with T315, then the timer T315 is started
• If T314 expires and T302 is not running, then all radio bearers associated with radio bearers with T314 value are locally
released. If additionally T315 is not running, the UE is moved to the RRC idle mode.
• If T315expires and T302 is not running, then all radio bearers associated with radio bearers with T315 value are locally
released. If additionally T314 is not running, the UE is moved to the RRC idle mode.

• T314: Range: 0, 2, 4, 6, 8, 12, 16, and 20 seconds. Default value is 12 seconds.

• T315: Range: 0,10, 30, 60, 180, 600,1200, and 1800 seconds. Default value is 180 seconds.

18 © Nokia Siemens Networks RN30094EN20GLA0

Fast L1 Synchronisation

RNC: PostVerifPeriodDLSynch

The parameter determines whether the post-verification is used in the downlink chip
and frame synchronization. A post-verification period can be used with the physical
layer synchronization procedure A when the first radio link set is established for the
UE. If the post-verification period is used, the UE starts transmission on uplink
immediately when it initiates the downlink dedicated physical channel establishment. If
the post-verification period is not used, the UE does not transmit on uplink until the
downlink physical channel is established. If enabled with the parameter, the post-
verification period is applied to the Rel-06 and later UEs.

Range and Step: 0 (Post-verification period not used), 1 (Post-verification period

used)
Default: 1

19 © Nokia Siemens Networks RN30094EN20GLA0

Fast L1 Synchronisation
• Not directly linked to Fast L1 Synchronisation but introduced as part of the feature
• The Power Control Preamble defines the number of DPCCH radio frames which the UE must transmit prior to
transmitting the DPDCH, E-DPCCH or E-DPDCH
• These radio frames during which only the DPCCH is transmitted allow time for the Node B to achieve uplink
synchronisation
• A large Power Control Preamble provides the Node B with more time to achieve synchronisation but increases the
connection establishment delay
• The default value of 0 frames is used to minimise the connection establishment delay
• This parameter was hardcoded and called ‘NPCP’ prior to RU20

RNC: PCPreamble (Uplink DPCCH power control preamble)

The parameter defines the length of the uplink DPCCH power control preamble period.
The uplink DPCCH power control preamble is a period of the uplink DPCCH
transmission prior to the frame where the uplink DPDCH/E-DPCCH/E-DPDCH
transmission can start. The period is defined in terms of the radio frames. The power
control preamble can be used with the physical layer synchronization procedure “A”
when the first radio link set is established for the UE.
Range and Step: 0..7 frame, step 1 frame
Default: 0 frame

20 © Nokia Siemens Networks RN30094EN20GLA0

Fast L1 Synchronisation
• Not directly linked to Fast L1 Synchronisation but introduced as part of the feature
• The SRB Delay defines the number of radio frames after the Power Control Preamble
during which the UE must not transmit any SRB data
• These radio frames provide further time for uplink synchronisation
• Application data can be transferred during these radio frames
• This parameter was hard coded prior to RU20

RNC: SRBDelay
The parameter defines the number of frames after the PC preamble period during
which the transmission of data on the RRC Signalling Radio Beares should be
suspended by the UE. The SRB delay can be applied to the physical layer
synchronization procedure A when the first radio link set is established for the UE.
Range and Step: 0..7 frame, step 1 frame
Default: 7 frame

21 © Nokia Siemens Networks RN30094EN20GLA0

RU20 Rel99 and Other Features

• Fast L1 Synchronisation
• 24 kbps Paging Channel
• Common Channel Setup
• Direct Resource Allocation for HSPA
• Power Saving Mode for WBTS

22 © Nokia Siemens Networks RN30094EN20GLA0

Abstract (1/2)
24 kbps Paging Channel
Cch,256,14
 Paging load/activity
- 8 kbps paging channel capacity is
implemented for (RU10) E-AGCH
- 24 kbps can be allocated for RU20 (ASW) Cch,128,6
- Transport block size increase Cch,128,5

- The stand alone 24kbps PCH is allocated on E-HICH & E-RGCH

S-CCPCH with SF128,
comparing 8 Kbps/SF256 (more PwR) No HSDPA code free HS-SCCH
- If Paging 24 kbps is used, Cch,128,4
maximum of available HSDPA codes are Cch,16,0
only14 S-CCPCH 2

PICH
Cch,64,1
Paging Ch with 24 kbps
• Bottleneck is PwR AICH

• Not code tree allocation P-CCPCH

Cch,256,3
(calculation on next slide)
CPICH
Pilot coverage Cch,256,2
S-CCPCH S-CCPCH 1
setup Cch,256,1
WCEL: PtxSCCPCH1
It carries a PCH/8 or FACH (mux) or FACH/
Cch,256,0
dedicated). Spreading factor is SF64 (RB 60 kbps)
Abstract (2/2)
8/24 kbps Paging Channel
Example: Power benchmark
What limits first: PwR or Code tree occupation

Average HSDPA throughput hardly affected by loss of 1 code, as CQI extremely seldom
good enough for 15 codes (e.g. probability < 1 : 1000)

With SF128 PCH (24kbps) needs power 2 dB below CPICH = 31 dBm = 1.26 Watt
60kbps/24kbps, cc. 1/2 Low processing

With SF256 PCH (8kbps) needs power 5 dB below CPICH = 28 dBm = 0.63 Watt
30kbps/8kbps cc.1/2
More processing
Power loss = 1.26 W – 0.63 W = 0.63 W approx. 600 mW
3 % of 20 W max. cell power (1% = 200mW, 3% = 600 mW)
5 % (600 mW) of about 12 W available for user data

Consider: PCH is not constantly transmitted

24 kbps Paging Channel
Introduction
T-Mobile all features busy
RAN 1202 (based on 3GPP 25.211)
Optional Feature (ASW)
RNC License Key required

Currently (RU10) 8kbps paging channel capacity is implemented.

As traffic in 3G is increasing, in some networks there is more capacity for paging
needed.

On cell level
WCEL: PCH24kbpsEnabled
This parameter is used for enabling\disabling 24kbps Paging channel at a cell level.
Range and Step: 0 (Disabled), 1 (Enabled)
Default: 0 (Disabled)
Notes: Changing parameters requires cell locking

25 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Concept
To support higher paging capacity, the size of transport block for PCH is
increased:

PCCH
Logical channel

8 kbps = up to 50-75% PCH load

8 kbps = 80 Bit / 10ms TTI (default)
Transport channel PCH

24 kbps = 240 Bit / 10ms TTI (optional)

Several
Physical channel SCCPC S-CCPCH possible
H

If WCEL: PCH24KbpsEnabled parameter is set to “enabled”, the PCH transport

channel is mapped to a dedicated S-CCPCH physical channel.

26 © Nokia Siemens Networks RN30094EN20GLA0

Transport Format Set

8 kbps PCH 24 kbps PCH

• Transport Format Sets for the
8 kbps and 24 kbps PCH are 0: 0x240 bits
0: 0x80 bits
very similar (0 kbit/s) (0 kbit/s)
• Only difference is the TFS
1: 1x80 bits 1: 1x240 bits
increased transport block (8 kbit/s)
size (24 kbit/s)

TTI 10 ms 10 ms

Channel
CC 1/2 CC 1/2
coding

CRC 16 bit 16 bits

27 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Configuration Options and Power Control Parameters
Following options in RU 20:

• PCH and FACH mapped to (a single) Physical Channel : S-CCPCH1

▪ PCH (PCCH), FACH (DCCH,BCCH, CCCH) and FACH (DTCH)
▪ WCEL: PtxSCCPCH1

• PCH and FACH are mapped to dedicated S-CCPCHs:

– FACH mapped to S-CCPCH1
▪ WCEL: PtxSCCPCH1
– PCH mapped to S-CCPCH2
▪ WCEL: PtxSCCPCH2SF128 if 24kbps PCH feature is used
▪ WCEL: PtxSCCPCH2 if 8 kbps PCH channel is used

• SAB (Service Area Broadcast)

– SAB is mapped to S-CCPCH3
▪ WCEL: PtxSCCPCH3

28 © Nokia Siemens Networks RN30094EN20GLA0

S-CCPCH Configuration 1
• This configuration limits the PCH bit rate to 8 kbps
• The PCH is multiplexed with the FACH-u and FACH-c
• The PCH always has priority
• SF64 is required to transfer the FACH-u and FACH-c bit rates

Logical channel DTCH DCCH CCCH BCCH PCCH

Transport channel FACH-u FACH-c PCH

U- user data C- control data

Physical channel SCCPCH 1

SF 64

29 © Nokia Siemens Networks RN30094EN20GLA0

S-CCPCH Configuration 2a
• PCH24kbpsEnabled is configured to disabled with this configuration
• Limits the PCH bit rate to 8 kbps
• The PCH is allocated its own S-CCPCH
• SF256 is allocated to the PCH as a result of the low bit rate

Logical channel DTCH DCCH CCCH BCCH PCCH

Transport channel FACH-u FACH-c PCH

Physical channel SCCPCH 1 SCCPCH 2

SF 64 SF 256

30 © Nokia Siemens Networks RN30094EN20GLA0

S-CCPCH Configuration 2b
• PCH24kbpsEnabled is configured to enabled with this configuration
• Increases the PCH bit rate to 24 kbps RU 20
• The PCH is allocated its own S-CCPCH
• SF128 is allocated to the PCH to support the increased bit rate

Logical channel DTCH DCCH CCCH BCCH PCCH

Transport channel FACH-u FACH-c PCH

Physical channel SCCPCH 1 SCCPCH 2

SF 64 SF 128
24 kbps
31 © Nokia Siemens Networks RN30094EN20GLA0
S-CCPCH Configuration 3a
• PCH24kbpsEnabled is configured to disabled with this configuration
• Limits the PCH bit rate to 8 kbps
• The PCH is allocated its own S-CCPCH
• SF256 is allocated to the PCH as a result of the low bit rate

Logical channel DTCH DCCH CCCH BCCH CTCH PCCH

Transport channel FACH-u FACH-c FACH-c FACH-s PCH

Physical channel SCCPCH SCCPCH SCCPCH

connected idle page
SF 64 SF 128 SF 256

32 © Nokia Siemens Networks RN30094EN20GLA0

S-CCPCH Configuration 3b
• PCH24kbpsEnabled is configured to enabled with this configuration
• Increases the PCH bit rate to 24 kbps
• The PCH is allocated its own S-CCPCH
• SF128 is allocated to the PCH to support the increased bit rate

Logical channel DTCH DCCH CCCH BCCH CTCH PCCH

Transport channel FACH-u FACH-c FACH-c FACH-s PCH

Physical channel SCCPCH SCCPCH SCCPCH

connected idle page
SF 64 SF 128 SF 128

33 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Number of S-CCPCH (how many #)

WCEL: NbrOfSCCPCHs
This parameter defines how many SCCPCHs are configured for the cell.

If only one SCCPCH is used, it carries FACH-c, FACH-u, and PCH. If two SCCPCHs are used,
the first SCCPCH always carries only PCH, and the second SCCPCH always carries FACH-u
and FACH-C. If three SCCPCHs are used, the third SCCPCH carries FACH-s and FACH-c-idle.

The recommended value of the transmission power of the SCCPCH depends on the number
of SCCPCHs. The third SCCPCH is needed only if SAB is available.
Range and Step: 1..3, step 1
Default: 1
Notes: (1) Changing parameters requires cell locking
(2) If PCH24kbps is enabled, parameter must be set to “2” or “3”

34 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Power Control Parameters (1/3)

WCEL: PtxSCCPCH1
The parameter defines the transmission power of the S-CCPCH channel.
It carries a 8 kbps PCH or FACH (mux) or FACH /dedicated). Spreading factor is SF64 (120 kbps)
Range and Step: -35..15 dB, step 0.1 dB
Default: 0 dB

WCEL: PtxSCCPCH2 (used for 8 kbps paging)

The parameter defines the transmission power of the S-CCPCH channel which carries
PCH only.
only Spreading factor is SF256 (30 kbps)
Range and Step: -35..15 dB, step 0.1 dB
Default: -5 dB

WCEL: PtxSCCPCH2SF128 (used for 24 kbps paging)

The parameter defines the transmission power of the S-CCPCH channel which carries
PCH only.
only Spreading factor is SF128 (60 kbps)
Range and Step: -35..15 dB, step 0.1 dB
Default: -2 dB

35 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Power Control Parameters (2/3)

WCEL: PtxSCCPCH3
The parameter defines the transmission power of the S-CCPCH channel which carries
FACH for broadcast messages.
Spreading factor is SF128 (60 kbps)
Range and Step: -35..15 dB, step 0.1 dB
Default: -2 dB

Impact on other features or functions:

• HSDPA
 If Paging 24 kbps feature is used, the maximum of available SF16 codes
for HSDPA is 14. This influences maximum achievable HSPA bitrate in the cell

• Transmission and Transport

 Transport manager in RNC uses same activity factors for 8kbps and
24kbps PCH booking on IuB interface (see: RNC: AfPCHDL, default is 0,1)

36 © Nokia Siemens Networks RN30094EN20GLA0

24 kbps Paging Channel
Power Control Parameters (3/3)
Slot format # 4 is implemented for 24 kbps paging feature (source 3GPP 25.211):
Slot Format #i Channel Bit Channel Symbol SF Bits/ Frame Bits/ Ndata1 Npilot NTFCI
Rate (kbps) Rate (ksps) Slot
0 30 15 256 300 20 20 0 0

1 30 15 256 300 20 12 8 0

2 30 15 256 300 20 18 0 2

3 30 15 256 300 20 10 8 2

4 60 30 128 600 40 40 0 0

[..]

As there are no TFCI data transmitted in slot format # 4, no need to focus

on parameter WCEL:PowerOffsetSCCPCHTFCI – however the parameter
exists in the NSN 3G system.

37 © Nokia Siemens Networks RN30094EN20GLA0

Code Allocation Cch,256,14

• Channelisation code for 24 kbps E-AGCH

PCH uses a larger section of the Cch,128,6
code tree Cch,128,5

• HSDPA cannot use 15 HS- E-HICH & E-RGCH

PDSCH codes when HSUPA 2 ms
TTI is enabled with 24 kbps PCH HS-SCCH
Cch,128,4
• Requirement for 2nd E-AGCH SF 128 - config 2b/3b, PCH (24 kbps)
Cch,16,0
code
S-CCPCH 2
• Requirement for F-DPCH code
PICH
Cch,64,1
AICH

SF 64 with FACH - u, FACH - P-CCPCH

c, and PCH (8 kbps) Cch,256,3
CPICH
Cch,256,2
S-CCPCH 1
Cch,256,1

Cch,256,0
38 © Nokia Siemens Networks RN30094EN20GLA0
24 kbps Paging Channel
Non-Controllable Parameters in RNC

PCH_CRCSize Default : 16 bits

PCH24_ChCodingType Default : Convolutional coding
PCH24_CodingRate Default : 1/2
PCH24_NoOfTFs Default : 2
PCH24_RM Default : 210
PCH24_NoOfTBs Default : 0 for TF0, 1 for TF1
PCH24_TBSize Default: 240 bits
PCH24_TTI Default: 10 ms

39 © Nokia Siemens Networks RN30094EN20GLA0

RU20 Rel99 and other Features

• Fast L1 Synchronisation
• 24 kbps Paging Channel
• Common Channel Setup (FACH)
• Direct Resource Allocation for HSPA
• Power Saving Mode for WBTS

40 © Nokia Siemens Networks RN30094EN20GLA0

Abstract
Common Channel Setup
UE setup via CELL FACH implemented within RU20
NW access of UE via Cell FACH
RACH and FACH transport channels are used for call setup
Call setup on CCH is faster than DCH
All time consuming procedures moves to Cell DCH
Depending on Ec/Io and CCH load/PwR calculation, UE moves to Cell DCH

RRC Idle Cell_PCH

Cell_DCH • UE’s cell known
• no UE Location • DCH allocated • UE to be paged
Information • UE’s cell known (DRX functionality
in UTRAN  PICH)
• only LAI / RAI
in CN
• no data transfer
possible
With i- phone • RRC Connection
establishment via
Cell_FACH URA_PCH
RACH/FACH • common channel • similar to Cell_PCH
Not possible signaling allocated (FACH, • no Cell Update,
New RACH, CPCH, DSCH) but URA Update
Quicker access Establish • UE’s cell known
/ Release
via RACH/FACH RRC Connection mode
Connection
for UE
Common Channel Setup

• RAN 1797 (ASW)

• 3GPP Rel 99,4,5,6,7 (and newer) UEs supported

• No other features required

• No hardware requirement in UTRAN

• Optional Feature using RNC capacity license (ASW)
• Number of cells is license criteria
• Available from RU10 on top onwards

42 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Introduction

• RACH and FACH transport channels are used for call setup

• Feature is used for SRB setup and connection setup

• Call setup on CCH is faster than DCH

• More efficient allocation of UTRAN resources

• less signaling processing power required
• no channel element (CE) required
• no dedicated transport resources on Iub interface …,but CCCH allocation
• less spreading code resource used

43 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Introduction

• Allocation of RACH and FACH or DCH is based on establishment

cause received from UE (22 causes)

• Available SRB DCH bitrates are 3.4 kbps or 13.6 kbps

• Parameter to set appropriate bit-rate per establishment cause

• RACH and FACH load is continuously monitored in RNC

• Common channel setup increases load to RACH-FACH channels

• Air interface quality (CPICH EcNo) criteria has impact on CCH

allocation
• Algorithm checks minimum required EcNo when triggered

44 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Signaling radio Bearers

During CCH setup there are 3 Signaling Radio Bearers

defined and allocated:
• SRB 1 is RLC Transparent Mode
• SRB 2 is RLC Acknowledged Mode Layer RAB 4 log. CH NAS

• Used for RRC messages 3 RRC

• SRB 3 is RLC Acknowledged Mode Layer RLC AM/UM one message
• Used for RRC messages carrying NAS 2 MAC
information
Layer 1 W-CDMA

During DCH setup there is another (optional) SRB Not enough space
allocated for recourse allocation on CCCH
• SRB 4 is RLC Acknowledged Mode
• Used for RRC messages carrying low priority NAS Low Prio.
signaling
for SMS

45 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Enabling

WCEL level parameter to enable SRB and Call setup on Common Channels

WCEL: CCHSetupEnabled
This parameter enables / disables the use of RRC connection setup on Common
Channels (CCHSetup).

When the value of the parameter is set to 1 (CCHSetup is enabled for the cell).

Range and Step: 0 (Disabled), 1 (Enabled)

Default: 0

46 © Nokia Siemens Networks RN30094EN20GLA0

 Decision Making Process
RNC receives RRC
Connection Request

Setup on CCH preferred for this establishment cause?

RACH and FACH Load ok?
CPICH Ec/Io ok? NO
RRC Idle -> CELL_DCH
Ptx_Total ok?
If Rel99 UE, then Setup on CCH is allowed?
If Rel7 UE, then Setup on HSPA/DCH not preferred? Check Directed RRC Setup
algorithm for appropriate RF
YES carrier

RRC Idle -> CELL_FACH

SRB mapped onto HSPA?
YES NO
SRB on
RACH/FACH SRB on HSPA SRB mapped onto
13.6 kbps DCH
YES NO
• Four possible outcomes:
SRB on 13.6 kbps SRB on 3.4 kbps
• SRB on RACH/FACH DCH DCH
• SRB on HSPA
• SRB on 3.4 kbps DCH • Mapping SRB onto HSPA requires F-
• SRB on 13.6 kbps DCH DPCH to be enabled
47 © Nokia Siemens Networks RN30094EN20GLA0
Common Channel Setup
Enabling FACH or DCH

WCEL: SRBMapRRCSetupEC
This parameter defines the Establishment Cause (EC) values which prefer SRB mapping to
the common channels (CCH) in the RRC connection setup. Establishment Cause is RRC
information element which is received from the UE in the RRC message RRC Connection
Request. The value 0 means that the corresponding Establishment Cause prefers SRB
mapping to the dedicated channel (DCH) or to the high speed packet access (HSPA, that
is, on HS-DSCH/E-DCH) in the RRC connection setup. The value 1 means that the
corresponding Establishment Cause prefers SRB mapping to the common channels in the
RRC connection setup. Bit 9: Emergency call does not effect, SRBs of emergency call are
always mapped to DCH in the RRC connection setup.
The parameter SRBBitRateRRCSetupEC defines the preferred bit rate for the SRB DCH if
DCH is selected to be preferred instead of CCH in the RRC connection setup.The
parameter FDPCHSetup defines allocation procedure of the F-DPCH in the RRC
connection setup.

Range and Step: see next slide

Default: 454656 (dec) – 0001101111000000000000 (bin)

48 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Establishment Cause Mapping All time consuming procedures moves direct to DCH
• 22-bit mapping coding various establishment reasons
Bit Cause Bit Cause
0 Originating conversational call 11 Inter-RAT cell change order

1 Originating streaming call 12 Registration

2 Originating interactive call 13 Detach

3 Originating background call 14 Originating high priority signalling

4 Originating subscribed traffic call 15 Originating low priority signalling

5 Terminating conversational call 16 Call re-establishment

6 Terminating streaming call 17 Terminating high priority signalling

7 Terminating interactive call 18 Terminating low priority signalling

8 Terminating background call 19 Terminating cause unknown

9 Emergency call (always 0) 20 MBMS reception

10 Inter-RAT cell re-selection 21 MBMS ptp RB request

Access causes in green prefer CCH – Access causes in black prefer DCH or HSPA
49 © Nokia Siemens Networks RN30094EN20GLA0
Establishment Causes for 13.6 kbps SRB

• The StandaloneDCCHBitRate parameter is deleted in RU20

• This parameter previously provided a mechanism for enabling/disabling 13.6 kbps DCH
SRB for all establishment causes
• StandaloneDCCHBitRate is replaced by SRBBitRateRRCSetupEC

Change of parameter name

50 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
DCH Bitrate selection (13.6/3.4 SRB)

• Parameter available to select SRB bitrate

WCEL: SRBBitRateRRCSetupEC
This parameter defines the Establishment Cause (EC) values which prefer faster dedicated
channel (DCH) for SRBs in the RRC connection setup. Establishment Cause is RRC information
element which is received from the UE in the RRC message RRC Connection Request. The
value 0 means that the corresponding Establishment Cause prefers 3.4 kbps dedicated channel
for SRBs in the RRC connection setup. The value 1 means that the corresponding Establishment
Cause prefers 13.6 kbps dedicated channel for SRBs in the RRC connection setup. If 13.6 kbps
DCH is preferred one for SRBs in the RRC connection setup but setup of it faces congestion,
setup is retried immediately with 3.4 kbps DCH.
The parameter SRBMapRRCSetupEC defines preferred channel type in the RRC connection
setup, either common or dedicated channel.
The parameter FDPCHSetup defines allocation procedure of the F-DPCH in the RRC connection
setup.
Range and Step: see next slide 69631dec - 0000010000111111111111bin
Default: see next slide

51 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
DCH Bitrate selection
• 22-bit mapping coding various establishment reasons
Bit Cause Bit Cause
0 Originating conversational call 11 Inter-RAT cell change order

1 Originating streaming call 12 Registration

2 Originating interactive call 13 Detach

3 Originating background call 14 Originating high priority signalling

4 Originating subscribed traffic call 15 Originating low priority signalling

5 Terminating conversational call 16 Call re-establishment

6 Terminating streaming call 17 Terminating high priority signalling

7 Terminating interactive call 18 Terminating low priority signalling

8 Terminating background call 19 Terminating cause unknown

9 Emergency call (always 0) 20 MBMS reception

10 Inter-RAT cell re-selection 21 MBMS ptp RB request

Access causes in red use 13.6kbps – Access causes in blue use 3.4 kbps
52 © Nokia Siemens Networks RN30094EN20GLA0
Common Channel Setup
Impact on Rel99 UE

• Operator can enable CCH call setup for Rel99 UE

WCEL: RRCSetupCCHEnabledR99
This parameter defines whether RRC connection setup for R99 UEs is allowed to be
performed on common channels (CCH). If the value of this parameter is disabled, RRC
connection setup is performed on dedicated channel (DCH) despite of the value of the
Establishment Cause information element in the RRC message RRC Connection Request.
If value of this parameter is enabled and the value of the Establishment Cause information
element is interpreted so (parameter SRBMapRRCSetupEC), RRC connection setup can
be performed on common channels.
The parameter SRBMapRRCSetupEC defines preferred channel type in the RRC
connection setup, either common or dedicated channel.

Range and Step: 0 (Disabled), 1 (Enabled)

Default: 0

53 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
Enabling

WCEL: CPICHEcNoSRBMapRRC
This parameter defines threshold for CPICH Ec/No to determine whether RRC
connection setup is allowed to be performed on common channels (CCH). RRC
connection setup on common channels is not possible if CPICH Ec/No measured and
reported by the UE is less than the value of this parameter. If the lowest possible
parameter value is defined, in practice CPICH Ec/No value does not affect the channel
type selection algorithm for SRBs.

Range and Step: -24 dB .. 0 dB

Default: - 8 dB

RNC receives CPICH EcNO measurement result in RRC: RRCconnectionsetupRequest message

(example from RNC log)

EcNo = - 2.5 dB

54 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup UE Node-B RNC CN

Signaling Procedure :
TM CCCH: RRC Connection Request
[ Establishment Cause such that setup on CCH is preferred ]
RNC allocates the C-RNTI,
establishes the RRC connection
/ onCCH and waits for RRC
Conn . Setup Complete from the UE.
UM CCCH: RRC Connection Setup
• Cell_FACH state used for UE in Cell_FACH state
[ RRC State Indicator: Cell_ FACH] Single mapping option
-SRB4 is not established
-UE capability required
subsequent signaling AM DCCH: Initial UE Message
[1st NAS- message from UE ]
AM DCCH: RRC Connection Setup Complete
RANAP: Initial Direct Transfer

RANAP: Common ID (optional)

:

RRC Connection established, UE in Cell FACH state

• UE stays on Cell_FACH
NAS signaling connection; UE- CN signaling continued...

during e.g NRT call setup RANAP: Security Mode Command

AM DCCH: Security Mode Command

AM DCCH: Security Mode Complete RANAP: Security Mode Complete

• Traffic Volume Measurements RANAP: RAB Assignment Request

performed in Cell_FACH state AM DCCH : Radio Bearer Setup Establish RB on FACH for nRT
RAB
AM DCCH : Radio Bearer Setup Complete -RRC_State_indicator: Cell_FACH
-don’t establish SRB4
RANAP: RAB Assignment Response

• Cell_DCH used once Channel

AM DCCH: RRC Measurement Control (TVM only)

-Default TVM threshold : 128Byte

Type switching selected DCH Measurement setup in BTS and RNC

or HSPA transport channels

NAS signaling connection; UE- CN signaling continued (e.g. SM: PDP Context Accept )

(not shown here)

UE in Cell_ FACH state, continued

55 © Nokia Siemens Networks RN30094EN20GLA0

RACH-FACH Common Channel Load

56 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load

RNC continuously monitors the load for RACH and FACH transport channels
That happens on MAC-c entity inside RNC

RACH Load FACH Load

Measurements Measurements

MAC-c

The following list of parameters represents a recap from legacy NSN (Nokia)RRM

57 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load (message part RACH)

RACH capacity is measured in number of RACH messages received by WBTS.

WCEL: RACHCapacity
The parameter defines the HW capacity reserved for a RACH transport channel in the BTS.
RACH Capacity is indicated as the number of decoded RACH messages in a 10 ms radio frame.
In case of WBTS with 3GPP interface, parameter modification requires object locking. It is
recommeded to use parameter value 4 if functionality RRC connection setup on common
channels is configured to be used in this cell.

Range and Step: 1 (1 message), 2 (2 messages), 3 (3 messages), 4 (4 messages)

Default: 2
400 messages
Recommendation when CCH call setup is enabled and used: 4 messages (approach)
per second
or 4 times/10 ms

58 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load (P-RACH)
Network Planning Parameter to define RACH load threshold:
Info comes from W-BTS and
WCEL: RachLoadThresholdCCH moves to RNC (RR IND)

The parameter defines the threshold for the RACH load for downlink channel type
selection. If the threshold is exceeded, a DCH or HS-DSCH is allocated. Measurement
is used for the channel type selection for the SRB in the RRC connection setup phase
and for the NRT RB in the RRC state CELL_FACH. The RACH load is measured as
the average number of acknowledged PRACH preambles over two radio frames, in
proportion to the RACH capacity which is given by the management parameter
RACHCapacity multiplied by two.

Range and Step: 0..100 %, step 1 % 300 messages/sec. (75%)

Default: 75 % with parameter 4

Average number of acknowledged PRACH Preambles over 20 ms

RACH Load =
RACHCapacity × 2
4096 chips/premanble

59 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load

Network Planning Parameter to define FACH load threshold for CCH-

it is based on FACH throughput:

WCEL: FachLoadThresholdCCH
The parameter defines the threshold for the total throughput of SCCPCH (FACH/PCH)
channel for downlink channel type selection. If the threshold is exceeded, DCH or HS-
DSCH is allocated. Measurement is used for the channel type selection for the SRB in
the RRC connection setup phase and for the NRT RB in the RRC state CELL_FACH.

Range and Step: 0..100 %, step 1 %

Default: 75 %

S-CCPCH throughput measured at the bottom of the Physical Layer

FACH Load =
Maximum Throughput Capability of the S-CCPCH

60 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load

WCEL: FachLoadMarginCCH
The parameter defines the margin for the total throughput of SCCPCH (FACH/PCH)
for downlink channel type selection. When the measured load is below the threshold by
at least this margin, FACH usage is possible.

Range and Step: 0..10 %, step 1 %

Default: 5 %

FACH
load 75%

After 5 % less load 70%

e.g. setup via FACH/RACH Hysteresis

No FACH time
61 © Nokia Siemens Networks RN30094EN20GLA0
Common Channel Setup
RACH and FACH load

Common channel can be measured in terms of downlink power used for CCH:

WCEL: PtxThresholdCCH
This parameter defines the threshold for the total downlink transmission power for
downlink channel type selection. If the threshold is exceeded, a DCH/HS-DSCH is
allocated. Measurement is used for the channel type selection for the SRB in the RRC
connection setup phase and for the NRT RB in the RRC state CELL_FACH.
Assumption here is that a DCH is more efficient than a FACH, due to fast power
control. Relative to PtxTarget.
PtxTarget

Range and Step: -5..0 dB, step 0.1 dB

Default: -1 dB
Example: PtxTarget = 40 dBm - 1 dB = 39dBm default (8 Watt)

62 © Nokia Siemens Networks RN30094EN20GLA0

Common Channel Setup
RACH and FACH load

Integral parameter to control the RACH procedure:

WCEL: AllowedPreambleSignatures
The preamble part in a PRACH channel carries one of the 16 different orthogonal
complex signatures. The allowed preamble signatures specify which signatures are
used in a cell.
The allowed preamble signatures use binary notation, where bit 0 indicates if the
signature #0 is allowed, bit 1 indicates if the signature #1 is allowed, and so on. If a bit
is set to 1, the corresponding signature is allowed.

BTS Restriction:
A maximum of 4 signatures can be allowed.
Up to 4 users can access simultaneously same RACH slot

63 © Nokia Siemens Networks RN30094EN20GLA0

Interaction with Directed RRC Connection Setup
• Common Channel Setup pre-empts the decision for Directed RRC Connection
Setup
if a UE triggers the transition from RRC Idle to CELL_FACH then the Directed RRC
Connection Setup algorithm is not applied
• If a UE subsequently triggers the transition from CELL_FACH to CELL_DCH then the
Common Channel Layer for HSDPA algorithm is applied

Directed RRC Connection Setup

RRC Idle Cell_PCH f3, HSDPA&HSUPA
Cell_DCH • UE’s cell known
• no UE Location • DCH allocated • UE to be paged
Information • UE’s cell known (DRX functionality
in UTRAN  PICH)
• only LAI / RAI
in CN
• no data transfer
possible
Yes (applied only HSPA) f2, HSDPA
• RRC Connection
establishment via
Cell_FACH URA_PCH
RACH/FACH • common channel • similar to Cell_PCH
signaling allocated (FACH, UE Rel-6 capability C
• no Cell Update,
New RACH, CPCH, DSCH) but URA Update
No directed RRC
Establish • UE’s cell known
/ Release UE Rel5/6 & B f1, R´
R´99
Connection HSDPA
mode capability
(f1 to f2) RRC
Connection
Any other UE A

Concept: Booking of resources/load within CCH first,

no direct shift load to other layer (Directed RRC)
64 © Nokia Siemens Networks RN30094EN20GLA0
RU20 Rel99 and Other Features

• Fast L1 Synchronisation
• 24 kbps Paging Channel
• Common Channel Setup
• Direct Resource Allocation for HSPA
• Power Saving Mode for WBTS

65 © Nokia Siemens Networks RN30094EN20GLA0

Abstract
Direct Resource Allocation for HSPA
Prior for a NRT service without "wasting time" for CR (RU20)
 UE must support HSDPA and HSUPA transport channels
 DRA is always used when UE has F-DPCH allocated
 HSDPA and HSUPA must be enabled in the cell
 Prior to RU20 for NRT user allocation of 0/0 DCH by AC
If a Capacity Request (CR) was received, RNC made channel type selection
If no Capacity Request received by RNC, UE was moved to Cell FACH

RRC Idle Cell_PCH

Cell_DCH • UE’s cell known
• DCH allocated
DRA
• no UE Location • UE to be paged
Information • UE’s cell known (DRX functionality In RU20 HSPA transport channels
in UTRAN  PICH)
• only LAI / RAI
can be allocated directly in Cell DCH
in CN or
• no data transfer
possible Cell FACH (Common Channel
• RRC Connection
establishment via
Cell_FACH URA_PCH Setup), without waiting for
RACH/FACH • common channel • similar to Cell_PCHcapacity request CR
signaling allocated (FACH, • no Cell Update,
New RACH, CPCH, DSCH) but URA Update
Establish • UE’s cell known
/ Release
RRC Connection mode
Connection
Direct Resource Allocation for HSPA
Introduction (status RU10)

• RAN 1762
• Basic Software Feature (BSW)

Prior to RU20 for a NRT service a 0/0 DCH was allocated to a user :

– If a Capacity Request (CR) was received, RNC made channel type selection
▪ DCH intial bitrate (UL/DL) was allocated if resource available (e.g. 64k / 64k)
▪ HSDPA and A-DCH or E-DCH was allocated depending on configuration
– If no Capacity Request received by RNC, UE was moved to Cell_FACH
(after RNC: DLcapacityReqWait default 5 sec)

• UE must support HSDPA and HSUPA transport channels

• HSDPA and HSUPA must be enabled in the cell

67 © Nokia Siemens Networks RN30094EN20GLA0

Direct Resource Allocation for HSPA
Introduction

In RU20 HSPA transport channels can be allocated directly in Cell_DCH or

Cell_FACH (Common Channel Setup), without waiting for capacity request.

• Operator can manage the feature to allocate HSPA directly

– never (DCH 0/0 is used) or Only used for HSPA
– when UE is in Cell_DCH and/or Still R99 users need CR
– when UE is in Cell-FACH

With F-DPCH
• DRA is always used when UE has F-DPCH allocated automatically DRA is
(even DRA shall not be used in a cell) enabled
• It is used for Background and Interactive traffic classes
• DCH in downlink / DCH in uplink still used 0/0 kbps DCH allocation
– DCH /DCH or
– HSDPA / DCH
Direct Resource Allocation for HSPA reduces the HSPA call setup delay

68 © Nokia Siemens Networks RN30094EN20GLA0

Enabling Direct Resource Allocation for HSPA

69 © Nokia Siemens Networks RN30094EN20GLA0

Direct Resource Allocation
Enabling the feature

RNC: RABDRAEnabled

The parameter enables/disables the use of the direct resource allocation for HSPA. It also
defines whether the direct resource allocation for HSPA is applied in Cell_FACH state,
Cell_DCH state or both. If the feature is enabled, HS-DSCH and E-DCH allocation is tried for PS
data of interactive and background traffic classes during the NRT RAB setup.

Range and Step: 0 (Disabled), 1 (Enabled in Cell_FACH), 2 (Enabled in Cell_DCH), 3 (Enabled in

Cell_FACH and Cell_DCH)
Default: 0
Default value is automatically deactivated with use of F-DPCH
Options: It means F-DPCH switched off PAR."0" and DRA is not working

0 (Disabled): Direct resource allocation for HSPA is not applied but DCH 0/0 kbps is allocated and traffic volume measurements
started in connection with PS NRT RAB setup
1 (Enabled in Cell_FACH): Direct resource allocation for HSPA is applied in Cell_FACH state but not in Cell_DCH state.
2 (Enabled in Cell_DCH): Direct resource allocation for HSPA is applied in Cell_DCH state but not in Cell_FACH state.
3 (Enabled in Cell_FACH and Cell_DCH): Direct resource allocation for HSPA is applied in Cell_FACH state and in Cell_DCH state.

Direct resource allocation is applied in the case of full HSPA (HS-DSCH/E-DCH and F-DPCH allocated)
irrespective of the value of this parameter.

70 © Nokia Siemens Networks RN30094EN20GLA0

Signaling

71 © Nokia Siemens Networks RN30094EN20GLA0

Signalling in CELL_DCH
UE Node-B RNC CN

Signalling link established and UE in Cell_DCH state

• HSPA is allocated during

RANAP:RAB ASSIGNMENT REQUEST [for PS HSPA NRT]

HSPA capacity request

RAB establishment for direct resource
allocation

• Replaces the allocation of

NPAB: RADIO LINK RECONFIGURATION PREPARE
a 0/0 kbps DCH NPAB: RADIO LINK RECONFIGURATION READY

L2 resource allocation and Iub transmission setup

GTP tunnel creation

No CR with DRA -
NPAB: RADIO LINK RECONFIGURATION COMMIT
shorten of call flow
and quicker RB
configuration RRC: RADIO BEARER SETUP [HS-DSCH + E-DCH]

RRC: RADIO BEARER SETUP COMPLETE

RANAP: RAB ASSIGNMENT RESPONSE

In case of successful DRA, HSPA connection is established for the user plane

72 © Nokia Siemens Networks RN30094EN20GLA0

Signalling in CELL_FACH

UE Node-B RNC CN

• HSPA is allocated during

RAB establishment Signalling link established and UE in Cell_FACH state after Common Channel setup (RAN1797)

• Moves the UE into RANAP:RAB ASSIGNMENT REQUEST [for PS HSPA NRT]

CELL_DCH during RAB HSPA capacity request for

establishment direct resource allocation

NPAB: RADIO LINK SETUP REQUEST

• Previously, the UE would be NPAB: RADIO LINK SETUP RESPONSE

left in CELL_FACH until after

L2 resource allocation and Iub transmission setup
a subsequent capacity
request GTP tunnel creation

RRC: RADIO BEARER SETUP [HS-DSCH + E-DCH]

RRC: RADIO BEARER SETUP COMPLETE

RANAP: RAB ASSIGNMENT RESPONSE

In case of successful DRA, HSPA connection is established for the user plane

73 © Nokia Siemens Networks RN30094EN20GLA0

NRT over NRT

Concept
Priority based scheduling
Down grade of BG user to get recourses for in-coming CR of interactive user

74 © Nokia Siemens Networks RN30094EN20GLA0

NRT over NRT

• Enhanced Priority based Scheduling (ePBS) represents NRT-over-NRT functionality

• Serving RNC
• direct resource allocation does not trigger NRT-over-NRT actions
• Drift RNC
• can not differentiate between capacity requests for direct resource allocation and
other capacity requests
• direct resource allocation can trigger NRT-over-NRT actions

• If direct resource allocation fails as a result of congestion then connection

establishment proceeds as in RU10, i.e. 0/0 kbps DCH is allocated for connection
establishment in CELL_DCH, and traffic volume measurements are configured to
trigger capacity requests

DRA (HSPA D-RNC does not

feature) does know type of
not use PBS request, therefore
PBS is still
IA users get no
available, like R99
priority!!!

75 © Nokia Siemens Networks RN30094EN20GLA0

RU20 Rel99 and Other Features

• Fast L1 Synchronisation
• 24 kbps Paging Channel
• Common Channel Setup
• Direct Resource Allocation for HSPA
• Power Saving Mode for WBTS

76 © Nokia Siemens Networks RN30094EN20GLA0

Abstract
Power Saving Mode for WBTS
Complete RF carrier can be shutdown &
complete Node B can be also shutdown

 power savings and efficient traffic management

 Reduction of inter cell interference
Cell
 Improving of soft capacity
shutdown
 less PwR & CCCH overshooting

Traffic
moved
Background (I)
• This feature allows the operator to automatically ‘shutdown’ cells during periods of low
traffic
• power savings which translate to OPEX savings
• CPICH is gradually ramped down during shutdown procedure
• triggers inter-frequency or inter-system handovers
• ‘Shutdown’ cells can be automatically ‘re-activated’ when traffic increases
Low traffic Cell
cell shutdown

Traffic
moved

78 © Nokia Siemens Networks RN30094EN20GLA0

Background (II)
• Depending upon traffic levels and RNC data build
• complete RF carrier can be shutdown
• complete Node B can be shutdown
• If HSDPA layer is shutdown, then HSDPA can be automatically enabled on another
layer
Complete RF carrier can Complete Node B can
be shutdown be shutdown

79 © Nokia Siemens Networks RN30094EN20GLA0

Requirements

UE Requirements
• None

Network Hardware Requirements

• None

Feature Requirements
• None

• The Power Saving Mode for BTS feature is optional and requires an ON/OFF
RNC license

80 © Nokia Siemens Networks RN30094EN20GLA0

Enabling the Feature
• The PWSMInUse parameter must be set to enabled
• Parameter can be modified online without object locking

Name Range Default Description

PWSMInUse 0 (OFF), 0 (OFF) The use of Power Saving Mode for BTS should be controlled in
1 (ON) BTS level. By this parameter the Power Saving Mode (PWSM)
(WBTS) feature can be set ON and OFF on BTS basis.

• Default value is OFF so enabling the feature requires the parameter to be

changed

81 © Nokia Siemens Networks RN30094EN20GLA0

Cells Groups (sectors)
Flexi BTS can handle up to 12 cells
• Cells belonging to a PWSM BTS (4+4+4 or 2+2+2+2+2+2)
must be grouped using the
PWSMCellGroup parameter Cell Group = 1 Cell Group = 3
(WCEL, range 0 to 6)
• Cell group typically corresponds to Cell Group = 2
all cells belonging to a sector RF Carrier 3
• Up to 6 cell groups can be defined
for each Node B Cell Group = 1 Cell Group = 3

• If a cell belongs to a PWSM cell

Cell Group = 2
group:
• it can be targetted for shutdown RF Carrier 2
and re-activation Cell Group = 1 Cell Group = 3
• it can be a target cell for IFHO
triggered by PWSM Cell Group = 2
• A PWSMCellGroup value of 0
RF Carrier 1
indicates that the cell does not
belong to a cell group

82 © Nokia Siemens Networks RN30094EN20GLA0

Shutdown Order
• Cells within a PWSM cell group must
be allocated a ‘shutdown order’
using the PWSMShutdownOrder Cell Group = 1 Cell Group = 3
Shutdown order = 1 Shutdown order = 1
parameter (WCEL, range 0 to 3)
Cell Group = 2
• Value of: Shutdown order = 1
RF Carrier 3
• 1: cell is shutdown first
• 2: cell is shutdown second Cell Group = 1 Cell Group = 3
• 3: cell is shutdown third Shutdown order = 2 Shutdown order = 2
Cell Group = 2
• Value of 0 means that the cell is Shutdown order = 2
categorised as a ‘Remaining Cell’ RF Carrier 2
• Every cell group must have at least Cell Group = 1 Cell Group = 3
one ‘Remaining Cell’ Shutdown order = 0 Shutdown order = 0
• Remaining Cells are not shutdown Cell Group = 2
as a result of low traffic but may be Shutdown order = 0
shutdown during pre-defined time RF Carrier 1
intervals ‘Remaining Cells’

83 © Nokia Siemens Networks RN30094EN20GLA0

MORAN Scenario
Operator 1
• Multiple cell groups can be Cell Group = 1 Cell Group = 3
defined for each sector Shutdown order = 1 Shutdown order = 1
Cell Group = 2
• Allows the definition of cell Shutdown order = 1
groups per operator
• Shutdown order values are Cell Group = 1 Cell Group = 3
Shutdown order = 0 Shutdown order = 0
defined per cell group
Cell Group = 2
Shutdown order = 0

Operator 2
Cell Group = 4 Cell Group = 6
Shutdown order = 1 Shutdown order = 1
Cell Group = 5
Shutdown order = 1

Cell Group = 4 Cell Group = 6

Shutdown order = 0 Shutdown order = 0
Cell Group = 5
Shutdown order = 0

84 © Nokia Siemens Networks RN30094EN20GLA0

Cell Groups and Shutdown Order
• The PWSMCellGroup and PWSMShutdownOrder parameters are shown below

Name Range Default Description

PWSMCellGroup 0 to 6, step 1 0 This parameter defines the Power Saving Mode
(PWSM) cell group of a cell.
(WCEL)

Name Range Default Description

PWSMShutdownOrder 0 to 3, step 1 0 This parameter defines the shutdown and activation
order inside one Power Saving Mode (PWSM) cell
(WCEL) group.

• The PWSMShutdownRemCell parameter determines whether or not a ‘Remaining

Cell’ can be shutdown during a pre-defined time interval

Name Range Default Description

PWSMShutdownRemCell 0 (NO), 0 (NO) This parameter determines if a remaining cell can be
1 (YES) shutdown or not.
(WCEL)

RNC checks every 60s, whether a remaining cell may be shutdown

85 © Nokia Siemens Networks RN30094EN20GLA0
Shutdown of Remaining Cells (I)

• All of the following criteria must be satisfied for a ‘Remaining Cell’ to be shutdown.
• The set of criteria are checked once every 60 seconds.

1. PWSM feature is licensed and enabled (PWSMInUse parameter)

2. Shutdown of remaining cell allowed (PWSMShutdownRemCell parameter)
3. All cells within the PWSM cell group are in a working state
4. Day is as specified by PWSMWeekday parameter, or time is as specified by
PWSMRemCellSDBeginHour, PWSMRemCellSDBeginMin,
PWSMRemCellSDEndHour, PWSMRemCellSDEndMin parameters
5. The cell must belong to a PWSM cell group
6. There only ‘Remaining’ cells active within the cell group
7. No emergency calls and no Wireless Priority Service calls in the cell
9. No ongoing O&M operation in the cell

86 © Nokia Siemens Networks RN30094EN20GLA0

Shutdown of Remaining Cells (II)
• A Remaining cell can be shut down if the current day matches the value of the
PWSMWeekday parameter

Name Range Default Description

PWSMWeekday 0 (None), 0 (None) This parameter defines the days on which the
remaining cells should be shut down at weekend.
(WBTS) 1 (Saturday),
2 (Sunday),
3 (Saturday and Sunday)

87 © Nokia Siemens Networks RN30094EN20GLA0

Shutdown of Remaining Cells (III)
• If current day does not match the value of PWSMWeekday then Remaining cells can be
shutdown within the time window defined by the parameters below

Name Range Default Description

PWSMRemCellSDBeginHour 0 to 23, step 22 hours This parameter defines the starting hour for cell
1 hour shutdown window in Power Saving Mode
(WBTS) (PWSM) for remaining cell.

Name Range Default Description

PWSMRemCellSDBeginMin 0 to 59, step 1 0 minutes This parameter defines the starting minute for
minute cell shutdown window in Power Saving Mode
(WBTS) (PWSM) for remaining cell.

Name Range Default Description

PWSMRemCellSDEndHour 0 to 23, step 6 hours This parameter defines the ending hour for the
1 hour cell shutdown window in Power Saving Mode
(WBTS) (PWSM) for the remaining cell.

Name Range Default Description

PWSMRemCellSDEndMin 0 to 59, step 1 0 minutes This parameter defines the ending minute for the
minute cell shutdown window in Power Saving Mode
(WBTS) (PWSM) for the remaining cell.

88 © Nokia Siemens Networks RN30094EN20GLA0

Shutdown of Non-Remaining Cells (I)
• All of the following criteria must be satisfied for a ‘Non-Remaining Cell’ to be shutdown.
The set of criteria are checked once every 60 seconds.
1. PWSM feature is licensed and enabled (PWSMInUse parameter)
2. All cells within the PWSM cell group are in a working state
3. The cell must belong to a PWSM Cell Group but must not be a Remaining cell
4. There must be at least one Remaining cell within the PWSM cell group
5. No emergency calls and no Wireless Priority Service calls in the cell
6. No ongoing O&M operation in the cell
7. If the PWSMDriftAllowed parameter is set to ‘NO’ and if there is a UE connected whose
serving RNC is a different RNC then shutdown is not allowed
8. Time is within the window defined by the PWSMShutdownBeginHour,
PWSMShutdownBeginMin, PWSMShutdownEndHour and PWSMShutdownEndMin
parameters
9. The traffic within the cell must be sufficiently low, for a period of time defined by the
PWSMDuration parameter
10. There must be sufficient spare capacity within the target cell
11. Cell must be the next cell to be shutdown according to PWSMShutdownOrder
12. If HSDPA is to be enabled in another cell as a result of the cell shutdown then
enabling HSDPA in that cell must be successful for the shutdown to proceed
13. Channel type switching from HSPA to DCH must be successful for all UE connected
to the cell to be shutdown
89 © Nokia Siemens Networks RN30094EN20GLA0
Shutdown of Non-Remaining Cells (II)
• Time window for the shutdown of non-remaining cells is defined by the parameters
shown below

Name Range Default Description

PWSMShutdownBeginHour 0 to 23, step 22 hours This parameter defines the starting hour for cell
1 hour shutdown window in Power Saving Mode
(WBTS) (PWSM).

Name Range Default Description

PWSMShutdownBeginMin 0 to 59, step 1 0 minutes This parameter defines the starting minute for
minute cell shutdown window in Power Saving Mode
(WBTS) (PWSM).

Name Range Default Description

PWSMShutdownEndHour 0 to 23, step 6 hours This parameter defines the ending hour for cell
1 hour shutdown window in Power Saving Mode
(WBTS) (PWSM).

Name Range Default Description

PWSMShutdownEndMin 0 to 59, step 1 0 minutes This parameter defines the ending minute for cell
minute shutdown window in Power Saving Mode
(WBTS) (PWSM).

90 © Nokia Siemens Networks RN30094EN20GLA0

Shutdown of Non-Remaining Cells (III)
• Parameter below determines whether or not cell shutdown is allowed when there is a UE
whose serving RNC is a different RNC

Name Range Default Description

PWSMDriftAllowed 0 (NO), 0 (NO) This parameter determines whether the cell shutdown is
1 (YES) allowed with drifting UEs or not. If there are drifting UEs in a
(RNC) cell and the parameter has value NO, then the cell cannot
be shutdown.

• Parameter below defines the time period during which the set of low traffic criteria must
be satisfied for cell shutdown to be triggered

Name Range Default Description

PWSMDuration 1 to 30, step 1 5 minutes This parameter defines the time period when the
Minutes shutdown criteria for low traffic have to be fulfilled in
(RNC) order to shutdown a cell.

91 © Nokia Siemens Networks RN30094EN20GLA0

Low Traffic Criteria for Shutdown (I)

• The criteria for Real Time DCH are:

• the number of real time DCH within the cell must be less than the value assigned to
the PWSMSDLimitRTDCH parameter
• the non-controllable downlink transmit power for real time DCH must be less than the
value assigned to the PWSMSDPwrRTDCH parameter

Name Range Default Description

PWSMSDPwrRTDCH 0 to 50, step 34 dBm This parameter defines the RT DCH Power limit
1 dBm used in cell shutdown decision.
(WCEL)

Name Range Default Description

PWSMSDLimitRTDCH 0 to 128, step 10 This parameter defines the limit for RT DCHs in
1 cell to be shutdown.
(WCEL)

Less than 34 dBm R99 RT power consumption AND less than 10 R99 RT DCH
during 5 min -> then shutdown
92 © Nokia Siemens Networks RN30094EN20GLA0
Low Traffic Criteria for Shutdown (II)

• The criteria for Non-Real Time DCH is:

• the number of downlink non-real time DCH within the cell must be less than the value
assigned to the PWSMSDLimitNRTDCH parameter

Name Range Default Description

PWSMSDLimitNRTDCH 0 to 128, step 10 This parameter defines the limit for NRT DCHs in
1 cell to be shutdown.
(WCEL)

Less than 10 R99 NRT DCH during 5 min -> then shutdown
Only the number of NRT DCH is considered, but not their power consumption

93 © Nokia Siemens Networks RN30094EN20GLA0

Low Traffic Criteria for Shutdown (III)

• The criteria for Real Time HSDPA connections are:

• the number of real time HSDPA connections within the cell must be less than the
value assigned to the PWSMSDLimitRTHSDPA parameter
• the HSDPA transmit power for real time HSDPA connections must be less than the
value assigned to the PWSMSDPwrRTHSDPA parameter
• Criteria are only applicable if HSDPA is enabled in the cell

Name Range Default Description

PWSMSDPwrRTHSDPA 0 to 50, step 34 dBm This parameter defines the RT HSDPA power
1 dBm limit used in cell shutdown decision.
(WCEL)

Name Range Default Description

PWSMSDLimitRTHSDPA 0 to 300, step 5 This parameter defines the limit for RT HSDPA
1 amount for cell shutdown decision.
(WCEL)

Logical AND
Both conditions must be fulfilled for RT HSDPA traffic for shutdown
94 © Nokia Siemens Networks RN30094EN20GLA0
Low Traffic Criteria for Shutdown (IV)

• The criteria for Non-Real Time HSDPA connections are:

• the number of non-real time HSDPA connections within the cell must be less than the
value assigned to the PWSMSDLimitNRTHSDPA parameter
• the HSDPA transmit power per user for non-real time HSDPA connections must be
greater than the value assigned to the PWSMSDPwrNRTHSDPA parameter
• Criteria are only applicable if HSDPA is enabled in the cell

Name Range Default Description

PWSMSDPwrNRTHSDPA 0 to 50, step 34 dBm This parameter defines the NRT HSDPA power
1 dBm per user margin for cell shutdown decision.
(WCEL)

Name Range Default Description

PWSMSDLimitNRTHSDPA 0 to 300, step 5 This parameter defines the limit for NRT HSDPA
1 amount for cell shutdown decision.
(WCEL)

Logical AND
Both conditions must be fulfilled for NRT HSDPA traffic for shutdown
95 © Nokia Siemens Networks RN30094EN20GLA0
Capacity Check on Target Cell (I)
• Capacity check is always completed for cell belonging to same Node B
• Cell is selected according to the value of the HOPI AdjiPriorityCoverage parameter
• Cell does not have to belong to the same PWSM cell group
• Cell can be different to RT and NRT connections
• These cells may not be the final cells upon which traffic is directed but are considered
the highest probability target cells
• The capacity checks on the RT target cell are:
• the number of real time HSDPA connections within the cell must be less than the
value assigned to the PWSMEXUsrLimit parameter
• the non-controllable downlink transmit power for RT DCH is less than the value
assigned to the PWSMEXPwrLimit parameter
• The capacity check on the NRT target cell is:
• the number of non-real time HSDPA connections within the cell must be less than
the value assigned to the PWSMEXUsrLimit parameter

96 © Nokia Siemens Networks RN30094EN20GLA0

Capacity Check on Target Cell (II)
• The parameters associated with the target cell capacity checks are shown below

Name Range Default Description

AdjiPriorityCoverage 0 to 7, 0 The inter-frequency measurement procedure measures one
step 1 frequency at a time. If there is more than one carrier
(HOPI) frequency to be measured, the RNC selects a subset of
inter-frequency neighbour cells (having the same UTRA RF
Specifies which carrier channel number) which are measured first. The range of
shall be measured first the parameter varies from zero to 7. Zero is the lowest and
7 the highest priority level.

Name Range Default Description

PWSMEXPwrLimit 0 to 50, step 37 dBm This parameter defines the total power limit used in virtual
1 dBm admission control decision.
(WCEL)

Name Range Default Description

PWSMEXUsrLimit 0 to 300, step 5 This parameter defines the limit for RT HSDPA and active
1 NRT HSDPA in cell for virtual AC decision. RT and NRT
(WCEL) HSDPA user amount are compared separately to this
parameter.

Before HO is started, the load situation of the target cell is checked

97 © Nokia Siemens Networks RN30094EN20GLA0
CPICH Ramping Period (slow down of PwR)
• The Cell Deletion procedure is used when shutting down a cell
• The CPICH is ramped down during a period defined by the ShutdownWindow parameter
• The gradual decrease of CPICH transmit power triggers soft handover branch deletion or
inter-frequency/inter-system handover
• If there are UE in the cell after CPICH power ramp down, the RNC waits 1 s and then
attempts to make a forced inter-frequency/inter-system handover
• Node B allows 10 s after power ramp down for forced handovers to complete
• Parameters which limit the number of users in Compressed Mode are ignored
• Inter-frequency handover is attempted prior to inter-system handover
• Inter-frequency handover is executed as soon as a neigbour cell is reported with the
minimum CPICH Ec/Io and RSCP requirements
Name Range Default Description
ShutdownWindow 5 to 45 s, 15 s This parameter defines the cell power ramp down duration
step 5 s for the CPICH, BCH and all other common physical and
(WCEL) transport channels.

EC/I0

time
98 © Nokia Siemens Networks RN30094EN20GLA0
Handling HSPA (I) (no start with HSPA in PwR save cell)
• If the HSDPAenabled parameter has a value “enabled”, and the PowerSavingHSPAType
parameter has a value “HSPA0” then HSDPA is not setup within that cell during initial
cell start-up
• If the HSUPAenabled parameter has a value “enabled”, and the PowerSavingHSPAType
parameter has a value “HSPA0” then HSUPA is not setup within that cell during initial
cell start-up See example on slide III

Name Range Default

PowerSaveHSPAType (WCEL) 0 (NoHSPA05ReConf), 1 (HSPA0), 2 (HSPA5) 0

Description
• HSPA0: A cell that is originally configured with no HSPA services. This cell can be reconfigured to provide HSPA
services by PWSM for BTS feature when HSPA5 cells are shutdown due to low traffic. In activating original HSPA5
cells, the HSPA0 cells shall be reconfigured back to provide no HSPA services.
• HSPA5: A cell that is originally configured to provide HSPA services. The shutdown of this cell due to Power Saving
Mode shall initiate the reconfiguration of an HSPA0 cell to provide HSPA services (i.e. reconfiguring a HSPA0 cell to
modified HSPA5 cell).
• NoHSPA05ReConf: A cell that is configured according to HSPA parameters in controller DB. Power Saving Mode
actions to this cell shall not initiate any HSPA05 reconfigurations.

When setting parameter PowerSaveHSPAType to value “HSPA0” in a cell there has to be at least one another cell in
same Local Cell Group with PowerSaveHSPAType set to value “HSPA5”.
99 © Nokia Siemens Networks RN30094EN20GLA0
Handling HSPA (II)

• HSPA reconfiguration is allowed if:

• the Node B has cells on exactly 2 RF carriers
• all cells at the Node B belong to same PWSM cell group
• the value of the PWSMCellGroup parameter is not equal to 0
• all cells at the Node B belong to the same LCG
• Cells on one RF carrier all have PWSMShutdownOrder of 1 and
PowerSaveHSPAType of “HSPA5”
• Cells on the other RF carrier all have PWSMShutdownOrder of 0 (remaining cells) and
PowerSaveHSPAType of “HSPA0”
• HSDPA is enabled in all cells of the Node B using HSDPAenabled
• The remaining cells are not allowed to be shutdown i.e. the parameter
PWSMShutdownRemCell has a value of ‘NO’ in all remaining cells

100 © Nokia Siemens Networks RN30094EN20GLA0

 Handling HSPA (III)

• Example scenario shown below

• HSDPA initially active on the second RF carrier
• Second RF carrier experiences low traffic
• HSDPA is enabled on first RF carrier
• First RF carrier is shutdown

PWSMCellGroup = 1
HSDPAenabled = enabled
HSDPA Cells
PWSMShutdownOrder = 1 F2 F2
PowerSaveHSPAType = HSPA0 Active shutdown
HO
HSDPAenabled = enabled
PWSMShutdownOrder = 0 F1 HSDPA F1 HSDPA
PowerSaveHSPAType = HSPA0 Inactive Active

Actual situation after

101 © Nokia Siemens Networks RN30094EN20GLA0

Re-Activation of Remaining Cells

• All of the following criteria must be satisfied for a ‘Remaining Cell’ to be re-activated.
The set of criteria are checked once every 60 seconds.
1. Day is not as specified by PWSMWeekday parameter, and time is not
as specified by PWSMRemCellSDBeginHour,
PWSMRemCellSDBeginMin, PWSMRemCellSDEndHour,
PWSMRemCellSDEndMin parameters
2. No ongoing O&M operation in a cell

• Note that re-activation of Remaining Cells does not depend upon traffic
because traffic is no longer loading the cell group, i.e. all cells within the cell group
are shutdown

Reactivation of remaining cells only controlled by timer

Not triggered by traffic

102 © Nokia Siemens Networks RN30094EN20GLA0

Re-Activation of Non-Remaining Cells

• All of the following criteria must be satisfied for a ‘Non-Remaining Cell’ to be re-
activated. The set of criteria is checked once every 10 seconds.
1. The traffic within the cell must be sufficiently high, for a period of time defined
by the PWSMExceededTrafficDur parameter
2. No ongoing O&M operation in a cell

Name Range Default Description

PWSMExceededTrafficDur 10 to 300, 20 secs This parameter defines the time that at least
step 10 one active cell in one Power Saving Mode
(RNC) seconds (PWSM) cell group needs to have traffic
criteria fulfilled in order to activate a previously
shutdown cell.

• All traffic criteria have to be satisfied within a specific cell belonging to the PWSM cell
group

103 © Nokia Siemens Networks RN30094EN20GLA0

High Traffic Criteria for Re-Activation (I)

• The criteria for Real Time DCH are:

• the non-controllable downlink transmit power for real time DCH must be greater than
the value assigned to the PWSMAVLimitRTDCH parameter

Name Range Default Description

PWSMAVLimitRTDCH 0 to 50, step 37 dBm This parameter defines the RT DCH power limit
1 dBm used in cell activation decision.
(WCEL)

104 © Nokia Siemens Networks RN30094EN20GLA0

High Traffic Criteria for Re-Activation (II)

• The criteria for Real Time HSDPA connections are:

• the number of real time HSDPA connections within the cell must be greater than the
value assigned to the PWSMAVLimitRTHSDPA parameter
• the HSDPA transmit power for real time HSDPA connections must be greater than
the value assigned to the PWSMAVPwrRTHSDPA parameter
• Criteria are only applicable if HSDPA is enabled in the cell

Name Range Default Description

PWSMAVPwrRTHSDPA 0 to 50, step 37 dBm This parameter defines the RT HSDPA power
1 dBm limit used in cell activation decision.
(WCEL)

Name Range Default Description

PWSMAVLimitRTHSDPA 0 to 300, step 0 This parameter defines the limit for RT HSDPA
1 amount for cell activation decision.
(WCEL)

105 © Nokia Siemens Networks RN30094EN20GLA0

High Traffic Criteria for Re-Activation (III)

• The criteria for Non-Real Time HSDPA connections are:

• the number of non-real time HSDPA connections within the cell must be greater than
the value assigned to the PWSMAVLimitNRTHSDPA parameter
• the HSDPA transmit power per user for non-real time HSDPA connections must be
less than the value assigned to the PWSMAVPwrNRTHSDPA parameter
• Criteria are only applicable if HSDPA is enabled in the cell

Name Range Default Description

PWSMAVPwrNRTHSDPA 0 to 50, step 31 dBm This parameter defines the NRT HSDPA power
1 dBm per user limit for cell activation decision.
(WCEL)

Name Range Default Description

PWSMAVLimitNRTHSDPA 0 to 300, step 10 This parameter defines the limit for NRT HSDPA
1 amount for cell activation decision.
(WCEL)

106 © Nokia Siemens Networks RN30094EN20GLA0

Thank You !

107 © Nokia Siemens Networks RN30094EN20GLA0