ATM Transport(RAN15.0 03)

WCDMA RAN

ATM Transport Feature ParameterDescription

Issue 03

Date 2014-09-15

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2014-09-15) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 Introduction....................................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................11.4 Differences Between Base Station Types.......................................................................................................................3

2 Overview of ATM Transport.......................................................................................................6

3 Protocol Stacks...............................................................................................................................73.1 Iub Over ATM................................................................................................................................................................73.1.1 Protocol Stack..............................................................................................................................................................73.1.2 Links on the Iub Interface............................................................................................................................................83.1.3 OM IPoA Data Configuration on the Iub Interface.....................................................................................................83.2 Iu-CS over ATM.............................................................................................................................................................93.2.1 Protocol Stack..............................................................................................................................................................93.2.2 Links on the Iu-CS Interface.....................................................................................................................................103.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8..................................................................113.3 Iu-PS over ATM...........................................................................................................................................................133.3.1 Protocol Stack............................................................................................................................................................133.3.2 Links on the Iu-PS Interface......................................................................................................................................143.3.3 IPoA Data Configuration on the Iu-PS User Plane...................................................................................................143.4 Iur over ATM................................................................................................................................................................163.4.1 Protocol Stack............................................................................................................................................................163.4.2 Links on the Iur Interface..........................................................................................................................................163.4.3 Configuration Principles for Static Relocation Routes over Iur................................................................................173.5 ATM Transport Modes.................................................................................................................................................183.5.1 UNI Mode..................................................................................................................................................................183.5.2 Fractional Mode.........................................................................................................................................................203.5.3 IMA Mode.................................................................................................................................................................233.6 Timeslot Cross Connection..........................................................................................................................................243.6.1 Principles of Timeslot Cross Connection..................................................................................................................253.6.2 Function of Timeslot Cross Connection....................................................................................................................253.7 PVC Parameters of the ATM Layer.............................................................................................................................263.7.1 VPI and VCI..............................................................................................................................................................26

WCDMA RANATM Transport Feature Parameter Description Contents


ii

3.7.2 Service Type..............................................................................................................................................................263.7.3 ATM Traffic Records................................................................................................................................................283.8 AAL5............................................................................................................................................................................303.9 AAL2 Path....................................................................................................................................................................303.9.1 AAL2 Connections and AAL2 Path..........................................................................................................................313.9.2 AAL2 Route..............................................................................................................................................................323.10 MTP3..........................................................................................................................................................................323.10.1 MTP3 Links.............................................................................................................................................................323.10.2 Types of MTP3 DSPs..............................................................................................................................................333.10.3 Signaling Route Mask and Signaling Link Mask....................................................................................................343.11 IPOA PVC..................................................................................................................................................................343.12 F5................................................................................................................................................................................35

4 ATM Transmission Resources..................................................................................................36

5 ATM Transmission Resource Management...........................................................................37

6 Engineering Guidelines.............................................................................................................386.1 WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.................................................................386.1.1 Requirements.............................................................................................................................................................386.1.2 Procedure...................................................................................................................................................................386.1.3 MML Command Examples.......................................................................................................................................406.2 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic..............................................................406.2.1 Requirements.............................................................................................................................................................406.2.2 Procedure...................................................................................................................................................................406.2.3 MML Command Examples.......................................................................................................................................416.3 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth................................................................426.3.1 Requirements.............................................................................................................................................................426.3.2 Procedure...................................................................................................................................................................426.3.3 MML Command Examples.......................................................................................................................................436.4 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes.........................................................................436.4.1 Requirements.............................................................................................................................................................436.4.2 Procedure...................................................................................................................................................................436.4.3 MML Command Examples.......................................................................................................................................446.5 WRFD-05030110 F5....................................................................................................................................................446.5.1 Requirements.............................................................................................................................................................446.5.2 Procedure...................................................................................................................................................................456.5.3 MML Command Examples.......................................................................................................................................456.6 WRFD-050305 UBR+ ATM QoS Class......................................................................................................................466.6.1 Requirements.............................................................................................................................................................466.6.2 Procedure...................................................................................................................................................................466.6.3 MML Command Examples.......................................................................................................................................46

7 Parameters.....................................................................................................................................47



iii

8 Counters........................................................................................................................................94

9 Glossary.......................................................................................................................................177

10 Reference Documents.............................................................................................................178



iv

1 Introduction

1.1 ScopeThis document merges the basic ATM transport principle. It describes protocol stacks,transmission resources, transmission resource management (TRM), and associated parameters.

This document applies to the following NE types.

NE Type NE Model

RNC BSC6900, BSC6910

NodeB Macro 3900 series macro base stations: BTS3900, BTS3900A,BTS3900L, BTS3900AL, DBS3900, BTS3900C3800 series macro base stations: DBS3800, BTS3812E,BTS3812AE

Micro Not supported

LampSite DBS3900 LampSite

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:

WCDMA RANATM Transport Feature Parameter Description 1 Introduction


1

l Feature changeChanges in features of a specific product version

l Editorial changeChanges in wording or addition of information that was not described in the earlier version

RAN15.0 03(2014-09-15)This issue includes the following changes.

Change Type Change Description Parameter Change

Feature change None None

Editorial change Optimized the figures and descriptionsin this document.

None

RAN15.0 02 (2014-08-15)This issue includes the following changes.



Editorial change Updated the description about the AAL2route in 3.9.2 AAL2 Route. The AAL2route does not need to be configured forthe adjacent node of the Iu-PS or Iubtype.

None

RAN15.0 01 (2013-04-28)This issue does not include any changes.

RAN15.0 Draft A (2013-01-30)Compared with issue 01 (2012-07-20) of RAN14.0, Draft A (2013-07-30) of RAN15.0 includesthe following changes.





2


Editorial change Added the differencesbetween the BSC6900 andBSC6910 to the followingchapters and sections: 2Overview of ATMTransport, 3.1 Iub OverATM,3.2 Iu-CS over ATM,3.4 Iur over ATM, 3.5.2Fractional Mode and 3.6.2Function of Timeslot CrossConnection.

None

1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations

FeatureID

Description

Supported byController(Y/N/NA)

Supported byMacro(Y/N/NA)

Supported by Micro(Y/N/NA)

LampSite

BSC6900

BSC6910

BTS3803E

BTS3902E

WRFD-050301

ATMTransmissionIntroductionPackage

Y Y Y N N Y

WRFD-05030101

ATMoverE1T1 onIubInterface

Y Y Y N N Y

WRFD-05030102

ATMoverChannelizedSTM-1/OC-3 onIubInterface

Y Y Y N N Y



3

WRFD-05030103

ATMoverNon-channelizedSTM-1/OC-3con Iub/Iu/IurInterface

Y Y Y N N Y

WRFD-05030104

DynamicAAL2Connections inIub/IuCS/IurInterface

Y Y Y N N Y

WRFD-05030105

Permanent AAL5Connections forControlPlaneTraffic

Y Y Y N N Y

WRFD-05030106

CallAdmission Basedon UsedAAL2PathBandwidth

Y Y Y N N Y

WRFD-05030107

CBR, rt-VBR,nrt-VBR,UBRATMQoSClasses

Y Y Y N N Y

WRFD-05030110

F5 Y Y Y N N Y



4

WRFD-050304

IMATransmission forE1T1 orChannelizedSTM-1/OC-3 onIubInterface

Y Y Y N N Y

WRFD-050305

UBR+ATMQoSClass

Y Y Y N N Y

WRFD-050302

Fractional ATMFunctionon IubInterface

Y Y Y N N Y

NOTE

Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE isnot involved, that is, a feature does not require the support of the NE.

Function Implementation in Macro, Micro, and LampSite Base StationsNone



5

2 Overview of ATM Transport

Huawei radio access network (RAN) provides ATM-based Iub/Iu-CS/Iu-PS/Iur interfaces andATM TRM, such as admission control based on AAL2 path bandwidth, transmission resourcemapping based on ATM QoS classes, and Iub overbooking.

NOTE

The Iu-PS interfaces of BSC6910 do not support ATM Transport.

WCDMA RANATM Transport Feature Parameter Description 2 Overview of ATM Transport


6

3 Protocol Stacks

3.1 Iub Over ATM

3.1.1 Protocol StackFigure 3-1 shows the protocol stack for the ATM-based Iub interface.

Figure 3-1 Protocol stack for the ATM-based Iub interface

The transport network layer of the Iub interface consists of the transport network layer controlplane (area A), transport network layer control plane (area B), and transport network layer userplane (area C).

WCDMA RANATM Transport Feature Parameter Description 3 Protocol Stacks


7

l Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the threeareas can be carried on common physical links.

l Links in areas A and B are carried on SAAL links. Based on the type of carried information,the upper layer of area A is classified into the NodeB Control Port (NCP) and theCommunication Control Port (CCP). Only Q.AAL2 links are carried in area B.

l In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is theATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set upor released for upper-layer services. Therefore, each AAL2 path must have itscorresponding controlling Q.AAL2.

3.1.2 Links on the Iub InterfaceThe links on the ATM-based Iub interface are of three types: SAAL link of User-NetworkInterface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carryNCP, CCP, and ALCAP, as shown in Figure 3-2.

Figure 3-2 Links on the Iub interface

As shown in Figure 3-2:

l For the BSC6900, the signaling processing subsystem consists of SPU boards, and theservice processing subsystem consists of DPU boards. For the BSC6910, the signalingprocessing subsystem and service processing subsystem consist of GPU boards.

l The RINT shown in Figure 3-2 refers to Iub ATM interface boards, including UOIa/UOIc/AOUa/AOUc/AEUa for the BSC6900 and UOIc/AOUc for the BSC6910.

3.1.3 OM IPoA Data Configuration on the Iub InterfaceOn the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance(OM) channel.



8

OM IPoA PVC on the Iub InterfaceFigure 3-3 shows the IPoA PVCs from the RNC to NodeBs.

Figure 3-3 IPoA PVCs from the RNC to NodeBs

NOTE

The RINT shown in Figure 3-3 refers to Iub interface boards, including UOIa/UOIc/AOUa/AOUc/AEUafor the BSC6900 and UOIc/AOUc for the BSC6910.

Network SegmentsIub OM channel travels through the following network segments before reaching the NodeB:

l The 80.168.3.0 segment (with network mask of 255.0.0.0) between the OM board and theATM interface board. This network segment is set before delivery of the BSC6900.

NOTE

When the preconfigured network segment conflicts with an external IP network segment, you canrun the SET SUBNET command to set the internal subnet number.

l The 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interfaceboard and the NodeBs. When setting this network segment, you need to take field conditionsinto consideration.

3.2 Iu-CS over ATM

3.2.1 Protocol StackFigure 3-4 shows the protocol stack for the Iu-CS interface.



9

Figure 3-4 Protocol stack for the ATM-based Iu-CS interface

The transport network layer of the Iu-CS interface consists of the following areas:

l Transport network layer control plane (area A)l Transport network layer control plane (area B)l Transport network layer user plane (area C)

Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areascan be carried on common physical links.

The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.The MSC server and MGW in an R4/R5/R6/R7/R8 network implement their functions asfollows:

l The MSC server implements the functions in area A.l The MGW implements the functions in areas B and C.

3.2.2 Links on the Iu-CS InterfaceThe Iu-CS links on the CN side are of two types: MTP3 link and AAL2 path. Figure 3-5 showsthe links on the ATM-based Iu-CS interface.



10

Figure 3-5 Links on the Iu-CS Interface



l The RINT shown in Figure 3-5 refers to Iu-PS ATM interface boards, including UOIa/UOIc for the BSC6900 and UOIc for the BSC6910.

3.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8

In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6/R7/R8,the MSC connects to the RNC after being split into two entities, namely, MSC server and MGW.

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8Figure 3-6 shows the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.



11

Figure 3-6 Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

The network may require multiple MGWs depending on the traffic volume.

In practice, the MSC server is often not directly connected to the RNC. Data is forwardedbetween the MSC server and the RNC through the routes configured on the MGW. Figure3-7 shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.

Figure 3-7 Example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

Data Configuration on the RNC

In the 3GPP R99, the RNC needs to be configured with only one type of Iu-CS signaling point,that is, the MSC.

In the 3GPP R4/R5/R6/R7/R8, the RNC needs to be configured with the following two types ofIu-CS signaling point:

l MSC server (also called Iu-CS RANAP signaling point)



12

l MGW (also called Iu-CS ALCAP signaling point)

Table 3-1 describes the differences between signaling point configuration in R99 and that inR4/R5/R6/R7/R8.

Table 3-1 Differences between signaling point configuration in R99 and that in R4/R5/R6/R7/R8

Item R4/R5/R6/R7/R8 R99

Type Iu-CS RANAP signalingpoint and Iu-CS ALCAPsignaling point

Iu-CS signaling point

Quantity More than one One

3.3 Iu-PS over ATMThe Iu-PS interface of the BSC6910 does not support ATM transport. This section only describesATM transport on the Iu-PS interface of the BSC6900.

3.3.1 Protocol StackFigure 3-8 shows the protocol stack for the Iu-PS interface.

Figure 3-8 Protocol stack for the ATM-based Iu-PS interface



13

The transport network layer of the Iu-PS interface consists of the transport network layer controlplane (area A) and the transport network layer user plane (area C).

Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas canbe carried on common physical links.

3.3.2 Links on the Iu-PS InterfaceThe Iu-PS links on the CN side are of two types: MTP3 link and IPoA PVC. Figure 3-9 showsthe links on the ATM-based Iu-PS interface.

Figure 3-9 Links on the ATM-based Iu-PS interface



l The RINT shown in Figure 3-9 refers to Iu-PS ATM interface boards, including UOIa/UOIc for the BSC6900.

3.3.3 IPoA Data Configuration on the Iu-PS User PlaneOn the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.

IPoA PVC on the Iu-PS User PlaneFigure 3-10 shows the IPoA PVC on the Iu-PS user plane.



14

Figure 3-10 IPoA PVC on the Iu-PS interface

NOTE

The RINT shown in Figure 3-10 refers to ATM interface boards UOIa/UOIc.

IPoA Data on the Iu-PS User Plane

Table 3-2 describes the IPoA data to be configured on the user plane of the ATM-based Iu-PSinterface.

Table 3-2 IPoA data on the user plane of the ATM-based Iu-PS interface

Item Description

Local IP address of the IPoA PVC (IPADDR(BSC6900,BSC6910))

Device IP address on the ATM interfaceboard of the RNC

Peer IP address of the IPoA PVC(PEERIPADDR(BSC6900,BSC6910))

IP address of the gateway on the SGSN side

PVC between the interface board carrying theIPoA data and the gateway on the SGSN side

-

Route between the interface board carryingthe IPoA data and the network segment of thepeer SGSN

If the IP address of the interface boardcarrying the IPoA data and the IP address ofthe peer SGSN are located on differentsubnets, routes to the destination IP addressneed to be configured at the RNC. DSTIP(BSC6900,BSC6910) is the IP address of theSGSN, and NEXTHOP(BSC6900,BSC6910) is the IP address of thegateway on the SGSN side.

NOTE

On the Iu-PS interface, the SGSN must be configured with routes to the network segment to which the IPaddress of the RNC interface board belongs. The next hop is the gateway on the RNC side. Otherwise, PSservices cannot be provided.



15

3.4 Iur over ATM

3.4.1 Protocol StackFigure 3-11 shows the protocol stack for the Iur interface.

Figure 3-11 Protocol stack for the ATM-based Iur interface

The transport network layer of the ATM-based Iur interface consists of the following areas:

l Transport network layer control plane (area A)l Transport network layer control plane (area B)l Transport network layer user plane (area C)

3.4.2 Links on the Iur InterfaceThe Iur links are of two types: MTP3 link and AAL2 path. Figure 3-12 shows the links on theATM-based Iur interface.



16

Figure 3-12 Links on the Iur interface



l The RINT shown in Figure 3-12 refers to Iu-PS ATM interface boards, including UOIa/UOIc for the BSC6900 and UOIc for the BSC6910.

3.4.3 Configuration Principles for Static Relocation Routes over IurThe IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites forconfiguring IP routes on the Iur interface are that the IP paths between the local RNC and theSGSN, between the neighboring RNC and the SGSN, and between the serving RNC and thedrift RNC are configured.

Figure 3-13 shows the configuration of IP routes on the Iur interface. The IP routes configuredin multiple subsystems are similar.



17

Figure 3-13 IP route configuration on the Iur interface

NOTE

The RINT shown in Figure 3-13 refers to Iur IP interface boards, including GOUa/GOUc/GOUe/FG2a/FG2c for the BSC6900 and GOUc/GOUe/FG2c/EXOUa for the BSC6910.

3.5 ATM Transport ModesATM transport has the following three modes:

l Fractional and IMA: They apply to an AEUa, AOUa, or AOUc.l UNI: It applies to an AEUa, AOUa, AOUc, or UOIc.

3.5.1 UNI Mode

Principles of UNI ModeThe UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of thephysical layer.

In UNI mode, an ATM cell is directly carried on an E1/T1 frame and the bits of the ATM cellare sequentially mapped to the valid timeslots on the E1/T1 frame. Figure 3-14 shows themapping between the ATM cell and the E1 timeslots in UNI mode. The 53 bytes of the ATMcell are sequentially carried on E1 timeslots. Each E1 frame provides 31 timeslots (with slot 0unavailable) for carrying the ATM cell.



18

Figure 3-14 Mapping between the ATM cell and the E1 timeslots in UNI mode

The UNI mode has the characteristics of scrambling, line coding, 16-timeslot enabling, and clockmode. The related parameters are as follows:

l Scrambling switch: specifies whether to enable scrambling.l Line coding method: specifies the line coding method.l 16-timeslot switch: specifies whether to use timeslot 16 or not.

The settings of scrambling switch, line coding method, and 16-timeslot switch at both ends ofE1/T1 must be identical.

The parameters corresponding to UNI mode are shown in Table 3-3.

Table 3-3 Parameters correspond to UNI mode

NE ScramblingSwitch

Line CodingMethod

16-TimeslotSwitch

RNC SCRAMBLESW(BSC6900,BSC6910)

PTCODE TS16ENABLE

NodeB SCRAM LNCODE TS16

Note:



19

Only AEUa support the parameter PTCODE and TS16ENABLE.

Clock Mode

There are two clock modes on the RNC side:

l Common Transmit Clock (CTC): In CTC clock mode, all links in an IMA group share oneclock source. The clock source may be extracted from the same external clock or from alink.

l Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within anIMA group are derived from at least two clock sources. The loopback clock mode is aspecial case of the ITC mode.

The clock mode on the RNC is not configurable, and the default clock mode on the RNC sideis CTC.

The clock mode on the NodeB side is specified by the parameter CLKM(UNI mode/fractionalmode)/CLKM(IMA mode). The clock mode settings at both ends of E1/T1 must be identical.

Line Coding Method

There are four line coding methods:

l HDB3 (for E1 port)

l AMI (for E1/T1 port)

l AMI_ZCS (for E1/T1 port)

l B8ZS (for T1 port)

The coding methods of E1 port are HDB3 and AMI, and the HDB3 is recommended. HDB3represents high-density bipolar code. It is not easy to be interfered, and the transmission distanceis several kilometers.

The coding methods of T1 port are B8ZS and AMI, and B8ZS is recommended. It helps preventclock signals from being lost, while AMI cannot perform this function.

3.5.2 Fractional ModeFractional mode (WRFD-050302 Fractional ATM Function on Iub Interface) is applicable tothe Transmission Convergence (TC) sublayer of the physical layer. This section describes theprinciples and functions of fractional ATM, introduces the two implementation modes (that is,fractional IMA and fractional ATM), and provides the principles for configuring fractional IMAlinks and fractional ATM links.

Principles of Fractional ATM

In the case of fractional ATM, multiple timeslots on an E1 or T1 are used to transmit an ATMcell. As shown in Figure 3-15, at the transmission end, an ATM cell is mapped to multipletimeslots on an E1 or T1; at the reception end, the ATM cell is restored from the associatedtimeslots on the E1/T1. An E1 frame has timeslots numbered from 0 to 31. All the timeslotsexcept timeslot 0 are available for service data transmission. A T1 frame has timeslots numberedfrom 1 to 24. All the timeslots are available for service data transmission. The timeslots to whichthe ATM cell is not mapped can transmit other data.



20

Figure 3-15 Fractional ATM mode

If multiple E1/T1 trunks exist between the transmission end and the reception end and work inIMA mode, such an IMA mode is called fractional IMA. In fractional IMA mode, an IMA groupcontains multiple fractional ATM links.

The fractional ATM mode has the characteristics of scrambling, line coding, and clock mode.For details about clock mode, see Clock Mode. The related parameters are as follows:

l Scrambling switch: specifies whether to enable scrambling.l Line coding method: specifies the line coding method.l E1/T1 timeslot: specifies the timeslot used to transmit the ATM cell.

The settings of scrambling switch, line coding method, and E1/T1 timeslot at both ends of E1/T1 must be identical.

The parameters corresponding to fractional mode are shown in Table 3-4.

Table 3-4 Parameters correspond to fractional mode

NE ScramblingSwitch

Line CodingMethod

E1/T1 Timeslot


PTCODE TSBITMAP(BSC6900,BSC6910)

NodeB SCRAM LNCODE TSN

NOTE

Only AEUa support the parameter PTCODE.

Function of Fractional ATMAfter the fractional ATM function is enabled, the ATM cells of a 3G network can be transmittedover an existing 2G network, as shown in Figure 3-16.



21

Figure 3-16 Fractional ATM function

Two Modes of the Fractional ATM Function

