Document TitleSecurity Level

IUB Protocol PrincipleI. Over ATM1 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 1shows the protocol stack for the ATM-based Iub interface.Figure 1Protocol 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.2 Links on the Iub Interface (over ATM)This section describes the links on the ATM-based Iub interface.Links on the Iub InterfaceThere 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 inFigure 1.Figure 1Links on the Iub interface (over ATM)

NOTE: The links in the NodeB are not shown inFigure 1because the data configuration does not involve the internal information of the NodeB. The RINT shown inFigure 1refers to the ATM interface boards of theBSC6900. For the recommended ATM interface boards of the Iub interface, seeInterface Boards Applicable to Terrestrial Interfaces.SAAL Link of UNI TypeAn 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 inTable 1.Table 1Data carried on SAAL links of UNI type

Data TypeDescription

NCPThe NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP.

CCPA 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.

ALCAPALCAP 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 theBSC6900and the NodeB.AAL2 PathAn AAL2 path is a group of connections between theBSC6900and 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 theBSC6900and the NodeB.IPoA PVCIPoA 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.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 PVCFigure 1shows the IPoA PVCs from theBSC6900to NodeBs.Figure 1IPoA PVCs from theBSC6900to NodeBs

NOTE:The RINT shown inFigure 1refers to the ATM interface boards of theBSC6900. For the recommended ATM interface boards of the Iub interface, seeInterface Boards Applicable to Terrestrial Interfaces.Network SegmentsEach 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 theBSC6900. 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 IP1. 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 1shows the protocol stack for the IP-based Iub interface.Figure 1Protocol stack for the IP-based Iub interface

2. Links on the Iub Interface (over IP)This section describes the links on the IP-based Iub interface.Links on the Iub InterfaceThere 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 inFigure 1.Figure 1Links on the Iub interface (over IP)

NOTE: The links in the NodeB are not shown inFigure 1because the data configuration does not involve the internal information of the NodeB. The RINT shown inFigure 1refers to the IP interface boards of theBSC6900. For the recommended IP interface boards of the Iub interface, seeInterface Boards Applicable to Terrestrial Interfaces.SCTP LinksAn 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 inTable 1.Table 1Data carried on SCTP links

Data TypeDescription

NCPThe NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP.

CCPA 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,SERVERandCLIENT, on theBSC6900and NodeB sides. On theBSC6900side, 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 theBSC6900be set toSERVERwhen you configure an SCTP link.IP PathAn IP path is a group of connections between theBSC6900and the NodeB. An Iub interface has at least one IP path. It is recommended that two or more IP paths be planned.

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 InterfaceThere 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 theBSC6900and NodeB are located on the same network segment and no route is required.Figure 1shows an example of layer 2 networking on the Iub interface.Figure 1Layer 2 networking on the Iub interface

NOTE:IP1 and IP2 are port IP addresses.Figure 2shows an example of layer 3 networking on the Iub interface.Figure 2Layer 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 theBSC6900side. IP7 is the gateway IP address on the NodeB side. IP8 is the IP address of the NodeB.IP Addresses on the Iub InterfaceAs shown inFigure 1andFigure 2, the Iub IP addresses at theBSC6900consist of IP addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups, and device IP addresses.Table 1describes these IP addresses.Table 1IP Addresses on the Iub Interface

IP AddressConfiguration ScenarioConfiguration Restriction

IP address of an Ethernet portRequired when the FG2a/FG2c/GOUa/GOUc board functions as the interface board Each Ethernet port can be configured with only one primary IP address and five secondary IP addresses. The IP address of an Ethernet 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 theBSC6900, 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 a PPP linkRequired when the PEUa, POUa/POUc, or UOIa (UOIa_IP) board functions as the interface boardEach PPP link can be configured with only one local IP address.

Local IP address of an MLPPP groupRequired when the PEUa or POUa/POUc board functions as the interface boardEach MLPPP group can be configured with only one local IP address.

Device IP addressRequired 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 InterfaceOn 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 inTable 2.Table 2Route on the Iub interface

EquipmentRoute Description

IP Interface BoardThe route travels from theBSC6900to the network segment where the NodeB is located.You can configure the route on theBSC6900.Destination IP addressis the address of the network segment where the NodeB or NodeB IP address is located, andNext Hop Addressis the gateway IP address, for example, IP5 or IP6, on theBSC6900side.

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 theBSC6900and the other is the routing between the M2000 and the NodeB not through theBSC6900.Routing Between the M2000 and the NodeB Through theBSC6900Figure 1shows an example of the routing between the M2000 and the NodeB through theBSC6900.Table 1describes the routes.Figure 1Example of the routing between the M2000 and the NodeB through theBSC6900

NOTE: Figure 1takes 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 inFigure 1refers to the IP interface boards of theBSC6900. For the recommended IP interface boards of the Iub interface, seeInterface Boards Applicable to Terrestrial Interfaces.Table 1Routes between the M2000 and the NodeB through theBSC6900

EquipmentForward RouteReverse Route

M2000From the M2000 to the NodeB OM network segment 19.19.19.X, withForward route addressto be the external virtual IP address of the OMU, that is, 172.121.139.200-

BSC6900From the OMU to the NodeB OM network segment 19.19.19.X, withForward route addressto be the internal IP address of the IP interface board at theBSC6900, that is, 80.168.3.66From the IP interface board of theBSC6900to the M2000 IP network segment 172.121.139.XYou can configure the route on theBSC6900side. When you run this command, setEMS IP Addressto the IP address of the M2000, setSubnet maskto the subnet mask of the M2000, and specify the values ofOMU External Network Virtual IPandOMU External Network Mask. In this example,EMS IP Addressis 172.121.139.56, andOMU External Network Virtual IPis 172.121.139.200.

If layer 2 networking is applied, add a route to the OM IP address of the NodeB.Forward route addressmust be the IP address of the NodeB interface board. If layer 3 networking is applied, add a route to the OM IP address of the NodeB.Forward route addressmust be the gateway IP address on theBSC6900side.

NodeB-From the NodeB to the M2000 IP network segment 172.121.139.X If layer 2 networking is applied to the Iub interface,Forward route addressis 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,Forward route addressis the gateway IP address on the NodeB side.

Routing Between the M2000 and the NodeB Not Through theBSC6900If 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 theBSC6900.Figure 2shows an example of routing between the M2000 and the NodeB not through theBSC6900.Table 2describes the routes.Figure 2Example of the routes between the M2000 and the NodeB not through theBSC6900

Table 2Routes between the M2000 and the NodeB not through theBSC6900

EquipmentForward RouteReverse Route

M2000From the M2000 to the NodeB OM network segment 19.19.19.X, withForward route addressbeing the port IP address of router 1, that is, 10.161.215.200-

Router 1From router 1 to the NodeB OM network segment 19.19.19.X, withForward route addressbeing the port IP address of router 2, that is, 172.16.16.10-

Router 2From router 2 to the NodeB OM network segment 19.19.19.X, withForward route addressbeing the IP address of the IP interface board at the NodeB, that is, 16.16.16.2From router 2 to the M2000 network segment 10.161.215.100, withForward route addressbeing the port IP address of router 1, that is, 172.16.16.9

NodeB-From the NodeB to the M2000 network segment 10.161.215.100, withForward route addressbeing the port IP address of router 2, that is, 16.16.16.20

2013-02-20Huawei Proprietary - Restricted DistributionPage6, Total16