29 Nokia-RU50 Feature Descriptions and Instructions

(1)

RU50 Feature Descriptions

and Instructions

DN09146788

Issue 01

Approval Date 2014-02-28

(2)

Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the cus-tomer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documenta-tion.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability aris-ing in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions con-tained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DA-TA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

NSN is a trademark 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 respec-tive owners, and they are mentioned for identification purposes only.

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 ser-vices we offer, please contact us at Nokia Solutions and Networks for any additional information.

(3)

Summary of changes...11 1 Introduction to RU50 features... 14 1.1 RU50 radio resource management features... 14 1.2 RU50 telecom features... 15 1.3 RU50 transmission and transport features...15 1.4 RU50 operability features...15 1.5 RU50 performance monitoring features... 16 1.6 RU50 RNC solution features... 16 1.7 RU50 BTS solution features...16 1.8 Licensing... 16 1.9 Reference documentation... 17 2 Radio resource management features... 19 2.1 RAN2963: Data Session Profiling... 19 2.1.1 Description of RAN2963: Data Session Profiling... 19 2.1.1.1 Benefits... 19 2.1.1.2 Requirements... 19 2.1.1.3 Functional description... 20 2.1.1.4 System impact...20 2.1.1.5 RAN2963: Data Session Profiling management data... 21 2.1.1.6 Sales information... 23 2.1.2 Activating RAN2963: Data Session Profiling...23 2.1.3 Verifying RAN2963: Data Session Profiling... 24 2.1.4 Deactivating RAN2963: Data Session Profiling... 25 2.2 RAN2179: Dual Band HSDPA 42 Mbps... 25 2.2.1 Description of RAN2179: Dual Band HSDPA 42 Mbps... 25 2.2.1.1 Benefits... 26 2.2.1.2 Requirements... 26 2.2.1.3 Functional description... 26 2.2.1.4 System impact...28 2.2.1.5 RAN2179: Dual-Band HSDPA 42Mbps management data...28 2.2.1.6 Sales information... 30 2.2.2 Activating RAN2179: Dual Band HSDPA 42 Mbps... 31 2.2.3 Verifying RAN2179: Dual Band HSDPA 42 Mbps... 32 2.2.4 Deactivating RAN2179: Dual Band HSDPA 42 Mbps... 33 2.3 RAN2482: Enhanced Virtual Antenna Mapping... 34 2.3.1 RAN2482: Enhanced Virtual Antenna Mapping ... 34 2.3.1.1 Benefits... 35 2.3.1.2 Requirements... 35 2.3.1.3 Functional description... 35 2.3.1.4 System impact...36

(4)

2.3.2 Activating RAN2482: Enhanced Virtual Antenna Mapping... 37 2.3.3 Verifying RAN2482: Enhanced Virtual Antenna Mapping... 40 2.3.4 Deactivating RAN2482: Enhanced Virtual Antenna Mapping... 40 2.4 RAN1668: HSUPA Inter-frequency Handover...41 2.4.1 Description of RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover... 41 2.4.1.1 Benefits... 41 2.4.1.2 Requirements... 41 2.4.1.3 Functional description... 42 2.4.1.4 System impact...42 2.4.1.5 RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover management data...44 2.4.1.6 Sales information... 47 2.4.2 Activating RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover... 47 2.4.3 Verifying RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover... 50 2.4.4 Deactivating RAN1668HSUPA Compressed Mode for LTE and Inter-frequency Handover... 52 2.5 RAN2980: Measurement Based LTE Layering... 53 2.5.1 Description of RAN2980: Measurement Based LTE Layering... 53 2.5.1.1 Benefits... 53 2.5.1.2 Requirements... 53 2.5.1.3 Functional description... 54 2.5.1.4 System impact...55 2.5.1.5 RAN2980: Measurement Based LTE Layering management data.. 55 2.5.1.6 Sales information... 58 2.5.2 Activating RAN2980: Measurement Based LTE Layering...58 2.5.3 Verifying RAN2980: Measurement Based LTE Layering ... 61 2.5.4 Deactivating RAN2980: Measurement Based LTE Layering... 62 2.6 RAN147: RRC Connection Setup Redirection... 62 2.6.1 Description of RAN147: RRC Connection Setup Redirection... 62 2.6.1.1 Benefits... 62 2.6.1.2 Requirements... 62 2.6.1.3 Functional description... 63 2.6.1.4 System impact...65 2.6.1.5 RAN147: RRC Connection Setup Redirection management data... 65 2.6.1.6 Sales information... 68 2.6.2 Activating RAN147: RRC Connection Setup Redirection... 68 2.6.2.1 Activating RAN147: RRC Connection Setup Redirection due to admission control reasons... 68 2.6.2.2 Activating RAN147: RRC Connection Setup Redirection due to signaling unit overload... 69

(5)

2.6.3.2 Verifying RAN147: RRC Connection Setup Redirection due to signaling unit overload reasons...71 2.6.4 Deactivating RAN147: RRC Connection Setup Redirection... 72 2.6.4.1 Deactivating RAN147: RRC Connection Setup Redirection due to admission control reasons... 72 2.6.4.2 Deactivating RAN147: RRC Connection Setup Redirection due to signaling unit overload reasons...73 2.7 RAN3069: RSRQ-based LTE Reselection... 74 2.7.1 Description of RAN3069: RSRQ-based LTE Reselection... 74 2.7.1.1 Benefits... 74 2.7.1.2 Requirements... 74 2.7.1.3 Functional description... 75 2.7.1.4 System impact...75 2.7.1.5 RAN3069: RSRQ-based LTE Reselection management data... 76 2.7.1.6 Sales information... 76 2.7.2 Activating RAN3069: RSRQ-based LTE Reselection...76 2.7.3 Verifying RAN3069: RSRQ-based LTE Reselection... 78 2.7.4 Deactivating RAN3069: RSRQ-based LTE Reselection... 79 2.8 RAN2264: Smart LTE Handover... 79 2.8.1 Description of RAN2264: Smart LTE Handover... 79 2.8.1.1 Benefits... 79 2.8.1.2 Requirements... 80 2.8.1.3 Functional description... 80 2.8.1.4 System impact...81 2.8.1.5 RAN2264: Smart LTE Handover management data... 81 2.8.1.6 Sales information... 86 2.8.2 Activating RAN2264: Smart LTE Handover...86 2.8.3 Verifying RAN2264: Smart LTE Handover... 90 2.8.4 Deactivating RAN2264: Smart LTE Handover... 91 2.9 RAN2881: WCDMA and GSM Layer Priorities... 92 2.9.1 Description of RAN2881: WCDMA and GSM Layer Priorities... 92 2.9.1.1 Benefits... 92 2.9.1.2 Requirements... 92 2.9.1.3 Functional description... 93 2.9.1.4 System impact...94 2.9.1.5 RAN2881: WCDMA and GSM Layer Priorities management data.. 94 2.9.1.6 Sales information... 97 2.9.2 Activating RAN2881: WCDMA and GSM Layer Priorities... 97 2.9.3 Verifying RAN2881: WCDMA and GSM Layer Priorities...99 2.9.4 Deactivating RAN2881: WCDMA and GSM Layer Priorities...99 3 Transmission and transport features...100