There are two implementation modes of the fractional ATM function on the Iub interface:

l Fractional ATM

In fractional ATM mode, multiple idle timeslots can be used for transmission.

l Fractional IMA

In fractional IMA mode, multiple fractional IMA links are logically gathered into a groupwith each fractional IMA link occupying the same number of idle timeslots.

The parameter FRALNKT is used to specify the fractional link mode on the RNC side.

Table 3-5 shows the boards that support the fractional mode.

Table 3-5 Fractional mode of BSC6900/BSC6910

Modes of the FractionalATM Function

BSC6900 BSC6910

Fractional ATM The fractional ATM/IMAmode is applicable only to theAEUa/AOUc board.

The fractional ATM mode isapplicable only to the AOUcboard.

Fractional IMA Not support



22

3.5.3 IMA Mode

Overview

IMA mode (WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on IubInterface) is applicable to the Transmission Convergence (TC) sublayer of the physical layer.The IMA function is implemented by the IMA group, which is composed of either IMA linksor fractional IMA links.

All IMA links within an IMA group must be of the same type, either common IMA link orfractional IMA link. If an IMA group is composed of fractional IMA links, the quantity oftimeslots carrying each fractional IMA link must be identical.

Principles of IMA Mode

Figure 3-17 shows the principles of the IMA mode based on the assumption that each IMAgroup contains three E1/T1 links.

l At the transmission end, the IMA group receives the ATM cell stream from the ATM layerand distributes the cells among the E1/T1 links.

l At the reception end, the IMA group reassembles the cells to restore the original ATM cellstream, and then transfers the cell stream to the ATM layer.

The physical layer provides high-speed transport channels for ATM cells from the perspectiveof the ATM layer.

Figure 3-17 Principles of the IMA mode

In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frameto implement necessary controlling functions.

The length of an IMA frame, m, is defined during the setup of an IMA group. The parameterFRMLEN(BSC6900,BSC6910)(at the RNC)/FRMLEN (at the NodeB) is used to specify thelength of an IMA frame.

Figure 3-18 shows an IMA frame. The mapping between the ATM cell and the physical link(that is, the E1/T1 link) is similar to that in UNI mode.



23

Figure 3-18 IMA frame

The IMA mode has the characteristics of scrambling, line coding, 16-timeslot enabling, andclock mode. The clock mode of an IMA group is defined from the perspective of an IMA grouprather than a single link. For details about clock mode, see Clock Mode. The related parametersare as follows:

l Scrambling switch: specifies whether to enable scrambling.

l Line coding method: specifies the line coding method.

l 16-timeslot switch: specifies whether to use timeslot 16 or not.

The setting of scrambling switch, line coding method, and 16-timeslot switch at both ends ofE1/T1 must be identical.

The parameters corresponding to IMA mode are shown in Table 3-6.

Table 3-6 Parameters correspond to IMA mode

NE Scrambling Switch Line CodingMethod

16-TimeslotSwitch


PTCODE TS16ENABLE

NodeB SCRAM LNCODE TS16

NOTE

Only AEUa support the parameter PTCODE and TS16ENABLE.

3.6 Timeslot Cross ConnectionThe timeslot cross connection function implements cross connections between timeslots on twoE1/T1s at the physical medium (PM) sublayer of the physical layer.



24

3.6.1 Principles of Timeslot Cross ConnectionFigure 3-19 shows an example of timeslot cross connection. The timeslot cross connectiondevice cross-connects the timeslots on one E1/T1 to the timeslots on the other E1/T1. In theexample shown in the following figure, the device cross-connects slots 2 and 3 on one E1/T1 toslots 4 and 8 on another E1/T1 respectively.

Figure 3-19 Example of timeslot cross connection

3.6.2 Function of Timeslot Cross ConnectionThe AEUa/PEUa/POUc board of BSC6900 supports timeslot cross connection. The BSC6910does not support timeslot cross connection. Through the configured timeslot cross connection,the E1 data in TS A of the source port is transmitted to TS B of the destination port. Therefore,the timeslot cross connection helps provide a transparent data transmission channel for the 2Gequipment or NodeB monitoring equipment.

Figure 3-20 shows implementation of timeslot cross connection.

Figure 3-20 Implementation of timeslot cross connection



25

NOTE

Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by otherapplications, such as fractional ATM, IMA, and UNI.If an E1 link is configured with a timeslot cross connection, the E1 link cannot carry any IMA or UNI link.The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.

The related parameters of the timeslot-cross connection function are as follows:

l SRCPORTNO: specifies the source port to perform the timeslot-cross connection function.l SRCTSMASK: specifies the timeslots occupied by the source port.l DSTPORTNO: specifies the destination port to perform the timeslot-cross connection

function.l DSTTSMASK: specifies the timeslots occupied by the destination port.

Note:

The BSC6910 does not support timeslot cross connection.

3.7 PVC Parameters of the ATM LayerFor configuring the IPoA PVCs, AAL2 paths, SAAL links, or VPCLCX links, the PVCparameters need to be set.

3.7.1 VPI and VCIThe main characteristics of the ATM technology are multiplexing, switching, and transmittingof ATM cells. All these operations are performed over Virtual Channels (VCs). A VC and aVirtual Path (VP) are identified by Virtual Channel Identifier (VCI) and Virtual Path Identifier(VPI) respectively.

Figure 3-21 shows the relationship between VC and VP.

l A VC is identified by a VCI. It is a logical connection between ATM nodes and is thechannel for transmitting ATM cells between two or more nodes. The VC is used for thedata transmission between mobile terminals, between networks, or between mobileterminal and network.

l A VP is a group of VCs at a given reference point. The VCs in the group have the sameVPI.

Figure 3-21 Relationship between VC and VP

3.7.2 Service TypeThe ATM services are of five types (WRFD-05030107 CBR, RT-VBR, NRT-VBR, UBR ATMQoS Classes, WRFD-050305 UBR+ ATM QoS Class): Constant Bit Rate (CBR), Real-Time



26

Variable Bit Rate (RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), Unspecified BitRate (UBR), and UBR_PLUS (UBR+).

Table 3-7 describes the types of service.

Table 3-7 Types of service

Type ofService

Description

CBR No error check, flow control, or other processing

RT-VBR Rate of a service with variable-rate data streams and strict real-timerequirements, for example, interactive compressed video (videotelephony).

NRT-VBR Rate of a service that is applicable to timing transmission. A service ofthis type, for example, e-mail, is relatively insensitive to delivery time ordelay.

UBR Rate of a service with no commitment to transmission and no feedbackon congestion. This type of service is ideal for the transmission of IPdatagrams. In congestion, UBR cells are discarded, and no feedback orrequest for slowing down the data rate is delivered to the transmissionend.

UBR+ UBR+ is an enhancement of UBR with minimum desired cell rate(MDCR) indication. UBR+ is the most suitable for Iub OAM channel.The MCR of UBR+ ensures the connectivity of OAM connection in thecase of Iub transmission resource congestion, and the best effort serviceof UBR+ uses the transmission bandwidth completely.

Table 3-8 describes the characteristics of different ATM services.

Table 3-8 Characteristics of different ATM services

Characteristic

CBR RT-VBR NRT-VBR UBR UBR+

Bandwidthguarantee

Yes Yes Yes No Yes

Applicability to real-timecommunication

Yes Yes No No No

Applicability to bursts ofcommunication

No Yes Yes No No



27

Characteristic

CBR RT-VBR NRT-VBR UBR UBR+

Feedback oncongestion

No No No No No

The ATM service type is also called ATM QoS class. The CBR, RT-VBR, NRT-VBR, or UBRATM QoS classes can be configured for AAL2 path, and the UBR+ ATM QoS class is generallyused for Iub OAM connection.

The service types carried on the AAL2 paths can be determined by running the ADDATMTRF command, and then the mapping between the service types and the transmissionresources for the adjacent node can be configured by running the ADD TRMMAP command.

3.7.3 ATM Traffic RecordsThe ATM traffic records are public resources, which can be used by the IPoA PVCs, AAL2paths, SAAL links, and VPCLCX links. You need to add the traffic record at the RNC based onthe traffic model of the link on the Iub/Iu-CS/Iu-PS/Iur interface. The ATM traffic records canbe configured by the ADD ATMTRF command.

Traffic Parameters

Traffic parameters refer to the parameters used by each PVC for flow control.

Table 3-9 describes the ATM traffic parameters.

Table 3-9 ATM traffic parameters

Parameter ID Description

TRFX(BSC6900,BSC6910)

Identifies a traffic record.

ST(BSC6900,BSC6910)

Indicates the type of service carried over ATM. CBR and RT-VBRindicate real-time services, which are usually carried on the userplanes of the Iur, Iub, and Iu-CS interfaces. NRT-VBR and UBRindicate non-real-time services, which are usually carried on theuser plane of the Iu-PS interface.

UT(BSC6900,BSC6910)

Indicates the unit of PCR(BSC6900,BSC6910), SCR(BSC6900,BSC6910), and MCR(BSC6900,BSC6910).

PCR(BSC6900,BSC6910)

Indicates the maximum rate of transmitting ATM cells. The valueof PCR(BSC6900,BSC6910) must be greater than that of SCR(BSC6900,BSC6910).

SCR(BSC6900,BSC6910)

Indicates the average rate of transmitting ATM cells over a longtime.



28

Parameter ID Description

MCR(BSC6900,BSC6910)

Indicates the minimum rate of transmitting ATM cells.

MBS(BSC6900,BSC6910)

Indicates the maximum number of continuous ATM cells.Generally, the value of MBS(BSC6900,BSC6910) cannot begreater than PCR(BSC6900,BSC6910) x CDVT(BSC6900,BSC6910). The value of CDVT(BSC6900,BSC6910)can be set as large as possible within the permission of the delayand delay variation.

CDVT(BSC6900,BSC6910)

Indicates the maximum tolerable variation in the unit of 0.1 μs.NOTE

It is recommended that the cell delay variation tolerance (CDVT) of a deviceconnected to the NodeB be set to twice the CDVT of the NodeB, therebypreventing packets from the NodeB being lost. The CDVT of the NodeB isset to 10240 by default.

REMARK(BSC6900,BSC6910)

Describes the usage of the ATM traffic record.

The traffic rate is indicated in the following ways:

l PCR(BSC6900,BSC6910): applicable when ST(BSC6900,BSC6910) is set to CBR andthe traffic rate is a constant value.

l Combination of PCR(BSC6900,BSC6910) and SCR(BSC6900,BSC6910): applicablewhen ST(BSC6900,BSC6910) is set to RTVBR or NRTVBR.

l MCR(BSC6900,BSC6910): applicable when ST(BSC6900,BSC6910) is set toUBR_PLUS.

ATM Traffic Record Configuration PrinciplesTable 3-10 provides suggestions for configuring service types during configuration of ATMtraffic records for links.

Table 3-10 Recommended service types for links

Link Preferred Service Type (In DescendingOrder)

NCP/CCP CBR, RTVBR

AAL2 path RTVBR, NRTVBR, CBR, UBR

IPoA PVC (user plane) UBR

IPoA PVC (management plane) UBR_PLUS, RTVBR, NRTVBR, CBR,UBR

MTP3 link RTVBR, NRTVBR, CBR



29

NOTE

l In practice, ATM traffic records should be negotiated between the local and the peer equipment.

l The ATM traffic parameters, such as PCR(BSC6900,BSC6910) and SCR(BSC6900,BSC6910),should be configured depending on the traffic model in use.

l When configuring ATM traffic records for links, you need to consider the traffic on the interface boardsof the RNC.

3.8 AAL5In ATM transport mode, AAL5 connections are used to carry the signaling on the Iub/Iur/Iuinterface (WRFD-05030105 permanent AAL5 connections for control plane traffic). As definedin 3GPP specifications, UNI-SAAL is used for control plane connections on the Iub interface,and NNI-SAAL is used for control plane connections on the Iur and Iu interfaces. The AAL5connections for Iub/Iu-CS/Iur are set up by configuring the SAAL links.

You can run the ADD SAALLNK command to configure the AAL5 connections on the Iub/Iur/Iu interface. On the RNC side, when an AAL5 connection is configured, the TXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910) parameters need to be set. TheTXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910) parameters record theATM traffic, and they can be configured through the ADD ATMTRF command.

An SAAL link is carried on an ATM PVC. The parameters CARRYVPI(BSC6900,BSC6910)and CARRYVCI(BSC6900,BSC6910) are used to identify the PVCs on the RNC side, and theparameters VPI and VCI are used to identify the PVCs on the NodeB side. The PVC identifierand other PVC attributes must be negotiated between the RNC and the peer end.

The signaling messages carried on the UNI-SAAL links are classified into NCP, CCP, andALCAP, and the signaling messages carried on the NNI-SAAL links are MTP3, as described inTable 3-11.

Table 3-11 Data carried on SAAL links

Data Type Description

NCP The NCP carries common process messages of NBAP over the Iub interface.An Iub interface has only one NCP.

CCP A CCP carries dedicated process messages of NBAP over the Iub interface.An Iub interface may have multiple CCPs. The number of CCPs depends onnetwork planning.

ALCAP ALCAP is also called Q.AAL2. Typically, an Iub interface has one ALCAP.

MTP3 MTP3 links are contained in an MTP3 link set. MTP3 links are carried on theSAAL links of Network-to-Network Interface (NNI) type.

3.9 AAL2 Path



30

3.9.1 AAL2 Connections and AAL2 PathThe Q.AAL2 module is responsible for dynamically setting up and releasing AAL2 connectionsbetween the RNC and the peer end. The peer end can be a NodeB, a CS CN node, or a neighboringRNC. PATHID(BSC6900,BSC6910) specifies the ID of an AAL2 path, and the PATHID(BSC6900,BSC6910) of the same AAL2 path configured between two AAL2 nodes must be thesame. An AAL2 path contains multiple AAl2 connections. CID specifies the ID of an AAL2connection on the path. The CID state can be Busy or Idle. If the CID is in the busy state, theCID carries traffic; if the CID is in the idle state, no traffic is carried on it.

The AAL2 paths can be configured for the Iub/Iu-CS/Iur interface (WRFD-05030104 DynamicAAL2 Connections on Iub/IuCS/Iur Interface).

Figure 3-22 shows the relationship between an AAL2 path and AAL2 connections on the Iubinterface.

Figure 3-22 Relationship between an AAL2 path and AAL2 connections

According to different traffic classes (conversational, streaming, interactive, and background),the following types of AAL2 path can be configured:

l CBRl RT-VBRl NRT-VBRl UBR

According to different types of service (R99, HSDPA, and HDUPA), the following types ofAAL2 path can be configured:

l R99l HSPAl SHARE

The AAL2 path can be configured through the ADD AAL2PATH command. On the RNC side,when an AAL2 path is configured, the TXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910) parameters need to be set. They determine the type of path. The TXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910) parameters record the ATM traffic,and they can be configured through the ADD ATMTRF command. For details, see section 3.7.3ATM Traffic Records.

An AAL2 path is carried on a PVC. The parameters VPI(BSC6900,BSC6910) and VCI(BSC6900,BSC6910) are used to identify the PVCs. The PVC identifier and other PVC attributesmust be negotiated between the RNC and the peer end.



31

3.9.2 AAL2 RouteAn AAL2 path may reach not the destination node but an adjacent node. In this case, AAL2routes can be configured to reach the destination node. The AAL2 route to an ATM node canbe configured through the ADD AAL2RT command.

Figure 3-23 shows an example of the AAL2 route.

Figure 3-23 Example of the AAL2 route

NOTE

l Even if the destination node and the adjacent node are the same, an AAL2 route needs to be configured.

l The AAL2 route does not need to be configured for the adjacent node of the Iu-PS or Iub type.

3.10 MTP3

3.10.1 MTP3 LinksMTP3 links are contained in an MTP3 link set. MTP3 links are carried on the SAAL links ofNetwork-to-Network Interface (NNI) type. You can run the command ADD MTP3LKS tospecify an MTP3 link set, and then run the command ADD MTP3LNK to add the MTP3 linksby using the parameter SIGLKSX(BSC6900,BSC6910).

MTP3 Links for Iu-CS Interface

The configuration of MTP3 links between the RNC and the MSC server depends on thenetworking between the MSC server and the RNC:

l If the MSC server is directly connected to the RNC, at least one MTP3 link is required forthe MSC server (IUCS_RANAP signaling point). It is recommended that more than oneMTP3 link be configured.

l If the MSC server is connected to the RNC through the MGW, the MSC server(IUCS_RANAP signaling point) does not require any MTP3 link.

l If the MSC server is connected to the RNC not only directly but also through the MGW,as shown in Figure 3-24, the MSC server (IUCS-RANAP) requires at least one MTP3 link.It is recommended that more than one MTP3 link be configured.



32

Figure 3-24 Example of connections between the MSC server and the RNC

MTP3 Links for Iu-PS Interface

An Iu-PS interface requires at least one MTP3 link. It is recommended that more than one MTP3link be configured.

MTP3 Links for Iur Interface

The configuration of MTP3 links depends on the networking between the RNC and theneighboring RNC:

l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at leastone MTP3 link. It is recommended that more than one MTP3 link be configured.

l If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP),no MTP3 link is required.

It is recommended that the SAAL links of NNI type be evenly distributed to the CPUSsubsystems in the MPS/EPS so that the signaling exchange can be reduced between the CPUSsubsystems.

3.10.2 Types of MTP3 DSPsThe RNC supports seven types of Destination Signaling Point (DSP): IUCS, IUCS_ALCAP,IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different types have differentmeanings.

Table 3-12 describes the types of DSP.

Table 3-12 Types of DSP

DSP Type Description

IUCS R99 MSC DSP. The IUCS DSP has the control plane functions of bothradio network layer and transport network layer on the Iu-CS interface.

IUCS_ALCAP R4 MGW DSP. The IUCS_ALCAP DSP has the control planefunctions of the transport network layer on the Iu-CS interface.



33

DSP Type Description

IUCS_RANAP R4 MSC server DSP. The IUCS_RANAP DSP has the control planefunctions of the radio network layer on the Iu-CS interface.

IUPS Signaling point in the Iu-PS control plane

IUR Other RNC signaling points

STP Signaling transfer point

AAL2SWITCH AAL2 transfer point

3.10.3 Signaling Route Mask and Signaling Link MaskThe number (represented by n) of 1s in a signaling route mask determines the maximum numberof routes (2n). For example, B0000 indicates that there is at most one route. B0001 or B1000indicates that there are at most two routes.

The number (represented by n) of 1s in a signaling link mask determines the maximum numberof links (2n). For example, B0000 indicates that there is at most one link. B0001 or B1000indicates that there are at most two links.

The result of the logical AND operation on the signaling link mask and the signaling route maskmust be 0, as shown in Figure 3-25.

Figure 3-25 Relationship between signaling link mask and signaling route mask

3.11 IPOA PVCIPOA is a technology in which IP packets are transmitted over the ATM transport network.Essentially, the ATM links over each interface are carried over PVCs. The IPoA PVCs on theIub interface are used to transmit the OM information of a NodeB. In this case, the IPoA PVCis called the management plane IPoA PVC. The IPoA PVC on the Iu-PS interface is a PVC tothe SGSN gateway.

The IPOA PVC can be configured through the ADD IPOAPVC command. If the parameterPEERT(BSC6900,BSC6910) is set to IUB, the IPOA link can only be used as an OM channel.The parameters CARRYVPI(BSC6900,BSC6910) and CARRYVCI(BSC6900,BSC6910) areused to identify the PVCs.

When an IPOA PVC is configured, the TXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910) parameters need to be set. The TXTRFX(BSC6900,BSC6910) and



34

RXTRFX(BSC6900,BSC6910) parameters record the ATM traffic, and they can be configuredthrough the ADD ATMTRF command.

3.12 F5Huawei supports operations on ATM OAM F5 end-to-end flows specified in ITU I.610(WRFD-05030110 F5):

l Fault management

– AIS: alarm indication signal

– RDI: remote defect indication

– CC: continuity check and loopbackl Performance management

– Forward monitoring

– Backward reportingl Activation and deactivation

The CC can be activated to monitor the end-to-end AAL2 path virtual connect link (VCL) andIu-PS user plane VCL. When one VCL for AAL2 path or Iu-PS GTPU is loss of continuity(LOC), AIS, or RDI, this VCL is blocked. Then the service is established on other alternativeVCLs to prevent the failure of the call. You can run the ACT VCLCC command to activate theCC function and the DEA VCLCC command to deactivate the CC function. When the parameterVCLTYPE is set to CC, the CC function is activated.

Huawei also supports proprietary delay detection function. When an NE receives a detectionstart command from the NMS, it starts detecting delay on the current AAL2 link or AAL5 linkand periodically reports the delay to the NMS. The 8-byte reserved IE (LB IE) in the loopbackmessage is used to store the message transmission time. When an NE receives the loopbackmessage, it calculates the delay based on the time difference between transmission and reception.



35

4 ATM Transmission Resources

ATM transmission resources can be classified into physical resources, logical ports, resourcegroups, and paths. The transmission resources for Iub/Iu/Iur interfaces vary according todifferent networking. Huawei supports the following types of ATM transmission:

l ATM over E1T1 on Iub interface (WRFD-05030101 ATM over E1T1 on Iub interface)The BSC6910 does not support this feature.

l ATM over channelized STM-1/OC-3 on Iub interface (WRFD-05030102 ATM overchannelized STM-1/OC-3 on Iub interface)

l ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface (WRFD-05030103ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface)

For details about the ATM transmission resources, see "Transmission Resources" in theTransmission Resource Management Feature Parameter Description.

