dic_RNC_counterRU50.pdf

Nokia Networks
WCDMA RAN, Rel. RU50 and

RU50 EP1, Operating
Documentation, Issue 08
RNC Counters - RNW Part

DN99581291
Issue 12G
Approval Date 2016-02-19

The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not
be used except for the purposes defined in the agreement between You and Nokia Solutions and Networks
(“Agreement”) under which this document is distributed. No part of this document may be used, copied,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that
Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part of
the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the right
to change any such information and statements without notice. Nokia Solutions and Networks has made all
reasonable efforts to ensure that the content of this document is adequate and free of material errors and
omissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,
Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correction
of such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia Solutions and
Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © 2016 Nokia Solutions and Networks. All rights reserved.
f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its
products and services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations
for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia Solutions and Networks for any additional information.
2 DN99581291 Issue: 12G
Table of Contents
This document has 2706 pages

Summary of changes................................................................... 23

1 Radio network measurements..................................................... 25
1.1 Status of counters........................................................................ 26
1.2 Optional counters......................................................................... 30
1.3 Counter compatibility with 3GPP..................................................55
1.4 Quality of service..........................................................................55
1.5 Used definitions............................................................................55
1.6 RNC roles.....................................................................................56
1.7 Formulas for unit conversions...................................................... 56
1.8 Field descriptions of counter boxes..............................................57
1.9 Special objects in measurements................................................ 60

2 Measurement: Service level (RRC and RAB connections) (M1001)
..................................................................................................... 62
2.1 Introduction to service level (RRC and RAB connections)
measurement............................................................................... 63
2.1.1 Failure and abnormal release causes.......................................... 67
2.1.2 The differences between service level and RRC signalling
measurement............................................................................... 70
2.2 RRC setup....................................................................................71
2.2.1 RRC setup attempts.....................................................................73
2.2.2 RRC setup completions............................................................... 88
2.2.3 RRC setup failures....................................................................... 90
2.2.4 RRC Setup on CCH..................................................................... 99
2.3 RRC access............................................................................... 102
2.3.1 RRC access completions........................................................... 102
2.3.2 RRC access failures...................................................................106
2.3.3 RRC access releases.................................................................108
2.4 RRC active................................................................................. 122
2.4.1 RRC active completions.............................................................123
2.4.2 RRC active releases.................................................................. 124
2.4.3 RRC active failures.................................................................... 129
2.4.4 Reference cell change............................................................... 137
2.5 RRC setup attempts and failures per establishment cause....... 138
2.5.1 Mobile originating conversational call........................................ 139
2.5.2 Mobile originating streaming call................................................140
2.5.3 Mobile originating interactive call............................................... 141
2.5.4 Mobile originating background call.............................................142
2.5.5 Mobile originating subscribed traffic call.....................................144
2.5.6 Mobile terminating conversational call....................................... 145
2.5.7 Mobile terminating streaming call...............................................146
2.5.8 Mobile terminating interactive call.............................................. 148
Issue: 12G DN99581291 3
2.5.9 Mobile terminating background call............................................149
2.5.10 Emergency call...........................................................................150
2.5.11 Inter-RAT cell reselection........................................................... 151
2.5.12 Inter-RAT cell change order....................................................... 153
2.5.13 Registration................................................................................ 154
2.5.14 Detach........................................................................................155
2.5.15 MOC high priority signalling....................................................... 156
2.5.16 MTC high priority signalling........................................................158
2.5.17 MOC low priority signalling.........................................................159
2.5.18 MTC low priority signalling......................................................... 160
2.5.19 Call re-establishment................................................................. 161
2.5.20 Terminating - cause unknown.................................................... 162
2.6 RRC establishments per UE capability...................................... 164
2.7 Incoming handovers and relocations ........................................ 196
2.7.1 Serving RNC relocation..............................................................196
2.7.2 Inter-RNC intra-frequency hard handover .................................198
2.7.3 Inter-RNC inter-frequency handover ......................................... 199
2.7.4 Inter-system handover from GSM or LTE to WCDMA................200
2.7.5 Common counters for incoming relocation and HHO.................201
2.8 RAB setup.................................................................................. 210
2.8.1 RAB setup attempts for CS voice calls ......................................211
2.8.2 RAB setup attempts for CS data calls .......................................212
2.8.3 RAB setup attempts for PS calls................................................ 215
2.8.4 RAB setup completions for CS voice calls................................. 233
2.8.5 RAB setup completions for CS data calls ................................. 234
2.8.6 RAB setup completions for PS calls...........................................237
2.8.7 RAB setup failures for CS voice calls.........................................240
2.8.8 RAB setup failures for CS data calls.......................................... 248
2.8.9 RAB setup failures for PS calls.................................................. 259
2.9 RAB access................................................................................271
2.9.1 RAB access completions for CS voice calls...............................271
2.9.2 RAB access completions for CS data calls................................ 273
2.9.3 RAB access completions for PS calls........................................ 277
2.9.4 RAB access failures for CS voice calls...................................... 287
2.9.5 RAB access failures for CS data calls .......................................289
2.9.6 RAB access failures for PS calls................................................291
2.10 RAB reconfiguration................................................................... 295
2.11 RAB active................................................................................. 296
2.11.1 RAB active completions for CS voice calls................................ 297
2.11.2 RAB active completions for CS data calls..................................299
2.11.3 RAB active completions for PS calls.......................................... 304
2.11.4 RAB active releases for CS voice calls...................................... 316
2.11.5 RAB active releases for CS data calls ...................................... 321
2.11.6 RAB active releases for PS calls ...............................................330
2.11.7 RAB active failures for CS voice calls ....................................... 342
2.11.8 RAB active failures for CS data calls......................................... 347
4 DN99581291 Issue: 12G
2.11.9 RAB active failures for PS calls .................................................357
2.11.10 Reference cell change............................................................... 371
2.12 RAB and DCH holding times......................................................395
2.12.1 RAB holding times......................................................................395
2.12.2 RAB holding time in reference cell............................................. 407
2.12.3 DCH holding times..................................................................... 415
2.13 RRC and RAB setup times.........................................................418
2.14 Multi-RAB................................................................................... 432
2.14.1 RAB setup.................................................................................. 434
2.14.2 RAB access................................................................................450
2.14.3 RAB active completions............................................................. 468
2.14.4 RAB active failures.....................................................................484

3 Measurement: Packet Call (M1022)...........................................505
3.1 Introduction to packet call measurement................................... 505
3.2 Packet session requests............................................................ 509
3.3 Packet call attempts................................................................... 510
3.4 Successful packet call allocations..............................................516
3.5 Packet call setup failures........................................................... 532
3.6 Packet call channel switches..................................................... 544
3.7 Packet call releases................................................................... 561
3.8 HSUPA Iub congestion control................................................... 583
3.9 Successful packet call allocations after Inter-RNC HHO........... 589
3.10 DCH user plane initial requests..................................................592
3.11 DCH user plane initial allocation successful.............................. 597
3.12 DCH user plane upgrade requests.............................................606
3.13 DCH user plane upgrade successful..........................................610
3.14 DCH reconfiguration failures...................................................... 619
3.15 HSPA session duration...............................................................629
3.16 HSPA user plane duration.......................................................... 633
3.17 RLC performance.......................................................................647
3.18 Application aware RAN statistics............................................... 653

4 Measurement: Location services (M1011)................................. 657
4.1 Introduction to location services measurement..........................658
4.2 Location requests.......................................................................662
4.3 Location related data requests...................................................670
4.4 Location calculations using cell ID/RTT method........................ 673
4.5 Location calculations using UE based A-GPS method.............. 678
4.6 Location calculations using network based A-GPS method.......684
4.7 Location services latency........................................................... 689
4.7.1 Latency of CI+RTT method........................................................ 689
4.7.2 Latency of A-GPS method......................................................... 692
4.7.3 Total latency............................................................................... 695
4.7.4 Latency of emergency ISHO...................................................... 697
4.7.5 Latency for emergency requests................................................700

Issue: 12G DN99581291 5
5 Measurement: Cell resource (M1000)........................................709
5.1 Introduction to cell resource measurement................................ 709
5.2 Cell availability........................................................................... 710
5.3 Received Rel99 wideband power...............................................715
5.4 Received total wideband power................................................. 729
5.5 Transmitted Rel99 wideband power...........................................745
5.6 Transmitted carrier power.......................................................... 756
5.7 HSPA power measurements...................................................... 764
5.8 Measuring LRT and LNRT estimations...................................... 772
5.9 Measuring Ptx_RT and Ptx_NRT estimations............................785
5.10 Measuring the RACH channel....................................................801
5.11 Measuring the SCCPCH channel...............................................805
5.12 Measuring the code tree............................................................ 816
5.12.1 Measuring code occupancy....................................................... 817
5.12.2 Measuring code blocking........................................................... 820
5.12.3 Measuring code requests...........................................................824
5.12.4 Measuring HSDPA code usage..................................................829
5.12.5 Measuring HSDPA code downgrades........................................ 835
5.13 Measuring the radio link reports.................................................837
5.14 Transmitted code power.............................................................840
5.15 Radio bearer downgrades and releases due to congestion.......846
5.16 Radio bearer downgrades and releases due to throughput based
optimisation................................................................................ 860
5.17 HSDPA user measurements...................................................... 861
5.18 HSUPA user measurements...................................................... 878
5.19 HSPA user amount per traffic class............................................901
5.20 Estimated usage of BTS channel elements............................... 909
5.21 BTS HSUPA resource status......................................................936
5.22 Load based AMR codec mode selection thresholds.................. 938
5.23 Service Area Broadcast............................................................. 945
5.24 Mass Event Handler...................................................................948

6 Measurement: WBTS Resource (M1031).................................. 950
6.1 HSPA users per WBTS.............................................................. 950
6.2 WBTS HSPA capability modification.......................................... 953

7 Measurement: Traffic (M1002)................................................... 956
7.1 Introduction to traffic measurement............................................956
7.1.1 DCH counters in general............................................................956
7.1.2 RT DCH allocation procedure.................................................... 960
7.1.3 NRT DCH allocation procedure..................................................962
7.1.4 NRT DCH upgrade and downgrade........................................... 964
7.1.5 Pre-emption and DCH counters................................................. 965
7.1.6 Example of counter updates...................................................... 965
7.1.7 HS-DSCH counters.................................................................... 968
7.1.8 E-DCH counters......................................................................... 969
7.1.9 Compressed mode allocation counters......................................970
6 DN99581291 Issue: 12G
7.2 DCH counters (SRNC)............................................................... 971

7.2.1 DCH requests for signalling links............................................... 972
7.2.2 DCH allocations for signalling links............................................ 976
7.2.3 DCH requests for CS voice calls................................................980
7.2.4 DCH allocations for CS voice calls.............................................984
7.2.5 DCH requests for CS data calls................................................. 995
7.2.6 DCH allocations for CS data calls............................................ 1004
7.2.7 DCH requests for PS data calls................................................1011
7.2.8 DCH allocations for PS data calls............................................ 1027
7.3 DCH counters (DRNC)............................................................. 1074
7.3.1 DCH requests for signalling links............................................. 1074
7.3.2 DCH allocations for signalling links.......................................... 1078
7.3.3 DCH requests for CS voice calls..............................................1082
7.3.4 DCH allocations for CS voice calls...........................................1086
7.3.5 DCH requests for data calls......................................................1108
7.3.6 DCH allocations for data calls...................................................1112
7.4 HS-DSCH counters.................................................................. 1138
7.4.1 HS-DSCH requests for PS calls............................................... 1139
7.4.2 HS-DSCH setup failures for PS calls........................................1140
7.4.3 HS-DSCH allocations for PS calls............................................ 1159
7.4.4 HS-DSCH allocation releases.................................................. 1185
7.4.5 HS-DSCH in DRNC.................................................................. 1196
7.4.6 Direct Resource Allocation for HSPA....................................... 1198
7.5 E-DCH counters....................................................................... 1200
7.5.1 E-DCH setup failures............................................................... 1200
7.5.2 E-DCH allocations for PS call.................................................. 1210
7.5.3 E-DCH allocation releases for PS call......................................1216
7.5.4 E-DCH in DRNC.......................................................................1223
7.6 SRB allocations on HSPA........................................................ 1225
7.7 CS Voice over HSPA................................................................ 1227
7.8 Multi-RAB counters.................................................................. 1243
7.9 Compressed mode requests and allocations........................... 1255
7.9.1 Requests for compressed mode (SRNC).................................1255
7.9.2 Allocations for compressed mode (SRNC).............................. 1260
7.9.3 Requests for compressed mode (DRNC)................................ 1273
7.9.4 Allocations for compressed mode (DRNC).............................. 1276
7.10 HSPA layering.......................................................................... 1284
7.11 HSPA channel type selection................................................... 1288
7.12 DCH setup failures for PS calls in SRNC.................................1299
7.13 Load based AMR codec mode selection..................................1306
7.14 Mass Event Handler.................................................................1310

8 Measurement: Cell Throughput (M1023)................................. 1314
8.1 Introduction to cell throughput measurement...........................1314
8.2 Counters of Cell Throughput measurement............................. 1315

Issue: 12G DN99581291 7
9 Measurement: CS Voice HSPA User Plane (M1032)...............1333
9.1 CS Voice over HSPA jitter........................................................ 1333
9.2 CS Voice over HSPA Iub delay................................................ 1336
9.3 CS Voice HSPA frame counters............................................... 1345

10 Measurement: RCPM OLPC (M1016)..................................... 1347
10.1 Introduction to RCPM OLPC measurement............................. 1347
10.2 Uplink radio connection quality................................................ 1348
10.2.1 Average experienced Eb/No.................................................... 1348
10.2.2 Uplink block error rate (BLER)................................................. 1350
10.2.3 Uplink bit error rate (BER)........................................................1354
10.3 Downlink radio link power........................................................ 1357
10.4 Uplink HARQ retransmissions..................................................1359

11 Measurement: RCPM RLC (M1017)........................................ 1361
11.1 Introduction to RCPM RLC measurement................................1361
11.2 DL PDCP and RLC buffers.......................................................1363
11.3 DL RLC SDU transmissions.....................................................1367
11.4 DL RLC PDU transmissions.....................................................1368
11.5 DL RLC PDU throughput..........................................................1374
11.6 DL RLC PDU discards............................................................. 1388
11.7 DL RLC PDU transmission quality........................................... 1389
11.8 DL RLC SDU transfer delay..................................................... 1393
11.9 UL AM RLC throughput ...........................................................1396

12 Measurement: RCPM UEQ (M1018)....................................... 1403
12.1 Introduction to RCPM UEQ measurement............................... 1403
12.2 UE quality measurement..........................................................1403

13 Measurement: RCPM Aggregate measurements (M1024, M1025,
M1026 and M1027).................................................................. 1406
13.1 Introduction to RCPM aggregate measurements.....................1406
13.2 WCEL level aggregation.......................................................... 1406
13.2.1 RCPM OLPC WCEL (M1024).................................................. 1408
13.2.2 RCPM RLC WCEL (M1026).....................................................1420
13.3 RNC level aggregation............................................................. 1458
13.3.1 RCPM OLPC RNC (M1025).....................................................1458
13.3.2 RCPM RLC RNC (M1027)....................................................... 1470

14 Measurement: Soft handover (M1007).................................... 1509
14.1 Introduction to soft handover measurement.............................1509
14.2 Soft handover counters for RT traffic....................................... 1513
14.2.1 SHO durations per active set size............................................1513
14.2.2 SHO durations for soft and softer handovers...........................1515
14.2.3 Cell additions, deletions, and replacements.............................1518
14.2.4 Success of active set update procedure.................................. 1521
14.2.5 Rx-Tx time difference measurements...................................... 1523
14.3 Soft handover counters for NRT traffic.....................................1524
8 DN99581291 Issue: 12G
14.4 Soft handover counters for HSDPA traffic................................ 1534
14.5 Soft handover counters for HSUPA traffic................................ 1543
14.5.3 Cell additions to E-DCH active set........................................... 1546
14.5.4 Soft handover failure cause counters.......................................1548
14.6 CPICH Ec/No distribution.........................................................1550

15 Measurement: Intra-system hard handover (M1008)...............1557
15.1 Introduction to intra-system hard handover measurement.......1557
15.2 RT traffic: common intra-system handover failures..................1563
15.3 RT traffic: intra-frequency hard HO cause counters.................1565
15.4 RT traffic: intra-frequency hard HO counters after positive HO
decision.................................................................................... 1567
15.4.1 Intra-frequency hard handover due to SHO incapability.......... 1567
15.5 RT traffic: inter-frequency measurement counters................... 1570
15.5.1 Inter-frequency measurements with compressed mode.......... 1571
15.5.2 Inter-frequency measurements without compressed mode..... 1579
15.5.3 Result of inter-frequency measurements: no cells good enough.....
1588
15.6 RT traffic: inter-frequency HO counters after positive HO decision
per cause................................................................................. 1597
15.6.1 Inter-frequency handover due to UL DCH quality.................... 1597
15.6.2 Inter-frequency handover due to UE Tx power........................ 1600
15.6.3 Inter-frequency handover due to DL DPCH power.................. 1603
15.6.4 Inter-frequency handover due to CPICH RSCP.......................1605
15.6.5 Inter-frequency handover due to CPICH Ec/No....................... 1608
15.6.6 Inter-frequency handover due to Immediate IMSI-based......... 1611
15.6.7 Inter-frequency handover due to HW or logical resources.......1613
15.6.8 Inter-frequency handover due to PrxTotal................................ 1616
15.6.9 Inter-frequency handover due to PtxTotal................................ 1619
15.6.10 Inter-frequency handover due to Service based...................... 1621
15.6.11 Inter-frequency handover due to lack of spreading codes....... 1624
15.6.12 Inter-frequency handover due to cell shutdown....................... 1627
15.6.13 Inter-frequency handover due to block resource......................1628
15.7 RT traffic: inter-frequency HO counters after positive HO decision
per type.................................................................................... 1629
Issue: 12G DN99581291 9
15.7.1 Intra-RNC intra-BTS inter-frequency handover........................1630
15.7.2 Intra-RNC inter-BTS inter-frequency handover........................1632
15.7.3 Inter-RNC inter-frequency handover........................................ 1635
15.8 NRT traffic: Common intra-system handover failures.............. 1637
15.9 NRT traffic: intra-frequency hard HO reason counters.............1640
15.10 NRT traffic: intra-frequency hard HO counters after positive HO
decision.................................................................................... 1641
15.10.1 Intra-frequency hard handover due to SHO incapability.......... 1642
15.11 NRT traffic: Inter-frequency measurement counters................ 1645
15.11.1 Inter-frequency measurements with compressed mode.......... 1645
15.11.2 Inter-frequency measurements without compressed mode..... 1654
15.11.3 Result of inter-frequency measurements: no cells good enough.....
1663
15.12 NRT traffic: inter-frequency HO counters after positive HO
decision per cause................................................................... 1671
15.12.1 Inter-frequency handover due to UL DCH quality.................... 1672
15.12.2 Inter-frequency handover due to UE Tx power........................ 1674
15.12.3 Inter-frequency handover due to DL DPCH power.................. 1677
15.12.4 Inter-frequency handover due to CPICH RSCP.......................1680
15.12.5 Inter-frequency handover due to CPICH Ec/No....................... 1682
15.12.6 Inter-frequency handover due to immediate IMSI-based......... 1685
15.12.7 Inter-frequency handover due to DL capacity request rejections.....
1688
15.12.8 Inter-frequency handover due to HW or logical resources.......1693
15.12.9 Inter-frequency handover due to PrxTotal................................ 1696
15.12.10 Inter-frequency handover due to PtxTotal................................ 1698
15.12.11 Inter-frequency handover due to Service based...................... 1701
15.12.12 Inter-frequency handover due to UL capacity request rejections.....
1704
15.12.13 Inter-frequency handover due to lack of spreading codes....... 1709
15.12.14 Inter-frequency handover due to cell shutdown....................... 1712
15.12.15 Inter-frequency handover due to block resource......................1713
15.13 NRT traffic: Inter-frequency HO counters after positive HO
decision per type...................................................................... 1715
15.13.1 Intra-RNC intra-BTS inter-frequency handover........................1715
15.13.2 Intra-RNC inter-BTS inter-frequency handover........................1717
15.13.3 Inter-RNC inter-frequency handover........................................ 1720
15.14 Multi-band load balancing handover........................................ 1723
15.15 Rejected SRNS relocations......................................................1730
15.16 HS-DSCH serving cell changes............................................... 1731
15.16.1 Started serving cell changes.................................................... 1733
15.16.2 Failed or prevented serving cell changes.................................1735
15.16.3 Successful serving cell changes.............................................. 1740
15.17 E-DCH serving cell changes.................................................... 1741
15.18 HSPA Inter-RNC hard handovers.............................................1745
15.19 HSPA inter-frequency handover...............................................1748
15.20 HSPA capability based handover............................................. 1758
10 DN99581291 Issue: 12G

16 Measurement: Inter-system handover (M1010)....................... 1766
16.1 Introduction to inter-system handover measurement...............1766
16.2 RT traffic: Common inter-system handover failures................. 1770
16.3 RT traffic: Inter-system measurement counters....................... 1772
16.3.1 Inter-system measurements with compressed mode...............1773
16.3.2 Inter-system measurements without compressed mode..........1781
16.3.3 Result of inter-system measurements: no cells good enough. 1790
16.4 RT traffic: Inter-system HO counters after positive HO decision......
1800
16.4.1 Inter-system handover due to UL DCH quality.........................1800
16.4.2 Inter-system handover due to UE Tx Power............................ 1803
16.4.3 Inter-system handover due to DL DPCH power.......................1805
16.4.4 Inter-system handover due to CPICH RSCP........................... 1808
16.4.5 Inter-system handover due to CPICH Ec/No........................... 1810
16.4.6 Inter-system handover due to Immediate IMSI-based............. 1813
16.4.7 Inter-system handover due to emergency call......................... 1815
16.4.8 Inter-system handover with CS/PS separation........................ 1817
16.4.9 Inter-system handover due to HW or logical resources........... 1820
16.4.10 Inter-system handover due to PrxTotal.................................... 1822
16.4.11 Inter-system handover due to PtxTotal.....................................1825
16.4.12 Inter-system handover due to Service based...........................1827
16.4.13 Inter-system handover due to lack of spreading codes............1830
16.4.14 Inter-system handover due to Wireless Priority Service.......... 1832
16.4.15 Inter-system handover due to cell shutdown............................1835
16.4.16 Inter-system handover due to block resource.......................... 1836
16.4.17 Directed retry............................................................................1837
16.4.18 Inter-system handover to GAN.................................................1840
16.4.19 Retry due to Multiple BSIC Identification..................................1842
16.5 NRT traffic: Common inter-system handover failures.............. 1844
16.6 NRT traffic: Inter-system measurement counters.....................1846
16.6.1 Inter-system measurements with compressed mode...............1846
16.6.2 Inter-system measurements without compressed mode..........1857
16.6.3 Result of inter-system measurements: no cells good enough. 1868
16.7 NRT traffic: Inter-system HO counters after positive HO decision...
1876
16.7.1 Inter-system handover due to UL DCH quality.........................1877
16.7.2 Inter-system handover due to UE Tx Power............................ 1879
16.7.3 Inter-system handover due to DL DPCH power.......................1882
16.7.4 Inter-system handover due to CPICH RSCP........................... 1884
16.7.5 Inter-system handover due to CPICH Ec/No........................... 1887
16.7.6 Inter-system handover due to Immediate IMSI-based............. 1889
16.7.7 Inter-system handover due to DL capacity request rejections. 1892
16.7.8 Inter-system handover due to HW or logical resources........... 1897
16.7.9 Inter-system handover due to PrxTotal.................................... 1899
16.7.10 Inter-system handover due to PtxTotal.....................................1902
Issue: 12G DN99581291 11
16.7.11 Inter-system handover due to Service based...........................1904
16.7.12 Inter-system handover due to UL capacity request rejections. 1907
16.7.13 Inter-system handover due to lack of spreading codes............1912
16.7.14 Inter-system handover due to cell shutdown............................1915
16.7.15 Inter-system handover due to block resource.......................... 1916
16.7.16 Retry due to Multiple BSIC Identification..................................1917
16.8 Inter-system handover cancellation......................................... 1918
16.9 LTE mobility..............................................................................1925
16.9.1 LTE redirection with measurements......................................... 1925
16.9.2 Inter-system handover to LTE.................................................. 1927

17 Measurement: RRC signalling (M1006)................................... 1946
17.1 Introduction to RRC signalling measurement...........................1946
17.2 RRC connection management procedures.............................. 1946
17.2.1 RRC connection establishment................................................1946
17.2.1.1 RRC connection setup requests.............................................. 1946
17.2.1.2 RRC connection rejects........................................................... 1958
17.2.2 RRC connection re-establishment........................................... 1964
17.2.3 RRC connection setup............................................................. 1971
17.2.4 RRC connection setup complete..............................................1973
17.2.5 RRC connection release.......................................................... 1974
17.2.6 Paging...................................................................................... 1979
17.2.6.1 Paging success rate.................................................................1982
17.2.6.2 Paging delay............................................................................ 1987
17.2.7 UE dedicated paging................................................................1991
17.2.8 Initial direct transfer..................................................................1991
17.2.9 Security mode control.............................................................. 1992
17.2.10 Signalling connection release ................................................. 1993
17.2.11 Signalling connection release indication.................................. 1994
17.3 Radio bearer control procedures..............................................1995
17.3.1 Radio bearer setup...................................................................1995
17.3.2 Radio bearer setup complete................................................... 1998
17.3.3 Radio bearer setup using blind HO.......................................... 1998
17.3.4 Radio bearer reconfiguration....................................................2003
17.3.5 Radio bearer reconfiguration complete.................................... 2011
17.3.6 Transport channel reconfiguration............................................2012
17.3.7 Physical channel reconfiguration............................................. 2013
17.3.8 Radio bearer release................................................................2017
17.3.9 Transport format combination control.......................................2018
17.3.10 HS-DSCH Mac-d flow setup.....................................................2019
17.4 RRC connection mobility procedures.......................................2027
17.4.1 Cell update............................................................................... 2027
17.4.2 URA update..............................................................................2035
17.4.3 RRC connected state UEs that moved to another cell.............2036
17.4.4 Inter-RAT cell change order from UTRAN................................2037
17.4.5 Handover from UTRAN ........................................................... 2038
12 DN99581291 Issue: 12G
17.4.6 RRC handover to UTRAN........................................................ 2039

17.4.7 Active set update......................................................................2040
17.4.8 LTE layering............................................................................. 2044
17.5 Measurement reporting............................................................ 2048
17.6 Protocol states......................................................................... 2049
17.6.1 Packet data state transition......................................................2049
17.6.2 Operating time of UE in packet data transfer states................ 2084
17.7 A-GPS Assistance Data Delivery............................................. 2092
17.8 RRC Status messages.............................................................2093
17.9 PRACH Propagation Delay ..................................................... 2095
17.10 Resource allocation time.......................................................... 2113
17.11 Fast dormancy profiling............................................................ 2116
17.12 Mass Event Handler................................................................. 2118

