Escolar Documentos
Profissional Documentos
Cultura Documentos
www.huawei.com
Page 3
References
Page 4
Training Objects
Page 5
Contents
1. Background
2. Feature Introduction
3. Networking Schemes
4. Related Features
5. Feature Deployment
6. O&M
Page 6
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
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.
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
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
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.
Page 8
Contents
1.
2.
3.
4.
5.
6.
Background
Feature Introduction
Networking Schemes
Related Features
Feature Deployment
O&M
Page 9
Page 10
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.
Page11
Page12
IPPOOL
D
P
U
D
P
U
50%
50%
SIP1
50%
50% SIP2
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:
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.
Page13
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:
Page14
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
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
Page16
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
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
10.10.10.1
20.20.20.1
Null
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
Feature Introduction
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.
Benefits
Page 20
IntroductionNetworking Scheme 2
Typical deployment scenario: The customer is sensitive to call drops caused by a faulty board.
Active/Standby interface boards form a
transmission resource pool.
All GE ports on the active and standby boards are active ports.
Benefits
Page 21
IntroductionNetworking Scheme 3
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.
Benefits
Page 22
IntroductionNetworking Scheme 4
Iub/Iu interface boards forming one or two
transmission resource pools.
Benefits
Page 23
Contents
1.
2.
3.
4.
5.
6.
Background
Feature Introduction
Networking Schemes
Related Features
Feature Deployment
O&M
Page 24
Required features
Affected features
Page 25
Required features
The transmission resource pool of RAN14.0 does not support the IPMUX function .
This feature and the feature GBFD-118610 UDP MUX for A Transmission are mutually
exclusive.
Page 26
IntroductionImpacts
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.
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
Feature Introduction
Networking Schemes
Related Features
Feature Deployment and Network Reconfiguration
O&M
Page 28
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.
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
Page 30
Description
Gain
Scenario 1: IP-
The RNC is connected to aL3 router. All DEVIP routes between the router and
1. Improved reliability
based L3
2. Simple deployment
networking
Scenario 2: IP-
The Iub interface adopts end-to-end layer 2 networking. The Iub bearer
based L2
networking
Scenario 3: PPP/MP-
based networking
(PPP/MP) networking.
None
None
based separated
transmission
Scenario 5: ATM&IP
1. Improved reliability
dual-stack
are transmitted over the Ethernet network. The Ethernet ports form a
2. Simple deployment
transmission
transmission pool.
None
1. Improved reliability
RANSharing
2. Simple deployment
3. High transmission utilization
Scenario 7: MBTS
When the GSM, UMTS, and LTE base stations share the transmission
1. Improved reliability
networking
2. Simple deployment
Page 31
Networking SolutionDeployment
Networking scheme for a newly deploy
ed network
Higher
reliability
Customers
requirements
Lower cost
and easier
to maintain
Page 32
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 Iu/Iur/A interface boards, Iub interface boards, user-plane boards, and control-plane boards are evenly
distributed among the RNC/BSC subracks.
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
Page 33
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
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
Recommended solution:
Active/standby interface
boards with individual ports
form an interface board
pool.
User-plane VPN
CE
MGW
Page 34
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
Page 35
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
form an interface board
pool.
Recommended solution:
Active/standby interface
boards with active/standby
ports form an interface
board pool.
IP1
BSC/RNC
Page 36
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
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
STM-1
RNC
TDM/SDH
backhaul
Page 38
CE
Operator B
NodeB
IP1
IP backhaul
CE
BSC/RNC site
BSC/RNC
BTS/NodeB
CE
GSM
IP1
IP backhaul
BTS/NodeB
BTS/NodeB
BSC/RNC site
CE
BSC/RNC
Page 39
Recommended Solution
Candidate Solution
Only the IP transmission part supports the feature Transmission Resource Pool in RNC. (L3/L2
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
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
Version requirement
RAN14.0 or later
Page 42
DeploymentRequirements
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
Page 43
DeploymentRequirements
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
The total number of IP addresses in all IP address pools cannot exceed 128.
Page 44
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.
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 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).
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
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.
Page 46
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
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
Step 4 (batch configuration): Choose UMTS Application > Import Data > Import I
ub Interface Data.
Page 50
Step 5 (batch configuration): Choose UMTS Application > Import Data > Import I
ub Interface Data.
Page 51
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 (batch configuration): Prepare the IuPS/IuCS/Iur interface data and add the
planning data to the IuIur negotiation template of the CME.
Page 53
Step 4 (batch configuration): Choose UMTS Application > Import Data > Import I
uIur Interface Data.
Page 54
Page 55
Step4. Select the NodeBs related to the transmission resource pool and c
lick Next.
Page 56
Activation observation
Page 57
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
Feature Introduction
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.
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.
The following counters are used to monitor load balancing over the Ethernet ports in the transmission
resource pool:
Page 60
Newly added
performance
monitoring on the
transmission
resource pool
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.
Copyright 2011 Huawei Technologies Co., Ltd. All rights reserved.
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
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
GU RNC-BSC
GU RNC-BSC
Counter Changes (Transmission
Parameter Changes (Transmissi
Value
Default Value
Description
SERVTYP
IUB0
Service IP
address type
IP
IPv4
N/A
IP address
Page 63
Terms
Page 64
Thank You
www.huawei.com