FN 159393 Configurable VSWR Alarm Threshold

FN 159393 Configurable VSWR Alarm Threshold

Document number: UMT/BTS/DD/037782 Document issue: 01.05/ EN Document status: Standard Date: November 15, 2012

Alcatel-Lucent - Internal - Proprietary - Use pursuant to Company instruction

Copyright 2011 Alcatel-Lucent, All Rights Reserved

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write

protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended.

Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be

regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-

Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information

contained herein confidential, shall disclose the information only to its employees with a need to know, and

shall protect the information from disclosure and dissemination to third parties. Except as expressly

authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained

herein. If you have received this document in error, please notify the sender and destroy it immediately.

without notice. Networks assumes no responsibility for errors that might appear in t.All other brand and



UMT/BTS/DD/037782 01.05/ EN Standard November 15, 2012 /24

PUBLICATION HISTORY

01/June/2012

Issue 01.01 / EN, Draft

Initial Draft for review

Brijesh Unnikrishnan

19/June/2012

Issue 01.02 / EN, Preliminary

Review comments incorporated. A new message is introduced to carry the VSWR

threshold parameters from CCM OAM to REPROXY. (Instead of Sector

Config/Reconfig message)


22/August/2012


Making Requirement R2.1 compliant for iBTS


15/November/2012


Adding semantics checks at WMS





CONTENTS

1 INTRODUCTION ..................................................................................................................................... 6

1.1 OBJECT ............................................................................................................................................ 6

1.2 FRS ................................................................................................................................................. 6

1.3 SCOPE OF THIS DOCUMENT .................................................................................................................... 6

1.4 AUDIENCE FOR THIS DOCUMENT ............................................................................................................. 6

2 RELATED DOCUMENTS.......................................................................................................................... 7

2.1 APPLICABLE DOCUMENTS ...................................................................................................................... 7

2.2 REFERENCE DOCUMENTS ....................................................................................................................... 7

3 FUNCTION OVERVIEW........................................................................................................................... 8

3.1 FEATURE OVERVIEW ............................................................................................................................ 8

3.2 COMPLIANCE MATRIX ........................................................................................................................... 8

4 FUNCTIONAL DESCRIPTION ................................................................................................................11

4.1 PRINCIPLE .......................................................................................................................................12

4.2 BTS SUPPORTED CONFIGURATIONS .......................................................................................................12

4.3 ASSUMPTIONS AND RESTRICTIONS ..........................................................................................................12

4.4 FUNCTIONALITY DISTRIBUTION ...........................................................................................................12

4.4.1 Configuring VSWR Thresholds .............................................................................................12

4.4.1.1 Feature Activation/Deactivation ........................................................... 12

4.4.1.1.1 CCM OAM ..................................................................................... 15

4.4.1.1.1 REPROXY ..................................................................................... 15

4.4.1.1.2 CCM CallP .................................................................................... 15

4.4.1.1.3 Layer 1/2 .................................................................................... 15

4.4.1.1.4 RRH/TRDU ................................................................................... 15

4.4.1.1.5 FPGA .......................................................................................... 16

4.4.1.1.6 Loader ........................................................................................ 16

4.4.1.1.7 Platform Software .......................................................................... 16

4.4.1.1.8 Hardware .................................................................................... 16

4.4.1.2 BTS Startup ..................................................................................... 16

4.4.1.2.1 CCM OAM ..................................................................................... 17

4.4.1.2.2 REPROXY ..................................................................................... 17

4.4.1.2.3 CCM CallP .................................................................................... 17

4.4.1.2.4 Layer 1 / 2 ................................................................................... 17

4.4.1.2.5 RRH/TRDU ................................................................................... 17

4.4.1.2.6 FPGA .......................................................................................... 17

4.4.1.2.7 Loader ........................................................................................ 17


4.4.1.2.9 Hardware .................................................................................... 17

4.4.1.3 RRH Plugin ...................................................................................... 18

4.4.1.4 Display the threshold values at TIL ......................................................... 18

4.4.1.4.1 CCM OAM ..................................................................................... 18

4.4.1.4.2 CCM CallP .................................................................................... 18




4.4.1.4.3 Layer 1 / 2 ................................................................................... 18

4.4.1.4.4 RRH/TRDU ................................................................................... 18

4.4.1.4.5 FPGA .......................................................................................... 18

4.4.1.4.6 Loader ........................................................................................ 18


