RU50 Feature Descriptions of N PDF

Introduction to RU50 features RU50 Feature Descriptions and Instructions
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 Activating RAN2963: Data Session
Profiling
WCDMA RAN Packet Data Transfer
States
RAN2179: Dual Band HSDPA 42 Mbps WCDMA RAN HSDPA in BTS Activating RAN2179: Dual Band
HSDPA 42 Mbps
WCDMA RAN RRM Handover Control
WCDMA RAN RRM HSDPA
WCDMA RAN RRM HSUPA
RAN2482: Enhanced Virtual Antenna This information will be provided in Activating RAN2482: Enhanced Virtual
Mapping future deliveries. Antenna Mapping
RAN1668: HSUPA Compressed Mode WCDMA RAN RRM Handover Control Activating RAN1668: HSUPA
for LTE and Inter-frequency Handover Compressed Mode for LTE and Inter-
WCDMA RAN RRM HSUPA
frequency Handover
WCDMA RAN SRNS Relocation
RAN2980: Measurement Based LTE WCDMA RAN RRM HSUPA Activating RAN2980: Measurement
Layering Based LTE Layering
RAN147: RRC Connection Setup WCDMA RAN RRM Admission Control Activating RAN147: RRC Connection
Redirection Setup Redirection
WCDMA RAN RRM Handover Control
WCDMA RAN RRM HSDPA
WCDMA RAN RRM HSUPA
RNC Overload Control
WCDMA RAN Call Setup and Release
RAN3069: RSRQ-based LTE WCDMA RAN RRM Handover Control Activating RAN3069: RSRQ-based LTE
Reselection Reselection
RAN2264: Smart LTE Handover WCDMA RAN RRM Handover Control Activating RAN2264: Smart LTE
Handover
WCDMA RAN RRM HSUPA
14 DN09146788 Issue: 01
RU50 Feature Descriptions and Instructions Introduction to RU50 features
Table 1 RU50 radio resource management features (Cont.)
WCDMA RAN SRNS Relocation
RAN2881: WCDMA and GSM Layer WCDMA RAN RRM Handover Control Activating RAN2881: WCDMA and
Priorities GSM Layer Priorities
1.2 RU50 telecom features

There are no RU50 features in the Telecom area.
1.3 RU50 transmission and transport features

feature activation:
RU50 features
Table 2 RU50 transmission and transport features
RAN2243: Performance Monitoring WCDMA RAN IP Transport Activating RAN2243: Performance

Based on ETH Service OAM Monitoring Based on ETH Service OAM
1.4 RU50 operability features

feature activation:
RU50 features
Table 3 RU50 operability features
RAN2199: BTS Event Triggered This feature does not have any related Activating RAN2199: BTS Event
Symptom Data Collection descriptions. Triggered Symptom Data Collection
RAN2554: Transport Configuration Fall- This feature does not have any related Activating RAN2554: Transport
back descriptions. Configuration Fall-back
Issue: 01 DN09146788 15
1.5 RU50 performance monitoring features

There are no RU50 features in the performance monitoring area.
1.6 RU50 RNC solution features

feature activation:
RU50 features
Table 4 RU50 RNC solution features
RAN3047: RTT Improvement to This feature does not have related This feature does not have related
enhance user experience descriptions. 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
RAN3017: Additional 6 WCDMA Cell This feature does not have any related Activating RAN3017: Additional 6
Activation descriptions. 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.
16 DN09146788 Issue: 01
RU50 Feature Descriptions and Instructions Introduction to RU50 features
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
• Frequently Used Parameters for SS7 signalling over IP
Issue: 01 DN09146788 17
• 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
18 DN09146788 Issue: 01
RU50 Feature Descriptions and Instructions Radio resource management features
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 OMS BTS Flexi
RNC
RU50 Planned for RN8.0 Planned for Planned for OMS3.0 Support not
later release later release later release (RU50) required
Table 6 Software requirements

Flexi Lite BTS Flexi NetAct MSC SGSN MGW UE
BTS 10
Support not Support not NetAct 8 Support not Support not Support not Support not
required required EP1 required required required required
Hardware requirements
This feature requires no new or additional hardware.
Issue: 01 DN09146788 19
Radio resource management features RU50 Feature Descriptions and Instructions
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
This feature has no impact on interfaces.
20 DN09146788 Issue: 01
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 RRC signalling (RNC)

TO DATA SESSION PROFILING
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 RRC signalling (RNC)

TIME PCH TO DCH
M1006C196 ATTEMPTED PCH TO DCH TRANSITIONS RRC signalling (RNC)

USING UM-RLC
M1006C197 SUCCESSFUL PCH TO DCH RRC signalling (RNC)

TRANSITIONS USING UM-RLC
M1006C198 CELL RESELECTIONS DURING PCH TO RRC signalling (RNC)

DCH TRANSITIONS USING UM-RLC
Issue: 01 DN09146788 21
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 HSChaPrefInDataSesProf RNPS

Session Profiling
Table 10: Modified parameters lists parameters modified by this feature.
Table 10 Modified parameters
RNCOptions RncOptions RNC
Uplink traffic volume measurement low TrafVolThresholdULLow RNPS

threshold
UL traffic volume threshold for SmartTrafVolThrUL WCEL

Smartphone
Downlink traffic volume measurement TrafVolThresholdDLLow WCEL

low threshold
DL traffic volume threshold for SmartTrafVolThrDL WCEL

Smartphone
Downlink NAS signalling volume NASsignVolThrDL WCEL

threshold
22 DN09146788 Issue: 01
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:
• The RNFC-DCHtoPCHEnabled is suggested to be set to the value 1 (enabled).
Issue: 01 DN09146788 23
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.
24 DN09146788 Issue: 01
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.


a) From the drop-down menu select Edit Parameters.
b) Set the DataSessionProfEnabled parameter value to Disable.
5 Save the changes.
2.2 RAN2179: Dual Band HSDPA 42 Mbps

2.2.1 Description of RAN2179: Dual Band HSDPA 42 Mbps
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
WCDMA RAN, Rel. RU20, Feature Descriptions.
Issue: 01 DN09146788 25
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.
RAS Flexi Direct IPA-RNC mcRNC Flexi OMS Flexi BTS

Direct RNC
RU50 Planned for RN8.0 Planned for Planned for OMS3.0 WN9.0
later later later (RU50)
releases releases releases
Flexi Lite Flexi 10 NetAct MSC SGSN MGW UE

BTS BTS
Not Planned for NetAct8 Support not SG8.0 Support not 3GPP Rel-
planned later EP1 required required 9
releases
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
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.
26 DN09146788 Issue: 01
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 UL Band DL Band

Configuration
1 I or VIII I and VIII
2 II or IV II and IV
3 I or V I and V
Issue: 01 DN09146788 27
g Mixed RF module configurations, Rel 1+Rel2 or Rel1+Rel3, cannot be used

with this feature.

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.
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

tools.

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
Alarms
Table 14: Existing alarms lists alarms related to this feature.
28 DN09146788 Issue: 01
Table 14 Existing alarms
Alarm ID Alarm name
3325 INCONSISTENCY IN CONFIGURATION PARAMETERS
7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

M1001C728 UE SUPPORT FOR DB-HSDPA BAND Service Level

REL9-1

REL9-2

REL9-3
M1006C293 RB SETUP ATTEMPT FOR DB-HSDPA RRC signalling
M1006C294 SUCCESSFUL RB SETUP FOR DB- RRC signalling

HSDPA
M1006C295 RB SETUP FAIL FOR DB-HSDPA DUE TO RRC signalling

NO REPLY
M1006C296 RB SETUP FAIL FOR DB-HSDPA DUE TO RRC signalling

UE NACK

Parameters
Dual Band HSDPA Enabled DBandHSDPAEnabled WCEL
Issue: 01 DN09146788 29
Table 16 New parameters (Cont.)
Preferred Frequency Layer for DB-DC- PFLDBHSDNRT PFL

HSDPA NRT
Preferred Layer for DB-DC-HSDPA NRT PrefLayerDBHSDNRT PFL
Preferred Frequency Layer for DB-DC- PFLDBHSDStr PFL

HSDPA Streaming
Preferred Layer for DB-DC-HSDPA PrefLayerDBHSDStr PFL

Streaming
Preferred Frequency Layer for DB-DC- PFLDBHSDAMR PFL

HSDPA AMR
Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMR PFL
Preferred Frequency Layer for DB-DC- PFLDBHSDAMRNRT PFL

HSDPA AMR and NRT
Preferred Layer for DB-DC-HSDPA AMR PrefLayerDBHSDAMRNRT PFL

and NRT
DC HSDPA Enabled DCellHSDPAenabled WCEL
Dual Cell versus MIMO preference DCellVsMIMOPreference RNC
Frame timing offset of a cell Tcell WCEL
ASW RAN RNC LK
30 DN09146788 Issue: 01
2.2.2 Activating RAN2179: Dual Band HSDPA 42 Mbps

Purpose
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.

• 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 Uplink band Downlink

HSDPA Configuration 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.
Issue: 01 DN09146788 31
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.
32 DN09146788 Issue: 01
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
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
Issue: 01 DN09146788 33
3 Expand the ROOT.
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".

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
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
antennas to obtain the best signal quality for HSDPA.
34 DN09146788 Issue: 01
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.
Table 20: Software requirements lists software required for this feature.
RAS Flexi Direct IPA-RNC mcRNC Flexi Direct OMS Flexi BTS
RNC
RU50 Not planned RN8.0 Planned for Not planned OMS3.0 WN9.0
later (RU50)
releases

BTS BTS
Planned for Planned for NetAct 8 Support not Support not Support not Support
later later EP1 required required required not
releases releases required

• 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.
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
Issue: 01 DN09146788 35
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.

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 MML commands

There are no MML commands related to this feature.

tools.

The feature increases the DL cell throughput.
2.3.1.5 RAN2482: Enhanced Virtual Antenna Mapping management data
Alarms

There are no measurements and counters related to this feature.
36 DN09146788 Issue: 01

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
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 you start
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.
Issue: 01 DN09146788 37
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
VAM is configured in chosen cells. Restart the BTS to make changes valid.
38 DN09146788 Issue: 01
Activating Enhanced Virtual Antenna Mapping

Before you start
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.

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.
• for IPA-RNC:
ZW7M:FEA=3732:ON;
g Note that in FlexiDirect RNC there is no need to configure the license.
3 Expand the ROOT.
4 Go to the WCEL object by following the path:

RNC object ► WBTSs folder ► WBTS object ► WCELs folder ► 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.
Issue: 01 DN09146788 39
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
3 Expand the ROOT.
4 Go to the WCEL object following the path:


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.
40 DN09146788 Issue: 01
2.4 RAN1668: HSUPA Inter-frequency Handover

2.4.1 Description of RAN1668: HSUPA Compressed Mode for
LTE and Inter-frequency Handover
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
• 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.

Direct RNC
RU50 Planned for RN8.0 Planned for Planned for Support not WN9.0
later later later required
Issue: 01 DN09146788 41

BTS BTS
Planned for Planned for NetAct8 Support not Support not Support not 3GPP Rel-
later later EP1 required required required 6
releases releases
This feature requires the following features:

• RAN1016: Flexi BTS Multimode System Module-FSMD
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.

The RAN1276: HSDPA Inter-frequency Handover feature is a prerequisite for using this
feature.
42 DN09146788 Issue: 01
The RAN1276: Inter-frequency Handover feature covers the following direct handover
cases:
• DCH/HSDPA to DCH/HSDPA
• DCH/HSDPA to HSUPA/HSDPA
• DCH/HSDPA to DCH/DCH
• DCH/DCH to DCH/HSDPA
• DCH/DCH to HSUPA/HSDPA
With the RAN1668: HSUPA Compressed Mode For LTE and Inter-frequency Handover
feature the following direct handover cases are supported in addition:
• HSUPA/HSDPA to DCH/HSDPA
• HSUPA/HSDPA to HSUPA/HSDPA
• HSUPA/HSDPA to DCH/DCH
HSUPA CM is configured and activated using the following messages:
• over Iub:
– NBAP: Radio Link Setup Request procedure
– NBAP: Radio Link Re-configuration Procedure (Synchronized)
• over Uu:
– RRC: Transport Channel Re-configuration
– RRC: Physical Channel Re-configuration
– RRC: Measurement Control (Setup)
HSUPA CM is deactivated using the following messages:
• over Iub:
– NBAP: Compressed Mode Command
– NBAP: Radio Link Re-configuration Procedure (Synchronized only)
• over Uu:
– RRC: Transport Channel Re-configuration
– RRC: Physical Channel Re-configuration
– RRC: Measurement Control (Release)
g Note that only messages supported by NSN are listed.

tools.

This feature impacts system performance as follows:
Issue: 01 DN09146788 43
• HSPA IFHO is done faster, as channel type switching to DCH is not needed first.
• ISHO and redirection from HSPA to LTE becomes more reliable, as the LTE cells can
be measured before ISHO or redirection.
• The UL throughput is impacted since UE cannot transmit on each slot. The reduction
depends on the configured transmission time interval and whether the UE is
performing intra- or inter-system measurement.
This feature impacts system capacity as follows:
• Signaling for RNC, Iub, BTS, and UE is reduced, as channel type switching to DCH
is not needed for enabling CM.
• In FSM3, a maximum 50% of the users with CM active can be supported, that is, a
maximum 50% of the users can have CM active at the same time.
2.4.1.5 RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency

Handover management data
Alarms

M1002C676 ALLOCATION FOR HSUPA IFHO Traffic (RNC)

COMPRESSED MODE
M1002C677 ALLOCATION DURATION FOR HSUPA Traffic (RNC)

IFHO COMPRESSED MODE
M1002C678 REJECTED HSUPA IFHO COMPRESSED Traffic (RNC)

MODE
M1002C692 ALLO FOR COM MODE LTE Traffic (RNC)
M1002C693 ALLO DURA FOR COM MODE LTE Traffic (RNC)
M1006C312 HSUPA IFHO COMPRESSED MODE FAIL RRC signalling

DUE TO UE
M1006C313 LTE COMPRESSED MODE FAIL DUE TO RRC signalling

UE
M1008C294 HSUPA IFHO ATTEMPTS Intra System Hard Handover

(RNC)
44 DN09146788 Issue: 01
Table 24 New counters (Cont.)
M1008C295 SUCCESSFUL HSUPA IFHO Intra System Hard Handover

(RNC)
M1002C623 ALLOCATION FOR HSDPA IFHO Traffic (RNC)

COMPRESSED MODE
M1002C624 ALLOCATION DURATION FOR HSDPA Traffic (RNC)

IFHO COMPRESSED MODE
M1002C625 REJECTED HSDPA IFHO COMPRESSED Traffic (RNC)

MODE

Table 26: New key performance indicators lists key performance indicators introduced
with this feature.
Table 26 New key performance indicators
KPI ID KPI name
RNC_5301a HSUPA Compressed Mode allocation success rate
There are no modified and existing key performance indicators related to this feature.
Parameters
TGPL for HSPA Inter Frequency TGPLHSPAInterFreq RNHSPA

Measurement
Issue: 01 DN09146788 45
Full name Abbreviated name Managed

object
BTS Support For HSPA CM BTSSupportForHSPACM WBTS
Max number of UEs in HSDPA CM due MaxNumberUEHSPACmHO WCEL

to critical HO
Max number of UEs in HSDPA CM due MaxNumberUEHSPACmNCHO WCEL

to NCHO
Table 29: Related existing parameters lists existing parameters related to this feature.
Table 29 Related existing parameters

object
Serving HS-DSCH cell change and SHO HSDPAMobility RNFC

on/off switch
Gap position single frame GAPPositionSingleFrame RNC
Gap position single frame GAPPositionSingleFrame RNMOBI
Recovery Period Power in UL UplinkRecoveryPeriodPowerMode RNAC

Compressed Mode
Initial transmit power in uplink UplinkInitialTransmitPowerMode RNC

compressed mode
UL Delta SIR1 in compressed mode DeltaSIRUplink RNC
UL Delta SIR1 in compressed mode DeltaSIRUplink WRAB
DL Delta SIR1 in compressed mode DeltaSIRDownlink RNC
DL Delta SIR1 in compressed mode DeltaSIRDownlink WRAB
UL Delta SIR after1 in compressed DeltaSIRAfterUplink RNC

mode
UL Delta SIR after1 in compressed DeltaSIRAfterUplink WRAB

mode
DL Delta SIR after1 in compressed DeltaSIRAfterDownlink RNC

mode
46 DN09146788 Issue: 01
Table 29 Related existing parameters (Cont.)

object
DL Delta SIR after1 in compressed DeltaSIRAfterDownlink WRAB

mode
Compressed Mode: Alternative AltScramblingCodeCM WCEL

scrambling code
Compressed mode master switch CmMasterSwitch RNFC
ASW HSPA RNC LK
2.4.2 Activating RAN1668: HSUPA Compressed Mode for LTE

and Inter-frequency Handover
Purpose
For more information on the feature, see the Description of RAN1668: HSUPA
Compressed Mode for LTE and Inter-frequency Handover in WCDMA RAN, rel. RU50,
feature descriptions.
Before you start
Restart of the RNC is not required after the activation of this feature.
This procedure does not cause downtime, and can be activated at any time of the day.

