Wcdma17 Feature Descriptions and Instructions

Nokia Networks

WCDMA RAN, Rel. WCDMA 17, Operating Documentation, Pre-release, Issue 01 WCDMA 17 Feature Descriptions and Instructions DN09232117 Issue 01A DRAFT Approval Date 2016-05-10

WCDMA 17 Feature Descriptions and Instructions

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.

DRAFT VERSION

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

DN09232117

Issue: 01A DRAFT


Table of Contents This document has 131 pages

Summary of changes................................................................... 12

Issue: 01A DRAFT

1

Introduction to WCDMA 17 features............................................ 13

2 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.5 2.5.1 2.5.2 2.5.3 2.5.4 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.8 2.8.1

Radio resource management features.........................................14 RAN3228: CS Call Re-establishment over Iur............................. 14 RAN3228 benefits........................................................................ 14 RAN3228 functional description...................................................14 RAN3228 system impact..............................................................17 RAN3228 reference data............................................................. 17 RAN3079: Dedicated Priorities.................................................... 18 RAN3079 benefits........................................................................ 18 RAN3079 functional description...................................................19 RAN3079 system impact..............................................................20 RAN3079 reference data............................................................. 21 RAN3280: Dynamic Baseband for HS RACH.............................. 23 RAN3280 benefits........................................................................ 23 RAN3280 functional description...................................................23 RAN3280 system impact..............................................................24 RAN3280 reference data............................................................. 25 RAN3266: Enhanced Mass Event Handler.................................. 26 RAN3266 benefits........................................................................ 27 RAN3266 functional description...................................................27 RAN3266 system impact..............................................................28 RAN3266 reference data............................................................. 29 RAN3263: Enhanced Power Control ...........................................32 RAN3263 benefits........................................................................ 32 RAN3263 functional description...................................................32 RAN3263 system impact..............................................................34 RAN3263 reference data............................................................. 35 RAN3341: Guaranteed Voice Calls in High Load.........................36 RAN3341 benefits........................................................................ 36 RAN3341 functional description...................................................37 RAN3341 system impact..............................................................37 RAN3341 reference data............................................................. 37 RAN3110: HSPA Queuing and Resource Rotation with QoS...... 39 RAN3110 benefits........................................................................ 39 RAN3110 functional description................................................... 39 RAN3110 system impact.............................................................. 40 RAN3110 reference data..............................................................41 RAN3270: Interference Control in HetNet....................................44 RAN3270 benefits........................................................................ 44

DN09232117

3


4

2.8.2 2.8.3 2.8.4 2.9 2.9.1 2.9.2 2.9.3 2.9.4 2.10 2.10.1 2.10.2 2.10.3 2.10.4 2.11 2.11.1 2.11.2 2.11.3 2.11.4 2.12 2.12.1 2.12.2 2.12.3 2.12.4 2.13 2.13.1 2.13.2 2.13.3 2.13.4 2.14 2.14.1 2.14.2 2.14.3 2.14.4

RAN3270 functional description...................................................44 RAN3270 system impact..............................................................46 RAN3270 reference data............................................................. 47 RAN2825: MOCN Capacity Assurance .......................................49 RAN2825 benefits........................................................................ 49 RAN2825 functional description...................................................49 RAN2825 system impact..............................................................50 RAN2825 reference data............................................................. 51 RAN3269: Optimised HSDPA Scheduler..................................... 58 RAN3269 benefits........................................................................ 58 RAN3269 functional description...................................................58 RAN3269 system impact..............................................................58 RAN3269 reference data............................................................. 59 RAN3271: Optimized Neighbor Cell Processing..........................60 RAN3271 benefits........................................................................ 61 RAN3271 functional description...................................................61 RAN3271 system impact..............................................................64 RAN3271 reference data............................................................. 65 RAN3291: UE History for WCDMA-LTE Mobility..........................67 RAN3291 benefits........................................................................ 67 RAN3291 functional description...................................................68 RAN3291 system impact..............................................................70 RAN3291 reference data............................................................. 70 RAN3044: Uplink CoMP...............................................................72 RAN3044 benefits........................................................................ 72 RAN3044 functional description...................................................72 RAN3044 system impact..............................................................73 RAN3044 reference data............................................................. 74 RAN3274: Uplink Data Compression...........................................75 RAN3274 benefits........................................................................ 75 RAN3274 functional description...................................................75 RAN3274 system impact..............................................................76 RAN3274 reference data............................................................. 77

4 4.1 4.1.1 4.1.2 4.1.3 4.1.4

Transmission and transport features............................................79 RAN3279: IP based Iu-interfaces via satellite..............................79 RAN3279 Benefits........................................................................79 RAN3279 Functional description..................................................79 RAN3279 System impact............................................................. 80 RAN3279 Reference data............................................................ 81

5 5.1 5.1.1 5.1.2 5.1.3

Operability features...................................................................... 83 RAN3277: CM Parameter Streamlining ...................................... 83 RAN3277 benefits........................................................................ 83 RAN3277 functional description...................................................83 RAN3277 system impact..............................................................85

DN09232117

Issue: 01A DRAFT


5.1.4 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.4.1

5.5.1 5.5.2 5.5.3 5.5.4 5.6 5.6.1 5.6.2 5.6.3 5.6.4

RAN3277 reference data............................................................. 85 RAN3157: mcRNC System diagnostic report.............................. 86 RAN3157 Benefits........................................................................86 RAN3157 Functional description..................................................86 RAN3157 System impact............................................................. 87 RAN3157 Reference data............................................................ 88 RAN3157 Description of diagnostic items in the system diagnostic report ...........................................................................................89 RAN3058: Online management of Antenna Line Devices (RET)..... 94 RAN3058 benefits........................................................................ 94 RAN3058 functional description...................................................94 RAN3058 system impact..............................................................94 RAN3058 reference data............................................................. 95 RAN2780: Remote Self Test for FSMF........................................ 96 RAN2780 benefits........................................................................ 96 RAN2780 functional description...................................................96 RAN2780 system impact..............................................................97 RAN2780 reference data............................................................. 98 RAN3156: RNC Troubleshooting Data Management by NetAct...... 98 RAN3156 benefits........................................................................ 99 RAN3156 functional description...................................................99 RAN3156 system impact............................................................100 RAN3156 reference data........................................................... 101 RAN3396: WCDMA OMS Connectivity Change for Gen9 HW.. 102 RAN3396 benefits...................................................................... 102 RAN3396 functional description.................................................102 RAN3396 system impact............................................................103 RAN3396 reference data........................................................... 103

6 6.1

Performance monitoring features...............................................105 RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring ................................................................................. 105 RAN3248 benefits...................................................................... 105 RAN3248 functional description.................................................105 RAN3248 system impact............................................................108 RAN3248 reference data........................................................... 108 RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA.........110 RAN2777 benefits...................................................................... 110 RAN2777 functional description................................................. 110 RAN2777 system impact............................................................ 112 RAN2777 reference data............................................................112 RAN2861: UE Tracing Support in BTS.......................................114 RAN2861 benefits...................................................................... 114 RAN2861 functional description................................................. 114 RAN2861 system impact............................................................ 117

5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.5

6.1.1 6.1.2 6.1.3 6.1.4 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.3 6.3.1 6.3.2 6.3.3

Issue: 01A DRAFT

DN09232117

5


6

6.3.4

RAN2861 reference data............................................................118

7 7.1 7.1.1 7.1.2 7.1.3 7.1.4

RNC solution features................................................................ 120 RAN3298: Support Max 32 PS Core Elements in RNC............. 120 RAN3298 benefits...................................................................... 120 RAN3298 functional description.................................................120 RAN3298 system impact............................................................121 RAN3298 reference data........................................................... 121

8 8.1 8.1.1 8.1.2 8.1.3 8.1.4 8.2 8.2.1 8.2.2 8.2.3 8.2.4 8.3 8.3.1 8.3.2 8.3.3 8.3.4

BTS solution features.................................................................123 RAN3259: 2 ms TTI Non-FDPCH Users Increase..................... 123 RAN3259 benefits...................................................................... 123 RAN3259 functional description.................................................123 RAN3259 system impact............................................................123 RAN3259 reference data........................................................... 124 RAN3067: Flexible HSDPA Carriers Allocation .........................125 RAN3067 benefits...................................................................... 125 RAN3067 functional description.................................................125 RAN3067 system impact............................................................126 RAN3067 reference data........................................................... 126 RAN3286: FSM-r2 Static Power Management ......................... 128 RAN3286 benefits...................................................................... 129 RAN3286 functional description.................................................129 RAN3286 system impact............................................................129 RAN3286 reference data........................................................... 129

DN09232117

Issue: 01A DRAFT


List of Figures

Issue: 01A DRAFT

Figure 1

Signaling of the CS Call Re-establishment for Anchoring.................. 14

Figure 2

Signaling of the CS Call Re-establishment with SRNS Relocation.... 16

Figure 3

Enhanced RTWP overload handling.................................................. 33

Figure 4

Interference between large and small cells: case 1............................45

Figure 5

Interference between large and small cells: case 2............................46

Figure 6

Small cell – macro cell network.......................................................... 62

Figure 7

Chained neighbors in the macro cell – small cell network..................63

Figure 8

Scrambling codes in chained neighbors cells.....................................64

Figure 9

RNC decision logic about handover or redirection to LTE.................. 69

Figure 10

RAN3044 process.............................................................................. 73

Figure 11

Architecture of Uplink Data Compression...........................................76

Figure 12

IP based Iu-interfaces via satellite links..............................................80

Figure 13

mcRNC System Diagnostic Report Overview.................................... 87

Figure 14

mcRNC System Diagnostic Report.................................................... 87

Figure 15

RAN2780 functional description......................................................... 97

Figure 16

Overview of the RAN3156 RNC Troubleshooting Data Management by NetAct feature................................................................................99

Figure 17

RAN3248 reporting mechanism....................................................... 106

Figure 18

MOCN NEs topology........................................................................ 110

Figure 19

IMSI-based call monitoring feature architecture............................... 115

DN09232117

7


List of Tables

8

Table 1

RAN3228 hardware and software requirements................................ 17

Table 2

Existing counters related to RAN3228................................................18

Table 3

New parameters introduced by RAN3228.......................................... 18

Table 4

Parameters modified by RAN3228..................................................... 18

Table 5

RAN3228 Sales information............................................................... 18

Table 6

WSP managed object for the RAN3079 feature.................................19

Table 7

WDP managed object for the RAN3079 feature.................................20

Table 8


Table 9

New counters introduced by 3079...................................................... 21

Table 10


Table 11


Table 12


Table 13


Table 14

Exising BTS faults related to RAN3280..............................................25

Table 15

New counters introduced by RAN3280.............................................. 26

Table 16

Counters modified by RAN3280......................................................... 26

Table 17


Table 18

RAN3280 sales information................................................................26

Table 19


Table 20


Table 21


Table 22


Table 23


Table 24

New PRFILE parameters introduced by RAN3266............................ 31

Table 25


Table 26


Table 27

Alarms modified by RAN3263............................................................ 35

Table 28

Existing key performance indicators related to RAN3263.................. 35

Table 29


Table 30


Table 31


Table 32


Table 33


Table 34


Table 35


Table 36


Table 37

RAN3110 hardware and software requirements.................................41

Table 38

New counters introduced by RAN3110...............................................42

DN09232117

Issue: 01A DRAFT


Issue: 01A DRAFT

Table 39

Existing counters related to RAN3110................................................ 42

Table 40

Existing key performance indicators related to RAN3110.................. 43

Table 41


Table 42


Table 43

PRFILE parameters related to RAN3110........................................... 44

Table 44

RAN3110 sales information................................................................ 44

Table 45


Table 46


Table 47


Table 48


Table 49


Table 50


Table 51

Existing alarms related to RAN2825...................................................51

Table 52


Table 53


Table 54


Table 55


Table 56

Parameters related to RAN2825........................................................ 55

Table 57


Table 58


Table 59


Table 60


Table 61

Existing alarms related to RAN3271...................................................65

Table 62


Table 63


Table 64


Table 65


Table 66


Table 67


Table 68


Table 69


Table 70


Table 71


Table 72


Table 73


Table 74


Table 75


Table 76


Table 77


Table 78


DN09232117

9


10

Table 79


Table 80


Table 81


Table 82

RAN3279 Software requirements.......................................................81

Table 83

RAN3279 New parameter.................................................................. 81

Table 84

RAN3279 Modified parameter............................................................ 82

Table 85


Table 86


Table 87


Table 88

RAN3157: mcRNC System Diagnostic Report hardware and software requirements.......................................................................................88

Table 89

New SCLI command introduced by RAN3157................................... 88

Table 90

New SCLI command introduced by RAN3157................................... 88

Table 91


Table 92

RAN3157 description of software diagnostic group............................89

Table 93

RAN3157 description of hardware diagnostic group.......................... 89

Table 94

RAN3157 description of resource diagnostic report group.................90

Table 95

RAN3157 description of alarm diagnostic report group......................92

Table 96

RAN3157 decription of signaling diagnostic report group.................. 92

Table 97

RAN3157 decription of startup diagnostic report group......................94

Table 98

RAN3058: Online management of Antenna Line Devices (RET) hardware and software requirements................................................. 95

Table 99

Parameters modified by RAN3058: Online management of Antenna Line Devices (RET)............................................................................ 96

Table 100

RAN3058: Online management of Antenna Line Devices (RET) sales information..........................................................................................96

Table 101


Table 102


Table 103

The RAN3156: RNC Troubleshooting Data Management by NetAct hardware and software requirements............................................... 101

Table 104

Existing alarms related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature........................................................101

Table 105

RAN3156: RNC Troubleshooting Data Management by NetAct sales information........................................................................................102

Table 106

RAN3396: WCDMA OMS Connectivity Change for Gen9 HW hardware and software requirements............................................... 103

Table 107

RAN3396: WCDMA OMS Connectivity Change for Gen9 HW sales information........................................................................................104

Table 108

RAN3248 Software requirements.....................................................108

Table 109

Existing alarms related to RAN3248.................................................109

Table 110

New counters introduced by RAN3248............................................ 109

Table 111

New parameters related to RAN3248...............................................109

Table 112

RAN3248 Sales information............................................................. 110

DN09232117

Issue: 01A DRAFT


Issue: 01A DRAFT

Table 113

Software requirements......................................................................112

Table 114

New counters introduced by RAN2777.............................................112

Table 115

RAN2777 Sales information............................................................. 114

Table 116

NE and tool tracing capacities.......................................................... 117

Table 117

Software requirements......................................................................118

Table 118

External monitoring tool.................................................................... 118

Table 119

New BTS faults introduced by RAN2861.......................................... 119

Table 120

New parameter introduced by RAN2861.......................................... 119

Table 121

Sales information.............................................................................. 119

Table 122

RAN3298 hardware and software requirements.............................. 121

Table 123

RAN3298 modified parameters........................................................ 122

Table 124

RAN3298 sales information..............................................................122

Table 125

RAN3259: 2 ms TTI Non-FDPCH Users Increase hardware and software requirements...................................................................... 124

Table 126

Existing counters related to RAN3259..............................................124

Table 127

Existing key performance indicators related to RAN3259................ 124

Table 128

New parameters introduced by RAN3259........................................ 125

Table 129


Table 130


Table 131

Existing alarms related to RAN3067.................................................127

Table 132

New BTS faults introduced by RAN3067..........................................127

Table 133

Existing counters related to RAN3067..............................................127

Table 134


Table 135


Table 136


Table 137

Existing faults and alarms related to RAN3286 ............................... 130

Table 138


Table 139


DN09232117

11

Summary of changes


Summary of changes Changes between issues 01 DRAFT (2016-03-11, WCDMA 17) and 01A DRAFT (2016-05-10, WCDMA 17) New feature descriptions: •

Transmission and transport features features –

DRAFT VERSION

•

12

Operability features – – – – –

•

RAN3279: IP Based Iu-Interfaces via Satellite

RAN3157: mcRNC System Diagnostic Report RAN3058: Online Management of Antenna Line Devices RAN2780: Remote Self Test for FSMF RAN3186: RNC Troubleshooting Data Management by NetAct RAN3396: WCDMA OMS Connectivity Change for Gen9 HW

Performance monitoring features – –

RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA RAN2861: UE Tracing Support in BTS

Removed feature descriptions: RAN2319: Remote RNC SW Upgrade via NetAct

DN09232117

Issue: 01A DRAFT


Introduction to WCDMA 17 features

1 Introduction to WCDMA 17 features This document provides feature descriptions and instructions for the WCDMA 17 release. In this delivery only feature descriptions are provided. Note that the subchapter Interdependencies between features lists only dependencies among Nokia RAN WCDMA features.

DRAFT VERSION

If the feature has no specific hardware requirements, it means that only WCDMA System Module must be used.

g

Issue: 01A DRAFT

Note: This document does not contain whole set of WCDMA 17 features. The full set of WCDMA 17 features will be provided in further deliveries.

DN09232117

13

Radio resource management features


2 Radio resource management features 2.1 RAN3228: CS Call Re-establishment over Iur Benefits, functionality, system impact, reference data of the feature.

DRAFT VERSION

The RAN3228: CS Call Re-establishment over Iur feature enables a re-establishment of a lost AMR call over Iur in anchoring, or with serving radio network subsystem (SRNS) relocation.

2.1.1 RAN3228 benefits The RAN3228: CS Call Re-establishment over Iur feature: • • •

improves call drops performance over Iurs. enables operators to select a CS call re-establishment over Iur either with SRNS relocation or for anchoring. works in multi-vendor environment.

2.1.2 RAN3228 functional description When a UE loses radio connection during CS voice call, it starts to search for a suitable cell to camp. If the UE regains the radio connection within a pre-defined time, it sends the RRC:CELL UPDATE to RNC, which in this case is the drifting RNC (DRNC). DRNC forwards the Cell Update to the serving RNC (SRNC). If possible, the SRNC starts to allocate the radio resources of the CS voice call over the Iur in DRNC, and reestablishes the CS voice call to the UE. CS Call Re-establishment for Anchoring The circuit-switched call (CS call) re-establishment over Iur for anchoring is suitable for the Iur interface between Nokia SRNC and other Vendor's DRNC. It can also be activated in the Nokia RNC - Nokia RNC Iur interface. In anchoring the SRNC controls the call re-establishment, and remains in control of the call after re-establishment. The SRNC allocates the radio resources over Iur in the DRNC and re-establishes the call to the UE. When the UE with a CS voice call loses radio connection, RNC receives the radio link (RL) Failure message from all the BTSs to which UE has a radio link. Upon receiving RL Failure, the SRNC starts the RRC_ConnRe-estab_T314 timer. If the UE provides Cell Update message before RRC_ConnRe-estab_T314 and UE timer T314/T315 have expired, RNC starts the RRC connection re-establishment. During the RRC connection re-establishment procedure the CS voice call connection moves back to the Cell_DCH state with a Cell Update Confirm message. The interrupted service continues when the radio link synchronization is restored. Figure 1

14

Signaling of the CS Call Re-establishment for Anchoring

DN09232117

Issue: 01A DRAFT


SRNC


DRNC

CN

BTS

UE

AMRon-going RL Failure CELL UPDATE RNSAP:UPLINKSIGNALLING TRANSFERINDICATION

DRAFT VERSION

RemoveRL'sifexistin SRNCorinDRNC EstablishRL overIUR for AMR RNSAP:RL SETUP REQUEST RADIOLINKSETUP RADIOLINKSETUP RESPONSE RNSAP:RL SETUP RESPONSE

Re-establishthe AMR toUE RNSAP:DOWNLINKSIGNALLING TRANSFERREQUEST CELL UPDATECONFIRM NBAP:RADIOLINKRESTOREINDICATION RNSAP:RADIOLINKRESTOREINDICATION RADIOBEARERRECONFCOMPLETE

CS Call Re-establishment with SRNS Relocation The CS Call re-establishment over Iur with SRNS relocation works only for the NokiaNokia Iur interface and it is UE sensitive.

g

Note: The CS Call Re-establishment with SRNS Relocation is used by default only with Rel-9 and newer UEs. For Rel-8 and older UEs the CS call re-establishment over Iur is done in anchoring. SRNC initiates SRNS relocation procedure and Target RNC sends Cell Update Confirm including the new U-RNTI and parameters for call re-establishment. When SRNC receives the cell update from target RNC, it checks whether the following requirements are met: • • • •

Issue: 01A DRAFT

A CS call is already established. T314 > 0 All network nodes support SRNS relocation. The RAN3228: CS Call Re-establishment over Iur feature is activated and the CS Call re-establishment over Iur with SRNS relocation is enabled.

DN09232117

15



If all of the above requirements are met, SRNC initiates SRNS relocation procedure by sending Relocation Required to the involved CN nodes.

DRAFT VERSION

When the Target RNC receives a Relocation Request from CS CN, it checks if the RAN3228: CS Call Re-establishment over Iur feature is enabled with the CS Call reestablishment over Iur with SRNS relocation. If the functionality is enabled, the target RNC accepts the relocation and continues with resource allocation procedure and initiates Radio Link Setup towards BTS. The Target RNC sends Cell Update Confirm to the UE with new U-RNTI and parameters for call re-establishment. When the UE sends a successful response for the Cell Update Confirm message, SRNS relocation is completed and Target RNC becomes a new SRNC. At this point it sends Relocation Complete to CN. The resources in the old SRNC are released, and the CS call continues. Figure 2

Signaling of the CS Call Re-establishment with SRNS Relocation

SRNC

DRNC

CN

BTS

UE

AMRon-going RL Failure CELL UPDATE RNSAP:UL SIGN TRFINDICATIONS

RemoveRL RELOCATIONREQUIRED RELOCATIONREQUEST RADIOLINKSETUP RADIOLINKSETUP RESPONSE RELOCATIONREQUEST ACK RELOCATIONCOMMAND RELOCATIONCOMMIT CELL UPDATECONFIRM RADIOBEARERRECONFCOMPLETE RELOCATIONDETECT RELOCATIONCOMPLETE UTRANMOBILITY INFORMATION UTRANMOBILITY INFORMATIONCOMPLETE IURELEASECOMMAND IURELEASECOMPLETE

Error Handling If SRNC notices an error during the CS call re-establishment over Iur, the SRNC initiates the RRC CONNECTION RELEASE procedure for the connection.

16

DN09232117

Issue: 01A DRAFT



If L3 in SRNC receives an error message or a timer expiry indicates that the CS call reestablishment over Iur does not succeed (either with anchoring or with SRNS relocation), the L3 interrupts the procedure and initiates the RRC CONNECTION RELEASE procedure for the connection.

2.1.3 RAN3228 system impact The RAN3228: CS Call Re-establishment over Iur impact on features, interfaces, network management tools, and system performance and capacity.

DRAFT VERSION

Interdependencies between features There are no interdependencies between the RAN3228: CS Call Re-establishment over Iur feature and any other feature. Impact on interfaces The RAN3228: CS Call Re-establishment over Iur feature has no impact on interfaces. Impact on network management tools The RAN3228: CS Call Re-establishment over Iur feature has no impact on network management tools. Impact on system performance and capacity The RAN3228: CS Call Re-establishment over Iur feature has no impact on system performance or capacity.

2.1.4 RAN3228 reference data RAN3228: CS Call Re-establishment over Iur requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 1

RAN3228 hardware and software requirements

RAS

IPA-RNC

mcRNC

Flexi Multiradio BTS

Flexi Multiradio 10 BTS

Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17

Support not required



OMS

NetAct

MSC

SGSN

MGW

UE


NetAct 17





This feature requires no new or additional hardware. Alarms There are no alarms related to the RAN3228: CS Call Re-establishment over Iur feature. Commands There are no commands related to the RAN3228: CS Call Re-establishment over Iur feature. Measurements and counters

Issue: 01A DRAFT

DN09232117

17


Table 2


Existing counters related to RAN3228

Counter ID

Counter name

Measurement RRC signalling (RNC)

M1006C314

RRC RE-ESTABLISH SUCCESS RT OVER IUR

M1006C315

RRC RE-ESTABLISH FAIL RT OVER IUR RRC signalling (RNC)

Key performance indicators There are no key performance indicators related to the RAN3228: CS Call Reestablishment over Iur feature.

DRAFT VERSION

Parameters Table 3

New parameters introduced by RAN3228 Full name

Abbreviated name

CS Call ReCSCallReEstOvrIurEn establishment over Iur abled Enabled

Table 4

Managed object

Parent structure

IUR

Parameters modified by RAN3228 Full name

Abbreviated name

RNC Options

RncOptions

Managed object

Parent structure

RNC

Sales information Table 5

RAN3228 Sales information

Product structure class

License control

Application software (ASW)

RNC License Key

Activated by default No

