BSSPAR1: Chapter 4 Radio Resource Management: 1 © Nokia Siemens Networks

BSSPAR1: Chapter 4
Radio Resource Management
1 © Nokia Siemens Networks

Legal Notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product
documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks
training material, are the exclusive property of Nokia Siemens Networks . Nokia Siemens Networks owns the
rights to copying, modification, translation, adaptation or derivatives including any improvements or
developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop,
license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material.
Individuals can use the Nokia Siemens Networks training material for their own personal self-development
only, those same individuals cannot subsequently pass on that same Intellectual Property to others without
the prior written agreement of Nokia Siemens Networks .
The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens
Networks training session for development of groups without the prior written agreement of Nokia Siemens
Networks.

Module Objectives
• Give an overview about the signalling to establish and release a call

• Discuss the standard and maximum acceptable interference level
algorithm used for TCH allocation
• Explain prioritised TCH allocation
• Give an overview about the parameter settings applied to queuing
• Explain how the queue is entered and left, and how these processes
interact with handover and especially directed retry
• Discuss the algorithms to verify call drop and re-establish a call
• Explain TCH allocation and queuing for Wireless Priority of Service
(WPS)

Signalling (Mobile Originating Call)
MS Channel request (RACH) NETWORK
Immediate assignment (AGCH) Immediate assignment
Service request (SDCCH)
Service request
Authentication request (SDCCH)
Authentication response (SDCCH) Authentication
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
Connect (FACCH)
Connect acknowledged (FACCH) Call accepted

Signalling (Mobile Terminating Call)
MS Page request (PCH) NETWORK
Channel request (RACH) Immediate assignment
Immediate assignment (AGCH)
Page response (SDCCH)
Service request
Authentication request (SDCCH)
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
Connect (FACCH)
Connect acknowledged (FACCH) Call accepted

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

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

TCH_HR_RADIO_CONGESTION_TIME (sec)
TCH_FR_RADIO_CONGESTION_TIME (sec)
TCH Allocation
2 TRX=16 channels
PEAK_PERMANENT_GPRS_CH
SDCCH
SDCCH_CONG_TIME(sec)
BCCH
PEAK_GPRS_CHANNELS
TCH_PEAK_BUSY_HALF
TCH_PEAK_BUSY_FULL
AVE_SDCCH (SDCCH/8)
AVE_GPRS_CHANNELS
PEAK_PERMANENT_GPRS_CH
AVE_AVAIL_FULL_TCH
AVE_TCH_BUSY_FULL
PEAK_BUSY_SDCCH
AVE_GPRS_CHANNELS
AVE_BUSY_SDCCH
AVE_TCH_BUSY_FULL
PEAK_BUSY_TCH
16.0
14.0
12.0
TIME
10.0
12:00:00 AM 32 5.0 18 6.3 4.0 9 9 0 0 8.48 0 4.7 8 2
RTSL
8.0
1:00:00 AM 32 3.1 13 6.8 3.4 9 9 0 0 1.41 0 4.2 9 2
6.0
2:00:00 AM 32 1.7 12 5.2 2.9 7 7 0 0 0 0 5.8 9 2
4.0 3:00:00 AM 32 1.5 12 6.2 1.4 7 7 0 0 0 0 4.8 9 2
4:00:00 AM 32 1.6 10 8.0 1.7 5 5 0 0 0 0 3.0 9 2
2.0
5:00:00 AM 32 8.8 32 5.7 0.8 6 6 0 559 0 0 5.3 9 2
0.0 6:00:00 AM 32 5.2 18 4.3 1.1 6 6 0 0 0 0 6.7 9 2
7:00:00 AM 32 6.5 23 8.5 2.6 8 8 0 0 0 0 2.5 6 2
2:00:00 AM
4:00:00 PM
12:00:00 AM
4:00:00 AM
6:00:00 AM
8:00:00 AM
12:00:00 PM
2:00:00 PM
6:00:00 PM
8:00:00 PM
10:00:00 PM
10:00:00 AM
8:00:00 AM 32 4.8 20 6.6 2.2 7 7 0 0 0 0 4.4 9 2

