atm transport(ran13.0 01)

7/28/2019 ATM Transport(RAN13.0 01)

1/71

ATM TransportRAN13.0

Feature Parameter Description

Issue 01

Date 2011-03-30

HUAWEI TECHNOLOGIES CO., LTD.


2/71

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

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

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase 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 orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]
http://www.huawei.com/http://www.huawei.com/mailto:[email protected]:[email protected]:[email protected]://www.huawei.com/


3/71

WCDMA RAN

ATM Transport Contents

Issue 01 (2011-03-30) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd

i

Contents

1 Introduction ................................................................................................................................ 1-11.1 Scope ............................................................................................................................................ 1-11.2 Intended Audience ........................................................................................................................ 1-11.3 Change History .............................................................................................................................. 1-1

2 Overview of ATM Transport .................................................................................................... 2-23 Protocol Stacks ......................................................................................................................... 3-1

3.1 Iub Over ATM ................................................................................................................................ 3-13.1.1 Protocol Stack ....................................................................................................................... 3-13.1.2 Links on the Iub Interface ..................................................................................................... 3-23.1.3 OM IPoA Data Configuration on the Iub Interface ................................................................ 3-2

3.2 Iu-CS over ATM ............................................................................................................................. 3-33.2.1 Protocol Stack ....................................................................................................................... 3-33.2.2 Links on the Iu-CS Interface ................................................................................................. 3-43.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8 .............................. 3-4

3.3 Iu-PS over ATM ............................................................................................................................. 3-63.3.1 Protocol Stack ....................................................................................................................... 3-63.3.2 Links on the Iu-PS Interface ................................................................................................. 3-73.3.3 IPoA Data Configuration on the Iu-PS User Plane ............................................................... 3-7

3.4 Iur over ATM .................................................................................................................................. 3-83.4.1 Protocol Stack ....................................................................................................................... 3-8

3.4.2 Links on the Iur Interface ...................................................................................................... 3-93.4.3 Configuration Principles for Static Relocation Routes over Iur ........................................... 3-10

3.5 ATM Transport Modes ................................................................................................................. 3-113.5.1 UNI Mode ........................................................................................................................... 3-113.5.2 Fractional Mode .................................................................................................................. 3-133.5.3 IMA Mode ........................................................................................................................... 3-15

3.6 Timeslot Cross Connection ......................................................................................................... 3-163.6.1 Principles of Timeslot Cross Connection ............................................................................ 3-163.6.2 Function of Timeslot Cross Connection .............................................................................. 3-17

3.7 PVC Parameters of the ATM Layer ............................................................................................. 3-183.7.1 VPI and VCI ........................................................................................................................ 3-183.7.2 Service Type ....................................................................................................................... 3-183.7.3 ATM Traffic Records ........................................................................................................... 3-19

3.8 AAL5 ............................................................................................................................................ 3-213.9 AAL2 Path ................................................................................................................................... 3-21

3.9.1 AAL2 Connections and AAL2 Path ..................................................................................... 3-213.9.2 AAL2 Route ........................................................................................................................ 3-22

3.10 MTP3 ......................................................................................................................................... 3-233.10.1 MTP3 Links ....................................................................................................................... 3-23


4/71

WCDMA RAN

ATM Transport Contents



ii

3.10.2 Types of MTP3 DSPs ....................................................................................................... 3-243.10.3 Signaling Route Mask and Signaling Link Mask .............................................................. 3-24

3.11 IPOA PVC .................................................................................................................................. 3-253.12 F5 .............................................................................................................................................. 3-25

4 ATM Transmission Resources............................................................................................... 4-15 ATM Transmission Resource Management ....................................................................... 5-16 Parameters ................................................................................................................................. 6-17 Counters...................................................................................................................................... 7-18 Glossary ...................................................................................................................................... 8-19 Reference Documents ............................................................................................................. 9-1


5/71

WCDMA RAN

ATM Transport 1 Introduction



1-1

1 Introduction

1.1 Scope

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

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics

Personnel who need to understand ATM transport

Personnel who work with Huawei products

1.3 Change History

This section provides information on the changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to the change in the ATM transport feature.

Editorial change: refers to the change in wording or the addition of the information that was notdescribed in the earlier version.

Document Issues

The document issues are as follows:

01 (2011-03-30)

Draft A (2010-12-30)

01 (2011-03-30)

