C 7[1].30 Operator Guide RMS

RMS.frontpage.fm Modified: 7 Mar 2002 Mid v.0.3

Roaming ManagementSystem GSM (RMS GSM)

Operator Manual

RMS.frontpage.fm Modified: 7 Mar 2002

Operator Manual

Roaming Management System GSM(RMS GSM)

(Software release C.07.30)

RMS.titlepages.fm Modified: June 2002 Mid v.0.3

Agilent Part no. J6743-91001-058Edition 1.00June 2002

Legal Information

Legal Information

Notice

The information in this manual is subject to change without notice.

Agilent Technologies warrants that this manual has been prepared byAgilent with all reasonable skill and care. Agilent gives no other warrantyor condition with respect to this manual, whether express or implied andwhether arising from statute or otherwise. Unless any advice orinstruction has been given negligently by Agilent, and death or personalinjury directly results from this, Agilent shall not be liable for anydamages whatsoever (whether direct, incidental, special or consequential)arising out of or connected with the supply or use of this manual.

Warranty

Unless specifically modified for a particular customer, warranties for thehardware and software of the system are as set out in the standardAgilent contracts. Details can be supplied by your nearest Agilent Salesand Service office.

UNIX® is a registered trademark in the USA and other countries,licensed exclusively through X/Open Company Limited.

Oracle® is a registered US trademark of Oracle Corporation, RedwoodCity, California.

OSF/Motif is a trademark of the Open Software Foundation in the USAand other countries.

© Copyright Agilent Technologies UK Ltd 2002

All rights reserved. Reproduction, adaptation, or translation without priorwritten permission is prohibited, except as allowed under the copyrightlaws.

Printed in the UK.

ii RMS GSM Operator Manual

RMS.titlepages.fm Modified: June 2002

Printing History

Printing History

Date ManualEdition

SoftwareRelease Notes

June 2002 1.00 C.07.30 Part No. J6743-91001-058

RMS GSM Operator Manual iii


List of Related Publications


About configuring the RMS software

About the acceSS7 software

Installing, administering & configuring acceSS7

Using acceSS7 software

Part Number Title

J6743-91001-059 RMS GSM System Administrator Guide

Part Number Title

E4260-90125-240 Installation Guide

E4260-90144-073 System Management Guide

E4260-90144-074 System Configuration Guide

E4260-90144-086 Configuration Manager User Guide

Part Number Title

E4260-90144-069 acceSS7 System Operator Manual

E4260-90144-064 Call Trace Operator Manual

E4260-90144-065 Protocol Analysis Operator Manual

E4260-90144-084 Datastore Operator Manual

E4260-90144-082 Alarm Manager Operator Manual

E4260-90144-081 Link Status Operator Manual

E4260-90144-075 Network Investigator Operator Manual

iv RMS GSM Operator Manual



acceSS7 software development kits

E4260-90144-070 OSS Gateway Operator Manual

E4260-90144-083 Traffic Monitor Operator Manual

Part Number Title

E4260-90144-088 P7 Application Developer’s ToolkitProgrammer’s Guide

E4260-90144-089 OSL Application Developer’s ToolkitProgrammer’s Guide

E4260-90144-090 OSL Application Developer’s ToolkitReference Guide

Part Number Title

RMS GSM Operator Manual v


About this Manual

About this Manual

This manual describes how to use the Roaming Management System(RMS) to monitor the status of the GSM service provided to yoursubscribers when roaming in other PLMNs, and to visitors roaming inyour PLMN. In addition, the manual contains introductory andbackground information to help get you started with RMS GSM.

This manual provides information on:

• Using RMS GSM to identify potential problems for roamers, andmonitor the progress and effectiveness of solutions.

• GSM roaming procedures and how you can use the informationderived from the measurements for each procedure to identifyproblems.

Operators using RMS GSM to monitor and investigate problems shouldread the following chapters:

• Chapter 2, “Getting Started”.• Chapter 3, “Using the Roaming Map”.• Chapter 4, “Using the Alarmogram”.• Chapter 5, “Using Radar Diagrams”.• Chapter 6, “Using Active Histograms”.• Chapter 7, “Using Time Series Histograms”.• Chapter 8, “Using the Alarm Management Reporter”.

System Administrators configuring RMS GSM should read the RMS GSMSystem Administrator Guide for complete instructions on how set up RMSGSM.

Some organisations may give Operators Read/Write permissions, so thatthey can define their own Radar Diagrams. This is done using theConfiguration Editor, and if you are an Operator with these permissions,then you should also read the RMS GSM System Administrator Guide forinformation on how to do this.

Finally, Operators and System Administrators may benefit from a betterunderstanding of GSM roaming procedures and measurements. You willfind this information in Appendix A, “RMS GSM Measurements”.

For more information about the acceSS7 system, see the acceSS7 OperatorManual.

vi RMS GSM Operator Manual


Safety Information

Safety Information

Cautions

This manual uses cautions to denote hazards.

Caution A caution calls attention to a procedure, practice or the like which,if not correctly performed or adhered to, could result in loss ofdata. Do not proceed beyond a caution until the indicatedconditions are fully understood and met.

RMS GSM Operator Manual vii


Safety Information

viii RMS GSM Operator Manual


Table of Contents

Page

Legal Information ......................................................................... iiPrinting History ........................................................................... iiiList of Related Publications ........................................................ iv

About configuring the RMS software ................................... ivAbout the acceSS7 software.................................................. iv

About this Manual ....................................................................... viSafety Information ...................................................................... vii

Introduction to RMS GSM................................................................. 1-1What is RMS GSM? ...................................................................... 1-2

Background............................................................................. 1-2What does RMS GSM do? ...................................................... 1-2What does RMS GSM measure? ............................................ 1-3What particular problems can it detect? ............................... 1-5How does RMS GSM get its data? ......................................... 1-6How does RMS GSM present the data .................................. 1-7

Overview of Operator Tasks......................................................... 1-9Monitoring performance......................................................... 1-9Investigating problems........................................................... 1-10Monitoring problem solutions................................................ 1-13

Standard & Optional Features..................................................... 1-14Currently available Function Upgrades ............................... 1-14Standard Features & Function Upgrades............................. 1-16

Getting Started .................................................................................... 2-1Starting & stopping RMS GSM.................................................... 2-2

Starting acceSS7..................................................................... 2-2Starting RMS GSM Displays ................................................. 2-2

Starting RMS GSM displays from the Application Manager ..... 2-3Starting the Alarmogram....................................................... 2-3Starting the Radar Diagram Launcher................................. 2-3Starting the Alarm Management Reporter........................... 2-4

RMS GSM Operator Manual Contents-1

RMSTOC.fm Modified: 13 Jun 2002 Mid v.0.3

Starting RMS GSM displays from OpenView ............................. 2-5Starting OpenView................................................................. 2-5Starting the Roaming Map .................................................... 2-5Starting the Alarmogram....................................................... 2-7Starting Radar Diagrams....................................................... 2-7

Ending an RMS GSM session....................................................... 2-9Logging off from acceSS7 ....................................................... 2-9What happens when a shutdown occurs ............................... 2-9

Saving and printing displayed information................................. 2-10Saving a data snapshot .......................................................... 2-10Saving a graphical snapshot .................................................. 2-10Printing a display ................................................................... 2-10

Using the Roaming Map .................................................................... 3-1About the Roaming Map............................................................... 3-2

Zooming in and out of a geographical area ........................... 3-3Selecting PLMNs for monitoring in Radar Diagrams .......... 3-4

Getting more detail ....................................................................... 3-6

Using the Alarmogram....................................................................... 4-1About the Alarmogram ................................................................. 4-2

Data storage and display periods .......................................... 4-2Showing the Alarmogram............................................................. 4-3

What you see........................................................................... 4-3Understanding the Alarmogram display ..................................... 4-4

Understanding the Alarmogram colour coding..................... 4-7Understanding how rows are ranked .................................... 4-9

Interpreting & manipulating the Alarmogram ........................... 4-10What happens each aggregation period ................................ 4-10Viewing Alarmogram data ..................................................... 4-10Using and suppressing the audible warning ........................ 4-13Using and suppressing row ranking...................................... 4-13Suspending and resuming screen display ............................. 4-14Finding what aggregation period a block covers .................. 4-14Finding the aggregation factor for a block ............................ 4-15Viewing measurement thresholds ......................................... 4-16Finding a specific PLMN........................................................ 4-16Deselecting a PLMN............................................................... 4-17Viewing the Measurement Summary for a PLMN............... 4-17Being aware of data loss......................................................... 4-18Using icons to manage your workspace................................. 4-18

Getting more detail ....................................................................... 4-19Closing the Alarmogram............................................................... 4-20

Contents-2 RMS GSM Operator Manual

RMSTOC.fm Modified: 13 Jun 2002

Using Radar Diagrams....................................................................... 5-1About Radar Diagrams................................................................. 5-2

About the Radar Diagram Launcher..................................... 5-2About Application Groups...................................................... 5-2Viewing a subset of PLMNs................................................... 5-3

Using the Radar Diagram Launcher ........................................... 5-4Starting Radar Diagrams from the Radar DiagramLauncher ................................................................................. 5-4Setting up a default set of Radar Diagrams ......................... 5-6

Understanding Radar Diagrams.................................................. 5-7What you see........................................................................... 5-7Each axis represents a measurement ................................... 5-7Measurement results are calculated ..................................... 5-8Measurement results are normalised.................................... 5-8Identify worst case results ..................................................... 5-8

Interpreting the Radar Diagram.................................................. 5-9Viewing performance against warning & criticalthresholds................................................................................ 5-9Origin offset ............................................................................ 5-12Incomplete measurements ..................................................... 5-12Loss of traffic .......................................................................... 5-13Monitoring a subset of PLMNs.............................................. 5-14Managing your workspace ..................................................... 5-14

Getting more detail ....................................................................... 5-15Closing a Radar Diagram ............................................................. 5-16

Closing all displays................................................................. 5-16

Using Active Histograms ................................................................... 6-1About Active Histograms.............................................................. 6-2Starting an Active Histogram ...................................................... 6-3Understanding Active Histograms .............................................. 6-4

What you see........................................................................... 6-4Each bar is the measurement result for a PLMN ................ 6-4Measurement results are calculated ..................................... 6-5Measurement results are normalised.................................... 6-5Identifying worst case results................................................ 6-5Maintaining the order PLMNs are displayed ....................... 6-6Searching for a specific PLMN .............................................. 6-7



Interpreting the Active Histogram .............................................. 6-8Viewing performance against warning & criticalthresholds................................................................................ 6-8Excluding a PLMN from measurements............................... 6-10Incomplete measurements ..................................................... 6-10Loss of traffic .......................................................................... 6-11Managing your workspace ..................................................... 6-11

Getting more detail ....................................................................... 6-12Closing an Active Histogram........................................................ 6-13

Closing all displays................................................................. 6-13

Using Time Series Histograms......................................................... 7-1About Time Series Histograms .................................................... 7-2Starting a Time Series Histogram ............................................... 7-3

Starting a Time Series Histogram from the Alarmogram ... 7-3Starting a Time Series Histogram from an ActiveHistogram ............................................................................... 7-4

Understanding Time Series Histograms ..................................... 7-5What you see........................................................................... 7-5Each bar shows one measurement interval .......................... 7-7Measurement results are calculated ..................................... 7-8You can easily identify worst case results ............................ 7-8

Interpreting & manipulating the Time Series Histogram.......... 7-11Showing the value of the bar measurement ......................... 7-11Viewing other measurements ................................................ 7-11Changing between Threshold and Data Value scaling ........ 7-12Viewing error measurements................................................. 7-13Exploding Errors into separate histograms.......................... 7-20Viewing all errors or only unmasked errors ......................... 7-21Incomplete measurements ..................................................... 7-22Loss of traffic .......................................................................... 7-22Managing your workspace ..................................................... 7-23

Closing a Time Series Histogram................................................. 7-24Closing all displays................................................................. 7-24

Using the Alarm Management Reporter........................................ 8-1Reporting on Alarms..................................................................... 8-2

Setting up a scheduled report ................................................ 8-2Generating an instant report................................................. 8-5

What does the report show? ......................................................... 8-9



Using the Customer Care Web Interface ....................................... 9-1About the CCWI............................................................................ 9-2Showing the CCWI........................................................................ 9-3

Starting the web browser and viewing CCWI information.. 9-3New search.............................................................................. 9-5

Closing the CCWI ......................................................................... 9-6

RMS GSM Measurements ..................................................................A-1Summary of procedures & measurements...................................A-2Update Location (UL) measurements..........................................A-5

UL volume...............................................................................A-5UL errors.................................................................................A-5UL error rate...........................................................................A-6UL absence..............................................................................A-6UL Average Transaction Length ...........................................A-7

Provide Roaming Number (PRN) measurements .......................A-8PRN volume ............................................................................A-8PRN errors ..............................................................................A-8PRN error rate ........................................................................A-9PRN absence ...........................................................................A-9PRN Average Transaction Length.........................................A-10

Forward Short Message (FSM) measurements...........................A-11FSM volume............................................................................A-11FSM errors ..............................................................................A-11FSM error rate........................................................................A-12FSM absence ...........................................................................A-12

Send Parameters (SP) measurements .........................................A-14SP volume ...............................................................................A-14SP errors .................................................................................A-14SP error rate ...........................................................................A-15SP absence ..............................................................................A-15SP Average Transaction Length............................................A-16

Total MAP measurements............................................................A-17Total MAP volume..................................................................A-17Total MAP errors....................................................................A-17Total MAP error rate..............................................................A-18Total MAP absence.................................................................A-18

SCCP Messaging (SCCP) measurements ....................................A-20SCCP volume ..........................................................................A-20SCCP errors ............................................................................A-20SCCP error rate ......................................................................A-21SCCP absence .........................................................................A-21



Roamers’ Terminating Calls (RTC) measurements ....................A-22RTC volume ............................................................................A-22RTC errors ..............................................................................A-23RTC error rate ........................................................................A-23RTC absence ...........................................................................A-24RTC Average Transaction Length.........................................A-24

CAMEL measurements ................................................................A-25CAMEL volume ......................................................................A-25CAMEL errors ........................................................................A-25CAMEL error rate ..................................................................A-26CAMEL absence .....................................................................A-26

USSD measurements....................................................................A-28USSD volume..........................................................................A-28USSD errors............................................................................A-28USSD error rate......................................................................A-29USSD absence.........................................................................A-29

GPRS measurements ....................................................................A-31GPRS volume..........................................................................A-31GPRS errors ............................................................................A-31GPRS error rate......................................................................A-32GPRS absence .........................................................................A-32

Normalised measurements...........................................................A-34Measurement performance limits ................................................A-36

General....................................................................................A-367-Day Alarmogram option......................................................A-36



1

1

Introduction to RMS GSMThis chapter provides a brief introduction to the Roaming ManagementSystem GSM (RMS GSM) and to the contents of this manual. It contains:

• a brief explanation of the system’s purpose, how it can be of use,how it is structured and what measurements it makes;

• an overview of the main tasks you can perform with RMS GSM;• an overview of the manual contents.

RMS.01_Intro.fm Modified: 2002 Mid v.0.3

Introduction to RMS GSMWhat is RMS GSM?

1
What is RMS GSM?
Background

The ability to roam in foreign networks is one of the most powerfulcapabilities of GSM. It does, however, bring two new challenges to theGSM service provider: the management of your own subscribers whilethey are not under your direct control, and the management of otherPLMNs’ subscribers.

To run a cellular network profitably, a key goal is to retain subscribers,especially those of high value such as business subscribers using theirGSM phone for work while travelling.

In addition, subscribers from abroad who roam in your network oftenmake a large number of long duration calls back to their country of origin,and receive a number of calls and short messages from home. Theseroaming customers generate revenue just by being in your network, butcan choose to use your network or that of one of your competitors.

To retain customers it is essential to offer a first-class quality of service –poor service may lose you subscribers and revenue. Service outages mustbe detected quickly, to minimise loss of service to the users.

What does RMS GSM do?

RMS GSM helps maximize the availability of crucial roaming functionsbetween home and foreign networks. It monitors the SS7 messagingbetween GSM networks, highlighting problems experienced bysubscribers from your network while abroad, or by foreign subscribersroaming in your network.

RMS GSM gathers data about the key roaming procedures between yournetwork and other PLMNs, in terms of volume and error rate. From this,it generates information about the roaming status. It displays thisinformation in a variety of graphical forms, allowing you to quickly andeasily identify problem areas. The displays are updated regularly, at theend of each measurement time interval, to ensure that you haveup-to-date information.

1-2 RMS GSM Operator Manual

RMS.01_Intro.fm Modified: 2002


1
Measurement interval The measurement interval is set when the system is installed, andcan be between one minute and one hour. This means that RMScan be set up to give the optimum measurement time for yourorganisation and the other PLMNs you are monitoring.
The system displays deviations from the expected behaviour of the serviceas they happen, giving early warning of critical conditions. Problems canthen be fixed before they lead to loss of revenue or subscribers.

In addition to monitoring the performance of roaming procedures, you canuse RMS for detailed investigation of problems.

What does RMS GSM measure?

Procedures

RMS GSM monitors the following GSM roaming procedures:

• Update Location (UL)• Provide Roaming Number (PRN)• Forward Short Message (FSM)1

• Send Parameters (SP)• The sum of all MAP procedures

Other procedures are available as optional Function Upgrades2:

• If you have purchased the RTC+SCCP Function Upgrade, RMSGSM also monitors the network to determine Roamers’ TerminatingCalls (RTC), and for SCCP messaging measurements.

• If you have purchased the CAMEL + USSD Function Upgrade,RMS GSM also monitors CAMEL services as a whole and USSDservices as a whole.

• If you have purchased the GPRS Function Upgrade, RMS GSM alsomonitors the update GPRS location procedure.

1. In MAP 2+, FSM is split into FSM-MO and FSM-MT. RMS GSM combines theseinto one generic FSM procedure.

2. See “Standard & Optional Features”, on page 1-14 for information on FunctionUpgrades.

RMS GSM Operator Manual 1-3



1
Measurements
For each procedure it measures:

• Volume: the amount of procedures initiated or received by a PLMN.• Errors: the number of errors received.• Error Rate: the failure rate for each type of procedure initiated or

received by a PLMN.• Absence: the amount of time for which messages have not been sent

or received by a PLMN.

Where appropriate, it also measures:

• Average Transaction Length: the average amount of time it takes tocomplete a transaction.

For each measurement, your System Administrator can set warnings andcritical threshold values. RMS GSM indicates on its displays whenmeasurements exceed their warning and critical thresholds.

Procedures

Measurements

Volume ErrorRate Absence Errors ATL

UL ✓ ✓ ✓ ✓ ✓

PRN ✓ ✓ ✓ ✓ ✓

FSM ✓ ✓ ✓ ✓

SP ✓ ✓ ✓ ✓ ✓

MAP ✓ ✓ ✓ ✓

Fu

nct

ion

Up

grad

es

SCCP ✓ ✓ ✓ ✓

RTC ✓ ✓ ✓ ✓ ✓

CAMEL ✓ ✓ ✓ ✓

USSD ✓ ✓ ✓ ✓

UL_GPRS ✓ ✓ ✓ ✓




1
RMS GSM maintains a history of the last 24 hours data for eachmeasurement1.
See Appendix A, “RMS GSM Measurements”, for details of all the typesand classes of measurements used.

What particular problems can it detect?

With this combination of procedure measurements you can use RMS todetect and monitor many conditions, including:

• Remote networks with large numbers of your subscribers roamingin them, or large numbers of foreign subscribers roaming in yournetwork.

