You are on page 1of 141

BSS Optimisation Workshop

Denpasar Bali
Oct 21-25, 2013
NSN TSEL

1 Nokia Siemens Networks


Radio Resource Administration

Idle Parameter Optimization

Radio resource Management

Measurement processing

Power Control Parameter

Handover Control parameter

KPI case

2 Nokia Siemens Networks


Radio Resource Administration

3 Nokia Siemens Networks


Basic TDMA Structure

5
4

e
3

tim
2
Physical channel 1
e.g. allocated to one 0
subscriber with FR voice 7
and no frequency hopping
6
5
4 TDMA frame
3 = 8 timeslots
2 ( 0.577ms * 8 = 4.615 ms)
1
0
7
6
5 2 2 2
4
3 TDMA frame
2
1
0
frequency
200 kHz
4 Nokia Siemens Networks
GSM Channel Organization

Logical Channels
for transport of specific content

mapping

MS Physical Channels
transport medium Base Station
Subsystem
Physical channel parameters
ARFCN
Time slot number
Frequency hopping algorithm

5 Nokia Siemens Networks


Logical Channels
FCCH Frequency Correction Channel

SCH Synchronisation Channel


DL
BCH
BCCH Broadcast Control Channel

CBCH Cell Broadcast Channel


Common
Channels
DL
PCH Paging Channel
UL
CCCH RACH Random Access Channel
DL
AGCH Access Grant Channel

SDCCH Stand alone Dedicated Control Channel


UL/DL
DCCH SACCH Slow Associated Control Channel

FACCH Fast Associated Control Channel


Dedicated
Channels
FR/HR Full rate / Halft rate TCH
UL/DL
TCH EFR Enhanced Full rate TCH

AMR FR/HR Adaptive multirate TCH (FR/HR)

6 Nokia Siemens Networks


Signalling Channel Mapping
(BCCH +CCCH/9)

Downlink
51 TDMA frames = 235 ms
1 51

f s f sf f s f s f s -

BCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH

Uplink
51 TDMA frames = 235 ms
1 51

r r r r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r

f = FCCH, s = SCH, r = RACH TDMA frame


- = dummy burst

7 Nokia Siemens Networks


Signalling Channel Mapping
(BCCH + SDCCH/4 + SACCH/C4)

Downlink
51 TDMA frames = 235 ms
1 51

f s f sf f s f s f s -

BCCH CCCH CCCH CCCH


SDCCH 0 SDCCH 2 SACCH
SDCCH 1 SDCCH 3 0/2 SACCH
1/3
Uplink
51 TDMA frames = 235 ms
1 51

rr f r r r r r r r r rf r r r r r r r r r rf r r r r f r r

SACCH SDCCH 0 SDCCH 2


SDCCH 3 2/0 SACCH SDCCH 1
3/1
f = FCCH, s = SCH, r = RACH TDMA frame
- = dummy burst
8 Nokia Siemens Networks
Traffic Channel Mapping

Full Rate Traffic Channel Configuration (UL & DL)


26 TDMA frames = 120 ms

t t t t t t t t t t t t sf t t t t t t t t t tf t t i

1 26
t = full rate TCH, s = SACCH/T, i = idle TDMA frame

Half Rate Traffic Channel Configuration (UL & DL)


26 TDMA frames = 120 ms

t t t t t t s t t t t t t
f f
T T T T T T T T T T T T S
...

1 26
t = half rate TCH, s = SACCH/T (first user)
T = half rate TCH, S = SACCH/T (second user) TDMA frame
9 Nokia Siemens Networks
Signalling Channel Mapping
(SDCCH/8 +SACCH/C4)

Downlink
51 TDMA frames = 235 ms
1 51

f i i i

SDCCH 0 SDCCH 2 SDCCH 4 SDCCH 6 SACCH SACCH


SDCCH 1 SDCCH 3 SDCCH 5 SDCCH 7 0/4 SACCH 2/6 SACCH
1/5 3/7
Uplink
51 TDMA frames = 235 ms
1 51

f fi i i

SACCH SDCCH 0 SDCCH 2 SDCCH 4 SDCCH 6 SACCH


SACCH 6/2 SACCH SDCCH 1 SDCCH 3 SDCCH 5 SDCCH 7 4/0
5/1 7/3
i = idle TDMA frame
10 Nokia Siemens Networks
Signalling Channel Mapping

New improved CCCH features in RG10


BSS20738 CS Paging Coordination in NMO II
BSS21538 Extended CCCH
Extended CCCH can be allocated to timeslot 2,4,6

BSS101411 Extended BCCH


For example Uncombined BCCH

11 Nokia Siemens Networks


Channel Mapping
Parameter Setting

MO Class TR/RTSL
Parameter channelxType (CHx) where x = 07

Channel configuration defined by parameter channelType

TCHF (0) = full rate traffic channel


TCHH (1) = half rate traffic channel
TCHD (2) = dual rate traffic channel
SDCCH (3) = standalone (SDCCH/8)
MBCCH (4) = broadcast control channel
MBCCHC (5) = BCCH + SDCCH/4
MBCCB (7) = BCCH + SDCCH/3 with CBCH
SDCCB (8) = SDCCH/7 with CBCH
NOTUSED (9) = timeslot has no radio definition or Abis allocation
ERACH (10) = random access channel of extended area
EGTCH (14) = EGPRS packed data traffic channel for extended area
LRTCH (15) = long reach traffic channel

Note:
Some values not allowed in certain tsl (e.g. TSL0
cant have value 8)
PBCCH is not supported in S13 and onwards

12 Nokia Siemens Networks


Paging Channel (PCH) Parameters

Mobile terminating call -> MSC performs paging

MS identifies paging message with the IMSI/TMSI


MS listens to own paging group only

SEG-BTS parameters
MO Abbreviated Range Description Default BSC - MML
Class Name And Step value Name
BTS noOfMFramesB 2...9, step Defines the number of multiframes between 4 MFR
etweenPaging 1 two transmissions of the same paging
message to the MSs of the same paging
group.

MSC parameters

Repaging Interval (INT) 0.5s10s Time between consecutive paging


attempts
Repaging Attempts (AT) 05 Number of paging repetitions

Buffering

BTS stores up to 8 paging messages of the MSC in page group buffer


BTS sends paging messages to MS according noOfMultiframesBetweenPaging

13 Nokia Siemens Networks


RACH Parameters

Mobile sends channel requests to BTS separated by random time intervals in case of no answer!

Parameters

MO Abbreviated Range And Step Description Default BSC - MML


Class Name value Name

BTS maxNumberRetra 1,2,4,7 Maximum number of retransmissions on the RACH 4 RET


nsmission that the MS can perform.

BTS nbrOfSlotsSpread MML Range: The number of TDMA frames over which 10 SLO
Trans 3..12, 14, 16, 20, retransmission is spread on the RACH (random
25, 32, 50 access channel)

Random time interval between consecutive retransmissions

t = S + random [0,.. numberOfSlotsSpreadTrans 1] RACH slots

S depends on numberOfSlotsSpreadTrans
signalling channel mapping (CCCH + SDCCH combined or not in one multi frame)

numberOfSlotsSpreadTrans = 10
signalling channel mapping = not combined S
= 58
Therefore t = 58..to..67 RACH slots
time channel requests

14 Nokia Siemens Networks


AGCH Parameters

Network gives the MS dedicated resources

Downlink CCCH blocks

PCH can be used for AGCH messages


AGCH cannot be used for PCH messages

Reservation of CCCH blocks for AGCH

noOfBlocksForAccessGrant (AG) 0..7 possible number, if CCCH and SDCCH are not combined
1..7 possible number, if CBCH is used in non combined
configuration
0..2 possible number, if CCCH and SDCCH are combined

Preference of AGCH messages on PCH

noOfBlocksForAccessGrant 0 PCH can be used only, if no paging messages have to be


send
=0 AGCH messages have higher priority than PCH ones

Number of paging groups

N = (number of CCCH blocks noOfBlocksForAccessGrant) * noOfMultiframesBetweenPaging

15 Nokia Siemens Networks


Paging Capacity
Example

Combined CCCH / SDCCH configuration BTS 3 MS

noOfBlocksForAccessGrant = 1 2 CCCH blocks for PCH


Paging_Request

3 MSs paged per paging message 3 pages per block


2 blocks per multi frame 3 * 2 = 6 pages per multiframe BTS 3 MS

Number of pages per hour 3600 s / 0.235 s * 6 = 91915 Paging_Request

