Introduction To The BSC6900 V900R014 Feature Transmission Resource Pool in RNC BSC

INTERNAL
Introduction to the
Feature–Transmission
Resource Pool in
RNC/BSC
www.huawei.com
by Chen Yanyan and Guo Chengxu
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

About This Training
 This course describes Iub/Iu/Iur/A Transmission Resource
Pool in RNC/BSC, which is a new feature in BSC6900
V900R014.
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved. Page 2
References
 Some of the sources this course references are as follows:
 RAN Feature Documentation: IP Transport Architecture
 RAN Feature Documentation: IP RAN
 RAN Feature Documentation: Transmission Resource Management
 RAN Feature Documentation: Transmission Resource Pool in

RNC/BSC
 CME Operation Guide to RAN14.0 Transmission Resource Pool in

RNC/BSC
 ROSA-RC V100R012C00 Transmission Resource Pool in RNC/BSC

Requirement Analysis and Feature Design Description
Training Objects
 After learning this course, you are supposed to:
 Understand the value and application scenario of the feature

Transmission Resource Pool in RNC/BSC.
 Understand the feature specifications.
 Explain basic principles of the feature.
 Be able to activate and verify the feature according to the

manual.
Contents
1. Background
2. Feature Introduction
3. Networking Schemes
4. Related Features
5. Feature Deployment
6. O&M
Background: Iu/A Interface
 The following figure shows the major solution to IP transmission networking over the Iub
interface in versions earlier than RAN14.0.
Router1 MGW POOL
GOUc/FG2 IPPATH
c
DIP DIP DIP
Subrack 1
IP1
VRRP
xGSN POOL
Subrack 0
IP2
DIP DIP DIP
Active Backup
Router2
• This solution has the following drawbacks:
 The configuration of IP paths is complex. An IP path is configured for each pair of source/destination IP addresses.
 User-plane IP addresses are added on the peer network element (NEs). Calls may be rejected because the
configuration data of some IP paths and IP routes is missing on the local RNC/BSC.
 The utilization of transmission resources is low. The GOUc/FG2c boards and GE ports work in 1+1 active/standby
mode.
 The multi-board load balancing effect is poor. Load balancing depends on configuration of IP paths for each board
and the condition of traffic balancing among subracks.
• Major objectives of the solution:
• 1. No configuration needs to be made on the local RNC/BSC when IP addresses are added on peer NEs.
• 2. Load is shared among all boards and all ports on the boards.
Background: Iub Interface
 The following figure shows the major solution to IP transmission networking over the Iub interface
in versions earlier than RAN14.0.
Router1 NodeBs
IPPATH
GOUc/FG2c DIP
DIP
Subrack 1 DIP
IP1
VRRP
NodeBs
Subrack 0
IP2 DIP
DIP
Active Backup
DIP
Router2
• This solution has the following drawbacks:
 The utilization of transmission resources is low. The GOUc/FG2c boards and GE ports work in 1+1 active/standby mode.
 IP addresses of NodeBs and RNCs are bound using IP paths. Dynamic load balancing is not supported for traffic over
the Iub interface.
 It is complex to expand GE ports or interface boards on the RNC side because NodeBs must be rehomed to the newly-
added ports and interface boards.
 Configuration of IP paths is complex. Call setup fails if the IP path type mapping the transmission resource mapping
table (TRMMAP) is not configured or the IP path configuration on the NodeB is inconsistent with that on the RNC.
• Major objectives of the solution:
• 1. Configuration of IP paths and rehoming of NodeBs are not required.
• 2. Load is shared among all boards and all ports on the boards.
Contents
1. Background
4. Related Features
6. O&M
Introduction to the Transmission Pool
IPPOOL
Application scenario:
IP3 IP6 IP13 IP16
MGW
MGW  Layer 3 (L3) Ethernet
Subrack 2 IP xxx MGW
Iub Iub Iu Iu  Supported RNC hardware:
GOUc/FG2c and
NodeBs IP2 IP5 IP12 IP15
GOUd/FG2d
MGW
SGSN/
MGW
IP xxx
Subrack 1 Iub Iub Iu Iu GGSN  Supported NodeB: BTS3900
series or BTS3902E series
IP1 IP4 IP11 IP14  Supported interfaces: Iub, Iur,
MGW
Subrack 0 IP xxx MGW
RNC IuCS, IuPS, and A interfaces
Iub Iub Iu Iu
• A transmission resource pool is formed by multiple interface boards on the RNC/BSC side in L3 Ethernet
networking. The IP addresses for these boards form an IP address pool. Any peer NE, for example, a
NodeB, NRNC, MGW, SGSN, or GGSN, can be connected to any interface board in the transmission
resource pool. When a call needs to be set up, the RNC/BSC selects an IP address from the IP address
pool for the call in a way that ensures load balancing.
• Iub, Iu-CS, Iu-PS, and Iur interface boards on the RNC side can each form a transmission resource pool.
• A-interface boards on the BSC side can form a transmission resource pool.
Introduction–Principle of Load Balancing for the
Iu/Iur/A Interface
 Objectives:
 1. Transmission ports and interface boards are shared within the entire RNC/BSC.
 2. Congestion does not occur between subracks because of SCU interconnection.
 Overview:
 During service setup, an appropriate SIP address is selected from the IP address pool based on the SIP load distribution
proportion.
 The SIP load distribution proportion is determined as follows:
 Initial proportion: The load is distributed evenly to each SIP address in the IP address pool. For example, if the IP address pool has
two SIP address, the load of each SIP address is 50%.
 Load distribution proportion adjustment algorithm:
 1. The load distribution proportion of each SIP address is calculated periodically (every 5 seconds).
 2. Triggering condition: Maximum load of a SIP address – Minimum load of a SIP address > INTLOADDIFFTH (10%)
 3. Action: Transfer 1% of load from the SIP address with the highest load to the SIP address with the lowest load.
 The load of a SIP address (SIP load) is defined as follows:
 MAX(SIP egress load, Inter-subrack load + Number of cross-subrack hops x 5% + INTSRLOADCOMPENSATETH(10%))
 The SIP load includes the inter-subrack load. Loads of SIP addresses in the IP address pool are different because the source