9:00:00 AM 32 4.3 20 6.8 2.4 8 8 0 0 0 0 4.3 9 2
10:00:00 AM 32 5.2 32 7.5 2.6 9 9 0 2 0.21 0 3.5 9 2
11:00:00 AM 32 5.9 18 6.3 2.9 9 9 0 0 8.98 0 4.7 9 2
12:00:00 PM 32 5.9 19 6.8 3.9 9 9 0 0 13.52 0 4.2 8 2
0 1 2 3 4 5 6 7 1:00:00 PM 32 7.3 24 6.4 3.4 9 9 0 0 8.96 0 4.6 9 2
TRX1 BCCH SDCCH SDCCH V/D V/D V/D V/D V/D 2:00:00 PM 32 6.8 30 6.2 3.9 9 9 0 0 44.05 0 4.8 8 2
TRX2 SDCCH SDCCH V/D V/D V/D V/D D D 3:00:00 PM 32 7.1 21 6.7 4.7 9 9 0 0 64.18 0 4.3 9 2
4:00:00 PM 32 7.7 23 6.6 3.9 9 9 0 0 25.61 0 4.4 8 2
5:00:00 PM 32 8.5 23 6.7 3.9 9 9 0 0 34.51 0 4.3 9 2
How can be optimized? 6:00:00 PM
7:00:00 PM
32 10.7 27 8.3 5.9
32 11.1 28 8.4 5.6
9
9
9
9
0
0
0 320.58
0 217.77
0
0
2.7
2.6
7
9
2
2
8:00:00 PM 32 10.4 30 7.8 5.5 9 9 0 0 284.15 0 3.2 8 2
9:00:00 PM 32 9.3 26 7.5 5.3 9 9 0 0 217.65 0 3.5 8 2
10:00:00 PM 32 8.3 22 7.5 5.2 9 9 0 0 185.36 0 3.5 9 2
8 © Nokia Siemens Networks 11:00:00 PM 32 5.8 21 6.8 4.6 9 9 0 0 89.61 0 4.2 9 2
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
Measurement Coding
LEVEL QUALITY INTERFERENCE
RxLev Coding BER(%) Coding I Interf.

(dBm) Band
-110dBm 0 < 0.2 0
-109 1 0.2-0.4 1 -110 to -105 0
-108 2 0.4-0.8 2 -104 to -100 1
. . 0.8-1.6 3 -99 to -95 2
. . -94 to -90 3
1.6-3.2 4
- 49 61
3.2-6.4 5 -89 to -47 4
- 48 62
- 47dBm 63 6.4-12.8 6
> 12.8 7

Maximum Interference Level
(Call Set Up + Intra Cell Handover)
Standard algorithm
Does not avoid allocation of strongly interfered channels

-> dropped calls
-> channels allocated again with same consequence
Maximum interference level algorithm
BSC tries to allocate TCH from interference band, into which MAX_INTF_LEV falls
-> TCH usually from better band than according the standard algorithm
MAX_INTF_LEV = RXLEV_UL - cNThreshold + (msTxPwrMax - MS_TXPWR)
Parameters
RXLEV_UL current uplink receive level

cNThreshold (CNT)0..63 dB desired C/N ratio
MS_TXPWR current MS output power
msTxPwrMax maximum allowed MS output power in serving cell
Maximum Interference Level
(Inter Cell Handover)
MAX_INTF_LEV = RXLEV_DL - rxLevBalance - cNThreshold
• RXLEV_UL is current uplink receive level
• BSC tries to allocate TCH in target cell from interference band, into which MAX_INTF_LEV falls
MO Abbreviated Range And Step Description Default BSC - MML

Class Name value Name
BSC rxLevBalance 0...20 dB, step 1 Balance between the DL signal level and 5 dB RXBAL
dB the UL signal level within the BSC
coverage area. DL is considered RXBAL
dB stronger than UL.
BTS cnThreshold 0...63, step 1 The minimum acceptable C/N 0 CNT
(carrier/noise) ratio when selecting a time
slot to be allocated for a call or handover.

Prioritized TCH Allocation
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

RX level based TCH Allocation
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

RX level based TCH Allocation
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: 0…63dB/ def: 12dB

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

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

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

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

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

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

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)
Counter has value 0 Example: short tunnel
Call release due to radio link

time out

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.

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

* MAX WAIT TIME OF RE-ESTAB REQ is a modifiable timer in MSC
Wireless Priority Service
• Wireless Priority Service is intended for National Security and

Emergency Preparedness (NS/EP) leaders and key personnel(ANSI
Markets)
• WPS calls are given priority access to the next available radio traffic
channel in congestion situation
• Reasonable amount of radio capacity must be available also for
public users

Principle
Overload situation  authorized personnel still should have access to network

 access for commercial users must be denied
MS access class
Indicated by BCCH system information message

MS belongs to indicated access class  access allowed
Otherwise  access not allowed
WPS user
Has basic access class and one of access classes 12-14

Resource management principle
Radio interface resource
WPS priority WPS preferred Public Service capacity %

capacity % capacity %
• Priority to WPS • Allowed to • Certain amount of public

users if the allocate to WPS calls must be served
share of WPS users without before resource to WPS
users is less restrictions when user can be allocated
than defined share of WPS when share of WPS users
WPS priority users exceeds exceeds WPS priority
capacity from WPS priority capacity and total cell
total cell load capacity but total load is exceeds WPS
• If cell is cell load is less priority capacity plus
congested WPS than WPS priority WPS preferred capacity
user is put on capacity plus WPS share.
queue preferred capacity • If cell is congested WPS
user is put on queue