WCDMA RANATM Transport Feature Parameter Description 4 ATM Transmission Resources


36

5 ATM Transmission Resource Management

For ATM transport, Huawei provides the following transmission resource management:

l Admission control (WRFD-05030106 Call Admission Based on Used AAL2 PathBandwidth), which is used to allow more users to be admitted with the QoS guaranteed.

l Transmission resource mapping, in which the CBR, RT-VBR, NRT-VBR, and UBR ATMQoS classes are used to implement differentiated services.

l Iub overbooking (WRFD-050405 Overbooking on ATM Transmission, WRFD-050406ATM QoS Introduction on Hub Node B (Overbooking on Hub Node B Transmission)),which is used to improve the usage efficiency on ATM transport scenario

For details about admission control, transmission resource mapping, and Iub overbooking, seethe Transmission Resource Management Feature Parameter Description.

WCDMA RANATM Transport Feature Parameter Description 5 ATM Transmission Resource Management


37

6 Engineering Guidelines

6.1 WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface

This section describes how to activate, verify, and deactivate the basic feature WRFD-05030104Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.

6.1.1 Requirementsl Dependencies on Hardware

None

l Dependencies on Other Features

None

l License

This feature is not under license control.

l Other Prerequisites

The RAN is based on ATM transmission.

6.1.2 Procedure

Activationl On the RNC side

1. Run the RNC MML command ADD ADJNODE (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > Adjacent Node, IURConfiguration Express > ATM Transport > Adjacent Node, IUCS ConfigurationExpress > ATM Transport > Adjacent Node; CME batch modification center: notsupported) to add an adjacent node. Set the parameter Adjacent Node Type to IUB,IUR, or IUCS, and the parameter Transport Type to ATM. If the node is the lowestleaf node of the switching network, set the parameter Is Root Node to YES; otherwise,set the parameter Is Root Node to NO.

WCDMA RANATM Transport Feature Parameter Description 6 Engineering Guidelines


38

NOTE

For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Type of its upper-level hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface, theparameter Adjacent Node Type of its upper-level hub node must be UNI_AAL2SWITCH.

2. Run the RNC MML command ADD AAL2PATH (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCSConfiguration Express > ATM Transport > AAL2 Path, IUR Configuration Express> ATM Transport > AAL2 Path; CME batch modification center: not supported) toadd an AAL2 path. The parameters CARRYVPI and CARRYVCI must be consistentwith those of the AAL2 path configured on the peer end.

l On the NodeB side

For details about configuration on the NodeB side, obtain the documentation 3900 SeriesBase Station Product Documentation and navigate in the following sequence: 3900 SeriesBase Station Initial Configuration (CME-based) > Creating Base Stations > CreatingNodeBs > Creating a Single NodeB > Configuring NodeB Transport Data > ConfiguringATM Transport Data on the NodeB Side.

Verification

Step 1 Run the RNC MML command DSP AAL2PATH to query the status of the AAL2 path on theIub interface.

Expected result: The value of Operation state is Available.

Step 2 Run the NodeB MML command DSP AAL2PATH to query the status of the AAL2 path on theIub.

Expected result: The value of AAL2 Path Status is Normal.

Step 3 In the Iub/Iu-CS ATM transmission scenario, a UE in idle state camps on CELL1 and the controlplane is correctly configured. Originate the speech and data services. If the service access isnormal, the AAL2 path on the Iub/Iu-CS interface is set up successfully.

Step 4 Optional: In the ATM transmission scenario on the Iur interface, a UE in idle state camps onCELL1 and the control plane is correctly configured. Originate a cross-Iur handover. If thehandover is successful, the AAL2 path on the Iur interface is set up successfully.

----End

Deactivation

Step 1 Run the RNC MML command RMV AAL2PATH (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCS ConfigurationExpress > ATM Transport > AAL2 Path, IUR Configuration Express > ATM Transport > AAL2Path; CME batch modification center: not supported) to delete an AAL2 path.

Step 2 Run the RNC MML command RMV ADJNODE (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > Adjacent Node, IUR ConfigurationExpress > ATM Transport > Adjacent Node, IUCS Configuration Express > ATM Transport >Adjacent Node; CME batch modification center: not supported) to delete an ATM adjacent node.



39

Step 3 Run the NodeB MML command RMV AAL2PATH (CME single configuration: ATMTransport Layer > AAL2path) to delete an AAL2 path on the NodeB side.

----End

6.1.3 MML Command Examples//Activating Dynamic AAL2 Connections in Iub/IuCS/Iur Interface//Adding an adjacent nodeADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, TRANST=ATM, IsROOTNODE=YES, DPX=1;//Adding an AAL2 pathADD AAL2PATH: ANI=2, PATHID=1, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=111, RXTRFX=111, AAL2PATHT=R99; //Verifying Dynamic AAL2 Connections in Iub/IuCS/Iur InterfaceDSP AAL2PATH: ANI=2, PATHID=1;

//Deactivating Dynamic AAL2 Connections in Iub/IuCS/Iur Interface//On the RNC side//Deleting an AAL2 pathRMV AAL2PATH: ANI=2, PATHID=1;//Deleting an ATM adjacent nodeRMV ADJNODE: ANI=2;//On the NodeB sideRMV AAL2PATH: NT=LOCAL, PATHID=1;

6.2 WRFD-05030105 Permanent AAL5 Connections forControl Plane Traffic

This section describes how to activate, verify, and deactivate the basic feature WRFD-05030105Permanent AAL5 Connections for Control Plane Traffic.


Nonel Dependencies on Other Features

This feature does not depend on other features.l License

This feature is not under license control.l Other Prerequisites

The equipment data has been configured for the ATM transmission on the Iub/Iu/Iurinterface. For details, see section Configuring the Equipment Data of the BSC6900 UMTSInitial Configuration Guide or BSC6910 UMTS Initial Configuration Guide.

6.2.2 Procedure

Activation Procedure

Step 1 Run the RNC MML command ADD SAALLNK (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > SAAL Signaling Link, IUCSConfiguration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express



40

> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) toadd an SAAL link. If the interface is Iub, set the parameter Interface type to UNI. If the interfaceis Iu or Iur, set Interface type to NNI.

Step 2 Optional: Run the RNC MML command ADD UNCP (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > NCP Link; CME batch modificationcenter: not supported) to add a NodeB Control Port (NCP) link.

Step 3 Optional: Run the RNC MML command ADD UCCP (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > CCP Link; CME batch modificationcenter: not supported) to add a Communication Control Port (CCP) link.

----End

NOTE:

An SAAL link can carry only one NCP or CCP link. Therefore, choose to perform step 2 or step3 based on the actual situation.

Verification ProcedureRun the RNC MML command DSP SAALLNK to query the status of the SAAL link.

Expected result: The value of SAAL link state is AVAILABLE.

Deactivation ProcedureNOTE:

An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP orCCP link carried by the SAAL link, based on the actual situation.

Step 1 Optional: Run the RNC MML command RMV UNCP (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > NCP Link; CME batch modificationcenter: not supported) to remove the NCP link carried by the SAAL link.

Step 2 Optional: Run the RNC MML command RMV UCCP (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > CCP Link; CME batch modificationcenter: not supported) to remove the CCP link carried by the SAAL link.

Step 3 Run the RNC MML command RMV SAALLNK (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > SAAL Signaling Link, IUCSConfiguration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) toremove the SAAL link.

----End

6.2.3 MML Command Examples//Activating Permanent AAL5 Connections for Control Plane Traffic ADD SAALLNK: SRN=1, SN=2, SAALLNKN=10, CARRYT=UNI, CARRYSRN=0, CARRYSN=14, CARRYUNILNKN=2, CARRYVPI=10, CARRYVCI=55, TXTRFX=100, RXTRFX=100, SAALLNKT=UNI; ADD UCCP: NODEBNAME="NodeB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=10; //Verifying Permanent AAL5 Connections for Control Plane Traffic DSP SAALLNK: SRN=1, SN=2, SAALLNKN=10; //Deactivating Permanent AAL5 Connections for Control Plane Traffic RMV UCCP: NODEBNAME="NodeB1", PN=0; RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;



41

6.3 WRFD-05030106 Call Admission Based on Used AAL2Path Bandwidth

This section describes how to activate, verify, and deactivate the basic feature WRFD-05030106Call Admission Based on Used AAL2 Path Bandwidth.


None


This feature does not depend on other features.

l License


6.3.2 Procedure

Activation

Step 1 Run the RNC MML command ADD ATMTRF (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batchmodification center: not supported) to set parameters to appropriate values. For example, setService type to NRTVBR, Peak cell rate to 100, and Sustainable cell rate to 80.

Step 2 Run the RNC MML command ADD AAL2PATH (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path; CME batch modificationcenter: not supported) to add an ATM Adaptation Layer type 2 (AAL2) path. In this step, setTXTRFX and RXTRFX in accordance with the settings in step 1.

----End

Verification

Step 1 Assume that the verification is based on the preceding parameter settings and the peer end isconfigured with the corresponding AAL2 path link. Originate a PS interactive service. If thesubscribed rate is 64 kbit/s, the UE successfully accesses the network.

Step 2 Run the RNC MML command DSP AAL2PATH to view that the used bandwidth of the pathis about 30 kbit/s, which is the admission bandwidth of the control plane.

Step 3 Originate consecutive multiple PS interactive services when the service established in step 1 isnot released. If the subscribed rate is 64 kbit/s, the third PS interactive service fails to be set up.

----End

Deactivation

This feature does not need to be deactivated.



42

6.3.3 MML Command Examples//Activation procedure ADD ATMTRF: TRFX=100, ST=NRTVBR, UT=CELL/S, PCR=100, SCR=80; ADD AAL2PATH: ANI=0, PATHID=10, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0, RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=100, RXTRFX=100, AAL2PATHT=R99;

6.4 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoSClasses

This section describes how to activate, verify, and deactivate the basic feature"WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes".


None



l License


6.4.2 Procedure


Run the RNC MML command ADD ATMTRF (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batchmodification center: not supported) to add an ATM traffic record. To add more ATM trafficrecords, run this command repeatedly.

Verification Procedure

Ensure that an AAL2 path using the ATM traffic record added in the activation procedure andTRMMAP of the AAL2 path have been set before the verification.

Step 1 Set up a service.

Step 2 Start the Iub interface tracing task on the LMT.

Step 3 Check TXTRFX of the AAL2 path corresponding to the path ID in the QAAL2 Establish requestmessage.

The expected result is that the value of TXTRFX is consistent with that in the ADDATMTRF command.

----End



43

Deactivation Procedure

Step 1 Run the RNC MML command RMV AAL2PATH (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCS ConfigurationExpress > ATM Transport > AAL2 Path, IUR Configuration Express > ATM Transport > AAL2Path; CME batch modification center: not supported) to delete an AAL2 path using an ATMtraffic record. To delete more AAL2 paths, run this command repeatedly.

Step 2 Run the RNC MML command RMV ATMTRF (CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batchmodification center: not supported) to delete an ATM traffic record. To delete more ATM trafficrecords, run this command repeatedly.

----End

6.4.3 MML Command Examples//Activating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes ADD ATMTRF: TRFX=105, ST=CBR, UT=CELL/S, PCR=1000; //Verifying CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes LST ATMTRF: TRFX=105; //Deactivating CBR, rt-VBR, nrt-VBR, UBR ATM QoS ClassesRMV AAL2PATH: ANI=2, PATHID=1;RMV ATMTRF: TRFX=105;

6.5 WRFD-05030110 F5This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110F5. (This feature cannot be configured using the CME.)


– Dependencies on the RNC sideNone.

– Dependencies on the NodeB sideOnly 3900 series Base Station supports the passive detection based on IE LB.

l Dependencies on Other FeaturesThis feature does not depend on other features.

l LicenseThis feature is not under license control.


– The basic information about the RNC is configured. For details, see the Configuringthe Basic Data.

– The SAALLNK, AAL2PATH, or IPOAPVC link exists.



44

6.5.2 Procedure


Step 1 Run the RNC MML command ACT VCLCC to activate the VCL CC or loopback function fora link. To activate the function for multiple links, run this command repeatedly. There are threetypes of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.

Step 2 Run the RNC MML command ACT VCLPM to activate the VCL PM function for a link. Toactivate the function for multiple links, run this command repeatedly. There are three types oflinks, that is, SAALLNK, AAL2PATH, and IPOAPVC.

----End


Step 1 Run the RNC MML command DSP VCLCC to query the CC result of a VCL.

l If the VCL CC is activated and the PVC is functional, the SINK activated state andSOURCE activated state are UP, and LOC, AIS, and RDI alarm state is normal.

l If the loopback is activated and the PVC is functional, the loopback query result is UP, andLOC, AIS, and RDI alarm state is normal.

Step 2 Run the RNC MML command DSP VCLPM to query the PM result of a VCL.

l If the VCL PM is activated, the SINK activated state and SOURCE activated state arePM_UP, and PM Active Fail Alarm is Normal.

----End


Step 1 Run the RNC MML command DEA VCLCC to deactivate the VCL CC or loopback functionfor a link. To deactivate the function for multiple links, run this command repeatedly. There arethree types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.

Step 2 Run the RNC MML command DEA VCLPM to deactivate the VCL PM for a link. To deactivatethe function for multiple links, run this command repeatedly. There are three types of links, thatis, SAALLNK, AAL2PATH, and IPOAPVC.

----End

6.5.3 MML Command Examples//Activating F5 ACT VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0, VCLTYPE=CC; ACT VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0; //Verifying F5 DSP VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0; DSP VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0; //Deactivating F5 DEA VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0; DEA VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;



45

6.6 WRFD-050305 UBR+ ATM QoS ClassThis section describes how to activate, verify, and deactivate the basic feature "WRFD-050305UBR+ ATM QoS Class".


None



l License



The basic information about the RNC is configured. For details, see the Configuring theBasic Data.

6.6.2 Procedure


Run the MML command ADD ATMTRF (CME single configuration: NodeB ConfigurationExpress > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch modification center:not supported) to add an ATM traffic record of the UBR+ class. To add more ATM trafficrecords, run this command repeatedly.


Run the MML command LST ATMTRF to query the ATM traffic configuration.

Expected result: The query result is consistent with the configuration information.


Run the MML command RMV ATMTRF (CME single configuration: NodeB ConfigurationExpress > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch modification center:not supported) to delete an ATM traffic record of the UBR+ class. To delete more ATM trafficrecords, run this command repeatedly.

6.6.3 MML Command Examples//Adding UBR+ ATM QoS ClassADD ATMTRF: TRFX=105, ST=UBR_PLUS, UT=CELL/S, MCR=100;//Verifying UBR+ ATM QoS ClassLST ATMTRF: TRFX=105;//Deactivating UBR+ ATM QoS ClassRMV ATMTRF: TRFX=105;



46

7 Parameters

Table 7-1 Parameter description

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

IPADDR

BSC6900

ADDIPOAPVCMODIPOAPVCRMVIPOAPVC

WRFD-050105WRFD-031100WRFD-05030105WRFD-050301

ATMSwitching BasedHubNode BBOOTPPermanent AAL5Connections forControlPlaneTrafficATMTransmissionIntroductionPackage

Meaning: Local IP address.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None

WCDMA RANATM Transport Feature Parameter Description 7 Parameters


47

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

IPADDR

BSC6910




Meaning: Local IP addressGUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None

PEERIPADDR

BSC6900




Meaning: Peer IP address.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None



48

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

PEERIPADDR

BSC6910




Meaning: Peer IP address.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None

DSTIP BSC6900

ADDIPRTMODIPRTRMVIPRT

WRFD-050409WRFD-050402WRFD-050410

IPTransmissionIntroduction onIuInterfaceIPTransmissionIntroduction onIubInterfaceIPTransmissionIntroduction onIurInterface

Meaning: Destination IP address.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None



49

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

DSTIP BSC6910


WRFD-150244WRFD-150243

Iu/Iur IPTransmissionBasedonDynamic LoadBalanceIub IPTransmissionBasedonDynamic LoadBalance

Meaning: Destination IP address.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None



50

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

NEXTHOP

BSC6900


WRFD-050402WRFD-050410WRFD-050409WRFD-050107WRFD-140207WRFD-140208

IPTransmissionIntroduction onIubInterfaceIPTransmissionIntroduction onIurInterfaceIPTransmissionIntroduction onIuInterfaceIProutingBasedHubNode BIu/IurTransmissionResource Pool inRNCIubTransmissionResource Pool inRNC

Meaning: IP address of the next hop.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None



51

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

NEXTHOP

BSC6910


WRFD-150244WRFD-050107WRFD-150243

Iu/Iur IPTransmissionBasedonDynamic LoadBalanceIProutingBasedHubNode BIub IPTransmissionBasedonDynamic LoadBalance

Meaning: IP address of the next hop.GUI Value Range: Valid IP AddressUnit: NoneActual Value Range: Valid IP AddressDefault Value: None

SCRAMBLESW

BSC6900

SETE1T1

WRFD-05030101


Meaning: Scramble switch.GUI Value Range: OFF(OFF), ON(ON)Unit: NoneActual Value Range: OFF, ONDefault Value: ON(ON)

SCRAMBLESW

BSC6910

SETE1T1

WRFD-05030102

ATMoverChannelizedSTM-1/OC-3 onIubInterface

Meaning: Scramble switch.GUI Value Range: OFF(OFF), ON(ON)Unit: NoneActual Value Range: OFF, ONDefault Value: ON(ON)

PTCODE

BSC6900

SETE1T1

WRFD-05030101


Meaning: Line coding method.GUI Value Range: AMI_ZCS(AMI_ZCS), B8ZS(B8ZS), HDB3(HDB3), AMI(AMI)Unit: NoneActual Value Range: AMI_ZCS, B8ZS, HDB3, AMIDefault Value: HDB3(HDB3)



52

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TS16ENABLE

BSC6900

SETE1T1

WRFD-05030101


Meaning: This parameter specifies whether to usetimeslot 16, or not.GUI Value Range: OFF(OFF), ON(ON)Unit: NoneActual Value Range: OFF, ONDefault Value: OFF(OFF)

SCRAM BTS3900,BTS3900WCDMA

ADDUNILNKLSTUNILNK

WRFD-05030101