18 Measurement: L3 signalling at Iub (M1005).............................2120
18.1 Introduction to L3 signalling at Iub measurement.................... 2120
18.2 NBAP common procedures......................................................2121
18.2.1 Radio link setup........................................................................2121
18.2.1.1 Radio link setup attempts.........................................................2121
18.2.1.2 Radio link setup successes......................................................2124
18.2.1.3 Radio link setup failures........................................................... 2127
18.2.2 Common measurement procedures.........................................2145
18.2.3 Block resource procedures...................................................... 2148
18.2.4 Reset procedures.....................................................................2150
18.3 NBAP dedicated procedures....................................................2154
18.3.1 Radio link addition....................................................................2154
18.3.1.1 Radio link addition attempts..................................................... 2154
18.3.1.2 Radio link addition successes.................................................. 2155
18.3.1.3 Radio link addition failures....................................................... 2157
18.3.2 Radio link failure.......................................................................2163
18.3.2.1 Radio link failures on SRNC side............................................. 2163
18.3.2.2 Radio link failures on DRNC side.............................................2166
18.3.3 Radio link deletion....................................................................2169
18.3.3.1 Radio link deletions on SRNC side.......................................... 2169
18.3.3.2 Radio link deletion responses on SRNC side.......................... 2173
18.3.3.3 Radio link deletions on DRNC side.......................................... 2173
18.3.3.4 Radio link deletion responses on DRNC side.......................... 2176
18.3.4 Synchronised radio link reconfiguration .................................. 2177
18.3.4.1 Radio link reconfiguration preparations....................................2177
18.3.4.2 Radio link reconfiguration preparations ready..........................2189
18.3.4.3 Radio link reconfiguration failures............................................ 2194
18.3.4.4 Synchronised radio link reconfiguration commit ......................2213
18.3.4.5 Synchronised radio link reconfiguration cancellation............... 2214
18.3.5 Compressed mode command procedure.................................2217
18.3.6 Dedicated measurement procedures....................................... 2217
18.3.6.1 Dedicated measurement initiation............................................2217
Issue: 12G DN99581291 13
18.3.6.2 Dedicated measurement reporting...........................................2220
18.3.6.3 Dedicated measurement failure indication............................... 2221
18.3.6.4 Dedicated measurement termination....................................... 2222
18.3.7 Radio link restoration............................................................... 2222
18.3.8 Downlink Power Control...........................................................2223
18.4 Error handling procedures........................................................2226
18.5 HS-DSCH MAC-d flow setup at Iub......................................... 2227
18.6 Radio link setup time................................................................2233

19 Measurement: L3 signalling at Iur (M1004)..............................2235
19.1 Introduction to L3 signalling at Iur measurement..................... 2235
19.2 RNSAP DCH procedures......................................................... 2235
19.2.1 Radio link setup over Iur.......................................................... 2235
19.2.1.1 Radio link setup requests for inter-RNC SHO over Iur.............2235
19.2.1.2 Radio link setup successes for inter-RNC SHO over Iur..........2237
19.2.1.3 Radio link setup failures for inter-RNC SHO over Iur...............2238
19.2.2 Radio link addition over Iur.......................................................2243
19.2.2.1 Radio link addition requests for inter-RNC SHO over Iur.........2243
19.2.2.2 Radio link addition successes for inter-RNC SHO over Iur......2244
19.2.2.3 Radio link addition failures for inter-RNC soft handover over Iur.....
2246
19.2.3 Radio link failures over Iur........................................................2251
19.2.3.1 Radio link failure for inter-RNC SHO on SRNC side over Iur...2251
19.2.3.2 Radio link failure for inter-RNC SHO on DRNC side over Iur.. 2254
19.2.4 Radio link deletions over Iur.....................................................2257
19.2.4.1 Radio link deletion for inter-RNC SHO on SRNC side over Iur........
2257
19.2.4.2 Radio link deletion response to inter-RNC SHO on SRNC side
over Iur..................................................................................... 2258
19.2.4.3 Radio link deletion for inter-RNC SHO on DRNC side over Iur........
2259
19.2.4.4 Radio link deletion response to inter-RNC SHO (RL setup) on
DRNC side over Iur.................................................................. 2260
19.2.5 Synchronised radio link reconfiguration over Iur...................... 2260
19.2.5.1 Radio link reconfiguration preparations (synchronised) over Iur......
2260
19.2.5.2 Radio link reconfiguration preparations ready (synchronised) over
Iur............................................................................................. 2265
19.2.5.3 Radio link reconfiguration failures (synchronized) over Iur...... 2270
19.2.5.4 Synchronised radio link reconfiguration commits over Iur........2286
19.2.5.5 Synchronised radio link reconfiguration cancellations over Iur........
2287
19.2.6 Unsynchronised radio link reconfiguration over Iur.................. 2289
19.2.6.1 Radio link reconfiguration preparations (unsynchronised) over Iur..
2289
19.2.6.2 Radio link reconfiguration preparations ready (unsynchronised)
over Iur..................................................................................... 2289
19.2.6.3 Radio link reconfiguration failures (unsynchronised) over Iur.. 2290
14 DN99581291 Issue: 12G
19.2.7 HS-DSCH MAC-d flow setup................................................... 2292

19.2.8 Compressed mode command.................................................. 2297
19.2.9 Dedicated measurement initiation ...........................................2298
19.2.9.1 Dedicated measurement initiation on SRNC over Iur.............. 2298
19.2.9.2 Dedicated measurement initiation on DRNC over Iur.............. 2300
19.2.10 Dedicated measurement reporting ..........................................2302
19.2.10.1 Dedicated measurement reports on SRNC over Iur................ 2302
19.2.10.2 Dedicated measurement reports on DRNC over Iur................ 2303
19.2.11 Dedicated measurement termination ...................................... 2303
19.2.11.1 Dedicated measurement terminations on SRNC over Iur........ 2303
19.2.11.2 Dedicated measurement terminations on DRNC over Iur........2304
19.2.12 Dedicated measurement failure .............................................. 2304
19.2.12.1 Dedicated measurement failure indications on SRNC over Iur........
2304
19.2.12.2 Dedicated measurement failure indications on DRNC over Iur........
2305
19.2.13 Radio link pre-emption ............................................................ 2306
19.2.13.1 Radio link pre-emption on SRNC over Iur................................2306
19.2.13.2 Radio link pre-emption on DRNC over Iur................................2306
19.2.14 Radio link restoration indication .............................................. 2307
19.2.14.1 Radio link restoration indication on SRNC over Iur..................2307
19.2.14.2 Radio link restoration indication on DRNC over Iur..................2308
19.2.15 Physical channel reconfiguration ............................................ 2308
19.2.15.1 Physical channel reconfiguration on SRNC over Iur................ 2308
19.2.15.2 Physical channel reconfiguration on DRNC over Iur................2309
19.2.16 Downlink Power Control........................................................... 2311
19.3 RNSAP global procedures....................................................... 2313
19.3.1 Error indication......................................................................... 2313
19.3.2 Common measurement initiation............................................. 2314
19.3.3 Common Measurement Procedures........................................ 2315
19.3.3.1 Common Measurement Initiation............................................. 2315
19.3.3.2 Common Measurement Report................................................2321
19.3.3.3 Common Measurement Termination........................................ 2322
19.3.3.4 Common Measurement Failure Indication............................... 2323
19.4 Iur interface availability.............................................................2328
19.5 Iur user plane throughput......................................................... 2330
19.6 NRT user plane allocation failures........................................... 2342
19.7 SHO branch setup failures due to transmission.......................2343

20 Measurement: L3 signalling at Iu (M1003)...............................2345
20.1 Introduction to L3 signalling at Iu measurement...................... 2345
20.2 RANAP procedures..................................................................2345
20.2.1 Initial UE message................................................................... 2345
20.2.2 Iu release command ................................................................2346
20.2.3 Iu release complete..................................................................2347
20.2.4 Iu release request.................................................................... 2347
Issue: 12G DN99581291 15
20.2.5 RAB assignment request ........................................................ 2351

20.2.5.1 RAB assignment requests........................................................2351
20.2.5.2 RAB reconfiguration requests.................................................. 2352
20.2.5.3 RAB release requests by CN................................................... 2353
20.2.6 RAB assignment response.......................................................2354
20.2.6.1 RAB assignment successful.....................................................2354
20.2.6.2 RAB reconfiguration successful............................................... 2354
20.2.6.3 RAB assignment not successful...............................................2355
20.2.6.4 RAB reconfiguration not successful......................................... 2359
20.2.6.5 RAB release successful........................................................... 2360
20.2.6.6 RAB release not successful..................................................... 2361
20.2.7 RAB release request................................................................ 2362
20.2.8 Paging message...................................................................... 2366
20.2.9 Location reporting control.........................................................2368
20.2.10 Location report ........................................................................ 2369
20.2.11 Overload control.......................................................................2369
20.2.12 Reset........................................................................................2370
20.2.13 Error indication......................................................................... 2373
20.2.14 Subscriber trace control........................................................... 2374
20.2.15 Location Related Data Request............................................... 2374
20.2.16 Location Related Data..............................................................2375
20.2.17 Location Related Data Failure..................................................2376
20.3 Iu interface availability..............................................................2376

21 Measurement: L3 relocation signalling (M1009)...................... 2379
21.1 Introduction to L3 relocation signalling measurement..............2379
21.2 RNSAP and RANAP procedures for serving RNS relocation.. 2379
21.2.1 Relocation commit (Iur)............................................................ 2379
21.2.1.1 Relocation commit (by source RNC) (Iur)................................ 2380
21.2.1.2 Relocation commit (by target RNC) (Iur)..................................2380
21.2.2 Relocation preparation (by source RNC) (Iu)...........................2381
21.2.2.1 SRNS relocation attempts........................................................2381
21.2.2.2 SRNS successful relocation preparations (Iu)......................... 2383
21.2.2.3 SRNS unsuccessful relocation preparations (Iu) .................... 2384
21.2.3 Relocation resource allocation (by target RNC) (Iu)................ 2396
21.2.3.1 SRNS relocation attempts........................................................2396
21.2.3.2 SRNS successful relocation preparations (Iu)......................... 2398
21.2.3.3 SRNS unsuccessful relocation preparations (Iu)..................... 2399
21.2.4 Relocation cancel (by source RNC) (Iu)................................... 2411
21.2.5 Relocation detect (by target RNC) (Iu).....................................2425
21.2.6 Relocation complete (by target RNC) (Iu)................................ 2426
21.2.7 Iu release request (Iu).............................................................. 2428
21.2.7.1 Iu release request for SRNS relocation (by source RNC)........2428
21.2.7.2 Iu release request for SRNS relocation (by target RNC)......... 2438
21.2.8 Forwarding of data on Iur (by Source RNC) (Iur)..................... 2449
21.3 Inter-RNC hard handover.........................................................2449
16 DN99581291 Issue: 12G
21.3.1 Relocation commit (Iur)............................................................ 2449

21.3.1.1 Relocation commit (by source RNC)........................................2450
21.3.1.2 Relocation commit (by target RNC)......................................... 2450
21.3.2.1 Inter-RNC hard handover relocation attempts......................... 2451
21.3.2.2 Inter-RNC hard handover successful relocation preparations (Iu)...
2453
21.3.2.3 Inter-RNC hard handover unsuccessful relocation preparations
(Iu)............................................................................................2454
21.3.3.1 Inter-RNC hard handover relocation attempts......................... 2465
21.3.3.2 Inter-RNC hard handover successful relocation preparations (Iu)...
2467
21.3.3.3 Inter-RNC hard handover unsuccessful relocation preparations
(Iu)............................................................................................2469
21.3.4 Relocation cancel (by source RNC) (Iu)...................................2480
21.3.5 Relocation detect (by target RNC) (Iu).....................................2493
21.3.7.1 Iu release request for inter-RNC HHO relocation (by source RNC).
2497
21.3.7.2 Iu release request for inter-RNC HHO relocation (by target RNC)..
2507
21.3.8 Forward SRNS context (Iu)...................................................... 2517
21.3.8.1 Forward SRNS context (by source RNC) (Iu).......................... 2517
21.3.8.2 Forward SRNS context (by target RNC) (Iu)............................2518
21.4 Circuit-switched inter-system hard handover .......................... 2519
21.4.1.1 Inter-system hard handover relocation attempts......................2519
21.4.1.2 Inter-system hard handover successful relocation preparations
(Iu)............................................................................................2519
21.4.1.3 Inter-system hard handover unsuccessful relocation preparations
(Iu) ...........................................................................................2520
21.4.2.1 Inter-system hard handover relocation attempts......................2524
21.4.2.2 Inter-system hard handover successful relocation preparations
(Iu)............................................................................................2524
21.4.2.3 Inter-system hard handover unsuccessful relocation preparations
(Iu)............................................................................................2525
21.4.3 Relocation cancellation (by source RNC) (Iu) ......................... 2529
21.4.5.1 Iu release request for inter-system HHO relocation (by source
RNC)........................................................................................ 2534
21.4.5.2 Iu release request for inter-system HHO relocation (by target
RNC)........................................................................................ 2538
21.5 Packet-switched inter-system hard handover.......................... 2541
21.5.1 Forwarding of data on Iu (by source RNC) (Iu)........................ 2541
Issue: 12G DN99581291 17
21.5.2 SRNS context request (by source RNC) (Iu)........................... 2542

21.5.3 SRNS context response (by source RNC) (Iu).........................2542
21.5.4 SRNS data forward command (by source RNC) (Iu)............... 2543
21.6 LTE handover........................................................................... 2544
21.6.1 Incoming CS handover from LTE............................................. 2544
21.6.2 Incoming PS handover from LTE............................................. 2551

22 Measurement: LTE relocation (M1036).................................... 2564
22.1 Outgoing PS inter-system handover to LTE............................. 2564

23 Measurement: Service area broadcast (M1012)......................2571
23.1 Introduction to service area broadcast measurement.............. 2571
23.2 Write-replace............................................................................ 2571
23.3 Kill............................................................................................ 2573
23.4 Message status........................................................................ 2575
23.5 Load status enquiry..................................................................2576
23.6 Reset........................................................................................2577
23.7 Restart......................................................................................2578
23.8 Failure...................................................................................... 2579
23.9 Error indication......................................................................... 2579

24 Measurement: Neighbour cell (M1013, M1014, M1015)..........2581
24.1 Introduction to neighbour cell measurements.......................... 2581
24.2 Autodef SHO (Neighbour cells in soft handovers) (M1013)..... 2582
24.2.1 Soft handover success rate......................................................2582
24.2.2 CPICH Ec/No and RSCP......................................................... 2583
24.3 Autodef IFHO (Neighbour cells in intra-system hard handovers)
(M1014)....................................................................................2588
24.4 Autodef ISHO (Neighbour cells in inter-system handovers)
(M1015)....................................................................................2592

25 Measurement: Autodef SHO DSR (M1028)............................. 2597
25.1 Introduction to Autodef SHO DSR measurement.....................2597
25.2 Autodef SHO DSR counters.....................................................2597

26 Measurement: Autodef LTE (M1019)....................................... 2601

27 Measurement: Iu-PC Interface (M1021)...................................2603
27.1 Introduction to Iu-PC interface measurement.......................... 2603
27.2 Iu-PC interface counters.......................................................... 2603
27.3 SAS-centric Iu-PC.................................................................... 2608
27.4 LCS periodic reporting............................................................. 2613
27.5 Broadcast of A-GPS Assistance Data......................................2617

28 Measurement: CPICH Quality (M1033)................................... 2621
28.1 CPICH EcNo in RRC Connection Request.............................. 2621
28.2 CPICH RSCP in RRC Connection Request.............................2627

29 Measurement: Operator Statistics in RNC (M1034).................2637
18 DN99581291 Issue: 12G
29.1 Inter-system handover............................................................. 2637

29.2 Data volume............................................................................. 2640
29.3 Code occupancy...................................................................... 2642
29.4 RAB statistics........................................................................... 2644
29.5 HSPA statistics......................................................................... 2657
29.6 Operator share configuration................................................... 2668

30 Measurement: DSCP Statistics (M1035)................................. 2670

31 Signaling diagrams...................................................................2677
31.1 RRC connection setup............................................................. 2677
31.1.1 RRC connection setup on DCH (ATM).....................................2678
31.1.2 RRC connection setup on CCH............................................... 2679
31.1.3 RRC connection setup on HSPA (IP)....................................... 2680
31.1.4 RRC connection setup - cell reselection.................................. 2681
31.1.5 RRC connection setup failure and retry................................... 2682
31.1.6 Directed RRC connection setup - success...............................2683
31.1.7 Directed RRC connection setup - access failure......................2684
31.1.8 Directed RRC connection setup - setup failure........................ 2685
31.2 RAB setup................................................................................ 2685
31.2.1 RAB setup - CS........................................................................2686
31.2.2 CS RAB setup with blind HO - success................................... 2687
31.2.3 CS RAB setup with blind HO - failure and retry....................... 2688
31.2.4 PS NRT RAB setup with Direct Resource Allocation enabled. 2689
31.2.5 PS NRT RAB setup with Direct Resource Allocation disabled.2690
31.2.6 PS NRT RAB setup with blind HO - success........................... 2691
31.3 PS call state transition..............................................................2691
31.3.1 DCH 0/0 to HSUPA user plane allocation................................ 2692
31.3.2 DCH x/y to HSUPA channel type switch (ATM)........................2693
31.3.3 FACH to HSDPA state transition.............................................. 2694
31.4 3G mobility............................................................................... 2694
31.4.1 Inter-BTS HSUPA serving cell change..................................... 2695
31.4.2 HSDPA serving cell change over Iur........................................ 2696
31.4.3 HSDPA serving cell change over Iur - failure........................... 2697
31.4.4 UE-not-involved SRNC relocation (CS voice).......................... 2698
31.4.5 UE-not-involved SRNC relocation (CS+PS).............................2699
31.4.6 Inter-RNC inter-frequency HHO, target RNC (CS voice)......... 2701
31.5 LTE mobility..............................................................................2701
31.5.1 CS fallback handover from LTE to WCDMA.............................2702
31.5.2 PS call handover from LTE to WCDMA....................................2703
31.5.3 CS+PS call SRVCC handover from LTE to WCDMA............... 2704
31.5.4 Redirection to LTE with measurements....................................2705
31.5.5 PS call handover from WCDMA to LTE....................................2706
Issue: 12G DN99581291 19
List of Figures
Figure 1 RAB types...........................................................................................56
Figure 2 Triggering of the most important RRC counters................................. 64
Figure 3 Triggering of the most important RAB counters..................................66
Figure 4 Failure/release causes used in different RRC/RAB phases............... 68
Figure 5 Triggering of RRC setup counters...................................................... 72
Figure 6 Example of multi-RAB connections.................................................. 433
Figure 7 Packet call example scenario........................................................... 506
Figure 8 Packet call example scenario (cont.)................................................507
Figure 9 Location calculations using Cell ID/RTT method.............................. 658
Figure 10 Location calculations using UE based A-GPS method.....................659
Figure 11 Location calculations using network based A-GPS method............. 660
Figure 12 Location related data requests......................................................... 661
Figure 13 PrxTotal load areas...........................................................................718
Figure 14 PtxTotal load areas when there are no HS-DSCH users in cell........748
Figure 15 DCH counters in SRNC side - part 1................................................ 958
Figure 16 DCH counters in SRNC side - part 2................................................ 959
Figure 17 DCH counters in DRNC side............................................................ 960
Figure 18 RT DCH allocation............................................................................ 961
Figure 19 NRT DCH allocation......................................................................... 962
Figure 20 Triggering of HSDPA counters in traffic measurement..................... 968
Figure 21 HS-DSCH release counters for interactive class..............................969
Figure 22 Relationships between E-DCH release counters............................. 970
Figure 23 Compressed mode allocation counters in SRNC............................. 971
Figure 24 Compressed mode allocation counters in DRNC............................. 971
Figure 25 Protocol stack and unit architecture of the cell throughput
measurement..................................................................................1315
Figure 26 Measurement point in RCPM OLPC measurement........................1347
Figure 27 Scope of the RCPM RLC measurement.........................................1362
Figure 28 Triggering of soft handover counters.............................................. 1510
Figure 29 Triggering of intra-system intra-frequency hard handover counters for
RT/NRT traffic.................................................................................1560
Figure 30 Inter-frequency HHO (RT/NRT): Inter-RNC case........................... 1561
Figure 31 Inter-frequency HHO (RT/NRT): Intra-RNC case........................... 1562
Figure 32 Intra-BTS HS-DSCH serving cell change....................................... 1731
Figure 33 Inter-BTS HS-DSCH serving cell change....................................... 1732
Figure 34 Triggering of inter-system handover counters for RT traffic........... 1768
Figure 35 Triggering of inter-system handover counters for NRT traffic......... 1769
Figure 36 RRC connection setup on DCH (ATM)........................................... 2678
Figure 37 RRC connection setup on CCH......................................................2679
20 DN99581291 Issue: 12G
Figure 38 RRC connection setup on HSPA (IP)............................................. 2680

Figure 39 RRC connection setup - cell reselection.........................................2681
Figure 40 RRC connection setup failure and retry..........................................2682
Figure 41 Directed RRC connection setup - success..................................... 2683
Figure 42 Directed RRC connection setup - access failure............................ 2684
Figure 43 Directed RRC connection setup - setup failure.............................. 2685
Figure 44 RAB setup - CS.............................................................................. 2686
Figure 45 CS RAB setup with blind HO - success..........................................2687
Figure 46 CS RAB setup with blind HO - failure and retry..............................2688
Figure 47 PS NRT RAB setup with Direct Resource Allocation enabled........2689
Figure 48 PS NRT RAB setup with Direct Resource Allocation disabled....... 2690
Figure 49 PS NRT RAB setup with blind HO - success..................................2691
Figure 50 DCH 0/0 to HSUPA user plane allocation.......................................2692
Figure 51 DCH x/y to HSUPA channel type switch (ATM).............................. 2693
Figure 52 FACH to HSDPA state transition.................................................... 2694
Figure 53 Inter-BTS HSUPA serving cell change........................................... 2695
Figure 54 HSDPA serving cell change over Iur.............................................. 2696
Figure 55 HSDPA serving cell change over Iur - failure................................. 2697
Figure 56 UE-not-involved SRNC relocation (CS voice)................................ 2698
Figure 57 UE-not-involved SRNC relocation (CS+PS)................................... 2699
Figure 58 UE-not-involved SRNC relocation (CS+PS) (cont.)........................2700
Figure 59 Inter-RNC inter-frequency HHO, target RNC (CS voice)................2701
Figure 60 CS fallback handover from LTE to WCDMA................................... 2702
Figure 61 PS call handover from LTE to WCDMA.......................................... 2703
Figure 62 CS+PS call SRVCC handover from LTE to WCDMA..................... 2704
Figure 63 Redirection to LTE with measurements.......................................... 2705
Figure 64 PS call handover from WCDMA to LTE.......................................... 2706
Issue: 12G DN99581291 21
List of Tables
Table 1 Service level measurement object identifiers..................................... 62
Table 2 Failure/release cause explanations.................................................... 68
Table 3 Counters in multi-RAB example figure............................................. 433
Table 4 Packet Call measurement object identifiers..................................... 505
Table 5 Location services measurement object identifiers............................657
Table 6 Cell resource measurement object identifiers.................................. 709
Table 7 PrxTotal load areas...........................................................................716
Table 8 PtxTotal load areas........................................................................... 746
Table 9 Transmitted code power................................................................... 837
Table 10 BTS channel element usage estimation per DCH bitrate ................ 909
Table 11 Traffic measurement object identifiers..............................................956
Table 12 Cell Throughput measurement object identifiers............................ 1314
Table 13 M1032 measurement object identifiers...........................................1333
Table 14 RCPM RLC measurement object identifiers...................................1361
Table 15 Soft handover measurement object identifiers............................... 1509
Table 16 CPICH Ec/No distribution classes (mapping based on 3GPP TS
25.133)........................................................................................... 1512
Table 17 Intra-system hard handover measurement object identifiers..........1557
Table 18 Inter-system handover measurement object identifiers..................1766
Table 19 RRC signalling measurement object identifiers..............................1946
Table 20 Mapping of PRACH Propagation Delay values to counters........... 2096
Table 21 Estimating UE-BTS distance in meters based on PRACH Propagation
Delay value.....................................................................................2097
Table 22 L3 signalling at Iub measurement object identifiers........................2120
Table 23 L3 signalling at Iur measurement object identifiers........................ 2235
Table 24 L3 signalling at Iu measurement object identifiers..........................2345
Table 25 L3 relocation signalling measurement object identifiers................. 2379
Table 26 Autodef LTE measurement object identifiers.................................. 2564
Table 27 Autodef SHO and AutoDef IFHO measurement object identifiers..2581
Table 28 Autodef ISHO measurement object identifiers............................... 2581
Table 29 Filtering of Ec/No values.................................................................2584
Table 30 Autodef LTE measurement object identifiers.................................. 2601
Table 31 Counter-feature relationship and used measurement object..........2670
22 DN99581291 Issue: 12G

RNC Counters - RNW Part Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 12F (2015-05-11, RU50) and 12G (2016-02-19, RU50)
Modified counters
Measurement: L3 signalling at Iub (M1005)
• M1005C255
Measurement: RRC Signalling (M1006)
• M1006C251
• M1006C252
Measurement: Inter-system handover (M1010)
• M1010C270
Measurement: RCPM OLPC (M1016)
• M1016C8
• M1016C9
Measurement: RCPM OLPC WCEL (M1024)
• M1024C8
• M1024C9
Measurement: RCPM OLPC RNC (M1025)
• M1025C8
• M1025C9
Removed Counters
g Note: These counters are removed as they are not supported.
Measurement: L3 signalling at Iub (M1005)
• M1005C256
• M1005C257
Changes between issues 12E (2014-10-30, RU50) and 12F (2015-05-11, RU50)
List of measurements in chapter Radio network measurements has been updated.
Chapter Introduction to Autodef SHO DSR measurement has been updated.
Modifications to existing counters
Measurement: RRC signalling (M1006)
• M1006C65
• M1006C228
Issue: 12G DN99581291 23

Summary of changes RNC Counters - RNW Part
Changes between issues 12D (2014-08-26, RU50) and 12E (2014-10-30, RU50)
PrxTotal load areas has been updated.
Modifications to existing counters
Measurement: Packet Call (M1022)
• M1022C224
• M1022C248
24 DN99581291 Issue: 12G

RNC Counters - RNW Part Radio network measurements
1 Radio network measurements

