Chapter 25 IP RAN

RAN Feature Description Chapter 25 IP RAN
Chapter 25 IP RAN
25.1 About This Chapter

This chapter describes the following:
 Introduction to IP RAN
 Availability
 Impact
 Technical Description
 Capabilities
 Implementation
 Maintenance Information
 References
25.2 Introduction to IP RAN

25.2.1 Definition
With the IP transport technology, the IP RAN feature enables IP transport on the Iub
interface.
25.2.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.2.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.
Huawei Technologies Proprietary
1
 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.
25.2.4 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.
In a cascading connection, the output of one entity is considered as

the input of its next entity.
Cascading
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
For DiffServ, the Type of Service (ToS) field of the IPv4 header is
DiffServ 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
25.2.5 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
DBS3800 A model of Huawei Distributed NodeB
DHCP Dynamic Host Configuration Protocol
DS Differentiated Services
2

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
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
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
3

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
25.3 Availability
25.3.1 Network Elements Involved
Table 1.1 describes the NEs involved with the IP RAN feature.
Table 1.1 NEs required for IP RAN

MSC
UE NodeB RNC MGW SGSN GGSN HLR
Server
– √ √ – – – – –
Note:
 –: not required
 √: required
25.3.2 License Support
To implement the optional IP RAN feature, you must purchase the license.
4
25.3.3 Software Releases
Table 1.2 describes the versions of RAN products that support IP RAN transport.
Table 1.2 RAN products and related versions

Product Version
RNC BSC6800 V100R007 and later releases
DBS3000
NodeB BTS3812A V100R007 and later releases
BTS3812E
25.3.4 Other Kinds of Support
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
Table 1.3 describes the functions of the IP transport boars and related sub-boards.
5
Table 1.3 Functions of the RNC IP interface boards and related sub-boards
Board Sub-board Functions Port Number
 Providing 32 E1/T1s
 Supporting IP over PPPoE
 Supporting 128 PPP links (0 to
63 for lower sub-board and 64  0 to 15 (for lower
sub-board)
to 127 for upper sub-board)
 16 to 31 (for
 Supporting 32 MLPPP groups upper sub-board)
Two EIU
WEIE Note:
sub-board Note:
 Each MLPPP group can be The ports are
configured with a maximum of 8 numbered from the
MLPPP links. bottom up.
 MLPPP links in one MLPPP
group must be carried on the
same WEIE board.
 Providing 4 FE ports
0 to 3
 Supporting IPoE
Note:
One FIU  Supporting the backup of the
WFIE The ports are
sub-board two FE ports on the same WFIE
numbered from the
 Supporting the backup of the
top down.
two WFIEs in the same WRBS
 Providing 16 E1/T1s
 Providing 4 FE ports
 Supporting IP over PPPoE
 Supporting IPoE
 Supporting the backup of the
two FE ports on the same  0 to 15 (for EIU
WFEE sub-board;
One EIU numbered from
 Supporting 64 PPP links (0 to the bottom up)
sub-board
WFEE and one 63 for lower sub-board)  0 to 3 (for FIU
FIU sub- sub-board;
 Supporting 32 MLPPP groups
board
Note: numbered from
 Each MLPPP group can be the top down)
configured with a maximum of 8

MLPPP links.
 MLPPP links in one MLPPP
group must be carried on the
same WFEE board.
6
II. IP Interface Board for the NodeB
The DBS3000 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.4 Impact
25.4.1 Impact on System Performance
None.
25.4.2 Impact on other Features
None.
25.5 Technical Description

25.5.1 Protocol Stack Based on IP RAN
Figure 1.2 shows the protocol stack for the Iub interface.
7
User plane
Radio Control plane
HSDSCH FP
network
RACH FP
USCH FP
CPCH FP
TFCI2 FP
FACH FP
DCH FP
PCH FP
layer
NBAP
NCP CCP CCP
Tranport Tranport
network layer network layer
user plane user plane
A C
Transport
network SCTP UDP
layer
IP IP
Data link layer Data link layer
Physical layer
Figure 1.2 Protocol stack for the Iub interface (based on IP RAN)
25.5.2 Protocol Encapsulation
As shown in Figure 1.2, 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
25.5.3 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.
8
I. Data Stream Processing of RNC
 UDP/IP packets on the user plane

