atm transport(ran15.0 01)

8/13/2019 ATM Transport(RAN15.0 01)

1/184

WCDMA RAN

ATM Transport Feature Parameter

Description

Issue 01

Date 2013-04-28

HUAWEI TECHNOLOGIES CO., LTD.


2/184

Copyright Huawei Technologies Co., Ltd. 2013. 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 or representations

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 a 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]

Issue 01 (2013-04-28) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/184

Contents

1 Introduction....................................................................................................................................1

1.1 Scope..............................................................................................................................................................................1

1.2 Intended Audience..........................................................................................................................................................1

1.3 Change History...............................................................................................................................................................1

2 Overview of ATM Transport.......................................................................................................3

3 Protocol Stacks...............................................................................................................................4

3.1 Iub Over ATM................................................................................................................................................................4

3.1.1 ProtocolStack..............................................................................................................................................................4

3.1.2 Links onthe Iub Interface............................................................................................................................................5

3.1.3 OM IPoA Data Configuration on the Iub Interface.....................................................................................................5

3.2 Iu-CS over ATM.............................................................................................................................................................6

3.2.1 ProtocolStack..............................................................................................................................................................6

3.2.2 Links onthe Iu-CS Interface.......................................................................................................................................7

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

3.3 Iu-PS over ATM...........................................................................................................................................................10

3.3.1 ProtocolStack............................................................................................................................................................10

3.3.2 Links onthe Iu-PS Interface......................................................................................................................................11

3.3.3 IPoA Data Configuration on the Iu-PS User Plane...................................................................................................11

3.4 Iur over ATM................................................................................................................................................................13

3.4.1 ProtocolStack............................................................................................................................................................13

3.4.2 Links onthe Iur Interface..........................................................................................................................................13

3.4.3 Configuration Principles for Static Relocation Routes over Iur................................................................................143.5 ATM Transport Modes.................................................................................................................................................15

3.5.1 UNI Mode..................................................................................................................................................................15

3.5.2 Fractional Mode.........................................................................................................................................................17

3.5.3 IMA Mode.................................................................................................................................................................20

3.6 Timeslot Cross Connection..........................................................................................................................................21

3.6.1 Principles of Timeslot Cross Connection..................................................................................................................22

3.6.2 Function of Timeslot Cross Connection....................................................................................................................22

3.7 PVC Parameters of the ATM Layer.............................................................................................................................23

3.7.1 VPI and VCI..............................................................................................................................................................23

3.7.2 Service Type..............................................................................................................................................................23

WCDMA RAN

ATM Transport Feature Parameter Description Contents



ii


4/184

3.7.3 ATM Traffic Records................................................................................................................................................25

3.8 AAL5............................................................................................................................................................................27

3.9 AAL2 Path....................................................................................................................................................................27

3.9.1 AAL2 Connections and AAL2 Path..........................................................................................................................28

3.9.2 AAL2 Route..............................................................................................................................................................29

3.10 MTP3..........................................................................................................................................................................29

3.10.1 MTP3 Links.............................................................................................................................................................29

3.10.2 Types of MTP3 DSPs..............................................................................................................................................30

3.10.3 Signaling Route Mask and Signaling Link Mask....................................................................................................31

3.11 IPOA PVC..................................................................................................................................................................31

3.12 F5................................................................................................................................................................................32

4 ATM Transmission Resources..................................................................................................33

5 ATM Transmission Resource Management...........................................................................34

6 Engineering Guidelines.............................................................................................................35

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

6.1.1 Requirements.............................................................................................................................................................35

6.1.2 Procedure...................................................................................................................................................................35

6.1.3 MML Command Examples.......................................................................................................................................37

6.2 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic..............................................................37

6.2.1 Requirements.............................................................................................................................................................37

6.2.2 Procedure...................................................................................................................................................................37


6.3 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth................................................................39

6.3.1 Requirements.............................................................................................................................................................39

6.3.2 Procedure...................................................................................................................................................................39


6.4 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes.........................................................................40

6.4.1 Requirements.............................................................................................................................................................40

6.4.2 Procedure...................................................................................................................................................................40


