Siemens SPOTS Performance and KPI Monitoring

Copyright 2004 © Siemens SA, All rights reserved

Product Description SPOTS Performance Management

SPOTS V12

July 2005

SPOTS - Performance Management SPOTS is the Performance Management module within the Siemens product portfolio. SPOTS offers Integrated Cross Domain Performance Management Solutions for telecommunication networks.

Issued by: Siemens SA, COM R&D1 NMP

Table of Contents

1 Introduction ...............................................................................................................5

1.1 Performance Management for all levels of the organisation .......................................7

1.2 Major Customer Benefits.............................................................................................8

1.3 Major features of SPOTS ............................................................................................9

1.4 Major improvements of V12 ......................................................................................11 1.4.1 Support for Configuration Management data: ............................................................ 11 1.4.2 New Online Monitoring feature (available with RT module): ...................................... 12 1.4.3 Unified SPOTS GUI.................................................................................................... 12 1.4.4 New OSS/J QoS API .................................................................................................. 12 1.4.5 Support to NetViewer 7.0 ........................................................................................... 12

2 Product features positioning .................................................................................13

3 Functions.................................................................................................................16

3.1 Graphical User Interface ...........................................................................................16

3.2 Data Collection..........................................................................................................17 3.2.1 Data Collection on UTRAN......................................................................................... 17 3.2.2 Data Collection on GERAN ........................................................................................ 17 3.2.3 Data Collection on CS and PS ................................................................................... 17

3.3 Data Storage.............................................................................................................18

4 Supported Traffic Measurements ..........................................................................19

5 Report Generation...................................................................................................20

5.1 Pre-defined Reports ..................................................................................................20 5.1.1 Pre-Defined Reports for PU load................................................................................ 21 5.1.2 Pre-Defined Reports for SS7 Surveillance ................................................................. 22 5.1.3 Pre-Defined Reports for Core Network (Circuit Switch Domain, CN-CS)................... 24 5.1.4 Pre-Defined Reports for Core Network (Packet Switched Domain, CN-PS) .............. 28 5.1.5 Pre-Defined Reports for Radio Access Network (GERAN Domain)........................... 31 5.1.6 Pre-Defined Reports for Radio Access Network (UTRAN Domain) ........................... 35

5.2 Ad-hoc Report Generator..........................................................................................37

5.3 SPOTS Reporting Language (SRL) ..........................................................................38

6 SPOTS Optional Modules.......................................................................................40

6.1 SPOTS Real Time Module........................................................................................40

SPOTS V12 Performance Management COM R&D1 NMP, July 2005

6.2 SNMP Alarm forwarding module .............................................................................. 42

6.3 Off-the-shelf HP OV TeMIP integration .................................................................... 42

6.4 SPOTS Web Reports module................................................................................... 43

6.5 Backup and Restore - BAR....................................................................................... 45

6.6 SPOTS Multi-vendor common 3GPP support:.......................................................... 46

7 Architecture ............................................................................................................ 47

7.1 High Availability ........................................................................................................ 48

7.2 Domain Management ............................................................................................... 48

7.3 User administration - Session control and roaming profiles...................................... 49

8 Open interfaces ...................................................................................................... 50

9 Abbreviations.......................................................................................................... 51

10 SPOTS Documentation .......................................................................................... 52


1 Introduction As a global leader in telecommunications products and services, Siemens is uniquely suited to

address the network infrastructure needs of mobile network operators. The need for highly reliable

and available networks dictates that the supplier of products and services understands the level of

commitment of a service provider and does not compromise their reputation.

As a company with over 150 years of communications experience Siemens enjoys the reputation

on understanding customer’s objectives and enhancing their competitiveness in the marketplace.

Siemens is highly committed to developing superior products and providing an unparalleled level of

service to meet its customers’ requirements.

With the introduction of GPRS and UMTS into the mobile market, it will be the first time that

operator can offer fast mobile data services to their customers. This allows totally new services and

business models creating new revenue streams. At the same time this will change the traditional

usage behaviour of mobile networks. Consequently this will have its impacts on the up to now

known load models. For the time being, nobody knows for sure what will really happen in the future

of UMTS, how the user community will accept the new technology and which new services will

make the race. But one thing is for sure, the network and business complexity increases

significantly. In this uncertain environment the operator has to make sure that he is aware of the

offered network performance and service quality.

SPOTS enables the operator to see what is happening in the network and generates all the

necessary information for taking the right decisions.

SPOTS system offers a high feature richness, reliability, scalability and modularity that ensure

suitable adaptation to customer needs and open-ended upgrading to match network growth while

preserving previous investment.


SPOTS Product Family is composed by SPOTS Long-Term, as mandatory module, and the

following optional modules:

• Real Time

• Backup & Restore

• SNMP Alarm Agent

• Web Reports

• Long Term Multi-Vendor Integration

Siemens has the know-how and worldwide presence to accurately assess the performance

requirements and assist network operators in designing complete and optimized solutions.

Siemens ultimate objective is to maximize customers’ business success, both today and into the

future as well.

With SPOTS Product Family, Siemens is offering a very powerful set of tools for monitoring and analysing the network traffic situation for multi-technology and multi-vendor Networks.


1.1 Performance Management for all levels of the organisation

SPOTS integrates seamlessly into the operational processes that depend on performance data.

At Network Operation & Maintenance (O&M) level, SPOTS permits efficient performance

monitoring of all parts of the GSM and UMTS mobile network: CS, PS, GERAN and UTRAN, by

one unified system. SPOTS not only covers Siemens own equipment, but can easily be enhanced

to integrate other vendors equipment as well. SPOTS detects and analyses problems at the

network layer. The QoS monitoring and alarming functionality with the continuous monitoring of key

indicators of the network shows exactly how well the network is performing at any given point in

time. Any deviations are caught, and displayed either in the monitoring panels or the alarm

browser, allowing for immediate analysis and if necessary, corrective action.

At Optimisation level, SPOTS enables early detection of bottlenecks and congestions, reducing

the impact on end-customers, and improving operator revenue.

SPOTS produces automatically sets of reports based on pre-defined KPIs, allowing the

optimisation team to efficiently tune the network. The reports and the metrics can be customised.

Further ad-hoc analysis capabilities allow an in depth investigation of the detected problems.

Operator can access locally or via remote access.

At Network Planning level, SPOTS helps to supervise traffic-load and key performance indicators

over long periods. SPOTS historical data analysis puts the Network Planning on a reliable basis.

SPOTS delivers the input for the correct dimensioning of the network equipment, shows

possibilities for network optimisation and produces the data for long-term network planning.

Regarding UMTS, SPOTS determines possible bottleneck as e.g. PS performance limit, CS

performance limit, or max. Number of sub/UMSC. Further analysis of interfaces completes the