This document provides information on the radio network measurements collected from
the RNC. The following measurements are available in the current release:
• M1000 Cell resource
• M1001 Service level
• M1002 Traffic
• M1003 L3 signalling at Iu
• M1004 L3 signalling at Iur
• M1005 L3 signalling at Iub
• M1006 RRC signalling
• M1007 Soft handover
• M1008 Intra-system hard handover
• M1009 L3 relocation signalling
• M1010 Inter-system handover
• M1011 Location services
• M1012 Service area broadcast
• M1013 Autodef SHO
• M1014 Autodef IFHO
• M1015 Autodef ISHO
• M1016 RCPM OLPC
• M1017 RCPM RLC
• M1018 RCPM UEQ
• M1019 Autodef LTE
• M1021 Iu-PC Interface
• M1022 Packet call
• M1023 Cell throughput
• M1024 RCPM OLPC WCEL
• M1025 RCPM OLPC RNC
• M1026 RCPM RLC WCEL
• M1027 RCPM RLC RNC
• M1028 Autodef SHO DSR
• M1031 WBTS Resource
• M1032 CS Voice HSPA User Plane
• M1033 CPICH Quality
• M1034 Operator Statistics in RNC
• M1035 DSCP Statistics
• M1036 LTE Relocation
The corresponding measurement chapters describe
• Measurement objects, measurement content in general, and so on.
• Detailed counter information: counter identifiers, descriptions, update reasons, and
so on.
For information on radio network measurement management, see the WCDMA RAN
performance management document.
Issue: 12G DN99581291 25

Radio network measurements RNC Counters - RNW Part
For an overall summary of all RNC performance monitoring, see How to find
performance monitoring documentation, which includes a complete list of monitoring-
related RNC documentation.
In addition to the radio network measurements listed above, RNC-OMS collects
measurements from the base stations. The counters of these measurements are
described in the WCDMA Base Station counter documentation.
1.1 Status of counters

The following list contains counters that can be found from the measurements, but which
do not provide useful information (for example, because related functionality is not
supported in this release).
Measurement name: Cell Resource
• M1000C152 RB DOWNGRADE BY PRE-EMPTION DUE TO INTERFERENCE
CONGESTION
• M1000C156 CELL RESOURCE SPARE 3
• M1000C161 CELL RESOURCE SPARE 4
• M1000C197 AVERAGE USED CE FOR PS STREAMING 384 KBPS DL
Measurement name: Service Level
• M1001C69 SETUP ATTEMPTS FOR PS DATA CONV
• M1001C76 RAB SETUP COMPLETIONS FOR PS DATA CONV
• M1001C95 RAB SETUP FAILURES DUE TO AC FOR PS DATA CONV
• M1001C96 RAB SETUP FAILURES DUE TO BTS FOR PS DATA CONV
• M1001C97 RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA CONV
• M1001C98 RAB SETUP FAILURES DUE TO RNC FOR PS DATA CONV
• M1001C99 RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA CONV
• M1001C118 RAB ACCESS COMPLETIONS FOR PS DATA CONV
• M1001C128 RAB SETUP ACC FAIL FOR PS DATA CALL CONV CLASS DUE TO
UE
• M1001C129 RAB SETUP ACC FAIL FOR PS DATA CALL CONV CLASS DUE TO
RNC INTERNAL
• M1001C139 RAB ACTIVE COMPLETIONS FOR PS DATA CONV
• M1001C167 RAB ACTIVE RELEASES DUE TO SRNC RELOC FOR PS DATA
CONV
• M1001C168 RAB ACTIVE RELEASES DUE TO PRE-EMPTION FOR PS DATA
CONV
• M1001C173 RAB ACTIVE FAILURES DUE TO IU FOR PS DATA CONV
• M1001C174 RAB ACTIVE FAILURES DUE TO RADIO INT FOR PS DATA CONV
• M1001C175 RAB ACTIVE FAILURES DUE TO BTS FOR PS DATA CONV
• M1001C176 RAB ACTIVE FAILURES DUE TO IUR FOR PS DATA CONV
• M1001C178 RAB ACTIVE FAILURES DUE TO RNC FOR PS DATA CONV
• M1001C198 RAB RECONFIGURATION FAILURES
• M1001C205 SUM OF RAB HOLDING TIMES FOR PS DATA CONV
• M1001C206 DENOMINATOR FOR RAB HOLDING TIME FOR PS DATA CONV
26 DN99581291 Issue: 12G

• M1001C229 SUM OF RAB SETUP TIMES FOR PS DATA CONV
• M1001C230 DENOMINATOR FOR SUM OF RAB SETUP TIMES FOR PS DATA
CONV
• M1001C243 RAB ACT COMP FOR PS CALL USING IPHC CONV CLASS
• M1001C244 RAB ACT COMP FOR PS CALL USING IPHC STREAM CLASS
• M1001C245 RAB ACT COMP FOR PS CALL USING ROHC CONV CLASS
• M1001C246 RAB ACT COMP FOR PS CALL USING ROHC STREAM CLASS
• M1001C251 RAB ACTIVE COMPLETIONS IN SAME CELL FOR PS DATA CONV
• M1001C390 UE SUPPORT FOR ROHC
• M1001C395 RAB ACTIVE FAILURES DUE TO UE FOR PS DATA CONV
• M1001C399 RRC SETUP FAIL DUE TO IUB AAL2 TRANS
• M1001C400 RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS VOICE
• M1001C401 RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS DATA
CONV
• M1001C402 RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS DATA
STREAM
• M1001C403 RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR PS DATA
STREAM
• M1001C447 RAB PS DATA CONV LEAVES OLD REF CELL
• M1001C470 RAB PS DATA CONV ENTERS NEW REF CELL
• M1001C737 RAB SETUP ATTEMPTS FOR PTT
• M1001C738 RAB ACCESS COMPLETIONS FOR PTT
• M1001C739 RAB ACTIVE COMPLETIONS FOR PTT
• M1001C740 RAB SETUP AND ACCESS FAILURESFOR PTT
• M1001C741 RAB ACTIVE FAILURES FOR PTT
• M1001C742 RAB HOLDING TIME FOR PTT
Measurement name: Traffic
• M1002C19 RT DCH ALLO FOR AMR 5.15 KBPS IN UL IN SRNC
• M1002C27 RT DCH ALLO FOR AMR 5.15 KBPS IN DL IN SRNC
• M1002C35 RT DCH ALLO DURA FOR AMR 5.15 KBPS IN UL IN SRNC
• M1002C43 RT DCH ALLO DURA FOR AMR 5.15 KBPS IN DL IN SRNC
Issue: 12G DN99581291 27

• M1002C82 RT DCH REQ FOR PS CALL CONV CLASS IN SRNC
• M1002C88 RT DCH REQ FOR PS CALL CONV CLASS REJECT IN UL IN SRNC
• M1002C89 RT DCH REQ FOR PS CALL CONV CLASS REJECT IN DL IN SRNC
• M1002C96 RT DCH INI REQ FOR PS CALL CONV CLASS IN SRNC
• M1002C102 RT DCH DHO REQ FOR PS CALL CONV CLASS IN SRNC
• M1002C103 RT DCH DHO REQ FOR PS CALL CONV CLASS REJECT IN SRNC
• M1002C110 RT DCH ALLO FOR PS CALL CONV CLASS 8 KBPS IN UL IN SRNC
• M1002C114 RT DCH ALLO FOR PS CALL CONV CLASS 128 KBPS IN UL IN
SRNC
SRNC
SRNC
• M1002C118 RT DCH ALLO FOR PS CALL CONV CLASS 8 KBPS IN DL IN SRNC
• M1002C122 RT DCH ALLO FOR PS CALL CONV CLASS 128 KBPS IN DL IN
SRNC
SRNC
SRNC
• M1002C131 RT DCH ALLO FOR PS CALL STREAM CLASS 256 KBPS IN UL IN
SRNC
• M1002C133 RT DCH ALLO FOR PS CALL STREAM CLASS 384 KBPS IN UL IN
SRNC
• M1002C174 RT DCH ALLO DUR FOR PS CALL CONV CLASS 8 KBPS IN UL IN
SRNC
SRNC
SRNC
SRNC
SRNC
SRNC
SRNC
• M1002C182 RT DCH ALLO DUR FOR PS CALL CONV CLASS 8 KBPS IN DL IN
SRNC
SRNC
28 DN99581291 Issue: 12G

SRNC
SRNC
SRNC
SRNC
SRNC
• M1002C195 RT DCH ALLO DUR FOR PS CALL STREAM CLASS 256 KBPS IN UL
IN SRNC
• M1002C197 RT DCH ALLO DUR FOR PS CALL STREAM CLASS 384 KBPS IN UL
IN SRNC
• M1002C347 RT DCH HHO REQ FOR PS CALL CONV CLASS IN SRNC
• M1002C348 RT DCH HHO REQ FOR PS CALL CONV CLASS REJECT IN SRNC
• M1002C589 HS-DSCH RETURN
• M1002C590 HS-DSCH RETURN CH DOWNGRADES FOR STREAMING
• M1002C679 SC-HSDPA SELECTED DUE TO UL LOAD
• M1002C683 HS-DSCH MAC-D FLOW ALLOCATIONSFOR PTT
• M1002C684 E-DCH ALLOCATIONS FOR PTT
Measurement name: L3 signalling at Iu
• M1003C21 RAB RECONF NONSUCC DUE TO TR LAYER CAUSE
• M1003C22 RAB RECONF NONSUCC DUE TO NAS CAUSE
• M1003C23 RAB RECONF NONSUCC DUE TO PROT CAUSE
• M1003C25 RAB RECONF NONSUCC DUE TO NON STAN CAUSE
L3 signalling at Iub
• M1005C256 RL ADDITION REJECTED DUE TO OVERLOAD
• M1005C257 RL RECONFIGURATION REJECT DUE TO OVERLOAD
Measurement name: RRC signalling
• M1006C258 SUCCESSFUL HIGH PEAK RATE UEREDIRECTIONS TO MCRNC
• M1006C259 SUCCESSFUL LOW PEAK RATE UEREDIRECTIONS TO MCRNC
DUE TO LOAD BALANCING
• M1006C260 HIGH PEAK RATE UE ADMITTED TO IPARNCDUE TO LOAD
BALANCING
• M1006C261 FAILED REDIRECTIONS TO MCRNC
• M1006C70 RRC CONN REJECT DUE TO RRC CONNECTION SETUP
REDIRECTION
• M1006C71 CELL DCH TO CELL FACH STATE TRANSITIONS DUE TO PS
INTERRUPTION TIMER
• M1006C78 SPARE COUNTER 1 FOR RRC
• M1006C97 SQUARED SUM OF UE OPERATING TIME IN URA_PCH
Issue: 12G DN99581291 29

• M1006C116 DCH RELEASE DUE TO HSDPA RESUMPTION TIMER
• M1006C117 DCH RELEASE DUE TO HSDPA RESUMPTION TIMER REJECTED
• M1006C207 RRC CONN REJECT DUE TO CN FAILURE
• M1006C297 SUCCESSFUL DCH STATE ALLOCATIONFOR PTT
• M1006C298 DCH STATE ALLOCATION FAILURESFOR PTT
• M1006C299 SUM OF PTT UE ACTIVE STATE OPERATINGTIMES
• M1006C300 DENOMINATOR FOR SUM OF PTT UEACTIVE STATE OPERATING
TIMES
Measurement name: RCPM OLPC measurement
• M1016C8 UL AVERAGE BER
• M1016C9 UL AVERAGE BER DENOMINATOR
Measurement name: RCPM OLPC WCEL
• M1024C8 UL AVERAGE BER FOR WCEL
• M1024C9 UL AVERAGE BER DENOMINATOR FOR WCEL
Measurement name: RCPM OLPC RNC
• M1025C8 UL AVERAGE BER FOR RNC
• M1025C9 UL AVERAGE BER DENOMINATOR FOR RNC
Counters which have never been updated
• M1002C679 TRAFFIC SPARE 1
• M1002C680 TRAFFIC SPARE 2
1.2 Optional counters

Some of the counters produced by the RNC are optional and if the related feature is
disabled, the counters will not be sent to NetAct and their value will always be zero in the
RNC Element Manager. If all the counters in the measurement are optional and the
related features are disabled, it is not even possible to start the measurement.
The following tables list the optional counters in each measurement type.
Measurement 1001
PI ID Name Feature
M1001C621 RAB SETUP FAILURES DUE TO IUR RAN1126

TRANSPORT FOR CS VOICE

TRANSPORT FOR CS CONV

TRANSPORT FOR CS STREAMING
30 DN99581291 Issue: 12G

PI ID Name Feature

TRANSPORT FOR PS STREAMING
M1001C625 RAB SETUP FAILURES DUE TO IU-CS RAN1126

TRANSPORT FOR CS VOICE

TRANSPORT FOR CS CONV

TRANSPORT FOR CS STREAMING
M1001C659 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

RATE - CLASS 1

RATE - CLASS 2

RATE - CLASS 3

RATE - CLASS 4

RATE - CLASS 5

RATE - CLASS 6

RATE - CLASS 7
M1001C666 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

RATE - CLASS 1

RATE - CLASS 2

RATE - CLASS 3

RATE - CLASS 4

RATE - CLASS 5
Measurement 1002
Issue: 12G DN99581291 31

PI ID Name Feature
M1002C553 NRT DCH SETUP REJECT FOR RAN1126

INTERACTIVE DUE TO OUT OF CODES DL

BACKGROUND DUE TO OUT OF CODES DL

INTERACTIVE DUE TO POWER LIMITS DL

BACKGROUND DUE TO POWER LIMITS DL
M1002C557 NRT DCH RECONFIG REJECT FOR RAN1126

INTERACTIVE DUE TO OUT OF CODES DL

BACKGROUND DUE TO OUT OF CODES DL

INTERACTIVE DUE TO POWER LIMITS DL

BACKGROUND DUE TO POWER LIMITS DL

INTERACTIVE DUE TO POWER LIMITS UL

BACKGROUND DUE TO POWER LIMITS UL

INTERACTIVE DUE TO POWER LIMITS UL

BACKGROUND DUE TO POWER LIMITS UL
Measurement 1004
PI ID Name Feature
TRANSFERRED DATA FOR AMR IN UL
M1004C147 FROM DRNC RAN1101
TRANSFERRED DATA FOR AMR IN DL TO
M1004C148 DRNC RAN1101
TRANSFERRED DATA FOR INTERACTIVE IN
M1004C149 UL FROM DRNC RAN1101
32 DN99581291 Issue: 12G

PI ID Name Feature
M1004C150 DL TO DRNC RAN1101
TRANSFERRED DATA FOR BACKGROUND
M1004C151 IN UL FROM DRNC RAN1101
M1004C152 IN DL TO DRNC RAN1101
TRANSFERRED DATA FOR CS
M1004C153 CONVERSATIONAL IN UL FROM DRNC RAN1101
M1004C154 CONVERSATIONAL IN DL TO DRNC RAN1101
TRANSFERRED DATA FOR CS STREAMING
TRANSFERRED DATA FOR PS STREAMING
M1004C159 DCH IN UL RAN1101
M1004C160 DCH IN DL RAN1101
TRANSFERRED DATA FOR NRT
M1004C161 INTERACTIVE DCH IN UL RAN1101
M1004C162 INTERACTIVE DCH IN DL RAN1101
M1004C163 BACKGROUND DCH IN UL RAN1101
M1004C164 BACKGROUND DCH IN DL RAN1101
M1004C165 NRT DCH SETUP FAIL DUE TO IUR RAN1126
NRT DCH UL RECONFIG FAIL FOR NRT RB
M1004C166 DUE TO IUR RAN1126
Issue: 12G DN99581291 33

PI ID Name Feature
NRT DCH DL RECONFIG FAIL FOR NRT RB
M1004C167 DUE TO IUR RAN1126
M1004C168 SHO BRANCH SETUP FAIL DUE TO IUR RAN1126
M1004C169 TRANSFERRED DATA FOR NRT HSDPA RAN1101

RETURN CHANNEL FROM DRNC
M1004C170 TRANSFERRED DATA FOR RT HSDPA RAN1101

RETURN CHANNEL FROM DRNC
Measurement 1007
PI ID Name Feature
SHO BRANCH SETUP FAILURES DUE TO
M1007C71 BTS RAN1126
SHO BRANCH SETUP FAILURES DUE TO
M1007C72 IUB TRANSMISSION RAN1126
Measurement 1013
PI ID Name Feature
NUMBER OF INTRA FREQUENCY SHO
M1013C0 ATTEMPTS RAN189
NUMBER OF COMPLETED INTRA
M1013C1 FREQUENCY SHO RAN189
CPICH ECNO SHO DIFFERENCE
M1013C2 SUMMATION RAN189
CPICH ECNO SHO DIFFERENCE
M1013C3 DENOMINATOR RAN189
M1013C4 CPICH ECNO SHO SUM RAN1191
M1013C5 CPICH ECNO SHO DENOM RAN1191
M1013C6 CPICH RSCP SHO SUM RAN1191
M1013C7 CPICH RSCP SHO DENOM RAN1191
Measurement 1014
34 DN99581291 Issue: 12G

PI ID Name Feature
NUMBER OF INTER FREQUENCY HHO
NUMBER OF COMPLETED INTER
M1014C1 FREQUENCY HHO RAN189
M1014C2 CPICH ECNO IFHO SUM RAN1245
M1014C3 CPICH ECNO IFHO DENOMINATOR RAN1245
M1014C4 CPICH RSCP IFHO SUM RAN1245
M1014C5 CPICH RSCP IFHO DENOMINATOR RAN1245
Measurement 1015
PI ID Name Feature
NUMBER OF INTER SYSTEM HHO
NUMBER OF COMPLETED INTER SYSTEM
M1015C1 HHO RAN189
M1015C2 RSSI SUM RAN1245
M1015C3 RSSI DENOMINATOR RAN1245
M1015C4 BSIC VERIFICATION TIME RAN1245
M1015C5 BSIC DENOMINATOR RAN1245
Measurement 1016
PI ID Name Feature
M1016C0 AVERAGE UL EB/NO RAN190
M1016C1 UL AVERAGE EB/NO DENOMINATOR RAN190
M1016C2 UL SUM OF SQUARED EB/NO VALUES RAN190
UL NUMBER OF RECEIVED EB/NO
M1016C3 REPORTS RAN190
Issue: 12G DN99581291 35

PI ID Name Feature
M1016C4 UPLINK CRC OK BLOCKS RAN190
M1016C5 UPLINK CRC NOK BLOCKS RAN190
M1016C6 SUM OF SQUARED BLER VALUES RAN190
M1016C7 UL NUMBER OF RECEIVED BLER REPORTS RAN190
M1016C8 UL AVERAGE BER RAN190
M1016C9 UL AVERAGE BER DENOMINATOR RAN190
M1016C10 SUM OF SQUARED UL BER VALUES RAN190
UL NUMBER OF RECEIVED UL BER
M1016C11 REPORTS RAN190
M1016C12 BAD UPLINK CONNECTIONS RAN190
M1016C13 IDEAL UPLINK CONNECTIONS RAN190
M1016C14 TOO GOOD UPLINK CONNECTIONS RAN190
M1016C15 AVERAGE RADIO LINK POWER IN DL RAN190
SUM OF SQUARED RADIO LINK POWER
M1016C16 VALUES IN DL RAN190
M1016C17 DL RADIO LINK POWER SAMPLES RAN190
RL REPORTS WITH MAXIMUM POWER
M1016C18 VALUE RAN190
M1016C19 UL E-DCH HARQ RETRANSMISSIONS RAN190
Measurement 1017
PI ID Name Feature
AVERAGE AM RLC TRANSMISSION BUFFER
M1017C0 OCCUPANCY RAN953
M1017C1 AVERAGE PDCP BUFFER OCCUPANCY RAN953
SUM OF SQUARED AM RLC BUFFER
M1017C2 OCCUPANCY VALUES RAN953
36 DN99581291 Issue: 12G

PI ID Name Feature
SUM OF SQUARED PDCP BUFFER
M1017C3 OCCUPANCY VALUES RAN953
REPORTS FOR AVERAGE DL BUFFER
M1017C4 OCCUPANCY RAN953
M1017C5 DL PDU ERROR RATIO IN AM RLC RAN953
AM RLC PDUS TRANSMITTED IN
M1017C6 DOWNLINK RAN953
M1017C7 SUM OF SQUARED DL PDU ERROR RATIO RAN953
M1017C8 RECEIVED DL PDU REPORTS RAN953
M1017C9 BAD RLC AM DL CONNECTIONS RAN953
M1017C10 TOO GOOD RLC AM DL CONNECTIONS RAN953
M1017C11 IDEAL RLC AM DL CONNECTIONS RAN953
M1017C12 DL GROSS THROUGHPUT OF AM RLC PDU RAN953
SUM OF SQUARED DL GROSS
M1017C13 THROUGHPUT OF RLC AM PDU RAN953
M1017C14 REPORTS FOR DL AM RLC THROUGHPUT RAN953
M1017C15 DL NET THROUGHPUT OF AM RLC PDU RAN953
SUM OF SQUARED DL NET THROUGHPUT
M1017C16 OF AM RLC PDU RAN953
SUM OF SQUARED TRANSMISSION TIME
M1017C17 VALUES FOR DL AM RLC RAN953
AVERAGE NUMBER OF TRANSMISSIONS
M1017C18 PER PDU IN AM RLC DL RAN953
M1017C19 PDU DISCARD RATIO IN AM RLC DL RAN953
SUM OF SQUARED AVE NUMBER OF PDU
M1017C20 TRANSMISSIONS RAN953
M1017C21 AM RLC DL PDUS FOR TRANSMISSION RAN953
M1017C22 RLC AM SDU DL ERROR RATIO RAN953
SUM OF SQUARED RLC AM SDU DL ERROR
M1017C23 RATIO RAN953
Issue: 12G DN99581291 37

PI ID Name Feature
RLC AM DL AVERAGE TRANSFER DELAY
M1017C24 OF SDU RAN953
RLC AM DL SUM OF AVE TRANSFER DELAY
M1017C25 OF SDU RAN953
RLC AM DL SUM OF STANDARD
M1017C26 DEVIATIONS OF TRANSFER DELAY OF SDU RAN953
RLC AM DL SUM OF SQUARED
M1017C27 TRANSMISSION DELAY OF SDU RAN953
M1017C28 SDUS FOR TRANSMISSION IN RLC AM DL RAN953
MEASUREMENT TIME PERIOD FOR DL RLC
M1017C29 AM RAN953
M1017C30 UL RLC AM SDU PAYLOAD OF PS TRAFFIC RAN953
M1017C31 DL RLC AM SDU PAYLOAD OF PS TRAFFIC RAN953
M1017C32 TRANSMITTED AM RLC PDUS IN UPLINK RAN953
MEASUREMENT TIME PERIOD FOR UL RLC
M1017C33 AM RAN953
USER DL THROUGHPUT DISTRIBUTION -
M1017C34 CLASS 1 RAN953
38 DN99581291 Issue: 12G

PI ID Name Feature
RLC RETRANSMISSION DISTRIBUTION -
USER UL THROUGHPUT DISTRIBUTION -
Measurement 1018
Issue: 12G DN99581291 39

PI ID Name Feature
AVERAGE BLER FROM QUALITY
M1018C0 MEASUREMENTS RAN190
M1018C1 RECEIVED QUALITY REPORTS FROM UES RAN190
M1018C2 SUM OF SQUARED UEQ BLER VALUES RAN190
Measurement 1022
PI ID Name Feature
INITIAL DCH REQUESTS FOR BITRATE 64
M1022C83 KBPS AND LOWER UL RAN1126
M1022C84 KBPS AND LOWER DL RAN1126
M1022C85 KBPS UL RAN1126
M1022C86 KBPS DL RAN1126
DCH UPGRADE REQUESTS FOR BITRATE
M1022C91 64 KBPS AND LOWER UL RAN1126
M1022C92 64 KBPS AND LOWER DL RAN1126
M1022C93 128 KBPS UL RAN1126
M1022C94 128 KBPS DL RAN1126
M1022C95 256 KBPS UL RAN1126
40 DN99581291 Issue: 12G

PI ID Name Feature
M1022C96 256 KBPS DL RAN1126
M1022C97 384 KBPS UL RAN1126
M1022C98 384 KBPS DL RAN1126
INITIAL DCH ALLOCATION SUCCESS FOR
M1022C99 NRT BITRATE 64 KBPS AND LOWER UL RAN1126
M1022C100 NRT BITRATE 64 KBPS AND LOWER DL RAN1126
M1022C101 NRT BITRATE 128 KBPS UL RAN1126
M1022C102 NRT BITRATE 128 KBPS DL RAN1126
INITIAL DCH ALLOCATION SUCCESS WITH
REQUESTED BITRATE 64 KBPS AND
M1022C107 LOWER UL RAN1126
REQUESTED BITRATE 64 KBPS AND
M1022C108 LOWER DL RAN1126
M1022C109 REQUESTED BITRATE 128 KBPS UL RAN1126
M1022C110 REQUESTED BITRATE 128 KBPS DL RAN1126
Issue: 12G DN99581291 41

PI ID Name Feature
DCH UPGRADE SUCCESS FOR BITRATE 64
M1022C115 KBPS AND LOWER UL RAN1126
DCH UPGRADE SUCCESS FOR BITRATE 64
M1022C116 KBPS AND LOWER DL RAN1126
DCH UPGRADE SUCCESS FOR BITRATE
M1022C117 128 KBPS UL RAN1126
M1022C118 128 KBPS DL RAN1126
M1022C119 256 KBPS UL RAN1126
M1022C120 256 KBPS DL RAN1126
M1022C121 384 KBPS UL RAN1126
M1022C122 384 KBPS DL RAN1126
DCH UPGRADE SUCCESS TO REQUESTED
M1022C123 BITRATE 64 KBPS AND LOWER UL RAN1126
M1022C124 BITRATE 64 KBPS AND LOWER DL RAN1126
M1022C125 BITRATE 128 KBPS UL RAN1126
M1022C126 BITRATE 128 KBPS DL RAN1126
42 DN99581291 Issue: 12G

PI ID Name Feature
DCH UPLINK RECONFIG FAIL DUE TO
M1022C131 TRANSPORT FOR INTERACTIVE RAN1126
M1022C132 TRANSPORT FOR BACKGROUND RAN1126
DCH DOWNLINK RECONFIG FAIL DUE TO
M1022C133 TRANSPORT FOR INTERACTIVE RAN1126
M1022C134 TRANSPORT FOR BACKGROUND RAN1126
DCH UPLINK RECONFIG FAIL DUE TO BTS
M1022C135 FOR INTERACTIVE RAN1126
DCH UPLINK RECONFIG FAIL DUE TO BTS
M1022C136 FOR BACKGROUND RAN1126
M1022C137 BTS FOR INTERACTIVE RAN1126
M1022C138 BTS FOR BACKGROUND RAN1126
DCH UPLINK RECONFIG FAIL DUE TO AC
M1022C139 FOR INTERACTIVE RAN1126
DCH UPLINK RECONFIG FAIL DUE TO AC
M1022C140 FOR BACKGROUND RAN1126
M1022C141 AC FOR INTERACTIVE RAN1126
M1022C142 AC FOR BACKGROUND RAN1126
M1022C143 OTHER REASONS FOR INTERACTIVE RAN1126
M1022C144 OTHER REASONS FOR BACKGROUND RAN1126
M1022C145 OTHER REASONS FOR INTERACTIVE RAN1126
Issue: 12G DN99581291 43

