You are on page 1of 51

WCDMA RAN

IP RAN
Feature Parameter Description Copyright © Huawei Technologies Co., Ltd. 2010. 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 the warranty of any kind, express or implied.

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

WCDMA RAN IP RAN

Contents

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.4.5 Other Data Configuration.................................................................................................... 3-13 3.5 Iu-PS over IP ............................................................................................................................... 3-13 3.5.1 Protocol Stack..................................................................................................................... 3-13 3.5.2 Transport Mode Configuration............................................................................................ 3-14 3.5.3 SCTP Link Configuration .................................................................................................... 3-14 3.5.4 IP Path Configuration ......................................................................................................... 3-14 3.5.5 Other Data Configuration.................................................................................................... 3-14 3.6 Iur over IP.................................................................................................................................... 3-14 3.6.1 Protocol Stack..................................................................................................................... 3-14 3.6.2 Transport Mode Configuration............................................................................................ 3-15 3.6.3 SCTP Link Configuration .................................................................................................... 3-15 3.6.4 IP Path Configuration ......................................................................................................... 3-15 3.6.5 Other Data Configuration.................................................................................................... 3-16 Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd iii

Contents

WCDMA RAN IP RAN

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

iv

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2010-03-30)

WCDMA RAN IP RAN

1 Introduction

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 (2010-03-30) of RAN12.0, this issue optimizes the description.

Draft (2009-12-05)
This is the draft of the document for RAN12.0.