6.5 WRFD-05030110 F5....................................................................................................................................................416.5.1 Requirements.............................................................................................................................................................41

6.5.2 Procedure...................................................................................................................................................................42


6.6 WRFD-050305 UBR+ ATM QoS Class......................................................................................................................43

6.6.1 Requirements.............................................................................................................................................................43

6.6.2 Procedure...................................................................................................................................................................43


7 Parameters.....................................................................................................................................44

8 Counters........................................................................................................................................95

WCDMA RAN




iii


5/184

9 Glossary.......................................................................................................................................178

10 Reference Documents.............................................................................................................179

WCDMA RAN




iv


6/184

1Introduction

1.1 Scope

This document merges the basic ATM transport principle. It describes protocol stacks,

transmission resources, transmission resource management (TRM), and associated parameters.

1.2 Intended Audience

This document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

1.3 Change History

This section provides information about the changes in different document versions. There are

two types of changes, which are defined as follows:

l Feature change

Changes in features of a specific product version

l Editorial change

Changes in wording or addition of information that was not described in the earlier version

01 (2013-04-28)

This issue does not include any changes.

Draft A (2013-01-30)

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

the following changes.

WCDMA RAN

ATM Transport Feature Parameter Description 1 Introduction



1


7/184

Change Type Change Description Parameter Change

Feature change None None

Editorial change Added the differences

between the BSC6900 and

BSC6910 to the following

chapters and sections: 2

Overview of ATM

Transport, 3.1 Iub Over

ATM,3.2 Iu-CS over ATM,

3.4 Iur over ATM, 3.5.2

Fractional Modeand 3.6.2

Function of Timeslot Cross

Connection.

None

WCDMA RAN

ATM Transport Feature Parameter Description 1 Introduction



2


8/184

2Overview of ATM TransportHuawei radio access network (RAN) provides ATM-based Iub/Iu(Iu-CS and Iu-PS)/Iur

interfaces and ATM TRM, such as admission control based on AAL2 path bandwidth;

transmission resource mapping based on ATM QoS classes, and Iub overbooking.

NOTE

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

WCDMA RAN

ATM Transport Feature Parameter Description 2 Overview of ATM Transport



3


9/184

3Protocol Stacks

3.1 Iub Over ATM

3.1.1 Protocol Stack

Figure 3-1shows the protocol stack for the ATM-based Iub interface.

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

The transport network layer of the Iub interface consists of the transport network layer control

plane (area A), transport network layer control plane (area B), and transport network layer user

plane (area C).

WCDMA RAN

ATM Transport Feature Parameter Description 3 Protocol Stacks



4


10/184

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

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 the

Communication 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 the

ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up

or released for upper-layer services. Therefore, each AAL2 path must have its

corresponding controlling Q.AAL2.

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, as shown in Figure 3-2.

Figure 3-2Links on the Iub interface

NOTE

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

BSC6900, UOIc/AOUc for BSC6910.

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-3shows the IPoA PVCs from the RNC to NodeBs.

WCDMA RAN




5


11/184

Figure 3-3IPoA PVCs from the RNC to NodeBs

NOTE

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

BSC6900, UOIc/AOUc for BSC6910.

Network Segments

Iub 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 the

ATM interface board. This network segment is set before delivery of the BSC6900.

l The 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface

board and the NodeBs. When setting this network segment, you need to take field conditionsinto consideration.

3.2 Iu-CS over ATM


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

WCDMA RAN




6


12/184

Figure 3-4Protocol 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 areas

can 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 as

follows:

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 Interface

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

the links on the ATM-based Iu-CS interface.

WCDMA RAN




7


13/184

Figure 3-5Links on the Iu-CS Interface

NOTE

The RINT shown in Figure 3-5refers to ATM interface boards UOIa/UOIc for BSC6900, UOIc for

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

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

WCDMA RAN




8


14/184

Figure 3-6Iu-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 forwarded

between the MSC server and the RNC through the routes configured on the MGW. Figure

3-7shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/

R7/R8.

Figure 3-7Example 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 of

Iu-CS signaling point:

WCDMA RAN




9