perception of potential dimensioning problems.

As Network Planning Departments are typically separated from the O&M Centre, SPOTS allows

remote access from the working place. SPOTS results can easily be integrated with planning tools

or transferred to the office environment.

Management and Marketing profit from SPOTS comprehensive network analysis capabilities. For

example, SPOTS allows the track of overall figures like evolution of total number of CS or PS

subscriber and throughput. In the introductory phases of UMTS, SPOTS provides valuable

information regarding the customer use pattern as reliable input for pricing and market

communication purposes. SPOTS allows generation of network-wide reports to control quality-of-


service goals or service level agreements. Such kind of feedback becomes more relevant as the

UMTS technology provides new services and it is important to observe their customer acceptance.

1.2 Major Customer Benefits

Net margin:

Since SPOTS enables the customer to tune the network efficiently, it increases the overall net

margin. SPOTS helps to reduce network congestion, contributes to the optimised usage of system

resources and helps to schedule the network growth effectively on the basis of reliable

performance data that indicates future capacity requirements.

Cost reduction:

SPOTS is highly scalable solution, covering 2G, 2,5G and 3G in one system, reducing the number

of systems to maintain. Effective rationalisation through complete task automation of the whole

processing chain also significantly reduces the operating costs and reaction times.

Quality increase:

Early detection of upcoming bottlenecks gives the operator all the information required in order to

take the right decisions, before it affects the customer. In the end, network improvements increase

the overall quality and consequently contribute to the satisfaction of the end customer.

Plug-in architecture: Allowing smooth upgrades meaning reduced time-back-to operation and faster alignment with NE-

rollout (e.g.: alignment with Siemens releases or support for new Multi-vendor equipment). It also

reduces the acceptance efforts for Siemens service and Customer.


1.3 Major features of SPOTS

Historical data: With SPOTS Data Summarisation, performance information can be stored for long periods of time,

offering every possibility for effective long-term performance analysis for network planning and

management.

Reports: SPOTS is delivered with a set of comprehensive pre-defined reports that meet the most common

operator needs and allow immediate use of SPOTS. The reports reflect Siemens' long experience

in traffic analysis, system and network engineering, and address all organisation levels.

Report generator: Users can easily create new reports to implement their own analysis strategies. Additionally, they

are able to customise or enhance the delivered pre-defined reports. All in all, they are able to build

up a complete report library for their network.

KPIs: SPOTS supports and uses the Siemens Key Performance indicators – KPIs. They provide key

values about quality, performance and capacity and are used in day-to-day operations as well as in

the long term for planning and optimisation. KPIs are used within the pre-defined reports, and are

available to use in user-defined reports as well as for ad-hoc reporting.

QoS Online monitoring : SPOTS QoS Online monitoring allows the operator to know the status of the network at any given

point in time. This intelligence add-on based on Key indicators enables the operator to focus its

resources on improving performance, not determining performance.

QoS alarming: SPOTS alarming addresses today’s pro-active performance management requirements. SPOTS

automatically detects any degradation in performance based on Thresholds analysis, generates an

alarm that allows the operator to address the problem, before it causes a fault condition. The alarm

handling is compliant to Rec. ITU-T: X.733 and Rec. ITU-T: X.739.


Automation:

SPOTS automates the whole processing chain of performance analysis, from data collection up to

report distribution. Reports can be generated for routine distribution to OA&M, planning or

management.

Scalability: SPOTS application architecture assures a widely scalable system and tailored customer solutions

for all sizes of telecommunications networks. SPOTS is based on a truly distributed architecture,

where services are spread across the available servers.

3GPP Multi-vendor and multi-technology support: SPOTS open system architecture supports deployment in multi-technology and multi-vendor

environments. Besides the cost savings associated with having only one system such as reduced

maintenance costs, fewer 3rd party SW licenses, training etc., the operator gain a single view of

the network performance. A consistent presentation across vendors and technologies gives

knowledge of total network performance and allows for comparative evaluation.

Off-the-shelf solutions are available for mobile-, wireline- and data-networks being deployed to

over 80 operator’s world-wide.

Future-proof: A future-proof solution means protection of investments. SPOTS constantly keeps track of the

latest telecommunication developments to meet upcoming requirements from the market and its

users. SPOTS adapts to all kinds of network environments, now and in the future.


1.4 Major improvements of V12

1.4.1 Support for Configuration Management data:

SPOTS V12 allows customers to handle configuration data in order to:

• CM API file based available

• Import/export mechanism provided for updating the CM data

• Automation achieved via periodic CM data import

• Automatic management of network resources:

- Creation of objects (e.g. NEs, Cells, Trunk Groups, Signalling Links) – already in place in SPOTS;

- Update objects parameters (e.g. NE SW version, Trunk Group destination, Signalling Link symbolic name).

• Network object filtering (e.g. by region), grouping (e.g. all trunks for same destination) and

searching (e.g. by symbolic name).

• Generation of reports with PM and CM data correlation (e.g. report with trunk group

characteristics – name/symbolic name, type, direction, region, destination – together with

PM counters).


1.4.2 New Online Monitoring feature (available with RT module):

The Online monitoring feature is for monitoring PM data in “near-real” time and it represents an

enhancement of SPOTS RT and provide a more intuitive and user-friendly Graphical User

Interface for the accomplishment of the two use-cases identified as the “Online Monitoring” feature

drivers: monitoring of expected events and monitoring of unexpected events.

Combined display of PM alarms and relevant PM KPIs in one unique monitoring window, user can

define their own relevant KPIs for quicker PM alarm troubleshooting and create their own

templates for alarm troubleshooting.

Multiple Graphics can be displayed simultaneously or multiple panels

1.4.3 Unified SPOTS GUI

The existing PMC (Performance Management Client), RTC (Real-Time Client) and the new Online

Monitor Window was merged in a new unified GUI. The RTC is integrated in the SPOTS PMC by

means of screen-level integration, providing a Menu Button to start the RTC as an external

application and the new Online Monitoring window as an internal frame window like any other

report window launched from the SPOTS PMC Task Tree.

1.4.4 New OSS/J QoS API

This feature allows importing the PM data using the OSS/J QoS API. With this feature, the SPOTS

application is able to import PM data from any EMS or NMS system with an OSS/J QoS API, even

from non Siemens equipment.

1.4.5 Support to NetViewer 7.0

SPOTS V12 is integrated with NetViewer 7.0, the Siemens Microwave Element Manager, via

OSS/J QoS and inventory API (as recommended by TeleManagement forum)


2 Product features positioning SPOTS V12 supports the GSM, GPRS and UMTS core and Radio Access Networks.

SPOTS V12 is prepared to handle the Siemens product lines on these domains, as described

below1:

Radio Access Network