Issue 01 (2010-03-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

1-1

FG2c and The following parameters change: GOUc. Parameter Change The added parameter is as follows: MUXTYPE The deleted parameter is as follows: FPMUXSWITCH Two new IP interfaces boards.1 Introduction WCDMA RAN IP RAN Compared with issue 02 (2009-06-30) of RAN11. The command ADD IPMUX is added. the IP RAN parameter description is split into two documents. this issue incorporates the changes described in the following table. Change Type Feature change Change Description The OM IP address of the BTS3900. BTS3900A. and some parameters are moved from ADD IPPATH to ADD IPMUX. None. Some technical aspects of IP RAN are described in a new document named IP Transport Architecture Description.. Editorial change In this release. The command ADD CNNODE is renamed ADD UCNNODE. Value range of MODE changes 1-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. GATEWAY in STR IPCHK is renamed PEERIP.0. and DBS3900 can be the same as either the control plane IP address or the user plane IP address. are added. Ltd Issue 01 (2010-03-30) .

Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd 2-1 .WCDMA RAN IP RAN 2 Overview of IP RAN 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. IP RAN brings the following advantages: IP transport features high bandwidth and low cost. IP transport enables operators to utilize the existing IP-based networks flexibly. Iur. thus reducing the costs of network deployment and maintenance. With the application of the multi-mode base station controller. and Iu interfaces. IP transport keeps pace with the evolution towards all-IP. thus easily meeting the requirements of data services for high bandwidth and enabling operators to introduce new services as required.. IP-based common transport can be implemented on the GSM and UMTS interfaces. thus reducing the network evolution cost.

.

2.WCDMA RAN IP RAN Error! Style not defined. This section describes the protocol stacks of the preceding interfaces and the relevant parameter settings.2 Iub over IP The Iub interface connects the RNC and the NodeB. the Iub interface supports two transport modes: Iub over IP and Iub over IP&ATM. 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 Protocol Stacks 3.Error! Style not defined.1 Protocol Stack Figure 3-1 shows the Iub over IP protocol stack. 3. 3. Figure 3-1 Iub over IP protocol stack Control plane Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd 3-1 .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.. When the Iub over IP protocol stack is used.

When Iub over IP is used. 3-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.2. When Iub over IP is used. NBAP is responsible for the transport of control plane messages between the NodeB and the controlling RNC (CRNC) at the radio network layer. 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.2 Transport Mode Configuration To enable Iub over IP. User plane The application protocols for the user plane of the Iub interface are a series of frame protocols: DCH FP.3 SCTP Link Configuration The Iub control plane has two types of control ports: NodeB control port (NCP) and communication control port (CCP). PCH FP. 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. peer SCTP port No. When Iub over IP is used..2.Error! Style not defined. The NCP and CCP carry different types of Iub interface signaling messages. Table 3-1 Description of the NCP and CCP Port NCP CCP Description Carries common process messages of NBAP over the Iub interface Carries dedicated process messages of NBAP over the Iub interface Quantity One Iub interface has only one NCP. An SCTP link is jointly specified by the local SCTP port No. HS-DSCH FP. the IPTRANSAPARTIND parameter must be set to SUPPORT or NOT_SUPPORT to specify whether to support hybrid IP transport. If the TnlBearerType parameter is set to HYBRID_IP_TRANS. 3.Error! Style not defined. The number of CCPs depends on the network planning. local IP address. These protocols are responsible for the transport of data and control frames between the NodeB and the CRNC. The TRANST parameter is set to IP. and E-DCH FP. IP over E1/T1 over SDH. RACH FP. and IP over Ethernet. the NCP and CCP are carried on different SCTP links. NBAP is carried on the Stream Control Transmission Protocol (SCTP) link. These frames contain Uu interface user data and user-related control data. IP over SDH. and peer IP address. FACH FP. set the following parameters on the RNC side: The TnlBearerType parameter is set to IP_TRANS or HYBRID_IP_TRANS. the user plane data on the Iub interface is carried on the IP path. WCDMA RAN IP RAN The application protocol for the control plane of the Iub interface is the NodeB Application Part (NBAP).. 3. The data link layer of Iub over IP supports the following transport modes: IP over E1/T1. Ltd Issue 01 (2010-03-30) . One Iub interface may have multiple CCPs.. The NODET parameter is set to IUB. the MODE parameter on the RNC side must be set to SERVER. as listed in Table 3-1.

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.WCDMA RAN IP RAN Error! Style not defined. Ltd 3-3 . 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. this parameter and PEERIP1 determine the main path of the SCTP link. SCTPLNKN: This parameter specifies the number of the SCTP link that carries the NCP or CCP. this parameter must be set to SCTP. this parameter specifies the IP address of the SCTP link on the RNC side. The RNC uses the NBAP service listening port to listen to the requests from the NodeB for establishing the SCTP link. the other must also be set. generally the RNC functions as the client and the CN node functions as the server.. or SAAL-SCTP. 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. When SCTP multi-homing is used. NBAPSRVPN: This parameter specifies the local port number when the RNC functions as the server.Error! Style not defined. This parameter should be set to the same value as the LOCIP1 parameter on the RNC side. CROSSIPFLAG: This parameter specifies whether the cross paths of the SCTP link is available. DSCP: This parameter specifies the priority of a signaling message. PEERIP: When SCTP multi-homing is not used. RNC) IP address of the SCTP link. PEERPN: This parameter specifies the peer port number of the SCTP link. LOCIP1: When SCTP multi-homing is not used. this parameter and PEERIP determine the main path of the SCTP link. this parameter specifies the peer (that is. For the SCTP link on the Iu interface. this parameter and LOCIP determine the main path of the SCTP link. PEERIP1: When SCTP multi-homing is not used. PEERIP2: This parameter specifies the second peer IP address of the SCTP link. NodeB) IP address of the SCTP link. When SCTP multi-homing is used. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. When Iub over IP is used. 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. This parameter should be set to the same value as the PEERIP1 parameter on the RNC side. SCTP. When SCTP multi-homing is used. this parameter specifies the peer (that is. For the SCTP link on the Iub interface. SECLOCIP: This parameter specifies the second IP address of the SCTP link on the NodeB side. this parameter specifies the IP address of the SCTP link on the NodeB side. If one of the LOCIP2 and PEERIP2 parameters is set. whereas the two IP addresses on the NodeB side must belong to the same interface board. 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 is set only when SCTP multi-homing is used. this parameter and LOCIP1 determine the main path of the SCTP link. the RNC functions as the server and thus this parameter need not be set. the two IP addresses of one SCTP link on the RNC side may belong to the same interface board or different interface boards. It is recommended that the default value be used. In the case of SCTP multi-homing. The default value is 48. 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. When SCTP multi-homing is used. which indicates that the NCP or CCP is carried on the SCTP link.

HSPA RT. as shown in Figure 3-2. For example.Error! Style not defined. Figure 3-2 IP paths on the Iub interface In this case. R99 NRT. WCDMA RAN IP RAN SECPEERIP: This parameter specifies the second peer (that is. the user plane data on the Iub interface is carried on the IP path. Different priorities are assigned to IP paths for the provisioning of differentiated services. The intermediate transport network also provides differentiated services according to the DSCP value in the IP header. the highpriority RT service data is preferentially transmitted and the low-priority NRT service data is buffered. In the case of transmission congestion. This parameter should be set to the same value as the PEERPN parameter on the RNC side. RNC) IP address of the SCTP link. four IP paths are configured between the RNC and the NodeB to share the physical transmission bandwidth on the Iub interface. When the NCP and CCP are added.Error! Style not defined. the BEAR parameter should be set to IPV4. At least one IP path is required between one RNC and one NodeB. The mapping between PHBs and DSCPs is set through the SET PHBMAP command. the low-priority NRT service data is discarded. the interface boards of the RNC and NodeB provide differentiated scheduling according to the value of differentiated service code point (DSCP). see the Transmission Resource Management Feature Parameter Description. 3.. These IP paths are specified to carry the R99 RT.2. This parameter should be set to the same value as the LOCIP2 parameter on the RNC side. This parameter should be set to the same value as the NBAPSRVPN parameter on the RNC side. This parameter is set only when SCTP multi-homing is used. Ltd Issue 01 (2010-03-30) .4 IP Path Configuration When Iub over IP is used. It is recommended that more than one IP path be configured. which indicates that the NCP and CCP are carried on the SCTP links. IP Path Configuration on the RNC Side The parameters for establishing an IP path on the RNC side are as follows: 3-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. For details. In the case of buffer overflow. LOCPORT: This parameter specifies the local port number of the SCTP link. which is set through the ADD TRMMAP command. 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. PEERPORT: This parameter specifies the peer port number of the SCTP link.

routes need to be configured on only the M2000 and NodeB. and NodeB.2.Error! Style not defined. PEERMASK: This parameter specifies the peer subnet mask. this parameter must be set to the same value as the NODEBIP parameter on the NodeB side. This IP address is used for the user plane of the Iub interface. RNC) IP address of the IP path. Iu-CS.. If the peer IP address of the IP path is a network segment IP address. and Iu-PS) can share one IP address. Different types of services are mapped to different types of IP paths. Generally. It is used to maintain and configure the NodeB remotely. BTS3900A. In addition. 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.5 OM Channel Configuration An operation and maintenance (OM) channel exists between the M2000 and the NodeB. M2000<—>NodeB: Routes are configured between the M2000 and the NodeB but not through the RNC. the port IP address is used. see the IP Transport Architecture Description. NODEBIP: This parameter specifies the IP address of the IP path on the NodeB side. 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. The default value of this parameter is 255. routes need to be configured on the M2000. see the Transmission Resource Management Feature Parameter Description. This parameter should be set to the same value as the IPADDR parameter on the RNC side. PEERIPADDR: This parameter specifies the peer IP address of the IP path. the OM IP address of the base station can be the same as the IP address Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. For descriptions of the port IP address and device IP address. In layer 3 networking. and DBS3900 can be the same as either the control plane IP address or the user plane IP address. If the OM subnet where the M2000 is located is connected to the IP network that covers the NodeB. IPADDR: This parameter specifies the local IP address of the IP path on the RNC side. RNCIP: This parameter specifies the peer (that is. 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. Figure 3-3 shows an example of OM channel in the case of M2000<—>RNC<—>NodeB in layer 2 networking.255.WCDMA RAN IP RAN Error! Style not defined. PATHT: This parameter specifies the type of an IP path. Ltd 3-5 . For the Iub interface. the M2000 and the NodeB can be directly networked without the RNC. In this case. For details. MLPPP group. RXBW: This parameter specifies the bandwidth for admission control on an IP path in the reception direction.255. TXBW: This parameter specifies the bandwidth for admission control on an IP path in the transmission direction. The control and user planes of the RNC-related interfaces (Iub. The shared IP address must be the interface IP address. This IP address can be the port IP address or device IP address. In this case. Different types of IP paths can be configured between the RNC and the NodeB. or Ethernet port. In this case. This IP address can be the port IP address or device IP address. which indicates that the peer IP address of the IP path is a host IP address. this parameter needs to be re-set. the OM IP addresses of the BTS3900. It can be PPP link. This IP address is used for the user plane of the Iub interface. Iur. two adjacent devices communicate with each other through routers.255. 3. RNC. DSCP: This parameter specifies the DSCP value of the IP path on the NodeB side.

the IP address of the interface. If active and standby OM IP addresses are applied. and OM of the Iub interface can share one IP address. 3-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. user plane IP address. If active and standby OM IP addresses are used. The maintenance IP address must be different from the IP address of the interface.. the control plane. see the NodeB Self-discovery. the control plane IP address and the user plane IP address are the same. The 3900 series base station is configured with one WMPT board and one UTRP board. 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 two OM IP addresses can be the same as the IP addresses of the two IP interfaces on the WMPT board respectively. Note: NodeB IP addresses involve the control plane IP address. BTS3900A. 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. In this case. user plane. Both the boards have one or more IP interfaces. 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. the two OM IP addresses can be the same as the IP addresses of the two IP interfaces respectively. WCDMA RAN IP RAN of one of the interfaces. For details about the DHCP function. 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. Generally.Error! Style not defined. however. For the BTS3900. Ltd Issue 01 (2010-03-30) . Figure 3-4 OM channel in the case of M2000<—> NodeB When Iub over IP is used. and DBS3900. NBIPOAMMASK: This parameter specifies the mask of the subnet where the OM IP address of the NodeB is located in IP transport. the OM IP address of the base station can be the same as the IP address of one IP interface on the WMPT board. The OM IP address can be the port IP address or device IP address. that is. IP routes need to be configured for the OM channel according to the actual networking conditions.Error! Style not defined. the OM IP address cannot be the same as the IP addresses of any IP interface on the UTRP board. and NodeB maintenance IP address.

IP routes need to be configured for the OM channel according to the actual networking conditions. data link layer data.3 Iub over IP&ATM The Iub interface connects the RNC and the NodeB. the RNC supports the following transport modes at the data link layer: Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Figure 3-5 Iub over IP&ATM protocol stack When Iub over IP&ATM is used. PEERIP: This parameter specifies the peer IP address. For details about these configurations. see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide. and activation factor table. the IPoA mode is used.WCDMA RAN IP RAN Error! Style not defined. 3. the Iub over IP&ATM protocol stack is used (WRFD-050404 ATM/IP Dual Stack Node B).1 Protocol Stack Figure 3-5 shows the Iub over IP&ATM protocol stack. Ltd 3-7 . TRM mapping table.. BEAR: This parameter specifies the bearer type (ATM or IPV4).2. 3.Error! Style not defined. MASK: This parameter specifies the local OM subnet mask. PEERMASK: This parameter specifies the peer subnet mask. If this parameter is set to IPV4.3. the following data should also be configured: physical layer data. When the Iub interface adopts hybrid ATM/IP transport. 3. the IP mode is used. If this parameter is set to ATM.6 Other Data Configuration To enable Iub over IP.

NBAP is responsible for the transport of control plane messages between the NodeB and the CRNC at the radio network layer. and ATM over unchannelized STM-1/OC3c When Iub over IP&ATM is used. WCDMA RAN IP RAN IP: IP over E1/T1. and IP over GE ATM: ATM over E1/T1 and ATM over unchannelized STM-1/OC-3c When Iub over IP&ATM is used. 3-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. If this parameter is set to SAAL or SCTP. the control plane can be configured as the active/standby mode (SAAL and SCTP) to improve the transport reliability. If this parameter is set to SAAL-SCTP. the data is automatically transferred to the standby link for transmission. Ltd Issue 01 (2010-03-30) . The NCP configuration principle is the same as the CCP configuration principle. the FLAG parameter specifies the active link. On the NodeB side. 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. the BTS3900. and IP over unchannelized STM-1/OC-3c ATM: ATM over E1/T1. In active/standby mode. After the active link becomes available.. IP over FE. On the RNC side. one SAAL link and one SCTP link are configured for each NCP and CCP. 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. and ATM over unchannelized STM-1/OC3c Control Plane The application protocol for the control plane of the Iub interface is the NBAP.Error! Style not defined. IP over GE. the CARRYLNKT parameter should be set on the RNC side to specify the bearer mode in the control plane. When Iub over IP&ATM is used. the MAINLINK parameter specifies the active link. the active/standby mode (SAAL and SCTP) is used. If the active link is unavailable. The NCP and CCP data is preferentially transmitted on the active link. IP over FE. ATM over channelized STM-1/OC-3. 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. the NCP and CCP are carried on the SAAL link or the SCTP link. and DBS3900 support the following transport modes at the data link layer: IP: IP over E1/T1.Error! Style not defined. 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. BTS3900A. IP over channelized STM-1/OC-3.

the main path and standby path that carry each type of service can be specified.. 3. These protocols are responsible for the transport of data and control frames between the NodeB and the CRNC. set the following parameters on the RNC side: The TnlBearerType parameter is set to ATMANDIP_TRANS. When the RNC performs admission control on a new call.WCDMA RAN IP RAN Error! Style not defined. User Plane The radio network user plane of the Iub interface uses a series of frame protocols: DCH FP. the user plane can be configured as the active/standby mode (AAL2 path and IP path) to improve the transport reliability. it preferentially uses the main path. the services carried on this path are disrupted. HS-DSCH FP. New service requests are established on the available path according to the TRM mapping table. Ltd 3-9 . For details. If an AAL2 path or an IP path is unavailable. several IP paths and AAL2 paths can be configured simultaneously. These frames contain Uu interface user data and user-related control data. and VOICESECPATH parameters should be set for AMR voice services. If the admission of the new call fails on the main path. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the VOICEPRIPATH. PCH FP. The type of every path should be specified. Figure 3-7 Active/standby mode in the user plane in the case of Iub over IP&ATM On the Iub interface.Error! Style not defined. When Iub over IP&ATM is used. The RNC provides the default mapping relations for transmission resources. the RNC tries the standby path. 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.3. The TRANST parameter is set to ATM_IP. RACH FP. Figure 3-7 shows the active/standby mode in the user plane in the case of Iub over IP&ATM.2 Trasnport Mode Configuration To enable Iub over IP&ATM. and E-DCH FP. see the Transmission Resource Management Feature Parameter Description. For example. By configuring the TRM mapping table through the execution of the ADD TRMMAP command. FACH FP. The NODET parameter is set to IUB.

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.AAL2..3 "SCTP Link. The number of CCPs depends on the network planning. If a call connection is required on the AAL2 path between the RNC and the NodeB. 3. the ALCAP must be carried by the SAAL link alone instead of by both the SAAL link and the SCTP link.3. CARRYVCI: This parameter specifies the VCI value of an SAAL link.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. CCP. Ltd Issue 01 (2010-03-30) . The signaling messages are classified into NCP. as described in Table 3-2.2. The UNI link is used for the Iub interface and the NNI link is used for the Iur and Iu interfaces. ALCAP The ALCAP is also called Q. and ALCAP. see section 3. The parameters for establishing an SAAL link on the RNC side are as follows: SAALLNKT: This parameter specifies the type of an SAAL link.Error! Style not defined. VCI: This parameter specifies the VCI value of an SAAL link. Table 3-2 Signaling messages carried on an SAAL link of UNI type Type NCP CCP Description An NCP carries common process messages of NBAP over the Iub interface. the AAL2 path ID and CID information is exchanged through the ALCAP.2." 3-10 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. A CCP carries dedicated process messages of NBAP over the Iub interface. The Iub interface may have multiple CCPs. For details.3. Therefore. the ALCAP is not required for signaling exchange. For details. CARRYVPI: This parameter specifies the VPI 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. The Iub interface has only one NCP. WCDMA RAN IP RAN 3." SAAL Link The SAAL link of User Network Interface (UNI) type is used to carry signaling messages on the Iub interface. see section 3.Error! Style not defined. The PVC identifier (VPI/VCI) of the SAAL link and other PVC attributes are negotiated between the RNC and the NodeB. SAAL links are classified into the UNI link and the NNI link.4 "IP Path. If the ATM network is unavailable and all the services are established on the IP path.

The settings of this parameter are negotiated between the RNC and the NodeB.Error! Style not defined. 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. and activation factor table.3. and SGSNs have an adjacent node ID. For details.. When the OM channel is based on IP and ATM. ATM. 3. LOCAL. 3. see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide. or ADJNODE.4. 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. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.5 "OM Channel.WCDMA RAN IP RAN Error! Style not defined. the OM channel can be based on IP. PATHID: This parameter specifies the ID of the AAL2 path that connects the RNC and an adjacent node. see the BSC6900 UMTS Initial Configuration Guide and the NodeB Initial Configuration Guide.2. the following data should also be configured: physical layer data. MGWs.1 Protocol Stack Figure 3-8 shows the Iu-CS over IP protocol stack.3. LOCAL indicates a leaf NodeB. It is used to receive the RNC messages required for the lower-level NodeBs to establish a link. This parameter should be set to the same value as the PATHID parameter on the RNC side. TRM mapping table." The parameter settings of the ATM-based OM channel for Iub over IP&ATM are the same as those for Iub over ATM. It is used to forward the lower-level NodeB link establishment messages to this NodeB. The AAL2 path of ADJNODE type is located between this NodeB and the lower-level NodeB.6 Other Data Configuration To enable Iur over IP&ATM. 3.4 Iu-CS over IP The Iu-CS interface connects the RNC and the MSC or MSC server. 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. Ltd 3-11 . HUB and ADJNODE indicate a Hub NodeB. For details. The PVC identifier (VPI/VCI) and other PVC attributes are negotiated between the RNC and the NodeB. The AAL2 path of HUB type is located between this NodeB and the upper-level equipment. 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. The AAL2 path is used to establish an AAL2 connection of this NodeB.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. see section 3. 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). PATHID: This parameter specifies the ID of the AAL2 path that connects the RNC and an adjacent node. When the Iu-CS over IP protocol stack is used. or both. For details about these configurations. It can be set to HUB. data link layer data. 3.

3. WCDMA RAN IP RAN Figure 3-8 Iu-CS over IP protocol stack Control plane The application protocol for the control plane of the Iu-CS interface is the Radio Access Network Application Part (RANAP). The TnlBearerType parameter is set to IP_TRANS.2.Error! Style not defined.4. see section 3..3 "SCTP Link.Error! Style not defined. The UE communicates with a circuit switched (CS) or packet switched (PS) node on the core network (CN) through RANAP signaling messages. 3. The TRANST parameter is set to IP.4. When Iu-CS over IP is used." 3-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Ltd Issue 01 (2010-03-30) . Iu-UP is responsible for the transport of the user data carried on the radio access bearer (RAB). the transport mode of Iu-CS over IP should be configured before other data. 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. The NODET parameter is set to IUCS. When Iu-CS over IP is used. The associated parameters need to be set as follows: The CNDomainId parameter is set to CS_DOMAIN. For details.3 SCTP Link Configuration The parameter settings of the SCTP link on the RNC side for Iu-CS over IP are similar to those of Iub over IP.2 Transport Mode Configuration On the RNC side. Iu-UP is carried on the IP path.

Ltd 3-13 . RANAP is carried on the SCTP link. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 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). 3. 3.4 IP Path Configuration The parameter settings of the IP path on the RNC side for Iu-CS over IP are similar to those of Iub over IP. data link layer data. When Iu-PS over IP is used. The UE communicates with a CS or PS node on the CN through RANAP signaling messages. User plane The application protocol for the user plane of the Iu-PS interface is the Iu-UP. TRM mapping table. When the Iu-PS over IP protocol stack is used. When Iu-PS over IP is used. see section 3." 3.4.WCDMA RAN IP RAN Error! Style not defined. Iu-UP is carried on the IP path.2.. For details about these configurations.4. For details. activation factor table. Iu-UP is responsible for the transport of the user data carried on the RAB. 3. Figure 3-9 Iu-PS over IP protocol stack Control plane The application protocol for the control plane of the Iu-PS interface is the RANAP. and M3UA data. see the BSC6900 UMTS Initial Configuration Guide.Error! Style not defined.5 Other Data Configuration To enable Iu-CS over IP.5.1 Protocol Stack Figure 3-9 shows the Iu-PS over IP protocol stack. the following data should also be configured: physical layer data.5 Iu-PS over IP The Iu-PS interface connects the RNC and the SGSN.4 "IP Path.