2.2 RAN3079: Dedicated Priorities Benefits, functionality, system impact, reference data of the feature. The RAN3079: Dedicated Priorities feature enables a flexible use of the dedicated (subscriber-specific) priorities in the absolute priority-based criteria for inter-frequency and inter-RAT (GSM and LTE) cell reselection. With the dedicated priorities the operator is able to define subscriber group-specific camping strategies and can prevent the movement to LTE for those subscribers who do not have LTE subscription.

2.2.1 RAN3079 benefits The RAN3079: Dedicated Priorities feature provides the following benefits: • • •

18

Allowing defining subscriber group-specific camping strategies. Enabling giving priorities to a UE for selecting Radio Access Technology (RAT): LTE, WCDMA or GSM, and the frequency within each RAT. Enabling a different handling of different roaming user groups.

DN09232117

Issue: 01A DRAFT


• •


Preventing a UE from camping to LTE for LTE devices without LTE subscription. Allowing network-sharing operators to use individual priority tables.

2.2.2 RAN3079 functional description

DRAFT VERSION

The RAN3079: Dedicated Priorities feature enables inter-frequency and inter-RAT (GSM, LTE) cell reselection based on the dedicated (subscriber-specific) WCDMA/LTE/GSM frequency priorities. When the RAN3079 feature is activated, the RNC sends the dedicated WCDMA/LTE/GSM frequency priorities to the specified Rel-8 or newer UEs in the RRC: UTRAN MOBILITY INFORMATION message after RAB setup and during the SRNC relocation procedure. The UEs in question use the dedicated priorities for cell reselection in the states: Idle, Cell_PCH, and URA_PCH instead of the absolute priorities broadcasted in the System Information Block type 19 (SIB19) message. The dedicated priorities are valid until the UE leaves the radio network or the dedicated priorities are resent. The cell reselection strategy (subscriber-specific, or user groupspecific) is controlled by the PLMN ID of the subscriber and/or the Subscriber Profile ID (SPID) for RAT/Frequency priority IE sent from the CN to the RNC in the RANAP: COMMON ID, DIRECT TRANSFER or the RELOCATION REQUEST message. The operator is able to define the WCDMA/LTE/GSM frequency priorities dedicated to a certain subscriber's PLMN ID, to a certain SPID value or to a certain PLMN ID and SPID combination. It is also possible to define the WCDMA/LTE/GSM frequency priorities that are dedicated to all roaming subscribers. In case of RAN sharing, each operator can define the dedicated priorities independently. In the Cell_DCH state, the RNC does not hand over or redirect a UE to the LTE carrier frequency that is not included in the dedicated priority information sent to the UE. The dedicated priority information does not affect inter-frequency and GSM handover control in the Cell_DCH state. The RAN3079 feature introduces the following managed objects: •

•

WSP (WCDMA Subscriber Profile): It contains the attributes which are used to generate the Subscriber Profile ID (SPID) mapping table in the RNC. WDP (WCDMA Dedicated Priority): It contains the priority and frequency information of the different radio access technologies for a specified SPID.

Table 6

WSP managed object for the RAN3079 feature WCDMA Subscriber Profiles (WSP), max 48 instances

IUO ID (separate tables can be defined for different RAN sharing operators) 1,...,255

Issue: 01A DRAFT

SPID, matched to the Subscriber Profile ID for RAT/Frequency priority IE, if sent from CN

1,...,255, not defined

DN09232117

PLMN, matched to the home PLMN of the subscriber MCC+MNC, not defined

19


Table 7


WDP managed object for the RAN3079 feature WCDMA Dedicated Priorities (WDP) for this WSP

DRAFT VERSION

WDP ID

Priority level for this WDP ID

RAT for this WDP ID

List of frequenicies applied for this WDP ID

1

0,...,7

LTE, WCDMA, GSM

values according to RAT, max 32 frequencies

2

0,...,7

LTE, WCDMA, GSM


...

...

...

...

max 8

0,...,7

LTE, WCDMA, GSM


2.2.3 RAN3079 system impact RAN3079: Dedicated Priorities impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The RAN3079: Dedicated Priorities feature is impacted by the following features: • • • • • •

RAN2067: LTE Interworking RAN2881: WCDMA and GSM layer priorities RAN3069: RSRQ-based LTE Reselection RAN2717: Smart LTE layering RAN2264: Smart LTE handover RAN2980: Measured based LTE layering

With the RAN2067 and the RAN3069 features, the absolute priority-based criteria is enabled for inter-RAT cell reselection to LTE. With the RAN2881 feature, the absolute priority-based criteria are enabled for interfrequency cell reselection and for inter-RAT cell reselection to GSM. The RNC broadcasts the absolute camping priorities to all UEs via system information (SIB19). If the dedicated priorities are sent to a UE, the dedicated priorities overwrite the broadcasted priorities.

g

Note: Even if the absolute priorities are not used in the RNC/Cell, the RNC sends dedicated priorities for a UE in Cell_DCH or Cell_FACH state as the RNC does not detect what kind of services the RNC/Cell offers when the UE needs the dedicated priorities in IDLE, Cell_PCH, and Cell_FACH states. If such dedicated priorities which do not include some LTE frequencies are sent to a UE, then handovers or re-directions to LTE are not done for this UE to those frequencies by the RAN2717: Smart LTE Layering, the RAN2264: Smart LTE Handover, and the RAN2980: Measurement Based LTE Layering feature.

20

DN09232117

Issue: 01A DRAFT



The RAN3079 feature does not change the existing WCDMA or GSM rules for handovers, redirections, layering within WCDMA and layering within GSM. Impact on interfaces The RAN3079: Dedicated Priorities feature has no impact on interfaces. Impact on network management tools The RAN3079: Dedicated Priorities feature has no impact on network management tools.

DRAFT VERSION

Impact on system performance and capacity The RAN3079: Dedicated Priorities feature has no impact on system performance or capacity.

2.2.4 RAN3079 reference data RAN3079: Dedicated Priorities requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 8


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17

NetAct 17


Support required 1)


3GPP Rel-8

1) The CN support is needed only for the SPID part. This information will be provided in

further deliveries. This feature does not require any new or additional HW. Alarms There are no alarms related to the RAN3079: Dedicated Priorities feature. Commands There are no commands related to the RAN3079: Dedicated Priorities feature. Measurements and counters Table 9 Counter ID

M1006C331

New counters introduced by 3079 Counter name

DEDICATED PRIORITY INFORMATION SENT TO UE

Measurement RRC signalling

Key performance indicators

Issue: 01A DRAFT

DN09232117

21



There are no key performance indicators related to the RAN3079: Dedicated Priorities feature. Parameters Table 10

New parameters introduced by RAN3079

DRAFT VERSION

Full name

g

22

Abbreviated name

Managed object

Parent structure

Dedicated Priority Enabled

DedicatedPriorityEn abled

RNFC

-

WSP Identifier

WSPId

WSP

-

WCDMA Subscriber Profile related Iu Operator

WSProfileRelatedIUO

WSP

-

Subscriber Profile ID

SPID

WSP

-

WCDMA Subscriber Profile E-UTRA detection

WSProfileEUTRADetec tion

WSP

-

WSP Change Origin

WSPChangeOrigin

WSP

-

Subscriber Profile MCC SubscriberProfileMC C

WSP

Subscriber Profile PLMN Identifier (SubscriberProfileP LMNId)

Subscriber Profile MNC SubscriberProfileMN C

WSP


Subscriber Profile MNC SubscriberProfileMN Length Clength

WSP


WDP Change Origin

WDPChangeOrigin

WDP

-

WDP Identifier

WDPId

WDP

-

Dedicated Priority Level

DedicatedPriorityLe vel

WDP

-

Radio Access Technology

RadioAccessTechnolo gy

WDP

-

Absolute Radio Frequency Channel Number

ARFCN

WDP

-

Note: If any of the LTE frequencies within one WDP instance (WDP-ARFCN) is defined as neighbouring E-UTRA frequency in LTE adjacencies (ADJL-AdjLEARFCN) under a WCEL instance, and both the AdjLThreshigh2 and the AdjLThreslow2 (HOPL object) parameters are set to value in range between 0 to 31 dB in some of the LTE adjacencies under the WCEL instance, the operator must ensure that both the AdjLThreshigh2 and the AdjLThreslow2 parameters are set to value in range between 0 to 31 dB in all LTE adjacencies under the WCEL instance in question.

DN09232117

Issue: 01A DRAFT


g

Note: WSP is a new managed object and contains the attributes which are used to generate the Subscriber Profile ID (SPID) mapping table in the RNC.

g

Note: WDP is a new managed object contains the priority and the frequency information for different radio access technologies for the specified SPID. Table 11


DRAFT VERSION


Abbreviated name

Managed object

Parent structure

RNC Options

RNCOptions

IADA

-

Threshold high 2 for LTE cell reselection

AdjLThreshigh2

HOPL

-

Threshold low 2 for LTE cell reselection

AdjLThreslow2

HOPL

-

E-UTRA Absolute Radio Frequency Channel Number

AdjLEARFCN

ADJL

-




License control


RNC License Key


2.3 RAN3280: Dynamic Baseband for HS RACH Benefits, functionality, system impact, reference data of the feature. The RAN3280: Dynamic Baseband for HS RACH feature introduces dynamic allocation of baseband resources in BTS for active high speed random access channel (HS-RACH) users based on the traffic in the local cell group (LCG).

2.3.1 RAN3280 benefits The RAN3280: Dynamic Baseband for HS RACH feature provides the following benefits: • • •

It prevents the operator from under- or over-allocation of BTS baseband resources for HS-RACH users. It provides optimal HS-RACH baseband resources usage in BTS. It provides dynamic change of required baseband resources for HS-RACH purpose and flexible range parameters settings without BTS restart.

2.3.2 RAN3280 functional description The RAN3280: Dynamic Baseband for HS RACH feature introduces dynamic allocation of BTS baseband resources for active HS-RACH users. RAN3280 feature includes the following enhancements:

Issue: 01A DRAFT

DN09232117

23


DRAFT VERSION

•


Configuration of minimum and maximum baseband resources for HS-RACH users per LCG RAN3280 feature enables to set the minimum and maximum value of HSUPA Resource Steps per LCG for HS-RACH using minNumOfHsRachResourceStepsRes and maxNumOfHsRachResourceStepsRes commissioning parameters. The system allocates needed HS-RACH resources between commissioned values based on HSRACH traffic. The number of minimum and maximum HSUPA Resource Steps for HS-RACH users can be changed at runtime without BTS restart. Baseband resources for the minNumOfHsRachResourceStepsRes value is guaranteed for HS-RACH users and based on the number of active HS-RACH users additional baseband resources are allocated until maxNumOfHsRachResourceStepsRes value is reached.

g

Note: If minNumOfHsRachResourceStepsRes parameter value is equal to maxNumOfHsRachResourceStepsRes parameter value then HS-RACH Resource Steps are reserved statically. •

Additional HSUPA Resource Steps This functionality is triggered if: – –

The number of allocated HSUPA Resource Steps is less than the configured amount of Common E-DCH resources. The number of preambles rejected due to lack of baseband resources for HSRACH is greater than the threshold value.

Additional HSUPA Resource Steps are assigned if the following conditions are fulfilled: – – –

g

The number of allocated HSUPA Resource Steps is equal to or greater than minNumOfHsRachResourceStepsRes value. The maximum capacity of HSUPA scheduler is not reached. The maximum number of HSUPA Resource Steps has not reached the maxNumOfHsRachResourceStepsRes value. Note: The number of HSUPA Resource Steps (RS) increases according to the following rule: 1 RS = 10 users.

•

Release of HSUPA Resource Steps This functionality is triggered if the allocated HSUPA Resource Step capacity is greater than the average amount of active common E-DCH resources based on runtime resource usage.

2.3.3 RAN3280 system impact RAN3280: Dynamic Baseband for HS RACH impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The following feature must be activated before activating the RAN3280: Dynamic Baseband for HS RACH feature: •

24

RAN1913: High Speed Cell_FACH

DN09232117

Issue: 01A DRAFT



The RAN3280: Dynamic Baseband for HS RACH feature is impacted by the following feature: •

RAN2518: High Speed Cell_FACH Enhanced feature increases the range for dynamic HS-RACH allocation.

Impact on interfaces The RAN3280: Dynamic Baseband for HS RACH feature has no impact on interfaces. Impact on network management tools

DRAFT VERSION

The RAN3280: Dynamic Baseband for HS RACH feature has no impact on network management tools. Impact on system performance and capacity The RAN3280: Dynamic Baseband for HS RACH feature has no impact on system performance and capacity.

2.3.4 RAN3280 reference data RAN3280: Dynamic Baseband for HS RACH requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 13


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17

WBTS17

WBTS17


OMS

NetAct

MSC

SGSN

MGW

UE







Alarms There are no alarms related to the RAN3280: Dynamic Baseband for HS RACH feature. BTS faults and reported alarms Table 14

Exising BTS faults related to RAN3280

Fault ID

Fault name

Reported alarms Alarm ID

162

Minimum number of HSRACH resource steps not allocated

7652

Alarm name

BASE STATION NOTIFICATION

Commands There are no commands related to the RAN3280: Dynamic Baseband for HS RACH feature.

Issue: 01A DRAFT

DN09232117

25



Measurements and counters Table 15

New counters introduced by RAN3280

DRAFT VERSION

Counter ID

Counter name

Measurement

M5006C76

AVERAGE HS-RACH SUBUNITS RESERVATION IN LCG

WBTS R99 HW Resource (WBTS)

M5006C77

MAXIMUM HS-RACH SUBUNITS RESERVATION IN LCG


M5006C78

CONFIGURED HS-RACH SUBUNITS IN LCG


Table 16

Counters modified by RAN3280

Counter ID

Counter name

Measurement

M5006C75

AVAILABLE NUMBER OF HIGH SPEED CELL_FACH USERS WITH HS RACH


M5008C50

CONFIGURED HS-FACH SUBUNITS IN BTS

WBTS level monitoring (WBTS)

M5012C6

CONFIGURED HS-FACH SUBUNITS IN FSM

FSM Level Monitoring (WBTS)

Key performance indicators There are no key performance indicators related to the RAN3280: Dynamic Baseband for HS RACH feature. Parameters Table 17


Abbreviated name

Managed object

Parent structure

Dynamic Baseband for High Speed RACH enabled

dynamicBasebandHsRa chEnabled

WBTS 17

-

Maximum number of HSUPA resource steps for HS-RACH users

maxNumOfHsRachResou rceStepsRes

WBTS 17

-

Minimum number of HSUPA resource steps for HS-RACH users

minNumOfHsRachResou rceStepsRes

WBTS 17

-


RAN3280 sales information

Product structure class Application software (ASW)

License control BTS LK


2.4 RAN3266: Enhanced Mass Event Handler Benefits, functionality, system impact, reference data of the feature.

26

DN09232117

Issue: 01A DRAFT



The RAN3266: Enhanced Mass Event Handler feature enhances the RAN2879: Mass Event Handler feature.

2.4.1 RAN3266 benefits The RAN3266: Enhanced Mass Event Handler feature provides the following benefits: • •

DRAFT VERSION

•

Improved cell capacity and user throughput Improved call success rate Efficient HSPA/HSDPA resource rotation upon high load conditions

2.4.2 RAN3266 functional description The RAN3266: Enhanced Mass Event Handler feature contains the following subfeatures: •

•

•

Issue: 01A DRAFT

Additional received total wideband power (RTWP) and HSUPA throughput inputs to trigger mass event handler (MEH) functions The RAN2879: Mass Event Handler feature detects the MEH load state of the cell from the number of the cell packet-switched (PS) queue items for non-real time dedicated traffic channel (NRT DCH/DCH) or high speed packet access (HSDPA/UL DCH) allocations. The RAN3266 feature introduces the cell RTWP and cell HSUPA throughput as new triggers for MEH with additional preventive and reactive load state handling. Preventive actions, including: dynamic or automatic adjustment of the HSUPA power offsets, initial signal-to-interference ratio (SIR) target configuration, high HSUPA block error ratio (BLER) target configuration, and HSUPA 2ms Transmission Time Interval (TTI) restriction, are automatically activated based on the RTWP input. This functionality optimizes the RTWP level and the upink (UL) performance of the cell. Reactive actions include the dynamic temporary maximum number of HSUPA users (EMEH DMHU) adjustment, which dynamically triggers the HSUPA limitation in the cell if the RTWP level increases too much or HSUPA user throughput decreases too low. HSUPA user limitation is then automatically tuned to a level which provides the optimum RTWP and HSUPA throughput during the high load conditions. Preventive actions are used in parallel with reactive actions. Load state triggers, apart from the fixed temporary maximum number of HSUPA users (MEH TMHU) introduced by the RAN2879: Mass Event Handler feature, are still available with the RAN3266 feature. The operator can configure the used EMEH states (preventive, reactive, and load) on cell basis. Limitation of UL NRT DCH bitrates A temporary uplink non-real time dedicated traffic channel (UL NRT DCH) maximum bit rate is determined based on the cell state. The temporary maximum bit rate is used during initial allocation and upgrade of the UL NRT DCH. This prevents further increase of UL noise in an already loaded cell. In case of diversity handover from an unloaded cell to the loaded cell during active state, the high UL NRT DCH bit rates are downgraded. Soft handover (SHO) prioritization over the HSUPA TTI reconfiguration If EMEH prohibits the HSUPA 2 ms TTI allocation in case of SHO branch setup or addition, the SHO branch setup or addition (active set update) is done first with the existing HSUPA 2 ms TTI allocation. HSUPA TTI reconfiguration from 2 ms to 10 ms

DN09232117

27


•


is started after active set update is completed. The same change is implemented generically to the HSUPA 2 ms TTI prevention function of the RAN2879: Mass Event Handler feature. Increased UE periodic measurement reporting interval UE periodic reporting of the common pilot channel (CPICH) Ec/N0 and CPICH received signal code power (RSCP) measurement increases the UL interference even if the UL data transfer is low or zero. This sub-feature increases the reporting interval of the UE periodic measurement from default 500 ms to 2 s when any cell of the active set is in EMEH state.

DRAFT VERSION

2.4.3 RAN3266 system impact RAN3266: Enhanced Mass Event Handler impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The RAN3266: Enhanced Mass Event Handler (EMEH) feature impacts the following feature: •

RAN2879: Mass Event Handler (MEH) RAN2879: Mass Event Handler feature is a pre-requisite for the RAN3266 Enhanced Mass Event Handler feature. However, the RAN3266 feature can be used in the cell also if any or every sub-feature of the RAN2879 feature is disabled. When both of the features are enabled in the same time, the sub-features of the RAN2879 feature have the following inter-operability with the RAN3266 feature: –

–

–

–

28

Increased traffic volume measurement (TVM) pending time Usage of the increased TVM pending time is triggered by the MEH load state because of the RAN2879 functionality. The RAN3266 feature introduces new triggers for the increased TVM pending time. The RAN3266 feature makes it possible to configure the EMEH cell states (EMEH preventive state, EMEH reactive state, and EMEH load state) where the increased TVM pending time function is used. Temporary maximum bit rate for UL DCH: Usage of the temporary maximum bit rate for UL DCH is triggered by the MEH load state because of the RAN2879 functionality. The RAN3266 feature introduces new triggers for the temporary maximum bit rate for UL DCH. The RAN3266 feature makes it possible to configure the EMEH cell states (EMEH preventive state, EMEH reactive state, and EMEH load state) where the temporary maximum bit rate for UL DCH function is used. Temporary maximum number of HSUPA users: Usage of the RAN2879 fixed temporary maximum number of HSUPA users (MEH TMHU) is disabled in the cell by the system (control plane) if usage of the RAN3266 dynamic HSUPA user limitation (EMEH DMHU) is enabled in the cell. Dynamic temporary maximum number of HSUPA users (EMEH DMHU) replaces the usage of the fixed MEH TMHU. If EMEH DMHU is not enabled in the cell, the RAN2879 fixed MEH TMHU is used in a regular way. Increased channel quality indicator (CQI) feedback cycle: Usage of the increased CQI feedback cycle is triggered if the number of HSDPA users in the cell exceeds a pre-defined threshold. This function works in a regular way irrespective of the RAN3266 feature.

DN09232117

Issue: 01A DRAFT


–

DRAFT VERSION

–


Load based E-DCH 2 ms TTI prevention: E-DCH 2 ms TTI limitation is triggered if the number of HSUPA users in the cell exceeds a pre-defined threshold. The RAN3266 feature introduces new triggers for the E-DCH 2 ms TTI limitation. The RAN3266 feature makes it possible to configure the EMEH cell states (EMEH preventive state, EMEH reactive state, and EMEH load state) where the E-DCH 2 ms TTI prevention function is used. Uplink (UL) load based admission control (AC) for HSPA+ features: UL load based AC for HSPA+ features is triggered if the load based AC exceeds a pre-defined threshold, or the MEH load state of the cell is active. The RAN3266 feature introduces new triggers for the UL load based AC for HSPA+ features function. The RAN3266 feature makes it possible to configure the EMEH cell states (EMEH preventive state, EMEH reactive state, and EMEH load state) where the UL load based AC for HSPA+ features function is used.

When RAN2879 (MEH) and RAN3266 (EMEH) are enabled in the same time, the MEH- and EMEH- introduced triggers work in parallel. Impact on interfaces The RAN3266: Enhanced Mass Event Handler feature has no impact on interfaces. Impact on network management tools The RAN3266: Enhanced Mass Event Handler feature has no impact on network management tools. Impact on system performance and capacity The RAN3266: Enhanced Mass Event Handler feature provides increased effectiveness and network capacity during mass events.

2.4.4 RAN3266 reference data RAN3266: Enhanced Mass Event Handler requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 19


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE







Alarms There are no alarms related to the RAN3266: Enhanced Mass Event Handler feature. Commands There are no commands related to the RAN3266: Enhanced Mass Event Handler feature.

Issue: 01A DRAFT

DN09232117

29



Measurements and counters Table 20


DRAFT VERSION

Counter ID

Counter name

Cell Resource (RNC)

M1000C418

MASS EVENT HANDLER PREVENTIVE STATE DURATION

M1000C419

MASS EVENT HANDLER REACTIVE STATE Cell Resource (RNC) DURATION

M1000C420

SUM OF DYNAMIC HSUPA USER LIMIT SAMPLES

Table 21

Cell Resource (RNC)

Counters modified by RAN3266

Counter ID

Counter name

Measurement

M1000C406

MASS EVENT HANDLER ACTIVE DURATION

Cell Resource (RNC)

M1000C407

MASS EVENT HANDLER ACTIVATIONS

Cell Resource (RNC)

M1006C301

MASS EVENT HANDLER INCREASED TVM PENDING TIME

RRC signalling (RNC)

M1002C685

MASS EVENT HANDLER RESTRICTED R99 Traffic (RNC) UL BITRATE

M1002C686

MASS EVENT HANDLER REJECTED E-DCH Traffic (RNC)

M1002C689

MASS EVENT HANDLER PREVENTED 2MS EDCH TTI

Traffic (RNC)

M1002C690

SC-HSDPA SELECTED DUE TO UL LOAD

Traffic (RNC)

Key performance indicators There are no key performance indicators related to the RAN3266: Enhanced Mass Event Handler feature. Parameters Table 22


Abbreviated name

Managed object

Parent structure

UE reporting interval of the EMEH periodic reporting

EMEHUEReportingInte rval

RNHSPA

-

Enhanced Mass Event Handler Enabled

EMEHEnabled

WCEL

-

Enhanced Mass Event Handler Cell States

EMEHCellStates

WCEL

-

Enhanced Mass Event Handler options

EMEHoptions

WCEL

-

WCEL

-

Enhanced Mass Event EMEHPreventivePrxOf Handler Preventive Prx fset Offset

30

Measurement

DN09232117

Issue: 01A DRAFT


Table 22

New parameters introduced by RAN3266 (Cont.) Full name

DRAFT VERSION


Abbreviated name

Managed object

Parent structure

Enhanced Mass Event Handler Reactive Prx Offset

EMEHReactivePrxOffs et

WCEL

-

Enhanced Mass Event Handler normal HSUPA throughput level

EMEHNormalHSUPATput

WCEL

-

Enhanced Mass Event Handler low HSUPA throughput level

EMEHLowHSUPATput

WCEL

-

Table 23


Abbreviated name

Managed object

Parent structure

RNC

-

Temporary max number MEHMaxHSUPAUsers of HSUPA users for the Mass Event

WCEL

-

Mass Event Handler functions

MassEventHandler

WCEL

-

Temporary TVM pending time for the Mass Event Handler

MEHTVMPendingTime

RNPS

-

UL load based HSDPA user amount limit for the MEH

MEHULLHSDPAUALimit

WCEL

-

RNC Options

Table 24

RncOptions

New PRFILE parameters introduced by RAN3266 Parameter ID