The UDP/IP packets on the user plane terminate at the IP interface boards. 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.
 SCTP/IP packets on the control plane
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. Conversely, the SCTP/IP
packets from the WSPUb reach 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.
 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 system multiplexing board, through IPoA PVCs. Conversely, the TCP/IP
packets from the WMUXb reach 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.
II. Data Stream Processing of NodeB
To describe the data streams processed by the NodeB, the following definitions are
given:
 Main control unit
The unit, such as the NMPT in the BTS3812E and the BTS3812A and the BBU
in the DBS3800, performs main control and processing.
 Terminating unit
The unit, such as HDLP and HULP, processes services.
 Interface unit
The unit, such as NUTI, provides IP transport interfaces.
Figure 1.3 shows the data streams processed by the NodeB in accordance with the
IP protocol.
9
1
2 Main control unit
3
4
Interface unit
Terminating
Forwarding
Terminating unit
1 Management plane data stream 3 Cascading data stream (NodeB)

2 Control plane data stream 4 User plane data stream
Figure 1.3 Data streams processed by the NodeB
25.5.4 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.4 shows the TDM networking mode.
NodeB
RNC
TDM networking
NodeB
Figure 1.4 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
10
II. Data Network
Figure 1.5 shows the data networking mode.
RNC
NodeB
Data networking
Figure 1.5 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:
 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.6 the hybrid networking mode.
11
TDM networking
RNC
NodeB
Data networking
Figure 1.6 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
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
12
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.5.5 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.7.
Subchannel 1
MP disassembly MP reassembly
Subchannel 2
Large packet at Large packet at

network transport network transport
layer layer
Subchannel 3
Figure 1.7 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
13
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 7.1 describes the IP addressing scheme for the networking.
Table 7.1 IP addressing scheme

Data Item RNC NodeB Data Source
Gateway IP address of router 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 – –
14
 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
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.8 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.
15
 Note:
 The topology takes only layer 2 networking as an example.
 The NodeB is of a macro type.
NodeB IP transport IP transport

board WMUX WSPUb board
IP 5 IP 3
IP 1 IP_2
IP_4 IP_1 IP_5
IP_3
IP 2
IP 6 IP 4
NodeB RNC
Figure 1.8 IP topology of the RAN system - 1
Figure 1.9 shows the IP topology in which the RNC connects to only one NodeB.
WSPUb IP transport NodeB

board
A B
E F
C D
Figure 1.9 IP topology of the RAN system - 2
Table 9.1 describes IP addresses A to F in Figure 1.9.
Table 9.1 IP addresses A to F of the RAN system

No. Address Type Location Description
IP address of the IP interface board
A
FE port of the RNC
Networking based on FE links
IP address of the
B NUTI of the NodeB
FE port
16
No. Address Type Location Description

IP address of the
IP interface board
C port for the
of the RNC
PPP/MLPPP link
Networking based on PPP links
IP address of the
D port for the NUTI of the NodeB
PPP/MLPPP link
IP address on the
E WSPUb of the RNC SCTP coupling at the RNC
control plane
When the IP address of the FE
port and the IP address of the
PPP/MLPPP link at the RNC
IP address on the IP interface board
F works as the IP address of the
user plane of the RNC
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
1.8. These IP addresses are used for your reference only. Perform site operations,
depending on the documents delivered with the related version.
Table 9.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
Active
192.1.8.4
WFIE
WFIE in
active/standby  IP addresses not assigned
IP mode Standby  Assigned the same IP address as that
transport WFIE
board of the active WFIE
WFIE in non Slot 0 192.1.8.4
active/standby
mode) Slot 15 192.1.8.5
III. Numbering Scheme for FE and E/T1 Ports
Table 9.3 describes the numbering scheme for the FE and E1/T1 ports on the NodeB
and the RNC.
17
Table 9.3 Numbering scheme for the FE and E1/T1 ports