(6)

Service OAM... 100 3.1.1.1 Benefits... 100 3.1.1.2 Requirements... 100 3.1.1.3 Functional description... 101 3.1.1.4 System impact...102 3.1.1.5 RAN2243: Performance Monitoring Based on ETH Service OAM management data... 103 3.1.1.6 Sales information... 106 3.1.2 Activating RAN2243: Performance Monitoring Based on ETH Service OAM... 106 3.1.2.1 Activating Ethernet Service OAM PM... 107 3.1.2.2 Activating Frame Loss Measurement session... 108 3.1.2.3 Activating Frame Delay Measurement session... 110 3.1.3 Verifying RAN2243: Performance Monitoring Based on ETH Service OAM... 112 3.1.4 Deactivating RAN2243: Performance Monitoring Based on ETH Service OAM... 116 3.1.4.1 Deactivating Ethernet Service OAM PM...117 3.1.4.2 Deactivating Frame Loss Measurement session...118 3.1.4.3 Deactivating Frame Delay Measurement session... 119 4 Operability features... 122 4.1 RAN2199: BTS Event Triggered Symptom Data Collection...122 4.1.1 Description of RAN2199: BTS Event Triggered Symptom Data Collection... 122 4.1.1.1 Benefits... 122 4.1.1.2 Requirements... 122 4.1.1.3 Functional description... 123 4.1.1.4 System impact...125 4.1.1.5 RAN2199: BTS Event Triggered Symptom Data Collection management data... 125 4.1.1.6 Sales information... 127 4.1.2 Activating RAN2199: BTS Event Triggered Symptom Data Collection... 127 4.1.3 Deactivating RAN2199: BTS Event Triggered Symptom Data Collection... 128 4.2 RAN2554: Transport Configuration Fall-back... 129 4.2.1 Description of RAN2554: Transport Configuration Fallback...129 4.2.1.1 Benefits... 129 4.2.1.2 Requirements... 129 4.2.1.3 Functional description... 130 4.2.1.4 System impact...130 4.2.1.5 RAN2554: Transport Configuration Fallback management data... 131 4.2.1.6 Sales information... 131

(7)

4.2.2.2 Activating RAN2554: Transport Configuration Fallback from

NetAct CM Editor... 132

4.2.3 Verifying RAN2554: Transport Configuration Fallback... 132

4.2.4 Testing RAN2554: Transport Configuration Fallback... 133

4.2.4.1 Test Case 1: Transport configuration fallback ... 133

4.2.4.2 Test Case 2: Transport configuration roll forward...134

4.2.5 Deactivating RAN2554: Transport Configuration Fallback... 136

4.2.5.1 Deactivating RAN2554: Transport Configuration Fallback using BTS Site Manager... 136

4.2.5.2 Deactivating RAN2554: Transport Configuration Fallback from NetAct CM Editor... 136 5 RNC solution features... 137 5.1 RAN3047: RTT Improvement to Enhance User Experience... 137 5.1.1 Description of RAN3047: RTT Improvement to enhance user experience...137 5.1.1.1 Benefits... 137 5.1.1.2 Requirements... 137 5.1.1.3 Functional description... 137 5.1.1.4 System impact...138 5.1.1.5 RAN3047: RTT Improvement to enhance user experience management data... 138 5.1.1.6 Sales information... 139 6 BTS solution features... 140 6.1 RAN3017: Additional 6 WCDMA Cell Activation... 140 6.1.1 Description of RAN3017: Additional 6 WCDMA Cell Activation. 140 6.1.1.1 Benefits... 140 6.1.1.2 Requirements... 140 6.1.1.3 Functional description... 141 6.1.1.4 System impact...141 6.1.1.5 RAN3017: Additional 6 WCDMA Cell Activation management data ... 141 6.1.1.6 Sales information... 142 6.1.2 Activating RAN3017: Additional 6 WCDMA Cell Activation... 142 6.1.3 Verifying RAN3017: Additional 6 WCDMA Cell Activation... 143 6.1.4 Deactivating RAN3017: Additional 6 WCDMA Cell Activation... 144

(8)

Figure 2 RRC connection setup redirection...63 Figure 3 Selection process of redirection information...64 Figure 4 WCDMA and GSM cell reselection based on layer priorities... 94 Figure 5 Performance monitoring using Ethernet Service OAM frames...102 Figure 6 Symptom data collection from the BTS... 123 Figure 7 RAN2554: Transport Configuration Fallback... 130 Figure 8 Activating RAN3017: Additional 6 WCDMA Cell Activation...143

(9)

Table 2 RU50 transmission and transport features... 15 Table 3 RU50 operability features... 15 Table 4 RU50 RNC solution features... 16 Table 5 RU50 BTS solution features... 16 Table 6 Software requirements... 19 Table 7 New counters...21 Table 8 Related existing counters... 21 Table 9 New parameters... 22 Table 10 Modified parameters...22 Table 11 Sales information...23 Table 12 Software requirements... 26 Table 13 Supported band combinations...27 Table 14 Existing alarms... 29 Table 15 New counters...29 Table 16 New parameters... 29 Table 17 Modified parameters...30 Table 18 Sales information...30 Table 19 Allowed band combinations for Dual Cell and Dual Band HSDPA... 31 Table 20 Software requirements... 35 Table 21 New parameters... 37 Table 22 Sales information...37 Table 23 Software requirements... 41 Table 24 New counters...44 Table 25 Related existing counters... 45 Table 26 New key performance indicators... 45 Table 27 New parameters... 45 Table 28 Modified parameters...46 Table 29 Related existing parameters...46 Table 30 Sales information...47 Table 31 Software requirements... 53 Table 32 New counters...56 Table 33 New parameters... 56 Table 34 Modified parameters...57 Table 35 Sales information...58 Table 36 New counters...65 Table 37 Related existing counters... 65 Table 38 New parameters... 66

(10)

Table 41 Counters verification...71 Table 42 Counters verification...72 Table 43 Software requirements... 75 Table 44 New parameters... 76 Table 45 Sales information...76 Table 46 Software requirements... 80 Table 47 New counters...82 Table 48 Related existing counters... 84 Table 49 New parameters... 84 Table 50 Modified parameters...85 Table 51 Sales information...86 Table 52 Software requirements... 93 Table 53 New parameters... 95 Table 54 Modified parameters...96 Table 55 Related existing parameters...96 Table 56 Sales information...97 Table 57 Software requirements... 101 Table 58 New faults...104 Table 59 New counters...104 Table 60 New parameters... 105 Table 61 Sales information...106 Table 62 Related existing alarms... 125 Table 63 New parameters... 126 Table 64 New OMS LDAP parameters...126 Table 65 Related existing OMS LDAP parameters... 126 Table 66 Sales information...127 Table 67 Software requirements... 129 Table 68 New fault...131 Table 69 New parameter... 131 Table 70 Sales information...131 Table 71 Software requirements... 137 Table 72 Sales information...139 Table 73 Software requirements... 140 Table 74 Number of needed license keys ... 141 Table 75 Modified parameters...142 Table 76 Sales information...142

