HSDPA Principles Seminar

Corrado Carbone - RO/QoS South

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
2

Outline
Lets get used with the main concepts of the HSDPA.

HSDPA introduces new technologies in the UMTS world and consequently a new way to manage PS traffic. The most important impacts of it are on:
Modulation Retransmission schemes Scheduling Usage of Power and Code

This presentation reports an overview of the main issues to take in mind.

HSDPA Basic Principles

1 - Shared Channel Transmission (1/2)

Shared-channel transmission implies that a certain amount of radio resources of a cell (codes and power) is seen as a common resource that is dynamically shared between users.
The idea is that a part of the total downlink code resource is dynamically shared between a set of packet-data users, primarily in the time domain. The codes are allocated to a user only when they are actually to be used for transmission, leading to efficient code and power utilization.

For P4 only 5 codes (SF = 16) will be available for the HSDPA feature and they will be shared on a time base.
SF=1 SF=2 SF=4 SF=8 SF=16

Channelization codes allocated for HS-DSCH transmission 5 codes (example) TTI Shared channelization codes

User #1

User #2

User #3

User #4

1 - Shared Channel Transmission (2/2)

The Shared-channel transmission allows: Higher peak bit rate: all the resource can be allocated to a single user in case of low
load.

Better application performance being closer to the model TCP has being designed
for.

More efficient utilization of available code resources compared to the use of a

dedicated channel, i.e. reduced risk for code-limited downlink.

The Shared-channel transmission impacts:

Scheduling become more complex

2 - Short 2 ms TTI (1/2)

The Transmission Time Interval becomes extremely short in HSDPA; 2 ms compared to the 10 ms used by R99 high bit rate radio bearer. The HS channels are organised in sub-frame of 3 slots each; this means that the slot time 2/3 ms/slot is the same as for R99 slots (10/15 ms/slot). The scheduling and the link adaptation algorithms work at this frequency!

2 ms

Rel 5 (HS-DSCH)
2 ms

Earlier releases
10 ms 20 ms 40 ms 80 ms

2 - Short 2 ms TTI (2/2)

The shorter TTI allows: Reduced air-interface delay: this is required by the the TCP at high data rates to Improved end-user performance

2 ms

The shorter TTI is necessary to benefit from other HSDPA features: Fast Link Adaptation Fast hybrid ARQ with soft combining Fast Channel-dependent Scheduling

3 - HSDPA Power Allocation

HS-DSCH allocated power is decided by the RNC, prioritizing the DCH channel HS-DSCH adjusts the data rate to match the instantaneous radio conditions and the available transmission power in the RBS
No closed loop power control is specified for HS-DSCH, unlike the DCH channel

The system adjusts the data rate by

varying the effective code rate changing the modulation scheme

This leads to a higher efficiency in the usage of power.

Power

3GPP Release 99
Unused power Total cell power

Power

3GPP Release 5
HS-DSCH (rate controlled)

Total cell power

Dedicated channels (power controlled)

Dedicated channels (power controlled) Common channels

Common channels
Power usage with dedicated channels channels
9

t HS-DSCH with dynamic power allocation

4 - Fast Link Adaptation (1/3)

The target for the link adaptation is to select a TFRC (Transport Format and Resource Combination) resulting in transmitting an as large transport block as possible with a reasonable error probability.

Channel Condition
Coding Available Power

Link
Adaptation

Modulation TFC

Bit Rate

UE category
Traffic (buffers state)
10

4 - Fast Link Adaptation (2/3)

Adjust transmission parameters to match instantaneous channel conditions HSDPA: Adapt on 2 ms TTI basis the Rate (constant power)
Adaptive coding Adaptive modulation (QPSK or 16QAM)

Link adaptation is implemented by allowing the MAC-hs to set the TFRC (Transport Format and Resource Combination) independently for each 2 ms HS-DSCH TTI

feedback data rate High

Low data rate

11

4 - Fast Link Adaptation (3/3)

In order to estimate current channel conditions, an estimate of the Channel Quality is reported by the UE to RBS (CQI). Based on the channel conditions and the available power, the network will select the Transport Format to have the maximum throughput achievable

feedback data rate High

Low data rate

12

5 - Fast Channel-dependent Scheduling (1/2)

Scheduling = which UE to transmit to at a given time instant

User1

User2

User3 User4
2 ms 2 ms time

There is a main tradeoff to choose between:

fairness vs. cell throughput

Every user has the same rights to access the resource

13

The user with better radio condition transmit more

5 - Fast Channel-dependent Scheduling (1/2)

2 opposite strategies are:

Round Robin: radio resources are allocated to communication links on a sequential basis. Proportional Fair: transmit at fading peaks. This may lead to large variations in data rate between users.

Scheduled user User 1

high data rate

low data rate User 2

#1 #2 #1 #2 #1 #2 #1

Time

14

6 - Fast Hybrid ARQ with Soft Combining (1/2)

HSDPA introduces a new retransmission level under the RLC scheme in the RNC. This new level allows rapid retransmissions of erroneous data:
Hybrid ARQ protocol terminated in RBS short RTT (typical example: 12 ms) Soft combining in UE of multiple transmission attempts reduced error rates for retransmissions

P1,1 Transmitter

P1,2

P2,1

P2,2

P3,1

P1,1 Receiver
15

P1,2 + P1,1

P2,1

P2,2 + P2,1

P3,1

6 - Fast Hybrid ARQ with Soft Combining (2/2)

A fundamental difference between conventional ARQ (used in RLC) and HARQ is that:
in the latter case received data blocks that cannot be correctly decoded are not discarded but buffered They are soft combined with later received retransmissions of the same set of information bits. Finally, decoding is applied to the combined signal.

16

7 - UE capabilities
The UE capabilities are divided into a number of parameters:
Total RLC AM and MAC-hs buffer size Maximum number of HS-DSCH transport channel bits received within a HS-DSCH TTI Support of HS-PDSCH Yes/No Maximum number of HS-DSCH codes received Total number of soft channel bits in HS-DSCH Minimum inter-TTI interval in HS-DSCH Supporting 16QAM

These physical layer UE capabilities can be translated in a limit on the requirements for 3 different UE resources:
the de-spreading resource (codes decoded in parallel) the soft buffer memory used by the hybrid ARQ functionality the turbo decoding speed (the maximum number of transport channel bits received within an HS-DSCH TTI and the minimum inter-TTI interval).

17

Throughput level: UE type cat 12

There are several levels for throughput calculation: lets clarify!
The biggest MAC-HS transport block size is 3440 including HS header and padding bits:

X 10 =
RLC SDU = 320 RLC head = 16 MAC- HS SDU head = 3360

= 3440 bits
Padding bits = 59

MAC- HS head = 21

That means the DSCH max scheduled bit rate could be 1720 kb/s:
That is including headers, padding and every type of retransmission

This is the level used by the RBS counters and Couei!

This corresponds to a max RAB bit rate of 1600 than 1600*0.9 =1440 bit/s

kb/s =320*10/2

In reality considering at least the HS retransmissions at this level the maximum bit rate could not be higher

18

Agenda

1. Overview

2. Architecture 3. Channel Structure

4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
19

Protocol stacks (1/4)

UE
User Data RLC MAC FP MAC-hs L1 L1 AAL2 ATM PHY
Uu

RBS

Iub

SRNC
RLC MAC FP AAL2 ATM PHY

Iu

CN
User Data

GTP-U UDP/IP AAL5 ATM PHY

GTP-U UDP/IP AAL5 ATM PHY

The figure shows the R99 protocol stack. Note in particular that MAC is a protocol between the RNC and the UE

20

Protocol stacks (2/4)

UE
User Data RLC MAC-d MAC-hs MAC-hs HS-DSCH FP AAL2 ATM PHY
Uu

RBS

Iub

SRNC
RLC MAC-d HS-DSCH FP AAL2 ATM PHY GTP-U UDP/IP AAL5 ATM PHY

Iu

CN
User Data GTP-U UDP/IP AAL5 ATM PHY

L1

L1

The new radio interface layer 2 functionality required by the HSDSCH (hybrid ARQ signaling, scheduling, etc) was placed in a new functional entity of the MAC layer, called MAC-hs. The physical layer was updated with new functionalities for HSDSCH (soft combining of retransmitted transport blocks, new physical channels, etc.).
21

Protocol stacks (3/4)

UE
RRC RLC MAC-d MAC-hs MAC-hs HS-DSCH FP AAL2 ATM PHY
Uu

RBS

Iub

SRNC
RRC RLC MAC-d HS-DSCH FP AAL2 ATM PHY GTP-U UDP/IP AAL5 ATM PHY

Iu

CN

GTP-U UDP/IP AAL5 ATM PHY

L1

L1

A new user-plane frame-handling protocol (UP FP) between the SRNC, DRNC and Node B needed to be developed for the radio network layer (RNL). It was based on the release 99 DSCH UP FP used over Iur. The layer 3 control-plane protocols (RRC, RNSAP and NBAP) needed to be updated with control procedures, handling HS-DSCH.
22

Protocol stacks (4/4)

UE
TCP/IP
RLC MAC-d MAC-hs MAC-hs HS-DSCH FP AAL2 ATM PHY RLC MAC-d HS-DSCH FP AAL2 ATM PHY GTP-U UDP/IP AAL5 ATM PHY
Uu

RBS

Iub

SRNC

Iu

CN
TCP/IP
GTP-U UDP/IP AAL5 ATM PHY

L1

L1

Note that RLC does not have significant impact When the HS-DSCH transport channel is used with AM RLC, it is expected that RLC re-transmissions will be required only in rare circumstances where the inner hybrid ARQ fails. E.g. in handover situations, the transmit and receive buffers in the MAC-hs layer may need to be re-initialized. This may cause data loss, which would be taken care of by RLC retransmission.
23