Avg of 2 pages required per MS 91915 / 2 = 45957 MSs per


hour

16 Nokia Siemens Networks


SDCCH Signalling Capacity
Example with call Establishment & Location Update

Cell with 325 subscribers


1 call per subscriber once in a hour
1 location update (LU) per subscriber once in 2 hours

Duration of call assignment = 4 s 4 s / 3600 s = 1.11 mErl on SDCCH per subscriber


325 subscribers 325 * 1.11 mErl = 0.3607 Erl on SDCCH

Reservation time for LU = 5s 5 s / 7200 s = 0.69 mErl on SDCCH per subscriber


325 subscribers 0.2242 Erl on SDCCH

Total SDCCH traffic 0.3607 Erl + 0.2242 Erl = 0.5849 Erl


Blocking probability = 1% 4 SDCCHs required SDCCH combined with
CCCH can be used (MBCCHC)

17 Nokia Siemens Networks


SDCCH Signalling Capacity
Example including SMS

Same cell with 325 subscribers


Additional SMS traffic of 1 mErl per subscriber

325 subscribers 325 * 1 mErl = 0.325 Erl on SDCCH

Total SDCCH traffic 0.5849 + 0.325 Erl = 0.9099 Erl


Blocking probability = 1% 5 SDCCHs required not combined with
CCCH (MBCCH)

18 Nokia Siemens Networks


Base Station Identity Code

Base Station Identity Code BSIC = Network Colour Code NCC + Base Station Colour Code BCC

bsIdentityCode Setting of BSIC

NCC 0..7, distinguishes between PLMNs


BCC 0..7, distinguishes between clusters

BSIC + frequency channel unique identity of adjacent cell

f1 bcc = 2
bcc = 1 f2
f1
f3
f1
bcc = 3

19 Nokia Siemens Networks


Defining Frequency carrier number

Example: GSM 900


Absolute radio frequency carrier number ARFCN

890 915 935 960

1 2 3 4 123 124 1 2 3 4 123 124

duplex distance

200 kHz

uplink direction downlink direction

20 Nokia Siemens Networks


Frequency Reuse

Frequency to be used by TRX (must be unique within a BTS)

initialFrequency (FREQ) 11023 Setting of ARFCNs

GSM 800: 128 .. 251


GSM 900: 1..124 and 975..1023, 0
GSM 1800: 512..885
GSM 1900: 512..810

f2
f2 f1 f4
f1 f4 f3
f3 f5 f7
f5 f7 f6
f6 f2
f1 f4
f3
f5 f7
f6

21 Nokia Siemens Networks


Principle of Frequency Hopping

Frequency hopping techniques

hoppingMode (HOP) BB,RF,N


BB = base band hopping (1)
RF = RF hopping (2)
N = no frequency hopping at all (0)

Frequency
Call is transmitted through several frequencies to
average the interference (interference diversity)
minimise the impact of fading (frequency diversity)

F1

F2

F3

Time
22 Nokia Siemens Networks
Base Band Hopping

TRXs do not hop


Physical channels moved from one TRX to another

Hopping sequence
hoppingSequenceNumber (HSN) 0..63
0 = cyclic hopping
1..63 = pseudorandom hopping

Baseband Hopping

0 1 2 7 Timeslot

TRX 1 BC f1 HSN1 (BB hopping group 1 and RF hopping)


CH
Timeslot 0 hops over TRXs 2-4 only
TRX 2 f2
BCCH does not hop
TRX 3 f3

TRX 4 f4 HSN2 (BB hopping group 2)


Timeslots 1-7 hop over all TRXs

23 Nokia Siemens Networks


RF Hopping
Standard technique

All TRXs hop except TRX1 (provides BCCH)


Up to 63 frequencies available defined by mobile allocation list -> better hopping gain

mobileAllocationList Setting of ARFCN values


usedMobileAllocation (MAL) 0,1...2000 0 = BTS detached from any list
1..2000 = indicates list which shall be used

0 1 2 7 Timeslot
TRX 1 BC
CH f1 no hopping

TRX 2

f2,f3..fn hopping according


TRX 3 mobile allocation list
One hopping sequence
number only
TRX 4

24 Nokia Siemens Networks


RF Hopping
Freeform Hopping

Standard technique

9 hopping hopping frequencies MAI = 0..8


But 3 frequencies available for every TRX only

Freeform hopping

For every sector same


mobile allocation list
hopping sequence number
frame number (frame synchronization)

For every sector different


starting points for hopping sequence
possible by mobile allocation index offset

maioOffset (MO) 0..62

setting of MAIO

9 hopping hopping frequencies MAI = 0..8


9 frequencies available for every TRX

25 Nokia Siemens Networks


RF Hopping
Flexible MAIO Management

Freeform hopping

Not adequate for MA list with consecutive ARFCN


values
Avoids co-channel interference but not adjacent
channel interference

Flexible MAIO management

MAIO increases with constant step size from one TRX


to the next one

maioStep (MS) 1..62

maioOffset = 0, 6, 12 for sector 1, 2, 3


maioStep = 2
18 frequencies required (2 * number of hopping TRXs)

26 Nokia Siemens Networks


RF Hopping (Tight Frequency Reuse)

Freeform hopping Flexible MAIO management


MAIO Offset MAIO Offset + MAIO Step

Band allocation: Band allocation:

BCCH BCCH

MA list MA list
Non-adjacent ARFCN Consecutive ARFCN

MA
MAlist
listand
andBCCH
BCCHfrequency
frequencyplanning
planningrequired Only
required OnlyBCCH
BCCHfrequency
frequencyplanning
planningrequired
required

27 Nokia Siemens Networks


Changing Frequency Plan

Plan downloaded to BSC/BTSs via MML or GUI


File-based plan provisioning
Immediate Plan activation method

BSIC / TSC
Frequencies
Frequency hopping setting
Intelligent underlay overlay TRX settings

28 Nokia Siemens Networks


Idle Mode Operation

29 Nokia Siemens Networks


IIdle Mode Operation

When?

When the MS is switched ON


When there is no dedicated connection MS switched ON

Why?
To camp on the best suitable cell Search RF channels
to find BCCH carrier
Why to camp on a specific cell?
For MS to receive system info from the NW on DL
For MS to be able to initiate a call whenever needed
For the NW to be able to locate the MS when there is a Check that the PLMN
MT call/SMS & cell is allowed

Idle Mode Tasks MS camps on


the best
suitable cell
PLMN selection
Cell selection & re-selection
Location updates See slide 10 for detail

30 Nokia Siemens Networks


IDs and ID Codes

Parameter Value

LAI (locationAreaId)
MCC (Mobile Country Code) 0 999
MNC (Mobile Network Code) 0 99,
0 999 (optional 3-digit MNC)
LAC (Location Area Code) 1 65533

BSIC (bsIdentityCode)
NCC (Network Colour Code) 07
BCC (BTS Colour Code) 07

