IP Active Performance Measurement: Twamp

IP Active Performance
Measurement
TWAMP
Avril 2017
Optim Huawei / Youssef Nouir

Overview
This feature measures IP performance on connections between network elements (NEs) and devices
that support TWAMP in a radio transmission network. The performance metrics include one-way
packet loss rate, round-trip delay, and one-way delay variation.
IP performance measurement can be performed on connections between eNodeBs, between a

GSM/UMTS dual-mode base station and a base station controller, between an eNodeB and a serving
gateway (S-GW), between base station controllers, between a base station controller and a core
network (CN), between an NE in a radio network and a transmission device (for example, a router),
and between an NE in a radio network and a test device.
TWAMP: Two-way Active Measurement Protocol
| 9 May 2018 | 2
Benefits
The IP Active Performance Measurement feature provides the following benefits:
Quick transmission network performance monitoring

If the transmission rate is unstable and the transmission bandwidth changes, this feature enables
operators to quickly identify transmission network problems for future capacity expansion and network
optimization.
Quick fault diagnosis

This feature uses TWAMP to quickly troubleshoot transmission faults, such as high packet loss rate or
long delay.
Low maintenance costs

This feature enables troubleshooting a transmission network by segment, which improves network
maintainability and reduce maintenance costs.
However, TWAMP uses User Datagram Protocol (UDP) packet injection, which generates traffic
and occupies bandwidth. For example, if 80-byte packets are continuously sent at a rate of 10
packets per second in a test stream, a bandwidth of 6.4 kbit/s is consumed.
| 9 May 2018 | 3
Technical Description
Position of TWAMP in the TCP/IP protocol stack
In accordance with TWAMP, this feature measures the transmission quality at the network layer. The
controller sends test packets before performing IP packet fragmentation. The responder performs IP
packet assembly before responding to the received test packets.
| 9 May 2018 | 4
Basic Concepts
TWAMP defines four logical entities: Session-Sender, Session-Reflector, Control-Client, and Server.
TWAMP also defines two packet types: control packet and test packet.
TWAMP deployment in full mode
In full mode, one host (Controller) plays the roles of the Session-Sender and Control-Client, and the other host
(Responder) plays the roles of the Session-Reflector and Server, as shown in Figure 3-3. The Controller sends TCP-type
TWAMP control packets to the Responder for establishing test sessions. After the sessions are established, the
Controller sends UDP-type TWAMP test packets to the Responder. The Session-Reflector of the Responder responds to
the test packets.
| 9 May 2018 | 5
TWAMP Measurement Parameters
Packet Loss Rate
The packet loss rate indicates the transmission quality of a tested IP link.
The calculation formulas are as follows:
- Forward packet loss rate = (Number of packets transmitted by the Session-Sender – Number of
packets transmitted by the Session-Reflector)/Number of packets transmitted by the Session-Sender.
- Backward packet loss rate = (Number of packets transmitted by the Session-Reflector – Number of
packets received by the Session-Sender)/Number of packets transmitted by the Session-Reflector.
Round-Trip Delay
The round-trip delay is the length of time it takes for a packet to be sent plus the length of time it takes
for an acknowledgment of that packet to be received. The round-trip delay indicates the delay in a
transmission network.
Delay Variation
The delay variation indicates the difference between delays of selected packets on an IP link.
| 9 May 2018 | 6
TWAMP Application
TWAMP applies to the following interfaces:
• GSM interfaces: Abis, A, and Gb.

• UMTS interfaces: Iub, Iu, Iur, and uX2.
• LTE interface: S1, X2 and eX2.
The working principles of TWAMP on these interfaces are the same.
TWAMP uses the combination of source IP address, destination IP address, source UDP port number,
destination UDP port number, and DSCP to identify a transmission link.
| 9 May 2018 | 7
Differences Between TWAMP and Huawei-
Private IP PM
Technical Differences
Application Differences
| 9 May 2018 | 8
Both TWAMP and Huawei-private IP PM measure the transmission quality in real time. Huawei-private
IP PM is recommended if both ends use Huawei devices, for example, between a Huawei base station
and a Huawei base station controller, between a Huawei eNodeB and a Huawei S-GW, and between
two Huawei base stations. TWAMP is recommended if devices provided by different vendors are used
at the two ends, for example, between a Huawei base station or base station controller and a
transmission device provided by another vendor.
| 9 May 2018 | 9
Engineering Guidelines
Maximum specifications of TWAMP sessions supported by different NEs
NE Maximum Specifications of TWAMP Sessions Supported

eGBTS/NodeB/eNodeB •Session-Sender16 per board
•16 per base station
•Control-Client16 per board
•Responder4 per board
| 9 May 2018 | 10
Deployment
Requirements in these scenarios are as follows:
• The BSC6900/BSC6910 must be configured with the FG2c/FG2d/FG2e/GOUc/GOUe/GOUd/EXOUa/EXOUb to support