Parameter name

002:2264

RU50_SPARE_02

002:2265

RU50_SPARE_03

002:2266

RU50_SPARE_04

002:2267

RU50_SPARE_05

002:2269

RU50_SPARE_07

002:2272

RU50_SPARE_10

002:2273

RU50_SPARE_11




Issue: 01A DRAFT

License control RNC LK

DN09232117


31



2.5 RAN3263: Enhanced Power Control Benefits, functionality, system impact, reference data of the feature.

DRAFT VERSION

The RAN3263: Enhanced Power Control feature introduces power control enhancements in both RNC and BTS to ensure a better and faster reaction to the changing cell load and UE radio conditions. Power control enhancements are achieved by introducing a set of improvements in the outer loop power control (OLPC) algorithm.

2.5.1 RAN3263 benefits The RAN3263: Enhanced Power Control feature provides the following benefits: • • • • •

More efficient power control provides bigger capacity and better service quality. Better and faster power control that results in less cell overload and smoother recovery from cell overload conditions. Reduced intra-cell and inter-cell interference. Better performance at the cell edge. Increased cell capacity, especially during mass events.

2.5.2 RAN3263 functional description The RAN3263: Enhanced Power Control feature introduces the following enhancements: Subfeature 1: Enhanced Received Total Wideband Power (RTWP) overload handling BTS indicates cell’s Received Total Wideband Power (RTWP) load level to RNC using spare fields in the DCH/E-DCH Frame Protocol. Outer loop power control (OLPC) at RNC adjusts the signal-to-interference ratio (SIR) target based on the load conditions. RTWP Normal

No OLPC behavior changes in RNC.

RTWP Overload

OLPC operation is modified in RNC so that the SIR target is not increased to avoid further worsening of the RTWP load in the cell.

RTWP High Overload

OLPC in RNC lowers SIR targets for all UEs in the cell. In this case the cell is already in a pole capacity and SIR target decrease is needed to save connections.

With this functionality OLPC is more sensitive to the cell RTWP what results in faster corrective actions in case of the RTWP overload.

32

DN09232117

Issue: 01A DRAFT


Figure 3


Enhanced RTWP overload handling

OLPC CONTROLLER TPCUp/Down commands

RTWP Loadinfo

OLPC ENTITY

SIRtarget adjustment

OLPC ENTITY

DRAFT VERSION

OLPC RNC Subfeature 2: Enhanced Outer Loop Power Control This subfeature contains the following enhancements: • •

HSUPA minimum SIR target change SIR target setting optimization: – – – – –

•

Valid for both DCH and HSUPA cases. The SIR target of the first radio link (RL) of the user decreases as long as the first block error is received or until the legacy minimum SIR target value is achieved. The SIR target changes are faster if SIR target is not in converged area. The SIR target decreases for silent PS service users. Cancellation of the SIR target change according to block error ratio (BLER) state change.

Faster OLPC for DCH: –

discontinuous transmission (DTX) period, minimum step size for SIR target modification, and SIR target modification interval set in the same way as for HSUPA cases.

Subfeature 3: Power control enhancements in BTS This subfeature introduces power control enhancements in BTS and SIR target decrease for specific UEs based on RTWP. The threshold of an RTWP limitation for 2 ms HSUPA users in the BTS is increased to ensure that the overload is detected before the BTS component. Cell overload is handled in case RTWP is higher than target + 6 dB irrespective of the transport protocol (TP) domain overload state. In addition, SIR adaptation based on transport format combination indicator (E-TFCI) is introduced at BTS level. As OLPC is not always able to follow the transport block (TB) size changes fast enough, a certain TB size-specific correction factor is introduced in BTS on top of the SIR target given by RNC. With this subfeature, the SIR target is better aligned with the changing TB sizes. In addition BTS user part (UP) is made more sensitive to RTWP. RAN3263 general information RAN3263 is controlled by an RNC level license with an activation parameter in RNC for subfeature 1 and 2 and activation parameter in BTS for subfeature 3. The RNC sends license and subfeature 1 activation information to the BTS using NBAP: PRIVATE MESSAGES (Configuration Data). In the RNC the feature is used based on the license

Issue: 01A DRAFT

DN09232117

33



and the activation parameter. In the BTS subfeature 1 is used based on the activation information received from the RNC and subfeature 3 is used based on the license information received from the RNC and feature activation parameter in the BTS.

2.5.3 RAN3263 system impact RAN3263: Enhanced Power Control impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features

DRAFT VERSION

The following features complement the RAN3263: Enhanced Power Control feature: • • •

RAN2302: Dynamic HSUPA BLER RAN2886: Faster OLPC RAN3266: Enhanced Mass Event Handler feature is recommended to be used with RAN3263 feature for better uplink interference management.

Impact on interfaces The RAN3263: Enhanced Power Control feature impacts the following interfaces: • •

NBAP - RNC indicates BTS by NBAP: PRIVATE MESSAGES (Configuration Data) about licence and subfeature 1 activation. Frame Protocol - BTS indicates cell’s RTWP load level to RNC using spare fields in the DCH/E-DCH Frame Protocol.

Impact on network management tools The RAN3263: Enhanced Power Control feature impacts network management tools as follows: •

BTS Site Manager: –

•

BTSSM shows information that RNC license is needed in case of feature activation trial.

RNC Element Manager –

RNC EM supports the RAN3263 feature activation with parameters.

Impact on system performance and capacity The RAN3263: Enhanced Power Control feature impacts system performance as follows: •

•

The feature helps to handle the cell load in cases when the RTWP load is high. When the RTWP load is high or in overload states, the feature adjusts SIR-targets to decrease RTWP. Overall cell performance is better compared to the situation when the feature is not used. When the measured RTWP load is normal, there still might be some positive impacts to system performance due to subfeatures 2 and 3.

The RAN3263: Enhanced Power Control feature impacts system capacity as follows: •

34

The cell is able to perform closer to the theoretical HSUPA pole capacity when the cell is in RTWP overload state. The change is visible with traffic mix, which has multiple UEs and data bursts with variable burst sizes and transmission speeds.

DN09232117

Issue: 01A DRAFT


•


This feature improves capacity as more optimal SIR target values are adjusted. More optimal SIR targets result in lower load, more coverage, and better service quality.

2.5.4 RAN3263 reference data RAN3263: Enhanced Power Control requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

DRAFT VERSION

Table 26


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17

WBTS17

WBTS17


OMS

NetAct

MSC

SGSN

MGW

UE







Alarms Table 27

Alarms modified by RAN3263

Alarm ID

Alarm name

7775

INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

7660

BASE STATION LICENCE EXPIRED

7661

BASE STATION LICENCE NOTIFICATION

Commands There are no commands related to the RAN3263: Enhanced Power Control feature. Measurements and counters There are no measurements or counters related to the RAN3263: Enhanced Power Control feature. Key performance indicators Table 28

Existing key performance indicators related to RAN3263

KPI ID

Issue: 01A DRAFT

KPI name

RNC_167c

CS Voice Erlangs

RNC_917a

HSUPA MAC-e BLER

RNC_1036b

Average number of simultaneous HSUPA users

RNC_1687a

Maximum number of simultaneous HSUPA user per cell

RNC_1883c

Active HSUPA cell throughput

RNC_5106a

E-DCH 2ms TTI utilization

RNC_5460a

Average HSUPA user throughput

DN09232117

35



Parameters Table 29


Abbreviated name

Parent structure

EnhOLPCFuncEnabled

RNFC

-

Enhanced OLPC based on EnhOLPCRTWPEnabled RTWP enabled

WBTS

-

Enhanced OLPC functionalities enabled

DRAFT VERSION

Managed object

Table 30


Abbreviated name

Managed object

Parent structure

RNC Options

RncOptions

RNC

-

DTX threshold for uplink faster outer loop

ULFastOLPCDTXthld

RNAC

-




License control


RNC LK


2.6 RAN3341: Guaranteed Voice Calls in High Load Benefits, functionality, system impact, reference data of the feature. The RAN3341 Guaranteed Voice Calls in High Load introduces prioritization of Voice real time (RT) traffic over high speed downlink packet access/high speed packet access (HSDPA/HSPA) non-real time (NRT) traffic when downlink (DL) spreading codes are seen as a limitation during Admission control. This improves voice call success rate in high loaded cells.

2.6.1 RAN3341 benefits The RAN3341 Guaranteed Voice Calls in High Load feature provides the following benefit: •

•

36

In high loaded cells, voice call setup succeeds because the downlink spreading code congestion is avoided by prioritizing voice calls over NRT HSDPA/HSPA calls especially for non-FDPCH users. Improves voice call success rate KPIs and reduces the voice call setup failure.

DN09232117

Issue: 01A DRAFT




DRAFT VERSION

In case of non-Fractional Dedicated Physical Channel User Equipment (FDPCH UEs) or if FDPCH is not enabled in the network, the signaling radio bearer (SRB) is mapped to the dedicated traffic channel (DCH), which would consume separate spreading code in the downlink. In a highly loaded cell with high number of non-FDPCH UEs, the downlink spreading codes congestion could lead to Voice call Setup failures (RAB_STP_FAIL_CS_VOICE_AS_COD). In such cases, voice calls are admitted into the system by prioritizing them over non-FDPCH HSDPA/HSPA NRT. Up to two such nonFDPCH HSDPA/HSPA radio bearers (RBs) are released to accommodate the AMR voice call.

g

Note: If NRT-over-NRT is needed, this functionality is provided by the RAN3110: HSPA Queuing and Resource Rotation with QoS.

2.6.3 RAN3341 system impact RAN3341 Guaranteed Voice Calls in High Load impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3341: Guaranteed Voice Calls in High Load feature and any other feature. Impact on interfaces The RAN3341: Guaranteed Voice Calls in High Load feature has no impact on interfaces. Impact on network management tools The RAN3341: Guaranteed Voice Calls in High Load feature has no impact on network management tools. Impact on system performance and capacity The RAN3341: Guaranteed Voice Calls in High Load feature improves voice call success rate in high loaded cells.

2.6.4 RAN3341 reference data RAN3341: Guaranteed Voice Calls in High Load requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 32 RAS

WCDMA17

Issue: 01A DRAFT

RAN3341 hardware and software requirements IPA-RNC

RNC17

mcRNC

mcRNC17

DN09232117





Flexi Lite BTS Support not required

37


Table 32


RAN3341 hardware and software requirements (Cont.)

OMS Support not required

NetAct

MSC



SGSN Support not required

MGW

UE



Alarms There are no alarms related to the RAN3341: Guaranteed Voice Calls in High Load feature.

DRAFT VERSION

BTS faults and reported alarms There are no faults related to the RAN3341: Guaranteed Voice Calls in High Load feature. Commands There are no commands related to the RAN3341: Guaranteed Voice Calls in High Load feature. Measurements and counters Table 33

New counters introduced by RAN3341 Counter ID

Counter name

M1000C417

HSPA RT-OVER-NRT DUE TO SPREADING CODE CONGESTION

Measurement Cell Resource (RNC)

Key performance indicators There are no key performance indicators related to the RAN3341: Guaranteed Voice Calls in High Load feature. Parameters Table 34


Full Name

Abbreviated name

Managed object

Guaranteed Voice GuaranteedVoiceD WCEL calls in high LCode load

Table 35

Parent structure -

Parameters modified by RAN3341

Full name RNC Options

Abbreviated name RncOptions

Managed object RNC

Parent structure -




38

License control Long term ON/OFF license

DN09232117


Issue: 01A DRAFT



2.7 RAN3110: HSPA Queuing and Resource Rotation with QoS

DRAFT VERSION

Benefits, functionality, system impact, reference data of the feature. The RAN3110: HSPA Queuing and Resource Rotation with QoS feature introduces the HSPA Queuing and NRT-over-NRT functionalities to the queuing and the scheduling of the resources request for the HSPA and HSDPA allocations in the CELL_DCH state. During HSPA congestion, a high-priority user requesting HSPA resources can bypass a low-priority user in queue. QoS-based resource rotation that refers to NRT-over-NRT enables operator to rotate the resources between all HSPA users or to favour the highpriority users.

2.7.1 RAN3110 benefits The RAN3110: HSPA Queuing and Resource Rotation with QoS feature provides: • • •

priority access to HSPA resources for high-priority users. the possibility to guarantee HSPA resources for high-priority or authorized users. the possibility to rotate HSPA resources between all HSPA users, so higher HSPA data rates could be offered.

2.7.2 RAN3110 functional description The RAN3110: HSPA Queuing and Resource Rotation with QoS feature introduces QoSbased resource allocation queuing and scheduling for HSPA and HSDPA users. HSPA queuing In current system implementation, access to HSPA is admitted without checking QoS priorities. After allocating the HSPA resources, the RAN1262: QoS Aware HSPA Scheduler feature enables taking the QoS priorities into account when scheduling the data packets. The RAN3110: HSPA Queuing and Resource Rotation with QoS feature provides QoS-based prioritization to admission control of HSPA resources. With the RAN3110 feature, higher priority HSPA users can bypass the lower priority users in the admission queue. RNC triggers HSPA queuing when a resource allocation request for NRT service mapped to HSPA transport channels (DCH/HS-DSCH or E-DCH/HS-DSCH) arrives, or when HSPA resource rotation cannot find suitable target for HSPA NRT over NRT. The order of resource allocation is based on priorities defined with the QoSPriorityMapping parameter. In case of equal priorities, HSPA resources are allocated according to queuing time - oldest requests first. When the policy for priority-based scheduling is configured to be based on allocation and retention priority (ARP), the queuing priorities are based on ARP level (the highest priority first) and the queuing time (the longest queuing time first). Priority-based scheduling policy is defined with the PBSPolicy parameter. At maximum, users are queued for HSPA resources for 25% of the time specified with the CrQueuingTimeUL RNPS parameter. After that time, RNC tries to allocate all possible configurations (HSPA, DCH/HS-DSCH, DCH x/x).

Issue: 01A DRAFT

DN09232117

39



Resource rotation With the RAN3110: HSPA Queuing and Resource Rotation with QoS feature, new HSPA resource requests are managed according to their QoS priority. In case of congestion for HSPA resources new HSPA capacity request may trigger release of an existing HSPA user. Operator can choose between the following approaches applied during the HSPA congestion: •

DRAFT VERSION

•

Favor the highest priority users and always keep them connected. This enables operator to guarantee the HSPA connection to authorized users. Rotate HSPA resources between users, even of the same priority. Resources can be rotated after an operator-definable timeslot finishes. This enables an operator to offer higher data rates to all HSPA users.

Operator manages HSPA resource allocation using the following parameters: • • • •

PBSPolicy PBSgrantedMinDCHalloc (PBSHSMinAllocLower, PBSHSMinAllocEqual, PBSHSMinAllocHigher) IurPriority QoSPriorityMapping

Congestions that triggers NRT-over-NRT: • • • • • • •

HSDPA user amount congestion HS-DSCH MAC-d flow amount congestion E-DCH user amount congestion HSPAtot user amount congestion F-DPCH slot format congestion DPCH code congestion BTS HW congestion identified by RNC receiving information: no free E-DCH resources available from WBTS in the HSUPA Resource Status IE of the Private NBAP: Radio Resource Measurement Report.

2.7.3 RAN3110 system impact RAN3110: HSPA Queuing and Resource Rotation with QoS impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The following features must be activated before activating the RAN3110: HSPA Queuing and Resource Rotation with QoS feature: • •

RAN395: Enhanced priority based scheduling and overload control for NRT traffic RAN1262: QoS Aware HSPA Scheduling

The RAN3110: HSPA Queuing and Resource Rotation with QoS feature impacts the following features: •

40

RAN2879: Mass Event Handler

DN09232117

Issue: 01A DRAFT


•


When the RAN2879 feature is active and the maximum HSUPA user amount is exceeded by any number, the resource rotation functionality of the RAN3110: HSPA Queuing and Resource Rotation with QoS feature removes two NRT users to release the resources for new users. RAN2717: Smart LTE Layering When the RAN2717 feature is active, the NRT UEs pre-emptied from WCDMA cell are redirected to LTE. The trigger for redirection is the UE's state change to CELL_FACH, CELL_PCH, or URA_PCH.

DRAFT VERSION

The RAN3110: HSPA Queuing and Resource Rotation with QoS feature is impacted by the following features: • •

g

RAN1231: HSPA Over Iur RAN1759: Iur Mobility Enhancements Note: If the RAN1231 feature is used, the RAN1759 feature enables the resource rotation functionality to be used over the Iur interface.

Impact on interfaces This feature has no impact on interfaces. Impact on network management tools This feature has no impact on network management tools. Impact on system performance and capacity The RAN3110: HSPA Queuing and Resource Rotation with QoS feature impacts system performance and capacity as follows: • • •

It provides QoS-based prioritization to admission control of HSPA resources. During the HSPA congestion, it enables to either favor the highest priority users or to rotate HSPA resources between users (even of the same priority). It increases HSPA setup success rate.

2.7.4 RAN3110 reference data RAN3110: HSPA Queuing and Resource Rotation with QoS requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 37

Issue: 01A DRAFT


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17

NetAct 17





DN09232117

41



Alarms There are no alarms related to the RAN3110: HSPA Queuing and Resource Rotation with QoS feature. Commands There are no commands related to the RAN3110: HSPA Queuing and Resource Rotation with QoS feature. Measurements and counters

DRAFT VERSION

Table 38

42

Counter ID

New counters introduced by RAN3110 Counter name

Measurement

M1000C413

HSPA NRT-OVER-NRT DUE TO USER AMOUNT

Cell Resource

M1000C414

HSPA NRT-OVER-NRT DUE TO BTS HW CONGESTION

Cell Resource

M1000C415

HSPA NRT-OVER-NRT DUE TO SPREADING CODE OR F-DPCH SLOT FORMAT CONGESTION

Cell Resource

M1002C698

E-DCH RELEASE DUE TO NRT-OVER-NRT Traffic FOR INTERACTIVE

M1002C699

E-DCH RELEASE DUE TO NRT-OVER-NRT Traffic FOR BACKGROUND

M1004C182

SENT RL CONGESTION INDICATION ON DRNC

M1004C184

RECEIVED RL CONGESTION INDICATION L3 signalling at Iur ON SRNC

Table 39 Counter ID

L3 signalling at Iur

Existing counters related to RAN3110 Counter name

Measurement

M1002C478

HS-DSCH RELEASE DUE TO PREEMPTION FOR INTERACTIVE

Traffic

M1002C481

HS-DSCH RELEASE DUE TO PREEMPTION FOR BACKGROUND

Traffic

M1002C535

E-DCH NORMAL RELEASE FOR INTERACTIVE

Traffic

M1002C536

E-DCH NORMAL RELEASE FOR BACKGROUND

Traffic

M1004C98

NBR OF REC RL PRE EMP REQ IND ON SRNC

L3Iur

M1004C99

NBR OF SENT RL PRE EMP REQ IND ON L3Iur DRNC

M1022C51

HS-DSCH/E-DCH PACKET CALL REL DUE Packet Call TO PRE-EMP FOR INTERACTIVE

M1022C52

HS-DSCH/E-DCH PACKET CALL REL DUE Packet Call TO PRE-EMP FOR BACKGROUND

M1022C53

HS-DSCH/DCH PACKET CALL REL DUE TO PRE-EMP FOR INTERACTIVE

DN09232117

Packet Call

Issue: 01A DRAFT


Table 39


Existing counters related to RAN3110 (Cont.)

Counter ID

Counter name

M1022C54

Measurement

HS-DSCH/DCH PACKET CALL REL DUE TO PRE-EMP FOR BACKGROUND

Packet Call

For counter descriptions, see RNC Counters - RNW Part. Key performance indicators

DRAFT VERSION

Table 40


KPI ID

g

KPI name

RNC_605b

HSDPA Resource Accessibility for NRT Traffic

RNC_913b

HSUPA Resource Accessibility for NRT Traffic

Note: If the RAN3110 feature HSPA queuing or resource rotation are in use there might be both failed and successful counter updates for a single request. The RAN3110 feature enables during the reservation process to find a resource for an already rejected resource request. As the KPI counts both requests then a lower success rate than in reality can be seen. Parameters Table 41


Abbreviated name

Parent structure

HSPANRTOVERNRTEnabl ed

WCEL

-

PBS granted min HS PBSHSMinAllocHigher allocation time higher priority

WCEL

PBSgrantedMinDC HallocT

PBS granted min HS allocation time equal priority

PBSHSMinAllocEqual

WCEL


PBS granted min HS allocation time lower priority

PBSHSMinAllocLower

WCEL


HSPA NRT over NRT Enabled

Table 42


Issue: 01A DRAFT

Managed object

Abbreviated name

Managed object

Parent structure

RNC Options

RncOptions

RNC

-

Priority based scheduling policy

PBSpolicy

RNFC

-

Inactive users number in XXX over NRT

InacUserNbrXXXOverN RT

RNHSPA

-

Maximum uplink capacity request queuing time

CrQueuingTimeUL

RNPS

-

DN09232117

43


Table 42


Parameters modified by RAN3110 (Cont.)

DRAFT VERSION

Full name

Abbreviated name

Managed object

Parent structure

Priority handling over IurPriority Iur-interface

RNPS

-

HSPA QoS enabled

HSPAQoSEnabled

WCEL

-

PBS granted min DCH and HSPA allocation time

PBSgrantedMinDCHall ocT

WCEL

-

Table 43

PRFILE parameters related to RAN3110 Parameter ID

Parameter name

007:0521

HSPA_DCH_MIN_RES




License control


RNC License Key


2.8 RAN3270: Interference Control in HetNet Benefits, functionality, system impact, reference data of the feature. The RAN3270: Interference Control in HetNet feature introduces means to reduce interference created by UEs in high-power cells towards low-power cells when there are cells of different sizes under one RNC, in the same network area and using the same carrier frequencies.

2.8.1 RAN3270 benefits The RAN3270: Interference Control in HetNet feature provides the following benefits: • • • •

Ensuring the highest traffic off-load by small cells. Maximizing packet data throughput and the capacity of the combined macro-small cell system. Minimizing inter-cell interference between large and small cells and helps the radio network planning with the automatic algorithms by RNC. Improving network performance both in large and in small cells.

2.8.2 RAN3270 functional description The RAN3270: Interference Control in HetNet provides the tools for radio resource management to help cope with the large transmission power difference between the high-power and low-power cells. Both the high-power and the low-power cells are

44

DN09232117

Issue: 01A DRAFT



located in the same area and use the same carrier frequencies. A power difference up to 6dB is handled through radio network planning and optimization. The RAN3270 feature tackles power differences larger than 6dB. The RAN3270 feature has the following functionalities: •

DRAFT VERSION

•

•

Boosting the High Speed Dedicated Physical Control Channel (HS-DPCCH) with the Active Set Update (ASU) and the Serving Cell Change (SCC). This is needed when an UE is in soft handover between a high-power macro cell and low-power small cell where the high-power cell is high-speed packet access (HSPA) serving cell. Enabling periodic EcNo reporting for both the monitored and the detected cells. Periodic reporting for the detected cells is also applied to chained neighbor cells by the RAN3271: Optimized Neighbor Cell Processing feature. Reducing the intra-frequency inter-cell interference. This is done through the soft handover (SHO) between the high-power cell and the low-power cell by using cell individual offsets (CIO), dynamically calculated by the RNC. When the SHO is not possible, uplink data rate downgrading in the high power cell is used instead.

The RAN3720 feature focuses on low-power small cells operating in the same frequency as a nearby high-power macro cell. To allow the UE to detect the small cells and report them to the network, that is, to trigger handover, the small cells must have their own dominant area. If a small cell is fully overlapped by a macro cell, the UE needs to be close to the small cell's antenna to be able to detect the small cell. In some cases the macro cell can be so dominant that handover is not possible even if the UE is very close to the small cell's antenna. If the macro cell is very dominant, the uplink interference from the UEs attached to the macro cell can block the small cell. An interference from a UE attached to a high-power cell towards a small cell occurs when the UE uses uplink (UL) power according to the requirements of the high-power cell and when the UE is not in soft handover (SHO) with the small cell. The small cell cannot prevent it when it is not in the Active Set (AS) yet. Figure 4

Interference between large and small cells: case 1.

UEuplinkrange

ServingcellDL HS-DPCCH

Micro/Pico Macrocell

When the UE is in soft handover between a high-power cell and a low-power cell, the high-power cell is a HSPA serving cell and the uplink power control is done by the lowpower cell, there might be a problem with the UE uplink synchronization in high-power cell. The high-power BTS cannot receive the UE’s uplink transmission due to its low uplink transmission power. The uplink transmission is needed for uplink grant signaling and data transmission in general. Therefore control channel boosting is needed.

Issue: 01A DRAFT

DN09232117

45


Figure 5


Interference between large and small cells: case 2.

