Ip Ran

IP RAN
RAN12.0
Feature Parameter Description

Issue 01
Date 2010-03-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees 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 the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

WCDMA RAN
IP RAN Contents

Issue 01 (2010-03-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
i

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-9
3.3.3 Control Plane Link Configuration ........................................................................................ 3-10
3.3.4 User Plane Path Configuration ........................................................................................... 3-10
3.3.5 OM Channel Configuration ................................................................................................. 3-11
3.3.6 Other Data Configuration .................................................................................................... 3-11
3.4 Iu-CS over IP ............................................................................................................................... 3-11
3.4.1 Protocol Stack ..................................................................................................................... 3-11
3.4.2 Transport Mode Configuration ............................................................................................ 3-12
3.4.3 SCTP Link Configuration .................................................................................................... 3-12
3.4.4 IP Path Configuration ......................................................................................................... 3-13
3.5 Iu-PS over IP ............................................................................................................................... 3-13
3.5.1 Protocol Stack ..................................................................................................................... 3-13
3.6 Iur over IP .................................................................................................................................... 3-14
3.6.1 Protocol Stack ..................................................................................................................... 3-14
WCDMA RAN
IP RAN Contents

ii

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 (2010-03-30)

Draft (2009-12-05)
01 (2010-03-30)
This is the document for the first commercial release of RAN12.0.
Compared with issue Draft (2009-12-05) of RAN12.0, this issue optimizes the description.
Draft (2009-12-05)
This is the draft of the document for RAN12.0.
WCDMA RAN
IP RAN 1 Introduction

1-2

Compared with issue 02 (2009-06-30) of RAN11.0, this issue incorporates the changes described in the
following table.
Change Type Change Description Parameter Change
Feature change The OM IP address of the BTS3900,
BTS3900A, and DBS3900 can be the
same as either the control plane IP
address or the user plane IP address.
Two new IP interfaces boards, FG2c and
GOUc, are added.
The command ADD IPMUX is added, and
some parameters are moved from ADD
IPPATH to ADD IPMUX.
The command ADD CNNODE is renamed
ADD UCNNODE.
The added parameter is as follows:

MUXTYPE
The deleted parameter is as follows:

FPMUXSWITCH
The following parameters change:

GATEWAY in STR IPCHK is renamed
PEERIP.

Value range of MODE changes
Editorial change In this release, the IP RAN parameter
description is split into two documents.
Some technical aspects of IP RAN are
described in a new document named IP
Transport Architecture Description.
None.

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.
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 (WRFD-050402 IP
Transmission Introduction on Iub Interface).
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 E1/T1
over SDH, IP over SDH, and IP over Ethernet.
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, 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.
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.
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.

LOCPN: This parameter specifies the local port number only when the RNC functions as the client.
For the SCTP link on the Iub interface, the RNC functions as the server and thus this parameter need
not be set. For the SCTP link on the Iu interface, generally the RNC functions as the client and the
CN node functions as the server.

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: 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: 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.
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
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. 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-
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:
WCDMA RAN

3-5

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

NODEBIP: 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.

RNCIP: 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.
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.
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
WCDMA RAN

3-6

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

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 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.
WCDMA RAN

3-7

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.
Figure 3-5 Iub over IP&ATM protocol stack
ATM
Data link
layer
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 link
layer
AAL 5
SSCOP
SSCF-UNI
IP
SCTP
Transport network layer
user plane
D
C
H

F
P
R
A
C
H

F
P
F
A
C
H

F
P
P
C
H

F
P
H
S
-
D
S
C
H

F
P
E
-
D
C
H

F
P
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:
WCDMA RAN

3-8

IP: IP over E1/T1, IP over channelized STM-1/OC-3, IP over FE, IP over 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, IP over FE, and IP over 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.
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 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 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.
WCDMA RAN

3-9

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

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.
WCDMA RAN

3-10

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:

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.

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:

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

3-11

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.
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
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.
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
(WRFD-050409 IP Transmission Introduction on Iu Interface).
Figure 3-8 shows the Iu-CS over IP protocol stack.
WCDMA RAN

3-12

Figure 3-8 Iu-CS over IP protocol stack
RANAP
Iu UP
IP
M3UA
SCCP
SCTP
UDP/IP
RTP
Data link layer Data 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 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."
WCDMA RAN

3-13

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 (WRFD-050409 IP
Transmission Introduction on Iu Interface).
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-14

On the RNC side, the transport mode of Iu-PS over IP should be configured before other data. The

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 (WRFD-050410 IP Transmission Introduction
on Iur Interface).
Figure 3-10 shows the Iur over IP protocol stack.
WCDMA RAN

3-15

Figure 3-10 Iur over IP protocol stack
Physical layer
RNSAP Iur Data Stream
Data link layer Data link layer
IP
M3UA
SCCP
SCTP
UDP/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

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

3-16

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 and 4.2.2 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.
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 Description
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
Unit: None
Default Value: None
TnlBearerType BSC6900 ADD 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)
IP_TRANS, ATMANDIP_TRANS,
HYBRID_IP_TRANS
Unit: None
Default Value: ATM circuit transmission
TnlBearerType BSC6900 MOD UNODEB(Optional) Meaning: Indicate the transmission type
be used by 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)
IP_TRANS, ATMANDIP_TRANS,
HYBRID_IP_TRANS
Unit: None
Default Value: ATM_TRANS
IPTRANSAPART
IND
BSC6900 ADD UNODEB(Mandatory) 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
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-2