CI (cell-ID 0 65535

TSC (trainingSequenceCode) 07

CGI (Cell Global Identity) MCC + MNC + LAC + CI

31 Nokia Siemens Networks


States and State Transition for Cell Selection

go here when no SIM in MS SIM inserted in MS


Any cell 1
selection

no suitable no suitable
cell found
cell found cell found

Choose cell suitable cell found Camped trigger Any


on cell re-
any cell cell selection
return
to idle leave re-selected
mode idle cell found
mode on selected
Connected mode PLMN
(emergency call
only)

2
(adopted from TS 43.022 V5.1
32 Nokia Siemens Networks
States and State Transition for Cell Selection
go here whenever a
new PLMN is selected

2 no BA list stored BA list stored


1 for PLMN
for PLMN

Normal no suitable cell found Stored list


cell selection cell selection

no suitable
cell found suitable cell found suitable cell found

Choose cell suitable cell found trigger


Camped Normal
normally cell re-selection
return Suitable cell
to idle re-selected
leave
mode
idle no suitable
mode cell found
IMSI unknown
Connected
Illegal MS
mode
PLMN not allowed
no 2
suitable
cell
found
(adopted from TS 43.022 V5.1.0 chap. 6
33 Nokia Siemens Networks
Normal Cell Selection
Search all the RF channels, take samples during
3-5 s and calculate averages. And put them in
ascending order with respect to signal level.
Then tune to the strongest RF channel.

Search for the frequency correction burst in that Tune to the next highest
carrier in order to verify if it is a BCCH carrier RF channel which is not
tried before

No
Is it a BCCH
carrier?

Yes

Try to synchronize to the carrier and read


the BCCH data

No
Is it a correct
PLMN ?

Yes

Yes
Is the cell barred?

No
No
Is C1>0

Yes
Camp on the cell

34 Nokia Siemens Networks


Pathloss Criterion C1 for Cell Selection
and Reselection
0..63 0..31
C1 = A max(B,0)
= RLA_C RXLEV_ACCESS_MIN max(MS_TXPWR_MAX_CCH P , 0)

RLA_C = avg received RxLev on BCCH


P = MS max output power

I am
outside

I am inside, but 0)
,
have not enough x(B
power ma

35 Nokia Siemens Networks


Cell Selection with C1
In case the neighbouring cells belong to different Location Area, a hysteresis is applied
with C1 criteria
minimizing ping-pong cell reselections
cellReselectHysteresis (HYS)(BTS) (014 dB)

Cell1 Cell2
LAC1 LAC2

C1 ( Cell1) C1 (Cell2) A= 4 dB
B= 6 dB
C= 8 dB
A B C

36 Nokia Siemens Networks


Pathloss Criterion C2
0 .. 126 dB 0, 10, 20, 30, 40, 20 .. 640 s
step size: 2 dB 50, 60, dB step size: 20 s

C1 + CELL_RESELECT_OFFSET (TEMPORARY OFFSET * H(PENALTY_TIME - T))


C2 = for PENALTY_TIME 640 s
< C1 if temporary offset big for PENALTY_TIME = 640 s

C2
no TEMPORARY OFFSET

serving cell: C1
C2:
new candidate
CELL_RESELECT_OFFSET
List of 6 = former serving
strongest cell
T
carriers:
C2: C2
C2:
C2: C1
C2:
C2:
C2: CELL_RESELECT_OFFSET
new candidate
= formerly non-
serving cell TEMPORARY OFFSET
T
PENALTY_TIME
37 Nokia Siemens Networks
Cell Reselection Based on Pathloss
Criterion C2

C2
cell 1 cell reselection &
cell 3
location update

cell
reselection cell 2

CELL_RESELECT_
HYSTERESIS (HYS)

5 seconds 5 seconds time

LAC = A LAC = B

38 Nokia Siemens Networks


Cell Reselection Based on Pathloss
Criterion C2
=30 Cell "A" (Serving Cell)
=25 Cell "B"
Road
Macro 900 "C" C1 =5 Cell "C"
=50 Cell "D"

C2 = C1 + cellReselectOffset -
Micro 900 "D" temporaryOffset*H(penaltyTime-T)
Macro 1800 "B"
=30 + 0 (H(x)=0, serving cell) Cell "A"
=25 + 20 - 30*H(20 - T) Cell "B"
C2 =5 + 0 - 0*H(20 - T) Cell "C"
=50 + 0 - 30*H(40 - T) Cell "D"

Cell "A" Cell "B" Cell "C" Cell "D"

cellReselectOffset 0 dB 20 dB 0 dB 0 dB

temporaryOffset 0 dB 30 dB 0 dB 30 dB
Macro 900 "A" Parameters
penaltyTime 20 s 20 s 20 s 40 s

Time T: (0 - 19 s) Time T: (20 - 39 s) Time T: (> 40 s)


C2 =30 Cell "A" C2 =30 Cell "A" C2 =30 Cell "A"
C2 =15 Cell "B" C2 =45 Cell "B" C2 =45 Cell "B"
C2 =5 Cell "C" C2 =5 Cell "C" C2 =5 Cell "C"
C2 =20 Cell "D" C2 =20 Cell "D" C2 =50 Cell "D"
39 Nokia Siemens Networks
Cell Reselection Events
Authentication Failure
Pathloss Criterion C1 notification by upper layers
C1 0 for a period of 5 s

Cell has been barred


Pathloss Criterion C2 CELL_BAR_ACCESS & CELL_BAR_QUALIFY
neighbours C2 value >
current cells C2 value (same LA)
neighbours C2 value > RACH Failure
current cells C2 value + HYS MAX RETRANS + 1 times
(new LA)
for a period of 5 s.
Downlink Signalling Failure
DSC 0

When shall I
select a new cell?

40 Nokia Siemens Networks


Location Update Procedure
MS BSS MSC VLR HLR

LOCATION UPDATE REQUEST

REQUEST SUBSCRIBER ID

SEND SUBSCRIBER ID

REQUEST SUBSCRIBER INFO

SEND SUBSCRIBER INFO

AUTHENTICATION

AUTHENTICATION RESPONSE

ALL OK - HLR UPDATE

41 Nokia Siemens Networks


Trade-off between Location Update and
Paging Traffic
signalling
traffic

function of user density,


function of cell size, call arrival rate ...
user mobility

Paging
LocUp

optimum number # of cells in Loc. area


of cells in Loc. area

42 Nokia Siemens Networks


Location Updates

MS location & status flag => MSC / VLR


Mobile Station switched ON mode
IMSI Attach / Detach
Same Location Area => No Location Update
Different Location Area => Location Update
Change of the Location Area
Location Area under the same MSC / VLR
Location Area under another MSC / VLR => HLR will be updated
Service is rejected (MS unknown in VLR)
Time-Periodic LU (MS -> MSC/VLR)

MO Abbreviated Range And Description Default BSC -


Class Name Step value MML
Name
BTS allowIMSIAtt Yes/No Defines whether IMSI attach/detach is used in the cell. Yes ATT
achDetach
BTS timerPeriodic 0...25.5 h, Defines the interval between periodic MS location 0.5 h PER
UpdateMs step 0.1 h updates.
The value 0 means that the periodic location update is
not used.

43 Nokia Siemens Networks


IDLE MODE OPERATION
Idle Mode Controls
Parameter Value
rxLevAccessMin -110 ... -47 (dBm)
msTxPwrMaxCCH 13 ... 43 (dBm)
notAllowedAccessClasses 0 ... 9, 11 ... 15
Access
emergencyCallRestricted Yes/No Parameters
msMaxDistanceInCallSetup 0 ... 255
radiusExtension 0 ... 67 (Km)

cellBarred Yes/No
Mobility
plmn-permitted 0 ... 7
Parameters
cellReselectHysteresis 0 ... 14 (dB)

cellReselectOffset (REO) 0 ... 126 (dB)

cell reselection parameter index (PI) (N/Y)

44 Nokia Siemens Networks


IDLE MODE OPERATION
Idle Mode Controls definitions
RxLevAccessmin :
With this parameter you define the minimum power level an MS has to receive before it is allowed to access the cell.
MsTxPwrMaxCCH :
With this parameter you define the maximum transmission power an MS may use when accessing a CCH in the cell.
notAllowedAccessClasses
With this parameter you define the MS access classes that are not allowed to access a cell.
Emergency Call Restricted
With this parameter you define if an emergency call in the cell is allowed to all MSs or only to the MSs which belong to
one of the classes between 11 to 15. Value Y means the latter case.
MsMaxDistancein CallSetup
With this parameter you define the maximum distance between the BTS and the MS in call setup. The maximum distance
is expressed as an access delay. Within the range of 0...62, one step correlates to a distance of 550 meters. If the access
delay of the channel request message exceeds the given maximum, the call attempt is rejected. When the parameter is
given a value from 63 to 255, call attempts are never rejected
radiusExtention
With this parameter you define the radius extension of an extended cell

45 Nokia Siemens Networks


Radio Resource management

46 Nokia Siemens Networks


Signalling (Mobile Originating Call)
MS Channel request (RACH) NETWORK

Immediate assignment (AGCH) Immediate assignment

Service request (SDCCH)

Service request
Authentication request (SDCCH)
Idle Authentication response (SDCCH) Authentication
parameter
Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Setup (SDCCH)

Call proceeding (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Alert (FACCH)

Call confirmation
Dedicated Connect (FACCH)
parameter
Connect acknowledged (FACCH) Call accepted

47 Nokia Siemens Networks


Signalling (Mobile Terminating Call)
MS Page request (PCH) NETWORK

Channel request (RACH) Immediate assignment


Immediate assignment (AGCH)

Page response (SDCCH)

Service request
Idle Authentication request (SDCCH)
parameter Authentication response (SDCCH) Authentication

Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Setup (SDCCH)

Call confirmation (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Alert (FACCH)

Call confirmation
Dedicated Connect (FACCH)
parameter
Connect acknowledged (FACCH) Call accepted

48 Nokia Siemens Networks


Signalling (Call Release)

Network initiated

MS Disconnect NETWORK

Release Call clearing


Release complete

Channel release

Release

MS initiated

MS Disconnect NETWORK

Release Call clearing


Release complete

Channel release

Release

49 Nokia Siemens Networks


Standard TCH Allocation (General Criteria)

MS capabilities

Channel rate : full, half, dual, multi rate


Speech codecs : normal FR, normal HR, EFR, AMR FR, AMR HR, doubleHR(OSC)

MSC demands

A interface circuit allocated for call

BTS demands

Speech codec capabilities


TCH configuration
Current resources
Homogeneous use of TRXs and radio time slots
Large free groups of radio time slots for high loaded HSCSD BTS

50 Nokia Siemens Networks


TCH Allocation

How can be optimized?

51 Nokia Siemens Networks


Channel allocation ( For each TS)
Each
EachTRX
TRXhave
haveitsitsown
ownQuality
Qualityboth
bothDL
DLand
andUL
ULand
andTRX
TRXwith
withbad
badquality
quality
(UL and DL) will result bad KPI on respective TRX
(UL and DL) will result bad KPI on respective TRX

Placing each Time Slot (BCCH, SDCCH, TCH and PDTCH) properly will result
good KPI (SDSR, DCR, HOSR TBF Completion rate)

Shitting
ShittingSDCCH,
SDCCH,BCCH
BCCHcan
canimprove
improveSDSR
SDSRand
andDCR
DCR
52 Nokia Siemens Networks
Standard TCH Allocation
(Interference Bands)
Measurement of uplink receive level on idle channels = uplink interference

Averaging over interferenceAveragingProcessAverPeriod (AP) = 1..32 SACCH


periods

Classification into interference bands based on interferenceAveragingProcess


(BO1..BO4) = -110..-47 dBm

BSC tries to allocate TCH from best interference band (can be requested by MSC)
If not available,
BSC tries to take TCH from next band

BO5 47 (fixed)
rxLevUL = -75 dBm
BO4 -90
BO3 -95
BO2 -100
BO1 -105
BO0 110 (fixed)
0 1 2 3 4 5 6 7
53 Nokia Siemens Networks
Prioritized TCH Allocation (TRP)
Whole band , 50 channels 1 ch=200kHz

Case1 BCCH, 30 channels TCH, 20 channels

Case2 All 50 channels for BCCH and TCH

Priority for TCH from BCCH TRX

BCCH transmitted permanently -> no additional interference in network


Planned to be least interfered channels

Priority for TCH from other TRX

BCCH TRX does not hop in case of RF hopping -> hopping gain only for other TRX

Parameter

trxPriorityInTCHAlloc (TRP) 0 = no priority


1 = priority for BCCH TRX
2 = priority for other TRX
3 = priority for BCCH TRX for non-AMR users,
priority for other TRX for AMR users

54 Nokia Siemens Networks


RX level based TCH Allocation (RXP)

Enables to differentiate Rx level requirement for:


MS camping to the network /RxLev Access Min
MS accessing to TCH /RX level based TCH access

RX level based TCH allocation method


RX Level measured by the MS is used to determine whether the BTS is
acceptable for TCH allocation
TCH allocation for emergency calls is not restricted due to low RX level

Provides better drop call meters and better performance of MSs


MSs having too low Rx levels are not allowed to camp the network
By separating camping and TCH access thresholds the operator will be able to
provide the maximum camping footprint

Note! RG20 feature Energy optimized TCH allocation

55 Nokia Siemens Networks


RX level based TCH Allocation (RXTA)

Allows to define minimum C/N ratios separately for each call type (AMR FR, AMR HR, EFR/FR, HR
and 14.4 data)
Parameter values RX level based TCH access:

0: RX level based TCH access is not used (C/N definitions not in use)
1: RX level based TCH access is used in call setup
2: RX level based TCH access is used in call setup and in handovers

Soft blocking C/N FR: 063dB/ def: 12dB


Soft blocking C/N FR: 063dB/ def: 12dB
Soft Blocking C/N HR: 063dB/ def: 14dB
Soft Blocking C/N HR: 063dB/ def: 14dB
Soft blocking C/N AMR FR: 063dB/ def: 7dB
Soft blocking C/N AMR FR: 063dB/ def: 7dB
Soft blocking C/N AMR HR: 063dB/ def: 12dB
Soft blocking C/N AMR HR: 063dB/ def: 12dB
Downlink RX Level Soft blocking C/N 14.4 : 063dB/ def: 14dB
Soft blocking C/N 14.4 : 063dB/ def: 14dB
-> TCH Access

56 Nokia Siemens Networks


Queuing (Parameters)

Priorities

No TCH available for call set up / handover -> request put into queue
Different kinds of requests can have different priorities

queuePriorityUsed (QPU) Y/N enables use of priorities

queueingPriorityCall (QPC) 1..14 priority for call set up request


queuePriorityNonUrgentHo (QPN) 1..14 priority for non urgent handover (power
budget,
umbrella, slow moving MS, traffic reason)
request
queueingPriorityHandover (QPH) 1..14 priority for urgent handover (all other) request

Queue length and time

maxQueueLength (MQL) 0..100% percentage of number of TCHs handled by


BTS timeLimitCall (TLC) 0..15 s time a call set up request is kept in the queue
0 = queuing is disabled
timeLimitHandover (TLH) 0..10 s time a handover request is kept in the queue
0 = queuing is disabled

57 Nokia Siemens Networks


Queuing (Entering the Queue)

Conditions

Timers set to values > 0


User of priorities enabled
Queue not full with requests of equal or higher priority than the current one

Queuing of call set up requests

Reservation of SDCCH resources


-> SDCCH easily overbooked
-> blocking of services like SMS or location update

58 Nokia Siemens Networks


Queuing (Handover)

Handover request queued by target BTS

Handover timers hoPeriodPBGT and hoPeriodUmbrella stopped


Measurement processing and averaging continues as usual

Intra BSC handover Inter BSC handover

Queuing possibility checked for all Target BTS given by MSC by


possible target cells Order handover request message
according conventional ranking

59 Nokia Siemens Networks


Queuing (Leaving the Queue)

With TCH allocation

Release of busy TCH


Check of queue from top to bottom for best matching request
If TCH allocation possible, request removed from queue

Without TCH allocation

Queuing timer expires


Request of higher priority enters full queue

60 Nokia Siemens Networks


Queuing (Together with Directed Retry)

Directed Retry Timer maxTimeLimitDirectedRetry expires

call cleared, even if still in queue

Queuing timer expires

target cell evaluation continues, if directed retry timer is still running

61 Nokia Siemens Networks


Dropped Call Control
Radio Link Timeout
BTS does not receive measurement report on
SACCH for running call for the first time

Counter initialised with value of radioLinkTimeout


(4,8,..64 SACCH periods)

SACCH not received again SACCH received again

Counter decremented by 1 Counter incremented by 2


(but not beyond initial value)

Example: short tunnel


Counter has value 0

Call release due to radio link


time out

62 Nokia Siemens Networks


Dropped Call Control
Radio Link Timeout

RLT is based on SACCH deletion but SACCH is though not using a dynamic
codec like voice in AMR, which means:
Using the EFR RLT value an AMR customer can have the call dropped
because RLT = 0 when still the FER is good
RLT is not anymore reliable with the same value in AMR than in EFR
Due to the fact that the FER performance is different when comparing AMR
calls to EFR calls, the Radio Link Timeout need to be defined separately for
AMR
The Radio Link Timeout parameters for AMR are ARLT and AHRLT. The
principle of these is the same than in the RLT but it is used only for the AMR
capable mobile stations. ARLT & AHRLT are not supported in Talk Family
base stations.

63 Nokia Siemens Networks


Dropped Call Control
Call Reestablishment
Radio link timeout occurs
callReestablishmentAllowed (RE) set to Y

Receive level of BCCH measured for serving and adjacent cell


Averaged over 5 s

Strongest cell considered Example: long tunnel

BCCH decoded
C1 cell selection criterion fulfilled
Cell not barred
Cell belongs to selected PLMN

Attempt to re-establish call

Successful within 20s * Not successful within 20s *


call released
call re-established

64 Nokia Siemens Networks * MAX WAIT TIME OF RE-ESTAB REQ is a modifiable timer in MSC
NPT parameter related (Idle Parameter)

65 Nokia Siemens Networks


Measurement Processing

66 Nokia Siemens Networks


Introduction

Measurement Measurements
Report

Standard Enhanced Idle mode Dedicated mode

Rx level Standard + following: MS listens MS sends DL


Rx quality DL frame erasure rate to BCCH measurement report on
Level & BSIC of up DTX bit error probability SACCH
to 6 neighbours Real time difference serving BTS performs UL
3G cells adjacent cell measurements
3G cells
Control over reporting priority

67 Nokia Siemens Networks


Introduction

Measurement Measurements
Report

Standard Enhanced Idle mode Dedicated mode

Rx level Standard + following: MS listens MS sends DL


Rx quality DL frame erasure rate to BCCH measurement report on
Level & BSIC of up DTX bit error probability SACCH
to 6 neighbours Real time difference serving BTS performs UL
3G cells adjacent cell measurements
3G cells
Control over reporting priority

68 Nokia Siemens Networks


Coding of Rx Level

P (dBm) P (dBm) LEV


No offset 10 dB offset

-110 -100 0
-109 -99 1
-108 -98 2
. . .
. . .
. . .
-49 -39 61
-48 -38 62
-47 -37 63

Activation of offset to code high levels


scaleOrd (SCO)(SEG)(0,1,2)(0)

0 = no offset used
1 = offset used in general
2 = MS decides automatically about offset

69 Nokia Siemens Networks


Coding of Rx Quality
BER (%) BER (%) QUAL

RANGE MEAN
< 0.2 0.14 0
0.2-0.4 0.28 1
0.4-0.8 0.57 2
0.8-1.6 1.13 3
1.6-3.2 2.26 4
3.2-6.4 4.53 5
6.4-12.8 9.05 6
> 12.8 18.1 7

Average window = 4
Quality samples 0,0,7,0
WRONG!!: (0+0+7+0)/4 = 1.75 (wrong!!)
RIGHT: (0.14+0.14.+18.1+0.14)/4 = 4.63 (right!!) => corresponds to Qual5

70 Nokia Siemens Networks


Mapping of BEP to RX Quality

BEP BER (%) QUAL

VALUE RANGE
22..31 < 0.2 0
19..21 0.2-0.4 1
16..18 0.4-0.8 2
13..15 0.8-1.6 3
10..12 1.6-3.2 4
7..9 3.2-6.3 5
4..6 6.3-12.6 6
0..3 > 12.6 7

71 Nokia Siemens Networks


Mapping of FER to RX Quality

X axis: frame erasure rate (< 1%, 1-5 %, 5-10 %, 10-15 %, > 15 %)
Y axis: RX quality (0..7)
Z axis: Percentage of measurements for each FER category

Frame Erasure Rate for Handover / Power Control Decision


fepInPcHoUse (FPHO)(BSC)(Y,N)(N)
72 Nokia Siemens Networks
MS Measurement Execution
Idle Mode

Decoding of BCCH
for serving (camped) cell every 30 s
for adjacent cells every 5 min
Pre-synchronization and decoding of BSIC
for adjacent cells every 30 s
Adjacent cell list
Updating every 60 s
BCCH decoding of new cell in 30 s

73 Nokia Siemens Networks


MS Measurement Execution
Dedicated Mode I

SACCH PERIOD = 480 ms

26 FRAME MULTIFRAME = 120 ms

TDMA FRAMES
TDMA FRAMES
4.615 ms TCH SACCH IDLE

RX TX MEAS RX TX MEAS RX TX MEAS


BSIC decoding for at least one adjacent cell
Pre-synchronization on SCH

Measures frequencies of adjacent cells

Measures RX level and quality for serving cell


Detects whether DTX is used

74 Nokia Siemens Networks


Power Control

75 Nokia Siemens Networks


Power Control Motivation

Reduced
interference on
DL/UL

Longer service time of battery


Realization of power class
Supported by default on UL

Activation of DL power control

powerCtrlEnabled (PENA) Y,N

Power control independent

for DL and UL
for each call

76 Nokia Siemens Networks


Power Control Parameter
Output Power Limits

Maximum MS output power

msTxPwrMaxGSM (PMAX1) 5..39 dBm GSM 900 TCH


Power msTxPwrMaxGSM1x00 0..36/32,33 dBm GSM 1800/1900
class TCH (PMAX2)
dependent msTxPwrMaxCCH (TXP1) 5..39 dBm GSM 900 CCH
range msTxPwrMaxCCH1x00 0..30 dBm GSM 1800 CCH
(TXP2) 0..32 dBm GSM 1900 CCH
Power Values
Minimum MS output power

minMSTxPower (PMIN) 5..39 dBm GSM 900


0..36 dBm GSM 1800
0..32 dBm GSM 1900

Maximum BTS output power (by minimum attenuation)

Attenuations bsTxPwrMax (PMAX1) 0..30 dB GSM 900


bsTxPwrMax1x00 (PMAX2) 0..30 dB GSM 1800/1900
30 dB
Range Minimum MS output power (by maximum attenuation)

bsTxPowerMin 0..30 dB

77 Nokia Siemens Networks


Power Control Parameters
Power Change Step Sizes

Desired power level can be achieved in 1 or 2 commands

Yes No

Fixed step size Variable step size

Fixed increment step size

pcIncrStepSize (INC) 2,4,6 dB

Fixed decrement step size

pcRedStepSize (RED) 2,4,6 dB

78 Nokia Siemens Networks


Power Control Strategy
Measurement Averaging

POWER CONTROL
UPLINK
UL Quality <Av_RXQUAL_UL>

UL Level <Av_RXLEV_UL> THRESHOLD


COMPARISON
DL Quality <Av_RXQUAL_DL>

DL Level <Av_RXLEV_DL>
POWER CONTROL
DOWNLINK

Power control interval

powerCtrlInterval (INT) 0..31 s

79 Nokia Siemens Networks


Power Control Strategy
Triggering

Nx samples
Less than Px samples exceed threshold
No power change triggered
Actual average samples

threshold

Nx samples
Px samples are equal to or exceed threshold
Signal level thresholds
Power change triggered
pcUpperThresholdLevelDL/UL (UDR/UUR) -110..-47 dBm
pcLowerThresholdLevelDL/UL (LDR/LUR) -110..-47 dBm

Signal quality thresholds Power change step size estimation

pcUpperThresholdQualDL/UL (UDR/UUR) 0..7


pcLowerThresholdQualDL/UL (LDR/LUR) 0..7

Number of average samples (for each threshold)

Nx 1..32
Px 1..32

80 Nokia Siemens Networks


Power Control Strategy
Scenarios

Exceeded threshold Action Reason

pcUpperThresholdLevelDL BTS power decrease Signal level


pcLowerThresholdLevelDL BTS power increase Signal level
pcUpperThresholdLevelUL MS power decrease Signal level
pcLowerThresholdLevelUL MS power increase Signal level

pcUpperThresholdQualDL BTS power decrease Signal quality


pcLowerThresholdQualDL BTS power increase Signal quality
pcUpperThresholdQualUL MS power decrease Signal quality
pcLowerThresholdQualUL MS power increase Signal quality

81 Nokia Siemens Networks


AMR Power Control

AMR FR

AMR HR

Details in chapter on AMR

82 Nokia Siemens Networks


POC

Lower Upper
-110 dB Level(-90) Level(-80)
-47 dB

Qual 0 Signal level

Ping Decrease due to good quality


pong
Upper effect
Quality(1)
Increase Decrease
No action
due to bad Due to good
Lower Signal level Signal level
Quality(3)
Increase due to Bad quality

Qual 7
Quality
83 Nokia Siemens Networks
POC

Lower Upper
-110 dB Level Level
-47 dB

Qual 0 Signal level

6dB Decrease due to quality


Upper
Quality
Increase No action Decrease
due to level Due to level
Lower
Quality
Increase due to quality

Qual 7
Quality
84 Nokia Siemens Networks
POC and HOC (UL)

UL Level HO
-110 dB Threshold
-47 dB

Qual 0 Signal level

When UL quality HO is triggered


No action Should MS be sent full power?
What about UL level
UL Quality HO
Threshold

Qual 7
Quality
85 Nokia Siemens Networks
Power Control Summary

-110 dBm Lower Level Upper Level -47 dBm

Qual 0
Power increase Power decrease Power decrease
due to level due to quality due to level
6 dB
or quality

Upper Quality

Power increase Power decrease


due to level No action due to level

Lower Quality
Power increase Power increase Power increase
due to level due to quality due to quality
or quality

Qual 7

86 Nokia Siemens Networks


Power Increase Due to Signal Level
For MS & BTS

Actual receive level RXLEV_DL/UL

pcLowerThresholdsLevelDL/UL

Power control triggered


UL: Power increase of MS
DL: Power increase of BTS

RXLEV_DL/UL > pcLowerThresholdLevelDL/UL - 2 powerIncrStepSize

Yes No

Fixed step size Variable step size

PWR_INCR_STEP = powerIncrStepSize PWR_INCR_STEP = pcLowerThresholdLevelDL/UL


RXLEV_UL/DL

87 Nokia Siemens Networks


Power Decrease Due to Signal Level
For BTS

pcUpperThresholdsLevelDL

Actual received level RXLEV_DL

Power control triggered


Power decrease

RXLEV_DL < pcUpperThresholdLevelDL + 2 powerDecrStepSize OR

variableDLStepUse (VDLS) = No

Yes No

Fixed step size Variable step size

PWR_DECR_STEP = powerDecrStepSize PWR_DECR_STEP = Min (RXLEV_DL


pcUpperThresholdLevelDL, 10)

88 Nokia Siemens Networks


Power Decrease Due to Signal Level
For MS

pcUpperThresholdsLevelUL

Actual received level RXLEV_UL

Power control triggered


Power decrease

RXLEV_UL < pcUpperThresholdLevelUL + 2 powerDecrStepSize

Yes No

Fixed step size Variable step size

PWR_DECR_STEP = powerDecrStepSize PWR_DECR_STEP = RXLEV_UL


pcUpperThresholdLevelUL

89 Nokia Siemens Networks


Power Increase Due to Signal Quality
For MS & BTS

Actual receive quality RXQUAL_DL/UL

pcLowerThresholdsQualDL/UL

Power control triggered


UL: Power increase of MS
DL: Power increase of BTS

Variable step size based on actual quality

PWR_INCR_STEP = (1 + Max (0,QUAL)) * powerIncrStepSize

QUAL = RXQUAL_DL/UL pcLowerThresholdQualDL/UL

Take largest step size


Step size based on actual level

Take algorithm for power increase due to signal level

90 Nokia Siemens Networks


Power Decrease Due to Signal Quality
For MS & BTS with No Power Optimization

pcUpperThresholdsQualDL/UL

Actual received quality RXQUAL_DL/UL

Power control triggered

Actual RXLEV_DL/UL pcLowerThresholdLevelDL/UL < 6 dB

Yes No

No power decrease Power decrease

Avoid ping pong effect Take algorithm for power decrease due to signal level
(different for MS & BTS power decrease)

91 Nokia Siemens Networks


NPT parameter related (POC Parameter)

Should be greater
than HOC
92 Nokia Siemens Networks
Handover Control

93 Nokia Siemens Networks


Handover Types

Germany Czech Republic

Intra PLMN
Simple Cell ID required Inter PLMN
LAC + CI Global Cell ID required
MCC + MNC + LAC + CI

Inter MSC
Intra cell
Only other carrier / timeslot

Inter cell
Intra BSC

Inter BSC
Intra MSC

94 Nokia Siemens Networks


Multi Layer Network Types
Super reuse
Normal frequency
frequency

Macro cells

Micro cells
Intelligent Underlay Overlay
Different frequencies for high / low power TRx

GSM 900 cell


GSM 1800 cell

Coverage Layer: Gives access to the network


Capacity Layer: Provides additional capacity and allows traffic
distribution
95 Nokia Siemens Networks
Handover Strategy
Triggering
Nx samples
Less than Px samples >= threshold
No handover triggered
Actual average samples

threshold

Signal interference thresholds Nx samples


hoThresholdsInterferenceDL/UL (IDR/IUR) -110..-47 dBm Px samples are >= threshold
Signal quality thresholds
handover triggered
hoThresholdsQualDL/UL (QDR/QUR) 0..7

Signal level thresholds


hoThresholdLevelDL/UL (LDR/LUR) -110..-47 dBm
hoThresholdRapidLevelUL (RPD) -110..-47 dBm
Target cell selection
MS speed thresholds
upper/lowerSpeedLimit (USL/LSL) 0..255 (unit = 2km/h)

Number of average samples


Trigger Point When the set
Nx 1..32 threshold has been met or
Px 1..32 exceeded Px times of Nx times

96 Nokia Siemens Networks


Handover Strategy
(Priorities)
More than one handover criterion fulfilled -> process of higher priority performed
Handover and power control criteria fulfilled -> handover performed

1) Interference (uplink or downlink)


2) Intra-segment inter-band because of downlink level (from higher to lower frequency band)
3) Uplink quality
4) Downlink quality
5) AMR unpacking (uplink level and also uplink unpacking quality triggers)
6) Uplink level
7) AMR unpacking (downlink level and also downlink unpacking quality triggers)
8) Downlink level
9) Coverage based inter-system handover to WCDMA RAN
10) IMSI-based inter-system handover to WCDMA RAN
11) IMSI-based handover
12) DTM-based handover to WCDMA RAN
13) Inter-system handover to WCDMA RAN Exercise:
14) MS-BS distance (maximum or minimum)
15)
16)
Turn-around-corner MS
Rapid field drop
Whu UL has many times
17) Slow/fast-moving MS higher priority than DL?
18) Umbrella
19) Power budget
20) DTM-based handover to a GSM DTM cell
21) BSC-initiated TRHO
22) IUO
23) Intra-segment HO based on load
24) AMR packing because of good uplink and downlink quality
25) AMR unpacking because of bad uplink or downlink quality
26) PC because of lower quality thresholds (uplink and downlink)
27) PC because of lower level thresholds (uplink and downlink)
28) PC because of upper quality thresholds (uplink and downlink)
29) PC because of upper level thresholds (uplink and downlink)