(11)

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 01 DRAFT (2013-12-13, RU50) and 01

(2014-02-28, RU50)

Description of RAN3017: Additional 6 WCDMA Cell Activation • Management data has been updated.

Description of RAN2264: Smart LTE Handover • Functional description has been updated.

• System impact has been updated.

• Management data has been updated.

Description of RAN2963: Data Session Profiling • The Benefits have been updated.

Activating RAN3069: RSRQ-based LTE Reselection • The instructions have been added.

Activating RAN147: RRC Connection Setup Redirection • The instructions have been updated.

Description of RAN147: RRC Connection Setup Redirection • Benefits has been updated.

• Functional description has been updated.

• Management data has been updated.

• Requirements has been updated.

Verifying RAN147: RRC Connection Setup Redirection • The instructions have been updated.

Deactivating RAN147: RRC Connection Setup Redirection • The instructions have been updated.

New feature descriptions

The following feature descriptions are new: • Radio resource management features

– RAN2482: Enhanced Virtual Antenna Mapping

• RNC solution features

– RAN3047: RTT Improvement to enhance user experience

(12)

Feature activation instructions have been added for the following features: • Radio resource management features

– RAN2963: Data Session Profiling

– RAN2179: Dual Band HSDPA 42 Mbps

– RAN2482: Enhanced Virtual Antenna Mapping

– RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover

– RAN2980: Measurement Based LTE Layering

– RAN147: RRC Connection Setup Redirection

– RAN3069: RSRQ-based LTE Reselection

– RAN2264: Smart LTE Handover

– RAN2881: WCDMA and GSM Layer Priorities

• Transmission and transport features

– RAN2243: Performance Monitoring Based on ETH Service OAM

• Operability features

– RAN2199: BTS Even Triggered Symptom Data Collection

– RAN2554: Transport Configuration Fall-back

• BTS solution features

– RAN3017: Additional 6 WCDMA Cell Activation

Changes between issues 00 DRAFT (2013-11-12, RU50) and 01

DRAFT (2013-12-13, RU50)

The following feature descriptions have been updated: • Radio resource management features

– RAN2963: Data Session Profiling

– RAN2179: Dual Band HSDPA 42 Mbps

– RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover

– RAN2980: Measurement Based LTE Layering

– RAN147: RRC Connection Setup Redirection

– RAN3069: RSRQ-based LTE Reselection

– RAN2264: Smart LTE Handover

– RAN2881: WCDMA and GSM Layer Priorities

• Transmission and transport features

– RAN2243: Performance Monitoring Based on ETH Service OAM

• Operability features

– RAN2199: BTS Event Triggered Symptom Data Collection

(13)

• BTS solution features

(14)

1 Introduction to RU50 features

1.1 RU50 radio resource management features

See the following table for more detailed information on WCDMA RAN functions and feature activation:

RU50 features

Table 1 RU50 radio resource management features

Feature Other related descriptions Related instructions

RAN2963: Data Session Profiling WCDMA RAN RRM Packet Scheduler

WCDMA RAN Packet Data Transfer States

Activating RAN2963: Data Session Profiling

RAN2179: Dual Band HSDPA 42 Mbps WCDMA RAN HSDPA in BTS

WCDMA RAN RRM Handover Control WCDMA RAN RRM HSDPA

WCDMA RAN RRM HSUPA

Activating RAN2179: Dual Band HSDPA 42 Mbps RAN2482: Enhanced Virtual Antenna Mapping This information will be provided in future deliveries. Activating RAN2482: Enhanced Virtual Antenna Mapping RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover

WCDMA RAN RRM Handover Control WCDMA RAN RRM HSUPA

WCDMA RAN SRNS Relocation

Activating RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover

RAN2980: Measurement Based LTE Layering

WCDMA RAN RRM HSUPA Activating RAN2980: Measurement Based LTE Layering

RAN147: RRC Connection Setup Redirection

WCDMA RAN RRM Admission Control WCDMA RAN RRM Handover Control WCDMA RAN RRM HSDPA

WCDMA RAN RRM HSUPA RNC Overload Control

WCDMA RAN Call Setup and Release

Activating RAN147: RRC Connection Setup Redirection

RAN3069: RSRQ-based LTE Reselection

WCDMA RAN RRM Handover Control WCDMA RAN Call Setup and Release

Activating RAN3069: RSRQ-based LTE Reselection

RAN2264: Smart LTE Handover WCDMA RAN RRM Handover Control

WCDMA RAN RRM HSUPA

Activating RAN2264: Smart LTE Handover

(15)

Table 1 RU50 radio resource management features (Cont.)

Feature Other related descriptions Related instructions WCDMA RAN SRNS Relocation

RAN2881: WCDMA and GSM Layer Priorities

WCDMA RAN RRM Handover Control WCDMA RAN Call Setup and Release

Activating RAN2881: WCDMA and GSM Layer Priorities

1.2 RU50 telecom features

There are no RU50 features in the Telecom area.

1.3 RU50 transmission and transport features

RU50 features

Table 2 RU50 transmission and transport features

Feature Other related descriptions Related instructions RAN2243: Performance Monitoring

Based on ETH Service OAM

WCDMA RAN IP Transport Activating RAN2243: Performance Monitoring Based on ETH Service OAM

1.4 RU50 operability features

RU50 features

Table 3 RU50 operability features

Feature Other related descriptions Related instructions RAN2199: BTS Event Triggered Symptom Data Collection This feature does not have any related descriptions. Activating RAN2199: BTS Event Triggered Symptom Data Collection RAN2554: Transport Configuration

Fall-back

This feature does not have any related descriptions.

Activating RAN2554: Transport Configuration Fall-back

(16)

1.5 RU50 performance monitoring features

There are no RU50 features in the performance monitoring area.

1.6 RU50 RNC solution features

RU50 features

Table 4 RU50 RNC solution features

Feature Other related descriptions Related instructions RAN3047: RTT Improvement to enhance user experience This feature does not have related descriptions. This feature does not have related instructions.

1.7 RU50 BTS solution features

See the following tables for more detailed information on WCDMA RAN functions and feature activation:

RU50 features

Table 5 RU50 BTS solution features

Feature Other related descriptions Related instructions RAN3017: Additional 6 WCDMA Cell

Activation This feature does not have any related descriptions. Activating RAN3017: Additional 6 WCDMA Cell Activation

1.8 Licensing

The application software features (ASW) are under license key management. A license is a file that includes the feature information. Before a licensed feature can be activated, the license file needs to be transferred to and installed in the IPA-RNC. For information on transferring the license, see License management operations in RNC in WCDMA

RAN License Operation. For information on installing the license, see Installing licenses in the network element in Managing License-based Features in IPA-RNC and Managing License-based Features in Multicontroller RNC.

