RRC Connection Release CCCH-unspecified

[kentck86]

Hi all,

Anyone can assists me on this please? I got a call attempt failure event due to RRC Connection Release CCCH cause-unspecified. RF condition and UL interference is normal, anyone experienced this?

thank you

[kentck86]

Hi All,

Here i added in screen capture for the failure event L3 signallings.

RRC_Connection_Release_CCCH.jpg

Anyone please enlighten me on the source of the failure cause please?

thank you

[boring]

i am not sure that this message was destined for your UE, but rather for a different UE which was listening at the same time the FACH channel.

from what i see from the trace the RRC connection was succesfully established (RRC connection setup complete), but the call was not setup due to the SERVICE_ABORT which was initiated by your UE.

makes sense?

[kentck86]

i am not sure that this message was destined for your UE, but rather for a different UE which was listening at the same time the FACH channel.

from what i see from the trace the RRC connection was succesfully established (RRC connection setup complete), but the call was not setup due to the SERVICE_ABORT which was initiated by your UE.

makes sense?

Hi,

i agree there were CM service abort, but as seen from the timing, RRC Connection release CCCH came before the CM service abort. Believe the cause if from the RRC Connection release.

[boring]

to prove my point, just check the UE reference of the messages: RRC connection request, RRC connection setup and RRC connection release

[kentck86]

Could you be more specific? How to check the UE reference base on those messages?

to prove my point, just check the UE reference of the messages: RRC connection request, RRC connection setup and RRC connection release

[boring]

Ok the UE reference is either TMSI, P-TMSI, or IMSI

in the screenshots here you can see that RRC request has the UE's TMSI (=2618809348), whereas its correspondings RRC setup has also the UE's TMSI

you could do the same check in your trace as well

hope this helps. reputation greatly appreciated!

RRC_request.jpgRRC_setup.jpg

[agenov]

how can you have command to release rrc in case of it hasnt been established yet (you are in the middle of RRC establishment procedure), obviously not possible. This is related to other user since UE still listen the common fach channel as other colleagues said. Focus on initiated by UE release in order to deal with the case.

BR
Alex

[kentck86]

Hi,

Please find the Capture TMSI infos as follows:
RRC_Connection_Request.jpg
RRC_Connection_Setup.jpg
RRC_Connection_Release.jpg

so,from your point, meaning that this is an event triggered by DT handling related issue, which is probably happens due to Abort was made by user or test device itself and it is non-network-related?

thank you

[boring]

yeap. this is totally correct

the CM_SERVICE_ABORT message was sent by UE (DT, technician etc)

and of course we remove this failed callsetup from the CSSR KPI