2. the transport mode of Iu-PS over IP should be configured before other data.5.4 IP Path Configuration The parameter settings of the IP path on the RNC side for Iu-PS over IP are similar to those of Iub over IP.1 Protocol Stack Figure 3-10 shows the Iur over IP protocol stack. WCDMA RAN IP RAN 3. When the Iur over IP protocol stack is used." 3.5 Other Data Configuration To enable Iu-PS over IP. the data in the control and user planes of the Iur interface is transported over IP (WRFD-050410 IP Transmission Introduction on Iur Interface).2 Transport Mode Configuration On the RNC side. The associated parameters need to be set as follows: The CNDomainId parameter is set to PS_DOMAIN.. see section 3.6.Error! Style not defined. 3.3 "SCTP Link. For details. activation factor table. the following data should also be configured: physical layer data. 3. The TRANST parameter is set to IP.3 SCTP Link Configuration The parameter settings of the SCTP link on the RNC side for Iu-PS over IP are similar to those of Iub over IP. data link layer data. For details about these configurations. see section 3. see the BSC6900 UMTS Initial Configuration Guide.5. and M3UA data. Ltd Issue 01 (2010-03-30) . The TnlBearerType parameter is set to IP_TRANS. 3. The NODET parameter is set to IUPS." 3. TRM mapping table.2.5.5. For details.4 "IP Path.Error! Style not defined. 3-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.6 Iur over IP The Iur interface connects RNCs.