(17)

g

Some RNC-controlled features are activated using an RNC general parameter file (PRFILE) or a feature information control file (FIFILE). For details, see

Parameter-based option management in WCDMA RAN License Operation.

g

There are no licenses in the Flexi Direct RNC.

A license can be installed using NetAct or a local MML (IPA-RNC) or SCLI (mcRNC) interface. If it is installed using NetAct, the licensed feature state is automatically set to ON state. If the MML/SCLI interface is used, the default value is OFF, and you need to set the feature to ON state manually. For information on feature states, see Feature

States in WCDMA RAN License Operation. The license-related MML commands are

described in W7 - License and Feature Handling.

License management in mcRNC

For details on the mcRNC-specific license management, see License management in

RNC in WCDMA RAN License Operation and Managing License-based Features in Multicontroller RNC.

License management in WBTS

License management in WBTS is based on a pool concept. Each license contains a specific amount of capacity that can be distributed among the selected WBTSs. Distributing licenses from the pool license decreases the amount of free capacity in the pool. Managing pool licenses and distributing to WBTSs is done via NetAct Licence Manager. Some basic license operations (for example, license installation or deletion) are also possible with BTS Site Manager. For details on the WBTS-specific license management, see License management in

WBTS in WCDMA RAN License Operation.

1.9 Reference documentation

For information on the parameters, counters and alarms related to each feature, see the

Management data section of the feature descriptions.

For parameter descriptions, see:

• WCDMA Radio Network Configuration Parameters Excel in WCDMA RAN Operating

Documentation, Parameters in NOLS PIC

• IP Configuration Plan Interface Parameters for Multicontroller RNC Excel in WCDMA

RAN Operating Documentation, Parameters in NOLS PIC • OMS LDAP parameters

• Flexi Transport Module Parameters Excel in WCDMA RAN Operating

• Flexi Multiradio BTS WCDMA Parameters Excel in WCDMA RAN Operating

• Multicontroller Radio Network Configuration Parameters Excel in WCDMA RAN

Operating Documentation, Parameters in NOLS PIC

• ATM Configuration Plan Interface Parameters Excel in WCDMA RAN Operating

(18)

• IP Configuration Plan Interface Parameters for Flexi Direct RNC Excel in WCDMA

RAN Operating Documentation, Parameters in NOLS PIC

• Radio Network Parameters in Flexi Direct Excel in WCDMA RAN Operating

• Reference Information Service in NOLS for RNC parameters For counter descriptions, see:

• RNC Counters - RNW Part

• RNC Counters – Transport and HW Part

• WBTS Counters

• Reference Information Service in NOLS For alarm descriptions, see:

• IPA-RNC Notices (0-999)

• IPA-RNC Disturbances (1000-1999)

• IPA-RNC Failure Printouts (2000-3999)

• IPA-RNC Diagnosis Reports (3700-3999)

• Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-9000)

• Flexi WCDMA Base Station Faults

• OMS Alarms

For key performance indicator descriptions, see: • WCDMA RAN Key Performance Indicators

(19)

2 Radio resource management features

2.1 RAN2963: Data Session Profiling

2.1.1 Description of RAN2963: Data Session Profiling

Introduction to the feature

The RAN2963: Data Session Profiling feature provides faster web browsing session for end user.

2.1.1.1 Benefits

End-user benefits

This feature enables fast web browsing to the end user.

Operator benefits

This feature benefits the operator as follows: • It allows operators to use higher thresholds for common channels. Keep-alive-type signaling is moved to common channels, more HSPA resources are available for data, what impacts end-user experience and increases satisfaction. • It allows for the usage of the Shorter Cell_DCH state inactivity timers, resulting in the faster direct Cell_PCH - Cell_DCH allocation, what improves HSPA efficiency. • The large amounts of data sent in short time period are allocated to HSPA directly. In this case Cell_FACH state is skipped, and state change from Cell_PCH to Cell_DCH is approximately one second faster.

2.1.1.2 Requirements

Software requirements

Table 6: Software requirements lists the software required for this feature. RAS Flexi Direct IPA-RNC mcRNC Flexi Direct

RNC OMS BTS Flexi RU50 Planned for later release RN8.0 Planned for later release Planned for later release OMS3.0 (RU50) Support not required Table 6 Software requirements Flexi Lite BTS BTS Flexi 10 NetAct MSC SGSN MGW UE Support not required Support not required NetAct 8 EP1 Support not required Support not required Support not required Support not required

Hardware requirements

This feature requires no new or additional hardware.

(20)

2.1.1.3 Functional description

Functional overview

The RAN2963: Data Session Profiling feature aims to provide faster web browsing. This is achieved by moving the terminal directly to the Cell_DCH, even though the initial data amount suggests allocation to the Cell_FACH - the amount of data is below the RNPS -TrafVolThresholdULLow parameter.

When the large data amount is identified in the session (the LargeDataThr parameter value is exceeded), after the end of the session (when the UE is moved to the

Cell/URA_PCH state), the timer defined by the LargeDataTime parameter is started. The UE, being in the Cell/URA_PCH state, starts next data session by sending the RRC:

CELL UPDATE message with cell update cause set as uplink data transmission. When

the time defined by the LargeDataTime parameter is not exceeded, the UE is moved directly to the Cell_DCH state, with the RRC: CELL UPDATE CONFIRM message. After successful procedure, when the RRC: RADIO BEARER RECONFIGURATION

COMPLETE message is successfully received from UE, the RNC updates the M1006C309: SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING counter, if TVI is not set as TRUE in RRC: CELL UPDATE message.

The amount of data (LargeDataThr) and the time period (LargeDataTime) are the parameters defined by the operator. The fast state change is performed both for sending and receiving data. For the UEs capable of using the HS-RACH, an RNPS- HSChaPrefInDataSesProf parameter is used. It allows either a direct transfer the Cell_DCH state or staying in the Cell_FACH state and using HS-RACH/FACH channels provided the data session profiling conditions. For proper functioning of the RAN2963 feature, please mind the following parameter configuration: • RNFC-DCHtoPCHEnabled should be set to its default value - enabled. • RNFC-CUCforPCHtoDCHallowed should be set to its default value - true. • WAC-MSActivitySupervision should be set to the value > 0.

2.1.1.4 System impact

Interdependencies between feature

• RAN1913: High Speed Cell_FACH

The feature enables a special handling for HS-RACH capable UE. If preferred, the feature can be disabled for HS-RACH capable UEs with

HSChaPrefInDataSesProf parameter. • RAN2494: Fast Cell_PCH Switching

This feature is recommended to be used with the Data Session Profiling feature. It helps in achieving faster state changes to the Cell_DCH state.

Impact on interfaces

(21)

Impact on commands

There are no commands related to this feature.

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

State transmission from the Cell_PCH to Cell_DCH is approximately one second faster.

2.1.1.5 RAN2963: Data Session Profiling management data

For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.

Alarms

There are no alarms related to this feature.

Measurements and counters

Table 7: New counters lists counters introduced with this feature.

