Ip PM (Ran14.0 - 02)

IP PM
RAN14.0
Feature Parameter Description

Issue 02
Date 2012-07-20

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
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 the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

WCDMA RAN
IP PM Contents

Issue 02 (2012-07-20) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
i

Contents
1 Introduction ................................................................................................................................ 1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History .............................................................................................................................. 1-1
2 Overview...................................................................................................................................... 2-1
3 Technical Description .............................................................................................................. 3-1
3.1 Basic Principles ............................................................................................................................. 3-1
3.2 Parameter Configurations ............................................................................................................. 3-2
3.2.1 Without an Iub Transmission Resource Pool ....................................................................... 3-2
3.2.2 With an Iub Transmission Resource Pool ............................................................................ 3-2
3.3 QoS Alarms ................................................................................................................................... 3-2
3.3.1 Without an Iub Transmission Resource Pool ....................................................................... 3-2
3.3.2 With an Iub Transmission Resource Pool ............................................................................ 3-2
3.4 Application Scenarios .................................................................................................................... 3-3
4 Related Features ....................................................................................................................... 4-1
4.1 Required Features......................................................................................................................... 4-1
4.2 Mutually Exclusive Features ......................................................................................................... 4-1
4.3 Impact ............................................................................................................................................ 4-1
5 Impact on the Network............................................................................................................. 5-1
5.1 Impact on System Capacity........................................................................................................... 5-1
5.2 Impact on Network Performance ................................................................................................... 5-1
6 Engineering Guidelines ........................................................................................................... 6-1
6.1 When to Use IP PM ....................................................................................................................... 6-1
6.2 Information to Be Collected ........................................................................................................... 6-1
6.3 Network Planning .......................................................................................................................... 6-1
6.3.1 Network Topology ................................................................................................................. 6-1
6.3.2 Hardware Planning ............................................................................................................... 6-1
6.4 Overall Deployment Procedure ..................................................................................................... 6-1
6.5 Deploying IP PM ............................................................................................................................ 6-1
6.5.1 Deployment Requirements ................................................................................................... 6-1
6.5.2 Data Preparation................................................................................................................... 6-2
6.5.3 Precautions ........................................................................................................................... 6-3
6.5.4 Feature Activation ................................................................................................................. 6-3
6.5.5 Activation Observation .......................................................................................................... 6-3
6.5.6 IP PM Adjustment ............................................................................................................... 6-13
6.5.7 Deactivation ........................................................................................................................ 6-13
6.6 Troubleshooting ........................................................................................................................... 6-14
WCDMA RAN
IP PM Contents

ii

7 Parameters.................................................................................................................................. 7-1
8 Counters ...................................................................................................................................... 8-1
9 Glossary ...................................................................................................................................... 9-1
10 Reference Documents ......................................................................................................... 10-1

WCDMA RAN
IP PM 1 Introduction

1-1

1 Introduction
1.1 Scope
This document describes the Internet Protocol (IP) performance monitoring (PM) feature on the RNC
and NodeB sides, including basic principles, feature dependencies, network impact, engineering
guidelines, and parameters.
1.2 Intended Audience
This document is intended for:
Personnel who are familiar with UMTS basics
Personnel who need to understand IP PM
Personnel who work with Huawei products
1.3 Change History
This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
Feature change: refers to a change in the IP PM feature of a specific product version
Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version
Document Issues
The document issues are as follows:
02 (2012-07-20)
01 (2012-04-30)
Draft A (2012-02-15)
02 (2012-07-20)
This is the document for the second commercial release of RAN14.0.
Compared with 01 (2012-04-30), issue 01 (2012-04-30) incorporates the changes described in the
following table.
Change
Type
Change Description Parameter Change
Feature
change
None None
Editorial
change
Added descriptions of scenarios where Iub interface
boards form a transmission resource pool in the RNC.
None
Optimized the description in section 6.3.2 "Hardware
Planning."
None
In chapter 8 "Counters", added performance counters and
related descriptions.
None

WCDMA RAN
IP PM 1 Introduction

1-2