subracks are different.
 Each subrack maintains the SIP load distribution proportion independently. During service setup, the RNC/BSC first selects the user-
plane board serving the UE/MS and then selects an SIP address. The RNC/BSC balances the load based on the SIP load distribution
proportion of the selected SIP address by using the subrack that houses the user-plane board as the source subrack.
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved. Page10
Introduction- Calculation of the Inter-Subrack Load
SCUs in the
main subrack
The figure on the left shows the SCUb
interconnection between subracks.
SCUs in the
extended subrack This figure assumes that:
1#  Subrack 2 houses the user-plane
3#
board serving the UE/MS that
5#
40％ accesses the network.
20％ 10％
 The SIP address is configured in
subrack 3.
2#
4#
 The number of cross-subrack
hops is 3.
10％
 The maximum inter-subrack
30％
load is 40%.
Introduction-Iu/Iur/A Load Balancing
The inter-subrack load The inter-subrack load
is light. is heavy.
IPPOOL IPPOOL
D When the inter-subrack load
increases, the load distributed across
D
P 50% subracks decreases.
P 100%
SIP1 SIP1
U 50% U 0%
The load is not balanced among SIP
D 50% addresses due to the unbalanced load on
the user plane of each subrack. As a
D 0%
P 50% SIP2
result, the load distributed across subracks
increases.
P 100% SIP2
U U
 For calls processed by subracks (DPU as the source subrack), the proportion of calls distributed to each SIP address is
adjusted to balance the load among interface boards and maintain a low inter-subrack load.
 The following types of inter-subrack load is not affected by load balancing among the Iu/Iur/A interface boards:
 Inter-subrack traffic generated by the Iub/Abis interface
 When data is migrated from PCH to DCH/HSPA, the SIP address of the Iu-PS interface remains unchanged but a
DPU is reselected. The inter-subrack load is not considered when a DPU is reselected.
 Cross-subrack communication inside the system
Introduction-Principle of Iub Load Balancing
 Initial binding: Each NodeB is bound to an initial IP address.
 Based on the bandwidth configured for the adjacent node corresponding to the NodeB,
the load is evenly distributed to the SIP addresses of the local subrack or the subrack
closest to the local subrack.
 Initial binding is triggered in any of the following situations:

 The ADD IPPOOLIP or RMV IPPOOLIP command is run to add IP addresses to or remove IP
addresses from an IP address pool.
 The status of the outbound port using a SIP address changes, for example, when an Ethernet
port used as the outbound port is deactivated.
 The ADD ADJNODE or RMV ADJNODE command is run to add or remove adjacent nodes.
 The load of the initially bound SIP address is distributed to and balanced among
non-initially bound SIP addresses if the following condition is met:
 Initially bound SIP load (considering the inter-subrack load) > INTLOADSHARETH
 Load balancing algorithm for balancing the load of the bound SIP address:
 Same as that of the Iu/A interface
Introduction–Impact of Packet Loss Rate on
Load Balancing
 Packet loss rate detection and isolation
 Ping packets are sent periodically to detect the packet loss rate.
 The RNC/BSC collects statistics on the packet loss rate and round trip time (RTT)
for ping packets sent from local IP addresses.
 The RNC/BSC refreshes and records the packet loss rate every 90 seconds. The
packet loss rate is regarded as the average of the latest five values.
 If the packet loss rate exceeds 5% for ping packets sent from a local IP address in
the transmission resource pool to every IP address on the peer end, the ALM-
21394 Transmission Resource Pool IP Packet Loss alarm is reported. When
selecting an IP address for a call from the IP address pool, the RNC/BSC attempts
to avoid IP addresses with high packet loss rates. Assume the IP address with the
lowest packet loss rate is SIP1 and the packet loss rate for an IP address is higher
than that for SIP1 by INTPINGLOSTPKTPRITH. In this case, the RNC/BSC does
not select this IP address, unless the other IP addresses in the IP address pool are
faulty or heavily loaded.
Page 14
Introduction–Principles of the IP Path
Configuration Free
 Non-transmission pool: The RNC/NodeB manages IP addresses based on the connection orientation
principle. IP paths must be configured to define IP transmission resources of the Iub, Iur, Iu, and A
interfaces. During service setup, the RNC selects an IP path from the configured IP paths to carry the
current service. An IP path is selected only when the destination IP address of the call matches the
destination IP address of the IP path and the priority of the TRMMAP matches the priority of the IP path.
 Transmission pool: Based on the hop-by-hop and connectionless nature of the IP address, IP paths are
not configured on the RNC. On the RNC/NodeB, only the service IP address pool used by the local
RNC/NodeB is configured. During service setup, an appropriate IP address is selected from the IP
address pool to carry the current service.
 Exchange of the service-specific bearer information: the transmission layer information (such as the IP
address and UDP port) used by the service is exchanged by using the radio layer signaling. This
process does not involve the transmission pool.
CRNC Node B
RADIO LINK SET UP REQUEST(containing the IP address and UPD port of the RNC)
RADIO LINK SET UP RESP ONSE(containing the IP address and UPD port of the NodeB)
Introduction–Prerequisites for IP Path
Configuration Free
 IP Path Configuration Free requires that the IP route between the RNC/BSC and a
peer NE side be reachable. In this way, selection of an IP address on the RNC/BSC
is independent of the IP address used on the peer NE.
√ RNC/BSC
× Peer NE
RNC/BSC Peer NE
E1/T1 link or dedicated

Ethernet connection
IP1_1 IP1_2 IP1_1 IP1_2
MPLS/IP network
E1/T1 link or dedicated

Ethernet conneciton
IP2_1 IP2_2 IP2_1 IP2_2
Introduction–Principle of Source-Based
Routing
 Objective of source-based routing: The route configuration on the local RNC/BSC does not need to be adjusted when IP
addresses are added or modified on a peer NE.
 Principle of source-based routing: The RNC/BSC only needs to send IP packets to a router and the router forwards the packets
based on the destination IP address.
 Description of source-based routing: (1) The ADD SRCIPRT command is run to add a source IP route on the RNC/BSC. The