• Large numbers of calls routed to your subscribers while roaming, orto foreign subscribers roaming in your network.

• Large numbers of Short Messages routed into or out of yournetwork, possibly indicating misuse of the service.

• Subscribers attempting to roam abroad and having problems withregistration, or subscribers roaming within your networkexperiencing registration problems.

• Problems routing calls to subscribers roaming abroad, or to roamersin your network.

• Major connectivity failures between networks.• Problems with subscribers having access to the network, but still

being unable to terminate calls.• Roamers unable to use CAMEL or USSD services.2

• Roamers unable to use GPRS services.3

1. If you have purchased the optional 7-day Alarmogram + Customer Care WebInterface Function Upgrade, RMS GSM gives you access to up to 7 days of dataon the Alarmogram and Time Series Histogram (TSH) displays. See “Standard& Optional Features”, on page 1-14 for information on Function Upgrades.

2. If you have purchased the optional CAMEL + USSD Function Upgrade.3. If you have purchased the optional GPRS Function Upgrade.




1
How does RMS GSM get its data?
RMS GSM is integrated with Agilent’s acceSS7 system, which monitorsSS7 signalling links to provide the required data.

Technical detail Agilent acceSS7 monitors SS7 signalling links and transports theraw SS7 signalling units onto the system hardware’s cardcagebackplane. Interface Processor Cards (IFPCs) collect rawsignalling data from the backplane and perform initial processing.The SS7 Data Broker (SDB) brings all the relevant data from theIFPCs and passes this to RMS GSM.




1
How does RMS GSM present the data
RMS GSM provides you with a variety of different graphical displays formonitoring roaming status:

• The Alarmogram covers multiple networks and, for a selectednetwork, multiple measurements (to and from the home network).It is a powerful visual tool, giving both high level and detailed viewsover a rolling time period1. It indicates when critical alarmthresholds have been exceeded. The high level view shows a history

1. 24 hours as standard, up to 7 days with 7-day Alarmogram + Customer CareWeb Interface Function Upgrade. See “Standard & Optional Features”, onpage 1-14 for information on Function Upgrades.

where you can view in detailthe performance of onemeasurement at one sourceover a period of time.

Radar Diagrams

... and then call up more detail on...

Active Histograms

where you canidentify where theproblem isoccurring

... and then call up more detail on...

Time Series Histograms

where you can identifywhat problem exists

ORThe Alarmogram




1
for each PLMN you are monitoring. For a selected PLMN, adrilldown view shows details for each measurement.
• Radar Diagrams cover multiple networks and multiplemeasurements (to or from the home network). Each Radar Diagramgives you a high level view of several measurements for all thePLMNs you are monitoring. It shows the worst-case (highest) valuefor a set of measurements throughout the monitored network. Theset of measurements displayed on each Radar Diagram is set up byyour System Administrator during system configuration.

• Active Histograms cover multiple networks for a singlemeasurement (either to or from the home network). Each ActiveHistogram gives you detailed information about which PLMN theproblem is occurring in. It displays the PLMNs giving theworst-case (highest) values for a specific measurement.

• Time Series Histograms cover a single network for a singlemeasurement (either to or from the home network). Each TimeSeries Histogram gives you a bar chart showing performance of onemeasurement for one PLMN over a period of time. Details are alsodisplayed of the most common errors encountered. The number oferrors – N – is set when the system is installed. Time SeriesHistograms display data for the same time period as theAlarmogram.

If your system is running acceSS7 OpenView, you can also view a RoamingMap. This shows PLMNs, and groups of PLMNs, on a geographical map.

Roaming Maps show a geographical representations of the PLMNs youare monitoring. You can view a Roaming Map at different levels ofresolution. You could, for example, view all of the different geographicalareas in the world, or you could home in on one particular geographicalarea to view the PLMNs within it. Roaming Maps will show when aPLMN is normal, or when it has crossed warning or critical threshold forany measurement. From the Roaming Map you can drill down to theAlarmogram or Radar Diagrams to find out more information about theproblem.

Roaming Mapshows PLMNs, and groupsof PLMNs, and let you viewwhere problems exist



Introduction to RMS GSMOverview of Operator Tasks

1
Overview of Operator Tasks
Your main tasks as an Operator of RMS GSM are:

• Monitoring roaming procedures for your own subscribers roamingin other PLMNs and visiting subscribers roaming in your network.

• Investigating details of any performance problem, or potentialproblem, signalled by RMS GSM.

• Monitoring details after corrective action has been taken.

This section outlines how to use RMS GSM to perform these generaltasks. Chapters 3 to 8 provide more detailed information on how to use theRMS GSM displays and features when performing these tasks.

Monitoring performance

To monitor the status of PLMNs overall, use the higher level displays: theRoaming Map, Alarmogram and Radar Diagrams. These use colour codingto draw your attention to problems.

When a display indicates that a problem has occurred, you can drill downusing the other displays to get further information to investigate thesource and cause.

Roaming Map and Radar Diagram displays are updated after eachmeasurement interval. The Alarmogram displays information that isaggregated by an aggregation factor.

Aggregation period This is the period covered by each block on the Alarmogram, and isalways a whole number of measurement intervals. This number,the aggregation factor, is set by your System Administrator.

In addition to monitoring these higher level displays, you can also set upalarms to generate regular Alarm Reports at scheduled intervals, or aone-off instant report whenever needed.




1
Investigating problems
When the colour coded indicators on the Alarmogram, Roaming Map orRadar Diagrams indicate that a PLMN has exceeded the warning orcritical threshold, you can drill down using other views to identify thesource and cause of the problem.

Investigating problems from the Alarmogram

The Alarmogram is split into two parts.

The PLMN Overview in the toppane shows the history of thegeneral condition of all PLMNs. 1. Select a PLMN here

to see measurementsummary informationhere.The Measurement Summary

(the lower two panes) showsmeasurement summaryinformation for allprocedure-measurementcombinations for the PLMNselected in the PLMN Overview.

2. Click a measurement to see theTime Series Histogram for thatmeasurement.




1
Investigating Problems from the Roaming Map
The Roaming Map shows a geographical representation of all PLMNs, orgeographical areas.

If a PLMN crosses the warning threshold for any of its measurements, itsicon will change from green to yellow. If it crosses the critical threshold itsicon will change to red. You will know that a problem exists, but cannotdetermine from this view which type of problem.

You can drill down to the Radar Diagrams to identify the problem.

Click on a PLMN in the RoamingMap to display Radar Diagrams.




1
Investigating Problems from a Radar Diagram
The Radar Diagram shows which procedure-measurement combinationshave crossed the warning or critical threshold.

2. Click on a particular PLMN to display the Time SeriesHistogram for that measurement for that PLMN. This displaysthe full data for that measurement for the complete datastorage period.

1. Click on an axis of the Radar Diagram to home in on aparticular measurement. This displays the Active Histogramfor that procedure-measurement combination




1
Monitoring problem solutions
After a problem has been fixed, you may want to check the effectiveness ofany corrective action.

In addition to general monitoring by means of the Roaming Map andAlarmogram or Radar Diagrams (or their icons), it is possible to show thespecific Active Histogram(s) and Time Series Histogram(s) that indicatedthe original problem.

When it is clear that the problem has been fixed, you can close the detailedwindows and return to general monitoring.

Once again, you can generate both regular (periodic) Alarm Reports andone-off (instant) reports.



Introduction to RMS GSMStandard & Optional Features

1
Standard & Optional Features
RMS GSM consists of a base product with optional extensions – FunctionUpgrades. This manual covers standard features and Function Upgrades:it highlights any areas that only apply if you have purchased a particularFunction Upgrade.

Currently available Function Upgrades

RTC+SCCP Function Upgrade

The Roamer Terminated Call (RTC) measurement correlates a ProvideRoaming Number (PRN) request with the subsequent outgoing ISUPcall-leg. This procedure is supported in the same way as the standardprocedures.

The SCCP measurement provides a real-time analysis of SCCPUDT/UDTS messages. This procedure is supported in the same way as thestandard procedures.

RMS Database Extended Aggregation Function Upgrade

The Extended Aggregation puts additional tables of aggregated data intothe RMS Database. You can then use the aggregated data to create morecomprehensive reports (for example), presenting information in an easilyunderstandable manner.

Any tool that can access RMS’ Oracle database (e.g. Microsoft Access, SQLPlus, Toad) can also take advantage of the extra features offered by theRMS Database Extended Aggregation.

7-day Alarmogram + Customer Care Web Interface Function Upgrade

The 7-Day Alarmogram extends the data range to allow users to viewAlarmograms and Time Series Histograms for up to seven days.

Customer Care Web Interface provides a web-based interface toAlarmogram data. This allows Customer Care staff to review seven days’data on any roaming partner via the world wide web.




1
TDR Feed Function Upgrade
The TDR feed provides real-time delivery of Transactional Data Records.This provides the raw data that operators can use to drive their ownhome-grown applications. TDR gives the potential to access extra businessinformation to assist with areas such as network operations and planning,marketing, fraud detection and billing verification.

CAMEL + USSD Function Upgrade

Measurements for CAMEL services as a whole and USSD services as awhole, for both inbound and outbound roamers.

GPRS Function Upgrade

Measurements of the update GPRS location procedure for inbound andoutbound roamers. This is a MAP Phase 2+ procedure originating in theSGSN controlling the routing area in which the mobile station is roaming,and terminating at the HLR.




1
Standard Features & Function Upgrades
Standard Features Function Upgrades

Procedures monitored Update Location (UL)Provide Roaming Number (PRN)Forward Short Message (FSM)Send Parameters (SP)Total MAP procedures.

RTC + SCCPCAMEL + USSDGPRS

Measurements VolumeErrors, Error RateAbsenceAverage Transaction Length

GUI AlarmogramRadar DiagramsActive HistogramsTime Series Histograms

Configuration PLMNsNormalisation GroupsExcluded ProceduresWarning and Critical ThresholdsError MessagesRadar DiagramsSystem ParametersColoursUser PermissionsError Masking

Measurement History 24 hours (Alarmograms and TimeSeries Histograms)

7-day Alarmogram +Customer Care WebInterface

Customer Care

Other outputs TCP/IP Alarm Feed TDR Feed

RMS Database ExtendedAggregation



2

2

Getting StartedThis chapter explains how to start the GSM Roaming ManagementSystem (RMS GSM). It also provides some general information thatapplies to all of the different RMS GSM displays. It contains:

• an explanation of how to start and stop RMS GSM;• a description of what you initially see when you start the system;• instructions on how to end your RMS GSM session;• instructions on how save copies of the RMS GSM displays for future

use.

RMS.02_Starting.fm Modified: 13 Jun 2002 Mid v.0.3

Getting StartedStarting & stopping RMS GSM

2

Starting & stopping RMS GSM

Starting acceSS7

Your System Administrator will have configured acceSS7 to runautomatically when your servers are running and you start up yourworkstation. Log on as explained in the acceSS7 Operator Manual.

When you log on, you will see the Application Manager, which containsgroups for acceSS7 Administration, acceSS7 Applications, RMS GSMAdministration (ARIA_Admin) and RMS GSM Applications (ARIA_Apps).Your System Administrator will have enabled applications for you.

Note The Application Manager is a component of the HP/UX CDE GUI.

Starting RMS GSM Displays

There are two ways that you can start the different RMS GSM displays:

• from icons contained in the Application Manager;• from OpenView (only applies if your system uses OpenView).

The RMS GSM icons are contained in the RMS GSM Applications group(ARIA_Apps). These will always be present.

OpenView is contained in the acceSS7 Applications group. This will onlybe present if your system uses OpenView.


RMS.02_Starting.fm Modified: 13 Jun 2002

Getting StartedStarting RMS GSM displays from the Application Manager

2

Starting RMS GSM displays from the ApplicationManager

In the RMS GSM Applications group (ARIA_Apps) you will find icons forthe Alarmogram, the Radar Diagram Launcher and the AlarmManagement Reporter. Double click on the appropriate icon to launch anapplication.

Starting the Alarmogram

To start the Alarmogram, double click on:

See Chapter 4 for details on using the Alarmogram.

Note The Alarmogram displays results for all PLMNs. Only oneAlarmogram can be started on any Common DesktopEnvironment display.

Starting the Radar Diagram Launcher

Radar Diagrams are started through the Radar Diagram Launcher. TheRadar Diagram Launcher lets you select which Radar Diagrams, fromyour set of Radar Diagrams, you want to launch. To start the RadarDiagram Launcher, double click on:

See Chapter 5 for details on the Radar Diagram Launcher and RadarDiagrams.



Getting StartedStarting RMS GSM displays from the Application Manager

2

Starting the Alarm Management Reporter

To use the Alarm Management Reporter, double click on:

See Chapter 8 for details of using the Alarm Management Reporter.



Getting StartedStarting RMS GSM displays from OpenView

2

Starting RMS GSM displays from OpenView

Starting OpenView

If your system uses OpenView, then in the acceSS7 Applications group youwill find an icon for the OpenView Map. Double click on this icon to startOpenView.

From the OpenView Map you can start the Roaming Map, theAlarmogram, Radar Diagrams and the Radar Diagram launcher.

From the Roaming Map you can start the Alarmogram, Radar Diagramsand the Radar Diagram Launcher.

Starting the Roaming Map

From the OpenView Map:

1. Select Submap from the Map pull-down menu.2. Select Open/List from the displayed options.3. Select the Roaming Map from the displayed list, and click on OK.




2

Alternatively, double click on the Roaming Map icon:

The Roaming Map is displayed, for example:

The objects shown on the Roaming Map are PLMNs and geographicalareas. The above example shows a single geographical area.

Double click




2

Starting the Alarmogram

From the Roaming Map or OpenView Map:

1. Click the Roaming pull-down menu.2. Select Alarms.3. Select Alarmogram.

Starting Radar Diagrams

There are three different ways to launch Radar Diagrams from theRoaming Map and the OpenView Map.

• Directly from the Roaming Map by double clicking on one or aselection of PLMNs – see “Selecting PLMNs for monitoring in RadarDiagrams”, on page 3-4.

• From the Roaming pull-down menu on the Roaming Map orOpenView Map.

• By launching the Radar Diagram Launcher from the Roamingpull-down menu on the Roaming Map or OpenView Map, and thenselecting the Radar Diagrams you want to launch. The RadarDiagram Launcher lets you select which Radar Diagrams, from yourset of Radar Diagrams, you want to launch.

Starting Radar Diagrams from the Roaming Map or Openview Map

From the Roaming Map or OpenView Map:

1. Click the Roaming pull-down menu.2. Select Roaming GUI.3. Select Radar Diagrams. If you have previously set up a default

subset of Radar Diagrams using the Radar Diagram Launcher, thenit is this subset that will be launched. Otherwise, all of your RadarDiagrams will be launched.




2

Starting the Radar Diagram Launcher

The Radar Diagram Launcher lets you select which Radar Diagrams youwant to launch. It also lets you specify a default subset, and it will be thissubset that is launched until you select another set.

From the OpenView Map or Roaming Map:

1. Click the Roaming pull-down menu.2. Select Roaming GUI.3. Select Radar Diagram Launcher.

Note On Radar Diagrams you can monitor the performance of allPLMNs or of a selected subset of PLMNs. You can select the subseteither on the Roaming Map or from the Radar Diagram launcher.



Getting StartedEnding an RMS GSM session

2

Ending an RMS GSM session

To end your RMS GSM session, close the Alarmogram, the Radar DiagramControl Panel, and all the Radar Diagrams, Active Histograms and TimeSeries Histograms you currently have open.

Logging off from acceSS7

Log off as explained in the acceSS7 Operator Manual.

What happens when a shutdown occurs

Shutdown

If the system is stopped intentionally by an Admin user, a “System Stop”warning message will be displayed giving information about the shutdownand the active front-end components will shut down. Terminals willunregister with the database.

If a serious problem occurs with the back-end Oracle database anyattached terminals may be running a variety of utilities, Alarmograms,Active Histograms, etc. These will normally stop without warning.

Restart after a shutdown

If you attempt to restart after a system stop and the alert is still in effectyou will be notified that an enforced stop is active.

After the problem has been cleared the system will restart normally. Datalost during the shutdown will cause gaps in the displays but historicaldata already saved in the database will display correctly.



Getting StartedSaving and printing displayed information

2

Saving and printing displayed information

From any of the RMS GSM displays, you can print and/or save to file thecurrently displayed information. You can save the display in either textformat or graphics format. You may want to do this to document particularproblems as they occur.

Saving a data snapshot

To save a data snapshot of any window, select the Save Data... option onthe File menu. This will save the raw data used to generate the currentimage in a text format.

Saving a graphical snapshot

To save a graphical snapshot of any window, select the Save Graphics...option on the File menu. This will save the current image as a bitmap file.

Printing a display

To send an image of the current display to the current printer, selectPrint... from the File menu.



3

3

Using the Roaming MapThis chapter introduces the Roaming Map and explains how you can use itto monitor PLMNs and to select PLMNs for further monitoring usingRadar Diagrams.

Note You will only have access to the Roaming Map if your system hasOpenView installed. If your system does not use OpenView, thenyou should turn to the other chapters for information on how touse other RMS GSM displays.

RMS.03_Roaming.fm Modified: 13 Jun 2002 Mid v.0.3

Using the Roaming MapAbout the Roaming Map

3

About the Roaming Map

The Roaming Map is a geographical display showing the PLMNs you aremonitoring with RMS GSM.

To make it easier to view PLMNs they can be grouped in geographicalareas. Clicking on a geographical area zooms in on that area to show thePLMNs, and any other geographical areas, contained within it.

The above example shows a single, high-level geographical area.

Your System Administrator will have set up the Roaming Map withPLMNs and geographical areas.

Geographical area


RMS.03_Roaming.fm Modified: 13 Jun 2002


3

You can use the Roaming Map to monitor the overall performance ofPLMNs. If a PLMN crosses a warning threshold its icon on the RoamingMap will change from green to yellow. If it crosses a critical threshold itsicon will change to red.

From the Roaming map you can drill down to view Radar Diagrams for allPLMNs or a selection of PLMNs.

Zooming in and out of a geographical area

Double click on a geographical area to show the PLMNs and anysubsidiary geographical areas it contains, for example:

You can move down through several levels of geographical areas in thisway.

PLMNs




3

To move back up to a higher level of geographical area, click on the uparrow symbol on the toolbar:

Selecting PLMNs for monitoring in Radar Diagrams

On Radar Diagrams you can monitor the performance of all PLMNs or of aselected subset of PLMNs.

To monitor a subset of PLMNs on Radar Diagrams, and subsequent ActiveHistograms, you must first select them from the Roaming Map.

Selecting all PLMNs on the map

To monitor all PLMNs that appear on the Roaming Map on RadarDiagrams, leave them all unselected – they are all then monitored bydefault.

Selecting a subset of PLMNs from the map:

To monitor a selection of PLMNs on Radar Diagrams, select the requiredPLMNs by holding down the Ctrl key and clicking on each PLMN in turn.Selected PLMNs are highlighted, for example:

Click here to move up a level

Selected PLMNs




3

Alternatively, to select all PLMNs in a rectangular area, click and hold theleft mouse button at one corner of the rectangle, drag to the diagonallyopposite corner, then release the mouse button, for example:

Caution If you select only some PLMNs and drill down to Radar Diagrams,these will be the only PLMNs you are monitoring. If a problemoccurs within a PLMN you have not selected, it will not be flaggedon the Radar Diagram (though it will still be flagged on theRoaming Map).

Selecting all PLMNs in a geographical area