01 (2012-04-30)
This is the document for the first commercial release of RAN14.0.
Compared with issue Draft A (2012-02-15) of RAN14.0, this issue has no change.
Draft A (2012-02-15)
This is the first draft of the document for RAN14.0.
This document is split from the IP Transport Architecture Feature Parameter Description. Compared with
the IP Transport Architecture Feature Parameter Description released in issue 01 (2011-03-30) of
RAN13.0, this document incorporates the changes described in the following table.
WCDMA RAN
IP PM 2 Overview

2-1

2 Overview
When IP transmission applies to the transport network between the RNC and NodeB, the bandwidth of
transmission links between the two nodes is often unstable. Huawei introduces the IP PM feature to
monitor the quality of service (QoS) for the IP transport network in real time.
IP PM uses a Huawei proprietary protocol to monitor the QoS of an end-to-end IP network through the
following parameters: delay, jitter, and packet loss rate.
IP PM must be supported by both the RNC and NodeB.
WCDMA RAN
IP PM 3 Technical Description

3-1

3 Technical Description
3.1 Basic Principles
IP PM uses Forward Monitoring (FM) and Backward Reporting (BR) frames. With FM and BR frames, IP
PM calculates the delay, jitter, and packet loss rate for an IP path. Figure 3-1 shows the working
principle of IP PM.
Figure 3-1 Working principle of IP PM

IP PM works as follows:
The local end (shown as A in Figure 3-1) periodically sends the peer end (shown as B in Figure 3-1) an
FM frame, which includes the number of service packets transmitted within the current monitoring
period (equal to the monitoring interval), number of bytes in these service packets, and the time this
FM frame was sent.
Upon receiving an FM frame, B records the receive time and calculates the number of service packets
received within the current monitoring period and number of bytes in these service packets. Then B
includes the receive time and calculation results in a BR frame along with the transmit time of the BR
frame.
A calculates the delay, jitter, and packet loss rate based on the data contained in the BR frame.
If the RNC triggers IP PM, the RNC checks the QoS for downlink transmission. If the NodeB triggers IP
PM, the NodeB checks the QoS for uplink transmission. In this document, the direction from the RNC to
NodeB is called downlink and the opposite direction is called uplink.
Table 3-1 provides the commands and parameters for setting the IP PM monitoring interval.
Table 3-1 Commands and parameters for setting the IP PM monitoring interval
Is There an Iub Transmission
Resource Pool in the RNC?
Direction Command Parameter
No Downlink ACT IPPM PMPRD
Uplink The monitoring interval is 100 ms and is not
configurable.
Yes Uplink or
downlink
ACT IPPOOLPM PMPRD

WCDMA RAN

3-2

3.2 Parameter Configurations
3.2.1 Without an Iub Transmission Resource Pool
IP PM can be activated on the RNC by running the ACT IPPM command and can be activated on the
NodeB by running the ADD IPPMSESSION command. IP PM is activated on the NodeB by default after
an IP path is configured on the NodeB side. IP PM takes effect only after IP paths have been set up
between the RNC and NodeB.
To activate IP PM for an IP path, perform the following steps:
Step 1 On the RNC side, run the ACT IPPM command with ANI and PATHID specified. If the target IP
path is a QoS path, specify PHB and set ISQOSPATH to YES.
Step 2 On the NodeB side, run the ADD IPPMSESSION command with PATHID specified.
----End
3.2.2 With an Iub Transmission Resource Pool
To activate IP PM for an RNC, configure the adjacent node, source IP address, and destination IP
address. For details, see Transmission Resource Pool in RNC Feature Parameter Description.
3.3 QoS Alarms
3.3.1 Without an Iub Transmission Resource Pool
If the QoS of an IP transport network deteriorates:
On the RNC side: After detecting that the packet loss rate over an IP path exceeds the threshold
specified by the LOSTPKTALARMTHD parameter in the ACT IPPM command, the RNC reports
ALM-21352 IP Path Excessive Packet Loss Rate.