source IP address (DEVIP, ETHIP, or ETHTRKIP) is associated with the next-hop gateway. (2) When sending an IP packet, the
interface board searches the source IP routing table based on the source IP address of the IP packet to obtain the next-hop
gateway. (3) The source-based route has a higher priority than the destination-based route.
 Source-based routing is applicable to the scenario where the primary and secondary gateways are configured.
Primary Secondary Description

Gateway Gateway
20.20.20.2 20.20.20.1 Null Configure the source IP route of the Ethernet port IP
address (ETHIP) first.
10.10.10.1 20.20.20.1 Null Configure the source IP route of the device IP

address (DEVIP).
RNC Router Peer NE

Peer
IP1 10.10.20.1
Peer
20.20.20.2 10.10.30.1
DEVIP IP Network IP2
20.20.20.1
10.10.10.1 Peer
IPn
Contents
1. Background
4. Related Features
6. O&M
Introduction–Networking Scheme 1
Typical deployment scenario: The operator is sensitive to the utilization of transmission
resources but not sensitive to call drops caused by a faulty board.
Individual interface boards form a
transmission resource pool.
GOUc ROUTER
• Four individual GOUc boards form a transmission
IP:10.10.1.1/30
resource pool. Each board is configured with a device IP1
IP:10.10.1.2/30
IP address as its service IP address. Services are
distributed among the four service IP addresses. To
prevent call drops caused by a faulty port, it is IP:10.10.1.5/30
IP2
recommended that two or more ports on an interface IP:10.10.1.10/30
board be aggregated into a trunk.

Benefits DIP
IP:10.10.1.9/30
• The maximum payload throughput and session IP3
IP:10.10.1.6/30
setup/release times of an interface board are doubled.
• Interface boards can be evenly distributed among the
IP:10.10.1.13/30
RNC/BSC subracks.
IP4
IP:10.10.1.14/30
• Capacity expansion can be performed on a single
board.
• The advantages of the interface board pool are provided.
Typical deployment scenario: The customer is sensitive to call drops caused by a faulty board.
Active/Standby interface boards form a

transmission resource pool. GOUc ROUTER
• Multiple pairs of GOUc boards working in active/standby mode IP:10.10.1.1/30
IP1
IP:10.10.1.2/30
Active
form a transmission resource pool.
• All GE ports on the active and standby boards are active ports.
• Multiple GE ports on an interface board are configured in a
IP:10.10.1.5/30
trunk group. IP2
Standby
IP:10.10.1.10/30
• Each DEVIP is configured with the primary and secondary
gateways of the source-based route.
• On the router, a primary route and a secondary route to each DIP
IP:10.10.1.9/30
DEVIP are configured. IP3
Active
Benefits IP:10.10.1.6/30
• The reliability is high. During switchover, CS calls are not

dropped and the time during which the PS throughput drops to 0 IP:10.10.1.13/30
IP4
Standby
is short. IP:10.10.1.14/30
• If the transmission resource pool is originally not configured and

GOUc boards work in active/standby mode, it is easy to deploy
networking scheme 2.
Typical reconfiguration scenario: Active/Standby interface boards with active/standby
Ethernet ports form a transmission resource pool.
Active/Standby interface boards with active/standby Ethernet
ports form a transmission resource pool.
IPPOOL
• Multiple pairs of GOUc boards working in active/standby mode
form a transmission resource pool. Port1
Active
GE ports on the active and standby boards work in
IP1
active/standby mode and are connected to routers using
VRRP1
Virtual Router Redundancy Protocol (VRRP). Router
Port2 1
• Multiple pairs of active/standby ports are configured on an
Standby
interface board. Each pair of active/standby ports is configured
with a DEVIP. DEVIPs of all interface boards form a service IP IP
Peer NE
address pool. Net work
• Reconfiguration on peer routers is not needed. VRRP IP2 Port3
Active
configuration is the same as that in the scenario where a VRRP
2
transmission resource pool is not configured.
Router
Benefits Standby 2
• The reliability is high. During switchover, CS calls are not Port4
dropped and the time during which the PS throughput drops to
0 is short.
• It is simple to use networking scheme 3 on an existing VRRP
network. Reconfiguration on peer routers is not needed.
Iub/Iu interface boards forming one or two
transmission resource pools.
• Like the scenario where the IP address is shared by the Iub
and Iu interfaces on an IPRAN, interface boards of the RNC
form a transmission resource pool that can be shared by the
IPPOOL
Iub and Iu interfaces. This networking scheme is applicable
IP3 IP6
to all the three scenarios described earlier. MGW
MGW
2# IP xxxMGW
• This networking scheme is specific to propaganda to to build
the brand of Huawei. It is not recommended or deployed.
Benefits NodeB IP2 IP5

• The resource usage of interface boards is high.
MGW
SGSN/
MGW
1# IP xxx
• The advantages of the interface board pool are provided. GGSN
It is recommended that the Iub interface and Iu/Iur interface use IP1 IP4
MGW
two transmission resource pools respectively formed by two
0# IP xxx MGW
RNC
groups of interface boards, based on the following two
considerations:
• The IP backhaul network should be separated from the IP
backbone network.
• Transmission capacity expansion for the Iub interface and the
Iu/Iur interface should be independent from each other.
Contents
1. Background
4. Related Features
6. O&M
Introduction to the Iub Transmission
Resource Pool–Related Features
 Required features
 This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub

Interface.
 Mutually exclusive features
This feature is mutually exclusive to the following features:
 WRFD-021305 RAN Sharing Phase 2
 WRFD-02130501 Dedicated Iub Transmission Control
 WRFD-050420 FP MUX for IP Transmission
 WRFD-050422 Dynamic Bandwidth Control of Iub IP
 WRFD-050403 Hybrid Iub IP Transmission
 Affected features
 WRFD-050408 Overbooking on IP Transmission
 WRFD-020101 Admission Control
Introduction to the Iu/Iur Transmission
Resource Pool–Related Features
Iu/Iur Transmission Resource Pool in RNC
 Required features
 WRFD-050409 IP Transmission Introduction on Iu Interface
 WRFD-050410 IP Transmission Introduction on Iur Interface
 Mutually exclusive features
 WRFD-050412 UDP MUX for Iu-CS Transmission
 The transmission resource pool of RAN14.0 does not support the IPMUX function.
