What preamble id in msg1?
Should be same in msg2.
RSRP is -82 so it’s good…
You could check MSG3 delta preamble to be sure.
PUSCH-ConfigCommon ::= SEQUENCE {
groupHoppingEnabledTransformPrecoding ENUMERATED {enabled} OPTIONAL,
pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList
msg3-DeltaPreamble INTEGER (-1..6)
p0-NominalWithGrant INTEGER (-202..24)
...
}
But i wouldn’t expect MSG3 failures under so good RF.
Here is the configuration of PUSCH.
I tried to put msg3-DeltaPreamble 4 instead of zero but it didnt affect.
I’m still having msg3 failure.
Will give you a practical (non scientific) feedback…
Seen it couple of time with one specific NW Vendor and issue was always solved by resetting gNB. Could you ask for a gNB reset? Your RSRP suggests you shouldn’t be struggling with UL TxPower.
Do you mean to change the msg3-deltaPreamble to 4 and then do a reset to gNB?
Just resetting the gNB could help.
Without touching offset.
I changed the msg3 delta to 4 and then did reset to gNB.
Not affect anything. 
You have UL CRC error.
In short, I wouldn’t play with preamble power, etc…
Most like a SW glitch on gNB or a mismatch between DCI config and what youre sending.
… Yes maybe.I think you have msg3 but with bad CRC on PUSCH.
Can you please paste here the content of msg2 like in this picture:
Also the content of msg3 as sent by UE?
Also check what’s the number of harq retransmissions for msg3: maxHarqMsg3Tx
Meantime some checking you can do: try with another UE, change the NRARFCN of the cell.
In my view
- Due to high pathloss gNB not able to decode msg 1.
- As msg 1 not able to decode properly, so msg 2 not received by UE.
msg3 is received, but with bad crc.
Yes crc nok, possibly we have msg3 harq retx parameter.
Hello dears,
Yesterday I was running into msg3 failure in 5G network. I did full reboot for gNB and it’s good.
I’m having success in msg3, and msg4 is also having success.
But the UE still not connected to 5G network - it fails.
This is because after msg4 success gNB sends msg19 which it’s CCH_MSG to UE and UE must ack to it in order to attach to 5G network.
The UE isn’t sending ack to gNB although it receieves msg19 from gNB.
Any help why UE isnt sending ack to gNB in response to msg19?
This is the last procedure of attaching to the network, once the UE sends ack in reponse to msg19 it will attach to the network but it fails for here in last step in sending ack.
It fails to send the ack to gnodeb where I drew an arrow in the photo.
What are MSG4 contents?
Good question. Will check but I have success in msg4.
So it will be efficient to check the contents?
You don’t know whats in Msg4.
May be gNodeB rejected or said something UE doesn’t like and so no Msg5 was sent.
But having success…
I mean, by msg19 in other words msg5 setup complete…
Is it for SA call flow?
Where did you find msg5 issue?