Cell Capacity Monitoring and

Optimization
GS NPO Radio
• Jarkko Itkonen
• 12-06-2015

Latest version: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D495067319

1 © Nokia Solutions and Networks 2014
<Change information classification in footer>
Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing

4 © Nokia Solutions and Networks 2014

Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing

5 © Nokia Solutions and Networks 2014

UL air interface capacity

• The uplink radio interface capacity is limited by noise rise

- In high traffic situations large share of the noise rise is caused by data user L1 signalling
• Uplink L1 signalling
- DPCCH (pilot, power control)
- HSDPA user: HS-DPCCH (CQI, ACK/NACK)
- HSUPA user: E-DPCCH (HSUPA user during UL transmission)
• Additional UL load is caused by the user data traffic
- DPDCH (UL DCH users)
- EDPDCH (HSUPA)

• Also RACH UL transmission is a significant source of UL load

6 © Nokia Solutions and Networks 2014

L1 signalling load in UL radio interface

• In smart phone dominated traffic the received

power of the L1 signalling channels depends
mostly on the initial SIR target defined in RNC
- Short data connections with low amount of
UL data
• Load caused by L1 signalling can be
estimated from initial SIR targets
- The initial SIR targets should be optimised
• Drop HSDPA return channel SIR targets
by 3 dB (WRAB parameters)
• Drop HSUPA initial SIR targets (see
parameter recommendations)

7 © Nokia Solutions and Networks 2014

Reduce HSUPA L1 control channel over heads – Theory

• The initial SIR target has extremely high impact on the control channel load of the HSUPA
transmission, below is graphs showing the load of ONLY L1 CONTROL PART i.e. no E-DPDCH
- Assuming 0% activity factor for HSUPA data channel
- Assuming short session with low data activity  SIR target remains at initial level
Default initial SIR targets NPO recommended initial SIR targets

8 © Nokia Solutions and Networks 2014

 Reduce HSUPA L1 control channel overheads -
Lab test result
UL FTP throughput
4
• With default+TN159 parameter set the FTP

L2 throughput (Mbps)
3
upload and http download throughputs collapse DEF
2
when more than 30 inactive users enter cell REC
1

0
• Recommended HSUPA SIR target offsets enable 0 0 0 0 0 0 0
d0 ad1 ad2 ad3 ad4 ad5 ad6 ad7
5
a
support for higher number of HSPA users in cell Lo Lo lo Lo Lo Lo lo Lo

DL http throughput
4

L2 throughput (Mbps)
3

2 DEF
Test cases:DEF: RNC+TN159 default parameters (PRFILE params = 0) REC
REC: Recommended set (NPO + TN159) 1

0
0 0 0 0 0 0 0 5
9 © Nokia Solutions and Networks 2014 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7
Lo Lo lo Lo Lo Lo lo Lo
Further reduction of L1 overheads in UL with RAN2879 Mass Event Handler

• 2 ms TTI users cause relatively higher UL noise rise and the benefit of 2 ms TTI usage
decrease in loaded cells. Thus it is beneficial to prevent 2 ms TTI usage in loaded
conditions.
- RAN2879 Mass Event Handler sub-feature “Load based E-DCH 2 ms TTI prevention”
can be used to prevent 2 ms TTI allocations when # of HSUPA links in the cells
exceed pre-defined threshold

• CQI reporting forms significant part of the UL L1 signalling for HSDPA users and in highly
loaded cells the UL capacity is most probably limiting
- RAN2879 Mass Event Handler sub-feature “Increased CQI feedback cycle” can be
used to decrease the UL load caused by the CQI reporting

10 © Nokia Solutions and Networks 2014

Total gain of 2ms TTI switching and CQI UL FTP throughput
reduction - Lab test result 3.5
3
2.5
• Test done with maximum CQI reporting period of 20 ms 2
REC
- The effect on HSDPA performance in live network 1.5
REC(2ms+CQI20)
1
conditions should be verified 0.5
0
0 0 0 0 0
ad0 ad2 ad4 ad6
• The total UL and DL throughput gain is significant when Lo lo Lo lo

both 2ms TTI prevention and CQI reporting reduction

functionalities are enabled same time DL http throughput
4

• More details in Mass Event handler NPO feature

L2 throughput (Mbps)
3
materials (NPO Mobile Radio Community) 2 REC
REC(2ms+CQI20)
1
Test cases:
0
REC: Recommended set
0 0 0 0 0
REC(2ms+CQI20): As REC, but use TTI switching from 2ms and CQI ad0 ad2 ad4 ad6
reporting interval 20 Lo lo Lo lo