To select all the PLMNs within a defined geographical area, click on theappropriate geographical area icon. If the geographical area containsother geographical areas then this also selects the PLMNs in these lowerlevel areas, and so on down through multiple levels.

To select the PLMNs from multiple geographical areas, hold down theCtrl key and click on the icon for each area it turn.

You can select a mixture of PLMNs and geographical areas.

Click and hold...

... and drag...

... and release.



Using the Roaming MapGetting more detail

3

Getting more detail

To display the Alarmogram from the Roaming Map (or from the OpenViewMap), see “Starting the Alarmogram”, on page 2-3.

To display Radar Diagrams from the Roaming Map (or from the OpenViewMap), see “Starting Radar Diagrams”, on page 2-7.

You can also double click on a PLMN selection on the Roaming Map todisplay the Radar Diagrams for the selected subset of PLMNs.

Note If a Radar Diagram of interest already has its icon displayed,double click on the icon to restore the window.



4

4

Using the AlarmogramThis chapter explains how to use the Alarmogram to monitor each PLMN.It contains:

• an introduction to the Alarmogram and how information ispresented;

• information on how to interpret and manipulate the Alarmogramdisplay

• instructions on how to get more detail about a particular PLMN andmeasurement.

RMS.04_Alarmogram.fm Modified: 2002 Mid v.0.3

Using the AlarmogramAbout the Alarmogram

4

About the Alarmogram

The purpose of the Alarmogram is to show a rolling history of criticalevents in all measurements for all the PLMNs configured for your system.

The Alarmogram is updated at the end of each aggregation period toensure that you are kept up-to-date on performance.

Aggregation period This is the period covered by each block on the Alarmogram, and isalways a whole number of measurement intervals. This number,the aggregation factor, is set by your System Administrator.

Data storage and display periods

Standard Alarmogram

The standard Alarmogram stores and displays data for the last 24 hours.

7-day Alarmogram

If you have purchased the 7-day Alarmogram + Customer Care WebInterface Function Upgrade, Alarmogram data will be available for up toseven days. The number of days data that you can view depend on twofactors:

• When the system is installed the maximum number of days datathat will be stored is fixed, up to the maximum of seven. EvenAdmin users cannot change this value.

• When the system is running, Admin users can use the SystemParameter tab in the Configuration Editor to change the number ofdays data that will be displayed, up to the stored maximum.

Definitions

Standard 7-Day

Data Storage Period 24 hours Maximum: 7 days

Data Display Period 24 hours Maximum: Data Storage Period


RMS.04_Alarmogram.fm Modified: 2002

Using the AlarmogramShowing the Alarmogram

4

Showing the Alarmogram

For information on how to start the Alarmogram see “Starting theAlarmogram”, on page 2-3, or page 2-7.

Note The Alarmogram displays results for all PLMNs. Only oneAlarmogram can be started on any Common DesktopEnvironment display.

What you see

Initially, only the top area is filled in, showing the PLMN Overview.



Using the AlarmogramUnderstanding the Alarmogram display

4

Understanding the Alarmogram display

The PLMN Overview in the upper pane of the Alarmogram summarisescritical event violations for all PLMNs. Each row represents a PLMN, andcan show details for the complete data display period. When theAlarmogram starts it displays the most recent history.

The Measurement Summary forms the two lower panes of theAlarmogram and shows detailed event summaries for the selected PLMN.Each row represents a measurement on a procedure. To showmeasurement details for a PLMN, click on that PLMN’s row in the PLMNOverview pane.

The middle pane shows measurements originating from the selectedPLMN; the lower pane shows those terminating in the selected PLMN.

Deselecting a PLMN

Click on the currently selected PLMN in the top pane to deselect it andclear the two measurement panes.

PLMN row

Measurement row

Ranking period




4

Ranking period

The shaded area identifies the current Ranking Period. For more detailson how rows are ranked see “Understanding how rows are ranked”, onpage 4-9.

Date of display

The left end of the Alarmogram, above the time stamps, displays therange of dates currently available for viewing.

Data is available for this period




4

Resizing the PLMN display

The default Alarmogram shows ten PLMN rows at a time and eachMeasurement Overview area shows eight rows. If there are more detailsyou can step through the lists using the scroll bars.

You can adjust the sizes of the three panes using the sizing buttonsbetween the panes. The mouse pointer changes to a cross when it is over asizing button. The PLMN overview pane will never disappear, there willalways be at least one PLMN on display. The measurement panes can beshrunk completely, leaving only the resizing button visible.

Sizing buttons




4

Understanding the Alarmogram colour coding

Each block in the Alarmogram summarises aggregated critical statusresults.

Colours in the Measurement Summary area

The blocks are coloured as follows:

Green: a critical event persisted for less than 50% of theaggregation period.

Yellow: a critical event persisted for 50% or more of theaggregation period.

Red: a critical event persisted for 100% of the aggregationperiod.

Grey: the measurement was not active during the period.

Aggregation period This is the period covered by each block on the Alarmogram, and isalways a whole number of measurement intervals. This number,the aggregation factor, is set by your System Administrator. Inthe above example it is 3.

Status per measurement interval:

Aggregation periods:

Alarmogram blocks:N

orm

al

No

rmal

No

rmal

War

nin

g

War

nin

g

War

nin

g

No

rmal

No

rmal

Cri

tica

l

No

rmal

Cri

tica

l

Cri

tica

l

Cri

tica

l

Cri

tica

l

Cri

tica

l

Green Green Green Yellow Red




4

Colours in the PLMN Overview area

The blocks are coloured as follows:

Red: one or more measurements have a red block active in thisaggregation period.

Yellow: there are no red blocks, but one or more measurementshave a yellow block active in this aggregation period.

Green: all measurements show green blocks in this aggregationperiod.

Grey: the PLMN was not active during the period.

Grey blocks

Grey blocks represent measurements or PLMNs that are not beingmonitored in a particular period. Grey blocks are not included in any ofthe calculations. Grey blocks appear if:

• a PLMN is not being monitored i.e. a PLMN is not enabled in theConfiguration Editor

• a procedure is not being monitored i.e. a procedure is marked asexcluded in the Configuration Editor

• an alarm is disabled i.e. an alarm for a procedure is disabled in theConfiguration Editor.

Block colours The colours you see may be different from the defaults if yourSystem Administrator has configured different colours for yourinstallation. Descriptions in this manual use the default colours.




4

Understanding how rows are ranked

By default, the rows in all three areas are ordered according to the“Olympic medal” rule. The data used for ranking is from a specifiedAlarmogram Ranking Period. The Ranking Period is configurable and isthe number of hours of data to be examined for the ranking process. Whenthe Alarmogram is first opened this period will be up to the latestaggregated data. When new data arrives the ranking period will move toinclude this new data. This means that:

• Rows are ranked first by the number of red blocks they contain overthe Alarmogram Ranking Period. Rows with more red blocks areshown above those with fewer or none.

• Rows with equal numbers of red blocks, or with no red blocks, arethen ranked by the number of yellow blocks they contain. Rows withonly red blocks are ranked alphabetically.

• Rows with equal numbers of yellow blocks, or with no yellow blocks,are then ranked by the number of green blocks they contain. Rowswith only yellow blocks are ranked alphabetically.

• Rows with equal numbers of green blocks, or with no green blocks,are then ranked by the number of grey blocks they contain. Rowswith only green blocks are ranked alphabetically.

• Rows with only grey blocks are ranked alphabetically.

For example:

Each aggregation period, the rows are re-sorted.

If you wish, you can suppress this re-sorting – see “Using and suppressingrow ranking”, on page 4-13.

7 red, 1 yellow

4 red, 2 yellow

4 red, 1 yellow

0 red, 2 yellow

0 red, 1 yellow

0 red, 0 yellow



Using the AlarmogramInterpreting & manipulating the Alarmogram

4

Interpreting & manipulating the Alarmogram

What happens each aggregation period

At the end of each aggregation period:

• A new column of blocks is added at the right hand end of the areasand all blocks move one space left.

• The date and time at which the Alarmogram was last updated, andthe aggregation factor in force at that time, are updated (shown atthe top of the display), and any change in the aggregation factor isflagged.

• Providing auto-ranking is on (the default), the rows of blocks aresorted into their new ranking order.

• Assuming the audio-alarm option is on (the default), an audiblewarning sounds and the Acknowledge Alarm button goes red ifnew red blocks appear.

Viewing Alarmogram data

Using the scroll bars

Each row of the display in the PLMN Summary and MeasurementSummary areas shows 61 blocks, or aggregation periods. Data is availablefor the complete display period. When the Alarmogram opens it displaysthe most recent data. If the required data is not visible you can move thedisplay using the scroll bar at the bottom.

This moves all three areas in synchronization.

Move one blockat a time

Move12blocksat a time




4

Date selection

As well as the standard scrolling methods it is possible to select a date toview.

1. Click on Date in the View menu.The dates displayed will be from the current date back to the startof the data currently being stored. Unless there have been dataproblems this will be for the complete display storage period.

Note If you have a standard Alarmogram this will cover the last 24hours. If you have the 7-day Alarmogram + Customer Care WebInterface Function Upgrade it will cover up to 7 days.

2. Select the required date.

If sufficient data is displayed, it will be centred around midday. This willnot happen if there is not enough data (first and last days for example).

Ranking using different data

When an Alarmogram first displays, the rows are ranked using the mostrecent values. It is possible to rank the data using other time periods.

Click anywhere on the date and time indicators, above the PLMNoverview pane. This will become the mid-point of a new ranking period.When a ranking period is selected in this way it will remain selected asnew data arrives in the Alarmogram.




4

The data in the current ranking period is highlighted in all panes of theAlarmogram by a grey shaded background.

Reset Alarmogram to normal ranking

There are two methods available to reset ranking to cover the most recentdata:

• Select data that covers the most recent available time by clickingnear the extreme right of the time line.

• Right-click anywhere in the time line. This resets the rankingperiod to the most recent data but leaves the display still showingthe same data.

Ranking period




4

Using and suppressing the audible warning

By default, the Alarmogram gives an audible warning if, in the newaggregation period, at least one new red block appears in the PLMNOverview in addition to those reported in the previous period. This meansthat you do not necessarily have to watch the Alarmogram at all times –the audible warning alerts you to major changes.

When the warning sounds, the Acknowledge Alarm button turns red –to stop the alarm, click on this button.

You can turn the audible warning on and off by toggling the Suspend/Resume Audio-Alarm button.

Note that after a timeout period the audible warning is automaticallyre-enabled. The timeout period is set by the Configuration Editor.

Using and suppressing row ranking

By default, the rows in all three areas are re-sorted each aggregationperiod according to the “Olympic medal” rule (see “Understanding howrows are ranked”, on page 4-9).

If you wish, you can suppress this re-sorting and keep the rows displayedin the current order, for example, to avoid confusion when status ischanging rapidly. With Auto-Ranking frozen the rows maintain theircurrent order through each new aggregation period, regardless of the newnumbers of red and yellow blocks.

The Freeze/Resume Auto-Ranking buttons turns the Auto-Rankingfeature on and off.




4

Suspending and resuming screen display

You can suspend the screen display from updating every time period. Youmight find this useful if you want to examine the display at a particularpoint in time. The Suspend/Resume Display button turns the suspendfeature on and off

Finding what aggregation period a block covers

Each aggregation period takes on the timestamp of the first measurementinterval in that block. The timestamps of every 12th block (columns 1, 13,25, 37, 49 and 61) are shown at the top of the display, in days, months,years, hours and minutes. For example:

As new blocks are added at the right, or as you scroll through the periodcovered, the values of the displayed timestamps change to match theblocks currently shown in those positions.

Timestamps




4

Finding the aggregation factor for a block

The current aggregation factor and measurement interval are shown inthe status bar at the bottom of the display. For example:

If your System Administrator changes the aggregation factor, this isindicated. At the top of the display, a small, down-pointing arrow is shownabove the last block before the change. The aggregation factor andmeasurement interval that applies to this column of blocks, and all thoseto the left, is shown above the arrow. For example:

If the aggregation factor is changed several times, there will be severalsuch markers. As new blocks are added at the right, or as you scrollthrough the period covered, these indicators move with their associatedcolumns of blocks.

Note A change to the measurement interval requires your SystemAdministrator to stop and restart RMS GSM.

MeasurementInterval

Aggrega-tion Factor

Changes inaggregation factor




4

Viewing measurement thresholds

The value of the critical threshold for each measurement in theMeasurement Summary areas is shown in brackets:

Finding a specific PLMN

In addition to scrolling through the PLMNs in the PLMN Overview, youcan search for a particular PLMN by either its short name or its full name.Select Search PLMN from the Search menu to display the Searchwindow:

To find a PLMN:

1. Enter either the short name or full name for the required PLMN inthe field. Note that you can use wildcards when specifying thename, for example “*air*” will find all PLMNs whose full names orshort names contain the string “air”.

Critical threshold




4

2. Click on Search. PLMNs whose names match the search patternyou specified will be listed in the Search Results window. Select aPLMN from this list and click on the Select button to highlight thePLMN on the Alarmogram.

Deselecting a PLMN

Click on the currently selected PLMN to deselect it. The two measurementoverview panes will clear.

Viewing the Measurement Summary for a PLMN

To show the measurement details for a PLMN, click on the PLMN’s labelin the PLMN Overview.

Note You can actually click anywhere on the PLMN’s row of blocks – thecursor shows as a pointing hand when you hover it over an areafrom which you can select a PLMN.

Alternatively, select the PLMN from the Search Results list as explainedin “Finding a specific PLMN”, on page 4-16.

The Measurement Summary areas will then display the aggregated statusblocks for all measurements originating from and terminating in thatPLMN.




4

Being aware of data loss

The Alarmogram indicates any missing or bad data over a particularaggregation period with a vertical black bar in all three sections.

A red bar in the time stamps area indicates “No Producer”. A grey barindicates incomplete data.

For example:

Using icons to manage your workspace

To manage your workspace, you can shrink the Alarmogram to an icon byclicking on the shrink button at the top right of the window border:

To expand an icon to show the Alarmogram, double click on it.

A black bar indicatesmissing or bad data duringthe aggregation period

A red over bar indicates“No Producer” during theaggregation period

A grey over bar indicatesincomplete data during theaggregation period

Click here to shrink window to an icon



Using the AlarmogramGetting more detail

4

Getting more detail

From the Alarmogram you can show the history of the measurementresult for a particular PLMN on a Time Series Histogram.

To show the Time Series Histogram, simply click on the measurement’slabel (at the right of the row of blocks).

Note You can actually click anywhere on the measurement’s row ofblocks – the cursor shows as a pointing hand when you hover itover an area from which you can select a measurement.

See Chapter 7, “Using Time Series Histograms” for details.

You can display one Time Series Histogram for each measurement on theAlarmogram.

Caution You can open a maximum of 6 Time Series Histograms on aworkstation at any given time. If your installation includes bothRMS GSM and RMS IS-41, then this limit applies to the totalnumber of Time Series Histograms from both systems.

Note The limit on the total number of windows you are displaying willdepend on the capabilities of your workstation.

The Alarmogram remains displayed when you select a Time SeriesHistogram.



Using the AlarmogramClosing the Alarmogram

4

Closing the Alarmogram

To close the Alarmogram, select the Close option from the File pull-downmenu. Alternatively, double click on the button at the top left of thewindow border:

When you close the Alarmogram, all Time Series Histograms that youhave launched from it will also close.

You may subsequently reopen the Alarmogram as explained in“Startingthe Alarmogram”, on page 2-3, and page 2-7.

Double click here to close window



5

5

Using Radar DiagramsThis chapter explains how to use Radar Diagrams. It contains:

• an introduction to Radar Diagrams and how information isdisplayed;

• information on how to interpret Radar Diagrams;• instructions on how to get more detail about a particular

measurement.

RMS.05_Radar.fm Modified: 13 Jun 2002 Mid v.0.3

Using Radar DiagramsAbout Radar Diagrams

5

About Radar Diagrams

The purpose of the Radar Diagram is to enable you to easily monitor thestatus of a set of measurements for all, or a selection of, PLMNs.

Radar Diagrams can be configured to display only those measurementsyou want to see. RMS GSM allows each Operator to have up to tendifferent Radar Diagram configurations. This means you can view theprecise set of measurements you want to monitor.

Radar Diagrams are configured using the Configuration Editor. If youhave Read/Write Permission for the Configuration Editor, you canconfigure your own Radar Diagrams. If not, your System Administratorwill configure Radar Diagrams for you.

Radar Diagrams are set up on an individual operator basis, and you willbe able to access your own set of Radar Diagrams from any workstation.

Radar Diagrams are updated at the end of each measurement interval toensure that you are kept up-to-date on performance.

About the Radar Diagram Launcher

The Radar Diagram Launcher lets you select which Radar Diagrams tostart, from your set of Radar Diagrams.

It also lets you to select which PLMNs you want to monitor. You might, forexample, choose to monitor a subset of all PLMNs.

If you view the same Radar Diagrams most of the time, you can set up adefault subset. It is this default subset of diagrams that will be startedwhen you launch Radar Diagrams.

About Application Groups

An application group is a group of Radar Diagrams that have beenlaunched together, along with any Active Histograms and Time SeriesHistograms subsequently launched from them.

When you close a Radar Diagram, an Active Histogram or a Time SeriesHistogram that belongs to an application group using the Close Alloption, all members of the group are closed.


RMS.05_Radar.fm Modified: 13 Jun 2002

Using Radar DiagramsAbout Radar Diagrams

5

Viewing a subset of PLMNs

On Radar Diagrams you can monitor the performance of all PLMNs or of aselected subset of PLMNs. You could, for example, monitor differentsubsets of PLMNs on different sets of Radar Diagrams; perhaps monitorall Scandinavian PLMNs on one set of Radar Diagrams and all UKPLMNs on another set.

There are two ways to select a subset of PLMNs for monitoring on RadarDiagrams:

• from OpenView – see “Selecting PLMNs for monitoring in RadarDiagrams”, on page 3-4.

• from the Radar Diagram Launcher.



Using Radar DiagramsUsing the Radar Diagram Launcher

5

Using the Radar Diagram Launcher

Starting Radar Diagrams from the Radar Diagram Launcher1. Start the Radar Diagram Launcher as described in Chapter 2,

“Getting Started”. The Radar Diagram Launcher window, with yourown set of Radar Diagrams, appears.

2. When you first start the Radar Diagram Launcher you will be givenan option to select a subset of PLMNs that you wish to monitor.You can select PLMNs in two ways:• The Network Name option allows you to select individual

networks to be monitored using Ctrl+Click. You can also click onthe All button to select all networks.

RDLMain.Tif




5

• The Country option allows you to choose the country, orcountries, to be monitored. When a country is selected allPLMNs in the country will be monitored.

3. Select the Radar Diagrams you want to launch by clicking on them.Selected Radar Diagrams are highlighted. Individual selections canbe cancelled by clicking on them again. You can cancel allhighlighted Radar Diagram by selecting Clear All from the Editmenu.

4. To launch the Radar Diagrams, select Activate from the Viewmenu (shortcut key Ctrl+A). The Radar Diagrams you select will bepart of one application group, along with any Active Histograms andTime Series Histograms you launch from them.

If you want to name the application group, then select Activatewith Name (shortcut key Ctrl+N). A dialog box appears andprompts you to enter a name for the application group you arelaunching.If you have already selected a subset of PLMNs using OpenView,then these are the PLMNs that will be monitored in the RadarDiagrams you are about to launch.




5

If you have not chosen a default set, then the following dialogue boxappears and prompts you to select the PLMNs you want to monitor.