UEuplinkrange

HSDPA cellDL

DRAFT VERSION

HS-DPCCH

Smallcell Macrocell

2.8.3 RAN3270 system impact RAN3270: Interference Control in HetNet impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The RAN3270: Interference Control in HetNet feature is impacted by the following features: •

•

RAN3271: Optimized Neighbor Cell Processing The RAN3271 feature is related to the interference reduction for the chained neighbor cells. RAN3266: Enhanced Mass Event Handler The RAN3266 feature is related to the uplink load reduction via limiting the number of periodic measurement reports and the uplink data rate.

The RAN3270: Interference Control in HetNet feature impacts the following feature: •

RAN2496: 3GPP Minimization of Drive Tests The RAN2496 feature is related to the period EcNo measurement and reporting. The RAN3270 impacts the RAN2496 feature in defining the cells configures to measurement and in determining the reporting period.

Impact on interfaces The RAN3270: Interference Control in HetNet feature has no impact on interfaces. Impact on network management tools The RAN3270: Interference Control in HetNet feature has no impact on network management tools. Impact on system performance and capacity The RAN3270: Interference Control in HetNet feature has no impact on system performance or capacity.

46

DN09232117

Issue: 01A DRAFT



2.8.4 RAN3270 reference data RAN3270: Interference Control in HetNet requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

DRAFT VERSION

Table 45

Issue: 01A DRAFT


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17

NetAct 17





Alarms There are no alarms related to the RAN3270: Interference Control in HetNet feature. Commands There are no commands related to the RAN3270: Interference Control in HetNet feature. Measurements and counters Table 46 Counter ID


Measurement Soft Handover

M1007C91

CELL ADDITION REQUEST DUE TO PERIODIC REPORTING FOR ADJS

M1007C92

SUCCESSFUL ACTIVE SET UPDATES DUE Soft Handover TO PERIODIC REPORTING FOR ADJS

M1007C93

UNSUCCESSFUL ACTIVE SET UPDATES DUE TO PERIODIC REPORTING FOR ADJS

Soft Handover

M1007C94

CELL ADDITION REQUEST DUE TO PERIODIC REPORTING FOR ADJD

Soft Handover

M1007C95

SUCCESSFUL ACTIVE SET UPDATES DUE Soft Handover TO PERIODIC REPORTING FOR ADJD

M1007C96

UNSUCCESSFUL ACTIVE SET UPDATES DUE TO PERIODIC REPORTING FOR ADJD

Soft Handover

M1007C97

CELL ADDITION REQUEST DUE TO PERIODIC REPORTING FOR CHAINED NEIGHBOR CELL

Soft Handover

M1007C98

SUCCESSFUL ACTIVE SET UPDATES DUE Soft Handover TO PERIODIC REPORTING FOR CHAINED NEIGHBOR CELL

M1007C99

UNSUCCESSFUL ACTIVE SET UPDATES DUE TO PERIODIC REPORTING FOR CHAINED NEIGHBOR CELL

DN09232117

Soft Handover

47


Table 46


New counters introduced by RAN3270 (Cont.)

Counter ID

Counter name

Measurement

M1022C254

SUCCESSFUL HSUPA DATA RATE DOWNGRADES DUE TO INTERFERENCE REDUCTION

Packet Call

M1022C255

SUCCESSFUL UL DCH DATA RATE DOWNGRADES DUE TO INTERFERENCE REDUCTION

Packet Call

DRAFT VERSION

Key performance indicators There are no key performance indicators related to the RAN3270: Interference Control in HetNet feature. Parameters Table 47


Managed object

Parent structure

Enabling interference IntfCtrlHetNetEnabl control in ed Heterogeneous Networks

RNFC

-

Interference Reduction InterfRedAppliedCel Applied in Cell l

WCEL

-

Interference Reduction InterfRedPwrOffset Power Offset

RNMOBI

-

Interference reduction InterfRedULData UL data throughput limit

RNMOBI

-

Interference reduction InterfRedUEAmount UE amount limit

RNMOBI

-

Interference reduction InterfRedNBMax maximum value for nonbalance

RNMOBI

-

Interference reduction InterfRedAveWin averaging window size

RNMOBI

-

Interference Reduction InterfRedRepPeriod EcNo Reporting Period

RNMOBI

-

Interference Reduction InterfRedUpgradeTim UL Data Rate Upgrade e Time

RNMOBI

-

Interference reduction InterfRedEcNoLimit EcNo limit for soft handover

RNMOBI

-

Table 48


48

Abbreviated name

Abbreviated name

Managed object

RNC Options

RncOptions

RNC

Whitelist features

Whitelist

WDEV

DN09232117

Parent structure -

Issue: 01A DRAFT


Table 48


Parameters modified by RAN3270 (Cont.) Full name

Abbreviated name

Blacklist features

Blacklist

Managed object

Parent structure

WDEV




License control

DRAFT VERSION


RNC License Key


2.9 RAN2825: MOCN Capacity Assurance Benefits, functionality, system impact, reference data of the feature. The RAN2825: MOCN Capacity Assurance feature introduces R99 and HSDPA capacity split between Multi-Operator Core Network (MOCN) operators according to agreed operator share.

2.9.1 RAN2825 benefits With the RAN2825: MOCN Capacity Assurance feature MOCN operators can provide their end users planned quality of service.

2.9.2 RAN2825 functional description The RAN966: Multi-Operator Core Network (MOCN) feature enables several core network operators to be connected to the same RNC and fully share all RAN resources. The RAN2825: MOCN Capacity Assurance feature allows the sharing of R99 and HSDPA RAN resources between the MOCN sharing operators, as per the configured operator share. MOCN capacity shares are defined separately for R99 and HSDPA. The capacity split per configured operator share is applicable for the UEs in the CELL_DCH state and for the UEs on HS-FACH in the CELL_FACH state. The HSDPA capacity split is applicable only for the downlink data.

g

Note: The RAN2825: MOCN Capacity Assurance feature supports all operators configured with the RAN966: Multi-Operator Core Network feature. In each cell, RNC monitors the DL spreading code usage which indicates the R99 cell load level. When the cell load exceeds the threshold defined with the LHOresRateSC parameter, RNC enforces a capacity split between the MOCN operators according to operator shares configured with the R99OperatorId and R99OperatorWeight parameters. For operators exceeding the configured capacity share limit, R99 data calls are downgraded to lower bit rates and R99 voice calls, if possible, are handed over to 2G system. The cell-load-triggered capacity split actions are continued until the R99 cell load drops below the threshold. For HSDPA traffic, cell load is indicated by the total number of HSDPA and HS-FACH users in a cell. When the cell load exceeds the threshold defined with the HSDPAUserThreshold parameter, the BTS scheduler starts the capacity split actions

Issue: 01A DRAFT

DN09232117

49



according to the operator-specific shares defined with the HSDPAOperatorId and HSDPAOperatorWeight parameters. The capacity split actions continue until the number of HSDPA users decreases below the threshold defined with the HSDPAUserHysterisis parameter. The capacity split is defined here in terms of the number of TTIs available for scheduling. The RAN2825: MOCN Capacity Assurance feature supports single and dual carrier HSDPA.

DRAFT VERSION

In case of congestion, the RAN2825: MOCN Capacity Assurance feature starts the preemption and resource rotation actions to release the resources of an existing call from an operator who exceeds his share the most for a call of an operator being under his share limit. The used share is defined based on the DL spreading code usage or HSDPA user amounts. The RAN2825: MOCN Capacity Assurance feature supports the configuration of up to 25 Public Land Mobile Network (PLMN) combinations (Mobile Country Code + Mobile Network Code). The PLMNs assigned to the operator use the operator's CN and capacity share limit in the RNC. During a CN connection establishment the selected PLMN is mapped to the operator ID, which is used for cell level DCH capacity share management and also delivered to BTS for cell level HSDPA capacity share management. In case of MOCN CA there are maximum 4 sharing operators.

2.9.3 RAN2825 system impact RAN2825: MOCN Capacity Assurance impact on impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The following features must be activated before activating the RAN2825: MOCN Capacity Assurance feature: • • •

RAN966: Multi-Operator Core Network RAN1262: QoS Aware HSPA Scheduling RAN395: Priority Based Scheduling

The following features must be deactivated before activating the RAN2825: MOCN Capacity Assurance feature: • •

RAN2412: Inter Circle Roaming RAN2179: Dual Band HSDPA 42 Mbps

The RAN2825: MOCN Capacity Assurance feature is impacted by the following features: •

• •

50

RAN3110: HSPA Queuing and Resource Rotation with QoS The RAN2825 feature utilizes a subset of the resource rotation functionality of the RAN3110 feature, even if this functionality is disabled in a cell (the value of HSPANRTOVERNRTEnabled WCEL parameter is set to HSPA Queuing and HSPA NRT-over-NRT are Disabled or HSPA Queuing is Enabled). During HSDPA congestion, when HSDPA call of the operator being under his share limit cannot be admitted in the cell, RNC checks if other MOCN operators are exceeding their share. The candidate for HSDPA resource release is selected from the calls of the operator who exceeds his share the most. The rules of selection are specified by the resource rotation functionality. RAN1637: High Speed Cell_FACH DL RAN1913: High Speed Cell_FACH

DN09232117

Issue: 01A DRAFT


•


RAN2518: High Speed Cell_FACH Enhanced

Impact on interfaces The RAN2825: MOCN Capacity Assurance feature impacts the interfaces in the following way: •

Iub interface –

DRAFT VERSION

–

Capability Indication information element is added to the NBAP: PRIVATE MESSAGE. Configuration Data information element, including the RAN2825 feature status and operators share information is added to the NBAP: PRIVATE MESSAGE.

Impact on network management tools The RAN2825: MOCN Capacity Assurance feature has no impact on network management tools. Impact on system performance and capacity With the RAN2825: MOCN Capacity Assurance feature, user-specific throughput can vary due to the capacity split functionality or downgrade actions. However, the cell capacity is not impacted with this feature.

2.9.4 RAN2825 reference data RAN2825: MOCN Capacity Assurance requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 50


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17

WBTS17

WBTS17

Not supported

OMS

NetAct

MSC

SGSN

MGW

UE


NetAct 17





Alarms Table 51

Existing alarms related to RAN2825

Alarm ID

7775

Alarm name

INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

For alarm descriptions, see RNC RNW and Flexi Lite BTS Alarms and Faults and RNC RNW and Flexi Multiradio BTS WCDMA Alarms and Faults. Commands There are no commands related to the RAN2825: MOCN Capacity Assurance feature. Measurements and counters

Issue: 01A DRAFT

DN09232117

51


Table 52

DRAFT VERSION

Counter ID

52



Measurement

M1034C49

MAX NUMBER OF HS-FACH/RACH USERS PER OPER

Operator Statistics in RNC

M1034C50

MAX NUMBER OF HS-FACH/HS-RACH USERS PER OPER


M1034C51

INTER SYSTEM HHO ATTEMPTS DUE TO MOCN THR PER OPER


M1034C52

INTER SYSTEM HHO SUCCESS DUE TO MOCN THR PER OPER


M5009C2

AVERAGE ALLOCATED HSDPA USERS PER Operator specific statistics OPERATOR

M5009C3

MAXIMUM ALLOCATED HSDPA USERS PER Operator specific statistics OPERATOR

M5009C4

AVERAGE ALLOCATED HSDPA USERS PER Operator specific statistics OPERATOR WHEN CA ACTIVE

M5009C5

MAXIMUM HSDPA USERS PER OPERATOR WHEN CA IS ACTIVE

Operator specific statistics

M5009C6

NUMBER HSDPA TTIS PER OPERATOR WHEN CA IS ACTIVE


M5009C7

NUMBER HSDPA TTIS PER OPERATOR


Table 53 Counter ID

Counters modified by RAN2825 Counter name

Measurement

M1034C0

INTER SYSTEM HHO RT ATTEMPTS PER OPER


M1034C1

INTER SYSTEM HHO RT SUCCESS PER OPER


M1034C2

INTER SYSTEM HHO NRT ATTEMPTS PER Operator Statistics in RNC OPER

M1034C3

INTER SYSTEM HHO NRT SUCCESS PER OPER

M1034C8

MAX SF256 CODE OCCUPANCY PER OPER Operator Statistics in RNC

M1034C9

SUM SF256 CODE OCCUPANCY PER OPER Operator Statistics in RNC

M1034C10

DENOM SF256 CODE OCCUPANCY PER OPER


M1034C11

RAB SETUP ATTEMPTS FOR CS VOICE PER OPER


M1034C12

RAB ACCESS COMPLETIONS FOR CS VOICE PER OPER


M1034C13

RAB SETUP ATTEMPTS FOR CS DATA CONV PER OPER


M1034C14

RAB ACCESS COMPLETIONS FOR CS DATA CONV PER OPER


M1034C15

RAB SETUP ATTEMPTS FOR PS STREAM PER OPER


DN09232117


Issue: 01A DRAFT


Table 53

DRAFT VERSION

Counter ID

Issue: 01A DRAFT


Counters modified by RAN2825 (Cont.) Counter name

Measurement Operator Statistics in RNC

M1034C16

RAB ACCESS COMPLETIONS FOR PS STREAM PER OPER

M1034C17

RAB SETUP ATTEMPTS FOR PS NRT PER Operator Statistics in RNC OPER

M1034C18

RAB ACCESS COMPLETIONS FOR PS NRT Operator Statistics in RNC PER OPER

M1034C19

RAB ACTIVE COMPLETIONS FOR CS VOICE PER OPER


M1034C20

RAB ACTIVE FAILURES FOR CS VOICE PER OPER


M1034C21

RAB ACTIVE COMPLETIONS FOR CS DATA CONV PER OPER


M1034C22

RAB ACTIVE FAILURES FOR CS DATA CONV PER OPER


M1034C23

RAB ACTIVE COMPLETIONS FOR PS DATA STREAM PER OPER


M1034C24

RAB ACTIVE FAILURES FOR PS STREAM Operator Statistics in RNC PER OPER

M1034C25

RAB ACTIVE COMPLETIONS FOR PS NRT Operator Statistics in RNC PER OPER

M1034C26

RAB ACTIVE FAILURES FOR PS NRT PER OPER

M1034C27

SUM RAB HOLDING TIME FOR CS VOICE Operator Statistics in RNC PER OPER

M1034C28

SUM RAB HOLDING TIME FOR CS DATA CONV PER OPER

M1034C31

MAX NUMBER OF HSDPA USERS IN CELL Operator Statistics in RNC PER OPER

M1034C32

MAX NUMBER OF HSUPA USERS IN CELL Operator Statistics in RNC PER OPER

M1034C33

SUM OF HSDPA USERS IN CELL PER OPER


M1034C34

SUM OF HSUPA USERS IN CELL PER OPER


M1034C35

DENOM HSPA USERS IN CELL PER OPER Operator Statistics in RNC

M1034C36

HS-DSCH MAC-D FLOW ALLOCATIONS PER OPER


M1034C37

E-DCH ALLOCATIONS PER OPER


M1034C38

HS-DSCH ALLO REJECT MAX USERS PER Operator Statistics in RNC OPER

M1034C39

HS-DSCH ALLO REJECT UL POWER PER OPER


M1034C40

HS-DSCH SETUP FAILURE PER OPER


DN09232117



53


Table 53


Counters modified by RAN2825 (Cont.)

DRAFT VERSION

Counter ID

54

Counter name

Measurement

M1034C41

HS-DSCH ALLO REJECT DL POWER PER OPER


M1034C42

E-DCH ALLO CANCEL DUE TO NON ACCEPTABLE AS PER OPER


M1034C43

E-DCH ALLO REJECT MAX USERS PER OPER


M1034C44

E-DCH ALLO REJECT BTS HW PER OPER Operator Statistics in RNC

M1034C45

E-DCH SETUP FAILURE PER OPER


M1034C46

E-DCH SETUP REJECT DUE TO AC PER OPER


M1034C47

OPERATOR SHARE FOR REL99


M1034C48

OPERATOR SHARE FOR HSDPA


M5009C0

HSDPA MAC-HS DATA VOLUME PER OPERATOR


For counter descriptions, see RNC Counters - RNW Part. Key performance indicators There are no key performance indicators related to the RAN2825: MOCN Capacity Assurance feature. Parameters Table 54


Abbreviated name

Managed object

Parent structure

HSDPA Operator Identifier

HSDPAOperatorId

WCEL

HSDPA Operator Identifier Weight Pair (HSDPAOperIdWei ghtPair)

HSDPA Operator Identifier Weight

HSDPAOperIdWeight

WCEL

HSDPA Operator Identifier Weight Pair (HSDPAOperIdWei ghtPair)

HSDPA User Hysterisis

HSDPAUserHysterisis

WCEL

-

HSDPA Iur Weight

HSDPAIurWeight

WCEL

-

HSDPA User Threshold

HSDPAUserThreshold

WCEL

-

MOCN Capacity Assurance Enabled

MOCNCAEnabled

WCEL

-

R99 Iur Weight

R99IurWeight

WCEL

-

R99 Operator Identifier

R99OperatorId

WCEL

R99 Operator Identifier Weight Pair

DN09232117

Issue: 01A DRAFT


Table 54



Abbreviated name

Managed object

Parent structure (R99OperIdWeight Pair)

DRAFT VERSION

R99 Operator Weight

Table 55

WCEL

R99 Operator Identifier Weight Pair (R99OperIdWeight Pair)


Abbreviated name

Managed object

Parent structure

RNC Options

RncOptions

RNC

-

IMSI Based GSM HO

IMSIBasedGsmHo

FMCG

-

Shared area PLMN identity

SharedAreaPLMNid

IUO

-

ICR PLMN Identifier

ICRPLMNid

IUO

-

Neighbouring PLMN identity

NeighbouringPLMNid

IUR

-

ICR Host Operator Identifier

ICRHostOperatorId

RNAC

-

Multi-Operator Core Network enabled

MOCNenabled

RNFC

-

Priority based scheduling policy

PBSpolicy

RNFC

-

Dual Band HSDPA Enabled

DBandHSDPAEnabled

WCEL

-

DC HSDPA Enabled

DCellHSDPAEnabled

WCEL

-

HSPA QoS enabled

HSPAQoSEnabled

WCEL

-

Multi Cell HSDPA Enabled

MCellHSDPAEnabled

WCEL

-

Number of UEs in inter-RAT load HO

LHONumbUEInterRAT

WCEL

-

NRT FMCG Identifier

RtFmcgIdentifier

WCEL

-

Table 56

Parameters related to RAN2825 Full name

Issue: 01A DRAFT

R99OperatorWeight

Abbreviated name

Managed object

Parent structure

ICR Operator Identifier

ICROperatorId

IUO

-

ICR Operator Name

ICROperatorName

IUO

-

ICR Downgrade Delay Timer

ICRDowngradeDelayTi mer

RNPS

-

DN09232117

55


Table 56


Parameters related to RAN2825 (Cont.)

DRAFT VERSION

Full name

56

Abbreviated name

Managed object

Parent structure

Minimum RX level for non-critical HO

AdjgMinRxLevNCHO

HOPG

-

Penalty time for GSM cell in non-critical HO

AdjgPenaltyTimeNCHO

HOPG

-

Neighbour cell priority for SLHO

AdjgPrioritySLHO

HOPG

-

Number of UEs in inter-RAT load HO

LHONumbUEInterRAT

WCEL

-

Maximum number of UEs in CM due to SLHO measurement

MaxNumberUECmSLHO

WCEL

-

Load HO reservation rate of DL spreading codes

LHOResRateSC

WCEL

-

Window size for DL SC reservation rate measurement to start LHOs

LHOWinSizeONResRate SC

WCEL

-

Window size for DL SC reservation rate measurement to stop LHOs

LHOWinSizeOFFResRat eSC

WCEL

-

Hysteresis for DL SC measurement of LHO

LHOHystTimeResRateS C

WCEL

-

Delay to broadcast DL LHODelayOFFResRateS SC load based HO state C over

WCEL

-

Load HO DL power offset

LHOPwrOffsetDL

WCEL

-

Load HO UL power offset

LHOPwrOffsetUL

WCEL

-

Window size for interference measurement to start LHOs

LHOWinSizeONInterfe rence

WCEL

-

Window size for interference measurement to stop LHOs

LHOWinSizeOFFInterf erence

WCEL

-

Hysteresis for interference measurement of LHO

LHOHystTimeInterfer ence

WCEL

-

Delay to broadcast interference load based HO state over

LHODelayOFFInterfer ence

WCEL

-

DN09232117

Issue: 01A DRAFT


Table 56

Parameters related to RAN2825 (Cont.) Full name

DRAFT VERSION


Abbreviated name

Managed object

Parent structure

Load HO DL NRT capacity request rejection rate

LHOCapaReqRejRateDL

WCEL

-

Load HO UL NRT capacity request rejection rate

LHOCapaReqRejRateUL

WCEL

-

Load HO NRT traffic base load

LHONRTTrafficBaseLo ad

WCEL

-

Load HO NRT traffic base load

LHONRTTrafficBaseLo ad

WCEL

-

Window size for NRT load measurement to start LHOs

LHOWinSizeONCapaReq RejRate

WCEL

-

Window size for NRT load measurement to stop LHOs

LHOWinSizeOFFCapaRe qRejRate

WCEL

-

Hysteresis for NRT load measurement of LHO

LHOHystTimeCapaReqR ejRate

WCEL

-

Delay to broadcast NRT LHODelayOFFCapaReqR load based HO state ejRate over

WCEL

-

Load HO hard blocking ratio

LHOHardBlockingRati o

WCEL

-

Load HO hard blocking base load

LHOHardBlockingBase Load

WCEL

-

Window size for hard blocking measurement to start LHOs

LHOWinSizeONHardBlo cking

WCEL

-

Window size for hard blocking measurement to stop LHOs

LHOWinSizeOFFHardBl ocking

WCEL

-

Hysteresis for hard blocking measurement of LHO

LHOHystTimeHardBloc king

WCEL

-

Delay to broadcast hard blocking load based HO state over

LHODelayOFFHardBloc king

WCEL

-




Issue: 01A DRAFT

License control RNC License Key

DN09232117


57



2.10 RAN3269: Optimised HSDPA Scheduler Benefits, functionality, system impact, reference data of the feature. The RAN3269: Optimised HSDPA Scheduler feature introduces optimizations to a HSDPA (high-speed downlink packet access) scheduler that increases the TTI (Transmission Time Interval) utilization and improves downlink cell throughput and end user experience.

DRAFT VERSION

2.10.1 RAN3269 benefits The RAN3269: Optimised HSDPA Scheduler feature provides the following benefits: •

Improved downlink (DL) cell throughput and end user experience: –

•

Increased TTI utilization results in overall increased of a HSDPA cell throughput.

Reduced scheduling delay: –

A HSDPA scheduling delay is reduced due to an increased number of the parallel code multiplexed users transmitting in the same TTI.

2.10.2 RAN3269 functional description High-Speed Shared Control Channel (HS-SCCH) resource utilization improvement A single MAC-hs scheduler in FSMr3 supports maximum up to 6 cells. The number of cells per scheduler related to the RAN3269 feature remains the same after the feature is enabled. The central processing unit (CPU) load limits the maximum number of parallel code multiplexed users transmitting in same 2ms TTI to 12 even though the cells can have up to 24 configured HS-SCCH channels. After enabling the RAN3269 feature the maximum number of parallel code multiplexed users per TTI increases from 12 to 24. With the RAN3269 feature users which do not require MAC-hs/ehs PDU assembly such as retransmission, the CPC order are considered (counted as) 0 users in resource check phase. There are also users with a small MAC-hs/ehs PDU assembly. And MAC-hs tries to serve those kinds of users depending on the total number of PDUs to be assembled in the current TTI.

2.10.3 RAN3269 system impact RAN3269: Optimised HSDPA Scheduler impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3269: Optimised HSDPA Scheduler feature and any other feature. Impact on interfaces The RAN3269: Optimised HSDPA Scheduler feature has no impact on interfaces. Impact on network management tools

58

DN09232117

Issue: 01A DRAFT



The RAN3269: Optimised HSDPA Scheduler feature has no impact on network management tools. Impact on system performance and capacity The RAN3269: Optimised HSDPA Scheduler feature impacts system performance as follows: •

DRAFT VERSION

•

There is an improvement of performance in HSDPA call delay in case system reaches the maximum number of parallel code multiplexed users for FSMr3. The maximum number of the parallel code multiplexed users transmitting in same 2ms TTI is changed from 12 to 24. There is a cell throughput improvement in high load traffic scenario with the HSFACH users. In a lab environment we can see around 2% improvement. MAC-hs can schedule more users and buffer occupancy is small for this type of the users.

2.10.4 RAN3269 reference data RAN3269: Optimised HSDPA Scheduler requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 58


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17