The access network comprises of two sub-domains.

• GERAN

Handles the circuit switched services provided by the network nodes (BSCs).

Supported releases in SPOTS V12 are: BR8.0, BR7.0, BR6.0, BR 5.5 and BR 5.0.

UMTS Terrestrial Radio Access Network (UTRAN) on the access part of the UMTS

network, Siemens provides a complete UMTS solution, comprising RNC and NodeB

elements. SPOTS V12 is designed to handle the UMR 2.0, UMR 2.5, UMR 2.7, UMR 3.0,

UMR 4.0 and UMR5.0 releases of these NEs.

The element managers for the Radio Access network, Radio Commander and OMC-B, are

responsible for collecting the PM files produced by the individual NEs.


Mobile Core Network

The Mobile Core Network comprises two sub domains:

Circuit Switched (CS)

Handles the circuit switched services provided by the network. Example: voice calls, WAP

access, etc.

It comprises the functional units MSC/VLR, HLR/AC. These can be located in the same

platform or installed in dedicated platforms. It also includes the HLRI

Supported releases in SPOTS V12 are: CS 3.0, CS 2.1, CS 2.0, SR12, SR11, SR10, and

NG-HLR3.0, HLRi2.0, HLRi1.1, HLRi1.1SP, UCR4.0 and NG-HLR3.0.

Packet Switched (PS)

PS is the core network part responsible for the packet-oriented services, with no permanent

circuit allocation. PS is nothing else than a normal GPRS network. It may perform “normal”

GPRS functions on a 2nd generation GSM mobile network, or carry the packet traffic on

UMTS.

Examples of services carried by PS are: video streaming, Web access, file transfer, etc.

PS comprises SGSN and GGSN Network Elements.

Supported releases in SPOTS V12 are: PO4.0 (GR5.0), PO3.0 (GR4.0), PO2.5 (GR3.5)

PO2.1(GR3.1), PO2.0(GR3.0) and PO1.0 (GR2.0) as well as well as, CPG-3200 GGSN

and CPG-3300 GGSN)

1 Support for other vendor equipment, is supported on a project basis.


Multi-vendor (optional)

SPOTS can be deployed also in Multi-vendor environments. This is accomplished via

Technology Plug-in modules (TPs).

The relevant Element Managers or other vendors’ equipment is integrated into SPOTS through the

TPs. In multi-vendor scenarios SPOTS can also support Core as well as Radio domains. Multi-

vendor integration is done on a per project basis.


3 Functions

3.1 Graphical User Interface

All user interaction with the SPOTS application is done through a windows based graphical user

interface.


3.2 Data Collection

SPOTS collects PM data on-line from the respective Management Systems (e.g. Radio

Commander, Switch Commander).

3.2.1 Data Collection on UTRAN

PM data files are generated periodically

in each UTRAN node (RNCs &

NodeBs). Radio Commanders collect

these files without changing its

contents. SPOTS acquires the files in

ASN1/BER format from the RCs and

before loading it into the SPOTS

database converts the format to SPF.

3.2.2 Data Collection on GERAN

PM files are generated in the BSCs and are collected by the Radio Commander, depending on

whether the NEs are BR 6.0, BR7.0 or BR 8.0. The files are collected and converted into SPF

format, before being loaded into the database.

3.2.3 Data Collection on CS and PS

The Switch Commander (SC) is responsible for the collection of PM data from the NEs in the Core

domain (CS+PS), except for the HLRi and MSP. Within the SC, PDC is the data collector module.

PDC provides as output PM files, using the SPF or “REC job files” format. The operator, in PDC,

defines the actual set of measurements being collected.

The collection mechanisms comprise passive collectors (the information is produced by the NEs)

as well as active collectors (PDC queries the NEs for the data). Depending on the format of the PM

file, it is either uploaded directly into the SPOTS database or it is first converted into SPF format

and then loaded.

PM files for the HLRi and MSP, SPOTS collects from the @commander in XML and SPF format.


3.3 Data Storage

PM data is stored in a normalised data model that supports the integrated analysis and reporting

requirements of the operator.

SPOTS uses a relational database system (Oracle). Multiple databases may be created, for large

networks, each handling part of the network (e.g.: geographical regions), in a transparent way for

the users. The database structure and access methods are optimised to speed up the processing

of several GB (Gigabyte) of PM data.

SPOTS distinguishes between two types of data, namely detailed and historical data. Network

Operation for in-depth performance and problem analysis typically uses detailed data. The user

can specify how long the detailed data is to be kept in the database.

From the detailed data, SPOTS derives historical data for storage over long periods of time. This

way, the user can analyse long-term trends at any time.

SQL

Views

Detailed Data History Data

Parser / LoaderSPOTS

As an option, SPOTS offers interfaces to allow the integration in customer-specific environments.

Using SQL views, any application can retrieve PM data from the database.


4 Supported Traffic Measurements

SPOTS supports all traffic measurements generated by the network elements in the supported

releases.

The following is a non-exhaustive list of groups of traffic measurements that SPOTS version V12

supports. .A Comprehensive list of all supported measurements is available as part of the

product user documentation.

SSS Traffic Measurements

• MSC measurements

• Supplementary Services measurements

• Cell-related traffic measurements

• Traffic-structure measurements for HO

• IWE traffic measurements

• VLR traffic measurements

• LAC traffic measurements

• HLR traffic measurements

• AC traffic measurements

• EIR traffic measurements

• Conventional SSS traffic measurements

• MP load measurements

• SS7- specific traffic measurements

GPRS/UMTS core Traffic Measurements

• SGSN Measurement

• GGSN Measurement

BSS Measurement groups

• BSC Measurements (data from BSC)

• BTS Measurements (data from BSC)

• BTS Measurements (data from BTSE)

• BTS incoming handovers

• BTSM measurements

• BTS outgoing handovers to internal cells

• BTS outgoing handovers to neighbour cells

• Air interface channels measurements

• Correlated TRX measurements

• GPRS related measurements

• SS7links related measurements

• TRX Measurements

UTRAN Measurements

• RNC Processor Measurement

• NodeB Measurement

• RNC Cell Measurement

• NodeB Cell Measurement

• RNC Anchor Cell Measurement


5 Report Generation SPOTS offers extensive and flexible performance reports, that are designed for immediate use at

Network Operation, Planning and Management level and range from interactive analysis to the

automatic generation of routine performance reports.

In SPOTS V12 there are three types of reports: Ad-hoc reports, Online Monitoring reports and

Predefined reports.

In terms of refresh SPOTS has the following behaviour:

• Ad-hoc with refresh: using the new MRS (Monitoring Report Service) service

• Ad-hoc without refresh: the current services will continue to be used

• Online Monitoring always with refresh: using the new MRS service

• Predefined reports with refresh: the current polling mechanism will continue to be used