11 © Nokia Solutions and Networks 2014

Dynamic HSUPA Power Offsets due to number of HSPA users
• Without use of the Dynamic HSUPA Power Offsets feature the HSUPA power offsets are optimized
for high bit data rates (HSUPA peak rates)
- The power offsets are too high for low bit rates
- Also the throughput is poor in cell edge
• The power offsets are not possible to be optimized for both high and low bit rates simultaneously
when E-DPDCH power extrapolation method is used
- Also Rel-6 UEs and newer UEs that not supporting interpolation method.
• In some networks has been seen that in certain level of load, the HSUPA peak rate of the UE is
limited to 2 Mbps
- Dynamic HSUPA Power Offset feature triggers too aggressively in terms of # of HSPA users in cell
• Delayed start of Dynamic HSUPA Power Offsets (PRFILE parameter 002:1903 RN60_MAINT_27)
due to number of HSPA users intoruduces HSPA threshold that can be controlled by operator

12 © Nokia Solutions and Networks 2014

Presentation / Author / Date

Dynamic power offset calculation

• UE calculates power offfset

between DPCCH and E-
DPDCH based on selected
TBS size and signalled
reference power offsets from
RNC
5760 kbps High bit rate

E-TFCI E-DCH size Power

offset
39.00 474 2.533333
101.00 4019 3.133333
125.00 10681 5
127.00 11484 6.333333
30000
13 © Nokia Solutions and Networks 2014

PS NPO Capability Creation / Feb 2013

 Dynamic power offset effect on UL end-user performance

• The dynamic power offset algorithm Dynamic power offset effect on HSUPA throughput
decreases the L1 signalling overhead but 4
3.5

L2 throughput (Mbps)
simultaneously limits the HSUPA peak 3
throughput 2.5
2 HPO
• Low bit rate offset are triggered by default 1.5 REC
1
after 3 users (4th with low bit rate offset) 0.5
• Results indicates that in the lab 0
0 5 10 15 20 25 30
environment the optimum point to trigger Number of HSUPA users
power offset change is around 15 HSUPA
users
Test cases:
• No other cell interference etc. REC: Recommended set
HPO: As REC, but additionally switch to low bit rate
• Only one active HSUPA upload power offsets disabled
 Recommendation to switch after 10
14
users © Nokia Solutions and Networks 2014
Dept. / Author / Date
UL air interface capacity optimisation

• Reduce number of simultaneous connections (optimise DCH usage)

- Short inactivity timers
- CCH setup usage for PS calls
- Higher traffic volume thresholds

• Optimised initial SIR targets (HSUPA and HSDPA return channel on DCH) (TN159 + NPO reco)

• RACH load control

- Power and ramp-up parameters
- Reduction of signalling

• Cell overlap control, dominance optimisation (DO NOT FORGET RF OPTIMISATION)

15 © Nokia Solutions and Networks 2014

Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing

16 © Nokia Solutions and Networks 2014

Downlink power

• Downlink power limitation is often seen with high number of simultaneous connections in
macro cells with high level of DL interference and DL pathloss

• DL power is used mainly by

- AMR calls
- HSDPA connection L1 DPCCH + HSDPA connection associated signalling SRB
- DL NRT R99 data connection (used when HSDPA can not be allocated)
- DL standalone SRBs (registrations, RAB 0/0)

17 © Nokia Solutions and Networks 2014

DL spreading codes
• Downlink spreading code capacity is shared between
- HSDPA HS-DSCH (fixed minimum 5 code SF16 reservation)
- DL R99 connections
• AMR calls, HSDPA associated signalling, R99 data, standalone signalling SRB3.4 and SRB13.6
- DL Common Control Channels (about 1 SF16 code)
- HSDPA and HSUPA DL control channels
• 1-3 x HS-SCCH, E-AGCH, 1-4 x (E-RGCH + E-HICH)

• Available code capacity is about 76 SF128 codes, after

CCH and HSDPA fixed allocation

• Enabled features also impact code usage, for example:

• HSUPA 10ms and HSUPA 2ms (different)
• 24 kbps paging channel due the addition of second
SCCPCH
channel
• 72 HSPA users (dynamic HS-SCCH code allocation)
• F-DPCH
18 © Nokia Solutions and Networks 2014
 DL air interface capacity optimisation
• Reduce number of simultaneous connections in CELL_DCH (as UL)