5. Select the PLMNs you want to launch:• To select all PLMNs, press All. All PLMNs will be monitored by

your chosen set of Radar Diagrams.• To select a subset of PLMNs from the entire list of available

PLMNs, Ctrl+click on the PLMNs you want to monitor andpress OK.

Setting up a default set of Radar Diagrams

The Radar Diagram Launcher lets you set up a default set of RadarDiagrams. If you have a default set and you start Radar Diagrams it is thedefault set that is launched – see “Starting Radar Diagrams”, on page 2-7

1. Start the Radar Diagram Launcher as described in Chapter 2,“Getting Started”. The Radar Diagram Launcher window, with yourown set of Radar Diagrams, appears.

2. Select the Radar Diagrams you want to place in your default set byclicking on them. Selected Radar Diagrams are highlighted.Individual selections can be cancelled by clicking on them again.You can cancel all highlighted Radar Diagram by selecting ClearAll from the Edit menu.

3. Select Save Default from the File menu.



Using Radar DiagramsUnderstanding Radar Diagrams

5

Understanding Radar Diagrams

What you see

Each axis represents a measurement

A Radar Diagram is a polar chart with up to 24 measurements. Each axisrepresents a measurement. The measurements are those that have beenconfigured for the Radar Diagram using the Configuration Editor. A labelat the outer end of each axis identifies the measurement.

The axes are spread evenly around 360 degrees.

Measurement label

Measurement axis



Using Radar DiagramsUnderstanding Radar Diagrams

5

Measurement results are calculated

The actual values plotted are the results of calculations performed on theraw measurement values. See Appendix A, “RMS GSM Measurements”,for details of the calculations performed in each case.

Measurement results are normalised

The measurement results shown are normalised to take account ofnetworks having different capacities.

Note The actual value is the absolute result of the measurement. Thenormalised value is the result after multiplying the absoluteresult by a scaling (normalisation) factor. This factor compensatesfor capacity differences between PLMNs. Normalisation factorsare set up using the Configuration Editor.

For an example of normalisation, see “Normalised measurements”, onpage A-34 of Appendix A.

Identify worst case results

Each axis plots the current worst case (highest) value for its measurementresult, taken over all the monitored PLMNs. For example, if an axis ismonitoring UL volume in the direction from external PLMNs to yourhome network, for three PLMNs (PLMN1, PLMN2 and PLMN3):

• In the first measurement interval, if the UL volumes are:• PLMN1 100• PLMN2 150• PLMN3 120then the value for PLMN2 is plotted on the axis.

• If, in the next measurement interval, the UL volumes change to:• PLMN1 100• PLMN2 130• PLMN3 135then the value for PLMN3 is plotted on the axis.

The plot is updated at the end of each measurement interval.



Using Radar DiagramsInterpreting the Radar Diagram

5

Interpreting the Radar Diagram

Viewing performance against warning & critical thresholds

The Radar Diagram includes circular guides to show the warning andcritical thresholds. The inner circle is the lower (warning) threshold andthe outer circle is the upper (critical) threshold.

Note To keep these guides circular: the scales between origin, warning,critical and maximum levels are automatically adjusted for eachaxis; the relative scales between the axes are also adjusted. Youcan adjust the spacing of the warning level guide between theorigin and the critical level guide (see “Creating a Radar Diagram”in the RMS GSM System Administrator Guide).

The value for a measurement is plotted on the axis. The further away aplotted point is from the centre of the circle the greater the value itrepresents.

Warning threshold

Critical threshold




5

When all the measurements are within the lower threshold, the polygon isgreen. This indicates that all the measurements on the Radar Diagramare normal and are functioning as expected.

When one or more measurement results exceed the lower threshold, butall are still within the upper threshold, the polygon changes to yellow. Thisis a warning, indicating a potential problem.




5

When one or more measurement results exceed the upper threshold, thepolygon changes to red, indicating a problem.

When all plotted values return to within the upper threshold, the polygoncolour returns to yellow. When all the values return to within the lowerthreshold, the polygon colour returns to green.

If the polygon is red or yellow, you may want more detailed informationabout where the problems are located. You can see this detail on an ActiveHistogram – see Chapter 6, “Using Active Histograms”.




5

Origin offset

So that all diagrams, including those with less than three measurements,show sensible polygons, the origins of each axis are offset from the centreso that zero readings of all measurements are shown as a small circle. Theeffect of this is that a single measurement diagram is shown as a thinvertical pointer, and a two measurement diagram as a thin verticaldiamond. For example:

Incomplete measurements

If measurements are not complete due to gaps in the data, this isindicated on the Radar Diagram by the label [Incomplete Data] in thestatus line. This label will disappear at the end of the next measurementinterval during which the data is complete. A gap of even onemeasurement is shown in this way.

Polygon

Origin




5

Loss of traffic

The Radar Diagram indicates any halt in the traffic it is monitoring. If, forany reason, traffic stops (known as “loss of producer”), RMS immediatelydoes the following:

• Removes the active part of the display except the thresholds.• Fills the background of the chart area with the critical colour.• Displays a [No Producers] label in the status bar.

When traffic resumes, the Radar Diagram reverts to normal and shows a[Producer resumed] message in the status bar for the duration of themeasurement interval.

Radar Diagram While “No producer” condition

existsFor rest of the measurement

interval after productionresumes




5

Monitoring a subset of PLMNs

The Radar Diagram shows a PLMN Subset button. For example:

You can click on the Subset button to show a list of the PLMNs in thecurrent subset.

Any PLMNs that you disable using the Active Histogram are indicatedwith an asterisk (*). See “Excluding a PLMN from measurements”, onpage 6-10 for information on how to disable a PLMN.

Managing your workspace

To manage your workspace, you can shrink a Radar Diagram to an icon byclicking on the shrink button at the top right of the window border:

When the Radar Diagram is shrunk to an icon, the icon is an activeminiature representation of the Radar Diagram without the labels. Anycolour changes to the polygon are displayed. To expand an icon to show theRadar Diagram, double click on it.

PLMN Subset button




Using Radar DiagramsGetting more detail

5

Getting more detail

From the Radar Diagram you can show more detail for a particularmeasurement on an Active Histogram. To do this, simply click on themeasurement’s name. See Chapter 6 “Using Active Histograms” fordetails.

You can display one Active Histogram for each measurement on the RadarDiagram, subject to the total window limit for your system.

Note The window limit applies to the total number of windows you aredisplaying. The actual limit will depend on the capabilities of yourworkstation.

The Radar Diagram remains displayed when you select an ActiveHistogram.



Using Radar DiagramsClosing a Radar Diagram

5

Closing a Radar Diagram

To close a Radar Diagram, select the Close option from the File pull-downmenu. Alternatively, double click on the button at the top left of thewindow border:

When you close a Radar Diagram, all the Active Histograms and TimeSeries Histograms that you have launched from it will also close. Notethat this will not close any Active Histograms and Time SeriesHistograms that you have launched from a different Radar Diagram.

Closing all displays

You can also close all Radar Diagrams in this application group, and allActive Histograms and Time Series Histograms started from them. To dothis, select the Close All option from the File pull-down menu. Note thatthis will not close the Alarmogram or any Time Series Histograms startedfrom it, or any Radar Diagrams, Active Histograms and Time SeriesHistograms in any other application group.

Note An application group is a group of Radar Diagrams that have beenlaunched together, along with any Active Histograms and TimeSeries Histograms launched from them.

You may subsequently restart Radar Diagrams as explained in Chapter 2,“Getting Started”.




6

6

Using Active HistogramsThis chapter explains how to use Active Histograms. It contains:

• an introduction to Active Histograms and how information isdisplayed;

• information on how to interpret Active Histograms;• instructions on how to get more detail about the history of a

particular measurement on a Time Series Histogram.

RMS.06_Active.fm Modified: 13 Jun 2002 Mid v.0.3

Using Active HistogramsAbout Active Histograms

6

About Active Histograms

The purpose of the Active Histogram is to show the status of a singlemeasurement for each of the PLMNs you are monitoring. This is moredetailed information than in a Radar Diagram, as it indicates in whichPLMN a problem exists.

Active Histograms are updated at the end of each measurement intervalto ensure that you are kept up-to-date on performance.


RMS.06_Active.fm Modified: 13 Jun 2002

Using Active HistogramsStarting an Active Histogram

6

Starting an Active Histogram

To start an Active Histogram, select the required measurement from aRadar Diagram by clicking on the measurement’s label, for example:

The Active Histogram for this measurement is then displayed.

Click on measurement label



Using Active HistogramsUnderstanding Active Histograms

6

Understanding Active Histograms

What you see

The status line displays the Total number of PLMNs exceeding eitherthreshold and the numbers exceeding the warning and critical thresholds.

Each bar is the measurement result for a PLMN

An Active Histogram displays a set of horizontal bars, each representingthe measurement result, for the most recent interval, for a differentPLMN. Ten bars are shown; if more PLMNs are being monitored you canscroll down the list one bar at a time.

To the left of each bar is a button. The label on the button states thePLMN Name and Network Type. Clicking on a button drills down to theTime Series Histogram for that PLMN.

Measurement bar

PLMN name

Scroll bar




6



Measurement results are normalised

The length of each bar represents the normalised measurement result forthat PLMN. To the right, the current normalised and actual numericalvalues are shown (the actual value in brackets).

Note The actual value is the absolute result of the measurement. Thenormalised value is the result after multiplying the absoluteresult by a scaling (normalisation) factor. This factor compensatesfor capacity differences between PLMNs. Normalisation factorsare set up using the Configuration Editor – see the RMS GSMSystem Administrator Guide.

For an example of normalisation, see “Normalised measurements”, onpage A-34 of Appendix A.

Identifying worst case results

By default, the bars are displayed in descending order, with the worst-case(largest) value at the top of the list – this is also the top bar on the displayunless you have scrolled down the list. That is, the bar at the top of the listis for the PLMN with the highest normalised measurement value.

Measurement result values

Worst-case result

Normalised (Actual)




6

Maintaining the order PLMNs are displayed

You may wish to preserve the order in which the PLMNs are displayed,rather than have the PLMNs re-sorted after each measurement interval.Click on Freeze Auto-ranking/Resume Auto-ranking in the Optionsmenu to toggle between the two modes. Auto-ranking will also resumeautomatically after the Freeze Auto-ranking time out expires




6

Searching for a specific PLMN

In addition to scrolling to find a PLMN, you can search for a particularPLMN by either its short name or its full name. Select Find PLMN fromthe Search menu to display the Search window:

To find a PLMN:

1. Enter either the short name or full name for the required PLMN inthe field. Note that you can use wildcards when specifying thename, for example “*air*” will find all PLMNs whose full names orshort names contain the string “air”.

2. Click on Search. PLMNs whose names match the search patternyou specified will be listed in the Search Results window. Select thePLMN you want to look at and click on the Select button to displayit in the active histogram.

After finding multiple PLMNs on a wildcard search the results areretained. Select Search Again from the Search menu (or use theshort-cut key F3) to display the next PLMN on the list. When thelast PLMN is displayed, search again will cycle to the top of the list.



Using Active HistogramsInterpreting the Active Histogram

6

Interpreting the Active Histogram

Viewing performance against warning & critical thresholds

The Active Histogram includes vertical guides to show the warning andcritical thresholds. The left-hand line is the lower (warning) threshold andthe right-hand line is the upper (critical) threshold.

A total box at the bottom of the histogram shows:

• the total number of PLMNs exceeding thresholds;• the number exceeding the warning threshold;• the number exceeding the critical threshold.

The colour of a bar reflects the state of the measurement for its PLMN.The colour changes when the bar crosses the lower or upper thresholds.

Thresholds The thresholds for the measurement are set using theConfiguration Editor, as are the colours for normal, warning andcritical values. The relative positions of the vertical thresholdguides are derived from the parent Radar Diagram.

The longer the bar the greater the value it represents.

Warning threshold Critical threshold




6

When the measurement result for a PLMN is below the lower threshold,the bar is green. This indicates that the measurement for that PLMN isnormal and is functioning as expected.

When the measurement result for a PLMN exceeds the lower threshold,but is still within the upper threshold, the bar changes to yellow. This is awarning, indicating a potential problem.

When the measurement result for a PLMN exceeds the upper threshold,the bar changes to red, indicating a problem.

Remember There is a relationship between an Active Histogram and theRadar Diagram from which it is generated. The worst-case valuefor a particular measurement is the value plotted on thatmeasurement’s Radar Diagram axis. This is the case whether ornot you display the Active Histogram for the measurement.

When the value plotted for a PLMN returns to within the upper threshold,its bar colour returns to yellow. When it returns to within the lowerthreshold, its bar colour returns to green.

If Freeze Auto-Ranking is off (the default), as values are updated at theend of each interval, the bars are maintained in descending order. Thiskeeps the worst-case (highest) value at the top of the list.




6

If a bar is red or yellow, you may want more detailed information aboutthe history of the measurement for that PLMN. You can see this detail ona Time Series Histogram – see Chapter 7, “Using Time SeriesHistograms”.

Excluding a PLMN from measurements

You can disable a PLMN from the measurement routine, by clicking on themeasurement bar for the PLMN (not the PLMN name). The disabledPLMN appears in the “Remainder” colour. Clicking on the measurementbar again will re-enable the PLMN

A disabled PLMN will be excluded from the application group but still beauto-ranked. The PLMN’s status will be reflected in the parent RadarDiagram where the PLMN subset status will be altered. The PLMN willbe automatically re-enabled if the Active Histogram is closed or the AutoRe-enable time out expires


If measurements are not complete due to gaps in the data, this isindicated on the Active Histogram by the label [Incomplete Data] in thestatus line. This label will disappear at the end of the next measurementinterval during which the data is complete. A gap of even onemeasurement is shown in this way.




6

Loss of traffic

The Active Histogram indicates any halt in the traffic it is monitoring. If,for any reason, traffic stops (known as “loss of producer”), RMS GSMimmediately does the following:

• Removes the active part of the display except the thresholds.• Fills the background of the chart area with the critical colour.• Displays a [No Producers] label in the status bar.

When traffic resumes, the Active Histogram reverts to normal and showsa [Producer resumed] message in the status bar.


To manage your workspace, you can shrink an Active Histogram to an iconby clicking on the shrink button at the top right of the window border:

When the Active Histogram is shrunk to an icon, the icon is an activeminiature representation of the Active Histogram without the labels. Toexpand an icon to show the Active Histogram, double click on it.




Using Active HistogramsGetting more detail

6

Getting more detail

From the Active Histogram you can display a Time Series Histogramshowing the history of a measurement result for a particular PLMN.

To show the Time Series Histogram, simply click on the PLMN’s name box(to the left of the bar). See “About Time Series Histograms”, on page 7-2for details.

You can display one Time Series Histogram for each PLMN on the ActiveHistogram.


Note The limit on the total number of windows you are displaying willdepend on the capabilities of your workstation.

The Active Histogram remains displayed when you select a Time SeriesHistogram.



Using Active HistogramsClosing an Active Histogram

6

Closing an Active Histogram

To close an Active Histogram, select the Close option from the Filepull-down menu. Alternatively, double click on the button at the top left ofthe window border:

When you close an Active Histogram, all the Time Series Histograms thatyou have launched from it will also close. Note that this will not close anyTime Series Histograms that you have launched from a different ActiveHistogram.

You may subsequently reopen the Active Histogram as explained in“Starting an Active Histogram”, on page 6-3.


You can also close all Radar Diagrams in this application group, and allActive Histograms and Time Series Histograms started from them. To dothis, select the Close All option from the File pull-down menu. Note thatthis will not close the Alarmogram or any Time Series Histograms startedfrom it, or any Radar Diagrams, Active Histograms and Time SeriesHistograms in any other application group.


To then reopen any Active Histograms, you must first restart RadarDiagrams as explained in Chapter 2, “Getting Started”.




Using Active HistogramsClosing an Active Histogram

6



7

7

Using Time Series HistogramsThis chapter explains how to use Time Series Histograms. It contains:

• an introduction to Time Series Histograms and how information isdisplayed;

• information on how to interpret and manipulate Time SeriesHistograms.

RMS.07_Time.fm Modified: 2002 Mid v.0.3

Using Time Series HistogramsAbout Time Series Histograms

7

About Time Series Histograms

The purpose of a Time Series Histogram is to show the status of a singlemeasurement for one of the PLMNs you are monitoring. Their primaryuse is for fault finding. More detailed measurement information isdisplayed and, in the case of Error Volume and Error Rate, it is possible toidentify individual error causes and SCCP addresses.

They also provide a historical record of performance over the latest displayperiod – see “Data storage and display periods”, on page 4-2 – allowingyou to study historical trends in the PLMN, and use these to forecastpossible future performance.

Time Series Histograms are updated at the end of each measurementinterval to ensure that you are kept up-to-date on performance.


7-day Time Series Histogram

If you have purchased the 7-day Alarmogram + Customer Care WebInterface Function Upgrade, Time Series Histogram data will be availablefor up to seven days. Any Time Series Histograms started from anAlarmogram that covers an extended period will also contain additionaldata. Refer to “7-day Alarmogram”, on page 4-2 for more information.

The 7-day Time Series Histogram works in the same way as the standardversion, the difference being a larger amount of data may be viewed.


RMS.07_Time.fm Modified: 2002

Using Time Series HistogramsStarting a Time Series Histogram

7

Starting a Time Series Histogram

You can invoke a Time Series Histogram either from the Alarmogram orfrom an Active Histogram.

Starting a Time Series Histogram from the Alarmogram1. Select the required PLMN by clicking on its label in the PLMN

Overview area of the Alarmogram.

2. Choose the required measurement for the selected PLMN byclicking on its label in one of the Measurement Summary areas ofthe Alarmogram.

Click on PLMN

Click on measurement



Using Time Series HistogramsStarting a Time Series Histogram

7

Starting a Time Series Histogram from an Active Histogram

An Active Histogram is already displaying data for a selectedmeasurement, so you only need to choose the required PLMN. To do this,click on the PLMN’s label, for example:

Click on PLMN label



Using Time Series HistogramsUnderstanding Time Series Histograms

7

Understanding Time Series Histograms

What you see

Displayed data

The data on display when you activate a Time Series Histogram dependson the application that you used to open the Time Series Histogram andwhich Alarmogram you are using – standard or 7-Day1.

Each Time Series Histogram shows the history of a single measurementresult for a single PLMN in one direction. How the Time Series Histogramlooks depends on the type of measurement you are looking at.

Volume, Absence & ATL measurements appear as single bars

1. Available if you have purchased the 7-day Alarmogram + Customer CareWeb Interface Function Upgrade.




7

Error measurements are broken down by error code

Each bar is a single measurement. The bar is subdivided into the variouserror codes that make up the total measurement.

Error measurements can also appear in exploded diagrams

As an alternative to viewing Error and Error Rate measurements assingle bar, you can also display each separate error code in its ownindividual graph.




7

Each bar shows one measurement interval

Each bar in the graph represents one measurement interval. The windowshows up to 60 different measurement intervals.

Example If the measurement interval is five minutes, the window shows60 x 5 minutes, or five hours’ worth of data.

A new bar is added to the right hand side of the window eachmeasurement interval. The other bars move one space to the left.

Each Time Series Histogram can display measurements for the currentdisplay period. Normally you will not be able to see all the data in thewindow at the same time, so you can scroll through the data using thescroll bar.

The mini view on the scroll bar shows the whole data set in miniature andhelps you locate and home in on times of specific interest.

Caution Scrolling too rapidly may show spurious gaps in the data.

