Protocol Structure for the Iub Interface

Document Title

Securit Level

IUB Protocol Principle I. Over ATM 1

Protoc Pro tocol ol Struc Structure ture for the Iub Int Interf erface ace (ov (over er ATM TM))

When ATM transport is applied to the Iub interface, the sequence of configuring Iub interface data should be consistent ith the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane! "igure # shos # shos the protocol stac$ for the ATM%based Iub interface! Figure 1 &rotocol stac$ for the ATM%based Iub interface

The transport netor$ layer of the Iub interface consists of the transport netor$ layer user plane 'area A(, transport netor$ layer control plane 'area )(, and transport netor$ layer user plane 'area *(! •

Areas A, A, ), and * share share the physical physical layer and ATM ATM layer! layer! Therefore, Therefore, all lin$s lin$s in the three areas can be carried on common physical lin$s!

+#-% .%#-

/uaei &roprietary % 0estricted Distribution

& age #, Total #1

Document Title

•

•



Securit Level

Lin$s in areas A and ) are carried on SAAL lin$s! )ased on the type of carried information, the upper layer of area A is classified into the 2ode) *ontrol &ort '2*&( and the *ommunication *ontrol &ort '**&(! 3nly 4!AAL+ lin$s are carried in area )! In area *, the user plane data is carried on AAL+ paths! The bearer at the loer layer is the ATM &5*! 6nder the control of 4!AAL+, AAL+ connections can be dynamically set up or released for upper%layer services! Therefore, each AAL+ path must have its corresponding controlling 4!AAL+!

!in"# on the Iub Interface (over ATM)

This section describes the lin$s on the ATM%based Iub interface!

!in"# on the Iub Interface There are three types of lin$s on the ATM%based Iub interface7 SAAL lin$ of 6ser%2etor$ Interface '62I( type, AAL+ path, and I&oA &5*! The SAAL lin$ of 62I type is used to carry 2*&, **&, and AL*A&, as shon in "igure #! Figure 1 Lin$s on the Iub interface 'over ATM(

$OT%& •

The lin$s in the 2ode) are not shon in "igure # because the data configuration does not involve the internal information of the 2ode)!

+#-% .%#-


& age +, Total #1

Document Title

•

Securit Level

The 0I2T shon in "igure # refers to the ATM interface boards of the )S*.1! "or the recommended ATM interface boards of the Iub interface, see Interface )oards Applicable to Terrestrial Interfaces!

SAA! !in" of U$I T'pe An SAAL lin$ of 62I type carries signaling messages on the Iub interface! The signaling messages carried on the SAAL lin$s are classified into 2*&, **&, and AL*A&, as described in Table #!

Table 1 Data carried on SAAL links of UNI type Data Type

Description

NCP

The NCP carries common process messages of NBAP over the I! interface" An I! interface has only one NCP"

CCP

A CCP carries dedicated process messages of NBAP over the I! interface" An I! interface may have mltiple CCPs" The nm!er of CCPs depends on net#ork planning"

ALCAP

ALCAP is also called $"AAL%" Typically& an I! interface has one ALCAP"

An SAAL lin$ of 62I type is carried on a &5*! The &5* identifier '5&I85*I( and other attributes of the &5* must be negotiated beteen the )S*.1 and the 2ode)!

AA! Path An AAL+ path is a group of connections beteen the )S*.1 and the 2ode)! An Iub interface has at least one AAL+ path! It is recommended that more than one AAL+ path be planned! An AAL+ path is carried on a &5*! The &5* identifier '5&I85*I( and other attributes of the &5* must be negotiated beteen the )S*.1 and the 2ode)!

IPoA P I&oA is a technology in hich I& pac$ets are transmitted over the ATM transport netor$! 9ssentially, the ATM lin$s over each interface are carried over &5*s! The I&oA &5*s over the Iub interface are used to transmit the 3M information of a 2ode)! In this case, the I&oA &5* is called the management plane I&oA &5*!

+#-% .%#-


& age :, Total #1

Document Title

Securit Level

* OM IPoA +ata onfiguration on the Iub Interface (over ATM) 3n the ATM%based Iub interface, the I&oA &5* functions as the 3peration and Maintenance '3M( channel!

