GSM GSM Huawei NSS MSC V61 Product Requirements

Data Export Date: 18 Oct 2007


1. Change History


IssueDateAuthorComments
TBD   


2. Document References


Document NameDateDocument ReferenceURL
Vendor Documentation
Measurement Items Digital Mobile Switch Traffic11/02/2005Operation Manual - Performance Measurement M900/M1800 MSC/SSP/IPhttp://notesdoc/87256D28003200ED/(ADCWebOpenLinkLatestVD)?OpenAgent&ddHID=11022005-HOYV-RD5Z&LinkType=VD&Open=


3. Outstanding Issues


NumberDateDescriptionPlanned Resolution
TBD   


4. Vendor Measurement Scope

The table below lists the vendor OM groups that are in scope for this technology pack, broken down by network element, together with their corresponding tech pack KPI group.


Vendor MeasurementTech Pack KPI Group
LAC - Mapped with LUPAG.LAC_NO
LUPAGLAC.Neutral.GSM.mobility
MSC - Mapped with MSC_TRAFTYPE.NODEID
ASSPROM_AGGRMSC.Neutral.GSM.call_setup
DESTMSC.Neutral.GSM.destination
HOVMSC.Neutral.GSM.handover
LUPAG_AGGRMSC.Neutral.GSM.page
MSC_TRAFTYPEMSC.Neutral.GSM.traffic
OBSCHM_AGGRMSC.Neutral.GSM.handover
VLRTMMSC.Neutral.GSM.services
Route_IF - Mapped with NODEID & "/" & TGRP.Office_Direction_No
nc_routeRoute_IF.Neutral.GSM.transmission.forecast
nc_routeRoute_IF.Neutral.GSM.transmission
route_interface_transmission_weekRoute_IF.Neutral.GSM.transmission
TGRPRoute_IF.Neutral.GSM.transmission
Signalling_Link - Mapped with NODEID & "/" & C7LL.Module_No & "-" & Link_No
C7LLSignalling_Link.Neutral.GSM.link
Signalling_LinkSet - Mapped with NODEID & "/" & LSETM.Link_Set_No
LSETMSignalling_LinkSet.Neutral.GSM.signalling_linkset
nc_ss7_linksetSignalling_LinkSet.Neutral.GSM.forecast
nc_ss7_linksetSignalling_LinkSet.Neutral.GSM.signalling_linkset
ss7_linkset_weekSignalling_LinkSet.Neutral.GSM.signalling_linkset
Signalling_Point - Mapped with NODEID & "/" & DSPM.MTPDSP_Index
DSPMSignalling_Point.Neutral.GSM.signalling_point
VLR - Mapped with AUTHSM.NODEID
AUTHSMVLR.Neutral.GSM.mobility
LUPAG_AGGRVLR.Neutral.GSM.mobility
MSCVLR.Neutral.GSM.mobility


5. Network Model


5.1 Network Objects

This section describes the logical structure of the key performance data that will be processed by Performance Manager, in terms of network objects and their attributes.

LAC

Location/Paging Area Code; a group of cells, managed by an MSC, that a mobile station's location may be recorded against.

In the network hierarchy, the immediate parent of the LAC object is MSC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the LAC.YLUPAG.LAC_NO
Relationship Attributes
MSCThe MSC which controls this Location Area Code.YLUPAG.NODEID
RegionRegion associated with the LAC.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
NetworkNetwork associated with the LAC.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the LAC. LUPAG.LAC_NO
VendorManufacturer of the LAC. "Huawei"


MSC

The Mobile Switching Centre has circuit/voice switching functions, as well as linking several BSCs to the core network and managing some of their functions (eg inter-BSC handover). It is also connected to an SS7 network for database queries.

In the network hierarchy, the immediate parent of the MSC object is Region.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the MSC.YMSC_TRAFTYPE.NODEID
Relationship Attributes
RegionRegion associated with the MSC.YPopulated by the customer
NetworkNetwork associated with the MSC.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the MSC. MSC_TRAFTYPE.NODEID
VendorManufacturer of the MSC. "Huawei"
MSC_VersionHardware/Software version of the MSC. "V61"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
MSC_TypeType of MSC. "Switch Voice"


Processor

The Processor object represents a CPU inside another network element. Some elements have more than one Processor.