Not planned

WBTS17

Not planned

OMS

NetAct

MSC

SGSN

MGW

UE







The RAN3269 feature is supported on FSMr3 or newer BTS System Module variant. Alarms There are no alarms related to the RAN3269: Optimised HSDPA Scheduler feature. Commands There are no commands related to the RAN3269: Optimised HSDPA Scheduler feature. Measurements and counters Table 59 Counter ID

Issue: 01A DRAFT


Measurement

M5011C25

NUMBER OF TTIs WITH 13 SCHEDULED HSDPA USERS

HSPA Scheduler Monitoring

M5011C26



M5011C27



DN09232117

59


Table 59



DRAFT VERSION

Counter ID

Counter name

Measurement

M5011C28



M5011C29



M5011C30



M5011C31



M5011C32



M5011C33



M5011C34



M5011C35



M5011C36



Key performance indicators There are no key performance indicators related to the RAN3269: Optimised HSDPA Scheduler feature. Parameters There are no parameters related to the RAN3269: Optimised HSDPA Scheduler feature. Sales information Table 60


Product structure class Basic Software (BSW)

License control -

Activated by default Yes

2.11 RAN3271: Optimized Neighbor Cell Processing Benefits, functionality, system impact, reference data of the feature. The RAN3271: Optimized Neighbor Cell Processing feature introduces automatic optimization of an intra-frequency neighbor cell processing for the large cells-small cells interworking, which is done in a real time. The feature provides means to manage calls and handovers in a heterogeneous radio network environment and in the environments where neighbor cells of neighbor cells could be considered target cells for handovers.

60

DN09232117

Issue: 01A DRAFT



2.11.1 RAN3271 benefits The RAN3271: Optimized Neighbor Cell Processing feature provides the following benefits: • •

It facilitates the configuration of the neighbor cell relations in a high cell density area. It helps cope with the 3GPP standard limitation of maximum 32 intra-frequency cells in the neighbor cell list which is signaled from the network to the UEs.

DRAFT VERSION

2.11.2 RAN3271 functional description The RAN3271: Optimized Neighbor Cell Processing feature manages an environment where a high number of small cells exist within a small area. With the RAN3271 feature less effort is needed for optimization of the neighbor cell relations in the heterogeneous networks with a high number of small cells located in the same area as macro cells. This feature consists of : •

•

Soft handover support with the missing neighbor relations to the target cell, that is, chained neighbor cell concept. Chained neighbor cells are the cells which are defined as the ADJS (intra-frequency adjacency) neighbor cells of ADJS neighbor cells defined for a cell. ASU (Active Set Update) to Detected Set cell reported in event-triggered measurement report.

The RAN3271 feature has the following functionalities: • • • • •

intra-frequency handover to chained neighbor cell event-based Detected Set Reporting (DSR) for intra-frequency cells alarm/notification when a chained neighbor cell indicates that two or more cells out of the reported cells have the same scrambling code Active Set Update to a chained neighbor cell based on event-triggered measurement report Cell Individual Offset for 1B and 1C events for cells based on event-triggered measurement report.

Basics of chained neighbors When several cells, for example macro and small cells, are allocated in the same frequency, the maximum amount of possible neighbor cells that can be indicated to UE for measuring is 32. This causes a limitation when all small cells in same area with macro cell cannot be indicated to the UE as the neighbor cells of macro cell because the other relevant macro cells must be indicated as neighbors due to mobility and coverage reasons. The chained neighbor cell concept with Detected Set Reporting must overcome this restriction by enabling UE to report detected small cells and Radio Network Controller to identify the reported cells as chained neighbor cells for handovers.

Issue: 01A DRAFT

DN09232117

61


DRAFT VERSION

Figure 6


Small cell – macro cell network.

Smallcells

Macrocells

The RAN3721 feature focuses on small cells operating in the same frequency as nearby macro cells. To allow the UE to detect a small cell and report it to the network, that is, to trigger event-based handover, the small cell needs to have its own dominance area. If a small cell is fully overlapped by a macro cell, the UE needs to be close to the small cell's antenna to be able to detect it. In some cases the macro cell can be so dominant that event 1A is not triggered even if the UE is very close to the small cell's antenna. Therefore a handover to the small cell is not possible. If the macro cell is very dominant, the uplink interference from the UEs attached to macro cell can block the small cell. The RAN3271 feature allows the network operator to define several small cells with own dominance area under macro cells and provide support for mobility and handovers between macro cells and small cells. The RNC provides counters for the missing synchronization incidents attempting to add a cell to the Active Set. This allows the network operator to identify the cases where radio link is released before synchronization happened. The counters are defined for RT (real time) and NRT (non-real time), and for both ADJS and ADJD (additional intrafrequency adjacency) cells and the chained neighbor cells. There are the following counters for the ADJS and the ADJD cells: • •

M1007C87 Missing synchronization for an ADJS or ADJD cell that was attempted to be added to Active Set for a RT radio link. M1008C88 Missing synchronization for an ADJS or ADJD cell that was attempted to be added to Active Set for a NRT radio link.

The chained neighbor concept makes it possible to find the relevant cells that are not Indicated to UE as neighbor cells to the Active Set cell. The cells set as neighbor cells to the Active Set cell are called gateway cells. Chained cells are defined then as neighbor cells to these gateway cells. The RAN3271 feature requires the Detected Set Reporting for events: 1A, 1B and 1C. Using of the chained neighbor cells in a macro cell – small cell network applies to all kind of networks despite of cell size and BTS type in case there are limitations with numbers of neighbor cell.

62

DN09232117

Issue: 01A DRAFT


DRAFT VERSION

Figure 7

Issue: 01A DRAFT


Chained neighbors in the macro cell – small cell network.

Macrocell Gatewaycell Smallcell/non-neighborcellfor AS

When finding the scrambling code, reported by UE, the RNC checks among the defined neighbor cells of the cell in the Active Set, that is, originating cell. The identification of the cell is based on reported scrambling code and on cell ID. In case the reported scrambling code was not found among defined neighbor cells, the RNC checks the chained neighbor cells.

DN09232117

63


Figure 8


Scrambling codes in chained neighbors cells.

Cell:SC#1,ID#1

Cell:SC#2,ID#2

DRAFT VERSION

1

Cell:SC#3,ID#3

Cell:SC#4,ID#4 2 Cell:SC#5,ID#5

X

3

Cell:SC#1,ID#6

X -originatingcell 1,2,3 -neighborcells Duplicating the scrambling codes in chained neighbors requires identification of the intrafrequency chained neighbor cell and the BTS that is not the neighbor cell for the originating cell. The originating cell, for example the cell where the UE is located and from where it is reporting the SC #1 based on the DSR. As chained neighbor is used, SC #1 is found behind X’s neighbor cells 1 and 3. In case of duplicating scrambling code the Active Set Update (ASU) is not done and the alarm must be set to indicate the duplicate reported scrambling code.

2.11.3 RAN3271 system impact RAN3271: Optimized Neighbor Cell Processing impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features It is recommended to use the RAN3270: Interference Control in HetNet feature together with the RAN3271 feature. Impact on interfaces The RAN3271: Optimized Neighbor Cell Processing feature has no impact on interfaces. Impact on network management tools The RAN3271: Optimized Neighbor Cell Processing feature has no impact on network management tools. Impact on system performance and capacity

64

DN09232117

Issue: 01A DRAFT



The RAN3271: Optimized Neighbor Cell Processing feature has no impact on system performance or capacity.

2.11.4 RAN3271 reference data RAN3271: Optimized Neighbor Cell Processing requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information.

DRAFT VERSION

Requirements

Issue: 01A DRAFT

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17

NetAct 17





Alarms Table 61


Alarm ID

Alarm name

3484

CONFLICTING SCRAMBLING CODES

3485

SCRAMBLING CODE CONFLICT

Commands There are no commands related to the RAN3271: Optimized Neighbor Cell Processing feature. Measurements and counters Table 62 Counter ID


Measurement

M1007C75

CELL ADDITION REQUEST DUE TO EVENT 1A ON CHAINED NEIGHBOR SHO FOR RT

Soft Handover

M1007C76

CELL ADDITION REQUEST DUE TO EVENT 1A ON CHAINED NEIGHBOR SHO FOR NRT

Soft Handover

M1007C77

CELL REPLACEMENT REQUEST DUE TO EVENT 1C ON CHAINED NEIGHBOR SHO FOR RT

Soft Handover

M1007C78

CELL REPLACEMENT REQUEST DUE TO EVENT 1C ON CHAINED NEIGHBOR SHO FOR NRT

Soft Handover

M1007C79

CELL ADDITION REPEATED REQUEST Soft Handover AFTER FAILURE ON CHAINED NEIGHBOR SHO FOR RT

DN09232117

65


Table 62

DRAFT VERSION

Counter ID

66


New counters introduced by RAN3271 (Cont.) Counter name

Measurement

M1007C80

CELL ADDITION REPEATED REQUEST Soft Handover AFTER FAILURE ON CHAINED NEIGHBOR SHO FOR NRT

M1007C81

CELL REPLACEMENT REPEATED REQUEST Soft Handover AFTER FAILURE ON CHAINED NEIGHBOR SHO FOR RT

M1007C82

CELL REPLACEMENT REPEATED REQUEST Soft Handover AFTER FAILURE ON CHAINED NEIGHBOR SHO FOR NRT

M1007C83

SUCCESSFUL ACTIVE SET UPDATES ON CHAINED NEIGHBOR SHO FOR RT

Soft Handover

M1007C84

SUCCESSFUL ACTIVE SET UPDATES ON CHAINED NEIGHBOR SHO FOR NRT

Soft Handover

M1007C85

UNSUCCESSFUL ACTIVE SET UPDATES ON CHAINED NEIGHBOR SHO FOR RT

Soft Handover

M1007C86

UNSUCCESSFUL ACTIVE SET UPDATES ON CHAINED NEIGHBOR SHO FOR NRT

Soft Handover

M1007C87

SYNC MISSING FOR ADDED CONFIGURED Soft Handover NEIGHBOR CELL FOR RT

M1007C88

SYNC MISSING FOR ADDED CONFIGURED Soft Handover NEIGHBOR CELL FOR NRT

M1007C89

SYNC MISSING FOR ADDED CHAINED NEIGHBOR CELL FOR RT

Soft Handover

M1007C90

SYNC MISSING FOR ADDED CHAINED NEIGHBOR CELL FOR NRT

Soft Handover

Table 63 Counter ID

Existing counters related to RAN3271 Counter name

Measurement

M1028C0

CPICH ECNO DETECTED CELL SUM

Autodef SHO DSR

M1028C1

CPICH ECNO DETECTED CELL DENOM

Autodef SHO DSR

M1028C2

CPICH RSCP DETECTED CELL SUM

Autodef SHO DSR

M1028C3

CPICH RSCP DETECTED CELL DENOM

Autodef SHO DSR

M1013C0

NUMBER OF INTRA FREQUENCY SHO ATTEMPTS

Autodef SHO

M1013C1

NUMBER OF COMPLETED INTRA FREQUENCY SHO

Autodef SHO

M1013C2

CPICH ECNO SHO DIFFERENCE SUMMATION

Autodef SHO

M1013C3

CPICH ECNO SHO DIFFERENCE DENOMINATOR

Autodef SHO

M1013C4

CPICH ECNO SHO SUM

Autodef SHO

M1013C5

CPICH ECNO SHO DENOM

Autodef SHO

M1013C6

CPICH RSCP SHO SUM

Autodef SHO

M1013C7

CPICH RSCP SHO DENOM

Autodef SHO

DN09232117

Issue: 01A DRAFT



Key performance indicators There are no key performance indicators related to the RAN3271: Optimized Neighbor Cell Processing feature. Parameters Table 64


DRAFT VERSION

Full name

Abbreviated name

Managed object

Parent structure

Enabling the Optimized OptNeighProcEnabled Neighbor Cell Processing

RNFC

-

Enabling the sending of chained neighbor cell list over Iur

IUR

-

ADJD

-

NNChainListOverIur

CPICH Ec/No Offset for AdjdEcNoOffset ADJD cell

Table 65


Abbreviated name

RNC Options

RncOptions

Detected Set Reporting DSRepBasedSHO Based SHO

Managed object

Parent structure

RNC

-

FMCS

-




License control


RNC License Key


2.12 RAN3291: UE History for WCDMA-LTE Mobility Benefits, functionality, system impact, reference data of the feature. The RAN3291: UE History for WCDMA-LTE Mobility feature adds the following new functionalities to the RAN2264: Smart LTE Handover and RAN2980: Measurement Based LTE Layering features: • •

Verification of LTE subscription by means of UE history information. Restriction of handovers and redirections back to LTE after coverage reason handover from LTE.

2.12.1 RAN3291 benefits The RAN3291: UE History for WCDMA-LTE Mobility feature provides the following benefits:

Issue: 01A DRAFT

DN09232117

67


• •


An increased usage of LTE for the LTE subscribers. A reduced possibility of fail in re-directions and handovers to LTE due to missing LTE subscription or LTE coverage.

DRAFT VERSION


68

The RAN3291: UE History for WCDMA-LTE Mobility feature enables verification whether the user has LTE subscription based on the UE history information. This functionality allows handover and redirection back to LTE also in cases where the UE has been handed over from LTE to WCDMA due to single radio voice call continuity (SRVCC), load or mobility reasons. The other methods (available in earlier releases) that are used to decide whether the UE has LTE subscription are E-UTRAN Service Handover IE sent from the core network (CN) to RNC (TS 25.413), pre-redirection information element (IE) sent from UE to RNC (TS 25.331) and indication of a CS fall back call, sent either from UE to RNC or from CN to RNC (TS 25.331 and TS 25.413). These features can be used together with the new feature to maximize LTE usage while minimizing the probability of failures. Figure 10: RNC decision logic about handover or redirection to LTE presents the RNC decision logic for allowing or rejecting the handover of redirection to LTE, if the coverage exists.

DN09232117

Issue: 01A DRAFT


Figure 9


RNC decision logic about handover or redirection to LTE

RNCdecisionlogicforallowing/notallowing handoverorre-directiontoLTE,ifcoverageexists UEisLTE capable

No

DRAFT VERSION

Yes

No

E-UTRANserviceIEnor DedicatedPriorities (RAN3079)donot preventhandovertoLTE Yes

UEhistoryin LTE

Yes

No

CSfallbackcall

Yes

No

No

Missingpreredirectioninfo

Handoversandre-directions toLTEarenotallowed

Yes

Handoversandre-directions toLTEareallowed

The RNC receives the UE history information from the CN in the RANAP: RELOCATION REQUEST message. If the last visited cell list in the UE history information contains a LTE cell or cells, the RNC assumes that the user has LTE subscription. If the last visited cell list does not contain LTE cells, the RNC assumes that the user does not have LTE subscription. If the user has LTE subscription, the RNC allows starting of inter-system measurements for handover to LTE and for redirection to LTE as well as blind redirection to LTE if the LTE layering is configured to be done blindly. The RNC verifies the cause of the inter-system handover from LTE to WCDMA based on the value of the cause IE which is received from the CN in the RANAP: RELOCATION REQUEST message. If the UE has been handed over to the WCDMA network from the LTE network because of coverage reasons, the RNC neither hands over nor redirects UE (with or without preceding measurements) back to the LTE network as long as the target cell of the coverage-motivated inter-system handover from LTE to WCDMA stays in the active set. Handover and redirection become possible after the target cell has been removed from the active set.

Issue: 01A DRAFT

DN09232117

69



2.12.3 RAN3291 system impact RAN3291: UE History for WCDMA-LTE Mobility impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The following feature must be activated before activating the RAN3291: UE History for WCDMA-LTE Mobility feature:

DRAFT VERSION

•

RAN2176: LTE PS Handover

The RAN3291: UE History for WCDMA-LTE Mobility feature impacts the following features: • •

RAN2264: Smart LTE Handover RAN2980: Measurement Based LTE Layering The RAN3291 adds the following functionalities to the RAN2264 and RAN2980: – –

Verification of LTE subscription with the UE history information. Restriction of handovers and redirections back to LTE after coverage reason handover from LTE.

The RAN3291: UE History for WCDMA-LTE Mobility feature is impacted by the following feature: •

RAN3079: Dedicated Priorities When this feature is enabled, the handover to LTE is not made if the LTE carrier frequency is not included in the subscriber specific priority information.

Impact on interfaces The RAN3291: UE History for WCDMA-LTE Mobility feature impacts interface as follows: •

Iu interface –

The messages about Last Visited Cell Information and Last Visited E-UTRAN Cell Information is sent.

Impact on network management tools The RAN3291: UE History for WCDMA-LTE Mobility feature has no impact on network management tools. Impact on system performance and capacity The RAN3291: UE History for WCDMA-LTE Mobility feature has no impact on system performance or capacity.

2.12.4 RAN3291 reference data RAN3291: UE History for WCDMA-LTE Mobility requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

70

DN09232117

Issue: 01A DRAFT


DRAFT VERSION

Table 67



RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17

NetAct 17





Alarms There are no alarms related to the RAN3291: UE History for WCDMA-LTE Mobility feature. Commands There are no commands related to the RAN3291: UE History for WCDMA-LTE Mobility feature. Measurements and counters Table 68


Counter ID

Counter name

Measurement

M1010C278

INCOMING HANDOVERS FROM LTE DUE TO LTE COVERAGE

Inter System Handover

M1010C279

BLOCKED HANDOVERS TO LTE DUE TO MISSING LTE SUBSCRIPTION


M1010C280

BLOCKED REDIRECTIONS TO LTE DUE TO MISSING LTE SUBSCRIPTION


M1010C281

BLOCKED HANDOVERS TO LTE DUE TO LTE COVERAGE HANDOVER


M1010C282

BLOCKED REDIRECTIONS TO LTE DUE TO LTE COVERAGE HANDOVER


Key performance indicators There are no key performance indicators related to the RAN3291: UE History for WCDMA-LTE Mobility feature. Parameters Table 69


Managed object

Parent structure

RNMOBI

-

NeighbourRNCFeatureSup Neighbour RNC port Feature Support

IUR

-

RANAPCause1LTECoverage RANAP Cause 1 LTE Ho Coverage Handover

RNMOBI

-

UEHistoryInfoEnabled

Issue: 01A DRAFT

Abbreviated name

UE History Information Enabled

DN09232117

71


Table 69



Abbreviated name

RANAPCause2LTECoverage RANAP Cause 2 LTE Ho Coverage Handover

Table 70

RNMOBI

Parent structure -


Abbreviated name

RNC Options

DRAFT VERSION

Managed object

RncOptions

Managed object RNC

Parent structure -




License control


RNC License Key


2.13 RAN3044: Uplink CoMP Benefits, functionality, system impact, reference data of the feature. The RAN3044: Uplink CoMP feature enables BTS to combine the receiver signals from the current and neighbor sectors even before softer handover. Thanks to receiver combining, there is no need to wait for the downlink UE measurements to update the active cell set.

2.13.1 RAN3044 benefits The RAN3044: Uplink CoMP feature provides the following benefits: • •

Increases uplink throughput at cell borders and reduces interference with neighboring cells. Increases the probability of successful softer HO and Serving Cell Change, especially for fast moving UEs.

2.13.2 RAN3044 functional description The RAN3044: Uplink CoMP feature introduces uplink (UL) coordinated multipoint (CoMP) transmission to BTS even before softer handovers (HO). BTS receiver combines signals from all additional antennas/links from neighbor sectors in the same local cell group. The signals are combined before UE measurements trigger an active set update. When the receiver combining starts, BTS also uses the signal-to-interference ratio (SIR) information of neighbor sector antennas/links for UL scheduling. In consequence, the UL throughput at cell boundaries and the probability of successful softer HO and serving cell change increases. This feature also reduces signal interference with neighboring cells by increasing the area of UL softer HO .

72

DN09232117

Issue: 01A DRAFT



For example, if the UE has radio link at Cell 21 and BTS registers sufficient UE power in Cell 22, BTS creates a virtual RL for the UE even before the signaling from RNC arrives and receiver combining starts. At the same time, the SIR from the virtual RL is used for UL scheduling. Figure 10

RAN3044 process

Cell22

DRAFT VERSION

Cell23

UEmoving virtualRL

activeRL

Cell21

g

Note: RNC is not involved in the UL CoMP.

2.13.3 RAN3044 system impact RAN3044: Uplink CoMP impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3044: Uplink CoMP feature and any other feature. Impact on interfaces RAN3044: Uplink CoMP feature has no impact on interfaces. Impact on network management tools RAN3044: Uplink CoMP feature has no impact on network management tools. Impact on system performance and capacity The RAN3044 Uplink CoMP feature impacts system performance as follows: • •

Issue: 01A DRAFT

Increases UL throughput as signal of neighbor sector is used and decreases the interference. Controls the UL throughput stability when UE moves between cells due to DL measurements, as UE has already used the signal of neighbor sectors.

DN09232117

73


•


Improves the probability of successful softer HO and serving cell change, as the related control plane message can be received via several sectors.

This feature has no impact on system capacity.

2.13.4 RAN3044 reference data RAN3044: Uplink CoMP requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information.

DRAFT VERSION

Requirements Table 72


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17



WBTS17

WBTS17


OMS

NetAct

MSC

SGSN

MGW

UE







This featue does not require any additional hardware. Alarms There are no alarms related to the RAN3044: Uplink CoMP feature. Commands There are no commands related to the RAN3044: Uplink CoMP feature. Measurements and counters Table 73 Counter ID


Measurement

M5005C61

SUM OF UL COMP USERS

HSPA in WBTS Extension (WBTS)

M5005C62

NUMBER OF VRL IN A CELL


M5005C63

NUMBER OF SUCCESFUL VRL FORECAST


M5005C64

DENOMINATOR FOR UL COMP


M5005C65

AVERAGE NUMBER OF USERS SCHEDULED HSPA in WBTS Extension BY VRL SIR (WBTS)

M5005C66

AVERAGE VRL USER THROUGHPUT


Key performance indicators There are no key performance indicators related to the RAN3044: Uplink CoMP feature. Parameters

74

DN09232117

Issue: 01A DRAFT


Table 74



Abbreviated name

Uplink CoMP enabled

uplinkCoMPEnabled

Managed object BTSSCW

Parent structure -




License control

DRAFT VERSION


BTS License Key


2.14 RAN3274: Uplink Data Compression Benefits, functionality, system impact, reference data of the feature. The RAN3274: Uplink Data Compression feature introduces new compression for uplink (UL) data and header based on the Qualcomm proprietary uplink compression.

2.14.1 RAN3274 benefits The RAN3274: Uplink Data Compression feature provides the following benefits: •

Improved user experience: More application data can be sent with the same bandwidth, which leads to a better perceived speed of the connection and improved device battery life.

2.14.2 RAN3274 functional description The RAN3274: Uplink Data Compression (UDC) feature introduces decompression of the compressed data received from the UE in uplink (UL). The decompression is based on the proprietary compression scheme introduced by Qualcomm. The compression of uplink data reduces the total uplink data volume and thereby reduces the interference, which increaces the overall uplink capacity, improves user experience and reduces the UE battery consumption. The compression of uplink data is based on pattern matching and an entropy coding. A significant amount of redundancy exists within and across the packets received in uplink and this increases the potential for compression in the UE. A compressor and a decompressor maintain a fixed amount of memory to keep track of the repetitive patterns from the past and across packets. The UE compresses both header and payload in the uplink packets. The compressed packets are decompressed at the RNC and the base station is not impacted by the RAN3274 feature. The decompression at the RNC requires an ordered delivery of packets. It is located above the Radio Link Control (RLC) and the Packet Data Convergence Protocol (PDCP) layers. This works only with the UEs that are capable of working with the RAN3274 feature and it does not impact UEs that do not support the RAN3274 feature. The UE capability is detected through Radio Resource Control (RRC message, IE and value to be checked) signaling.

Issue: 01A DRAFT

DN09232117

75



Uplink data compression is enabled only for PS NRT RABs using the AM RLC mode. It works in Cell FACH and Cell DCH states. In case there are more than one PS NRT RABs then UDC is applied only for one PS NRT. Figure 11

Architecture of Uplink Data Compression Applications

ApplicationServers

DRAFT VERSION

@

@ www

www

OS

CoreNetwork

UEModem

RAN

TCP/IP Header

Payload

TCP/IP Header

UL Data Compression

Payload

UL Data Decompression

Compressed Packet

Compressed Packet

RLC,MAC,PHY

RLC,MAC,PHY

CompressedPacket (overtheair) Uplink

2.14.3 RAN3274 system impact RAN3274: Uplink Data Compression impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The RAN3274: Uplink Data Compression feature is impacted by the following feature: •

