IP RAN 3G Design

Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

WCDMA RAN

IP RAN Feature Parameter Description

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 the property 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 commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by 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.

WCDMA RAN

IP RAN Contents

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


ii

Contents

1 Introduction ................................................................................................................................ 1-1

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

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

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

2 Overview of IP RAN .................................................................................................................. 2-1

3 Protocol Stacks ......................................................................................................................... 3-1

3.1 Overview ....................................................................................................................................... 3-1

3.2 Iub over IP ..................................................................................................................................... 3-1

3.2.1 Protocol Stack ....................................................................................................................... 3-1

3.2.2 Transport Mode Configuration .............................................................................................. 3-2

3.2.3 SCTP Link Configuration ...................................................................................................... 3-2

3.2.4 IP Path Configuration ........................................................................................................... 3-4

3.2.5 OM Channel Configuration ................................................................................................... 3-5

3.2.6 Other Data Configuration ...................................................................................................... 3-7

3.3 Iub over IP&ATM ........................................................................................................................... 3-7

3.3.1 Protocol Stack ....................................................................................................................... 3-7

3.3.2 Trasnport Mode Configuration ............................................................................................ 3-10

3.3.3 Control Plane Link Configuration ........................................................................................ 3-10

3.3.4 User Plane Path Configuration ........................................................................................... 3-11

3.3.5 OM Channel Configuration ................................................................................................. 3-12

3.3.6 Other Data Configuration .................................................................................................... 3-12

3.4 Iu-CS over IP ............................................................................................................................... 3-12

3.4.1 Protocol Stack ..................................................................................................................... 3-12

3.4.2 Transport Mode Configuration ............................................................................................ 3-13

3.4.3 SCTP Link Configuration .................................................................................................... 3-13

3.4.4 IP Path Configuration ......................................................................................................... 3-14


3.5 Iu-PS over IP ............................................................................................................................... 3-14

3.5.1 Protocol Stack ..................................................................................................................... 3-14





3.6 Iur over IP .................................................................................................................................... 3-15

3.6.1 Protocol Stack ..................................................................................................................... 3-15





WCDMA RAN

IP RAN Contents



iii

4 IP RAN Networking ................................................................................................................... 4-1

4.1 Overview ....................................................................................................................................... 4-1

4.2 Iub Interface Networking ............................................................................................................... 4-1

4.2.1 Iub over IP Networking ......................................................................................................... 4-1

4.2.2 Iub over IP&ATM Networking ............................................................................................... 4-4

4.3 Iu/Iur Interface Networking ............................................................................................................ 4-5

5 Parameters ................................................................................................................................. 5-1

6 Counters ...................................................................................................................................... 6-1

7 Glossary ...................................................................................................................................... 7-1

8 Reference Documents ............................................................................................................. 8-1

WCDMA RAN

IP RAN 1 Introduction



1-1

1 Introduction

1.1 Scope

This document describes the IP Radio Access Network (RAN) feature. It covers the protocol stacks and the networking over the terrestrial interfaces of RAN.

Before reading this document, you are advised to read the following documents:

IP Transport Architecture Description: to learn about the IP transport architecture overview, IP protocols, IP transmission efficiency improvement, IP reliability improvement, IP fault detection, and so on.

BSC6900 UMTS Initial Configuration Guide and NodeB Initial Configuration Guide: to learn about the data configuration procedures of the Iub, Iur, Iu interfaces

Other relevant documents are as follows:

BSC6900 UMTS Hardware Description: to learn about the functions, specifications, and panels of the RNC interface boards

NodeB Hardware Description: to learn about the functions, specifications, and panels of the NodeB interface boards

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics

Personnel who need to understand IP RAN

Personnel who work with Huawei products

Personnel who configure the WCDMA RAN transport network

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 IP RAN feature.

Editorial change: refers to the change in wording or the addition of the information that was not described 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.

WCDMA RAN

IP RAN 1 Introduction



1-2

Compared with issue 01 (2010-03-30) of RAN12.0, this issue optimizes the description.

WCDMA RAN

IP RAN 2 Overview of IP RAN



2-1

2 Overview of IP RAN

IP RAN is a feature based on which the Radio Access Network (RAN) can use the IP transport network as the data bearers over the Iub, Iur, and Iu interfaces.

IP RAN brings the following advantages:

IP transport features high bandwidth and low cost, thus easily meeting the requirements of data services for high bandwidth and enabling operators to introduce new services as required.

IP transport enables operators to utilize the existing IP-based networks flexibly, thus reducing the costs of network deployment and maintenance.

IP transport keeps pace with the evolution towards all-IP, thus reducing the network evolution cost.

With the application of the multi-mode base station controller, IP-based common transport can be implemented on the GSM and UMTS interfaces.

IP transmission over Iub interface corresponds to feature WRFD-050402 IP Transmission Introduction on Iub Interface. IP transmission over Iur interface corresponds to feature WRFD-050410 IP Transmission Introduction on Iur Interface. IP transmission over Iu interface corresponds to feature WRFD-050409 IP Transmission Introduction on Iu Interface. In RAN13.0, Iub, Iur, and Iu interfaces support the built-in firewall at the BSC6900, and Iub interface supports the built-in firewall at the NodeB. For details, see Security Feature Parameter Description.

Security.htm

WCDMA RAN

IP RAN 3 Protocol Stacks



3-1

3 Protocol Stacks

3.1 Overview

RAN uses IP transport to carry upper-layer data over the following terrestrial interfaces:

Iub interface

Iu-CS interface

Iu-PS interface

Iur interface

Here, the Iub interface supports two transport modes: Iub over IP and Iub over IP&ATM.

This section describes the protocol stacks of the preceding interfaces and the relevant parameter settings.

3.2 Iub over IP

The Iub interface connects the RNC and the NodeB. When the Iub over IP protocol stack is used, the data in the control and user planes of the Iub interface is transported over IP.

3.2.1 Protocol Stack

Figure 3-1 shows the Iub over IP protocol stack.

Figure 3-1 Iub over IP protocol stack

Control plane

WCDMA RAN




3-2

The application protocol for the control plane of the Iub interface is the NodeB Application Part (NBAP). NBAP is responsible for the transport of control plane messages between the NodeB and the controlling RNC (CRNC) at the radio network layer.

When Iub over IP is used, NBAP is carried on the Stream Control Transmission Protocol (SCTP) link.

User plane

The application protocols for the user plane of the Iub interface are a series of frame protocols: DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, and E-DCH FP. These protocols are responsible for the transport of data and control frames between the NodeB and the CRNC. These frames contain Uu interface user data and user-related control data.

When Iub over IP is used, the user plane data on the Iub interface is carried on the IP path.

The data link layer of Iub over IP supports the following transport modes: IP over E1/T1, IP over channelized STM-1/OC-3, IP over unchannelized STM-1/OC-3c, and IP over FE/GE.

3.2.2 Transport Mode Configuration

To enable Iub over IP, set the following parameters on the RNC side:

The TnlBearerType parameter is set to IP_TRANS or HYBRID_IP_TRANS. If the TnlBearerType parameter is set to HYBRID_IP_TRANS or IP_TRANS, the IPTRANSAPARTIND parameter must be set to SUPPORT or NOT_SUPPORT to specify whether to support hybrid IP transport.

The NODET parameter is set to IUB.

The TRANST parameter is set to IP or HYBRID_IP.

You also need to set the Bearing Mode (MODE) parameter to IPV4 on the NodeB side if E1/T1 is used for transport at the physical layer.

3.2.3 SCTP Link Configuration

The Iub control plane has two types of control ports: NodeB control port (NCP) and communication control port (CCP).

The NCP and CCP carry different types of Iub interface signaling messages, as listed in Table 3-1.

Table 3-1 Description of the NCP and CCP

Port Description Quantity

NCP Carries common process messages of NBAP over the Iub interface

One Iub interface has only one NCP.

CCP Carries dedicated process messages of NBAP over the Iub interface

One Iub interface may have multiple CCPs. The number of CCPs depends on the network planning.

When Iub over IP is used, the NCP and CCP are carried on different SCTP links. An SCTP link is jointly specified by the local SCTP port No., local IP address, peer SCTP port No., and peer IP address.

SCTP Link Configuration on the RNC Side

The parameters for establishing an SCTP link on the RNC side are as follows:

MODE: When Iub over IP is used, the MODE parameter on the RNC side must be set to SERVER.

../RNCParaHtml/mbsc/m-para/unodeb_tnlbearertype.html


../RNCParaHtml/mbsc/m-para/unodeb_iptransapartind.html

../RNCParaHtml/mbsc/m-para/adjnode_nodet.html

../RNCParaHtml/mbsc/m-para/adjnode_transt.html

../NodeBParaHtml/mml-mo-para/para/E1T1BEAR-Mode.html

../RNCParaHtml/mbsc/m-para/sctplnk_mode.html


WCDMA RAN




3-3

LOCIP1: When SCTP multi-homing is not used, this parameter specifies the IP address of the SCTP link on the RNC side. When SCTP multi-homing is used, this parameter and PEERIP1 determine the main path of the SCTP link.

LOCIP2: This parameter specifies the second IP address of the SCTP link on the RNC side. This parameter is set only when SCTP multi-homing is used.

APP: This parameter specifies the upper layer application type of the SCTP link. The upper layer application type of the Iub interface is NBAP.

NBAPSRVPN: This parameter specifies the local port number when the RNC functions as the server. The RNC uses the NBAP service listening port to listen to the requests from the NodeB for establishing the SCTP link. Note that the PEERPORT parameter for the SCTP link on the NodeB side should be set to the same value as the NBAPSRVPN parameter on the RNC side.

PEERIP1: When SCTP multi-homing is not used, this parameter specifies the peer (that is, NodeB) IP address of the SCTP link. When SCTP multi-homing is used, this parameter and LOCIP1 determine the main path of the SCTP link.

PEERIP2: This parameter specifies the second peer IP address of the SCTP link. This parameter is set only when SCTP multi-homing is used.

PEERPN: This parameter specifies the peer port number of the SCTP link.

DSCP: This parameter specifies the priority of a signaling message. The default value is 48. It is recommended that the default value be used.

CROSSIPFLAG: This parameter specifies whether the cross paths of the SCTP link is available. This parameter is set only when SCTP multi-homing is used.

If one of the LOCIP2 and PEERIP2 parameters is set, the other must also be set.

In the case of SCTP multi-homing, the two IP addresses of one SCTP link on the RNC side may belong to the same interface board or different interface boards, whereas the two IP addresses on the NodeB side must belong to the same interface board.

The parameters for establishing an NCP or CCP are as follows:

CARRYLNKT(NCP)/CARRYLNKT(CCP): This parameter specifies whether the bearer link type of the NCP or CCP is SAAL, SCTP, or SAAL-SCTP. When Iub over IP is used, this parameter must be set to SCTP, which indicates that the NCP or CCP is carried on the SCTP link.

SCTPLNKN(NCP)/SCTPLNKN(CCP): This parameter specifies the number of the SCTP link that carries the NCP or CCP.

SCTP Link Configuration on the NodeB Side

The parameters for establishing an SCTP link on the NodeB side are as follows:

LOCIP: When SCTP multi-homing is not used, this parameter specifies the IP address of the SCTP link on the NodeB side. When SCTP multi-homing is used, this parameter and PEERIP determine the main path of the SCTP link. This parameter should be set to the same value as the PEERIP1 parameter on the RNC side.

SECLOCIP: This parameter specifies the second IP address of the SCTP link on the NodeB side. This parameter is set only when SCTP multi-homing is used. This parameter should be set to the same value as the PEERIP2 parameter on the RNC side.

PEERIP: When SCTP multi-homing is not used, this parameter specifies the peer (that is, RNC) IP address of the SCTP link. When SCTP multi-homing is used, this parameter and LOCIP determine the main path of the SCTP link. This parameter should be set to the same value as the LOCIP1 parameter on the RNC side.

../RNCParaHtml/mbsc/m-para/sctplnk_locip1.html

../RNCParaHtml/mbsc/m-para/sctplnk_peerip1.html


../RNCParaHtml/mbsc/m-para/sctplnk_app.html

../RNCParaHtml/mbsc/m-para/sctpsrvport_nbapsrvpn.html

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-PeerPort.html





../RNCParaHtml/mbsc/m-para/sctplnk_peerpn.html

../RNCParaHtml/mbsc/m-para/sctplnk_dscp.html

../RNCParaHtml/mbsc/m-para/sctplnk_crossipflag.html



../RNCParaHtml/mbsc/m-para/uncp_carrylnkt.html

../RNCParaHtml/mbsc/m-para/uccp_carrylnkt.html

../RNCParaHtml/mbsc/m-para/uncp_sctplnkn.html

../RNCParaHtml/mbsc/m-para/uccp_sctplnkn.html

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-LocIP.html

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-PeerIP.html


../NodeBParaHtml/mml-mo-para/para/SCTPLNK-SecLocIP.html





WCDMA RAN




3-4