97 Nokia Siemens Networks


HO due to UL/DL Quality
IF IF
AV_RXQUAL_DL_HO >= AV_RXQUAL_UL_HO >=
HoThresholdsQualDL HoThresholdsQualUL
THEN THEN
Handover cause Downlink quality Handover cause Uplink quality

Target cells is listed based on below criteria


1. AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0,Pa)
2.AND IF
EnableHoMarginLevQual(n)= Yes
Listing set of
THEN target cell
AV_RXLEV_NCELL(n) > AV_RXLEV_DL_HO + (BsTxPwrMax - BS_TXPWR)
+ HoMarginQual(n)
3. ELSE
PBGT(n) > HoMarginPBGT(n) (2)

Order of preference of target cells


PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n) Priority of
HoLoadFactor value is taken into account when BTSLoadThreshold is target cell
exceeded.

Interval between handovers and handover attempts Timer of


source cell
98 Nokia Siemens Networks
HO due to UL/DL LEVEL
IF IF
AV_RXLEV_DL_HO<= AV_RXLEV_UL_HO<=
HoThresholdsLevDL HoThresholdsLevUL
THEN THEN
Handover cause Downlink level Handover cause Uplink level

Target cells is listed based on below criteria


1. AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0,Pa)
2.AND IF
EnableHoMarginLevQual(n)= Yes
Listing set of
THEN target cell
AV_RXLEV_NCELL(n) > AV_RXLEV_DL_HO + (BsTxPwrMax - BS_TXPWR)
+ HoMarginLev(n)
3. ELSE
PBGT(n) > HoMarginPBGT(n) (2)

