IPRAN Deployment Guide V210-20090303

(1)

Intended Audience

INTERNAL Product

Version

V200R0010

Department WCDMA UMTS

Maintenance Dept

Document Version

IPRAN Deployment Guide V210

Prepared by Transport Team of UMTS

Maintenance Dept

Date 2008-08-25

Reviewed by Transport Team of UMTS Maintenance Dept

Date 2008-08-25

Reviewed by Transport Team of UMTS Maintenance Dept

Date 2008-08-25

Approved by Date

Huawei Technologies Co., Ltd.

(2)

Revision Record

Date Revision

Version

Description Author

2008-06-16 V1.0 Initial draft Transport Team of

UMTS Maintenance Dept

2008-08-01 V1.1 Modified on the basis of test and review results

Transport Team of UMTS Maintenance Dept

2008-08-21 V1.2 Modified on the basis of review results by Maintenance Dept

Transport Team of UMTS Maintenance Dept

(3)

(4)

Tables

Table 2.1Hardware requirements ...12

Table 2.2Version requirement ...13

Table 2.3Comparison of RNC IP interface boards ...13

(5)

Figures

Figure 1.1PPP frame format ...8

Figure 1.2IPHC compression range ...8

Figure 1.3Position of the M3UA in each interface protocol stack ...16

Figure 1.4Principle of multi-home ...18

Figure 1.5PDH/SDH-based IPRAN L2 networking ...24

Figure 1.6SDH-based IPRAN L2 networking ...24

Figure 1.7MSTP-based IPRAN L2 networking ...25

Figure 1.8Data network-based IPRAN L2 networking ...26

Figure 1.9L3 networking of RNC directly connecting to one router ...27

Figure 1.10L3 networking of RNC directly connecting to two routers ...28

Figure 1.11L3 networking with the load sharing ...29

Figure 1.12IPRAN networking in the hybrid transport - Iub...30

Figure 1.13IPRAN networking in the ATM/IP dual-stack transport - Iub...31

Figure 1.14 Iub interface protocol stack ...42

Figure 1.15IP planning of Ethernet-based L3 networking ...47

Figure 1.16IP RAN hybrid transport networking ...52

Figure 1.17IP planning of Ethernet-based L3 networking ...53

Figure 1.18E1-based IP planning ...53

Figure 1.19Dual stack transport networking...59

Figure 1.20ATM configuration planning...59

Figure 1.21IP address planning for layer 3 networking over Ethernet...60

Figure 1.22IP address planning for layer 2 networking over Ethernet...60

Figure 1.23IP protocol stack of IU-PS interface...92

Figure 1.24IP protocol stack of IU-CS interface...93

Figure 1.25IP protocol stack of IUR interface...93

Figure 1.26IUPS data planning ...94

(6)

Figure 1.28ASP-SGP direct connection networking ...96

Figure 1.29ASP-SGP transfer networking ...96

Figure 1.30IUCS data planning ...100

Figure 1.31IUR data planning ...104

Figure 1.32Maintaining NodeB by the M2000 Through the RNC...113

Figure 1.33Maintaining the NodeB directly by the M2000 ...116

Figure 1.34Initial address application in the scenario without using DHCP Relay ...121

Figure 1.35Server-Client networking with using the Relay ...122

Figure 1.36Initial address application in the scenario using the DHCP Relay ...122

(7)

IPRAN Deployment Guide

Keywords: IPRAN, PPP, FE, SCTP, IPPATH

Abstract: This document describes the basic principle, basic networking, deployment preparation, basic configuration procedure, precautions, principles and configurations of the DHCP remote debugging of the WCDMA IPRAN.

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:

Abbreviations Full Name

PPP Point-to-Point Protocol

DHCP Dynamic Host Configuration

Protocol

OSPF Open Shortest Path First

RIP Route Information Protocol

ISIS Intermediate

System-Intermediate System

WFQ Weighted Fair Queuing

Chapter 1 Overview

1.1 Introduction to the V210 IPRAN

In V210, the Iub, Iur, and Iu interfaces are carried over the IP transport network. An operator can use the existing IP networks for the transport expansion. The network construction cost is saved. In addition, the IP network provides a variety of access modes and provides the sufficient transport bandwidth for high speed data services (for example, HSDPA).

(8)

With the comparison to V18 and V29, the new IPRAN functions in the V210 are as follows:

1.1.1 FP MUX

1. Principles

The frame protocol multiplexing (FPMUX) multiplexes several small FP PDU frames (sub-frame) that should be transmitted independently to one UDP/IP frame header. As a result, a number of UDP/IP headers are saved. Hence, the transport efficiency increases.

The FP MUX is applicable to only the user plane in the IPRAN Iub interface.

2. Protocol

The FP MUX is the protocol defined by Huawei.

3. Command

//At the RNC side:

ADD IPPATH: FPMUX=YES, SUBFRLEN=127, MAXFRAMELEN=270, FPTIME=2; By default, the FP MUX is disabled.

After the FP MUX is enabled, the default parameters are as follows:  FPMux maximum sub frame length (SUBFRLEN)=127Bytes

 FPMux maximum multiplexing frame length (MAXFRAMELEN)=127Bytes  Multiplexing maximum delay (FPTIME) =2ms

// At the NodeB side:

ADD IPPATH: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE, FPMUXSWITCH=ENABLE, SUBFRAMELEN=127, FRAMELEN=270, TIMER=1;

By default, the FP MUX is disabled.

After the FP MUX is enabled, the default parameters are as follows:  FPMux maximum sub frame length (SUBFRAMELEN)=127Bytes  FPMux maximum multiplexing frame length (FRAMELEN)=127Bytes  Multiplexing maximum delay (TIMER) = 1ms

(9)

1.1.2 IPRAN Header Compression

1. Principles

The IPRAN header compression improves the transport efficiency by compressing partial fields of PPP frames.

Figure 1.1 PPP frame format

The PPP frame header compression algorithm implements the following:

 Address and control field compression (ACFC): The address and control field is the constant value (0XFF03) and is not transported every time. After the PPP link is configured with the Link Control Protocol (LCP), the subsequent packet address and control fields can be compressed.

 Protocol field compression (PFC): The PFC can compress two-byte protocol field to one byte. The system judges whether the protocol field is one byte or two bytes according to the last significant bit (LSB) of the first byte in the protocol field. If the LSB is 1, it indicates that the protocol field is two bytes in length. If the LSB is 0, it indicates that the protocol field is only one byte in length. For example, the first byte of the protocol field is 0x00, it can be compressed.

 IP Header Compression (IPHC): The IPHC compresses the IP/UDP header of the PPP frame.

Compression range PPP

header IP header _headerUDP

Application

data PPP tail

(10)

IPHC principles:

1) The header field remaining unchanged is not carried in each packet that is sent. The header field changed according to the designated mode can be replaced by fewer bits.

2) If the header context of the packet stream is established at both ends of a link, only the changed header field and the corresponding context tag are transferred. The original header can be recovered according to the context and changed fields.

Terms:

Context: It is the status table of the synchronization maintenance of the same packet stream by the compresser and decompresser. The compresser uses it to compress the packet header. The decompresser uses it to recover the compressed packet header.

2. Protocol  ACFC: RFC 1661  PFC: RFC 1661  IPHC: RFC 2507 and RFC 3544 3. Command  At the RNC side:

ADD PPPLNK: MUX=Disable, IPHC=UDP/IP_HC, PFC=Enable, ACFC=Enable; By default, three algorithms are enabled.

 At the NodeB side:

ADD PPPLNK: IPHC=ENABLE, PFC=ENABLE, ACFC=ENABLE; By default, three algorithms are enabled.

1.1.3 IPRAN Fault Detection

1. Principles

At present, the RNC supports the ARP detection and BFD detection for detecting the transport link from the RNC to the peer equipment:

 Address resolution protocol (ARP) detection

(11)

peer equipment by sending ARP requests to the peer equipment. Every the fixed duration, the RNC constructs an ARP request packet to send to the network. The destination address of the packet is the peer address to be detected. The RNC determines the continuity of the link by judging whether the response from the destination address is received.

The ARP detection is applicable to only the direct connection detection whose both ends are on the same network segment.

Features of the ARP detection are as follows:

 The ARP is the basic protocol, without depending on the peer equipment. The detection starts at one single end.

 The detection state is related to the port state. The port switchover is triggered if a fault is detected. The system deletes the route whose detection address is the next hop. The upper layer service selects other available channels.

 The ARP detection supports the independent port detection, only active port detection, and active/standby port simultaneous detection.

 When the active and standby ports are detected at the same time, the IP address of the active and standby ports should not be on the same network segment.

 Bidirectional forwarding detection (BFD)

The method of the BFD detecting the link continuity: The system originates the handshake packets from both ends and determines the link continuity according to the handshake result (success or failure).

The V210 RNC implements the single-hop BFD (SBFD) and multi-hop BFD (MBFD):

 SBFD:

The SBFD is applicable to only the direct connection detection whose both ends are on the same network segment, which is the same as the ARP detection. The features of the SBFD are as follows:

 The both ends must start at the same time. The detection duration at both ends must be configured to be equivalent. At present, only the asynchronous mode is supported.

 The detection state is related to the port state. The port switchover is triggered if a fault is detected. The system deletes the route whose detection address is the next hop. The upper layer service selects other available channels.

 The independent port detection is supported. Only the active port is detected. The active/standby port simultaneous detection is not supported.

(12)

 MBFD:

The MBFD is applicable to the non direct connection end-to-end detection in the scenario where signals pass more than one network nodes. The features of the MBFD are as follows:

 The both ends must start at the same time. The detection duration at both ends must be configured to be equivalent. At present, only the asynchronous mode is supported.

 The detection state is not associated. If a fault is detected, only an alarm is reported.

 The MBFD does not depend on a port. The IP (DEVIP or ETHIP) of the active and standby boards can be used as the local address of the multi-hop BFD. In addition, the peer IP address and any local IP address should not be on the same network segment.

2. Protocol

ARP protocol and BFD protocol

3. Commands

By default, ARP detection, SBFD, or MBFD is disabled.  ARP detection (three modes)

1) Active/standby port simultaneous detection

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=ARP, PN=0, MODE=REDPORT, GATEWAY="100.10.10.20", BAKIP="100.10.20.10", BAKMASK="255.255.255.0", BAKGATEWAY="100.10.20.20", ARPTIMEOUT=3, ARPRETRY=3;

2) Active port detection

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=ARP, PN=0, MODE=PRIMARYCHKONLY, GATEWAY="100.10.10.10", ARPTIMEOUT=3, ARPRETRY=3;

3) Independent port detection

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=ARP, PN=0, MODE=INDPORT, GATEWAY="100.10.10.10", ARPTIMEOUT=3, ARPRETRY=3;

Default parameters of the ARP detection:  ARPTIMEOUT: 300 ms

(13)

 ARPRETRY: 3 times

 SBFD

1) Independent port detection

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=SBFD, PN=0, MODE=INDPORT, GATEWAY="100.10.10.20", MINTXINT=30, MINRXINT=30, BFDDETECTCOUNT=3;

2) Active port detection

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=SBFD, PN=0, MODE=PRIMARYCHKONLY, GATEWAY="100.10.10.20", MINTXINT=30, MINRXINT=30, BFDDETECTCOUNT=3;

 MBFD

STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=MBFD,

MBFDLOCALIP="100.10.10.10", GATEWAY="100.20.20.20", MINTXINT=30, MINRXINT=30, BFDDETECTCOUNT=3

The default parameters of the BFD are as follows:  Min interval of BFD packet send (MINTXINT): 30 ms  Min interval of BFD packet receive (MINTXINT): 30 ms  BFDDETECTCOUNT: 3 times

1.2 Availability

1.2.1 Requirements for NEs

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

Table 2.1 Hardware requirements

IP feature requirement NodeB RNC CN Data configuration √ √ √ Hardware requirements WMPT/UTRP PEUa/POUa/UOIa_IP/FG2a/GOUa

(14)

1.2.2 Supporting Versions

Table 2.2 Version requirement

Product Supporting Version

RNC BSC6810 _{BSC6810V200R010C01B051 and later}

NodeB DBS3836 _{V200R010C01B040 and later}

BTS3836/ BTS3836A _{V200R010C02B040 and later} CME

M2000

1.2.3 Other Support

1. RNC side

If the IP RAN feature is required, the corresponding IP interface boards should be added at the RNC and NodeB sides. At the RNC side, the interface boards supporting the IP interface are as follows:

 FG2a: RNC packet over electronic 8-port FE or 2-port GE Ethernet Interface

unit REV:a

 GOUa: RNC 2-port packet over Optical GE Ethernet Interface Unit REV:a  PEUa: RNC 32-port Packet over E1/T1/J1 Interface Unit REV:a

 UOIa_IP: RNC 4-port Packet over Unchannelized Optical STM-1/OC-3c Interface

unit REV:a

 POUa: RNC 2-port packet over channelized Optical STM-1/OC-3 Interface Unit

REV:a

The following table describes the features and functions of these boards.

Table 2.3 Comparison of RNC IP interface boards

Board Type _Description

FG2a  Enabling IP over Ethernet

 Providing eight FE ports and two GE electrical ports  Providing IP over FE/GE

(15)

GOUa  Enabling IP over Ethernet  Providing two GE optical ports  Providing IP over GE

 _{Supporting interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub}

PEUa  Supporting IP over E1/T1/J1

 Providing 32 channels of IP over PPP/MLPPP over E1/T1

 _{Providing 128 PPP links or 64 MLPPP groups, each MLPPP group}

containing 8 MLPPP links

 Providing the fractional IP function  Providing the timeslot cross-connection

 Obtaining clock signals from the Iu interface and exporting timing signals to

the GCUa/GCGa board

 Exporting timing signals to the NodeB

 Supporting interfaces such as Iu-CS, Iur, and Iub

UOIa_IP  _{Providing 4 unchannelized STM-1/OC-3c optical interfaces}  Supporting IP over SDH/SONET

 Supporting PPP (LCP/NCP/IPCP)/PPPMUX protocol

 Supporting interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub

 Obtaining clock signals from the Iu interface and exporting the clock

signals to the GCUa/GCGa board

 Exporting clock signals to the NodeB

POUa  Providing two optical interfaces over channelized optical STM-1/OC-3

transmission based on IP protocols

 Supporting IP over E1/T1 over SDH/SONET

 Providing Multi-Link PPP. In E1 transmission mode, 42 MLPPP groups are

provided, and in T1 transmission mode, 64 MLPPP groups are provided.

 Providing 126 E1s or 168 T1s

 Supporting interfaces such as Iu-CS, Iur, and Iub

 Obtaining clock signals from the Iu interface and exporting the clock

signals to the GCUa/GCGa board

 _{Exporting timing signals to the NodeB}

2. At the NodeB side:

(16)

 WCDMA Main Processing & Transmission unit board (WMPT): Provides one

4-channel E1 port, one FE electrical port, and one FE optical port. Supports ATM and IP.

 Universal Transmission Processing unit (UTRP): Provides 8 E1s/T1s. The

board supports ATM and IP protocols.

The following table describes the functions of these boards.

Table 2.4 Functions of NodeB IP transmission boards

Board Type Description

WMPT Supporting IP over Ethernet and IP over E1/T1/J1

Providing one 4-channel E1 port, one FE electrical port, and one FE optical port

Providing 8-channel IP over PPP/MLPPP over E1/T1

Providing 8 PPP links or 4 MLPPP groups (each MLPPP group contains up to eight MLPPP links)

Providing Fractional IP function

Providing the timeslot cross-connection function Supporting the line clock extraction

Supporting the Iub interface

UTRP Supporting IP over E1/T1/J1

Providing 8-channel E1/T1 interfaces

Providing 16-channel IP over PPP/MLPPP over E1/T1

Providing 16 PPP links or 4 MLPPP groups (each MLPPP group contains up to 16 MLPPP links)

Providing Fractional IP function

Providing the timeslot cross-connection function Supporting the line clock extraction

(17)

Chapter 2 Introduction to Basic

Protocols

2.1 M3UA

Figure 1.3 Position of the M3UA in each interface protocol stack

2.1.1 Principles and Relevant Concepts

MTP3 User Adaption Layer (M3UA): It is the adaption layer protocol of MTP level-3 users. The M3UA provides the conversion between the signaling point code (SPC) and IP address. The M3UA is applicable to the transmission of the SS7 protocol between the SoftSwitch and signaling gateway (SG). The M3UA supports the transmission of MTP level-3 user message in the IP network, including but not limited to, ISUP, TUP, and SCCP messages. The RANAP is the SCCP user protocol. Their messages are transparently transmitted in the M3UA protocol layer as the SCCP payload.

Concepts related to the M3UA:

Application server (AS): It serves the logical entity of specific routing keywords. The AS processes the call procedure of all SCN trunks identified by SS7 SIO, DPC, OPC, and CIC. The AS contains a group of unique AS process, among them, one or two are in the active state.

(18)

Application server process (ASP): It is the process instance of the AS. One ASP functions as one active or standby process of the AS. One ASP contains one SCTP endpoint and may be configured to process signaling services in one or more ASs.

IP server process (IPSP): It is the process instance based on the IP application. Essentially, the IPSP is the same as the ASP. The IPSP uses the point to point M3UA, instead of SG services.

Signaling gateway (SG): It is the signaling proxy for receiving and sending signaling messages at the edge between the SS7 network and IP network.

Signaling gateway process (SGP): It is an instance of the signaling gateway process. The SGP is the activation, backup, load-sharing, or broadcast process of the signaling gateway.

Switched Circuit Network (SCN): It is the network carrying services by using the channel with the pre-defined bandwidth.

Media gateway (MG): When a media stream flows from the SCN to the PS network, the MG terminates the SCN media stream and packs media data (if media data is not based on the data packet form), and transfers the packed service to the packet-based network. When a media stream flows from the PS network to the SCN, the system implements the reversal procedure.

Media gateway controller (MGC): The MGC is responsible for processing the resource registration and management on the MG.

2.1.2 Functions of the M3UA

Functions of the M3UA are as follows:

 Supporting the transport of all MTP3 user message (ISUP, TUP, or SCCP)  Supporting the seamless interaction of the same MTP3 user protocol in

different networks (for example, the interaction between the ISUP in the SCN and the ISUP in the IP network)

 Supporting the SCTP connection and service management between the SG

and MGC (or the database in the IP network), and between IPSPs

 Supporting the redundancy protection (active/standby connection or load

sharing) between the SG and MGC (or the database in the IP network), and between IPSPs

 Supporting the interworking capability of the MTP3 network management

function and address translation mapping (SS7<->IP)

(19)

congestion control

 Supporting the seamless network management interaction and active

connection control

2.1.3 Protocol

RFC 3332

2.1.4 Configuration Sequence at the RNC Side

The configuration sequence at the RNC side is as follows:

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

2.2 SCTP

For the SCTP principles, see V18 Deployment Guide. This section describes the multi-homed SCTP.

2.2.1 Principles of Multi-Homed SCTP

The multi-homed SCTP means that one device has multiple IP addresses.

Figure 1.4 Principle of multi-home

Path: It is the route of data transmission. In the IP network, the transmission path is related to the destination IP address and the source IP address. Actually, a path is determined by the destination address and source address. The SCTP supports the

(20)

multi-home, that is, multiple IP addresses can be used for the transport. The conservative policy is used. In the case of the connection setup, the system selects one active path (active source address and active destination address) for the transport. When the active path is unreachable or the retransmission is required, another path is used.

Multi-homed endpoint: In one endpoint, if multiple transport addresses are used as the destination address, the endpoint is considered as the multi-homed endpoint.

2.2.2 SCTP Dual-Homed Mechanism Supported by the RNC

The multi-homed SCTP supported by V210 RNC refers to two local addresses and two peer addresses. As shown in Figure 2-2, the local system has IP A and IP B, and the peer system has IP 1 and IP 2.

Active destination address:

The Path is maintained by maintaining the state of the destination address. In the case of multiple destination addresses, one active destination address is maintained. The active destination address is preferred for sending data.

Maintenance path:

At present, only two maintenance paths are available. When one is unavailable, the system finds the next available path through sending the heartbeat. In the path that is not maintained, the system does not send the heartbeat actively.

2.2.3 Protocol

For the relevant protocol, see the RFC2960. For the dual-homed SCTP, see "

6.4 Multi-homed SCTP Endpoints

".

2.3 Others

For the principles of the TCP, UDP, PPP, ARP, NAT, VLAN, and TRACERT, see V18 Deployment Guide.

(21)

Chapter 3 Introduction to the Networking

3.1 V2 Backup Policy

3.1.1 Backup Mode at the RNC Side

Two backup modes are available in the RNC: board backup and port backup

 Board backup

In the board backup mode, one board is active and the other is standby. The service can be processed by the active board or by active and standby boards. When the active board is faulty, the RNC automatically originates the switchover of the active/standby boards.

 Port backup

In the port backup mode, one port is active and the other is standby. Services are transported through the active port only. When the active port is faulty, the RNC automatically originates the switchover of the active/standby ports.

1. Board backup mode

With the comparison to V29, the board backup and port backup in V210 are independent. If only the board backup is configured, without configuring the port backup, the board is switched over only when the board is faulty.

In the board backup mode, one board is active and the other is standby. The service can be processed by the active board or by active and standby boards (that is, the board is in the active/standby mode and the port is in the load sharing mode).

When the active board is faulty, the RNC automatically originates the switchover of active/standby board.

You can set the board backup relation by running ADD BRD. If Backup is set to Yes, the board backup applies.

2. Port backup mode

(22)

When the active/standby slots in the RNC subrack are configured with two FG2a/GOUa boards, two FG2a/GOUa boards can be set to Board backup;port not backup, or board and port backup.

When FG2a/GOUa boards are set to the board backup, you can configure the FE/GE port backup by running ADD ETHREDPORT.

If the port backup is not configured and only the board backup is configured, the board backup and port load-sharing mode applies.

With the comparison to V29, the Board and port backup bonding is reduced in the IP interface board for the backup mode in V210, and only Board and port backup apart and the board backup and port load sharing mode are available in V210.

 UOIa_IP and POUa boards

When the UOIa is in the board backup mode, the corresponding optical ports (for example, optical port 0 in the active board and optical port 0 in the standby board) in active/standby UOIa are also backed up. The backup mode is MSP 1:1 or MSP 1+1 (single end or dual ends).

When the optical interface of the UOIa is in MSP 1:1 backup, one optical port is active, and the other optical port is standby. The active optical port is responsible for receiving and transmitting data.

In the case of the MSP 1+1 backup of the optical port in the UOIa board, one optical interface is active and the other is standby. The data processing of the backup mode: The active and standby optical ports send data at the same time, and only the active optical port receives data.

To set the relevant attributes of the MSP backup, run SET MSP. MSP attributes include 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.

3. Impact on the system by the switchover

When the FG2a/GOUa adopts the board backup without the port backup, the switchover of the active/standby board has not impact on existing services.

When the FG2a/GOUa adopts the board backup and port backup, the switchover of the active/standby board has the slight impact on the data transport. The existing service is not interrupted.

If the data traffic of the optical interface is large, the switchover of the active/standby UOIa board has the slight impact on the data transport. The existing service is not interrupted.

(23)

3.1.2 NodeB Side

1. NodeB supports only the board backup mode, without supporting the port backup mode

In the board backup mode, data is configured and processed only in the active board, and the standby board is in the monitoring status. When all used physical links in the active board is in the unavailable state (For example, E1 has the LOS alarm and the FE port is DOWN) and a physical link is available in the standby board, the board can be switched over. In the case of the switchover, the active and standby boards are restarted. When the configurations of the active board are loaded to the standby board, the standby board is upgraded to the active board. In the case of the switchover, the service is interrupted.

In the configuration of the board backup mode, only the CME can be used to generate the configuration file. To query the current board mode, run LST IUBGRP in the LMT. If the board is not configured to the active/standby mode, you can perform configurations by running commands. The specific configuration modes are as follows:

(24)

3.2 Common Networking Modes

3.2.1 Layer-2 Networking Mode

(25)

connected to the SGSN (Iu interface) through the LAN. The RNC is connected to the RNC (Iur interface) through the LAN. The interface address of each NE is on the same network segment.

According to the transport media, the following network modes are available:

1. IP over E1/T1 over PDH/SDH (Iub interface)

Figure 1.5 PDH/SDH-based IPRAN L2 networking

 The RNC and NodeB access the transport network through the E1/T1. The data is transmitted in the IP over MLPPP or PPP over E1/T1 mode.

 The NodeB can obtain the line clock over E1/T1.

 Backup mode: The PEUa is set to active/standby board by running ADD BRD. The active/standby PEUa board is connected to the peer equipment through the Y-shaped E1/T1 cable.

 The RNC and NodeB use the header compression algorithm to improve the transport efficiency.

2. IP over SDH (Iub interface)

Figure 1.6 SDH-based IPRAN L2 networking

 The RNC accesses the transport network through the channelized STM-1 on the POUa. The NodeB accesses the transport network through the E1/T1. The data is

(26)

transmitted in IP over MLPPP or PPP over E1/T1 mode.  NodeB can obtain the line clock over E1/T1.

 Backup mode: The POUa is set to the active/standby board by running ADD BRD. The optical interface in the board is set to MSP 1:1 or MSP 1+1 backup mode.  The RNC and NodeB use the header compression algorithm to improve the transport efficiency.

3. MSTP-based IP networking (Iub interface)

Figure 1.7 MSTP-based IPRAN L2 networking

 The RNC accesses the MSTP network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The NodeB accesses the transport network through the FE electrical port or optical port. The data is transmitted in the IP over Ethernet mode.

 The NodeB can extract the clock from the MSTP network over E1/T1, or obtain the clock source from the GPS/IP Clock Server.

 Backup mode: The FG2a/GOUa is set to the active/standby board, port backup (Board and port backup apart) or board backup while the port in the load-sharing mode.

 Transport efficiency: Multiple NodeBs share the VC Trunk bandwidth to use the transport network resources to the maximum extent.

 QoS: The RNC and NodeB support the mapping of IEEE 802.1p/q, DSCP, and VLAN Priority. The transport network supports the IEEE 802.1p/q to schedule the QoS of different services.

(27)

4. Data network-based IP networking (IUB/IUR/IUCS/IUPS)

The RNC is connected to the NodeB (Iub interface) through the L2 data network. The RNC is connected to the SGSN (Iu interface) through the L2 data network. The RNC is connected to the RNC (Iur interface) through the L2 data network. The interface address of the interconnected NE is on the same network segment.

Figure 1.8 Data network-based IPRAN L2 networking

 The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The NodeB/NRNC/MGW/SGSN accesses the L2 data network through the FE electrical port or optical port.

 The NodeB can extract the clock from the ATM transport network over E1/T1, or obtain the clock source from the GPS/IP Clock Server.

 Backup mode: The FG2a/GOUa is set to the active/standby board, port backup (board backup separated from port backup) or board backup while the port in the load-sharing mode.

 QoS: The RNC, NodeB, core network equipment, and L2 support IEEE 802.1p/q, that is, support the VLAN and VLAN priorities for the QoS scheduling of the data network. The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss ratio < 0.05%

3.2.2 Layer-3 Networking Modes

1. RNC directly connecting to one router

(28)

The RNC is connected to the SGSN (Iu interface) through the L3 switching network. The RNC is connected to the RNC (Iur interface) through the L3 switching network. The interface address of each NE is in different network segments.

Figure 1.9 L3 networking of RNC directly connecting to one router

 The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. The data is transmitted in the IP over Ethernet mode.

 The NodeB can extract the clock over E1/T1, or obtain the clock source from the GPS/IP Clock Server.

 Backup mode: The FG2a/GOUa is in the board backup and port backup. The active and standby ports are connected to two ports of one router/L3 switch. The two ports in the router/L3 switch are configured in the same VLAN. One VLAN interface address is configured as the RNC gateway.

 QoS: The RNC, NodeB, and core network equipment support the mapping of IEEE 802.1p/q, DSCP, and VLAN Priority. The data network supports the MPLS TE, MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the service QoS. The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss ratio < 0.05%

(29)

2. RNC directly connecting to two routers

Figure 1.10 L3 networking of RNC directly connecting to two routers

 Backup mode: The FG2a/GOUa is in the board backup and port backup. The board backup and port backup are independent of each other.

The active and standby ports of RNC are respectively connected to two ports of the active and standby PEs. The RNC is connected to the data transport network through the PE.

The active and standby ports of the RNC share one IP address (IP1-1). Two ports of the active and standby PE are configured in the same VLAN, with the configuration of the VRRP. The VRRP virtual IP (IP-0) functions as the RNC gateway.

 QoS: The RNC, NodeB, and core network equipment support the mapping of IEEE 802.1p/q, DSCP, and VLAN Priority. The data network supports the MPLS TE, MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the QoS of different services. The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss ratio < 0.05%

(30)

3. Load sharing

Figure 1.11 L3 networking with the load sharing

 Backup mode: The FG2a/GOUa is in the board backup and the port is in the load sharing mode. The double bandwidths are obtained with the reliability guarantee of the board and transport.

Two ports of the active and standby boards in the load sharing are connected to two routers/L3 switch. Two ports in the FG2a/GOUa are respectively configured with the IP address, with the corresponding gateway in the interconnected router/L3 switch.

 Through the routing configuration, the IP load sharing is implemented between any active FE/GE ports.

 Route with the load sharing: Multiple different NEXTHOP routes exist in the network segment to the same destination.

 Traffic in the route with the load sharing is distributed on average.

 The load sharing is in the load sharing mode to ensure the correct time sequence of user flows.

 QoS: The RNC, NodeB, and core network equipment support the mapping of IEEE 802.1p/q, DSCP, and VLAN Priority. The data network supports the MPLS TE,

(31)

MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the QoS of different services. The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss ratio < 0.05%

3.2.3 Hybrid Transport Networking

TDM network

Data network

Figure 1.12 IPRAN networking in the hybrid transport - Iub

 The Iub interface uses the transport network of different QoSs to carry services of different QoSs: The service with high QoS is transported through the dedicated line. The service with low QoS is transported through the low cost transport network (for example, Ethernet).

 The control plane and real-time services and OM services are transported through the TDM with the high QoS.

 Non real-time services are transported through the data network with low QoS.  The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical port or optical port. The data is transmitted in IP over Ethernet mode.

RNC and NodeB access the TDM transport network over E1/T1. The data is transmitted in IP over MLPPP/PPP over E1/T1 mode.

 The NodeB can extract the clock through additionally over E1/T1.

 Backup mode:

The FG2a/GOUa is in the board backup, with the port backup or port load sharing mode. PEUa/POS/UOI_IP is the board backup.

(32)

3.2.4 ATM/IP Dual-Stack Transport Networking

Figure 1.13 IPRAN networking in the ATM/IP dual-stack transport - Iub

 When the bandwidth in the original ATM networking is deficient (in the case of the HSDPA/HSUPA), the IP transport network can be extended. The transport cost is saved and the bandwidth is improved.

 The original ATM networking remains unchanged. The RNC and NodeB access the TDM transport network through the E1/T1.

 The RNC and NodeB access the data transport network through the new IP interface board. The RNC accesses the data network through the GE optical port of the GOUa board or FE/GE electrical port of the FG2a board. The NodeB/NRNC/MGW/SGSN accesses 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 over E1/T1.

 Backup mode: see L2 data networking and L3 data networking.

 QoS: The control plane and real-time services and OM services are transported through the ATM. The non real-time service is transported through the IP.

3.3 Backup Constraint

3.3.1 RNC

1) In the separate mode, the route must be configured in even slots. 2) The backup mode should not be configured in odd slots.

(33)

ports of the active/standby boards function as the active/standby ports. 4) The backup port should not be used. The gateway continuity check can be

started.

5) When at least either of the active and standby ports is configured with IP or port control, two ports are not allowed to be configured as the active and standby ports.

3.3.2 NodeB:

1) Boards supporting the board backup: V210: WMPT/UTRP

V110: NUTI/HBBU. NDTI does not support.

2) The code backup is performed in the NodeB. Hence, the service is interrupted in the case of the switchover.

3) In the backup mode, data is configured only in the active board. By default, the slot with the smaller ID in the backup group is the active board in the initial configuration.

Chapter 4 V210 IPRAN Key Configurations

4.1 Relevant Settings of the IPRAN

4.1.1 RNC Side

1. Set the Ethernet port attribute.

Command: SET ETHPORT

 Set the VLAN tag attribute of the Ethernet port

The VLAN tag attribute of the Ethernet port cannot be set. By default, the setting is HYBRID.

 Set the work mode of the FE/GE port: The work mode at both ends for the interconnection must be consistent.

(34)

SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2, PTYPE=FE, PN=0, AUTO=ENABLE; SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2, PTYPE=FE, PN=0, AUTO=DISABLE, FESPEED=100M, DUPLEX=Full;

//The work mode of the GE port of the FG2 board cannot be configured. By default, the value is 1000M/FULL.

//Set the GE port of the GOUa board to Auto negotiation.

SET ETHPORT: SRN=0, SN=14, BRDTYPE=GOU, PTYPE=GE, PN=0, AUTO=ENABLE; //Set the GE port of the GOUa board to non-auto negotiation. The default value is 1000M/FULL, which cannot be modified.

SET ETHPORT: SRN=0, SN=14, BRDTYPE=GOU, PTYPE=GE, PN=0, AUTO=DISABLE;

 Set the percentage of the OAM minimum assurance bandwidth to the port bandwidth. By default, the value is 0%. The value can be changed according to the planning of the current network.

SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2/GOU, PTYPE=FE/GE, OAMFLOWBW=0;

 Set the MTU. By default, the value is 1500 bytes.

SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2/GOU, PTYPE=FE/GE, MTU=1500,

2. Set the mapping between the DSCP and VLAN PRI.

Command: SET DSCPMAP

SET DSCPMAP: DSCP=X, VLANPRI=X; The default mapping relation is as follows:

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

(35)

3. Set the mapping between the queue of the IP type port and the DSCP

SET QUEUEMAP: Q0MINDSCP=XX, Q1MINDSCP= XX, Q2MINDSCP= XX,

Q3MINDSCP= XX, Q4MINDSCP= XX; The default setting is as follows:

The mapping between the DSCP value range and Q0-Q5 is as follows:

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

1) The IP port types include Ethernet port, PPP link, MP group, and IP logical port. Each IP type port has six service data queues. The priorities of each queue are different. Q0 features the highest priority. Q5 features the lowest priority.

2) Q0MINDSCP - Q4MINDSCP must meet the following conditions:

Q0MINDSCP > Q1MINDSCP > Q2MINDSCP > Q3MINDSCP > Q4MINDSCP

4. Set the DSCP value of the OAM flow

SET QUEUEMAP: SRN=0, SN=14, OAMMINBWKEY=ON, OAMFLOWDSCP=X;

By default, the value is OFF. Note:

1) The OAM flow cannot be transported through Q0-Q5, but transported through private queues.

(36)

the designated OAM flow should not be identical with the DSCP value of any IPPATH.

5. Set the corresponding DSCP of the SCTP link and whether to enable the VLAN.

ADD SCTPLNK: DSCP=X, VLANFlAG=ENABLE, VLANID=X;

Default configurations: DSCP=62. The VLAN is not enabled.

6. Set the corresponding DSCP of the IPPATH and whether to enable the VLAN.

ADD IPPATH: PATHT=X, DSCP=X, VLANFlAG=ENABLE, VLANID=X;

The default setting is as follows:

IPPATH Type DSCP VLANID Flag

HQ_RT 46 Disable LQ_RT 34 HQ_NRT 18 Disable LQ_NRT 10 HQ_HSDPART 38 Disable LQ_HSDPART 30 HQ_HSDPANRT 14 Disable LQ_HSDPANRT 4 HQ_HSUPART 36 Disable LQ_HSUPART 28 HQ_HSUPANRT 12 Disable LQ_HSUPANRT 0 HQ_QOSPATH Null The value is determined according to the configuration in the TRMMAP. Disable LQ_QOSPATH

7. Add the mapping between the destination IP and VLANID

ADD VLANID: IPADDR="X.X.X.X", VLANID=X;

If the VLAN is not enabled in Steps 5 and 6, the following two purposes are achieved by running this command:

(37)

ID.

2) ARP request packets of the destination IP address are labeled with the designated VLAN ID.

8. Set the mapping between the PHB and DSCP

ADD TRMMAP: ITFT=IUB_IUR_IUCS/IUPS, TRANST=IP, EFDSCP=X, AF43 DSCP=X,

AF42 DSCP=X, AF41 DSCP=X, AF33 DSCP=X, AF32 DSCP=X, AF31 DSCP=X, AF23 DSCP=X, AF22 DSCP=X, AF21 DSCP=X, AF13 DSCP=X, AF12 DSCP=X, AF11 DSCP=X, BEDSCP=X;

The default mapping relation is 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.1.2 NodeB Side

1. Set the Ethernet port attribute

Command: SET ETHPORT

Set the work mode of the FE port: The work mode at both ends for the interconnection must be consistent.

(38)

2. Set the priority of the signaling and OM

Command: SET DIFPRI

Related parameters are as follows:

Name Description

Priority Rule Value range: IPPRECEDENCE,DSCP Signal Priority Value range:

0 - 7: when PRIRULE is IPPRECEDENCE, 0 - 63: when PRIRULE is DSCP.

OM Priority Value range:

0 - 7: when PRIRULE is IPPRECEDENCE, 0 - 63: when PRIRULE is DSCP.

The relations between the signaling, service, and DSCP values are as follows: 1) Iub interface signaling data

Signaling data over Iub interface is transported with SCTP. The sending of the DSCP priority in the SCTP protocol package is determined by the DSCP in the Signaling Priority type by running SET DIFPRI.

2) Common channel

The common channel transports control information, with the higher priority. The priority is equivalent to the NCP/CCP data. For services in the common channel, data from the RNC to the NodeB is transmitted through the DSCP on the RT PATH. The data returned from the NodeB to the RNC is transmitted through the DSCP of the Signal Priority by running SET DIFPRI.

3) R99 service (user voice and PS network access data)

The NodeB sends the DSCP priority of these UDP packages. When the connection is established, the RNC notifies the NodeB. The DSCP settings are determined by the RNC.

4) HSDPA

Data from the RNC to the NodeB is the downloaded data. The DSCP value of the HSDPA_IPPATH configured by the RNC determines the DSCP for the data transmitting. The flow control information frame returned from the NodeB to the RNC is uploaded by using the DSCP value of the Signal Priority configured by running SET DIFPRI.

5) HSUPA

The data from the NodeB to the RNC and data from the RNC to the NodeB are transmitted by using the DSCP value sent in the case of the RNC link setup.

(39)

6) OM maintenance data

The OM maintenance data is transported through the TCP. The sending of the DSCP priority in the packages is determined by the DSCP in the OM type by running SET DIFPRI.

Precautions for the configuration:

1) Priority Rule: It has two options: IPPRECEDENCE and DSCP. The recommended configuration is DSCP. The IPPRECEDENCE is labeled by using the priority field in the type of service (TOS) field in the IP header. The DSCP is configured according to the DSCP value of the Diffserv.

One IPPRECEDENCE corresponds to a range of the DSCP value. DSCP range: [A,B) Specific value:

I PPRECEDENCE DSCP

0 000000~001000

1 001000~010000

2 010000~011000

3 011000~100000

4 100000~101000

5 101000~110000

6 110000~111000

7 111000~111111

2) The SIG precedence is configured to be consistent with the DSCP value of the SCTP in the RNC.

3. Set the configuration between the DSCP and VLAN

Command: SET VLANCLASS

In the VLAN configurations, the VLANIDs vary with protocol types. The NodeB distinguishes according to the following rules:

 Protocol type = SCTP: Iub interface signaling data includes only the NCP/CCP data. Correspond to the SIG class by running the command SET VLANCLASS.

SET VLANCLASS: VLANGROUPNO=X, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=X, VLANPRIO=X;

 Protocol type = UDP: Voice, PS network access, and H download. It applies to data of common channels. In addition, the local UDP port number is in the legal range of the NodeB. It corresponds to USERDATA class by running the command SET VLANCLASS.

(40)

SET VLANCLASS: VLANGROUPNO=X, TRAFFIC=USERDATA, SRVPRIO=X, INSTAG=ENABLE, VLANID=X, VLANPRIO=0;

 Protocol type = UDP: The local UDP port number is not in the legal range of the NodeB. It is other applications (for example, TRACERT). It corresponds to OTHER class by running the command SET VLANCLASS.

SET VLANCLASS: VLANGROUPNO=X, TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=X, VLANPRIO=X;

 Protocol type = TCP: Data of OM management and maintenance. It corresponds to the OM class by running the command SET VLANCLASS.

Protocol type = Others: Includes, but not limited to, ICMP, ARP, and DHCP. The value is treated as other types. It corresponds to the OM class by running the command SET VLANCLASS.

SET VLANCLASS: VLANGROUPNO=X, TRAFFIC=OM, INSTAG=ENABLE, VLANID=X, VLANPRIO=X;

4. Set the VLAN based on the next hop (V210)

Command: ADD VLANMAP

Set the VLANID based on the next hop (V210). The configuration methods are as follows:

1) All data is labeled with the same VLAN.

When running the command ADD VLANMAP, select the single VLAN for the VLANMODE. That is, all data with the same next hop address is labeled with the VLAN. ADD VLANMAP: NEXTHOPIP="12.13.14.15", VLANMODE=SINGLEVLAN, INSTAG=ENABLE, VLANID=100, VLANPRIO=1;

2) Label different VLANs according to data types

When running the command ADD VLANMAP, select VLANGRP for the VLANMODE. To set the VLAN in the VLANGRP, run SET VLANCLASS.

ADD VLANMAP: NEXTHOPIP="12.13.14.15", VLANMODE=VLANGROUP,

VLANGROUPNO=0;

According to the correspondence between the service and DSCP, the signaling at the NodeB side, uplink frame of the common channel, the uplink control frame of the HSDPA use the DSCP value of the SIG type by running the command SET DIFPRI. The signaling uses the SCTP. The uplink frame of the common channel and the uplink control frame of the HSDPA use the UDP. Hence, the VLANs should be set respectively.

(41)

5. Example

SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMPRI=20; VLAN configuration of the signaling:

SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=100, VLANPRIO=6;

VLAN configuration of the uplink frame of the common channel and the uplink control frame of the HSDPA

SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=48, INSTAG=ENABLE, VLANID=2, VLANPRIO=5;

If the priority rule by running the command SET DIFPRI is IPPRECEDENCE, use one value in the DSCP range corresponding to the IPPRCEDENCE by running the command SET VLANCLASS.

Note: V110 does not support the label of the VLAN based on the next hop; therefore, the command ADD VLANMAP does not apply. Enable the VLANTAG by running the command SET ETHPORT. Then, run the command SET VLANCLASS. The configuration method is the same as that by running the command SET VLANCLASS in V210.

4.2 Constraint and Restrictions of IP Address and Configuration

This section describes current constraints on the IP transport configurations. In the networking, data is planned according to the constraints.

4.2.1 Constraints of RNC IP Address

The interface IP address, user plane IP address, and control plane IP address should not be 0.*.*.*, 127.*.*.*, 255.255.255.255, RNC internal subnet segment, RNC debug subnet segment (by running the command SET SUBNET. The default network segment is 192), BAM internal/external network segment, and M2000 network segment.

Constraints of RNC IP address network segment:

1. All Ethernet port address (ETHIP) in the RNC interface board should not be on the same network segment.

2. The device IP address (DEVIP) of the same interface board in the RNC should not be on the same network segment.

(42)

should not be on the same network segment.

4. The device IP address should not be the same as the configured IP address (including local/peer IP address of the PPP link, local/peer IP address of the MLPPP group, Ethernet port IP address, IPPATH peer address, SCTP link peer address) in the RNC.

5. The Ethernet port IP address should not be the same as the configured IP address (including local/peer IP address of the PPP link, local/peer IP address of the MLPPP group, and the device IP address) in the RNC.

6. The local IP address of the MLPPP group and PPPLNk should not be the same as the local address in the RNC, or the same as the peer address (for example, PPP port IP address, ETH port address, ETH gateway, and logical IP address) in the RNC. The peer address should not be the same as the local address in the RNC.

4.2.2 Constraints of NodeB IP Address

The NodeB interface address, user plane address, control plane address, or maintenance address should not be 0.*.*.*, 127.*.*.*, 255.255.255.255, and 10.22.1.x (internal restricted address in the RAN6.0 NodeB).

Constraints of NodeB IP address network segment:

One interface can be configured with up to four IP addresses, which can be on the same network segment.

The addresses of different interfaces should not be on the same network segment. The interface address and the maintenance address may be on the same network segment.

The peer addresses such as the MLPPP group and PPPLNK should not be the same as the configured address in the NodeB. The local address should not be the same as the configured interface address in the NodeB.

Chapter 5 Example of Iub Interface Configuration

5.1 Version Description

(43)

5.2 IUB Interface Protocol Stack

In the case of the Iub over IP, the compliant sequence in adding Iub interface data should be consistent with the protocol structure, that is, from the lower layer to the upper layer. Data is configured from the control plane to the user plane.

The following figure shows IP-based protocol stack of the Iub interface.

Figure 1.14 Iub interface protocol stack

5.3 Data Planning

In the case of the IP transport, the interconnected data (unless otherwise specified) of the Iub interface is obtained through the negotiation between the RNC and the NodeB. Before configuring IP-based Iub interface data, confirm the following information:

•L2 networking or L3 networking

•Ethernet-based transport, private line-based transport, or IP hybrid transport The IP transport solutions vary with transport networks used in the Iub interface.

(44)

5.3.1 Data Planning in L2 Networking

This section describes the data planning in the case of the use of the FE. For the data planning of PPP/MLPPP, see section 7.3.3.

1. Data planning of physical layer and data link layer

Data Item RNC Side NodeB Data Source

FE port data

Interface board type

FG2/GOUa WMPT _{Internal planning}

Gateway IP address 10.10.10.2/24 10.10.10.1/24 _{Network planning} Whether to backup/backup mode Yes/Board backup, port backup No _{Internal planning} Subrack No./Slot No./Port No. 0/18/0 0/6/0 Port IP address/subnet mask 10.10.10.1/24 10.10.10.2/24 _{Network planning} Master IP address/slave IP address - -

2. Data planning of control plane

Data Item RNC NodeB _{Data Source}

IUB congestion control switch

OFF OFF _{Negotiation data}

NodeB Max Hsdpa User Number

3840 3840

NCP _{Local SCTP Port No.} 58080 9000

SCTP signaling link mode

Server Client

SPU Slot No. 0 -

SPU Subsystem No. 0 -

DSCP 62 62

First local IP address 10.10.10.1/24 10.10.10.2/24

Second local IP address

(45)

Whether to bind logical port/logical port slot No. and port No. Yes/18/20 - Whether to add VLAN/VLAN ID 10 10 CCP

Local SCTP Port No. 58080 9001

SCTP signaling link mode

Server Client

Port No. 0 0

SPU Slot No. 0 -

SPU Subsystem No. 0 -

DSCP 62 62

First local IP address 10.10.10.1/24 10.10.10.2/24

Second local IP address

- -

Whether to bind logical port/logical port slot No. and port No.

Yes/18/20 -

Whether to add VLAN/VLAN ID

10 10

3. Data planning of user plane

NodeB name RNC8-BBU1 BBU1 _Negotiation

data Transport Neighbor Node

ID

1 1

IP Protocol Version IPv4 IPv4 _Network

planning

IP path 1 _{Port type} Eth Eth _Negotiation

data

IP Path flag 1 1

PATH Type RT RT

Yes/18/20 -

Local IP address/subnet mask

10.10.10.1/24 10.10.10.2/24 _Network

(46)

Use VLAN or

not/Enabled VLAN ID

YES/VLAN10 YES/VLAN10

PATH check flag ENABLE - _Internal

planning Check IP address 10.10.10.2/24 -DSCP 46 46 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO IP path2

Port type Eth Eth _Negotiation

data

IP Path flag 2 2

PATH type NRT NRT

Yes/18/20 - Local IP address/subnet mask 10.10.10.1/24 10.10.10.2/24 _Network planning Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10

planning Check IP address 10.10.10.2/24 -DSCP 18 18 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO

data

IP Path flag 3 3

PATH type HSDPANRT HSDPANRT

(47)

Data Item RNC NodeB _{Data Source} Local IP address/subnet mask 10.10.10.1/24 10.10.10.2/24 _Network planning Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10

data

IP Path flag 4 4

PATH type HSUPANRT HSUPANRT

Yes/18/20 - Local IP address/subnet mask 10.10.10.1/24 10.10.10.2/24 _Network planning Use VLAN or not/Enabled VLAN ID YES/VLAN10 YES/VLAN10

4. Data planning of management plane

(48)

OMIP address at NodeB side

- _{10.10.10.3/24 (If NodeB}

OMIP and the interface IP are on the same network segment, enable the ARP proxy function of the interface) Network planning Interface IP address at NodeB side - 10.10.10.2/24 Gateway IP address at NodeB side - 10.10.10.1/24 Gateway IP address at RNC side 10.10.10.2/24 -Interface IP address at RNC side 10.10.10.1/24 -BAM external network IP address 10.161.215.242/24 -IP address of M2000 Server 10.161.215.230/24

-5.3.2 Data Planning in L3 Networking

1. IP addresses planning

The following figure shows the Ethernet-based IP planning.

If the load-sharing mode is not used and only one IP address is used at the RNC side, the ETHIP of the FG2 can be used directly. The DEVIP should not be configured and used. In the example, the DEVIP used in the SCTP and IPPATH local address is optional, and indicates only the configuration and usage of the DEVIP.

(49)

Data Item RNC

Side

NodeB Data Source

FE por t dat a Interface board type

FG2/GOUa WMPT _{Internal planning}

Gateway IP

address

10.10.10.1/26 16.16.16.1/26 _{Network planning}

Backup/backup

mode Yes/Board backup, port backup No _{Internal planning} Subrack No./Slot No./Port No. 0/18/0 0/6/0 Port IP address/subnet mask 10.10.10.2/26 16.16.16.2/26 _{Network planning} Master IP address/slave IP address - -

IUB congestion control switch

NodeB Max Hsdpa User Number 3840 3840 NCP _{Local SCTP Port} No. 58080 9000 SCTP signaling link mode Server Client

SPU Slot No. 0 -

SPU Subsystem No. 0 - DSCP 62 62 First local IP address 10.10.10.100/26 16.16.16.2/26 Second local IP address - -

(50)

Whether to bind logical port/logical port slot No. and port No. Yes/18/20 - Whether to add VLAN/VLAN ID - - CCP Local SCTP port No. 58080 9001 SCTP signaling link mode Server Client Port No. 0 0

SPU Slot No. 0 -

SPU Subsystem No. 0 - DSCP 62 62 First local IP address 10.10.10.100/26 16.16.16.2/26 Second local IP address - - Whether to bind logical port/logical port slot No. and port No.

Yes/18/20 -

- -

NodeB name RNC8-BBU1 BBU1 Negotiation

data Transport Neighbor Node

ID

1 1

IP Protocol Version IPv4 IPv4 _Network

planning

data

IP Path flag 1 1

PATH Type RT RT

(51)

10.10.10.100/26 16.16.16.2/26 _Network

planning Use VLAN or not/Enabled

VLAN ID

- -

PATH check flag ENABLE - Internal planning

Check IP address 16.16.16.2/26 -DSCP 46 46 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO IP path2

Port type Eth Eth _Negotiation

data

IP Path flag 2 2

PATH type NRT NRT

Yes/18/20 -

10.10.10.100/26 16.16.16.2/26 _Network

VLAN ID

- -

Check IP address 16.16.16.2/26 - DSCP 18 18 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO

data

IP Path flag 3 3

PATH type HSDPANRT HSDPANRT

(52)

10.10.10.100/26 16.16.16.2/26 _Network

VLAN ID

- -

Check IP address 16.16.16.2/26 -DSCP 10 10 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO

data

IP Path flag 4 4

PATH type HSUPANRT HSUPANRT

Yes/18/20 -

10.10.10.100/26 16.16.16.2/26 _Network

VLAN ID

- -

Check IP address 16.16.16.2/26 -DSCP 10 10 Transmit bandwidth (kbps) 20000 20000 Receive bandwidth (kbps) 20000 20000 FPMUX Enable NO NO

5. Data planning of management plane

(53)

OMIP address at NodeB side

- _{9.9.9.9/26 (If NodeB}

OMIP and the interface IP are on the same network segment, enable the ARP proxy function of the interface)

Network planning Interface IP address at NodeB side - 16.16.16.2/26 Gateway IP address at NodeB side - 16.16.16.1/26 Gateway IP address at RNC side 10.10.10.1/26 -Interface IP address at RNC side 10.10.10.2/26 -BAM external network IP address 10.161.215.242/24 -IP address of M2000 Server 10.161.215.230/24

-5.3.3 Data Planning of Hybrid Transport Networking

In the case of the hybrid transport, signaling and real-time services are transmitted through the PPP, and BE services are transmitted through the FE.

1. IP addresses planning

The RNC and NodeB (3X1) access the SDH optical transport network through the Add/Drop Multiplexer (ADM) respectively. The RNC is connected to the NodeB through the SDH or Plesiochronous Digital Hierarchy (PDH) transport network. Meanwhile, the RNC and NodeB access the Ethernet (L3 networking).

E1/T1

PDH/SDH

E1/T1 ADM ADM

NodeB1 BSC6800

Ethernet

(54)

The following figure shows the Ethernet-based IP planning.

Figure 1.17 IP planning of Ethernet-based L3 networking

The following figure shows the E1-based IP planning.

Figure 1.18 E1-based IP planning

Data Item RNC Side NodeB Data Source

FE port data

Interface board type FG2/GOUa WMPT _{Internal planning}

Gateway IP address 10.10.10.1/26 16.16.16.1/26 _Network

planning Backup/backup

mode Yes/Board backup

separated from port backup No Internal planning Subrack No./Slot No./Port No. 0/18/0 0/12/0 Port IP address/subnet mask 10.10.10.2/26 16.16.16.2/26 _Network planning

(55)

Data Item RNC Side NodeB Data Source Master IP address/slave IP address - - PPP /MLPPP Link PPP Link data

Interface board type PEU/UOI_IP/POUa WMPT _{Internal planning}

Gateway IP address - -

Subrack No./Slot No./E1T1 Port No.

0/14/0 0/12/0 MLPPP group No. - -PPP/MLPPP link No. 0 0 Local IP address, subnet mask 13.13.13.1/24 13.13.13.2/24 _Network planning Bearer timeslot TS1&TS2&TS3

&TS4&TS5&TS6

TS1&TS2&TS3 &TS4&TS5&TS6

Negotiation data

The settings are not required when the RNC uses UOI_IP and POUa.

Iub congestion control switch

NodeB Max Hsdpa User Number 3840 3840 NCP _{Local SCTP Port} No. 58080 9000 SCTP signaling link mode Server Client

SPU Slot No. 0 -

SPU Subsystem No. 0 - DSCP 62 62 First local IP address 13.13.13.1/24 13.13.13.2/24 Second local IP address - -

(56)

Whether to bind logical port/logical port slot No. and port No. - - Whether to add VLAN/VLAN ID - - CCP Local SCTP port No. 58080 9001 SCTP signaling link mode Server Client Port number 0 0

SPU Slot No. 0 -

SPU Subsystem No. 0 - DSCP 62 62 First local IP address 13.13.13.1/24 13.13.13.2/24 Second local IP address - - Whether to bind logical port/logical port slot No. and port No.

- -

NodeB name RNC8-BBU1 BBU1 Negotiation

data Transport neighbor node

flag

1 1

IP protocol version IPv4 IPv4 _Network

planning

IP path 1 _{Port type} PPP PPP _Negotiation

data

IP Path flag 1 1

PATH type RT RT