This is the document for the first commercial release of RAN13.0.

Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.

Draft A (2010-12-30)

This is the draft of the document for RAN13.0.

Compared with issue 01 (2010-10-15) of RAN12.0, this issue incorporates the changes described in the

following table.

Change Type Change Description Parameter Change

Feature change None None

Editorial change The characteristic of line coding methodof E1/T1 link is added. For details, seesection Line Coding Method.

None

The description of ATM transport modesis optimized. For details, see 3.5 ATMTransport Modes.

None


6/71

WCDMA RAN

ATM Transport 2 Overview of ATM Transport



2-2

2 Overview of ATM Transport

Huawei radio access network (RAN) provides ATM-based Iub/Iu(Iu-CS and Iu-PS)/Iur interfaces andATM TRM, such as admission control based on AAL2 path bandwidth; transmission resource mapping

based on ATM QoS classes, and Iub overbooking.


7/71

WCDMA RAN

ATM Transport 3 Protocol Stacks



3-1

3 Protocol Stacks

3.1 Iub Over ATM

3.1.1 Protocol Stack

Figure 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 user plane (areaA), transport network layer control plane (area B), and 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 areas can be

carried on common physical links.

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

In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is the ATM PVC.Under the control of Q.AAL2, AAL2 connections can be dynamically set up or released for upper-layerservices. Therefore, each AAL2 path must have its corresponding controlling Q.AAL2.


8/71

WCDMA RAN




3-2

3.1.2 Links on the Iub Interface

The links on the ATM-based Iub interface are of three types: SAAL link of User-Network Interface (UNI)type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carry NCP, CCP, and ALCAP, asshown in Figure 3-2.

Figure 3-2 Links on the Iub interface

The RINT shown in Figure 3-2 refers to ATM interface boards UOIa/UOIc, AOUa/AOUc, and AEUa.

3.1.3 OM IPoA Data Configuration on the Iub Interface

On the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance (OM)channel.

OM IPoA PVC on the Iub Interface

Figure 3-3 shows the IPoA PVCs from the BSC6900 to NodeBs.

Figure 3-3 IPoA PVCs from the BSC6900 to NodeBs


9/71

WCDMA RAN




3-3


Network Segments

Each IPoA PVC travels through the following network segments before reaching the NodeB:

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

The 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface board andthe NodeBs. When setting this network segment, you need to take field conditions into consideration.

3.2 Iu-CS over ATM


Figure 3-4 shows the protocol stack for the Iu-CS interface.

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:

Transport network layer user plane (area A)

Transport network layer control plane (area B)

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 areas can becarried on common physical links.


10/71

WCDMA RAN




3-4

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

The MSC server implements the functions in area A.

The MGW implements the functions in areas B and C.

3.2.2 Links on the Iu-CS Interface

The Iu-CS links on the CN side are of two types: MTP3 link and AAL2 path. Figure 3-5 shows the linkson the ATM-based Iu-CS interface.

Figure 3-5 Links on the Iu-CS Interface

The RINT shown in Figure 3-5 refers to ATM interface boards of the BSC6900. The UOIa/UOIc board is recommendedwhen ATM transport is applied to the Iu-CS interface.

3.2.3 Differences of the Iu-CS Interface Between R99 and

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

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8

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


11/71

WCDMA RAN




3-5

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 BSC6900. Data is forwarded betweenthe MSC server and the BSC6900 through the routes configured on the MGW. Figure 3-7 shows anexample 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 BSC6900

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

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

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

MGW (also called Iu-CS ALCAP signaling point)


12/71

WCDMA RAN




3-6

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 R99Type Iu-CS RANAP signaling point and Iu-CS ALCAP signaling point Iu-CS signaling point

Quantity More than one One

3.3 Iu-PS over ATM


Figure 3-8 shows the protocol stack for the Iu-PS interface.

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

The transport network layer of the Iu-PS interface consists of the transport network layer user plane(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 can becarried on common physical links.


13/71

WCDMA RAN




3-7

3.3.2 Links on the Iu-PS Interface

The Iu-PS links on the CN side are of two types: MTP3 link and IPoA PVC. Figure 3-9 shows the links onthe ATM-based Iu-PS interface.

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

The RINT shown in Figure 3-9 refers to the UOIa/UOIc board.

3.3.3 IPoA Data Configuration on the Iu-PS User Plane

On the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.

IPoA PVC on the Iu-PS User Plane

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

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


14/71

WCDMA RAN




3-8


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

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) Device IP address on the ATM interface board of theBSC6900