• Predefined reports without refresh: the current services will continue to be used

5.1 Pre-defined Reports

SPOTS pre-defined Performance Reports reflect Siemens’ long experience in traffic analysis,

system and network engineering. They are designed for instant and effective use of SPOTS and

meet the most common needs of the network operator.

SPOTS pre-defined reports are available for Core Network, GERAN and UTRAN performance

analysis. Core Network comprises both the packet switched and the circuit switched technologies.

All the operator has to do is choosing the desired pre-defined report and following the instructions

of the Report Definition Wizard, selecting the input parameters, such as object instances, filter,

reference values, time window and output format. Reports can run on demand or automatically by

time schedule. The results are delivered to the requested destinations.


The operator can customize these reports to match his particular needs. A customised pre-defined

report can also be stored as a new report for later re-use. This way the user can build up a

complete report library adapted to his needs.

The following sections describe the SPOTS predefined reports that are available in V12.

5.1.1 Pre-Defined Reports for PU load

Core Network

MP Load Report Reports the load of the node's main processors sorted by date/time and

Exchange name. They are:

MP Load– Top 10 Monthly Reports

MP Load (Total) – Top 10 Monthly Report MP Load (SLT) – Top 10 Monthly Report MP Load (SM) – Top 10 Monthly Report MP Load (NM) – Top 10 Monthly Report MP Load (SA) – Top 10 Monthly Report MP Load (STATS) – Top 10 Monthly Report

MP Load–SPBH reports

MP Load SPBH Max Peak MP Load SPBH Daily Peaks MP Load (Total, PRH, OAM, NM, Base and CallP) per MP MP Load (Total, PRH, OAM and NM) per MP

MP Load-DTOT reports

MP Load (Total, PRH, OAM, NM, Base and CallP) per MP

MP Load- Time Evolution reports

MP Load (Total, PRH, OAM, NM, Base and CallP) per MP MP Load TEVL

The following monitoring panels were added to this version

MP Load Monitoring Panel LinkLoad Monitoring Panel

CP Load Report The performance of an exchange is significantly determined by the computer

capacity of the central computer. The report provides information about the

load situation of all processors at the switching centre and alerts for overload

situations.

CP Load TEVL


CP Load SPBH Max Peak

CP Load SPBH Daily Peaks

Radio Access Network

BSC Load Report The purpose of this report is to evaluate the BSC processors load evolution

throughout the time.

RNC Processor Load Report

This report provides the Peak Hour evolution of the RNC total load and call

processing load for a specified period of time.

The report is presented in chart format.

Node B Load Report

Peak Hour evolution of the Node B Load for a specified period of time.

The following indicators are presented in a chart format: Call Processing Usage

Ratio, Base Band Usage Ratio and Rest of Call Capacity.

5.1.2 Pre-Defined Reports for SS7 Surveillance

CCNC Platforms

CCNC SS7 Switch surveillance report

This report is based on data relative to MSUs. It provides per exchange the

number of MSUs handled, number of MSUs discarded and discard rate.

CCNC SS7 Route set Surveillance report

This report provides data relative to Route Set failures.

CCNC SS7 Link Set Surveillance report

This report is based on data referent to unavailability of link sets. A link set is

considered to be unavailable when the last link in the set goes into state

"inactive".


CCNC SS7 Link Surveillance Report

This report presents some of the most important signalling link statistics. It

provides a first overview of the link performance.

CCNC SS7 Link Load Report

Report the load of the CCS7 links at the peak hour or for all granularity periods,

assuming 64kbit/s links. This report provides the fundamental performance

indicators for SS7 link dimensioning.

The PBH is evaluated based on TotalLoad.

SSNC Platforms

SSNC SS7 Node Surveillance Report

This report is based on data relative to MSUs. It provides per exchange the

number of MSUs handled, number of MSUs discarded and discard rate.

SSNC SS7 Sign Point Surveillance Report

This report provides performance data related to SS7 signalling points

concerning inaccessibility of adjacent points and number of discarded MSUs.

SSNC SS7 Route Set Surveillance report

This report provides data relative to Route Set failures.

SSNC SS7 Link Set Surveillance Report

This report concerns indicators referent to unavailability of link sets.

Furthermore, it provides also per link set, other indicators related with the links

load. A link set is considered to be unavailable when the last link in the set

goes into state "inactive".

The SUM operation should be done over all signalling Links belonging to the

same link set.

SSNC SS7 Link Surveillance Report

This report provides performance indicators concerning the SS7 links load.


5.1.3 Pre-Defined Reports for Core Network (Circuit Switch Domain, CN-CS)

TGRP Load Report

Reports the load of the Trunk Groups providing useful information both for

dimensioning and for troubleshooting. Basic indicators like Mean Holding

Times, Answer Seizure Ratios, Traffic offered and Loss are provided in this

report.

TGRP Load Type Report

Reports the incoming and outgoing load of the Trunk Group for the PBH, within

the evaluation period. They include (per Trunk Group):

• Mean Holding Times

• Answer Seizure Ratios

• Traffic Carried

• Traffic blocking

“Exception marks” identify the Trunk Groups for which the Traffic Loss or the

Mean Occupation Time is higher than the specified values.

Destination Report

This report provides information about the load situation for each route (Origin

→ Destination) including the supervised exchange. The traffic without

originating point code can also be measured independent from how the

connection is switched through the network.

It also provides the number of occurrences for each possible call fail cause.

Call failure causes are separated in two groups, Calls Carried Successfully

(CCS) and Calls Carried Unsuccessfully (CCU), with the purpose of distinguish

between failures in the own and in the subsequent exchange.

Flow Report Reports the load per pair Destination Directory Number – originating Code. The

report provides basic indicators like Mean Holding Times, Calls carried and

unsuccessful calls.

PBX Load Report SPOTS pre-defined PBX-Report is based on historical data. The request can

be made for a single network element or for all network elements ('*').


Filtering conditions are available for Load value of Traffic Intensity per PBX

circuit.

Threshold values can be defined for the Mean Holding Time, Answer-Seizure

Ratio and Portability of Loss parameters. A PBX is highlighted, when the

minimum or maximum threshold values are not reached.

PBX Service Load Report

Reports the load per PBX service. The report provides basic indicators such as

Mean Holding Times, Answer Seizure Ratio, Calls carried and Traffic carried.

Thresholds can be defined like in the PBX Load Report

MSC Grade of Service Report

The MSC Grade of Service Report provides a general overview of the MSC

performance. This includes information on originating calls, terminated calls,

paging, handover, location update, short message service, CP load and

reasons for unsuccessful calls.

VLR Load Analysis Report

The VLR Load Report provides information about average subscriber

behaviour in terms of Traffic Volume produced and procedures performed