4.4.1.4.8 Hardware .................................................................................... 18

4.5 FEATURE INTERWORKING ....................................................................................................................19

4.6 PERFORMANCE OBJECTIVES AND IMPACTS...............................................................................................19

4.6.1 System performances .........................................................................................................19

4.6.2 Dimensioning .......................................................................................................................19

4.6.3 Capacity ..............................................................................................................................19

4.6.4 Dependability ......................................................................................................................19

4.7 SECURITY ........................................................................................................................................19

5 INTERFACES ........................................................................................................................................19

5.1 UMTS INTERFACES ............................................................................................................................19

5.2 INTERNAL IBTS INTERFACES ................................................................................................................20

5.2.1 CCM OAM – REPROXY ...........................................................................................................20

5.3 EXTERNAL OAM INTERFACES ...............................................................................................................20

6 OAM .....................................................................................................................................................20

6.1 CONFIGURATION MANAGEMENT............................................................................................................20

6.1.1 RAN Objects ........................................................................................................................20

6.1.2 RAN Parameters ..................................................................................................................20

6.1.3 Semantic check ...................................................................................................................22

6.2 FAULT MANAGEMENT .........................................................................................................................22

6.2.1 Alarms .................................................................................................................................22

6.2.2 State Changes .....................................................................................................................22

6.3 PERFORMANCE MANAGEMENT...............................................................................................................22

6.3.1 Counters ..............................................................................................................................22

6.3.2 Traces .................................................................................................................................22

6.4 I&C ...............................................................................................................................................22

6.5 MISCELLANEOUS ...............................................................................................................................22

7 O&M PROCEDURES ..............................................................................................................................23

7.1 WCDMA IBTS UPGRADE ....................................................................................................................23

7.2 BENIGNESS, BACKWARD COMPATIBILITY ................................................................................................23

7.3 INSTALLATION AND COMMISSIONING ......................................................................................................23

8 FIELD INTRODUCTION ........................................................................................................................23

8.1 HARDWARE CONSTRAINTS ...................................................................................................................23

8.2 MS INTERWORKING............................................................................................................................23

9 TOOLS IMPACTS ..................................................................................................................................23

9.1 TIL IMPACTS ....................................................................................................................................23




9.2 OTHER TOOLS ..................................................................................................................................23

10 OPEN POINTS ....................................................................................................................................24

11 ABBREVIATIONS AND DEFINITIONS ..................................................................................................24

11.1 ABBREVIATIONS ..............................................................................................................................24

11.2 DEFINITIONS ..................................................................................................................................24




1 INTRODUCTION

1.1 OBJECT

This document is the functional specification for the feature ‘159393 Configurable

VSWR Alarm Threshold’ for UA9.1 release.

1.2 FRS

FSD – 159393 Configurable VSWR Alarm Threshold- version 1.06

1.3 SCOPE OF THIS DOCUMENT

The scope of this document is to describe the iBTS impacts for this feature that is

introduced in UA9.1 release.

1.4 AUDIENCE FOR THIS DOCUMENT

This document is intended for iBTS development and integration teams as well as system architecture, system integration, engineering, PLM teams and GPS.




2 RELATED DOCUMENTS

2.1 APPLICABLE DOCUMENTS

[A1] FSD – 159393 Configurable VSWR Alarm Threshold - http://mtsweb.fr.alcatel-lucent.com:8080/dolphins/web_kiosk_link.php?search=k&key=UMT/SYS/APR/036949/01/

2.2 REFERENCE DOCUMENTS

[R1] SII CCM OAM - TRM for Ua8.1 - UMT/BTS/DD/026637




3 FUNCTION OVERVIEW

3.1 FEATURE OVERVIEW

This feature provides an option to configure the two VSWR alarm thresholds based

on the implementation needs. VSWR readings provide information on the return loss

of the antenna system.

Currently ALU provides two fixed values for the VSWR alarms in distributed NodeB

systems as defined in ARD-0546. These values cannot be modified by application and

are set at the following levels:

• Level 2 indicates the return loss of 9 dB, i.e. VSWR 2.1:1; this requires onsite maintenance by operator.

• Level 3 indicates the return loss of 6 dB, i.e. VSWR 3.01:1; the PA will shutdown in case this level is reached as the intent is to protect the PA from not being damaged by the high returned signal level.

With WCDMA deep coverage rollout, there is variant path loss due to the fact that

antenna is situated at variant distance from NodeB. Hence there is a need to have