I&oA &5* "igure # shos the I&oA &5*s from the )S*.1 to 2ode)s! Figure 1 I&oA &5*s from the )S*.1 to 2ode)s

$OT%& The 0I2T shon in "igure # refers to the ATM interface boards of the )S*.1! "or the recommended ATM interface boards of the Iub interface, see Interface )oards Applicable to Terrestrial Interfaces!

2etor$ Segments 9ach I&oA &5* travels through the folloing netor$ segments before reaching the

+#-% .%#-


& age ;, Total #1

Document Title

Securit Level

2ode)7

•

•

II.

The <!#.
Over IP 1. Protocol Structure for the Iub Interface (over IP) When I& transport is applied to the Iub interface, the sequence of adding Iub interface data should be consistent ith the protocol structure, that is, from the bottom layer to the top layer and from the control plane to the user plane! "igure # shos the protocol stac$ for the I&%based Iub interface! Figure 1 &rotocol stac$ for the I&%based Iub interface

+#-% .%#-


& age -, Total #1

Document Title

Securit Level

. !in"# on the Iub Interface (over IP) This section describes the lin$s on the I&%based Iub interface!

Lin$s on the Iub Interface There are to types of lin$s on the I&%based Iub interface7 S*T& lin$ and I& path! The S*T& lin$ is used to carry 2*& and **&, as shon in "igure #! Figure 1 Lin$s on the Iub interface 'over I&(

+#-% .%#-


& age ., Total #1

Document Title

Securit Level

$OT%& •

•

The lin$s in the 2ode) are not shon in "igure # because the data configuration does not involve the internal information of the 2ode)! The 0I2T shon in "igure # refers to the I& interface boards of the )S*.1! "or the recommended I& interface boards of the Iub interface, see Interface )oards Applicable to Terrestrial Interfaces!

S*T& Lin$s An S*T& lin$ carries signaling messages on the Iub interface! The signaling messages carried on the S*T& lin$s are classified into 2*& and **&, as described in Table #!

+#-% .%#-


& age =, Total #1

Document Title

Securit Level

Table 1 Data carried on SCTP links

Data Type

NCP

Description

The NCP carries common process messages of NBAP over the I! interface" An I! interface has only one NCP"

CCP

A CCP carries dedicated process messages of NBAP over the I! interface" An I! interface may have mltiple CCPs" The nm!er of CCPs depends on net#ork planning"

The S*T& lin$ can or$ in to modes, S%,%, and !I%$T, on the )S*.1 and 2ode) sides! 3n the )S*.1 side, the differences beteen the to or$ing modes are as follos7

•

S%,%,7 The local end enables only the listening port and the peer end sends the initiali>ation request! In S90590 mode, all S*T& lin$s use the listening port as a local port! The listening port also becomes the local port of 2*& or **& on the control plane! 3n the 2ode) side, a port number is added to each ne 2*& and **&!

•

!I%$T7 The local end sends the initiali>ation request during the setup of a lin$! In *LI92T mode, each S*T& lin$ must be configured ith a local port, hich means that a local port number is added to each 2*& and **&! 3n the 2ode) side, only one port number needs to be configured!

It is recommended that the or$ing mode of the )S*.1 be set to S%,%, hen you

+#-% .%#-


& age <, Total #1

Document Title

Securit Level

configure an S*T& lin$!

I& &ath An I& path is a group of connections beteen the )S*.1 and the 2ode)! An Iub interface has at least one I& path! It is recommended that to or more I& paths be planned!

*. IP A--re##e# an- ,oute# on the Iub Interface (over IP) 3n the I&%based or ATM8I& dual stac$%based Iub interface, I& addresses and routes are required!

2etor$ing on the Iub Interface There are to types of netor$ing on the Iub interface7 layer + netor$ing and layer : netor$ing! *ompared ith layer : netor$ing, layer + netor$ing is simple because the port I& addresses of the )S*.1 and 2ode) are located on the same netor$ segment and no route is required! "igure # shos an e?ample of layer + netor$ing on the Iub interface! Figure 1 Layer + netor$ing on the Iub interface