General impacts of the new architecture

There will be impacts on the buffer capabilities
for data in the RBS a new buffer is needed to store data of different users The mobile has to store erroneous PDU for Soft Combining Requirements on buffer could be different due to the new amount of transmitted data

Algorithms have to be adapted:

Admission and Congestion Control for example need new way to estimate the load and accept new users. Closed loop power control does not apply to HS. New algorithms that manage the new functionalities have to be introduced (buffer, scheduling).

Mobility algorithm in particular is conditioned since the fast link adaptation does not allow the Soft Handover anymore.
The e2e performance of the PS users significantly improves due to a smaller RTT.

24

HSDPA Basics: Node Impacts

RBS
New TX board in RBS

RNC
No HW upgrades Only SW!! Setup of HS-DSCH/HS-SCCH

R99:
Scheduling, TF selection, Link layer retransmission (ARQ)
Core Network
RNC

HSDPA:
Scheduling, Link Adaptation, Hybrid ARQ
25

Node B

Node Functionality

Iu RNC Iur

RNC Function: RAB establishment & release Channel switching Mobility

Iub

Resource handling
Associated Dedicated Channels

Capacity management L2 (MAC-d) UL HS control channel power control

Certain flow control

26

Node Functionality

Iu RNC Iur

RBS Function: L2 (MAC-hs) Scheduling HARQ process handling

Associated Dedicated Channels

Iub

Transport format selection Certain flow control DL HS shared control power control

27

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
28

HSDPA new channels

HSDPA introduces specific channels, 1transport and 3 physical channels:
The transport channel High Speed Downlink Shared Channel (HS-DSCH) is a resource existing only in downlink and carries user data in HSDPA. The High Speed Physical Downlink Shared Channel (HS-PDSCH) is a downlink physical channel, to which the HS-DSCH channels are mapped. The High-Speed Shared Control Channels (HS-SCCH) is used for downlink control signaling and carries indication about UE scheduling. One Associated Dedicated Channel (A-DCH) pair (UL & DL) per HSDPA user in connected state, used for control signaling and uplink data transmission. The uplink control information is carried by the Uplink High Speed Dedicated Physical Control Channel (HS-DPCCH).

A-DCH

29

Channel Structure
Associated Dedicated Channels

Control Channel HS-DSCH High-Speed Downlink Shared Channel (Transport) HS-SCCH High-Speed Shared Control Channel(s) (Physical) A-DCH Associated Dedicated Channel A-DCH (Transport)

HS-DPCCH High-Speed (related uplink) Dedicated Physical Control Channel (Physical)

HS-PDSCH High-Speed Physical Downlink Shared Channel (Physical)

30

An overview of HS-DSCH and its associated channels

CN

RNC

RBS

UE

RRC For each user NAS NAS

DCCH
DCCH DCCH DCCH
DPCCH DCH DCH

DPCH

DPDCH HS DPCCH -

HS-SCCH
Interactive PS RAB User 1 Interactive PS RAB User 2 DTCH HS -DSCH DTCH

HS-PDSCH

Interactive PS RAB User n

DTCH

Iu
Radio Access Bearers:
- Interactive - Background Logical Channels: -Dedicated Control Channel, DCCH -Dedicated Traffic Channel, DTCH

Iub
Transport Channels: -Dedicated Channel, DCH -High-Speed Downlink Shared Channel, HS-DSCH

Uu
Physical Channels: -Dedicated Physical Channel, DPCH -DPCCH, Dedicated Physical Control Channel -DPDCH, Dedicated Physical Data Channel -HS-DPCCH, HS-DSCH Dedicated Physical Control Channel -HS-DSCH Shared Control Channel, HS-SCCH -High Speed Physical Downlink Shared Channel, HS-PDSCH

31

HS-DSCH : High-Speed Dedicated Shared Channel

HS-DSCH is the transport channel used for data transmission on the downlink and is shared by all users in the cell. In the HSDPA first phase product release:
the sharing of code resource is done in the time domain on a 2 ms time basis (TTI). The shared code resource consists of 5 channelization codes with fixed spreading factor SFHS-DSCH = 16, in this time frame.

The HS-DSCH cannot be in soft/softer handover and no fast power control is used. The HS-DSCH uses all the excess power from the available transmission power at the base station left from the common and dedicated channels

32

HS-SCCH: High-Speed Shared Control Channel

HS-SCCH is a downlink physical channel used to carry HS-DSCH related control signaling (Physical Layer signaling).
It is shared among the HSDPA users on time division basis (TTI), with the same scheduling as for HS-DSCH. All UEs listen to the same HS-SCCH channel and after decoding, decide whether the information to start listening the HS-PDSCH was intended to that UE. Informs the UE about:
HS-DSCH code set Modulation scheme (QPSK/16QAM) HS-DSCH transport format (number of transport blocks per TTI and number of bits per transport block) Hybrid ARQ information

Never in soft handover The HS-SCCH has a spreading factor SFHS-DSCH = 128

33

A-DCH: Associated Dedicated Channel

One A-DCH pair is set up for every HSDPA user in connected state.
It is used for control signaling (RRC and NAS) in UL and DL. It is a new Radio Bearer corresponding to a 3.4 kbps SRB in the DL (Sf 256). In the uplink A-DCH is also used as the channel for data transmission, where the rate can be either 384 kbps or 64 kbps.
The uplink data rate 384 kbps is selected as first priority and 64 kbps is used as a fall back rate if the path loss is judged to be too large or 384 kbps radio bearer setup fails for any reason (e.g. lack of radio or hardware resources).

The uplink A-DCH channel also contains the High-Speed Dedicated Physical Control Channel (HS-DPCCH), the new physical channel that carries the L1 related signaling in UL.

34

HS-DPCCH: High-Speed Dedicated Physical Control Channel

It is used for transmitting the following information from UE to RBS:
HARQ acknowledgement (1 bit coded in 10) Channel quality indicator (5 bits coded to 20 bits in 2 slots)
channel quality measurements based on CPICH reporting rate is configurable through RRC/NBAP signaling information reflecting the instantaneous downlink radio channel conditions to assist the RBS in the transport format selection (fast link adaptation) and the scheduling The HS-DPCCH has a spreading factor SFHS-DSCH = 256

The A-DCH both UL and DL can be in soft/softer handover whilst the HSDPCCH can never be in soft handover (softer is possible). HS-DPCCH (UL) is transmitted within a dedicated channel. The main idea is that it is power controlled from the other part of the A-DCH.

35

HSDPA Channel Operation

Physical Channels: -Dedicated Physical Channel, DPCH -DPCCH, Dedicated Physical Control Channel -DPDCH, Dedicated Physical Data Channel -HS-DPCCH, HS-DSCH Dedicated Physical Control Channel -HS-DSCH Shared Control Channel, HS-SCCH -High Speed Physical Downlink Shared Channel, HS-PDSCH

HS-DPCCH: CQI HS-SCCH: DL Transfer Information HS-DSCH: Data Transfer HS-DPCCH: ACK/NACK

36

UserPlane: Overview
There are 8 steps to transmit on the HS-DSCH:
In the RNC, the Interactive RAB is mapped to a radio bearer to be transmitted on the HS-DSCH. The radio bearer is then processed by the RLC and MAC-d layer 2 protocols in the RNC. The resulting MAC-d PDUs are transmitted over Iub to the RBS using the HSDSCH frame protocol. The MAChs receive the Channel Quality Indicator adjusted by the Node B The MAC-hs scheduling function selects in each TTI the user to which the HSDSCH is transmitted. Following the selection of a user, the user data to transmit on the HS-DSCH is put into one of several HARQ processes in the MAC-hs HARQ protocol. The amount of data to transmit is determined by the TFRC selection algorithm. Hence the data is transmitted to the UE over the air interface.

37

RAB/RB Combination Overview

Interactive and background Packet Service
New RABs defined:
Interactive PS 64/HS PS 384/HS (optional)

DL bit rate up to 4.32 Mbps in P4 (user data rate) About HS-DSCH:

Max. 5 codes DL: QPSK or DL: 16QAM (optional) UL 64 kbps interactive radio bearer Supported by symmetric 3.4 kbps signaling radio bearer (SRB)

38

Agenda

1. Overview 2. Architecture Accessibility: Call setup phases

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
39

Radio network functions

Iu RNC Iur Iu RNC

7
Iub Iub Iub

1 2 3 4 5 6

Camping in idle Access the HSDPA system Move within the system Move out of the system Control the power Decide which mobile and how much to transmit to it RRM policy

Associated Dedicated Channels

4
f2 HS f1

3
f2 HS f2 HS 2 f1 f1 f1

f1
40

f1

State Diagram non HSDPA-P4

SRB CS Streaming

Speech

Other int. RAB state

New!

Int. 64/384 SP64 PS Streaming+Int 8/8 Int. 64/128 UDI (CS64)

SP0

Int. 64/64

UDI+Int. 8/8

New!
SP0 not available

New!
RAB Release RAB Establishment Channel Switching Int. FACH

SRB

RAB est on FACH

Note 1: It is possible to go to Idle from all states (Signaling connection release) Note 2: QoS profiling on the PS Int RAB is handled by Channel Switching Note 3: Same transitions is valid for PS Streaming 16/64 and PS Streaming 16/128 Note 4: RAB establishment on FACH depending on the setting for parameter PacketEstMode

41

State Diagram only HSDPA

HS-DSCH (uplink 64 or 384)

The diagram is clearly much easier. What does it means? Few transitions
RAB Establishment RAB Release

SRBDCH

Signaling Connection handling

Idl e

Only 2 HS RABs exist The choice between 64 or 384 is done at the beginning and cannot be changed during the connection.

42

Idle mode & RRC Connection Establishment

f2 HS HS+f1
f2 f1

Ec/No

f2 HS f1

