RRC Release before Attach complete

[pongpang]

Hi Expert,

I found a bit strange from below picture, Why nw send "RRC Release" message before Attach complete??
and Actix count its to "Attach fail" (Aborted) event, Its occurred about 10 times/cluster.
Does anyone can explain or some suggestion?? :confused:

Thanks
PongpanG
31930

[scorpion]

Check the traces at SGSN side for the authentication procedures.....

But how comes there is a Attach Accept +Complete ?

[agenov]

What is the reason for RRC connection release?


Hi Expert,

I found a bit strange from below picture, Why nw send "RRC Release" message before Attach complete??
and Actix count its to "Attach fail" (Aborted) event, Its occurred about 10 times/cluster.
Does anyone can explain or some suggestion?? :confused:

Thanks
PongpanG
31930

[pongpang]

@Scorpion: for Attach accept+Attach complete, Is it normal??
@agenov: releaseCause: 0 ( normalEvent)

thanks,

[scorpion]

pongpang (http://www.finetopix.com/member.php?34064-pongpang),

Just for analysis I will forget about that RRC-Release you have observed, I agree it is an important KPI from Radio perspective..but
From Core point of view..the procedure looks normal...have you initiated a PDP post that what happens then ?

[agenov]

Have you tried to open the log file in the software u use to do measurements nemo,tems etc and see there how it looks like. To me it seems like actix issue.

br

[pongpang]

@Scorpion : Umm. Its not effect to user and can going to do PDP procedure , im just a bit wondering.
@agenov : I already tried to playback by TEMS, its same as actix

thanks,

[babak1349]

Hello,
Are you sure Actix is showing the order of messages correctly ? Based on shown image, the attach process has been completed. Can yuo check the time stamp in TEMS and see if the order of messages is ok I meant RRC Release comes BEFORE Attach Accept.
Anyway RRC carries NAS messages and if Attach Accept/ Attach complete come after RRC release, it wouldn't make any sense Because there is no RRC conection to carry NAS massages

So I think it would be TEMS or Actix failure in decoding the messages in proper order.


Best Regards




Hi Expert,

I found a bit strange from below picture, Why nw send "RRC Release" message before Attach complete??
and Actix count its to "Attach fail" (Aborted) event, Its occurred about 10 times/cluster.
Does anyone can explain or some suggestion?? :confused:

Thanks
PongpanG
31930

[babak1349]

Further Suggestion,
It is better to check SGSN counters in order to see the Attach failure causes If the attach failure rate is higher than 5% you should see the reasons and take further actions For example running traces in SGSN in order to collect the causes

Best Regards


Hi Expert,

I found a bit strange from below picture, Why nw send "RRC Release" message before Attach complete??
and Actix count its to "Attach fail" (Aborted) event, Its occurred about 10 times/cluster.
Does anyone can explain or some suggestion?? :confused:

Thanks
PongpanG
31930

[pongpang]

Hi babak1349
I thinks so,maybe TEMS or Actic falut..
my nw didnt on commercial launch, we cant get any statistics to monitor.

more question,
-can we check from RNC trace message(UE trace, ISO trace etc..)??
-can we get the "USIM class(class1-15)" from DT logfile or RNC trace message, if can which message??? (not relate the topic)

Thanks and sorry about grammar :p,

[babak1349]

Hi Buddy,
Yeah you can run trace on RNC, in E*******, you can run UETR ( IMSI based Traces for E******* ) and in the same time do the drive test and then you can compare the drive test with Traces
You can check the RRC connection release causes and and compare it with Traces. in Trace you can see RRC. NBAP Iu, Iur and internal measurement So easily you can confirm if the problem is due to DT tools
I believe it is related to DT tools' failure
Anyway the problem occurs in the end of log file or in the middle of log file?

BR


Hi babak1349
I thinks so,maybe TEMS or Actic falut..
my nw didnt on commercial launch, we cant get any statistics to monitor.

more question,
-can we check from RNC trace message(UE trace, ISO trace etc..)??
-can we get the "USIM class(class1-15)" from DT logfile or RNC trace message, if can which message??? (not relate the topic)

Thanks and sorry about grammar :p,

[babak1349]

About Access class, I am not sure how you can see it from Drive test But UE capability is informed by UE through "RRC connection Complete" message, Maybe you can see the Assigned class to USIM

As far as I know E does not need to inform system about its assigned class It is just compare ts class with cell defined access class

I remember in TEMS ( old versions) you could see some USIM data So Maybe TEMS provides USIM data

Best Regards

[agenov]

Ok than it is TEMS issue /or the one u use for drive test/. You know that PDP can not be exchanged without RRC carrying those messages. You may ask them or just leave it anyway you dont have failure.


br
alex

@Scorpion : Umm. Its not effect to user and can going to do PDP procedure , im just a bit wondering.
@agenov : I already tried to playback by TEMS, its same as actix

thanks,

[ninjafine]

Hi babak1349
I thinks so,maybe TEMS or Actic falut..
my nw didnt on commercial launch, we cant get any statistics to monitor.

more question,
-can we check from RNC trace message(UE trace, ISO trace etc..)??
-can we get the "USIM class(class1-15)" from DT logfile or RNC trace message, if can which message??? (not relate the topic)

Thanks and sorry about grammar :p,

Hi! Regarding to USIM class. You may get from air so called ASC (Access Service Classes).
Access Service Classes shall be used to provide different priorities on the RACH.
It is in WCDMA RACH Control Parameters that looks like:
Maximum Number of Preamble Cycles: 4
Minimum Backoff Time: 0
Maximum Backoff Time: 0
Number of Access Service Classes: 1
Access Service Class Identifier 0, Access Service Class Persistence: 25,0

You may also find Mapping Table from AC (Access Class from SIM) To ASC (Access Service Classes) in SysInfoType5 that looks like:
AC-To-ASC-MappingTable :
[0 ] : 0
[1 ] : 0
[2 ] : 0
[3 ] : 0
[4 ] : 0
[5 ] : 0
[6 ] : 0

If you need to know exactly the number of Access Control Class that is in USIM you may need to get
access to EFACC (Elementary File Access Control Class) in SIM. There you may discover something like this:

Access control classes:
ACC number 0: not allocated
ACC number 1: not allocated
ACC number 2: not allocated
ACC number 3: not allocated
ACC number 4: not allocated
ACC number 5: not allocated
ACC number 6: not allocated
ACC number 7: allocated
ACC number 8: not allocated
ACC number 9: not allocated
Bit 3 of Byte 1: 0
ACC number 11: not allocated
ACC number 12: not allocated
ACC number 13: not allocated
ACC number 14: not allocated
ACC number 15: not allocated

[pongpang]

thanks all friends,

and @ninjafine could u explain more detali, how to mapping the ASC???
ect,,which L3 message, mapping which one..

thanks

[scorpion]

I dont think ACC is the topic we should work on here...because in case if it is ACC then why the SIM sends "RCConnectionRequest".It suppose not to ... as per standards.

Also whether it is SIM/USIM the network is 3G-WCDMA, Dont mix it up with LTE.

[scorpion]

Hi! Regarding to USIM class. You may get from air so called ASC (Access Service Classes).
Access Service Classes shall be used to provide different priorities on the RACH.
It is in WCDMA RACH Control Parameters that looks like:
Maximum Number of Preamble Cycles: 4
Minimum Backoff Time: 0
Maximum Backoff Time: 0
Number of Access Service Classes: 1
Access Service Class Identifier 0, Access Service Class Persistence: 25,0

You may also find Mapping Table from AC (Access Class from SIM) To ASC (Access Service Classes) in SysInfoType5 that looks like:
AC-To-ASC-MappingTable :
[0 ] : 0
[1 ] : 0
[2 ] : 0
[3 ] : 0
[4 ] : 0
[5 ] : 0
[6 ] : 0

If you need to know exactly the number of Access Control Class that is in USIM you may need to get
access to EFACC (Elementary File Access Control Class) in SIM. There you may discover something like this:

Access control classes:
ACC number 0: not allocated
ACC number 1: not allocated
ACC number 2: not allocated
ACC number 3: not allocated
ACC number 4: not allocated
ACC number 5: not allocated
ACC number 6: not allocated
ACC number 7: allocated
ACC number 8: not allocated
ACC number 9: not allocated
Bit 3 of Byte 1: 0
ACC number 11: not allocated
ACC number 12: not allocated
ACC number 13: not allocated
ACC number 14: not allocated
ACC number 15: not allocated


I dont think ACC is the topic we should work on here...because in case if it is ACC then why the SIM sends "RCConnectionRequest".It suppose not to ... as per standards.

Also whether it is SIM/USIM the network is 3G-WCDMA, Dont mix it up with LTE.

By the way, SIB3/4 is carrying the ACC in Idle mode right ? and SIB 5 in Connected mode right ?

[pongpang]

I dont think ACC is the topic we should work on here...because in case if it is ACC then why the SIM sends "RCConnectionRequest".It suppose not to ... as per standards.

Also whether it is SIM/USIM the network is 3G-WCDMA, Dont mix it up with LTE.

thanks friend,
for ACC, I just want to know la..