Guys, did you knew that Huawei not only have 16 specific footprints for cell coverage in 5G (16 deployment scenarios) but also is able to fit for each of the 8 SSB beams a specific azimuth and tilt?
This is really something to point any SSB beam to the desired location. Of course, is a feature and is based on license but I wonder how many really use this feature?
How azimuth possible to be tune for ssb?
We have coverage only for ssb defined by left and right angle.
By changing beamforming weights any beam can be changed in azimuth and tilt.
Yes, we done it in mMIMO.
But not big impact.
For 5G fixed weights used as of now.
In Huawei it depends on what users chooses.
Once we have srs we can change weights.
@RFSpecialist, it’s available and we used it based on ACP recommendation.
As of now, NR ACP is based on Drive test data only and it will be based on MR data in future to get good gain by setting multiple scenarios in network based in clutter.
Can be fixed SSBs (default) or each SSB can have a different tilt and azimuth.
Also I have seen in several projects that people use default scenario for footprint of cell meaning zero optimisation on a cell by cell basis.
I mean why to use 105H16V in whole network when there are so many other options.
Like 45H25V.
Or many others.
Especially for tall buildings in cities.
Per ssb tilt sure, per cell seen option there.
We did many simulation as SSB Beams and Data beams are different so there should not be more offset in SSB coverage and PDSCH Beams.
We are using multiple scenarios in network based with 3D Beam forming license.
People tune parameters but they don’t look at cell’s footprint which is most important design of a cell.
Agree 
killing factor with beam concept.
The only problem with different azimuth and tilt per SSB is that gain is reduced.
Gain of AAU won’t be 30 dB anymore but maybe 26-27 dB.
Default tilt and azimuth of SSB ensure highest gain.
This different azimuth and tilt per ssb is based on user locations dynamically or its fixed value?
This is planning input.
SSB is having Fixed weight based on coverage scenario file while PDSCH is having diff weight based on PMI or SRS weight.
So there will be some gap if you use very different SSB coverage footprint scenario than default.
Agree!
Also I read that csi-rs beamform Huawei are available just for mmWave.
So how to minimize this gap?
So if traffic pattern or clutter got change then won’t it create accesibility issues?
There is a clear distinction between csi-rs reference signals and csi-rs beams.
Totally different concept.
Idea is don’t play with them unless you are clear what you are doing.