25-Ip Ran

RAN Feature Description
Table of Contents
Table of Contents
Chapter 25 IP RAN...................................................................................................................... 25-1
25.1 Introduction................................................................................................................... 25-1
25.1.1 Definition............................................................................................................. 25-1
25.1.2 Purposes............................................................................................................ 25-1
25.1.3 Benefits............................................................................................................... 25-1
25.1.4 Terms and Abbreviations....................................................................................25-1
25.2 Availability..................................................................................................................... 25-4
25.2.1 Network Elements Involved................................................................................25-4
25.2.2 Software Releases............................................................................................. 25-4
25.2.3 Miscellaneous..................................................................................................... 25-5
25.3 Impact........................................................................................................................... 25-6
25.3.1 On System Performance....................................................................................25-6
25.3.2 On other Features.............................................................................................. 25-6
25.4 Technical Description.................................................................................................... 25-6
25.4.1 IPRAN Configuration Model................................................................................25-6
25.4.2 Protocol Stack Based on IP RAN.......................................................................25-7
25.4.3 Protocol Encapsulation.......................................................................................25-8
25.4.4 Data Streams...................................................................................................... 25-8
25.4.5 Scenarios.......................................................................................................... 25-17
25.4.6 Implementation Policies....................................................................................25-20
25.5 Capabilities................................................................................................................. 25-29
25.6 Implementation........................................................................................................... 25-30
25.6.1 Data Preparation.............................................................................................. 25-31
25.6.2 Configuration Procedure...................................................................................25-36
25.6.3 Examples.......................................................................................................... 25-40
25.7 Maintenance Information.............................................................................................25-50
25.7.1 MML Commands..............................................................................................25-50
25.7.2 Alarms............................................................................................................... 25-51
25.7.3 Counters........................................................................................................... 25-52
25.8 References.................................................................................................................. 25-53
Huawei Technologies Proprietary

i
List of Figures
List of Figures
Figure 25-1 IPRAN configuration model (1)........................................................................25-7
Figure 25-2 IPRAN configuration model (2)........................................................................25-7
Figure 25-3 Protocol stack for the Iub interface (based on IP RAN)...................................25-8
Figure 25-4 TDM networking mode...................................................................................25-17
Figure 25-5 Data networking mode...................................................................................25-18
Figure 25-6 Hybrid networking mode................................................................................25-19
Figure 25-7 Implementation of MLPPP links.....................................................................25-20
Figure 25-8 IP topology of the RAN system - 1.................................................................25-23
Figure 25-9 IP topology of the RAN system - 2.................................................................25-23
Figure 25-10 DiffServ service processing procedure........................................................25-26
Figure 25-11 Data network security..................................................................................25-28
Figure 25-12 Flow chart for configuring IP transport data at the NodeB...........................25-38
Figure 25-13 IP RAN topology.......................................................................................... 25-40
Figure 25-14 IP addressing scheme for Ethernet-based IP transport...............................25-40
Figure 25-15 IP addressing scheme based on private transport network.........................25-41

ii
List of Tables
List of Tables
Table 25-1 NEs required for IP RAN....................................................................................25-4
Table 25-2 RAN products and related versions...................................................................25-4
Table 25-3 Functions of the RNC IP interface boards and related sub-boards....................25-5
Table 25-4 IP addressing scheme.....................................................................................25-21
Table 25-5 IP addresses A to F of the RAN system...........................................................25-23
Table 25-6 Internal IP addresses of the RNC....................................................................25-24
Table 25-7 Numbering scheme for the FE and E1/T1 ports..............................................25-25
Table 25-8 Numbering scheme for the PPP links..............................................................25-25
Table 25-9 QoS assurance mechanisms implemented on different layers........................25-25
Table 25-10 DiffServ service processing procedure..........................................................25-26
Table 25-11 Rules for configuring PQs in NodeB..............................................................25-27
Table 25-12 MML commands for QoS configuration on the RNC side..............................25-27
Table 25-13 MML commands for QoS configuration on the NodeB side...........................25-27
Table 25-14 IP transport capabilities at the RNC...............................................................25-29
Table 25-15 IP transport capabilities at the NodeB............................................................25-29
Table 25-16 IP addressing scheme...................................................................................25-31
Table 25-17 Data (physical layer and data link layer) to be planned and negotiated.........25-32
Table 25-18 Data on the control plane to be planned and negotiated...............................25-32
Table 25-19 Data on the user plane to be planned and negotiated...................................25-33
Table 25-20 Data on the management plane to be planned and negotiated.....................25-34
Table 25-21 Cell data to be planned and negotiated.........................................................25-35
Table 25-22 IP transport data configuration procedure......................................................25-38
Table 25-23 Cell states and values....................................................................................25-40
Table 25-24 Data (physical layer and data link layer) to be planned and negotiated.........25-41
Table 25-25 Data on the control plane to be planned and negotiated...............................25-42
Table 25-26 Data on the user plane to be planned and negotiated...................................25-43
Table 25-27 Data on the management plane to be planned and negotiated.....................25-44
Table 25-28 Cell data to be planned and negotiated.........................................................25-45
Table 25-29 MML commands............................................................................................ 25-50

iii
List of Tables
Table 25-30 Counters related to the SCTP........................................................................25-52

Table 25-31 Counters related to the IP PATH feature........................................................25-52

iv
Chapter 25 IP RAN
Chapter 25 IP RAN
25.1 Introduction
25.1.1 Definition
With the IP transport technology, the IP RAN feature enables IP transport on the Iub
interface.
25.1.2 Purposes
The IP RAN feature is implemented to:
Provide enough transmission bandwidth for high speed data services such as
HSDPA
Provide more flexible networking for the operator to reduce network deployment
costs
25.1.3 Benefits
The IP RAN feature yields the following benefits:
Fully utilizing rich IP network resources

Mainstream data communication networks are based on IP transport. They have
multiple access modes and large-scale deployment. The IP RAN feature enables
the operator to fully utilize the existing IP network resources for Iub networking.
Economical IP network construction

While facing the competition from the ATM network, the more economical IP
network is preferred by a number of vendors.
Following the trend in network migration to protect your investment
The IP transport technology is taking the lead in the data communication field, and
will dominate this field in the future.

1
Chapter 25 IP RAN
25.1.4 Terms and Abbreviations

I. Terms
Term
Description
IP
The RNC has three types of IP interface board: WEIE, WFIE, and
interface
WFEE.
board
The NodeB has only one such board, that is, the NUTI.
Cascading
In a cascading connection, the output of one entity is considered as

the input of its next entity.
Cascading in this chapter refers to the topology type (chain and tree)
of NodeBs.
Macro
A type of NodeB that can be categorized into outdoor NodeB and
NodeB
indoor NodeB
DiffServ
For DiffServ, the Type of Service (ToS) field of the IPv4 header is
replaced by the DS field. After the DS field is defined and processed
on the basis of predefined rules, it is forwarded to the next node that
processes the received packets according to this field. This is to say,
the next node converts complicated QoS assurance to PHB[6].
Note:
DiffServ = Differentiated Service
II. Abbreviations
Abbreviation
Full Spelling
ADSL
Asymmetrical Digital Subscriber Loop
ATM
Asynchronous Transfer Mode
BBU
Baseband Unit
BSC6800
A model of Huawei RNC
BTS3812A
A model of Huawei outdoor macro NodeB
BTS3812E
A model of Huawei indoor macro NodeB
CCP
Communication Control Port
CS
Circuit Switched

2
Chapter 25 IP RAN
Abbreviation
Full Spelling
DBS3800
A model of Huawei Distributed NodeB
DHCP
Dynamic Host Configuration Protocol
DS
Differentiated Services
DSCP
DiffServ Code Point
FE
Fast Ethernet
FP
Frame Protocol
GGSN
Gateway GPRS Support Node
HLR
Home Location Register
HSDPA
High Speed Downlink Packet Access
IMA
Inverse Multiplexing on ATM
IP
Internet Protocol
IPoA
Internet Protocols over ATM
IPSec
IP Security
LLC
Link Layer Control
MAC
Medium Access Control
MCPPP
Multi-Class Extension to Multi-link PPP
MGW
Media Gateway
MLPPP
PPP Multilink Protocol
MML
Man Machine Language
MSB
Most Significant Bit
MSC
Mobile Switching Center
NBAP
NodeB Application Protocol
NCP
NodeB Control Port
NMPT
NodeB Main Processing & Timing unit
NUTI
NodeB Universal Transport Interface unit
OMIP
IP Address of Operation and Maintenance

3
Chapter 25 IP RAN
Abbreviation
Full Spelling
PCI
Peripheral Component Interconnect
PDH
Plesiochronous Digital Hierarchy
PPP
Point-to-Point Protocol
PPPoE
Point-to-Point Protocol over Ethernet
PQ
Priority Queue
PS
Packet Switched
QoS
Quality of Service
RAN
Radio Access Network
RNC
Radio Network Controller
RRC
Radio Resource Control
SCTP
Stream Control Transmission Protocol
SDH
Synchronous Digital Hierarchy
SGSN
Serving GPRS Support Node
STM-1
Synchronous Transport Mode-1
TCA
Traffic Conditioning Agreement
TCP
Transmission Control Protocol
TDM
Time Division Multiplex(ing)
UDP
User Datagram Protocol
UE
User Equipment
UMTS
Universal Mobile Telecommunications System
UTRAN
Universal Terrestrial Radio Access Network
VLAN
Virtual Local Area Network
VPN
Virtual Private Network
WSPUb
WCDMA RNC Signaling Processing board

4
Chapter 25 IP RAN
25.2 Availability
25.2.1 Network Elements Involved
Table 1.1 describes the NEs involved with the IP RAN feature.
Table 1.1 NEs required for IP RAN
UE
NodeB
RNC
MSC
MGW
SGSN
GGSN
HLR
Server
Note:
: not required
: required
25.2.2 Software Releases

Table 1.1 describes the versions of RAN products that support IP RAN transport.
Table 1.1 RAN products and related versions
Product
Version
RNC
BSC6800
V100R007 and later releases
NodeB
DBS3800
V100R007 and later releases
BTS3812A
BTS3812E
25.2.3 Miscellaneous
To implement the IP RAN feature, the RNC and the NodeB must be configured with
related IP interface boards.
I. IP Interface Boards for the RNC

The IP interface boards of the RNC use two types of sub-boards (EIU and FIU) as
follows:
WEIE board: upper and lower EIU sub-boards
WFIE board: only upper FIU sub-board
WFEE board: lower EIU sub-board and upper FIU sub-board

5
Chapter 25 IP RAN
Table 1.1 describes the functions of the IP transport boars and related sub-boards.
Table 1.1 Functions of the RNC IP interface boards and related sub-boards
Board
Sub-board
Functions
WEIE
Two EIU
Providing 32 E1/T1s
sub-board
Supporting IP over PPPoE
Supporting 128 PPP links (0 to

63 for lower sub-board and 64
0 to 15 (for lower
sub-board)
16 to 31 (for
upper sub-board)
to 127 for upper sub-board)
Note:
Supporting 32 MLPPP groups
The ports are

numbered from the
Note:
Port Number
Each MLPPP group can be
bottom up.
configured with a maximum of 8

MLPPP links.
MLPPP links in one MLPPP

group must be carried on the
same WEIE board.
WFIE
One FIU
Providing 4 FE ports
0 to 3
sub-board
Supporting IPoE
Note:
Supporting the backup of the

two FE ports on the same WFIE

two WFIEs in the same WRBS

6
The ports are

numbered from the
top down.
Chapter 25 IP RAN
Board
Sub-board
WFEE
One EIU
Providing 16 E1/T1s
sub-board
Providing 4 FE ports
sub-board;
and one
Supporting IP over PPPoE
numbered from
FIU sub-
Supporting IPoE
board
Functions
two FE ports on the same

WFEE
Supporting 64 PPP links (0 to
Port Number
0 to 15 (for EIU
the bottom up)
0 to 3 (for FIU
sub-board;
numbered from
the top down)
63 for lower sub-board)
Supporting 32 MLPPP groups
Note:
Each MLPPP group can be

configured with a maximum of 8
MLPPP links.
MLPPP links in one MLPPP

group must be carried on the
same WFEE board.
II. IP Interface Board for the NodeB

The DBS3800 of earlier versions has FE ports. Therefore, no hardware change is
made.
To support the IP RAN feature, the BTS3812E and the BTS3812A require the NUTI
board that can provide eight E1/T1 ports and two FE ports.
25.3 Impact
25.3.1 On System Performance
None.
25.3.2 On other Features

None.
25.4 Technical Description

25.4.1 IPRAN Configuration Model
The configuration model for IPRAN is as show in Figure 1.1 and Figure 1.2.
7
Chapter 25 IP RAN
RNC
TransportClass
IPPATH .Class
SCTPLNK .Class
SCTPLOCIP .Class
Local IP address
Signalling link model
First Local IP Address
Peer IP address
First destination IP address
Server Port No
Peer subnet mask
Destination SCTP port No.
IP path type
Differentiated Services Codepoint
Figure 1.1 IPRAN configuration model (1)

NodeB
TransportClass
OMIP .Class
OM IP address
OM IP mask
OM Peer IP address
Figure 1.2 IPRAN configuration model (2)
25.4.2 Protocol Stack Based on IP RAN

Figure 1.1 shows the protocol stack for the Iub interface.

8
Chapter 25 IP RAN
User plane
TFCI2 FP
CPCH FP
USCH FP
CCP
PCH FP
NCP
RACH FP
DCH FP
NBAP
HSDSCH FP
Control plane
FACH FP
Radio
network
layer
CCP
Tranport
network layer
user plane
Tranport
network layer
user plane
Transport
network
layer
SCTP
UDP
IP
IP
Data link layer
Data link layer

Physical layer
Figure 1.1 Protocol stack for the Iub interface (based on IP RAN)
25.4.3 Protocol Encapsulation

As shown in 25.4.2
IFigure 1.1, the introduction of the IP transport technology
enables:
The NBAP on the control plane to be carried on SCTP, IP, layer 2 (data link
layer), and PHY (physical layer). The data stream on the control plane is
transmitted only after SCTP/IP encapsulation.
The FP on the user plane is carried on UDP, IP, layer 2, and PHY (physical
layer). The data stream on the user plane is transmitted only after UDP/IP
encapsulation.
Data streams on the user plane and the control plane are encapsulated using
different protocols, depending on layer 2 technologies:
Private network: encapsulated with PPP, MLPPP, MCPPP, or PPPMUX
Ethernet: encapsulated at the MAC and LLC (for receive purpose only) sublayers

9
Chapter 25 IP RAN
25.4.4 Data Streams

The IP protocol stack applies to the Iub interface. The IP protocol terminates at the IP
interface boards of the RNC. Data streams, however, are processed by NEs in
compliance with ATM protocols.
I. Data Stream Processing of RNC

The RNC assigns the Local IP address and Local IP Port No. and sends the two
parameters to the NodeB in the Iub signaling messages.
The NodeB also assigns the IP address and IP port No. and sends them to the RNC
in the response messages of the Iub signaling. The IP address and IP port No. are
Peer IP address and Peer IP port No. of the RNC respectively.
Then the RNC establishes the correlation between a combination of certain
parameters and AAL2 channel ID in the Iub IP interface board. The parameters are as
follows:
Local IP address
Local IP Port No.
Peer IP address
Peer IP port No.
The UDP/IP packets on the user plane travel from the NodeB to the IP interface
boards of the RNC. The RNC then extracts the payloads from UDP/IP packets. After
AAL2 encapsulation, the UDP payloads, that is, FP packets, are transferred to the
WFMR board.
Conversely, the WFMR transfers FP packets to the IP interface boards after AAL2
encapsulation. After UDP/IP encapsulation, the IP interface boards forward the routes
of FP packets according to their destination IP addresses.
When ADD IPPTAH is executed on the LMT of the RNC, Local IP address and Peer
IP address may be specified. Besides, IP path type and Differentiated Services
Codepoint should be set based on the service type and QoS requirement.
Parameters:

10
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
Local IP address
IPADDR
###.###.###.###
### (0255)
Physical Range& Unit
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
ADD IPPATH
Description:
Local IP address must be either the IP address of an IPoA client already

configured to the WFIE/WEIE/WFEE or the local IP address on the
WFIE/WEIE/WFEE. The port can be the Ethernet port or the PPP or MLPPP
port.
Local IP address cannot be 0, all binary 1, 127.0.0.1, or any internal IP

address beginning with 192.
Local IP address cannot be the same as Local IP address or Peer IP

address already configured in the RNC.
On one WFIE/WEIE/WFEE, a maximum of ten local IP addresses can be used

by all IP paths. The local IP addresses include those of the WPIE client,
Ethernet port, PPP port, and MLPPP port.
To a Peer IP address, there is only one Local IP address.

11
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
Peer IP address
PEERIPADDR
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
ADD IPPATH
Description:
Peer IP address may be the IP address of the FE or PPP/MLPPP port at the

NodeB.
Peer IP address cannot be 0, all binary 1, 127.0.0.1, or any internal IP address

beginning with 192.
Peer IP address cannot be the same as Local IP address configured in the

RNC.

12
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
Peer subnet mask

PEERMASK
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
ADD IPPATH
Description:
If Peer subnet mask is not 255.255.255.255, the host or network routes cannot
be smaller than the value of Peer IP address AND Peer subnet mask. By this,
one IP path does not terminate at multiple ports.
If the IP path supports the check function, Check IP address is required. The
IP address must be within the network segment specified by Peer IP address
AND Peer subnet mask, no matter Peer IP address is a network number or a
host number.
Parameter Name
Parameter ID
GUI Range
IP path type
IPPATHT
RT, NRT, HSDPA_RT, HSDPA_NRT
None
Default Value
NRT
Optional/Mandatory
MML Command
Optional
ADD IPPATH
Description:
Common channels, CS services, PS conversional services, and PS streaming

services are carried on the IP path of RT or HSDPA_RT type.
PS background and PS interactive services are carried on the IP path of NRT or

HSDPA_NRT type.
Each IP node must be configured with an IP path of RT type.

13
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
Default Value
Optional/Mandatory
MML Command
Differentiated Services Codepoint

DSCP
B000000B111111, B11111111
063, 255
46-RT; 18-NRT; 38-HSDPA_RT; 0-HSDPA_NRT
Optional
ADD IPPATH
Description:
The RNC sets the DSCP value in the DS field of IP headers according to the
class of service.
The RNC transmits the DSCP value to the NodeB through dedicated Iub
signaling messages, and the NodeB sets the value to the DSCP domain of IP
packets Head. The DSCP in used into Dedicated channel UDP/IP packets.
SCTP/IP packets on the control plane
An SCTP link is a logical connection or path for data transmission between two SCTP
endpoints.
One end of an SCTP link works in server mode, and the other end in client mode.
An SCTP transport address consists of an IP address and a port number. The port
number identifies users on the same address. The SCTP endpoint is the logical
transmitter or receiver of SCTP packets.
An SCTP endpoint can use multiple transport addresses, all of which, however, must
use the same port number. That is what is called multi-homing.
Therefore, an SCTP link needs the following parameters at least:
Local IP address
Local SCTP port No.
Peer IP address
Peer SCTP port No.
Work mode
The IP interface boards forward the routes of SCTP/IP packets according to their
destination IP addresses. The packets are then transferred to the WSPUb, an RNC
signaling processing
board, through IPoA PVCs.

14
Chapter 25 IP RAN
Conversely, the SCTP/IP packets from the WSPUb travel to the IP interface boards
through IPoA PVCs. The IP interface boards then forward the routes of the SCTP/IP
packets according to their destination IP addresses.
Parameter:
Parameter Name
Parameter ID
GUI Range
First Local IP Address

ADDR1
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
ADD SCTPLOCIP
Description:
First local IP address is configured by the customers based on the real

network planning. The IP address belongs to A/B/C address classes. The IP
address consists of two parts: network number and host number. The network
number cannot be set to all 0s or 1s. The IP address cannot be set to 0.0.0.0 or
127.0.0.1. The internal class C addresses (192.1.###.###) are reserved for
internal purposes except the WHPU board.
First Local IP Address and Second Local IP Address must be configured

through the command ADD IPOACLIENT. Before the execution of this
command, the two IP addresses cannot be used for ATM transport.
First Local IP Address cannot be the same as Second Local IP Address.

15
Chapter 25 IP RAN
Parameter Name
Parameter ID
Server Port No.

SRVPN
GUI Range
102465534
102465534
Default Value
Optional/Mandatory
MML Command
58080
Optional
ADD SCTPLOCIP
Description:
When the RNC enables the listening port, the ports on the server side can use the
same Server Port No.
Parameter Name
Parameter ID
GUI Range
Signalling link model

MODE
SERVER, CLIENT
None
Default Value
SERVER
Optional/Mandatory
Optional
MML Command
ADD SCTPLNK
Description:
Generally, the working mode of the RNC is SERVER, and that of the NodeB is
CLIENT.

16
Chapter 25 IP RAN
Parameter Name
First destination IP address
Parameter ID
PEERIPADDR1
GUI Range
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
MML Command
Mandatory
ADD SCTPLNK
Description:
First destination IP address may be the IP address of the FE or PPP/MLPPP
port.
Parameter Name
Parameter ID
Destination SCTP port No.

PEERPORTNO
GUI Range
102465535
102465535
Default Value
Optional/Mandatory
MML Command
None
Mandatory
ADD SCTPLNK
Description:
Destination SCTP port number cannot be the same for different SCTP links that
have the same Destination SCTP IP address.
TCP/IP packets on the management plane
The IP interface boards forward the routes of TCP/IP packets according to their
destination IP addresses. The packets are then transferred to the WMUXb, an RNC
multiplexing board, through IPoA PVCs.
Conversely, the TCP/IP packets from the WMUXb travel to the IP interface boards
through IPoA PVCs. The IP interface boards then forward the routes of the TCP/IP
packets according to their destination IP addresses.

17
Chapter 25 IP RAN
II. Data Stream Processing of NodeB

To describe the data streams processed by the NodeB, the following definitions are
given:
User plane
At the IP interface board, the NodeB receives the user plane data, for example,
FP packets encapsulated in UDP/IP packets. Then the pure data is encapsulated
into AAL2 packets and transferred to the baseband board, such as the HDLP
and HBBI.
Conversely, FP packets encapsulated in AAL2 packets are transferred from the
baseband board, such as the HBBI and HULP, to the IP interface board of the
NodeB. Then the pure data is encapsulated into UDP/IP packets and transferred
to the RNC.
Control plane
The SCTP protocol is applied to the IP interface board, and the NBAP protocol to
the main control unit. The SCTP entity receives NBAP signalings from the RNC
and forwards them to the Main Control unit through AAL5 PVCs between boards.
Conversely, the NBAP entity sends the messages to the SCTP entity through
AAL5 PVCs. Then the SCTP entity encapsulates them into SCTP/IP packets and
transfers SCTP/IP packets to the RNC.
Management plane
The management plane provides the operation and maintenance channel for
remote configuration. The M2000 or LMT be connected to the NodeB directly or
through the RNC.
At the IP interface board, the NodeB receives the TCP/IP packets and forwards
the routes of TCP/IP packets according to their destination IP addresses. The IP
address is OM IP address. The packets are then transferred to the NMPT, a
NodeB main control board, through IPoA PVCs.
Conversely, the TCP/IP packets from the NMPT travel to the IP interface boards
through IPoA PVCs. The IP interface boards then forward the routes of the
TCP/IP packets according to their destination IP addresses. The IP address is
OM Peer IP address.
MML commands used to set remote operation & maintenance IP addresses are
available at the LMT.
Parameters:

18
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
OM IP address
IP
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
Mandatory
MML Command
SET OMIP
Description:
From the remote side, you can log in to the NodeB through the OM PC by using
the OM IP address.
Parameter Name
Parameter ID
GUI Range
OM IP mask
MASK
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
Mandatory
MML Command
SET OMIP
Description:
OM IP address cannot be in the same subnet with the IP address of the FE, PPP,
or MLPPP port or with the local maintenance IP address.

19
Chapter 25 IP RAN
Parameter Name
Parameter ID
GUI Range
OM Peer IP address
PEERIP
###.###.###.###
### (0255)
None
Default Value
None
Optional/Mandatory
Mandatory
MML Command
SET OMIP
Description:
OM Peer IP address is the PC IP address of the M2000 client or NodeB LMT.

From the PC, you can log in to and maintain the NodeB.
OM Peer IP address and the local maintenance IP address must be in different

network segments.
25.4.5 Scenarios
At present, the IP RAN feature can be implemented in the following three scenarios:
TDM network
Data network
Hybrid transport network
I. TDM Network
Figure 1.1 shows the TDM networking mode.

20
Chapter 25 IP RAN
NodeB
RNC
TDM networking
NodeB
Figure 1.1 TDM networking mode

In TDM networking mode, the RNC and NodeBs support IP over PPP over E1, which
can be based on PDH/SDH or MSTP.
Benefits: ensures security and QoS. Line clock signals can be extracted.
Restrictions: relatively high costs of E1 leasing
II. Data Network

Figure 1.1 shows the data networking mode.
RNC
NodeB
Data networking
Figure 1.1 Data networking mode

The data network can be any of the following three types:
Layer 2 network, for example, metropolitan area Ethernet
Layer 3 network
MSTP network
The data network can be accessed through FE or E1.

A common IP network has the following benefits and restrictions:
21
Chapter 25 IP RAN
Benefits: good availability and relatively low costs of leasing
Restrictions: low security without QoS assurance. The requirements for realtime
services cannot be satisfied.
An IP network with assured QoS or a private network has the following benefits and
restrictions:
Benefits: high security and assured QoS
Restrictions: relatively high costs
III. Hybrid Transport Network

Figure 1.1 the hybrid networking mode.
TDM networking
RNC
NodeB
Data networking
Figure 1.1 Hybrid networking mode

Hybrid transport enables services of different QoSs to be transported in different
paths.
The speech service with high QoS requirements is carried on the private network
such as PDH and SDH.
Data services with low QoS requirements are carried on the data network such
as Ethernet.
The hybrid transport network has the following benefits and restrictions:
Benefits: flexible to meet your different requirements
Restrictions: complicated management
The relation between the transmission on the Iub interface and the transmission
technologies is as follows:
Control plane on the Iub interface

22
Chapter 25 IP RAN
To reduce signaling delay and connection time, data on the control plane for the
Iub interface is carried on the private network.
User plane on the Iub interface

Realtime services are carried by private networks and non-realtime services are
carried by Ethernet.
The IP transport technology for the Iub interface has the following characteristics:
The two paths from the RNC to the NodeB can connect to two transport
networks with different QoS requirements either:
Through different ports, or
Through the same port that connects to the external data equipment
according to DSCP
When the bandwidth of the low QoS network is restricted, low QoS services can
be carried on the high QoS network. When the bandwidth of the high QoS
network is limited, the RNC reduces the rate of the low QoS services that are
carried on high QoS network, or the RNC rejects the access of high QoS
services if no low QoS services are carried on the high QoS network.
The mapping between types of services and transmission modes is configurable.

The default mapping is as follows:
The interactive service and the background service in the PS domain has low
QoS requirements. The two types of services are carried on the high QoS
network only when the bandwidth of the low QoS network is restricted.
Other services have high QoS requirements such as Iub data on the control
plane, RRC signaling, CS services, common channel data of cells, PS
conversational service, and PS streaming service.
25.4.6 Implementation Policies

I. Data Link Layer
In the present IP-based RAN system, the data link layer supports the following:
FE networking
PPP links
MLPPP links
The MLPPP links are implemented in a way similar to the implementation of IMA
groups on an ATM network, as shown in Figure 1.1.

23
Chapter 25 IP RAN
Subchannel 1
MP disassembly
MP reassembly
Subchannel 2
Large packet at
network transport
layer
Large packet at
network transport
layer
Subchannel 3
Figure 1.1 Implementation of MLPPP links

In compliance with the MLPPP protocol, multiple physically independent physical links
are bound. The network transport layer considers the bound links as one logical
channel and transfers packets to this channel. The MLPPP protocol allows a larger
bandwidth, which speeds up data transmission.
II. IP Addressing Scheme

The implementation of the IP RAN feature varies according to the transport network
on the Iub interface:
If the transport network is private, the data on PPP or MLPPP links requires
negotiation and planning.
If the transport network is based on Ethernet, data on the FE interfaces requires

negotiation and planning. In this situation, the transport network can work in layer
2 or layer 3 networking mode.
If the transport network is based on the IP hybrid transport technology, the data
on the private network and the Ethernet requires negotiation and planning.
Note:
Compared with layer 3 networking mode, the interface IP addresses of the RNC and
NodeBs in layer 2 networking mode stay within the same network segment. Route
forwarding is unnecessary in this situation, which results in relatively simple
networking.
Table 1.1 describes the IP addressing scheme for the networking.

Table 1.1 IP addressing scheme
Data Item
RNC
Gateway IP address of router
NodeB
Data Source
Network plan

24
Chapter 25 IP RAN
IP address and subnet mask of FE port
(interface IP address at the RNC)

Primary and secondary IP addresses of FE port
(interface IP address at the NodeB)

Local IP address and subnet mask of
PPP/MLPPP link
IP address on the control plane
Traffic IP address
Detecting IP address of IP path
OMIP address at the NodeB
IP address of the external network where the

BAM is located
IP address of the M2000 server
Note:
The IP addresses of the FE ports and PPP/MLPPP links at the RNC are also
called interface IP addresses. The IP addresses of the IPoA clients that are added
for traffic are called traffic IP addresses.
An IP address on the user plane of the RNC can be either an interface IP address
or a traffic IP address. If traffic IP addresses are used by the IP address on the
user plane, additional IPoA clients are required to increase the number of traffic IP
addresses. In this situation, you must specify multiple traffic IP addresses if
several IP paths that do not share the same traffic IP address are configured.
If the IP path detection is enabled, you must configure the detecting IP address
that stay in the same network segment as the IP address on the user plane of the
NodeB.
The IP addresses at the NodeB are of the following types:
IP address of PPP/MLPPP link

If data is transferred on PPP or MLPPP links, the IP addresses on both sides of
the links depend on network planning. They are usually assigned by the RNC.
IP address of FE port

25
Chapter 25 IP RAN
If data is transferred on FE ports, the IP addresses on both sides of the links

depend on network planning. At present, one FE port on the NodeB can be
assigned with one primary IP address and three secondary IP addresses. The
distinguish between primary and secondary IP addresses only facilitates IP
address management.
OMIP address
If the O&M channel is required, you must configure its OMIP address to maintain
the NodeB remotely. Functionally, the OMIP address is similar to the IP address
of an IPoA client in the ATM networking mode.
Figure 1.2 shows the IP topology of the RAN system in which the RNC connects to
two NodeBs.
IP_1 to IP_5 are internal IP addresses of the RNC.
IP 1 to IP 6 are IP addresses to be planned by the RNC.
IP 3 and IP 4 are IP addresses for SCTP coupling, that is, the IP addresses of
the IPoA clients configured for the WSPUb subsystem.
Note:
The topology takes only layer 2 networking as an example.
The NodeB is of a macro type.
NodeB
IP transport
board
WMUX
IP 5
WSPUb
IP transport
board
IP 3
IP 1
IP_2
IP_4
IP_1
IP_5
IP_3
IP 2
IP 6
IP 4
NodeB
RNC
Figure 1.2 IP topology of the RAN system - 1

Figure 1.3 shows the IP topology in which the RNC connects to only one NodeB.

26
Chapter 25 IP RAN
IP transport
board
WSPUb
NodeB
Figure 1.3 IP topology of the RAN system - 2

Table 3.1 describes IP addresses A to F in Figure 1.3.
Table 3.1 IP addresses A to F of the RAN system
No.
A
Address Type
Location
IP address of the
IP interface board
FE port
of the RNC
IP address of the
NUTI of the NodeB
Description
Networking based on FE links
FE port
C
IP address of the
IP interface board
port for the
of the RNC
Networking based on PPP links
PPP/MLPPP link
D
IP address of the
NUTI of the NodeB
port for the

PPP/MLPPP link
E
IP address on the
WSPUb of the RNC
SCTP coupling at the RNC
IP address on the
IP interface board
When the IP address of the FE
user plane
of the RNC
port and the IP address of the
control plane
F
PPP/MLPPP link at the RNC

works as the IP address of the
gateway, you must set the IP
address of the IPoA client as the
user plane IP address.
The IP addresses on the control plane and the management plane over the Iub
interface are forwarded in the RNC according to the predefined routing table. The
routing table contains IP_1 to IP_5, the internal IP addresses of the RNC in Figure
27
Chapter 25 IP RAN
1.2. These IP addresses are used for your reference only. Perform site operations,
depending on the documents delivered with the related version.
Table 3.2 Internal IP addresses of the RNC
Board
IP Address
WMUX
192.1.8.1
Master WSPUb
192.1.8.2
Slave WSPUb
192.1.8.3
IP
WFIE in
Active
transport
active/standby
WFIE
board
mode
192.1.8.4
Standby
IP addresses not assigned
WFIE
Assigned the same IP address as that

of the active WFIE
WFIE in non
active/standby
mode)
Slot 0
192.1.8.4
Slot 15
192.1.8.5
III. Numbering Scheme for FE and E/T1 Ports

Table 1.1 describes the numbering scheme for the FE and E1/T1 ports on the NodeB
and the RNC.
Table 1.1 Numbering scheme for the FE and E1/T1 ports
Board
RNC
WFIE
Location
One FIU sub-board
Port Number
0 to 3 (numbered from the top
down)
WFEE
One FIU upper sub-board
0 to 3 (numbered from the top

down)
One lower EIU sub-board
0 to 15 (numbered from the

bottom up)
NodeB
NUTI
Upper FE port
Lower FE port

28
Chapter 25 IP RAN
IV. Numbering Scheme for PPP Links at the RNC

Table 1.1 describes the numbering scheme for the PPP links at the RNC that
correspond to the sub-board of the WEIE.
Table 1.1 Numbering scheme for the PPP links
Sub-board
Link Number
Upper sub-board
64 to 127
Lower sub-board
0 to 63
Note:
The lower sub-board of the WFEE supports E1/T1 connections, but not the upper
sub-board.
V. Routing Scheme
The IP RAN feature supports the following static routes that are manually configured:
Routes on the control plane
Routes on the user plane
Routes on the management plane
VI. QoS
The implementation of the QoS of the IP transport network is complicated.
To put it simply, different QoS assurance mechanisms are implemented on different
layers, as described in Table 1.1.
Table 1.1 QoS assurance mechanisms implemented on different layers
Layer
Mechanism
APP
Admission control
IP
DiffServ
Data Link Layer
Priority Queue (PQ)
Physical Layer
RL (rate limiting at the physical port)
Figure 1.2 shows the DiffServ service processing procedure.

29
Chapter 25 IP RAN
Metering
Data packet
Data packet
Classifying
Shaping/
dropping
Marking
Figure 1.2 DiffServ service processing procedure

Table 2.1 describes the DiffServ service processing procedure.
Table 2.1 DiffServ service processing procedure
Step
Description
Classification of traffic
Traffic classification enables different types of

services that are implemented by conditioning them
and setting DS values.
Conditioning
Metering
Marking
The data rate is metered through
The traffic flow
such mechanism as token
involving
bucket. Subsequent shaping and
differentiated
scheduling are based on the
services complies
metering.
with TCA.
The packets are dyed according

to Traffic Conditioning Agreement
(TCA).
Dropping
Non-TCA-supportive packets are

dropped.
Shaping
The packets in the traffic flow are

delayed as required by the
service model.
Note:
The classification and conditioning of traffic usually happen at the network edge.
The PQs are configured automatically in the NodeB. No manual configuration is

necessary. Table 2.2 shows the rules for configuring PQs based on the three Most
Significant Bits (MSBs) of the DSCP.

30
Chapter 25 IP RAN
Table 2.2 Rules for configuring PQs in NodeB

Three MSBs of the DSCP
PQ
110 or 111
The urgent queue is used by default. No

manual configuration of the PQ is necessary.
101
TOP
100 or 011
MIDDLE
010 or 001
NORMAL
000
BOTTOM
Table 2.3 describes the MML commands on the RNC side for QoS configuration.
Table 2.3 MML commands for QoS configuration on the RNC side
Function
About the congestion
control parameters of
an IP node
To set congestion control parameters
ADD IPNODE
To display congestion control
LST IPNODE
parameters
About the DSCP
To set different DSCPs to IP paths of
parameters of an IP
different types
path
Command
To display IP path parameters
ADD IPPATH
LST IPPATH
Table 2.4 describes the MML commands on the NodeB side for QoS configuration.
Table 2.4 MML commands for QoS configuration on the NodeB side
Function
About the DSCP
To set the priorities for data
parameters
transmission
About the rate restriction

parameters at the
physical port
Command
SET DIFPRI
To display the DSCP parameters
LST DIFPRI
To add rate restriction parameters
SET LR
To display the rate restriction
LST LR
parameters

31
Chapter 25 IP RAN
Parameters:
Parameter Name
Parameter ID
Signaling priority
SIGPRI
GUI Range
063
063
Default Value
None
Optional/Mandatory
MML Command
Optional
SET DIFPRI
Description:
Signaling priority is contained in Common Channel UDP/IP packets.
Parameter Name
Parameter ID
OM priority
OMPRI
GUI Range
063
063
Default Value
None
Optional/Mandatory
MML Command
Optional
SET DIFPRI
Description:
OM priority is contained in operation and maintenance TCP/IP packets of the
NodeB.
VII. Security
The TDM network has a relatively high security. Data of different users is isolated on
different physical channels.
The VLAN plus VPN scheme is implemented in the data network, as shown in Figure
1.1. The security of VLANs is implemented at the NodeB and the RNC, and that of
the VPNs is implemented by external equipment.

32
Chapter 25 IP RAN
Ethernet
VLAN
(V18)
NodeB
Ethernet
VPN
VLAN
(V18)
R
RNC
Figure 1.1 Data network security
25.5 Capabilities
I. IP Transport Capabilities at the RNC
Table 1.1 IP transport capabilities at the RNC
Item
Physical
Sub-item
Description
Board
2 per WRBS
Sub-board
2 per board
FE port
4 per sub-board
E1/T1
16 per sub-board
IP version
IP protocol version
IPv4
Layer 2
MAC/FE
Supported
PPP/E1
Supported
PPPmux/E1
Supported
ML PPP/E1
Supported
Header
IP Header Compression over
Supported (on E1)
compression
PPP (RFC 2507)
QoS
DiffServ
Supported
Security
IPv4 IPSec
Not supported
IPv6 IPSec
Not supported
Capability
Forwarding
60 Mbit/s (traffic)
Reliability
Port backup
Supported (board-level)
Board backup
Supported (WFIE)
interfaces
protocols

33
Chapter 25 IP RAN
II. IP Transport Capabilities at the NodeB

Table 1.1 IP transport capabilities at the NodeB
Item
BBU
Quantity &
Flow
Macro NodeB
Protocol
Quantity
Location
Flow
Protocol
PPP
MAC
ATM
TCP
TCP
UDP
SCTP
&
Location
Local
E1/T1
port
8 per
PPP
subrack
8 per
interface
board
FE
2 per
MAC
subrack
2 per
interface
board
IPoA
Several per
client
subrack
ATM
Several
per
interface
board
Maintenance
1 basic
TCP
flow on the Iub
subrack
subrack
interface
per NodeB
per NodeB
Internal
1 per
maintenance
subrack
TCP
1 basic
1 per
board
flow
Traffic flow
Several per
UDP
subrack
Several
per
interface
board
Signaling flow
Several per
SCTP
subrack
Several
per
interface
board

34
Chapter 25 IP RAN
Item
BBU
Quantity &
Flow
Macro NodeB
Protocol
Quantity
Location
Flow
Protocol
IP
&
Location
IP route flow
Several per
IP
Several
BBU (inter-
per
board flow
interface
supported)
board
(interboard flow
supported)
Note:
H: high
L: low
M: medium
25.6 Implementation
This section describes the procedures to configure the initial data related to the IP
RAN feature, but not the procedures to reconfigure or disable the feature.
Note:
To reconfigure the IP RAN parameters is to configure them again after the NodeB
data is deleted. To disable the IP RAN feature is to delete the data of the NodeB.
At present, the Iub data at the NodeB, but not the RNC, cannot be configured on
the Configuration Management Express (CME). The data at the RNC is configured
on the LMT.
The related personnel must be familiar with CME and RNC LMT operations.
25.6.1 Data Preparation

I. IP Addressing Scheme
The implementation of the IP RAN feature varies according to the transport network
on the Iub interface. This section takes IP transport technology on the Iub interface
and layer 3 networking mode on the Ethernet as an example.
Table 1.1 describes the IP addressing scheme for the networking.
35
Chapter 25 IP RAN
Table 1.1 IP addressing scheme

Data Item
RNC
NodeB
Gateway IP address of router
Data Source
Network plan
IP address and subnet mask of FE port
(interface IP address at the RNC)

Primary and secondary IP addresses of
FE port (interface IP address at the

NodeB)
Local IP address and subnet mask of
PPP/MLPPP link
IP address on the control plane
Traffic IP address
Detecting IP address of IP path
OMIP address at the NodeB
IP address of the external network where

the BAM is located
IP address of the M2000 server
II. Physical Layer and the Data Link Layer Data

Table 1.1 describes the data to be planned and negotiated. The data is transported at
the physical layer and the data link layer.
Table 1.1 Data (physical layer and data link layer) to be planned and negotiated
Data Item
RNC
NodeB
Data Source
Type of interface board
Internal plan
IP address of gateway
Network plan
FE port data
Internal plan
Backup required?/backup
mode
Slot number/port number
IP address and subnet
mask
36
Network plan
Chapter 25 IP RAN
Data Item
RNC
Primary and secondary
NodeB
Data Source
IP addresses
PPP/MLPPP
Subrack number/slot
link data
number/E1T1 port
Internal plan
number
MLPPP group number
Link number
Local IP address and
Network plan
subnet mask
Timeslots
Negotiated data
Note:
If the WFIE, a type of interface board, is used, you must decide whether to use 1:1
backup mode or not.
III. Control Plane Data

Table 1.1 describes the data on the control plane to be planned and negotiated.
Table 1.1 Data on the control plane to be planned and negotiated
Data Item
RNC
NodeB
Iub congestion control algorithm
Negotiated data
Maximum number of HSDPA

subscribers of the NodeB
NCP
Local IP address
(control plane)
Local SCTP port
number
SCTP link working
Data Source
Server
mode

37
Client
Chapter 25 IP RAN
Data Item
CCP
RNC
NodeB
Data Source
Local IP address
(control plane)
Local SCTP port
number
SCTP link working
Server
Client
Server
Client
mode
Port number
CCP
Local IP address
(control plane)
Local SCTP port
number
SCTP link working
mode
Port number
IV. User Plane Data

Table 1.1 describes the data on the user plane to be planned and negotiated.
Table 1.1 Data on the user plane to be planned and negotiated
Data Item
RNC
NodeB
NodeB name
Data Source
Negotiated data
IP node identifier
IP version
IPv4
IPv4
Network plan
Congestion control threshold
Internal plan
Congestion recovery threshold
IP
Port type
Negotiated data
path 1
(Ethernet/PPP/MLPPP/PPP
oE)
IP path type
DSCP
38
Chapter 25 IP RAN
Data Item
RNC
NodeB
Data Source
Path detecting flag

Detecting IP address
IP path identifier
Forward/backward
Internal plan
bandwidth
Subsystem number
Subrack number/slot
number
Local IP address and subnet
Network plan
mask
V. Management Plane Data

Table 1.1 describes the data on the management plane to be planned and negotiated.
Table 1.1 Data on the management plane to be planned and negotiated
Data Item
RNC
OMIP address at the
NodeB
Network plan
NodeB
Interface IP address at
the NodeB
Gateway IP address at
Data Source
the NodeB (layer 3

networking)
the RNC (layer 3

networking)
the RNC

39
Chapter 25 IP RAN
Data Item
RNC
Internal IP address of
192.1.8.4 (slot 0)
the interface board at
192.1.8.5 (slot
the RNC
15)
NodeB
Data Source
Internal IP
addresses
192.1.8.4 (active
WFIE)
192.1.8.1
192.1.1. (subrack
WMUX connecting to
number)
WMUX in the local

subrack
the WRSS
192.1.1.254
WMPU connecting to
the WRBS
IP address of the
Internal plan
external network where

the WMPU is located
IP address of the
internal network where

the BAM is located
IP address of the
Network plan

the BAM is located
IP address of the
M2000 server
VI. Cell Data

Table 1.1 describes the cell data to be planned and negotiated.
Table 1.1 Cell data to be planned and negotiated
Data Item
Cell 0
RNC
Cell name

40
NodeB
Data Source
Chapter 25 IP RAN
Data Item
RNC
NodeB
Local cell ID
Data Source
Negotiated
data
Frequency (UL/DL)
TX diversity
PCPICH transmit power
Maximum cell transmit power
Frequency band indication
DL primary scrambling
Timing offset
Logical cell ID
LAC/RAC/SAC
URA ID
Site ID/sector number
Antenna connector number
UL baseband resource group
Internal plan
number (including UL
processing unit number)
Power amplifier cabinet
number/subrack number/slot
number
Local cell radius
Local cell handover radius
Network plan
25.6.2 Configuration Procedure

I. Hardware Installation
To install the required hardware elements, perform the following steps:
1)
Install the WRBS subrack and related cables, if necessary, before adding the
NodeB.
This step is optional. For details, refer to the RNC Installation Guide.
41
2)
Chapter 25 IP RAN
Install the interface boards of the NodeB and the RNC according to the planned
data.
For the differences between IP interface boards, refer to section 25.2.3
"Miscellaneous."
3)
Configure the LAN switches at the RNC, depending on the necessity to converge
traffic flow at the FE ports. The necessity is specified in the configuration
scheme.
For details, refer to the RNC Commission Guide.
4)
Connect the NodeB to the RNC either in layer 2 or layer 3 networking mode
before data configuration.
For details about how to route the cables, refer to the RNC Installation Guide.
II. Data Configuration at the RNC

The initial data is configured for the RNC by executing related MML commands on the
LMT. To configure initial data at the RNC, perform the following steps:
1)
Execute the ADD SUBRACK command to add a WRBS subrack.

This step is optional.
2)
Execute SET ETHPORT, ADD ETHIP, and ADD ETHREDPORT to set the FE
port data and the port backup properties.
If the Iub interface does not support the transport over Ethernet, this step can be
skipped.
3)
Execute ADD PPPLNK, ADD MPGRP, and ADD MPLNK to add PPP/MLPPP
link data.
If the Iub interface does not support the transport on the private network, this
step can be skipped.
4)
Execute ADD IPOACLIENT, ADD SCTPLOCIP, and ADD SCTPLNK to add

SCTP link data.
5)
Execute ADD NODEB, ADD NODEBALGOPARA, ADD NCP, and ADD CCP to
add the data of Iub ports.
6)
Execute ADD IPNODE to add an IP node.
7)
Execute ADD IPPATH to add an IP path.

If the IP address of the FE port and the local IP address of the PPP/MLPPP link
works as the IP address of the gateway, execute ADD IPOACLIENT to create
the traffic IP address (user plane IP address) of the IP interface board before
adding the IP path. If the IP address of the IP path is that of the FE port or the
local IP address of the PPP/MLPPP link, it is not necessary to configure the
traffic IP address.

42
8)
Chapter 25 IP RAN
Execute ADD IPRSCGRP and ADD IPRSCGRPPATH to add an IP path

resource group.
IP path resource group is a concept related to Ethernet-based transport. It can
be carried by only one FE port. Therefore, all IP paths in the group are carried on
that port.
9)
Execute ADD BAMIPRT and ADD IPRT to add routes on the control plane, user
plane, and management plane.
III. Data Configuration at the NodeB

Figure 1.1 shows the flow chart for configuring IP transport data at the NodeB.
Start
Configure PPP
Configure
PPPoE
Configure MP
Configure
Ethernet IP
Configure IP
route
Optional
Configure
NodeQoS
B
Configure
NBAP
IP
Route
Configure OM
IP Route
Configure IP
IP
pathRoute
End
Figure 1.1 Flow chart for configuring IP transport data at the NodeB
Table 1.1 describes the IP transport data configuration procedure.

43
Chapter 25 IP RAN
Table 1.1 IP transport data configuration procedure

Step
1
Action
Description
Start
Before configuring the IP transport data, set

the following information of the NodeB:
Basic information
Hardware information (for the addition of

the NUTI)
Configure
Usually, one type of link is selected.
PPP/MP/PPPoE/Ethernet
IP
For the transport on the private network,

configure PPP or MP links.
For
the
transport
on
the
Ethernet,
configure PPPoE or Ethernet IP links.

3
Configure IP route
At least routes are configured:
Route on the control plane
Route on the user plane
Route on the management plane
Configure QoS
Optional
Configure NBAP, OM,
To configure the NBAP is to configure the

data on the control plane.
and IP path
To configure OM is to configure the data

on the management plane.
To configure IP paths is to configure the

data on the user plane.
Note:
Configure the data on the three planes in any
order you like.
IV. Data Configuration on the M2000 Server

The routes on the management plane are configured on the M2000 server.
To configure the routes, perform the following steps:
1)
Log in to the Solaris system on the M2000 server with the user name of root.
2)
Execute route add to add a route to the NodeB.
3)
Execute #vi to create the /etc/rc2.d/S97route file.
4)
Record the route to the NodeB in the created file.

44
Chapter 25 IP RAN
The route is permanent.

5)
Save the file, and then exit vi.
V. Cell Data Configuration

To configure cell data at the RNC, perform the following steps:
1)
Execute ADD LOCELL to add the basic data of local cells.
2)
Execute ADD QUICKCELLSETUP to add the data of logical cells.
3)
Execute ACT CELL to activate the cells.
To configure cell data at the NodeB, perform the following steps:

1)
Add the data of sites.
2)
Add the data of sectors.
3)
Add the data of local cells.
VI. Configuration Verification

To verify the configuration, perform the following steps:
1)
Log in to the NodeB LMT.
2)
Execute DSP LOCELL to query the states of the cells.
Table 1.1 describes the states of normal cells. The configuration fails if any of the
queried states falls out of the values.
Table 1.1 Cell states and values
Logical Cell
Local Cell Administration
Operational State
State
Available
Unblocked
Local Cell State
Local cell available
25.6.3 Examples
I. Task Description
As shown in Figure 1.1, the RNC connects to NodeB 1 in 3 x 1 configuration through
Add/Drop Multiplexers (ADMs). Both elements are connected to the following
transport networks:
Private transport network based on SDH or PDH
Ethernet in layer 3 networking mode

45
Chapter 25 IP RAN
E1/T1
ADM
PDH/SDH
ADM
E1/T1
BSC6800
NodeB 1
Ethernet
Figure 1.1 IP RAN topology

Figure 1.2 shows the IP addressing scheme for Ethernet-based IP transport.
FE port:
11.11.11.101
NodeB1
OMIP:
3.3.3.3
Gateway on RNC:
10.10.10.1
15.15.15.15
10.121.139.100
WSPUb
BAM
FE port:
10.10.10.19
W
F
E
E
Router
Gateway on NodeB:
11.11.11.1
10.121.139.200
192.1.1.1
192.1.8.4
WMUXb
192.1.8.1
W
M
P
U
192.1.1.254
IPoA client:
16.16.16.16
BSC6800
Figure 1.2 IP addressing scheme for Ethernet-based IP transport

Figure 1.3 shows the IP addressing scheme based on private transport network (SDH
or PDH).
15.15.15.15
10.121.139.100
WSPUb
BAM
PPP/MLPPP:
17.17.17.17
17.17.17.111
NodeB1
OMIP:
3.3.3.3
W
F
E
E
10.121.139.200
192.1.8.4
192.1.1.1
WMUXb
192.1.8.1
W
M
P
U
192.1.1.254
IPoA client:
18.18.18.18
BSC6800
Figure 1.3 IP addressing scheme based on private transport network

46
Chapter 25 IP RAN
II. Data Preparation

Table 1.1 describes the data to be planned and negotiated. The data is transported at
the physical layer and the data link layer.
Table 1.1 Data (physical layer and data link layer) to be planned and negotiated
Data Item
RNC
NodeB
Data Source
Type of interface board
WFEE
NUTI
Internal plan
IP address of gateway
10.10.10.1
11.11.11.1
Network plan
FE port
Backup
No
No
Internal plan
data
required?/backup
1/0/0
0/12/0
IP address and
10.10.10.19
subnet mask
/255.255.25
mode
Slot number/port
number
Network plan
5.0
Primary and
11.11.11.10
secondary IP
1/255.255.
addresses
255.0/no
secondary
IP address
PPP/ML
Subrack number/slot
PPP
number/E1T1 port
link
number
data
1/0/0
0/12/0
Link number
Local IP address and
17.17.17.17
17.17.17.11
subnet mask
/255.255.25
1/255.255.
5.0
255.0
TS1, TS2,
TS1, TS2,
TS3, TS4,
TS3, TS4,
TS5, TS6
TS5, TS6
MLPPP group
Internal plan
number
Timeslots

47
Network plan
Negotiated data
Chapter 25 IP RAN
Table 1.2 describes the data on the control plane to be planned and negotiated.
Table 1.2 Data on the control plane to be planned and negotiated
Data Item
RNC
NodeB
Iub congestion control algorithm
OFF
OFF
Maximum number of HSDPA
3840
3840
15.15.15.15
17.17.17.111
58080
8021
Server
Client
15.15.15.15
17.17.17.111
58080
8022
Server
Client
Port number
Local IP address
15.15.15.15
17.17.17.111
58080
8023
Server
Client
Data Source
Negotiated data
subscribers of the NodeB

NCP
Local IP address
(control plane)
Local SCTP port
number
SCTP link working
mode
CCP
Local IP address
(control plane)
Local SCTP port
number
SCTP link working
mode
CCP
(control plane)
Local SCTP port
number
SCTP link working
mode
Port number
Table 1.3 describes the data on the user plane to be planned and negotiated.
Table 1.3 Data on the user plane to be planned and negotiated
Data Item
NodeB name
RNC
IP_TRANS

48
NodeB
IP_TRANS
Data Source
Chapter 25 IP RAN
Data Item
NodeB name
RNC
0
NodeB
0
Data Source
Negotiated
data
IP node identifier
IPv4
IPv4
Network plan
IP version
80
Internal plan
Congestion control threshold
70
IP path 1
Eth
Eth
Port type
(Ethernet/PPP/MLP
Negotiated
data
PP/PPPoE)
IP path type
RT
RT
DSCP
EF
EF
Path detecting flag
DISABLED
Detecting IP
IP path identifier
Forward/backward
10000
bandwidth
/10000
Subsystem number
Subrack
1/0
0/12
Local IP address
18.18.18.18
17.17.17.111
and subnet mask
/255.255.255.0
/255.255.25
Internal plan
address
number/slot
number
Network plan
5.0
IP path 2
Port type
PPP
PPP
(Ethernet/PPP/MLP
Negotiated
data
PP/PPPoE)
IP path type
NRT
NRT
DSCP
EF
EF
Path detecting flag
DISABLED

49
Internal plan
Chapter 25 IP RAN
Data Item
RNC
Detecting IP
NodeB
Data Source
IP path identifier
Forward/backward
10000
bandwidth
/10000
Subsystem number
Subrack
1/0
0/12
16.16.16.16
11.11.11.101
/255.255.255.0
/255.255.25
address
number/slot
number
Local IP address
and subnet mask
Network plan
5.0
Table 1.4 describes the data on the management plane to be planned and negotiated.
Table 1.4 Data on the management plane to be planned and negotiated
Data Item
RNC
OMIP address at the
NodeB
3.3.3.3
11.11.11.101
11.11.11.1
10.10.10.1
10.10.10.19
NodeB
the NodeB
the NodeB (layer 3
networking)
the RNC (layer 3
networking)
the RNC

50
Data Source
Network plan
Chapter 25 IP RAN
Data Item
RNC
192.1.8.4 (slot
the interface board at
0)
the RNC
192.1.8.5 (slot
NodeB
Data Source
Internal IP
addresses
15)
192.1.8.4
(active WFIE)
192.1.8.1
192.1.1.1
192.1.1.254
WMUX in the local

subrack
WMUX connecting to
the WRSS
WMPU connecting to
the WRBS
IP address of the
10.121.139.200
Network plan

the WMPU is located
IP address of the
10.121.139.100
internal network where

the BAM is located
IP address of the
10.124.0.100

the BAM is located
IP address of the
M2000 server
(10.124.0.200)
Table 1.5 describes the cell data to be planned and negotiated.

Table 1.5 Cell data to be planned and negotiated
Data Item
Cell 0
RNC
Cell name
Cell 0

51
NodeB
Cell 0
Data Source
Chapter 25 IP RAN
Data Item
RNC
NodeB
Local cell ID
Frequency (UL/DL)
10563/961
10563/96
13
NO_TX_DI
NO_TX_D
VERSITY
IVERSITY
330
430
430
Band1
Timing offset
CHIP0
Logical cell ID
LAC/RAC/SAC
100/-/100
URA ID
URA 1: 0
TX diversity
Data Source
Negotiated
data
Internal plan
of RNC
URA 2: 1
0/0
N0A
0(0)
MASTER/
Internal plan
of NodeB
2/0
number
Cell 1
Local cell radius
5000
150
Cell name
Cell 1
Cell 1
Local cell ID
Frequency (UL/DL)
10563/961
10563/96
13

52
Network plan
Negotiated
data
Chapter 25 IP RAN
Data Item
RNC
NodeB
NO_TX_DI
NO_TX_D
VERSITY
IVERSITY
330
430
430
Band 1
Timing offset
CHIP256
Logical cell ID
LAC/RAC/SAC
100/0/100
URA ID
URA 1: 0
TX diversity
Data Source
Internal plan
of RNC
URA 2: 1
0/1
N0B
0 (1)
MASTER/
Internal plan
of NodeB
2/1
number
Cell 2
Local cell radius
4000
140
Cell name
Cell 2
Cell 2
Local cell ID
Frequency (UL/DL)
10563/961
10563/96
13
NO_TX_DI
NO_TX_D
VERSITY
IVERSITY
330
TX diversity

53
Network plan
Negotiated
data
Chapter 25 IP RAN
Data Item
RNC
NodeB
430
430
Band1
Timing offset
CHIP512
Logical cell ID
LAC/RAC/SAC
100/0/100
URA ID
URA 1: 0
Data Source
Internal plan
of RNC
URA 2: 1
0/2
Internal plan
N1A
0 (2)
MASTER/
of NodeB
2/2
number
Local cell radius
5000
140
Network plan
III. Data Configuration at the RNC

MML commands are executed to configure data at the RNC.
1)
Configure the data at the physical layer and the data link layer.
SET ETHPORT: SRN=1, SN=0, PN=0, MTU=1500, Auto=Enable;
ADD
ETHIP:
SRN=1,
SN=0,
PN=0,
IPADDR="10.10.10.19",
MASK="255.255.255.0", GateWayIPADDR="10.10.10.1";
ADD PPPLNK: SRN=1, SN=0, PPPLNKN=0, DS1=0,
TSBITMAP=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&
TS15&TS17&TS18&TS19, IPADDR="17.17.17.17", MASK="255.255.255.0",
PEERIPADDR="17.17.17.111";
2)
Add the data on the control plane.

54
Chapter 25 IP RAN
//Set the IPoA client of WSPUb. The local IP address of the SCTP link
is 15.15.15.15.
ADD IPOACLIENT: SRN=1, LSN=10, SSN=0, IPADDR="15.15.15.15",
MASK="255.255.255.0";
//Add the local IP address of an SCTP link.

ADD SCTPLOCIP: SRN=1, SSN=0, IPADDR1="15.15.15.15", SRVPN=58080;
//Add the SCTP link.
ADD
SCTPLNK:
SRN=1,
SSN=0,
SCTPLNKN=0,
MODE=SERVER,
PEERIPADDR1="17.17.17.111", PEERPORTNO=8021;
ADD
SCTPLNK:
SRN=1,
SSN=0,
SCTPLNKN=1,
MODE=SERVER,
ADD
SCTPLNK:
SRN=1,
SSN=0,
SCTPLNKN=2,
MODE=SERVER,
//Add a NodeB and set the parameters of the Iub congestion control
algorithm.
ADD
NODEB:
NodeBName="IP_TRANS",
NodeBId=0,
TnlBearerType=IP_TRANS,
IPTRANSAPARTIND=SUPPORT,
IPAPARTTRANSDELAY=100,
SATELLITEIND=FALSE,
SRN=1,
SSN=0,
TRANSDELAY=0,
NodeBType=NORMAL,
NodeBProtclVer=R99;
ADD
NODEBALGOPARA:
NodeBName="IP_TRANS",
IubCongCtrlSwitch=OFF,
NodeBHsdpaMaxUserNum=3840;
//Configure IP transport data for Iub ports.
ADD NCP: NODEBNAME="IP_TRANS", CARRYLNKT=SCTP, SCTPLNKN=0;
ADD CCP: NODEBNAME="IP_TRANS", PN=0, CARRYLNKT=SCTP, SCTPLNKN=1;
ADD CCP: NODEBNAME="IP_TRANS", PN=1, CARRYLNKT=SCTP, SCTPLNKN=2;
3)
Add the data on the user plane.

//Add an IP node.
ADD
IPNODE:
IPNI=0,
CONGESTRTHD=70,
NODEBNAME="IP_TRANS",
IPVER=IPV4,
CONGESTCTHD=80,
RRCFACTOR=50,
CSDATAFACTOR=100, PSDATAFACTOR=100;
//Add IPoA clients based on Ethernet and private network.

55
AMRFACTOR=70,
ADD
Chapter 25 IP RAN
IPOACLIENT:
SRN=1,
LSN=0,
SSN=0,
IPADDR="16.16.16.16",
LSN=0,
SSN=0,
IPADDR="18.18.18.18",
MASK="255.255.255.0";
ADD
IPOACLIENT:
SRN=1,
MASK="255.255.255.0";
//Add IP paths based on hybrid transport.
//Add two IP paths to the IP node. One path based on private network
is realtime. The other one based on Ethernet is non-realtime.
ADD
IPPATH:
IPNI=1,
PATHID=1,
CARRYSRN=1,
IPADDR="18.18.18.18",
CONTROLSSN=0,
CARRYSN=0,
PEERIPADDR="17.17.17.111",
PEERMASK="255.255.255.0", TXBW=10000, RXBW=10000, IPPATHT=RT, DSCP=EF,

PATHCHK=DISABLED;
ADD
IPPATH:IPNI=0,
PEERMASK=255.255.255.0,
PATHID=2,
IPADDR="16.16.16.16",
PEERIPADDR="11.11.11.101",
TXBW=10000,
RXBW=10000, CARRYSN=0, CARRYSRN=1, CONTROLSSN=0, IPPATHT=NRT, DSCP=EF,

PATHCHK=DISABLED;
4)
Add a route.
//Add routes on the control plane.
//Add the route on the control plane to WSPUb. The route goes from the
RNC to the NodeB, and its next hop is WFEE in slot 0.
ADD
IPRT:SRN=1,
LSN=10,
SSN=0,
RTDEST=11.11.11.0,
RTDESTMASK=255.255.255.0, NEXTHOP=192.1.8.4;
//Add routes on the user plane.

//Add the route from the WFEE to the NodeB. The next hop is the IP
address of the gateway at the RNC.
ADD
IPRT:
SRN=11,
LSN=0,
SSN=0,
RTDEST="11.11.11.101",
RTDESTMASK="255.255.255.255", NEXTHOP="10.10.10.1";
//Add routes on the management plane.

//The NodeB OMIP address is assumbed to be 3.3.3.3.
//Add the route form the BAM to WMPU.
ADD BAMIPRT: RTDEST="3.3.3.0", RTDESTMASK="255.255.255.0",
NEXTHOP="10.121.139.200";
//Add the route from WMPU to WMUX. Assuming that the WRBS subrack
number is 1, the internal IP address of WMUX is 192.1.1.1.

56
ADD
Chapter 25 IP RAN
IPRT:
SRN=1,
LSN=0,
SSN=0,
RTDEST="3.3.3.0",
//Add the route from WMUX to the IP interface board.

ADD
IPRT:
SRN=1,
LSN=7,
SSN=0,
RTDEST="3.3.3.0",
//Add the route from the IP interface board to the router.

ADD
IPRT:
SRN=1,
LSN=0,
SSN=0,
RTDEST="3.3.3.0",
IV. Data Configuration at the NodeB

To configure the planned data at the NodeB on the CME, perform the following steps:
1)
Log in to the CME, and then configure data at the NodeB on the CME.
2)
Configure the data at the physical layer and the data link layer in the NodeB IP
Link window.
3)
Configure the IP route data in the NodeB IP Route window.
4)
Configure the data on the control plane on the NBAP tab in the NodeB IP
Transport Layer window.
5)
Configure the data on the management plane on the OM tab in the NodeB IP
Transport Layer window.
6)
Configure the data on the user plane on the IP Path in the NodeB IP Transport
Layer window.
7)
Configure the cell data at the NodeB in the NodeB Radio Layer window.
For details, refer to the BTS3812E and BTS3812A Initial Configuration Guide.
V. Data Configuration on the M2000 Server

To configure data on the M2000 server, perform the following steps:
1)
Log in to the Solaris system on the M2000 server with the user name of root.
2)
Execute the following command to add a route to the NodeB:

route add 3.3.3.0/24 10.124.0.100
3)
Execute the following command to create the /etc/rc2.d/S97route file:

# vi /etc/rc2.d/S97route
4)
Execute the following command to record the route to the NodeB in the created
file. The route is permanent.
route add 3.3.3.0/24 10.124.0.100
5)
Save the file, and then exit vi.

57
Chapter 25 IP RAN
25.7 Maintenance Information

25.7.1 MML Commands
Table 1.1 describes the related MML commands.
Table 1.1 MML commands
Command
Executed to
ADD SUBRACK
Add the subrack that uses the IP interface

board.
ADD NODEB and MOD NODEB
Set or modify the transport properties of the

NodeB.
ADD IPNODE
Add an IP node.
ADD PPPLNK
An a PPP link.
ADD MPGRP
Add an MP group.
ADD MPLNK
Add an MP link.
SET ETHPORT/ADD ETHIP
Set the properties of Ethernet ports.
ADD ETHREDPORT
Add active and standby Etherent ports.
ADD IPOACLIENT
Add the IP address of the IP interface board.
ADD SCTPLOCIP
Add the local IP address of the SCTP.
ADD SCTPLNK
Add the SCTP singaling link.
ADD NCP/ADD CCP
Add an NCP or CCP link.
ADD IPPATH
Add an IP path.
ADD IPRSCGRP
Add an IP path resource group.
ADD IPRSCGRPPATH
Add an IP path to the resource group.
ADD IPRT
Add an IP route.
25.7.2 Alarms
NodeB related alarms:
ALM-2750 FE Chip Initialization Failure
ALM-2751 IP Transmission Network FE Interface Abnormal

58
Chapter 25 IP RAN
ALM-2752 IP Transmission Network PPP Interface Abnormal
ALM-2753 IP Transmission Network ML PPP Interface Abnormal
ALM-2754 IP Transmission Network PPPOE Interface Abnormal
ALM-2755 IP RAN NCP Abnormal
ALM-2756 IP RAN CCP Abnormal
RNC related alarms:
ALM-317 Card Fault
ALM-315 WFIE/WFEE/WEIE Microcode Thread Abort
ALM-316 WFIE/WFEE/WEIE board PCI Channel Abnormity
ALM-851 FE Link Down
ALM-852 FE Link Send Defect Indication
ALM-853 FE Link Receive Defect Indication
ALM-854 FE Link Loop
ALM-2602 PPP/MLPPP Link Down
ALM-2603 PPP/MLPPP Link Loop
ALM-2604 MLPPP Group Down
ALM-2605 MLPPP Band Width Insufficient
ALM-2606 IP PATH Down
ALM-2607 FE Port Band Width Insufficient
ALM-2608 Primary FE Port Band Width Is Different With The Standby Port
ALM-2609 FE Primary/Standby Port SWAP
ALM-2610 Card Type Mismatch
ALM-1851 SCTP Link Down
ALM-1852 SCTP Link Congest
25.7.3 Counters
Table 1.1 describes the counters related to the SCTP.
Table 1.1 Counters related to the SCTP
Counter
Description
VS.SCTP.RX.BYTES
IP bytes received on SCTP links
VS.SCTP.TX.BYTES
IP bytes sent on SCTP links
VS.SCTP.RX.PKGNUM
Number of IP packets received on SCTP

links
VS.SCTP.TX.PKGNUM
Number of IP packets sent on SCTP links
VS.SCTP.RX.BYTES
Maximum IP bytes received on SCTP links
VS.SCTP.TX.BYTES
Maximum IP bytes sent on SCTP links

59
Chapter 25 IP RAN
Counter
Description
VS.SCTP.RX.PKGNUM
Maximum number of IP packets received

on SCTP links
VS.SCTP.TX.PKGNUM
Maximum number of IP packets sent on

SCTP links
VS.SCTP.SERVICE.INTERVAL
SCTP service interval
VS.SCTP.CONGESTION.INTERVAL
SCTP congestion interval
Table 1.2 describes the counters related to the IP PATH feature.

Table 1.2 Counters related to the IP PATH feature
Counter
Description
VS.IPPATH.RX.BYTES
Bytes received on IP paths
VS.IPPATH.TX.BYTES
Bytes sent on IP paths
VS.IPPATH.RX.MEANKBPS
Average rate of data received on IP paths
VS.IPPATH.TX.MEANKBPS
Average rate of data sent on IP paths
VS.IPPATH.PEAK.RXBYTES
Peak bytes received on IP paths
VS.IPPATH.PEAK.TXBYTES
Peak bytes sent on IP paths
25.8 References
3GPP TR25.933 "IP transport in UTRAN"
3GPP TR23.107 "Quality of Service (QoS) concept and architecture"
RFC1661 The Point-to-Point Protocol (PPP), provides a standard method for

transporting multi-protocol datagrams over point-to-point links
RFC1662 PPP in HDLC-link Framing, describes the use of HDLC-like framing

for PPP encapsulated packets
RFC1990 The PPP Multilink Protocol (ML-PPP), describes a method for

splitting, recombining and sequencing datagrams across multiple logical data
links
RFC2686 The Multi-Class Extension to Multi-link PPP (MC-PPP), describes

extensions that allow a sender to fragment the packets of various priorities into
multiple classes of fragments, allowing high-priority packets to be sent between
fragments of lower priorities
60
Chapter 25 IP RAN
RFC3153 PPP Multiplexing (PPPmux), describes a method to reduce the PPP

framing overhead used to transport small packets over low bandwidth links.

61

25-Ip Ran

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

25-Ip Ran

Diunggah oleh

Hak Cipta:

Format Tersedia

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Huawei Technologies Proprietary

RAN Feature Description

Table 25-30 Counters related to the SCTP........................................................................25-52

Huawei Technologies Proprietary

RAN Feature Description

Fully utilizing rich IP network resources

Economical IP network construction

Following the trend in network migration to protect your investment

Huawei Technologies Proprietary

RAN Feature Description

25.1.4 Terms and Abbreviations

In a cascading connection, the output of one entity is considered as

A type of NodeB that can be categorized into outdoor NodeB and

Asymmetrical Digital Subscriber Loop

Asynchronous Transfer Mode

A model of Huawei RNC

A model of Huawei outdoor macro NodeB

A model of Huawei indoor macro NodeB

Communication Control Port

Huawei Technologies Proprietary

RAN Feature Description

A model of Huawei Distributed NodeB

Dynamic Host Configuration Protocol

DiffServ Code Point

Gateway GPRS Support Node

Home Location Register

High Speed Downlink Packet Access

Inverse Multiplexing on ATM

Internet Protocols over ATM

Link Layer Control

Medium Access Control

Multi-Class Extension to Multi-link PPP

PPP Multilink Protocol

Man Machine Language

Most Significant Bit

Mobile Switching Center

NodeB Application Protocol

NodeB Control Port

NodeB Main Processing & Timing unit

NodeB Universal Transport Interface unit

IP Address of Operation and Maintenance

RAN Feature Description

Peripheral Component Interconnect

Plesiochronous Digital Hierarchy

Point-to-Point Protocol over Ethernet

Radio Access Network

Radio Network Controller

Radio Resource Control

Stream Control Transmission Protocol

Synchronous Digital Hierarchy

Serving GPRS Support Node

Synchronous Transport Mode-1

Traffic Conditioning Agreement

Transmission Control Protocol

Time Division Multiplex(ing)

User Datagram Protocol

Universal Mobile Telecommunications System