Board Location Port Number
0 to 3 (numbered from the top
WFIE One FIU sub-board
down)
0 to 3 (numbered from the top
RNC One FIU upper sub-board
down)
WFEE
0 to 15 (numbered from the
One lower EIU sub-board
bottom up)
Upper FE port 1
NodeB NUTI
Lower FE port 0
IV. Numbering Scheme for PPP Links at the RNC
Table 9.4 describes the numbering scheme for the PPP links at the RNC that
correspond to the sub-board of the WEIE.
Table 9.4 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 9.5.
18
Table 9.5 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.10 shows the DiffServ service processing procedure.
Metering
Data packet Data packet

Shaping/
Classifying Marking
dropping
Figure 1.10 DiffServ service processing procedure
Table 10.1 describes the DiffServ service processing procedure.
Table 10.1 DiffServ service processing procedure

Step Description
Traffic classification enables different types of
Classification of traffic services that are implemented by conditioning them
and setting DS values.
The data rate is metered through
such mechanism as token
Metering bucket. Subsequent shaping and
scheduling are based on the
metering.
The traffic flow
The packets are dyed according involving
Conditioning Marking to Traffic Conditioning Agreement differentiated
(TCA). services complies
Non-TCA-supportive packets are with TCA.
Dropping
dropped.
The packets in the traffic flow are
Shaping delayed as required by the
service model.
Note:
The classification and conditioning of traffic usually happen at the network edge.
19
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.11. The security of VLANs is implemented at the NodeB and the RNC, and that of
the VPNs is implemented by external equipment.
Ethernet VPN Ethernet

VLAN VLAN
(V18) (V18)
NodeB R R RNC
Figure 1.11 Data network security
25.6 Capabilities
I. IP Transport Capabilities at the RNC
Table 11.1 IP Transport Capabilities at the RNC

Item Sub-item Description
Board 2 per WRBS
Physical Sub-board 2 per board

Interfaces FE port 4 per sub-board
E1/T1 16 per sub-board
IP version IP protocol version IPv4
MAC/FE Supported
Layer 2 PPP/E1 Supported

protocols PPPmux/E1 Supported
ML PPP/E1 Supported
Header IP Header Compression over
Supported (on E1)
compression PPP (RFC 2507)
QoS DiffServ Supported
IPv4 IPSec Not supported
Security
IPv6 IPSec Not supported
Capability Forwarding 60 Mbit/s (traffic)
Reliability Port backup Supported (board-level)
20
Item Sub-item Description

Board backup Supported (WFIE)
II. IP Transport Capabilities at the NodeB
Table 11.2 IP transport capabilities at the NodeB

BBU Macro NodeB
Item Quantity
Quantity &
Flow Protocol & Flow Protocol
Location
Location
8 per
8 per
E1/T1 – PPP interface – PPP
subrack
board
2 per
2 per
Local FE – MAC interface – MAC
subrack
port board
Several
IPoA Several per per
– ATM – ATM
client subrack interface
board
Maintenance 1 basic 1 basic
flow on the Iub subrack L TCP subrack L TCP
interface per NodeB per NodeB
Internal
1 per 1 per
maintenance L TCP L TCP
subrack board
flow
Several
Several per per
Traffic flow H UDP H UDP
subrack interface
board
Several
Several per per
Signaling flow M SCTP M SCTP
subrack interface
board
Several
per
Several per
interface
BBU (inter-
IP route flow H IP board H IP
board flow
(inter-
supported)
board flow
supported)
21
BBU Macro NodeB
Item Quantity
Quantity &
Flow Protocol & Flow Protocol
Location
Location
Note:
 H: high
 L: low
 M: medium
25.7 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.7.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 11.3 describes the IP addressing scheme for the networking.
Table 11.3 IP addressing scheme