a new bar is added here at the endof each measurement interval

the other bars move along one space to the left

Use the scroll bar to scroll throughthe measurements

Use the mini view to home in onspecific measurements




7

Date selection

As well as the standard scrolling methods it is possible to select a date toview.

1. Click on Date in the View menu.The dates displayed will be from the current date back to the startof the data currently being stored. Unless there have been dataproblems this will be for the complete display storage period.

2. Select the required date.

The data displayed will be centred about midday on the selected date.



The length of each bar represents the actual measurement result for theselected PLMN for that interval.

You can easily identify worst case results

The height of the bar indicates the measurement value. The higher a barthe higher the measurement. You can view measurements in two ways:

• scaled against the Warning and Critical Thresholds (ThresholdScaling)

• scaled relative to the actual value (Data Value Scaling)

Information about which scaling option is active is displayed in the bottomright corner of the Time Series Histogram.

Active scaling option




7

Threshold Scaling shows measurements relative to the threshold values

The Y axis is scaled to the Warning and Critical threshold values. You caneasily see if a measurement is exceeding a threshold. Thresholds displayas dashed lines.

Warning threshold Critical threshold




7

Data value scaling shows measurements relative to each other

The Y axis scale is set to accommodate the highest measurement value.You can more easily see measurements relative to one another. Maximumand minimum values display as solid lines. The median value will displayas a tick mark and value on the y axis. Warning and Critical thresholdonly appear if they fall within the displayed area.

Maximum MinimumMedian



Using Time Series HistogramsInterpreting & manipulating the Time Series Histogram

7

Interpreting & manipulating the Time SeriesHistogram

Showing the value of the bar measurement

To show the value of the bar measurement, hover the cursor over therequired bar. The timestamp and value for this bar are then displayed atthe bottom right of the window, for example:

The value displayed depends on the measurement:

Viewing other measurements

You can view data that is outside the visible window by scrolling throughthe data using the scroll bar and mini view.

Measurement Value displayed

Volume (VOL) – except SCCP transactions per minute tpm

Error (ERR) – except SCCP transactions per minute tpm

Volume (VOL) – SCCP only messages per minute mpm

Error (ERR) – SCCP only messages per minute mpm

Absence (ABS) minute min

Error Rate (ERA) percent %

Average Transaction Length seconds sec

Hover cursor over bar... ... to show the time and value forthe bar’s measurement interval




7

Changing between Threshold and Data Value scaling

To change between Threshold scaling and Data Value scaling selectScaling from the View menu. You can also change between the options bypressing Ctrl+S

Threshold scaling view

Data Value scaling view

Thresholds only appear in the Data Value scalingif they are within the measurement range or nomore than 10% higher than the maximum




7

Viewing error measurements

Error and Error Rate measurements can be viewed in two different ways.

The following sections deal with the Time Series Histogram as a combinedview. The section “Exploding Errors into separate histograms”, onpage 7-20 looks at exploded Time Series Histograms in more detail.

When you view a Time Series Histogram showing error or error ratemeasurements, you can view:

• the error causes only; or• error causes plus details of the called party address; or• error causes plus details of the calling party address.

Combined view…

Exploded view…

a single combined bar showing thetop N errors plus the remainder

a stack with a separate graph for each of thetop N errors, plus one for the remainder




7

Before looking at how you can manipulate error codes you must firstunderstand the selected bar on the graph.

Understanding the selected bar and how to change it

Why is the selected bar important? Each bar represents a different timeinterval. Each time interval can have different errors. It would beimpossible to compare one time interval with another and see trends ifeach bar showed different errors, and if these were arranged in differentorder. So that the display is consistent all bars show the same errorsarranged in the same order as the selected bar.

Which bar is the selected bar? When you initially open a Time SeriesHistogram, the selected bar is the most recent bar displayed. At the end ofeach measurement interval, when the data is updated, the newlydisplayed bar becomes the selected bar.

The most recent bar remains as the selected bar until you select adifferent bar by left clicking on it. The selected interval is identified by asmall black triangle underneath it.

initially selected bar

Currently selected bar Click on another bar to select it




7

In this case, the bar you select remains as the selected bar until you selectanother bar, or until it disappears from the diagram. When the selectedbar disappears from the diagram, the most recently displayed bar becomesthe selected bar.

Examining different error codes

The different errors that appear in the combined bar are colour coded. Thecolours correspond with the colour of the buttons at the right of thehistogram.

The blocks in the selected bar are arranged in order. The one with thelargest value is placed at the base of the bar, with the others in decreasingsize above it. The block for the remainder is placed at the top. Forexample:

Selected bar Error detailsKeyLargest block

Colour coded bars

Labels show:Error Code Only; orError Code + Called PA; orError Code + Calling PA.




7

The labelled buttons to the right show the colours and descriptions of eachof the error codes. One of the colours will always be for the remainder.

The order of segments for the selected bar determines the order in allother bars. The error description buttons are also derived from theselected bar. When you select a different bar the graph is redrawn with theblocks and the buttons in the correct order for that bar. For example:

Initially selected bar

New selected bar

Key and top N errors forinitially selected bar andnewly selected bar

All bar colour blocks redrawn toshow top N error codes inselected bar




7

Displaying the trend for a particular error code

You might find it useful to look at the history and trend of a particularerror. You can do this by placing that error at the base of the selected bar.The selected error will be displayed at the base of all other bars in thedisplay.

To do this, single click on the button for the error code of interest. Thisredraws the graph with the coloured block for this error code at the base ofall bars that have this subdivision. For example:

Click here...

... to redraw graph with the selected errorcode at the base of all bars, regardless of thetop errors in the selected bar




7

Changing the error details displayed

Error Rate and Error measurements can be displayed in different ways:

• top N error causes;• top N error code plus called party address;• top N error code plus calling party address.

To change the displayed information for a particular Time SeriesHistogram:

1. Select Drilldown to... from the Options pull-down menu on therequired Time Series Histogram.

2. From here, select the required information to be displayed:• Error Code Only; or• Error Code + Called PA; or• Error Code + Calling PA

The active Drilldown option is displayed in the bottom right corner of theTime Series Histogram.

Note If you have purchased the RTC+SCCP Function Upgrade thereare further Drilldown variations available, see “Drilldown optionswith SCCP messaging only”, on page 7-19




7

Drilldown options with SCCP messaging only

Note This option is only available if you have purchased theRTC+SCCP Function Upgrade.

To change the displayed information for a particular Time SeriesHistogram:

1. Select Drilldown to... from the Options pull-down menu on therequired Time Series Histogram.

2. From here, select the required information to be displayed:• Error Code Only; or• Error Code + Called PA; or• Error Code + Calling PA

When the Called or Calling option is selected the following informationwill be displayed in the text button:

• Return Cause• Called/Calling Party Address• Originating Point Code (OPC)

In this case, hover the mouse pointer over the OPC field to display apop-up box with details of how the OPC relates to the networkcomponents. The message will be in the format:

“Error <Return Cause> returned from node <OPC/PC Label>when trying to send from home network to<SCCP Calling PA/GT Label>”

Hoverover




7

Exploding Errors into separate histograms

To change between the combined view and the exploded view, select Viewfrom the View menu. You can also change between the two options bypressing the Ctrl-V.

The errors that previously appeared in the combined bar now appear asseparate graphs stacked above each other.

The errors that appear in the stack and order they are arranged in isdetermined by the bar that was the selected bar when you switched to the

All histograms share thesame scroll bar

The histogram for theremainder appears atthe bottom of the stack

The order of the stack is determined by the selected bar.The largest error appears at the top of the stack




7

exploded error view. Hover the mouse pointer over a bar to displayinformation about the data at the right of the status line.

Clicking on a bar in one of the histograms makes that measurement theselected bar. The whole stack will be redrawn to reflect the errors andorder of the new selected bar.

You can view data using either threshold or data value scaling forexploded Time Series Histograms.

Viewing all errors or only unmasked errors

The Administrator can recategorise some errors. This allows lessimportant errors to be masked, preventing them from swamping moreserious ones. Recategorising is performed in the Configuration Editor –see “Masking less significant errors” in the RMS GSM SystemAdministrator Guide

…to see its data value andtime stamp in the status bar

Hover the cursor over a bar…




7

In the Time Series Histogram, you can choose whether you want to viewall errors or remove masked errors to view unmasked errors only.

To change between viewing all errors and unmasked errors only selectError Recategorisation from the Options menu. You can also changebetween the two options by pressing the Ctrl+E.

The active Error Recategorisation option is displayed in the bottom rightcorner of the Time Series Histogram.

Note Threshold Violations are always calculated using unmasked errorsonly.


If measurements are not complete due to gaps in the data, this isindicated on the Time Series Histogram by a small black bar below theinterval bar concerned. If you hover the cursor over any bar withincomplete data, an [Incomplete] message is shown in the status bar. Agap of even one measurement is shown in this way.

Caution Scrolling too rapidly through the Time Series Histogram mayshow spurious gaps in the data.

Loss of traffic

The Time Series Histogram indicates any halt in the traffic it ismonitoring. If, for any reason, traffic stops (known as “loss of producer”),RMS immediately redraws the Time Series Histogram with thebackground in the critical colour, and a [No producers] message in thestatus bar. The Time Series Histogram stops updating – that is, no newbars are added and bars stop shifting left each measurement interval.

When traffic resumes, the Time Series Histogram starts to update againand shows a [Producers resumed] message in the status bar. Ahorizontal bar, in the critical colour, under an interval indicates wherethere has been a “loss of producer”.

A “hat” symbol above the graph indicates the volume for that interval wasbelow the Error Rate Floor. See the RMS GSM System Administrator’sGuide for information on configuring the Error Rate Floor.




7


To manage your workspace, you can shrink a Time Series Histogram to anicon by clicking on the shrink button at the top right of the window border:

When the Active Histogram is shrunk to an icon, the icon is an activeminiature representation of the Time Series Histogram without the labels.To expand an icon to show the Time Series Histogram, double click on it.




Using Time Series HistogramsClosing a Time Series Histogram

7

Closing a Time Series Histogram

To close a Time Series Histogram, select the Close option from the Graphpull-down menu. Alternatively, double click on the button at the top left ofthe window border:

You may subsequently reopen the Time Series Histogram as explained in“Starting a Time Series Histogram”, on page 7-3.


If you started the Time Series Histogram from the Alarmogram, then theClose All option from the File pull-down menu will close the Alarmogramand all Time Series Histograms started from it.

If you started the Time Series Histogram from an Active Histogram, thenthe Close All option from the File pull-down menu will close all RadarDiagrams, Active Histograms and Time Series Histograms that belong tothis application group. Note that this will not close Radar Diagrams,Active Histograms or Time Series Histograms that belong to otherapplication groups.





8

8

Using the Alarm ManagementReporterThis chapter explains how to use Alarm Management Reporter. Itcontains:

• an introduction to Alarm Reporting;• instructions on how to set up scheduled alarm reports and how to

generate an instant report;• a description of the information shown on the report.

RMS.08_Reporting.fm Modified: 2002 Mid v.0.3

Using the Alarm Management ReporterReporting on Alarms

8

Reporting on Alarms

You can configure Alarm Management Reports to be generated at regular,scheduled intervals. You can print these reports, send them to selectedrecipients, or both.

You can also generate a one-off instant report. You can set these up to bedisplayed on screen, saved to file, or printed.

These reports list alarms generated on critical events, or on both criticaland warning events.

Setting up a scheduled report

To configure a scheduled report:

1. Start the Alarm Reports dialogue:• In the RMS GSM Applications group (ARIA_Apps) you will find

an icon for the Alarm Reports. Double click on this to launch thedialogue.

• Alternatively, if your system uses OpenView, you can start fromeither the Roaming Map or the acceSS7 Map. On either Map,select the Roaming pull-down menu, then choose Alarms andthen Alarm Management Reporter:


RMS.08_Reporting.fm Modified: 2002


8

2. Click on Scheduled Report to show:

3. To remove any previously scheduled report and start reportconfiguration from scratch, click on Remove Schedule.

4. Choose when to schedule the report. This can be every 24 hours (at00:00), every 12 hours (at 00:00 and 12:00), or every 8 hours (at00:00, 08:00 and 16:00):

5. Select which alarms triggered during the reporting period to reporton – warning and critical alarms, or critical alarms only:




8

6. Indicate where the report is to be delivered when it is generated:• To mail reports directly to selected people, turn on the Mail

reports to recipients option by clicking in its box (a tickappears in the box when the option is on), and type the emailaddresses of the intended recipients in the Mail names field:

If mailing to more than one recipient, separate the emailaddresses by a comma (,). Do not leave any spaces between emailaddresses.You can send to local Unix email addresses and, if your acceSS7system is connected to the Internet, to any Internet emailaddress.

• To print reports, turn on the Print reports to selected printeroption by clicking in its box (a tick appears in the box when theoption is on), and enter the printer name, printer options, andnumber of copies required in the appropriate fields:

Note that the printer options you specify are applied to the Unixlp command. Your System Administrator will be able to tell youwhich options are configured for your specific printer.

7. To accept this report configuration, click on Apply Schedule.Alternatively, to clear the Scheduled Reports dialogue and start theconfiguration again (from step 3 above), click on RemoveSchedule.

8. When you have finished configuring the report, click on Close toclose the Scheduled Reports dialogue.

The last 7 days of scheduled report data is kept

Scheduled reports are automatically written to files in the directory/usr/RMS/alarms/scheduled, in subdirectories identified by date –YYYYMMDD – for example 19981114. The most recent 7 days of reportsare kept – older directories are automatically removed.




8

Generating an instant report

To configure an instant report:

1. Start the Alarm Reports dialogue:• In the RMS GSM Applications group (ARIA_Apps) you will find

an icon for the Alarm Reports. Double click on this to launch thedialogue.

• Alternatively, if your system uses OpenView, you can start fromeither the Roaming Map or the acceSS7 Map. On either Map,select the Roaming pull-down menu, then choose Alarms andthen Alarm Management Reporter:




8

2. Click on Instant Report to show:

3. Choose what alarms to show in the report. This can be all completealarms, all alarms in progress, or both:

Note that you need to select at least one option to generate a report.




8

4. Select which PLMN(s), procedure(s), direction(s) andmeasurement(s) to cover in the report. Use the selection boxes inthe Report Parameters section to make your choices. In each caseyou can choose a single item or ALL for all items on the list:

Note that the list includes all PLMNs that have received an alarmwithin the last seven days.

5. Select the required reporting period. Use the radio buttons to chooseeither the last 24 hours or a user defined period. If you select a userdefined reporting period, enter the start and stop times for theperiod in the fields:

6. Select which alarms triggered during the reporting period to reporton – warning and critical alarms, or critical alarms only:

7. Indicate where the report is to be delivered when it is generated:• To display the report on-screen, turn on the Send report to

display option by clicking in its box (a tick appears in the boxwhen the option is on).




8

• To save the report to file, turn on the Send report to file optionby clicking in its box (a tick appears in the box when the option ison), and type a file name in the field:

• To print the report, turn on the Print reports to selectedprinter option by clicking in its box (a tick appears in the boxwhen the option is on), and enter the printer name, printeroptions, and number of copies required in the appropriate fields:

Note that the printer options you specify are applied to the Unixlp command. Your System Administrator will be able to tell youwhich options are configured for your specific printer.

8. To produce the instant report, click on Generate Report.9. When you have finished generating instant reports, click on Close

to close the Instantaneous Reports dialogue.



Using the Alarm Management ReporterWhat does the report show?

8

What does the report show?

The following information is shown for each alarm reported:

• Nation (e.g. France, UK, Germany).• PLMN short name.• Alarm severity – W(arning) or C(ritical).• A unique identifier (e.g. 1867305073MAP015E2HABS).

This comprises:• a unique 10 digit number generated every second (e.g.

1867305073);• the failing procedure – UL, PRN, FSM, SP, MAP or RTC;• PLMN network identifier (e.g. 015);• the measurement direction – E2H or H2E;• the failing measurement – VOL, QoS, ERR, ABS or ATL.

Note In this identifier, QoS indicates that Error Rate is the failingmeasurement.

• Alarm start time – YYYYMMDD_hhmmss (e.g. 19980714_231900).• Alarm stop time – YYYYMMDD_hhmmss (e.g. 19980714_232100).• Alarm duration – hh:mm:ss (e.g. 00:50:00).• Warning threshold value for the alarm event.• Critical threshold value for the alarm event.• Triggering event measurement value (normalised).• Error details for triggering event, by calling party and called party.

In the report, alarms are sorted first by nation, then by PLMN, then byseverity and finally by unique identifier.

An alarm that has started but not yet stopped at the time the report isgenerated is an open alarm. Open alarms are marked with asterisks –**** – in place of the alarm stop time and duration.

An alarm that has not been closed but is likely to have ended (e.g. due to asystem error) is a hanging alarm. Hanging alarms are marked with plussigns – ++++ – in place of the alarm stop time and duration.

For practical purposes, there is little difference between open and hangingalarms.



Using the Alarm Management ReporterWhat does the report show?

8



9

9

Using the Customer Care WebInterfaceThis chapter explains how to use the Customer Care Web Interface toobtain information on quality of service. It contains:

• information on how to start the Customer Care Web Interface(CCWI) and

• an introduction to the Customer Care Web Interface (CCWI) andhow information is presented.

RMS.09_CCWI.fm Modified: 2002 Mid v.0.3

Using the Customer Care Web InterfaceAbout the CCWI

9

About the CCWI

Note The Customer Care Web Interface is only available if yourorganisation has purchased the 7-day Alarmogram + CustomerCare Web Interface Function Upgrade.

The purpose of the CCWI is to provide the Customer Care departmentwith information on the quality of service provided to:

• your customers roaming in partner networks and• visitors in your network.

Information will only be available for Error Rate and Total MAP Absencemeasurements that have generated warning or critical messages, for allPLMNs, for a maximum of the last seven days. No information will beavailable for Total Volume, Error Volume, Average Transaction Length orother Absence measurements

You can view the information using Internet Explorer v4.0 (or higherversion) web browser. Details are displayed in a format similar to theAlarmogram.

Definitions

Standard 7-Day

Data Storage Period 24 hours Maximum: 7 days

Data Display Period 24 hours Maximum: Data Storage Period


RMS.09_CCWI.fm Modified: 2002

Using the Customer Care Web InterfaceShowing the CCWI

9

Showing the CCWI

Starting the web browser and viewing CCWI information

Start your normal web browser and access the CCWI start page asdirected by your Systems Administrator. To use the CCWI your webbrowser must be Internet Explorer, version 4.0 or higher.

To ensure that data is only available to company employees you will onlybe able to access the web pages on the company intranet.

Note If you have been given no other instructions about how to accessthe CCWI page you will need to find the IP address of RMS GSMServer, type it into your web browser address line and press Enter.

The initial screen is the Network Information Search screen.

1. Select the following details from drop-down lists:• The country for the PLMN(s) that you are interested in and• The day (from the last seven days) for which you want details.

2. Click on Search.




9

If there is no data available for the selected day a warning message will bedisplayed

The details are displayed on a Network Information screen. The selectedcountry and date will be displayed at the top of the screen.

The top section shows a list of all PLMNs in the selected country. Initiallythe top PLMN on this list will be selected. To select a different networkclick on the network name at the right of the screen.

The list below the PLMNs shows details of problems with the selectedPLMN on the selected day.

Note Details will only be displayed for measurements that have hadeither warning or critical conditions on the selected day.

... to see fulldescription here

Click on briefdescription...

Click on thename of a PLMN




9

Descriptions of errors