Meaning: Indicates whether scrambling is applied to theUNI link.GUI Value Range: DISABLE(Disable), ENABLE(Enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: ENABLE(Enable)

LNCODE

BTS3900,BTS3900WCDMA,BTS3900 LTE

ADDE1T1SETE1T1LSTE1T1

WRFD-05030101WRFD-050411

GBFD-118611

ATMoverE1T1 onIubInterfaceFractional IPFunctionon IubInterface

Abis IPover E1/T1

Meaning: Indicates the line coding mode of an E1/T1port.GUI Value Range: HDB3(E1 HDB3 Code), AMI(E1/T1 AMI Code), B8ZS(T1 B8ZS Code)Unit: NoneActual Value Range: HDB3, AMI, B8ZSDefault Value: None

TS16 BTS3900,BTS3900WCDMA

ADDUNILNKLSTUNILNK

WRFD-05030101


Meaning: Indicates whether the UNI link can usetimeslot 16 of an E1 port.GUI Value Range: DISABLE(Disable), ENABLE(Enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: DISABLE(Disable)



53

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

CLKM BTS3900,BTS3900WCDMA,BTS3900 LTE

ADDE1T1SETE1T1DSPE1T1LSTE1T1

MRFD-210501WRFD-05030101WRFD-050411

GBFD-118611

Node BClockATMoverE1T1 onIubInterfaceFractional IPFunctionon IubInterface

Abis IPover E1/T1

Meaning: Indicates the clock mode of the E1/T1 port.1. If the BS extracts the line clock from the E1/T1 port,the clock mode of the E1/T1 port must be set to SLAVE.If the BS provides the line clock for the lower-levelequipment through the E1/T1 port, the clock mode ofthe E1/T1 port must be set to MASTER. Otherwise, theline clock may fail to work properly. 2. When the E1/T1 port provides an 8K clock reference for thetransmission interface board, the clock mode of the E1/T1 port must be set to SLAVE. 3. The clock modes ofE1/T1 ports used by an inter-board MLPPP groupcannot be all set to SLAVE.GUI Value Range: MASTER(Master Mode), SLAVE(Slave Mode)Unit: NoneActual Value Range: MASTER, SLAVEDefault Value: SLAVE(Slave Mode)

CLKM BTS3900,BTS3900WCDMA

ADDIMAGRPMODIMAGRPLSTIMAGRP

WRFD-050304

IMA forE1T1 orChannelizedSTM-1/OC-3 onIubInterface

Meaning: Indicates the clock mode of the IMA group.Links in an IMA group may pass through differenttransport networks. As a result, links in the IMA groupmay use different clock sources for synchronization. Itis recommended that the IMA group work inIndependent Transmit Clock (ITC) mode.GUI Value Range: CTC(Common Transmit Clock),ITC(Independent Transmit Clock)Unit: NoneActual Value Range: CTC, ITCDefault Value: ITC(Independent Transmit Clock)



54

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TSBITMAP

BSC6900

ADDFRALNKMODFRALNK

WRFD-050105WRFD-050302

ATMSwitching BasedHubNode BFractional ATMFunctionon IubInterface

Meaning: Bearer timeslotGUI Value Range: TS1(Time_slot_1), TS2(Time_slot_2), TS3(Time_slot_3), TS4(Time_slot_4),TS5(Time_slot_5), TS6(Time_slot_6), TS7(Time_slot_7), TS8(Time_slot_8), TS9(Time_slot_9),TS10(Time_slot_10), TS11(Time_slot_11), TS12(Time_slot_12), TS13(Time_slot_13), TS14(Time_slot_14), TS15(Time_slot_15), TS16(Time_slot_16), TS17(Time_slot_17), TS18(Time_slot_18), TS19(Time_slot_19), TS20(Time_slot_20), TS21(Time_slot_21), TS22(Time_slot_22), TS23(Time_slot_23), TS24(Time_slot_24), TS25(Time_slot_25), TS26(Time_slot_26), TS27(Time_slot_27), TS28(Time_slot_28), TS29(Time_slot_29), TS30(Time_slot_30), TS31(Time_slot_31)Unit: NoneActual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15,TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23,TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31Default Value: None

TSBITMAP

BSC6910

ADDFRALNKMODFRALNK

WRFD-050105WRFD-050302


Meaning: Bearer timeslotGUI Value Range: TS1(Time_slot_1), TS2(Time_slot_2), TS3(Time_slot_3), TS4(Time_slot_4),TS5(Time_slot_5), TS6(Time_slot_6), TS7(Time_slot_7), TS8(Time_slot_8), TS9(Time_slot_9),TS10(Time_slot_10), TS11(Time_slot_11), TS12(Time_slot_12), TS13(Time_slot_13), TS14(Time_slot_14), TS15(Time_slot_15), TS16(Time_slot_16), TS17(Time_slot_17), TS18(Time_slot_18), TS19(Time_slot_19), TS20(Time_slot_20), TS21(Time_slot_21), TS22(Time_slot_22), TS23(Time_slot_23), TS24(Time_slot_24), TS25(Time_slot_25), TS26(Time_slot_26), TS27(Time_slot_27), TS28(Time_slot_28), TS29(Time_slot_29), TS30(Time_slot_30), TS31(Time_slot_31)Unit: NoneActual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15,TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23,TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31Default Value: None



55

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description


ADDFRAATMLSTFRAATM

WRFD-05030101


Meaning: Indicates whether scrambling is applied to thefractional ATM link.GUI Value Range: DISABLE(Disable), ENABLE(Enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: ENABLE(Enable)

TSN BTS3900,BTS3900WCDMA

ADDFRAATMDSPDHCPRSLTLSTFRAATM

WRFD-05030101


Meaning: Indicates the number of the ET/T1 timeslotthat carries the fractional ATM link.GUI Value Range: TS1(Time Slot 1), TS2(Time Slot2), TS3(Time Slot 3), TS4(Time Slot 4), TS5(Time Slot5), TS6(Time Slot 6), TS7(Time Slot 7), TS8(Time Slot8), TS9(Time Slot 9), TS10(Time Slot10), TS11(TimeSlot11), TS12(Time Slot12), TS13(Time Slot13), TS14(Time Slot14), TS15(Time Slot15), TS16(TimeSlot16), TS17(Time Slot17), TS18(Time Slot18), TS19(Time Slot19), TS20(Time Slot20), TS21(TimeSlot21), TS22(Time Slot22), TS23(Time Slot23), TS24(Time Slot24), TS25(Time Slot25), TS26(TimeSlot26), TS27(Time Slot27), TS28(Time Slot28), TS29(Time Slot29), TS30(Time Slot30), TS31(Time Slot31)Unit: NoneActual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15,TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23,TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31Default Value: None

FRALNKT

BSC6900

ADDFRALNK

WRFD-050105WRFD-050302


Meaning: Fractional link type.GUI Value Range: FRAATM, FRAIMAUnit: NoneActual Value Range: FRAATM, FRAIMADefault Value: None



56

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

FRMLEN

BSC6900

ADDIMAGRPMODIMAGRP

WRFD-050105WRFD-050304

ATMSwitching BasedHubNode BIMA forE1T1 orChannelizedSTM-1/OC-3 onIubInterface

Meaning: Frame length. A longer frame improves thetransmission efficiency, but at the same time reduces thesensitivity to errors.GUI Value Range: D32, D64, D128, D256Unit: NoneActual Value Range: D32, D64, D128, D256Default Value: D128

FRMLEN

BSC6910

ADDIMAGRPMODIMAGRP

WRFD-050105WRFD-050304

ATMSwitching BasedHubNode BIMA forE1T1 orChannelizedSTM-1/OC-3 onIubInterface

Meaning: Frame length. A longer frame improves thetransmission efficiency, but at the same time reduces thesensitivity to errors.GUI Value Range: D32, D64, D128, D256Unit: NoneActual Value Range: D32, D64, D128, D256Default Value: D128

FRMLEN

BTS3900,BTS3900WCDMA

ADDIMAGRPMODIMAGRPDSPDHCPRSLTLSTIMAGRP

WRFD-050304


Meaning: Indicates the length of the frame used for datatransmission on the IMA link in the IMA group. A largervalue of this parameter results in higher efficiency butlower sensitivity to bit errors.GUI Value Range: D32(D32), D64(D64), D128(D128),D256(D256)Unit: NoneActual Value Range: D32, D64, D128, D256Default Value: D128(D128)



57

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description



WRFD-050304


Meaning: Indicates whether scrambling is applied to theIMA group.GUI Value Range: DISABLE(Disable), ENABLE(Enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: ENABLE(Enable)

TS16 BTS3900,BTS3900WCDMA


WRFD-050304


Meaning: Indicates whether to enable E1 timeslot 16.GUI Value Range: DISABLE(Disable), ENABLE(Enable)Unit: NoneActual Value Range: DISABLE, ENABLEDefault Value: DISABLE(Disable)

SRCPORTNO

BSC6900

ADDTSCROSS

None None Meaning: Source of timeslot crossGUI Value Range: 0~335Unit: NoneActual Value Range: 0~335Default Value: None



58

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

SRCTSMASK

BSC6900

ADDTSCROSS

None None Meaning: Source timeslot mask.GUI Value Range: TS1(Time_slot_1), TS2(Time_slot_2), TS3(Time_slot_3), TS4(Time_slot_4),TS5(Time_slot_5), TS6(Time_slot_6), TS7(Time_slot_7), TS8(Time_slot_8), TS9(Time_slot_9),TS10(Time_slot_10), TS11(Time_slot_11), TS12(Time_slot_12), TS13(Time_slot_13), TS14(Time_slot_14), TS15(Time_slot_15), TS16(Time_slot_16), TS17(Time_slot_17), TS18(Time_slot_18), TS19(Time_slot_19), TS20(Time_slot_20), TS21(Time_slot_21), TS22(Time_slot_22), TS23(Time_slot_23), TS24(Time_slot_24), TS25(Time_slot_25), TS26(Time_slot_26), TS27(Time_slot_27), TS28(Time_slot_28), TS29(Time_slot_29), TS30(Time_slot_30), TS31(Time_slot_31)Unit: NoneActual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15,TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23,TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31Default Value: None

DSTPORTNO

BSC6900

ADDTSCROSS

None None Meaning: Destination of the timeslot cross connectionGUI Value Range: 0~335Unit: NoneActual Value Range: 0~335Default Value: None



59

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

DSTTSMASK

BSC6900

ADDTSCROSS

None None Meaning: Target timeslot maskGUI Value Range: TS1(Time_slot_1), TS2(Time_slot_2), TS3(Time_slot_3), TS4(Time_slot_4),TS5(Time_slot_5), TS6(Time_slot_6), TS7(Time_slot_7), TS8(Time_slot_8), TS9(Time_slot_9),TS10(Time_slot_10), TS11(Time_slot_11), TS12(Time_slot_12), TS13(Time_slot_13), TS14(Time_slot_14), TS15(Time_slot_15), TS16(Time_slot_16), TS17(Time_slot_17), TS18(Time_slot_18), TS19(Time_slot_19), TS20(Time_slot_20), TS21(Time_slot_21), TS22(Time_slot_22), TS23(Time_slot_23), TS24(Time_slot_24), TS25(Time_slot_25), TS26(Time_slot_26), TS27(Time_slot_27), TS28(Time_slot_28), TS29(Time_slot_29), TS30(Time_slot_30), TS31(Time_slot_31)Unit: NoneActual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15,TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23,TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31Default Value: None



60

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TRFX BSC6900

ADDATMTRFMODATMTRFRMVATMTRF


HSDPAIntroductionPackageUBR+ATMQoSClassATMTransmissionIntroductionPackageE-DPCCHBoosting

Meaning: Traffic index. ATM traffic record indexes areused by the upper layers of the ATM layer. The upperlayers consist of the SAAL link, AAL2 path, and IPoAPVC. Each ATM traffic record is uniquely numberedwithin a RNC by using an ATM traffic record index. AnATM traffic record index ranges from 100 to 1999 (1 to99 are reserved for internal use). The numbering is notnecessarily consecutive. Specify different numberranges for different interfaces. For example, specify therange of 100 to 199 for ATM traffic record indexes overIub, the range of 200 to 299 for ATM traffic recordindexes over Iur, the range of 300 to 399 for ATM trafficrecord indexes over Iu-CS, and the range of 400 to 499for ATM traffic record indexes over Iu-PS. Specifydifferent ranges of ATM traffic record indexes fordifferent links over an interface. For example, over theIub interface, specify the range of 100 to 149 for ATMtraffic record indexes of SAAL links, the range of 150to 179 for ATM traffic record indexes of AAL2 paths,and the range of 180 to 189 for ATM traffic recordindexes of IPoA PVCs.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



61

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TRFX BSC6910

ADDATMTRFMODATMTRFRMVATMTRF

WRFD-010610WRFD-010697

HSDPAIntroductionPackageE-DPCCHBoosting

Meaning: Traffic index. ATM traffic record indexes areused by the upper layers of the ATM layer. The upperlayers consist of the SAAL link, AAL2 path, and IPoAPVC. Each ATM traffic record is uniquely numberedwithin a RNC by using an ATM traffic record index. AnATM traffic record index ranges from 100 to 1999 (1 to99 are reserved for internal use). The numbering is notnecessarily consecutive. Specify different numberranges for different interfaces. For example, specify therange of 100 to 199 for ATM traffic record indexes overIub, the range of 200 to 299 for ATM traffic recordindexes over Iur, and the range of 300 to 399 for ATMtraffic record indexes over Iu-CS. Specify differentranges of ATM traffic record indexes for different linksover an interface. For example, over the Iub interface,specify the range of 100 to 149 for ATM traffic recordindexes of SAAL links, the range of 150 to 179 for ATMtraffic record indexes of AAL2 paths, and the range of180 to 189 for ATM traffic record indexes of IPoAPVCs.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None

ST BSC6900

ADDATMTRF



Meaning: Service type of the ATM. When traffic indexis used by the SAAL, IPoA PVC, VPCLCX link, orAAL2 path of the AOUc/UOIc board, the service typeUBR and UBR_PLUS must be configured with thePCR.GUI Value Range: UBR_PLUS, UBR, NRTVBR,RTVBR, CBRUnit: NoneActual Value Range: UBR_PLUS, UBR, NRTVBR,RTVBR, CBRDefault Value: None



62

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

ST BSC6910

ADDATMTRF

WRFD-010610WRFD-010697


Meaning: Service type of the ATM. When traffic indexis used by the SAAL, IPoA PVC, or AAL2 path of theAOUc/UOIc board, the service type UBR andUBR_PLUS must be configured with the PCR.GUI Value Range: UBR_PLUS, UBR, NRTVBR,RTVBR, CBRUnit: NoneActual Value Range: UBR, CBR, RTVBR, NRTVBR,UBR_PLUSDefault Value: None

UT BSC6900

ADDATMTRF

WRFD-010610WRFD-050305WRFD-010697WRFD-050301WRFD-05030107

HSDPAIntroductionPackageUBR+ATMQoSClassE-DPCCHBoostingATMTransmissionIntroductionPackageCBR, rt-VBR,nrt-VBR,UBRATMQoSClasses

Meaning: Rate unit.GUI Value Range: CELL/S, KBIT/SUnit: NoneActual Value Range: CELL/S, KBIT/SDefault Value: None



63

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

UT BSC6910

ADDATMTRF



Meaning: Rate unit.GUI Value Range: CELL/S, KBIT/SUnit: NoneActual Value Range: CELL/S, KBIT/SDefault Value: None



64

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

PCR BSC6900

ADDATMTRF



Meaning: Peak rate of the ATM traffic. When the ATMtraffic record indexes corresponding to the service typeUBR, RTVBR or NRTVBR are used by AOUa, AEUaor UOIa(ATM), the peak cell rate (PCR), if configured,must be lower than 60000 KBIT/S or 141510 CELL/S.GUI Value Range: 30~353207Unit: NoneActual Value Range: 30~353207Default Value: None



65

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

PCR BSC6910

ADDATMTRF



Meaning: Peak rate of the ATM traffic.GUI Value Range: 30~353207Unit: NoneActual Value Range: 30~353207Default Value: None



66

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

SCR BSC6900

ADDATMTRF



Meaning: Maximum average cell rate of a VBR servicesource. The VBR is short for Variable Bit Rate. Theaverage cell rate is the average value of cell rates for aservice source on a physical service access point (PHY-SAP) within a period of time. This parameter iscalculated using the following formula: SCR = 1/Ts,where, Ts indicates the minimum average intervalbetween sending ATM cells.GUI Value Range: 30~353207Unit: NoneActual Value Range: 30~353207Default Value: None



67

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

SCR BSC6910

ADDATMTRF



Meaning: Maximum average cell rate of a VBR servicesource. The VBR is short for Variable Bit Rate. Theaverage cell rate is the average value of cell rates for aservice source on a physical service access point (PHY-SAP) within a period of time. This parameter iscalculated using the following formula: SCR = 1/Ts,where, Ts indicates the minimum average intervalbetween sending ATM cells.GUI Value Range: 30~353207Unit: NoneActual Value Range: 30~353207Default Value: None



68

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

MCR BSC6900

ADDATMTRF



Meaning: Minimum guarantee rate of the ATMtraffic.The "Minimum cell rate" of the AOUc or UOIcboard cannot be greater than 13.8 Mbit/s.GUI Value Range: 30~70754Unit: NoneActual Value Range: 30~70754Default Value: None



69

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

MCR BSC6910

ADDATMTRF



Meaning: Minimum guarantee rate of the ATMtraffic.The "Minimum cell rate" of the AOUc or UOIcboard cannot be greater than 13.8 Mbit/s.GUI Value Range: 30~70754Unit: NoneActual Value Range: 30~70754Default Value: None

MBS BSC6900

ADDATMTRF



Meaning: Maximum burst size (MBS). For details aboutthis parameter, see TM4.1 protocol.GUI Value Range: 3~10000Unit: cell/sActual Value Range: 3~10000Default Value: None



70

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

MBS BSC6910

ADDATMTRF

WRFD-010610WRFD-010697


Meaning: Maximum burst size (MBS). For details aboutthis parameter, see TM4.1 protocol.GUI Value Range: 3~10000Unit: cell/sActual Value Range: 3~10000Default Value: None

CDVT BSC6900

ADDATMTRF



Meaning: Tolerable delay jitter. For details about thisparameter, see TM4.1 protocol.GUI Value Range: 1024~212000Unit: 100nsActual Value Range: 102400~21200000Default Value: 1024

CDVT BSC6910

ADDATMTRF

WRFD-010610WRFD-010697


Meaning: Tolerable delay jitter. For details about thisparameter, see TM4.1 protocol.GUI Value Range: 1024~212000Unit: 100nsActual Value Range: 102400~21200000Default Value: 1024

CDVT BTS3900,BTS3900WCDMA

ADDAAL2PATHMODAAL2PATHLSTAAL2PATH

WRFD-05030104

Dynamic AAL2Connections inIub/IuCS/IurInterface

Meaning: Indicates the cell delay variation tolerance.The value of this parameter is subject to the actualnetwork. Setting the parameter to an improper valueaffects the service quality.

GUI Value Range: 1024~13300000

Unit: 0.1microsecond

Actual Value Range: 102.4~1330000, step:0.1

Default Value: 10240



71

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

REMARK

BSC6900

ADDATMTRFMODATMTRF

None None Meaning: Purpose description of the ATM traffic record

GUI Value Range: 0~255 characters

Unit: None

Actual Value Range: 0~255 characters

Default Value: -

REMARK

BSC6910

ADDATMTRFMODATMTRF

WRFD-010610WRFD-010697


Meaning: Purpose description of the ATM traffic recordGUI Value Range: 0~255 charactersUnit: NoneActual Value Range: 0~255 charactersDefault Value: -

TXTRFX

BSC6900

ADDSAALLNKMODSAALLNK

WRFD-05030105WRFD-050301

Permanent AAL5Connections forControlPlaneTrafficATMTransmissionIntroductionPackage

Meaning: TX traffic record index of the SAAL link.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None

TXTRFX

BSC6910


WRFD-05030105WRFD-050301


Meaning: TX traffic record index of the SAAL link.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



72

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

RXTRFX

BSC6900


WRFD-05030105WRFD-050301


Meaning: RX traffic record index of the SAAL link.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None

RXTRFX

BSC6910


WRFD-05030105WRFD-050301


Meaning: RX traffic record index of the SAAL link.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None

CARRYVPI

BSC6900


WRFD-050404WRFD-05030105WRFD-050301

ATM/IPDualStackNode BPermanent AAL5Connections forControlPlaneTrafficATMTransmissionIntroductionPackage

Meaning: VPI value of the SAAL out RNC.GUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None



73

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

CARRYVPI

BSC6910


WRFD-050404WRFD-05030105WRFD-050301


Meaning: VPI value of the SAAL out RNC.GUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None

CARRYVCI

BSC6900


WRFD-050404WRFD-05030105WRFD-050301


Meaning: VCI value of the SAAL out RNC.GUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None



74

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

CARRYVCI

BSC6910


WRFD-050404WRFD-05030105WRFD-050301


Meaning: VCI value of the SAAL out RNC.GUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None

VPI BTS3900,BTS3900WCDMA

ADDSAALLNKLSTSAALLNK

WRFD-05030101WRFD-05030103

ATMoverE1T1 onIubInterfaceATMoverNon-channelizedSTM-1/OC-3con Iub/Iu/IurInterface

Meaning: Indicates the Virtual Path Identifier (VPI),which is used for VP routing. A virtual path containsmultiple virtual channels.GUI Value Range: 0~255Unit: NoneActual Value Range: 0~255Default Value: None



75

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

VCI BTS3900,BTS3900WCDMA

ADDSAALLNKLSTSAALLNK

WRFD-05030101WRFD-05030103

ATMoverE1T1 onIubInterfaceATMoverNon-channelizedSTM-1/OC-3con Iub/Iu/IurInterface

Meaning: Indicates the Virtual Channel Identifier(VCI), which is used for VC routing.GUI Value Range: 32~511Unit: NoneActual Value Range: 32~511Default Value: None

PATHID

BSC6900

ADDAAL2PATH

BLKAAL2PATH

MODAAL2PATH

RMVAAL2PATH

UBLAAL2PATH

WRFD-05030104WRFD-050404WRFD-02130501

Dynamic AAL2Connections inIub/IuCS/IurInterfaceATM/IPDualStackNode BDedicated IubTransmissionControl

Meaning: ID of one AAL2 path between two AAL2nodes. The PATHID of the same AAL2 path configuredbetween two AAL2 nodes must be the same. The valueshould not be equal to 0.GUI Value Range: 1~4294967295Unit: NoneActual Value Range: 1~4294967295Default Value: None



76

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

PATHID

BSC6910

ADDAAL2PATH

BLKAAL2PATH

MODAAL2PATH

RMVAAL2PATH

UBLAAL2PATH

WRFD-05030104WRFD-050404WRFD-02130501

Dynamic AAL2Connections inIub/IuCS/IurInterfaceATM/IPDualStackNode BDedicated IubTransmissionControl

Meaning: ID of one AAL2 path between two AAL2nodes. The PATHID of the same AAL2 path configuredbetween two AAL2 nodes must be the same. The valueshould not be equal to 0.GUI Value Range: 1~4294967295Unit: NoneActual Value Range: 1~4294967295Default Value: None



77

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TXTRFX

BSC6900

ADDAAL2PATHMODAAL2PATH


Overbooking onATMTransmissionATMQoSIntroduction onHubNode B(Overbooking onHubNode BTransmission)Dedicated IubTransmissionControlDynamic AAL2Connections inIub/IuCS/IurInterfaceCallAdmissionBasedon UsedAAL2PathBandwidthCBR, rt-VBR,nrt-VBR,UBRATM

Meaning: TX traffic record index of the AAL2 Path onthe out RNC port (ATM layer PVC traffic). The trafficindex is configured in the ATM traffic table (see "LSTATMTRF").GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



78

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

QoSClasses



79

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TXTRFX

BSC6910




Meaning: TX traffic record index of the AAL2 Path onthe out RNC port (ATM layer PVC traffic). The trafficindex is configured in the ATM traffic table (see "LSTATMTRF").GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



80

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

QoSClasses



81

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

RXTRFX

BSC6900




Meaning: RX traffic record index of the AAL2 Path onthe out RNC port (ATM layer PVC traffic). The trafficindex is configured in the ATM traffic table (see "LSTATMTRF").GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



82

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

QoSClasses



83

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

RXTRFX

BSC6910




Meaning: RX traffic record index of the AAL2 Path onthe out RNC port (ATM layer PVC traffic). The trafficindex is configured in the ATM traffic table (see "LSTATMTRF").GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



84

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

QoSClasses

VPI BSC6900



Dedicated IubTransmissionControlDynamic AAL2Connections inIub/IuCS/IurInterfaceATMTransmissionIntroductionPackageCallAdmissionBasedon UsedAAL2PathBandwidth

Meaning: VPI of the AAL2 path out RNC. When theAAL2 path is carried on the UOIa, AOUa, AEUa, orAOUc board, the value for Bearing VPI ranges from 0to 255. When the AAL2 path is carried on the UOIcboard, the value for Bearing VPI ranges from 0 to 255if WORKTYPE in the "SET OPT" command is set to"UNI"; the value for Bearing VPI ranges from 0 to 4095if WORKTYPE in the "SET OPT" command is set to"NNI".GUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None



85

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

VPI BSC6910



Dedicated IubTransmissionControlDynamic AAL2Connections inIub/IuCS/IurInterfaceATMTransmissionIntroductionPackageCallAdmissionBasedon UsedAAL2PathBandwidth

Meaning: VPI of the AAL2 path out RNC. When theAAL2 path is carried on the AOUc board, the value forBearing VPI ranges from 0 to 255. When the AAL2 pathis carried on the UOIc board, the value for Bearing VPIranges from 0 to 255 if WORKTYPE in the "SET OPT"command is set to "UNI"; the value for Bearing VPIranges from 0 to 4095 if WORKTYPE in the "SETOPT" command is set to "NNI".GUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None

VCI BSC6900


WRFD-02130501WRFD-050404WRFD-050301

Dedicated IubTransmissionControlATM/IPDualStackNode BATMTransmissionIntroductionPackage

Meaning: VCI of the AAL2 path out RNC.GUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None



86

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

VCI BSC6910


WRFD-02130501WRFD-050404WRFD-050301

Dedicated IubTransmissionControlATM/IPDualStackNode BATMTransmissionIntroductionPackage

Meaning: VCI of the AAL2 path out RNC.GUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None

SIGLKSX

BSC6900

ACTMTP3LNKADDMTP3LNKDEAMTP3LNKINHMTP3LNKMODMTP3LNKRMVMTP3LNKUINMTP3LNK

WRFD-050301


Meaning: Uniquely identifies a signaling link set. MTP3signaling link sets are uniquely but not necessarilyconsecutively numbered within a RNC by using thesignaling link set index. For example, you can set thenumber of an MTP3 signaling link set towards aneighboring MGW to 10 and the number of an MTP3signaling link set towards another neighboring MGW to12.GUI Value Range: 0~186Unit: NoneActual Value Range: 0~186Default Value: None



87

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

SIGLKSX

BSC6910

ACTMTP3LNKADDMTP3LNKDEAMTP3LNKINHMTP3LNKMODMTP3LNKRMVMTP3LNKUINMTP3LNK

WRFD-050301


Meaning: Uniquely identifies a signaling link set. MTP3signaling link sets are uniquely but not necessarilyconsecutively numbered within a RNC by using thesignaling link set index. For example, you can set thenumber of an MTP3 signaling link set towards aneighboring MGW to 10 and the number of an MTP3signaling link set towards another neighboring MGW to12.GUI Value Range: 0~427Unit: NoneActual Value Range: 0~427Default Value: None

PEERT BSC6900

ADDIPOAPVC

WRFD-05030105WRFD-050301


Meaning: IPoA PVC peer typeGUI Value Range: IUB, IUPS, OTHERUnit: NoneActual Value Range: IUB, IUPS, OTHERDefault Value: None



88

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

PEERT BSC6910

ADDIPOAPVC

WRFD-05030105WRFD-050301


Meaning: IPoA PVC peer type.GUI Value Range: IUB, OTHERUnit: NoneActual Value Range: IUB, OTHERDefault Value: None

CARRYVPI

BSC6900

ADDIPOAPVCMODIPOAPVC



Meaning: VPI value of the VCL of the bearer networkGUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None



89

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

CARRYVPI

BSC6910




Meaning: VPI value of the VCL of the bearer networkGUI Value Range: 0~4095Unit: NoneActual Value Range: 0~4095Default Value: None

CARRYVCI

BSC6900




Meaning: VCI value of the VCL of the bearer networkGUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None



90

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

CARRYVCI

BSC6910




Meaning: VCI value of the VCL of the bearer networkGUI Value Range: 32~65535Unit: NoneActual Value Range: 32~65535Default Value: None

TXTRFX

BSC6900


WRFD-05030105WRFD-050301


Meaning: Sending traffic index.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



91

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

TXTRFX

BSC6910


WRFD-05030105WRFD-050301


Meaning: Sending traffic index.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None

RXTRFX

BSC6900


WRFD-050107WRFD-05030105WRFD-050301

IProutingBasedHubNode BPermanent AAL5Connections forControlPlaneTrafficATMTransmissionIntroductionPackage

Meaning: Receiving traffic index.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



92

Parameter ID

NE MMLCommand

FeatureID

FeatureName

Description

RXTRFX

BSC6910


WRFD-050107WRFD-05030105WRFD-050301

IProutingBasedHubNode BPermanent AAL5Connections forControlPlaneTrafficATMTransmissionIntroductionPackage

Meaning: Receiving traffic index.GUI Value Range: 100~1999Unit: NoneActual Value Range: 100~1999Default Value: None



93

8 Counters

Table 8-1 Counter description

Counter ID Counter Name CounterDescription

NE Feature ID Feature Name

1542455312 VS.E1T1.CodeViolate

Number of CodeType Errors onthe E1/T1Electrical Port

NodeB Multi-mode:NoneGSM:GBFD-118611UMTS:WRFD-05030101WRFD-050402LTE: None

Abis IP over E1/T1ATM over E1T1on Iub InterfaceIP TransmissionIntroduction onIub Interface

1542455313 VS.E1T1.FramingError

Number of BaseFrameAlignmentErrors on the E1/T1 ElectricalPort



WCDMA RANATM Transport Feature Parameter Description 8 Counters


94



1542455314 VS.E1T1.CrcError

Number of CRCErrors on the E1/T1 ElectricalPort



1542455315 VS.E1T1.EbitError

Number of EbitErrors on the E1/T1 Port



1542455316 VS.E1T1.Sa6Error

Number of Sa6Errors on the E1/T1 Port



1542455320 VS.E1T1.Multi-frame

Number ofmultiframecycles at the E1/T1 port





95



1542455321 VS.E1T1.FrameAlignChanged

Number ofTimes thatFrames Are NotAligned



1542455866 VS.E1T1.ES.TES

Total ErroredSeconds in theTX Direction



1542455867 VS.E1T1.ES.TSES

Total SeverelyErrored Secondsin the TXDirection



1542455868 VS.E1T1.ES.TUAS

TotalUnavailableSeconds in theTX Direction





96



1542455869 VS.E1T1.ES.RES

Total ErroredSeconds in theRX Direction



1542455870 VS.E1T1.ES.RSES

Total SeverelyErrored Secondsin the RXDirection



1542455871 VS.E1T1.ES.RUAS

TotalUnavailableSeconds in theRX Direction



1542455884 VS.AAL2PATH.RxPkts

Number ofpacketssuccessfullyreceived on theAAL2 Path

NodeB Multi-mode:NoneGSM: NoneUMTS:WRFD-05030104LTE: None

Dynamic AAL2connection onIub/IuCS/IurInterface



97



1542455885 VS.AAL2PATH.TxPkts

Number ofpacketssuccessfullytransmitted onthe AAL2 Path



1542455886 VS.AAL2PATH.TxDropPkts

Number ofdiscardedpacketstransmitted onthe AAL2 Path



1542455887 VS.AAL2PATH.RxDropPkts

Number ofdiscardedpackets receivedon the AAL2Path



1542455888 VS.SAALAAL5.RxPkts

Number ofpackets receivedon the SAALAAL5 link


AAL5permanentconnection oncontrol surfacesbusiness

1542455889 VS.SAALAAL5.TxPkts

Number ofpacketstransmitted onthe SAALAAL5 link





98



1542455890 VS.SAALAAL5.RxDropPkts

Number ofdiscardedpackets receivedon the SAALAAL5 link



1542455891 VS.SAALAAL5.TxDropPkts

Number ofdiscardedpacketstransmitted onthe SAALAAL5 link



1542455892 VS.SAALAAL5.TxCells

Number of cellstransmitted onthe SAALAAL5 link



1542455893 VS.SAALAAL5.RxCells

Number of cellsreceived on theSAAL AAL5link



1542455894 VS.SAAL.ToAAL5Pkts

Number ofpacketssuccessfullyreceived to theAAL5 layer onthe SAAL link





99



1542455895 VS.SAAL.ToAAL5DropPkts

Number ofdiscardedpackets receivedto the AAL5layer on theSAAL link



1542455896 VS.SAAL.FromAAL5Pkts

Number ofpacketssuccessfullyreceived fromthe AAL5 layeron the SAALlink



1542455897 VS.SAAL.FromAAL5DropPkts

Number ofdiscardedpackets receivedfrom the AAL5layer on theSAAL link



1542455898 VS.SAAL.FromUserPkts

Number ofpackets receivedfrom the userlayer on theSAAL link



1542455899 VS.SAAL.ToU-serPkts

Number ofpacketssuccessfullytransmitted tothe user layer onthe SAAL link





100



1542455900 VS.SAAL.ToUserFailedNumber

Number ofpackets failed tobe transmitted tothe user layer onthe SAAL link



1542455901 VS.IMAGRP.TxDropCells

Number ofdiscarded cellstransmitted onthe IMAGRP


IMA over E1T1or STM-1/OC-3on Iub Interface

1542455902 VS.IMAGRP.TxCells

Number of usercells transmittedon the IMAGRP



1542455903 VS.IMAGRP.RxCells

Number of usercells received onthe IMAGRP



1542455904 VS.IMAGRP.RxDropCells

Number ofdiscarded cellsreceived on theIMAGRP



1542455905 VS.IPOAAAL5.RxPkts

Number ofpackets receivedon the IPOAAAL5 link





101



1542455906 VS.IPOAAAL5.TxPkts

Number ofpacketstransmitted onthe IPOA AAL5link



1542455907 VS.IPOAAAL5.RxDropPkts

Number ofdiscardedpackets receivedon the IPOAAAL5 link



1542455908 VS.IPOAAAL5.TxDropPkts

Number ofdiscardedpacketstransmitted onthe IPOA AAL5link



1542455909 VS.IPOAAAL5.TxCells

Number of cellstransmitted onthe IPOA AAL5link



1542455910 VS.IPOAAAL5.RxCells

Number of cellsreceived on theIPOA AAL5link





102



50332673 VS.ATMUlTotal.1

ATM physicalport_1 uplinktotal bandwidth

NodeB Multi-mode:NoneGSM: NoneUMTS:WRFD-05030101WRFD-05030102LTE: None

ATM over E1T1on Iub InterfaceATM overChannelizedSTM-1/OC-3 onIub Interface

50332674 VS.ATMUlMaxUsed.1

ATM physicalport_1 uplinkmaximum usedbandwidth



50332675 VS.ATMUlAvgUsed.1

ATM physicalport_1 uplinkaverage usedbandwidth



50332676 VS.ATMDlTotal.1

ATM physicalport_1 downlinktotal bandwidth





103



50332677 VS.ATMDlMaxUsed.1

ATM physicalport_1 downlinkmaximum usedbandwidth



50332678 VS.ATMDlAvgUsed.1

ATM physicalport_1 downlinkaverage usedbandwidth













104





















105





















106












ATM physicalport uplink totalbandwidth









107





















108



67182593 VS.SAAL.LnkServDur.Time

In-ServiceDuration ofSAAL Link

BSC6900 WRFD-05030105

PermanentAAL5Connections forControl PlaneTraffic

67182594 VS.SAAL.FailLnk.AllReasons

Number ofSAAL LinkFailures (AllCauses)

BSC6900 WRFD-05030105


67182595 VS.SAAL.FailLnk.NoRspTimExp

Number ofSAAL Failures(Timer Expires)

BSC6900 WRFD-05030105


67182596 VS.SAAL.FailLnk.ExcesErr.Rat

Number ofSAAL Failures(Over-HighBER)

BSC6900 WRFD-05030105


67182597 VS.SAAL.FailLnk.ExcesNoCred

Number ofSAAL LinkFailures(Congestion)

BSC6900 WRFD-05030105


67182598 VS.SAAL.FailLnk.AlignFail

Number ofSAAL LinkAlignmentFailures

BSC6900 WRFD-05030105


67182599 VS.SAAL.LnkErr.SDRetransTx

Number ofSAAL LinkMAA-ERRORIndications(SDLOSS_TX)

BSC6900 WRFD-05030105


67182600 VS.SAAL.LnkErr.PDUInval

Number ofSAAL LinkMAA-ERRORIndications(Invalid PDU)

BSC6900 WRFD-05030105




109



67182601 VS.SAAL.LnkErr.OthReasons

Number ofSAAL LinkMAA-ERRORIndications(Others)

BSC6900 WRFD-05030105


67182602 VS.SAAL.LnkErr.RetransFail

Number ofSAAL LinkMAA-ERRORIndicationsReceived(UnsuccessfulRetransmission)

BSC6900 WRFD-05030105


67183361 VS.QAAL2.ERQ.Tx

Number ofAAL2ConnectionEstablishmentRequests Sentby the QAAL2

BSC6900 WRFD-05030104


67183362 VS.QAAL2.ERQ.Rx

Number ofAAL2ConnectionEstablishmentRequestsReceived by theQAAL2

BSC6900 WRFD-05030104


67183363 VS.QAAL2.Est.RLC.Rx

Number ofAAL2ConnectionReleaseConfirmations(RLCs)Received by theQAAL2 Afterthe QAAL2Sends the ERQMessage

BSC6900 WRFD-05030104


67183364 VS.QAAL2.Est.ECF.Rx

Number of ECFMessagesReceived by theQAAL2 Afterthe QAAL2Sends the ERQMessage

BSC6900 WRFD-05030104




110



67183365 VS.QAAL2.Est.ECF.Tx

Number of ECFMessages Sentby the QAAL2After theQAAL2Receives theERQ Message

BSC6900 WRFD-05030104


67183366 VS.QAAL2.Est.RLC.Tx

Number of RLCMessages Sentby the QAAL2After theQAAL2Receives theERQ Message

BSC6900 WRFD-05030104


67183367 VS.QAAL2.Rel.Tx

Number ofAAL2ConnectionReleaseRequests(RELs) Sent bythe QAAL2

BSC6900 WRFD-05030104


67183368 VS.QAAL2.Rel.Rx

Number ofAAL2ConnectionReleaseRequests(RELs)Received by theQAAL2

BSC6900 WRFD-05030104


67183369 VS.QAAL2.Rel.RLC.Rx

Number ofAAL2ConnectionReleaseConfirmations(RLCs)Received by theQAAL2 Afterthe QAAL2Sends the RELMessage

BSC6900 WRFD-05030104




111



67183370 VS.QAAL2.Rel.RLC.Tx

Number of RLCMessages Sentby the QAAL2After theQAAL2Receives theREL Message

BSC6900 WRFD-05030104


67190053 VS.AAL2.CAC.Att

Number ofAAL2 PathResourceAdmissions

BSC6900 WRFD-05030106

Call AdmissionBased on UsedAAL2 PathBandwidth

67190054 VS.AAL2.CAC.Succ

Number ofSuccessfulAAL2 PathAdmissions

BSC6900 WRFD-05030106


67190055 VS.QAAL2.Est.RLC.NoRoute.Rx

Number of RLCMessagesReceived by theQAAL2 Due toNo Route at theRemote End

BSC6900 WRFD-05030104


67190056 VS.QAAL2.Est.RLC.NoPath.Rx

Number of RLCMessagesReceived byQAAL2 Due toNo AAL2 PathConfigued at theRemote End

BSC6900 WRFD-05030104


67190057 VS.QAAL2.Est.RLC.NoCID.Rx

Number of RLCMessagesReceived byQAAL2 Due toNo CIDAvailable at theRemote End

BSC6900 WRFD-05030104




112



67190058 VS.QAAL2.Est.RLC.Fail.Rx

Number of RLCMessagesReceived byQAAL2 Due toRemoteNetwork Fault,RemoteTemporaryFailure, orRemote NormalReleases

BSC6900 WRFD-05030104


67190059 VS.QAAL2.Est.RLC.Cong.Rx

Number of RLCMessagesReceived byQAAL2 Due toSwitchCongestion atthe Remote End

BSC6900 WRFD-05030104


67190060 VS.QAAL2.Est.RLC.RecovOut.Rx

Number of RLCMessagesReceived byQAAL2 Due toTimer Expiry atthe Remote End

BSC6900 WRFD-05030104


67190061 VS.QAAL2.Est.RLC.NoRoute.Tx

Number of RLCMessages Sentby the QAAL2Due to No Routeat the RemoteEnd

BSC6900 WRFD-05030104


67190062 VS.QAAL2.Est.RLC.NoPath.Tx

Number of RLCMessages Sentby the QAAL2Due to NoAAL2 PathConfigured

BSC6900 WRFD-05030104


67190063 VS.QAAL2.Est.RLC.NoCID.Tx

Number of RLCMessages Sentby the QAAL2Due to No CIDAvailable

BSC6900 WRFD-05030104




113



67190064 VS.QAAL2.Est.RLC.Fail.Tx

Number of RLCMessages Sentby the QAAL2Due to NetworkFailure,UnspecifiedReason, orTemporaryFailure

BSC6900 WRFD-05030104


67190065 VS.QAAL2.Est.RLC.Cong.Tx

Number of RLCMessages Sentby QAAL2 Dueto SwitchCongestion

BSC6900 WRFD-05030104


67190066 VS.QAAL2.Est.RLC.RecovOut.Tx

Number of RLCMessages Sentby QAAL2 Dueto Timer Expiry

BSC6900 WRFD-05030104


67190067 VS.QAAL2.RxModRej

Number ofAAL2ConnectionModificationRejections(MORs)Received by theQAAL2

BSC6900 WRFD-05030104


67190068 VS.QAAL2.TxModRej

Number ofMOR MessagesSent by theQAAL2 Afterthe QAAL2Receives theMOD Message

BSC6900 WRFD-05030104


67190490 VS.UNILNK.RXCELLS

Number of CellsReceived on aUNI Link

BSC6900 WRFD-05030101

ATM over E1T1on Iub Interface

67190491 VS.UNILNK.TXCELLS

Number of CellsTransmitted on aUNI Link

BSC6900 WRFD-05030101




114



67190553 VS.QAAL2.TxMod

Number ofAAL2ConnectionModificationRequests(MODs) Sent bythe QAAL2

BSC6900 WRFD-05030104


67190554 VS.QAAL2.RxMod

Number ofAAL2ConnectionModificationRequests(MODs)Received by theQAAL2

BSC6900 WRFD-05030104


67190555 VS.QAAL2.AllocedFwd.AAL2BitRate

Mean ForwardBandwidth ofAAL2 PathAllocated to anAdjacent Node

BSC6900 WRFD-05030106


67190558 VS.QAAL2.AllocedBwd.AAL2BitRate

Mean BackwardBandwidth ofAAL2 PathAllocated to anAdjacent Node

BSC6900 WRFD-05030106


67190562 VS.QAAL2.AllocedMaxFwd.AAL2BitRate.Value

MaximumValue of AAL2Path ForwardBandwidthAllocated to anAdjacent Node

BSC6900 WRFD-05030106


67190565 VS.QAAL2.AllocedMaxBwd.AAL2BitRate.Value

MaximumValue of AAL2Path BackwardBandwidthAllocated to anAdjacent Node

BSC6900 WRFD-05030106


67190615 VS.AAL5.SAALLnk.BytesRx

Number ofBytes Receivedby SAAL Link

BSC6900 WRFD-05030105




115



67190616 VS.AAL5.SAALLnk.BytesTx

Number ofBytes Sent bySAAL Link

BSC6900 WRFD-05030105


67193215 VS.IMAGRP.Alloced.Max.Fwd

MaximumOccupiedForwardBandwidth of anIMA Group

BSC6900 WRFD-05030106


67193216 VS.IMAGRP.Alloced.Max.Bwd

MaximumOccupiedBackwardBandwidth of anIMA Group

BSC6900 WRFD-05030106


67193217 VS.IMAGRP.Fwd.Cong

Number ofForwardCongestions onan IMA Group

BSC6900 WRFD-05030106


67193218 VS.IMAGRP.Fwd.Cong.Dur

Duration ofForwardCongestions onan IMA Group

BSC6900 WRFD-05030106


67193219 VS.IMAGRP.Bwd.Cong

Number ofBackwardCongestions onan IMA Group

BSC6900 WRFD-05030106


67193220 VS.IMAGRP.Bwd.Cong.Dur

Duration ofBackwardCongestions onan IMA Group

BSC6900 WRFD-05030106


67193235 VS.UNILNK.Alloced.Max.Fwd

MaximumForwardBandwidthAllocated forUNI Link

BSC6900 WRFD-05030106


67193236 VS.UNILNK.Alloced.Max.Bwd

MaximumBackwardBandwidthAllocated forUNI Link

BSC6900 WRFD-05030106




116



67193237 VS.UNILNK.Fwd.Cong

Number of UNILink ForwardCongestions

BSC6900 WRFD-05030106


67193238 VS.UNILNK.Fwd.Cong.Dur

Duration of UNILink ForwardCongestions

BSC6900 WRFD-05030106


67193239 VS.UNILNK.Bwd.Cong

Number of UNILink BackwardCongestions

BSC6900 WRFD-05030106


67193240 VS.UNILNK.Bwd.Cong.Dur

Duration of UNILink BackwardCongestions

BSC6900 WRFD-05030106


67193989 VS.FRACATMLNK.TXCELLS

Number of CellsTransmitted onan FractionalATM Link

BSC6900 WRFD-050302 Fractional ATMFunction on IubInterface

67193991 VS.FRACATMLNK.RXCELLS

Number of CellsReceived on anFractional ATMLink


67193993 VS.FRACATMLNK.RXHCSERRCELLS

Number of ErrorCells Receivedon an FractionalATM Link


67193994 VS.FRACATMLNK.RXDROPPEDCELLS

Number of CellsDiscarded on anFractional ATMLink


67193995 VS.FRACATMLNK.TXMAXSPEED

MaximumTransmit Rate ofan FractionalATM Link


67193996 VS.FRACATMLNK.TXMINSPEED

MinimumTransmit Rate ofan FractionalATM Link




117



67193997 VS.FRACATMLNK.TXMEANSPEED

Mean TransmitRate of anFractional ATMLink


67193998 VS.FRACATMLNK.RXMAXSPEED

MaximumReceive Rate ofan FractionalATM Link


67193999 VS.FRACATMLNK.RXMINSPEED

MinimumReceive Rate ofan FractionalATM Link


67194000 VS.FRACATMLNK.RXMEANSPEED

Mean ReceiveRate of anFractional ATMLink


67194002 VS.FRACIMALNK.TXUSERCELLS

Number of UserCellsTransmitted onan FractionalIMA Link


67194003 VS.FRACIMALNK.TXSTUFFCELLS

Number ofFilling CellsTransmitted onan FractionalIMA Link


67194005 VS.FRACIMALNK.RXUSERCELLS

Number of CellsReceived on anFractional IMALink


67194006 VS.FRACIMALNK.RXSTUFFCELLS

Number ofFilling CellsReceived on anFractional IMALink


67194008 VS.FRACIMALNK.RXDROPPEDCELLS

Number of CellsDiscarded on anFractional IMALink




118



67194009 VS.FRACIMALNK.RXHCSERRCELLS

Number of ErrorCells Receivedon an FractionalIMA Link


67194010 VS.FRACIMALNK.TXMAXSPEED

MaximumTransmit Rate ofan FractionalIMA Link


67194011 VS.FRACIMALNK.TXMINSPEED

MinimumTransmit Rate ofan FractionalIMA Link


67194012 VS.FRACIMALNK.TXMEANSPEED

Mean TransmitRate of anFractional IMALink


67194013 VS.FRACIMALNK.RXMAXSPEED

MaximumReceive Rate ofan FractionalIMA Link


67194014 VS.FRACIMALNK.RXMINSPEED

MinimumReceive Rate ofan FractionalIMA Link


67194015 VS.FRACIMALNK.RXMEANSPEED

Mean ReceiveRate of anFractional IMALink


67194017 VS.IMAGROUP.RXUSERCELLS

Number of UserCells Receivedon an IMAGroup

BSC6900 WRFD-050304 IMA for E1T1 orChannelizedSTM-1/OC-3 onIub Interface

67194018 VS.IMAGROUP.RXSTUFFCELLS

Number ofFilling CellsReceived on anIMA Group




119



67194020 VS.IMAGROUP.RXFILLERCELLS

Number ofdecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Received on anIMA Group


67194021 VS.IMAGROUP.TXUSERCELLS

Number of UserCellsTransmitted onan IMA Group


67194022 VS.IMAGROUP.TXSTUFFCELLS

Number ofFilling CellsTransmitted onan IMA Group


67194024 VS.IMAGROUP.TXFILLERCELLS

Number ofDecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Transmitted onan IMA Group


67194025 VS.IMAGROUP.TXDISCARD

Number of CellsDiscarded inTransmission onan IMA Group


67194026 VS.IMAGROUP.RXDROP

Number of CellsDiscarded inReception on anIMA Group


67194027 VS.IMAGROUP.TXERRORCELLS

Number of ErrorCellsTransmitted onan IMA Group


67194028 VS.IMAGROUP.RXERRORCELLS

Number of ErrorCells Receivedon an IMAGroup




120



67194029 VS.IMALNK.RXUSERCELLS

Number of UserCells Receivedon an IMA Link


67194030 VS.IMALNK.RXUSTUFFCELLS

Number ofFilling CellsReceived on anIMA Link


67194032 VS.IMALNK.RXIDLECELLS

Number of idleCells Receivedon an IMA Link


67194033 VS.IMALNK.TXUSERCELLS

Number of UserCellsTransmitted onan IMA Link


67194034 VS.IMALNK.TXUSTUFFCELLS

Number ofFilling CellsTransmitted onan IMA Link


67194036 VS.IMALNK.RXFILTERCELLS

Number of UserCells Discardedon an IMA LinkDue to Errors inthe Link


67194037 VS.IMALNK.RXANOMALY

Number of Cellswith FramesynchronizationError on an IMALink


67194038 VS.IMALNK.RXICPVIOLATE

Number of Cellswith Error ICP(IMA ControlProtocol)Received on anIMA Link


67194039 VS.IMALNK.RXICPCELLS

Number of Cellswith valid ICP(IMA ControlProtocol)Received on anIMA Link




121



67194040 VS.IMALNK.RXHCSERROR

Number of Cellswith HCS(Header CheckSum) ErrorReceived on anIMA Link


67194041 VS.IMALNK.RXFILLERCELLS

Number ofdecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Received on anIMA Link


67194042 VS.IMALNK.FAULTEMIT

Number ofTimes that aFault Occurs inan IMA Link


67194043 VS.IMALNK.FAULTCLEAR

Number ofTimes that aFault is Clearedin an IMA Link


67194044 VS.IMALNK.FAULTTIME

Duration ofFaults in an IMALink


67194049 VS.UNILNK.RXHCSERRCELLS

Number of ErrorCells Receivedon a UNI Link

BSC6900 WRFD-05030101


67194050 VS.UNILNK.RXDROPS

Number of CellsDiscarded on aUNI Link

BSC6900 WRFD-05030101


67194073 VS.IPOALNK.RXCORRECTCELLS

Number ofCorrect CellsReceived on theIPoA Link

BSC6900 WRFD-05030105


67194074 VS.IPOALNK.RXBYTES

Number ofBytes Receivedon an IPoA Link

BSC6900 WRFD-05030105




122



67194076 VS.IPOALNK.TXCORRECTCELLS

Number ofCorrect CellsTransmitted onan IPoA Link

BSC6900 WRFD-05030105


67194077 VS.IPOALNK.TXBYTES

Number ofBytesTransmitted onan IPoA Link

BSC6900 WRFD-05030105


67194079 VS.IPOALNK.DROPFORHEADCELLS

Number of CellsDiscarded on anIPoA Link Dueto PacketHeader Error

BSC6900 WRFD-05030105


67194080 VS.IPOALNK.DROPFORRXOVERFLOWCELLS

Number of CellsDiscarded on anIPoA Link Dueto the Overflowof the inputBuffer

BSC6900 WRFD-05030105


67194081 VS.IPOALNK.DROPFORTXOVERFLOWCELLS

Number of CellsDiscarded on anIPoA Link Dueto the Overflowof the outputBuffer

BSC6900 WRFD-05030105


67194097 VS.AAL2PATH.PVCLAYER.RXCORRECTCELLS

Number of CellsReceived on theATM Layer ofthe AAL2 Path

BSC6900 WRFD-05030104


67194098 VS.AAL2PATH.PVCLAYER.RXBYTES

Number ofBytes Receivedon the ATMLayer of theAAL2 Path

BSC6900 WRFD-05030104


67194099 VS.AAL2PATH.PVCLAYER.PEAK.RXBYTES

Peak Number ofBytes Receivedon the ATMLayer of theAAL2 Path

BSC6900 WRFD-05030104




123



67194100 VS.AAL2PATH.PVCLAYER.TXCORRECTCELLS

Number of CellsTransmitted onthe ATM Layerof the AAL2Path

BSC6900 WRFD-05030104


67194101 VS.AAL2PATH.PVCLAYER.TXBYTES

Number ofBytesTransmitted onthe ATM Layerof the AAL2Path

BSC6900 WRFD-05030104


67194102 VS.AAL2PATH.PVCLAYER.PEAK.TXBYTES

Peak Number ofBytesTransmitted onthe ATM Layerof the AAL2Path

BSC6900 WRFD-05030104


67194103 VS.AAL2PATH.PVCLAYER.RXBYTESOFAAL2CPSPKTS

Number ofBytes of AAL2CPS(CommonPart Sublayer)PacketsReceived on theATM Layer ofthe AAL2 Path

BSC6900 WRFD-05030104


67194104 VS.AAL2PATH.PVCLAYER.TXBYTESOFAAL2CPSPKTS

Number ofBytes of AAL2CPS(CommonPart Sublayer)PacketsTransmitted onthe ATM Layerof the AAL2Path

BSC6900 WRFD-05030104


67194105 VS.AAL2PATH.PVCLAYER.DROPFORHEADCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to IncorrectHeader

BSC6900 WRFD-05030104




124



67194106 VS.AAL2PATH.PVCLAYER.DROPFORRXOVERFLOWCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to Overflowof ReceiveBuffer

BSC6900 WRFD-05030104


67194107 VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to Overflowof TransmitBuffer

BSC6900 WRFD-05030104


67194334 VS.ELECT.CODEVIOLATE

T7016:Numberof Cells withError Codes inthe E1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194335 VS.ELECT.FRAMINGERROR

T7020:Numberof Cells withError FrameDelimitation inthe E1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194336 VS.ELECT.CRCERROR

T7024:Numberof Cells withCRC Error in theE1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194337 VS.ELECT.EBITERROR

T7028:Numberof Cells withEbit Error in theE1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194338 VS.ELECT.SA6ERROR

T7032:Numberof Cells with Sa6Error in the E1/T1 ElectronicalPort

BSC6900 WRFD-05030101




125



67194341 VS.ELECT.FAULTTIME

T7035:Durationof Faults in theE1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194342 VS.ELECT.MULTIFRAME

T7036:Numberof Multiframeson the E1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194343 VS.ELECT.RXFLOWCAPACITY

T7037:TrafficReceived on theE1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194344 VS.ELECT.TXFLOWCAPACITY

T7038:TrafficTransmitted onthe E1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194347 VS.ELECT.FRAMEALIGNCHANGED

T7039:Numberof FrameAlignmentChanges of theE1/T1ElectronicalPort

BSC6900 WRFD-05030101


67194494 VS.VCCROSS.RXBYTES

Number ofBytes Receivedon a VC CrossConnection

BSC6900 WRFD-05030101


67194495 VS.VCCROSS.TXBYTES

Number ofBytesTransmitted on aVC CrossConnection

BSC6900 WRFD-05030101


67194496 VS.VCCROSS.RXCELLS

Number of CellsReceived on aVC CrossConnection

BSC6900 WRFD-05030101




126



67194497 VS.VCCROSS.TXCELLS

Number of CellsTransmitted on aVC CrossConnection

BSC6900 WRFD-05030101


67194498 VS.VCCROSS.RXHCSERRCELLS

Number of Cellswith HCS(Header CheckSum) ErrorsReceived on aVC CrossConnection

BSC6900 WRFD-05030101


67194499 VS.VCCROSS.RXDROPCELLS

Number of CellsDiscarded in theReceivingDirection of aVC CrossConnection Dueto theCongestion ofthe ATM Layer

BSC6900 WRFD-05030101


67194500 VS.VCCROSS.RXOVERFLOWDROPCELLS

Number of CellsDiscarded on aVC CrossConnection Dueto the Overflowof the ReceivingBuffer

BSC6900 WRFD-05030101


67194501 VS.VCCROSS.RXRECTIFIABLEHECERRCELLS

Number of Cellswith rectifiableHEC ErrorsReceived on aVC CrossConnection

BSC6900 WRFD-05030101


67194502 VS.VCCROSS.RXUNRECTIFIABLEHECERRCELLS

Number of CellswithUnrectifiableHEC ErrorsReceived on aVC CrossConnection

BSC6900 WRFD-05030101




127



67194503 VS.VCCROSS.TXOVERFLOWDROPCELLS

Number of CellsDiscardedBecause ofSending BufferOverflow on aVC CrossConnection

BSC6900 WRFD-05030101


67194504 VS.VCCROSS.TXDROPCELLS

Number of CellsAbnormallyDiscarded on aVC CrossConnection

BSC6900 WRFD-05030101


67194505 VS.VCCROSS.TXOVERFLOWCELLS

Number ofOverflow Cellson a VC CrossConnection

BSC6900 WRFD-05030101


67194506 VS.VCCROSS.TXMAXSPEED

MaximumTransmit Rate ofa VC CrossConnection

BSC6900 WRFD-05030101


67194507 VS.VCCROSS.TXMINSPEED

MinimumTransmit Rate ofa VC CrossConnection

BSC6900 WRFD-05030101


67194508 VS.VCCROSS.TXMEANSPEED

AverageTransmit Rate ofa VC CrossConnection

BSC6900 WRFD-05030101


67194509 VS.VCCROSS.RXMAXSPEED

MaximumReceive Rate ofa VC CrossConnection

BSC6900 WRFD-05030101


67194510 VS.VCCROSS.RXMINSPEED

MinimumReceive Rate ofa VC CrossConnection

BSC6900 WRFD-05030101


67194511 VS.VCCROSS.RXMEANSPEED

AverageReceive Rate ofa VC CrossConnection

BSC6900 WRFD-05030101




128



67194612 VS.QAAL2PART.Est.RLC.Fail.Rx

Number ofAAL2ConnectionReleaseConfirmationsReceived byQAAL2 onDual-StackAdjacent NodeDue to RemoteNetwork Fault,RemoteTemporaryFailure, orRemote NormalReleases

BSC6900 WRFD-05030104


67194771 VS.SAALLNK.PVCLAYER.TXBYTES

Number ofBytesTransmitted onan SAAL LinkATM Layer

BSC6900 WRFD-05030105


67194773 VS.SAALLNK.PVCLAYER.RXBYTES

Number ofBytes Receivedon an SAALLink ATMLayer

BSC6900 WRFD-05030105


67194775 VS.SAALLNK.PVCLAYER.RXCORRECTPKTS

Number ofCorrect PacketsReceived on anSAAL LinkATM Layer

BSC6900 WRFD-05030105


67194776 VS.SAALLNK.PVCLAYER.TXCORRECTPKTS

Number ofCorrect PacketsTransmitted onan SAAL LinkATM Layer

BSC6900 WRFD-05030105


67194777 VS.SAALLNK.PVCLAYER.DROPFORCNTERRCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto Incorrectcontent

BSC6900 WRFD-05030105




129



67194778 VS.SAALLNK.PVCLAYER.DROPFORLENERRCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto IncorrectPacket length

BSC6900 WRFD-05030105


67194779 VS.SAALLNK.PVCLAYER.RXBYTESOFAAL5CPSPKTS

Number ofBytes in CorrectAAL2 CPSPacketsReceived on anSAAL LinkATM Layer

BSC6900 WRFD-05030105


67194780 VS.SAALLNK.PVCLAYER.TXBYTESOFAAL5CPSPKTS

Number ofBytes in CorrectAAL2 CPSPacketsTransmitted onan SAAL LinkATM Layer

BSC6900 WRFD-05030105


67194781 VS.SAALLNK.PVCLAYER.RXOVERFLOWDROPPEDCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto the Overflowof the ReceivingBuffer

BSC6900 WRFD-05030105


67194782 VS.SAALLNK.PVCLAYER.TXOVERFLOWDROPPEDCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto the Overflowof theTransmittingBuffer

BSC6900 WRFD-05030105


67195595 VS.AAL2PATH.Fwd.Cong

Number ofForwardCongestions onthe AAL2 Path

BSC6900 WRFD-05030106


67195596 VS.AAL2PATH.Fwd.Cong.Dur

Duration ofForwardCongestions onthe AAL2 Path

BSC6900 WRFD-05030106




130



67195597 VS.AAL2PATH.Bwd.Cong

Number ofBackwardCongestions onthe AAL2 Path

BSC6900 WRFD-05030106


67195598 VS.AAL2PATH.Bwd.Cong.Dur

Duration ofBackwardCongestions onthe AAL2 Path

BSC6900 WRFD-05030106


67195938 VS.FRACATMLNK.Alloced.Max.Fwd

MaximumOccupiedForwardBandwidth of anFRA ATM Link


67195939 VS.FRACATMLNK.Alloced.Max.Bwd

MaximumOccupiedBackwardBandwidth of anFRA ATM Link


67195940 VS.FRACATMLNK.Fwd.Cong

Number ofForwardCongestions onan FRA ATMLink


67195941 VS.FRACATMLNK.Fwd.Cong.Dur

Duration ofForwardCongestions onan FRA ATMLink


67195942 VS.FRACATMLNK.Bwd.Cong

Number ofBackwardCongestions onan FRA ATMLink


67195943 VS.FRACATMLNK.Bwd.Cong.Dur

Duration ofBackwardCongestions onan FRA ATMLink




131



67196149 VS.QAAL2.Est.RLC.NoBitRate.Tx

Number of RLCMessages Sentby the QAAL2Due to NoBandwidthAvailable

BSC6900 WRFD-05030106


67196153 VS.SAAL.LnkErr.BufferLoss

Number ofPacketsDiscarded bySAAL Link Dueto BufferCongestion

BSC6900 WRFD-05030105


67196319 VS.ATMLGCPRT.Alloced.Max.Fwd

MaximumForwardBandwidthAssigned to theATM LogicalPort

BSC6900 WRFD-05030104


67196320 VS.ATMLGCPRT.Alloced.Max.Bwd

MaximumBackwardBandwidthAssigned to theATM LogicalPort

BSC6900 WRFD-05030104


67196321 VS.ATMLGCPRT.Fwd.Cong

Number ofForwardCongestions onthe ATMLogical Port

BSC6900 WRFD-05030104


67196322 VS.ATMLGCPRT.Fwd.Cong.Dur

Duration ofForwardCongestions onthe ATMLogical Port

BSC6900 WRFD-05030104


67196323 VS.ATMLGCPRT.Bwd.Cong

Number ofBackwardCongestions onthe ATMLogical Port

BSC6900 WRFD-05030104




132



67196324 VS.ATMLGCPRT.Bwd.Cong.Dur

Duration ofBackwardCongestions onthe ATMLogical Port

BSC6900 WRFD-05030104


67199677 VS.QAAL2.Act.Con

Number ofActive AAL2Connections toan QAAL2Adjacent Node

BSC6900 WRFD-05030104


67202907 VS.IMA.Grp.MeanKbps.Rx

Mean ReceiveRate of an IMAGroup


67202908 VS.IMA.Grp.MeanKbps.Tx

Mean TransmitRate of an IMAGroup


67202909 VS.IMA.Lnk.MeanKbps.Rx

Mean ReceiveRate of an IMALink


67202910 VS.IMA.Lnk.MeanKbps.Tx

Mean TransmitRate of an IMALink


67202915 VS.UNI.Lnk.MeanKbps.Rx

Average Rate ofReceiving Cellsa UNI Link

BSC6900 WRFD-05030101


67202916 VS.UNI.Lnk.MeanKbps.Tx

Average Rate ofTransmittingCells on a UNILink

BSC6900 WRFD-05030101


67202976 VS.UNILNK.PEAK.RXRATE

Maximum Rateof ReceivingCells on a UNILink

BSC6900 WRFD-05030101


67202977 VS.UNILNK.PEAK.TXRATE

Maximum Rateof TransmittingCells on a UNILink

BSC6900 WRFD-05030101




133



67203408 VS.IMALNK.PEAK.RXRATE

Maximum CellReceive Rate ofan IMA Link


67203409 VS.IMALNK.PEAK.TXRATE

Maximum CellTransmit Rate ofan IMA Link


67204192 VS.IMAGRP.Alloced.Ave.Fwd

Mean OccupiedForwardBandwidth of anIMA Group

BSC6900 WRFD-05030106


67204193 VS.IMAGRP.Alloced.Ave.Bwd

Mean OccupiedBackwardBandwidth of anIMA Group

BSC6900 WRFD-05030106


67204196 VS.UNILNK.Alloced.Ave.Fwd

Mean ForwardBandwidthAllocated forUNI Link

BSC6900 WRFD-05030106


67204197 VS.UNILNK.Alloced.Ave.Bwd

Mean BackwardBandwidthAllocated forUNI Link

BSC6900 WRFD-05030106


67204206 VS.AAL2PATH.Act.Con

Number ofActive AAL2Connections toan AdjacentNode

BSC6900 WRFD-05030106


67204457 VS.IMAGROUP.PEAK.RXRATE

MaximumReceive Rate ofan IMA GROUP


67204458 VS.IMAGROUP.PEAK.TXRATE

MaximumTransmit Rate ofan IMA Group


67204471 VS.IPOALNK.PEAK.RXRATE

MaximumReceive Rate ofan IPoA Link

BSC6900 WRFD-05030105




134



67204472 VS.IPOALNK.PEAK.TXRATE

MaximumTransmit Rate ofan IPoA Link

BSC6900 WRFD-05030105


67204473 VS.SAALLNK.PVCLAYER.PEAK.TXRATE

MaximumTransmit Rate ofSAAL LinkATM Layer

BSC6900 WRFD-05030105


67204474 VS.SAALLNK.PVCLAYER.PEAK.RXRATE

MaximumReceive Rate ofan SAAL LinkATM Layer

BSC6900 WRFD-05030105


67204488 VS.ELECT.CODEVIOLATE.Rate.Mean

T7017:Rate ofCells with ErrorCodes in the E1/T1 ElectronicalPort

BSC6900 WRFD-05030101


67204489 VS.ELECT.FRAMINGERROR.Rate.Mean

T7021:Rate ofCells withFrameDelimitationError in the E1/T1 ElectronicalPort

BSC6900 WRFD-05030101


67204490 VS.ELECT.CRCERROR.Rate.Mean

T7025:Rate ofCells with CRCError in the E1/T1 ElectronicalPort

BSC6900 WRFD-05030101


67204491 VS.ELECT.EBITERROR.Rate.Mean

T7029:Rate ofCells with EbitError in the E1/T1 ElectronicalPort

BSC6900 WRFD-05030101


67204779 VS.FRACATMLNK.Alloced.Ave.Fwd

Mean OccupiedForwardBandwidth of anFRA ATM Link




135



67204780 VS.FRACATMLNK.Alloced.Ave.Bwd

Mean OccupiedBackwardBandwidth of anFRA ATM Link


67204858 VS.ATMLGCPRT.Alloced.Ave.Bwd

Mean BackwardBandwidthAssigned to theATM LogicalPort

BSC6900 WRFD-05030104


67204859 VS.ATMLGCPRT.Alloced.Ave.Fwd

Mean ForwardBandwidthAssigned to theATM LogicalPort

BSC6900 WRFD-05030104


73403242 VS.E1T1.ES.ES T7001:E1/T1Error Seconds

BSC6900 WRFD-05030101


73403243 VS.E1T1.ES.SES

T7002:E1/T1Severely ErrorSeconds

BSC6900 WRFD-05030101


73403244 VS.E1T1.ES.UAS

T7003:E1/T1UnavailableSeconds

BSC6900 WRFD-05030101


73403245 VS.E1T1.ES.BBE

T7004:Numberof E1/T1BackgroundError Blocks

BSC6900 WRFD-05030101


73403645 VS.E1T1.ES.TES

T7010:Numberof Seconds withError CodesTransmittedover E1/T1

BSC6900 WRFD-05030101


73403646 VS.E1T1.ES.TSES

T7011:Numberof Seconds withSeverely ErrorCodesTransmittedover E1/T1

BSC6900 WRFD-05030101


73403647 VS.E1T1.ES.TBBE

T7012:Numberof BackgroundError BlocksTransmittedover E1/T1

BSC6900 WRFD-05030101




136



73404129 VS.CHANNELIZED.FAULTTIME

T7247:Durationof Faults on theChannelizedOptical Port


73404139 VS.NONCHANNELIZED.FAULTTIME

T7222:Durationof Faults on theOptical Port

BSC6900 WRFD-05030103

ATM over Non-channelizedSTM-1/OC-3con Iub/Iu/IurInterface

73415654 VS.E1T1.ES.ESR

T7005:E1/T1Error SecondRate

BSC6900 WRFD-05030101


73415655 VS.E1T1.ES.SESR

T7006:E1/T1Severely ErrorSecond Rate

BSC6900 WRFD-05030101


73415656 VS.E1T1.ES.UASR

T7007:E1/T1UnavailableSecond Rate

BSC6900 WRFD-05030101


73415657 VS.E1T1.ES.BBER

T7008:E1/T1BackgroundBlock ErrorRate

BSC6900 WRFD-05030101


73415827 VS.E1T1.ES.TESR

T7013:SecondRate with ErrorCodesTransmittedover E1/T1

BSC6900 WRFD-05030101


73415828 VS.E1T1.ES.TSESR

T7014:SecondRate withSeverely ErrorCodesTransmittedover E1/T1

BSC6900 WRFD-05030101


73415829 VS.E1T1.ES.TBBER

T7015:ErrorRate ofBackgroundBlockTransmittedover E1/T1

BSC6900 WRFD-05030101




137



73416121 VS.NONCHANNELIZED.RXCELLS

T7214:Numberof CellsReceived on theOptical Port

BSC6900 WRFD-05030103


73416122 VS.NONCHANNELIZED.TXCELLS

T7217:Numberof CellsTransmitted onthe Optical Port

BSC6900 WRFD-05030103


73416123 VS.NONCHANNELIZED.TXMAXSPEED

T7225:HighestTransmit Rateover the OpticalPort

BSC6900 WRFD-05030103


73416124 VS.NONCHANNELIZED.TXMINSPEED

T7226:LowestTransmit Rateover the OpticalPort

BSC6900 WRFD-05030103


73416125 VS.NONCHANNELIZED.TXMEANSPEED

T7227:MeanTransmit Rateover the OpticalPort

BSC6900 WRFD-05030103


73416126 VS.NONCHANNELIZED.RXMAXSPEED

T7230:HighestReceive Rateover the OpticalPort

BSC6900 WRFD-05030103


73416127 VS.NONCHANNELIZED.RXMINSPEED

T7231:LowestReceive Rateover the OpticalPort

BSC6900 WRFD-05030103


73416128 VS.NONCHANNELIZED.RXMEANSPEED

T7232:MeanReceive Rateover the OpticalPort

BSC6900 WRFD-05030103




138



73416129 VS.UOI.RXMAXSPEED

T7236:Maximum Receive Rateof UOI board

BSC6900 WRFD-05030103


73416130 VS.UOI.TXMAXSPEED

T7237:Maximum Transmit Rateof UOI board

BSC6900 WRFD-05030103


73421684 VS.SAAL.LnkErr.SDRetransRx

Number ofSAAL LinkMAA-ERRORIndications(SDLOSS_RX)

BSC6900 WRFD-05030105


73424515 VS.SAAL.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73424516 VS.SAAL.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof a SAAL link

BSC6900 WRFD-05030110

F5

73424531 VS.AAL2PATH.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73424538 VS.AAL2PATH.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5



139



73424539 VS.AAL2PATH.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof an AAL2 Path

BSC6900 WRFD-05030110

F5

73424558 VS.IPOAPVC.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73424559 VS.IPOAPVC.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof an IPOAPVClink

BSC6900 WRFD-05030110

F5

73426203 VS.E1T1.ES.NUV

T7077:E1/T1Number ofUnavailability

BSC6900 WRFD-05030101


73441389 VS.SAAL.VCLPM.RXCELL

Number ofReceived VCLPM Cells on aSAAL link

BSC6900 WRFD-05030110

F5

73441390 VS.SAAL.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson a SAAL link

BSC6900 WRFD-05030110

F5

73441391 VS.SAAL.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on aSAAL link

BSC6900 WRFD-05030110

F5

73441392 VS.SAAL.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on aSAAL link

BSC6900 WRFD-05030110

F5



140



73441393 VS.SAAL.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441394 VS.SAAL.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441395 VS.SAAL.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441396 VS.SAAL.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441397 VS.SAAL.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441398 VS.SAAL.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of aSAAL link

BSC6900 WRFD-05030110

F5



141



73441399 VS.SAAL.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441400 VS.SAAL.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of aSAAL link

BSC6900 WRFD-05030110

F5

73441401 VS.AAL2PATH.VCLPM.RXCELL

Number ofReceived VCLPM Cells on anAAL2 Path

BSC6900 WRFD-05030110

F5

73441402 VS.AAL2PATH.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson an AAL2Path

BSC6900 WRFD-05030110

F5

73441403 VS.AAL2PATH.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on anAAL2 Path

BSC6900 WRFD-05030110

F5

73441404 VS.AAL2PATH.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on anAAL2 Path

BSC6900 WRFD-05030110

F5

73441405 VS.AAL2PATH.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441406 VS.AAL2PATH.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5



142



73441407 VS.AAL2PATH.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441408 VS.AAL2PATH.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441409 VS.AAL2PATH.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441410 VS.AAL2PATH.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441411 VS.AAL2PATH.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of anAAL2 Path

BSC6900 WRFD-05030110

F5

73441412 VS.IPOAPVC.VCLPM.RXCELL

Number ofReceived VCLPM Cells on anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441413 VS.IPOAPVC.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson an IPOAPVClink

BSC6900 WRFD-05030110

F5



143



73441414 VS.IPOAPVC.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441415 VS.IPOAPVC.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441416 VS.IPOAPVC.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441417 VS.IPOAPVC.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441418 VS.IPOAPVC.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441419 VS.IPOAPVC.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441420 VS.IPOAPVC.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5



144



73441421 VS.IPOAPVC.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441422 VS.IPOAPVC.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

73441423 VS.IPOAPVC.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of anIPOAPVC link

BSC6900 WRFD-05030110

F5

67182593 VS.SAAL.LnkServDur.Time

In-ServiceDuration ofSAAL Link

BSC6910 WRFD-05030105


67182594 VS.SAAL.FailLnk.AllReasons

Number ofSAAL LinkFailures (AllCauses)

BSC6910 WRFD-05030105


67182595 VS.SAAL.FailLnk.NoRspTimExp

Number ofSAAL Failures(Timer Expires)

BSC6910 WRFD-05030105


67182596 VS.SAAL.FailLnk.ExcesErr.Rat

Number ofSAAL Failures(Over-HighBER)

BSC6910 WRFD-05030105




145



67182597 VS.SAAL.FailLnk.ExcesNoCred

Number ofSAAL LinkFailures(Congestion)

BSC6910 WRFD-05030105


67182598 VS.SAAL.FailLnk.AlignFail

Number ofSAAL LinkAlignmentFailures

BSC6910 WRFD-05030105


67182599 VS.SAAL.LnkErr.SDRetransTx

Number ofSAAL LinkMAA-ERRORIndications(SDLOSS_TX)

BSC6910 WRFD-05030105


67182600 VS.SAAL.LnkErr.PDUInval

Number ofSAAL LinkMAA-ERRORIndications(Invalid PDU)

BSC6910 WRFD-05030105


67182601 VS.SAAL.LnkErr.OthReasons

Number ofSAAL LinkMAA-ERRORIndications(Others)

BSC6910 WRFD-05030105


67182602 VS.SAAL.LnkErr.RetransFail

Number ofSAAL LinkMAA-ERRORIndicationsReceived(UnsuccessfulRetransmission)

BSC6910 WRFD-05030105


67183361 VS.QAAL2.ERQ.Tx

Number ofAAL2ConnectionEstablishmentRequests Sentby the QAAL2

BSC6910 WRFD-05030104




146



67183362 VS.QAAL2.ERQ.Rx

Number ofAAL2ConnectionEstablishmentRequestsReceived by theQAAL2

BSC6910 WRFD-05030104


67183363 VS.QAAL2.Est.RLC.Rx

Number ofAAL2ConnectionReleaseConfirmations(RLCs)Received by theQAAL2 Afterthe QAAL2Sends the ERQMessage

BSC6910 WRFD-05030104


67183364 VS.QAAL2.Est.ECF.Rx

Number of ECFMessagesReceived by theQAAL2 Afterthe QAAL2Sends the ERQMessage

BSC6910 WRFD-05030104


67183365 VS.QAAL2.Est.ECF.Tx

Number of ECFMessages Sentby the QAAL2After theQAAL2Receives theERQ Message

BSC6910 WRFD-05030104


67183366 VS.QAAL2.Est.RLC.Tx

Number of RLCMessages Sentby the QAAL2After theQAAL2Receives theERQ Message

BSC6910 WRFD-05030104




147



67183367 VS.QAAL2.Rel.Tx

Number ofAAL2ConnectionReleaseRequests(RELs) Sent bythe QAAL2

BSC6910 WRFD-05030104


67183368 VS.QAAL2.Rel.Rx

Number ofAAL2ConnectionReleaseRequests(RELs)Received by theQAAL2

BSC6910 WRFD-05030104


67183369 VS.QAAL2.Rel.RLC.Rx

Number ofAAL2ConnectionReleaseConfirmations(RLCs)Received by theQAAL2 Afterthe QAAL2Sends the RELMessage

BSC6910 WRFD-05030104


67183370 VS.QAAL2.Rel.RLC.Tx

Number of RLCMessages Sentby the QAAL2After theQAAL2Receives theREL Message

BSC6910 WRFD-05030104


67190053 VS.AAL2.CAC.Att

Number ofAAL2 PathResourceAdmissions

BSC6910 WRFD-05030106


67190054 VS.AAL2.CAC.Succ

Number ofSuccessfulAAL2 PathAdmissions

BSC6910 WRFD-05030106




148



67190055 VS.QAAL2.Est.RLC.NoRoute.Rx

Number of RLCMessagesReceived by theQAAL2 Due toNo Route at theRemote End

BSC6910 WRFD-05030104


67190056 VS.QAAL2.Est.RLC.NoPath.Rx

Number of RLCMessagesReceived byQAAL2 Due toNo AAL2 PathConfigued at theRemote End

BSC6910 WRFD-05030104


67190057 VS.QAAL2.Est.RLC.NoCID.Rx

Number of RLCMessagesReceived byQAAL2 Due toNo CIDAvailable at theRemote End

BSC6910 WRFD-05030104


67190058 VS.QAAL2.Est.RLC.Fail.Rx

Number of RLCMessagesReceived byQAAL2 Due toRemoteNetwork Fault,RemoteTemporaryFailure, orRemote NormalReleases

BSC6910 WRFD-05030104


67190059 VS.QAAL2.Est.RLC.Cong.Rx

Number of RLCMessagesReceived byQAAL2 Due toSwitchCongestion atthe Remote End

BSC6910 WRFD-05030104


67190060 VS.QAAL2.Est.RLC.RecovOut.Rx

Number of RLCMessagesReceived byQAAL2 Due toTimer Expiry atthe Remote End

BSC6910 WRFD-05030104




149



67190061 VS.QAAL2.Est.RLC.NoRoute.Tx

Number of RLCMessages Sentby the QAAL2Due to No Routeat the RemoteEnd

BSC6910 WRFD-05030104


67190062 VS.QAAL2.Est.RLC.NoPath.Tx

Number of RLCMessages Sentby the QAAL2Due to NoAAL2 PathConfigured

BSC6910 WRFD-05030104


67190063 VS.QAAL2.Est.RLC.NoCID.Tx

Number of RLCMessages Sentby the QAAL2Due to No CIDAvailable

BSC6910 WRFD-05030104


67190064 VS.QAAL2.Est.RLC.Fail.Tx

Number of RLCMessages Sentby the QAAL2Due to NetworkFailure,UnspecifiedReason, orTemporaryFailure

BSC6910 WRFD-05030104


67190065 VS.QAAL2.Est.RLC.Cong.Tx

Number of RLCMessages Sentby QAAL2 Dueto SwitchCongestion

BSC6910 WRFD-05030104


67190066 VS.QAAL2.Est.RLC.RecovOut.Tx

Number of RLCMessages Sentby QAAL2 Dueto Timer Expiry

BSC6910 WRFD-05030104


67190067 VS.QAAL2.RxModRej

Number ofAAL2ConnectionModificationRejections(MORs)Received by theQAAL2

BSC6910 WRFD-05030104




150



67190068 VS.QAAL2.TxModRej

Number ofMOR MessagesSent by theQAAL2 Afterthe QAAL2Receives theMOD Message

BSC6910 WRFD-05030104


67190490 VS.UNILNK.RXCELLS

Number of CellsReceived on aUNI Link

BSC6910 WRFD-05030102

ATM overChannelizedSTM-1/OC-3 onIub Interface

67190491 VS.UNILNK.TXCELLS

Number of CellsTransmitted on aUNI Link

BSC6910 WRFD-05030102


67190553 VS.QAAL2.TxMod

Number ofAAL2ConnectionModificationRequests(MODs) Sent bythe QAAL2

BSC6910 WRFD-05030104


67190554 VS.QAAL2.RxMod

Number ofAAL2ConnectionModificationRequests(MODs)Received by theQAAL2

BSC6910 WRFD-05030104


67190555 VS.QAAL2.AllocedFwd.AAL2BitRate

Mean ForwardBandwidth ofAAL2 PathAllocated to anAdjacent Node

BSC6910 WRFD-05030106


67190558 VS.QAAL2.AllocedBwd.AAL2BitRate

Mean BackwardBandwidth ofAAL2 PathAllocated to anAdjacent Node

BSC6910 WRFD-05030106




151



67190562 VS.QAAL2.AllocedMaxFwd.AAL2BitRate.Value

MaximumValue of AAL2Path ForwardBandwidthAllocated to anAdjacent Node

BSC6910 WRFD-05030106


67190565 VS.QAAL2.AllocedMaxBwd.AAL2BitRate.Value

MaximumValue of AAL2Path BackwardBandwidthAllocated to anAdjacent Node

BSC6910 WRFD-05030106


67190615 VS.AAL5.SAALLnk.BytesRx

Number ofBytes Receivedby SAAL Link

BSC6910 WRFD-05030105


67190616 VS.AAL5.SAALLnk.BytesTx

Number ofBytes Sent bySAAL Link

BSC6910 WRFD-05030105


67193215 VS.IMAGRP.Alloced.Max.Fwd

MaximumOccupiedForwardBandwidth of anIMA Group

BSC6910 WRFD-05030106


67193216 VS.IMAGRP.Alloced.Max.Bwd

MaximumOccupiedBackwardBandwidth of anIMA Group

BSC6910 WRFD-05030106


67193217 VS.IMAGRP.Fwd.Cong

Number ofForwardCongestions onan IMA Group

BSC6910 WRFD-05030106


67193218 VS.IMAGRP.Fwd.Cong.Dur

Duration ofForwardCongestions onan IMA Group

BSC6910 WRFD-05030106




152



67193219 VS.IMAGRP.Bwd.Cong

Number ofBackwardCongestions onan IMA Group

BSC6910 WRFD-05030106


67193220 VS.IMAGRP.Bwd.Cong.Dur

Duration ofBackwardCongestions onan IMA Group

BSC6910 WRFD-05030106


67193235 VS.UNILNK.Alloced.Max.Fwd

MaximumForwardBandwidthAllocated forUNI Link

BSC6910 WRFD-05030106


67193236 VS.UNILNK.Alloced.Max.Bwd

MaximumBackwardBandwidthAllocated forUNI Link

BSC6910 WRFD-05030106


67193237 VS.UNILNK.Fwd.Cong

Number of UNILink ForwardCongestions

BSC6910 WRFD-05030106


67193238 VS.UNILNK.Fwd.Cong.Dur

Duration of UNILink ForwardCongestions

BSC6910 WRFD-05030106


67193239 VS.UNILNK.Bwd.Cong

Number of UNILink BackwardCongestions

BSC6910 WRFD-05030106


67193240 VS.UNILNK.Bwd.Cong.Dur

Duration of UNILink BackwardCongestions

BSC6910 WRFD-05030106


67193989 VS.FRACATMLNK.TXCELLS

Number of CellsTransmitted onan FractionalATM Link


67193991 VS.FRACATMLNK.RXCELLS

Number of CellsReceived on anFractional ATMLink




153



67193993 VS.FRACATMLNK.RXHCSERRCELLS

Number of ErrorCells Receivedon an FractionalATM Link


67193994 VS.FRACATMLNK.RXDROPPEDCELLS

Number of CellsDiscarded on anFractional ATMLink


67193995 VS.FRACATMLNK.TXMAXSPEED

MaximumTransmit Rate ofan FractionalATM Link


67193996 VS.FRACATMLNK.TXMINSPEED

MinimumTransmit Rate ofan FractionalATM Link


67193997 VS.FRACATMLNK.TXMEANSPEED

Mean TransmitRate of anFractional ATMLink


67193998 VS.FRACATMLNK.RXMAXSPEED

MaximumReceive Rate ofan FractionalATM Link


67193999 VS.FRACATMLNK.RXMINSPEED

MinimumReceive Rate ofan FractionalATM Link


67194000 VS.FRACATMLNK.RXMEANSPEED

Mean ReceiveRate of anFractional ATMLink


67194017 VS.IMAGROUP.RXUSERCELLS

Number of UserCells Receivedon an IMAGroup


67194018 VS.IMAGROUP.RXSTUFFCELLS

Number ofFilling CellsReceived on anIMA Group




154



67194020 VS.IMAGROUP.RXFILLERCELLS

Number ofdecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Received on anIMA Group


67194021 VS.IMAGROUP.TXUSERCELLS

Number of UserCellsTransmitted onan IMA Group


67194022 VS.IMAGROUP.TXSTUFFCELLS

Number ofFilling CellsTransmitted onan IMA Group


67194024 VS.IMAGROUP.TXFILLERCELLS

Number ofDecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Transmitted onan IMA Group


67194025 VS.IMAGROUP.TXDISCARD

Number of CellsDiscarded inTransmission onan IMA Group


67194026 VS.IMAGROUP.RXDROP

Number of CellsDiscarded inReception on anIMA Group


67194027 VS.IMAGROUP.TXERRORCELLS

Number of ErrorCellsTransmitted onan IMA Group


67194028 VS.IMAGROUP.RXERRORCELLS

Number of ErrorCells Receivedon an IMAGroup




155



67194029 VS.IMALNK.RXUSERCELLS

Number of UserCells Receivedon an IMA Link


67194030 VS.IMALNK.RXUSTUFFCELLS

Number ofFilling CellsReceived on anIMA Link


67194032 VS.IMALNK.RXIDLECELLS

Number of idleCells Receivedon an IMA Link


67194033 VS.IMALNK.TXUSERCELLS

Number of UserCellsTransmitted onan IMA Link


67194034 VS.IMALNK.TXUSTUFFCELLS

Number ofFilling CellsTransmitted onan IMA Link


67194036 VS.IMALNK.RXFILTERCELLS

Number of UserCells Discardedon an IMA LinkDue to Errors inthe Link


67194037 VS.IMALNK.RXANOMALY

Number of Cellswith FramesynchronizationError on an IMALink


67194038 VS.IMALNK.RXICPVIOLATE

Number of Cellswith Error ICP(IMA ControlProtocol)Received on anIMA Link


67194039 VS.IMALNK.RXICPCELLS

Number of Cellswith valid ICP(IMA ControlProtocol)Received on anIMA Link




156



67194040 VS.IMALNK.RXHCSERROR

Number of Cellswith HCS(Header CheckSum) ErrorReceived on anIMA Link


67194041 VS.IMALNK.RXFILLERCELLS

Number ofdecouplingCells(Idle CellsReceived whenThere Is No Cellto Transmit)Received on anIMA Link


67194042 VS.IMALNK.FAULTEMIT

Number ofTimes that aFault Occurs inan IMA Link


67194043 VS.IMALNK.FAULTCLEAR

Number ofTimes that aFault is Clearedin an IMA Link


67194044 VS.IMALNK.FAULTTIME

Duration ofFaults in an IMALink


67194049 VS.UNILNK.RXHCSERRCELLS

Number of ErrorCells Receivedon a UNI Link

BSC6910 WRFD-05030102


67194050 VS.UNILNK.RXDROPS

Number of CellsDiscarded on aUNI Link

BSC6910 WRFD-05030102


67194073 VS.IPOALNK.RXCORRECTCELLS

Number ofCorrect CellsReceived on theIPoA Link

BSC6910 WRFD-05030105




157



67194074 VS.IPOALNK.RXBYTES

Number ofBytes Receivedon an IPoA Link

BSC6910 WRFD-05030105


67194076 VS.IPOALNK.TXCORRECTCELLS

Number ofCorrect CellsTransmitted onan IPoA Link

BSC6910 WRFD-05030105


67194077 VS.IPOALNK.TXBYTES

Number ofBytesTransmitted onan IPoA Link

BSC6910 WRFD-05030105


67194079 VS.IPOALNK.DROPFORHEADCELLS

Number of CellsDiscarded on anIPoA Link Dueto PacketHeader Error

BSC6910 WRFD-05030105


67194080 VS.IPOALNK.DROPFORRXOVERFLOWCELLS

Number of CellsDiscarded on anIPoA Link Dueto the Overflowof the inputBuffer

BSC6910 WRFD-05030105


67194081 VS.IPOALNK.DROPFORTXOVERFLOWCELLS

Number of CellsDiscarded on anIPoA Link Dueto the Overflowof the outputBuffer

BSC6910 WRFD-05030105


67194097 VS.AAL2PATH.PVCLAYER.RXCORRECTCELLS

Number of CellsReceived on theATM Layer ofthe AAL2 Path

BSC6910 WRFD-05030104


67194098 VS.AAL2PATH.PVCLAYER.RXBYTES

Number ofBytes Receivedon the ATMLayer of theAAL2 Path

BSC6910 WRFD-05030104




158



67194099 VS.AAL2PATH.PVCLAYER.PEAK.RXBYTES

Peak Number ofBytes Receivedon the ATMLayer of theAAL2 Path

BSC6910 WRFD-05030104


67194100 VS.AAL2PATH.PVCLAYER.TXCORRECTCELLS

Number of CellsTransmitted onthe ATM Layerof the AAL2Path

BSC6910 WRFD-05030104


67194101 VS.AAL2PATH.PVCLAYER.TXBYTES

Number ofBytesTransmitted onthe ATM Layerof the AAL2Path

BSC6910 WRFD-05030104


67194102 VS.AAL2PATH.PVCLAYER.PEAK.TXBYTES

Peak Number ofBytesTransmitted onthe ATM Layerof the AAL2Path

BSC6910 WRFD-05030104


67194103 VS.AAL2PATH.PVCLAYER.RXBYTESOFAAL2CPSPKTS

Number ofBytes of AAL2CPS(CommonPart Sublayer)PacketsReceived on theATM Layer ofthe AAL2 Path

BSC6910 WRFD-05030104


67194104 VS.AAL2PATH.PVCLAYER.TXBYTESOFAAL2CPSPKTS

Number ofBytes of AAL2CPS(CommonPart Sublayer)PacketsTransmitted onthe ATM Layerof the AAL2Path

BSC6910 WRFD-05030104




159



67194105 VS.AAL2PATH.PVCLAYER.DROPFORHEADCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to IncorrectHeader

BSC6910 WRFD-05030104


67194106 VS.AAL2PATH.PVCLAYER.DROPFORRXOVERFLOWCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to Overflowof ReceiveBuffer

BSC6910 WRFD-05030104


67194107 VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS

Number of CellsDiscarded on theATM Layer ofthe AAL2 PathDue to Overflowof TransmitBuffer

BSC6910 WRFD-05030104


67194612 VS.QAAL2PART.Est.RLC.Fail.Rx

Number ofAAL2ConnectionReleaseConfirmationsReceived byQAAL2 onDual-StackAdjacent NodeDue to RemoteNetwork Fault,RemoteTemporaryFailure, orRemote NormalReleases

BSC6910 WRFD-05030104


67194771 VS.SAALLNK.PVCLAYER.TXBYTES

Number ofBytesTransmitted onan SAAL LinkATM Layer

BSC6910 WRFD-05030105




160



67194773 VS.SAALLNK.PVCLAYER.RXBYTES

Number ofBytes Receivedon an SAALLink ATMLayer

BSC6910 WRFD-05030105


67194775 VS.SAALLNK.PVCLAYER.RXCORRECTPKTS

Number ofCorrect PacketsReceived on anSAAL LinkATM Layer

BSC6910 WRFD-05030105


67194776 VS.SAALLNK.PVCLAYER.TXCORRECTPKTS

Number ofCorrect PacketsTransmitted onan SAAL LinkATM Layer

BSC6910 WRFD-05030105


67194777 VS.SAALLNK.PVCLAYER.DROPFORCNTERRCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto Incorrectcontent

BSC6910 WRFD-05030105


67194778 VS.SAALLNK.PVCLAYER.DROPFORLENERRCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto IncorrectPacket length

BSC6910 WRFD-05030105


67194779 VS.SAALLNK.PVCLAYER.RXBYTESOFAAL5CPSPKTS

Number ofBytes in CorrectAAL2 CPSPacketsReceived on anSAAL LinkATM Layer

BSC6910 WRFD-05030105


67194780 VS.SAALLNK.PVCLAYER.TXBYTESOFAAL5CPSPKTS

Number ofBytes in CorrectAAL2 CPSPacketsTransmitted onan SAAL LinkATM Layer

BSC6910 WRFD-05030105




161



67194781 VS.SAALLNK.PVCLAYER.RXOVERFLOWDROPPEDCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto the Overflowof the ReceivingBuffer

BSC6910 WRFD-05030105


67194782 VS.SAALLNK.PVCLAYER.TXOVERFLOWDROPPEDCELLS

Number of CellsDiscarded on anSAAL LinkATM Layer Dueto the Overflowof theTransmittingBuffer

BSC6910 WRFD-05030105


67195595 VS.AAL2PATH.Fwd.Cong

Number ofForwardCongestions onthe AAL2 Path

BSC6910 WRFD-05030106


67195596 VS.AAL2PATH.Fwd.Cong.Dur

Duration ofForwardCongestions onthe AAL2 Path

BSC6910 WRFD-05030106


67195597 VS.AAL2PATH.Bwd.Cong

Number ofBackwardCongestions onthe AAL2 Path

BSC6910 WRFD-05030106


67195598 VS.AAL2PATH.Bwd.Cong.Dur

Duration ofBackwardCongestions onthe AAL2 Path

BSC6910 WRFD-05030106


67195938 VS.FRACATMLNK.Alloced.Max.Fwd

MaximumOccupiedForwardBandwidth of anFRA ATM Link


67195939 VS.FRACATMLNK.Alloced.Max.Bwd

MaximumOccupiedBackwardBandwidth of anFRA ATM Link




162



67195940 VS.FRACATMLNK.Fwd.Cong

Number ofForwardCongestions onan FRA ATMLink


67195941 VS.FRACATMLNK.Fwd.Cong.Dur

Duration ofForwardCongestions onan FRA ATMLink


67195942 VS.FRACATMLNK.Bwd.Cong

Number ofBackwardCongestions onan FRA ATMLink


67195943 VS.FRACATMLNK.Bwd.Cong.Dur

Duration ofBackwardCongestions onan FRA ATMLink


67196149 VS.QAAL2.Est.RLC.NoBitRate.Tx

Number of RLCMessages Sentby the QAAL2Due to NoBandwidthAvailable

BSC6910 WRFD-05030106


67196153 VS.SAAL.LnkErr.BufferLoss

Number ofPacketsDiscarded bySAAL Link Dueto BufferCongestion

BSC6910 WRFD-05030105


67196319 VS.ATMLGCPRT.Alloced.Max.Fwd

MaximumForwardBandwidthAssigned to theATM LogicalPort

BSC6910 WRFD-05030104




163



67196320 VS.ATMLGCPRT.Alloced.Max.Bwd

MaximumBackwardBandwidthAssigned to theATM LogicalPort

BSC6910 WRFD-05030104


67196321 VS.ATMLGCPRT.Fwd.Cong

Number ofForwardCongestions onthe ATMLogical Port

BSC6910 WRFD-05030104


67196322 VS.ATMLGCPRT.Fwd.Cong.Dur

Duration ofForwardCongestions onthe ATMLogical Port

BSC6910 WRFD-05030104


67196323 VS.ATMLGCPRT.Bwd.Cong

Number ofBackwardCongestions onthe ATMLogical Port

BSC6910 WRFD-05030104


67196324 VS.ATMLGCPRT.Bwd.Cong.Dur

Duration ofBackwardCongestions onthe ATMLogical Port

BSC6910 WRFD-05030104


67199677 VS.QAAL2.Act.Con

Number ofActive AAL2Connections toan QAAL2Adjacent Node

BSC6910 WRFD-05030104


67202907 VS.IMA.Grp.MeanKbps.Rx

Mean ReceiveRate of an IMAGroup


67202908 VS.IMA.Grp.MeanKbps.Tx

Mean TransmitRate of an IMAGroup




164



67202909 VS.IMA.Lnk.MeanKbps.Rx

Mean ReceiveRate of an IMALink


67202910 VS.IMA.Lnk.MeanKbps.Tx

Mean TransmitRate of an IMALink


67202915 VS.UNI.Lnk.MeanKbps.Rx

Average Rate ofReceiving Cellsa UNI Link

BSC6910 WRFD-05030102


67202916 VS.UNI.Lnk.MeanKbps.Tx

Average Rate ofTransmittingCells on a UNILink

BSC6910 WRFD-05030102


67202976 VS.UNILNK.PEAK.RXRATE

Maximum Rateof ReceivingCells on a UNILink

BSC6910 WRFD-05030102


67202977 VS.UNILNK.PEAK.TXRATE

Maximum Rateof TransmittingCells on a UNILink

BSC6910 WRFD-05030102


67203408 VS.IMALNK.PEAK.RXRATE

Maximum CellReceive Rate ofan IMA Link


67203409 VS.IMALNK.PEAK.TXRATE

Maximum CellTransmit Rate ofan IMA Link


67204192 VS.IMAGRP.Alloced.Ave.Fwd

Mean OccupiedForwardBandwidth of anIMA Group

BSC6910 WRFD-05030106


67204193 VS.IMAGRP.Alloced.Ave.Bwd

Mean OccupiedBackwardBandwidth of anIMA Group

BSC6910 WRFD-05030106




165



67204196 VS.UNILNK.Alloced.Ave.Fwd

Mean ForwardBandwidthAllocated forUNI Link

BSC6910 WRFD-05030106


67204197 VS.UNILNK.Alloced.Ave.Bwd

Mean BackwardBandwidthAllocated forUNI Link

BSC6910 WRFD-05030106


67204206 VS.AAL2PATH.Act.Con

Number ofActive AAL2Connections toan AdjacentNode

BSC6910 WRFD-05030106


67204457 VS.IMAGROUP.PEAK.RXRATE

MaximumReceive Rate ofan IMA GROUP


67204458 VS.IMAGROUP.PEAK.TXRATE

MaximumTransmit Rate ofan IMA Group


67204471 VS.IPOALNK.PEAK.RXRATE

MaximumReceive Rate ofan IPoA Link

BSC6910 WRFD-05030105


67204472 VS.IPOALNK.PEAK.TXRATE

MaximumTransmit Rate ofan IPoA Link

BSC6910 WRFD-05030105


67204473 VS.SAALLNK.PVCLAYER.PEAK.TXRATE

MaximumTransmit Rate ofSAAL LinkATM Layer

BSC6910 WRFD-05030105


67204474 VS.SAALLNK.PVCLAYER.PEAK.RXRATE

MaximumReceive Rate ofan SAAL LinkATM Layer

BSC6910 WRFD-05030105




166



67204779 VS.FRACATMLNK.Alloced.Ave.Fwd

Mean OccupiedForwardBandwidth of anFRA ATM Link


67204780 VS.FRACATMLNK.Alloced.Ave.Bwd

Mean OccupiedBackwardBandwidth of anFRA ATM Link


67204858 VS.ATMLGCPRT.Alloced.Ave.Bwd

Mean BackwardBandwidthAssigned to theATM LogicalPort

BSC6910 WRFD-05030104


67204859 VS.ATMLGCPRT.Alloced.Ave.Fwd

Mean ForwardBandwidthAssigned to theATM LogicalPort

BSC6910 WRFD-05030104


73403242 VS.E1T1.ES.ES T7001:E1/T1Error Seconds

BSC6910 WRFD-05030102


73403243 VS.E1T1.ES.SES

T7002:E1/T1Severely ErrorSeconds

BSC6910 WRFD-05030102


73403244 VS.E1T1.ES.UAS

T7003:E1/T1UnavailableSeconds

BSC6910 WRFD-05030102


73403245 VS.E1T1.ES.BBE

T7004:Numberof E1/T1BackgroundError Blocks

BSC6910 WRFD-05030102


73403645 VS.E1T1.ES.TES

T7010:Numberof Seconds withError CodesTransmittedover E1/T1

BSC6910 WRFD-05030102




167



73403646 VS.E1T1.ES.TSES

T7011:Numberof Seconds withSeverely ErrorCodesTransmittedover E1/T1

BSC6910 WRFD-05030102


73403647 VS.E1T1.ES.TBBE

T7012:Numberof BackgroundError BlocksTransmittedover E1/T1

BSC6910 WRFD-05030102


73404129 VS.CHANNELIZED.FAULTTIME

T7247:Durationof Faults on theChannelizedOptical Port


73404139 VS.NONCHANNELIZED.FAULTTIME

T7222:Durationof Faults on theOptical Port

BSC6910 WRFD-05030103


73415654 VS.E1T1.ES.ESR

T7005:E1/T1Error SecondRate

BSC6910 WRFD-05030102


73415655 VS.E1T1.ES.SESR

T7006:E1/T1Severely ErrorSecond Rate

BSC6910 WRFD-05030102


73415656 VS.E1T1.ES.UASR

T7007:E1/T1UnavailableSecond Rate

BSC6910 WRFD-05030102


73415657 VS.E1T1.ES.BBER

T7008:E1/T1BackgroundBlock ErrorRate

BSC6910 WRFD-05030102


73415827 VS.E1T1.ES.TESR

T7013:SecondRate with ErrorCodesTransmittedover E1/T1

BSC6910 WRFD-05030102




168



73415828 VS.E1T1.ES.TSESR

T7014:SecondRate withSeverely ErrorCodesTransmittedover E1/T1

BSC6910 WRFD-05030102


73415829 VS.E1T1.ES.TBBER

T7015:ErrorRate ofBackgroundBlockTransmittedover E1/T1

BSC6910 WRFD-05030102


73416121 VS.NONCHANNELIZED.RXCELLS

T7214:Numberof CellsReceived on theOptical Port

BSC6910 WRFD-05030103


73416122 VS.NONCHANNELIZED.TXCELLS

T7217:Numberof CellsTransmitted onthe Optical Port

BSC6910 WRFD-05030103


73416123 VS.NONCHANNELIZED.TXMAXSPEED

T7225:HighestTransmit Rateover the OpticalPort

BSC6910 WRFD-05030103


73416124 VS.NONCHANNELIZED.TXMINSPEED

T7226:LowestTransmit Rateover the OpticalPort

BSC6910 WRFD-05030103


73416125 VS.NONCHANNELIZED.TXMEANSPEED

T7227:MeanTransmit Rateover the OpticalPort

BSC6910 WRFD-05030103


73416126 VS.NONCHANNELIZED.RXMAXSPEED

T7230:HighestReceive Rateover the OpticalPort

BSC6910 WRFD-05030103




169



73416127 VS.NONCHANNELIZED.RXMINSPEED

T7231:LowestReceive Rateover the OpticalPort

BSC6910 WRFD-05030103


73416128 VS.NONCHANNELIZED.RXMEANSPEED

T7232:MeanReceive Rateover the OpticalPort

BSC6910 WRFD-05030103


73416129 VS.UOI.RXMAXSPEED

T7236:Maximum Receive Rateof UOI board

BSC6910 WRFD-05030103


73416130 VS.UOI.TXMAXSPEED

T7237:Maximum Transmit Rateof UOI board

BSC6910 WRFD-05030103


73421684 VS.SAAL.LnkErr.SDRetransRx

Number ofSAAL LinkMAA-ERRORIndications(SDLOSS_RX)

BSC6910 WRFD-05030105


73424515 VS.SAAL.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73424516 VS.SAAL.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof a SAAL link

BSC6910 WRFD-05030110

F5



170



73424531 VS.AAL2PATH.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73424538 VS.AAL2PATH.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73424539 VS.AAL2PATH.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof an AAL2 Path

BSC6910 WRFD-05030110

F5

73424558 VS.IPOAPVC.VCLPM.SOURCEBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSourceDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73424559 VS.IPOAPVC.VCLPM.SINKBIP16CRCERRCELL

Number of VCLPM Error CellBlocks Failedthe BIP16Check in theSink Directionof an IPOAPVClink

BSC6910 WRFD-05030110

F5

73426203 VS.E1T1.ES.NUV

T7077:E1/T1Number ofUnavailability

BSC6910 WRFD-05030102




171



73441389 VS.SAAL.VCLPM.RXCELL

Number ofReceived VCLPM Cells on aSAAL link

BSC6910 WRFD-05030110

F5

73441390 VS.SAAL.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson a SAAL link

BSC6910 WRFD-05030110

F5

73441391 VS.SAAL.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on aSAAL link

BSC6910 WRFD-05030110

F5

73441392 VS.SAAL.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on aSAAL link

BSC6910 WRFD-05030110

F5

73441393 VS.SAAL.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441394 VS.SAAL.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441395 VS.SAAL.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441396 VS.SAAL.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of aSAAL link

BSC6910 WRFD-05030110

F5



172



73441397 VS.SAAL.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441398 VS.SAAL.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441399 VS.SAAL.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441400 VS.SAAL.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of aSAAL link

BSC6910 WRFD-05030110

F5

73441401 VS.AAL2PATH.VCLPM.RXCELL

Number ofReceived VCLPM Cells on anAAL2 Path

BSC6910 WRFD-05030110

F5

73441402 VS.AAL2PATH.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson an AAL2Path

BSC6910 WRFD-05030110

F5

73441403 VS.AAL2PATH.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on anAAL2 Path

BSC6910 WRFD-05030110

F5

73441404 VS.AAL2PATH.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on anAAL2 Path

BSC6910 WRFD-05030110

F5



173



73441405 VS.AAL2PATH.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441406 VS.AAL2PATH.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441407 VS.AAL2PATH.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441408 VS.AAL2PATH.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441409 VS.AAL2PATH.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441410 VS.AAL2PATH.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5



174



73441411 VS.AAL2PATH.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of anAAL2 Path

BSC6910 WRFD-05030110

F5

73441412 VS.IPOAPVC.VCLPM.RXCELL

Number ofReceived VCLPM Cells on anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441413 VS.IPOAPVC.VCLPM.TXCELL

Number ofTransmittedVCL PM Cellson an IPOAPVClink

BSC6910 WRFD-05030110

F5

73441414 VS.IPOAPVC.VCLPM.PEAK.RXRATE

MaximumReceive Rate ofVCL PM on anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441415 VS.IPOAPVC.VCLPM.PEAK.TXRATE

MaximumTransmit Rate ofVCL PM on anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441416 VS.IPOAPVC.VCLPM.RX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theReceiveDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441417 VS.IPOAPVC.VCLPM.RX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theReceiveDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441418 VS.IPOAPVC.VCLPM.TX.MEAN.LOSTCELLRATE

Average VCLPM Cell DiscardRate in theTransmitDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5



175



73441419 VS.IPOAPVC.VCLPM.TX.PEAK.LOSTCELLRATE

Maximum VCLPM Cell DiscardRate in theTransmitDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441420 VS.IPOAPVC.VCLPM.RX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theReceiveDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441421 VS.IPOAPVC.VCLPM.RX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theReceiveDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441422 VS.IPOAPVC.VCLPM.TX.MEAN.ERRINSERTCELLRATE

Average Rate ofIncorrectlyInserted VCLPM Cells in theTransmitDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5

73441423 VS.IPOAPVC.VCLPM.TX.PEAK.ERRINSERTCELLRATE

Maximum Rateof IncorrectlyInserted VCLPM Cells in theTransmitDirection of anIPOAPVC link

BSC6910 WRFD-05030110

F5



176

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

WCDMA RANATM Transport Feature Parameter Description 9 Glossary


177

10 Reference Documents

1. Transmission Resource Management Feature Parameter Description

WCDMA RANATM Transport Feature Parameter Description 10 Reference Documents


178