Base Station Controller Transmission Performance Monitoring (01) (PDF) - EN
Base Station Controller Transmission Performance Monitoring (01) (PDF) - EN
SRAN19.1
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: [email protected]
Contents
Product Version
Product Name Product Version Solution Version
Intended Audience
This document is intended for:
● System engineers
● Site maintenance personnel
1.1 Changes in Base Station Controller Transmission Performance Monitoring
1.2 Overview
1.3 Transmission Capacity Monitoring
1.4 Transport Congestion Monitoring
1.5 Transmission QoS Monitoring
01 (2023-03-07)
Compared with Draft A (2022-12-30), this issue does not include any changes.
Draft A (2022-12-30)
Compared with Issue 01 (2022-03-07) of SRAN18.1, this issue does not include
any changes.
1.2 Overview
Throughput ● Data receive rate ● Data receive rate ● Data receive rate
rate ● Data transmit ● Data transmit ● Data transmit
rate rate rate
1.3.1 Overview
This chapter describes counters related to BSC service traffic. The BSC provides
user-plane, control-plane, and transmission port (Ethernet port and ports in an
LAG) traffic statistics.
The counter monitoring helps the operation and maintenance (O&M) personnel
track equipment traffic in real time, analyze usage of IP-based network
bandwidths, and determine the following:
● Whether the transmission bandwidth allocated to the BSC is fully utilized
● Whether the BSC transmission bandwidth needs to be increased
measurement period. The measurements reflect the average load of the local IP
address.
VS.LGCPRT.Alloced.Max.Fwd
VS.LGCPRT.Alloced.Max.Bwd
These counters track the maximum forward and backward bandwidths allocated
to a logical port during a measurement period. The measurements reflect the
maximum service volume of the logical port within the measurement period.
VS.LGCPRT.Alloced.Ave.Fwd
VS.LGCPRT.Alloced.Ave.Bwd
These counters track the average forward bandwidth and average backward
bandwidth allocated to a logical port during a measurement period. The
measurements reflect the service volume of the logical port within the
measurement period.
Counters
VS.SCTP.IPLAYER.TXMAXSPEED
VS.SCTP.IPLAYER.RXMAXSPEED
These counters track the maximum transmit and receive rates for a single SCTP
link at the IP layer during a measurement period. The measurements reflect the
maximum load of the SCTP link.
VS.SCTP.IPLAYER.TXMEANSPEED
VS.SCTP.IPLAYER.RXMEANSPEED
These counters track the average transmit and receive rates for a single SCTP link
at the IP layer during a measurement period. The measurements reflect the
average load of the SCTP link.
VS.FEGE.RXBYTES
These counters track the total number of bytes transmitted and received by a
single Ethernet port during a measurement period. The measurements reflect the
throughput of the Ethernet port.
VS.FEGE.TXMAXSPEED
VS.FEGE.RXMAXSPEED
These counters track the maximum transmit and receive rates for a single Ethernet
port during a measurement period. The measurements reflect the maximum load
of the Ethernet port.
VS.FEGE.TXMEANSPEED
VS.FEGE.RXMEANSPEED
These counters track the average transmit and receive rates for a single Ethernet
port during a measurement period. The measurements reflect the average load of
the Ethernet port.
and other related counters be analyzed together. The analysis result helps
determine whether the exception is normal or caused by a fault.
Counters
VS.IPPOOL.ADJNODE.Fwd.Cong
VS.IPPOOL.ADJNODE.Bwd.Cong
These counters track the number of times there was forward and backward
congestion on an IP transport adjacent node. These counters and the following
two counters reflect the overall IP transport adjacent node congestion. If a large
number of IP transport adjacent nodes are congested for a long time, services will
be affected.
VS.IPPOOL.ADJNODE.Fwd.Cong.Dur
VS.IPPOOL.ADJNODE.Bwd.Cong.Dur
These counters track how long an IP transport adjacent node experiences forward
and backward congestion. These counters and the above two counters reflect the
overall IP transport adjacent node congestion. If a large number of IP transport
adjacent nodes are congested for a long time, services will be affected.
Counters
VS.LGCPRT.Fwd.Cong
VS.LGCPRT.Bwd.Cong
These counters track the number of times there was forward and backward
congestion on a logical port during a measurement period. These counters and
the following two counters reflect the overall logical port congestion. If a large
number of logical ports experience congestion for a long time, service experience
will deteriorate.
VS.LGCPRT.Fwd.Cong.Dur
VS.LGCPRT.Bwd.Cong.Dur
These counters track how long a logical port experiences congestion during a
measurement period. These counters and the number of times a logical port is
congested reflect the overall logical port congestion. If a large number of logical
ports are congested for a long time, service access will be affected.
Counters
VS.FEGE.Fwd.Cong
VS.FEGE.Bwd.Cong
These counters track the number of times there was forward and backward
congestion at an FE/GE Ethernet port within a measurement period. If an FE/GE
Ethernet port is congested for a long time, service access may be affected. The
values of these counters and the following two counters jointly reflect the overall
congestion situation of an FE/GE Ethernet port.
VS.FEGE.Fwd.Cong.Dur
VS.FEGE.Bwd.Cong.Dur
These counters track the accumulated duration of forward and backward
congestion on an FE/GE Ethernet port during a measurement period. If an FE/GE
Ethernet port is congested for a long time, service access may be affected. The
values of these counters and the number of times the FE/GE Ethernet port was
congested jointly reflect the overall congestion situation of an FE/GE Ethernet
port.
Counters
VS.SCTP.REQ.RETX.NUM
This counter tracks the number of retransmission requests on an SCTP link during
a measurement period. The measurements indicate whether there is packet loss or
a delay in the receive direction.
VS.SCTP.RETX.PKGNUM
This counter tracks the number of retransmitted packets on an SCTP link during a
measurement period. The measurements indicate whether there is packet loss or a
delay in the transmit direction.
Counters
VS.SCTP.CONGESTION.INTERVAL
This counter tracks how long there is SCTP link congestion during a measurement
period. The system periodically checks the SCTP link status. If the SCTP link is
congested, the system measures the duration of SCTP link congestion within a
measurement period. At the end of the measurement period, the system sums all
measured durations to obtain the value of the T6012: Congestion Duration of the
SCTP Link counter.
VS.SCTP.SERVICE.INTERVAL
This counter tracks how much time services are available on an SCTP link during a
measurement period. The system periodically checks the SCTP link status. If the
SCTP link is normal, the system measures the amount of time services are
available on an SCTP link within a measurement period. At the end of the
measurement period, the system adds the time together to calculate the value of
the T6011: Service Duration of the SCTP Link counter.
1.5.1 Overview
This chapter describes how to monitor the QoS of a transport network based on
counters provided by the BSC, and details technologies used by the BSC to
measure the QoS of the transport network. The BSC measures the QoS of the
transport network either using IP performance monitoring (IPPM) or Two-Way
Active Measurement Protocol (TWAMP) technology.
● IPPM
Monitors the user-plane service transmission QoS in online mode and
provides end to end (E2E) measurement from a BTS to a BSC.
● TWAMP
Checks the QoS of a transport network link between NEs or switches, such as
between a BTS and a BSC and between a BTS/BSC and the equipment on a
bearer network.
The transport network QoS is a key counter for evaluating network quality. It
involves packet loss, delay, and jitter. Long-term monitoring of these counters
helps users track the network quality in real time. If the network quality is poorer
than the specified standard, expand the network capacity.
The transport network QoS also provides a basis for the BSC flow control
algorithm to detect congestion. QoS changes reflect network congestion, based on
which targeted flow control can be performed to relieve network congestion.
● Maintenance
QoS-related counters of a transport network are monitored to determine
whether an intermediate device becomes faulty or whether the network is
affected by an abnormal process.
● Network capacity
The transport network QoS is monitored for a long period. If the QoS is poor
within a long time, network capacity needs to be expanded.
This chapter describes how to observe the transport network QoS using
available performance counters related to delay, packet loss, and jitter.
Counters
VS.IPPOOL.IPPM.Rtt.Means
VS.IPPOOL.IPPM.MaxRttDelay
These counters track the IPPM RTT delay during a measurement period and reflect
the transmission quality between the local and peer IP addresses to be checked.
The measurements reflect the overall situation of the bi-directional transport
network RTT delay and help evaluate transport network quality.
VS.IPPOOL.IPPM.Forward.JitterStandardDeviation
This counter tracks the standard deviation for delay jitter of forward IPPM data
packets during a measurement period and reflects transmission delay stabilization
of the local and peer IP addresses to be checked. The measurements reflect
changes in the transport network delay and help evaluate transport network
stability.
VS.IPPOOL.IPPM.Forward.DropMeans
VS.IPPOOL.IPPM.Forward.Peak.DropRates
These counters track the average and maximum numbers of IPPM packets lost on
the forward link during a measurement period. The measurements reflect the
overall packet loss situation of the transport network and help evaluate transport
network quality.
If the standard deviation of jitter increases suddenly, the transport network delay
frequently changes, indicating unstable network quality. If the standard deviation
of jitter decreases, the transport network delay slightly changes, indicating stable
network quality.
If packet loss increases suddenly, the transport network quality is poor. In this
case, a call may have unclear voice or a video may stall. If packet loss is small, the
transport network quality is good.