IP RAN

RAN12 IPRAN Deployment Guide

Keywords: IPRAN, SCTP, IPPATH, VLAN, DSCP

Abstract: This document describes the preparations and precautions for the IPRAN deployment, IPRAN networking examples of each interface, data planning, configuration examples, and basic principle and configuration of remote OM channels. It provides operation guides to the IPRAN deployment on site.

The information in this document is for the internal use only and cannot be used as the basis for the reply to a customer or Market Dept.

Acronyms and Abbreviations

Table 1-1 Explanations of acronyms and abbreviations

1 Overview

1.1 Introduction

From V210, the Iub, Iur and IU interfaces can serve the IP transport. Then, operators can implement the transmission capacity expansion by using the existing IP network, thus, saving the network construction expanses. In addition, the IP network provides multiple

Acronym and Abbreviation Expansion SCTP Simple Control Transmission Protocol DSCP Differentiated Services Code Point VLAN Virtual LAN DSCP Differentiated Services Code Point PPP Point-to-Point Protocol MP Multilink PPP

access modes as well as sufficient transmission bandwidth for the high-speed data services, including the HSDPA and HSPA+.

For the description of the IPRAN feature of V210 and earlier versions, refer to the RAN10 Feature Description and RAN10 V2 IPRAN Deployment Guide.

For the description of the IPRAN feature of V211 and V212, refer to the corresponding RAN Feature Description.

1.2 Others

For basic principles and protocols (including TCP, UDP, PPP, ARP, VLAN, TRACERT, SCTP, and M3UA) adopted by the IPRAN feature, refer to the V18 IPRAN Deployment Guide and V210 IPRAN Deployment Guide.

1.3 Availability

1.3.1 Involved NEs

The IP feature requires the cooperation of the NodeB, RNC, and CN. Table 1-1 lists the data configuration requirements of the IP feature on these NEs. √ indicates that the NE is required.

Table 1-1 Hardware support

1.3.2 Version Support

Table 1-2 Supported versions

Requirements of the IP Feature

NodeB RNC

Data configuration requirements

√ √

Hardware requirements

WMPT/UTRP PEUa/POUa/UOIa_IP/FG2a/GOUa/POUc/FG2c/GOUc

Product Supported Versions RNC BSC6810 BSC6900V900R012 NodeB DBS3900 V200R012

DBS3800/ BTS3812E

V100R012

CME M2000 V200R009/V200R10

1.3.3 Other Support

For support capabilities of the boards of the RNC and the NodeB, refer to the related product manuals.

2 Common Networking

2.1 V2 Backup Policy

2.1.1 Backup Mode on the RNC

RNC backup consists of board backup and port backup.

For detailed description, refer to Parts Reliability of the Product Description. The following brief description is for your reference.

I. Board Backup

When two boards work in backup mode, one board is active and the other is standby. Services can be processed by either the active board only or both the active and standby boards. If the active board is faulty, the RNC automatically switches over the active and standby boards.

During the addition of a board through the ADD BRD command, the backup of the boards is configurable. If Backup is set to YES, the backup mode of boards is board backup.

II. Board Backup+Port Backup

The port backup can be configured on the basis of board backup. In backup mode, one port is active and the other is standby. Services can be transmitted through the active port only. If the active port is faulty, the RNC automatically switches over the active and standby ports.

Backup of FG2a/GOUa/FG2c/GOUc boards+port backup

If boards work in backup mode, you can run the ADD ETHREDPORT command to configure the backup of FE/GE ports.

Backup of UOIa_IP/POUa/POUc boards+port backup

When the boards work in backup mode, the corresponding optical ports on the active and standby boards, such as optical ports 0 on the boards, can be configured for MSP 1:1 or MSP 1+1 backup (unidirectional or bidirectional).

The SET MSP command is available for setting the attributes for MSP backup. The MSP attributes refer to Revertive type, WTR Time (required only when Revertive type is set to REVERTIVE), K2 Mode, SDSF Priority, and Backup mode. The settings of these parameters must be consistent with those at the peer end through negotiation.

III. Board Backup+Load Sharing Between Ports (No Port Backup)

In this mode, FG2a/GOUa/FG2c/GOUc boards work in backup mode, whereas ports do not work in backup mode. That is, ports on both active and standby boards can be used at the same time.

2.1.2 Backup Mode on the NodeB

I. Board Backup Mode Instead of Port Backup Mode on the NodeB

When boards work in backup mode, the configuration can be performed only on the active board which processes the data, whereas the standby board is monitored. When all used physical links on the active boards are unavailable (for example, the LOS alarm is generated on the E1 cable or the FE interface is down) and there are available physical links on the standby boards, the active/standby switchover is performed. During the switchover, both the active board and standby board are restarted and the configuration on the active board is loaded to the standby board. Then, the standby board becomes active. The switchover may cause service interruptions.

You can configure the board backup mode only on the CME rather than MML commands. However, you can run the LST IUBGRP command to query the working mode of boards.

II. Board Backup Constraints on the NodeB

The following boards support board backup. − V212: WMPT/UTRP − V112: Either the NUTI or the HBBU supports board backup, whereas the NDTI

does not support board backup. Boards work in cold backup mode on the NodeB. Therefore, the board switchover

may cause service interruptions. If the boards are set to work in active/standby mode, ensure that transmission

cables on the active and standby boards are properly connected, for example, connect cables on the FE ports and connect E1 cables on active and standby boards.

When boards work in active/standby mode, transmission objects except the objects in the physical layer can only be configured in the logic slot. The smaller slot number in slot backup mode is the logic slot number.

2.2 Common Networking Modes

For detailed networking description, refer to Transport and Networking of the Product Description.

2.2.1 Layer 2 Networking Mode

The RNC connects to the NodeB (Iub interface), SGSN (IU interface), and RNC (Iur interface) through the local area network (LAN). The interface addresses of all NEs are on the same network segment.

Layer 2 networking modes are classified into the following types in terms of the transmission media.

I. IP over E1/T1 over PDH/SDH Networking (Iub interface)—Connection to the RNC Through E1/T1 Cables

Figure 2-1 IPRAN layer 2 networking based on PDH/SDH transmission—connection to the RNC through E1/T1 cables

Figure 2-2 IPRAN layer 2 networking based on SDH transmission—channelized STM-1 access to the RNC

Both the RNC and NodeB connect to the transport network through E1/T1 cables. Alternatively, the RNC connects to the transport network through the channelized STM-1 on the POUa/POUc and the NodeB connects to the transport network through

the E1/T1 cables. The data is transmitted in IP over MLPPP/PPP over E1/T1 mode. The NodeB can obtain the line clock through E1/T1 cables. Backup mode

PEUas can be set to work in active/standby mode by using the ADD BRD command. The active and standby PEUas are connected to the peer end through Y-shaped E1/T1 cables.

The POUa and POUc can be set to work in active/standby mode by using the ADD BRD command. Optical ports on the boards can be set to work in MSP 1:1 or MSP 1+1 mode.

The RNC and NodeB can enable the IP header compression algorithm to improve the transmission efficiency.

II. IP Layer 2 Network Based on MSTP (Iub Interface)

Figure 2-3 IPRAN layer 2 networking based on MSTP

The RNC connects to the MSTP network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB connects to the transport network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. The NodeB can extract the clock from the MSTP network through additional E1/T1

cables or obtain the clock source from the GPS/IP clock server. Backup mode: Backup of interface boards on the RNC+port backup or board

backup+load sharing between ports Transmission efficiency: Multiple NodeBs share the VC trunk bandwidth to make full

use of transport network resources. QoS: To implement the QoS scheduling of various services, the RNC and NodeB

support IEEE 802.1p/q and the mapping between the DSCP and VLAN priority, whereas the transport network supports IEEE 802.1p/q.

III. IP Layer 2 Networking (Iub/Iur/IUCS/IUPS) Based on the Data Network

The RNC connects to the NodeB (Iub interface), SGSN (IU interface), and RNC (Iur interface) through the layer 2 data network, including the PTN networking or layer 2 LAN switch networking. Interface addresses of interconnected NEs are on the same network segment.

Figure 2-4 IPRAN layer 2 networking based on the data network

The RNC connects to the layer 2 data network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB/NRNC/MGW/SGSN connects to the layer 2 data network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. The NodeB can extract the clock from the transmission device in the ATM network

through additional E1/T1 cables or obtain the clock source from the GPS/IP clock server. Backup mode: Backup of interface boards on the RNC+port backup or board

backup+load sharing between ports QoS: To implement the QoS scheduling of the data network, the RNC, NodeB, core

network (CN) device, and layer 2 supports IEEE 802.1p/q, that is, support the VLAN and VLAN priority. Generally, the data network needs to meet the following conditions: − The delay is controlled within 40 ms (unidirectional); the jitter is smaller than 15

ms. − The packet loss rate is within 0.05%. − The values vary from site to site and they are subject to the bid clarification

document of the marketing department.

2.2.2 Layer 3 Networking Modes

I. Direct Connection Between the RNC and A Router

This networking mode is seldom used.

The RNC connects to the NodeB (Iub interface), SGSN (IU interface), and RNC (Iur interface) through the layer 3 switching network. Interface addresses of all NEs are on the same network segment.

Figure 2-5 Direct connection between the RNC and a router

The RNC connects to the data network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB/NRNC/MGW/SGSN connects to the data network through the FE electrical port or FE/GE optical port. The data is transmitted in IP over Ethernet mode. The NodeB can extract the clock through additional E1/T1 cables or obtain the clock

source from the GPS/IP clock server. Backup mode: Backup of interface boards on the RNC+port backup

The active and standby ports connect to two ports on the router/layer 3 switch. Two ports on the router/layer 3 switch are configured in an identical VLAN. In addition, the two ports are configured with one VLAN interface address, which serves as the network gateway of the RNC. QoS: To implement the QoS scheduling of various services, the RNC, NodeB, and

CN device support IEEE 802.1p/q and the mapping between the DSCP and VLAN priority, whereas the data network supports the MPLS TE, MPLS Diffserv, IP Diffserv, and VLAN COS. Generally, the data network needs to meet the following conditions: − The delay is controlled within 40 ms (unidirectional); the jitter is smaller than 15

ms. − The packet loss rate is within 0.05%. − The values vary from site to site and they are subject to the bidding document of

the marketing department.

II. Direct Connection Between the RNC and Two Routers

Figure 2-6 Direct connection between the RNC and two routers

The RNC connects to the data network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB/NRNC/MGW/SGSN connects to the data network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. The NodeB can extract the clock through additional E1/T1 cables or obtain the clock

source from the GPS/IP clock server. Backup mode: Backup of interface boards on the RNC+port backup

The active and standby ports on the RNC connect to two ports of the active and standby PEs. The RNC connects to the data transmission network through the PE. The active and standby ports on the RNC share one IP address (IP1-1). Two ports of the active and standby PEs are configured in the same VLAN. In addition, VRRP is configured and the virtual VRRP IP address (IP-0) serves as the network gateway of the RNC. QoS: To implement the QoS scheduling of various services, the RNC, NodeB, and

CN device support IEEE 802.1p/q and the mapping between the DSCP and VLAN priority, whereas the data network supports the MPLS TE, MPLS Diffserv, IP Diffserv, and VLAN COS. Generally, the data network needs to meet the following conditions: The delay is controlled within 40 ms (unidirectional); the jitter is smaller than 15 ms; the packet loss rate is within 0.05%. The values vary from site to site and they are subject to the bid clarification document of the marketing department.

2.2.3 Load Sharing Networking

The load sharing networking mode can be used during the interconnection between the IUCS and IUPS.

Figure 2-7 Layer 3 load sharing networking

The RNC connects to the data network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB/NRNC/MGW/SGSN connects to the data network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. The NodeB can extract the clock through additional E1/T1 cables or obtain the clock

source from the GPS/IP clock server. Backup mode: board backup+load sharing between ports

Thanks to the double reliability guarantee of the boards and transmission, you can obtain doubled transmission bandwidth. Two ports working in load sharing mode on the active and standby boards connect to two routers/layer 3 switches. Two ports on the active and standby boards on the RNC are configured with two IP addresses (IP1, IP2) and connect to two network gateways (GW1, GW2) on the interconnected routers/layer 3 switches. The traffic on the RNC can use the IP addresses of interfaces or be configured with the logic IP address (DEVIP). QoS: To implement the QoS scheduling of various services, the RNC, NodeB, and

CN device support IEEE 802.1p/q and the mapping between the DSCP and VLAN priority, whereas the data network supports the MPLS TE, MPLS Diffserv, IP Diffserv, and VLAN COS. Generally, the data network needs to meet the following conditions: − The delay is controlled within 40 ms (unidirectional). − The jitter is smaller than 15 ms; the packet loss rate is within 0.05%. − The values vary from site to site and they are subject to the bid clarification

document of the marketing department.

2.2.4 Hybrid Transport Networking

Figure 2-8 IPRAN networking based hybrid transport—Iub interface

On the Iub interface, services of different QoS requirements are transmitted on transport networks with two different QoS requirements. High-QoS services are transmitted through dedicated lines, whereas services of lower QoS requirements are transmitted through low-cost transport networks, for example, Ethernet. − Services on the control plane, real-time services, and OM services are

transmitted on high-QoS transport network, for example, the TDM transport network.

− Non-real-time services are transmitted on the low-QoS data network. Low-QoS path: The RNC connects to the data network through the FE/GE electrical

port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board. The NodeB/NRNC/MGW/SGSN connects to the data network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. High-QoS path: Both the RNC and NodeB connect to the TDM transport network

through E1/T1 cables. The data is transmitted in IP over MLPPP/PPP over E1/T1 mode. The NodeB can obtain the line clock through E1/T1 cables. Backup mode − Backup of FG2a/GOUa/FG2c/GOUc boards+port backup or board backup+load

sharing between ports − Backup of PEUa/POUa/UOIa_IP/POUc boards

2.2.5 ATM/IP Dual Stack-Based Networking

Figure 2-9 IPRAN networking based on dual stack transport—Iub interface

If the original ATM networking provides insufficient bandwidth (especially when the HSDPA/HSUAP is used), you can expand the IP transport network to save transmission expanses and obtain high bandwidth. The original ATM networking remains unchanged. Both the RNC and NodeB

connect to the TDM transport network through E1/T1 cables. Both the RNC and NodeB connect to the data transmission network through the new

IP interface board: The RNC connects to the data network through the FE/GE electrical port or GE optical port on the FG2a/GOUa/FG2c/GOUc interface board, whereas the NodeB/NRNC/MGW/SGSN connects to the data network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode. The NodeB can obtain the line clock through E1/T1 cables. Backup mode: For details, see layer 2 data networking and layer 3 data networking. QoS: Services on the control plane, real-time services, and OM services are

transmitted on the ATM network, whereas the non-real-time services are transmitted on the IP network.

3 Major Configurations of RAN12 IPRAN

3.1 Description

Configuration examples are based on RNC V900R012 and NodeB V200R12. For configuration details, refer to the Initial Configuration Guide and the

corresponding MML online help. The networking of configuration examples is only for reference. The networking of

each site needs to be designed and deployed according to the actual situations. During the deployment on site, the data on the NodeB is configured on the CME. For

clear configuration description, here only describes the configuration related to MML commands.

3.2 Setting Attributes of An Ethernet Port

I. RNC

Command: SET ETHPORT

Note: Refer to the online help on the LMT, especially the precautions during the attribute setting.

Set the VLAN tag attribute of an Ethernet port.

This attribute cannot be set. The default value is HYBRID.

Set the working mode of the FE/GE port. Ensure that the working modes (auto negotiation or non-auto negotiation) of the two ends are consistent. Set the maximum transmission unit (MTU). Ensure that the MTU on the RNC is

smaller or equal to that of the intermediate transmission device. Set the ratio of the minimum bandwidth of the OAM flow to the port bandwidth. The

default ratio is 0%. The ratio can be adjusted according to the planning of the existing network if the OMCH between M2000 and NodeB pass by RNC.

SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0;

II. NodeB

Command: SET ETHPORT

Set the VLAN tag attribute of an Ethernet port.

This attribute cannot be set. The default value is HYBRID.

Set the working mode of the FE/GE port. Ensure that the working modes (auto negotiation or non-auto negotiation) of the two ends are consistent. Set the maximum transmission unit (MTU). Ensure that the MTU on the NodeB is

smaller or equal to that of the intermediate transmission device. Set the ARP proxy switch. If the OM IP address and the corresponding interface IP

address are on the same network segment, you need to enable the ARP proxy switch.

SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, ARPPROXY=ENABLE;

3.3 VLAN ID Configuration

3.3.1 General Principle of the VLAN Configuration

If VLAN IDs are carried by the packets from the RNC and NodeB, you need to perform the relevant VLAN configuration on the RNC and NodeB. If the VLAN IDs are not carried by the packets from the RNC and NodeB but can be carried by packets on the intermediate device (for example, the switch), you need not perform the relevant VLAN configuration on the RNC and NodeB. The VLAN IDs used by each site need to be planned by the operator and configured

on the intermediate transmission device. A VLAN ID can be added according to the IP address of the next hop (IP address of

the network gateway) on the RNC.

3.3.2 Adding the VLAN ID According to the IP Address of the Next Hop

I. RNC

Command: ADD VLANID

1. Packets destined to the network gateway with this IP address carry the same VLAN ID.

2. IP packets sent from the network gateway with this IP address carry the specified VLAN ID.

3. The ARP request packets to the network gateway with this IP address carry the specified VLAN ID. For example, run the following command to set the IP address of the network gateway to GW1 and set the VLAN ID to 100 for all packets destined to this network gateway. ADD VLANID: IPADDR="GW1", VLANID=100

II. NodeB

Command: ADD VLANMAP

This command is only valid for V2.

Method 1:

All packets from the NodeB to the network gateway carry the same VLAN ID and have the same VLAN priority.

When running the ADD VLANMAP command, select SINGLEVLAN for the VLAN mode.

ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 for all packets destined to the network gateway.

Method 2 (recommended)

ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0;

You can set the VLANID of data flows by MML command SET VLANCLASS and refer to the following information to get detailed.

3.3.3 Setting the VLAN ID for the Data on the SCTP Link

I. RNC

The VLAN ID is added according to the IP address of the next hop and does not need to be independently configured. In particular, disable the VLAN tag when running the ADD SCTPLNK command.

II. NodeB

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=SIG, INSTAG=ENABLE, VLANID=100, VLANPRIO=6;

2. For V2, add the VLAN ID according to the IP address of the next hop. Additional configurations are unnecessary. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 for all packets destined to the network gateway.

3. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // Set the VLAN ID to 100 for the signaling link data. Note: If different VLAN priorities need to be assigned to different types of services delivered to the network gateway, set the VLAN mode to VLANGROUP. If SINGLEVLAN is selected, all packets destined to the network gateway carry the same VLAN ID and have the same VLAN priority.

3.3.4 Setting the VLAN ID for the Data on the IP Path

I. RNC

The VLAN ID is added according to the IP address of the next hop and does not need to be independently configured. In particular, set VLANID Flag to DISABLE when running the ADD IPPATH command.

II. NodeB

Run the ADD IPPATH command to set the DSCP value for each IP path.

ADD IPPATH: PATHID=1, JNRSCGRP=DISABLE, DSCP=46; // Set the DSCP value of a specific IP path to 46.




When running the SET VLANCLASS command, set Traffic Type to USERDATA, which indicates that the UDP protocol is supported, including the voice service, PS, HSPA service, and data on common channels.

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=48, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // For the data on the IP path whose DSCP value is 46, the VLAN ID is set to 100. Note: Common signaling messages are transmitted on the common channels of the cell through UDP. These packets have higher priorities. The data from the NodeB to the RNC uses the DSCP value specified by Signal Priority in the SET DIFPRI command. Therefore, set Traffic Type to USERDATA and add the corresponding VLAN ID to the data whose DSCP is specified by Signal Priority. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=46, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 for the data on the IP path whose DSCP is 46. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=38, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set the VLAN ID to 100 for the data on the IP path whose DSCP is 38. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=22, INSTAG=ENABLE, VLANID=100, VLANPRIO=2; // Set the VLAN ID to 100 for the data on the IP path whose DSCP is 22. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=14, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the VLAN ID to 100 for the data on the IP path whose DSCP is 14.

2. For V2, Method 1 Add the VLAN ID according to the IP address of the next hop. Additional configurations are unnecessary. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 for all packets destined to the network gateway.

3. For V2 Method 2 (Recommended)

if VLANGROUP is selected, run the following command:

ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=48, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // Set the VLAN ID to 100 for the

data whose DSCP value is 48. Note: Common signaling messages are transmitted on the common channels of the cell through UDP. These packets have higher priorities. The data from the NodeB to the RNC uses the DSCP value specified by Signal Priority in the SET DIFPRI command. Therefore, set Traffic Type to USERDATA and add the corresponding VLAN ID to the data whose DSCP is specified by Signal Priority. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=46, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 for the data on the IP path whose DSCP value is 46. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=38, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set the VLAN ID to 100 for the data on the IP path whose DSCP value is 38. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=22, INSTAG=ENABLE, VLANID=100, VLANPRIO=2; // Set the VLAN ID to 100 for the data on the IP path whose DSCP value is 22. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=14, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the VLAN ID to 100 for the data on the IP path whose DSCP value is 14.

3.3.5 Setting the VLAN ID of the OAM Flow on the Iub Interface

I. RNC

The VLAN ID is added according to the IP address of the next hop and does not need to be configured independently.

II. NodeB

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=OM, INSTAG=ENABLE, VLANID=100, VLANPRIO=5;

2. For V2

Method 1:

Add the VLAN ID according to the IP address of the next hop. Additional configurations are unnecessary.

ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 for all packets destined to the network gateway.

3. For V2

Method 2

If VLANGROUP is selected, run the following command:

ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 for the OAM data, including the TCP maintenance data flow and SNTP data flow.

3.3.6 Setting the VLAN ID of the PTP Clock Packet

I. RNC

Not involved.

II. NodeB

1. For V1, run the following command:

SET VLANCLASS: TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=100, VLANPRIO=5;

2. For V2

Method 1


ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100,

3. For V2

Mehod 2

If VLANGROUP is selected in the ADD VLANMAP command, run the following command:

SET VLANCLASS: TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=100; // Set the VLAN ID to 100 for the PTP data flow.

3.3.7 Setting the VLAN ID of the BFD Packet

I. RNC

The VLAN ID is added according to the IP address of the next hop and does not need to be configured independently.

II. NodeB

1. For V2

Method 1


ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100,

2. For V2

Method 2

If VLANGROUP is selected in the ADD VLANMAP command, run the following command:

Run the ADD BFDSESSION command to set the DSCP value. The default DSCP is 48.

ADD BFDSESSION: BFDSN=0, DSCP=34; // Set the DSCP value of a specific BFD session to 48.

SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=34, INSTAG=ENABLE, VLANID=100; // Set the VLAN ID to 100 for the BFD session. Set Traffic Type to USERDATA and set User Data Service Priority to the DSCP value of the ADD BFDSESSION command.

3.3.8 Setting the VLAN ID for the ARP/DHCP/ICMP/Tracert Packet

I. RNC

Set the VLAN ID for the packets destined to the network gateway. For example, the IP address of the network gateway of the RNC is GW1. Run the following command to set the VLAN ID to 100 for all packets, including ARP/DHCP/ICMP/Tracert packets.

ADD VLANID: IPADDR="GW1", VLANID=100;

II. NodeB

SET VLANCLASS: TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=100; // Traffic Type is set to OTHER, indicating that ARP/DHCP/ICMP/Tracert is supported.

Note: During the initial deployment phase of a new site, DHCP packets from the NodeB carry the VLAN ID learnt by the VLAN.

3.4 DSCP Value Configuration

Note: The DSCP values recommended in the Transmission Configuration Specifications are used in the following example. The DSCP value used by each site needs to be planned by the operator and configured on the intermediate transmission device.

3.4.1 Setting the DSCP Value of the SCTP Link

I. RNC

ADD SCTPLNK: SCTPLNKN=2, DSCP=48; // Set the DSCP value of an SCTP link to 48.

II. NodeB

Command: SET DIFPRI

SET DIFPRI: PRIRULE=DSCP, SIGPRI=48; // Set the DSCP value of a signaling link to 48.

3.4.2 Setting the DSCP Value of the IP Path

I. RNC

Command: ADD IPPATH, SET PHBMAP

1. Run the ADD IPPATH command to set IP path type of an IP path to a PHB. ADD IPPATH: ANI=1, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=EF; // Set IP path type of a specific IP path to EF. ADD IPPATH: ANI=1, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF43; // Set IP path type of a specific IP path to AF43. ADD IPPATH: ANI=1, PATHID=3, ITFT=IUB, TRANST=IP, PATHT=AF23; // Set IP path type of a specific IP path to AF23. ADD IPPATH: ANI=1, PATHID=4, ITFT=IUB, TRANST=IP, PATHT=AF13; // Set IP path type of a specific IP path to AF13.

2. Run the SET PHBMAP command to set the DSCP value corresponding to the PHB. You can run the LST PHBMAP command to query the default configuration. SET PHBMAP: PHB=EF, DSCP=46; // When the PHB is EF, the DSCP value is 46.

SET PHBMAP: PHB= AF43, DSCP=38; // When the PHB is AF43, the DSCP value is 38. SET PHBMAP: PHB= AF23, DSCP=22; // When the PHB is AF23, the DSCP value is 22. SET PHBMAP: PHB= AF13, DSCP=14; // When the PHB is AF13, the DSCP value is 14.

II. NodeB

ADD IPPATH: PATHID=1, JNRSCGRP=DISABLE, DSCP=46; // Set the DSCP value of an IP path to 46.




3.4.3 Setting the DSCP Value of the OAM Flow on the Iub Interface

I. RNC

SET QUEUEMAP: OAMMINBWKEY=ON, OAMFLOWDSCP=34; // Set the minimum bandwidth switch of the OAM flow to ON and set the DSCP value of the OAM flow to 34.

By default, the minimum bandwidth switch is disabled. The data of the OAM flow enters a dedicated queue for transmission rather than queues 0 to 5. If the minimum bandwidth of the OAM flow is set to ON, the DSCP value of the OAM flow must be different from the DSCP value of any IP path.

II. NodeB

SET DIFPRI: PRIRULE=DSCP, SIGPRI=0, OMDIF=DISABLE, OMPRI=34; //The OM priority is not considered. Set the DSCP value of the OM flow to 34.

SET DIFPRI: PRIRULE=DSCP, SIGPRI=0, OMDIF=ENABLE, OMHPRI=34, OMLPRI=10; // The OM priority is considered. Set the DSCP value of the OM flow with the high priority to 43 and that of the OM flow with the low priority to 10.

3.4.4 Setting the DSCP Value of the PTP Clock Packet

I. RNC

Not involved.

II. NodeB

SET DIFPRI: PRIRULE=DSCP, PTPPRI=34; // Set the DSCP value of the PTP clock packet to 34. Generally, the DSCP value of the PTP packet is consistent with that of the OAM flow.

3.4.5 Setting the DSCP Value of the BFD Packet

I. RNC

The RNC does not support the DSCP value configuration of the BFD packet. The default DSCP value is 56.

II. NodeB

Command: ADD BFDSESSION

ADD BFDSESSION: BFDSN=1, HT=SINGLE_HOP, DSCP=34; // Set the DSCP value of the BFD session flow to 34. The default DSCP value is 48.

3.4.6 Setting the DSCP Value of the DHCP/ICMP/Tracert Packet

I. RNC

1. The RNC does not support the DSCP value configuration of the DHCP/Tracert packet. The default DSCP value is 0.

2. You can run the PING IP command to set the DSCP value of the ICMP packet.

PING IP: CONTPING=NO, DSCP=46; // Set the DSCP value of the ping packet to 46.

II. NodeB

1. DHCP: For a new site, the DSCP value is fixed to 0. 2. Tracert/ICMP: The DHCP value configuration is not supported. If the NodeB initiates

an ICMP request, the DSCP value is fixed to 63; if the NodeB initiates a Tracert packet, the DSCP value is fixed to 0; the ICMP response uses the DSCP value of the ICMP request; the DSCP value of the Tracert packet is fixed to 0.

3.5 VLAN Priority Configuration

The VLAN priorities used by each site need to be planned by the operator and configured on the intermediate transmission device.

3.5.1 Setting the VLAN Priority of the SCTP Link

I. RNC

Command: ADD SCTPLNK, SET DSCPMAP

1. Run the ADD SCTPLNK command to set the DSCP value of the SCTP link. ADD SCTPLNK: SCTPLNKN=2, DSCP=48; // Set the DSCP value of an SCTP link to 48.

2. Run the SET DSCPMAP command to set the mapping between the DSCP value and the VLAN priority. SET DSCPMAP: DSCP=48, VLANPRI=6; // The DSCP value 48 maps the VLAN priority 6.

II. NodeB

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=SIG, INSTAG=ENABLE, VLANID=100, VLANPRIO=6;

2. For V2, set the VLAN ID and VLAN priority according to the IP address of the next hop. Additional configurations are unnecessary. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // Set the IP address of the network

gateway of the NodeB to GW2. Set the VLAN ID to 100 and VLAN priority to 6 for all packets destined to the network gateway.

3. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // For the signaling link data, set the VLAN ID to 100 and VLAN priority to 6. Note If different VLAN priorities need to be assigned to different types of services delivered to the network gateway, set the VLAN mode to VLANGROUP. If the VLAN mode is set to SINGLEVLAN, all packets destined to the network gateway carry the same VLAN ID and have the same VLAN priority.

3.5.2 Setting the VLAN Priority of the IP Path

I. RNC

Command: ADD IPPATH, SET PHBMAP, SET DSCPMAP

1. Run the ADD IPPATH command to set IP path type of an IP path to a PHB. ADD IPPATH: ANI=1, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=EF; // Set IP path type of a specific IP path to EF. ADD IPPATH: ANI=1, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF43; // Set IP path type of a specific IP path to AF43. ADD IPPATH: ANI=1, PATHID=3, ITFT=IUB, TRANST=IP, PATHT=AF23; // Set IP path type of a specific IP path to AF23. ADD IPPATH: ANI=1, PATHID=4, ITFT=IUB, TRANST=IP, PATHT=AF13; // Set IP path type of a specific IP path to AF13.

2. Run the SET PHBMAP command to set the DSCP value corresponding to the PHB. SET PHBMAP: PHB=EF, DSCP=46; // When the PHB is EF, the DSCP value is 46. SET PHBMAP: PHB= AF43, DSCP=38; // When the PHB is AF43, the DSCP value is 38. SET PHBMAP: PHB= AF23, DSCP=22; // When the PHB is AF23, the DSCP value is 22. SET PHBMAP: PHB= AF13, DSCP=14; // When the PHB is AF13, the DSCP value is 14.

3. Run the SET DSCPMAP command to set the mapping between the DSCP value and the VLAN priority. You can run the LST DSCPMAP command to query the default configuration. SET DSCPMAP: DSCP=46, VLANPRI=5; // The DSCP value 46 maps the VLAN priority 5. SET DSCPMAP: DSCP=38, VLANPRI=4; // The DSCP value 38 maps the VLAN priority 4. SET DSCPMAP: DSCP=22, VLANPRI=2; // The DSCP value 22 maps the VLAN priority 2. SET DSCPMAP: DSCP=14, VLANPRI=1; // The DSCP value 14 maps the VLAN priority 1.

II. NodeB

Run the ADD IPPATH command to set the DSCP value of an IP path.





When running the SET VLANCLASS command, set Traffic Type to USERDATA, which indicates that the UDP protocol is supported, including the voice service, PS, HSPA service, and data on common channels.

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=48, INSTAG=ENABLE, VLANID=100, VLANPRIO=6; // Set the VLAN ID to 100 for the data whose DSCP value is 48. Note: Common signaling messages are transmitted on the common channels of the cell through UDP. These packets have higher priorities. The data from the NodeB to the RNC uses the DSCP value specified by SIG Priority in the SET DIFPRI command. Therefore, set Traffic Type to USERDATA and add the corresponding VLAN ID to the data whose DSCP is specified by Signal Priority. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=46, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 and VLAN priority to 5 for the data on the IP path whose DSCP value is 46. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=38, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set the VLAN ID to 100 and VLAN priority to 4 for the data on the IP path whose DSCP value is 38. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=22, INSTAG=ENABLE, VLANID=100, VLANPRIO=2; // Set the VLAN ID to 100 and VLAN priority to 2 for the data on the IP path whose DSCP value is 22. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=14, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the VLAN ID to 100 and VLAN priority to 1 for the data on the IP path whose DSCP value is 14.

2. For V2, add the VLAN ID according to the IP address of the next hop. Additional configurations are unnecessary. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 for all packets destined to the network gateway.

3. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=48, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 and VLAN priority to 6 for the data whose DSCP is 48. Note: Common signaling messages are transmitted on the common channels of the cell through UDP. These packets have higher priorities. The data from the NodeB to the RNC uses the DSCP value specified by Signal Priority in the SET DIFPRI

command. Therefore, set Traffic Type to USERDATA and add the corresponding VLAN ID to the data whose DSCP is specified by Signal Priority. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=46, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set the VLAN ID to 100 and VLAN priority to 5 for the data on the IP path whose DSCP is 46. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=38, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set the VLAN ID to 100 and VLAN priority to 4 for the data on the IP path whose DSCP is 38. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=22, INSTAG=ENABLE, VLANID=100, VLANPRIO=2; // Set the VLAN ID to 100 and VLAN priority to 2 for the data on the IP path whose DSCP is 22. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=14, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the VLAN ID to 100 and VLAN priority to 1 for the data on the IP path whose DSCP is 14.

3.5.3 Setting the VLAN Priority of the OAM Flow on the Iub Interface

I. RNC

Command: SET QUEUEMAP, SET DSCPMAP

1. Run the SET QUEUEMAP command to set the DSCP value of the Iub OAM flow. For details, see section 3.4.3 .

2. Run the SET DSCPMAP command to set the mapping between the DSCP value and the VLAN priority of the Iub OAM flow. SET DSCPMAP: DSCP=34, VLANPRI=4; // The DSCP value 34 maps the VLAN priority 4.

II. NodeB

1. For V1, run the following command: SET VLANCLASS: TRAFFIC=OM, INSTAG=ENABLE, VLANID=100, VLANPRIO=4;

2. For V2, set the VLAN ID and VLAN priority according to the IP address of the next hop. Additional configurations are unnecessary. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set the IP address of the network gateway of the NodeB to GW2. Set the VLAN ID to 100 and VLAN priority to 6 for all packets destined to the network gateway.

3. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM, INSTAG=ENABLE, OMDIF=DISABLE, VLANID=100, VLANPRIO=4; // Set the VLAN ID to 100 and VLAN priority to 4 for the OM data. // The priority of the OM flow is not considered. Set the VLAN priority of the Iub OAM flow to 4. SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM, INSTAG=ENABLE, OMDIF=ENABLE, VLANID=100, VLANHPRIO=4, VLANLPRIO=1; // The OM priority is considered. Set the priority of the OM flow with the high priority to 34 and the priority of the OM flow with the low priority to 1.

3.5.4 Setting the VLAN Priority of the PTP Clock Packet

I. RNC

Not involved.

II. NodeB


2. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET DIFPRI: PRIRULE=DSCP, PTPPRI=34; // Set the DSCP value of the PTP clock packet to 34. Generally, the DSCP value of the PTP packet is consistent with that of the OAM flow. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=34, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set VLAN Priority to 4, Traffic Type to USERDATA, and SPVPRIO to the DSCP value of the PTP packet.

3.5.5 Setting the VLAN Priority of the BFD Packet

I. RNC

The RNC does not support the DSCP value configuration of the BFD packet. The default DSCP value is 7.

II. NodeB


2. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET DIFPRI: PRIRULE=DSCP, PTPPRI=34; // Set the DSCP value of the PTP clock packet to 34. Generally, the DSCP value of the PTP packet is consistent with that of the OAM flow. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=34, INSTAG=ENABLE, VLANID=100, ADD BFDSESSION: BFDSN=1, HT=SINGLE_HOP, DSCP=34; // Set the DSCP value of a specific BFD session to 48. SET VLANCLASS: TRAFFIC=USERDATA, SRVPRIO=34, INSTAG=ENABLE, VLANID=100, VLANPRIO=4; // Set VLAN Priority of the BFD session flow to 4 and Traffic Type to USERDATA for the BFD packets are transmitted through UDP. Set the user priority to the DSCP value of the BFD packet.

3.5.6 Setting the VLAN Priority of the ARP/DHCP/ICMP/Tracert

Packet I. RNC

1. ARP packet The RNC does not support the DSCP value configuration of the ARP packet. The default DSCP value is 0.

2. DHCP/Tracert The RNC does not support the DSCP value configuration of the DHCP/Tracert packet. The default DSCP value is 0.

3. ICMP Run the PING IP command to set the DSCP value of the ping packet and then run the SET DSCPMAP command to set the VLAN priority mapping the DSCP value. PING IP: CONTPING=NO, DSCP=46; // Set the DSCP value of the ping packet to 46.SET DSCPMAP: DSCP=46, VLANPRI=5; // The DSCP value 46 maps the VLAN priority 5.

II. NodeB


2. For V2, if VLANGROUP is selected, run the following command: ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=VLANGROUP, VLANGROUPNO=0; SET VLANCLASS: TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=100, VLANPRIO=5; // Set VLAN Priority of the ARP/DHCP/ICMP/Tracert packet to 5 and Traffic Type to OTHER, which indicates that ARP/DHCP/ICMP/Tracert is supported. Note The VLAN priority of either the ARP/ICMP request or response uses the value set in the preceding command. During the initial deployment phase of a new site, DHCP packets from the NodeB carry the VLAN ID learnt by the VLAN. VLAN Priority of such packets is set to 0.

3.6 Others

3.6.1 Setting the Mapping Between Queues at IP Ports and DSCP Values on the RNC

Command: SET QUEUEMAP

The DSCP field in the IP packet indicates the priority of the packet. After the mapping between queues and DSCP values is set, IP packets of different types are assigned to queues of different priorities for transmission.

SET QUEUEMAP: Q0MINDSCP=XX, Q1MINDSCP= XX, Q2MINDSCP= XX, Q3MINDSCP= XX, Q4MINDSCP= XX;

You can run the LST QUEUEMAP command to query the default mapping configuration as follows.

The default mapping between DSCP values and queues 0 to 5 is as follows.

Note

IP ports include the Ethernet ports, PPP links, MP groups, and IP logic ports. Each IP port has six traffic queues with different priorities. The queues, from queue 0 to queue 5, are in descending order by priority.

(2) Q0MINDSCP to Q4MINDSCP must meet the following conditions:

Q0MINDSCP > Q1MINDSCP > Q2MINDSCP > Q3MINDSCP > Q4MINDSCP

3.6.2 Setting the Mapping Between the DSCP Value and VLAN Priority on the RNC

Command: SET DSCPMAP

SET DSCPMAP: DSCP=X, VLANPRI=X;

You can run the LST DSCPMAP command to query the default mapping configuration as follows:

DSCP QUEUE ID 40~63 0 32~39 1 24~31 2 16~23 3 8~15 4 0~7 5

DSCP VLAN Priority 0~7 0 8~15 1 16~23 2 24~31 3 32~39 4 40~47 5 48~55 6 56~63 7

3.6.3 Setting the Mapping Between the PHB and DSCP on the RNC

Command: SET PHBMAP

SET PHBMAP: SRN=0, SN=18, PHB=BE, DSCP=X;

You can run the LST PHBMAP command to query the default mapping configuration as follows:

PHB DSCP EF 46 AF4 AF43 38

AF42 36 AF41 34

AF3 AF33 30 AF32 28 AF31 26

AF2 AF23 22 AF22 20 AF21 18

AF1 AF13 14 AF12 12 AF11 10

BE 0

4 Configuration Example of the Iub Interface

4.1 Description



each site needs to be designed and deployed according to the actual situations.

4.2 Typical Configuration of IP Layer 2 Networking Based on MSTP 4.2.1 Networking Diagram

4.2.2 Preparations

Cables are properly connected and intermediate transmission devices are ready. The data planning is completed.

4.2.3 Networking Data Planning

I. Data Planning in the Physical Layer and Data Link Layer

II. Data Planning of the Control Plane

Data Item RNC NodeB Data Source Data on the FE port

Interface board type GOUa WMPT Internal planning IP address of the network gateway

10.10.10.10/24 10.10.10.1/24 Network planning

Whether to back up/Backup mode

Yes/Board backup+port backup

No Internal planning

Subrack No./slot No./port No.

0/18/0 0/6/0

IP address of the FE port/subnet mask


Device IP address/subnet mask

20.20.20.20/32 –

Data on the IP logic port

IP logic port No. 10 – Bandwidth of the IP logic port

40000kbps(64k*625) –

Dynamic bandwidth adjustment switch

OFF –

Data Item RNC NodeB Data Source NCP SCTPLNK No. 1 1 Data to be

negotiated Local SCTP port No. 58080 8000 Working mode of the SCTP link Server Client Subrack No./slot No. of the SPU 0/0 – DSCP 48 48 Local IP address 1 20.20.20.20/32 10.10.10.10/24 Local IP address 2 – – Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –

Whether to add the VLAN/VLAN ID YES/VLAN100 YES/VLAN100 CCP SCTPLNK No. 2 2

Local SCTP port No. 58080 8001 Working mode of the SCTP link Server Client Port No. 0 0 Subrack No./slot No. of the SPU 0/0 – DSCP 48 48 Local IP address 1 20.20.20.20/32 10.10.10.10/24 Local IP address 2 – – Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –

Whether to add the VLAN/VLAN ID YES/VLAN100 YES/VLAN100

III. Data Planning of the User Plane

4.2.4 Data Configuration on the RNC

The following blue data in the MML command needs to be planned or negotiated.

I. Data Configuration in the Physical Layer and Data Link Layer

Configure the backup information of the interface board according to the networking situation on site. ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and GOUa board in slot 19 to work in active/standby mode. Configure the backup information of the ports on the interface board according to the

networking situation on site. ADD ETHREDPORT: SRN=0, SN=18, PN=0; // Set port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 to work in active/standby mode. Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are

consistent on both ends. The MTU value on the NodeB needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;

Data Item RNC NodeB Data Source

NodeB name RNC8-BBU1 BBU1 Data to be negotiated Adjacent node ID 10 –

Transport type of the Iub interface IP IP Four IP paths of different types with different DSCP values

Port type ETH ETH Data to be negotiated IP path ID 1/2/3/4 1/2/3/4

Path type/DSCP value PHB:EF/AF43/AF23/AF13 DSCP:46/38/22/14 Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –

Local IP address/subnet mask


Whether to enable the VLAN/What the enabled VLAN ID is

YES/VLAN100 YES/VLAN100

Path detection flag ENABLE DISABLE Network planning Detected IP address 10.10.10.10/24 –

TX bandwidth (kbps) 40000 40000 RX bandwidth (kbps) 40000 40000 Whether to enable the FPMUX

NO NO

Major parameters are described as follows:

Add the IP address of the Ethernet port. The IP address is planned by the operator. ADD ETHIP: SRN=0, SN=18, PN=0, IPINDEX=0, IPADDR="10.10.10.1", MASK="255.255.255.0"; // The IP address of the interface board on the RNC is 10.10.10.1/24. Add the device IP address of the interface board (optional). The IP address is

planned by the operator or set ETHIP to service IP. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add the logic IP address 20.20.20.20 on the interface board in slot 18. The default subnet mask 255.255.255.255 is adopted. Add the IP logic port (optional). Operators need to purchase the corresponding

license. ADD IPLOGICPORT: SRN=0, SN=18, BT=GOUa, LPN=10, CARRYT=ETHER, PN=0, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, BWADJ=OFF, CIR=625, FLOWCTRLSWITCH=ON; // The logic port is on port 0 in slot 18 and the bandwidth on the port is 625 × 64 kbps = 40 Mbps,

II. Data Configuration on the Control Plane

Add SCTP signaling links (the data on the control plane). At least two SCTP links are needed; one is used to transmit the NCP data and the other is used to transmit the CCP data. The RNC acts as a server. The local IP address can be the IP address of an Ethernet port or the device IP address. In this example, the device IP address is used. The peer IP address is the IP address of an FE port of the interface board of the NodeB. The port No. is negotiated by two ends. Both the SCTP links are added to the planned IP logic port. ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=1, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="20.20.20.20", PEERIP1="10.10.10.10", PEERPN=8000, LOGPORTFLAG=YES, LOGPORTSN=18, LOGPORTNO=10, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=2, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="20.20.20.20", PEERIP1="10.10.10.10", PEERPN=8001, LOGPORTFLAG=YES, LOGPORTSN=18, LOGPORTNO=10, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;

AUTO Auto negotiation or not

Description: This parameter setting on the RNC must be consistent with that on the peer device through negotiation. That is, if this parameter is set to auto negotiation on the peer device, the parameter on the port of the RNC is also set to auto negotiation; otherwise, it is set to non-auto negotiation.

SPEED Transmission rate over the port

Description: Generally, the transmission rate over the FE port is 100 Mbit/s or 1000 Mbit/s.

DUPLEX Working mode Description: Half duplex indicates that the data packets cannot be transmitted during the receiving of data packets; full duplex indicates that the data packets can be transmitted and received at the same time. Generally, the working mode is set to full duplex.

Note: When the RNC acts as an SCTP server, you can run the SET SCTPSRVPORT command to set the local SCTP port No.. Generally, the default No. is used. You can use the LST SCTPSRVPORT command to query the default No..

Add a NodeB and algorithm parameters (data on the control plane). ADD UNODEB: NodeBName="RNC8-BBU1", NodeBId=1, SRN=0, SN=0, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; ADD UNODEBALGOPARA: NodeBName="RNC8-BBU1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1; // The algorithm switch is configured based on the data planning of the radio layer. It necessary to set corresponding parameter for the algorithm switch if turn it on. Add an adjacent node (data on the control plane).

ADD ADJNODE: ANI=10, NAME=" NODEB1", NODET=IUB, NODEBID=1, TRANST=IP; Add links on the NodeB control port (data on the control plane).

ADD UNCP: NodeBName=" RNC8-BBU1", CARRYLNKT=SCTP, SCTPLNKN=1; ADD UCCP: NodeBName=" RNC8-BBU1", PN=0, CARRYLNKT=SCTP, SCTPLNKN=2;

III. Mapping Between Transmission Resources and Configuration of the Activation Factor Table

Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. When the IP transport is applied to the Iub port, TRMMP ID is set to 1 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID.

You can run the LST TRMMAP command to query the default settings.

TRMMAP(Iub IP)

Service Type Default Primary Secondary

Common channel EF NULL IMS SRB EF NULL SRB EF NULL AMR voice EF NULL R99 CS conversational AF43 NULL R99 CS streaming AF43 NULL R99 PS conversational AF43 NULL R99 PS streaming AF43 NULL R99 PS high PRI interactive AF23 NULL R99 PS middle PRI interactive AF23 NULL

Add an activation factor table to specify proper factors for each traffic class. Through this task, the transmission resources can be multiplexed. By default, Factor Table Index is set to 0. If the default mapping cannot meet the requirements, you can use the ADD TRMFACTOR command to add an index.

You can run the LST TRMFACTOR command to query the default settings.

R99 PS low PRI interactive AF23 NULL R99 PS background AF23 NULL HSDPA Signal EF NULL HSDPA IMS Signal EF NULL HSDPA Voice AF43 NULL HSDPA conversational AF43 NULL HSDPA streaming AF43 NULL HSDPA high PRI interactive AF13 NULL HSDPA middle PRI interactive AF13 NULL HSDPA low PRI interactive AF13 NULL HSDPA background AF13 NULL HSUPA Signal EF NULL HSUPA IMS Signal EF NULL HSUPA Voice AF43 NULL HSUPA conversational AF43 NULL HSUPA streaming AF43 NULL HSUPA high PRI interactive AF13 NULL HSUPA middle PRI interactive AF13 NULL HSUPA low PRI interactive AF13 NULL HSUPA background AF13 NULL

TRMFACTOR Service Type Default Factor (%) General common channel service downlink 70 General common channel service uplink 70 IMS SRB service downlink 15 IMS SRB service uplink 15 MBMS common channel service downlink 100 SRB service downlink 15 SRB service uplink 15 AMR voice service downlink 70 AMR voice service uplink 70 R99 CS conversational service downlink 100 R99 CS conversational service uplink 100 R99 CS streaming service downlink 100 R99 CS streaming service uplink 100

Configure the TRM mapping on the adjacent node. You can run the ADD TRMMAP command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=1, TMISLV=1, TMIBRZ=1, FTI=0; // In this example, both TMI and FTI use default values.

IV. Data Configuration on the User Plane

Configure the IP route to the interface of the NodeB on the Iub interface board of the RNC. In layer 2 networking, the IP route is not configured for the interface IP address of the RNC is in the same network segment as that of the NodeB. Add IP paths. The traffic unit is kbps. The Transmission Configuration Specifications

recommends four IP paths with four priorities. You can run the LST PHBMAP command to query the DSCP value corresponding to the PHB of each IP path. ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=EF, IPADDR="20.20.20.20", PEERIPADDR="10.10.10.10", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.10.10.10"; // When the PHB is EF, the DSCP value is 46. ADD IPPATH: ANI=10, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF43,

R99 PS conversational service downlink 70 R99 PS conversational service uplink 70 R99 PS streaming service downlink 100 R99 PS streaming service uplink 100 R99 PS interactive service downlink 100 R99 PS interactive service uplink 100 R99 PS background service downlink 100 R99 PS background service uplink 100 HSDPA signal downlink 50 HSDPA IMS signal downlink 15 HSDPA voice service downlink 70 HSDPA conversational service downlink 70 HSDPA streaming service downlink 100 HSDPA interactive service downlink 100 HSDPA background service downlink 100 HSUPA signal uplink 50 HSUPA IMS signal uplink 15 HSUPA voice service uplink 70 HSUPA conversational service uplink 70 HSUPA streaming service uplink 100 HSUPA interactive service uplink 100 HSUPA background service uplink 100 EFACH channel forward 20

IPADDR="20.20.20.20", PEERIPADDR="10.10.10.10", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.10.10.10"; // When the PHB is AF43, the DSCP value is 38. ADD IPPATH: ANI=10, PATHID=3, ITFT=IUB, TRANST=IP, PATHT= AF23, IPADDR="20.20.20.20", PEERIPADDR="10.10.10.10", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.10.10.10"; // When the PHB is AF23, the DSCP value is 22. ADD IPPATH: ANI=10, PATHID=4, ITFT=IUB, TRANST=IP, PATHT= AF13, IPADDR="20.20.20.20", PEERIPADDR="10.10.10.10", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.10.10.10"; // When the PHB is AF13, the DSCP value is 14.

V. VLAN/VLAN Priority/DSCP Configuration

VLAN Configuration Generally, the VLAN ID needs to be configured in layer 2 networking. In this example, the VLAN ID is set to 100 between the RNC and NodeB1. ADD VLANID: SRN=0, SN=18, IPADDR="10.10.10.10", VLANID=100; // On the RNC, the VLAN ID is set to 100 for the next hop. In layer 2 networking, the interface IP address of NodeB1 is the next hop of the RNC. Note: The VLAN needs to be configured on the intermediate transmission device. If the VLAN ID can be added on the peer transmission device, the VLAN configuration is unnecessary on the RNC. DSCP Configuration

According to the planning of the existing network, see section 3.4 for DSCP values of various services. Note: DSCP values need to be configured on intermediate transmission devices. VLAN Priority Configuration

According to the planning of the existing network, see section 3.5 for VLAN priorities of various services. Note: VLAN priorities need to be configured on the intermediate transmission devices.

VI. IP Route Configuration

4.2.5 Data Configuration on the NodeB

Note

During the deployment on site, the data on the NodeB is configured by using the CME. For clear configuration description, here only describes the configuration related to MML commands. The contents in blue in the following MML commands need to be planned or negotiated.

I. Data Configuration in the Physical Layer

Set the attributes of the Ethernet ports. Ensure that Ethernet port attributes are consistent on both ends. The MTU value on the NodeB needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 .

SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE; // If the interface IP address on the NodeB is in the same network segment as that of the OM IP address, ARPPROXY is set to Enable. Add the IP address of the Ethernet port. The IP address of the FE port on the NodeB

is 10.10.10.10/24. ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.10.10.10", MASK="255.255.255.0";


At least add two SCTP links; one is used to transmit the NCP data and the other is used to transmit the CCP data. ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="10.10.10.10", LOCPORT=8000, PEERIP="20.20.20.20", PEERPORT=58080; ADD SCTPLNK: SCTPNO=2, SRN=0, SN=6, LOCIP="10.10.10.10", LOCPORT=8001, PEERIP="20.20.20.20", PEERPORT=58080; Add links on the NodeB control port.

ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1; ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2;