IPTRANSAPART
IND
BSC6900 MOD UNODEB(Optional) Meaning: IP transmission apart indication
of Iub interface.
GUI Value Range: SUPPORT(Support),
NOT_SUPPORT(Not support)
Actual Value Range: SUPPORT,
NOT_SUPPORT
Unit: None
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)
Actual Value Range: IUB, IUR, IUCS,
IUPS, UNI_AAL2SWITCH,
NNI_AAL2SWITCH
Unit: None
Default Value: None
TRANST BSC6900 ADD ADJNODE(Mandatory)
MOD ADJNODE(Optional)
Meaning: Transport type
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
Unit: None
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
Unit: None
Default Value: None
LOCIP1 BSC6900 ADD SCTPLNK(Mandatory)
MOD SCTPLNK(Optional)
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.
GUI Value Range: None
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-3

PEERIP1 BSC6900 ADD SCTPLNK(Mandatory)
Meaning: First destination IP address.
The invalid value is 0.
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
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.
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
LOCPN BSC6900 ADD SCTPLNK(Mandatory)
MOD SCTPLNK(Mandatory)
Meaning: Local SCTP port number
GUI Value Range: 1024~65535
Actual Value Range: 1024~65535
Unit: None
Default Value: None
NBAPSRVPN BSC6900 SET
SCTPSRVPORT(Optional)
Meaning: Number of the NBAP service
listening port
Unit: None
Default Value: 58080
PEERIP2 BSC6900 ADD SCTPLNK(Optional)
Meaning: Second destination IP address.
The invalid value is 0.
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
PEERPN BSC6900 ADD SCTPLNK(Mandatory)
Meaning: Destination SCTP port number
Unit: None
Default Value: None
DSCP BSC6900 SET DSCPMAP(Mandatory) Meaning: Differentiated service code is
used to identify the service priority of the
user.
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-4

DSCP BSC6900 SET PHBMAP(Mandatory) 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.
Unit: None
Default Value: 48
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.
Unit: None
Default Value: 48
WCDMA RAN
IP RAN 5 Parameters

5-5

CROSSIPFLAG BSC6900 ADD 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. 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
Unit: None
Default Value: UNAVAILABLE
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
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-6

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.
Type ), SCTP(SCTP Link Type), SAAL-
SCTP(SAAL-SCTP Link Tpye)
Actual Value Range: SAAL, SCTP,
SAAL-SCTP
Unit: None
Default Value: None
SCTPLNKN BSC6900 ADD SCTPLNK(Mandatory)
MOD SCTPLNK(Mandatory)
RMV SCTPLNK(Mandatory)
Meaning: SCTP link number of XPU
board. This number identifies an SCTP
link uniquely.
Unit: None
Default Value: None
SCTPLNKN BSC6900 MOD UCCP(Mandatory)
ADD UCCP(Mandatory)
link uniquely.
Unit: None
Default Value: None
SCTPLNKN BSC6900 MOD UNCP(Mandatory)
ADD UNCP(Mandatory)
link uniquely.
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-7

PATHT BSC6900 ADD IPPATH(Optional) Meaning: Type of the IP path
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_AF43, LQ_EF
Unit: None
Default Value: None
IPADDR BSC6900 ADD DEVIP(Mandatory)
RMV DEVIP(Mandatory)
Meaning: IP address of the board
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
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).
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-8