The RNC can report the preceding alarm only when LOSTPKTDETECTSW is set to ON(ON).
On the NodeB side: After detecting that the packet loss rate over an IP path exceeds the threshold
specified by the PLRAT parameter in the SET PLRTHRESHOLD command, the NodeB reports
ALM-25898 IP Path Excessive Packet Loss Rate. After detecting that the packet loss rate over an IP
path is lower than the threshold specified by the PLRDT parameter, ALM-25898 IP Path Excessive
Packet Loss Rate is cleared.

Whether the NodeB reports the preceding alarm is not under switch control.
The value of PLRAT applies to all IP paths.
If active and standby routers or Ethernet ports in the intermediate transport network between the RNC
and NodeB are switched over during a measurement period, IP PM monitoring results may be
inaccurate.
3.3.2 With an Iub Transmission Resource Pool
If the QoS of an IP transport network deteriorates, the RNC reports ALM-21352 IP Path Excessive
Packet Loss Rate. For details, see Transmission Resource Pool in RNC Feature Parameter Description.
WCDMA RAN

3-3

3.4 Application Scenarios
In versions earlier than RAN14.0, the RNC and NodeB support IP PM only when IP over FE/GE is
applied, and IP PM is referred to as IP PM V1.
In RAN14.0, the NodeB supports IP PM when IP over E1/T1 is applied, the RNC supports IP PM when
link aggregation groups (LAGs) work in active/standby mode, and IP PM is referred to as IP PM V2.
IP PM V2 is compatible with IP PM V1. If IP PM V2 is used on one end but IP PM V1 is used on the other
end, functions of only IP PM V1 can be used.
Table 3-2 describes the usage scenarios of IP PM.
Table 3-2 Application scenarios of IP PM
Scenario IP PM V1 IP PM V2 Remarks
RNC NodeB
IP over FE/GE is applied to the Iub
interface.
Supported Supported None
IP over FE/GE is
applied to the
RNC.
IP over E1/T1 is
applied to the
NodeB.
Not
supported
Supported None
- IPSec is enabled on
the NodeB.
Not involved Supported None
- A Universal
Transmission
Processing unit
(UTRP) board is
used in a
single-mode base
station.
Supported Supported IP PM must be activated on the
UTRP or UTRPc board.
- A UTRP board is
used in a multimode
base station
(MBTS).
Supported Supported
IP PM must be activated on the
UTRP or UTRPc board
configured for the primary mode
of the MBTS. For the other
modes of the base station, do
not activate IP PM.
- NodeBs are
cascaded.
Supported Supported IP PM can be activated on each
NodeB.
- Two BBUs are
interconnected.
Not
supported
Supported N/A
IP over E1/T1 is
applied to the
RNC.
- Not
supported
Not
supported
None
Ethernet ports
on the RNC work
in active/standby
mode.
- Supported Supported None
WCDMA RAN

3-4

LAGs on the
RNC work in
active/standby
mode.
- Not
supported
Supported None
Route-based
load sharing is
applied to
Ethernet ports
on the RNC.
- Not
supported
Not
supported
None
LAGs over the
RNC interface
boards work in
load sharing
mode and these
interface boards
do not form
transmission
resource pools.
- Not
supported
Not
supported
None
RNC interface
boards form
transmission
resource pools
and links carried
over ports on
these boards do
not form LAGs.
- Not involved Supported None
RNC interface
boards form
transmission
resource pools
and links carried
over ports on
each of these
boards form
LAGs.
- Not involved Supported None
RNC interface
boards form
transmission
resource pools
and links carried
over ports on
these boards
form inter-board
LAGs. In
addition, these
LAGs work in
active/standby
mode.
- Not involved Not
supported
None
WCDMA RAN

3-5

RNC interface
boards form
transmission
resource pools
and links carried
over ports on
these boards
form inter-board
LAGs. In
addition, these
LAGs work in
load sharing
mode.
- Not involved Not
supported
None

For details about the primary and other modes of an MBTS, see Common Transmission Feature
Parameter Description.
WCDMA RAN
IP PM 4 Related Features

4-1