15/184

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

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

Table 3-1describes the differences between signaling point configuration in R99 and that in

R4/R5/R6/R7/R8.

Table 3-1Differences 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 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-8shows the protocol stack for the Iu-PS interface.

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

WCDMA RAN




10


16/184

The transport network layer of the Iu-PS interface consists of the transport network layer control

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

be carried on common physical links.

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-9shows

the links on the ATM-based Iu-PS interface.

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

NOTE

The RINT shown in Figure 3-9refers 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-10shows the IPoA PVC on the Iu-PS user plane.

WCDMA RAN




11


17/184

Figure 3-10IPoA 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-2describes the IPoA data to be configured on the user plane of the ATM-based Iu-PS

interface.

Table 3-2IPoA 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 the

IPoA data and the gateway on the SGSN side

-

Route between the interface board carrying

the IPoA data and the network segment of the

peer SGSN

If the IP address of the interface board

carrying the IPoA data and the IP address of

the peer SGSN are located on different

subnets, routes to the destination IP addressneed to be configured at the RNC. DSTIP

(BSC6900,BSC6910)is the IP address of the

SGSN, and NEXTHOP

(BSC6900,BSC6910)is the IP address of the

gateway on the SGSN side.

NOTE

On the Iu-PS interface, the SGSN must be configured with routes to the network segment to which the IP

address of the RNC interface board belongs. The next hop is the gateway on the RNC side. Otherwise, PSservices cannot be provided.

WCDMA RAN




12


18/184

3.4 Iur over ATM


Figure 3-11shows the protocol stack for the Iur interface.

Figure 3-11Protocol 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 Interface

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

ATM-based Iur interface.

WCDMA RAN




13


19/184

Figure 3-12Links on the Iur interface

NOTE

The RINT shown in Figure 3-12refers to ATM interface boards UOIa/UOIc for BSC6900, UOIc for

BSC6910.

3.4.3 Configuration Principles for Static Relocation Routes over Iur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network

Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the

local RNC to the SGSN and then tothe neighboring RNC. Therefore, the prerequisites for

configuring IP routes on the Iur interface are that the IP paths between the local RNC and the

SGSN, between the neighboring RNC and the SGSN, and between the serving RNC and the

drift RNC are configured.

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

in multiple subsystems are similar.

WCDMA RAN




14


20/184

Figure 3-13IP route configuration on the Iur interface

NOTE

The RINT shown in Figure 3-13refers to Iu-PS IP interface boards GOUa/GOUc, FG2a/FG2c, and UOIa

(UOIa_IP) for BSC6900, GOUc/FG2c/EXOUa for BSC6910.

3.5 ATM Transport Modes

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

are sequentially mapped to the valid timeslots on the E1/T1 frame. Figure 3-14shows the

mapping between the ATM cell and the E1 timeslots in UNI mode. The 53 bytes of the ATM

cell are sequentially carried on E1 timeslots. Each E1 frame provides 31 timeslots (with slot 0

unavailable) for carrying the ATM cell.

WCDMA RAN




15


21/184

Figure 3-14Mapping 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 of

E1/T1 must be identical.

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

Table 3-3Parameters correspond to UNI mode

NE Scrambling Switch

Line CodingMethod

16-TimeslotSwitch

RNC SCRAMBLESW

(BSC6900,BSC6910

)

PTCODE TS16ENABLE

NodeB SCRAM LNCODE TS16

Note:

WCDMA RAN




16


22/184

Only AEUa support the parameterPTCODEand 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 one

clock source. The clock source may be extracted from the same external clock or from a

link.

l Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an

IMA group are derived 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.

The clock mode on the NodeB side is specified by the parameter CLKM(UNI mode/fractional

mode)/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 distance

is several kilometers.

The coding methods of T1 port are B8ZS and AMI, and B8ZS is recommended. It helps prevent

clock signals 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

the Transmission Convergence (TC) sublayer of the physical layer. This section describes the

principles 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 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 restored from the associated timeslots on the E1/T1. Figure 3-15shows

the fractional ATM mode. An E1 frame has timeslots numbered from 0 to 31. All the timeslots