Order of preference of target cells


PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n) Priority of
HoLoadFactor value is taken into account when BTSLoadThreshold is target cell
exceeded.

GUARD_TIME = 2 * HoPeriodPBGT (Ho Due PBGT) Timer of


GUARD_TIME = 2 * HoPeriodUmbrella (HO Due to Umbrella)
source cell
99 Nokia Siemens Networks
HO due to Fast/Slow moving MS
MS speed in relation to cell size: Measured MS speed:
IF IF
MsSpeedDetectionState= 0 AV_MS_SPEED <= LowerSpeedLimit
AdjCellLayer(n) = Lower THEN
FastMovingThreshold(n)> 0 MS is slow-moving
IF
AV_MS_SPEED >= UpperSpeedLimit
AV_RXLEV_NCELL(n) >
RxLevMinCell(n) + MAX (0, Pa) THEN
THEN MS is fast-moving
RXLEV_CNT(n) = RXLEV_CNT(n) + 2
ELSE
IF
RXLEV_CNT(n) = RXLEV_CNT(n) - 1
MsSpeedDetectionState= 0
THEN
IF Handover Cause Fast/Slow-moving MS
RXLEV_CNT(n) >= ELSE
FastMovingThreshold(n) Scale averaging parameters
THEN
Handover cause Slow-moving MS