PI ID Name Feature
M1022C146 OTHER REASONS FOR BACKGROUND RAN1126
Measurement 1023
PI ID Name Feature
TRANSFERRED DATA FOR SIGNALLING RB
M1023C0 DCH UL RAN86
TRANSFERRED DATA FOR SIGNALLING RB
M1023C1 DCH DL RAN86
TRANSFERRED DATA FOR CS CALL DCH
M1023C2 UL RAN86
TRANSFERRED DATA FOR CS CALL DCH
M1023C3 DL RAN86
M1023C4 TRANSFERRED DATA FOR PS RT DCH UL RAN86
M1023C5 TRANSFERRED DATA FOR PS RT DCH DL RAN86
M1023C6 TRANSFERRED DATA FOR NRT DCH UL RAN86
M1023C7 TRANSFERRED DATA FOR NRT DCH DL RAN86
M1023C8 TRANSFERRED DATA FOR HS-DSCH RAN86
TRANSFERRED DATA FOR NRT DCH FOR
M1023C9 HSDPA RETURN CHANNEL UL RAN86
M1023C10 TRANSFERRED DATA FOR NRT E-DCH RAN86
M1023C11 TRANSFERRED DATA FOR AMR IN UL RAN1101
M1023C12 TRANSFERRED DATA FOR AMR IN DL RAN1101
M1023C13 CONVERSATIONAL IN UL RAN1101
M1023C14 CONVERSATIONAL IN DL RAN1101
M1023C15 IN UL RAN1101
44 DN99581291 Issue: 12G

PI ID Name Feature
M1023C16 IN DL RAN1101
M1023C19 UL RAN1101
M1023C20 DL RAN1101
TRANSFERRED DATA FOR RT E-DCH
M1023C23 STREAMING UL RAN1101
TRANSFERRED DATA FOR RT DCH
STREAMING FOR HSDPA RETURN
M1023C24 CHANNEL UL RAN1101
TRANSFERRED DATA FOR RT HS-DSCH
M1023C25 STREAMING DL RAN1101
M1023C26 TRANSFERRED HS-DSCH DATA FOR CS RAN86

VOICE
M1023C27 TRANSFERRED E-DCH DATA FOR CS RAN86

VOICE
Measurement 1024
PI ID Name Feature
M1024C0 AVERAGE UL EB/NO FOR WCEL RAN1188
UL AVERAGE EB/NO DENOMINATOR FOR
M1024C1 WCEL RAN1188
UL SUM OF SQUARED EB/NO VALUES FOR
Issue: 12G DN99581291 45

PI ID Name Feature
M1024C3 REPORTS FOR WCEL RAN1188
M1024C4 UPLINK CRC OK BLOCKS FOR WCEL RAN1188
M1024C5 UPLINK CRC NOK BLOCKS FOR WCEL RAN1188
SUM OF SQUARED BLER VALUES FOR
UL NUMBER OF RECEIVED BLER REPORTS
M1024C7 FOR WCEL RAN1188
M1024C8 UL AVERAGE BER FOR WCEL RAN1188
UL AVERAGE BER DENOMINATOR FOR
SUM OF SQUARED UL BER VALUES FOR
M1024C11 REPORTS FOR WCEL RAN1188
M1024C12 BAD UPLINK CONNECTIONS FOR WCEL RAN1188
M1024C13 IDEAL UPLINK CONNECTIONS FOR WCEL RAN1188
TOO GOOD UPLINK CONNECTIONS FOR
AVERAGE RADIO LINK POWER IN DL FOR
M1024C16 VALUES IN DL FOR WCEL RAN1188
DL RADIO LINK POWER SAMPLES FOR
M1024C18 VALUE FOR WCEL RAN1188
UL E-DCH HARQ RETRANSMISSIONS FOR
Measurement 1025
46 DN99581291 Issue: 12G

PI ID Name Feature
M1025C0 AVERAGE UL EB/NO FOR RNC RAN1188
UL AVERAGE EB/NO DENOMINATOR FOR
M1025C1 RNC RAN1188
UL SUM OF SQUARED EB/NO VALUES FOR
M1025C2 RNC RAN1188
M1025C3 REPORTS FOR RNC RAN1188
M1025C4 UPLINK CRC OK BLOCKS FOR RNC RAN1188
M1025C5 UPLINK CRC NOK BLOCKS FOR RNC RAN1188
M1025C6 SUM OF SQUARED BLER VALUES FOR RNC RAN1188
UL NUMBER OF RECEIVED BLER REPORTS
M1025C7 FOR RNC RAN1188
M1025C8 UL AVERAGE BER FOR RNC RAN1188
UL AVERAGE BER DENOMINATOR FOR
M1025C9 RNC RAN1188
SUM OF SQUARED UL BER VALUES FOR
M1025C10 RNC RAN1188
M1025C11 REPORTS FOR RNC RAN1188
M1025C12 BAD UPLINK CONNECTIONS FOR RNC RAN1188
M1025C13 IDEAL UPLINK CONNECTIONS FOR RNC RAN1188
TOO GOOD UPLINK CONNECTIONS FOR
AVERAGE RADIO LINK POWER IN DL FOR
M1025C16 VALUES IN DL FOR RNC RAN1188
DL RADIO LINK POWER SAMPLES FOR
M1025C18 VALUE FOR RNC RAN1188
Issue: 12G DN99581291 47

PI ID Name Feature
UL E-DCH HARQ RETRANSMISSIONS FOR
Measurement 1026
PI ID Name Feature
M1026C0 OCCUPANCY FOR WCEL RAN1188
AVERAGE PDCP BUFFER OCCUPANCY
M1026C2 OCCUPANCY VALUES FOR WCEL RAN1188
M1026C3 OCCUPANCY VALUES FOR WCEL RAN1188
M1026C4 OCCUPANCY FOR WCEL RAN1188
DL PDU ERROR RATIO IN AM RLC FOR
M1026C6 DOWNLINK FOR WCEL RAN1188
SUM OF SQUARED DL PDU ERROR RATIO
M1026C8 RECEIVED DL PDU REPORTS FOR WCEL RAN1188
M1026C9 BAD RLC AM DL CONNECTIONS FOR WCEL RAN1188
TOO GOOD RLC AM DL CONNECTIONS
IDEAL RLC AM DL CONNECTIONS FOR
DL GROSS THROUGHPUT OF AM RLC PDU
M1026C13 THROUGHPUT OF RLC AM PDU FOR WCEL RAN1188
REPORTS FOR DL AM RLC THROUGHPUT
48 DN99581291 Issue: 12G

PI ID Name Feature
DL NET THROUGHPUT OF AM RLC PDU
M1026C16 OF AM RLC PDU FOR WCEL RAN1188
M1026C17 VALUES FOR DL AM RLC FOR WCEL RAN1188
M1026C18 PER PDU IN AM RLC DL FOR WCEL RAN1188
PDU DISCARD RATIO IN AM RLC DL FOR
M1026C20 TRANSMISSIONS FOR WCEL RAN1188
AM RLC DL PDUS FOR TRANSMISSION FOR
M1026C22 RLC AM SDU DL ERROR RATIO FOR WCEL RAN1188
M1026C23 RATIO FOR WCEL RAN1188
M1026C24 OF SDU FOR WCEL RAN1188
M1026C25 OF SDU FOR WCEL RAN1188
DEVIATIONS OF TRANSFER DELAY OF SDU
M1026C27 TRANSMISSION DELAY OF SDU FOR WCEL RAN1188
SDUS FOR TRANSMISSION IN RLC AM DL
M1026C29 AM FOR WCEL RAN1188
UL RLC AM SDU PAYLOAD OF PS TRAFFIC
DL RLC AM SDU PAYLOAD OF PS TRAFFIC
Issue: 12G DN99581291 49

PI ID Name Feature
TRANSMITTED AM RLC PDUS IN UPLINK
M1026C33 AM FOR WCEL RAN1188
M1026C34 CLASS 1 FOR WCEL RAN1188
50 DN99581291 Issue: 12G

PI ID Name Feature
Measurement 1027
PI ID Name Feature
M1027C0 OCCUPANCY FOR RNC RAN1188
AVERAGE PDCP BUFFER OCCUPANCY
M1027C2 OCCUPANCY VALUES FOR RNC RAN1188
M1027C3 OCCUPANCY VALUES FOR RNC RAN1188
M1027C4 OCCUPANCY FOR RNC RAN1188
M1027C5 DL PDU ERROR RATIO IN AM RLC FOR RNC RAN1188
Issue: 12G DN99581291 51

PI ID Name Feature
M1027C6 DOWNLINK FOR RNC RAN1188
SUM OF SQUARED DL PDU ERROR RATIO
M1027C8 RECEIVED DL PDU REPORTS FOR RNC RAN1188
M1027C9 BAD RLC AM DL CONNECTIONS FOR RNC RAN1188
TOO GOOD RLC AM DL CONNECTIONS
M1027C11 IDEAL RLC AM DL CONNECTIONS FOR RNC RAN1188
DL GROSS THROUGHPUT OF AM RLC PDU
M1027C13 THROUGHPUT OF RLC AM PDU FOR RNC RAN1188
REPORTS FOR DL AM RLC THROUGHPUT
DL NET THROUGHPUT OF AM RLC PDU
M1027C16 OF AM RLC PDU FOR RNC RAN1188
M1027C17 VALUES FOR DL AM RLC FOR RNC RAN1188
M1027C18 PER PDU IN AM RLC DL FOR RNC RAN1188
PDU DISCARD RATIO IN AM RLC DL FOR
M1027C20 TRANSMISSIONS FOR RNC RAN1188
AM RLC DL PDUS FOR TRANSMISSION FOR
M1027C22 RLC AM SDU DL ERROR RATIO FOR RNC RAN1188
M1027C23 RATIO FOR RNC RAN1188
52 DN99581291 Issue: 12G

PI ID Name Feature
M1027C24 OF SDU FOR RNC RAN1188
M1027C25 OF SDU FOR RNC RAN1188
DEVIATIONS OF TRANSFER DELAY OF SDU
M1027C27 TRANSMISSION DELAY OF SDU FOR RNC RAN1188
SDUS FOR TRANSMISSION IN RLC AM DL
M1027C29 AM FOR RNC RAN1188
UL RLC AM SDU PAYLOAD OF PS TRAFFIC
DL RLC AM SDU PAYLOAD OF PS TRAFFIC
TRANSMITTED AM RLC PDUS IN UPLINK
M1027C33 AM FOR RNC RAN1188
M1027C34 CLASS 1 FOR RNC RAN1188
Issue: 12G DN99581291 53

PI ID Name Feature
54 DN99581291 Issue: 12G

Measurement 1028
PI ID Name Feature
M1028C0 CPICH ECNO DETECTED CELL SUM RAN1191
M1028C1 CPICH ECNO DETECTED CELL DENOM RAN1191
M1028C2 CPICH RSCP DETECTED CELL SUM RAN1191
M1028C3 CPICH RSCP DETECTED CELL DENOM RAN1191
1.3 Counter compatibility with 3GPP

The RNC supports counters which are compatible with the counters described in 3GPP
TS 32.405 release 7. Standard relation can be found from the counter description fields
Related to standard, 3GPP Measurement Name and 3GPP Measurement Type.
1.4 Quality of service

There are four different quality of service (QoS) classes (or traffic classes) for UMTS
bearer service and radio access bearer service:
• conversational class
• streaming class
• interactive class
• background class.
1.5 Used definitions

The following definitions are used for easier understanding of the contents of radio
network measurements:
• Call
• User
Call
>In UMTS network the services are carried out by RAB s. The RABs are used to build up
different services. The RNC does not "see" the used services; it only sees the used
RABs. Therefore the word RAB is a synonym for a call in RNC.
The call can either be a CS (circuit-switched) call or a PS (packet-switched) call:
• A circuit-switched call takes place between CS core network (MGW) and the UE .
There are two types of CS calls: CS voice call and CS data call. A CS data call is
divided into two classes: conversational class and streaming class.
Issue: 12G DN99581291 55

The CS call definitions are used in both service and traffic measurements.
• A packet-switched call takes place between PS core network(3G SGSN) and the UE.
A PS call is divided into four classes: conversational, streaming, interactive and
background.
The PS call definitions are used in both service and traffic measurements.
• Regardless if the call belongs to CS or PS core, the conversational class and
streaming class are seen as real time (RT) data calls and interactive and background
calls are seen as non-real-time (NRT) data calls. The CS voice call belongs to RT
calls.
The RT/NRT definitions are used in both handover and traffic measurements.
Figure 1 RAB types
Call
CSCall PSCall
CSDataCall CSVoiceCall
InteractiveClass BackgroundClass
PSDataCall PSDataCall
NRT DataCalls
ConversationalClass StreamingClass ConversationalClass StreamingClass

CSDataCall CSDataCall PSDataCall PSDataCall
RT DataCalls
User
User means all CS and PS calls belonging to one UE. Currently user-specific
measurements are not done.
1.6 RNC roles

RNC can have the following roles:
• serving RNC (SRNC)
• drifting RNC (DRNC)
• controlling (CRNC)
For each measurement there is a statement revealing whether the measurement is
carried out in an SRNC, DRNC and/or CRNC.
1.7 Formulas for unit conversions

Here are formulas for the most common unit conversions:
56 DN99581291 Issue: 12G

• dBm_value = 10*LOG(watt_value*1000)
• RSSI_LEV = (dBm_value+112)*621/62+1
• UTRAN_CODE_POWER = 10+ABS(dBm_value+10)/0.5
• UTRAN_TX_POWER = watt_value/dBm_value*100
For more information, see 3GPP TS 25.133.
1.8 Field descriptions of counter boxes

The table describes fields used in the counter boxes.
Field name Description Example
Counter ID Counter identification Format: M1002C65

MxxxxCyyyy, where xxxx =
measurement number, and
yyyy = number which defines
the counter within the
measurement.
Network element name Counter name - long version. RT DCH ALLO FOR TRANS

Used in the OMS Element CS DATA CONV CLASS 64
Manager. KBPS IN SRNC
Version A database-internal version 5.2

number of the counter. The
version number may be
different in Operating
Documentation (NED) and in
the Reference Information
Service in Product
Information Center (NSN
Customer Extranet) due to
differences in the publishing
of the database information.
A change in the version
number in itself does not
indicate change in content.
All content changes are
explained in Operating
Documentation (NED); for
more information on content
changes, see Counter
changes or the Summary of
changes page in the PDF
version of the measurement
document. Alternatively, use
the Compare function in the
Reference Information
Service to export a list of
counter changes in Excel
format.
Issue: 12G DN99581291 57

NetAct name Counter name - short ALLO_TRAN_CS_CONV_64

version. Used as database _IN_SRNC
view column name in NetAct.
The maximum length of
NetAct name is 31
characters.
Description Describes what information A number of RT DCH

this counter provides. allocations for a transparent
CS Data Call with
conversational class 64 kbps
in the SRNC. Transparent CS
Calls are symmetric, i.e.
there is no need for separate
UL and DL counters.
Updated Describes when this counter When the DCH is accepted.

is updated; that is, what is the
triggering point.
Logical type This field can be used for Sum

example to tell whether this
counter provides minimum,
maximum, average, sum, or
cumulative values. "sum" and
"cumulative" are
interchangeable terms, they
both count the amount of
some events or duration.
Trigger type This field provides Event

information on whether the
triggering of the counter
update is event based or
periodical (sample based).
The 3rd possibility is
duration, in which case the
triggering can be considered
as a combination of start and
stop events.
Sampling interval If the trigger type is -
periodical, this field provides
the used sampling interval.
Unit The unit of the counter. The Integer number

physical quantity is equal to
the numerical value times the
unit.
58 DN99581291 Issue: 12G

Range This field can be used if the -
counter has minimum and
maximum values which are
not self-evident.
Example values This field can be used to -
further clarify what kind of
values the counter may have.
In most cases, this field is not
needed.
Dependencies with other Provides information on M1002C69: RT DCH ALLO

counters counters which are updated DUR FOR TRANS CS DATA
together with this counter. CONV CLASS 64 KBPS IN
SRNC
Operability class The operability class is used -
to map counters to basic
network operability aspects.
Example values: Mobility,
Traffic, Resources,
Admission, Quality, and
Security.
Related to feature Defines the feature which is RAN 1.029: Packet

the main reason for Scheduler Algorithms
introducing this counter.
Related to standard The related standard, and its -
version number.
3GPP Measurement name More detailed information on -
(Clause header) the related standard.
Customized for 3GPP
purposes.
3GPP Measurement type More detailed information on -
the related standard.
Customised for 3GPP
purposes.
Exceptions to related In a fully compliant case, this -
standard field can be used, for
example, to describe how the
standard defined counter can
be derived from NSN
counters, or what additional
information the counters
provide. In a partially
compliant case, this field can
be used to describe the
difference between the
standard defined and NSN
Issue: 12G DN99581291 59

counters. In that case, the
3GPP Measurement Type
begins with 'VS'.
Used from release The first product release in RN1.5.1

which the counter was
available.
Definition updated in release The product release when -
the counter information has
last been modified. This may
happen, for example, due to
a change in the measured
functionality or due to a
description clarification.
1.9 Special objects in measurements

Measurement files produced by the RNC OMS can contain several different special
objects that do not represent any real radio network topology object, but they are meant
for describing miscellaneous situations in the network as described in the measurement
type chapters of this document.
The NetAct PM system does not accept any data from unknown objects, that is, objects
that cannot be found in NetAct topology DB. These kinds of measurements must be
converted in the NetAct PM pipe before they can be inserted into NetAct DB and before
they can be forwarded to Measurement Data Export interface that is the northbound
interface of the NetAct.
This chapter describes what are the differences in the measurement object format in
these cases, when comparing the measurement file format produced by OMS to the
format that is produced by the NetAct Measurement Data Export.
Measurements M1007 and M1008
From RU40 onwards, for measurements M1007 and M1008, OMS produces the RNC
level special object by itself so that NetAct does not need to make the conversion for the
Measurement Data Export. The object that was previously produced by OMS as NE-
WBTS-0/WCEL-0 is now in the format:
<MO>
<baseId>NE-RNC-100</baseId>
</MO>
<MO>
<DN>PLMN-PLMN/MCC-300000000/MNC-300000000</DN>
</MO>
When OMS produces the special object, it uses a measurementType attribute value
that is different from the real WCEL objects:
• Soft_Handover -> Soft_Handover_RNC
60 DN99581291 Issue: 12G

• Intra_System_Handover -> Intra_System_HHO_RNC
This change in OMS implementation does not cause any changes in the data format in
the NetAct northbound measurement data export interface because in the previous
releases, the same object format was already used for M1007 and M1008 and it was
NetAct that does the object conversion then.
Measurements M1005
For measurements M1005 OMS produces special object WCEL-300000000:
<MO>
<baseId>NE-RNC-100</baseId>
<localMoid>DN:NE-WBTS-20/WCEL-300000000</localMoid>
</MO>
<MO>
<DN>PLMN-PLMN/MCC-300000000/MNC-300000000</DN>
</MO>
NetAct does not support this object at all but it is discarded before the database
insertion.
Issue: 12G DN99581291 61