III. Data Configuration on the User Plane

Add four IP paths with different priorities. Ensure that the configuration is consistent with that on the RNC. The ping detection switch on the IP path on the NodeB is disabled.

ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="10.10.10.10", RNCIP="20.20.20.20", DSCP=46, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;




IV. VLAN/VLAN Priority/DSCP Configuration

VLAN Configuration Generally, the VLAN ID needs to be configured in layer 2 networking. In this example, the VLAN ID is set to 100 between the RNC and NodeB1. Method I: All packets from the NodeB to the network gateway carry the same VLAN ID and have the same VLAN priority. ADD VLANMAP: NEXTHOPIP="GW2", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=1; // Set the VLAN mode to SINGLEVLAN and the IP address of the network gateway on the NodeB to GW2. Set

the VLAN ID to 100 and VLAN priority to 4 for all packets to this network gateway. Method 2: Add the same VLAN ID for all packets from the NodeB to the network gateway. Assign different VLAN priorities to different traffic. ADD VLANMAP: NEXTHOPIP="10.10.10.1", VLANMODE=VLANGROUP, VLANGROUPNO=0; // Set the VLAN mode to VLANGROUP. Set the VLAN ID and VLAN priority of the traffic by using the SET VLANCLASS command. For the specific VLAN ID setting, see sections 3.3.2 –3.3.7 . Note: The VLAN needs to be configured on the intermediate transmission device. If the VLAN ID can be added on the peer transmission device, the VLAN configuration is unnecessary on the RNC. The VLAN needs to be configured on the intermediate transmission device. DSCP Configuration

According to the planning of the existing network, see section 3.4 for DSCP values of various services. Note: DSCP values need to be configured on the intermediate transmission device. VLAN Priority Configuration

According to the planning of the existing network, see section 3.5 for VLAN priorities of various services. Note: VLAN priorities need to be configured on the intermediate transmission devices.

V. IP Route Configuration

Configure the IP route to the device IP address of the RNC on the WMPT of the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="20.20.20.20", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.10.10.1"; // In this case, the device IP address serves the IP address for the traffic on the RNC. Therefore, add this route on the NodeB. The next hop is the interface IP address of the RNC.

4.3 Typical Configuration of IP Layer 3 Networking Based on the Data Network 4.3.1 Networking Diagram

4.3.2 Preparations


4.3.3 Data Planning of Layer 3 Networking




Interface board type GOUa WMPT Internal planning IP address of the network gateway






0/18/0 0/6/0




20.20.20.20/32 –


IP logical port No. 10 – Bandwidth of the IP logic port

40000kbps(64k*625)

–


OFF –


NCP

SCTKLNK No. 1 1 Data to be negotiated Local SCTP port No. 58080 8000

Working mode of the SCTP link Server Client Subrack No./slot No. of the SPU

0/0 –

DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/24 Local IP address 2 – – Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –

Whether to add the VLAN/VLAN ID

NO YES/VLAN200

SCTPLNK No. 2 2 Local SCTP port No. 58080 8001 Working mode of the SCTP link Server Client Port No. 0 0 Subrack No./slot No. of the 0/0 –



I. Data Configuration on the Physical Layer and Data Link Layer

The configuration on the RNC is the same as that of the layer 2 on the Iub interface. For details, see section 4.2.4 .


Add SCTP signaling links (data on the control plane). At least two SCTP links are needed; one is used to transmit the NCP data and the other is used to transmit the

CCP

SPU DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/24 Local IP address 2 – – Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –


NO YES/VLAN200

Data Item RNC NodeB Data Source NodeB name RNC8-BBU1 BBU1 Data to be

negotiated Adjacent node ID 10 – Transport type of the Iub interface IP IP

Four IP paths of different path types with different DSCP values

Port type ETH ETH Data to be negotiated IP path ID 1/2/3/4 1/2/3/4

Path type/DSCP value

PHB:EF/AF43/AF23/AF13 DSCP:46/38/22/14

Whether to bind the IP logic port/slot No. and port No. of the logic port

Yes/18/10 –



Whether to enable the VLAN/enabled VLAN ID

NO YES/VLAN200

Path detection flag ENABLE DISABLE Network planning Detected IP address 40.40.40.40/24 –


NO NO

CCP data. The RNC acts as a server. The local IP address can be the IP address of an Ethernet port or the device IP address. In this example, the device IP address is used. The peer IP address is the IP address of an FE port of the interface board of the NodeB. The port No. is negotiated by two ends. Two SCTP links are added to the planned IP logic port. ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=1, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="20.20.20.20", PEERIP1="40.40.40.40", PEERPN=8000, LOGPORTFLAG=YES, LOGPORTSN=18, LOGPORTNO=10, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=2, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="20.20.20.20", PEERIP1="40.40.40.40", PEERPN=8001, LOGPORTFLAG=YES, LOGPORTSN=18, LOGPORTNO=10, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; Note: When the RNC acts as an SCTP server, you can run the SET SCTPSRVPORT command to set the local SCTP port No.. Generally, the default No. is used. You can use the LST SCTPSRVPORT command to query the default No..

Add a NodeB and algorithm parameters (data on the control plane). ADD UNODEB: NodeBName="RNC8-BBU1", NodeBId=1, SRN=0, SN=0, TnlBearerType=IP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; ADD UNODEBALGOPARA: NodeBName="RNC8-BBU1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1; // The algorithm switch is configured based on the data planning of the radio layer. Add an adjacent node (data on the control plane).

ADD ADJNODE: ANI=10, NAME=" NODEB1", NODET=IUB, NODEBID=1, TRANST=IP; Add links on the NodeB control port (data on the control plane).



Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. When the IP transport is applied to the Iub port, TRMMP ID is set to 1 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID. See section 4.2.4 . Add an activation factor table to specify proper factors for each traffic class. Through

this task, the transmission resources can be multiplexed. By default, Factor Table Index is set to 0. If the default mapping cannot meet the requirements, you can use the ADD TRMFACTOR command to add an index. See section 4.2.4 . Configure the TRM mapping on the adjacent node. You can run the ADD TRMMAP

command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=1, TMISLV=1, TMIBRZ=1, FTI=0; // In this example, both TMI and FTI use default values.


According to the planning on site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). Configure the IP route to the interface IP address of the NodeB on the Iub interface board of the RNC. ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP="10.10.10.2", PRIORITY=HIGH, REMARK="RNC INT To NodeB1"; // Configure the host route to the interface IP address of NodeB1. Add IP paths. The traffic unit is kbps. The Transmission Configuration Specifications

recommends four IP paths with four priorities. You can run the LST PHBMAP command to query the DSCP value corresponding to the PHB of each IP path. ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=EF, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the PHB is EF, the DSCP value is 46. ADD IPPATH: ANI=10, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF43, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the PHB is AF43, the DSCP value is 38. ADD IPPATH: ANI=10, PATHID=3, ITFT=IUB, TRANST=IP, PATHT= AF23, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the PHB is AF23, the DSCP value is 22. ADD IPPATH: ANI=10, PATHID=4, ITFT=IUB, TRANST=IP, PATHT= AF13, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the PHB is AF13, the DSCP value is 14.


VLAN Configuration

If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC.

If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID for the next hop (VRRP Virtual IP) of the RNC.

Note: The VLAN needs to be configured on the intermediate transmission device.

DSCP Configuration

According to the planning of the existing network, see section 3.3 for DSCP values of various services.

Note: DSCP values need to be configured on the intermediate transmission device.

VLAN Priority Configuration

If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured.

If VLAN priorities need to be configured on the RNC, see section 3.4 according to the planning of the existing network.

Note: VLAN priorities need to be configured on the intermediate transmission devices.


Note

During the deployment on site, the data on the NodeB is configured by using the CME. For clear configuration description, here only describes the configuration related to MML commands.

The contents in blue in the following MML commands need to be planned or negotiated.

I. Data Configuration in the Physical Layer

Set attributes of Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the NodeB needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE; // If the interface IP address of the NodeB is on the same network segment as that of the OM IP address, set ARP Proxy to Enable. Add the IP address of the Ethernet port. The IP address of the FE port on the NodeB

is 10.10.10.10/24. ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="40.40.40.40", MASK="255.255.255.0";


At least, add two SCTP links; one is used to transmit the NCP data and the other is used to transmit the CCP data.

ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="10.10.10.10", LOCPORT=8000, PEERIP="20.20.20.20", PEERPORT=58080;

ADD SCTPLNK: SCTPNO=2, SRN=0, SN=6, LOCIP="10.10.10.10", LOCPORT=8001, PEERIP="20.20.20.20", PEERPORT=58080;

Add links on the NodeB control port.

ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1;

ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2;


Add four IP paths with different priorities. Ensure that the configuration is consistent

with that on the RNC. The ping detection switch on the IP path on the NodeB is disabled. ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=46, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=38, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=22, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=14, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;


VLAN Configuration In layer 3 networking, the NodeB may first connect to a layer 2 network. In this case, a VLAN ID needs to be configured on the NodeB. In this example, the VLAN ID is set to 200 on the NodeB. ADD VLANMAP: NEXTHOPIP="40.40.40.39", VLANMODE=VLANGROUP, VLANGROUPNO=0; // Configure a VLAN group to the network gateway on the NodeB. For the specific VLAN ID setting, see sections 3.3.2 –3.3.7 . Note: The VLAN needs to be configured on the intermediate transmission device. If the VLAN ID can be added on the peer transmission device, the VLAN configuration is unnecessary on the RNC. DSCP Configuration

According to the planning of the existing network, see section 3.4 for DSCP values of various services.

Note: DSCP values need to be configured on the intermediate transmission devices.


According to the planning of the existing network, see section 3.5 for VLAN priorities of various services.



According to the planning on site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255).

Configure the IP route to the RNC on the WMPT of the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="20.20.20.20", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the device IP address of the RNC for the device IP

address serve as the IP address for the traffic on the RNC. Configure the IP route to the Ethernet port of the RNC on the WMPT of the NodeB.

It is optional. To facilitate the commissioning, the route needs to be configured when you need to ping the IP address of the Ethernet port on the RNC from the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.10.10.1", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the interface IP address of the RNC.

4.4 Typical Configuration of Hybrid Transport Networking

4.4.1 Networking Diagram

The hybrid transport can be planned on site based on the path on which each service is transmitted.

For the signaling, real-time service, and R99 PS, the IP over SDH is preferred; for the HSPA BE service, the IP over Ethernet over Iub OMCH is preferred.

4.4.2 Preparations


4.4.3 Data Planning of the Hybrid Transport Networking


Data Item RNC NodeB Data Source Interface board type GOUa WMPT Internal planning IP address of the network gateway



Yes/Board backup+port



Data on the FE port

backup Subrack No./slot No./port No.

0/18/0 0/6/0




20.20.20.20/32 –


IP logical port No. 10 – Bandwidth of the IP logic port

40000kbps(64k*625)

–


OFF –

PPP/MLPPP link data

Interface board type POUa WMPT Internal planning IP address of the network gateway

– –

Subrack No./Slot No./Port No.

0/14/0,1,2 0/6/0,1,2

MPGRP group No. 0 0 MPLNK No. 0/1/2 0/1/2 Local IP address/subnet mask


Bearer timeslot TS1–TS31 TS1–TS31 Data to be negotiated


NCP

SCTPLNK No. 1 1 Data to be negotiated Local SCTP port No. 58080 8000

Working mode of the SCTP link Server Client Subrack No./slot No. of the SPU 0/0 – DSCP 48 48 Local IP address 1 13.13.13.1/24 13.13.13.2/24 Local IP address 2 – – Whether to add the VLAN/VLAN ID

NO NO

CCP

SCTPLNK No. 2 2

Local SCTP port No. 58080 8001

Working mode of the SCTP link Server Client

Port No. 0 0 Subrack No./slot No. of the SPU 0/0 – DSCP 48 48 Local IP address 1 13.13.13.1/24 13.13.13.2/24


Local IP address 2 – – Whether to add the VLAN/VLAN ID

NO NO

Data Item RNC NodeB Data Source NodeB name RNC8-BBU1 BBU1 Data to be

negotiated Adjacent node ID 10 – Transport type of the Iub interface HYBRID_IP HYBRID_IP

Four IP paths are carried on MP.

Port type MP MP Data to be negotiated IP path ID 1/2/3/4 1/2/3/4

Path type/DSCP value PHB:EF/AF43/AF23/AF13 DSCP:46/38/22/14 Local IP address/subnet mask



NO NO

Path detection flag ENABLE DISABLE Detected IP address 13.13.13.2/24 –


NO NO

Four IP paths are carried on the GE.

Port type ETH ETH Data to be negotiated

IP path ID 5/6/7/8 5/6/7/8 Path type/DSCP value PHB:LQ_EF/ LQ_AF43/

LQ_AF23/ LQ_AF13 DSCP:46/38/22/14


Yes/18/10 –




NO YES/VLAN200

Path detection flag ENABLE DISABLE Detected IP address 40.40.40.40/24 – TX bandwidth (kbps) 40000 40000

RX bandwidth (kbps) 40000 40000

Whether to enable the FPMUX

NO NO



Configure the backup information of the interface board according to the networking situation on site.

ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and GOUa board in slot 19 to work in active/standby mode.

ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=POUa, SN=14, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the POUa board in slot 14 of subrack 0 and POUa board in slot 15 to work in active/standby mode.

Configure the backup information of the ports on the interface board according to the networking situation on site.

ADD ETHREDPORT: SRN=0, SN=18, PN=0; //Port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 are configured to work in active/standby mode.

SET MSP: SRN=0, SN=14, PN=0, RT=REVERTIVE, K2MODE=NOT-INDICATE-END, SDSFPRI=HIGH, MODE=MODE3; // Port 0 on the POUa in slot 14 of subrack 0 and port 0 on the POUa in slot 15 are configured to work in MSP mode. Ensure that settings of interconnection parameters are consistent on both ends through negotiation.

Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the RNC needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;


Run the following command to add the IP address of the Ethernet port. The IP address is planned by the operator. ADD ETHIP: SRN=0, SN=18, PN=0, IPINDEX=0, IPADDR="10.10.10.1", MASK="255.255.255.0"; // The IP address of the interface board on the RNC is 10.10.10.1/24. Add the device IP address of the interface board (optional) on the GOUa. The IP






address is planned by the operator. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add the logic IP address 20.20.20.20 on the interface board in slot 18. The default subnet mask 255.255.255.255 is adopted. Add the IP logic port (optional) on the interface board of the GOUa. Operators need

to purchase the corresponding license. ADD IPLOGICPORT: SRN=0, SN=18, BT=GOUa, LPN=10, CARRYT=ETHER, PN=0, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, BWADJ=OFF, CIR=625, FLOWCTRLSWITCH=ON; // The logic port is on port 0 in slot 18 and the bandwidth on the port is 625 × 64 kbps = 40 Mbps. Set attributes of the optical ports on the POUa. Ensure that the attribute values are

consistent on both ends. You can run the LST OPT command to query the default attribute values. If the default values can meet the requirements, additional configuration is unnecessary. SET OPT: SRN=0, SN=14, BT=POUa, PS=SINGLE, PN=0, LNKNUMMODE=HUAWEI_MODE, J0TXT=NULL, J0RXT=NULL, J1TXT=NULL, J1RXT=NULL, S1VALUE=1, JAUTOADD=ZERO; Set attributes of the E1 cables on the POUa. Ensure that the attribute values are

consistent on both ends. You can run the LST E1T1 command to query the default attribute values. If the default values can meet the requirements, additional configuration is unnecessary. SET E1T1: SRN=0, SN=14, BT=POUa, PS=SINGLE, PN=0, PTTYPE=E1_CRC4_MULTI_FRAME; SET E1T1: SRN=0, SN=14, BT=POUa, PS=SINGLE, PN=1, PTTYPE=E1_CRC4_MULTI_FRAME; SET E1T1: SRN=0, SN=14, BT=POUa, PS=SINGLE, PN=2, PTTYPE=E1_CRC4_MULTI_FRAME; Add MP groups and MP links.

ADD MPGRP: SRN=0, SN=14, BRDTYPE=POUa, MPGRPN=0, MPTYPE=MCPPP, BORROWDEVIP=NO, LOCALIP="13.13.13.1", MASK="255.255.255.0", PEERIP="13.13.13.2", MHF=LONG, PPPMUX=Disable, PFC=Enable, ACFC=Enable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF, ANTIERRFLAG=OFF; ADD MPLNK: SRN=0, SN=14, BRDTYPE=POUa, MPGRPN=0, PPPLNKN=0, DS1=0, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1; ADD MPLNK: SRN=0, SN=14, BRDTYPE=POUa, MPGRPN=0, PPPLNKN=1, DS1=1, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1; ADD MPLNK: SRN=0, SN=14, BRDTYPE=POUa, MPGRPN=0, PPPLNKN=2, DS1=2, TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;


Add SCTP signaling links (data on the control plane). At least two SCTP links are needed; one is used to transmit the NCP data and the other is used to transmit the

CCP data. The RNC acts as a server. The local IP address can be the IP address of an Ethernet port or the device IP address. In this example, the device IP address is used. The peer IP address is the IP address of an FE port of the interface board of the NodeB. The port No. is negotiated by two ends. ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=1, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="13.13.13.1", PEERIP1="13.13.13.2", PEERPN=8000, LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=2, MODE=SERVER, APP=NBAP, DSCP=48, LOCIP1="13.13.13.1", PEERIP1="13.13.13.2", PEERPN=8001, LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; Note: When the RNC acts as an SCTP server, you can run the SET SCTPSRVPORT command to set the local SCTP port No.. Generally, the default No. is used. You can use the LST SCTPSRVPORT command to query the default No..