+#-% .%#-


& age 1, Total #1

Document Title

Securit Level

$OT%& I&# and I&+ are port I& addresses! "igure + shos an e?ample of layer : netor$ing on the Iub interface! Figure  Layer : netor$ing on the Iub interface

+#-% .%#-


& age #, Total #1

Document

Securit Level

Title

$OT%& I&# and I&+ are device I& address on the I& interface board! I&: and I&; are port I& addresses on the I& interface board! I&- and I&. are gateay I& addresses on the )S*.1 side! I&= is the gateay I& address on the 2ode) side! I&< is the I& address of the 2ode)!

I& Addresses on the Iub Interface As shon in "igure # and "igure +, the Iub I& addresses at the )S*.1 consist of I& addresses of 9thernet ports, local I& addresses of &&& lin$s, local I& addresses of ML&&& groups, and device I& addresses! Table # describes these I& addresses!

Table 1 IP Addresses on the I! Interface

IP Address

Configuration Scenario

Configuration Restriction

•

IP address of an

'e(ired #hen the )*%a+)*%c+*,Ua+*,Uc

+#-% .%#-


-ach -thernet port can !e configred #ith only one primary IP address and five secondary IP addresses"

& age ##, Total #1

Document

Securit Level

Title

Table 1 IP Addresses on the I! Interface

IP Address

Configuration Scenario

Configuration Restriction

•

-thernet port

!oard fnctions as the interface !oard

•

The IP address of an -thernet port and the internal IP address of the ,.U mst !e located on different net#ork segments" )or these net#ork segments& one cannot cover another" In the BSC/011& the IP addresses of different -thernet ports mst !e located on different net#ork segments" )or these net#ork segments& one cannot cover another"

Local IP address

'e(ired #hen the P-Ua&

-ach PPP link can !e

of a PPP link

P,Ua+P,Uc& or U,Ia

configred #ith only one local

2U,Ia3IP4 !oard fnctions as

IP address"

the interface !oard

Local IP address

'e(ired #hen the P-Ua or

-ach .LPPP grop can !e

of an .LPPP

P,Ua+P,Uc !oard fnctions as

configred #ith only one local

grop

the interface !oard

IP address"

•

Device IP

'e(ired in layer 5 net#orking

address

•

+#-% .%#-


-ach interface !oard can !e configred #ith a ma6imm of 7/ device IP addresses" The IP addresses of any t#o different devices mst !e located on different s!nets"

& age #+, Total #1

Document Title

Securit Level

0oute on the Iub Interface 3n the Iub interface here layer + netor$ing is applied, no route is required! 3n the Iub interface here layer : netor$ing is applied, you should configure the route described in Table +!

Table 2 'ote on the I! interface

Equipment

Route Description

IP Interface

The rote travels from the BSC/011 to the net#ork segment #here the NodeB is

Board

located" 8o can configre the rote on the BSC/011" Destination IP address is the addr of the net#ork segment #here the NodeB or NodeB IP address is located& and e "op Address is the gate#ay IP address& for e6ample& IP9 or IP/& on

the BSC/011 side"

 OM hannel onfiguration on the Iub Interface (over IP) There are to types of routing for the 3M channel on the Iub interface! 3ne is the routing beteen the M+ and the 2ode) through the )S*.1 and the other is the routing beteen the M+ and the 2ode) not through the )S*.1!

0outing )eteen the M+ and the 2ode) Through the )S*.1 "igure # shos an e?ample of the routing beteen the M+ and the 2ode) through the )S*.1! Table # describes the routes! Figure 1 9?ample of the routing beteen the M+ and the 2ode) through the )S*.1

+#-% .%#-


& age #:, Total #1

Document

Securit Level

Title

$OT%& •

•

"igure # ta$es layer + netor$ing on the Iub interface as an e?ample! When layer : netor$ing is applied to the Iub interface, the I& interface board and the 2ode) communicate ith each other through a router! The 0I2T shon in "igure # refers to the I& interface boards of the )S*.1! "or the recommended I& interface boards of the Iub interface, see Interface )oards Applicable to Terrestrial Interfaces! Table 1 'otes !et#een the .%111 and the NodeB throgh the BSC/011