PEERIPADDR BSC6900 ADD IPPATH(Mandatory) Meaning: The peer IP address should not
be the same as the local address.
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
PEERMASK BSC6900 ADD IPPATH(Optional) Meaning: Subnet mask of the peer IP
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: 255.255.255.255
NBTRANTP BSC6900 ADD UNODEBIP(Mandatory)
MOD UNODEBIP(Mandatory)
Meaning: Transmission type of NodeB
GUI Value Range:
ATMTRANS_IP(ATMTRANS_IP),
IPTRANS_IP(IPTRANS_IP),
ATMANDIPTRANS_IP(ATMANDIPTRAN
S_IP)
Actual Value Range: ATMTRANS_IP,
IPTRANS_IP, ATMANDIPTRANS_IP
Unit: None
Default Value: None
NBIPOAMMASK BSC6900 ADD UNODEBIP(Mandatory)
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.
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
IP BSC6900 ADD
SNTPSRVINFO(Mandatory)
RMV
SNTPSRVINFO(Optional)
Meaning: IP address of the server
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-9

MAINLINK BSC6900 MOD UCCP(Mandatory) 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.
Type ), SCTP(SCTP Link Type)
Actual Value Range: SAAL, SCTP
Unit: None
Default Value: None
MAINLINK BSC6900 ADD UCCP(Optional) Meaning: Preferred type of the link used
Unit: None
Default Value: SAAL
MAINLINK BSC6900 MOD UNCP(Mandatory) Meaning: Preferred type of the link used
Unit: None
Default Value: None
MAINLINK BSC6900 ADD UNCP(Optional) Meaning: Preferred type of the link used
Unit: None
Default Value: SAAL
WCDMA RAN
IP RAN 5 Parameters

5-10

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
Unit: None
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,
LQAF41, LQAF42, LQAF43, LQEF
Actual Value Range: CBR, RT_VBR,
AF21, AF22, AF23, AF31, AF32, AF33,
LQAF41, LQAF42, LQAF43, LQEF
Unit: None
Default Value: None
VOICESECPATH BSC6900 ADD TRMMAP(Optional)
MOD TRMMAP(Optional)
Meaning: AMR voice service bearer
secondary path
GUI Value Range: CBR, RT_VBR,
AF21, AF22, AF23, AF31, AF32, AF33,
LQAF41, LQAF42, LQAF43, LQEF,
NULL
Actual Value Range: CBR, RT_VBR,
AF21, AF22, AF23, AF31, AF32, AF33,
LQAF41, LQAF42, LQAF43, LQEF,
NULL
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-11

SAALLNKT BSC6900 ADD SAALLNK(Mandatory)
MOD SAALLNK(Optional)
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
Unit: None
Default Value: None
CARRYVPI BSC6900 ADD SAALLNK(Mandatory)
Meaning: VPI value of the SAAL out
BSC6900
Unit: None
Default Value: None
CARRYVCI BSC6900 ADD SAALLNK(Mandatory)
Meaning: VCI value of the SAAL out
BSC6900
Unit: None
Default Value: None
VPI BSC6900 ADD AAL2PATH(Mandatory)
Meaning: VPI of the AAL2 path out
BSC6900
Unit: None
Default Value: None
VCI BSC6900 ADD AAL2PATH(Mandatory)
Meaning: VCI of the AAL2 path out
BSC6900
Unit: None
Default Value: None
ANI BSC6900 ADD AAL2PATH(Mandatory)
MOD AAL2PATH(Mandatory)
RMV AAL2PATH(Mandatory)
Meaning: Uniquely identifies an adjacent
node
Unit: None
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
Unit: None
Default Value: None
WCDMA RAN
IP RAN 5 Parameters

5-12

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
Unit: None
Default Value: None
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
Unit: None
Default Value: None
TXBW BSC6900 ADD IPPATH(Mandatory)
MOD IPPATH(Optional)
Meaning: Transmit bandwidth of IP path
Unit: kbit/s
Default Value: None
RXBW BSC6900 ADD IPPATH(Mandatory)
MOD IPPATH(Optional)
Meaning: Receive bandwidth of IP path
Unit: kbit/s
Default Value: None
PATHID BSC6900 ADD AAL2PATH(Mandatory)
MOD 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.
Unit: None
Default Value: None
PEERPORT NodeB ADD SCTPLNK(Mandatory) Meaning: Local SCTP port is one of the
parameters between NodeB and RNC.
Unit: None
Default Value: -
SECLOCIP NodeB ADD SCTPLNK(Optional) Meaning: Second local IP address
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
WCDMA RAN
IP RAN 5 Parameters

5-13