the transport mode of Iur over IP should be configured before other data. Ltd 3-15 . The UE communicates with the DRNC through RNSAP signaling messages. The associated parameters need to be set as follows: The IurExistInd parameter is set to TRUE. the Iur data stream is carried on the IP path. RNSAP is carried on the SCTP link.WCDMA RAN IP RAN Error! Style not defined. 3.4 IP Path Configuration The parameter settings of the IP path on the RNC side for Iur over IP are similar to those of Iub over IP.6. 3.2 Transport Mode Configuration On the RNC side. The TRANST parameter is set to IP.2.4 "IP Path. The NODET parameter is set to IUR. User plane The Iur data stream carries the data forwarded by the DRNC between the SRNC and the NodeB.6.6. see section 3.Error! Style not defined. Figure 3-10 Iur over IP protocol stack Radio network layer Control plane RNSAP User plane Iur Data Stream Transport network layer user plane Transport network layer user plane Transport network layer SCCP M3UA SCTP IP Data link layer Physical layer UDP/IP Data link layer Control plane The application protocol for the control plane of the Iur interface is the Radio Network Subsystem Application Part (RNSAP).2. The TnlBearerType parameter is set to IP_TRANS. For details." 3. When Iur over IP is used.3 SCTP Link Configuration The parameter settings of the SCTP link on the RNC side for Iur over IP are similar to those of Iub over IP. see section 3..3 "SCTP Link. For details." Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. When Iur over IP is used.

TRM mapping table. For details about these configurations. Ltd Issue 01 (2010-03-30) .Error! Style not defined. 3-16 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the following data should also be configured: physical layer data. data link layer data.Error! Style not defined. activation factor table.6. see the BSC6900 UMTS Initial Configuration Guide.5 Other Data Configuration To enable Iur over IP.. WCDMA RAN IP RAN 3. and M3UA data.

the Iub interface supports ATM transport networking. and ring topologies. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. the Iub interface can use hybrid IP transport networking to improve the transport reliability of the Iub interface. From the perspective of transport bearers. In addition. LAN switches).1 and 4. as shown in Figure 42.1 Iub over IP Networking Based on the data switching technology that is used. Layer 2 Networking Layer 2 networking is relatively simple because all the network devices are located on the same network segment. Figure 4-1 shows an example of layer 2 networking in the case of Iub over IP. and IP routes need not be configured. 4 IP RAN Networking 4. The layer 2 network distinguishes data from different NodeBs according to the VLAN ID. the RNC uses port backup.. highpriority packets are scheduled.1 Overview This section describes the IP networking on the terrestrial interfaces of RAN.WCDMA RAN IP RAN Error! Style not defined. If the network is congested. and low-priority packets are buffered or discarded. In addition. Sections 4. To improve the transport security of the Iub interface. and hybrid ATM/IP transport networking.Error! Style not defined. IP transport networking (including hybrid IP transport). data is switched by layer 2 devices (for example. IP networking can be classified into layer 2 networking and layer 3 networking. the NodeBs and the RNC are connected through a layer 2 network.2 describe Iub over IP networking (including hybrid IP transport) and Iub over IP&ATM networking respectively.2.2. Figure 4-1 Example of layer 2 networking in the case of Iub over IP As shown in Figure 4-1.2 Iub Interface Networking The Iub interface supports star.2. 4. Ltd 4-1 . the layer 2 network provides differentiated services according to the PRI field in the VLAN tag. In this case. link. 4.

4-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. Layer 3 Networking In layer 3 networking. the ARPPROXY parameter on the NodeB side must be set to ENABLE. user plane. BTS3900A. and another IP address is configured for the OM. the ARP proxy function of the FE port must be enabled. In this case. IP route configuration Routes are not required for layer 2 networking. on the NodeB side a port IP address is configured as the common IP address of the control and user planes. the control plane. and IP routes need to be configured. routers). In other words. If they are located on the same network segment.Error! Style not defined. on the RNC side a port IP address is configured as the common IP address of the control plane. and OM of a NodeB can share one IP address. The BTS3900. Figure 4-3 shows an example of layer 3 networking in the case of Iub over IP. WCDMA RAN IP RAN Figure 4-2 Example of VLAN application on the Iub interface IP address configuration To facilitate data configuration. the network devices are located on different network segments. and DBS3900 support a single IP address for a NodeB. Ltd Issue 01 (2010-03-30) . user plane.Error! Style not defined.. that is. The port IP address and the OM IP address can be located either on the same network segment or on different network segments. and OM. data is switched by layer 3 devices (for example.

A layer-2-enabled router supports the configuration of VLANs. only the route from the RNC to the network segment 10. the RNC uses active and standby GE ports to connect to the two peer GE ports on the layer 3 router. which is on the same network segment as the VLAN IF IP address of the router. and low-priority packets are buffered or discarded. and another IP address is configured for the OM. If they are located on the same network segment. The port IP address on the RNC side functions as the common IP address of the control plane. For example. routes to the NodeBs need to be configured. The active and standby GE ports on the RNC side share one IP address.0/16 is configured. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. IP route configuration On the RNC side. the ARP proxy function of the FE port must be enabled. the layer 3 network provides differentiated services according to the DSCP value in the IP header. high-priority packets are scheduled. and DBS3900 support a single IP address for a NodeB. Figure 4-3 Example of layer 3 networking in the case of Iub over IP As shown in Figure 4-3. that is. In other words. Ltd 4-3 . The configuration of routes for the routers in the intermediate network depends on the actual networking conditions. The port IP address and the OM IP address can be located either on the same network segment or on different network segments. The routes are accessible to each NodeB or to the network segment where several NodeBs are located. user plane. the RNC communicates with the two NodeBs. 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). On the NodeB side. Through this route. the ARPPROXY parameter on the NodeB side must be set to ENABLE. In addition.Error! Style not defined. and OM of a NodeB can share one IP address.0. 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).WCDMA RAN IP RAN Error! Style not defined. Routes to the RNC should be configured for each NodeB.. One VLAN has several Ethernet ports and can be configured with a layer 3 IP address (VLAN IF IP) for the interworking between VLANs. and OM. the control plane. The BTS3900. the RNC and the NodeBs are connected through a layer 3 network. To improve the transport security of the Iub interface. a port IP address is configured as the common IP address of the control and user planes. If the network is congested.10. as shown in Figure 4-3. user plane. Figure 4-4 shows an example of hybrid IP transport. BTS3900A.