TWAMP.
• The base station must be configured with the GTMUc/WMPT/LMPT/UMPT/UMDU/UTRPc/UCCU/UBBPe to support
TWAMP in full mode.
• The base station must be configured with the GTMUc/LMPT/UMPT/UMDU/MDUC/UTRPc to support TWAMP in light
mode.
• Licenses for the features listed in the following table must be purchased and activated.
Feature ID Feature Name License Control Item ID License Control Item NE Sales Unit
GBFD-151201 BSC IP Active LGMIBSCTWAMP BSC IP Active BSC Per TRX
Performance Performance
Measurement Measurement
GBFD-151202 BTS IP Active LGB3TWAMP01 BTS IP Active BTS Per BTS
WRFD-151211 RNC IP Active LQW1RNCTWAMPRESE & RNC IP Active RNC Per Erl & Mbps
Performance LQW1RNCTWAMPRESM Performance
WRFD-151212 NodeB IP Active LQW9IPAPM01 NodeB IP Active NodeB Per NodeB
LOFD-070219 IP Active LT1S0IPAPM00 IP Active Performance eNodeB Per eNodeB
Performance Measurement (FDD)
Measurement
TDLOFD- IP Active LT1SIPAPM000 IP Active Performance eNodeB Per eNodeB
003018 Performance Measurement (TDD)
Measurement
| 9 May 2018 | 11
Data preparation for the TWAMP
Controller function
MO Parameter Name Parameter ID Setting Notes Data Source

TWAMPCLIENT Local IP Address LocalIP N/A Network plan
Peer IP Address PeerIP N/A Network plan
Peer TCP Port No PEERPORT N/A Network plan
Client Index ClientID N/A Network plan
VRF Index (only for base VRFINDEX N/A Network plan
stations)
Differentiated services DSCP The default value is 46. Internal plan
code point
TWAMPSENDER DSCP DSCP It is recommended that Network plan
you set this parameter to
the priority of the service
packets for which the
user shows concern.
Packet Size Type PktSizeType The default value Fixed is Internal plan
recommended.
Packet Size PktSize The default value Internal plan
is 128 bytes.
Packet Send Interval Type PktIntType The default value Internal plan
is Fixed.
Packet Interval PktInt N/A Internal plan
| 9 May 2018 | 12
Data preparation for the base station
serving as the TWAMP Responder
MO Parameter Name Parameter ID Setting Notes Data Source

TWAMPRESPONDER Local IP Address LocalIP N/A Network plan
TWAMP Architecture TWAMPARCH FULL Internal plan
Light Architecture Local LIGHTLOCALUDPPORT N/A Internal plan
UDP Port No.
Local TCP Port No LOCALPORT N/A Network plan

Responder Index ResponderID N/A Network plan
VRF Index (only for base VRFINDEX N/A Network plan
stations)
Differentiated services DSCP The default value is 46. Internal plan

code point
Negotiation Wait Time SERVWAIT The default value defined Internal plan
by the protocol 900s is
recommended.
Measurement Wait Time REFWAIT The default value defined Internal plan
by the protocol 900s is
recommended.
| 9 May 2018 | 13
Activation
To activate the TWAMP Controller function on the local end, perform the following steps:
1. Run the MML command ADD TWAMPCLIENT to set the TWAMP Control-Client, which sends
negotiation packets to establish TCP connections with the Responder, and negotiates control
information (such as DSCP and UDP ports) for test sessions.
2. Run the MML command ADD TWAMPSENDER to set the TWAMP Session-Sender, which sends test
packets and collects measurement information.
To activate the TWAMP Responder function on the local end, perform the following steps:
1. Run the MML command ADD TWAMPRESPONDER to configure the TWAMP Responder, which
responds to the negotiation packets and test packets received from the TWAMP Controller.
| 9 May 2018 | 14
MML Command Examples
| 9 May 2018 | 15
performance counters on the base
station side
| 9 May 2018 | 16
| 9 May 2018 | 17

IP Active Performance Measurement: Twamp

Uploaded by

Copyright:

Available Formats

IP Active Performance Measurement: Twamp

Uploaded by

Document Information

Original Description:

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

IP Active Performance Measurement: Twamp

Uploaded by

Copyright:

Available Formats

IP Active Performance

Optim Huawei / Youssef Nouir

IP performance measurement can be performed on connections between eNodeBs, between a

TWAMP: Two-way Active Measurement Protocol

The IP Active Performance Measurement feature provides the following benefits:

Quick transmission network performance monitoring

Quick fault diagnosis

Low maintenance costs

TWAMP deployment in full mode

TWAMP applies to the following interfaces:

• GSM interfaces: Abis, A, and Gb.

The working principles of TWAMP on these interfaces are the same.

Maximum specifications of TWAMP sessions supported by different NEs

NE Maximum Specifications of TWAMP Sessions Supported

• The BSC6900/BSC6910 must be configured with the FG2c/FG2d/FG2e/GOUc/GOUe/GOUd/EXOUa/EXOUb to support

MO Parameter Name Parameter ID Setting Notes Data Source

MO Parameter Name Parameter ID Setting Notes Data Source

Local TCP Port No LOCALPORT N/A Network plan

Differentiated services DSCP The default value is 46. Internal plan

You might also like