• DL R99 power and codes used by HSDPA associated signalling can be limited by limitation of max number of HSDPA
connections (Adaptive limitation with RU40 feature

• Limitation of SHO overhead decreases DL power and code usage

• Initial downlink radio link power reduction (PRFILE, see NPO recommended parameters)

• Limitation of maximum power per radio link

• AMR 5.6 can potentially provide small DL power saving but clear saving in codes

• F-DPCH reduces L1 DPCCH and SRB power together with DL codes for HSPA connections

19 © Nokia Solutions and Networks 2014

Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing
•
20 © Nokia Solutions and Networks 2014
AC and PS functionality

• Admission Control
- AMR calls
- SRB allocations (partly)
- No AC for packet calls setups
• HSUPA/HSDPA (HSUPA AC optional functionality, TN137)
• HSDPA DL (RU40 optional Voice Call Prioritization)
• SRB allocations (partly)
Packet scheduler
- Queuing of capacity requests
• Max 20 CR in queue, after that AC failure (initial CR requests, bit rate upgrade requests)
• HSPA request allocated before queuing (full queue does not prevent)
• Maximum queuing time
- Initial allocation and bit rate selection for R99 data connections (R99/R99, HSDPA/R99 UL)
- Enhanced PBS to downgrade or release existing connection when no room for incoming initial bit rate (optional)

21 © Nokia Solutions and Networks 2014

AC for SRB requests
• RRC Connections requests not subject to power based AC
- Establishment Cause values “Emergency Call”, “Registration”, “Detach”, “Originating High Priority
Signalling”, “Terminating High Priority Signalling”, “Inter-RAT Cell Re-selection”, or “Inter-RAT Cell
Change Order”
• RRC Connections requests subject to power based AC
- Admission criteria: PtxTotal < PtxTarget (no power increase added)
- the values “Originating Conversational Call”, “Terminating Conversational Call”, “Originating
Streaming Call”, “Terminating Streaming Call”, “Originating Interactive Call”, “Originating
Background Call”, “Terminating Interactive Call”, “Terminating Background Call”, “Originating
Subscribed Traffic Call”, “Originating Low Priority Signalling”, “Terminating Low Priority Signalling”,
“Call Re-establishment”, or “Terminating – cause unknown”
• AC will always admit cell update request
- No need for CELL_DCH allocation, UE will end up to same state in most cases
- “UL data transmission” cause will be handled as capacity request

22 © Nokia Solutions and Networks 2014

Throughput based scheduling in UL
• Throughput based scheduling can be used to maintain a minimum level of traffic allocations even in
case of UL power congestion
• PrxLoadMarginDCH is used for admission control and packet scheduling of R99 UL connections
- Based on estimated load (user plane + SRB + L1 control), also L1 of HSUPA (DPCCH and HS-
DPCCH) included in UL load
Load per connection calculated based on initial SIR target

23 © Nokia Solutions and Networks 2014

AC and PS optimisation - UL

• AC for AMR/SRB
- Targets at reasonable load level (PrxTarget <= 8dB)
- Utilise throughput based scheduling in UL (PrxLoadMarginDCH = 2-4 dB)

• NRT R99 packet scheduling

- Targets at reasonable load level (PrxTargetPSMax&Min <= 8 dB)
- Minimum and initial bit rates low
- Some throughput based scheduling in UL (PrxLoadMarginDCH = 2-4 dB)
- Reduce capacity request repetitions

HSUPA packet scheduling

- Targets at reasonable level (PrxMaxTargetBTS <= 10 dB)
24 © Nokia Solutions and Networks 2014
AC and PS optimisation - DL

• AC for AMR/SRB
- Targets at reasonable load level (PtxTarget <= Ptx_max – 1 dB)
- Use PtxOffset (Ptx_max – PtxTarget) to improve AMR (+ selected SRB) accessibility

• NRT R99 packet scheduling

- Targets at reasonable load level (PtxTargetPSMax&Min << PtxTarget)
- Minimum and initial bit rates low
- Reduce capacity request repetitions

• Voice Call Prioritisation to prioritise AMR + SRB over HSPA

25 © Nokia Solutions and Networks 2014

High traffic optimised AC + PS

• Scenario: Extreme traffic conditions with >2000 smartphone subs in cell

• Traffic profile
- SRB traffic: Registrations (RRC setups), capacity requests (RRC setups and
Cell updates, Cell updates (Cell re-selection)
- AMR traffic: Average traffic load 10-15 Erlangs
- PS (HSPA) traffic: High # packet calls and UL/DL data volume
- Some HSDPA/R99

26 © Nokia Solutions and Networks 2014

Traffic handling strategy and Design

• Traffic handling strategy

- Which services to prioritise?

• Design
- AC and PS configuration
- Features and setup

27 © Nokia Solutions and Networks 2014

Traffic handling strategy – Example

• 1st priority target 100% accessibility for

- High priority RRC setups
- AMR calls
• 2nd priority target 100% retainability for
- Stand-alone SRB
- AMR calls
• 3rd priority target maintain cell throughput

• 4th priority target Accessibility and retainability:

- RRC setups
- Packet calls
28 © Nokia Solutions and Networks 2014
Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing
•
29 © Nokia Solutions and Networks 2014
Common control channel signalling capacity

• Common control channels carry paging and connection request/setup signalling

- PCH on S-CCPCH
• Terminated speech call pages
• DL traffic initiated packet connection pages
- FACH-c on S-CCPCH
• RRC Setup
• Packet session setup (RB reconfiguration, Cell Update Confirm)
- RACH on PRACH
• RRC connection requests
• Cell update messages (UL capacity request, Cell update, Routing area and location area update, inter-system
mobility

- RACH and FACH carry also user plane data traffic if there is room

30 © Nokia Solutions and Networks 2014

 CCH channel capacity

messages/10 messages/10
RACH_capacity parameter 2 ms RACH_capacity parameter 4 ms
Time interval 10 ms Time interval 10 ms
RACH-c TB 168 bit RACH-c TB 168 bit
RACH-u TB 360 bit RACH-u TB 360 bit

RACH-c throughput 33.6 kbps RACH-c throughput 67.2 kbps

RACH-u throughput 72 kbps RACH-u throughput 144 kbps

RACH preambles per RACH RACH preambles per RACH frame 60

frame 60
PCH capacity FACH capacity (Dedicated, 2 S-
CCPCH)

PCH TB size max 80 bits

PCH TB size max, 24k 240 bits TTI 10 ms
TTI 10 ms

FACH-c TB size 168 bits

PCH throughput 8 kbps FACH-c TB/TTI max 2 TB/TTI
PCH throughput, 24k 24 kbps FACH-u TB size 360 bits
FACH-u TB/TTI max 1 TB/TTI

FACH-c throughput 33.6 kbps

31 © Nokia Solutions and Networks 2014 FACH-u throughput 36 kbps
CCH capacity optimisation

• Activation of 2 S-CCPCH

• Increase RACH decoding capacity (max 4)

• Decrease required signalling in CCH

• Reduce capacity requests
• Reduce RRC request retransmissions
• Reduce cell updates (URA_PCH)

CCH load control limits the CCH usage when load reached 75% on PRACH or FACH
• FACH load threshold can be increased to 90%
32 © Nokia Solutions and Networks 2014
Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing

33 © Nokia Solutions and Networks 2014

BTS baseband capacity optimisation

• Reduce number of simultaneous connections (as UL)

• HSUPA resource usage can be limited by limitation of max number of HSUPA

connections per LCG

• Limitation of SHO overhead increases DL power and code usage

• F-DPCH reduces L1 DPCCH and SRB power together with DL codes for HSPA
connections

34 © Nokia Solutions and Networks 2014

Cell capacity optimisation areas

• UL air interface capacity

• DL air interface capacity

• AC and PS optimisation

• CCH capacity optimisation

• BTS baseband capacity optimisation

• Load balancing

35 © Nokia Solutions and Networks 2014

Optimisation of load balancing between carriers, bands and systems

• Layering strategy to balance load between U2100 carriers

Layering strategy to balance load between U900 and U2100 bands

Layering strategy to balance load between WCDMA and GSM

36 © Nokia Solutions and Networks 2014

SUMMARY: Cell capacity optimisation

• Main target of cell capacity optimisation is to provide good voice service accessibility and
simultaneously maintain cell throughput

• Main optimisation areas

1. Optimise CELL_DCH usage (state machine, CCH setup etc.)
2. Utilise HSUPA AC functionality to restrict HSUPA access when UL power in overload
3. Configure throughput based scheduling to maintain planned level of UL DCH allocations
4. Restrict HSDPA connection per cell to protect voice service from DL power blocking (RU40 use
Voice Call Prioritization)
5. Implement HSUPA initial SIR target and other NPO/PL parameter recommendations
6. Last but not least: RF optimisation

37 © Nokia Solutions and Networks 2014