f2 HS f1 HS+ f1

f1

In idle mode there is no difference between a user with HSDPA capability or not.

The UEs select the the cell with best Ec/N0 with the procedure cell reselection as in R99.
In second carrier sites, HSDPA is deployed in the second carrier only
Most idle UEs will camp on f1 Most HS users must be moved to f2 in order to get the HS service

There is no difference in the RRC Connection Establishment procedure between a user with HSDPA capability or not
RRC Connection Request and Radio Connection Setup Complete contains information about the UE capability
43

RAB establishment
UE UTRAN
SRB - DCH

SGSN

0
RANAP: RAB Assignment Request (establish PS Interactive/Background RAB)

HSDPA capability analysis

1 2

Serving HS - DSCH cell selection

Possible Inter frequency hard handover

3
Radio Bearer setup

4
44

RANAP: RAB Assignment Response

Capability analysis
At the reception of RANAP RAB Assignment Request, if:

the present UE state is SRB-DCH and if the RAB mapping gives as result PS interactive or PS background the Access stratum release indicator received from UE indicates Rel-5 or later release, the Physical channel capability received from UE indicates that the UE supports FDD HS-PDSCH (any HS-DSCH-physical-layer-category shall be supported), if the existing UE capability check for L2 are successful

UE

UTRAN
SRB - DCH

SGSN

RANAP: RAB Assignment Request (establish PS Interactive/Background RAB)

HSDPA capability analysis

The RNC performs the Serving HS-DSCH cell selection

Serving HS-DSCH cell selection

Otherwise the RAB is established in design base system.

45

Serving HS-DSCH cell selection

When, at RAB establishment, the UE starts the procedure 3 results are possible:
If the HS-DSCH is enabled in the best cell, the connection is set up in that cell.

Current active set

Otherwise the RNC check the coverage relation of the best cell.
If the HS-DSCH is enabled in the target cell, an hard handover New active set is tried to the new selected cell. If no cells are available and the connection is established on an interactive DCH. DCH

46

Coverage relations
The coverage relation is a unique uni-directional relation between two cells, a source and a target cell.
The purpose of the coverage relation is to give the operator a possibility to distribute HSDPA downlink traffic among the cells of an RNC. The target cell covers almost the same area and can be assigned the same frequency or different ones. Typically the cells will be co-located.

A coverage relation is defined for a source cell with the parameters (3GPP R5 25.423):
hsPathLossThreshold utranCellRef (the target cell) coverageIndicator

47

Two Carriers scenario: IF HO

In case the HSDPA is deployed on a second layer and the mobile access the network from the first layer the step will be the following:

The mobile ask for a SRB establishment on a cell of Carrier 1 Start the RAB establishment and the Cell Selection procedure..

2nd carrier

When the attempt on the AS cells fails, check the coverage relation of the best cell and its path loss

f2 HS f2 HS

f2 HS

f2 HS

If everything is ok, perform a BLIND IF-HO If the IF HO succeed continue the RB set up on the new carrier..

ff1 1 f1 f1

f1

f1

Otherwise the RNC try to establish a R99 PS RAB on the first carrier
48

1st carrier

Interfrequency load distribution

It adds the possibility to configure a "load-sharing margin" which can be used to reserve output power, for e.g. HSDPA traffic, in selected cells
It makes the cell appear more loaded than it actually is It can be used to push traffic on a specific carrier

49

UE

RB setup (1/2)

RBS RBS

DRNC DRNC

SRNC
1. Admission request 2. Allocate resources

4
If the result from the Serving HS-DSCH cell selection gives that a Serving HS-DSCH cell is selected
-> the RB setup, SRB-DCH to PS interactive (64 or 384)/HS - HSDSCH transition is performed

3. NBAP: Radio Link Reconfiguration Prepare 4. RNSAP: Radio Link Reconfiguration Prepare 4. Admission request 4. Allocate resources 4. NBAP: Radio Link Reconfiguration Prepare 5. Allocate resources 5. Allocate resources 6. NBAP: Radio Link Reconfiguration Ready 6. RNSAP: Radio Link Reconfiguration Ready

If the result gives that no Serving HS-DSCH cell is selected, but UE connection is still maintained -> the RAB establishment is
performed as in the design base.

7. NBAP: Radio Link Reconfiguration Ready 8. Iub and Iur Transport Bearer setup, AAL2 Connection setup 9. Set Activation time 9.RNSAP: Radio Link Reconfiguration Commit 9. NBAP: Radio Link Reconfiguration Commit 9. NBAP: Radio Link Reconfiguration Commit 10. RRC: Radio Bearer Setup R5 11. Perform actions at Activation time 12. RRC: Radio Bearer Setup Complete 13. Release resources

50

RB setup (2/2)
Different levels of Admission control runs in the RNC
For the selected serving HS-DSCH cell, run Admission Control algorithm for the A-DCH configuration and for HS-DSCH configuration (number of serving links). For the other cells within SRNC, run Admission Control algorithm for the A-DCH configuration.

The RANAP RAB Assignment Response is sent to the CN when the Radio Bearer Setup Complete has been received. The handling of UL/DL user data on RLC level is done as in the R99 for PS interactive RB.

51

UL: 64 or 384?
Which UL A-DCH to set is decided during the AC phase.
From an AC point of view, there are 2 guaranteed-hs service types:
PS64/HS Interactive PS service with rate 64 kbps in uplink and HS-DSCH using up to 5 HS-PDSCH codes in downlink. PS384/HS Interactive PS service with rate 384 kbps in uplink and HS-DSCH using up to 5 HS-PDSCH codes in downlink.

A part from the other AC check there are 2 special checks for the UL ADCH:
Histogram Admission Policy: requests demanding spreading factor 4 in uplink (PS384/HS radio connection type) are compared with sf4AdmUl. The path loss is checked in order to understand if a 384 UL bearer can be sustained.

If the 384 RB is denied (or is accepted but the RBS dont find the synchronization in the establishment phase) the connection is established on the 64 RB.

52

Release of Iu-PS connection due to inactivity in HSDSCH state (1/2)

When a user finishes its transmission has to release the resources.
The procedure is really simple:
An "HS-DSCH inactivity" timer is started when there is no data to transmit. When the timer expires a Iu Release request is sent and the resources are released.

The value of the timer is a system parameter hsdschInactivityTimer

53

Please note that..

No Channel Switching, cell_DCH -> Idle:
No cell_FACH for HS users. No soft switch between HSDPA and DCH No transition between the UL rate is possible The UE can regulate its rate in UL depending on the cell interference level. Hence a 384 RB in UL has to be considered as the maximum bit rate.

HS-DSCH (uplink 64 or 384) SRB DC H

Idle

RAB Combinations:
Interactive 64/HS kbps PS RAB
UL: Interactive 64 kbps PS RB + 3.4 kbps SRBs on DPCH DL: Interactive PS RB on HS-PDSCH + 3.4 kbps SRBs on DPCH

Interactive 384/HS kbps PS

UL: Interactive 384 kbps PS RB + 3.4 kbps SRBs on DPCH DL: Interactive PS RB on HS-PDSCH + 3.4 kbps SRBs on DPCH

54

Please note that..

Iu RNC

Speech call

Incoming CS call

A critical issue for the HSDPA in P4 is the management of the incoming call.
Subsequent RAB assignments are rejected by RNC
no multi RABs

Iub

f f HSf2 HS f HS

UE

UTRAN
PS Interactive 64/HS - HS-DSCH

MSC SGSN

1. RANAP: RAB Assignment Request (CS RAB)

2. RANAP: RAB Assignment Response

If the current PS Interactive RB is allocated HS-DSCH resources, the RAB Assignment response includes the unmapped RAB IDs in the RABs failed to setup or modify IE.
55

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
56

Mobility: Intra-HSDPA

HSDPA Mobility: introduction (1/3)

After the cell selection, the network has to guarantee the mobility of the HSDPA users
Since No Soft/Softer HO exist for HSDSCH, there will be only one serving Iu cell for the HS-DSCH.
RNC Iur

2 algorithms are interested in the mobility of HSDPA users in connected mode:

Serving HS-DSCH Cell Change A-DCH Soft/Softer HO
Iu RNC

Iub
Iub

Associated Dedicated Channels

Iub

57

HSDPA Mobility: introduction (2/3)

The HSDPA mobility will be splitted here in different issues:
Measurement reporting handling Handover for A-DCH Serving HSDPA cell change

58

HSDPA Mobility: introduction (3/3)

Note that when the UE is PS Interactive using HSDPA, the MEASUREMENT CONTROL includes only neighbor cells of type intrafrequency and no Compressed Mode is triggered, that means that InterFrequency and Inter-RAT Handover are not possible to be performed What happens when the mobile move to area without HSDPA coverage?

1 layer
f HS f2 HS HS f f f1

f2 HS f1

f2 HS

f2 HS f1

2 layers
f1
f1

f1

59

Measurement reporting (1/2)

While user moves in the network, it continues to perfom measurement on the CPICH of the detected cells.
When a UE is setup on a dedicated channel:
the SRNC sends a MEASUREMENT CONTROL (some information are broadcasted in the system information on the BCCH channel) orders the UE to start Intra frequency measurement. As soon as the triggering conditions are fullfilled, the UE sends a MEASUREMENT REPORT message to the SRNC indicating which event occurred and which among the measured cells fulfilled the event criteria.

60

Measurement reporting
4 types of intra-frequency measurements are defined in the 3GPP:
Event 1a: Add cell Event 1b: Delete cell Event 1c: Replace cell - A primary CPICH enters the reporting range - A primary CPICH leaves the reporting range - A Non-active primary CPICH becomes better than an active primary CPICH Event 1d: Change of best cell - A primary CPICH becomes better than the previously best primary CPICH Event 1e: A primary CPICH becomes better than an absolute threshold Event 1f: A primary CPICH becomes worse than an absolute threshold