(namely Handovers, Location updates, Busy Hour call attempts etc.) It enables

the creation of a precise traffic model based on valuables obtained from real

data. It also informs about the authentication procedure success rate and the

number of subscribers currently in the VLR.

Mobile Originating Calls Analysis Report

The MOC Analysis Report provides a detailed analysis of the Mobile

Originating Calls providing statistics of indicators like Average Duration, the

Answer Seizure Ratio and the Percentage of Terminations due to No-answer

or Busy detection.

UMTS Mobile Originating Calls Analysis Report

This report provides basic information about the UMTS Circuit Switched Mobile

Originating Calls on the UMSC. Examples of this information are the average

duration, the Answer Seizure Ratio and the percentage of terminations due to

No-answer or Busy destination.

The information provided here is similar to the one provided by the "Mobile


Originating Calls Analysis" report, the main difference is that the indicators on

this report are referred only to UMTS calls and the other report aims all types of

calls, both GSM and UMTS.

Mobile Terminating Calls Analysis Report

The MTC Analysis Report provides a detailed analysis of the Mobile

Terminating Calls providing statistics of indicators like Average Duration, the

Answer Seizure Ratio and the Percentage of Terminations due to No-answer

or Busy detection. It also shows statistics related with the completion of the

paging procedure.

UMTS Mobile Terminating Calls Analysis Report

This report provides basic information about the UMTS Circuit Switched Mobile

Terminating Calls. Examples of this information are the average duration, the

Answer Seizure Ratio and the percentage of terminations due to No-answer or

Busy destination.

The information provided here is similar to the one provided by the "Mobile

Terminating Calls Analysis Report", the main difference is that the indicators on

this report are referred only to UMTS calls and the other report aims all types of

calls, both GSM and UMTS.

Handover Analysis Report

This report details the causes of handovers and the success rates for several

different types of Handovers – depending on the network elements involved in

the procedure.


UMTS Handover Analysis Report

This report details the causes of handovers and the success rates for several

different types of UMTS handover (the type of handover depends on the

network elements involved in the procedure).

The information provided here is similar to the one provided by the "Handover

Analysis Report", the main difference is that the indicators on this report are

referred only to Handovers performed on UMTS calls and the other report aims

handovers performed on all types of calls, both GSM and UMTS.

Location Update Analysis Report

This report provides the success rate of the Location Update procedure, it

details this value for inter and intra VLR, and provides the proportions of both

types of LUP related to the total of LUP procedures performed. It also provides

the frequency of IMSI attaches performed together with Location Updates.

SMS Analysis Report

This report gives a detailed analysis of the Short Messages sent or received by

the MSC.

Data and Fax Analysis report

This report provides information about fax and data success rates. Examples

are:

- Fax Call Attempts

- Fax Ratio

- Fax Answer Rate

- Data Call Attempts

- Data Ratio

- Data Answer Rate

- #7 MOC PSTN Success Rates

- #7 MTC Success Rates

- #7 MOC PLMN Success Rates

MSC Call Flow Report

This report aims to support the Operation/Planning of the SSS Network. It

provides general information about the load situation at a mobile switching

centre. It gives an overview of the traffic flow in the MSC distinguishing


between different types of traffic. The type of traffic depends on the origin and

destination of the related calls.

MSC Handover Flow Report

This report gives information of the Handovers performed and attempted by the

MSC per origin cell.

The information provided concerns the number of handover attempted by each

origin cell per target cell and the relative proportion of those handovers

compared with the total number of attempts by the origin cell expressed in a

grey scale.

This report can be useful to obtain an overview of the traffic flow between Cells

or BSCs, and the success rates per target Cell.

5.1.4 Pre-Defined Reports for Core Network (Packet Switched Domain, CN-PS)

General CN-PS report features

The reports provide detailed information that allows the performance

evaluation of interfaces, load and protocol procedures. They also provide

statistics to enable an improvement of the traffic models used.

Most of the evaluations are based on historical data where the results are performed for the PBH (Peak Busy Hour) of the evaluation period or for the daily values (i.e. total for each day of the evaluation period).

ATM SP on xGSN

GTP Throughput Report

This report provides information regarding the number of packets and

throughput transmitted via GTP (GPRS Tunnelling Protocol) per

SP:GTP on any type of GSN, to help determine the efficiency of the

network


ATM MP on SGSN

SGSN Uplink MP load report

For GPRS the report provides detailed information regarding the overload

handling on the LLC layer. The results include the number of rejected PDP

context activations due to overload control (only for PO2.0 on), the number of

discarded packets due to overload control, and, transmission rates for LLC

and SNDCP packets.

The SNDCP packets transmitted represent the chargeable service provided to

the subscribers. The SNDCP packets are transmitted uplink to the service

access point defined by the PDP context received.

LLC frames are transparent to the BSS and they transmit to the peer layer in

the MS the user data compressed received from the SNDCP layer SAP along

with signalling data for GMM functions. LLC frames have variable numbers of

bytes and their transmission rates represent the efficiency in the use of the

radio interface.

SGSN downlink MP load report

The purpose of this report is equal to the previous except it analysis the load

on the downlink direction per SGSN.

SGSN License violations report

This report monitors violation of the parameters of the SGSN licenses, namely

number of attached subscribers, number of attached camel subscribers,

number of simultaneous sessions and throughput. Warnings related with these

license violations are also provided via QoS Alarms on the SGSN. For GPRS it

provides information on user data throughput in each direction (uplink and

downlink).

SGSN Session analysis report

The report provides detailed analysis of the session handling per SGSN. It

supplies statistics regarding session activation, update, modification, average

duration, etc. Separated indicators depending on session priority are provided

for equipment versions greater than GR2.0.

SGSN Provided by this report is a general overview of the SGSN performance. This


Performance analysis report

includes information on: number of subscribers in SGSN area, average

number of sessions, short message service, routing area updates and attach

and detach success rates. For GPRS it also provides information regarding

average throughput, number of Kbytes per session along with paging success

rate.

SGSN Nominal load report

This report will be very useful because many details related to subscriber

behaviour are yet poorly known. The development and the optimisation of the

network are dependent of a realistic traffic model.

This report will provide a set of statistic results to be compared with the node

specifications. The information included is related to both number of

subscribers and the processes run by the Node such as attach, detach, routing

area updates, paging, activation and deactivation. Furthermore for GPRS the

report will supply information regarding the amount of handled packages and

user data throughput in both directions.


5.1.5 Pre-Defined Reports for Radio Access Network (GERAN Domain)

Base Station Overview Report

This report aims to provide overview information about the load situation and

success rates of basic protocol procedures of the GSM Cells both for TCH and

for SDCCH channels.

Basic problems related to load can be immediately detected as well as

indications leading to other more complex problems that need further