Measurement: Service level (RRC and RAB RNC Counters - RNW Part
connections) (M1001)
2 Measurement: Service level (RRC and RAB

From the viewpoint of the call entity, that is, the user viewpoint, the service level
measurement provides information on RRC and RAB connections.
g Note: There is another measurement called RRC signalling which provides information
on RRC signalling from the signalling entity viewpoint. For more information on the
differences of the two measurements, see
The differences between service level and RRC signalling measurement.
The service level measurement is carried out in the serving RNC (SRNC).
The object of this measurement is the WBTS/WCEL within MCC/MNC.In cells shared
with Multi-Operator Core Network feature, the cell common MCC/MNC is used. In other
words, this measurement has two object identifiers (see the following table).
Table 1 Service level measurement object identifiers
Object identifier Optionality
WBTS/WCEL NO
MCC/MNC NO
The object of the measurement is the WBTS/WCEL, which is the best active set cell of
the SRNC (having the biggest CPICH Ec/No value in the last RRC: Measurement
Report).
• In anchoring case, all active set cells belong to the drifting RNC (DRNC) and the
serving RNC is not aware of their WBTS/WCEL identifications. Therefore, this
measurement is forced to use the special WBTS/WCEL object identifier WBTS-
0/WCEL-0, which is shown as "DRNC" in the RNW Measurement Presentation GUI.
The special object can be used for any of the M1001 counters.
• When SRNC relocation is successfully performed after the last active set cell has
been removed from the active set or a UE makes Cell Update to a DRNC cell, the
RRC and RAB release counters are updated for the last SRNC cell that the UE used
during the connection.
• Note that the best active set cell may change during the call. Therefore, the object of
the measurement can be different for connection establishment (setup and access
phases) and release counters (active phase) of the same call. RRC and RAB phases
are defined in section Introduction to service level (RRC and RAB connections)
measurement.
• Note that a RAB can be established and released in two separate measurement
intervals. In that case, connection establishment (setup and access phases) and
release counters (active phase) of the same call are updated during different
measurement intervals.
62 DN99581291 Issue: 12G

RNC Counters - RNW Part Measurement: Service level (RRC and RAB
2.1 Introduction to service level (RRC and RAB

connections) measurement
The service level measurement provides RRC and RAB connections -related
information.
Both RRC and RAB connection are divided into three phases: setup, access, and active
phase. The figures below show the triggering of the most important counters and how
the phases are defined.
In addition to the counters presented in the figures below, this measurement provides
information on incoming handovers and SRNC relocations, RAB holding times, DCH
holding times per NRT RAB type, RRC and RAB setup times, and multi-RABs.
g Note: If a failure which leads to RRC connection release occurs during any RAB
phase, both RRC active and RAB (setup, access or active) failure counters are updated
with an appropriate cause.
g Note: An AMR multimode call is an AMR call that is triggered by a RANAP: RAB
ASSIGNMENT REQUEST message where Maximum Bit Rate parameter is greater
than Guaranteed Bit Rate. In an AMR singlemode call, these two parameters are equal.
An additional condition for AMR multimode related counters to be updated is that the
feature be enabled and admission control accept the call as multimode.
g Note: This measurement also provides counters for reference cell changes. They can
be used to explore RRC and RAB performance on the cell level.
The first reference cell is the cell through which the RRC connection has been
established. The reference cell is not changed until the current reference cell is deleted
from the active set. When it is deleted, the next reference cell will be the cell with the
greatest CPICH Ec/No value in the last RRC: MEASUREMENT REPORT.
For more information on call phases, see Call Setup and Release.
Issue: 12G DN99581291 63

Figure 2 Triggering of the most important RRC counters
UE BTS RNC
CN
RRC:RRCRadioConnectionRequest 2
RRCSETUPphase
3
(ResourceReservationinRNC,BTS,Transport)
4
RRC:RRCConnectionSetup
RCC setup time
RRCACCESSphase
(RNCwaitsforreplyfromUE)
5
RRC:RRCConnectionSetupComplete
6
RCCACTIVEphase
RCC:InitialDirectTransfer
RANAP:InitialUEMessage 7
8
UE-CNSignalling
(Forexample:RABestablishmentandrelease) 9
RANAP:IuReleaseCommand(forthelastIuconnection)
RRC:RRCConnectionRelease
9
RRC:RRCConnectionReleaseComplete
ReleaseRRCresourcesinRNC,BTS,Transport
1. RRC setup attempts. For more details, see RRC setup.
2. RRC setup attempts per setup cause. Details in the section RRC setup causes.
3. RRC setup failures due to
• handover control
• admission control
• transport (Transmission)
• RNC internal
• frozen BTS
• BTS
64 DN99581291 Issue: 12G

• ICSU overload
Details in the section RRC setup.
4. RRC setup failures per setup cause.
Details in the section RRC setup causes.
5. RRC setup complete. Details in the section RRC setup.
6. RRC access failures due to
• radio interface
• UE
• RNC internal
RRC access releases
Details in the section RRC access.
7. RRC access complete. Details in the section RRC access.
8. Special reason: RRC active release due to
• SRNC Relocation
• Pre-emption
• User inactivity
• RNC HW resources
• Inter-system handover to GAN (Generic Access Network)
• Inter-system handover to GSM
• Intra-frequency inter-RNC hard handover
• Inter-frequency inter-RNC hard handover
Details in the section RRC active.
9. RRC active failures due to
• Iu interface (transport)
• radio interface (synchronisation)
• BTS
• Iur interface (DRNC)
• RNC internal
• UE
• Transmission
Details in the section RRC active.
10. RRC active complete. Details in the section RRC active.
Issue: 12G DN99581291 65

Figure 3 Triggering of the most important RAB counters
UE BTS RNC
CN
1
RRCConnectionActivephase
UE-CNSignalling
RANAP:RABAssignmentRequest
RABSETUPphase
(ResourceReservationinRNC,BTS,Transport)
2
RABsetuptime
RRCRadioBearerSetup
RABACCESSphase
(RNCwaitsforreplyfromUE)
3
RRCRadioBearerSetupComplete
4
RANAP:RABAssignmentResponse
RABACTIVEphase
UserPlaneDataTransfer
5
RANAP:RABAssignmentRequestwithIE:RABreconfiguration 6
7
RAB holding time
RABreconfigurationactions
(ReconfigureRABresourcesinRNC,BTS,Transport)
RRC:RadioBearerReconfiguration 8
RRC:RadioBearerReconfigurationComplete
9
RANAP:RABAssignmentRequestwithIE:RABRelease
RRC:RadioBearerRelease
RRC:RadioBearerReleaseComplete
10
ReleaseRABresourcesinRNC,BTS,Transmission
This measurement provides also RAB counters with higher granularity which are not
shown in this picture. Note that RAB active phase is completed also when CN sends
RANAP: Iu Release Command.
1. RAB setup attempts. Separate counter per each RAB type. Details in the section
RAB setup.
2. RAB setup failures due to
• admission control
• transport (transmission)
• RNC internal
66 DN99581291 Issue: 12G

• frozen BTS
• BTS (RT only)
• anchoring (NRT only)
• capacity license (for CS voice RAB only)
Separate counter for each RAB type. Details in the section RAB setup.
3. RAB setup complete. Separate counter per each RAB type. Details in the section
RAB setup.
4. RAB access failures due to
• UE
• RNC internal
Separate counters per each RAB type. Details in the section RAB access.
5. RAB access complete. Separate counters per each RAB type. Details in the section
RAB access.
6. Special reason: RAB active release due to
• SRNC relocation
• pre-emption
• capacity license pre-emption (only for CS voice RAB)
Separate counters per each RAB type. Details in the section RAB active.
7. RAB active failures due to
• Iu interface (transport)
• radio interface (synchronisation)
• BTS
• Iur interface (DRNC)
• RNC internal
• UE
• Transmission
Separate counters per each RAB type. Details in the section RAB active.
8. RAB reconfiguration attempts. Details in the section RAB reconfiguration.
9. RAB reconfiguration failures. Details in the section RAB reconfiguration.
10. RAB active complete. Separate counters per each RAB type. Details in the section
RAB active.
2.1.1 Failure and abnormal release causes

The failure and abnormal release causes for RRC and RAB phases are presented in the
tables below.
Issue: 12G DN99581291 67

Figure 4 Failure/release causes used in different RRC/RAB phases
Table 2 Failure/release cause explanations
Failure / abnormal release Explanation
Admission control Admission control rejects setup, cell change or
handover (excluding frozen BTS failure)
Frozen BTS Admission control blocks RL establishment to ensure
the setup of emergency calls
Handover control Handover control entity reports a failure
Transport (Transmission) Any transport failure (RRC/RAB setup); transport
failure excluding Iu transport (RRC/RAB active)
68 DN99581291 Issue: 12G

Table 2 Failure/release cause explanations (Cont.)
Failure / abnormal release Explanation
RNC internal RNC internal failure (examples: L2 failure, capacity
problem)
BTS Unsuccessful radio link setup (RRC setup); radio link
reconfiguration preparation (RT RAB setup); other
BTS reason excluding synchronisation failure
(RRC/RAB active)
Anchoring NRT RAB setup requested, but NRT RAB is not
allowed during anchoring
UE / Uu UE failure (based on RRC messages)
Radio interface Radio interface synchronisation failure (based on
NBAP)
Iur Procedure failure in drift RNC (example: radio link
reconfiguration failure in DRNC)
Iu Iu transport failure (RRC/RAB active)
Pre-emption RAB and RRC connections are released in order to
make room for a higher priority RAB, for example,
emergency call
SRNC relocation RAB/RRC release due to SRNC relocation
Unspecified RANAP: IU RELEASE COMMAND or RANAP: RAB
ASSIGNMENT REQUEST message with cause
"unspecified error" is received from CN
RNTI allocation RNTI allocation failure due to RRMU overload
Iub transport Lack of Iub AAL2 transport resources for RT
Iur transport Lack of Iur AAL2 transport resources for RT
Iu transport Lack of Iu AAL2 transport resources for RT
UE capability Requested parameters are not supported by the UE
Not supported parameters Requested parameters are not supported by the RNC
License Procedure fails due to AMR capacity licence
exceeded
User inactivity RRC connection released due to user inactivity in
Cell-PCH or URA-PCH state
RNC HW resources RRC connection released due to the shortage of HW
resources in ICSU/DMCU units
Issue: 12G DN99581291 69

g Note: There are separate counters for RAB active failures in PCH state.
2.1.2 The differences between service level and RRC signalling

measurement
This section describes the differences between RRC connection counters in service level
measurement and RRC signalling measurement.
1. In service level measurement, the measurement is carried out in the serving RNC
(SRNC). In RRC signalling measurement, the measurement is carried out in the
controlling RNC (CRNC).
2. In service level measurement, the counters are updated by the call control entity (UE
specific). In RRC signalling measurement, the counters are updated by the RRC
signalling entity.
3. Counters based on RRC CONNECTION REQUEST message
• RRC signalling measurement: counters include all RRC CONNECTION
REQUEST messages received from UEs
• Service level measurement: counters do not include the RRC CONNECTION
REQUEST messages received from UEs
if
– the RRC signalling entity receives a defective message, for example,
mandatory fields are missing,
or
– the RRC signalling entity detects that RRC connection setup procedure is
already running for this UE/cell pair.
4. Counters based on RRC CONNECTION SETUP message
• Service level measurement: counters include the RRC CONNECTION SETUP
messages which are sent from the call control entity to the RRC signalling entity.
• RRC signalling measurement: counters include all RRC CONNECTION SETUP
messages which are sent to UEs. They include the messages initiated by the call
control entity and repeats. The RRC signalling entity repeats the RRC
CONNECTION SETUP message
if
– the UE does not send RRC CONNECTION SETUP COMPLETE message to
the RRC signalling entity within a certain period of time. The maximum
number of repeats is two.
5. Counters based on RRC CONNECTION SETUP COMPLETE message
• RRC signalling measurement: counters include all RRC CONNECTION SETUP
COMPLETE messages received from UEs
• Service level measurement: counters do not include the RRC CONNECTION
SETUP COMPLETE messages received from UEs
if
– the RRC signalling entity receives a defective message.
6. Counter based on RRC CONNECTION RELEASE message
70 DN99581291 Issue: 12G

• Service level measurement: counters include the RRC CONNECTION RELEASE
messages which are sent from the call control entity to the RRC signalling entity.
• RRC signalling measurement: counters include the RRC CONNECTION
RELEASE messages which are sent from the call control entity to the RRC
signalling entity like in service level measurement.
g Note: RRC signalling entity repeats RRC CONNECTION RELEASE message a
maximum of two times if the UE does not respond within a certain period of time.
However, in this case, the repeat does not cause the update of RRC signalling counters
unlike in RRC CONNECTION SETUP case.
2.2 RRC setup

The UE sends an RRC: RRC CONNECTION REQUEST message to the RNC's RRC
signalling entity. If the RRC connection request is accepted, the RRC setup starts.
RRC connection request is not accepted
if
• The RRC signalling entity receives a defective message, for example, mandatory
fields are missing,
or
• The RRC signalling entity detects that RRC connection setup procedure is already
running for this UE/cell pair.
RRC setup is completed, when the RNC has reserved all resources (RNC, BTS, air,
transport) needed for the RNC connection and sends the RRC: RRC CONNECTION
SETUP message to the UE.
RRC setup fails if some of the needed resources (RNC, BTS, air, transport) are not
available. When an RRC setup failure occurs, the RNC sends an RRC: RRC
CONNECTION REJECT message to the UE.
The figure below shows the triggering of the RRC setup counters.
Issue: 12G DN99581291 71

Figure 5 Triggering of RRC setup counters
objectsarecolor-marked
requestedcell
RRCConnectionRequestsis celldirectedto
receivedfromUE cellofthepreviousrequest
[messageisdefective,setupprocedureisalreadyrunningforthis
UE/cellpair,orMCCcreationisnotattemptedduetoRNCoverload]
[otherwise] ServiceLevelcountersarenot
updated.NomessageissenttoUE
[IfanewRequesttoanothercellisreceivedbeforeSetupComplete
isreceived.EitherinRRCSetuporinRRCAccessphase]
[otherwise] RRCACCRELEASEDUETOCELLRESEL.
InRRCSetupPhase,also RRCSETUPCOMP isupdated.
RRCSETUPATT
[messageisreceivedduringmin(WaitTimeRRC+N300*T300+2.5s,
17.5s)afterRRCCONNECTIONREJECThasbeensenttothisUE]
[otherwise] RRCSETUPATTREPEAT
[ACdeniesorRNC/BTS/transportresourcereservationfails]
[otherwise] RRCSETUPFAIL
RRCConnectionRejectmessageissenttoUE
RRCSETUPwasdirectedtoanother
frequencyofsameBTS/sector
[otherwise]
RRCSETUPCOMPDIR
RRCSETUPCOMPAFTERDIRRRC
RRCSETUPCOMP SETUPCOMP
RRCConnectionSetupmessage RRCConnectionSetupmessageissenttoUE
issenttoUE
g Note: In case of an emergency call, the RRC connection establishment is never
rejected due to congestion reasons.
Figure Triggering of RRC setup counters presents the service level counters. All received
and sent RRC CONNECTION REQUEST/ REJECT/ SETUP messages are counted by
the RRC signalling measurement.
If an RRC connection reject message is sent, the setup procedure ends immediately. If
an RRC connection setup message is sent, the setup procedure ends:
72 DN99581291 Issue: 12G

• when the RRC connection setup complete message is received, or
• after 6 s.
2.2.1 RRC setup attempts

Counter ID: M1001C0 Network element name: RRC SETUP ATT
Version: 7.1 NetAct name: RRC_CONN_STP_ATT
Description: The number of RRC connection setup attempts. Note that from RN5.0 onwards this
counter does not include incoming relocations and hard handovers because they have dedicated
counters.
Updated: When the RNC receives an RRC: RRC CONNECTION REQUEST message from the UE,
and the RNC starts to reserve resources for the RRC connection.
Logical type: Cumulative Trigger type: Event Sampling interval:
Unit: Integer number Range: Example values:
Dependencies with other counters:
Operability class:
Related to feature: Related to standard:
RAN 1.008: RAN - MS Connection Establishment 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement name (Clause header): Attempted RRC connection establishments
3GPP Measurement type: RRC.AttConnEstab.Sum
Exceptions to related standard:
Used from release: RN1.5.1 Definition updated in release: RN5.0
Counter ID: M1001C242 Network element name: RRC CONNECTION SETUP
ATTEMPT REPEATS
Version: 5.2 NetAct name: RRC_CONN_SETUP_ATT_REPEAT
Description: The number of RRC connection request retransmissions (successfully received by the
RNC) from the same UE if the RRC connection request is rejected due to an unsuccessful resource
reservation attempt in RNC. This counter is used for gathering information on RRC connection request
retransmissions eventually leading to the successful RRC connection establishment (i.e. the
retransmissions were not caused by a failure in the Uu).
Issue: 12G DN99581291 73

Updated: When a repeated RRC CONNECTION REQUEST is received from the same UE as the first
RRC CONNECTION REQUEST during the time interval defined as the shorter one of these
alternatives: A) WaitTimeRRC+N300*T300 + 2.5 s B) 17.5 s This counter is not updated if the previous
RRC Connection Request was rejected due to uplink scrambling code allocation failure.
Operability class:
RAN 1.008: RAN - MS Connection Establishment
3GPP Measurement name (Clause header):
3GPP Measurement type:
Used from release: RN1.5.2ED2 Definition updated in release:
Counter ID: M1001C573 Network element name: RRC SETUP ATT REPEAT MO
CONVERSATIONAL CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MO_CONV
RNC) with the cause originating conversational call from the same UE whose previous RRC connection
request was rejected due to an unsuccessful resource reservation attempt in RNC.
alternatives: A) WaitTimeRRC+N300*T300 + 2.5 s B) 17.5 s.
M1001C242: RRC CONNECTION SETUP ATTEMPT REPEATS
Operability class:
74 DN99581291 Issue: 12G

Used from release: RN2.1 Definition updated in release:
STREAMING CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MO_STREAMING
RNC) with the cause originating streaming call from the same UE whose previous RRC connection
Operability class:
INTERACTIVE CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MO_INTERACTIVE
RNC) with the cause originating interactive call from the same UE whose previous RRC connection
Issue: 12G DN99581291 75

Operability class:
BACKGROUND CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MO_BACKGROUND
RNC) with the cause originating background call from the same UE whose previous RRC connection
Operability class:
76 DN99581291 Issue: 12G

SUBSCRIBED TRAFFIC CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MO_SUBSCRIBED
RNC) with the cause originating subscribed traffic call from the same UE whose previous RRC
connection request was rejected due to an unsuccessful resource reservation attempt in RNC.
Operability class:
Counter ID: M1001C578 Network element name: RRC SETUP ATT REPEAT MT
CONVERSATIONAL CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MT_CONV
RNC) with the cause terminating conversational call from the same UE whose previous RRC
Issue: 12G DN99581291 77

Operability class:
STREAMING CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MT_STREAMING
RNC) with the cause terminating streaming call from the same UE whose previous RRC connection
Operability class:
INTERACTIVE CALL
Version: 3.2 NetAct name: RRC_ATT_REP_INTERACTIVE
78 DN99581291 Issue: 12G

RNC) with the cause terminating interactive call from the same UE whose previous RRC connection
Operability class:
BACKGROUND CALL
Version: 3.2 NetAct name: RRC_ATT_REP_MT_BACKGROUND
RNC) with the cause terminating background call from the same UE whose previous RRC connection
Operability class:
Issue: 12G DN99581291 79

Counter ID: M1001C582 Network element name: RRC SETUP ATT REPEAT
EMERGENCY CALL
Version: 3.2 NetAct name: RRC_ATT_REP_EMERGENCY
RNC) with the cause emergency call from the same UE whose previous RRC connection request was
rejected due to an unsuccessful resource reservation attempt in RNC.
Operability class:
Counter ID: M1001C583 Network element name: RRC SETUP ATT REPEAT INTER
RAT CELL RESEL
Version: 3.2 NetAct name: RRC_ATT_REP_INTER_RAT_RESEL
RNC) with the cause inter-RAT cell reselection from the same UE whose previous RRC connection
80 DN99581291 Issue: 12G

Operability class:
Counter ID: M1001C584 Network element name: RRC SETUP ATT REPEAT INTER
RAT CELL CHANGE ORDER
Version: 3.2 NetAct name: RRC_ATT_REP_INTER_RAT_CCO
RNC) with the cause inter-RAT cell change order from the same UE whose previous RRC connection
Operability class:
Issue: 12G DN99581291 81

Counter ID: M1001C585 Network element name: RRC SETUP ATT REPEAT
REGISTRATION
Version: 3.2 NetAct name: RRC_ATT_REP_REGISTRATION
RNC) with the cause registration from the same UE whose previous RRC connection request was
rejected due to an unsuccessful resource reservation attempt in RNC.
Operability class:
Counter ID: M1001C586 Network element name: RRC SETUP ATT REPEAT DETACH
Version: 3.2 NetAct name: RRC_ATT_REP_DETACH
RNC) with the cause detach from the same UE whose previous RRC connection request was rejected
due to an unsuccessful resource reservation attempt in RNC.
82 DN99581291 Issue: 12G

Operability class:
HIGH PRIORITY SIGNALLING
Version: 3.2 NetAct name: RRC_ATT_REP_MO_HIGH_PR_SIGN
RNC) with the cause originating high priority signalling from the same UE whose previous RRC
Operability class:
Issue: 12G DN99581291 83

LOW PRIORITY SIGNALLING
Version: 3.2 NetAct name: RRC_ATT_REP_MO_LOW_PR_SIGN
RNC) with the cause originating low priority signalling from the same UE whose previous RRC
Operability class:
Counter ID: M1001C589 Network element name: RRC SETUP ATT REPEAT CALL
RE-ESTABLISHMENT
Version: 3.2 NetAct name: RRC_ATT_REP_CALL_RE_ESTAB
RNC) with the cause call re-establishment from the same UE whose previous RRC connection request
was rejected due to an unsuccessful resource reservation attempt in RNC.
84 DN99581291 Issue: 12G

Operability class:
HIGH PRIORITY SIGNALLING
Version: 3.2 NetAct name: RRC_ATT_REP_MT_HIGH_PR_SIGN
RNC) with the cause terminating high priority signalling from the same UE whose previous RRC
Operability class:
Issue: 12G DN99581291 85

Counter ID: M1001C591 Network element name: RRC SETUP ATT REPEAT MT LOW
PRIORITY SIGNALLING
Version: 3.2 NetAct name: RRC_ATT_REP_MT_LOW_PR_SIGN
RNC) with the cause terminating low priority signalling from the same UE whose previous RRC
Operability class:
CAUSE UNKNOWN
Version: 8.2 NetAct name: RRC_ATT_REP_MT_CAUSE_UNKNOWN
RNC) with the cause "Terminating - cause unknown" from the same UE whose previous RRC
connection request was rejected because of an unsuccessful resource reservation attempt in RNC.
Such cases are also included in this "unknown" category when the establishment cause IE of RRC
Connection Request is out of the expected range, for example, because of RACH frame corruption.
86 DN99581291 Issue: 12G

Operability class:
RAN1.008: RAN - MS Connection Establishment
Counter ID: M1001C747 Network element name: RRC SETUP ATT CSFB
Version: 1.0 NetAct name: RRC_CONN_STP_ATT_CSFB
Description: The number of RRC connection setup attempts for CS fallback.
This counter does not replace any other M1001 counters but is additional information on top of them.
For example M1001C0 is updated along with M1001C747.
The activation status of LTE layering features in the RNC does not impact counter updates.
Updated: When the RNC receives RRC: RRC CONNECTION REQUEST message with "CSFB
Indication" IE from the UE, and the RNC starts to reserve resources for the RRC connection.
Logical type: Sum Trigger type: Event Sampling interval:
M1001C0: RRC SETUP ATT
Operability class:
RAN2980: Measurement Based LTE Layering
Issue: 12G DN99581291 87

Counter ID: M1001C750 Network element name: RRC SETUP ATT REPEAT CSFB
Version: 1.0 NetAct name: RRC_ATT_REP_CSFB
Description: The number of RRC connection setup repetitions for CS fallback.
RRC CONNECTION REQUEST with "CSFB Indication" IE during the time interval defined as the
shorter one of these alternatives:
A) WaitTimeRRC+N300*T300 + 2.5 s
B) 17.5 s
Operability class:
2.2.2 RRC setup completions

Counter ID: M1001C1 Network element name: RRC SETUP COMPL
Version: 7.1 NetAct name: RRC_CONN_STP_COMP
Description: The number of completed RRC setup phases. Note that from RN5.0 onwards this counter
does not include incoming relocations and hard handovers because they have dedicated counters.
Updated: When the RNC sends an RRC: RRC CONNECTION SETUP message to the UE. The
counter is updated only once per RRC connection establishment attempt, not separately for each
repeated RRC CONNECTION SETUP message sent by the RNC.
88 DN99581291 Issue: 12G

Operability class:
Counter ID: M1001C259 Network element name: RRC CONN SETUP COMPLETED
AFTER DIRECTED
Version: 4.2 NetAct name: RRC_CONN_SETUP_COMP_AFT_DIR
Description: The RRC connection setup is completed after directed to the cell. This counter is updated
to that cell to which the RRC connection is directed.
Updated: The counter is updated when the RRC connection setup is sent with new cell carrier
information.
Operability class:
RAN 2.0079: Directed RRC Connection Setup
RAN 1.010: RAN Radio Access Bearer Services
Issue: 12G DN99581291 89

Counter ID: M1001C260 Network element name: RRC CONN SETUP COMPLETED
AND DIRECTED
Version: 4.2 NetAct name: RRC_CON_SETUP_COMP_DIRECTED
Description: RRC Connection setup completed and directed to another cell. This counter is updated for
the cell where the RRC CONNECTION REQUEST was received.
Updated: Updated when RRC CONNECTION SETUP is sent with new cell carrier information.
Operability class:
RAN 2.0079: Directed RRC Connection Setup
2.2.3 RRC setup failures

Counter ID: M1001C2 Network element name: RRC SETUP FAIL DUE TO HC
Version: 7.1 NetAct name: RRC_CONN_STP_FAIL_HC
Description: The number of RRC setup failures caused by Handover Control.
Updated: When the RNC decides to reject the RRC connection request because the handover control
entity reports a failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to
the UE. (For more information, see section Failure and abnormal release causes.) Note that from
RN5.0 onwards this counter does not include incoming relocation and hard handover failures.
Operability class:
90 DN99581291 Issue: 12G

RAN1.008: RAN - MS Connection Establishment 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement name (Clause header): Failed RRC connection establishments
3GPP Measurement type: RRC.FailConnEstab.unspecified
Exceptions to related standard: Sum of signaling cause (proprietary causes)
Used from release: RN1.5.1 Definition updated in release:RN5.0
Counter ID: M1001C3 Network element name: RRC SETUP FAIL DUE TO AC
Version: 7.2 NetAct name: RRC_CONN_STP_FAIL_AC
Description: The number of RRC setup failures caused by Admission Control. The reason for the
rejection can be uplink power, downlink power, spreading codes or a temporary failure in the cell
common measurement reporting by the BTS.
Updated: When the RNC decides to reject the RRC connection request because the admission control
entity reports a failure (excluding frozen BTS reason). After this, the RNC sends an RRC: RRC
CONNECTION REJECT message to the UE. (For more information, see section Failure and abnormal
release causes.) Note that from RN5.0 onwards this counter does not include incoming relocation and
hard handover failures.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.FailConnEstab.congestion
Counter ID: M1001C4 Network element name: RRC SETUP FAIL DUE TO BTS
REASONS
Issue: 12G DN99581291 91

Version: 11.1 NetAct name: RRC_CONN_STP_FAIL_BTS
Description: The number of RRC setup failures caused by BTS or Iub overload control.
Updated: When the RNC decides to reject the RRC connection request due to unsuccessful radio link
setup or the radio link setup was not attempted due to Iub overload control. After this, the RNC sends
an RRC: RRC CONNECTION REJECT message to the UE. Note that from RN5.0 onwards this counter
does not include incoming relocation and hard handover failures.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
Counter ID: M1001C5 Network element name: RRC SETUP FAIL DUE TO TRANS
Version: 7.1 NetAct name: RRC_CONN_STP_FAIL_TRANS
Description: The number of RRC setup failures caused by Transport.
Updated: When the RNC decides to reject the RRC connection request due to transport failure. After
this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. (For more
information, see section Failure and abnormal release causes.) Note that from RN5.0 onwards this
counter does not include incoming relocation and hard handover failures.
Operability class:
92 DN99581291 Issue: 12G

3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
Counter ID: M1001C6 Network element name: RRC SETUP FAIL DUE TO RNC
INTER REASONS
Version: 7.1 NetAct name: RRC_CONN_STP_FAIL_RNC
Description: The number of RRC setup failures caused by RNC internal reason.
Updated: When the RNC decides to reject the RRC connection request due to RNC internal failure.
After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. (For more
information, see section Failure and abnormal release causes.) Note that from RN5.0 onwards this
counter does not include incoming relocation and hard handover failures.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
Counter ID: M1001C7 Network element name: RRC SETUP FAIL DUE TO
FROZEN BTS
Version: 7.1 NetAct name: RRC_CONN_STP_FAIL_FROZBS
Description: The number of RRC setup failures caused by frozen BTS.
Issue: 12G DN99581291 93

Updated: When the RNC decides to reject the RRC connection request, because the admission control
entity blocks the radio link establishment, to ensure the setup of high priority calls. After this, the RNC
sends an RRC: RRC CONNECTION REJECT message to the UE. (For more information, see section
Failure and abnormal release causes.) Note that from RN5.0 onwards this counter does not include
incoming relocation and hard handover failures.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
Counter ID: M1001C247 Network element name: RRC CONN SETUP FAIL DUE TO
RNTI ALLO FAIL
Version: 10.1 NetAct name: RRC_CONN_STP_FAIL_RNTI_ALLO
Description: This counter is not supported.
Updated: Never.
M1006C69: RRC CONN REJECT DUE TO RRMU OVERLOAD
Operability class:
94 DN99581291 Issue: 12G

Used from release: not supported Definition updated in release:
Counter ID: M1001C530 Network element name: RRC SETUP FAIL DUE TO IUB
AAL2 TRANS
Version: 5.1 NetAct name: RRC_CONN_STP_FAIL_IUB_AAL2
Description: The number of RRC setup failures caused by Iub AAL2 transport resource shortage.
Updated: When the RNC decides to reject the RRC connection request due to Iub transport resource
shortage between RNC and WBTS. After this the RNC sends an RRC: RRC CONNECTION REJECT
message to the UE. (For more information, see the section "Failure and abnormal release causes".)
Note that from RN5.0 onwards this counter does not include incoming relocation and hard handover
failures.
M1001C5: RRC SETUP FAIL DUE TO TRANS
Operability class:
Used from release: RN2.1 Definition updated in release:RN5.0
Counter ID: M1001C617 Network element name: RRC SETUP REJECT DUE TO
EMERGENCY CALL REDIRECTION
Version: 1.0 NetAct name: RRC_CONN_STP_REJ_EMERG_CALL
Description: The number of RRC connections rejected due to emergency call redirection.
Updated: When the RNC redirects an emergency call to the GSM network by sending an RRC
CONNECTION REJECT with redirection information to the UE.
Issue: 12G DN99581291 95

M1001C41: EMERGENCY CALL FAILURES
M1006C70: RRC CONN REJECT DUE TO RRC CONNECTION SETUP REDIRECTION
Operability class:
RAN1177: Emergency Call Redirect to GSM
Counter ID: M1001C618 Network element name: RRC CONN SETUP FAIL DUE TO
ICSU OVERLOAD
Version: 6.2 NetAct name: RRC_CONN_STP_FAIL_ICSU_OVERL
Description: The number of RRC setup failures caused by L3 control plane unit overload. In IPA-RNC
the unit is ICSU and in mcRNC the unit is USPU.
Updated: When the RNC decides to reject the RRC connection request due to L3 control plane unit
overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.
Operability class:
Counter ID: M1001C731 Network element name: RRC SETUP FAIL DUE TO AC UL
POWER
96 DN99581291 Issue: 12G

Version: 1.0 NetAct name: RRC_CONN_STP_FAIL_AC_UL
Description: The number of RRC setup failures caused by Admission Control because of uplink power
limitation. M1001C3 is also updated along with this counter.
Updated: When the RNC decides to reject the RRC connection request because of uplink power
admission control.
M1001C3: RRC SETUP FAIL DUE TO AC
Operability class:
Counter ID: M1001C732 Network element name: RRC SETUP FAIL DUE TO AC DL
POWER
Version: 1.0 NetAct name: RRC_CONN_STP_FAIL_AC_DL
Description: The number of RRC setup failures caused by Admission Control because of downlink
power limitation. M1001C3 is also updated along with this counter.
Updated: When the RNC decides to reject the RRC connection request because of downlink power
admission control.
Operability class:
Issue: 12G DN99581291 97

Counter ID: M1001C733 Network element name: RRC SETUP FAIL DUE TO AC
CODE
Version: 1.0 NetAct name: RRC_CONN_STP_FAIL_AC_COD
Description: The number of RRC setup failures caused by Admission Control because of downlink
spreading code congestion. M1001C3 is also updated along with this counter.
Updated: When the RNC decides to reject the RRC connection request because of downlink spreading
code congestion.
Operability class:
Counter ID: M1001C748 Network element name: RRC SETUP ACCESS FAIL CSFB
Version: 1.0 NetAct name: RRC_STP_ACC_FAIL_CSFB
Description: The number of RRC connection setup/access failures for CS fallback.
Updated: When the RRC connection setup fails either in the resource reservation or access phase, and
RRC: RRC CONNECTION REQUEST included "CSFB Indication" IE.
98 DN99581291 Issue: 12G

M1001C2: RRC SETUP FAIL DUE TO HC
M1001C4: RRC SETUP FAIL DUE TO BTS REASONS
M1001C5: RRC SETUP FAIL DUE TO TRANS
M1001C6: RRC SETUP FAIL DUE TO RNC INTER REASONS
M1001C7: RRC SETUP FAIL DUE TO FROZEN BTS
M1001C9: RRC ACC FAIL DUE TO RADIO INT SYNCH
M1001C11: RRC ACC FAIL DUE TO RNC INTER REASONS
M1001C10: RRC ACC FAIL DUE TO UU INT
M1001C247: RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL
M1001C618: RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD
Operability class:
2.2.4 RRC Setup on CCH