Note that the RNC can configure more than 1 measurement report for the same event.

61

Mobility Example
2

Active set handling: (Max active set = 3)

event 1a: Add cell 2, to the AS Add cell 3, to the AS event 1b: Delete cell2 event 1d: Change of best cell, to cell 3
Ec/N0 [dB]

1
0

cell 1 cell 2 cell 3

-5

-10

-15

-20 0

5 time [s]

10

15

62

Measurement reporting for HSDPA

When PS Interactive using HSDPA is started, an extra MEASUREMENT CONTROL related only to the event 1d HS , is sent to the UE having another MEASUREMENT ID than the ones dealing with the conventional event 1d for Soft Handover evaluation.
The reason for having a separate event 1d HS is
to be able to get UE reports triggered by only Active Set cells to be able to use different hysteresis and time to trigger parameters to trigger HSDSCH Cell Change. to use a different quality criteria (RSCP of the cells in the Active Set)

Since the 1d Hs reported cell is already a member of the current Active Set, this event do not trigger any change in the AS.

63

A-DCH handover
In the previous slide it is stated that there will be only one serving cell for the HS-DSCH. This does not mean that the UE is connected to only one cell.
For what concerns the A-DCH they continue to perfrom soft and softer hand-over as in normal R99 case.

Note that HS-DPCCH can be only in softer HO.

In the example supposing the best server does not change... A-DCH HS-DSCH

R99
64

R99

HS R99 HS HS

HS HS HS

HS

HS

Serving HSDPA Cell Change (1/2)

When the UE moves between cells, the HSDPA connection is maintained by means of intra frequency serving HS-DSCH Cell Change.
HS-DSCH Cell Change evaluation performs the evaluation of a valid target cell within the current Active Set, only towards a suitable HS-DSCH cells.

A suitable HS-DSCH Cell is a cell that satisfies the following conditions:

Cell in the current Active Set. Internal UTRAN cell. Cell having HS-DSCH enabled.

65

Serving HSDPA Cell Change (2/2)

Serving HS-DSCH cell change is triggered by:
Change of Best cell as indicated by receiving an event 1d, UE measurement report Removal of the Serving HS-DSCH cell from the active set due to receiving an event 1b, UE measurement report. Removal of the Serving HS-DSCH cell from the active set due to receiving an event 1c, UE measurement report. any other reason where the current serving HS-DSCH cell is to be removed from the active set.

No support for HS-DSCH over Iur:

RRC Directed Signaling Connection Re-establishment

66

Soft/softer HO for A-DCH and cell change for HSDPA channels

Measurement quantity

Note, there is of course a time-totrigger also for event 1d-hs

Rep. Range 1a Rep. Range 1b

Initially A-DCH and HSDPA both only on cell 1 P_CPICH 1

P_CPICH 2

hysteresis _ 1d hs

A-DCH on cell 2 only

Reporting event 1a

Reporting event 1d-hs

Reporting event 1b

time

A-DCH in SHO with cell 1 and 2

67

HSDPA channels cell change from cell 1 to cell 2

Serving HSDPA Cell Change

If a suitable HS-DSCH cell can not be found within the current RNS a RRC connection release is triggered. After this a new cell selection can follow:
Another connection establishment with a new Cell selection normal connection establishment on R99 A connection establishment on GSM

f HS f2 HS2 f2 HS

Ex1 Cell Selection

f f2 HS2 HSf2 HS

Ex3
R99 R99

R99
R99 R99 f f2 HS2 HSf2 HS

R99

f HS f HS f1 HS2 f1 HS f1 HS2 f1 HS

Ex 4

RNC
f HS R99 R99 HS 2 HS
68

RNC
Cell Selection
f HS R99 HS 2 HS

Ex 2

GSM GSM GSM GSM GSM GSM

Ex 5
f R99 HS HS R99 HS 2 R99 R99 R99 R99

Radio Connection Supervision Whatever case

f HS f2 HS2 f2 HS GSM GSM GSM GSM GSM GSM Radio Connection supervision is the algorithm monitoring the synchronization of a mobile, that is, if the mobile is still connected or not.

Separate parameter hsdschRcLostT determines how long time a HS user can be out-of-sync before the connection is released For HS users only the RL in the serving HS-DSCH cell is supervised.
Sync status may change at serving HS-DSCH cell change

69

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
70

Carrier mobility
A user conected with a UMTS network on a certain carrier can move out of the its layer coverage. There are 2 mechanisms to avoid the drop, at least for some services:

Inter-RAT Handover Inter-Frequency Handover

f2 HS
Most of the time anyway the passage between carriers happens in idle mode

f2 HS

f2 HS f1
f1 f1

f1
f1

f1

GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM GSM
71

IRAT/IF Handover in five steps

(IRAT HO in the example)

UE moves to poor carrier coverage area and reports to UTRAN

UTRAN
UTRAN commands CM measurements

UE finds suitable cells in another layer and when coverage is even worse it reports the candidates

Core Network

UTRAN evaluates the candidates and commands the HO

5
72

UE gets access to the new LAYER

GSM/ Other Carrier

IF&IRAT Handover: basic

Main steps
When the quality of the connection overcomes a certain thresholds (event 2d or 6a) UE reports a Measurement report and the network orders the UE to activate the CM and check the other layer. If the connection quality further degrades and the other layer has a quality high enough the HO is triggered (events 3a and 2b). If the connection quality turns out to be good, the UE signals it to the network and the mobile stops the CM (events 2f or 6b).

Layer Quality
Threshold 1 Threshold 2

Threshold 3
time

CM HO Compressed Mode

L1 L2

The problem is that there are several thresholds

73

IRAT & IFHO procedures

The evaluation process for HO execution depends on the quantity that started measurements (CPM) among:
CPICH RSCP CPICH Ec/Io UE TX power

Evaluated In parallel

At the same time, the cell in the target layer should have the quality good enough. That means:
For GSM: the quality of the measured GSM cells is above a gsmThresh3a. For the second UMTS layer: the measured best cell on unused frequency is above both the thresholds nonUsedFreqThresh4_2bEcno and nonUsedFreqThresh4_2bRscp

Both of the HO are hard HO:

This means that there will be small interruptions in the data flow to and from the UE.

74

CPM start and HO trigger

CPICH

Target Layer

Ec/No CPICH
RSCP
Start CPM

UE TX

Initial Cell

Start CPM

power

Other layer good enough

HO Start trigg CPM

HO trigg HO trigg

75

IRAT HO and Cell Change

Until here, concerning 3G to 2G switch, only IRAT HO has been mentioned. Anyway when the UE is in connected mode with a PS RAB, the switching procedure to 2G is called IRAT Cell Change.
Compared to IRAT HO:
There is no difference in the evaluation procedure. In the Inter-RAT Cell Change case there are no resources reserved in the target cell before the Inter-RAT Cell Change is executed. There is significant outage period and a certain number of lost packets when moving toward 2G that have to be carefully evaluated (If the Inter-RAT Cell Change is evaluated and executed by the UE in Idle mode or connected mode on common channels it is denoted Cell Reselection or InterRAT Cell Reselection, see Idle Mode and Common Channel Behaviour for more details)

76

IF or IRAT?
A decision has to be made to evaluate either Inter-Frequency handover or Inter-RAT Handover/Cell Change. This decision is based on parameters on RNC level, cell level, and UeRc state. Inter-Frequency handover is only attempted if C_IfHoAllowed is set to Allowed for the current UeRc state, and FddIfHoSupp (RNC) is set to On . Inter-RAT handover is only attempted if C_GsmHoAllowed is set to Allowed for the current UeRc state, and FddGsmHoSupp (RNC) is set to On. If both the conditions are verified the decision is based on a configurable parameter, hoType (cell), defined per cell (IFHO preferred, GSM preferred, None).

Where?

f2 HS

f1 f1

Hence, for a certain cell only one of the 2 Handover types will be allowed.

GSM GSM

77

CIPICH dimensioning
Dimensioning example

CPICH power = 0.87 W

In the dimensioning process the power found with CPICH is done in order to guarantee an adeguate CPICH level (Ec/N0 > -16) within the cell area (Range = 1.17 km).

Does that mean that the boundary of a UMTS cell corresponds to CIPICH_EC/N0 = -16?
78

Which is the real area of a UMTS cell?

When a GSM network or a second carrier is deployed the question is not easy to be answered.

Only looking at the Ec/N0 suggested threshold for IF/IRAT HO we note that:
usedFreqThresh2dEcno = -12 utranRelThresh3aEcno = -1 (relative to 2d thr.) = -13

Different terminals have different behaviours. The load changes the cell border.

79

Impact on coverage

New area the cell

CM start Tx Pwr

HO RSCP

CM start Ec/No Area WCDMA CM without RBS HO Ec/N0

CM start RSCP
HO RSCP
80

Notes for HSDPA

HSDPA users, when in connected mode with a HSDSCH:
will not be allowed to perform IF and IRAT HO. will not experience CM.

Anyway:
they can experiment it when in connected mode with a R99 RAB or in other dedicated connection. They can impact on other users behavior

Dont forget idle mode!

Users change carrier or network even in idle mode and the coprresponding parameters have to be carefully tuned as well.

81

IRAT Cell Reselection

Overall description of thresholds
Ec/No>qQualMin

WCDMA acceptable area

RSCP>qRxLevMin +P

WCDMA->GSM normal reselection area GSM->WCDMA entering area Unstable areas WCDMA unacceptable area because of low RSCP WCDMA unacceptable area because of low Ec/No GSM only area

RSCP+qHyst1 > GSM_RSSI-qOffset1

WCDMA Service
WCDMA RBS
Ec/No>FDDQMIN RSCP>GSM_RLA +FDDQOFF

Ec/No>qQualMin+sRATsearch

GSM coverage
82

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
83

Capacity Management Algorithm

Capacity Management (Overview)

Capacity Management solution controls the load in the WCDMA cells. It includes 3 main algorithms:
Admission Control controls the utilization of dedicated monitored resources by accepting or refusing requests for utilization of these resources Congestion Control detects overload situations on some dedicated monitored resources and initiates congestion resolve actions to decrease the load Dedicated Monitored Resource Handling gathers and provides information about the current usage of critical resources

84

Dedicated Resources
The Dedicated Monitored Resource Handling function collects and provides information about the current usage of resources that are critical to the load of the cell. There are three reasons for blocking:

RF POWER:
the total transmitted carrier power is constantly monitored by the algorithm. When the value exceeds some configurable thresholds the admission/congestion take decisions for guaranteed and non-guaranteed service class connections

CODE
Code Usage: the total number of codes is monitored. Code Hystogram: the number of codes used for each SF are monitored. The max number of code for
each SF is configurable. A control is also done on the maximum number of compressed mode connections

ASE (Air-Speech Equivalent):

This monitor is based on the estimation of the air-interface usage per radio link type (RB type) in a cell. Thresholds can be defined separately for the uplink and downlink, for guaranteed or non-guaranteed connections

85

Admission Control Algorithm

Requests arrive to the AC at several moments:

Radio Link Setup Radio Link Addition Radio Link Reconfiguration Compressed Mode Command

Downlink Transmitted Carrier Power Monitor (for Admission purpose)

Different thresholds exist for different types of request:

(g,ho) guaranteed, handover (g,nho) guaranteed, non-handover (ng,ho) non-guaranteed, handover (ng,nho) non-guaranteed, non-handover

The AC accepts requests until a certain threshold on a monitored resource (power in this case) is reached.

85% 35% 75% default values

86

Congestion Control Algorithm

The congestion control has an unique threshold for all the service types (pwrAdm+ pwrAdmOffset +pwrOffset) to regard the cell as congested.

Downlink Transmitted Carrier Power Monitor (for Congestion control)

The action to decrease the load in the cell considers instead the different priorities of the services.

Default values: pwrOffset = +5% 90% pwrHyst = 600 ms

87

Traffic Algorithms The PS traffic (non-guaranteed) is managed by the RRM algorithms with a lower priority at several levels:
Lower threshold on AC First user to be considered for Congestion actions

Besides RRM algorithms, even the Channel Switching algorithm acts to control the PS traffic.

88

HSDPA Monitored Resource Handling

The way of measuring the resources has to be adapted to the HSDPA:
The monitored power in the RNC keeps track only of the usage of total non-HS downlink transmitted carrier power.
The reports of the power measurements are adapted to the capability of a cell: HSDPA capable Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission HSDPA not capable Transmitted carrier power

2 new dedicated monitored resource is introduced:

the number of HS-serving links in a cell. The usage of SF 4 in uplink (the usage of the optional PS384/HS radio connection type)

The measurement of code tree utilization considers the codes allocated for HSPDSCH and HS-SCCH channels.

89

HSDPA Admission Control Algorithm

The AC receives requests from a HS users in 2 moments:
At RAB establishment; in particular after the serving HS-DSCH cell selection. For mobility, e.g. A Radio link Addition for A-DCH handover
Iub Iu AC RNC Iur

No AC is performed within a Cell Change procedure

Associated Dedicated Channels

Note that there are neither Compressed Mode requests nor Radio Link Reconfiguration

f HS R99
90

f2 HS R99

f2 HS1

R99

HSDPA Admission Control Algorithm

The AC performs several types of check:

A-DCH:
Total available codes (for A-DCH only). ASE (for A-DCH only). Power (for A-DCH) Code with SF=4 in UL (for A-DCH PS 384 in UL) (Hardware, new in P4)

HS-DSCH:
Number of HS-serving links (for RAB set up only)

91

HSDPA - Code Control

There is no check on HSDSCH and HSSCCH codes done by the AC. The operator configure and reserve the number of HS-PDSCH codes allocated in a cell for HSDPA (numHsPdschCodes)
Increase lock of the cell and release of traffic Decrease no effect on ongoing traffic

The number of HS-SCCH (SF=128) codes is one

92

HSDPA Number of HS users

The operator can limit the number of users that can be allocated to the HS-DSCH cell (hsdpaUsersAdm)

# users on HS-PDSCH / HS-SCCH

This limit enables the users allocated to the HS-DSCH (shared channel) to experience a sufficient end-to-end quality

Only serving cell change of HSDPA admitted hsdpaUsersAdm Request for HSDPA resources always admitted

The new policy is only applied to requests for new HSDPA connections

93

HSDPA UL Histogram AC
The operator can set a limit for the guaranteed-hs admission requests demanding spreading factor 4 in uplink that can be accepted (in cells where the PS384/HS is activated) The threshold is set according to the parameter sf4AdmUl This policy allows the operator to disable the PS384/HS feature on a cell basis sf4AdmUl can be reduced if the uplink is experienced as problematic, for example due to high Received Total Wideband Power or transport network problems

94

HSDPA DL Power Admission

New service class, guaranteed-hs, assigned to the A-DCHs
non-guaranteed / handover guaranteed / non-handover guaranteed-hs / handover Admission Granted Reject

Soft congestion is not affected by the introduction of HSDPA

Power
pwrAdm + pwrAdmOffset + pwrOffset pwrAdm + pwrAdmOffset pwrAdm pwrAdm beMarginPwrAdm

non-guaranteed / non-handover

Reject

guaranteed / handover

Highest priority for guaranteed-hs service class in admission decisions to enable HSDPA users to use the excess power in high loaded (noncongested) cells

Admission Granted Reject

Admission Granted Reject

Reject

Admission Granted

95

Admission Granted

Admission Granted

Reject

guaranteed-hs / non-handover

HSDPA Link Power Admission

Total available cell power

While the admission control on a session level is performed by the RNC, it is important to take in mind that the RBS control the HS access to the shared resources.

HSDPA

Dedicated channels

Common channels

96

HSDPA - Congestion Control

guaranteed-hs service class gets intermediate priority (between non-guaranteed and guaranteed) tmInitialGhs minimum time between start of DL congestions and initiation of congestion resolve action on HSDPA users

tmInitialG tmInitialGhs tmCongActionNg Release non-guaranteed traffic tmCongActionGhs Release guaranteed HS traffic tmCongAction Release guaranteed traffic

Power tmCongActionGhs time interval between congestion release actions on HSDPA releaseAseDIGhs amount of ASE to be released at congestion resolve action Congestion threshold
All non-guaranteed traffic released. tmCongActionGhs is restarted as tmInitialGhs has not expired.

Time This policy enforces the higher retention priority of CS services compared to interactive services
97

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
98

Load Sharing Techniques

Load Sharing (1/2)

Load sharing features pool together resources from different parts of the entire network.

2 load-sharing features are available in the WCDMA RAN: Inter-Frequency Load Sharing Directed Retry to GSM

Both load-sharing features redirect calls during the connection setup phase:
RRC connection setup for IF load Sharing RAB setup for Directed retry

Both IF HO and Directed retry will be present at the same time but IF will act first!

99

Load Sharing (2/2)

For load sharing purposes, cell load is defined as the ratio between the downlink transmitted carrier power and the admission limit, as given by the cell parameter pwrAdm. The load sharing algorithm acts only when the load of a cell overcomes a certain threshold:
For IF, the threshold is set to 50% For directed retry both the threshold and the percentage of users to be redirected can be tuned
Cell Load = Tx_power/PwrAdm

Cell Load

IF
50%

Time

Cell Load

DR
thr

Time

100

For HSDPA cells, only the non-HSDPA part is counted

Directed Retry algorithm

Speech call (without packet connection) is the only service that is targeted since it is also the only one that is safe to divert to GSM Directed Retry is performed during the RAB establishment procedure;
the first request will be rejected with cause "Directed retry a request is made to the core network to relocate the UE to a specific GSM cell, using the Inter-RAT handover procedure.

This handover is a blind HO since the target cell is chosen not based on UE measurements. Therefore, the target cell must be co-located with the WCDMA cell.

loadSharingGsmThreshold specifies
the minimum cell load at which off-loading to GSM begins.

Cell Load

There are 2 control parameters:

DR
loadSharingGsmThreshold

loadSharingGsmFraction specifies
the percentage of Directed Retry candidates to be diverted to GSM

Time
101

Inter-Frequency Load Sharing (1/2) 1

The mobile starts a RRC connection establishment procedure ( NO distinction in RRC cause is made)

If the cell load is higher than 50%, the load of the co-located load-sharing neighbor is compared with the accessed cell and the least loaded cell is chosen as target.

If the target cell is less loaded, the UE will not be instructed directly to go to the target cell but it will be told to scan for a suitable cell in the frequency of the target cell, by sending an RRC Connection Reject message.

Load

UMTS L2
UMTS L1 GSM
102

3 1

Load

>=<
Cell 2

2 50%
Cell 1

IF Load Sharing
Here an example of comparison between 2 different frequency is reported.
L[2] = 33% ---- L[1] =60% L[2] = 33% L[1] = 60% Second Carrier 50 % ->20% > L[2] R[2], L[1] < L[1] L[2] Select > L[1] Select Second -> Dont do anythingCarrier Compare the load with the
33% load sharing candidate 33%
Free Resource = R[2]

Layer 2 Layer 1
Load

Power/ 100% pwrAdm

>=<
Cell 2

Load

loadSharingThreshold (20%) First Carrier

Free Resource Free Resource Power/ pwrAdm

33% 60%

Cell 1

DL power in use

100%

To minimize excessive load sharing a hysteresis is used in the comparison, loadSharingThreshold.

103

HSDPA IF Load Sharing

