PRACH Demo for Eden-NET Live 2016-10-26

PRACH Optimization Eden-NET 16 SP2 •

Elina Järvelä

•

October 2016

1

© Nokia Solutions and Networks 2014

PRACH – LTE UL cont rol channel Primary Random Access Channel PRACH is used when UE needs to •

send new UL data

•

send control information

•

RACH setup failure rate

•

receive new DL data

•

Call setup failure rate

hand over from serving cell to target cell

•

Handover failure rate

•

•

2

Non-optimized PRACH settings lead to increased

transit from RRC_IDLE to RRC Connected state


PRACH Parameter Plann ing Primary Random Access Channel s r e t e m a r a P

PRACH configuration is combination of four parameters •

Root Sequence Index (RSI) in Code domain

•

Frequency Offset (FO) in Frequency domain

•

Configuration Index (CI) in Time domain

•

Cyclic Shift (CS) in Code domain

UE should not receive simulaneously multiple PRACH from immediate neighbors with any of the n following conditions o i t Overlapping RSIs while PRACH being transmitted in same time and frequency g a d n i n Transmitted in overlapping time while similar code and frequency are used n e n Transmitted in overlapping frequency while similar code and time are used a m l m P o c e r In addition, the four PRACH parameters must not be inconsistent with one another •

•

•

3


PRACH Planning Challenges Challenges Challenges Manual planning of PRACH parameters is tedious and error prone Quick fine tuning of PRACH parameters to suit changing radio conditions is not feasible manually Improving RACH success rate •

•

•

4


Vendor support LTE PRACH module •

Nokia -

HetNet support utilizing Nokia eNB functionality: LTE2020 PRACH Management Optimization for HetNet •

5

Automatic calculation of expected cell range

•

HetNet neighbor identification

•

High speed UE flag

•

Huawei

•

Ericsson


Use cases LTE PRACH module •

•

•

Fresh allocation

change all

-

When hard to fix conflicts

-

When unable to find values for new cells

-

If RACH success rate it poor for an area

Conflict resolution

–

minimal changes

-

When new cells are on air and start serving

-

When minimal changes preferred

-

If individual cell has poor RACH success rate

Inconsistency resolution -

6

–

–

within one cell

When cell is having no conflicts but RACH success rate is poor


RSI FO CI PUCCH PUSCH

Use cases PRACH Module

Root Sequence Index Frequency Offset Configuration Index Physical Uplink Control Channel Physical Uplink Shared Channel

Fresh allocation

Conflict resolution

Inconsistency resolution

Allocation is re-planned for all selected cells

PRACH issues detected for

Detect PRACH parameter inconsistencies within a cell

− −

Option: HsFlag indicates if the cell serves high speed or low speed users

−

Cells on same site Cells within a reuse distance Cells with incoming or outgoing intra LTE neighbor relations, within or out of reuse distance

Checking: −

−

−

−

Option: FDD LTE cells also time synchronized

−

−

7


Global and forbidden values Unsupported or out of range values Overlap with PUCCH or masked PUSCH area (interference) Not adjacent to PUCCH area (inefficient utilization of physical resouce blocks, PRBs) Out of band FO (interference and loss of information) Not aligned parameters RSI, CI and FO

Policies LTE PRACH module •

•

•

Neighbor finding strategy -

Coverage overlap: Expected / Fixed cell range or Propagation path loss

-

Reuse distance: Fixed / Relative

Parameter planning -

RSI (code domain)

-

FO (frequency domain) - optionally planned

-

CI (time domain)

-

CS (code domain)

always planned

optionally planned –

optionally planned

Differentiation strategy -

8

–

–

Code domain and frequency and/or time domain


RSI FO CI CS

Root Sequence Index Frequency Offset Configuration Index Cyclic Shift

Key principl e & planning rule PRACH Module Key principle •

PRACH configuration must not be identical in the user defined neighborhood of a selected LTE cell

Planning rule •

•

•

9

First try to differentiate the PRACH by using Root Sequence Index (RSI) Then, if user has chosen one of both of the optional settings, try to differentiate cells based on Time and/or Frequency domain RSI is always planned, optional by user: FO, CI, CS


RSI FO CI CS

Root Sequence Index Frequency Offset Configuration Index Cyclic Shift

UI parameters 1/3 PRACH Module

Maintenance windo w

No change in HsFlag True False Fresh allocation Use case

Conflict resolution Inconsistency resolution

Modify necessary parameters Use manual selection 10



By expected cell range By fixed cell range By propagation path loss

Coverage overlap Neighbor finding strategy

Reuse distance

Fixed reuse distance

Relative reuse distance 11



Parameters planning

Differentiation strategy

Mod2(PCI) value Use PRFO forbidden list

Skip target cell Skip neighbor cell

Other settings

Open loop Closed loop 12


Back-end parameters – configuration.ini PRACH Module configuration.ini file contains the common settings used whenever PRACH module is run [Forbidden.Global] -

Forbidden or reserved PRACH configuration values

-

The module must not use any values from the reserved PRACH configuration groups for recommending new PRACH configuration

[FixedCellRange] #cellType_deploymentType (Range in km) = Value (km) -

Cell Type: Macro, Micro, Pico, Femto

-

Deployment Type: Urban, SubUrban, Rural

[PropagationPathLoss] #propagationPathLossSetting (Ranges) = Value

13

-

Cell type: Macro, Micro, Pico, Femto

-

Cell edge RSRP and UE antenna height © Nokia Solutions and Networks 2014

PRACH Demo for Eden-NET Live 2016-10-26

Recommend Documents