Transmission Resource Pool for A Interface
 This feature is an enhanced version of the feature GBFD-118602 A over IP.
 This feature and the feature GBFD-118610 UDP MUX for A Transmission are mutually
exclusive.
Introduction–Impacts
 Impact on radio equipment:
 Impact on the RNC: The feature simplifies the configuration and maintenance of the transport layer. To expand
the capacity of the IuB interface boards on the RNC, NodeBs do not need to be rehomed based on the load
changes of interface boards. When user-plane IP addresses are added or adjusted on the core network and
RNC, no configuration change is needed on the RNC. Status of load balancing among interface boards and
ports on the RNC may change. Inter-subrack traffic may change as well
 Impact on the NodeB: The feature simplifies the configuration and maintenance of the transport layer of the Iub
interface. Configuration of IP paths is not needed.
 Impact on network equipment:

Customer edge (CE) routers connected to the RNC must be reconfigured to support the RNC pool.
 Pool formed by active/standby interface boards (individual ports): The primary and secondary static routes are
configured. In addition, these routes have different priorities and are imported to Open Shortest Path First
(OSPF) areas.
 Pool formed by individual interface boards: Two routers can be independent of each other. OSPF is deployed
between routers.
 Pool formed by active/standby interface boards (active/standby ports): Original configurations (such as VRRP
and route configuration) on routers are retained after the pool is configured.
 Impact on networking: All routes between IP addresses in the transmission resource pool and IP addresses of a peer
NE are reachable.
Contents
1. Background
4. Related Features
5. Feature Deployment and Network Reconfiguration
6. O&M
When to Use the Feature and Information
to Be Collected
Before deploying the feature Transmission Resource Pool in RNC/BSC, collect the
following information:
 Iu/Iur Transmission Resource Pool in RNC
 The GOUc or FG2c boards are used as the Iu/Iur interface boards.
 The Iu/Iur interface adopts L3 networking, that is, all routes between the RNC and a
peer NE are reachable.
 Iub Transmission Resource Pool in RNC

 The GOUc or FG2c boards are used as the Iub interface boards.
 The BTS3900 series and BTS3902E are supported. The BTS3800 series does not
support the transmission resource pool on the Iub interface.
 The Iu/Iur interface adopts L3 networking, that is, all IP routes between the RNC and
NodeBs are reachable.
Feature Activation Planning–
Version/License Planning
• Version requirement:
• BSC6900: BSC6900 V900R014C01 or later
• M2000: iManager M2000-II V200R012C00 or later
• CME: WRAN CME V200R012 or later
• NodeB: V100R014C00 or later
• License control:
• WRFD-140207 Iu/Iur Transmission Resource Pool in RNC
• WRFD-140208 Iub Transmission Resource Pool in RNC
Introduction–Application Scenario and Feature Gain
Scenario Description Gain
Scenario 1: IP-based The RNC is connected to aL3 router. All DEVIP routes between the router and the RNC 1. Improved reliability
L3 networking are reachable. 2. Simple deployment
The feature Transmission Resource Pool in RNC is recommended. 3. High transmission resource
utilization
Scenario 2: IP-based The Iub interface adopts end-to-end layer 2 networking. The Iub bearer network uses None
L2 networking the MSTP/PTN Ethernet dedicated lines. The feature Transmission Resource Pool in
RNC is NOT recommended.
Scenario 3: PPP/MP- The Iub interface adopts end-to-end Point-to-Point Protocol/Multilink Protocol (PPP/MP) None
based networking networking.
The feature Transmission Resource Pool in RNC is NOT recommended.
Scenario 4：IP-based Real-time services are transmitted over PPP/MP, and non-real-time services are None
separated transmitted over the Ethernet network.
transmission The feature Transmission Resource Pool in RNC is NOT recommended.
Scenario 5: ATM&IP Real-time services are transmitted over ATM, and non-real-time IP services are 1. Improved reliability
dual-stack transmitted over the Ethernet network. The Ethernet ports form a transmission pool. 2. Simple deployment
transmission The feature Transmission Resource Pool in RNC is recommended. 3. High transmission utilization
Scenario 6: On a RANSharing or MOCN network, if the transmission resource pool is used, 1. Improved reliability
RANSharing separated transmission between carriers is not supported. 2. Simple deployment
3. High transmission utilization
Scenario 7: MBTS When the GSM, UMTS, and LTE base stations share the transmission resources, only 1. Improved reliability
networking the UMTS NodeBs support configuration of the transmission resource pool on the RNC. 2. Simple deployment
3. High transmission utilization
Networking Solution–Deployment
Networking scheme for a newly
deployed network
 It is strongly recommended that the
feature Transmission Resource Pool in
Lower cost
RNC/BSC be sold to a newly deployed Higher Customer’s and easier
site. On an MSC pool –enabled network, it reliability requirements to maintain
is strongly recommended that the feature
Iu/Iur Transmission Resource Pool in RNC
be sold as well.
 Suggestions for selecting a transmission
resource pool networking scheme for each Candidate solution 1: Ports of Recommended solution: Ports of
interface: If the customer is sensitive to routers share the load. The interface routers share the load. The
boards of the RNC/BSC form the interface boards of the
reliability and requires that ongoing calls
transmission resource pool. The RNC/BSC form the transmission
are not dropped when an interface board
interface boards work in resource pool. The interface
is faulty, use interface boards that work in active/standby mode. All ports on boards work independently.
active/standby mode to form the pool. interface boards are active ports. SIP Ports on an interface board are
Otherwise, use individual interface boards addresses are configured with the aggregated to share the load.
to form the pool. primary and secondary gateways.
Ports on an interface board are
aggregated to share the load.
Network Planning for the Iu/Iur/A
Transmission Resource Pool
• Network planning
 User plane:
1. The Iu-CS, Iu-PS and Iur interfaces are deployed on different interface boards. (The IP address pool is not shared.)
2. The Iu-CS, Iu-PS and Iur interfaces are deployed on the same interface board but use different physical ports. (The
IP address pool is not shared.)
3. The Iu-CS, Iu-PS and Iur interfaces are deployed on the same interface boards and use the same physical port, but
do not share an IP address. (The IP address pool is not shared.)
4. The Iu-CS, Iu-PS and Iur interfaces are deployed on the same interface board and use the same physical port and
IP address. (The IP address pool is shared.)
 Signaling plane: The control-plane IP addresses can be the same as the user-plane IP addresses or can be
logical IP addresses. On the Iu-CS interface, the user plane and control plane often use different IP addresses,
VLANs, or physical ports, On the Iu-PS or Iur interface, physical port isolation between the control plane and
the user plane is of little significance.
 The A interface cannot share the IP address pool with the Iu/Iur interface, but they can share interface boards
and physical ports.
• Hardware planning
 The RNC/BSC uses the GOUc or FG2c as the interface board.
 The Iu/Iur/A interface boards, Iub interface boards, user-plane boards, and control-plane boards are evenly
distributed among the RNC/BSC subracks.
Existing Networking Schemes of the Iu/Iur/A Interface
and Network Reconfiguration Solutions
Networking scheme 1: Active/standby interface boards, active/standby Network Reconfiguration
ports + VRRP Solution
RAN BACKBONE IP5
CE
Control-plane VPN
Recommended solution:
IP1&IP2
Active/standby interface
VRRP1&2
VIP: IP1'&IP2' IP core MSC SVR boards with active/standby
IP6 ports form an interface
board pool.
User-plane VPN
BSC/RNC CE
MGW Candidate solution:

Individual interface boards
form an interface board
Networking scheme 2: Active/standby interface boards, active ports pool.
(primary and secondary routes)
RAN BACKBONE IP5
CE
Control-plane VPN Recommended solution:
IP1'&IP2'
Active/standby interface
IP1&IP2
boards with individual ports
IP core MSC SVR
pool.
IP6
IP3&IP4
IP3'&IP4' User-plane VPN
BSC/RNC CE
MGW
Network Planning for the Iub
Transmission Resource Pool
Networking planning
 Networking solution to Iub transmission resource pool: If a customer has a high requirement for the
network reliability, use the interface boards that work in active/standby mode to form a transmission
resource pool. In this way, a fault on an interface board does not result in call drops. If the network
reliability requirements are not high, use individual interface boards to form a transmission resource
pool.
 Signaling plane: For NCP/CCP signaling over the Iub interface, it is recommended that one SCTP
link be bound to the IP addresses of two interface boards in the transmission resource pool on the
RNC/BSC side to improve the reliability. In this way, a faulty interface board does not result in the
failure of the NodeB.
 It is recommended that the Iub interface do not share interface boards with the Iu/Iur interface. All
Iub interface boards form a resource pool. All NodeBs share an Iub interface resource pool.
 It is recommended that the Iub O&M signaling be not routed to the RNC.
Hardware planning
 The RNC uses the GOUc or FG2c as the interface board.
 The Iu/Iur interface boards, Iub interface boards, user-plane boards, and control-plane boards are
evenly distributed among the RNC subracks
 The NodeB must be a BTS3900 series base station or BTS3902E.
Existing Networking Schemes of the Iub
Interface and Network Reconfiguration
Solutions
 Networking scheme 1: Iub L3 networking
BSC/RNC site Recommended solution:
Active/standby Active/standby interface
interface boards; CE DEV IP boards with individual ports
primary/secondary IP1'
IP11 form an interface board
routes BTS/NodeB IP1 pool.
IP backhaul IP2
IP2’
BTS/NodeB
BSC/RNC
CE Candidate solution:
BTS/NodeB Individual interface boards
pool.
Active/standby
CE BSC/RNC site
ports + VRRP
BTS/NodeB Recommended solution:
IP1
VRRP Active/standby interface
IP backhaul VIP: IP1' boards with active/standby
ports form an interface
BTS/NodeB board pool.
BSC/RNC
CE
BTS/NodeB
Existing Networking Schemes of the Iub Interface
 Networking scheme 2: Iub L2 networking
Interconnection BSC/RNC site
using the LAG

Network BTS/NodeB
LAG
reconfiguration is
not supported.
IP backhaul
BTS/NodeB LSW
BSC/RNC
BTS/NodeB
Interconnecti
on using the
L2 switch LSW
BTS/NodeB Active
Network
reconfiguration is IP backhaul
not supported. Standby
BTS/NodeB LSW BSC/RNC

L2 switch
BTS/NodeB
Existing Networking Schemes of the Iub Interface and
Network Reconfiguration Solutions
 Networking scheme 3: Iub IP over E1 networking
CE
E1 TDM/SDH GE
NodeB backhaul
Network
RNC
reconfiguration is not CE STM-1
supported.
E1 TDM/SDH
NodeB
backhaul
 Networking schemes 4 and 5: IP-based separated transmission and ATM&IP dual-

stack transmission over Iub
• The transmission resource pool
CE cannot be configured for either IP
over E1 or IP over ETH.
GE
IP backhaul
FE
STM-1 RNC
CE • For ATM over E1 and IP over ETH
E1
NodeB dual stacks, the IP address pool
TDM/SDH can be configured only for the IP
network part.
backhaul
Existing Networking Schemes of the Iub Interface
 Networking scheme 6: Iub RANSharing networking
Operator A BSC/RNC site
CE
NodeB Operator B Operators can share
IP1
the Iub interface.
IP backhaul
BSC/RNC
CE
 Networking scheme 7: MBTS networking