Cell Load Thresholds
Parameter
wpsPriCapa (WPIC) 0..100% percentage of cell load, for which WPS users have
higher priority
wpsPrefCapa (WPEC) 0..100% percentage of remaining cell load, which can be
occupied without restricting access for WPS users
PublicServCount (PSC) 0..10 number of public user that must be served prior to
serving the next WPS call in the round robin allocation
Example
8 TCHs
wpsPriCapa = 50% (8 * 0.5) = 4 TCHs
wpsPrefCapa = 75% (8 – 4) * 0.75 = 3 TCHs
 round robin allocation is invoked when at least four WPS users occupy the cell and a total of seven or
more traffic channels (TCH) are occupied

Cell Load Calculation
Cell load = occupied resources / working resources
Rules to estimate number of occupied and working resources
Channel Number of Number of

occupied resources working resources
Free FR timeslot 0 1
Reserved FR timeslot 1 1
Free DR timeslot 0 3
Half reserved DR timeslot 2 3
Fully reserved DR timeslot 3 3
Free HR timeslot 0 2
Half reserved HR timeslot 1 2
Fully reserved HR timeslot 2 2
Default (E)GRPS timeslot taken into account for load calculation
Dedicated (E)GPRS timeslot not taken into account for load calculation

Round Robin Algorithm
At least wpsPriCapa capacity occupied by WPS users AND at

least wpsPrefCapa further capacity occupied by any users
Radio capacity assurance for public algorithm
Repeat steps until cell Serve publicServCount consecutive users

load falls below one of
the thresholds
Serve WPS user

Queuing
One queue for WPS users and one for all other ones
Same priority parameters

msPriorityUsedInQueueing Y/N must be set to Y to replace WPS calls of low
MS priority level with such ones of high priority
level in a full queue
But individual timers for WPS queue

timeLimitWPS (TLW) 0..30 s analogue to timeLimitCall
timeLimitWPSHO (TLWH) 0..30 s analogue to timeLimitHandover
Queuing and directed retry
Queuing continues, if timer maxTimeLimitDirectedRetry expires earlier than queuing timer

Queuing instead of directed retry, if load of target cell exceeds upper threshold wpsPrefCapa
Inter BSC directed retry not possible for WPS user

BSSPAR1: Chapter 4 Radio Resource Management: 1 © Nokia Siemens Networks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSSPAR1: Chapter 4 Radio Resource Management: 1 © Nokia Siemens Networks

Uploaded by

Copyright:

Available Formats

BSSPAR1: Chapter 4

Radio Resource Management

1 © Nokia Siemens Networks

Intellectual Property Rights

2 © Nokia Siemens Networks

• Give an overview about the signalling to establish and release a call

3 © Nokia Siemens Networks

Immediate assignment (AGCH) Immediate assignment

Service request (SDCCH)

Authentication request (SDCCH)

Authentication response (SDCCH) Authentication

Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Call proceeding (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Connect acknowledged (FACCH) Call accepted

4 © Nokia Siemens Networks

Channel request (RACH) Immediate assignment

Immediate assignment (AGCH)

Page response (SDCCH)

Authentication response (SDCCH) Authentication

Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Call confirmation (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Connect acknowledged (FACCH) Call accepted

5 © Nokia Siemens Networks

Release Call clearing

Release Call clearing

6 © Nokia Siemens Networks

Channel rate : full, half, dual, multi rate

A interface circuit allocated for call

Speech codec capabilities

7 © Nokia Siemens Networks

8:00:00 AM 32 4.8 20 6.6 2.2 7 7 0 0 0 0 4.4 9 2

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

Classification into interference bands based on interferenceAveragingProcess

BO5 –47 (fixed)

RxLev Coding BER(%) Coding I Interf.

10 © Nokia Siemens Networks

Does not avoid allocation of strongly interfered channels

Maximum interference level algorithm

MAX_INTF_LEV = RXLEV_UL - cNThreshold + (msTxPwrMax - MS_TXPWR)

RXLEV_UL current uplink receive level

MAX_INTF_LEV = RXLEV_DL - rxLevBalance - cNThreshold

• RXLEV_UL is current uplink receive level

MO Abbreviated Range And Step Description Default BSC - MML

12 © Nokia Siemens Networks

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

Priority for TCH from other TRX

trxPriorityInTCHAlloc (TRP) 0 = no priority

13 © Nokia Siemens Networks

Enables to differentiate Rx level requirement for:

RX level based TCH allocation method

Provides better drop call meters and better performance of MSs

Note! RG20 feature – Energy optimized TCH allocation

14 © Nokia Siemens Networks

Soft blocking C/N FR: 0…63dB/ def: 12dB