loadSharingMargin is a cell-specific parameter that specifies the amount of resource excluded from load-sharing use (as a percentage of pwrAdm). When loadSharingMargin is greater than 0, the cell appears to be more loaded than it really is, resulting in more traffic being directed away from it

L[2] = 33% + 10% -- L[1] = 60% L[1] - 2 Second Carrier Layer 20% < L[2] 40% < 43% Stay on the First Carrier

loadSharingMargin (10%) 100% Power/ pwrAdm

Layer 1
Load

33%
Free Resource = R[2]

>=<
Cell 2

Load

loadSharingThreshold Free Resource (20%)

50%
Cell 1

60%
DL power in use 100%

Power/ pwrAdm

This parameter gives the operator the possibility to reserve a higher priority to the HSDPA users on the second carriers (in case this is deployed and HSDPA is introduced there)
104

Inter-Frequency Load Sharing

Apart from the load sharing algorithm, other aspects have to be managed and tuned with the introduction of the second layer:
Mobility:

IF HO procedure is more critical compared to a normal SHO and has to be verified and tuned. The compressed mode activity increases in the border cells.
The first IF Load Sharing will increase the call set up time.

Accessibility:

Terminal equipment limitations:

At them moment, there are several terminal types not fully supporting the features to manage a second layer. In particular several models are not IF HO capable.

105

Agenda

1. Overview 2. Architecture

3. Channel Structure
4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 7. KPIs
106

Cell Breathing

Coverage vs. traffic load A well known effect of WCDMA CPICH coverage is that it changes depending on the load.

The DL coverage (considering the Ec/N0 of the CPICH) in particular decreases with the DL total power (hence with the load). CPICH_Ec/N0 in a point:

UL high Loa d

DL high Load

WCDMA RBS

UL low load

DL low load

Ec/N0Cpich = RSCP/RSSI = Pcpich/( (PtotIntra + Ptotinter + Noise)

(*P = received power)
107

DL Problem CPICH Ec/N0 triggering

Expected cell area

Low load CM Area
UL high Load DL high Load
WCDMA RBS

CM start

IRAT

High load CM Area

CM start IRAT
108

Agenda

1. Overview 2. Architecture 3. Channel Structure 4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles 6. Capacity Management 6. KPIs
109

Accessibility KPI

Accessibility (CSSR) KPI

CSSR is currently calculated by two factors: RRC Establishment Success Rate = RRC_Success / RRC_Attempts * RAB Establishment Success Rate = RAB_Success / RAB_Attempts The IF Load Sharing feature impacts on the RRC Establishment Success Rate since several RRC Connection Attempts are rejected to be redirected towards the other frequency. So it is expected that, in case of IFLS activated, the number of RRC Connection Success will be reduced because of the Load Sharing Reject events. To take into account this fact the LoadSharingRejects must be subtracted from the total number of RRC_Attempts: RRC Establishment Success Rate (IFLS) = RRC_Success / ( RRC_Attempts LoadSharingRejects) However the counter for Load Sharing Rejects (pmNoLoadSharingRrcConn) is unique and it does not distinguish between CS, PS or any other kind of RRC Connection cause. This make not easy to adjust the RRC Success Rate for CS and for PS in case of IFLS.
110

Proposed new formulae

Here we tried to evaluate the performance of some formulae to derive the RRC_Estab_Succ_Rate for PS and CS in case of IFLS. (The results are taken from RNC???) The tested formulae are:
RRC _ Succ _ CS pmTotNoRrc ConnectReqCsSucc pmTotNoRrc ConnectReqCs pmTotNoRrc ConnectReqCs - pmNoLoadSharingRrcConn pmTotNoRrc ConnectReq pmTotNoRrc ConnectReqPsSucc pmTotNoRrc ConnectReqPs pmTotNoRrc ConnectReqPs - pmNoLoadSharingRrcConn pmTotNoRrc ConnectReq

RRC _ Succ _ PS

The basic idea is to calculate the load sharing reject for PS and CS by a wheight factor given by the fraction of the RRC_CS (or PS) respect to the total number of RRCs. In case of RRC Succ general the formula is muche more simple instead....
RRC _ Succ _ general pmTotNoRrc ConnectReq Succ pmTotNoRrc ConnectReq - pmNoLoadSh aringRrcCo nn

111

Load Sharing Impact on Accessibility (CSSR) KPI - Results

RRC Connection Establishment Success Rate CS and PS in case of Load Sharing
10000 120%

9000 100% 8000

7000 80% 6000

5000

4000

The RRC Succ estimation CS and PS are disturbed by the Load Sharing rejects. We registered strong fluctuations of values expecially in case of high IFLS activity....

LoadSharingReject 60% RRC_SUC_CS_LS RRC_SUC_PS_LS

40% 3000

2000 20% 1000

0 Days

0%

112

Load Sharing Impact on Accessibility (CSSR) KPI - Results

RRC Connection Establishment Success Rate General in case of Load Sharing
10000 120.0%

9000 100.0% 8000

7000 80.0% 6000

5000

In case of RRC Succ Rate calculated for all kinds of RRC, the estimation is much more stable instead and not affected by IFLS!

60.0%

LoadSharingEvents RRC_SUC_LS

4000 40.0% 3000

2000 20.0% 1000

0 Days

0.0%

113

Load Sharing Impact on Accessibility (CSSR) KPI - Results

RRC Connection Estab. Succ. Rate comparison (General, CS, PS) including Load Sharing
110.0%

>100% values
105.0%

100.0%

RRC_SUC_LS 95.0%

Here it is quite evident the noise introduced by the load sharing in CS and PS RRC Succ estimations.

RRC_SUC_CS_LS RRC_SUC_PS_LS

90.0%

85.0%

Strong KPI deterioration

80.0% Days
114

Please consider that the values are calculated on daily base. So they should be quite stable

Conclusions (1/2)
When Load sharing is introduce the accessibility formulae should be updated to take into consideration the RRC Connection Attempts rejected to be redirected towards the other frequency (). While no problem should exist for the tot accessibility formula:
RRC _ Succ _ general pmTotNoRrc ConnectReq Succ pmTotNoRrc ConnectReq - pmNoLoadSh aringRrcCo nn

2 new formulae are proposed for the CS and PS specific KPIs:

RRC _ Succ _ CS pmTotNoRrc ConnectReqCsSucc pmTotNoRrc ConnectReqCs pmTotNoRrc ConnectReqCs - pmNoLoadSharingRrcConn pmTotNoRrc ConnectReq pmTotNoRrc ConnectReqPsSucc pmTotNoRrc ConnectReqPs pmTotNoRrc ConnectReqPs - pmNoLoadSharingRrcConn pmTotNoRrc ConnectReq

RRC _ Succ _ PS

However the estimation given by this KPI is not extremely stable/reliable and accurate (the average error seems to be acceptable compared to the error that affects the other formulae but the fluctuation are high).
115

Conclusions
An alternative suggestion could be to use the following formula for CSSR
CSSR_CS = RRC_Succ_Global x RAB_CS_Succ CSSR_PS = RRC_Succ_Global x RAB_PS_Succ

The estimation given by this KPI is much more stable/reliable and the average error seems to be acceptable compared to the error that affects the other formulae.
The main drawback of this solution is that the Global RRC Succ is often a little bit worse compared with the real CS and PS values. (This is probably related to different radio environment: i.e. the major part of RRC Connections are established for registration purpose, when the UE is entering back to 3G coverage; those radio procedures often occur at cell coverage borders and so are affected by a worse performance.)

116

Agenda
1. Overview 2. Architecture 3. Channel Structure 4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles RBS KPI 6. Capacity Management 6. KPIs
117

RBS Counters KPIs

This appendix reports the main KPIs that could be used for HS testing divided by:
Throughput Scheduling Ratio and Transmission efficiency CQI/ACK/NACK Power RBS RSSI

Note that performing tests with a single HS user in a unloaded network is useful to:
Have specific user information for a user Verify counters/KPI meanings and compare them with UE based KPI

118

Throughput Counters
Counters:
pmSumAckedBits: the number of Media Access Control high-speed (MAC-hs) bits received and acknowledged by the UE. pmSumTransmittedBits: the number of transmitted bits at MAC-hs, level including retransmissions pmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data. pmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the RBS. pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is scheduled for priority queue.

Still not used:

pmAverageUserRate (PDF): The distribution of the average user rate among all users allocated to high-speed-DSCH in the cell.

119

Throughput KPIs
DSCH UE Thr. NET = Av. Throughput (PS-HS) without retransmission:
Sum(pmSumAckedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002s)

DSCH UE Thr. GROSS = Av. Throughput (PS-HS) with retransmission:

Sum(pmSumTransmittedBits)/(Sum(pmSumNonEmptyUserBuffers)*0.002)

DSCH Cell Thr. NET = The MAC-hs throughput on cell level

pmSumAckedBits / (0.002s * pmNoActiveSubFrame)

DSCH Cell Thr. GROSS = The MAC-hs data rate on cell level
pmSumTransmittedBits / (0.002 s* pmNoActiveSubFrame)

Cell Thr. NET = The MAC-hs throughput on cell level

pmSumAckedBits / (ROP period)

Cell Thr. GROSS = The MAC-hs data rate on cell level

pmSumTransmittedBits / (ROP period)

120

Throughput KPIs Values Live Network

RBS Name Average RBS DSCH UE DSCH UE DSCH Cell DSCH Cell RBS Number Sector Throughput Throughput Throughput Throughput Sector Of UE In Carrier NET GROSS NET GROSS a Queue 3 1 1 92.32 148.32 194.89 313.11 2 2 1 164.11 221.32 265.44 357.98 1 2 1 183.97 202.45 292.65 322.04 3 2 1 218.77 259.69 218.77 259.69 2 1 1 242.96 350.73 242.96 350.73 3 1 1 248.4 405.3 248.4 405.3 2 2 1 324.44 405.58 324.79 406.02 1 1 1 352.6 566.15 491.79 789.63 2 1 1 389 518.5 389 518.5 1 2 1 399.94 542.16 399.94 542.16 3 1 1 424.5 500.75 424.5 500.75 2 1 1.01 449.73 749.43 461.94 769.76 1 1 1 456.78 565.98 456.78 565.98 3 2 1 509.66 552.27 509.66 552.27 2 1 1 518.67 518.67 518.67 518.67 1 2 1 556.41 648.95 557.03 649.67 1 1 1 632.88 838.31 632.88 838.31 2 1 1 652.58 878.57 751.29 1,011.47 1 1 1 662.62 1,142.64 662.62 1,142.64 3 1 1 710.73 1,071.00 710.73 1,071.00 3 1 1.01 734.94 901.09 828.62 1,015.96 3 2 1 764.56 995.06 817.15 1,063.51 1 1 1 770.18 1,170.15 775.24 1,177.84 1 1 1 828.63 1,319.63 933.18 1,486.14 2 1 1 881.87 1,205.44 913.16 1,248.20 1 2 1 1,183.36 1,390.58 1,193.88 1,402.94 2 2 1 1,200.85 1,605.63 1,200.85 1,605.63 3 2 1 1,285.29 1,503.11 1,285.65 1,503.53 2 2 1 1,318.85 1,537.49 1,354.04 1,578.52

RBS32601-01 RBS05314-01 RBS37058-01 RBS00003-01 RBS34645-01 RBS01281-01 RBS37058-01 RBS01780-01 RBS00357-01 RBS00429-01 RBS37242-01 RBS34375-01 RBS01263-01 RBS23074-01 RBS23066-01 RBS04995-01 RBS00370-01 RBS01546-01 RBS01281-01 RBS34375-01 RBS23025-01 RBS37058-01 RBS00353-01 RBS34645-01 RBS23025-01 RBS05314-01 RBS00429-01 RBS01164-01 RBS01164-01
121

Transmission efficiency KPIs

MAC Tx efficiency (or Efficiency factor ) =
Sum(pmNoActiveSubFrame )/ (Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame))