Each measurement that appears in the network problems section of thescreen will have a short description beside it of the problem that is beingidentified. Click on the brief description to display a full description at thefoot of the screen.

These descriptions are set up by your System Administrator. To configurethe descriptions consult the RMS GSM System Administrator’s Guide.

Viewing all data

If there is more data than your screen can display click on the scroll barsto bring data into view.

Understanding how rows are ranked

Rows in both areas are ordered according to the “Olympic medal” rule.

• Rows are ranked first by the number of red blocks they contain overthe selected day. Rows with more red blocks are shown above thosewith fewer or none.

• Rows with equal numbers of red blocks, or with no red blocks, arethen ranked by the number of yellow blocks they contain.

New search

If you want to look at networks in a different country, or select a differentdate, click on the New Search link at the top right of the screen to returnto the search screen.



Using the Customer Care Web InterfaceClosing the CCWI

9

Closing the CCWI

To close the CCWI either:

• select a different URL in the web browser, or• close down the web browser.



A

1

Appendix A

RMS GSM MeasurementsThis appendix provides a detailed description of the measurements usedby the GSM Roaming Management System (RMS GSM). It contains:

• a list of the measurement types and classes used;• detailed descriptions of each measurement;• an explanation of normalisation of measurements;• measurement performance limits.

RMS.A_Measurements.fm Modified: 2002 Mid v.0.3

RMS GSM MeasurementsSummary of procedures & measurements

A

Summary of procedures & measurements

RMS GSM monitors both MAP and ISUP traffic, keeping counts for thefollowing procedures and meta-procedures:

• Update Location (UL). A MAP procedure sent in response to achange in a mobile user’s position

• Provide Roaming Number (PRN). A MAP procedure sent to obtain anumber that can be used to call a mobile user roaming in a networkbelonging to a different operator.

• Forward Short Message (FSM). A MAP procedure used to deliverShort Message data to mobile users who are roaming in anotheroperator’s network.

• Send Parameters (SP). A MAP procedure used to provideauthentication triplets to a mobile terminal.

• Sum of all MAP procedures (MAP). A count of all MAP proceduresthat were detected, including those that were counted separately.

If you have purchased the RTC+SCCP Function Upgrade, RMS GSM alsomonitors:

• SCCP messaging. The SCCP measurement provides a real-timeanalysis of SCCP UDT/UDTS messages.

• Roamers’ Terminating Calls (RTC). A meta-transaction thatmatches PRN procedures with subsequent CDRs, describing thecalls that are placed using the roaming number provided by thePRN procedure.

If you have purchased the CAMEL + USSD Function Upgrade, RMS GSMalso monitors:

• CAMEL services as a whole, by monitoring InitialDP messages.• USSD services as a whole, by monitoring the MAP Phase 2+

ProcessUnstructuredSSRequest procedure.

If you have purchased the GPRS Function Upgrade, RMS GSM alsomonitors:

• The GPRS service as a whole, by monitoring the MAP Phase 2+updateGPRSlocations procedure.

A-2 RMS GSM Operator Manual

RMS.A_Measurements.fm Modified: 2002


A

RMS GSM calculates measurements from the data that it is monitoring.All measurements are calculated separately for each of two directions:from the home network to an external network (H2E) and from anexternal network to the home network (E2H). RMS GSM counts thetransaction data throughout a measurement interval (defined when thesystem is started), then makes the measurement calculations at the end ofthe interval.

The measurements and their units are:

• Volume (VOL) is the total number of transactions of a particularprocedure that were detected during a measurement interval.Volume is expressed as transactions per minute, and so isindependent of the length of the measurement interval.

• Errors (ERR), or Error Volume, is a count of unsuccessfultransactions detected during a measurement interval. A transactionis unsuccessful if it returns an error result, aborts or times outwaiting for completion. Error Volume is expressed as transactionsper minute, and so is independent of the length of the measurementinterval.

• Absence (ABS) is expressed as a whole number of intervals forwhich a procedure has been absent.

• Error Rate (ERA) is defined as the Errors divided by the Volume.It ranges from 0 (good) to 1 (bad). Error rate is a ratio and isindependent of the length of the measurement interval.

Note Error rate is an inverse measure of quality of service (QoS) – i.e.the lower the error rate the higher the quality of service.

• Average Transaction Length (ATL) is the average length of timetaken for transactions to complete. The length of a transaction isthe number of seconds between the TC-BEGIN and the TC-END, or,for a pre-arranged end (for instance with CAMEL), betweenTC-BEGIN and TC-CONTINUE. Note that this measurement is notgiven for timed out transactions.

RMS GSM Operator Manual A-3



A

General notes on measurements detailed in the following sections

Directions Measurements made from your own network to an externalPLMN are referred to as “from” measurements. Those made toyour own network from an external PLMN are called “to”measurements.

Subscribers Customers of other PLMNs are referred to as “foreign subscribers”to distinguish them from your own network’s direct customers,who are “your own subscribers”.

Networks The service provided by your own company (your own PLMN) isreferred to as the HPLMN (Home PLMN). Other PLMNs arereferred to as VPLMNs (Visitor PLMNs).



RMS GSM MeasurementsUpdate Location (UL) measurements

A

Update Location (UL) measurements

UL volume

Purpose

The to measurement monitors the number of ULs received by theHPLMN from individual VPLMNs. This can show, for instance, theVPLMN in which the largest numbers of your subscribers are roaming.

The from measurement monitors the number of ULs sent by the HPLMNto VPLMNs. This can show, for instance, the VPLMN with the greatestnumber of subscribers roaming in your own network.

Formula

# ULs * weight (PLMN) / measurement period

Time series measurement parameters

None.

UL errors

Purpose

The to measurement monitors the number of errors in ULs received bythe HPLMN from individual VPLMNs.

The from measurement monitors the number of errors in ULs sent by theHPLMN to VPLMNs.

Formula

# errors in ULs * weight (PLMN) / measurement period