Add a NodeB and algorithm parameters (data on the control plane). ADD UNODEB: NodeBName="RNC8-BBU1", NodeBId=1, SRN=0, SN=0, TnlBearerType=HYBRID_IP_TRANS, IPTRANSAPARTIND=SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; ADD UNODEBALGOPARA: NodeBName="RNC8-BBU1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1; // The algorithm switch is configured based on the data planning of the radio layer. It’s necessary to configure parameters corresponding to a specific algorithm switch if it is turned on. Add an adjacent node (data on the control plane).

ADD ADJNODE: ANI=10, NAME=" NODEB1", NODET=IUB, NODEBID=1, TRANST=HYBRID_IP; Add links on the NodeB control port (data on the control plane).



Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. When the IP transport is applied to the Iub port, TRMMP ID is set to 1 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID.


TRMMAP(Iub Hybrid IP)


Common channel EF LQEF

Add an activation factor table to specify proper factors for each traffic class. Through this task, the transmission resources can be multiplexed. By default, Factor Table Index is set to 0. If the default mapping cannot meet the requirements, you can use the ADD TRMFACTOR command to add an index. See section 4.2.4 . Configure the threshold table for load balancing between active and standby paths.

You can run the LST LOADEQ command (LOADEQ ID = 0) to obtain the default threshold table. If the default mapping cannot meet the requirement, you can run the ADD LOADEQ command to add an index. In this example, the default mapping is used.

Generally, the active path is preferred to carry the load. If the following conditions are met, the standby path is preferred.

IMS SRB EF LQEF SRB EF LQEF AMR voice EF LQEF R99 CS conversational AF43 LQAF43 R99 CS streaming AF43 LQAF43 R99 PS conversational AF43 LQAF43 R99 PS streaming AF43 LQAF43 R99 PS high PRI interactive AF23 LQAF23 R99 PS middle PRI interactive AF23 LQAF23 R99 PS low PRI interactive AF23 LQAF23 R99 PS background AF23 LQAF23 HSDPA Signal EF LQEF HSDPA IMS Signal EF LQEF HSDPA Voice AF43 LQAF43 HSDPA conversational AF43 LQAF43 HSDPA streaming AF43 LQAF43 HSDPA high PRI interactive LQAF13 AF13 HSDPA middle PRI interactive LQAF13 AF13 HSDPA low PRI interactive LQAF13 AF13 HSDPA background LQAF13 AF13 HSUPA Signal EF LQEF HSUPA IMS Signal EF LQEF HSUPA Voice AF43 LQAF43 HSUPA conversational AF43 LQAF43 HSUPA streaming AF43 LQAF43 HSUPA high PRI interactive LQAF13 AF13 HSUPA middle PRI interactive LQAF13 AF13 HSUPA low PRI interactive LQAF13 AF13 HSUPA background LQAF13 AF13

The load on the active path is greater than the load threshold of this path. The load on the active path times the threshold for the ratio of the load on the active path to the load on the standby path is greater than the load on the standby path.

Configure the TRM mapping on the adjacent node. You can run the ADD TRMMAP command to add the TRMMAP ID for the gold, silver, and bronze users.

Service Type

Default

Load Threshold of the Active Path (%)

Threshold for the Ratio of the Load on the Active Path to the Load on the Standby Path (%)

Common channel 100 0 IMS SRB 100 0 SRB 100 0 AMR voice 100 0 R99 CS conversational 100 0 R99 CS streaming 100 0 R99 PS conversational 100 0 R99 PS streaming 100 0 R99 PS high PRI interactive 30 100 R99 PS middle PRI interactive 30 100 R99 PS low PRI interactive 30 100 R99 PS background 30 100 HSDPA Signal 100 0 HSDPA IMS Signal 100 0 HSDPA Voice 100 0 HSDPA conversational 100 0 HSDPA streaming 100 0 HSDPA high PRI interactive 30 100 HSDPA middle PRI interactive 30 100 HSDPA low PRI interactive 30 100 HSDPA background 30 100 HSUPA Signal 100 0 HSUPA IMS Signal 100 0 HSUPA Voice 100 0 HSUPA conversational 100 0 HSUPA streaming 100 0 HSUPA high PRI interactive 30 100 HSUPA middle PRI interactive 30 100 HSUPA low PRI interactive 30 100 HSUPA background 30 100

ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=HYBRID_IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=3, TMISLV=3, TMIBRZ=3, FTI=0, LEIGLD=0, LEISLV=0, LEIBRZ=0;


Configure the IP route to the interface IP address of the NodeB on the Iub interface board of the RNC. According to the planning on site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP="10.10.10.2", PRIORITY=HIGH, REMARK="RNC INT To NodeB1"; // Configure the host route to the interface IP address of NodeB1. The route does not need to be configured on the Iub interface board of the POUa on the RNC for IP addresses of both MP ends are on the same network segment. Add IP paths. The traffic unit is kbps. The Transmission Configuration Specifications

recommends four IP paths with four priorities. You can run the LST PHBMAP command to query the DSCP value corresponding to the PHB of each IP path. ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=HYBRID_IP, PATHT=EF, IPADDR="13.13.13.1", PEERIPADDR="13.13.13.2", PEERMASK="255.255.255.255", TXBW=5952, RXBW=5952, CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="13.13.13.2"; // When the PHB is EF, the DSCP value is 46. The data is transmitted in IP over SDH mode. ADD IPPATH: NI=10, PATHID=2, ITFT=IUB, TRANST=HYBRID_IP, PATHT=AF43, IPADDR="13.13.13.1", PEERIPADDR="13.13.13.2", PEERMASK="255.255.255.255", TXBW=5952, RXBW=5952, CARRYFLAG= NULL, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="13.13.13.2"; // When the PHB is AF43, the DSCP value is 38. The data is transmitted in IP over SDH mode. ADD IPPATH: ANI=10, PATHID=3, ITFT=IUB, TRANST=HYBRID_IP, PATHT=AF23, IPADDR="13.13.13.1", PEERIPADDR="13.13.13.2", PEERMASK="255.255.255.255", TXBW=5952, RXBW=5952, CARRYFLAG= NULL, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="13.13.13.2"; // When the PHB is AF23, the DSCP value is 22. The data is transmitted in IP over SDH mode. ADD IPPATH: ANI=10, PATHID=4, ITFT=IUB, TRANST=HYBRID_IP, PATHT=AF13, IPADDR="13.13.13.1", PEERIPADDR="13.13.13.2", PEERMASK="255.255.255.255", TXBW=5952, RXBW=5952, CARRYFLAG= NULL, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="13.13.13.2"; // When the PHB is AF13, the DSCP value is 14. The data is transmitted in IP over SDH mode. ADD IPPATH: ANI=10, PATHID=5, ITFT=IUB, TRANST=HYBRID_IP, PATHT= LQ_EF, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When PATH Type is set to LQ_EF, the DSCP value is 46. The data is transmitted in IP over Ethernet mode. ADD IPPATH: ANI=10, PATHID=6, ITFT=IUB, TRANST=HYBRID_IP, PATHT= LQ_AF43, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When PATH Type is set to LQ_AF13, the DSCP value is 38. The data is transmitted in IP over Ethernet mode. ADD IPPATH: ANI=10, PATHID=7, ITFT=IUB, TRANST=HYBRID_IP, PATHT=

LQ_AF23, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When PATH Type is set to LQ_AF23, the DSCP value is 22. The data is transmitted in IP over Ethernet mode. ADD IPPATH: ANI=10, PATHID=8, ITFT=IUB, TRANST=HYBRID_IP, PATHT= LQ_AF13, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When PATH Type is set to LQ_AF13, the DSCP value is 14. The data is transmitted in IP over Ethernet mode.


VLAN Configuration − IP over Ethernet: If the RNC directly connects to the router in layer 3 networking,

the VLAN ID is not configured on the RNC. If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID for the next hop (VRRP Virtual IP) of the RNC.

− IP over SDH: The VLAN is not configured. Note: The VLAN needs to be configured on the intermediate transmission device. DSCP Configuration

According to the planning of the existing network, see section 3.3 for DSCP values of various services. Note: DSCP values need to be configured on the intermediate transmission device. VLAN Priority Configuration − IP Over Ethernet: If the RNC directly connects to the router in layer 3 networking,

the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured. If VLAN priorities need to be configured on the RNC, see section 3.4 according to the planning of the existing network.

− IP over SDH: The VLAN is not configured. Note: VLAN priorities need to be configured on the intermediate transmission devices.


Note




Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the NodeB needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE; // If the interface IP address of the NodeB is on the same network segment as that of the OM IP address, set ARP Proxy to Enable.

Add the IP address of the Ethernet port. The IP address of the FE port on the NodeB is 40.40.40.40/24. ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="40.40.40.40", MASK="255.255.255.0"; Set the bearer mode of the E1/T1 cables to IPV4. Then, reset the transmission

interface board. SET E1T1BEAR: SRN=0, SN=6, MODE=IPV4; Set attributes of the E1 cables on the WMPT. Ensure that the attribute values are

consistent on both ends. You can run the DSP E1T1WORKMODE command to query the attribute values. SET E1T1WORKMODE: SRN=0, SN=6, SBT=BASE_BOARD, FRAME=E1_CRC4_MULTI_FRAME, LNCODE=HDB3, CLKM=MASTER; Add MP groups and MP links.

ADD MPGRP: SRN=0, SN=6, SBT=BASE_BOARD, MPGRPN=0, AUTH=NONAUTH, LOCALIP="13.13.13.2", IPMASK="255.255.255.0", PEERIP="13.13.13.1", IPHC=ENABLE; ADD MPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=0, MPGRPSBT=BASE_BOARD, MPGRPN=0, E1T1SRN=0, E1T1SN=6, E1T1SBT=BASE_BOARD, E1T1PN=0, TSN=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&TS15&TS16&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24&TS25&TS26&TS27&TS28&TS29&TS30&TS31, PFC=ENABLE, ACFC=ENABLE; ADD MPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=1, MPGRPSBT=BASE_BOARD, MPGRPN=0, E1T1SRN=0, E1T1SN=6, E1T1SBT=BASE_BOARD, E1T1PN=1, TSN=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&TS15&TS16&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24&TS25&TS26&TS27&TS28&TS29&TS30&TS31, PFC=ENABLE, ACFC=ENABLE; ADD MPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=2, MPGRPSBT=BASE_BOARD, MPGRPN=0, E1T1SRN=0, E1T1SN=6, E1T1SBT=BASE_BOARD, E1T1PN=1, TSN=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&TS15&TS16&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24&TS25&TS26&TS27&TS28&TS29&TS30&TS31, PFC=ENABLE, ACFC=ENABLE;


At least, add two SCTP links; one is used to transmit the NCP data and the other is used to transmit the CCP data. ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="13.13.13.2", LOCPORT=8000, PEERIP="13.13.13.1", PEERPORT=58080; ADD SCTPLNK: SCTPNO=2, SRN=0, SN=6, LOCIP="13.13.13.2", LOCPORT=8001, PEERIP="13.13.13.1", PEERPORT=58080; Add links on the NodeB control port.

ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1; ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2;


Add IP paths. Configure four IP paths with different priorities in IP over SDH mode; configure four IP paths with different priorities in IP over Ethernet mode. The configuration must be consistent with that on the RNC. The ping detection switch on the IP path on the NodeB is disabled. ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT= MPGRP, PN=0, JNRSCGRP=DISABLE, NODEBIP="13.13.13.2",

RNCIP="13.13.13.1", DSCP=46, RXBW=5952, TXBW=5952, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT= MPGRP, PN=0, JNRSCGRP=DISABLE, NODEBIP="13.13.13.2", RNCIP="13.13.13.1", DSCP=38, RXBW=5952, TXBW=5952, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT= MPGRP, PN=0, JNRSCGRP=DISABLE, NODEBIP="13.13.13.2", RNCIP="13.13.13.1", DSCP=22, RXBW=5952, TXBW=5952, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=4, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT= MPGRP, PN=0, JNRSCGRP=DISABLE, NODEBIP="13.13.13.2", RNCIP="13.13.13.1", DSCP=14, RXBW=5952, TXBW=5952, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=5, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=46, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=6, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=38, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=7, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=22, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=8, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=14, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;


VLAN Configuration − IP Over Ethernet

In layer 3 networking, the NodeB may first connect to a layer 2 network. In this case, the VLAN ID is configured on the NodeB. In this example, set the VLAN ID to 200 on the NodeB. ADD VLANMAP: NEXTHOPIP="40.40.40.39", VLANMODE=VLANGROUP, VLANGROUPNO=0; // Configure a VLAN group to the network gateway on the NodeB. For the specific VLAN ID setting, see sections 3.3.2 –3.3.7 .

− IP over SDH: The VLAN is not configured. Note: The VLAN needs to be configured on the intermediate transmission device.

DSCP Configuration According to the planning of the existing network, see section 3.3 for DSCP values of various services. Note: DSCP values need to be configured on the intermediate transmission device. VLAN Priority Configuration − IP Over Ethernet

For VLAN priorities of various services, see section 3.4 according to the planning

of the existing network. IP over SDH: The VLAN is not configured.




Configure the IP route to the device IP address of the RNC on the WMPT of the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="20.20.20.20", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the device IP address of the RNC for the device IP address serve as the IP address for the traffic on the RNC in this example. Configure the IP route to the Ethernet port of the RNC on the WMPT of the NodeB.

It is optional. To facilitate the commissioning, the route needs to be configured when you need to ping the IP address of the Ethernet port on the RNC from the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.10.10.1", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the interface IP address of RNC. The route does not need to be configured on the interface board of the NodeB for IP

addresses of both MP ends are on the same network segment.

4.5 Typical Configuration of the Dual-Stack-Based Networking 4.5.1 Networking Diagram

The dual stack transport can be planned on site based on the path on which each service is transmitted.

For the signaling, real-time service, and R99 PS, the ATM networking is preferred; for the

HSPA BE service, the Iub OMCH over IP over Ethernet is preferred.

4.5.2 Preparations


4.5.3 Data Planning of the Dual Stack Transport Networking




Interface board type

GOUa WMPT Internal planning

IP address of the network gateway





Subrack No./Slot No./Port No.

0/18/0 0/6/0




20.20.20.20/32 –


IP logic port No. 10 – Bandwidth of the IP logic port

40000kbps(64k*625)

–


OFF –

IMA link data

Interface board type

UOIa WMPT Internal planning

Subrack No./slot No./optical port No.

0/14/0 0/6/0,1,2

IMA group No. – 0

IMA link No. – 0/1/2 Data of the ATM logic port

ATM logic port No. 20 –

Bandwidth of the ATM logic port

5712kbps –



NCP Subrack No./slot No. of the SPU

0/0 –

Carried VPI/VCI 10/34 1/34 TX traffic type CBR CBR TR traffic type CBR CBR Bearer link type SAAL SAAL

CCP Subrack No./slot No. of the SPU

0/0 –

Carried VPI/VCI 10/35 1/35

TX traffic type CBR CBR TR traffic type CBR CBR Bearer link type SAAL SAAL

ALCAP Subrack No./slot No. of the SPU

0/0 –

Carried VPI/VCI 10/36 1/36 TX traffic type CBR CBR TR traffic type CBR CBR

Bearer link type SAAL SAAL


NodeB name RNC8-BBU1 BBU1 Data to be negotiated Adjacent node ID 10 10

Transport type of the Iub interface ATM_IP ATM_IP Five AAL2 paths

Port type NCOPT IMA Data to be negotiated AAL2 path identifier 1/2/3/4/5 1/2/3/4/5

Path type Three RT_VBRs, one NRT_VBR, and one UBR

Three RT_VBRs, one NRT_VBR, and one UBR

Whether to bind the ATM logic port/slot No. and port No. of the logic port

Yes/14/20 – Network planning

Subrack No./slot No. 0/14/0 0/7/0 VPI/VCI 10/40,10/41,10/42,

10/43,10/44 1/40,1/41,1/42,1/43,1/44

Four IP paths are carried on the GE.

Port type ETH ETH Data to be negotiated

IP path ID 1/2/3/4 1/2/3/4 Path type/DSCP value PHB:EF/ AF43/

AF23/ AF13 DSCP:46/38/22/14


Yes/18/10 –



Configure the backup information of the interface board according to the networking situation on site. ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and GOUa board in slot 19 to work in active/standby mode. ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=UOIa, LGCAPPTYPE=ATM, SN=14, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the UOIa board in slot 14 of subrack 0 and UOIa board in slot 15 to work in active/standby mode. Configure the backup information of the ports on the interface board according to the

networking situation on site. ADD ETHREDPORT: SRN=0, SN=18, PN=0; //Set port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 to work in active/standby mode. SET MSP: SRN=0, SN=14, PN=0, RT=REVERTIVE, K2MODE=NOT-INDICATE-END, SDSFPRI=HIGH, MODE=MODE3; // Port 0 on the UOIa in slot 14 of subrack 0 and port 0 on the UOIa in slot 15 are configured to work in MSP mode. Ensure that settings of interconnection parameters are consistent on both ends through negotiation. Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are

consistent on both ends. The MTU value on the RNC needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;





NO YES/VLAN200

Path detection flag ENABLE DISABLE Detected IP address 40.40.40.40/24 – TX bandwidth (kbps) 40000 40000

RX bandwidth (kbps) 40000 40000

Whether to enable the FPMUX

NO NO





Add the IP address of the Ethernet port. The IP address is planned by the operator. ADD ETHIP: SRN=0, SN=18, PN=0, IPINDEX=0, IPADDR="10.10.10.1", MASK="255.255.255.0"; // The IP address of the interface board on the RNC is 10.10.10.1/24. Add the device IP address of the interface board (optional) on the GOUa. The IP