4 Related Features
4.1 Required Features
IP PM depends on the WRFD-050402 IP Transmission Introduction on Iub Interface feature.
4.2 Mutually Exclusive Features
No feature is mutually exclusive with IP PM.
4.3 Impact
Activating the WRFD-140208 Iub Transmission Resource Pool in RNC feature has the following impact
on IP PM:
On the RNC side, you must configure the adjacent node, source IP address, and destination IP
address to activate IP PM.
On the NodeB side, the NodeB cannot trigger IP PM because the NodeB does not know the service IP
address of the RNC. Only the RNC can trigger IP PM and calculate the delay, jitter, and packet loss
rate.
For details, see Transmission Resource Pool in RNC Feature Parameter Description.
WCDMA RAN
IP PM 5 Impact on the Network

5-1

5 Impact on the Network
5.1 Impact on System Capacity
There are no impacts on system capacity.
5.2 Impact on Network Performance
Due to the introduction of FM and BR frames, IP PM occupies extra bandwidth of lower than 10 kbit/s
over an IP path.
WCDMA RAN
IP PM 6 Engineering Guidelines

6-1

6 Engineering Guidelines
6.1 When to Use IP PM
Use IP PM when the following conditions are met:
IP transmission applies to the transport network between the RNC and NodeB.
Bandwidth resources allocated for data exchange between the RNC and NodeB are sufficient.
The PS data rate fluctuates.
If the bandwidth resources allocated for data exchange between the RNC and NodeB are not
guaranteed, you can temporarily use IP PM when locating the cause of PS data rate fluctuation.
6.2 Information to Be Collected
No information needs to be collected before activating the feature.
6.3 Network Planning
6.3.1 Network Topology
Not involved
6.3.2 Hardware Planning
Plan hardware as follows:
On the RNC side
For the BSC6900, GOUc or FG2c boards must be configured.

GOUc or FG2c boards can work only with IP PM V1.
For GOUc and FG2c boards, IP PM can be triggered over a maximum of 4000 data flows. For GOUa and FG2a boards, IP
PM can be triggered over a maximum of 1200 data flows.
Without an Iub transmission resource pool, one IP path corresponds to a data flow. With an Iub transmission resource
pool, one pair of IP addresses and a DSCP value specify a data flow.
On the NodeB side
UTRP, UTRPc, WMPT, or UMPTa1 boards must be configured.

BTS3902Es and 3900 series base stations can work with IP PM V2. DBS3800s can work with IP PM V1.
On the NodeB, IP PM can be triggered over a maximum of 16 data flows.
6.4 Overall Deployment Procedure
Not involved
6.5 Deploying IP PM
6.5.1 Deployment Requirements
The requirements for deploying IP PM on the RNC and NodeB are as follows:
The transport network between the RNC and NodeB uses the IP transmission scheme.
The RNC and NodeB support IP PM.
WCDMA RAN

6-2

The DSCP value cannot be changed by any intermediate devices.
6.5.2 Data Preparation
Table 6-1 Without an Iub transmission resource pool
Parameter
Name
Parameter ID Remarks Data Source
Adjacent node
ID
ANI - Internal RNC
data plan
IP path ID PATHID - Internal RNC
data plan
IS QOSPATH ISQOSPATH - Internal RNC
data plan
PHB PHB -
Internal RNC
data plan
IPPM packet
send period
PMPRD The default value is recommended. Internal RNC
data plan
Lost-Packet
Detect Switch
LOSTPKTDETECTSW The recommended value is ON. Internal RNC
data plan
IP Path ID PATHID - Internal NodeB
data plan

Table 6-2 With an Iub transmission resource pool
Parameter
Name
Adjacent Node
ID
ANI - Internal RNC
data plan
Sip Type SIPTYPE Set this parameter to ASSIGN_ONE_SIP
when locating faults.
Internal RNC
data plan
PHB PHB - Internal RNC
data plan
Activation
Direction
DR

Set this parameter to SINK when
checking the QoS for uplink transmission.

Set this parameter to SOURCE when
checking the QoS for downlink
transmission.

Set this parameter to BOTH when
checking the QoS for both uplink and
downlink transmission.
Internal RNC
data plan
Lost-Packet
Detect Switch
LOSTPKTDETECT
SW
The recommended value is ON. Internal RNC
data plan
FM packet send PMPRD The default value is recommended. Internal RNC
WCDMA RAN

