Protocol Structure For The Iub Interface

Securit
Document Title
y Level
IUB Protocol Principle

I. Over ATM
1 Protocol Structure for the Iub Interface (over ATM)
When ATM transport is applied to the Iub interface, the sequence of configuring Iub interface
data should be consistent with the protocol structure, that is, from the bottom layer to the top
layer and from the control plane to the user plane.
Figure 1 shows the protocol stack for the ATM-based Iub interface.
Figure 1 Protocol stack for the ATM-based Iub interface
2018-08-22 Huawei Proprietary - P

Restricted Distribution age1,
Total1
8
Securit
Document Title
y Level
The transport network layer of the Iub interface consists of the transport network layer user
plane (area A), transport network layer control plane (area B), and transport network layer user
plane (area C).
 Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three
areas can be carried on common physical links.
 Links in areas A and B are carried on SAAL links. Based on the type of carried information,
the upper layer of area A is classified into the NodeB Control Port (NCP) and the
Communication Control Port (CCP). Only Q.AAL2 links are carried in area B.
 In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is the
ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up or
released for upper-layer services. Therefore, each AAL2 path must have its corresponding
controlling Q.AAL2.
2 Links on the Iub Interface (over ATM)
This section describes the links on the ATM-based Iub interface.
Links on the Iub Interface
There are three types of links on the ATM-based Iub interface: SAAL link of User-Network
Interface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carry
NCP, CCP, and ALCAP, as shown in Figure 1.

Total1
8
Securit
Document Title
y Level
Figure 1 Links on the Iub interface (over ATM)
NOTE:
 The links in the NodeB are not shown in Figure 1 because the data configuration does not
involve the internal information of the NodeB.
 The RINT shown in Figure 1 refers to the ATM interface boards of the BSC6900. For the
recommended ATM interface boards of the Iub interface, see Interface Boards Applicable
to Terrestrial Interfaces.
SAAL Link of UNI Type
An SAAL link of UNI type carries signaling messages on the Iub interface. The signaling
messages carried on the SAAL links are classified into NCP, CCP, and ALCAP, as described
in Table 1.
Table 1 Data carried on SAAL links of UNI type
Data Type Description

Total1
8
Securit
Document Title
y Level
Table 1 Data carried on SAAL links of UNI type
NCP The NCP carries common process messages of NBAP over the
Iub interface. An Iub interface has only one NCP.
CCP A CCP carries dedicated process messages of NBAP over the Iub
interface. An Iub interface may have multiple CCPs. The number
of CCPs depends on network planning.
ALCAP ALCAP is also called Q.AAL2. Typically, an Iub interface has

one ALCAP.
An SAAL link of UNI type is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes
of the PVC must be negotiated between the BSC6900 and the NodeB.
AAL2 Path
An AAL2 path is a group of connections between the BSC6900 and the NodeB. An Iub
interface has at least one AAL2 path. It is recommended that more than one AAL2 path be
planned.
An AAL2 path is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes of the PVC
must be negotiated between the BSC6900 and the NodeB.
IPoA PVC
IPoA is a technology in which IP packets are transmitted over the ATM transport network.
Essentially, the ATM links over each interface are carried over PVCs. The IPoA PVCs over the
Iub interface are used to transmit the OM information of a NodeB. In this case, the IPoA PVC is
called the management plane IPoA PVC.

Total1
8
Securit
Document Title
y Level
3 OM IPoA Data Configuration on the Iub Interface (over
ATM)
On the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance
(OM) channel.
IPoA PVC
Figure 1 shows the IPoA PVCs from the BSC6900 to NodeBs.
Figure 1 IPoA PVCs from the BSC6900 to NodeBs
NOTE:
The RINT shown in Figure 1 refers to the ATM interface boards of the BSC6900. For the
recommended ATM interface boards of the Iub interface, see Interface Boards Applicable to
Terrestrial Interfaces.
Network Segments
Each IPoA PVC travels through the following network segments before reaching the NodeB:
 The 80.168.3.0 segment (with network mask of 255.0.0.0) between the OMUa board and
the ATM interface board. This network segment is set before delivery of the BSC6900.

Total1
8
Securit
Document Title
y Level
 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface
board and the NodeBs. When setting this network segment, you need to take field
conditions into consideration.
II. Over IP
1. Protocol Structure for the Iub Interface (over IP)
When IP transport is applied to the Iub interface, the sequence of adding Iub interface data
should be consistent with the protocol structure, that is, from the bottom layer to the top layer
and from the control plane to the user plane.
Figure 1 shows the protocol stack for the IP-based Iub interface.
Figure 1 Protocol stack for the IP-based Iub interface

Total1
8
Securit
Document Title
y Level
2. Links on the Iub Interface (over IP)
This section describes the links on the IP-based Iub interface.
Links on the Iub Interface
There are two types of links on the IP-based Iub interface: SCTP link and IP path. The SCTP
link is used to carry NCP and CCP, as shown in Figure 1.
Figure 1 Links on the Iub interface (over IP)

Total1
8
Securit
Document Title
y Level
NOTE:
 The links in the NodeB are not shown in Figure 1 because the data configuration does not
involve the internal information of the NodeB.
 The RINT shown in Figure 1 refers to the IP interface boards of the BSC6900. For the
recommended IP interface boards of the Iub interface, see Interface Boards Applicable to
SCTP Links
An SCTP link carries signaling messages on the Iub interface. The signaling messages carried
on the SCTP links are classified into NCP and CCP, as described in Table 1.
Table 1 Data carried on SCTP links
NCP The NCP carries common process messages of NBAP over the Iub interface.

Total1
8
Securit
Document Title
y Level
Table 1 Data carried on SCTP links
An Iub interface has only one NCP.
CCP A CCP carries dedicated process messages of NBAP over the Iub interface.
An Iub interface may have multiple CCPs. The number of CCPs depends on
network planning.
The SCTP link can work in two modes, SERVER and CLIENT, on the BSC6900 and NodeB
sides. On the BSC6900 side, the differences between the two working modes are as follows:
 SERVER: The local end enables only the listening port and the peer end sends the
initialization request.
In SERVER mode, all SCTP links use the listening port as a local port. The listening port
also becomes the local port of NCP or CCP on the control plane. On the NodeB side, a
port number is added to each new NCP and CCP.
 CLIENT: The local end sends the initialization request during the setup of a link.
In CLIENT mode, each SCTP link must be configured with a local port, which means that
a local port number is added to each NCP and CCP. On the NodeB side, only one port
number needs to be configured.
It is recommended that the working mode of the BSC6900 be set to SERVER when you
configure an SCTP link.
IP Path
An IP path is a group of connections between the BSC6900 and the NodeB. An Iub interface
has at least one IP path. It is recommended that two or more IP paths be planned.

Total1
8
Securit
Document Title
y Level
3. IP Addresses and Routes on the Iub Interface (over IP)
On the IP-based or ATM/IP dual stack-based Iub interface, IP addresses and routes are
required.
Networking on the Iub Interface
There are two types of networking on the Iub interface: layer 2 networking and layer 3
networking. Compared with layer 3 networking, layer 2 networking is simple because the port IP
addresses of the BSC6900 and NodeB are located on the same network segment and no route
is required.
Figure 1 shows an example of layer 2 networking on the Iub interface.
Figure 1 Layer 2 networking on the Iub interface
NOTE:
IP1 and IP2 are port IP addresses.
Figure 2 shows an example of layer 3 networking on the Iub interface.

Total1
8
Securit
Document Title
y Level
Figure 2 Layer 3 networking on the Iub interface
NOTE:
IP1 and IP2 are device IP address on the IP interface board. IP3 and IP4 are port IP addresses
on the IP interface board. IP5 and IP6 are gateway IP addresses on the BSC6900 side. IP7 is
the gateway IP address on the NodeB side. IP8 is the IP address of the NodeB.
IP Addresses on the Iub Interface
As shown in Figure 1 and Figure 2, the Iub IP addresses at the BSC6900 consist of IP
addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP
groups, and device IP addresses. Table 1 describes these IP addresses.
Table 1 IP Addresses on the Iub Interface
IP Address Configuration Scenario Configuration Restriction
IP address of an Required when the  Each Ethernet port can be

Ethernet port FG2a/FG2c/GOUa/GOUc board configured with only one
functions as the interface board primary IP address and five
secondary IP addresses.
 The IP address of an Ethernet