Gateway IP address of router Network plan
IP address and subnet mask of FE port
–
(interface IP address at the RNC)
22

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 11.4 describes the data to be planned and negotiated. The data is transported
at the physical layer and the data link layer.
Table 11.4 Data (physical layer and data link layer) to be planned and negotiated
Type of interface board Internal plan
IP address of gateway Network plan
Backup required?/backup
mode Internal plan
Slot number/port number
FE port data IP address and subnet
–
mask
Network plan
Primary and secondary
–
IP addresses
Subrack number/slot
number/E1T1 port
number
Internal plan
MLPPP group number
PPP/MLPPP
link data Link number
Local IP address and
Network plan
subnet mask
Timeslots Negotiated data
23
 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 11.5 describes the data on the control plane to be planned and negotiated.
Table 11.5 Data on the control plane to be planned and negotiated

Iub congestion control algorithm
Maximum number of HSDPA
subscribers of the NodeB
Local IP address
(control plane)
Local SCTP port
NCP
number
SCTP link working
Server Client
mode
Local IP address
(control plane)
Local SCTP port Negotiated data
CCP number
SCTP link working
Server Client
mode
Port number
Local IP address
(control plane)
Local SCTP port
CCP number
SCTP link working
Server Client
mode
Port number
IV. User Plane Data
Table 11.6 describes the data on the user plane to be planned and negotiated.
24
Table 11.6 Data on the user plane to be planned and negotiated

NodeB name
Negotiated data
IP node identifier
IP version IPv4 IPv4 Network plan
Congestion control threshold –
Internal plan
Congestion recovery threshold –
Port type
(Ethernet/PPP/MLPPP/PPPoE)
IP path type
Negotiated data
DSCP
Path detecting flag
IP Detecting IP address
path
1 IP path identifier –
Forward/backward bandwidth –
Internal plan
Subsystem number –
Subrack number/slot number –
Local IP address and subnet
Network plan
mask
V. Management Plane Data
Table 11.7 describes the data on the management plane to be planned and
negotiated.
Table 11.7 Data on the management plane to be planned and negotiated

OMIP address at the Network plan
–
NodeB
Interface IP address at
–
the NodeB
Gateway IP address at
the NodeB (layer 3 –
networking)
Gateway IP address at –
the RNC (layer 3
networking)
25

the RNC
192.1.8.4 (slot 0)
192.1.8.5 (slot
Internal IP address of
the interface board at 15) –
the RNC
192.1.8.4 (active
WFIE)
Internal IP address of Internal IP

WMUX in the local 192.1.8.1 – addresses
subrack
192.1.1. (subrack
WMUX connecting to –
number)
the WRSS
WMPU connecting to 192.1.1.254 –
the WRBS
IP address of the
external network where –
the WMPU is located
Internal plan
IP address of the
internal network where –
the BAM is located
IP address of the
external network where –
the BAM is located Network plan
IP address of the
– –
M2000 server
VI. Cell Data
Table 11.8 describes the cell data to be planned and negotiated.
Table 11.8 Cell data to be planned and negotiated

Cell 0 Cell name Negotiated
data
Local cell ID
Frequency (UL/DL)
TX diversity
PCPICH transmit power
26

Maximum cell transmit power
Frequency band indication –
DL primary scrambling –
Timing offset –
Logical cell ID –
LAC/RAC/SAC –
URA ID –
Internal plan
Site ID/sector number –
Antenna connector number –
UL baseband resource group
number (including UL –
processing unit number)
Power amplifier cabinet
number/subrack number/slot –
number
Local cell radius –
Network plan
Local cell handover radius –
25.7.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.
2) 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.3.4"Other
Kinds of Support."
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.
27
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:
5) Execute the ADD SUBRACK command to add a WRBS subrack.
This step is optional.
6) 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.
7) 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.
8) Execute ADD IPOACLIENT, ADD SCTPLOCIP, and ADD SCTPLNK to add
SCTP link data.
9) Execute ADD NODEB, ADD NODEBALGOPARA, ADD NCP, and ADD CCP to
add the data of Iub ports.
10) Execute ADD IPNODE to add an IP node.
11) 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.
12) 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.
13) 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.12 shows the flow chart for configuring IP transport data at the NodeB.
28
Start
Configure Configure
Configure PPP Configure MP
PPPoE Ethernet IP
Configure IP
route
Optional
增加物理
Configure
NodeQoS
B
Configure
NBAP
配置IP Route
Configure OM
配置IP Route
Configure IP
pathRoute
配置IP
End
Figure 1.12 Flow chart for configuring IP transport data at the NodeB
Table 12.1 describes the IP transport data configuration procedure.
Table 12.1 IP transport data configuration procedure