except timeslot 0 are available for service data transmission. A T1 frame has timeslots numbered

from 1 to 24. All the timeslots are available for service data transmission. The timeslots to which

the ATM cell is not mapped can transmit other data.

WCDMA RAN




17


23/184

Figure 3-15Fractional 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 fractionalIMA mode, an IMA group

contains 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 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-4Parameters correspond to fractional mode

NE Scrambling Switch

Line CodingMethod

E1/T1 Timeslot

RNC SCRAMBLESW

(BSC6900,BSC6910

)

PTCODE TSBITMAP

(BSC6900,BSC6910

)

NodeB SCRAM LNCODE TSN

NOTE

Only AEUa support the parameter PTCODE.

Function of Fractional ATM

After the fractional ATM function is enabled, the ATM cells of a 3G network can be transmitted

over an existing 2G network, as shown in Figure 3-16.

WCDMA RAN




18


24/184

Figure 3-16Fractional 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 group

with each fractional IMA link occupying the same number of idle timeslots.

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

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

Table 3-5Fractional mode of BSC6900/BSC6910

Modes of the FractionalATM Function

BSC6900 BSC6910

Fractional ATM The fractional ATM/IMA

mode are applicable only to

the AEUa/AOUc board.

The fractional ATM mode

are applicable only to the

AOUc board.

Fractional IMA Not support

WCDMA RAN




19


25/184

3.5.3 IMA Mode

Overview

IMA mode (WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub

Interface) 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 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 IMA link must be identical.

Principles of IMA Mode

Figure 3-17shows 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 layer

and distributes the cells among the E1/T1 links.

l At the reception end, the IMA group reassembles the cells to restore the original ATM cell

stream, and then transfers the cell stream to the ATM layer.

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

of the ATM layer.

Figure 3-17Principles of the IMA mode

In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frame

to implement necessary controlling functions.

The length of an IMA frame, m, is defined during the setup of an IMA group. The parameter

FRMLEN(BSC6900,BSC6910)(at the RNC)/FRMLEN(at the NodeB) is used to specify the

length of an IMA frame.

Figure 3-18shows 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.

WCDMA RAN




20


26/184

Figure 3-18IMA 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:



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 of

E1/T1 must be identical.

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

Table 3-6Parameters correspond to IMA mode

NE Scrambling Switch Line Coding Method

16-TimeslotSwitch

RNC SCRAMBLESW

(BSC6900,BSC6910)

PTCODE TS16ENABLE

NodeB SCRAM LNCODE TS16

NOTE

Only AEUa support the parameter PTCODEand TS16ENABLE.

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.

WCDMA RAN




21


27/184

3.6.1 Principles of Timeslot Cross Connection

Figure 3-19shows an example of timeslot cross connection. The timeslot cross connection

device cross-connects the timeslots on one E1/T1 to the timeslots on the other E1/T1. In the

example 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-19Example of timeslot cross connection

3.6.2 Function of Timeslot Cross Connection

The AEUa/PEUa/POUc board of BSC6900 supports timeslot cross connection. The BSC6910

does 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 2G

equipment or NodeB monitoring equipment.

Figure 3-20shows implementation of timeslot cross connection.

Figure 3-20Implementation of timeslot cross connection

WCDMA RAN




22


28/184

NOTE

Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by other

applications, 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 PVC

parameters need to be set.

3.7.1 VPI and VCI

The main characteristics of the ATM technology are multiplexing, switching, and transmitting

of ATM cells. All these operations are performed over Virtual Channels (VCs). A VC and a

Virtual Path (VP) are identified by Virtual Channel Identifier (VCI) and Virtual Path Identifier(VPI) respectively.

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

l A VC is identified by a VCI. It is a logical connection between ATM nodes and is the

channel for transmitting ATM cells between two or more nodes. The VC is used for the

data transmission between mobile terminals, between networks, or between mobile

terminal and network.

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

VPI.

Figure 3-21Relationship 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

WCDMA RAN




23


29/184

Variable Bit Rate (RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), Unspecified Bit

Rate (UBR), and UBR_PLUS (UBR+).