Peer IP address of the IPoA PVC(PEERIPADDR)

IP address of the gateway on the SGSN side

PVC between the interface board carryingthe IPoA data and the gateway on the SGSN

side

-

Route between the interface board carryingthe IPoA data and the network segment ofthe peer SGSN

If the IP address of the interface board carrying the IPoAdata and the IP address of the peer SGSN are located ondifferent subnets, routes to the destination IP addressneed to be configured at the BSC6900.DSTIPis the IPaddress of the SGSN, andNEXTHOPis the IP address ofthe gateway on the SGSN side.

On the Iu-PS interface, the SGSN must be configured with routes to the network segment to which the IP address of theBSC6900 interface board belongs. The next hop is the gateway on the BSC6900 side. Otherwise, PS services cannot beprovided.

3.4 Iur over ATM


Figure 3-11 shows the protocol stack for the Iur interface.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peeripaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peeripaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peeripaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_nexthop.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_nexthop.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_nexthop.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_nexthop.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peeripaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.html


15/71

WCDMA RAN




3-9

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:

Transport network layer user plane (area A)

Transport network layer control plane (area B)

Transport network layer user plane (area C)

3.4.2 Links on the Iur Interface

The Iur links are of two types: MTP3 link and AAL2 path. Figure 3-12 shows the links on the ATM-basedIur interface.


16/71

WCDMA RAN




3-10

Figure 3-12 Links on the Iur interface


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 the localBSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisites forconfiguring IP routes on the Iur interface are that the IP paths between the local BSC6900 and the SGSN,between the neighboring BSC6900 and the SGSN, and between the serving BSC6900 and the driftBSC6900 are configured.

Figure 3-13 shows the configuration of IP routes on the Iur interface. The IP routes configured in multiplesubsystems are similar.


17/71

WCDMA RAN




3-11

Figure 3-13 IP route configuration on the Iur interface

The RINT shown in Figure 3-13 refers to IP interface boards PEUa, POUa/POUc, UOIa (UOIa_IP), FG2a/FG2c, andGOUa/GOUc.

3.5 ATM Transport Modes

ATM transport has three modes: UNI, fractional, and IMA.

3.5.1 UNI Mode

Principles of UNI Mode

The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of the physical layer.

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


18/71

WCDMA RAN




3-12

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 clock mode.The related parameters are as follows:

Scrambling switch: specifies whether to enable scrambling.

Line coding method: specifies the line coding method.

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 of E1/T1must be identical.

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

Table 3-3 Parameters correspond to UNI mode

NE Scrambling Switch Line Coding Method 16-Timeslot Switch

RNC SCRAMBLESW PTCODE TS16ENABLE

NodeBSCRAM LNCODE TS16

Clock Mode

There are two clock modes on the RNC side:

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

Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an IMA group arederived from at least two clock sources. The loopback clock mode is a special case of the ITC mode.

The clock mode on the RNC is not configurable, and the default clock mode on the RNC side is CTC.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/UNILNK-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.html


19/71

WCDMA RAN




3-13