Step Action Description
Before configuring the IP transport data, set
the following information of the NodeB:
1 Start  Basic information
 Hardware information (for the addition of
the NUTI)
Usually, one type of link is selected.
Configure
 For the transport on the private network,
2 PPP/MP/PPPoE/Ethernet configure PPP or MP links.
IP  For the transport on the Ethernet,
configure PPPoE or Ethernet IP links.
29
Step Action Description

At least routes are configured:
 Route on the control plane
3 Configure IP route
 Route on the user plane
 Route on the management plane
4 Configure QoS Optional
 To configure the NBAP is to configure the
data on the control plane.
 To configure OM is to configure the data
on the management plane.
Configure NBAP, OM,  To configure IP paths is to configure the
5
and IP path 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:
14) Log in to the Solaris system on the M2000 server with the user name of root.
15) Execute route add to add a route to the NodeB.
16) Execute #vi to create the /etc/rc2.d/S97route file.
17) Record the route to the NodeB in the created file.
The route is permanent.
18) Save the file, and then exit vi.
V. Cell Data Configuration
To configure cell data at the RNC, perform the following steps:

19) Execute ADD LOCELL to add the basic data of local cells.
20) Execute ADD QUICKCELLSETUP to add the data of logical cells.
21) 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.
30
VI. Configuration Verification
To verify the configuration, perform the following steps:

4) Log in to the NodeB LMT.
5) Execute DSP LOCELL to query the states of the cells.
Table 12.2 describes the states of normal cells. The configuration fails if any of the
queried states falls out of the values.
Table 12.2 Cell states and values

Logical Cell Local Cell Administration
Local Cell State
Operational State State
Available Unblocked Local cell available
25.7.3 Examples
I. Task Description
As shown in Figure 1.13, 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
ADM PDH/SDH ADM

E1/T1 E1/T1
BSC6800
NodeB 1
Ethernet
Figure 1.13 IP RAN topology
Figure 1.14 shows the IP addressing scheme for Ethernet-based IP transport.
31
15.15.15.15 10.121.139.100
WSPUb BAM
FE port:
Gateway on RNC: 10.10.10.19 10.121.139.200
FE port: 10.10.10.1
11.11.11.101 W 192.1.8.4 192.1.1.1 W
NodeB1 Router F WMUXb M
E P
OMIP: E 192.1.8.1 U
Gateway on NodeB:
3.3.3.3
11.11.11.1 IPoA client: 192.1.1.254
16.16.16.16
BSC6800
Figure 1.14 IP addressing scheme for Ethernet-based IP transport
Figure 1.15 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 10.121.139.200
17.17.17.111 W W
192.1.8.4 192.1.1.1
NodeB1 F WMUXb M
E P
192.1.8.1
OMIP: E U
3.3.3.3
IPoA client: 192.1.1.254
18.18.18.18
BSC6800
Figure 1.15 IP addressing scheme based on private transport network
II. Data Preparation
Table 15.1 describes the data to be planned and negotiated. The data is transported
at the physical layer and the data link layer.
Table 15.1 Data (physical layer and data link layer) to be planned and negotiated
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
mode
32

Slot number/port
1/0/0 0/12/0
number
10.10.10.19
IP address and
/255.255.25 –
subnet mask
5.0
11.11.11.10 Network plan
Primary and 1/255.255.
secondary IP – 255.0/no
addresses secondary
IP address
Subrack number/slot
number/E1T1 port 1/0/0 0/12/0
number
Internal plan
MLPPP group
– –
number
PPP/ML
PPP Link number 0 0
link
data 17.17.17.17 17.17.17.11
Local IP address and
/255.255.25 1/255.255. Network plan
subnet mask
5.0 255.0
TS1, TS2, TS1, TS2,
Timeslots TS3, TS4, TS3, TS4, Negotiated data
TS5, TS6 TS5, TS6
Table 15.2 describes the data on the control plane to be planned and negotiated.
Table 15.2 Data on the control plane to be planned and negotiated