Table 3-7describes the types of service.

Table 3-7Types 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-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, for example, e-mail, is relatively insensitive to delivery time ordelay.

UBR Rate of a service with no commitment to transmission and no feedback

on congestion. This type of service is ideal for the transmission of IP

datagrams. In congestion, UBR cells are discarded, and no feedback or

request for slowing down the 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 transmission resource congestion, and the best effort serviceof UBR+ uses the transmission bandwidth completely.

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

Table 3-8Characteristics of different ATM services

Characteris

tic

CBR RT-VBR NRT-VBR UBR UBR+

Bandwidth

guarantee

Yes Yes Yes No Yes

Applicabilit

y to real-time

communicati

on

Yes Yes No No No

Applicabilit

y to bursts of

communicati

on

No Yes Yes No No

WCDMA RAN




24


30/184

Characteristic

CBR RT-VBR NRT-VBR UBR UBR+

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 QoS classes can be configured for AAL2 path, and the UBR+ ATM QoS class is generally

used for Iub OAM connection.

The service types carried on the AAL2 paths can be determined by running the ADD

ATMTRFcommand, and then the mapping between the service types and the transmission

resources for the adjacent node can be configured by running the ADD TRMMAPcommand.

3.7.3 ATM Traffic Records

The ATM traffic records are public resources, which can be used by the IPoA PVCs, AAL2

paths, SAAL links, and VPCLCX links. You need to add the traffic record at the RNC based on

the traffic model of the link on the Iub/Iu-CS/Iu-PS/Iur interface. The ATM traffic records can

be configured by the ADD ATMTRFcommand.

Traffic Parameters

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

Table 3-9describes the ATM traffic parameters.

Table 3-9ATM 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-VBR

indicate real-time services, which are usually carried on the user

planes of the Iur, Iub, and Iu-CS interfaces. NRT-VBR and UBR

indicate non-real-time services, which are usually carried on the

user 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 value

of 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 long

time.

WCDMA RAN




25


31/184

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 be

greater 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 delay

and 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 device

connected to the NodeB be set to twice the CDVTof the NodeB, thereby

preventing packets from the NodeB being lost. The CDVTof the NodeB is

set 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 CBRand

the traffic rate is a constant value.

l Combination of PCR(BSC6900,BSC6910)and SCR(BSC6900,BSC6910): applicable

when ST(BSC6900,BSC6910)is set to RTVBRor NRTVBR.

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

UBR_PLUS.

ATM Traffic Record Configuration Principles

Table 3-10provides suggestions for configuring service types during configuration of ATM

traffic records for links.

Table 3-10Recommended service types for links

Link Preferred Service Type (In Descending Order)

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

WCDMA RAN




26


32/184

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 boards

of the RNC.

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

connections for Iub/Iu-CS/Iur are set up by configuring the SAAL links.

You can run the ADD SAALLNKcommand 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. The

TXTRFX(BSC6900,BSC6910) and RXTRFX(BSC6900,BSC6910)parameters record the

ATM traffic, and they can be configured through the ADD ATMTRFcommand.

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 the

parameters VPIand VCIare used to identify the PVCs on the NodeB side. The PVC identifier

and 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, and

ALCAP, and the signaling messages carried on the NNI-SAAL links are MTP3, as described in

Table 3-11.

Table 3-11Data 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 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 of Network-to-Network Interface (NNI) type.

3.9 AAL2 Path

WCDMA RAN




27


33/184

3.9.1 AAL2 Connections and AAL2 Path

The Q.AAL2 module is responsible for dynamically setting up and releasing AAL2 connections

between the RNC and the peer end. The peer end can be a NodeB, a CS CN node, or a neighboring

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

same. An AAL2 path contains multiple AAl2 connections. CID specifies the ID of an AAL2

connection on the path. The CID state can be Busy or Idle. If the CID is in the busy 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

AAL2 Connections on Iub/IuCS/Iur Interface).

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

interface.

Figure 3-22Relationship 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 CBR

l RT-VBR

l NRT-VBR

l UBR

According to different types of service (R99, HSDPA, and HDUPA), the following types of