RAN3082: Device Detection If both the RAN3274 and the RAN3082 features are activated simultaneously in an RNC, the RNC combines the International Mobile Equipment Identity (IMEI) and the uplink data compression capability inquiry. The RNC stores the IMEI and the UDC capability information from the UE for the duration of the RRC connection. The IMEI inquiry procedure is used for the UDC capability inquiry.

Impact on interfaces

76

DN09232117

Issue: 01A DRAFT



The RAN3274: Uplink Data Compression feature has no impact on interfaces. Impact on network management tools The RAN3274: Uplink Data Compression feature has no impact on network management tools. Impact on system performance and capacity The RAN3274: Uplink Data Compression feature has no impact on system performance or capacity.

DRAFT VERSION

2.14.4 RAN3274 reference data RAN3274: Uplink Data Compression requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 76 RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE


NetAct17




Qualcom UL compression support required

Alarms There are no alarms related to the RAN3274: Uplink Data Compression feature. Commands There are no commands related to the RAN3274: Uplink Data Compression feature. Measurements and counters Table 77 Counter ID

Issue: 01A DRAFT



Measurement

M1022C256

UDC ACTIVATION ATTEMPTS

Packet Call

M1022C257

SUCCESSFUL UDC ACTIVATION

Packet Call

M1022C258

IMPLICIT UDC DEACTIVATION

Packet Call

M1022C259

UE NUMBER SUPPORTING UDC

Packet Call

M1022C260

RECEIVED UDC SDU BYTES COMPRESSED Packet Call

M1022C261

RECEIVED UDC SDU BYTES DECOMPRESSED

DN09232117

Packet Call

77


Table 78



Counter ID

Counter name

Measurement

M1022C237

RLC RESET TRIGGERED BY RNC

Packet Call

M1022C240

RLC UL SDU BYTES RECEIVED

Packet Call

Key performance indicators There are no key performance indicators related to the RAN3274: Uplink Data Compression feature.

DRAFT VERSION

Parameters

78

Table 79


UDC Enabled

Table 80

Abbreviated name

UDCEnabled

Managed object RNFC

Parent structure -


RNC Options

Abbreviated name

RncOptions

Managed object RNC

Parent structure -




License control RNC License Key

DN09232117


Issue: 01A DRAFT


Transmission and transport features

3 Transmission and transport features 3.1 RAN3279: IP based Iu-interfaces via satellite Benefits, requirements, functionality, system impact, reference data of the feature. Introduction to the feature

DRAFT VERSION

The RAN3279: IP Based Iu-interfaces via satellite feature introduces support for IPbased transport via satellite connections for Iu-PS, Iu-CS, Iu-BC, and Iu-PC interfaces. The satellite links are used in cases where conventional IP/Ethernet transport is not available or feasible like on islands, mountains, jungle, or any other remote areas.

3.1.1 RAN3279 Benefits End-user benefits This feature can partially eliminate end-user impacts at some point when high latency satellite transport is in use. Operator benefits This feature benefits the operator from transport network maintenance, cost optimization, and for remotely located RNCs that are connected to the Core Network via satellite connections.

3.1.2 RAN3279 Functional description The RAN3279: IP Based Iu-interfaces via satellite feature supports two main use cases: • •

satellite-based Iu and Iub interfaces satellite-based Iu interfaces, while Iub is implemented through fiber or microwave radio

Satellite connections with up to 1000ms transport latency (Round-trip delay time or RTT), and up to 60ms jitter will be supported. Inter-system handovers are also supported.

g

Issue: 01A DRAFT

Note: Expect potential quality degradation if higher delay or jitter increases.

DN09232117

79


Figure 12


IP based Iu-interfaces via satellite links

DRAFT VERSION

Satellite

IuInterfaces

RNC

SMLC

SGSN MGW

In using satellites, the Iu transmission delay increases dramatically compared to normal Iu. The delay of a geostationary satellite hop is approximately 240-280ms. Therefore, RTT from RNC may be around 550-600ms.

3.1.3 RAN3279 System impact RAN3279: IP Based Iu-Interfaces via Satellite impact on features and system performance and capacity. Interdependencies between features • • •

g

RAN164: Satellite Iub Narrow and wide-band AMR Inter-system handovers Note: RAN3279: IP Based Iu-interfaces via Satellite can work together with or without RAN164: Satellite Iub. Inter-system handovers can still work, but with some additional impacts to user plane interruption time.

Impact on interfaces This feature has no impact on interfaces. Impact on commands There are no commands related to this feature.

80

DN09232117

Issue: 01A DRAFT



Impact on network and network element management tools This feature has no impact on network management or network element management tools. Impact on system performance and capacity The end user perceived network performance will be impacted by the significant delay induced by the satellite link.

DRAFT VERSION

3.1.4 RAN3279 Reference data RAN3279: IP Based Iu-Interfaces via Satellite requirements, parameters, and sales information. Requirements Table 82

RAN3279 Software requirements

RAS

IPA-RNC

mcRNC



WCDMA17

RNC17

mcRNC17



OMS

NetAct

MSC

SGSN

MGW






Flexi Lite BTS Support not required UE Support not required

This feature requires no new or additional hardware. Alarms There are no new alarms related to this feature. BTS faults and reported alarms There are no BTS faults and reported alarms related to this feature. Commands There are no new commands related to this feature. Measurements and counters There are no existing measurements or counters related to this feature. Key performance indicators There are no KPIs related to this feature. Parameters Table 83

RAN3279 New parameter Full name

Satellite Iu Enabled

Issue: 01A DRAFT

Abbreviated name

SatelliteIuEnabled

DN09232117

Managed object IuCS

81


Table 84


RAN3279 Modified parameter Full name

RNC Options

Abbreviated name

RncOptions

Managed object RNC



DRAFT VERSION

BSW/ASW

82

-ASW

License control in network element -RNC LK

DN09232117

License control attributes Long term ON/OFF license

Issue: 01A DRAFT


Operability features

4 Operability features 4.1 RAN3277: CM Parameter Streamlining

DRAFT VERSION

Benefits, requirements, functionality, system impact, and reference data of the feature. The RAN3277: CM Parameter Streamlining feature introduces the organization of the configuration management parameters of the radio network elements (NEs). The following radio network parameter metadata is analyzed and, if necessary, updated to facilitate support of the NetAct Intelligent Feature Activation (IFA) application: related features, related parameters, related functions, and controlling license keys.

4.1.1 RAN3277 benefits The RAN3277: CM Parameter Streamlining feature provides the following benefits: • • •

The feature lessens the effort for troubleshooting because of the decreased probability of wrong parameter configuration. The operators can easily select a feature and able to see, modify, and provision all of the feature’s relevant and related configuration parameters for optimization purposes. This feature lessens the consumed time in setting feature parameters that resulted to faster deployment of RNW features.

4.1.2 RAN3277 functional description The RAN3277: CM Parameter Streamlining feature provides the parameter metadata that NetAct requires to allow the IFA functions. IFA is a NetAct application that facilitates the provisioning of features within the network, and the organization of a feature’s related parameters. The RAN3277: CM Parameter Streamlining feature introduces new object model metadata, and modifies the existing object model metadata. The following are the parameter metadata that are used for the RAN3277: CM Parameter Streamlining feature: • • • • •

Related features Related parameters Description of Parameter Relationships Related Functions Controlling License Keys

Related features The Related features parameter metadata identifies the features with which a parameter is associated. A single parameter may be related to one or more RAN features, and thus, be considered a feature parameter for one or more features. Feature parameters are used to identify the set of parameters that are: •

Issue: 01A DRAFT

used to configure the feature

DN09232117

83



• • •

DRAFT VERSION

g

required for the proper operation of the feature introduced by the feature modified by the feature Note: The parameter modifications are identified by a related feature only if the modifications are associated with changes to the functional aspects of the parameter such as: changes to a parameter's range; or the addition of enumerator values to an enumeration parameter. The features that change the non-functional aspects of a parameter, such as its categorization, are not identified in the related features' metadata.

Related functions The Related functions parameter metadata identifies the functional grouping of parameters (FGPs) to which a parameter belongs. A single parameter may belong to one or more FGPs. Each FGP has both a main group identifier and an optional subgroup identifier. Related parameter The Related parameters parameter metadata identifies parameters that are related to one another, particularly for the purpose of defining parameter constraints recognized as consistency check is executed during the configuration plan. The following are examples of parameter constraints that indicate a relationship between parameters: • • • • • • • •

The value of a parameter depends on the value of another related parameter. A parameter's value range depends on the value of another related parameter. A parameter's default value depends on the value of another related parameter. The multiplicity of a parameter depends on the value of another related parameter. A parameter's value is calculated based on the value of another related parameter. A parameter is considered mandatory (that is, a value must be supplied during object creation) based on the value of another related parameter. A parameter must not be configured based on the value of another related parameter. A parameter's value is composed from the value of other related parameters.

Description of parameter relationships The Description of Parameter Relationships parameter metadata provides an operatorvisible description of the relationship between parameters. This information is used to formulate the object model constraints that are verified during configuration plan validation. Controlling license keys The Controlling license keys parameter metadata indicates any license keys that are required to be in place in order for a particular parameter value to be read or modified. This metadata is formulated as a logical expression that can make use of logical operators (such as AND and OR operations) and groupings (using the parenthesis). If the Controlling license key expression evaluates to false, the associated parameter's value is not uploaded by the NE to the management system. Additionally, the parameter's value cannot be modified by the operator.

84

DN09232117

Issue: 01A DRAFT



4.1.3 RAN3277 system impact RAN3277: CM Parameter Streamlining impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3277: CM Parameter Streamlining feature and any other feature.

DRAFT VERSION

Impact on interfaces The RAN3277: CM Parameter Streamlining feature provides additional parameter metadata for WCDMA network elements. Impact on network management tools The RAN3277: CM Parameter Streamlining feature has no impact on network management tools. Impact on system performance and capacity The RAN3277: CM Parameter Streamlining feature has no impact on system performance or capacity.

4.1.4 RAN3277 reference data The RAN3277: CM Parameter Streamlining feature requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 86 RAS

WCDMA 17

OMS Support not required

RAN3277 hardware and software requirements IPA-RNC

mcRNC

RNC17

mcRNC17

NetAct

MSC

NetAct 17


Flexi Multiradio BTS Support not required SGSN Support not required

Flexi Multiradio 10 BTS Support not required MGW Support not required

Flexi Lite BTS Support not required UE Support not required

Alarms There are no alarms related to the RAN3277: CM Parameter Streamlining feature. Commands There are no commands related to the RAN3277: CM Parameter Streamlining feature. Measurements and counters There are no measurements or counters related to the RAN3277: CM Parameter Streamlining feature. Key performance indicators There are no key performance indicators related to the RAN3277: CM Parameter Streamlining feature.

Issue: 01A DRAFT

DN09232117

85



Parameters There are no control parameters related to the RAN3277: CM Parameter Streamlining feature. Sales information Table 87



License control

DRAFT VERSION

Basic Software (BSW)

Yes

4.2 RAN3157: mcRNC System diagnostic report The RAN3157: mcRNC System Diagnostic Report feature provides summary information on overall system status of Multicontroller RNC (mcRNC) with a single command. This allows, faster troubleshooting of ongoing problems as well as providing early warning signs of potential problems.

4.2.1 RAN3157 Benefits The RAN3157: mcRNC System Diagnostic Report feature provides the following benefits: • • •

Faster and easier troubleshooting Behavior prognosis basing on signs of potential problems Simplified log collection

4.2.2 RAN3157 Functional description The RAN3157: mcRNC System Diagnostic Report feature allows to check the system health and performance status by running a single command. As shown in mcRNC System Diagnostic Report Overview, a report contains a summary on various areas of mcRNC, including the following: • • • • • • • • • • •

86

-

Activated by default

System Diagnostic Report header Software Diagnostic Report Hardware Diagnostic Report Resource Diagnostic Report Alarm Diagnostic Report Monitoring status Diagnostic Report Transport connectivity Diagnostic Report Networking Diagnostic Report The Operation and Management Unit (OMU) and Operation and Management Server (OMS) status Diagnostic Report Signaling Diagnostic Report Startup Diagnostic Report

DN09232117

Issue: 01A DRAFT


Figure 13


mcRNC System Diagnostic Report Overview

DRAFT VERSION

Systemdiagnosticreport

SCLI

·Systemdiagnosticreportheader ·Softwarediagnosticreport ·Hardwarediagnosticreport ·Resourcediagnosticreport ·Alarmdiagnosticreport ·Monitoringstatusdiagnosticreport ·Transportconnectivitydiagnostic report ·Networkingdiagnosticreport ·OMUandOMSstatusdiagnostic report ·Signalingdiagnosticreport ·Startupdiagnosticreport

mcRNC

A system-diagnostic report is generated in about 3 minutes. The SCLI command displays the summary file on the screen in real time and saves the complete report on the mcRNC hard disk as shown in mcRNC System Diagnostic Report Figure 14

mcRNC System Diagnostic Report Summaryreportsavedtodisk (TXT andXML formats) Example:/mnt/backup/sysdiag

RAN3157SCLIuser:invoke

>startsystem-diagnostics RAN3157SCLI

Realtimeprogresstoscreen

SWdiagnostic

HWdiagnostic

Resource...

...

mcRNC

The System Diagnostic SCLI command is integrated into a group-RNC plug-in of the RAN2601: mcRNC Symptom Report, making the System Diagnostic Report a part of mandatory data required for every problem reported to Nokia.

4.2.3 RAN3157 System impact Interdependencies between features There are no interdependencies between the RAN3157: mcRNC System Diagnostic Report feature and any other feature. Impact on interfaces The RAN3157: mcRNC System Diagnostic Report feature has no impact on interfaces.

Issue: 01A DRAFT

DN09232117

87



Impact on network management tools The RAN3157: mcRNC System Diagnostic Report feature has no impact on network management tools. Impact on system performance and capacity The RAN3157: mcRNC System Diagnostic Report feature has no impact on system performance or capacity.

4.2.4 RAN3157 Reference data

DRAFT VERSION

Requirements Table 88

RAN3157: mcRNC System Diagnostic Report hardware and software requirements

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA17


mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE







Alarms This information will be provided in further deliveries. BTS faults and reported alarms There are no faults related to the RAN3157: mcRNC System Diagnostic Report feature. Commands Table 89

New SCLI command introduced by RAN3157 Command name

Optional parameters Default value of timeout parameter is 5 minutes and its range can be set from 3 to 10 minutes.

start system-diagnostics [timeout]

Table 90

New SCLI command introduced by RAN3157 Command name

show system-diagnostics

Measurements and counters There are no measurements or counters related to the RAN3157: mcRNC System Diagnostic Report feature. Key performance indicators There are no key performance indicators related to the RAN3157: mcRNC System Diagnostic Report feature.

88

DN09232117

Issue: 01A DRAFT



Parameters There are no parameters related to the RAN3157: mcRNC System Diagnostic Report feature. Sales information Table 91



License control

DRAFT VERSION

BSW

4.2.4.1

RAN


RAN3157 Description of diagnostic items in the system diagnostic report Software diagnostic report Table 92

RAN3157 description of software diagnostic group Header

Text

Measurement interval

Active software version

Status is shown as OK if the active software version is running in all units, otherwise nodes on which there is a mismatch are printed.

Instantaneous

Software on-top patches

Patches installed on top of the installed software are printed.

Instantaneous

DMX clients messages and buffer queue

Not functioning Linux based Instantaneous program blocks (PRB) (or responding so slowly that clients give up and stop waiting before they get responses) are printed on each node. Detection is made based on whether the oldest message has been in the message queue for more than 5 seconds (TE value).

Licences validity

Validity is printed as NOK if there are capacity licenses where used capacity >= 80

Instantaneous

Software crashes

Software crashes from the last 24 hours are reported by checking /srv/Log/crash for "*core.gz" files.

From the last 24 hours

Hardware diagnostic report Table 93

RAN3157 description of hardware diagnostic group Header

Hard disk health

Issue: 01A DRAFT

Text


Smartctl toolchecks history of disk health checks. If there have not been any self-tests done in history, then a short disk check is initiated. Since the normal disk check lasts for

From previous health checks if available

DN09232117

89



Table 93

RAN3157 description of hardware diagnostic group (Cont.) Header

Text


~ 7 minutes based on I/O load, the output of the disk check is used only when the next round of System Diagnostics report is initiated.

DRAFT VERSION

Temperatures

90

Hard disk and AMC sensor temperatures on CFPU-0 and CFPU-1 are checked. Disaster Recovery Disk is covered as well. Smartctl and ipmitool commands are used.

Instantaneous

1. NOK is shown for smartctl command, if Current Drive Temperature > Drive Trip - 5. Therefore, the warning is indicated before the drive actually trips, due to increased temperature. 2. For ipmitool command, rows having Measuring = degrees C are checked and shown as NOK if the Reading + 5 is bigger than > UNC (Upper Non Critical). Add-in cards

HAS states of all units are checked. If operational status does not equal ENABLED or usage does not equal ACTIVE, NOK is shown along with the unit name.

Instantaneous

Resource diagnostic report Table 94

RAN3157 description of resource diagnostic report group Header

Text


Linux nodes CPU load average

The CPU load is not the same as CPU Load average over the last utilization. The load is basically an 1,5 and 15 minutes indicator of how many processes are waiting to be executed. As long as the load is less than the number of CPU cores, the status shall be shown as OK. If it gets above, it means that the system is not able to cope with its workload at "real time". Thus, some processes need to wait to get CPU time (or IO access).

Linux nodes CPU utilization

1. This is the percentage of processor time being used. Top command is executed on each node at 5 second intervals for a span of 1 minute. CPU utilization

DN09232117

From execution at 5 second intervals for a span of 1 minute

Issue: 01A DRAFT


Table 94


RAN3157 description of resource diagnostic report group (Cont.)

DRAFT VERSION

Header

Text


values are compared at the end of 1 minute. 2. If all the samples record more than 75%, node name and NOK is shown, and the reason is shown as CPU utilization being constantly bigger than 75% over a span of 1 minute. 3. The average, maximum and minimum values for each node are shown. User Plane application CPU load

1. Only the User Plane CPU load in

Instantaneous

Memory usage on Linux nodes

Status is marked NOK if occupied memory on any linux node is more than75%.

Instantaneous

Memory usage on SE(CSUP) nodes

1. Only applicable for CSUP. 2. Status is shown as NOK alarm if

Instantaneous

percentage from User Plane applications point of view is given here as that for UMW/PAL is not necessary. 2. CPU load of 90% and above is shown as NOK as beyond this point, User Plane has packet drop mechanism for different traffic types. 3. If reported as NOK, the exact number of channels present in each of the UP application servers is printed.

alarm 3870 (upmem_above_highest_wate rmrk_a) is active. Disk space usage

1. Both CFPUs are considered 2. WARNING status is indicated if :

Instantaneous

a) available space of state volume is lesser than 200 MB.

b) available space of backup volume is lesser than 8GB alarm 70158 is active. LMP RAM disk utilization

1. Each LMP is checked. 2. NOK is indicated as status, along

Instantaneous

with the reason, if any of these checks fail:

a) There has to be more than 300MB free RAM space in all the LMPs. b) The use ratio of NOR Flash /dev/mtdblock1 file

Issue: 01A DRAFT

DN09232117

91



Table 94

RAN3157 description of resource diagnostic report group (Cont.) Header

Text


DRAFT VERSION

system does not exceed 83% in any LMP. c) There must be a minimum free space of 7 MB available in the /tmp folder of every LMP. State of nodes and recovery groups

1. Node Status is shown as NOK if

Functional units

1. NOK is printed if there is some unit

Instantaneous

in SE-OU state (SE-OU* state is acceptable). 2. SE-OU (Separated, Out of use) means that unit is not available for automatic recovery actions. 3. SE-OU* = unit is available for taking over the active role in case of switchover.

Alarm diagnostic report Table 95

RAN3157 description of alarm diagnostic report group Header

Text

Active alarms


Active alarms are sorted based Instantaneous on severity. More severe alarms are shown first.

Signaling diagnostic report Table 96

RAN3157 decription of signaling diagnostic report group Header

Local and Remote SCCP SubSystem

92

Instantaneous

Nodes in configuration != Unlocked nodes. 2. RG Status is shown as NOK if RGs in configuration != Unlocked RGs. 3. RG unit balance on EIPU is checked. If active RU instance of both RGs of same type remain in one node (processing unit) while both of the standby RU instances remain in the other node, RG imbalance warning is shown.

Text

1. Local, remote

Measurement interval Instantaneous

SCCP_SubSystem_Id, SCCP_SubSystem, SCCP_SubSystem_numb er, and SCCP_SubSystem_status es are checked 2. If a local_SCCP_SubSyste m_status != CONFIGURED, REGISTERED, or

DN09232117

Issue: 01A DRAFT


Table 96


RAN3157 decription of signaling diagnostic report group (Cont.) Header

Text


ALLOWED, the status is shown as NOK. 3. If a remote_SCCP_SubSyste m_status != CONFIGURED, ALLOWED, the status is shown as NOK.

DRAFT VERSION

M3UA association

Issue: 01A DRAFT

1. M3UA_association_id,

Instantaneous

local_as_name, local_ip_addr, association_status are checked. 2. If M3UA_association_status != asp_state_active, the status is shown as NOK. 3. If admin state != enabled, the status is shown as NOK. M3UA local and remote application servers

1. M3UA local and remote id, Instantaneous

SCCP connections info, traffic distribution and Load status per QNIU

1. Checks that traffic is

SCCP Subsystem <-> Signaling Point Code mapping and state

Signaling Point Codes (SPC) mapped to RANAP and RNSAP has one of the states: unavailable, available, prohibited and allowed. The state is printed.

name, traffic mode, routing-context and network-appearance in outgoing messages are checked. 2. If M3UA_LOCAL_traffic_mo de != loadshare, the status is shown as NOK. Same is applicable to Remote traffic mode as well. Instantaneous

distributed equally. If any QNIU has All value 50% higher than average, the Traffic distribution status for that QNIU is marked as NOK. 2. If the value of All for any QNIU (total number of SCCP connections = total number of active calls) exceeds 80% of the Max value, the Load status for that QNIU is marked as NOK.

DN09232117

Instantaneous

93



Startup diagnostic report Table 97

RAN3157 decription of startup diagnostic report group Header

Text

DRAFT VERSION

Latest RNC (cluster) and unit restarts

1. Latest 3 RNC (cluster)

Measurement interval Latest (from history)

restarts are shown with timestamps. 2. Only the last 20 unit restarts are shown. They are sorted by end time, with the most recent ones at the beginning.

4.3 RAN3058: Online management of Antenna Line Devices (RET) Benefits, functionality, system impact, reference data of the feature The RAN3058: Online management of Antenna Line Devices (RET) feature enables the operator to assign RET units to Antenna Line Device ports and commission them without taking the site off air.

4.3.1 RAN3058 benefits The RAN3058: Online management of Antenna Line Devices (RET) feature provides the following benefits: • • • •

New RET unit commissioning without BTS restart RET unit full online reconfiguration: antenna line assignment can be performed without taking the site off air Avoidance of unnecessary site outages End-user and customer satisfaction improvement when maintaining or adding new RET units

4.3.2 RAN3058 functional description RAN3058 enables the reduction of BTS resets when performing RET operations. When plugging in the new RET unit, the scope of required shutdown or reset operations can be limited to one or several antenna lines, instead of the whole BTS. This enables the site to remain on air. RAN3058 is an improvement to RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support.

4.3.3 RAN3058 system impact RAN3058: Online management of Antenna Line Devices (RET) has no impact on features, interfaces, network management tools, and system performance and capacity Interdependencies between features

94

DN09232117

Issue: 01A DRAFT



There are no interdependencies between the RAN3058: Online management of Antenna Line Devices (RET) feature and any other feature. Impact on interfaces The RAN3058: Online management of Antenna Line Devices (RET) feature has no impact on interfaces. Impact on network management tools The RAN3058: Online management of Antenna Line Devices (RET) feature has no impact on network management tools. Impact on system performance and capacity

DRAFT VERSION

The RAN3058: Online management of Antenna Line Devices (RET) feature has no impact on system performance or capacity.

4.3.4 RAN3058 reference data RAN3058: Online management of Antenna Line Devices (RET) requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information Requirements Table 98

RAN3058: Online management of Antenna Line Devices (RET) hardware and software requirements

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA17



WBTS17

WBTS17

Not supported

OMS

NetAct

MSC

SGSN

MGW

UE


NetAct17





This feature requires a Rel.2 or Rel.3 System Module. Alarms There are no alarms related to the RAN3058: Online management of Antenna Line Devices (RET) feature. BTS faults and reported alarms There are no faults related to the RAN3058: Online management of Antenna Line Devices (RET) feature. Commands There are no commands related to the RAN3058: Online management of Antenna Line Devices (RET) feature. Measurements and counters There are no measurements or counters related to the RAN3058: Online management of Antenna Line Devices (RET) feature. Key performance indicators There are no key performance indicators related to the RAN3058: Online management of Antenna Line Devices (RET) feature. Parameters