Table 7 New counters

Counter ID Counter name Measurement

M1006C309 SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING

RRC signalling (RNC)

Table 8: Related existing counters lists existing counters related to this feature.

Table 8 Related existing counters

M1006C174 STATE TRANSITION TIME PCH TO DCH RRC signalling (RNC) M1006C175 DENOMINATOR FOR STATE TRANSITION TIME PCH TO DCH RRC signalling (RNC) M1006C196 ATTEMPTED PCH TO DCH TRANSITIONS USING UM-RLC RRC signalling (RNC) M1006C197 SUCCESSFUL PCH TO DCH TRANSITIONS USING UM-RLC RRC signalling (RNC) M1006C198 CELL RESELECTIONS DURING PCH TO DCH TRANSITIONS USING UM-RLC RRC signalling (RNC)

(22)

Key performance indicators

There are no key performance indicators related to this feature.

Parameters

Table 9: New parameters lists parameters introduced with this feature.

Table 9 New parameters

Full name Abbreviated name Managed object

Data Session Profiling Enabled DataSessionProfEnabled RNFC Large DataThreshold LargeDataThr RNPS Large Data Time LargeDataTime RNPS HS-RACH/FACH Preferred in Data Session Profiling HSChaPrefInDataSesProf RNPS Table 10: Modified parameters lists parameters modified by this feature. Table 10 Modified parameters

RNCOptions RncOptions RNC Uplink traffic volume measurement low threshold TrafVolThresholdULLow RNPS UL traffic volume threshold for Smartphone SmartTrafVolThrUL WCEL Downlink traffic volume measurement low threshold TrafVolThresholdDLLow WCEL DL traffic volume threshold for Smartphone SmartTrafVolThrDL WCEL Downlink NAS signalling volume threshold NASsignVolThrDL WCEL

(23)

2.1.1.6 Sales information

Table 11 Sales information

BSW/ASW SW component License control in network element

ASW RAN RNC LK

2.1.2 Activating RAN2963: Data Session Profiling

Purpose

Follow this procedure to activate this feature.

For more information on the feature, see the RAN2963: Data Session Profiling Feature Description.

Before you start

Restart of the RNC is not required after the activation of this feature. This procedure does not require cell locking. This procedure does not cause downtime, and it can be activated at any time of the day. Make sure you have access to the following applications: • OMS Element Manager • Application Launcher This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command: • for IPA-RNC: ZW7M: FEA=4654:ON; The following feature is recommended to be activated/configured before activation of

RAN2963: Data Session Profiling feature:

• RAN2494: Fast Cell_PCH Switching

• RAN1232: Fast Call Setup from Cell_PCH State The following parameters need to be set as follows:

• The WAC-MSActivitySupervision must be set to non-zero value, to allow the Cell_PCH Data Session Profiling to function.

• The RNFC-CUCforPCHtoDCHallowed parameter must be set to its default value -true - to allow the Data Session Profiling to function.

The following parameter is suggested to be set as follows:

(24)

1 Open the OMS Element Manager.

2 Go to the Topology Tree View.

Select: Network Management ► Topology Tree View

3 Expand the RNFC object.

4 Configure the RNFC object.

a) From the drop-down menu select Edit Parameters.

b) Set the DataSessionProfEnabled parameter value to Enabled.

5 Save the changes. a) Click the Apply button.

The RNFC - DataSessionProfEnabled parameter is visible as Enabled in the OMs Element Manager and as a result the feature RAN2963: Data Session Profiling is activated.

2.1.3 Verifying RAN2963: Data Session Profiling

Purpose

Follow this procedure to verify that this feature works properly in the network.

1 Activate measurement M1006

In the Application Launcher, activate the measurement M1006 and set the measurement interval to 15 minutes.

2 Start the PS session with the smartphone.

It can be internet-browsing, mailbox checking. The transmitted data amount must be higher then the value specified in the LargeDataThr parameter

3 During the session make pauses.

During the data session make pauses, but keep the RRC connection. The pauses must not be longer than the time value defined in the LargeDataTime parameter. 4 Resume the user-data transmission.

After the pause, when the UE was moved from the Cell_DCH to Cell_PCH, renew the user-data transmission. Even little data amount is sufficient for the purposes of the veneration process.The data transmission must not be longer than the time value defined in the LargeDataTime parameter.

(25)

5 Open the Application Launcher

6 Use the RNW measurement management application to start measurements of the Cell_PCH to Cell_DCH transitions due to data session profiling counter The value of the counter M1006C309 (SUCCESSFUL PCH TO DCH TRANS DUE TO DATA SESSION PROFILING) should be larger than 0, that implies that the direct transmission from the Cell_PCH to Cell_DCH state occurred.

2.1.4 Deactivating RAN2963: Data Session Profiling

Purpose

Follow this procedure to deactivate this feature.

2 Go to the Topology Tree View.

Select: Network Management ► Topology Tree View

3 Expand the RNFC object.

4 Configure the RNFC object.

a) From the drop-down menu select Edit Parameters.

b) Set the DataSessionProfEnabled parameter value to Disable.

5 Save the changes. a) Click the Apply button.

2.2 RAN2179: Dual Band HSDPA 42 Mbps

2.2.1 Description of RAN2179: Dual Band HSDPA 42 Mbps

Introduction to the feature

With RAN2179: Dual Band HSDPA 42 Mbps, it is possible to use Dual Cell HSDPA with two carriers located in different frequency bands (example: Carrier 1 in band 2110-2170 MHz and Carrier 2 in band 925-960 MHz). Dual Band HSDPA is therefore very similar to Dual Cell HSDPA, the only difference is at Layer 1: the carriers are in different frequency bands. For more information on Dual Cell HSDPA, see RAN1906: Dual Cell HSDPA in

(26)

2.2.1.1 Benefits

End-user benefits

With this feature, end-user benefits from increased coverage and throughput.

Operator benefits

With this feature, Dual Cell HSDPA benefits can be obtained even when no contiguous 10 MHz frequency allocation is available. Gains are obtained from additional frequency band. Lower band provides coverage, while higher band provides increased capacity and peak rate. BTS based scheduling enables dynamic resource sharing, so that far-away-UEs mainly use low frequency band, while close-by-UEs mainly use the high frequency. This approach maximizes the sector coverage and capacity.

2.2.1.2 Requirements

Software requirements

Table 12: Software requirements lists the software required for this feature. Table 12 Software requirements

RAS Flexi Direct IPA-RNC mcRNC Flexi Direct RNC OMS Flexi BTS RU50 Planned for later releases RN8.0 Planned for later releases Planned for later releases OMS3.0 (RU50) WN9.0 Flexi Lite BTS Flexi 10 BTS NetAct MSC SGSN MGW UE Not planned Planned for later releases NetAct8 EP1 Support not required SG8.0 Support not required 3GPP Rel-9

Hardware requirements

For Flexi Multiradio BTS WCDMA this feature requires one of the following features: • RAN2382: Flexi BTS Multimode System Module - FSMC