SECPEERIP: This parameter specifies the second peer (that is, RNC) IP address of the SCTP link. This parameter is set only when SCTP multi-homing is used. This parameter should be set to the same value as the LOCIP2 parameter on the RNC side.

LOCPORT: This parameter specifies the local port number of the SCTP link. This parameter should be set to the same value as the PEERPN parameter on the RNC side.

PEERPORT: This parameter specifies the peer port number of the SCTP link. This parameter should be set to the same value as the NBAPSRVPN parameter on the RNC side.

When the NCP and CCP are added, the BEAR parameter should be set to IPV4, which indicates that the NCP and CCP are carried on the SCTP links.

3.2.4 IP Path Configuration

Overview

When Iub over IP is used, the user plane data on the Iub interface is carried on the IP path. At least one IP path is required between one RNC and one NodeB. It is recommended that more than one IP path be configured. IP paths are configured in normal conditions according to the following policies:

Only one QoS path is configured on the RNC side, and more than one path is configured on the NodeB side according to priorities.

More than one path is configured on both the RNC and NodeB sides according to priorities.

Different priorities are assigned to IP paths for the provisioning of differentiated services. For details, see the Transmission Resource Management Feature Parameter Description.

For example, four IP paths are configured between the RNC and the NodeB to share the physical transmission bandwidth on the Iub interface, as shown in Figure 3-2.

These IP paths are specified to carry the R99 RT, R99 NRT, HSPA RT, and HSPA NRT services respectively by setting the following:

PATHT parameter

Mapping between services and Per-Hop Behaviors (PHBs)

Mapping between PHBs and DSCPs

The mapping between services and PHBs is contained in the transmission resource management (TRM) mapping table, which is set through the ADD TRMMAP command. The mapping between PHBs and DSCPs is set through the SET PHBMAP command.

Figure 3-2 IP paths on the Iub interface

In this case, the interface boards of the RNC and NodeB provide differentiated scheduling according to the value of differentiated service code point (DSCP). In the case of transmission congestion, the high-

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-SecPeerIP.html


../NodeBParaHtml/mml-mo-para/para/SCTPLNK-LocPort.html




../NodeBParaHtml/mml-mo-para/para/IUBCP-CarryType.html

Transmission%20Resource%20Management.htm

../RNCParaHtml/mbsc/m-para/ippath_patht.html

WCDMA RAN




3-5

priority RT service data is preferentially transmitted and the low-priority NRT service data is buffered. In the case of buffer overflow, the low-priority NRT service data is discarded. The intermediate transport network also provides differentiated services according to the DSCP value in the IP header.

IP Path Configuration on the RNC Side

The parameters for establishing an IP path on the RNC side are as follows:

ITFT: This parameter specifies the type of the adjacent node.

TRANST: This parameter specifies the transport type of the adjacent node to which the path belongs.

IPADDR: This parameter specifies the local IP address of the IP path on the RNC side. This IP address is used for the user plane of the Iub interface. This IP address can be the port IP address or device IP address. For descriptions of the port IP address and device IP address, see the IP Transport Architecture Description. The control and user planes of the RNC-related interfaces (Iub, Iur, Iu-CS, and Iu-PS) can share one IP address.

PEERIPADDR: This parameter specifies the peer IP address of the IP path. For the Iub interface, this parameter must be set to the same value as the LOCALIP parameter on the NodeB side.

PEERMASK: This parameter specifies the peer subnet mask. The default value of this parameter is 255.255.255.255, which indicates that the peer IP address of the IP path is a host IP address. If the peer IP address of the IP path is a network segment IP address, this parameter needs to be re-set.

PATHT: This parameter specifies the type of an IP path. Different types of IP paths can be configured between the RNC and the NodeB. Different types of services are mapped to different types of IP paths. For details, see the Transmission Resource Management Feature Parameter Description.

TXBW: This parameter specifies the bandwidth for admission control on an IP path in the transmission direction.

RXBW: This parameter specifies the bandwidth for admission control on an IP path in the reception direction.

IP Path Configuration on the NodeB Side

The parameters for establishing an IP path on the NodeB side are as follows:

PT: This parameter specifies the type of the port that carries the IP path. It can be PPP link, MLPPP group, or Ethernet port.

LOCALIP: This parameter specifies the IP address of the IP path on the NodeB side. This IP address is used for the user plane of the Iub interface. This IP address can be the port IP address or device IP address. Generally, the port IP address is used.

PEERIP: This parameter specifies the peer (that is, RNC) IP address of the IP path. This parameter should be set to the same value as the IPADDR parameter on the RNC side.

DSCP: This parameter specifies the DSCP value of the IP path on the NodeB side.

RXBW: This parameter specifies the RX bandwidth. This parameter is important to the algorithm for flow control. The value of RXBW must be equal to the DL bandwidth at RNC. Otherwise, it will affect the result of the algorithm for flow control.

TXBW: This parameter specifies the TX bandwidth.

TXCBS: This parameter specifies the TX committed burst size.

TXEBS: This parameter specifies the TX excess burst size.

3.2.5 OM Channel Configuration

An operation and maintenance (OM) channel exists between the M2000 and the NodeB. It is used to maintain and configure the NodeB remotely.

../RNCParaHtml/mbsc/m-para/ippath_itft.html

../RNCParaHtml/mbsc/m-para/ippath_transt.html

../RNCParaHtml/mbsc/m-para/ippath_ipaddr.html

../RNCParaHtml/mbsc/m-para/ippath_peeripaddr.html

../NodeBParaHtml/mml-mo-para/para/IPPATH-LocalIP.html

../RNCParaHtml/mbsc/m-para/ippath_peermask.html



../RNCParaHtml/mbsc/m-para/ippath_txbw.html

../RNCParaHtml/mbsc/m-para/ippath_rxbw.html

../NodeBParaHtml/mml-mo-para/para/IPPATH-PortType.html


../NodeBParaHtml/mml-mo-para/para/IPPATH-PeerIP.html


../NodeBParaHtml/mml-mo-para/para/IPPATH-DSCP.html

../NodeBParaHtml/mml-mo-para/para/IPPATH-RxBandwidth.html


../NodeBParaHtml/mml-mo-para/para/IPPATH-TxBandwidth.html

../NodeBParaHtml/mml-mo-para/para/IPPATH-TxCBS.html

../NodeBParaHtml/mml-mo-para/para/IPPATH-TxEBS.html

WCDMA RAN




3-6

There are two methods of configuring routes for the OM channel on the Iub interface:

M2000<—>RNC<—>NodeB: Routes are configured between the M2000 and the NodeB through the RNC. In this case, routes need to be configured on the M2000, RNC, and NodeB.

M2000<—>NodeB: Routes are configured between the M2000 and the NodeB but not through the RNC. If the OM subnet where the M2000 is located is connected to the IP network that covers the NodeB, the M2000 and the NodeB can be directly networked without the RNC. In this case, routes need to be configured on only the M2000 and NodeB.

Figure 3-3 shows an example of OM channel in the case of M2000<—>RNC<—>NodeB in layer 2 networking. In layer 3 networking, two adjacent devices communicate with each other through routers. In addition, the OM IP addresses of the BTS3900, BTS3900A, and DBS3900 can be the same as either the control plane IP address or the user plane IP address. The shared IP address must be the interface IP address. This single IP function of the NodeB (WRFD-021404 Single IP Address for NodeB) is supported in the following scenarios:

The 3900 series base station is configured with one WMPT board and the WMPT has one or multiple IP interfaces. In this case, the OM IP address of the base station can be the same as the IP address of one of the interfaces. If active and standby OM IP addresses are used, the two OM IP addresses can

be the same as the IP addresses of the two IP interfaces respectively.

The 3900 series base station is configured with one WMPT board and one UTRP board. Both the boards have one or more IP interfaces. In this case, the OM IP address of the base station can be the same as the IP address of one IP interface on the WMPT board. If active and standby OM IP

addresses are applied, the two OM IP addresses can be the same as the IP addresses of the two IP

interfaces on the WMPT board respectively; however, the OM IP address cannot be the same as the IP

addresses of any IP interface on the UTRP board.

Note:

NodeB IP addresses involve the control plane IP address, user plane IP address, and NodeB maintenance

IP address. Generally, the control plane IP address and the user plane IP address are the same, that is, the

IP address of the interface. The maintenance IP address must be different from the IP address of the

interface.

Figure 3-3 OM channel in the case of M2000<—>RNC<—>NodeB

Figure 3-4 shows an example of OM channel in the case of M2000<—>NodeB.

Figure 3-4 OM channel in the case of M2000<—> NodeB

WCDMA RAN




3-7

When Iub over IP is used, the RNC adopts the Dynamic Host Configuration Protocol (DHCP) function to enable the restarted NodeB to automatically obtain the network address information and establish an OM channel. For details about the DHCP function, see the NodeB Self-discovery.

OM Channel Configuration on the RNC Side

The parameters for establishing an OM channel on the RNC side are as follows:

NBTRANTP: This parameter specifies the transmission type of the NodeB.

NBIPOAMIP: This parameter specifies the OM IP address of the NodeB in IP transport. The OM IP address can be the port IP address or device IP address. For the BTS3900, BTS3900A, and DBS3900, the control plane, user plane, and OM of the Iub interface can share one IP address.

NBIPOAMMASK: This parameter specifies the mask of the subnet where the OM IP address of the NodeB is located in IP transport.

IP routes need to be configured for the OM channel according to the actual networking conditions.

OM Channel Configuration on the NodeB Side

The parameters for establishing an OM channel on the NodeB side are as follows:

IP: This parameter specifies the local OM IP address.

MASK: This parameter specifies the local OM subnet mask.

PEERIP: This parameter specifies the peer IP address.

PEERMASK: This parameter specifies the peer subnet mask.

BEAR: This parameter specifies the bearer type (ATM or IPV4). If this parameter is set to ATM, the IPoA mode is used. If this parameter is set to IPV4, the IP mode is used.

IP routes need to be configured for the OM channel according to the actual networking conditions.

3.2.6 Other Data Configuration

To enable Iub over IP, the following data should also be configured: physical layer data, data link layer data, TRM mapping table, and activation factor table.

For details about these configurations, see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide.

3.3 Iub over IP&ATM

The Iub interface connects the RNC and the NodeB. When the Iub interface adopts hybrid ATM/IP transport, the Iub over IP&ATM protocol stack is used (WRFD-050404 ATM/IP Dual Stack Node B).


Figure 3-5 shows the Iub over IP&ATM protocol stack.

../RNCParaHtml/mbsc/m-para/unodebip_nbtrantp.html

../RNCParaHtml/mbsc/m-para/unodebip_nbipoamip.html

../RNCParaHtml/mbsc/m-para/unodebip_nbipoammask.html

../NodeBParaHtml/mml-mo-para/para/OMCH-LocalIP.html

../NodeBParaHtml/mml-mo-para/para/OMCH-LocalMask.html

../NodeBParaHtml/mml-mo-para/para/OMCH-PeerIP.html

../NodeBParaHtml/mml-mo-para/para/OMCH-PeerMask.html

../NodeBParaHtml/mml-mo-para/para/OMCH-BearType.html

WCDMA RAN




3-8

Figure 3-5 Iub over IP&ATM protocol stack

ATM Data linklayer

AAL 2

UDP

IP

NBAP

Transport

network

control plane

User plane

Physical layer

Control plane

ATM ATM

AAL 5

SSCOP

SSCF-UNI

ALCAP

Q.2630.1

Q.2150.2

Data linklayer

AAL 5

SSCOP

SSCF-UNI

IP

SCTP

Transport network layer

user plane

DC

H F

P

RA

CH

FP

FA

CH

FP

PC

H F

P

HS

-DS

CH

FP

E-D

CH

FP


user plane

Radio

network

layer

Transport

network

layer

When Iub over IP&ATM is used, the RNC supports the following transport modes at the data link layer:

IP: IP over E1/T1, IP over channelized STM-1/OC-3, IP over FE/GE, and IP over unchannelized STM-1/OC-3c

ATM: ATM over E1/T1, ATM over channelized STM-1/OC-3, and ATM over unchannelized STM-1/OC-3c

When Iub over IP&ATM is used, the BTS3900, BTS3900A, and DBS3900 support the following transport modes at the data link layer:

IP: IP over E1/T1, and IP over FE/GE

ATM: ATM over E1/T1 and ATM over unchannelized STM-1/OC-3c

When Iub over IP&ATM is used, the 3800 series NodeBs and V1-platform-based NodeBs support the following transport modes at the data link layer:

IP: IP over E1/T1 and IP over FE

ATM: ATM over E1/T1, ATM over channelized STM-1/OC-3, and ATM over unchannelized STM-1/OC-3c

Control Plane

The application protocol for the control plane of the Iub interface is the NBAP. NBAP is responsible for the transport of control plane messages between the NodeB and the CRNC at the radio network layer.