Issue: 01A DRAFT

DN09232117

95



Table 99

Parameters modified by RAN3058: Online management of Antenna Line Devices (RET)

DRAFT VERSION

Full name

Abbreviated name

Managed object

Parent structure

Antenna line identifier antlIdList list

RET

-

Connection

connection

RET

-

Scanned antenna interface

scannedAntennaInt RET erface

-

For parameter descriptions, see Flexi Multiradio BTS WCDMA Parameters. Sales information Table 100

RAN3058: Online management of Antenna Line Devices (RET) sales information


License control


-


4.4 RAN2780: Remote Self Test for FSMF Benefits, functionality, system impact, reference data of the feature The RAN2780: Remote Self Test for FSMF feature allows: • • • •

initiating self tests via BTS Site Manager resetting the BTS when it is blocked and performing the necessary HW tests detecting the faulty unit and providing summary in GUI obtaining detailed information available in the troubleshooting snapshot

BTS Site Manager interface is modified and now supports the FSMF Remote Self Test triggering from BTS Site Manager and shows the test results.

4.4.1 RAN2780 benefits The RAN2780: Remote Self Test for FSMF feature provides the following benefits: • •

the test might be run remotely without visiting the site it provides better diagnosis between HW failures and SW failures

4.4.2 RAN2780 functional description BTS Site Manager The self test is initiated from the BTS Site Manager. During the self test procedure, the BTS is blocked and restarted with a self-test option. For procedure description, see Nokia BTS Site Manager Online Help for WCDMA 17.

96

DN09232117

Issue: 01A DRAFT



The test concerns modules and sub-modules of FSMF and it might also include extension modules. BTS Site Manager's tasks: • •

g

Note: The remote self test does not start when some tests are already ongoing. Active Test List contains a list of ongoing tests. •

DRAFT VERSION

Allows the user to execute a remote self test Shows a confirmation message that the BTS will reset and there will be no connection during the test

•

Informs the user about the running time of estimated tests (about 10 minutes) Allows for saving the test results

Figure 15

RAN2780 functional description

BTSSiteManager

SystemModule And Sub-modules

Result analysis In result the feature indicates the faulty HW for replacement to the Field Engineer. The test reports are available in detailed form in snapshot and might be viewed in BTS Site Manager later.

4.4.3 RAN2780 system impact RAN2780: Remote Self Test for FSMF impact on network management tools Interdependencies between features There are no interdependencies between the RAN2780: Remote Self Test for FSMF feature and any other feature. Impact on interfaces The RAN2780: Remote Self Test for FSMF feature has no impact on interfaces. Impact on network management tools The RAN2780: Remote Self Test for FSMF feature has no impact on network management tools. Impact on system performance and capacity The RAN2780: Remote Self Test for FSMF feature has no impact on system performance or capacity.

Issue: 01A DRAFT

DN09232117

97



4.4.4 RAN2780 reference data RAN2780: Remote Self Test for FSMF requirements and sales information Requirements

DRAFT VERSION

Table 101


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17



Not supported WBTS17

Not supported

OMS

NetAct

MSC

SGSN

MGW

UE







Alarms There are no alarms related to the RAN2780: Remote Self Test for FSMF feature. BTS faults and reported alarms There are no faults related to the RAN2780: Remote Self Test for FSMF feature. Commands There are no commands related to the RAN2780: Remote Self Test for FSMF feature. Measurements and counters There are no measurements or counters related to the RAN2780: Remote Self Test for FSMF feature. Key performance indicators There are no key performance indicators related to the RAN2780: Remote Self Test for FSMF feature. Parameters There are no parameters related to the RAN2780: Remote Self Test for FSMF feature. Sales information Table 102



License control -


4.5 RAN3156: RNC Troubleshooting Data Management by NetAct Benefits, functionality, system impact, reference data of the feature. The RAN3156: RNC Troubleshooting Data Management by NetAct feature improves the troubleshooting data collection framework for IPA-RNC and mcRNC. This framework was initially introduced by the RAN2229: Troubleshooting Data Management by NetAct feature for the purpose of IPA-RNC and mcRNC symptom data collection and control via NetAct.

98

DN09232117

Issue: 01A DRAFT



4.5.1 RAN3156 benefits The RAN3156: RNC Troubleshooting Data Management by NetAct feature provides the following benefits: • • •

Simplified symptom data collection from NetAct Faster and easier network troubleshooting Cost reduction for the operator

DRAFT VERSION

4.5.2 RAN3156 functional description The RAN3156: RNC Troubleshooting Data Management by NetAct feature provides enhancements for the following Network Elements: IPA-RNC • •

NetAct support for collecting symptom data of Basic as well as Standard profiles. Transferring the symptom data collected from IPA-RNC to NetAct, for a selected profile.

mcRNC • • •

Automatic symptom data upload to OMS. Troubleshooting Data management by NetAct. NetAct support for the RAN2601: Symptom Data Collection for mcRNC and Flexi Direct feature, allowing to take a symptom data snapshot of Basic as well as Standard profiles, from the NE.

To view the functionality of the RAN3156: RNC Troubleshooting Data Management by NetAct see: Figure 16: Overview of the RAN3156 RNC Troubleshooting Data Management by NetAct feature Figure 16

Overview of the RAN3156 RNC Troubleshooting Data Management by NetAct feature OMS

RAN3156

RAN3156

NetAct RAN2229

RAN2601 mcRNC RAN2872

Symptomdata

RAN1805

Manualeventtrigger

RAN2446 IPA-RNC

Issue: 01A DRAFT

DN09232117

99



4.5.3 RAN3156 system impact RAN3156: RNC Troubleshooting Data Management impact on features, interfaces, network management tools. Interdependencies between features The RAN3156: RNC Troubleshooting Data Management feature impacts the following features:

DRAFT VERSION

The RAN3156: RNC Troubleshooting Data Management feature is impacted by the following features: •

RAN2229 Troubleshooting Data Management by NetAct –

•

RAN1805 [IPA-]RNC Event Triggered Symptom Data Collection –

•

This feature introduces the Basic and Standard Troubleshooting Data profiles for the IPA-RNC. These profiles are then used by the RAN3156: RNC Troubleshooting Data Management feature for requesting the Troubleshooting Data from an IPA-RNC.

RAN2601 Symptom Data Collection for mcRNC and Flexi Direct –

•

This feature triggers the IPA-RNC Emergency Troubleshooting Data creation.

RAN2872 IPA-RNC Symptom Report –

•

This feature provides the functionality of Alarm-triggered IPA-RNC Troubleshooting Data creation.

RAN2446 Emergency Data Collection for IPA-RNC –

•

This feature allows the NetAct user to manually trigger the creation of Troubleshooting Data at the IPA-RNC, and to automatically upload the collected Troubleshooting Data to OMS, and further on to NetAct. After a successful upload to OMS, the Troubleshooting Data is then automatically deleted from the controller.

This feature introduces the functionality of creating a symptom report of the symptom data from the mcRNC.

RAN1873 OMS Troubleshooting Data Collection –

This feature allows to collect the OMS Troubleshooting data at a single location at OMS.

Impact on interfaces The RAN3156: RNC Troubleshooting Data Management feature impacts interfaces as follows: •

100

NWI3 interface

DN09232117

Issue: 01A DRAFT


–


The feature uses the existing NWI3 operations to support the automatic upload of Troubleshooting Data via NetAct, that becomes available at OMS. The NWI3 operations are also used to support a NetAct request to create Troubleshooting Data at an NE via OMS, and for the automatic upload of the NE Troubleshooting Data via OMS to NetAct.

Impact on network management tools The RAN3156: RNC Troubleshooting Data Management feature impacts network management tools as follows:

DRAFT VERSION

•

NetAct –

This feature enhances the NetAct troubleshooting data collection for IPA-RNC and mcRNC.

Impact on system performance and capacity The RAN3156: RNC Troubleshooting Data Management feature has no impact on system performance or capacity.

4.5.4 RAN3156 reference data The RAN3156: RNC Troubleshooting Data Management by NetAct requirements, alarms and sales information. Requirements Table 103

The RAN3156: RNC Troubleshooting Data Management by NetAct hardware and software requirements

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC 17

mcRNC 17




OMS

NetAct

MSC

SGSN

MGW

UE

OMS 17

NetAct 17





Alarms Table 104

Existing alarms related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature

Alarm ID 71106

Alarm name TROUBLESHOOTING DATA RECEIVED

For alarm descriptions see WCDMA OMS Alarms Commands There are no commands related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature. Measurements and counters

Issue: 01A DRAFT

DN09232117

101



There are no measurements or counters related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature. Key performance indicators There are no key performance indicators related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature. Parameters There are no parameters related to the RAN3156: RNC Troubleshooting Data Management by NetAct feature.

DRAFT VERSION


RAN3156: RNC Troubleshooting Data Management by NetAct sales information


License control


Not defined


4.6 RAN3396: WCDMA OMS Connectivity Change for Gen9 HW Benefits, functionality, system impact, reference data of the feature The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature extends the WCDMA OMS connectivity values for HP Proliant Gen9 (blade and rack-mounted) hardware in WCDMA 17.

4.6.1 RAN3396 benefits The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature reduces the number of OMSs needed, hence, smaller capex and opex.

4.6.2 RAN3396 functional description With RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature, the OMS connectivity values for HP ProLiant Gen9 (rack-mounted and blade) hardware can be increased. This feature increases parallel processing to get the maximum benefit from heavily increased number of CPU cores (and hyper-threading). The new target OMS connectivity values for Gen9 HW are (current values in brackets): •

HP ProLiant DL360 Gen9 (rack-mounted) – – –

•

HP ProLiant BL460c Gen9 (blade) –

102

15 min : 22 000 (7 500) 30 min : 30 000 (22 500) 60 min : 40 000 (30 000)

15 min : 15 000 (7 500)

DN09232117

Issue: 01A DRAFT


– –


30 min : 22 000 (15 000) 60 min : 30 000 (30 000)

4.6.3 RAN3396 system impact The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature impact on features, interfaces, network management tools, and system performance and capacity.

DRAFT VERSION

Interdependencies between features There are no interdependencies between the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature and any other feature. Impact on interfaces The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature has no impact on interfaces. Impact on network management tools The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature has no impact on network management tools. Impact on system performance and capacity The RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature has no impact on system performance or capacity.

4.6.4 RAN3396 reference data RAN3396: WCDMA OMS Connectivity Change for Gen9 requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 106

RAN3396: WCDMA OMS Connectivity Change for Gen9 HW hardware and software requirements

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17






OMS

NetAct

MSC

SGSN

MGW

UE

WCDMA OMS17






Alarms There are no alarms related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature. BTS faults and reported alarms There are no faults related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature.

Issue: 01A DRAFT

DN09232117

103



Commands There are no commands related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature. Measurements and counters There are no measurements or counters related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature. Key performance indicators

DRAFT VERSION

There are no key performance indicators related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature.

104

Parameters There are no parameters related to the RAN3396: WCDMA OMS Connectivity Change for Gen9 HW feature. Sales information Table 107

RAN3396: WCDMA OMS Connectivity Change for Gen9 HW sales information


License control -

DN09232117


Issue: 01A DRAFT


Performance monitoring features

5 Performance monitoring features 5.1 RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring

DRAFT VERSION

Benefits, requirements, functionality, system impact, and reference data. The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature introduces new software to support power metering function available with the new hardware to monitor the power consumption of the RF module.

5.1.1 RAN3248 benefits The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature enables the operators to monitor the power consumption from RF modules, and system modules, which enhanced power management and optimization of a particular site.


Issue: 01A DRAFT

The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature introduces a new hardware called power meter, which is embedded in the BTS hardware's RF module. The power meter is capable of measuring power consumption in DC voltage and amperage. New counters within the M5008 measurements are created that are based on the reports from the power meter in RFs and static values in system modules. Power reports and counters are viewed in the BTS site manager (BTSSM), while only counters are collected in NetAct. The power meter function is available in RF modules that have embedded power meter. Only static values are provided for system modules that do not have energy meter hardware. RAN3248 reporting mechanism Figure 17: RAN3248 reporting mechanism describes how the power consumption is reported and viewed in BTSSM and NetAct.

DN09232117

105


Figure 17


RAN3248 reporting mechanism

NetAct counters

DRAFT VERSION

OMS

RNC

BTSSM

Calculatedreport or/and counters

BTSOM OAM

Systemmodule Static values

Report or/and counters

RFmodule Power meter

Power meter A power meter is embedded in the RF modules, and it measures the power consumption in voltage (V) and amperage (A) of RF (with RRH) for every one-minute. The measured values are reported to the Operations, Administrations and Maintenance (OAM). The OAM uses these measured values to create counters and power reports to the BTSSM. OAM The OAM calculates the measured values reported by the power meter embedded in the RFs. The OAM sends the calculated counters in kilowatt-hour (kWh) to the BTSSM and to NetAct via RNC and OMS. The measured values are calculated separately by the OAM for system modules, and RFs, and the entire BTS. The OAM calculates the following counters:

106

DN09232117

Issue: 01A DRAFT


•

g

DRAFT VERSION

g

Energy consumption in all RFs: The OAM sums up the energy consumption in all radio modules (with RRH) with power meter on-board in the BTS over the whole measurement period duration. This is obtained by sampling with a predefined sampling period and summing the samples. Note: In case of RF sharing, the RF value is calculated only for the master RAT. At the same time, non-shared RFs are always reported to the RAT to which they belong.

g

Note: Measurements are done only for RFs which have power meter on-board. In case of having different RFs, (with and without power meter) in BTS, counter includes only the values from RFs with power meter. •

g

Energy consumption in all system modules: The OAM sums up the energy consumption in all system modules in the BTS over the whole measurement period duration. This is obtained by sampling with a predefined sampling period and summing the samples. Note: Static values are used for all FSM-r3 and FSM-r2 (in case of FSM-r3 + FSM-r2).

•

g


Energy consumption for the entire BTS: The OAM sums up the energy consumption in the entire BTS over the whole measurement period duration. This is obtained by sampling with a predefined sampling period and summing the samples. Note: In case of RF sharing, the RF value is calculated only for the master RAT. At the same time, non-shared RFs are always reported to the RAT to which they belong. Note: Measurements are done only for RFs which have power meter on-board. In case of having different RFs, (with and without power meter) in BTS, counter includes only the values from RFs with power meter. Static values are used for all FSM-r3 and FSM-r2 (in case of FSM-r3 + FSM-r2).

BTSSM The BTSSM receives the calculated power reports from the OAM, and displays the measured voltage (V) and power (W) of the RF modules. The power report is updated according to the new reports received from the OAM for each one minute with the information of the hardware. The first power consumption report is available when the BTS reaches the configuration state. NetAct NetAct also receives the counters from the OAM via RNC and OMS. Counters that are used for KPI report are stored and viewed in NetAct. Supported hardware This feature is applicable for RF modules with RRH that has the supported power meter hardware on board. The RF sharing is also supported by this feature. The reported values of shared RFs are displayed only in the master radio access technology (RAT).

Issue: 01A DRAFT

DN09232117

107



5.1.3 RAN3248 system impact RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature and any other feature.

DRAFT VERSION

Impact on interfaces The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature impacts interfaces as: •

•

•

BTS-RNC New counters within the M5008 measurement are transferred periodically between the BTS and the RNC. RNC-OMS New counters within the M5008 measurement are transferred periodically between the RNC and the OMS. OMS-NetAct New counters within the M5008 measurement are transferred periodically between the OMS and NetAct.

Impact on network and network element management tools The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature impacts network management tools as follows: •

•

BTSSM: A new power report and counters are generated to the BTSSM. The power report consists of voltage (V) and power (W) of the RF modules and the counters show the power consumption in kWh of all SMs, all RF modules and the whole BTS. NetAct: New counters are received by NetAct.

Impact on system performance and capacity The RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature has no impact on the system performance and capacity.

5.1.4 RAN3248 reference data RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring requirements, alarms and faults, measurements and counters, parameters, and sales information. Requirements Table 108 RAS

WCDMA 17

108

RAN3248 Software requirements IPA-RNC

mcRNC



DN09232117

Flexi Multiradio BTS Support not required

Flexi Multiradio 10 BTS WBTS17


Issue: 01A DRAFT


Table 108


RAN3248 Software requirements (Cont.)

OMS

NetAct

WCDMA OMS17

MSC

NetAct 17


SGSN Support not required

MGW Support not required

UE Support not required

This feature requires System module release 3.

g

Note: Only the static value of the energy consumption is used for system module release 3.

DRAFT VERSION

Alarms Table 109

Existing alarms related to RAN3248 Alarm ID

Alarm name

7660


7661


Commands There are no commands related to the RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. Measurements and counters Table 110


Counter ID

g

Counter name

Measurement

M5008C51

ENERGY CONSUMPTION IN SYSTEM MODULES

WBTS level monitoring

M5008C52

ENERGY CONSUMPTION IN RADIO MODULES


M5008C53

ENERGY CONSUMPTION IN ENTIRE BTS


Note: Counter values are calculated based on the measurements from RF modules which have power meter. Key performace indicators There are no key performance indicators related to the RAN3248: BTS Embedded Power Meter for Energy Efficiency Monitoring feature. Parameters Table 111

New parameters related to RAN3248 Full name

Power Meter enabled

Abbreviated name

powerMeterEnabled

Managed object BTSSCW

Sales information

Issue: 01A DRAFT

DN09232117

109


Table 112




License control


BTS license key (LK)


5.2 RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA

DRAFT VERSION

Benefits, requirements, functionality, system impact, and reference data of the feature. The RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature provides new multi-operator core network (MOCN) counters for WCDMA to show the performance of the MOCN that works with the shared radio access network (RAN) such as the radio network controller (RNC).

5.2.1 RAN2777 benefits The RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature provides the following benefits: • •

The operator can identify the possible problems in the MOCN environment that are related to the unusual behavior of the core networks (CNs). Minimal efforts in troubleshooting are needed for the operator to investigate end-user problems that occur in the MOCN environment.

5.2.2 RAN2777 functional description An MOCN refers to a network configuration in which the operators have their own CNs but share a RAN as illustrated in Figure 18: MOCN NEs topology. Figure 18

MOCN NEs topology

CNx

CN2

CN1

RNC

UE BTS

110

DN09232117

Issue: 01A DRAFT



The RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature introduces new MOCN counters for WCDMA that indicates the performance of the MOCN that has shared RNC. This feature also monitors possible problems that a user equipment (UE) might experience when connecting to the CNs. The RNC provides counters to measure the following: • •

DRAFT VERSION

• • • • • • • • • • • • • • • • • • • •

Issue: 01A DRAFT

The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error PLMN not allowed. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error location area not allowed. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error roaming not allowed in this location area. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error GPRS services not allowed in this PLMN. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error no suitable cells in location area. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error network failure. The number of attach/location update/routing area update rejects received by the RNC from the CN due to the error CS/PS coordination required. The number of attach/location update/routing area update rejects received by the RNC from the CN due to other error codes. The number of attach/location update/routing area update rejects sent to the UE due to the error PLMN not allowed. The number of attach/location update/routing area update rejects sent from the RNC to the UE due to the error location area not allowed. The number of attach/location update/routing area update rejects sent from the RNC to the UE due to the error roaming not allowed in this location area. The number of attach/location update/routing area update rejects sent from the RNC to the UE due to the error GPRS services not allowed in this PLMN. The number of attach/location update/routing area update rejects sent to the UE due to the error no suitable cells in location area. The number of attach/location update/routing area update rejects sent from the RNC to the UE due to the error network failure. The number of attach/location update/routing area update rejects sent to the UE due to other error codes. The number of Iu connection setup with redirect attempt flags sent from the RNC to the CN. The number of IMSI requests received by the RNC from the CN. The number of Iu connection setup routed on the NRI based on the (P)TMSI. The number of Iu connection requests sent to the CN when IMSI is used to select CN node. The number of Iu connection requests sent to the CN node which is selected by the supporting UE. The number of Iu connection setup with redirection completed indication received by the RNC from the CN. The number of attach/location update/routing area update requests with redirection indication received by the RNC from the CN.

DN09232117

111



5.2.3 RAN2777 system impact Interdependencies between features There are no interdependencies between the RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature and any other feature. Impact on interfaces The RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature has no impact on interfaces.

DRAFT VERSION

Impact on system performance and capacity The RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature has no impact on system performance or capacity.

5.2.4 RAN2777 reference data RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA requirements, measurement and counters, and sales information. Requirements Table 113

Software requirements

RAS

IPA-RNC

WCDMA 17

OMS WCDMA OMS17

RNC17

mcRNC

mcRNC17

NetAct NetAct 17

MSC Support not required

Flexi Multiradio BTS Support not required SGSN Support not required

Flexi Multiradio 10 BTS Support not required MGW

Flexi Lite BTS Support not required UE



Alarms There are no alarms related to the RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature. Commands There are no commands related to the RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature. Measurements and counters Table 114

New counters introduced by RAN2777 Counter ID

112

Counter name

Measurement

M1003C62

ATTACH REQUEST REJECTED BY CN DUE TO PLMN NOT ALLOWED

1003 - L3 signaling at Iu (RNC)

M1003C63

ATTACH REQUEST REJECTED BY CN DUE TO LA NOT ALLOWED


DN09232117

Issue: 01A DRAFT


Table 114


DRAFT VERSION

Counter ID

Issue: 01A DRAFT


Counter name

Measurement

M1003C64

ATTACH REQUEST REJECTED BY CN DUE TO ROAMING NOT ALLOWED


M1003C65

ATTACH REQUEST REJECTED BY CN DUE TO GPRS NOT ALLOWED


M1003C66

ATTACH REQUEST REJECTED BY CN DUE TO NO SUITABLE CELLS IN LA


M1003C67

ATTACH REQUEST REJECTED BY CN DUE TO NETWORK FAILURE


M1003C68

ATTACH REQUEST REJECTED BY CN DUE TO COORDINATION


M1003C69

ATTACH REQUEST REJECTED BY CN DUE TO OTHER ERRORS


M1003C70

ATTACH REQUEST REJECTED BY RNC DUE TO PLMN NOT ALLOWED


M1003C71

ATTACH REQUEST REJECTED BY RNC DUE TO LA NOT ALLOWED


M1003C72

ATTACH REQUEST REJECTED BY RNC DUE TO ROAMING NOT ALLOWED


M1003C73

ATTACH REQUEST REJECTED BY RNC DUE TO GPRS NOT ALLOWED


M1003C74

ATTACH REQUEST REJECTED BY RNC DUE TO NO SUITABLE CELLS IN LA


M1003C75

ATTACH REQUEST REJECTED BY RNC DUE TO NETWORK FAILURE


M1003C76

ATTACH REQUEST REJECTED BY RNC DUE TO OTHER ERRORS


M1003C77

IU CONNECTION WITH REDIRECT FLAG


M1003C78

IU IMSI REQUESTS


M1003C79

IU CONNECTION ROUNTED ON NRI


M1003C80

IU CONNECTION ROUNTED ON IMSI


DN09232117

113


Table 114


New counters introduced by RAN2777 (Cont.) Counter ID

Counter name

Measurement

M1003C81

IU CONNECTION ROUNTED ON IUO


M1003C82

REDIRECTION COMPLETE NUMBER


M1003C83

RECEIVED IU CONNECTION REQ WITH REDIRECTION INDICATION


DRAFT VERSION

Key performance indicators There are no key performance indicators related to the RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature. Parameters There are no parameters related to the RAN2777: Iu-PS and Iu-CS MOCN counters for WCDMA feature. Sales information Table 115



License control

Basic software (BSW)

-


5.3 RAN2861: UE Tracing Support in BTS Benefits, requirements, functionality, system impact, and reference data of the feature. The RAN2861: UE Tracing Support in BTS feature allows operators to capture and analyze traces from BTS for a particular international mobile subscriber indentity (IMSI).

5.3.1 RAN2861 benefits The RAN2861: UE Tracing Support in BTS feature provides the following benefits: • • •

faster troubleshooting of subscribers' complains remote data collection avoiding the need for BTS site visit comprehensive data content for individual monitored calls

5.3.2 RAN2861 functional description Operators often need call trace to further investigate the problems experienced by subscribers or during drive tests. Faster retrieval of call logs speeds up root cause analysis, which, in turn, allows operators to address the problem quickly. The RAN2861: UE Tracing Support in BTS feature supports remote collection and graphical analysis of call traces for a specific IMSI number from BTSs in the operator's network.

114

DN09232117

Issue: 01A DRAFT



The BTS call trace data includes the following: •

control plane – – –