• RAN1016: Flexi BTS Multimode System Module - FSMD

• RAN1848: Flexi BTS Multimode System Module - FSME

2.2.1.3 Functional description

With the RAN2179: Dual Band HSDPA 42 Mbps feature data for capable UE is scheduled on two distinct frequency bands in the downlink. With this feature, the maximum peak rate is 42 Mbps when 64QAM is enabled and 15 codes are available on both frequencies.

(27)

The BTS uses proportional fair scheduling and optimizes the sector coverage and capacity by favoring the low-frequency band for cell-edge-UEs and the high-frequency band for UEs, that are closer to the BTS. This allows Dual Band HSDPA to combine the gain of normal Dual Cell HSDPA scheduling and the benefits of low frequency band for faraway users. The carrier selection is based both on the UE distance and current load on both uplink carriers. The RNC uses the RAN2172: Multi-Band Load Balancing feature for carrier selection.

Figure 1 Two HSDPA carriers located in two different frequency bands.

Table 13: Supported band combinations shows three band combinations supported by the RAN2179: Dual Band HSDPA 42 Mbps feature.

Table 13 Supported band combinations

Dual Band HSDPA Configuration

UL Band DL Band

1 I or VIII I and VIII 2 II or IV II and IV

(28)

g

Mixed RF module configurations, Rel 1+Rel2 or Rel1+Rel3, cannot be used with this feature.

2.2.1.4 System impact

Interdependencies between features

• The RAN1906: Dual Cell HSDPA feature and all its preconditions are prerequisites for this feature.

• Use of 64QAM modulation requires the RAN1643: HSDPA 64QAM feature. • Licenses for two separate frequency bands in the same NodeB and RNC are required.

Impact on interfaces

RNC and BTS NBAP interface including new IE's in messages: (BTS -> RNC) Audit Response: BTS informs RNC on DualBand-HSDPA capability (BTS -> RNC) Resource Status Indication: BTS informs RNC which cell will support DualBand-HSDPA. Following NBAP procedures are unchanged between DC-HSDPA and DB-HSDPA: • Radio Link Setup • Radio Link Reconfiguration Changed NBAP procedures between DC-HSDPA and DB-HSDPA: Audit Response and Resource Status Indication. These procedures are enhanced with new IE indicating that NodeB has new DB-capability

Impact on network and network element management tools

Impact on system performance and capacity

The RAN2179: Dual Band HSDPA 42 Mbps feature can double maximum achievable peak user throughput. It also increases cell capacity (by up to 40%) and cell edge throughput.

2.2.1.5 RAN2179: Dual-Band HSDPA 42Mbps management data

For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.

Alarms

(29)

Table 14 Existing alarms

Alarm ID Alarm name

3325 INCONSISTENCY IN CONFIGURATION PARAMETERS 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

Measurements and counters

Table 15: New counters lists counters introduced with this feature.

Table 15 New counters

M1001C728 UE SUPPORT FOR DB-HSDPA BAND REL9-1 Service Level M1001C729 UE SUPPORT FOR DB-HSDPA BAND REL9-2 Service Level M1001C730 UE SUPPORT FOR DB-HSDPA BAND REL9-3 Service Level M1006C293 RB SETUP ATTEMPT FOR DB-HSDPA RRC signalling M1006C294 SUCCESSFUL RB SETUP FOR DB-HSDPA RRC signalling M1006C295 RB SETUP FAIL FOR DB-HSDPA DUE TO NO REPLY RRC signalling M1006C296 RB SETUP FAIL FOR DB-HSDPA DUE TO UE NACK RRC signalling

Key performance indicators

Parameters

(30)

Table 16 New parameters (Cont.)

Preferred Frequency Layer for DB-DC-HSDPA NRT PFLDBHSDNRT PFL Preferred Layer for DB-DC-HSDPA NRT PrefLayerDBHSDNRT PFL Preferred Frequency Layer for DB-DC-HSDPA Streaming PFLDBHSDStr PFL Preferred Layer for DB-DC-HSDPA Streaming PrefLayerDBHSDStr PFL Preferred Frequency Layer for DB-DC-HSDPA AMR PFLDBHSDAMR PFL Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMR PFL Preferred Frequency Layer for DB-DC-HSDPA AMR and NRT PFLDBHSDAMRNRT PFL Preferred Layer for DB-DC-HSDPA AMR and NRT PrefLayerDBHSDAMRNRT PFL Table 17: Modified parameters lists parameters modified by this feature. Table 17 Modified parameters

DC HSDPA Enabled DCellHSDPAenabled WCEL Dual Cell versus MIMO preference DCellVsMIMOPreference RNC

Frame timing offset of a cell Tcell WCEL

2.2.1.6 Sales information

BSW/ASW SW component License control in network element

(31)

2.2.2 Activating RAN2179: Dual Band HSDPA 42 Mbps

Purpose

Follow this procedure to activate this feature. Before you start

A restart of the RNC and the BTS is not required after the activation of this feature. This procedure requires cell locking. Make sure you have access to the following applications: • OMS Element Manager • Application Launcher • Man-machine interface (MMI) Make sure that:

• RAN1906: Dual-Cell HSDPA 42 Mbps feature is activated in the RNC.

• Dual Cell HSDPA must be activated to those cells that are going to be used for Dual Band HSDPA. • Used cells must be configured to those bands that are supported for Dual Band HSDPA. • Used frequencies (in two bands) must be handed with the same HSDPA scheduler (similar to Dual Cell HSDPA uses frequencies in one band that must be handled with the same scheduler). For the allowed band combinations for Dual Band HSDPA, see Table 19: Allowed band combinations for Dual Cell and Dual Band HSDPA. Table 19 Allowed band combinations for Dual Cell and Dual Band HSDPA

Dual Band - Dual Cell HSDPA Configuration

Uplink band Downlink band

1 I or VIII I and VIII 2 II or IV II and IV

3 I or V I and V

The RAN2179: Dual Band HSDPA 42 Mbps feature is controlled by the capacity license key. For more information on licensing, see Licensing.

g

The feature code for this feature is 2118. To set the the feature state to ON, use the following command: • for IPA-RNC: ZW7M:FEA=2118:ON; • No license is required in Flexi Direct RNC.

(32)

2 Go to the Topology.

3 Expand the ROOT.

4 Expand the RNC object.

5 Expand the WBTS object.

6 Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs to be activated:

a) Select the WCEL object.

b) Select the cell in the WCell(s) table.

c) From the drop-down menu select "State ► Change State: Lock".

7 Configure the WCEL object:

a) Select Edit parameters from the WCEL object. b) Set the DBandHSDPAEnabled parameter to Enabled.

8 Unlock the WCEL.

9 Repeat the steps 6-8 for all the required cells.

2.2.3 Verifying RAN2179: Dual Band HSDPA 42 Mbps

Purpose

Follow the procedure below to verify that the activation of the RAN2179: Dual Band HSDPA 42Mbps feature has been successful.

(33)

1 Perform the RRC connection setup with UE that supports Dual Band HSDPA and send some data.