Counter ID: M1001C678 Network element name: RRC SETUP ATTEMPT CCH
Version: 1.0 NetAct name: RRC_CONN_STP_ATT_CCH
Description: The number of RRC connection requests that are handled with CCH. Also counter
M1001C0 is updated along with this counter.
Updated: When the RNC receives an RRC CONNECTION REQUEST message and starts to reserve
resources for the RRC connection on CCH. This counter is updated for the cell where the RRC
CONNECTION REQUEST message is received.
Issue: 12G DN99581291 99

M1001C0: RRC SETUP ATT
Operability class:
RAN1797: Common Channel Setup
Counter ID: M1001C679 Network element name: RRC ACCESS COMPLETE CCH
Version: 1.0 NetAct name: RRC_CONN_ACC_COMP_CCH
Description: The number of successfully established RRC connections using CCH. Also counter
Updated: When the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE
indicating a successful RRC connection setup on CCH. This counter is updated for the cell where the
RRC CONNECTION SETUP COMPLETE message is received.
M1001C8: RRC ACC COMP
Operability class:
Counter ID: M1001C680 Network element name: RRC ACCESS RELEASE DUE TO
CELL RESELECTION CCH
100 DN99581291 Issue: 12G

Version: 1.0 NetAct name: RRC_CONN_ACC_REL_RESEL_CCH
Description: The number of RRC connection access releases due to cell reselection for RRC
connection establishments using CCH. This is the case when the UE has sent a new RRC connection
request to the new cell while the RRC connection setup phase is still ongoing in the old cell. The RNC
releases resources for the old RRC connection attempt. Also counter M1001C241 is updated along
with this counter.
Updated: When the RNC receives an RRC CONNECTION REQUEST message from another cell from
a UE for which RRC connection setup on CCH is already ongoing. This counter is updated for the cell
where the original RRC CONNECTION REQUEST message was received.
M1001C241: RRC CONNECTION ACCESS RELEASE DUE TO CELL RESELECTION
Operability class:
Counter ID: M1001C681 Network element name: RRC SETUP ATTEMPT REPEATS
CCH
Version: 1.0 NetAct name: RRC_CONN_STP_ATT_REPEAT_CCH
Description: The number of repeated RRC connection setup attempts using CCH. Also counter
Updated: When the RNC receives an RRC CONNECTION REQUEST message from a UE within
MAX(WaitTimeRRC+N300*T300+2.5s, 17.5s), after rejecting the previous attempt with an RRC
CONNECTION REJECT. This counter is updated for the cell where the repeated RRC CONNECTION
REQUEST message is received.
Issue: 12G DN99581291 101

Operability class:
2.3 RRC access

RRC access starts when the RNC sends an RRC: RRC CONNECTION SETUP
message to the UE.
RRC access is completed when the RNC receives the RRC: RRC CONNECTION
SETUP COMPLETE message from the UE.
RRC access fails if the UE does not reply to the RRC: RRC CONNECTION SETUP
message with the RRC: RRC CONNECTION SETUP COMPLETE message in a given
time, if the BTS reports a radio link synchronisation failure, or if an RNC internal failure
occurs. When an RRC access failure occurs, the RNC releases all the reserved
resources (RNC, BTS, air, transport).
RRC access is released in the cell reselection case. It happens if the following conditions
are valid simultaneously for the same UE:
• The RNC has sent an RRC: RRC CONNECTION SETUP message to the UE and
waits for the RRC: RRC CONNECTION SETUP COMPLETE message from the UE.
• The RNC receives an RRC: RRC CONNECTION REQUEST message from the UE
in a new cell.
2.3.1 RRC access completions

Counter ID: M1001C8 Network element name: RRC ACC COMP
Version: 7.1 NetAct name: RRC_CONN_ACC_COMP
Description: The number of completed RRC access phases. Note that from RN5.0 onwards this
counter does not include incoming relocations and hard handovers because they have dedicated
counters.
Updated: When the RNC receives an RRC: RRC CONNECTION SETUP COMPLETE message from
the UE.
102 DN99581291 Issue: 12G

Operability class:
RAN 1.008: RAN - MS Connection Establishment 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement name (Clause header): Successful RRC connection establishments
3GPP Measurement type: RRC.SuccConnEstab.Sum
Counter ID: M1001C630 Network element name: RRC SETUP SUCCESS
CONVERSATIONAL
Version: 1.1 NetAct name: SUCC_RRC_SETUP_CONV
Description: The number of successful RRC connection setups for a conversational call. Both
originating and terminating conversational calls are included. RRC connections established via SRNC
relocation, Inter-RNC HHO or CS Inter-System handover are not included.
Updated: When the RRC connection is set up successfully, i.e. RNC receives RRC: RRC
CONNECTION SETUP COMPLETE and the establishment cause in the preceding RRC: RRC
CONNECTION REQUEST has been either Originating Conversational Call or Terminating
Conversational Call.
Operability class:
RAN 1601: Complementary Counters in RU10
Issue: 12G DN99581291 103

STREAMING
Version: 1.0 NetAct name: SUCC_RRC_SETUP_STREA
Description: The number of successful RRC connection setups for a streaming call. Both originating
and terminating streaming calls are included. RRC connections established via SRNC relocation, Inter-
RNC HHO or CS Inter-System handover are not included.
CONNECTION REQUEST has been either Originating Streaming Call or Terminating Streaming Call.
Operability class:
INTERACTIVE
Version: 1.0 NetAct name: SUCC_RRC_SETUP_INTERA
Description: The number of successful RRC connection setups for a interactive call. Both originating
and terminating interactive calls are included. RRC connections established via SRNC relocation, Inter-
RNC HHO or CS Inter-System handover are not included.
CONNECTION REQUEST has been either Originating Interactive Call or Terminating Interactive Call.
104 DN99581291 Issue: 12G

Operability class:
BACKGROUND
Version: 1.0 NetAct name: SUCC_RRC_SETUP_BACKG
Description: The number of successful RRC connection setups for a background call. Both originating
and terminating background calls are included. RRC connections established via SRNC relocation,
Inter-RNC HHO or CS Inter-System handover are not included.
CONNECTION REQUEST has been either Originating Background Call or Terminating Background
Call.
Operability class:
Counter ID: M1001C634 Network element name: RRC SETUP SUCCESS OTHER
Issue: 12G DN99581291 105

Version: 1.0 NetAct name: SUCC_RRC_SETUP_OTHER
Description: The number of successful RRC connection setups with establishment cause other than
those covered by counters M1001C630-M1001C633. RRC connections established via SRNC
relocation, Inter-RNC HHO or CS Inter-System handover are not included.
CONNECTION REQUEST has been some other cause.
Operability class:
2.3.2 RRC access failures

Counter ID: M1001C9 Network element name: RRC ACC FAIL DUE TO RADIO INT
SYNCH
Version: 10.0 NetAct name: RRC_CONN_ACC_FAIL_RADIO
Description: The number of RRC access failures caused by radio interface synchronization failure.
Updated: When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE
message from the UE within 11 seconds, and the RNC has not received the NBAP message which
indicates that L1 synchronization has been established between UE and BTS. Note that from RN5.0
onwards this counter does not include incoming relocation and hard handover failures.
Dependencies on counters:
Operability class:
106 DN99581291 Issue: 12G

Counter ID: M1001C10 Network element name: RRC ACC FAIL DUE TO UU INT
Version: 11.1 NetAct name: RRC_CONN_ACC_FAIL_MS
Description: The number of RRC access failures caused by UE.
Updated: When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE
message from the UE within 11 seconds, and the RNC has received the NBAP message which
indicates that L1 synchronisation has been established between UE and BTS. This counter is updated
also in case the UE does not respond RRC CONNECTION SETUP COMPLETE when attempting to
setup RRC connection to Cell_FACH state, even if in that case L1 synchronization is not expected.
Note that from RN5.0 onwards this counter does not include incoming relocation and hard handover
failures.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.FailConnEstab.NoReply
Counter ID: M1001C11 Network element name: RRC ACC FAIL DUE TO RNC
INTER REASONS
Version: 7.1 NetAct name: RRC_CONN_ACC_FAIL_RNC
Issue: 12G DN99581291 107

Description: The number of RRC access failures caused by reasons not covered by the other failure
counters.
Updated: When an RNC internal failure occurs before receiving the RRC: RRC CONNECTION SETUP
COMPLETE message from the UE.
Operability class:
2.3.3 RRC access releases

Counter ID: M1001C241 Network element name: RRC CONNECTION ACCESS
RELEASE DUE TO CELL RESELECTION
Version: 5.2 NetAct name: RRC_CONN_ACC_REL_CELL_RESEL
Description: The number of RRC Connection Access releases due to cell reselection. This is the case
when the UE has sent a new RRC connection request to the new cell while the RRC connection setup
phase is still ongoing in the old cell. The RNC releases resources for the old RRC connection attempt.
Updated: When the RRC Connection attempt is released before the RRC Connection Setup Complete
is received from the UE due to a new RRC Connection Request to another cell.
Operability class:
108 DN99581291 Issue: 12G

Used from release: RN1.5.2ED2 Definition updated in release:
Counter ID: M1001C553 Network element name: RRC ACCESS RELEASE MO
CONVERSATIONAL CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MO_CONV
Description: The number of RRC connection access releases due to cell reselection for calls
established with the cause originating conversational call. This is the case when the UE has sent a new
RRC connection request to the new cell while the RRC connection setup phase is still ongoing in the
old cell. The RNC releases resources for the old RRC connection attempt.
Updated: When the RRC connection attempt is released before the RRC Connection Setup Complete
message is received from the UE due to a new RRC connection request to another cell.
Operability class:
STREAMING CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MO_STREAMING
established with the cause originating streaming call. This is the case when the UE has sent a new
Issue: 12G DN99581291 109

Operability class:
INTERACTIVE CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MO_INTERACTIVE
established with the cause originating interactive call. This is the case when the UE has sent a new
Operability class:
110 DN99581291 Issue: 12G

BACKGROUND CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MO_BACKGROUND
established with the cause originating background call. This is the case when the UE has sent a new
Operability class:
SUBSCRIBED TRAFFIC CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MO_SUBSCRIBED
established with the cause originating subscribed traffic call. This is the case when the UE has sent a
new RRC connection request to the new cell while the RRC connection setup phase is still ongoing in
the old cell. The RNC releases resources for the old RRC connection attempt.
Issue: 12G DN99581291 111

Operability class:
Counter ID: M1001C558 Network element name: RRC ACCESS RELEASE MT
CONVERSATIONAL CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MT_CONV
established with the cause terminating conversational call. This is the case when the UE has sent a
Operability class:
112 DN99581291 Issue: 12G

STREAMING CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MT_STREAMING
established with the cause terminating streaming call. This is the case when the UE has sent a new
Operability class:
INTERACTIVE CALL
Version: 3.1 NetAct name: RRC_ACC_REL_INTERACTIVE
established with the cause terminating interactive call. This is the case when the UE has sent a new
Issue: 12G DN99581291 113

Operability class:
BACKGROUND CALL
Version: 3.1 NetAct name: RRC_ACC_REL_MT_BACKGROUND
established with the cause terminating background call. This is the case when the UE has sent a new
Operability class:
Counter ID: M1001C562 Network element name: RRC ACCESS RELEASE
EMERGENCY CALL
Version: 3.1 NetAct name: RRC_ACC_REL_EMERGENCY
114 DN99581291 Issue: 12G

established with the cause emergency call. This is the case when the UE has sent a new RRC
connection request to the new cell while the RRC connection setup phase is still ongoing in the old cell.
The RNC releases resources for the old RRC connection attempt.
Operability class:
Counter ID: M1001C563 Network element name: RRC ACCESS RELEASE INTER
RAT CELL RESEL
Version: 3.1 NetAct name: RRC_ACC_REL_INTER_RAT_RESEL
established with the cause inter-RAT cell reselection. This is the case when the UE has sent a new
Operability class:
Issue: 12G DN99581291 115

Counter ID: M1001C564 Network element name: RRC ACCESS RELEASE INTER
RAT CELL CHANGE ORDER
Version: 3.1 NetAct name: RRC_ACC_REL_INTER_RAT_CCO
established with the cause inter-RAT cell change order. This is the case when the UE has sent a new
Operability class:
Counter ID: M1001C565 Network element name: RRC ACCESS RELEASE
REGISTRATION
Version: 3.1 NetAct name: RRC_ACC_REL_REGISTRATION
116 DN99581291 Issue: 12G

established with the cause registration. This is the case when the UE has sent a new RRC connection
releases resources for the old RRC connection attempt.
Updated: When the RRC Connection attempt is released before the RRC Connection Setup Complete
message is received from the UE due to a new RRC Connection Request to another cell.
Operability class:
Counter ID: M1001C566 Network element name: RRC ACCESS RELEASE DETACH
Version: 3.1 NetAct name: RRC_ACC_REL_DETACH
established with the cause detach. This is the case when the UE has sent a new RRC connection
releases resources for the old RRC connection attempt.
Operability class:
Issue: 12G DN99581291 117

Counter ID: M1001C567 Network element name: RRC ACCESS RELEASE MO HIGH
PRIORITY SIGNALLING
Version: 3.1 NetAct name: RRC_ACC_REL_MO_HIGH_PR_SIGN
established with the cause originating high priority signalling. This is the case when the UE has sent a
Operability class:
Counter ID: M1001C568 Network element name: RRC ACCESS RELEASE MO LOW
PRIORITY SIGNALLING
Version: 3.1 NetAct name: RRC_ACC_REL_MO_LOW_PR_SIGN
established with the cause originating low priority signalling. This is the case when the UE has sent a
118 DN99581291 Issue: 12G

Operability class:
Counter ID: M1001C569 Network element name: RRC ACCESS RELEASE CALL RE-
ESTABLISHMENT
Version: 3.1 NetAct name: RRC_ACC_REL_CALL_RE_ESTAB
established with the cause call re-establishment. This is the case when the UE has sent a new RRC
connection request to the new cell while the RRC connection setup phase is still ongoing in the old cell.
The RNC releases resources for the old RRC connection attempt.
Operability class:
Issue: 12G DN99581291 119

Counter ID: M1001C570 Network element name: RRC ACCESS RELEASE MT HIGH
PRIORITY SIGNALLING
Version: 3.1 NetAct name: RRC_ACC_REL_MT_HIGH_PR_SIGN
established with the cause terminating high priority signalling. This is the case when the UE has sent a
Operability class:
Counter ID: M1001C571 Network element name: RRC ACCESS RELEASE MT LOW
PRIORITY SIGNALLING
Version: 3.1 NetAct name: RRC_ACC_REL_MT_LOW_PR_SIGN
established with the cause terminating low priority signalling. This is the case when the UE has sent a
120 DN99581291 Issue: 12G

Operability class:
CAUSE UNKNOWN
Version: 8.2 NetAct name: RRC_ACC_REL_MT_CAUSE_UNKNOWN
Description: The number of RRC connection access releases because of cell reselection for calls
established with the cause "Terminating - cause unknown". This is the case when the UE has sent a
the old cell. The RNC releases resources for the old RRC connection attempt. Such cases are also
included in this "unknown" category when the establishment cause IE of RRC Connection Request is
out of the expected range, for example, because of RACH frame corruption.
message is received from the UE because of a new RRC connection request to another cell.
Operability class:
Issue: 12G DN99581291 121

Counter ID: M1001C750 Network element name: RRC SETUP ATT REPEAT CSFB
Version: 1.0 NetAct name: RRC_ATT_REP_CSFB
Description: The number of RRC connection setup repetitions for CS fallback.
RRC CONNECTION REQUEST with "CSFB Indication" IE during the time interval defined as the
shorter one of these alternatives:
A) WaitTimeRRC+N300*T300 + 2.5 s
B) 17.5 s
Operability class:
2.4 RRC active

RRC active starts when the RNC sends a RANAP: INITIAL UE MESSAGE message to
the CN.
RRC active is completed when the RNC releases the RRC connection after receiving
RANAP: IU RELEASE COMMAND from the CN.
122 DN99581291 Issue: 12G

RRC active fails when an interface-related (Iu, Iur, Iub, or Uu) or RNC internal failure
occurs, and the failure causes the release of the RRC connection. When an RRC active
failure occurs, the RNC sends a RANAP: IU RELEASE REQUEST to all involved CNs
and waits for RANAP: IU RELEASE COMMAND message(s).
In addition to completed and failed RRC active phase counters, this section includes so-
called "active release" counters. They provide information on RRC active releases, the
cause of which has been either inter-system handover, intra-system hard handover,
SRNS relocation, or pre-emption.
g Note: The cause of the RANAP: IU RELEASE COMMAND message does not have
any effect on counter updates. If the CN initiates the release of the Iu signalling
connection (that is, the RNC has not sent a RANAP: IU RELEASE REQUEST message
to the CN), the RNC always updates the RRC active complete counter, not any failure
counter.
2.4.1 RRC active completions

Counter ID: M1001C12 Network element name: RRC ACTIVE COMP
Version: 5.3 NetAct name: RRC_CONN_ACT_COMP
Description: The number of normal completions of RRC active phases.
Updated: When the RNC receives an RANAP: IU RELEASE COMMAND from the CN, and the RNC
has not sent an RANAP: IU RELEASE REQUEST message to the CN before that, and no other Iu
connections for the UE exist. Exception 1: This counter is updated if the RRC connection is released
due to PS inactivity (even though RNC sends an RANAP: IU RELEASE REQUEST message to the CN
in this case). Exception 2: This counter is not updated in case of SRNS relocation, inter-RNC hard
handover, or inter-system handover. Exception 3: This counter is not updated if the RANAP: IU
RELEASE COMMAND cause is "Requested Ciphering and/or Integrity Protection Algorithms not
Supported". In that case counter M1001C19 is updated instead.
Operability class:
Issue: 12G DN99581291 123

2.4.2 RRC active releases

Counter ID: M1001C13 Network element name: RRC ACTIVE REL DUE TO SRNC
RELOC
Version: 6.2 NetAct name: RRC_CONN_ACT_REL_SRNC
Description: The number of RRC Connection Active Releases due to UE not involved SRNC relocation
or Directed Signalling Connection Re-establishment. Note: From RN4.0 onwards this counter does not
include inter-RNC hard handover and inter-system handover but they have dedicated counters.
Updated: When the RRC connection is released due to SRNC relocation or Directed Signalling
Connection Re-establishment due to Cell Update via DRNC.
Operability class:
RAN419: SRNS Relocation
Counter ID: M1001C14 Network element name: RRC ACTIVE REL DUE TO PRE
EMP
Version: 6.1 NetAct name: RRC_CONN_ACT_REL_P_EMP
Description: The number of RRC active releases due to pre-emption.
Updated: When the RRC connection is released in order to make room for a higher priority RAB, for
example, an emergency call. (For more information, see section Failure and abnormal release causes.)
Operability class:
124 DN99581291 Issue: 12G

Counter ID: M1001C421 Network element name: RRC CONN ACTIVE REL DUE TO
UNSPEC ERROR IN CN
Version: 4.3 NetAct name: RRC_CONN_ACT_REL_UNSPEC_CN
Description: The number of RRC connection active releases with "unspecified failure" cause received
from CN. Also M1001C12 is updated along with this counter.
Updated: When a RANAP:IU RELEASE COMMAND message with cause "unspecified failure" is
received from CN.
M1001C12: RRC ACTIVE COMP
Operability class:
Counter ID: M1001C628 Network element name: RRC CONN RELEASE DUE TO
USER INACTIVITY
Version: 1.2 NetAct name: RRC_CONN_REL_DUE_INACTIVITY
Description: The number of RRC connection releases due to user inactivity in Cell-PCH or URA-PCH
state. Also counter M1001C12 is updated along with this counter.
Updated: When the RNC releases the RRC/Iu-PS connection based on the MSActivitySupervision
timer using release cause 'User Inactivity'.
Issue: 12G DN99581291 125

Operability class:
RAN 833: PS UE States: URA PCH
Counter ID: M1001C629 Network element name: RRC CONN RELEASE DUE TO
RNC HW RESOURCES
Version: 1.2 NetAct name: RRC_CONN_REL_DUE_HW_RES
Description: The number of RRC connection releases due to RNC HW resources. Also counter
Updated: When the RNC releases the RRC/Iu-PS connection due to the HW-resource shortage in
ICSU-units (amount of simultaneous RRC-connections) or in DMCU-units (no L2 processing resources
available for UE DCCH/DTCH).
Operability class:
RAN 833: PS UE States: URA PCH
Counter ID: M1001C640 Network element name: RRC ACTIVE RELEASE AFTER
SUCCESSFUL DIRECTED RETRY
126 DN99581291 Issue: 12G

Version: 1.0 NetAct name: RRC_ACT_REL_DIRECTED_RETRY
Description: The number of RRC connections released after a successful Directed Retry inter-system
handover procedure for CS Voice calls. Also some RAB setup failure counter is updated before this
counter. This counter does not include Wireless Priority Service related inter-system handovers.
Updated: When the inter-system handover triggered by directed retry is successful.
M1001C803: RRC ACTIVE REL DUE TO ISHO
Operability class:
RAN 928: Directed Retry
Counter ID: M1001C642 Network element name: RRC ACTIVE REL DUE TO INTRA-
FREQ HHO
Version: 1.0 NetAct name: RRC_CONN_ACT_REL_INTRA_HHO
Description: The number of RRC active releases due to intra-frequency inter-RNC hard handover.
Updated: When the RNC receives RANAP: IU RELEASE COMMAND with cause "successful
relocation" from the CN.
Operability class:
Issue: 12G DN99581291 127

Counter ID: M1001C643 Network element name: RRC ACTIVE REL DUE TO GANHO
Version: 1.0 NetAct name: RRC_CONN_ACT_REL_GANHO
Description: The number of RRC active releases due to inter-system handover to Generic Access
Network (GAN).
Operability class:
RAN1183: UTRAN-GAN Interworking
Counter ID: M1001C800 Network element name: RRC ACTIVE REL DUE TO INTER-
FREQ HHO
Version: 1.0 NetAct name: RRC_CONN_ACT_REL_HHO
Description: The number of RRC active releases due to inter-frequency inter-RNC hard handover.
Operability class:
128 DN99581291 Issue: 12G

RAN 1.5010: Inter Frequency HHO
Counter ID: M1001C803 Network element name: RRC ACTIVE REL DUE TO ISHO
Version: 7.1 NetAct name: RRC_CONN_ACT_REL_ISHO
Description: The number of RRC active releases due to inter system handover to GSM or LTE, or due
to SRNS CONTEXT REQUEST received from the CN.
relocation" from the CN. Also RANAP: SRNS CONTEXT REQUEST received for a PS call triggers this
counter update, even if it is not always reselection to another radio technology but can also be
reselection to another RNC.
Operability class:
RAN 1.5009: WCDMA - GSM Inter System Handover
Used from release: Definition updated in release:
RN4.0
2.4.3 RRC active failures

Counter ID: M1001C15 Network element name: RRC ACTIVE FAIL DUE TO IU INT
Version: 13.1 NetAct name: RRC_CONN_ACT_FAIL_IU
Issue: 12G DN99581291 129

Description: The number of RRC active failures caused by Iu-interface related problem.
Updated: When an Iu interface related failure occurs, and the failure causes the release of the RRC
connection. A typical reason for this is that the CN rejects SCCP connection establishment, for
example because a service area corresponding to WCEL->SAC is not configured on the core network
side.
Operability class:
RAN1.010: RAN Radio Access Bearer Services
RN1.5.1
Counter ID: M1001C16 Network element name: RRC ACTIVE FAIL DUE TO RADIO
INTERFACE
Version: 6.1 NetAct name: RRC_CONN_ACT_FAIL_RADIO
Description: The number of RRC active failures due to radio interface.
Updated: When a radio interface failure occurs, and the failure causes the release of the RRC
connection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. (For
more information, see section Failure and abnormal release causes.)
Operability class:
130 DN99581291 Issue: 12G

Used from release: RN1.5.1 Definition updated in release:
Counter ID: M1001C17 Network element name: RRC ACTIVE FAIL DUE TO BTS
REASONS
Version: 6.1 NetAct name: RRC_CONN_ACT_FAIL_BTS
Description: The number of RRC active failures due to BTS.
Updated: When a BTS failure occurs, and the failure causes the release of the RRC connection. After
this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. (For more information,
see section Failure and abnormal release causes.)
Operability class:
Counter ID: M1001C18 Network element name: RRC ACTIVE FAIL DUE TO THE
IUR INT
Version: 6.1 NetAct name: RRC_CONN_ACT_FAIL_IUR
Description: The number of RRC active failures due to drift RNC.
Updated: When a procedure failure in drift RNC occurs, and the failure causes the release of the RRC
connection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. (For
more information, see section Failure and abnormal release causes.)
Issue: 12G DN99581291 131

Operability class:
Counter ID: M1001C19 Network element name: RRC ACTIVE FAIL DUE TO CIPH
FAIL
Version: 6.1 NetAct name: RRC_CONN_ACT_FAIL_CIPH
Description: The number of RRC connection releases after a failed Security Mode Control procedure.
Updated: When the RNC releases the RRC connection after receiving RANAP: IU RELEASE
COMMAND with cause "Requested Ciphering and/or Integrity Protection Algorithms not Supported"
from the core network.
Operability class:
Counter ID: M1001C21 Network element name: RRC ACTIVE FAIL DUE TO RNC
INTER REASONS
Version: 7.1 NetAct name: RRC_CONN_ACT_FAIL_RNC
Description: The number of RRC active failures due to reasons not covered by the other failure
counters.
132 DN99581291 Issue: 12G