proceedings; examples of these problems are interference and bad coverage.

Additional handover information can also be provided by adding the handover

information from the "Base Station Handover Analysis Report" to this report,.

This will give more details about any problems affecting the performance of the

network.

Base Station Ranking Report

The purpose of this report is to evaluate and compare cell performances using

a unique indicator: "Quality Index". This indicator aggregates the key

performance indicators that give information about the resource usage and

about the subscriber perception related to the quality of a network.

Base Station Grade Of Service Report

This report provides detailed information about the load situation of the GSM

Cells both for TCH and for SDCCH channels. In addition it provides important

results for channel resource optimisation like the number of defined SDCCH

channels, SDCCH traffic carried, the number of defined TCH channels and the

TCH traffic carried. It also presents several calculations using traffic theory

formulas both for Waiting systems (Erlang C formula) and for Loss systems

(Erlang B formula).

Base Station Call Set-up Analysis Report

The purpose of this report is to detect GSM Cells with problems in the call set-

up procedure. By analysing the indicators "Number of Call Setup Attempts",

"Call Setup Success Rate", "Number Of Call Setup Failures" and "Percentage

of Call Setup Failure Rate due to SSS Procedure Failure" it provides detailed

information about reasons for call setup failure.


Base Station Traffic Flow Report

This report provides the number of calls and the number of intracell handovers

between different cell areas (if extended or concentric cells), the number of

internal intercell handovers and the number of external intercell handovers.

Base Station Handover Overview Report

The purpose of this report is to detect GSM Cells with problems in the

Handover procedure. Separated Performance Indicators for each handover

type are presented (i.e. Intra Cell HO, Outgoing Internal HO, Outgoing External

HO, Outgoing SDCCH HO, Incoming Internal HO, Incoming External HO).

It also allows to detect missing neighbourhood relationships by analysing the

indicator "Inter Cell Handover indication Success Rate"

Base Station Handover Analysis Report

This report provides the number of HOs per cause and some important

performance indicators to correlate with the HO information. This simple

information table should be enough for an optimiser with reasonable

background knowledge to detect many problems affecting the network

performance. For instance, he will be able to identify cells which have: an

unusual high number of handover attempts; cells with high number of quality

handover attempts due to interference problems, cells with a high number of

dropped calls due to HO drops, unbalanced links, etc.

Base Station Outgoing Handover Report

The purpose of this report is to monitor the handover success rate between

Origin- and Target Cell. Furthermore, this report help to identify Origin/Target

cell pairs with unusual behaviour such as:

• No handover attempts between neighbour cells

• High number of handover attempts indicating overlapping of cell

coverage areas with subsequent ping-pong handovers.

• High number of handover attempts between two neighbours, but zero

successful handover

• High number of handover attempts between two neighbours, but low

handover success rate

• Target cells, for which it is in general difficult to make an handover into


Out of this report, a top-ten list can be produced for those Origin/Target cell

pairs that have a very high difference between attempted HO and successful

HO. For each pair the distribution between handover causes is also analysed.

Unbalanced Links Report

The purpose of this report is to detect GSM Cells with unbalanced links

between uplink and downlink direction and identify the level difference between

them. Unbalanced links might result in degraded network performance.

Base Station GPRS Performance Report

The purpose of this report is to evaluate the performance of GPRS connections

on GSM Cells. It provides indicators that enable the identification of problems

related to channel capacity.

Base Station Interference Band Report

This report provides the percentage of idle TCH in each interference band

calculated from the total number of idle TCHs (it uses the Interference Band

Rate on Idle TCH key performance indicator). The results are produced per

cell.

BSC Load Report The purpose of this report is to evaluate the BSC processors load evolution

throughout the time.

Base Station Interference Report

This report provides the percentage of idle TCH in each interference band

calculated from the total number of idle TCHs (it uses the Interference Band

Rate on Idle TCH key performance indicator). The results are produced per

cell.

TRX Level and Quality Report

The report provides the mean RXLEV and RXQUAL on busy TCH. Both for

uplink and downlink.

It also provides the Level Band for which 10% of the measurements on busy

channels registered a RXLEV in a lower Level Band. This information is directly


related with the coverage probability because it can be stated that 90%

coverage probability was achieved (usual goal of network planning) if the result

Level Band was found greater or equal to the Level Band which includes the

defined minimum acceptable RXLEV.

Furthermore, the report also provides the Quality Band for which 90% of the

measurements on busy channels registered a RXQUAL in a lower Quality

Band. Two indicators distinguish between uplink and downlink.

Base Station Link Quality Report

This report provides some of the most important performance indicators to

enable the detection of interference and subsequent bad call quality problems.

Correlated Data Histogram Reports

Certain BR6.0 measurements, namely CRXLVQUU, CRXLVQUD, CRXLVTAU,

CRXLVTAD and CFERRXQU require a specific type of report layout to enable

a graphical, user-friendly, use-case oriented, presentation of the histograms

provided.

All these reports have exactly the same structure which corresponds to an 8x8

matrix with the following results:

CorrRxLevRxQualUL report provides all 64 counters from CRXLVQUU

CorrRxLevRxQualDL report provides all 64 counters from CRXLVQUD

CorrRxLevTAUL report provides all 64 counters from CRXLVTAU

CorrRxLevTADL report provides all 64 counters from CRXLVTAD

CorrFERRxQualUL report provides all 64 counters from CFERRXQU

The final goal for these reports is to present the previous information as 3D

graphics where, in the current implementation, the "zz" axis corresponds to a

grey scale for the total number of times a certain (x, y) combination pair

occurred during the evaluation period.


5.1.6 Pre-Defined Reports for Radio Access Network (UTRAN Domain)

UTRAN Overview Report

This report provides information like Call Setup Success Rates, Number of Call

Attempts and Mean Call Duration per QoS class. Or like general quality

indicators for Hard and Soft Handovers and, moreover the connection drop

rate.

The report results can be provided on a per cell basis.

Connection Drop per Cause Report

The purpose of this report is to provide the list of reasons for connection drops.

The report should be presented as pie chart - one per cell or per RNC - to

enable the analysis of the relative weight of each cause. Please note that the

actual percentage value for each cause is displayed in SPOTS interface.

Additionally, to simplify the chart analysis by removing unnecessary

information, all causes with zero occurrences should be filtered on the report.

RRC Analysis Report

This report provides RRC related information in a per cell basis.

The information concerns the number of RRC connection establishment

attempts, respective success rate and ratio to radio link failures. Besides it also

details the reasons for radio link failures namely: synchronisation failure, call

processing overload, hardware failure, etc.

RRC Establishment per Cause Report

The purpose of this report is to provide the list of reasons for the Call

Establishment Procedure. The report should be presented as pie chart - one