2 Open the RNW measurement management application from Application Launcher.

3 Use the RNW measurement management application to start measurements M1006 Traffic with 15 minute interval.

Alternatively the measurement can be started using NetAct Administration of Measurements Application.

Wait until the measurement interval starts.

4 After the measurement data has been collected, use the RNW Measurement presentation GUI to check if any of the following counters has value greater than 0. • M1006C293 - RB SETUP ATTEMPT FOR DB-HSDPA • M1006C294 - SUCCESSFUL RB SETUP FOR DB-HSDPA • M1006C295 - RB SETUP FAIL FOR DB-HSDPA DUE TO NO REPLY • M1006C296 - RB SETUP FAIL FOR DB-HSDPA DUE TO UE NACK • M1001C728 - UE SUPPORT FOR DB-HSDPA BAND REL9-1 • M1001C729 - UE SUPPORT FOR DB-HSDPA BAND REL9-2 • M1001C730 - UE SUPPORT FOR DB-HSDPA BAND REL9-3 Expected outcome Values of counters M1006C293 and M1006C294 are updated by a normal DB call setup, and value of counter M1006C295 or M1006C296 is updated by related failure RB setup scenarios.The approximate throughput is 42 Mbit/s. The RAN2179: Dual Band HSDPA

42Mbps feature has been activated successfully.

2.2.4 Deactivating RAN2179: Dual Band HSDPA 42 Mbps

Purpose

(34)

4 Expand the RNC object.

5 Expand the WBTS object.

6 Lock the WCEL where the RAN2179: Dual Band HSDPA 42 Mbps feature needs to be activated:

a) Select the WCEL object

b) Select the cell in the WCell(s) table.

c) From the drop-down menu select "Start ► Change state: Lock".

7 Configure the WCEL object:

a) Select Edit parameters from the WCEL object. b) Set the DBandHSDPAEnabled parameter to Disabled

8 Unlock the WCEL.

9 Repeat the steps 6-8 for all the required cells.

Further information

g

A restart of the RNC and the BTS is not required after the deactivation of this feature.

2.3 RAN2482: Enhanced Virtual Antenna Mapping

2.3.1 RAN2482: Enhanced Virtual Antenna Mapping

Introduction to the feature

With the Virtual Antenna Mapping the WCDMA or HSDPA downlink signals, either non-MIMO or MIMO, are all sent from two physical antennas using a virtual antenna mapping matrix between the virtual antennas and physical antennas. The RAN2482: Enhanced

Virtual Antenna Mapping feature tunes the phase difference between the two physical

(35)

2.3.1.1 Benefits

End-user benefits

The end user benefits from an enhanced application experience because of higher HSDPA DL throughput.

Operator benefits

The operator benefits from higher average DL throughput for HSDPA users, and thus higher average cell throughput.

2.3.1.2 Requirements

Software requirements

Table 20: Software requirements lists software required for this feature. Table 20 Software requirements

RAS Flexi Direct IPA-RNC mcRNC Flexi Direct RNC

OMS Flexi BTS

RU50 Not planned RN8.0 Planned for later releases Not planned OMS3.0 (RU50) WN9.0 Flexi Lite BTS Flexi 10 BTS NetAct MSC SGSN MGW UE Planned for later releases Planned for later releases NetAct 8 EP1 Support not required Support not required Support not required Support not required

Hardware requirements

For Flexi Multiradio BTS WCDMA this feature requires one of the following features: • RAN2382: Flexi BTS Multimode System Module - FSMC

• RAN1016: Flexi BTS Multimode System Module (FSMD)

This feature also requires double Tx and double antenna lines per sector. For supported BTS configurations, see Flexi Multiradio BTS WCDMA Supported and Planned

Configurations Excel in NOLS.

2.3.1.3 Functional description

Virtual Antenna Mapping (VAM) was introduced with the feature RAN1642: MIMO and it can be used in cells with two Tx like in physical MIMO configuration. With the VAM the cell area is covered with two physical antennas using virtual antenna mapping between physical and virtual antennas. The mapping can be used for MIMO and non-MIMO

(36)

configurations. However, VAM solution provides more efficient MIMO performance by transmitting to non-MIMO UEs without transmit diversity but by Virtual Antenna Mapping for power balancing. VAM is beneficial for adding power of two power amplifiers instead of one and introducing polarization diversity when the cross-polarized base station antennas are used.

The RAN2482: Enhanced Virtual Antenna Mapping (E-VAM) feature improves the performance of VAM by controlling the phase difference between the physical antennas. The RAN2482: Enhanced Virtual Antenna Mapping feature tunes the phase difference between the two physical antennas to obtain the best signal quality for HSDPA. The channel quality indicators of active non-MIMO UEs in the cell are used to obtain the best phase difference between the two physical antennas. Tuning of the phase offset is dynamic and automatic. The best benefits are obtained for UEs with one Rx.

The E-VAM can be activated only in cells with two Tx. Cell restart is required whenever the RAN2482: Enhanced Virtual Antenna Mapping feature is activated or deactivated.

2.3.1.4 System impact

Interdependencies between features

There is no interdependencies with other features. Virtual Antenna Mapping (VAM) has to be configured in the cells prior to E-VAM activation.

Impact on interfaces

This feature has no impact on interfaces.

Impact on MML commands

There are no MML commands related to this feature.

Impact on network and network element management tools

Impact on system performance and capacity

The feature increases the DL cell throughput.

2.3.1.5 RAN2482: Enhanced Virtual Antenna Mapping management data

For information on alarm, counter, key performance indicator, and parameter documents, see Reference documentation.

Alarms

There are no alarms related to this feature.

Measurements and counters

(37)

Key performance indicators

Parameters

EVAM in use EVAMInUse WCEL

Sweep time EvamTSweep WCEL Keep time EvamTKeep WCEL Phase offset amount EvamNumPhaseOffset WCEL

Initial Phase Offset EvamDInit WCEL EVAM Capability EVAMCapability WCEL

2.3.1.6 Sales information

BSW/ASW RAS SW component License control in network element

ASW RAN RNC LK

2.3.2 Activating RAN2482: Enhanced Virtual Antenna Mapping

Purpose

Follow this procedure to activate RAN2482: Enhanced Virtual Antenna Mapping feature.

Configuring Virtual Antenna Mapping

Before activating the RAN2482: Enhanced Virtual Antenna Mapping feature, Virtual

Antenna Mapping (VAM) needs to be configured first. The VAM is configured via BTS Site Manager only in MIMO-capable BTSs. After VAM configuration, BTS restart is required. Although VAM was introduced with the RAN1642: MIMO feature, it does not require a license to be configured. Make sure you have access to the BTS Site Manager.

(38)

1 Start the WCDMA BTS Site Manager application and establish the connection to the BTS.

Flexi Multiradio BTS WCDMA is able to autonomously request for missing license file(s) from the NetAct License Manager during the RAN2131: Automatic Licence

Distribution to Flexi BTS feature activation.