When Iub over IP&ATM is used, the control plane can be configured as the active/standby mode (SAAL and SCTP) to improve the transport reliability. The NCP configuration principle is the same as the CCP configuration principle. Figure 3-6 takes the NCP as an example to show the active/standby mode in the control plane in the case of Iub over IP&ATM.

WCDMA RAN




3-9

Figure 3-6 Active/standby mode in the control plane in the case of Iub over IP&ATM

When the NCP and CCP are added, the CARRYLNKT(NCP)/CARRYLNKT(CCP) parameter should be set on the RNC side to specify the bearer mode in the control plane. If this parameter is set to SAAL-SCTP, the active/standby mode (SAAL and SCTP) is used. If this parameter is set to SAAL or SCTP, the NCP and CCP are carried on the SAAL link or the SCTP link.

In active/standby mode, one SAAL link and one SCTP link are configured for each NCP and CCP. On the RNC side, the MAINLINK(ADD UCCP)/MAINLINK(ADD UNCP) parameter specifies the active link. On the NodeB side, the FLAG parameter specifies the active link.

The NCP and CCP data is preferentially transmitted on the active link. If the active link is unavailable, the data is automatically transferred to the standby link for transmission. After the active link becomes available, the ES parameter on the NodeB side can be used to specify whether the data is automatically transferred back to the active link for transmission.

User Plane

The radio network user plane of the Iub interface uses a series of frame protocols: DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, and E-DCH FP. These protocols are responsible for the transport of data and control frames between the NodeB and the CRNC. These frames contain Uu interface user data and user-related control data.

When Iub over IP&ATM is used, the user plane can be configured as the active/standby mode (AAL2 path and IP path) to improve the transport reliability. Figure 3-7 shows the active/standby mode in the user plane in the case of Iub over IP&ATM.

Figure 3-7 Active/standby mode in the user plane in the case of Iub over IP&ATM



../RNCParaHtml/mbsc/m-para/uccp_mainlink.html

../RNCParaHtml/mbsc/m-para/uncp_mainlink.html

../NodeBParaHtml/mml-mo-para/para/IUBCP-MSFlag.html

../NodeBParaHtml/mml-mo-para/para/DHCPRELAYSWITCH-Switch.html

WCDMA RAN




3-10

On the Iub interface, several IP paths and AAL2 paths can be configured simultaneously. The type of every path should be specified. On the RNC side, the PATHT parameter is used to specify the type of an IP path and the AAL2PATHT parameter is used to specify the type of an AAL2 path.

By configuring the TRM mapping table through the execution of the ADD TRMMAP command, the main path and standby path that carry each type of service can be specified. For example, the VOICEPRIPATH, and VOICESECPATH parameters should be set for AMR voice services. The RNC provides the default mapping relations for transmission resources.

When the RNC performs admission control on a new call, it preferentially uses the main path. If the admission of the new call fails on the main path, the RNC tries the standby path. For details, see the Transmission Resource Management Feature Parameter Description.

If an AAL2 path or an IP path is unavailable, the services carried on this path are disrupted. New service requests are established on the available path according to the TRM mapping table.

3.3.2 Trasnport Mode Configuration

To enable Iub over IP&ATM, set the following parameters on the RNC side:

The TnlBearerType parameter is set to ATMANDIP_TRANS.

The NODET parameter is set to IUB.

The TRANST parameter is set to ATM_IP.

3.3.3 Control Plane Link Configuration

SCTP Link

The parameter settings related to the SCTP link on the RNC and NodeB sides for Iub over IP&ATM are similar to those of Iub over IP. For details, see section 3.2.3 "SCTP Link."

SAAL Link

The SAAL link of User Network Interface (UNI) type is used to carry signaling messages on the Iub interface. The signaling messages are classified into NCP, CCP, and ALCAP, as described in Table 3-2.

Table 3-2 Signaling messages carried on an SAAL link of UNI type

Type Description

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

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

ALCAP The ALCAP is also called Q.AAL2. If a call connection is required on the AAL2 path between the RNC and the NodeB, the AAL2 path ID and CID information is exchanged through the ALCAP.

If the ATM network is unavailable and all the services are established on the IP path, the ALCAP is not required for signaling exchange. Therefore, the ALCAP must be carried by the SAAL link alone instead of by both the SAAL link and the SCTP link.

The parameters for establishing an SAAL link on the RNC side are as follows:


../RNCParaHtml/mbsc/m-para/aal2path_aal2patht.html

../RNCParaHtml/mbsc/m-para/trmmap_voicepripath.html

../RNCParaHtml/mbsc/m-para/trmmap_voicesecpath.html





WCDMA RAN




3-11

CARRYT: This parameter specifies the bearer type of the SAAL link outgoing port.

SAALLNKT: This parameter specifies the type of an SAAL link. SAAL links are classified into the UNI link and the NNI link. The UNI link is used for the Iub interface and the NNI link is used for the Iur and Iu interfaces.

TXTRFX: This parameter specifies the TX traffic record index of the SAAL link.

RXTRFX: This parameter specifies the RX traffic record index of the SAAL link.

CARRYVPI: This parameter specifies the VPI value of an SAAL link.

CARRYVCI: This parameter specifies the VCI value of an SAAL link.

The parameters for establishing an SAAL link on the NodeB side are as follows:

ST: This parameter specifies the bearing service type. It is recommended that the ST of the SAAL link be set to CBR.

VPI: This parameter specifies the VPI value of an SAAL link.

VCI: This parameter specifies the VCI value of an SAAL link.

The PVC identifier (VPI/VCI) of the SAAL link and other PVC attributes are negotiated between the RNC and the NodeB.

3.3.4 User Plane Path Configuration

IP Path

The parameter settings related to the IP path on the RNC and NodeB sides for Iub over IP&ATM are similar to those of Iub over IP. For details, see section 3.2.4 "IP Path."

AAL2 Path

An AAL2 path is a permanent virtual channel (PVC) between the AAL2 entity of the RNC and the AAL2 entity of the NodeB. The PVC identifier (VPI/VCI) and other PVC attributes are negotiated between the RNC and the NodeB.

The parameters for establishing an AAL2 path on the RNC side are as follows:

ANI: This parameter specifies the ID of an adjacent node. Each NodeB in the RNC and adjacent RNCs, MGWs, and SGSNs have an adjacent node ID.

PATHID: This parameter specifies the ID of the AAL2 path that connects the RNC and an adjacent node. The settings of this parameter are negotiated between the RNC and the NodeB.

VPI: This parameter specifies the VPI of the AAL2 path out BSC6900.

VCI: This parameter specifies the VCI of the AAL2 path out BSC6900.

TXTRFX: This parameter specifies the TX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table. You can use the MML command LST ATMTRF to see the ATM traffic table.

RXTRFX: This parameter specifies the RX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table. You can use the MML command LST ATMTRF to see the ATM traffic table.

The parameters for establishing an AAL2 path on the NodeB side are as follows:

NT: This parameter specifies the type of the NodeB that functions as an AAL2 node. It can be set to HUB, LOCAL, or ADJNODE. LOCAL indicates a leaf NodeB. The AAL2 path is used to establish an AAL2 connection of this NodeB. HUB and ADJNODE indicate a Hub NodeB. The AAL2 path of HUB type is located between this NodeB and the upper-level equipment. It is used to receive the RNC messages required for the lower-level NodeBs to establish a link. The AAL2 path of ADJNODE type is

../RNCParaHtml/mbsc/m-para/saallnk_carryt.html

../RNCParaHtml/mbsc/m-para/saallnk_saallnkt.html

../RNCParaHtml/mbsc/m-para/saallnk_txtrfx.html

../RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.html

../RNCParaHtml/mbsc/m-para/saallnk_carryvpi.html

../RNCParaHtml/mbsc/m-para/saallnk_carryvci.html

../NodeBParaHtml/mml-mo-para/para/SAALLNK-SERVICETYPE.html


../NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.html

../NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.html

../RNCParaHtml/mbsc/m-para/aal2path_ani.html

../RNCParaHtml/mbsc/m-para/aal2path_pathid.html

../RNCParaHtml/mbsc/m-para/aal2path_vpi.html

../RNCParaHtml/mbsc/m-para/aal2path_vci.html

../RNCParaHtml/mbsc/m-para/aal2path_txtrfx.html

../RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.html

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-NT.html

WCDMA RAN




3-12

located between this NodeB and the lower-level NodeB. It is used to forward the lower-level NodeB link establishment messages to this NodeB.

PATHID: This parameter specifies the ID of the AAL2 path that connects the RNC and an adjacent node. This parameter should be set to the same value as the PATHID parameter on the RNC side.

ST: This parameter specifies the bearing service type.

VPI: This parameter specifies the VPI of the AAL2 path.

VCI: This parameter specifies the VCI of the AAL2 path.

3.3.5 OM Channel Configuration

The OM channel between the RNC and the NodeB also supports the dual-stack (IP and ATM) mode. In actual situations, the OM channel can be based on IP, ATM, or both.

When the OM channel is based on IP and ATM, the parameter settings are as follows:

The parameter settings of the IP-based OM channel for Iub over IP&ATM are the same as those for Iub over IP. For details, see section 3.2.5 "OM Channel."

The parameter settings of the ATM-based OM channel for Iub over IP&ATM are the same as those for Iub over ATM. For details, see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide.


To enable Iur over IP&ATM, the following data should also be configured: physical layer data, data link layer data, TRM mapping table, and activation factor table.

For details about these configurations, see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide.

3.4 Iu-CS over IP

The Iu-CS interface connects the RNC and the MSC or MSC server. When the Iu-CS over IP protocol stack is used, the data in the control and user planes of the Iu-CS interface is transported over IP.


Figure 3-8 shows the Iu-CS over IP protocol stack.

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-PATHID.html


../NodeBParaHtml/mml-mo-para/para/AAL2PATH-ST.html

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-VPI.html

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-VCI.html

WCDMA RAN




3-13

Figure 3-8 Iu-CS over IP protocol stack

RANAP Iu UP

IP

M3UA

SCCP

SCTP

UDP/IP

RTP

Data link layerData link layer

Radio

network

layer

Transport

network

layer

Physical layer


user plane

Control plane User plane


user plane

Control plane

The application protocol for the control plane of the Iu-CS interface is the Radio Access Network Application Part (RANAP). The UE communicates with a circuit switched (CS) or packet switched (PS) node on the core network (CN) through RANAP signaling messages.

When Iu-CS over IP is used, RANAP is carried on the SCTP link.

User plane

The application protocol for the user plane of the Iu-CS interface is the Iu-UP. Iu-UP is responsible for the transport of the user data carried on the radio access bearer (RAB).

When Iu-CS over IP is used, Iu-UP is carried on the IP path.


On the RNC side, the transport mode of Iu-CS over IP should be configured before other data. The associated parameters need to be set as follows:

The CNDomainId parameter is set to CS_DOMAIN.

The TnlBearerType parameter is set to IP_TRANS.

The NODET parameter is set to IUCS.

The TRANST parameter is set to IP.


The parameter settings of the SCTP link on the RNC side for Iu-CS over IP are similar to those of Iub over IP. For details, see section 3.2.3 "SCTP Link."

../RNCParaHtml/mbsc/m-para/ucndomain_cndomainid.html

../RNCParaHtml/mbsc/m-para/ucnnode_tnlbearertype.html



WCDMA RAN




3-14


The parameter settings of the IP path on the RNC side for Iu-CS over IP are similar to those of Iub over IP. For details, see section 3.2.4 "IP Path."


To enable Iu-CS over IP, the following data should also be configured: physical layer data, data link layer data, TRM mapping table, activation factor table, and M3UA data.

For details about these configurations, see the BSC6900 UMTS Initial Configuration Guide.

3.5 Iu-PS over IP

The Iu-PS interface connects the RNC and the SGSN. When the Iu-PS over IP protocol stack is used, the data in the control and user planes of the Iu-PS interface is transported over IP.


Figure 3-9 shows the Iu-PS over IP protocol stack.

Figure 3-9 Iu-PS over IP protocol stack

Radio

network

layer

Transport

network

layer

RANAP

Data link layer

IP

M3UA

SCCP

SCTP

Control plane


user plane

Data link layer

GTP-U

UDP

IP

User plane

Iu UP


user plane

Physical layer

Control plane

The application protocol for the control plane of the Iu-PS interface is the RANAP. The UE communicates with a CS or PS node on the CN through RANAP signaling messages.

When Iu-PS over IP is used, RANAP is carried on the SCTP link.

User plane

The application protocol for the user plane of the Iu-PS interface is the Iu-UP. Iu-UP is responsible for the transport of the user data carried on the RAB.

When Iu-PS over IP is used, Iu-UP is carried on the IP path.

WCDMA RAN




3-15


On the RNC side, the transport mode of Iu-PS over IP should be configured before other data. The associated parameters need to be set as follows:

The CNDomainId parameter is set to PS_DOMAIN.


The NODET parameter is set to IUPS.



The parameter settings of the SCTP link on the RNC side for Iu-PS over IP are similar to those of Iub over IP. For details, see section 3.2.3 "SCTP Link."