per cell or per RNC - to enable the analysis of the relative weight of each

cause. Please note that the actual percentage value for each cause is

displayed in SPOTS interface. Additionally, to simplify the chart analysis by

removing unnecessary information, all causes with zero occurrences should be

filtered on the report.


RAB Analysis Report

This report provides for each cell the number of RAB establishment attempts,

success rate, failure rate and failure number per cause. Separation is done

between QoS classes, Packet Switched and Circuit Switched traffic to obtain

different RAB establishment success rates.

RAB Failure per Cause Report

The purpose of this report is to provide the list of reasons for RAB failure. The

report should be presented as pie chart - one per cell or per RNC - to enable

the analysis of the relative weight of each cause. Please note that the actual

percentage value for each cause is displayed in SPOTS interface. Additionally,

to simplify the chart analysis by removing unnecessary information, all causes

with zero occurrences should be filtered on the report.

Soft HO Analysis Report

It provides the number and success rates for either intra Node B and inter

Node B branch additions.

Branch Addition Failure per Cause

The purpose of this report is to provide the list of reasons for RAB failure. The

report should be presented as pie chart - one per cell or per RNC - to enable

the analysis of the relative weight of each cause. Please note that the actual

percentage value for each cause is displayed in SPOTS interface.

Hard HO Analysis Report

The purpose of the report is to provide numbers and success rates for outgoing

Hard Handovers and causes.


5.2 Ad-hoc Report Generator

The integrated Ad-hoc report generator allows rapid deployment of new reports.

This feature is easy to operate and does not require specific expertise in database or programming

language.

The report generator includes the following features:

• Expression wizard to define the performance analysis task

• Standard traffic analysis functions according to ITU-T Rec. E.500 series, such as peak busy

hour and daily totals

• Powerful tool set for designing the graphical presentation (charts, tables, header, legend,

colours, borders, shading, etc.)

• Zooming into graphs to move from the overview to the details

• Office integration (e.g. Excel)

• Automation of report generation

• Automatic refreshing of reports mode

• Ad-hoc reports may be stored for further use

Examples:


5.3 SPOTS Reporting Language (SRL)

The pre-defined reports and the ad-hoc report generator handle the majority of report analysis of

the network. If it is necessary to extend the functionality of these reports (e.g. customisation for a

particular case), this can be done using the SPOTS Reporting Language. This language is flexible

and powerful to describe any complex report.

The offered reports (ad-hoc, pre-defined) make use of SRL to access the data in a transparent

way. Thus it is possible by customisation to create specific sets of reports in addition to the ones

already offered by SPOTS.

For reports, two types are possible:

• Public: they are available to all users that are connected to the SPOTS Application Server where the report is created

• Private: they remain reserved to the user who has created them.


Within the report editor, three steps are necessary in order to succesfully create a new report.

First the report source code must be created and saved. Secondly the report is compiled and lastly

the report is published in the SPOTS Application Server for future use.


6 SPOTS Optional Modules SPOTS Product Family is composed by SPOTS Long-Term, as mandatory module, and the 4

optional modules. In this document we will present a small description of each of the modules. A

more detailed description can be found on the documents listed in chapter 10 of this document.

6.1 SPOTS Real Time Module

It is a clear today that one of the operator’s main requirements is to be able to access and analyze

Performance Management data on a quick and reliable way. In the light of online monitoring

needs, PM data has to be provided by all system components in a faster time frame than before.

SPOTS Real Time Module provides reporting updates of the network performance data. The

continuous reporting is done on a near-real time basis, with data updates every 5/15 minutes

(depending on the NE settings) allowing continuous online monitoring of the network.

Benefits:

• Be proactive and win up to 24 hours in solving PM problems

• Set-up pro-active QoS thresholds, to react before PM problems become fault conditions

• Continuous QoS monitoring of your key network indicators

• Get your priorities by using differentiated classes of thresholds (e.g.: Gold, Silver…)


SPOTS RT provides an excellent answer to the use cases identified for Online Monitoring:

• monitoring of expected events, and • monitoring of unexpected events

This is achieved by the optimization of the PM data path inside the SPOTS application and by

providing more intuitive and user-friendly panels in the SPOTS GUI, specifically designed for this

purpose.


6.2 SNMP Alarm forwarding module

SPOTS performance alarms can be forwarded via SNMP interface to fault management or

graphical information systems (e.g. HP´s OV TeMIP or Micromuse Netcool) for integrated

fault management.

This allows a seamless integration in the

fault management process. The

performance alarms will be handled in the

Fault Management application (e.g. notified

via Map topology or Alarm browser).

6.3 Off-the-shelf HP OV TeMIP integration

HP has an off-the-shelf access module available for SPOTS. Performance Alarms generated

by SPOTS shall be forwarded to the TeMIP Fault Management application and processed

there exactly as any other alarm coming directly from the network. This is done by forwarding

the SPOTS QoS alarms via SNMP interface to

HP TeMIP AM Solution Set.

In addition, Desktop integration of SPOTS into

the TeMIP Iconic Map PM has shown in the

figure below can further be done on a project

basis, allowing direct call of SPOTS reports from

TeMIP Iconic Map window through entry Window

“SPOTS Report

SPOTS

FM

Alarm notification (SNMP TRAP)

Alarm synchronisation (SNMP GET)

Alarm Trap filter (SNMP SET)

Delete perf. alarm (SNMP SET)


6.4 SPOTS Web Reports module

SPOTS Web Reports module provides the

customer with the Web reporting functionality

for all supported Network Elements.

SPOTS Web Reports is an optional module

in SPOTS Framework, which enables web

access to the SPOTS functionality. It

complements the traditional SPOTS

reporting solution, providing access to

predefined performance reports and allowing

the user to create his own performance

reports view Web environment.

SPOTS Web Reports is suitable for all type of users (novice to advanced users), provides a

comprehensive range of high-value report types and enables the interactive report customisation

(users can create new reports simply by dragging and dropping the report objects into a window). It

also provides dynamic and multi-object reports (conditional report layout to adapt dynamically to

the data and end-user requirements and multiple queries to different databases). SPOTS Web

Reports enables to deliver the report content in more than one language (e.g. English, French,

Chinese) and can work with exiting

web portals.

SPOTS Web Reports provides a web

portal, from where all the functionality

can be accessed just by clicking in the

web browser. The web portal can

cover all the PM reporting needs

across the operator organization.


Benefits:

• Centralized reporting, organization-wide accessibility:

- Zero footprint: Access from any office PC

• Reduce IT costs:

- No integration efforts are required enabling kick start of operations

- Intuitive access to novice users with drag-and-drop simplicity

- No need for programming skills, advanced features for power-users to create easily

most complex reports

• Meet all reporting needs across the organization :