The clock mode on the NodeB side is specified by the parameterCLKM(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 method:

HDB3 (for E1 port)

AMI (for E1/T1 port)

AMI_ZCS (for E1/T1 port)

B8ZS (for T1 port)

The coding methods of E1 port are HDB3 and AMI, and the HDB3 is recommended. HDB3 representshigh-density bipolar code. It is not easy to be interfered, and the transmission distance is about severalkilometers.

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

3.5.2 Fractional Mode

Fractional mode (WRFD-050302 Fractional ATM Function on Iub Interface) is applicable to theTransmission Convergence (TC) sublayer of the physical layer. This section describes the principles andfunctions of fractional ATM, introduces the two implementation modes (that is, fractional IMA andfractional ATM), and provides the principles for configuring fractional IMA links and fractional ATM links.

Principles of Fractional ATM

In the case of fractional ATM, multiple timeslots out of the 32 timeslots on an E1 (or 24 timeslots on a T1)are used to transmit an ATM cell. At the transmission end, an ATM cell is mapped to multiple timeslots

among the 31 timeslots on an E1 (or 24 timeslots on a T1). At the reception end, the ATM cell is restoredfrom the associated timeslots on the E1/T1. Figure 3-15 shows the fractional ATM mode. An E1 framehas timeslots numbered from 0 to 31. All the timeslots except timeslot 0 are available for service datatransmission. A T1 frame has timeslots numbered from 1 to 24. All the timeslots are available for servicedata transmission. The timeslots to which the ATM cell is not mapped can transmit other data.

Figure 3-15 Fractional ATM mode

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

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


http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-ClockMode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-ClockMode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-ClockMode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-ClockMode.html


20/71

WCDMA RAN




3-14

E1/T1 timeslot: specifies the timeslot used to transmit the ATM cell.

The setting of scrambling switch, line coding method, and E1/T1 timeslot at both ends of E1/T1 must beidentical.

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

NE Scrambling Switch Line Coding Method E1/T1 Timeslot

RNC SCRAMBLESW PTCODE TSBITMAP

NodeB SCRAM LNCODE TSN

Function of Fractional ATM

After the fractional ATM function is enabled, the ATM cells of a 3G network can be transmitted over anexisting 2G network, as shown in Figure 3-16.

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:

Fractional ATM

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

Fractional IMA

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

The parameterFRALNKTis used to specify the fractional link mode on the RNC side.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_tsbitmap.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_tsbitmap.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-TIMESLICE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-TIMESLICE.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-TIMESLICE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/FRAATM-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_tsbitmap.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.html


21/71

WCDMA RAN




3-15

The fractional ATM/IMA mode are applicable only to the AEUa/AOUc board.

3.5.3 IMA Mode

Overview

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

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

Principles of IMA Mode

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

At the transmission end, the IMA group receives the ATM cell stream from the ATM layer anddistributes the cells among the E1/T1 links.

At the reception end, the IMA group reassembles the cells to restore the original ATM cell stream, andthen transfers the cell stream to the ATM layer.

The physical layer provides high-speed transport channels for ATM cells from the perspective of the ATMlayer.

Figure 3-17 Principles of the IMA mode

In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frame to implementnecessary controlling functions.

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

Figure 3-18 shows an IMA frame. The mapping between the ATM cell and the physical link (that is, theE1/T1 link) is similar to that in UNI mode.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.html


22/71

WCDMA RAN




3-16

Figure 3-18 IMA frame

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



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 of E1/T1 mustbe identical.

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

Table 3-5 Parameters correspond to IMA mode

NE Scrambling Switch Line Coding Method 16-Timeslot Switch

RNC SCRAMBLESW PTCODE TS16ENABLE

NodeB SCRAM LNCODE TS16

3.6 Timeslot Cross Connection

The timeslot cross connection function implements cross connections between timeslots on two E1/T1s

at the physical medium (PM) sublayer of the physical layer.

3.6.1 Principles of Timeslot Cross Connection

Figure 3-19 shows an example of timeslot cross connection. The timeslot cross connection devicecross-connects the timeslots on one E1/T1 to the timeslots on the other E1/T1. In the example shown inthe following figure, the device cross-connects slots 2 and 3 on one E1/T1 to slots 4 and 8 on anotherE1/T1 respectively.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-TS16.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-SCRAM.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ts16enable.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_ptcode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/e1t1_scramblesw.html


23/71

WCDMA RAN




3-17

Figure 3-19 Example of timeslot cross connection

3.6.2 Function of Timeslot Cross Connection

The AEUa/PEUa/POUc board supports timeslot cross connection. Through the configured timeslot crossconnection, 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 the2G equipment or NodeB monitoring equipment.

Figure 3-20 shows implementation of timeslot cross connection.

Figure 3-20 Implementation of timeslot cross connection

Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by other applications, suchas 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 othertimeslots on this E1 link can carry fractional ATM or fractional IMA links.

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


24/71

WCDMA RAN




3-18

SRCPORTNO: specifies the source port to perform the timeslot-cross connection function.

SRCTSMASK: specifies the timeslots occupied by the source port.

DSTPORTNO: specifies the destination port to perform the timeslot-cross connection function.

DSTTSMASK: specifies the timeslots occupied by the destination port.

3.7 PVC Parameters of the ATM Layer

For configuring the IPoA PVCs, AAL2 paths, SAAL links, or VPCLCX links, the PVC parameters need tobe set.

3.7.1 VPI and VCI

The main characteristics of the ATM technology are multiplexing, switching, and transmitting of ATMcells. All these operations are performed over Virtual Channels (VCs). A VC and a Virtual Path (VP) areidentified by Virtual Channel Identifier (VCI) and Virtual Path Identifier (VPI) respectively.

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

A VC is identified by a VCI. It is a logical connection between ATM nodes and is the channel fortransmitting ATM cells between two or more nodes. The VC is used for the data transmission betweenmobile terminals, between networks, or between mobile terminal and network.

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

Figure 3-21 Relation between VC and VP

3.7.2 Service Type

The ATM services are of five types (WRFD-05030107 CBR, RT-VBR, NRT-VBR, UBR ATM QoS Classes,WRFD-050305 UBR+ ATM QoS Class): Constant Bit Rate (CBR), Real-Time Variable Bit Rate (RT-VBR),Non-Real-Time Variable Bit Rate (NRT-VBR), Unspecified Bit Rate (UBR), and UBR_PLUS (UBR+).

Table 3-6 describes the types of service.

Table 3-6 Types of service

Type of Service Description

CBR No error check, flow control, or other processing

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

NRT-VBR Rate of a service that is applicable to timing transmission. A service of this type, forexample, e-mail, is relatively insensitive to delivery time or delay.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srcportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srcportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srctsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srctsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srctsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_srcportno.html


25/71

WCDMA RAN




3-19

Type of Service Description

UBR Rate of a service with no commitment to transmission and no feedback oncongestion. This type of service is ideal for the transmission of IP datagrams. Incongestion, UBR cells are discarded, and no feedback or request for slowing downthe data rate is delivered to the transmission end.

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 the case of Iub transmissionresource congestion, and the best effort service of UBR+ uses the transmissionbandwidth completely.

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

Table 3-7 Characteristics of different ATM services

Characteristic CBR RT-VBR NRT-VBR UBR UBR+

Bandwidth guarantee Yes Yes Yes No Yes

Applicability to real-timecommunication

Yes Yes No No No

Applicability to bursts ofcommunication

No Yes Yes No No

Feedback on congestion No No No No No

The ATM service type is also called ATM QoS class. The CBR, RT-VBR, NRT-VBR, or UBR ATM QoSclasses can be configured for AAL2 path, and the UBR+ ATM QoS class is generally used for Iub OAMconnection.

The service types carried on the AAL2 paths can be determined by running the ADD ATMTRF command,and then the mapping between the service types and the transmission resources for the adjacent nodecan be configured by running the ADD TRMMAP command.

3.7.3 ATM Traffic Records

The ATM traffic records are public resources, which can be used by the IPoA PVCs, AAL2 paths, SAALlinks, and VPCLCX links. You need to add the traffic record at the BSC6900 based on the traffic model ofthe link on the Iub/Iu-CS/Iu-PS/Iur interface. The ATM traffic records can be configured by the ADDATMTRF command.

Traffic Parameters

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

Table 3-8 describes the ATM traffic parameters.

Table 3-8ATM traffic parameters

Parameter ID Description

TRFX Identifies a traffic record.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_trfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_trfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_trfx.html


26/71


27/71

WCDMA RAN




3-21

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

The ATM traffic parameters, such asPCRandSCR, should be configured depending on the traffic model in use.

When configuring ATM traffic records for links, you need to consider the traffic on the interface boards of the BSC6900.

3.8 AAL5

In ATM transport mode, AAL5 connections are used to carry the signaling on the Iub/Iur/Iu interface(WRFD-05030105 permanent AAL5 connections for control plane traffic). As defined in 3GPPspecifications, UNI-SAAL is used for control plane connections on the Iub interface, and NNI-SAAL isused for control plane connections on the Iur and Iu interfaces. The AAL5 connections for Iub/Iu-CS/Iurare set up by configuring the SAAL links.

You can run the ADD SAALLNK command to configure the AAL5 connections on the Iub/Iur/Iu-CSinterface. On the RNC side, when an AAL5 connection is configured, theTXTRFXandRXTRFXparameters need to be set. TheTXTRFXandRXTRFXparameters record the ATM traffic, and they canbe configured through the ADD ATMTRF command.

An SAAL link is carried on an ATM PVC. The parametersCARRYVPIandCARRYVCIare used toidentify the PVCs on the RNC side, and the parametersVP IandVCIare used to identify the PVCs onthe NodeB side. The PVC identifier and other PVC attributes must be negotiated between the BSC6900and the peer end.

The signaling messages carried on the UNI-SAAL links are classified into NCP, CCP, and ALCAP, andthe signaling messages carried on the NNI-SAAL links are MTP3, as described in Table 3-10.

Table 3-10 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 Iubinterface may have multiple CCPs. The number of CCPs depends on network 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 the SAAL links ofNetwork-to-Network Interface (NNI) type.

3.9 AAL2 Path

3.9.1 AAL2 Connections and AAL2 Path

The Q.AAL2 module is responsible for dynamically setting up and releasing AAL2 connections betweenthe BSC6900 and the peer end. The peer end can be a NodeB, a CS CN node, or a neighboringBSC6900.PATHIDspecifies the ID of an AAL2 path, and thePATHIDof the same AAL2 path configuredbetween two AAL2 nodes must be the same.An AAL2 path contains multiple AAl2 connections. CIDspecifies the ID of an AAL2 connection on the path. The CID state can be Busy or Idle. If the CID is in thebusy state, the CID 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 Dynamic AAL2Connections on Iub/IuCS/Iur Interface).