Before activating this feature, activate the RAN1276: HSDPA Inter-frequency Handover
feature (see Activating RAN1276: HSDPA Inter-frequency Handover).
Before activating this feature make sure that basic HSUPA and HSDPA mobility are
enabled.
This feature is controlled by the long-term ON/OFF license key. For more information on
licensing, see Licensing.
Issue: 01 DN09146788 47
• for IPA-RNC:
ZW7M:FEA=4783:ON;
48 DN09146788 Issue: 01
3 Expand the ROOT.
5 Expand the RNHSPAs folder.
6 Configure the RNHSPA object:

a) Select Edit Parameters from the RNHSPA object.
b) In Packet Scheduler tab set the TGPLHSPAInterFreq parameter to 5 if this
feature is used for inter-frequency handovers or/and set the value of the
TGPLForLTEMeas parameter to 6 if this feature is used for LTE handover or
layering. Set the TGPLAMRHSDPAInterFreq parameter and the
TGPLHSDPAInterFreq parameter to default value 4.
c) Navigate back to the RNC object.
7 Expand the WBTSs folder.
8 Configure the WBTS object:

a) Select Edit Parameters from the WBTS object.
b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM
parameter to "HSPA CM supported".
9 Expand the RNFCs folder.
10 Enable compressed mode by configuring the RNFC object:

a) Select Edit Parameters from the RNFC object.
b) In Packet Scheduler tab set the CmMasterSwitch parameter to "Used".
11 Go to the WCEL object by the following path:

Issue: 01 DN09146788 49
12 Configure the WCEL object.

a) Select Edit Parameters from the WCEL object.
b) In Packet Scheduler tab, set value greater than 0 for the parameter
MaxNumberUEHSPACmHO .
c) In Packet Scheduler tab, set value greater than 0 for the parameter
MaxNumberUEHSPACmNCHO.
2.4.3 Verifying RAN1668: HSUPA Compressed Mode for LTE and

Inter-frequency Handover
Purpose
Before you start

1. Make sure that the RAN1668: HSUPA Compressed Mode for LTE and Inter-
frequency Handover feature is activated in the RNC (see Activating RAN1668:
HSUPA Compressed Mode for LTE and Inter-frequency Handover).
2. Set BTS 1 CELL 2 as inter-frequency adjacent cell of BTS 1 CELL 1.
3. Set the value of FMCI - IFHOcauseCPICHEcNo parameter to 1 ('Enabled') in
FMCI_ID assigned to BTS 1 CELL 1 (HsdpaFmciIdentifier or
NrtFmciIdentifier parameter).
4. Set the value of FMCS - HHoEcNoTimeHysteresis parameter to 6 (100 ms) in
FMCS_ID assigned to BTS1 CELL1 (HspaFmcsIdentifier,
HsdpaFmcsIdentifier, or NrtFmcsIdentifier parameter).
5. Set WCEL parameter MaxNumberUECmHO to value greater than or equal to the
value of WCEL-MaxNumberUEHSPACmHO parameter in BTS1 CELL1 (for the access
path, see step 11 and step 12 in Activating RAN1668: HSUPA Compressed Mode for
LTE and Inter-frequency Handover).
50 DN09146788 Issue: 01
1 Make an NRT interactive call with the UE (Rel-6/Rel-7/Rel-8/Rel-9), RAB on

HSPA in BTS 1 CELL 1 and send data.
2 Adjust the signal of BTS 1 CELL 1, so that it is lower than the threshold value
of the HHoEcNoThreshold parameter.
3 Adjust the signal of BTS 1 CELL 2, so that it is stronger than the signal of BTS
1 CELL 1.
4 Release the call.
5 Collect the log for "step 1", "step 2", "step 3", and "step 4" and analyze the log.
6 Verify that:
• The UE sends out RRC: MEASUREMENT REPORT with Measured Results for
intra-frequency event 1f.
• In NBAP message RADIO LINK RECONFIGURATION PREPARE the values of
IEs in Transmission Gap Pattern Sequence Information are as follows:
TGPS Identifier xx
tGSN xx
tGL1 7
tGD xx
tGPL1 5
uL/DL mode UL/DL
Downlink Compressed Mode Method sf/2
Uplink Compressed Mode Method sf/2
Downlink Frame Type xx
DeltaSIR1 xx
DeltaSIRafter1 xx
g “xx” means that the value of the IE is not relevant for verifying this
feature.
• In RRC message PHYSICAL CHANNEL RECONFIGURATION the values of IEs

are as follows:
tgp-SequenceList {{
tgpsi xx,
tgps-Status activate : {
tgcfn xx },
tgps-ConfigurationParams {
tgmp fdd-Measurement,
tgprc xx,
tgsn xx,
tgl1 7,
tgd xx,
tgpl1 5,
rpp xx,
itp xx,
Issue: 01 DN09146788 51
ul-DL-Mode ul-and-dl : {
ul sf-2,
dl sf-2 },
dl-FrameType dl-FrameTypeA,
deltaSIR1 xx,
deltaSIRAfter1 xx }}}
g “xx” means that the value of the IE is not relevant for verifying this
feature.
• Counters M1002C676 ALLO_CM_HSUPA_IFHO and M1002C623

ALLO_CM_HSDPA_IFHO are updated: 1 is added to their value.
Expected outcome
HSUPA compressed mode starts successfully and call release is normal. Log’s data are
as specified above and counters are updated.
2.4.4 Deactivating RAN1668HSUPA Compressed Mode for LTE

and Inter-frequency Handover
Purpose
3 Expand the ROOT.
5 Expand the WBTSs folder.
6 Configure the WBTS object:

a) Select Edit Parameters from the WBTS object.
b) In Packet Scheduler tab set the value of the BTSSupportForHSPACM
parameter to "Only DCH CM supported" or "HSDPA CM supported".
Further information
After deactivating the feature, set the feature state to OFF.
52 DN09146788 Issue: 01
2.5 RAN2980: Measurement Based LTE Layering

2.5.1 Description of RAN2980: Measurement Based LTE
Layering
In the current system implementation, the RAN2717: Smart LTE Layering feature
supports redirection from WCDMA to LTE. This redirection is performed blindly, that is
without prior measurements of LTE layer. It is a good alternative when, for example,
WCDMA and LTE cells are co-located and have largely overlapping coverage areas.
However, UEs could face problem in cell reselection which can cause unsatisfying end-
user experience.
The RAN2980: Measurement Based LTE Layering feature supports the redirection of UE
to LTE layer only if measurement results indicate that LTE-capable UE could camp on
LTE cell successfully. This ensures seamless LTE camping even if the WCDMA cell has
only partial LTE coverage. Both FDD-LTE and TDD-LTE are supported.
2.5.1.1 Benefits
End-user benefits
Ensuring a successful LTE camping improves end-user experience.
Operator benefits
Operator benefits from having two types of WCDMA to LTE redirections available: with
and without a measurement. Operator can choose if the trigger activates with- or without-
measurement-based redirection.
RNC
RU50 Planned for RN8.0 Planned for Planned for OMS3.0 WN9.0
Issue: 01 DN09146788 53

BTS BTS
Planned for Planned for NetAct 8 Support not Support not Support not 3GPP
later later EP1 required required required Rel-8
releases releases


Functional overview
RRC connection release with redirection command to LTE can be used for moving LTE-
capable UE to LTE, if compressed mode measurements indicate that LTE coverage is
available. Each of the following events triggers compressed mode measurements for
LTE:
• RCC state change from Cell_DCH to Cell_FACH, Cell_PCH, or URA_PCH

• channel type change from HSDPA/HSPA to DCH/DCH CTS
• CS call release when UE has CS and PS connection active
• periodic trigger with operator-definable timer:
When LTE-capable UE enters the Cell_DCH state having only PS RAB(s), its timer
(controlled with LTEPeriodicTriggerTimer parameter) is set. At the expiry of
timer, measurements for redirection to LTE are started and timer is set again. If
measurement results lead to decision to redirect UE to LTE system, UE is then
redirected. If the measurement results do not trigger UE’s redirection to LTE and UE
still continues data activity, then at the expiry of the timer the new timer is set and
measurements are started again.
First three of the above mentioned triggers are also used in the RAN2717: Smart LTE
Layering feature. The RAN2980: Measurement Based LTE Layering feature introduces
the fourth trigger for UEs keeping long Cell_DCH reservations for PS services. Note that
when the RAN2980: Measurement Based LTE Layering feature is active, all four triggers
are valid and there is no need to have the RAN2717: Smart LTE Layering feature
installed separately.
In uplink, DCH is used during compressed mode. HSPA compressed mode, also
including HSUPA compressed mode, is supported by the RAN1668: HSUPA
Compressed Mode for LTE and Inter-frequency Handover feature. If the RAN1668:
HSUPA Compressed Mode for LTE and Inter-frequency Handover feature is not
implemented in the network, the RAN2980: Measurement Based LTE Layering feature
supports HSDPA/DCH, and DCH/DCH. If there is HSUPA (E-DCH) in uplink, then it is
reconfigured to DCH, before initiating the compressed mode measurements.
54 DN09146788 Issue: 01
LTE-capable UEs are checked for their measurement capabilities. UEs with dual receiver
do not require compressed mode for creating gaps to listen to other frequencies. For
such UEs, compressed-mode-related information is not required and thus not sent to
them.
If WCDMA cell load is not high and users can be provided good enough experience
within WCDMA layer, measurements and redirection to LTE can be bypassed. RNC load
level parameter can be used to define if load is low enough for keeping UEs in WCDMA.
With the RAN2980: Measurement Based LTE Layering feature operator can:
• enable LTE redirection without measurements for the first three redirection triggers
(also provided with the RAN2717: Smart LTE Layering feature) and measurement-
based redirection to LTE for the periodic trigger
• establish measurement-based redirection to LTE for all four redirection triggers
• select the frequencies to which UEs in Cell_DCH state are redirected in LTE system
as well as define camping priorities for those frequencies
• exclude some LTE carrier frequencies from LTE target camping layers
• disable the WCDMA cell load check which will result in automatic LTE redirection
every time the LTE coverage is available

The RAN2067: LTE Interworking feature provides support for LTE cell reselection in idle
mode Cell_PCH and URA_PCH states.
This feature affects Uu and Iub interfaces and uses standard signaling procedures.
Impact on commands

tools.

This feature has no impact on system performance or capacity.
2.5.1.5 RAN2980: Measurement Based LTE Layering management data
Alarms
Issue: 01 DN09146788 55

M1001C747 RRC SETUP ATT CSFB Service Level
M1001C748 RC SETUP ACCESS FAIL CSFB Service Level
M1001C749 RRC ACCESS RELEASE CSFB Service Level
M1001C750 RRC SETUP ATT REPEAT CSFB Service Level
M1006C310 RRC CONN RELEASE LTE REDIR IN DCH RRC signaling
M1010C237 LTE CARRIER NOT FOUND FOR REDIRECTION Inter System Hard
Handover
M1010C238 LTE REDIRECTION STARTED AFTER Inter System Hard

MEASUREMENT Handover
M1010C239 DURATION OF LTE CARRIER MEASUREMENT Inter System Hard

Handover

Parameters

object
FMCL Identifier FMCLId RNC

FMCL
Change origin for FMCL object FMCLChangeOrigin FMCL
LTE Measurement Averaging Window LTEMeasAveWindow FMCL
LTE Maximum Measurement Period LTEMaxMeasPeriod FMCL
LTE Minimum Measurement Interval LTEMinMeasInterval FMCL
56 DN09146788 Issue: 01

object
LTE Neighbor Carrier Frequency Search LTENcarrFreqSearchPeriod FMCL

Period
Measurement Based LTE Layering and LTELayeringMeasAndHOActivatio WCEL

Handover Activation n
LTE Periodic trigger timer LTEPeriodicTriggerTimer RNC
Adjacent LTE Selected Frequency AdjLSelectFreq ADJL

( EARFCN)
WCDMA Cell Load Threshold WCDMACellLoadThreshold WCEL
FMCL Identifier FMCLIdentifier WCEL
Adjacent LTE Frequency Priority AdjLFreqPriority HOPL
LTE Carrier frequency selection AdjLMinRSRPLevel HOPL

Minimum Rx Power level
LTE Carrier frequency selection AdjLMinRSRQLevel HOPL

Minimum Rx qual level
Transmission Gap Length for LTE TGPLForLTEMeas RNHSPA

Carrier frequency measurements

object
RNC Options RncOptions RNC
Smart LTE Layering Enabled SmartLTELayeringEnabled WCEL
Smart LTE Layering RSCP threshold SmartLTELayeringRSCP WCEL
Smart LTE Layering NRT user amount SmartLTELayeringUA WCEL

threshold
Smart LTE Layering service control SmartLTELayeringServ RNMOBI
Timer for Smart LTE Layering Preventio SmartLTELayeringPrevT RNMOBI
Issue: 01 DN09146788 57
Table 34 Modified parameters (Cont.)

object
Smart LTE Layering Target System SmartLTELayeringTSysSel WCEL

Selection
ASW RAN RNC LK
2.5.2 Activating RAN2980: Measurement Based LTE Layering

Purpose
Follow this procedure to activate the RAN2980: Measurement Based LTE Layering
feature.
Before you start
After activating this feature there is no need to restart neither the RNC, nor the BTS.
Activating procedure does not cause downtime and the feature can be activated at any
time of the day.
Activate the license of the RAN2067: LTE Interworking feature using LTE Interworking
license key. For more information, see Activating RAN2067: LTE Interworking.
Activate the license of the RAN2980: Measurement Based LTE Layering feature using
Measurement Based LTE Layering license key.
• for IPA-RNC:
ZW7M:FEA=4839:ON;
For more information on managing licenses, see Licensing.

Before activating the RAN2980: Measurement Based LTE Layering feature, the LTE
neighbors must be configured according to the RAN2067: LTE Interworking feature.
HSDPA compressed mode measurements for LTE requires setting the
BTSSupportForHSPACM WBTS parameter value to 1. If HSDPA CM is not activated,
then the HS-DSCH to DCH channel switching is needed before starting the LTE
measurements. Note that if the RAN1276: HSDPA Inter-frequency Handover feature
license is ON, HSDPA Compressed Mode measurements for IFHO to the BTS in
question is activated, provided the BTSSupportForHSPACM parameter value is set to 1.
The HSUPA compressed mode measurement support for LTE is provided with the
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If
that feature is not activated, then the E-DCH to uplink DCH channel switching is needed
58 DN09146788 Issue: 01
before starting the LTE measurements. The HSPA (HSUPA/HSDPA) compressed mode
measurements for LTE requires that the license of RAN1668: HSUPA Compressed Mode
for LTE and Inter-frequency Handover feature is ON and the value of the
BTSSupportForHSPACM parameter is set to 2.
Configure the following database objects and relevant parameters for the RAN2980:
Measurement Based LTE Layering feature and attach them to the WCDMA cell:
• FMCL parameters for controlling inter-RAT (LTE) measurement:

– LTEMeasAveWindow
– LTEMaxMeasPeriod
– LTEMinMeasInterval
– LTENcarrFreqSearchPeriod
• HOPL parameters for controlling inter-RAT (LTE) neighbor frequency:

– AdjLFreqPriority
– AdjLMinRSRPLevel
– AdjLMinRSRQLevel
• ADJL parameters for defining inter-RAT (LTE) neighbor frequency:

– AdjLEARFCN
– AdjLMeasBw
• WCEL parameters for identifying the Measurement Control Parameter Set and
controlling redirection triggers:
– FMCLIdentifier
– LTELayeringMeasActivation
g Note that the listed parameters are optional and have a default value. Only the
AdjLEARFCN ADJL parameter, for defining the E-UTRA Absolute Radio
Frequency Channel Number of the neighboring E-UTRA frequency, is
mandatory.
g Redirection to LTE happens only when the cell has at least one Cell_DCH
adjacency defined with the AdjLSelectFreq RNC/WBTS/WCEL/ADJL
parameter. Operator can exclude chosen frequency from redirection target
using the AdjLSelectFreq parameter. In order to use redirection to LTE,
value 0 for the AdjLSelectFreq parameter must be used for at least one LTE
frequency configured in the cell.
g Ensure that RSRP and RSRQ thresholds in both LTE and WCDMA networks
are aligned. Corresponding parameters related to this feature are
AdjLMinRSRPLevel and AdjLMinRSRQLevel.
Additionally, the following parameters can be used for tuning the RAN2980:
Measurement Based LTE Layering feature:
• LTEPeriodicTriggerTimer RNC parameter

• SmartLTELayeringServ RNMOBI parameter
• LTETargetFreqCriterion RNMOBI parameter
• LTELayerCellHSLoad WCEL parameter
• SmartLTELayeringUA WCEL parameter
Issue: 01 DN09146788 59
• SmartLTELayeringTSysSel WCEL parameter

• SmartLTELayeringRSCP WCEL parameter
g It is crucial to ensure the correctness of AdjLEARFCN and AdjLMeasBw

neighboring LTE parameters while configuring, because RNC O&M is not able
to verify the values of these parameters.
2 Go to Topology and expand the ROOT directory.
3 Expand the RNC object and then the WBTS object.

a) Right-click on the WCEL object and select Edit parameters.
b) In Handover Control tab, set the value of the SmartLTELayeringEnabled
parameter to Enabled.
5 In Handover Control tab, set the value LTELayeringMeasActivation

parameter to:
• 0 for setting T1, T2, T3 as triggers for redirection without measurements and T4
as a trigger for redirection with measurements
• 1 for setting T1, T2, T3, T4 as triggers for redirection with measurements
Further information
SmartLTELayeringEnabled WCEL parameter enables triggers (T) for the RAN2980:
Measurement Based LTE Layering feature as follows:
• value (0) = T1, T2, T3, and T4 disabled