6-3

Parameter
Name
period data plan

6.5.3 Precautions
The precautions for deploying IP PM are as follows:
The RNC and NodeB must use the same DSCP value for the same IP path. Otherwise, IP PM will not
work.
The DSCP value must not be changed by any intermediate device between the RNC and NodeB
because the RNC and NodeB summarize the calculation results of the three QoS parameters by
DSCP value. If the DSCP value is changed, IP PM will not work.
When configuring an IP path on the RNC side, set PEERIPADDR to 255.255.255.255. Otherwise, IP
PM cannot be activated.
6.5.4 Feature Activation
IP PM can be activated in the uplink by using either the CME or MML commands and in the downlink by
using MML commands.
Using the CME
Load a CME configuration file. After the file is loaded, IP PM is activated in the uplink by default.
Using MML Commands
Without an Iub transmission resource pool
Activate IP PM as follows:
Run the ACT IPPM command on the RNC LMT to activate IP PM in the downlink. For the NodeB, no
configurations are required because the NodeB automatically responds to FM frames.
Run the ADD IPPMSESSION command on the NodeB LMT to activate IP PM in the uplink. For the
RNC, no configurations are required because the RNC automatically responds to FM frames.
With an Iub transmission resource pool
IP PM in the downlink: Run the ACT IPPOOLPM command on the RNC LMT with DR set to
SOURCE. For the NodeB, no configurations are required because the NodeB automatically responds
to FM frames.
IP PM in the uplink: Run the ACT IPPOOLPM command on the RNC LMT with DR set to SINK. For
the NodeB, no configurations are required because the NodeB automatically sends FM frames.
IP PM in the uplink and downlink: Run the ACT IPPOOLPM command on the RNC LMT with DR set
to BOTH. For the NodeB, no configurations are required because the NodeB automatically responds
to and sends FM frames.
6.5.5 Activation Observation
After activating IP PM, users can query the QoS of the transport network between the RNC and NodeB
by running MML commands, starting monitoring tasks on the LMT, or checking values of QoS-related
counters on the M2000.
MML commands: are used to check the operating status of IP PM and to check whether IP PM has
been activated.
WCDMA RAN

6-4

LMT GUI: On the LMT, you can check the QoS of an IP transport network in real time. The NodeB
exports monitoring results every 1s by default, and the RNC exports monitoring results every 5s by
default.
QoS-related counters: The measurement period of QoS-related counters on the M2000 can be
specified. The shortest measurement period is 5 minutes. However, 5- and 15-minute measurements
lead to a high CPU usage and capacity on the M2000. Therefore, you are advised to set the
measurement period to 5 or 15 minutes only when you are troubleshooting emergencies.
Running MML Commands
The following table provides the MML commands for querying the QoS of the transport network between
the RNC and NodeB.
Downlink Uplink
No DSP IPPM command on the
RNC LMT
DSP IPPMSESSION command
on the NodeB LMT
Yes DSP IPPOOLPM command on the RNC LMT

Starting Monitoring Tasks on the LMT
Without an Iub transmission resource pool
Downlink transmission
1. Log in to the RNC LMT and click the Monitor tab.
2. In Monitor Navigation Tree, choose Monitor > Common Monitoring > Link Performance
Monitoring.
3. In the displayed Link Performance Monitoring dialog box, choose IPPM from the Monitor Item
drop-down list box and choose a value from the Subrack No. drop-down list box. Enter a value in the
Adjacent Node ID and IP Path Symbol fields and click Submit. Figure 6-1 shows the results of
operations described in steps 1 through 3.
WCDMA RAN

6-5

Figure 6-1 Operation results

----End
Uplink transmission
1. Log in to the NodeB LMT and click the Maintenance tab.
2. Choose Realtime Specific Monitoring > IUB Link Flux Stat Monitoring.
3. In the displayed IUB Link Flux Stat Monitoring dialog box, choose IP from the Protocol Type
drop-down combo box and select the Include IPPM Statistic check box under Parameter Setting.
Under IP Parameter, select the IPPATH1 check box and enter a value in the PATHID field, which is
on the right side of IPPATH1. Figure 6-2 shows the results of operations described in steps 2 and 3.
WCDMA RAN