•

user plane – –

DRAFT VERSION

– – •

NBAP messages BTSOM - TCOM interface messages TCOM - DSP interface messages

HSUPA L2 TTI trace Mac-hs TTI trace Rake TTI trace Codec TTI trace

internal messaging

This feature provides an extension of the RAN2930: IMSI-based Call Monitoring and RAN2973: Enhanced IMSI Based Call Monitoring RNC features into the BTS. This also enables end-to-end WCDMA IMSI-based call monitoring solutions from the BTS and RNC logs. Figure 19: IMSI-based call monitoring feature architecture shows the architecture of the existing IMSI-based call monitoring and the new RAN2861: UE Tracing Support in BTS feature. Figure 19

IMSI-based call monitoring feature architecture

Datacollectorand analyzer IMSI list

BTSIMSIbased monitoreddata: (RAN2861) -controlplane -userplane -internalmessaging

PS/CScore

RNC RNC

TraceUE capabilityindicator

BTS

BTS

UE

Issue: 01A DRAFT

RNCIMSIbased monitoreddata: (RAN2930andRAN2973) -controlplane -userplane -transportplane -internalmessaging

DN09232117

UE

115



All logs are collected in the Layer3 Data Collector (L3DC), which is Megaplexer (L3DC) tool for the BTS, and Megamon (L3DC) tool for the RNC. The monitored data is retrieved and analyzed in IMSImon3G. For more information, see TSS IMSIMon3G solution description in NOLS. The RAN2861: UE Tracing Support in BTS feature requires the license activation of the RAN2930: IMSI-based Call Monitoring and RAN2973: Enhanced IMSI Based Call Monitoring features. For more information, see the following documents: •

DRAFT VERSION

•

RAN2930: IMSI-based Call Monitoring RAN2973: Enhanced IMSI Based Call Monitoring

The Megaplexer (L3DC) tool must be configured first in the BTS. Operators must configure the Megaplexer's IP address, port number, and trace contents using the BTS site manager (BTSSM). For more information, see Activating RAN2861: UE Tracing Support in BTS. The BTS sends the capability indication message to the RNC. The capability indication is determined in the BTS based on the parameters received from the BTSOM. The RNC receives the message and the call trace information is included once tracing is started in Megamon (L3DC) tool. The call trace information includes the radio link (RL) setup request or RL reconfiguration prepare message. The information in the RL message indicates the particular IMSI to be traced. The particular IMSI must be configured in Megamon (L3DC) tool to be able to trace. The list of IMSIs to be traced must be configured in the L3DC/Megamon tool. The configuration procedure is included in Activating RAN2930: IMSI-based Call Monitoring. The operator can analyze the collected call logs through the L3DA/Emil tool. The call logs are retrieved from the data collector and are decoded through the L3DA/Emil tool. For more information, see L3DA/Emil tool product description in NOLS. Active alarms are seen in NetAct when the connections between L3DC and the BTS are interrupted. The BTS sets the 7652 BASE STATION NOTIFICATION alarm if the following scenarios are encountered: • •

L3DC is faulty. Transmission Control Protocol (TCP) connection is interrupted.

The L3DA/Emil tool user is informed by a message in case that L3DA/Emil tool is unable to receive data from the L3DC during the retrieval of the call logs. The BTS stops the UE log tracing in the following scenarios: • • • • • • •

The last radio link of the specific UE is deleted. The radio link reconfiguration prepare message is received with call trace information filled with a Disabled value. The reset request procedure message is triggered from the RNC. The Iub link is disconnected. A cell with an enabled Trace UE is deleted. The BTS hardware is reset. The TCP connection with the Megaplexer is interrupted.

Table 116: NE and tool tracing capacities shows the network element (NE) or tools and their corresponding tracing capabilities:

116

DN09232117

Issue: 01A DRAFT


Table 116


NE and tool tracing capacities NE/tool

Capacity

1 BTS

1 UE trace

1 RNC

At least 16 simultaneous UE traces

1 L3DC

Megamon (L3DC) tool: 1 RNC Megaplexer (L3DC) tool: 1 RNC

DRAFT VERSION

The operators can view each BTS that L3DC is serving through NetAct Configurator. The RAN2861: UE Tracing Support in BTS feature introduces new parameters such as: •

•

•

•

UE Tracing L3DC Connection Details (ueTracingL3dcConnectionDetails): This parameter defines the IP address and TCP port of the L3DC (Data Collection) entity for UE tracing. When setting a valid IP address and TCP port, the UE tracing is activated for the specific UE. UE Tracing L3DC IP address (ueTracingL3dcIpAddress): This parameter defines the IP address of the L3DC (Data Collection) entity for UE tracing. UE Tracing L3DC TCP port (ueTracingL3dcConnectionDetails): This parameter defines the TCP port of the L3DC (Data Collection) entity for UE tracing. UE Tracing trace type (ueTraceType): This parameter defines the types of the traced log.

5.3.3 RAN2861 system impact The RAN2861: UE Tracing Support in BTS feature impact on features, and interfaces. Interdependencies between features The RAN2973: Enhanced IMSI Based Call Monitoring feature must be activated before configuring the RAN2861: UE Tracing Support in BTS feature. Impact on interfaces The RAN2861: UE Tracing Support in BTS feature impacts interfaces as follows: •

g

BTS and RNC: The BTS sends the tracing capability information message to the RNC if the trace type is defined, and the Megaplexer (L3DC) tool IP address and port number are configured at the BTS and the BTS SW is WBTS17 and beyond. Note: The BTS TCP connection and the Megaplexer is successfully established.

•

•

BTS and L3DC/Megaplexer: A cell trace interface from the BTS to the L3DC/Megaplexer tool is introduced for the transferring of logs. RNC and L3DC/Megamon: An existing interface from the RNC towards L3DC/Megamon is still used.

Impact on network management tools

Issue: 01A DRAFT

DN09232117

117



The RAN2861: UE Tracing Support in BTS feature impacts the BTS site manager (BTSSM). A new BTS monitoring parameter must be enabled using the BTSSM, and the following data needs to be configured: • • •

IP address of Megaplexer tool Port number of Megaplexer tool Trace contents

Impact on system performance and capacity

DRAFT VERSION

The RAN2861: UE Tracing Support in BTS feature has the following capacity considerations: • • •

g

Trace parameters are filtered and traffic rate less than 25 kbps is preferred. M-Plane bandwidth with 1000 kbps is mandatory to enable the feature. Only one trace type is allowed to enable at a time. Note: Enabling all trace types can cause data dropped.

5.3.4 RAN2861 reference data RAN2861: UE Tracing Support in BTS feature requirements, alarms and faults, parameters, and sales information. Requirements Table 117

Software requirements

RAS

IPA-RNC

WCDMA 17

RNC17

OMS

NetAct



mcRNC

mcRNC17

WBTS17

MSC

SGSN



Flexi Multiradio 10 BTS WBTS17


MGW

UE



Hardware • •

FSME FSMF

Table 118

External monitoring tool Tool name

118


Purpose

Location

L3DC/Megamon

For collecting the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Data Collector (Megamon)

L3DC/Megaplexer

For collecting the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access

DN09232117

Issue: 01A DRAFT


Table 118


External monitoring tool (Cont.) Tool name

Purpose

Location Network Tools → L3 Data Collector (Megaplexer)

L3DA/Emil

For decoding the monitored data

From NOLS: Care → Software Supply Tool → Product Related Tools / Radio Access Network Tools → L3 Analyzer/Viewer (Emil)

DRAFT VERSION

BTS faults and reported alarms Table 119

New BTS faults introduced by RAN2861

Fault ID

Fault name

Reported alarm Alarm ID

168

Failure in connection between WBTS and 3rd party tool

Alarm name

7652


Commands There are no commands related to the RAN2861: UE Tracing Support in BTS feature. Measurements and counters There are no measurements or counters related to the RAN2861: UE Tracing Support in BTS feature. Key performance indicators There are no key performance indicators related to the RAN2861: UE Tracing Support in BTS feature. Parameters Table 120

New parameter introduced by RAN2861 Full name

Abbreviated name

Managed object

UE Tracing L3DC Connection Details

ueTracingL3dcConnectio BTSSCW nDetails

UE Tracing L3DC IP address

ueTracingL3dcIpAddress

UE Tracing L3DC TCP port

ueTracingL3dcTcpPort

UE Tracing trace type

ueTraceType


Sales information


g Issue: 01A DRAFT

License control RNC license key


Note: The same license is used as in RAN2930: IMSI-based Call Monitoring.

DN09232117

119

RNC solution features


6 RNC solution features 6.1 RAN3298: Support Max 32 PS Core Elements in RNC Benefits, functionality, system impact, reference data of the feature.

DRAFT VERSION

The RAN3298: Support Max 32 PS Core Elements in RNC feature increases the maximum number of PS core network elements supported by RNC from 16 to 32.

6.1.1 RAN3298 benefits The RAN3298: Support Max 32 PS Core Elements in RNC feature provides the following benefits: •

•

It ensures better operational flexibility and increased network capacity by allowing more nodes into one core network (CN) pool. This is beneficial in case of a multioperator radio access network (MORAN) where several network operators connect their core elements to the same radio network controller (RNC). The network is more robust and resilient thanks to properly distributed load across more nodes.

6.1.2 RAN3298 functional description Feature overview The RAN3298: Support Max 32 PS Core Elements in RNC feature increases the maximum number of links towards the packet core network nodes supported by RNC from 16 to 32. The support of maximum 32 PS core network elements is provided in all the RNC HW capacity steps. Only the maximum number of PS core network elements is modified. Other capacity figures remain unchanged. The maximum number of CS core network elements supported by RNC remains 16. License operations To enable configuration of more than 16, and up to 32 Iu-PS managed objects (MOs), the RAN3298 feature license must exist, and its state must be set to ON. The RAN3298 feature license name is SupportMax32PSCoreElementsInRNC and the feature code is 0000019734. After the license becomes expired, removed, or its state is set to OFF, the RAN3298 feature allows for continued use of all previously configured Iu-PS MOs (including those exceeding 16). All of the already configured Iu-PS MOs are still workable, and can be modified or removed. However, it is disallowed to create another Iu-PS until the license becomes valid, or the total Iu-PS MOs number is less than 16.

120

DN09232117

Issue: 01A DRAFT



6.1.3 RAN3298 system impact RAN3298: Support Max 32 PS Core Elements in RNC impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features If the customers use MORAN or MOCN, it is required that the RAN1602: Flexible Iu with Multi-Operator RAN feature is activated before activating the RAN3298: Support Max 32 PS Core Elements in RNC feature.

DRAFT VERSION

Impact on interfaces The RAN3298: Support Max 32 PS Core Elements in RNC allows for increased number of IuPS links. Impact on network management tools The RAN3298: Support Max 32 PS Core Elements in RNC feature has no impact on network management tools. Impact on system performance and capacity The RAN3298: Support Max 32 PS Core Elements in RNC feature has no impact on system performance. The RAN3298: Support Max 32 PS Core Elements in RNC increases the system capacity by allowing more nodes into one core network (CN) pool.

6.1.4 RAN3298 reference data RAN3298: Support Max 32 PS Core Elements in RNC requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements Table 122


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA17

RNC17

mcRNC17




OMS

NetAct

MSC

SGSN

MGW

UE







Alarms There are no alarms related to the RAN3298: Support Max 32 PS Core Elements in RNC feature. Commands There are no commands related to the RAN3298: Support max 32 PS core elements in RNC feature. Measurements and counters

Issue: 01A DRAFT

DN09232117

121



There are no measurements or counters related to the RAN3298: Support max 32 PS core elements in RNC feature. Key performance indicators There are no key performance indicators related to the RAN3298: Support max 32 PS core elements in RNC feature. Parameters Table 123

RAN3298 modified parameters

DRAFT VERSION

Full Name

122

Abbreviated name

Managed object

RNC Options

RncOptions

RNC

IuPS Interface

IUPS

IUPS




License control Long-term ON/OFF licence

DN09232117


Issue: 01A DRAFT


BTS solution features

7 BTS solution features 7.1 RAN3259: 2 ms TTI Non-FDPCH Users Increase Benefits, functionality, system impact, reference data of the feature.

DRAFT VERSION

The RAN3259: 2 ms TTI Non-FDPCH Users Increase feature improves baseband capacity for 2 ms non-FDPCH users.

7.1.1 RAN3259 benefits The RAN3259: 2 ms TTI Non-FDPCH Users Increase feature provides the following benefits: • • •

Up to 40% baseband capacity improvement for 2 ms non-FDPCH users Flexi WCDMA BTS Rel.2 and Rel.3 throughput improvement End-user experience improvement due to UL/DL throughput gain

7.1.2 RAN3259 functional description RAN3259 improves baseband capacity up to 40% for 2 ms TTI non-FPDCH user for both Rel.2 and Rel.3 system modules. The increase in the maximum user capacity per subunit is as follows: • •

for Rel.2, from 20 to 28 user per subunit for Rel.3, from 40 to 56 user per subunit

7.1.3 RAN3259 system impact RAN3259: 2 ms TTI Non-FDPCH Users Increase impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features The RAN1470: HSUPA 2 ms TTI feature is a prerequisite for this feature. Impact on interfaces The RAN3259: 2 ms TTI Non-FDPCH Users Increase feature has no impact on interfaces. Impact on network management tools The RAN3259: 2 ms TTI Non-FDPCH Users Increase feature has no impact on network management tools. Impact on system performance and capacity The RAN3259: 2 ms TTI Non-FDPCH Users Increase feature impacts system performance and capacity as follows: •

Issue: 01A DRAFT

increases number of non-FDPCH 2 ms users from 20 to 28 per subunit (for Rel.2 SM)

DN09232117

123



•

increases number of non-FDPCH 2 ms users from 40 to 56 per subunit (for Rel.3 SM)

7.1.4 RAN3259 reference data RAN3259: 2 ms TTI Non-FDPCH Users Increase requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

DRAFT VERSION

Table 125

RAN3259: 2 ms TTI Non-FDPCH Users Increase hardware and software requirements

RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17

WBTS17

WBTS17

Not planned

OMS

NetAct

MSC

SGSN

MGW

UE


NetAct 17





Alarms There are no alarms related to the RAN3259: 2 ms TTI Non-FDPCH Users Increase feature. BTS faults and reported alarms There are no faults related to the RAN3259: 2 ms TTI Non-FDPCH Users Increase feature. Commands There are no commands related to the RAN3259: 2 ms TTI Non-FDPCH Users Increase feature. Measurements and counters Table 126


Counter ID

Counter name

Measurement

M5008C 34

AVERAGE HSUPA SUBUNITS USAGE


M5008C 35

MAXIMUM HSUPA SUBUNITS USAGE


Key performance indicators Table 127


KPI ID RNC_931c

KPI name HSUPA MAC-es data volume at RNC

RNC_1883c Active HSUPA cell throughput

Parameters

124

DN09232117

Issue: 01A DRAFT


Table 128



Abbreviated name

Managed object

Parent structure

2ms TTI non-FDPCH users tti2msNonFdpchUse MRBTS/B increase enabled rIncEnabled TSSCW



DRAFT VERSION


License control


BTS License Key


7.2 RAN3067: Flexible HSDPA Carriers Allocation Benefits, functionality, system impact, reference data of the feature The RAN3067: Flexible HSDPA Carriers Allocation feature enables large downlink carrier aggregation, that is Dual Carrier/Dual Band HSPA configurations without the need for sector-based baseband pooling.

7.2.1 RAN3067 benefits The RAN3067: Flexible HSDPA Carriers Allocation feature enables large carrier aggregation, that is Dual Band / Dual Carrier HSPA configurations without the need for sector-based pooling in pure FSMF configurations. Carrier aggregation is supported between local cell groups, resulting in the best possible uplink performance with softer handover and interference cancellation between the cells being enabled. RAN3067: Flexible HSDPA Carriers Allocation also reduces the baseband resource need (compared to sector pooling) required for soft handover between the sector pools.

7.2.2 RAN3067 functional description The current HSPA carrier aggregation implementation requires that the cells participating in the carrier aggregation are processed in the same MAC-hs instance (same LCG and HSPA schedulers). The Local Cell Group (LCG) capacity has required sector pooling to be used in configurations with multiple LCGs. RAN3067 adds the support of carrier aggregation between multiple MAC-hs instances. The feature is enabled by the high speed low latency communication (SRIO) available in the FSMF Flexi Multiradio System Module architecture. Since the MAC-hs limitation is removed, the LCGs can be allocated as per frequency layer, enabling multiple LCGs to process UEs from the same sector while supporting carrier aggregation. FSMF supports SRIO between system modules, therefore the LCGs can be mapped between different system modules and still maintain the carrier aggregation. Uplink carrier aggregation is supported within a LCG. Sector pooling-based mapping: •

Issue: 01A DRAFT

LCG1: 4+0+0

DN09232117

125



• •

LCG2: 0+4+0 LCG3: 0+0+4

Each sector has its own LCG, and no softer handovers between the cells are supported. With RAN3067, the mapping can be done in multiple ways. An example with two LCG mapping: • •

LCG1: 2+2+2 LCG2: 2+2+2

DRAFT VERSION

No new BTS configurations are introduced with this feature, except for the possibility to pool cells and LCGs in a more efficient way than before. While this feature is activated and new configuration is used, DC-HSDPA users consume part of the secondary pool resources. Additional resource usage is taken into use in the RNC. RAN3067 supports softer handover with interference cancellation between the sectors where carrier aggregation is supported, which improves uplink performance.

7.2.3 RAN3067 system impact RAN3067: Flexible HSDPA Carriers Allocation impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features RAN3067:Flexible HSDPA Carriers Allocation makes it possible to use DC/DB-HSDPA with frequency based pooling BTS configuration. Impact on interfaces New IE: Secondary HSDPA User Weight Info is introduced to the NBAP message: NBAP: PRIVATE MESSAGE (Capability Indication) . Impact on network management tools The RAN3067:Flexible HSDPA Carriers Allocation feature has no impact on network management tools. Impact on system performance and capacity •

•

Carrier Aggregation Dual Cell HSDPA users require more scheduling resources comparing to legacy Dual Cell HSDPA users. See Dimensioning WCDMA RAN: Flexi BTS Baseband for more details. RAN3067 supports softer handover with interference cancellation between the sectors where carrier aggregation is supported, which improves uplink performance.

7.2.4 RAN3067 reference data RAN3067: Flexible HSDPA Carriers Allocation requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

126

DN09232117

Issue: 01A DRAFT


DRAFT VERSION

Table 130



RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

RNC17

mcRNC17


WBTS17


OMS

NetAct

MSC

SGSN

MGW

UE







Alarms Table 131


Alarm ID

7652

Alarm name


BTS faults and reported alarms Table 132 Fault ID

New BTS faults introduced by RAN3067 Fault name Alarm ID

Alarm name

165

Incorrect Carrier Aggregation Configuration [LCG ]

7652


167

Unsupported CA Group ID change [LCG ]

7652


Commands There are no commands related to the RAN3067: Flexible HSDPA Carriers Allocation feature. Measurements and counters Table 133

Existing counters related to RAN3067 Counter ID

Issue: 01A DRAFT

Reported alarms

Counter name

M1005C253

SUCCESSFUL MAC-D SETUP FOR DCHSDPA

M1005C254

FAILED MAC-D SETUP FOR DC-HSDPA

M1006C209

RB SETUP ATTEMPT FOR DC-HSDPA

M1006C210

SUCCESSFUL RB SETUP FOR DC-HSDPA

M1006C211

RB SETUP FAIL FOR DC-HSDPA DUE TO NO REPLY

M1006C212

RB SETUP FAIL FOR DC-HSDPA DUE TO UE NACK

M1005C252

MAC-D SETUP ATTEMPT FOR DC-HSDPA

M5008C19

MINIMUM NUMBER OF HSDPA USERS

DN09232117

127



Table 133

Existing counters related to RAN3067 (Cont.)

DRAFT VERSION

Counter ID

Counter name

M5008C20

AVERAGE NUMBER OF HSDPA USERS

M5008C21

MAXIMUM NUMBER OF HSDPA USERS

M5008C0

HSDPA MAXIMUM MAC-HS THROUGHPUT

M5008C1

HSDPA AVERAGE MAC-HS THROUGHPUT

M5006C55

MAXIMUM NUMBER OF HSDPA USERS IN LCG

M5006C56

AVERAGE NUMBER OF HSDPA USERS IN LCG

M5006C61

MAXIMUM HSDPA THROUGHPUT IN LCG

M5006C62

AVERAGE HSDPA THROUGHPUT IN LCG

M5011C0

MAXIMUM NUMBER OF HSDPA USERS IN SCHEDULER

M5011C1

AVERAGE NUMBER OF HSDPA USERS IN SCHEDULER

M5011C3

MAXIMUM HSDPA THROUGHPUT IN SCHEDULER

M5011C4

AVERAGE HSDPA THROUGHPUT IN SCHEDULER

Key performance indicators There are no key performance indicators related to the RAN3067: Flexible HSDPA Carriers Allocation feature. Parameters Table 134


Abbreviated name

Managed object

Carrier Aggregation enabled

carrierAggregationEnabl ed

BTSCW

Carrier Aggregation Group Identifier

cAGroupId

LCELGW




License control BTS License Key


7.3 RAN3286: FSM-r2 Static Power Management Benefits, functionality, system impact, reference data of the feature.

128

DN09232117

Issue: 01A DRAFT



The RAN3286: FSM-r2 Static Power Management feature introduces the possibility to power off unused FSP cards.

7.3.1 RAN3286 benefits The RAN3286: FSM-r2 Static Power Management feature provides energy savings.

DRAFT VERSION

7.3.2 RAN3286 functional description BTS configurations, especially with FSM-r2 system modules, can have an unused baseband capacity. RAN3286 feature allows to switch off unused FSP cards. The system checks the configuration file (SCF) which includes the amount of baseband resources (FSP cards) per configuration that can be switched off. For the configurations where not all capacity is needed, unused FSP cards are automatically powered off based on parameter given by the operator during commissioning.

g g

Note: MORAN solution is not supported. Note: Synergies can be gained when RAN955 is also used.

7.3.3 RAN3286 system impact RAN3286: FSM-r2 Static Power Management impact on features, interfaces, network management tools, and system performance and capacity. Interdependencies between features There are no interdependencies between the RAN3286: FSM-r2 Static Power Management feature and any other feature. Impact on interfaces The RAN3286: FSM-r2 Static Power Management feature has no impact on interfaces. Impact on network management tools The RAN3286: FSM-r2 Static Power Management feature has no impact on network management tools. Impact on system performance and capacity The RAN3286: FSM-r2 Static Power Management feature impacts system capacity as follows: •

Allows to automatically power off unused FSP cards.

The RAN3286: FSM-r2 Static Power Management feature has no impact on system performance.

7.3.4 RAN3286 reference data RAN3286: FSM-r2 Static Power Management requirements, alarms and faults, commands, measurements and counters, KPIs, parameters, and sales information. Requirements

Issue: 01A DRAFT

DN09232117

129



Table 136


RAS

IPA-RNC

mcRNC



Flexi Lite BTS

WCDMA 17

-

-

-

-

-

OMS

NetAct

MSC

SGSN

MGW

UE

-

-

-

-

-

-

DRAFT VERSION

The RAN3286: FSM-r2 Static Power Management feature requires the following hardware: • •

g

Master System Module (MSM): FSMC, FSMD or FSME Extension System Module (ESM): FSMC, FSMD or FSME Note: While using an FSMC-type MSM, the ESM should be of an FSMD or FSME type.

BTS faults and reported alarms Table 137

Existing faults and alarms related to RAN3286

Fault ID

1885

Fault name

Reported alarms Alarm ID

EFaultId_MissingLicenseAl

Alarm name

7660


7661


For alarm and fault descriptions, see RNC RNW and Flexi Multiradio BTS WCDMA Alarms and Faults. Commands There are no commands related to the RAN3286: FSM-r2 Static Power Management feature. Measurements and counters There are no measurements or counters related to the RAN3286: FSM-r2 Static Power Management feature. Key performance indicators There are no key performance indicators related to the RAN3286: FSM-r2 Static Power Management feature. Parameters Table 138


Abbreviated name

Amount of FSP cards to be powered off

130

Managed object

Parent structure

amountOfFspToBePo SMOD weredOff

DN09232117

Issue: 01A DRAFT


Table 138



FSM-r2 static power management enabled

Abbreviated name

Managed object

Parent structure

staticPowerManage BTSSCW mentEnabled

For parameter descriptions, see Flexi Multiradio BTS WCDMA Parameters. Sales information

DRAFT VERSION

Table 139

Issue: 01A DRAFT



License control BTS License Key

DN09232117


131

Wcdma17 Feature Descriptions and Instructions

Recommend Documents