Definition, Configuration and
Reporting of PM Counters for Iuh
15 December 2015
Document Version: 3.0
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Ref: USC-44-12-002
EDCS-1538715
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE
WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO
BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE
FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE
INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE.
IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO
REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of
California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved.
Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS
ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES,
EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING
OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses
and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in
the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative
content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should
be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other
countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks
mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
© 2015 Cisco Systems, Inc. All rights reserved.
Contents
1
SCOPE ........................................................................................................................................ 4
2
REFERE NCES ............................................................................................................................ 4
3
ABBREVIATIONS ....................................................................................................................... 4
4
OVERVIEW ................................................................................................................................. 5
5
THE PM FILE .............................................................................................................................. 5
5.1
PM FILE NAMIN G .................................................................................................................... 5
5.2
PM FILE F ORMAT .................................................................................................................... 5
5.2.1
Further Information Included in the XML File .................................................................. 7
5.3
FILE S IZE E STIM ATES .............................................................................................................. 7
5.3.1
PM File Compression..................................................................................................... 8
6
MEASUREMENT CO NTROL....................................................................................................... 8
6.1
REPORT ING PM FILES ............................................................................................................. 8
6.1.1
Enabling Reporting and Uploading of PM Files............................................................... 8
6.1.2
Configuration of PMS ..................................................................................................... 8
6.1.3
The Reporting Process................................................................................................... 9
6.2
T HE COLLECTION P R OCESS ................................................................................................... 10
6.2.1
Override Collection Period ........................................................................................... 11
6.2.2
Counters Sa mpling ...................................................................................................... 11
6.2.3
Me mory Availability for Storage of PM Data.................................................................. 11
7
ADDI TIONAL INFORM ATIO N ................................................................................................... 12
7.1
PM COMMENT B LOCK ............................................................................................................ 12
7.1.1
Alarm Status ................................................................................................................ 12
7.1.2
Histograms .................................................................................................................. 13
7.1.3
Further Co mment Types .............................................................................................. 14
7.2
PM COMMENT B LOCK ............................................................................................................ 15
8
PM COUNTE RS ........................................................................................................................ 34
ANNEX A – CHANGE HIS TO RY ...................................................................................................... 35
▄ Definition, Configuration and Reporting of PM Counters for Iuh
iii
USC-44-12-002
▀ Scope
1 Scope
This document describes the performance management functionality that is supported by the Cisco
Universal Small Cell solution as part of R3.8 TR-196 specification defines the part of the means to
manage the collection of performance measurements, but this document describes the Cisco
implementation and extensions to this specification.
This document contains information relating to product that is rated as dual use controlled technology.
Note: It is recommended that Export Control advice is taken before onward forwarding of this document
or its contents.
2 References
The following references are used in this document.
[1]
TR-196 Femto Access Point Service Data Model
[2]
TS32.401 PM Concept and requirements
[3]
TS32.404 PM Definitions and template
[4]
TS32.432 PM File format definition
[5]
TS32.435 PM eXtensible Markup Language (XML) file format definition
[6]
TS32.452 Performance measurements Home Node B Access (HNB) network
[7]
TS32.581 HNB OAM&P; Concepts and Requirement Type 1 interface HNB to HMS
[8]
TS32.582 HNB OAM&P; Information model for Type 1 interface HNB to HMS
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
HMS
HNB
KPI
PM
PMS
QoS
UE
UL
USC
WCDMA
Automatic Configuration System
Access Point
Key Performance Indicator
Performance Management
Performance Management Server
Quality of Service
User Equipment
Uplink
Universal Small Cell aka HNB
Wideband Code Division Multiple Access
▄ Definition, Configuration and Reporting of PM Counters for Iuh
4
USC-44-12-002
▀ Overview
4 Overview
The Cisco Universal Small Cell (referred to throughout this document as an HNB) supports the
collection and upload to a PM server of performance metrics. The metrics are collected and added to a
performance report. The HNB will peg these metrics to pre-defined intervals and place them into an
XML encoded file. At the end of the performance reporting interval the HNB will close the report. The
HNB will then open a new report and start collecting performance information for the next period.
5 The PM File
5.1 PM File Naming
The naming convention is compliant to TS32.432 as follows:
<Type><Startdate>.<Starttime>-[<Enddate>.]<Endtime> [_-<jobId> ][_< UniqueId> ][_-_<RC>]
With the following assumptions, based on sect 5.1.2 [TS 32.432]:
•
The Type Field use “A” or “C”:
o An “A” type filename is normally obtained when the file only contains a single granularity
period, and the “C” filename is used when there are multiple granularity periods.
o There is a special case where the “C” type filename is used but there is only one granularity
period. This happens when the pegging interval crosses midnight. The “C” filename therefore
is used to capture the different start and end days.
•
The <Startdate> and <Starttime> in the filename are the value of the beginTime in the fileHeader
section of the XML file
•
The <Enddate> and <Endtime> in the filename are the value of the endTime in the fileFooter
section of the XML file
•
The JobID can be optionally configured from HMS
•
The UniqueId will be OUI/SerialNumber of the HNB
•
The optional RC parameter (running count) is not used
A typical example is:
A20120717.1801+0100-1900+0100_001B67-357539010392740.xml.gzip
Note:
The <Starttime> and <Endtime> are rounded to the nearest 1minute. The Specification in [TS
32.432] rounds the value to the nearest 5 minute.
The UniqueID includes the OUI/SerialNumber pair (001B67-357539010392740)
5.2 PM File Format
The file format uses XML follows the XML description from 3GPP TS32.581 [7] and associated
specifications, according to the following document hierarchy of referencing:
•
[2] TS32.401 PM Concept and requirements