address is planned by the operator. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add the logic IP address 20.20.20.20 on the interface board in slot 18. The default subnet mask 255.255.255.255 is adopted. Add the IP logic port (optional) on the interface board of the GOUa. The operator

needs to purchase the corresponding license. ADD IPLOGICPORT: SRN=0, SN=18, BT=GOUa, LPN=10, CARRYT=ETHER, PN=0, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, BWADJ=OFF, CIR=625, FLOWCTRLSWITCH=ON; // The logic port is on port 0 in slot 18 and the bandwidth on the port is 625 × 64 kbps = 40 Mbps. Set attributes of the optical ports on the UOIa. Ensure that the attribute values are

consistent on both ends. You can run the LST OPT command to query the default attribute values. If the default values can meet the requirements, additional configuration is unnecessary. SET OPT: SRN=0, SN=14, BT=UOIa, PS=SINGLE, PN=0, LNKNUMMODE=HUAWEI_MODE, J0TXT=NULL, J0RXT=NULL, J1TXT=NULL, J1RXT=NULL, S1VALUE=1, JAUTOADD=ZERO; Add the ATM logic port (optional) on the interface board of the GOUa. The operator

needs to purchase the corresponding license. ADD ATMLOGICPORT: SRN=0, SN=14, LPNTYPE=Leaf, BT=UOIa, LPN=20, CARRYT=NCOPT, CARRYPN=0, TXBW=5712, RXBW=5712, RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, FLOWCTRLSWITCH=ON, FCINDEX=1, TRMLOADTHINDEX=0; Add ATM traffic records.

ADD ATMTRF: TRFX=100, ST= CBR, UT=KBIT/S, PCR=240, CDVT=1024, REMARK="for Iub NCP "; ADD ATMTRF: TRFX=101, ST= CBR, UT=KBIT/S, PCR=680, CDVT=1024, REMARK="for Iub CCP "; ADD ATMTRF: TRFX=102, ST= CBR, UT=KBIT/S, PCR=104, CDVT=1024, REMARK="for Iub ALCAP "; ADD ATMTRF: TRFX=120, ST=RTVBR, UT=KBIT/S, PCR=1915, SCR=1741, MBS=1000, CDVT=1024, REMARK="for Iub R99 RT"; ADD ATMTRF: TRFX=121, ST=NRTVBR, UT=KBIT/S, PCR=5712, SCR=5288, MBS=1000, CDVT=1024, REMARK="for Iub R99 NRT"; ADD ATMTRF: TRFX=122, ST=UBR, UT=KBIT/S, PCR=5712, CDVT=1024, REMARK="for Iub H_NRT";



At least, add three SAAL links; one is used to transmit the NCP data; one is used to transmit the CCP data; the last one is used to transmit the ALCAP data. ADD SAALLNK: SRN=0, SN=0, SAALLNKN=1, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=14, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=34, TXTRFX=100, RXTRFX=100, SAALLNKT=UNI; // This link is used to transmit the NCP data. ADD SAALLNK: SRN=0, SN=0, SAALLNKN=2, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=14, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=35, TXTRFX=101, RXTRFX=101, SAALLNKT=UNI; // This link is used to transmit the CCP data. ADD SAALLNK: SRN=0, SN=0, SAALLNKN=3, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=14, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=36, TXTRFX=102, RXTRFX=102, SAALLNKT=UNI; // This link is used to transmit the ALCAP data. Add a NodeB and algorithm parameters (data on the control plane).

ADD UNODEB: NodeBName="RNC8-BBU1", NodeBId=1, SRN=0, SN=0, TnlBearerType=ATMANDIP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED, CnOpIndex=0; // Note that the ATM address of the NodeB is not configured on the RAN12. ADD UNODEBALGOPARA: NodeBName="RNC8-BBU1", NodeBLdcAlgoSwitch=IUB_LDR-1&NODEB_CREDIT_LDR-1; // The algorithm switch is configured based on the data planning of the radio layer. It’s necessary to configure the corresponding parameter to the algorithm switch if turn it on. Add an adjacent node (data on the control plane).

ADD ADJNODE: ANI=10, NAME=" NODEB1", NODET=IUB, NODEBID=1, TRANST=ATM_IP, IsROOTNODE=YES, SAALLNKN=3; Add links on the NodeB control port (data on the control plane).

ADD UNCP: NodeBName=" RNC8-BBU1", CARRYLNKT=SAAL, SAALLNKN=1; ADD UCCP: NodeBName=" RNC8-BBU1", PN=0, CARRYLNKT= SAAL, SAALLNKN=2;


Add the mapping between transmission resources to map services of different QoS requirements to different AAL2 paths or IP paths. When the dual stack transport is applied to the Iub interface, TRMMP ID is set to 2 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID. In this example, the default mapping is used.


TRMMAP(Iub)


Common channel RT_VBR EF IMS SRB RT_VBR EF SRB RT_VBR EF AMR voice RT_VBR EF R99 CS conversational RT_VBR AF43 R99 CS streaming RT_VBR AF43 R99 PS conversational RT_VBR AF43 R99 PS streaming RT_VBR AF43

Add an activation factor table to specify proper factors for each traffic class. Through this task, the transmission resources can be multiplexed. By default, Factor Table Index is set to 0. If the default mapping cannot meet the requirements, you can use the ADD TRMFACTOR command to add an index. See section 4.2.4 . Configure the threshold table for load balancing between active and standby paths.

You can run the LST LOADEQ command (LOADEQ ID = 0) to obtain the default threshold table. If the default mapping cannot meet the requirement, you can run the ADD LOADEQ command to add an index.

In this example, the default mapping is used.

Generally, the active path is preferred to carry the load. If the following conditions are met, the standby path is recommended.

The load on the active path is greater than the load threshold of this path. The load on the active path times the threshold for the ratio of the load on the active path to the load on the standby path is greater than the load on the standby path.

R99 PS high PRI interactive NRT_VBR AF23 R99 PS middle PRI interactive NRT_VBR AF23

R99 PS low PRI interactive NRT_VBR AF23 R99 PS background NRT_VBR AF23 HSDPA Signal RT_VBR EF HSDPA IMS Signal RT_VBR EF HSDPA Voice RT_VBR AF43 HSDPA conversational RT_VBR AF43 HSDPA streaming RT_VBR AF43 HSDPA high PRI interactive AF13 UBR HSDPA middle PRI interactive AF13 UBR

HSDPA low PRI interactive AF13 UBR HSDPA background AF13 UBR HSUPA Signal RT_VBR EF HSUPA IMS Signal RT_VBR EF HSUPA Voice RT_VBR AF43 HSUPA conversational RT_VBR AF43 HSUPA streaming RT_VBR AF43 HSUPA high PRI interactive AF13 UBR HSUPA middle PRI interactive AF13 UBR

HSUPA low PRI interactive AF13 UBR HSUPA background AF13 UBR

Default

Threshold for the Ratio of

Configure the TRM mapping on the adjacent node. You can run the ADD TRMMAP command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=ATM_IP, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=2, TMISLV=2, TMIBRZ=2, FTI=0, LEIGLD=0, LEISLV=0, LEIBRZ=0;


Configure the IP route to the interface IP address of the NodeB on the Iub interface of the GOUa of the RNC.

Service Type Load Threshold of the Active Path (%)

the Load on the Active Path to the Load on the Standby Path (%)

Common channel 100 0 IMS SRB 100 0 SRB 100 0 AMR voice 100 0 R99 CS conversational 100 0 R99 CS streaming 100 0 R99 PS conversational 100 0 R99 PS streaming 100 0 R99 PS high PRI interactive 30 100 R99 PS middle PRI interactive 30 100 R99 PS low PRI interactive 30 100 R99 PS background 30 100 HSDPA Signal 100 0 HSDPA IMS Signal 100 0 HSDPA Voice 100 0 HSDPA conversational 100 0 HSDPA streaming 100 0 HSDPA high PRI interactive 30 100 HSDPA middle PRI interactive 30 100 HSDPA low PRI interactive 30 100 HSDPA background 30 100 HSUPA Signal 100 0 HSUPA IMS Signal 100 0 HSUPA Voice 100 0 HSUPA conversational 100 0 HSUPA streaming 100 0 HSUPA high PRI interactive 30 100 HSUPA middle PRI interactive 30 100 HSUPA low PRI interactive 30 100 HSUPA background 30 100


ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP="10.10.10.2", PRIORITY=HIGH, REMARK="RNC INT To NodeB1"; // Configure the host route to the interface IP address of NodeB1. Add the AAL2 path to the NodeB.

ADD AAL2PATH: ANI=10, PATHID=1, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=14, CARRYVPN=20, VPI=10, VCI=40, TXTRFX=120, RXTRFX=120, AAL2PATHT=SHARE; ADD AAL2PATH: ANI=10, PATHID=2, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=14, CARRYVPN=20, VPI=10, VCI=41, TXTRFX=120, RXTRFX=120, AAL2PATHT=SHARE; ADD AAL2PATH: ANI=10, PATHID=3, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=14, CARRYVPN=20, VPI=10, VCI=42, TXTRFX=120, RXTRFX=120, AAL2PATHT=SHARE; ADD AAL2PATH: ANI=10, PATHID=4, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=14, CARRYVPN=20, VPI=10, VCI=43, TXTRFX=121, RXTRFX=121, AAL2PATHT=SHARE; ADD AAL2PATH: ANI=10, PATHID=5, CARRYT=ATMLOGICPORT, CARRYF=0, CARRYSN=14, CARRYVPN=20, VPI=10, VCI=44, TXTRFX=122, RXTRFX=122, AAL2PATHT=SHARE; Add the IP path to the NodeB.

ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=ATM_IP, PATHT=EF, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the path type is EF, the DSCP value is 46. ADD IPPATH: ANI=10, PATHID=2, ITFT=IUB, TRANST=ATM_IP, PATHT=AF43, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the path type is AF43, the DSCP value is 38. ADD IPPATH: ANI=10, PATHID=3, ITFT=IUB, TRANST=ATM_IP, PATHT=AF23, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the path type is AF23, the DSCP value is 22. ADD IPPATH: ANI=10, PATHID=4, ITFT=IUB, TRANST=ATM_IP, PATHT=AF13, IPADDR="20.20.20.20", PEERIPADDR="40.40.40.40", PEERMASK="255.255.255.255", TXBW=40000, RXBW=40000, CARRYFLAG=IPLGCPORT, LPNSN=18, LPN=10, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.40"; // When the path type is AF13, the DSCP value is 14.


VLAN Configuration

− IP over Ethernet: If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID for the next hop (VRRP Virtual IP) of the RNC.

− IP over SDH: The VLAN is not configured. Note: The VLAN needs to be configured on the intermediate transmission device. DSCP Configuration


IP Over Ethernet: If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured. If VLAN priorities need to be configured on the RNC, see section 3.5 according to the planning of the existing network. Note: VLAN priorities need to be configured on the intermediate transmission devices.


Note




Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the NodeB needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M, DUPLEX=FULL, ARPPROXY=DISABLE; // If the interface IP address of the NodeB is on the same network segment as that of the OM IP address, set ARP Proxy to Enable. Add the IP address of the Ethernet port. The IP address of the FE port on the NodeB

is 40.40.40.40/24. ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="40.40.40.40", MASK="255.255.255.0"; Set the bearer mode of the E1/T1 cables to IPV4. Then, reset the transmission

interface board. SET E1T1BEAR: SRN=0, SN=6, MODE=ATM, IMPEDANCE=75; Set attributes of the E1 cables on the WMPT. Ensure that the attribute values are

consistent on both ends. You can run the DSP E1T1WORKMODE command to query the attribute values. SET E1T1WORKMODE: SRN=0, SN=6, SBT=BASE_BOARD, FRAME=E1_CRC4_MULTI_FRAME, LNCODE=HDB3, CLKM=MASTER; Add IMA groups and IMA links. Ensure that the settings are consistent on both ends.

ADD IMAGRP: SRN=0, SN=6, SBT=BASE_BOARD, VER=V1.1, CLKM=ITC, FRMLEN=D128, SCRAM=ENABLE; ADD IMALNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, IMALNKN=0, IMAGRPSBT=BASE_BOARD, IMAGRPN=0; ADD IMALNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, IMALNKN=1, IMAGRPSBT=BASE_BOARD, IMAGRPN=0; ADD IMALNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, IMALNKN=2, IMAGRPSBT=BASE_BOARD, IMAGRPN=0;


At least, add three SAAL links; one is used to transmit the NCP data; one is used to transmit the CCP data; the last one is used to transmit the ALCAP data. ADD SAALLNK: SAALNO=0, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=34, RU=KBPS, ST=CBR, PCR=240; // This link is used to transmit the NCP data. ADD SAALLNK: SAALNO=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=35, RU=KBPS, ST=CBR, PCR=680; // This link is used to transmit the CCP data. ADD SAALLNK: SAALNO=2, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=36, RU=KBPS, ST=CBR, PCR=104; // This link is used to transmit the ALCAP data. Add links on the NodeB control port.

ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=1; ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=ATM, LN=2;


Add AAL2 paths. ADD AAL2PATH: NT=LOCAL, PATHID=1, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=40, RU=KBPS, ST=RTVBR, PCR=1915, SCR=1741, MBS=1000, CDVT=10240, RCR=1741; ADD AAL2PATH: NT=LOCAL, PATHID=2, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=41, RU=KBPS, ST=RTVBR, PCR=1915, SCR=1741, MBS=1000, CDVT=10240, RCR=1741; ADD AAL2PATH: NT=LOCAL, PATHID=3, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=42, RU=KBPS, ST=RTVBR, PCR=1915, SCR=1741, MBS=1000, CDVT=10240, RCR=1741; ADD AAL2PATH: NT=LOCAL, PATHID=4, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=43, RU=KBPS, ST=NRTVBR, PCR=5712, SCR=5288, MBS=1000, CDVT=10240, RCR=5288; ADD AAL2PATH: NT=LOCAL, PATHID=5, SRN=0, SN=6, SBT=BASE_BOARD, PT=IMA, PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=44, RU=KBPS, ST=UBR, PCR=5712, RCR=5508; Add four IP paths with different priorities. Ensure that the configuration is consistent

with that on the RNC. The ping detection switch on the IP path on the NodeB is disabled. ADD IPPATH: PATHID=1, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=46, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=2, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH,

JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=38, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=3, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=22, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE; ADD IPPATH: PATHID=4, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, NODEBIP="40.40.40.40", RNCIP="20.20.20.20", DSCP=14, RXBW=40000, TXBW=40000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;


VLAN Configuration − IP path In layer 3 networking, the NodeB may first connect to a layer 2 network. In this case, the VLAN ID is configured on the NodeB. In this example, set the VLAN ID to 200 on the NodeB. ADD VLANMAP: NEXTHOPIP="40.40.40.39", VLANMODE=VLANGROUP, VLANGROUPNO=0; // Configure a VLAN group to the network gateway on the NodeB. For the specific VLAN ID setting, see section 3.3.2 –3.3.7 . Note: The VLAN needs to be configured on the intermediate transmission device. DSCP Configuration


1. IP path According to the planning of the existing network, see section 3.5 for VLAN priorities of various services. Note: VLAN priorities need to be configured on the intermediate transmission devices.



Configure the IP route to the device IP address of the RNC on the WMPT of the NodeB. ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="20.20.20.20", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the device IP address of the RNC for the device IP address serve as the IP address for the traffic on the RNC in this example. Configure the IP route to the Ethernet port of the RNC on the WMPT of the NodeB.

It is optional. To facilitate the commissioning, the route needs to be configured when you need to ping the IP address of the Ethernet port on the RNC from the NodeB.

ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.10.10.1", DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="40.40.40.39"; // Configure the host route to the interface IP address of RNC.

5 IUPS Configuration Example

5.1 Description





5.2.2 Preparations

Cables are properly connected and intermediate transmission devices are ready.

The data planning is completed.

5.2.3 Data Planning of IP Layer 3 Networking

5.2.4 Data Planning of Layer 3 Networking



Data Item RNC SGSN Data Source Data on the FE port

Interface board type GOUa – Internal planning IP address of the network gateway

10.10.10.2/24 – Network planning



– Internal planning


0/18/0 –



IP address for the traffic

CP_IP1 20.20.20.20/32 40.40.40.40/32

CP_IP2 20.20.20.30/32 40.40.40.50/32

UP_IP1 20.20.20.40/32 40.40.40.60/32


IP logic port No. – – Bandwidth of the IP logic port

– –


OFF –

Data Item RNC SGSN Data Source SCTP0 Local SCTP port No. 8525 8625 Data to be

negotiated Working mode of the SCTP link Client Server Subrack No./slot No. of the SPU 0/2 – DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –

Whether to add the VLAN/VLAN ID NO – SCTP1 Local SCTP port No. 8526 8626

Working mode of the SCTP link Client Server Subrack No./slot No. of the SPU 0/4 – DSCP 48 48




Configure the backup information of the interface board according to the networking situation on site. ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and GOUa board in slot 19 to work in active/standby mode. Configure the backup information of the ports on the interface board according to the

networking situation on site. ADD ETHREDPORT: SRN=0, SN=18, PN=0; // Set Port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 to work in active/standby mode.

Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –

Whether to add the VLAN/VLAN ID NO – M3UA Type of the local entity M3UA_IPSP M3UA_IPSP Data to be

negotiated Context of the local entity route 4294967295 4294967295 Working mode Load sharing Load sharing Working mode M3UA_IPSP M3UA_IPSP

Data Item RNC SGSN Data Source Adjacent node ID 10 – Internal

planning Transport type of the IUPS interface IP – One IP path

Port type ETH ETH Data to be negotiated IP path ID 0 –

Path type QoS – Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –

Local IP address/subnet mask 20.20.20.40/32 40.40.40.60/24 Network planning Whether to enable the

VLAN/enabled VLAN ID NO –

Path detection flag ENABLE – Network planning Detected IP address 40.40.40.60/24 –

TX bandwidth (kbps) 1000000 1000000 RX bandwidth (kbps) 1000000 1000000 Whether to enable the FPMUX NO NO

Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the RNC needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;


Run the following command to add the IP address of the Ethernet port. The IP address is planned by the operator. ADD ETHIP: SRN=0, SN=18, PN=0, IPINDEX=0, IPADDR="10.10.10.1", MASK="255.255.255.0"; // The IP address of the interface board on the RNC is 10.10.10.1/24. Add the device IP address of the interface board (optional). The IP address is

planned by the operator. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add logic IP address 1 20.20.20.20 on the interface board in slot 18 to be local IP address 1 of SCTP. The default subnet mask 255.255.255.255 is adopted. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.30"; // Add logic IP address 1 20.20.20.30 on the interface board in slot 18 to be local IP address 2 of SCTP. The default subnet mask 255.255.255.255 is adopted. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.40"; // Add logic IP address 1 20.20.20.40 on the interface board in slot 18 to be local IP address 1 of the GTPU. The default subnet mask 255.255.255.255 is adopted.


The general configuration procedure is as follows:

(OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK

Add SCTP signaling links. Set Signaling link mode to CLIENT or SERVER. Generally, the SGSN serves as the server, whereas the RNC acts as the client. Set Application type to M3UA. The port No. must be consistent on both ends. In this example, configure the SCTP dual homing. ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=M3UA,






DSCP=48, LOCPN=8525, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=8625, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=4, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=48, LOCPN=8526, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=8626, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; According to the planning on site, you can configure either the host route (the subnet

mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To SGSN1_CP1"; ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.50", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To SGSN1_CP2"; Add a destination signaling point.

ADD N7DPC: NAME="SGSN1", DPX=3, SPX=0, SPDF=WNF, DPC= H'000515, DPCT=IUPS, SLSMASK=B0000, NEIGHBOR=YES, STP=OFF, BEARTYPE=M3UA, PROT=ITUT; Add a local M3UA entity.

ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME=" RNC12"; Add an M3UA destination entity. If the negotiation is required by the peer end, set

the route context of the destination entity according to the route context provided by the peer end. ADD M3DE: DENO=3, LENO=0, DPX=3, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME=" SGSN1"; Add an M3UA link set. To implement load sharing among M3UA links, it is

recommended to set Signaling link mask to B0111. Settings of Work mode and Traffic mode need to be consistent on both ends. ADD M3LKS: SIGLKSX=3, DENO=3, LNKSLSMASK=B1111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, NAME=" SGSN1"; Note: If signaling routes need to work in load sharing mode, set Signaling route mask to B1000 in the ADD N7DPC command and set Signaling link mask to B0111 in the ADD M3LKS command because the result of the AND operation of the two settings must be 0. Add an M3UA route.

ADD M3RT: DENO=3, SIGLKSX=3, PRIORITY=0, NAME=" to SGSN1"; Add M3UA links.

ADD M3LNK: SIGLKSX=3, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to SGSN1_0"; ADD M3LNK: SIGLKSX=3, SIGLNKID=1, SRN=0, SN=4, SCTPLNKN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to SGSN1_1"; Add a transport adjacent node. Set Adjacent Node Type to IUPS and Transport

Type to IP. ADD ADJNODE: ANI=3, NAME=" SGSN1", NODET=IUPS, SGSNFLG=YES, TRANST=IP, DPX=3;

Add a CN domain. Set CN domain ID to PS_DOMAIN (PS domain). ADD UCNDOMAIN: CNDomainId=PS_DOMAIN, NMO=MODE2, DRXCycleLenCoef=6; Add a CN node. Set CN domain ID to PS_DOMAIN (PS domain) and Iu transfers

bearer type to IP_TRANS (IP transport). ADD UCNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=3, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS;


Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. For the IUPS transport, TRMMP ID is set to 8 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID.


Add an activation factor table to specify proper factors for each traffic class. Through this task, the transmission resources can be multiplexed. By default, Factor Table Index is set to 0. If the default mapping cannot meet the requirements, you can use the ADD TRMFACTOR command to add an index. See section 4.2.4 . Configure the TRM mapping on the adjacent node. You can run the ADD TRMMAP

command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=3, ITFT=IUPS, TMIGLD=8, TMISLV=8, TMIBRZ=8, FTI=0; // In this example, both TMI and FTI use default values.


Add an IP path. The traffic unit is kbps. PHBs corresponding to various services on the IUPS can be obtained by using the LST TRMMAP command. DSCP values

TRMMAP(IuPS)


Common channel NULL NULL IMS SRB EF NULL SRB NULL NULL AMR voice NULL NULL R99 CS conversational NULL NULL R99 CS streaming NULL NULL R99 PS conversational AF43 NULL R99 PS streaming AF43 NULL R99 PS high PRI interactive AF23 NULL R99 PS middle PRI interactive AF23 NULL R99 PS low PRI interactive AF23 NULL R99 PS background AF23 NULL

corresponding to PHBs can be obtained by using the LST PHBMAP command. ADD IPPATH: ANI=3, PATHID=0, ITFT=IUPS, PATHT=QoS, IPADDR="20.20.20.40", PEERIPADDR="40.40.40.60", PEERMASK="255.255.255.255", TXBW=1000000, RXBW=1000000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.60"; // If more than one GTPU address is available on the peer end, you need to configure multiple IP addresses. Configure routes on the user plane. It is optional. According to the planning on site,

you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.60", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To SGSN1_UP";


VLAN Configuration

If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC.

If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID on the next hop (VRRP Virtual IP) of the RNC.


DSCP Configuration

According to the planning of the existing network, see section 3.4.1 for DSCP values on the signaling plane.

According to the planning of the existing network, run the ADD TRMMAP command to set the PHB of the IUPS to QoS during the setting of DSCP values. Then, run the SET PHBMAP command to set the mapping between the PHB and the DSCP value.



If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured.

After DSCP values are set for various services on the user plane, run the SET DSCPMAP command to set the mapping between DSCP values and VLAN priorities.

For the detailed configuration of VLAN priorities of other services, see section 3.5 .


6 IUCS Configuration Example

6.1 Description





6.2.2 Preparations





Data Item RNC MGW/MSC Server Data Source Data on the FE port

Interface board type GOUa – Internal planning IP address of the network gateway




– Internal planning


0/18/0 –




CP_IP1 20.20.20.20/32 40.40.40.40/32

CP_IP2 20.20.20.30/32 40.40.40.50/32

UP_IP1 20.20.20.40/32 40.40.40.60/32



– –


OFF –

Data Item RNC MSC Server Data Source

SCTP0 Local SCTP port No. 5000 5100 Data to be negotiated Working mode of the SCTP

link Client Server

Subrack No./slot No. of the SPU

0/2 –

DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –

Whether to add the VLAN/VALN ID

NO –

SCTP1 Local SCTP port No. 5002 5102 Working mode of the SCTP link

Client Server

Subrack No./slot No. of the 0/4 –




Configure the backup information of the interface board according to the networking situation on site. ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and

SPU DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –

Whether to add the VLAN/VALN ID

NO –

M3UA Type of the local entity M3UA_IPSP M3UA_IPSP Data to be negotiated Context of the local entity

route 4294967295 4294967295

Working mode Load sharing Load sharing Working mode M3UA_IPSP M3UA_IPSP

Data Item RNC MGW Data Source Adjacent node ID 10 – Internal

planning Transport type of the IUCS interface IP – Two IP paths

Port type ETH ETH Data to be negotiated IP path ID 0/1 –

PATH type EF/AF43 – Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –




NO –

Path detection flag ENABLE – Network planning Detected IP address 40.40.40.60/24 –


NO NO

GOUa board in slot 19 to work in active/standby mode. Configure the backup information of the ports on the interface board according to the

networking situation on site. ADD ETHREDPORT: SRN=0, SN=18, PN=0; // Set port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 to work in active/standby mode. Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are

consistent on both ends. The MTU value on the RNC needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 . SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;



planned by the operator. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add logic IP address 1 20.20.20.20 on the interface board in slot 18 to be local IP address 1 of SCTP. The default subnet mask 255.255.255.255 is adopted. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.30"; // Add logic IP address 1 20.20.20.30 on the interface board in slot 18 to be local IP address 2 of SCTP. The default subnet mask 255.255.255.255 is adopted. ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.40"; // Add logic IP address 1 20.20.20.40 on the interface board in slot 18 to be local IP address 1 of the GTPU. The default subnet mask 255.255.255.255 is adopted.



(OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK






Add SCTP signaling links. Set Signaling link mode to CLIENT or SERVER. Generally, the SGSN serves as the server, whereas the RNC acts as the client. Set Application type to M3UA. The port No. must be consistent on both ends. ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=M3UA, DSCP=48, LOCPN=5000, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=5100, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=4, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=48, LOCPN=5002, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=5102, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; According to the planning on site, you can configure either the host route (the subnet

mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To MSC1_CP1"; ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.50", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To MSC1_CP2"; Add two destination signaling point.

ADD N7DPC: NAME="MSC1", DPX=0, SPX=0, SPDF=WNF, DPC=H'000972, DPCT= IUCS_RANAP, SLSMASK=B0000, NEIGHBOR=YES, STP=OFF, BEARTYPE=M3UA, PROT=ITUT; ADD N7DPC: NAME="MGW1", DPX=1, SPX=0, SPDF=WNF, DPC=H'000973, DPCT= IUCS_ALCAP, SLSMASK=B0000, NEIGHBOR=YES, STP=OFF, BEARTYPE=M3UA, PROT=ITUT; Add a local M3UA entity.


the route context of the destination entity according to the route context provided by the peer end. ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME=" MSC1"; Add an M3UA link set. To implement load sharing among M3UA links, it is

recommended to set Signaling link mask to B0111. Ensure that settings of Work mode and Traffic mode are consistent on both ends. ADD M3LKS: SIGLKSX=0, DENO=0, LNKSLSMASK=B1111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, NAME=" MSC1"; Note: If signaling routes need to work in load sharing mode, set Signaling route mask to B1000 in the ADD N7DPC command and set Signaling link mask to B0111 in the ADD M3LKS command because the result of the AND operation of the two settings must be 0. Add an M3UA route.

ADD M3RT: DENO=0, SIGLKSX=0, PRIORITY=0, NAME=" to MSC1"; Add M3UA links.

ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to MSC1_0";

ADD M3LNK: SIGLKSX=0, SIGLNKID=1, SRN=0, SN=4, SCTPLNKN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to MSC1_1"; Add an adjacent node. Set Adjacent Node Type to IUCS and Transport Type to

IP. ADD ADJNODE: ANI=1700, NAME=" MGW1", NODET=IUCS, TRANST=IP, DPX=1; Add a CN domain. Set CN domain ID to CS_DOMAIN.

ADD UCNDOMAIN: CNDomainId=CS_DOMAIN, T3212=10, ATT=ALLOWED, DRXCycleLenCoef=6; Add a CN node. Set CN domain ID to PS_DOMAIN (PS domain) and Iu transfers

bearer type to IP_TRANS (IP transport). ADD UCNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS, RTCPSwitch=OFF, Switch3GPP25415CR0125=OFF;


Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. For the IUCS transport, TRMMP ID is set to 7 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID.



command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=1700, ITFT=IUCS, TRANST=IP, TMIGLD=7, TMISLV=7, TMIBRZ=7, FTI=0; // In this example, both TMI and FTI use default values.


Add IP paths. The traffic unit is kbps. You can run the LST PHBMAP command to query the DSCP value corresponding to the PHB of each IP path. ADD IPPATH: ANI=1700, PATHID=0, ITFT=IUCS, PATHT=EF, IPADDR="20.20.20.40", PEERIPADDR="40.40.40.60",

TRMMAP(Iub)


Common channel NULL NULL IMS SRB NULL NULL SRB NULL NULL AMR voice EF NULL R99 CS conversational AF43 NULL R99 CS streaming AF43 NULL

PEERMASK="255.255.255.255", TXBW=1000000, RXBW=1000000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.60"; // When the path type is EF, the DSCP value is 46. ADD IPPATH: ANI=1700, PATHID=1, ITFT=IUCS, PATHT=AF43, IPADDR="20.20.20.40", PEERIPADDR="40.40.40.60", PEERMASK="255.255.255.255", TXBW=1000000, RXBW=1000000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.60"; // When the path type is AF43, the DSCP value is 38. Configure the route on the user plane. It is optional. According to the planning on

site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.60", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To MGW1_UP";


VLAN Configuration If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID on the next hop (VRRP Virtual IP) of the RNC.

ADD VLANID: IPADDR="10.10.10.2", VLANID=100;




DSCP Configuration According to the planning of the existing network, see section 3.3 for the DSCP configuration.


VLAN Priority Configuration If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured. If VLAN priorities need to be configured on the RNC, see section 3.4 . Note: VLAN priorities need to be configured on the intermediate transmission devices.

7 Iur Configuration Example

7.1 Description





7.2.2 Preparations





Data Item RNC HW NRNC Data Source Data on the FE port

Interface board type GOUa GOUa Internal planning IP address of the network gateway





Internal planning


0/18/0 0/24/0




CP_IP1 20.20.20.20/32 40.40.40.40/32

CP_IP2 20.20.20.30/32 40.40.40.50/32

UP_IP1 20.20.20.40/32 40.40.40.60/32



– –


OFF –

Data Item RNC HW NRNC Data Source SCTP0 Local SCTP port No. 2905 9000 Data to be

negotiated Working mode of the SCTP link

Server Client


0/2 –

DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP logic port/slot No. and port No. of the logic port

NO –


NO –

SCTP1 Local SCTP port No. 2905 9001

Working mode of the SCTP link

Server Client


0/4 –

DSCP 48 48 Local IP address 1 20.20.20.20/32 40.40.40.40/32 Local IP address 2 20.20.20.30/32 40.40.40.50/32 Whether to bind the IP NO –




Configure the backup information of the interface board according to the networking situation on site.

ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=18, RED=YES, MPUSUBRACK=0, MPUSLOT=0; // Set the GOUa board in slot 18 of subrack 0 and GOUa board in slot 19 to work in active/standby mode.

Configure the backup information of the ports on the interface board according to the networking situation on site.

logic port/slot No. and port No. of the logic port Whether to add the VLAN/VLAN ID

NO –

M3UA Type of the local entity M3UA_IPSP M3UA_IPSP Data to be negotiated Context of the local

entity route 4294967295 4294967295

Working mode Load sharing Load sharing

Working mode M3UA_IPSP M3UA_IPSP

Data Item RNC HW NRNC Data Source Adjacent node ID 10 – Internal

planning Transport type of the Iur interface IP – One IP path

Port type ETH ETH Data to be negotiated IP path ID 0 0

PATH type QoS QoS Whether to bind the IP logic port/slot No. and port No. of the logic port

NO NO




NO NO

Path detection flag ENABLE ENABLE Network planning Detected IP address 40.40.40.60/32 20.20.20.40/32


NO NO

ADD ETHREDPORT: SRN=0, SN=18, PN=0; //Set port 0 on the GOUa in slot 18 of subrack 0 and port 0 on the GOUa in slot 19 to work in active/standby mode.

Set the attributes of the Ethernet ports. Ensure that the Ethernet port attributes are consistent on both ends. The MTU value on the RNC needs to be smaller or equal to that of the intermediate transmission device. See section 3.2 .

SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOUa, PN=0, AUTO=ENABLE, MTU=1500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=1;



planned by the operator.

ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.20"; // Add logic IP address 1 20.20.20.20 on the interface board in slot 18 to be local IP address 1 of SCTP. The default subnet mask 255.255.255.255 is adopted.

ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.30"; // Add logic IP address 1 20.20.20.30 on the interface board in slot 18 to be local IP address 2 of SCTP. The default subnet mask 255.255.255.255 is adopted.

ADD DEVIP: SRN=0, SN=18, DEVTYPE=LOGIC_IP, IPADDR="20.20.20.40"; // Add logic IP address 1 20.20.20.40 on the interface board in slot 18 to be the local IP address of the user plane. The default subnet mask 255.255.255.255 is adopted.



(OPC --> N7DPC )-->SCTPLNK--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK

Add SCTP signaling links. Set Signaling link mode to CLIENT or SERVER. In this






example, the SGSN serves as the server, whereas the RNC acts as the client. Set Application type to M3UA. The port No. must be consistent on both ends. ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE= SERVER, APP=M3UA, DSCP=48, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=9000, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=1, MODE= SERVER, APP=M3UA, DSCP=48, LOCIP1="20.20.20.20", LOCIP2="20.20.20.30", PEERIP1="40.40.40.40", PEERIP2="40.40.40.50", PEERPN=9001, LOGPORTFLAG=NO, MTU=800, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES; Note: When the RNC acts as an SCTP server, you can run the SET SCTPSRVPORT command to set the local SCTP port No.. Generally, the default No. is used. You can use the LST SCTPSRVPORT command to query the default No..

Configure the route on the control plane. It is optional. According to the planning on

site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.40", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To NRNC1_CP1"; ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.50", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To NRNC1_CP2"; Add a destination signaling point.

ADD N7DPC: NAME="NRNC1", DPX=11, SPX=0, SPDF=WNF, DPC= H'000579, DPCT= IUR, SLSMASK=B0000, NEIGHBOR=YES, STP=OFF, BEARTYPE=M3UA, PROT=ITUT; Add an adjacent RNC. Set the switch in the radio layer according to the planning of

the existing network. ADD UNRNC: NRncId=11, HHOTRIG=OFF, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=11, RncProtclVer=R6, TnlBearerType=IP_TRANS; Add a local M3UA entity.


the route context of the destination entity according to the route context provided by the peer end. ADD M3DE: DENO=11, LENO=0, DPX=11, ENTITYT=M3UA_IPSP, RTCONTEXT=4294967295, NAME=" NRNC1"; Add an M3UA link set. To implement load sharing among M3UA links, it is

recommended to set Signaling link mask to B0111. Ensure that settings of Work mode and Traffic mode are consistent on both ends. ADD M3LKS: SIGLKSX=11, DENO=11, LNKSLSMASK=B1111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, NAME=" To NRNC1"; Note: If signaling routes need to work in load sharing mode, set Signaling route mask to B1000 in the ADD N7DPC command and set Signaling link mask to

B0111 in the ADD M3LKS command because the result of the AND operation of the two settings must be 0. Add an M3UA route.

ADD M3RT: DENO=11, SIGLKSX=11, PRIORITY=0, NAME=" To NRNC1"; Add M3UA links.

ADD M3LNK: SIGLKSX=11, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to MSC1_0"; ADD M3LNK: SIGLKSX=11, SIGLNKID=1, SRN=0, SN=4, SCTPLNKN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME=" to MSC1_1"; Add an adjacent node. Set Adjacent Node Type to Iur and Transport Type to IP.

ADD ADJNODE: ANI=5, NAME=" NRNC1", NODET=Iur, TRANST=IP, DPX=11;


Add the mapping between transmission resources to map services of different QoS requirements to different IP paths. For the IP transport on the Iur interface, TRMMP ID is set to 5 by default. If the default mapping cannot meet the requirements, you can use the ADD TRMMAP command to add a TRMMP ID.


TRMMAP(Iub IP)


Common channel EF NULL IMS SRB EF NULL SRB EF NULL AMR voice EF NULL R99 CS conversational AF43 NULL R99 CS streaming AF43 NULL R99 PS conversational AF43 NULL R99 PS streaming AF43 NULL R99 PS high PRI interactive AF23 NULL R99 PS middle PRI interactive AF23 NULL R99 PS low PRI interactive AF23 NULL R99 PS background AF23 NULL HSDPA Signal EF NULL HSDPA IMS Signal EF NULL HSDPA Voice AF43 NULL HSDPA conversational AF43 NULL HSDPA streaming AF43 NULL HSDPA high PRI interactive AF13 NULL HSDPA middle PRI interactive AF13 NULL HSDPA low PRI interactive AF13 NULL HSDPA background AF13 NULL


command to add the TRMMAP ID for the gold, silver, and bronze users. ADD ADJMAP: ANI=5, ITFT=Iur, TRANST=IP, TMIGLD=5, TMISLV=5, TMIBRZ=5, FTI=0; // In this example, both TMI and FTI use default values.


Add IP paths. The traffic unit is kbps. PHBs corresponding to various services on the Iur interface can be obtained by using the LST TRMMAP command. DSCP values corresponding to PHBs can be obtained by using the LST PHBMAP command. In this example, the HW RNC connects to each other. Therefore, the PATH type can be set to QoS. ADD IPPATH: ANI=5, PATHID=0, ITFT=Iur, PATHT=QoS, IPADDR="20.20.20.40", PEERIPADDR="40.40.40.60", PEERMASK="255.255.255.255", TXBW=1000000, RXBW=1000000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.60"; If the HW RNC connects to the RNCs provided by other competitors, configure four IP paths of the EF, AF43, AF 23, and AF13 types according to the Transmission Configuration Specifications. Configure the route on the user plane. It is optional. According to the planning on

site, you can configure either the host route (the subnet mask of the destination IP address is 255.255.255.255) or the network segment route (the destination IP address is the network address and the subnet mask cannot be 255.255.255.255). ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.60", DSTMASK="255.255.255.255", NEXTHOP=""10.10.10.2", PRIORITY=HIGH, REMARK=" To NRNC_UP1";


VLAN Configuration If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. If the VLAN ID needs to be configured on the RNC, run the ADD VLANID command to add the VLAN ID on the next hop (VRRP Virtual IP) of the RNC.


HSUPA Signal EF NULL HSUPA IMS Signal EF NULL HSUPA Voice AF43 NULL HSUPA conversational AF43 NULL HSUPA streaming AF43 NULL HSUPA high PRI interactive AF13 NULL HSUPA middle PRI interactive AF13 NULL HSUPA low PRI interactive AF13 NULL HSUPA background AF13 NULL



Note: The VLAN needs to be configured on the intermediate transmission device. DSCP Configuration

According to the planning of the existing network, see section 3.3 for the DSCP configuration. Note: DSCP values need to be configured on the intermediate transmission device. VLAN Priority Configuration

If the RNC directly connects to the router in layer 3 networking, the VLAN ID is not configured on the RNC. Then, the VLAN priorities are not configured. If VLAN priorities need to be configured on the RNC, see section 3.4 . Note: VLAN priorities need to be configured on the intermediate transmission devices.

VI. Data Configuration for Static Relocation

To reduce the bandwidth occupied by the Iur interface and the transmission delay on the user plane, you can configure static SRNC relocation from a Serving RNC (SRNC) to a Drift RNC (DRNC).

Add an IP route to the DRNC by running the following command: ADD IPRT: SRN=0, SN=18, DSTIP="40.40.40.60", DSTMASK="255.255.255.255", NEXTHOP="GW1", PRIORITY=HIGH, REMARK="Static Relocation"; \\ Set Destination IP address (DSTIP) to the user plane IP address of the DRNC and Forward route address (NEXTHOP) to the SGSN gateway (GW1) IP address for the forward route from the RNC. Add an IP path used for static relocation by running the following command:

ADD IPPATH: ANI=3, PATHID=0, ITFT=IUPS, PATHT=QoS, IPADDR="20.20.20.40", PEERIPADDR="40.40.40.60", PEERMASK="255.255.255.255", TXBW=1000000, RXBW=1000000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="40.40.40.60"; \\ Set Adjacent Node ID (ANI) to the adjacent node ID of the SGSN. Set Local IP address (IPADDR) to the user plane IP address of the SRNC. Set Peer IP address (PEERIPADDR) to the user plane IP address of the DRNC. Set Peer subnet mask (PEERMASK) to the subnet mask of the DRNC user plane IP address and the recommended value is 255.255.255.0.

It is recommended that an IP route and IP path to the DRNC be configured for each IP interface board configured with Iu-PS user plane data. If there exist multiple destination IP network segments at the DRNC, an IP route and IP path to each network segment need to be configured for each IP interface board. This facilitates load sharing between Iu-PS and Iur interfaces.

8 Remote OM Channel

8.1 IPRAN O&M Networking Diagram

8.2 Interworking Between the M2000 and the OMU on the RNC 8.2.1 Networking Diagram

8.2.2 Data Planning

8.2.3 Data Configuration

I. Data Configuration on the RNC

Add an IP address of the EMS. ADD EMSIP: EMSIP="10.30.30.30", MASK="255.255.255.0", OMUIP="10.161.215.242", OMUMASK="255.255.255.0"; Add the route to the IP address of the EMS on the OMU. Before the configuration,

you can use the LST OMUIPRT command to check whether the route to the IP address of the EMS exists in the route table. If yes, the route addition is unnecessary. Generally, when the network gateway is configured for the OMU, a route to the network gateway (that is, the next hop) is automatically generated. ADD OMUIPRT: RTDEST="10.30.30.30", RTDESTMASK="255.255.255.0", NEXTHOP="10.161.215.1";

II. Route Configuration Requirements on the M2000

Add the route to the external virtual IP address of the OMU. Before the configuration, you can check whether the route exists in the route table. If yes, the route addition is unnecessary.

Generally, a route to the network gateway (that is, the next hop) is automatically generated.

Data Item RNC M2000 Server Data Source External virtual IP address of the OMU


IP address of the external network gateway of the OMU

10.161.215.1/24 –

IP address of the EMS – 10.30.30.30/24 IP address of the network gateway of the M2000 server

10.30.30.1/24

Destination Gateway

III. Configuration Requirements of Devices Between the M2000 and OMU

Configure routes (for example, host routes, network segment routes, and default routes) to the IP address of the EMS and the external virtual IP address of the OMU on layer 3 routers between the M2000 and OMU.

8.3 OM Channels Between the M2000 and NodeB Not Through the RNC 8.3.1 Networking Diagram

OM packets from the M2000 to the NodeB do not pass through the internal devices of the RNC. This networking is recommended in IP over Ethernet mode for it uses fewer transport resources of the Iub interface and reduces the traffic between boards of the RNC.

8.3.2 Data Planning

10.161.215.0/24 10.161.215.1

Data Item IP Address/Mask Data Source OM IP address on the NodeB 30.30.30.30/30 Network planning

Interface IP address on the NodeB 20.20.20.20/24

IP address of the network gateway on the NodeB

20.20.20.2/24

Extern virtual IP address of OMU 10.161.215.242/24


I. Add an OM IP address on the NodeB, which is used for the OM channel of the NodeB.

ADD UNODEBIP: NODEBID=1, NBTRANTP=IPTRANS_IP, NBIPOAMIP="30.30.30.30", NBIPOAMMASK="255.255.255.252", IPSRN=0, IPSN=18, IPLOGPORTFLAG=YES, IPLPN=10, VLANFLAG=ENABLE, VLANID=100, VLANPRI=4; // The VLAN ID and VLAN priority is configured for the OM channel on the NodeB. If the VLAN ID is not added on the OM channel, the configuration is unnecessary.

II. Add the IP attribute for the NE management system. The IP address of the EMS serves as the IP address of the M2000.

ADD EMSIP: EMSIP="10.30.30.30", MASK="255.255.255.0", OMUIP="10.161.215.242", OMUMASK="255.255.255.0";

III. IP Route Configuration

IP routes are not configured on the RNC for the OM packets from the M2000 to the NodeB does not pass through the RNC.


I. Add the OM IP address for the NodeB to operate and maintain channels.

ADD OMCH: IP="30.30.30.30", MASK="255.255.255.252", PEERIP="10.30.30.30", PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BASE_BOARD, BRT=NO;

If the OM IP address and the interface IP address on the NodeB are on the same network segment, run the SET ETHPORT command to set ARP Proxy to ENABLE. If the M2000 works in two-node cluster mode, the IP address of the EMS is fixed and Peer IP is set to EMSIP. If the M2000 works in a remote two-node cluster mode, the IP address of the EMS is float and it is recommended to set Peer IP to the IP address of the gateway IP address on the NodeB.

II. IP Route Configuration

Add the route to the IP address of the EMS. Before the configuration, you can run the LST IPRT command to check whether the route exists in the route table on the corresponding transmission interface board. If yes, the route addition is unnecessary. ADD IPRT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.30.30.30", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.2";

III. VLAN/VLAN Priority/DSCP Configuration

According to the planning of the existing network, see Chapter 3 for the configuration.

8.3.5 Route Configuration Requirements on the M2000

I. IP Route Configuration

IP address of the EMS 10.30.30.30/24 IP address of the network gateway of the M2000 server

10.30.30.1/24

Add the route to the OM IP address of the NodeB. Before the configuration, you can check whether the route exists in the route table on the M2000. If yes, the route addition is unnecessary.

Generally, a route to the network gateway (that is, the next hop) exists on the M2000.

8.3.6 Configuration Requirements of Devices Between the M2000 and OMU

I. Route Configuration Requirements

Configure routes (for example, host routes, network segment routes, and default routes) to the IP address of the EMS and the OM IP address of the NodeB on layer 3 routers between the M2000 and NodeB.

II. VLAN/VLAN Priority/DSCP Configuration Requirements

You need to configure the VLAN, VLAN priorities, and DSCP values used during the planning.

8.4 OM Channels Between the M2000 and NodeB Through the RNC 8.4.1 Networking Diagram

Destination Gateway 30.30.30.30/32 10.161.215.1

OM packets from the M2000 are transmitted on the route to the RNC and pass through the OMU, SCU, and Iub interface board in the RNC. This networking mode is applicable to the ATM networking and IP over PPP/MP networking.

In IP over Ethernet networking, if the Iub interface requires the VLAN but the VLAN ID is not carried on any intermediate transmission device, you can consider to adopt this networking mode.

8.4.2 Data Planning



ADD NODEBIP: NODEBID=1, NBTRANTP=IPTRANS_IP, NBIPOAMIP="30.30.30.30", NBIPOAMMASK="255.255.255.252", IPSRN=0, IPSN=18, IPLOGPORTFLAG=YES, IPLPN=10, VLANFLAG=ENABLE, VLANID=100, VLANPRI=4; // The VLAN ID and VLAN priority is configured for the OM channel on the NodeB. If the VLAN ID is not added on the OM channel, the configuration is unnecessary.

II. Add the IP attribute for the NE management system. The IP address of the EMS serves as the IP address of the M2000.

ADD EMSIP: EMSIP="10.30.30.30", MASK="255.255.255.0", OMUIP="10.161.215.242", OMUMASK="255.255.255.0";

III. IP Route Configuration

Configure the route to the OM IP address of the NodeB on the Iub interface board. That is, you can configure the host route or network segment route according to the network planning. ADD IPRT: SRN=0, SN=18, DSTIP="30.30.30.30", DSTMASK="255.255.255.255", NEXTHOP="10.10.10.2", PRIORITY=HIGH, REMARK="to NodeB OMIP"; Configure the route to the IP address of the EMS on the Iub interface board.

After the ADD EMSIP command is run, a network segment route is automatically generated. The size of the route is the result of the AND operation of the added IP

Data Item IP Address/Mask Data Source OM IP address on the NodeB 30.30.30.30/30 Network planning

Interface IP address on the NodeB 20.20.20.20/24

IP address of the network gateway on the NodeB

20.20.20.2/24

IP address of the network gateway on the RNC

10.10.10.2/24

Interface IP address on the RNC 10.10.10.1/24

External virtual IP address of the OMU

10.161.215.242/24

IP address of the EMS 10.30.30.30/24

IP address of the network gateway of the M2000 server

10.30.30.1/24

address of the EMS and the mask. Configure the route to the OM IP address of the NodeB on the OMU.

After the ADD NODEBIP command is run, a host route is automatically generated. Configure the route to the IP address of the EMS on the OMU. Before the

configuration, you can run the LST OMUIPRT command to check whether the route to the IP address of the EMS exists in the route table. If yes, the route addition is unnecessary. Generally, when the network gateway is configured on the OMU, a route whose next hop is the IP address of the gateway is automatically generated. ADD OMUIPRT: RTDEST="10.30.30.30", RTDESTMASK="255.255.255.0", NEXTHOP="10.161.215.1";





ADD OMCH: IP="30.30.30.30", MASK="255.255.255.252", PEERIP="10.30.30.30", PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BASE_BOARD, BRT=NO;

If the OM IP address and the interface IP address on the NodeB are on the same network segment, run the SET ETHPORT command to set ARP Proxy to ENABLE. If the M2000 works in local two-node cluster mode and the IP address of the EMS is fixed, set Peer IP to EMSIP. If the M2000 works in remote two-node cluster mode and the IP address of the EMS is float, it is recommended to set Peer IP to the gateway IP address on the NodeB.

II. IP Route Configuration

Add the route to the IP address of the EMS. Before the configuration, you can run the LST IPRT command to check whether the route exists in the route table on the corresponding transmission interface board. If yes, the route addition is unnecessary. ADD IPRT: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.30.30.30", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="20.20.20.2";

III. VLAN/VLAN Priority/DSCP Configuration


8.4.5 Route Configuration Requirements of Devices Between the M2000 and OMU

Configure routes (for example, host routes, network segment routes, and default routes) to the IP address of the EMS and the OM IP address of the NodeB on layer 3 routers between the M2000 and NodeB.

8.5 Active/Standby OMCH Configuration on the NodeB

8.5.1 Application Scenario

Presently, active/standby OMCH configuration is supported only when the NodeB uses an ATM_IP dual-stack network structure. The NodeB selects the active OMCH as the activated OMCH after being started. If no active OMCH is available, the standby OMCH does not work as the activated OMCH automatically. The result of the DSP OMCH command shows NULL under the activated OMCH. Therefore, one active OMCH must be configured during initial configuration.

8.5.2 Configuration on the RNC

Configure two OM channels. One OM channel is carried on IP over Ethernet; the other is carried on ATM. The configuration in the existing network is based on the planning.

ADD UNODEBIP: NODEBID=100, NBTRANTP=ATMANDIPTRANS_IP, NBIPOAMIP="30.30.30.30", NBIPOAMMASK="255.255.255.252", IPSRN=0, IPSN=18, IPLOGPORTFLAG=YES, IPLPN=10, NBATMOAMIP="40.40.40.40", NBATMOAMMASK="255.255.255.252", ATMSRN=0, ATMSN=14, VLANFLAG=DISABLE;

8.5.3 Configuration on the NodeB

ADD OMCH: FLAG=MASTER, IP="30.30.30.30", MASK="255.255.255.252", PEERIP="10.30.30.30", PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=7, SBT=BASE_BOARD, BRT=NO; // The primary OM channel is carried on IP over Ethernet;

ADD OMCH: FLAG=SLAVE, IP="40.40.40.40", MASK="255.255.255.252", PEERIP="10.30.30.30", PEERMASK="255.255.255.0", BEAR=ATM, SRN=0, SN=7, JNRSCGRP=DISABLE, SBT=BASE_BOARD, PT=IMA, PN=0, VPI=1, VCI=33, RU=KBPS, ST=UBR+, MCR=64, PCR=512; // The spare OM channel is carried on ATM.

9 Reference List

Product manuals, such as the Initial Configuration Guide and Product Description RAN Feature Configuration Specification in the Transmission Layer RAN10 V2 IPRAN Deployment Guide

Date post:	27-Oct-2014
Category:	Documents
Upload:	fmobile0
View:	442 times
Download:	8 times

IP RAN

Documents