Professional Documents
Culture Documents
Issue Draft A
Date 2014-01-20
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 purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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 a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview.........................................................................................................................................3
2.1 Protocol Stack.................................................................................................................................................................4
2.2 Transmission Mode Configuration.................................................................................................................................4
3 Networking.....................................................................................................................................6
4 Related Features.............................................................................................................................8
4.1 Features Related to WRFD-050403 Hybrid Iub IP Transmission..................................................................................8
5 Network Impact.............................................................................................................................9
5.1 WRFD-050403 Hybrid Iub IP Transmission..................................................................................................................9
6 Engineering Guidelines.............................................................................................................10
6.1 WRFD-050403 Hybrid Iub IP Transmission................................................................................................................10
6.1.1 When to Use Hybrid Iub IP Transmission.................................................................................................................10
6.1.2 Required Information................................................................................................................................................10
6.1.3 Planning.....................................................................................................................................................................10
6.1.4 Deployment...............................................................................................................................................................11
6.1.5 Performance Monitoring............................................................................................................................................13
6.1.6 Troubleshooting.........................................................................................................................................................14
7 Parameters.....................................................................................................................................15
8 Counters........................................................................................................................................16
9 Glossary.........................................................................................................................................17
10 Reference Documents...............................................................................................................18
1.1 Scope
This document describes WRFD-050403 Hybrid Iub IP Transmission , including its networking,
protocol stack for IP over PPP and IP over ETH, related features, network impact, and
engineering guidelines.
Before reading this document, familiarize yourself with the following documents:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
Draft A (2014-01-20)
This document is created for RAN16.0.
2 Overview
The Iub connects the RNC and the NodeB. When IP over E1/T1 and IP over FE/GE are used
over Iub, the protocol stack for IP over PPP and IP over ETH is used.
This chapter assumes that the BSC6900 is used, IP over E1/T1 and IP over FE/GE are used over
Iub, and IP over FE/GE is in non-transmission-resource-pool mode. For details about IP over
FE/GE in transmission resource pool mode, see Transmission Resource Pool in RNC Feature
Parameter Description.
Figure 2-1 Protocol stack for IP over E1/T1 and IP over ETH
When IP over E1/T1 and IP over FE/GE are used over Iub, the RNC supports IP over E1/T1, IP
over channelized STM-1/OC-3, and IP over FE/GE at the data link layer, among which IP over
FE/GE is recommended.
On the NodeB side, the BTS3900, BTS3900A, and DBS3900 support IP over E1/T1 and IP over
FE/GE at the data link layer. The protocols in the control plane, user plane, and OM plane are
the same as those when only IP transmission is used over Iub.
It is recommended that layer 3 and layer 2 networking be applied and hybrid transmission be
applied between NodeBs and routers. IP over FE/GE is used between RNCs and the U2000.
l The RNC provides only Ethernet ports, and hybrid transmission is not used on the RNC
side. Transmission configuration on the RNC side is the same as that when the Iub uses IP
transmission.
l The NodeB provides the E1/T1 port and Ethernet port. To implement hybrid IP transmission
on the NodeB side, IP over PPP is configured on the E1/T1 port and IP over ETH is
configured on the Ethernet port. Transmission configuration on the NodeB side is the same
as that when the Iub uses IP transmission.
l High- and low-priority services are carried over different IP addresses at the transport layer.
High-priority services are carried over the E1/T1 port and low-priority services are carried
over the Ethernet port. Active and standby routes are configured at the transport layer to
implement route backup between E1/T1 and Ethernet ports. For details, see section
"Ethernet Route Backup" in IP Transmission Feature Parameter Description.
For details about the protocol stack for hybrid IP transmission, see IP Transmission Feature
Parameter Description.
3 Networking
The Iub interface can be connected to two networks with different QoS standards to implement
hybrid IP transmission.
Figure 3-1 shows an example of hybrid IP transmission topology.
Services with different QoS requirements are carried over different networks.
l Low-QoS network (data network, for example, Ethernet): carries low-QoS services such
as PS interactive and background services.
l High-QoS network (TDM network, for example, PDH or SDH network): carries control
plane data, Radio Resource Control (RRC) signaling, common channel data, CS services,
and PS conversational and streaming services.
In actual networking, the NodeB can be connected to two networks through the E1/T1 port and
ETH port. The RNC, however, is connected to an external data device such as a router through
one port, and the router distributes the services to different ports and networks based on the IP
addresses.
The requirements for an external data device are as follows:
l If the NodeB is connected to an external data device through two ports and active and
standby routes are configured between the NodeB and the external data device, the external
data device must support Bidirectional Forwarding Detection (BFD) and the NodeB must
support port switchover for services when faults occur. When BFD detects a route failure,
the NodeB switches to the standby route to ensure reliability of transmission links.
l If the NodeB is connected to two external data devices through two ports, active and standby
routes can be configured between the NodeB and the external data devices and hybrid
transmission can be configured at the transport layer. If active and standby routes are
configured, heartbeat monitoring must be implemented between the two external data
devices by using, for example, Open Shortest Path First (OSPF). If hybrid transmission is
used at the transport layer, different IP paths are configured for high- and low-priority
services. High-priority services are carried over E1/T1 and low-priority services are carried
over Ethernet. Dual-homing is configured for SCTP over E1/T1 and Ethernet. Only one
OM channel is configured and is recommended to be carried over E1/T1. In the engineering
guidelines in Chapter 6, active and standby routes configuration is recommended for IP
over ETH and hybrid transmission is not recommended at the transport layer.
4 Related Features
Impacted Features
None
5 Network Impact
Network Performance
No impact.
6 Engineering Guidelines
l Physical layer data: port configuration, PPP link configuration, and VLAN configuration
of the peer equipment
l Transport layer data: IP addresses, maximum transmission units (MTUs), and differentiated
services code points (DSCPs) of the peer equipment and next-hop equipment
l Data link layer data: SCTP link configurations of the peer equipment
6.1.3 Planning
Network Planning
It is recommended that layer 3 networking should be used, the NodeB should use hybrid IP
transmission over physical layer links, and the RNC should use non-hybrid IP transmission over
physical layer links. The layer 3 equipment, such as routers, is used for hybrid transmission on
the transport network.
Hardware Planning
l The FG2a/FG2c and GOUa/GOUc of the BSC6900 support this feature.
l The following BTS3900 boards support this feature: WMPT, UMPT, UTRP2, UTRP4,
UTRP9, and UTRPc.
l The BSC6910, BTS3902E, and BTS3803E do not support this feature.
6.1.4 Deployment
Process
For details about the deployment process on the RNC side, see IP RAN Engineering Guide
Feature Parameter Description.
Figure 6-1 shows the deployment of hybrid Iub IP transmission on the NodeB side.
Requirements
l Other Features
This feature depends on the WRFD-050402 IP Transmission Introduction on Iub Interface
feature.
l License
The license control item IUB Hybrid IP Transportation Function has been activated on the
RNC side. For details about the license control items and how to activate the license, see
License Management Feature Parameter Description. The following table lists the license
information for this feature.
l Others
-The RNC and NodeB must support IP transmission.
-The control plane of the IP-based Iub interface and the corresponding data on the physical
equipment have been configured.
Data Preparation
For data preparation on the RNC side, see section "Data Preparation for Initial Configuration"
in BSC6900 UMTS Initial Configuration Guide (MML-Based).
For data preparation on the NodeB side, see section "NodeB Transport Data" in 3900 Series
Base Station Initial Configuration Guide.
Initial Configuration
l For details about activation using MML commands on the RNC side, see Configuring the
Interfaces > Configuring the Iub Interface (over IP) in BSC6900 UMTS Initial
Configuration Guide (MML-Based). For details about activation using the CME on the
RNC side, see Configuring BSC6900 Data (General Configuration) > Configuring
Interface Data in BSC6900 UMTS Initial Configuration Guide (CME-Based).
l For details about activation on the NodeB side, see 3900 Series Base Station Initial
Configuration Guide (CME-Based) > Creating Base Stations > Creating NodeBs >
Creating a Single NodeB > Configuring NodeB Transport Data > Configuring IP
Transport Data on the NodeB Side (Non-secure Networking) in 3900 Series Base
Station Initial Configuration Guide.
Activation Observation
For details about activation observation on the RNC side, see IP Transmission Feature
Parameter Description
Step 1 Run the NodeB MML command DSP ETHPORT to check the ETH port status of the NodeB.
Step 2 Run the NodeB MML command DSP PPPLNK to check the status of PPP link over E1 of the
NodeB.
Step 3 Start MAC Message Statistics and PPP Message Statistics tasks on the NodeB LMT. If there
are messages traced, services are carried over the Ethernet port and E1/T1 port.
----End
Table 6-1 describes the counters related to hybrid Iub IP transmission on the NodeB side.
Table 6-1 Counters related to hybrid Iub IP transmission on the NodeB side
Reconfiguration
For detailed operations, see RAN Reconfiguration Guide.
Deactivation
This feature does not need to be deactivated.
6.1.6 Troubleshooting
For details about troubleshooting on the RNC side, see section "Troubleshooting IP
Transmission Faults" in RAN Troubleshooting Guide. For details about alarm handling
procedures on the RNC side, see section "Transport Alarm" in BSC6900 UMTS Alarm
Reference.
7 Parameters
8 Counters
9 Glossary
10 Reference Documents