The parameter settings of the IP path on the RNC side for Iu-PS over IP are similar to those of Iub over IP. For details, see section 3.2.4 "IP Path."


To enable Iu-PS over IP, the following data should also be configured: physical layer data, data link layer data, TRM mapping table, activation factor table, and M3UA data.


3.6 Iur over IP

The Iur interface connects RNCs. When the Iur over IP protocol stack is used, the data in the control and user planes of the Iur interface is transported over IP.


Figure 3-10 shows the Iur over IP protocol stack.

../RNCParaHtml/mbsc/m-para/ucnnode_cndomainid.html




WCDMA RAN




3-16

Figure 3-10 Iur over IP protocol stack

Physical layer

RNSAP Iur Data Stream

Data link layerData link layer

IP

M3UA

SCCP

SCTPUDP/IP

Radio

network

layer

Transport

network

layer

Control plane User plane


user plane


user plane

Control plane

The application protocol for the control plane of the Iur interface is the Radio Network Subsystem Application Part (RNSAP). The UE communicates with the DRNC through RNSAP signaling messages.

When Iur over IP is used, RNSAP is carried on the SCTP link.

User plane

The Iur data stream carries the data forwarded by the DRNC between the SRNC and the NodeB.

When Iur over IP is used, the Iur data stream is carried on the IP path.


On the RNC side, the transport mode of Iur over IP should be configured before other data. The associated parameters need to be set as follows:

The IurExistInd parameter is set to TRUE.


The NODET parameter is set to IUR.



The parameter settings of the SCTP link on the RNC side for Iur over IP are similar to those of Iub over IP. For details, see section 3.2.3 "SCTP Link."


The parameter settings of the IP path on the RNC side for Iur over IP are similar to those of Iub over IP. For details, see section 3.2.4 "IP Path."

../RNCParaHtml/mbsc/m-para/unrnc_iurexistind.html

../RNCParaHtml/mbsc/m-para/unrnc_tnlbearertype.html



WCDMA RAN




3-17


To enable Iur over IP, the following data should also be configured: physical layer data, data link layer data, TRM mapping table, activation factor table, and M3UA data.


WCDMA RAN

IP RAN 4 IP RAN Networking



4-1

4 IP RAN Networking

4.1 Overview

This section describes the IP networking on the terrestrial interfaces of RAN.

4.2 Iub Interface Networking

The Iub interface supports star, link, and ring topologies. From the perspective of transport bearers, the Iub interface supports ATM transport networking, IP transport networking (including hybrid IP transport), and hybrid ATM/IP transport networking.

Sections 4.2.1 “Iub over IP Networking” and 4.2.2 “Iub over IP&ATM Networking” describe Iub over IP networking (including hybrid IP transport) and Iub over IP&ATM networking respectively.

4.2.1 Iub over IP Networking

Based on the data switching technology that is used, IP networking can be classified into layer 2 networking and layer 3 networking. In addition, the Iub interface can use hybrid IP transport networking to improve the transport reliability of the Iub interface.

Layer 2 Networking

Layer 2 networking is relatively simple because all the network devices are located on the same network segment. In this case, data is switched by layer 2 devices (for example, LAN switches), and IP routes need not be configured.

Figure 4-1 shows an example of layer 2 networking in the case of Iub over IP.

Figure 4-1 Example of layer 2 networking in the case of Iub over IP

As shown in Figure 4-1, the NodeBs and the RNC are connected through a layer 2 network. To improve the transport security of the Iub interface, the RNC uses port backup. The layer 2 network distinguishes data from different NodeBs according to the VLAN ID. In addition, the layer 2 network provides differentiated services according to the PRI field in the VLAN tag. If the network is congested, high-priority packets are scheduled, and low-priority packets are buffered or discarded, as shown in Figure 4-2.

WCDMA RAN




4-2

Figure 4-2 Example of VLAN application on the Iub interface

IP address configuration

To facilitate data configuration, on the RNC side a port IP address is configured as the common IP address of the control plane, user plane, and OM; on the NodeB side a port IP address is configured as the common IP address of the control and user planes, and another IP address is configured for the OM. The port IP address and the OM IP address can be located either on the same network segment or on different network segments. If they are located on the same network segment, the ARP proxy function of the FE port must be enabled, that is, the ARPPROXY parameter on the NodeB side must be set to ENABLE.

The BTS3900, BTS3900A, and DBS3900 support a single IP address for a NodeB. In other words, the control plane, user plane, and OM of a NodeB can share one IP address.

IP route configuration

Routes are not required for layer 2 networking.

Layer 3 Networking

In layer 3 networking, the network devices are located on different network segments. In this case, data is switched by layer 3 devices (for example, routers), and IP routes need to be configured.

Figure 4-3 shows an example of layer 3 networking in the case of Iub over IP.

../NodeBParaHtml/mml-mo-para/para/ETHPORT-ARPProxy.html

WCDMA RAN




4-3

Figure 4-3 Example of layer 3 networking in the case of Iub over IP

As shown in Figure 4-3, the RNC and the NodeBs are connected through a layer 3 network. To improve the transport security of the Iub interface, the RNC uses active and standby GE ports to connect to the two peer GE ports on the layer 3 router. In addition, the layer 3 network provides differentiated services according to the DSCP value in the IP header. If the network is congested, high-priority packets are scheduled, and low-priority packets are buffered or discarded.

IP address configuration

The two GE ports on the router are configured in the same VLAN and share one VLAN port IP address (VLAN IF IP shown in Figure 4-3).

The active and standby GE ports on the RNC side share one IP address, which is on the same network segment as the VLAN IF IP address of the router. The port IP address on the RNC side functions as the common IP address of the control plane, user plane, and OM.

On the NodeB side, a port IP address is configured as the common IP address of the control and user planes, and another IP address is configured for the OM. The port IP address and the OM IP address can be located either on the same network segment or on different network segments. If they are located on the same network segment, the ARP proxy function of the FE port must be enabled, that is, the ARPPROXY parameter on the NodeB side must be set to ENABLE.

The BTS3900, BTS3900A, and DBS3900 support a single IP address for a NodeB. In other words, the control plane, user plane, and OM of a NodeB can share one IP address.

A layer-2-enabled router supports the configuration of VLANs. One VLAN has several Ethernet ports and can be configured with a layer 3 IP address (VLAN IF IP) for the interworking between VLANs.

IP route configuration

On the RNC side, routes to the NodeBs need to be configured. The routes are accessible to each NodeB or to the network segment where several NodeBs are located. For example, as shown in Figure 4-3, only the route from the RNC to the network segment 10.10.0.0/16 is configured. Through this route, the RNC communicates with the two NodeBs.

Routes to the RNC should be configured for each NodeB. The configuration of routes for the routers in the intermediate network depends on the actual networking conditions.

Hybrid IP Transport

Two networks with different quality of service (QoS) requirements can co-exist on the Iub interface to achieve hybrid IP transport (WRFD-050403 Hybrid Iub IP Transmission).

Figure 4-4 shows an example of hybrid IP transport.


WCDMA RAN




4-4

Figure 4-4 Example of hybrid IP transport

As shown in Figure 4-4, services with different QoS requirements are processed by different networks.

Low-QoS network (data network, for example, Ethernet): carries low-QoS services such as PS interactive and background services.

High-QoS network (TDM network, for example, PDH or SDH network): carries control plane data, Radio Resource Control (RRC) signaling, common channel data, CS services, and PS conversational and streaming services.

In actual networking, the RNC and the NodeB can be connected to two networks through two ports respectively. Alternatively, they can be connected to the external data device through the same port, and then the external data device distributes the services to different networks based on the settings of the DSCP value and VLAN.

Hybrid IP transport enables flexible processing of the services with different QoS requirements, but it makes network management complicated.

4.2.2 Iub over IP&ATM Networking

With the development of data services and the introduction of High Speed Packet Access (HSPA), the bandwidth requirement of the Iub interface is on the increase. The ATM network provides a high QoS, but it requires high transmission costs. The IP network does not require high transmission costs, but it provides a relatively low QoS. In this case, Iub over IP&ATM networking is introduced so that services with different QoS requirements can be processed in different types of networks.

Figure 4-5 shows an example of Iub over IP&ATM networking.

Figure 4-5 Example of Iub over IP&ATM networking

As shown in Figure 4-5, the IP and ATM networks can carry services with different QoS requirements respectively.

High-QoS network (ATM network): carries voice services, streaming services, and signaling.

WCDMA RAN




4-5

Low-QoS network (IP network): carries services with low-QoS requirements, such as PS Best Effort (BE) services.

In actual networking, both the RNC and the NodeB should be configured with ATM interface boards and IP interface boards, because the RNC and the NodeB are connected to the ATM network through the ATM interface boards and to the IP network through the IP interface boards.

In Iub over IP&ATM networking, the ATM network can provide a high QoS, and the IP network can reduce the transmission costs and meet the requirements of high-speed data services on the Iub interface for high bandwidth. The network maintenance, however, is complex and expensive because both the ATM and IP networks need to be maintained.

4.3 Iu/Iur Interface Networking

Figure 4-6 shows an example of Iu/Iur over IP networking.

Figure 4-6 Example of Iu/Iur over IP networking

The IP network shown in Figure 4-6 can be any one of the following networks:

Layer 2 network, for example, metro Ethernet, VPLS network, and MSTP network

Layer 3 network, for example, IP network and MPLS VPN

WCDMA RAN

IP RAN 5 Parameters



5-1

5 Parameters

Table 5-1 Parameter description

Parameter ID NE MML Command Description

AAL2PATHT BSC6900 ADD AAL2PATH(Mandatory)

MOD AAL2PATH(Optional)

Meaning: Service type of carried over the PATH. For R99, only the R99 service can be carried. For HSPA, only the HSPA service can be carried. For SHARE, R99 and HSPA services can be carried at the same time.

GUI Value Range: R99(R99), HSPA(HSPA), SHARE(SHARE)

Actual Value Range: R99, HSPA, SHARE

Default Value: None

ANI BSC6900 ADD AAL2PATH(Mandatory)

MOD AAL2PATH(Mandatory)

RMV AAL2PATH(Mandatory)

Meaning: Uniquely identifies an adjacent node. The numbers of adjacent nodes range from 0 to 4599. Adjacent nodes are uniquely but not necessarily consecutively numbered within a BSC6900.

GUI Value Range: 0~4599

Actual Value Range: 0~4599

Default Value: None

APP BSC6900 ADD SCTPLNK(Mandatory)

Meaning: Upper layer application type of the SCTP link. The upper layer application type of the Iub interface is NBAP. The upper layer application type of the Iur, IuPS, IuCS, A and LB interface is M3UA. In the BSC disaster tolerance, the application type is BBAP in the case of the communication between the primary and secondary BSC.

GUI Value Range: NBAP(NBAP), M3UA(M3UA), BBAP(BBAP)

Actual Value Range: NBAP, M3UA, BBAP

Default Value: None

ARPPROXY NodeB ADD ETHPORT

SET ETHPORT

Meaning: Indicates whether to enable the ARP proxy function. If the ARP proxy function is enabled, the system performs the ARP proxy on the IP addresses of loopback interfaces on the BS or the IP addresses of ports on the lower-level BS. If the ARP proxy function is disabled, the system does not perform the ARP proxy on the IP addresses of loopback interfaces on the BS or the IP addresses of ports on the lower-level BS. In this case, the external device whose IP address is on the same subnet as the IP address of the loopback interface on the BS (or of the lower-level BS) needs to access the loopback interface (or the lower-level BS) through a

../RNCParaHtml/mbsc/m-para/aal2path_aal2patht.html

../RNCParaHtml/mbsc/m-mml/add-aal2path.html


../RNCParaHtml/mbsc/m-mml/mod-aal2path.html


../RNCParaHtml/mbsc/m-para/aal2path_ani.html





../RNCParaHtml/mbsc/m-mml/rmv-aal2path.html


../RNCParaHtml/mbsc/m-para/sctplnk_app.html

../RNCParaHtml/mbsc/m-mml/add-sctplnk.html



../NodeBMMLHtml/mml-mo-para/mml/add_ethport.html

../NodeBMMLHtml/mml-mo-para/mml/set_ethport.html

WCDMA RAN

IP RAN 5 Parameters



5-2


route. This parameter does not take effect after the Ethernet port is added to an Ethernet trunk.

GUI Value Range: DISABLE(Disable), ENABLE(Enable)

Actual Value Range: DISABLE, ENABLE

Default Value: DISABLE(Disable)

BEAR NodeB ADD OMCH

MOD OMCH

Meaning: Indicates the bearer type of a remote maintenance channel. This parameter can be set to ATM or IPV4.

If this parameter is set to ATM, the Element Management System (EMS) uses the ATM transport network to maintain the device.

If this parameter is set to IPV4, the EMS uses the IP transport network to maintain the device.

GUI Value Range: ATM(ATM), IPV4(IPV4)

Actual Value Range: ATM, IPV4

Default Value: IPV4(IPV4)

BEAR NodeB ADD IUBCP Meaning: Indicates the bearer type of the Iub control port.

GUI Value Range: ATM(ATM), IPV4(IPV4)

Actual Value Range: ATM, IPV4

Default Value: ATM(ATM)

CARRYLNKT BSC6900 ADD UCCP(Mandatory) Meaning: When the NCP/CCP is based on ATM, set Bearing link type to SAAL. When the NCP/CCP is based on IP, set Bearing link type to SCTP. When the NCP/CCP is based on ATM/IP, set Bearing link type to SAAL-SCTP. For detailed information of this parameter, refer to 3GPP TS 25.430.

GUI Value Range: SAAL(SAAL Link Type ), SCTP(SCTP Link Type), SAAL-SCTP(SAAL-SCTP Link Tpye)

Actual Value Range: SAAL, SCTP, SAAL-SCTP

Default Value: None

CARRYLNKT BSC6900 ADD UNCP(Mandatory) Meaning: When the NCP/CCP is based on ATM, set Bearing link type to SAAL. When the NCP/CCP is based on IP, set Bearing link type to SCTP. When the NCP/CCP is based on ATM/IP, set Bearing link type to SAAL-SCTP. For detailed information of this parameter, refer to 3GPP TS 25.430.

GUI Value Range: SAAL(SAAL Link Type ),

../NodeBParaHtml/mml-mo-para/para/OMCH-BearType.html

../NodeBMMLHtml/mml-mo-para/mml/add_omch.html

../NodeBMMLHtml/mml-mo-para/mml/mod_omch.html

../NodeBParaHtml/mml-mo-para/para/IUBCP-CarryType.html

../NodeBMMLHtml/mml-mo-para/mml/add_iubcp.html


../RNCParaHtml/mbsc/m-mml/add-uccp.html


../RNCParaHtml/mbsc/m-mml/add-uncp.html

WCDMA RAN

IP RAN 5 Parameters



5-3


SCTP(SCTP Link Type), SAAL-SCTP(SAAL-SCTP Link Tpye)

Actual Value Range: SAAL, SCTP, SAAL-SCTP

Default Value: None

CARRYT BSC6900 ADD SAALLNK(Mandatory)

MOD SAALLNK(Optional)

Meaning: Bearer type of the SAAL link outgoing port

GUI Value Range: UNI(UNI), IMA(IMA), FRAATM(FRAATM), NCOPT(NCOPT), ATMLOGICPORT(ATMLOGICPORT), NULL(NULL)

Actual Value Range: UNI, IMA, FRAATM, NCOPT, ATMLOGICPORT, NULL

Default Value: None

CARRYVCI BSC6900 ADD SAALLNK(Mandatory)


Meaning: VCI value of the SAAL out BSC6900



Default Value: None

CARRYVPI BSC6900 ADD SAALLNK(Mandatory)


Meaning: VPI value of the SAAL out BSC6900



Default Value: None

CNDomainId BSC6900 ADD UCNNODE(Mandatory)

MOD UCNNODE(Mandatory)

Meaning: Identifying the type of a CN.

GUI Value Range: CS_DOMAIN, PS_DOMAIN

Actual Value Range: CS_DOMAIN, PS_DOMAIN

Default Value: None

CNDomainId BSC6900 ADD UCNDOMAIN(Mandatory)

MOD UCNDOMAIN(Mandatory)

RMV UCNDOMAIN(Mandatory)

Meaning: Identifying the type of a CN.

GUI Value Range: CS_DOMAIN, PS_DOMAIN

Actual Value Range: CS_DOMAIN, PS_DOMAIN

Default Value: None

CROSSIPFLAG BSC6900 ADD SCTPLNK(Optional)

MOD SCTPLNK(Optional)

Meaning: The field indicates whether the cross-connect path is available. When the cross-path is available, a maximum of four IP paths exists. The four IP paths are the IP path between the first local IP address and the first peer IP address, the IP path between the first local IP address and the second peer IP address, the IP path between the second local IP address and the first peer IP address, and the IP path between the second local IP address and the second peer IP address.

../RNCParaHtml/mbsc/m-para/saallnk_carryt.html

../RNCParaHtml/mbsc/m-mml/add-saallnk.html


../RNCParaHtml/mbsc/m-mml/mod-saallnk.html

../RNCParaHtml/mbsc/m-para/saallnk_carryvci.html




../RNCParaHtml/mbsc/m-para/saallnk_carryvpi.html




../RNCParaHtml/mbsc/m-para/ucnnode_cndomainid.html

../RNCParaHtml/mbsc/m-mml/add-ucnnode.html


../RNCParaHtml/mbsc/m-mml/mod-ucnnode.html


../RNCParaHtml/mbsc/m-para/ucndomain_cndomainid.html

../RNCParaHtml/mbsc/m-mml/add-ucndomain.html

../RNCParaHtml/mbsc/m-mml/add-ucndomain.html

../RNCParaHtml/mbsc/m-mml/mod-ucndomain.html

../RNCParaHtml/mbsc/m-mml/mod-ucndomain.html

../RNCParaHtml/mbsc/m-mml/rmv-ucndomain.html

../RNCParaHtml/mbsc/m-mml/rmv-ucndomain.html

../RNCParaHtml/mbsc/m-para/sctplnk_crossipflag.html


../RNCParaHtml/mbsc/m-mml/mod-sctplnk.html

WCDMA RAN

IP RAN 5 Parameters



5-4


When the cross-path is unavailable, a maximum of two IP paths exists. The two IP paths are the IP path between the first local IP address and the first peer IP address and the IP path between the second local IP address and the second peer IP address.

GUI Value Range: UNAVAILABLE(UNAVAILABLE), AVAILABLE(AVAILABLE)

Actual Value Range: UNAVAILABLE, AVAILABLE

Default Value: UNAVAILABLE

DSCP NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the Differentiated Services Code Point (DSCP) of the services carried on an IP path.



Default Value: None

DSCP BSC6900 ADD SCTPLNK(Optional)


Meaning: The DSCP is a field of the IP data packet. It is used to assign the differentiated service to the communication networks. The DSCP code is used to label each data packet on the network and allocate the corresponding service levels. In the same network environment, the larger the DSCP is, the higher the priority is.



Default Value: 48

ES NodeB SET DHCPRELAYSWITCH

Meaning: Indicates whether to enable the DHCP relay switch.

GUI Value Range: DISABLE(DISABLE), ENABLE(ENABLE)

Actual Value Range: DISABLE, ENABLE

Default Value: DISABLE(DISABLE)

FLAG NodeB ADD IUBCP

RMV IUBCP

Meaning: Indicates whether the transport channel carried on the Iub control port is a master or slave channel.

GUI Value Range: MASTER(Master), SLAVE(Slave)

Actual Value Range: MASTER, SLAVE

Default Value: MASTER(Master)

IP NodeB ADD OMCH

MOD OMCH

Meaning: Indicates the local IP address of the remote maintenance channel.

../NodeBParaHtml/mml-mo-para/para/IPPATH-DSCP.html

../NodeBMMLHtml/mml-mo-para/mml/add_ippath.html

../NodeBMMLHtml/mml-mo-para/mml/mod_ippath.html

../RNCParaHtml/mbsc/m-para/sctplnk_dscp.html



../NodeBParaHtml/mml-mo-para/para/DHCPRELAYSWITCH-Switch.html

../NodeBMMLHtml/mml-mo-para/mml/set_dhcprelayswitch.html

../NodeBMMLHtml/mml-mo-para/mml/set_dhcprelayswitch.html

../NodeBParaHtml/mml-mo-para/para/IUBCP-MSFlag.html

../NodeBMMLHtml/mml-mo-para/mml/add_iubcp.html

../NodeBMMLHtml/mml-mo-para/mml/rmv_iubcp.html

../NodeBParaHtml/mml-mo-para/para/OMCH-LocalIP.html



WCDMA RAN

IP RAN 5 Parameters



5-5


GUI Value Range: Valid IP address

Actual Value Range: Valid IP address

Default Value: None

IPADDR BSC6900 ADD IPPATH(Mandatory) Meaning: The local IP address must be the configured IP address (including the IP address and port address of the interface board).

GUI Value Range: None

Actual Value Range: 0.0.0.0~255.255.255.255

Default Value: None

IPTRANSAPARTIND BSC6900 ADD UNODEB(Mandatory)

MOD UNODEB(Optional)

Meaning: Indicating whether the Iub interface supports IP hybrid transport.

GUI Value Range: SUPPORT(Support), NOT_SUPPORT(Not support)

Actual Value Range: SUPPORT, NOT_SUPPORT

Default Value: None

ITFT BSC6900 ADD IPPATH(Mandatory)

MOD IPPATH(Mandatory)

Meaning: Type of the adjacent node

GUI Value Range: IUB(Iub Interface), IUR(Iur Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS Interface), ABIS(Abis Interface), A(A Interface), ATER(ATER Interface), IUR_G(IUR_G Interface)

Actual Value Range: IUB, IUR, IUCS, IUPS, ABIS, A, ATER, IUR_G

Default Value: None

IurExistInd BSC6900 ADD UNRNC(Mandatory)

MOD UNRNC(Optional)

Meaning: Indicating whether to config neighbouring RNC's DSP index.

GUI Value Range: TRUE, FALSE

Actual Value Range: TRUE, FALSE

Default Value: None

LOCALIP NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the local IP address of an IP path. This IP address must be a valid one of class A, B, or C but must not be the reserved address 0.x.x.x or 127.x.x.x. If this parameter is set to 0.0.0.0, this IP address needs to be negotiated.



Default Value: None

LOCIP NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the first local IP address of an SCTP link. It must be a valid IP address of class A, B, or C but must not be the reserved


../RNCParaHtml/mbsc/m-mml/add-ippath.html

../RNCParaHtml/mbsc/m-para/unodeb_iptransapartind.html

../RNCParaHtml/mbsc/m-mml/add-unodeb.html


../RNCParaHtml/mbsc/m-mml/mod-unodeb.html

../RNCParaHtml/mbsc/m-para/ippath_itft.html


../RNCParaHtml/mbsc/m-mml/mod-ippath.html

../RNCParaHtml/mbsc/m-para/unrnc_iurexistind.html

../RNCParaHtml/mbsc/m-mml/add-unrnc.html

../RNCParaHtml/mbsc/m-mml/mod-unrnc.html





../NodeBMMLHtml/mml-mo-para/mml/add_sctplnk.html

../NodeBMMLHtml/mml-mo-para/mml/mod_sctplnk.html

WCDMA RAN

IP RAN 5 Parameters



5-6


address 0.x.x.x or 127.x.x.x.



Default Value: 0.0.0.0

LOCIP1 BSC6900 ADD SCTPLNK(Mandatory)


Meaning: Identifies the first local IP address that communicates with the peer end. When it is set to 0, it is invalid. This IP address must be first configured on the corresponding interface board.



Default Value: None

LOCIP2 BSC6900 ADD SCTPLNK(Optional)


Meaning: Identifies the second local IP address that communicates with the peer end. When it is set to 0, it is invalid. This IP address must be first configured on the corresponding interface board.



Default Value: None

LOCPORT NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the local port number of the SCTP link.



Default Value: None

MAINLINK BSC6900 ADD UNCP(Optional) Meaning: Preferred type of the link used to carry a link when the bearer link type is SAAL-SCTP. When the current bearer link fails, it will be automatically carried on the other type of bearer link. For detailed description of this parameter, refer to the 3GPP TS 25.430.

GUI Value Range: SAAL(SAAL Link Type ), SCTP(SCTP Link Type)

Actual Value Range: SAAL, SCTP

Default Value: SAAL

MAINLINK BSC6900 ADD UCCP(Optional) Meaning: Preferred type of the link used to carry a link when the bearer link type is SAAL-SCTP. When the current bearer link fails, it will be automatically carried on the other type of bearer link. For detailed description of this parameter, refer to the 3GPP TS 25.430.

GUI Value Range: SAAL(SAAL Link Type ), SCTP(SCTP Link Type)

Actual Value Range: SAAL, SCTP








../NodeBParaHtml/mml-mo-para/para/SCTPLNK-LocPort.html



../RNCParaHtml/mbsc/m-para/uncp_mainlink.html


../RNCParaHtml/mbsc/m-para/uccp_mainlink.html


WCDMA RAN

IP RAN 5 Parameters



5-7


Default Value: SAAL

MASK NodeB ADD OMCH

MOD OMCH

Meaning: Indicates the local subnet mask of a remote maintenance channel.



Default Value: None

MODE NodeB ADD E1T1BEAR

SET E1T1BEAR

Meaning: Indicates the bearing mode of the E1/T1 port on a board.

GUI Value Range: ATM(ATM), IP(IP)

Actual Value Range: ATM, IP

Default Value: ATM(ATM)

MODE BSC6900 ADD SCTPLNK(Mandatory)


Meaning: SCTP link work mode. Server mode: BSC6900 starts the listening and waits for the peer to send the SCTP-INIT message. Client mode: BSC6900 actively sends the SCTP-INIT message.

GUI Value Range: SERVER(SERVER MOD), CLIENT(CLIENT MOD)

Actual Value Range: SERVER, CLIENT

Default Value: None

NBAPSRVPN BSC6900 SET SCTPSRVPORT(Optional)

Meaning: Number of the NBAP service listening port



Default Value: 58080

NBIPOAMIP BSC6900 MOD UNODEBIP(Optional)

ADD UNODEBIP(Mandatory)

Meaning: When the operation and maintenance channel of NodeB is operating in the IP transmission mode, this parameter indicates the address of the operation and maintenance console.



Default Value: None

NBIPOAMMASK BSC6900 MOD UNODEBIP(Optional)


Meaning: When the operation and maintenance channel of NodeB is operating in the IP transmission mode, this parameter indicates the mask of the operation and maintenance console.



Default Value: None

NBTRANTP BSC6900 MOD Meaning: Transmission type of NodeB

../NodeBParaHtml/mml-mo-para/para/OMCH-LocalMask.html



../NodeBParaHtml/mml-mo-para/para/E1T1BEAR-Mode.html

../NodeBMMLHtml/mml-mo-para/mml/add_e1t1bear.html

../NodeBMMLHtml/mml-mo-para/mml/set_e1t1bear.html






../RNCParaHtml/mbsc/m-mml/set-sctpsrvport.html

../RNCParaHtml/mbsc/m-mml/set-sctpsrvport.html

../RNCParaHtml/mbsc/m-para/unodebip_nbipoamip.html

../RNCParaHtml/mbsc/m-mml/mod-unodebip.html


../RNCParaHtml/mbsc/m-mml/add-unodebip.html


../RNCParaHtml/mbsc/m-para/unodebip_nbipoammask.html





../RNCParaHtml/mbsc/m-para/unodebip_nbtrantp.html


WCDMA RAN

IP RAN 5 Parameters



5-8


UNODEBIP(Mandatory)


GUI Value Range: ATMTRANS_IP(ATMTRANS_IP), IPTRANS_IP(IPTRANS_IP), ATMANDIPTRANS_IP(ATMANDIPTRANS_IP)

Actual Value Range: ATMTRANS_IP, IPTRANS_IP, ATMANDIPTRANS_IP

Default Value: None

NODET BSC6900 ADD ADJNODE(Mandatory)

MOD ADJNODE(Optional)

Meaning: Type of the adjacent node

GUI Value Range: IUB(Iub Interface), IUR(Iur Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS Interface), UNI_AAL2SWITCH(the adjacent node of the ATM switch on the Iub interface), NNI_AAL2SWITCH(the adjacent node of ATM switch on Iur or Iu-CS interface), ABIS(Abis Interface), A(A Interface), BSC(Ater Interface on BSC), TC(Ater Interface on TC), IUR_G(IUR_G Interface)

Actual Value Range: IUB, IUR, IUCS, IUPS, UNI_AAL2SWITCH, NNI_AAL2SWITCH, ABIS, A, BSC, TC, IUR_G

Default Value: None

NT NodeB ADD AAL2PATH

MOD AAL2PATH

RMV AAL2PATH

Meaning: Indicates the type of AAL2 path. If the local end node is selected, the AAL2 path is used by local services. If the switching node is selected, the AAL2 path is used to connect to the controller through the HUB BS. If the adjacent node is selected, the AAL2 path is used to connect to the lower-level BS through the HUB BS.

GUI Value Range: LOCAL(End Node), HUB(Switching Node), ADJNODE(Adjacent Node)

Actual Value Range: LOCAL, HUB, ADJNODE

Default Value: None

PATHID BSC6900 ADD AAL2PATH(Mandatory)

MOD AAL2PATH(Mandatory)

RMV AAL2PATH(Mandatory)

Meaning: ID of one AAL2 path between two AAL2 nodes. The PATHID of the same AAL2 path configured between two AAL2 nodes must be the same. The value should not be equal to 0.



Default Value: None

PATHID NodeB ADD AAL2PATH

MOD AAL2PATH

RMV AAL2PATH

Meaning: Indicates the number of the AAL2 path.






../RNCParaHtml/mbsc/m-mml/add-adjnode.html


../RNCParaHtml/mbsc/m-mml/mod-adjnode.html

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-NT.html

../NodeBMMLHtml/mml-mo-para/mml/add_aal2path.html

../NodeBMMLHtml/mml-mo-para/mml/mod_aal2path.html

../NodeBMMLHtml/mml-mo-para/mml/rmv_aal2path.html








../NodeBParaHtml/mml-mo-para/para/AAL2PATH-PATHID.html



../NodeBMMLHtml/mml-mo-para/mml/rmv_aal2path.html

WCDMA RAN

IP RAN 5 Parameters



5-9


Default Value: None

PATHT BSC6900 ADD IPPATH(Optional) Meaning: This parameter specifies the type of an IP path. It indicates the priority of the user plane data that is carried on the IP path. The mapping between the priority of the user plane data and IP path is configured through the "ADD TRMMAP" command. An IP path is of either the QoS type or the non-QoS type. For example, the IP paths used to carry BE data, AF data, and EF data are all of the non-QoS type. Different data can share the bandwidth of a QoS-type IP path. The bandwidth of a non-QoS type IP path, however, cannot be shared. IP path in hybrid IP transmission can be further categorized into high-priority IP path and low-priority IP path (identified as LQ_xx). When the bearing type of the physical port is PPP or MP, the non-QoS type IP path is configured as a high-priority path. When the physical port is an Ethernet port, the non-QoS type IP path is configured as a low-priority path. For the non-QoS type IP path, the priority of EF data is higher than that of AF data, which in turn is higher than that of BE data. The actual priority of user plane data, however, is set through the "SET PHBMAP" command.

GUI Value Range: QoS(QoS), BE(BE), AF11(AF11), AF12(AF12), AF13(AF13), AF21(AF21), AF22(AF22), AF23(AF23), AF31(AF31), AF32(AF32), AF33(AF33), AF41(AF41), AF42(AF42), AF43(AF43), EF(EF), LQ_QOS(LQ_QOS), LQ_BE(LQ_BE), LQ_AF11(LQ_AF11), LQ_AF12(LQ_AF12), LQ_AF13(LQ_AF13), LQ_AF21(LQ_AF21), LQ_AF22(LQ_AF22), LQ_AF23(LQ_AF23), LQ_AF31(LQ_AF31), LQ_AF32(LQ_AF32), LQ_AF33(LQ_AF33), LQ_AF41(LQ_AF41), LQ_AF42(LQ_AF42), LQ_AF43(LQ_AF43), LQ_EF(LQ_EF)

Actual Value Range: QoS, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, LQ_QOS, LQ_BE, LQ_AF11, LQ_AF12, LQ_AF13, LQ_AF21, LQ_AF22, LQ_AF23, LQ_AF31, LQ_AF32, LQ_AF33, LQ_AF41, LQ_AF42, LQ_AF43, LQ_EF

Default Value: None

PEERIP NodeB ADD OMCH

MOD OMCH

Meaning: Indicates the peer IP address of the connectivity detection of the remote maintenance channel. The BS performs PING from the local IP address to the peer IP



../NodeBParaHtml/mml-mo-para/para/OMCH-PeerIP.html



WCDMA RAN

IP RAN 5 Parameters



5-10


address of the remote maintenance channel. In general, the peer IP address is set to the IP address of the M2000; but when the BS cannot directly connect to the M2000 by performing PING, for example, a firewall is located between the BS and the M2000, the peer IP address can be set to the gateway IP address of the BS.



Default Value: None

PEERIP NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the first peer IP address of an SCTP link. It must be a valid IP address of class A, B, or C but must not be the reserved address 0.x.x.x or 127.x.x.x.




PEERIP NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the peer IP address of the IP path.



Default Value: None

PEERIP1 BSC6900 ADD SCTPLNK(Mandatory)


Meaning: First destination IP address. The invalid value is 0.



Default Value: None

PEERIP2 BSC6900 ADD SCTPLNK(Optional)


Meaning: Second destination IP address. The invalid value is 0.



Default Value: None

PEERIPADDR BSC6900 ADD IPPATH(Mandatory) Meaning: The peer IP address should not be the same as the local address.



Default Value: None

PEERMASK NodeB ADD OMCH

MOD OMCH

Meaning: Indicates the peer subnet mask of a remote maintenance channel.






../NodeBParaHtml/mml-mo-para/para/IPPATH-PeerIP.html










../RNCParaHtml/mbsc/m-para/ippath_peeripaddr.html


../NodeBParaHtml/mml-mo-para/para/OMCH-PeerMask.html



WCDMA RAN

IP RAN 5 Parameters



5-11


Default Value: None

PEERMASK BSC6900 ADD IPPATH(Optional) Meaning: Subnet mask of the peer IP




PEERPN BSC6900 ADD SCTPLNK(Mandatory)


Meaning: Destination SCTP port number



Default Value: None

PEERPORT NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the peer port number of the SCTP link. This port number must be the same as the local port number of the SCTP link that is configured on the RNC.



Default Value: None

PT NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the physical port type of the IP path.

GUI Value Range: PPP(PPP Link), MPGRP(Multi-link PPP Group), ETH(Ethernet Port), ETHTRK(Ethernet Trunk), LOOPINT(Loopback Interface)

Actual Value Range: PPP, MPGRP, ETH, ETHTRK, LOOPINT

Default Value: None

RXBW BSC6900 ADD IPPATH(Mandatory)

MOD IPPATH(Optional)

Meaning: Receive bandwidth of IP path



Default Value: None

RXBW NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the RX bandwidth of the IP path. When the IP path is not added to a transmission resource group, the RX bandwidth cannot be greater than the maximum RX bandwidth of the physical port. When the IP path is added to a transmission resource group, the RX bandwidth cannot be greater than the maximum RX bandwidth of the physical port on which the transmission resource group is established.



Default Value: 8

../RNCParaHtml/mbsc/m-para/ippath_peermask.html









../NodeBParaHtml/mml-mo-para/para/IPPATH-PortType.html






../NodeBParaHtml/mml-mo-para/para/IPPATH-RxBandwidth.html



WCDMA RAN

IP RAN 5 Parameters



5-12


RXTRFX BSC6900 ADD SAALLNK(Mandatory)


Meaning: RX traffic record index of the SAAL link



Default Value: None

RXTRFX BSC6900 ADD AAL2PATH(Mandatory)


Meaning: RX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table (see "LST ATMTRF").



Default Value: None

SAALLNKT BSC6900 ADD SAALLNK(Mandatory)


Meaning: Interface type of the SAAL link. The interface type of the Iub interface is UNI. The interface type of the Iu and Iur interface link is NNI.

GUI Value Range: UNI(UNI), NNI(NNI)

Actual Value Range: UNI, NNI

Default Value: None

SCTPLNKN BSC6900 ADD UNCP(Mandatory)

MOD UNCP(Mandatory)

Meaning: The numbers of SCTP links range from 0 to 1199. SCTP links are uniquely numbered within an XPU board. The numbering for SCTP links of the same type may not be consecutive.



Default Value: None

SCTPLNKN BSC6900 ADD UCCP(Mandatory)

MOD UCCP(Mandatory)

Meaning: The numbers of SCTP links range from 0 to 1199. SCTP links are uniquely numbered within an XPU board. The numbering for SCTP links of the same type may not be consecutive.



Default Value: None

SECLOCIP NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the second local IP address of the SCTP link. It must be a valid IP address of Class A, B, or C, but it cannot be set to 0.x.x.x or 127.x.x.x. The value 0.0.0.0 indicates that the second local IP address is invalid.



../RNCParaHtml/mbsc/m-para/saallnk_rxtrfx.html




../RNCParaHtml/mbsc/m-para/aal2path_rxtrfx.html





../RNCParaHtml/mbsc/m-para/saallnk_saallnkt.html




../RNCParaHtml/mbsc/m-para/uncp_sctplnkn.html


../RNCParaHtml/mbsc/m-mml/mod-uncp.html

../RNCParaHtml/mbsc/m-para/uccp_sctplnkn.html


../RNCParaHtml/mbsc/m-mml/mod-uccp.html

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-SecLocIP.html



WCDMA RAN

IP RAN 5 Parameters



5-13



SECPEERIP NodeB ADD SCTPLNK

MOD SCTPLNK

Meaning: Indicates the second peer IP address of an SCTP link. It must be a valid IP address of class A, B, or C but must not be the reserved address 127.x.x.x.




ST NodeB ADD SAALLNK

MOD SAALLNK

Meaning: Indicates the type of the service carried by the SAAL link. In flow control, services are classified into five categories: the Constant Bit Rate (CBR) service, Real-Time Variable Bit Rate (RTVBR) service, Non Real-Time Variable Bit Rate (NRTVBR) service, Unspecified Bit Rate Plus (UBR+) service, and Unspecified Bit Rate (UBR) service.