Only the UMTS
UMTS BSC/RNC site
CE NodeBs support
BTS/NodeB GSM configuration of the
IP1
IP backhaul transmission resource
pool on the RNC
BTS/NodeB
BSC/RNC
CE
BTS/NodeB
Solutions to Configuration of an Iub Transmission
Resource Pool for a Live Network
Existing Networking Scheme Recommended Solution Candidate Solution
L3 networking: The GOUc/FG2c The GOUc/FG2c boards still work in active/standby mode. The individual GOUc boards form
boards work in active/standby mode. 1. Active/standby ports + VRRP: Active/standby interface a transmission resource pool.
boards with active/standby ports form a transmission The operator is not sensitive to call
resource pool. drops and agrees to change the
2. Individual ports + primary/secondary routes: configurations of the bearer
Active/standby interface boards with individual ports form a network.
transmission resource board pool. Advantage: The cost is low.
Advantage: The network reliability is high. After the pool is
configured, reconfiguration of the bearer network is not
needed.
L3 networking: The GOUc/FG2c The individual GOUc boards form a transmission resource pool.
boards work independently.
L3 networking: The GOUa/FG2a The feature Transmission Resource Pool in RNC is not supported.
boards are used.
L2 networking: EPL or EPLAN The feature Transmission Resource Pool in RNC is not supported.
networking
End-to-end TDM networking The feature Transmission Resource Pool in RNC is not supported.
ATM/IP dual-stack networking Only the IP transmission part supports the feature Transmission Resource Pool in RNC. (L3/L2
networking)
G/U dual-mode co-transmission Currently, the GSM does not support the interface board pool. Therefore, different configuration
networking policies must be used for the GSM and UMTS networks in order to configure the pool. Solution 2
that uses individual interface boards to form the pool is not recommended because reliability
protection measures are not adopted on the BSC.
Deployment–Overall Procedure
Deployment scenario Network reconfiguration scenario:
Networking planning Networking planning

CME data preparation CME data preparation
Information collection Information collection
Hardware preparation Deployment Data configuration Feature activation
Data configuration Feature activation
Deployment–Requirements
 Deployment requirements
 To deploy the feature Iu/Iur Transmission Resource Pool in RNC, licenses for
the following features must be available:
 WRFD-050409 IP Transmission Introduction on Iu Interface
 WRFD-050410 IP Transmission Introduction on Iur Interface
 WRFD-050402 IP Transmission Introduction on Iub Interface
 WRFD-140207 Iu/Iur Transmission Resource Pool in RNC
 WRFD-140208 Iub Transmission Resource Pool in RNC
 Version requirement
RAN14.0 or later
 Transport network requirement

 L3 networking is used and the adjacent L3 devices (such as routers) of the RNC
support link aggregation.
 All routes from a peer NE to the interface boards in the transmission resource pool of
the RNC are reachable.
 Data preparation
 Plan the transmission resource pool on the RNC, establish an IP address pool,
and then add IP addresses to the IP address pool.
 On the NodeB side, prepare the service IP addresses used to connect the
NodeB to the IP address pool of the RNC.
POOL POOL IP
POOL ID
Name IP1 IP2 IP3 … Ipn
0 Iub POOL 10.10.1.1 10.10.1.2 10.10.1.3 10.10.1.n
 Hardware installation
 RNC hardware requirement: The GOUc/FG2c board is used as the interface
board.
 NodeB hardware requirement: a BTS3900 series base station or BTS3902E
 Precautions
 Logical ports are not supported on the RNC side. The Iub interface does not support scheduling
and shaping. The HSDPA adaptive flow control algorithm is used on the Iub interface. The
bandwidth-based admission control is performed only on real-time services.
 IP paths cannot be configured on NodeBs that are added to the transmission resource pool on
the RNC side.
 After the source-based routes are configured, the source-based routes take precedence over the
destination-based routes.
 The same operator cannot configure both IP paths and the IP address pool for the Iu interface.
 The transmission resource pool is applicable only to the Ethernet L3 networking scenario.
 When the transmission resource pool is configured, the RANSharing Phase 1 (operators’
transmission not separated) is supported, but RANSharing Phase 2 (operators’ user plane and
admission separated) and RANSharing Phase 3 (operators’ user plane not separated but
admission separated) are not supported.
 The IPMUX function is not supported.
 If the trunk is used as the outbound port in the transmission resource pool, all the member ports
of the trunk must be located on the same physical interface board. If active and standby trunks
are configured, only the manual aggregation mode is supported.
 Specifications
 An RNC/BSC supports a maximum of 16 transmission resource pools.
 An IP address pool can contain a maximum of 24 IP addresses.
 The total number of IP addresses in all IP address pools cannot exceed 128.
Deployment of the Iub Transmission Resource
Pool in RNC–Requirements
 Activation
The following provides key MML commands for configuring an IP address pool. Other transmission configurations (such as the physical ports
and VLANs) are the same as those in the scenario where the pool is not configured. For details, see the Initial Configuration Guide.
RNC basic physical configuration RNC control plane RNC user plane NodeB configuration
Run the ADD DEVIP

Run the SET ETHPORT command Run the ADD SCTPLNK Run the ADD SERV
command to add a
to set properties of Ethernet ports. command to add two IP command to add an
device IP address and
SCTP links. service IP address.
run the ADD SRCIPRT
command to specify the
source IP route.
Optional: Run the ADD
Run the ADD UNCP Run the ADD IPRT
ETHREDPORT command to
command to add an NCP. Run the ADD IPPOOL command to add a
add active/standby Ethernet
command to add an IP route.
ports.
address pool.
Run the ADD UCCP Run the ADD

Run the ADD Link aggregation: Run the ADD IPPOOLIP SCTPLNK command
command to add a CCP
ETHIP command Run the ADD ETHTRK command to add user- to add an SCTP link.
link.
to add IP command to add an plane IP address (IP1 to
addresses for LAG. Run the ADD IPn) to the IP address
Ethernet ports. ETHTRKLNK pool.
commands to add links Run the SET
to the LAG. Run the HSDPAFLOWCTRLPARA
ADD ETHTRKIP command to turn on the
Run the ADD ADJNODE
command to add IP DYNAMIC_BW_SHAPING
command to add an
address for the LAG. switch (dynamic traffic shaping).
adjacent node and run
the ADD ADJMAP
command to map the
adjacent node to the IP
address pool.
Deployment of the Iu/Iur/A Transmission
Resource Pool in RNC–Requirements
 Activation
Except the control plane configuration, other configurations are the same as those made for deployment of the Iub transmission
resource pool in RNC. Control plane User plane
Basic physical configuration Run the ADD SCTPLNK command to Run the ADD DEVIP
add multiple SCTP links. command to add a
device IP address and
Run the SET ETHPORT command run the ADD SRCIPRT
to set properties of Ethernet ports. command to specify the
Run the ADD M3LKS command to add source IP route.
an M3UA link set.
Optional: Run the ADD Run the ADD IPPOOL

ETHREDPORT command to command to add an IP
add active/standby Ethernet address pool.
ports. Run the ADD M3RT command to add an
M3UA route.
Run the ADD IPPOOLIP
command to add user-
Run the ADD ETHIP Link aggregation: plane IP address (IP1 to
command to add IP Run the ADD ETHTRK Run the ADD M3LNK command to add IPn) to the IP address
addresses for Ethernet command to add an an M3UA link. pool.
ports. LAG. Run the ADD
ETHTRKLNK
commands to add links
Run the ADD UCNDOMAIN command to
to the LAG. Run the Run the ADD ADJNODE
add the CN domain.
ADD ETHTRKIP command to add an
command to add IP adjacent node and run the
address for the LAG. ADD ADJMAP
Run the ADD UCNNODE to add a CN command to map the
node. adjacent node to the IP
address pool.
Deployment of the Iub Transmission
Resource Pool in RNC–CME
Requirements for using the CME for network reconfiguration
 Objective: The customer service engineers can use the CME tool to configure a transmission resource pool for
a live network that does not have the pool.
 Scenario constraints
 The CME is not applicable to network reconfiguration in the scenario where the interface boards of the
RNC cannot be used to form a transmission resource pool.
 The CME is not applicable to network reconfiguration in the ATM&IP dual-stack networking scenario.
 If new configurations are added to NodeBs during network reconfiguration, the CME cannot be used for
network reconfiguration. For example, if it is required that VLAN configuration be added after network
reconfiguration, the reconfiguration cannot be completed at a time.
Configuring an Iub Transmission Resource
Pool on a Newly Deployed Network–CME
 To configure an Iub transmission resource pool on a newly deployed network, perform the
following steps:
Step 1. In the Main View navigation tree, right-click NodeB and choose NodeB Configuration Express.
Step 2. Click a node under IP Transport.
 Step 3 (GUI-based configuration): In the Main View navigation tree, right-click NodeB and choose IP
Transport Layer.
 Step 3 (batch configuration): Prepare the Iub interface data and add the RNC planning data and NodeB
planning data to the Iub negotiation template of the CME.
 Step 4 (GUI-based configuration): Click Export Incremental Scripts. The
incremental script is an incremental MML script for an RNC and an incremental
XML file for a NodeB. The script is sent to the related NE.
 Step 4 (batch configuration): Choose UMTS Application > Import Data > Import
Iub Interface Data.
Iub Interface Data.
Configuring an Iu Transmission Resource
To configure an Iu transmission resource pool on a newly deployed network, perform
the following steps:
 Step 1. In the Transmission View navigation tree, choose UMTS > IuPS (or IuCS,
or Iur). An interface navigation tree is displayed.
 Step 2. Click a node under IP Transport.
 Step 3 (GUI-based configuration): Click Export Incremental Scripts to obtain the
MML scripts for the RNC and then send the script to the BAM.
 Step 3 (batch configuration): Prepare the IuPS/IuCS/Iur interface data and add the
planning data to the IuIur negotiation template of the CME.
IuIur Interface Data.
 Step 5 (batch configuration): Choose Data Management > Export Incremental

Scripts to obtain the scripts for the RNC and sends the scripts to the RNC.
Configuring an Iub Transmission
Resource Pool on a Live Network–CME
To configure an Iub transmission resource pool on a newly deployed network, perform the following steps:
Step 1. In the Main View navigation tree, right-click NodeB and choose NodeB Configuration Express.
Step 2. Click a node under IP Transport.
Configuring an Iub Transmission
Resource Pool on a Live Network–CME
 Step3. Choose UMTS Application > RNC Pool Configuration.
 Step4. Select the NodeBs related to the transmission resource pool and
click Next.
Feature Deployment–Activation
Observation
 Activation observation
 Transmission over the Iu/Iub interface is a fundamental part of
a service flow. If various services (for example, CS, PS,
HSDPA, and HSUPA services) can be completed properly, a
transmission resource pool has been configured for the Iu/Iub
interface.
 If the inter-RNC handovers are successful on the UMTS

network, a transmission resource pool has been configured for
the Iur interface.
Feature Deployment–Capacity Expansion
A transmission resource pool can be expanded in either of the following methods:
 Adding a physical port: The transmission resource pool has sufficient interface boards but insufficient physical ports.
 Adding an interface board: The transmission resource pool has insufficient interface boards.
Adding a Physical Port
The following steps assume that each interface board has a GE port and these ports has been aggregated into an LAG:
1. Run the SET ETHPORT command to add a GE port to each interface board. Connect the GE port to the router.
2. Add the new GE port to the LAG for each interface board.
 On the RNC/BSC side, run the ADD ETHTRKLNK command to add the new GE port to the LAG.
 On the router side, add a sublink to the LAG that is connected to the RNC/BSC.
Adding an Interface Board
The following steps assume that individual interface boards have formed a transmission resource pool and an interface board is
to be added:
1. Configure a trunk group and add the Ethernet ports of interface boards to the trunk group.
2. Configure an IP address for the trunk group.
3. Configure an device IP addresses.
4. Configure a source IP routes.
5. Add the device IP address to the IP address pool.
6. Configure routes to the new IP addresses on routers and peer NEs.
Contents
1. Background
4. Related Features
5. Feature Deployment and Network Reconfiguration
6. O&M
O&M–Performance Monitoring
The load of each interface board in the transmission resource pool must be monitored to
determine whether it is necessary to expand the capacity of the pool.
 Monitoring of the CPU usage of an interface board: If the CPU usage is lower than the peak value 70% and
the average CPU usage is lower than 50%, the capacity is sufficient. Otherwise, the capacity of interface
boards must be expanded.
 Monitoring of the utilization of interface boards: If the forwarding ratio of an interface board is greater than
70%, it is recommended that the capacity of interface boards be expanded.
 Maximum Forwarding Ratio of Interface Boards (VS.INT.TRANSLOAD.RATIO.MAX)
 Average Forwarding Ratio of Interface Boards (VS.INT.TRANSLOAD.RATIO.MEAN)
 Monitoring of MAC throughput on ports of interface boards: If the proportion of the MAC throughput on
Ethernet ports exceeds 60%, it is recommended that the capacity of Ethernet ports be expanded.
 Mean Receive Rate of the FEGE Ethernet Port (VS.FEGE.RXMEANSPEED)
 Highest Receive Rate of the FEGE Ethernet Port (VS.FEGE.RXMAXSPEED)
 The following counters are used to monitor load balancing over the Ethernet ports in the transmission
resource pool:
 Mean Receive Rate of the FEGE Ethernet Port (VS.FEGE.RXMEANSPEED)
 Highest Receive Rate of the FEGE Ethernet Port (VS.FEGE.RXMAXSPEED)
 Mean Transmit Rate of the FEGE Ethernet Port (VS.FEGE.TXMEANSPEED)
 Highest Transmit Rate of the FEGE Ethernet Port (VS.FEGE.TXMAXSPEED)
O&M–Real-Time Performance Monitoring
Newly added
performance
monitoring on the
transmission
resource pool
Real-time performance monitoring

 Monitor the traffic of the local IP addresses in the IP address pool: Select IPPOOL LOCAL IP from the Monitor
Item drop-down list box, and specify Subrack No., Slot No., Local IP Address. All the three parameters are
mandatory.
 Monitor the IP PM of the IP address pool: Select IPPOOL PM from the Monitor Item drop-down list box, and
specify Adjacent Node ID, Local IP Address, Peer IP Address, and Priority. All the four parameters are
mandatory.
Page 60
O&M–Summary
Alarm Counter Fault Location Real-Time Performance
Monitoring
• ALM-21392 Adjacent • Number of active • Manually bind a • Real-time performance

Node IP Address Ping connections of an NodeB to an IP monitoring of IP traffic
Failure adjacent node address in the • IP PM real-time
• ALM-21393 Adjacent • Bandwidth allocated transmission performance
Node IP Path Ping to an adjacent node resource pool. monitoring
Failure • Congestion status of • Specify the source
• ALM-21394 an adjacent node IP address to trace
Transmission signaling of a single
• Ping test results of an subscriber.
Resource Pool IP adjacent node
Packet Loss
• Traffic of an adjacent
• ALM-21603 Adjacent node
Node Congestion
• SIP traffic
• ALM-21602 IP In IP
Address Pool Blocked
O&M–Customized Parameters and
Counters
MML commands and counters on the RNC side
MML commands on the NodeB side: ADD/RMV/LST/MOD SERVIP
Parameter Value Default Value Description

SERVTYP IUB–0 0 Service IP
address type
IP IPv4 N/A IP address
Terms
 LAG: Link Aggregation Group
 DEVIP: Device Internet Protocol
 ANI: Adjacent Node Identifier
 OSPF: Open Shortest Path First
 VRRP: Virtual Router Redundancy Protocol
 IPPM: Internet Protocol performance monitoring
 SIP: Source Internet Protocol
 DIP: Destination IP Address
 BFD: Bidirectional Forwarding Detection
Thank You
www.huawei.com

Introduction To The BSC6900 V900R014 Feature Transmission Resource Pool in RNC BSC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction To The BSC6900 V900R014 Feature Transmission Resource Pool in RNC BSC

Uploaded by

Copyright:

Available Formats

INTERNAL

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

 RAN Feature Documentation: IP RAN

 RAN Feature Documentation: Transmission Resource Management

 RAN Feature Documentation: Transmission Resource Pool in

 CME Operation Guide to RAN14.0 Transmission Resource Pool in

 ROSA-RC V100R012C00 Transmission Resource Pool in RNC/BSC

 Understand the value and application scenario of the feature

 Understand the feature specifications.

 Explain basic principles of the feature.

 Be able to activate and verify the feature according to the

 Inter-subrack traffic generated by the Iub/Abis interface

 Cross-subrack communication inside the system

 Initial binding is triggered in any of the following situations:

E1/T1 link or dedicated

E1/T1 link or dedicated

Primary Secondary Description

10.10.10.1 20.20.20.1 Null Configure the source IP route of the device IP

RNC Router Peer NE

board be aggregated into a trunk.

Active/Standby interface boards form a

• The reliability is high. During switchover, CS calls are not

• If the transmission resource pool is originally not configured and

Benefits NodeB IP2 IP5

 This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub

 Mutually exclusive features

This feature is mutually exclusive to the following features:

 WRFD-021305 RAN Sharing Phase 2

 WRFD-02130501 Dedicated Iub Transmission Control

 WRFD-050420 FP MUX for IP Transmission

 WRFD-050422 Dynamic Bandwidth Control of Iub IP

 WRFD-050403 Hybrid Iub IP Transmission

 WRFD-050408 Overbooking on IP Transmission

 WRFD-020101 Admission Control

Transmission Resource Pool for A Interface

 This feature is an enhanced version of the feature GBFD-118602 A over IP.

 Impact on network equipment:

5. Feature Deployment and Network Reconfiguration

 Iub Transmission Resource Pool in RNC

MGW Candidate solution:

Interconnection BSC/RNC site

using the LAG

BTS/NodeB LSW BSC/RNC

 Networking schemes 4 and 5: IP-based separated transmission and ATM&IP dual-

 Networking scheme 7: MBTS networking

Networking planning Networking planning

Hardware preparation Deployment Data configuration Feature activation

Data configuration Feature activation

 Transport network requirement

0 Iub POOL 10.10.1.1 10.10.1.2 10.10.1.3 10.10.1.n

 NodeB hardware requirement: a BTS3900 series base station or BTS3902E

Run the ADD DEVIP

Run the ADD UCCP Run the ADD

Optional: Run the ADD Run the ADD IPPOOL

Step 2. Click a node under IP Transport.

 Step 5 (batch configuration): Choose Data Management > Export Incremental

Step 2. Click a node under IP Transport.

 If the inter-RNC handovers are successful on the UMTS

Adding a Physical Port

Adding an Interface Board

2. Configure an IP address for the trunk group.

3. Configure an device IP addresses.

4. Configure a source IP routes.