SECPEERIP NodeB ADD SCTPLNK(Optional) Meaning: Second peer IP address
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
LOCPORT NodeB ADD SCTPLNK(Mandatory) Meaning: Local SCTP port is one of the
parameters between NodeB and RNC.
Unit: None
Default Value: -
BEAR NodeB ADD IUBCP(Optional) Meaning: It indicates whether the
transport mode is IP or ATM.
GUI Value Range: ATM, IPV4
Actual Value Range: ATM, IPV4
Unit: None
Default Value: ATM
NODEBIP NodeB ADD IPPATH(Mandatory) Meaning: It indicates NodeB IP address
of IP port, which can be classified into the
following types:
When the NodeB IP address is
configured by link layer, this configured
address can be used;
When the DEVIP is configured, the
DEVIP address can be used;
When the NodeB IP address is obtained
by link layer negotiation, the negotiated
address that can be configured as 0.0.0.0
can not be used.
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
ES NodeB SET
DHCPRELAYSWITCH(Optiona
l)
Meaning: DHCP relay enable switch
GUI Value Range: DISABLE, ENABLE
Actual Value Range: DISABLE, ENABLE
Unit: None
Default Value: ENABLE
NT NodeB ADD AAL2PATH(Mandatory)
Meaning: Node type
GUI Value Range: LOCAL(End Node),
HUB(Switching Node),
ADJNODE(Adjacent Node)
Actual Value Range: LOCAL, HUB,
ADJNODE
Unit: None
Default Value: -
WCDMA RAN
IP RAN 5 Parameters

5-14

ARPPROXY NodeB SET ETHPORT(Optional) Meaning: ARP proxy
GUI Value Range: DISABLE, ENABLE
Actual Value Range: DISABLE, ENABLE
Unit: None
Default Value: -
LOCIP NodeB ADD SCTPLNK(Mandatory) Meaning: Local IP address
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
FLAG NodeB ADD IUBCP(Optional)
RMV IUBCP(Optional)
Meaning: A flag indicating whether the
transmission channel is the master or the
slave one
GUI Value Range: MASTER(Master
Channel), SLAVE(Slave Channel)
Actual Value Range: MASTER, SLAVE
Unit: None
Default Value: MASTER
PATHID NodeB ADD AAL2PATH(Mandatory)
Meaning: AAL2 path ID
Unit: None
Default Value: -
PT NodeB ADD IPPATH(Optional) Meaning: Port type
GUI Value Range: PPP, MPGRP, ETH,
LOOPINT, ETHTRK
Actual Value Range: PPP, MPGRP,
ETH, LOOPINT, ETHTRK
Unit: None
Default Value: -
DSCP NodeB ADD IPPATH(Mandatory) Meaning: Differentiated services code
point.
Unit: None
Default Value: -
PEERIP NodeB ADD OMCH(Mandatory)
MOD OMCH(Optional)
Meaning: Peer IP address
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
WCDMA RAN
IP RAN 5 Parameters

5-15

PEERIP NodeB ADD SCTPLNK(Mandatory) Meaning: Peer IP address
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
PEERMASK NodeB ADD OMCH(Mandatory)
MOD OMCH(Optional)
Meaning: Peer IP mask
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
IP NodeB ADD OMCH(Mandatory)
MOD OMCH(Optional)
Meaning: Local IP cannot equal to peer
IP.
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
MASK NodeB ADD OMCH(Mandatory)
MOD OMCH(Optional)
Meaning: A valid IP address must satisfy
all the following conditions:
IP & ~mask cannot be 0.
IP & mask cannot be 0.
IP & mask + ~mask cannot be 0xffffffff.
IP & ~mask + mask cannot be 0xffffffff.
Note: "~mask" indicates the complement
on mask.
And Mask can not be 255.255.255.254.
The mask in binary allows no "0" before
"1" or "1" after "0". The mask can not be.
32 bits,when BEAR is IP.
GUI Value Range: -
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: -
VPI NodeB ADD SAALLNK(Mandatory) Meaning:
Value range: 0~255;
Unit: None
Default Value: -
VCI NodeB ADD SAALLNK(Mandatory) Meaning:
Value range: 32~511;
Unit: None
Default Value: -
WCDMA RAN
IP RAN 5 Parameters

5-16

MODE NodeB
SET E1T1BEAR(Optional)
Meaning: Bearing mode

GUI Value Range: ATM, IPV4
Actual Value Range: ATM, IPV4
Unit: None
Default Value: ATM

The Default Value column is valid only for optional parameters and the "-" symbol indicates that there is no default value.
WCDMA RAN
IP RAN 6 Counters

6-1

6 Counters
For details, see the BSC6900 UMTS Performance Counter Reference and the NodeB Performance
Counter Reference.
WCDMA RAN
IP RAN 7 Glossary

7-1

7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
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 Description
[8] NodeB Initial Configuration Guide
[9] NodeB Product Description
[10] NodeB Self-discovery

Ip Ran

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ip Ran

Uploaded by

Copyright:

Available Formats

IP RAN

You might also like