Iub congestion control algorithm OFF OFF Negotiated data
Maximum number of HSDPA
3840 3840
subscribers of the NodeB
Local IP address
15.15.15.15 17.17.17.111
(control plane)
Local SCTP port
NCP 58080 8021
number
SCTP link working
Server Client
mode
CCP Local IP address
15.15.15.15 17.17.17.111
(control plane)
Local SCTP port 58080 8022
number
33

SCTP link working
Server Client
mode
Port number 0 0
Local IP address
15.15.15.15 17.17.17.111
(control plane)
Local SCTP port
58080 8023
CCP number
SCTP link working
Server Client
mode
Port number 1 1
Table 15.3 describes the data on the user plane to be planned and negotiated.
Table 15.3 Data on the user plane to be planned and negotiated

NodeB name IP_TRANS IP_TRANS Negotiated
NodeB name 0 0 data
IP node identifier IPv4 IPv4 Network plan

IP version 80 –
Internal plan
Congestion control threshold 70 –
IP path 1 Port type
(Ethernet/PPP/MLP Eth Eth
PP/PPPoE) Negotiated
data
IP path type RT RT
DSCP EF EF
Path detecting flag DISABLED – Internal plan
Detecting IP
– –
address
IP path identifier 1 1
Forward/backward 10000
–
bandwidth /10000
Subsystem number 0 –
Subrack 1/0 0/12
number/slot
number
34
18.18.18.18 17.17.17.111
Local IP address
/255.255.25 Network plan
and subnet mask /255.255.255.0 5.0
Port type
(Ethernet/PPP/MLP PPP PPP
PP/PPPoE) Negotiated
data
IP path type NRT NRT
DSCP EF EF
Path detecting flag DISABLED –
Detecting IP
– –
address
IP path identifier 2 2
IP path 2
Forward/backward 10000
– Internal plan
bandwidth /10000
Subsystem number 0 –
Subrack
number/slot 1/0 0/12
number
16.16.16.16 11.11.11.101
Local IP address
/255.255.25 Network plan
and subnet mask /255.255.255.0 5.0
Table 15.4 describes the data on the management plane to be planned and
negotiated.
Table 15.4 Data on the management plane to be planned and negotiated

OMIP address at the
– 3.3.3.3
NodeB
– 11.11.11.101
the NodeB
the NodeB (layer 3 – 11.11.11.1
Network plan
networking)
the RNC (layer 3 10.10.10.1 –
networking)
10.10.10.19 –
the RNC
35

192.1.8.4 (slot
0)
Internal IP address of 192.1.8.5 (slot
the interface board at 15) –
the RNC
192.1.8.4
(active WFIE)
Internal IP address of Internal IP

WMUX in the local 192.1.8.1 – addresses
subrack
WMUX connecting to 192.1.1.1 –
the WRSS
WMPU connecting to 192.1.1.254 –
the WRBS
IP address of the
external network where 10.121.139.200
the WMPU is located
IP address of the
internal network where 10.121.139.100 Network plan
the BAM is located
IP address of the
external network where 10.124.0.100 –
the BAM is located
IP address of the
M2000 server – –
(10.124.0.200)
Table 15.5 describes the cell data to be planned and negotiated.
Table 15.5 Cell data to be planned and negotiated

Cell 0 Cell name Cell 0 Cell 0 Negotiated
data
Local cell ID 0 0
10563/961 10563/96
Frequency (UL/DL)
3 13
NO_TX_DI NO_TX_D
TX diversity
VERSITY IVERSITY
PCPICH transmit power 330 –
Maximum cell transmit power 430 430
36

Frequency band indication Band1 –
DL primary scrambling 0 –
Timing offset CHIP0 –
Internal plan
Logical cell ID 0 –
of RNC
LAC/RAC/SAC 100/-/100 –
URA 1: 0
URA ID –
URA 2: 1
Site ID/sector number – 0/0