• value (1) = T1 enabled
• value (2) = T1 and T2 enabled
• value (4) = T1, T2, and T3 enabled
• value (8) = T1, T2, T3, and T4 enabled
where the triggers are:
• T1: RRC state change Cell_DCH to CCH

• T2: HSDPA/HSPA to DCH/DCH CTS
• T3: CS RAB release
• T4: periodic trigger
60 DN09146788 Issue: 01
For more information on triggers, see Description of RAN2980: Measurement Based LTE
Layering.
The RAN2980: Measurement Based LTE Layering feature is supported for the following
PS QoS classes:
• interactive (NRT)
• background (NRT)
• streaming (RT)
2.5.3 Verifying RAN2980: Measurement Based LTE Layering

Purpose
Follow these tips to verify that the RAN2980: Measurement Based LTE Layering feature
works properly in the network.
Redirection to LTE, provided with the RAN2980: Measurement Based LTE Layering
feature, is done after successful LTE measurements and sending the UE the RRC
CONNECTION RELEASE message by the RNC. Feature's performance can be verified
with the following counters:
• M1006C310 RRC CONN RELEASE LTE REDIR IN DCH

which is updated when the RNC sends RRC connection release message to the UE,
because of LTE redirection started by periodic trigger
• M1010C238 LTE REDIRECTION STARTED AFTER MEASUREMENT
which is updated when the LTE carrier measurement performed by the UE finds a
carrier frequency with the quality acceptable to perform redirection and the RNC
initiates the redirection procedure
g Note that for verification using counters, the end-user has to make a PS call.
Expected outcome
Redirection to LTE is successful and visible in the listed counters.
Unexpected outcome
Redirection to LTE is not successful and is visible in the following counter:
• M1010C237 LTE CARRIER NOT FOUND FOR REDIRECTION

which is updated when the LTE carrier frequency measurement performed by the UE
does not result in a carrier frequency with the quality acceptable to perform
redirection
Further information
g The following counter can be used for more detailed monitoring the
RAN2980: Measurement Based LTE Layering feature:
• M1010C239 DURATION OF LTE CARRIER MEASUREMENT
Counters related to CS Fallback:
• M1001C747 RRC SETUP ATT CSFB

• M1001C748 RRC SETUP ACCESS FAIL CSFB
Issue: 01 DN09146788 61
• M1001C749 RRC ACCESS RELEASE CSFB

• M1001C750 RRC SETUP ATT REPEAT CSFB
2.5.4 Deactivating RAN2980: Measurement Based LTE Layering

Follow this procedure to deactivate the RAN2980: Measurement Based LTE Layering
feature.

b) In Handover Control tab, set the value of the SmartLTELayeringEnabled
parameter to Disabled.
2.6 RAN147: RRC Connection Setup Redirection

2.6.1 Description of RAN147: RRC Connection Setup
Redirection
In case the RRC connection is rejected due to the admission control reasons, the RNC
sends the UE to 2G or 3G, to a new frequency for the next try. If RRC connection is
rejected due to the signaling unit overload reason, the RNC sends UE to 2G.
2.6.1.1 Benefits
End-user benefits
Better subscriber experience because of less call setup delay.
Operator benefits
This feature helps to reduce call setup delay in case of congestion.
Software requirements lists the software required for this feature.
62 DN09146788 Issue: 01
RAS Flexi Direct IPA-RNC mcRNC OMS BTS Flexi Flexi Lite
RU50 Not planned RN8.0 Planned for OMS3.0 Support not Support
later (RU50) required not
releases required
BTS Flexi 10 NetAct MSC SGSN MGW UE
Support not NetAct 8 EP1 Support not Support not Support not Support not
required required required required required
This feature does not require any new or additional hardware.

Functional overview
The RAN 147: RRC Connection Setup Redirection feature enables to redirect an RRC
connection to another 3G frequency or GSM. The redirection happens if admission
control rejects the RRC connection request. The Figure 2: RRC connection setup
redirection illustrates the described situation.
Figure 2 RRC connection setup redirection
The redirection info sent in the RRC message RRC CONNECTION REJECT depends on
the target system. If the target system is GSM, then the redirection info is a list of target
cells for the UE with release rel-6 or newer. If the UE release is older than rel-6, then the
redirection info is just the target system, for example, GSM.
Issue: 01 DN09146788 63
If the target system is 3G, then the redirection info is a target frequency (UTRA Absolute
Radio Frequency Channel Number). The inter-frequency neighbor cell AdjiUARFCN
parameter defines it for downlink. The RNC calculates it for uplink in legacy way from
value of the AdjiARFCN parameter and duplex distance used in the RF band.
RRC connection sets up on Cell_DCH state, when the redirection is triggered. RRC
connection can be setup also on common channels. For more information, see RAN1797
Common channel setup.
There is no Admission control in common channels thus it cannot fail, when RRC
connection is setup on common channels.
RRM decides about the target system on the basis of establishment cause of the RRC
Connection Request and the new management RRCReDirTargetSys parameter. The
RRCReDirTargetSys parameter defines the target system for each establishment
cause. Also, if the RNC tries to redirect the RRC connection into GSM but UE is not able
to camp to the new target cell in GSM, then the RNC is allowed to redirect the RRC
connection into 3G. Value for each parameter need to be planned based on functionality
of actual establishment cause and available radio access technologies. Especially need
to be considered if this certain functionality can be performed on GSM.
The RRCReDirBlockedCellAllowed parameter defines if cells, which are marked as
blocked in SLHO or MBLB procedure, should not be used as a target cell of an RRC
connection redirection. If MBLB load information is not available, then only SLHO
information (loaded or not loaded) is used. If both MBLB and SLHO load information is
not available, then SLHO and MBLB blocked cells are not reduced from the target cell
list, although the RRCReDirBlockedCellAllowed parameter indicates that the
blocked cells should not be used as a target cell of an RRC connection redirection.
The AdjiPriorityReDir parameter defines priority for each inter-frequency cell in the
neighbor cell list if congestion of Iub transmission or BTS causes the rejection.
The AdjiPriorityQuality parameter defines priority for cells in the neighbor cell list
if the RRC connection is rejected because of downlink power, uplink interference or
downlink spreading code congestion. The frequency of feasible target cell with the
highest priority is selected as the target frequency for redirection.
For more information, see the Figure 3: Selection process of redirection information.
Figure 3 Selection process of redirection information
64 DN09146788 Issue: 01
If the RNC signaling unit overload is the reason to reject the RRC Connection Request,
UE can be redirected to GSM network without target cell list.

There are no interdependencies between this and any other feature.
Impact on commands

tools.

2.6.1.5 RAN147: RRC Connection Setup Redirection management data
Alarms

M1006C305 RRC_CONN_REDIR_GSM_FAIL 1006 - RRC signalling (RNC)
M1006C70 RRC_CONN_REJ_DIR_SETUP 1006 - RRC signalling (RNC)
Issue: 01 DN09146788 65
Table 37 Related existing counters (Cont.)
M1001C618 RRC CONN SETUP FAIL DUE TO ICSU 1001 - RRC signaling (RNC)
OVERLOAD

Parameters
Enabling RRC connection Redirection RRCReDirEnabled RNFC
RRC Connection Redirection Target RRCReDirTargetSys WCEL

System
RCC Connection Redirection Target TargetsystemConversationalC WCEL

System for conversational causes all
RRC Connection Redirection Target TargetsystemStreamingCall WCEL

System for streaming causes
RCC Connection Redirection Target TargetsystemInteractiveCall WCEL

System for interactive causes
RCC Connection Redirection Target TargetsystemBackgroundCall WCEL

System for background causes
RCC Connection Redirection Target TargetsystemSubscribedTraffi WCEL

System for subscribed traffic causes c
RCC Connection Redirection Target TargetsystemEmergencyCall WCEL

System for emergency call causes
RCC Connection Redirection Target TargetsysteminterRATreselecti WCEL

System for inter-RAT re-selection on
causes
RCC Connection Redirection Target TargetsysteminterRATchangeo WCEL

System for inter-RAT cell change order rder
causes
RCC Connection Redirection Target Targetsystemregistration WCEL

System for registration causes
66 DN09146788 Issue: 01
RCC Connection Redirection Target TargetsystemDetach WCEL

System for detach causes
RCC Connection Redirection Target TargetsystemHighPrioritySign WCEL

System for high priority signalling alling
causes
RCC Connection Redirection Target TargetsystemLowPrioritySigna WCEL

System for low priority signalling causes lling
RCC Connection Redirection Target Targetsystemreestablishment WCEL

System for call re-establishment causes
RCC Connection Redirection Target Targetsystemunknown WCEL

System for unknown causes
RCC Connection Redirection Target TargetsystemMBMSreception WCEL

System for MBMS reception causes
RCC Connection Redirection Target TargetsystemMBMSrbrequest WCEL

System for MBMS ptp RB request
causes
RRC Connection Redirection allows RRCReDirBlockedCellAllowed RNMOBI

blocked cells
Neighbour cell priority for RRC AdjiPriorityReDir HOPI

Connection Redirection
Ncell Priority for Quality IFHO AdjiPriorityQuality HOPI
Ncell Priority for Coverage HO AdjgPriorityCoverage HOPG
RNC Options RncOptions IADA
Issue: 01 DN09146788 67
ASW RAN RNC LK
2.6.2 Activating RAN147: RRC Connection Setup Redirection

2.6.2.1 Activating RAN147: RRC Connection Setup Redirection due to
admission control reasons
Purpose
For more information on the feature, see the RAN147: RRC Connection Setup
Redirection Feature Description.
Before you start

Restart of the RNC is not required after activation of this feature.
This procedure does not cause downtime and it can be activated at any time of the day.


Licensing.
• for IPA-RNC:
ZW7M: FEA=4780:ON;


a) From the drop-down menu select Edit ► Edit Parameters.
68 DN09146788 Issue: 01
b) Set the RRCReDirEnabled parameter value to Enabled(AC 1 or 3).

c) The value of the target system for redirection (both primary and secondary)
should be defined, and its value depends on the value of the Establishment
Cause received in the message RRC: RRC CONNECTION REQUEST.
The RRCReDirTargetSys (under WCEL objects) parameter value primary
target system secondary target system:
• 0 none,
• 1 GSM 3G,
• 2 3G GSM,
• 3 GSM none,
• 4 3G none.
5 Save the changes.

b) If the UE should be redirected to UMTS, then ADJI's should to be created. If the
redirection should be done to GSM, then ADJG's should be created for WCEL.
2.6.2.2 Activating RAN147: RRC Connection Setup Redirection due to

signaling unit overload
Purpose
For more information on the feature, see the RAN147: RRC Connection Setup
Redirection Feature Description.
Before you start

Restart of the RNC is not required after activation of this feature.
This procedure does not cause downtime and it can be activated at any time of the day.


Licensing.
• for IPA-RNC:
ZW7M: FEA=4780:ON;
Issue: 01 DN09146788 69


b) Set the RRCReDirEnabled parameter value to Enabled(AC 2 or 3).
c) The value of the target system for redirection (both primary and secondary)
should be defined, and its value depends on the value of the Establishment
Cause received in the message RRC: RRC CONNECTION REQUEST.
The RRCReDirTargetSys (under WCEL objects) parameter value primary
target system secondary target system:
• 0 none,
• 1 GSM 3G,
• 2 3G GSM,
• 3 GSM none,
• 4 3G none.
5 Save the changes.

b) If the UE should be redirected to UMTS, then ADJI's should to be created. If the
redirection should be done to GSM, then ADJG's should be created for WCEL.
2.6.3 Verifying RAN147: RRC Connection Setup Redirection

2.6.3.1 Verifying RAN147: RRC Connection Setup Redirection due to
Purpose
Before you start

Make sure you have access to the following application:
• RNW Measurement Management
70 DN09146788 Issue: 01
1 UE1 sends RRC Connection Request with cause

"originatingInteractiveCall" to WBTS1 CELL-1. RRC Connection of UE1
is rejected due to DL Power.
Verify, if RNC sends RRC: RRC Connection Reject to UE with redirection info
specifying frequencyInfo. Since Primary Target System (selected on the base of
HOPI - AdjiPriorityQuality), defined for RRCReDirTargetSys-
TargetsystemInteractiveCall is 3G. The specified target frequency of WBTS1
CELL-3 has the highest priority defined by HOPI2- AdjiPriorityQuality.
2 RRC connection setup successfully on WBTS1 CELL-3 with cause

"originatingInteractiveCall" for UE1.
3 Counters verification.
The counters are updated as follows:
Table 41 Counters verification
ID Name Value Updated objects
M1006C70 RRC CONN 1 WBTS1 CELL-1

REJECT DUE TO
RRC
CONNECTION
SETUP
REDIRECTION
2.6.3.2 Verifying RAN147: RRC Connection Setup Redirection due to

signaling unit overload reasons
Purpose
Before you start

Make sure you have access to the following application:
1 Make sure that there is very heavy CPU load in signaling unit (ICSU or USCP).
2 UE1 sends RRC Connection Request.

Verify, if the RNC sends RRC: RRC Connection Reject to UE with
redirection info / Inter-RAT info = GSM.
3 Counters verification.
The counters are updated as follows:
Issue: 01 DN09146788 71
Table 42 Counters verification
ID Name Value Updated objects

SETUP FAIL DUE
TO ICSU
OVERLOAD

REJECT DUE TO
RRC
CONNECTION
SETUP
REDIRECTION
2.6.4 Deactivating RAN147: RRC Connection Setup Redirection

2.6.4.1 Deactivating RAN147: RRC Connection Setup Redirection due to
Purpose
Before you start



b) Set the RRCReDirEnabled parameter value to Disabled (0 or 2).
5 Save the changes.
72 DN09146788 Issue: 01
6 Open the MMI session.

Open the Secure MMI Window application from the Application Launcher.
Alternatively, any other configured MMI client can be used.
7 To deactivate the feature execute the follows:
• To set the feature state to OFF, set the value of the RRCReDirEnabled to 0.
• To enable the signaling unit overload, set the value of the RRCReDirEnabled to
2.
g For more information, see

Deactivating RAN147: RRC Connection Setup Redirection due to signaling
unit overload reasons
For IPA-RNC, use the following MML command:
ZW7M: FEA=4780:OFF;
2.6.4.2 Deactivating RAN147: RRC Connection Setup Redirection due to

signaling unit overload reasons
Purpose
Before you start



b) Set the RRCReDirEnabled parameter value to Disabled (0 or 1).
5 Save the changes.
Issue: 01 DN09146788 73
6 Open the MMI session.

Open the Secure MMI Window application from the Application Launcher.
Alternatively, any other configured MMI client can be used.
7 To deactivate the feature execute the follows:
• To set the feature state to OFF, set the value of the RRCReDirEnabled to 0.
• To enable the admission control modifications, set the value of the
RRCReDirEnabled to 1.
g For more information, see

Deactivating RAN147: RRC Connection Setup Redirection due to admission
control reasons
For IPA-RNC, use the following MML command:
ZW7M: FEA=4780:OFF;
2.7 RAN3069: RSRQ-based LTE Reselection

2.7.1 Description of RAN3069: RSRQ-based LTE Reselection
The RAN3069: RSRQ-based LTE Reselection feature provides support for LTE cell
reselection based on the reference signal received quality (RSRQ).
2.7.1.1 Benefits
End-user benefits
This feature maximizes end-user’s LTE experience.
Operator benefits
This feature assures smooth WCDMA-LTE interworking when in LTE network RSRQ
criteria are used for cell reselection.
74 DN09146788 Issue: 01
RNC
RU50 Not planned RN8.0 Planned for Not planned OMS3.0 Support
later (RU50) not
releases required

BTS BTS
Support not Support not NetAct 8 Support not Support not Support not 3GPP
required required EP1 required required required Rel-9

Functional overview
In current system implementation the RAN2067: LTE Interworking feature supports
reference symbol received power (RSRP)-based LTE reselection. The RAN3069: RSRQ-
based LTE Reselection feature introduces an upgrade by including quality thresholds for
LTE priority-based cell reselection. These quality thresholds are specified in 3GPP Rel-9
and they include the UTRA serving cell Ec/N0 threshold and E-UTRA neighbor cell
RSRQ quality threshold. These thresholds are broadcast in the system information block
type 19 (SIB19).

This feature requires the RAN2067: LTE Interworking feature.
Impact on commands

tools.

Issue: 01 DN09146788 75
2.7.1.5 RAN3069: RSRQ-based LTE Reselection management data
Alarms

There are no measurements or counters related to this feature.

Parameters
Table 44: New parameters lists parameters introduced with this feature and the
corresponding SIB19 parameters specified in 3GPP Rel-9.
Full name Abbreviated name SIB19 IE Managed

object
Thresh serving low 2 Threshservlow2 Threshserving,low2 WCEL
Qqualmin for LTE cell reselection AdjLQqualminEUTRA QqualminEUTRA HOPL
Threshold high 2 for LTE cell reselection AdjLThreshigh2 Threshx,high2 HOPL
Threshold low 2 for LTE cell reselection AdjLThreslow2 Threshx,low2 HOPL
ASW1) RAN RNC LK
1)the RAN2067: LTE Interworking feature license also controls the RAN3069: RSRQ-
based LTE Reselection feature
2.7.2 Activating RAN3069: RSRQ-based LTE Reselection