In the network hierarchy, the immediate parent of the Processor object is Region.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Processor.YNODEID & "/" & CPXX.Module_No
Relationship Attributes
RegionRegion associated with the Processor.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
NetworkNetwork associated with the Processor.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the Processor. NODEID & "/" & CPXX.Module_No
Processor_TypeType of Processor. "MSC Processor"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Node_IdThis is the identifier for the network element containing the Processor. CPXX.NODEID
Node_NameA user friendly name preferably unique for the Node. lookup("nc_msc","msc_name", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Node_TypeThe type of the network element containing the Processor. "MSC"
Processor_VersionHardware/Software version of the Processor. "V61"
VendorManufacturer of the Processor. "Huawei"


Route_IF

For each logical Route Interface, there will be 2 entries - 1 for the interface at each end, as it is the interfaces that report the data. Routes may connect switches and other nodes (including BSCs) in a circuit-switched network.

In the network hierarchy, the immediate parent of the Route_IF object is Region.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the Route IF.YNODEID & "/" & TGRP.Office_Direction_No
Relationship Attributes
RegionRegion associated with the Route IF.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
NetworkNetwork associated with the Route IF.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the Route IF. NODEID & "/" & TGRP.Office_Direction_No
Source_IdA unique identifier for the Node (Switch) at this end of the connection. NODEID
Source_TypeType of Source. "MSC"
Source_NameA user friendly name preferably unique for the Source. lookup("nc_msc", "msc_name", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Is_POIIs it a Point of Interconnection. "True"
Is_TrunkIs it a Trunk Route? "True"
Route_DirectionThere are three options - Incoming, Outgoing or BothWay. "No Mapping"
Route_TypeThe type of route. Peer_Office_Type
Target_IdA unique identifier for the Node at the other end of the connection. "No Mapping"
Source_TechnologyTechnology of the Source (e.g. GSM, GPRS, UMTS). "GSM"
Target_TechnologyTechnology of the Target (e.g. GSM, GPRS, UMTS). "No Mapping"


Signalling_LinkSet

A set of Signalling Links between two points.

In the network hierarchy, the immediate parent of the Signalling_LinkSet object is Signalling_Point.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SS7 LinkSet.YNODEID & "/" & LSETM.Link_Set_No
Relationship Attributes
SS7_PointThe SS7 Point to which this SS7 LinkSet is connected to (at this end).Y"No Mapping"
NetworkNetwork associated with the SS7 LinkSet.Y"PLMN"
RegionRegion associated with the SS7 LinkSet.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Configuration Attributes
NameA user friendly name preferably unique for the SS7 LinkSet. NODEID & "/" & LSETM.Link_Set_No
Node_IdThe Node (MSC or HLR) that this SS7 LinkSet is connected to (at this end). NODEID
Node_NameName of the node that this SS7 LinkSet is connected to (at this end). lookup("nc_msc","msc_name", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Data_RateThe total of all the individual SS7 Link speeds (aggregated over all SS7 Links in the SS7 LinkSet) in bits per second (bit/s). 64000
Designed_Link_FailuresThe number of SS7 Link failures permitted on the SS7 LinkSet while still keeping the SS7 LinkSet up to its designed capacity. "No Mapping"
Node_TypeThe type of the network element that the SS7 LinkSet is connected to (at this end). "MSC"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdThe Adjacent Node that this SS7 LinkSet is connected from (at the other end). "No Mapping"


Signalling_Link

The SS7 Signalling data link is a full-duplex, digital transmission channel, usually operating at 64 kbit/s.

In the network hierarchy, the immediate parent of the Signalling_Link object is Signalling_LinkSet.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SS7 Link.YNODEID & "/" & C7LL.Module_No & "-" & Link_No
Relationship Attributes
SS7_LinkSetThe Node (MSC or HLR) that this SS7 Link is connected to (at this end).YNODEID & "/" & C7LL.Link_Set_No
SS7_PointA unique identifier for the SS7 Point.YNODEID
RegionRegion associated with the SS7 Link.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
NetworkNetwork associated with the SS7 Link.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Link. NODEID & "/" & C7LL.Module_No & "-" Link_Name
Node_NameThe name for the network element that the SS7 Link is connected to (at this end). lookup("nc_msc","msc_name",utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Node_IdThe Node (MSC or HLR) that this SS7 Link is connected to (at this end). NODEID
Data_RateThe SS7 Link speed in bits per second (bit/s). "Populated by the customer"
Node_TypeThe type of the network element that the SS7 Link is connected to at this end. "MSC"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdThe Adjacent Node that this SS7 Link is connected from (at the other end). "No Mapping"


Signalling_Point

Represents a signalling entity that is part of a Node.

In the network hierarchy, the immediate parent of the Signalling_Point object is Region.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the SS7 Point.YNODEID & "/" & DSPM.MTPDSP_Index
Relationship Attributes
RegionRegion associated with the SS7 Point. SS7_Point - the default value is derived via the Node.Ylookup("nc_msc","region_id",utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
NetworkNetwork associated with the SS7 Point.Y"PLMN"
Configuration Attributes
NameA user friendly name preferably unique for the SS7 Point. NODEID & "/" & DSPM.MTPDSP_Index
Node_IdA unique identifier for the Node. NODEID
Node_NameA user friendly name preferably unique for the Node. lookup("nc_msc","msc_name",utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Node_TypeType of Node. "MSC"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"
Adjacent_Node_IdA unique identifier for the Adjacent Node. "No Mapping"


VLR

The Visitor Location Register is distributed, and one VLR is usually associated with each MSC. It caches a subset of the information from the HLR, for subscribers that connected locally, plus some other temporary information.

In the network hierarchy, the immediate parent of the VLR object is MSC.

Attribute NameDescriptionRead-Only?Mapping
Primary Identifier
IDA unique identifier for the VLR.YAUTHSM.NODEID
Relationship Attributes
MSCThe MSC to which the VLR belongs.YMSC.NODEID
NetworkNetwork associated with the VLR.Y"PLMN"
RegionRegion associated with the VLR.Ylookup("nc_msc","region_id", utime(START_DATE & START_TIME,"%Y-%m-%d %R"), NODEID)
Configuration Attributes
NameA user friendly name preferably unique for the VLR. AUTHSM.NODEID
VLR_VersionHardware/Software version of the VLR. "V61"
VendorManufacturer of the VLR. "Huawei"
TechnologyTechnology of the network/element (e.g. GSM, GPRS, UMTS). "GSM"


5.2 Reference Objects

This section describes the reference objects that are used only as lookups for compound-keyed raw data.

Not applicable to this tech pack.


6. Busy Hours

This section lists the busy hours which are defined for the network objects previously described.

ObjectBusy HourAcronymDefining KPI
MSCbusy_hourmbhMSC.Neutral.GSM.traffic.traffic
MSCtraffic_type_busy_hourmtbhMSC.Neutral.GSM.traffic.traffic
Route_IFbusy_hourrbhRoute_IF.Neutral.GSM.transmission.bothway_traffic
Route_IFincoming_busy_hourribhRoute_IF.Neutral.GSM.transmission.incoming_traffic
Route_IFoutgoing_busy_hourrobhRoute_IF.Neutral.GSM.transmission.outgoing_traffic
Signalling_Linkreceived_busy_hourslrbhSignalling_Link.Neutral.GSM.link.incoming_utilisation
Signalling_Linktransmitted_busy_hoursltbhSignalling_Link.Neutral.GSM.link.outgoing_utilisation
Signalling_LinkSetreceived_busy_hourslsrbhSignalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_utilisation
Signalling_LinkSettransmitted_busy_hourslstbhSignalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_utilisation
VLRbusy_hourvbhVLR.Neutral.GSM.mobility.vlr_subscribers


7. Constants


This section lists all constants that are defined in this technology pack, and which may be referenced in KPI expressions.

None.

8. Performance Indicators

This section describes the performance indicators (both one-to-one counter mappings, and complex KPIs) that are defined in this technology pack, grouped by the network object to which they relate, as follows:

Note that all KPIs will have total, average, minimum and maximum values calculated for daily, weekly, and monthly summaries. Individual groups of KPIs may have additional summary types (including busy hours) applied to them, and these are listed against the respective KPIs in the tables below.


LAC Performance Indicators

This section shows the key performance indicators and other counters for the LAC object, divided into the following sub-sections:


LAC.Neutral.GSM.mobility

The results of updates from or within a Location Area (LA)

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_vlr_update_failurePERCENTAGEFLOATPercentage of failures to update the VLR with location information about MS?s in this LApercentfail({LAC.Neutral.GSM.mobility.vlr_update_failures}, {LAC.Neutral.GSM.mobility.vlr_update_attempts})mbh
%_vlr_update_successesPERCENTAGEFLOATPercentage of successful attempts to update the VLR with location information about MS?s in this LApercentok({LAC.Neutral.GSM.mobility.vlr_update_successes}, {LAC.Neutral.GSM.mobility.vlr_update_attempts})mbh
attach_updatesACCUMULATIONINTEGERUpdates from IMSI Attach actionsLUPAG.Number_of_IMSI_Attachesmbh
la_updatesACCUMULATIONINTEGERUpdates from MS?s changing to this LACLUPAG.Number_of_Subscriber_Roaming_Location_Update_Requestsmbh
periodic_updatesACCUMULATIONINTEGERPeriodic updates mbh
vlr_update_attemptsACCUMULATIONINT8Attempts to update the VLR with location information about MS?s in this LALUPAG.Number_of_Location_Update_Requests_in_VLRmbh
vlr_update_failuresACCUMULATIONINT8Failures to update the VLR with location information about MS?s in this LA(LUPAG.Number_of_Location_Update_Requests_in_VLR)-(Number_of_Successful_Location_Updates_in_VLR)mbh
vlr_update_successesACCUMULATIONINT8Successful attempts to update the VLR with location information about MS?s in this LALUPAG.Number_of_Successful_Location_Updates_in_VLRmbh


LAC.Neutral.GSM.page

The results of paging activity within a Location Area

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_responsePERCENTAGEFLOATThe percentage of pages (first + subsequent) that received a responsepercentok({LAC.Neutral.GSM.page.responses}, {LAC.Neutral.GSM.page.total_pages})mbh
%_successPERCENTAGEFLOATThe percentage of pages (not counting repeat attempts to send the same page) that eventually received a response (possibly after re-paging)percentok({LAC.Neutral.GSM.page.responses}, {LAC.Neutral.GSM.page.pages})mbh
%_unresponsePERCENTAGEFLOATThe percentage of pages (first + subsequent) that didn?t receive a responsepercentfail({LAC.Neutral.GSM.page.unresponses}, {LAC.Neutral.GSM.page.total_pages})mbh
pagesACCUMULATIONINT8First attempts to page an MS within this Location Area mbh
repagesACCUMULATIONINT8Attempts to re-page (after the first page in this LAC received no response) mbh
responsesACCUMULATIONINT8Responses to pages mbh
total_pagesACCUMULATIONINT8Total attempts to page an MS within this Location Area mbh
unresponsesACCUMULATIONINT8The number of paging attempts that received no response the MS mbh


MSC Performance Indicators

This section shows the key performance indicators and other counters for the MSC object, divided into the following sub-sections:


MSC.Neutral.GSM.call_setup

The call setup performance for calls originating or terminating at an MS in the BSS controlled by this MSC

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_originate_failurePERCENTAGEFLOAT% Failure to assign channels for originating callspercentfail({MSC.Neutral.GSM.call_setup.originate_failures}, {MSC.Neutral.GSM.call_setup.originate_attempts})mbh
%_originate_successPERCENTAGEFLOAT% Success to assign channels for originating callspercentok({MSC.Neutral.GSM.call_setup.originate_successes}, {MSC.Neutral.GSM.call_setup.originate_attempts})mbh
%_terminate_failurePERCENTAGEFLOAT% Failure to assign channels for terminating callspercentfail({MSC.Neutral.GSM.call_setup.terminate_failures}, {MSC.Neutral.GSM.call_setup.terminate_attempts})mbh
%_terminate_successPERCENTAGEFLOAT% Success to assign channels for terminating callspercentok({MSC.Neutral.GSM.call_setup.terminate_successes}, {MSC.Neutral.GSM.call_setup.terminate_attempts})mbh
originate_attemptsACCUMULATIONINT8Channel assignment attempts for originating callsASSPROM_AGGR.Number_of_MO_Traffic_Channel_Assignment_Requestsmbh
originate_failuresACCUMULATIONINT8Failures to assign channels for originating callsASSPROM_AGGR.(Number_of_MO_Traffic_Channel_Assignment_Requests-Number_of_MO_Traffic_Channel_Assignment_Successesmbh
originate_successesACCUMULATIONINT8Successful attempts to assign channels for originating callsASSPROM_AGGR.Number_of_MO_Traffic_Channel_Assignment_Successesmbh
terminate_attemptsACCUMULATIONINT8Channel assignment attempts for terminating callsASSPROM_AGGR.Number_of_MT_Traffic_Channel_Assignment_Requestsmbh
terminate_failuresACCUMULATIONINT8Failures to assign channels for terminating calls(ASSPROM_AGGR.Number_of_MT_Traffic_Channel_Assignment_Requests)-(Number_of_MT_Traffic_Channel_Assignment_Successes)mbh
terminate_successesACCUMULATIONINT8Successful attempts to assign channels for terminating callsASSPROM_AGGR.Number_of_MT_Traffic_Channel_Assignment_Successesmbh


MSC.Neutral.GSM.destination

The calls managed by an MSC to a particular destination MSC

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_answered_callsPERCENTAGEFLOATPercentage of calls to the destination that were answered (Answer-Seize percentage)percentok({MSC.Neutral.GSM.destination.answered_calls}, {MSC.Neutral.GSM.destination.total_calls})mbh
answered_callsACCUMULATIONINT8Number of calls to the destination that were answeredDEST.Number_of_Responsesmbh
answered_mean_holding_timeACCUMULATIONFLOATConversational mean holding time of circuits to the destination (i.e. only counting the part of the call after it has been answered)({MSC.Neutral.GSM.destination.answered_traffic} * {measurement_seconds}) / {MSC.Neutral.GSM.destination.answered_calls}mbh
answered_trafficERLANGFLOATConversational traffic to the destination (i.e. only including the part of the call after it has been answered)DEST.Answered_Traffic_Amountmbh
mean_holding_timeACCUMULATIONFLOATMean holding time of circuits to the destination({MSC.Neutral.GSM.destination.traffic} * {measurement_seconds}) / {MSC.Neutral.GSM.destination.total_calls}mbh
total_callsACCUMULATIONINT8Number of calls to the destinationDEST.Number_of_Call_Attemptsmbh
trafficERLANGFLOATTraffic to the destination (including calls that have not been answered)DEST.Seized_Traffic_Amountmbh


MSC.Neutral.GSM.handover

The results of handovers passing through this MSC, either (a) to or from a different MSC, or (b) between two BSCs controlled by this MSC

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_incoming_intermsc_failurePERCENTAGEFLOATPercentage of incoming nter-MSC handovers that failedpercentfail({MSC.Neutral.GSM.handover.incoming_intermsc_failures}, {MSC.Neutral.GSM.handover.incoming_intermsc_attempts})mbh
%_incoming_intermsc_successPERCENTAGEFLOATPercentage of incoming inter-MSC handovers that succeededpercentfail({MSC.Neutral.GSM.handover.incoming_intermsc_successes}, {MSC.Neutral.GSM.handover.incoming_intermsc_attempts})mbh
%_interbsc_failurePERCENTAGEFLOATPercentage of inter-BSC handovers that failedpercentfail({MSC.Neutral.GSM.handover.interbsc_failures}, {MSC.Neutral.GSM.handover.interbsc_attempts})mbh
%_interbsc_successPERCENTAGEFLOATPercentage of inter-BSC handovers that succeededpercentok({MSC.Neutral.GSM.handover.interbsc_successes}, {MSC.Neutral.GSM.handover.interbsc_attempts})mbh
%_outgoing_intermsc_failurePERCENTAGEFLOATPercentage of outgoing inter-MSC handovers that failedpercentfail({MSC.Neutral.GSM.handover.outgoing_intermsc_failures}, {MSC.Neutral.GSM.handover.outgoing_intermsc_attempts})mbh
%_outgoing_intermsc_successPERCENTAGEFLOATPercentage of outgoing inter-MSC handovers that succeededpercentok({MSC.Neutral.GSM.handover.outgoing_intermsc_successes}, {MSC.Neutral.GSM.handover.outgoing_intermsc_attempts})mbh
incoming_intermsc_attemptsACCUMULATIONINT8Handover attempts coming in from another MSC (i.e. inter-MSC)OBSCHM_AGGR.number_of_to_this_cell_inter_msc_handover_requestsmbh
incoming_intermsc_failuresACCUMULATIONINT8Failed incoming inter-MSC handover attempts (i.e. inter-MSC)OBSCHM_AGGR.number_of_to_this_cell_inter_msc_handover_requests - number_of_to_this_cell_inter_msc_handover_successesmbh
incoming_intermsc_successesACCUMULATIONINT8Successful incoming inter-MSC handover attempts (i.e. inter-MSC)OBSCHM_AGGR.number_of_to_this_cell_inter_mscn_handover_successesmbh
interbsc_attemptsACCUMULATIONINT8Attempted inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HOV.Number_of_Intra_MSC_Handover_Requestsmbh
interbsc_failuresACCUMULATIONINT8Failed inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HOV.Number_of_Intra_MSC_Handover_Requests - Number_of_Intra_MSC_Handover_Successesmbh
interbsc_successesACCUMULATIONINT8Successful inter-BSC handovers controlled by this MSC (i.e. intra-MSC)HOV.Number_of_Intra_MSC_Handover_Successesmbh
outgoing_intermsc_attemptsACCUMULATIONINT8Handover attempts to another MSC (i.e. inter-MSC)OBSCHM_AGGR.number_of_to_other_cell_inter_msc_handover_requestsmbh
outgoing_intermsc_failuresACCUMULATIONINT8Failed outgoing inter-MSC handover attempts (i.e. inter-MSC)OBSCHM_AGGR.(number_of_to_other_cell_inter_msc_handover_requests-number_of_to_other_cell_inter_msc_handover_successes)mbh
outgoing_intermsc_successesACCUMULATIONINT8Successful outgoing inter-MSC handover attempts (i.e. inter-MSC)OBSCHM_AGGR.number_of_to_other_cell_inter_msc_handover_successesmbh


MSC.Neutral.GSM.page

The Paging activity to Mobiles in the BSS controlled by this MSC

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_global_responsePERCENTAGEFLOATPercentage of Global page responsespercentok({MSC.Neutral.GSM.page.global_responses}, {MSC.Neutral.GSM.page.total_global_pages})mbh
%_global_unresponsePERCENTAGEFLOATPercentage of Global pages with no responsepercentfail({MSC.Neutral.GSM.page.global_unresponses}, {MSC.Neutral.GSM.page.total_global_pages})mbh
%_local_responsePERCENTAGEFLOATPercentage of Local responsespercentok({MSC.Neutral.GSM.page.local_responses}, {MSC.Neutral.GSM.page.total_local_pages})mbh
%_local_unresponsePERCENTAGEFLOATPercentage of Local pages with no responsepercentfail({MSC.Neutral.GSM.page.local_unresponses}, {MSC.Neutral.GSM.page.total_local_pages})mbh
global_pagesACCUMULATIONINT8First Global paging messages sentNo mappingmbh
global_repagesACCUMULATIONINTEGERSubsequent (repeat) Global paging messages sentNo mappingmbh
global_responsesACCUMULATIONINTEGERResponses to Global paging messagesNo mappingmbh
global_unresponsesACCUMULATIONINTEGERGlobal paging messages that received no responseNo mappingmbh
local_pagesACCUMULATIONINT8First Local paging messages sentLUPAG_AGGR.Number_of_First_Pagings_from_AIM_Interfacembh
local_repagesACCUMULATIONINT8Subsequent (repeat) Local paging messages sentLUPAG_AGGR.Number_of_Repeated_Pagings_from_AIM_Interfacembh
local_responsesACCUMULATIONINT8Responses to Local paging messagesLUPAG_AGGR.Number_of_First_Paging_Responses+Number_of_Repeated_Paging_Responsesmbh
local_unresponsesACCUMULATIONINT8Local paging messages that received no response((LUPAG_AGGR.Number_of_First_Pagings_from_AIM_Interface)+(Number_of_Repeated_Pagings_from_AIM_Interface))-((Number_of_First_Paging_Responses)+(Number_of_Repeated_Paging_Responses))mbh
total_global_pagesACCUMULATIONINTEGERFirst and subsequent Global paging messagesNo mappingmbh
total_local_pagesACCUMULATIONINT8First and subsequent Local paging messages(LUPAG_AGGR.Number_of_First_Pagings_from_AIM_Interface)+(Number_of_Repeated_Pagings_from_AIM_Interface)mbh


MSC.Neutral.GSM.services

The usage of a Supplementary Service (SS) on an MSC. These are sometimes reported by the HLR, but are associated with an MSC in this data model

KPITypeData TypeDescriptionDerivationAdditional Summaries
activatesACCUMULATIONINTEGERActivations of the SSVLRTM.Number_of_SS_Registrationsmbh
deactivatesACCUMULATIONINTEGERDeactivations of the SSVLRTM.Number_of_SS_Withdrawalsmbh
interrogationsACCUMULATIONINT8Number of times that the SS was interrogatedVLRTM.Number_of_SS_Interrogationsmbh
invocationsACCUMULATIONINT8Invocations of the SSNo mappingmbh


MSC.Neutral.GSM.traffic.total_switched_traffic

The call-switching performance of the MSC for a all switched traffic types

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_answered_callsPERCENTAGEFLOATPercentage of calls that were answeredpercentok({MSC.Neutral.GSM.traffic.total_switched_traffic.answered_calls}, {MSC.Neutral.GSM.traffic.total_switched_traffic.call_attempts})mbh
%_call_failurePERCENTAGEFLOATPercentage of calls that failed (all reasons)percentfail({MSC.Neutral.GSM.traffic.total_switched_traffic.call_failures}, {MSC.Neutral.GSM.traffic.total_switched_traffic.call_attempts})mbh
%_call_successPERCENTAGEFLOATPercentage of calls that were set uppercentok({MSC.Neutral.GSM.traffic.total_switched_traffic.call_successes}, {MSC.Neutral.GSM.traffic.total_switched_traffic.call_attempts})mbh
answered_callsACCUMULATIONINTEGERCalls that were answeredgroup({MSC.Neutral.GSM.traffic.answered_calls})mbh
call_attemptsACCUMULATIONINTEGERCall attempts for all switched Traffic Typesgroup({MSC.Neutral.GSM.traffic.call_attempts})mbh
call_failuresACCUMULATIONINTEGERCalls that failed (all reasons)group({MSC.Neutral.GSM.traffic.call_failures})mbh
call_successesACCUMULATIONINTEGERCalls that were set upgroup({MSC.Neutral.GSM.traffic.call_successes})mbh
external_failed_callsACCUMULATIONINTEGERCalls that failed due to errors beyond this entity or networkgroup({MSC.Neutral.GSM.traffic.external_failed_calls})mbh
internal_failed_callsACCUMULATIONINTEGERCalls that failed due to errors in this entity or networkgroup({MSC.Neutral.GSM.traffic.internal_failed_calls})mbh
subscriber_error_callsACCUMULATIONINTEGERFailed calls due to subscriber errorgroup({MSC.Neutral.GSM.traffic.subscriber_error_calls})mbh
trafficERLANGFLOATCircuit occupancy for all switched Traffic Typesgroup({MSC.Neutral.GSM.traffic.traffic})mbh


MSC.Neutral.GSM.traffic

The call-switching performance of the MSC for a particular traffic type

The performance data measurements for this KPI group are recorded against the combination of MSC and Traffic_Type (Traffic_Type_Id) .

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_answered_callsPERCENTAGEFLOATPercentage of calls that were answeredpercentok({MSC.Neutral.GSM.traffic.answered_calls}, {MSC.Neutral.GSM.traffic.call_attempts})mbh, mtbh
%_call_failurePERCENTAGEFLOATPercentage of calls that failed (all reasons)percentfail({MSC.Neutral.GSM.traffic.call_failures}, {MSC.Neutral.GSM.traffic.call_attempts})mbh, mtbh
%_call_successPERCENTAGEFLOATPercentage of calls that were set uppercentok({MSC.Neutral.GSM.traffic.call_successes}, {MSC.Neutral.GSM.traffic.call_attempts})mbh, mtbh
answered_callsACCUMULATIONINT8Calls that were answeredMSC_TRAFTYPE.Number_of_Answered_Calls (where traffic_type = ORG or INT or ORGOEX or IEX or IEXTE or TRA or TE or OEX)mbh, mtbh
call_attemptsACCUMULATIONINT8Call attempts in this Traffic TypeMSC_TRAFTYPE.Number_of_Call_Attempts (where traffic_type = ORG or INT or ORGOEX or IEX or IEXTE or TRA or TE or OEX)mbh, mtbh
call_failuresACCUMULATIONINT8Calls that failed (all reasons)MSC_TRAFTYPE.Number_of_Call_Attempts - Number_of_Connected_Calls (where traffic_type = ORG or INT or ORGOEX or IEX or IEXTE or TRA or TE or OEX)mbh, mtbh
call_successesACCUMULATIONINT8Calls that were set upMSC_TRAFTYPE.Number_of_Connected_Calls (where traffic_type = ORG or INT or ORGOEX or IEX or IEXTE or TRA or TE or OEX)mbh, mtbh
external_failed_callsACCUMULATIONINT8Calls that failed due to errors beyond this entity or networkNo mappingmbh, mtbh
internal_failed_callsACCUMULATIONINT8Calls that failed due to errors in this entity or networkNo mappingmbh, mtbh
subscriber_error_callsACCUMULATIONINT8Failed calls due to subscriber errorNo mappingmbh, mtbh
trafficERLANGFLOATCircuit occupancy for this Traffic TypeMSC_TRAFTYPE.Seized_Traffic_Amount (where traffic_type = ORG or INT or ORGOEX or IEX or IEXTE or TRA or TE or OEX)mbh, mtbh


Route_IF Performance Indicators

This section shows the key performance indicators and other counters for the Route_IF object, divided into the following sub-sections:


Route_IF.Neutral.GSM.transmission.forecast

The forecast performance of the Route

KPITypeData TypeDescriptionDerivationAdditional Summaries
capacityINTENSITYFLOATForecast capacity or critical traffic level based upon a user supplied grade of service leveltp_gsm_route_capacity_collect(nc_route.route_if_id, ml_subst(gStartdate), tp_gsm_route_bh_traffic_end_date(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)), ml_subst(gNumdays), "ml_subst(gGOS)", ml_property(system.property.dgos)) 
extra_circuitsINTENSITYINTEGERForecast extra circuits requiredtp_gsm_route_bh_extra_circuits_forecast_value(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), "ml_subst(gGOS)") 
linear_exhaustion_dateINTENSITYINTEGERForecast linear exhaustion date for the routeDECODE((tp_gsm_route_bh_traffic_exhaustion_date(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage), "ml_subst(gGOS)", ml_property(system.property.dgos),NULL)), NULL, "will not reach exhaustion in this period","will reach exhausion on "||(tp_gsm_route_bh_traffic_exhaustion_date(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage), "ml_subst(gGOS)", ml_property(system.property.dgos),NULL))) 
linear_regression_coefficientINTENSITYFLOATForecast linear regression coefficienttp_gsm_route_bh_traffic_forecast_growth(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_regression_errorINTENSITYFLOATForecast linear regression errortp_gsm_route_bh_traffic_regression_error(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_traffic_growthERLANGFLOATForecast linear traffic growthtp_gsm_route_bh_traffic_forecast_growth(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
required_circuitsINTENSITYINTEGERForecast number of circuits that can deliver the specified forecast grade of service for the offered traffictp_gsm_route_bh_required_circuits_forecast_value(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), "ml_subst(gGOS)") 
trafficERLANGFLOATForecast traffic on the routetp_gsm_route_bh_traffic_forecast_value(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), NULL) 
utilisationINTENSITYFLOATForecast utilisationtp_gsm_route_bh_utilisation_forecast_value(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), NULL) 


Route_IF.Neutral.GSM.transmission

The performance of the Route as seen from this end (Interface), reported by an MSC

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_blocked_circuitsPERCENTAGEFLOATPercentage of circuits that are blocked or otherwise out of servicepercentfail({Route_IF.Neutral.GSM.transmission.blocked_circuits}, {Route_IF.Neutral.GSM.transmission.circuits})rbh
%_bothway_answeredPERCENTAGEFLOATPercentage of calls (incoming+outgoing) that were answered (Answer-Seize percentage)percentok({Route_IF.Neutral.GSM.transmission.bothway_answered_calls}, {Route_IF.Neutral.GSM.transmission.bothway_calls})rbh
%_incoming_answeredPERCENTAGEFLOATPercentage of incoming calls that were answered (Answer-Seize percentage)percentok({Route_IF.Neutral.GSM.transmission.incoming_answered_calls}, {Route_IF.Neutral.GSM.transmission.incoming_calls})rbh, ribh
%_outgoing_answeredPERCENTAGEFLOATPercentage of outgoing calls that were answered (Answer-Seize percentage)percentok({Route_IF.Neutral.GSM.transmission.outgoing_answered_calls}, {Route_IF.Neutral.GSM.transmission.outgoing_calls})rbh, robh
%_outgoing_congestionsPERCENTAGEFLOATPercentage of outgoing calls that found all circuits busypercentfail({Route_IF.Neutral.GSM.transmission.outgoing_congestions}, {Route_IF.Neutral.GSM.transmission.bids})rbh, robh
available_circuitsINTENSITYFLOATNumber of unblocked, in-service circuitsTGRP.Total_Number_of_Bidirectional_Trunk_Available_Trunk_Linesrbh
bidsACCUMULATIONINT8The number of attempts to seize a circuit (from this end)No mappingrbh, robh
blocked_circuitsINTENSITYFLOATNumber of circuits that are blocked or otherwise out of serviceTGRP.Total_Number_of_Bidirectional_Trunk_Blocked_Trunk_Linesrbh
bothway_answered_callsACCUMULATIONINTEGERNumber of incoming+outgoing calls that were answered{Route_IF.Neutral.GSM.transmission.incoming_answered_calls} + {Route_IF.Neutral.GSM.transmission.outgoing_answered_calls}rbh
bothway_callsACCUMULATIONINTEGERThe number of incoming calls plus the number of outgoing calls{Route_IF.Neutral.GSM.transmission.incoming_calls} + {Route_IF.Neutral.GSM.transmission.outgoing_calls}rbh
bothway_trafficERLANGFLOATIncoming+Outgoing traffic on the Route{Route_IF.Neutral.GSM.transmission.incoming_traffic} + {Route_IF.Neutral.GSM.transmission.outgoing_traffic}rbh
busy_time_pcINTENSITYFLOATThe percentage of time that all circuits were busy (i.e. couldn?t accept outgoing bids)No mappingrbh
capacityINTENSITYFLOATThe capacity or critical traffic level based upon a user supplied grade of service levelcriticaltraffic({Route_IF.Neutral.GSM.transmission.circuits},ml_property(system.property.dgos))rbh
circuitsINTENSITYINT8Number of circuits provisioned on the Route for incoming and or outgoing trafficTGRP.Total_Number_of_Bidirectional_Trunk_Linesrbh
extra_capacity_requiredINTENSITYINTEGERForecast extra capacity requiredDECODE("ml_subst(gUser)","true","true",(DECODE((tp_gsm_route_bh_required_circuits_end_value(nc_route.route_if_id, tp_gsm_route_bh_traffic_end_date(nc_route.route_if_id,ml_subst(gStartdate),ml_subst(gEnddate),ml_subst(gDataCoverage)), "ml_subst(gGOS)", ml_property(system.property.dgos))-tp_gsm_route_bh_circuits_end_value(nc_route.route_if_id, tp_gsm_route_bh_traffic_end_date(nc_route.route_if_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)), NULL, NULL)),0,"false","true"))) 
grade_of_serviceINTENSITYFLOATThe estimated Grade of Service (GoS)gos({Route_IF.Neutral.GSM.transmission.available_circuits}, {Route_IF.Neutral.GSM.transmission.offered_traffic})rbh
incoming_answered_callsACCUMULATIONINT8Number of incoming calls that were answeredTGRP.Bidirectional_Trunk_Incoming_Call_Answered_Traffic_Amountrbh, ribh
incoming_callsACCUMULATIONINT8The number of incoming calls started (i.e. circuit seizures from the other end)TGRP.Number_of_Bidirectional_Trunk_Incoming_Call_Seizures Bidirectional_trunk_incoming_call_seizuresrbh, ribh
incoming_mean_holding_timeACCUMULATIONFLOATMean holding time for incoming calls({Route_IF.Neutral.GSM.transmission.incoming_traffic} * {Route_IF.Neutral.GSM.transmission.measurement_seconds}) / {Route_IF.Neutral.GSM.transmission.incoming_calls}rbh, ribh
incoming_trafficERLANGFLOATIncoming traffic on the RouteTGRP.Bidirectional_Trunk_Incoming_Call_Seized_Traffic_Amountrbh, ribh
is_exhaustedINTENSITYINTEGERForecasting flag indicating if route is exhaustedDECODE(tp_gsm_route_bh_traffic_exhaustion_date(nc_route.route_if_id,ml_subst(gStartdate),ml_subst(gEnddate),ml_subst(gDataCoverage), "ml_subst(gGOS)", ml_property(system.property.dgos),NULL),NULL,"YES","NO") 
lost_trafficERLANGFLOATThe estimated traffic lost to the route{Route_IF.Neutral.GSM.transmission.offered_traffic} - {Route_IF.Neutral.GSM.transmission.bothway_traffic}rbh
number_of_samplesINTENSITYINTEGERForecasting number of data samples  
offered_trafficERLANGFLOATThe estimated traffic offered to the Routeofferedtraffic({Route_IF.Neutral.GSM.transmission.available_circuits}, ({Route_IF.Neutral.GSM.transmission.bothway_traffic}))rbh
offered_utilisationPERCENTAGEFLOATThe estimated traffic lost to the routepercentok({Route_IF.Neutral.GSM.transmission.offered_traffic}, {Route_IF.Neutral.GSM.transmission.circuits})rbh
outgoing_answered_callsACCUMULATIONINT8Number of outgoing calls that were answeredTGRP.Number_of_Answered_Bidirectional_Trunk_Outgoing_Callsrbh, robh
outgoing_callsACCUMULATIONINT8The number of successful bids (seizures) of a circuitTGRP.Bidirectional_Trunk_Outgoing_Call_Seizure_Attemptsrbh, robh
outgoing_congestion_timeACCUMULATIONINT8The total time during the measurement period that all circuits on the Route were busy (i.e. couldn?t accept outgoing bids)No mappingrbh, robh
outgoing_congestionsACCUMULATIONINT8The number of bids that find that all circuits are busy. Such bids may either fail or overflow onto another Circuit GroupTGRP.Number_of_Bidirectional_Trunk_Outgoing_Call_Peer_Office_Circuit_Group_Congestionsrbh, robh
outgoing_mean_holding_timeACCUMULATIONFLOATMean holding time for outgoing calls({Route_IF.Neutral.GSM.transmission.outgoing_traffic} * {Route_IF.Neutral.GSM.transmission.measurement_seconds}) / {Route_IF.Neutral.GSM.transmission.outgoing_calls}rbh, robh
outgoing_trafficERLANGFLOATOutgoing traffic on the RouteTGRP.Bidirectional_Trunk_Incoming_Call_Seized_Traffic_Amountrbh, robh
required_circuitsINTENSITYINTEGERThe smallest integer number of circuits that can deliver the specified design grade of service for the offered trafficrequiredcircuits({Route_IF.Neutral.GSM.transmission.offered_traffic}, ml_property(system.property.dgos))rbh
required_extra_circuitsINTENSITYINTEGERThe smallest integer number of extra circuits required that can deliver the specified design grade of service for the offered traffic{Route_IF.Neutral.GSM.transmission.required_circuits} - {Route_IF.Neutral.GSM.transmission.circuits}rbh
trafficERLANGFLOATForecasting traffic value based on weekly summary data(route_interface_transmission_week.rbh_incoming_traffic + route_interface_transmission_week.rbh_incoming_traffic)rbh


Signalling_Link Performance Indicators

This section shows the key performance indicators and other counters for the Signalling_Link object, divided into the following sub-sections:


Signalling_Link.Neutral.GSM.link

The performance of an individual Signalling Link

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_availablePERCENTAGEFLOATPercentage of time (during the measurement period) that the Link was availablepercentok({Signalling_Link.Neutral.GSM.traffic.available_time}, ({Signalling_Link.Neutral.GSM.traffic.available_time} + {Signalling_Link.Neutral.GSM.traffic.unavailable_time}))slrbh, sltbh
%_local_inhibition_timePERCENTAGEFLOATPercentage of time (during the measurement period) that the link was inhibited due to local management actionspercentfail({Signalling_Link.Neutral.GSM.traffic.local_inhibition_time}, ({Signalling_Link.Neutral.GSM.traffic.available_time} + {Signalling_Link.Neutral.GSM.traffic.unavailable_time}))slrbh, sltbh
%_remote_inhibition_timePERCENTAGEFLOATPercentage of time (during the measurement period) that the link was inhibited due to remote management actionspercentfail({Signalling_Link.Neutral.GSM.traffic.remote_inhibition_time}, ({Signalling_Link.Neutral.GSM.traffic.available_time} + {Signalling_Link.Neutral.GSM.traffic.unavailable_time}))slrbh, sltbh
%_unavailablePERCENTAGEFLOATPercentage of time (during the measurement period) that the Link was unavailablepercentfail({Signalling_Link.Neutral.GSM.traffic.unavailable_time}, ({Signalling_Link.Neutral.GSM.traffic.available_time} + {Signalling_Link.Neutral.GSM.traffic.unavailable_time}))slrbh, sltbh
available_timeACCUMULATIONINT8Amount of time the Link was available during the measurement period(GP) - round(C7LL.Duration_of_Signaling_Link_Unavailable, 0)slrbh, sltbh
changebacksACCUMULATIONINT8Local automatic changebacksNo mappingslrbh, sltbh
changeoversINTENSITYFLOATLocal automatic changeoversNo mappingslrbh, sltbh
congestion_lossesACCUMULATIONINT8Number of congestion events that resulted in lost MSUsNo mappingslrbh, sltbh
congestion_timeACCUMULATIONINT8Amount of time during which the Link was congestedC7LL.round(Duration_of_Signaling_Link_Congestions,0)slrbh, sltbh
congestionsACCUMULATIONINT8Number of Link congestion indicationsC7LL.Number_of_Signaling_Link_Congestionsslrbh, sltbh
discarded_msusACCUMULATIONINT8Number of MSUs that were discarded because of Link congestionC7LL.Number_of_Lost_Message_Signal_Units_due_to_Signaling_Link_Congestionsslrbh, sltbh
failures_abrACCUMULATIONINT8Link failures due to receipt of an abnormal FIBR or BSNRNo mappingslrbh, sltbh
failures_alignmentACCUMULATIONINT8Link failures due to alignment or proving failureNo mappingslrbh, sltbh
failures_congestionACCUMULATIONINT8Link failures due to the link being congested for too longNo mappingslrbh, sltbh
failures_delayACCUMULATIONINT8Link failures due to excessive delay on ACKNo mappingslrbh, sltbh
failures_error_rateACCUMULATIONINT8Link failures due to an excessive error rateNo mappingslrbh, sltbh
failuresACCUMULATIONINT8Link failures (any reason)C7LL.Number_of_Signaling_Link_Failuresslrbh, sltbh
in_service_timeINTENSITYFLOATThe total time the Link has been up (since last reset)No mappingslrbh, sltbh
incoming_trafficACCUMULATIONINT8Incoming traffic receivedC7LL.Number_of_SIF_and_SIO_Octets_Received + (6*Number_of_Message_Signal_Units_Received)slrbh
incoming_utilisationPERCENTAGEFLOATIncoming traffic utilisation ? percentage of available incoming capacity usedpercentok((8 * {Signalling_Link.Neutral.GSM.traffic.incoming_traffic}), {Signalling_Link.Neutral.GSM.measurement_seconds} * (decode(nc_ss7_link.data_rate, null, 0, "NULL", 0, nc_ss7_link.data_rate)))slrbh
link_failure_timeACCUMULATIONINT8Amount of time the Link was unavailable because it had failedC7LL.round(Duration_of_Signaling_Link_Failure, 0)slrbh, sltbh
local_busy_timeACCUMULATIONINT8Amount of local busy timeNo mappingslrbh, sltbh
local_inhibition_timeACCUMULATIONINT8Amount of time the link was inhibited due to local management actionsC7LL.round(Duration_of_Local_Management_Inhibit, 0)slrbh, sltbh
outgoing_trafficACCUMULATIONINT8Outgoing traffic sentC7LL.Number_of_Sent_SIF_and_SIO_Octets + (6 * Number_of_Sent_Message_Signal_Units)sltbh
outgoing_utilisationPERCENTAGEFLOATOutgoing traffic utilisation ? percentage of available outgoing capacity usedpercentok((8 * {Signalling_Link.Neutral.GSM.traffic.outgoing_traffic}), {Signalling_Link.Neutral.GSM.measurement_seconds} * (decode(nc_ss7_link.data_rate, null, 0, "NULL", 0, nc_ss7_link.data_rate)))sltbh
received_msusACCUMULATIONINT8Number of Message Signal Units (MSUs) receivedC7LL.Number_of_Message_Signal_Units_Receivedslrbh
received_neg_ackACCUMULATIONINT8Number of negative acknowledgements (ACK) receivedNo mappingslrbh
received_sif_siosACCUMULATIONINT8Number of SIF and SIO octets receivedC7LL.Number_of_SIF_and_SIO_Octets_Receivedslrbh
received_su_errorsACCUMULATIONINT8Number of Signalling Units (Sus) received with errorsNo mappingslrbh
remote_inhibition_timeACCUMULATIONINT8Amount of time the link was inhibited due to remote management actionsC7LL.round(Duration_of_Remote_Management_Inhibit, 0)slrbh, sltbh
remote_outage_timeACCUMULATIONINTEGERAmount of time the Link was unavailable because of a remote Processor outageC7LL.round(Duration_of_Remote_Processor_Fault, 0)slrbh, sltbh
remote_outagesACCUMULATIONINT8Number of remote Processor outagesC7LL.Number_of_Remote_Processor_Faultsslrbh, sltbh
restoresACCUMULATIONINTEGERNumber of times the link was restoredC7LL.Number_of_Local_Automatic_Switchoversslrbh, sltbh
retransmitted_sif_siosACCUMULATIONINT8Number of SIF and SIO octets re-transmittedNo mappingsltbh
transmitted_msusACCUMULATIONINT8Number of Message Signal Units (MSUs) transmittedC7LL.Number_of_Sent_Message_Signal_Unitssltbh
transmitted_sif_siosACCUMULATIONINT8Number of SIF and SIO octets transmittedC7LL.Number_of_Sent_SIF_and_SIO_Octetssltbh
unavailable_timeACCUMULATIONINT8Amount of time the Link was unavailable (for any reason)C7LL.round(Duration_of_Signaling_Link_Unavailable, 0)slrbh, sltbh


Signalling_LinkSet Performance Indicators

This section shows the key performance indicators and other counters for the Signalling_LinkSet object, divided into the following sub-sections:


Signalling_LinkSet.Neutral.GSM.forecast

The forecast performance of a set of Signalling Links

KPITypeData TypeDescriptionDerivationAdditional Summaries
capacityERLANGFLOATForecast maximum nominal Erlangs per linksettp_gsm_linkset_capacity_collect(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), tp_gsm_linkset_bh_incoming_traffic_end_date(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)), ml_subst(gNumdays), "ml_subst(gNMT)", ml_property(system.property.dnmt)) 
in_failure_capacityERLANGFLOATForecast capacity for the entire linkset during design link failurestp_gsm_linkset_in_failure_capacity_collect(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), tp_gsm_linkset_bh_incoming_traffic_end_date(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)), ml_subst(gNumdays), "ml_subst(gNMT)", ml_property(system.property.dnmt)) 
linear_exhaustion_dateINTENSITYINTEGERForecast linear exhaustion dateDECODE((tp_gsm_linkset_bh_incoming_traffic_exhaustion_date(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage), "ml_subst(gNMT)" ,ml_subst(gMIT),ml_subst(gLIF))), NULL, "will not reach exhaustion in this period","will reach exhausion on "||(tp_gsm_linkset_bh_incoming_traffic_exhaustion_date(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage), "ml_subst(gNMT)",ml_subst(gMIT),ml_subst(gLIF)))) 
linear_regression_coefficientINTENSITYFLOATForecast linear regression coefficienttp_gsm_linkset_bh_incoming_traffic_forecast_growth(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_regression_errorINTENSITYFLOATForecast linear regression errortp_gsm_linkset_bh_incoming_traffic_regression_error(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
linear_traffic_growthINTENSITYFLOATFroecast linear traffic growthtp_gsm_linkset_bh_incoming_traffic_forecast_growth(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gDataCoverage)) 
trafficACCUMULATIONFLOATForecast traffic valuetp_gsm_linkset_bh_incoming_traffic_forecast_value(nc_ss7_linkset.ss7_linkset_id, ml_subst(gStartdate), ml_subst(gEnddate), ml_subst(gNumdays), ml_subst(gDataCoverage), NULL) 


Signalling_LinkSet.Neutral.GSM.signalling_linkset

The performance of a set of Signalling Links

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_availablePERCENTAGEFLOATPercentage of time (during the measurement period) that the LinkSet was availablepercentok({Signalling_LinkSet.Neutral.GSM.signalling_linkset.available_time}, ({Signalling_LinkSet.Neutral.GSM.signalling_linkset.available_time} + {Signalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_time}))slsrbh, slstbh
%_unavailablePERCENTAGEFLOATPercentage of time (during the measurement period) that the LinkSet was unavailablepercentfail({Signalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_time}, ({Signalling_LinkSet.Neutral.GSM.signalling_linkset.available_time} + {Signalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_time}))slsrbh, slstbh
available_timeACCUMULATIONINT8Time for which the LinkSet was available(GP) - LSETM.Signaling_Link_Set_Not_Available_Durationslsrbh, slstbh
capacityERLANGFLOATMaximum nominal Erlangs per linksetNo mappingslsrbh, slstbh
failuresACCUMULATIONINT8Number of LinkSet failuresLSETM.Number_of_times_Signaling_Link_Set_Not_Availableslsrbh, slstbh
in_failure_capacityERLANGFLOATCapacity for the entire linkset during design link failurescriticaltraffic(ss7_linkset_week.count_links, "ml_subst(gMIT)") 
incoming_trafficACCUMULATIONINTEGERTotal Incoming traffic receivedNo mappingslsrbh
incoming_utilisationPERCENTAGEFLOATIncoming traffic utilisation ? percentage of available incoming capacity usedpercentok((8 * {Signalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_traffic}), {Signalling_LinkSet.Neutral.GSM.signalling_linkset.measurement_seconds} * avg(decode(nc_ss7_linkset.data_rate, null, 0, "NULL", 0, nc_ss7_linkset.data_rate)))slsrbh
is_exhaustedINTENSITYINTEGERForecast flag indicating if linkset capacity is exhaustedDECODE(tp_gsm_linkset_bh_incoming_traffic_exhaustion_date(nc_ss7_linkset.ss7_linkset_id,ml_subst(gStartdate),ml_subst(gEnddate),ml_subst(gDataCoverage), "ml_subst(gNMT)",ml_subst(gMIT),ml_subst(gLIF)),NULL,"YES","NO") 
linksACCUMULATIONINTEGERNumber of Links in the LinkSetcount({Signalling_Link.Neutral.GSM.link.ss7_link_id})slsrbh, slstbh
mean_%_availablePERCENTAGEFLOATAverage percentage Availability of the Links in the LinkSetpercentfail({Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_available_time}, ({Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_available_time} + {Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_unavailable_time}))slsrbh, slstbh
mean_%_unavailablePERCENTAGEFLOATAverage percentage Unavailability of the Links in the LinkSetpercentfail({Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_unavailable_time}, ({Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_available_time} + {Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_unavailable_time}))slsrbh, slstbh
mean_available_timeINTENSITYFLOATAverage Link available time for all the Links in the LinksetNo mappingslsrbh, slstbh
mean_incoming_trafficINTENSITYFLOATAverage Incoming traffic received per link slsrbh
mean_outgoing_trafficINTENSITYFLOATAverage Outgoing traffic sent per link slstbh
mean_unavailable_timeINTENSITYFLOATAverage Link available time for all the Links in the Linkset slsrbh, slstbh
msusACCUMULATIONINTEGERForecast number of Message Signal Units (MSUs)  
number_of_samplesINTENSITYINTEGERForecast number of samples  
outgoing_trafficACCUMULATIONINTEGERTotal Outgoing traffic sent slstbh
outgoing_utilisationPERCENTAGEFLOATOutgoing traffic utilisation ? percentage of available outgoing capacity usedpercentok((8 * {Signalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_traffic}), {Signalling_LinkSet.Neutral.GSM.signalling_linkset.measurement_seconds} * avg(decode(nc_ss7_linkset.data_rate, null, 0, "NULL", 0, nc_ss7_linkset.data_rate)))slstbh
received_msusACCUMULATIONINTEGERNumber of Message Signal Units (MSUs) receivedNo mappingslsrbh
received_sif_siosACCUMULATIONINTEGERNumber of SIF and SIO octets receivedNo mappingslsrbh
total_failuresACCUMULATIONINTEGERTotal Failures of all Links in the LinkSetNo mappingslsrbh, slstbh
trafficACCUMULATIONINTEGERForecast total trafficNo mappingslsrbh, slstbh
transmitted_msusACCUMULATIONINTEGERNumber of Message Signal Units (MSUs) transmittedNo mappingslstbh
transmitted_sif_siosACCUMULATIONINTEGERNumber of SIF and SIO octets transmittedNo mappingslstbh
unavailable_timeACCUMULATIONINT8Time for which the LinkSet was unavailableLSETM.Signaling_Link_Set_Not_Available_Durationslsrbh, slstbh


Signalling_Point Performance Indicators

This section shows the key performance indicators and other counters for the Signalling_Point object, divided into the following sub-sections:


Signalling_Point.Neutral.GSM.signalling_point

The signalling networks performance, as seen from a Signalling Point

KPITypeData TypeDescriptionDerivationAdditional Summaries
adjacent_sp_inaccessible_timeACCUMULATIONINT8Time for which an adjacent Signalling Point was inaccessibleDSPM.DSP_Inaccessible_Duration 
adjacent_sp_inaccessibleACCUMULATIONINT8Number of times an adjacent Signalling Point became inaccessibleDSPM.Number_of_Times_DSP_Inaccessible 
discarded_msusACCUMULATIONINT8Number of Message Signal Units (MSUs) discarded due to routing errorsNo mapping 
received_tfcsACCUMULATIONINTEGERNumber of Transfer-Control (TFC) signals received, indicating RouteSet congestionNo mapping 


VLR Performance Indicators

This section shows the key performance indicators and other counters for the VLR object, divided into the following sub-sections:


VLR.Neutral.GSM.mobility

The Mobility management activity (e.g. Location Area updates) in the BSS controlled by this VLR

KPITypeData TypeDescriptionDerivationAdditional Summaries
%_id_request_failurePERCENTAGEFLOATPercentage of failed identification requests to PVLRpercentfail({VLR.Neutral.GSM.mobility.id_request_failures}, {VLR.Neutral.GSM.mobility.id_request_attempts})mbh, vbh
%_id_request_successPERCENTAGEFLOATPercentage of successful identification requests to PVLRpercentok({VLR.Neutral.GSM.mobility.id_request_successes}, {VLR.Neutral.GSM.mobility.id_request_attempts})mbh, vbh
%_imsi_attach_failurePERCENTAGEFLOATPercentage of failed IMSI attach attemptspercentfail({VLR.Neutral.GSM.mobility.imsi_attach_failures}, {VLR.Neutral.GSM.mobility.imsi_attach_attempts})mbh, vbh
%_imsi_attach_successPERCENTAGEFLOATPercentage of successful IMSI attach attemptspercentok({VLR.Neutral.GSM.mobility.imsi_attach_successes}, {VLR.Neutral.GSM.mobility.imsi_attach_attempts})mbh, vbh
%_lac_update_failurePERCENTAGEFLOATPercentage of failed Location Area updatespercentfail({VLR.Neutral.GSM.mobility.lac_update_failures}, {VLR.Neutral.GSM.mobility.lac_update_attempts})mbh, vbh
%_lac_update_successPERCENTAGEFLOATPercentage of successful Location Area updatespercentok({VLR.Neutral.GSM.mobility.lac_update_successes}, {VLR.Neutral.GSM.mobility.lac_update_attempts})mbh, vbh
%_vlr_update_failurePERCENTAGEFLOATPercentage of Intra-VLR Location Area update failurespercentfail({VLR.Neutral.GSM.mobility.vlr_update_failures}, {VLR.Neutral.GSM.mobility.vlr_update_attempts})mbh, vbh
%_vlr_update_successPERCENTAGEFLOATPercentage of Intra-VLR Location Area update successespercentfail({VLR.Neutral.GSM.mobility.vlr_update_successes}, {VLR.Neutral.GSM.mobility.vlr_update_attempts})mbh, vbh
id_request_attemptsACCUMULATIONINT8Identification requests to PVLRAUTHSM.Number_of_Times_VLR_Acquiring_Authentication_Set_from_PVLRmbh, vbh
id_request_failuresACCUMULATIONINTEGERFailed identification requests to PVLRAUTHSM.Number_of_Times_VLR_Acquiring_Authentication_Set_from_PVLR - Number_of_times_VLR_Received_Authentication_Set_from_PVLRmbh, vbh
id_request_successesACCUMULATIONINTEGERSuccessful identification requests to PVLRAUTHSM.Number_of_times_VLR_Received_Authentication_Set_from_PVLRmbh, vbh
imsi_attach_attemptsACCUMULATIONINT8IMSI attach attemptsLUPAG_AGGR.Number_of_IMSI_Attachesmbh, vbh
imsi_attach_failuresACCUMULATIONINT8Failed IMSI attach attemptsLUPAG_AGGR.Location_Update_Failure_due_to_HLR_Unknown_Subscribermbh, vbh
imsi_attach_successesACCUMULATIONINT8Successful IMSI attach attemptsLUPAG_AGGR.Number_of_IMSI_Attaches - Location_Update_Failure_due_to_HLR_Unknown_Subscribermbh, vbh
imsi_attach_updatesACCUMULATIONINT8Updates due to IMSI attachNo mappingmbh, vbh
imsi_detachesACCUMULATIONINT8IMSI detach eventsLUPAG_AGGR.Number_of_IMSI_Detachesmbh, vbh
lac_update_attemptsACCUMULATIONINT8Location Area update attemptsLUPAG_AGGR.Number_of_Location_Update_Requestsmbh, vbh
lac_update_failuresACCUMULATIONINT8Failed Location Area updatesLUPAG_AGGR.Number_of_Location_Update_Rejectsmbh, vbh
lac_update_successesACCUMULATIONINT8Successful Location Area updatesLUPAG_AGGR.Number_of_Location_Update_Requests - Number_of_Location_Update_Rejectsmbh, vbh
new_la_updatesACCUMULATIONINT8Updates for a new Location AreaLUPAG_AGGR.Number_of_Subscriber_Roaming_Location_Update_Requestsmbh, vbh
periodic_updatesACCUMULATIONINT8Periodic updatesNo mappingmbh, vbh
vlr_subscribersACCUMULATIONINT8Subscribers in this VLRMSC.Number_of_VLR_subscribers_in_totalmbh, vbh
vlr_update_attemptsACCUMULATIONINT8Intra-VLR Location Area update attemptsLUPAG_AGGR.Number_of_Location_Update_Requests_in_VLRmbh, vbh
vlr_update_failuresACCUMULATIONINTEGERIntra-VLR Location Area update failuresLUPAG_AGGR.Number_of_Location_Update_Requests_in_VLR - Number_of_Successful_Location_Updates_in_VLRmbh, vbh
vlr_update_successesACCUMULATIONINTEGERIntra-VLR Location Area update successesLUPAG_AGGR.Number_of_Successful_Location_Updates_in_VLRmbh, vbh
vlr_visitorsACCUMULATIONINT8Visitors from other PLMNs in this VLRMSC.Number_of_Other_Network_Subscribers_in_VLRmbh, vbh



9. Performance Alarms

This section shows details of the alarms that are defined in this technology pack:

None.

10. Reports

This section shows details of the reports that are defined in this technology pack:


Historical Route Traffic Report

This report shows key route traffic statistics for a single route over all the weeks in the forecast base range. The report shows available & defined circuits, % congestion, carried traffic, offered traffic, lost traffic, critical traffic, 3-DAV and 5-DAV traffic, % utilisation and grade of service. The report is always generated with weekly busy hour values.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingNo
Period SelectionWeekly
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Historical Route Traffic Report (Table)
3-DAV Summarised Carried Traffic (E)Route_IF.Neutral.GSM.transmission.traffic3-day Average 
5-DAV Summarised Carried Traffic (E)Route_IF.Neutral.GSM.transmission.traffic5-day Average 
Available ChannelsRoute_IF.Neutral.GSM.transmission.available_circuitsbusy_hour 
Blocking (%)Route_IF.Neutral.GSM.transmission.%_outgoing_congestionsbusy_hour 
Busy Hourbusy_hourbusy_hour 
CapacityRoute_IF.Neutral.GSM.transmission.capacitybusy_hour 
Carried Traffic (E)Route_IF.Neutral.GSM.transmission.trafficbusy_hour 
Defined ChannelsRoute_IF.Neutral.GSM.transmission.circuitsbusy_hour 
GOSRoute_IF.Neutral.GSM.transmission.grade_of_servicebusy_hour 
Lost Traffic (E)Route_IF.Neutral.GSM.transmission.lost_trafficbusy_hour 
Offered Traffic (E)Route_IF.Neutral.GSM.transmission.offered_trafficbusy_hour 
Offered UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationbusy_hour 
RouteRoute_IF.nameUser-defined 
Week_of User-defined 

Interconnect Traffic Graph

This graph shows the total traffic profile for all routes connecting an MSC to a POI (a POI route).

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object Selection 
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Interconnect Traffic Graph (Line Chart)
Traffic (E)Route_IF.Neutral.GSM.transmission.bothway_trafficUser-defined 

Inter-switch Traffic Graph

This graph shows the total traffic profile for all routes connecting an MSC to an MSC (a trunk route).

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object Selection 
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Inter-switch Traffic Graph (Line Chart)
Traffic (E)Route_IF.Neutral.GSM.transmission.bothway_trafficUser-defined 

LAC Paging Graph

This shows the performance of LAC paging attempts within a Location Area

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.LAC
Primary ObjectLAC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionLAC
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Eventual Response (Line Chart)
% Eventual ResponseLAC.Neutral.GSM.page.%_successUser-defined 
Component 2: % Page/Repage Response (Line Chart)
% Page/Repage ResponseLAC.Neutral.GSM.page.%_responseUser-defined 
Component 3: Pages Without Response (Line Chart)
Pages Without ResponseLAC.Neutral.GSM.page.unresponsesUser-defined 
Component 4: Total Paging Attempts (Line Chart)
Total Paging AttemptsLAC.Neutral.GSM.page.total_pagesUser-defined 

Linkset Availability Report Link KPIs

This report shows the availability of a set of linksets and failures and unavailability on the constituent links.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionTotal
FilteringSignalling_LinkSet.Neutral.GSM.signalling_linkset.total_failures (min), Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverage (min), Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_unavailable_time (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SS7 Linkset Availability Report (Link KPIs) (Table)
# LinksSignalling_LinkSet.Neutral.GSM.signalling_linkset.linksUser-defined 
Link FailuresSignalling_LinkSet.Neutral.GSM.signalling_linkset.total_failuresUser-defined 
Not displayed (for filtering only)Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverageUser-defined 
LinksetSignalling_LinkSet.nameUser-defined 
Links Unavailable (s)Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_unavailable_timeUser-defined 

Linkset Availability Report Linkset KPIs

This report shows the availability of a set of linksets and failures

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary SelectionTotal
FilteringSignalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_time (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SS7 Linkset Availability Report (Linkset KPIs) (Table)
% Linkset In-serviceSignalling_LinkSet.Neutral.GSM.signalling_linkset.%_availableUser-defined 
LinksetSignalling_LinkSet.nameUser-defined 
Not displayed (for filtering only)Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverageUser-defined 
Linkset Unavailable (s)Signalling_LinkSet.Neutral.GSM.signalling_linkset.unavailable_timeUser-defined 

Linkset Utilisation Report

This report shows the utilisation of a set of linksets through the traffic carried on their constituent links.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
FilteringSignalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_traffic (min), Signalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_traffic (min), Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Linkset Utilisation Report (Table)
# LinksSignalling_LinkSet.Neutral.GSM.signalling_linkset.linksTotal 
LinksetSignalling_LinkSet.nameUser-defined 
TX Usage (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_traffictransmitted_busy_hour 
TX SIF/SIO OctetsSignalling_LinkSet.Neutral.GSM.signalling_linkset.transmitted_sif_siostransmitted_busy_hour 
TX MSUSSignalling_LinkSet.Neutral.GSM.signalling_linkset.transmitted_msustransmitted_busy_hour 
TX Busy Hourtransmitted_busy_hourtransmitted_busy_hour 
TX Average Link (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_outgoing_traffictransmitted_busy_hour 
RX Usage (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_trafficreceived_busy_hour 
RX SIF/SIO OctetsSignalling_LinkSet.Neutral.GSM.signalling_linkset.received_sif_siosreceived_busy_hour 
RX MSUSSignalling_LinkSet.Neutral.GSM.signalling_linkset.received_msusreceived_busy_hour 
RX Busy Hourreceived_busy_hourreceived_busy_hour 
RX Average Link (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_incoming_trafficreceived_busy_hour 
Not displayed (for filtering only)Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverageUser-defined 

MSC Calls Graph

This graph shows network incoming and mobile originating call statistics for the specified MSC over the selected days.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Calls Graph (Line Chart)
AttemptsMSC.Neutral.GSM.traffic.call_attemptsUser-defined 
FailuresMSC.Neutral.GSM.traffic.call_failuresUser-defined 

MSC Handover Graph

This graph shows the handover performance of a MSC for inter-cell intra-MSC handover and incoming and outgoing inter-MSC handover.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Incoming Inter-MSC (Line Chart)
AttemptsMSC.Neutral.GSM.handover.incoming_intermsc_attemptsUser-defined 
FailuresMSC.Neutral.GSM.handover.incoming_intermsc_failuresUser-defined 
Component 2: Inter-Cell Intra-MSC (Line Chart)
FailuresMSC.Neutral.GSM.handover.interbsc_failuresUser-defined 
SuccessesMSC.Neutral.GSM.handover.interbsc_successesUser-defined 
Component 3: Outgoing Inter-MSC (Line Chart)
AttemptsMSC.Neutral.GSM.handover.outgoing_intermsc_attemptsUser-defined 
FailuresMSC.Neutral.GSM.handover.outgoing_intermsc_failuresUser-defined 

MSC Handover Report

This report shows handover performance at the MSC level for either all MSCs in a region or all MSCs in the network during a selected time period. The report shows intra-MSC handover attempts and failures and incoming and outgoing inter-MSC handover attempts and failures.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
FilteringMSC.Neutral.GSM.handover.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Handover Report (Table)
Busy Hourbusy_hourbusy_hour 
Incoming Inter-MSC Handover % FailureMSC.Neutral.GSM.handover.%_incoming_intermsc_failureUser-defined 
Incoming Inter-MSC Handover AttemptsMSC.Neutral.GSM.handover.incoming_intermsc_attemptsUser-defined 
Incoming Inter-MSC Handover FailuresMSC.Neutral.GSM.handover.incoming_intermsc_failuresUser-defined 
Inter-Cell Handover % FailureMSC.Neutral.GSM.handover.%_interbsc_failureUser-defined 
Inter-Cell Handover AttemptsMSC.Neutral.GSM.handover.interbsc_attemptsUser-defined 
Inter-Cell Handover FailuresMSC.Neutral.GSM.handover.interbsc_failuresUser-defined 
MSCMSC.nameUser-defined 
Not displayed (for filtering only)MSC.Neutral.GSM.handover.%_data_coverageUser-defined 
Outgoing Inter-MSC Handover % FailureMSC.Neutral.GSM.handover.%_outgoing_intermsc_failureUser-defined 
Outgoing Inter-MSC Handover AttemptsMSC.Neutral.GSM.handover.outgoing_intermsc_attemptsUser-defined 
Outgoing Inter-MSC Handover FailuresMSC.Neutral.GSM.handover.outgoing_intermsc_failuresUser-defined 

MSC Paging Graph

This graph shows the performance of the paging function for the MSC

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Global Paging (Line Chart)
Failed to RespondMSC.Neutral.GSM.page.global_unresponsesUser-defined 
Pages and RepagesMSC.Neutral.GSM.page.total_global_pagesUser-defined 
Component 2: Location Area Paging (Line Chart)
Failed to RespondMSC.Neutral.GSM.page.local_unresponsesUser-defined 
Pages and RepagesMSC.Neutral.GSM.page.total_local_pagesUser-defined 

MSC Switched Traffic Graph

This graph shows the key traffic performance statistics for an MSC specifically the total switched traffic and total failed calls. Total switched traffic must be calculated by summing traffic from the appropriate traffic categories.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Failed Calls (Line Chart)
% Failed CallsMSC.Neutral.GSM.traffic.total_switched_traffic.%_call_failureUser-defined 
Component 2: Total Switched Traffic (Line Chart)
Total Switched TrafficMSC.Neutral.GSM.traffic.total_switched_traffic.trafficUser-defined 

MSC Switched Traffic Report Individual TT

This report shows key switched traffic statistics for a single MSC or all MSCs in a region or all MSCs in the network during a selected time period. The report shows attempts, calls, failures, %failures, answered, % answered and traffic for all traffic types.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectiontraffic_type_busy_hour, Total
FilteringMSC.Neutral.GSM.traffic.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: [ Traffic Type ] (Table)
% Answered CallsMSC.Neutral.GSM.traffic.%_answered_callsUser-defined 
% Failed CallsMSC.Neutral.GSM.traffic.%_call_failureUser-defined 
Answered CallsMSC.Neutral.GSM.traffic.answered_callsUser-defined 
AttemptsMSC.Neutral.GSM.traffic.call_attemptsUser-defined 
CallsMSC.Neutral.GSM.traffic.call_successesUser-defined 
Failed CallsMSC.Neutral.GSM.traffic.call_failuresUser-defined 
MSCMSC.nameUser-defined 
MSC Busy Hourtraffic_type_busy_hourtraffic_type_busy_hour 
Not displayed (for filtering only)MSC.Neutral.GSM.traffic.%_data_coverageUser-defined 
TrafficMSC.Neutral.GSM.traffic.trafficUser-defined 

MSC Switched Traffic Report Total Switched

This report shows key switched traffic statistics for a single MSC or all MSCs in a region or all MSCs in the network during a selected time period. The report shows the total switched traffic calls, failures % failures, answered, %answered and traffic.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
FilteringMSC.Neutral.GSM.traffic.total_switched_traffic.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Switched Traffic Report (Total Switched Traffic Type) (Table)
% Answered Switched CallsMSC.Neutral.GSM.traffic.total_switched_traffic.%_answered_callsUser-defined 
% Failed Switched CallsMSC.Neutral.GSM.traffic.total_switched_traffic.%_call_failureUser-defined 
Switched TrafficMSC.Neutral.GSM.traffic.total_switched_traffic.trafficUser-defined 
Switched CallsMSC.Neutral.GSM.traffic.total_switched_traffic.call_successesUser-defined 
Switched AttemptsMSC.Neutral.GSM.traffic.total_switched_traffic.call_attemptsUser-defined 
Not displayed (for filtering only)MSC.Neutral.GSM.traffic.total_switched_traffic.%_data_coverageUser-defined 
MSC Busy Hourbusy_hourbusy_hour 
MSCMSC.nameUser-defined 
Failed Switched CallsMSC.Neutral.GSM.traffic.total_switched_traffic.call_failuresUser-defined 
Answered Switched CallsMSC.Neutral.GSM.traffic.total_switched_traffic.answered_callsUser-defined 

MSC Traffic Dispersion Report

For each MSC this report shows calls, answered calls and traffic to each destination recorded by the MSC.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.MSC
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
FilteringMSC.Neutral.GSM.destination.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSC Traffic Dispersion Report (Table)
% AnswersMSC.Neutral.GSM.destination.%_answered_callsUser-defined 
AnswersMSC.Neutral.GSM.destination.answered_callsUser-defined 
TrafficMSC.Neutral.GSM.destination.trafficUser-defined 
Not displayed (for filtering only)MSC.Neutral.GSM.destination.%_data_coverageUser-defined 
MSCMSC.nameUser-defined 
Destination User-defined 
CallsMSC.Neutral.GSM.destination.total_callsUser-defined 
Busy Hourbusy_hourbusy_hour 

Processor Load Graph

This graph shows the performance of a support processor associated with a node against time

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Processor
Primary ObjectProcessor
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionProcessor
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Average
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Processor Load (Line Chart)
% LoadProcessor.Neutral.Generic.cpu.load_pcUser-defined 

Route Congestion Graph

This graph shows the congestion on a selected route

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Congestion (Line Chart)
% CongestionRoute_IF.Neutral.GSM.transmission.%_outgoing_congestionsUser-defined 
Component 2: Congestions (Line Chart)
CongestionsRoute_IF.Neutral.GSM.transmission.outgoing_congestionsUser-defined 
Component 3: Defined and Available Circuits (Line Chart)
Available CircuitsRoute_IF.Neutral.GSM.transmission.available_circuitsUser-defined 
Defined CircuitsRoute_IF.Neutral.GSM.transmission.circuitsUser-defined 
Component 4: Outgoing Bids (Line Chart)
Outgoing BidsRoute_IF.Neutral.GSM.transmission.bidsUser-defined 

Route Exhaustion Report

This report shows all routes that will reach exhaustion in the specified forecast. The report shows carried traffic, % congestion, % utilisation, grade of service and lost traffic in the most recent actual busy hour and then the selected dimensioning parameter, the critical traffic, the sample size, correlation coefficient, traffic growth and exhaustion date. The report is always generated with weekly busy hour values. The user defines the length of forecast in days and the design GOS as runtime parameters, and has the option to include or exclude exhausted routes.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Route_IF, Region
Date RangingYes
Period SelectionWeekly
Summary Selectionbusy_hour, 3-day Average, 5-day Average
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Route Exhaustion Report (Table)
End Date % BlockingRoute_IF.Neutral.GSM.transmission.%_outgoing_congestionsbusy_hour 
End Date % UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationbusy_hour 
End Date CapacityRoute_IF.Neutral.GSM.transmission.capacityUser-defined 
End Date Grade Of ServiceRoute_IF.Neutral.GSM.transmission.grade_of_servicebusy_hour 
End Date Lost Traffic (E)Route_IF.Neutral.GSM.transmission.lost_trafficbusy_hour 
End Date Traffic (E)Route_IF.Neutral.GSM.transmission.trafficbusy_hour 
Exhaustion DateRoute_IF.Neutral.GSM.transmission.forecast.linear_exhaustion_dateUser-defined 
Is ExhaustedRoute_IF.Neutral.GSM.transmission.is_exhaustedUser-defined 
RouteRoute_IF.nameUser-defined 
SamplesRoute_IF.Neutral.GSM.transmission.number_of_samplesUser-defined 
Traffic (E)Route_IF.Neutral.GSM.transmission.trafficUser-defined 
Traffic Growth (Erlangs/week)Route_IF.Neutral.GSM.transmission.forecast.linear_traffic_growthUser-defined 

Route Interface Offered Traffic Graph

This chart shows the trend in the principal route interface parameters: busy hour traffic, 3-DAV and 5-DAV traffic

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionWeekly
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Route Interface Offered Traffic Graph (Line Chart)
CapacityRoute_IF.Neutral.GSM.transmission.capacityUser-defined 
Weekly 3-DAV ValueRoute_IF.Neutral.GSM.transmission.traffic3-day Average 
Weekly 5-DAV ValueRoute_IF.Neutral.GSM.transmission.traffic5-day Average 
Weekly Busy Hour ValueRoute_IF.Neutral.GSM.transmission.trafficbusy_hour 

Route Interface Traffic Forecast Graph

This chart allows the user to plot the weekly trend of either the carried or offered traffic for one of the three following dimensioning parameters: the busy hour traffic; 3-day average traffic; or, the 5-day average traffic. It also plots a regression of the selected dimensioning parameter extrapolated over a user-defined forecast period.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionWeekly
Summary Selectionbusy_hour, 3-day Average, 5-day Average
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: [N]-Day Route Interface Traffic Forecast Graph (Line Chart)
Capacity GOS=[GOS1]Route_IF.Neutral.GSM.transmission.forecast.capacityUser-defined 
Coefficient of RegressionRoute_IF.Neutral.GSM.transmission.forecast.linear_regression_coefficientUser-defined 
Growth is [linear_traffic_growth] Erlangs/weekRoute_IF.Neutral.GSM.transmission.forecast.linear_traffic_growthUser-defined 
Route Interface [will reach exhaustion on date|will not reach exhaustion in this period]Route_IF.Neutral.GSM.transmission.forecast.linear_exhaustion_dateUser-defined 
Standard Error of RegressionRoute_IF.Neutral.GSM.transmission.forecast.linear_regression_errorUser-defined 
TrafficRoute_IF.Neutral.GSM.transmission.trafficUser-defined 
Traffic ForecastRoute_IF.Neutral.GSM.transmission.forecast.trafficUser-defined 

Route Low Utilisation Report

This report shows all routes that will remain consistently under utilised in the forecast period i.e. start off with low utilisation and finish with low utilisation. The report shows carried traffic, % congestion, % utilisation, grade of service and lost traffic in the most recent actual busy hour and then the selected dimensioning parameter, the critical traffic, the sample size, correlation coefficient and current and final utilisation. The report is always generated with weekly busy hour values. The report can be filtered on the maximum current utilisation and forecast utilisation; these parameters mandatory and default to 25%. The user defines the length of forecast in days and the design GOS as runtime parameters.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Route_IF, Region
Date RangingYes
Period SelectionWeekly
Summary Selectionbusy_hour, 3-day Average, 5-day Average
FilteringRoute_IF.Neutral.GSM.transmission.offered_utilisation (max), Route_IF.Neutral.GSM.transmission.forecast.utilisation (max)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Route Low Utilisation Report (Table)
CapacityRoute_IF.Neutral.GSM.transmission.capacityUser-defined 
End Date % CongestedRoute_IF.Neutral.GSM.transmission.%_outgoing_congestionsbusy_hour 
End Date % UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationbusy_hour 
End Date Grade of ServiceRoute_IF.Neutral.GSM.transmission.grade_of_servicebusy_hour 
End Date Lost Traffic (E)Route_IF.Neutral.GSM.transmission.lost_trafficbusy_hour 
End Date Traffic (E)Route_IF.Neutral.GSM.transmission.trafficbusy_hour 
Forecast % UtilisationRoute_IF.Neutral.GSM.transmission.forecast.utilisationbusy_hour 
RouteRoute_IF.nameUser-defined 
SamplesRoute_IF.Neutral.GSM.transmission.number_of_samplesUser-defined 
Traffic (E)Route_IF.Neutral.GSM.transmission.trafficUser-defined 

Route Required Circuits Report

This report shows the forecast circuit requirements for a set of routes for three different forecast periods. The forecast can be dimensioned using Weekly BH, 3-DAV or 5-DAV values of carried or offered traffic. For all selected routes, the report shows the sample size, the correlation coefficient of the forecast, the actual and required number of circuits and the selected dimensioning parameter in the latest busy hour and then the required circuits and forecast traffic at periods of N1, N2 and N3 days ahead where N1, N2 and N3 are configurable but default to 60, 90 and 120. The report is always generated with weekly busy hour values.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Route_IF, Region
Date RangingYes
Period SelectionWeekly
Summary Selectionbusy_hour, 3-day Average, 5-day Average
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Route Required Circuits Report (Table)
End Date Defined CircuitsRoute_IF.Neutral.GSM.transmission.circuitsbusy_hour 
End Date Grade Of ServiceRoute_IF.Neutral.GSM.transmission.grade_of_servicebusy_hour 
[N3] Days Forecast Extra CircuitsRoute_IF.Neutral.GSM.transmission.forecast.extra_circuitsUser-defined 
[N1] Days Forecast Required No. Of CircuitsRoute_IF.Neutral.GSM.transmission.forecast.required_circuitsUser-defined 
SamplesRoute_IF.Neutral.GSM.transmission.number_of_samplesUser-defined 
RouteRoute_IF.nameUser-defined 
Latest Actual Traffic (E)Route_IF.Neutral.GSM.transmission.trafficUser-defined 
Latest Actual Required No. Of CircuitsRoute_IF.Neutral.GSM.transmission.required_circuitsUser-defined 
End Date UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationbusy_hour 
End Date Lost Traffic (E)Route_IF.Neutral.GSM.transmission.lost_trafficbusy_hour 

Route Traffic Graph

This graph shows the traffic profile for a selected route.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Answer Seize Ratio (Line Chart)
% Answer Seize RatioRoute_IF.Neutral.GSM.transmission.%_outgoing_answeredUser-defined 
Component 2: Calls (Line Chart)
IncomingRoute_IF.Neutral.GSM.transmission.incoming_callsUser-defined 
OutgoingRoute_IF.Neutral.GSM.transmission.outgoing_callsUser-defined 
Component 3: Traffic (Line Chart)
IncomingRoute_IF.Neutral.GSM.transmission.incoming_trafficUser-defined 
OutgoingRoute_IF.Neutral.GSM.transmission.outgoing_trafficUser-defined 

Route Traffic Report

This report shows key route traffic statistics for either all routes or all routes in a specified region or all routes from a specified MSC or all routes of a certain type during a selected time period.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Route_IF, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectionincoming_busy_hour, outgoing_busy_hour, busy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Bothway (Table)
% UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationUser-defined 
ASRRoute_IF.Neutral.GSM.transmission.%_bothway_answeredUser-defined 
Available CircuitsRoute_IF.Neutral.GSM.transmission.available_circuitsUser-defined 
Busy Hourbusy_hourbusy_hour 
CallsRoute_IF.Neutral.GSM.transmission.bothway_callsUser-defined 
CongestionRoute_IF.Neutral.GSM.transmission.%_outgoing_congestionsUser-defined 
Defined CircuitsRoute_IF.Neutral.GSM.transmission.circuitsUser-defined 
GOSRoute_IF.Neutral.GSM.transmission.grade_of_serviceUser-defined 
RouteRoute_IF.nameUser-defined 
TrafficRoute_IF.Neutral.GSM.transmission.bothway_trafficUser-defined 
Component 2: Incoming (Table)
ASRRoute_IF.Neutral.GSM.transmission.%_incoming_answeredUser-defined 
Busy Hourincoming_busy_hourincoming_busy_hour 
CallsRoute_IF.Neutral.GSM.transmission.incoming_callsUser-defined 
RouteRoute_IF.nameUser-defined 
TrafficRoute_IF.Neutral.GSM.transmission.incoming_trafficUser-defined 
Component 3: Outgoing (Table)
ASRRoute_IF.Neutral.GSM.transmission.%_outgoing_answeredUser-defined 
Busy Houroutgoing_busy_houroutgoing_busy_hour 
CallsRoute_IF.Neutral.GSM.transmission.outgoing_callsUser-defined 
CongestionsRoute_IF.Neutral.GSM.transmission.%_outgoing_congestionsUser-defined 
RouteRoute_IF.nameUser-defined 
TrafficRoute_IF.Neutral.GSM.transmission.outgoing_trafficUser-defined 

Route Utilisation Graph

This graph shows the trend in utilisation of a route: traffic (offered and carried), % utilisation and calculated GOS.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionRoute_IF
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: % Utilisation (Line Chart)
Graph Overlay Value: User-defined
100% overlay
% UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationUser-defined 
Component 2: Carried Traffic (E) (Line Chart)
Critical Traffic (overlay)Route_IF.Neutral.GSM.transmission.capacityUser-defined 
Traffic (E)Route_IF.Neutral.GSM.transmission.bothway_trafficUser-defined 
Component 3: GoS (Line Chart)
Graph Overlay Value: User-defined
Desgin GOS overlay
Grade Of ServiceRoute_IF.Neutral.GSM.transmission.grade_of_serviceUser-defined 
Component 4: Offered Traffic (E) (Line Chart)
Critical Traffic (overlay)Route_IF.Neutral.GSM.transmission.capacityUser-defined 
Traffic (E)Route_IF.Neutral.GSM.transmission.offered_trafficUser-defined 

Signalling Linkset Exhaustion Report

This report shows all linksets that will reach exhaustion in the specified forecast. The report is always generated with weekly busy hour values. The user has the option to set the following run-time parameters: Nominal Maximum Traffic - Default value 0.4, Maximum In-Failure Traffic - Default value 0.8, Default Links In-Failure - Default value 1.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingYes
Period SelectionWeekly
Summary Selectionreceived_busy_hour, transmitted_busy_hour
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SS7 Linkset Exhaustion Report (Table)
CapacitySignalling_LinkSet.Neutral.GSM.signalling_linkset.capacityUser-defined 
Designed Link FailuresSignalling_LinkSet.Designed_Link_FailuresUser-defined 
Exhaustion DateSignalling_LinkSet.Neutral.GSM.forecast.linear_exhaustion_dateUser-defined 
In-Failure CapacitySignalling_LinkSet.Neutral.GSM.signalling_linkset.in_failure_capacityUser-defined 
Is ExhaustedSignalling_LinkSet.Neutral.GSM.signalling_linkset.is_exhaustedUser-defined 
LinksSignalling_LinkSet.Neutral.GSM.signalling_linkset.linksUser-defined 
Linkset NameSignalling_LinkSet.nameUser-defined 
MSUsSignalling_LinkSet.Neutral.GSM.signalling_linkset.msusUser-defined 
SamplesSignalling_LinkSet.Neutral.GSM.signalling_linkset.number_of_samplesUser-defined 
TrafficSignalling_LinkSet.Neutral.GSM.signalling_linkset.trafficUser-defined 
Traffic ForecastSignalling_LinkSet.Neutral.GSM.forecast.trafficUser-defined 
Traffic GrowthSignalling_LinkSet.Neutral.GSM.forecast.linear_traffic_growthUser-defined 

SS7 Link Availability Graph

This graph shows the link availability for a selected SS7 link

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Link
Primary ObjectSignalling_Link
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_Link
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary SelectionTotal
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Total % Link Availability (Line Chart)
% Link AvailabilitySignalling_Link.Neutral.GSM.link.%_availableTotal 
Component 2: Total % Local Busy (Line Chart)
% Local BusySignalling_Link.Neutral.GSM.link.%_local_inhibition_timeTotal 
Component 3: Total Link Failures (Line Chart)
Link FailuresSignalling_Link.Neutral.GSM.link.failuresTotal 

SS7 Linkset Availability Graph Link KPIs

This graph shows the linkset availability of the constituent links for a selected SS7 linkset.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary SelectionTotal
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Total % Link Availability (Line Chart)
% Link AvailabilitySignalling_LinkSet.Neutral.GSM.signalling_linkset.mean_%_availableTotal 
Component 2: Total Link Failures (Line Chart)
Link FailuresSignalling_LinkSet.Neutral.GSM.signalling_linkset.total_failuresTotal 

SS7 Linkset Availability Graph Linkset KPIs

This graph shows the linkset availability for a selected SS7 linkset.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary SelectionTotal
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Total % Linkset Availability (Line Chart)
% Linkset AvailabilitySignalling_LinkSet.Neutral.GSM.signalling_linkset.%_availableTotal 
Component 2: Total Linkset Failures (Line Chart)
Linkset FailuresSignalling_LinkSet.Neutral.GSM.signalling_linkset.failuresTotal 

SS7 Linkset Utilisation Graph

This graph shows the linkset transmission and reception utilisation for a selected SS7 link.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionreceived_busy_hour, transmitted_busy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Signalling Linkset MSUs on Linkset (Line Chart)
RXSignalling_LinkSet.Neutral.GSM.signalling_linkset.received_msusUser-defined 
TXSignalling_LinkSet.Neutral.GSM.signalling_linkset.transmitted_msusUser-defined 
Component 2: Signalling Linkset Traffic (Octets) (Line Chart)
IncomingSignalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_trafficUser-defined 
OutgoingSignalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_trafficUser-defined 

SS7 Linkset Utilisation Report RX

This report shows the utilisation of a set of linksets through the traffic received on their constituent links.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectionreceived_busy_hour, Total
FilteringSignalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SS7 Linkset Utilisation Report (RX) (Table)
# LinksSignalling_LinkSet.Neutral.GSM.signalling_linkset.linksUser-defined 
LinksetSignalling_LinkSet.nameUser-defined 
Not displayed (for filtering only)Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverageUser-defined 
RX Average Link (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_incoming_trafficUser-defined 
RX Busy Hourreceived_busy_hourreceived_busy_hour 
RX MSUSSignalling_LinkSet.Neutral.GSM.signalling_linkset.received_msusUser-defined 
RX SIF/SIO OctetsSignalling_LinkSet.Neutral.GSM.signalling_linkset.received_sif_siosUser-defined 
RX Usage (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.incoming_trafficUser-defined 

SS7 Linkset Utilisation Report TX

This report shows the utilisation of a set of linksets through the traffic transmitted on their constituent links.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet, Signalling_Point, Region
Date RangingNo
Period SelectionDaily (Raw), Daily, Weekly, Monthly
Summary Selectiontransmitted_busy_hour, Total
FilteringSignalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverage (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: SS7 Linkset Utilisation Report (TX) (Table)
# LinksSignalling_LinkSet.Neutral.GSM.signalling_linkset.linksUser-defined 
LinksetSignalling_LinkSet.nameUser-defined 
TX Usage (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.outgoing_trafficUser-defined 
TX SIF/SIO OctetsSignalling_LinkSet.Neutral.GSM.signalling_linkset.transmitted_sif_siosUser-defined 
TX MSUSSignalling_LinkSet.Neutral.GSM.signalling_linkset.transmitted_msusUser-defined 
TX Busy Hourtransmitted_busy_hourtransmitted_busy_hour 
TX Average Link (Octets)Signalling_LinkSet.Neutral.GSM.signalling_linkset.mean_outgoing_trafficUser-defined 
Not displayed (for filtering only)Signalling_LinkSet.Neutral.GSM.signalling_linkset.%_data_coverageUser-defined 

SS7 Link Utilisation Graph

This graph shows the link utilisation for a selected SS7 link.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Link
Primary ObjectSignalling_Link
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_Link
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionreceived_busy_hour, transmitted_busy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: MSUs (Line Chart)
ReceivedSignalling_Link.Neutral.GSM.link.received_msusUser-defined 
TransmittedSignalling_Link.Neutral.GSM.link.transmitted_msusUser-defined 
Component 2: SIF and SIO Octets (Line Chart)
ReceivedSignalling_Link.Neutral.GSM.link.received_sif_siosUser-defined 
TransmittedSignalling_Link.Neutral.GSM.link.transmitted_sif_siosUser-defined 
Component 3: Traffic (Line Chart)
IncomingSignalling_Link.Neutral.GSM.link.incoming_trafficUser-defined 
OutgoingSignalling_Link.Neutral.GSM.link.outgoing_trafficUser-defined 

SS7 Signalling Linkset Traffic Forecast Graph

This chart allows the user to plot the weekly trend of either the busy hour received or transmitted traffic. It also plots a regression of the selected parameter extrapolated over a user-defined forecast period. The report is always generated with weekly busy hour values. The user has the option to set the following run-time parameters: Nominal Maximum Traffic - Default value 0.4, Maximum In-Failure Traffic - Default value 0.8, Default Links In-Failure - Default value 1.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Linkset
Primary ObjectSignalling_LinkSet
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionSignalling_LinkSet
Date RangingYes
Period SelectionWeekly
Summary Selectionreceived_busy_hour, transmitted_busy_hour
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Heading (Line Chart)
Coefficient of RegressionSignalling_LinkSet.Neutral.GSM.forecast.linear_regression_coefficientUser-defined 
Growth is {linear_traffic_growth}Signalling_LinkSet.Neutral.GSM.forecast.linear_traffic_growthUser-defined 
Linkset [will reach exhaustion on {linear_exhaustion_date}|will not reach exhaustion in this period]Signalling_LinkSet.Neutral.GSM.forecast.linear_exhaustion_dateUser-defined 
Standard Error of RegressionSignalling_LinkSet.Neutral.GSM.forecast.linear_regression_errorUser-defined 
Component 2: SS7 Signalling Linkset Traffic Forecast Graph (Line Chart)
CapacitySignalling_LinkSet.Neutral.GSM.forecast.capacityUser-defined 
Forecast TrafficSignalling_LinkSet.Neutral.GSM.forecast.trafficUser-defined 
TrafficSignalling_LinkSet.Neutral.GSM.signalling_linkset.trafficUser-defined 
In-Failure CapacitySignalling_LinkSet.Neutral.GSM.forecast.in_failure_capacityUser-defined 

Summary Route Traffic Report

This report shows key route traffic statistics for a set of routes in a selected time period. The report shows available & defined circuits, % congestion, carried traffic, offered traffic, lost traffic, critical traffic, 3-DAV and 5-DAV traffic, % utilisation and grade of service. The report is always generated with weekly busy hour values.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.Route
Primary ObjectRoute_IF
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object SelectionMSC, Route_IF, Region
Date RangingNo
Period SelectionWeekly
FilteringRoute_IF.Neutral.GSM.transmission.traffic (min), Route_IF.Neutral.GSM.transmission.grade_of_service (min), Route_IF.Neutral.GSM.transmission.lost_traffic (min), Route_IF.Neutral.GSM.transmission.offered_utilisation (min)

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: Summary Route Traffic Report (Table)
3-DAV Summarised Carried Traffic (E)Route_IF.Neutral.GSM.transmission.traffic3-day Average 
5-DAV Summarised Carried Traffic (E)Route_IF.Neutral.GSM.transmission.traffic5-day Average 
Available CircuitsRoute_IF.Neutral.GSM.transmission.available_circuitsbusy_hour 
Blocking (%)Route_IF.Neutral.GSM.transmission.%_outgoing_congestionsbusy_hour 
Busy Hourbusy_hourbusy_hour 
CapacityRoute_IF.Neutral.GSM.transmission.capacitybusy_hour 
Carried Traffic (E)Route_IF.Neutral.GSM.transmission.trafficUser-defined 
Defined CircuitsRoute_IF.Neutral.GSM.transmission.circuitsbusy_hour 
Grade of ServiceRoute_IF.Neutral.GSM.transmission.grade_of_servicebusy_hour 
Lost Traffic (E)Route_IF.Neutral.GSM.transmission.lost_trafficbusy_hour 
Offered Traffic (E)Route_IF.Neutral.GSM.transmission.offered_trafficbusy_hour 
Offered UtilisationRoute_IF.Neutral.GSM.transmission.offered_utilisationbusy_hour 
RouteRoute_IF.nameUser-defined 

System Traffic MSC Graph

This graph shows the total switch traffic for the appropriate traffic categories totalled for all MSCs in the network.

Overview

Report FeatureDetails
Report Tree BranchGSM.Engineering.Core Network.System
Primary ObjectMSC
Drill-down Behaviour 

Report Parameters

ParameterOptions
Object Selection 
Date RangingYes
Period SelectionRaw, Daily, Weekly, Monthly
Summary Selectionbusy_hour, Total
Filtering 

Report Components

LabelAttribute/KPISummary TypeOverlay
Component 1: System Traffic (MSC) Graph (Line Chart)
Traffic (E)MSC.Neutral.GSM.traffic.total_switched_traffic.trafficUser-defined 


11. Data Availability

This section lists the data availability definitions for the network objects previously described.

Grouping ObjectKPI TypeReporting ObjectDefining KPI Group
MSCMSCs ReportingMSCMSC.Neutral.GSM.page