Figure 3-22 shows the relation between an AAL2 path and AAL2 connections on the Iub interface.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_pcr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_pcr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_pcr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_scr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_scr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_scr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_pathid.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_scr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_pcr.html


28/71

WCDMA RAN




3-22

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

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

CBR

RT-VBR

NRT-VBR

UBR

According to different types of service (R99, HSDPA, and HDUPA), the following types of AAL2 path canbe configured:

R99

HSPA

SHARE

The AAL2 path can be configured through the ADD AAL2PATH command. On the RNC side, when an

AAL2 path is configured, theTXTRFXandRXTRFXparameters need to be set. They determine the typeof path. TheTXTRFXandRXTRFXparameters record the ATM traffic, and they can be configuredthrough the ADD ATMTRF command. For details, see section 3.7.3 "ATM Traffic Records."

An AAL2 path is carried on a PVC. The parametersVP IandVCIare used to identify the PVCs. The PVCidentifier and other PVC attributes must be negotiated between the BSC6900 and the peer end.

3.9.2 AAL2 Route

An AAL2 path may reach not the destination node but an adjacent node. In this case, AAL2 routes canbe configured to reach the destination node. The AAL2 route to an ATM node can be configured throughthe ADD AAL2RT command.

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

Figure 3-23 Example of the AAL2 route
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_vpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/aal2path_txtrfx.html


