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

INTERNAL
Introduction to the Featur

eTransmission Resourc
e Pool in RNC/BSC
by Chen Yanyan and Guo Chengxu
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
www.huawei.com
About This Training
This course describes Iub/Iu/Iur/A Transmission Resource P

ool in RNC/BSC, which is a new feature in BSC6900 V900R
014.
Page 3
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/B
SC
CME Operation Guide to RAN14.0 Transmission Resource Pool in RN
C/BSC
ROSA-RC V100R012C00 Transmission Resource Pool in RNC/BSC
Requirement Analysis and Feature Design Description
Page 4
Training Objects
After learning this course, you are supposed to:
Understand the value and application scenario of the feature Tr

ansmission 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 man

ual.
Page 5
Contents
1. Background
2. Feature Introduction
3. Networking Schemes
4. Related Features
5. Feature Deployment
6. O&M
Page 6
Background: Iu/A Interface
The following figure shows the major solution to IP transmission networking over the Iub int
erface in versions earlier than RAN14.0.
MGW POOL
Router1
IPPATH
GOUc/FG2
c
Subrack 1
IP1
Subrack 0
DIP
xGSN POOL
Backup
DIP
Router2
DIP
DIP
This solution has the following drawbacks:
VRRP
DIP
IP2
Active
DIP
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.
Page 7
Background: Iub Interface
The following figure shows the major solution to IP transmission networking over the Iub interface i
n versions earlier than RAN14.0.
NodeBs
Router1
IPPATH
GOUc/FG2c
DIP
DIP
Subrack 1
Subrack 0
IP1
DIP
Backup
DIP
DIP
Router2
This solution has the following drawbacks:
NodeBs
IP2
Active
VRRP
DIP
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 newlyadded 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.
Page 8
Contents
1.
2.
3.
4.
5.
6.
Background
Feature Introduction
Networking Schemes
Related Features
Feature Deployment
O&M
Page 9
Introduction to the Transmission Pool

Application scenario:
Layer 3 (L3) Ethernet
Supported RNC hardware:
GOUc/FG2c and
GOUd/FG2d
Supported NodeB: BTS3900
series or BTS3902E series
Supported interfaces: Iub,
Iur, IuCS, IuPS, and A
interfaces
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.
Page 10
IntroductionPrinciple of Load Balancing for the Iu/Iur/A I

nterface
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 prop
ortion.
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 tw
o 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 subrack
s are different.
Each subrack maintains the SIP load distribution proportion independently. During service setup, the RNC/BSC first selects the user-p
lane board serving the UE/MS and then selects an SIP address. The RNC/BSC balances the load based on the SIP load distribution p
roportion of the selected SIP address by using the subrack that houses the user-plane board as the source subrack.
Page11
Introduction- Calculation of the Inter-Subrack Load

The figure on the left shows the SCUb
interconnection between subracks.
This figure assumes that:
Subrack 2 houses the user-plane

board serving the UE/MS that
accesses the network.
The SIP address is configured in

subrack 3.
The number of cross-subrack

hops is 3.
The maximum inter-subrack
load is 40%.
Page12
Introduction-Iu/Iur/A Load Balancing

The inter-subrack load
is heavy.
The inter-subrack load

is light.
IPPOOL
D
P
U
D
P
U
50%
50%
When the inter-subrack load

increases, the load distributed across
subracks decreases.
SIP1
50%
50% SIP2
The load is not balanced among SIP

addresses due to the unbalanced load on
the user plane of each subrack. As a
result, the load distributed across subracks
increases.
IPPOOL
D
P
U
100%
D
P
U
0%
100% SIP2
0%
SIP1
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
Page13
Introduction-Principle of Iub Load Balancing
Initial binding: Each NodeB is bound to an initial IP address.
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 add
resses 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:
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 cl
osest to the local subrack.
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
Page14
IntroductionImpact of Packet Loss Rate on Load Bala

ncing
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) f
or ping packets sent from local IP addresses.
The RNC/BSC refreshes and records the packet loss rate every 90 seconds. The p
acket 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-2139
4 Transmission Resource Pool IP Packet Loss alarm is reported. When selecting a
n 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 pack
et loss rate is SIP1 and the packet loss rate for an IP address is higher than that fo
r SIP1 by INTPINGLOSTPKTPRITH. In this case, the RNC/BSC does not select th
is IP address, unless the other IP addresses in the IP address pool are faulty or he
avily loaded.
Page15
Page
15
IntroductionPrinciples of the IP Path Configuration

Free
Non-transmission pool: The RNC/NodeB manages IP addresses based on the connection orientatio
n 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 t
he current service. An IP path is selected only when the destination IP address of the call matches t
he destination IP address of the IP path and the priority of the TRMMAP matches the priority of the I
P 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 lo
cal 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)
Page16
IntroductionPrerequisites for IP Path Configuration

Free
IP Path Configuration Free requires that the IP route between the RNC/BSC and a pe
er NE side be reachable. In this way, selection of an IP address on the RNC/BSC is i
ndependent of the IP address used on the peer NE.
Page17
IntroductionPrinciple of Source-Based Routing
Objective of source-based routing: The route configuration on the local RNC/BSC does not need to be adjusted w
hen 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 forward
s 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 RN
C/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 destinatio
n-based route.
Source-based routing is applicable to the scenario where the primary and secondary gateways are configured.
Primary
Gateway
Secondary
Gateway
Description
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
DEVIP
Router
20.20.20.2
20.20.20.1
Peer NE
IP Network
10.10.10.1
Peer
IP1
10.10.20.1
Peer
IP2
10.10.30.1
Peer
IPn
Page18
Contents
1.
2.
3.
4.
5.
6.
Background
Networking Schemes
Related Features
Feature Deployment
O&M
Page 19
IntroductionNetworking 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.
Four individual GOUc boards form a transmission

resource pool. Each board is configured with a device
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
recommended that two or more ports on an interface
board be aggregated into a trunk.
Benefits
The maximum payload throughput and session

setup/release times of an interface board are doubled.
Interface boards can be evenly distributed among the

RNC/BSC subracks.
Capacity expansion can be performed on a single

board.
The advantages of the interface board pool are

provided.
Page 20
Typical deployment scenario: The customer is sensitive to call drops caused by a faulty board.
Active/Standby interface boards form a
transmission resource pool.
Multiple pairs of GOUc boards working in active/standby mode

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

trunk group.
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

DEVIP are configured.
Benefits
The reliability is high. During switchover, CS calls are not

dropped and the time during which the PS throughput drops to
0 is short.
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.
The advantages of the interface board pool are provided.
Page 21
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.
Multiple pairs of GOUc boards working in active/standby mode

form a transmission resource pool.
GE ports on the active and standby boards work in

active/standby mode and are connected to routers using
Virtual Router Redundancy Protocol (VRRP).
Multiple pairs of active/standby ports are configured on an

interface board. Each pair of active/standby ports is configured
with a DEVIP. DEVIPs of all interface boards form a service IP
address pool.
Reconfiguration on peer routers is not needed. VRRP

configuration is the same as that in the scenario where a
transmission resource pool is not configured.
Benefits
The reliability is high. During switchover, CS calls are not

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.
Page 22
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
Iub and Iu interfaces. This networking scheme is applicable
to all the three scenarios described earlier.
This networking scheme is specific to propaganda to to build

the brand of Huawei. It is not recommended or deployed.
Benefits
The resource usage of interface boards is high.
It is recommended that the Iub interface and Iu/Iur interface use

two transmission resource pools respectively formed by two
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.
Page 23
Contents
1.
2.
3.
4.
5.
6.
Background
Networking Schemes
Related Features
Feature Deployment
O&M
Page 24
Introduction to the Iub Transmission Res

ource PoolRelated Features
Required features
This feature depends on the feature WRFD-050402 IP Transmission Introduction on Iub I

nterface.
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
Page 25
Introduction to the Iu/Iur Transmission Resou

rce PoolRelated 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.
Page 26
IntroductionImpacts
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 ch
anges of interface boards. When user-plane IP addresses are added or adjusted on the core network and RN
C, 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 (OS
PF) areas.
Pool formed by individual interface boards: Two routers can be independent of each other. OSPF is deployed b
etween routers.
Pool formed by active/standby interface boards (active/standby ports): Original configurations (such as VRRP a
nd 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 pee
r NE are reachable.
Page 27
Contents
1.
2.
3.
4.
5.
6.
Background
Networking Schemes
Related Features
Feature Deployment and Network Reconfiguration
O&M
Page 28
When to Use the Feature and Information to Be Collec

ted
Before deploying the feature Transmission Resource Pool in RNC/BS
C, 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 serie
s does not support the transmission resource pool on the Iub interface.
The Iu/Iur interface adopts L3 networking, that is, all IP routes between t
he RNC and NodeBs are reachable.
Page 29
Feature Activation PlanningVersion/Li

cense 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
Page 30
IntroductionApplication Scenario and Feature Gain

Scenario
Description
Gain
Scenario 1: IP-
The RNC is connected to aL3 router. All DEVIP routes between the router and
1. Improved reliability
based L3
the RNC are reachable.
2. Simple deployment
networking
The feature Transmission Resource Pool in RNC is recommended.
3. High transmission resource

utilization
Scenario 2: IP-
The Iub interface adopts end-to-end layer 2 networking. The Iub bearer
based L2
network uses the MSTP/PTN Ethernet dedicated lines. The feature
networking
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
based networking
(PPP/MP) networking.
None
None
The feature Transmission Resource Pool in RNC is NOT recommended.

Scenario 4 IP-
Real-time services are transmitted over PPP/MP, and non-real-time services
based separated
are 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
dual-stack
are transmitted over the Ethernet network. The Ethernet ports form a
transmission
transmission pool.
3. High transmission utilization
None
The feature Transmission Resource Pool in RNC is recommended.

Scenario 6:
On a RANSharing or MOCN network, if the transmission resource pool is used,
RANSharing
separated transmission between carriers is not supported.
Scenario 7: MBTS
When the GSM, UMTS, and LTE base stations share the transmission
networking
resources, only the UMTS NodeBs support configuration of the transmission
resource pool on the RNC.
Page 31
Networking SolutionDeployment
Networking scheme for a newly deploy
ed network
It is strongly recommended that the feature

Transmission Resource Pool in RNC/BSC b
e sold to a newly deployed site. On an MSC
Higher
reliability
pool enabled network, it is strongly recom
Customers
requirements
Lower cost
and easier
to maintain
mended that the feature Iu/Iur Transmission

Resource Pool in RNC be sold as well.
Suggestions for selecting a transmission res

ource pool networking scheme for each inter
face: If the customer is sensitive to reliability
and requires that ongoing calls are not drop
ped when an interface board is faulty, use in
terface boards that work in active/standby m
ode to form the pool. Otherwise, use individ
ual interface boards to form the pool.
Candidate solution 1: Ports of

routers share the load. The interface
boards of the RNC/BSC form the
transmission resource pool. The
interface boards work in
active/standby mode. All ports on
interface boards are active ports.
SIP addresses are configured with
the primary and secondary
gateways. Ports on an interface
board are aggregated to share the
load.
Page 32
Recommended solution: Ports

of routers share the load. The
interface boards of the
RNC/BSC form the transmission
resource pool. The interface
boards work independently.
Ports on an interface board are
aggregated to share the load.
Network Planning for the Iu/Iur/A T

ransmission 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.
Page 33
Existing Networking Schemes of the Iu/Iur/A Interface a

nd Network Reconfiguration Solutions
Networking scheme 1: Active/standby interface boards, active/standby
ports + VRRP
RAN
BACKBONE
Network Reconfiguration
Solution
IP5
CE
Control-plane VPN
IP1&IP2
VRRP1&2
VIP: IP1'&IP2'
IP core
MSC SVR
IP6
User-plane VPN
BSC/RNC
CE
MGW
Networking scheme 2: Active/standby interface boards, active ports

(primary and secondary routes)
RAN
BACKBONE
Control-plane VPN
IP1'&IP2'
IP1&IP2
IP core
IP3&IP4
IP3'&IP4'
Candidate solution:
Individual interface boards
form an interface board
pool.
IP5
CE
BSC/RNC
Recommended solution:
Active/standby interface
boards with active/standby
ports form an interface
board pool.
MSC SVR
IP6
boards with individual ports
pool.
User-plane VPN
CE
MGW
Page 34
Network Planning for the Iub Transmis

sion 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 r
esource pool. In this way, a fault on an interface board does not result in call drops. If the network rel
iability requirements are not high, use individual interface boards to form a transmission resource po
ol.
Signaling plane: For NCP/CCP signaling over the Iub interface, it is recommended that one SCTP lin
k be bound to the IP addresses of two interface boards in the transmission resource pool on the RN
C/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 Iu
b 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 ev
enly distributed among the RNC subracks
The NodeB must be a BTS3900 series base station or BTS3902E.
Page 35
Existing Networking Schemes of the Iub Interfac

e and Network Reconfiguration Solutions
Networking scheme 1: Iub L3 networking

boards with individual ports
pool.
BSC/RNC site
Active/standby
interface boards;
primary/secondary
routes
CE
DEV IP
IP11
IP1'
BTS/NodeB
IP1
IP backhaul
IP2
IP2
BTS/NodeB
BSC/RNC
CE
BTS/NodeB
Active/standby
ports + VRRP
CE
BSC/RNC site
BTS/NodeB
VRRP
VIP: IP1'
IP backhaul
BTS/NodeB
BTS/NodeB
CE
Candidate solution:
Individual interface boards
pool.
boards with active/standby
ports form an interface
board pool.
IP1
BSC/RNC
Page 36
Existing Networking Schemes of the Iub Interface

and Network Reconfiguration Solutions
Networking scheme 2: Iub L2 networking

BSC/RNC site
Interconnection
using the LAG
Network
reconfiguration is
not supported.
BTS/NodeB
LAG
IP backhaul
LSW
BTS/NodeB
BSC/RNC
BTS/NodeB
Interconnecti
on using the
L2 switch
Network
reconfiguration is
not supported.
LSW
Active
BTS/NodeB
IP backhaul
BTS/NodeB
Standby
BSC/RNC
LSW
L2 switch
BTS/NodeB
Page 37
Existing Networking Schemes of the Iub Interface and

Network Reconfiguration Solutions
Networking scheme 3: Iub IP over E1 networking

CE
E1
NodeB
TDM/SDH
backhaul
GE
Network
reconfiguration is not
supported.
CE
E1
NodeB
RNC
STM-1
TDM/SDH
backhaul
Networking schemes 4 and 5: IP-based separated transmission and ATM&IP dualstack transmission over Iub
CE
GE
IP backhaul
FE
NodeB
CE
E1
The transmission resource pool

cannot be configured for either IP
over E1 or IP over ETH.
STM-1
RNC
TDM/SDH
backhaul
For ATM over E1 and IP over ETH

dual stacks, the IP address pool
can be configured only for the IP
network part.
Page 38
Existing Networking Schemes of the Iub Interface

and Network Reconfiguration Solutions
Networking scheme 6: Iub RANSharing networking

Operator A
CE
Operator B
NodeB
Operators can share

the Iub interface.
IP1
IP backhaul
CE
BSC/RNC site
BSC/RNC
Networking scheme 7: MBTS networking

UMTS
BTS/NodeB
CE
GSM
IP1
IP backhaul
BTS/NodeB
BTS/NodeB
BSC/RNC site
CE
BSC/RNC
Page 39
Only the UMTS

NodeBs support
configuration of the
transmission resource
pool on the RNC
Solutions to Configuration of an Iub Transmission R

esource Pool for a Live Network
Existing Networking Scheme
Recommended Solution
Candidate Solution
L3 networking: The GOUc/FG2c

boards work in active/standby mode.
The GOUc/FG2c boards still work in active/standby mode.

1. Active/standby ports + VRRP: Active/standby interface
boards with active/standby ports form a transmission
resource pool.
2. Individual ports + primary/secondary routes:
Active/standby interface boards with individual ports form a
transmission resource board pool.
Advantage: The network reliability is high. After the pool is
configured, reconfiguration of the bearer network is not
needed.
The individual GOUc boards form

a transmission resource pool.
The operator is not sensitive to call
drops and agrees to change the
configurations of the bearer
network.
Advantage: The cost is low.
L3 networking: The GOUc/FG2c

boards work independently.
The individual GOUc boards form a transmission resource pool.
L3 networking: The GOUa/FG2a

boards are used.
The feature Transmission Resource Pool in RNC is not supported.
L2 networking: EPL or EPLAN

networking
End-to-end TDM networking
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

networking
Currently, the GSM does not support the interface board pool. Therefore, different configuration
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.
Page 40
DeploymentOverall Procedure
Deployment scenario
Network reconfiguration scenario:
Networking
planning
Information
collection
CME data
preparation
Networking
planning
Information
collection
CME data
preparation
Hardware
preparation
Deployment
Data
configuration
Feature
activation
Data
configuration
Feature
activation
Page 41
DeploymentRequirements
Deployment requirements
To deploy the feature Iu/Iur Transmission Resource Pool in RNC, lic

enses 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 t

he RNC support link aggregation.
All routes from a peer NE to the interface boards in the transmission res
ource pool of the RNC are reachable.
Page 42
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 Nod
eB to the IP address pool of the RNC.
POOL ID
POOL
Name
0 Iub POOL
POOL IP
IP1
IP2
IP3
Ipn
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 bo

ard.
NodeB hardware requirement: a BTS3900 series base station or BTS3902E
Page 43
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 band
width-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 t
he RNC side.
After the source-based routes are configured, the source-based routes take precedence over th
e 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 trans
mission not separated) is supported, but RANSharing Phase 2 (operators user plane and admis
sion separated) and RANSharing Phase 3 (operators user plane not separated but admission s
eparated) 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.
Page 44
Deployment of the Iub Transmission Resource

Pool in RNCRequirements
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
Run the SET ETHPORT command

to set properties of Ethernet ports.
Run the ADD SCTPLNK

command to add two
SCTP links.
Optional: Run the

ADD ETHREDPORT
command to add
active/standby Ethernet ports.
Run the ADD UNCP

command to add an NCP.
Run the
ADD ETHIP
command to add
IP addresses for
Ethernet ports.
Link aggregation:
Run the ADD ETHTRK
command to add an
LAG. Run the
ADD ETHTRKLNK
commands to add links
to the LAG. Run the
ADD ETHTRKIP
command to add IP
address for the LAG.
Run the ADD UCCP

command to add a CCP
link.
RNC user plane

Run the ADD DEVIP
command to add a
device IP address and
run the ADD SRCIPRT
command to specify the
source IP route.
Run the ADD IPPOOL
command to add an IP
address pool.
Run the
ADD IPPOOLIP
command to add userplane IP address (IP1 to
IPn) to the IP address
pool.
Run the ADD ADJNODE
command to add an
adjacent node and run
the ADD ADJMAP
command to map the
adjacent node to the IP
address pool.
Page 45
NodeB configuration
Run the
ADD SERV IP
command to add an
service IP address.
Run the ADD IPRT
command to add a
route.
Run the
ADD SCTPLNK
command to add an
SCTP link.
Run the
SET HSDPAFLOWCTRLPARA
command to turn on the
DYNAMIC_BW_SHAPING
switch (dynamic traffic
shaping).
Deployment of the Iu/Iur/A Transmission Resourc

e Pool in RNCRequirements
Activation
Except the control plane configuration, other configurations are the same as those made for deployment of the Iub transmission resou
rce pool in RNC.
Control plane
Basic physical configuration
User plane
Run the ADD SCTPLNK command to

add multiple SCTP links.
Run the SET ETHPORT command

to set properties of Ethernet ports.
Run the ADD M3LKS command to add
an M3UA link set.
Optional: Run the
ADD ETHREDPORT
command to add
active/standby Ethernet ports.
Run the ADD ETHIP

command to add IP
addresses for Ethernet
ports.
Link aggregation:
Run the ADD ETHTRK
command to add an
LAG. Run the
ADD ETHTRKLNK
commands to add links
to the LAG. Run the
ADD ETHTRKIP
command to add IP
address for the LAG.
Run the ADD M3RT command to add an

M3UA route.
Run the ADD M3LNK command to add

an M3UA link.
Run the ADD UCNDOMAIN command to

add the CN domain.
Run the ADD UCNNODE to add a CN

node.
Page 46
Run the ADD DEVIP

command to add a
device IP address and
run the ADD SRCIPRT
command to specify the
source IP route.
Run the ADD IPPOOL
command to add an IP
address pool.
Run the ADD IPPOOLIP

command to add userplane IP address (IP1 to
IPn) to the IP address
pool.
Run the ADD ADJNODE

command to add an
adjacent node and run the
ADD ADJMAP
command to map the
adjacent node to the IP
address pool.
Deployment of the Iub Transmission

Resource Pool in RNCCME
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 R
NC 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 n
etwork reconfiguration. For example, if it is required that VLAN configuration be added after network reco
nfiguration, the reconfiguration cannot be completed at a time.
Page 47
Configuring an Iub Transmission Resource P

ool on a Newly Deployed NetworkCME
To configure an Iub transmission resource pool on a newly deployed network, perform the follo
wing 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.
Page 48

Step 3 (GUI-based configuration): In the Main View navigation tree, right-click NodeB and choose IP Transpo
rt Layer.
Step 3 (batch configuration): Prepare the Iub interface data and add the RNC planning data and NodeB planni
ng data to the Iub negotiation template of the CME.
Page 49
Configuring an Iub Transmission Resource

Pool on a Newly Deployed NetworkCME
Step 4 (GUI-based configuration): Click Export Incremental Scripts. The increme

ntal 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 I
ub Interface Data.
Page 50

ub Interface Data.
Page 51
Configuring an Iu Transmission Resource

To configure an Iu transmission resource pool on a newly deployed network, perform t
he following steps:
Step 1. In the Transmission View navigation tree, choose UMTS > IuPS (or IuCS,
or Iur). An interface navigation tree is displayed.
Page 52

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.
Page 53

uIur Interface Data.
Step 5 (batch configuration): Choose Data Management > Export Incremental Sc

ripts to obtain the scripts for the RNC and sends the scripts to the RNC.
Page 54
Configuring an Iub Transmission Resource Pool on

a Live NetworkCME
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.
Page 55
Configuring an Iub Transmission Resour

ce Pool on a Live NetworkCME
Step3. Choose UMTS Application > RNC Pool Configuration.
Step4. Select the NodeBs related to the transmission resource pool and c
lick Next.
Page 56
Feature DeploymentActivation Obs

ervation
Activation observation
Transmission over the Iu/Iub interface is a fundamental part of

a service flow. If various services (for example, CS, PS, HSDP
A, and HSUPA services) can be completed properly, a transmis
sion resource pool has been configured for the Iu/Iub interface.
If the inter-RNC handovers are successful on the UMTS netwo
rk, a transmission resource pool has been configured for the Iu
r interface.
Page 57
Feature DeploymentCapacity 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.
Page 58
Contents
1.
2.
3.
4.
5.
6.
Background
Networking Schemes
Related Features
Feature Deployment and Network Reconfiguration
O&M
Page 59
O&MPerformance Monitoring
The load of each interface board in the transmission resource pool must be monitore
d 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 t
han 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 o
n 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)
Page 60
O&MReal-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 LO
CAL 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 d
rop-down list box, and specify Adjacent Node ID, Local IP Address, Peer IP Addres
s, and Priority. All the four parameters are mandatory.
Page61
Page
61
O&MSummary
Alarm
Counter
Fault Location
Real-Time
Performance
Monitoring
ALM-21392
Adjacent Node IP
Address Ping Failure
Number of active
connections of an
adjacent node
ALM-21393
Adjacent Node IP
Path Ping Failure
Bandwidth
allocated to an
adjacent node
Manually bind a
NodeB to an IP
address in the
transmission
resource pool.
Real-time
performance
monitoring of IP
traffic
ALM-21394
Transmission
Resource Pool IP
Packet Loss
Congestion status
of an adjacent
node
ALM-21603
Adjacent Node
Congestion
ALM-21602 IP In IP
Address Pool
Blocked
Ping test results of

an adjacent node
Specify the
source IP
address to trace
signaling of a
single subscriber.
Traffic of an
adjacent node
SIP traffic
Page 62
IP PM real-time
performance
monitoring
O&MCustomized Parameters and

Counters
MML commands and counters on the RNC side
GU RNC-BSC
GU RNC-BSC
Counter Changes (Transmission
Parameter Changes (Transmissi
MML commands on the NodeB side: ADD/RMV/LST/MOD SERVIP

Parameter
Value
Default Value
Description
SERVTYP
IUB0
Service IP
address type
IP
IPv4
N/A
IP address
Page 63
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
Page 64
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

Introduction to the Featur

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

About This Training

This course describes Iub/Iu/Iur/A Transmission Resource P

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

Some of the sources this course references are as follows:

RAN Feature Documentation: IP Transport Architecture

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

After learning this course, you are supposed to:

Understand the value and application scenario of the feature Tr

Understand the feature specifications.

Explain basic principles of the feature.

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

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

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

Background: Iu/A Interface

This solution has the following drawbacks:

Major objectives of the solution:

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

Background: Iub Interface

This solution has the following drawbacks:

Major objectives of the solution:

1. Configuration of IP paths and rehoming of NodeBs are not required.

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

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

Introduction to the Transmission Pool

IntroductionPrinciple of Load Balancing for the Iu/Iur/A I

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%))

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

Introduction- Calculation of the Inter-Subrack Load

Subrack 2 houses the user-plane

The SIP address is configured in

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

The number of cross-subrack

Introduction-Iu/Iur/A Load Balancing

The inter-subrack load

When the inter-subrack load

The load is not balanced among SIP

Inter-subrack traffic generated by the Iub/Abis interface

Cross-subrack communication inside the system

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

Introduction-Principle of Iub Load Balancing

Initial binding: Each NodeB is bound to an initial IP address.

Initial binding is triggered in any of the following situations:

Same as that of the Iu/A interface

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

IntroductionImpact of Packet Loss Rate on Load Bala

Packet loss rate detection and isolation

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

IntroductionPrinciples of the IP Path Configuration

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)

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

IntroductionPrerequisites for IP Path Configuration

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

IntroductionPrinciple of Source-Based Routing

Configure the source IP route of the Ethernet port IP

Configure the source IP route of the device IP

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

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