AAL2 path can be configured:

l R99

l HSPA

l 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)andRXTRFX(BSC6900,BSC6910)parameters record the ATM traffic,

and they can be configured through the ADD ATMTRFcommand. For details, see section 3.7.3

ATM 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 attributes

must be negotiated between the RNC and the peer end.

WCDMA RAN




28


34/184

3.9.2 AAL2 Route

An AAL2 path may reach not the destination node but an adjacent node. In this case, AAL2

routes can be configured to reach the destination node. The AAL2 route to an ATM node can

be configured through the ADD AAL2RT command.

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

Figure 3-23Example 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 cannot be configured for the adjacent node of the IUPS type.

3.10 MTP3

3.10.1 MTP3 Links

MTP3 links are contained in an MTP3 link set. MTP3 links are carried on the SAAL links of

Network-to-Network Interface (NNI) type. You can run the command ADD MTP3LKSto

specify an MTP3 link set, and then run the command ADD MTP3LNKto add the MTP3 links

by using the parameterSIGLKSX(BSC6900,BSC6910).

MTP3 Links for Iu-CS Interface

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

networking 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 for

the MSC server (IUCS_RANAP signaling point). It is recommended that more than one

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

WCDMA RAN




29


35/184

Figure 3-24Example 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 MTP3

link be configured.

MTP3 Links for Iur Interface

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

neighboring RNC:

l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at least

one 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 CPUS

subsystems in the MPS/EPS so that the signaling exchange can be reduced between the CPUS

subsystems.

3.10.2 Types of MTP3 DSPs

The 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-12describes the types of DSP.

Table 3-12Types of DSP

DSP Type Description

IUCS R99 MSC DSP. The IUCS DSP has the control plane functions of both

radio network 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 the transport network layer on the Iu-CS interface.

WCDMA RAN




30


36/184

DSP Type Description

IUCS_RANAP R4 MSC server DSP. The IUCS_RANAP DSP has the control plane

functions 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 Mask

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

of routes (2n). 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 (2n). 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 be 0, as shown in Figure 3-25.

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

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 used to transmit the OM information of a NodeB. In this case, the IPoA PVC

is called the management plane IPoA 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 IPOAPVCcommand. If the parameter

PEERT(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) are

used 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

WCDMA RAN




31


37/184

RXTRFX(BSC6900,BSC6910)parameters record the ATM traffic, and they can be configured

through the ADD ATMTRFcommand.

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 loopback

l Performance management

Forward monitoring

Backward reporting

l Activation and deactivation

The CC can be activated to monitor the end-to-end AAL2 path virtual connect link (VCL) and

Iu-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 alternative

VCLs to prevent the failure of the call. You can run the ACT VCLCCcommand to activate the

CC function and the DEA VCLCCcommand to deactivate the CC function. When the parameter

VCLTYPEis set to CC, the CC function is activated.

Huawei also supports proprietary delay detection function. When an NE receives a detection

start 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 loopback

message is used to store the message transmission time. When an NE receives the loopback

message, it calculates the delay based on the time difference between transmission and reception.

WCDMA RAN




32


38/184

4ATM Transmission ResourcesATM 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:

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 over

channelized STM-1/OC-3 on Iub interface)

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

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

For details about the ATM transmission resources, see "Transmission Resources" in the

Transmission Resource Management Feature Parameter Description.

WCDMA RAN

ATM Transport Feature Parameter Description 4 ATM Transmission Resources



33


39/184

5ATM Transmission Resource ManagementFor ATM transport, Huawei provides the following transmission resource management:

l Admission control (WRFD-05030106 Call Admission Based on Used AAL2 Path

Bandwidth), 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 ATM

QoS classes are used to implement differentiated services.