Target cell evaluation:


AdjCellLayer(n) = Lower/Upper
AND
AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
Handover to low layer cell is not possible if maximum power capability of MS exceeds
gsm/dcsMicrocellThreshold
100 Nokia Siemens Networks
HO due to Fast/Slow moving MS (Count)
Target cell evaluation:
AdjCellLayer(n) = Lower/Upper
AND
AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
Handover to low layer cell is not possible if maximum power capability of MS exceeds
gsm/dcsMicrocellThreshold

Order of preference of target cells


PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded

Interval between handovers and handover attempts

101 Nokia Siemens Networks


HO due to Umbrella
IF
EnableUmbrellaHO= Yes
HoPeriodUmbrella - interval between the umbrella
handover threshold comparisons

Umbrella handover and target cell evaluation:


AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
AND
( [(P >= macro_thr) AND (pwr(n) >= macro_thr)]
OR
[(P <= micro_thr) AND (pwr(n) <= micro_thr)]
OR
[(P < macro_thr) AND (pwr(n) < macro_thr) AND
(P > micro_thr) AND (pwr(n) > micro_thr)] )

Order of preference of target cells


PRIORITY (n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded.

Interval between handovers and handover attempts

102 Nokia Siemens Networks


Umbrella +FMT Handover
Example

hoLevelUmbrella = -85 dBm PTCH (msTxPwrMax(n)) = 30 dBm -> micro cell


gsmMacrocellThreshold = 33 dBm
PMAX = 30 dBm -> handover to micro cell only
dcsMacrocellThreshold = 33 dBm
hoThresholdLevelDL = -95 dBm

900 Macro

After FMT>1 (example)

A
1800 Micro
Threshold umbrella
handover 85 dBm

Threshold RX level
handover 95 dBm

Umbrella handover RX
B Umbrella handover RXlevel
levelhandover
handover
toto1800
1800cell back
back to 900cell
cell to 900 cell
103 Nokia Siemens Networks
HO due to PBGT
IF
EnablePowerBudgetHO= Yes
HoPeriodPBGT - interval between the power budget
threshold comparisons

Power budget and target cell evaluation:


AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)
AND
PBGT(n) > HoMarginPBGT(n) (2)
PBGT(n) = (B - AV_RXLEV_DL_HO -
(BsTxPwrMax - BS_TXPWR)) - (A - AV_RXLEV_NCELL(n))