6-6


The number of check boxes, such as IPPATH1, depends on the number of IP paths configured for the corresponding slot.
All the related PATHID fields must be filled in.
----End
With an Iub transmission resource pool
You can check the QoS for uplink and downlink transmission on the RNC LMT.
To check the QoS, repeat steps for downlink transmission in the scenario "Without an Iub transmission
resource pool." Note that you must choose IPPOOL PM from the Monitor Item drop-down list box in the
displayed Link Performance Monitoring dialog box. Figure 6-3 shows the operation results.
WCDMA RAN

6-7


Querying QoS Counter Values on the M2000

The following description takes RNC counter values as examples.
To query QoS counter values for downlink transmission, perform the following steps:
Step 1 Log in to the M2000 and choose Performance > Measurement Management.
Step 2 In the navigation tree, expand a node (for example, BSC6900 UMTS) and Measurements
related to Transport layer Link (uni,ima,fra,atm) displayed underneath the node. Right-click
Measurement Related to IPPM and choose Active Measurement from the shortcut menu. On
the displayed Measurement Status tab page, select a management object (for example,
185.22.61.13-zq) under UMTS TRANSMISSION. Figure 6-4 shows the results of operations
described in this step.
WCDMA RAN

6-8


To query QoS counter values for uplink transmission, choose the NodeB in question and perform the
preceding steps.

If Iub interface boards do not form an Iub transmission resource pool in the RNC, the RNC and NodeB calculate QoS
counter values for downlink transmission and uplink transmission, respectively.
If Iub interface boards form an Iub transmission resource pool in the RNC, the RNC calculates QoS counter values for
both uplink and downlink transmission.
Step 3 In the displayed Active dialog box, click the 5 Minutes check box under Period, select the
management object under Range, and select Measurement Related to IPPM under Search.
Figure 6-5 shows the results of operations described in this step.
WCDMA RAN

6-9


Step 4 On the Measurement Status tab page, right-click in the blank area and choose Refresh from
the shortcut menu. Figure 6-6 shows the results of operations described in this step.
WCDMA RAN

6-10


Step 5 Choose Performance > Query Result. Figure 6-7 shows the results of operations described in
this step.

WCDMA RAN

6-11

Step 6 In the displayed Query Result dialog box, select an IP path under Available Objects on the
Object Settings tab page, and click > and Query. Figure 6-8 shows the results of operations

Step 7 Click the Counter Settings tab, select the counter whose value needs to be queried, and click >.
Figure 6-9 shows the results of operations described in this step.
WCDMA RAN

6-12


Step 8 Click the Other Settings tab, set items under Time Mode, Date Range, Period, and Sort
according to user requirements, and click Query. Figure 6-10 shows the results of operations
WCDMA RAN

6-13


----End
6.5.6 IP PM Adjustment
IP PM does not need to be adjusted.
6.5.7 Deactivation
Deactivate IP PM when either of the following conditions is met:
The QoS of the transport network between the RNC and NodeB does not need to be monitored.
Exceptions occur during IP PM measurement.
The following table provides MML commands for deactivating IP PM in the uplink and downlink.
WCDMA RAN

6-14

Downlink Uplink
No DEA IPPM command on the
RNC LMT
RMV IPPMSESSION command
on the NodeB LMT
Yes DEA IPPOOLPM command on the RNC LMT

6.6 Troubleshooting
Alarms are generated when either of the following conditions is met:
IP PM fails to be activated.
A DSCP value is changed by an intermediate device in the transport network between the RNC and
NodeB.
Table 6-3 provides the alarms generated if IP PM fails to be activated.
Table 6-3 Alarms generated if IP PM fails to be activated
Downlink Uplink
No ALM-21341 IP PM Activation
Failure by the RNC
ALM-25900 IP PM Activation
Failure by the NodeB
Yes ALM-21341 IP PM Activation Failure by the RNC

WCDMA RAN
IP PM 7 Parameters

7-1