If this parameter is set to CBR, the bandwidth is calculated based on the PCR.

If this parameter is set to VBR, the bandwidth is calculated based on the SCR.

If this parameter is set to UBR, the bandwidth is calculated based on the PCR.

If this parameter is set to UBR+, the bandwidth is calculated based on the MCR.

GUI Value Range: CBR(CBR), RTVBR(RTVBR), NRTVBR(NRTVBR), UBR+(UBR+), UBR(UBR)

Actual Value Range: CBR, RTVBR, NRTVBR, UBR+, UBR

Default Value: CBR(CBR)

ST NodeB ADD AAL2PATH

MOD AAL2PATH

Meaning: Indicates the type of the service carried on the AAL2 path. In flow control, services carried by an AAL2 path are classified into five categories: the Constant Bit Rate (CBR) service, Real-Time Variable Bit Rate (RTVBR) service, Non-Real-Time Variable Bit Rate (NRTVBR) service, Unspecified Bit Rate Plus (UBR+) service, and Unspecified Bit Rate (UBR) service.

GUI Value Range: CBR(CBR), RTVBR(RTVBR), NRTVBR(NRTVBR), UBR+(UBR+), UBR(UBR)

Actual Value Range: CBR, RTVBR, NRTVBR, UBR+, UBR

Default Value: RTVBR(RTVBR)

TRANST BSC6900 ADD Meaning: Transport type

../NodeBParaHtml/mml-mo-para/para/SCTPLNK-SecPeerIP.html




../NodeBMMLHtml/mml-mo-para/mml/add_saallnk.html

../NodeBMMLHtml/mml-mo-para/mml/mod_saallnk.html

../NodeBParaHtml/mml-mo-para/para/AAL2PATH-ST.html





WCDMA RAN

IP RAN 5 Parameters



5-14


ADJNODE(Mandatory)

MOD ADJNODE(Optional)

GUI Value Range: ATM(ATM), IP(IP), ATM_IP(ATM and IP), HYBRID_IP(HYBRID IP)

Actual Value Range: ATM, IP, ATM_IP, HYBRID_IP

Default Value: None

TRANST BSC6900 ADD IPPATH(Mandatory) Meaning: Transport type of the adjacent node to which the path belongs

GUI Value Range: IP(IP), HYBRID_IP(HYBRID IP)

Actual Value Range: IP, HYBRID_IP

Default Value: None

TXBW NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the TX bandwidth of an IP path. When the IP path is not added to a transmission resource group, the TX bandwidth cannot be greater than the maximum TX bandwidth of the physical port. When the IP path is added to a transmission resource group, the TX bandwidth cannot be greater than the maximum TX bandwidth of the physical port on which the transmission resource group is established.



Default Value: 8

TXBW BSC6900 ADD IPPATH(Mandatory)

MOD IPPATH(Optional)

Meaning: Transmit bandwidth of IP path



Default Value: None

TXCBS NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the TX committed burst size at the IP path.



Default Value: 15000

TXEBS NodeB ADD IPPATH

MOD IPPATH

Meaning: Indicates the TX excessive burst size at the IP path.



Default Value: 0

TXTRFX BSC6900 ADD SAALLNK(Mandatory)


Meaning: TX traffic record index of the SAAL link


../RNCParaHtml/mbsc/m-mml/mod-adjnode.html

../RNCParaHtml/mbsc/m-para/ippath_transt.html


../NodeBParaHtml/mml-mo-para/para/IPPATH-TxBandwidth.html



../RNCParaHtml/mbsc/m-para/ippath_txbw.html



../NodeBParaHtml/mml-mo-para/para/IPPATH-TxCBS.html



../NodeBParaHtml/mml-mo-para/para/IPPATH-TxEBS.html



../RNCParaHtml/mbsc/m-para/saallnk_txtrfx.html




WCDMA RAN

IP RAN 5 Parameters



5-15



Default Value: None

TXTRFX BSC6900 ADD AAL2PATH(Mandatory)


Meaning: TX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table (see "LST ATMTRF").



Default Value: None

TnlBearerType BSC6900 ADD UCNNODE(Optional)

MOD UCNNODE(Optional)

Meaning: The transfers bearer type of Iu interface.

GUI Value Range: ATM_TRANS, IP_TRANS

Actual Value Range: ATM_TRANS, IP_TRANS

Default Value: None

TnlBearerType BSC6900 ADD UNRNC(Mandatory)

MOD UNRNC(Mandatory)

Meaning: The transfers bearer type of Iur interface.

GUI Value Range: ATM_TRANS, IP_TRANS

Actual Value Range: ATM_TRANS, IP_TRANS

Default Value: None

TnlBearerType BSC6900 ADD UNODEB(Optional)

MOD UNODEB(Optional)

Meaning: Transport type of the Iub interface

GUI Value Range: ATM_TRANS(ATM circuit transmission), IP_TRANS(IP transmission), ATMANDIP_TRANS(ATM and IP transmission), HYBRID_IP_TRANS(Hybrid IP transmission)

Actual Value Range: ATM_TRANS, IP_TRANS, ATMANDIP_TRANS, HYBRID_IP_TRANS

Default Value: ATM circuit transmission

VCI BSC6900 ADD AAL2PATH(Mandatory)


Meaning: VCI of the AAL2 path out BSC6900



Default Value: None

VCI NodeB ADD SAALLNK Meaning: Indicates the Virtual Channel Identifier (VCI), which is used for VC routing.



Default Value: None

VCI NodeB ADD AAL2PATH Meaning: Indicates the Virtual Channel Identifier (VCI) of the AAL2 path.

../RNCParaHtml/mbsc/m-para/aal2path_txtrfx.html









../RNCParaHtml/mbsc/m-para/unrnc_tnlbearertype.html

../RNCParaHtml/mbsc/m-mml/add-unrnc.html

../RNCParaHtml/mbsc/m-mml/mod-unrnc.html



../RNCParaHtml/mbsc/m-mml/mod-unodeb.html

../RNCParaHtml/mbsc/m-para/aal2path_vci.html





../NodeBParaHtml/mml-mo-para/para/SAALLNK-VCI.html


../NodeBParaHtml/mml-mo-para/para/AAL2PATH-VCI.html


WCDMA RAN

IP RAN 5 Parameters



5-16




Default Value: None

VOICEPRIPATH BSC6900 ADD TRMMAP(Optional)

MOD TRMMAP(Optional)

Meaning: AMR voice service bearer primary path

GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11, LQAF12, LQAF13, LQAF21, LQAF22, LQAF23, LQAF31, LQAF32, LQAF33, LQAF41, LQAF42, LQAF43, LQEF

Actual Value Range: CBR, RT_VBR, NRT_VBR, UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11, LQAF12, LQAF13, LQAF21, LQAF22, LQAF23, LQAF31, LQAF32, LQAF33, LQAF41, LQAF42, LQAF43, LQEF

Default Value: None

VOICESECPATH BSC6900 ADD TRMMAP(Optional)

MOD TRMMAP(Optional)

Meaning: AMR voice service bearer secondary path

GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11, LQAF12, LQAF13, LQAF21, LQAF22, LQAF23, LQAF31, LQAF32, LQAF33, LQAF41, LQAF42, LQAF43, LQEF, NULL

Actual Value Range: CBR, RT_VBR, NRT_VBR, UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11, LQAF12, LQAF13, LQAF21, LQAF22, LQAF23, LQAF31, LQAF32, LQAF33, LQAF41, LQAF42, LQAF43, LQEF, NULL

Default Value: None

VPI BSC6900 ADD AAL2PATH(Mandatory)


Meaning: VPI of the AAL2 path out BSC6900



Default Value: None

VPI NodeB ADD AAL2PATH Meaning: Indicates the Virtual Path Identifier (VPI) of the AAL2 path.



../RNCParaHtml/mbsc/m-para/trmmap_voicepripath.html

../RNCParaHtml/mbsc/m-mml/add-trmmap.html

../RNCParaHtml/mbsc/m-mml/mod-trmmap.html

../RNCParaHtml/mbsc/m-para/trmmap_voicesecpath.html

../RNCParaHtml/mbsc/m-mml/add-trmmap.html

../RNCParaHtml/mbsc/m-mml/mod-trmmap.html

../RNCParaHtml/mbsc/m-para/aal2path_vpi.html





../NodeBParaHtml/mml-mo-para/para/AAL2PATH-VPI.html


WCDMA RAN

IP RAN 5 Parameters



5-17


Default Value: None

VPI NodeB ADD SAALLNK Meaning: Indicates the Virtual Path Identifier (VPI), which is used for VP routing. A virtual path contains multiple virtual channels.



Default Value: None

../NodeBParaHtml/mml-mo-para/para/SAALLNK-VPI.html


WCDMA RAN

IP RAN 6 Counters



6-1

6 Counters

Table 6-1 Counter description

Counter ID Counter Name Counter Description

Feature ID Feature Name

67184352 VS.SCTP.RX.ERRPKGNUM T6010:Number of Error Packets Received on SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP

IP Transmission Introduction on Iub Interface

IP Transmission Introduction on Iu Interface

IP Transmission Introduction on Iur Interface

67191610 VS.SCTP.RX.BYTES T6001:Number of IP Bytes Received on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191611 VS.SCTP.TX.BYTES T6002:Number of IP Bytes Transmitted on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




../RNCCounterHtml/mbsc/m-perf/Mt-5152.html



WCDMA RAN

IP RAN 6 Counters



6-2



67191612 VS.SCTP.RX.PKGNUM T6003:Number of IP Packets Received on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191613 VS.SCTP.TX.PKGNUM T6004:Number of IP Packets Transmitted on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191614 VS.SCTP.RX.MAXBYTES T6005:Maximum Number of IP Bytes Received on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP







WCDMA RAN

IP RAN 6 Counters



6-3



67191615 VS.SCTP.TX.MAXBYTES T6006:Maximum Number of IP Bytes Transmitted on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191616 VS.SCTP.RX.MAXPKGNUM T6008:Maximum Number of IP Packets Received on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191617 VS.SCTP.TX.MAXPKGNUM T6009:Maximum Number of IP Packets Transmitted on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP







WCDMA RAN

IP RAN 6 Counters



6-4



67191618 VS.SCTP.SERVICE.INTERVAL T6011:Service Duration of the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67191619 VS.SCTP.CONGESTION.INTERVAL T6012:Congestion Duration of the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




67192144 VS.SCTP.RETX.PKGNUM T6007:Number of Packets Resent on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP







WCDMA RAN

IP RAN 6 Counters



6-5



67192414 VS.IPPART.Node.Conn.Modify.Succ Number of Successful IP Connection Modifications Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node

WRFD-050404

ATM/IP Dual Stack Node B

67192415 VS.IPPART.Node.Conn.Rel Number of IP Connection Release Requests Sent from the Radio Network Layer to the Transport Layer on the Dual-Stack Transport Adjacent Node

WRFD-050404


67192422 VS.QAAL2IP.AttResAlloc Number of Resource Requests Sent from the Radio Network Layer to the Transport Layer on Dual-Stack Transport Adjacent Node

WRFD-050404


67192423 VS.QAAL2IP.SuccResAlloc Number of Successful Resource Allocations After the Transport Layer Receives the Resource Requests from the Radio Network Layer on Dual-Stack Transport Adjacent Node

WRFD-050404


67192424 VS.QAAL2PART.Est.RLC.NoRoute.Rx Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Route at the Remote End

WRFD-050404







WCDMA RAN

IP RAN 6 Counters



6-6



67192425 VS.QAAL2PART.Est.RLC.NoPath.Rx Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No Path path Configured at the Remote End

WRFD-050404


67192446 VS.QAAL2PART.RxModRej Number of Modification Rejection (MOR) Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends Connection Modification Request (MOD) Messages

WRFD-050404


67192447 VS.QAAL2PART.TxModRej Number of MOR Messages Sent by QAAL2 on the Dual-Stack Adjacent Node After the QAAL2 Receives Connection MOD Messages

WRFD-050404


67192448 VS.QAAL2PART.TxMod Number of MOD Messages Sent by QAAL2 on Dual-Stack Adjacent Node

WRFD-050404


67192449 VS.QAAL2PART.RxMod Number of MOD Messages Received by QAAL2 on Dual-Stack Adjacent Node

WRFD-050404







WCDMA RAN

IP RAN 6 Counters



6-7



67194363 VS.FEGE.TXDROPPEDPKTS T7113:Number of frames Discarded in Transmission on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP

67194364 VS.FEGE.RXERRORPKTS T7114:Number of FCS(Frame Check Sequence) Error frames Received on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP

67194365 VS.FEGE.RXUNKNOWNPKTS T7115:Frames Number of Unknown Protocol Received on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP




WCDMA RAN

IP RAN 6 Counters



6-8



67194368 VS.FEGE.FAULTTIME T7118:Duration of Faults in the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP




67194369 VS.FEGE.RXMAXSPEED T7121:Highest Receive Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP




67194370 VS.FEGE.RXMINSPEED T7122:Lowest Receive Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP







WCDMA RAN

IP RAN 6 Counters



6-9



67194371 VS.FEGE.RXMEANSPEED T7123:Mean Receive Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP




67194372 VS.FEGE.TXMAXSPEED T7126:Highest Transmit Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP




67194373 VS.FEGE.TXMINSPEED T7127:Lowest Transmit Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP







WCDMA RAN

IP RAN 6 Counters



6-10



67194374 VS.FEGE.TXMEANSPEED T7128:Mean Transmit Rate of the FEGE Ethernet Port

GBFD-118601

GBFD-118602

GBFD-118603

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP

Gb over IP




67194611 VS.QAAL2PART.Est.RLC.NoCID.Rx Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to No CID Available at the Remote End

WRFD-050404


67194620 VS.QAAL2PART.Est.ECF.Tx Number of Connection ECF Messages Sent by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Receives the Connection ERQ Message

WRFD-050404


67194621 VS.QAAL2PART.Est.RLC.Tx Number of RLC Messages Sent by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Receives the Connection ERQ Message

WRFD-050404






WCDMA RAN

IP RAN 6 Counters



6-11



67194622 VS.QAAL2PART.Rel.Tx Number of Connection Release (REL) Messages Sent by QAAL2 on Dual-Stack Adjacent Node

WRFD-050404


67194623 VS.QAAL2PART.Rel.Rx Number of Connection REL Messages Received by QAAL2 on Dual-Stack Adjacent Node

WRFD-050404


67194626 VS.QAAL2PART.Est.RLC.Cong.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Switch Congestion

WRFD-050404


67194627 VS.QAAL2PART.Est.RLC.RecovOut.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Timer Expiry

WRFD-050404


67194628 VS.QAAL2PART.ERQ.Tx Number of Connection Establishment Request (ERQ) Messages Sent by QAAL2 on Dual-Stack Adjacent Node

WRFD-050404


67194629 VS.QAAL2PART.ERQ.Rx Number of Connection Establishment Requests Received by QAAL2 on the Dual-Stack Adjacent Node

WRFD-050404








WCDMA RAN

IP RAN 6 Counters



6-12



67194630 VS.QAAL2PART.Est.RLC.Rx Number of RLC Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages

WRFD-050404


67194631 VS.QAAL2PART.Est.ECF.Rx Number of ECF Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends the Connection ERQ Messages

WRFD-050404


67194632 VS.QAAL2PART.Rel.RLC.Rx Number of RLC Messages Received by QAAL2 on Dual-Stack Adjacent Node After the QAAL2 Sends REL Messages

WRFD-050404


67194633 VS.QAAL2PART.Rel.RLC.Tx Number of RLC Messages Sent by QAAL2 on the Dual-Stack Adjacent Node After the QAAL2 Receives Connection REL Messages

WRFD-050404


67194636 VS.IPPATH.PING.MaxDELAY T6553:Maximum IP Path Ping Delay

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP









WCDMA RAN

IP RAN 6 Counters



6-13



67194639 VS.IPPATH.PING.MaxJITTER T6555:Maximum IP Path Ping Delay variation

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67194642 VS.IPPATH.PING.MaxLOST T6557:Maximum IP Path Ping Packet Loss Rate

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67194658 VS.IPPART.Node.Conn.Estab.Att Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the Dual-Stack Transport Adjacent Node

WRFD-050404


67194659 VS.IPPART.Node.Conn.Estab.Succ Number of Successful IP Connection Setups Initiated by the Transport Layer on the Dual-Stack Transport Adjacent Node

WRFD-050404






WCDMA RAN

IP RAN 6 Counters



6-14



67194660 VS.IPPART.Node.Conn.Modify.Att Number of IP Connection Modifications on the Dual-Stack Transport Adjacent Node

WRFD-050404


67194661 VS.QAAL2PART.Est.RLC.Cong.Rx Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Switch Congestion at the Remote End

WRFD-050404


67194662 VS.QAAL2PART.Est.RLC.RecovOut.Rx Number of AAL2 Connection Release Confirmations Received by QAAL2 on Dual-Stack Adjacent Node Due to Timer Expiry at the Remote End

WRFD-050404


67194663 VS.QAAL2PART.Est.RLC.NoRoute.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Route

WRFD-050404


67194664 VS.QAAL2PART.Est.RLC.NoPath.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Path Configured

WRFD-050404







WCDMA RAN

IP RAN 6 Counters



6-15



67194665 VS.QAAL2PART.Est.RLC.NoCID.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No CID Available

WRFD-050404


67194666 VS.QAAL2PART.Est.RLC.Fail.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to Network Failure, Unspecified Reason, or Temporary Failure

WRFD-050404


67194793 VS.ANI.IP.Conn.Estab.Att T6501:Number of Connection Setup Requests for IP Transport from the Transport Layer to the Radio Network Layer on the IP Transport Adjacent Node

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195360 VS.LGCPRT.TXPACKETS T7501:Number of frames Transmitted over Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP








WCDMA RAN

IP RAN 6 Counters



6-16



67195361 VS.LGCPRT.TXBYTES T7502:Number of Bytes Transmitted over Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195362 VS.LGCPRT.TXDROPPACKETS T7503:Number of frames Discarded in Transmission over Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195363 VS.LGCPRT.TXDROPBYTES T7504:Number of Bytes Discarded in Transmission over a Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-17



67195365 VS.LGCPRT.QUEUE.TXPACKETS T7531:Number of Packets Transmitted over Logical Port Queue

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195366 VS.LGCPRT.QUEUE.TXBYTES T7532:Number of Bytes Transmitted over Logical Port Queue

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195367 VS.LGCPRT.QUEUE.TXDROPPACKETS T7533:Number of Packets Discarded in Transmission over Logical Port Queue

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-18



67195368 VS.LGCPRT.QUEUE.TXDROPBYTES T7534:Number of Bytes Discarded in Transmission over Logical Port Queue

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195395 VS.IPPATH.IPLAYER.TXPACKETS T7401:Number of Packets Transmitted at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195396 VS.IPPATH.IPLAYER.TXBYTES T7402:Number of Bytes Transmitted at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-19



67195397 VS.IPPATH.IPLAYER.TXDROPPACKETS T7403:Number of Packets Discarded in Transmission at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195398 VS.IPPATH.IPLAYER.TXDROPBYTES T7404:Number of Bytes Discarded in Transmission at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195399 VS.IPPATH.IPLAYER.RXPACKETS T7405:Number of Packets Received at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-20



67195400 VS.IPPATH.IPLAYER.RXBYTES T7406:Number of Bytes Received at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195401 VS.IPPATH.IPLAYER.RXDROPPACKETS T7407:Number of Packets Discarded in Reception at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195402 VS.IPPATH.IPLAYER.RXDROPBYTES T7408:Number of Bytes Discarded in Reception at the IP Layer of an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-21



67195599 VS.IPPATH.Fwd.Cong T6558:Number of Forward Congestions on the IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195600 VS.IPPATH.Fwd.Cong.Dur T6559:Duration of Forward Congestion on the IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67195601 VS.IPPATH.Bwd.Cong T6560:Number of Backward Congestions on the IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-22



67195602 VS.IPPATH.Bwd.Cong.Dur T6561:Duration of Backward Congestion on the IP PATH

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67196160 VS.QAAL2IP.FailResAllocForBwLimit Number of Failed Resource Allocations Due to Insufficient Bandwidth on the Dual-Stack Transport Adjacent Node

WRFD-050404


67196185 VS.QAAL2PART.Est.RLC.NoBitRate.Tx Number of AAL2 Connection Release Confirmations Sent by QAAL2 on Dual-Stack Adjacent Node Due to No Bandwidth

WRFD-050404


67204200 VS.IPPART.Node.Act.Con Mean Number of Active IP Connections to a Dual-Stack Transport Adjacent Node

WRFD-050404


67204201 VS.IPPART.AllocedFwd Forward Bandwidth of IP Path Allocated to a Dual-Stack Transport Adjacent Node

WRFD-050404


67204202 VS.IPPART.AllocedBwd Backward Bandwidth of IP Path Allocated to a Dual-Stack Transport Adjacent Node

WRFD-050404








WCDMA RAN

IP RAN 6 Counters



6-23



67204203 VS.QAAL2PART.Act.Con Number of Active AAL2 Connections to a Dual-Stack Transport Adjacent Node

WRFD-050404


67204204 VS.QAAL2PART.AllocedFwd.AAL2BitRate Mean Forward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node

WRFD-050404


67204205 VS.QAAL2PART.AllocedBwd.AAL2BitRate Mean Backward Bandwidth of AAL2 Path Allocated to a Dual-Stack Transport Adjacent Node

WRFD-050404


67204207 VS.IPPATH.Act.Con T6551:Number of Active Connections on an IP Path

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204390 VS.IPPATH.PING.MeanDELAY T6552:Average IP Path Ping Delay

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP









WCDMA RAN

IP RAN 6 Counters



6-24



67204391 VS.IPPATH.PING.MeanJITTER T6554:Average IP Path Ping Delay variation

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204392 VS.IPPATH.PING.MeanLOST T6556:Average IP Path Ping Packet Loss Rate

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204393 VS.FEGE.RXBYTES T7101:Number of Bytes Received on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP




WCDMA RAN

IP RAN 6 Counters



6-25



67204394 VS.FEGE.TXBYTES T7104:Number of Bytes Transmitted on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP

67204395 VS.FEGE.RXPACKETS T7107:Number of frames Received on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP

67204396 VS.FEGE.TXPACKETS T7110:Number of frames Transmitted on the FEGE Ethernet Port

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP




WCDMA RAN

IP RAN 6 Counters



6-26



67204684 VS.LGCPRT.PEAK.TXRATE T7506:Maximum Transmit Rate of Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204685 VS.LGCPRT.MEAN.TXRATE T7507:Average Transmit Rate of Logical Port

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204686 VS.LGCPRT.QUEUE.PEAK.TXRATE T7536:Maximum Transmit Rate of Logical Port Queue

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-27



67204698 VS.IPPATH.IPLAYER.PEAK.TXRATE T7410:Maximum Transmit Rate of an IP Path at the IP Layer

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204699 VS.IPPATH.IPLAYER.MEAN.TX T7411:Mean Transmit Rate of an IP Path at the IP Layer

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204700 VS.IPPATH.IPLAYER.PEAK.RXRATE T7413:Maximum Receive Rate of an IP Path at the IP Layer

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP







WCDMA RAN

IP RAN 6 Counters



6-28



67204701 VS.IPPATH.IPLAYER.MEAN.RX T7414:Mean Receive Rate of an IP Path at the IP Layer

GBFD-118601

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP




67204764 VS.FEGE.RXPAUSEFRAMES T7129:Number of the PAUSE Control Frames Received on the FEGE Ethernet Port

GBFD-118601

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP




67204765 VS.FEGE.TXPAUSEFRAMES T7130:Number of the PAUSE Control Frames Transmitted on the FEGE Ethernet Port

GBFD-118601

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

Abis over IP

A over IP







WCDMA RAN

IP RAN 6 Counters



6-29



73403174 UPUSER.SEND.MSG.NUM T6014:Number of Packets Sent on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




73403175 UPUSER.RECEIVE.MSG.NUM T6015:Number of Packets Received on SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




73422157 VS.INT.TRANSLOAD.RATIO.MAX HR9705a:Maximum Forwarding Ratio of Interface Boards

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP




WCDMA RAN

IP RAN 6 Counters



6-30



73423484 VS.SCTP.REQ.RETX.NUM T6016:Number of Retransmit Request Sent on the SCTP Link

GBFD-118602

WRFD-050402

WRFD-050409

WRFD-050410

A over IP




73440118 VS.INT.TRANSLOAD.RATIO.MEAN AR9705a:Average Forwarding Ratio of Interface Boards

WRFD-050402

WRFD-050409

WRFD-050410

GBFD-118601

GBFD-118602

GBFD-118603




Abis over IP

A over IP

Gb over IP



WCDMA RAN

IP RAN 7 Glossary



7-1

7 Glossary

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

Glossary.htm

WCDMA RAN

IP RAN 8 Reference Documents



8-1

8 Reference Documents

[1] 3GPP TS 25.410: UTRAN Iu Interface: General Aspects and Principles

[2] 3GPP TS 25.420: UTRAN Iur Interface: General Aspects and Principles

[3] 3GPP TS 25.430: UTRAN Iub Interface: General Aspects and Principles

[4] 3GPP TR25.933: IP transport in UTRAN

[5] BSC6900 UMTS Initial Configuration Guide

[6] BSC6900 UMTS Product Description

[7] IP Transport Architecture Feature Parameter Description

[8] NodeB Initial Configuration Guide

[9] NodeB Product Description

[10] NodeB Self-discovery Feature Parameter Description

[11] Security Feature Parameter Description

IP%20Transport%20Architecture.htm

NodeB%20Self-discovery.htm

Security.htm