Scheduling Ratio = This KPI simply highlights the percentage of time the HS-DSCH is used
Sum(pmNoActiveSubFrame)*0.002/ (ROP period)

Transmission ratio = This highlight the percentage of time there is something to transmit. This is a good index
on how efficiently the application level can exploit DSCH capabilities (Sum(pmNoActiveSubFrame)+Sum(pmNoInactiveRequiredSubFrame))*0.002 / (ROP period)

Av.# UEs in queue

Sum(pmSumNonEmptyUserBuffers) / ( Sum(pmNoActiveSubFrame)+ Sum(pmNoInactiveRequiredSubFrames) )

122

Transmission Efficiency (1/2)

The first index to look at when talking about transmission efficiency is the ratio between the used TTI (the one where something is transmitted) and the total #TTI in the test period

Scheduling Ratio = 81.3% ( + )

PDU is transmitted Nothing transmitted

Mac Tx Efficiency = 99.05% ( + )

Buffer not empty but PDU not transmitted

Transmission Ratio = 82.8% ( + ) (

123

Transmission Efficient KPIs Values Live Network

RBS Name RBS32601-01 RBS05314-01 RBS37058-01 RBS00003-01 RBS34645-01 RBS01281-01 RBS37058-01 RBS01780-01 RBS00357-01 RBS00429-01 RBS37242-01 RBS34375-01 RBS01263-01 RBS23074-01 RBS23066-01 RBS04995-01 RBS00370-01 RBS01546-01 RBS01281-01 RBS34375-01 RBS23025-01 RBS37058-01 RBS00353-01 RBS34645-01 RBS23025-01 RBS05314-01 RBS00429-01 RBS01164-01 RBS01164-01
124

% % Sector Carrier Scheduling Tranmission Ratio Ratio 3 2 1 3 2 3 2 1 2 1 3 2 1 3 2 1 1 2 1 3 3 3 1 1 2 1 2 3 2 1 2 2 2 1 1 2 1 1 2 1 1 1 2 1 2 1 1 1 1 1 2 1 1 1 2 2 2 2 0.00% 1.54% 0.01% 0.00% 0.00% 0.00% 0.11% 0.00% 0.00% 0.03% 0.00% 0.00% 0.00% 0.00% 0.00% 0.12% 0.02% 0.06% 0.00% 0.15% 0.11% 0.01% 0.03% 0.34% 0.09% 0.06% 0.07% 0.03% 0.14% 0.00% 2.49% 0.02% 0.00% 0.00% 0.00% 0.11% 0.00% 0.00% 0.03% 0.00% 0.00% 0.00% 0.00% 0.00% 0.12% 0.02% 0.07% 0.00% 0.15% 0.12% 0.01% 0.03% 0.38% 0.09% 0.06% 0.07% 0.03% 0.15%

CQI/ACK/NACK counters
pmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in the cell and received by the RBS. pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for the HS-DSCH. Within the reportedCQI tables, there is a column called InvalidCQI. This counter will be used as well

pmAckReceived: The number of Acknowledgements (ACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH). pmNackReceived: The number of Negative-Acknowledgements (NACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH).

125

CQI/ACK/NACK KPIs
HS-BLER: pmNackReceived /(pmNackReceived + pmAckReceived) RtxOverhead = Percentage of the Retransmitted bits over the total
100*(pmSumTransmittedBits - pmSumAckedBits) /(pmSumTransmittedBits)

CQI specific
Av. Reported Av. USed CQI Delta CQI = Difference between the 2 averaged values above. This is an index of how much CQI adjustment acts. CQIequalTo0 = Count(CQIreported=0)/Count(CQIreported). This is the main reason of MAC inefficiency InvalidCQI = invalideCQI/Count(CQIreported). Not clear what invlid means

Proposal: (ACK+NACK)/ActiveTTI: still not clear WHAT WE CAN SEE FROM IT

(pmNackReceived+pmAckReceived)/ActiveFrame

126

HS scheduling
Baseline Test 2

The BLER is the ratio between NACK and (ACK + NACK) The Rtx overhead is the ratio between the transmitted and the acked bits Delta CQI could be seen as index of the CQI adjustment impact When 0 is received no transmission will be allowed to the mobile for the following TTI

Reported BLER [%]

RtxOverhead [%] Av Reported CQI Av Used CQI Delta CQI (ACK+NACK)/Active [%] CQI = 0 [%]

12,6 14,8
10,1 9,8 0,32 98,68 0,79

12,5 15,0
17,0 16,5 0,48 97,29 0,01

The CQI=0 percentage drop to 0.01%, almost nothing. The BLER and the Retransmission rate are almost identical, that means the CQI adjustment has been able to reach the target

127

Integrity KPIs Values Live Network

RBS RBS Name Sector RBS23066-01 RBS37058-01 RBS37242-01 RBS23074-01 RBS05314-01 RBS04995-01 RBS01164-01 RBS05314-01 RBS01164-01 RBS01263-01 RBS23025-01 RBS37058-01 RBS00003-01 RBS37058-01 RBS34375-01 RBS01546-01 RBS00370-01 RBS00429-01 RBS32601-01 RBS23025-01 RBS34375-01 RBS01780-01 RBS00429-01 RBS00357-01 RBS34645-01 RBS00353-01 RBS34645-01 RBS01281-01 RBS01281-01
128

RBS Sector Carrier 2 1 3 3 2 1 2 1 3 1 3 2 3 3 2 2 1 1 3 2 3 1 2 2 1 1 2 3 1 1 2 1 2 2 2 2 2 2 1 1 2 2 2 1 1 1 2 1 1 1 1 2 1 1 1 1 1 1

MAC % HS% Rtx Transmission BLER Overhead Efficiency 0.00% 0.00% 100.00% 4.14% 9.13% 62.87% 8.85% 15.23% 100.00% 9.43% 7.72% 100.00% 10.01% 25.85% 61.83% 11.74% 14.26% 99.89% 12.03% 14.22% 97.41% 12.99% 14.90% 99.12% 13.28% 14.49% 99.97% 13.64% 19.29% 100.00% 14.18% 18.44% 89.32% 14.34% 20.01% 99.89% 15.38% 15.76% 100.00% 18.06% 23.16% 93.56% 18.24% 39.99% 98.14% 18.33% 25.72% 87.02% 18.44% 24.51% 100.00% 19.62% 26.23% 100.00% 21.05% 37.76% 47.37% 22.70% 26.84% 96.60% 23.36% 33.64% 100.00% 23.64% 37.72% 71.70% 24.27% 25.21% 100.00% 25.00% 24.98% 100.00% 27.50% 37.21% 88.80% 28.36% 34.18% 99.35% 30.77% 30.73% 100.00% 33.68% 38.71% 100.00% 38.09% 42.01% 100.00%

RBS power
pmTransmittedCarrierPowerNonHs: The transmitted carrier power for all non high-speed codes in the cell.
pmTransmittedCarrierPower: the transmitted carrier power measured at the TX reference point every 4 seconds.

Notes:
Every 100 ms the transmitted carrier power for all non high-speed codes in the cell are sampled. The problem is that there are not necessary data enough to transmit in every slot: hence some kind of normalization should be investigated.

129

Tx Power examples
(almost 100% of Scheduling Ratio)

The power is calculated at the antenna reference point

0.6

0.5

TxCarrierPower
0.4

R99Power

0.3

0.2

0.1

1. 0

1. 3

1. 6

2. 0

2. 5

3. 2

4. 0

5. 0

6. 3

7. 9

10 .0

12 .6

15 .8

130

CCH power = 1.7

The Max power = 8.7

20 .0

Transmitted Power (2/2)

The Average Tx power is:
Total Carrier = 4.85 W R99 power = 1.63 W TotalHS_power = 3.22 W

Note that the HS power is an estimation of the power transmitted for the HS on average during the test period but it is NOT an estimate of the power that HS required in the cell!
The activity of the HS (when we transmit something) is still low (80%). Maybe a more interesting KPI could be: TotalHS_power/SchedulingRatio*100
= 100*3.22/81.3 = 3.96 W

It is interesting to notice anyway that even with a single user the MaxTxPower is reached.

131

RBS list of counters

pmTransmittedCarrierPowerNonHs: The transmitted carrier power for all non high-speed codes in the cell. pmTransmittedCarrierPower: the transmitted carrier power measured at the TX reference point every 4 seconds pmNoActiveSubFrames: the number of subframes containing high-speed data transmitted by the RBS. pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is scheduled for priority queue. pmSumNonEmptyUserBuffers: The number of user buffers containing high-speed data. pmSumAckedBits:the number of Media Access Control high-speed (MAC-hs) bits received and acknowledged by the UE. pmSumTransmittedBits: Description The number of transmitted bits at MAC-hs, level including retransmissions pmReportedCqi: the Channel Quality Indicators (CQI) reported by the UE in the cell and received by the RBS. pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for the HS-DSCH. pmAckReceived: The number of Acknowledgements (ACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HSDSCH). pmNackReceived: The number of Negative-Acknowledgements (NACK) that the RBS receives from the User Equipment (UE) over the High-Speed Downlink Shared Channel (HS-DSCH). pmAverageRssi: The average Received Signal Strength Indication (RSSI).

132

Agenda
1. Overview 2. Architecture 3. Channel Structure 4. Accessibility & Mobility Principles 5. InterFrequency Mobility Principles RNC KPI 6. Capacity Management 6. KPIs
133

Cell Availability (1)

1) HS cell Availability (24 Hours period)