Purpose
Follow this procedure to activate the RAN3069: RSRQ-based LTE Reselection feature.
76 DN09146788 Issue: 01
Before you start

time of the day.
g The RAN2067: LTE Interworking feature license also controls the

RAN3069: RSRQ-based LTE Reselection feature. Activate the
RAN2067: LTE Interworking feature controlled by the license key
LTE Interworking. For more information, see
Activating RAN2067: LTE Interworking.
For information on managing licenses, see Licensing.

To provide seamless priority-based cell reselection between GSM, WCDMA, and LTE,
make sure to admit each Radio Access Technology a different priority:
• AbsPrioCellReselec WCEL parameter, introduced with the RAN2067:LTE

Interworking feature, defines the priority of the WCDMA serving cell (UTRA priority
info list/UTRA Serving Cell IE)
• AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881:
WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequency
priority (UTRA priority info list/UTRAN FDD Frequencies IE)
• AdjgAbsPrioCellReselec HOPG parameter, introduced with the RAN2881:
WCDMA and GSM Layer Priorities feature, defines the GSM priority (GSM priority
info list/GSM Priority Info IE)
• AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE
Interworking feature, defines the LTE priority (E-UTRA frequency and priority info
list/E-UTRA frequency and priority IE)
g Priority-based cell-reselection between GSM and WCDMA radio technologies is

provided by the RAN2881: WCDMA and GSM Layer Priorities feature.
WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority value
should be given for each inter-frequency WCDMA neighbor. If more than one value is
given, the highest priority is broadcast in SIB19 message.
g If quality criteria are chosen to be used for LTE absolute-priority-based cell

reselection, ensure that both Threshx, high2 (AdjLThreshigh2 HOPL
parameter) and Threshx, low2 (AdjLThreslow2 HOPL parameter) are
configured at the same time and broadcast in SIB19. Otherwise UE is not using
these parameters. Also, ensure that priorities for which both Threshx, high2
and Threshx, low2 are provided in SIB19 are always different from the
priorities for which these parameters are not provided in SIB19. By default
Threshx, high2 and Threshx, low2 are not broadcast in SIB19.
g Note that the activation procedure for the

RAN3069: RSRQ-based LTE Reselection feature is the same as for the
RAN2067: LTE Interworking feature.
Issue: 01 DN09146788 77

b) In System Info tab, set the values of LTECellReselection parameter to
Enabled.
Further information
g Note that the UE does not use Hierarchical Cell Structure (HCS) for inter-
frequency or inter-RAT reselection if absolute-priority-based cell reselection is
used.
2.7.3 Verifying RAN3069: RSRQ-based LTE Reselection

Purpose
Follow these tips to verify that the RAN3069: RSRQ-based LTE Reselection feature
Before you start

To verify the usage of the quality criteria for LTE absolute-priority-based cell reselection,
you also need to activate and verify the RAN2067: LTE Interworking feature. For more
information, see Activating RAN2067: LTE Interworking and Verifying RAN2067: LTE
Interworking.
g There are no counters involved in cell reselection process. The UE reselects the
cell according to the parameters broadcast by the network in SIB19 message.
When the RAN3069: RSRQ-based LTE Reselection feature is active, it is visible in the
content of SIB19 message. After activating this feature and ascribing values to the
parameters listed in RAN3069: RSRQ-based LTE Reselection management data
section, the E-UTRA frequency and priority info list/E-UTRA frequency and priority
information elements will be broadcast in SIB19 message.
Content of SIB19 message can be monitored by using UE and network protocol
analyzer.
Further information
Camping on a desired layer is performed by the UE using SIB19 parameters. Cell
reselection algorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures
in idle mode and procedures for cell reselection in connected mode.
78 DN09146788 Issue: 01
2.7.4 Deactivating RAN3069: RSRQ-based LTE Reselection

Purpose
Follow this procedure to deactivate the RAN3069: RSRQ-based LTE Reselection
feature.
Before you start
g In order to verify usage of the quality criteria for LTE absolute priority based cell
reselection, activation of the RAN2067: LTE Interworking feature was needed.
Therefore, for deactivating the RAN3069: RSRQ-based LTE Reselection
feature, instructions on the RAN2067: LTE Interworking feature deactivation are
also included. For more information, see
Deactivating RAN2067: LTE Interworking.

b) In System Info tab, set the values of LTECellReselection parameter to
Disabled.
2.8 RAN2264: Smart LTE Handover

2.8.1 Description of RAN2264: Smart LTE Handover
The RAN2264: Smart LTE Handover feature introduces inter-RAT WCDMA to LTE
handover. This feature supports traffic steering to LTE layers, providing seamless
handover experience for the end-users.
2.8.1.1 Benefits
End-user benefits
End user benefits from seamless WCDMA to LTE handover experience.
Operator benefits
Thanks to this feature WCDMA to LTE mobility becomes faster end more reliable, as
handover is preceded with compressed mode measurements.
Issue: 01 DN09146788 79

Direct RNC
RU50 Planned for RN8.0 Planned for Planned for OMS 3.0 WN9.0

BTS BTS
Planned for Planned for NetAct 8 Support not Planned for Support not 3GPP Rel-
later later EP1 required later required 8 (optional)

• RAN1016: Flexi BTS Multimode System Module- FSMD
The RAN2264: Smart LTE Handover feature introduces inter-system handover from
WCDMA to LTE.
Inter-RAT handover from WCDMA to LTE can be started if compressed mode
measurements indicate that LTE coverage is available. The following events can trigger
compressed mode measurements for LTE handover:
• T1: Cell_DCH to Cell_FACH, Cell_PCH, or URA_PCH selection

• T2: HSDPA reconfiguration to traditional DCH, for example reconfiguration caused by
high HSDPA load and lack of HSDPA cell resources
• T3: CS call release with active PS RAB
• T4: Periodic trigger
In uplink DCH is used during compressed mode. However, if HSUPA compressed mode
supported by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency
Handover feature is active, then HSUPA compressed mode is used in uplink.
80 DN09146788 Issue: 01
In cases when WCDMA cell load is not high and users can be provided with good
enough experience in WCDMA layer, measurements and handover to LTE can be by-
passed. Cell level load parameters can be used to define if load is low enough for
keeping UEs in WCDMA.
The RAN2264: Smart LTE Handover feature supports inter-RAT handover from WCDMA
to both FDD-LTE and TDD-LTE.

The RAN2067: LTE Interworking feature is a prerequisite for using this feature.
For HSUPA compressed mode measurements, the RAN1668: HSUPA Compressed
Mode for LTE and Inter-frequency Handover feature is required.
g This feature requires also support from the UE, 3G core network, LTE core
network, and LTE eNB.
This feature causes rise of signaling traffic on Uu, Iub, Iur, and IuPS interfaces
(compressed mode related signaling, LTE neighbor reporting over Iur, relocation related
signaling between RNC and core network).

• New Managed Object Class (MOC): ADJE is introduced for defining E-UTRA (LTE)
neighbor cells.
• New counters for monitoring outgoing LTE PS Handover are introduced.

• This feature supports traffic steering and network load balancing scenarios.
Offloading WCDMA network during high load states via seamless handover to LTE
(resources are reserved in advance on LTE side in contrast to layering features)
increases available HSDPA power per user ratio in WCDMA cell.
• This feature impacts the maximum number of UEs that are simultaneously in
compressed mode in the cell due to a non-critical handover measurement reason
(both DCH and HSPA compressed modes).
2.8.1.5 RAN2264: Smart LTE Handover management data
Alarms

Issue: 01 DN09146788 81
M1010C240 LTE NRT ISHO MEAS WITH CM DUE TO Inter System Hard Handover
DCH TO CCH
HSPA TO DCH
CS RAB RELEASE
PERIODIC TRIGGER
M1010C244 LTE NRT ISHO MEAS WITHOUT CM DUE Inter System Hard Handover
TO DCH TO CCH
TO HSPA TO DCH
TO CS RAB RELEASE
TO PERIODIC TRIGGER
M1010C248 LTE NRT ISHO NO CELL FOUND DUE TO Inter System Hard Handover
DCH TO CCH
HSPA TO DCH
CS RAB RELEASE
PERIODIC TRIGGER
M1010C252 LTE NRT ISHO ATTEMPTS DUE TO DCH Inter System Hard Handover
TO CCH
M1010C253 LTE NRT ISHO ATTEMPTS DUE TO HSPA Inter System Hard Handover
TO DCH
M1010C254 LTE NRT ISHO ATTEMPTS DUE TO CS Inter System Hard Handover
RAB RELEASE
M1010C255 LTE NRT ISHO ATTEMPTS DUE TO Inter System Hard Handover
PERIODIC TRIGGER
82 DN09146788 Issue: 01
M1010C256 LTE NRT ISHO SUCCESS DUE TO DCH Inter System Hard Handover
TO CCH
M1010C257 LTE NRT ISHO SUCCESS DUE TO HSPA Inter System Hard Handover
TO DCH
M1010C258 LTE NRT ISHO SUCCESS DUE TO CS Inter System Hard Handover
RAB RELEASE
M1010C259 LTE NRT ISHO SUCCESS DUE TO Inter System Hard Handover
PERIODIC TRIGGER
M1010C260 LTE NRT ISHO UE NACK DUE TO DCH Inter System Hard Handover
TO CCH
M1010C261 LTE NRT ISHO UE NACK DUE TO HSPA Inter System Hard Handover
TO DCH
M1010C262 LTE NRT ISHO UE NACK DUE TO CS Inter System Hard Handover
RAB RELEASE
M1010C263 LTE NRT ISHO UE NACK DUE TO Inter System Hard Handover
PERIODIC TRIGGER
M1010C264 LTE NRT ISHO UE LOST DUE TO DCH TO Inter System Hard Handover
CCH
M1010C265 LTE NRT ISHO UE LOST DUE TO HSPA Inter System Hard Handover
TO DCH
M1010C266 LTE NRT ISHO UE LOST DUE TO CS RAB Inter System Hard Handover
RELEASE
M1010C267 LTE NRT ISHO UE LOST DUE TO Inter System Hard Handover
PERIODIC TRIGGER
M1010C268 LTE NRT ISHO PREPARATION FAIL Inter System Hard Handover
M1019C0 LTE ISHO ATTEMPTS AutoDef LTE
M1019C1 LTE ISHO SUCCESSFUL AutoDef LTE
M1036C0 LTE PS ISHO OUT PREP REQ LTE Relocation
M1036C1 LTE PS ISHO OUT PREP SUCC LTE Relocation
M1036C2 LTE PS ISHO OUT PREP FAIL DUE TO LTE Relocation

RN LAYER CAUSE
Issue: 01 DN09146788 83
M1036C3 LTE PS ISHO OUT PREP FAIL DUE TO TR LTE Relocation

LAYER CAUSE

NAS CAUSE

PROT CAUSE

MISC CAUSE

NON STAN CAUSE
M1036C8 LTE PS ISHO CANCEL TOTAL LTE Relocation
M1036C9 LTE PS ISHO FAIL DUE TO RELOC LTE Relocation

OVERALL TIMER EXPIRY
M1036C10 LTE PS ISHO CANCEL DUE TO RELOC LTE Relocation

PREP TIMER EXPIRY
M1010C239 DURATION OF LTE CARRIER Inter System Hard Handover

MEASUREMENT

Parameters
Outgoing LTE Handover Enabled LTEHandoverEnabled RNC/WBTS/WCEL
84 DN09146788 Issue: 01
Minimum Interval Between LTE HOs LTEMinHoInterval RNC/FMCL
ADJE Identifier ADJEId RNC/WBTS/WCEL

/ADJE
Change origin for ADJE object ADJEChangeOrigin RNC/WBTS/WCEL

/ADJE
Inter-RAT LTE adjacent physical cell AdjePhysicalCellId RNC/WBTS/WCEL

identifier /ADJE
Mobile Country Code AdjeMCC RNC/WBTS/WCEL

/ADJE
Mobile Network Code AdjeMNC RNC/WBTS/WCEL

/ADJE
Mobile Network Code Length AdjeMNCLength RNC/WBTS/WCEL

/ADJE
Macro eNB ID AdjeENodeBId RNC/WBTS/WCEL

/ADJE
Cell ID AdjeCellId RNC/WBTS/WCEL

/ADJE
Tracking Area Code AdjeTAC RNC/WBTS/WCEL

/ADJE
ADJL Identifier AdjLIdentifier RNC/WBTS/WCEL

/ADJE
RNC Options RncOptions RNC
BTS support for HSPA CM BTSSupportForHSPACM RNC/WBTS
Max number of UEs in HSDPA CM due MaxNumberUEHSPACmNCH RNC/WBTS/WCEL

to NCHO O
LTE Layer Cell HSDPA Load LTELayerCellHSLoad WCEL
Issue: 01 DN09146788 85
Table 50 Modified parameters (Cont.)
Smart LTE Layering NRT user amount SmartLTELayeringUA WCEL

threshold
Smart LTE Layering service control SmartLTELayeringServ RNMOBI
Smart LTE Layering Target System SmartLTELayeringTSysSel WCEL

Selection
LTE Periodic trigger timer LTEPeriodicTriggerTimer RNC
LTE Measurement Averaging Window LTEMeasAveWindow RNC/FMCL
LTE Maximum Measurement Period LTEMaxMeasPeriod RNC/FMCL
LTE Minimum Measurement Interval LTEMinMeasInterval RNC/FMCL
LTE Neighbor Carrier Frequency Search LTENcarrFreqSearchPeriod RNC/FMCL

Period
Adjacent LTE Frequency Priority AdjLFreqPriority RNC/HOPL
LTE Carrier frequency selection AdjLMinRSRPLevel RNC/HOPL

Minimum Rx Power level
LTE Carrier frequency selection AdjLMinRSRQLevel RNC/HOPL

Minimum Rx qual level
Identifier of inter- system adjacency to ADJLId RNC/WBTS/WCEL

LTE /ADJL
FMCL Identifier FMCLIdentifier RNC/WBTS/WCEL
Maximum number of UEs in CM due to MaxNumberUECmSLHO RNC/WBTS/WCEL

SLHO measurement
ASW RAN RNC LK
2.8.2 Activating RAN2264: Smart LTE Handover

Purpose
86 DN09146788 Issue: 01
Before you start

Restart of the RNC and the BTS is not required after the activation of this feature.
This procedure does not cause downtime, and it can be activated at any time of the day.

Before activating this feature, activate the license of the RAN2067: LTE Interworking
feature (feature code 1755, see Activating RAN2067: LTE Interworking).
This feature is controlled by the long-term ON/OFF license key. For information on
managing licenses, see Licensing.
• for IPA-RNC:
ZW7M: FEA=3414:ON;
Before activating this feature configure the following database objects and relevant
parameters and attach them to WCDMA cell:
• FMCL (Inter-RAT (LTE) measurement control parameter set)

– LTEMinHoInterval (optional, default value exists)
– LTEMeasAveWindow (optional, default value exists)
– LTEMaxMeasPeriod (optional, default value exists)
– LTEMinMeasInterval (optional, default value exists)
– LTENcarrFreqSearchPeriod (optional, default value exists)
• HOPL (Inter-RAT (LTE) neighbor frequency parameter set)

– AdjLFreqPriority (optional, default value exists)
– AdjLMinRSRPLevel (optional, see Further information section)
– AdjLMinRSRQLevel (optional, see Further information section)
• ADJL (Inter-RAT (LTE) neighbor frequency definitions)

– AdjLEARFCN (mandatory)
– HopLIdentifier (mandatory)
– AdjLMeasBw (optional, default value exists)
g Note that even though configuring AdjLMeasBw parameter is not

mandatory for creating ADJL-object, it is important for network planning.
• ADJE (Inter-RAT (LTE) neighbor cell definitions)

– AdjePhysicalCellId (mandatory)
– AdjeMCC (mandatory)
– AdjeMNC (mandatory)
– AdjeMNCLength (optional, default value exists for the 2 digit MNC)
Issue: 01 DN09146788 87
– AdjeENodeBId (mandatory)
– AdjeCellId (mandatory)
– AdjeTAC (mandatory)
– AdjLIdentifier (mandatory)
Additionally, the following parameters can be used for tuning the RAN2264: Smart LTE
Handover feature:
• RNC parameter LTEPeriodicTriggerTimer (optional, default value exists)

• RNMOBI parameter SmartLTELayeringServ (optional, default value exists)
• WCEL parameter LTELayerCellHSLoad (optional, default value exists)
• WCEL parameter SmartLTELayeringUA (optional, default value exists)
• WCEL parameter SmartLTELayeringTSysSel (optional, default value exists)
• RNHSPA parameter TGPLForLTEMeas (optional, default value exists)
Before activating this feature ensure the correctness of the following neighboring LTE
and CN configuration and identifier parameters:
• ADJL-AdjLEARFCN
• ADJL-AdjLMeasBw
• ADJE-AdjePhysicalCellId
• ADJE-AdjeMCC
• ADJE-AdjeMNC
• ADJE-AdjeMNCLength
• ADJE-AdjeENodeBId
• ADJE-AdjeCellId
• ADJE-AdjeTAC
• ADJE-AdjLIdentifier
RNC O&M is not able to verify the values of these parameters.
g The RAN2264: Smart LTE Handover feature is activated on cell basis.
88 DN09146788 Issue: 01
2 Go to Topology.
3 Expand the ROOT.

b) Activate the RAN2264: Smart LTE Handover feature with the
LTEHandoverEnabled parameter.
g WCEL should be associated with FMCL object.
g State of the licenses must not be changed after activating the feature.
Further information
WCEL parameter LTEHandoverEnabled enables triggers for the Smart LTE Handover
as follows:
• value (0) = all triggers disabled

• value (1) = T1 enabled
• value (8) = all triggers enabled (T1, T2, T3, and T4)
where:
• T1: RRC state change Cell_DCH to CCH

• T2: HSDPA/HSPA to DCH/DCH CTS
• T3: CS RAB release
• T4: Periodic trigger
For more information, see Description of RAN2264: Smart LTE Handover.
Issue: 01 DN09146788 89
The HSUPA compressed mode measurement support for LTE is provided by the
RAN1668: HSUPA Compressed Mode for LTE and Inter-frequency Handover feature. If
the feature is not available, E-DCH to UL DCH switch is needed before starting the LTE
measurements for handover.
For instructions on how to activate and configure DCH/DCH compressed mode (CM) and
HSDPA/DCH CM for LTE handover, see Activating RAN2980: Measurement Based LTE
Layering. For information on how to activate and configure HSPA CM for LTE handover,
see Activating RAN1668 HSUPA Compressed Mode for LTE and Inter-frequency
Handover.
The minimum required RSRP (AdjLMinRSRPLevel) and RSRQ (AdjLMinRSRQLevel)
levels of the cell under LTE carrier frequency should be aligned with the corresponding
thresholds in the LTE network.
Ensure that the UE is not redirected or handed over from WCDMA to LTE with the RSRP
or RSRQ levels, which are lower than the thresholds for the coverage (RSRP) or quality
(RSRQ)-based handover from LTE to WCDMA. For example, if the coverage (RSRP)
based handover from LTE to WCDMA is configured to trigger with RSRP level – 115
dBm, then the recommended minimum RSRP threshold for the WCDMA to LTE
handover is – 112 dBm (3 dB hysteresis) in order to avoid immediate handover back to
WCDMA. Correspondingly, if the quality (RSRQ)-based handover from LTE to WCDMA
is configured to trigger with RSRQ level - 15 dB, then the minimum RSRQ threshold for
the WCDMA to LTE handover should be set to - 12 dB (3 dB hysteresis).
Inter-RAT handover from WCDMA to LTE is supported for the following PS QoS classes:
• Interactive (NRT)
• Background (NRT)
2.8.3 Verifying RAN2264: Smart LTE Handover

Purpose
The functioning of the RAN2264: Smart LTE Handover feature can be verified with the
following counters for the inter-RAT LTE handover attempts and successes:
• M1010C252 LTE NRT ISHO ATTEMPTS DUE TO DCH TO CCH

• M1010C253 LTE NRT ISHO ATTEMPTS DUE TO HSPA TO DCH
• M1010C254 LTE NRT ISHO ATTEMPTS DUE TO CS RAB RELEASE
• M1010C255 LTE NRT ISHO ATTEMPTS DUE TO PERIODIC TRIGGER
• M1010C256 LTE NRT ISHO SUCCESS DUE TO DCH TO CCH
• M1010C257 LTE NRT ISHO SUCCESS DUE TO HSPA TO DCH
• M1010C258 LTE NRT ISHO SUCCESS DUE TO CS RAB RELEASE
• M1010C259 LTE NRT ISHO SUCCESS DUE TO PERIODIC TRIGGER
Expected outcome
Outgoing inter-RAT LTE handover is successful and visible in the attempt and success
counters.
Further information
More detailed monitoring of the RAN2264: Smart LTE Handover feature can be
performed with the following counters:
90 DN09146788 Issue: 01
• M1010C239 DURATION OF LTE CARRIER MEASUREMENT

• M1010C240 LTE NRT ISHO MEAS WITH CM DUE TO DCH TO CCH
• M1010C241 LTE NRT ISHO MEAS WITH CM DUE TO HSPA TO DCH
• M1010C242 LTE NRT ISHO MEAS WITH CM DUE TO CS RAB RELEASE
• M1010C243 LTE NRT ISHO MEAS WITH CM DUE TO PERIODIC TRIGGER
• M1010C244 LTE NRT ISHO MEAS WITHOUT CM DUE TO DCH TO CCH
• M1010C245 LTE NRT ISHO MEAS WITHOUT CM DUE TO HSPA TO DCH
• M1010C246 LTE NRT ISHO MEAS WITHOUT CM DUE TO CS RAB RELEASE
• M1010C247 LTE NRT ISHO MEAS WITHOUT CM DUE TO PERIODIC TRIGGER
• M1010C248 LTE NRT ISHO NO CELL FOUND DUE TO DCH TO CCH
• M1010C249 LTE NRT ISHO NO CELL FOUND DUE TO HSPA TO DCH
• M1010C250 LTE NRT ISHO NO CELL FOUND DUE TO CS RAB RELEASE
• M1010C251 LTE NRT ISHO NO CELL FOUND DUE TO PERIODIC TRIGGER
• M1010C260 LTE NRT ISHO UE NACK DUE TO DCH TO CCH
• M1010C261 LTE NRT ISHO UE NACK DUE TO HSPA TO DCH
• M1010C262 LTE NRT ISHO UE NACK DUE TO CS RAB RELEASE
• M1010C263 LTE NRT ISHO UE NACK DUE TO PERIODIC TRIGGER
• M1010C264 LTE NRT ISHO UE LOST DUE TO DCH TO CCH
• M1010C265 LTE NRT ISHO UE LOST DUE TO HSPA TO DCH
• M1010C266 LTE NRT ISHO UE LOST DUE TO CS RAB RELEASE
• M1010C267 LTE NRT ISHO UE LOST DUE TO PERIODIC TRIGGER
• M1010C268 LTE NRT ISHO PREPARATION FAIL
• M1019C0 LTE ISHO ATTEMPTS
• M1019C1 LTE ISHO SUCCESSFUL
• M1036C0 LTE PS ISHO OUT PREP REQ
• M1036C1 LTE PS ISHO OUT PREP SUCC
• M1036C2 LTE PS ISHO OUT PREP FAIL DUE TO RN LAYER CAUSE
• M1036C3 LTE PS ISHO OUT PREP FAIL DUE TO TR LAYER CAUSE
• M1036C4 LTE PS ISHO OUT PREP FAIL DUE TO NAS CAUSE
• M1036C5 LTE PS ISHO OUT PREP FAIL DUE TO PROT CAUSE
• M1036C6 LTE PS ISHO OUT PREP FAIL DUE TO MISC CAUSE
• M1036C7 LTE PS ISHO OUT PREP FAIL DUE TO NON STAN CAUSE
• M1036C8 LTE PS ISHO CANCEL TOTAL
• M1036C9 LTE PS ISHO FAIL DUE TO RELOC OVERALL TIMER EXPIRY
• M1036C10 LTE PS ISHO CANCEL DUE TO RELOC PREP TIMER EXPIRY
2.8.4 Deactivating RAN2264: Smart LTE Handover

Purpose
g The RAN2264: Smart LTE Handover feature is deactivated on cell basis.
Issue: 01 DN09146788 91
2 Go to Topology.
3 Expand the ROOT.

b) Deactivate the RAN2264: Smart LTE Handover feature with the
LTEHandoverEnabled parameter.
2.9 RAN2881: WCDMA and GSM Layer Priorities

2.9.1 Description of RAN2881: WCDMA and GSM Layer Priorities
The RAN2881: WCDMA and GSM Layer Priorities feature allows idle mode traffic
steering according to priorities given for WCDMA and GSM layers.
2.9.1.1 Benefits
End-user benefits
This feature provides end-user higher data rates and faster response times.
Operator benefits
Introduced idle-mode traffic steering reduces the need for handovers and reselects the
best possible layer for the end-user. Operator controls the priorities of the layers.
92 DN09146788 Issue: 01
RNC
RU50 Not planned RN8.0 Planned for Not planned OMS3.0 Support
later (RU50) not
releases required

BTS BTS

Functional overview
The RAN2881: WCDMA and GSM Layer Priorities feature enables WCDMA and GSM
cell reselection based on layer/Radio Access Technology priorities. When layer-specific
absolute priority information is provided in the system information block type 19 (SIB19),
UE periodically measures higher priority layers. UE measurements are applicable when
the UE is in idle mode, Cell_PCH, or URA_PCH state. Also lower and equal priority
layers are measured by UE, if radio conditions in the camped frequency fall below
criteria defined with search thresholds.
Based on results of these measurements, UE performs priority-based cell reselection
using both coverage and quality thresholds broadcast in SIB19. For WCDMA and GSM
priority-based cell reselection these thresholds are specified in 3GPP Rel-8.
In addition to the priority number for the layer, signal strength and quality thresholds are
provided for cell reselection. Frequency band prioritization can be adjusted with
thresholds, for example, 900 MHz can be preferred for cell edge UEs and 2100 MHz - for
close by UEs. UEs above certain threshold move to higher priority layer, whereas cell
edge UEs prefer low priority layer as they are below the threshold. Figure 4: WCDMA
and GSM cell reselection based on layer priorities shows the mechanism of cell
reselection. The absolute priority mechanism is 3GPP Rel-8 feature.
Issue: 01 DN09146788 93
Figure 4 WCDMA and GSM cell reselection based on layer priorities

Hierarchical Cell Structure cannot be used simultaneously with RAN2881: WCDMA and
GSM Layer Priorities feature.
Impact on commands

tools.

2.9.1.5 RAN2881: WCDMA and GSM Layer Priorities management data
Alarms


94 DN09146788 Issue: 01
Parameters
Table 53: New parameters lists parameters introduced with this feature and the

object
WCDMA Cell Reselection WCDMACellReselection N/A WCEL
GSM Cell Reselection GSMCellReselection N/A WCEL
Absolute priority for inter-frequency cell AdjiAbsPrioCellReselec priority HOPI

reselection
Threshold high for inter-frequency cell AdjiThreshigh Threshx,high HOPI

reselection
Threshold low for inter-frequency cell AdjiThreslow Threshx,low HOPI

reselection
QqualminFDD for inter-frequency cell AdjiQqualminFDD QqualminFDD HOPI

reselection
QrxlevminFDD for inter-frequency cell AdjiQrxlevminFDD QrxlevminFDD HOPI

reselection
Absolute priority for GSM cell reselection AdjgAbsPrioCellReselec priority HOPG
Threshold high for GSM cell reselection AdjgThreshigh Threshx,high HOPG
Threshold low for GSM cell reselection AdjgThreslow Threshx,low HOPG
Thresh serving low 2 Threshservlow2 Threshserving,low2 WCEL
System Information Block 19 Compmask 5 SIB19Compmask5 N/A WCEL
Table 54: Modified parameters lists parameters modified by this feature and the
Issue: 01 DN09146788 95

object
RNC Options RncOptions N/A RNC
Absolute priority level for cell reselection AbsPrioCellReselec priority WCEL
S prioritysearch1 Sprioritysearch1 Sprioritysearch1 WCEL
S prioritysearch2 Sprioritysearch2 Sprioritysearch2 WCEL
Thresh serving low Threshservlow Threshserving,low WCEL
UTRA Absolute Radio Frequency Channel AdjiUARFCN UARFCN ADJI

Number
RT HOPI Identifier RtHopiIdentifier N/A ADJI
Cell Re-selection Minimum RX Level AdjgQrxlevMin QrxlevminGSM HOPG
RT HOPG Identifier RtHopgIdentifier N/A ADJG
Cell Reselection Absolute Priority AdjLAbsPrioCellReselec priority HOPL
Priority for SIB19 SIB19Priority N/A RNC
List of Compmasks in System Information Block SIB19CompmaskInfo N/A WCEL

19
Block 19 Compmask 1 SIB19Compmask1 N/A WCEL
Table 55: Related existing parameters lists existing parameters related to this feature
and the corresponding SIB19 parameters specified in 3GPP Rel-8.
Table 55 Related existing parameters

object
BCCH ARFCN AdjgBCCH GSM cell group List / ADJG

Starting ARFCN
96 DN09146788 Issue: 01
Table 55 Related existing parameters (Cont.)

object
GSM cell group List / List

of ARFCNs
Band Indicator AdjgBandIndicator GSM cell group List / ADJG

Band Indicator
ASW RAN RNC LK
2.9.2 Activating RAN2881: WCDMA and GSM Layer Priorities

Purpose
Follow this procedure to activate the RAN2881: WCDMA and GSM Layer Priorities
feature.
Before you start

time of the day.
Activate the license of the RAN2881: WCDMA and GSM Layer Priorities feature using
WCDMA and GSM Layer Priorities license key.
• for IPA-RNC:
ZW7M: FEA=4781:ON;
For information on managing licenses, see Licensing.

To provide seamless priority-based cell reselection between GSM, WCDMA, and LTE,
make sure to admit each Radio Access Technology a different priority:
• AbsPrioCellReselec WCEL parameter, introduced with the RAN2067:LTE

Interworking feature, defines the priority of the WCDMA serving cell (UTRA priority
info list/UTRA Serving Cell IE)
• AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881:
WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequency
priority (UTRA priority info list/UTRAN FDD Frequencies IE)
Issue: 01 DN09146788 97
• AdjgAbsPrioCellReselec HOPG parameter, introduced with the RAN2881:

WCDMA and GSM Layer Priorities feature, defines the GSM priority (GSM priority
info list/GSM Priority Info IE)
• AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE
Interworking feature, defines the LTE priority (E-UTRA frequency and priority info
list/E-UTRA frequency and priority IE)
g Priority-based cell reselection between WCDMA and LTE radio technologies is

provided by the RAN2067: LTE Interworking feature. The
RAN3069: RSRQ-based LTE Reselection feature is an extension to the
RAN2067: LTE Interworking feature and provides quality thresholds for LTE
priority-based cell reselection.
RtHopiIdentifier (RT HOPI Identifier) ADJI parameter is used for defining
parameter set for WCDMA inter-frequency absolute priority cell reselection.
RtHopgIdentifier (RT HOPG Identifier) ADJG parameter is used for defining
parameter set for GSM absolute priority cell reselection.
WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority value
should be given for each inter-frequency WCDMA neighbor. If more than one value is
given, the highest priority is broadcast in SIB19 message. Correspondingly, GSM priority
is broadcast per GSM cell group (BCCH ARFCN + Band Indicator) in SIB19 message.
Thus, priority should be defined so that the same priority value is given for each GSM
neighbor within the same frequency. If more than one value is given, the highest priority
is broadcast in SIB19 message.
g Before enabling the GSMCellReselection WCEL parameter in the cell, make

sure that GSM priority (AdjgAbsPrioCellReselec parameter) is defined for
each GSM neighbor cell. If priority information is provided for any GSM layer,
cells belonging to GSM layer for which no priority is assigned are not
considered for reselection. Default value of AdjgAbsPrioCellReselec
parameter means that GSM priority is not defined.

b) In System Info tab, set the values of WCDMACellReselection and
GSMCellReselection parameter to Enabled.
Further information
g Note that the UE does not use Hierarchical Cell Structure (HCS) for inter-
frequency or inter-RAT reselection if absolute-priority-based cell reselection is
used.
98 DN09146788 Issue: 01
2.9.3 Verifying RAN2881: WCDMA and GSM Layer Priorities

Purpose
Follow these tips to verify that the RAN2881: WCDMA and GSM Layer Priorities feature
Before you start
g There are no counters involved in cell reselection process. UE reselects the cell
according to the parameters broadcast by the network in SIB19 message.
When the RAN2881: WCDMA and GSM Layer Priorities feature is active, it is visible in
the content of SIB19 message. After activating this feature and ascribing values to the
parameters listed in RAN2881: WCDMA and GSM Layer Priorities management data
section, the following information elements will be broadcasted in SIB19 message:
• UTRA priority info list / UTRA Serving Cell

• UTRA priority info list / UTRAN FDD Frequencies
• GSM priority info list / GSM Priority Info
Content of SIB19 message can be monitored by using UE and network protocol

analyzer.
Further information
Camping on a desired layer is perfomed by UE using SIB19 parameters. Cell reselection
algorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures in idle mode
and procedures for cell reselection in connected mode.
2.9.4 Deactivating RAN2881: WCDMA and GSM Layer Priorities

Purpose
Follow this procedure to deactivate the RAN2881: WCDMA and GSM Layer Priorities
feature.

b) In System Info tab, set the values of WCDMACellReselection and
GSMCellReselection parameter to Disabled.
Issue: 01 DN09146788 99
Transmission and transport features RU50 Feature Descriptions and Instructions
3 Transmission and transport features
3.1 RAN2243: Performance Monitoring Based on ETH

Service OAM
3.1.1 Description of RAN2243: Performance Monitoring Based
on ETH Service OAM
This feature enhances the RAN1880: Ethernet OAM in BTS feature to provide
performance monitoring functionality using Ethernet Service OAM frames.
Performance monitoring according to the ITU-T Y.1731 provides Ethernet performance
measurement between Maintenance End Points (MEPs) that are placed at the edges of
each maintenance domain. The performance monitoring feature supports the Frame
Loss and Frame Delay Measurements. The Frame Delay Measurements are showed
with maximum, minimum and average values of the measurement period of fifteen
minutes to provide the information about the Frame Delay Variation.
3.1.1.1 Benefits
End-user benefits
This feature does not affect the end-user experience.
Operator benefits
This feature provides the maintenance hierarchy structure where the performance
measurements are performed between the MEPs of the same grade of hierarchy.
Different grades of hierarchy monitor different Ethernet network segments to find the
problems more efficiently.
Table 57: Software requirements lists software required for this feature.
RAS Flexi Direct IPA-RNC mcRNC Flexi Direct RNC OMS Flexi BTS
RU50 Not planned Support not Support not Not planned OMS3.0 WN9.0
required required (RU50)
100 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions Transmission and transport features

BTS BTS
Planned Planned NetAct 8 EP1 Support not Support not Support not Support not
for later for later (RU50) required required required required
releases releases
This feature requires one of the following Flexi Multiradio BTS Transport Sub-Modules:
• Flexi FTIA
• Flexi FTJA
• Flexi FTIB
• Flexi FTLB
• Flexi FTFB
This feature requires one of the following features for Flexi Multiradio BTS WCDMA:


Functional overview
This feature enhances the RAN1880: Ethernet OAM in BTS feature to provide
performance monitoring (PM) functionality using Ethernet Service OAM frames. The
Ethernet OAM performance monitoring functions are defined by ITU-T Y.1731 standard.
The ITU-T Y.1731 standard sets up an L2 network on hierarchy, which conforms
maintenance domains. Different maintenance domains are assigned to the customer,
service providers or operators. The edges of each domain are Maintenance End Points
(MEPs). The ports within domains are Maintenance Intermediate Points (MIPs). The
maintenance hierarchy allows to monitor different segments of the Ethernet network,
which are under the responsibility of different hierarchy departments. The segmentation
of maintenance domains simplifies finding the problems on the L2 Ethernet network.
When the performance monitoring feature is not activated, the L2 (Ethernet)
performance monitoring functions are not possible to be performed.
Issue: 01 DN09146788 101

Figure 5 Performance monitoring using Ethernet Service OAM frames
Eth PM
Eth PM
Eth PM
MEP MEP MEP MEP
BTS
Eth Ethernet Ethernet
The performance monitoring functions supported by the performance monitoring feature

are Frame Loss and Frame Delay Measurement. There are different modes of each
measurement. These modes are presented beneath:
• Frame Loss Measurement

– dual-ended (ETH-CCM)
– single-ended (ETH-LMM / ETH-LMR)
• Frame Delay Measurement (ETH-DM)

– One-way Delay Variation
– Two-way Delay
This feature provides also configurable thresholds for triggering alarms for Frame Loss
Measurement and Frame Delay/Delay Variation Measurement. Thresholds are
configurable per measurement session.
The Frame Loss Measurements are obtained by means of counters for received and
transmitted data frames between a pair of MEPs. These counters are provided by the
performance monitoring feature. The Frame Loss Measurement can be calculated for
each direction. Far-end and near-end Frame Loss Measurements are supported. The
BTS supports both kinds of Frame Loss Measurements. The operator configures the
measurement nature.
g Note that mesh, chain, tree, and circle topology should have point-to-point
Ethernet connections between MEPs to perform accurate Frame Loss
Measurement, whereas there are no similar conditions for Frame Delay/Delay
Variation Measurement.

This feature does not need a separate license.
This feature needs the licenses of features:
102 DN09146788 Issue: 01

• RAN1880: Ethernet OAM in BTS

• RAN1900: IP Transport Network Measurement
This feature needs the activation of feature:

This feature has an impact on network element management tools as beneath:
• new alarms/faults supported by NetAct

• new counters supported by NetAct
• new parameters supported by NetAct

This feature has an impact on system performance and capacity as beneath:
• The Service OAM can consume significant amount of bandwidth, particularly when
pro-active functions (ETH-CC) are activated simultaneously and using high
transmission rates. However, the Service OAM performance monitoring functions are
not meant to use high transmission rates. The feature standard recommends 10 fps.
The usage of these functions must be confined then.
• The capacity demands for Service OAM performance monitoring functions is usually
not significant. With default settings, each ETH-CCM measurement consumes less
than 1 kbps, whereas ETH-LM and ETH-DM measurements - less than 0.1 kbps.
The default interval values for measurements are given below:
– ETH-CCM measurement - 1 s
– ETH-LM measurement - 10 s
– ETH-DM measurement - 10 s
• At maximum (not recommended), ETH-CCM Frame Loss Measurement can

consume 312 kbps at Ethernet layer when 3.33 ms interval is configured.
3.1.1.5 RAN2243: Performance Monitoring Based on ETH Service OAM

management data
Faults
Table 58: New faults lists faults and reported alarms introduced with this feature.
Issue: 01 DN09146788 103

Table 58 New faults
Fault ID Fault name Reported alarms
61635 Frame loss threshold 7665 BASE STATION TRANSMISSION ALARM

exceeded on mac $m
61636 Two way delay 7665 BASE STATION TRANSMISSION ALARM

threshold exceeded on
mac $m
61637 OneWay delay variation 7665 BASE STATION TRANSMISSION ALARM

threshold exceed on
mac $m
g The performance monitoring faults are presented as alarms at:
• OMS Fault Management

• NetAct Monitor

M5141C0 soamIngressFramesLost M5141 (Frame Loss)
M5141C1 soamIngressTotalFrames M5141 (Frame Loss)
M5141C2 soamNearEndFrameLossRatio M5141 (Frame Loss)
M5141C3 soamEgressFramesLost M5141 (Frame Loss)
M5141C4 soamEgressTotalFrames M5141 (Frame Loss)
M5141C5 soamFarEndFrameLossRatio M5141 (Frame Loss)
M5142C0 soamTwowayAverageDelay M5142 (Frame Delay)
M5142C1 soamTwowayMaxDelay M5142 (Frame Delay)
M5142C2 soamTwowayMinDelay M5142 (Frame Delay)
M5143C0 soamOnewayNearEnDelayVariation M5143 (Frame Delay)
M5143C1 soamOnewayFarEndDelayVariation M5143 (Frame Delay)
104 DN09146788 Issue: 01


Parameters
Enable service OAM performance enableSoamPm IPNO

monitoring
Flag for enabling/disabling SOAM enableSoamFrameLossMeas OAMFLM

frame loss measurement
MAC address of the frame loss macAddr OAMFLM

measurement remote MEP
Service OAM frame loss alarm soamFrameLossAlarmThres OAMFLM

threshold
Service OAM frame loss soamFrameLossMeasInt OAMFLM

measurement interval
Service OAM Frame loss soamFrameLossMeasMode OAMFLM

Measurement Mode
Enable service OAM delay enableSoamDelayMeasure OAMDM

measurement
MAC address of the delay macAddr OAMDM

measurement remote MEP
Service OAM oneway delay soamDelayAlarmThresOneway OAMDM

variation 15m alarm threshold
Service OAM two-way delay 1 min soamDelayAlarmThresTwoway OAMDM

alarm threshold
Service oam delay measurement soamDmmPduSize OAMDM

PDU length
Service OAM frame delay soamFrameDelayMeasInt OAMDM

measurement interval
Commands
Issue: 01 DN09146788 105

ASW RAN TRS LK
3.1.2 Activating RAN2243: Performance Monitoring Based on

ETH Service OAM
Purpose
The purpose of this procedure is to activate the performance monitoring (PM) feature.
Before you start

The activating procedure does not cause downtime.
The activating procedure can be performed at any time of the day.
The activating procedure does not need a separate license.
The activating procedure needs the licenses of features:

The activating procedure needs the activation of feature:
The activating procedure to activate the Ethernet Service OAM PM on the BTS needs:
• BTS Site Manager

• NetAct Configuration Management software
The activating procedure to configure the PM measurement sessions on the BTS needs:

The activating procedure to start the measurements at OMS needs:

• NetAct Administration of Measurements
The activating procedure to monitor the PM measurement sessions data needs:

• NetAct Performance Manager
The activating procedure consists of three procedures:
• activating Ethernet Service OAM PM

• activating Frame Loss Measurement session
106 DN09146788 Issue: 01

• activating Frame Delay Measurement session
3.1.2.1 Activating Ethernet Service OAM PM

Purpose
This procedure is used to activate the Ethernet Service OAM PM on the BTS.
Before you start
g This procedure needs these actions to be performed:
• Determine the Maintenance Domain and Maintenance Association.

• Determine the Maintenance End Point(s) within given Maintenance
Association.
• Determine the Ethernet Service OAM performance monitoring switch.
g These actions happen when the preconditions are not met:
• The Ethernet Service OAM PM features can be set but they are not
operable.
• The messages from the remote MEPs are discarded.
• The PM measurements are not generated.
1 Open the BTS Site Manager.
g The NetAct Configuration Management software can be used

alternatively.
2 Turn on the Ethernet Service OAM PM feature on the BTS.

The actions of current step are:
a) Open the TRS Hardware from the View bar.
b) Open the Ethernet Service OAM menu.
c) Mark on the Ethernet Service OAM in use checkbox.
d) Mark on the Ethernet Service OAM performance monitoring in use checkbox.
g The activation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Ethernet Service OAM PM has been activated successfully on the BTS.
The Ethernet Service OAM PM statistics are cleared.
The BTS only answers to the incoming PM messages from the remote MEPs.
The PM measurement sessions are supported on the BTS:
• Frame Loss Measurement session

• Frame Delay Measurement session
Issue: 01 DN09146788 107

The PM measurement sessions with active status are automatically restarted on the
BTS.
g The PM measurement sessions have to be further activated separately on the

BTS.
g The proper measurements have to be started at OMS. The measurements are:
• M5141 - Soam Frame Loss statistics

• M5142 - Soam Two Way Delay Statistics
• M5143 - Soam One Way Delay Variation Statistics
g The operator can set the BTS thresholds for triggering alarms.
The PM thresholds are set on the BTS for each measurement separately.
3.1.2.2 Activating Frame Loss Measurement session

Purpose
This procedure is used to activate the Frame Loss Measurement session on the BTS.
This procedure consists also of the step to start the associated measurement at OMS.
Before you start

This procedure needs the activation of the Ethernet Service OAM PM on the BTS.
The Frame Loss statistics are fifteen-minute statistics.
g The Frame Loss Measurement session at single-ended mode cannot be

activated when:
• The Maintenance Association has more than one remote MEP.

• They cause the total egress of Service OAM frames to surpass 1000 fps.
• There are measurements under the same MEP with the same measurement
mode.
g The Frame Loss Measurement session at dual-ended mode cannot be

activated when:
• The Maintenance Association has zero or more than one remote MEP.
• The Maintenance Association does not have the ETH-CC activated.
• There are measurements under the same MEP with the same measurement
mode.

alternatively.
108 DN09146788 Issue: 01

2 Turn on the Frame Loss Measurement session on the BTS.

c) Open the New drop-down menu and create Frame loss measurement session.
d) Mark on the Frame loss measurement in use checkbox.
3 Determine the Frame Loss Measurement session parameters.

The Frame Loss Measurement session needs to configure the parameters:
• MAC address of remote MEP
• Frame loss measurement mode
• Frame loss transmission interval (for single-ended measurements)
• Frame loss alarm ratio threshold
• MEP with hereditary VLAN ID and PCP from Maintenance Association
BTS Site Manager.
4 Monitor the measurement session using the BTS Site Manager.

Expected outcome
The Frame Loss Measurement session has been activated on the BTS.
When Frame Loss Measurement session has been activated on the BTS then:
• The BTS purges the current Frame Loss statistics.
• The BTS starts to measure the Frame Loss statistics again.
• The BTS measures the Frame Loss Ratio every fifteen minutes.
• The BTS sends the measurement data to the OMS every hour.
• The BTS sends the CCM messages to the remote MEP (dual-ended mode).
• The BTS sends the LMM messages to the remote MEP (single-ended mode).
• The LMR messages are transmitted from the remote MEP (single-ended mode).
• The Frame Loss alarm occurs when the threshold has been reached.
5 Start the Soam Frame Loss statistics measurement (M5141) at OMS.
g This step must be performed using:

g The OMS does not store the measurement data to database.

The OMS transfers the measurement data from the BTS to the NetAct.
Expected outcome
The Soam Frame Loss statistics measurement has been started at OMS.
Issue: 01 DN09146788 109

The OMS sends the measurement data to the NetAct ten minutes after every hour.
6 Monitor the measurement session using the NetAct Performance Manager.
g This step must be performed after the proper time.

The BTS sends the measurement data to the OMS every hour.
The measurement data comprises four fifteen-minute statistics.
The OMS sends the measurement data to the NetAct ten minutes after.
The measurement data can be monitored then using:
Expected outcome
The Frame Loss Measurement session has been activated on the BTS.
3.1.2.3 Activating Frame Delay Measurement session

Purpose
This procedure is used to activate the Frame Delay Measurement session on the BTS.
This procedure consists also of the steps to start the associated measurement at OMS.
Before you start

The One-way Frame Delay Variation statistics are fifteen-minute statistics.
The Two-way Frame Delay statistics are one-minute and fifteen-minute statistics.
g The Frame Delay Measurement session cannot be activated when:
• There are 80 Frame Delay Measurement sessions which are already

created.
• They cause the total egress of Service OAM frames to surpass 1000 fps.
• The Frame Delay Measurement session with the same remote MAC was
already activated.

alternatively.
2 Turn on the Frame Delay Measurement session on the BTS.

110 DN09146788 Issue: 01

c) Open the New drop-down menu and create Delay measurement session.
d) Mark on the Delay measurement in use checkbox.
3 Determine the Frame Delay Measurement session parameters.

The Frame Delay Measurement session needs to configure the parameters:
• MAC address of remote MEP
• Delay measurement transmission interval
• Delay measurement message PDU size
• One-way delay variation 15 min alarm threshold
• Two-way delay measurement 1 min alarm threshold
• MEP with hereditary VLAN ID and PCP from Maintenance Association
BTS Site Manager.
4 Monitor the measurement session using the BTS Site Manager.

Expected outcome
The Frame Delay Measurement session has been activated on the BTS.
When Frame Delay Measurement session has been activated on the BTS then:
• The BTS purges the current Frame Delay statistics.
• The BTS starts to measure the Frame Delay statistics again.
• The BTS sends the measurement data to the OMS every hour.
• The BTS sends the DMM messages to the remote MEP.
• The DMR messages are transmitted from the remote MEP.
• The Frame Delay alarms occur when the thresholds have been reached.
5 Start the Soam Two Way Delay Statistics measurement (M5142) at OMS.


Expected outcome
The Soam Two Way Delay Statistics measurement has been started at OMS.
Issue: 01 DN09146788 111

6 Start the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.


Expected outcome
The Soam One Way Delay Variation Statistics measurement has been started at
OMS.

g NetAct does not support one-minute statistics.
Expected outcome
The Frame Delay Measurement session has been activated on the BTS.
3.1.3 Verifying RAN2243: Performance Monitoring Based on ETH

Service OAM
Purpose
The purpose of this procedure is to verify activation of PM feature.
Before you start

The verifying procedure does not cause downtime.
The verifying procedure can be performed at any time of the day.
The verifying procedure needs the PM measurement sessions activation on the BTS:
• Frame Loss Measurement session (make sure that there are any lost frames)
• Frame Delay Measurement session
The verifying procedure to start the measurements at OMS needs:
112 DN09146788 Issue: 01


The verifying procedure to monitor the PM measurement sessions data needs:

The verifying procedure to monitor the PM alarms needs:

• NetAct Monitor
The Frame Loss statistics are fifteen-minute statistics.

The One-way Frame Delay Variation statistics are fifteen-minute statistics.
The Two-way Frame Delay statistics are one-minute and fifteen-minute statistics.
1 Open the RNW Measurement Management.
g The NetAct Administration of Measurements application can be used

alternatively.
2 Start the proper measurements at OMS.

The Frame Loss Measurement is M5141 measurement.
The Two-way Frame Delay Measurement is M5142 measurement.
The One-way Frame Delay Variation Measurement is M5143 measurement.

4 After one minute verify that the proper PM counters are greater than zero.
g This step must be performed one minute after measurement start.
The proper PM counters are (when performing the current step):

• Two-way Frame Delay Measurement counters:
– M5142C0 - soamTwowayAverageDelay
– M5142C1 - soamTwowayMaxDelay
– M5142C2 - soamTwowayMinDelay
g The Frame Delay counters must be always greater than zero at the present
moment.
Issue: 01 DN09146788 113

g The measurement data of each minute can be monitored only using:

Expected outcome
The Two-way Frame Delay counters are greater than zero.
g The proper PM counters are presented during the one minute measurement.
The proper PM counters are updated after the completion of one minute
measurement.
5 Verify that the proper alarm has been raised when the threshold was reached.
g This step must be performed one minute after measurement start.

The proper alarm can occur for (when performing the current step):
• Two-way Frame Delay Measurement
Expected outcome
The proper alarm has been raised when the threshold was reached.
g The proper alarm does not occur when the threshold has been set to zero.
The proper alarm occurs only when the threshold has been reached after
the one minute measurement.
g The proper alarms are presented as faults at the BTS Site Manager.
g The proper alarms are reported from the BTS to the OMS / NetAct promptly.
The proper alarms can be monitored also using:
• NetAct Monitor
Further information
The proper alarms are canceled when the thresholds are not reached after the next
one minute measurement for:
• Two-way Frame Delay Measurement
6 After fifteen minutes verify that the proper PM counters are greater than zero.
g This step must be performed fifteen minutes after measurement start.
The proper PM counters are (when performing the current step):

• Frame Loss Measurement counters:
– M5141C0 - soamIngressFramesLost
– M5141C1 - soamIngressTotalFrames
– M5141C2 - soamNearEndFrameLossRatio
114 DN09146788 Issue: 01

– M5141C3 - soamEgressFramesLost
– M5141C4 - soamEgressTotalFrames
– M5141C5 - soamFarEndFrameLossRatio
• One-way Frame Delay Variation Measurement counters:

– M5143C0 - soamOnewayNearEndDelayVariation
– M5143C1 - soamOnewayFarEndDelayVariation
g The Two-way Frame Delay Measurement counters can be verified again.
g The Frame Loss counters are greater than zero only when there are any lost
frames.
The Frame Delay counters must be always greater than zero at the present
moment.
g The measurement data of each minute can be monitored only using:

Expected outcome
The One-way Frame Delay Variation counters are greater than zero.
The Frame Loss counters are greater than zero.
g The proper PM counters are presented during the fifteen minutes

measurement.
The proper PM counters are updated after the completion of fifteen minutes
measurement.
7 Verify that the proper alarm has been raised when the threshold was reached.
g This step must be performed fifteen minutes after measurement start.

The proper alarm can occur for (when performing the current step):
• One-way Frame Delay Variation Measurement
Expected outcome
The proper alarm has been raised when the threshold was reached.
g The proper alarm does not occur when the threshold has been set to zero.
The proper alarms occur only when the thresholds have been reached after
the fifteen minutes measurement.
g The proper alarms are presented as faults at the BTS Site Manager.
Issue: 01 DN09146788 115

g The proper alarms are reported from the BTS to the OMS / NetAct promptly.
The proper alarms can be monitored also using:
• NetAct Monitor
Further information
The proper alarms are canceled when the thresholds are not reached after the next
fifteen minutes measurement for:
• One-way Frame Delay Variation Measurement

g NetAct does not support one-minute statistics.
9 Verify that the proper PM counters are greater than zero.

Expected outcome
The One-way Frame Delay Variation counters are greater than zero.
The Frame Loss counters are greater than zero.
Expected outcome
The Frame Loss/Delay Measurement sessions have been activated successfully.
3.1.4 Deactivating RAN2243: Performance Monitoring Based on

ETH Service OAM
Purpose
The purpose of this procedure is to deactivate the performance monitoring (PM) feature.
Before you start

The deactivating procedure does not cause downtime.
The deactivating procedure can be performed at any time of the day.
The deactivating procedure needs that the feature has been activated successfully.
116 DN09146788 Issue: 01

The deactivating procedure to deactivate the Ethernet Service OAM PM (BTS) needs:

The deactivating procedure to deactivate the PM measurement sessions (BTS) needs:

The deactivating procedure to stop the measurements at OMS needs:

The deactivating procedure consists of three procedures:
• deactivating Ethernet Service OAM PM

• deactivating Frame Loss Measurement session
• deactivating Frame Delay Measurement session
3.1.4.1 Deactivating Ethernet Service OAM PM

Purpose
This procedure is used to deactivate the Ethernet Service OAM PM on the BTS.
Before you start

This procedure can be performed by disable the license of one of the features:

g The Ethernet Service OAM PM features are stopped after one of the actions:
• The Ethernet Service OAM PM has been deactivated.

• The Ethernet Service OAM has been deactivated.

alternatively.
2 Turn off the Ethernet Service OAM PM feature on the BTS.

c) Unmark the Ethernet Service OAM performance monitoring in use checkbox.
Issue: 01 DN09146788 117

g The deactivation must be confirmed using the Send button when using the
BTS Site Manager.
Expected outcome
The Ethernet Service OAM PM has been deactivated successfully on the BTS.
The BTS discards the incoming PM messages from the remote MEPs.
The PM measurement sessions are not supported on the BTS.
The PM measurement sessions are stopped on the BTS and PM alarms are canceled.
The PM measurement sessions activation on the BTS does not have any effect.
The Frame Loss/Delay statistics are not cleared but they are not further updated.
g The proper measurements have to be stopped at OMS. The measurements are:
• M5141 - Soam Frame Loss statistics

• M5142 - Soam Two Way Delay Statistics
• M5143 - Soam One Way Delay Variation Statistics
g The operator can also deactivate a single PM measurement session.

The above operation can be performed without fully deactivation of PM feature.
3.1.4.2 Deactivating Frame Loss Measurement session

Purpose
This procedure is used to deactivate the Frame Loss Measurement session on the BTS.
This procedure consists also of the step to stop the associated measurement at OMS.
Before you start

This procedure needs the activation of the Frame Loss Measurement session on the
BTS.
This procedure needs the activation of the associated measurement at OMS.

g The Frame Loss Measurement session (BTS) stops after one of the actions:
• The Frame Loss Measurement session has been deactivated.

118 DN09146788 Issue: 01


alternatively.
2 Turn off the Frame Loss Measurement session on the BTS.

c) Perform one of the actions:
• Unmark on the Frame loss measurement in use checkbox.
• Delete the selected measurement session using Delete button.
BTS Site Manager.
Expected outcome
The Frame Loss Measurement session has been stopped on the BTS.
When Frame Loss Measurement session has been stopped on the BTS then:
• The BTS stops measuring the Frame Loss statistics.
• The BTS stops sending the Frame Loss Measurement data to the OMS.
• The BTS discards the incoming Frame Loss messages from the remote MEPs.
• The Frame Loss messages are not transmitted anymore.
• The Frame Loss alarm is canceled.
• The Frame Loss statistics are not cleared but they are not further updated.
3 Stop the Soam Frame Loss statistics measurement (M5141) at OMS.

Expected outcome
The Soam Frame Loss statistics measurement has been stopped at OMS.
The OMS stops sending the Frame Loss Measurement data to the NetAct.
3.1.4.3 Deactivating Frame Delay Measurement session

Purpose
This procedure is used to deactivate the Frame Delay Measurement session on the BTS.
The procedure consists also of the steps to stop the associated measurement at OMS.
Issue: 01 DN09146788 119

Before you start

This procedure needs the activation of the Frame Delay Measurement session on the
BTS.
This procedure needs the activation of the associated measurement at OMS.

g The Frame Delay Measurement session (BTS) stops after one of the actions:
• The Frame Delay Measurement session has been deactivated.


alternatively.
2 Turn off the Frame Delay Measurement session on the BTS.

c) Perform one of the actions:
• Unmark on the Delay measurement in use checkbox.
• Delete the selected measurement session using Delete button.
BTS Site Manager.
Expected outcome
The Frame Delay Measurement session has been stopped on the BTS.
When Frame Delay Measurement session has been stopped on the BTS then:
• The BTS stops measuring the Frame Delay statistics.
• The BTS stops sending the Frame Delay Measurement data to the OMS.
• The BTS discards the incoming Frame Delay messages from the remote MEPs.
• The Frame Delay messages are not transmitted anymore.
• The Frame Delay alarms are canceled.
• The Frame Delay statistics are not cleared but they are not further updated.
120 DN09146788 Issue: 01

3 Stop the Soam Two Way Delay Statistics measurement (M5142) at OMS.

Expected outcome
The Soam Two Way Delay Statistics measurement has been stopped at OMS.
The OMS stops sending the Two-way Frame Delay Measurement data to the NetAct.
4 Stop the Soam One Way Delay Variation Statistics measurement (M5143) at
OMS.

Expected outcome
The Soam One Way Delay Variation Statistics measurement has been stopped at
OMS.
The OMS stops sending the One-way Frame Delay Variation Measurement data to
the NetAct.
Issue: 01 DN09146788 121

Operability features RU50 Feature Descriptions and Instructions
4 Operability features
4.1 RAN2199: BTS Event Triggered Symptom Data

Collection
4.1.1 Description of RAN2199: BTS Event Triggered Symptom
Data Collection
This feature introduces automatic fault-triggered BTS symptom data collection. The
triggering BTS faults are defined in the Site Configuration File (SCF) using the NetAct
Configurator.
4.1.1.1 Benefits
End-user benefits
Operator benefits
• Automatic symptom data collection reduces the workload.

• The immediate data collection following the fault occurrence assists the
troubleshooting process. Self-triggered symptom data generation is more accurate
and thus more efficient in solving failures.
Software requirements lists the software required for this feature.
RNC
RU50 Not planned RN8.0 Planned for Not planned OMS3.0 WN9.0
later
releases

BTS BTS
Planned for Planned for Support not Support not Support not Support not Support not
later later required required required required required
releases releases
122 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions Operability features
This feature requires one of the following features:

The event triggered symptom data collection can be divided into following steps:
1. Selection of the triggering faults

2. Data collection after the selected faults occur
3. Data transfer and storage
4. Viewing the collected data
Figure 6: Symptom data collection from the BTS illustrates the log collection mechanism.
Figure 6 Symptom data collection from the BTS
Selection of the triggering faults

The automatic symptom data collection is triggered by BTS faults selected by the user,
who should contact the NSN Technical Support personnel to get the list of recommended
triggers. The list of faults is defined with the symptomDataTriggerL parameter.
g The list of BTS faults is available in the Flexi Multiradio BTS WCDMA Faults
document. The TRS faults (IDs within range 61000-61999) are not considered
as triggers for the symptom data collection.
A triggering threshold can be set - it defines how many times a certain fault should occur
for the same fault source to trigger the data collection. By default no triggers are defined.
Data collection after the selected faults occur
The log collection happens only when the fault occurs. The log consists of, for example:
• computer log writings
Issue: 01 DN09146788 123

• HW configuration
• alarm history
• active SW version
• transport configuration
• black box data
• performance data
• auto-connection report
Data transfer and storage

Symptom data consists of one or several files that are transferred separately to OMS
immediately after the data has been collected. The OMS is able to perform simultaneous
uploads from several BTSs. The existing file transfer mechanism through the BTSOM
interface is used to transfer the data to OMS. If the triggering fault leads to a recovery
reset of the BTS, the upload to OMS is stopped and it is not restarted automatically.
In the OMS, the files are combined into one package file. This file is named in a common
way: TSUPL_<NE>_<NEid>_BTS_<BTSid>_<TRSHid>.<date-time>.tar
The name contains the following information:
• TSUPL: used by OMS to identify the file type as a symptom data file
• <NE>: identifies the controller (for example, RNC)
• <NEid>: the controller ID number
• <BTSid>: the BTS ID number
• <TRSHid>: identifies the troubleshooting task in the BTS
• <date-time>: indicates when the file is created (using the OMS local time). The date
and time format is YYYYMMDDhhmmss.
The files are stored in the following directory:

/var/opt/OMSftproot/NE/TroubleshootingData
g The 71106 TROUBLESHOOTING DATA RECEIVED alarm indicates that the log
file has been transferred to OMS. The dwAlarmForUploadCompleted
parameter is used for disabling/enabling the alarm setting in OMS.
The 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED
indicates that the data creation or upload to OMS has failed.
Old symptom data files are deleted automatically from the BTS (after being transferred to
OMS). When the clean up procedure starts in the OMS, the OMS deletes files older than
certain number of days (defined with the dwNELogDaysSpan parameter). By default,
files older than 10 days are removed. Additionally, the OMS monitors the disk space use
and if needed, performs additional clean up procedure.
With the dwBTSUploadEnabled parameter, the automatic data transfer to OMS can be
enabled/disabled.
Viewing the collected data
The files can be viewed using the Log Viewer in the OMS Element Manager. The Log
Viewer introduces the Troubleshooting data filter component to allow user to filter
troubleshooting files to show only those files not older than a defined period of days
(user can specify value from 1 to 30). When user logs in to OMS Element Manager, the
Troubleshooting data filter component contains the default value which is taken from the
124 DN09146788 Issue: 01

HideTRSFilesOlderThanDaysFilter LDAP parameter (2 days) or from the web

browser cookie (if any is stored). When the user sets new value in this component, this
new value is preserved within the same session and also restored next time when the
user logs in to OMS Element Manager (web browser cookie mechanism is used to
preserve the value set by the user).
The troubleshooting data files can also be downloaded to the client's computer using the
Log Viewer. Only the archive files can be downloaded and not the content of the archive.
The log files are sent to OMS even if the BTS fault was filtered by the BTS alarm system
and the related alarm was not displayed in OMS.

This feature is a part of generic troubleshooting data collection function that consists of
the following features:
• RAN1873: OMS Troubleshooting Data Collection

• RAN1805: RNC Event Triggered Symptom Data Collection
• RAN2446: Emergency Symptom Data Collection in IPA-RNC
Impact on commands

This feature has no impact on network element management tools.

4.1.1.5 RAN2199: BTS Event Triggered Symptom Data Collection

management data
Alarms
Table Related existing alarms lists existing alarms related to this feature.
Table 62 Related existing alarms
Alarm ID Alarm name
71106 TROUBLESHOOTING DATA RECEIVED
Issue: 01 DN09146788 125

Table 62 Related existing alarms (Cont.)
Alarm ID Alarm name
71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILED


Parameters
Table New parameters lists parameters introduced with this feature.
Symptom data trigger list symptomDataTriggerL MRBTS
Table 64 New OMS LDAP parameters
Attribute
ClusterRoot/OMS/OMSPlatform/SS_SpringyUI/HideTRSFilesOlderThanDaysFilter
g To make the new value effective, user needs to restart TomcatPlat using the following
command: fshascli -rn /TomcatPlat
Table 65: Related existing OMS LDAP parameters lists existing parameters related to
this feature.
Table 65 Related existing OMS LDAP parameters
Attribute
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwAlarmForUploadCom
pleted
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUploadEnabled
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwNELogDaysSpan
126 DN09146788 Issue: 01

Table 65 Related existing OMS LDAP parameters (Cont.)
Attribute
g When the LDAP parameter value is changed, the new value immediately takes effect
(no additional action is necessary). It applies to all parameters in this table.
BSW RAN -
4.1.2 Activating RAN2199: BTS Event Triggered Symptom Data

Collection
Purpose
Follow this procedure to activate the RAN2199: BTS Event Triggered Symptom Data
Collection feature. For more information on the feature, see the RAN2199: BTS Event
Triggered Symptom Data Collection feature description in RU50 Feature Descriptions
and Instructions.
Before you start
g The feature is activated when the operator enables automatic upload of

symptom data to OMS using the dwBTSUploadEnabled LDAP parameter. By
default the functionality is turned on.
The actual symptom data collection takes place if any triggering faults have been defined
during the BTS commissioning. The list of faults is defined using the Symptom data
trigger list (symptomDataTriggerL) parameter under the MRBTS object.
Restart of the RNC, OMS or BTS is not required after the activation of this feature. This
procedure does not cause downtime, and it can be performed at any time of the day.
Make sure you have access to the Parameter Tool in the OMS Element Manager.
1 Log in to OMS Element Manager.
2 Open the Parameter Tool.

The Parameter Tool is available in the External Applications (in the Application
Launcher window that is displayed).
Issue: 01 DN09146788 127

3 Change the dwBTSUploadEnabled LDAP parameter value to 1.

Path:
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload
Enabled
Expected outcome
The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned on.
Further information
It takes approximately 10 minutes to make the change effective in the OMS.
4.1.3 Deactivating RAN2199: BTS Event Triggered Symptom

Data Collection
Purpose
Follow this procedure to deactivate the RAN2199: BTS Event Triggered Symptom Data
Collection feature. For more information on the feature, see the RAN2199: BTS Event
Triggered Symptom Data Collection feature description in RU50 Feature Descriptions
and Instructions.
Before you start
Restart of the RNC, OMS or BTS is not required after the deactivation of this feature.
This procedure does not cause downtime, and it can be performed at any time of the
day.
Make sure you have access to the Parameter Tool in the OMS Element Manager.
1 Log in to OMS Element Manager.
2 Open the Parameter Tool.

The Parameter Tool is available in the External Applications (in the Application
Launcher window that is displayed).
3 Change the dwBTSUploadEnabled LDAP parameter value to 0.

Path:
ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwBTSUpload
Enabled
Expected outcome
The RAN2199: BTS Event Triggered Symptom Data Collection feature is turned off.
Further information
It takes approximately 10 minutes to make the change effective in the OMS.
128 DN09146788 Issue: 01

4.2 RAN2554: Transport Configuration Fall-back

4.2.1 Description of RAN2554: Transport Configuration Fallback
If after a configuration update the Flexi Multiradio BTS fails to connect to its management
network, self healing measures are taken. This applies for failures during normal
operation after a configuration-update.
4.2.1.1 Benefits
End-user benefits
Operator benefits
• Self healing reduces the effort for network management and maintenance and
• increases the Flexi Multiradio BTS availability due to less outage.
• Site visits can be avoided when a changed BTS transmission configuration prohibits
remote management connections.
Table 67: Software requirements lists the software that is required for this feature.
RAS Flexi Direct IPA-RNC mcRNC OMS BTS Flexi Flexi Lite
RU50 Not planned Support not Support not Support not WN9.0 Planned for
required required required later
releases
BTS Flexi 10 NetAct MSC SGSN MGW UE
Planned for Support not Support not Support not Support not Support not
later releases required required required required required

Issue: 01 DN09146788 129


Autonomous fallback to previous configuration
A fallback to the previous configuration happens when the BTS fails to successfully
(re)connect the M-plane to the Network Management System after a remote
configuration update and activation. If the M-plane can be established with the old
configuration, a notification is sent to the Network Management System indicating that
the new configuration was not activated. If the old one fails as well, the received new one
is activated again and the BTS continues with the regular link failure mechanism.
The self healing recovery is initiated only after Transport Network Layer (TNL)
configuration changes via BTS Site Configuration file (SCF) activation. The TNL
configuration refers to the parameters defined in the Transport System (TRS) PDDB.
Figure 7 RAN2554: Transport Configuration Fallback
g Self-healing is not allowed when BTSSM is connected to the BTS.

There are no interdependencies between features.
130 DN09146788 Issue: 01

Impact on commands

The self healing functionality and logic are implemented in the BTS. There are new
parameters introduced, which impact NetAct adaptation.

4.2.1.5 RAN2554: Transport Configuration Fallback management data
Alarms
The following table lists alarms and faults, which are related to this feature.
Table 68 New fault
Alarm ID Alarm name
7665 New fault coming with: BASE STATION TRANSMISSION ALARM. Meaning
of new fault: the base station has recovered the M-plane connection by
falling back to the old transport configuration after the configuration change
Parameters
Table 69 New parameter
Enable transport configuration fallback enableTransportConfigF IPNO

allback
ASW RAN BTS LK
Issue: 01 DN09146788 131

4.2.2 Activating RAN2554: Transport Configuration Fallback

Purpose
Follow this procedure to activate RAN2554: Transport Configuration Fallback feature.
For more information on this feature, see Description of RAN2554: Transport
Configuration Fallback. The feature can be activated using BTS Site Manager or NetAct
CM Editor.
Before you start
This feature requires that FSMrel2 (excluding FSIA and FSIB) or FSMrel3 is present.
4.2.2.1 Activating RAN2554: Transport Configuration Fallback using BTS

Site Manager
1 Open the BTS Site manager.
2 Download feature license to BTS.

a) In the Configuration menu, choose License Management.
b) A License Managament window opens. Select the appropriate license file
and click Download to BTS.
3 Enable transport configuration fallback.

a) In the Configuration menu, choose IP Configuration.
b) Choose IP Adresses tab.
Or in the IP view, choose the IP Addresses tab.
c) Check the Enable Transport Configuration Fallback checkbox.
4.2.2.2 Activating RAN2554: Transport Configuration Fallback from NetAct

CM Editor
1 Open NetAct CM Editor
2 Configure IPNO/enableTransportConfigFallback to "True".
3 Activate SCF in BTS from NetAct.

When enableTransportConfigFallback is set to "True" using SCF then
corresponding license is automatically downloaded to BTS.
4.2.3 Verifying RAN2554: Transport Configuration Fallback

Purpose
Follow this procedure to verify that this feature has been activated successfully.
132 DN09146788 Issue: 01

1 Activate the transport configuration fallback feature.

For more information see, Activating RAN2554: Transport Configuration Fallback.
2 Testing the transport configuration fallback feature.

For more information see, Testing RAN2554: Transport Configuration Fallback.
4.2.4 Testing RAN2554: Transport Configuration Fallback

Purpose
The purpose of this test is to verify if the RAN2554 Transport Configuration Fallback
feature is activated and working correctly.
Before you start
Required test environment:
• 1 Flexi Multiradio BTS WCDMA integrated to the network with FSMrel2 (excluding
FSIA and FSIB) or FSMrel3
• NetAct integrated to the network.
• RNC/mcRNC integrated to network
The following conditions must be true before testing:
• Enable transport configuration fallback from SEM, or from NetAct.

• Make sure that the license for RAN2554 Transport Configuration Fallback is valid on
NetAct.
• Ensure that the BTSOM is connected with source RNC on OMS GUI, the
DCNLinkStatus on OMS is Enabled, and the WCELs are alive.
4.2.4.1 Test Case 1: Transport configuration fallback
Steps
1 Create a new TRS plan.

a) Open NetAct CM Editor.
b) Modify the TNL parameters to an unreachable RNC IP address;.
For example, the reachable RNC IP address is 10.68.178.18, we may modify it to

10.82.1.1 which is unreachable.
g It is also feasible to modify TNL parameters by recommisionning the WBTS

via SEM.
Result
The paremeters are modified successfully in the plan.
2 Download and activate the plan to the WBTS.
Result
The plan provisions successfully and after the TRS/BTS restart, the BTS is
disconnected to the unreachable RNC.
Issue: 01 DN09146788 133

3 Connect to the WBTS locally, and monitor the O&M status of the WBTS.
Result
RNC IP has been modified to new target IP on WBTS IP configuration, and WBTS
OAM status is disconnected
4 Check the WBTS and WCELs status on target RNC on Netact GUI.
There will be no new target RNC because it is not a valid IP address.
Result
After the WBTS initiates re-establishment to the new target RNC for 10 connection
attempts, the WBTS falls back to the original RNC. Then DCNLinkStatus with
original RNC is Enabled, and the WCELs are alive.
5 Check the BTS status. Check the alarm on BTS, OMS, and NetAct.
Result
The WBTS modifies its RNC IP into the original RNC IP address, and O&M's
connection to the original RNC is established.
g An alarm is issued indicating that the planned configuration changes are not
used in the WBTS --- 7665 BASE STATION TRANSMISSION ALARM is
present.

a) Open the NetAct CM Editor.
b) Modify the TNL parameters to a reachable IP address.
c) Provision the plan.
Result
The parameter modification and provision are successful, and the BTS connects to
the new target RNC.
g The configuration change is a corrective configuration change for an earlier

recovery ending in the fallback operation. The alarm
7665 BASE STATION TRANSMISSION ALARM is cancelled on BTSSM,
OMS, and NetAct GUI.
4.2.4.2 Test Case 2: Transport configuration roll forward
Steps

a) Open NetAct CM Editor.
b) Modify the TNL parameters to an unreachable RNC IP address;.
For example, the reachable RNC IP address is 10.68.178.18, we may modify it to

10.82.1.1 which is unreachable.
134 DN09146788 Issue: 01

Result
The parameters are modified successfully in the plan.
2 Download and activate the new plan to WBTS.
Result
The plan provisions successfully and after the TRS/BTS restart the BTS is
disconnected to the unreachable RNC.
3 Connect to WBTS locally, and monitor the O&M status of the WBTS.
Result
After the WBTS initiates re-establishment to the new target RNC for 10 connection
attempts, the WBTS falls back to the original RNC.
4 Check the BTS and WCELS status on a new target RNC on NetAct GUI.
Result
After WBTS initiates re-establishment to the new target RNC for ten connection
attempts, WBTS fall back to the original RNC
5 Disable the O&M of the WBTS.

a) When the WBTS is trying to connect to new target RNC, log on to the
original RNC.
b) Use the following command to delete the O&M route:
ZQKA:[<route_id>]:[<unit_type>,[<unit_index>]];
Result
The WBTS modifies its RNC IP to original RNC IP address, but WBTS will not be
able to connect because O&M is disabled on original RNC. After 10 times attempts,
the WBTS roll forward to the new target RNC once more.
6 Check the BTS status. Check the alarm on BTS, OMS, and NetAct.
Result
The O&M connection to both RNC is unestablished. In the WBTS site manager, the
RNC IP address should be the new target RNC. No RAN2554 alarm would be
present in the SEM.

a) Open the NetAct CM Editor.
b) Use the following command to create a new O&M route:
ZQKC:<unit type>,<unit index...>:
[<destination IP address>|<default route> def,
[<netmask length>]]:<gateway IP address>:
[<route type>]:[<preference>];
Issue: 01 DN09146788 135

c) Modify the TNL parameters to a reachable IP address.

d) Provision the plan.
Result
The parameter modification and provision are successful, and the BTS connects to
the target RNC.
4.2.5 Deactivating RAN2554: Transport Configuration Fallback

Purpose
Follow this procedure to deactivate RAN2554: Transport Configuration Fall-back. For
more information, see Description of RAN2554: Transport Configuration Fall-back. The
feature can be activated using BTS Site Manager or NetAct CM Editor.
Before you start
Make sure that RAN2554: Transport Configuration Fallback feature is already activated.
4.2.5.1 Deactivating RAN2554: Transport Configuration Fallback using BTS
Site Manager
1 Disabling the feature

a) Open BTS Site manager.
b) Choose the IP Addresses tab.
c) Uncheck the Enable Transport Configuration Fallback checkbox.
4.2.5.2 Deactivating RAN2554: Transport Configuration Fallback from

NetAct CM Editor
1 Disabling the feature

a) Open NetAct CM Editor
b) Configure IPNO/enableTransportConfigFallback to "False".
c) Activate SCF in BTS from NetAct.
136 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions RNC solution features
5 RNC solution features
5.1 RAN3047: RTT Improvement to Enhance User

Experience
5.1.1 Description of RAN3047: RTT Improvement to enhance
user experience
This feature will reduce RTT RNC delay in an end to end environment.
5.1.1.1 Benefits
End-user benefits
This feature provides better end user experience in terms of RTT delay.
Operator benefits
The feature provides faster data transfer for interactive applications and background
traffic.
RNC
RU50 Planned for RN8.0 Planned for Planned for OMS3.0 Support
later later later (RU50) not
releases releases releases required

BTS BTS
No hardware requirements. It is hardware independent.

Functional overview
This feature enables faster data transfer for interactive applications and background
traffic by reducing delay in data handling, and push end to end HSPA RTT delay for a 32
Byte Ping to be comparable with LTE delay.
Issue: 01 DN09146788 137

RNC solution features RU50 Feature Descriptions and Instructions
Improvement in Round Trip Time (RTT) is achieved by reducing the delay components in
the data path between the network and UE. The feature focus to reduce RNC Delay in
HS(D)PA Downlink data path by using data arrival event to schedule data towards BTS
in Iub.
The data event trigger enables reduction of RTT, which further improves the response
times for interactive services and faster data transfer for background traffic, thereby
enhancing the user experience.

This feature has no feature interdependencies.
Impact on commands

tools.

5.1.1.5 RAN3047: RTT Improvement to enhance user experience

management data
Alarms

There are no key performance indicators related to this feature at this time.

Parameters
There are no key performance indicators related to this feature at this time.
138 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions RNC solution features
BSW RAN RNC LK
Issue: 01 DN09146788 139

BTS solution features RU50 Feature Descriptions and Instructions
6 BTS solution features
6.1 RAN3017: Additional 6 WCDMA Cell Activation

6.1.1 Description of RAN3017: Additional 6 WCDMA Cell
Activation
RAN3017: Additional 6 WCDMA Cell Activation license key increases the number of
supported cells in the BTS configuration. Step size of one license key is 6 cells. In RU50
the number of cells can be up to 18.
6.1.1.1 Benefits
End-user benefits
Operator benefits
Increasing traffic, demand for multicarrier, multiband, and multi-sector sites leads
operator needs towards larger BTS site configurations, especially in hot spot areas. This
feature enables to build such configurations with simple SW configuration.

RNC
RU50 Not planned Support not Support not Not planned Support not WN9.0
required required required

BTS BTS
Not relevant WN9.1 NetAct 8 Support not Support not Support not Support not
EP1 required required required required
(RU50)

140 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions BTS solution features
For Flexi Multiradio 10 BTS this feature requires the following feature:
• RAN2262: Flexi Multiradio System Modules - FSMF

Functional overview
Site configuration enables creation up to 12 cells without a license key. To activate
additional 6 cells in BTS configuration a license key (LK) is required.
Table 74 Number of needed license keys

Number of cells License keys
0 - 12 0 x LK
13 - 18 1 x LK
g Need for license key(s) is checked based on the RNC cell setup.

Currently, RAN2736 Extended BTS Site Capacity license key is needed if BTS site
configuration has more than 12 cells. RAN3017: Additional 6 WCDMA Cell Activation
replaces the existing solution.

tools.

This feature enables the operator to enlarge site configuration by adding new cells.
6.1.1.5 RAN3017: Additional 6 WCDMA Cell Activation management data
Alarms

Issue: 01 DN09146788 141


Parameters
Extended BTS site capacity extendedBtsSiteCapacity BTSSCW
enabled

BSW/ASW SW component License control in network
element
ASW RAN BTS LK
6.1.2 Activating RAN3017: Additional 6 WCDMA Cell Activation

Purpose
Follow the procedure below to activate the RAN3017: Additional 6 WCDMA Cell
Activation.
Before you start
Make sure you have access to the BTS Site Manager.
g Note that this feature is under license control. This feature requires a valid
license file. The feature code is 0000005171. See
WCDMA RAN License Operation document for details.
1 Start the WCDMA BTS Site Manager application and establish the connection
to the BTS.
Flexi Multiradio BTS WCDMA can autonomously request for missing license file(s)
from NetAct Licence Manager during feature activation (RAN2131: Automatic
Licence Distribution to Flexi BTS).
Make sure that you have selected Automatic licensing in use checkbox in the
Automatic License Distribution Settings page.
g If RAN2131: Automatic Licence Distribution to Flexi BTS is not activated,

relevant license must be uploaded manually.

When BTS Site Manager is connected to the BTS, it automatically uploads the
current configuration plan file from the BTS.
142 DN09146788 Issue: 01

RU50 Feature Descriptions and Instructions BTS solution features
3 Activate RAN3017: Additional 6 WCDMA Cell Activation feature.

Go to Local Cell Resources page and select the Extended BTS site capacity
enabled checkbox.
Figure 8 Activating RAN3017: Additional 6 WCDMA Cell Activation
4 Send the commissioning plan file to the BTS.

Click Send Parameters button.
You might save the parameters at this point.
5 The new commissioning plan file is automatically activated in the BTS.

BTS Site Manager 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.
Result
The feature RAN3017: Additional 6 WCDMA Cell Activation is activated.
6.1.3 Verifying RAN3017: Additional 6 WCDMA Cell Activation
Purpose
Follow steps below to verify that the activation of the RAN3017: Additional 6 WCDMA
Cell Activation feature has been successful.
Issue: 01 DN09146788 143

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

When BTS Site Manager is connected to the BTS, it automatically uploads the
current configuration plan file from the BTS.
3 Verify that Extended BTS site capacity enabled checkbox is selected.

The value of BTSSCW extendedBtsSiteCapacity parameter should be 1/true.
Additionally, verify on the main page that all created cells are working:
• local cell state is "Operational"
• operational state is "Enabled"
• working state is "Working"
6.1.4 Deactivating RAN3017: Additional 6 WCDMA Cell

Activation
Purpose
To deactivate RAN3017: Additional 6 WCDMA Cell Activation feature, follow this
procedure.
Before you start
1 Start BTS Site Manager application and establish the connection to the BTS.
2 Perform recommissioning procedure.

Select Commissioning, choose reconfiguration.
3 Disable RAN3017: Additional 6 WCDMA Cell Activation feature.

Go to Local Cell Resources page and remove the selection from the Extended BTS
site capacity enabled checkbox.
4 Complete the recommissioning procedure.
144 DN09146788 Issue: 01

RU50 Feature Descriptions of N PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RU50 Feature Descriptions of N PDF

Uploaded by

Copyright:

Available Formats

Introduction to RU50 features RU50 Feature Descriptions and Instructions

1 Introduction to RU50 features

1.1 RU50 radio resource management features

Table 1 RU50 radio resource management features

Feature Other related descriptions Related instructions

Table 1 RU50 radio resource management features (Cont.)

Feature Other related descriptions Related instructions

WCDMA RAN SRNS Relocation

1.2 RU50 telecom features

1.3 RU50 transmission and transport features

Table 2 RU50 transmission and transport features

Feature Other related descriptions Related instructions

RAN2243: Performance Monitoring WCDMA RAN IP Transport Activating RAN2243: Performance

1.4 RU50 operability features

Table 3 RU50 operability features

Feature Other related descriptions Related instructions

1.5 RU50 performance monitoring features

1.6 RU50 RNC solution features

Table 4 RU50 RNC solution features

Feature Other related descriptions Related instructions

1.7 RU50 BTS solution features

Table 5 RU50 BTS solution features

Feature Other related descriptions Related instructions

g Some RNC-controlled features are activated using an RNC general parameter

g There are no licenses in the Flexi Direct RNC.

License management in mcRNC

License management in WBTS

1.9 Reference documentation

• WCDMA Radio Network Configuration Parameters Excel in WCDMA RAN Operating

For counter descriptions, see:

• RNC Counters - RNW Part

For alarm descriptions, see:

• IPA-RNC Notices (0-999)

For key performance indicator descriptions, see:

• WCDMA RAN Key Performance Indicators

2 Radio resource management features

2.1 RAN2963: Data Session Profiling

• It allows operators to use higher thresholds for common channels. Keep-alive-type

Table 6 Software requirements

2.1.1.3 Functional description

• RNFC-DCHtoPCHEnabled should be set to its default value - enabled.

2.1.1.4 System impact

Impact on network and network element management tools

Impact on system performance and capacity

2.1.1.5 RAN2963: Data Session Profiling management data

Measurements and counters

Table 7 New counters

Counter ID Counter name Measurement

M1006C309 SUCCESSFUL PCH TO DCH TRANS DUE RRC signalling (RNC)

Table 8 Related existing counters

Counter ID Counter name Measurement

M1006C174 STATE TRANSITION TIME PCH TO DCH RRC signalling (RNC)

M1006C175 DENOMINATOR FOR STATE TRANSITION RRC signalling (RNC)

M1006C196 ATTEMPTED PCH TO DCH TRANSITIONS RRC signalling (RNC)

M1006C197 SUCCESSFUL PCH TO DCH RRC signalling (RNC)

M1006C198 CELL RESELECTIONS DURING PCH TO RRC signalling (RNC)

Key performance indicators

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 HSChaPrefInDataSesProf RNPS