Total1
8
Securit
Document Title
y Level
Table 1 IP Addresses on the Iub Interface
IP Address Configuration Scenario Configuration Restriction
port and the internal IP address

of the OMU must be located on
different network segments. For
these network segments, one
cannot cover another.
 In the BSC6900, the IP
addresses of different Ethernet
ports must be located on
different network segments. For
these network segments, one
cannot cover another.
Local IP address of Required when the PEUa, Each PPP link can be configured
a PPP link POUa/POUc, or UOIa (UOIa_IP) with only one local IP address.
board functions as the interface
board
Local IP address of Required when the PEUa or Each MLPPP group can be
an MLPPP group POUa/POUc board functions as configured with only one local IP
the interface board address.
Device IP address Required in layer 3 networking  Each interface board can be

configured with a maximum of
16 device IP addresses.
 The IP addresses of any two
different devices must be located
on different subnets.
Route on the Iub Interface

Total1
8
Securit
Document Title
y Level
On the Iub interface where layer 2 networking is applied, no route is required. On the Iub
interface where layer 3 networking is applied, you should configure the route described in Table
2.
Table 2 Route on the Iub interface
Equipment Route Description
IP Interface The route travels from the BSC6900 to the network segment where the NodeB is locat
Board You can configure the route on the BSC6900. Destination IP address is the addre
the network segment where the NodeB or NodeB IP address is located, and Next H
Address is the gateway IP address, for example, IP5 or IP6, on the BSC6900 side
4 OM Channel Configuration on the Iub Interface (over IP)
There are two types of routing for the OM channel on the Iub interface. One is the routing
between the M2000 and the NodeB through the BSC6900 and the other is the routing between
the M2000 and the NodeB not through the BSC6900.
Routing Between the M2000 and the NodeB Through the BSC6900
Figure 1 shows an example of the routing between the M2000 and the NodeB through
the BSC6900. Table 1 describes the routes.
Figure 1 Example of the routing between the M2000 and the NodeB through
the BSC6900

Total1
8
Securit
Document Title
y Level
NOTE:
 Figure 1 takes layer 2 networking on the Iub interface as an example. When layer 3
networking is applied to the Iub interface, the IP interface board and the NodeB
communicate with each other through a router.
 The RINT shown in Figure 1 refers to the IP interface boards of the BSC6900. For the
recommended IP interface boards of the Iub interface, see Interface Boards Applicable to
Table 1 Routes between the M2000 and the NodeB through the BSC6900
Equipment Forward Route Reverse Route
M2000 From the M2000 to the NodeB OM -

network segment 19.19.19.X,
withForward route address to be
the external virtual IP address of the
OMU, that is, 172.121.139.200
BSC6900 From the OMU to the NodeB OM From the IP

network segment 19.19.19.X, interface board of

Total1
8
Securit
Document Title
y Level
withForward route address to be theBSC6900 to

the internal IP address of the IP the M2000 IP
interface board at the BSC6900, network segment
that is, 80.168.3.66 172.121.139.X
You can configure
 If layer 2 networking is applied,
the route on
add a route to the OM IP address of
theBSC6900 side.
the NodeB. Forward route
When you run this
address must be the IP address of
command,
the NodeB interface board.
set EMS IP
 If layer 3 networking is applied, Address to the IP
add a route to the OM IP address of address of the
the NodeB. Forward route M2000,
address must be the gateway IP set Subnet
address on theBSC6900 side. mask to the
subnet mask of the
M2000, and
specify the values
of OMU
External
Network Virtual
IP andOMU
External
Network Mask.
In this
example, EMS IP
Address is
172.121.139.56,
and OMU
External
Network Virtual

Total1
8
Securit
Document Title
y Level
IP is
172.121.139.200.
NodeB - From the NodeB

to the M2000 IP
network segment
172.121.139.X
 If layer 2
networking is
applied to the
Iub
interface,Forw
ard route
address is the
IP address of
the IP interface
board at
theBSC6900,
that is,
16.16.16.1.
 If layer 3
networking is
applied to the
Iub
interface,Forw
ard route
address is the
gateway IP
address on the
NodeB side.