29/71

WCDMA RAN




3-23

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

The AAL2 route cannot be configured for the adjacent node of the IUPS type.

3.10 MTP33.10.1 MTP3 Links

MTP3 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 to specify an MTP3link set, and then run the command ADD MTP3LNK to add the MTP3 links by using the parameterSIGLKSX.

MTP3 Links for Iu-CS Interface

The configuration of MTP3 links between the BSC6900 and the MSC server depends on the networkingbetween the MSC server and the BSC6900:

If the MSC server is directly connected to the BSC6900, at least one MTP3 link is required for the MSCserver (IUCS_RANAP signaling point). It is recommended that more than one MTP3 link beconfigured.

If the MSC server is connected to the BSC6900 through the MGW, the MSC server (IUCS_RANAPsignaling point) does not require any MTP3 link.

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

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

MTP3 Links for Iu-PS Interface

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

MTP3 Links for Iur Interface

The configuration of MTP3 links depends on the networking between the BSC6900 and the neighboringBSC6900:

If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requires at leastone MTP3 link. It is recommended that more than one MTP3 link be configured.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/mtp3lnk_siglksx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/mtp3lnk_siglksx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/mtp3lnk_siglksx.html


30/71

WCDMA RAN




3-24

If the BSC6900 is connected to the neighboring BSC6900 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 SPU subsystems in theMPS/EPS so that the signaling exchange can be reduced between the SPU subsystems.

3.10.2 Types of MTP3 DSPs

The BSC6900 supports seven types of Destination Signaling Point (DSP): IUCS, IUCS_ALCAP,IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different types have different meanings.

Table 3-11 describes the types of DSP.

Table 3-11 Types of DSP

DSP Type Description

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

IUCS_ALCAP R4 MGW DSP. The IUCS_ALCAP DSP has the control plane functions of thetransport network layer on the Iu-CS interface.

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 BSC6900 signaling points

STP Signaling transfer point