Antenna connector number – N0A
number (including UL – 0（0） Internal plan
processing unit number) of NodeB

MASTER/
2/0
number
Local cell radius – 5000
Network plan
Local cell handover radius – 150
Cell 1 Cell name Cell 1 Cell 1
Local cell ID 1 1
10563/961 10563/96
Frequency (UL/DL)
3 13 Negotiated
NO_TX_DI NO_TX_D data
TX diversity
VERSITY IVERSITY
Frequency band indication Band 1 –
Internal plan
of RNC
LAC/RAC/SAC 100/0/100 –
URA 1: 0
URA ID –
URA 2: 1
Site ID/sector number – 0/1 Internal plan

of NodeB
Antenna connector number – N0B
37

number (including UL – 0（1）
processing unit number)
MASTER/
2/1
number
Network plan
Cell name Cell 2 Cell 2
Local cell ID 2 2
10563/961 10563/96
Frequency (UL/DL)
3 13 Negotiated
NO_TX_DI NO_TX_D data
TX diversity
VERSITY IVERSITY
Frequency band indication Band1 –
Internal plan
of RNC
Cell 2
LAC/RAC/SAC 100/0/100 –
URA 1: 0
URA ID –
URA 2: 1
Site ID/sector number – 0/2

Antenna connector number – N1A
number (including UL – 0 (2) Internal plan
processing unit number) of NodeB

MASTER/
2/2
number
Network plan
III. Data Configuration at the RNC
MML commands are executed to configure data at the RNC.
38
6) 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";
7) Add the data on the control plane.

//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 a NodeB and set the parameters of the Iub congestion control
algorithm.
ADD NODEB: NodeBName="IP_TRANS", NodeBId=0, SRN=1, SSN=0,

TnlBearerType=IP_TRANS, IPTRANSAPARTIND=SUPPORT, TRANSDELAY=0,
IPAPARTTRANSDELAY=100, SATELLITEIND=FALSE, 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;
39
8) Add the data on the user plane.

//Add an IP node.
ADD IPNODE: IPNI=0, NODEBNAME="IP_TRANS", CONGESTCTHD=80,

CONGESTRTHD=70, IPVER=IPV4, RRCFACTOR=50, AMRFACTOR=70,
CSDATAFACTOR=100, PSDATAFACTOR=100;
//Add IPoA clients based on Ethernet and private network.

MASK="255.255.255.0";

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, CONTROLSSN=0, CARRYSN=0,

IPADDR="18.18.18.18", PEERIPADDR="17.17.17.111",
PEERMASK="255.255.255.0", TXBW=10000, RXBW=10000, IPPATHT=RT, DSCP=EF,
PATHCHK=DISABLED;
ADD IPPATH:IPNI=0, PATHID=2, IPADDR="16.16.16.16",

PEERMASK=255.255.255.0, PEERIPADDR="11.11.11.101", TXBW=10000,
RXBW=10000, CARRYSN=0, CARRYSRN=1, CONTROLSSN=0, IPPATHT=NRT, DSCP=EF,
PATHCHK=DISABLED;
9) 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";
40
//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.

//Add the route from WMUX to the IP interface board.

//Add the route from the IP interface board to the router.

IV. Data Configuration at the NodeB
To configure the planned data at the NodeB on the CME, perform the following steps:
10) Log in to the CME, and then configure data at the NodeB on the CME.
11) Configure the data at the physical layer and the data link layer in the NodeB IP
Link window.
12) Configure the IP route data in the NodeB IP Route window.
13) Configure the data on the control plane on the NBAP tab in the NodeB IP
Transport Layer window.
14) Configure the data on the management plane on the OM tab in the NodeB IP
Transport Layer window.
15) Configure the data on the user plane on the IP Path in the NodeB IP Transport
Layer window.
16) 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:
41
17) Log in to the Solaris system on the M2000 server with the user name of root.
18) Execute the following command to add a route to the NodeB:
route add 3.3.3.0/24 10.124.0.100
19) Execute the following command to create the /etc/rc2.d/S97route file:
# vi /etc/rc2.d/S97route
20) 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
21) Save the file, and then exit vi.
25.8 Maintenance Information