l Iub overbooking (WRFD-050405 Overbooking on ATM Transmission, WRFD-050406

ATM 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, see

the Transmission Resource Management Feature Parameter Description.

WCDMA RAN

ATM Transport Feature Parameter Description 5 ATM Transmission Resource Management



34


40/184

6Engineering 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-05030104

Dynamic AAL2 Connections in Iub/IuCS/Iur Interface.

6.1.1 Requirements

l Dependencies on Hardware

BTS3902E and BTS3803E does not support this feature.

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

Activation

l On the RNC side

1. Run the RNC MML command ADD ADJNODE(CME single configuration: NodeB

Configuration Express > IUB_RNC > ATM Transport > Adjacent Node, IUR

Configuration Express > ATM Transport > Adjacent Node, IUCS Configuration

Express > ATM Transport > Adjacent Node; CME batch modification center: not

supported) to add an adjacent node. Set the parameter Adjacent Node Typeto IUB,

IUR, or IUCS, and the parameter Transport Typeto ATM. If the node is the lowest

leaf node of the switching network, set the parameter Is Root Nodeto YES; otherwise,

set the parameter Is Root Nodeto NO.

WCDMA RAN

ATM Transport Feature Parameter Description 6 Engineering Guidelines



35


41/184

NOTE

For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Typeof its upper-

level hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface, the

parameter Adjacent Node Typeof its upper-level hub node must be UNI_AAL2SWITCH.

2. Run the RNC MML command ADD AAL2PATH(CME single configuration: NodeB

Configuration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCS

Configuration Express > ATM Transport > AAL2 Path, IUR Configuration Express

> ATM Transport > AAL2 Path; CME batch modification center: not supported) to

add an AAL2 path. The parameters CARRYVPIand CARRYVCImust be consistent

with 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 Series

Base Station Product Documentation and navigate in the following sequence: 3900 Series

Base Station Initial Configuration (CME-based) > Creating Base Stations > Creating

NodeBs > Creating a Single NodeB > Configuring NodeB Transport Data > ConfiguringATM Transport Data on the NodeB Side.

Verification

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

Expected result: The value of Operation stateis Available.

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

Expected result: The value of AAL2 Path Statusis 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 is

normal, 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 the

handover 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 Configuration

Express > ATM Transport > AAL2 Path, IUR Configuration Express > ATM Transport > AAL2

Path; 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 Configuration

Express > ATM Transport > Adjacent Node, IUCS Configuration Express > ATM Transport >

Adjacent Node; CME batch modification center: not supported) to delete an ATM adjacent node.

WCDMA RAN




36


42/184

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 node

ADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, TRANST=ATM, IsROOTNODE=YES, DPX=1;

//Adding an AAL2 path

ADD 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 Interface

DSP 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 node

RMV ADJNODE: ANI=2;

//On the NodeB side

RMV AAL2PATH: NT=LOCAL, PATHID=1;

6.2 WRFD-05030105 Permanent AAL5 Connections for

Control Plane Traffic


Permanent AAL5 Connections for Control Plane Traffic.

6.2.1 Requirements




This feature does not depend on other features.

l License



The equipment data has been configured for the ATM transmission on the Iub/Iu/Iur

interface. For details, see section Configuring the Equipment Dataof theBSC6900 UMTS

Initial Configuration Guide orBSC6910 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, IUCS

Configuration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express

WCDMA RAN




37


43/184

> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) to

add an SAAL link. If the interface is Iub, set the parameter Interface typeto UNI. If the interface

is Iu or Iur, set Interface typeto NNI.

Step 2 Optional: Run the RNC MML command ADD UNCP(CME single configuration: NodeB

Configuration 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 modification

center: 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 step

3 based on the actual situation.

Verification Procedure

Run the RNC MML command DSP SAALLNKto query the status of the SAAL link.

Expected result: The value of SAAL link stateis AVAILABLE.

Deactivation Procedure

NOTE:

An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP or

CCP 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 modification

center: 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 modification

center: 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, IUCS

Configuration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express

> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) to

remove 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 TrafficRMV UCCP: NODEBNAME="NodeB1", PN=0; RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;

WCDMA RAN




38


44/184

6.3 WRFD-05030106 Call Admission Based on Used AAL2

Path BandwidthThis section describes how to activate, verify, and deactivate the basic feature WRFD-05030106

Call Admission Based on Used AAL2 Path Bandwidth.

6.3.1 Requirements





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 batch

modification center: not supported) to set parameters to appropriate values. For example, set