AAL2SWITCH AAL2 transfer point

3.10.3 Signaling Route Mask and Signaling Link Mask

The number (represented by n) of 1s in a signaling route mask determines the maximum number ofroutes (2

n). For example, B0000 indicates that there is at most one route. B0001 or B1000 indicates that

there are at most two routes.

The number (represented by n) of 1s in a signaling link mask determines the maximum number of links(2

n). For example, B0000 indicates that there is at most one link. B0001 or B1000 indicates that there

are at most two links.

The result of the logical AND operation on the signaling link mask and the signaling route mask must be0, as shown in Figure 3-18.

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


31/71

WCDMA RAN




3-25

3.11 IPOA PVC

IPOA 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 the Iub interface are usedto transmit the OM information of a NodeB. In this case, the IPoA PVC is called the management planeIPoA PVC. The IPoA PVC on the Iu-PS interface is a PVC to the SGSN gateway.

The IPOA PVC can be configured through the ADD IPOAPVC command. If the parameterPEERTis setto IUB, the IPOA link can only be used as an OM channel. The parametersCARRYVPIandCARRYVCIare used to identify the PVCs.

When an IPOA PVC is configured, theTXTRFXandRXTRFXparameters need to be set. TheTXTRFXandRXTRFXparameters record the ATM traffic, and they can be configured through the ADD ATMTRFcommand.

3.12 F5

Huawei supports operations on ATM OAM F5 end-to-end flows specified in ITU I.610 (WRFD-05030110

F5):

Fault management

AIS: alarm indication signal

RDI: remote defect indication

CC: continuity check and loopback

Performance management

Forward monitoring

Backward reporting

Activation and deactivation

The CC can be activated to monitor the end-to-end AAL2 path virtual connect link (VCL) and Iu-PS userplane VCL. When one VCL for AAL2 path or Iu-PS GTPU is loss of continuity (LOC), AIS, or RDI, thisVCL is blocked. Then the service is established on other alternative VCLs to prevent the failure of thecall. You can run the SET VCLLOP command to activate or deactivate the CC function. When theparameterLOPTis set to LOCAL_LOOP, and the LOP VCL command is executed, the CC function isactivated. When the parameterLOPTis set to NO_LOOP, the CC function is deactivated.

Huawei also supports proprietary delay detection function. When an NE receives a detection startcommand from the NMS, it starts detecting delay on the current AAL2 link or AAL5 link and periodicallyreports the delay to the NMS. The 8-byte reserved IE (LB IE) in the loopback message is used to storethe message transmission time. When an NE receives the loopback message, it calculates the delaybased on the time difference between transmission and reception.
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peert.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peert.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peert.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/vcllop_lopt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_rxtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_txtrfx.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_peert.html


32/71

WCDMA RAN

ATM Transport 4 ATM Transmission Resources



4-1

4 ATM Transmission Resources

ATM transmission resources can be classified into physical resources, logical ports, resource groups,and paths. The transmission resources for Iub/Iu/Iur interfaces vary according to different networking.

Huawei supports the following types of ATM transmission:

ATM over E1T1 on Iub interface (WRFD-05030101 ATM over E1T1 on Iub interface)

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

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

For details about the ATM transmission resources, see "Transmission Resources" in theTransmissionResource Management Feature Parameter Description.
http://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htm


33/71

WCDMA RAN

ATM Transport 5 ATM Transmission Resource Management



5-1

5 ATM Transmission Resource Management

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

Admission control (WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth), which isused to allow more users to be admitted with the QoS guaranteed.

Transmission resource mapping, in which the CBR, RT-VBR, NRT-VBR, and UBR ATM QoS classesare used to implement differentiated services.

Iub overbooking (WRFD-050405 Overbooking on ATM Transmission, WRFD-050406 ATM QoSIntroduction on Hub Node B (Overbooking on Hub Node B Transmission)), which is used to improvethe usage efficiency on ATM transport scenario

For details about admission control, transmission resource mapping, and Iub overbooking, see theTransmission Resource Management Feature Parameter Description.
http://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htmhttp://localhost/var/www/apps/conversion/tmp/scratch_12/Transmission%20Resource%20Management.htm


34/71

WCDMA RAN

ATM Transport 6 Parameters



6-1

6 Parameters

Table 6-1 Parameter description

Parameter ID NE MML Command DescriptionCARRYVCI BSC6900 ADD