7 Parameters
Table 7-1 Parameter description
Parameter ID NE MML Command Feature ID Feature Name Description
PATHID NodeB ADD
IPPMSESSION
WRFD-050402 IP Transmission
Introduction on
Iub Interface
Meaning:Indicates the ID
of the IP path to which an
IP PM session is bound.
GUI Value
Range:0~65535
Actual Value
Range:0~65535
Unit:None
Default Value:None
PEERIPADDR BSC6900 ADD IPPATH GBFD-118605
WRFD-050402
WRFD-050403
WRFD-050404
IP QOS
IP Transmission
Introduction on
Iub Interface
Hybrid Iub IP
Transmission
ATM/IP Dual
Stack Node B
Meaning: The peer IP
address should not be
the same as the local
address.
GUI Value Range: None
Actual Value Range:
0.0.0.0~255.255.255.255
Unit: None
Default Value: None
PLRAT NodeB SET
PLRTHRESHOLD
Introduction on
Iub Interface
Meaning:Indicates the
threshold above which
the packet loss alarm is
generated on an IP path.
When the packet loss
rate of an IP path
exceeds the threshold,
generated on the IP path.
GUI Value Range:0~100
Actual Value
Range:0~100
Unit:per mill
Default Value: None
PLRDT NodeB SET
PLRTHRESHOLD
Introduction on
Iub Interface
Meaning: Indicates the
threshold below which
cleared on an IP path.
When the packet loss
rate of an IP path does
not exceed the threshold,
WCDMA RAN
IP PM 7 Parameters

7-2

Parameter ID NE MML Command Feature ID Feature Name Description
cleared on the IP path.
GUI Value Range: 0~100
Actual Value Range:
0~100
Unit: per mill
Default Value: None

WCDMA RAN
IP PM 8 Counters

8-1

8 Counters
Table 8-1 RNC performance counters (without an Iub transmission resource pool)
Counter ID Counter Name Description
67192968 VS.IPPM.MaxRttDelay Maximum RTT Delay of IPPM
67204117 VS.IPPM.Bits.MeansTx Average TX Bit Rate of IPPM
67204118 VS.IPPM.Pkts.MeansTx Average TX Packet Rate of IPPM
67204119 VS.IPPM.Peak.Bits.RateTx Peak TX Bit Rate of IPPM
67204120 VS.IPPM.Peak.Pkts.RateTx Peak TX Packet Rate of IPPM
67204121 VS.IPPM.Peer.Bits.MeansRx Average RX Bit Rate of IPPM
67204122 VS.IPPM.Peer.Pkts.MeansRx Average RX Packet Rate of Peer End of
IPPM
67204123 VS.IPPM.Peer.Peak.Bits.RateRx Peak RX Bit Rate of Peer End of IPPM
67204124 VS.IPPM.Peer.Peak.Pkts.RateRx Peak RX Packet Rate of Peer End of
IPPM
67204127 VS.IPPM.Forword.DropMeans Average Forward Packet Loss Rate of
IPPM
67204128 VS.IPPM.Forword.Peak.DropRates Peak Forward Packet Loss Rate of IPPM
67204131 VS.IPPM.Forward.JitterStandardDeviation Forward Jitter Standard Deviation of IPPM
67204132 VS.IPPM.Rtt.Means Average RTT Delay of IPPM
67204731 VS.IPPM.Back.JitterStandardDeviation Backward Jitter Standard Deviation of
IPPM
73441211 VS.IPPM.Forward.Precise.Peak.DropRate
s
High-Precision Peak Forward Packet Loss
Rate of IPPM

If the peer NodeB is a DBS3800 series or BTS3812E series base station, the value of VS.IPPM.Forword.DropMeans may
not be reported as expected. Therefore, you are not advised to use the value of this counter as a unique condition for
determining packet loss during transmission.

Table 8-2 NodeB performance counters (without an Iub transmission resource pool)
1542455408 VS.IPPM.Bits.MeansTx Average bit transmit rate on the IP PM
1542455409 VS.IPPM.Pkts.MeansTx Average packet transmit rate on the IP
PM
1542455410 VS.IPPM.Peak.Bits.RateTx Peak bit transmit rate on the IP PM
1542455411 VS.IPPM.Peak.Pkts.RateTx Peak packet transmit rate on the IP PM
WCDMA RAN
IP PM 8 Counters

