RL50 RACH Optimization

NEI RACH Optimization
RL50/RL50FZ – LTE962 RACH Optimization

(on top of RL30 - LTE581 PRACH Management)
Adam Pomykala
MBB CS Network Engineering
Wrocław, 03.2014
Please always check the latest version of this NEI slides here
For internal use
5/16/2018 © Nokia Solutions and Networks 2013
LTE962 - RACH Optimization
Table of Contents
Introduction Configuration Management

1 Motivation and Feature Overview
5 Parameters and Parameterisation scenarios
Technical Details Deployment Aspects

2 Functionality and Implementation, Message Flows
6 Activation, Configuration Examples, Fault Mgmt, Trial Area
Interdependencies Performance Aspects

3 Interdependencies with Other Features and Functions 7 Counters and KPIs, Feature Impact Analysis and Verification
Benefits and Gains

4 Simulation, Lab and Field Findings
NEI Contact: Adam Pomykala

For internal use
4 © Nokia Solutions and Networks 2013
Table of Contents



Benefits and Gains


For internal use
Introduction - Definitions Main
Table of Menu
Contents
• Random Access procedure - used by UE and Network to get access to the services
• RACH - Random Access Channel, is an uplink transport channel where

each user equipment (UE) transmits PRACH, to get access to the network.
• PRACH - Physical Random Access CHannel.
• Due to network topology change, incorrect initial configuration of PRACH parameters may result in:
 Collisions: PRACH settings (within the reuse distance) among neighbors and inside the site (e.g. Distributed
Antenna System) that are colliding, which results in... decreased PRACH detection probability.
 Inconsistencies: PRACH related parameters not in line with other own cell parameters, provide interferences to
cells and physical channels. It results in decreased overall performance for RA and other procedures.
PRACH optimization is used to reduce impact from Collisions and Inconsistencies in the eNB, with neighboring
For internal use
6 cells and other cells within theSolutions
© Nokia reuseanddistance
Networks 2013
Introduction – What and when could be optimized? Main
Table of Menu
Contents
• Differentiation of PRACH can be done in:

- Time Domain
• PRACH configuration index [prachConfIndex]
- Frequency Domain
• PRACH frequency offset [prachFreqOff]
- Code Domain
• PRACH cyclic shift [prachCS]
• PRACH Root sequence [rootSeqIndex]
• Since RL50 NetAct gives possibility to configure PRACH related parameters:

• as a part of eNB auto-configuration process – for new deployments
• for existing sites by MANUAL triggering optimization process
• The optimization for the collision and inconsistency resolution can be
applied for:
• single eNB and all its subordinate cells or individual cells
• dedicated list of eNBs and all their subordinate cells
• all eNBs of NetAct Regional Cluster
For internal use

7 MBB CS Network Engineering/ Adam Pomykala © Nokia Solutions and Networks 2013
Introduction – LTE581 and LTE962 Main
Table of Menu
Contents
• In RL30 with LTE581 PRACH management PRACH parameters could be allocated ONLY during initial
RL30 auto-configuration process supported by NetAct (incl. CM Operations Manager)
• In RL30 initially configured PRACH parameters were not further optimized in NetAct
• In RL50 the LTE962 - RACH Optimization feature is requested in addition (as a Feature Component) to the
existing LTE581 PRACH management feature.
RL50
• RACH Optimization will follow 3GPP (TS 36.902) definitions, but will consider centralized approach as
defined with LTE581 PRACH management.
LTE 962 ‘RACH optimization’ scope:

• RACH Optimization feature basically deals with the identification and resolution of conflicts and
inconsistencies due to incorrect configuration of PRACH related parameters or PRACH
parameters itself
• LTE 962 can be used AFTER initial assignment of PRACH parameters e.g. if performed with
LTE581 or where eNodeB was manual configured
For internal use

Introduction – LTE581 and LTE962 Main
Table of Menu
Contents
PRACH management feature in Optimizer 3.0 CD 3

Automatic assignment of the PRACH parameters defined as a part of eNB auto configuration. During
auto configuration, Optimizers ‘PRACH management’ feature is invoked by NetAct Configurator through
Configurator Workflow Engine to configure PRACH parameters: PRACH configuration index , PRACH
frequency offset, PRACH cyclic shift , PRACH Root sequence
PRACH parameter assignment is done considering,
• Geo Location of the eNodeB and neighboring cells RACH Optimization
based on TA KPIs (LTE
• Own cell database parameters RACH Optimization based 1463. Release not
on own cell parameters finalized)
• User Input Parameters (e.g., Expected cell range, RACH density) (LTE962. OPT 3.2, OPT 8)
PRACH configuration from
LTE 962 RACH Optimization feature in Optimizer 3.2 Tier-1 Client
(LTE581. OPT 3.1 CD 2)
This feature offers the optimization of PRACH / RACH parameters by Resolution of
Collisions and Inconsistencies. Collision and inconsistency resolution can be
PRACH Auto configuration
applied for: from WFE
•Single eNB and all its subordinate cells or individual cells (LTE581. OPT 3.0 CD 3)
•Dedicated List of eNBs and all their subordinate cells
•All eNBs of NetAct Region
RACH Optimization can be executed by manual trigger from Optimizer

client and Configurator WFE (Work Flow Engine)
For internal use
Introduction – LTE581 in RL30 Main
Table of Menu
Contents
LTE581 PRACH Management in RL30:

• Automatic assignment of PRACH parameters settings possible ONLY during the initial auto-configuration process
• Process is based on pre-planning information: from NetAct plan file or

• geo-location information of eNB where the cell(s) is to be configured
• geo-locations of all other already configured eNBs
from the actual
• own and surrounding eNBs/cells configuration data (parameters) Configurator CM database
• The algorithm uses dedicated information as INPUT:

• Reuse distance
• Expected pathloss characteristic of the cell
• Expected UE speed with the cell / high speed flag
Defined in Configurator
• Expected RACH load for the cell / target RACH collision probability preferences
• process is applied only for cells using THE SAME frequency and bandwidth
Process is embedded into the LTE720 auto-configuration frame work.
For internal use

Table of Menu
Contents
LTE581 PRACH Management related IMPROVEMENTS in RL50:
LTE581 in RL50 has the same approach as in RL30 in area of:

• automatic assignment of PRACH parameters settings during the initial auto-configuration process
but with the modifications/extensions in RL50:
• LTE581 improvements common with LTE962

- New algorithm to identify cells which have PRACH resources overlapping in frequency domain
- Time domain overlapping can be identified based on their prachConfIndex value (and tddFrameConf for TDD)
- Instead of Extended Cell Range (ECR) the prachCS parameter of neighboring cells is used to calculate number of used Root
Sequence Index (RSIs)
- New mapping table of E-UTRA bands and corresponding downlink and uplink configurations
- during PRACH Allocation it is possible to define CELL forbidden parameter settings on top of existing GLOBAL forbidden
set
• Improvements applied Only for LTE581 for auto-configuration process:

- configuring raRespWindowSize and prachConfIndex parameter based on number of Intra eNB cells
For internal use

Table of Menu
Contents
LTE962 RACH Optimization introduction in RL50:

• LTE962 RACH Optimization introdused as new feature component for LTE581 PRACH Management
• It supports the automatic assignment of the same parameters as LTE581:
• PRACH configuration index (LNCEL:prachConfIndex)
• PRACH frequency offset (LNCEL:prachFreqOff)
• PRACH cyclic shift (LNCEL:prachCS)
• PRACH Root sequence (LNCEL:rootSeqIndex)
NOTE: LTE962 gives option to initiate optimization process AFTER parameter initial
assignment e.g. that was performed with LTE581
LTE962 can be used for network settings verification if:
• Some of eNodeBs were manually configured (i.e. without LTE581)

• eNB parameters relevant for PRACH allocation were CHANGED AFTER auto-configuration process of eNB
• There is a change of network topology (new eNBs added with auto-configuration process BUT as LTE581 is
not able to change already configured eNBs therefore collision free PRACH allocation could not be performed)
• There is a Change of Antenna location e.g. use of distributed sites
For internal use

Introduction – RL50 extensions Main
Table of Menu
Contents
• LTE962/LTE381 with extensions to support HetNet

• Cases which may exist in network either …
• due to cells having SMALLER available bandwidth (i.e. ulChBw/chBw) or
• due to cells having LARGER available bandwidth or
• cells placed in neighboring frequency (overlapped bandwidths)
are now supported as the cells under optimization.
• Cell from different frequencies and with different bandwidth are checked against collisions
For internal use

Table of Contents



Benefits and Gains


For internal use
Technical Details Main
Table of Menu
Contents
• Dependency table:
FD-LTE RL release eNB NetAct
Release/version RL50 LN5.0 OSS5.5 (Optimizer 3.2)
TD-LTE TD LTE release eNB NetAct
Release/version RL45TD LNT3.0 OSS5.5 (Optimizer 3.2)
Flexi Zone Micro FZM release eNB NetAct
Release/version RL50FZ LNFZ5.0 OSS5.5 (Optimizer 3.2)
HW & IOT HW requirements MME SAE GW UE
Release/version - - - -
For internal use

Technical Details – Why Random Access Procedure is Used? Main
Table of Menu
Contents
To schedule UE ...
UL transmission timing should be synchronized
1. Initial access from RRC_IDLE;

2. RRC Connection Re-establishment procedure;
3. Handover;
4. DL data arrival during RRC_CONNECTED requiring random access
procedure, e.g. when UL synchronization status is ‘non-synchronised’;
5. UL data arrival during RRC_CONNECTED requiring random access procedure, e.g.
when UL synchronization status is ‘non-synchronised’ or there are no PUCCH
resources for Scheduling Request (SR) available;
6. For positioning purpose during RRC_CONNECTED requiring
random access procedure (e.g. when timing advance is needed for UE positioning);
The random access procedure takes two distinct forms:
• Contention based (applicable to first five events)
• Contention free (applicable only to handover, DL data arrival and positioning) mainly for time critical events
For internal use

Technical Details –What is PRACH? Main
Table of Menu
Contents
Before initiation of the non-synchronized RA procedure, UE physical layer should receive the following
information (parameters) from the higher layers (e.g. previously received in SIB2):
• Physical RA channel parameters (PRACH configuration and frequency position)
• Parameters for determining the root sequences (index to logical root sequence table) their cyclic shifts (Ncs)
and sequence set type (unrestricted or restricted set) – based on prachHsFlag
UE is sending preamble to the network on PRACH:
• PRACH occupies 6 resource blocks (of 180 kHz) in a
subframe (or set of consecutive subframes) reserved for
sending random access preamble to the network.
• The length of TCP (Cyclic Prefix)，TPRE (Preamble) and TGT
(Guard Time) depends on the preamble format
• PRACH reserved PRBs cannot be used by PUSCH i.e. they

are out of scope for scheduling for data transmission
Fig. PRACH channel structure for preamble format type 0
no data from higher layers is
For internal use
17 carried on PRACH © Nokia Solutions and Networks 2013
Technical Details – RA procedure: When and what to send? Main
Table of Menu
Contents
When UE can start Random Access Procedure:

• The transmission of a Random Access preambles (UL: UE to the Network) is restricted to certain time and frequency resources.
• Parameter prachConfIndex is indicating when - in time domain - preamble transmission can occur
• The start of the random access preamble is aligned with the start of the corresponding uplink subframe and the UE is assuming time
shift NTA equal to 0
What UE can send to the Network during RA procedure:
• UE can send different preamble formats  number of allocated subframes and max. cell range depends on the preamble format
• parameter prachConfIndex is indicating also allowed preamble format
PRACH configuration index for MACRO sites:

• Cell range: guard time length: 97...715 us  small, medium, large
• Path loss: preamble length: 800 or 1600 us  normal or increased
• RACH density: up to 2 subframes can be used for PRACH  How to calculate? Link to slide
Preamble format TCP TPRE Description
Normal 1 ms RA burst with 800 µs preamble sequenc
0 103.13 800 e, for small-medium cells
(up to ~14.5 km)
2 ms RA burst with 800 µs preamble sequence, for larg
1 684.38 800 e cells (up to ~77 km) without a link budget problem
2 ms RA burst with 1600 µs preamble sequence, for m
2 203.13 1600 edium cell (up to ~29 km) and increased path loss
3 ms RA burst with 1600 µs preamble sequence, for v
3 684.38 1600 ery large cells (up to ~100 km) and increased path loss
For internal use
Tab: Mapping table for PRACH configuration index, subframe
format and number of subframes within the frame:
Technical Details – RA procedure: When and what to send? – Flexi Zone Micro Table of Contents
PRACH configuration index limitation in Flexi ZoneMicro (FZM)

• preamble format 0 only is supported in FZM
• range of the prachConfIndex is limited to 3…8
Why is limited?
• PRACH configuration index is limited to FZM as a consequence of transmit power capability (small cell solution) - with no option to
use FZM within large cell deployment
PRACH configuration index for FZM:

• Cell range: guard time length 97us  cell range up to 14.5 km
• Path loss: preamble length: 800us  NORMAL link budget (pathloss)
• RACH density: up to 2 subframes can be used for PRACH  How to calculate? Link to slide
Preamble format TCP TPRE Description
Normal 1 ms RA burst with 800 µs preamble sequenc
0 103.13 800 e, for small-medium cells
(up to ~14.5 km)
2 ms RA burst with 800 µs preamble sequence, for larg
1 684.38 800 e cells (up to ~77 km) without a link budget problem
2 ms RA burst with 1600 µs preamble sequence, for m
2 203.13 1600 edium cell (up to ~29 km) and increased path loss
3 ms RA burst with 1600 µs preamble sequence, for v
3 684.38 1600 ery large cells (up to ~100 km) and increased path loss
For internal use
Tab: Mapping table for PRACH configuration index, subframe
format and number of subframes within the frame:
Technical Details – RACH density Main
Table of Menu
Contents
prachConfIndex selection based on PRACH detection probability:

- limited number of preambles is available in the cell  64 preambles in total (dedicated, non-dedicated)
- random preamble selection (done by UE) out of non-dedicated preamble set cannot guarantee collision free transmission 
contention resolution is required
- to maximize contention resolution probability RACH density should be taken into account when PRACH capacity is planned – e.g.
based on expected load
How to calculate capacity required for PRACH based on EXPECTED load?
1. Calculate RACH Density (x): based on the expected RACH load and the maximum RACH collisions probability
• RACH load: is the number of RACH attempts per second – estimated e.g. based on predictions.
• Maximum RACH collisions probability: indicate the collision probability threshold [%] that will be required to not exceed (e.g. ~2%).
2. Find the number of sub-frames (possible prachConfIndex settings) within the frame that could be used by UE to send preamble
1 2
( RACH _ Load ) If RACH density (x) based on equation is:
x 0.5 ≤ x  required # of sub frames = 0.5
 UE

 1  64  ln 1  pcoll
 100 0.5 < x ≤ 1  required # of sub frames = 1
1 < x ≤ 2  required # of sub frames = 2
 100  2 < x ≤ 3  required # of sub frames = 3
UE
3 < x ≤ 5  required # of sub frames = 5
pcoll - maximum collision probability [%] 5<x  required # of sub frames = 10
For internal use

RACH density based on: 3GPP TSG-RAN WG2 LTE: Random Access Collision Probability and Load Estimates Fig. Example of RACH density calculation
Technical Details – Where PRACH is placed on the grid? Main
Table of Menu
Contents
Where PRACH is placed in frequency domain:

• PRACH could be placed either on lower or upper edge of the bandwidth
• Due to this possible range for prachFreqOffset is:
0  nPRBoffset
RA
 NRB
UL
6
...
If PRACH area is placed at the lower border of UL frequency band then: PRACH
prachFreqOffset = roundup [maxPucchResourceSize /2] PUCCH
If PRACH area is placed at the upper border of the UL frequency band then:
prachFreqOffset = MAXNRB – 6 - roundup [maxPucchResourceSize /2] ...
The PRACH area (6 PRBs) should be next to PUCCH area either at upper or
freq
lower border of frequency band to maximize the PUSCH area but not
freq
overlap with PUCCH area
time time
For internal use
21 © Nokia Solutions andFig: LTE UL
Networks resource grids: 1.4 and 5 MHz
2013
Technical Details – Where PRACH is placed on the grid? Main
Table of Menu
Contents
Where PRACH is placed in frequency domain:

• as for prachFreqOffset the possible range is
0  nPRBoffset
RA
 NRB
UL
6
• and the PRACH area (6 PRBs) should be next to PUCCH area either at upper or lower border
of frequency band to maximize the PUSCH area but not overlap with PUCCH area
...
• The prachFreqOffset should be calculated based on PUCCH size i.e.maxPucchResourceSize
TOTAL _ NUM _ CCEs  deltaPucchShif  n1PucchAn  deltaPucchShift
maxPucchRe sourceSize  nCqiRb  roundup[ ]
3 12
where: PRACH next to
((maxNrSym Pdcch *12) - 4) * dlChBw - (roundup (phichRes 
dlChBw
) *12) - 16
the PUCCH
TOTAL _ NUM _ CCEs  rounddown ( 8 )
36
then:
maxPucchRe sourceSize
prachFreqO ffset  roundup ( )
2
freq
In RL50 ‘PRACH frequency offset’ parameter relation was updated based on LBT1835 CRL0962. time
Since RL50 PRACH
For internal useresource configuration will NOT allow to OVERLAP with PUCCH based on Fig: LTE UL resource grids 5 MHz
22
value for maxPucchResourceSize calculated by BTS © Nokia Solutions
Site Managerand Networks 2013
Technical Details – How to generate preamble? (1/2) Main
Table of Menu
Contents
The random access preambles are generated from: # root sequences = 838 in total
• Zadoff-Chu root sequences (838 in total) with zero correlation zone # preamble sequences = 64 per cell
• one or several sequences (length 839 each)
Zadoff–Chu sequence is known as a CAZAC sequence (Constant Amplitude Zero AutoCorrelation waveform).
There are 64 preambles sequences available in each cell. The set of 64 preamble sequences in a cell is found by
including first, in the order of increasing cyclic shift, all the available cyclic shifts of a root Zadoff-Chu sequence
Fig:
example of preambles
generation with zero
autocorrelation zone
length equal to 279
(prachCS=14)
Fig: Zadoff-Chu sequence. The real (upper) and imaginary
(lower) parts of the complex-valued output (Wikipedia)
Additional preamble sequences:

in case the 64 preambles cannot be generated from a single root Zadoff-Chu sequence, then remaining
preambles are obtained from the root sequences with the consecutive logical indexes until all the 64
sequences are found.
For internal use
Technical Details – How to generate preamble? (2/2) Main
Table of Menu
Contents
Zero correlation zone and Cyclic shift

• zero correlation zone existence in Zadoff-Chu sequence provides possibility to decode signals on PRACH even if
sent on the same shared resources: on the same frequency and in the same time.
• preamble signals generated based on two different ZC sequences are not correlated within the geographical range
related to prachCS (i.e. Cyclic Shift configuration index)
• the size of the cyclic shift, must be larger than the maximum round-trip delay, so is depending on cell
radius
Required number of different root Zadoff–Chu sequences grows with Ncs (Cyclic Shift) and the cell radius:
NCS value
prachCS Unrestricted Restricted
set set Limits due to preamble
premable formats
0 839 15
1 13 18
2 15 22
3 18 26
Recommended
4 22 32
5 26 38 for MICRO
6 32 46
7 38 55
8 46 68
9 59 82
10 76 100
11 93 128
12 119 158 Recommended
13 167 202
for MACRO
14 279 237 use
For internal
2415 419 - © Nokia Solutions and Networks 2013
Technical Details – rootSequenceIndex planning (1/4) Main
Table of Menu
Contents
PRACH Root Sequences and Cyclic Shifts

• 838 different root sequences available (PRACH Root Sequence)  rootSeqIndex (LNCEL)
• different cyclic shifts can be used depending on cell size  prachCS (LNCEL)
• 64 preambles made of Zadoff-Chu (Z-C) sequences with zero correlation zone:
• given by the logical index RACH_ROOT_SEQUENCE
• ZC sequence of length 839 (prime number) is used
General Root Sequence planning rule:

• Required number of different root Z-C sequences grows with prachCS i.e. with the cell radius
• Possible values for rootSeqIndex are all values which allow to have consecutive #rootseq-1 (# of required root sequences is taken
from prachCS) that are NOT USED by any neighbor (i.e. within reuse distance)
Example for normal planning case:
NCell 1: prachConfIndex = 3 / prachCs = 12 / rootseqIndex = 0  prachCs = 12 requires 10 root sequences
NCell 2: prachConfIndex = 3 / prachCs = 12 / rootseqIndex = 10  rootSeqIndex=10 selected based # of root sequences used by NCELL 1
SMALL NCell 3: prachConfIndex = 3 / prachCs = 4 / rootseqIndex = 20  rootSeqIndex=20 selected based on # of root sequences used by NCELL 1 & 2
CELLS NCell 4: prachConfIndex = 3 / prachCs = 4 / rootseqIndex = 22  rootSeqIndex=22 selected based on # of root sequences used by NCELL 1 … 3
NCell 5: prachConfIndex = 3 / prachCs = 12 / rootseqIndex = 24  rootSeqIndex=24 selected based on # of root sequences used by NCELL 1 … 4
… …
For internal use

25 rootseqIndex
© Nokia Solutions and Networksis2013
pointing first possible root sequence
(root sequences of Ncells should NOT overlap to avoid collisions)
Technical Details – rootSequenceIndex planning (2/4) Table of Contents
PRACH Root Sequences and Cyclic Shifts limitations for HetNet:

• Different cyclic shifts need to be used for MACRO and MICRO  prachCS depends on cell size
• Different REUSE DISTANCE should be applied for MACRO and MICRO
• Only 838 different root sequences available (PRACH Root Sequence)  limited resources
Root Sequence planning proposal for HetNet environment:
rootSeqIndex split into different POOLS for MACRO and MICRO layers
• Advantages:
• Improved maintaining of fast changing environment – no root sequence resources fragmentation:
• removed MICRO cell (with required 2 root sequences) cannot be easily replaced by MACRO cell (10 root sequences required)
– if neighboring root sequences are already occupied
• no gaps between occupied root sequences – NO RESOURCES FRAGMENTATION
• Easy NetAct Optimizer configuration and maintaining
• In optimizer there is an option to define different cell GROUPS/SETS  e.g. MACRO, MICRO
• rootSeqIndex pools could be applied as different forbidden sets of parameters for different sets MICRO/MICRO
• the range prachCS and expected cell range should be also limited with respect to the potential MAX cell range
• Disadvantages:
• No single resources multiplexing gain – one POOL root sequences cannot be used when other POOL is with lack of resources
(no option to configure collision free settings) - can be MINIMIZE with good pool size planning
For internal use
PRACH Root Sequences POOL and Cyclic Shifts for SMALL CELLS
• Dedicated pool of root sequences out of all 838 available different root sequences
• Dedicated cyclic shift can be used depending for small cells
• Reduced reuse distance for rootsequences
Root Sequence planning proposal for SMALL cells:

• The range for prachCS should be limited with respect to the potential MAX cell range
• rootSeqIndex pools can be defined separately for MACRO and MICRO layers
Example for MACRO and MICRO environment:
Dedicated rootSequenceIndex pool for MACRO layer: 0 up to 799 80 cells with ~15km range
Macro Cell 1: prachConfIndex = 3 / prachCs = 12 / rootseqIndex = 0  prachCS=12 requires 10 root sequences therefore …
Macro Cell 2: prachConfIndex = 3 / prachCs = 12 / rootseqIndex = 10  rootSeqIndex=10 selected based on Macro Cell 1 configs
Dedicated rootSequenceIndex pool for MICRO layer: 800 up to 837 19 cells with ~2km range
Micro Cell 1: prachConfIndex = 3 / prachCs = 4 / rootseqIndex = 800
Micro Cell 2: prachConfIndex = 3 / prachCs = 4 / rootseqIndex = 802  rootSeqIndex=802 selected based on MICRO CELL 1 configs
POOL
for MACRO layer
… …
For internal use
27 © Nokia Solutions and Networks 2013 POOL
for MICRO layer
Root Sequence planning proposal for HetNet enviorment:
rootSeqIndex split into different POOLS for MACRO and MICRO layers
• Simplified Root Sequences Pool size evaluation:
• one of possible way is to calculate the pool size as a SHARE of required resources for MICRO and MACRO out of ALL available
root sequences – within given reuse distance for given area
• Required ‘MICRO layer resources’ evaluation should base on:

• reuse distance MICRO cells – e.g. to be used in Optimizer
• estimated # of MICRO cells within the reuse distance  e.g. based on deployment strategy
• # of required root sequences per MICRO cell  based on prachCS for MICRO cells
• Required ‘MACRO layer resources’ evaluation should base on:

• reuse distance for MACRO
• estimated # of MACRO cells within the reuse distance  e.g. based on deployment strategy
• # of required root sequences per MACRO cell based on prachCS for MACRO cells
if TOTAL # of required resources for ‘MACRO and MICRO’ is lower than # of ALL (by default 838) available root sequences:
Pool Size (micro)= MICRO layer resources
else:
Pool Size (micro) = roundup [( MICRO layer resources / ‘MICRO + MACRO resources’ ) * # of available seq.]
Example 1: MACRO layer requires 600 root sequences to provide collision free allocations within reuse distance. For MICRO layer 100 root sequences. 700 sequences required in TOTAL. Based
on the 1st equation 100 root sequences should be sufficient for micro layer pool to allocate collision free resources.
Example 2: MACRO layer For requires

internal 800
useroot sequences when for MICRO 250 root sequences are required. The # of 1050 root sequences to be allocated in total is higher than all 838 available root
28
sequences therefore based on the 2nd equation  MIN (250, 200) root sequences in micro layer  pool© Nokia Solutions
size for micro isand Networks
equal to 200. 2013
Note: probably no collision free allocation within original
reuse distance will be possible, further iterations with limited reuse distance then will be used.
Technical Details - PRACH planning rules Main
Table of Menu
Contents
Planning rules for PRACH parameters:

Define the prachConfIndex
• Depends on preamble format (RACH density and cell range)
• It should be the same for each cell of the site
• SMALL CELL should use the same prachConfIndex as overlaid MACRO to avoid PUSCH/PRACH interference
Define the prachFreqOff
• depends on the PUCCH area
• It can be assumed to be the same for all cells for the network within the given area (i.e. with the same traffic and PUCCH area)
• SMALL CELL should use the same prachFreqOff as overlaid MACRO to avoid PUSCH/PRACH interference
Define the prachCS
• Depends on the cell range
• If for simplicity same cell range is assumed for all network then prachCS is the same for all cells
• SMALL CELL can have limited prachCS due to limited cell range (lower output power)
Define the rootSeqIndex
• It points to the first root sequence out of all required based on prachCS
• It needs to be different for neighboring cells within the reuse distance
• rootSeqIndex separation between cells depends on how many root sequences are required per cell (depends on PrachCS)
• dedicated pools of the root sequences could be defined for MACRO and MICRO in HetNet environment
• unwanted resources fragmentation of macro layer by small cells can be avoided
• Improved network maintenance especially for fast changing small cells environment
For internal use
Technical Details - PRACH planning rules SUMMARY Main
Table of Menu
Contents
Parameters setting and planning rules for dedicated and HetNet scenarios. SUMMARY:
Parameter settings
prachConfIndex prachFreqOff prachCS rootSeqIndex
Use case
All allowed. All allowed.
All allowed. All not used in ADJ cell.
Macro layer ONLY Same for each cell
Same in the given Same in the given
Different for neighbor
(dedicated frequency) network area (wrt. network area (e.g. wrt
of the site cells
PUCCH) cell range)
All allowed. Range limited due
All not used in ADJ cell.
Micro layer ONLY Format 0 only. Same in the given to cell size.
Different for neighbor
(dedicated frequency) Same for the layer. network area (wrt. To Same in the given
cells
PUCCH) network area.
All not used in ADJ cell.
All allowed. All allowed.
All allowed. Different for neighbor
MACRO in HetNet case Same for each cell
Same in the given Same in the given
cells. Possible MACRO
(Macro/Micro in the same frequency layer) network area (wrt. network area (e.g. wrt
of the site. dedicated pool of root
PUCCH) cell range)
sequences
All allowed.
Format 0 only. All not used in ADJ cell.
Same in the given Range limited due
Same for the layer. Different for neighbor
MICRO in HetNEt case Same as a overlaid
network area (wrt. to to cell size.
cells. Possible MICRO
(Macro/Micro in the same frequency layer) PUCCH). Same as a Same in the given
For internal use MACRO if dedicated pool of root
30 MBB CS Network Engineering/ Adam Pomykala MACRO©(if possible,
Nokia Solutions i.e.
and Networksnetwork
2013 area.
possible. sequences
same PUCCH size).
Technical Details - PRACH planning process in LTE581 and LTE962 Main
Table of Menu
Contents
PRACH Management configuration process BASICS:

• generate PRACH Config Set A based on own cell data (configuration)
• out of PRACH Config Set A generate Config Set B by aligning configuration data with surrounding cells
• if more than one possible set is available select the one with the highest PRIORITY (weights)
Two parameter sets A and B are defined stepwise:
• Step 1: checking of all allowed values for OWN cell

- set A is created – lists of possible:
• PRACH configuration index (LNCEL:prachConfIndex)
• PRACH frequency offset (LNCEL:prachFreqOff)
• PRACH cyclic shift (LNCEL:prachCS)
• PRACH Root sequence (LNCEL:rootSeqIndex)
• Step 2: Parameters set A is limited by neighboring

cells (if any) parameters – set B is created
• Step 3: Based on the parameter set B content the

best PRACH configuration settings are chosen for
the given cell
For internal use
Technical Details - „PRACH config set A” configuration process Main
Table of Menu
Contents
PRACH config set A:

contains all possible settings for OWN cell
Selection of Preamble Format:

• customer input (in case of NO input default value is used): Output:
• High speed flag (default: false)
• Preamble format 4 (default: NO i.e. FDD system) • Adjusted ECR
• Increased Path Loss (default: NO) • Average Inter-site distance (AISD)
• ECR: Expected Cell Range (default: 14.5 km as limit for format 0) • Preamble format
• forbidden preamble list that the operator would like to restrict (e.g. no licences)
• own cell parameter: CyclicPrefix (FDD/TDD), TDD frame and subframe configuration (TDD)
• as sub process based on eNB geolocation AISD and adjusted ECR is calculated
Selection of PRACH configuration Index

• customer input (in case of NO input default value is used): Output:
• RACH density (default:1)
• UL channel bandwidth (DB parameter): if 1.4 MHz RACH density=1 allowed only • PrachConfIndex
• PRACH conf index forbidden list (e.g. international coordination)
For internal use

Technical Details - „PRACH config set A” configuration process Main
Table of Menu
Contents
Selection of possible PRACH Frequency Offsets Output:

• PUCCH related configuration (DB parameters) to calculate required
capacity for PUCCH
• Channel Bandwidth (DB parameter)  both PUCCH area and Channel • required number of PRBs for PUCCH
Bandwidth are used to calculate possible Frequency Offsets set • possible PRACH frequency offsets
• Lower or upper edge of bandwidth as input
Selection of PRACH Cyclic Shift and RACH Root Sequence

• ECR Expected cell range (also required for Preamble Conf Index)
• High speed flag (default: false) Output:
•NCS config (prachCS)

• number of required root sequences
• possible value of rootSequenceIndex
For internal use

Technical Details - „PRACH config set B” configuration process Main
Table of Menu
Contents
PRACH config set B:

contains all possible settings for OWN cell with respect to the neighboring cells
Following attributes for the neighbor cells under evaluation:

• geo-location
• PRACH Configuration Index: prachConfIndex
• PRACH Frequency Offset: prachFreqOff
• RACH Root Sequence: rootSeqIndex
• PRACH Cyclic Shift: prachCS PRA
C H reu
se D
istan
ce
• High speed Flag: prachHsFlag

Cell under
configuration
Optional switches for this process:

• enable time domain differentiation for PRACH configuration
• enable frequency domain differentiation for PRACH configuration
• If frequency domain differentiation is disabled then operator input is
required as selection of PRACH allocation on lower or on upper edge eNB which belongs to the cell
under configuration
• to be used e.g. if no collision free resources are found with given iteration eNB outside PRACH reuse
distance
Cells considered as neighbor cells for PRACH planning
Cells not considered as neighbor cells for PRACH planning

eNB within PRACH reuse
distance
PRACH config set A as input, if no neighboring cells is set as PRACH config set B
For internal use
Technical Details - „PRACH config set B” configuration process Main
Table of Menu
Contents
PRACH config set B:

• can contain more than one parameter set
• priorities are used
Priorities for multiple content in set B

• Priority selection for prachConfIndex
• lowest prachConfIndex value  highest priority
• highest prachConfIndex value  lowest priority
ce
istan
se D
C H reu
PRA
• Selection of prachFreqOff if frequency differentiation is enabled then select

Cell under
configuration
• prachFreqOff = prachFreqOff1 (lower edge) for cells with mod2(phyCellId) = 0

• prachFreqOff = prachFreqOff2 (upper edge) for cells with mod2(phyCellId) = 1
• Selection & priority selection for rootSeqIndex

• take into account frequency offsets for all neighboring cells
eNB which belongs to the cell
under configuration
eNB outside PRACH reuse Cells considered as neighbor cells for PRACH planning
distance
Cells not considered as neighbor cells for PRACH planning
eNB within PRACH reuse
distance
For internal use

Technical Details – neighboring cell collsion finding Main
Table of Menu
Contents
Neighbor finding strategy for LTE962:
In RL30 the LTE 581 PRACH algorithm identifies neighbor cells (NC) of the Cell A based on the following criteria
1. Neighboring LTE cell is within reuse distance of Cell A and
2. EARFCNUL NC = EARFCNUL Cell A and
3. ULCHBW NC = ULCHBW Cell A and
4. Frequency Offset FO Nc in range FO Cell A ± 5 where, Frequency Offset  Index of 1st PRB of PRACH Resource.
Note : Criterion 4 checks if the PRACH resources of Cell A and NC are overlapping in Frequency domain
In RL50 the new algorithm is implemented in both LTE581 and LTE962 to identify neighboring cells:
• cell A, find the First (SF) and Last (LF) sub carrier frequency of PRACH resource
• for NC, find the First (SF) and Last (LF) sub carrier frequency of PRACH resource
Using the above data, we can easily identify if the PRACH resources of Cell A and NC are overlapping in Frequency Domain
For internal use

Table of Contents



Benefits and Gains


For internal use
Interdependencies Main
Table of Menu
Contents
There should be some impact, LTE xxx

but there is not impact in fact Potentially
impacted feature
name
The main feature limits
LTE xxx the limiting feature LTE xxx
Limiting feature Impacted feature
name Minor impact on the main
Running both features at the feature, e.g. in some very name
same time is problematic specific/rare scenarios
The limiting feature limits
the main feature
LTE720: SON LTE BTS

‘main feature supports Auto Configuration
‘supporting feature, e.g. gives
extra benefits/gains LTE 962
RACH Optimization The feature is prerequisite for the main feature
Both features
complement each other
to boost gains/benefits Both features must be
LTE xxx activated together
LTE581
Supporting feature ‘supporting feature’ supports PRACH management
name the main feature, e.g. gives
The main feature is prerequisite
extra benefits/gains
For internal use

Table of Contents



Benefits and Gains


For internal use
Benefits and Gains Main
Table of Menu
Contents
With incorrect configuration of the PRACH parameters it is possible to observe:

 Collisions: PRACH settings (within the reuse distance) among neighbors and inside the site (e.g. Distributed Antenna
System) that are colliding, which results in... decreased PRACH detection probability.
 Inconsistencies: PRACH related parameters not in line with other own cell parameters, provide interferences to cells
and physical channels. It results in decreased overall performance for RA and other procedures.
 Due to removing Collisions and Inconsistencies the general system accessibility can be improved:
 Increased PRACH detection probability
 Improved overall performance for Random Access and other procedures
What to observe? Please refer to the ‘Performance Aspects’ section

For internal use
Table of Contents



Benefits and Gains


For internal use
Configuration Management Main
Table of Menu
Contents
Definition of terms and rules for parameter classification
- The ‘Basic Parameters’ category contains primary parameters which should be considered during cell deployment and must be
adjusted to a particular scenario. These are:
- Network Element (NE) identifiers
- Planning parameters, e.g. neighbour definitions, frequency, scrambling codes, PCI, RA preambles
- Parameters that are the outcome from dimensioning, i.e. basic parameters defining amount of resources
- Basic parameters activating basic functionalities, e.g. power control, admission control, handovers
- Parameters defining operators’ strategy, e.g. traffic steering, thresholds for power control, handovers, cell reselections, basic
parameters defining feature behaviour
- The ‘Advanced Parameters’ category contains the parameters for network optimisation and fine tuning:
- Decent network performance should be achieved without tuning these parameters
- Universal defaults ensuring decent network performance need to be defined for all parameters of this category. If this is not possible for
a given parameter it must be put to the ‘Basic Parameters’ category
- Parameters requiring detailed system knowledge and broad experience unless rules for the ‘Basic Parameters’ category are violated
- All parameters (even without defaults) related to advanced and very complex features
Purpose: Categories of parameters have been defined to simplify network parameterization. Parameterization effort shall be focused
mainly on parameters included in basic category.
Categorization will be reflected in a ‘view’ definition in NetAct CM Editor (planned in RL60) i.e. parameters will be displayed according
For internal use
42
to the category: either in the ‘Basic parameters’ view or the ‘Advanced
MBB CS Network Engineering/ Adam Pomykala
parameters’ view.
© Nokia Solutions and Networks 2013
Table of Menu
Contents
• Radio parameters modifiable by LTE962

prachConfIndex PRACH configuration index
Object: LNCEL Defines allowed system frame and subframe, numbers for random access attempts,
and the preamble format.
Range: 3...24 (3…8 for FZM)
Step: 1
Parameter prachConfIndex is indicating preamble format and when - in time
Default: 3 domain - preamble transmission can occur.
Multiplicity: 1
Unit: - For a cell with bandwidth 1.4 MHz the following prachConfIndex values are
recommended dependent on the physical cell id (PCI):
Category: BASIC
-PCI modulo 3 = 0 => prachConfIndex = 3 (PRACH format 0) or 19 (PRACH format
1) i.e. PRACH occasion is within TTI 1
-- PCI modulo 3 = 1 => prachConfIndex = 4 (PRACH format 0) or 20 (PRACH
format 1) i.e. PRACH occasion is within TTI 4
-- PCI modulo 3 = 2 => prachConfIndex = 5 (PRACH format 0) or 21 (PRACH
format 1) i.e. PRACH occasion is within TTI 7
Note: Parameter range is limited to the preamble format 0 for FlexiZone Micro
For internal use

Table of Menu
Contents

prachCS PRACH cyclic shift
Object: LNCEL Preamble cyclic shift defines the configuration which is used for preamble
generation.
Range: 0...15
Step: 1
The configuration determines how many cyclic shifts are needed to generate
Default: 12 preamble. Unrestricted set is supported. Configuration also defines the zero
Multiplicity: 1 correlation zone and respective maximum cell range
Unit: -
Note: Parameter range should be limited to the range 1…12 for FlexiZone Micro as
Category: BASIC preamble format 0 is only supported.
Recommended value for FZM is prachCS = 4 (cell range ~2 km)
For internal use

Table of Menu
Contents

prachFreqOff PRACH frequency offset
Object: LNCEL Defines the location in frequency for the PRACH transmissions.
Range: 0...94 For UL scheduling its recommended that PRACH is located next to PUCCH either
on the lower or upper edge of the bandwidth because UL PRB allocation for UE
Step: 1 consist of consecutive PRBs.
Default: - If there is a small gap between PUCCH and PRACH PRBs, UL scheduler cannot
Multiplicity: 1 utilize those PRBs effectively.
prachFreqOffset for each bandwidth should be set aligned with the parameters
Unit: - determining the number of PRBs for PUCCH, so that PRACH is located next to
Category: BASIC PUCCH.
For internal use

Table of Menu
Contents

rootSeqIndex RACH root sequence
Object: LNCEL The preamble generation is started from the Root Sequence which is pointed by the
logical root sequence number.
Range: 0...837
RACH root sequence is cell specific information and neighboring cells should have a
Step: 1 different value.
Default: - RACH root sequence is transmitted in system information.
Multiplicity: 1
There are 64 preambles available in each cell. The set of 64 preamble sequences in
Unit: -
a cell is found by including first, in the order of increasing cyclic shift, all the
Category: BASIC available cyclic shifts of a root Zadoff-Chu sequence
Additional preamble sequences: in case 64 preambles cannot be generated from a
single root Zadoff-Chu sequence, then they are obtained from the root sequence
with the next consecutive logical indexes until all the 64 sequences are found.
Note: Required number of different root Zadoff–Chu sequences grows with the cell
radius
For internal use

Table of Contents



Benefits and Gains


For internal use
Deployment Aspects Main
Table of Menu
Contents
Preconditions for PRACH optimization process:

• eNB: parameters structure as PDDB
• Configurator: to have actual DB (including site and antenna data)
• Optimizer:
• Actual NW configuration
• Preferences set
• Licence available and active
Where to start?
• CM Operations manager:
• via the Work Flow Engine (WFE) SON Operations manually (for Site Autoconfiguration)
• Command line interface:
• racclimx.sh of NetAct Configuration to invoke work flow engine SON Operations manually or
scheduled racclimx.sh
• Optimizer User Interface:
• RACH Optimization tool available as part of Optimizer client and can be triggered manually
For internal use

Table of Menu
Contents
LTE962 RACH Optimization Manual trigger only

• It was planned to have automatically triggered SON operations … already in RL50
• … but according to the CRL0994 the requested functionality of LTE962 can be implemented in 2 steps from
Optimizer with respect to the way of execution (manual/time scheduled).
STEP 1: The following functionality is included in RL50:

• RACH Optimization by collision and inconsistency resolution: Manual Trigger
- Using NetAct Optimizer UI – Manual
STEP 2: Following functionality planned be included with NetAct8, RL60, included by Operations on Demand (OOD):
• RACH Optimization by collision and inconsistency resolution: Manual Trigger
- Using Configurator Workflow Engine – Manual
• RACH Optimization by collision and inconsistency resolution: Automatic Trigger
- Using Configurator SON Scheduler – Automatic and Semi Automatic
For internal use

Deployment Aspects – process flow Main
Table of Menu
Contents
Optimizer
Trigger RACH RACH optimization:

Optimization via Collision and Inconsistency
Optimizer client detection & resolutions
Configurator
Results visualization
RACH Optimization Plan in Optimizer user
interface:
Optimizer RACH
Plan validation Optimization tool
eNB
eNB operation with
Configuration activation &
eNB configurations optimized PRACH
reset
settings
For internal use

Table of Menu
Contents
NetAct main page

1 2
Access to WFE Access to OPTIMIZER
1’
2’
For internal use

Table of Menu
Contents
Basic Optimizer GUI view:
• Navigator:
• Network Elements (NE) structured in tree
• Could be used for NE selection
• Cell Groups and Scopes

• containing predefined groups or scopes for
selected cells
• Cell groups/scopes can be modified
• New cell groups/scopes can be created
• Map
• Used to visualize geo location for selected
sites/cells
• Whole SCOPE/GROUP can be visualized
at one go
PRACH management is available:

• under TOOLS  ‘PRACH management’
52
• whenever
For internal use
CELLs selected from Navigator,© Cell Group/Scope or from Map
Nokia Solutions and Networks 2013
Table of Menu
Contents
Start with NetAct Optimizer: optimization area 5 Pop-up window
Select from
the map: What
to optimize?
1 2 Proceed …
6
Select 7
network
element …
6’
3
1’
… or display
on the map the
GROUP or the
SCOPE
For internal use

4
Table of Menu
Contents
RACH optimization: SETTINGS for the selected cells under optimization area
CONFIGURATION and RESULTS storage
PRACH optimization operations
FIXED or RELATIVE reuse distance
Is network synchronized?
Lower or upper edge allocations
If to use TIME and FREQUENCY

differentiation?
For internal use

Table of Menu
Contents
Cell groups and Cell scopes creation in Optimizer

Use existing group to define SCOPE
6 List to browser (optional)
2 Select technology
Set filters (values) 3

1 Create and saveSCOPE
Create cell 7 e.g. select eNB from the
group… group (optional)
4 Give the group name
7’
5 Set new GROUP

Cell groups and scopes
For internal use are usefull for
55
MACRO and MICRO cells differentiation © Nokia Solutions and Networks 2013
Table of Menu
Contents
PRACH optimization: ALLOCATIONS and forbidden profiles
1 Edit/Add FORBIDEN profiles
3 EDIT forbiden profile
Assign forbiden profiles

2
Add GLOBAL or CELL level

forbidden profile
Since RL30 only global forbidden sets was considered during

PRACH allocation
With new RL50 implementation

For internal useis considering both GLOBAL
56 and CELL level forbidden sets during PRACH Allocation © Nokia Solutions and Networks 2013
Table of Menu
Contents
PRACH optimization: PRACH reuse distance options
1 Reuse distance preferences
2 Fixed reuse distance settings

3 Relative reuse distance settings
4 Select most suitable option
For internal use

Table of Menu
Contents
RACH optimization: checking the CONFLICTS and INCONSISTENCES

Start CONFLICTS and INCONSISTENCIES detection
1 (ONLY detection no conflict resolution)
2 List the CONFLICTS and INCONSISTENCIES
CONFLICTS and INCONSISTENCIES can be showed

3 on the map
For internal use

Table of Menu
Contents
PRACH optimization: triggering PRACH configuration
1 Start PRACH configuration
2 Check the results
3 Save the plan (will be visible in CONFIGURATOR)
For internal use

Table of Menu
Contents
PRACH optimization: PRACH managment SETTINGS for AUTOCONFIGURATION PROCESS
1 Start WFE in CM Operations Manager
2 Drag and drop Network Element
3 Select Autoconfiguration operation
Start Autoconfiguration process

4
For internal use

60 PRACH Management/Optimization is a part of Solutions
© Nokia basic and
licence
Networks of
2013LTE optimizer
Table of Menu
Contents
PRACH optimization: PRACH management SETTINGS for AUTOCONFIGURATION PROCESS
Select preferences
1
3 Use preferences for PRACH

2 management
Include PRACH management

for Autoconfiguration process
4 Use Reuse distance preferences for

PRACH management
For internal use
Table of Menu
Contents
PRACH optimization process duration

• Expected time for PRACH conflict detection and resolution is as below based on the number of cells:
- 2 000 cells should be checked for conflicts, PRACH re-configuration in:
15 minutes
45 to 60 minutes
1.5 hours to 2 hours
For internal use

Table of Contents



Benefits and Gains


For internal use
Performance Aspects Main
Table of Menu
Contents
• Feature monitoring based on RACH Setup Completion Success Rate

KPI /Counter ID KPI Name Short Info
Ratio between the number of RACH setup completions and the number of all RACH
Attempts.
 RACH_STP_C OMPLETIONS 
RACH Stp Comp Succ Rate    *100%
LTE_5569a E-UTRAN RACH Setup Completion Success Rate  RACH_STP_A TT 
Where RACH_STP_ATT is sum of RACH_STP_ATT_SMALL_MSG, RACH_STP_ATT_LARGE_MSG and
RACH_STP_ATT_DEDICATED.
NetAct (Reporting Suite) name: STP SR
RACH setup attempts for dedicated preambles
M8001C286 RACH setup attempts for dedicated preambles NetAct name: RACH_STP_ATT_DEDICATED
Updated: The reception of a dedicated RA preamble sent by the UE to the eNB.
RACH setup attempts for small size messages (only contention based).
M8001C6 RACH setup attempts for small size messages NetAct name: RACH_STP_ATT_SMALL_MSG
Updated: The reception of an RA preamble group A sent by the UE to the eNB.
RACH setup attempts for large size messages (only contention based).
M8001C7 RACH setup attempts for large size messages NetAct name: RACH_STP_ATT_LARGE_MSG
Updated: The reception of an RA preamble group B sent by the UE to the eNB.
The number of RACH setup completions (contention based and dedicated preambles).
M8001C8 RACH setup completions NetAct name: RACH_STP_COMPLETIONS
Updated: The transmission of a RA preamble response sent by the eNB to the UE.
For internal use

Table of Menu
Contents
• Feature monitoring based on Complete RACH Setup Success Rate

Ratio between the number of connection setup ATTEMPTS (Msg3) and the number of
contention based RACH Attempts. Complete RACH Setup Success Rate is given by:
 RRC_CON_RE _ESTAB_ATT 
 
 + SIGN_CONN_ESTAB_ATT_ MO_S 
 + SIGN_CONN_ESTAB_ATT_ MT 
 
 + SIGN_CONN_ESTAB_ATT_ MO_D 
 + SIGN_CONN_ESTAB_ATT_ OTHERS 
 
LTE_1056b Complete RACH Setup Success Rate  + SIGN_CONN_ESTAB_ATT_ EMG 
RACH Stp Comp Succ Rate    *100%
 RACH_STP_A TT_SMALL_M SG 
 + RACH_STP_A TT_LARGE_M SG 
 
 
 
 
 
 
 
NetAct (RS) name: COMPLETE STP SR
For KPI DENOMINATOR

For internal use related counters see previous slide For KPI NUMERATOR related counters see next slide
Table of Menu
Contents
• Feature monitoring based on Complete RACH Setup Success Rate

The number of Signaling Connection Establishment attempts for mobile originated signaling.
Signaling Connection Establishment attempts due From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED has started.
M8013C17
to MO-Signaling NetAct name: SIGN_CONN_ESTAB_ATT_MO_S
Updated: reception of an RRC Connection Request message sent by the UE to eNB
The number of Signaling Connection Establishment attempts for mobile terminated connections.
Signaling Connection Establishment attempts due From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.
M8013C18
to MT-Access NetAct name: SIGN_CONN_ESTAB_ATT_MT
The number of Signaling Connection Establishment attempts for mobile originated data
connections. From UE's point of view, the transition from ECM-IDLE to ECM-CONNECTED is
Signaling Connection Establishment attempts due
M8013C19 started.
to MO-Data NetAct name: SIGN_CONN_ESTAB_ATT_MO_D
The number of Signaling Connection Establishment attempts due to other reasons. From UE's
Signaling Connection Establishment attempts due point of view, the transition from ECM-IDLE to ECM-CONNECTED is started.
M8013C20
to others NetAct name: SIGN_CONN_ESTAB_ATT_OTHERS
Updated: reception of an RRC Connection Request message sent by the UE to eNB.
Number of Signaling Connection Establishment attempts for emergency calls.
Number of Signaling Connection Establishment NetAct name: SIGN_CONN_ESTAB_ATT_EMG
M8013C21
attempts for emergency calls Updated: Reception of the RRC: RRCConnectionRequest message (eNB <- UE) in case that
this message contains the EstablishmentCause set to emergency.
Number of RRC Connection Re-establishment attempts
Number
For of use
internal RRC Connection Re-establishment
M8008C4 NetAct name: RRC_CON_RE_ESTAB_ATT
66 attempts © Nokiaof
Updated: reception Solutions
an RRC:and Networks 2013
RRCConnectionReestablishmentRequest message from the UE
Main
Table of Menu
Contents
Thank you.
For internal use


RL50 RACH Optimization

Uploaded by

Copyright:

Available Formats

RL50 RACH Optimization

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

RL50 RACH Optimization

Uploaded by

Copyright:

Available Formats

What is the purpose of RACH optimization?

What is the purpose of RACH optimization?

What parameters can be differentiated for PRACH?

What parameters can be differentiated for PRACH?

NEI RACH Optimization

RL50/RL50FZ – LTE962 RACH Optimization

Introduction Configuration Management

Technical Details Deployment Aspects

Interdependencies Performance Aspects

Benefits and Gains

NEI Contact: Adam Pomykala

Introduction Configuration Management

Technical Details Deployment Aspects

Interdependencies Performance Aspects

Benefits and Gains

NEI Contact: Adam Pomykala

• RACH - Random Access Channel, is an uplink transport channel where

• PRACH - Physical Random Access CHannel.

• Differentiation of PRACH can be done in:

• Since RL50 NetAct gives possibility to configure PRACH related parameters:

For internal use

LTE 962 ‘RACH optimization’ scope:

For internal use

PRACH management feature in Optimizer 3.0 CD 3

RACH Optimization can be executed by manual trigger from Optimizer

LTE581 PRACH Management in RL30:

• Process is based on pre-planning information: from NetAct plan file or

• The algorithm uses dedicated information as INPUT:

Process is embedded into the LTE720 auto-configuration frame work.

For internal use

LTE581 PRACH Management related IMPROVEMENTS in RL50:

LTE581 in RL50 has the same approach as in RL30 in area of:

but with the modifications/extensions in RL50:

• LTE581 improvements common with LTE962

• Improvements applied Only for LTE581 for auto-configuration process:

For internal use

LTE962 RACH Optimization introduction in RL50:

LTE962 can be used for network settings verification if:

• Some of eNodeBs were manually configured (i.e. without LTE581)

For internal use

• LTE962/LTE381 with extensions to support HetNet

For internal use

Introduction Configuration Management

Technical Details Deployment Aspects

Interdependencies Performance Aspects

Benefits and Gains

NEI Contact: Adam Pomykala

Release/version RL50 LN5.0 OSS5.5 (Optimizer 3.2)

TD-LTE TD LTE release eNB NetAct

Release/version RL45TD LNT3.0 OSS5.5 (Optimizer 3.2)

Flexi Zone Micro FZM release eNB NetAct

Release/version RL50FZ LNFZ5.0 OSS5.5 (Optimizer 3.2)

HW & IOT HW requirements MME SAE GW UE

For internal use

1. Initial access from RRC_IDLE;

For internal use

• PRACH reserved PRBs cannot be used by PUSCH i.e. they

When UE can start Random Access Procedure:

PRACH configuration index for MACRO sites: