29 Nokia-RU50 Feature Descriptions and Instructions

8/9/2019 29 Nokia-RU50 Feature Descriptions and Instructions

http://slidepdf.com/reader/full/29-nokia-ru50-feature-descriptions-and-instructions 1/144























































































































































2.7.1.5 RAN3069: RSRQ-based LTE Reselection 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

There are no measurements or counters related to this feature.

Key performance indicators

There are no key performance indicators related to this feature.

Parameters

Table 44: New parameters lists parameters introduced with this feature and thecorresponding SIB19 parameters specified in 3GPP Rel-9.

Table 44 New parameters

Full name

Abbreviated name

SIB19 IE

Managedobject

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

2.7.1.6 Sales information

Table 45 Sales information

BSW/ASW

SW component

License control in network element

ASW 1) 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.

Radio resource management features RU50 Feature Descriptions and Instructions

76 DN09146788 Issue: 01



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.

g The RAN2067: LTE Interworking feature license also controls theRAN3069: RSRQ-based LTE Reselection feature. Activate theRAN2067: LTE Interworking feature controlled by the license keyLTE 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,ma ke sure to admit each Radio Acces s Technology a different priority:

• AbsPrioCellReselec WCEL parameter, introduced with the RAN2067:LTE Interworking feature, defines the priority of the WCDMA serving cell (UTRA priorityinfo list/UTRA Serving Cell IE)

• AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881:WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequencypriority (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 priorityinfo list/GSM Priority Info IE)

• AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE Interworking feature , defines the LTE priority (E-UTRA frequency and priority infolist/E-UTRA frequency and priority IE)

g Priority-based cell-reselection between GSM and WCDMA radio technologies isprovided by the RAN2881: WCDMA and GSM Layer Priorities feature.

WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority valueshould be given for each inter-frequency WCDMA neighbor. If more than one value isgiven, the highest priority is broadcast in SIB19 message.

g If quality criteria are chosen to be used for LTE absolute-priority-based cellreselection, ensure that both Threshx, high2 (AdjLThreshigh2 HOPLparameter) and Threshx, low2 (AdjLThreslow2 HOPL parameter) areconfigured at the same time and broadcast in SIB19. Otherwise UE is not usingthese parameters. Also, ensure that priorities for which both Threshx, high2and Threshx, low2 are provided in SIB19 are always different from thepriorities for which these parameters are not provided in SIB19. By defaultThreshx, high2 and Threshx, low2 are not broadcast in SIB19.

g Note that the activation procedure for theRAN3069: RSRQ-based LTE Reselection feature is the same as for theRAN2067: LTE Interworking feature.

RU50 Feature Descriptions and Instructions Radio resource management features

Issue: 01 DN09146788 77



1 Open the OMS Element Manager.

2 Go to Topology and expand the ROOT directory.

3 Expand the RNC object and then the WBTS object.

4 Configure the WCEL object:

a) Right-click on the WCEL object and select Edit parameters.

b) In System Info tab, set the values of LTECellReselection parameter toEnabled.

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

2.7.3 Verifying RAN3069: RSRQ-based LTE Reselection

Purpose

Follow these tips to verify that the RAN3069: RSRQ-based LTE Reselection featureworks properly in the network.

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 moreinformation, see Activating RAN2067: LTE Interworking and Verifying RAN2067: LTE Interworking .

g There are no counters involved in cell reselection process. The UE reselects thecell 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 thecontent of SIB19 message. After activating this feature and ascribing values to the

parameters listed in RAN3069: RSRQ-based LTE Reselection management datasection, 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 protocolanalyzer.

Further information

Camping on a desired layer is performed by the UE using SIB19 parameters. Cellreselection algorithm is specified in 3GPP TS 25.304 User Equipment (UE) proceduresin 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 Reselectionfeature.

Before you start

g In order to verify usage of the quality criteria for LTE absolute priority based cellreselection, activation of the RAN2067: LTE Interworking feature was needed.Therefore, for deactivating the RAN3069: RSRQ-based LTE Reselectionfeature, instructions on the RAN2067: LTE Interworking feature deactivation arealso included. For more information, seeDeactivating RAN2067: LTE Interworking .






b) In System Info tab, set the values of LTECellReselection parameter toDisabled.

2.8 RAN2264: Smart LTE Handover

2.8.1 Description of RAN2264: Smart LTE Handover

Introduction to the feature

The RAN2264: Smart LTE Handover feature introduces inter-RAT WCDMA to LTE

handover. This feature supports traffic steering to LTE layers, providing seamlesshandover 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, ashandover is preceded with compressed mode measurements.


Issue: 01 DN09146788 79



2.8.1.2 Requirements

Software requirements

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

Table 46 Software requirements

RAS

Flexi Direct

IPA-RNC

mcRNC

FlexiDirect RNC

OMS

Flexi BTS

RU50 Planned for later releases

RN8.0 Planned for later releases

Planned for later releases

OMS 3.0(RU50)

WN9.0

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE



NetAct 8EP1

Support notrequired


Support notrequired

3GPP Rel-8 (optional)

Hardware requirements

For Flexi Multiradio BTS WCDMA this feature requires one of the following features:

• RAN2382: Flexi BTS Multimode System Module - FSMC • RAN1016: Flexi BTS Multimode System Module - FSMD• RAN1848: Flexi BTS Multimode System Module - FSME

2.8.1.3 Functional description

The RAN2264: Smart LTE Handover feature introduces inter-system handover fromWCDMA to LTE.

Inter-RAT handover from WCDMA to LTE can be started if compressed modemeasurements 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 modesupported by the RAN1668: HSUPA Compressed Mode for LTE and Inter-frequencyHandover 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 goodenough 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 WCDMAto both FDD-LTE and TDD-LTE.

2.8.1.4 System impact

Interdependencies between features

The RAN2067: LTE Interworking feature is a prerequisite for using this feature.

For HSUPA compressed mode measurements, the RAN1668: HSUPA CompressedMode for LTE and Inter-frequency Handover feature is required.

g This feature requires also support from the UE, 3G core network, LTE corenetwork, and LTE eNB.

Impact on interfaces

This feature causes rise of signaling traffic on Uu, Iub, Iur, and Iu PS interfaces(compressed mode related signaling, LTE neighbor reporting over Iur, relocation relatedsignaling between RNC and core network).

Impact on network and network element management tools

• New Managed Object Cla ss (MOC): ADJE is intro duced for defining E-UTRA (LTE)

neighbor cells.• New counters for monitoring outgoing LTE PS Handover are introduced.

Impact on system performance and capacity

• 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 incompressed 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 dataFor information on alarm, counter, key performance indicator, and parameter documents,see Reference documentation .

Alarms



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


Issue: 01 DN09146788 81



Table 47 New counters

Counter ID

Counter name

Measurement

M1010C240 LTE NRT ISHO MEAS WITH CM DUE TODCH TO CCH

Inter System Hard Handover

M1010C241 LTE NRT ISHO MEAS WITH CM DUE TOHSPA TO DCH


M1010C242 LTE NRT ISHO MEAS WITH CM DUE TOCS RAB RELEASE


M1010C243 LTE NRT ISHO MEAS WITH CM DUE TOPERIODIC TRIGGER


M1010C244 LTE NRT ISHO MEAS WITHOUT CM DUETO DCH TO CCH


M1010C245 LTE NRT ISHO MEAS WITHOUT CM DUETO HSPA TO DCH


M1010C246 LTE NRT ISHO MEAS WITHOUT CM DUETO CS RAB RELEASE


M1010C247 LTE NRT ISHO MEAS WITHOUT CM DUETO PERIODIC TRIGGER


M1010C248 LTE NRT ISHO NO CELL FOUND DUE TODCH TO CCH


M1010C249 LTE NRT ISHO NO CELL FOUND DUE TOHSPA TO DCH


M1010C250 LTE NRT ISHO NO CELL FOUND DUE TOCS RAB RELEASE


M1010C251 LTE NRT ISHO NO CELL FOUND DUE TOPERIODIC TRIGGER


M1010C252 LTE NRT ISHO ATTEMPTS DUE TO DCHTO CCH


M1010C253 LTE NRT ISHO ATTEMPTS DUE TO HSPATO DCH


M1010C254 LTE NRT ISHO ATTEMPTS DUE TO CSRAB RELEASE


M1010C255 LTE NRT ISHO ATTEMPTS DUE TOPERIODIC TRIGGER



82 DN09146788 Issue: 01



Table 47 New counters (Cont.)

Counter ID

Counter name

Measurement

M1010C256 LTE NRT ISHO SUCCESS DUE TO DCHTO CCH


M1010C257 LTE NRT ISHO SUCCESS DUE TO HSPATO DCH


M1010C258 LTE NRT ISHO SUCCESS DUE TO CSRAB RELEASE


M1010C259 LTE NRT ISHO SUCCESS DUE TOPERIODIC TRIGGER


M1010C260 LTE NRT ISHO UE NACK DUE TO DCHTO CCH


M1010C261 LTE NRT ISHO UE NACK DUE TO HSPATO DCH


M1010C262 LTE NRT ISHO UE NACK DUE TO CSRAB RELEASE


M1010C263 LTE NRT ISHO UE NACK DUE TOPERIODIC TRIGGER


M1010C264 LTE NRT ISHO UE LOST DUE TO DCH TOCCH


M1010C265 LTE NRT ISHO UE LOST DUE TO HSPATO DCH


M1010C266 LTE NRT ISHO UE LOST DUE TO CS RABRELEASE


M1010C267 LTE NRT ISHO UE LOST DUE TOPERIODIC 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 TORN LAYER CAUSE

LTE Relocation


Issue: 01 DN09146788 83



Table 47 New counters (Cont.)

Counter ID

Counter name

Measurement

M1036C3 LTE PS ISHO OUT PREP FAIL DUE TO TRLAYER CAUSE

LTE Relocation

M1036C4 LTE PS ISHO OUT PREP FAIL DUE TONAS CAUSE

LTE Relocation

M1036C5 LTE PS ISHO OUT PREP FAIL DUE TOPROT CAUSE

LTE Relocation

M1036C6 LTE PS ISHO OUT PREP FAIL DUE TOMISC CAUSE

LTE Relocation

M1036C7 LTE PS ISHO OUT PREP FAIL DUE TONON STAN CAUSE

LTE Relocation

M1036C8 LTE PS ISHO CANCEL TOTAL LTE Relocation

M1036C9 LTE PS ISHO FAIL DUE TO RELOCOVERALL TIMER EXPIRY

LTE Relocation

M1036C10 LTE PS ISHO CANCEL DUE TO RELOCPREP TIMER EXPIRY

LTE Relocation

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

Table 48 Related existing counters

Counter ID

Counter name

Measurement

M1010C239 DURATION OF LTE CARRIERMEASUREMENT




Parameters

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


Full name

Abbreviated name

Managed object

Outgoing LTE Handover Enabled LTEHandoverEnabled RNC/WBTS/WCEL


84 DN09146788 Issue: 01



Table 49 New parameters (Cont.)

Full name

Abbreviated name

Managed object

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 cellidentifier

AdjePhysicalCellId RNC/WBTS/WCEL/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

Table 50: Modified parameters lists parameters modified by this feature.

Table 50 Modified parameters

Full name

Abbreviated name

Managed object

RNC Options RncOptions RNC

BTS support for HSPA CM BTSSupportForHSPACM RNC/WBTS

Max number of UEs in HSDPA CM dueto NCHO

MaxNumberUEHSPACmNCHO

RNC/WBTS/WCEL

LTE Layer Cell HSDPA Load LTELayerCellHSLoad WCEL


Issue: 01 DN09146788 85



Table 50 Modified parameters (Cont.)

Full name

Abbreviated name

Managed object

Smart LTE Layering NRT user amountthreshold

SmartLTELayeringUA WCEL

Smart LTE Layering service control SmartLTELayeringServ RNMOBI

Smart LTE Layering Target SystemSelection

SmartLTELayeringTSysSel WCEL

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 SearchPeriod

LTENcarrFreqSearchPeriod RNC/FMCL

Adjacent LTE Frequency Priority AdjLFreqPriority RNC/HOPL

LTE Carrier frequency selectionMinimum Rx Power level

AdjLMinRSRPLevel RNC/HOPL

LTE Carrier frequency selectionMinimum Rx qual level

AdjLMinRSRQLevel RNC/HOPL

Identifier of inter- system adjacency toLTE

ADJLId RNC/WBTS/WCEL/ADJL

FMCL Identifier FMCLIdentifier RNC/WBTS/WCEL

Maximum number of UEs in CM due toSLHO measurement

MaxNumberUECmSLHO RNC/WBTS/WCEL

2.8.1.6 Sales informationTable 51 Sales information

BSW/ASW

SW component


ASW RAN RNC LK

2.8.2 Activating RAN2264: Smart LTE Handover

Purpose

Follow this procedure to activate this feature.


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.

Make sure you have access to the following applications:

• OMS Element Manager • Application Launcher • Man-machine interfa ce (MMI)

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 onmanaging licenses, see Licensing .

g The feature code for this feature is 3414.

To set the feature state to ON, use the following command:

• for IPA-RNC:ZW7M: FEA=3414:ON;

Before activating this feature configure the following database objects and relevantparameters 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 notmandatory 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 LTEand 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.

4 Expand the RNC object.

5 Expand the WBTS object.

6 Configure the WCEL object:a) Select Edit Parameters from the WCEL object.

b) Activate the RAN2264: Smart LTE Handover feature with theLTEHandoverEnabled 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 (2) = T1 and T2 enabled• value (3) = T1 and T3 enabled• value (4) = T1, T2, and T3 enabled• value (5) = T1 and T4 enabled• value (6) = T1, T2, and T4 enabled• value (7) = T1, T3, and T4 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 theRAN1668: 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 LTEmeasurements for handover.

For instructions on how to activate and configure DCH/DCH compressed mode (CM) andHSDPA/DCH CM for LTE handover, see Activating RAN2980: Measurement Based LTELayering . For information on how to activate and configure HSPA CM for LTE handover,see Activating RAN1668 HSUPA Compressed Mode for LTE and Inter-frequencyHandover .

The minimum required RSRP ( AdjLMinRSRPLevel ) and RSRQ ( AdjLMinRSRQLevel )levels of the cell under LTE carrier frequency should be aligned with the correspondingthresholds in the LTE network.

Ensure that the UE is not redirected or handed over from WCDMA to LTE with the RSRPor 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 – 115dBm, then the recommended minimum RSRP threshold for the WCDMA to LTEhandover is – 112 dBm (3 dB hysteresis) in order to avoid immediate handover back toWCDMA. Correspondingly, if the quality (RSRQ)-based handover from LTE to WCDMAis 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

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

The functioning of the RAN2264: Smart LTE Handover feature can be verified with thefollowing 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 successcounters.

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

Follow this procedure to deactivate this feature.

g The RAN2264: Smart LTE Handover feature is deactivated on cell basis.


Issue: 01 DN09146788 91



1 Open the O MS Element Manager.

2 Go to Topology.

3 Expand the ROOT.

4 Expand the RNC object.

5 Expand the WBTS object.

6 Configure the WCEL object:a) Select Edit Parameters from the WCEL object.

b) Deactivate the RAN2264: Smart LTE Handover feature with theLTEHandoverEnabled parameter.

2.9 RAN2881: WCDMA and GSM Layer Priorities

2.9.1 Description of RAN2881: WCDMA and GSM Layer Priorities

Introduction to the featureThe RAN2881: WCDMA and GSM Layer Priorities feature allows idle mode trafficsteering 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 thebest possible layer for the end-user. Operator controls the priorities of the layers.





92 DN09146788 Issue: 01




RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi DirectRNC

OMS

Flexi BTS

RU50 Not planned RN8.0 Planned for later releases

Not planned OMS3.0(RU50)

Supportnotrequired

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE

Support notrequired

Support notrequired

NetAct 8EP1

Support notrequired

Support notrequired

Support notrequired

3GPPRel-8


This feature does not require any new or additional hardware.


Functional overview

The RAN2881: WCDMA and GSM Layer Priorities feature enables WCDMA and GSMcell 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 whenthe UE is in idle mode, Cell_PCH, or URA_PCH state. Also lower and equal prioritylayers are measured by UE, if radio conditions in the camped frequency fall belowcriteria defined with search thresholds.

Based on results of these measurements, UE performs priority-based cell reselectionusing both coverage and quality thresholds broadcast in SIB19. For WCDMA and GSMpriority-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 areprovided for cell reselection. Frequency band prioritization can be adjusted withthresholds, 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 celledge UEs prefer low priority layer as they are below the threshold. Figure 4: WCDMAand GSM cell reselection based on layer priorities shows the mechanism of cellreselection. 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

There are no commands related to this feature.


This feature has no impact on network management or network element managementtools.


This feature has no impact on system performance or capacity.

2.9.1.5 RAN2881: WCDMA and GSM Layer Priorities management data

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

Alarms







94 DN09146788 Issue: 01



Parameters

Table 53: New parameters lists parameters introduced with this feature and thecorresponding SIB19 parameters specified in 3GPP Rel-8.


Full name

Abbreviated name

SIB19 IE

Managedobject

WCDMA Cell Reselection WCDMACellReselection N/A WCEL

GSM Cell Reselection GSMCellReselection N/A WCEL

Absolute priority for inter-frequency cell

reselection

AdjiAbsPrioCellReselec priority HOPI

Threshold high for inter-frequency cellreselection

AdjiThreshigh Threshx,high HOPI

Threshold low for inter-frequency cellreselection

AdjiThreslow Threshx,low HOPI

QqualminFDD for inter-frequency cellreselection

AdjiQqualminFDD QqualminFDD HOPI

QrxlevminFDD for inter-frequency cellreselection

AdjiQrxlevminFDD QrxlevminFDD HOPI

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 servi ng 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 thecorresponding SIB19 parameters specified in 3GPP Rel-8.


Issue: 01 DN09146788 95




Full name

Abbreviated name

SIB19 IE

Managedobject

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 ChannelNumber

AdjiUARFCN UARFCN ADJI

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 Block19

SIB19CompmaskInfo N/A WCEL

Block 19 Compmask 1 SIB19Compmask1 N/A WCEL




Table 55: Related existing parameters lists existing parameters related to this featureand the corresponding SIB19 parameters specified in 3GPP Rel-8.

Table 55 Related existing parameters

Full name

Abbreviated name

SIB19 IE

Managedobject

BCCH ARFCN AdjgBCCH GSM cell group List /Starting ARFCN

ADJG


96 DN09146788 Issue: 01



Table 55 Related existing parameters (Cont.)

Full name

Abbreviated name

SIB19 IE

Managedobject

GSM cell group List / Listof ARFCNs

Band Indicator AdjgBandIndicator GSM cell group List /Band Indicator

ADJG



BSW/ASW

SW component


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

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 anytime of the day.

Activate the license of the RAN2881: WCDMA and GSM Layer Priorities feature usingWCDMA and GSM Layer Priorities license key.

To set the feature state to ON, use the following command:

• 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 priorityinfo list/UTRA Serving Cell IE)

• AdjiAbsPrioCellReselec HOPI parameter, introduced with the RAN2881:WCDMA and GSM Layer Priorities feature, defines the WCDMA inter-frequencypriority (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 priorityinfo list/GSM Priority Info IE)

• AdjLAbsPrioCellReselec HOPL parameter, introduced with the RAN2067: LTE Interworking feature , defines the LTE priority (E-UTRA frequency and priority infolist/E-UTRA frequency and priority IE)

g Priority-based cell reselection between WCDMA and LTE radio technologies isprovided by the RAN2067: LTE Interworking feature. TheRAN3069: RSRQ-based LTE Reselection feature is an extension to theRAN2067: LTE Interworking feature and provides quality thresholds for LTEpriority-based cell reselection.

RtHopiIdentifier (RT HOPI Identifier) ADJI parameter is used for definingparameter set for WCDMA inter-frequency absolute priority cell reselection.RtHopgIdentifier (RT HOPG Identifier) ADJG parameter is used for definingparameter set for GSM absolute priority cell reselection.

WCDMA priority is broadcast per UARFCN in SIB19 message. The same priority valueshould be given for each inter-frequency WCDMA neighbor. If more than one value isgiven, the highest priority is broadcast in SIB19 message. Correspondingly, GSM priorityis 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 GSMneighbor within the same frequency. If more than one value is given, the highest priorityis broadcast in SIB19 message.

g Before enabling the GSMCellReselection WCEL parameter in the cell, makesure 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 notconsidered for reselection. Default value of AdjgAbsPrioCellReselecparameter means that GSM priority is not defined.






b) In System Info tab, set the values of WCDMACellReselection andGSMCellReselection 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 isused.


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 featureworks properly in the network.

Before you start

g There are no counters involved in cell reselection process. UE reselects the cellaccording to the parameters broadcast by the network in SIB19 message.

When the RAN2881: WCDMA and GSM Layer Priorities feature is active, it is visible inthe content of SIB19 message. After activating this feature and ascribing values to theparameters listed in RAN2881: WCDMA and GSM Layer Priorities management datasection, 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 protocolanalyzer.

Further information

Camping on a desired layer is perfomed by UE using SIB19 parameters. Cell reselectionalgorithm is specified in 3GPP TS 25.304 User Equipment (UE) procedures in idle modeand 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 Prioritiesfeature.






b) In System Info tab, set the values of WCDMACellReselection andGSMCellReselection parameter to Disabled.


Issue: 01 DN09146788 99



3 Transmission and transport features

3.1 RAN2243: Performance Monitoring Based on ETHService OAM

3.1.1 Description of RAN2243: Performance Monitoring Basedon ETH Service OAM


This feature enhances the RAN1880: Ethernet OAM in BTS feature to provideperformance monitoring functionality using Ethernet Service OAM frames.

Performance monitoring according to the ITU-T Y.1731 provides Ethernet performancemeasurement between Maintenance End Points (MEPs) that are placed at the edges of each maintenance domain. The performance monitoring feature supports the FrameLoss and Frame Delay Measurements. The Frame Delay Measurements are showedwith maximum, minimum and average values of the measurement period of fifteenminutes 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 benefitsThis feature provides the maintenance hierarchy structure where the performancemeasurements are performed between the MEPs of the same grade of hierarchy.Different grades of hierarchy monitor different Ethernet network segments to find theproblems 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 notrequired

Support notrequired

Not planned OMS3.0(RU50)

WN9.0

Transmission and transport features RU50 Feature Descriptions and Instructions

100 DN09146788 Issue: 01




Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE

Plannedfor later releases

Plannedfor later releases

NetAct 8 EP1(RU50)

Support notrequired

Support notrequired

Support notrequired

Support notrequired


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 provideperformance monitoring (PM) functionality using Ethernet Service OAM frames. TheEthernet 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 conformsmaintenance 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). Themaintenance hierarchy allows to monitor different segments of the Ethernet network,which are under the responsibility of different hierarchy departments. The segmentationof 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.

RU50 Feature Descriptions and Instructions Transmission and transport features

Issue: 01 DN09146788 101



Figure 5 Performance monitoring using Ethernet Service OAM frames

Eth Ethernet Ethernet

BTS

MEP MEP MEP MEP

Eth PM

Eth PM

Eth PM

The performance monitoring functions supported by the performance monitoring featureare Frame Loss and Frame Delay Measurement. There are different modes of eachmeasurement. 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 LossMeasurement and Frame Delay/Delay Variation Measurement. Thresholds areconfigurable per measurement session.

The Frame Loss Measurements are obtained by means of counters for received andtransmitted data frames between a pair of MEPs. These counters are provided by theperformance monitoring feature. The Frame Loss Measurement can be calculated for each direction. Far-end and near-end Frame Loss Measurements are supported. TheBTS 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-pointEthernet connections between MEPs to perform accurate Frame LossMeasurement, whereas there are no similar conditions for Frame Delay/DelayVariation 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:

• RAN1880: Ethernet OAM in BTS


This feature has no impact on interfaces.


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 whenpro-active functions (ETH-CC) are activated simultaneously and using hightransmission rates. However, the Service OAM performance monitoring functions arenot 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 lessthan 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 canconsume 312 kbps at Ethernet layer when 3.33 ms interval is configured.

3.1.1.5 RAN2243: Performance Monitoring Based on ETH Service OAMmanagement 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 thresholdexceeded on mac $m

7665 BASE STATION TRANSMISSION ALARM

61636 Two way delaythreshold exceeded onmac $m


61637 OneWay delay variationthreshold exceed onmac $m


g The performance monitoring faults are presented as alarms at:

• OMS Fault Management• NetAct Monitor


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

Table 59 New counters

Counter ID

Counter name

Measurement

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





ParametersTable 60: New parameters lists parameters introduced with this feature.


Full name

Abbreviated name

Managed object

Enable service OAM performancemonitoring

enableSoamPm IPNO

Flag for enabling/disabling SOAMframe loss measurement enableSoamFrameLossMeas OAMFLM

MAC address of the frame lossmeasurement remote MEP

macAddr OAMFLM

Service OAM frame loss alarmthreshold

soamFrameLossAlarmThres OAMFLM

Service OAM frame lossmeasurement interval

soamFrameLossMeasInt OAMFLM

Service OAM Frame loss

Measurement Mode

soamFrameLossMeasMode OAMFLM

Enable service OAM delaymeasurement

enableSoamDelayMeasure OAMDM

MAC address of the delaymeasurement remote MEP

macAddr OAMDM

Service OAM oneway delayvariation 15m alarm threshold

soamDelayAlarmThresOneway OAMDM

Service OAM two-way delay 1 minalarm threshold

soamDelayAlarmThresTwoway OAMDM

Service oam delay measurementPDU length

soamDmmPduSize OAMDM

Service OAM frame delaymeasurement interval

soamFrameDelayMeasInt OAMDM

Commands



Issue: 01 DN09146788 105





BSW/ASW

SW component


ASW RAN TRS LK

3.1.2 Activating RAN2243: Performance Monitoring Based onETH 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:• RAN1880: Ethernet OAM in BTS

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:

• RNW Measurement Management• NetAct Administration of Measurements

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

• BTS Site Manager • 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 notoperable.

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

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

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




108 DN09146788 Issue: 01



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


a) Open the TRS Hardware from the View bar .b) Open the Ethernet Service OAM menu.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


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:

• NetAct Performance Manager

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

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



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


a) Open the TRS Hardware from the View bar .

b) Open the Ethernet Service OAM menu.


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


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





Expected outcome

The Soam One Way Delay Variation Statistics measurement has been started atOMS.









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 ETHService 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:

• BTS Site Manager • NetAct Performance Manager

The verifying procedure to monitor the PM alarms needs:

• BTS Site Manager • NetAct Monitor • OMS Fault Management

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

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:

• BTS Site Manager

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

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 • OMS Fault Management

Further information

The proper alarms are canceled when the thresholds are not reached after the nextone 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 lostframes.

The Frame Delay counters must be always greater than zero at the presentmoment.

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

• BTS Site Manager

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

The proper PM counters are updated after the completion of fifteen minutesmeasurement.

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• Frame Loss 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 • OMS Fault Management

Further information

The proper alarms are canceled when the thresholds are not reached after the nextfifteen minutes measurement for:

• One-way Frame Delay Variation Measurement• Frame Loss 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 onETH 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 dea ctivate 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.



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


a) Open the TRS Hardware from the View bar .b) Open the Ethernet Service OAM menu.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 theBTS 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 theBTS.

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.• The Ethernet Service OAM PM has been deactivated.• The Ethernet Service OAM has been deactivated.


118 DN09146788 Issue: 01





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


a) Open the TRS Hardware from the View bar .b) Open the Ethernet Service OAM menu.c) Perform one of the actions:

• Unmark on the Frame loss measurement in use checkbox.

• Delete the selected measurement session using Delete button.


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

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.• The Ethernet Service OAM PM has been deactivated.• The Ethernet Service OAM has been deactivated.



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


a) Open the TRS Hardware from the View bar .b) Open the Ethernet Service OAM menu.c) Perform one of the actions:

• Unmark on the Delay measurement in use checkbox.• Delete the selected measurement session using Delete button.


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.

g This step must be performed using:• RNW Measurement Management• NetAct Administration of Measurements

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



Expected outcome

The Soam One Way Delay Variation Statistics measurement has been stopped atOMS.

The OMS stops sending the One-way Frame Delay Variation Measurement data tothe NetAct.


Issue: 01 DN09146788 121



4 Operability features

4.1 RAN2199: BTS Event Triggered Symptom DataCollection

4.1.1 Description of RAN2199: BTS Event Triggered SymptomData Collection


This feature introduces automatic fault-triggered BTS symptom data collection. Thetriggering BTS faults are defined in the Site Configuration File (SCF) using the NetActConfigurator.

4.1.1.1 Benefits

End-user benefits


Operator benefits

This feature benefits the operator as follows:

• 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 accurateand thus more efficient in solving failures.



Software requirements lists the software required for this feature.

RAS

Flexi Direct

IPA-RNC

mcRNC

Flexi DirectRNC

OMS

Flexi BTS

RU50 Not planned RN8.0 Planned for later releases

Not planned OMS3.0 WN9.0

Flexi LiteBTS

Flexi 10BTS

NetAct

MSC

SGSN

MGW

UE



Support notrequired

Support notrequired

Support notrequired

Support notrequired

Support notrequired

Operability features RU50 Feature Descriptions and Instructions

122 DN09146788 Issue: 01




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 faults2. Data collection after the selected faults occur 3. Data transfer and storage4. 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 recommendedtriggers. The list of faults is defined with the symptomDataTriggerL parameter.

g The list of BTS faults is available in the Flexi Multiradio BTS WCDMA Faultsdocument. The TRS faults (IDs within range 61000-61999) are not consideredas 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

RU50 Feature Descriptions and Instructions Operability features

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 OMSimmediately after the data has been collected. The OMS is able to perform simultaneousuploads from several BTSs. The existing file transfer mechanism through the BTSOMinterface is used to transfer the data to OMS. If the triggering fault leads to a recoveryreset 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 commonway: 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 logfile has been transferred to OMS. The dwAlarmForUploadCompletedparameter is used for disabling/enabling the alarm setting in OMS.

The 71129 TROUBLESHOOTING DATA CREATION OR UPLOAD FAILEDindicates that the data creation or upload to OMS has failed.

Old symptom data files are deleted automatically from the BTS (after being transferred toOMS). When the clean up procedure starts in the OMS, the OMS deletes files older thancertain number of days (defined with the dwNELogDaysSpan parameter). By default,files older than 10 days are removed. Additionally, the OMS monitors the disk space useand if needed, performs additional clean up procedure.

With the dwBTSUploadEnabled parameter, the automatic data transfer to OMS can beenabled/disabled.

Viewing the collected data

The files can be viewed using the Log Viewer in the OMS Element Manager. The LogViewer 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 webbrowser cookie (if any is stored). When the user sets new value in this component, thisnew value is preserved within the same session and also restored next time when theuser logs in t o OMS Element Manager (web browser cookie mechanism is used topreserve the value set by the user).

The troubleshooting data files can also be downloaded to the client's computer using theLog 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 systemand 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 Collectionmanagement 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

Measurements and cou nters




ParametersTable New parameters lists parameters introduced with this feature.


Full name

Abbreviated name

Managed object

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 followingcommand: fshascli -rn /TomcatPlat

Table 65: Related existing OMS LDAP parameters lists existing parameters related tothis feature.

Table 65 Related existing OMS LDAP parameters

Attribute

ClusterRoot/OMS/OMSPlatform/SS_NELogManager/NELogManager/dwAlarmForUploadCompleted

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/ASW

SW component


BSW RAN -

4.1.2 Activating RAN2199: BTS Event Triggered Symptom DataCollection

Purpose

Follow this procedure to activate the RAN2199: BTS Event Triggered Symptom DataCollection feature. For more information on the feature, see the RAN2199: BTS Event Triggered Symptom Data Collection feature description in RU50 Feature Descriptionsand 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. Bydefault the functionality is turned on.

The actual symptom data collection takes place if any triggering faults have been definedduring the BTS commissioning. The list of faults is defined using the Symptom datatrigger list (symptomDataTriggerL) parameter under the MRBTS object.

Restart of the RNC, OMS or BTS is not required after the activation of this feature. Thisprocedure 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 ApplicationLauncher 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 CollectionPurpose

Follow this procedure to deactivate the RAN2199: BTS Event Triggered Symptom DataCollection feature. For more information on the feature, see the RAN2199: BTS Event Triggered Symptom Data Collection feature description in RU50 Feature Descriptionsand 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 theday.

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 ApplicationLauncher 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 managementnetwork, self healing measures are taken. This applies for failures during normaloperation after a configuration-update.

4.2.1.1 Benefits

End-user benefits

This feature does not affect the end-user experience.Operator benefits

This feature benefits the operator as follows:

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


Software requirementsTable 67: Software requirements lists the software that is required for this feature.

RAS

Flexi Direct

IPA-RNC

mcRNC

OMS

BTS Flexi

Flexi Lite


Support notrequired

Support notrequired

WN9.0 Planned for later releases


BTS Flexi 10

NetAct

MSC

SGSN

MGW

UE


Support notrequired

Support notrequired

Support notrequired

Support notrequired

Support notrequired



• RAN2382: Flexi BTS Multimode System Module - FSMC• RAN1016: Flexi BTS Multimode System Module - FSMD


Issue: 01 DN09146788 129



• RAN1848: Flexi BTS Multimode System Module - FSME


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 remoteconfiguration update and activation. If the M-plane can be established with the oldconfiguration, a notification is sent to the Network Management System indicating thatthe new configuration was not activated. If the old one fails as well, the received new oneis 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 TNLconfiguration 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 commandsThere are no commands related to this feature.


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



4.2.1.5 RAN2554: Transport Configuration Fallback management data

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

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. Meaningof new fault: the base station has recovered the M-plane connection byfalling back to the old transport configuration after the configuration change

Parameters

Table 69 New parameter

Full name

Abbreviated name

Managed object

Enable transport configuration fallback enableTransportConfigFallback

IPNO



BSW/ASW

SW component


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 NetActCM 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 BTSSite 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 fileand 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 NetActCM 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 thencorresponding 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 to10.82.1.1 which is unreachable.

g It is also feasible to modify TNL parameters by recommisionning the WBTSvia 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 isdisconnected to the unreachable RNC.


Issue: 01 DN09146788 133



3 Connect to the WBTS locally, and monitor the O&M status of the WBTS.

ResultRNC IP has been modified to new target IP on WBTS IP configuration, and WBTSOAM 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 connectionattempts, the WBTS falls back to the original RNC. Then DCNLinkStatus withoriginal 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'sconnection to the original RNC is established.

g An alarm is issued indicating that the planned configuration changes are notused in the WBTS --- 7665 BASE STATION TRANSMISSION ALARM ispresent.


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 tothe new target RNC.

g The configuration change is a corrective configuration change for an earlier recovery ending in the fallback operation. The alarm7665 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 to10.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 isdisconnected 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 connectionattempts, 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 connectionattempts, 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 theoriginal 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 beable 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, theRNC IP address should be the new target RNC. No RAN2554 alarm would bepresent 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 tothe 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. Thefeature can be activated using BTS Site Manager or NetAct CM Editor.

Before you startMake sure that RAN2554: Transport Configuration Fallback feature is already activated.

4.2.5.1 Deactivating RAN2554: Transport Configuration Fallback using BTSSite 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 fromNetAct 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



5 RNC solution features

5.1 RAN3047: RTT Improvement to Enhance User Experience

5.1.1 Description of RAN3047: RTT Improvement to enhanceuser 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 backgroundtraffic.




RAS Flexi Direct IPA-RNC mcRNC Flexi DirectRNC

OMS Flexi BTS

RU50 Planned for later releases

RN8.0 Planned for later releases


OMS3.0(RU50)

Supportnotrequired


Flexi LiteBTS

Flexi 10BTS

NetAct MSC SGSN MGW UE

Support notrequired

Support notrequired

NetAct 8EP1

Support notrequired

Support notrequired

Support notrequired

3GPPRel-8


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 32Byte Ping to be comparable with LTE delay.

RU50 Feature Descriptions and Instructions RNC solution features

Issue: 01 DN09146788 137



Improvement in Round Trip Time (RTT) is achieved by reducing the delay components inthe data path between the network and UE. The feature focus to reduce RNC Delay inHS(D)PA Downlink data path by using data arrival event to schedule data towards BTSin Iub.

The data event trigger enables reduction of RTT, which further improves the responsetimes for interactive services and faster data transfer for background traffic, therebyenhancing the user experience.



This feature has no feature interdependencies.



Impact on commands






5.1.1.5 RAN3047: RTT Improvement to enhance user experiencemanagement data


Alarms


Measurements and countersThere 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.

RNC solution features RU50 Feature Descriptions and Instructions

138 DN09146788 Issue: 01





BSW/ASW

SW component


BSW RAN RNC LK

RU50 Feature Descriptions and Instructions RNC solution features

Issue: 01 DN09146788 139



6 BTS solution features

6.1 RAN3017: Additional 6 WCDMA Cell Activation

6.1.1 Description of RAN3017: Additional 6 WCDMA CellActivation


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 RU50the number of c ells can be up to 18.

6.1.1.1 BenefitsEnd-user benefits


Operator benefits

Increasing traffic, demand for multicarrier, multiband, and multi-sector sites leadsoperator needs towards larger BTS site configurations, especially in hot spot areas. Thisfeature enables to build such configurations with simple SW configuration.





RAS Flexi Direct IPA-RNC mcRNC Flexi DirectRNC

OMS Flexi BTS


Support notrequired

Not planned Support notrequired

WN9.0

Flexi LiteBTS Flexi 10BTS NetAct MSC SGSN MGW UE

Not relevant WN9.1 NetAct 8EP1(RU50)

Support notrequired

Support notrequired

Support notrequired

Support notrequired



• RAN2382: Flexi BTS Multimode System Module - FSMC • RAN1016: Flexi BTS Multimode System Module - FSMD

• RAN1848: Flexi BTS Multimode System Module - FSME

BTS solution features RU50 Feature Descriptions and Instructions

140 DN09146788 Issue: 01



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 activateadditional 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 siteconfiguration has more than 12 cells. RAN3017: Additional 6 WCDMA Cell Activationreplaces the existing solution.






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




RU50 Feature Descriptions and Instructions BTS solution features

Issue: 01 DN09146788 141





ParametersTable 75: Modified parameters lists parameters modified by this feature.


Full name Abbreviated name Managed object

Extended BTS site capacityenabled

extendedBtsSiteCapacity BTSSCW



BSW/ASW SW component License control in networkelement

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 validlicense file. The feature code is 0000005171. SeeWCDMA RAN License Operation document for details.

1 Start the WCDMA BTS Site Manager application and establish the connectionto 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 IfRAN2131: Automatic Licence Distribution to Flexi BTS is not activated,relevant license must be uploaded manually.

2 Upload the configuration plan file from the BTS.

When BTS Site Manager is connected to the BTS, it automatically uploads thecurrent configuration plan file from the BTS.

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


142 DN09146788 Issue: 01



3 Activate RAN3017: Additional 6 WCDMA Cell Activation feature.

Go to Local Cell Resources page and select the Extended BTS site capacityenabled 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 filedownload.

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 WCDMACell Activation feature has been successful.

RU50 Feature Descriptions and Instructions BTS solution features

Issue: 01 DN09146788 143



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

2 Upload the configuration plan file from the BTS.

When BTS Site Manager is connected to the BTS, it automatically uploads thecurrent configuration plan file from the BTS.

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

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 CellActivation

Purpose

To deactivate RAN3017: Additional 6 WCDMA Cell Activation feature, follow thisprocedure.

Before you start

1 S BTS Si M li i d bli h h i h BTS


29 Nokia-RU50 Feature Descriptions and Instructions

Documents