Documente Academic
Documente Profesional
Documente Cultură
IP RAN Description
Issue
01
Date
2008-05-30
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For
any assistance, please contact our local office or company headquarters.
Website:
http://www.huawei.com
Email:
support@huawei.com
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.
RAN
IP RAN Description
Contents
Contents
1 IP RAN Change History ...........................................................................................................1-1
2 IP RAN Introduction .................................................................................................................2-1
3 IP RAN Principles......................................................................................................................3-1
3.1 IP RAN Application Scenarios......................................................................................................................3-3
3.1.1 Iub over TDM Network .......................................................................................................................3-3
3.1.2 Iub over IP Network.............................................................................................................................3-3
3.1.3 Iub over Hybrid IP Transport Network ................................................................................................3-4
3.1.4 Iub over IP/ATM Network ...................................................................................................................3-5
3.1.5 Iu/Iur over IP Network .........................................................................................................................3-6
3.2 IP RAN Protocol Stacks ................................................................................................................................3-6
3.2.1 Protocol Stack of Iub (over IP) ............................................................................................................3-7
3.2.2 Protocol Stack of Hybrid Iub (over IP /TM) ...................................................................................... 3-11
3.2.3 Protocol Stack of Iu-CS (over IP) ......................................................................................................3-14
3.2.4 Protocol Stack of Iu-PS (over IP).......................................................................................................3-15
3.2.5 Protocol Stack of Iur (over IP) ...........................................................................................................3-16
3.2.6 Protocols of Data Link Layer.............................................................................................................3-17
3.3 IP Addresses and Routes of IP RAN ...........................................................................................................3-18
3.3.1 Two Networking Types on the Iub/Iur/Iu-CS/Iu-PS Interfaces ..........................................................3-18
3.3.2 Route on the Iub/Iur/Iu-CS/Iu-PS Interface .......................................................................................3-20
3.3.3 IP Addresses for SCTP Links and IP Paths Between RNC and NodeB .............................................3-21
3.4 IP RAN QoS................................................................................................................................................3-22
3.4.2 Admission Control and Congestion Control ......................................................................................3-22
3.4.3 Differentiated Service ........................................................................................................................3-22
3.4.4 PQ and RL .........................................................................................................................................3-23
3.5 IP RAN VLAN............................................................................................................................................3-24
3.5.1 Ensuring Security...............................................................................................................................3-24
3.5.2 Providing Priority Service..................................................................................................................3-24
3.6 IP RAN FP-Mux..........................................................................................................................................3-26
3.7 IP RAN Header Compression .....................................................................................................................3-26
3.7.1 ACFC .................................................................................................................................................3-27
3.7.2 PFC ....................................................................................................................................................3-27
3.7.3 IPHC ..................................................................................................................................................3-27
Issue 01 (2008-05-30)
RAN
IP RAN Description
Contents
ii
Issue 01 (2008-05-30)
RAN
IP RAN Description
IP RAN Change History provides information on the changes between different document
versions.
RAN Version
RNC Version
NodeB Version
01 (2008-05-30)
10.0
V200R010C01B051
V100R010C01B049
V200R010C01B040
Draft (2008-03-20)
10.0
V200R010C01B050
V100R010C01B045
Feature change: refers to the change in the IP RAN feature of a specific product version.
Editorial change: refers to the change in information that was already included or the
addition of information that was not described in the previous version.
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.
Change Type
Change Description
Parameter Change
Feature change
IP transport capabilities of
DBS3900 and iDBS3900 are
added to 3.11 IP RAN
Transport Capabilities.
None
Information of NodeB
V200R010C01B040 is added
to 2 IP RAN Introduction.
None
Issue 01 (2008-05-30)
1-1
RAN
IP RAN Description
Change Type
Change Description
Parameter Change
None
Editorial
change
General documentation
change:
z
VLAN Tag
Signaling priority
None
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.
1-2
Issue 01 (2008-05-30)
RAN
IP RAN Description
Change
Type
Change Description
Parameter Change
Feature
change
Board type
Backup
Port No.
Check type
None
FPMUX flag
FPTIME
Issue 01 (2008-05-30)
Backup
Bear Type
1-3
RAN
IP RAN Description
Change
Type
Change Description
Parameter Change
Editorial
change
None
1-4
None
Issue 01 (2008-05-30)
RAN
IP RAN Description
2 IP RAN Introduction
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
PEUa
FG2a
GOUa
UOIa
POUa
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
Issue 01 (2008-05-30)
2-1
RAN
IP RAN Description
2 IP RAN Introduction
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
Board
RNC
E1/T1: 0 to 31
FG2a
FE: 0 to 7
Electrical GE: 0 to 1 (corresponding to 0 and 3 of the FE port number).
GOUa
Optical GE: 0 to 1
UOIa
POUa
E1: 0 to 125
T1: 0 to 167
NodeB
NUTI
FE: 0 to 1
E1/T1: 0 to 7
BBU
FE: 0 to 1
E1/T1: 0 to 7
WMPT
FE: 0 to 1
E1/T1: 0 to 3
UTRP
E1/T1: 0 to 7
NOTE:
BBU = Baseband Unit
PEUa: 0 to 127
POUa: 0 to 167
UOIa: 0 to 3
Impact
This feature has no impact on system performance.
z
2-2
Issue 01 (2008-05-30)
RAN
IP RAN Description
2 IP RAN Introduction
NodeB
RNC
MSC Server
MGW
SGSN
GGSN
HLR
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
Issue 01 (2008-05-30)
2-3
RAN
IP RAN Description
3 IP RAN Principles
IP RAN Principles
Describes
Issue 01 (2008-05-30)
3-1
RAN
IP RAN Description
3 IP RAN Principles
3-2
Section
Describes
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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.
Issue 01 (2008-05-30)
3-3
RAN
IP RAN Description
3 IP RAN Principles
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
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).
3-4
Issue 01 (2008-05-30)
RAN
IP RAN Description
z
3 IP RAN Principles
The hybrid transport network is flexible in terms of meeting different QoS requirements, but it
is complicated to manage.
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.
The IP interface board is connected to the IP network through the FE/GE port.
Issue 01 (2008-05-30)
3-5
RAN
IP RAN Description
3 IP RAN Principles
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
3-6
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
The data link layer can use IP over E1/T1, IP over Ethernet, IP over E1/T1 over SDH, or
IP over SDH.
Issue 01 (2008-05-30)
3-7
RAN
IP RAN Description
3 IP RAN Principles
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.
Local IP address
Peer IP address
IP path type
DSCP
Port Type
NodeB IP address
RNC IP address
Traffic Type
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.
Table 3-1 Signaling messages carried on SCTP links
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.
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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
Local IP address
Peer IP address
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.
Configuring routes between the M2000 and the NodeB not through the RNC.
Issue 01 (2008-05-30)
3-9
RAN
IP RAN Description
3 IP RAN Principles
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
3-10
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Local IP Address
Local IP Mask
Peer IP address
Peer IP Mask
Bear Type
Issue 01 (2008-05-30)
3-11
RAN
IP RAN Description
3 IP RAN Principles
z
On the IP network
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.
Adjacent node ID
AAL2 path ID
For detailed information about AAL2 path resources, see ATM Transmission Resources.
AAL2 path ID
Node Type
Path Type
3-12
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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.
Interface type
Bearing VPI
Bearing VCI
Bearing VPI
Bearing VCI
Issue 01 (2008-05-30)
3-13
RAN
IP RAN Description
3 IP RAN Principles
3-14
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Issue 01 (2008-05-30)
3-15
RAN
IP RAN Description
3 IP RAN Principles
z
The parameters for transport mode are similar to those for Iu-CS (over IP). For detailed
information, see 3.2.3 Protocol Stack of Iu-CS (over IP).
3-16
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Figure 3-12 shows the protocol stack of Iur (over IP), where:
z
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.
Issue 01 (2008-05-30)
3-17
RAN
IP RAN Description
3 IP RAN Principles
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.
Figure 3-13 MLPPP implementation
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
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
3-18
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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.
Figure 3-14 Layer 2 networking on the Iub/Iur/Iu-CS/Iu-PS interfaces
In layer 2 networking mode, the interface IP addresses of the RNC and NodeBs are in the same
network segment. A route is not necessary in this case, which makes the networking relatively
simple.
Layer 3 Networking
Figure 3-15 shows an example of layer 3 networking on the Iub/Iur/Iu-CS/Iu-PS interface.
Issue 01 (2008-05-30)
3-19
RAN
IP RAN Description
3 IP RAN Principles
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.
Route Description
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.
3-20
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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
Issue 01 (2008-05-30)
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.
3-21
RAN
IP RAN Description
3 IP RAN Principles
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.
Mechanism
Application layer
IP layer
Differentiated Service
Physical layer
Table 3-5 describes the differentiated service process. The classification and adjustment of
traffic usually happen at the network edge.
3-22
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Description
Adjusting
the service
Metering
Marking
Shaping
Dropping
The adjustment of
service ensures that the
traffic flow involving
differentiated services
complies with TCA.
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.
Table 3-6 Rules for PQs in NodeB
MSBs of the DSCP
PQ
110 or 111
101
TOP
100 or 011
MIDDLE
010 or 001
NORMAL
BOTTOM
The parameters for setting the priorities for data transmission on the NodeB side are as
follows:
z
Signaling priority
OM priority
Issue 01 (2008-05-30)
3-23
RAN
IP RAN Description
3 IP RAN Principles
3-24
One Ethernet is a private network for the real-time services of multiple NodeBs without
the influence of other customers. This Ethernet is used to carry services of high priority.
The other Ethernet is a public network for the non-real-time services of multiple NodeBs
and can be shared with other customers. The services are prone to the influence of other
customers. Thus, this Ethernet is used to carry services of low priority.
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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.
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
Issue 01 (2008-05-30)
Traffic Type
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
3-25
RAN
IP RAN Description
3 IP RAN Principles
z
Vlan Id
Vlan priority
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.
3-26
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
The RNC and the NodeB support the following three header compression methods:
z
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.
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
Issue 01 (2008-05-30)
3-27
RAN
IP RAN Description
3 IP RAN Principles
Figure 3-21 shows the single-homing layer 3 networking. The FE/GE ports on the RNC serve
the IP transport.
Figure 3-21 Single-homing layer 3 networking
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.
3-28
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
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.
Board type
Backup
When the interface board is set to the backup mode, run the ADD ETHREDPORT command
to set the backup mode of the associated ports.
The parameter involved is Port No..
For detailed information about board redundancy and port redundancy, see RNC Parts Reliability in the
RNC Product Description.
Issue 01 (2008-05-30)
3-29
RAN
IP RAN Description
3 IP RAN Principles
The ARP detection is used only when the peer equipment does not support the BFD, because the
ARP detection is unidirectional.
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.
Gateway IP address
Check type
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.
3-30
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Working in the Client/Server mode. When receiving the request from a client, the server
provides parameters such as the IP address, gateway address, DNS server address for the
client.
In the DHCP procedure, the RNC works as the DHCP server and the NodeBs work as DHCP
clients. The NodeB can automatically obtain the IP address to set up the OM channel. Figure
3-24 shows the DHCP procedure.
Figure 3-24 DHCP procedure
Issue 01 (2008-05-30)
3-31
RAN
IP RAN Description
3 IP RAN Principles
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
IP Address
----End
3-32
Item
Sub-Item
Description
Physical interfaces
Board
FE port
GE port
E1/T1
IP version
IP protocol version
IPv4
Layer 2 protocols
MAC/FE or MAC/GE
Supported
PPP/E1
Supported
PPPmux/E1
Supported
ML PPP/E1
Supported
MC PPP/E1
Supported
PPP/E1/SDH
Supported
PPPmux/E1/SDH
Supported
ML PPP/E1/SDH
Supported
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Item
Sub-Item
Description
MC PPP/E1/SDH
Supported
PPP/SDH
Supported
PPPmux/SDH
Supported
QoS
DiffServ
Supported
Header compression
IP Header Compression
over PPP (RFC 2507)
Reliability
Port backup
Supported (FG2a/GOUa/POUa/UOIa
inter-board level)
Board backup
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
Quantity/Location
Flow
Protocol
E1/T1
8 per BBU
PPP
FE
2 per BBU
MAC
IPoA client
1 per BBU
ATM
1 per BBU
Low
TCP
Traffic flow
High
UDP
Signaling flow
Medium
SCTP
IP route flow
High
IP
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).
Issue 01 (2008-05-30)
3-33
RAN
IP RAN Description
3 IP RAN Principles
Table 3-9 IP transport capabilities abilities at the BBU (DBS3900 and iDBS3900)
Item
Quantity/Location
Flow
Protocol
E1/T1
PPP
FE
MAC
IPoA client
1 per BBU
ATM
Maintenance flow on
the Iub interface
1 per BBU
Low
TCP
Traffic flow
High
UDP
Signaling flow
Medium
SCTP
IP route flow
High
IP
NOTE:
IPoA = IP over ATM, TCP = Transfer Control Protocol, UDP = User Datagram Protocol, SCTP =
Stream Control Transmission Protocol
Quantity/Location
Flow
Protocol
E1/T1
PPP
FE
MAC
IPoA client
ATM
1 per BBU
Low
TCP
Traffic flow
High
UDP
Signaling flow
Medium
SCTP
IP route flow
High
IP
3-34
Item
Quantity/Location
Flow
Protocol
E1/T1
PPP
FE
MAC
Issue 01 (2008-05-30)
RAN
IP RAN Description
3 IP RAN Principles
Item
Quantity/Location
Flow
Protocol
IPoA client
ATM
1 per BBU
Low
TCP
Traffic flow
High
UDP
Signaling flow
Medium
SCTP
IP route flow
High
IP
Issue 01 (2008-05-30)
3-35
RAN
IP RAN Description
RFC1662: PPP in HDLC-link Framing, describes the use of HDLC-like framing for PPP
encapsulated packets
RFC1990: The PPP Multilink Protocol (ML-PPP), describes a method for splitting,
recombining and sequencing datagrams across multiple logical data links
RFC3153: PPP Multiplexing (PPPmux), describes a method to reduce the PPP framing
overhead used to transport small packets over low bandwidth links.
IETF RFC 1889(01/1996): RTP: A Transport Protocol for Real Time Applications
IETF RFC 3309 (09/2002): Stream Control Transmission Protocol (SCTP) Checksum
Change
Issue 01 (2008-05-30)
4-1