Nokia KPI for Tracking Timing Advance (TA) and Creating a Time-Distance Chart

Hello Nokia Experts.

Is there a KPI available for tracking timing advance (TA)?

I’d like to create a chart with time on the x-axis and distance on the y-axis.

Thank you!

For LTE, there is a counters like TimingAdvance, where you might have distributions or even average TA values.

You can plot it in Excel or if you have a Python skill so use the library.

If I am not wrong so it is mathplotlib.

Yes TA counter there.

You can use seaborn or mathplotlib to create plot for analysis, as menitoned.

I am not an expert in Nokia, but in Ericsson and Huawei you have several counters that indicate ranges of distances.

You would have to look up what those counters are called in Nokia.

So if you want to analyze overshooters, you should have ranges on the X-axis, for example, (0 to 500m), (500 to 1000m)…, and the number of samples on the Y-axis.

This way, you can see where your samples are concentrated and start optimizing.

Hello All: Thanks all for your anwsers

I’ve done it on Excel and got this result:

But I am looking for something like this:

My question is:
Is there an equation to get TA by combinig all these ranges ?

Follow TA Excel example (sample data), maybe you can ajust to your counters.

LTE TA.xlsx.zip (276.5 KB)

1 Like

Hello, Nokia 5G experts!

Does anyone have the distance equivalence for Timing Advance (TA) in the newer releases (5G22C onwards)?

Previously, before 5G22, the distance calculation was based on TA counters (M55307C01001…32) and the Subcarrier Spacing parameter (NRCELLGRP.scs). However, in the latest releases, the calculation now also includes the NRCELL.expectedCellSize parameter.

Can anyone confirm the updated formula or provide additional insights?

The bin size depends on the value of parameter NRBTS.NRPMRNL.NRPMCCP.cfgTAcounters

When NRBTS.NRPMRNL.NRPMCCP.cfgTAcounters =1, this counter indicates the range d (in m) from UE to the antenna depending on the value i of the counter EXP_CELL_SIZE_CFG:
i = 1: e = 78.07
i = 2: e = 156.14
i = 3: e = 312.28
i = 4: e = 468.43
i = 5: e = 936.85
i = 6: e = 1873.7
i = 7: e = 3122.84

0e <= d < 1e

When NRBTS.NRPMRNL.NRPMCCP.cfgTAcounters =0, this counter indicates the range d (in m) from UE to the antenna depending on the SCS configuration of the cell. The counter EXP_CELL_SIZE_CFG is reported with a special value of 99.

SCS=15kHz : s= 78.07
SCS=30kHz : s= 39.04
SCS=60kHz : s= 19.52
SCS=120kHz : s= 9.76
SCS=240kHz : s= 4.88

0s <= d < 8s

Thanks!

For the case where cfgTAcounters =1, could you confirm if EXP_CELL_SIZE_CFG is a counter or a parameter?

I found NRCELL.expectedCellSize parameter

Counter: M55307C03001 EXP_CELL_SIZE_CFG → Expected Cell Size Configuration

It might be a similar case to 4G, where the M8029C0 counter derives its value from the LNCEL.expectedCellSize parameter.

Yes …

So, do you think the values I entered for cfgTAcounters=1 in the chart are correct? (I filled them in a few minutes ago based on the information you provided.)

For your table with cfgTAcounters=1, the values are correct.

However, check your values when cfgTAcounters=0 (SCS).

When cfgTAcounters=0 (SCS), I took the values from a Nokia document. However, I didn’t find mathematical precision or logical consistency in the values shown in the table. Still, it was the only related document I found, so I tried to keep the information in this table.