Criteria for Optimizing SSB Periodicity in 5G NR

Hell NR Experts.

What are the criteria for selecting the optimized value of SSB periodicity in 5G NR?

(5, 10, 20…)

If you keep it 20 msec it will be OK.

Others who tried 5 and 10 msec had problems.

Thanks!

Any problem in terms of service accessibilty ENDC for NSA deployement?

Check that there should be correct Anchor definitions.

IP must be correct for X2 links.

ENDC enabled and must be set with correct value.

No PCI conflict on 4G Anchor.

No overshoot Anchor dominance.

It can make an Accessibility issue for 5G.

Thanks!

But I mean if the SSB periodicity is not configured with the optimezd value, can it create an accessbility issue?

Depend on many factors:

5ms / 10ms setting for high mobility, dense traffic, mmWave bands, low latency.
20ms / 40ms for medium mobility, moderate traffic, sub-6GHz bands (like 2.5G TDD ot 3.7G C-Band), balance of efficiency and performance.

If the SSB periodicity is not optimized based on the specific deployment scenario (cell size, user mobility, traffic density, etc.), it can indeed create accessibility issues like connection delays, handover failures, frequent disconnections, and degraded user experience.

Depend on the clutter and traffic trending.

Can you please tell the significance of TDD pattern 2 why it’s needed?

When we have TDD pattern 1 there…

Check this:

Very informative!

It’s seen symbol per slot can vary too.

Like we have range from 0 to 13 to configure.

Any logic behind that to configure less symbols like 3, 4 per slot instead of 14?

I think is due to URLLC with minislot.

High periodicity of SSB add overheads, low periodicity will not ensure quality.

Rest all pros and cons discussed in previous messages.

It adds flexibility to customer for about how much resources to allocate to DL/UL/GP.

They have very well explained about the tdd slot configuration but still couldn’t find the ans for the use of pattern-2, what if network doesn’t configure pattern-2?

Fewer symbols can be used for low latency small data buffer aplications like URLLC.

Yes good point.

I think all UE support URLCC, eMBB mode in 5G as well mini slot…

No special reported capabilities for same by UE to network.

I am not sure about this.

Minislot is an Ericsson concept.

URLLC requires 10-12 dB in link budget constraint, so cells shrinks a lot.

Also on UE side not sure how many support it.

Ins’t it 3gpp defined?

I remember it’s for URLCC only.

What is the recommended value for NR SA deployment?

Will it create any impact for SA only?

20 msec and you will have no problems at all.

5 or 10 for dense urban and high mobility.

40 or 80 for rural and low mobility.

Just for fun: If no problem that means we are done. :stuck_out_tongue_winking_eye:

TDD Pattern 2 is needed to handle specific scenarios where Uplink traffic demand is higher (like AR Gaming, IoT, Stadiums where people uploading more than downloading) or more balanced with Downlink traffic, whereas TDD Pattern 1 is ideal for Downlink-heavy situations.

But how can you run some cells with a TDD configuration (for stadium) and rest of network with other TDD configuration (rest of network)?

Wouldn’t it be strong interference in overlapping area?

To run cells with different TDD configurations like inside a stadium vs. the rest of the network, interference can be managed by using guard periods and time alignment to prevent overlapping transmissions.

Leveraging geographical isolation (indoor vs. outdoor cells).

Using beamforming, directional antennas, and small cells to reduce interference.