PUSCH and Uppts interference

Yes in RACHCFG MO.

This is huge work network wide to analyse them one by one.

It is easier to take all cells with over 60-70 neighbors and implement 1 more degree tilt.
Although this is also risky as well.
Can generate coverage holes.

I use to do like this for accurate results will take time but result are fruitful.

Before adjusting ZCZC, we should look at TAs from where RACH attempts are coming. I think 15 KM is enough after downtiliting.

Yes and having cell radius 15 km network wide.
For 14 kn we can keep RACH format 0.

Yes no point in serving user from far, as it is bound to degrade other KPIs.

zeroCorrelationZone 12 .
This allows a reuse pattern of RSI of 83.
But there are cells with more than 83 neighbours all of them active.
So we need first to downtilt such cells first.
Reuse 83 is a difficult pattern for RSI plan. Is not easy.
You need a SON module for this.
Based on distance, angle, handover attempts and so on.

What is this reuse pattern?
Can you please elaborate? Sorry I don’t have idea.

For RSI planning generally we are using NCS then gap value between sectors per TAC it should not repeat.

I mean, if you use RSI 30 on a cell you can use RSI 40 on another cell RSI 60 in another cell.
So 839/10 = 83 RSIs value available network wide that you must reuse them.
For cells and neighbours.

Ok thanks got it :+1:.
For city site generally NCS 8.
For rural it’s 12.

That’s L.Ul.Interference.Avg.

How far do sites have to be for impact to be felt?
If sites are 30km away from a site with GPS alarm, can it have an impact?

The transmission distance of the GPS interference is greater than 2km based on the formula for calculating the transmission distance of the RFsignal based on the transmission distance of the RF signal.

Lbf=32.5+20lgF+20lgD

Lbf: free Space Loss (DB) , F: Frequency (MHz) ,D: Transmission distance (Km)

Huawei doesn’t define ZCZ ( Ncs) parameter explicitly unlike other OEM such as Samsung, instead it defines the Cell Radius.
The cell radius indicates the Ncs value and based on which RSI planning is done.

In Hedex you can find.
MO: RACHCfg
Parameter ID: ZeroCorrelationZoneConf

But I don’t see this parameter in RACHCONFG MO of OMSTAR.
I think Huawei does not define this parameter.
In Documentation both the Default value and Recommended values are set as None.

I also didn’t find it in XML dumps.

But if you check LTE logs from Huawei RAN there is zerocorrelationzoneconfig in SIB2.
So somehow must be set-up.

Guys, you can see zerocorrelationzoneconfig in DSP RACHCFG in Huawei.
It’s outcome parameter and it’s concluded base on your setting in RACHCFG MO, by setting prach config index and radius.

We cannot avoid standard parameter configuring to avoid to UE.
It is must. Based on that only UE can know how preambles will be generated.
So as per me, zczc is must required parameter to UE.
Doesn’t matter what vendor equipment.

It can vary vendor to vendor.