Equipment

.%111

#or$ard Route

)rom the .%111 to the NodeB

Re%erse Route

<

,. net#ork segment 70"70"70":& #ith #or$ard route address to !e the e6ternal virtal

IP address of the ,.U& that is& 7;%"7%7"750"%11

+#-% .%#-


& age #;, Total #1

Document

Securit Level

Title

Table 1 'otes !et#een the .%111 and the NodeB throgh the BSC/011

Equipment

BSC/011

#or$ard Route

Re%erse Route

)rom the ,.U to the NodeB

)rom the IP

,. net#ork segment

interface !oard

70"70"70":& #ith #or$ard route

of

address to !e the internal IP

theBSC/011 to

address of the IP interface !oard

the .%111 IP

at the BSC/011& that is&

net#ork

=1"7/="5"//

segment 7;%"7%7"750":

•

•

If layer % net#orking is applied& add a rote to the ,. IP address of the NodeB" #or$ard route address mst !e the IP address of the NodeB interface !oard" If layer 5 net#orking is applied& add a rote to the ,. IP address of the NodeB" #or$ard route address mst !e the gate#ay IP address on theBSC/011 side"

8o can configre the rote on theBSC/011 sid e" >hen yo rn this command& set E&S IP Address to the

IP address of the .%111& set Subnet mas' to the

+#-% .%#-


& age #-, Total #1

Document Title

Securit Level


Equipment

#or$ard Route

Re%erse Route

s!net mask of the .%111& and specify the vales of (&) E!ternal et$or' *irtual IP and(&) E!ternal et$or'

NodeB

&as' " In this )rom the

< +#-% .%#-


& age #., Total #1

Document

Securit Level

Title


Equipment

#or$ard Route

Re%erse Route

NodeB to the .%111 IP net#ork segment 7;%"7%7"750": •

•

If layer % net#orking is applied to the I! interface& #or$ ard route address is the IP address of the IP interface !oard at theBSC/011& that is& 7/"7/"7/"7" If layer 5 net#orking is applied to the I! interface& #or$ ard route address is the gate#ay IP address on the NodeB side"

0outing )eteen the M+ and the 2ode) 2ot Through the )S*.1

+#-% .%#-


& age #=, Total #1

Document

Securit Level

Title

If the 3M subnet here the M+ is located is connected to the I& netor$ that covers the 2ode), routes can be configured beteen the M+ and the 2ode) not through the )S*.1! "igure + shos an e?ample of routing beteen the M+ and the 2ode) not through the )S*.1! Table + describes the routes! Figure  9?ample of the routes beteen the M+ and the 2ode) not through the )S*.1

Table 2 'otes !et#een the .%111 and the NodeB not throgh the BSC/011

Equipment

.%111

#or$ard Route

)rom the .%111 to the NodeB

Re%erse Route

<

,. net#ork segment 70"70"70":& #ith #or$ard route address !eing the port IP

address of roter 7& that is& 71"7/7"%79"%11

'oter 7

)rom roter 7 to the NodeB ,.

<

net#ork segment 70"70"70":&

+#-% .%#-


& age #<, Total #1

Document Title

Securit Level

Table 2 'otes !et#een the .%111 and the NodeB not throgh the BSC/011

Equipment

#or$ard Route

Re%erse Route

#ith#or$ard route address !eing the port IP

address of roter %& that is& 7;%"7/"7/"71

'oter %

NodeB

)rom roter % to the NodeB ,.

)rom roter % to the .%111

net#ork segment 70"70"70":&

net#ork segment

#ith#or$ard route

71"7/7"%79"711& #ith #or$a

address !eing the IP address of

route address !eing the port

the IP interface !oard at the

address of roter 7& that is&

NodeB& that is& 7/"7/"7/"%

7;%"7/"7/"0

<

)rom the NodeB to the . net#ork segment 71"7/7"%79"711& #ith #or route address !eing the p

IP address of roter %& that 7/"7/"7/"%1

+#-% .%#-


& age #1, Total #1

Protocol Structure for the Iub Interface

Recommend Documents