Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
IP RAN Description
Issue 01
Date 2008-05-30
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
IP RAN Change History provides information on the changes between different document
versions.
01 (2008-05-30)
This is the document for the first commercial release of RAN10.0.
Compared with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-30) of RAN10.0
incorporates the changes described in the following table.
Draft (2008-03-20)
This is a draft of the document for the first commercial release of RAN10.0.
Compared with issue 03 (2008-01-20) of RAN 6.1, this issue incorporates the changes
described in the following table.
Feature The port backup mode is changed in The following parameters are deleted:
change 1.3.8 IP RAN Redundancy. z Slot 14 interface board type
z14 interface board Backup type
The following parameters are added:
z Board type
z Backup
z Port No.
The fault detection is added in 1.3.8 The following parameters are added:
IP RAN Redundancy. z Check type
z Port work mode
z Min interval of BFD packet send
[ms]
z Min interval of BFD packet
receive [ms]
z Times of out-time of BFD packet
z ARP packet out-time
z ARP packet resend times
The IP interface boards POUa and None
UOIa are added in 1.2.1 IP RAN
Introduction.
IP RAN FP-Mux is added in 1.3.6 IP The following parameters are added:
RAN FP-Mux. z FPMUX flag
z Max subframe length
z Mux package length
z FPTIME
The configuration on the RNC side is The following parameter is deleted:
changed in 1.3.9 IP RAN Load z14 interface board Backup type
Sharing.
The following parameter is added:
z Backup
In Protocol Stack of Iub (over IP), the The following parameter is deleted:
NCP/CCP Bearing Type parameter zNCP/CCP Bearing Type
in the ADD IUBCP command is
renamed as Bear Type. The SET The following parameter is added:
OMCH (BTS3812E, BTS3812AE, z Bear Type
BBU3806, BBU3806C) command is
changed to ADD OMCH
(BTS3812E, BTS3812AE,
BBU3806, BBU3806C).
2 IP RAN Introduction
The IP Radio Access Network (RAN) feature enables IP transport on the Iub, Iur, and Iu
interfaces. This makes it possible for the operators to use their existing IP networks in a larger
and more flexible capacity. In this way, network deployment costs are reduced.
The most widely used data communication networks are based on IP transport. Apart from
being more economical than the Asynchronous Transfer Mode (ATM) network, the IP
networks offer multiple access modes and provide enough transmission bandwidth for high
speed data services, such as High Speed Downlink Packet Access (HSDPA).
IP Interface Boards
To implement the IP RAN feature, the RNC and the NodeB must be configured with the
related IP interface boards. The IP interface boards are as follows:
z IP interface boards for the RNC
PEUa
FG2a
GOUa
UOIa
POUa
z IP interface board for the NodeB
The DBS3800 of earlier versions provides Fast Ethernet (FE) ports.
Therefore, no hardware change is necessary.
The BTS3812E and the BTS3812AE require the Universal Transport Interface Unit
(NUTI) board.
The NUTI board provides eight E1/T1 ports and two FE ports.
The WMPT board provides 4 E1/T1 ports and 2 FE ports, the UTRP board provides 8
E1/T1 ports.
Numbering Schemes
Numbering schemes are used for this feature for FE, GE and E1/T1 ports of the NodeB and
the RNC, and for the RNC Point-to-Point Protocol (PPP) links.
Numbering Scheme for FE, GE and E1/T1 Ports
Table 2-1 describes the numbering scheme for the FE, GE, and E1/T1 ports on the NodeB and
the RNC.
Table 2-1 Numbering scheme for the FE, GE and E1/T1 ports on the NodeB and the RNC
E1/T1: 0 to 3
UTRP E1/T1: 0 to 7
NOTE:
BBU = Baseband Unit
Impact
z Impact on System Performance
This feature has no impact on system performance.
z Impact on Other Features
This feature has no impact on other features.
NOTE:
z : not involved
z : involved
UE = User Equipment, RNC = Radio Network Controller, MSC = Mobile Service Switching Center,
MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support
Node, HLR = Home Location Register
3 IP RAN Principles
Section Describes
3.1 IP RAN Application The IP RAN application scenarios consist of Iub over
Scenarios Time Division Multiplexing (TDM) network, Iub over IP
network, Iub over hybrid IP transport network, Iub over
IP/ATM network, and Iu/Iur over IP network.
3.2 IP RAN Protocol Stacks This section describes the IP-based protocol stacks on the
Iub, Iu-CS, Iu-PS, and Iur interfaces, protocol stack of
hybrid Iub (over IP/ATM), and the IP-based protocol
stacks at the data link layer.
3.3 IP Addresses and Routes This section describes the IP addresses and routes that are
of IP RAN required for running an IP RAN network.
3.4 IP RAN QoS The assurance mechanisms of QoS are implemented at
the application layer, IP layer, data link layer, and
physical layer
3.5 IP RAN VLAN Virtual Local Area Network (VLAN) enhances the IP
transport security. Besides, VLAN provides the priority
service and isolates different users
3.6 IP RAN FP-Mux Frame Protocol Multiplexing (FP-Mux) encapsulates
multiple small FP PDU frames (also called subframes)
into a UDP package, thus improving the transport
efficiency. FP-Mux is only applicable to the user plane
data on the Iub interface based on UDP/IP.
3.7 IP RAN Header Header compression is used to reduce protocol header
Compression overhead of point-to-point links and to improve
bandwidth efficiency.
Section Describes
In the TDM networking mode, the RNC uses the PEUa and POUa as the Iub interface boards.
The RNC and NodeBs support IP over E1/T1, which is based on Plesiochronous Digital
Hierarchy (PDH) or Synchronous Digital Hierarchy (SDH).
The TDM network ensures the reliability, security, and QoS of the Iub interface data
transmission, but the costs of E1 transport are relatively high.
In the IP networking mode, the FG2a or GOUa board of the RNC serves as the Iub interface
board and supports board backup, FE/GE port backup, or FE/GE port load sharing.
The IP network can be any of the following types:
z Layer 2 network, for example, metropolitan area Ethernet and VPLS
z Layer 3 network, for example, IP/MPLS/VPN
z Multi-Service Transmission Platform (MSTP) network
In this networking mode, the PEUa/POUa and FG2a/GOUa boards of the RNC serve as the
Iub interface boards and support FG2a/GOUa board backup, FE/GE port backup, or FE/GE
port load sharing. The POUa supports the board with Multiplex Section Protection (MSP)
backup mode, and port wih MSP backup mode.
In Hybrid IP transport, services with different QoS requirements can be transmitted in
different paths. The two paths from the RNC to the NodeB are connected to two different
networks through different ports, or through the same port that is connected to the external
data equipment according to Differentiated Service Code Point (DSCP).
The ATM/IP networking mode allows hybrid transport of services with different QoS
requirements. High QoS services, such as voice services, streaming services, and signaling,
are transmitted on the ATM network. Low QoS services, such as PS Best Effort (BE) services,
are transmitted on the IP network.
The ATM and IP interface boards of the RNC must be configured to support this networking
mode. The ATM interface board can be the AEUa, AOUa, or UOIa. The IP interface board can
be the FG2a, GOUa, UOIa, POUa, or PEUa.
z The ATM interface board is connected to the ATM network through the E1/T1 or STM-1
port.
z The IP interface board is connected to the IP network through the FE/GE port.
The NodeB is connected to the ATM/IP networks through the ATM and IP interface boards
respectively.
In the ATM/IP network, the ATM network ensures the QoS, while the IP network reduces the
transmission costs and fulfills the requirement of high-speed data services for high bandwidth
on the Iub interface. On the other hand, the ATM/IP network requires the maintenance of both
the ATM and the IP networks; thus the maintenance is more complex and expensive.
In this networking mode, the FG2a, GOUa, or UOIa board of the RNC serves as the Iu or Iur
interface board and supports board backup, FE/GE port backup, or FE/GE port load sharing.
The IP network can be any of the following three types:
z Layer 2 network, for example, metropolitan area Ethernet and VPLS
z Layer 3 network, for example, IP/MPLS VPN
z Multi-Service Transmission Platform (MSTP) network
IP Path
An IP path is a group of connections between the RNC and the NodeB. An Iub interface has at
least one IP path. It is recommended that more than one IP path be planned.
SCTP Link
An SCTP link carries signaling messages on the Iub interface. The signaling messages carried
on the SCTP link are classified into NCP and CCP, as described in Table 3-1.
Type Description
NCP An 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.
NOTE:
NCP = NodeB Control Port, CCP = Communication Control Port
The Signalling link model parameter of an SCTP link can be SERVER or CLIENT.
In Iub IP transport, the Signalling link model parameter has to be set to SERVER when you
configure an SCTP link on the RNC side.
The parameters for establishing an SCTP link on the RNC side are as follows:
z Signalling link model
z First local IP address
z Second local IP address
z First destination IP address
z Second destination IP address
z Local SCTP port No.
z Destination SCTP port No.
The second local IP address and the second peer IP address must be configured together.
OM Channel
OM channel is used to maintain and configure the NodeB remotely. There are two methods to
configure routes for the OM channel on the Iub interface:
z Configuring routes between the M2000 and the NodeB through the RNC.
z Configuring routes between the M2000 and the NodeB not through the RNC.
Figure 3-7 shows an example of configuring routes between the M2000 and the NodeB
through the RNC.
Figure 3-7 Example of configuring routes between the M2000 and the NodeB through the RNC
Figure 3-7 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 through a router.
If the OM subnet where the M2000 is located is connected to the IP network that covers the
NodeB, the routes can be configured between the M2000 and the NodeB not through the RNC.
Figure 3-8 shows an example of configuring routes between the M2000 and the NodeB not
through the RNC.
Figure 3-8 Example of configuring routes between the M2000 and the NodeB not through the
RNC
IP Path and SCTP Link Configuration on the RNC and NodeB Sides
The parameters for IP path and SCTP link on the RNC and NodeB sides are similar to those
for Iub (over IP). For detailed information, see 3.2.1 Protocol Stack of Iub (over IP).
AAL2 Path
An AAL2 path is a group of connections between the RNC and the NodeB. An Iub interface
has at least one AAL2 path. It is recommended 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 RNC and the NodeB.
Table 3-2 The type of the signaling messages carried on the SAAL links
Type Description
NCP An NCP carries common process messages of NBAP over the Iub interface. The
Iub interface has only one NCP.
CCP A CCP carries dedicated process messages of NBAP over the Iub interface. The
Iub interface may have multiple CCPs. The number of CCPs depends on
network planning.
ALCAP The ALCAP is also called Q.AAL2. Typically, the 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 RNC and the NodeB.
Figure 3-12 shows the protocol stack of Iur (over IP), where:
z The control plane data is carried on the SCTP link.
z The user plane data is carried on the IP path.
Ethernet
Ethernet is a standard that was jointly released by Digital Equipment Corp., Intel Corp., and
Xerox in 1982. It is the most widely used Local Area Network (LAN) technology based on
TCP/IP and CSMA/CD access method.
The MAC addressing scheme of Ethernet helps to resolve the addressing problem of entities
within the Ethernet. Each MAC address has 48 bits and the addresses are assigned worldwide
under the same rule.
The earliest Ethernet packet encapsulation format complies with Ethernet 802.3 defined by
IEEE and the most common format now is Ethernet II specified by RFC0826. The NodeB and
the RNC can transmit frames in Ethernet II format and receive frames in Ethernet 802.3 and
Ethernet II formats.
PPP/MLPPP
The PPP provides standard methods for encapsulating the multi-protocol datagrams on
point-to-point links. These datagrams consist of IP, IPX, and Apple Talk.
MLPPP (MP) is used to combine multiple physical links into a logical link. Therefore, it
provides a relatively high bandwidth and facilitates quick data transfer. MLPPP
implementation is shown in Figure 3-13.
MCPPP
MCPPP (MC) is an extension of the MLPPP protocol and provides more priorities. Packets
with a higher priority can interrupt the transmission of those with a lower priority. The MC
protocol is implemented in compliance with RFC2686.
The bits, responsible for marking the priority of a packet, in the MLPPP header are not used
in the MLPPP protocol. These bits are the two bits after the E flag bit in the short sequence, or
the four bits after the E flag bit in the long sequence. Packets at each priority level have their
own MLPPP mechanism, for example, independent sequence number and reassembly queue.
z The parameter on the RNC side is MLPPP type.
z The parameter on the NodeB side is MCPPP.
PPPMux
PPPMux encapsulates multiple PPP frames (also called subframes) in a single PPPMux frame.
The subframes in the PPPMux frame are distinguished by delimiters. PPPMux reduces PPP
overhead per packet and improves bandwidth efficiency. PPPMux is implemented in
compliance with RFC3153.
z The parameter on the RNC side is PPP mux.
z The parameter on the NodeB side is PPP MuxCP.
Layer 2 Networking
Compared with layer 3 networking, layer 2 networking is simpler. That is because the port IP
addresses of the RNC, NodeB, and neighboring RNC, MGW and SGSN are located in the
same network segment and no route is required.
Figure 3-14 shows an example of layer 2 networking on the Iub/Iur/Iu-CS/Iu-PS interfaces.
Layer 3 Networking
Figure 3-15 shows an example of layer 3 networking on the Iub/Iur/Iu-CS/Iu-PS interface.
z IP 1 and IP 2 are device IP addresses of the IP interface board. One interface board supports a
maximum of five device IP addresses. The device IP addresses configured on the same interface
board cannot be located in the same subnet.
z IP 3 and IP 4 are port IP addresses of the IP interface board.
z IP 5 and IP 6 are gateway IP addresses on the RNC side.
z IP 7 is the gateway IP address on the NodeB/neighboring RNC/MGW/SGSN side.
z IP 8 is the IP address of the NodeB/neighboring RNC/MGW/SGSN.
IP interface board The route travels from the RNC to the network segment where the
NodeB/neighboring RNC/MGW/SGSN is located.
You can run the ADD IPRT command on the RNC to configure the
route. Destination IP address is the address of the network segment
where the NodeB/neighboring RNC/MGW/SGSN is located, and Next
hop IP address, for example, IP 5 or IP 6, is the gateway IP address
on the RNC side.
Figure 3-16 IP addresses for SCTP links and IP paths between RNC and NodeB
IP1-0 and IP2-0: IP addresses for SCTP links on the NodeB side
IP1-1 and IP2-1: IP addresses for SCTP links on the RNC side
IP3-0: IP address for the IP paths on the NodeB side
IP3-1: IP address for the IP paths on the RNC side
Figure 3-16 shows two interconnected BBUs on the NodeB side as an example. When two
BBUs are interconnected through the EIa ports, the two BBUs are regarded as one NodeB on
the RNC side. On the NodeB side, BBU1, which is connected to the transport network
between RNC and NodeB, is an active BBU, while BBU2 is a standby BBU. The IP addresses
of the NodeB for communicating with the RNC are configured only on BBU1. The data of the
Iub interface is sent or received through the FE/E1 ports of BBU1, as shown in Figure 3-16.
You can specify the active BBU and standby BBU by setting the Dual-In-line Package (DIP) switch. For
detailed information about the DIP switch, see DIP Switch on the BBU3806 or DIP Switch on the
BBU3806C in the DBS3800 Hardware Description.
z IP1-0 and IP 2-0 are configured as the first local IP address and the second local IP
address respectively for the SCTP links on the NodeB side. IP1-1 and IP2-1 are
configured accordingly on the RNC side. The first local IP address and the second local
IP address cannot be the same. When the first local IP address for the SCTP links is
unavailable, the data on the SCTP links is transmitted through the second local IP
address.
When the layer 2 or TDM networking is applied, IP1-0, IP1-1, IP2-0, and IP2-1 are
the IP addresses of the port (FE/GE/PPP/MLPPP). IP1-0 and IP1-1 are within the
same network segment, and the same is true for IP2-0 and IP2-1.
When the layer 3 networking is applied, IP1-0 and IP2-0 are the IP addresses of the
FE ports, and IP1-1 and IP2-1 are the device IP addresses. IP1-0 and IP1-1 do not
stay within the same network segment, and the same is true for IP2-0 and IP2-1.
z IP paths between RNC and NodeB do not work in backup mode.
When the layer 2 or TDM networking is applied, IP3-0 and IP3-1 are IP addresses of
the port (FE/PPP/MLPPP). IP3-0 and IP3-1 are within the same network segment.
When the layer 3 networking is applied, IP3-0 is IP address of the FE port and IP3-1
is the device IP address. IP3-0 and IP3-1 do not stay within the same network
segment.
Layer Mechanism
Table 3-5 describes the differentiated service process. The classification and adjustment of
traffic usually happen at the network edge.
Operation Description
Classifying the service Traffic classification enables different types of services that are
implemented by setting different values.
Adjusting Metering The data rate is metered and the The adjustment of
the service subsequent shaping and scheduling service ensures that the
are based on the metering. traffic flow involving
differentiated services
Marking The packets are marked with complies with TCA.
different colors according to Traffic
Conditioning Agreement (TCA).
Shaping The packets in the traffic flow are
delayed as required by the service
model.
Dropping Non-TCA-supportive packets are
dropped.
3.4.3 PQ and RL
The principles of PQ and RL are considered together. The PQs are configured automatically in
the NodeB. When the actual bandwidth exceeds the specified bandwidth, the system buffers
the congested data or discards it to ensure a specified bandwidth at the physical port. When
the physical port is congested, the system discards the message with lower priority according
to the PQ principle.
Table 3-6 describes the rules for PQs based on the three Most Significant Bits (MSBs) of the
DSCP.
110 or 111 The urgent queue is used by default. No manual configuration of the
PQ is necessary.
101 TOP
100 or 011 MIDDLE
010 or 001 NORMAL
0 BOTTOM
The parameters for setting the priorities for data transmission on the NodeB side are as
follows:
z Signaling priority
z OM priority
The VLANID Flag parameter indicates whether VLAN is enabled or not. The NodeB and the
RNC identify the service QoS through Vlan priority in the VLAN tag. Each NodeB or the
RNC provides an Ethernet port to connect to the MSTP network. The MSTP transmits the
Ethernet data to either of the VC trunks according to Vlan priority in the VLAN tag. Each
VC trunk supports up to two QoS classes. In the same VC trunk, the data of different NodeBs
is identified by different VLAN ID parameters.
The VLAN tag contains a 2-byte Tag Protocol Identifier (TPID) and a 2-byte Tag Control
Information (TCI).
z TPID is defined by the IEEE and is used to indicate that the frame is attached with an
802.1Q tag. VLAN TPID has a fixed value 0x8100.
z TCI contains the frame control information and consists of the following items:
Priority: a 3-bit field that indicates the frame priority. The eight values, from 0 to 7,
represent eight priorities. The priority field is defined in the IEEE 802.1Q protocol.
Canonical Format Indicator (CFI): a 1-bit field. The value 0 indicates the canonical
format and 1 indicates the non-canonical format. CFI specifies the bit sequence of the
address contained in the encapsulated frame in the token ring or source route FDDI
media access method.
VLAN Identifier (VLAN ID): a 12-bit field that indicates the VLAN ID. It represents
4096 IDs. The frame, which complies with 802.1Q, contains this field and indicates
which VLAN the frame belongs to.
The NodeB attaches VLAN tags to the frames that are sent from the Ethernet port, but does
not attach VLAN tags to the frames that are received from the Ethernet port.
When the NodeB supports the VLAN, it attaches diverse tags to different traffic flows to
enable the traffic flow transmission in different VLAN channels.
The parameters on the NodeB side are as follows:
z Traffic Type
On the RNC side, the NodeB detection function can be started through the MML command STR
NODEBDETECT in order to periodically send the VLAN IDs to the NodeBs. By this means, when a
new NodeB is set up or a NodeB recovers from the fault, the NodeB can automatically obtain its VLAN
ID from the RNC.
To enable FP-Mux, the FPMUX flag parameter has to be set to YES. Max subframe length
indicates the maximum length of the subframe. Maximum Frame Length indicates the
maximum length of the frame of the FP-Mux UPD/IP package. The UDP package frame is
sent out once the time set by FPTIME expires.
FP-Mux is applicable to frames with the same priority, that is, frames of the same DSCP value.
The RNC and the NodeB support the following three header compression methods:
z Address and Control Field Compression (ACFC)
z Protocol Field Compression (PFC)
z IP Header Compression (IPHC)
3.7.1 ACFC
ACFC, which complies with RFC 1661, is used to compress the address and control fields of
PPP protocol. These fields usually contain constant values for PPP links. It is unnecessary to
transport the whole fields every time. If ACFC passes the negotiation during the PPP Link
Control Protocol (LCP), the address and control fields (0xFF03) of subsequent packets can be
compressed.
3.7.2 PFC
PFC, which complies with RFC 1661, is used to compress the protocol field of PPP. PFC can
compress the 2-byte protocol field into a 1-byte one.
The compression complies with the ISO3309 extension mechanism, that is, a binary 0 in the
Least Significant Bit (LSB) indicates that the protocol field contains two bytes, and the other
byte follows this byte. And a binary 1 in the LSB indicates that the protocol field contains one
byte, and this byte is the last one. The majority of packets are compressible, because the
protocol fields assigned are usually less than 256.
3.7.3 IPHC
IPHC, which complies with RFC 2507 and RFC 3544, is used to compress the IP/UDP header
of PPP links. IPHC improves bandwidth efficiency in the following two ways:
z The unchanged header fields in packet (IP/UDP) headers are not carried by each packet.
z The header fields that vary with specified modes are replaced with fewer bits.
The header context is established on both ends of a link when packets with complete headers
are sent occasionally. Thus the compressed packets can retrieve their original headers
according to the context and the changed fields.
z The parameter on the RNC side is Head compress.
z The parameter on the NodeB side is IP Head compress.
Figure 3-21 shows the single-homing layer 3 networking. The FE/GE ports on the RNC serve
the IP transport.
In this networking mode, the FE/GE ports of the RNC are configured for backup. The active
and standby FE/GE ports of the RNC are connected to the Provider Edge (PE), which are
further connected to the IP network. The active and standby FE/GE ports of the RNC share
one IP address, IP 1-0. The PE configures the active and standby ports of the RNC in one
VLAN and uses one interface IP address of the VLAN, IP 1-1.
The GE optical ports on the GOUa board are applicable when the RNC is far away from the PE, and the
FE/GE electrical ports on the FG2a board are applicable when the distance between the RNC and the PE
is within 100 m.
In this networking mode, the FE/GE ports of the RNC are configured for backup. The active
and standby FE/GE ports of the RNC are connected to two PEs, which are further connected
to the IP network. Complying with the Virtual Router Redundancy Protocol (VRRP), the two
PEs provide redundancy-based protection for the data transmitted from the RNC. One PE
connects to the other through two GE ports. Link Aggregation (LAG) is applied to the
interconnection links between the PEs to increase the bandwidth and reliability of the links.
The active and standby FE/GE ports of the RNC share one IP address, IP 1-0. The PEs
configure the active and standby ports of the RNC in one VLAN and use one virtual VRRP IP
address, IP 1-1.
The GE optical ports on the GOUa board are applicable when the RNC is far away from the PE, and the
FE/GE electrical ports on the FG2a board are applicable when the distance between the RNC and the PE
is within 100 m.
For detailed information about board redundancy and port redundancy, see RNC Parts Reliability in the
RNC Product Description.
z The ARP detection is used only when the peer equipment does not support the BFD, because the
ARP detection is unidirectional.
z The ARP message is a broadcast message; therefore, if there is a relatively large L2 broadcast
domain between the RNC and the L3 equipment, a broadcast storm may easily occur. But if the
RNC and the L3 equipment are directly connected, a broadcast storm never occurs.
In this scenario, the FG2a or GOUa board of the RNC serves as the interface board, and
supports board backup and FE/GE port apart.
The two FE/GE ports on the active and standby boards are configured with IP addresses of
different network segments, IP 1-0 and IP 2-0. The PE configures the corresponding IP
addresses, IP 1-1 and IP 2-1. The data to the destination IP address is shared by the two routes.
The load sharing ports on the RNC can be connected to one PE or two different PEs.
For details about board redundancy, port redundancy, and port load sharing, refer to RNC Parts
Reliability in the RNC Product Description
Step 2 DHCP offer: The RNC sends the configuration information such as IP addresses to the NodeB
through DHCPOFFER packets.
Step 3 DHCP selection: The NodeB selects an IP address from the DHCPOFFER packets and then
responds by broadcasting DHCPREQUEST packets.
Step 4 DHCP acknowledgement: The RNC responds by sending DHCPACK packets to the NodeB.
The parameters on the RNC side are as follows:
z The First Serial Number
z The Second Serial Number
z IP Address
----End
MC PPP/E1/SDH Supported
PPP/SDH Supported
PPPmux/SDH Supported
QoS DiffServ Supported
Header compression IP Header Compression Supported (on E1)
over PPP (RFC 2507)
Reliability Port backup Supported (FG2a/GOUa/POUa/UOIa
inter-board level)
Board backup Supported (all the interface boards)
NOTE:
RBS = RNC Business Subrack, RSS = RNC Switch Subrack, IPv4 = Internet Protocol version 4, MAC =
Media Access Control, PPPMux = PPP Multiplexing, ML PPP = Multi-Link PPP, MC PPP = Multi-Class
PPP, SDH = Synchronous Digital Hierarchy, QoS = Quality of Service, DiffServ = Differentiated
Services
NOTE:
IPoA = IP over ATM, TCP = Transfer Control Protocol, UDP = User Datagram Protocol, SCTP = Stream
Control Transmission Protocol
Table 3-9 describes the IP transport capabilities at the BBU (DBS3900 and iDBS3900).
Table 3-9 IP transport capabilities abilities at the BBU (DBS3900 and iDBS3900)
NOTE:
IPoA = IP over ATM, TCP = Transfer Control Protocol, UDP = User Datagram Protocol, SCTP =
Stream Control Transmission Protocol