Returned error codes for UL (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for UL.Returned error code and SCCP Called Party address pairs for UL.




A

UL error rate

Purpose

The to measurement monitors the number of failed UL results sent by theHPLMN to a VPLMN against the number of attempted UL requests sentto the HPLMN from the same VPLMN. It highlights problems experiencedby your own subscribers trying to register while they are abroad.

The from measurement monitors the number of failed UL results sent bya VPLMN to the HPLMN against the number of attempted UL requestssent from the HPLMN to the same VPLMN. It shows problems for foreignsubscribers roaming in the HPLMN.

Formula

(# failed ULs / # attempted ULs) * weight (PLMN)


Returned error codes for UL (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for UL.Returned error code and SCCP Called Party address pairs for UL.

UL absence

Purpose

The to measurement monitors the highest number of intervals withoutreceiving a UL from your own subscribers roaming in a VPLMN. It detectsmajor interconnectivity problems for your subscribers roaming inVPLMNs.

The from measurement monitors the highest number of intervals withouta UL from foreign subscribers roaming in the HPLMN. It provides a toolto immediately detect loss of connectivity for foreign subscribers roamingin the HPLMN, before they decide to switch to other networks.

Formula

# intervals without UL * weight (PLMN)


None.




A

UL Average Transaction Length

Purpose

The to measurement identifies the average length of time it takes for aroaming subscriber to register in the VLPMN. Subscribers abroad have toregister with a VLR. To achieve this an Update Location is sent to thesubscribers HLR. Until the HLR responds to the VLR the transaction isnot complete and the subscriber is not registered in the VLR. A delay inthe response may affect the subscriber’s ability to make and receive calls.The Average Transaction Length measurement provides an indication ofthe delay in registering.

The from measurement identifies the average length of time it takes for aforeign subscriber roaming in your network to register with a local VLR.Subscribers abroad have to register with a VLR. To achieve this anUpdate Location is sent to the subscriber’s HLR. Until the HLR respondsto the VLR the transaction is not complete and the subscriber is notregistered in the VLR. A delay in the response may affect the subscriber’sability to make and receive calls. The Average Transaction Lengthmeasurement provides an indication of the delay in registering.

Formula

(SUM (transaction end time - transaction start time) / # transactions) *weight (PLMN)


None.



RMS GSM MeasurementsProvide Roaming Number (PRN) measurements

A

Provide Roaming Number (PRN) measurements

PRN volume

Purpose

The to measurement monitors the number of PRNs received by theHPLMN because of foreign subscribers being called while roaming in theHPLMN.

The from measurement monitors the number of PRNs sent by theHPLMN because of calls received for your own subscribers roaming in aVPLMN.

Formula

# PRNs * weight (PLMN) / measurement period


None.

PRN errors

Purpose

The to measurement monitors the number of errors in PRNs received bythe HPLMN because of foreign subscribers being called while roaming inthe HPLMN.

The from measurement monitors the number of errors in PRNs sent bythe HPLMN because of calls received for your own subscribers roaming ina VPLMN.

Formula

# errors in PRNs * weight (PLMN) / measurement period


Returned error codes for PRN (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for PRN.Returned error code and SCCP Called Party address pairs for PRN.




A

PRN error rate

Purpose

The to measurement monitors the number of failed PRN results sent by aVPLMN to the HPLMN against the number of attempted PRN requestssent from the same VPLMN to the HPLMN. It highlights problemsplacing calls to foreign subscribers while they are roaming in the HPLMN.

The from measurement monitors the number of failed PRN results sentby the HPLMN to a VPLMN against the number of attempted PRNrequests sent to the same VPLMN from the HPLMN. It highlightsproblems placing calls to your own subscribers while they are roamingabroad.

Formula

(# failed PRNs / # attempted PRNs) * weight (PLMN)


Returned error codes for PRN (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for PRN.Returned error code and SCCP Called Party address pairs for PRN.

PRN absence

Purpose

The to measurement monitors the highest number of intervals without aPRN from foreign subscribers roaming in the HPLMN. It detects loss ofconnectivity for foreign subscribers roaming in the HPLMN.

The from measurement monitors the highest number of intervals withoutreceiving a PRN from your own subscribers roaming in a VPLMN. Itprovides a tool to immediately detect loss of connectivity for your ownsubscribers roaming in a VPLMN.

Formula

# intervals without PRN * weight (PLMN)


None.




A

PRN Average Transaction Length

Purpose

The to measurement identifies the average length of time it takes for aforeign subscriber roaming in the home network to be assigned with aMobile Subscriber Roaming Number (MSRN) by the home network.Without the MSRN the roaming subscriber cannot receive calls. Theaverage transaction length directly affects the time the caller has to waitfor the circuit to be established and the call made.

The from measurement identifies the average length of time it takes for aroaming subscriber abroad to be assigned a Mobile Subscriber RoamingNumber (MSRN) by the foreign network in which they are currentlyroaming. Without the MSRN the roaming subscriber cannot receive calls.The average transaction length directly affects the time the caller has towait for the circuit to be established and the call made.

Formula



None.



RMS GSM MeasurementsForward Short Message (FSM) measurements

A

Forward Short Message (FSM) measurements1

FSM volume

Purpose

The to measurement monitors the number of FSMs received by theHPLMN from a VPLMN.

The from measurement monitors the number of FSMs originating fromthe HPLMN and sent to VPLMNs.

These measurements show potential misuse of the service by your ownsubscribers. They also highlight misuse of the service by other users whencommunicating with subscribers via SMS while abroad, and show floodingof the SS7 network by malicious or unintentional behaviour of VPLMNs.

Formula

# FSMs * weight (PLMN) / measurement period


None.

FSM errors

Purpose

The to measurement monitors the number of errors in FSMs received bythe HPLMN from a VPLMN.

The from measurement monitors the number of errors in FSMsoriginating from the HPLMN and sent to VPLMNs.

Formula

# errors in FSMs * weight (PLMN) / measurement period

1. In MAP 2+, FSM is split into FSM-MO and FSM-MT. RMS GSM combines theseinto one generic FSM procedure.




A


Returned error codes for FSM (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for FSM.Returned error code and SCCP Called Party address pairs for FSM.

FSM error rate

Purpose

The to measurement monitors the number of failures against attempts indelivering messages to the HPLMN from VPLMNs.

The from measurement monitors the number of failures against attemptsin delivering messages from the HPLMN to VPLMNs.

These measurements detect problems in the SM service for roamingsubscribers. They are important because the destination MS may remainunaware of not being reachable, particularly with an asynchronous servicelike SMS.

Formula

(# failed FSMs / # attempted FSMs) * weight (PLMN)


Returned error codes for FSM (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for FSM.Returned error code and SCCP Called Party address pairs for FSM.

FSM absence

Purpose

The to measurement monitors the highest number of intervals withoutreceiving an FSM from a VPLMN. It provides a tool to immediately detectloss of connectivity – the inability of the HPLMN to receive FSMs fromoutside.

The from measurement monitors the highest number of intervals withoutan FSM being sent by the HPLMN. It detects major interconnectivityproblems in which subscribers using the HPLMN cannot send FSMs toVPLMNs.




A

Formula

# intervals without FSM * weight (PLMN)


None.



RMS GSM MeasurementsSend Parameters (SP) measurements

A

Send Parameters (SP) measurements

SP volume

Purpose

The to measurement monitors the number of SPs received by the HPLMNfrom individual VPLMNs. It may indicate an unusually high number ofrequests for authentication information from your subscribers whileroaming.

The from measurement monitors the number of SPs sent by the HPLMNto VPLMNs. It may indicate an unusually high number of requests forauthentication information made by foreign subscribers while roaming inthe HPLMN.

Formula

# SPs * weight (PLMN) / measurement period


None.

SP errors

Purpose

The to measurement monitors the number of unsuccessful SP requestsfrom individual VPLMNs.

The from measurement monitors the number of unsuccessful SP requestsmade from the HPLMN.

Formula

# errors in SPs * weight (PLMN) / measurement period


Returned error codes for SP (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for SP.Returned error code and SCCP Called Party address pairs for SP.




A

SP error rate

Purpose

The to measurement monitors the ratio of unsuccessful SPs sent by aVPLMN to the HPLMN versus the total number of attempted SPs sent bythe same VPLMN. It may identify problems with your own AuthenticationCentre experienced by your subscribers when roaming abroad.

The from measurement monitors the ratio of unsuccessful SPs sent by theHPLMN to a VPLMN versus the total number of attempted SPs sent bythe HPLMN to the same VPLMN. It may identify problems with a foreignAuthentication Centre experienced by foreign subscribers roaming in theHPLMN.

Formula

(# failed SPs / # attempted SPs) * weight (PLMN)


Returned error codes for SP (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for SP.Returned error code and SCCP Called Party address pairs for SP.

SP absence

Purpose

The to measurement monitors the number of intervals since an SP waslast received from individual VPLMNs.

The from measurement monitors the number of intervals since an SP waslast sent to individual VPLMNs.

In both cases this may point to a connectivity problem with a VPLMN.

Formula

# intervals without SP * weight (PLMN)


None.




A

SP Average Transaction Length

Purpose

The to measurement identifies the average length of time it takes for aforeign MSC/VLR to receive Authentication Triplets from the home HLR.Delay in these transactions can affect the authentication of roamingsubscribers in foreign networks.

The from measurement identifies the average length of time it takes for ahome MSC/VLR to receive Authentication Triplets from a foreign HLR.Delay in these transactions can affect the authentication of foreignsubscribers in the home network.

Formula



None.



RMS GSM MeasurementsTotal MAP measurements

A

Total MAP measurements

Measurements on any one of the MAP procedures will provide specificinformation regarding activity and health of specific roaming services. Itis also essential to consider the sum of all MAP transactions to allow amore global view of the activity on the GSM network.

Total MAP volume

Purpose

The to measurement monitors the total number of MAP proceduresreceived by the HPLMN from individual VPLMNs.

The from measurement monitors the total number of MAP proceduressent from the HPLMN to individual VPLMNs.

Formula

# MAP procedures * weight (PLMN) / measurement period


None.

Total MAP errors

Purpose

The to measurement monitors the number of unsuccessful MAPprocedure requests from individual VPLMNs.

The from measurement monitors the number of unsuccessful MAPprocedure requests made from the HPLMN.

Formula

# errors in MAP procedures * weight (PLMN) / measurement period




A


Returned error codes for all MAP procedures (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for all MAPprocedures.Returned error code and SCCP Called Party address pairs for all MAPprocedures.

Total MAP error rate

Purpose

The to measurement monitors the ratio of failed MAP procedures sent bya VPLMN to the HPLMN versus the total number of attempted MAPprocedures sent by the same VPLMN.

The from measurement monitors the ratio of failed MAP procedures sentby the HPLMN to a VPLMN versus the total number of attempted MAPprocedures sent by the HPLMN to the same VPLMN.

Formula

(# failed MAP procedures / # attempted MAP procedures) * weight(PLMN)


Returned error codes for all MAP procedures (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for all MAPprocedures.Returned error code and SCCP Called Party address pairs for all MAPprocedures.

Total MAP absence

Purpose

The to measurement monitors the number of intervals since any MAPprocedure was last received from individual VPLMNs.

The from measurement monitors the number of intervals since any MAPprocedure was last sent to individual VPLMNs.




A

In both cases an excessive absence may indicate major interconnectivityproblems for roaming subscribers, for example a total loss of connectionbetween networks. Alternatively it may be a naturally quiet period for aspecific VPLMN.

Formula

# intervals without MAP procedures * weight (PLMN)


None.



RMS GSM MeasurementsSCCP Messaging (SCCP) measurements

A

SCCP Messaging (SCCP) measurements

SCCP volume

Purpose

The to measurement monitors the number of SCCP messages received bythe HPLMN from individual VPLMNs. It may indicate an unusually highnumber of requests for authentication information from your subscriberswhile roaming.

The from measurement monitors the number of SCCP messages sent bythe HPLMN to VPLMNs. It may indicate an unusually high number ofrequests for authentication information made by foreign subscribers whileroaming in the HPLMN.

Formula

# SCCPs * weight (PLMN) / measurement period


None.

SCCP errors

Purpose

The to measurement monitors the number of unsuccessful SCCP requestsfrom individual VPLMNs.

The from measurement monitors the number of unsuccessful SCCPrequests made from the HPLMN.

Formula

# errors in SCCPs * weight (PLMN) / measurement period


Returned error codes for SCCP (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for SP.Returned error code and SCCP Called Party address pairs for SP.



RMS GSM MeasurementsSCCP Messaging (SCCP) measurements

A

SCCP error rate

Purpose

The to measurement monitors the ratio of unsuccessful SCCP messagessent by a VPLMN to the HPLMN versus the total number of attemptedSPs sent by the same VPLMN. It may identify problems with your ownAuthentication Centre experienced by your subscribers when roamingabroad.

The from measurement monitors the ratio of unsuccessful SCCPmessages sent by the HPLMN to a VPLMN versus the total number ofattempted SPs sent by the HPLMN to the same VPLMN. It may identifyproblems with a foreign Authentication Centre experienced by foreignsubscribers roaming in the HPLMN.

Formula

(# failed SCCPs / # attempted SCCPs) * weight (PLMN)


Returned error codes for SCCP (as in MAP specifications).Returned error code and SCCP Calling Party address pairs for SP.Returned error code and SCCP Called Party address pairs for SP.

SCCP absence

Purpose

The to measurement monitors the number of intervals since an SCCPmessage was last received from individual VPLMNs.

The from measurement monitors the number of intervals since an SCCPmessage was last sent to individual VPLMNs.

In both cases this may point to a connectivity problem with a VPLMN.

Formula

# intervals without SCCP * weight (PLMN)


None.



RMS GSM MeasurementsRoamers’ Terminating Calls (RTC) measurements

A

Roamers’ Terminating Calls (RTC) measurements

Before a roaming subscriber can receive a call, a temporary number mustbe obtained using the MAP PRN procedure. This number, the MobileSubscriber Roaming Number (MSRN), is then used in the subsequentISUP leg.

The RTC measurement correlates the fixed and mobile network services(ISUP and PRN) needed to successfully terminate a call to roamingsubscriber. If a PRN fails then there is no MSRN to use in an IAM, so nocall is attempted.

RTC volume

Purpose

The to measurement monitors the number calls routed to internationalsubscribers roaming in the HPLMN.

The from measurement monitors the number of calls originating in theHPLMN and routed to your own subscribers roaming abroad.

Formula

# RTCs * weight (PLMN) / measurement period


None.

HLR

GSMC MSC /VLR

SRI (IMSI)

SRI (MSRN)

PRN (IMSI)PRN (MSRN)

IAM (MSRN)

IAM (MSRN)

IAM (MSISDN)




A

RTC errors

Purpose

The to measurement monitors the number of unsuccessful RTCs forforeign subscribers roaming in the HPLMN.

The from measurement monitors the number of unsuccessful RTCs foryour own subscribers roaming in VPLMNs.

In both cases it may indicate an unusually high number of incompletecalls being made to roaming subscribers.

Formula

# errors in RTCs * weight (PLMN) / measurement period


Returned error codes for RTC (ISUP correlation).Returned error code and SCCP Calling Party address pairs for RTC.Returned error code and SCCP Called Party address pairs for RTC.

RTC error rate

Purpose

The to measurement monitors the ratio of unsuccessful RTCs versus thenumber of RTC attempts for foreign subscribers in the HPLMN.

The from measurement monitors the ratio of unsuccessful RTCs versusthe number of RTC attempts for your own subscribers in VPLMNs.

Formula

(# failed RTCs / # attempted RTCs) * weight (PLMN)


Returned error codes for RTC (ISUP correlation).Returned error code and SCCP Calling Party address pairs for RTC.Returned error code and SCCP Called Party address pairs for RTC.




A

RTC absence

Purpose

The to measurement monitors the number of intervals without RTCactivity for foreign subscribers roaming in the HPLMN. It provides a toolto immediately detect loss of connectivity for foreign roaming subscribers.

The from measurement monitors the number of intervals withoutreceiving RTC activity for your own subscribers roaming in VPLMNs. Itidentifies major interconnectivity problems for your roaming subscribers.

Formula

# intervals without RTC * weight (PLMN)


None.

RTC Average Transaction Length

Purpose

The to measurement identifies the average length of time it takes for acall to be terminated to a roaming subscriber. The average transactionlength indicates the total length of time it takes to terminate a call to aroaming subscriber.

The from measurement identifies the average length of time it takes for acall to be terminated to a foreign subscriber roaming in the home network.The average transaction length indicates the total length of time it takesto terminate a call to a foreign subscriber roaming in the home network.

Formula



None.



RMS GSM MeasurementsCAMEL measurements

A

CAMEL measurements

CAMEL volume

Purpose

The to measurement monitors the number of CAMEL InitialDP messagesreceived by the HPLMN from individual VPLMNs.

The from measurement monitors the number of CAMEL InitialDPmessages sent by the HPLMN to VPLMNs.

Formula

# CAMEL InitialDPs * weight (PLMN) / measurement period


None.

CAMEL errors

Purpose

This measurement monitors the number of errors indicated by: errorcodes in TCAP ABORTs, TCAP REJECTs and TCAP ENDs; and releasecodes in CAMEL ReleaseCalls.

The to measurement monitors the number of unsuccessful CAMELmessages for foreign subscribers roaming in the HPLMN.

The from measurement monitors the number of unsuccessful CAMELmessages for your own subscribers roaming in VPLMNs.

Formula

# errors in CAMEL * weight (PLMN) / measurement period


Returned error codes or release causes for CAMEL.Returned error code/release cause and SCCP Calling Party address pairsfor CAMEL.




A

Returned error code/release cause and SCCP Called Party address pairsfor CAMEL.

CAMEL error rate

Purpose

The to measurement monitors the ratio of unsuccessful CAMEL messagessent by a VPLMN to the HPLMN versus the total number of attemptedmessagess sent by the same VPLMN.

The from measurement monitors the ratio of unsuccessful CAMELmessages sent by the HPLMN to a VPLMN versus the total number ofattempted messages sent by the HPLMN to the same VPLMN.

Formula

(# failed CAMEL / # attempted CAMEL) * weight (PLMN)


Returned error codes or release causes for CAMEL.Returned error code/release cause and SCCP Calling Party address pairsfor CAMEL.Returned error code/release cause and SCCP Called Party address pairsfor CAMEL.

CAMEL absence

Purpose

The to measurement monitors the number of intervals since a CAMELInitialDP message was last received from individual VPLMNs.

The from measurement monitors the number of intervals since a CAMELInitialDP message was last sent to individual VPLMNs.

In both cases this may point to a connectivity problem with CAMELservices.

Formula

# intervals without CAMEL InitialDP * weight (PLMN)




A


None.



RMS GSM MeasurementsUSSD measurements

A

USSD measurements

USSD volume

Purpose

The to measurement monitors the number of USSDProcessUnstructuredSSRequest messages received by the HPLMN fromindividual VPLMNs.

The from measurement monitors the number of USSDProcessUnstructuredSSRequest messages sent by the HPLMN toVPLMNs.

Formula

# USSD ProcessUnstructuredSSRequests * weight (PLMN) /measurement period


None.

USSD errors

Purpose

This measurement monitors the number of errors indicated by: errorcodes in TCAP ABORTs, TCAP REJECTs and TCAP ENDs.

The to measurement monitors the number of unsuccessful USSDmessages for foreign subscribers roaming in the HPLMN.

The from measurement monitors the number of unsuccessful USSDmessages for your own subscribers roaming in VPLMNs.

Formula

# errors in USSD * weight (PLMN) / measurement period




A


Returned error codes for USSD.Returned error code and SCCP Calling Party address pairs for USSD.Returned error code and SCCP Called Party address pairs for USSD.

USSD error rate

Purpose

The to measurement monitors the ratio of unsuccessful USSD messagessent by a VPLMN to the HPLMN versus the total number of attemptedmessagess sent by the same VPLMN.

The from measurement monitors the ratio of unsuccessful USSDmessages sent by the HPLMN to a VPLMN versus the total number ofattempted messages sent by the HPLMN to the same VPLMN.

Formula

(# failed USSD / # attempted USSD) * weight (PLMN)


Returned error codes for USSD.Returned error code and SCCP Calling Party address pairs for USSD.Returned error code and SCCP Called Party address pairs for USSD.

USSD absence

Purpose

The to measurement monitors the number of intervals since a USSDProcessUnstructuredSSRequest message was last received fromindividual VPLMNs.

The from measurement monitors the number of intervals since a USSDProcessUnstructuredSSRequest message was last sent to individualVPLMNs.

In both cases this may point to a connectivity problem with USSDservices.




A

Formula

# intervals without USSD ProcessUnstructuredSSRequest * weight(PLMN)


None.



RMS GSM MeasurementsGPRS measurements

A

GPRS measurements

GPRS volume

Purpose

The to measurement monitors the number of updateGPRSlocationmessages received by the HPLMN from individual VPLMNs.

The from measurement monitors the number of updateGPRSlocationmessages sent by the HPLMN to VPLMNs.

Formula

# updateGPRSlocations * weight (PLMN) / measurement period


None.

GPRS errors

Purpose

This measurement monitors the number of errors indicated by: errorcodes in TCAP ABORTs, TCAP REJECTs and TCAP ENDs.

The to measurement monitors the number of unsuccessfulupdateGPRSlocation messages for foreign subscribers roaming in theHPLMN.

The from measurement monitors the number of unsuccessfulupdateGPRSlocation messages for your own subscribers roaming inVPLMNs.

Formula

# errors in updateGPRSlocation * weight (PLMN) / measurement period


Returned error codes for updateGPRSlocation.Returned error code and SCCP Calling Party address pairs forupdateGPRSlocation.




A

Returned error code and SCCP Called Party address pairs forupdateGPRSlocation.

GPRS error rate

Purpose

The to measurement monitors the ratio of unsuccessfulupdateGPRSlocation messages sent by a VPLMN to the HPLMN versusthe total number of attempted messagess sent by the same VPLMN.

The from measurement monitors the ratio of unsuccessfulupdateGPRSlocation messages sent by the HPLMN to a VPLMN versusthe total number of attempted messages sent by the HPLMN to the sameVPLMN.

Formula

(# failed updateGPRSlocation / # attempted updateGPRSlocation) *weight (PLMN)


Returned error codes for updateGPRSlocation.Returned error code and SCCP Calling Party address pairs forupdateGPRSlocation.Returned error code and SCCP Called Party address pairs forupdateGPRSlocation.

GPRS absence

Purpose

The to measurement monitors the number of intervals since anupdateGPRSlocation message was last received from individual VPLMNs.

The from measurement monitors the number of intervals since anupdateGPRSlocation message was last sent to individual VPLMNs.

In both cases this may point to a connectivity problem with GPRSservices.




A

Formula

# intervals without updateGPRSlocation * weight (PLMN)


None.



RMS GSM MeasurementsNormalised measurements

A

Normalised measurements

Some of the measurements made by the Roaming Monitoring System arenormalised. This means that the absolute result of the measurement ismultiplied by a scaling (normalisation) factor. This adjustmentcompensates for the different capacities of the PLMNs.

Each measurement is allocated an individual scaling factor for eachPLMN. During system configuration, your System Administrator sets thenormalisation factors to meaningful values.

The normalisation factor is typically based on the number of visitors fromor to a particular PLMN.

Example

For example, if you have roaming agreements with three PLMNs:

• PLMN1 and PLMN3 generate double the traffic of PLMN2• PLMN3 is in a sensitive area, therefore you want earlier warning of

potential overloading at PLMN3 compared to PLMN1 and PLMN2.

Example PRN volume measurement:

PLMN1 is allocated a normalisation factor of 1, meaning that the PRNvolume is multiplied by 1 to obtain the normalised result.

PLMN2 is allocated a normalisation factor of 2 because it has half thetraffic of PLMN1. This means that although the PRN volume is half thatof PLMN1, the normalised results are identical – in other words PLMN2would become overloaded at half the PRN volume of PLMN1.

Relative traffic 2 1 2

PRN volume 100 50 100

Normalisation factor 1 2 1.25

Normalised PRN volume 100 100 125

PLMN1 PLMN2 PLMN3



RMS GSM MeasurementsNormalised measurements

A

PLMN3 has the same capacity as PLMN1, but is allocated anormalisation factor of 1.25 to provide an earlier warning of overload. Forexample, if the warning threshold is set to 120, only PLMN3 will generatea warning.

Of course, this example is simplified. Your System Administrator willprobably also include other aspects of performance when determining thenormalisation factors.



RMS GSM MeasurementsMeasurement performance limits

A

Measurement performance limits

General

Latency

Depending on system loading, it may take up to a few seconds to updateRMS GSM displays with new information. Compared with the typicalmeasurement interval of five minutes between updates, this latency isnegligible.

7-Day Alarmogram option

Note This option is only available if you have purchased the 7-dayAlarmogram + Customer Care Web Interface Function Upgrade

Alarmogram

A new Alarmogram should start within 15 seconds.

When using the scroll bar new data should be displayed within 5 seconds.After data has been displayed for the first time it is stored in a cache. Datafrom cache should be displayed immediately.

Time Series Histogram

A new Time Series Histogram should display within 5 seconds.

When using the scroll bar new data should be displayed within 1 second.After data has been displayed for the first time it is stored in a cache. Datafrom cache should be displayed immediately.



Glossary

ACM Address Complete Message. The ISUP procedure at which pointthe ringing tone starts.

AIN Advanced Intelligent Network.

A-interface The interface between an MSC and a BSS.

A Link Access Link. A signalling link which connects a signalling endpoint and its home pair of STPs.

ANM Answer Message.

ANSI The American National Standards Institute (ANSI), a non-profitorganization, made up of various expert committees, thatpublishes standards for use by national industries. ANSI hasadopted the IEEE standards for local area networks.

API Application Program Interface.

Area Group An Area Group contains a list of STP pairs, together with theirassociated SCPs, SSPs, and CCSSOs.Each acceSS7 user is a member of a single area group.

The list of STP pairs is defined by a System Administrator.

Partitioning the SS7 network in this way eases the task ofmanaging the network, because a user is configured to monitoronly those links in a specific area group.

ARIA Advanced Roaming Intelligence Agent - the name used previouslyfor Roaming Management System.

ASCII American Symbolic Code for Information Interchange

ASN.1 Abstract Syntax Notation 1. A specification language for thesyntax used to exchange information between two entities.

RMS GSM Operator Manual Glossary-1

RMS.Glossary.fm Modified: 29 Mar 2002 Mid v.0.0RMS.Glossary.fm Modified: 29 Mar 2002 Mid v.0.3

ATL The Average Transaction Length (ATL) is the average length oftime taken for transactions to complete. The length of atransaction is the number of seconds between the TC-BEGIN andthe TC_END.

Background Session acceSS7 provides the facility to exit a monitoring session but leaveit running as a background activity. Background monitoringsessions continue to operate even if you log out. Both real-timeand post-capture monitoring sessions can be run as backgroundtasks. You can run multiple Call Trace and Protocol Analysissessions both interactively and as background sessions.

The results from a Background Session are stored in a “SessionBuffer”.

BIB The Backward Indicator Bit (BIB) is part of the message sequencedata which is added to Signal Units (SUs) at Message TransferPart (MTP) Level 2 to ensure that Signal Units (messages) sent tothe other end of a Link are in the correct sequence and withouterror.

B Link Bridge Link. A signalling link which connects STP pairs thatperform work at the same functional level.B links are arranged in sets of 4 sometimes referred to as quads.

BSN Backward Sequence Number (BSN) is the part of the messagesequence data which is added to Signal Units (SUs) at MessageTransfer Part (MTP) Level 2 to identify the last Signal Unit thatwas acknowledged/processed by the sending code.

BSS Base Station Subsystem.

BSSMAP BSS Mobile Application Part.

BTS Base Transceiver Station.

CAMEL Customised Application for Mobile Enhanced Logic.

CAP CAMEL Application Protocol.

CBA Change Back Acknowledgement, a message relating to linkchangeovers.

Glossary-2 RMS GSM Operator Manual

RMS.Glossary.fm Modified: 29 Mar 2002

CBD Change Back Declaration, a message relating to link changeovers.

CCS Common Channel Signalling.

CCSSO For the purpose of processing, each Common Channel SignallingSwitching Office (CCSSO) is treated as an SSP. Thus, allprocessing applicable to SSPs is also applied to CCSSOs.

CCWI Customer Care Web Interface is available as a Feature UpgradeProduct to the standard RMS software. It allows customer carestaff to view error details for a selected network on any of the lastseven days using a standard web browser.

CIC The Circuit Identification Code (CIC) is the part of a signallingmessage used to identify the circuit being set up between twosignalling points.

CDR Call Detail Records. ISUP transactions.

CLASS Service Custom Local Area Signalling Services (CLASS) provide call-management features to residence and small business customersenabling them to load and maintain call-processing instructionsfor incoming and/or outgoing calls.

C Link Cross Link. A signalling link which connects mated pairs of STPs.

Configuration The Configuration details identify the conditions under whichdata in a “Session Buffer” was collected. The details recordeddepend upon the type of session:

• For Protocol Analysis sessions this includes the selected links,and the triggers and filters applied

• For Call Trace sessions this includes the selected links, andthe telephone numbers being traced

When editing a Session Buffer you can view the stored data andapply monitoring configurations to modify the data being viewed.After modifying your view of the data you can save the modifiedview for later analysis (referred to as “Post-capture Analysis”).

COO Change Over Order, a message relating to link changeovers.

DCS 1800 Digital Cellular System at 1800 MHz (now GSM 1800).



DES Data Encryption Standard.

D Link Diagonal Link. A signalling link which connects STP pairs thatperform work at different functional levels.D links are arranged in sets of 4 sometimes referred to as quads.

DPC The Destination Point Code (DPC) is that part of a Routing Labelthat identifies where the signalling message should be sent.

DXI Digital eXchange Interface.

ECA Emergency Changeover Acknowledgment, a message relating tolink changeovers.

ECO Emergency Changeover Order, a message relating to linkchangeovers.

E Link Extension Link. A signalling link which connects a signallingpoint and its remote pair of STPs.

Erlang A unit of average traffic density.

ETSI European Telecommunications Standards Institute.

FIB The Forward Indicator Bit (FIB) is part of the message sequencedata which is added to Signal Units (SUs) at MTP Level 2 toensure that Signal Units (messages) sent to the other end of aLink are in the correct sequence and without error.

FISU A packet transmitted between Message Transfer Parts (MTPs) tomaintain a continuous flow of data over the signalling links whenthere are no Message Signal Units (MSUs) or Link Status SignalUnits (LSSUs) to be sent.

FISUs carry basic level 2 information only, for example, theacknowledgment of the last MSU.

F Link Fully Associated Links. A signalling link which connects twosignalling points when there is a high community of interestbetween them and it is economical to link them. It is sometimescalled associated signalling.

FSM Forward Short Message. One of the MAP procedures.



FSN The Forward Sequence Number (FSN) is a number which is partof the message sequence data added to Signal Units (SUs) at MTPLevel 2. It identifies the SU in which it appears. All SUs areassigned an FSN of from 0 to 127. FISUs and LSSUs are notassigned new FSNs and retain the FSN of the last MSU sent.

Function Upgrade Function Upgrades are additional features that are purchased toadd extra functions to the standard RMS installation.

GMSC Gateway Mobile Services Switching Centre.

GPRS General Packet Radio Service.

GRA Circuit Group Acknowledgement.

GRS Circuit Group Reset.

GSM Global System for Mobile communications.

GSM 1800 GSM operating at 1800 MHz – formerly DCS 1800.

GSM 1900 GSM operating at 1900 MHz – formerly PCS 1900.

GSMC GSM CDMA, where CDMA is Channel Domain Multiplex Access.

GSMT GSM TDMA, where TDMA is Time Domain Multiplex Access.

HLR Home Location Register.

HPLMN Home PLMN.

IAM Initial Address Message (ISDN user part). The ISUP procedurewith which dialled digits are sent to the destination.

IDN Integrated Digital Network.

IEEE Institute of Electrical and Electronic Engineers, and the interfaceformat which bears its name.

IFPC Interface Processor Card.

IMEI International Mobile Equipment Identity.



IMSI International Mobile Subscriber Identity.

IN Intelligent Network.

INAP Intelligent Network Application Part.

ISDN The Integrated Services Digital Network (ISDN) is an integrateddigital network in which the same digital switches and digitalpaths are used to establish connections for different services, forexample telephony and data.

ISUP The Integrated Services Digital Network user Part (ISUP) is thatpart of a signalling node that is used to develop and formatsignalling messages.

ITU-T X.208 Recommendation from the Telecommunication StandardizationSector of the ITU (International Telecommunication Union). TheX-series recommendations cover Data Networks and Open SystemCommunication. X.208 is Model and Notation - Specification ofAbstract Syntax Notation One (ASN.1).

ITU-T X.209 Recommendation from the Telecommunication StandardizationSector of the ITU (International Telecommunication Union). TheX-series recommendations cover Data Networks and Open SystemCommunication. X.209 is Model and Notation - Specification ofBasic Encoding Roles for Abstract Syntax Notation One (ASN.1).

ITU-T X.721 Recommendation from the Telecommunication StandardizationSector of the ITU (International Telecommunication Union). TheX-series recommendations cover Data Networks and Open SystemCommunication. X.721 is Structure of Management Information -Definition of Management Information.

LAP Link Access Protocol.

LAPD LAP D-channel.

LAPDm Modified LAPD.

LI The Length Indicator (LI) is a six-bit field which differentiatesbetween MSUs, LSSUs, and FISUs. If the binary value of the fieldis less than 63, this field indicates the length of a signal unit.



LIDB The Line Information Database (LIDB) is used for customerbilling information.

Link A Link is one of the components of a Linkset. Each Link has twochannels, one for each direction of data flow. The data rate isusually 56 or 64 kbits/s.

Linkset A Linkset, which consists of a number of Links (maximum 16),interconnects two Signalling Points (SPs). Information is sharedevenly across the Links in a Linkset and those of the alternativeroute (loadsharing).

If a Link fails, the load is transferred to the remaining Linkswithin that Linkset.

LMSI Local Mobile Station Identity.

LNP Local Number Portability.

Log in To begin a session on the computer by entering the necessaryinformation, such as your login name and password.

LPLMN Local PLMN.

LSSU Link Status Signal Units (LSSUs) carry information relating tothe status of the Links. Normally, LSSUs are only seen during theinitial alignment procedure when a Link is brought into servicebut are used at other times, for example, to stop the flow of SignalUnits (SUs) when processors are busy.

MAP Mobile Application Part.

MCC Mobile Country Code.

MEB ‘Maverick Operating System’ Event Bus.

MOC Mobile Originated Call.

MoU Memorandum of Understanding.

MOU Minutes of Use.



MS Mobile Station.

MSC Mobile Switching Centre.

MSRN Mobile Subscriber Roaming Number.

MSU Message Signal Unit (MSUs) carry all Service/Application datasent on the SS7 Network. The amount of data per MSU is limitedto 273 octets maximum.

MT The Message Type (MT) is the part of a signalling message used toidentify the purpose and format of the octets that follow.

MTC Mobile Terminated Calls.

MTP The function of the Message Transfer Part (MTP) is to reliablytransfer messages across the SS7 Network in the correct sequenceand without loss or duplication.

NAM Network Alarm Manager.

O&M Operations and Maintenance.

Object There are four types of object that you can manipulate using theObject Management tool:

• Signalling Unit (SU) Templates• Protocol Analysis Configurations• Call Trace Configurations• Session Buffers

Octet Instead of bytes (which is computer jargon for 8 bits), the termoctet is used in SS7 to represent 8 bits. The longest SS7 messagescan contain up to 273 octets of data (which does not include theMTP Level 2 head and tail of the message).

OMAP Operations and Maintenance Application Part.

OMC O&M Centre.

OPC Originating Point Code (OPC) is the part of a Routing Label thatidentifies which SU sent a signalling message.



OPLMN Other PLMN.

OSI Open Systems Interconnection.

OSS Operations Support Systems.

Owner You are the owner of an object if you either:

• Create the object in your “Private Workspace”• Move/copy the object from the “Public Workspace”

If you are the owner of an object, you can edit, delete, move, copy,or rename the object in both your private workspace and thepublic workspace.

An object can also be owned by the system. In this case you cancopy the object to your private workspace and work on it fromthere.

Password An encrypted sequence of characters used by HP-UX to identify anauthorized user and to permit authorized login on a system.

PCS 1900 Personal Communications System operating at 1900 MHz (nowGSM 1900).

PIN Personal Identification Number.

PLMN Public Land Mobile Network.

PNO Public Network Operator.

POTS Plain Old Telephone Service.

Private Workspace Your private workspace is where acceSS7 stores the objects thatyou own. You can use the Object Management tool to list, view,move, and copy the objects in your workspace.

Apart from yourself, the only users with access to your privateworkspace are those with System Administrator privileges. If youwant other users to have access to objects in your workspace, moveor copy the object to the “Public Workspace”.

PRN Provide Roaming Number. One of the MAP procedures.



PSTN Public Switched Telephone Network.

Public Workspace The public workspace is where acceSS7 stores objects that can beaccessed by all users. By moving or copying objects to thisworkspace, you make it possible for other users to share yourwork.

When you move or copy an object to the public workspace youcontinue to own the object, and can edit, delete, or rename thatobject. If you want to change an object in the public workspacethat belongs to another user, you must copy the object to your“Private Workspace” before working on it.

Note Users with System Administrator privileges can move or copyobjects from any user’s workspace into the public workspace.When doing this, they can change the ownership of the object fromthat of the original user to being owned by System.

PVLR Previous Visitor Location Register.

QoS Quality of Service. In RMS GSM, an inverse measure of quality ofservice is given by the Error Rate measurement.

RCP The signalling Rout-Set-Test Cluster Prohibited signal.

RCR The signalling Rout-Set-Test Cluster Restricted signal.

RCT The signalling Rout-Set-Test Congestion Test message.

REL Release Message. An ISUP procedure.

RES Resume Message.

RLC Release Complete.

RP Roaming Porter.

Routing Label The Routing label is the part of a signalling message used toidentify the origin, and the destination of a message, and the linkneeded for message transmission.



RPLMN Remote PLMN.

RSP The signalling Rout-Set-Test Prohibited signal.

RSR The signalling Rout-Set-Test Restricted signal.

RST The signalling Rout-Set-Test messages: RSP, RSR, RCP and RCR.

RTC Roamers’ Terminating Calls. Correlation of the ISUP IAMprocedure with the MAP PRN procedure. The result of thecorrelation shows how many initiated calls are successful.

SAM Subsequent Address Message.

SCCP Signalling Connection Control Part (SCCP) is the part of asignalling node that is used when the SCCP method of end-to-endsignalling is invoked.

SCE Service Creation Environment.

SCMG SCCP Management.

SCP The Service Control Point (SCP) acts as a data store for theNetwork by providing a query/response dialogue for certainservices provided by the Network, for example, an 800 numbertranslation query sent from an SSP to a SCP.

Note The SCP is also called a Network Control Point (NCP) by AT&T ora Data Base Node (DBN) by ANSI.

Session A session can be any of the following:

• Real-time, where you are connected to the computer while thesession is running

• Post-capture, where you analyze data collected during someprevious session

• A “Background Session”, which runs to collect SS7 signallingdata even when you are not connected to the computer

The results from a session are stored in a “Session Buffer”, whichyou can examine at a later time.



Session Buffer A session buffer is produced by each Call Trace or ProtocolAnalysis monitoring session that stores captured data. EachSession Buffer contains the following information:

• The SS7 traffic captured as a result of the monitoring session• The configuration details under which the data was captured• The start and stop times for the monitoring session• A notes field

When a session buffer is first created, it is given a name consistingof a sequence of digits by acceSS7. You can use the ObjectManagement tool to assign a meaningful name to the buffer.

SI The Service Indicator Field (SI) is a subset of the ServiceInformation Octet (SIO) that is used to perform messagedistribution and, in some special applications, message routing.

SIB LSSU counts with Busy status indication.

SIO The Service Information Octet (SIO) is a binary code sent with aMessage Signal Unit (MSU) for the purpose of messagedistribution, discrimination, and in some cases, establishingpriorities for messages.

SIPO LSSU counts with Processor Outage status indication.

Site Your acceSS7 monitoring hardware is located at Monitoring Sites.Each site normally monitors a single STP.

SLC The Signalling Link Code (SLC) is a field with certain networkmanagement messages which indicates the particular signallinglink to which the message refers among those interconnecting thetwo involved Signalling Points (SPs).

SLT Signalling Link Test.

SLTA Signalling Link Test Acknowledgment, part of an SLT.

SLTM Signalling Link Test Message, part of an SLT.

SMAP System Management Application Part.



SMS Short Message Service.

SM-SC Short Message - Service Centre.

SMSCB SMS Cell Broadcast.

SNM Signalling Network Management.

SP Send Parameters. One of the MAP procedures.

SP The nodes in an SS7 network (Service Switching Points (SSPs),Signalling Transfer Points (STPs) and Service Control Points(SCPs) are commonly referred to as Signalling Points (SPs).

SS The Subservice Field (SS) is a subset of the Service InformationOctet (SIO) that is used to provide discrimination betweenInternational and National messages. This field may also be usedto establish priorities for messages.

SS Supplementary Services.

SSA Subsystem Allowed.

SSN The subsystem number (SSN) is a number used to identify anSCCP user (e.g. ISDN-User Part or TCAP).

SSP Service Switching Points (SSPs) are points of origin of a requestfor service, for example, an End Office. The SSPs send messages(requests) on the Signalling Network to set up calls or accessservice features requested by the customer.

SSP can also stand for Subsystem Prohibited.

SST Subsystem Status Test.

SS7 Signalling System 7.



Statistics The acceSS7 System maintains the following Statistics for eachLink:

• Number of occurrences of each type of LSSU over a 60 secondinterval.

• Number of FIB/BIB inversions over a 60 second interval.• Number of frames in error over a 60 second interval.• Duration of unavailability over a 60 second interval.• Duration of oscillating status over a 60 second interval.• Count of SLTM MSUs over selected time interval.

- Range: - 1 to 30000 seconds.- Default: - 300 seconds.

• Count of SLTA MSUs over selected time interval.- Range: - 1 to 30000 seconds.- Default: - 300 seconds.

• SLC value in last SLTM message.• Current channel state for each channel.• Number of link status changes over selected time interval.

- Range: - 1 to 30000 seconds.- Default: - 60 seconds.

• The number of MSU octets detected on each channel over a 60second interval.

Status The Status of each channel on each Link is derived from the datacarried on the channel.

The following channel states are defined for each channel:

• Out of Sync• Out of Service• Processor Outage• Busy• In Service• Idle



STP The Signalling Transfer Point (STP) is a packet switch whichperforms the message routing function within a SS7 Network.

Each Service Switching Point SSP is connected to a mated pair ofSTPs which is connected in a mesh to another mated pair of STPs.Redundancy in this quad configuration allows for failure of anyone STP.

Quads can be chained together to extend the network.

SU A Signal Units (SU) is a packet of data (a message) sent on aSignalling Link. There are three types of Signal Unit,

• Message Signal Unit MSUs,• Link Status Signal Units LSSUs and• Fill-in Signal Units FISUs.

SUD Signal Unit Display Format.

SU Pump Signal Unit Pump. An application for transferring messages(MSUs) within an acceSS7 system from the IFPCs to the remotesite server for the same IFPCs.

SUS Suspend Message.

TCAP Transaction Capabilities Application Part (TCAP) is used forquerying databases and carrying the response.

TCH Traffic Channel.

TMN Telecommunications Management Network.

TMSI Temporary Mobile Subscriber Identification.

TVE Threshold Violation Event.

UL Update Location. One of the MAP procedures.

UM GSM Air Interface.



User Quota Your user quota determines how much disc space you have on eachcomputer in your acceSS7 monitoring system. Your disc space isused to store “Session Buffer” and other data used whenexamining the acceSS7 system.

Your initial quota is allocated when your user workspace is set upon a computer. Any user with System Administration privilegescan use the System Administration tool to change your quota foryou.

User Type acceSS7 allows you to control the configuration of the users onyour system. This is achieved by allowing you to create structuresknown as user types.

A user type is a statement of the acceSS7 system configurationwhich you wish to grant to a particular group of users. Each usertype that is created must be given a unique name, by which it canbe referred to in other parts of the system.

By creating different user types, you can configure the users ofyour system as you choose.

USSD Unstructured Supplementary Service Data.

VLR Visitor Location Register.

VMS Voice Messaging/Mail System.

VPLMN Visited PLMN.

VPN Virtual Private Network.

WAP Wireless Application Protocol.

WIN Wireless Intelligent Network.

(X)UDTS (Extended) Unitdata Service.



Index

AacceSS7

logging off 2-9Map 2-5starting 2-2

Active Histogramsclosing 6-13icons 6-11purpose 6-2using 6-2

aggregation factor 1-9, 4-2, 4-7, 4-15changes 4-15

aggregation period 1-9, 4-2, 4-7, 4-10, 4-14timestamp 4-14

Alarm Management Reporter 8-2starting 2-3

Alarm Management Reports 8-2Instant Reports 8-5Scheduled Reports 8-2what they show 8-9

Alarmogramaudible warning 4-13block colours 4-7blocks 4-7closing 4-20finding a PLMN 4-16, 6-7icons 4-18Measurement Summary 4-4, 4-17PLMN Overview 4-4purpose 4-2range of data 4-10resizing panes 4-6row ranking 4-9, 4-13row ranking (suppressing) 4-13rows 4-4, 4-9, 4-13searching for a PLMN 4-16, 6-7starting 2-3, 2-7using 4-2

audible warning 4-13

auto-rankingfreezing 6-6

Bbackground to RMS 1-2

Ccalculated results 5-8, 6-5, 7-8, A-2CAMEL

absence A-26error rate A-26errors A-25volume A-25

CCWIclosing 9-6error descriptions 9-5new search 9-5

closingActive Histograms 6-13Alarmogram 4-20CCWI 9-6Radar Diagrams 5-16RMS session 2-9Time Series Histograms 7-24

colourActive Histogram bars 6-8Alarmogram blocks 4-7order on Time Series Histogram bars 7-15Radar Diagram polygon 5-9

combined viewTime Series Histogram 7-20

critical threshold 5-9, 6-8, 7-9

Ddata

available dates 4-5graphical presentation 1-7snapshot 2-10source 1-6

RMS GSM Operator Manual Index-1

RMSIX.fm Modified: 13 Jun 2002 Mid v.0.0RMSIX.fm Modified: 13 Jun 2002 Mid v.0.3

data value scaling 7-10changing to 7-12

detecting roaming problems 1-5drilldown

error display options 7-18

Eending

RMS session 2-9error descriptions

CCWI 9-5errors

masked and unmasked 7-21exploded view

Time Series Histogram 7-20

Ffreeze

auto-ranking 6-6FSM


Ggenerating reports

Instant Reports 8-5Scheduled Reports 8-2

geographical areas 2-6getting more detail 4-19, 5-15, 6-12GPRS


graphical display 1-7graphical snapshot 2-10

Iicons 2-3

Active Histograms 6-11Alarmogram 4-18Radar Diagrams 3-6, 5-14Roaming Map 2-6Time Series Histograms 7-23

incomplete measurements 5-12, 6-10, 7-22

informationsaving a data snapshot 2-10saving a graphical snapshot 2-10

Instant Reports 8-5

Llatency A-36logging off 2-9loss of data 4-18loss of producer 5-13, 6-11, 7-22loss of traffic 5-13, 6-11, 7-22

Mmasked errors

viewing 7-21measurement bars

colour 6-8measurement intervals 7-7order 6-5, 6-6, 6-9

measurement categorieschanging 7-18choosing 7-18colour key 7-16descriptions 7-16examining 7-15for selected bar 7-16order 7-15viewing behaviour 7-17

measurement history 1-5measurement interval 1-3

Time Series Histogram bars 7-7total number stored 7-7

measurement results 5-8, 6-5, 7-8Measurement Summary

viewing on Alarmogram 4-17measurement types 1-3, A-3measurements

axes 5-7choosing sub-categories 7-18direction A-3, A-4incomplete 5-12, 6-10, 7-22Measurement Summary 4-4selecting 6-3types A-3

Index-2 RMS GSM Operator Manual

RMSIX.fm Modified: 13 Jun 2002

Nnetwork exclusion 6-10Network Information 9-4Network Information Search 9-3new search

CCWI 9-5normalisation A-34

example A-34

OOpenView Map 2-5order

of Active Histogram bars 6-5, 6-6, 6-9of blocks in Time Series Histogram bars 7-15

origin offset 5-12

Pperformance limits A-36PLMN Overview 4-4PLMNs

deselecting 4-4, 4-17on Active Histograms 6-4on Roaming Map 2-6, 3-2removing from a measurement 6-10selecting 3-4, 7-4subset 3-5, 5-14totals exceeding thresholds 6-8

PRNabsence A-9ATL A-10error rate A-9errors A-8volume A-8

purposeof Active Histograms 6-2of Alarmogram 4-2of Radar Diagrams 5-2of RMS 1-2of Roaming Map 3-2of Time Series Histograms 7-2

RRadar Diagram Launcher 2-3, 5-2

starting 2-3, 2-8starting Radar Diagrams 5-4

Radar Diagramsaxes 5-7closing 5-16configuring 5-2icons 3-6, 5-14origin offset 5-12polygon 5-9purpose 5-2starting 2-3, 2-7starting from the Radar Diagram Launcher 5-4subsets 5-6using 5-2

resizingAlarmogram panes 4-6

resultscalculated 5-8, 6-5, 7-8, A-2normalised A-34normalised - example A-34values 6-5worst case 5-8, 6-5, 6-9, 7-8

RMSbackground 1-2icons 2-3starting 2-2

Roaming Mapicon 2-6PLMNs 3-2purpose 3-2starting 2-5using 3-2

roaming problems 1-5roaming procedures 1-2, A-2roaming status 1-2RTC

absence A-24ATL A-24error rate A-23errors A-23volume A-22



Ssaving

displayed information 2-10graphical data 2-10raw data 2-10

scale adjustment 5-9scaling

changing between threshold and data value 7-12

Time Series Histogram 7-20SCCP

in Time Series Histograms 7-19Scheduled Reports 8-2scroll bar

on Active Histograms 6-4selected bar 7-14selecting

a single measurement 6-3a single PLMN 7-4

setting upRadar Diagram subsets 5-6

source of data 1-6SP

absence A-15, A-21ATL A-16error rate A-15, A-21errors A-14, A-20volume A-14, A-20

startingacceSS7 2-2Alarm Management Reporter 2-3, 2-4Alarmogram 2-3, 2-7Radar Diagram Launcher 2-8Radar Diagrams 2-3, 2-7RMS 2-2RMS displays 2-2Roaming Map 2-5

statuscritical 5-11, 6-9normal 5-9, 6-9warning 5-10, 6-9

Subset button 3-5, 5-14subset of PLMNs 3-5, 5-14subsets of Radar Diagrams 5-6

Ttask overview 1-9

investigating problems 1-10monitoring performance 1-9monitoring solutions 1-13

threshold scaling 7-9changing to 7-12

thresholds 1-4on Active Histograms 6-8on Alarmogram 4-16on Radar Diagrams 5-9on Time Series Histograms 7-9scale adjustment 5-9

Time Series Histogramsbar totals 7-11closing 7-24combined view 7-13data value scaling 7-10exploded view 7-13icons 7-23measurement bars 7-7purpose 7-2SCCP Messaging 7-19selected bar 7-14threshold scaling 7-9using 7-2

Total MAPabsence A-18error rate A-18errors A-17volume A-17

UUL

absence A-6ATL A-7error rate A-6errors A-5volume A-5

unmasked errorsviewing 7-21

USSDabsence A-29error rate A-29errors A-28volume A-28



Wwarning

audible 4-13warning threshold 5-9, 6-8, 7-9window limit 4-19, 5-15, 6-12, 7-2worst case results 5-8, 6-5, 6-9, 7-8





RMS.Backpage.fm
Modified: June 2002

RMS.Backpage.fm Modified: June 2002 Mid v.0.3

© Copyright 2002Agilent Technologies UK LtdPrinted in UK June 2002

ManufacturingPart No.J6743-91001-058

Reorder No.J6743-91001-058

Date post:	21-Apr-2015
Category:	Documents
Upload:	reut-avraham-jerby
View:	60 times
Download:	5 times

C 7[1].30 Operator Guide RMS

Documents