Total1
8
Securit
Document Title
y Level
Routing Between the M2000 and the NodeB Not Through the BSC6900
If the OM subnet where the M2000 is located is connected to the IP network that covers the
NodeB, routes can be configured between the M2000 and the NodeB not through
the BSC6900. Figure 2 shows an example of routing between the M2000 and the NodeB not
through the BSC6900. Table 2 describes the routes.
Figure 2 Example of the routes between the M2000 and the NodeB not through
the BSC6900
Table 2 Routes between the M2000 and the NodeB not through the BSC6900
M2000 From the M2000 to the NodeB OM -

withForward route address being
the port IP address of router 1, that
is, 10.161.215.200
Router 1 From router 1 to the NodeB OM -

withForward route address being
the port IP address of router 2, that
is, 172.16.16.10
Router 2 From router 2 to the NodeB OM From router 2 to the M2000

network segment 19.19.19.X, network segment 10.161.215.10

Total1
8
Securit
Document Title
y Level
Table 2 Routes between the M2000 and the NodeB not through the BSC6900
withForward route address being withForward route address be

the IP address of the IP interface the port IP address of router 1,
board at the NodeB, that is, is, 172.16.16.9
16.16.16.2
NodeB - From the NodeB to the M2

network segment
10.161.215.100, withForw
route address being the po
IP address of router 2, that
16.16.16.20

Total1
8

Protocol Structure For The Iub Interface

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

Protocol Structure For The Iub Interface

Uploaded by

Copyright:

Available Formats

Securit

IUB Protocol Principle

1 Protocol Structure for the Iub Interface (over ATM)

Figure 1 Protocol stack for the ATM-based Iub interface

2018-08-22 Huawei Proprietary - P

2 Links on the Iub Interface (over ATM)

This section describes the links on the ATM-based Iub interface.

Links on the Iub Interface

2018-08-22 Huawei Proprietary - P

Figure 1 Links on the Iub interface (over ATM)

SAAL Link of UNI Type

Table 1 Data carried on SAAL links of UNI type

Data Type Description

2018-08-22 Huawei Proprietary - P

Table 1 Data carried on SAAL links of UNI type

Data Type Description

ALCAP ALCAP is also called Q.AAL2. Typically, an Iub interface has

2018-08-22 Huawei Proprietary - P

3 OM IPoA Data Configuration on the Iub Interface (over

Figure 1 shows the IPoA PVCs from the BSC6900 to NodeBs.

Figure 1 IPoA PVCs from the BSC6900 to NodeBs

2018-08-22 Huawei Proprietary - P

1. Protocol Structure for the Iub Interface (over IP)

Figure 1 Protocol stack for the IP-based Iub interface

2018-08-22 Huawei Proprietary - P

2. Links on the Iub Interface (over IP)

This section describes the links on the IP-based Iub interface.

Links on the Iub Interface

Figure 1 Links on the Iub interface (over IP)

2018-08-22 Huawei Proprietary - P

Table 1 Data carried on SCTP links

Data Type Description

2018-08-22 Huawei Proprietary - P

Table 1 Data carried on SCTP links

Data Type Description

An Iub interface has only one NCP.

2018-08-22 Huawei Proprietary - P

3. IP Addresses and Routes on the Iub Interface (over IP)

Networking on the Iub Interface

Figure 1 shows an example of layer 2 networking on the Iub interface.

Figure 1 Layer 2 networking on the Iub interface

IP1 and IP2 are port IP addresses.

Figure 2 shows an example of layer 3 networking on the Iub interface.

2018-08-22 Huawei Proprietary - P

Figure 2 Layer 3 networking on the Iub interface

IP Addresses on the Iub Interface

Table 1 IP Addresses on the Iub Interface

IP Address Configuration Scenario Configuration Restriction

IP address of an Required when the  Each Ethernet port can be

2018-08-22 Huawei Proprietary - P

Table 1 IP Addresses on the Iub Interface

IP Address Configuration Scenario Configuration Restriction

port and the internal IP address

Device IP address Required in layer 3 networking  Each interface board can be

Route on the Iub Interface

2018-08-22 Huawei Proprietary - P

Table 2 Route on the Iub interface

Equipment Route Description

4 OM Channel Configuration on the Iub Interface (over IP)

2018-08-22 Huawei Proprietary - P

Equipment Forward Route Reverse Route

M2000 From the M2000 to the NodeB OM -

BSC6900 From the OMU to the NodeB OM From the IP