AIRCOM International to Orange RRC Active IU Failures And RRC Access Radio Failures

RRC Active IU Failures

Summary
According to network statistics a large percentage of failures in the RRC Active phase is attributed to problems with the Iu Interface. Most RRC Active Iu failures occur while there was an active PS NRT RAB. This RAB would also fail with the Iu reason. Correlation with NRT Connections drops while performing Inter-System HHO to GSM/GPRS was found. From Drive tests done to specifically target the fault, it was seen that at the application level, the active FTP session was not terminated .i.e. user is not aware of the fault. The possible scenarios that may lead this counter to increment even though no abnormal condition is present are:
 The old Radio Link times out and the Nobe B sends a radio link failure message to the

RNC before the Iu Release Command is received from the CN. The RNC then misinterprets the failure and pegs the Iu failure counter (unsure if an Iu Release request is issued towards the CN). If this is the case then RRC_CONN_ACC_FAIL_RADIO should be incremented instead.  A timer in the CN expires before the GSM/GPRS network informs the CN that the mobile has successfully connected to the GSM/GPRS network. The CN then sends the Iu Release Command to the RNC with a cause value that the RNC misinterprets.

Most likely this is a bug with the RNC but if not then the timers involved in the Inter-System HHO to GSM procedure should be checked to see if they allow enough time for the handover to complete.

Analysis Work Flow

A large percentage of Failures occurring in the RRC Active phase was being associated with problems with the Iu Interface.
 KPI:
RRC _ CONN _ ACT _ FAIL _ IU RRC _ CONN _ ACT _ FAIL _ xxxx

A search was conducted to find possible correlations between RRC_CONN_ACT_FAIL_IU and other Service Level counters.
 Result : Correlation with the Iu failures for PS Background Service -

RAB_ACT_FAIL_PS_BACKG_IU

Now knowing that that the PS Background Service was reported as the main contributor, counters involving PS and NRT services were investigated.
 Result : Correlation with NRT Connections drops while performing

Inter-System HHO to GSM/GPRS

-

CON _ DRPS _ IS _ HHO _ xxxx _ NRT

Analysis Work Flow

Since only CS drive tests were previously loaded into database, it was decided to use the e1f (HHO to GSM measurement) events in the log files and plot them on a map. This pinpointed the locations where intersystem handovers (and most likely where Cell Change Orders for PS calls) most often occur. Cells near clusters of such events were checked to see if their Iu failures were high and if so added to a list of test candidates.
 Cell GLN0177C1, which had a high RRC_CONN_ACT_FAIL_IU

count, was selected to be tested.

The test was as follows:

 Start a PS background call on the cell and download a file using ftp.  Drive towards an area where no or poor 3g coverage is found but

the 2g coverage is good.

A route was planned to force Inter-RAT Cell Reselections (3g to 2g and 2g to 3g) in order that the impact on the ftp session (user perception) and statistics (network perception) could be assessed.

Statistics
Statistics during a 20 day period as shown below for RNC Enfield
Comparison between RRC Active IU Failures and RAB Active IU Failures with ISHO PS Drops
400 350 300 250 Occurances 200 150 100 50 0 01/01 02/01 03/01 04/01 05/01 06/01 07/01 08/01 09/01 10/01 11/01 12/01 13/01 14/01 15/01 16/01 17/01 18/01 19/01 20/01 con_drps_is_hho_all_nrt rab_act_fail_ps_backg_iu rrc_conn_act_fail_iu 63 59 77 166 152 161 78 72 84 51 44 60 89 82 98 136 126 170 165 160 176 102 69 83 90 77 104 85 80 93 119 111 123 172 165 280 162 153 235 94 87 116 181 172 210 151 143 183 332 323 348 107 95 113 192 176 191 172 161 179

Statistics (Test Candidate)

Statistics during a 20 day period as shown below for GLN0177C1
C a isi n et een C cti e fai e s and cti e ai es it S O S s

ances Occ

01 01