[4] TS32.432 PM File format definition
▄ Definition, Configuration and Reporting of PM Counters for Iuh
5
USC-44-12-002
▀ The PM File
•
[5] TS32.435 PM eXtensible Markup Language (XML) file format
definition
Note that the Iuh releases uses Release 9 of the 3GPP PM file format specifications.
A generic example of the PM file XML structure is shown below. However, please note:
The actual content of the DNPrefix value is defined by the RMS (i.e. operator-defined format and
content) and is configured to the 3G HNB during the provisioning period. Therefore, its exact format
and content is not defined in this document. However, as an example, the format is expected to look
something like the following:
<DNPrefix> = “ HNB-GW=<value>, Site=<value>, CLLI=<CLLI>, Chassis ID=<value>, EID=<value>”
HNB-GW value:
HNB-GW name and/or value
Site value:
Site name and/or value
Chassis ID value:
Chassis ID as in X_UBIQUISYS_COM_ChassisSN
EID value:
Module S/N as in InternetGatewayDevice.DeviceInfo.Seria lNumber (TR-098)
Note: From R3.5 onwards in case device-unique identity(ies) is/are a part of the DNPrefix, then, during
the provisioning phase, the HNB first provides the value(s) to the RMS over TR-069. Then the RMS
constructs the entire DNPrefix content and configures it back to the HNB for later use.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="MeasDataCollection.x sl"?>
<measCollecFile x mlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measColl ec"
xmlns:x si="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.3gpp.org/ftp/specs/archive/32_s eri es/32.435#meas Collec">
<fileHeader fileFormatVersion="32.435 V9.0" vendorName="Ubiquisys" dnPrefix="HNBGW=,HNB-GW-SRV=CGW001BKTV2,HeNB-G W=,HeNB-G W-SRV=, SeGW=,SeGWSRV=CGW001BKTV2,Area=UK_En t_SD,Enterp rise=3,Site=2,Chassis ID=,RAT
Type=UMTS,EID=001B67-357539015675008,SecondaryID=G RID-G7-3,DeviceID=001B67357539015675008">
<fileSender localDn="local distinguished name"
elementType="RATtype=UMTS,PMversion=1.0,Deploymen tProfile=''"/>
<measCollec beginTime="2015-06-14T00:15:00+00:00"/>
</fileHeader>
<measData>
<managedElement localDn="local distinguished name" userLabel="user
label" swVersion="BV3.5.11.15"/>
<measInfo>
<job jobId="4002"/>
<granPeriod duration="PT900S" endTime="2015-0614T00:30:00+00:00"/>
<repPeriod duration="PT900S"/>
Note: After USC release R3.4.4, F5.1.15.2 [OAM Tagging Enhancements] is introduced, whereby
dnPrefix="distinguished name prefix" is filled in with the actual value configured by O&M.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
6
▀ The PM File
5.2.1 Further Information Included in the XML File
The HNB appends additional information in the PM file in the form of XML comments. Namely:
• The status of all the supported alarms
• The NeighboourListInUse, for example:
<!-- NeighborListInUse.IntraFreqCell List
PARAM:IntraFreqCellNumberOfEntries=6
INTRA_FREQ__1_PARAM:PLMNID=
INTRA_FREQ__1_PARAM:RNCID=
INTRA_FREQ__1_PARAM:CID=
INTRA_FREQ__1_PARAM:LAC=
INTRA_FREQ__1_PARAM:RAC=
INTRA_FREQ__1_PARAM:URA=
INTRA_FREQ__1_PARAM:UARFCNDL=
INTRA_FREQ__1_PARAM:PrimaryScramblingCode=
Note: Additional information from R3.5 onwards is discussed in Section 7.
5.3 File Size Estimates
An estimate for the size of uploaded files is provided in the table below. This can be used to estimate the
capacity requirements of the Upload server.
Number of
counters uploaded
Reporting period
to PMS
(See Note 1)
(See Note 2)
(See Note 3)
[Kbytes]
File Size: 45Kbytes
Daily total (96 files):
4.2Mbytes
200
350
TOTAL
15min
516
File Size: 70Kbytes
Daily total (96 files):
6.5Mbytes
File Size: 98Kbytes
(compressed
8.7Kbytes)
1hour
File Size: 144Kbytes
Daily total (24 files):
3.4Mbytes
24 hours
File Size: 242Kbytes
Daily total (24 files):
5.7Mbytes
File Size: 3.2Mbytes
Daily total (1 file):
3.2Mbytes
200
350
200
350
File Size: 5.5Mbytes
Daily total (1 file):
5.5Mbytes
▄ Definition, Configuration and Reporting of PM Counters for Iuh
7
USC-44-12-002
▀ Measurement Control
Note 1: As a guideline, in R3.8 up to 523 counters are available. These are all detailed in the PM Counter file autogenerated foreach load, for example PM_Counters_and_Description_DSV3.8.3T.33AutoGen.xls.
Note 2: The full list of reporting periods is defined elsewhere in this document; this table only provides a few
exemplary cases. A collection period of 15min is assumed in all cases.
Note 3: The “ Analytic” data reported include lists of neighbouring cells, alarms (~10Kbytes). Future analytic data
can include lists of neighbouring cells in use, handover and handover failure stats, GPS etc., increasing the
file size by a further 60Kbyte for each file per day.
5.3.1 PM File Compression
The PM file uploaded to the PM server is compressed by using the "GNU gzip”. The extension “.gzip”
is used.
6 Measurement Control
Configuration of collection of measurements and reporting of PM files involves the following steps:
•
Enabling and configuration of collection period for each PM: allowing selection of the metrics of
interests and the discrete intervals in which measurement are collected
•
Configuration of time of creation and periodic reporting of PM files: allowing control on the content
and size of the reported PM files
•
Configuration of the PMS server used for file upload
6.1 Reporting PM Files
This section provides details on the configuration of reporting and uploading of PM files.
The parameters used for configuring the reporting periods are listed within the object
InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt.
6.1.1 Enabling Reporting and Uploading of PM Files
The AP collects, generate and report the performance metric files if the parameter
.PerfMgmt.FileMgmt.PeriodicUploadEnable is set to True.
6.1.2 Configuration of PMS
The HNB upload the PM files to a Performance Management Server (PMS) configured by the HMS.
The following parameters are used:
•
6.1.2.1
.PerfMgmt.FileMgmt.URL: the destination of the upload
Supported Transfer Protocols
The PM upload server used within the USC solution supports the FTP protocol. The HNB resolves the
PMS’s FQDN (if provided) via the internal (private, behind IPSec) DNS server.
Other options such as HTTP(S) PUT and GET or FTPS are supported by the HNB, but not used by the
USC solution.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
8
▀ Measurement Control
6.1.3 The Reporting Process
The time of reporting of the PM files is configured by the parameters:
•
.PerfMgmt.FileMgmt.PeriodicUploadInterval : The duration (in seconds) of the interval for which
the HNB creates a Performance File and attempt to upload the file to URL
o
•
Currently, by default the RMS sets it to 15min for enterprise devices and 24hours for
residential devices
.PerfMgmt.FileMgmt.PeriodicUploadTime: An absolute time reference in UTC in order to
determine when the HNB will initiate the periodic file upload. Each file upload MUST occur at this
reference time plus or minus an integer multiple of the PeriodicUploadInterval.
PeriodicUploadTime is used only to set the “phase” of the periodic uploads (see definition in TR196).
The phase of the periodic upload is calculated such that the following scheduling is respected:
•
6.1.3.1
Assuming that PeriodicUploadTime is set at 20:10’:00’’
o
If PeriodicUploadInterval is set to 24h: the HNB attempts to upload the files every day, at
20:10’:00’’
o
If PeriodicUploadInterval is set to 1h: the HNB attempts to upload the files every hour at
10’:0’’ past the hour
o
If PeriodicUploadInterval is set to 15min: the HNB attempts to upload the files at 10’:0’’,
25’:0’’, 40:0’’ and 55:0’’ past the hours
Randomization of Uploading
When operating within a Cisco’s RMS environment:
•
The HNB will attempt to upload PM files at the time provided by the parameter
PeriodicUploadTime (the HNB will not apply any random delay when uploading PM files)
•
Cisco’s RMS will set a value to the parameter .PerfMgmt.FileMgmt.PeriodicUploadTime of each
served HNB, such to ensure that upload traffic is randomly spread within the
PeriodicUploadInterval at the PMS. The value set by the RMS is randomly selected within a 24h
period, independent of the upload interval, the phase calculation shown above ensure random
upload of large number of devices.
6.1.3.2
Immediate Upload
The HMS can trigger an immediate upload of the current PM file. Such forced upload is controlled by
the parameter .PerfMgmt.FileMgmt X_UBIQUISYS_COM_ForceFileSend.
When the parameter is set to True by the HMS, it triggers an immediate file upload. The HNB will also
reset the parameter to its default value (False) and create a new PM file. Note that the next file will
normally be reported at the end of the scheduled reporting period (unless a new forced upload is sent
by the HMS).
6.1.3.3
Uploading Process at Software Restart
At HNB restart (power-up, reboot or software restart) and if PM reporting is enabled, the HNB will:
•
Try to upload any PM file stored in non-volatile memory and not yet uploaded;
o
Retry and backoff mechanism of 10minutes is applied if uploading is unsuccessful
▄ Definition, Configuration and Reporting of PM Counters for Iuh
9
USC-44-12-002
▀ Measurement Control
o
•
Upload is attempted following a successful establishment of the IPSec tunnel
Created a new PM file to be reported at the next reporting period.
6.1.3.4
Unsuccessful Upload and Retention of PM Files
PM files may not be successfully uploaded to a server due to:
•
The PMS is down or un-reachable
•
The upload is stalled
The process monitors the data rate used. In case it is below 8kb/s for a period of time,
the HNB aborts the upload
o
These PM files are stored in non-volatile memory; the HNB tries to upload these files:
•
Every 10 minutes
•
At the next reporting interval
•
Following a HNB restart (as described in the previous section)
As memory protection mechanism: PM files, which consecutively fail to be uploaded to the PMS, are
deleted from memory if the HNB attempted to upload them for over 48 hours.
Therefore, following consecutive unsuccessful uploads of PM files to the PMS:
•
If the HNB was not restarted, the oldest files attempted to be uploaded is 48 hours old.
•
If the HNB was restarted once, the oldest file to be uploaded may older than 96 hours (if the HNB
was restarted just before the 48 period expired) and the time it was powered off
6.1.3.5
Alarms
The HNB will raise the following alarm when unable to upload a PM file to the PMS because it was not
able to contact the PMS (any causes)
•
PM Report Failure: “The HNB is unable to upload the PM files.”
o
The alarm is only issued at the first failed attempt, not subsequent retry
o
The alarm is cleared when the upload succeeds
6.2 The Collection Process
The collection process defines the discrete intervals at which each measurement is collected.
Each PM can be specified with a different collection periods. At the end of the collection period of each
PM, the metrics are written in the PM file. Those counters pegged to the collection period are set to 0.
The collection period defined for the counters are shown in Table 1:
Collection Period
Off
The counter is disabled
15 min
Parameter Setting
0
1
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
10
▀ Measurement Control
Collection Period
Parameter Setting
30 min
2
1 hour
3
6 hours
4
12 hours
5
24 hours
6
Table 1: Collection Periods
6.2.1 Override Collection Period
From release R3.4.4 onwards, F5.3.23 provides a common means for configuration of all PM counters
using OverridePeggingPeriod, a global override for counter pegging parameters. When an individual
pegging parameter has been enabled this override will be applied. The override does not apply where
the individual pegging parameter is off.
6.2.2 Counters Sampling
The collection process is based on a non-configurable sampling time of 15 minutes. At each sample,
the HNB determines whether each metric need to be written to file based on the individual collection
period setting. As a consequence, if the HNB is powered up at 13:20 and then a file is uploaded at
13:30, then the file would only have a header and footer and no other counters.
The time at which the collection sampling is started is always based the 0, 15, 30 and 45 minutes past
the hours. Therefore, acquisition time of PMs from different HNBs is always aligned to each other.
6.2.3 Memory Availability for Storage of PM Data
PM files are text files and generally small in size. Therefore, it is deemed a very rare condition in which
a HNB cannot store performance metrics due to memory limitations.
However, PM data will not be written to the file during periods when memory is limited. The resulting
PM file will miss data during these collection events, such events will be detected by non-contiguous
timestamps in the PM file.
As soon as space memory is made available, the HNB will append data to the current PM file.
▄ Definition, Configuration and Reporting of PM Counters for Iuh
11
USC-44-12-002
▀ Additional Information
7 Additional Information
In addition to the PM metrics, additional information can be added to the PM report to help with the
analysis of the system operation. This additional information is appended as an XML comment block to
the PM report to ensure that it does not break the XML encoding scheme of the PM report proper.
Prior to R3.5 this information is limited to the current alarms active at the time of the report and the list
of neighbor cells with their reported measurements (see section 6). There are two associated datamodel parameters provided within the InternetGatewayDevice.Ser vices.FAPServi ce.1.PerfMgmt.FileMg mt
object to enable the addition of this information to the PM reports. These controls are:
•
X_UBIQUISYS_COM_ AddCurr entlAlar mInf ormation
•
X_UBIQUISYS_COM_ AddNei ghbourList Metri cs
From R3.5 onwards the additional information set is extended with support for current operational
parameters, GPS location, Hand-out statistics broken down by neighbour and last REM scan results.
The following control parameters are added to the same data-model object from R3.5:
•
X_UBIQUISYS_COM_ AddOper ationalPar ameters
•
X_UBIQUISYS_COM_ AddGPSLo cation
•
X_UBIQUISYS_COM_ AddHandout StatsByNeighbour
•
X_UBIQUISYS_COM_ AddREMSca n
At the end of each reporting period the additional information will be added to the PM file and the file
will then be closed. Examples of the additional information added can be seen in the following section:
7.1 PM Comment Block
7.1.1 Alarm Status
<!-ALARM STATUS
CANNOTSELECTRFPROFILE Cleared
SOFTWAREERROR Cleared
PMREPORTFAILURE Cleared
LOCATIONCHANGED Cleared
POORRFQOS Cleared
POORBACKHAULQOS Cleared
HIGHTEMPERATURE Cleared
UPGRADEFAILURE Cleared
FILESYSTEMFAILURE Cleared
HOTSPOTINDICATION Cleared
NONTPSERVER Cleared
INVALIDCOUNTRY Cleared
GATEWAYCHANGED Cleared
LOSSOFALLTIMING_SERVERCONNECTIVITY Cleared
NOTIMINGSOURCE Cleared
ENTERPRISELACREUSEDETECTED Cleared
SERVICEAFFECTINGBACKHAULQOS Cleared
CAPACITYLIMITINGBACKHAULQOS Cleared
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
12
▀ Additional Information
NOSONTRAFFICRECEIVEDFROMSMALLCELLPEERS Cleared
HARDWAREFAULT Cleared
HARDWAREORNETWORKTIMINGPROBLEM Cleared
CONGESTION Cleared
TRANSMISSIONERROR Cleared
APPLICATIONSUBSYSTEMFAILURE Cleared
HIGHTRAFFICLOAD Cleared
HNBPSCINUSEONTHESAMEUARFCNBYATIER1NEIGHBOUR Cleared
HNBPSCISREUSEDONTHESAMEUARFCN Cleared
PSCCONFUSIONDETECTED Cleared
CANNOTSELECTPSC Cleared
ACTIVESONTIMEOUT Cleared
INCONSISTENTUARFCNSDETECTED Cleared
HNBREGISTRATIONREJECTORDEREGISTERED Cleared
IPSECCONNECTIVITYFAILURE Cleared
HNBGWCONNECTIVITYORSCTPASSOCIATIONFAILURE Cleared
OPERATIONSTATECHANGE Cleared
ENCLOSURETAMPERINGDETECTED Cleared
LONGTERMIPSECFAILURE Cleared
SONSERVERCOORDINATIONFAILED Cleared
SONGROUPSIZELIMITEXCEEDED Cleared
SONCOORDINATEDHNBGWREGISTRATIONFAILED Cleared
PERSISTENTHNB_GWLATENCY Cleared
-->
7.1.2 Histograms
<!-- IurhDHandinTNLUpdateLatencyDist Histogram
0,0,0,0,0,0,0,0,0,0,0,0
-->
<!-- IurhDHandinFailedTNLUpdateLatencyDist Histogram
0,0,0,0,0,0,0,0,0,0,0
-->
<!-- SRNSRelocHandoutCSPrepLatencyDist Histogram:
0,0,0,0,0,0,0,0,0,0,0,0
-->
<!-- SRNSRelocHandoutPSPrepLatencyDist Histogram
0,0,0,0,0,0,0,0,0,0,0,0
-->
<!-- SRNSRelocHandoutCSExecFailPrep Histogram
0,0,0,0,0,0,0,0,0,0,0
-->
<!-- SRNSRelocHandoutPSExecFailPrep Histogram
0,0,0,0,0,0,0,0,0,0,0
▄ Definition, Configuration and Reporting of PM Counters for Iuh
13
USC-44-12-002
▀ Additional Information
-->
7.1.3 Further Comment Types
<!-- NeighborListInUse.IntraFreqCell List
<!-- NeighborListInUse.InterFreqCell List
<!-- NeighborListInUse.InterRATCell List
<!-- Handout stats by neighbour
<!-- REM scan
<!-- Operational parameters
<!-- GPS Location
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
14
▀ Additional Information
7.2 PM Comment Block
(L)egacy ,
(N)ew
<!--
Note: Current Alarms can be referenced in USC-44-54-010 HNB Alarms Summary
ALARM STATUS
L
SOFTWAREERROR < Active /Cleared>
L
CANNOTSELECTRFPROFILE <Active/Cleared>
PMREPORTFAILURE < Active /Cleared>
LOCATIONCHANGED < Active /Cleared>
POORRFQOS < Active /Cleared>
L
"The HNB is unable to select a valid set of RF parameters because of excessive interference."
L
"The HNB is unable to upload the PM files."
L
L
POORBACKHAULQOS < Active /Cleared>
L
HIGHTEMPERATURE < Active /Cleared>
L
FILESYSTEMFAILURE < Active /Cleared>
L
UPGRADEFAILURE < Active /Cleared>
L
HOTSPOTINDICATION < Active /Cleared>
L
INVALIDCOUNTRY < Active /Cleared>
L
NONTPSERVER < Active /Cleared>
▄ Definition, Configuration and Reporting of PM Counters for Iuh
15
Description
L
"The HNB detected a software problem which requires it to re-initialise in order to provide service."
"The HNB has detected that it has potentially changed location."
"The HNB has measured that the QoS on the RF uplink and/or downlink have has diminished below a
preset threshold."
"The HNB has measured that the QoS on the backhaul connection have has diminished below a preset
threshold."
"The HNB shutdown because of over temperature."
"The HNB could not complete its upgrade successfully."
"The HNB secondary file system has failed. (will be escalated to a System Failure if the fault cannot be
cleared)."
"The HNB has detected an excessive number of attach rejects which indicates it is in a hotspot."
"The HNB cannot connect to an NTP server to set its internal date/time clock."
"Potential change location into a different country. HNB home PLMN MCC has not been detected on
any macro cells."
Activ ation
InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt.X_UBIQUISYS_COM_Add
CurrentlAlarmInformation
PM Comment Entry
USC-44-12-002
▀ Additional Information
GATEWAYCHANGED < Active /Cleared>
L
LOSSOFALLTIMING_SERVERCONNECTIVITY<
Active /Cleared>
L
NOTIMINGSOURCE < Active /Cleared>
ENTERPRISELACREUSEDETECTED
/Cleared>
<
SERVICEAFFECTINGBACKHAULQOS
/Cleared>
CAPACITYLIMITINGBACKHAULQOS
/Cleared>
L
Active
L
<
Active
L
<
Active
L
NOSONTRAFFICRECEIVEDFROMSMALLCELLPEER
S < Active /Cleared>
HARDWAREFAULT < Active /Cleared>
HARDWAREORNETWORKTIMINGPROBLEM
Active /Cleared>
L
<
CONGESTION < Active /Cleared>
TRANSMISSIONERROR < Active /Cleared>
APPLICATIONSUBSYSTEMFAILURE
/Cleared>
<
Active
HIGHTRAFFICLOAD < Active /Cleared>
HNBPSCINUSEONTHESAMEUARFCNBYATIER1NEI
GHBOUR < Active /Cleared>
HNBPSCISREUSEDONTHESAMEUARFCN
USC-44-12-002
<
Active
"The HNB has detected that it has potentially change location as the Home Gateway MAC address has
changed"
"The HNB has detected that all the configured timing servers are no longer contactable."
"No macro coverage, no timing servers, or LossOfAllTimingServerConnectivity alarm raised. HNB drift
until timing restored"
"The HNB has detected that the LAC assigned to the enterprise is being used by a cell that is not part of
the enterprise group"
"Backhaul QoS below threshold with only one CS call in progress. CS service will be affected"
"Backhaul QoS below threshold with several CS calls in progress. HNB may limit CS capacity to
maintain acceptable service level"
"Inter-Small Cell P2P interface is enabled but no traffic received, check OAM and LAN config."
L
"The AP has a detected a major hardware fault, refer to event log."
L
"The AP has experienced signalling overload when already at minimum possible coverage"
L
"Communication Failure: CBC"
L
L
"Oscillator Stability Problem"
"Communication Failure: CBC"
L
"The FemtoEngine is consistently reaching its Erlang capacity"
L
"The HNB has detected that the PSC, it is using is also in use on the same UARFCN."
L
"The HNB has detected that the PSC it is using is also in use on the same UARFCN by a tier 1
neighbour."
Definition, Configuration and Reporting of PM Counters for Iuh ▄
16
▀ Additional Information
/Cleared>
PSCCONFUSIONDETEC TED < Active /Cleared>
L
"The HNB has detected that the same PSC is in use by more than one neighbour on the same UARFCN"
ACTIVESONTIMEOUT < Active /Cleared>
L
"AciveSON has timed out despite Inter-HNB SON connection established"
CANNOTSELECTPSC < Active /Cleared>
INCONSISTENTUARFCNSDETECTED
/Cleared>
<
L
Active
HNBREGISTRATIONREJECTORDEREGISTERED
Active /Cleared>
<
L
"The HNB cannot use any of the provisioned PSCs"
"AciveSON has detected that the same UARFCN is not used throughout the grid"
L
"Service cannot be provided due to Iuh registration reject or deregistration"
IPSECCONNECTIVITYFAILURE < Active /Cleared>
L
"The HNB has failed to establish or dropped the connection to the IPSec tunnel"
OPERATIONSTATECHANGE < Active /Cleared>
L
"HNB's RF radio transmitter has been disabled and the cell is not providing service"
"The eNB has failed to connect to any of the provisioned Security Gateways; multiple attempts have
been made to each gateway."
HNBGWCONNECTIVITYORSCTPASSOCIATIONFAIL
URE < Active /Cleared>
ENCLOSURETAMPERINGDETECTED
/Cleared>
<
LONGTERMIPSECFAILURE < Active /Cleared>
L
SONSERVERCOORDINATIONFAILED
/Cleared>
<
Active
L
Active
L
SONGROUPSIZELIMITEXCEEDED
/Cleared>
<
Active
L
L
SONCOORDINATEDHNBGWREGISTRATIONFAILE
D < Active /Cleared>
L
IPCOMMUNICATIONLOST< Active /Cleared>
N
PERSISTENTHNB_GWLA TENCY< Active /Cleared>
▄ Definition, Configuration and Reporting of PM Counters for Iuh
17
L
"Service cannot be provided due to HNBGW service failure"
"Physical tampering of the device enclosure has been detected"
"The HNB is provisioned with a different set of servers than the other SON peers."
"The HNB is operating beyond its maximum supported number of SON secure peer connections. The
HNB may become overloaded."
"The HNB failed to register to the same HNB-GW as its peers (prevents Iurh handover)."
"Persistent over-threshold HNB-GW response latency"
"The IPC communication has been lost with the co-located module"
USC-44-12-002
▀ Additional Information
N
<!-- NeighborListInUse.IntraFreqCell List
L
INTRA_FREQ__<1..NintraFreq>_PARAM:PLMNID=<
>
L
INTRA_FREQ__<1..NintraFreq>_PARAM:RNCID =< >
L
INTRA_FREQ__<1..NintraFreq>_PARAM:CID= < >
L
INTRA_FREQ__<1..NintraFreq>_PARAM:LAC=< >
L
INTRA_FREQ__<1..NintraFreq>_PARAM:RAC=< >
L
-->
PARAM:IntraFreqCellNumberOfEntries=<NintraFr
eq>
"Insufficient power-over-ethernet"
L
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5.
RNC-ID of an intra-freq neighbour cell. It uniquely identifies an RNC within a PLMN.
Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than
4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP.
The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit
need to have them separated.
3GPP-TS.25.413 Section 9.2.1.39
Cell Identifier (C-id) that identifies a cell within an RNS. This Cell Identifier together with the
controlling RNC (RNC-ID) constitutes the UTRAN Cell ID (UCID) and is used to identify a cell uniquely
within UTRAN. C-ID is either 12-bit or 16-bit value. 3GPPTS.25.401 Section 6.1.5.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the
Location Area ID (LAI).
3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely
identifies the Routing Area ID (RAI).
InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt.X_UBIQUI
SYS_COM_AddNeighbourListMetrics
INSUFFICIENTPOWER< Active /Cleared>
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
18
▀ Additional Information
INTRA_FREQ__<1..NintraFreq>_PARAM:URA=< >
L
INTER_FREQ__<1..NintraFreq>_PARAM:UARFCND
L=< >
L
INTRA_FREQ__<1..NintraFreq>_PARAM:PrimarySc
ramblingCode=< >
L
<!-- NeighborListInUse.InterFreqCell List
L
INTER_FREQ__<1..NinterFreq>_PARAM:PLMNID=<
>
L
INTER_FREQ__<1..NinterFreq>_PARAM:RNCID=< >
L
INTER_FREQ__<1..NinterFreq>_PARAM:CI D=< >
L
INTER_FREQ__<1..NinterFreq>_PARAM:LAC= < >
L
-->
PARAM:InterFreqCellNumberOfEntries=<NinterFr
eq>
3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7
UTRAN Registration Area (URA) 3GPP-TS.23.401.
Indicates to the UE which URA it shall use in case of overlapping URAs.
3GPP-TS.25.331 Section 10.3.2.6
The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell.
3GPPTS.25.433
Primary CPICH scrambling code.
L
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5.
RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC within a PLMN.
Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than
4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP.
The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit
need to have them separated.
3GPP-TS.25.413 Section 9.2.1.39
Cell Identifier (C-id) that identifies a cell within an RNS. This Cell Identifier together with the
controlling RNC (RNC-ID) constitutes the UTRAN Cell ID (UCID) and is used to identify a cell uniquely
within UTRAN. C-ID is either 12-bit or 16-bit value. 3GPPTS.25.401 Section 6.1.5.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the
Location Area ID (LAI).
▄ Definition, Configuration and Reporting of PM Counters for Iuh
19
USC-44-12-002
▀ Additional Information
INTER_FREQ__<1..NinterFreq>_PARAM:RAC=< >
L
INTER_FREQ__<1..NinterFreq>_PARAM:URA=< >
L
INTER_FREQ__<1..NinterFreq>_PARAM:UARFCND
L=< >
L
INTER_FREQ__<1..NinterFreq>_PARAM:PrimarySc
ramblingCode=< >
L
<!-- NeighborListInUse.InterRATCell List
L
INTER_RAT__<1..NinterRAT>_PARAM:PL MNID= < >
L
-->
PARAM:GSMNumberOfEntries=<Nint erRAT>
L
INTER_RAT__<1..NinterRAT>_PARAM:LAC=< >
L
INTER_RAT__<1..NinterRAT>_PARAM:RAC=< >
L
INTER_RAT__<1..NinterRAT>_PARAM:ARFCN=< >
L
3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely
identifies the Routing Area ID (RAI).
3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7
UTRAN Registration Area (URA) 3GPP-TS.23.401.
Indicates to the UE which URA it shall use in case of overlapping URAs.
3GPP-TS.25.331 Section 10.3.2.6
The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell.
3GPPTS.25.433
Primary CPICH scrambling code.
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5.
Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the
Location Area ID (LAI).
3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6
Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely
identifies the Routing Area ID (RAI).
3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7
ARFCN of this cell.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
20
▀ Additional Information
INTER_RAT__<1..NinterRAT>_PARAM:NC C=< >
L
NCC (PLMN Color Code)
INTER_RAT__<1..NinterRAT>_PARAM:CI=< >
N
Cell ID of the cell per 3GPP-TS.23.003 Section 4.3.1.
INTER_RAT__<1..NinterRAT>_PARAM:BandIndicat
or=< >
L
N
-->
<!-- Handout stats by neighbour
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
PrepPSAttempts=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
PSPrepSuccess=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
PrepCSAttempts=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
CSPrepSuccess=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
PrepCSFailRelocationCanc elled=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
PrepPSFailRelocationCanc elled=< >
N
▄ Definition, Configuration and Reporting of PM Counters for Iuh
21
BCC (BS color code)
"Indicates how to interpret the BCCH ARFCN.
Enumeration of:
- ""GSM 850""
- ""GSM 900""
- ""DCS 1800""
- ""PCS 1900"""
This counter is incremented for each SRNS Relocation preparation of the CS domain made towards a
target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each SRNS Relocation preparation of the PS domain made towards a
target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each successful CS domain SRNS Relocation preparation towards a
target cell as indicated by receiving RANAP Relocation Command from the CN.
This counter is incremented for each successful PS domain SRNS Relocation preparation towards a
target cell as indicated by receiving RANAP Relocation Command from the CN.
This counter is incremented for each SRNS Relocation preparation attempt towards a target cell that
was cancelled by the HNB for the CS domain, as indicated by sending RANAP Relocation Cancel
towards the CN.
This counter is incremented for each SRNS Relocation preparation attempt towards a target cell that
was cancelled by the HNB for the PS domain, as indicated by sending RANAP Relocation Cancel
InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileM
gmt.X_UBIQUISYS_COM_AddHandoutStatsByNeighbour
INTER_RAT__<1..NinterRAT>_PARAM:BCC=< >
USC-44-12-002
▀ Additional Information
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
ExecutionCSAttempt=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
ExecutionCSSuccess=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
ExecutionPSAttempt=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:Relocation
ExecutionPSSuccess=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutRequestedCS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutRequestedMulti=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutRequestedPS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutAcceptedCS=< >
N
towards the CN.
This counter is incremented when the HNB instructs the UE to perform the handout of a CS connection
(SRB or RAB) to a target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the CS domain to a target is successfully
completed, as indicated by reception of the RANAP Iu Release Command that terminates the
procedure.
This counter is incremented when the HNB instructs the UE to perform the handout of a PS connection
(SRB or RAB) to a target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the PS domain to a target is successfully
completed, as indicated by reception of the RANAP Iu Release Command that terminates the
procedure.
Incremented when RNSAP Enhanced Relocation Request is sent for a CS specific relocation via a Direct
(LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Request is sent for a PS specific relocation via a Direct
(LAN based) Iurh connection.
Iincremented when RNSAP Enhanced Relocation Request is sent for a multi-domain relocation via a
Direct (LAN based) Iurh connection.
Iincremented when RNSAP Enhanced Relocation Response is received for a CS specific relocation via a
Direct (LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Response is received for a PS specific relocation via a
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
22
▀ Additional Information
doutAcceptedPS=< >
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutAcceptedMulti=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCancelledCS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCancelledPS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCancelledMu lti=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCompletedCS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCompletedPS=< >
N
INTRA_FREQ__<1..NintraFreq>_PARAM:IurhDHan
doutCompletedMulti=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
PrepCSAttempts=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
CSPrepSuccess=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
PrepPSAttempts=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
PSPrepSuccess=< >
N
▄ Definition, Configuration and Reporting of PM Counters for Iuh
23
Direct (LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Response is received for a multi-domain relocation
via a Direct (LAN based) Iurh connection.
Incremented whenever the sHNB sends RNSAP Enhanced Relocation Cancel to abort a CS specific
Direct (LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedCSAcceptTi meou t is counted in the timeout case.)
Incremented when the sHNB sends RNSAP Enhanced Relocation Cancel to abort a PS specific Direct
(LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedPSAcceptTi meou t is counted in the timeout case.)
Incremented when the sHNB sends RNSAP Enhanced Relocation Cancel to abort a multi-domain Direct
(LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedMultiAcc eptTi meo ut is counted in the timeout case.)
Represents the sum of the IurhDHandoutCompleted* counters below.
Incremented when a CS specific Direct (LAN based) Iurh relocation is terminated at the sHNB by
receiving message HNBAP UE Deregister with cause ‘UE relocated’.
Incremented when a PS specific Direct (LAN based) Iurh relocation is terminated at the sHNB by
receiving message HNBAP UE Deregister with cause ‘UE relocated’.
This counter is incremented for each SRNS Relocation preparation for the CS domain made towards a
target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each SRNS Relocation preparation for the PS domain made towards a
target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each successful CS domain SRNS Relocation preparation towards a
target cell as indicated by receiving RANAP Relocation Command from the CN.
This counter is incremented for each successful PS domain SRNS Relocation preparation towards a
target cell as indicated by receiving RANAP Relocation Command from the CN.
USC-44-12-002
▀ Additional Information
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
PrepCSFailRelocationCanc elled=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
PrepPSFailRelocationCanc elled=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
ExecutionCSAttempt=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
ExecutionCSSuccess=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
ExecutionPSAttempt=< >
N
INTER_FREQ__<1..NinterFreq>_PARAM:Relocation
ExecutionPSSuccess=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutRequestedCS=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutRequestedMulti=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutRequestedPS=< >
N
This counter is incremented for each CS domain SRNS Relocation preparation attempt towards a target
cell that was cancelled by the HNB, as indicated by sending RANAP Relocation Cancel towards the CN.
This counter is incremented for each PS domain SRNS Relocation preparation attempt towards a target
cell that was cancelled by the HNB, as indicated by sending RANAP Relocation Cancel towards the CN.
This counter is incremented when the HNB instructs the UE to perform the handout of a CS connection
(SRB or RAB) to a target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the CS domain to a target is successfully
completed, as indicated by reception of the RANAP Iu Release Command that terminates the
procedure.
This counter is incremented when the HNB instructs the UE to perform the handout of a PS connection
(SRB or RAB) to a target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the PS domain to a target is successfully
completed, as indicated by reception of the RANAP Iu Release Command that terminates the
procedure.
Incremented when RNSAP Enhanced Relocation Request is sent for a CS specific relocation via a Direct
(LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Request is sent for a PS specific relocation via a Direct
(LAN based) Iurh connection.
Iincremented when RNSAP Enhanced Relocation Request is sent for a multi-domain relocation via a
Direct (LAN based) Iurh connection.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
24
▀ Additional Information
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutAcceptedCS=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutAcceptedMulti=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutAcceptedPS=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCancelledCS= < >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCancelledPS=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCancelledMu lti=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCompletedCS=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCompletedMulti=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repPSAttempts=< >
N
INTER_FREQ__<1..NINTERFreq>_PARAM:IurhDHa
ndoutCompletedPS=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repCSAttempts=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repCSSuccess=< >
N
Iincremented when RNSAP Enhanced Relocation Response is received for a CS specific relocation via a
Direct (LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Response is received for a PS specific relocation via a
Direct (LAN based) Iurh connection.
Incremented when RNSAP Enhanced Relocation Response is received for a multi-domain relocation
via a Direct (LAN based) Iurh connection.
Incremented whenever the sHNB sends RNSAP Enhanced Relocation Cancel to abort a CS specific
Direct (LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedCSAcceptTi meou t is counted in the timeout case.)
Incremented when the sHNB sends RNSAP Enhanced Relocation Cancel to abort a PS specific Direct
(LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedPSAcceptTi meou t is counted in the timeout case.)
Incremented when the sHNB sends RNSAP Enhanced Relocation Cancel to abort a multi-domain Direct
(LAN based) Iurh relocation for reasons other than timeout recovery. (Note:
IurhDHandoutFailedMultiAcc eptTi meo ut is counted in the timeout case.)
Represents the sum of the IurhDHandoutCompleted* counters below.
Incremented when a CS specific Direct (LAN based) Iurh relocation is terminated at the sHNB by
receiving message HNBAP UE Deregister with cause ‘UE relocated’.
Incremented when a PS specific Direct (LAN based) Iurh relocation is terminated at the sHNB by
receiving message HNBAP UE Deregister with cause ‘UE relocated’.
This counter is incremented for each SRNS Relocation preparation for the CS domain made towards an
Inter-RAT target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each SRNS Relocation preparation for the PS domain made towards an
Inter-RAT target cell, as indicated by sending RANAP Relocation Required towards the CN.
This counter is incremented for each successful CS domain SRNS Relocation preparation towards an
Inter-RAT target cell as indicated by receiving RANAP Relocation Command from the CN.
▄ Definition, Configuration and Reporting of PM Counters for Iuh
25
USC-44-12-002
▀ Additional Information
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repPSSuccess=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repCSFailRelocationCanc elled=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationP
repPSFailRelocationCanc elled=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationE
xecutionCSAttempt=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationE
xecutionCSSuccess=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationE
xecutionPSAttempt=< >
N
INTER_RAT__<1..NinterRAT>_PARAM:RelocationE
xecutionPSSuccess=< >
N
-->
This counter is incremented for each successful PS domain SRNS Relocation preparation towards an
Inter-RAT target cell as indicated by receiving RANAP Relocation Command from the CN.
This counter is incremented for each CS domain SRNS Relocation preparation attempt towards an
Inter-RAT target cell that was cancelled by the HNB, as indicated by sending RANAP Relocation Cancel
towards the CN.
This counter is incremented for each PS domain SRNS Relocation preparation attempt towards an
Inter-RAT target cell that was cancelled by the HNB, as indicated by sending RANAP Relocation Cancel
towards the CN.
This counter is incremented when the HNB instructs the UE to perform the handout of a CS connection
(SRB or RAB) to an Inter-RAT target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the CS domain to an Inter-RAT target is
successfully completed, as indicated by reception of the RANAP Iu Release Command that terminates
the procedure.
This counter is incremented when the HNB instructs the UE to perform the handout of a PS connection
(SRB or RAB) to an Inter-RAT target cell by sending one of the following RRC messages:
• Radio Bearer Setup
• Radio Bearer Release
• Radio Bearer Reconfiguration
• Transport Channel Reconfiguration
• Physical Channel Reconfiguration
This counter is incremented when SRNS Relocation of the PS domain to an Inter-RAT target is
successfully completed, as indicated by reception of the RANAP Iu Release Command that terminates
the procedure.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
26
<!-- UE detected qualified candidates
UEDetQualCandidate_<1..NDetectedCells>_PARAM:
PSC=< >
N
Primary scrambling code of detected cell
UEDetQualCandidate_<1..NDetectedCells>_PARAM:
LastReportedTime=< >
N
Time last reported for detected cell
<!-- REM scan
N
-->
PARAM:WCDMAFDD.REMBandList=< >
PARAM:CellConfig.UMTS.RAN.C ellID= < >
N
PARAM:WCDMAFDD.UARFCNDLList=< >
N
PARAM:WCDMAFDD.LastScan Time=< >
N
PARAM:WCDMAFDD.CellLas tSc an Time=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.RF.UARF
CNDL=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.RF.CPICH
▄ Definition, Configuration and Reporting of PM Counters for Iuh
27
N
Comma-separated list of strings. Each item is a UMTS Band to measure. Each band is identified in by a
roman numeral 3GPP-TS.25.104.
If an empty string then no specific UMTS band is provided, meaning that the FAP is required to scan all
available bands.
The order of the band indicator has no significance.
Cell ID of the cell per 3GPP-TS.23.003 Section 4.3.1.
Comma-separated list (maximum length 64) of strings. Each entry is a UARFCN in the DL direction to
measure.
If an empty string, then no specific UARFCN is provided, meaning that the FAP is required to scan all
UARFCNs that it is aware of.
The time of the last UMTS system radio environment measurement.
Note that Ubiquisys FAPs will only update this after a full REM scan, not during the 'Continuous' scan
mode
The time of the last UMTS system radio environment measurement.
Note that Ubiquisys FAPs will only update this after a full REM scan, not during the 'Continuous' scan
mode
The UTRA Absolute Radio Frequency Channel Number (UARFCN) in the DL direction of an FDD mode
cell. 3GPP-TS.25.433
Received signal level in dBm of the CPICH channel. (Ref. 3GPP-TS 25.133)
InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt.X_UBIQUISY
S_COM_AddREMScan
▀ Additional Information
USC-44-12-002
▀ Additional Information
RSCP=< >
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.RF.CPICH
EcNo=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.RF.RSSI=
<>
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.RF.Prima
ryScramblingCode=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.PL
MNType=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.PL
MNID=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.LA
C=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.Cell
ID=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.X_U
BIQUISYS_COM_TxDiversityInd=< >
Measured EcNo. (energy per chip to interference power density) in dB received in the downlink pilot
channel.
Actual values of the range are -24.0 dB to 0.0 dB in steps of 0.5 dB. The value of CPICHEcNo divided by
2 yields the actual value of the range. 3GPP-TS.25.133 Section 9.1.2.3
This measurement is for Inter-frequency handover evaluation, measured in total dBm in the band.
3GPP-TS.25.133 Section9.1.3
Primary scrambling code.
Type of Public Land Mobile Network (PLMN).
Enumeration of:
- "GSM-MAP"
- "ANSI-41"
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5.
Location Area Code (LAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID
(MCC+MNC) and LAC uniquely identifies the LAI (Location Area ID) 3GPP-TS.23.003
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.RA
C=< >
N
Routing Area Code (RAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID
(MCC+MNC), LAC, and RAC uniquely identifies the RAI (Routing Area ID) 3GPP-TS.23.003.
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.PC
PICHTxPower=< >
N
Primary Common Pilot Channel (CPICH) power level on SIB 5/6 3GPP-TS.25.331 Section10.3.6.55
N
Indicates whether the cell is using transmit diversity
Cell Identity as defined in SIB3 3GPP-TS.25.331 Section10.3.2.2. 3GPP-TS.24.008
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
28
▀ Additional Information
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.X_U
BIQUISYS_COM_MaxU lTxPo wer=< >
N
Max permitted UE Tx power: -50-33 (dBm) as broadcast in SIB 3 3GPP-TS.25.331 10.3.6.39
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.CSG
Indicator=< >
N
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.CSG
ID=< >
N
The CSG-indicator Information Element (IE) in the Master Information Block reflects the access mode
of the CSG cell. It is hence dependent on the value of .AccessMgmt.AccessMode.
If true the CSG-indicator IE is present, reflecting closed access to the CSG cell.
If false the CSG-indicator IE is absent, reflecting the access mode as "not a closed-access".
3GPP-TS.25.331 Section 10.2.48.8.1
PARAM:WCDMAFDD.Cell.<1..NWCDMA>.BCCH.UA
RFCNDLList=< >
N
PARAM:GSM.REMBandList=< >
N
PARAM:GSM.LastScanTime=< >
N
▄ Definition, Configuration and Reporting of PM Counters for Iuh
29
Defines the Closed Subscriber Group of the Access Control List. FAP broadcasts this CSG ID in SIB3
3GPP-TS.25.331 Section10.3.2.8 depending on the AccessMode.
Comma-separated list (maximum length 128) of unsigned integers (range 0 to 16383). Each item is a
UTRA Absolute Radio Frequency Channel Number (UARFCN} in the DL direction dedicated to the CSG
cells.
UARFCNDLList is broadcast in SIB 11bis 3GPPTS.25.331 Section 10.2.48.8.14a.
The corresponding UTRA Absolute Radio Frequency Channel Number (UARFCN} in the UL direction is
derived based on the fixed offset applicable for the frequency band.
"Comma-separated list of strings. Each item is a GSM Band to measure. Each list item is an
enumeration of:
- ""T-GSM380""
- ""T-GSM410""
- ""GSM450""
- ""GSM480""
- ""GSM710""
- ""GSM750""
- ""T-GSM810""
- ""GSM850""
- ""P-GSM900""
- ""E-GSM900""
- ""R-GSM900""
- ""T-GSM900""
- ""DCS1800""
- ""PCS1900""
If an empty string then no specific GSM band is provided, meaning that the FAP MUST scan all bands.
If a list is provided, the FAP is expected to limit the REM measurement to the band(s) specified in this
list only and ignore others even if they are detected."
"The time of the last UMTS system radio environment measurement.
Note that Ubiquisys FAPs will only update this after a full REM scan, not during the 'Continuous' scan
USC-44-12-002
▀ Additional Information
PARAM:GSM.Cell.<1..NGSM>.BandIn dicator=< >
N
PARAM:GSM.Cell.<1..NGSM>.ARFCN=< >
N
PARAM:GSM.Cell.<1..NGSM>.PLMNID=< >
N
PARAM:GSM.Cell.<1..NGSM>.BSIC=< >
N
PARAM:GSM.Cell.<1..NGSM>.LAC=< >
N
PARAM:GSM.Cell.<1..NGSM>.RAC=< >
N
PARAM:GSM.Cell.<1..NGSM>.CI=< >
N
PARAM:GSM.Cell.<1..NGSM>.RSSI=< >
-->
<!-- Operational parameters
PARAM:UARFCDLInUse=< >
N
mode"
Indicates how to interpret the BCCH ARFCN.
Enumeration of:
- "GSM 850"
- "GSM 900"
- "DCS 1800"
- "PCS 1900"
Absolute Radio Frequency Channel Number (ARFCN) 3GPP-TS.05.05
Base Station Identity Code 3GPP-TS.03.03
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5.
Location Area Code (LAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID
(MCC+MNC) and LAC uniquely identifies the LAI (Location Area ID) 3GPP-TS.23.003
Routing Area Code (RAC) consists of up to 3 numerical characters. The concatenation of PLMN ID
(MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2
3GPP-TS.25.413 Section 9.2.3.7
Cell Identity. 3GPP-TS.25.331 Section 10.3.2.2
Received signal level in dBm of the BCCH carrier.
The DL UARFCN being used by the FAP.
Self-configuration for UARFCN is controlled by .Capabilities.UMTS.SelfConfi g.UARFCNConfig from an
availability perspective and .FAPControl.UMTS.SelfConfig.UARFC NSelfCo nfigEn ab le from an enabled
perspective.
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
30
▀ Additional Information
If the self-configuration capability is available and enabled, this parameter indicates the value selected
by the FAP among the choices provided in UARFCNDL.
PARAM:PrimaryScramblingCod eInUs e=< >
If the self-configuration capability is not available or not enabled, then this parameter contains the first
value in UARFCNDL.
The PSC being used by the FAP.
Self-configuration for PSC is controlled by .Capabilities.UMTS.SelfConfig. Primary Scramb lingCodeConfig
from an availability perspective and
.FAPControl.UMTS.SelfConfig.Pri maryScr amblin gCod eSelfConfigEnab le from an enabled perspective.
If the self-configuration capability is available and enabled, this parameter indicates the value selected
by the FAP among the choices provided in PrimaryScramblingCode.
If the self-configuration capability is not available or not enabled, then this parameter contains the first
value in PrimaryScramblingCode.
PARAM:MaxFAPTxPowerInUs e=< >
512 is treated as invalid value and defines that the PSC selction is not yet completed. FAP will write the
valid value after the PSC selection is completed during boot up. This is too ensure that FAP reports the
PSC in the inform if active notification is set for this parameter.
The maximum transmission power measured in dBm currently used by the FAP.
Actual values of the maximum transmission power are -40.0dBm to 30.0 dBm in steps of 0.1 dB. The
value of MaxFAPTxPowerInUse divided by 10 yields the actual value of the maximum transmission
power.
Self-configuration for maximum transmission power is controlled by
.Capabilities.UMTS.SelfCo nfig.MaxFA PTxPow erConfig from an availability perspective and
.FAPControl.UMTS.SelfConfig. MaxFAPTxPo wer SelfConfigEnab le from an enabled perspective.
If the self-configuration capability is available and enabled, this parameter indicates the value selected
by the FAP among the range provided in MaxFAPTxPower.
PARAM:LACInUse=< >
If the self-configuration capability is not available or not enabled, then this parameter contains a value
selected by the ACS.
The LAC being used by the FAP.
Self-configuration for LAC is controlled by .Capabilities.UMTS.SelfConfig.LACRACURAConfi g from an
availability perspective and .FAPControl.UMTS.SelfConfig.LACRACURA SelfConfigEnab le from an
enabled perspective.
If the self-configuration capability is available and enabled, this parameter indicates the value selected
by the FAP among the choices provided in LACRAC.
▄ Definition, Configuration and Reporting of PM Counters for Iuh
31
If the self-configuration capability is not available or not enabled, then this parameter contains the first
USC-44-12-002
▀ Additional Information
LAC value in LACRAC.
LACInUse is made persistent so that on reboot, the previous LACInUse may be discounted from the
selected choice of LAC
PARAM:RACInUse=< >
The RAC being used by the FAP.
Self-configuration for RAC is controlled by .Capabilities.UMTS.SelfConfig.LACRACURAConfig from an
availability perspective and .FAPControl.UMTS.SelfConfig.LACRACURA SelfConfigEnab le from an
enabled perspective.
If the self-configuration capability is available and enabled, this parameter indicates the value selected
by the FAP among the choices provided in LACRAC.
If the self-configuration capability is not available or not enabled, then this parameter contains the first
RAC value in LACRAC.
PARAM:X_UBIQUISYS_COM_LAIRAISwapEnable=<
>
If configured and enabled (X_UBIQUISYS_COM_LAIRAISwapEn able = true), the following three valus
replace those received from the UE in RANAP and NAS messages to the CN. RANAP and NAS message
from the CN to the UE will have these values overwritten with the PLMNID, LACInUse and RACInUse
values.
PARAM:PLMNID [MCC , MNC]=< >
PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003,
3GPP-TS.24.008.
Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the
subscriber.
Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country.
For a 2-digit MNC the total string length of PLMNID is 5. Note that the MNC is always maintained in the
database as a fixed-length 3-digits - the 3rd digit is 'F' where only a 2-digit MNC is required.
PARAM:X_UBIQUISYS_COM_I uLAC=< >
Defines the LAC reported on the Iu interface in place of the LAC used by the UE. Only used (and
mandatory) if X_UBIQUISYS_COM_LAIRAISwapEnab le is TRUE or
if X_UBIQUISYS_COM_CBSSAItyp e is set to Iu
PARAM:X_UBIQUISYS_COM_I uRAC=< >
Defines the RAC reported on the Iu interface in place of the RAC used by the UE. Only used (and
mandatory) if X_UBIQUISYS_COM_LAIRAISwapEnab le is TRUE
-->
<!-- GPS location
PARAM:LockedLatitude=< >
N
This parameter specifies the latitude of the device's position in degrees, multiplied by 1 million. The
positive value signifies the direction, north of the equator. The negative value signifies the direction,
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
32
▀ Additional Information
south of the equator.
Range is from: 90deg00.00' South (-90,000,000) to 90deg00.00' North (90,000,000).
Example: A latitude of 13deg19.43' N would be represented as 13,323,833, derived as
(13*1,000,000)+((19.43*1,000,0 00)/60 ). Latitude of 50deg0.00' S would be represented as value 50,000,000.
PARAM:LockedLongitude=< >
N
This value is retained across reboots and is only reset after another scan completes successfully. If a
scan has never succeeded before, the value 0 is reported.
This parameter specifies the longitude of the device's position in degrees, multiplied by 1 million. The
positive value signifies the direction, east of the prime meridian. The negative value signifies the
direction, west of the prime meridian.
Range is from: 180deg00.00' West (-180,000,000) to 180deg00.00' East (180,000,000).
Example: A longitude of 13deg19.43' E would be represented as 13,323,833, derived as
(13*1,000,000)+((19.43*1,000,0 00)/60 ). A longitude of 50deg0'0'' W would be represented as value 50,000,000.
This value is retained across reboots and is only reset after another scan completes successfully. If a
scan has never succeeded before, the value 0 is reported.
-->
IurhDHandinTNLUpdateLat encyDist Histogram
Handover Latency Statistics: Iurh TNL Update
SRNSRelocHandoutCSPrepL at encyDist Histogram:
Handover Latency Statistics: SRNS Relocation Handout
SRNSRelocHandoutCSExecFai lPrep Histogram
Handover Latency Statistics: SRNS Relocation for Failed handovers
IurhDHandinFailedTNLUpdateLatencyDist
Histogram
SRNSRelocHandoutPSPrepL at encyDist Histogram
Handover Latency Statistics: Iurh TNL Update for Failed handovers
Handover Latency Statistics: SRNS Relocation Handout
▄ Definition, Configuration and Reporting of PM Counters for Iuh
33
USC-44-12-002
▀ PM Counters
8 PM Counters
As a guideline, in R3.8 up to 523 counters are available. These are all detailed in the PM Counter
file auto-generated for each load, for example:
•
PM_Counters_and_Description_DSV3.8.3T.33AutoGen.xls.
This file contains the PM Counter Name, Description, XML Name and Release version for each
Counter.
▄ Definition, Configuration and Reporting of PM Counters for Iuh
34
USC-44-12-002
▀ PM Counters
Annex A – Change History
Version
Authors
Date
1.0
Simon Hughes
26-10-2012
Status
Comment
1.0
Simon Hughes
20-02-2013
Released
Amended global replace error, release v 1.0
1.1
Simon Hughes
26-03-2013
Draf t
Added R3.4 and R3.4 counters, remov ed superf luous
S7.8 and S8 plus minor edits
1.2
Simon Hughes
02-04-13
Amendments to S6 post Sy s Eng rev iew
1.2.1
Simon Hughes
16-05-13
Remov ed obsolete ref to APM_PERFORMANCE_
First edition based on UBS-71-20-306 Iuh
Perf ormance Management and rev iew comments
prefix
1.2.2
Simon Hughes
17-05-13
Mapped in Pegging/Granularity Control
1.3
Simon Hughes
31-05-13
Released
Corrections to R3.4 RB Setup Failure counter triggers
1.4
Simon Hughes
05-06-13
Released
Addition of note to S5.1
1.4.1
Simon Hughes
08-08-13
Re-branded
1.4.2
Simon Hughes
08-11-13
Released
Addition of 2 missing CBS counters in line with data
model
1.5
Simon Hughes
In Rev iew
Additions brought in f rom R3.5 f eatures:
FEAT-825, FEAT-826, FEAT-1085
1.5
Simon Hughes
30-04-14
Released
Amendment to S5.3
1.6
Simon Hughes
12-05-14
Update
S8.8 CBS updated f or R3.6
1.7
Simon Hughes
09-06-14
Released
Clarif ications in S5.2 and S6.1.3.1
1.8
Simon Hughes
01-08-14
1.9
Simon Hughes
08-10-14
Correct ty pos f or IuRelCommandPSCNGenReason
and CS. Add clarif ication note in S5.2.
Rev iew
Change list:
Updated descriptions of NonCSGUEClosedAccess*
set of counters
Added IurhDirectLinkEstablishmentFail
Changed units of UserDataVolumePS* group of
counters to Kby tes to align with SW implementation
Additions brought in f rom f eatures:
F1.48 [Uplink Inter-cell interf erence limiting - PS
release], F5.3.22 [Counters f or
RABReleasePSUTRANGenReason in Cell FACH and
PCH], F5.3.15 [CS and PS abnormal release
counters], F10.41.1 [Iuh Inf ormation Cell Broadcast
(CBS) with DRX], F2.1.7 [Cell PCH], F2.2.4 [WB-AMR]
Split RelocationPrep counters by domains
Clarif ied Radio Bearer Reconf iguration counters
Minor clarif ication to
Int**RATRelocationExecution*SAttempts counters
Identif y deprecated counters
Identif y HO counters remov ed in R3.5
Add R3.7 counters
2.0
Simon Hughes
22-12-14
Release f or RABAttemptsPSConv ersational/success clarif y RTBD
FCS
RBReleaseAttempts/Success clarif y description
R3.6/7 remov ed
2.1
Simon Hughes
15-01-15
Updated,
Added missing R2.x backhaul counters and replaced:
▄ Definition, Configuration and Reporting of PM Counters for Iuh
35
USC-44-12-002
▀ PM Counters
Version
Authors
Date
Status
released
Comment
UserDataVolumePSUplinkOnloaded ->
UserDataVolumePSUplinkR99Onloaded,
UserDataVolumePSUplinkHSPAOnloaded
UserDataVolumePSDownlinkOnloaded ->
UserDataVolumePSDownlinkR99Onloaded,
UserDataVolumePSDownlinkHSPAOnloaded
Clarif y pegging dif f erence between
SPEECHSUCCESS and RABSUCCESSCSVOICE
2.2
Simon Hughes
28-01-15
Update,
released
S8.1.5 clarif ication f or RBSetupAttempts
2.3
Simon Hughes
09-02-15
Updated
Inter/IntraRATRelocationP repFailNoReply incorrectly
identif ied as remov ed in R3.5. Cellstatus updated to
ref lect the RFStatus options.
2.4
Mauro Fiacco
12-03-15
Updated,
released
Updated and corrected section “The Reporting
Process” (S6.1.3), esp. how randomization is achiev ed
when employ ing Cisco’s RMS
2.5
Shameem Ahamed
18-03-15
Draf t
Update document f or R3.5 MR Release.
2.6
Simon Hughes
15-09-15
Draf t
Updated f or R3.8
2.7
Dav id Price
15-12-15
Draf t
Updated Section 7.2
3.0
Arati Rita Glasf urd
16-02-15
Released
Released f or R3.8 FCS
Definition, Configuration and Reporting of PM Counters for Iuh ▄
USC-44-12-002
36