Make sure that you have selected Automatic licensing in use checkbox in the Automatic License Distribution Settings page.

g

If the RAN2131: Automatic Licence Distribution to Flexi BTS feature is not activated, the relevant license must be uploaded manually.

2 Upload the configuration plan file from the BTS.

When BTSSM is connected to the BTS, it automatically uploads the current configuration plan file from the BTS.

• Select View ► Commissioning or click Commissioning on the View bar.

3 Configure Virtual Antenna Mapping in a cell.

a) In Commissioning, go to Local Cell Resources page and assign two Tx outputs for a single cell to make MIMO settings section appear. b) In MIMO settings section, select the Virtual antenna mapping in use checkbox and choose MIMO type from the drop-down list.

g

Please note, that following this step allows to configure VAM only in one specific cell. To configure VAM in multiple cells, run this step on each cell separately.

4 Send the commissioning plan file to the BTS. Click Send Parameters button.

You may save the parameters at this point.

5 The new commissioning plan file is automatically activated in the BTS.

BTSSM automatically sends an activation command after finishing the file download.

6 Select Next to complete the commissioning. You can save the commissioning report, if required.

7 Backup commissioning files (if applicable). Select File Backup commissioning files

Save the complete backup commissioning file for further use. Expected outcome

(39)

Activating Enhanced Virtual Antenna Mapping

The RAN2482: Enhanced Virtual Antenna Mapping feature activating procedure does not cause downtime and the feature can be activated at any time of the day.

Make sure you have access to the following applications: • OMS Element Manager

• Application Launcher

• Man-machine interface (MMI)

The RAN2482: Enhanced Virtual Antenna Mapping feature is controlled by the long-term capacity Enhanced Virtual Antenna mapping license key. Capacity license refers to the number of cells. For more information on licensing, see Licensing.

g

Number of activated cells must not exceed the capacity of the

Enhanced Virtual Antenna mapping license.

g

The feature code for this feature is 3732.

To set the feature state to ON, use the following command: • for IPA-RNC:

ZW7M:FEA=3732:ON;

g

Note that in FlexiDirect RNC there is no need to configure the license. 1 Open the OMS Element Manager.

4 Go to the WCEL object by following the path:

RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object

5 Configure the WCEL object: a) Lock the WCEL object.

b) Right-click on the WCEL object and select Edit parameters. c) Set the EVAM in use (EVAMInUse) parameter to Enabled.

The change of the parameter to Enabled consumes the license in terms of number of cells.

(40)

d) Unlock the WCEL object.

Expected outcome

The RAN2482: Enhanced Virtual Antenna Mapping feature has been activated in the RNC. After activating the feature, there is no need to reset the RNC or the BTS.

2.3.3 Verifying RAN2482: Enhanced Virtual Antenna Mapping

Purpose

In a cell which has MIMO hardware capability, E-VAM provides higher average DL throughput for non-MIMO users and thus higher average cell throughput. When compared to VAM, the enhanced VAM is expected to increase stationary one-Rx UE’s average throughput by at least 10%.

2.3.4 Deactivating RAN2482: Enhanced Virtual Antenna Mapping

Purpose

Follow this procedure to deactivate this feature.

4 Go to the WCEL object following the path:

RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► WCEL object

5 Configure the WCEL object: a) Lock the WCEL object.

b) Right-click on the WCEL object and select Edit parameters. c) Set the EVAM in use (EVAMInUse) parameter to Disabled.

The change of the parameter to Disabled frees the license in terms of number of cells.

d) Unlock the WCEL object.

Further information

g

A restart of the RNC and the BTS is not required after the deactivation of the feature.

(41)

2.4 RAN1668: HSUPA Inter-frequency Handover

2.4.1 Description of RAN1668: HSUPA Compressed Mode for

LTE and Inter-frequency Handover

Introduction to the feature

The RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature introduces compressed mode measurements with HSPA active without UL channel type switching to DCH. The feature also introduces basic compressed mode support for performing measurements related to inter-system handover to LTE. Without this feature, during inter-frequency handover in HSPA, before compressed mode is started, switching the UL transport channel from HSUPA to DCH is needed. A switch back to HSPA is performed, after inter-frequency handover using UL DCH.

2.4.1.1 Benefits

End-user benefits

The end-user benefits from fast HSPA inter-frequency handover and higher data throughput during compressed mode.

Operator benefits

This feature benefits the operator as follows: • HSPA inter-frequency handover (HO) is done faster when channel type switching to DCH is not needed first • The inter-system handover (ISHO) and redirection from HSPA to LTE becomes more reliable when LTE cells are measured before ISHO or redirection. • This feature reduces signaling for RNC, Iub, BTS, and the UE as channel type switching to DCH is not needed.

2.4.1.2 Requirements

Software requirements

Table 23: Software requirements lists the software required for this feature. Table 23 Software requirements

RAS Flexi Direct IPA-RNC mcRNC Flexi Direct RNC OMS Flexi BTS RU50 Planned for later releases RN8.0 Planned for later releases Planned for later releases Support not required WN9.0

(42)

Flexi Lite BTS Flexi 10 BTS NetAct MSC SGSN MGW UE Planned for later releases Planned for later releases NetAct8 EP1 Support not required Support not required Support not required 3GPP Rel-6

Hardware requirements

This feature requires the following features:

• RAN2382: Flexi BTS Multimode System Module - FSMC

• RAN1016: Flexi BTS Multimode System Module-FSMD

2.4.1.3 Functional description

The RAN1668: HSUPA Compressed Mode for LTE and Inter- frequency Handover feature introduces HSUPA compressed mode (CM) for LTE and inter-frequency measurements, without UL channel type switching to DCH. HSUPA CM configuration for inter-frequency measurements is achieved using a single-frame method with 7 (or less)-slot transmission gap pattern (TGP). HSUPA CM configuration for LTE measurements is achieved using a double-frame method with 7 (or more)-slot TGP. In NSN implementation the TGP for single frame method is always fixed to 7 slots and for double frame method, the TGP is fixed to 10 slots. Compressed mode is supported while the radio bearers are mapped to E-DCH in uplink and SRBs are mapped on DCH or E-DCH. This also includes the case where DL SRB is mapped to DCH or HSDPA. Avoiding the channel-type switch to UL DCH reduces the total handover execution time up to 1.5s. Also, the high HSUPA throughput can be experienced during compressed mode. For inter-system handover to LTE, only the basic HSUPA compressed mode support is covered in this feature. HSUPA compressed mode for LTE is used by the RAN2980:

Measurement based LTE Layering feature and the RAN2264: Smart LTE Handover feature. All the control, signaling, and RRM decision making of measurement-based redirection and PS HO to LTE are included in those features.

g

In NSN implementation HSUPA CM is never enabled independently. It is always done in tandem with HSDPA CM, that is CM is always enabled in both directions together

g

Note that HSUPA compressed mode is not supported over Iur.

2.4.1.4 System impact

Interdependencies between features

The RAN1276: HSDPA Inter-frequency Handover feature is a prerequisite for using this feature.