02 01 1 0 0

01

01

01

01

07 01 0 0 0

01

01

10 01

11 01

12 01

01

01

01

01

17 01 1 1 1

01

01

20 01 1 1

C C NN C

C L

1 0 0

1 1 0

0 0 0

1 1 1

2 2 2

0 0 0

2 0 0

1 1 1

1 0 1

1 0 0

0 0 0

CKG

1 0

7 7

C N

S S

LL N

10

a te

   !

!

!

!

!#

  !"

!

   !

   !

 !

!

 !

!

!#

!"

!

          

2 20 1 10

Test Setup
From Orange London Drivetest Methodology Document
1.1.1 S ata c llecti 1.1.1.1 Met l y

Methodology ll be dependant upon hich tests are being conducted. he follo ing test are defined:Data 1 ( F) ontext ct vat on ata 3 (L )  G

    

Log n

    

100k

do n oad

1M

Log off

etach

etach

       

ttach

Log off

  

Log off etach

etach

ontext eact vat on

ontext eact vat on

500k

do n oad

100k

' 46 5 3

Log n

Log n

500 byte p ng

500 byte p ng

up oad

ontext ct vat on

ontext ct vat on

1 )(' 2 '1' ' 4 5

2 '1' )(' 4)

' 4 5

1 )(' 3 1 2 '1' ' 4 5 8 7 ' 46 5 3 ' 4 5

2 '1' )(' 4

ata 2 (M )

ata 4 (

ttach

ontext eact vat on

1 )(' 1 2 '1' ' 4 5 8 7 ' 46 5 3 ' 4 5

Log n

do n oad

Log off

ontext eact vat on

1 )(' 3 1 2 '1' ' 4 5 8 7 ' 46 5 3 ' 4 5

500 byte p ng

500 byte p ng

ontext ct vat on

2 '1' )('

ttach

ttach

2 '1' )(' 4

&

Example Trace (Network View)

NodeB informs RNC of Loss of Sync with MS

PS-CN asks RNC to release resources

RNC does not respond in in 3 secs

PS-CN re-asks RNC to release resources RNC Releases the IU connection RNC sends Connection Release But MS not on channel any more

Drive Test Example (Subscriber View)

13:17:38.397 13:17:38.948 13:17:40.549 13:17:41.050 13:17:41.290 13:17:43.223 13:17:43.413 13:17:43.533 13:17:43.744 13:17:43.744 13:17:43.774 13:17:44.004 13:17:44.475 13:17:44.915 13:17:45.416 13:17:45.676 13:17:45.887 13:17:46.087 13:17:46.357 13:17:47.579 13:17:47.980 13:17:48.240 13:17:48.440 .. 13:18:09.220 13:18:09.300 13:18:09.400 13:18:09.501 13:18:09.581 13:18:09.621 13:18:09.621 13:18:09.701 13:18:09.821 13:18:09.881 PACCH PACCH PACCH PACCH PACCH PACCH PACCH PACCH PACCH PTCCH PACKET_DOWNLINK_ACK/NACK PACKET_UPLINK_ASSIGNMENT PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK PACKET_UPLINK_ACK/NACK PACKET_CONTROL_ACKNOWLEDGEMENT PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK TIMING_ADVANCE_BLOCK DCCH DCCH DCCH BCCH BCCH RACH CCCH SDCCH DCCH DCCH SDCCH SDCCH SDCCH SDCCH SDCCH SDCCH SDCCH SDCCH SDCCH SACCH SDCCH SDCCH SDCCH PHYSICAL_CHANNEL_RECONFIGURATION PHYSICAL_CHANNEL_RECONFIGURATION_COMPLETE CELL_CHANGE_ORDER_FROM_UTRAN SYSTEM_INFORMATION_TYPE_3 SYSTEM_INFORMATION_TYPE_4 CHANNEL_REQUEST IMMEDIATE_ASSIGNMENT LOCATION_UPDATING_REQUEST UE_RADIO_ACCESS_CAPABILITY_INFO INTER_RAT_HANDOVER_INFO CLASSMARK_CHANGE GPRS_SUSPENSION_REQUEST UTRAN_CLASSMARK_CHANGE AUTHENTICATION_REQUEST AUTHENTICATION_RESPONSE CIPHERING_MODE_COMMAND CIPHERING_MODE_COMPLETE IDENTITY_REQUEST IDENTITY_RESPONSE SYSTEM_INFORMATION_TYPE_5 LOCATION_UPDATING_ACCEPT TMSI_REALLOCATION_COMPLETE CHANNEL_RELEASE Time Cellular System Service Info Status Packet State Application Throughput Downlink Application Throughput Uplink Data Transferred Bytes Downlink Data Transfer Host Address 13:18:09.300 GSM 1800 Service received PDP Active 21928 n/a 223428 ftp.aircom.co.uk Cell Reselection to 2g cell Time Cellular System Service Info Status RRC State Packet State Spreading Factor DL Application Throughput Downlink Application Throughput Uplink Data Transferred Bytes Downlink Data Transfer Host Address 13:17:39.337 UMTS 2100 FDD Service received Cell DCH PDP Active 8 101173 n/a 202848 ftp.aircom.co.uk

View rom statistics rom test period

Statistics during the testing period as shown below for GLN0177C1
Comparison between RRC Active IU Failures and RAB Active IU Failures with ISHO PS Drops
7

Occurances

0
RRC_CONN_ACT_FAIL_IU RAB_ACT_FAIL_PS_BACKG_IU CON_DRPS_IS_HHO_ALL_NRT

11:30 6 6 6

11:45 1 1 1

12:00 1 1 2

12:15 3 3 3

12:30 1 1 1

12:45 0 0 0

13:00 1 1 1

13:15 1 1 1

13:30 1 1 1

13:45 0 0 1

14:00 1 1 1

14:15 3 3 3

14:30 0 0 0

14:45 4 4 4

15:00 0 0 0

15:15 3 3 3

15:30 3 3 3

Time

Conclusions
From the analysis of drive test data, the problem does not seem to be visible to the subscriber. At the application level, FTP session was not terminated. Hence the user would have only experienced a temporary pause in the transfer and then a slowdown of the throughput rate. So the possible scenarios that may lead this counter to increment even though no abnormal condition is present:
 The old Radio Link times out and the Nobe B sends a radio link failure message to the RNC before the Iu Release Command is received from the CN. With the receipt of the Iu Release Command, the RNC misinterprets the failure.  A timer in the CN expires before the GSM/GPRS network informs the CN that the mobile has successfully connected to the GSM/GPRS network. The CN then sends the Iu Release Command to the RNC with a failure cause that the RNC misinterprets.

Most likely this is a bug with the RNC but if not then the timers involved in the Inter-System HHO to GSM procedure should be checked to see if they should allow more time for the procedure to complete.

RRC Access Radio Failures

Summary
From results of investigations in other networks:
 Most Active Radio Access failures were caused during the registration and inter-rat cell reselection procedures

Registration is used for either IMSI attach or GPRS attach, while Interrat Cell Reselection is used for 2g to 3g cell reselection. In Orange network, there is a high correlation between RRC Access Radio (Synchro) Failures and the counters for Registration Failures and Inter-RAT Reselection failures for those cells with high numbers of failures. The Registration and Inter-RAT Reselection procedures were tested in a normal cell to check if the issue was a problem with the counter or the system. Result was that under normal conditions these procedures do not increment the counters. Evaluation of cells suffering from high failures for high interference or availability problems found no relationship between the failures. So far results are inconclusive as to where the fault lies with poor radio conditions or system fault. Iub Trace has been requested on a candidate site with high numbers of failures to further investigate problem.

Analysis Work Flow

From the results of investigations in other networks:
 Most Active Radio Access failures were caused during the

registration and inter-rat cell reselection procedures

Registration is used for either IMSI attach or GPRS attach Inter-rat Cell Reselection used for 2g to 3g cell reselection
RRC Access Fa
1% 0% 1% 2% 1% 3%1%1% 5% 7% 7% 47%

re for Sy c
in e

o ig on o ig in e o ig e e lo

dea h o ig lo

24%

o ig e e

Q C H9 A 9 A H9 A QC P E 9 A H @ A@ B 9 C E @ GA 9 9 I 9 CA D C H9 A @ GA 9 9 I H9 A E @ GA 9 9 FE 9 9 A 9 ED C 9 A C @ 9 C A 9 B9 A A 9A @ 9
a igh p io i p io i ign ign on p io i ign all e e abli h en a g in e ba g

egi

a ion

ell e ele ion

Analysis Work Flow

Tests were performed to verify which procedures cause an RRC Connection Request to be sent to the RNC with establishment cause Registration and if the procedures are inherently causing the RRC Access Radio failure counter to increment. The following procedures were tested:
 Home Subscriber attaching to GPRS services.  Other national network subscriber attempting to attach to network.  Foreign roaming subscriber attempting to attach to network. (This is the same procedure Location Update - for a home subscriber at the Uu interface)  Foreign roaming subscriber attempting to attach to GPRS service.

The tests were conducted in a static environment where signal level and quality was good. The objective was to test the actual procedures and not the type of radio environment in which the procedures may usually occur. While undergoing the tests to identify causes of the Iu failures, many Registrations and Inter-RAT cell reselections were made. The data collected from that test was also analysed to check for RRC access radio failures.

Registration event or GPRS Attach rom Orange Subscriber

Messages from test data:
12:08:39.301 12:08:39.301 12:08:39.421 12:08:39.922 12:08:40.002 12:08:40.382 12:08:40.382 12:08:40.382 12:08:40.482 12:08:40.983 12:08:41.003 12:08:41.013 12:08:41.404 12:08:41.404 12:08:41.724 12:08:41.804 12:08:41.894 12:08:41.894 12:08:42.015 12:08:42.015 12:08:42.085 12:08:42.085 12:08:42.085 12:08:42.165 12:08:42.325 BCCH BCCH CCCH CCCH CCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH SYSTEM_INFORMATION_BLOCK_TYPE_7 SYSTEM_INFORMATION_BLOCK_TYPE_18 RRC_CONNECTION_REQUEST RRC_CONNECTION_SETUP RRC_CONNECTION_SETUP DCCH_RRC_CONNECTION_SETUP_COMPLETE INITIAL_DIRECT_TRANSFER ATTACH_REQUEST MEASUREMENT_REPORT MEASUREMENT_REPORT ACTIVE_SET_UPDATE ACTIVE_SET_UPDATE_COMPLETE SECURITY_MODE_COMMAND SECURITY_MODE_COMPLETE MEASUREMENT_CONTROL MEASUREMENT_CONTROL DOWNLINK_DIRECT_TRANSFER ATTACH_ACCEPT DOWNLINK_DIRECT_TRANSFER GMM_INFO RRC_CONNECTION_RELEASE RRC_CONNECTION_RELEASE_COMPLETE RRC_CONNECTION_RELEASE RRC_CONNECTION_RELEASE_COMPLETE RRC_CONNECTION_RELEASE_COMPLETE Time: 12:08:40.382 ATTACH REQUEST M Protocol Discriminator (hex data: 8) (0x8) Mobility Management message for GPRS services M Attach Type (hex data: 1) Type of attach: GPRS attach Time: 12:08:39.421 RRC_CONNECTION_REQUEST establishmentCause: registration

Registration event or IMSI Attach rom other UK network subscriber

Messages from test data:
13:02:30.202 13:02:30.202 13:02:30.222 13:02:30.222 13:02:30.372 13:02:30.783 13:02:31.063 13:02:31.063 13:02:31.063 13:02:31.494 13:02:31.494 13:02:31.654 13:02:31.654 13:02:31.824 13:02:31.984 13:02:32.255 13:02:32.255 13:02:32.255 13:02:32.255 BCCH BCCH_BCH BCCH_BCH BCCH CCCH CCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH BCCH_BCH BCCH BCCH BCCH "SYSTEM_INFORMATION_BLOCK_TYPE_18" "SYSTEM_INFORMATION_BCH" "SYSTEM_INFORMATION_BCH" "SYSTEM_INFORMATION_BLOCK_TYPE_11" "RRC_CONNECTION_REQUEST" "RRC_CONNECTION_SETUP" "DCCH_RRC_CONNECTION_SETUP_COMPLETE" "INITIAL_DIRECT_TRANSFER" "LOCATION_UPDATING_REQUEST" "DOWNLINK_DIRECT_TRANSFER" "LOCATION_UPDATING_REJECT" "RRC_CONNECTION_RELEASE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" "SYSTEM_INFORMATION_BCH" "SYSTEM_INFORMATION_BLOCK_TYPE_2" "SYSTEM_INFORMATION_BLOCK_TYPE_7" "SYSTEM_INFORMATION_BLOCK_TYPE_18" Time: 13:02:31.654 RRC_CONNECTION_RELEASE releaseCause: normalEvent Time: 13:02:31.494 LOCATION UPDATING REJECT Reject cause value (11): PCN/PLMN not allowed Time: 13:02:30.372 RRC_CONNECTION_REQUEST establishmentCause: registration

Registration event or IMSI Attach rom roaming subscriber

Messages from test data:
16:34:38.552 16:34:38.822 16:34:39.092 16:34:39.092 16:34:39.092 16:34:39.483 16:34:39.483 16:34:39.493 16:34:39.493 16:34:40.645 16:34:40.645 16:34:40.835 16:34:40.835 16:34:41.135 16:34:41.135 16:34:41.466 16:34:41.466 16:34:41.466 16:34:41.466 16:34:44.941 16:34:44.941 16:34:44.951 16:34:44.951 16:34:45.331 16:34:45.331 16:34:45.492 16:34:45.652 CCCH CCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH "RRC_CONNECTION_REQUEST" "RRC_CONNECTION_SETUP" "DCCH_RRC_CONNECTION_SETUP_COMPLETE" "INITIAL_DIRECT_TRANSFER" "LOCATION_UPDATING_REQUEST" "DOWNLINK_DIRECT_TRANSFER" "IDENTITY_REQUEST" "UPLINK_DIRECT_TRANSFER" "IDENTITY_RESPONSE" "DOWNLINK_DIRECT_TRANSFER" "AUTHENTICATION_REQUEST" "UPLINK_DIRECT_TRANSFER" "AUTHENTICATION_RESPONSE" "SECURITY_MODE_COMMAND" "SECURITY_MODE_COMPLETE" "DOWNLINK_DIRECT_TRANSFER" "IDENTITY_REQUEST" "UPLINK_DIRECT_TRANSFER" "IDENTITY_RESPONSE" "DOWNLINK_DIRECT_TRANSFER" "LOCATION_UPDATING_ACCEPT" "UPLINK_DIRECT_TRANSFER" "TMSI_REALLOCATION_COMPLETE" "RRC_CONNECTION_RELEASE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" MS is allowed to roam on network and is allocated a new TMSI CS-CN Requests UE to Authenticate and start encryption CS-CN requests the IMSI of MS since TMSI is unknown Location Update to inform CN of MS location. SGSN/MSC does an IMSI Attach procedure with the VLR and the Subscribers HLR. MS sent TMSI in message Time: 16:34:38.552 RRC_CONNECTION_REQUEST establishmentCause: registration

Registration event or GPRS Attach rom roaming subscriber

Messages from test data:
16:48:44.100 16:48:44.270 16:48:44.671 16:48:44.921 16:48:44.921 16:48:44.921 16:48:45.352 16:48:45.352 16:48:45.352 16:48:45.352 16:48:45.632 16:48:45.632 16:48:45.762 16:48:45.762 16:48:45.912 16:48:46.073 16:48:46.353 BCCH CCCH CCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH BCCH_BCH "SYSTEM_INFORMATION_BLOCK_TYPE_18" "RRC_CONNECTION_REQUEST" "RRC_CONNECTION_SETUP" "DCCH_RRC_CONNECTION_SETUP_COMPLETE" "INITIAL_DIRECT_TRANSFER" "ATTACH_REQUEST" "DOWNLINK_DIRECT_TRANSFER" "GPRS_IDENTITY_REQUEST" "UPLINK_DIRECT_TRANSFER" "GPRS_IDENTITY_RESPONSE" "DOWNLINK_DIRECT_TRANSFER" "ATTACH_REJECT" "RRC_CONNECTION_RELEASE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" "RRC_CONNECTION_RELEASE_COMPLETE" "SYSTEM_INFORMATION_BCH" PS-CN requests MS for IMSI since ATTACH REQUEST has unknown TMSI Time: 16:48:45.632 ATTACH REJECT M Protocol Discriminator (hex data: 8) (0x8) Mobility Management message for GPRS services M GMM Cause (hex data: 0e) Cause value (0x0e): GPRS services not allowed in this PLMN Time: 16:48:44.921 ATTACH REQUEST M Protocol Discriminator (hex data: 8) (0x8) Mobility Management message for GPRS services M Attach Type (hex data: 1) Type of attach: GPRS attach Time: 16:48:44.270 RRC_CONNECTION_REQUEST establishmentCause: registration

Statistics recorded during Tests

Ti e 10 0 00 00 10 11 00 00 11 1 00 11 0 00 00 11 1 00 00 1 1 00 1 0 00 00 1 1 00 00 1 1 00 .. 1 1 00 1 0 00 00 1 1 00 00 1 1 00 egistrations 1 11 egistration ai s 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ccess adio ai s Test ase 0 0 IMSI Attach from ome Subscriber 0 0 0 0 0 RS Attach from ome Subscriber 0 0 0 0 IMSI Attach from other U networ Subscriber 0 0 0 IMSI Attach from Foreign Roaming Subscriber 0 RS Attach from Foreign Roaming Subscriber 0 0

1 1

10 0

All these procedures cause the registrations counter in M1001 Service Level to increment. If the attach is rejected for any of these procedures, the Registration Failures in M1001 Service Level does NOT increment. No RRC Access failures due to radio was seen during the tests. This proves that under good conditions, the registration procedures are not prone to cause the counter RRC_CON_ACC_FAIL_RADIO to increment. Some other reason must be the cause. Bad UE? Bad coverage? System Malfunction?

Inter RAT Cell Reselection (2g to 3g)

Messages from test data:
13:07:36.180 13:07:36.360 13:07:36.390 13:07:36.460 13:07:36.500 13:07:36.621 13:07:36.741 13:07:36.951 13:07:37.011 13:07:37.011 13:07:37.011 13:07:37.011 13:07:37.011 13:07:37.101 13:07:37.592 13:07:37.932 13:07:37.932 13:07:37.932 13:07:37.932 13:07:37.932 13:07:38.603 13:07:38.603 13:07:38.924 13:07:38.924 continued on next page PACCH PACCH PACCH PACCH PACCH PACCH PACCH BCCH BCCH_BCH BCCH BCCH BCCH BCCH CCCH CCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH PACKET_CONTROL_ACKNOWLEDGEMENT PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK PACKET_UPLINK_ASSIGNMENT PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK PACKET_DOWNLINK_ACK/NACK MASTER_INFORMATION_BLOCK SYSTEM_INFORMATION_BCH SYSTEM_INFORMATION_BLOCK_TYPE_1 SYSTEM_INFORMATION_BLOCK_TYPE_2 SYSTEM_INFORMATION_BLOCK_TYPE_7 SYSTEM_INFORMATION_BLOCK_TYPE_18 RRC_CONNECTION_REQUEST RRC_CONNECTION_SETUP DCCH_RRC_CONNECTION_SETUP_COMPLETE INITIAL_DIRECT_TRANSFER LOCATION_UPDATING_REQUEST INITIAL_DIRECT_TRANSFER ROUTING_AREA_UPDATE_REQUEST DOWNLINK_DIRECT_TRANSFER AUTHENTICATION_AND_CIPHERING_REQUEST DOWNLINK_DIRECT_TRANSFER AUTHENTICATION_REQUEST CS-CN requests UE to Authenticate PS-CN Requests UE to Authenticate and start encryption Routing Area Update to inform PS-CN that MS is back on 3g Location Update to inform CS-CN that MS is back on 3g Time: 13:07:37.101 RRC_CONNECTION_REQUEST establishmentCause: interRAT-CellReselection

GSM

Inter RAT Cell Reselection (2g to 3g)

Messages from test data (continued):
13:07:39.304 13:07:39.304 13:07:39.615 13:07:39.615 13:07:39.615 13:07:39.615 13:07:39.965 13:07:39.965 13:07:40.316 13:07:40.316 13:07:40.316 13:07:40.316 13:07:40.887 13:07:40.887 13:07:40.887 13:07:40.887 13:07:41.207 13:07:41.207 13:07:41.928 13:07:41.928 13:07:41.928 13:07:41.928 13:07:42.399 DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH UPLINK_DIRECT_TRANSFER AUTHENTICATION_RESPONSE UPLINK_DIRECT_TRANSFER AUTHENTICATION_AND_CIPHERING_RESPONSE SECURITY_MODE_COMMAND SECURITY_MODE_COMPLETE SECURITY_MODE_COMMAND SECURITY_MODE_COMPLETE DOWNLINK_DIRECT_TRANSFER IDENTITY_REQUEST UPLINK_DIRECT_TRANSFER IDENTITY_RESPONSE DOWNLINK_DIRECT_TRANSFER ROUTING_AREA_UPDATE_ACCEPT UPLINK_DIRECT_TRANSFER ROUTING_AREA_UPDATE_COMPLETE DOWNLINK_DIRECT_TRANSFER GMM_INFO DOWNLINK_DIRECT_TRANSFER LOCATION_UPDATING_ACCEPT UPLINK_DIRECT_TRANSFER TMSI_REALLOCATION_COMPLETE SIGNALLING_CONNECTION_RELEASE CS-CN releases signalling link but PS session continues PS-CN gives UE new P-TMSI at this stage CS-CN requests UE for IMEI CS-CN and PS-CN request for UE to restart ciphering

Statistics during drive test period

V V S V S V V V V S V V V V V V V V V S V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V US YS XS S W SS SS Y `S S W YS `S X a YS VS U XS Y XS V` a` V` b` a c b YS Y SS S` YS S` W W
STARTTIME REGISTRATI N_ATTS INTR_RAT_CELL_RE_SEL_ATTS REGISTRATI N_FAILS INTR_RAT_CELL_RE_SEL_FAILS RRC_C NN_ACC_FAIL_RADI

In normal conditions, Inter-RAT Cell Reselection and Registrations do not inherently fail or cause the counters to increment. Hence unlikely it is a mistriggering of the counter by the RNC. In normal conditions, there is a low correlation between the RRC Access failure counters and the Establishment Cause failure counters. This can be seen from the RNC level statistics. However there seems to be a very close relationship between RCC Access Failures due to Radio with the sum of Registration Failures and Inter-RAT cell reselection failures when a cell is functioning abnormally.

V U T YS Y S T YS V V T YS YTS W VUT WS YST WS VVT WS W Y T US W V U T US Y S T US V V T US Y T `S W V U T `S Y S T `S V V T `S Y T SS W V U T SS

143 164 170 170 186 205 213 233 265 353 144 157 163 198 204 257 333 380 559 17608 144 172 183 182 186 209 211 230 276 356 152 162 170 206 401 182 413 389 559 17427

oxf0023c1 hrt0244c1 hrt0283c1

gln0170b1 gln0484a1 gln0649b1 ess0015c1 gln0881b1 gln0779a1 gln0788a1 gln0677a1 gln3192c1 sur0003c1 gln0537a1 gln0826c1 gln0462c1 gln0494b1 gln0730b1 gln0537c1 gln4013a1 gln0596c1 gln0367a1 gln3207a1

oxf0023c1 hrt0244c1 hrt0283c1 gln0140b1 gln0055a1 gln0390b1 gln0140c1 gln0322b1 gln0455b1 gln0289a1 gln3109a1

Statistics o 10 Worst Per orming Cells (Week 5)

gln0140b1 gln0055a1 gln0390b1 gln0140c1 gln0322b1

a il r e s

gln0455b1 gln0289a1 gln3109a1

RRC_CONN_ACC_FAIL_RADIO

esx0047a1 hrt0120b1 gln3095c1 gln0434b1 gln0525a1 gln0271b1 esx0156c1 gln0580c1

C e lls

esx0033c1

esx0047a1 hrt0120b1 gln3095c1 gln0434b1 gln0525a1 gln0271b1

INTERRAT_AND_REG_FAIL

gln0170b1 gln0484a1 gln0649b1 ess0015c1 gln0881b1 gln0779a1 gln0788a1 gln0677a1 gln3192c1 sur0003c1 gln0537a1 gln0826c1 gln0462c1 gln0494b1 gln0730b1 gln0537c1 gln4013a1 gln0596c1 gln0367a1 gln3207a1

C o rre la tio n o Wo rs t 10 c e lls

esx0156c1 gln0580c1

esx0033c1

RRC_C NN_ CC_ L_R DIO INTERR T_ ND_REG_ IL

RRC_CONN_ CC_ IL_R DIO INTERR T_ ND_REG_ IL

1000 800 600 400 200 0

88 100

89 90

92 95

103 114 152 191 204 241 1972 154 176 210 276 281 346 349 369 449 101 116 155 198 205 240 1971 154 175 210 313 132 352 357 369 448

er R N C

it

re s e c t to R R C

c c e s s R a io

a il r e s a n

n te r-R

T +R e gis tra tio n

473 444

q p e e

h ri q p i h g f d

Statistics o Network RNCs (Week 5)

Corre atio er RNC wit res ect to RRC ccess Ra io Fai res a R +Re istratio Fai res
50000 40000
Fai res

ter

30000 20000 10000 0

ts

GLN500 GLN500 BRK400 GLN200 GLN200 GLN300 GLN300 GLN107 GLN107 0RNC1 0RNC2 0RNC1 0RNC1 0RNC2 0RNC1 0RNC2 0RNC1 0RNC2 8375 10385 104 148 2323 39160 23117 24541 668 807
RNC

RRC_CONN_ACC_FA _RA O INTERRAT_AND_RE _FAIL

6065 9794

1557 2820

6166 27001

1771 4990

Conclusions
RRC Access Radio Failures were compared with the M1000 counters: Site Availability, PRXNOISE and PRXTOT of the tested cells (5 of them) and no correlation was found between any of the counters.
 Not Interference related.  Not related to Site Availability.

Are Registrations fails causing the RRC Access failure counter to increment or RRC Access failures causing the Registration failure counter to increment? Iub trace to be done on candidate site GLN0730 with motivation to conclude if the problem is merely a side effect of poor coverage and/or large spillage, or if it is related with some system fault. Also a correlation was found on cells having a low RRC Setup Success Rate: many of the Setup failures also occur while doing Inter-RAT reselections and/or registrations. It might be possible that when an UE fails to register (attach) or complete the inter-RAT cell reselection, it may retry over and over again (all the time incremented the counters) while a user would most likely desist after a few failures.