more sensitive threshold for VSWR alarms.

This feature shall allow configuration of the two threshold values as follows:

• Level 2: Configurable from 1.43:1 to 2.32:1 (i.e from 8 to 15 dB, Step 1dB RL), default 9dB.

• Level 3: Configurable from 1.58:1 to 3.01:1 (i.e from 6 to 13 dB, Step 1dB RL), default 6dB.

As part of the feature a cleanup of existing parameters (rxVswrPeriodicity & rxVswrThreshold) of rx VSWR are done from RAN Model.

3.2 COMPLIANCE MATRIX

Req. # General Requirements R&D Response

R1 Applicable products:

9326 and 9926 d2U V2, 4U and ibts+xcob, and all future evolutions; All Radio Units (RU) which already support 3 2 levels VSWR alarm threshold in hardware and software. (RRH40-21, RRH60-21A, RRH60-21C, TRUD60-21A/B, RRH2x60-21 (This list is just as an example and might not be complete); � both CPRI protocol shall be covered, over RMM or

ARD546. �

Note: Priorities for RUs to be supported (PLM have confirmation that they are all configurable by SW now):

Compliant




P1 RRH60-21C (ASB) P2 TRDU60-21A/B (ASB) P3 RRH40-21 (ST) P4 TRDU40-21 (Andrew) P5 RRH60-21A (GPCS) P6 RRH2x60-21A

� P7 TRDU60-21 (GPCS)

R2 D2U will notify each RU with 2 levels of VSWR alarms:

� Level 2: shall be configurable as Return Loss (RL): range [8, 15], step 1dB; default 9 dB (VSWR 2.1)

� Level 3: shall be configurable RL [6, 13]dB, default 6dB (VSWR 3.01)

Compliant

R2.1 � The Level 2 value shall be at least 2dB (3dB?) greater

than Level 3; Compliant

R3 A GUI will have to be provided in TIL (read only) within WMS (read-write) and WIPS (read-write), supporting the following format:

� RL x.0dB (VSWR x.xx) � For example: RL 14.0dB (VSWR 1.50) �

WMS GUI and WPS shall allow the operator to enter the required Return Loss in dB as a text entry field, for both Level 2 and Level 3 thresholds. The decimal value shall be shown as non-editable “.0 dB” to indicate that only integer values are allowed. The corresponding VSWR value shall be indicated next to the Return Loss field. Alternatively a drop-down menu shall be provided, from which the operator can select from a list of allowed values. The drop-down list shall show both Return Loss (in dB) and VSWR (as a ratio). The two thresholds shall also be displayed (read-only) on the TIL along with all the RAN parameters.

Compliant for iBTS

The values would be part of the existing menu in TIL, which displays the entire DLU

R4 The VSWR valued shall be kept all through the site working time before next round data reloading, since the site initial installation and commissioning load up, will be no impact due to site shut down, reset, etc. site status change. [MD: not clear enough] The VSWR alarm thresholds shall be stored locally in non-volatile memory at the RU and shall not be altered except as defined by WMS and WPS. The locally stored values shall not be altered by events including:

• RU reset

• Digital unit reset

• Site power-down

• Normal installation activities

• Normal commissioning activities The vswr alarm threshold shall be an optional OAM parameter part of the NodeB data model. This value will be used to configure the RU at each initialisation of the RU. This VSRW threshold cannot be set to the RU until the Node B site is built

Compliant

R5 The GUI shall support two Required to have two levels of scope:

� TIL GUI solve the single site set/modification demand TIL GUI would




either at the initial commissioning or on site maintenance (Nice to have);

� In case of no compliance with requirent in bullet above, then at least the TIL GUI shall be able to display (RO) VSWR values which are set by WiPS;

� WPS tool (and WMS GUI correlated) solve the multiple sites set/modification demand, either on line at WMS GUI or offline from work order .

WMS and WPS GUIs will provide 2 different levels of operations:

� Single site VSWR alarm threshold set/modification

via WMS. The operator can set/modify the VSWR

alarm threshold for one specific site remotely.

� Group of sites VSWR alarm threshold

set/modification through the WIPS tool. The

operator can set/modify the VSWR alarm threshold

for one group of specific sites offline. This is useful

when the threshold is fixed for a given area or

region.

display the value as Read-Only.

R6 Parameter, rxVSWRThreshold which was introduced with 96374 for oneBTS parity shall be removed since MSNB has been cancelled and 96374 was also cancelled (model changes were made in UA7.2)

Compliant. Both rxVswrPeriodicity and rxVswrThreshold are removed.

Req. # Performance / Capacity / Reliability Requirements

R&D Response

Req. # Configuration Management and Parameter Requirements

R&D Response

R6

Req. # Counter Requirements R&D Response

Req. # Fault Management and Alarm Requirements R&D Response




Req. # Billing and Licensing Requirements R&D Response

R7 A parameter shall be available to activate the feature.

Compliant

Req. # Serviceability Requirements R&D Response

Req. # Specific Documentation Requirements R&D Response

R1 Installation manual NA

R2 Node B maintenance manual NA

R3 TIL manual NA

R4 WPS manual NA

R5 WMS manual (Node B parameter list, Node B alarm list, etc.)

NA

4 FUNCTIONAL DESCRIPTION




4.1 PRINCIPLE

The feature shall be activated/de-activated by using a class 3 activation parameter

(isVSWRThresholdConfigurable). When the feature is deactivated, the default VSWR

threshold levels would be used. The threshold values are passed by CCM OAM to REPROXY.

REPROXY would carry these parameters over ARD 0546 / RMM to the respective REs.

4.2 BTS SUPPORTED CONFIGURATIONS

This feature shall be supported for all d2U and all future evolutions. Both CPRI protocol are

supported. (RMM or ARD 0546)

4.3 ASSUMPTIONS AND RESTRICTIONS

• The RU should support the configuration of the thresholds values for level 2 and level 3

alarms.

• Not all RRH supports the configurable VSWR thresholds. It is not clear as which RRH

supports and which does not. RRH 40-21 supports and RRH 60-21c/TRDU60-21A/B

supports via CR DCTPD00835782

4.4 FUNCTIONALITY DISTRIBUTION

4.4.1 Configuring VSWR Thresholds

4.4.1.1 Feature Activation/Deactivation

The parameter ‘isVSWRThresholdConfigurable’ shall be used to activate this feature. This parameter shall be set to FALSE by default. When feature is activated the VSWR alarm threshold level 2 and 3 are taken from the two model parameters, vSWRAlarmThresholdLevel2 and vSWRAlarmThresholdLevel3. When feature is deactivated, the default values of 9 dB and 6 dB respectively are applied for level 2 and level 3 threshold.




Online Feature activation (Success):

Online Feature activation (Failure):

RE_ SetVswrThresholds Report

TxMainThreshold1 = vswrAlarmThresholdLevel2 TxMainThreshold2 = vswrAlarmThresholdLevel3

OMCB CCM OAM RE REPROXY

TGE_SET

(isVSWRThresholdConf

igurable = TRUE)

RGE_OK

Set_VSWR_Threshold_Req

RE_ SetVswrThresholds Request

Set_VSWR_Threshold_Ack

TxMainThreshold1 = vSWRAlarmThresholdLevel2 TxMainThreshold2 = vSWRAlarmThresholdLevel3

Status = Success


TGE_SET

(isVSWRThresholdConfig

urable = TRUE)

RGE_NOK



Set_VSWR_Threshold_Nack


Status = Failed





Online Feature deactivation (Success):

Online Feature deactivation (Failure):

RE_ SetVswrThresholds Report

TxMainThreshold1 = 9 dB TxMainThreshold2 = 6 dB


TGE_SET

(isVSWRThresholdConf

igurable = FALSE)

RGE_OK





Status = Success


TGE_SET

(isVSWRThresholdConfig

urable = FALSE)

RGE_NOK



Set_VSWR_Threshold_Nack


Status = Failed





The above sequence diagram is the same for online modification of the VSWR alarm threshold parameter.

4.4.1.1.1 CCM OAM

CCM OAM shall perform the check as mentioned in Requirement R2.1 (Section 3.2). If the check fails, online activation is not performed and a nack is sent to OMCB / Simulator. CCM OAM shall carry two new parameters (TxMainThreshold1 and TxMainThreshold2) which indicate the VSWR alarm threshold level 2 and 3 in the new Set_VSWR_Threshold_Req message. The values are as follows:

If isVSWRThresholdConfigurable == TRUE:

TxMainThreshold1 = vSWRAlarmThresholdLevel2 (from DLU) TxMainThreshold2 = vSWRAlarmThresholdLevel3 (from DLU)

Else If isVSWRThresholdConfigurable == FALSE:


EndIf

The new Set_VSWR_Threshold_Req message is sent on online modification of any of the three parameters below:

• isVSWRThresholdConfigurable

• vSWRAlarmThresholdLevel2

• vSWRAlarmThresholdLevel3

4.4.1.1.1 REPROXY

REPROXY should extract the values of TxMainThreshold1 and TxMainThreshold2 from the new Set_VSWR_Threshold_Req message and use the same values in RE_ SetVswrThresholds Request message towards RE. REPROXY would send Nack to CCM OAM only when the RE_ SetVswrThresholds message has failed in all REs.

4.4.1.1.2 CCM CallP

No impacts.

4.4.1.1.3 Layer 1/2

No impacts.

4.4.1.1.4 RRH/TRDU

Not all RRH supports the configurable VSWR thresholds. It is not clear as which RRH

supports and which does not. RRH 40-21 and RRH 60-21c/TRDU60-21A/B supports via CR

DCTPD00835782




4.4.1.1.5 FPGA

No impacts.

4.4.1.1.6 Loader

No impacts.

4.4.1.1.7 Platform Software

No impacts.

4.4.1.1.8 Hardware

No impacts.

4.4.1.2 BTS Startup

The following figure outlines how the VSWR alarm thresholds values are sent to RE during

BTS startup.

If isVSWRThresholdConfigurable == TRUE: TxMainThreshold1 = vSWRAlarmThresholdLevel2 TxMainThreshold2 = vSWRAlarmThresholdLevel3 If isVSWRThresholdConfigurable == FALSE: TxMainThreshold1 = 9 dB TxMainThreshold2 = 6 dB Status = Success

CCM OAM RE REPROXY




TxMainThreshold1 , TxMainThreshold2

After Sector Configuration Procedure




4.4.1.2.1 CCM OAM

CCM OAM shall perform the MIB check as mentioned in Requirement R2.1 (Section 3.2). If the check fails, MIB is set to KO. CCM OAM shall carry two new parameters (TxMainThreshold1 and TxMainThreshold2) which indicate the VSWR alarm threshold level 2 and 3 in the new Set_VSWR_Threshold_Req message. The values are as follows:





EndIf

4.4.1.2.2 REPROXY

REPROXY should extract the values of TxMainThreshold1 and TxMainThreshold2 from the new Set_VSWR_Threshold_Req message and use the same values in RE_ SetVswrThresholds Request message towards RE.

4.4.1.2.3 CCM CallP

No impacts

4.4.1.2.4 Layer 1 / 2

No impacts

4.4.1.2.5 RRH/TRDU

No impacts

4.4.1.2.6 FPGA

No impacts

4.4.1.2.7 Loader

No impacts


No impacts

4.4.1.2.9 Hardware

No impacts




4.4.1.3 RRH Plugin

Existing procedure should follow in setting the VSWR alarm thresholds. If feature is activated, the threshold values should be taken from DLU, else default values of 9dB and 6dB should be applied

4.4.1.4 Display the threshold values at TIL

TIL Applet would use the existing menu which shows the entire DLU to display the additional two VSWR alarm threshold values. These values are read-only.

4.4.1.4.1 CCM OAM

CCM OAM would store the two threshold values in the format below. This format would be used for display in TIL. “RL x.0dB (VSWR x.xx) For example: RL 14.0dB (VSWR 1.50) “ The VSWR value could be obtained from the formula below.

VSWR = (1+ (10^(RL/20))) / ((10^(RL/20))-1); RL is the value in dB from DLU

4.4.1.4.2 CCM CallP

No impacts

4.4.1.4.3 Layer 1 / 2

No impacts

4.4.1.4.4 RRH/TRDU

No impacts

4.4.1.4.5 FPGA

No impacts

4.4.1.4.6 Loader

No impacts


No impacts

4.4.1.4.8 Hardware

No impacts




4.5 FEATURE INTERWORKING

None

4.6 PERFORMANCE OBJECTIVES AND IMPACTS

4.6.1 System performances

None

4.6.2 Dimensioning

No impacts.

4.6.3 Capacity

No impacts.

4.6.4 Dependability

No impacts.

4.7 SECURITY

No impacts.

5 INTERFACES

5.1 UMTS INTERFACES

No impacts.




5.2 INTERNAL IBTS INTERFACES

5.2.1 CCM OAM – REPROXY

CCM OAM shall carry two new parameters (TxMainThreshold1 and TxMainThreshold2) which indicate the VSWR alarm threshold level 2 and 3 in a new message (Set_VSWR_Threshold_Req). The values are as follows:

0 type: SPECIFIC_REQ

1 sub-type: SET_VSWR_THRESHOLD

2..7 Generic part

8 TxMainThreshold1

9 TxMainThreshold2





EndIf The corresponding Ack and Nack message shall be defined too. (Set_VSWR_Threshold_Ack and Set_VSWR_Threshold_Nack). REPROXY shall populate the same cause value received from RE (if any) in Nack message. The cause value will be ignored by CCM OAM.

5.3 EXTERNAL OAM INTERFACES

No impacts.

6 OAM

6.1 CONFIGURATION MANAGEMENT

6.1.1 RAN Objects

No impacts.

6.1.2 RAN Parameters

New parameters:




object BTSEquipment

parameter name isVSWRThresholdConfigurable

parameter usage Customer

class 3

domain BTS

definition This parameter defines whether the VSWR (Voltage Standing Wave Ratio) alarm threshold shall be configured or not

activation parameter Yes

mandatory Yes

Range, step Boolean (TRUE/FALSE)

unit N/A

Initial values FALSE

Recommended values TRUE

new/modified/deleted

New

Upgrade rule No

object BTSEquipment

parameter name vSWRAlarmThresholdLevel2


class 3

domain BTS

definition Threshold level for VSWR (Voltage Standing Wave Ratio) Level 2 Alarm

activation parameter No

mandatory Yes

Range, step 8 – 15, Step 1

unit dB

Initial values 9

Recommended values None


New

Upgrade rule No

object BTSEquipment

parameter name vSWRAlarmThresholdLevel3


class 3

domain BTS

definition Threshold level for VSWR (Voltage Standing Wave Ratio) Level 3 Alarm

activation parameter No

mandatory No

Range, step 6 – 13, Step 1

unit dB

Initial values 6

Recommended values None


New

Upgrade rule No




Deleted parameters:

The following two parameters are removed from RAN Model:

rxVswrPeriodicity

rxVswrThreshold

6.1.3 Semantic check

WMS/WPS shall perform the check as mentioned in Requirement R2.1 (Section 3.2).

6.2 FAULT MANAGEMENT

6.2.1 Alarms

No new alarms.

6.2.2 State Changes

No impacts.

6.3 PERFORMANCE MANAGEMENT

6.3.1 Counters

No impacts.

6.3.2 Traces

No impacts.

6.4 I&C

No impacts.

6.5 MISCELLANEOUS

No impacts.




7 O&M PROCEDURES

7.1 WCDMA IBTS UPGRADE

None

7.2 BENIGNESS, BACKWARD COMPATIBILITY

There shall be no impacts to the existing functionalities of the BTS.

7.3 INSTALLATION AND COMMISSIONING

No impacts.

8 FIELD INTRODUCTION

8.1 HARDWARE CONSTRAINTS

None

8.2 MS INTERWORKING

Not applicable.

9 TOOLS IMPACTS

9.1 TIL IMPACTS

TIL will display the two new parameters defined for VSWR Alarm Threshold (Level 2 and

Level 3) as part of the existing menu which displays the entire DLU.

9.2 OTHER TOOLS

No impacts.




10 OPEN POINTS

None

11 ABBREVIATIONS AND DEFINITIONS

11.1 ABBREVIATIONS

BTS CCM CEM FN

Base Transceiver Station Core Controller Module Channel Element Module Functional Note

FRS FSD

Feature Requirements Specification Feature Specification Document

OAM Operation Administration & Maintenance RU Radio Unit (Remote) VSWR Voltage Standing Wave Ratio WMS Wireless Network Management Solution

11.2 DEFINITIONS

Class 0: the parameter cannot be modified and a new object instance must be

created or recreated with the requested value, thanks to build process or on line

creation command.

Class 2: the object instance (or the parent object instance) must be locked to

modify the parameter and the modification will be taken into account after the

object instance (or the parent object instance) has been unlocked.

Class 3: the parameter can be changed on-line without impact on the service. The

new value is taken into account either immediately or for new calls only.

Operator: the parameter is configurable from the OMC and seen by the operator

Manufacturer: the parameter is configurable from the OMC and only seen by Nortel

engineering teams

�� END OF DOCUMENT

FN 159393 Configurable VSWR Alarm Threshold

Documents

Transcript of FN 159393 Configurable VSWR Alarm Threshold