Av_HS(Hsdsch)

24 * 3600 (pmHsDownti meAuto pmHsDownti meMan) *100 24 * 3600

2) percentage of unplanned HS downtime (24 Hours period)

Av_Auto_HS(Hsdsch)

pmHsDownti meAuto *100 24 * 3600

3) percentage of planned HS downtime (24 Hours period)

Av_Man_HS(Hsdsch)

pmHsDownti meMan *100 24 * 3600

The length of time in seconds that a cell is available for Packet Interactive HS service is defined as cell HS availability. in the example, the cell HS availability during 24 hour period is reported.

134

Accessibility
The number of attempted RAB establishments for PS Interactive The new and existing cell counters used in the PS RAB establishment RAB procedure are givenHS-DSCH (stepped for the selected Serving HS-DSCH cell mapped on in the following list: at RAB establishment and before possible Inter-Frequency HO).
Counter name

The number of successful RAB establishments for PS New/existing Interactive RAB mapped on HS-DSCH. Number of successful Hard HO for serving Existing HS-DSCH cell selection (in the source cell). Number of successful Hard HO for serving New HS-DSCH cell selection (in the target cell).
New Existing

pmNoRabEstablishAttemptPacketInteractive pmNoRabEstablishSuccessPacketInteractive

pmNoRabEstablishAttemptPacketInteractiveHs
pmNoRabEstablishSuccessPacketInteractiveHs pmNoOutgoingHsHardHoAttempt pmNoIncomingHsHardHoAttempt pmNoHsHardHoReturnOldChSource pmNoHsHardHoReturnOldChTarget

New

Number of failed Hard HO for serving HSNew DSCH cell selection and UE connection maintained (in the source cell).
New

135

NumberNewfailed Hard HO for serving HSof DSCH cell selection and UE connection maintained (in the target cell).

Accessibility/ IF counters

136

Accessibility

PS Interactive Total RAB establishment, success rate =

pmNoRabEstablishSuccessPacketInteractive

100 *

(pmNoRabEstablishAttemptPacketInteractive pmNoOutgoingHsHardHoAttempt + pmNoIncomingHsHardHoAttempt +pmNoHsHardHoReturnOldChSource- pmNoHsHardHoReturnOldChTarget )

PS Interactive HS RAB establishment success rate =

100 *
pmNoRabEstablishSuccessPacketInteractiveHs pmNoRabEstablishAttemptPacketInteractiveHs

137

InterFrequency Handover
1) PS Interactive HS Hard Handover outgoing success rate

PS_M_HSHar dOut_S

pmNoOutgoi ngHsHardHo Success *100 pmNoOutgoi ngHsHardHo Attempt

2) PS Interactive HS Hard Handover incoming success rate

PS_M_HSHar dIn_S

pmNoIncomi ngHsHardHo Success *100 pmNoIncomi ngHsHardHo Attempt

pmNoHsHard HoReturnOl dChSource *100 pmNoOutgoi ngHsHardHo Attempt

3) PS Interactive HS Hard Handover return to old channel rate (source Cell)

PS_M_HSHar dOldCh_Sou rce

4) PS Interactive HS Hard Handover return to old channel rate (target Cell)

PS_M_HSHar dOldCh_Tar get

pmNoHsHard HoReturnOl dChTarget *100 pmNoIncomi ngHsHardHo Attempt

5) PS Interactive HS Hard Handover outgoing Lost connection rate

PS_M_HSHar dOut_Lost pmNoOutgoi ngHsHardHo Attempt - (pmNoOutgo ingHsHardH oSuccess pmNoHsHard HoReturnOl dChSource) * 100 pmNoOutgoi ngHsHardHo Attempt

6) PS Interactive HS Hard Handover incoming Lost connection rate

P S_M_HSHar dIn_Lost
138

pmNoIncomingHsHardHo Attempt - (pmNoIncom ingHsHardH oSuccess pmNoHsHard HoReturnOl dChTarget) * 100 pmNoIncomingHsHardHo Attempt

Retainability
The new and existing cell counters used for Retainability are given in the following list: Number of system releases of packet RABs mapped New/existing on HS-DSCH in the Serving HS-DSCH cell. Number of successful normal releases of packet RABs mapped on HS-DSCH in the Serving HS-DSCH cell. Existing
Existing Existing

Counter name

pmNoSystemRabReleasePacket pmNoNormalRabReleasePacket pmChSwitchFachIdle pmNoTpSwitchSp64Speech

pmNoSystemRbReleaseHs
pmNoNormalRbReleaseHs pmInactivityHsIdle

The number of signalling connection releases Existing triggered for PS Interactive RAB mapped on HSDSCH due to inactivity (Channel Switching New Evaluation algorithms request the execution of a switch to idle). New
The counter is stepped at the reception of RANAP Iu Release Command from CN, for HS channel cell or RANAP RAB New assignment Request (when the RAB is released) and the RANAP cause is User Inactivity.

139

Retainability

HS Radio Bearer retainability, drop rate =

pmNoSystemRbReleaseHs pmNoSystemRbReleaseHs + pmNoNormalRbReleaseHs

100 *

Total PS Interactive retainability, drop rate =

( pmNoSystemRabReleasePacket )

100 *

pmNoSystemRabReleasePacket + pmNoNormalRabReleasePacket

140

System Utilization
It is possible to measure HS A-DCH utilisation in terms of code usage and average number of users per cell. Two new set of counters shall be implemented. The first set is used to observe the HS ADCH code utilisation per cell. The KPI indicates the the total number of A-DCH radio bearers established in a cell.
( pmSumPsHsAdchRabEstablish /pmSamplePsHsAdchRabEstablish )

The second set is used to observe the average number of users per cell (hence the number of HS users), which is done by looking only at the best cell:
(pmSumBestPsHsAdchRabEstablish /pmSampleBestPsHsAdchRabEstablish )

141

Throughput

142

Throughput
1) Average Throughput for PS interactive HS (RNC Level)
PintHS_I_TP pmSentPack etDataHs1 pmSentPack etDataHs2 pmSentPack etDataHs3 pmSentPack etDataHs4 *8 pmTotalPac ketDurationHs1 pmTotalPac ketDurationHs2 pmTotalPac ketDurationHs3 pmTotalPac ketDurationHs4

2) Retransmission Rate for PS interactive HS

(RNC Level)

PintHS_I_R 1 et
Where:

pmSentPack etDataHs1 pmSentPack etDataHs2 pmSentPack etDataHs3 pmSentPack etDataHs4

PDHs12 PDHs 34

PDHs12 pmSentPacketDataIncl RetransHs1 pmSentPacketDataIncl RetransHs2

PDHs 34 pmSentPacketDataIncl RetransHs3 pmSentPacketDataIncl RetransHs4

3) HSDPA total RLC data Traffic DL [MByte]

(RNC Level)

PintHS_I_DATA
143

pmSentPack etDataHs1 pmSentPack etDataHs2 pmSentPack etDataHs3 pmSentPack etDataHs4

1000000

Retrans rate live RNC

Object Name RNCCN1 RNCKS1 RNCKS2 RNCNY1

Retrans Rate PS Int HS 99.63% 99.49% 100.00% 98.03%

144

Mobility
For mobility only the HS serving cell Note that no change procedure is considered .AC is

requested in the cell change procedure

Counter name
pmNoHsCcSuccess pmNoHsCcAttemptt

New/existing
New New

The corresponding KPI is 1) Success rate for HS Cell Change in target cell
PS_M_HSCC_ S pmHsCcSucc ess *100 pmHsCcAtte mpt

145

Admission & Congestion Control

Number of of radio links that are on SF=4 in UL
pmSumSf4Ul /pmSamplesSf4Ul

RNC counter monitoring no. of admission rejects (RAB setup) of HSDPA users
pmNoOfNonHoReqDeniedHs

RNC counters monitoring no. of HSDPA users (connections) released due to congestion
pmNoOfTermHsCong & pmNoOfIurTermHsCong

146