SAALLNK(Mandatory)

MOD SAALLNK(Optional)

Meaning: VCI value of theSAAL out BSC6900

GUI Value Range:32~65535

Actual Value Range:32~65535

Default Value: None

CARRYVCI BSC6900 ADD IPOAPVC(Optional)

MOD IPOAPVC(Optional)

Meaning: VCI value of theVCL of the bearer network



Default Value: None

CARRYVPI BSC6900 ADD IPOAPVC(Optional)

MOD IPOAPVC(Optional)

Meaning: VPI value of theVCL of the bearer network


Actual Value Range:

0~4095Default Value: None

CARRYVPI BSC6900 ADDSAALLNK(Mandatory)

MOD SAALLNK(Optional)

Meaning: VPI value of theSAAL out BSC6900



Default Value: None

CDVT BSC6900 ADD ATMTRF(Optional) Meaning: Tolerable delay

itter



Default Value: 1024

CLKM NodeB ADD IMAGRP

MOD IMAGRP

Meaning: Indicates theclock mode of the IMAgroup. Links in an IMAgroup may pass through

different transport
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_cdvt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_cdvt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-atmtrf.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-atmtrf.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/mod_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/mod_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/mod_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/IMAGRP-CLOCKMODE.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-atmtrf.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/atmtrf_cdvt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvpi.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_carryvci.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-saallnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/saallnk_carryvci.html


35/71


36/71

WCDMA RAN




6-3

Parameter ID NE MML Command Description

MASTER, SLAVE

Default Value:SLAVE(Slave Mode)

DSTIP BSC6900 ADD IPRT(Mandatory)

RMV IPRT(Mandatory)

MOD IPRT(Mandatory)

Meaning: Destination IPaddress

GUI Value Range: None

Actual Value Range:0.0.0.0~255.255.255.255

Default Value: None

DSTPORTNO BSC6900 ADDTSCROSS(Mandatory)

Meaning: Destination ofthe timeslot crossconnection

GUI Value Range: 0~335Actual Value Range:0~335

Default Value: None

DSTTSMASK BSC6900 ADDTSCROSS(Mandatory)

Meaning: Target timeslotmask

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),
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dsttsmask.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-tscross.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/tscross_dstportno.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-iprt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/iprt_dstip.html


37/71

WCDMA RAN




6-4


TS30(Time_slot_30),TS31(Time_slot_31)

Actual 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,TS31

Default Value: None

FRALNKT BSC6900 ADDFRALNK(Mandatory)

Meaning: Fractional linktype

GUI Value Range:FRAATM, FRAIMA

Actual Value Range:FRAATM, FRAIMA

Default Value: None

FRMLEN BSC6900 ADD IMAGRP(Optional)

MOD IMAGRP(Optional)

Meaning: Frame length. Alonger frame improves thetransmission efficiency,but at the same timereduces the sensitivity toerrors.

GUI Value Range: D32,D64, D128, D256

Actual Value Range: D32,D64, D128, D256

Default Value: D128

IPADDR BSC6900 ADDIPOAPVC(Mandatory)

RMVIPOAPVC(Mandatory)

MODIPOAPVC(Mandatory)

Meaning: Local IPaddress

GUI Value Range: None

Actual Value Range:

0.0.0.0~255.255.255.255Default Value: None

LNCODE NodeB ADD E1T1

SET E1T1

Meaning: Indicates theline coding mode of anE1/T1 port.

GUI Value Range:HDB3(E1 HDB3 Code),AMI(E1/T1 AMI Code),B8ZS(T1 B8ZS Code),UNKNOWN(Unknown)

Actual Value Range:

HDB3, AMI, B8ZS,
http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-fralnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-fralnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-fralnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_e1t1.htmlhttp://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/E1T1-LineCode.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/rmv-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ipoapvc.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ipoapvc_ipaddr.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-imagrp.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/imagrp_frmlen.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-fralnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-fralnk.htmlhttp://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/fralnk_fralnkt.html


38/71

WCDMA RAN




6-5


UNKNOWN

Default Value: None

LOPT BSC6900 SET VCLLOP(Mandatory)Meaning: This parameterspecifies the loopbacktype.

GUI Value Range:NO_LOOP(No loop),LOCAL_LOOP(Localloop)

Actual Value Range:NO_LOOP,LOCAL_LOOP

Default Value: None

MBS BSC690