Order of preference of target cells


PRIORITY (n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded.

Interval between handovers and handover attempts

104 Nokia Siemens Networks


Power Budget Handover
Exercise
BTS A BTS B
Serving cell: A
HO candidate target cells: B, C, D
Serving cell A:
All cells have the following parameter set: AV_RXLEV_DL_HO= -92 dBm
rxLevMinCell= -99 dBm BTS_TX_PWR= 42 dBm
msTxPwrMax= 33 dBm BTS C
btsTxPwrMax= 42 dBm
hoMarginPBGT= 6 dB
BSC
BTS D

Target cell hoPriorityLevel: AV_RXLEV_NCELL (B)= -80 dBm


B priority: 4
AV_RXLEV_NCELL (C)= -83 dBm
C priority: 3
D priority: 3 AV_RXLEV_NCELL (D)= -85 dBm

Target cell HOLoadFactor:


B load factor: 2
C load factor: 1 Which
Whichcell
cell(B/C/D)
(B/C/D)will
willbe
bechosen
chosenas
as
D load factor: 1 target for the Power Budget
target for the Power Budget HO?HO?
Target cell B is considered overloaded

Exercis e Solution

105 Nokia Siemens Networks


Combined Umbrella & Power Budget HO
Overview

enablePowerBudgetHo = Yes & enableUmbrellaHo = Yes


Power budget handover to cells of the same layer
Umbrella and FMT handover to cells of different layer

UMBR umbrella HO
RR radio reason HO
PBGT power budget HO
macrocells

PBGT,RR
UMBR+FMT RR

PBGT,RR
microcells

106 Nokia Siemens Networks


Combined Umbrella & Power Budget HO
Adjacent Cell Classification

Predefinition of layer possible by adjCellLayer (ACL)


Three layers visible relative to serving cell
Used for target cell evaluation
Combined umbrella and power budget
Handover based on MS speed
Fast moving MS handling in macro cell

UPPER layer (macro)

SAME layer (serving


layer)

LOWER layer (micro)

N (no
predefinition)
107 Nokia Siemens Networks
HO due to Directed Retry
IF
DirectedRetryUsed = Yes
Handover from SDCCH of serving cell to TCH of adjacent cell due to congestion
minTimeLimitDR Target cell evaluation started
MaxTimeLimitDR - Target cell evaluation stopped

Target Cell evaluation


IF
DirectedRetryMethod = 1
THEN
AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)
AND
AV_RXLEV_NCELL(n) > DRThreshold
ELSE
AV_RXLEV_NCELL(n) >RxLevMinCell(n) + MAX (0,Pa)

Interval between handovers and handover attempts

108 Nokia Siemens Networks


Directed Retry
Parameters

No TCH available during call set up in serving cell -> handover to TCH of other cell

Must be enabled with


drInUse (DR) Y/N

Thresholds to be exceeded by target cell according condition (1a)


drMethod (DRM) 0/1 Defined type of threshold
rxLevMinCell -110..-47 dBm Used if drMethod = 0
drThreshold (DRT) -110..-47 dBm Used if drMethod = 1 and
drThreshold > rxLevMin Cell
Timers (to be counted from TCH assignment)
minTimeLimitDirectedRetry (MIDR) 0..14 s No target cell evaluation
allowed
maxTimeLimitDirectedRetry (MADR) 1..15 s Target cell evaluation allowed

TCH
SDCCH minTimeLimitDR

Assignment
congested Request Time
maxTimeLimitDR

DR not allowed
DR allowed

109 Nokia Siemens Networks


HO due to Rapid Field Drop

IF
HoThresholdsRapidLevUL/Px > 0

IF
Px number of RXLEV_UL measurement < HoThresholdsRapidLevUL
THEN
Handover cause Rapid field drop

Target cell evaluation


IF
ChainedAdjacentCell(n) = Yes
AND
AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)

Order of preference of target cells:


The target cells are ranked according to radio link properties
(equation 1).

110 Nokia Siemens Networks


Rapid Field Drop Handover
Example

hoThresholdRapidLevUL = -93 dBm Chained


hoThresholdRapidLevUlN =2 Cell
chainedAdjacentCell =Y
Serving Cell

Serving cell

Threshold rapid field drop


handover 93 dBm
1st

2nd
Handover
triggered

111 Nokia Siemens Networks


NPT parameter related (HOC Parameter)

Should be lower
than POC
112 Nokia Siemens Networks
NPT parameter related (ADCE Parameter)

113 Nokia Siemens Networks


NPT parameter related (ADCE Parameter)

114 Nokia Siemens Networks


KPI case

115 Nokia Siemens Networks


Optimization Principle

Optimization process is a way to do changes in


a network so that those network have maximum
service on Capacity, Coverage and Quality
quality
Optimization
Excessive value RxLevAmi will
and Tailoring improve KPI but coverage and
quality will reduce

Site with height >40m with


cell coverage cell capacity total tilt =2 will have wide
coverage but KPI will bad

Site with FRL/FRU = 100% will


have max capacity but have
lower Quality

116 Nokia Siemens Networks


KPI- Rules, SDCCH Blocking

If SDCCH block high please check:


1.TCH/SDCCH availability
2.LOC design (SDCCH traffic profile)
3.Parameter (CRO, CRH,
RxLevAmi)

117 Nokia Siemens Networks


KPI- Rules, SDCCH Drop

If SDCCH drop high please check:


1.DL/UL Quality
2.CRO/CRH, TRP setting
3.TA profile overshooting possibility
118 Nokia Siemens Networks
4.SDCCH TS location
KPI- Rules, SDCCH Drop due to RF/Abis

119 Nokia Siemens Networks


KPI- Rules, SDCCH Drop due to Aif

120 Nokia Siemens Networks


KPI- Rules, SDCCH Drop (A)

121 Nokia Siemens Networks


KPI- Rules, SDCCH Drop (other)

122 Nokia Siemens Networks


KPI- Rules, TCH Block

123 Nokia Siemens Networks


KPI- Rules, TCH Drop Call Ratios
Dcr_3j

TCH DROPS AFTER SEIZURE