8-2

1542455412 VS.IPPM.Peer.Bits.MeansRx Average peer bit receive rate on the IP
PM
1542455413 VS.IPPM.Peer.Pkts.MeansRx Average peer packet receive rate on the
IP PM
1542455414 VS.IPPM.Peer.Peak.Bits.RateRx Peak peer bit receive rate on the IP PM
1542455415 VS.IPPM.Peer.Peak.Pkts.RateRx IPeak peer packet receive rate on the IP
PM
1542455416 VS.IPPM.Forword.DropMeans Average forward packet loss rate on the
IP PM
1542455417 VS.IPPM.Forword.Peak.DropRates Peak forward packet loss rate on the IP
PM
1542455418 VS.IPPM.Forward.JitterStandardDeviation Standard deviation of forward jitter on
the IP PM
1542455419 VS.IPPM.Back.JitterStandardDeviation Standard deviation of backward jitter on
the IP PM
1542455420 VS.IPPM.Rtt.Means Average RTT on the IP PM
1542455421 VS.IPPM.MaxRttDelay Maximum RTT on the IP PM
1542455452 VS.IPPM.MinRttDelay Minimum RTT on the IP PM

Table 8-3 Performance counters (with an Iub transmission resource pool)
73441257 VS.IPPOOL.IPPM.ForwardBits.MeansTx Average Forward Transmit Bit Rate of
Transmission Resource Pool IPPM
73441259 VS.IPPOOL.IPPM.Peak.ForwardBits.Rate
Tx
Maximum Forward Transmit Bit Rate of
73441264 VS.IPPOOL.IPPM.BackwardBits.MeansTx Average Backward Transmit Bit Rate of
73441266 VS.IPPOOL.IPPM.Peak.BackwardBits.Rat
eTx
Maximum Backward Transmit Bit Rate
of Transmission Resource Pool IPPM
73441258 VS.IPPOOL.IPPM.ForwardPkts.MeansTx Average Forward Transmit Packet Rate
73441260 VS.IPPOOL.IPPM.Peak.ForwardPkts.Rate
Tx
Maximum Forward Transmit Packet
Rate of Transmission Resource Pool
IPPM
73441265 VS.IPPOOL.IPPM.BackwardPkts.MeansTx Average Backward Transmit Packet
IPPM
WCDMA RAN
IP PM 8 Counters

8-3

73441267 VS.IPPOOL.IPPM.Peak.BackwardPkts.Rat
eTx
Maximum Backward Transmit Packet
IPPM
73441261 VS.IPPOOL.IPPM.Forward.DropMeans Average Forward Packet Loss Rate of
73441522 VS.IPPOOL.IPPM.Forward.Peak.DropRate
s
Maximum Forward Packet Loss Rate of
73441268 VS.IPPOOL.IPPM.Backward.DropMeans Average Backward Packet Loss Rate of
73441523 VS.IPPOOL.IPPM.Backward.Peak.DropRa
tes
Maximum Backward Packet Loss Rate
73424341 VS.IPPOOL.IPPM.Forward.JitterMax Maximum Forward Jitter of
73441262 VS.IPPOOL.IPPM.Forward.JitterStandard
Deviation
Forward Jitter Standard Deviation of
73441263 VS.IPPOOL.IPPM.Rtt.Means Average RTT Delay of Transmission
Resource Pool IPPM
73424342 VS.IPPOOL.IPPM.MaxRttDelay Maximum RTT Delay of Transmission
Resource Pool IPPM
WCDMA RAN
IP PM 9 Glossary

9-1

9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
WCDMA RAN
IP PM 10 Reference Documents

10-1

10 Reference Documents
[1] Common Transmission Feature Parameter Description
[2] IP Transport Architecture Feature Parameter Description

Ip PM (Ran14.0 - 02)

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

Ip PM (Ran14.0 - 02)

Uploaded by

Copyright:

Available Formats

IP PM

You might also like