- Take advantage of all SPOTS powerful KPI´s and predefined reports

- Dynamic filtering and easy drill-down functions

• Off-the-shelf integrated SPOTS portal solution


6.5 Backup and Restore - BAR

With PM data growing in volume and the frequency of data collection increasing, SPOTS

database(s) should not be closed for backup, as this will disrupt the normal operation too much.

SPOTS BAR solves this problem by making incremental and complete system back-ups. By

reconfiguring SPOTS database(s) putting it in archive log mode of operation it is possible to

perform SPOTS database(s) backups in on-line mode, thus not interrupting the normal SPOTS

application operation.

SPOTS BAR solution involves two types of data protection:

• File system backup; and

• Database(s) backup.

The BAR solution produces a full system Back-up of the OSS and system application periodically,

once a week as default.

The database is backed-up incrementally and a full Back-up is achieved periodically, once a week

as default, through synchronization points.


6.6 SPOTS Multi-vendor common 3GPP support:

SPOTS plug-in architecture supports fast deployment of multi-vendor solutions. Besides major cost

savings associated with having only one system such as, reduced maintenance costs, fewer 3rd

party SW licenses, one unique tool, and less training, the operator gain a single unique view of the

network performance covering all vendors. Based on the 3GPP standards, we provide a future

proof solution and consistent reporting across vendors, reducing KPI complexity for the operator.

Benefits:

• Cut Performance Management Invest by at least 50%

• Multi-technology, multi-vendor

• Maximum scalability due to advanced architecture

• Less training needed for your staff


7 Architecture The open system architecture supports the deployment of multi-technology and multi-vendor

solutions.

This architecture is based on a plug-in concept, which enables rapid deployment of new

functionality (i.e. new equipment/reports/features) by "plugging-in" these new modules to the core

package.

To offer a highly scalable solution addressing small and very large Networks, SPOTS is defined as

a multi-tiered architecture. The client Java application is available for Solaris, Windows NT or

Windows 2000, which means it can run on any desktop notebook or workstation, allowing local and

remote access and desktop integration.

The middle tier includes business logic, and the lower tier consists of the database server, which

uses Oracle as the standard relational database.

All entities communicate internally via a common CORBA bus.


7.1 High Availability

As the SPOTS tool becomes more and more critical for the operators, the application needs to

meet high availability requirements; this means to provide increased uptime and make the

application as resilient as possible against failures.

Several measures have been implemented in the configuration of SPOTS V12.

• SPOTS backup scripting that enable the configuration of automatic backup process for

small SPOTS configuration

• Usage of Disk Suite with total/partial disks mirroring for medium and/or large SPOTS

configurations

• Efficient backup and restore procedures – based on the SPOTS BAR solution.

7.2 Domain Management

For large Networks, SPOTS simplifies network analysis by using the domain concept.

The network can be divided into several domains (e.g. regions), which can be analysed separately

or, if desired, correlated across different domains. This segmentation is transparent to the users,

because the object naming system is sufficient for SPOTS to know where and how to access them.

North-East

North-West

South


When working with a single domain, only the information related to the objects assigned to the

domain will be displayed. This makes analysis much easier and less prone to errors in the

definition of reports and Virtual Counters.

7.3 User administration - Session control and roaming profiles

SPOTS users are required to login to the network. This authentication opens a session with a

specific set of privileges associated with the user profile (e.g. according to their responsibility tasks

in O&M). They may be allowed to edit NE definitions, schedule reports, or just simply run reports.

Also the user profile supports the domain concept, specifying which domains the user has

privileges to access.

The roaming profile is available from any SPOTS client.

In this way, SPOTS allows users to respond more efficiently, since they can now work directly with

SPOTS from any location with their own access profile.


8 Open interfaces SPOTS supports several open standard interfaces, enabling the easy integration in umbrella

network management systems or other external systems.

CORBA

Corba methods allow the following dialog function:

– Execution of performance analysis reporting

Invocation is possible in a synchronous dialog mode, with a response that complies with the return

type of the method (e.g. executed, not executed). Potential errors are returned using appropriate

exceptions, which are handled by the external operating system.

SQL

For integration in eg. Data warehousing solutions, PM data in the SPOTS Oracle DB can be

accessed via SQL views.

CLI

Several of the most relevant functions within the SPOTS application can be initiated via CLI, eg.

Execution of reports, Mkhistory, BackupDB,

SNMP

The SNMP interface supported by SPOTS is used for the forwarding of alarms to an external fault

management application. Please see chapter 6.2, for more information.

Office Applications

The output format of the SPOTS reports can be xls, PDF, text file, or comma separated allowing for easy import in any office application.


9 Abbreviations ATM Asynchronous Transfer Mode

CLI Command Line Interface CORBA Common Object Request Broker Application CS Circuit Switched GB Gigabyte GERAN GSM Edge Radio Access Network GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GR GPRS Release GTP GPRS Tunnelling Protocol HO Handover KPI Key Performance Indicator MRS Monitoring Report Service NE Network Element O&M Operation and Maintenance OSS Operation Support System PBH Peak Busy Hour PO Packet Oriented PS Packet Switched PDC Performance Data Collector RAB Radio Access Bearer RC Radio Commander RNC Radio Network Controller RRC Radio Resource Control SC Switch Commander SDCCH Stand alone Dedicated Control Channel SGSN Serving GPRS Support Node SP Service Pack SPF Siemens Performance Format SPOTS Support for Planning, Operation & Maintenance by Traffic

Analysis System SQL Structured Query Language STP Stand-alone Signal Transfer Point TCH Traffic Channel TCP/IP Transmission Control Protocol – Internet Protocol (RFC 793) TGRP Trunk group TMN Telecommunications Management Network TP Technology Plug-in TRX Transceiver UCR UMTS Equipment Release (Core) UMR UMTS Equipment Release (Radio) UMTS Universal Mobile Telecommunication System UTRAN UMTS Terrestrial Radio Access Network VLR Visitor Location Registry


10 SPOTS Documentation There are several documents that describe the SPOTS modules, as showed bellow:

Document Name Document Content

SPOTS V12 SPOTS V12 product description

Real-Time Module for SPOTS V12 Description of the Real-Time module features

SNMP Alarm Forwarding Module for SPOTS V12

SNMP Alarm Agent module for alarm forwarding description

Backup & Restore for SPOTS V12 Backup & Restore module product description

Web Reports module for SPOTS V12 Web Reporting module product description

Multivendor Integration module for SPOTS V12

Multivendor module product description

All documents are available in IMS Link (Siemens internal link): https://ims.icn.siemens.de/livelink/livelink?func=ll&objId=309969809&objAction=Browse

Siemens SPOTS Performance and KPI Monitoring

Mobile

Transcript of Siemens SPOTS Performance and KPI Monitoring