The ATM network provides a high QoS. they can be connected to the external data device through the same port. WCDMA RAN IP RAN Figure 4-4 Example of hybrid IP transport As shown in Figure 4-4. but it makes network management complicated. 4. CS services.2 Iub over IP&ATM Networking With the development of data services and the introduction of High Speed Packet Access (HSPA).Error! Style not defined. streaming services. Figure 4-5 shows an example of Iub over IP&ATM networking. and signaling. and PS conversational and streaming services. Figure 4-5 Example of Iub over IP&ATM networking As shown in Figure 4-5. Radio Resource Control (RRC) signaling. PDH or SDH network): carries control plane data.2. High-QoS network (TDM network.Error! Style not defined. The IP network does not require high transmission costs. Low-QoS network (data network. Alternatively. and then the external data device distributes the services to different networks based on the settings of the DSCP value and VLAN. 4-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. services with different QoS requirements are processed by different networks. In this case. for example. for example. Hybrid IP transport enables flexible processing of the services with different QoS requirements.. Ethernet): carries low-QoS services such as PS interactive and background services. Ltd Issue 01 (2010-03-30) . In actual networking. but it requires high transmission costs. common channel data. the bandwidth requirement of the Iub interface is on the increase. High-QoS network (ATM network): carries voice services. but it provides a relatively low QoS. the IP and ATM networks can carry services with different QoS requirements respectively. Iub over IP&ATM networking is introduced so that services with different QoS requirements can be processed in different types of networks. the RNC and the NodeB can be connected to two networks through two ports respectively.

In Iub over IP&ATM networking.Error! Style not defined. both the RNC and the NodeB should be configured with ATM interface boards and IP interface boards. Ltd 4-5 . IP network and MPLS VPN Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. 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.. for example. is complex and expensive because both the ATM and IP networks need to be maintained. such as PS Best Effort (BE) services. VPLS network. Low-QoS network (IP network): carries services with low-QoS requirements. metro Ethernet. however. The network maintenance.3 Iu/Iur Interface Networking Figure 4-6 shows an example of Iu/Iur over IP networking.WCDMA RAN IP RAN Error! Style not defined. 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. In actual networking. and MSTP network Layer 3 network. 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. 4.

.

Error! Style not defined. ATMANDIP_TRANS(ATM and IP transmission). IP_TRANS(IP transmission). GUI Value Range: ATM_TRANS. GUI Value Range: ATM_TRANS(ATM circuit transmission). IP_TRANS Unit: None Default Value: None Meaning: Transport type of the Iub interface GUI Value Range: ATM_TRANS(ATM circuit transmission). IP_TRANS Actual Value Range: ATM_TRANS.WCDMA RAN IP RAN Error! Style not defined. Ltd 5-1 . ATMANDIP_TRANS. HYBRID_IP_TRANS(Hybrid IP transmission) Actual Value Range: ATM_TRANS. NOT_SUPPORT(Not support) Actual Value Range: SUPPORT. GUI Value Range: SUPPORT(Support). ATMANDIP_TRANS(ATM and IP transmission).. 5 Parameters Table 5-1 Parameter description Parameter ID TnlBearerType NE BSC6900 MML ADD UCNNODE(Optional) MOD UCNNODE(Optional) Description Meaning: The transfers bearer type of Iu interface. IP_TRANS(IP transmission). ATMANDIP_TRANS. IP_TRANS. NOT_SUPPORT Unit: None Default Value: None TnlBearerType BSC6900 ADD UNODEB(Optional) TnlBearerType BSC6900 MOD UNODEB(Optional) IPTRANSAPART BSC6900 IND ADD UNODEB(Mandatory) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. IP_TRANS. HYBRID_IP_TRANS Unit: None Default Value: ATM circuit transmission Meaning: Indicate the transmission type be used by Iub interface. HYBRID_IP_TRANS(Hybrid IP transmission) Actual Value Range: ATM_TRANS. HYBRID_IP_TRANS Unit: None Default Value: ATM_TRANS Meaning: Indicating whether the Iub interface supports IP hybrid transport.

HYBRID_IP(HYBRID IP) Actual Value Range: IP. IP(IP). WCDMA RAN IP RAN Parameter ID NE MML MOD UNODEB(Optional) Description Meaning: IP transmission apart indication of Iub interface. NNI_AAL2SWITCH Unit: None Default Value: None Meaning: Transport type GUI Value Range: ATM(ATM). IUR(Iur Interface). IP.0. IUCS. IUCS(Iu-CS Interface). IUPS. GUI Value Range: None Actual Value Range: 0. NNI_AAL2SWITCH(the adjacent node of ATM switch on Iur or Iu-CS interface) Actual Value Range: IUB. NOT_SUPPORT(Not support) Actual Value Range: SUPPORT. Ltd Issue 01 (2010-03-30) . it is invalid. IUR.0~255. UNI_AAL2SWITCH(the adjacent node of the ATM switch on the Iub interface). HYBRID_IP Unit: None Default Value: None Meaning: Transport type of the adjacent node to which the path belongs GUI Value Range: IP(IP). This IP address must be first configured on the corresponding interface board. IUPS(Iu-PS Interface).255.Error! Style not defined. GUI Value Range: SUPPORT(Support).0. ATM_IP(ATM and IP).. HYBRID_IP(HYBRID IP) Actual Value Range: ATM. When it is set to 0.255 Unit: None Default Value: None IPTRANSAPART BSC6900 IND NODET BSC6900 ADD ADJNODE(Mandatory) MOD ADJNODE(Optional) TRANST BSC6900 ADD ADJNODE(Mandatory) MOD ADJNODE(Optional) TRANST BSC6900 ADD IPPATH(Mandatory) LOCIP1 BSC6900 ADD SCTPLNK(Mandatory) MOD SCTPLNK(Optional) 5-2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.255. UNI_AAL2SWITCH.Error! Style not defined. HYBRID_IP Unit: None Default Value: None Meaning: Identifies the first local IP address that communicates with the peer end. NOT_SUPPORT Unit: None Default Value: None Meaning: Type of the adjacent node GUI Value Range: IUB(Iub Interface). ATM_IP.

255. GUI Value Range: None Actual Value Range: 0.0.255. Parameter ID PEERIP1 NE BSC6900 MML ADD SCTPLNK(Mandatory) MOD SCTPLNK(Optional) Description Meaning: First destination IP address.255.255.0.0~255.Error! Style not defined. it is invalid. GUI Value Range: 0~63 Actual Value Range: 0~63 Unit: None Default Value: None LOCIP2 BSC6900 ADD SCTPLNK(Optional) MOD SCTPLNK(Optional) LOCPN BSC6900 ADD SCTPLNK(Mandatory) MOD SCTPLNK(Mandatory) NBAPSRVPN BSC6900 SET SCTPSRVPORT(Optional) PEERIP2 BSC6900 ADD SCTPLNK(Optional) MOD SCTPLNK(Optional) PEERPN BSC6900 ADD SCTPLNK(Mandatory) MOD SCTPLNK(Optional) DSCP BSC6900 SET DSCPMAP(Mandatory) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. The invalid value is 0.0~255..0~255.0. This IP address must be first configured on the corresponding interface board.255. GUI Value Range: None Actual Value Range: 0.WCDMA RAN IP RAN Error! Style not defined.255 Unit: None Default Value: None Meaning: Local SCTP port number GUI Value Range: 1024~65535 Actual Value Range: 1024~65535 Unit: None Default Value: None Meaning: Number of the NBAP service listening port GUI Value Range: 1024~65535 Actual Value Range: 1024~65535 Unit: None Default Value: 58080 Meaning: Second destination IP address.0.0.255 Unit: None Default Value: None Meaning: Identifies the second local IP address that communicates with the peer end. GUI Value Range: None Actual Value Range: 0.0.255.255 Unit: None Default Value: None Meaning: Destination SCTP port number GUI Value Range: 1024~65535 Actual Value Range: 1024~65535 Unit: None Default Value: None Meaning: Differentiated service code is used to identify the service priority of the user. Ltd 5-3 . When it is set to 0. The invalid value is 0.

The DSCP code is used to label each data packet on the network and allocate the corresponding service levels. GUI Value Range: 0~63 Actual Value Range: 0~63 Unit: None Default Value: 48 Meaning: The DSCP is a field of the IP data packet.Error! Style not defined. GUI Value Range: 0~63 Actual Value Range: 0~63 Unit: None Default Value: 48 DSCP BSC6900 ADD SCTPLNK(Optional) MOD SCTPLNK(Optional) 5-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. It is used to assign the differentiated service to the communication networks. the higher the priority is. the higher the priority is. the larger the DSCP is. It is used to assign the differentiated service to the communication networks. In the same network environment. In the same network environment. Ltd Issue 01 (2010-03-30) . WCDMA RAN IP RAN Parameter ID DSCP NE BSC6900 MML SET PHBMAP(Mandatory) Description Meaning: The DSCP is a field of the IP data packet. the larger the DSCP is.Error! Style not defined. The DSCP code is used to label each data packet on the network and allocate the corresponding service levels..

WCDMA RAN IP RAN Error! Style not defined. a maximum of four IP paths exists. Ltd 5-5 . SAAL-SCTP Unit: None Default Value: None CROSSIPFLAG BSC6900 CARRYLNKT BSC6900 ADD UCCP(Mandatory) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. SCTP(SCTP Link Type). SAALSCTP(SAAL-SCTP Link Tpye) Actual Value Range: SAAL. set Bearing link type to SCTP. AVAILABLE Unit: None Default Value: UNAVAILABLE Meaning: When the NCP/CCP is based on ATM. When the cross-path is available. SCTP. set Bearing link type to SAAL-SCTP. refer to 3GPP TS 25. AVAILABLE(AVAILABLE) Actual Value Range: UNAVAILABLE. 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. The four IP paths are the IP path between the first local IP address and the first peer IP address. Parameter ID NE MML ADD SCTPLNK(Optional) MOD SCTPLNK(Optional) Description Meaning: The field indicates whether the cross-connect path is available. a maximum of two IP paths exists. For detailed information of this parameter. set Bearing link type to SAAL. When the cross-path is unavailable. the IP path between the first local IP address and the second peer IP address. GUI Value Range: UNAVAILABLE(UNAVAILABLE). GUI Value Range: SAAL(SAAL Link Type ).430. When the NCP/CCP is based on IP.Error! Style not defined. the IP path between the second local IP address and the first peer IP address. When the NCP/CCP is based on ATM/IP. and the IP path between the second local IP address and the second peer IP address.

When the NCP/CCP is based on IP. GUI Value Range: 0~1199 Actual Value Range: 0~1199 Unit: None Default Value: None Meaning: SCTP link number of XPU board. SCTP. SAAL-SCTP Unit: None Default Value: None Meaning: SCTP link number of XPU board.. This number identifies an SCTP link uniquely. GUI Value Range: SAAL(SAAL Link Type ). For detailed information of this parameter.Error! Style not defined. refer to 3GPP TS 25. GUI Value Range: 0~1199 Actual Value Range: 0~1199 Unit: None Default Value: None SCTPLNKN BSC6900 ADD SCTPLNK(Mandatory) MOD SCTPLNK(Mandatory) RMV SCTPLNK(Mandatory) SCTPLNKN BSC6900 MOD UCCP(Mandatory) ADD UCCP(Mandatory) SCTPLNKN BSC6900 MOD UNCP(Mandatory) ADD UNCP(Mandatory) 5-6 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.430. SAALSCTP(SAAL-SCTP Link Tpye) Actual Value Range: SAAL. set Bearing link type to SAAL.Error! Style not defined. When the NCP/CCP is based on ATM/IP. set Bearing link type to SCTP. set Bearing link type to SAAL-SCTP. This number identifies an SCTP link uniquely. Ltd Issue 01 (2010-03-30) . This number identifies an SCTP link uniquely. GUI Value Range: 0~1199 Actual Value Range: 0~1199 Unit: None Default Value: None Meaning: SCTP link number of XPU board. SCTP(SCTP Link Type). WCDMA RAN IP RAN Parameter ID CARRYLNKT NE BSC6900 MML ADD UNCP(Mandatory) Description Meaning: When the NCP/CCP is based on ATM.

255 Unit: None Default Value: None IPADDR BSC6900 ADD DEVIP(Mandatory) RMV DEVIP(Mandatory) IPADDR BSC6900 ADD IPPATH(Mandatory) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. LQ_AF13. LQ_AF22(LQ_AF22). AF41. LQ_EF Unit: None Default Value: None Meaning: IP address of the board GUI Value Range: None Actual Value Range: 0.0~255. LQ_AF31(LQ_AF31). LQ_AF12(LQ_AF12).0~255. AF43. Ltd 5-7 . AF12. LQ_AF21. AF23. AF21(AF21). AF32. AF31. LQ_AF33. AF42(AF42). AF32(AF32). AF22. BE(BE). LQ_AF12. LQ_QOS(LQ_QOS).. LQ_AF31. AF21. LQ_AF43. GUI Value Range: None Actual Value Range: 0. LQ_BE(LQ_BE). LQ_AF21(LQ_AF21).255. LQ_AF33(LQ_AF33). AF11(AF11). LQ_AF11(LQ_AF11). EF(EF).WCDMA RAN IP RAN Error! Style not defined. LQ_AF43(LQ_AF43). AF22(AF22).255. AF33. AF41(AF41). LQ_QOS.Error! Style not defined.255. AF11. AF31(AF31). AF33(AF33). LQ_AF42(LQ_AF42). BE. LQ_AF42. LQ_BE. LQ_AF23(LQ_AF23). AF13. AF23(AF23). LQ_AF32(LQ_AF32).255 Unit: None Default Value: None Meaning: The local IP address must be the configured IP address (including the IP address and port address of the interface board). LQ_AF23. LQ_AF13(LQ_AF13).0.255. LQ_AF32.0. AF13(AF13). EF. LQ_EF(LQ_EF) Actual Value Range: QoS. AF12(AF12). LQ_AF41(LQ_AF41).0. LQ_AF11. LQ_AF22. Parameter ID PATHT NE BSC6900 MML ADD IPPATH(Optional) Description Meaning: Type of the IP path GUI Value Range: QoS(QoS). AF42. LQ_AF41.0. AF43(AF43).

WCDMA RAN IP RAN Parameter ID PEERIPADDR NE BSC6900 MML ADD IPPATH(Mandatory) Description Meaning: The peer IP address should not be the same as the local address.255 Unit: None Default Value: 255.255.255. ATMANDIPTRANS_IP(ATMANDIPTRAN S_IP) Actual Value Range: ATMTRANS_IP.255. IPTRANS_IP(IPTRANS_IP).0.255 Unit: None Default Value: None NBIPOAMMASK BSC6900 IP BSC6900 ADD SNTPSRVINFO(Mandatory) RMV SNTPSRVINFO(Optional) 5-8 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.Error! Style not defined.0.255.0~255.0.0. this parameter indicates the mask of the operation and maintenance console. GUI Value Range: None Actual Value Range: 0. IPTRANS_IP. ATMANDIPTRANS_IP Unit: None Default Value: None ADD UNODEBIP(Mandatory) MOD UNODEBIP(Optional) Meaning: When the operation and maintenance channel of NodeB is operating in the IP transmission mode.255.255 PEERMASK BSC6900 ADD IPPATH(Optional) NBTRANTP BSC6900 ADD UNODEBIP(Mandatory) Meaning: Transmission type of NodeB MOD UNODEBIP(Mandatory) GUI Value Range: ATMTRANS_IP(ATMTRANS_IP).0~255.0.0.255 Unit: None Default Value: None Meaning: IP address of the server GUI Value Range: None Actual Value Range: 0.255.0~255. GUI Value Range: None Actual Value Range: 0. Ltd Issue 01 (2010-03-30) .255.255.Error! Style not defined.255.0.255.255 Unit: None Default Value: None Meaning: Subnet mask of the peer IP GUI Value Range: None Actual Value Range: 0.0.0~255..

SCTP(SCTP Link Type) Actual Value Range: SAAL. refer to the 3GPP TS 25. it will be automatically carried on the other type of bearer link. For detailed description of this parameter. When the current bearer link fails. SCTP Unit: None Default Value: SAAL Meaning: Preferred type of the link used to carry a link when the bearer link type is SAAL-SCTP. For detailed description of this parameter. SCTP Unit: None Default Value: None Meaning: Preferred type of the link used to carry a link when the bearer link type is SAAL-SCTP. it will be automatically carried on the other type of bearer link. SCTP Unit: None Default Value: None Meaning: Preferred type of the link used to carry a link when the bearer link type is SAAL-SCTP. it will be automatically carried on the other type of bearer link. When the current bearer link fails. For detailed description of this parameter. For detailed description of this parameter.Error! Style not defined. GUI Value Range: SAAL(SAAL Link Type ).430. SCTP(SCTP Link Type) Actual Value Range: SAAL.430.430. GUI Value Range: SAAL(SAAL Link Type ). SCTP(SCTP Link Type) Actual Value Range: SAAL. SCTP Unit: None Default Value: SAAL MAINLINK BSC6900 ADD UCCP(Optional) MAINLINK BSC6900 MOD UNCP(Mandatory) MAINLINK BSC6900 ADD UNCP(Optional) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.430. refer to the 3GPP TS 25. it will be automatically carried on the other type of bearer link.WCDMA RAN IP RAN Error! Style not defined. SCTP(SCTP Link Type) Actual Value Range: SAAL. GUI Value Range: SAAL(SAAL Link Type ). GUI Value Range: SAAL(SAAL Link Type ). Parameter ID MAINLINK NE BSC6900 MML MOD UCCP(Mandatory) Description 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. Ltd 5-9 . refer to the 3GPP TS 25. When the current bearer link fails. refer to the 3GPP TS 25..

LQAF13.. NRT_VBR. LQAF22. AF43. AF33. WCDMA RAN IP RAN Parameter ID AAL2PATHT NE BSC6900 MML ADD AAL2PATH(Mandatory) MOD AAL2PATH(Optional) Description Meaning: Service type of carried over the PATH. LQAF32. LQAF33. AF11. AF12. UBR. UBR.Error! Style not defined. AF12. LQAF42. NULL Unit: None Default Value: None VOICEPRIPATH BSC6900 ADD TRMMAP(Optional) MOD TRMMAP(Optional) VOICESECPATH BSC6900 ADD TRMMAP(Optional) MOD TRMMAP(Optional) 5-10 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. AF21. LQAF31. LQAF21. BE. AF23. AF23. LQAF12.Error! Style not defined. LQAF23. AF13. AF11. NRT_VBR. AF32. AF21. LQAF32. LQAF41. RT_VBR. AF21. AF41. LQAF42. AF42. LQAF11. LQAF22. AF43. AF33. BE. AF31. SHARE(SHARE) Actual Value Range: R99. LQAF23. LQBE. LQAF12. AF11. AF32. HSPA(HSPA). EF. LQAF12. AF13. AF12. EF. LQAF43. AF43. LQAF31. AF32. LQEF. AF31. LQAF31. LQAF21. LQAF41. AF33. LQBE. only the R99 service can be carried. AF41. LQAF13. SHARE Unit: None Default Value: None Meaning: AMR voice service bearer primary path GUI Value Range: CBR. AF12. LQEF. LQAF13. LQAF21. AF22. AF23. AF13. Ltd Issue 01 (2010-03-30) . UBR. LQEF Actual Value Range: CBR. LQAF21. For HSPA. For SHARE. AF42. LQAF23. AF42. LQAF32. RT_VBR. AF11. LQAF32. LQAF43. LQAF41. HSPA. BE. AF32. AF23. AF22. AF33. AF22. AF41. AF22. only the HSPA service can be carried. LQAF41. LQAF23. NRT_VBR. LQAF11. AF13. AF41. EF. LQAF31. RT_VBR. LQBE. LQEF Unit: None Default Value: None Meaning: AMR voice service bearer secondary path GUI Value Range: CBR. LQAF43. BE. R99 and HSPA services can be carried at the same time. AF31. LQAF33. LQBE. AF42. For R99. NULL Actual Value Range: CBR. AF21. LQAF22. NRT_VBR. GUI Value Range: R99(R99). LQAF43. LQAF12. LQAF42. RT_VBR. LQAF42. LQAF33. LQAF13. LQAF11. AF31. LQAF22. LQAF33. LQAF11. AF43. UBR. EF.

PS_DOMAIN Actual Value Range: CS_DOMAIN. PS_DOMAIN Unit: None Default Value: None CNDomainId BSC6900 Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.. MOD UCNNODE(Mandatory) GUI Value Range: CS_DOMAIN. Ltd 5-11 .Error! Style not defined. Parameter ID SAALLNKT NE BSC6900 MML ADD SAALLNK(Mandatory) MOD SAALLNK(Optional) Description Meaning: Interface type of the SAAL link. NNI(NNI) Actual Value Range: UNI. GUI Value Range: UNI(UNI). NNI Unit: None Default Value: None Meaning: VPI value of the SAAL out BSC6900 GUI Value Range: 0~4095 Actual Value Range: 0~4095 Unit: None Default Value: None Meaning: VCI value of the SAAL out BSC6900 GUI Value Range: 32~65535 Actual Value Range: 32~65535 Unit: None Default Value: None Meaning: VPI of the AAL2 path out BSC6900 GUI Value Range: 0~4095 Actual Value Range: 0~4095 Unit: None Default Value: None Meaning: VCI of the AAL2 path out BSC6900 GUI Value Range: 32~65535 Actual Value Range: 32~65535 Unit: None Default Value: None CARRYVPI BSC6900 ADD SAALLNK(Mandatory) MOD SAALLNK(Optional) CARRYVCI BSC6900 ADD SAALLNK(Mandatory) MOD SAALLNK(Optional) VPI BSC6900 ADD AAL2PATH(Mandatory) MOD AAL2PATH(Optional) VCI BSC6900 ADD AAL2PATH(Mandatory) MOD AAL2PATH(Optional) ANI BSC6900 ADD AAL2PATH(Mandatory) Meaning: Uniquely identifies an adjacent MOD AAL2PATH(Mandatory) node RMV AAL2PATH(Mandatory) GUI Value Range: 0~4599 Actual Value Range: 0~4599 Unit: None Default Value: None ADD UCNNODE(Mandatory) Meaning: Identifying the type of a CN.WCDMA RAN IP RAN Error! Style not defined. The interface type of the Iub interface is UNI. The interface type of the Iu and Iur interface link is NNI.

Error! Style not defined.0. GUI Value Range: SERVER(SERVER MOD).255. GUI Value Range: 1~4294967295 Actual Value Range: 1~4294967295 Unit: None Default Value: None ADD SCTPLNK(Mandatory) Meaning: Local SCTP port is one of the parameters between NodeB and RNC. The PATHID of the RMV AAL2PATH(Mandatory) same AAL2 path configured between two AAL2 nodes must be the same.255 Unit: None Default Value: 0. FALSE Actual Value Range: TRUE.0.Error! Style not defined. GUI Value Range: TRUE. Ltd Issue 01 (2010-03-30) . FALSE Unit: None Default Value: None Meaning: SCTP link work mode. GUI Value Range: 1024~65535 Actual Value Range: 1024~65535 Unit: None Default Value: Meaning: Second local IP address GUI Value Range: Actual Value Range: 0. WCDMA RAN IP RAN Parameter ID IurExistInd NE BSC6900 MML ADD UNRNC(Mandatory) MOD UNRNC(Optional) Description Meaning: Indicating whether to config neighbouring RNC's DSP index.0. 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. The value should not be equal to 0. CLIENT Unit: None Default Value: None Meaning: Transmit bandwidth of IP path GUI Value Range: 1~3000000 Actual Value Range: 1~3000000 Unit: kbit/s Default Value: None Meaning: Receive bandwidth of IP path GUI Value Range: 1~3000000 Actual Value Range: 1~3000000 Unit: kbit/s Default Value: None MODE BSC6900 ADD SCTPLNK(Mandatory) MOD SCTPLNK(Optional) TXBW BSC6900 ADD IPPATH(Mandatory) MOD IPPATH(Optional) RXBW BSC6900 ADD IPPATH(Mandatory) MOD IPPATH(Optional) PATHID BSC6900 ADD AAL2PATH(Mandatory) Meaning: ID of one AAL2 path between MOD AAL2PATH(Mandatory) two AAL2 nodes.0~255.0.255.0 PEERPORT NodeB SECLOCIP NodeB ADD SCTPLNK(Optional) 5-12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. CLIENT(CLIENT MOD) Actual Value Range: SERVER..

0. ADJNODE(Adjacent Node) Actual Value Range: LOCAL. Parameter ID SECPEERIP NE NodeB MML ADD SCTPLNK(Optional) Description Meaning: Second peer IP address GUI Value Range: Actual Value Range: 0.0. this configured address can be used.0~255. Ltd 5-13 .255. the DEVIP address can be used. GUI Value Range: Actual Value Range: 0. IPV4 Unit: None Default Value: ATM Meaning: It indicates NodeB IP address of IP port.0. ENABLE l) Actual Value Range: DISABLE.0. GUI Value Range: ATM. When the NodeB IP address is obtained by link layer negotiation. ENABLE Unit: None Default Value: ENABLE ADD AAL2PATH(Mandatory) RMV AAL2PATH(Mandatory) Meaning: Node type GUI Value Range: LOCAL(End Node). When the DEVIP is configured. the negotiated address that can be configured as 0.WCDMA RAN IP RAN Error! Style not defined. GUI Value Range: 1024~65535 Actual Value Range: 1024~65535 Unit: None Default Value: Meaning: It indicates whether the transport mode is IP or ATM.0~255. IPV4 Actual Value Range: ATM.0.255 Unit: None Default Value: 0.Error! Style not defined.0.0.255. HUB(Switching Node).0.255. ADJNODE Unit: None Default Value: - NT NodeB Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co..255 Unit: None Default Value: - LOCPORT NodeB ADD SCTPLNK(Mandatory) BEAR NodeB ADD IUBCP(Optional) NODEBIP NodeB ADD IPPATH(Mandatory) ES NodeB SET Meaning: DHCP relay enable switch DHCPRELAYSWITCH(Optiona GUI Value Range: DISABLE.0 can not be used. HUB. which can be classified into the following types: When the NodeB IP address is configured by link layer.255.0 Meaning: Local SCTP port is one of the parameters between NodeB and RNC.

WCDMA RAN IP RAN Parameter ID ARPPROXY NE NodeB MML SET ETHPORT(Optional) Description Meaning: ARP proxy GUI Value Range: DISABLE. ENABLE Actual Value Range: DISABLE.0~255.255. ETHTRK Unit: None Default Value: Meaning: Differentiated services code point. MPGRP.0~255. SLAVE(Slave Channel) Actual Value Range: MASTER. ENABLE Unit: None Default Value: Meaning: Local IP address GUI Value Range: Actual Value Range: 0.0.255. MPGRP.Error! Style not defined.255 Unit: None Default Value: Meaning: A flag indicating whether the transmission channel is the master or the slave one GUI Value Range: MASTER(Master Channel).0.0.255.Error! Style not defined. ETHTRK Actual Value Range: PPP.0. ETH. Ltd Issue 01 (2010-03-30) .. LOOPINT. ETH. GUI Value Range: 0~63 Actual Value Range: 0~63 Unit: None Default Value: Meaning: Peer IP address GUI Value Range: Actual Value Range: 0.255 Unit: None Default Value: - LOCIP NodeB ADD SCTPLNK(Mandatory) FLAG NodeB ADD IUBCP(Optional) RMV IUBCP(Optional) PATHID NodeB ADD AAL2PATH(Mandatory) RMV AAL2PATH(Mandatory) PT NodeB ADD IPPATH(Optional) DSCP NodeB ADD IPPATH(Mandatory) PEERIP NodeB ADD OMCH(Mandatory) MOD OMCH(Optional) 5-14 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. SLAVE Unit: None Default Value: MASTER Meaning: AAL2 path ID GUI Value Range: 1~4294967295 Actual Value Range: 1~4294967295 Unit: None Default Value: Meaning: Port type GUI Value Range: PPP.255. LOOPINT.

254.0~255.255 Unit: None Default Value: Meaning: Value range: 0~255..255 Unit: None Default Value: Meaning: Local IP cannot equal to peer IP.0~255.255. IP & mask cannot be 0.0~255.255.255 Unit: None Default Value: Meaning: A valid IP address must satisfy all the following conditions: IP & ~mask cannot be 0.255. Ltd 5-15 . And Mask can not be 255. GUI Value Range: Actual Value Range: 0.255. GUI Value Range: 0~255 Actual Value Range: 0~255 Unit: None Default Value: Meaning: Value range: 32~511.255 Unit: None Default Value: Meaning: Peer IP mask GUI Value Range: Actual Value Range: 0.0. GUI Value Range: 32~511 Actual Value Range: 32~511 Unit: None Default Value: - PEERMASK NodeB ADD OMCH(Mandatory) MOD OMCH(Optional) IP NodeB ADD OMCH(Mandatory) MOD OMCH(Optional) MASK NodeB ADD OMCH(Mandatory) MOD OMCH(Optional) VPI NodeB ADD SAALLNK(Mandatory) VCI NodeB ADD SAALLNK(Mandatory) Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.255.0.0.255. 32 bits. The mask in binary allows no "0" before "1" or "1" after "0".0.0.0.255.0. GUI Value Range: Actual Value Range: 0. The mask can not be. IP & ~mask + mask cannot be 0xffffffff.255.255.WCDMA RAN IP RAN Error! Style not defined. Parameter ID PEERIP NE NodeB MML ADD SCTPLNK(Mandatory) Description Meaning: Peer IP address GUI Value Range: Actual Value Range: 0.255.0~255.when BEAR is IP.Error! Style not defined. IP & mask + ~mask cannot be 0xffffffff. Note: "~mask" indicates the complement on mask.0.

Error! Style not defined. 5-16 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. IPV4 Actual Value Range: ATM.. Ltd Issue 01 (2010-03-30) . WCDMA RAN IP RAN Parameter ID MODE NE NodeB MML SET E1T1BEAR(Optional) Description Meaning: Bearing mode GUI Value Range: ATM.Error! Style not defined. 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 Error! Style not defined.. 6 Counters For details.Error! Style not defined. Ltd 6-1 . see the BSC6900 UMTS Performance Counter Reference and the NodeB Performance Counter Reference. Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.

.

and definitions. terms.Error! Style not defined. see the Glossary.WCDMA RAN IP RAN Error! Style not defined. 7 Glossary For the acronyms. Ltd 7-1 . Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co. abbreviations..

.

410: UTRAN Iu Interface: General Aspects and Principles [2] 3GPP TS 25.430: UTRAN Iub Interface: General Aspects and Principles [4] 3GPP TR25. Ltd 8-1 . 8 Reference Documents [1] 3GPP TS 25.Error! Style not defined.420: UTRAN Iur Interface: General Aspects and Principles [3] 3GPP TS 25..WCDMA RAN IP RAN Error! Style not defined.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 Issue 01 (2010-03-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co.