Академический Документы
Профессиональный Документы
Культура Документы
p
Seminar
Corrado Carbone - RO/QoS South
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
2
Outline
Modulation
Retransmission schemes
Scheduling
Usage
g of Power and Code
For P4 onlyy 5 codes ((SF = 16)) will be available for the HSDPA feature and they
y will be
shared on a time base.
SF=1
SF 2
SF=2
SF=4
SF=8
SF=16
TTI
Shared
channelization
codes
User #1
User #2
User #3
User #4
The
Th Shared-channel
Sh d h
l transmission
i i allows:
ll
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.
The Shared
Shared-channel
channel transmission impacts:
Scheduling become more complex
2 ms
Th
The Transmission
T
i i Time
Ti
Interval
I t
l becomes
b
extremely
t
l short
h t in
i HSDPA;
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!
Rel 5 (HS-DSCH)
2 ms
Earlier releases
10 ms
20 ms
40 ms
80 ms
2 ms
P
Power
3GPP Release 99
3GPP Release 5
Tota
al cell power
Tota
al cell powerr
Unused power
HS-DSCH
HS
DSCH (rate controlled)
t
HS-DSCH with dynamic power allocation
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
Li k
Link
Adaptation
UE category
Traffic ((buffers state))
10
Modulation
TFC
Bit
Rate
feedback
High data rate
Low data rate
11
feedback
High data rate
Low data rate
12
User1
User2
User3 User4
2 ms
2 ms
time
Scheduled
user
ser
User 1
low data rate
User 2
Time
#1
14
#2
#1
#2
#1
#2
#1
HSDPA iintroduces
t d
a new retransmission
t
i i llevell under
d th
the RLC scheme
h
iin th
the
RNC.
This new level allows rapid
p 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
d
d error rates
t ffor retransmissions
t
i i
P1,1
P1,2
P2,1
P2,2
P3,1
Transmitter
P1,1
Receiver
15
P1,2
+
P1,1
P2,1
P2,2
+
P2,1
P3,1
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
S
t off HS-PDSCH
HS PDSCH Yes/No
Y /N
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
17
X 10 =
RLC SDU
= 320
RLC
head = 16
+
MAC- HS SDU
head = 3360
MAC- HS
head = 21
= 3440 bits
Padding
bits = 59
That means the DSCH max scheduled bit rate could be 1720 kb/s:
That is including headers, padding and every type of retransmission
kb/s =320*10/2
In reality considering at least the HS retransmissions at this level the maximum bit rate could not be higher
than 1600*0.9 =1440 bit/s
18
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
19
RBS
Uu
User Data
RLC
MAC
MAC-hs
MAC
hs
L1
SRNC
Iub
Iu
CN
User Data
RLC
MAC
L1
GTP-U
UDP/IP
GTP-U
UDP/IP
FP
FP
AAL2
ATM
AAL2
ATM
AAL5
ATM
AAL5
ATM
PHY
PHY
PHY
PHY
The figure
g
shows the R99 pprotocol stack.
Note in particular that MAC is a protocol between the RNC and the
UE
20
RBS
Uu
Iub
User Data
RLC
MAC-d
SRNC
Iu
CN
User Data
MAC hs
MAC-hs
MAC hs
MAC-hs
HS-DSCH
FP
AAL2
ATM
L1
L1
PHY
RLC
MAC-d
HS-DSCH
FP
AAL2
ATM
PHY
GTP-U
UDP/IP
GTP-U
UDP/IP
AAL5
ATM
AAL5
ATM
PHY
PHY
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
ft combining
bi i off retransmitted
t
itt d transport
t
t blocks,
bl k new
physical channels, etc.).
21
RBS
Uu
Iub
SRNC
RRC
RRC
RLC
MAC-d
RLC
MAC-d
HS-DSCH
FP
AAL2
ATM
PHY
MAC hs
MAC-hs
MAC hs
MAC-hs
HS-DSCH
FP
AAL2
ATM
L1
L1
PHY
Iu
CN
GTP-U
UDP/IP
GTP-U
UDP/IP
AAL5
ATM
AAL5
ATM
PHY
PHY
RBS
Uu
Iub
SRNC
Iu
TCP/IP
CN
TCP/IP
RLC
MAC-d
MAC hs
MAC-hs
MAC hs
MAC-hs
HS-DSCH
FP
AAL2
ATM
L1
L1
PHY
RLC
MAC-d
HS-DSCH
FP
AAL2
ATM
PHY
GTP-U
UDP/IP
GTP-U
UDP/IP
AAL5
ATM
AAL5
ATM
PHY
PHY
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
24
RNC
No HW upgrades
Only SW!!
Setup of HS-DSCH/HS-SCCH
R99:
Scheduling,
TF selection,
Link layer
retransmission
(ARQ)
HSDPA:
Scheduling,
g
Link
Adaptation,
Hybrid ARQ
25
Core
Network
RNC
Node B
Node Functionality
Iu
RNC Function:
RNC
Iur
Iub
Resource handling
Associated
Dedicated
Ch
Channels
l
Capacity management
L2 (MAC-d)
UL HS control channel power control
Certain flow control
26
Node Functionality
Iu
RBS Function:
RNC
Iur
L2 (MAC-hs)
Scheduling
Iub
27
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
28
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
CN
RNC
UE
RBS
DCCH
RRC
For each
user
DPCCH
DCCH
DCH
NAS
DCCH
DCH
DPCH
DPDCH
HS
- DPCCH
NAS
DCCH
HS SCCH
HS-SCCH
Interactive PS RAB
DTCH
User 1
Interactive PS RAB
DTCH
User 2
Interactive PS RAB
User n
- Interactive
- Background
31
HS-PDSCH
DTCH
Iu
Radio Access Bearers:
HS -DSCH
Iub
Logical Channels:
-Dedicated Control Channel, DCCH
-Dedicated Traffic Channel, DTCH
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
HS DSCH Shared Control Channel
Channel, HS-SCCH
-High Speed Physical Downlink Shared Channel, HS-PDSCH
The HS
HS-DSCH
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 att the
th base
b
station
t ti left
l ft from
f
the
th common and
d dedicated
d di t d channels
h
l
32
Never
Ne er in soft hando
handover
er
The HS-SCCH has a spreading factor SFHS-DSCH = 128
33
34
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
HS-DPCCH
DPCCH (UL) iis ttransmitted
itt d within
ithi a dedicated
d di t d channel.
h
l Th
The main
i id
idea
is that it is power controlled from the other part of the A-DCH.
35
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.
RNC
The resulting MAC-d PDUs are transmitted over Iub to the RBS using the HSDSCH frame protocol.
The MAC
MAChs
hs receive the Channel Quality Indicator adjusted
adjusted by the Node B
The MAC-hs scheduling function selects in each TTI the user to which the HSDSCH is transmitted.
Following
g the selection of a user, the user data to transmit on the HS-DSCH is p
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
38
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)
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
39
Accessibility:
Call setup phases
Iu
RNC
RNC
Iur
Camping in idle
3
4
Iub
Iub
3
f2 HS
f2 HS
f1
f1
f2 HS 2
f1
f1
f1
f1
1
40
Iub
Associated
Dedicated
Channels
RRM policy
Speech
CS Streaming
New!
Int. 64/384
SP64
PS Streaming+Int 8/8
Int. 64/128
SP0
Int. 64/64
UDI (CS64)
UDI+Int. 8/8
New!
New!
SP0 not available
RAB Release
RAB Establishment
E t bli h
t
Channel Switching
41
Int. FACH
SRB
HS-DSCH
(uplink 64 or 384)
RAB
Establishment
RAB Release
SRBDCH
Signaling
Connection
handling
Idl
e
42
Ec/No
HS+f1
f2 HS
f2 HS
f2 HS
f1
f1
f1
HS+ f1
f2
f1
RAB establishment
UTRAN
UE
SGSN
SRB - DCH
HSDPA
S
capab
capability
ya
analysis
a ys s
2
Possible Inter frequency hard handover
3
Radio Bearer setup
44
Capability analysis
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
g UE capability
p
y check for L2 are successful
UE
UTRAN
SGSN
SRB - DCH
RANAP: RAB Assignment Request
(establish PS Interactive/Background RAB)
46
If the
h HS-DSCH
HS DSCH iis enabled
bl d iin th
the ttargett cell,
ll an hard
h dh
handover
d
New active set
is tried to the new selected cell.
If no cells
ll are available
il bl and
d th
the connection
ti iis established
t bli h d on an
interactive DCH.
DCH
Coverage relations
The coverage relation is a unique uni-directional relation between two
cells,
ll a source and
d a ttargett cell.
ll
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):
25 423):
hsPathLossThreshold
utranCellRef (the target cell)
coverageIndicator
47
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
ff1
1
f1
f1
f1
f1
1st carrier
49
UE
RB setup (1/2)
SRNC
2. Allocate resources
DRNC
DRNC
1. Admission request
q
RBS
RBS
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.
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
p to 5 HS-PDSCH codes in downlink.
up
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 AA
DCH:
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.
52
53
HS-DSCH
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
54
Speech
call
Incoming CS call
Iub
no multi RABs
UE
f f HSf2 HS f HS
UTRAN
MSC SGSN
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
56
Mobility:
Intra--HSDPA
Intra
Since No Soft/Softer HO exist for HSDSCH there will be only one serving
DSCH,
Iu
cell for the HS-DSCH.
Iu
RNC
RNC
Iur
Iub
Iub
57
Associated
Dedicated
Channels
Iub
58
1 layer
f
59
HS
f2 HS
HS
f2 HS
f
f2 HS
f1
f1
2 layers
f2 HS
f1
f1
f1
f1
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
Note that the RNC can configure more than 1 measurement report for the
same event.
61
Mobility Example
2
0
cell 1
cell 2
cell 3
event 1a:
Add cell 2, to the AS
Add cellll 3
3, tto th
the AS
-5
Ec/N0 [dB]
event 1b:
Delete cell2
-10
-15
event 1d:
Change of best cell, to cell 3
-20
0
10
time [s]
62
15
63
A-DCH handover
In the previous slide it is stated that there will be only one serving cell for
th HS-DSCH.
the
HS DSCH Thi
This d
does nott mean th
thatt th
the UE iis connected
t d tto only
l 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
I the
th example
l supposing
i the
th b
bestt server d
does nott change...
h
A-DCH
HS--DSCH
HS
R99
64
R99
HS
R99
HS
S
HS
HS
HS
HS
HS
HS
65
66
Measurement
quantity
IInitially
iti ll A
A-DCH
DCH and
d HSDPA
both only on cell 1 P_CPICH 1
Rep. Range 1b
Rep. Range 1a
P_CPICH 2
h
hysteresis
i _ 1d hs
h
A-DCH on cell 2
only
Reporting
event 1a
Reporting
event 1d-hs
Reporting
event 1b
time
Ex1
f HS
f2 HS2 f2 HS
R99
Cell Selection
f HS
f HS
f1 HS2 f1 HS f1 HS2 f1 HS
RNC
RNC
Cell Selection
f HS
R99 2
R99
HS
HS
68
f HS
R99 2
HS
HS
Ex3
f2 HSf2 HSf2 HS
R99
R99
R99
f2 HSf2 HSf2 HS
Ex 2
R99
R99
Ex 4
GSM
GSM
GSM
GSM
GSM
GSM
Ex 5
R99f2 HS HS
R99
HS
R99
R99
R99
R99
GSM
GSM
GSM
GSM
GSM
GSM
69
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
70
Carrier mobility
A user conected with a UMTS network on a certain carrier can move out of
the its layer coverage
coverage.
There are 2 mechanisms to avoid the drop, at least for some services:
Inter-RAT
Inter RAT Handover
Inter-Frequency Handover
f2 HS
f2 HS
f1
f2 HS
f1
f1
f1
f1
f1
GSM
GSM GSM
GSM
GSM
GSM
GSM GSM
GSM
GSM
GSM
GSM
71
UE moves to poor
carrier coverage area
and reports to UTRAN
UTRAN
UTRAN commands
CM measurements
5
72
Core
Network
GSM/
Other Carrier
Layer Quality
Threshold 1
Threshold 2
Threshold 3
time
The p
problem is that there are several thresholds
73
L1
CM
HOCompressed Mode
L2
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.
gsmThresh3a
For the second UMTS layer: the measured best cell on unused frequency is
above both the thresholds nonUsedFreqThresh4_2bEcno and
q
_
p
nonUsedFreqThresh4_2bRscp
74
CPICH
Ec/No
CPICH
RSCP
Start
CPM
UE TX
Initial
Cell
75
power
Start
CPM
Other layer
ggood enough
g
St t
HO Start
trigg CPM
HO
trigg
HO
trigg
gg
76
IF or IRAT?
Hence, for a certain cell only one of the 2 Handover types will
be allowed.
Where?
f2 HS
f1
f1
GSM
GSM
77
CIPICH dimensioning
Dimensioning example
79
Impact on coverage
CM start Tx Pwr
HO RSCP
CM start Ec/No
Area
WCDMA RBS
without
CM
HO Ec/N0
CM start RSCP
HO RSCP
80
Anyway:
th
they can experiment
i
t it when
h in
i connected
t d mode
d with
ith a R99 RAB or iin other
th d
dedicated
di t d
connection.
They can impact on other users behavior
81
GSM->WCDMA
entering area
WCDMA Service
WCDMA RBS
WCDMA->GSM normal
reselection area
Unstable areas
Ec/No>FDDQMIN
RSCP>GSM_RLA +FDDQOFF
Ec/No>qQualMin+sRATsearch
GSM coverage
82
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
83
Capacity Management
Algorithm
84
Dedicated Resources
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
(Air-Speech
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
86
85%
35%
75%
default values
Default values:
pwrOffset = +5% 90%
pwrHyst = 600 ms
87
Traffic Algorithms
88
The measurement of code tree utilization considers the codes allocated for HSPDSCH and HS-SCCH channels.
89
RNC
Iur
Associated
Dedicated
Channels
f HS
R99
90
f2 HS
R99
f2 HS1
R99
HS-DSCH:
91
16
C om m on
C h a n n els;
H S -S C C H
D e d ica te d
C h a n n els
H S -P D S C H
(d e fa u lt)
The operator configure and reserve the number of HS-PDSCH codes allocated in a
cell for HSDPA (numHsPdschCodes)
(
)
The operator
p
can limit the number
of users that can be allocated to the
HS-DSCH cell (hsdpaUsersAdm)
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
guaranteeed-hs / handover
Reject
Admisssion Granteed
guaranteeed-hs / non
n-handover
Reject
95
Admisssion
Granteed
pwrAdm beMarginPwrAdm
Admisssion Granteed
pwrAdm + pwrAdmOffset
pwrAdm
p
guaranteeed / handoveer
Reject
Power
Admisssion Granteed
guaranteeed / non-han
ndover
non-guarranteed / han
ndover
Reject
non-guarranteed /
non-hand
dover
HSDPA
To
otal availab
ble cell pow
wer
Dedicated channels
Common channels
96
ttmInitialG
I iti lG
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.
g
is restarted as
tmCongActionGhs
tmInitialGhs has not expired.
Time
This policy enforces the higher retention priority of
CS services compared
p
to interactive services
97
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
98
Load Sharing
Techniques
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
IF
50%
Time
Cell Lo
oad
Ce
ell Load
DR
thr
Time
100
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
This handover is a blind HO since the target cell is chosen not based on UE
measurements Therefore
measurements.
Therefore, the target cell must be co
co-located
located with the WCDMA
cell.
There are 2 control parameters:
l dSh i G Th h ld specifies
loadSharingGsmThreshold
the minimum cell load at which off-loading to GSM
begins.
loadSharingGsmFraction specifies
ifi
Cell Load
C
d
DR
loadSharingGsmThreshold
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.
g
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.
UMTS L1
3
1
>=<
Cell 2
2
Load
d
UMTS L2
Load
L
50%
Cell 1
GSM
102
IF Load Sharing
Here an example of comparison between 2 different frequency is reported.
L[2]
L[2] == 33%
33%----L[1]
L[1]= =60%
60%
L[1]
L[2]
R[2],
L[1]
L[2]>
Select
R[2]
Second Carrier
L[1] <
> 50
% ->20%
Select
Second
-> Dont
Compare
do anything
the
load Carrier
with the
Layer 2
Power/
pwrAdm
100%
33%
Layer 1
33% candidate
load sharing
loadSharingThreshold
(20%)
First
Carrier
Load
Load
Free
[ ]
ee Resource
esou ce = R[2]
>=<
C ll 2
Cell
Free
Resource
Free
Resource
33%
60%
Cell 1
DL power in use
100%
Power/
P
pwrAdm
loadSharingMargin (10%)
33%
Layer 1
100%
Load
Loa
ad
>=<
Cell 2
Power/
pwrAdm
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
Apart from the load sharing algorithm, other aspects have to be managed
and tuned with the introduction of the second layer:
Mobility:
Accessibility:
The first IF Load Sharing will increase the call set up time.
105
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.
Agenda
1 O
1.
Overview
i
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6 Capacity
6.
C
it Management
M
t
7. KPIs
106
Cell Breathing
UL
high
Loa
d
DL
high
Load
WCDMA RBS
UL low
load
Ec/N0Cpich = RSCP/RSSI
= Pcpich/( (PtotIntra + Ptotinter + Noise)
(*P = received power)
107
DL low
load
DL
hi h
high
Load
CM start
IRAT
WCDMA RBS
Agenda
1. Overview
2 Architecture
2.
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility Principles
6. Capacity Management
6 KPIs
6.
109
Accessibility KPI
Accessibility
y ((CSSR)) KPI
CSSR is currently calculated by two factors:
RRC Establishment Success Rate = RRC_Success / RRC_Attempts *
RAB Establishment Success Rate = RAB_Success
RAB Success / RAB
RAB_Attempts
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
events.
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 off IFLS.
IFLS
110
Proposed
p
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 =
pmTotNoRrcConnectReqCsSucc
pmTotNoRrcConnectReqCs
pmTotNoRrcConnectReqCs - pmNoLoadSharingRrcConn
pmTotNoRrcConnectReq
RRC _ Succ _ PS =
pmTotNoRrcConnectReqPsSucc
pmTotNoRrcConnectReqPs
pmTotNoRrcConnectReqPs - pmNoLoadSharingRrcConn
pmTotNoRrcConnectReq
The basic
Th
b i idea
id iis tto calculate
l l t th
the lload
d sharing
h i reject
j t ffor PS and
d CS b
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
instead....
RRC _ Succ _ general =
111
pmTotNoRrcConnectReqSucc
pmTotNoRrcConnectReq - pmNoLoadSharingRrcConn
120%
9000
100%
8000
7000
80%
6000
5000
4000
LoadSharingReject
60%
RRC_SUC_PS_LS
40%
3000
2000
20%
1000
0%
Days
112
RRC_SUC_CS_LS
120.0%
9000
100.0%
8000
7000
80.0%
6000
5000
60.0%
4000
40 0%
40.0%
3000
2000
20.0%
1000
0.0%
Days
113
L dSh i E t
LoadSharingEvents
RRC_SUC_LS
>100% values
105.0%
100.0%
RRC_SUC_LS
95.0%
RRC_SUC_CS_LS
RRC_SUC_PS_LS
90 0%
90.0%
85.0%
Strong KPI
deterioration
80.0%
D
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 =
pmTotNoRrcConnectReqSucc
pmTotNoRrcConnectReq - pmNoLoadSharingRrcConn
pmTotNoRrc
T N R ConnectReq
C
R CsSucc
CS
pmTotNoRrcConnectReqCs
pmTotNoRrcConnectReqCs - pmNoLoadSharingRrcConn
pmTotNoRrcConnectReq
RRC _ Succ _ PS =
pmTotNoRrcConnectReqPsSucc
pmTotNoRrcConnectReqPs
pmTotNoRrcConnectReqPs - pmNoLoadSharingRrcConn
ppmTotNoRrcConnectReqq
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
CSSR
CS = RRC
RRC_Succ_Global
Succ Global x RAB_CS_Succ
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
p
y related to different radio environment: i.e. the major
j p
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
bili Principles
i i l
RBS KPI
6. Capacity Management
6. KPIs
117
Throughput
Scheduling Ratio and Transmission efficiency
CQI/ACK/NACK
Power
RBS RSSI
118
Throughput Counters
Counters:
pmSumAckedBits: the number of Media Access Control high
high-speed
speed (MAC-hs)
(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:
N A ti S bF
the
th number
b off subframes
bf
containing
t i i hi
high-speed
h
dd
data
t ttransmitted
itt d b
by th
the
RBS.
pmNoInactiveRequiredSubFrames: the number of empty subframes transmitted even though data is
scheduled for priority queue.
119
Throughput KPIs
DSCH UE Thr. NET = Av. Throughput (PS-HS) without retransmission:
Sum(pmSumAckedBits)/(Sum(pmSumNonEmptyUserBuffers)*0
Sum(pmSumAckedBits)/(Sum(pmSumNonEmptyUserBuffers)
0.002s)
002s)
Cell Thr.
Thr NET = The MAC-hs throughput on cell level
pmSumAckedBits / (ROP period)
120
RBS32601-01
RBS05314-01
RBS37058-01
RBS00003-01
RBS34645-01
RBS01281-01
RBS37058 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
RBS01164-01
121
Average
RBS
DSCH UE
RBS
Number
Sector
Throughput
Sector
Of UE In
Carrier
NET
a Queue
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
1
1
1
1
1
1
1
1
1
1
1
1 01
1.01
1
1
1
1
1
1
1
1
1.01
1
1
1
1
1
1
1
1
92.32
164.11
183.97
218.77
242.96
248.4
324 44
324.44
352.6
389
399.94
424.5
449 73
449.73
456.78
509.66
518.67
556.41
632.88
652.58
662.62
710.73
734.94
764.56
770.18
828.63
881.87
1,183.36
1,200.85
1 285 29
1,285.29
1,318.85
DSCH UE
Throughput
GROSS
148.32
221.32
202.45
259.69
350.73
405.3
405 58
405.58
566.15
518.5
542.16
500.75
749 43
749.43
565.98
552.27
518.67
648.95
838.31
878.57
1,142.64
1,071.00
901.09
995.06
1,170.15
1,319.63
1,205.44
1,390.58
1,605.63
1 503 11
1,503.11
1,537.49
313.11
357.98
322.04
259.69
350.73
405.3
406 02
406.02
789.63
518.5
542.16
500.75
769 76
769.76
565.98
552.27
518.67
649.67
838.31
1,011.47
1,142.64
1,071.00
1,015.96
1,063.51
1,177.84
1,486.14
1,248.20
1,402.94
1,605.63
1 503 53
1,503.53
1,578.52
Scheduling Ratio = This KPI simply highlights the percentage of time the HS-DSCH is used
Sum(pmNoActiveSubFrame)*0
Sum(pmNoActiveSubFrame)
0.002/
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.#
Av # UEs in queue
Sum(pmSumNonEmptyUserBuffers) / ( Sum(pmNoActiveSubFrame)+ Sum(pmNoInactiveRequiredSubFrames) )
122
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
PDU is transmitted
Nothing transmitted
%
%
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.11%
0.00%
0.00%
0.03%
0.00%
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.03%
0.34%
0.09%
0.06%
0.07%
0 03%
0.03%
0.14%
0.00%
2.49%
0.02%
0.00%
0.00%
0.00%
0 11%
0.11%
0.00%
0.00%
0.03%
0.00%
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.03%
0.38%
0.09%
0.06%
0.07%
0 03%
0.03%
0.15%
CQI/ACK/NACK counters
pmUsedCqi: the CQI, used by the RBS for scheduling the priority queue for
the HS-DSCH.
125
CQI/ACK/NACK KPIs
HS-BLER: pmNackReceived /(pmNackReceived + pmAckReceived)
RtxOverhead = Percentage
g 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
g values above. This is an index of how much CQI adjustment
j
acts.
CQIequalTo0 = Count(CQIreported=0)/Count(CQIreported). This is the main reason of MAC inefficiency
InvalidCQI = invalideCQI/Count(CQIreported). Not clear what invlid means
(pmNackReceived+pmAckReceived)/ActiveFrame
126
HS scheduling
Baseline
R
Reported
t d BLER [%]
RtxOverhead [%]
Av Reported CQI
Av Used CQI
Delta CQI
(ACK+NACK)/Active [%]
CQI = 0 [%]
12,6
12
6
14,8
10,1
9,8
0,32
98,68
0,79
Test 2
12,5
12
5
15,0
17,0
16,5
0,48
97,29
0,01
127
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%
12.03%
14 22%
14.22%
97 41%
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%
14.34%
20 01%
20.01%
99 89%
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%
24.27%
25 21%
25.21%
100 00%
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%
33.68%
38 71%
38.71%
100 00%
100.00%
38.09%
42.01%
100.00%
RBS power
pmTransmittedCarrierPowerNonHs: The transmitted carrier power for all
non high-speed
hi h
d codes
d iin th
the cell.
ll
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
high-speed
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)
0 .5
0 .4
0 .3
0 .2
0 .1
130
.0
20
.8
15
.6
12
.0
10
9
7.
0
5.
6.
0
4.
2
3.
5
2.
2.
0
6
1.
3
1.
1.
0
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
100*3.22/81.3
3.22/81.3 = 3.96 W
It is interesting to notice anyway that even with a single user the MaxTxPower is
reached.
131
132
Agenda
1. Overview
2. Architecture
3. Channel Structure
4. Accessibility & Mobility Principles
5. InterFrequency Mobility
bili Principles
i i l
RNC KPI
6. Capacity Management
6. KPIs
133
Av_HS(Hsdsch) =
A A t HS(Hsdsch)
Av_Auto_HS
(H d h) =
pmHsDowntimeAuto
p
*100
24 * 3600
pmHsDowntimeMan
*100
Av_Man_HS(Hsdsch) =
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
reported.
134
Accessibility
attempted
establishments
PS Interactive RAB
The newThe
andnumber
existingofcell
countersRAB
used
in the PS RABfor
establishment
procedure
are given
in the
following
list: for the selected Serving HS-DSCH
mapped
on HS-DSCH
HS
DSCH
(stepped
HS DSCH cell
at RAB establishment and before possible Inter-Frequency HO).
Counter name
pmNoRabEstablishAttemptPacketInteractive
Existing
pmNoRabEstablishS ccessPacketInteracti e
pmNoRabEstablishSuccessPacketInteractive
pmNoRabEstablishAttemptPacketInteractiveHs
pmNoRabEstablishSuccessPacketInteractiveHs
pmNoOutgoingHsHardHoAttempt
pmNoIncomingHsHardHoAttempt
p
g
p
pmNoHsHardHoReturnOldChSource
pmNoHsHardHoReturnOldChTarget
135
New
NumberNew
of failed Hard HO for serving HSDSCH cell selection and UE
connection maintained (in the target cell).
Accessibility/ IF counters
136
Accessibility
100 *
(pmNoRabEstablishAttemptPacketInteractive
pmNoOutgoingHsHardHoAttempt + pmNoIncomingHsHardHoAttempt
+pmNoHsHardHoReturnOldChSource- pmNoHsHardHoReturnOldChTarget )
137
pmNoRabEstablishSuccessPacketInteractiveHs
pmNoRabEstablishAttemptPacketInteractiveHs
N R bE t bli hAtt
tP k tI t
ti H
InterFrequency Handover
1) PS Interactive HS Hard Handover outgoing success rate
PS_M_HSHardOut_S =
pmNoOutgoingHsHardHoSuccess
*100
pmNoOutgoingHsHardHoAttempt
PS_M_HSHardIn_S =
pmNoIncomingHsHardHoSuccess
*100
pmNoIncomingHsHardHoAttempt
PS M HSHardOldCh_Sou
PS_M_HSHar
dOldCh Source =
pmNoHsHardHoReturnOldChSource
* 100
pmNoOutgoingHsHardHoAttempt
PS M HSH dOldCh_Tar
PS_M_HSHar
dOldCh T get =
pmNoHsHard
p
No s a dHoReturnOl
o etu O dC
dChTarget
a get
*100
pmNoIncomingHsHardHoAttempt
Retainability
The new and existing cell counters used for Retainability are given in the
following list:
Counter name
pmNoSystemRabReleasePacket
pmNoNormalRabReleasePacket
pmChSwitchFachIdle
pmNoTpSwitchSp64Speech
pmNoSystemRbReleaseHs
pmNoNormalRbReleaseHs
pmInactivityHsIdle
139
Existing
Retainability
100 *
pmNoSystemRbReleaseHs
y
pmNoSystemRbReleaseHs + pmNoNormalRbReleaseHs
100 *
140
pmNoSystemRabReleasePacket + pmNoNormalRabReleasePacket
System Utilization
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
S P H Ad hR bE t bli h /pmSamplePsHsAdchRabEstablish
/
S
l P H Ad hR bE t bli h )
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:
141
(pmSumBestPsHsAdchRabEstablish /pmSampleBestPsHsAdchRabEstablish )
Throughput
142
Throughput
1) Average Throughput for PS interactive HS (RNC Level)
pmSentPacketDataHs1+ pmSentPacketDataHs2 + pmSentPacketDataHs3 + pmSentPacketDataHs4
PintHS_I_TP =
*8
pmTotalPacketDurationHs1 + pmTotalPacketDurationHs2 + pmTotalPacketDurationHs3 + pmTotalPacketDurationHs4
PintHS I Ret = 1
PintHS_I_R
(RNC Level)
PDHs12 + PDHs34
Where:
PDHs12 = ppmSentPacketDataInclRetransHs1 + p
pmSentPacketDataInclRetransHs2
PDHs 34 = pmSentPacketDataInclRetransHs3 + pmSentPacketDataInclRetransHs4
PintHS I DATA =
PintHS_I_D
(RNC Level)
1000000
143
Object Name
RNCCN1
RNCKS1
RNCKS2
RNCNY1
144
Retrans Rate
PS Int HS
99.63%
99.49%
100 00%
100.00%
98.03%
Mobility
For mobility only the HS serving cell
Note
that no .AC is
change procedure is
considered
requested
q
in the cell
change procedure
Counter name
New/existing
pmNoHsCcSuccess
New
pmNoHsCcAttemptt
New
145
pmHsCcSucc ess
* 100
pmHsCcAtte mpt
RNC counter
t monitoring
it i no. off admission
d i i rejects
j t (RAB setup)
t ) off HSDPA
users
pmNoOfNonHoReqDeniedHs
146