25.8.1 MML Commands
Table 15.6 describes the related MML commands.
Table 15.6 MML commands

Command Executed to…
Add the subrack that uses the IP interface
ADD SUBRACK
board.
Set or modify the transport properties of the
ADD NODEB and MOD NODEB
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.
42
25.8.2 Alarms
NodeB related alarms:

 ALM-2750 FE Chip Initialization Failure
 ALM-2751 IP Transmission Network FE Interface Abnormal
 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.8.3 Counters
Table 15.7 describes the counters related to the SCTP.
Table 15.7 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
Number of IP packets received on SCTP
VS.SCTP.RX.PKGNUM
links
VS.SCTP.TX.PKGNUM Number of IP packets sent on SCTP links
43
Counter Description
VS.SCTP.RX.BYTES Maximum IP bytes received on SCTP links
VS.SCTP.TX.BYTES Maximum IP bytes sent on SCTP links
Maximum number of IP packets received
VS.SCTP.RX.PKGNUM
on SCTP links
Maximum number of IP packets sent on
VS.SCTP.TX.PKGNUM
SCTP links
VS.SCTP.SERVICE.INTERVAL SCTP service interval
VS.SCTP.CONGESTION.INTERVAL SCTP congestion interval
Table 15.8 describes the counters related to the IP PATH feature.
Table 15.8 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.9 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
 RFC3153 – PPP Multiplexing (PPPmux), describes a method to reduce the PPP
44
framing overhead used to transport small packets over low bandwidth links.
45

Chapter 25 IP RAN

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Chapter 25 IP RAN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 25 IP RAN

Uploaded by

Copyright:

Available Formats

RAN Feature Description Chapter 25 IP RAN

25.1 About This Chapter

25.2 Introduction to IP RAN

The IP RAN feature is implemented to:

The IP RAN feature yields the following benefits:

Huawei Technologies Proprietary

 Following the trend in network migration to protect your investment

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

Abbreviation Full Spelling

Huawei Technologies Proprietary

Abbreviation Full Spelling

Huawei Technologies Proprietary

Abbreviation Full Spelling

Table 1.1 NEs required for IP RAN

25.3.2 License Support

Huawei Technologies Proprietary

25.3.3 Software Releases

Table 1.2 RAN products and related versions

25.3.4 Other Kinds of Support

I. IP Interface Boards for the RNC

Huawei Technologies Proprietary

configured with a maximum of 8

Huawei Technologies Proprietary

II. IP Interface Board for the NodeB

The DBS3000 of earlier versions has FE ports. Therefore, no hardware change is

25.4.2 Impact on other Features

25.5 Technical Description

Huawei Technologies Proprietary

NCP CCP CCP

Data link layer Data link layer

25.5.2 Protocol Encapsulation

As shown in Figure 1.2, the introduction of the IP transport technology enables:

25.5.3 Data Streams

Huawei Technologies Proprietary

I. Data Stream Processing of RNC

 UDP/IP packets on the user plane

II. Data Stream Processing of NodeB

Huawei Technologies Proprietary

1 Management plane data stream 3 Cascading data stream (NodeB)

Figure 1.4 shows the TDM networking mode.

Figure 1.4 TDM networking mode

Huawei Technologies Proprietary

II. Data Network

Figure 1.5 shows the data networking mode.

Figure 1.5 Data networking mode

The data network can be any of the following three types:

III. Hybrid Transport Network

Figure 1.6 the hybrid networking mode.

Huawei Technologies Proprietary

Figure 1.6 Hybrid networking mode

Hybrid transport enables services of different QoSs to be transported in different

Huawei Technologies Proprietary

25.5.5 Implementation Policies

I. Data Link Layer

Large packet at Large packet at

Figure 1.7 Implementation of MLPPP links

In compliance with the MLPPP protocol, multiple physically independent physical

II. IP Addressing Scheme