IE "tci-presentinDCI" in RRC Connection Reconfiguration Message

Ok. So Huawei does not transmit TCI-presentinDCI, Ericsson does not transmit TCI-presentinDCI.
Let’s wait for answers about Nokia and Samsung.

Yet there is no confirmation that this parameter decides whether beam switching in mobility is based on csi-rs beams or based on ssb beams.

Also in ShareTechNote, it seems more that those 2 parameters decide beam mobility type like explained by @Jaeku_Ryu: repetition and trs-info. In the example above it is matched to ssb beams. So we should all look in the logs for trs-info and repetition inside RRC connection reconfiguration message to add the scg cell to understand beam mobility type.

This log of TMO might help. It have this info:

This shows SSB usage for beam switching I guess.
tci-StateId ranges from 0 to 63 for mmWave and qcl-Type A,C & D is used

Currently X55 supports 32 TCI states and these can be used when you have aperiodic CSI.

I think the above log file is for X50 chipset S10 device.

Yes, might be.
But also if Network has not deployed aperiodic CSI it will use periodic CSI with 8 TCI states.

Sorry it’s 32 TRS and 64 TCI states.
S10 currently supports 4 TRS.

Yes that makes sense since 63 is corresponding to the SSB beams which is max 0-63 for mmwave and it is there in X50 chipset also.

Ok , last time I checked it was supporting 4TRS, may be SW got upgraded.

So you guys confirm that type of beams used for mobility (whether CSI-RS beams or SSB beams) it is determined by trs-info and repetition type?

That information is defined in CSI report config.
If Network configures UE to report SSB RSRP the it will use SSB to switch the beams, if it configures CSI RS then Network will use CSI RS for beam switch.
That info is there is L1 reports that UE sends.

Which IE precisely defines this?
Can you provide an example for type D QCL?

So you say it is not like explained on sharetechnote?

Im not sure about L1 information.
But from he above snap it is evident in the log file which I have that SSB beam is used.

But does this show information about QCL or TRS.
I havent seen so far.
MAC LL1 CSF Indication doesn’t have this.

I believe this table should be correct one.

But then why @samohiuddin is explaining something different?

May be he have some more clues. :slight_smile:

NR5G MAC LL1 CSF Indication

Chipset timestamp: 2020-03-18 18:12:11.918938, CFN : 94
Dual Mode Index : 1
SIM Index : 255
Version : 65537
Major.Minor Version : 1.1
log_fields_change
log_fields_change_bmask : 0x0000
sub_id : 0
num_records : 3
Records
Record[0]
report_ul_time
slot : 65
numerology : 120kHz
frame : 615
carrier_id : 0
report_id : 2
report_type : APERIODIC
num_bits_part1 : 35
num_bits_part2 : 0
is_rsrp : RSRP
num_bits_part2 : 0
debug_only : Result_from_WP
report_quanlity : RSRP , SSB_INDEX
resource1 : 5
resource2 : 2
resource3 : 4
resource4 : 1
resource_type : SSB
num_resource_bits : 4
pad : 0
rsrp1 : 59
rsrp2 : 59
rsrp3 : 58
rsrp4 : 51
valid_rsrp : 4
Record[1]
report_ul_time
slot : 65
numerology : 120kHz
frame : 615
carrier_id : 0
report_id : 0
report_type : APERIODIC
num_bits_part1 : 24
num_bits_part2 : 0
is_rsrp : RSRP
num_bits_part2 : 6
debug_only : Result_from_WP
report_quanlity : CRI , RSRP
resource1 : 0
resource2 : 1
resource3 : 2
resource4 : 0
resource_type : CSI_RS
num_resource_bits : 3
pad : 0
rsrp1 : 67
rsrp2 : 66
rsrp3 : 54
rsrp4 : 0
valid_rsrp : 3
Record[2]
report_ul_time
slot : 65
numerology : 120kHz
frame : 615
carrier_id : 0
report_id : 1
report_type : APERIODIC
num_bits_part1 : 24
num_bits_part2 : 0
is_rsrp : RSRP
num_bits_part2 : 6
debug_only : Result_from_WP
report_quanlity : CRI , RSRP
resource1 : 0
resource2 : 1
resource3 : 3
resource4 : 0
resource_type : CSI_RS
num_resource_bits : 3
pad : 0
rsrp1 : 72
rsrp2 : 59
rsrp3 : 53
rsrp4 : 0
valid_rsrp : 3

The above msg is the one which I referred for report quantity

Is it mobility or beam switching?

Beam mobility/switching
Beam HO aka Beam switching, right?

Beam mobility: change of beam between 2 cells.
Beam switching: change of beam between same cell ie from ssb 0 to ssb 1 for ex.

Please correct if above wrong…