Updated: When such failure happens that is not covered by the other failure counters, and the failure
causes the release of the RRC connection. After this, the RNC sends an RANAP: IU RELEASE
REQUEST to all involved CNs.
Operability class:
Counter ID: M1001C391 Network element name: RRC ACTIVE FAIL DUE TO UE
Version: 5.1 NetAct name: RRC_CONN_ACT_FAIL_UE
Description: Number of RRC active failures due to UE.
Updated: When the RRC connection is released due to the UE not responding to an RRC message or
responding with such failure message that the connection must be released. After this, the RNC sends
a RANAP: IU RELEASE REQUEST to all involved CNs. (See the section "Failure and abnormal
release causes" for more details)
Operability class:
Issue: 12G DN99581291 133

Counter ID: M1001C635 Network element name: SRB ACTIVE FAILURE
CONVERSATIONAL
Version: 1.2 NetAct name: SRB_ACT_FAIL_CONV
Description: The number of abnormally released RRC connections with standalone signalling radio
bearer before RAB assignment. Both originating and terminating conversational calls are included.
Updated: When a standalone SRB is released due to some failure, i.e. when it is counted as RRC
Active Failure in the old Service Level counters. The counter is updated when the establishment cause
in RRC: RRC CONNECTION REQUEST is either Originating Conversational Call or Terminating
Conversational Call.
Operability class:
STREAMING
Version: 1.2 NetAct name: SRB_ACT_FAIL_STREA
bearer before RAB assignment. Both originating and terminating streaming calls are included.
in RRC: RRC CONNECTION REQUEST is either Originating Streaming Call or Terminating Streaming
Call.
134 DN99581291 Issue: 12G

Operability class:
INTERACTIVE
Version: 1.2 NetAct name: SRB_ACT_FAIL_INTERA
bearer before RAB assignment. Both originating and terminating interactive calls are included.
in RRC: RRC CONNECTION REQUEST is either Originating Interactive Call or Terminating Interactive
Call.
Operability class:
BACKGROUND
Issue: 12G DN99581291 135

Version: 1.2 NetAct name: SRB_ACT_FAIL_BACKG
bearer before RAB assignment. Both originating and terminating background calls are included.
in RRC: RRC CONNECTION REQUEST is either Originating Background Call or Terminating
Background Call.
Operability class:
Counter ID: M1001C639 Network element name: SRB ACTIVE FAILURE OTHER
Version: 1.2 NetAct name: SRB_ACT_FAIL_OTHER
bearer before RAB assignment.
in RRC: RRC CONNECTION REQUEST is some other cause not covered by counters M1001C635-
M1001C638.
Operability class:
136 DN99581291 Issue: 12G

Counter ID: M1001C689 Network element name: RRC ACTIVE FAIL DUE TO TRANS
Version: 1.0 NetAct name: RRC_CONN_ACT_FAIL_TRANS
Description: The number of RRC active failures due to transmission.
Updated: When a transmission failure occurs and causes the release of the RRC connection.
Operability class:
2.4.4 Reference cell change

Counter ID: M1001C443 Network element name: RRC CONNECTION LEAVES OLD
REF CELL
Version: 3.1 NetAct name: RRC_CONN_OUT_REF_CELL
Description: The number of RRC Connections that have left from the old reference cell.
Updated: When the RRC connection leaves the old reference cell.
Issue: 12G DN99581291 137

Operability class:
Counter ID: M1001C466 Network element name: RRC CONNECTION ENTERS NEW
REF CELL
Version: 3.1 NetAct name: RRC_CONN_IN_REF_CELL
Description: The number of RRC connections that enter a new reference cell.
Updated: When the RRC connection enters a new reference cell.
Operability class:
2.5 RRC setup attempts and failures per establishment

cause
This section contains RRC setup attempt and failure counters per establishment cause
as specified by 3GPP TS 25.331.
138 DN99581291 Issue: 12G

RRC setup attempt and failure terms are described in section RRC setup.
2.5.1 Mobile originating conversational call

Counter ID: M1001C22 Network element name: MOBILE ORIGINATING
CONVERSATIONAL CALL ATTEMPTS
Version: 6.3 NetAct name: MOC_CONV_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Originating
conversational call".
Updated: When the RNC receives RRC connection request with establishment cause "Originating
Operability class:
RAN 1.010: RAN Radio Access Bearer Services 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingConversationalCall
CONVERSATIONAL CALL FAILURES
Version: 7.1 NetAct name: MOC_CONV_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Originating
Updated: When the RNC sends RRC: RRC CONNECTION REJECT to the UE or the connection
attempt fails while waiting for RRC: CONNECTION SETUP COMPLETE from the UE, after RRC
connection request with establishment cause "Originating conversational call".
Issue: 12G DN99581291 139

Operability class:
2.5.2 Mobile originating streaming call

STREAMING CALL ATTEMPTS
Version: 6.3 NetAct name: MOC_STREA_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Originating streaming
call".
streaming call".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingStreamingCall
140 DN99581291 Issue: 12G

STREAMING CALL FAILURES
Version: 7.1 NetAct name: MOC_STREA_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Originating streaming
call".
connection request with establishment cause "Originating streaming call".
Operability class:
2.5.3 Mobile originating interactive call

INTERACTIVE CALL ATTEMPTS
Version: 6.3 NetAct name: MOC_INTER_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Originating interactive
call".
interactive call".
Operability class:
Issue: 12G DN99581291 141

3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingInteractiveCall
INTERACTIVE CALL FAILURES
Version: 7.1 NetAct name: MOC_INTER_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Originating interactive
call".
connection request with establishment cause "Originating interactive call".
Operability class:
2.5.4 Mobile originating background call

BACKGROUND CALL ATTEMPTS
Version: 6.3 NetAct name: MOC_BACKG_CALL_ATTS
142 DN99581291 Issue: 12G

background call".
background call".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingBackgroundCall
BACKGROUND CALL FAILURES
Version: 7.1 NetAct name: MOC_BACKG_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Originating background
call".
connection request with establishment cause "Originating background call".
Operability class:
Issue: 12G DN99581291 143

2.5.5 Mobile originating subscribed traffic call

SUBSCRIBED TRAFFIC CALL ATTEMPTS
Version: 6.3 NetAct name: MOC_SUBSC_TRAF_CALL_ATTS
subscribed traffic call".
subscribed traffic call".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingSubscribedtrafficCall
SUBSCRIBED TRAFFIC CALL FAILURES
Version: 7.1 NetAct name: MOC_SUBSC_TRAF_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Originating subscribed
traffic call".
144 DN99581291 Issue: 12G

connection request with establishment cause "Originating subscribed traffic call".
Operability class:
2.5.6 Mobile terminating conversational call

Counter ID: M1001C32 Network element name: MOBILE TERMINATING
CONVERSATIONAL CALL ATTEMPTS
Version: 6.3 NetAct name: MTC_CONV_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Terminating
Updated: When the RNC receives RRC connection request with establishment cause "Terminating
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
Issue: 12G DN99581291 145

3GPP Measurement type: RRC.AttConnEstab.TerminatingConversationalCall
CONVERSATIONAL CALL FAILURES
Version: 7.1 NetAct name: MTC_CONV_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Terminating
connection request with establishment cause "Terminating conversational call".
Operability class:
2.5.7 Mobile terminating streaming call

STREAMING CALL ATTEMPTS
Version: 6.3 NetAct name: MTC_STREA_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Terminating streaming
call".
streaming call".
146 DN99581291 Issue: 12G

Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.TerminatingStreamingCall
STREAMING CALL FAILURES
Version: 7.1 NetAct name: MTC_STREA_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Terminating streaming
call".
connection request with establishment cause "Terminating streaming call".
Operability class:
Issue: 12G DN99581291 147

2.5.8 Mobile terminating interactive call

INTERACTIVE CALL ATTEMPTS
Version: 6.3 NetAct name: MTC_INTER_CALL_ATTS
interactive call".
interactive call".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.TerminatingInteractiveCall
INTERACTIVE CALL FAILURES
Version: 7.1 NetAct name: MTC_INTER_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Terminating interactive
call".
connection request with establishment cause "Terminating interactive call".
148 DN99581291 Issue: 12G

Operability class:
2.5.9 Mobile terminating background call

BACKGROUND CALL ATTEMPTS
Version: 6.3 NetAct name: MTC_BACKG_CALL_ATTS
background call".
background call".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.TerminatingBackgroundCall
BACKGROUND CALL FAILURES
Issue: 12G DN99581291 149

Version: 7.1 NetAct name: MTC_BACKG_CALL_FAILS
Description: The number of failed RRC connection establishments with cause "Terminating background
call".
connection request with establishment cause "Terminating background call".
Operability class:
2.5.10 Emergency call

Counter ID: M1001C40 Network element name: EMERGENCY CALL ATTEMPTS
Version: 11.1 NetAct name: EMERGENCY_CALL_ATTS
Description: The number of RRC connection attempts with establishment cause "Emergency Call".
Updated: When the RNC receives RRC connection request with establishment cause "Emergency Call"
Operability class:
RAN1.010: RAN Radio Access Bearer Services 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
150 DN99581291 Issue: 12G

3GPP Measurement type: RRC.AttConnEstab.EmergencyCall
Counter ID: M1001C41 Network element name: EMERGENCY CALL FAILURES
Version: 7.1 NetAct name: EMERGENCY_CALL_FAILS
Description: The number of emergency call attempts that have not been admitted in the RNC either
due to a failure in RRC connection establishment procedure or due to RRC connection redirection to
GSM.
connection request with establishment cause 'emergency call'.
M1001C617: RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTION
Operability class:
RAN1177: Emergency Call Redirect to GSM
2.5.11 Inter-RAT cell reselection

Counter ID: M1001C42 Network element name: INTR_RAT_CELL_RE_SELECT
ATTEMPTS
Version: 5.3 NetAct name: INTR_RAT_CELL_RE_SEL_ATTS
Description: The number of RRC connection attempts with establishment cause "Inter-RAT cell re-
selection".
Issue: 12G DN99581291 151

Updated: When the RNC receives RRC connection request with establishment cause "Inter-RAT cell
re-selection".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Inter-RATcellre-selection
Counter ID: M1001C43 Network element name: INTR_RAT_CELL_RE_SELECT
FAILURES
Version: 7.1 NetAct name: INTR_RAT_CELL_RE_SEL_FAILS
Description: The number of failed RRC connection establishments with cause "Inter-RAT cell re-
selection".
connection request with establishment cause "Inter-RAT cell re-selection".
Operability class:
152 DN99581291 Issue: 12G

2.5.12 Inter-RAT cell change order

Counter ID: M1001C44 Network element name: INTR_RAT_CELL_CHNG_ORD
ATTEMPTS
Version: 5.3 NetAct name: CELL_CHNG_ORD_ATTS
Description: The number of RRC connection attempts with establishment cause "Inter-RAT cell change
order".
Updated: When the RNC receives RRC connection request with establishment cause "Inter-RAT cell
change order".
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Inter-RATcellchangeorder
Counter ID: M1001C45 Network element name: INTR_RAT_CELL_CHNG_ORD
FAILURES
Version: 7.1 NetAct name: CELL_CHNG_ORD_FAILS
Description: The number of failed RRC connection establishments with cause "Inter-RAT cell change
order".
connection request with establishment cause "Inter-RAT cell change order".
Issue: 12G DN99581291 153

Operability class:
2.5.13 Registration
Counter ID: M1001C46 Network element name: REGISTRATION ATTEMPTS
Version: 6.2 NetAct name: REGISTRATION_ATTS
Description: The number of registration attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Registration".
Logical type: Sum Trigger type: Sampling interval:
Unit: Range: Example values:
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Registration
154 DN99581291 Issue: 12G

Counter ID: M1001C47 Network element name: REGISTRATION FAILURES
Version: 7.1 NetAct name: REGISTRATION_FAILS
Description: The number of registration failures.
connection request with establishment cause "Registration".
Operability class:
2.5.14 Detach
Counter ID: M1001C48 Network element name: DETACH ATTEMPTS
Version: 6.2 NetAct name: DETACH_ATTS
Description: The number of detach attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Detach".
Operability class:
3GPP 32.403, 5.9.0
Issue: 12G DN99581291 155

3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Detach
Counter ID: M1001C49 Network element name: DETACH FAILURES
Version: 7.1 NetAct name: DETACH_FAILS
Description: The number of detach failures.
connection request with establishment cause "Detach".
Operability class:
2.5.15 MOC high priority signalling

Counter ID: M1001C50 Network element name: MOBILE ORIGINATING HIGH
PRIORITY SIGNALLING ATTEMPTS
Version: 6.2 NetAct name: MOC_HIGH_PRIOR_SIGN_ATTS
Description: The number of mobile originating high priority signalling attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Originating high
priority signalling".
156 DN99581291 Issue: 12G

Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingHighPrioritySignalling
Counter ID: M1001C51 Network element name: MOBILE ORIGINATING HIGH
PRIORITY SIGNALLING FAILURES
Version: 7.1 NetAct name: MOC_HIGH_PRIOR_SIGN_FAILS
Description: The number of mobile originating high priority signalling failures.
connection request with establishment cause "Originating high priority signalling".
Operability class:
Issue: 12G DN99581291 157

2.5.16 MTC high priority signalling

Counter ID: M1001C52 Network element name: MOBILE TERMINATING HIGH
Version: 6.2 NetAct name: MTC_HIGH_PRIOR_SIGN_ATTS
Description: The number of mobile terminating high priority signalling attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Terminating high
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.TerminatingHighPrioritySignalling
Counter ID: M1001C53 Network element name: MOBILE TERMINATING HIGH
Version: 7.1 NetAct name: MTC_HIGH_PRIOR_SIGN_FAILS
Description: The number of mobile terminating high priority signalling failures.
connection request with establishment cause "Terminating high priority signalling".
Operability class:
158 DN99581291 Issue: 12G

2.5.17 MOC low priority signalling

Counter ID: M1001C54 Network element name: MOBILE ORIGINATING LOW
Version: 6.2 NetAct name: MOC_LOW_PRIOR_SIGN_ATTS
Description: The number of mobile originating low priority signalling attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Originating low
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.OriginatingLowPrioritySignalling
Counter ID: M1001C55 Network element name: MOBILE ORIGINATING LOW
Version: 7.1 NetAct name: MOC_LOW_PRIOR_SIGN_FAILS
Description: The number of mobile originating low priority signalling failures.
Issue: 12G DN99581291 159

connection request with establishment cause "Originating low priority signalling".
Operability class:
2.5.18 MTC low priority signalling

Counter ID: M1001C56 Network element name: MOBILE TERMINATING LOW
Version: 6.2 NetAct name: MTC_LOW_PRIOR_SIGN_ATTS
Description: The number of mobile terminating low priority signalling attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Terminating low
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
160 DN99581291 Issue: 12G

3GPP Measurement type: RRC.AttConnEstab.TerminatingLowPrioritySignalling
Counter ID: M1001C57 Network element name: MOBILE TERMINATING LOW
Version: 7.1 NetAct name: MTC_LOW_PRIOR_SIGN_FAILS
Description: The number of mobile terminating low priority signalling failures.
connection request with establishment cause "Terminating low priority signalling".
Operability class:
2.5.19 Call re-establishment

Counter ID: M1001C58 Network element name: CALL RE ESTAB ATTEMPTS
Version: 6.2 NetAct name: CALL_RE_ESTAB_ATTS
Description: The number of call re-establishment attempts.
Updated: When the RNC receives RRC connection request with establishment cause "Call re-
establishment".
Issue: 12G DN99581291 161

Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Callre-establishment
Counter ID: M1001C59 Network element name: CALL RE ESTAB FAILURES
Version: 7.1 NetAct name: CALL_RE_ESTAB_FAILS
Description: The number of call re-establishment failures.
connection request with establishment cause "Call re-establishment".
Operability class:
2.5.20 Terminating - cause unknown

Counter ID: M1001C60 Network element name: TERMINATING CAUSE UNKNOWN
ATTEMPTS
162 DN99581291 Issue: 12G

Version: 10.2 NetAct name: MTC_CAUSE_UNKNOWN_ATTS
Description: The number of RRC connection setup attempts with cause "Terminating - cause unknown".
Such cases are also included in this "unknown" category when the establishment cause IE of RRC
Connection Request is out of the expected range, for example, because of RACH frame corruption.
Updated: When the RNC receives RRC connection request with establishment cause "Terminating -
cause unknown".
Operability class:
RAN1.010: RAN Radio Access Bearer Services 3GPP 32.403, 4.8.0
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RRC.AttConnEstab.Terminating - causeunknown
Counter ID: M1001C61 Network element name: TERMINATING CAUSE UNKNOWN
FAILURES
Version: 10.2 NetAct name: MTC_CAUSE_UNKNOWN_FAILS
Description: The number of RRC connection setup failures for requests with establishment cause
"Terminating - cause unknown". Such cases are also included in this "unknown" category when the
establishment cause IE of RRC Connection Request is out of the expected range, for example, because
of RACH frame corruption.
connection request with establishment cause "Terminating - cause unknown".
Operability class:
Issue: 12G DN99581291 163

2.6 RRC establishments per UE capability

This section covers the counters which provide information on the number of RRC
connection establishments per particular UE capabilities. The RNC receives UE
capability information from the UE in the RRC: RRC CONNECTION SETUP COMPLETE
message, or from the core network during relocation preparation procedure.
In case of directed RRC connection setup, these counters are updated for the target cell
of the redirection where RRC: RRC CONNECTION SETUP COMPLETE was received.
Counter ID: M1001C389 Network element name: UE SUPPORT FOR IPHC
Version: 5.3 NetAct name: UE_SUPPORT_FOR_IPHC
Description: The number RRC connection establishments by UEs that support RFC2507 IP header
compression.
Updated: When an RRC connection is successfully established either via RRC: RRC CONNECTION
REQUEST message or incoming relocation/HHO/ISHO. In case of directed RRC connection setup, this
counter is updated for the target cell of the redirection.
Operability class:
Used from release: RN2.1 Definition updated in release: RN4.0
164 DN99581291 Issue: 12G

Counter ID: M1001C404 Network element name: ACCESS STRATUM RELEASE
INDICATOR RELEASE 4
Version: 4.3 NetAct name: ACCESS_STRATUM_REL_IND_4
Description: The number of RRC connection establishments by UEs with access stratum release
indicator release 4.
Operability class:
INDICATOR RELEASE 99
Operability class:
Issue: 12G DN99581291 165

INDICATOR RELEASE 5
Operability class:
Counter ID: M1001C406 Network element name: UE SUPPORT FOR GSM
Version: 4.3 NetAct name: UE_SUPPORT_GSM
Description: The number of RRC connection establishments by UEs that support GSM.
166 DN99581291 Issue: 12G

Operability class:
Counter ID: M1001C407 Network element name: UE SUPPORT FOR MULTI
CARRIER CDMA
Version: 4.3 NetAct name: UE_SUPPORT_MULTICARRIER_CDMA
Description: The number of RRC connection establishments by UEs that support multi-carrier CDMA.
Operability class:
Counter ID: M1001C408 Network element name: UE RXTX TIME DIFFERENCE
POSITIONING CAPABILITY TYPE 2
Version: 4.3 NetAct name: UE_RXTX_POSITION_CAPAB_2
Description: The number of RRC connection establishments by UEs that support RX-TX time difference
positioning capability type 2.
Issue: 12G DN99581291 167

Operability class:
RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical
Coordinates
Counter ID: M1001C548 Network element name: UE SUPPORT FOR HSDSCH
CLASS 1 TO 6
Version: 4.3 NetAct name: UE_SUPP_HSDSCH_CLASS_1_6
Description: The number of RRC connection establishments by UEs supporting HS-DSCH classes 1, 2,
3, 4, 5 or 6. The classes are defined in 3GPP TS 25.306.
Operability class:
RAN 763: Basic HSDPA with QPSK and 5 Codes
168 DN99581291 Issue: 12G

CLASS 7 OR 8
Description: The number of RRC connection establishments by UEs supporting HS-DSCH classes 7 or
8. The classes are defined in 3GPP TS 25.306.
Operability class:
CLASS 9 OR 10
Description: The number of RRC connection establishments by UEs supporting HS-DSCH classes 9 or
10. The classes are defined in 3GPP TS 25.306.
Operability class:
Issue: 12G DN99581291 169

CLASS 11 OR 12
Description: The number of RRC connection establishments by UEs supporting HS-DSCH classes 11
or 12. The classes are defined in 3GPP TS 25.306.
Operability class:
Counter ID: M1001C595 Network element name: UE SUPPORT FOR NETWORK
ASSISTED GPS
Version: 3.3 NetAct name: UE_SUPPORT_NW_AGPS
Description: The number of RRC connection establishments by UEs that support network-assisted
GPS.
170 DN99581291 Issue: 12G

Operability class:
RAN 223: UE Based A-GPS Using External Reference Network
Counter ID: M1001C610 Network element name: UE SUPPORT FOR E-DCH
CATEGORY 1
Version: 2.3 NetAct name: UE_SUPP_EDCH_CATEGORY_1
Description: The number of RRC connection establishments by UEs supporting the E-DCH category 1
defined in 3GPP TS 25.306.
Operability class:
RAN 826: Basic HSUPA
Issue: 12G DN99581291 171

CATEGORY 2
Operability class:
CATEGORY 3
Operability class:
172 DN99581291 Issue: 12G

CATEGORY 4
Operability class:
CATEGORY 5
Issue: 12G DN99581291 173

Operability class:
CATEGORY 6
Operability class:
174 DN99581291 Issue: 12G

INDICATOR RELEASE 6
Operability class:
RAN 997: 3GPP R6 Baseline
Counter ID: M1001C641 Network element name: UE SUPPORT FOR GANHO
Version: 1.2 NetAct name: UE_SUPPORT_GANHO
Description: The number of RRC connection establishments by UEs that support handover to Generic
Access Network (GAN).
Operability class:
RAN1183: UTRAN-GAN Interworking
Issue: 12G DN99581291 175

Counter ID: M1001C671 Network element name: UE SUPPORT FOR CS VOICE
OVER HSPA
Version: 1.0 NetAct name: UE_SUPP_CS_VOICE_OVER_HSPA
Description: The number of RRC connection establishments by UEs that support CS Voice over HSPA.
Updated: When an RRC connection is successfully established either via an RRC: RRC
CONNECTION REQUEST message or incoming relocation/HHO/ISHO by a UE that supports CS Voice
over HSPA.
Operability class:
RAN1689: CS Voice Over HSPA
Used from release: RN5.0 EP1 Definition updated in release:
CLASS 13 OR 14
CONNECTION REQUEST message or incoming relocation/HHO/ISHO by a UE that supports HS-
DSCH physical layer category 13 or 14.
176 DN99581291 Issue: 12G

Operability class:
RAN1643: HSDPA 64QAM
CLASS 15 OR 16
Operability class:
CLASS 17 OR 18
Issue: 12G DN99581291 177

Operability class:
INDICATOR RELEASE 7
Updated: When the access stratum release indicator release 7 is received from the UE in an RRC
Connection Setup Complete message.
Operability class:
178 DN99581291 Issue: 12G

CATEGORY 7
Updated: When the RNC receives an RRC Connection Setup Complete message from a UE and the E-
DCH physical layer category information 7 can be obtained from the message.
Operability class:
Counter ID: M1001C677 Network element name: UE SUPPORT FOR CONTINUOUS
PACKET CONNECTIVITY
Version: 1.0 NetAct name: UE_SUPP_CPC
Description: The number of RRC connection establishments by UEs that support Continuous Packet
Connectivity (CPC).
CONNECTION REQUEST message or incoming relocation/HHO/ISHO by a UE that supports
Continuous Packet Connectivity.
Operability class:
Issue: 12G DN99581291 179

RAN1644: Continuous Packet Connectivity
CLASS 19 OR 20
Operability class:
RAN1642: MIMO 28 Mbps
CLASS 21 OR 22
180 DN99581291 Issue: 12G

Operability class:
CLASS 23 OR 24
Operability class:
Issue: 12G DN99581291 181

INDICATOR RELEASE 8
Operability class:
Counter ID: M1001C715 Network element name: EUTRA CAPABILITY FDD
Version: 1.0 NetAct name: EUTRA_CAPABILITY_FDD
Description: The number of RRC connection establishments by UEs supporting E-UTRA FDD.
Updated: When an RRC connection is successfully established either via RRC Connection Request or
incoming Relocation/HHO/ISHO by an UE that supports E-UTRA FDD. The UE capability information is
received from the UE in RRC: RRC CONNECTION SETUP COMPLETE or from the core network with
RANAP: RELOCATION REQUEST. In case of directed RRC connection setup, this counter is updated
for the target cell of the redirection.
Operability class:
182 DN99581291 Issue: 12G

Counter ID: M1001C716 Network element name: EUTRA CAPABILITY TDD
Version: 1.0 NetAct name: EUTRA_CAPABILITY_TDD
Description: The number of RRC connection establishments by UEs supporting E-UTRA TDD.
Updated: When an RRC connection is successfully established either via RRC Connection Request or
incoming Relocation/HHO/ISHO by an UE that supports E-UTRA TDD. The UE capability information is
received from the UE in RRC: RRC CONNECTION SETUP COMPLETE or from the core network with
RANAP: RELOCATION REQUEST. In case of directed RRC connection setup, this counter is updated
for the target cell of the redirection.
Operability class:
Counter ID: M1001C705 Network element name: UE SUPPORT FOR HS
CELL_FACH
Version: 3.0 NetAct name: UE_SUPP_HS_CELL_FACH
Description: The number of RRC connections established by UEs supporting the HS Cell_FACH
downlink. The counter is updated independently of possible support for HS Cell_FACH uplink.
Updated: When an RRC connection is successfully established via RRC: RRC CONNECTION SETUP
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports HS Cell_FACH
downlink.
Issue: 12G DN99581291 183

Operability class:
RAN1637: High Speed Cell_FACH DL
RAN1913: High Speed Cell_FACH
Used from release: RN6.0 EP2 Definition updated in release:
Counter ID: M1001C706 Network element name: UE SUPPORT FOR FLEXIBLE RLC
UPLINK
Version: 4.2 NetAct name: UE_SUPP_FLEX_RLC_UL
Description: The number of RRC connections established by UEs supporting Flexible-RLC in the uplink
direction.
Updated: When an RRC connection is successfully established with RRC: RRC CONNECTION SETUP
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports Flexible-RLC in the
uplink direction.
Operability class:
RAN1910: Flexible RLC in UL
184 DN99581291 Issue: 12G

CLASS 25 OR 26
Updated: When an RRC connection is successfully established either with an RRC: RRC
Operability class:
RAN1907: DC-HSDPA with MIMO 84Mbps
CLASS 27 OR 28
Operability class:
Issue: 12G DN99581291 185

INDICATOR RELEASE 9
Updated: When an RRC connection is successfully established either with RRC: RRC CONNECTION
Operability class:
CATEGORY 8
186 DN99581291 Issue: 12G

DCH physical layer category information 8 can be obtained from the message. The counter is updated
also during incoming HHO/ISHO/relocation.
Operability class:
RAN1905: DC-HSUPA
CATEGORY 9
DCH physical layer category information 9 can be obtained from the message. The counter is updated
also during incoming HHO/ISHO/relocation.
Operability class:
RAN1905: DC-HSUPA
Issue: 12G DN99581291 187

Counter ID: M1001C713 Network element name: UE SUPPORT FOR HS
CELL_FACH UPLINK
Version: 4.2 NetAct name: UE_SUPP_HS_CELL_FACH_UL
Description: The number of RRC connections established by UEs supporting the HS Cell_FACH uplink
(HS-RACH). Also "M1001C705 UE SUPPORT FOR HS CELL_FACH" is updated along with this
counter because if the UE supports HS-FACH uplink, it supports also HS-FACH downlink.
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports HS Cell_FACH uplink.
Operability class:
RAN1913: High Speed Cell_FACH
Counter ID: M1001C722 Network element name: UE SUPPORT FOR UMTS 850
Version: 1.0 NetAct name: UE_SUPP_UMTS_850
Description: The number of RRC connections established by UEs supporting UMTS band V (850 MHz).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band V.
Operability class:
188 DN99581291 Issue: 12G

Description: The number of RRC connections established by UEs supporting UMTS band VIII (900
MHz).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band VIII.
Operability class:
Description: The number of RRC connections established by UEs supporting UMTS band XI (1500
MHz).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band XI.
Issue: 12G DN99581291 189

Operability class:
Description: The number of RRC connections established by UEs supporting UMTS band IV (1700
MHz / AWS).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band IV.
Operability class:
Description: The number of RRC connections established by UEs supporting UMTS band II (1900
MHz).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band II.
190 DN99581291 Issue: 12G

Operability class:
Description: The number of RRC connections established by UEs supporting UMTS band I (2100
MHz).
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports UMTS band I.
Operability class:
Counter ID: M1001C728 Network element name: UE SUPPORT FOR DB-HSDPA
BAND REL9-1
Version: 1.0 NetAct name: UE_SUPP_DBHSDPA_9_1
Issue: 12G DN99581291 191

Description: The number of RRC connections established by UEs supporting DB-HSDPA band
combination Rel9-1. This refers to table 5.0aA of 3GPP TS 25.101. Configuration 9-1 means UL band I
(2100 MHz) or VIII (900 MHz) and DL bands I (2100 MHz) and VIII (900 MHz). It is possible that also
M1001C729 and M1001C730 are updated along with this counter if the UE supports multiple DB-
HSDPA band combinations.
COMPLETE message or incoming relocation/HHO/ISHO by a UE that supports DB-HSDPA band
combination 9-1.
Operability class:
RAN2179: Dual Band HSDPA 42 Mbps
BAND REL9-2
combination Rel9-2. This refers to table 5.0aA of 3GPP TS 25.101. Configuration 9-2 means UL band II
(1900 MHz) or IV (1700 MHz) and DL bands II (1900 MHz) and IV (1700 MHz). It is possible that also
combination 9-2.
Operability class:
192 DN99581291 Issue: 12G

BAND REL9-3
combination Rel9-3. This refers to table 5.0aA of 3GPP TS 25.101. Configuration 9-3 means UL band I
(2100 MHz) or V (850 MHz) and DL bands I (2100 MHz) and V (850 MHz). It is possible that also
combination 9-3.
Operability class:
Issue: 12G DN99581291 193

Operability class:
RAN1905: DC-HSUPA
RAN2211: Multi-Cell HSDPA
Operability class:
194 DN99581291 Issue: 12G

CLASS 29 OR 30
Operability class:
CLASS 31 OR 32
Issue: 12G DN99581291 195

Operability class:
2.7 Incoming handovers and relocations

This section covers the counters of those handovers in which the serving RNC is to be
changed. Other handover counters are covered by handover-only-measurements
described in the sections Measurement: Soft handover (M1007), Measurement: Intra-
system hard handover (M1008), and Measurement: Inter-system handover (M1010).
The updating principle of M1001 counters during incoming hard handovers and
relocations is changed in the RN5.0 release. The basic RRC and RAB setup related
counters like M1001C0 RRC SETUP ATT and M1001C66 RAB SETUP ATTEMPTS FOR
CS VOICE are not anymore updated during these incoming relocation procedures but
only during initial RRC and RAB establishments performed using RRC CONNECTION
REQUEST and RAB ASSIGNMENT REQUEST.
The incoming hard handovers and relocations are now counted into dedicated counters
like for example M1001C808 RRC RELOC SETUP ATT and M1001C653 RAB RELOC
SETUP ATTEMPTS FOR CS VOICE. These counters are included in chapter Common
counters for incoming relocation and HHO.
The triggers for updating the RRC/RAB related counters during incoming relocation or
hard handover are the following:
• Relocation Setup Attempt counters, for example M1001C653, are updated when
RANAP: RELOCATION REQUEST received from the core network.
• Relocation Access Complete counters, for example M1001C654, are updated when
the target-RNC sends RANAP: RELOCATION COMPLETE to the core network after
the UE has successfully relocated to the new RNC.
If the incoming relocation is cancelled by the core network before completion, then the
counter updates are rolled back and none of these counters gets incremented as a result
of the cancelled relocation procedure.
2.7.1 Serving RNC relocation

Counter ID: M1001C62 Network element name: NUMBER OF SRNC RELOCATION
ATTEMPTS
196 DN99581291 Issue: 12G

Version: 6.2 NetAct name: SRNC_RELOC_ATTS
Description: The number of incoming UE-not-involved SRNC relocation attempts.
Updated: When the target-RNC receives RANAP: RELOCATION REQUEST from the core network for
initiating the relocation procedure.
Operability class:
Counter ID: M1001C63 Network element name: NUMBER OF UNSUCCESSFUL
SRNC RELOCATION ATTEMPTS
Version: 6.2 NetAct name: SRNC_RELOC_FAILS
Description: The number of unsuccessful UE-not-involved SRNC relocation attempts.
Updated: When the incoming relocation fails either in the resource allocation phase or the target-RNC
does not receive RRC: UTRAN MOBILITY INFORMATION COMFIRM from the UE.
Operability class:
Issue: 12G DN99581291 197

2.7.2 Inter-RNC intra-frequency hard handover

Counter ID: M1001C64 Network element name: NUMBER OF INTER-RNC INTRA
FREQ HHO ATTEMPTS
Version: 13.1 NetAct name: INTRA_FREQ_HHO_ATTS
Description: The number of inter-RNC intra-frequency hard handover attempts.
initiating the hard handover procedure. If however the core network later cancels the procedure, also
the counter update is canceled, i.e. the counter includes only those cases where the actual handover
attempt was done from UE point of view.
It is not always possible for the target RNC to distinguish whether the incoming hard handover is intra-
frequency or inter-frequency and therefore this counter can sometimes be updated also in the inter-
frequency inter-RNC hard handover.
Operability class:
RN1.5.1
INTER RNC INTRA FREQ HHO ATTEMPTS
Version: 6.2 NetAct name: INTRA_FREQ_HHO_FAILS
Description: The number of unsuccessful incoming inter-RNC intra-frequency hard handover attempts.
Updated: When the incoming hard handover procedure fails either in the resource allocation phase or
the target-RNC cannot establish connection with the UE.
198 DN99581291 Issue: 12G

Operability class:
2.7.3 Inter-RNC inter-frequency handover

Counter ID: M1001C217 Network element name: NUMBER OF INT RNC INTER
FREQ HHO ATTEMPTS
Version: 6.4 NetAct name: INTER_FREQ_HHO_ATTS
Description: The number of inter-RNC inter-frequency hard handover attempts.
initiating the hard handover procedure. If however the core network later cancels the procedure, also
the counter update is canceled, i.e. the counter includes only those cases where the actual handover
Operability class:
Issue: 12G DN99581291 199

Counter ID: M1001C218 Network element name: NUMBER OF UNSUCCESSFUL INT
RNC INTER FREQ HHO ATTEMPTS
Version: 6.2 NetAct name: INTER_FREQ_HHO_FAILS
Description: The number of unsuccessful incoming inter-RNC inter-frequency hard handover attempts.
Updated: When the incoming hard handover procedure fails either in the resource allocation phase or
the target-RNC cannot establish connection with the UE.
Operability class:
2.7.4 Inter-system handover from GSM or LTE to WCDMA

Counter ID: M1001C219 Network element name: NUMBER OF INTER SYS HHO
ATTEMPTS
Version: 12.1 NetAct name: INTER_SYS_HHO_ATTS
Description: The number of incoming inter-system handover attempts from GSM or LTE.
initiating the handover procedure. If however the core network later cancels the procedure, also the
counter update is canceled, i.e. the counter includes only those cases where the actual handover
Operability class:
200 DN99581291 Issue: 12G

INTER SYS HHO ATTEMPTS
Version: 12.1 NetAct name: INTER_SYSTEM_HHO_FAILS
Description: The number of unsuccessful incoming inter-system hard handover attempts from GSM or
LTE.
Updated: When the incoming handover procedure fails either in the resource allocation phase or the
target-RNC cannot establish connection with the UE.
Operability class:
2.7.5 Common counters for incoming relocation and HHO

Counter ID: M1001C651 Network element name: RAB RELOC SETUP ATTEMPTS
FOR PS DATA STREAM
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_PS_STREA
Description: The number of attempted PS streaming RAB setups during relocation procedure.
Issue: 12G DN99581291 201

Updated: When a target RNC of HHO or relocation receives a RANAP: RELOCATION REQUEST
message from a core network, and the RAB type is PS data streaming.
Operability class:
RAN1136: Separate Counters for Relocations
Counter ID: M1001C652 Network element name: RAB RELOC ACCESS
COMPLETIONS FOR PS DATA STREAM
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_PS_STREA
Description: The number of successfully established PS streaming RABs during relocation procedure.
Updated: When a target RNC of HHO or relocation sends a RANAP: RELOCATION COMPLETE
message to a core network after a successful incoming SRNC relocation, Inter-RNC HHO or ISHO
procedure, and the RAB type is PS data streaming.
Operability class:
202 DN99581291 Issue: 12G

FOR CS VOICE
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_CS_VOICE
Description: The number of attempted CS voice RAB setups during relocation procedure.
message from a core network, and the RAB type is CS voice.
Operability class:
COMPLETIONS FOR CS VOICE
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_CS_VOICE
Description: The number of successfully established CS voice RABs during relocation procedure.
procedure, and the RAB type is CS voice.
Operability class:
Issue: 12G DN99581291 203

FOR CS DATA CONV
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_CS_CONV
Description: The number of attempted CS data conversational RAB setups during relocation procedure.
message from a core network, and the RAB type is CS data conversational.
Operability class:
COMPLETIONS FOR CS DATA CONV
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_CS_CONV
Description: The number of successfully established CS data conversational RABs during relocation
procedure.
procedure, and the RAB type is CS data conversational.
204 DN99581291 Issue: 12G

Operability class:
FOR CS DATA STREAM
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_CS_STREA
Description: The number of attempted CS data streaming RAB setups during relocation procedure.
message from a core network, and the RAB type is CS data streaming.
Operability class:
COMPLETIONS FOR CS DATA STREAM
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_CS_STREA
Description: The number of successfully established CS data streaming RABs during relocation
procedure.
Issue: 12G DN99581291 205

procedure, and the RAB type is CS data streaming.
Operability class:
Counter ID: M1001C808 Network element name: RRC RELOC SETUP ATT
Version: 1.0 NetAct name: RRC_RELOC_STP_ATT
Description: The number of attempted RRC connection setups during relocation procedure.
message from a core network.
Operability class:
206 DN99581291 Issue: 12G

Counter ID: M1001C810 Network element name: RRC RELOC ACCESS
COMPLETIONS
Version: 1.0 NetAct name: RRC_RELOC_ACC_COMP
Description: The number of successfully established RRC connections during relocation procedure.
procedure.
Operability class:
FOR PS INTERACTIVE
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_PS_INT
Description: The number of attempted PS interactive RAB setups during relocation procedure.
message from a core network, and the RAB type is PS data interactive.
Operability class:
Issue: 12G DN99581291 207

COMPLETIONS FOR PS INTERACTIVE
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_PS_INT
Description: The number of successfully established PS interactive RABs during relocation procedure.
procedure, and the RAB type is PS data interactive.
Operability class:
FOR PS BACKGROUND
Version: 1.0 NetAct name: RAB_RELOC_STP_ATT_PS_BGR
Description: The number of attempted PS background RAB setups during relocation procedure.
message from a core network, and the RAB type is PS data background.
208 DN99581291 Issue: 12G

Operability class:
COMPLETIONS FOR PS BACKGROUND
Version: 1.0 NetAct name: RAB_RELOC_ACC_COMP_PS_BGR
Description: The number of successfully established PS background RABs during relocation
procedure.
procedure, and the RAB type is PS data background.
Operability class:
Counter ID: M1001C704 Network element name: INTER SYSTEM LTE HHO FAIL
DUE TO CONFIG
Version: 7.1 NetAct name: INTER_SYS_LTE_HHO_FAIL_CONF
Issue: 12G DN99581291 209

Description: The number of incoming inter-system handovers rejected because the feature is disabled
in the cell with parameter WCEL-IncomingLTEISHO or RAN2176 feature is disabled. Also M1001C220
is updated along with this counter.
Updated: When the RNC sends RANAP: RELOCATION FAILURE to the core network after an
attempted incoming inter-system handover from LTE.
M1001C220: NUMBER OF UNSUCCESSFUL INTER SYS HHO ATTEMPTS
Operability class:
RAN2176: LTE PS Handover
RN5.0 EP1
2.8 RAB setup

RAB setup starts when the RNC receives a RANAP: RAB ASSIGNMENT REQUEST
message from the CN.
RAB setup is completed when the RNC has reserved all resources (RNC, BTS, air,
transport) needed for the RAB connection, and sends an RRC: RADIO BEARER SETUP
message to the UE.
RAB setup fails if some of the needed resources (RNC, BTS, air, transport) are not
available. When a RAB setup failure occurs, the RNC sends a RANAP: RAB
ASSIGNMENT RESPONSE message to the CN with an appropriate failure cause.
g Note: RNC does not reserve radio interface resources in RAB setup phase for NRT
RAB. The bit rates used in some of the RAB counter descriptions, refer to the Radio
Access Bearer bitrate requested by the core network from the RNC via RANAP
signalling. The RAB bit rates do not have any direct relation to the Radio Bearer bit rate
used in the air interface, but the Radio Bearer bit rate can be lower than the bit rate
negotiated in the Iu-interface between the core network and the RNC.
210 DN99581291 Issue: 12G

2.8.1 RAB setup attempts for CS voice calls

Counter ID: M1001C66 Network element name: RAB SETUP ATTEMPTS FOR CS
VOICE
Version: 5.3 NetAct name: RAB_STP_ATT_CS_VOICE
Description: The number of RAB setup attempts for CS voice calls.
Updated: When the RNC receives an RANAP: RAB ASSIGNMENT REQUEST message, the purpose
of which is to initate the establishment of a new CS voice RAB.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement name (Clause header): Attempted RAB establishments for CS domain
3GPP Measurement type: RAB.AttEstabCS.Conv
Exceptions to related standard: NetAct creates the needed counter by summing related counters
(Conversational class split according to source descriptor parameter(voice or unknown))
Counter ID: M1001C261 Network element name: RAB SETUP ATTEMPT CS AMR
MULTIMODE
Version: 8.1 NetAct name: RAB_SETUP_ATT_CS_AMR_MULTIM
Description: The number of RAB setup attempts for CS AMR Multimode calls. Also M1001C66 is
updated along with this counter.
Updated: When the RAB setup for a CS AMR Multimode call starts.
M1001C66: RAB SETUP ATTEMPTS FOR CS VOICE
Issue: 12G DN99581291 211

Operability class:
Counter ID: M1001C599 Network element name: RAB SETUP ATTEMPT CS VOICE
WPS
Version: 2.1 NetAct name: RAB_STP_ATT_CS_VOICE_WPS
Description: The number of RAB setup attempts for CS voice calls using Wireless Priority Service. Also
M1001C66 RAB SETUP ATTEMPTS FOR CS VOICE is updated along with this counter.
Updated: When the RNC receives an RANAP: RAB ASSIGNMENT REQUEST message with
parameters requesting to establish CS Voice RAB for Wireless Priority Service.
M1001C66: RAB SETUP ATTEMPTS FOR CS VOICE
Operability class:
RAN 1180: Wireless Priority Service
Used from release: RN2.2ED Definition updated in release:
2.8.2 RAB setup attempts for CS data calls

DATA CONV
212 DN99581291 Issue: 12G

Version: 5.3 NetAct name: RAB_STP_ATT_CS_CONV
Description: The number of RAB setup attempts for CS data conversational calls.
of which is to initate the establishment of a new CS data conversational RAB.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RAB.AttEstabCS.Conv
Exceptions to related standard: NetAct creates the needed counter by summing related counters
(Conversational class split according to source descriptor parameter(voice or unknown))
DATA STREAM
Version: 5.3 NetAct name: RAB_STP_ATT_CS_STREA
Description: The number of RAB setup attempts for CS data streaming calls.
of which is to initate the establishment of a new CS data streaming RAB.
Operability class:
3GPP 32.403, 5.9.0
Issue: 12G DN99581291 213

3GPP 32.403, 6.9.0
3GPP Measurement type: RAB.AttEstabCS.Strm
Counter ID: M1001C263 Network element name: RAB SETUP ATTEMPT CS
CONVERSATIONAL 64
Version: 4.1 NetAct name: RAB_SETUP_ATT_CS_CONV_64
Description: Number of RAB setup attempts for CS Conversational 64 kbps.
Updated: When the RAB setup attempt for a CS Conversational 64 kbps starts.
Operability class:
STREAMING 14.4
Version: 4.1 NetAct name: RAB_SETUP_ATT_CS_STREAM_14_4
Description: Number of RAB setup attempt for CS Streaming 14.4 kbps.
Updated: When the RAB setup attempt for a CS Streaming 14.4 kbps starts.
214 DN99581291 Issue: 12G

Operability class:
STREAMING 57.6
Version: 4.1 NetAct name: RAB_SETUP_ATT_CS_STREA_57_6
Description: Number of RAB setup attempts for CS Streaming 57.6 kbps.
Updated: When the RAB setup attempt for a CS Streaming 57.6 kbps starts.
Operability class:
2.8.3 RAB setup attempts for PS calls

Counter ID: M1001C70 Network element name: RAB SETUP ATTEMPTS FOR PS
DATA STREAM
Version: 5.3 NetAct name: RAB_STP_ATT_PS_STREA
Issue: 12G DN99581291 215

Description: The number of RAB setup attempts for PS data streaming calls.
of which is to initate the establishment of a new PS data streaming RAB.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement name (Clause header): Attempted RAB establishments for PS domain
3GPP Measurement type: RAB.AttEstabPS.Strm
DATA INTERA
Version: 5.3 NetAct name: RAB_STP_ATT_PS_INTER
Description: The number of RAB setup attempts for PS data interactive calls.
of which is to initate the establishment of a new PS data interactive RAB.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
216 DN99581291 Issue: 12G

3GPP Measurement type: RAB.AttEstabPS.Intact
DATA BACKG
Version: 5.3 NetAct name: RAB_STP_ATT_PS_BACKG
Description: The number of RAB setup attempts for PS data background calls.
of which is to initate the establishment of a new PS data background RAB.
Operability class:
3GPP 32.403, 5.9.0
3GPP 32.403, 6.9.0
3GPP Measurement type: RAB.AttEstabPS.Bgrd
Counter ID: M1001C269 Network element name: RAB SETUP ATTEMPT PS
STREAMING 16/64 GUAR 16/64
Version: 4.1 NetAct name: RAB_SET_A_PS_S_16_64_G_16_64
Description: Number of RAB setup attempts for PS Streaming RAB with a maximum bitrate of 16 kbps
uplink/64 kbps downlink and guaranteed bitrate of 16 kbps uplink/64 kbps downlink.
Updated: When the RAB setup for a PS Streaming starts.
Issue: 12G DN99581291 217

Operability class:
Counter ID: M1001C271 Network element name: RAB SETUP ATTEMPT PS
STREAMING 16/64 GUAR 8/32
Version: 4.1 NetAct name: RAB_SET_A_PS_S_16_64_G_8_32
Description: Number of RAB setup attempts for PS Streaming RAB with a maximum bitrate of 16 kbps
uplink/64 kbps downlink and guaranteed bitrate of 8 kbps uplink/32 kbps downlink.
Updated: When the RAB setup for a PS Streaming starts.
Operability class:
Counter ID: M1001C273 Network element name: RAB SETUP ATTEMPT PS NRT
64/64
Version: 4.1 NetAct name: RAB_SETUP_ATT_PS_NRT_64_64
Description: Number of RAB setup attempts for PS NRT RAB with a bit rate of 64 kbps uplink/64 kbps
downlink.
218 DN99581291 Issue: 12G

Updated: When the RAB setup for a PS NRT RAB starts.
Operability class:
64/128
downlink.
Operability class:
Issue: 12G DN99581291 219

64/256
downlink.
Operability class:
64/384
downlink.
Updated: When the RAB setup for a PS NRT starts.
Operability class:
220 DN99581291 Issue: 12G

128/64
Description: The number of RAB setup attempts for PS NRT RAB with a bitrate of 128 kbps uplink/64
kbps downlink.
Updated: When the RAB setup attempt for the RAB type in question starts.
Operability class:
128/128
kbps downlink.
Issue: 12G DN99581291 221

Operability class:
128/384
kbps downlink.
Operability class:
384/384
kbps downlink.
222 DN99581291 Issue: 12G

Operability class:
384/64
kbps downlink.
Operability class:
128/256
Issue: 12G DN99581291 223

Description: Number of RAB setup attempts for PS NRT RAB with a bit rate of 128 kbps uplink/256
kbps downlink.
Updated: When the RAB setup for a PS NRT starts.
Operability class:
Used from release: RN2.2ED Definition updated in release:
Counter ID: M1001C659 Network element name: RAB SETUP ATTEMPTS FOR DL
MAX BIT RATE - CLASS 1
Version: 1.0 NetAct name: RAB_STP_ATT_BR_CLASS_1_DL
Description: The number of NRT RAB setup attempts for DL maximum bitrate value inside the Class 1
range.
Updated: When the RNC receives a RANAP:RAB ASSIGNMENT REQUEST message or a RANAP:
RELOCATION REQUEST message from a core network with NRT RAB (interactive/background)
downlink maximum bitrate inside the Class 1 range (BITRATE<= 384 kbps).
M1001C71: RAB SETUP ATTEMPTS FOR PS DATA INTERA
M1001C72: RAB SETUP ATTEMPTS FOR PS DATA BACKG
M1001C817: RAB RELOC SETUP ATTEMPTS FOR PS INTERACTIVE
M1001C826: RAB RELOC SETUP ATTEMPTS FOR PS BACKGROUND
Operability class:
224 DN99581291 Issue: 12G

RAN1509: RAB Bit Rate Counters
range.
downlink maximum bitrate inside the Class 2 range (384 kbps< BITRATE<= 1.8 Mbps).
Operability class:
Issue: 12G DN99581291 225

range.
downlink maximum bitrate inside the Class 3 range (1.8 Mbps <BITRATE<= 3.6 Mbps).
Operability class:
range.
downlink maximum bitrate inside the Class 4 range ( 3.6 Mbps <BITRATE<= 7.2 Mbps).
226 DN99581291 Issue: 12G

Operability class:
range.
downlink maximum bitrate inside the Class 5 range (7.2 Mbps <BITRATE<= 10 Mbps).
Operability class:
Issue: 12G DN99581291 227

range.
downlink maximum bitrate inside the Class 6 range (10 Mbps <BITRATE<= 14 Mbps).
Operability class:
range.
228 DN99581291 Issue: 12G

downlink maximum bitrate inside the Class 7 range (BITRATE> 14.4 Mbps).
Operability class:
Counter ID: M1001C666 Network element name: RAB SETUP ATTEMPTS FOR UL
Version: 1.0 NetAct name: RAB_STP_ATT_BR_CLASS_1_UL
Description: The number of NRT RAB setup attempts for UL maximum bitrate value inside the Class 1
range.
RELOCATION REQUEST message from a core network with NRT RAB (interactive/background) uplink
maximum bitrate inside the Class 1 range (BITRATE<= 128 kbps).
Issue: 12G DN99581291 229

Operability class:
Counter ID: M1001C667 Network element name: RAB SETUP ATTEMPTS FOR UL
Version: 1.0 NetAct name: RAB_STP_ATT_BR_CLASS_2_UL
Description: The number of NRT RAB

Sprache

Willkommen bei Scribd!

dic_RNC_counterRU50.pdf

Hochgeladen von

Dokumentinformationen

Datum des Uploads

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Beschreibung:

Copyright:

Verfügbare Formate

dic_RNC_counterRU50.pdf

Hochgeladen von

Beschreibung:

Copyright:

Verfügbare Formate

Verwandte Titel

Nokia Networks

WCDMA RAN, Rel. RU50 and

RNC Counters - RNW Part

f Important Notice on Product Safety

7.2 DCH counters (SRNC)............................................................... 971

17.4.6 RRC handover to UTRAN........................................................ 2039

19.2.7 HS-DSCH MAC-d flow setup................................................... 2292

20.2.5 RAB assignment request ........................................................ 2351

21.3.1 Relocation commit (Iur)............................................................ 2449

21.5.2 SRNS context request (by source RNC) (Iu)........................... 2542

29.1 Inter-system handover............................................................. 2637

Figure 38 RRC connection setup on HSPA (IP)............................................. 2680

1 Radio network measurements

1.1 Status of counters

1.2 Optional counters

M1001C621 RAB SETUP FAILURES DUE TO IUR RAN1126

M1001C622 RAB SETUP FAILURES DUE TO IUR RAN1126

M1001C623 RAB SETUP FAILURES DUE TO IUR RAN1126

M1001C624 RAB SETUP FAILURES DUE TO IUR RAN1126

M1001C625 RAB SETUP FAILURES DUE TO IU-CS RAN1126

M1001C626 RAB SETUP FAILURES DUE TO IU-CS RAN1126

M1001C627 RAB SETUP FAILURES DUE TO IU-CS RAN1126

M1001C659 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C660 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C661 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C662 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C663 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C664 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C665 RAB SETUP ATTEMPTS FOR DL MAX BIT RAN1509

M1001C666 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

M1001C667 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

M1001C668 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

M1001C669 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

M1001C670 RAB SETUP ATTEMPTS FOR UL MAX BIT RAN1509

M1002C553 NRT DCH SETUP REJECT FOR RAN1126

M1002C554 NRT DCH SETUP REJECT FOR RAN1126

M1002C555 NRT DCH SETUP REJECT FOR RAN1126

M1002C556 NRT DCH SETUP REJECT FOR RAN1126

M1002C557 NRT DCH RECONFIG REJECT FOR RAN1126

M1002C558 NRT DCH RECONFIG REJECT FOR RAN1126

M1002C559 NRT DCH RECONFIG REJECT FOR RAN1126

M1002C560 NRT DCH RECONFIG REJECT FOR RAN1126

M1002C626 NRT DCH SETUP REJECT FOR RAN1126

M1002C627 NRT DCH SETUP REJECT FOR RAN1126

M1002C628 NRT DCH RECONFIG REJECT FOR RAN1126

M1002C629 NRT DCH RECONFIG REJECT FOR RAN1126

M1004C165 NRT DCH SETUP FAIL DUE TO IUR RAN1126

M1004C168 SHO BRANCH SETUP FAIL DUE TO IUR RAN1126

M1004C169 TRANSFERRED DATA FOR NRT HSDPA RAN1101

M1004C170 TRANSFERRED DATA FOR RT HSDPA RAN1101

M1013C4 CPICH ECNO SHO SUM RAN1191

M1013C5 CPICH ECNO SHO DENOM RAN1191

M1013C6 CPICH RSCP SHO SUM RAN1191

M1013C7 CPICH RSCP SHO DENOM RAN1191

M1014C2 CPICH ECNO IFHO SUM RAN1245

M1014C3 CPICH ECNO IFHO DENOMINATOR RAN1245

M1014C4 CPICH RSCP IFHO SUM RAN1245

M1014C5 CPICH RSCP IFHO DENOMINATOR RAN1245