TCH_RADIO_FAIL /c1013
+TCH_RF_OLD_HO /c1014
+TCH_ABIS_FAIL_CALL /c1084
+TCH_ABIS_FAIL_OLD /c1085 Dcr_8h
+TCH_A_IF_FAIL_CALL /c1087 Dcr_5a
+TCH_A_IF_FAIL_OLD /c1088
+TCH_TR_FAIL /c1029
+TCH_TR_FAIL_OLD /c1030
+TCH_LAPD_FAIL /c1046 TCH DROPS AFTER ASSIGNMENT
+TCH_BTS_FAIL /c1047 tch_new_call_assign /c57033 CONVERSATION DROPS
+TCH_USER_ACT /c1048 +tch_ho_assign /c57034 dropped_calls /c57007
+TCH_BCSU_RESET /c1049
+TCH_NETW_ACT /c1050 -tch_norm_release /c57035
+TCH_ACT_FAIL_CALL /c1081 -tch_ho_release /c57036

-tch_re_est_assign /c57032 (S7) -tch_re_est_assign /c57032

DROPS

100 * %

CALLS
TCH SEIZURES FOR NEW CALL TCH ASSIGNMENTS FOR NEW CALL
tch_norm_seiz /c1009 tch_new_call_assign /c57033
+tch_seiz_due_sdcch_con /c1099 (S5)
+msc_i_sdcch_tch /c4044
STARTED CONVERSATIONS
-tch_re_est_assign /c57032
conver_started /c57015
+bsc_i_sdcch_tch /c4057
- msc_i_tch_tch /c4043
+cell_sdcch_tch /c4074
-tch_succ_seiz_for_dir_acc /c1165 (S7)
TCH RELEASE
-tch_re_est_assign /c57032 (S7)
CONVERSATION STARTED Disconnect from MS
conn_ack to BTS
TCH SEIZED
BSC allocates a TCH as a response to TCH ASSIGNED
TCH request (Channel Activation) Assignment_complete from BTS

RF CHN RELEASE
Rf_channel_release_ack
from BTS
124 Nokia Siemens Networks
KPI- Rules, TCH Drop due to RF/Abis

125 Nokia Siemens Networks


KPI- Rules, TCH Drop due to RF Old

126 Nokia Siemens Networks


How unnecessary HO happened??

RxLev = -80dBm
CRO=0

GSM

DCS

RxLev = -95dBm
CRO=23
HO threshold = 20

On idle mode received level for GSM is


-80 dBm while DCS can be (-95 dBm +
(2 x 23) -49dBm
On dedicated mode user will move Unecessary HO can lead to DCR due
from DCS to GSM due to DCS level to RF Old and HO fail (ex. Due to GSM
already too low blocking)
127 Nokia Siemens Networks
How unnecessary HO happened??
RxLev = -95dBm RxLev = -92dBm
HO threshold = 20 HO threshold = 20
RxLevmin from A to B = 12 RxLevmin from A to B = 12

GSM/DCS A GSM/DCS B

Call establish on cell A, then received After user serve by cell B, cell B will
level drop below HO threshold. User ask user to do handover as received
will move from cell A to cell B level on cell B already below HO
threshold.

128 Nokia Siemens Networks


KPI- Rules, TCH Drop due to Aif

129 Nokia Siemens Networks


KPI- Rules, TCH Drop due to Transcoder

130 Nokia Siemens Networks


KPI- Rules, TCH Drop

131 Nokia Siemens Networks


KPI- Rules, TCH Drop (Other)

132 Nokia Siemens Networks


KPI- Rules, coverage problems (dlq_2a and ulq_2a)
Here are some examples how different kind of HW problems can be found

1 4

2
1. Lots of Q4 samples. Distribution is not OK HW problem. Site reset will help
2. Lots of bad signal level samples. TRX/Combiner is broken. If no HW problem
Site is totally in wrong place, site is like transferring traffic to another cell ( cause
level HO). Typically a HW problem
3. Lots of Q6 and Q7 samples. Distribution is not OK, no Q5 samples HW
problems. Site reset or broken TRX
4. Typical normal interference problem.

133 Nokia Siemens Networks


KPI- Rules, Interference analysis DL /UL

Same level quality distribution


for both UL and DL

HW Problem
All samples below
-100dBm
CL10 <-100dBm

134 Nokia Siemens Networks


KPI- Rules, Interference, UL

MS power control can be seen here.


If Power is reduced no bad UL
problems. BSC border is increasing
good level samples

Bad interference problems. By POC


parameter interference can be
decreased, how power is adjusted
etc. Also optimum MS power feature
improves UL interference, no full
power is sent after HO.

Bad quality sample due to signal


level problems. Diversity should be
checked, also possibilities to use
LNA to improve UL signal level.
Antenna place should be also
checked if there are some obstacles
near the antenna.

135 Nokia Siemens Networks


KPI- Rules, Interference, UL, examples
Some UL interference in good signal
level. UL power control is not
working properly. Ul power control is
good indicator, if power is adjusted,
there are no big problems in UL
direction

There is no UL interference, or just a


little. MS is adjusting power properly,
there are only little samples in good
UL signal level.

Huge amount of UL bad samples. Cells is not working properly, it is like transferring traffic, UL quality/ UL level HOs are triggering
immediately. These kind of cells must be investigated.

136 Nokia Siemens Networks


KPI- Rules, Interference, DL
Really bad interference problem signal level is really
good (<-70dBm) and usually no better cell available no
HO samples can be seen in the table. Interference is
causing drops.

Bad interference problem signal level good (<-80dBm)


and sometimes no better cell available. If better cell
available and quality samples are 4 or worse HO (reason
quality or interference, depends on the parameter)
Interference is causing drops.

Situation is network is working properly If there are quality


4 or worse samples quality HO. Most of the samples are
q4 samples. If lots of q5..q7 samples interference
problem and interference must be analyzed / removed. If
quality HOs but no q5..q7 samples better cell is available
no interference problems. In these signal levels
overlapping exists and if handover reason is no PBGT, it will
be quality HO. By parameter amount of quality HOs can be
adjusted

Bad quality samples due to signal level problems. If PBGT


overlapping is not existing lots of quality HOs + level HOs
(margin are lower than in PBGT).
Not interference problem, more signal level problem.

Check how much samples vs. HOs are


137 Nokia Siemens Networks
better cells available or not.
KPI- Rules, Interference, DL, examples

There are almost as much samples Q5 and Q7 samples as


Q 4 samples even interference is really bad or there is
no better cell available ( no hos after bad quality samples).
These kind of interference cells should be optimized,
otherwise there are lots of drops etc

There are no as much Q5Q7 samples as Q4 samples


after interference samples Quality HO is done or the
interference situation is not so bad, for example sampling is
Q0,Q2,Q4,Q2,Q5,Q0,Q2,Q3,Q4,Q2 quality HO is not
triggering

There are bad quality samples only due to signal level


problems.

138 Nokia Siemens Networks


KPI- Rules, Interference (internal / external)

Internal Interference
Interference can be seen from stats or can be measured by scanner.
Neighbor cells (DL) or mobiles (UL) are causing interference.
By frequency / network planning interference can be decreased.
External Interference
Interference can be seen from stats or can be measured by scanner.
External radio frequencies are causing interference
Military use
In the border area, interference is coming from other country.
Some external wireless system (for example some wireless industry system)
is causing interference
Increased I level can be also due to external interference

139 Nokia Siemens Networks


KPI- Rules, HOSR

140 Nokia Siemens Networks


KPI- Rules, HO fail

sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho)


Total HO success ratio = 100 * (-------------------------------------------------------------------------------- ) (ho_65)
sum(msc_o_ho_cmd + bsc_o_ho_cmd_assgn + bts_ho_assgn)

sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho +


a.msc_to_wcdma_ran_succ_tch_ho)
Total HO failure ratio = 100 * (1- -------------------------------------------------------------------------------------) (hfr_2b)
sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +
b.bts_ho_assgn+a.msc_gen_sys_wcdma_ran_ho_com)

/* handovers failing due to blocking */


sum(a.msc_o_fail_lack + a.bsc_o_fail_lack + a.cell_fail_lack
+ a.msc_to_wcdma_ran_fail_lack)
HO failure ratio due to RF blocking = 100 * ---------------------------------------------------------------------------------------
/* all HO attempts */
sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn +
b.bts_ho_assgn + a.msc_gen_sys_wcdma_ran_ho_com)

(hfr_55a)

141 Nokia Siemens Networks

You might also like