Service typeto NRTVBR, Peak cell rateto 100, and Sustainable cell rateto 80.

Step 2 Run the RNC MML command ADD AAL2PATH(CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path; CME batch modification

center: not supported) to add an ATM Adaptation Layer type 2 (AAL2) path. In this step, set

TXTRFXand RXTRFXin 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 is

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

WCDMA RAN




39


45/184

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

6.4.1 Requirements





l License


6.4.2 Procedure


Run the RNC MML command ADD ATMTRF(CME single configuration: NodeB

Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch

modification center: not supported) to add an ATM traffic record. To add more ATM traffic

records, run this command repeatedly.


Ensure that an AAL2 path using the ATM traffic record added in the activation procedure and

TRMMAP 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 TXTRFXof the AAL2 path corresponding to the path ID in the QAAL2 Establish requestmessage.

The expected result is that the value of TXTRFXis consistent with that in the ADD

ATMTRFcommand.

----End

WCDMA RAN




40


46/184


Step 1 Run the RNC MML command RMV AAL2PATH(CME single configuration: NodeBConfiguration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCS Configuration

Express > ATM Transport > AAL2 Path, IUR Configuration Express > ATM Transport > AAL2Path; CME batch modification center: not supported) to delete an AAL2 path using an ATM

traffic 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 batch

modification center: not supported) to delete an ATM traffic record. To delete more ATM traffic


----End


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

RMV AAL2PATH: ANI=2, PATHID=1;

RMV ATMTRF: TRFX=105;

6.5 WRFD-05030110 F5


F5. (This feature cannot be configured using the CME.)

6.5.1 Requirements


Dependencies on the RNC side

None.

Dependencies on the NodeB side

Only 3900 series Base Station supports the passive detection based on IE LB.




l License



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

the Basic Data.

The SAALLNK, AAL2PATH, or IPOAPVC link exists.

WCDMA RAN




41


47/184

6.5.2 Procedure


Step 1 Run the RNC MML command ACT VCLCCto activate the VCL CC or loopback function fora link. To activate the function for multiple links, run this command repeatedly. There are three

types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.

Step 2 Run the RNC MML command ACT VCLPMto activate the VCL PM function for a link. Toactivate the function for multiple links, run this command repeatedly. There are three types of

links, that is, SAALLNK, AAL2PATH, and IPOAPVC.

----End


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

l If the VCL CC is activated and the PVC is functional, the SINK activated stateand

SOURCE activated stateare UP, and LOC, AIS, and RDIalarm state is normal.

l If the loopback is activated and the PVC is functional, the loopbackquery result is UP, and

LOC, AIS, and RDIalarm state is normal.

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

l If the VCL PM is activated, the SINK activated stateand SOURCE activated stateare

PM_UP, and PM Active Fail Alarmis Normal.

----End


Step 1 Run the RNC MML command DEA VCLCCto deactivate the VCL CC or loopback functionfor a link. To deactivate the function for multiple links, run this command repeatedly. There are

three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.

Step 2 Run the RNC MML command DEA VCLPMto deactivate the VCL PM for a link. To deactivatethe function for multiple links, run this command repeatedly. There are three types of links, that

is, SAALLNK, AAL2PATH, and IPOAPVC.

----End


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

WCDMA RAN




42


48/184

6.6 WRFD-050305 UBR+ ATM QoS Class

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

6.6.1 Requirements





l License



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

Basic Data.

6.6.2 Procedure


Run the MML command ADD ATMTRF(CME single configuration: NodeB Configuration

Express > 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 traffic



Run the MML command LST ATMTRFto 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 Configuration

Express > 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 traffic



//Adding UBR+ ATM QoS Class

ADD ATMTRF: TRFX=105, ST=UBR_PLUS, UT=CELL/S, MCR=100;

//Verifying UBR+ ATM QoS Class

LST ATMTRF: TRFX=105;

//Deactivating UBR+ ATM QoS Class

RMV ATMTRF: TRFX=105;

WCDMA RAN




43


49/184

7ParametersTable 7-1Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

IPADDR BSC6900 ADD IPOAPVC

MOD