Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Document Title
y Level
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.
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.
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.
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.
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.
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.
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.
ATM)
On the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance
(OM) channel.
IPoA PVC
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.
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
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.
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.
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
Terrestrial Interfaces.
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.
NCP The NCP carries common process messages of NBAP over the Iub interface.
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.
On the IP-based or ATM/IP dual stack-based Iub interface, IP addresses and routes are
required.
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.
NOTE:
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.
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.
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.
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.
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
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
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
Terrestrial Interfaces.
Table 1 Routes between the M2000 and the NodeB through the BSC6900
Table 1 Routes between the M2000 and the NodeB through the BSC6900
Table 1 Routes between the M2000 and the NodeB through the BSC6900
IP is
172.121.139.200.
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
Table 2 Routes between the M2000 and the NodeB not through the BSC6900